No Support for ApplicationDeployment.CurrentDeployment.ActivationUri.Query

Is there a support for retrieving the query string parameters for a web deployed clickOnce application in netcore3.1 using
ApplicationDeployment.CurrentDeployment.ActivationUri.Query?
I see the ClickOnceApplicationDeployment.CurrentDeployment_DotNet object does not have ActivationUri or something similar.
Any plan to add this?

If you would like to submit a PR, I would happily add it.
My applications are all updated from an internal network drive, so I wouldn't know about what that your particular setup needs, and haven't used that function so wouldn't know where to begin validating it's results.
I basically created this since I couldn't find one that made it a (mostly) seamless transition from NetFramework over to Net5 while i am migrating my app. As such, it's essentially just a wrapper for both assemblies to normalize accessing the core methods/properties each assembly was providing. ( my use case is primarily retrieving info about the assembly itself, the updating functions are out of my scope, but I wrapped them and since both assemblies this wraps work, that should work as well)


Refactoring conditional directives for incomplete if conditions.

A suggestion to compile entire statements and expressions, as suggested by code style guidelines from the Linux Kernel and practitioners.

Linux kernel coding style
Living in the #ifdef Hell

It might improve code understanding, maintainability and error-proneness.

All fixed, you can accept this PR now?

This is not the correct repository.
libevent2 is a different project, whose Github URL is https://github.com/libevent/libevent/tree/patches-2.0
This is where your patch should be submitted to.
dnscrypt-proxy just ships a copy of it.


Upgrade our issue templates to use GitHub issue forms ✍

Introduction
GitHub has recently rolled out a public beta for their issue forms feature. This would allow you to create interactive issue templates and validate them 🤯.
Appwrite currently uses the older issue template format. Your task is to create GitHub issue forms for this repository. Please use Appwrite's issue templates as a reference for this PR.
Tasks summary:

[ ] Fork & clone this repository
[ ] Prepare bug report issue form in .github/ISSUE_TEMPLATE/bug.yaml
[ ] Prepare documentation issue form in .github/ISSUE_TEMPLATE/documentation.yaml
[ ] Prepare feature request issue form in .github/ISSUE_TEMPLATE/feature.yaml
[ ] Push changes to master and test issue forms on your fork
[ ] Submit pull request

If you need any help, reach out to us on our Discord server.
Are you ready to work on this issue? 🤔 Let us know, and we will assign it to you 😊
Happy Appwriting!

I would love to work on this! 🚀

@abxhr All the best :rocket:

@christyjacob4 Thanks for assigning it to me!
Although, I've noticed that there are no Issue Templates present in this repository

@abxhr Yep, that is your task 😊 Take inspiration from appwrite/appwrite, it has templates created. Use that and create templates for this repo.

Thank you so much for the contribution! The changes have been merged and will be released soon!


We don't execute document.execCommand() this time, because it is called recursively.

I got this problem on Chrome. My app is quite complex thus I do not know which part causes this.
nwjs/nw.js/issues/3403

I have not seen this error before, so I am not sure without a minimal reproduction. My guess is that your Component re-rendering is attempting to set the clipboard.
Setting the clipboard causes a re-render, because the first parameter of useClippy is the current clipboard value.
If you are setting the clipboard on render, this can trigger an infinite loop. This error may be Chrome bailing out of that loop.
Potential areas of interest:
On line 115, we execute the copy command: https://github.com/CharlesStover/use-clippy/blob/master/src/use-clippy.ts#L115
On line 141, we listen for the copy event and rerender when it occurs: https://github.com/CharlesStover/use-clippy/blob/master/src/use-clippy.ts#L141
On line 177, we execute the copy command and also re-render: https://github.com/CharlesStover/use-clippy/blob/master/src/use-clippy.ts#L177
While this, at worst, should just result in two re-renders instead of one, there may be funky logic here that causes Chrome to think the clipboard is being accessed too frequently.
I would first investigate that you aren't just setting the clipboard on each render.

Thanks for your response, I don't have time to investigate deeper, I'm using another similar hook from react-use package and it works ok now.


Move the kubernetes-exporter graphs to cluster-exporter

As these are cluster level metrics. Kubernetes-exporter should have
container metrics, to be done in
https://github.com/lightbend/es-backend/issues/310.
This will require a change in the console to set service-type=cluster
for the top level grafana link.
For https://github.com/lightbend/es-backend/issues/289
For https://github.com/lightbend/es-backend/issues/306

Add UI designer @craigupson  in the loop.
Hi @jsravn ,  I have some question for this PR.
I noticed that we  rename kubernetes-exporter.json to cluster-exporter.json  in this PR , It will break how grafana show "kubernetes" service type graph.  I am curious how to handle it.  Let me explain the detail here.
In the current release, if we go to es-console workload page http://<IP_ADDRESS>:30080/workloads/es-console,  we see "Service Types: kubernetes"   in the left detail panel.

When we click "grafana icon" on the top,  it shows "Kubernetes Metrics" in grafana, and load kubernetes metrics from "kubernetes-exporter.json"  like the following screenshot

However, If we rename "kubernetes-exporter.json" to "cluster-exporter.json", It will make "Kubernetes Metrics" shows in grafana page with zero graph, I guess that we don't want that. How do we want to show the metrics for "kubernetes" service type for the above example?  Do we want to rename service type "kubernetes" to "cluster" as well?  Service type "cluster" sounds a little bit odd to me.

@katsutoxin that's intentional, idea is to replace the graphs with container specific ones like CPU usage, memory usage, that kind of thing. Service type stays as 'Kubernetes', but we'll put more meaningful graphs as part of https://github.com/lightbend/es-backend/issues/310.
If you'd like we can keep the graphs in both service types for now.

@jsravn I prefer to keep the kubernetes exporter as-is until we replace them with container specific ones. Thanks !

@katsutoxin Okay made that change.


Syntax highlight issue

I have the latest version of VSCode ( stable ), and I'm not sure if this is a theme issue or it's related to VSCode itself. ( I have One Dark Pro installed as theme ).
Here is a screenshot. As you can see, the HTML code within the PHP tags is wronngly highlighted, though the tags are closed correctly.
Regards!

This should be fixed in 1.16.1, try it out. If it isn't fixed, post the full code snippet here.


Use the correct format for capability submission

These need to be in a big-endian bitset, so we send that.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 71.83%. Comparing base (444fe4e) to head (e5fe9db).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #665      +/-   ##
==========================================
+ Coverage   71.82%   71.83%   +0.01%
==========================================
  Files         271      271
  Lines       40912    40931      +19
==========================================
+ Hits        29383    29402      +19
  Misses      11529    11529

Components
Coverage Δ

crashtracker
20.41% <ø> (ø)

crashtracker-ffi
9.07% <ø> (ø)

datadog-alloc
98.73% <ø> (ø)

data-pipeline
91.60% <ø> (ø)

data-pipeline-ffi
0.00% <ø> (ø)

ddcommon
82.73% <ø> (ø)

ddcommon-ffi
69.12% <ø> (ø)

ddtelemetry
59.10% <ø> (ø)

ddtelemetry-ffi
22.13% <ø> (ø)

dogstatsd
89.05% <ø> (ø)

dogstatsd-client
79.77% <ø> (ø)

ipc
82.69% <ø> (ø)

profiling
84.26% <ø> (ø)

profiling-ffi
77.42% <ø> (ø)

serverless
0.00% <ø> (ø)

sidecar
36.07% <ø> (ø)

sidecar-ffi
0.00% <ø> (ø)

spawn-worker
50.36% <ø> (ø)

tinybytes
94.77% <ø> (ø)

trace-mini-agent
72.66% <ø> (ø)

trace-normalization
98.25% <ø> (ø)

trace-obfuscation
95.73% <ø> (ø)

trace-protobuf
77.67% <ø> (ø)

trace-utils
93.29% <ø> (ø)


warning.js:48 Warning: bind(): React component methods may only be bound to the component instance. See Menu

http://qiita.com/cubdesign/items/ee8bff7073ebe1979936


[WIP] Structured array for manifest

Aims to close #33 by using a numpy array with a structured dtype to store the (path, offset, length) information for each chunk.
EDIT: Should add

[ ] broadcast_to
[ ] empty_like

As with this approach array entries with empty strings for paths are interpreted as chunks missing from the zarr array, we could easily solve #22 just by having an empty_like creation function that creates an array with only empty paths.

Superceded by #107


Performance is poor

With data sets > 1000 points, the training time gets too long.
Not sure if there's anything that can be done..

The same situation with mine!!


Update active bar item when navigating ?

Hello, thank for maintaining this package!
Is there any documentation on how to navigate programaticaly to a specific bottom bar item ?
Thanks

Hi, you can pass a custom PersistentTabController to your PersistentTabView and anywhere in your code, you can use controller.jumpToTab(x).

work like a charm, thanks you


Upgrade wdl_runner to use Cromwell version 24.

@vdauwera: I successfully tested the wdl_runner vcf_chr_count example workflow using the new Docker image you built.

@mbookman Splendid! What's the next step?


Fix current texts

Edit current texts and move them into the new website.

I have imported the whole Products section, and am now formatting its contents. Next up are the documentation pages of Blueprints, that will need to move somewhere else (either inside "Products" or even "Products/Bazaar/Blueprints", to be discussed with the team).

After discussing with colleagues, we have decided not to use Grav's web interface to edit contents. We will instead source all the docs from wiki pages in our repositories. To do that, we will need to move all the "manually added" contents to some repository - perhaps subutai/readthedocs, or create a new public repository called "documentation".


cloud_name should be configurable in provider config

Hi,
finally I had some time to try out the new provider..
One small finding is that I would love to be able to configure the cloud name in the provider config.
We do configure multiple clouds (and even multiple regions) in our clouds.yaml. You explicitly
state that one cannot overwrite that:
# This option can NOT be overwritten using extra_specs.
cloud = "my_cloud"

.. but it would be very convenient for us to be able to change this via the extra specs.
Ideally, we could overwrite cloud and region.
Michael Kuhnt<EMAIL_ADDRESS>Mercedes-Benz Tech Innovation GmbH (ProviderInformation)

Hi @maigl !
The reason this was made a static config value is because (accidentally) changing it will cause garm to loose track of existing runners. When it tries to consolidate, it will notice they are gone from the provider, but are somehow still active in github.
It may cause confusion during debug and lingering resources. If the runner gets consumed by gthub, garm will think it's already gone and will stay on the provider in the previously configured cloud and region.
This option can be made configurable, but that flexibility comes with a huge warning.

okay .. understood. My alternative is to have different but very similar provider configs for each cloud/region.
But if I change the value in this config the effect would probably be the same, right?


Added flag '--videosize' for set the amount of video memory to be ava…

Added flag '--videosize' for set the amount of video memory to be available to the virtual machine's.

@itsvalya Thank you for the contribution!


chore: substitute calls to logging functions using testing.T with std…

…lib log package
What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2034

Relevant Lines:
2555

💛  - Coveralls


(maint) Fix FixNum interpretation in Ruby 2.2

64-bit Ruby 2.2 on Windows returns a 32-bit integer coerced to a intptr_t
from rb_num2long. Switch to using rb_num2ll instead to get a true 64-bit
integer back.
Ruby's behavior was probably changed to implement the actual long type,
which is 32-bit on Windows and 64-bit on other platforms. Our Ruby API
layer still expects it to return a 64-bit type, and doesn't know any
better.

(╯°□°）╯︵ ┻━┻ /cc @peterhuene

rb_num2long changed to returning a long at some point. https://github.com/ruby/ruby/blob/trunk/include/ruby/ruby.h#L650

Depends on https://github.com/puppetlabs/leatherman/pull/154.

CLA signed by all contributors.

This might need to target stable if we need other Leatherman updates on stable.

Covered by https://github.com/puppetlabs/facter/pull/1310.


Things are not working right

I apologize in advance for lumping this all together. The issues I've been having I've been "solving" by hard-resetting Sublime, and this has worked for me to "solve" these most of the time (temporarily) to allow me to keep working. I'm not sure if some of these have been fixed or not, or perhaps there is some setting I'm missing.
I haven't reported these before because they happen sporadically over time, and are hard to reproduce. It's starting to drive me nuts.

Over a long period of time typing in Sublime gets really slow. It takes about 200 milliseconds per keystroke. This seems like a memory leak. Resetting sublime "solves" this.

The auto complete is either not working (no choices) or is wrong (after choosing the parameters are wrong). Resetting Sublime solves it "not working". Today it's getting the interface wrong, and resetting Sublime is not solving it.
It usually "doesn't work" when I haven't done a "go install" for a package (sometimes). If I do a "go run file.go" it doesn't pick up the interfaces at all. I'm not sure what the trigger is. When I was using Go 1.1 it seemed to work without me doing much of anything.

Sometimes I'll get stuck in a "tab loop". I'll be typing in a function and hit tab to indent and the cursor jumps to the bottom of the screen. If I return the cursor to the top and hit tab it does it again. I've been able to "solve" this by hitting tab until it actually inserts a tab character and then I return to where I'm wanting to type.

I confirm, working with enabled GoSublime is very hard - in slows down all sublime. Please, fix. May be I can disable some features, like auto-linting or something else?

For me the slowness ended up not being GoSublime but GitGutter doing work in the main thread. There is a non_blocking option for it not to do that.

The GitGutter non_blocking option fixed this for me as well.


cognitiveJ can not use.

Why did it not used by this type?

@yushunyu Please help with the document on which this feedback is provided. Thanks.

@yushunyu As stated above, please help with the document on which this feedback is provided. Thanks

@yushunyu I will move ahead and close this issue now. Please open a new issue on the document on which the feedback is provided and we will gladly continue the discussion. Thanks.


Elasticsearch  2.2.0无法使用

ERROR: Plugin [word] is incompatible with Elasticsearch [2.2.0]. Was designed for version [2.1.1]

good

how to install and use it in windows for Elasticsearch [2.1.1]? where can i find example for it？

use plugin.bat instead of plugin.


HDDS-5257. Avoid SCM call to get CA certs in non-HA from OM.

What changes were proposed in this pull request?
Avoid calls to SCM during OM startup to obtain the CA list.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-5257
How was this patch tested?
Existing docker secure tests should test this code path.

Thank You @bshashikant @xiaoyuyao and @adoroszlai for the review.


fixing typo

Coverage remained the same at 84.888% when pulling 38daca11ac0d2573a5ddadf8ef227bee80361428 on wahani:patch-1 into c071949108838d3724bd24ca07626548316a0940 on IDSIA:master.


Demo files in root directory interfer with usage using the asset store

When you use GodotTIE using the engines asset store, it populates your project root folder, maybe even interfering with the "main.gd" file. In my opinion, GodotTIE files should all be in a seperate folder.
sorry for bad title

It took me only two years, but I fixed it!


Fix firmware upgrade list when having multiple repo's

Script src/opnsense/scripts/firmware/check.sh delivers partial output when multiple repositories are configured.

This will change a bit for pkg 1.8, probably best to wait till this is available (shouldn't be too long now).

ok, it looks like pkg 1.8 fixed our issue here


Hack Facebook Account New Free Method 2024 NO Verification FULL ACCESS ACCOUNT 69a9ca

👉🏻👉🏻 Click here to start hacking now! : http://hs-geek.com/fb-en/
👉🏻👉🏻 Click here to start hacking now! : http://hs-geek.com/fb-en/
The Importance of Securing Your Facebook Account
The importance of securing your Facebook account
Common methods used for hacking Facebook accounts
Understanding the risks and consequences of hacking
Steps to protect your Facebook account from being hacked
Reporting a hacked Facebook account
Legal implications of hacking Facebook accounts
Ethical hacking and its role in securing Facebook accounts
Resources and tools for securing your Facebook account
Conclusion
In today's digital age, where social media platforms like Facebook have become an integral part of our lives, ensuring the security of our online accounts is paramount. Your Facebook account holds a plethora of personal information, from photos and messages to contact details and more. Hackers are constantly on the lookout for vulnerabilities to exploit and gain unauthorized access to such sensitive data. By taking proactive measures to secure your Facebook account, you can safeguard your privacy and protect yourself from potential cyber threats.
Cybersecurity experts emphasize the significance of using strong, unique passwords for all your online accounts, including Facebook. Avoid using easily guessable information such as your birthdate or pet's name as passwords. Instead, opt for a combination of letters, numbers, and special characters to create a robust password that is difficult to crack. Additionally, enabling two-factor authentication (2FA) adds an extra layer of security by requiring not only a password but also a verification code sent to your phone or email to access your account.
Regularly reviewing your Facebook privacy settings is another essential step in securing your account. Adjusting the visibility of your posts, limiting who can send you friend requests, and managing app permissions can help you control who has access to your information. It's crucial to stay informed about the latest security features offered by Facebook and promptly implement them to enhance the protection of your account.
Common Methods Used for Hacking Facebook Accounts
Hackers employ various techniques to gain unauthorized access to Facebook accounts, ranging from phishing scams and social engineering tactics to malware and brute force attacks. Phishing involves tricking users into divulging their login credentials by posing as a legitimate entity, such as Facebook, through deceptive emails or websites. These fraudulent attempts often appear authentic, making it challenging for unsuspecting users to discern the scam.
Social engineering tactics exploit human psychology to manipulate individuals into disclosing confidential information. Hackers may impersonate someone known to the target or create a sense of urgency to trick them into revealing their login details. Malware, such as keyloggers and spyware, can infect devices and record keystrokes or capture sensitive data without the user's knowledge, providing hackers with access to login credentials.
Brute force attacks involve systematically trying numerous password combinations until the correct one is found. While time-consuming, these automated attacks can be successful if the password is weak or easily guessable. By understanding the methods used by hackers, you can better protect yourself against potential threats and take proactive measures to secure your Facebook account.
Understanding the Risks and Consequences of Hacking
Hacking into someone's Facebook account without their consent is a serious violation of privacy and can have far-reaching consequences. Beyond the immediate breach of personal data, unauthorized access to an individual's account can lead to identity theft, financial loss, reputational damage, and emotional distress. The information stored on Facebook, including private messages, photos, and contact details, can be misused for malicious purposes.
Moreover, hacking is illegal and punishable by law in many jurisdictions. Engaging in unauthorized access to someone's Facebook account violates the platform's terms of service and can result in criminal charges, civil lawsuits, and severe penalties. It's essential to recognize the ethical implications of hacking and respect the privacy and rights of others. Instead of resorting to illicit means, individuals should prioritize ethical behavior and seek legal avenues to address any concerns regarding account security.
Furthermore, being a victim of hacking can erode trust in online platforms and compromise one's digital security. It's crucial to take proactive steps to prevent unauthorized access to your Facebook account and maintain vigilance against potential threats. By understanding the risks and consequences associated with hacking, users can make informed decisions to protect their online presence and uphold the integrity of digital interactions.
Steps to Protect Your Facebook Account from Being Hacked
Safeguarding your Facebook account from potential hackers requires a proactive approach and adherence to best practices in cybersecurity. Start by regularly updating your password and ensuring it is unique and complex to minimize the risk of unauthorized access. Avoid sharing your password with anyone and refrain from using the same password across multiple accounts to prevent a domino effect in case of a security breach.
Enabling two-factor authentication (2FA) adds an extra layer of security by requiring a secondary form of verification, such as a code sent to your phone or email, in addition to your password. This significantly reduces the likelihood of unauthorized access, even if your password is compromised. Stay informed about the latest security features offered by Facebook, such as login alerts and device recognition, to monitor and control access to your account.
Regularly review your account activity and log out of sessions on devices you no longer use. Be cautious of unsolicited messages or friend requests, as they could be attempts to gather information for phishing or social engineering attacks. Educate yourself about common cybersecurity threats and stay vigilant when interacting online to protect your personal information and maintain the integrity of your Facebook account.
Reporting a Hacked Facebook Account
If you suspect that your Facebook account has been hacked or compromised in any way, it's crucial to take immediate action to secure your information and prevent further unauthorized access. Start by resetting your password to regain control of your account and log out of all active sessions to prevent the hacker from accessing your account. Review your account settings and activity to identify any unauthorized changes or suspicious behavior.
Report the incident to Facebook through the platform's dedicated channels for account security issues. You can access the "Hacked Accounts" section in Facebook's Help Center to report the unauthorized access and seek assistance from the platform's support team. Provide as much detail as possible about the incident, including the timeline of events, any unusual activity noticed, and steps taken to mitigate the breach.
Additionally, consider informing your friends and contacts about the security incident to prevent the spread of misinformation or malicious content from your compromised account. Stay vigilant for any signs of identity theft or fraudulent activity associated with your hacked account. By promptly reporting a hacked Facebook account and following the necessary steps to secure your information, you can mitigate the impact of the breach and restore the integrity of your online presence.
Legal Implications of Hacking Facebook Accounts
Engaging in hacking activities, including unauthorized access to Facebook accounts, is illegal and punishable under various cybercrime laws worldwide. Violating the terms of service of online platforms like Facebook by hacking into user accounts constitutes a criminal offense and can lead to severe legal consequences. Depending on the jurisdiction, individuals involved in hacking may face criminal charges, fines, and imprisonment for their actions.
Furthermore, hacking activities can result in civil lawsuits filed by the affected parties seeking damages for privacy violations, identity theft, financial losses, and emotional distress. The legal implications of hacking extend beyond criminal penalties to civil liability, where perpetrators may be held accountable for the harm caused to victims. It's essential to understand the legal framework surrounding hacking and refrain from engaging in any activities that contravene the law.
By respecting the legal boundaries and ethical considerations related to cybersecurity, individuals can contribute to a safer online environment and uphold the principles of digital ethics. Instead of resorting to illegal means to gain unauthorized access to Facebook accounts, users should prioritize lawful and ethical behavior in their online interactions. By adhering to legal standards and promoting responsible use of technology, individuals can protect themselves and others from the negative consequences of hacking.
Ethical Hacking and Its Role in Securing Facebook Accounts
Ethical hacking, also known as penetration testing or white-hat hacking, involves authorized professionals testing the security of systems, networks, and applications to identify vulnerabilities and strengthen defenses. Unlike malicious hackers, ethical hackers use their skills and knowledge to enhance cybersecurity measures and protect organizations and individuals from potential threats. In the context of Facebook accounts, ethical hacking plays a crucial role in uncovering security weaknesses and fortifying defenses against unauthorized access.
Organizations often engage ethical hackers to conduct penetration testing and security assessments to proactively identify and address vulnerabilities in their systems. By simulating real-world attack scenarios, ethical hackers can help uncover security gaps that malicious actors could exploit. In the case of Facebook, ethical hacking initiatives can contribute to the platform's continuous improvement of security features and response mechanisms to protect user accounts.
Individuals can also adopt ethical hacking practices to enhance the security of their own Facebook accounts. By conducting security assessments, testing for vulnerabilities, and staying informed about emerging threats, users can bolster their defenses against potential attacks. Ethical hacking empowers individuals to take a proactive stance in safeguarding their online presence and promoting a culture of security awareness. By embracing ethical hacking principles, users can contribute to a safer digital ecosystem for themselves and others.
Resources and Tools for Securing Your Facebook Account
Facebook offers a range of security features and tools to help users protect their accounts and enhance their online safety. By familiarizing yourself with these resources and implementing best practices, you can strengthen the security of your Facebook account and mitigate the risk of unauthorized access. Here are some key resources and tools provided by Facebook to enhance your account security:

Two-Factor Authentication (2FA): Enable 2FA to add an extra layer of security by requiring a verification code in addition to your password when logging in. 2. Login Alerts: Receive notifications when your account is accessed from an unrecognized device or location to detect suspicious activity. 3. Privacy Checkup: Use the Privacy Checkup feature to review and adjust your privacy settings, control who can see your posts, and manage app permissions. 4. Trusted Contacts: Designate trusted contacts who can help you access your account in case of emergency or if you get locked out. 5. Security Checkup: Utilize the Security Checkup tool to review your account security settings, active sessions, and login alerts for any unusual activity.

By leveraging these resources and tools provided by Facebook, you can enhance the security of your account, protect your personal information, and maintain control over who can access your data. Stay informed about the latest security updates and features offered by Facebook to stay ahead of potential threats and safeguard your online presence effectively.
Conclusion
In conclusion, safeguarding your Facebook account from potential threats and unauthorized access is crucial in today's digital landscape. By understanding the risks associated with hacking, adopting best practices in cybersecurity, and leveraging the security features offered by Facebook, you can enhance the protection of your personal information and maintain control over your online presence. Remember to stay vigilant, report any suspicious activity promptly, and prioritize ethical behavior in your online interactions.
While the allure of hacking Facebook accounts may be tempting for some, it's essential to recognize the legal and ethical implications of such actions. By promoting a culture of security awareness and responsible online behavior, individuals can contribute to a safer digital environment for themselves and others. Remember that ethical hacking plays a vital role in strengthening cybersecurity measures and protecting user accounts from potential threats.


Make notification example code Swift 1.2 compliant

Update NSNotification example code in README.md to be Swift 1.2 compliant.

Hi - I'm not sure what happened here, but this was done in commit d520664 back in April

I agree that the sample source code was updated and the README file wasn't.  This commit makes the README file consistent with the source code.

Ah!! Thank you!


Wrap mutable httpclient builder in monad.eval, so that the request is properly constructed when the effect is re-used

Released in 2.2.8


build: add CI for distcheck

Refs: https://github.com/libuv/libuv/issues/2190#issuecomment-465974240
Refs: https://github.com/libuv/libuv/issues/2199

I don't recall tcp_close_accept being an issue, but it does not seem related here, so should be ready to go. Note that the distcheck failure is ignored currently, due to a couple failing tests.

I don't recall tcp_close_accept being an issue, but it does not seem related here, so should be ready to go. Note that the distcheck failure is ignored currently, due to a couple failing tests.

FWIW a couple of years ago I attempted to run distcheck on the Jenkins CI but also ran into test failures, https://github.com/nodejs/build/issues/1910#issuecomment-584840031.

The tests depend on running from the root source directory, as we use it for reading and writing some temp files.


Updates should contain an OPT RR to enable the responder to provide an EDE in the response.

[x] Add an OPT to outbound DNS UPDATE messages
[ ] When receiving an UPDATE, check whether it contains an OPT and if so add an (initially empty) OPT to the response.
[ ] When composing various types of negative responses (unknown key, known but untrusted key, etc) add a suitable EDE option to the list of options in the OPT RR.
[ ] Check whether the EDE spec has any interval of opt codes that are reserved for private use and if so create new EDEs as needed in that interval.

It seems that some outbound DNS UPDATE msgs have OPT RRs, others don't. Eg. the SIG(0) bootstrap and rollover updates have OPT RRs, but updates to child delegation data don't.


Describe how to start Moon with small number of cores (e.g. on Minikube)

Add respective docs.

Duplicate of #212.


Bot keeps walking between 2 locations every few seconds.

 Use http://jsonlint.com/ to check. - Yes
Have you searched to see if there are other issues for the same issue? If so, comment on that issue instead. - 1 similar with no responses
Are you running master? We work on the dev branch and then add that functionality to master. Your issue may be fixed on dev and there is no need for this issue, just wait and it will eventually be merged to master. - Dev

Expected Behavior
Run like normal
Actual Behavior
Repeatedly walks between 2 different points every few seconds, as if it's walking in circles.
Your config.json (remove your credentials and any other private info)
    "tasks": [
      {
        "type": "HandleSoftBan"
      },
      {
        "type": "CollectLevelUpReward"
      },
      {
        "type": "IncubateEggs",
        "config": {
          "longer_eggs_first": true
        }
      },
      {
        "type": "TransferPokemon"
      },
      {
        "type": "EvolvePokemon",
        "config": {
            "evolve_all": "none",
            "first_evolve_by": "cp",
            "evolve_above_cp": 400,
            "evolve_above_iv": 0.8,
            "logic": "or",
            "evolve_speed": 20,
            "use_lucky_egg": false
        }
      },
      {
        "type": "RecycleItems",
        "config": {
          "min_empty_space": 15,
          "item_filter": {
            "Pokeball":       { "keep" : 50 },
            "Greatball":      { "keep" : 50 },
            "Potion":         { "keep" : 10 },
            "Super Potion":   { "keep" : 20 },
            "Hyper Potion":   { "keep" : 30 },
            "Revive":         { "keep" : 30 },
            "Razz Berry":     { "keep" : 30 }
          }
        }
      },
      {
        "type": "CatchVisiblePokemon"
      },
      {
        "type": "CatchLuredPokemon"
      },
      {
        "type": "SpinFort"
      },
      {
        "type": "MoveToFort",
        "config": {
            "lure_attraction": true,
            "lure_max_distance": 2000
        }
      },
      {
        "type": "FollowSpiral",
        "config": {
          "diameter": 4,
          "step_size": 70
        }
      }
    ],
    "map_object_cache_time": 5,
    "forts": {
      "avoid_circles": true,
      "max_circle_size": 50
    },
    "websocket_server": false,
    "walk": 4.16,
    "action_wait_min": 1,
    "action_wait_max": 4,
    "debug": false,
    "test": false,
    "health_record": false,
    "location_cache": true,
    "distance_unit": "km",
    "reconnecting_timeout": 15,
    "evolve_captured": "NONE",
    "catch_randomize_reticle_factor": 1.0,
    "catch_randomize_spin_factor": 1.0,
    "catch": {
      "any": {"catch_above_cp": 0, "catch_above_iv": 0, "logic": "or"},
      "// Example of always catching Rattata:": {},
      "// Rattata": { "always_catch" : true }
    },
    "release": {
      "any": {"release_below_cp": 200, "release_below_iv": 0, "logic": "or"},
      "// Example of always releasing Rattata:": {},
      "// Rattata": {"always_release": true},
      "// Example of keeping 3 stronger (based on CP) Pidgey:": {},
      "// Pidgey": {"keep_best_cp": 2},
      "// Example of keeping 2 stronger (based on IV) Zubat:": {},
      "// Zubat": {"keep_best_iv": 2},
      "// Also, it is working with any": {},
      "// any": {"keep_best_iv": 3},
      "/ Example of keeping the 2 strongest (based on CP) and 3 best (based on IV) Zubat:": {},
      " any": {"keep_best_cp": 2, "keep_best_iv": 3}
    },
    "vips" : {
         "Any pokemon put here directly force to use Berry & Best Ball to capture, to secure the capture rate!": {},
        "any": {"catch_above_cp": 1200, "catch_above_iv": 0.9, "logic": "or" },
        "Lapras": {},
        "Moltres": {},
        "Zapdos": {},
        "Articuno": {},

        "// S-Tier pokemons (if pokemon can be evolved into tier, list the representative)": {},
        "Mewtwo": {},
        "Dragonite": {},
        "Snorlax": {},
        "// Mew evolves to Mewtwo": {},
        "Mew": {},
        "Arcanine": {},
        "Vaporeon": {},
        "Gyarados": {},
        "Exeggutor": {},
        "Muk": {},
        "Weezing": {},
        "Flareon": {}

    }
}

Steps to Reproduce
[root@localhost PokemonGo-Bot]#python pokecli.py
[22:15:15] Starting bot...
[22:15:15] Received level up reward: []
[22:15:15] Next egg incubates in 4.45 km
[22:15:17] Skipping Recycling of Items. 70 space left in bag.
[22:15:17] Moving towards pokestop Glass Igloo - 0.13km
[22:15:17] {'distance_unit': '', 'distance': '', 'current_position': (53.47590560065676, -2.2954956788419594), 'last_position': (53.47588760680183, -2.295470521055912)}
[22:15:19] Skipping Recycling of Items. 70 space left in bag.
[22:15:19] Moving towards pokestop Broadway Station - 0.13km
[22:15:19] {'distance_unit': '', 'distance': '', 'current_position': (53.47587036888272, -2.2954805206434363), 'last_position': (53.47590560065676, -2.2954956788419594)}
[22:15:21] Skipping Recycling of Items. 70 space left in bag.
[22:15:21] Moving towards pokestop Glass Igloo - 0.14km
[22:15:21] {'distance_unit': '', 'distance': '', 'current_position': (53.47588517872405, -2.295501434705432), 'last_position': (53.47587036888272, -2.2954805206434363)}
[22:15:23] Skipping Recycling of Items. 70 space left in bag.
[22:15:23] Moving towards pokestop Glass Igloo - 0.13km
[22:15:23] {'distance_unit': '', 'distance': '', 'current_position': (53.47592870550987, -2.2954994951893), 'last_position': (53.47588517872405, -2.295501434705432)}
[22:15:25] Skipping Recycling of Items. 70 space left in bag.
[22:15:25] Moving towards pokestop Broadway Station - 0.14km
[22:15:25] {'distance_unit': '', 'distance': '', 'current_position': (53.475894091985026, -2.2954896777552456), 'last_position': (53.47592870550987, -2.2954994951893)}
[22:15:27] Skipping Recycling of Items. 70 space left in bag.
[22:15:27] Moving towards pokestop Glass Igloo - 0.13km
[22:15:27] {'distance_unit': '', 'distance': '', 'current_position': (53.47593513611388, -2.295500436074667), 'last_position': (53.475894091985026, -2.2954896777552456)}
[22:15:28] Skipping Recycling of Items. 70 space left in bag.
[22:15:28] Moving towards pokestop Broadway Station - 0.14km
[22:15:28] {'distance_unit': '', 'distance': '', 'current_position': (53.47587977177501, -2.2954549215504563), 'last_position': (53.47593513611388, -2.295500436074667)}
[22:15:30] Skipping Recycling of Items. 70 space left in bag.
[22:15:30] Moving towards pokestop Glass Igloo - 0.14km
[22:15:30] {'distance_unit': '', 'distance': '', 'current_position': (53.47592244188027, -2.2954814461272663), 'last_position': (53.47587977177501, -2.2954549215504563)}
This has already ran repeatedly with the above issue for a few hrs, only stopped and restarted recently.
Other Information
OS: CentOS Linux release 7.2.1511 (Core)
Git Commit: f7838b8b431ff36b12f6c0bd643dbf673db34be5
Python Version: 2.7.5

Resolved;
Manually changed my location, which overwrote cached location, possible alternative fix could be clearing the bot's cache (Not confirmed).


Automatic publish to PyPI when creating new release

In this commit I created new Github Action that does the following:

Detects when new release is created
Reads release version and assigns it to package version
Publishes package to PyPI

It also needs pypi token to be set in secrets
It also requires all release versions to be in format "v{some correct new version of pypi}", e.g. v0.1.2.dev3
I also removed en-core-web-sm package, since I couldn't release to testing because of it

Could you add info, how to install en-core-web-sm @ https://github.com/explosion/spacy-models/releases/download/en_core_web_sm-3.7.1/en_core_web_sm-3.7.1-py3-none-any.whl ?

Could you add info, how to install en-core-web-sm @ https://github.com/explosion/spacy-models/releases/download/en_core_web_sm-3.7.1/en_core_web_sm-3.7.1-py3-none-any.whl ?

How to install en-core-web-sm @ https://github.com/explosion/spacy-models/releases/download/en_core_web_sm-3.7.1/en_core_web_sm-3.7.1-py3-none-any.whl:
pip install https://github.com/explosion/spacy-models/releases/download/en_core_web_sm-3.7.1/en_core_web_sm-3.7.1-py3-none-any.whl

It will also be done automatically in code


Fix service task for nested services.

The collecting now properly detects also nested services:
[
"Bar" => "App\Service\BarService"
"Foo" => "App\Service\FooService"
"Bar/Baz" => "App\Service\Bar\BazService"
"Bar/BarBaz/BarBaz" => "App\Service\Bar\BarBaz\BarBazService"
]
etc

Test coverage from 34 to 53 :)


feat: Add Consent related Ophan component types

What does this change?
The Ophan thrift model was recently updated ( https://github.com/guardian/ophan/pull/4258 ) to allow for consent related component events. This brings the same change to this repository so that we can correctly send those events from DCR client side.

Coverage remained the same at 99.527% when pulling 98494b6dc8421b4bcb2a71d6bd43f71ca92f4fd3 on ph-20210923-1818-ophan-consent-types into 3adc57042833a5cd06396a1e5b884c3adb69aa7c on main.


lots of changes to handle new routing

📝 Changed routes:

…Address]/[...catchAll]
…on-drop/[edition-drop]

(view full size)
(view full size)

…ess]/edition/[edition]
/[networkOrAddress]

(view full size)
(view full size)

…ketplace/[marketplace]
…ction/[nft-collection]

(view full size)
(view full size)

And 9 other routes:

/[networkOrAddress]/nft-drop/[nft-drop]
/[networkOrAddress]/pack/[pack]
/[networkOrAddress]/signature-drop/[signature-drop]
/[networkOrAddress]/split/[split]
/[networkOrAddress]/token-drop/[token-drop]
/[networkOrAddress]/token/[token]
/[networkOrAddress]/vote/[vote]
/dashboard
/network/[...customContract]

2 deleted routes:

/contracts/[wallet]/[contractName]
/start

Commit 7f8505e0732954ec9421b11013836928ec7ea3fd (https://thirdweb-e2ckpmogi-thirdweb.vercel.app).


Update scodec-bits to 1.1.25

Updates org.scodec:scodec-bits from 1.1.23 to 1.1.25.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scodec", artifactId = "scodec-bits" } ]

labels: library-update, semver-patch

Superseded by #254.


"there was a problem parsing the package" message

Hello Stefan.
Thank you for a good work.
I see that for many of us Elementum works on android 10+, but I still have an issue with it. Whatever I do this message is on my screen when trying to run apk. And it doesn't matter if it is universal or specific one. Too many times too many tries.
Simply I don't know what to do.
I have some android 10 tv box.
Sorry to bother you.

This was reported before and all I could think of was a corrupt download. Since then however I've encountered something that might be similar. To help test this, could you please try installing the attached modified builds of another one of my repositories and report which if any you were able to. I chose to make test builds out of that repository instead of this one because its APKs are smaller.
CallBlocker.zip

Yes, I've seen that message before and because of your answer I've tried to
download everything on multiple devices, put it on usb.
attached apks are on my usb and will try to install those later.
I'm going to try kodi and elementum now on my phones.
an update is comming.
чет, 22. дец 2022. у 09:30 StefanIlchev @.***> је
написао/ла:

This was reported before
https://github.com/StefanIlchev/ElementumService/issues/16 and all I
could think of was a corrupt download. Since then however I've encountered
something that might be similar. To help test this, could you please try
installing the attached modified builds of another one of my repositories
https://github.com/StefanIlchev/CallBlocker and report which if any you
were able to. I chose to make test builds out of that repository instead of
this one because its APKs are smaller.
CallBlocker.zip
https://github.com/StefanIlchev/ElementumService/files/10285014/CallBlocker.zip
—
Reply to this email directly, view it on GitHub
https://github.com/StefanIlchev/ElementumService/issues/23#issuecomment-1362552400,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A44LTEYLR5F3DT3OCZK423TWOQGSBANCNFSM6AAAAAATFLR5DU
.
You are receiving this because you authored the thread.Message ID:
@.***>

elementum apk installed on two phones (android 11) easily.
will try callblocker apks when i get home
чет, 22. дец 2022. у 09:43 Darko Nije @.***> је написао/ла:

Yes, I've seen that message before and because of your answer I've tried
to download everything on multiple devices, put it on usb.
attached apks are on my usb and will try to install those later.
I'm going to try kodi and elementum now on my phones.
an update is comming.
чет, 22. дец 2022. у 09:30 StefanIlchev @.***> је
написао/ла:

This was reported before
https://github.com/StefanIlchev/ElementumService/issues/16 and all I
could think of was a corrupt download. Since then however I've encountered
something that might be similar. To help test this, could you please try
installing the attached modified builds of another one of my repositories
https://github.com/StefanIlchev/CallBlocker and report which if any
you were able to. I chose to make test builds out of that repository
instead of this one because its APKs are smaller.
CallBlocker.zip
https://github.com/StefanIlchev/ElementumService/files/10285014/CallBlocker.zip
—
Reply to this email directly, view it on GitHub
https://github.com/StefanIlchev/ElementumService/issues/23#issuecomment-1362552400,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A44LTEYLR5F3DT3OCZK423TWOQGSBANCNFSM6AAAAAATFLR5DU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Nope. Not even one of CallBlocker releases doesn't work. Same message from
the system "there was a problem parsing the package"
On Thu, Dec 22, 2022, 10:28 Darko Nije @.***> wrote:

elementum apk installed on two phones (android 11) easily.
will try callblocker apks when i get home
чет, 22. дец 2022. у 09:43 Darko Nije @.***> је
написао/ла:

Yes, I've seen that message before and because of your answer I've tried
to download everything on multiple devices, put it on usb.
attached apks are on my usb and will try to install those later.
I'm going to try kodi and elementum now on my phones.
an update is comming.
чет, 22. дец 2022. у 09:30 StefanIlchev @.***> је
написао/ла:

This was reported before
https://github.com/StefanIlchev/ElementumService/issues/16 and all I
could think of was a corrupt download. Since then however I've encountered
something that might be similar. To help test this, could you please try
installing the attached modified builds of another one of my
repositories https://github.com/StefanIlchev/CallBlocker and report
which if any you were able to. I chose to make test builds out of that
repository instead of this one because its APKs are smaller.
CallBlocker.zip
https://github.com/StefanIlchev/ElementumService/files/10285014/CallBlocker.zip
—
Reply to this email directly, view it on GitHub
https://github.com/StefanIlchev/ElementumService/issues/23#issuecomment-1362552400,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A44LTEYLR5F3DT3OCZK423TWOQGSBANCNFSM6AAAAAATFLR5DU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Can you please confirm that there are apps that you can install from APK files.
Maybe logcat can tell us what exactly is the problem. Try the following:

clear logcat:

adb logcat -c

install the app:

adb install "CallBlocker-release-10-type-C.apk"

dump log:

adb logcat -d

share the output of these commands.

If you can find an open source app like Kodi itself or VLC that you can install from a file, I'll check what they're doing differently.

Kodi is installed from apk, and some other apps like media player for
example.
On Thu, Dec 22, 2022, 20:54 StefanIlchev @.***> wrote:

If you can find an open source app like Kodi itself or VLC that you can
install from a file, I'll check what they're doing differently.
—
Reply to this email directly, view it on GitHub
https://github.com/StefanIlchev/ElementumService/issues/23#issuecomment-1363286783,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A44LTEYU6D5YPVFW4LFLSE3WOSWWZANCNFSM6AAAAAATFLR5DU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Not even one. So sorry for bothering you.
On Fri, Dec 23, 2022, 10:50 StefanIlchev @.***> wrote:

Alright, so it can be done. This time I attached some modified builds from
this repository without the binaries to save on time and space. Just like
last time could you please try installing them and report which if any you
were able to.
ElementumService.zip
https://github.com/StefanIlchev/ElementumService/files/10294105/ElementumService.zip
—
Reply to this email directly, view it on GitHub
https://github.com/StefanIlchev/ElementumService/issues/23#issuecomment-1363796933,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A44LTEZX5IVEOXE2EKNW4ALWOVYV5ANCNFSM6AAAAAATFLR5DU
.
You are receiving this because you authored the thread.Message ID:
@.***>

No problem, I'm curious what your device doesn't like about the way I build my projects :-)
I have other ideas but guessing blindly is taking too long. If you or someone else would be willing to connect to such a device with Android Debug Bridge (ADB) we might get a more meaningful error message.

Yes, my device is a real disaster.
I am willing to do that thing with ADB but I ha e to find out how to do
that. I am going to do some research and hope for the best. 😁
On Fri, Dec 23, 2022, 18:29 StefanIlchev @.***> wrote:

No problem, I'm curious what your device doesn't like about the way I
build my projects :-)
I have other ideas but guessing blindly is taking too long. If you or
someone else would be willing to connect to such a device with Android
Debug Bridge (ADB) we might get a more meaningful error message.
—
Reply to this email directly, view it on GitHub
https://github.com/StefanIlchev/ElementumService/issues/23#issuecomment-1364135816,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A44LTE34M5H2OOHK6FCGTG3WOXONZANCNFSM6AAAAAATFLR5DU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Maybe it wants the APK to be signed as a JAR file, like an Android 6 or older device.
ElementumService2.zip

Same problem here, tried all the zips including ElementumService2.zip got the same error message.


Add submit body

Submit body for Save button added

Thank you for your submission. However, I am rejecting the pull request.
These are supposed to be the "starter" files for the "Angular Front to Back with Web API" course. Developers that are taking the course can then fill in the content as part of their learning process. I purposefully did not mean to provide the detailed code.
Please let me know if you have any questions about this.


Tests\Feature::withHeader('host', 'domain.com') Invalid

Laravel Version: 8.14.0
PHP Version: 7.3.11
Database Driver & Version: mariadb & 10.3.26

Description:
多域名配置下，使用 withHeader 设置 host 字段无效。
In the multi-domain configuration, using the withHeader to set the host field is invalid.
原因(the reason)：
vendor/laravel/framework/src/Illuminate/Foundation/Testing/Concerns/MakesHttpRequests.php:call (line: 503)
$this->prepareUrlForRequest($uri)
如果 $url 不是完整路径，会自动获取域名补全。
If $url is not a full path, the domain name completion will be automatically obtained.
则导致其在后续 SymfonyRequest::create (line: 350)被用于覆盖 host
It causes it to be used to overwrite host in the subsequent SymfonyRequest::create (line: 350)
Steps To Reproduce:
file: routes/api.php
Route::domain('api.example.test')->get('/ping', function() {
    return 'pong';
});

file: tests/Feature/ApiTest.php
fuction:
    public function testPing()
    {
        $this->withHeader('host', 'api.example.test');
        $response = $this->get('/ping', ['host' => 'api.example.test']);

        $response->assertStatus(200);
    }

Hey there,
Can you first please try one of the support channels below? If you can actually identify this as a bug, feel free to report back and I'll gladly help you out and re-open this issue.

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

Thanks!

very sorry, After careful consideration, I still think this should be a BUG.
Unless the official believes that this should be a Feature, that is, the Host field must be passed through $uri and should not be set through Header.
For a detailed description of this issue, you can read this post I posted.
Although answer #1 (overriding fields such as get to add Host to $uri) is desirable, it should be unnecessary.
symfony - Feature Test in Laravel 8 uses withHeader to set Host invalid? - Stack Overflow

This should work.
    public function testPing()
    {
        $response = $this->get('http://api.example.test/ping', ['host' => 'api.example.test']);

        $response->assertStatus(200);
    }

@imdong I'm sorry but I don't think so. @crynobone's answer from above is the correct wtg.


TOUCHSCREEN DON'T WORK CUH!

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Use a literal phone
Touchscreen mode
mfw touchscreen buttons don't work

Expected behavior
A clear and concise description of what you expected to happen.
Touchscreen buttons should work
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: postmarketOS
Minecraft 1.19.3
Fabric 0.14.15
Mods Midnightcontrols, fabric api, starlight, sodium, no chat reports, no telemetry, iris shaders, mod menu, multiconnect, chat heads
Version 1.7.3
Branch (I think it's main because there's no dev mention)

Additional context
Add any other context about the problem here.
Unofficially running it on a Oneplus 6. Minecraft indeed detects my fingers.

I am having the same issue on mobian with my pinephone pro, except I can't even navigate menus.

just read #20 , this issue should probably be closed


Autodetect unstripped ReMIX files

I think this would be a useful thing to have, specifically for the game engine so far. It would also be a good start to finally interweave our tools together. Upon launching the game engine if it detects ReMIX files but notices they are not stripped, prompt the user to strip them before finally starting the game.

easy done #126

Fixed with #126


⚠ Bofrost.fr has degraded performance

In 3b3980e, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1170 ms

Resolved: Bofrost.fr performance has improved in e30c5d2 after 6 minutes.


[Bug] Inconsistent font-color in story list

Describe the bug
In the brand guidelines, it is mentioned that #008acf should be the color for links in the application. However in the story list of homepage, the Category field is a text field and uses this color. This creates inconsistency with the guidelines
To Reproduce
Steps to reproduce the behavior:

Go to userstory.eosdesignsystem.com
Scroll down to the stories
For every story, the Categroy field is marked with wrong font-color

Expected behavior
Since it is plain text, it should have #1E3B51 font-color
Logs

Environment (please complete the following information):

OS: Windows 10
Browser: Chrome

I want to work on this


Getting 400 Bad Request

can you please clarify for me?

any updates here guys?
Please help!
@kevmoo @michalt @cdibona @dberlin

There's no reproduction steps. No details. No idea how we can help...

@kevmoo Well, I believe there's no details and/or steps to reproduce the issue because of absence of a template to be filled out whenever someone tries to file a new issue!
I think It was supposed/expected for the issue creator to be guided to create an issue for this repository via a template placeholder that was supposed to exist and being put by the maintainers inside the box of a new issue body.
Since there's lack of guidance (Yet in my POV), even inside the Contributing Guidelines and the Code of Conduct that are being mentioned below this page "as well as in the About Section at the repository's home page", and since there's nothing that relates to creating or reporting an issue even at an external place while being referenced here by this repo, Therefore, I think I have to guess and assume on my own in order to make it more clear for you.
And hopefully this will make sense for you eventually, Otherwise, Kindly let me know how can I meet the expectations.
Hence I am going to use the following template:
Steps to reproduce

Create a client code that uses this lib. e.g

import 'sync_http.dart';

void main() {
  var uri = Uri.parse('https://dog.ceo/api/breeds/image/random');
  var request = SyncHttpClient.getUrl(uri);
  var response = request.close();
  print('Response Status Code: ${response.statusCode}');
  print('Response Body: ${response.body}');
}

Run the code.

Current behaviour (bug)
Response Status Code: 400
Response Body:
<title>400 The plain HTTP request was sent to HTTPS port</title>

400 Bad Request

The plain HTTP request was sent to HTTPS port

cloudflare

Expected behaviour (correct)
Response Status Code: 200
Response Body: {"message":"https:\/\/images.dog.ceo\/breeds\/whippet\/n02091134_7375.jpg","status":"success"}

Relevant logs and/or media

Other comment

Dart SDK Version (dart --version): Dart SDK version: 2.16.1 (stable) (Tue Feb 8 12:02:33 2022 +0100) on "linux_x64".
Operating System is Linux UBUNTU.
lib sync_http version: 0.3.1-dev "From pubspec.yaml".
Related issue: Here

Reported by
@ahmadSaeedGoda && @alaashahin1
/label ~Bug
Hope you find this useful.
In addition, if I can provide any further information let me know, would be more than happy to assist!

I am facing the same issue. Did you find a solution for this?

@kevmoo Well, I believe there's no details and/or steps to reproduce the issue because of absence of a template to be filled out whenever someone tries to file a new issue!
I think It was supposed/expected for the issue creator to be guided to create an issue for this repository via a template placeholder that was supposed to exist and being put by the maintainers inside the box of a new issue body.
Since there's lack of guidance (Yet in my POV), even inside the Contributing Guidelines and the Code of Conduct that are being mentioned below this page "as well as in the About Section at the repository's home page", and since there's nothing that relates to creating or reporting an issue even at an external place while being referenced here by this repo, Therefore, I think I have to guess and assume on my own in order to make it more clear for you. And hopefully this will make sense for you eventually, Otherwise, Kindly let me know how can I meet the expectations.
Hence I am going to use the following template:
Steps to reproduce

Create a client code that uses this lib. e.g

import 'sync_http.dart';

void main() {
  var uri = Uri.parse('https://dog.ceo/api/breeds/image/random');
  var request = SyncHttpClient.getUrl(uri);
  var response = request.close();
  print('Response Status Code: ${response.statusCode}');
  print('Response Body: ${response.body}');
}

Run the code.

Current behaviour (bug)
Response Status Code: 400
Response Body:
<title>400 The plain HTTP request was sent to HTTPS port</title>

400 Bad Request

The plain HTTP request was sent to HTTPS port

cloudflare

Expected behaviour (correct)
Response Status Code: 200
Response Body: {"message":"https:\/\/images.dog.ceo\/breeds\/whippet\/n02091134_7375.jpg","status":"success"}

Relevant logs and/or media

Other comment

Dart SDK Version (dart --version): Dart SDK version: 2.16.1 (stable) (Tue Feb 8 12:02:33 2022 +0100) on "linux_x64".
Operating System is Linux UBUNTU.
lib sync_http version: 0.3.1-dev "From pubspec.yaml".
Related issue: Here

Reported by
@ahmadSaeedGoda && @alaashahin1
/label ~Bug
Hope you find this useful. In addition, if I can provide any further information let me know, would be more than happy to assist!

I am facing same issue. Did you find a solution to make sync call ?

I am facing same issue. @kevmoo @ahmadSaeedGoda @alaashahin1 @saurabhgoyal12 @michalt

Apparently all HTTPS requests would fail. Client sents request as plain http even if specified https:// in url. It is not a matter of localhost or remote.
To whoever looking for a synchonous http call solution, I end up using dart:io with async/await. Below is an example I figured out that works.
import 'dart:io';
import 'dart:convert';
...
var request = await HttpClient().postUrl(url);
request.headers.set('Content-Type', 'application/json');
request.write(body);
var response = await request.close();
if (response.statusCode == 200) {
final responseBody = await response.transform(utf8.decoder).join();
// actions here
}

Digging into the code a bit, I find that the request is sent using RawSynchronousSocket which is not going to work with any HTTPS (SSL/TLS) connection.  Unfortunately, I find evidence here that the Flutter/Dart team may not plan to fix it:
https://github.com/dart-lang/sdk/issues/39703#issuecomment-563226251
Now, that comment is very old but they did close the issue with the guidance to "just use async."  Which is not particularly helpful in the context sync_http -- so I hope this is just a resource issue, since I doubt anybody has ever used sync_http for anything in production.
Flutter team, any guidance for sync TLS in 2024?
(Yes, I would prefer to use async everywhere, but that's not currently possible with Flutter forms and the various hackarounds are not working for me.  YMMV.)


[Azure.Core] Add Public Model Serialization

Add Public Model Serialization classes to all Models
To be completed by May Milestone
Checklist:

[ ] Add SerializableOptions as a parameter to IUtf8JsonSerializable
[ ] https://github.com/Azure/azure-sdk-for-net/blob/652dc91766f8336af2d9e36604d29a9f782fe4e4/sdk/metricsadvisor/Azure.AI.MetricsAdvisor/src/Utf8JsonWriterExtensions.cs#L18 needs case for ISerializable

Fixes:

https://github.com/Azure/azure-sdk-for-net/issues/37094
https://github.com/Azure/azure-sdk-for-net/issues/35783
https://github.com/Azure/azure-sdk-for-net/issues/28358
https://github.com/Azure/azure-sdk-for-net/issues/35201#issuecomment-1503756381
https://github.com/Azure/azure-sdk-for-net/issues/35963
https://github.com/Azure/autorest.csharp/issues/3353
https://github.com/Azure/azure-sdk-for-net/issues/37475

https://github.com/Azure/azure-sdk-for-net/issues/35783

https://github.com/Azure/azure-sdk-for-net/issues/28358

https://github.com/Azure/azure-sdk-for-net/issues/35201#issuecomment-1503756381

https://github.com/Azure/azure-sdk-for-net/issues/35963

https://github.com/Azure/autorest.csharp/issues/3353

Diplicate: #38763

Thanks for pointing to this tracking work item from the duplicated issues. It seems like the mile stone has been changed several times. Is this work item commited? Could you please also share an very rough ETA for this work item?

The only statement that I can make is that this is something that we are working on.  There is no committed timeline that I can share.

Duplicate: #39107.

Could you include clone methods? In our use cases, we need to adjust request options just before dispatching them. Modifying properties of the original instance is not convenient operation :)

@m-nash, I believe the work on the Core side of this is complete with the release of System.ClientModel v1.0.0.  If work remains to implement model serialization in various client libraries, should this be moved to track those separately?


Silent option

I got gulp-connect-php to work in conjunction with browserSync, which works perfectly so far.
I've been using grunt-php before which this plugin seems to be based on and I remember it having a silent flag to suppress the output to the console. I would very much like to have that feature as well since I use the console output for things like JSHint and don't really need a bunch of [200] access codes cluttering my console. I couldn't find a similar option for gulp-connect-php :(
Is there any way this can be implemented or achieved in my gulp setup?
Any help is much appreciated!

I submitted a pull request for this here: https://github.com/micahblu/gulp-connect-php/pull/11

I merged  https://github.com/micahblu/gulp-connect-php/pull/11 which gives a silent option


Added Events log to Azurite

Thanks for contribution! Please go through following checklist before sending PR.
PR Branch Destination

For Azurite V3, please send PR to main branch.
For legacy Azurite V2, please send PR to legacy-dev branch.

Always Add Test Cases
Make sure test cases are added to cover the code change.
Add Change Log
Add change log for the code change in Upcoming Release section in ChangeLog.md.
Development Guideline
Please go to CONTRIBUTION.md for steps about setting up development environment and recommended Visual Studio Code extensions.

@prajjawal05
Azurite is an Azure Storage API compatible emulator.
But Event Grid  is not a part of Storage API, so this PR is out of Azurite scope.
We can't merge this PR in this case.
If you really want this code change, you might can keep it in your own Azurite fork, and following https://github.com/Azure/Azurite#github to build and run Azurite with your code change.

Oh missed this, I'll keep this in mind. Closing the PR for now.


Update myo_sim submodule from dev to main before release.

          Note. This needs to be updated before the merge.

Originally posted by @vikashplus in https://github.com/MyoHub/myosuite/pull/184#discussion_r1676374067

Changed to point to main

@vikashplus This can be closed, since it is completed.


Not waiting for all data from socket before parsing message

Steps:

??? I'm not sure what I did to get into this state (maybe have a bunch of gcm notifications queued?), but I'm consistently in it
Get multiple socket data events per gcm notification

Expected:
Able to parse notifications
Actual:
index out of range errors from protobuf
I think this is also the cause of #9
When you get into this state, if you add a console.log in socket.on('data' like so:
console.log('got data', buffer.length)
Than for the first push notification you'll see the following:
got data 1
got data 88
got data 105
got data 514
got data 695

For subsequent push notifications you'll see the following:
got data 1026
got data 189

Note that the first push notification always starts with a buffer of length 1.
When you're in this state NotificationSchema.decode(buffer) always fails with messages like:
Error: invalid wire type 7 at offset 9
    at BufferReader.Reader.skipType (/Users/islam/Projects/superhuman/desktop-electron/node_modules/protobufjs/src/reader.js:375:19)
    at BufferReader.Reader.skipType (/Users/islam/Projects/superhuman/desktop-electron/node_modules/protobufjs/src/reader.js:366:22)
    at Type.DataMessageStanza$decode [as decode] (eval at Codegen (/Users/islam/Projects/superhuman/desktop-electron/node_modules/@protobufjs/codegen/index.js:50:33), <anonymous>:67:5)
    at Type.decode_setup [as decode] (/Users/islam/Projects/superhuman/desktop-electron/node_modules/protobufjs/src/type.js:502:25)
    at onMessageReceived (/Users/islam/Projects/superhuman/desktop-electron/node_modules/push-receiver/src/client/socket/index.js:125:34)
    at Timeout.setTimeout [as _onTimeout] (/Users/islam/Projects/superhuman/desktop-electron/node_modules/push-receiver/src/client/socket/index.js:105:9)
    at ontimeout (timers.js:475:11)
    at tryOnTimeout (timers.js:310:5)
    at Timer.listOnTimeout (timers.js:270:5)

This is because socket.on('data' is not waiting for all the data to arrive before parsing it. I was able to demonstrate this by making a hack fix:
function listen(socket, NotificationSchema, keys, persistentIds) {
  let buf = null
  let timeout = null

  socket.on('data', (buffer) => {
    if (buf) {
      buf = Buffer.concat([buf, buffer])
    } else {
      buf = buffer
    }

    if (!timeout) {
      timeout = setTimeout(() => {
        onMessageReceived(buf, NotificationSchema, keys, persistentIds)
        buf = null
        timeout = null
      }, 1000)
    }
  });
}

This works but isn't the right fix since it's race-condition prone.

@MatthieuLemoine / @yurynix FYI I started on this and I should have something usable in the next day or two. I'm copying the implementation from chromium (with a few slight simplifications) so hopefully it's mostly correct.
Also - @MatthieuLemoine would you be opposed to restructuring this library to use more classes? Ideally each connection can be isolated.

@ibash sure if it makes sense

Pull request is here: https://github.com/MatthieuLemoine/push-receiver/pull/13 let me know if you have questions / thoughts!

Fixed in v2.0.0


Opacity

I think that changing the opacity is not available right now. So i think it would be really cool if it did.

Do you mean an option for transparent background? I think the specific opacity is controlled by the terminal, not neovim. I could try to implement this a bit later, maybe within this week.

Yes, exactly that. I'm using st and also double checked my Xresourcess, even tough i have them both set to 0.92 opacity background, it does not affect nvim with this specific colorscheme.


Fix an issue with effect reference counting

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Reviewer - this PR has made changes to the build configuration file.
This build will release a new package on npm
If that was unintentional please make sure to revert those changes or close this PR.

Snapshot stored with reference name:
refs/pull/15964/merge
Test environment:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15964/merge/index.html
To test a playground add it to the URL, for example:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15964/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/15964/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/15964/merge
https://gui.babylonjs.com/?snapshot=refs/pull/15964/merge
https://nme.babylonjs.com/?snapshot=refs/pull/15964/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/15964/merge#BCU1XR#0

Visualization tests for WebGPU (Experimental)
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15964/merge/testResults/webgpuplaywright/index.html

WebGL2 visualization test reporter:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15964/merge/testResults/webgl2playwright/index.html

Reviewer - this PR has made changes to the build configuration file.
This build will release a new package on npm
If that was unintentional please make sure to revert those changes or close this PR.


ngxtension:convert-outputs does not work for EventEmitters with types

Problem:
convert-outputs migration does not support EventEmitters that are typed with objects(?).
If a component has an output defined such as
´´´
@Output()
createOrUpdateDtoOutput = new EventEmitter<{
id: string;
dto: CreateOrUpdateDto;
}>();
´´´
it will end up as
´´´
createOrUpdateDtoOutput = output();
´´´
and later in the code when stuff calls .next() it is not changed to .emit(), and Angular will also complain in all parent components about that output Argument of type 'void' is not assignable to paramter of type '{dto: {....}}; id: string;}'

Hello @BeGj
I'd recommend to try using the official Angular migrations
https://angular.dev/reference/migrations/outputs
The version we have on ngxntesion will be deprecated soon, as the official one is better and supports more usecases and patterns.

Closing as not planned.


Appending node type to local tensor names for calibration

New command line argument for caffe_to_nnir, onnx_to_nnir, nnef_to_nnir , nnir_update to take 'node_type_append'.
Appends type of the node to local tensor names, when needed for calibration

@LakshmiKumar23 is this ready to be merged?

@kiritigowda yes

@LakshmiKumar23 is this ok to merge now?

@kiritigowda I think this needs to be merged with the master. Let me do that and see if it gives any merge conflicts.

@kiritigowda Ready to be merged now


How to resize a vertical split window?

Hi,
Is there a shortcut to resize windows after doing a vsplit ?
Thanks

You can resize using the ^W-, ^W+, ^W<, ^W>, and ^W= keybindings from Vim. There's not currently a :resize command like Vim has, but I filed an issue at ulyssa/modalkit#114.

I've filed an issue to update the webside documentation at ulyssa/iamb.chat#11.

Thanks

@ulyssa I have tried to use the keybinding but it did not work.
I probably think that my terminal is intercepting these bindings before iamb.
It would be great to have the :resize command


SabreLayout does not terminate in some cases

Environment
Qiskit version: master
Python version: 3.8.8
OS: Mac OS 12.2
What is happening?
SabreSwap gets stuck in some specific cases and does not make forward progress.
How can we reproduce the issue?
here's an example that runs indefinitely for me. Note that even though I run SabreLayout, internally it is calling SabreSwap and that's where it gets stuck.
from qiskit.circuit.library import QuantumVolume
from qiskit.transpiler import PassManager, CouplingMap
from qiskit.transpiler.passes import SabreLayout

n = 30
coupling_map = CouplingMap.from_line(n)
basis_gates=['cx', 'u']
qv = QuantumVolume(n, seed=983).decompose()
pm = PassManager(SabreLayout(coupling_map, seed=1))
pm.run(qv)

What should happen?
map the circuit and terminate
Any suggestions?
I think the SabreSwap algorithm has a way to score different swap options and to make forward progress, so not sure what's going on.

@ajavadia I can take a look at this.

@ajavadia Just an initial report. I turned debug logging on for the SabreSwap runs and have determined that there are 6 calls to SabreSwap.run. The first 4 and the sixth runs work, but the 5th one gets in a state where it can't make progress. The extended_set is the same 4 qubits and the best_swap is the same 2 qubits.
Next step is to work back to see where this begins and to see why qubits_decay doesn't get the run out of the loop. Will report any progress.

@ajavadia Here's a rundown of what I've found so far.

There are 6 calls to SabreSwap from SabreLayout. Given the seeds in your test case, 5 of the calls terminate after about 2500 internal loops. The other one does not terminate.
For the run that doesn't terminate, on loop 2451, a new front_layer appears and a new extended_set. From that point on, the extended_set does not change.
On loop 2483, a final new front_layer appears.
Beyond that point, the best_swap changes regularly, but there is no longer any progress made on that front_layer.
If I adjust any of the 4 global parameters at the top of sabre_swap.py, either up or down, by arbitrary amounts, all the calls terminate.

I have uploaded a log file
sabre_bad_run1.txt
that goes from loop 2300 to loop 2600 for that non-terminating loop if anyone else wants to look at that. Search for
'count: 2451' to locate the start of the issue.
I'm not sure why the process gets stuck, but if you can point me in a direction, I'm willing to pursue this further.

Thanks for looking into it @enavarro51.  The extended_set here is the set of node pairs in the DAG that we must make neighbors through insertion of swaps. Since best_swap gets picked at every step but extended_set does not change, it looks like it is just swapping qubits around without ever actually making progress on resolving the extended_set (i.e. it goes in circles, sometimes those nodes get closer and sometimes get further). Maybe we can draw this on paper to see which swaps get inserted and why they never converge.

This might not be the only case of an infinite loop in the algorithm, but I'm confident that I understand how it happens here, and I've produced a minimal circuit for which SabreSwap immediately enters an infinite loop from which it can provably never escape no matter how the pass is seeded:
 q_0: ─■────────────────
       │
 q_1: ─┼──■─────────────
       │  │
 q_2: ─┼──┼──■──────────
       │  │  │
 q_3: ─┼──┼──┼──■───────
       │  │  │  │
 q_4: ─┼──┼──┼──┼─────■─
       │  │  │  │     │
 q_5: ─┼──┼──┼──┼──■──■─
       │  │  │  │  │
 q_6: ─┼──┼──┼──┼──┼────
       │  │  │  │  │
 q_7: ─┼──┼──┼──┼──■──■─
       │  │  │  │     │
 q_8: ─┼──┼──┼──┼─────■─
       │  │  │  │
 q_9: ─┼──┼──┼──■───────
       │  │  │
q_10: ─┼──┼──■──────────
       │  │
q_11: ─┼──■─────────────
       │
q_12: ─■────────────────

The relevant coupling map is a line in the same order the qubits are displayed in the drawing.  The first five gates are the front layer, and the second two are the extended set.  The algorithm will get stuck making random swaps from the set [(0, 1), (1, 2), (2, 3), (9, 10), (10, 11), (11, 12)] (i.e. the outermost qubits), even though the only way it could possibly progress (and would do immediately) would be to swap (5, 6) or (6, 7).
It gets stuck because it's in a stable local minimum of the (non-basic) heuristics.  The only way it can advance is by making a swap that temporarily increases the score from the "lookahead" components.  I've written a routine that produces a circuit with arbitrarily many layouts in the stable local minimum region (increase additional_local_minimum_gates), and requires arbitrarily many swaps to be made "uphill" against the heuristic (increase uphill_swaps) before progress can be made:
from qiskit.circuit import QuantumCircuit

def looping_circuit(uphill_swaps=1, additional_local_minimum_gates=0):
    """Create a circuit that is arbitrarily hard for the advanced SABRE
    heuristics to route.

    The circuit is in a stable local minimum of the "lookahead" and "decay"
    SABRE heuristics, where you need to increase the values of those heuristics
    before you can make progress.  This minimum is stable no matter what
    weighting is attached to the cost of the gates in the extended set (except
    if they're weighted as zero).  If the decay reset interval is set
    sufficiently high, it _can_ become possible to escape the minimum, but you
    need to get arbitrarily lucky as the two inputs to this function are
    increased.

    Draw the circuit output from this function to see the hill structure.

    Args:
        uphill_swaps (int): how many swaps SABRE will need to make that increase
            the total score of the layout before it can make further progress
        additional_local_minimum_gates (int): how many additional gates to add
            in the front layer that produces the local minumum that the routing
            pass gets stuck in.  This increases the number of layouts that all
            have the same score that the pass will get stuck switching between.
    """
    outers = 4 + additional_local_minimum_gates
    n_qubits = 2*outers + 4 + uphill_swaps
    # This is (most of) the front layer, which is a bunch of outer qubits in the
    # coupling map.
    outer_pairs = [(i, n_qubits - i - 1) for i in range(outers)]
    inner_heuristic_peak = [
        # This gate is completely "inside" all the others in the front layer in
        # terms of the coupling map, so it's the only one that we can in theory
        # make progress towards without making the others worse.
        (outers + 1, outers + 2 + uphill_swaps),
        # These are the only two gates in the extended set, and they both get
        # further apart if you make a swap to bring the above gate closer
        # together, which is the trick that creates the "heuristic hill".
        (outers, outers + 1),
        (outers + 2 + uphill_swaps, outers + 3 + uphill_swaps),
    ]
    qc = QuantumCircuit(n_qubits)
    for pair in outer_pairs + inner_heuristic_peak:
        qc.cz(*pair)
    return qc

If you want to run the infinite loop, the extra bit to demonstrate it is:
from qiskit.converters import circuit_to_dag
from qiskit.transpiler import CouplingMap
from qiskit.transpiler.passes import SabreSwap

def infinite_loop(circuit, method="lookahead"):
    if method == "basic":
        raise Exception("the 'basic' heuristic can't get stuck")
    coupling_map = CouplingMap.from_line(circuit.num_qubits)
    # If called on the output of `looping_circuit`, this will never return.
    return SabreSwap(coupling_map, method).run(circuit_to_dag(circuit))

I have several modifications to the heuristics that would always allow it to progress eventually, but with the extra parameters in looping_circuit above, I can make all of them either take factorial (I think) amounts of memory to detect or require exponential time to make progress.

Oh, I'm actually slightly wrong in the docstring of looping_circuit above - it's not a priori stable against the weighted of the extended set heuristic additions, but with a suitably large additional_local_minimum_gates you can make it stable against a weighting that becomes arbitrarily close to zero.
The requirement to have four outer gates right now is because of our particular choice of EXTENDED_SET_WEIGHT = 0.5.  If we instead set that to 1, we'd only need three outer gates to make it work, and in general you need to satisfy 1 / (n_outer_gates + 1) >= EXTENDED_SET_WEIGHT / 2 to be able to escape the loop.

I know there is a fix already, but I am curious if this is fixed by perturbing the coupling map weights like Stochastic swap does?  The circuit above has degenerecies due to the symmetry that might be making it hard to decide where to go next.

If you re-perturb the coupling map at every iteration of the swap algorithm, I think you could overcome the infinite loop like this (if the perturbations are sufficiently large), but if it's done only once at the beginning of the run, I think you'd probably still get stuck in the same manner.
The reason it gets stuck is that the "lookahead" heuristics that SabreSwap uses to improve its output can (in super rare circumstances) end up causing an isolated local minimum in the heuristic where all the layouts at the same value make no progress, and the ones which do make progress need you to increase the heuristic.  My first thought was to introduce a stochasticity to the heuristic itself, widening the perturbation the longer we go without making progress until we're just picking swaps randomly, which would also work, but be super inefficient.
With the looping_circuit I have above, you can make it arbitrarily hard for the Sabre algorithm - there's only one path to progress, which you can make arbitrarily long (uphill_swaps), and you can increase the "potential barrier" in the heuristic that you need to overcome to escape the local minimum up to a limit.


fix the calling of deleted ncp function

fs.ncp is not exporting anymore. Use copyFile instead.

Thank you! This is a good catch!


sim/macos:fix system bzero recursive call

Summary
sim/macos:fix system bzero recursive call
Impact
noting
Testing
sim:nsh
There may be other functions where recursion occurs

0000000100024574 <_bzero>: /bzero       [3/19]
100024574: d10083ff     sub sp, sp, #32
100024578: a9017bfd     stp x29, x30, [sp, #16]
10002457c: f90007e0     str x0, [sp, #8]
100024580: f90003e1     str x1, [sp]
100024584: f94007e0     ldr x0, [sp, #8]
100024588: f94003e1     ldr x1, [sp]
10002458c: 97fffffa     bl  0x100024574 <_bzero>
100024590: a9417bfd     ldp x29, x30, [sp, #16]
100024594: 910083ff     add sp, sp, #32
100024598: d65f03c0     ret

This is the assembly before modification. I suspect that the bug may be caused by macos clang upgrade. @masayuki2009

@anjiahao1
Could you move the commit to https://github.com/apache/nuttx/pull/11207?
Using the same PR is easy to test.

@anjiahao1 Could you move the commit to #11207? Using the same PR is easy to test.

ok i move it ，and close this pr


Bind is unable to access data when called on component element with replace: false.

I'm unable to bind directly on a Component element with replace: false set.
E.g: <comp v-bind:class="{'expanded': expand}" />
The class is never applied even though expand is true.
However, <comp v-bind:class="{'expanded': true}" /> does apply the class.
See: https://jsfiddle.net/8rczqdee/4/

Hey there! The issue doesn't seem to be reproducible in the Fiddle you provided, since removing the replace: false does not add the class.
Anyhow, this doesn't seem to be the issue - instead you should take a look at the Compilation Scope section in the VueJs Guide. You are trying to bind to a child property from within the parent's scope. Instead you might want to try something like this:
https://jsfiddle.net/p9aj0s55/
I hope this helps! If you feel this doesn't solve your issue, please feel free to reopen it :)

Or you can move expand  to it's parent scope,  try it like this:
https://jsfiddle.net/avalon_api/d4532zat/1/


fix(compaction): fix compaction task do not schedule even if the number of L0 files is very large

Signed-off-by: Little-Wallace<EMAIL_ADDRESS>What's changed and what's your intention?
close https://github.com/singularity-data/risingwave/issues/3066
Checklist

[x] I have written necessary docs and comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Refer to a related PR or issue link (optional)

merge?


repo:createdDate vs repo:createDate

Asked via email to Grp-XDM-API-WGs 10 May 2018:
There appears to be a discrepancy between the following:

https://github.com/adobe/xdm/blob/master/schemas/external/repo/common.schema.json has “repo:createDate” (‘create’, not ‘created’).
https://github.com/adobe/xdm/blob/master/schemas/external/repo/asset.schema.json has “repo:createdDate” (‘created’, not ‘create’), as do 5 other schema files and 14 example files in the schemas directory.

May I assume that common.schema.json is in error and that “repo:createdDate” is the correct property name?
NOTE: Leonard Rosenthol commented via email (before this issue was created) that he thinks that "repo:createDate" would be the correct one "since it is based on XMP". I was not aware that the repository metadata concepts were specifically based on XMP.
Whichever direction this goes, I recommend that the tense of both the "create" and "modify" metadata be aligned. (In other words, I recommend that we either choose "repo:createDate" and "repo:lastModifyDate" or choose "repo:createdDate" and "repo:lastModifiedDate". (Choosing the later would clearly require the least change to existing schemas.)
Current situation, looking only in the 'schemas' directory:

repo:createDate: Found only in external/repo/common.schema.json
repo:createdDate: Found in assets/asset.schema.json, assets/image.schema.json, assets/video.schema.json, content/componentized-page.schema.json, external/repo/asset.schema.json, and external/repo/directory.schema.json, and 14 example files.
repo:lastModifyDate: Not found
repo:lastModifiedDate: Found in assets/asset.schema.json, assets/image.schema.json, assets/video.schema.json, content/componentized-page.schema.json, external/repo/asset.schema.json, external/repo/common.schema.json, and external/repo/directory.schema.json, and 14 example files.

For comparison:

xmp:createDate: Found in assets/asset.schema.json and 5 example files.
xmp:modifyDate: Found in assets/asset.schema.json and 5 example files.

The original “Core Asset Data Model”, on which the core asset and other schemas were defined, started from XMP.  As such, those definitions take precidence.

Thanks, Leonard. The issue remains... the XDM spec currently has repo:createDate defined in one place and repo:createdDate defined other places.
By what process does this get resolved?
Options to achieve consistency appear to be:

repo:createDate, repo:modifyDate (most directly related to XMP naming)
repo:createDate, repo:lastModifyDate (close to existing, but lastModify sounds a bit odd)
repo:createdDate, repo:lastModifiedDate (least change to current spec, by far)

On a related note: I see that xdm:repositoryCreatedBy and xdm:repositoryLastModifiedBy are defined in four different schema.json files. Do those come from XMP? I am a bit surprised that such metadata is not defined closer to "common" in the schema inheritance hierarchy. In any case, is there no need for a corresponding "repo" version of such metadata? (repo:createdBy and repo:lastModifiedBy, anyone?)

@kstreeter  @trieloff @lrosenthol - I think it would make sense to roll this into the next milestone build which is just 2 business days away. I am happy to push the buttons on a PR to make this happen but I need you to decide on what is the right option going forward.

@jimaldous I'm referring to the internal Confluence wiki. Simply search for "repo:id" (with quotes) and you'll see what I'm referring to. There seem to be assumptions that "repo:id" already exists or will exist soon.
"Yes" to moving it into its own issue. I created a new issue #348

@trieloff - Who would be the approvers for this change in the ACP API WG? Lets add them to this and get it resolved one way or the other.

That would be @ogoldman

@ogoldman - can you please provide your assessment of how to resolve this issue?

Oliver and I have a proposal we are working through for how to resolve this - its' related to our discussion about setting up a separate git repo...

The repo property should be repo:CreateDate and repo:ModifyDate, in order to remain consistent with the existing XMP properties with related names and semantics.

I just looked over the state of assets in XDM to see if the attribute capitalization issue has been addressed yet and I noted that there remains a mix of repo:createDate and repo:createdDate. A quick search in the source code of the spec shows the following counts:

repo:createDate in .md files: 59
repo:createDate in .json files: 2
repo:createdDate in .md files: 15
repo:createdDate in .json files: 40
repo:lastModifyDate in any file: 0
repo:lastModifiedDate in any file: 116
Given that the ACP API spec uses repo:createdDate, I recommend changing all repo:createDate to repo:createdDate.

So in the internal API specification we have repo:createdDate and repo:lastModifiedDate. So I tend to agree. I think the asset metadata might come up with more along the lines as indicated by @ogoldman due to XMP mapping.
I am not sure where this goes or should go from here. Maybe a PR @jimaldous ?
/cc @lrosenthol, @kstreeter


Allow profiling on controller

Is your feature request related to a problem? Please describe.
We have a problem with the cert-manager-controller taking a huge amount of memory (1.5gb for a large cluster). And removing the various controllers, as well as removing its permissions to list pods/services didn't help.
Describe the solution you'd like
The cert-manager-webhook already has profiling as an option. It would really help to have pprof available in the cert-manager-controller as well. This can enable finding the source of the memory consumption.
Environment details (remove if not applicable):

Kubernetes version: 1.18.2
Cloud-provider/provisioner: AWS & kops
cert-manager version: 1.0.4
Install method: helm

/kind feature

I like to work on this


Docker build failed with v0.6.1

I am using ubuntu 22.04 and run  make -C docker release_build
It is failing in the pip install mpi4py step.
54.13       checking for library 'lmpe' ...
54.13       /usr/local/mpi/bin/mpicc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -c _configtest.c -o _configtest.o
54.13       /usr/local/mpi/bin/mpicc _configtest.o -llmpe -o _configtest
54.13       /usr/bin/ld: cannot find -llmpe: No such file or directory
54.13       collect2: error: ld returned 1 exit status
54.13       failure.

I manged to skip this error by replacing the pip install mpi4py in tensorrt_llm/docker/common/install_base.sh  with:
python -m pip install https://github.com/Shixiaowei02/mpi4py/tarball/fix-setuptools-version

I managed to skip this error by replacing the pip install mpi4py in tensorrt_llm/docker/common/install_base.sh with: python -m pip install https://github.com/Shixiaowei02/mpi4py/tarball/fix-setuptools-version.

Hi @Slyne , do you mind sharing what is the fix in your tarball file? if it is a issue in the v0.6.0, it would be ideal to fix it in the master.

I managed to skip this error by replacing the pip install mpi4py in tensorrt_llm/docker/common/install_base.sh with: python -m pip install https://github.com/Shixiaowei02/mpi4py/tarball/fix-setuptools-version.

Hi @Slyne , do you mind sharing what is the fix in your tarball file? if it is a issue in the v0.6.0, it would be ideal to fix it in the master.

It's not from my repo. It belongs to one of the TRTLLM developer @Shixiaowei02 . I think this issue is related to mpi4py and I remember they've already sent the pr.

Thanks everyone for your helpful answers!


Remove some unused CIPD packages before android compile.

This should save about 2.5GB of space.
Ideally we should not download these in the first place, however I would have to figure out how to set that up.
For now tested locally that compile seems to pass because we use the NDK, however CI will fully validate this.

Merging since android smoke tests passed (and no other workflows are affected)


New issue workflow

New Issue workflow
Create a workflow that activates when a new Issue is created.
Requirements

Adds issue to the 'vue-masterclass-library' project

Sets status to 'new'
Sets priority to 'medium'

Applies the correct labels

Workflow has been set up.