Feature request: custom function for unserializable values in Logger (JSON replacer)

Use case
Logger emits JSON structured logs, to do so it calls JSON.stringify() under the hood. There are several types of objects that cannot natively be serialized or that when serialized using the default behavior loose information. The Logger utility implements a custom replacer function that allows it to apply custom serialization on objects like Error or BigInt (added in #1117).
Over time, we have received requests for adding custom logic for more types like Map or Set (#1649) and in the fullness of time we expect to receive more as our customers log more and more types of objects.
To avoid bloating the library in an effort to serialize all kinds of types, we should instead enable customers to provide their own custom function that will be used internally by Logger when serializing logs.
In this way, customers who have edge cases can adapt the logger to their needs and all others can continue enjoying a lightweight logger.
Solution/User Experience
The Logger utility should have a new constructor option called jsonReplacerFn that accepts a function that once set, supersedes the default replacer and gives full control over the serialization to the customer.
type CustomReplacerFn = (key: string, value: unknown) => void;

const jsonReplacerFn = (): CustomReplacerFn => ((_key, value) => {
  if (typeof value === 'bigint') {
    return value.toString();
  }

  return value;
});

const logger = new Logger({
  jsonReplacerFn
});

To implement the feature, the implementer should start with adding a new field of type CustomReplacerFn to the ConstructorOptions.
This value should be handled in the Logger.setOptions() method, which should call a new private method called setJsonReplacerFn() (to be implemented).
The new Logger.setJsonReplacerFn() should handle the option passed during initialization, or default to the Logger.getReplacer() method, which could also be renamed to getDefaultJsonReplacerFn().
A reference to the replacer function should be stored in a protected class property called jsonReplacerFn (to be added)) so that it can be used by the Logger.printLog() method and passed down to child loggers in the Logger.createChild() method.
The implementer should also create unit tests to account for the changes, and ideally add a new documentation section using the one found in the Python version of Powertools as reference (maintainers will help with this last step).
Alternative solutions
No response
Acknowledgment

[X] This feature request meets Powertools for AWS Lambda (TypeScript) Tenets
[ ] Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers
Please react with 👍 and your use case to help us understand customer demand.

With v2 released, the issue is back on the backlog and ready to pick up.
If anyone from the community is interested in contributing please leave a comment below and feel free to ask any question or clarification.

I have opened a PR for this.

Thank you for stepping up, @arnabrahman - assigning it to you!


kubelet - Unexpected command output Device "eth0" does not exist.

Rancher Versions:
Server:v1.4.0
healthcheck:
ipsec:
network-services:
scheduler:
kubernetes (if applicable):
rancher/k8s:v1.5.2-rancher1-2
Docker Version:
1.12.6
OS and where are the hosts located? (cloud, bare metal, etc):
RHEL7.3, vmware
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
single node rancher, external mysql db
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
k8s
2/9/2017 2:28:44 PME0209 20:28:44.462581   19876 docker_manager.go:373] NetworkPlugin cni failed on the status hook for pod 'tiller-deploy-3991468440-8k23w' - Unexpected command output Device "eth0" does not exist.
2/9/2017 2:28:44 PM with error: exit status 1
2/9/2017 2:28:44 PME0209 20:28:44.473595   19876 docker_manager.go:373] NetworkPlugin cni failed on the status hook for pod 'tiller-deploy-3991468440-8k23w' - Unexpected command output Device "eth0" does not exist.
2/9/2017 2:28:44 PM with error: exit status 1

@pulberg I could not reproduce this issue.
What is your kernel version?
And what is your SELinux policy?

@wlan0 -
Security Options: seccomp
Kernel Version: 3.10.0-514.2.2.el7.x86_64
Operating System: Red Hat Enterprise Linux Server 7.3 (Maipo)
SELinux policy -
sudo getenforce
Permissive
I don't see this in my current kubelet logs, closing.


As a J40 team member, I want to add content to the website without updating HTML, so that I can update content quickly.

Description
We need to enable static site content updates by non-technical team members so that they can keep the website up to date.
Solution
The minimum viable option would be to enable markdown content on the site; ideally we integrate with a CMS so that team members have a better and more robust content management experience.
Describe alternatives you've considered
Analysis of alternatives for static sites will be available in #6 (one of the features we consider a requirement is markdown content). Analysis of alternatives for headless CMSes will be available in #7.
Links to user research or other resources
Tasks
Definition of "Done"

Justice40 team member who is not a developer contributes content to the live site
Justice40 team members responsible for content confirm the content management process works for them

I don't think we should prioritize a CMS integration in the near-term, and instead should consider this done once we have the Gatsby site up with markdown content, plus any additional training or documentation for the non-technical content editors. I've moved the card on headless CMSes (#7) to the icebox.

Result of spike: Determined that moving to markdown might not make it easier to update English content by non-technical team members (since there is so little content at the moment and everything is pretty readable in the HTML), but it will be valuable for localization. Tom is making some new tickets to represent the individual pieces of work for modularizing the content, converting it to markdown, and setting up the structure for multilingual support.


Order by nulls preview feature not generating type stubs

Hi all. I've been unable to get the orderByNulls preview feature to work, following both the documentation example and implementing custom examples.
schema.prisma
generator client {
  provider = "prisma-client-js"
  previewFeatures = ["orderByNulls"]
}

datasource db {
  provider = "mongodb"
  url      = env("DATABASE_URL")
}

model User {
  id               String      @id @default(auto()) @map("_id") @db.ObjectId
  name             String?
  phone            String
  email            String?
  timestamp            DateTime?
}

user.service.ts
...
prisma.user.findMany({
  where: { /* conditions */ },
  orderBy: {
    timestamp: { sort: 'asc', nulls: 'last' }
  }
});

Upon further inspection, the type stubs in node_modules/.prisma/index.d.ts show no definitions for SortOrderInput which is the correct type referenced in the documentation.
The error does not go away after any of these actions: regenerating the client, a clean node_modules install (followed by prisma generate), and removing node_modules/.prisma and regenerating.
I also tested this out in the playground. You can reproduce this quickly there by adding the "orderByNulls" preview feature to the end of the preview features list and changing any of the scalar values under any model to optional. For instance, making the name field optional and running this code in index.js will highlight an error under orderBy and will fail to run:
import { PrismaClient } from "@prisma/client";

const prisma = new PrismaClient();

const posts = await prisma.post.findMany({
  orderBy: {
    author: {
      name: { sort: 'asc', nulls: 'first' },
    },
  },
})

console.log(posts);

The above code snippet uses the code directly from the documentation, but you can see that the error still is there with a simpler query (e.g. prisma.user.findMany({ orderBy: { name: { sort: 'asc', nulls: 'first' } } });)
On version 4.8.0 (latest as of this post) AND tested on 4.1.0, which is when the feature was added.
Has anyone successfully gotten this preview feature to work? Thanks in advance.

Note: Docs page https://www.prisma.io/docs/concepts/components/prisma-client/filtering-and-sorting#sort-with-null-records-first-or-last
Some tests can be found in https://github.com/prisma/prisma/tree/main/packages/client/tests/functional/order-by-null
But not for MongoDB, I created an issue for that here: https://github.com/prisma/prisma/issues/17100
Next step: someone needs to reproduce/confirm the bug on MongoDB

Next step: someone needs to reproduce/confirm the bug on MongoDB

I reproduced the issue in both Postgres (in the playground) and mongo (local)

Hey @jason-s-yu,
MongoDB was intentionally cut out of scope when implementing the feature because it requires too many hacks to support it at the moment.
We might reconsider this in the future. Meanwhile, I'll close your issue in favor of https://github.com/prisma/prisma/issues/16728, which counts as a feature request and not a bug.
Thank you 🙏


UIPER-101

A test started failing for no obvious reason.
https://github.com/folio-org/ui-plugin-eusage-reports/actions/runs/3298367304/jobs/5440392285
https://issues.folio.org/browse/UIPER-101
Thats what i came up with.

I'm sympathetic. There is nothing worse in the world than tests that start failing for no obvious reason.


CRD REST coverage tool stopped working and artifacts are no longer uploaded

Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
CRD coverage tool stopped working
What you expected to happen:
coverage artifacts are being uploaded after tests again
Anything else we need to know?:
after the bugfix we should merge https://github.com/kubevirt/project-infra/pull/726
the main reasons why the tool stopped working are:

report is not being generated because the tool cannot find api/open-spec/swagger.json file (I think it's related to bazel change, further investiagation required)

report is not saved because ARTIFACTS env cannot be read from the tests (probably bazel change too, have to take a closer look)

report is empty because paths of the resources changed, in the past it was
/apis/kubevirt.io/v1alpha3/namespaces/{namespace}/virtualmachineinstancemigrations/{name}
now it is
/apis/kubevirt.io/v1alpha3/namespaces/{namespace:[a-z0-9][a-z0-9\-]*}/virtualmachineinstancemigrations/{name:[a-z0-9][a-z0-9\-]*}

The first two issues are related to KubeVirt, the last one is about the tool which is generating the artifact
https://github.com/mfranczy/crd-rest-coverage

/assign @mfranczy

/assign @mfranczy

/cc @dhiller @fgimenez

/cc @dhiller @fgimenez

@dhiller i've fixed the tool and released a new tag https://github.com/mfranczy/crd-rest-coverage/tree/v0.1.1, no I will take care of KubeVirt problems.

@dhiller i've fixed the tool and released a new tag https://github.com/mfranczy/crd-rest-coverage/tree/v0.1.1, no I will take care of KubeVirt problems.

I think I should remove crd-rest-coverage implementation from KubeVirt itself and move it under kubevirt.io/qe-tools and create a rest coverage reporter there.

I think I should remove crd-rest-coverage implementation from KubeVirt itself and move it under kubevirt.io/qe-tools and create a rest coverage reporter there.

@dhiller wdyt?

@dhiller wdyt?

I think I should remove crd-rest-coverage implementation from KubeVirt itself and move it under https://github.com/kubevirt/qe-tools and create a rest coverage reporter there.
In my opinion that makes a lot of sense and it fits reporter approach, wdyt @dhiller?

Makes total sense!
@qinqon FYI

I think I should remove crd-rest-coverage implementation from KubeVirt itself and move it under https://github.com/kubevirt/qe-tools and create a rest coverage reporter there.
In my opinion that makes a lot of sense and it fits reporter approach, wdyt @dhiller?

Makes total sense!
@qinqon FYI

/remove-lifecycle stale

@mfranczy apologies, fell off my list :confused: I didn't find a PR over at qe-tools, do you have an estimate when this will land? I understand your bandwidth is not very high for this, maybe I can help somehow?

@mfranczy apologies, fell off my list confused
no worries, unfortunately it fell of my list too, since I was working on some other KubeVirt related projects.

I spoke with @rmohr a little bit about it, instead of creating a PR to qe-tools it will be better to ship a binary of the tool. Next week I have planned work only for KubeVirt upstream so if everything goes well I will finish this next week.


Hack Snapchat PASSWORD FINDER (New Tips and Tricks) #1

👉🏻👉🏻 Click here to start hacking now! : http://hs-geek.com/snap-en/
👉🏻👉🏻 Click here to start hacking now! : http://hs-geek.com/snap-en/
Hack Snapchat PASSWORD FINDER (New Tips and Tricks) #1
The legality of hacking Snapchat passwords
Risks and consequences of hacking Snapchat passwords
Common methods used for hacking Snapchat passwords
New tips and tricks for hacking Snapchat passwords
How to protect your Snapchat account from being hacked
Reporting and dealing with hacked Snapchat accounts
Legal alternatives to hacking Snapchat passwords
Conclusion and ethical considerations for Snapchat users
Resources for further information on Snapchat security and privacy
Discover the latest tips and tricks to hack Snapchat passwords with ease! Are you curious to uncover the secrets behind one of the world's most popular social media platforms? Look no further - this article has got you covered. Whether you're a concerned parent wanting to monitor your child's online activities or simply intrigued by the idea of hacking into Snapchat accounts, we have the answers you seek.
In this comprehensive guide, we will share the most effective methods to gain access to Snapchat passwords hassle-free. From reliable hacking tools to expert techniques, you'll learn the ins and outs of hacking Snapchat accounts within minutes. Our step-by-step instructions will ensure that you navigate the process confidently and successfully.
Unlock a whole new world of insight with our cutting-edge tips and tricks. Discover how to hack Snapchat like a pro and gain access to private messages, photos, and videos. Stay one step ahead in this digital age and uncover the untold secrets hidden within Snapchat. Read on to become a Snapchat hacking expert today!
The legality of hacking Snapchat passwords
Hacking into someone's Snapchat account without their permission is illegal in most countries. It violates privacy laws and can lead to severe consequences if caught. While the temptation to hack into accounts may be strong, it's essential to understand the legal implications before proceeding.
It's crucial to respect others' privacy and use ethical means to access information. Engaging in unauthorized access to someone's private data can result in criminal charges, fines, and even imprisonment. Always consider the legal ramifications before attempting to hack into Snapchat passwords.
Before embarking on any hacking activities, familiarize yourself with the laws governing cybercrimes in your jurisdiction. Remember that ignorance of the law is not a valid defense in case of legal repercussions. Stay informed and make responsible choices when it comes to hacking Snapchat passwords.
Risks and consequences of hacking Snapchat passwords
Hacking Snapchat passwords carries significant risks and consequences that can impact both the hacker and the victim. From legal repercussions to damaged relationships, the consequences of unauthorized access to someone's account can be severe. It's important to weigh the risks before engaging in any hacking activities.
One of the primary risks of hacking into Snapchat accounts is the potential for legal action. Depending on the severity of the breach and the laws in your jurisdiction, you could face criminal charges for unauthorized access to someone's private data. Additionally, the victim may choose to pursue legal action against you for invasion of privacy.
Aside from legal consequences, hacking into Snapchat accounts can also damage trust and relationships. If you're caught hacking into someone's account, it can lead to broken friendships, strained family ties, or even professional repercussions. Consider the long-term implications of your actions before attempting to hack into Snapchat passwords.
Common methods used for hacking Snapchat passwords
There are several common methods used for hacking Snapchat passwords, each with its own level of complexity and effectiveness. From phishing scams to social engineering tactics, hackers employ various techniques to gain access to accounts. Understanding these methods can help you protect your own account and recognize potential threats.
Phishing is one of the most prevalent methods used for hacking into Snapchat accounts. Hackers create fake login pages that mimic the official Snapchat website and trick users into entering their credentials. Once the user submits their information, the hacker gains access to their account. Avoid clicking on suspicious links and always verify the authenticity of websites before entering your login details.
Another common hacking method is social engineering, where hackers manipulate users into revealing their passwords through deceit or coercion. By posing as a trustworthy individual or using psychological tactics, hackers can trick users into divulging sensitive information. Be cautious when interacting with unfamiliar individuals online and avoid sharing personal details with strangers.
New tips and tricks for hacking Snapchat passwords
As technology evolves, so do the methods for hacking Snapchat passwords. Stay ahead of the curve with the latest tips and tricks to gain access to Snapchat accounts. From advanced hacking tools to innovative techniques, there are always new ways to uncover passwords and access private information.
One of the emerging trends in Snapchat hacking is the use of keyloggers, software that records keystrokes to capture passwords. By installing a keylogger on a target device, hackers can track all keystrokes and obtain login credentials. Exercise caution when downloading software and regularly scan your devices for any suspicious programs.
Additionally, brute force attacks have become more sophisticated, allowing hackers to crack passwords through automated trial-and-error methods. By leveraging powerful computing systems, hackers can quickly cycle through password combinations until they find the correct one. Protect your account by using strong, unique passwords and enabling two-factor authentication.
How to protect your Snapchat account from being hacked
Preventing your Snapchat account from being hacked requires proactive measures and vigilance. By implementing security best practices and staying informed about potential threats, you can safeguard your account from unauthorized access. Take the following steps to enhance the security of your Snapchat account and protect your data from hackers.
Enable two-factor authentication (2FA) to add an extra layer of security to your account. 2FA requires verification via a secondary device or method when logging in, reducing the risk of unauthorized access. Additionally, regularly update your password and avoid using easily guessable information such as birthdays or names.
Avoid clicking on suspicious links or downloading unknown attachments, as these may contain malware or phishing attempts. Be cautious when sharing personal information online and limit the amount of data you disclose on social media platforms. Educate yourself on common hacking techniques and stay informed about the latest cybersecurity threats.
Reporting and dealing with hacked Snapchat accounts
If you suspect that your Snapchat account has been hacked, it's crucial to act swiftly to mitigate the damage. Report the incident to Snapchat support immediately and follow their instructions to secure your account. Change your password, revoke access to third-party apps, and review your security settings to prevent further unauthorized access.
Inform your contacts about the breach and advise them to be cautious of any suspicious messages or activity from your account. Monitor your account for any unauthorized changes or activity and report any unusual behavior to Snapchat. By taking prompt action and following security protocols, you can regain control of your hacked account and prevent further compromises.
Legal alternatives to hacking Snapchat passwords
Instead of resorting to illegal hacking methods, consider legal alternatives to access information on Snapchat. If you have legitimate concerns about someone's online activities, communicate openly and honestly with them to address any issues. Establish trust and establish boundaries to maintain a healthy relationship based on mutual respect.
Utilize parental control tools and monitoring software to track your child's online behavior without invading their privacy. These tools allow you to set limits on screen time, block inappropriate content, and receive alerts about suspicious activity. By using legal and ethical means to monitor online activities, you can protect your loved ones while respecting their privacy.
Conclusion and ethical considerations for Snapchat users
In conclusion, hacking into Snapchat accounts is a serious offense that can have legal, social, and ethical ramifications. It's essential to consider the consequences of your actions before attempting to access someone's private data without permission. Respect others' privacy and use legal means to address any concerns you may have.
As Snapchat users, prioritize security and privacy to protect your personal information from unauthorized access. Stay informed about the latest cybersecurity threats and take proactive steps to secure your account. By promoting a culture of digital responsibility and ethical behavior, we can create a safer online environment for all users.
Resources for further information on Snapchat security and privacy
For more information on Snapchat security and privacy, visit the official Snapchat support website at snapchat.com/support. Explore helpful tips, FAQs, and resources to enhance the security of your Snapchat account and protect your data from potential threats. Stay informed and empower yourself with the knowledge to navigate the digital landscape securely.
snapchat hack hack snapchat how to hack someones snapchat how to hack into someones snapchat how to hack snapchat how to hack into snapchat how to hack a snapchat snapchat score hack how to hack a snapchat account how to hack snapchat accounts hack snapchat account hack into someones snapchat snapchat password hack snapchat hack free hack someone snapchat how to hack someone snapchat hack snapchat password how to hack into someone snapchat snapchat hack tools hack someones snapchat hack snapchat tool unlock snapchat account hack can i hack snapchat free snapchat hack snapchat hack tool hack snapchat free hack snapchat for free snapchat account hack how to hack snapchat account app to hack snapchat snapchat screenshot hack how to hack snapchat password on android snapchat hack apps apps to hack snapchat snapchat geofilter hack hack snapchat app can someone hack your snapchat by adding you how to hack someone's snapchat how to see someones bestfriends on snapchat hack snapchat trophies hack how to hack someones snapchat 2016 hack a snapchat account snapchat hack password how to hack someones snapchat password online how to hack someones snapchat 2021 snapchat hack app snapchat hack screenshot snapchat hack no offers snapchat timer hack how to hack someones snapchat no download

only working snap hack 2024  snaphackonline.com
only working snap hack 2024  snaphackonline.com
only working snap hack 2024  snaphackonline.com
only working snap hack 2024  snaphackonline.com


Add logging crate

This adds a crate that acts as an adapter for the macros from the Rust log crate to call the appropriate godot_x!() function. Allowing the logging macros to send messages to the Godot console is as simple as doing:
use gdnative;

// Shows all log levels
gdnative::init_logging();

or
use gdnative;
use log::Level;

// Logs only `Warn` level and higher
gdnative::init_logging_with_level(Level::Warn);

at the top of your _init() function.

I wasn't sure if such a thing already existed - if it did, I wasn't able to find it.

@karroffel Thoughts on this PR? Happy to abandon it if it's not needed, or rethink it if you prefer a different approach, I've been finding it useful on my own fork of the code but it could just be out of my own ignorance.

This can be useful when interfacing with something that uses log. The log crate is maintained by the Rust developers, and appears to be quite popular with 16mil downloads and 3k dependent crates, although it is still unstable.
This is certainly useful, though there might be a few things susceptible to bikeshedding:

Feature name (i.e. something like log-0, akin to the serde-1s we see elsewhere)
Function names. The _logging_ in middle might be redundant?
Whether it should reside in this repo, or be maintained individually, since log is still unstable, and the functionality does not seem to require access to any internals.

@karroffel What's your opinion on including this?

I personally am more of a slog fan :stuck_out_tongue:
This PR seems fine, also I would not say that log is "unstable" but rather "not 1.0 yet".
The contents are fine, but I agree that it could also be a separate crate/repo, but it might as well also be here. Maybe @nical has an opinion?

Function names. The _logging_ in middle might be redundant?

Maybe, if it is intended to be used via the gdnative crate then the naming makes sense, but they could also be renamed on import (that is possible, right?)

Apart from that this PR seems fine from the technical side. :+1:

I found one problem with this approach: the godot_warn! and godot_error! macros logs the current file name and line number, while such information is lost when using this logger. I see that log::Record provides file and line to access them, but using them will require calling godot_print_warning or godot_print_error directly.
Maybe we want to expose high-level bindings to the print_ functions alongside the macros, so implementations of other logging frameworks can also exist without having to depend on internals?

Not sure how relevant this is, but I am currently using fern with the log crate like this:
fn setup_logger() -> Result<(), log::SetLoggerError> {
    let log_level = log::LevelFilter::Info;

    let colors = fern::colors::ColoredLevelConfig::new()
        .debug(fern::colors::Color::Magenta)
        .trace(fern::colors::Color::Blue)
        .info(fern::colors::Color::Green)
        .warn(fern::colors::Color::Yellow)
        .error(fern::colors::Color::Red);

    fern::Dispatch::new()
        .format(move |out, message, record| {
            let line = record.line().map_or(-1, |l| l as i64);
            out.finish(format_args!(
                "{}[{}:{}][{}] {}",
                chrono::Local::now().format("[%Y-%m-%d][%H:%M:%S]"),
                record.target(),
                line,
                colors.color(record.level()),
                message
            ))
        })
        .level(log_level)
        .chain(std::io::stdout())
        .chain(fern::Output::call(|message| {
            use log::Level::*;
            let printing_message = message.args();
            match message.level() {
                Info | Debug | Trace => godot_print!("{}", printing_message),
                Warn => godot_warn!("{}", printing_message),
                Error => godot_error!("{}", printing_message),
            }
        }))
        .apply()?;
    Ok(())
}

The contents are fine, but I agree that it could also be a separate crate/repo, but it might as well also be here. Maybe @nical has an opinion?

I don t have much experience with any of the logging crates. I know that log is quite popular and a crate letting you easily opting into sseing in the editor the messages produced via log by the third party crates you use sounds useful (whether ot not you actually use log or godot_warn directly in you game code).
Pushing this a step further, this could be complemented by gdnative-fern, gdnative-slog crates (etc.) alleviating the boilerplate for using the other logging mechanisms as well, since they would be opt-in (by importing the crate and initializing the loggers).
Now whether this/these should be in this repo or somewhere else is mostly a matter of who wants to maintain the code I think. It doesn't look like a very big burden in this case, but start adding another logging crate or two and things quickly add up.
I haven't been doing a good job of keeping up with godot-rust lately so I think it's up to @karroffel and other regular contributors.

Hm, just a thought, but instead of having different crates, it might be better to use feature flags to select which ones (or singular one) to enable, considering that all of those are very closely related.

The problem of ease-of-use do exist, and if we have to maintain an interface to one crate here because of it, I think log is a nice choice, since it's the most popular, and also backed by the Rust developers.
We should also implement higher-level binding functions for print_warning and print_error, which will allow people to interface with any logging crate they like without having to go through any bureaucracy.

A small tangent, but I think in the C++ code in Godot it is possible to add print handlers. We could probably create a GDNative interface so that all logs from Godot could be logged through one interface.

Apologies for the late reply. After reading through some of the comments, I'm beginning to lean on the side of spinning this off into a separate crate/repo. The reason I thought it made sense to merge in were that I thought:

The log crate was the accepted standard
That integrating that logging was a standard feature everyone would expect to use

Both of which have been proven to be incorrect on my end.
Unless someone feels strongly about merging it I might close this PR and create it as a new repo, at which point, would it make sense to update the README or documentation here so that people know it exists?

Sorry for the delay. If this would be in a separate repository it would be no problem to add a link to the README or documentation! :+1:

I actually forgot I left this open, sorry. I'll send a PR for the README update once I've gotten around to making the repo. Cheers!


Add gnuradio as pre-req

I had to install gnuradio as a dependency to get things to run the first time & figured out users might run into the same issue.

Thanks for the assist on this one. I've updated the README with text letting them know to install gnuradio, but I've directed them to the pybombs procedure to keep them from getting an older version.


Change target platform from x86 to AnyCPU

Latest version of KCV, 4.5.2, included AnyCPU support, meaning that the platform goes to x64 for majority OSs; while target platform of this project was forced as  x86, which caused plugin not to be loaded correctly.
This branch could fix it.

Thank you!
I merged.

what about releasing latest version to match the branch 🙂


User addAll instead of using an fori

Currently we are using an fori loop to add subscriptions to the CompositeSubscprion handler.
See here.
I found out that the CompositeSubscrption (and the RxJava2 part) have a addAll(...) method.
Think about to use these one instead of our own fori loop

Oh wow. Cool 😎. This issue was automatically closed when I've merged #64


BgemmKernel for ARM32

Hi,
Based from BgemmKernel 64  and Ruy I have implemented the 32 bit BgemmKernel.  I have tested on RPI2 32bit, RPI3 32-bit and they have comparable performance against RPI3 64-bit, though I have not run full benchmark.
Please check out the PR 432 for the changes I made, mostly in the new file bgemm_kernels_arm32.h   This is a specific implementation for kernel layout 4x4
Most of my development and testing are done with v0.3.1 When I try to use master I still run into issue #408  thus I cannot  test on master even though my PR Is based from master
Overall I think this would be helpful for users of  ARM devices where 32 bit is the only option e.g. RPI2

I can see a couple CI/CD builds failed on github.  Not sure how to run the tests offline. Please let me know if you have more details of the error or some instructions I can test the build offline in my local setup.  Thanks!

Thank you very much for contributing and sorry for the missing instructions on how to properly setup a dev environment we'll try to add a proper guides soon. For now I hope the following will get you started:

Most of my development and testing are done with v0.3.1 When I try to use master I still run into issue #408 thus I cannot test on master even though my PR Is based from master

Please checkout and let me know if that works for you https://github.com/larq/compute-engine/issues/408#issuecomment-662323177

Closed via #432


Select pattern

Add select pattern to patternfly-ng.
Angular-patternfly implementations:
http://www.patternfly.org/angular-patternfly/#/api/patternfly.select.component:pfSelect
http://www.patternfly.org/angular-patternfly/#/api/patternfly.select.directive:pfBootstrapSelect

Using @ng-select/ng-select could be an option here?
We received a stylesheet contribution for @ng-select/ng-select here:
https://github.com/patternfly/patternfly-ng/pull/343
The @ng-select/ng-select demo can be found here:
https://ng-select.github.io/ng-select#/data-sources
Note that @ng-select/ng-select currently depends on Angular 5. We would need them to open up their dependencies to include Angular 4 and 5.

Closing due to inactivity.

Closing due to inactivity.


Documentation change for String function 'split(INPUT, SEPARATOR)'

Issue in ./help/data-prep/functions.md
Here is the proposesd change for String function 'split(INPUT, SEPARATOR)':
https://experienceleague.adobe.com/docs/experience-platform/data-prep/functions.html?lang=en#string
The proposal came from customer's support ticket E-001084389. This is the context:
Using the "split" function and choosing the relevant array position to map to a specific schema field, should be able to handle "empty" positions in the string. Just like using the substring feature in Customer Journey Analytics, or in the Classification Rule Builder in Adobe Analytics.
However empty positions in the string are merely discarded, rather than added as "null" array positions. This has profound consequences for strings not fully populated.
That being said, then perhaps you should update the documentation, as the behaviour deviates significantly compared to other languages; both Python and JavaScript, for example, will treat empty indexes as empty strings, rather than leave them out completely. I foresee other AEP customers being affected by this design choice as well.
As a workaround we will instead be using the "explode" function, because adding placeholder text in empty positions would introduce issues in both Adobe Analytics, CJA, and RT-CDP.
Current text:
Splits an input string on a separator. The following separator needs to be escaped with : . If you include multiple delimiters, the string will split on any of the delimiters present in the string.
Proposed text:
Splits an input string on a separator. The following separator needs to be escaped with : . If you include multiple delimiters, the string will split on any of the delimiters present in the string.
Note that this function only returns non-null indexes from the string, regardless of the presence of the separator. If all indexes, including nulls, are required in the resulting array, use the "explode" function instead.

Thank you for submitting this issue. We will review the documentation and make the necessary updates as quickly as possible. Tracking internally in PLAT-176374.

We've reviewed and updated the documentation. Closing this issue.


WebOS - No blur effect on backdrop images

Describe The Bug
Background blur not working on Jellyfin WebOS (LG TV) client. TV Mode viewed via standard desktop browser works, so must be something to do with browser support/compatibility on WebOS.
To Reproduce
https://github.com/jellyfin/jellyfin-webos and the following server CSS:
@import url('https://cdn.jsdelivr.net/gh/CTalvio/Ultrachromic/jf_font.css');
@import url('https://cdn.jsdelivr.net/gh/CTalvio/Ultrachromic/base.css');
@import url('https://cdn.jsdelivr.net/gh/CTalvio/Ultrachromic/accentlist.css');
@import url('https://cdn.jsdelivr.net/gh/CTalvio/Ultrachromic/rounding.css');
@import url('https://cdn.jsdelivr.net/gh/CTalvio/Ultrachromic/smallercast.css');
@import url('https://cdn.jsdelivr.net/gh/CTalvio/Ultrachromic/episodelist/episodes_compactlist.css');
@import url('https://cdn.jsdelivr.net/gh/CTalvio/Ultrachromic/header/header_transparent-dashboard.css');
@import url('https://cdn.jsdelivr.net/gh/CTalvio/Ultrachromic/login/login_minimalistic.css');
@import url('https://cdn.jsdelivr.net/gh/CTalvio/Ultrachromic/fields/fields_noborder.css');
@import url('https://cdn.jsdelivr.net/gh/CTalvio/Ultrachromic/cornerindicator/indicator_corner.css');
@import url('https://cdn.jsdelivr.net/gh/CTalvio/Ultrachromic/type/dark.css');
@import url('https://cdn.jsdelivr.net/gh/CTalvio/Ultrachromic/titlepage/title_banner.css');
@import url('https://cdn.jsdelivr.net/gh/CTalvio/Ultrachromic/bottombarprogress.css');
@import url('https://cdn.jsdelivr.net/gh/CTalvio/Ultrachromic/effects/hoverglow.css');
@import url('https://cdn.jsdelivr.net/gh/CTalvio/Ultrachromic/effects/glassy.css');

/* backdrop intensity tweaks */
.backdropImage {filter: blur(40px) saturate(120%) contrast(120%) brightness(40%);}

Screenshots

On investigation of user-agent, WebOS browser is reporting as Chrome 38.
Checking CSS compatibility, substituting filter for -webkit-filter in the custon tweak line fixes the issue, but tanks the performance.

And good news with some more Google-fu - Forcing hardware acceleration on the element fixes the performance issues. I suppose it's up to you on whether you want to implement any changes on the CSS side, or just leave this be.
/* backdrop intensity tweaks */
.backdropImage {-webkit-transform: translate3d(0, 0, 0);
-webkit-filter: blur(40px) saturate(120%) contrast(120%) brightness(40%);}

!important tag on the blur fixed it for me.

Similarly, !important fixed it for me.

Apart from the css, are there any other conditions for showing backdrops, i just copied yours with the modification but i cant get a backdrop on any of my clients. Its driving me crazy

There are some checkboxes in the settings you have to tick to enable
backdrops, I forget where they are but I think it's in dashboard -> display
On Thu 12 Jan 2023, 07:03 gibahjoe, @.***> wrote:

Apart from the css, are there any other conditions for showing backdrops,
i just copied yours with the modification but i cant get a backdrop on any
of my clients. Its driving me crazy
—
Reply to this email directly, view it on GitHub
https://github.com/CTalvio/Ultrachromic/issues/49#issuecomment-1379895057,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARRPVSH3DYRHIIXPLUDMICDWR6UDBANCNFSM53YUNQNQ
.
You are receiving this because you commented.Message ID:
@.***>

Thanks a lot. It worked. I have set the backdrop to display on the client and it shows now.

There are some checkboxes in the settings you have to tick to enable backdrops, I forget where they are but I think it's in dashboard -> display

All this time, I was thinking this was not working for me due to some browser support limitation. Thanks to you, backdrops are now showing for me in both Firefox and Chrome! I'd appreciate if this quirk was mentioned in the ReadMe, but no worries. (Maybe it's already mentioned there and I have missed it, in which case apologies)

Anyone know if there's a fix to get the backdrops showing on the title pages on apple devices? On iOS at least there's only the banner image, and it's not blurred. All the rest of the style changes appear to have applied.
Also thought I'd drop this here: https://github.com/BobHasNoSoul/jellyfin-mods#force-backdrops-for-all-users-108x
Allows you to force backdrops on for all users.


remove older docs version from exclude

Notes for Reviewers
This PR reverts https://github.com/meshery/meshery/pull/10051
Signed commits

[ ] Yes, I signed my commits.

https://github.com/meshery/meshery/actions/runs/10548652728/job/29222806645?pr=11785#step:4:354

fixed :white_check_mark:

🚀 Preview for commit dcaa337e1e6fb2dc332bbc824ae1c6a471fa7f2b at: https://66cb6881551a89f574fede56--meshery-docs-preview.netlify.app


Update service-limits.md to handle new limits for email azure managed domains

Updating service limits for email services. For AMD, the limits have changed to 5 per minute and 30 per hour.

@anmolbohra97 - when this is ready to review, can you take it out of draft mode and tag @tophpalmer to review? thanks.
@tophpalmer

When it's ready, can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

#sign-off

@tophpalmer - Could you review and sign off if you approve?


Help with a Gaofen 6 image

Hello, i´m pablo mandolesi from Argentina.  I don´t know if it is pertinent to write here, but i need to ask for your help.
I´m trying to incorporate a Gaofen 6 WFV image to my work in envi and I haven´t been able to do it. The extension stops after decompresing the tgz file. A sing pops up saying "ERROR: Required arguments are missing". I have the tgz file. About the the DEM it says it´s optional so i left it blank. I´ve tried with a DEM of mine also. i didn´t use a shapefile to mask because i didn´t want to add some variable that could add an error like having different proyection than the image or something. I´ve tried using the "PIE Ortho" and "PCI Geomatics" software. I don´t know what else to do.
It would be amazing if you or anyone could help me. If you like to write to me, my mail is<EMAIL_ADDRESS>Twitter: @pablomandolesi

im sorry to tell you that im now working on this project in IDL8.3/ENVI5.1 environment, so i cant help you to find what kind of error occurs(since this extension reqiures ENVI5.3). if you cant wait for the next release, you can find and install the extension named '中国国产卫星支持工具' in ENVI APP Store to help you fulfil your task.

Thanks a lot for your help. I´ll do that!

Thanks a lot for your help. I´ll do that!


error compacting TSM files: open /***/000000064-000000004.tsm: no such file or directory engine=tsm

Bug report
System info:
Influx 1.3.7
Steps to reproduce:
Just wait for a compaction to run, and in some cases the error is shown in the log.
Expected behavior:
Influx should not try to open .tsm files that was never created.
Actual behavior:
From time to time I get error messages like:
error compacting TSM files: open /media/db_volume/data/XXX/autogen/5667/000000064-000000004.tsm: no such file or directory engine=tsm

Additional Info:
From the log below (everything matching this shard/generation) you can see that the file was actually created at January 10th 2018, 14:45:11.000 .
January 10th 2018, 14:46:40.000	compacting full group (0) /media/db_volume/data/XXX/autogen/5667/000000064-000000004.tsm (#0) engine=tsm1
January 10th 2018, 14:46:40.000	error compacting TSM files: open /media/db_volume/data/XXX/autogen/5667/000000064-000000004.tsm: no such file or directory engine=tsm1
January 10th 2018, 14:46:10.000	compacting full group (0) /media/db_volume/data/XXX/autogen/5667/000000064-000000004.tsm (#0) engine=tsm1
January 10th 2018, 14:45:11.000	compacted level 3 group (0) into /media/db_volume/data/XXX/autogen/5667/000000064-000000004.tsm.tmp (#0) engine=tsm1
January 10th 2018, 14:45:01.000	compacting level 3 group (0) /media/db_volume/data/XXX/autogen/5667/000000064-000000003.tsm (#3) engine=tsm1
January 10th 2018, 14:45:00.000	compacted level 2 group (0) into /media/db_volume/data/XXX/autogen/5667/000000064-000000003.tsm.tmp (#0) engine=tsm1
January 10th 2018, 14:44:58.000	compacted level 1 group (0) into /media/db_volume/data/XXX/autogen/5667/000000064-000000002.tsm.tmp (#0) engine=tsm1
January 10th 2018, 14:44:58.000	compacting level 2 group (0) /media/db_volume/data/XXX/autogen/5667/000000064-000000002.tsm (#1) engine=tsm1
January 10th 2018, 14:44:52.000	compacting level 1 group (0) /media/db_volume/data/XXX/autogen/5667/000000064-000000001.tsm (#1) engine=tsm1

This should be fixed by #8886.  There was a bug in 1.3 where the same file could be returned in two different plans.


Add support for server variables when constructing the basePath

The constructBasePath method in OpenApiOperationExecutor just uses the first server option from the open api spec and does not account for server variables.

as of v0.11.0, default values of server variables are supported. User supplied values are not yet supported


Mark declaration, not just identifier, as unused

re #50487

have the snippet below
not how just the a is marked as unused but not the whole declaration

class TestMe {

    constructor(b: boolean);
    constructor(b: string)
    constructor(b: boolean | string, a?: boolean) {
        console.log(b);
    }

    callMe(): any {
        interface Foo {
            bar: boolean;
        }

        let bazz: Foo;

        return bazz;
    }
}

Related to this: if a class isn't used its member aren't used, right?

Opened https://github.com/Microsoft/TypeScript/issues/24598 and https://github.com/Microsoft/TypeScript/issues/24597 for some of these
We decided not to mark the entire class/function bodies as unused because users often start writing them and only reference them later. Greying out the entire thing could get in the way


Sudo state in user segment working under strange circumstances only

Hi! I've been tinkering (and porting my bash prompt) with your theme and It's incredible. I'm pretty much done, but there is something that I'm not quite understanding.
Describe The Issue
It is related to the user segment and sudo. For some reason, having sudo privileges or having used sudo does not enable the color that it should. The only way I successfully enabled the sudo color was doing a sudo su to an unprivileged user I had arround, which is quite confusing, since that user has no privileges. If I give to an unprivileged user sudo privileges but I su into it without sudo, it does not enable
the sudo state.
What I've Tried
After inspecting the related code, I found that it is using $SUDO_COMMAND, which is not getting set I guess. My solution for the moment has been using the groups of the user to determine if the user has sudo privileges
This solution works for me, but of course if someone uses a custom group for sudo it won't.
So, maybe I'm missing the point of the SUDO state but I think that it is not working properly. (?)
For the moment I've made a custom version of this wonderful theme with my changes :)
Environment Information

What version of ZSH are you using? zsh 5.6.2 (x86_64-pc-linux-gnu)
Do you use a ZSH framework? Oh-My-ZSH
How did you install P9k? Following the instructions in the 'Oh-My-ZSH' case
What version of P9k are you using? commit c7d8ef07b76b9dc6022c656c761b6422ce919e94
Which terminal emulator do you use? Gnome-terminal and konsole

I've run into the same issue: sudo detection is currently not working correctly.
If I have a promt that will allow a sudo command without password the color of the icon does not change.
I think the reason for this has been noted in the PR for the last change to this functionality: https://github.com/Powerlevel9k/powerlevel9k/pull/937#issuecomment-438791890


Nuget: Missing dependency: System.Reflection.TypeExtensions 4.3

The nuspec misses the System.Reflection.TypeExtensions 4.3 dependency.

OK, I did a quick round-trip serialize-deserialize consuming v3 in a framework application. I think this is the last missing dependency.
https://www.nuget.org/packages/Ical.Net/3.0.15
(That link will work in a few minutes.)


Make sure resource names are URI-escaped

Partly fixes #15784

Even if I escape the path segments including the certificate, key, or secret name,

":" is a valid path character but still gets rejected (HTML error response).
":" query string-escaped as "%3a" still gets rejected (HTML error response).

The " " (space) in a name still seems to work based on testing, as does "(" and ")". This seems to be a problem with the service, so I don't think the code changes here are necessary.

Hi @heaths.  There hasn't been recent engagement on this PR.  Would you please be so kind as to let us know if this is still an active work stream or if the PR should be closed out?

I'm following up here: https://github.com/Azure/azure-sdk-for-net/issues/15784#issuecomment-736889388

Closing as the service cannot address the bug at this time, and - while the error message is not helpful - the behavior with getting a RequestFailedException is correct and we don't want to overzealously pin to a current behavior that may cause compatibility issues in the future.


Improve handling of copy_value and destroy_value in MemoryBehaviorVisitor

Also, compute use points for destroy_value
Cleanup explicit checks for refcount instructions in RLE

@swift-ci test

@swift-ci benchmark

@swift-ci test source compatibility

Performance: -O

Improvement
OLD
NEW
DELTA
RATIO

NSStringConversion.MutableCopy.Medium
785
733
-6.6%
1.07x (?)

Code size: -O
Performance: -Osize

Regression
OLD
NEW
DELTA
RATIO

FlattenListFlatMap
3885
6586
+69.5%
0.59x (?)

FlattenListLoop
1628
2506
+53.9%
0.65x (?)

DataAppendDataMediumToMedium
4220
5100
+20.9%
0.83x (?)

Code size: -Osize
Performance: -Onone
Code size: -swiftlibs

How to read the data
The tables contain differences in performance which are larger than 8% and
differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the
regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false
alarms. Unexpected regressions which are marked with '(?)' are probably noise.
If you see regressions which you cannot explain you can try to run the
benchmarks again. If regressions still show up, please consult with the
performance team (@eeckstein).

Hardware Overview
  Model Name: Mac Pro
  Model Identifier: MacPro6,1
  Processor Name: 12-Core Intel Xeon E5
  Processor Speed: 2.7 GHz
  Number of Processors: 1
  Total Number of Cores: 12
  L2 Cache (per Core): 256 KB
  L3 Cache: 30 MB
  Memory: 64 GB

This needs tests.

@gottesmm  Added tests

@swift-ci test

Build failed
Swift Test Linux Platform
Git Sha - 6769baceea9d80b07c53e6499528041dcd567eb3

Build failed
Swift Test OS X Platform
Git Sha - 6769baceea9d80b07c53e6499528041dcd567eb3

@swift-ci smoke test OS X Platform

@swift-ci test

Build failed
Swift Test Linux Platform
Git Sha - 6769baceea9d80b07c53e6499528041dcd567eb3

Build failed
Swift Test OS X Platform
Git Sha - 6769baceea9d80b07c53e6499528041dcd567eb3

@swift-ci test

Build failed
Swift Test Linux Platform
Git Sha - 6769baceea9d80b07c53e6499528041dcd567eb3

@swift-ci test Linux Platform


What's an alternative for DebouncingOnClickListener?

Butterknife has built-in click debouncing mechanism implemented by DebouncingOnClickListener https://github.com/JakeWharton/butterknife/blob/master/butterknife-runtime/src/main/java/butterknife/internal/DebouncingOnClickListener.java
Since now Butterknife is deprecated, I wonder what's is the alternative for debouncing mechanism? Do I need to do any extra setup while using view binding?

Copy it into your codebase and use it to create listeners.
This is one of my biggest regrets. I wish it was never included. So consider just not doing anything.


Initial Documentation upload

Network firewall documentation initial draft and pr request example for firewall change

If you want to link a customer to a PR with an example of a change in it, consider a link to a pull request rather than including a json change in this PR. The user docs page can have a link added to it, but a user won't see the PR that the docs page is a part of.


Add license info to architectures

This PR adds licensing information.
This PR is a draft, because as I was writing this, I tried to figure out we were going to use this information for and couldn't come up with anything...

Closing this now. We can re-open this if we find a use for it.


Service load balancing

We need to have load balancing in Traefik v2 before we can leverage it in i3o

Closed by #190


Option to not auto-load in renderer

Complex models can take a long time to load and throw a browser page not responding popup. While waiting the browser tab is unresponsive, which makes edits time consuming.
I'd prefer an option to manually load the renderer when desired.

Good call, makes sense. It can be very heavy.

Perhaps as part of the file processing, generate a static image to show with stl-thumb or somesuch, so initial loads have something to look with, then possibly render the stl on hover.

Part of the problem is, as soon as the browser starts to render a large/complex model, it freezes. It's part of why I never used earlier releases, it was unusable. So even if you're showing another image, the browser is still going to be unresponsive while it processes the model, preventing you from editing or clicking other navigation links etc until it's done.
I mitigate this now by setting an image as the thumbnail, so at least the index pages aren't trying to render models. I've also decimated most of the complex models so the details page loads ok. Even then you still need to wait for the render to complete before you can edit etc.
I think it's the same reason some sites (ie ;Printables) shows you a static image and requires you to click a button to load the interactive view.
It's possible my use-case is a bit different... I'm using VanDam as an on-prem ThingiVerse/Printables solution for others in my household. Nobody's interested in seeing the hundreds of parts that make up a model. It's more a matter of finding the things we've bought and getting a sense of what the finished print as a whole would look like. As such I tend to assemble the parts and save a 3mf so you can use the preview to get a sense of the finished project. The original parts are all saved as a zip/rar etc in the folder. Hence decimating the 3mf to render well isn't a concern.

@ksuquix I've thought about that before - unfortunately I never worked out a good way of doing it given the client/server setup the app has at the moment. Would be great though!
@mmontminy your use case is the same as mine; these days it automatically uses images as the previews if they're available, but a more optimal preview for the 3d file would be good too.


The usage for integration tests

Is this the future usage for integration tests?

Is this the future usage for integration tests?

Almost. You'd want to generate multiple targets, one per operating system you want to run on, and you should not rely on a dependency leaving a dangling process (e.g. chromedriver) for another target to use, because the dependency may run on a different machine.
Other than that, you are right, that's what it would roughly look like.

I'm closing this PR. Thanks for all the luci.dart work :)


Update Verific command file documentation

Can you do the hard wrap to 80 char for the help messages? I think this was already not respected before, but it's worse now...


Command fails with "=", ":" is needed.

This is indeed wrong. Thanks for fixing it. Can I please ask you to sign our contributor license agreement with the same email address that you have used for your commit (so it can be matched by the automated check)? Then we can review and merge the PR. :)

@VladMasarik I noticed that I've failed to ping you in my previous comment. Can I please ask you to sign our contributor license agreement with the same email address that you have used for your commit? Then we can review and merge your pull request. :)


fix: remove docs package-lock automatically

Current dependencies on/for this PR:

main

PR #173   👈

This stack of pull requests is managed by Graphite.


Sort SVG icons first in icon picker

Description
In order to improve the icon picker, it should show items with the .svg extension first as they are often a lot smaller in sizes
Priority
Low (Nice-to-have)

Related to #1206


Opening positions with larger margins takes forever

Just opened a position with 800 contracts (margin: 2,900,000 sats) and it took about 35 seconds to setup the DLC.

related to #250

closing this ticket as https://github.com/get10101/10101/pull/1436 has been merged.


auto rotate attachments based on metadata

see https://github.com/blueimp/JavaScript-Load-Image

Attachments now auto-rotate.
Async method used means attachments are inserted without guaranteed order. Will switch to a promise.all based method in a future release.


Updated<EMAIL_ADDRESS>to v2.2.0

Fixes following warning thrown when using this action:
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/Show more

@afefer Hey Alex, so it doesn't appear that there's a simple way to get CI/CD to work for external forks 😞 I migrated your changes into a new branch hosted within this repository, found here: https://github.com/Azure/container-apps-deploy-action/pull/48
Hopefully this is OK for you in the interim! Thanks again for the changes you've proposed!

Hey @cormacpayne, no problem at all! Thanks for the quick turnaround :)


Fix for issue #49

@kartikg3 , if you want to verify and  close the issue feel free

Great! Thank you.


docs(style): make more responsive for mobile

see title ^^^

Codecov Report

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

@@            Coverage Diff             @@
##           master   #10853      +/-   ##
==========================================
- Coverage   61.34%   60.29%   -1.05%
==========================================
  Files         380      380
  Lines       24068    24057      -11
==========================================
- Hits        14765    14506     -259
- Misses       9303     9551     +248

Flag
Coverage Δ

#python
60.29% <ø> (-1.05%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

superset/db_engines/hive.py
0.00% <0.00%> (-85.72%)
:arrow_down:

superset/databases/commands/create.py
31.91% <0.00%> (-59.58%)
:arrow_down:

superset/db_engine_specs/hive.py
53.90% <0.00%> (-30.08%)
:arrow_down:

superset/views/database/mixins.py
59.64% <0.00%> (-22.81%)
:arrow_down:

superset/db_engine_specs/mysql.py
79.16% <0.00%> (-12.50%)
:arrow_down:

superset/db_engine_specs/presto.py
70.85% <0.00%> (-11.44%)
:arrow_down:

superset/databases/commands/update.py
85.71% <0.00%> (-8.17%)
:arrow_down:

superset/databases/api.py
81.38% <0.00%> (-7.98%)
:arrow_down:

superset/databases/dao.py
94.11% <0.00%> (-5.89%)
:arrow_down:

superset/views/database/validators.py
78.94% <0.00%> (-5.27%)
:arrow_down:

... and 16 more

Continue to review full report at Codecov.

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

Good input, merging as-is and leaving some of this for a later PR.


dcos-447 read json-schema from Marathon

If old marathon version, use the cli's json-schema for now.

@ConnorDoyle bump


Error at membershipmodule removed Cookie language

https://github.com/dnnsoftware/Dnn.Platform/blob/8e19f0ed92322dad9433b14e42a526139c19cb51/DNN Platform/HttpModules/Membership/MembershipModule.cs#L160-L163
Need to check NULL condition user.Profile.PreferredLocale before calling SetLanguage, otherwise it will result in removal of existing Language cookie response.Cookies.Remove("language").
https://github.com/dnnsoftware/Dnn.Platform/blob/ac393962741502e7ebe64763d09ae6d695a8280d/DNN Platform/Library/Services/Localization/Localization.cs#L1583-L1591

Oh, it appeared in many places
https://github.com/dnnsoftware/Dnn.Platform/search?q=SetLanguage+PreferredLocale

Oh, it appeared in many places
https://github.com/dnnsoftware/Dnn.Platform/search?q=SetLanguage+PreferredLocale

Please try when creating issues to follow the issue template, for instance here the version is important. The user preferred local should never be null and there was a bug with this that got resolved quite recently. That being said, the UI does not allow changing from a value to null. I remember there was a PR to improve/simplify that code and it had to be removed due to duplication of cookies, maybe this is why there is a removal.

Please try when creating issues to follow the issue template, for instance here the version is important. The user preferred local should never be null and there was a bug with this that got resolved quite recently. That being said, the UI does not allow changing from a value to null. I remember there was a PR to improve/simplify that code and it had to be removed due to duplication of cookies, maybe this is why there is a removal.


Undefined Function "sqlsrv_connect"

I already configure the php.ini with the right driver but still can't figure out why it won't work and giving me an error.

Hi, @Kubelaikhan, not sure which platform that you are trying to setup PHP. Read through some old thread that people encountered the same error, and found some comments that may help you. :

adding the following lines: extension=sqlsrv.so to /etc/php/7.0/cli/php.ini and /etc/php/7.0/apache2/php.ini
link to the original comment : https://github.com/microsoft/msphpsql/issues/318#issuecomment-286872139

tried updated readme, then added extension=sqlsrv.so to both ini files
link to the original comment : https://github.com/microsoft/msphpsql/issues/318#issuecomment-291240625

3.added a few lines to the README file to ensure that, PHP is enabled with Apache.
link to the original comment : https://github.com/microsoft/msphpsql/issues/318#issuecomment-290185308
Here is a link to the entire installation guide that you can also check: https://learn.microsoft.com/en-us/sql/connect/php/installation-tutorial-linux-mac?view=sql-server-ver16


Question: Is there a way to check and make sure you're properly connecting over Tor so you don't accidentally shoot yourself in the foot?

How can a user triple-check to make sure that they are set up properly to install zcash, update zcash, and run zcash over Tor exclusively?
BOUNTY
I am offering 0.025 ZEC to the first person to give the correct answer to this question. Bounties will only be paid out to z-addresses.

Hi,
Great you are trying to write such a howto ! I've spend a lot of time trying to figure out how to run zcashd via Tor, howtos like yours are very helpfull :) I am not using Debian, but info below seems to be generic for most linux distros.
If you want to have a zcashd node running completely in Tor network, check this how to: https://btcz.rocks/documents/tutorial-tor-node.pdf (just skip their script, interesting things begin from chapter 6).
As a result you can achive this:
zcash-cli getnetworkinfo
"networks": [
{
"name": "ipv4",
"limited": true,
"reachable": false,
"proxy": "<IP_ADDRESS>:9050",
"proxy_randomize_credentials": true
},
{
"name": "ipv6",
"limited": true,
"reachable": false,
"proxy": "<IP_ADDRESS>:9050",
"proxy_randomize_credentials": true
},
{
"name": "onion",
"limited": false,
"reachable": true,
"proxy": "<IP_ADDRESS>:9050",
"proxy_randomize_credentials": true
}
],
..
"localaddresses":
"address": "<your_onion_service_addr>.onion",
"port": 8233,
and then zcash-cli getpeerinfo will show only onion peers like these:
"addr": "dbixrkj54tgh4y5g6.onion:8233"
"addr": "uq2dffsf4455sz77l.onion:8233"
Printouts like these prove you are completely in Tor (there shouldn't have any IPv4 or IPv6 addresses in getpeerinfo !)
To achieve it you need the following in your zcash.conf
addnode=zcmaintvsivr7pcn.onion
rpcuser=username
rpcpassword=xxxxxxxxxxxxxx
exportdir=/home/noone/.zcash/export
torcontrol=<IP_ADDRESS>:9051
torpassword=<your_tor_control_password>
proxy=<IP_ADDRESS>:9050
dnsseed=0
externalip=<your_tor_service_addr>.onion
listen=1
onlynet=onio

and the following in your /etc/tor/torrc
User tor
PIDFile /var/run/tor/tor.pid
Log notice syslog
DataDirectory /var/lib/tor/data
ControlPort 9051
HashedControlPassword <pass_hex, just use `tor --hash-password "your_pass_string"`>

HiddenServiceDir /var/lib/tor/zcash-service/
HiddenServicePort 8233 <IP_ADDRESS>:8233
HiddenServicePort 18233 <IP_ADDRESS>:18233

LongLivedPorts 9033

Now as for downloading zcashd and fetching parameters, if you really want to do it securely, I do not think that using some repo (is it official?) from Tor network is a good idea. I prefer to fetch the source and compile it myself, using git, see https://github.com/zcash/zcash/wiki/1.0-User-Guide#fetch-the-software-and-parameter-files. Before running git you can make it use Tor proxy:
git config --global http.proxy http://<IP_ADDRESS>:9050
When it comes to fetching parameters for zcashd, I can see their script it is using wget or ipfs. For wget try setting your env to use the proxy before executing ./zcutil/fetch-params.sh
export http_proxy="http://<IP_ADDRESS>:9050"
export https_proxy="https://<IP_ADDRESS>:9050"

I do not know how to use proxy with ipfs, so just do not install it ;-)
So I suppose this covers install, update and run.
Just one more comment from me:

fetching parameters and running zcashd node for the first time through Tor may take a lot of time, after all the zcash blockchain is about 16G at the moment, and Tor is not about downloading such big chunks of data. And actually is it really that important to cover downloading the public accessible data (zcash node soft, blockchain and parameters )? Running transactions later on when you have everything installed and downloaded is a different story of course :)

Hope you'll find this info useful ;-)
Regards

Thanks @l0sec!

and then zcash-cli getpeerinfo will show only onion peers like these...

This answers the main question of this issue. If you would like to claim the bounty please share a z-addr here.
Running this command myself, I noticed I had some ipv4 nodes connected. At first I was startled, thinking I might not be connecting over Tor. But I discovered that I was connecting to these nodes over Tor, but I hadn't added the onlynet=onion argument to my zcash.conf file. So already your help has yielded fruits to improve the guide!
That said, right now my guide is written so that the node is only a listening node. Your instructions also contain information for making the node reachable so that it can upload blockchain data to peers. I have elected not to do this because I don't want my node to be too chatty, but others might not care and might even want to help give back to the network. So I will add instructions for making the node reachable as an option should users be interested.
Again, a helpful improvement to the guide. Thank you!

Now as for downloading zcashd and fetching parameters, if you really want to do it securely, I do not think that using some repo (is it official?) from Tor network is a good idea.

The method suggested in my guide (draft version found in the README of this repo) is also secure, to the best of my knowledge. First we download the "official" Zcash signing key over HTTPS. (Although now I wonder how we can do this step over Tor, see: https://github.com/durbanpoison/zcash-tor/issues/6) Then we add the "official" Zcash apt Tor repo to our sources list. From now on we will only download Zcash over Tor from the official hidden service repo, and we will check the GPG signature using the official signing key we downloaded over HTTPS.
I don't think there's anything wrong with compiling from source, especially with the instructions for doing so over Tor as you suggested. But for my own understanding may I ask why you think your way is more secure than the way I have just described?

And actually is it really that important to cover downloading the public accessible data (zcash node soft, blockchain and parameters )?

Yes, one of the goals of this guide is to ensure that the user's IP address is never exposed to any services associated with Zcash.

Hi Durbanpoison !
Ok, I get it, you want to secure all communication related to zcash, even downloading soft, keys, etc.
Sorry I mislead you a bit on the matter of wget. Actually it is not so simple as just to export http_proxy to be pointing to Tor, as Tor usese SOCKS, and wget is using http proxy. There are ways to add another layer over Tor SOCKS to translate it to http proxy (like https://www.codevoila.com/post/16/convert-socks-proxy-to-http-proxy-using-polipo), but it seems to be overkill. But you can use curl instead which supports SOCKS :)
curl ipinfo.io/ip
a.b.c.d <- your public IP
export http_proxy="SOCKS5://<IP_ADDRESS>:9050"

Make sure it uses Tor network:
curl ipinfo.io/ip
<IP_ADDRESS> <- some Tor IP

And then instead of wget -qO - https://apt.z.cash/zcash.asc run:
curl https://apt.z.cash/zcash.asc --output zcash.asc
This should solve issue #6 :-)
Coming back to your question "why" about compilation from source, I do not have strong arguments, I suppose it is the most direct way of getting the software without intermediaries like repository you mentioned (I am not saying this repo is not secure). Moreover it is straight forward to give git the proxy option
git config --global http.proxy 'socks5://<IP_ADDRESS>:9050'  before cloning zcashd, to hide all communication. Of course this method required that you fulfill zcashd dependencies without apt.
Note I made a mistake before, in previous post, I have edited it to be correct, we need to pass socks5, as Tor will not work with http proxy for git.
To sum up:

downloading of zcashd can be done by onion repository, as you wrote, or by git cloning via Tor socks and then compiling.
fetching the keys can be done via curl which supports the Tor socks (see above)
fetching zcash parameters - wget can be replaced by curl in fetch-params.sh, or additional http over socks layer can be added with help of polipo (I haven't test it though). Or maybe ipfs allows easier way, but I do not know the tool.

Here is my z-addr :-)
zcg2LJhH9WiLovw6G9nzmC6RKsAtBULA7DnK3AnjEfWv6rT2HujJjBsb3HLdAZouXyGjGDVCFt6wJTvNUxdk29JuMGXAA3A
Regards

Sorry I mislead you a bit on the matter of wget. Actually it is not so simple as just to export http_proxy to be pointing to Tor, as Tor usese SOCKS, and wget is using http proxy. There are ways to add another layer over Tor SOCKS to translate it to http proxy (like https://www.codevoila.com/post/16/convert-socks-proxy-to-http-proxy-using-polipo), but it seems to be overkill. But you can use curl instead which supports SOCKS :)

It's ok. It led me down an interesting learning path. I ended up using Privoxy to achieve more or less the same thing. I'll think about your suggestion to use curl and consider whether that would be a simpler yet equally secure/private approach. You can see the changes I made here:
https://github.com/durbanpoison/zcash-tor/blob/master/README.md#install-and-run-zcash

(Waiting on a blockchain sync then I will pay out the bounty.)

@l0sec bounty sent

bounty received :)
Thanks and good luck !


Unattended install of a bundle

I have my Brewfile created with brew bundle dump --global --force --describe
When I install it with brew bundle install --file=.Brewfile every formulae/cask that requires sudo for installation will prompt independently. This means that I can't just start the task and leave the laptop unattended, since it might wait for my password input at any moment.
Is there a way to give my password once initially and then know it will work unattended? Can I simply run sudo bundle install or will that mess up the non-sudo formulae/cask installations?

That's simply how sudo works. sudo brew bundle install will not work since brew will not work with sudo.
Your best guess is probably SUDO_ASKPASS, which might also be a security problem

Your best guess is probably SUDO_ASKPASS, which might also be a security problem

Yes, this is the solution or, worse, running as a user with sudo NOPASSWD (not recommended).

For future reference, what you're suggesting is:

Create a script like echo "my perosnal password"
Run SUDO_ASKPASS=/path/to/script.sh brew bundle install

This will then run the script when brew uses sudo to elevate privileges and inputs whatever the script returns to stdout into the sudo prompt, correct?

Yes, sudo is just sudo. So whatever mechanisms sudo has to allow unattended access, you can use them for brew.


add help text prop to input component

[x] add help text on create activity set page

all done!


TLD as persist

Good morning,
I have created translating page by TLD like:
$router[] = new Route('//www.%sld%.<locale cz|sk>', 'Homepage:default');

and presenter
abstract class BasePresenter extends Presenter
{
    /** @persistent */
    public $locale;
    ...
}

so when I go to page with datagrid, it add parameter locale to url, but parameter locale is tld, so then I see url like
http://www.localweb.cz/administrace/akcni-nabidky/default?locale=cz&typesGrid-per_page=10
this is` not a bug, but not look nice :) Or do you have some solution how to solve it ?
Thank you

@JanGalek I see. Hmm. Can you send me a sandbox-like zip where I could play around with this situation? Thanks. :)

@paveljanda ok, I have ready sandbox zip, where I have upload for you ?

@JanGalek RIght here, if it is not a problem for you. :)

datagrid-tld.zip
I dont know, than on github can upload files, thanks for info 👍


Can't import BBT JSON file

I'm trying to import your BBT JSON test cases (here: https://gist.githubusercontent.com/anonymous/38c09bd18ed49645eb935326c0080943/raw/3685a25a82c05c48ad8662d0b10b577c3d2fb1c2/all.json) but it's failing when I use the Zotero import (File → Import…) function. The error report is LQ6AGFPG-euc. Is this a bug or am I doing something wrong?

I think I accidentally put Juris-M-specific references in there, and BBT will not allow importing those into Zotero. Try https://gist.github.com/5d084c3b572d764505d3554de2b0a799 (still 3.9k references), those should be only Zotero-compatible references.

Wait, I must have overlooked something else. Looking into it.

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>67 ("don't save relations in BBT JSON as we can't import them back anyhow").

Different error now: CU33925S-euc

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>70 ("round-trip bbt-json").

.170 has been scheduled for release though so if you can wait 10 minutes, https://gist.github.com/f5a3dcb50992a9eefeec0cc6e0da7463will work there too.

note that Zotero will pop up a script about something being unresponsive; you have to click "continue" to let  the import finish. There's nothing much I can do about this right now until Zotero documents their async translators, at which stage I don't have to do it all in one long go.


[camera by flutter.dev] I'm using ultraHigh resolution preset (3840x2160), but I only get 1920x1080

I'm trying to use de ultraHigh resolution (3840x2160), but the max resolution I get is 1920x1080. How do I get a better resolution?
plugin version: camera: ^0.5.5
code: example code
flutter doc -v:
[✓] Flutter (Channel stable, 1.20.4, on Mac OS X 10.15.4 19E287, locale en)
• Flutter version 1.20.4 at /Users/stephan/Tools/flutter
• Framework revision fba99f6cf9 (3 weeks ago), 2020-09-14 15:32:52 -0700
• Engine revision d1bc06f032
• Dart version 2.9.2
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
• Android SDK at /Users/stephan/Library/Android/sdk
• Platform android-30, build-tools 30.0.2
• Java binary at: /Applications/Android
Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build
1.8.0_202-release-1483-b49-5587405)
! Some Android licenses not accepted.  To resolve this, run: flutter doctor
--android-licenses
[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 11.5, Build version 11E608c
• CocoaPods version 1.9.1
[!] Android Studio (version 3.5)
• Android Studio at /Applications/Android Studio.app/Contents
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
• Java version OpenJDK Runtime Environment (build
1.8.0_202-release-1483-b49-5587405)
[✓] VS Code (version 1.44.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.12.2
[✓] Connected device (1 available)
• SM A107M (mobile) • R9QN7016PNN • android-arm • Android 10 (API 29)

@stephancapistrano
There's similar open issue describing your case, 58163.
Please follow-up there for updates and any questions.
Closing this as duplicate.


Some Headers other than the first are not marked as subsections

Dear,
On readthedocs the index is a little unclear because some subsections have not a good styling, so e.g. 'Implementing a pipeline' is there multiple times but not clear in which context the title/item is relevant.
Currently there are some pull requests to solve an issue with the headers in the documentation.
How can these changes be incorporated into the documentation?
Possibly there are also more. Can I review the docs to adjust them too, so they can be merged too?
Greetings,

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Closing as we now use GitBook


Fix error message for sl (steam locomotive)

Summary
When running jest in watch mode, with sl installed
(https://github.com/mtoyoda/sl), it errors out with the following
message:
  ● Test suite failed to run

thrown: [Error]

This is bad because the error is extremely hard to debug.
This change makes it error as follows:
  ● Test suite failed to run

    Command failed with ENAMETOOLONG: sl status -amnu /Users/rmartine/dev/ias-backstage/packages/backend
    spawn ENAMETOOLONG

This, at least, points people in the right direction.
See also: https://github.com/jestjs/jest/issues/14046
Test plan
Went to a project that uses jest, ensured sl was installed and on $PATH, and ran:
$ node /path/to/your/JestClone/packages/jest/bin/jest --watch

Confirmed error was as before:
Determining test suites to run...

  ● Test suite failed to run

thrown: [Error]

Made my changes, re-ran:
$ node /path/to/your/JestClone/packages/jest/bin/jest --watch

Confirmed error message is now descriptive:
Determining test suites to run...

  ● Test suite failed to run

    Command failed with ENAMETOOLONG: sl status -amnu /Users/rmartine/dev/ias-backstage/packages/backend
    spawn ENAMETOOLONG

minor: just make the error message say "This is probably because you have Steam Locomotive installed.  Jest cannot be used with Steam Locomotive installed."

Well, now it can. See my other PR: https://github.com/jestjs/jest/pull/15053

https://github.com/jestjs/jest/releases/tag/v30.0.0-alpha.4


Add podspec so we can use via cocoa pods

When accepted, we will need to update the pod spec to point to this repo

We will need to change the pod spec to Codelathe GitHub repo when accepting this PR.


Add Fenwick Tree

Have you read the Contributing Guidelines on Pull Requests?
YES
Checklist

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

Related Issues or Pull Requests
#7191

Check it @ankitaggarwal23 @bhav09 @HarshCasper


Rename checkExists to checkNameExistsInClass

Fixes #894

To validate this pull request against other sbt modules, please visit this link.


Variables are not saved in an Environment with parenthesis in the name

Steps to reproduce

Open an existing Operation in a Project.
Go to Variables tab.
Click on Add new environment button.
Use a name with parenthesis, e.g. Test (Something).
Click on Save Environment button.
Click on ADD VARIABLE button.
Add a new variable, e.g. test=variable.
Save the request under the existing project.
Select another Environment.
Switch back to Test (Something).

Expected outcome
The Test (Something) environment should have test=variable variable.
Actual outcome
The Test (Something) environment does not have any variables.
Versions
App: <IP_ADDRESS>5-stable
Chrome: 59.0.3071.115
Platform: Windows (10)

Hi,
Thank you for issue report. I can confirm the bug in current version of the application.
The component responsible for this behavior has been fixed, however. New release is scheduled in coming  weeks.

Great, thank you!

This is already fixed. New release coming soon.


cmd/compile: prove bounds for & of positive values

What version of Go are you using (go version)?

$ go version
go version go1.14.2 linux/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env

What did you do?

Compile
package main

func test(foo []byte, i int) {
	_ = foo[63]
	r := i & 63
	_ = foo[r]
}

func main() {}

go build -gcflags="-d=ssa/check_bce/debug=1"
What did you expect to see?
Just the first bounds check for the initial length of the slice
./test.go:4:9: Found IsInBounds

Because prove should be able to deduce that the masked value is bounded by 63 and so is already in bounds.
r := i&m && m >= 0 --> 0 <= r <= m
What did you see instead?
Both accesses require a bounds check.
./test.go:4:9: Found IsInBounds
./test.go:6:9: Found IsInBounds

This is related to #38476
@rasky @josharian @zdjones

I think this is because prove doesn't make inferences inolving binary operations. I have some CLs I've neglected, to which I could hope to someday add inference over bitwise operations (my employer eliminated our 20% time).

Yes, I believe it is.


Feature/fail with descriptive error#issues60

Hello!
If I understand it right we need to check if the package.json is missing or not, like @kirbysayshi said it on the description.
In this case I made a small condition to check this ['undefined', null].indexOf(config) > 0.
Let me know if there is more about this issue than this.

IssueHunt Summary

Referenced issues
This pull request has been submitted to:

#60: Fail with descriptive error if package.json is missing

IssueHunt has been backed by the following sponsors. Become a sponsor

Please spend some more time on the code.

Yeah, I saw the travis build fail, I will working on it. But beside that, did you see something wrong?

Can you change the pull request title to be more descriptive? It should concisely explain what this PR fixes.
Also include Fixes #123 with the issue number of the issue this pull request fixes in the pull request description so the issue is closed when this PR is merged.


jbpm-dashboard Zanata-translation-changes 2016.04.13

@psiroky the jenkins build complains about a totally different module... do yo know what's wrong here?

@dgutierr the PR build takes all upstream repos as well and builds them to make sure the PR uses the latest changes. We can't rely on SNAPSHOT in nexus as that has proven to cause lot of issues with stale content. In this specific case, jbpm repo was broken at the time of running the build. Should be fixed now I guess, I re-triggered the build.

+1


PrismaClientUnknownRequestError on create statement default optional value

Bug description
Hello,
Since version 4.4.0 I have a breaking change in our code. Their is some create statement that do not work if a default time based field is not set. It is now a mandatory to explicitly specify default value within create statement ? It was basically working in 4.3.1 version. However it does work if you explicitly set the time based field (created_at, in my case) with a date value for instance.
It very like or similar to this #14918  or #10497
Base SQL schema is
CREATE TABLE public.values (
    value_id uuid NOT NULL,
    value numeric(13, 5) NOT NULL DEFAULT 0,
    created_at timestamp(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
    CONSTRAINT values_pkey PRIMARY KEY (value_id, created_at)
);

In 4.4.0
  prisma:tryLoadEnv  Environment variables loaded from /Users/iiaku/dev-d/create_repro/.env +0ms
  prisma:tryLoadEnv  Environment variables loaded from /Users/iiaku/dev-d/create_repro/.env +2ms
  prisma:client  dirname /Users/iiaku/dev-d/create_repro/node_modules/.prisma/client +0ms
  prisma:client  relativePath ../../../prisma +0ms
  prisma:client  cwd /Users/iiaku/dev-d/create_repro/prisma +0ms
  prisma:client  clientVersion 4.4.0 +0ms
  prisma:client  clientEngineType library +0ms
  prisma:client:libraryEngine  internalSetup +0ms
  prisma:client:libraryEngine:loader  Searching for Query Engine Library in /Users/iiaku/dev-d/create_repro/node_modules/.prisma/client +0ms
  prisma:client:libraryEngine:loader  loadEngine using /Users/iiaku/dev-d/create_repro/node_modules/.prisma/client/libquery_engine-darwin-arm64.dylib.node +0ms
  prisma:client  Prisma Client call: +13ms
  prisma:client  prisma.values.create({
  data: {
    value_id: '37958000-3275-4f29-a4b4-1d26705de434',
    value: 1000
  }
}) +1ms
  prisma:client  Generated request: +0ms
  prisma:client  mutation {
  createOnevalues(data: {
    value_id: "37958000-3275-4f29-a4b4-1d26705de434"
    value: 1000
  }) {
    value_id
    value
    created_at
  }
}
 +0ms
  prisma:client:libraryEngine  sending request, this.libraryStarted: false +14ms
  prisma:client:libraryEngine  library starting +1ms
prisma:info Starting a postgresql pool with 21 connections.
  prisma:client:libraryEngine  library started +25ms
prisma:query BEGIN
prisma:query INSERT INTO "public"."values" ("value_id","value","created_at") VALUES ($1,$2,$3) RETURNING "public"."values"."value_id", "public"."values"."created_at"
prisma:query SELECT "public"."values"."value_id", "public"."values"."created_at", "public"."values"."value" FROM "public"."values" WHERE ("public"."values"."value_id" = $1 AND "public"."values"."created_at" = $2) LIMIT $3 OFFSET $4
prisma:query ROLLBACK
  prisma:client:request_handler  PrismaClientUnknownRequestError: Query createOnevalues is required to return data, but found no record(s).
    at prismaGraphQLToJSError (/Users/iiaku/dev-d/create_repro/node_modules/@prisma/client/runtime/index.js:20428:10)
    at LibraryEngine.buildQueryError (/Users/iiaku/dev-d/create_repro/node_modules/@prisma/client/runtime/index.js:27330:12)
    at LibraryEngine.request (/Users/iiaku/dev-d/create_repro/node_modules/@prisma/client/runtime/index.js:27263:22)
    at async RequestHandler.request (/Users/iiaku/dev-d/create_repro/node_modules/@prisma/client/runtime/index.js:30816:24)
    at async PrismaClient._request (/Users/iiaku/dev-d/create_repro/node_modules/@prisma/client/runtime/index.js:31812:16) {
  clientVersion: '4.4.0'
} +0ms
  prisma:client:libraryEngine:exitHooks  exit event received: exit +0ms
/Users/iiaku/dev-d/create_repro/node_modules/@prisma/client/runtime/index.js:30855
      throw new PrismaClientUnknownRequestError(message, this.client._clientVersion);
            ^
PrismaClientUnknownRequestError:
Invalid `prisma.values.create()` invocation in
/Users/iiaku/dev-d/create_repro/index.ts:6:23

  3   log: ["error", "info", "query", "warn"],
  4 })
  5 const main = async () => {
→ 6   await prisma.values.create(
Query createOnevalues is required to return data, but found no record(s).
    at RequestHandler.handleRequestError (/Users/iiaku/dev-d/create_repro/node_modules/@prisma/client/runtime/index.js:30855:13)
    at RequestHandler.request (/Users/iiaku/dev-d/create_repro/node_modules/@prisma/client/runtime/index.js:30834:12)
    at async PrismaClient._request (/Users/iiaku/dev-d/create_repro/node_modules/@prisma/client/runtime/index.js:31812:16) {
  clientVersion: '4.4.0'
}

In 4.3.1
  prisma:tryLoadEnv  Environment variables loaded from /Users/iiaku/dev-d/create_repro/.env +0ms
  prisma:tryLoadEnv  Environment variables loaded from /Users/iiaku/dev-d/create_repro/.env +2ms
  prisma:client  dirname /Users/iiaku/dev-d/create_repro/node_modules/.prisma/client +0ms
  prisma:client  relativePath ../../../prisma +0ms
  prisma:client  cwd /Users/iiaku/dev-d/create_repro/prisma +0ms
  prisma:client  clientVersion 4.3.1 +0ms
  prisma:client  clientEngineType library +0ms
  prisma:client:libraryEngine  internalSetup +0ms
  prisma:client:libraryEngine:loader  Searching for Query Engine Library in /Users/iiaku/dev-d/create_repro/node_modules/.prisma/client +0ms
  prisma:client:libraryEngine:loader  loadEngine using /Users/iiaku/dev-d/create_repro/node_modules/.prisma/client/libquery_engine-darwin-arm64.dylib.node +0ms
  prisma:client  Prisma Client call: +242ms
  prisma:client  prisma.values.create({
  data: {
    value_id: '37958000-3275-4f29-a4b4-1d26705de434',
    value: 1000
  }
}) +1ms
  prisma:client  Generated request: +0ms
  prisma:client  mutation {
  createOnevalues(data: {
    value_id: "37958000-3275-4f29-a4b4-1d26705de434"
    value: 1000
  }) {
    value_id
    value
    created_at
  }
}
 +0ms
  prisma:client:libraryEngine  sending request, this.libraryStarted: false +243ms
  prisma:client:libraryEngine  library starting +1ms
prisma:info Starting a postgresql pool with 21 connections.
  prisma:client:libraryEngine  library started +29ms
prisma:query BEGIN
prisma:query INSERT INTO "public"."values" ("value_id","value","created_at") VALUES ($1,$2,$3) RETURNING "public"."values"."value_id", "public"."values"."created_at" /* traceparent=00-00-00-00 */
prisma:query SELECT "public"."values"."value_id", "public"."values"."created_at", "public"."values"."value" FROM "public"."values" WHERE ("public"."values"."value_id" = $1 AND "public"."values"."created_at" = $2) LIMIT $3 OFFSET $4 /* traceparent=00-00-00-00 */
prisma:query COMMIT
  prisma:client:libraryEngine:exitHooks  exit event received: beforeExit +0ms
  prisma:client:libraryEngine:exitHooks  exit event received: exit +0ms

How to reproduce

Clone repro from here: https://github.com/iiAku/prisma-default-field-repro
Follow usage README.md section
Try with both version Prisma Client 4.3.1 and 4.4.0

Expected behavior
We should either have the same behavior with both version OR to know that defaulted field from db should now be explicitly set within data statements.
Prisma information

generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model values {
  value_id   String   @db.Uuid
  value      Decimal  @default(0) @db.Decimal(13, 5)
  created_at DateTime @default(now())

  @@id([value_id, created_at])
}

import { Prisma, PrismaClient } from "@prisma/client"
const prisma = new PrismaClient({
  log: ["error", "info", "query", "warn"],
})
const main = async () => {
  await prisma.values.create({
    data: {
      value_id: "37958000-3275-4f29-a4b4-1d26705de434",
      value: 1000,
      //created_at: new Date(),
    },
  })
}

main()

Environment & setup

OS: macOS Monterey
Database: PostgreSQL
Node.js version: v16.17.0

Prisma Version
4.4.0

thanks for the info @iiAku we will look into this.

I think the issue can be traced to this commit https://github.com/prisma/prisma-engines/commit/fcf3572335e1fd8e0cd0fff9322345dae114f071
In 4.3 we would run this query:

INSERT INTO
"public"."values" ("value_id", "value", "created_at")
VALUES
($1, $2, $3) RETURNING "public"."values"."value_id",
"public"."values"."created_at"
params=["37958000-3275-4f29-a4b4-1d26705de434",1000,"2022-09-28 13:25:31.713 UTC"] result="success" item_type="query" is_query=true duration_ms=41
query=SELECT
"public"."values"."value_id",
"public"."values"."created_at",
"public"."values"."value"
FROM
"public"."values"
WHERE
(
"public"."values"."value_id" = $1
AND "public"."values"."created_at" = $2
)
LIMIT
$3 OFFSET $4
params=["37958000-3275-4f29-a4b4-1d26705de434","2022-09-28 13:25:31.713 UTC",1,0] result="success" item_type="query" is_query=true duration_ms=26

And in 4.4 we run:
INSERT INTO
"public"."values" ("value_id", "value", "created_at")
VALUES
($1, $2, $3) RETURNING "public"."values"."value_id",
"public"."values"."created_at"
params=["37958000-3275-4f29-a4b4-1d26705de434",1000,"2022-09-28 13:16:50.552979 UTC"]

query=SELECT
"public"."values"."value_id",
"public"."values"."created_at",
"public"."values"."value"
FROM
"public"."values"
WHERE
(
"public"."values"."value_id" = $1
AND "public"."values"."created_at" = $2
)
LIMIT
$3 OFFSET $4
params=["37958000-3275-4f29-a4b4-1d26705de434","2022-09-28 13:16:50.552979 UTC",1,0] result="success" item_type="query" is_query=true duration_ms=2

We have a lot more precision in the time .552979 versus the older precision of 3 decimal points. I'm not sure why that causes an issue but it does.

This is exactly what @garrensmith mentioned that cause the bug. Basically my timestamp field has a p = 3 precision.
From https://www.postgresql.org/docs/current/datatype-datetime.html
it says:

time, timestamp, and interval accept an optional precision value p which specifies the number of fractional digits retained in the seconds field. By default, there is no explicit bound on precision. The allowed range of p is from 0 to 6.

So I increased the precision it does work, with:
ALTER TABLE public."values" ALTER COLUMN created_at TYPE timestamp(6) USING created_at::timestamp;

Nevertheless it does not answer why we are getting more precision between version but at least it a fix for the problem.
Thanks for looking into this.


ip match: simplify and speed up the LC Trie implementation

Description:
This change removes the special-case handling for nested lists.
It works by preprocessing the input list of prefixes into an
equivalent list where no prefix is nested under another.
Benchmark test results:
Before:
-------------------------------------------------------------------------
Benchmark                                  Time           CPU Iterations
-------------------------------------------------------------------------
BM_LcTrieLookup                          364 ns        364 ns    1916720
BM_LcTrieLookupWithNestedPrefixes      20546 ns      20545 ns      33952

After:
-------------------------------------------------------------------------
Benchmark                                  Time           CPU Iterations
-------------------------------------------------------------------------
BM_LcTrieLookup                          233 ns        233 ns    3008092
BM_LcTrieLookupWithNestedPrefixes        411 ns        411 ns    1702732

Risk Level: Medium
Testing: unit tests
Docs Changes: N/A
Release Notes: N/A
Fixes #3188
Signed-off-by: Brian Pane<EMAIL_ADDRESS>

@ccaraman PTAL

@ggreenway Can you assign a senior maintainer to do the second pass? Ty!

The error in the CircleCI Mac test run is in a test called IpVersions/SslSocketTest.HalfClose/IPv6, and this PR doesn't change any socket code, so I think that error is unrelated.

@brian-pane will get to this first thing tomorrow, sorry about the delay, want to make sure I have cycles to fully understand this.

@brian-pane Just saw this test failure in a build a few after this was merged. Can you please take a look and see if it's related to this change?
https://circleci.com/gh/envoyproxy/envoy/49127?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
FAIL: @envoy//test/common/network:lc_trie_test (see /build/tmp/_bazel_bazel/400406edc57d332f0b9b805d2b8e33a1/execroot/envoy/bazel-out/k8-dbg/testlogs/external/envoy/test/common/network/lc_trie_test/test.log)

INFO: From Testing @envoy//test/common/network:lc_trie_test:

==================== Test output for @envoy//test/common/network:lc_trie_test:
[==========] Running 14 tests from 1 test case.
[----------] Global test environment set-up.
[----------] 14 tests from LcTrieTest
[ RUN      ] LcTrieTest.IPv4Defaults
[       OK ] LcTrieTest.IPv4Defaults (301 ms)
[ RUN      ] LcTrieTest.RootBranchingFactor
[       OK ] LcTrieTest.RootBranchingFactor (367 ms)
[ RUN      ] LcTrieTest.IPv4AddressSizeBoundaries
[       OK ] LcTrieTest.IPv4AddressSizeBoundaries (389 ms)
[ RUN      ] LcTrieTest.IPv4Boundaries
[       OK ] LcTrieTest.IPv4Boundaries (639 ms)
[ RUN      ] LcTrieTest.IPv6
[       OK ] LcTrieTest.IPv6 (399 ms)
[ RUN      ] LcTrieTest.IPv6AddressSizeBoundaries
[       OK ] LcTrieTest.IPv6AddressSizeBoundaries (364 ms)
[ RUN      ] LcTrieTest.IPv6Boundaries
[       OK ] LcTrieTest.IPv6Boundaries (602 ms)
[ RUN      ] LcTrieTest.CatchAllIPv4Prefix
[       OK ] LcTrieTest.CatchAllIPv4Prefix (658 ms)
[ RUN      ] LcTrieTest.CatchAllIPv6Prefix
[       OK ] LcTrieTest.CatchAllIPv6Prefix (708 ms)
[ RUN      ] LcTrieTest.BothIpvVersions
[       OK ] LcTrieTest.BothIpvVersions (780 ms)
[ RUN      ] LcTrieTest.NestedPrefixes
[       OK ] LcTrieTest.NestedPrefixes (677 ms)
[ RUN      ] LcTrieTest.NestedPrefixesWithCatchAll
[       OK ] LcTrieTest.NestedPrefixesWithCatchAll (671 ms)
[ RUN      ] LcTrieTest.MaximumEntriesException
[       OK ] LcTrieTest.MaximumEntriesException (47299 ms)
[ RUN      ] LcTrieTest.ExceedingAllocatedTrieNodesException
Killed
================================================================================```

@ggreenway thanks for pointing that out I'm checking now, and I'll post an update shortly.

@ggreenway I can't repro the error, but I think I know why it happens:
With this PR, the intermediate binary trie is built before the check for too many trie nodes. In a way, that makes sense: the LC trie has a small address space because it only uses 20-bit "pointers," so it needs to worry about running out of address space; but the binary trie uses native pointers and won't run out of address space.
However, on server or container with a small amount of memory, this test (which tries to build an enormous LC trie) can run out of memory while building the intermediate binary trie.
So I'll make a follow-up PR that moves the too-many-prefixes check before the creation of the intermediate binary trie.

Thanks @brian-pane for addressing this.


Remove cache from service worker

Current domain: https://store-front.getsaleor.com

Seems like it's still an issue. We should clear cache whenever a new version is released or installed.


[FeatureReq] Get rid of this message popping up every 2 weeks.

Is your feature request related to a problem? Please describe.
I'm always frustrated when this annoying popup shows up bimonthly and sometimes not paying attention, I hit the wrong button. I sometimes use extensions from GitHub, I understand it's a safety concern but some users know their way around and don't need excessive babysitting.
Describe the solution you'd like
After showing up the first time (for each sideloaded extension), this pop-up allow you to dismiss it for ever.
Additional context
Provided in attachments.

Hi @khulpu-1, thank you for reporting this. We are looking into this and will let you know as soon as we have an update.

Pop-ups are very annoying.
Chrome tries to minimize unnecessary message interruptions to users(most edge developers are experts), which is great and worth learning.