[Bug]: Fix GitHub Action Failure for Welcome Message in DevDisplay

What happened?
I found a BUG 🐞
Description:
The welcome message GitHub Action, which is supposed to trigger when a user adds their profile to DevDisplay, is no longer working as expected. It was functioning properly when the project started, but now fails to execute during deployment.
Steps to Reproduce:

Add a profile to DevDisplay.
Expect a welcome message to be triggered via GitHub Action.
Observe that the action fails to send the message.

Expected Behavior: When a user adds their profile, they should receive a welcome message through GitHub.
Actual Behavior: No message is triggered, and the GitHub Action fails during deployment.
Help Needed: If anyone with experience in GitHub Actions can investigate and fix this issue, your contribution would be greatly appreciated!
Add screenshots

What browsers are you seeing the problem on?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

assign me this please

I think this issue might be coming because in github action file we do not have a condition for when the PR gets merged which means the user is added to DevDisplay
so maybe giving this condition might help
if:  github.event.pull_request.merged == true
and also we should change pull_request_target: to pull_request as this is more secure

📢 Invitation to Join the DevDisplay WhatsApp Community!
We are excited to invite you to join the WhatsApp community of DevDisplay, where developers and contributors come together to collaborate and share their ideas.
Collaborative Support: If you are interested in working together with extensive support, we encourage you to join our community.
Open Source Contribution: If you would like to contribute to the DevDisplay open-source project, your participation is welcomed in our WhatsApp group.
By joining, you will have the opportunity to connect with like-minded individuals, discuss project developments, and contribute to our shared goals.
For more information and to join the community, please visit: Join DevDisplay WhatsApp Community.
We look forward to your participation!

Hi @avishek999,
Any updates on the GitHub Action bug regarding the welcome message? Let me know if you need any help.


Add defaulting for OnDemandPercentageAboveBaseCapacity in AWSMachineDeployment creation/changes

Towards https://github.com/giantswarm/giantswarm/issues/11956
This PR adds defaulting of the OnDemandPercentageAboveBaseCapacity attribute in AWSMachineDeployment resources.

I merged my PR switching to micrologger, will do some changes. Please wait until you merge it.

Tested again in my kind cluster if logging is ok.
{"caller":"github.com/giantswarm/admission-controller/pkg/awsmachinedeployment/admit_awsmachinedeployment.go:95","level":"debug","message":"AWSMachineDeployment 9cvci onDemandBaseCapacity is nil and will be set to default 100","time":"2020-07-13T09:54:47.684468+00:00"}
{"caller":"github.com/giantswarm/admission-controller/pkg/awsmachinedeployment/admit_awsmachinedeployment.go:95","level":"debug","message":"admitted infrastructure.giantswarm.io/v1alpha2, Kind=AWSMachineDeployment default/9cvci (with 1 patches)","time":"2020-07-13T09:54:47.6846+00:00"}

    Instance Distribution:
      On Demand Base Capacity:                   0
      On Demand Percentage Above Base Capacity:  100

@marians should be good to merge it.
Those changes were basically coming from master but since I also merged some parts into this branch directly it's a bit more work to rebase. I checked all changes again and for me it looks good.

Changes from https://github.com/giantswarm/admission-controller/pull/15,  https://github.com/giantswarm/admission-controller/pull/12


installing pod issues

appodeal not installing in my temple when repo update give me solution please..

Hello! Sometimes appodeal fails to install. Try later until success. It is usually helps ))

i tryed but always fails (:
On Thu, Jun 7, 2018 at 3:48 PM, geekkon<EMAIL_ADDRESS>wrote:

Hello! Sometimes appodeal fails to install. Try later until success. It is
usually helps ))
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/KosyanMedia/Aviasales-iOS-SDK/issues/84#issuecomment-395369954,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AmKncUVdkHJChVBC5awqPHfapr-dT9qrks5t6P3YgaJpZM4Ud4NQ
.

Try verbose mode, when pod install / update. Maybe logs will show something useful

I have the same issue. In general Appodeal is sdk for ads. Why does it belong to this repo and can't be disabled?

Because it is an SDK Template repo. And it provides ads support. You can remove appodeal pod in podfile and change the according code in sample. Or you can use SDK Core and build your own UI :)

@gerchicov-bp this repo is what you need
https://github.com/KosyanMedia/Aviasales-iOS-SDK-Core


Fix marshaling - allow specifying payload and key buffer lengths for Produce()

Fix for bug in #73

Hi @ah- with this fix all the examples/tests now work, let me know if you'd like me to change anything.


Frontend - Pipeline Build and Deploy Slow Down Significantly

Describe the bug
This is an observation in pipeline and also can be seen in locally.
After probably task #704 (switch to carbon icons) was merged to main, frontend build and deployment slow down significantly.
From normally 2~ 3 minutes to now can be observed between 13~20 minutes (normal Github action slowness probably isn't the main factor at this issue).
Observation also includes:

The frontend production build (locally and at pipeline) produces lots of import-artifacts at "dist/assets" folder (more than 7000 small files).
During frontend deployment, these small files are contributing to the large amount of AWS bucket creation and large increase of transfer time to AWS buckets.

Possible reason:

It is very likely due to the frontend Icon.vue component is using "dynamic import" for Carbon Icons.
Private Zenhub Image
"Vite" probably does not know how to resolve this (and thus include everything ?? no tree shaking?? Just a guessing).
The intention having one component to dynamically loading icon was good but maybe it isn't the scenario to fit in this case for loading icons.

Root cause and solution are not immediately clear yet but need to be investigated for possible mitigations .

Can "Vite" have build option to optimize this dynamic icon imports issue, plus a way for icons packing into a small bundle?
Is it possible to still have "Icon.vue" but not using dynamic imports for icon to resolve the problem (so limit this issue within Icon.vue and no impact for other codes)?
Don't use dynamic imports for icons for this case (basically partially re-do #704)?
Other options?

To Reproduce
Please observer past pipeline run mentioned at "Additional context":
Private Zenhub Image
Private Zenhub Image
Locally:

Go to "frontend" folder (main branch).
Do "npm run build".
Observe terminal build message output.
Also Observe produced "./frontend/dist/assets" folder.
Do a quick ls | wc -l bash line count, will show:
Private Zenhub Image

Additional context
We can compare the time ran between these two DEV deployments:

https://github.com/bcgov/nr-forests-access-management/actions/runs/5907237754
https://github.com/bcgov/nr-forests-access-management/actions/runs/5931271453

Figma clues:  https://forum.figma.com/t/every-icon-best-practice-you-need-to-know/6445

Just for a reference here.
The dynamic import can be bundled with this option with vite's rollout option ("inlineDynamicImports"):
build: {
chunkSizeWarningLimit: 1600,
outDir: "dist",
sourcemap: true,
rollupOptions: {
output: {
inlineDynamicImports: true,
},
}
},
Tried it out, seems to be good.
However, it seems to be conflict with other vite's plugin for the manulChunk setup.
Since the code fix to specific import the icons (still it is a dynamic imports) we need can resolve much of this issue, so will just keep this option as reference for now (if issue come up again in future).


begin work implementing ORM relationships

Allow users the ability to define cross references as ORM-style relationships within their object definitions. Such an implementation is heavily inspired by the ORM capabilities of SQLalchemy, Django, and ODMantic.

Closing for the near future as ORM functionalities deprioritised


compressed file handling

zcat zgrep? possible with grada? to support fastq.gz files?

This was automaticly implemented with
if(compressed == TRUE){% use zcat | ... %}
Problem is, the search take quite longer if file is compressed! (maybe this is just the way it is.)


fix Symbol duplication causes crash

Related to: https://github.com/Im-Beast/deno_tui/issues/36

Thanks, good catch at that!

Fixes #36

Its a Christmas Miracle


Allow invoking base (virtual) method directly from IMethodInvocation

Based on feedback from @stakx, it looks like the way we currently implement CallBase in Moq is quite convoluted (it involves skipping other behaviors dynamically, tightly coupling the call base behavior to the other configured behaviors).
Instead of that, just add a new API to the IMethodInvocation to directly create a return by calling the base method. Proposal:
IMethodReturn CreateCallBaseReturn(IArgumentCollection? arguments = null);

The optional arguments would allow the caller/behavior to perform any last-minute tweaks to the arguments ultimately used in the base call prior to returning a value (and optional ref/out args).
This also means we can simplify the behavior pipeline API itself, since there would be no concept of a target to invoke, just the pipeline itself. The pipeline would need to be modified so that invoking it for a method with no implementation (abstract or interface) and with no configured behaviors, throws NotImplementedException now automatically.

Good to hear that this would indeed make it possible to simplify the pipeline architecture.

The pipeline would need to be modified so that invoking it for a method with no implementation (abstract or interface) and with no configured behaviors, throws NotImplementedException now automatically.

That appears to match Castle DynamicProxy's behavior, :+1: as it facilitates swapping between the two technologies upstream.

IMethodReturn CreateCallBaseReturn(IArgumentCollection? arguments = null);

The optional arguments would allow the caller/behavior to perform any last-minute tweaks to the arguments ultimately used in the base call prior to returning a value (and optional ref/out args).

Does the returned IMethodReturn represent the result of calling the base method implementation? That is, will the base method be called right away? If so :+1: as that would allow you to not just tweak the base method's inputs, but also its outputs.

Great questions 💯

Does the returned IMethodReturn represent the result of calling the base method implementation?

Yes, indeed. But modifying the return isn't currently as straightforward since the implementation of IMethodReturn is not public. Maybe it should be public so you can modify it? Alternatively, perhaps we could have mutating methods in the IMethodReturn like WithArguments, WithReturnValue and WithException, say?

Is it permissible to call this method more than once?

I'm not limiting that in the pipeline at all, so technically yes. It wouldn't be a recorded invocation through the pipeline though (no further behaviors applied either, it's a straight delegate to the implementation inside the generated proxy).

Great to hear that the base method call's output(s) can in principle be modified; that was really my main concern here.

Maybe it should be public so you can modify it? Alternatively, perhaps we could have mutating methods in the IMethodReturn like WithArguments, WithReturnValue and WithException, say?

I would keep the IMethodReturn implementation private, in order to keep the public API surface as minimal as possible – less maintenance, plus more freedom to refactor internals, if needed.
 They would be a nice fit for the current "immutable type" design and C# 9's new with expressions for record types.
Even if you don't add those methods, one could still reimplement IMethodReturn and copy over properties from the original instance to a custom instance, right? That would be some work, but it would be possible; that's the main thing IMHO.

Yeah, maybe. The thing is that the MethodReturn implementation is really trivial. Moreover, someone inspecting the API might wonder why did I make MethodInvocation and ArgumentCollection public and not the MethodReturn? The answer is not trivial, of course: the first two are used in generated proxy/avatar code and therefore have to be public, but at face value, it seems like a weird design choice and a (however minor) friction point for extensibility in the pipeline... dunno...


Verify type hints matching types of options/args

I'd love to see a way to verify if mypy option/argument types are consistent with types of parameters defined in the decorated methods. It seems that it should be possible - many of the types of options have precise expected type of the parameter that accepts the option, so once we (not sure if possible) join the decorated option definition with type-hints - both available to static checkers - we should be able to determine if the type hint is ok.
Maybe I could contribute myself - though I'd need to deeper dive in mypy and type hinting integration with other tools - but I wanted to open an issue first, because maybe this is something that is difficult/impossible or - on the other hand - already possible but I have not found out how. Or maybe someone works on it (searched through issues / PRs and could not find anything though).
Context:
In Airflow development environment (breeze) we are using click a LOT (including rich-click extension) - it's really cool and helpful and I am very happy with the flexibility and convenience of click. The reason why we need it is that we have likely close to ~ 250 number of options  and multiple tens of commands in it and it's becoming a bit problematic when for example you miss that option has no "default", but it is defined as str (instead of str | None).
Just the recent example of it https://github.com/apache/airflow/pull/35842 - having type checking working via (for example) mypy plugin, could have prevented this kind of mistake.
Would love to hear what the maintainers think about such a feature.
And of course - kudos for the great library!

I'm very hesitant to do something this complex with typing, given my general experience trying to support typing at all so far. Typer wraps Click and includes more integration with typing, but I'm not sure what it does and doesn't support. There are a lot of non-obvious interactions between the many ways a parameter can be defined, such as default sources, prompting, nargs, multiple, callbacks, etc. If you want to figure out how to implement it, I'm willing to consider a proposal and then PR, but it's such a large feature I'd need some commitment to support it after release as well.

I'm willing to consider a proposal and then PR, but it's such a large feature I'd need some commitment to support it after release as well.

Much appreciated - and thanks for being super candid and open. I will see if I can spare some time on investigations, and I fully agree that if it comes as one that is on a complex-ish side the maintenance burden migh be way more than the benefit,  so let me see when (if?) I can come up with something.  There are often far too many interesting things to do :).
Not sure how you do it here - but feel free to assign it to me, and I will come back here when I do my part.

No time to look so far and it's not as annoying regularly. I think the assesment on not doing this was a good one. Closing it.


ACM-3283 : Introduce Hosted Mode

Jira: https://issues.redhat.com/browse/ACM-3283
Scope is limited to just setting up the MCE in hosted mode, and supporting more than one MCE or MCH. Most of the code is contained within the hosted.go files to minimize affecting the main code paths.

/lgtm


Enable-WriteCore-feature-for-networkcloud

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.NetworkCloud


Create mailing lists for public comms

Create general PDS mailing lists for public comms / coordination of open source work.

pds-users@ - Public mailing list for users to come and ask questions and get help, etc.
pds-dev@ - Public mailing list focused on development work. Good place for external users to go to communicate about development activities, contribute to the tools, etc.
pds-pmc@ - Private list for the open source management team(s)
pds-codeofconduct@ - A private list for receiving any code of conduct violation / concern emails

Lists created. Security settings applied are listed below. @jordanpadams, at the moment you're only person added to any of these lists.
Stuff to think about:

Do we actually want a separate user / dev list? If the traffic is low enough it might make sense to keep them as a single list.
Do we have interest in the Collaborative Inbox option?
I left the "shared label" option off for all these groups (well, whatever the default was). We should consider coming up with a list of helpful labels to use for stuff.

pds-users

pds-dev

pds-pmc

pmc-code-of-conduct


Fix link redirection

HTTP status code is 301. The link should be updated.

r? @nikomatsakis
(rust_highfive has picked a reviewer for you, use r? to override)

Thanks!


Update loading of QRRSA from config

This PR cleans up unused configuration and updates function for loading QRRSA configuration.
Previously we had qr and qrsmall in the configuration YAML, but we never used qr. I replaced the values of the previous qr with those defined for qrsmall, so that they are now always loaded (without the need for the caller to specify which one). qrsmall field was removed, as its values are now under qr.

@miha-stopar Travis CI build times out before all the tests can be completed for QR/QNR proofs with longer keys. I would keep the shorter ones, as the entire test suite already runs quite some time. Perhaps we should add safety controls to ensure a safe key size some time in the future. Do you agree?

OK. Perhaps just add a comment in the test that says that at least 1024 bit length should be used for p and q outside the tests.


Inadequate information on GDPR section

Description:
Section[1] only focuses on forgetme feature as GDPR compliancy of the product so please include cookie handling part as well.
NOTE: Adding this for tracking the requested improvement while there is a note saying the 'section is in progress'
[1]
https://docs.wso2.com/display/DAS3xx/General+Data+Protection+Regulations+for+WSO2+Data+Analytics+Server
Suggested Labels:
Documentation, 3.2.0
Suggested Assignees:
@RukshiW

Added [1] for SP. The DAS docs will be updated with a similar page.
[1] https://docs.wso2.com/display/SP4xx/Handling+Cookies


fix: typos in documentation files

This pull request contains changes to improve clarity, correctness and structure.
Description correction:
Corrected edits to editing
Corrected dual licensed to dual-licensed
Please review the changes and let me know if any additional changes are needed.

I'm sorry but I manually recreated this in https://github.com/toml-rs/toml/commit/675edca4c312e2dcdbcef301d34fefdaa9ca66f7 and https://github.com/epage/_rust/commit/15ede43536f52b96d69152522bf57156662960a3 (which will b pushed to toml on next template update).
I normally prefer merging other people's work and giving them credit but I've been getting a lot of drive-by typo corrections over the last week which has been very suspicious.


[Feature request] Legacy SSL/TLS ciphers, digests and protocols

I would kindly like to request a (maybe opt-in?) reactivation of certain older SSL/TLS cipher suites and protocols such as SSLv3, TLS v1.0 and v1.1.
I understand that many people might be against this for security reasons, however. Hence my idea of leaving the legacy crypto off by default, but allowing the user to switch it on, maybe either globally or per target host, like Firefox can.
My reasoning is that I'm also running legacy servers within my LAN with which I would like to communicate using Supermium on a retro XP x64 box. Assuming you're linking in OpenSSL for this, it should be possible in the configuration. I've once recompiled OpenSSL for a Win2k target to get everything from SSLv3 and stuff such as 3DES and MD5 up to TLS v1.3 and modern cipher suites, though admittedly that was still OpenSSL v1.x.
I would personally benefit from having TLS v1.0 up to TLS v1.3 and in addition to what Supermium can do already, I would like to request the following ciphers in the TLS v1.0 context:
TLS_DHE_RSA_WITH_AES_256_CBC_SHA (dh 1024) - A
TLS_RSA_WITH_AES_256_CBC_SHA (rsa 2048) - A
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (dh 1024) - D
TLS_RSA_WITH_3DES_EDE_CBC_SHA (rsa 2048) - C
TLS_DHE_RSA_WITH_AES_128_CBC_SHA (dh 1024) - A
TLS_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A
TLS_RSA_WITH_RC4_128_SHA (rsa 2048) - C
TLS_RSA_WITH_RC4_128_MD5 (rsa 2048) - C
TLS_DHE_RSA_WITH_DES_CBC_SHA (dh 1024) - D
TLS_RSA_WITH_DES_CBC_SHA (rsa 2048) - C
TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA (dh 512) - E
TLS_RSA_EXPORT_WITH_DES40_CBC_SHA (rsa 64) - E
TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 (rsa 64) - E
TLS_RSA_EXPORT_WITH_RC4_40_MD5 (rsa 64) - E
In any case, thank you very much for your awesome work!

Couldn't you just use an old browser for this? IE, old firefox?

Well, yes, you're not wrong. That's what I'm doing for now, using Supermium (since a few days) for modern servers, and some Chinese-made Chromium 87 backport for all the other stuff. But it would be quite convenient to have one browser that can do it all. :)
It should be possible, so I thought I'd just ask. If the developer refuses, I'll just have to live with two browsers. Asking won't hurt I guess. :)

Assuming you're linking in OpenSSL for this

... I think BoringSSL is being used, a fork :wink: ...
https://github.com/win32ss/boringssl

Couldn't you just use an old browser for this? IE, old firefox?

Or run a local proxy that either strips HTTPS or upgrades it.

I could use stunnel for that, as I've already ported it back to XP and Win2000 with OpenSSL 1.x. But while it's super convenient on the server side, it's not on the client side. stunnel is tedious to configure as a client, as you have to explicitly add every single host you want to visit in your configuration file, and you need to open a specific, local listen port for each target server. With that, you need to memorize which local socket represents which remote service.
Or is there any better, XP-compatible software for that that works for arbitrary hosts? I'm open to any recommendations in case the Supermium developer does not wish to add legacy protocols and cipher suites.

... I think BoringSSL is being used, a fork 😉 ...
https://github.com/win32ss/boringssl

Ah okay. I have never worked with BoringSSL before, but if it's a fork I assume the build toolchain and configuration parts are similar?
And I have another question, even if it doesn't exactly belong here: Are there any complete build HowTo's for Supermium? If I could manage to compile and link the whole project myself, I could attempt to patch it for my own use case.
Thank you!

If it's in your LAN, do you really need SSL/TLS? Why not just do it over http?


Is there No Svelte Variant

Hello  i love the libary but svelte is like the best thing now, would have loved a svelte variant, please make one compatible with svelte 5

Hey @hybornconcept, you can find a non-official Origin UI Svelte here: https://originui-svelte.pages.dev/.


Display molecule status when not created

status displays not_created when the instance(s) are not created.
Added offline status to functional test suite.
Also, believe fixed a bug with molecule status with docker driver.
Was displaying status for the wrong hosts.


Dependencies Problem "@capacitor/core": "latest", "@capacitor/ios": "latest" and "@capacitor/android": "latest" breaks builds : New Capacitor 3.x Release

Describe the bug
The dependencies "@capacitor/core": "latest", "@capacitor/ios" and "@capacitor/android" are specified to the latest version.
The new Capacitor 3.0 was released yesterday and now the builds of Capacitor 2.X apps, are broken, because internally this plugin installs the new Capacitor 3.0 (latest version).
Older Capacitor 2.x apps seems to be broken because of this dependency, and new Capacitor 3.X apps still have the same problem because this plugin does not support yet Capacitor 3.X.
To Reproduce
Steps to reproduce the behavior:

Use an "old" Capacitor 2.X project;
Add this plugin to the project;
Try to run the project.

Reported Error
Error: node_modules/@capacitor-community/apple-sign-in/node_modules/@capacitor/core/types/definitions-internal.d.ts:16:18 - error TS2430: Interface 'CapacitorInstance' incorrectly extends interface 'CapacitorGlobal'. [ng]   Types of property 'Plugins' are incompatible. [ng]     Property 'SignInWithApple' is missing in type '{ [pluginName: string]: { [prop: string]: any; }; }' but required in type 'PluginRegistry'. [ng] 16 export interface CapacitorInstance extends CapacitorGlobal { [ng]                     ~~~~~~~~~~~~~~~~~ [ng]   node_modules/@capacitor-community/apple-sign-in/dist/esm/definitions.d.ts:3:9 [ng]     3         SignInWithApple: SignInWithApplePlugin; [ng]               ~~~~~~~~~~~~~~~ [ng]     'SignInWithApple' is declared here.
Expected behavior
The Capacitor dependencies should be specified to a specific version so older versions of capacitor could still use this plugin and build the app.
A new release should be created with a "pinned" version the latest Capacitor 2.X.X version so the support to older apps could still be possible.
And eventually a new version should be release to add support to the new Capacitor 3.X.X.
Screenshots

Fixed

@epicshaggy Hi, can you be more specific ? which version of this plugin should we use to keep compatibility with capacitor 2 ?
thanks !

Finally, I use this version to fix this problem :
"@capacitor-community/apple-sign-in": "0.0.14",


request: accommodate file imports

I found that by targeting specific Stonecutter source files in my imports, I saved around 220 KB in my (webpack) bundle -- a little more than 80% (pre-minified) compared to importing without direct paths. Everything still functions perfectly:
// before
import { CSSGrid, layout, easings } from 'react-stonecutter';

// after
import CSSGrid from 'react-stonecutter/src/components/CSSGrid';
import simple from 'react-stonecutter/src/layouts/simple';
import { expoOut } from 'react-stonecutter/src/utils/easings';

To do this, though, I had to reconfigure webpack for .jsx files, add the /src path for compilation, and enable a few Babel loaders that I wasn't already using.
It would be great if the /lib directory could also include compiled versions of the modules in /src. You can see an example of this in the Redux source; see /src/applyMiddleware.js compared to /lib/applyMiddleware.js.
I would contribute this myself but am unfamiliar with the Gulp/Weback build config you're using. Otherwise I'm happy to pitch in where possible if you think this is worthwhile.

Hi, thanks for finding these savings! I'll take a look at how Redux approaches this as you suggest and see what I can do.
I'm looking forward to tree-shaking in Webpack 2, should make things less fiddly!


I completely follow the tutorial to the author, but the right-click does not appear after the plugin logo

I am a Windows system.New Typora, What Should I Do?

@Coinsi
hi. is there a button group in the bottom right corner of Typora? if there is, it seems like you clicked in the wrong spot - you should be right-clicking in the writing area instead.

@Coinsi
close this issue. if you have any questions, feel free to leave a message below or open a new issue


VS2015 - Failed to make the following project runnable ... [file] is being used by another process

Description
Building a .net core Web Api project with a reference to a Library project with a dependency on Confluent.Kafka results in the following error :
Failed to make the following project runnable: Tii.ProjectReporting.Intranet.Api (.NETFramework,Version=v4.5.2) reason: The process cannot access the file 'c:\users...\packages\librdkafka.redist.0.11.0\runtimes\win7-x64\native\librdkafka.dll' because it is being used by another process.	WebProjectName	C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Common.Targets	262
Have verified that the file, librdkafka.dll is not locked by another process, that it exists and is accessible.
How to reproduce
Try building WebApplication2 in this project => https://github.com/NiallHdn/confluentkafka-build-problem
Checklist
Please provide the following information:

[x] Confluent.Kafka nuget version: 0.11.0
[x] Apache Kafka version: <IP_ADDRESS>
[x] Client configuration: .net core web app, running on .net framework 4.5.2
[x] Operating system: Windows 10, Visual Studio 2015 with Update 3
[ ] Provide logs (with "debug" : "..." as necessary in configuration) - see link to repo above and build project
[ ] Provide broker log excerpts - see link to repo above and build project
[x] Critical issue - It a show stopper for us

We don't test on project.json anymore as it was replaced by new csproj (we do test net452 and netcore on various vs dist). Also as side note, you don't use .net core but net452 with project.json format from what I saw
Will try to reproduce when back from holidays next week

Echoing @treziac: we don't support project.json anymore and nor does Microsoft. Your first step should be to move away from this. If you still have problems, feel free to update in this thread.

I can't compile the xproj projects. The VSToolPath the xproj define does not exist on my computer, didn't try harder
opening with vs2017 (and converting to new csproj), I have no problem to run both WebAPI

From what I remember when I used xproj, the project.json dotnet sdk doesn't support very well a mix of non-nuget project references between standard projects (your class libraries which are standard 4.5 csproj) and xproj.
I assume your project would work if you create an nuget for your class libraries and reference them in yout webapp, or perhaps if your classLibrary was a project.json project also. (but won't test, I encourage you to migrate to new csproj - only issue is that you will need to upgrade to vs2017, which may indeed be problematic in terme of licence purchasing giving your needs/company ; but you can also use vsCode or vs2017 community, or any other ide supporting dotnet core )

Many thanks for your responses guys. It sounds like upgrading to vs2017 might be our best option since we will have to do so at some point anyway. I'll update this issue when I've retried in vs2017.

closing as no longer relevant.


[SPARK-36166][TESTS][FOLLOWUP] Add BLOCK_SCALA_VERSION to sparktestssupport/init.py

What changes were proposed in this pull request?

This is a followup PR for SPARK-36166 (#33411), which adds BLOCK_SCALA_VERSION to sparktestssupport/__init__.py.
Why are the changes needed?

The following command fails due to the definition is missing.
SCALA_PROFILE=scala2.12 dev/run-tests.py

Does this PR introduce any user-facing change?

No.
How was this patch tested?

The command shown above works.

cc: @HyukjinKwon

oops, thanks man!

Merged to master and branch-3.2.

Thank you, @sarutak .


Fix a bug of cross-subnet check

Description
This commit can fix a bug(#907).
When enable route reflector in a cluster and enable IPinIP in cross-subnet mode, the calico couldn't work correctly.No mater the calico/nodes were in a same subnet or different subnets, they all communicate with other calico/nodes by IPinIP.
The calico/nodes do cross-subnet check by the 'from' filter. When enable route reflector, the 'from' filter would get the route reflector's IP address not the calico/node's IP address, so we should use the 'bgp_next_hop' filter instead of the 'from' filter.
I have tested this commit on my private cluster(both for with route reflector and without route reflector). The calico/nodes in my cluster can create route rules for each node correctly. Only the calico/nodes in different subnet communicate by IPinIP.
I do not test this commit on any public cloud, please test it if necessary.
Todos

[x] Tests
[x] Documentation
[x] Release note

Release Note
Support cross-subnet IP-in-IP when using a route reflector

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.lilianrong seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.lilianrong seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@robbrockbank I'm sorry for my mistakes.
If the next hop IP address is from a different subnet, 'gw' will get the gateway IP of the host, but the 'bgp_next_hop' can get the IP of next hop. So we should the 'bgp_next_hop' not 'gw'  to fix the bug of cross-subnet.

@robbrockbank can you assign a milestone tag for this PR ? thank you.

LGTM.  @caseydavenport :  we'd need to test this in a couple of deployment scenarios, namely #907 and also in a cross-subnet AWS deployment.

This LGTM too.
I've raised https://github.com/projectcalico/calico/issues/1150 as a way to track validation in AWS.
Thanks @nightmeng!


Fix code for ekssum

FIXES 98
Fix up typemap for test_ekssum.   Fix test to get it to fit our prototype.
Only wrap arrays of strings inside an additional [] if it's the first argument.  Maybe we should just make it a tuple.

Closing this so I can make a slightly bigger pull request


Error following the guide.

When following the guide, after linking to the path where the .iso file is located the error, is thrown:
Export-WindowsImage : Either the Name or Index parameter is required
At C:\Users\User1\downloads\CreateSrsMedia.ps1:1464 char:9

    Export-WindowsImage -DestinationImagePath "$NewInstallWim" -S ...

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidArgument: (:) [Export-WindowsImage], PSArgumentException
FullyQualifiedErrorId : Export-WindowsImage,Microsoft.Dism.Commands.ExportWindowsImageCommand

Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


Docs: adding a favicon

Added section to the docs; changed example to use redirect in place of send_file.

Please you could fix the styling issue, then happy to merge 👍

p.s.


Service: AmazonServerlessRepository; Status Code: 502; Error Code: null

Hello. I am trying to use the splunk-kinesis-stream-processor serverless application to setup Cloudwatch Logs (VPC Flow Logs) log ingestion into our Splunk Cloud environment. At the very last step of the process at AWS->Lambda->Functions->Create Function->Review,configure and deploy, I get the following error after clicking the "Deploy" button:
Internal server error (Service: AmazonServerlessRepository; Status Code: 502; Error Code: null; Request ID: 711dca4d-2300-11e8-af75-a7e16485785d)
What does this mean?

Hi @tjrun262. Could you share what region you are attempting to deploy from?

US-West-2 (Oregon)
From: nstonesplunk<EMAIL_ADDRESS>Sent: Thursday, March 08, 2018 11:38 AM
To: splunk/splunk-aws-serverless-apps<EMAIL_ADDRESS>Cc: Jones, Tim<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [splunk/splunk-aws-serverless-apps] Service: AmazonServerlessRepository; Status Code: 502; Error Code: null (#4)
Hi @tjrun262 https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tjrun262&d=DwMCaQ&c=N13-TaG7c-EYAiUNohBk74oLRjUiBTwVm-KSnr4bPSc&r=m7IS8tZL1RqLG_wVs3uyPn5LojCLRfRpgazd19Zweso&m=ebCyo9QbOkXOLW7LMsCELNCxFMB_i08jLIjPavrax8o&s=nvAdeEeFmoVZf4fiuQJmUDfrushebXtOmOG7nOyQNwo&e= . Could you share what region you are attempting to deploy from?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_splunk_splunk-2Daws-2Dserverless-2Dapps_issues_4-23issuecomment-2D371599459&d=DwMCaQ&c=N13-TaG7c-EYAiUNohBk74oLRjUiBTwVm-KSnr4bPSc&r=m7IS8tZL1RqLG_wVs3uyPn5LojCLRfRpgazd19Zweso&m=ebCyo9QbOkXOLW7LMsCELNCxFMB_i08jLIjPavrax8o&s=0HFVTMWfZVIIDtqXYpqbeAkmKAW0KVjbVnifTzuKAOc&e= , or mute the thread https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AE11B3ajQlXFBKQzDCVDavgpo6eQk69Gks5tcYiggaJpZM4SjM8r&d=DwMCaQ&c=N13-TaG7c-EYAiUNohBk74oLRjUiBTwVm-KSnr4bPSc&r=m7IS8tZL1RqLG_wVs3uyPn5LojCLRfRpgazd19Zweso&m=ebCyo9QbOkXOLW7LMsCELNCxFMB_i08jLIjPavrax8o&s=TPzXkWRmycNjRsD96m4uJZGSKusMFoQmwvImft7i3UM&e= .  https://github.com/notifications/beacon/AE11B30_Y-XYFUofcPlv7OB58I9-6fTZks5tcYiggaJpZM4SjM8r.gif

This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.


bsc#1117942: fixes for volume plugins

Use a writable directory for volume plugins
Use the same volumes plugins directory for the controller-manager and the kubelet

bsc#1117942

@MalloZup this is not specific to cloud, it is used to configure flexvolume drivers.
I'm currently testing it

@r0ckarong we've fixed this issue but we're not using the default path because it points to a RO mountpoint, so this would need a point in documentation just to explain what is the good path ;)

Install FlexVolume drivers on CaaSP

A FlexVolume driver is an external (out of tree) driver usually provided by a specific Vendor.
These volume drivers have to be installed on each node (worker/master) in a Kubernetes cluster.
On SUSE CaaSP the path to install these drivers is /var/lib/kubelet/plugins.
Doc: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-storage/flexvolume.md

@inercia we need to backport this one ;)

@lcavajani Is the documentation you linked applicable to CaaSP like that? If not could someone please provide the CaaSP specific steps.
Also, which version of CaaSP will receive this functionality? Is this going to be backported to v3?

@r0ckarong this will be backported to v3 yes.
There is no specific configuration to do for CaaSP afterwards.
These drivers are usually deployed with DaemonSets, what the user should do is to change the value of the flexolume dir path in the manifests which is usually in the form of an environment variable (e.g FLEXVOLUME_DIR_PATH for rook [1])
[1] https://rook.io/docs/rook/v0.9/flexvolume.html#configuring-the-flexvolume-path

so this would need a point in documentation just to explain what is the good path ;)

What is this path?

@r0ckarong the path is /var/lib/kubelet/plugins


Does it support pause & resume feature?

Thanks

It doesn’t currently support that. If you find time to implement this yourself, feel free to file a PR so that others can benefit from this as well. See #23 for a possible architecture that would allow this feature.


[Android] purchaseUpdatedListener auto-renew subscription not listened

Description
When I use purchaseUpdatedListener to listen subscription renew in iOS, it works normally.
But, I can only listen to the first subscription purchase in Android, subsequent renewals are not listened.
Environment:

react-native-iap: ^12.12.1
react-native: 0.71.11
Platforms Android

Try this

the linked video above doesn't answer the question, still I don't see subsequent calls for Android


Loops endlessly on 4x4

The solver spins through 3x3, 4x3, and 3x4 boards to a solution nicely given any of the heuristic variations, but it spins endlessly on 4x4 boards.  Was this tested?
I tried generating the board several times just in case the IsSolvable check was failing.
After playing around a little more, I did notice 4x4 puzzles being solved, but only after a 3x3 had been previously solved.
So to duplicate what I'm doing, immediately change to a 4x4 puzzle after launching the application, generate a new puzzle and try to solve.  I could never get this working.  Perhaps there is some initialization issue for the 4x4 code path?

Yeah, I mentioned in the readme that it doesn't work well for 4x4 and bigger. Probably needs better algorithm/heuristics. such as Disjoint Pattern Database.

I did notice 4x4 puzzles being solved, but only after a 3x3 had been previously solved.
Maybe it simply generated easier puzzle? If you were using random puzzles each time.

Most of the published code on the net fails on a 4x4 puzzle.  In fact, I've only found one solver that works every time, and very quickly.  It uses a brute force algorithm and comes up with a sub optimal answer in under a second for a 4x4 puzzle.  The smart approaches tend to get "lost" and never produce an answer.  I've let your code spin for 3 hours on a relatively easy 4x4 puzzle on a very fast machine before stopping it.
I'm surprised that smart back tracking isn't talked about more often with respect to this problem.  The other A* code I've looked at lacks the smarts to know when to stop searching.  You're looping code is one such example.  Adding a simple check for an iteration limit would make the code a little bit smarter.  Had you weighted the search path, and then back tracked to the next best candidate after the iteration limit is hit, the search would be even smarter.
I've also seen minimal use of threading.

I'd like to ask about how I can change the goal board to the state below.

I'd like to ask about how I can change the goal board to the state below.

It's initialized here https://github.com/AlexP11223/EightPuzzleSolver/blob/57bc1d5c4a7f49cae074eef18b559426de225dfa/EightPuzzleSolverApp/Model/PuzzleSolverService.cs#L16, you can pass the goal as the second parameter.
PRs adding it in UI are welcome :)

Also please do not ask your questions in old unrelated issues like this one.


Does this repo support vision model like resnet?

In your official pytorch-1.12 runtime decker, I use the following code
model = models.resnet50().float().cuda()
dummy = torch.rand(1, 3, 224, 224).cuda()
torch_blade.optimize(resnet_50, allow_tracing=True,model_inputs=(dummy,))
I got many errors when I called optimize

It’s supposed to work functionally while it may be less performant than NLP/speech models since CV model optimization is WIP.

I got many errors when I called optimize

Could you please paste the error logs?

maybe try to freeze the graph first？

When my input is model = models.resnet50().float().cuda().eval(), the optimize func runs two hours and still do not return.
When my input is model_jit = torch.jit.script(model).eval(), I can get the optimized model, but I also meet some errors.

It seemed to fail on some check in aten::conv2d's converter, roll the log up, there should some log. Otherwise, you can try setting env var TORCH_DISC_USE_TORCH_MLIR to true to use switch to the new converter in development.

Thanks, after set TORCH_DISC_USE_TORCH_MLIR to true, I do not get any error. And it really doesn't have a noticeable performance boost

And it really doesn't have a noticeable performance boost

The aten::_convolution failed to lower due to bugs in the shape analysis pass. I will fix it in this PR and an ResNet50 example would be put later: https://github.com/alibaba/BladeDISC/pull/627

@eclipse9527 You can try disc inference example on ResNet after the PR is merged: https://github.com/alibaba/BladeDISC/pull/642

Hi @fortianyou ,I get poor performance in the official resnet50 examples in official pytorch-1.12 bladedisc docker, my gpu is 3090.

I get poor performance when I set batch=1

@eclipse9527 Thank you for reporting this.  As @wyzero mentioned before, we are still tuning the performance. We will update the result later.

@fortianyou

The issue had been addressed, feel free to reopen it if needed.


[AUTOPATCHER] Kernel upgrade to version <IP_ADDRESS> - branch main -

This version of the source fails to build for ARM. See new PR with corrected source v<IP_ADDRESS>: https://github.com/microsoft/CBL-Mariner/pull/3564


Mapping conflict Output suspend in Konsole

The mapping for multiple cursor selection  makes the output halt.
Changing it to anything else solve the problem ofc.

Please report this in https://github.com/terryma/vim-multiple-cursors


make with_raw_connection invocations compatible with rails main branch

After https://github.com/rails/rails/pull/48068 was merged with_raw_connection invocations don't work anymore :C

This is a good idea, Kamil -- and things are almost shuffled around into a good state in which we can bring in rails/rails#48068.  Most importantly to change uses_transaction over to materialize_transactions in all places where it exists.
If you'd like, we can work together to have this happen.  Would just like to have #50 and #51 brought in first.


Unable to upload to Appstore

Describe the bug
With latest update, firmware update working, but when we upload IPA to Appstore, upload fails with following error,
ERROR ITMS-90206: “Invalid Bundle. The bundle at ‘XamarinApp.app/Frameworks/ZIPFoundation.framework’ contains disallowed file ‘Frameworks’.”
ERROR ITMS-90206: “Invalid Bundle. The bundle at ‘XamarinApp.app/Frameworks/iOSDFULibrary.framework’ contains disallowed file ‘Frameworks’.”
To Reproduce
Steps to reproduce the behavior:

Create new project
add dfu library v <IP_ADDRESS>
Build and archive for Appstore release
Upload IPA to AppstoreConnect

Expected behavior
Should get uploaded without any error.

@framinosona can you help with this?
I tried following suggestions, with no success.
https://stackoverflow.com/a/25789145/1760421
https://stackoverflow.com/a/33092433/1760421


Minify slates before armoring

This PR minifies the JSON strings (removing spaces and linebreaks) before armoring.
Similarly, when the armor is removed on the other side, the JSON output is pretty printed and returned in its original format.

Thanks for exploring this @lehnberg! We seem to be getting closer and closer to a copy/pastable slate string :tada:
After taking a closer look, I think serde_json handles this for us already and outputs minified json strings when serializing objects to strings of json. I did not take this into account in the hacked together initial attempt and missed this great efficiency opportunity, nice find :rocket:
In practice (at least for file-based tx) grin-wallet serializes slates into json strings from the application objects with serde_json::to_string(slate). At this point point the json string is already minified. From here slatepack::armor(serde_json::to_string(slate)) could be called and would return a minified armored slate.
However, when reading directly from a written slate file with include_str! macro (without type casting with serde_json), and armoring that directly, we are not minified as it includes newlines etc.
So I think we get this minification out-of-the-box in grin-wallet when using serde_json to serialize the application objects into the json string like we already do.
We can check some of this with something like:
use serde_json::Value;

let slate_file = include_str!("pub.tx");
println!("SLATE FILE: {:?}", &slate_file);

let slate_json: Value = serde_json::from_str(&slate_file).unwrap();
println!("JSON VALUE: {:?}", &slate_json);

let slate_string = serde_json::to_string(&slate_json).unwrap();
println!("JSON STRING: {:?}", &slate_string);

let naive_armor = armor(&slate_file).unwrap();
println!("NAIVE ARMORED SLATE: {}", &naive_armor);

let minified_armor = armor(&slate_string).unwrap();
println!("MINIFIED ARMOR SLATE: {}", &minified_armor);

Unfortunately the above example doesn't quite work out-of-the-box with the existing hack of generating a tx file with grin-wallet and importing it into a rust binary and using slatepack for armor serde. However, it should work out-of-the-box if called directly in grin-wallet today because it would be using serde_json when serializing to string.
I'd like to find a change we can make to continue testing in the same method of reading from file while still minifying slates without assuming the strings passed to armor() aren't yet minified (because they will be in practice).
Maybe we could add something like armor_file() and remove_armor_file() to handle (de)serializing when reading directly from a written non-minified slate file?

Yeah I was experimenting with serde_json but couldn't get it to work properly. Closing this PR in favour of the approach you are suggesting. 👍


Fixers should be forced to have a rationale

I would like to start a discussion about the need for every single fixers to be documented with their rationale. This should then appear in the describe command, and in the documentation (README.rst).
For now all fixers must have a summary and may have a description. The description usually explains in details what it does, but it rarely says why we should enable that particular fixer. This makes it difficult and/or time consuming to decide whether or not new fixers should be enabled during an upgrade.
A recent example of this is the StaticLambdaFixer. From the describe command it is extremely clear what it does, but there not even a hint of why it may be a good idea to consider it:
$ ./vendor/bin/php-cs-fixer describe static_lambda
Description of static_lambda rule.
Lambdas not (indirect) referencing `$this` must be declared `static`.

Fixer applying this rule is risky.
Risky when using "->bindTo" on lambdas without referencing to `$this`.

Fixing examples:
 * Example #1.
   ---------- begin diff ----------
   --- Original
   +++ New
   @@ -1,4 +1,4 @@
    <?php
   -$a = function () use ($b)
   +$a = static function () use ($b)
    {   echo $b;
    };

   ----------- end diff -----------

This is even exacerbated by @localheinz who kind of asked about it in the PR, but never gives an answer.
A counter-example of that is ExplicitStringVariableFixer whose description contains a rationale, and makes it much easier to make a decision about it:
$ ./vendor/bin/php-cs-fixer describe explicit_string_variable
Description of explicit_string_variable rule.
Converts implicit variables into explicit ones in double-quoted strings or heredoc syntax.
The reasoning behind this rule is the following:
- When there are two valid ways of doing the same thing, using both is confusing, there should be a coding standard to follow
- PHP manual marks `"$var"` syntax as implicit and `"${var}"` syntax as explicit: explicit code should always be preferred
- Explicit syntax allows word concatenation inside strings, e.g. `"${var}IsAVar"`, implicit doesn't
- Explicit syntax is easier to detect for IDE/editors and therefore has colors/hightlight with higher contrast, which is easier to read

Fixing examples:
 * Example #1.
   ---------- begin diff ----------
   --- Original
   +++ New
   @@ -1,4 +1,4 @@
    <?php
   -$a = "My name is $name !";
   -$b = "I live in $state->country !";
   -$c = "I have $farm[0] chickens !";
   +$a = "My name is ${name} !";
   +$b = "I live in {$state->country} !";
   +$c = "I have {$farm[0]} chickens !";

   ----------- end diff -----------

Other projects, such as TSLint are doing that very well and have a short and clear rationale for every single rule (see example).
So I would like to suggest the following steps:

As of right now, reject all new fixers who don't include a rationale in their description
Enforce that requirement by code

Come up with a new signature for FixerDefinition that includes a mandatory rationale, separate from description
Update all fixers accordingly
Show that new info in documentation

As a bonus, generate one page per fixer to document them, which would include pretty much the output of describe command, because the single list in the README is getting very long

I cannot tell if @keradus reply is being sarcastic or not, so I am not sure how to reply to that. But just in case if it isn't, wouldn't you that a description is not the same as a rationale and thus it should be two different fields ? That way the description would be kept optional could be as short or as long as needed, while the rationale would be mandatory and be as concise as possible ?
@SpacePossum by not considering point 1, you seem to be saying that you refuse to increase the quality of newer code on the pretext that existing code is of lower quality. That does not sound very motivating for the people trying to "fix it" if somebody else keep adding broken stuff. Would you reconsider your position on that ?
Also I forgot to mention in my original post that we could also consider categorizing fixers. Some of them are purely aesthetic, such as no_extra_blank_lines. While others might be performance related, such as native_function_invocation. And others might be about strictness (strict_param). Would there be any interest/use for something like that ?

I stated I would not consider any of the points, especially point 1., until  , so clearly I would consider it as the until part is matched.
So to  That does not sound very motivating for the people trying to "fix it" if somebody else keep adding broken stuff.
I'm stating: please people fix it! Very much welcome, send it in as a PR and I merge it in heart beat.  This can be done as @keradus stated within the current definition. We can split it out later when needed.
This is not sarcastic, we will merge any documentation improvements we get in PR form.
Till then, however, I'm not going to stop merging good fixers, like you suggest in point 1. You consider a good working fixer still broken stuff if the docs are not on some level, I think it is not broken and very demotivating for people to see their work not merged over wording in the docs.
All in all we all like better docs, so lets get these first before we start making changes to the definitions, interfaces and stop merging other work. Maybe a good start would to look at the current PR's with proposed new fixers and see if these have an acceptable rationale in the description?

Thank you for the clarification on your position. I most likely won't invest more time in this, so I'll be closing the issue for now. If other people join the discussion in the future, and have I have more time at that point, I might join back in though.

@PowerKiKi, I'm super serious on that !
As @SpacePossum mentioned, we were doing exactly the same thing once already - with summary of rules.
We didn't enforced it until we provided them for all rules. It was pretty big thing to do.
I would be super happy to see rationate for the rules, and your help with providing them is much appreciated !
Please, start working on it ;)
In definition of rule, we do have 2 fields, summary and description. Summary is super short (one-liner) info about the rule, it's mandatory, while description was planned especially to contain the rationate. No need for new field.
My 2 cents for your further discussion with @SpacePossum.
Sadly, it's super common that one who create a great code, can't create at least decent docs for it.
So for long we have the field optional, let us not block new rules by lack of it.

Summarizing the thread. It's great idea to have rationale for all rules, but it's so big thing to do, that even initiator of idea don't want to make that happen.


Android: Set up proxy on mobile data

I can't edit the APN of my service provider. Is there any other way to set up the proxy on mobile data, without WLAN connection on Android?

You might try giving ProxyDroid a try. It didnt work for me, I ended up having to edit the APN's anyways. But it might for you. Even with root you are unable to modify the APN? Might need a custom ROM.

My solution: I added a new APN (which was possible), copied all the information of the default mobile providers APN and added the proxy.


Get RequestTelemetry (or ITelemetry) in derived ActionFilterAttribute using dependency injection

How to get the object of ITelemety object in an ASP.NET Core ActionFilterAttribute using dependency injection?

Platform - .Net Core

What is required : ITelemetry  object
 public class RequestLogActionFilterAttribute : ActionFilterAttribute
 {
    private readonly ITelemetry telemetry;

    public RequestLogActionFilterAttribute(ITelemetry telemetry)
    {
        this.telemetry= telemetry;
    }
 }

Need to resolve ITelemetry object to add the custom Global Properties in the request context.
Content: https://docs.microsoft.com/en-us/azure/azure-monitor/app/custom-operations-tracking
Content Source: https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/azure-monitor/app/custom-operations-tracking.md
Service: application-insights
Edited: Added doc details.

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

ID: 62521082-c9fb-646f-6db0-2cdabe486dab
Version Independent ID: ebf938ec-1d97-1cfd-ad28-5e616990d658
Content: Track custom operations with Azure Application Insights .NET SDK
Content Source: articles/azure-monitor/app/custom-operations-tracking.md
Service: application-insights
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@amigup, Thanks for leveraging Azure docs feedback channel! Could you please share the Azure document for which this feedback is applicable to?

@AjayKumar-MSFT Thanks for your prompt response. I've updated the Content, Content Source and Service name (pasting those below too.)
Content: https://docs.microsoft.com/en-us/azure/azure-monitor/app/custom-operations-tracking
Content Source: https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/azure-monitor/app/custom-operations-tracking.md
Service: application-insights

@amigup, Thanks for sharing the document details, we are taking a look into this and will get back to you soon.

@amigup You would first need to register your custom filters with the framework IoC. And then use the ServiceFilter attribute to add the custom filters to the controller method and class. Please refer to this blog post and this wiki that explains this in greater detail.
Also, on a side note, please be aware that this channel is only for driving improvements related to the Azure documentation. The best place for specific answers about implementations are going to be the MSDN and Stack Overflow forums. We actively look through posts in the forums, and will do our best to get you going in the right direction!

@amigup We will now proceed to close this thread as resolved, but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

Thanks @BhargaviAnnadevara-MSFT. I'd a question regarding dependency injection of  ITelemetry object in custom ActionFilterAttribute class. The custom ActionFilterAttribute class is already been injected through global filter; however, I could not able to inject the  ITelemetry instance in it. Can you please assist the way forward to achieve that?

@BhargaviAnnadevara-MSFT - Can you please assist on the question? Also as mentioned by you, I've posted the query on Stackoverflow. Can you or anyone from Azure application insights team assist on it?

@amigup Thanks for reverting. I shall go through the mentioned resources and get back to you!

@BhargaviAnnadevara-MSFT - Any update on this question? Please assist by letting me know how the asked requirement can be achieved.

adding @cijothomas

@cijothomas - Can you please assist on this query?

@cijothomas, @mrbullwinkle - can you please assist on this query?

ITelemetry is not available for constructor injection. To enrich any ITelemetry, use TelemetryInitializers. You may want to get access to httpcontext inside the TelemetryInitializer, which may contain the information required to enrich ITelemetry.

Thanks @cijothomas - Currently, I've used ITelemetryInitializer to store ITelemetry object in HttpContext.Items and later retrieving the object in the custom ActionFilterAttribute. The implementation is done as mentioned in this link. The way it is implemented is more like a workaround instead of appropriate solution. The solution I'm looking is --- to inject ITelemetry object in custom ActionFilterAttribute which seems NOT to be possible.

@cijothomas - Do you think with the suggested approach, there would be a side effect in terms of performance?

I am sorry I cannot comment on the side effects of the workaround in the link.


How to initialize component

Hello,
I created smart component using "connect" like below.
let Home = ({ text }) => {
	return (
		<div>{text}</div>
	);
};
Home = connect(
	(state) => {
		return {
			text: state.text
		};
	},
	null
)(Home);
export default Home;

Now, where should I write my ajax call to get server data ("text" in this case) to initialize my component?

I’d create an async action creator:
export function loadText(loader) {
  return dispatch => {
    dispatch({ type: 'LOAD_TEXT_STARTED' });

    loader()
      .then(data => {
        dispatch({ type: 'LOAD_TEXT_SUCCEEDED', text: data.text })
      })
      .catch(error => {
        dispatch({ type: 'LOAD_TEXT_FAILED', error })
      });
  }
}

And then simply dispatch the action passing the method that loads the data:
import { loadText } from './reducers/loadText';

const dataLoader = () => fetch('/api/data')
  .then(response => response.json());

store.dispatch(loadText(dataLoader));

The dispatching can take place in any appropriate part of your app. If the app is small, I’d do it right where the store is created.
Additionally, you’ll need to create a reducer that handles LOAD_TEXT_SUCCEEDED actions and updates the store with the new text.

Also feel free to check out https://github.com/reactjs/redux/tree/master/examples/async and other examples :wink:

@iamakulov  Thanks lot for your answer. I understood how to dispatch for initial loading.

The dispatching can take place in any appropriate part of your app. If the app is small, I’d do it right where the store is created.

Now, my application wouldn't be small. I have scenario where I need to initialize a component with fresh data whenever it gets called.
Now, I have three case where my component gets called.
1). When I simply click on link to go to "home". <Link to="/home"/>
2). When I do dynamic routing to "home". store.dispatch(push("/home");
3). When user sometimes directly change URL in brwoser and hit "Enter". http://localhost:8080/myapp/home

The dispatching can take place in any appropriate part of your app

So, I actually don't know what is appropriate part of my app where I can handle all three scenarios?
Thanks again
Manan V. Panchal

@mananvpanchal, do you have any action that is triggered when a user switches to a route? If so, I’d create a middleware that listens for such switch actions, checks if the switch is performed to /home, and dispatches an additional loadText async action if it is. This way is quite verbose (as the new middleware is created), but I don’t know the more elegant one.

@iamakulov Thank you very much. I will try to implement triggering actions on route switching. Need to research on route switching. That way I can handle all three scenarios. But, need to research first that how can I know that "route is going to switch now".

@iamakulov I found something like this.
<Route path="home" component={Home} onEnter={loadHome}/>
and I write "loadHome" like this
const loadHome = () => { 	store.dispatch({type: "LOAD_HOME"}); };
Using this, I can handle all that three scenario.
Thanks.


fix(versions): update Activiti/activiti-cloud-full-chart-security versions

UpdateBot pushed helm dependency: activiti-cloud-full-example to: 7.1.110

UpdateBot commands:
updatebot push-version --kind helm activiti-cloud-full-example 7.1.110


Errors running Escoria in Daïza tutorial

Hi, following line by line the Escoria in Daïza tutorial with Escoria3 I fail to run even on the first scene ( https://fr.flossmanuals.net/creating-point-and-click-games-with-escoria/creat-your-scene/ ) , with AssertionFailed: "Errors in File item, Background item area is not Area2D"

I have the same problem.
I discovered Escoria through fr.flossmanuals.net Daïza tutorial and failed making it at first scene.
Would it be possible to update this ticket with steps to make it work?

FYI, while Escoria 3.x is underway, Escoria 2 was ported to Godot 3.2 (branch esc2-godot3.2) and the Escoria in Daïza was updated for Godot 3.2 as well :)


[helm-charts] Expose NGINX service to users

NGINX pod is the main entry pod to the OPEA services. In most cases, the NGINX service should have the service.type.loadBalancer. This is currently not exposed in any of the helm charts but hard coded to NodePort.

we'll make it configurable using the helm value 'nginx.service.type'


copy indicator on 0% when copying to SD card

Describe the bug
When copying file from hdd to SD card, the file is being copied but there is no visual indication of it happening. When I check the status on "Ongoing task" it's stuck at 0% until the file is actually copied (it was 2,5GB file)
To Reproduce
Steps to reproduce the behavior:

Go to any file on HDD (I've chosen 2,5Gb because it takes some time)
Click on drag and drop file to SD card
check the ongoing operations on the right side bottom corner
the progress bar is stuck at 0% until the file is actually copied then it shows "copy complete"

Expected behavior
It should visually show what is the status of the copied file in % and graph.
Screenshots

Desktop (please complete the following information):

OS Version:  Windows 10 20H2 19042.746
App version: v<IP_ADDRESS>

Additional context
N/A
Log file
Please upload the log file here so that we can understand your issue better. You can access it from Settings->About->Open log location. You can also find the log file manually by following [this](http
debug.txt
debug_fulltrust.txt
s://github.com/files-community/Files/wiki/Opening-the-log-file) guide.

Merging with #2543

Merging with #2543


docs: translate Legacy React APIs

Closes #545
Description
Translate the Legacy React APIs page.
Page URL:  https://id.react.dev/reference/react/legacy

This is quite small, let's ship this @resir014, need your approval

Thanks for the correction, mas @resir014 @mazipan.


Typescript migration

Left in MVP:

check if a match is already on the calendar before adding it
deployment tidying

Future feature:

handle an existing event changing


💡[FEATURE]: Adding more appropriate PR template

Is your feature request related to a problem? Please describe.
Yes, the request for adding a pull request template is related to the problem of inconsistent and poorly defined current PR template. Often, pull requests lack necessary details, making it difficult for reviewers to understand the changes, the reasons behind them, and how to test them. This can lead to delays in the review process, increased back-and-forth communication, and potential oversight of critical issues.
Describe the solution you'd like
The solution is to implement a standardized pull request template. This template should include sections that prompt the author to provide essential information, such as:
A brief description of the changes.

The issue or feature being addressed (linked to relevant issue tracker entries).
Screenshots or GIFs (if the changes include UI modifications).
Checklist for confirming code adheres to coding standards, tests are added/updated, and documentation is updated.

@Anishkagupta04 @varshith257 please assign me this issue under gssoc'24

@Anishkagupta04 I have raised this issue because of the current poorly structured PR template, you can take a look at it


Tyring to install via npm not working

I am trying to install vue-dropzone via npm but it isn't working.
npm install<EMAIL_ADDRESS>-save

What does the error say?

I get the following error after running npm install<EMAIL_ADDRESS>zsh: no matches found<EMAIL_ADDRESS>

It's working perfectly fine for me
npm install<EMAIL_ADDRESS>What OS? Anything special about your setup?


Links are no longer working..

[Enter feedback here]
The script
https://go.microsoft.com/fwlink/?linkid=867842  CreateSrsMedia
and
https://go.microsoft.com/fwlink/?linkid=851168  deployment kit
Are no longer working, both are returning 404..

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

ID: 6f8b204f-9650-d268-8566-7a75ba0a1b6a
Version Independent ID: 9a963e63-6716-7522-8abe-c8a407d3a46d
Content: Build a Microsoft Teams Rooms image - Microsoft Teams
Content Source: Teams/rooms/console.md
Service: msteams
GitHub Login: @dstrome
Microsoft Alias: dstrome

First link already in https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/8932


fix(docs): typo, refactor(docs), license(): copyright and author name added

This is the PR for

Fix short arrow syntax type in the documentation.
Convert HTML to markdown format.
Included license in the documentation.
Added copyright year and author name

I am going to close this since it's now outdated.


Add Pastebot.app v2.0 Beta 5

Checklist

[x] The commit message includes the cask’s name and version.
[x] brew cask audit --download pastebot is error-free.
[ ] brew cask style --fix pastebot left no offenses.

Additionally, when adding a new cask:

[x] Checked there are no open pull requests for the same cask.
[x] Checked there are no closed issues where that cask was already refused.
[x] When naming the cask, followed the token reference.
[x] brew cask install pastebot worked successfully.
[x] brew cask uninstall pastebot worked successfully.

brew cask style --fix pastebot did not pass without offenses. Travis caught one.

Since the beta is the only available version (there is no stable), please submit this to the main repo.