Using real-/full path with blade compiler exceptions

Hi. Is there a speciel reason why we are showing the full path for a blade view, when an exception occurs?
https://github.com/laravel/framework/blob/d6b96ce6b097c55b9f31bc3839938ae286de4843/src/Illuminate/View/Engines/CompilerEngine.php#L90
My issue is that I want the exception message to be unique.
But when an error happens with the full path and when using paths with timestamp/deploymentid like for example Envoyer, the path will not be unique.
Why not use the base path of the application?

I don't understand the use case. Is the full path not unique?

I don't understand the use case. Is the full path not unique?

Not in his deployment, because:

full path and when using paths with timestamp/deploymentid

I think this is more suited for laravel/ideas TBD first.

I didn't really get that part. All these paths are unique. What am I missing?
/var/www/domain.com/release-20180814-commit-ca11ab1e/
/var/www/domain.com/release-20180815-commit-b01dface/
/var/www/domain.com/release-20180815-commit-5ca1ab1e/

Yay, this is a real funny one. Indeed, OP says:

wants exception unique
paths aren't unique

When in fact, I'm pretty sure, OP means the exact opposite:

wants exception to be not unique
but paths are unique

I understood it this way automagically because I too use an external exception aggregation system which works on a few factors to group things, and error message content is one of them. And the full realpath being one of them makes each exception unique and thus not useful for aggregation.
@kasperhartwich you better confirm this or I feel stupid 😄

I added a pull request to solve this.

You're keep mixing up "unique" vs. "non-unique" that's why @sisve asked about it.
There are unique exceptions; each one is unique / different from each other:

Use of undefined constant reference - assumed 'something' (View: /var/www/domain.com/release-20180814-commit-ca11ab1e/resources/views/dashboard/index.blade.php)
Use of undefined constant reference - assumed 'something' (View: /var/www/domain.com/release-20180815-commit-b01dface/resources/views/dashboard/index.blade.php)

You want them not to be unique so you can group them. I get and support your point.

I agree. They are different from each other and that is the problem. I want them to be the same. All exception/ticket systems is looking at the exception message.
These are not unique, as they are different from eachother:

Use of undefined constant reference - assumed 'something' (View: /var/www/domain.com/release-20180814-commit-ca11ab1e/resources/views/dashboard/index.blade.php)
Use of undefined constant reference - assumed 'something' (View: /var/www/domain.com/release-20180815-commit-b01dface/resources/views/dashboard/index.blade.php)

This would be the same, so they will end on same "ticket":

Use of undefined constant reference - assumed 'something' (View: /resources/views/dashboard/index.blade.php)
Use of undefined constant reference - assumed 'something' (View: /resources/views/dashboard/index.blade.php)

Could you just override this in your app\Exceptions\Handler.php file?

I think it's best to open up an issue in https://github.com/laravel/ideas first to see how others feel about it. If you can gather support for your use case there, it could be considered.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-k8s-25-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1932

Questions ?
Please refer to the Backport tool documentation


[Feat]Group tasks by date

Is your feature request related to a problem? Please describe.
Currently, all tasks are shown in a list which could make the Home Screen cluttered.
Describe the solution you'd like
Incorporate UI changes on Home Screen to show tasks grouped by date. This could include ui elements like such or any other similar way

NOTE - this is different than filters as in filters we are trying to find tasks of a specific date but in this we are changing the way of presenting the Home Screen tasks altogether.

By date, you mean deadline date of a task or date of creation of that task?

By date, you mean deadline date of a task or date of creation of that task?
Deadline date, I don't think creation date would be much useful.


Security: Require Strong password

Inevitably, someone is going to use "password" as their password. Let's restrict this.

I'll go ahead and do this on the front-end, eventually.

I'll do this in #177 closing


Fixes pin and adds pin-off

I think the current pin icon has several issues, the style is inconsistent with the rest of the icons, it has very little visual weight, not to mention the rendering issue.
Here is my proposal to fix these issues, and maybe also add a pin-off icon while we're at it (usually when pinning stuff, unpinning/removing the pin also comes up).
Also included are 45deg versions up for discussion (for maybe including as alternate styles?).

I think I like the top version the best 👍

I agree with @lscheibel .

@ericfennis: perfect, that's what I included in the PR. 😊


Role Users function not working $admin->users();

Laravel 5.2 Has a different config/auth file for the model you just need to change
public function users()
{
return $this->belongsToMany(config('auth.model'))->withTimestamps();
}
to
public function users()
{
return $this->belongsToMany(config('auth.providers.users.model'))->withTimestamps();
}
or just add another configuration variable in your config file and use that

I would prefer the config variable approach. What do you think about this solution?

Oh, and can you specifically "tag L5.2" in the headline? ;)

Actually, there is already a pull request pending for this issue: See here #157


We need a way to iterate external sources

Issues

[X] I have checked existing issues and there are no existing ones with the same request.

Feature description
for builtins we have

print(vim.table(require("null-ls").builtins): To list all builtins.

But we don't have a way to list all external sources. One can only access them individually like

print(vim.inspect(require("none-ls.formatting.reformat_gherkin")))

But the next line will fail with error, as it is not exposed.

print(vim.inspect(require("none-ls.formatting")))

As result we have no way to iterate all external sources.
Help
No
Implementation help

We should have a list somewhere where we store all non builtin sources.
This is a requirement so we can add external source support to mason-null-ls.
We could store them like none-ls.external_sources.formatting, now that we have the concept of external sources.

I just noticed none-ls.formatting is just the root directory name of none-ls-extras.nvim, so formatting would just be the directory containing all the sources.
So as long as every external source repository has the same structure, it would be technically possible to

Iterate the directories formatting, diagnostics, etc
For every item, require it and start it.

Sadly, I've gone through the projects in https://github.com/nvimtools/none-ls-extras.nvim?tab=readme-ov-file#related-projects
and each of them have a different project structure, so this is not a reliable solution if we want to read the available sources and automatically load them.

Closed as non viable.


#17 Start developing using Storybook

Coverage remained the same at 100.0% when pulling 2a2a3161012dfb64473fd921d1371790a5497d63 on feature-17 into 2fd43feda276e751507109af80065b65f85155c7 on develop.


Lookup for service connection needs to be case insensitive

Description
Service connection created in Azure DevOps has lower case github and code is checking for GitHub

Reproduction Steps

Create service connection in Azure DevOps
Warning is shown when running generate scripts command even though the connection is there

Will push this with my PR for ado #124, just logging in case someone else comes across it.


Visualise the hidden layer in the model

It should be possible to explore the visualisation through the live data input.
First step: explore if a 2D (or 3D) representation of the latent space in NN gives any meaningful representation.
We should probably use t-SNE: https://distill.pub/2016/misread-tsne/
See this https://colah.github.io/posts/2014-10-Visualizing-MNIST/
Thought: The dimensional reduction could confuse students.

In an effort to keep our changelog history clean, I have scheduled this to version 3.1 in order to close version 2.5 before the domain objects implementation.


[BUGish] Remove ethers as project dependency

Description
ethers is responsible for a hefty 296KB of the bundle size. I think we might be able to remove it and replace it with the @ethersproject/<module> sub-modules and save a bunch of bundle space.

Proposal
Possible approach:

Run yarn analyze to get a baseline bundle size.

Grep the codebase for string from 'ethers'

Replace each import with the corresponding submodule import.
- import { constants } from 'ethers'
+ import * as constants from '@ethersproject/constants'

Remove the ethers dependency (e.g. yarn remove ethers)

Run yarn analyze again and compare.

i didn't understood the grep part?

@RishiKumarRay one way to do that is "find all" in your code editor:

@aeolianeth

getting these warnings for these sub modules

@aeolianeth  getting these warnings for these sub modules

@RishiKumarRay ah, looks like the utils is broken up across many modules. For example:
- import { utils } from 'ethers'
+ import { formatBytes32String } from '@ethersproject/strings'
// ...
- utils.formatBytes32String('')
+ formatBytes32String('')

This file might help you find which modules to import for various util functions: https://github.com/ethers-io/ethers.js/blob/master/packages/ethers/src.ts/utils.ts

@aeolianeth one more thing in some places there are two functions together then what to implement like big number and constant are together then should i write their submodule together?

@aeolianeth one more thing in some places there are two functions together then what to implement like big number and constant are together then should i write their submodule together?

@RishiKumarRay  In that case, we can import them separately:
- import { BigNumber, constants } from 'ethers'
+ import * as constants from '@ethersproject/constants'
+ import { BigNumber } from '@ethersproject/bignumber'

Is anyone still working on this issue? I'd be happy to submit a PR.

@benschac thanks for your interest! I gave this a crack in https://github.com/jbx-protocol/juice-interface/pull/639, and it looks good, although it doesn't appear to have a massive impact on chunk JS loaded (about 100kb, which is still quite good).
Going to investigate further 👍 . let me know if you have any thoughts.

Nice, I was looking at the PR and had a quick question. I'll comment there.


ms1 and ms2 tolerance

Hi,

I have a sciex qtof 7600 and orbitrap HF. How can I know the optimal ms1 and ms2 tolerance.
For qtof every time set as 0? 10ppm or 15ppm for Orbitrap?

Is there any function like DIA-NN's pipeline in window GUI? I have to run first and second search manualy every time?

Best,
Ko

Use this optimized parameter for all future search?
PROGRESS: Search parameter optimization finished. Values taken forward for search are: 2:50:50.152362 PROGRESS: ============================================== 2:50:50.152362 PROGRESS: ms2_error      : 5.3499 2:50:50.152362 PROGRESS: rt_error       : 1024.5078 2:50:50.162362 PROGRESS: ms1_error      : 9.2534 2:50:50.162362 PROGRESS: ==============================================

Hi,
if you don't know, search a triplicate with MS2=0 and MS1=0.
Then have a look at the stat.tsv table where the optimal value is reported.
You can also use the tolerance which was reported by DIA-NN.
To give you some intuition:
For ScieX 7600 I usually use 15ppm MS1 and MS2.
For the Orbitrap it depends on the transient.
I would use 15-20ppm with 30k resolution, 10ppm for 60k resulution, 5ppm for 120k resolution (mostly MS1)
Leave RT optimization always on (RT=0).
I hope this helps,
Georg


Issues with GoADropdown

The following is as of react 4.0.0-alpha.15:

The GoADropdown component does not bind to a value:
<GoADropdown name={"test"} values=["1"] onChange={() => {}}>
   <GoADropdownOption name={"test"} value={"1"} label={"1"} />
</GoADropdown>

Notice in the above, the drop down does not default any value.

GoADropdown onChange method is always passing undefined as the values argument.

GoADropdown now takes a width property, thanks!  However, the value "100%" is not working.  It currently only works with a pixel value.

Issue resolved through this work


Regex QA: intro, text edits, assert tests working.t

Pre-Submission Checklist

[x] Your pull request targets the feature/curriculum-expansion branch of FreeCodeCamp - not staging.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[ ] All new and existing tests pass the command npm run test-challenges. Use git commit --amend to amend any fixes. Tests not passing in general for the branch.

Type of Change

[x] New feature (non-breaking change which adds new functionality)

Checklist:

[x] Tested changes locally.

Description

QA for Regular expressions section. Added intro text and image. Text and formatting changes for consistency. All tests working
Visual Design - edited intro text
Responsive Web Design - swapped out a photo

@HKuz Travis has found quite a few syntax errors there (229), but they don't all seem to be coming from RegEx challenges?

@Bouncey - yes, this branch has been triggering the red X since I've started work on it. Some sections (like Basic HTML5 & CSS) with errors aren't changing much with the expansion, so I think they'll get swapped out with the latest right before this goes live. That said, I certainly don't want to be introducing issues in the sections I've worked on, and notice some of them in the report. I thought I had a linter running in Atom and it's been saying no issues, I'll need to double check that. For some of these errors, I'm not sure how to interpret them ("Unexpected token <" is coming up a lot in the seed/test-challenges.json for some challenges) - is there a good resource I can check out to better understand these?

@HKuz @Bouncey all the errors I'm getting seem to be React-specific. We can leave this PR open until their fixed, but this isn't something you need to tackle yourself. You can move on to other things :)

PR on hold.

@Bouncey, this can be merged. It's not being merged to any production or staging branch yet anyways. The curriculum expansion branch has already got syntax errors.


Fix getKB() to work with partition sizes > 1TiB

getKB() previously only understood 'G' and 'M' as postfixes of human-readable partition sizes.
Future-proofed to work for all SI prefixes up to Yottabyte (as supported by df -h).

Future-proofing, I love it. Thank you!


NIFI-3517 If HandleHttpResponse cannot write response remove entry from HttpContextMap

Add test for failure not clear context map.
Add handler to remove context map entry if ProcessException occurs during while exporting response.

Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit?

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

+1, full build with contrib check, change LGTM, merged to master.


2 3 1 manage app

SonarQube analysis reported 20 issues

 3 critical
 9 major
 5 minor
 3 info

Watch the comments in this conversation to review them.
7 extra issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 TaskList.java#L19: Make "data" transient or serializable.
 ApplicationCreationRestWorkflowExecutor.java#L318: Add the missing @deprecated Javadoc tag.
 ActivityClientFactory.java#L25: Remove this unused "subscriptionClient" private field.
 ApplicationCreationRestWorkflowExecutor.java#L147: Remove this use of "getDeploymentType"; it is deprecated.
 INTGWQueryBuilder.java#L24: Immediately return this expression instead of assigning it to the temporary variable "queryMap".
 ApplicationCreationRestWorkflowExecutor.java#L318: Do not forget to remove this deprecated code someday.
 INTGWQueryBuilder.java#L25: Complete the task associated to this TODO comment.


show nice icons for when a pod has started (but is not yet Ready - so its kinda running) and when its Terminating

we seem to only show icons for downloading and running mostly; we can probably show a few more nicer icons to give a better idea of the actual status

I've just pushed @d5e41e634c4cb245e00fee5f856f42c7253c87f4 that adds icons for the creation sequence (scheduled, pulled, created, started) as well as for the termination. Let me know your feedback on the code and the new icon set.

For the record, I gave a spin on trying to use a filter / directive for the status icon instead of embedding presentation information into the model with the $statusCss here astefanutti/hawtio-profiles@8b0d9eb05884b997b5efc32a30f55477cc3fbe8c. Let me know if that's something worth using as well.

@astefanutti Do we use sass or less? Can we just create classes in generated CSS & use a class name derived from status rather than the big old switch stuff? More efficient client side & neater imo. Does that make sense?

Yeah, we're using less in hawtio-kubernetes at least.  @astefanutti  That's still a nicer solution though with ng-switch.  Wonder if it'd be difficult to continue using the font awesome icons while also using just CSS classes for the states...

Oh sounds like a great idea. The filter would do the mapping and we could eventually get rid of the directive.
I propose that I merge @d5e41e6, if it's ok with you, so that we can get those nice status icons and I'll create a separate issue for the refactoring.

@astefanutti sounds good to me!

@astefanutti awesome thanks!


Route

Hey, I'm trying to make an entire page where people can see their notifications, not just from a popout, how do I implement this?

Under the hood, Megaphone is just using Laravels default notifications systems.
All you need to do is create a route in your application and access the notifications as described in the documentation https://laravel.com/docs/10.x/notifications#accessing-the-notifications
The only difference you should make is that when pulling the notification relationships from your model, use the "announcements()" method which is added to the model via the HasMegaphone Trait.
If you want to introduce other features like the mark as read functionality, you'll likely need to create your page as a Livewire component and duplicate some of the functionality found in the Megaphone Livewire component.


Add extensible label support on Kibana

Common labels were moved to helpers template to have only one source of truth of common/added labels shared between all Kibana resources.
Also, this extends the capability to add a custom label and this will be common between all the resources.
This is useful in many ways because it allows querying all the Kibana resources that match a common label and be used in a whole service backup with other resources outside of its chart's responsibility.

[x] Chart version not bumped (the versions are all bumped and released at the same time)
[x] README.md updated with any new values or changes
[ ] Updated template tests in ${CHART}/tests/*.py
[ ] Updated integration tests in ${CHART}/examples/*/test/goss.yaml

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

I have already signed the CLA (just after creating the PR). Is there something else that I have to do to trigger the check again?

jenkins test this please

I did a rebase because there were conflicts with the README file

jenkins test this please

jenkins test this please

backported to 6.8, 7.7and 7.x branches


Safe Links updates

Docs Build status updates of commit 42b1c69:
:clock10: Full build: the average full build time is 17 min(s) 34 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 42b1c69:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/New-SafeLinksPolicy.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/Set-AtpPolicyForO365.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/Set-SafeLinksPolicy.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit ddac3f2:
:clock10: Full build: the average full build time is 17 min(s) 33 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit ddac3f2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/New-SafeLinksPolicy.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/Set-AtpPolicyForO365.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/Set-SafeLinksPolicy.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Needs updated steps and screenshots

Looks like the UI flow and screens have changed and that makes this article hard to follow, it needs updated to reflect the new flow

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

ID: 52a30d54-41e5-425e-a015-36cfa8747a6a
Version Independent ID: ec8968fc-a232-671a-74b2-2a5f30652bb7
Content: Request an increase in vCPU quota limits per Azure VM series
Content Source: articles/azure-portal/supportability/per-vm-quota-requests.md
Service: azure-supportability
GitHub Login: @sowmyavenkat86
Microsoft Alias: svenkat

Thanks for your feedback @euangms
Assigning to content author @msftsvenkat for review and document enhancement consideration.


chore: Use json logs for production

Description
Added configurations to enable json logging for server that allows use to have structured labels for all logs coming out of server
Automation
/ok-to-test tags=""
:mag: Cypress test results

[!CAUTION]
If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[ ] No

/build-deploy-preview skip-tests=true


Make function calls to zero-arity functions explicit

There was a warning introduced in Elixir 1.4 which complained about
zero-arity function calls without parentheses roughly like the
following:

warning: variable "foo" does not exist and is beeing expanded to "foo()", please use parentheses to remove the ambiguity or change the variable name

Thanks!


Improve CI performance with xdist pytests

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. What kind of performance improvements would you like to see with this new API?
All tests currently executed on GitHub Actions work in single process. This is not optimal since even free GA workers contain 2 CPU cores, so we could speed up CI tasks at least 2x times. More speedup may be possible if we utilize our own GA workers with more CPU cores.

Windows on Ray tests fail because of Ray bug https://github.com/ray-project/ray/issues/13213

We definitely need this for Windows CI to stop randomly failing, as it now seems to be hitting timeout time and again randomly.

The timeouts are due to issues in the Dask engine, I believe. We added a timeout because the default timeout of 6 hours was always getting hit. I think there's an underlying issue that I haven't reproduced locally, but I don't think this would solve the timeout issue. cc @YarShev who worked with me to add the timeout in the first place

I was referring to timeouts in running Ray tasks, but whenever we lessen CI run time the better :)

I noticed that test_io.py when it successfully finished on windows was very close to its timeout of 20 minutes, so I increased it to 30 minutes in this fix too.


Fix dashboard to match warn states in monitors

We had a typo (and no tests)

Tested successfully with dashing outside the pipeline. Merging.


Cleanup in prep for Sprint 2

Rearranging a few things that ended up in funky places after the commit mayhem on Friday, removing things that were good for first commit but will not be useful in production.
LMK if I took something out or moved something incorrectly!

Thank you for cleaning up our repo! It looks good to me :)


Opt-in row animation

Please update the readme file, add the new parameter there.

@daniel-tabarcea ^^

@rkrupinski I just seen your PR, it is merged now and the new version of this element is available v1.0.6.
I'm sorry I didn't see it earlier :)


Generalize nc2bins

This branch adds two nc2bin python programs. One works with NSIDC sea ice concentration netCDF files (currently nsidc0051 and nsidc0081), and the other with NSIDC TB netCDF files (currently nsidc0001 and nsidc0080).

This PR is superceded by #11  and is therefore being closed as OBE


bugfix: setting custom layer overwrites exsting layers

chore: added prettierrc

@fsdavid I have made some changes to custom layers
instead of using queryparam, it now uses specific path (since it's more straight forward with the existing customRoute functionality.
now, by appending /x-overlaylayer:${encodeUriComponent('nifti://http://localhost:3000/test.nii.gz')}, one can overlay any volume on existing atlas

Should tests be fixed before the merge?

yes, I am looking into it
in the mean time, can you check the others?

Sure


"simple" vg support

Based on some ideas from @dnfield  and my own thoughts:
For very, very simple vgs : i.e. single path or stroke, we should avoid calling toImage and instead directly apply any opacity or colorblending to the encoded paint.
I had previously encountered some difficulty with this sort of conditional decoding, since we normally don't make the paths/paints accessible in an easy way. Instead perhaps we should use a different runtime structure for this sort of "simple" graphic that allows the vector graphic widget to easily blend its own opacity/colors with the paint.

And of course, this would have to be for a single path, otherwise we'd need to deal with collisions

We could have the compiler emit a field to the header with some kind of complexity score or enum

Or just a field devoted specifically to whether this graphic is worth pre rasterizing

Yeah, something like that and we decode into a slightly different runtime structure.

From some investigation, I've found that performane only improves measurable for very, very low count of path ops, less than 10 or so

From the investigation above, I think we can conclude this isn't really worth it right now, but we can come back to the above if we get a convincing use-case


Create index.html

Your pull request needs further work because of the following reason(s):

You added/changed/deleted 1 files. You can only add three (3) files index.html main.js main.css.
Your main.js file was not found, it is a requirement (even if empty)
Your main.css file was not found, it is a requirement (even if empty)

Once you have resolved the issues, comment on this request to be re-judged
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

12c0ef3169d2a42aba5a15710496ec6c8a8ccd97


What's the difference between gauges and counters?

Usually counters are used for values that always increment where as gauges are used for values that increment and decrement, such as temperature. But Java Metrics provides a decrement function on Counters. So what is the difference between gauges and counters in this case?

I, too, was very surprised when I saw the method to decrement for counter.

Let's say that a system uses a Java queue which already has a size method.
An implementer has two paths to expose the queue size as a metric:

wrap the queue and have the wrapper update a counter when objects are
queued or deqeued, or
implement a gauge that calls the size method of the queue periodically.

The second approach is vastly simpler to implement.
So in my mind, use a counter where possible in an application and use a
gauge when necessary to integrate with some existing construct in an
application.
-- Patrick
On Jan 15, 2017 7:27 AM, "Vladimir Bukhtoyarov"<EMAIL_ADDRESS>wrote:
I, too, was very surprised when I saw the method to decrement for counter.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dropwizard/metrics/issues/1043#issuecomment-272698503,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAhiCYR03sUsdCFcPE0iUpt-yUPKr8cRks5rSizkgaJpZM4Lj7Pi
.

@PatrickOsborne Why would we have to wrap the queue? we can still have a counter inside the queue and let it inc and dec? Why is a wrapper needed for the queue?

How would you add a counter to a class that is part of the JDK?  I would do
it by extending the queue or creating a new object which wraps the queue
and presents its own API.  I'd like to hear how you would approach that
problem
On Sun, Jan 15, 2017 at 5:52 PM, Mayooran Macilamany <
<EMAIL_ADDRESS>wrote:

@PatrickOsborne https://github.com/PatrickOsborne Why would we have to
wrap the queue? we can still have a counter inside the queue and let it inc
and dec? Why is a wrapper needed for the queue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dropwizard/metrics/issues/1043#issuecomment-272751780,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAhiCXOfIAmo7yj4faF49EM2TkSDfYbRks5rSr9pgaJpZM4Lj7Pi
.

Oh you mean add a counter to the queue itself. Apologies. I was thinking of having a counter in the class where the values are being added to the queue and retrieved to process. Your explanation makes sense.

A decreasing counter could be used when you start with e.g. 1000 credits and decrease by 1 for each call to a certain api.


QueryRadiusRequest: Get items in a nearest to farthest order

I got 2 questions:

Currently, the dynamodbgeo.QueryRadiusRequest gets all of the stored items that fall within the specified radius, but the returned list is not sorted in the order of nearest to farthest point starting from the dynamodbgeo.GeoPoint. It doesn't matter where the provided geopoint is, the resultset is always in the same order sorted as per the calculated geohash attribute.
Are there any plans for a feature to get the items in an order of nearest to farthest from a given point inside of a certain radius? Like in the Haversine Formaula?

Secondly, what is the mechanism of the sort order when the items are stored in the DB? The geohash gets generated from a lot of stuff going in the background, but in simple terms, in what manner is the geohash calculated from the coordinates. E.g., from north to south or something along those lines? I couldn't figure a pattern.

Great effort in building this. TIA

I too would love to see results ordered by distance!

Hey @waqas-syed,
Sorry for the late reply.

Currently, the dynamodbgeo.QueryRadiusRequest gets all of the stored items that fall within the specified radius, but the returned list is not sorted in the order of nearest to farthest point starting from the dynamodbgeo.GeoPoint. It doesn't matter where the provided geopoint is, the resultset is always in the same order sorted as per the calculated geohash attribute.
Are there any plans for a feature to get the items in an order of nearest to farthest from a given point inside of a certain radius? Like in the Haversine Formaula?

This sounds like a good feature, I'll add this, thank you for the suggestion.

Secondly, what is the mechanism of the sort order when the items are stored in the DB? The geohash gets generated from a lot of stuff going in the background, but in simple terms, in what manner is the geohash calculated from the coordinates. E.g., from north to south or something along those lines? I couldn't figure a pattern.

Just as many hashing functions, geohash doesn't perserve any order so I don't think it's possible to find a pattern in it.

Added here.


chore(docs): add build info #104

https://github.com/survivejs/webpack-merge/issues/104
In markdown 1. can used for ordered lists and markdown will do the bumbering:

foo
bar
foobar

Cool, thanks.


GUI scaling is a mess

The game doesn't display correctly at all for any GUI scale other than 1

Ah nevermind just saw #14 which this is a duplicate of


filter by run in results by suites detail

the following tests are broken / missing:

tests on the new methods in models.Suite (missing, coverage 94% on that file)
5 errors running tests inherited by tests.view.results.suites.test_views.SuiteResultsViewTest
3 tests i added but never fleshed out in tests.view.results.suites.test_views.SuiteResultsViewTest (failing)

so far, tests for views don't really make sense to me

@klrmn is this still relevant?
@peterbe / @camd - got a moment for a review?

no clue. given that almost 2 years have gone by, it's probably the thing to take the spirit without the code, rather than trying ot fix the merge conflicts.

<3 thanks @klrmn -- I apologize for missing this [by 2 years] in the noise.

It needs to be rebased against the current master. You're going to get a merge conflict to figure out.

MozTrap EOL


Create Option on Purchases Page to Filter by Specific Date Range

Summary

Diaper banks often need to filter purchases by date.  The purchases page should have the ability to be filtered by a specific date range.  For example 1/15/2018-2/3/2019

Like this example:

Filtering is an existing pattern that we use in a few places, via Filterable concern. Several of the models have existing filters at the top. Adding a new filter will require adding additional stuff to both the model (adding a scope) and the controller (adding a parameter), as well as the view (adding the form-control).
We use some of the Date Range logic in the /app/helpers/dashboard_helper -- this should probably be extracted into a separate helper that we can use in both the Dashboard and also on this page.
Ref #1093
Criteria for Completion

[x] ~Add a scope for :by_issued_at to Purchase~
[ ] Extract date range code from the app/helpers/dashboard_helper.rb out to a new helper
[ ] Add filters to the Purchase resource
[ ] Add a system spec to verify that filtering by issued_at works

Closed via #1177


Question about bloom files!

Greetings, just a small doubt, if I create and save with the -S option a bloom file for a certain public key and hexadecimal range, and I want to search now for another different public key and another hexadecimal range, is it necessary to delete the old bloom file and create a new one for the new parameters? thanks in advance

for BSGS the bloom filter is generic, it can be used with any range and any public key.


Pneumonia detection #167

Description
I had made a model that can predict whether a person has pneumonia or not by taking his X-ray as input
I made this model by using ANN(artificial neural network)
@khusheekapoor @theyashwanthsai
I had completed the issue assigned to me within the given time
So kindly check and please merge into the main branch : )
Thank You : )
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

(Add x in the [] to mark as completed.)
Related Issues or Pull Requests
#167

I had linked the link of notebook in the readme correctly , I apologize for  doing lot of mistakes as I am still new to git ,I am still learning ,I will not repeat my mistake : )
@khusheekapoor


'clrcompression.dll': The specified module could not be found. when using openxmlsdk

Unhandled Exception: System.IO.Compression.ZLibException: The underlying compression routine could not be loaded correctly. ---> System.DllNotFoundException: Unable to load DLL 'clrcompression.dll': The specified module could not be found.
at Internal.Runtime.CompilerHelpers.InteropHelpers.FixupModuleCell(InteropHelpers.ModuleFixupCell*) + 0x7f
at Internal.Runtime.CompilerHelpers.InteropHelpers.ResolvePInvokeSlow(InteropHelpers.MethodFixupCell*) + 0x1d
at Interop.zlib.InflateInit2_(ZLibNative.ZStream&, Int32) + 0x40
at System.IO.Compression.ZLibNative.ZLibStreamHandle.InflateInit2_(Int32) + 0x30
at System.IO.Compression.Inflater.InflateInit(Int32) + 0x48
--- End of inner exception stack trace ---
at System.IO.Compression.Inflater.InflateInit(Int32) + 0x1e5
at System.IO.Compression.DeflateStream.InitializeInflater(Stream, Boolean, Int32) + 0x4a
at System.IO.Compression.ZipArchiveEntry.GetDataDecompressor(Stream) + 0x45
at System.IO.Compression.ZipArchiveEntry.OpenInReadMode(Boolean) + 0x86
at System.IO.Packaging.ZipStreamManager.Open(ZipArchiveEntry, FileMode, FileAccess) + 0x108
at System.IO.Packaging.ZipPackage.ContentTypeHelper.ParseContentTypesFile(ReadOnlyCollection`1) + 0x1e
at System.IO.Packaging.ZipPackage.ContentTypeHelper..ctor(ZipArchive, FileMode, FileAccess, ZipStreamManager) + 0x88
at System.IO.Packaging.ZipPackage..ctor(String, FileMode, FileAccess, FileShare) + 0x1c3
at System.IO.Packaging.Package.Open(String, FileMode, FileAccess, FileShare) + 0x280
at DocumentFormat.OpenXml.Packaging.OpenXmlPackage.OpenCore(String, Boolean) + 0x61
at DocumentFormat.OpenXml.Packaging.SpreadsheetDocument.Open(String, Boolean, OpenSettings) + 0x1d0

This is duplicate of https://github.com/dotnet/corert/issues/5496. The last comment in that issue has a workaround that you can use for now.

@jkotas
Thanks.It is working for now.
But,Am I misunderstood with the project target " single-file executable that is easy to deploy"?

We do not have clrcompression.dll wired for the single-file compilation yet. It is a bug.


[Prefix] Restrict uploads for prefix matching IDs

This PR addresses #4379. Now on a package push/upload we have additional validation for a new package id. The package ID matching a reserved namespace will allowed to be uploaded only if it that user is the owner of the namespace, or the namespace is shared with public to upload. Also added tests.
Screenshots:
Upload flow:

Command line push:

@skofman1, @joelverhagen - addressed comments.

Addressed the feedback. @skofman1 @joelverhagen take look.
It seems there are currently broken tests in dev, holding off on resolving merge conflicts until the tests are fixed.


fix: update component name in navigator template

Please verify the following:

[ ] yarn ci:test jest tests pass with new tests, if relevant
[x] README.md has been updated with your changes, if relevant

Describe your PR
Append "Navigator" to name of navigator component in navigator template. resolves #1854
Note: I tried to run tests (used both  yarn test and yarn ci:test) right after cloning the repo but it got stuck at test/ignite-new.test.ts, so this PR is not tested :cry:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Addresses feedback on accept forward ref change

Hello! Thanks for initially raising #1658
This fix is pretty crucial for some work our team is doing so I have addressed the feedback and fixed the conflicts. I believe if we merge this into your fork, these change will be included in the PR to styled-components.

hmm this diff looks pretty strange with the rebase. The comparison here looks ok though.

Hmm well I'll try merging it and see what happens


sctp processing problem in 5.4 linux kernel

I created a sctp load-balancer rule as follows  in loxilb docker based on loxilb documentation -
root@5affc126b9e2:/# loxicmd  get lb -o wide
| EXTERNAL IP | PORT | PROTOCOL | SELECT | ENDPOINT IP | TARGET PORT | WEIGHT |
|-------------|------|----------|--------|-------------|-------------|--------|
| <IP_ADDRESS>  | 2020 | sctp     |      0 | <IP_ADDRESS>  |        5001 |      1 |
|             |      |          |        | <IP_ADDRESS>  |        5001 |      1 |
|             |      |          |        | <IP_ADDRESS>  |        5001 |      1 |

But when LB session packets are sent towards the VIP (<IP_ADDRESS>), nothing is shown in conntrack table.  However TCP rule is being processed properly.
When kernel was upgraded to 5.13. the sctp problem went away on its own. Can somebody clarify this behavior ??

Yes, in 5.4 kernel eBPF programs are unable to parse beyond IP header (if packet contains sctp). In recent kernels, due to improved eBPF support, this issue is not seen anymore.


MERC-410: Improve gallery image size

What
Use the gallery image size and also bump it up slightly to prevent blurry images
Why
The product preset is much larger than the css limited size of card images. They are never larger than 300px across all responsive widths so this appears to be an appropriate size.
Screenshots
Before

After

@sherrybc @bc-ejoe @mickr @mcampa

👍


context menu in AgGrid with popupParent

It would be nice to use the Popup Parent way to make right-click pop-up context menù from AgGrid cells as documented here:
https://www.ag-grid.com/javascript-grid-context-menu/#popup-parent
I tried just adding the grid option to this examples, but cannot make it to work:
import justpy as jp
import pandas as pd

wm_df = pd.read_csv('https://elimintz.github.io/women_majors.csv').round(2)

def row_selected(self, msg):
    print(msg)
    if msg.selected:
        self.row_data_div.text = msg.data
        self.row_selected = msg.rowIndex
    elif self.row_selected == msg.rowIndex:
        self.row_data_div.text = ''

def grid_test():
    wp = jp.WebPage()
    row_data_div = jp.Div(a=wp)
    grid = wm_df.jp.ag_grid(a=wp)
    grid.row_data_div = row_data_div
    grid.on('rowSelected', row_selected)
    grid.options.columnDefs[0].checkboxSelection = True
    grid.options.popupParent = "document.querySelector('body')"
    return wp

jp.justpy(grid_test)

neither this way:
import justpy as jp

grid_options = """
{
    defaultColDef: {
        filter: true,
        sortable: true,
        resizable: true,
        cellStyle: {textAlign: 'center'},
        headerClass: 'font-bold'
    },
      columnDefs: [
      {headerName: "Make", field: "make"},
      {headerName: "Model", field: "model"},
      {headerName: "Price", field: "price"}
    ],
      rowData: [
      {make: "Toyota", model: "Celica", price: 35000},
      {make: "Ford", model: "Mondeo", price: 32000},
      {make: "Porsche", model: "Boxter", price: 72000}
    ],
    popupParent: "document.querySelector('body')"
}
"""

def grid_test():
    wp = jp.WebPage()
    grid = jp.AgGrid(a=wp, options=grid_options)
    return wp

jp.justpy(grid_test)

The newly released version 0.1.4 supports this:
https://justpy.io/grids_tutorial/field_evaluation/
Please let me know if it works for you

great thank's, like a charm!


Failing RSpec tests on ~>7.0.0

I am setting up Knapsack Pro with gem version 7.0.0 and 7.0.1. Tests are failing with both the versions which otherwise is passing.
I am mostly getting two types of error which relates to instance_double tests and materialize-view dependent tests. Following is the error description from the runs

  1) SalesforceAppConfiguration AASM when revoked when activate with active subscription with stored auth transitions
     Failure/Error:
       allow(app_configuration).to receive(:salesforce_authentication)
                                     .and_return(instance_double(Salesforce::Authentication,
                                                                 refresh_token: 'aBc'))

       the Salesforce::Authentication class does not implement the instance method: refresh_token
     # ./spec/models/salesforce_app_configuration_spec.rb:121:in `block (7 levels) in <top (required)>'
     # ./spec/spec_helper.rb:209:in `block (2 levels) in <main>'

  2) SalesforceAppConfiguration AASM when new when activate with active subscription with stored auth transitions
     Failure/Error:
       allow(app_configuration).to receive(:salesforce_authentication)
                                     .and_return(instance_double(Salesforce::Authentication,
                                                                 refresh_token: 'aBc'))

       the Salesforce::Authentication class does not implement the instance method: refresh_token
     # ./spec/models/salesforce_app_configuration_spec.rb:63:in `block (7 levels) in <top (required)>'
     # ./spec/spec_helper.rb:209:in `block (2 levels) in <main>'
.
.
.
Finished in 3 minutes 19.4 seconds (files took 1.04 seconds to load)
888 examples, 10 failures, 1 pending

Other error:
       PG::ObjectNotInPrerequisiteState: ERROR:  materialized view "best_product_medals" has not been populated
       HINT:  Use the REFRESH MATERIALIZED VIEW command.
     # ./app/domain/medals/list.rb:47:in `map'
     # ./app/domain/medals/list.rb:47:in `wrap_medals'
     # ./app/domain/medals/list.rb:21:in `block in medals'
     # ./app/domain/medals/list.rb:21:in `each'
     # ./app/domain/medals/list.rb:21:in `flat_map'
     # ./app/domain/medals/list.rb:21:in `medals'
     # ./app/domain/vendor_admin/medals/product_medals.rb:15:in `medal_class_and_ids'
     # ./app/domain/vendor_admin/medals/product_medals.rb:9:in `exclude?'
     # ./app/models/product_reference_page_medal.rb:54:in `medal_invalid?'
     # ./spec/models/product_reference_page_medal_spec.rb:24:in `block (4 levels) in <top (required)>'
     # ./spec/spec_helper.rb:207:in `block (2 levels) in <main>'
     # ------------------
     # --- Caused by: ---
     # PG::ObjectNotInPrerequisiteState:
     #   ERROR:  materialized view "best_product_medals" has not been populated
     #   HINT:  Use the REFRESH MATERIALIZED VIEW command.
     #   ./app/domain/medals/list.rb:47:in `map'

I am trying to set it up on Github Actions with VCR/WebMosck setup. All of these tests are passing when I try it with 6.0.4.
Following is the command that I'm using to invoke the test in GHA runner bundle exec rake "knapsack_pro:queue:rspec[--require packs/rails/rspec --require spec_helper --order rand --require fivemat --format Fivemat --format RSpec::Github::Formatter --format RspecJunitFormatter --out report/ruby-rspec-${{ matrix.node_index }}.xml]"

Could you prepare an integration test like this one to help us reproduce an issue?
Or it could be a new Rails app that we could use to debug it?
Thank you.

Hi @ArturT do you mean something like https://github.com/KnapsackPro/knapsack_pro-ruby/pull/247/files ?

@GeoffTidey Yes.
I've run this test and it's passing successful.
➜  knapsack_pro-ruby git:(pr/247) rspec spec/integration/runners/queue/rspec_runner_spec.rb:382
Resolving dependencies...
Run options: include {:locations=>{"./spec/integration/runners/queue/rspec_runner_spec.rb"=>[382]}}

Randomized with seed 65516

KnapsackPro::Runners::Queue::RSpecRunner - Integration tests
  when rails_helper file exists
    requires the rails_helper file when running RSpec and runs hooks defined within it

Finished in 0.2351 seconds (files took 0.42629 seconds to load)
1 example, 0 failures

Randomized with seed 65516

We need to prepare a test that would fail with the same error as you see in your project. Then we could prepare a fix for that.
Are you able to identify what is causing the error in your project?

Afraid not.  It's intermittent.

Hi @ArturT , sorry for the radio silence.  It's not been happening at all since my last update.  Two things have changed, the first is probably the issue:

I moved the KnapsackPro::Adapters::RSpecAdapter.bind to spec/spec_helper.rb (it was perviously in another helper that is only loaded for system tests),
the other is we're now using GitHub Actions for CI, rather than Heroku CI.

@GeoffTidey Thank you for providing solution to your issue.
@AnkeshThakur Could you ensure KnapsackPro::Adapters::RSpecAdapter.bind is in spec/spec_helper.rb?
You could also update the knapsack_pro gem to the latest version. We released a couple of improvements.
I'd appreciate an update from you. If it's no longer a relevant issue, please let me know.

@ArturT apology for silence. I'm no longer integrating KnapsackPro. For me older version (<7.0.0) worked without issue.
I have not updated it to later version to check if 7+ versions are working or not.


Update deployment document to fit what's in beta release

Fixes #106
cc @bgrant0607 @amygdala @kargakis @pwittrock @kubernetes/sig-config

We changed A LOT in 1.2. @janetkuo Could you please read this over and check what else should be updated? We don't have any user docs for your new kubectl commands, for instance.

The status is all out of date, also

And Deployment manages ReplicaSets instead of RCs.
Etc.

Updated. PTAL @bgrant0607 @kargakis @madhusudancs

This is a huge improvement, so I'm going to merge it and we can do a followup PR to do more.
Thanks!
LGTM

In the future, please make sure you do not use "console" but instead use "shell" to ensure proper syntax highlighting. For a list of valid values, see the list of Rouge lexers:
https://github.com/jneen/rouge/wiki/list-of-supported-languages-and-lexers
(Console ain't on it)

@johndmulhausen I believe "console" is supported here http://tinker.kotaweaver.com/blog/?p=152, it's used for bash sessions. I only use "console" for console interaction (input starts with $ vs. output) but not for shell scripts.
console separates input commands from demo output:
$ kubectl get rs
NAME                          DESIRED   CURRENT   AGE
nginx-deployment-1564180365   2         2         25s
nginx-deployment-2035384211   0         0         36s
nginx-deployment-3066724191   2         2         6s

But shell doesn't (and the output of "kubectl get rs" isn't shell script)
$ kubectl get rs
NAME                          DESIRED   CURRENT   AGE
nginx-deployment-1564180365   2         2         25s
nginx-deployment-2035384211   0         0         36s
nginx-deployment-3066724191   2         2         6s

@johndmulhausen oh, I see that we're using "rouge" as syntax highlighter.

@janetkuo Yes, that's changed vs. what we used to use.


Merge develop into master

The Condor-CLI merge is inbound and will make this PR pretty much obsolete. Deleting it.


Resolve colliding file names on case-insensitive file systems

Resolves #7837.
Signed-off-by: Sebastian Schuberth<EMAIL_ADDRESS>

Closing per https://github.com/clearlydefined/curated-data/issues/7837#issuecomment-719905197


Add the packaging metadata to build the nanocoin snap

This package will let you publish the latest nanocoin in the Ubuntu store, and from there reach many users on all the supported Ubuntu versions, and more Linux distributions in progress. You just have to go to https://build.snapcraft.io and enable the automated continuous delivery.

Hello @tdietert!
Here at ubuntu we are working in a new packaging system. And I'm starting to experiment with haskell projects. I used quorum as the first test subject, and that lead me to your project which is very interesting. I think it will be useful for you to find new contributors from Ubuntu, and for us in Ubuntu it will be really nice to learn more about cryptocurrencies.
And in addition to that, this will help us test if our system is good enough for haskell programmers. Any feedback you can give us will be very appreciated, and we will use it to guide our next sprints.
pura vida

@tdietert oh, sorry, I missed your message.
The idea of the snap store is to give control to upstream about when and how they release their software to Linux. After maintaining the ubuntu archive for over 10 years, we learned the shortcomings and we are fixing them here. In order to do this, the system needs to be super secure, which we achieve with the confinement: strict that you will see in the snapcraft.yaml file, using apparmor and seccomp to isolate your application. The result is that people can start trying nanocoin with a single command: sudo snap install nanocoin, making it even easier to start learning about cryptocurrencies with your project.


build iOS error in Mac

Plugin Version or Commit ID
lasted
Unity Version

Your Host OS
Mac OS 11.1
Target Platform
iOS
[Windows Only] Visual Studio C++ and Windows SDK Version
No response
[Linux Only] GCC/G++ and GLIBC Version
No response
[Android Only] Android Build Tools and NDK Version
No response
[iOS Only] XCode Version
No response
Command Sequences
after 5 month I try again to build an iOS for my project
in the previous test I haven't any error in run Python commands
but today I got this error
can you help me what is reason of this error
Log
DEBUG (build.py): Copying '.nuget/System.Buffers.4.4.0/lib/netstandard2.0/System.Buffers.dll' to 'build/Plugins/Protobuf/System.Buffers.dll'...
DEBUG (build.py): Creating 'build/Plugins/Protobuf'...
DEBUG (build.py): Changing the mode of 'build/Plugins/Protobuf/System.Buffers.dll'...
DEBUG (build.py): Copying '.nuget/Google.Protobuf.3.20.0/lib/netstandard2.0/Google.Protobuf.dll' to 'build/Plugins/Protobuf/Google.Protobuf.dll'...
DEBUG (build.py): Changing the mode of 'build/Plugins/Protobuf/Google.Protobuf.dll'...
DEBUG (build.py): Copying '.nuget/System.Runtime.CompilerServices.Unsafe.4.5.2/lib/netstandard2.0/System.Runtime.CompilerServices.Unsafe.dll' to 'build/Plugins/Protobuf/System.Runtime.CompilerServices.Unsafe.dll'...
DEBUG (build.py): Changing the mode of 'build/Plugins/Protobuf/System.Runtime.CompilerServices.Unsafe.dll'...
DEBUG (build.py): Copying '.nuget/System.Memory.4.5.3/lib/netstandard2.0/System.Memory.dll' to 'build/Plugins/Protobuf/System.Memory.dll'...
DEBUG (build.py): Changing the mode of 'build/Plugins/Protobuf/System.Memory.dll'...
INFO (build.py): Downloaded protobuf dlls
INFO (build.py): Building resource files
DEBUG (build.py): Running `bazel build -c opt --verbose_failures //mediapipe_api:mediapipe_assets`
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/tensorflow/runtime/archive/2f6de37d68a4c69e2ff9eec3cebbf1369e496940.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'com_google_benchmark' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'pybind11_bazel' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'com_google_protobuf' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'com_google_googletest' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'com_github_gflags_gflags' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'rules_python' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'build_bazel_rules_apple' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'build_bazel_rules_swift' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'build_bazel_apple_support' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'xctestrunner' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'pybind11' because it already exists.
DEBUG: Rule 'rules_cc' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "73106859751c2bc314861adc136d5cbecee3f7ae7d05539dc8235efbf4efdcbe"
DEBUG: Repository rules_cc instantiated at:
  /Users/admin/Downloads/MediaPipeUnityPlugin-master-2/WORKSPACE:90:13: in <toplevel>
Repository rule http_archive defined at:
  /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/bazel_tools/tools/build_defs/repo/http.bzl:353:31: in <toplevel>
INFO: Analyzed target //mediapipe_api:mediapipe_assets (11 packages loaded, 54 targets configured).
INFO: Found 1 target...
Target //mediapipe_api:mediapipe_assets up-to-date:
  bazel-bin/mediapipe_api/mediapipe_assets.zip
INFO: Elapsed time: 22.977s, Critical Path: 17.18s
INFO: 28 processes: 2 internal, 26 darwin-sandbox.
INFO: Build completed successfully, 28 total actions
DEBUG (build.py): Unarchiving 'bazel-bin/mediapipe_api/mediapipe_assets.zip' to 'build/Resources'...
DEBUG (build.py): Unarchiving 'bazel-bin/mediapipe_api/mediapipe_assets.zip' to 'Assets/StreamingAssets'...
INFO (build.py): Built resource files
INFO (build.py): Building native libraries for Desktop...
DEBUG (build.py): Running `bazel build -c opt --verbose_failures --define MEDIAPIPE_DISABLE_GPU=1 --@opencv//:switch=local //mediapipe_api:mediapipe_desktop`
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/tensorflow/runtime/archive/2f6de37d68a4c69e2ff9eec3cebbf1369e496940.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'com_google_benchmark' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'pybind11_bazel' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'com_google_protobuf' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'com_google_googletest' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'com_github_gflags_gflags' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'rules_python' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'build_bazel_rules_apple' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'build_bazel_rules_swift' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'build_bazel_apple_support' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'xctestrunner' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'pybind11' because it already exists.
INFO: Build option --define has changed, discarding analysis cache.
DEBUG: Rule 'rules_cc' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "73106859751c2bc314861adc136d5cbecee3f7ae7d05539dc8235efbf4efdcbe"
DEBUG: Repository rules_cc instantiated at:
  /Users/admin/Downloads/MediaPipeUnityPlugin-master-2/WORKSPACE:90:13: in <toplevel>
Repository rule http_archive defined at:
  /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/bazel_tools/tools/build_defs/repo/http.bzl:353:31: in <toplevel>
WARNING: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/com_google_mediapipe/mediapipe/framework/BUILD:54:24: in cc_library rule @com_google_mediapipe//mediapipe/framework:calculator_cc_proto: target '@com_google_mediapipe//mediapipe/framework:calculator_cc_proto' depends on deprecated target '@com_google_protobuf//:cc_wkt_protos': Only for backward compatibility. Do not use.
WARNING: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/com_google_mediapipe/mediapipe/framework/tool/BUILD:184:24: in cc_library rule @com_google_mediapipe//mediapipe/framework/tool:field_data_cc_proto: target '@com_google_mediapipe//mediapipe/framework/tool:field_data_cc_proto' depends on deprecated target '@com_google_protobuf//:cc_wkt_protos': Only for backward compatibility. Do not use.
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/google/XNNPACK/archive/a0ec971de0dc82e0bf8784393cb8c4a56c171045.zip failed: class java.io.FileNotFoundException GET returned 404 Not Found
INFO: Analyzed target //mediapipe_api:mediapipe_desktop (106 packages loaded, 7799 targets configured).
INFO: Found 1 target...
INFO: From Compiling src/raw_logging.cc [for host]:
external/com_github_glog_glog/src/raw_logging.cc:139:3: warning: 'syscall' is deprecated: first deprecated in macOS 10.12 - syscall(2) is unsupported; please switch to a supported interface. For SYS_kdebug_trace use kdebug_signpost(). [-Wdeprecated-declarations]
  safe_write(STDERR_FILENO, buffer, strlen(buffer));
  ^
external/com_github_glog_glog/src/raw_logging.cc:63:34: note: expanded from macro 'safe_write'
# define safe_write(fd, s, len)  syscall(SYS_write, fd, s, len)
                                 ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/unistd.h:742:6: note: 'syscall' has been explicitly marked deprecated here
int      syscall(int, ...);
         ^
1 warning generated.
INFO: From Compiling src/utilities.cc [for host]:
external/com_github_glog_glog/src/utilities.cc:251:17: warning: 'syscall' is deprecated: first deprecated in macOS 10.12 - syscall(2) is unsupported; please switch to a supported interface. For SYS_kdebug_trace use kdebug_signpost(). [-Wdeprecated-declarations]
    pid_t tid = syscall(__NR_gettid);
                ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk/usr/include/unistd.h:742:6: note: 'syscall' has been explicitly marked deprecated here
int      syscall(int, ...);
         ^
1 warning generated.
INFO: From Compiling mediapipe/framework/deps/ret_check.cc [for host]:
In file included from external/com_google_mediapipe/mediapipe/framework/deps/ret_check.cc:15:
In file included from external/com_google_mediapipe/mediapipe/framework/deps/ret_check.h:19:
external/com_google_mediapipe/mediapipe/framework/deps/status_builder.h:95:12: warning: 'Status' is deprecated: Use absl::Status directly [-Wdeprecated-declarations]
  operator Status() const&;
           ^
external/com_google_mediapipe/mediapipe/framework/deps/status.h:30:14: note: 'Status' has been explicitly marked deprecated here
using Status ABSL_DEPRECATED("Use absl::Status directly") = absl::Status;
             ^
external/com_google_absl/absl/base/attributes.h:648:49: note: expanded from macro 'ABSL_DEPRECATED'
#define ABSL_DEPRECATED(message) __attribute__((deprecated(message)))
                                                ^
In file included from external/com_google_mediapipe/mediapipe/framework/deps/ret_check.cc:15:
In file included from external/com_google_mediapipe/mediapipe/framework/deps/ret_check.h:19:
external/com_google_mediapipe/mediapipe/framework/deps/status_builder.h:96:12: warning: 'Status' is deprecated: Use absl::Status directly [-Wdeprecated-declarations]
  operator Status() &&;
           ^
external/com_google_mediapipe/mediapipe/framework/deps/status.h:30:14: note: 'Status' has been explicitly marked deprecated here
using Status ABSL_DEPRECATED("Use absl::Status directly") = absl::Status;
             ^
external/com_google_absl/absl/base/attributes.h:648:49: note: expanded from macro 'ABSL_DEPRECATED'
#define ABSL_DEPRECATED(message) __attribute__((deprecated(message)))
                                                ^
2 warnings generated.
INFO: From Compiling mediapipe/framework/tool/text_to_binary_graph.cc [for host]:
In file included from external/com_google_mediapipe/mediapipe/framework/tool/text_to_binary_graph.cc:27:
In file included from external/com_google_mediapipe/mediapipe/framework/port/ret_check.h:18:
In file included from external/com_google_mediapipe/mediapipe/framework/deps/ret_check.h:19:
external/com_google_mediapipe/mediapipe/framework/deps/status_builder.h:95:12: warning: 'Status' is deprecated: Use absl::Status directly [-Wdeprecated-declarations]
  operator Status() const&;
           ^
external/com_google_mediapipe/mediapipe/framework/deps/status.h:30:14: note: 'Status' has been explicitly marked deprecated here
using Status ABSL_DEPRECATED("Use absl::Status directly") = absl::Status;
             ^
external/com_google_absl/absl/base/attributes.h:648:49: note: expanded from macro 'ABSL_DEPRECATED'
#define ABSL_DEPRECATED(message) __attribute__((deprecated(message)))
                                                ^
In file included from external/com_google_mediapipe/mediapipe/framework/tool/text_to_binary_graph.cc:27:
In file included from external/com_google_mediapipe/mediapipe/framework/port/ret_check.h:18:
In file included from external/com_google_mediapipe/mediapipe/framework/deps/ret_check.h:19:
external/com_google_mediapipe/mediapipe/framework/deps/status_builder.h:96:12: warning: 'Status' is deprecated: Use absl::Status directly [-Wdeprecated-declarations]
  operator Status() &&;
           ^
external/com_google_mediapipe/mediapipe/framework/deps/status.h:30:14: note: 'Status' has been explicitly marked deprecated here
using Status ABSL_DEPRECATED("Use absl::Status directly") = absl::Status;
             ^
external/com_google_absl/absl/base/attributes.h:648:49: note: expanded from macro 'ABSL_DEPRECATED'
#define ABSL_DEPRECATED(message) __attribute__((deprecated(message)))
                                                ^
2 warnings generated.
INFO: From Compiling mediapipe/framework/deps/status_builder.cc [for host]:
In file included from external/com_google_mediapipe/mediapipe/framework/deps/status_builder.cc:15:
external/com_google_mediapipe/mediapipe/framework/deps/status_builder.h:95:12: warning: 'Status' is deprecated: Use absl::Status directly [-Wdeprecated-declarations]
  operator Status() const&;
           ^
external/com_google_mediapipe/mediapipe/framework/deps/status.h:30:14: note: 'Status' has been explicitly marked deprecated here
using Status ABSL_DEPRECATED("Use absl::Status directly") = absl::Status;
             ^
external/com_google_absl/absl/base/attributes.h:648:49: note: expanded from macro 'ABSL_DEPRECATED'
#define ABSL_DEPRECATED(message) __attribute__((deprecated(message)))
                                                ^
In file included from external/com_google_mediapipe/mediapipe/framework/deps/status_builder.cc:15:
external/com_google_mediapipe/mediapipe/framework/deps/status_builder.h:96:12: warning: 'Status' is deprecated: Use absl::Status directly [-Wdeprecated-declarations]
  operator Status() &&;
           ^
external/com_google_mediapipe/mediapipe/framework/deps/status.h:30:14: note: 'Status' has been explicitly marked deprecated here
using Status ABSL_DEPRECATED("Use absl::Status directly") = absl::Status;
             ^
external/com_google_absl/absl/base/attributes.h:648:49: note: expanded from macro 'ABSL_DEPRECATED'
#define ABSL_DEPRECATED(message) __attribute__((deprecated(message)))
                                                ^
external/com_google_mediapipe/mediapipe/framework/deps/status_builder.cc:72:25: warning: 'Status' is deprecated: Use absl::Status directly [-Wdeprecated-declarations]
StatusBuilder::operator Status() const& {
                        ^
external/com_google_mediapipe/mediapipe/framework/deps/status.h:30:14: note: 'Status' has been explicitly marked deprecated here
using Status ABSL_DEPRECATED("Use absl::Status directly") = absl::Status;
             ^
external/com_google_absl/absl/base/attributes.h:648:49: note: expanded from macro 'ABSL_DEPRECATED'
#define ABSL_DEPRECATED(message) __attribute__((deprecated(message)))
                                                ^
external/com_google_mediapipe/mediapipe/framework/deps/status_builder.cc:79:25: warning: 'Status' is deprecated: Use absl::Status directly [-Wdeprecated-declarations]
StatusBuilder::operator Status() && {
                        ^
external/com_google_mediapipe/mediapipe/framework/deps/status.h:30:14: note: 'Status' has been explicitly marked deprecated here
using Status ABSL_DEPRECATED("Use absl::Status directly") = absl::Status;
             ^
external/com_google_absl/absl/base/attributes.h:648:49: note: expanded from macro 'ABSL_DEPRECATED'
#define ABSL_DEPRECATED(message) __attribute__((deprecated(message)))
                                                ^
external/com_google_mediapipe/mediapipe/framework/deps/status_builder.cc:100:10: warning: 'Status' is deprecated: Use absl::Status directly [-Wdeprecated-declarations]
  return Status(status_.code(), message);
         ^
external/com_google_mediapipe/mediapipe/framework/deps/status.h:30:14: note: 'Status' has been explicitly marked deprecated here
using Status ABSL_DEPRECATED("Use absl::Status directly") = absl::Status;
             ^
external/com_google_absl/absl/base/attributes.h:648:49: note: expanded from macro 'ABSL_DEPRECATED'
#define ABSL_DEPRECATED(message) __attribute__((deprecated(message)))
                                                ^
5 warnings generated.
Target //mediapipe_api:mediapipe_desktop up-to-date:
  bazel-bin/mediapipe_api/mediapipe_desktop.zip
INFO: Elapsed time: 5830.982s, Critical Path: 2365.50s
INFO: 3719 processes: 1137 internal, 2582 darwin-sandbox.
INFO: Build completed successfully, 3719 total actions
DEBUG (build.py): Unarchiving 'bazel-bin/mediapipe_api/mediapipe_desktop.zip' to 'build/Plugins'...
INFO (build.py): Built native libraries for Desktop
INFO (build.py): Building native libraries for Android...
DEBUG (build.py): Running `bazel build -c opt --verbose_failures --config=android_arm64 --java_runtime_version=remotejdk_11 //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android`
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/tensorflow/runtime/archive/2f6de37d68a4c69e2ff9eec3cebbf1369e496940.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'com_google_benchmark' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'pybind11_bazel' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'com_google_protobuf' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'com_google_googletest' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'com_github_gflags_gflags' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'rules_python' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'build_bazel_rules_apple' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'build_bazel_rules_swift' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'build_bazel_apple_support' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'xctestrunner' because it already exists.
DEBUG: /private/var/tmp/_bazel_admin/38dff6c5b36768738c2afb113c06f5d6/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'pybind11' because it already exists.
INFO: Build options --cpu, --crosstool_top, --define, and 4 more have changed, discarding analysis cache.
ERROR: /Users/admin/Downloads/MediaPipeUnityPlugin-master-2/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:10:14: While resolving toolchains for target //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: no matching toolchains found for types @bazel_tools//tools/android:sdk_toolchain_type
ERROR: Analysis of target '//mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android' failed; build aborted:
INFO: Elapsed time: 4.590s
INFO: 0 processes.

Additional Context
No response

after 5 month I try again to build an iOS for my project

Pull the latest commit, please.
If the problem still occurs with it, please reopen it.

hello
i check the last commit its works without error
but
in the xcode build i have an error that say the bundle id must be unique
i think you forget to add ".mediapipeunity" at end of
mediapipe_api/objc/BUILD
i remember  in the old version in the end of the bundle_id  we have an .MEDIUAPIPEUNITY or a text like it
but in the new version it was deleted
do you think is this reason to i got this error ?


KL430 support

Hi,
Does this plugin support the Kasa KL430 smart Light Strip?
The 'Tplink Smarthome' plugin for HOOBS doesn't support the light strip and work on that plugin seems to be at a crawl. Any chance this plugin will support it?
Cheers!

Hey, sorry for the late response, I am not sure, I don't have a KL430 to test with, you can clone the project and test it, and if it not supported, maybe you can write a PR which can add support for that.

Hey @alexneth i have a RGBIC Strip from tapo L920 which works with no problems


Resurrect the Shared View example

The previous example was lost as a result of https://github.com/openlayers/openlayers/commit/7fa2189fe997a87f28e9551242a71e1da211e5cc#diff-bfebe34154a0dfd9fc7b447fc9ed74e9  Obviously WebGL is no longer applicable but a side by side example of the use of a shared view such as for road and aerial would be useful.

Can you come up with a PR, that'd be awesome.


Resolve Any environment types before optimization.

This allows us to correctly inspect environment capabilities during optimization, etc.
This should fix #28972

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

Let me add a cherry-pick PR for this to fix permared postcommit on release branch


RDSInstance is in synced:false state because Cannot upgrade postgres from 12.7 to 12.5

What happened?
We are using crossplane to manage our RDSInstances in AWS. We use argo-cd to get the objects synced. Now when we deployed RDSInstance in crossplane we used posgres engineVersion: 12 and (autoMinorVersionUpgrade: true) we didn't mention this value because according to the documetation, its default value is true,  so the expected behaviour is, it will upgrade the RDS to the latest available minor version. But after upgrading, crossplane replaced engineVersion with 12.5 which is the version on which the RDS instance was initially on. We are unable to pinpoint why crossplane is trying to downgrade the instance version.
P.S. - I don't think crossplane should update the minor-version in spec. That might cause unnecessary reconciliations
How can we reproduce it?
apiVersion: database.aws.crossplane.io/v1beta1
kind: RDSInstance
metadata:
  name: some-rdsinstance
spec:
  deletionPolicy: Orphan
  forProvider:
    allocatedStorage: 100
    availabilityZone: us-west-2b
    backupRetentionPeriod: 7
    dbInstanceClass: db.m5.large
    dbParameterGroupName: default
    dbSubnetGroupName: XXXX-XXXX-XXXX
    deletionProtection: true
    enablePerformanceInsights: true
    engine: postgres
    engineVersion: '12'
    masterUsername: master_user
    multiAZ: false
    performanceInsightsRetentionPeriod: 7
    preferredBackupWindow: '06:21-06:51'
    preferredMaintenanceWindow: 'mon:00:00-mon:01:00'
    publiclyAccessible: true
    region: us-west-2
    storageEncrypted: true
    storageType: gp2
    tags:
      - key: crossplane-kind
        value: rdsinstance.database.aws.crossplane.io
      - key: crossplane-name
        value: master-postgres-instance
      - key: crossplane-providerconfig
        value: default
    vpcSecurityGroupIds:
      - XXXX-XXXX
  providerConfigRef:
    name: default
  writeConnectionSecretToRef:
    name: master.rds-admin-connection
    namespace: master

What environment did it happen in?
Crossplane version:  crossplane-1.3.1
Kubernetes version: v1.19.7

I agree with @shubhindia... When you specify engineVersion: '12', you're pretty much saying not to check the minor version and let AWS take care of the minor for you.

https://github.com/crossplane/provider-aws/blob/988e66c6befcb6b6e7ce575d56f8254683aa442b/pkg/clients/rds/rds.go#L440-L445
I think we have to either

Avoid this code in late init, but do something similar in IsUpToDate
Fix isUpToDate so it returns true for minor upgrades, like 12.5 vs 12.7, if autoMinorVersionUpgrade is set
or
Also allow late init 12.5 -> 12.7  if autoMinorVersionUpgrade. But at this point spec becomes like status so I don't think this is a good idea?

I think fixing isUpToDate would be a better idea. Or maybe set the actual version in status and refer it for future operations. We might need to change this as well https://github.com/crossplane/provider-aws/blob/master/apis/database/v1beta1/rdsinstance_types.go#L1101

In terraform this was solved for and  if auto_minor_version_upgrade is enabled, you can provide a prefix of the version such as 5.7 (for 5.7.10). The actual engine version used is returned in the attribute engine_version_actual.


Schema doesn't respect Object

We are trying to work with schemas.
It appears that it sends any king of object, regardless of schema set.
For example, it will send your initial Person Object from the example without any errors.
The only thing it checks is schema itself, it must be valid (that's okay).
Is there any option to validate an object before send?
thanks

@djdance
Yes, schemas can send any object to pulsar without validating the object options, but it must meet this one requirement, the object must be able to json_encode, however json_encode will only extract public properties, so as long as the object can successfully json_encode it will be sent successfully, the same goes for the consumer, when it receives When the json data is received, it will be converted to the corresponding object, and there is no need to manually convert it to an object, which saves us a lot of conversion work

example

class Person
{
    public $id;
    public $name;
    public $age;

    protected $test = 'ignore';
    // ...
}

$person = new Person();
$person->id = 1;
$person->name = 'Tony';
$person->age = 1;

echo json_encode($person);

// output：{"id":1,"name":"Tony","age":1}

$producer->send($person);   // The actual message sent is `{"id":1,"name":"Tony ","age":1}`

got it.
Would you plan to add some kind of validation to Object sending?
as in appropriate Java library (they say)

I don't know what verification there is in the java library, can you tell me in detail?

I am not so familiar with this java realization, but apparently this is here
https://github.com/spring-projects-experimental/spring-pulsar/blob/488c5d2e64294009453611d83884321fe228b834/spring-pulsar/src/main/java/org/springframework/pulsar/core/DefaultSchemaResolver.java#L159


add module.exports = nextConfig to next.config.js

I had to add
module.exports = nextConfig
to the bottom of the next.config.js file in order to get the demo app to work. Otherwise, it threw the no exported configuration found error in the terminal and a runtime error in the DOM

Hey thanks for reporting.
I'm not sure how you encountered this issue, as the module.exports = nextConfig line you mentioned is present in the file and has been for some time.
I'm going to go ahead and close this, but please let me know if I'm missing something.


[HUDI-5976] Add fs in the constructor of HoodieAvroHFileReader

Change Logs
Fixes https://github.com/apache/hudi/issues/8257
After hbase 2.4.13, the constructor of ReaderContext has changed, and a configuration needs to be fetched through hfs,
But currently hudi will pass hfs as null, which will cause NPE
hbase 2.4.13+:
https://github.com/apache/hbase/blob/90fb1ddc1df9b345f26687d5d24cedfb19621d63/hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/ReaderContext.java#L53
hbase 2.4.9: (hudi use)
https://github.com/apache/hbase/blob/c49f7f63fca144765bf7c2da41791769286dfccc/hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/ReaderContext.java#L50
Impact
Avoid potential risk of NPE caused by upgrading hbase in the future
Risk level (write none, low medium or high below)
low
Documentation Update
None
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@Zouxxyy Looks like there is a checkstyle violation. Can you please correct? https://github.com/apache/hudi/actions/runs/4509620758/jobs/7944047354?pr=8277

done

@codope hi, CI is green

Hi @Zouxxyy HBase dependencies are shaded in Hudi so Hudi always uses the shaded version based on HBase 2.4.9.  Could you clarify why Hbase 2.4.13+ fails Hudi in this case?

Hi @Zouxxyy HBase dependencies are shaded in Hudi so Hudi always uses the shaded version based on HBase 2.4.9. Could you clarify why Hbase 2.4.13+ fails Hudi in this case?

In https://github.com/apache/hudi/issues/8257, user manually modified the version of hbase, and then compiled his own package


want to make a blog archive by category, posts listed in a grid

[x] This is a question about using the theme.
[ ] This is a feature request.
[ ] I have updated all gems with bundle update.
[ ] I have tested locally with bundle exec jekyll build.
[ ] I believe this to be a bug with the theme --- not Jekyll, GitHub Pages or one of the bundled plugins.

Environment informations

Minimal Mistakes version: 4.4.1
github-pages or jekyll gem version: github-pages in browser
Operating system: windows

Expected behavior

An archive page with headers for each category, with posts listed in grid view beneath each header.
Steps to reproduce the behavior

Here is the file and repository: https://github.com/everymind/SurprisingMinds/blob/gh-pages/_pages/blog-archive.html
It almost does it -- the category headers are just floating at the top of the page, instead of with their respective posts. The posts themselves seem to have filtered correctly, and are displaying in a grid more or less how I want them. But I can't figure out how to get the headers to go in the right place.

I've tried moving around the location of the grid__wrapper div, but I suspect I need to change something else, perhaps something in a css file? Apologies if this is super obvious, any tips much appreciated!

This one might be tricky to get right. The grid items use nth-child selectors to float and clear floats at various breakpoints.
Depending on where you inject the category headings it might be viewed as a child element and that could explain the overlapping. You'll most likely need to add some
 or other wrappers to combat the nth-child CSS so it only applies to the grid items and not the headings. Then make sure the headings clear any floats.
The relevant CSS is all in _archive.scss if you want to get a feel for what's going on.

Hi, thanks for the prompt reply!
I'm looking at _archive.scss, in the section labeled "Grid view". When you say I might need to add  or other wrappers, do you mean here? I don't see anything using :nth-child here, nor in the gallery document in the _includes directory, which seems to get called here.
My current best guess is that I need to add something that takes care of archive subtitles in the Grid View, then perhaps all of this:
`  .archive__item-title {
margin-top: 0.5em;
font-size: $type-size-5;
}
.archive__item-excerpt {
display: none;
}
@include breakpoint($small) {
@include gallery(5 of 10);
.archive__item-teaser {
max-height: 200px;
}
}
@include breakpoint($medium) {
margin-left: 0; /* reset before mixin does its thing*/
margin-right: 0; /* reset before mixin does its thing*/
@include gallery(2.5 of 10);
.archive__item-teaser {
  max-height: 120px;
}

.archive__item-excerpt {
  display: block;
  font-size: $type-size-6;
}`

needs to be placed inside of a wrapper?
I'm pretty new to css in general -- any good documentation you could suggest that would be relevant to this puzzle?

I'm talking about these lines https://github.com/mmistakes/minimal-mistakes/blob/master/_sass/minimal-mistakes/_archive.scss#L114-L189
You'll see all sorts of &:nth-child selectors in there.
In it's most simplest form you should have HTML like this:

Heading

Heading 2

The CSS for .grid_item uses the nth-child selectors to position the 2nd, 3rd, 4th, etc. grid items in a repeatable pattern so everything lines up.
What you need to do is clear the floated grid__item elements.
Add clear: both to .grid__wrapper and to .archive__subtitle and it should fix your problem.

Ack, I was looking at an older version of this document! I understand now :)
It's almost working! Now the category titles are in the correct places, more or less, but the second category seems to be offset by the wrong number of grid cells:

does it matter the order in which clear: both appears under .grid__wrapper and .archive_subtitle?

No shouldn't matter. For what it's worth when I look at your site it's aligned correctly.

Oh! I guess things just hadn't updated properly yet.
Many thanks!!


[BT] Search doesn't find Governance Action by ID (TBC: works on test now, check invalid GA actions search)

Context & versions
staging.sanchonet
Steps to reproduce
See Video: https://www.loom.com/share/6ad99e1b324141a6837318cc90ffdffb?sid=393484be-43c1-4e7c-812e-6711f3a2a4d7

Go to GA list page
Copy any GA Id
Paste it into search box

Actual behavior
Nothing is found on the search
Expected behavior
Search should find any GA by ID

Might be resolved after:
https://github.com/IntersectMBO/cardano-db-sync/issues/1716

@MSzalowski @pmbinapps This is working on dev environment. Can we assume it will work on staging once its up and running?

@MSzalowski @pmbinapps Titles are missing on dev Governance Actions, but they were showing on staging, as you can see in the video.

Works now, that is, the GA is found by searching for ID. Not tested for other text strings. Closing


feat(tmux): add support for fzf-tmux in interactive mode

add support for tmux users via fzf-tmux

Thanks for the submission. However, the shell script implementations are largely in maintenance mode as we're switching to Go programs. I recommend maintaining a fork for the time being if you plan on continuing to use these.
I suspect the right solution here is to offer an env var like KUBECTX_PICKER so the power users can pick between fzf, sk etc. #305


Adjust Radar view based on the direction you're looking

I'm aware features like the Radar are still a work in progress, however something I'd like to suggest is having the view inside the gui either:

Change to have the top of the radar match the direction the player is facing, so it's easier to tell where storm systems are located relative to you.
Have a compass graphic that makes it more obvious that the top of the radar is always north.

Basically, I built a house with south-facing windows which has created this small annoyance where the radar is always backwards compared to the view outside.
That's all, I hope this is something you consider :3

I like that :3
Will definitely consider adding


Add files via upload

add bausate college

@oswalj First stage of verification passed, official domain is bausate.edu.pe as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@oswalj Please provide us with an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course.

@oswalj You might miss my previous comment. Please react.

@oswalj I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for your understanding!


CLI command to show public key

Provide a publickey CLI command to show the public key of the current wallet, if any

Let's have this https://github.com/dusk-network/dusk-blockchain/pull/92 merged first before adding new CLI command.


Adding AADProperties query object for CRR

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[ ] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Please review this breaking change intake.
https://msazure.visualstudio.com/One/_workitems/edit/9183985
The x-ms-Odata query object (BMSAadPropertiesQueryObject) in the AadProperties_Get API was not added in the Json spec due to an issue with the json generation tool. We are adding it  to maintain consistency. This will not cause a breaking change issue because only the C# SDK has been published on top of this and this filter object was already included in it post manual testing.
Since this is a bug fix and customers won't be impacted, no alternatives explored.
With the current files, our new SDK generation is blocked for C# since the generated files is removing the above change.

Updating with the correct workitem https://msazure.visualstudio.com/One/_workitems/edit/9183985

Please fix the SpellCheck CI so that we could merge this PR