[GH Actions] Move 'lock.yml' to '.github/workflows' to make it work

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context

I stumbled on the inactive lock.yml github action just because it's in the root directory. To make it work, it should be in .github/workflows. You can see that it hasn't been active in the actions tab.
I assumed this is unexpected based on https://github.com/fastlane/fastlane/pull/16446, but please let me know if we'd like to remove it for some reason.
Description

Just moved lock.yml to .github/workflows to make it work again.
Testing Steps

Tested the action is shown in the actions tab in my private repo with this change.

This change seems to cause failures with lock workflow on forked repos every midnight as forked repos don't have access to GitHub's access token😅

Perhaps there is a better way to handle this, but as far as I know, you could delete all the workflow for Locking issues and pull requests in the forked repository. Unfortunately, you need to do so one by one.

 Sorry for the inconvenience!


Typo and wrong charts in plot_time_function.py

The last loop:
for tf, ax in zip(time_functions, ax_list):
plot_timefunction(tf_1, ax=ax)
ax.set_ylim([-0.5, 6.0])
plt.show()
Should be:
for tf, ax in zip(time_functions, ax_list):
plot_timefunction(tf, ax=ax)
ax.set_ylim([-0.5, 6.0])
plt.show()
And now the charts will be different (now they're all the same).

PRs are welcome @MarcosCarreira

I believe this has been resolved

Yes, the PR was accepted. https://github.com/X-DataInitiative/tick/blob/master/doc/modules/code_samples/plot_time_function.py is Ok now but https://x-datainitiative.github.io/tick/auto_examples/plot_time_function.html still shows the old version.

ok we have to regenerate the documentation, thanks @MarcosCarreira


Spanish locale.

Is there any reason why the spanish locale is not included with the gem as the others [de, en, nb, pl, ru]?
Also the 'es' locale in the spec file have a typo that I would gladly fix. I know that for the purpose of where it's being used doesn't matter (it's just to confirm that the gem would work with custom locales) but if a non-spanish speaker would take it to use in their own application then it's a problem.

No idea. Probably legacy reasons. If you could submit a PR to move it in there that would be nice.

On 4 Mar 2015, at 04:19, Luis Urraca<EMAIL_ADDRESS>wrote:
Is there any reason why the spanish locale is not included with the gem as the others [de, en, nb, pl, ru]?
Also the 'es' locale in the spec file have a typo that I would gladly fix. I know that for the purpose of where it's being used doesn't matter (it's just to confirm that the gem would work with custom locales) but if a non-spanish speaker would take it to use in their own application then it's a problem.
—
Reply to this email directly or view it on GitHub.


Serverless Deployment

any discussion forums? I would like to deploy my first app

We have chat in Discord 🙂


comments

If you face any problems please comment here or dm me.

If you face any problems please comment here.


[Feature Request] variable initial and local value

Hello,
thanks for your awesome work.
The variables in the environment or pre-request are saved on the git repo.
So if I'm testing something and one of my colleague changes the same variable it's a problem.
Could you implement an "initial value" saved on the collection, and a "local value" not saved, so if one changes the local it won't be saved in the git repo?. Obviously the local value, if present, must overwrite the initial value.
Thanks
Andrea

This sounds related to #1033
Any mechanism that would let me set a variable value, but NOT save that value to the file would be great.

Yep the 1033 Is an awesome request, but if you have 10 variables and usually you have to change 1 or 2 values a default value would be great. Just save those default values on a file local.json like secret.json and let the user to customize it: for example when the popup is showed prefill with default values, a button "save as default" will alter then  and another "continue" will use those values, even changed, without saving it.

...Just save those default values on a file local.json like secret.json and let the user to customize it...

That's exactly what I had in mind, although I think I'd want these values to be even more transient, so that they don't carry over to the next session, or maybe even if I closed the tab and reopened it. I want an in-memory-only option so that I don't accidentally run one of these requests with the same values in the future. Maybe the dialog could have checkboxes to determine whether or not the values would be retained at all.

Probably, we can consider these ephemeral variables as secrets. It will prevent these values from being pushed to git.


Unexpected behavior with a singleton actor server outage when queued messages are pending

queued-msg-problem.zip
scenario 1: stop and restart actor server with queued messages (works)

start server: kar run -app queue -actors Stateful -- node stateful-server.js
create queue of messages: kar run -app queue -actors Stateful -- node queue-stateful.js 10
before queue is fully processed, kill and restart actor server
result: actor server continues processing queued messages after restart

scenario 2: same as s1, but with a client interacting with the actor during the outage (hangs)

start server as in s1 above
start probe-client: kar run -missing_component_timeout 0 -app queue -actors Stateful -- node probe-stateful.js
create queue of messages as in s1 above
before queue is fully processed, kill actor server, wait 10 seconds and restart actor server
result: actor server will not process any more queued messages until probe-client is killed
note: if there are two actor server instances, the actor immediately migrates to the other server and all works

scenario 3: same as s2, but only kill and restart server when no messages are queued (works)

start server as in s1
start probe-client as in s1
create queue of messages and let them complete processing
kill and restart actor server
reset server state: kar invoke -app queue Stateful singleton clear (works)
result: probe reports that the server state has changed

Very likely this will be fixed by the new Kafka-only roc library, but leaving open until we can verify


I failed to publish npm package (v1.0.3.)

Today, I tried to publish npm package from our latest GitHub repository.
But I found that I failed to build it and the unvt/kata package in npm is still v.1.0.2.
https://github.com/unvt/kata/runs/5990663867?check_suite_focus=true
Can anyone have any advice on this issue? I am sorry for my poor experience in this area, but I appreciate your kind support.
Yours, Taro Ubukawa

itoma has been released as v.1.0.4. Thank you @miya0001 !


Bump the version of @azure/communication-common to 2.2.0 in all ACS packages

Packages impacted by this PR

@azure/communication-*

Describe the problem that is addressed by this PR

there is a new version of the @azure/communication-common which should be adopted by all communication packages

Are there test cases added in this PR? (If not, why?)

no, adjusted existing functionality

Provide a list of related PRs (if any)

https://github.com/Azure/azure-sdk-for-js/pull/23264
https://github.com/Azure/azure-sdk-for-js/pull/23504

Checklists

[x] Added impacted package name to the issue description
[x] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

/azp run js - communication-chat - tests
/azp run js - communication-phone-numbers - tests
/azp run js - communication-rooms - tests
/azp run js - communication-network-traversal - tests
/azp run js - communication-sms - tests
/azp run js - communication-email- tests
/azp run js - communication-short-codes - tests
/azp run js - communication-alpha-ids - tests
/azp run js - communication-identity - tests

/azp run js - communication-chat - tests

/azp run js - communication-phone-numbers - tests

/azp run js - communication-network-traversal - tests

/azp run js - communication-sms - tests

/azp run js - communication-email- tests

/azp run js - communication-short-codes - tests

/azp run js - communication-identity - tests

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

/azp run js - communication-phone-numbers - ci

/azp run js - communication-rooms - ci

/azp run js - communication-sms - ci

/azp run js - communication-short-codes - ci

/azp run js - communication-phone-numbers - tests

/azp run js - communication-rooms - tests

/azp run js - communication-short-codes - tests

/azp run js - communication-sms - tests

/azp run js - communication-identity - tests


Azure Region switch not working

Hi, I am evaluating terraspaces deploy to multiple region functionality and it doesnt seem to let me switch region.
I first set my defaults to northeurope and deployed and that worked fine, i then attempted to change to westeurope. As per the guide i ran the az cli commands to set the region
az configure --defaults location=westeurope
I confirmed that  it was set in my defaults
az configure --list-defaults
Then i ran
terraspace up demo
it built for northeurope
I then created a new terraspace project to see if there was some kind of persistance in teh project and it still sticks with northeurope.
It appears that its maintaining some cache where by the az settings are being stored in memory.

Realised this was due to a conflict between an env var and the AZ CLI defaults.


Hutchison/master

replaces #3966

Thanks @specialunderwear for writing the test case! And thanks to @joeyjurjens for merging! 👍


Enable to trace the elapsed time of assigning/revoking partitions

移除了consumer端追蹤subscription的功能，當時我睡眠不足設計得不夠好
將Report改為基礎類別，同時producer/consumer 各自有延伸類別，這是因為兩者會有不同的指標需要呈現
consumer現在會額外印出rebalance過程中每次被呼叫的延遲，如下方示範

consumer completion rate: 92.83%
  average throughput: 312.567 MB/second
  end-to-end max latency: 69423 ms
  end-to-end mim latency: 0 ms
  subscription max latency: 9169 ms
  subscription average latency: 2930.451901901902 ms
  consumer[0] has 2 partitions
  consumer[0] average throughput: 111.684 MB
  consumer[0] average ene-to-end latency: 10634.607 ms
  consumer[1] has 3 partitions
  consumer[1] average throughput: 97.400 MB
  consumer[1] average ene-to-end latency: 41353.370 ms
  consumer[2] has 0 partitions
  consumer[2] average throughput: 103.485 MB
  consumer[2] average ene-to-end latency: 19784.386 ms

@harryteng9527 再麻煩看一下，我希望能稍微推進一下consumer的進度


Issue#2210 : Unit Tests for SmtpDataStuffing (2)

Implemented feedback from #2228
Let me know if more tests are needed or if I'm missing something.

I've updated changes from the review for #2210 . Let me know if anything else is required.

Thanks!
I cleaned up the tests a bit and merged manually. See https://github.com/k9mail/k-9/commit/47b86f6146f5e95f1027e6e129e1febf794ff5b8


Improve the Homebrew Debugging Experience

Older revision of this issue.

Note:  This issue was previously named/titled:
  [Feature Request] Add Support for Step-Into Debugging Homebrew With pry-byebug

Main Issue Body (Feature Request)
Please replace this section with:

A detailed description of your proposed feature:
     When troubleshooting an issue with Homebrew or one of its various and sundry available formulas, the tool's users may occasionally wish to understand how it's behaving during execution given any particular invocation.  Some useful techniques to do this are those of step-into debugging.  An oft-recommended tool for doing such debugging in Ruby code is pry-byebug.  Users should be able to tell Homebrew to execute itself within the context of pry-byebug.

The motivation for the feature:
     Originally, I yearned for this functionality while debugging a particular formula (vim, when installed --with-client-server when its python dependency is installed --with-tcl-tk; I'd reference the associated issue here, but that would spam it with an unneeded in-thread GitHub notification.)  It occurred to me while hacking my way around doing this without the feature proposed here that the functionality in question could prove useful not only in my current situation, but also in an untold future number of debugging scenarios involving Homebrew itself or one of the formulas directing its actions; people troubleshooting problems of any of this sort in the past would likely also have loved to have access to such tooling then, too.

How the feature would be relevant to at least 90% of Homebrew users (if it's not: do not open a feature request:)
     Any effort to ease understanding, and thus maintainability, of a software project should find a warm welcome among its maintainers and contributors.  The feature proposed/requested here would go a non-trivial length of the way towards enabling Homebrew internals and formula developers to better understand the package manager's behavior when it fails to match their expectations.
(N. b.:  This text could likely be improved substantially, but I'm leaving it as is for now.)

What alternatives to the feature you have considered:
     Alternatively, the pry-byebug-based debugging functionality proposed here could instead not be implemented.  Homebrew internals and formula developers would then continue to temporarily insert ad-hoc code for tracing execution into brew's implementation as they do now.  This approach, however, brings along with it at least the following few problematic pain points:

Anybody wishing to debug a 'require' statement to see why it's not finding something will need to step over, not into, its implementation's uses of 'RUBYGEMS_ACTIVATION_MONITOR;' trying to introspect them quickly leads to deadlock and a crashed Pry session.

Homebrew's internal implementation easily spawns multiple processes, each with their own separate entry point within the project's source code.  Pry needs a separate in-code invocation for each of these entry points; otherwise, entering each new one of these beyond the one through which the tool was first brought to bear either allows execution past them to continue unhindered by its introspection capabilities or causes the user's Pry session to hang while attempting to do that.  Examples of such entry points include, relative to Homebrew's repository root:

FormulaInstaller#build (currently starting on line 718 of 'Library/Homebrew/formula_installer.rb' as of this writing.)  This uses:

'Utils.safe_fork,' regardless.
'Sandbox.exec' if using the build sandbox, as is the default.  (Disable-able using brew's '--no-sandbox' argument or 'HOMEBREW_NO_SANDBOX' environment variable as a workaround.)   (Note that this is especially problematic, as the sandbox used for this operation has no provisions in place for Pry to run without running up against its restrictions.)

I'll document more examples of such trouble as I remember or run into them.

Other alternatives may well exist, but have not yet been considered for addition to this issue documentation.
Future Extensions
     The proposed functionality could, in future, be extended to allow users to specify a particular section in Homebrew's code from whence to start tracing brew's execution, thereby avoiding any overhead incurred by stepping through the preceding code manually.  This or any other such further improvement would, however, likely involve modifying `breathe program's source to include additional complexity beyond what would be necessary to implement what I've initially proposed here and is thus not put forth for consideration at the current time.

(Note that I didn't submit this issue upstream because I've already been asked to create a pull request for this instead.)

(Notes:

This issue may well work better as one that's explicitly meant only for my personal use and hence scoped locally only to this repository fork of mine, as opposed to one meant for upstreaming.  Consider doing whatever refactoring ends up being needed to change this issue's text accordingly.
Either way, this issue's format and style are based on that/those from what may well be an earlier version of upstream's issue template for feature requests.  Consider updating this issue's format and style to update and bring it in line with upstream's current format and style.)

Main Issue Body (Feature Request)
Please replace this section with:

A detailed description of your proposed feature:
     When troubleshooting an issue with Homebrew or one of its various and sundry available formulas, the tool's users may occasionally wish to understand how it's behaving during execution given any particular invocation.  Some useful techniques to do this are those of step-into debugging.  Users should be able to tell Homebrew to execute itself within the context of a suitable Ruby debugging tool.
     An oft-recommended tool for doing such debugging in Ruby code was pry-byebug.  'byebug,' the tool that pry-byebug extended Pry with capabilities from, has, however, long since become unmaintained.  A (fairly straightforward) replacement likely exists, but I haven't yet done enough research to find out yet.

The motivation for the feature:
     Originally, I yearned for this functionality while debugging a particular formula (vim, when installed --with-client-server when its python dependency is installed --with-tcl-tk; I'd reference the associated issue here, but that would spam it with an unneeded in-thread GitHub notification.)  It occurred to me while hacking my way around doing this without the feature proposed here that the functionality in question could prove useful not only in my current situation, but also in an untold future number of debugging scenarios involving Homebrew itself or one of the formulas directing its actions; people troubleshooting problems of any of this sort in the past would likely also have loved to have access to such tooling then, too.

How the feature would be relevant to at least 90% of Homebrew users (if it's not: do not open a feature request:)
     Any effort to ease understanding, and thus maintainability, of a software project should find a warm welcome among its maintainers and contributors.  The feature proposed/requested here would go a non-trivial length of the way towards enabling Homebrew internals and formula developers to better understand the package manager's behavior when it fails to match their expectations.
(N. b.:  This text could likely be improved substantially, but I'm leaving it as is for now.)

What alternatives to the feature you have considered:
     Alternatively, the debugging functionality proposed here could instead not be implemented.  Homebrew internals and formula developers would then continue to temporarily insert ad-hoc code for tracing execution into brew's implementation as they do now.  This approach, however, brings along with it at least the following few problematic pain points:

Anybody wishing to debug a 'require' statement to see why it's not finding something will need to step over, not into, its implementation's uses of 'RUBYGEMS_ACTIVATION_MONITOR;' trying to introspect them quickly leads to deadlock and a crashed Pry session.

Homebrew's internal implementation easily spawns multiple processes, each with their own separate entry point within the project's source code.  Pry needs a separate in-code invocation for each of these entry points; otherwise, entering each new one of these beyond the one through which the tool was first brought to bear either allows execution past them to continue unhindered by its introspection capabilities or causes the user's Pry session to hang while attempting to do that.  Examples of such entry points include, relative to Homebrew's repository root:

FormulaInstaller#build (currently starting on line 718 of 'Library/Homebrew/formula_installer.rb' as of this writing.)  This uses:

'Utils.safe_fork,' regardless.

'Sandbox.exec' if using the build sandbox, as is the default.  (Disable-able using brew's '--no-sandbox' argument or 'HOMEBREW_NO_SANDBOX' environment variable as a workaround.)   (Note that this is especially problematic, as the sandbox used for this operation has no provisions in place for Pry to run without running up against its restrictions.)
CAUTION!
     Upstream has begun considering deprecating and obsoleting/removing both --no-sandbox' argument and its 'HOMEBREW_NO_SANDBOX' environment variable.  (Note:  I need to go back and find where this has been discussed.)  This will make it impossible, or at least extremely difficult, to debug any potential issues with the sandbox, but upstream considers its build and process sandboxing functionality stable enough that it won't need any further debugging regardless of how true that turns out to be in the future.

I'll document more examples of such trouble as I remember or run into them.

Other alternatives may well exist but have not yet been considered for addition to this issue documentation.
Future Extensions
     The proposed functionality could, in future, be extended to allow users to specify a particular section in Homebrew's code from whence to start tracing brew's execution, thereby avoiding any overhead incurred by stepping through the preceding code manually.  This or any other such further improvement would, however, likely involve modifying `breathe program's source to include additional complexity beyond what would be necessary to implement what I've initially proposed here and is thus not put forth for consideration at the current time.

     (Note that I didn't submit this issue upstream because I've already been asked to create a pull request for this instead.)

     I'm deferring pursuing this myself until my Ruby skills have improved significantly.  (Granted, that may be a while, hence me adding the 'help wanted' label just now.)

     I've updated my OP here with some examples of problems that are easy to run into during ad-hoc debugging attempts, particularly with respect to multiprocessing and alternative entry points (currently only the ways they're called, but I'll list some out later.)

     Since I initially staged this issue here, support for Byebug itself was landed upstream by @vidusheeamoli in Homebrew/bew@7577.  One does still, however, need to have 'pry-byebug' installed locally for this to be usable and work 100% correctly from within Pry, if any basis for my understanding of this hadn't since become outdated.  Additionally, there're still those other unresolved issues with using 'pry-byebug' from within the Homebrew codebase that I have yet to investigate fully.

Hey there,
We've got some thrilling news for you! GitHub is currently looking for skilled Developers to join our team. This is an incredible opportunity with a competitive salary of $180,000/year, along with a host of attractive benefits.
Interested in taking your career to the next level? Don't miss out! Click here to apply and secure your spot.
Looking forward to potentially welcoming you aboard!
Best regards, GitHub Recruitment Team duolaAOA, @ogty, @yunusd, @georgelemon, @hiw0rld, @maxweng, @Caly-Cai, @espoal, @isair, @ageldama, @saminfante, @wlfly, @januaryofmine, @, @sighttviewliu, @teiuaz, @dfmcvn, @utkarsh23, @bnsfan, @junli-cuny

DO NOT click on the link, it's a social engineering attack

     This issue now needs updating after developments upstream of upstream, namely as noted only one level upstream as part of Homebrew/brew#17010:  byebug has been unmaintained for quite a while now.

     This issue now needs updating after developments upstream of upstream, namely as noted only one level upstream as part of Homebrew#17010: byebug has been unmaintained for quite a while now.

     I've now made some minor updates to this issue's OP to address this.  Further updates may be appropriate, however.

     A potential further improvement and very likely a to-do item:

Follow the lead of PRs like sharesight/flappi#64 and rebase this issue, replacing (proposed further) usage of Pry, pry-byebug, and Byebug with usage of the official Ruby 'debug' gem.


How do I change my hardware ID?

How do I change my hardware ID? Why do I use fingerprint browser to create a new account and all the hardware IDs are the same?
Looking forward to your answer，thks

use other device, or use gen.js (but this only for testing, use it with your own risk)


Can I apply CrossMatch to Transformer-based networks?

Hello author,
Thanks for the release of the code of your paper. I love your work.
Can I apply CrossMatch to Transformer-based networks?
If not, what's the reason?
I appreciate any help you can provide.

Sure, it's totally possible as transformer is a bidirectional model.


Custom Plots to support Metric vs Metric or Param vs Param or Metric vs Param

Currently the custom plots only support param vs metric. It would be great if the custom plots can support metric vs metric, param vs param, or even metric vs param.

@daveraghav could you please give a bit more context? how do you use extension, how critical is this feature for you? (It would be great to jump on a call for me to learn more about you scenarios and cases).

for some of the training algorithms I'm running, that do self-optimisation, for example, automatic feature selection, or instances where I could be running hyperparameter optimisation as part of the training script, the parameters like number of features, or specific algorithm parameters are often part of output of one of the stages. so they're not really the metrics itself but params. so in these cases I would like to plot those outs (metrics as per dvc, but params as per my training process), vs the actual accuracy metrics. In these cases I've had to pre-define the plots, as part of the pipeline. It would be handy to allow plotting as part of custom plots through the extension directly. I hope that makes sense. Please let me know if further context is needed. Happy to jump on a call.

Was there any update to this issue?

@daveraghav sorry for the radio-silence here. I'll check with the team if we have capacity to take this. I've DMed you on LI - let's jump on call and discuss the details - it can help a lot.


Some styles are not respected in eM Client

Describe the Bug
Seems some styles are not applied in eM Client, max width for instance seems to be ignored when there are multiple emails with the same subject.
This does appear to happen when using react-email, but not with email builders like sendgrid.
This could easily be construed as a bug with eM Client, and happy for it to be closed with that reason.
Mainly wondering if this has been come across before and if there is any advice.
Which package is affected (leave empty if unsure)
No response
Link to the code that reproduces this issue
https://github.com/resend/react-email/blob/canary/apps/demo/emails/notifications/vercel-invite-user.tsx
To Reproduce
Here is an example with one of the demo emails:

Can reproduce by sending a test email and opening in eM Client
Expected Behavior
The CSS is respected
What's your node version? (if relevant)
No response

Wonder if this is an incompatibility of Tailwind with the email client you mentioned. Do any of the other emails, that don't have Tailwind in them, have this issue as well?

Wonder if this is an incompatibility of Tailwind with the email client you mentioned. Do any of the other emails, that don't have Tailwind in them, have this issue as well?

I will try tomorrow refactoring out of tailwind to see if that solves the issue and report back.

It seems there are some nuances with how certain clients handle CSS and with some of them not offering tools for easy debugging it was hard to understand the problem in depth, we are still seeing some issues where heights and widths are not respected and children are able to override maximums of their parents.
However we have been able to resolve these by being more strict with ensuring that children are not overflowing parent containers.


Omnisharp not respecting IgnoredCodeIssues

Hello,
I have been trying to get rid of Code Issue messages in C# (like having to have an underscore before a variable declaration for Unity3D programming).
As you can see in the picture my Omnisharp server is working and it has loaded the json config file that should be ignoring this message, but the message still appears.

BUMP: I have also not been able to resolve this issue. I've tested the regex for the "Name should have prefix" on multiple occasions and it seems to match just fine.
I'm beginning to think that the IgnoredCodeIssues is parsed before it displays the warning and the text is actually different on the warning in the backend parser, and the text it displays here is the result of some other warning that isn't getting picked up by the ignored code issue.

This is an omnisharp-server issue. It looks like "SyntaxErrors" are not checking IgnoredCodeIssues  the way "CodeIssues" do, see nosami's comment
However, omnisharp-server no longer seems to be maintained. You could try either making the fix locally yourself, or switch to the "roslyn" server, which is very actively maintained.


Media keys don't work

Hope this isn't a stupid issue but:
I'm under the impression that media keys functionality are automatic with leanback, however I've been having issues with it in my own project and also with the Leanback project.
When running the Leanback project in an emulator and on real hardware, I've noticed that the play/pause buttons function but others don't (at least the fast forward and rewind buttons on both, i've also tried the stop button on real hardware and that also does nothing)
Is this wrong, or is support not included automatically and I'm missing some implementation step

The recommended way of handling the buttons is with MediaSession, which the Leanback example doesn't demonstrate. If you use MediaSession, you can have all the media buttons treated as callbacks (ideally, you also do the same with the transport control UI as well). Some common video players will do a lot of this for you though. For example, if you use ExoPlayer, you can use MediaSessionConnector (https://exoplayer.dev/doc/reference/com/google/android/exoplayer2/ext/mediasession/MediaSessionConnector.html) to call the applicable player methods. That is demonstrated in the ClassicKotlins project. If you want/need to more directly handle the media session, you can also do that (see the MusicPlaybackService in LeanbackShowcase).


Revert "update libsvm file to start with 1 index"

This reverts commit a894ab6898f5ed525ca7dec89a79ea1fa7f49f5a.
I went back to 0.70 and the libsvm parser in dmlc-core has always been 0-based.

Need to fix some indexing mode instead of doing a full  revert.


UI does not support versions of drafts

Situation: User edits a draft and creates a new version of the draft. The new version is successfully created and displayed. Url is something like this:
https://marketplace.sshopencloud.eu/workflow/Cy8Vyg/version/{NewVersionId}
Issue: In the UI, links to this version of the draft are not updated. If the user closes the page and returns to the MP later, all links will point to the initial draft and there is no way for the user to find the latest version.
This is a serious issue for any workshop, where we usually encourage participants to work with drafts.

which links are we talking about?

I've tried to reproduce on stage, with a contributor role.
I've created a new tool, and saved it as draft.
When I then go to "my draft item" I can access the draft and edit it again, the URL was in my case: /tool-or-service/Lh6gZh/version/64302?draft=true
Then, I made new edits and clicked again on save as draft.
I went again in "my draft items" and accessed again the item. This indeed triggers the SAME URL: /tool-or-service/Lh6gZh/version/64302/edit?draft=true - but I can SEE my latest changes.
Then, assuming the contributor submit the item, and a moderator approves it. The item will disappear form the "my draft items" and be visible in the "my contributed items" section.
New edits on this item now approved will create a new version of the items (i.e. Lh6gZh/version/64304/edit?draft=true
So links do not update indeed, but changes in the drafts are incremented. Drafts are not versioned, and I vaguely remember we discussed why a long time ago. Exceptions/bugs could be coming from people working in multiple tabs maybe. This would require further testing to identify where changes in drafts are not well recorded/stored/saved.

Drafts are not versioned

yes, intentionally.

is there an actual issue where draft data is not saved properly / cannot be retrieved again?

seems to behave as expected, not able to reproduce the issue?
potential case (suspicion):

create a new item submit a draft => goes to moderation queue, removed from draft queue
because draft disappeared in the list, use may think, it got lost and try to create anew.


Photo selector widget flashes with ZoomPageTransitionsBuilder

Description

Use the ZoomPageTransitionsBuilder as default transition theme for android.

pageTransitionsTheme: PageTransitionsTheme(
  builders: <TargetPlatform, PageTransitionsBuilder>{
    TargetPlatform.android: ZoomPageTransitionsBuilder(),
  },
)

Pick photos and tap on a single photo widget to preview.
The widget flashes.

Plugin version
0.4.8
Flutter version
1.12.13+hotfix.7

Resolved with Flutter 1.20.


[enhancement] [WIP] Replace Null by Optional

Java offers us a really good thing called Optionals, which allow us to avoid NullPointerExceptions. This pull request will offer all changes to make it works fine.
To Note: This pull request still work in progress. Any feedback is welcome, but this pull request is not yet ready to be merge

Like I said when creating this pull request, it still in developement, so there is nothing sure about this changes. Of course the getArray should return something non-null, so needn't optional for that, I will fix that :)


If anyone need jieba as web api

簡單的包成了一個 web api，有需要可以參考一下
https://github.com/eit/nodejieba-webservice

Why not host somewhere?


Updated InstallerUrl: to full path Malwarebytes.Malwarebytes version <IP_ADDRESS>

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Fixed Install winget install error added full path
https://data-cdn.mbamupdates.com/web/mb4-setup-consumer/MBSetup.exe

This damn GitHub API issue...
@denelon can this issue get fixed ASAP? It only happens to Publisher.PackageName.installer.yaml, or is there a reason for that?

 It only happens to Publisher.PackageName.installer.yaml, or is there a reason for that?

Would it make more logic to have it as Malwarebytes.Malwarebytes-Free ?

 It only happens to Publisher.PackageName.installer.yaml, or is there a reason for that?

Would it make more logic to have it as Malwarebytes.Malwarebytes-Free ?

is there a different download link for premium?.. Free, Beta, Alpha etc in PackageIdentifier is only needed for programs with different branches

This damn GitHub API issue...
@denelon can this issue get fixed ASAP? It only happens to Publisher.PackageName.installer.yaml, or is there a reason for that?

Would it make more logic to have it as Malwarebytes.Malwarebytes-Free ?

is there a different download link for premium?.. Free, Beta, Alpha etc in PackageIdentifier is only needed for programs with different branches

Its the same link. So guess keep it the same.

@OfficialEsco which issue were you referring to?

@OfficialEsco which issue were you referring to?

2 files renamed, 1 file created and 1 file deleted when it should actually be 3 files renamed.
https://github.com/microsoft/winget-pkgs/pull/16268/files
Managed to do it for the locale file on this PR


GoRoute's builder is called multiple times

Steps to reproduce
Run the code sample.
Used
go_router: ^14.2.3
Expected results
When we push to the same router again and again, the builder of that router has to be called once every time.
Actual results
When we push to the same router again and again, the builder of that router is called as many times as we push to that route.
If we send to the same router 5th time. The builder will be called like this with 4 previous ones.
DetailsPage 5
DetailsPage 1
DetailsPage 2
DetailsPage 3
DetailsPage 4
Actually in my case where a router brings different extra data each time and builds a DetailsPage. My DetailsPage is heavy with many Blocs and sometimes the router builds the DetailsPage with one of the previous data which is pretty bad. Currently it makes me to use pushReplacement but I lose the stack.
Code sample
Code sample
import 'package:flutter/material.dart';
import 'package:go_router/go_router.dart';

void main() => runApp(const MyApp());

final GoRouter _router = GoRouter(
  routes: <RouteBase>[
    GoRoute(
      path: '/',
      builder: (BuildContext context, GoRouterState state) {
        return const HomeScreen();
      },
    ),
    GoRoute(
      path: '/details',
      builder: (BuildContext context, GoRouterState state) {
        print('/details');
        return const DetailsScreen();
      },
    ),
  ],
);

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) => MaterialApp.router(routerConfig: _router);
}

class HomeScreen extends StatelessWidget {
  const HomeScreen({super.key});

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: const Text('Home Screen')),
      body: Center(
        child: ElevatedButton(
          onPressed: () => context.push('/details'),
          child: const Text('Go to the Details screen'),
        ),
      ),
    );
  }
}

class DetailsScreen extends StatelessWidget {
  const DetailsScreen({super.key});

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: const Text('Details Screen')),
      body: Center(
        child: ElevatedButton(
          onPressed: () => context.push('/details'),
          child: const Text('Go to the Details screen'),
        ),
      ),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
Restarted application in 4,082ms.
D/EGL_emulation( 4136): app_time_stats: avg=310428.56ms min=310428.56ms max=310428.56ms count=1
I/flutter ( 4136): /details
W/OnBackInvokedCallback( 4136): OnBackInvokedCallback is not enabled for the application.
W/OnBackInvokedCallback( 4136): Set 'android:enableOnBackInvokedCallback="true"' in the application manifest.
D/EGL_emulation( 4136): app_time_stats: avg=1651.42ms min=1651.42ms max=1651.42ms count=1
D/EGL_emulation( 4136): app_time_stats: avg=440.85ms min=10.62ms max=2504.05ms count=6
I/flutter ( 4136): /details
I/flutter ( 4136): /details
W/OnBackInvokedCallback( 4136): OnBackInvokedCallback is not enabled for the application.
W/OnBackInvokedCallback( 4136): Set 'android:enableOnBackInvokedCallback="true"' in the application manifest.
D/EGL_emulation( 4136): app_time_stats: avg=33.23ms min=1.98ms max=520.17ms count=30
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
W/OnBackInvokedCallback( 4136): OnBackInvokedCallback is not enabled for the application.
W/OnBackInvokedCallback( 4136): Set 'android:enableOnBackInvokedCallback="true"' in the application manifest.
D/EGL_emulation( 4136): app_time_stats: avg=38.07ms min=1.97ms max=604.24ms count=25
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
W/OnBackInvokedCallback( 4136): OnBackInvokedCallback is not enabled for the application.
W/OnBackInvokedCallback( 4136): Set 'android:enableOnBackInvokedCallback="true"' in the application manifest.
D/EGL_emulation( 4136): app_time_stats: avg=47.56ms min=1.63ms max=1103.05ms count=26
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
W/OnBackInvokedCallback( 4136): OnBackInvokedCallback is not enabled for the application.
W/OnBackInvokedCallback( 4136): Set 'android:enableOnBackInvokedCallback="true"' in the application manifest.
D/EGL_emulation( 4136): app_time_stats: avg=31.46ms min=2.16ms max=502.62ms count=30
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
W/OnBackInvokedCallback( 4136): OnBackInvokedCallback is not enabled for the application.
W/OnBackInvokedCallback( 4136): Set 'android:enableOnBackInvokedCallback="true"' in the application manifest.
D/EGL_emulation( 4136): app_time_stats: avg=72.78ms min=10.68ms max=1219.43ms count=22
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
W/OnBackInvokedCallback( 4136): OnBackInvokedCallback is not enabled for the application.
W/OnBackInvokedCallback( 4136): Set 'android:enableOnBackInvokedCallback="true"' in the application manifest.
D/EGL_emulation( 4136): app_time_stats: avg=65.08ms min=1.38ms max=1316.55ms count=26
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
W/OnBackInvokedCallback( 4136): OnBackInvokedCallback is not enabled for the application.
W/OnBackInvokedCallback( 4136): Set 'android:enableOnBackInvokedCallback="true"' in the application manifest.
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
W/OnBackInvokedCallback( 4136): OnBackInvokedCallback is not enabled for the application.
W/OnBackInvokedCallback( 4136): Set 'android:enableOnBackInvokedCallback="true"' in the application manifest.
D/EGL_emulation( 4136): app_time_stats: avg=27.67ms min=2.16ms max=388.27ms count=35
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
W/OnBackInvokedCallback( 4136): OnBackInvokedCallback is not enabled for the application.
W/OnBackInvokedCallback( 4136): Set 'android:enableOnBackInvokedCallback="true"' in the application manifest.
D/EGL_emulation( 4136): app_time_stats: avg=32.89ms min=1.70ms max=470.33ms count=34
I/flutter ( 4136): /details
I/flutter ( 4136): /details
I/flutter ( 4136): /details
W/OnBackInvokedCallback( 4136): OnBackInvokedCallback is not enabled for the application.
W/OnBackInvokedCallback( 4136): Set 'android:enableOnBackInvokedCallback="true"' in the application manifest.
I/flutter ( 4136): /details
I/flutter ( 4136): /details
W/OnBackInvokedCallback( 4136): OnBackInvokedCallback is not enabled for the application.
W/OnBackInvokedCallback( 4136): Set 'android:enableOnBackInvokedCallback="true"' in the application manifest.
D/EGL_emulation( 4136): app_time_stats: avg=28.81ms min=7.88ms max=419.58ms count=34
D/EGL_emulation( 4136): app_time_stats: avg=62.91ms min=13.19ms max=753.42ms count=16
I/flutter ( 4136): /details
W/OnBackInvokedCallback( 4136): OnBackInvokedCallback is not enabled for the application.
W/OnBackInvokedCallback( 4136): Set 'android:enableOnBackInvokedCallback="true"' in the application manifest.
D/EGL_emulation( 4136): app_time_stats: avg=73.80ms min=6.44ms max=1286.38ms count=22

Flutter Doctor output
flutter doctor -v
[✓] Flutter (Channel stable, 3.24.0, on macOS 13.2.1 22D68 darwin-x64, locale en-TJ)
    • Flutter version 3.24.0 on channel stable at /Users/vfiruz/fvm/versions/3.24.0
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 80c2e84975 (2 weeks ago), 2024-07-30 23:06:49 +0700
    • Engine revision b8800d88be
    • Dart version 3.5.0
    • DevTools version 2.37.2

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0-rc2)
    • Android SDK at /Users/vfiruz/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0-rc2
    • ANDROID_HOME = /Users/vfiruz/Library/Android/sdk
    • Java binary at: /Users/vfiruz/Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11609105)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    ! Flutter recommends a minimum Xcode version of 15.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.14.2

[✓] Android Studio (version 2024.1)
    • Android Studio at /Users/vfiruz/Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11609105)

[✓] VS Code (version 1.92.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.94.0

[✓] Connected device (1 available)
    • sdk gphone x86 64 (mobile) • emulator-5554 • android-x64 • Android 13 (API 33) (emulator)

[✓] Network resources
    • All expected network resources are available.

This issue requires urgent attention.

I think multiple call will not rebuild previous DetailsPage  in stack as you have set the DetailsPage  as const in builder.
I add some heavy calculation in the build method.

As you can see, only the latest route you pushed will call the build method.

I think this is duplicate as #152906

@vfiruz97
Please check this comment to see if it helps in your case or not.

@SuicaLondon According to your comment I got that my Pages which ain't const will be rebuild every pushing a new route.
Actually my real-code looks like this

And if I make the root widget const in the route builder, will it be cached in pop?

@vfiruz97 Did you get a chance to check this ?

Yes, I did a test.
I didn't know that sending a new route would rebuild the entire GoRoute. I don't know why we need that if the Flutter's Navigator doesn't do that. We could manage UI changes via StateManagers. Now to avoid rebuilding the widget, we need to return a constant widget in the GoRoute's builder.
Knowing this, I solved my problem.

Good to know. Closing as resolved.


Add my blog into showcase

The URL of my blog is: www.bradenericson.com
P.S. Love the theme :)

done! Remember open new issues to report problems of improvements :-)


chore: make sure the changelog modifications are with the proper git tag

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] The changes are appropriately documented (if applicable).
[x] The changes have sufficient test coverage (if applicable).
[x] The testsuite passes successfully on my local machine (if applicable).

Summarize your changes:
Fixed a long-standing release bug that annoyed me :smile:
Works around the lack of a feature in generate-changelog (manually specifying a version).

I've tested this without publishing, I'm fairly confident it works the way I want it to. Also I want to release a new version :smile:


Only play one video in PiP at once.

Summary
When initializing the PiP experience, make sure no other video is playing. If it is, exit that PiP experience first and pause the previously playing video before opening a new PiP window.

Fixes #106 #178

LGTM. PiP displays one video at a time, and if a second video start on PiP, the first one stops.


Compile misc3d in conda's virtual environment

All of my environments are installed in conda's virtual environment，And the source code is compiled to open3d with the python path specified as: /home/tsy/anaconda3/envs/ttt/bin/python, and after testing open3d is compiled successfully，How does misc3d compile into conda's virtual environment? Can't seem to specify a python path?
ERROR: could not find a package configuration file provided by "Eigen3"

Hey @kungkook , you should install pybind and eigen by your self in your system. eigen is python independent so you can install it from offical guide. pybind can be installed using pip or build it from source.

you should install pybind and eigen by your self in your system. eigen is python independent so you can install it from offical guide. pybind can be installed using pip or build it from source.

Thank u, But I failed to compile Misc3D.
i use "pip install "pybind11[global]"" to install pybind11-2.10.1 successful and sucess install eigen successful；
i use cmake.. -DCMAKE_INSTALL_PREFIX=/home/tsy/anaconda3/envs/ttt/lib/cmake/Misc3D
and make install -j
ERROR: undefined reference to "cudaGetERRORName" and so on

undefined reference to "cudaGetERRORName" and so on

I have successfully compiled and installed the Misc3D library, but the python interpreter in my conda virtual environment cannot find Misc3D

Hey @kungkook , when you configure the misc3d, you can see the cmake output message about the version and path of python interpreter. Make sure that is the same with the one you used in your conda environment.

I check the python path in cmake. txt is the path of my conda. Can I specify the python path during compilation? For example, when compiling open3d，cmake .. DPython3_ROOT=usr/bin/python3

I havn't try this before, but you can have a try. Also, don't forget to add the paths bash:


image_test: Add Oslogin ssh tests

image_test: move metadata_ssh code to linux_common
Mode code from metadata_ssh to linux_common that will be reused in
oslogin
Also modify the coding style to cammel case to be consistent with
linux_common
image_test: Add Oslogin ssh tests
Implement oslogin tests
Update README.md with instructions to setup the required service
accounts with the right roles
Integrate it in img_test.wf.json

/ok-to-test

/flake8

/retest

/retest

/flake8

/flake8

/flake8

@illfelder hi, could you please take another look in this last version? Thanks

@illfelder could you please take a look on this last version?
Thanks

/flake8

I removed almost all flake8 erros regarding image_test/ folder, the errors left there are due to import orders which cannot be fixed because we need to install the dependencies before including them. This problem is also present in image_build/ and image_import/ as well, one solution would be to move the installation of the dependencies to a bash script, what do you think?

/retest

Thanks Helen! No need to move the installation of the dependencies to a bash script - we should look into a way to ignore the linter warning in cases where the import ordering needs to break linter checks. It would be good to update the other directories to fix issues like line length, but that can be a separate PR. I'll review your current PR and get back to you (apologies in advanced if I am slower than usual to respond this week).

Querying metadata oslogin/authorized should work as long as OS Login is enabled on the VM (meaning that either enable-oslogin is set in instance level metadata or set in project level metadata where instance metadata is not set). The precise logic that determines whether oslogin/authorized works is what the accounts daemon uses for determining if OS Login is enabled.

Right, so if I understand correctly, I would need to poll metadata oslogin/authorized from the instance under test. I rather not put much code inside the "testee" instance, as it could be any custom distribution and it might not have curl for example nor the ways to install it.

Running inside an instance, you should be able to assume the guest environment is installed so you can execute python code, correct? If so, you should be able to use the same logic we use in the guest environment to retrieve data from the metadata server.
That said, if you would like to keep most of the logic outside of the testee instance, you can poll instance and project level metadata from the API.

I see, well, yes, I prefer to keep most of the logic outside of the testee instance if you don't mind.
Would you mind if I add the polling of oslogin/authorized metadata in another PR? It seems it is working fine the way it is implemented (polling the ssh connection) with the exception of ubuntu-1604 (that I still need to investigate). If the user is authorized then the ssh should succeed, in my pov polling the metadata is basically an optimization (and also a test of the metadata server), please let me know it is not the case.

I'm happy with considering polling a secondary change as long as it isn't required to make the test functional. That said, it's concerning that Ubuntu 1604 is not currently passing given that we don't see issues in our internal image testing. I think we should figure out the test failure before merging in the test to ensure we aren't considering images unsupported when they are working properly in practice.

Tests for Ubuntu 16 are now working (solved by disabling sshguard. please let me know if you think this is not appropriated).
Suse 11 is failing, but it seems to be something else: https://github.com/GoogleCloudPlatform/compute-image-packages/issues/581
Another question related to the development workflow: To apply fixes in a PR I was using git commit --amend, but then I realized that all the commits in a PR get squashed when merged in the master branch. So instead of modifying previous commits with --amend I am just adding more commits with the fixes. Please let me know if this is not appropriated.

Awesome job tracking down the Ubuntu 1604 issue. I have no concerns with your fix for testing. I commented in the issue you filed that you don't need to worry about SLES 11.
Regarding development, no need to amend commits.

Looking at the presubmit flake8 output, it looks like there are some new linter errors though - please make sure to fix them before we merge this in.

@illfelder Thanks for the review and comments
I applied the changes that you mentioned.
Regarding flake8, the warnings there are only regarding the imports in the wrong order/place, but these are required as I need to install the dependencies before some imports.

Yeah, we can ignore those flake8 failures for the moment. LGTM merging.

Zach merged prematurely. I left some review comments - please address them in a follow-up (no rush on it though).


Terminal is blank after restoring window

Issue Type: Bug
After minimizing the VS Code window, then at some point restoring it, the terminal panel will be blank - I cannot enter any commands nor see any output. I have to kill the window (click the Trash icon), and reopen a new terminal. Unfortunately I cannot reproduce it on demand, but it has happened frequently, recently.
VS Code version: Code - Insiders 1.35.0-insider<PHONE_NUMBER>a94b116f468345f6e98688a737015d, 2019-05-31T21:28:16.350Z)
OS version: Darwin x64 18.6.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12 x 2600)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledrasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
1, 1, 1

Memory (System)
32.00GB (0.12GB free)

Process Argv
-psn_0_3396413

Screen Reader
no

VM
25%

Extensions (19)

Extension
Author (truncated)
Version

ng-template
Ang
0.800.0

path-intellisense
chr
1.4.2

vscode-svgviewer
css
2.0.0

vscode-eslint
dba
1.9.0

githistory
don
0.4.6

auto-close-tag
for
0.5.6

auto-rename-tag
for
0.1.0

output-colorizer
IBM
0.1.2

Angular2
joh
7.1.6

azure-account
ms-
0.8.4

csharp
ms-
1.19.1

vscode-typescript-tslint-plugin
ms-
1.1.0

debugger-for-chrome
msj
4.11.3

vetur
oct
0.21.0

material-icon-theme
PKi
3.8.0

quicktype
qui
12.0.46

vue-vscode-snippets
sdr
1.6.0

open-in-browser
tec
2.0.0

vscodeintellicode
Vis
1.1.6

(3 theme extensions excluded)

Different issue, not Windows.

The next time it happens could you check the devtools console for any errors and post it here? That will likely point to what the problem is.

It did just happen again - unfortunately I forgot to check the console, and I didn't at first notice the terminal window was blank. I did resize it and the text did come back. I will keep an eye out.

Just happened again, after restoring the window. This is all that was in the dev console:
/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:238 [Extension Host] Trace: BAD uri lacks scheme, falling back to file-scheme.
	at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:120:484
	at new f (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:120:557)
	at new m (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:122:853)
	at Function.parse (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:122:157)
	at nullConverter (/Users/johntsombakos/.vscode-insiders/extensions/octref.vetur-0.21.0/node_modules/vscode-languageclient/lib/protocolConverter.js:22:47)
	at asLocation (/Users/johntsombakos/.vscode-insiders/extensions/octref.vetur-0.21.0/node_modules/vscode-languageclient/lib/protocolConverter.js:313:34)
	at locations.map (/Users/johntsombakos/.vscode-insiders/extensions/octref.vetur-0.21.0/node_modules/vscode-languageclient/lib/protocolConverter.js:356:52)
	at Array.map (<anonymous>)
	at asLocationResult (/Users/johntsombakos/.vscode-insiders/extensions/octref.vetur-0.21.0/node_modules/vscode-languageclient/lib/protocolConverter.js:356:34)
	at asDefinitionResult (/Users/johntsombakos/.vscode-insiders/extensions/octref.vetur-0.21.0/node_modules/vscode-languageclient/lib/protocolConverter.js:325:16) (at Console.trace (console.js:253:8))
t.log @ /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:238

I suspect this shares the same root cause as https://github.com/Microsoft/vscode/issues/69665

FWIW - I checked and I did have that setting enabled - terminal.integrated.experimentalRefreshOnResume
while I  was seeing that issue.

@jtsom that setting will only do something after the OS resumes though, not when restoring the window from being minimized.


BK7231 I2C driver

Hi.
Is there any way an implamentation of the "I2C" led driver KP18058 or KP18068 could be implemented?
A range of very affordable Bulbs is available with BK7231n using the 18058/18068 is now available. Everything works up to a point of ESPHome having no support for the driver. OpenBeken has the support, but ESPhome is the platform of  choice for many of us and except for the led driver support, it has all else inplace already.
p.kacmarek and his team made a huge progress and all the workd id bssically done:
https://www.elektroda.com/rtvforum/viewtopic.php?p=20708687#20708687
I am saying "I2C" as it's function is fully described here:
https://www.elektroda.com/rtvforum/topic3991620.html
I am more than happy to help in making this happen, unfortunately not throught my knowledge (limited) but I am happy to preovide a bulb for testing, buy coffee... :)
Many thanks

That's not really up to me - you'd have to ask ESPHome developers for this driver support. I don't own any bulbs with such a driver, so I'm not really able to write a component for it.
That being said, it's true that I2C is not yet supported in LibreTiny. There are, however, components that use software based I2C in ESPHome itself, such as BP5758 driver (if I got the symbol right).

Thanks for your reply. I will do as you suggest. Thanks for your time and your great work!

is there any eta, when i2c will be available?

Probably soon. I'm waiting for new Beken boards to arrive, then I'll be able to work on I2C for BK7231. I've already implemented I2C and SPI for RTL8710, so it should be pretty straightforward.

Would be awesome.
i own a Klarstein Wonderwall, and it communicates over i2c with the other controller.

What other controller is that? Are you sure it uses I2C?
TuyaMCU controllers always use UART. If that's a PWM controller which uses I2C, there's a high chance that ESPHome has a component for it which uses software I2C.

It uses the https://github.com/buzzer13/esphome-components TM1650 controller.
Extended Information about the device:
https://www.elektroda.com/rtvforum/topic3952083.html
Would be awesome to got it in esphome.

FWIW ...The problem with KP18058/18068 is that is a sort of a hack I2C. It's documented (now) but acan't be used with existing controllers supported by ESPHome. In their Discord channel one person mentioned thay looked into this a while ago a did quite a lot of work on a similar controller... so I'm hoping htis will become more popolar controller that will eventually get support...

am adding a lot of homemate 4 gang switches to my house. These have the  7231N controller with 5 free GPIO pins, so will be very cool to be able to use existing i2s sensors with controller

I would love to help / contribute to writing the i2c driver, but will need guidance to get started.

Just following to have a notification for when this will be implemented. Hope to see it soon. I would like to help, but i have a very poor knowledge on the argument.
Thanks in advance


django-contrib-comments' COMMENT_MAX_LENGTH setting does not work.

I tried editing this line:
COMMENT_MAX_LENGTH = getattr(settings, 'COMMENT_MAX_LENGTH', 3000)
to this:
COMMENT_MAX_LENGTH = getattr(settings, 'COMMENT_MAX_LENGTH', 6000)
and changed the max_length of user_name to 100 but both fields remain with the same maximum size.
I tried migrating after the changes but no changes were detected.
What is the right approach to increase the maximum length of these fields ?

Please direct questions to the mailing list.

I haven't tried to reproduce this, but it could be a bug if mezzanine is somehow preventing the django-contrib-comments setting from working.

@logileifs Why are you setting COMMENT_MAX_LENGTH = getattr(settings, 'COMMENT_MAX_LENGTH', 6000) rather than COMMENT_MAX_LENGTH = 6000? Shouldn't you be setting it in your settings.py?

I added COMMENT_MAX_LENGTH = 6000 to settings.py and ran makemigrations which generated a new migration for the comments app.
As Ryne suggested, it looks like you're simply re-assigning whatever the existing value is, which would have no effect.


fix access restrictions for /_mxbuild/ and /_mxadmin/

These locations are protected by basic auth only.
Not yet tested.

LGTM!

Peer-tested with Maarten, merging now.


hadoop-lakefs test app read parquet fails on databricks

Using test/lakefsfs under Databricks Spark v3 the application reaches the point where it reads the
data from lakeFS and fails with the following exception:
stderr
log4j-active

tested following on databricks spark 3 here are results
Ok so ran a bit of testing here:
parquet partitioned write faii
parquet partitioned read fail
delta partitioned write fail
delta partitioned read  pass  (confused about this one ) when all the rest pass (I guess delta points directly at the files to read)


[Question] Support for Anomaly Detection Training

Liking the new updates to Model Builder.  Good job team 👍
If I may ask, I noticed there is a link to samples for anomaly detection.  Do you have firm plans when we will see more support for related training and code generation for anomaly detection?  Thanks in advance.

Thanks for the support, and the suggestion!
@briacht Do we have an issue tracking anomaly detection?

I don't believe we do, but it is on the roadmap! I believe we will implement forecasting first and then anomaly detection.


use non_reentrant_checkpoint fix requires_grad of input must be true for activation checkpoint layer in pipeline train.

from original PR
https://github.com/microsoft/DeepSpeed/pull/4128 rebase on feature proposed in
https://github.com/microsoft/DeepSpeed/pull/4118.  should be reviewed after https://github.com/microsoft/DeepSpeed/pull/4118 merged.

set config ['pipeline']['use_reentrant']=False to open it, it won't affect the original stable workload.
add cifar10 train ut and passed, it seems that there is no megatron-deepspeed pipeline train ut for reference. I have verified it locally（model parameters update process is consistent), and can still reduce a small memory on rank0（stage0, also the most memory occupied rank) on some 3D configurations.
@tohtana @tjruwase @hughpu

@inkcherry Thank you for submitting this as a new PR! Sorry for the delay of my review.
The change looks much simpler now, but the new tests failed. Can you check it?

Hi @inkcherry,
I could reproduced the same error (AssertionError on line 109). How did you run the test? I ran the following:
pytest test_pipe.py::TestPipeCifar10::test_pipe_use_reentrant[topo_config0]

Hi @inkcherry,
I could reproduced the same error (AssertionError on line 109). How did you run the test? I ran the following:
pytest test_pipe.py::TestPipeCifar10::test_pipe_use_reentrant[topo_config0]

Hi, @tohtana, very Thanks for helping me find the reason~ seems my testing environment version is a bit higher than ci.
It can be reproduced through the following two dockers+install deepspeed
pytorch/pytorch:2.0.1-cuda11.7-cudnn8-devel
(same version to ci, always failed)
nvcr.io/nvidia/pytorch:23.07-py3
(higher version than ci, always passed)
I have reduced the check level from params equal to loss convergence and can be passed currently. params equal check could be reused when the version is updated.


Helm operator leader election lost

Bug Report

What did you do?

Our operator is based on the helm-operator v1.11.0. When the manager is running, we get constant CrashLoop with the message leader election lost.
Here are the logs produced by all the reboots:
{"level":"info","ts":1630651003.0890665,"logger":"cmd","msg":"Version","Go Version":"go1.16.7","GOOS":"linux","GOARCH":"amd64","helm-operator":"v1.11.0","commit":"28dcd12a776d8a8ff597e1d8527b08792e7312fd"}
{"level":"info","ts":1630651003.09068,"logger":"cmd","msg":"Watch namespaces not configured by environment variable WATCH_NAMESPACE or file. Watching all namespaces.","Namespace":""}
I0903 06:36:44.244793       1 request.go:668] Waited for 1.039457424s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/elasticsearch.k8s.elastic.co/v1beta1?timeout=32s
{"level":"info","ts":1630651006.893125,"logger":"controller-runtime.metrics","msg":"metrics server is starting to listen","addr":"<IP_ADDRESS>:8080"}
{"level":"info","ts":1630651006.8952067,"logger":"helm.controller","msg":"Watching resource","apiVersion":"apps.cps.deepsearch.ibm.com/v1alpha1","kind":"KgAmqp","namespace":"","reconcilePeriod":"1m0s"}
{"level":"info","ts":1630651006.8960173,"logger":"controller-runtime.manager","msg":"starting metrics server","path":"/metrics"}
I0903 06:36:46.896255       1 leaderelection.go:243] attempting to acquire leader lease openshift-operators/ibm-cps-operator...
I0903 06:37:05.245608       1 leaderelection.go:253] successfully acquired lease openshift-operators/ibm-cps-operator
{"level":"info","ts":1630651025.2462952,"logger":"controller-runtime.manager.controller.kgamqp-controller","msg":"Starting EventSource","source":"kind source: apps.cps.deepsearch.ibm.com/v1alpha1, Kind=KgAmqp"}
{"level":"info","ts":1630651025.2464244,"logger":"controller-runtime.manager.controller.kgamqp-controller","msg":"Starting Controller"}
{"level":"info","ts":1630651025.7481437,"logger":"controller-runtime.manager.controller.kgamqp-controller","msg":"Starting workers","worker count":16}
I0903 06:37:08.088098       1 request.go:668] Waited for 1.030828222s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/operators.coreos.com/v1alpha1?timeout=32s
I0903 06:37:19.237634       1 request.go:668] Waited for 1.048805637s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/tuned.openshift.io/v1?timeout=32s
I0903 06:37:31.488584       1 request.go:668] Waited for 1.093715185s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/certificates.k8s.io/v1beta1?timeout=32s
E0903 06:37:41.490874       1 leaderelection.go:361] Failed to update lock: Put "https://<IP_ADDRESS>:443/api/v1/namespaces/openshift-operators/configmaps/ibm-cps-operator": context deadline exceeded
I0903 06:37:41.491073       1 leaderelection.go:278] failed to renew lease openshift-operators/ibm-cps-operator: timed out waiting for the condition
{"level":"error","ts":1630651061.4911356,"logger":"cmd","msg":"Manager exited non-zero.","Namespace":"","error":"leader election lost","stacktrace":"github.com/operator-framework/operator-sdk/internal/cmd/helm-operator/run.NewCmd.func1\n\t/workspace/internal/cmd/helm-operator/run/cmd.go:74\ngithub.com/spf13/cobra.(*Command).execute\n\t/go/pkg/mod/github.com/spf13/cobra@v1.1.3/command.go:856\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\t/go/pkg/mod/github.com/spf13/cobra@v1.1.3/command.go:960\ngithub.com/spf13/cobra.(*Command).Execute\n\t/go/pkg/mod/github.com/spf13/cobra@v1.1.3/command.go:897\nmain.main\n\t/workspace/cmd/helm-operator/main.go:40\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:225"}

Environment
Operator type:

/language helm
Kubernetes cluster type:

OpenShift 4.7.
$ operator-sdk version
operator-sdk version: "v1.11.0", commit: "28dcd12a776d8a8ff597e1d8527b08792e7312fd", kubernetes version: "1.20.2", go version: "go1.16.7", GOOS: "darwin", GOARCH: "amd64"

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.3", GitCommit:"ca643a4d1f7bfe34773c74f79527be4afd95bf39", GitTreeState:"clean", BuildDate:"2021-07-15T21:04:39Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.0+558d959", GitCommit:"558d959332b3f1f7bf786673bf294e6e0932bb18", GitTreeState:"clean", BuildDate:"2021-07-13T20:45:42Z", GoVersion:"go1.15.14", Compiler:"gc", Platform:"linux/amd64"}

It might be a side discussion, but from the logs it looks like the helm-operator is fetching APIs which should not be related to our Helm chart https://<IP_ADDRESS>:443/apis/elasticsearch.k8s.elastic.co/v1beta1, etc which are creating some client-side throttling.
Could this be related?

If your operator is hitting some API that you've never heard of, that's a pretty good indicator that you've generated your operator incorrectly.  It looks like you might be getting rate limited due to hammering the API, and that's causing the leader elections to time out. What helm chart are you using and what commands did you run to generate your operator?

The operator was created using the tutorial on the operator-sdk page:
operator-sdk init --domain cps.deepsearch.ibm.com --plugins helm
operator-sdk create api --group apps --version v1alpha1 --kind KgAmqp

Is "KgAmqp" a pre-existing Helm chart or are you just making a void Helm chart like the example? I can't get the void operator example to fail like this.
I suspect that you are getting rate-limited, but it looks like it's happening client side (on the controller) rather than by the API server. This can be configured via flags thrown on the controller-manager - is there anything funky when you look at the startup command there? "--kube-api-qps" in particular, as it looks like that's what sets the client side rate limited for the controller-manager.

Our current intuition is that the error is visible only on a large OCP 4.6 cluster (+60 nodes, +2500 Pods, etc).
As advised we tried out to introduce the selectors matching the label of some KgAmqp CR.
When the controller was not matching any CR, the logs were quite and the memory usage was very low.
After patching a few (not all) KgAmqp, we saw a huge increase in the memory usage, and the logs are showing 1) constant "Reconciled release", 2) "client-side throttling" from APIs which we would not expect to be queried (tekton.dev, knative, etc). Those APIs are for sure not matching our labels, and don't contain the CRD defined in the watches.yaml.
For reference, here is the watches.yaml
# Use the 'create api' subcommand to add watches to this file.
- group: apps.cps.deepsearch.ibm.com
  version: v1alpha1
  kind: KgAmqp
  chart: helm-charts/kgamqp
  watchDependentResources: false # adding this doesn't help
  selector: # adding this doesn't help, when
    matchLabels:
      app.kubernetes.io/name: kgamqp
      app.kubernetes.io/managed-by: ibm-cps-operator
#+kubebuilder:scaffold:watch

Regarding the previous questions.
The helm-chart was started with the vanilla example, and modified with a) a bit more values, b) remove hpa, c) add configmap and secrets.
The controller (reading from the running deployment) has the following args
args:
- --health-probe-bind-address=:8081
- --metrics-bind-address=<IP_ADDRESS>:8080
- --leader-elect
- --leader-election-id=ibm-cps-operator

@dolfim Thanks for raising the issue. With the current information we are also not able to figure out the reason behind this error. And as you have mentioned since the client-side throttling is happening only on large clusters, it would be difficult for us to reproduce. On brainstorming about this in our community meeting, we could think of a few pointers:

How many CRDs are installed in the cluster?
Could you try setting the --zap-log-level (ref) to increase the verbosity so that we could have more logs to debug.
If possible, it would be helpful if you could share the operator code. We can try reproducing it locally or at the least verify if there is something which could be improved or is wrong.

Thanks for looking at our issue and brainstorming about possibilities.

kubectl get crd shows 152 CRDs
We launched the controller with the following flags      args:
        - '--health-probe-bind-address=:8081'
        - '--metrics-bind-address=<IP_ADDRESS>:8080'
        - '--leader-elect'
        - '--leader-election-id=ibm-cps-operator'
        - '--zap-log-level=debug'

The debug logs now look like:
{"level":"info","ts":1632210241.791085,"logger":"cmd","msg":"Version","Go Version":"go1.16.8","GOOS":"linux","GOARCH":"amd64","helm-operator":"v1.11.0","commit":"28dcd12a776d8a8ff597e1d8527b08792e7312fd"}
{"level":"info","ts":1632210241.7931075,"logger":"cmd","msg":"Watch namespaces not configured by environment variable WATCH_NAMESPACE or file. Watching all namespaces.","Namespace":""}
I0921 07:44:03.538887       1 request.go:668] Waited for 1.046670127s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/storage.k8s.io/v1?timeout=32s
{"level":"info","ts":1632210245.8048182,"logger":"controller-runtime.metrics","msg":"metrics server is starting to listen","addr":"<IP_ADDRESS>:8080"}
{"level":"info","ts":1632210245.8914208,"logger":"helm.controller","msg":"Watching resource","apiVersion":"apps.cps.deepsearch.ibm.com/v1alpha1","kind":"KgAmqp","namespace":"","reconcilePeriod":"1m0s"}
I0921 07:44:05.892824       1 leaderelection.go:243] attempting to acquire leader lease openshift-operators/ibm-cps-operator...
{"level":"info","ts":1632210245.8931193,"logger":"controller-runtime.manager","msg":"starting metrics server","path":"/metrics"}
I0921 07:44:22.484699       1 leaderelection.go:253] successfully acquired lease openshift-operators/ibm-cps-operator
{"level":"debug","ts":1632210262.4847672,"logger":"controller-runtime.manager.events","msg":"Normal","object":{"kind":"ConfigMap","namespace":"openshift-operators","name":"ibm-cps-operator","uid":"4600a34a-c21e-4698-b83f-0bcbdfc4929c","apiVersion":"v1","resourceVersion":"610631877"},"reason":"LeaderElection","message":"ibm-cps-operator-controller-manager-557c88f7f6-mhlt2_be7ef8ca-2fb9-41b1-9d2d-c3d044ab3633 became leader"}
{"level":"info","ts":1632210262.4856992,"logger":"controller-runtime.manager.controller.kgamqp-controller","msg":"Starting EventSource","source":"kind source: apps.cps.deepsearch.ibm.com/v1alpha1, Kind=KgAmqp"}
{"level":"info","ts":1632210262.485977,"logger":"controller-runtime.manager.controller.kgamqp-controller","msg":"Starting Controller"}
{"level":"info","ts":1632210262.9877303,"logger":"controller-runtime.manager.controller.kgamqp-controller","msg":"Starting workers","worker count":16}
{"level":"debug","ts":1632210262.9914088,"logger":"helm.controller","msg":"Reconciling","namespace":"deepsearch-dev","name":"cps-edda45b6-kgamqp-90f46298","apiVersion":"apps.cps.deepsearch.ibm.com/v1alpha1","kind":"KgAmqp"}
{"level":"debug","ts":1632210262.9916945,"logger":"helm.controller","msg":"Reconciling","namespace":"foc-mvp-deepsearch","name":"cps-617ffb14-kgamqp-30b90812","apiVersion":"apps.cps.deepsearch.ibm.com/v1alpha1","kind":"KgAmqp"}
{"level":"debug","ts":1632210262.9957469,"logger":"helm.controller","msg":"Reconciling","namespace":"foc-mvp-deepsearch","name":"cps-f21574fe-kgamqp-5f323a8a","apiVersion":"apps.cps.deepsearch.ibm.com/v1alpha1","kind":"KgAmqp"}
{"level":"debug","ts":1632210262.998314,"logger":"helm.controller","msg":"Reconciling","namespace":"deepsearch-dev","name":"cps-bd768688-kgamqp-59041f3c","apiVersion":"apps.cps.deepsearch.ibm.com/v1alpha1","kind":"KgAmqp"}
{"level":"debug","ts":1632210263.091478,"logger":"helm.controller","msg":"Reconciling","namespace":"foc-mvp-deepsearch","name":"cps-6dc398bc-kgamqp-5e842217","apiVersion":"apps.cps.deepsearch.ibm.com/v1alpha1","kind":"KgAmqp"}
{"level":"debug","ts":1632210263.0931582,"logger":"helm.controller","msg":"Reconciling","namespace":"foc-mvp-deepsearch","name":"cps-617ffb14-kgamqp-0bbf559a","apiVersion":"apps.cps.deepsearch.ibm.com/v1alpha1","kind":"KgAmqp"}
{"level":"debug","ts":1632210263.093546,"logger":"helm.controller","msg":"Reconciling","namespace":"foc-mvp-deepsearch","name":"cps-617ffb14-kgamqp-fa7b5983","apiVersion":"apps.cps.deepsearch.ibm.com/v1alpha1","kind":"KgAmqp"}
{"level":"debug","ts":1632210263.0950687,"logger":"helm.controller","msg":"Reconciling","namespace":"foc-mvp-deepsearch","name":"cps-617ffb14-kgamqp-801751ea","apiVersion":"apps.cps.deepsearch.ibm.com/v1alpha1","kind":"KgAmqp"}
{"level":"debug","ts":1632210263.0951493,"logger":"helm.controller","msg":"Reconciling","namespace":"deepsearch-dev","name":"cps-bd768688-kgamqp-7f18f401","apiVersion":"apps.cps.deepsearch.ibm.com/v1alpha1","kind":"KgAmqp"}
{"level":"debug","ts":1632210263.0968616,"logger":"helm.controller","msg":"Reconciling","namespace":"deepsearch-dev","name":"cps-617ffb14-kgamqp-5b8ab839","apiVersion":"apps.cps.deepsearch.ibm.com/v1alpha1","kind":"KgAmqp"}
{"level":"debug","ts":1632210263.190764,"logger":"helm.controller","msg":"Reconciling","namespace":"deepsearch-dev","name":"cps-bd768688-kgamqp-17e384d1","apiVersion":"apps.cps.deepsearch.ibm.com/v1alpha1","kind":"KgAmqp"}
{"level":"debug","ts":1632210263.193185,"logger":"helm.controller","msg":"Reconciling","namespace":"foc-mvp-deepsearch","name":"cps-617ffb14-kgamqp-a4f4d947","apiVersion":"apps.cps.deepsearch.ibm.com/v1alpha1","kind":"KgAmqp"}
{"level":"debug","ts":1632210263.0953085,"logger":"helm.controller","msg":"Reconciling","namespace":"foc-mvp-deepsearch","name":"cps-617ffb14-kgamqp-1f739374","apiVersion":"apps.cps.deepsearch.ibm.com/v1alpha1","kind":"KgAmqp"}
{"level":"debug","ts":1632210263.4915593,"logger":"helm.controller","msg":"Reconciling","namespace":"deepsearch-dev","name":"cps-99cf5236-kgamqp-72952c4d","apiVersion":"apps.cps.deepsearch.ibm.com/v1alpha1","kind":"KgAmqp"}
{"level":"debug","ts":1632210263.491967,"logger":"helm.controller","msg":"Reconciling","namespace":"deepsearch-dev","name":"cps-bd768688-kgamqp-fa5a863e","apiVersion":"apps.cps.deepsearch.ibm.com/v1alpha1","kind":"KgAmqp"}
{"level":"debug","ts":1632210263.4956002,"logger":"helm.controller","msg":"Reconciling","namespace":"deepsearch-dev","name":"cps-26239ca0-kgamqp-503b8ba5","apiVersion":"apps.cps.deepsearch.ibm.com/v1alpha1","kind":"KgAmqp"}
I0921 07:44:25.491421       1 request.go:668] Waited for 1.078316488s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/node.k8s.io/v1beta1?timeout=32s
I0921 07:44:35.494616       1 request.go:668] Waited for 2.301755739s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/rbac.authorization.k8s.io/v1beta1?timeout=32s
I0921 07:44:50.992501       1 request.go:668] Waited for 1.000852157s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/scheduling.k8s.io/v1beta1?timeout=32s
E0921 07:44:53.894135       1 leaderelection.go:325] error retrieving resource lock openshift-operators/ibm-cps-operator: Get "https://<IP_ADDRESS>:443/api/v1/namespaces/openshift-operators/configmaps/ibm-cps-operator": context deadline exceeded
I0921 07:44:53.990918       1 leaderelection.go:278] failed to renew lease openshift-operators/ibm-cps-operator: timed out waiting for the condition
{"level":"error","ts":1632210293.9922085,"logger":"cmd","msg":"Manager exited non-zero.","Namespace":"","error":"leader election lost","stacktrace":"github.com/operator-framework/operator-sdk/internal/cmd/helm-operator/run.NewCmd.func1\n\t/workspace/internal/cmd/helm-operator/run/cmd.go:74\ngithub.com/spf13/cobra.(*Command).execute\n\t/go/pkg/mod/github.com/spf13/cobra@v1.1.3/command.go:856\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\t/go/pkg/mod/github.com/spf13/cobra@v1.1.3/command.go:960\ngithub.com/spf13/cobra.(*Command).Execute\n\t/go/pkg/mod/github.com/spf13/cobra@v1.1.3/command.go:897\nmain.main\n\t/workspace/cmd/helm-operator/main.go:40\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:225"}

It looks like it is getting the leader election once, and then it fails.
Since the timeout seems to be on the configmap, I tried count all of them:
# count configmaps
❯ kubectl get cm --all-namespaces -o name |wc -l
    1211

At the moment the controller doesn't survive more than 2min, so I cannot inspect the API calls done when raising the memory.

I don't think the debug zap-log-level introduced more verbose output. The only debug entries are Reconciling and Reconciled release.
As posted before, I see lots of API request which (at least to me) look weird for our controller.
https://<IP_ADDRESS>:443/apis/migration.k8s.io/v1alpha1?timeout=32s
https://<IP_ADDRESS>:443/apis/autoscaling/v2beta1?timeout=32s
https://<IP_ADDRESS>:443/apis/serving.knative.dev/v1alpha1?timeout=32s
https://<IP_ADDRESS>:443/apis/image.openshift.io/v1?timeout=32s
https://<IP_ADDRESS>:443/apis/elasticsearch.k8s.elastic.co/v1?timeout=32s
https://<IP_ADDRESS>:443/apis/snapshot.storage.k8s.io/v1?timeout=32s
https://<IP_ADDRESS>:443/apis/cloudcredential.openshift.io/v1?timeout=32s
https://<IP_ADDRESS>:443/apis/operators.coreos.com/v1?timeout=32s
https://<IP_ADDRESS>:443/apis/extensions/v1beta1?timeout=32s
https://<IP_ADDRESS>:443/apis/autoscaling/v2beta2?timeout=32s
https://<IP_ADDRESS>:443/apis/whereabouts.cni.cncf.io/v1alpha1?timeout=32s
https://<IP_ADDRESS>:443/apis/operators.coreos.com/v1alpha1?timeout=32s
https://<IP_ADDRESS>:443/apis/triggers.tekton.dev/v1alpha1?timeout=32s
https://<IP_ADDRESS>:443/apis/kibana.k8s.elastic.co/v1beta1?timeout=32s

I don't know the inner logic of the helm-controller but I don't really see a reason for it querying stuff like Tekton, Knative, etc.
But I can imagine that if the controller is caching the output of all tekton jobs, then this might explain the origin of the memory usage.
Does anybody understand why those APIs are called? Is this maybe a helm sdk issue?

When the helm controller comes up it dynamically queries the API to build a spec for talking to the cluster, so it might hit a bunch of APIs that look weird. Going to have to do some more digging.

So, trying to reproduce this on my rinky-dink minikube with 150+ CRDS deployed, my controller comes up fine with no hint of self-rate limiting. I suspect that maybe some Openshift specific stuff or configuration might be causing this.

Closing this as the user is no longer experiencing the problem and we're unable to reproduce it.


Remove pinterest and iframe from sharing button

For simplicity and to keep the focus on the majority
let's remove </> (does iframe even work with our XSS headers anyway?
Pinterest.
Probably make a tooltip with a black background and borders?

I will take it but I'm not sure what else to do except removing the </> icon.
And Is this what you want?


Add Nong song

Song Name
EDÉN-XO COVER ESPAÑOL
Artist Name
J O N A T Á N
Source
Youtube
Youtube Link
https://youtu.be/HLeVbWW0FTk?si=rDKc11-RUeNhK2tg
Direct File Link
No response
Song ID
766165
Extra
No response

this sadly doesn't sync to the level in game. there is intro for like 2 seconds


Fatal Error.

Hi Leon.
I just tried to install and enable the plugin using the current version you have here in GitHub.
It's giving me the following error:
Fatal error: Uncaught Error: Class 'WP2Static\Controller' not found in /home/CpanelUser/public_html/wp-content/plugins/wp2static-master/wp2static.php:24 Stack trace: #0 /home/CpanelUser/public_html/wp-admin/includes/plugin.php(2297): include() #1 /home/CpanelUser/public_html/wp-admin/plugins.php(191): plugin_sandbox_scrape('wp2static-maste...') #2 {main} thrown in /home/CpanelUser/public_html/wp-content/plugins/wp2static-master/wp2static.php on line 24
Just wanted to let you know, and in case you need any further info, let me know.
Greetings.
Chris.

Hi @cjcg1991, please run following command from within that directory composer install. I'll make the process easier for you in future

I am getting the same error

Hi @gilluminate - I'll prepare some ready to go installers and link to them from the homepage when ready. In the meantime, what errors did you encounter with composer install?

Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for phar-io/manifest 2.0.1 -> satisfiable by phar-io/manifest[2.0.1].
    - phar-io/manifest 2.0.1 requires ext-dom * -> the requested PHP extension dom is missing from your system.
  Problem 2
    - Installation request for phpunit/php-code-coverage 9.1.4 -> satisfiable by phpunit/php-code-coverage[9.1.4].
    - phpunit/php-code-coverage 9.1.4 requires ext-dom * -> the requested PHP extension dom is missing from your system.
  Problem 3
    - Installation request for phpunit/phpunit 9.3.7 -> satisfiable by phpunit/phpunit[9.3.7].
    - phpunit/phpunit 9.3.7 requires ext-dom * -> the requested PHP extension dom is missing from your system.
  Problem 4
    - Installation request for squizlabs/php_codesniffer 3.5.6 -> satisfiable by squizlabs/php_codesniffer[3.5.6].
    - squizlabs/php_codesniffer 3.5.6 requires ext-simplexml * -> the requested PHP extension simplexml is missing from your system.
  Problem 5
    - Installation request for theseer/tokenizer 1.2.0 -> satisfiable by theseer/tokenizer[1.2.0].
    - theseer/tokenizer 1.2.0 requires ext-dom * -> the requested PHP extension dom is missing from your system.
  Problem 6
    - phpunit/phpunit 9.3.7 requires ext-dom * -> the requested PHP extension dom is missing from your system.
    - 10up/wp_mock 0.4.2 requires phpunit/phpunit >=7.0 -> satisfiable by phpunit/phpunit[9.3.7].
    - Installation request for 10up/wp_mock 0.4.2 -> satisfiable by 10up/wp_mock[0.4.2].

Hi @gilluminate,
OK, that's useful and should be fairly quickly solvable. We'll need to install the DOM extension for PHP, which can vary for your specific system.
If you search for "install php-xml in {MY OPERATING SYSTEM}" it should give some ideas. If you're using another tool to setup WordPress on your system, there may be guides for that, but usually those will come with that extension enabled by default.

Issue initially reported here is fixed in code and available from next release (7.1.5)


packager in 0.5.0-rc1 fails to parse command line options like --root

This might be due to a missed commit to packager.js which adds a 'string' type to the packager commands as expected here:
https://github.com/facebook/react-native/commit/1b2975803b1b0ebad693342e51a5c9b533d7a15d

Closing this because you created a pull request, so we can track the issue there :+1:


Need To Avoid SSL Problems

In Chapter 10, net.sci.gsfc.nasa.gov api has a ssl problem.

Facing the same issue :(

To @loinsir .
Thanks a lot ! It works well.
At first it didn't work after I modifying the codes according to your solution. I checked the error message, it was not the same as before. So I doubt  it may be caused by some mysterious strength , and after I enabling the proxy, it works as expected 🥳
Anyway, thanks again!


Remove periods in label value

Fixes https://github.com/getsentry/raven-python/issues/594

Thanks for the PR and apologizes for closing the previous issue too fast.

Fantastic. Thank you!


Enable python 2.7

Depends on https://github.com/nitely/v8-cffi/pull/12

Coverage remained the same at 100.0% when pulling 5e09e142c34257dd6c74c0278570283953c4299b on heston:py27-fixes into 15191480b6b5660d97b95cca95be968a6c031c12 on nitely:master.

Coverage decreased (-3.0%) to 97.015% when pulling b26a5a2d61f8cbf078fcb79592f9a06aad359d6e on heston:py27-fixes into 15191480b6b5660d97b95cca95be968a6c031c12 on nitely:master.

Coverage decreased (-0.7%) to 99.254% when pulling 1a04f0068148969cf3f539e2d48a1c39b7ff49cf on heston:py27-fixes into 15191480b6b5660d97b95cca95be968a6c031c12 on nitely:master.

Coverage decreased (-3.0%) to 97.015% when pulling 4f4a46a923720a4b37d4367b7d26fa45fd01ffe0 on heston:py27-fixes into 15191480b6b5660d97b95cca95be968a6c031c12 on nitely:master.

Coverage decreased (-3.0%) to 97.015% when pulling ba5514de7977e59ae5a595ef1054981706c264c9 on heston:py27-fixes into 15191480b6b5660d97b95cca95be968a6c031c12 on nitely:master.

@nitely Any thoughts on this one?

Aparently py2 json.dumps returns a str, I think I would prefer to maintain the py3 behaviour of returning an unicode.
Importing from __future__ import unicode_literals everywhere and returning six.text_type(json.dumps(data)) from to_json(data) should do it.

returning six.text_type(json.dumps(data)) from to_json(data) should do it.

On a second thought, it would be better to decode the string this way:
data_ = json.dumps(data)

if isinstance(data_, binary_type):
    return data_.decode('utf-8')
else:
    return data_

This test failure is strange:
react.React.to_json('{"foo": "foo", "bar": 1}'))
    AssertionError: '{"foo": "foo", "bar": 1}' != u'"{\\"foo\\": \\"foo\\", \\"bar\\": 1}"'

It looks like you're expecting a string of json to be returned as-is. However, passing a string to `json.dumps

Ah, nm. Looks like I inadvertently removed the check for a string input type. Added it back.

Coverage decreased (-2.9%) to 97.122% when pulling 99c6ec0d47fbda1ee8e0626f0c0ad1a6a3dce7d4 on heston:py27-fixes into 15191480b6b5660d97b95cca95be968a6c031c12 on nitely:master.

Coverage decreased (-3.6%) to 96.403% when pulling ced91e5a7a269c8870b6708e65f8590bab81c2c0 on heston:py27-fixes into 15191480b6b5660d97b95cca95be968a6c031c12 on nitely:master.

@nitely I think I addressed everything. Looks like coveralls missed the 2.7 job, but coverage should still be 100%.

Great, LGTM then :+1: . I'll some more tests later and then releasing it.

@nitely Great, thank you!


Use HolidayBase::add_holiday* family methods [l-m]

Proposed change

This PR continues https://github.com/vacanza/python-holidays/pull/1368. Update countries starting w/ l-m.
Type of change

[ ] New country/market holidays support (thank you!)
[ ] Supported country/market holidays update (calendar discrepancy fix, localization)
[x] Existing code/documentation/test/process quality improvement (best practice, cleanup, refactoring, optimization)
[ ] Dependency update (version deprecation/upgrade)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (a code change causing existing functionality to break)
[ ] New feature (new python-holidays functionality in general)

Checklist

[x] I've followed the contributing guidelines
[x] This PR is filed against beta branch of the repository
[x] This PR doesn't contain any merge conflicts and has clean commit history
[x] The code style looks good: make pre-commit
[x] All tests pass locally: make test, make tox (we strongly encourage adding tests to your code)
[x] The related documentation has been added/updated (check off the box for free if no updates is required)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
9117

Relevant Lines:
9126

💛  - Coveralls


It doesn't seem this is bi-directional communication.  Only from iframe to parent window (or one window to another)

Would be much more useful if it was bidirectional.
My current project is going to have to do this manually like:
https://gist.github.com/pbojinov/8965299

oh but it is. See 'communicate with another window' example in https://github.com/pshihn/windtalk/wiki/Examples where each window sends a message to the other.
Each window can call windtalk.expose(object) and call windtalk.link(otherWindow)

Tried it with child iframe to parent... Didn't work. Add example if so
please?
On Wed, May 9, 2018 at 4:40 PM Preet<EMAIL_ADDRESS>wrote:

oh but it is. See 'communicate with another window' example in
https://github.com/pshihn/windtalk/wiki/Examples where each window sends
a message to the other.
Each window can call windtalk.expose(object) and call
windtalk.link(otherWindow)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pshihn/windtalk/issues/2#issuecomment-387907034, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACx4iy2UXB1mvm6abM_6Afo0UgO3Drf4ks5tw353gaJpZM4T5JZI
.

Here's a simple example: https://pshihn.github.io/windtalk/examples/window-bidirection.html
Code for the main window: https://github.com/pshihn/windtalk/blob/master/examples/window-bidirection.html
Code for the iframe: https://github.com/pshihn/windtalk/blob/master/examples/iframe-bidirection.html
The idea is quite simple. Whatever function or object you want the other window to use, call expose
windtalk.expose(function);

And to connect to the other window's exposed method or object, call link
const remoteFunction = windtalk.link(otherWindow)
remoteFunction();


Call to undefined method Josh\Faker\Generator::fulltname()

Hey,
of course the method fulltname is undefined cause it has typo!
you should call fullname method.

Thanks for the issue.
The readme file had typo for fullname method!
It fixed in (9db3dea43)


Add automatic TLS certificates from Let's Encrypt

This is a very crude start.

this is needed. as a new user TLS certs wasted hours of my time trying to figure out. I almost gave up hope.

I also hope this PR made well and merge into master. It'll be great to newcomers. :)

Closing because this is out of date.


Nuget package

Hello
Your library would be very useful for needs of our project. But I work with Xamarin Android and in nuget I can see the lib version 2.0 only. Is it possible to update the library on nuget to the latest version?
Thank you in advance!

I am only maintaining the Java version. Please contact the Xamarin maintainer.


Grommet

Played around a bit with grommet.
I am not sure if grommet is stable enough to use it in our project.
Maybe we can use grommet as inspiration and write our own framework.

Just two little things, if possible let's try to write tests for our examples and fill in the readme.  Also, the React-router link component will automatically add an active class if you set it up correctly.  Otherwise, we can use the location api to do something similar.
Nice work and thanks for submitting!!

Just two little things, if possible let's try to write tests for our examples and fill in the readme.  Also, the React-router link component will automatically add an active class if you set it up correctly.  Otherwise, we can use the location api to do something similar.
Nice work and thanks for submitting!!

Hey, sorry just one more thing, which you probably know already (figured I'd mention if not.)  You can use ES6 Destructuring for importing multiple components from Grommet.
i.e.
import {
  Header,
  Title,
  Menu,
  Anchor,
  Search,
} from 'grommet';

vs.
import Header from 'grommet/components/Header';
import Title from 'grommet/components/Title';
import Menu from 'grommet/components/Menu';
import Anchor from 'grommet/components/Anchor';
import Search from 'grommet/components/Search';


Update CHANGELOG file for v2.1.7 release

From pierre.raybaut on 2012-01-14T09:28:20Z
This is the last task to be done before releasing v2.1.7.
Not sure I can do this right now... if anyone has some time to update this file, it would certainly help.
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=909

From pierre.raybaut on 2012-01-14T06:44:36Z
This issue was closed by revision f3833ac1806b .
Status: Fixed