ruby 3 upgrade

maybe install ruby 3 with rbenv using cap?
https://github.com/capistrano-plugins/capistrano-rbenv-install
update on progress:

Got the app booting and the tests passing under ruby 3 (minimal effort)
Ember CLI Rails is now broken

Ember CLI Rails issue
Github issue: https://github.com/thoughtbot/ember-cli-rails/pull/591
where the issue originates: https://github.com/thoughtbot/ember-cli-rails/blob/main/lib/ember_cli/configuration.rb
stack trace:
solutions_sidekiq    | 2022-04-23T04:25:22.069Z pid=1 tid=731 WARN: ArgumentError: wrong number of arguments (given 2, expected 1)
solutions_sidekiq    | 2022-04-23T04:25:22.070Z pid=1 tid=731 WARN: /usr/local/bundle/gems/ruby/3.0.0/gems/ember-cli-rails-0.11.0/lib/ember_cli/app.rb:11:in `initialize'
solutions_sidekiq    | /usr/local/bundle/gems/ruby/3.0.0/gems/ember-cli-rails-0.11.0/lib/ember_cli/configuration.rb:11:in `new'
solutions_sidekiq    | /usr/local/bundle/gems/ruby/3.0.0/gems/ember-cli-rails-0.11.0/lib/ember_cli/configuration.rb:11:in `app'
solutions_sidekiq    | /var/app/config/initializers/ember.rb:2:in `block in <main>'
solutions_sidekiq    | /usr/local/bundle/gems/ruby/3.0.0/gems/ember-cli-rails-0.11.0/lib/ember_cli.rb:12:in `configure'
solutions_sidekiq    | /var/app/config/initializers/ember.rb:1:in `<main>'
solutions_sidekiq    | /usr/local/bundle/gems/ruby/3.0.0/gems/bootsnap-1.7.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:59:in `load'
solutions_sidekiq    | /usr/local/bundle/gems/ruby/3.0.0/gems/bootsnap-1.7.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:59:in `load'
solutions_sidekiq    | /usr/local/bundle/gems/ruby/3.0.0/gems/activesupport-6.1.5/lib/active_support/dependencies.rb:326:in `block in load'
solutions_sidekiq    | /usr/local/bundle/gems/ruby/3.0.0/gems/activesupport-6.1.5/lib/active_support/dependencies.rb:299:in `load_dependency'

ruby 3 is going to be deprecated in the next heroic stack
854
remote:        Your Ruby version is not present on the next stack
[855](https://github.com/restarone/violet_rails/actions/runs/11203888631/job/31141640289?pr=1659#step:5:856)
remote:
[856](https://github.com/restarone/violet_rails/actions/runs/11203888631/job/31141640289?pr=1659#step:5:857)
remote:        You are currently using ruby-3.0.0 on heroku-20 stack.
[857](https://github.com/restarone/violet_rails/actions/runs/11203888631/job/31141640289?pr=1659#step:5:858)
remote:        This version does not exist on heroku-22. In order to upgrade your stack you will
[858](https://github.com/restarone/violet_rails/actions/runs/11203888631/job/31141640289?pr=1659#step:5:859)
remote:        need to upgrade to a supported Ruby version.
[859](https://github.com/restarone/violet_rails/actions/runs/11203888631/job/31141640289?pr=1659#step:5:860)
remote:
[860](https://github.com/restarone/violet_rails/actions/runs/11203888631/job/31141640289?pr=1659#step:5:861)
remote:        For a list of supported Ruby versions see:
[861](https://github.com/restarone/violet_rails/actions/runs/11203888631/job/31141640289?pr=1659#step:5:862)
remote:        https://devcenter.heroku.com/articles/ruby-support#supported-runtimes
[862](https://github.com/restarone/violet_rails/actions/runs/11203888631/job/31141640289?pr=1659#step:5:863)
remote:
[863](https://github.com/restarone/violet_rails/actions/runs/11203888631/job/31141640289?pr=1659#step:5:864)
remote:        For a list of the oldest Ruby versions present on a given stack see:
[864](https://github.com/restarone/violet_rails/actions/runs/11203888631/job/31141640289?pr=1659#step:5:865)
remote:        https://devcenter.heroku.com/articles/ruby-support#oldest-available-runtimes
[865](https://github.com/restarone/violet_rails/actions/runs/11203888631/job/31141640289?pr=1659#step:5:866)
remote:
[866](https://github.com/restarone/violet_rails/actions/runs/11203888631/job/31141640289?pr=1659#step:5:867)
remote:
[867](https://github.com/restarone/violet_rails/actions/runs/11203888631/job/31141640289?pr=1659#step:5:868)
remote:        Using release configuration from last framework (Ruby).
[868](https://github.com/restarone/violet_rails/actions/runs/11203888631/job/31141640289?pr=1659#step:5:869)
remote:        -----> Discovering process types
[869](https://github.com/restarone/violet_rails/actions/runs/11203888631/job/31141640289?pr=1659#step:5:870)
remote:        Procfile declares types -> release, web, worker


Add @jwt_refresh_cookie decorator

ref #217 #230 #276

Codecov Report

Merging #287 (3bf0469) into main (704f24e) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #287   +/-   ##
=======================================
  Coverage   99.84%   99.84%
=======================================
  Files          47       47
  Lines        1321     1321
=======================================
  Hits         1319     1319
  Misses          2        2

Impacted Files
Coverage Δ

graphql_jwt/decorators.py
100.00% <ø> (ø)

graphql_jwt/settings.py
100.00% <ø> (ø)

graphql_jwt/mixins.py
100.00% <100.00%> (ø)

graphql_jwt/refresh_token/mixins.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Why i cant download new version?

Rocket is currently not available for download.  Whats this?

https://rocket.foundation/viewtopic.php?f=44&t=328&p=1030#p1030


App launches in Mint Cinnamon in taskbar but not working

Hello,
I am using Linux Mint 22 with Cinnamon 6.2.9 and Kernel 6.8.0-4. I installed the app from the Software Flatpak manager, which installs the latest Trayscale version 0.13.4 and when I launch the icon shows in the task bar but when I click on the Icon nothing appears but I can see the "Connect" option while it used to work on Mint 21.3.
I tried to lunch from terminal also and I get this:

lmuser@lmyg14:~$ flatpak run dev.deedles.Trayscale
2024/09/06 22:46:56 systray error: failed to request name: org.freedesktop.DBus.Error.ServiceUnknown
Does it require another service that is missing on Linux Mint 22?
Thanks!

That error is not a fatal one. Does anything else show up in the console?

Thx for having a look!
You mean the terminal?
Amy command that I can use you logs may be?

Similar issue on Debian Xfce

Do you have Tailscale installed and configured as explained in the Flathub description?

I have the same issue here. I did the steps for allowing Tailscale to communicate with Trayscale and it will show in the taskbar, and after like 20 seconds it will close itself

Any output if you run it in the command line?

I have recently run into what might be either this issue or a related one myself. Some notes as I'm too busy to take a look at it at the moment:
The app works fine when it first starts, but sometimes will refuse to open the window after that. I think that it's tied to tailscaled restarting while Trayscale is running. Closing the app from the icon seems to work at first, but the process doesn't actually exit, so the app name isn't relinquished and new instances can't start. Killing it manually will allow it to open again.


Blazor: <InputDate ... @bind-Value:format="dd-MM-yyyy"> doesn't format.

Describe the bug
With Blazor <InputDate ... @bind-Value:format="dd-MM-yyyy"> the date doesn't format.
With <input @bind="starship.ProductionDate" @bind:format="dd-MM-yyyy" /> it `does.
See "InputDate" > https://docs.microsoft.com/en-us/aspnet/core/blazor/forms-validation?view=aspnetcore-3.0
Screenshot

Additional context
.NET Core SDK (reflecting any global.json):
Version:   3.1.100-preview1-014459
Commit:    ac3b59712d
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.18362
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\3.1.100-preview1-014459\
Host (useful for support):
Version: 3.1.0-preview1.19506.1
Commit:  bbf5542781
.NET Core SDKs installed:
2.1.802 [C:\Program Files\dotnet\sdk]
2.2.402 [C:\Program Files\dotnet\sdk]
3.0.100 [C:\Program Files\dotnet\sdk]
3.1.100-preview1-014459 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.13 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.13 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.0-preview1.19508.20 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.13 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.0-preview1.19506.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.0-preview1.19506.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

@JeepNL thanks for contacting us.
@SteveSandersonMS can you take a look? I'm not sure how "@bind" works with components.

In the specific case of InputDate, it wouldn't make sense to offer a "format" option, because the whole idea of InputDate is to render an <input type=date>. This is a built-in HTML input type, and as per the HTML spec, the format must be yyyy-mm-dd internally, and the way it gets presented to users in the UI is controlled by the browser. Browsers will represent the data according to the browser's language settings.
This is different from a plain <input> as given in the original example, since that's just a freeform textbox and can contain data in any format.
@javiercn When binding to components, it's entirely up to the component to choose what additional options to provide for binding. For example, a component could expose an additional parameter like:
[Parameter] public string ValueFormat { get; set; }

... and then make use of it internally. It's not something that Blazor can add automatically, because the framework itself doesn't know how the component plans to implement the binding.

@SteveSandersonMS I know on first sight It looks like it doesn't make sense, and if you live in the US it probably doesn't, but for some people in the rest of the world it does. I've had this kind of conversation about phone-number formatting, postal codes and states 'a couple of times' 20-25 years ago.
The date format of  is controlled by the browser, and exactly that is the problem. I am Dutch, but I use en US/English W10 O/S. My preferred language for content in my Browser is US/English. Why? Because I don't want to see auto translated 'Dutch' pages on international web sites is one example.
And because I'm a developer, I want to be able how to format the date in such circumstances when I know my (internal business) application will only be used in The Netherlands.
So, for me, it does make sense. See?

I don't live in the US :) I'm British.
I'm afraid the feature you're asking for is just not something that Blazor controls. The date format within an <input type=date> is completely controlled by the browser. See https://stackoverflow.com/a/9519493 for info.
If using a non-browser-controlled format is an absolute requirement for you, then you'll need to not use <input type=date> or InputDate which wraps that. Instead, consider using or implementing an alternative date picker, for example via JS interop. I know that's not as convenient, but I'm afraid that is just the feature set that browsers offer.

Oops :) Sorry! (British)
So, the browser/HTML 5 input specification is the problem. Well, I didn't know that. The StackOverflow article cleared that up. That's actually a big disappointment. We're using internet browsers for more than 25 years now and this still isn't fixed. (ie: implemented)
I will look into your suggestions, thank you for your reply.


DCOS-14307: Fix Discard dialogue behavior

This PR addresses the issue when discarding changes would have just closed the form which cause a glitch with Universe install button.
The issue is addressed by resetting the flag hasChangesApplied every time we discard changes.
Checklist

[x] Did you add a JIRA issue in a commit message or as part of the branch name?
[ ] Did you add new unit tests?
[ ] Did you add new integration tests?
[ ] If this is a regression, did you write a test to catch this in the future?

Nice work! Works great. :ship:

Thanks Dima!


Add incompatibility to setBadgeBackgroundColor

We do not support CSS color names (i.e. red or blue). Updating docs to reflect this.

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


for protein-ligand complex w/ gromacs (lysozyme), update the npt.mdp file

Hello,
I had to change this line in npt.mdp so that gromacs run:
; Pressure coupling
;;pcoupl                  = Berendsen                     ; pressure coupling is on for NPT
pcoupl                  = C-rescale                     ; pressure coupling is on for NPT

The tutorials are designed for GROMACS 2018, which should allow use of Berendsen. It is indeed outdated as far as available pressure coupling algorithms go, so a future version will update this to C-rescale.


New script decorator

Pull Request Checklist

[x] Fixes #1042
[x] Tests added
[x] Documentation/examples added
[x] Good commit messages and/or PR title

Description of PR

Rearranged examples folder so it's easier to navigate
Added basic script example from HEP0001, with a second script template to demonstrate setting the entrypoint using the alternative template name

@elliotgunton can we rearrange the examples in a separate PR?

@elliotgunton re:set entrypoint erroring out, I think we should make it idempotent instead. ie if the same entrypoint is set, let it be (this might happen if the module is imported multiple times which is quite common). In case of a different entrypoint, maybe a warning rather than an error would be better and have the last one be the default one.


One more formula reference issue - cut and paste

If you cut a cell which contains a parameter for a function, and paste it into another cell, the formula reference does not update.
For example:
put: 1 in cell A1
put: 2 in cell A2
put =sum(A1,A2) in cell A3
If you cut cell A1 and paste it to B1, the expected result would be for the formula to update to: =sum(B1,A2)

Even in Excel, cutting A1 and pasting it to B1 does not update the function to SUM(B1,A2). Closing this.

Very sorry…I used an incorrect example. I will reopen with the correct information.
Alex
From: Sanchit Agarwal @.>
Sent: Sunday, March 17, 2024 1:33 PM
To: ruilisi/fortune-sheet @.>
Cc: visualbasik @.>; Author @.>
Subject: Re: [ruilisi/fortune-sheet] One more formula reference issue - cut and paste (Issue #377)
Even in Excel, cutting A1 and pasting it to B1 does not update the function to SUM(B1,A2). Closing this.
—
Reply to this email directly, view it on GitHub https://github.com/ruilisi/fortune-sheet/issues/377#issuecomment-2002548334 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ARG7XBPWZOACZDC5I33URNTYYXHUTAVCNFSM6AAAAAAYKO6AKGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBSGU2DQMZTGQ .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/ARG7XBN4Z63AWCGXVWLLG73YYXHUTA5CNFSM6AAAAAAYKO6AKGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTXLR3G4.gif Message ID: @.***>


Rename swish to silu to give appropriate credit

Hi,
The swish was originally coined the "SiLU" in https://arxiv.org/pdf/1606.08415.pdf (2016) and re-introduced in https://arxiv.org/abs/1702.03118 (early 2017) long before the swish paper. Renaming other peoples' exact same ideas is unacceptable, as we all know. A recent discussion and a recent pytorch and jax and tensorflow issue  show that we should call this the SiLU. In light of recent efforts to make the ML community more equitable and fair, this is a no-brainer. (Since this repo uses pytorch, I'll note that a future version of pytorch will add the silu activation.)

@TFUsers I saw the discussion in the swish (silu) PR in pytorch repo. I'll likely switch once the PyTorch version makes it nearer release and I refactor the activations here.

This is in progress, I now use the official PyTorch SiLU when I can (still supporting some older PyTorch versions), and string activations can use 'silu' but bwds compat with 'swish'. Will eventually pull out the extra swish code when enough PyTorch versions have passed


Unable to send invoke tx

neolineN3.invoke({
                    scriptHash: "0xd2a4cff31913016155e38e474a2c06d08be276cf",
                    operation: "transfer",
                    args: [
                        {
                            type: "Address",
                            value: "NUqsqGmgTCf5t9pVf9Tz3E3riUsu91tgWj"
                        },
                        {
                            type: "Address",
                            value: "NdfY7Wr6K29GTyu3CySLASBhjYLVXnhqrP"
                        },
                        {
                            type: "Integer",
                            value: "1"
                        },
                        {
                            type: "Any",
                            value: null
                        }
                    ],
                    fee: '0.0001',
                    broadcastOverride: false,
                    signers: [{ account: "NUqsqGmgTCf5t9pVf9Tz3E3riUsu91tgWj", scopes: 128 }]
                }).then(result => {
                    console.log('Read invocation result: ' + JSON.stringify(result));
                })

wrote this script to transfer some gas tokens but it skips to the result part even before I have signed the transaction.
BTW, I just tried the memeGovernance dapp , and its showing rpc error when sending tx , so is there any bypass to this.
or is the RPC down or something for now?

@fuzious the param account in signers should be the scriptHash of your address.


Clearing the terminal throws off navigation selection

Testing #145627

run a lot of commands
type in clear
run more commands
:above: as you navigate around the selection will often highlight the wrong item

Looks like we need a similar Windows workaround when clearing a screen when shell integration is disabled as well.

To verify make sure you do not have shell integration enabled. Note when verifying that the experience after clearing may be a little wonky because of https://github.com/microsoft/vscode/issues/145917, try not navigating until running clear to workaround that.


fix: revert PR-5520

Motivation

To unblock v1.9.0
Not a fix for #5549 but hope we don't see the issue there

Description

Revert #5520
Add more logs to investigate #5591 if it happens again

:tada: This PR is included in v1.9.0 :tada:


Deployment timeout after 10 minutes

Hey,
First many thanks for maintaining this plugin.
Last couple of days we hit some weird errors with deployment. Looks like:
> gatsby-plugin-s3 deploy --yes

- Retrieving bucket info...

Too long with no output (exceeded 10m0s): context deadline exceeded

It times out after 10m. Not sure what times out though. Admittedly we have a lot of pages to upload on each build (35k right now and growing) and the build is running on circleci. Sometimes it finishes after 3 minutes, sometimes after 7 i guess this is circleci related.
I d really like to get a better understanding of this 10 minute timeout and see whether we can increase it.

Hmm, so it's not making it to the 'Configuring bucket...' step? That's pretty unexpected. That means it seems to be getting stuck somewhere in here.
Even with 35k pages I wouldn't expect those lines to present a problem, since those lines aren't particularly dependant on how many pages you have. Do you have a lot of redirects by any chance?

I never see Configuring bucket even if everything goes smoothly. maybe i should change something in the configuration?
And there shouldn't be a lot redirects no. Anyway i could list those? I would guess it will be something like 10-20

Yea, I think ora just stops logging to stdout if the terminal doesn't support updates.
Basically, it's still doing stuff, but CircleCI thinks it's not.
10 minutes is a long time for the upload to take, but I've seen this happen on pretty large (10k+ pages) sites, so it's not that uncommon.
You mention it sometimes does finish, so it's clearly not stuck or anything.
On my own CI, the maximum execution time can be increased.
Is this not possible for CircleCI?
I wonder what kind of library the gatsby CLI itself uses for the progressbars, because the build output in my CI is a lot cleaner there. (it logs after the ending of each phase)

For your reference, my output looks the same, even though it did clearly did far more stuff than just retrieving the bucket info

Ora has actually been causing issues for my testing suite work too. If I make the test suite pass-through console output from the deploy process then the spinner animation causes hundreds of lines to be logged.
It's worth investigating what Gatsby uses. Another option would be to write a wrapper around Ora and replace it with console.log if we are running in a CI environment.

As a workaround, check out CircleCI's no_output_timeout setting. https://support.circleci.com/hc/en-us/articles/360045268074-Build-Fails-with-Too-long-with-no-output-exceeded-10m0s-context-deadline-exceeded-

Ha ok now it makes more sense that its circleci killing the job!
we will update that and should be good. i don't think there's something to do in the plugin! Thanks both of you for the support :)


Expert-informed feature bagging

Summary
I would like to control feature bagging rather than having it be random. I'd like to specify, for a given iteration, the subset of features that I want that tree to be fit to.
Motivation
For my use of lightgbm, I've found that my models underfit when using random feature bagging, but if I manually select subsets of features that make sense together, I'm able to achieve much higher performance than random feature bagging or using all the candidate features.
Description
I would like to either have a callback on each iteration to specify the features to use for that tree, or a the ability to specify a set of feature subsets that can be randomly selected from each iteration.

We have recently added the ability to exclude specific feature interactions: https://lightgbm.readthedocs.io/en/latest/Parameters.html#interaction_constraints
It sounds like you want the opposite feature to this (ability to specify the allowed feature interactions), but it might be helpful nevertheless (depending on your specific use case).

Ah, so supposing that I had 2 correlated conditioning features (A & B), and a predictive feature (P), then I could ensure that any path in any tree has (A&P or B&P), but never (A&B or A&B&P)? Is there a reference where I can read more about this?
While that could be helpful for my application, I actually would like something like the learning rate callback, but for feature selection for a given tree. There are many combinations of interactions I'd like, and I'd like to have the model learn (randomly or deterministically) from only the feature subsets that I choose.
Could I generate interaction constraints to do that w/o hitting pathological algorithmic performance?

@dgrnbrg See my edit to my earlier comment above, I had misremembered how this works. Our implementation is similar to xgboost's; see their docs for detailed explanation: https://xgboost.readthedocs.io/en/latest/tutorials/feature_interaction_constraint.html
For your example, assuming your features are in the order [A, B, P], you could specify interaction_constraints=[[A,P], [B,P]] to prevent A and B appearing in the same branch.


Support for macos 10.13.4 (High Sierra)

I have just upgraded to a new macos version 10.13.4 (High Sierra)
I downloaded Node 10.0.0 as the current stable version but this had an error, so I installed 8.11.1 over the top, hoping that would work.
I'm getting the following problem (with 8.11.1) when trying to run 'gulp':
kohekohe:trunk murraycollingwood$ gulp
/Users/murraycollingwood/dev/sobs-git/trunk/node_modules/node-sass/lib/binding.js:13
throw new Error(errors.unsupportedEnvironment());
^
Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (57)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v3.13.1
at module.exports (/Users/murraycollingwood/dev/sobs-git/trunk/node_modules/node-sass/lib/binding.js:13:13)
at Object. (/Users/murraycollingwood/dev/sobs-git/trunk/node_modules/node-sass/lib/index.js:14:35)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object. (/Users/murraycollingwood/dev/sobs-git/trunk/node_modules/gulp-sass/index.js:187:21)
I did visit the page suggested but it didn't mean much to me.
OS X 64-bit has been out for a while now, in fact my previous mac is running OS X 64-bit and I was running Node-Sass on this machine without a problem.  So I think there is something amiss with the error message, or I am missing a particular matching software version.

NPM version (npm -v): 5.6.0
Node version (node -v): 8.11.1
Node Process (node -p process.versions): { http_parser: '2.8.0',
node: '8.11.1',
v8: '6.2.414.50',
uv: '1.19.1',
zlib: '1.2.11',
ares: '1.10.1-DEV',
modules: '57',
nghttp2: '1.25.0',
openssl: '1.0.2o',
icu: '60.1',
unicode: '10.0',
cldr: '32.0',
tz: '2017c' }
Node Platform (node -p process.platform): darwin
Node architecture (node -p process.arch): x64
node-sass version (node -p "require('node-sass').info"): kohekohe:trunk murraycollingwood$ node -p "require('node-sass').info"
/Users/murraycollingwood/dev/sobs-git/trunk/node_modules/node-sass/lib/binding.js:13
throw new Error(errors.unsupportedEnvironment());
^

Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (57)

npm node-sass versions (npm ls node-sass<EMAIL_ADDRESS>/Users/murraycollingwood/dev/sobs-git/trunk
└─┬<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
I've been using sass for a couple of years, so I'm still relatively new.  If there is any versions to change please include copies of the commands I should use to uninstall/install/update/replace etc.
Cheers
Murray

This isn't an OSX support issue.
You're using<EMAIL_ADDRESS>which is very very old. You'll need<EMAIL_ADDRESS>for Node 10 support. You can get that with gulp-sass@v3.

Solved with:
npm rebuild node-sass


[SPARK-21417][SQL] Infer join conditions using propagated constraints

What changes were proposed in this pull request?
This PR adds an optimization rule that infers join conditions using propagated constraints.
For instance, if there is a join, where the left relation has 'a = 1' and the right relation has 'b = 1', then the rule infers 'a = b' as a join predicate. Only semantically new predicates are appended to the existing join condition.
Refer to the corresponding ticket and tests for more details.
How was this patch tested?
This patch comes with a new test suite to cover the implemented logic.

Test build #79804 has started for PR 18692 at commit e67d4d3.

I think we already did it via constraint propagation, didn't we?

@cloud-fan which rule do you mean? PushPredicateThroughJoin seems to be the closest by logic but it has a slightly different purpose and does not cover this use case. In fact, I used the proposed rule in conjunction with PushPredicateThroughJoin in the tests.

We need to use the propagated constraints to infer the join conditions.

@gatorsmile thanks for the input. Let me check that I understood everything correctly. So, I keep it as a separate rule that is applied only if constraint propagation enabled. Inside the rule, I rely on join.constraints to infer the join conditions. The remaining logic stays the same. Correct?
I guess that InferFiltersFromConstraints can be used as a guideline.

You are on the right track. You might find some bugs/issues when you implement it. Sorry, too busy recently.

Test build #80056 has started for PR 18692 at commit 915dc7e.

Test build #80056 has finished for PR 18692 at commit 915dc7e.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80056/
Test FAILed.

Merged build finished. Test FAILed.

Test build #80058 has started for PR 18692 at commit 851f388.

You also need to resolve another case:
        Seq((1, 2)).toDF("col1", "col2").write.saveAsTable("t1")
        Seq(1, 2).toDF("col").write.saveAsTable("t2")
        sql("SELECT * FROM t1, t2 WHERE t1.col1 = t1.col2 AND t1.col1 = 1 AND t2.col = 1")

This new rule can infer the unneeded join conditions, col2 = col1 AND col2 = col AND col1 = col

Test build #80058 has finished for PR 18692 at commit 851f388.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80058/
Test PASSed.

Merged build finished. Test PASSed.

BTW, your PR title and descriptions are out of dated.

@gatorsmile I took a look at the case above. Indeed, the proposed rule triggers this issue but only indirectly. In the example above, the optimizer will never reach a fixed point. Please, find my investigation below.
...

// The new rule infers correct join predicates
Join Inner, ((col2#33 = col#34) && (col1#32 = col#34))
:- Filter ((col1#32 = col2#33) && (col1#32 = 1))
:  +- Relation[col1#32,col2#33] parquet
+- Filter (col#34 = 1)
   +- Relation[col#34] parquet

// InferFiltersFromConstraints adds more filters
Join Inner, ((col2#33 = col#34) && (col1#32 = col#34))
:- Filter ((((col2#33 = 1) && isnotnull(col1#32)) && isnotnull(col2#33)) && ((col1#32 = col2#33) && (col1#32 = 1)))
:  +- Relation[col1#32,col2#33] parquet
+- Filter (isnotnull(col#34) && (col#34 = 1))
   +- Relation[col#34] parquet

// ConstantPropagation is applied
Join Inner, ((col2#33 = col#34) && (col1#32 = col#34))
!:- Filter (((((col2#33 = 1) && isnotnull(col2#33)) && isnotnull(col1#32)) && ((1 = col2#33) && (col1#32 = 1)))
 :  +- Relation[col1#32,col2#33] parquet
 +- Filter (isnotnull(col#34) && (col#34 = 1))
    +- Relation[col#34] parquet

// (Important) InferFiltersFromConstraints infers (col1#32 = col2#33), which is added to the join condition.
Join Inner, ((col1#32 = col2#33) && ((col2#33 = col#34) && (col1#32 = col#34)))
!:- Filter (((((col2#33 = 1) && isnotnull(col2#33)) && isnotnull(col1#32)) && ((1 = col2#33) && (col1#32 = 1)))
 :  +- Relation[col1#32,col2#33] parquet
 +- Filter (isnotnull(col#34) && (col#34 = 1))
    +- Relation[col#34] parquet

 // PushPredicateThroughJoin pushes down (col1#32 = col2#33) and then CombineFilters produces
Join Inner, ((col1#32 = col#34) && (col2#33 = col#34))
!:- Filter ((((isnotnull(col1#32) && (col2#33 = 1)) && isnotnull(col2#33)) && ((1 = col2#33) && (col1#32 = 1))) && (col2#33 = col1#32))
 :  +- Relation[col1#32,col2#33] parquet
 +- Filter (isnotnull(col#34) && (col#34 = 1))
    +- Relation[col#34] parquet

After that, ConstantPropagation replaces (col2#33 = col1#32) as (1 = 1), BooleanSimplification removes (1 = 1), InferFiltersFromConstraints infers (col2#33 = col1#32) again and the procedure repeats forever. Since InferFiltersFromConstraints is the last optimization rule, we have the redundant condition mentioned by you. The Optimizer without the new rule will also not converge on the following query:
Seq((1, 2)).toDF("col1", "col2").write.saveAsTable("t1")
Seq(1, 2).toDF("col").write.saveAsTable("t2")
spark.sql("SELECT * FROM t1, t2 WHERE t1.col1 = 1 AND 1 = t1.col2 AND t1.col1 = t2.col AND t1.col2 = t2.col").explain(true)

Correct me if I am wrong, but it seems like an issue with the existing rules.

Test build #80362 has started for PR 18692 at commit 281f955.

Test build #80362 has finished for PR 18692 at commit 281f955.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80362/
Test PASSed.

Merged build finished. Test PASSed.

@gatorsmile I updated the rule to cover cross join cases. Regarding the case with the redundant condition mentioned by you, I opened SPARK-21652. It is an existing issue and is not caused by the proposed rule. BTW, I can try to fix it once we agree on a solution.

@aokolnychyi Thanks for finding the non-convergent case! Let me see how to fix it.

@gatorsmile what is our decision here? Shall we wait until SPARK-21652 is resolved? In the meantime, I can add some tests and see how the proposed rule works together with all others.

Sorry for the delay. @jiangxb1987 will submit a simple fix for the issue you mentioned. That will not be a perfect fix but it partially resolve the issue. In the future, we need to move the filter removal to a separate batch for cost-based optimization instead of doing it with filter inference in the same RBO batch.

Can we restrict this to cartesian product ONLY ? One clear downside of doing this for other joins is that it will potentially add shuffle in case of (bucketing queries) and (subqueries in general). After adding the inferred join conditions, it might lead to the child node's partitioning NOT satisfying the JOIN node's requirements which otherwise could have.

In this PR, we should limit it to cartesian product now. In the future, we need to perform smarter when extracting equi-join keys.

Test build #81390 has started for PR 18692 at commit cfeae46.

Test build #81390 has finished for PR 18692 at commit cfeae46.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81390/
Test PASSed.

After adding the inferred join conditions, it might lead to the child node's partitioning NOT satisfying the JOIN node's requirements which otherwise could have.

Isn't it an existing problem? the current constraint propagation framework infers as many predicates as possible, so we may already hit this problem. I think we should revisit the constraint propagation framework to think about how to avoid adding more shuffles, instead of stopping improving this framework to infer more predicates.

@cloud-fan : In event when the (set of join keys) is a superset of (child node's partitioning keys), its possible to avoid shuffle : https://github.com/apache/spark/pull/19054 ... this can help with 2 cases - when users unknowingly join over extra columns in addition to bucket columns

the one you mentioned (ie. inferred conditions).

cc @gengliangwang Review this?

Test build #82891 has started for PR 18692 at commit e0e6ad3.

Test build #82892 has started for PR 18692 at commit b69185c.

Test build #82891 has finished for PR 18692 at commit e0e6ad3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/82891/
Test PASSed.

Test build #82892 has finished for PR 18692 at commit b69185c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/82892/
Test PASSed.

Hi, we are very interested in this patch. I wonder if it could detect this code automatically, without needing to write the explicit join:
package net.sansa_stack.spark.playground

import org.apache.spark.sql.{Row, SparkSession}
import org.apache.spark.sql.types.{IntegerType, StructField, StructType}
import org.scalatest._

class TestSparkSqlJoin extends FlatSpec {

  "SPARK SQL processor" should "be capable of handling transitive join conditions" in {

    val spark = SparkSession
      .builder()
      .master("local[1]")
      .getOrCreate()

    val schema = new StructType()
      .add("s", IntegerType, nullable = true)
      .add("p", IntegerType, nullable = true)
      .add("o", IntegerType, nullable = true)

    val data = List((1, 2, 3))
    val dataRDD = spark.sparkContext.parallelize(data).map(attributes => Row(attributes._1, attributes._2, attributes._3))
    spark.createDataFrame(dataRDD, schema).createOrReplaceTempView("T")

    spark.sql("SELECT A.s FROM T A, T B WHERE A.s = 1 AND B.s = 1").explain(true)
  }

}

I built this Pull request locally but it still gives me the same issue -->
== Physical Plan ==
org.apache.spark.sql.AnalysisException: Detected cartesian product for INNER join between logical plans
Project [s#3]
+- Filter (isnotnull(s#3) && (s#3 = 1))
   +- LogicalRDD [s#3, p#4, o#5], false
and
Project
+- Filter (isnotnull(s#25) && (s#25 = 1))
   +- LogicalRDD [s#25, p#26, o#27], false
Join condition is missing or trivial.
Use the CROSS JOIN syntax to allow cartesian products between these relations.;

@SimonBin The initial solution handled your case but then there was a decision to restrict the proposed rule to cross joins only. You can find the reason in this comment or in the code.

@aokolnychyi thank you for the clarification, I see now

Hi @aokolnychyi, a on note on @SimonBin 's comment (I am his colleague):

The initial solution handled your case but then there was a decision to restrict the proposed rule to cross joins only.

SimonBin's example appears to work when in addition enabling spark.conf.set("spark.sql.crossJoin.enabled", "true")
We will investigate further how far this gets us.

Test build #84176 has started for PR 18692 at commit ab7d966.

Test build #84177 has started for PR 18692 at commit 3e090f9.

Test build #84176 has finished for PR 18692 at commit ab7d966.

This patch fails Spark unit tests.
This patch does not merge cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/84176/
Test FAILed.

Build finished. Test FAILed.

Test build #84177 has finished for PR 18692 at commit 3e090f9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/84177/
Test PASSed.

Also add a test case for non-deterministic cases.  For example, given the left child has a = rand() and the right child has b = rand(), we should not get a = b

Test build #84349 has started for PR 18692 at commit 0e5a9f2.

Test build #84349 has finished for PR 18692 at commit 0e5a9f2.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class EquivalentExpressionMap

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/84349/
Test FAILed.

Test build #84351 has started for PR 18692 at commit 9ab91a1.

Test build #84351 has finished for PR 18692 at commit 9ab91a1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/84351/
Test PASSed.

LGTM
Thanks for your patience! It looks much good now. Really appreciate for your contributions! Welcome to make more contributions!
Thanks! Merged to master.

@aokolnychyi After rethinking about it, we might need to revert this PR. Although it converts a CROSS Join to an Inner join, it does not improve the performance. What do you think?

Yea I have the same feeling. If the left side has a a = 1 constraint, and the right side has a b = 1 constraint, adding a a = b join condition does not help as it always evaluate to true.

Sure, if you guys think it does not give any performance benefits, then let's revert it.
I also had similar concerns but my understanding was that having an inner join with some equality condition can be beneficial during the generation of a physical plan. In other words, Spark should be able to select a more efficient join implementation. I am not sure how it is right now but previously you could have only BroadcastNestedLoopJoin or CartesianProduct without any equality condition. Again, that was my assumption based on what I remember.

I took a look at JoinSelection. It seems we will not get BroadcastHashJoin or ShuffledHashJoin if we revert this rule.

Yeah, correct. So, we should revert then.

Will do it. Thanks!

Done. Reverted.

Hi, All.
Since the commit is reverted from the master branch, can we update the status of JIRA issue?

https://issues.apache.org/jira/browse/SPARK-21417

@aokolnychyi Could you rethink about it by using some cases like a in (0, 2, 3, 4) and b in (0, 2, 3, 4)? and then refer to a = b?

I am not sure we can infer a == b if a in (0, 2, 3, 4) and b in (0, 2, 3, 4).
table 'a'
a1 a2
1  2
3  3
4  5

table 'b'
b1 b2
1  -1
2  -2
3  -4

SELECT * FROM a, b WHERE a1 in (1, 2) AND b1 in (1, 2)
// 1 2 1 -1
// 1 2 2 -2

SELECT * FROM a JOIN b ON a.a1 = b.b1 WHERE a1 in (1, 2) AND b1 in (1, 2)
// 1 2 1 -1

Do I miss anything?

you are right, then I don't know if there is any valid use case for inferring join condition from literals...

Yeah. That is a wrong case. Let us revisit it if we can find any useful case here. Thank you!


Testing tracker integration update

Ensure gitbot integration works

test comment

closing after talking to Juan, Dominic, and Hema


[11.x] Support Model::class Table Discovery in Migrations Schema

This PR consists of adding the same support we have for test stuff like:
$this->assertDatabaseHas(User::class, [...]);

$this->assertDatabaseMissing(User::class, [...]);

$this->assertDatabaseEmpty(User::class);

$this->assertDatabaseCount(User::class, 1);

... but thinking about migrations, making possible things like:
Schema::table(User::class, function (Blueprint $table) {
    /* ... */
});

The main benefit of this is that it allows us to fix the name of the table defined through the model, which can be reused mainly in the table method, making errors related to the table name impossible.

@devajmeireles I believe migrations and models should remain decoupled and operate independently since they represent different abstraction layers within the application.

Migrations are focused on database schema management, while models represent the business logic in an OOP context. Mixing these layers adds unnecessary complexity.
Migrations need to run in isolation, especially in environments like CI/CD pipelines or during headless deployments, where models may not even be available. Introducing a dependency on models would complicate this process.
This approach also raises challenges for scenarios like multi-tenant systems or applications with dynamic tables, where table names can vary at runtime.

Keeping migrations and models separate ensures flexibility, simplicity, and a clear separation of concerns.
Thank you for your collaboration.


1x1 MeshDevice isn't properly supported for all apis

The following snippet will hit an assertion in copy_host_to_device_tensor with a 1x1 MeshDevice if built in debug mode or a bad variant access in release, but not with MeshDevices that use more than 1 device.
    num_devices = device.get_num_devices() if isinstance(device, ttnn.MeshDevice) else 1
    x = torch.randn(num_devices, 1, 64, 64, dtype=torch.bfloat16)
    xt = ttnn.from_torch(
        x,
        dtype=ttnn.bfloat16,
        layout=ttnn.TILE_LAYOUT,
        device=device,
        memory_config=ttnn.L1_MEMORY_CONFIG,
        mesh_mapper=inputs_mesh_mapper,
        sub_device_ids=[ttnn.SubDeviceId(0)],
    )

    xt_host = ttnn.from_torch(
        x,
        dtype=ttnn.bfloat16,
        layout=ttnn.TILE_LAYOUT,
        mesh_mapper=inputs_mesh_mapper,
        sub_device_ids=[ttnn.SubDeviceId(1)],
    )

    ttnn.copy_host_to_device_tensor(xt_host, xt)

Assertion is: RuntimeError: TT_ASSERT @ /localdev/aho/tt-metal/ttnn/cpp/ttnn/tensor/tensor.cpp:922: std::holds_alternative<OwnedStorage>(async_safe_tensor.get_storage())
This is because the device tensor is created as a StorageType::Device tensor even though a MeshDevice was passed in because the infra automatically converts tensors with a single worker to a single device tensor.
However, the host tensor created here is created as a StorageType::MULTI_DEVICE_HOST tensor, which leads to the incorrect behaviour since the infra sees a single device tensor, so it expects the host tensor to be Borrowed or Owned, not MultiDeviceHost.

Taking a look

Confirmed that with https://github.com/tenstorrent/tt-metal/pull/15845 fixes the issue.  Tracking that in #15840.

https://github.com/tenstorrent/tt-metal/pull/15845 was merged, tracking further work #15840.
@tt-aho / @SeanNijjar  - can you confirm the tests cases that were commented out now work?

Confirmed this seems to pass locally for me now. Will try on ci. Thanks!

Also passing on ci for my test case, closing the issue.


Banner links dont work in local build

Currently if you build locally the banner links - ie:

they 404
the reason for this is that the links are to eg training rather than training.html - on the real website netlify mangles/redirects these
fixing this is not trivial - we would need to add some nginx config (or similar) to do it.
relatedly the main link goes to the envoy website not to the local site root. This should be an easier fix

cc @missBerg  - i think you mentioned this

@phlax can i work on this ?

@MAVRICK-1 for sure - that would be appreciated
this is for the static target in docker-compose
probably the easiest way to resolve is adding a custom nginx config with something like:
server {
    listen 80;
    server_name yourdomain.com;

    location / {
        try_files $uri $uri.html $uri/ =404;
    }
}

Okay I'm working on it
On Thu, 12 Dec 2024, 15:43 phlax, @.***> wrote:

@MAVRICK-1 https://github.com/MAVRICK-1 for sure - that would be
appreciated
this is for the static target in docker-compose
probably the easiest way to resolve is adding a custom nginx config with
something like:
server {
listen 80;
server_name yourdomain.com;
location / {
    try_files $uri $uri.html $uri/ =404;
}

}
—
Reply to this email directly, view it on GitHub
https://github.com/envoyproxy/envoy-website/issues/496#issuecomment-2538452747,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDBQOEN622OVZ5POVW6INTD2FFOVXAVCNFSM6AAAAABTN5I2T2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZYGQ2TENZUG4
.
You are receiving this because you were mentioned.Message ID:
@.***>


YouTube Red Music Service

Work on the new YouTube Red music service

service not available in AUS

I have a YouTube Red subscription if there's anything I can do to assist with testing this one.

@Celti ... thankfully we have received YouTube Red here is Australia ... I have tested it already and it seems to work with what I have at the moment. I do however appreciate your offer, cheers

seems to work with YouTube Red music service. Closing issue


RuntimeError: Error compiling objects for extension

Thank you for your awesome works!
I follow your tutorial, but when I run python setup.py install, this problem as title has shown. And my gcc version is 9.4.0.
Can you check out some dependency of your code?

I am using:

Ubuntu 20.04.2 LTS
Python 3.7.11
GCC 9.3.0
torch 1.9.0
torchvision 0.2.2
CUDA 11.1
Nvidia Driver 455.23.05


Imposible scan the api qrcode from Whatsapp Bussines after today updates

the update released today (24/02/2022) by whatsapp caused the qrcode generated by the api cannot be scanned from whatsapp bussines, any ideas

I'm facing the same problem

WhatsApp has now made multi-device official. One of my clients updated the app by himself and it stopped working.

Hi,
I have the same problem..... any news?

This library works with multidevice feature: https://github.com/tulir/whatsmeow

@dfelici87 are you using whatsmeow? How much effort to convert from go-whatsapp to it? Any issue?

Depends, but whatsmeow is quite easy to use


Fix uninstall script

Fixes #2378
Changes proposed:

[x] Fix

This PR introduces the creation of an uninstall bundled script. It's a separate script than the main extension bundled script.
I also tested in live-action.


Fix bug in CC0008 when accessing declaring variable

Closes #324

Coverage increased (+0.02%) to 89.96% when pulling cda7e65f30c5dda882fac163456df297fda346cb on giggio:fix-cc0008 into b66ec13b3b120f3e8413d18d0e1a65ea42b39cf1 on code-cracker:master.


New tiles appear in next available empty space

Description
Rather than having tiles appear in the top left and forcing everything around to move, new tiles should appear in the next available space. If you really wanted to get fancy, you could have the page scroll down to where the new tile got dropped upon creation.
I'd really like this feature because it annoys me that I have to reorganize everything that got shifted whenever a new tile is created.
Priority
Low (Nice-to-have)

Can you try and tell us if this issue still happens as of the latest image ? v0.14.0 ?

This feature is already implemented on my board-database branch

Hello, new user here,
i just installed and configured Homarr and have to say: Great Work 👍
But this issue here is one that I immediatly noticed and was annoyed by.
I use this docker image, i think it should be the latest one:
ghcr.io/ajnart/homarr                   latest    64f08324f08f   3 weeks ago    663MB
according to the temp_package.json inside the container it's v0.15.2
on another node, while searching for my version number, i stumbled upon this feature request
https://github.com/ajnart/homarr/issues/93
it seems like it got implemented once but got lost again in a regression. Would be really handy in cases like these...

This feature will be part of v1.0, see #1993


Heml3: Upgrade of secret with immutable field fails

Output of helm version: 3.3
Output of kubectl version: v1.16.6-beta.0"
I changed/set type of secret after it was created in release, and helm faild to upgrade release.

Error: UPGRADE FAILED: cannot patch "gcr-cred" with kind Secret: Secret "gcr-cred" is invalid: type: Invalid value: "kubernetes.io/dockerconfigjson": field is immutable

So probaly in such cases helm should recreate resource, but not throw the error?

@whitecolor Can you provide some details around "changed/set type of secret after it was created in release"? It would help to better try and troubleshoot the issue.

I first created release with chart containing named secret that didn't have type field, then I changed it (added to chart resource), and tried to upgrade the release.

The error is being returned from Kubernetes and it is saying that the type field of the secret object cannot be updated. You should get the same error if you try to update it using Kubernetes directly e.g. using kubectl.
If you can, it maybe best to remove the release and re-install with the correct secret type.

If you can, it maybe best to remove the release and re-install with the correct secret type.

I did this. I'm telling that probably heml itself could handle this by fully removing resource and recreating it.

Helm calls the Kubernetes API to apply updates. It is therefore working as expected and returning the expected error.
You can use the --force flag but that pretty much destroys the resources and recreates them. So, similar to doing it as a user.
Hope this answers your question.

Ok, I belive, thanks)


Module compiled with Swift 5.1.3 cannot be imported by the Swift 5.2.4 compiler

Hey,
I'm using Xcode 11.5 and I've updated the latest version of SDK still I'm getting the following error:
Module compiled with Swift 5.1.3 cannot be imported by the Swift 5.2.4 compiler
P.S: I did this so many times in the past and once I update the SDK it worked well with updated version Xcode but this time it's giving me this error.

Latest version (1.7.3) should be compiled with Swift 5.2 compiler
Check Podfile.lock and look for version of ClaySDK
if you are using pods like this:
pod 'ClaySDK', '~> 1.7'
try running
pod install --repo-update
to fetch latest version of pod

Thanks. I've updated the SALTOJustInMobileSDK and pods and it worked.


Add support for curl_easy_upkeep

Add feature-gated support for curl_easy_upkeep, introduced in 7.62.0

Happy to discuss feature naming, etc! Would be nice to have a model for adding in features that have been introduced within the last 9 years.

Thanks for this! I wonder, though, would it be possible to do some quick-and-dirty version detection of the libcurl found at build time? That way we could change this function to always be available and simply return an error unconditionally if the linked version doesn't have support.

Even that won't always work though, because if we are linking to libcurl dynamically then the build machine might have a newer version of libcurl than the user's machine. Depending on the system you'll probably get undefined symbol errors when the OS tries to run your program and the only way to opt-out would be to downgrade libcurl to an old enough version on your build machine.

I guess for dynamic curl one option might be to use something like
libloading to dynamically load the library, and try and get the relevant
function pointer, failing the call if it's not found.
For static curl it could be determined at build time.
On Thu, 25 Feb 2021, 18:15 Stephen M. Coakley<EMAIL_ADDRESS>wrote:

Even that won't always work though, because if we are linking to libcurl
dynamically then the build machine might have a newer version of libcurl
than the user's machine. Depending on the system you'll probably get undefined
symbol errors when the OS tries to run your program and the only way to
opt-out would be to downgrade libcurl to an old enough version on your
build machine.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/alexcrichton/curl-rust/pull/378#issuecomment-786101485,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPA36MMH2BPKP42NPUIAR3TA2HTRANCNFSM4YGXDDBA
.

I also realised I missed a few files off - let me push those before pushing anything else.

The code I've written for dynamic loading is this:
    /// Some protocols have "connection upkeep" mechanisms. These mechanisms
    /// usually send some traffic on existing connections in order to keep them
    /// alive; this can prevent connections from being closed due to overzealous
    /// firewalls, for example.
    ///
    /// Currently the only protocol with a connection upkeep mechanism is
    /// HTTP/2: when the connection upkeep interval is exceeded and upkeep() is
    /// called, an HTTP/2 PING frame is sent on the connection.
    #[cfg(not(feature = "static-ssl"))]
    pub fn upkeep(&self) -> Result<(), Error> {
        // Derive the curl binary name
        let libname = libloading::library_filename("curl");

        let ret = unsafe {
            let lib = libloading::Library::new(&libname).map_err(|_| {
                let mut e = Error::new(curl_sys::CURLE_FAILED_INIT);
                e.set_extra(format!("Failed to load library: {:?}", libname));
                e
            })?;

            let func = lib
                .get::<unsafe extern "C" fn(*mut curl_sys::CURL) -> curl_sys::CURLcode>(
                    b"curl_easy_upkeep",
                )
                .map_err(|_| {
                    let mut e = Error::new(curl_sys::CURLE_FAILED_INIT);
                    e.set_extra("Failed to find function: curl_easy_upkeep".to_string());
                    e
                })?;

            self.cvt(func(self.inner.handle))
        };

        panic::propagate();
        return ret;
    }

The test_upkeep test fails with
---- test_upkeep stdout ----
thread 'test_upkeep' panicked at 'handle.upkeep() failed with Error { description: "Failed initialization", code: 2, extra: Some("Failed to find function: curl_easy_upkeep") }', tests/easy.rs:849:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

with dynamic libcurl 7.60.0, and passes with dynamic libcurl 7.76.0. "static-curl" curl works as well regardless.
@alexcrichton - thoughts on the above? If you want me to explore using libc::dlsym instead of libloading I can (to reduce the number of dependencies) but afaict libloading makes it ergonomic to use those functions.

Interesting approach, I'll have to think about this. Some initial thoughts:

We should probably return some sort of "your curl does not support this method" error if the symbol cannot be found.
We should probably avoid loading libraries on every method call and instead do it just once lazily as needed. Otherwise it could be expensive.
There's a potential safety risk here if the libcurl that dynamic loading finds gets a different binary than the one the application is linked to, which could happen if the user has more than one libcurl installed. We'd be calling methods from one libcurl version on a handle created by a different libcurl version

Completely agree on your last point - I'm not sure how to reconcile it. I
did a little research into dlsym and dlopen but couldn't immediately see an
answer. If I have time I'll dig a little deeper.
On Thu, 25 Feb 2021, 21:42 Stephen M. Coakley<EMAIL_ADDRESS>wrote:

Interesting approach, I'll have to think about this. Some initial thoughts:

We should probably return some sort of "your curl does not support
this method" error if the symbol cannot be found.
We should probably avoid loading libraries on every method call and
instead do it just once lazily as needed. Otherwise it could be expensive.
There's a potential safety risk here if the libcurl that dynamic
loading finds gets a different binary than the one the application is
linked to, which could happen if the user has more than one libcurl
installed. We'd be calling methods from one libcurl version on a handle
created by a different libcurl version

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/alexcrichton/curl-rust/pull/378#issuecomment-786247236,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPA36KDUAESYLPBTZY2OVTTA274JANCNFSM4YGXDDBA
.

Looking at the man page for dlopen, it seems that if you use a NULL pointer
as your argument to dlopen, it will allow you to search the main program
plus any loaded shared libraries for a given symbol name, which seems
perfect. I'll see how that maps into libloading (if at all) and make a
patch tomorrow.
On Thu, 25 Feb 2021, 23:03 Max Dymond<EMAIL_ADDRESS>wrote:

Completely agree on your last point - I'm not sure how to reconcile it. I
did a little research into dlsym and dlopen but couldn't immediately see an
answer. If I have time I'll dig a little deeper.
On Thu, 25 Feb 2021, 21:42 Stephen M. Coakley<EMAIL_ADDRESS>wrote:

Interesting approach, I'll have to think about this. Some initial
thoughts:

We should probably return some sort of "your curl does not support
this method" error if the symbol cannot be found.
We should probably avoid loading libraries on every method call and
instead do it just once lazily as needed. Otherwise it could be expensive.
There's a potential safety risk here if the libcurl that dynamic
loading finds gets a different binary than the one the application is
linked to, which could happen if the user has more than one libcurl
installed. We'd be calling methods from one libcurl version on a handle
created by a different libcurl version

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/alexcrichton/curl-rust/pull/378#issuecomment-786247236,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPA36KDUAESYLPBTZY2OVTTA274JANCNFSM4YGXDDBA
.

Seems as if you can do this with libloading, though for some reason this is not exposed on the top level Library in libloading.
    #[cfg(not(feature = "static-curl"))]
    pub fn upkeep(&self) -> Result<(), Error> {
        let ret = unsafe {
            let lib = libloading::os::unix::Library::this();
            let func = lib
                .get::<unsafe extern "C" fn(*mut curl_sys::CURL) -> curl_sys::CURLcode>(
                    b"curl_easy_upkeep",
                )
                .map_err(|_| {
                    let mut e = Error::new(curl_sys::CURLE_FAILED_INIT);
                    e.set_extra("Failed to find function: curl_easy_upkeep".to_string());
                    e
                })?;

            self.cvt(func(self.inner.handle))
        };

        panic::propagate();
        return ret;
    }

Whether that's easier to use I don't know! There does appear to be similar support in the Windows Library as well for this but am unsure it works in the same way.

That's a good point about build-time vs runtime, but I think that it may be a concern best handled by applications themselves rather than this crate. For example if we unconditionally define the method here (not even do version detection), it shouldn't cause problems if you don't actually even call the method in your application (the function is GC'd away and the symbol is never referenced).
In that sense I don't think that adding this symbol is a detriment to existing users. I'd prefer to avoid detection if possible because it tends to be pretty heavyweight and not always the most portable.
Perhaps this could do build-time detection, and then eschew runtime detection to the caller? (e.g. applications would be responsible for providing the right knobs to doing this detection at runtime if necessary).

I haven't seen a good way of fitting build-time detection in with the existing build.rs code; presumably you'd want to do something like:

in curl-sys, try and build against "the library" to detect the function, ala AC_CHECK_LIB.

not trivial because pkgconfig just outputs cargo build lines to stdout, rather than in an inspectable way.

if function is detected, set cfg variable with cargo:rustc-cfg=KEY[="VALUE"]
expose this up the chain somehow so that curl knows that curl-sys was compiled with a certain feature enabled.

There's a lot of steps there that I'm handwaving away because I'm not really sure how to achieve them.

If you'd prefer to keep this as a Cargo feature that seems fine too. My experience is that this makes it pretty non-composable and this is pretty unlikely to ever get used as a result. By putting some extra work in it's possible to make it much more ergonomic to use and possible for consumers to use in more circumstances.

In the short term I think I'd prefer "merged and using a feature" over "rewriting the build script system and not yet merged" :smile: After that I'd be happy to throw some thinking and prototyping power at doing feature detection - surely this must be solved in other -sys libraries, so I can do a bit of investigation there.

Ok sounds fine by me.


[Bug]: TypeError: stat: path should be string, bytes, os.PathLike or integer, not NoneType

Project Version
3.2.6
Platform and OS Version
Windows 10
Affected Devices
All
Existing Issues
No response
What happened?
I tried to convert my previously trained RVC models to an audio file. But when I try to convert it, I get an error and I don't know why. I tried restarting my computer but it doesn't help. And I tried everything to fix this error
Steps to reproduce

Restarted my computer
Clicked on convert
Tried to move Applio folder to local disc (C:)

Expected behavior
The conversion should worked correctly
Attachments
No response
Screenshots or Videos

Additional Information
Can someone help me how to fix this please?

make sure that you've selected a model, upload again your audio etc. it's likely a gradio bug


Fix the build

There are methods unused in the other tree but used here.

thanks.  talked to the build team this morning.  we'll get an automated build going here one way or another.


Remove duplicate from KafkaRuntimeHints

Hey, sorry for one small PR again. I noticed one more duplicate.
KafkaListenerEndpointRegistry.class is specified above with categories that include more than one from where I removed it.
builder -> builder.withMembers(MemberCategory.INVOKE_DECLARED_CONSTRUCTORS,
								MemberCategory.INVOKE_DECLARED_METHODS,
								MemberCategory.INTROSPECT_PUBLIC_METHODS))

:) I am writing hints for Spring Cloud AWS SQS so wanted to see how it was done in Spring Kafka.

Thanks; I realize duplicates are sloppy in general but, for the most part, they are no-ops because computeIfAbsent is used when registering.
However, this one is particularly bad because it has different characteristics to the previously registered one and is effectively ignored.
Not sure why the PR build failed, possibly a flaky test.

I agree, none of this affected the code. It was more of me seeing it and couldn't resist not making PR to remove it. 😅

Thanks again; we appreciate it.


Default interface methods page is not up to date

The status on top of the page is not up to date.
Should it be removed?
Also, since the feature was actually released, there could be a link to the related page: https://docs.microsoft.com/en-us/dotnet/csharp/whats-new/csharp-8#default-interface-methods

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

ID: 17012c83-0313-919b-eb8b-04fae8f4df4a
Version Independent ID: 05252e5a-e53c-5ce5-84b3-671faad0549c
Content: Default interface methods - C# 8.0 specification proposals
Content Source: proposals/csharp-8.0/default-interface-methods.md
Product: dotnet-csharp
Technology: csharp-spec
GitHub Login: @dotnet-bot
Microsoft Alias: wiwagn

Thanks for writing this up @paolofulgoni
This page is correct. The language reflects the difference between "shipping a feature" and "updating the standard".
You are correct that default interface members shipped with C# 8.0, and is available.
We use the term "proposal" here to reflect that these features are proposed for the ECMA C# standard, but have not yet been incorporated into the standard. The standards committee will be working to update the standard using the reference implementation Microsoft provided in C# 8.
This distinction is explained here.
I'll close this as the docs accurately reflect the standardization process.

Thanks for the detailed answer.
I was a little confused by this:

But now I understood it's about the standard, not the reference implementation.


How To Ignore THIS ERRORS?????????????


Update terser-webpack-plugin to avoid terser vulnerability

Update terser-webpack-plugin to avoid terser vulnerability:

Filename: terser:5.13.1 | Reference: 1081698 | CVSS Score: 7.0 | Category: | The package terser before 4.8.1, from 5.0.0 and before 5.14.2 are vulnerable to Regular Expression Denial of Service (ReDoS) due to insecure usage of regular expressions.

This can be solved in the last terser-webpack-plugin because is in<EMAIL_ADDRESS>

@alexander-akait I have a same issue<EMAIL_ADDRESS>have dependencies on<EMAIL_ADDRESS><EMAIL_ADDRESS>have dependencies on<EMAIL_ADDRESS>terser@^5.7.2(5.10.0) has a terser vulnerability issue. Plase update dependency on terser-webpack-plugin.

The latest terser version is https://github.com/terser/terser/blob/master/package.json#L7, so run rm -rf package-lock.json node_modules && npm i

@alexander-akait
Oh, thank you. It works fine. It looks like the yarn.lock file had an older version cached.


MySQL container does not initialize on docker-compose up -d nginx mysql

$ docker-compose up -d  nginx mysql
Starting laradock_volumes_source_1
Starting laradock_volumes_data_1
laradock_workspace_1 is up-to-date
laradock_php-fpm_1 is up-to-date
laradock_nginx_1 is up-to-date

ERROR: for volumes_data  Mounts denied: er -> Preferences...
.
ib/postgres and /var/lib/redis and /var/lib/mariadb and /var/lib/mongo and /var/lib/memcached and /var/lib/mysql and /var/lib/neo4j
are not shared from OS X and do not belong to the system.
You can configure shared paths from Dock
ERROR: Encountered errors while bringing up the project.

Hi @mruzekw
Can you try updating the volumes_data container definitions in the docker-compose.yml with the below:
    volumes_data:
        build: ./volumes/data
        volumes:
            - ./data/mysql:/var/lib/mysql
            - ./data/postgres:/var/lib/postgres
            - ./data/mariadb:/var/lib/mariadb
            - ./data/memcached:/var/lib/memcached
            - ./data/redis:/data
            - ./data/neo4j:/var/lib/neo4j/data
            - ./data/mongo:/data/db

I believe this is because LaraDock will try to use system directories by default, which it can't access as  your log shows.
#138, #139, #170

Sure, I'll give this a try. I saw the other issues, but wasn't sure if it applied to this case. Thanks!


Do you have any plans to make actual release?

It would be good to mark current code base as release :)

Huh, yes. Creating corresponding tags now...

Both 1.0 and 1.1 tags have been created.

Thank you :)


[Doc] Modules Update

This pull request has automatically created by PinpointAutoBot
Updated Item : [mongodb-driver, spring-webmvc, grpc-stub] has been updated
*Updated item list may differ if this PR is updated*

Codecov Report

Merging #7082 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #7082      +/-   ##
==========================================
- Coverage   38.92%   38.90%   -0.02%
==========================================
  Files        3290     3290
  Lines       95771    95771
  Branches    11964    11964
==========================================
- Hits        37275    37263      -12
- Misses      55529    55542      +13
+ Partials     2967     2966       -1

Impacted Files
Coverage Δ

...rp/pinpoint/rpc/control/ControlMessageDecoder.java
64.28% <0.00%> (-14.29%)
:arrow_down:

...nitor/DefaultDataSourceMonitorRegistryService.java
77.77% <0.00%> (-11.12%)
:arrow_down:

.../pinpoint/rpc/client/PinpointClientHandshaker.java
60.00% <0.00%> (-6.43%)
:arrow_down:

...navercorp/pinpoint/rpc/common/SocketStateCode.java
82.92% <0.00%> (-2.44%)
:arrow_down:

...point/rpc/client/DefaultPinpointClientHandler.java
70.77% <0.00%> (-1.30%)
:arrow_down:

...pinpoint/profiler/monitor/DeadlockMonitorTask.java
18.60% <0.00%> (-1.17%)
:arrow_down:

...orp/pinpoint/rpc/server/DefaultPinpointServer.java
80.28% <0.00%> (+1.05%)
:arrow_up:

...java/com/navercorp/pinpoint/rpc/DefaultFuture.java
74.16% <0.00%> (+1.66%)
:arrow_up:

...cluster/zookeeper/ZookeeperClusterDataManager.java
54.83% <0.00%> (+1.93%)
:arrow_up:

...rc/main/java/com/navercorp/pinpoint/test/Item.java
73.33% <0.00%> (+3.33%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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


Use deps.ts and dev_deps.ts.

It is a good practice to centralise Deno dependencies within deps.ts and dev_deps.ts files.
See https://deno.land/manual/examples/manage_dependencies

Related to https://github.com/slackapi/deno-slack-builder/pull/14 and https://github.com/slackapi/deno-slack-sdk/pull/14

Requirements (place an x in each [ ])

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.

Sorry we let this get pretty stale. Totally appreciate the change, and will incorporate it. Going to close this in favor of just spinning up a new PR that does this in a bit.

No worries @selfcontained 👍
BTW, most of the PR done on the new Slack Future / Deno API were made without actually testing the features on Slack.
I already applied for the beta many months ago, and I would love to have early access  (slack ws: semalead)


Add "group by monster family" to grid/monster view

Grouping by monster/family is available in game, and I think it would be super useful here as well.  Just my $0.02

Is it available in game? I like the idea but I didn't know it was available in game. I only see Attribute, Level, Grade, Recent.

When you are going into your Storage mode, you can group by Monster/Family.

Ah, I see. I could do something like this pretty quickly.

It might also be useful if you are trying to decide which nat4's to sacrifice to the alter of legendary scroll pieces.

I really like how this turned out, thanks for the suggestion!


Wrong Tile - Application Crash

Hello all,
During my short scenario creation, I was facing an issue.
Running the scenario in editor mode ==> No problem.
Running the scenario in regular mode ==> on an event, the app crash systematically.
After digging a bit, I was running the scenario whitout including the correct extension.
Means:

In regular mode, I could start it, even I do not have the extension.
The application crash/close without message.

Maybe it could be interesting to add the extension "check" also in editor mode.
I hope this can help for the app evolution.
Mam's

I think you are saying you are using content from an expansion, and if the expansion isn't selected it will fail.  The editor always loads all content so it will work.
You have to set your expansion requirements for your scenario to prevent this.  It is possible to use components that are not from requirements, because they could be optional features, but it is up to the developer to ensure they are only used when available.
Controlling which expansions are selected in test mode is something to do later.

Its also interesting to note, that when you run the scenario from "Save and test" in the editor, it automatically enables all expansions. You can see this by opening the log (it will say BtT = 1, SoA = 1 etc).
Run th same scenario without content selected in Valkyrie and all of those variables will be 0 (or just won't be there). To get to the debug log when playing a normal game, you need to press "alt" + d.
So if you want to check that a scenario works with limited or no expansions, you will have to run it like a normal players (from the scenarios section, not the editor).

Good spot on test mode.  That is useful to know.  I've been testing content selected using the test mode!
I think would be better if the app did not crash if content is used for an expansion which has not been selected.

It's tooks me hours to understand why the app crash.
I use a BtT tile, but I do not own it.
And, when I use a regular way to load my scenario, it was possible for me.

In the folder where the Valkyrie executable is, you will find a subfolder called 'valkyrie_Data'
Inside there is the text file 'output_log.txt'
It sometimes contains relevant error messages hidden amoung the messages about assets.

That will be usefull.
Thank's

Tiles are easy to spot. You can just file the tiles by expansion (left menu when picking them). Any used will be blue.
Not sure if it crashed of you last a token or monster from an expansion not owned though. That might be trickier to find.

Closed also.
If this happen, make sure to have activated the appropriate set of tiles in the application.


Implement UI device setup

Is your feature request related to a problem? Please describe.
I have been developing another integration with more or less the same idea in mind, it would be nice to join the two in this one, and not have multiple integrations with the same purpose laying around.
Describe the solution you'd like
Add the config_flow device setup and features of ArnyminerZ/HomeAssistant-GoogleHome.
I'm working on implementing it, but there's quite a lot to adapt.

I was also building my own integration See here, until i found @leikoilja also were making. We have already decided to combine ours and i think it would be great if you would join us.

Setting up this integration works from the UI already. When you say device configurator, do you mean building a way to supply each device with an IP so we can connect to it. Homegraph does not include an IP of each device.
Please see my pull request and build up on that. So we dont do same work twice.

I meant not having to add the REST device in configuration.yaml. Adding an UI to create all the GET from GHLocalApi as sensors. But will stop working on this, since it's secondary, and start researching a "device discovery" way of getting the connected devices to the network, since I've just had an idea with the PyChromecast API.

Okay, my pull request and the integration i have build retrieves timers and alarms. The only thing that is need in that pull request i have made, is a way to retrieve an IP for each device so that It can create sensors for each device(Right now it only works for one device). There are also a couple of small things like getting the sensors to update( The API retrieves every 15 secs. But doesn't update the sensors for what ever reason)
It would be great if you could find a solution with pychromecast API
And a good idea with implementing the rest of the sensors, but I don't know if they are that useful
Sorry if I'm misunderstanding you and what you intend to do. It's great to have you onboard

Yeah, will start working on that, I find it more important than the other, see #18.
Have just made an snippet that works flawlessly, so I will keep going in that way. Still have to do some research on how discovery works on Home Assistant, but I hope it won't be such a mistery.

Nice! This looks promising. I will test and help as soon as you have something.
How do we make sure that the discovered ip correlate with the same device in homegraph?

Nice, I m happy to see us collaborating together to make the HA integration work.
@DurgNomis-drol, I have recently seen something interesting in homegraph. When glocaltoken package fetches tokens it can also extract local IP address (within your home network) from devices. We can extent glocaltoken client to fetch IPs per device together with tokens. The only problem is that those IPs are dynamic at most of the setups, but I guess we can just periodically fetch those and keep them in HA sensors together with tokens.

Nice, I m happy to see us collaborating together to make the HA integration work.
@DurgNomis-drol, I have recently seen something interesting in homegraph. When glocaltoken package fetches tokens it can also extract local IP address (within your home network) from devices. We can extent glocaltoken client to fetch IPs per device together with tokens. The only problem is that those IPs are dynamic at most of the setups, but I guess we can just periodically fetch those and keep them in HA sensors together with tokens.

I was hoping that was an option, but didn't find it 😮. Maybe I didn't find hard enough. In that case, i don't think PyChromecast is necessary, everything, even autodiscovery could be done directly with glocaltoken, which would be really convenient. Maybe opening a new issue there regarding device discovery?

See #18

This is probably not needed anymore. Feel free to reopen if otherwise


[PIP-152] Support subscription level dispatch rate limiter setting.

Motivation
See PIP-152 #15094
Modifications
See #15094
Verifying this change

[ ] Make sure that the change passes the CI checks.

This change added tests and can be verified as follows:

org.apache.pulsar.broker.admin.TopicPoliciesTest#testSubscriptionLevelDispatchRate

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (yes)
The admin cli options: (yes)
Anything that affects deployment: (no)

Documentation
Check the box below or label this PR directly.
Need to update docs?

[x] doc
Doc added in admin client api.

/pulsarbot run-failure-checks

@codelipenghui @nodece @complone PTAL

LGTM with a minor suggestion

/pulsarbot run-failure-checks

LGTM

LGTM

/pulsarbot run-failure-checks


Tried to register two views with same name DebuggingOverlay

Describe the bug
Hi,
I'm trying to create MFE application for mobile and web as well. While creating facing following issue. Anybody face this kind of issue earlier.

Thanks in advance.
System Info
React-Native 0.74.4

Re.Pack Version
4.1.1
Reproduction

Steps to reproduce

I able to resolve this issue, by just updating react-native version. In package.json, earlier we have React-native version "0.74.4". so we change it to "0.74.0".

I able to resolve this issue, by just updating react-native version. As per error, there's package which is trying different version in app. so I thought, to update react-native version. In package.json, earlier we have React-native version "0.74.4". so we change it to "0.74.0".

Sounds very plausible - when doing MFE with RN we have to align react & react-native version perfectly in order to reuse it correctly. Glad you figured that out!
Closing since the issue was resolved


User Manager Add FindByPhoneNumber

some times phone number used as identity of user it will be good enhancement to add method to
find user by Phone Number

We decided no to add this functionality to the framework


KeyError: 'MATEID'

Hi,
I'm running svtyper on the output of Delly2. Then I got these error messages:
Traceback (most recent call last):
  File "/home/work01/tools/SVTyper/svtyper/svtyper", line 1808, in <module>
    sys.exit(main())
  File "/home/work01/tools/SVTyper/svtyper/svtyper", line 1803, in main
    args.max_reads)
  File "/home/work01/tools/SVTyper/svtyper/svtyper", line 1480, in sv_genotype
    if var.info['MATEID'] in breakend_dict:
KeyError: 'MATEID'

Thanks!

I'm getting a similar KeyError, for the CIPOS field:
.. svtyper/classic.py", line 262, in sv_genotype
ciA = map(int, var.info['CIPOS'].split(','))
KeyError: 'CIPOS'
I assume that this is because my vcf has no CIPOS field -- it was generated with Sniffles, not Lumpy, as I'm trying to see if I can use svtyper to genotype variants from Illumina reads (bam file) given a vcf which was generated from long reads.
Are there certain fields which are required in the vcf such as MATEID (which is also not in my vcf) and CIPOS, and if so, is that documented somewhere?
Thanks!

You are correct in your assumptions, but there isn't a documented list.
Looking quickly through the code, it would appear that MATEID, END, CIPOS, CIEND and SVTYPE are all required.
Furthermore, the only supported variant types are BND, DEL, DUP or INV.

Thanks!


Use more extra quantization options of ONNX Runtime

Pass AddQDQPairToWeight, DedicatedQDQPair, QDQOpTypePerChannelSupportToAxis to QDQQuantizer or ONNXQuantizer, as those configuration attributes are available in QuantizationConfig but were not passed up to now.
This is useful if we later aim at using TensorrtExecutionProvider with a static quantized model.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


The segments are stored in memory

Once segments are assigned, Pinot servers get notified via Helix to “host” the segment. The servers download the segments (as a cached local copy to serve queries) and load them into local memory. All segment data is maintained in memory as long as the server hosts that segment.
I want to know which segments are permanently loaded into the memory, and whether the memory is expensive and the data volume is large

All segments of a table are divided among the tenant instances that host the table. If a server has a segment to serve, it will be loaded into memory.  You can use rest commands on the controller to see the idealstate of a table, and that will indicate to you the servers that host each segment.
It is up to you how you want to reduce cost.
You can load the segments in "HEAP" mode, you just need to make sure that the maxDirectMemory argument to the jvm is sufficiently large so that the segments are loaded without OOM errors.
You can load the segments in MMAP mode, in which case the segments are paged in from disk and Pinot lets the Operating System handle paging of segments in and out.

All segments of a table are divided among the tenant instances that host the table. If a server has a segment to serve, it will be loaded into memory. You can use rest commands on the controller to see the idealstate of a table, and that will indicate to you the servers that host each segment.
It is up to you how you want to reduce cost.
You can load the segments in "HEAP" mode, you just need to make sure that the maxDirectMemory argument to the jvm is sufficiently large so that the segments are loaded without OOM errors.
You can load the segments in MMAP mode, in which case the segments are paged in from disk and Pinot lets the Operating System handle paging of segments in and out.

If the load model changes from HEAP to MMAP, will the segments loaded into memory be released and then read data from the disk?

You can read up on MMAP here : https://en.wikipedia.org/wiki/Memory-mapped_file
A segment is MMAPed as long as the server is alive and hosts the segment. If the server is restarted, it is mmaped again.
If you want to change the load mode of segments, you can update the table config with the new load mode (MMAP), and use the controller console to reload the segment (or all segments of a table). If you do this, the direct-allocated memory will be released and the segment will now be loaded in MMAP mode.
Hope this helps.

I understanding is that when I change the table's loading mode, for example, from HEAP to MMAP, I need to disable the table first, and then enable the table, and all the segments are reloaded， the direct-allocated memory will be released and the segment will now be loaded in MMAP mode.

You do not need to disable and re-enable table for doing this.
You can change the table config from HEAP to MMAP and either reload all segments of the table or one segment at a time.
Doing it one segment at a time is better in production scenarios since the servers need to keep both versions of the segment loaded and swap the reference while serving live traffic. You can write a script to get the segments of the table and reload each one of them

Do you mean the loading segment as shown below?


Dedup Index Cache requests

Is your proposal related to a problem?

It is very common to have duplicate Index Cache requests on a single Store Gateway. For example, when opening a Grafana dashboard, multiple panels might request the same matcher, causing getting/setting the same posting/series multiple times.
Especially for those postings that has very high cardinality, downloading those data can consume a large amount of bandwidth. For example, we have posting with size over > 100 MB. When we have 10 duplicated requests we overfetch 1GB of data.
Describe the solution you'd like
Introduce https://pkg.go.dev/golang.org/x/sync/singleflight to index cache clients. For example, memcached client, redis client and even the inmemory cache client.
Describe alternatives you've considered
Implement GroupCache which provides the same SingleFlight capability. However, as a user I still want to use existing cache clients but have SingleFlight support.

cc @GiedriusS does this make sense to you?


Improved reporting of BEP runs with multiple test results

Previously a new BSP build/taskStart and build/taskFinish event was triggered with the same build identifier for each test result within a single BEP task run. The result was only showing one of the tests in the IJ test report UI.
This was encountered using the java_test_suite rule from contrib_rules_jvm which creates a Bazel test_suite wrapping many individual tests.
My solution was to track a test run from the beginning to end BEP events which seems solid. I moved tracking of event statuses into BspClientTestNotifier which feels somewhat strange, however a bunch of added state in BspServer also seemed strange. I will wait for feedback on this.
The TestReport now contains correct metrics for the number of tests executed, which was accidentally fixed by the above change. It tracks number of leaf tests, not including wrapping suites. This behavior was taken from what the IJ task report shows, not sure if suites should be included or not.

please, merge latest main into all PRs, because it includes changes that require for some of the tests on CI


update comments for TypeReference and add a method in JSON

What this PR does / why we need it?
update comments for TypeReference and add a method in JSON
Summary of your change
Please indicate you've done the following:

[ ] Made sure tests are passing and test coverage is added if needed.
[ ] Made sure commit message follow the rule of Conventional Commits specification.
[ ] Considered the docs impact and opened a new docs issue or PR with docs changes if needed.

java doc格式不对，build error

哈哈! 笔误导致!


non-ascii characters in author/title breaks recently visited on dashboard

While we're anticipating fixing these encoding issues across the system with the python 3 upgrade, we should patch the recently visited page.

@sblack-usu Do you want to verify before closing it? It should have been fixed.


parse usernameFragment

Codecov Report

Merging #35 into master will decrease coverage by 0.58%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #35      +/-   ##
==========================================
- Coverage   90.34%   89.76%   -0.59%
==========================================
  Files           1        1
  Lines         290      293       +3
==========================================
+ Hits          262      263       +1
- Misses         28       30       +2

Impacted Files
Coverage Δ

sdp.js
89.76% <100%> (-0.59%)
:arrow_down:

Continue to review full report at Codecov.

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


Remove dependency dir being set to empty string

Not sure the intention of the original, but dependency dir was being set to an empty string rather than pwd/wheel as is specified by build_wheel.sh. This resulted in failure to copy over perf_analyzer binary in setup.py

Did not see: https://github.com/triton-inference-server/model_analyzer/pull/174. Closing.


Fix read file of type gzip

Description
When reading gzip files, with utf8 encoding, files have wrong size
Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist:

My code follows the code style of this project.
If my change requires a change to the documentation I have updated the documentation accordingly.
I have read the CONTRIBUTING document.
I created an issue for the Pull Request

#266

@rkistner
Any updates on this?

I'm not a maintainer on this project, so can't help unfortunately.

@siddharthkp any updates on this?


Publish to NPM?

Since this app is designed to be developer friendly, could we get it published officially to NPM? In my experience people seem to be moving towards npm for front end stuff quite often and using stuff like babeljs to develop modularly.
Thanks! Love the library!

:+1: didn't notice that when found it today.

:+1:

Anyone can provide a PR?

Or @noelboss ?

It seems you already have a package.json (though I would argue that "main" should point at src/featherlight.js instead).
Regardless, it should be as simple as this to add an NPM package:
https://docs.npmjs.com/getting-started/publishing-npm-packages

@noelboss Would you mind publishing the last release to npm? @mikelambert the last release contains the change you mentioned.

Is to fix the issue with NPM package pointing to the gruntfile.js instead of the featherlight.min.js file?

From the GitHub history, this is indeed the fix for the incorrect value for main in packages.json.
Can this please be released to npm? This issue fundamentally breaks JSPM's ability to consume the NPM package.
Thanks!

Sorry, I thought I had. Should be done now.

Brilliant! Thank you very much! It works now.
FYI: For those who use jspm, you can reference is with "jspm install npm:featherlight"


remove flannel, default calico

default none network driver, and use calico static pod yaml to setup network

add calico operator to setup network.

done.


[may18] Add buttons from Examples\UX\Prefabs to UX\Prefabs\Buttons

Overview
The HoloToolkit-Examples package has a set of highly useful buttons in it's UX\Prefabs folder that should actually be part of the toolkit itself.
The following should be moved from examples into the toolkit for greater visibility and use:

Button
ToggleButton
Checkbox
Radial
Toggle
Slider (not technically a button :) )

These are all featured in the InteractiveButtonComponents scene, which will need to be updated as well.

@killerantz can provide insights here😄

I made some improvements to the InteractiveElements components in a side project, but the changes are breaking. There are some nicer features in the new work which I could bring over, but after speaking with @cre8ivepark I started looking at combining InteractiveElements with InteractableObjects in the examples and create a new set of components. This work is in progress as outlined here #1625. I have a rough prototype and can move what I have to a public branch, just let me know.
The work on it has slowed down over the past few weeks because of work conflicts so I don't have a timeline as of now.

Moving to vNext. Will work with @killerantz and @cre8ivepark


Can't send/receive events between two iPhones

I have three clients running: one iPhone simulator client, one physical iPhone client, and one web client. (Both iPhone clients were loaded with XCode.) I also have a rails server configured with the key, secret, and app_id.
I'm able to broadcast an event from the server to all three clients. I'm also able to broadcast from either iPhone to the web client. But for some reason, the two iPhone clients can't send/receive events from each other.
I've set up authentication and am triggering the event client-my_event to the channel private-test_channel. I can't figure out why two of the clients can't communicate with each other, when they're able to send and receive events on the same channel/event.
I'm not sure what additional information I can provide to help debug this, so let me know if you have any hunches.

Could you provide a sample project that displays this problem?
If not, please could you provide information about the specifics of the setup that produces this problem: version of Xcode, version of iOS, which device is being used to test (e.g. iPhone 7, 6S etc), which version of PusherSwift?
Thanks!

Thanks for replying so quickly Hamilton. I've set up a project here: https://github.com/dmdque/PusherClientExample
I'm using Slanger as the backend in my project, and it turns out that's the source of the problem. Once I switched to using Pusher as the backend, it worked.
I'll open an issue for the Slanger project, but if you've got any insight I'd love to hear it!
Thanks.

You could try using an older version of libPusher to see if that works.
In terms of this being an issue for this library though, I don't think it is so I'm going to close it for now 👍


Remove white space beneath widget

This is a beautifully working package. However I'd like to be able to remove the white space below the dates. I think this is probably there so the selected date can overlap, but it makes it very hard to theme when the body of the scaffold has a color value other than white.
Additionally, I'd like to be able to reduce the padding in the selected date so it does NOT overlap so much. Thanks for this awesome package.

I ended up making this package local to my project and altering the height of the appbar container and making the first child Positioned widget the same height. This fixed it for my needs.


kustomize fallback can cause version mismatch problems

From the Tilt channel:

I did not have a kustomize binary, and tilt appears to fall back on kubectl kustomize. This call failed, because kubectl (v1.17) uses kustomize v2 and is incompatible with CAPI's kustomizations, which need kustomize v3.

Currently Tilt prints:
Successfully loaded Tiltfile (6.567930778s)
Traceback (most recent call last):
  /home/dlipovetsky/projects/cluster-api/Tiltfile:217:17: in <toplevel>
  /home/dlipovetsky/projects/cluster-api/Tiltfile:205:24: in enable_providers
  /home/dlipovetsky/projects/cluster-api/Tiltfile:170:25: in enable_provider
  <builtin>: in kustomize
Error: command ["kubectl" "kustomize" "/home/dlipovetsky/projects/cluster-api/config/default"] failed.
error: exit status 1
stdout: ""
stderr: "Error: AccumulateTarget: couldn't find target apps_v1_Deployment|system|~P|controller-manager|~S for json patch\n\n\n\nExamples:\n  # Use the current working directory\n  kubectl kustomize .\n  \n  # Use some shared configuration directory\n  kubectl kustomize /home/configuration/production\n  \n  # Use a URL\n  kubectl kustomize github.com/kubernetes-sigs/kustomize.git/examples/helloWorld?ref=v1.0.6\n\nUsage:\n  kubectl kustomize <dir> [flags] [options]\n\nUse \"kubectl options\" for a list of global command-line options (applies to all commands).\n\nAccumulateTarget: couldn't find target apps_v1_Deployment|system|~P|controller-manager|~S for json patch\n\n"

And there's probably an opportunity here for better hints what's wrong. They might include:

more explicitly pointing out that we're falling back to the kubectl kustomize
adding min_version parameters to the built-in customize

adding min_version parameters to the built-in customize

It is awkward to determine the version of kustomize used by kubectl kustomize. There is no way to get the version, i.e. kubectl kustomize version is not available. So tilt would need to map kubectl to kustomize versions.
Makes we wonder if kubectl kustomize version would be generally useful...

ya, i think that's a great idea, i filed https://github.com/kubernetes/kubectl/issues/797 upstream


bytes: typo fixing

This fixes a small typo in escaped_transform! docstring.

erf, that's a typo I oftne make 😐