More flexible lr (3+ delimiters)

Description
I can see this being implemented in two main ways:
The first would be a new function, e.g. delim, that accepts arguments for delimiter(s), a separator, and an array / varargs for content. Example:
$delim("{", "|", (n, m) in ZZ^2, n < m and sum_(i=n)^m 1/i = X})$ \
// This would produce a similar result to the current (though admittedly hacky and awkward):
$lr(lr(\{ (n, m) in ZZ^2 space \|) space n < m and sum_(i=n)^m 1/i = X\} )$

This function could be easily already be implemented in native Typst simply enough, and though it's API is a little bulky, I find it's a great improvement over the alternative with nested lrs.
The latter, which I personally prefer, yet I can see how it might introduce some hurdles in development, would be to either modify lr itself, or create a similar function (perhaps lcr for left, centre, right or lsr for separator) to detect cases such as the above automatically, thereby allowing the simple and intuitive markup of ${(n, m) in ZZ^2 | n < m and sum_(i=n)^m 1/i = X}$ to produce the desirable result with the separator bar scaled together with the delimiting curly braces.
Use Case
Some use cases would be the builder set notation as above, and augmented matrices with a separating bar as well, though I think even enumeration separators such as , and ; would more often then not be more pleasing when scaled together with their surrounding braces. Though it's important to remember these incur a different spacing scheme around them.

I like the idea of a mid() function that you can call in lr to scale something up.

that seems like a nice and simple-to-understand API, but I don't see how it fits into place with the rest of Typst's design; we don't really have any 'context-sensitive' functions like that anywhere else. What does mid do outside of lr? Does it find the closest pair? Is it a special-case compiler error? Maybe it's a no-op? What even is considered 'in' lr? Is at the syntax-tree level or at the level of concrete elements?

mid would simply scale up to the height of the surrounding math "group". lr makes a group, but if you're outside lr the group is the whole equation.

Duplicate of https://github.com/typst/typst/issues/240


idk

when i enter a song (playstate), everything will be like not smooth like 20 fps or 10 but in the fps counter in the corner i have 60 fps but in the other states everything is normal.
i m trying to port this engine to android, so pls can you help me?

likely an issue with your phone, and this engine wasn't really targeted towards android either

likely an issue with your phone, and this engine wasn't really targeted towards android either

no , it s not because i have fnf ported by MaysLastPlay77 and work smoothly

oh, well point being this engine wasn't optimized for android, nor was it targeted towards android users

oh, well point being this engine wasn't optimized for android, nor was it targeted towards android users

ok i will try to optimize

👍🏻

👍🏻

i got just some problems with teascript and hscript files about teascript with class but the hscript i have try the zavodila.hscript who is in the data folder

kid I can't help with android ports because I only have a emulator, and I can't compile android either sorry

kid I can't help with android ports because I only have a emulator, and I can't compile android either sorry

ok about that it can be fixed but about hscript idk about lua functions if imported or not

kid I can't help with android ports because I only have a emulator, and I can't compile android either sorry

Now it s fixed


Fix markdown headers from showing escape characters inside code sections

This is a bandaid, which fixes #19. It makes sure our current (soon legacy?) renderer works correctly for our main example: our README.md.
If you were to dive deeper into this issue (dominictarr is probably aware already), then we'd see that there isn't graceful support for nested code ``` sections, as well as non-javascript hightlighted coded sections. To do this, we'd need a bunch of code or a Lexer(?). It isn't worth the effort since #17 will fix this for new users, once merged.

Once #21 goes through, I can surely just merge this minor fix in myself and publish as semver patch.


test: add tests for state_and_loan_entity

hello @djeck1432 kindly review #260

hello @djeck1432 kindly review

@djeck1432 i did it b4 i pushed sir

you need  not only to run, but fix all these issues @Kaminar-i

@Kaminar-i If you need to explain what you should do text me in DM in telegram djeck_vorobey1

@Kaminar-i any updates?

@djeck1432 review :)


Asaflevi/fix/pypi references

update changelog with new release version and date
update readme files with pypi links

API change check
API changes are not detected in this pull request.


letsencrypt for docker deployment

I used this doc to install four docker nodes in one server. I followed letsencrypt doc for minio to add SSL to my installation but did not find any directions for docker deployments. I am slightly confused about where should I add the certificates.
It might be super useful to update that doc and add steps for docker installs. not everyone is a docker-literate.

Thanks for bringing this up @hadifarnoud we'll add the documentation

@hadifarnoud closing this for now as we don't have cycles to do this.
The process for Docker containers/Swarm remains the same, i.e.

Create / Acquire certificates for each Minio service name (minio1, minio2 .. etc in our docs)
Add the private key and public certificate to the certs directory in --certs-dir (~/.minio/certs by default).
In case of untrusted certs (e.g. self-signed) add trust for these certificates to Minio Server by placing these certificates under --certs-dir/CAs (~/.minio/certs/CAs by default).

You can use Docker Secrets to manage and mount sensitive data like certs and private keys to containers.

I would keep it in "future" milestone though


Cannot Answer Inbound Call

In Google Chrome the inbound call only "rings" on occasions...  but usually it just Answers automatically! In both Chrome and Edge there is no way to "Answer" the call? Outbound calls work great!

Please can you share your code . @6Hat  ?

Is there any event to find out if the user attend the call . I want to start a timer (call duration) when user pick a call.

Try something like this?
  $('#button-answer').on('click', function () {
    conn.accept();
    functionThatStartsATimer()
  });

@forrestedw yeah but this is for incoming calls. I'm talking about outbound calls.

@forrestedw yeah but this is for incoming calls. I'm talking about outbound calls.

device.on('connect', function (conn) {
log('Successfully established call!');
functionThatStartsATimer();
});


how to check if the product was purchased or not

how to check if the product was purchased or not.
Thank you very much

IAPManager.sharedManager.isProductPurchased(productId) - it returns Bool


CLASSIFICATION ALGORITHM IN PYTHON

I wan to work on it.

Hello, Can you please assign this issue to me?
Thanks in advance :)

Scrapping upcoming hackathons and events.
@theanshulcode  I want to work on this issue under hacktober fest.


Support for csswring

Now that we have nice sourcemap support in mincer and grunt-mincer (thank you! thank you! thank you!), it would be great to control csswring through the Gruntfile as well. Specifically I'm looking to use the preserveHacks option and I've also noticed that csswring appends its own sourcemap comment by default. So when using it with grunt-mincer as in the configuration below, 2 comments are generated in every individual CSS file.
    // Run Mincer
    mince: {
      main: {
        options: {
          include: ['assets/css/', 'assets/js/'],
          manifestPath: 'public/assets/manifest.json',
          manifestOptions: {
            compress: false,
            sourceMaps: true,
            embedMappingComments: true
          },
          jsCompressor: 'uglify',
          cssCompressor: 'csswring'
        },
        files: [
          {
            src: ['assets/js/*.js', 'assets/js/*.coffee', 'assets/css/*.css', 'assets/css/*.less']
          }
        ]
      },
    },

The CSS files have 2 comments whereas only the latter one really is correct (the one which is set via mincer and not by csswring automatically):
body { ... }
/*# sourceMappingURL=style.css.map */
/*# sourceMappingURL=style-fb726407f08d769c56898f726719061c.css.map */

closing this as nothing is happening on the mincer side of things to help this along and without configurable csswring options in mincer I can't support it in grunt-mincer.


Trying to use PAM model giving by input processed text

Hi. I'm trying to implement PAM Model by giving as input a processed text (list of lemmatized words, I removed punctuation and stop words).
def topicExtraction(corpus):
    model = tomotopy.PAModel(k=20)
    model.add_doc(corpus)
    model.train()

    print(model.get_topic_words(k, top_n = 20))

But it returns error.
Just one thing: This project looks great.

Thank you for your feedback.
The code you shared means following, doesn't it?
def topicExtraction(corpus):
    model = tomotopy.PAModel(k=20)
    for doc in corpus:
        model.add_doc(doc)
    model.train()
    for k in range(20):
        print(model.get_topic_words(k, top_n = 20))

However, there is a difficulty in reproducing the error. Can you tell me more about what error occurred?

Oh sorry. I gave as Input the entire list. I have to give as input each word in list through a a loop.

Anyway If I try to run the script, it says that the class PAModel doesn’t
accept ‘k’ as parameter (invalid parameter). How to fix it?
Il giorno lun 2 dic 2019 alle 04:45 bab2min<EMAIL_ADDRESS>ha
scritto:

Thank you for your feedback.
The code you shared means following, doesn't it?
def topicExtraction(corpus):
model = tomotopy.PAModel(k=20)
for doc in corpus:
model.add_doc(doc)
model.train()
for k in range(20):
print(model.get_topic_words(k, top_n = 20))
However, there is a difficulty in reproducing the error. Can you tell me
more about what error occurred?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bab2min/tomotopy/issues/22?email_source=notifications&email_token=ANGSWMX6WSESAXV4WODBIRDQWSAHHA5CNFSM4JTNUWN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFSDR6A#issuecomment-560216312,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANGSWMUEJZFIU2TQIC2L5NDQWSAHHANCNFSM4JTNUWNQ
.

Oh, I missed one of the important things in the above answer. PAModel doesn't accept k, but k1, k2. You can see the detail information at documentation. (https://bab2min.github.io/tomotopy/v0.4.2/en/#tomotopy.PAModel)
Please try following code:
def topicExtraction(corpus):
    model = tomotopy.PAModel(k1=5, k2=50)
    for doc in corpus:
        model.add_doc(doc)
    model.train()
    for k in range(20):
        print(model.get_topic_words(k, top_n=20))

It works greatly. Thank you.
Il giorno mar 3 dic 2019 alle 02:12 bab2min<EMAIL_ADDRESS>ha
scritto:

Oh, I missed one of the important things in the above answer. PAModel
doesn't accept k, but k1, k2. You can see the detail information at
documentation. (
https://bab2min.github.io/tomotopy/v0.4.2/en/#tomotopy.PAModel)
Please try following code:
def topicExtraction(corpus):
model = tomotopy.PAModel(k1=5, k2=50)
for doc in corpus:
model.add_doc(doc)
model.train()
for k in range(20):
print(model.get_topic_words(k, top_n=20))
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bab2min/tomotopy/issues/22?email_source=notifications&email_token=ANGSWMX6R23IYKPZHZNSMW3QWWW6PA5CNFSM4JTNUWN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFXXIOQ#issuecomment-560952378,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANGSWMTE2P5EQQ475OYFUITQWWW6PANCNFSM4JTNUWNQ
.


[stable/kube-state-metrics] add pod affinity

What this PR does / why we need it:
Ability to define affinity for pods added to the kube-state-metrics chart.
Which issue this PR fixes

fixes #12818

Special notes for your reviewer:
@fiunchinho Just a quick addition to the chart.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/assign @lachie83

/lgtm

@lachie83 @prydonius Any chance of getting this accepted?

@tongpu Can you rebase this PR ?

@tariq1890 Done.

@davidkarlsen PTAL at this PR.

/ok-to-test

/approve
/lgtm


Address Particles HDR sample blue trail

The following blue trail is a pet peeve of me in the Particles (HDR) sample:

I can reproduce on macOS (Apple M1 Pro device with Chrome and Safari), but not on Android.
Could this be a Metal driver issue or something else? FYI @mwyrzykowski

I have also noticed this and it seems to occur in different locations in Chrome (left, trail in far top-left) compared to Safari (right, trail in middle top-left)

I have not debugged the sample first, so I would start there before thinking it is a metal bug. The issue is present on AMD Intel Mac as well, so if it is a Metal issue it is not hardware specific.

that looks better:

It is an issue in the sample, I don't reproduce when I disable fastMath (options.fastMathEnabled = NO;) in WebKit
The WGSL specification is supposed to allow for variances due to having fast math enabled, so likely these functions:
fn init_rand(invocation_id : u32, seed : vec4f) {
  rand_seed = seed.xz;
  rand_seed = fract(rand_seed * cos(35.456+f32(invocation_id) * seed.yw));
  rand_seed = fract(rand_seed * cos(41.235+f32(invocation_id) * seed.xw));
}

fn rand() -> f32 {
  rand_seed.x = fract(cos(dot(rand_seed, vec2f(23.14077926,<PHONE_NUMBER>5))) * 136.8168);
  rand_seed.y = fract(cos(dot(rand_seed, vec2f(54.47856553,<PHONE_NUMBER>6))) * 534.7645);
  return rand_seed.y;
}

are making assumptions about numerical accuracy which are not guaranteed by WGSL.

There's at least one other issue. The code is using workgroups of size 64 and then dispatching Math.ceil(numParticles / 64) workgroups. It's using 50000 particles. That means it's calculating and writing to 50048 particles, 48 of which are out of bounds. Out of bounds writes could corruprt other particles. That they aren't is just luck.
The sample should either round up/down the number of particles to a multiple of 64, or it should check in the shader and not process out of bounds particles.

Indeed, I think both Chrome and Safari are clamping, but that is not the only behavior allowed by the specification

I can confirm with https://chromium-review.googlesource.com/c/chromium/src/+/5920336 that setting strict math removes the blue trail. Thank you!
I'm not sure yet though how to fix the root issue. Setting numParticles to 50048 alone was not enough by itself.

sorry, I didn't mean to suggest the out-of-bounds writting was the source of the problem. I only meant to point out it is yet another problem that may show a different issue on some implementations

So not technically fast math in WebKit for the following WGSL:
fn init_rand(invocation_id : u32, seed : vec4f) {
  rand_seed = seed.xz;
  rand_seed = fract(rand_seed * cos(35.456+f32(invocation_id) * seed.yw));
  rand_seed = fract(rand_seed * cos(41.235+f32(invocation_id) * seed.xw));
}

we generate:
void function0(unsigned parameter0, vec<float, 4> parameter1, thread vec<float, 2>& global0)
{
    global0 = parameter1.xz;
    global0 = fract((global0 * cos((35.45600128173828 + (float(parameter0) * parameter1.yw)))));
    global0 = fract((global0 * cos((41.23500061035156 + (float(parameter0) * parameter1.xw)))));
}

replacing that with (note precise:: in front of the call to cos):
void function0(unsigned parameter0, vec<float, 4> parameter1, thread vec<float, 2>& global0)
{
    global0 = parameter1.xz;
    global0 = fract((global0 * precise::cos((35.45600128173828 + (float(parameter0) * parameter1.yw)))));
    global0 = fract((global0 * precise::cos((41.23500061035156 + (float(parameter0) * parameter1.xw)))));
}

corrects the issue @beaufortfrancois

@beaufortfrancois it looks like the value being passed to cos call is too large, I didn't debug the actual values but dividing parameter0 by 100 seems to resolve the issue:
void function0(unsigned parameter0, vec<float, 4> parameter1, thread vec<float, 2>& global0)
{
    global0 = parameter1.xz;
    global0 = fract((global0 * fast::cos((35.45600128173828 + (float(parameter0)*0.01f * float2(parameter1.y, parameter1.w))))));
    global0 = fract((global0 * fast::cos((41.23500061035156 + (float(parameter0)*0.01f * float2(parameter1.x, parameter1.w))))));
}

I confirm that the following code hides the blue trail. I wish I understood why it's happening... https://gpuweb.github.io/gpuweb/wgsl/#cos-builtin doesn't help ;(
 fn init_rand(invocation_id : u32, seed : vec4f) {
   rand_seed = seed.xz;
-  rand_seed = fract(rand_seed * cos(35.456+f32(invocation_id) * seed.yw));
+  rand_seed = fract(rand_seed * cos(35.456+f32(invocation_id) * 0.01f * seed.yw));
-  rand_seed = fract(rand_seed * cos(41.235+f32(invocation_id) * seed.xw));
+  rand_seed = fract(rand_seed * cos(41.235+f32(invocation_id) * 0.01f * seed.xw));
 }

Seems maybe we need to figure out the restriction on cos or trig functions in general since the WGSL documentation claiming one can pass:

Scalar domain | Interval (−∞, +∞)

seems a bit optimistic if we are to allow fast math functions

@alan-baker shared offline that the domain is the set of inputs that don't result in a NaN, not the set of inputs that have an accurate result. It would be nice if WGSL could call out the accuracy limitations.

@alan-baker shared offline that the domain is the set of inputs that don't result in a NaN, not the set of inputs that have an accurate result. It would be nice if WGSL could call out the accuracy limitations.

There's a section for accuracy, amidst all the details of floating point.  It's a complicated topic in part because of "inherited from" formulas, and various loose rules for subnormals, rounding, and the need to take the worst observed across devices/specs.
https://gpuweb.github.io/gpuweb/wgsl/#concrete-float-accuracy

Sounds like modifying the sample is reasonable then and everything is compliant within the specification 👍

Thanks! I've opened https://github.com/webgpu/webgpu-samples/pull/469


Bug: problem of importing resources but cannot get necessary information to use

What happened?
For example I have a workspace with a module mysql has imported resources like this:
modules:
    mysql:
        path: oci://ghcr.io/viettelcloud/mysql
        version: 0.2.0
        configs:
            default:
                category: basic
                cloud: viettelcloud
                databaseName: quickstart
                importedResources:
                    hashicorp:viettelcloud:viettelcloud_db_instance:test-mysql: test-mysql

Then, in stack project, I have main.k file like this one to import the existing MySQL instance name test-mysql.
quickstart: ac.AppConfiguration {
    workload: service.Service {
        containers: {
            quickstart: c.Container {
                image: "kusionstack/kusion-quickstart:latest"
                env: {
                    "DB_HOST": "$(KUSION_DB_HOST_QUICKSTART_DEFAULT_QUICKSTART_MYSQL)"
                    "DB_USERNAME": "$(KUSION_DB_USERNAME_QUICKSTART_DEFAULT_QUICKSTART_MYSQL)"
                    "DB_PASSWORD": "$(KUSION_DB_PASSWORD_QUICKSTART_DEFAULT_QUICKSTART_MYSQL)"
                }
            }
        }
    }
    accessories: {
        "network": n.Network {
            ports: [
                n.Port {
                    port: 8080
                }
            ]
        }
        "mysql": mysql.MySQL {
           type: "cloud"
           version: "5.7.30"
           databaseName: "test-mysql"
        }
    }
}

With the project above, kusion will import the MySQL database instance test-mysql to stack. But there is one problem the target of importing the database is to get the credential information for the application to connect but after importing the database test-mysql, there is no necessary credential information.
What did you expect to happen?
The goal of the import resource feature is to acquire the necessary information for the application's use. There may be alternative methods to store database credentials or similar types of information from other resources.
How can we reproduce it (as minimally and precisely as possible)?
When creating a shareable resource, it may be necessary to save important information that the application can use in a secret manager.
Anything else we need to know?
It appears that kusion generate does not yet support retrieving secrets from the secret manager.
Kusion version

$ kusion version
releaseVersion: 0.12.1+f2ee4522
gitInfo:
    latestTag: v0.12.1
    commit: f2ee4522600ee35227bedcd13a28c9fb1ce6bd9a
    treeState: dirty
buildInfo:
    goVersion: go1.22.3
    GOOS: linux
    GOARCH: amd64
    numCPU: 8
    compiler: gc
    buildTime: "2024-08-16 02:11:56"

OS version

# On Linux:
$ cat /etc/os-release
PRETTY_NAME="Ubuntu 24.04 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo
$ uname -a
Linux buddy 6.8.0-40-generic #40-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul  5 10:34:03 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

cc @liu-hm19 @SparkYuan @ffforest

@hoangndst Hi, I've reproduced the problem locally. It seems that Kusion indeed does not import certain sensitive information such as database password when importing some existing cloud resources using terraform import.
I think this should be a feature of the underlying API called by the Terraform provider when importing the resources, more details may find in this issue. Therefore, for sensitive information like database passwords that cannot be obtained from the state file with terraform import, users may need to provide it themselves.
For example, module generators may create a random_password resource to record the password, and for the mysql module provided by KusionStack community officially:
# example_workspace.yaml
modules:
    mysql:
      path: oci://ghcr.io/kusionstack/mysql
      version: 0.2.0
      configs:
          default:
            cloud: alicloud
            size: 20
            instanceType: mysql.n2.serverless.1c
            category: serverless_basic
            privateRouting: false
            subnetID: vsw-2ze*******
            databaseName: "wordpress-demo"
            importedResources:
              "aliyun:alicloud:alicloud_rds_account:wordpress-demo": "rm-2ze*******"
              "aliyun:alicloud:alicloud_db_instance:wordpress-demo": "rm-2ze*******"
              "aliyun:alicloud:alicloud_db_connection:wordpress-demo": "rm-2ze*******"
              "hashicorp:random:random_password:wordpress-demo-mysql": "rds-account-password" # The RDS account password obtained from cloud console or recreated.
    network:
        path: oci://ghcr.io/kusionstack/network
        version: 0.2.0
        configs:
            default: {}

# Ignore the randomly changed field in random_password to avoid recreate a new one.
kusion apply --ignore-fields "bcrypt_hash"

And I think it should also be feasible to obtain the credentials through Secrets Manager. We can further explore this scenario and provide a demo for other users. cc @ffforest

I agree with your solution. Besides creating the database and random password, the credentials should be saved to the secret manager. We should generate the credential in another way and save it to the secret manager not just using hashicorp:random for a random password. Or create a resource random_password for the first time and save it to the secret manager so other stacks in the workspace can reuse the database and get the credentials from the secret.

I think the solution provided by @hoangndst is reasonable. Maybe we can try to update the mysql module and add a configuration item in the Workspace configs as a switch to decide whether to use Secrets Manager to store the credentials. cc @ffforest

After the discussion with @ffforest, we believe that managing the credentials with Secrets Manager is a feasible solution. And we can add a configuration item in the Workspace configs of the mysql module to identify whether to use Secrets Manager to store the credentials.
If convenient, @hoangndst can add the support for Viettel Cloud database in the mysql module and implement the relevant interface for storing credentials in Secrets Manager. And I will then implement the support for AWS and Alicloud. 😊


Feature Request: Support Windows

Hi
Today, Whatsapp forced user to use Microsoft store version which is quite bad for corporate environment (Microsoft store is not allowed) and the UX is lacking. Is it possible to support Windows?

I will try to build the app in windows.
Thanks.

+1

Would love to see this

Hi, I've been looking for a replacement for the official desktop app that WhatsApp made available for Windows because of its issues with automatic theme switches and scrolling getting stuck.
Did you manage to build the app for Windows and if yes, could you make binaries available on the GitHub release? Alternatively, could you provide build instructions for Windows?
Much appreciated!


Facebook and G+ links broken.

Actual Behavior
FB and G+ links on the login page ( http://open-event-dev.herokuapp.com/login/ ) are broken.
Expected Behavior
When click those links it must be open correct way to login.
See in this link. Example for expected behavior - https://eventyay.com/login/
G+ link must be like this -
https://accounts.google.com/o/oauth2/auth?response_type=code&client_id=1033793180170-3hce8s4mcef7s878ojp4tbm9ijfh207i.apps.googleusercontent.com&redirect_uri=https%3A%2F%2Feventyay.com%2FgCallback&scope=profile+email&state=6naN4K21FWqHPbLpfF5DuVX40cXP17&access_type=offline
FB link must be like this -
https://www.facebook.com/dialog/oauth?response_type=code&client_id=203571866755829&redirect_uri=https%3A%2F%2Feventyay.com%2FfCallback&scope=public_profile+email&state=cI3tT3UWNZ4HIOQj93yWK1bcRJ9tt0&access_type=offline
Steps to reproduce it
Add correct links.
Screen-shots of the issue
Login page

Facebook link is broken.

G+ link is broken

Would you like to work on the issue?
I am busy, Please work on this!

The link for google + is working perfectly on the main site however the one for facebook is not.
@STEdirisuriya for anyone knowing the basics of authentication, it would be obvious that neither of them would work for herokuapp or any other similar deployment (unless the specific call back urls are set for it at console developers google).
The  problem needs to be addressed for facebook though.

http://open-event-dev.herokuapp.com/login/
no both are not working see this @shikhar-scs

Anyone work on this issue!

You can go ahead @STEdirisuriya  👍

I guess the problem is with some incorrect routing. I'd start working on it right away .

@STEdirisuriya can you please provide me the source code for https://eventyay.com/login/ and http://open-event-dev.herokuapp.com/login/ please. I need to work on them to fix this.


create_docker_sysext.sh: no containerd-shim in v23 and higher

This change fixes a bug with ONLY_DOCKER builds in create_docker_sysext.sh. Docker binary releases version 23 and above do not ship /usr/bin/containerd-shim anymore, leading to the following error when building a "docker only" sysext w/o containerd:
rm: cannot remove 'docker/usr/bin/containerd-shim': No such file or directory

This PR handles versions below major release 23 separately and only deletes containerd-shim for these versions.
Tested with docker releases 20.10.9, 23.0.0, and 24.0.6.

I'm only wondering why we weren't using rm -f in the first place.

My first approach was to switch to -f but then I thought that we deliberately want this to break if docker ships different sets of binaries. Not sure :shrug:


Editor crashes after loading GDNative

Description
I've used example from https://github.com/ShadowApex/godot-go/tree/master/examples/gdnative/SimpleDemo but this seems to not work.
Ouput from console when running game looks like:
OpenGL ES 2.0 Renderer: GeForce GTX 860M/PCIe/SSE2
ERROR: _get_socket_error: Socket error: 10054
   At: drivers/unix/net_socket_posix.cpp:190
WARNING: main.nativeScriptInit: Initializing nativescript from Go!
     At: C:/path/to/main.go:20
WARNING: main.nativeScriptInit: Registering SIMPLE class...
     At: C:/path/to/main.go:39
WARNING: main.nativeScriptInit: Registering SIMPLE method...
     At: C:/path/to/main.go:48
Cetn e ipels.
Dsryn ipels ihI:x00808.

I suppose, last two lines are from main.go.
gdnative.Log.Println("Creating new SimpleClass...") and gdnative.Log.Println("Destroying SimpleClass with ID:", userData, "..."). If I change gdnative.Log.Println to gdnative.Log.Warning this logs seems to be working but editor still crashes.
Details

Go version
go version go1.12 windows/amd64

Godot version
v3.1.beta8.official

Godot-Go version/commit hash
1746202a2001f65ff7eb635b8cd7fc2a6ea64ca2

OS
windows10 64bit

Looks like creating simple.gdns from Godot's interface works fine.
[gd_resource type="NativeScript" load_steps=2 format=2]

[sub_resource type="GDNativeLibrary" id=1]
config_file = Object(ConfigFile,"script":null)

entry/Windows.64 = "res://native-plugins/gameanalytics/bin/game-analytics.dll"
dependency/Windows.64 = [  ]

[resource]
class_name = "SIMPLE"
library = SubResource( 1 )
script_class_name = "SIMPLE"

But this solution does not fix weird logs.

even the binding generator dies at some error. Its the previous issue to this one. So yeah, i think its broken.. I could fix it, but i don't have much free time.

I started a new godot-go project here (https://github.com/godot-go/godot-go) because this project has gone dormant. my project properly integrates into the editor. custom nativescript properties will register and can be modified on the editor panel.


Connect button broken DeviceConnect.js:31

When i try to connect to ssh or VNC using open-balena-admin i get the vollowing error in the javascript console.
Chrome:
DeviceConnect.js:31
Uncaught TypeError: Cannot read properties of undefined (reading 'generateKey')
    at genRsaKeys (DeviceConnect.js:31:37)
    at handleSubmit (DeviceConnect.js:75:9)
    at Object.submit (final-form.es.js:1437:1)
    at handleSubmit (react-final-form.es.js:268:1)
    at HTMLUnknownElement.callCallback (react-dom.development.js:3945:1)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:3994:1)
    at invokeGuardedCallback (react-dom.development.js:4056:1)
    at invokeGuardedCallbackAndCatchFirstError (react-dom.development.js:4070:1)
    at executeDispatch (react-dom.development.js:8243:1)
    at processDispatchQueueItemsInOrder (react-dom.development.js:8275:1)

Firefox:
DeviceConnect.js:31:8
Uncaught TypeError: window.crypto.subtle is undefined

After running the admin, remote and posgrest behind nginxproxy i can connect but get now get the
Error:
Unable to connect to device.
this is with both ssh and vnc.
in the vnc log on the client i get the following:
[2023-05-15T07:15:45.158Z] 15/05/2023 07:15:45 Got connection from client <IP_ADDRESS>
[2023-05-15T07:15:45.160Z] 15/05/2023 07:15:45 0 other clients
[2023-05-15T07:15:45.160Z] 15/05/2023 07:15:45 webSocketsHandshake: unknown connection error
[2023-05-15T07:15:45.160Z] 15/05/2023 07:15:45 Client <IP_ADDRESS> gone
[2023-05-15T07:15:45.164Z] 15/05/2023 07:15:45 Statistics events Transmit/ RawEquiv ( saved)
[2023-05-15T07:15:45.165Z] 15/05/2023 07:15:45 TOTALS : 0 | 0/ 0 ( 0.0%)
[2023-05-15T07:15:45.166Z] 15/05/2023 07:15:45 Statistics events Received/ RawEquiv ( saved)
[2023-05-15T07:15:45.166Z] 15/05/2023 07:15:45 TOTALS : 0 | 0/ 0 ( 0.0%)

After running all openbalena-admin web servers behind a ssl proxy the problem was solved


Login via github fails

the sign-in popup appears, and lets you log into github if you are already logged in, otherwise it closes without asking to authorise playground.

My apologies. works now in safari.
Must have been a local browser issue.
Note to self - try clear all browser settings if recurs.
RacketScript Playground Program; view at: http://play.racketscript.org/#gist/2ef0bae9c4b44483a79a5d7c7be65b91


Update to container-vm-v20150505 (Also updates GCE to Docker 1.6)

Ran 38 of 43 Specs in 1317.103 seconds
SUCCESS! -- 38 Passed | 0 Failed | 1 Pending | 4 Skipped I0505 16:54:33.660644   18816 driver.go:96] All tests pass

cc @dchen1107

Lgtm

LGTM.


Added new Accessibe script to load delayed

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #30
Test URLs:

Before: https://main--danaher-ls-aem--hlxsites.hlx.page/
After: https://feat-30-accessible--danaher-ls-aem--hlxsites.hlx.page

@rgravitvl  and @mhaack - I have now updated, solved the conflict and also added it to be ignored on the lint checks.  Please can you review and provide honest feedback


Add get_url() helpers to Study and Assay models

This would eliminate the need for e.g. template tag helpers, remove repetition and simplify templates.
Tasks

implement helpers
Replace and remove get_zone_samples_url() and other possibly existing implementations
Add/update tests

Done.


Task 2

How is task two coming up? @JustinJaniszewski

I am supposed to do task 1. Unless I missed an issue about it or something? @WildJimmy is doing Task 2

@uarif @JustinJaniszewski Yep, I am doing/did task 2 (root finding). Still haven't worked out that final error with tanh though so I'm looking at that


Syntax error in INSERT INTO statement

Get a 'Syntax error in INSERT INTO statement' on attempt to insert data into Access database table with an auto increment ID column and specifying which columns to insert.
The insert is successful if no columns are specified and all columns are given a value.
This is Access 2007 compatible file running on Windows 7.

Sorry, can you give an example?

@grayfella - One thing you can do is check the names of the columns you wish to insert the data in. Some words are reserved words and you cannot use them in your query. If you want to use them anyway, you can probably enclose them with square brackets like [column].
Hope this helps :smile:


Fix default values of selected/selectedGlyphImage

See https://github.com/Nicolapps/mapkit-react/pull/38#discussion_r1342194554

Also I personally feel, from a MapKit JS perspective, I would rather want the implementation to not pass those props which are not defined, than passing them with the default values. Not sure if Apple thinks like I do, though, it could even at some point prevent some errors. Talking about the selected feature for example. Let's say we haven't defined the prop, then the user selects the annotation and then we pass in a false. Would the API be even able to get the changed value, as internally selected is already true, though the prop passed (default value = false) is false and the new passed value also is false. Please correct me if this does not make sense what I am thinking here.

Could we possibly also discuss this here? So basically what I am saying is that it might be better to pass undefined whenever a prop is not set and not pass any prop with the value undefined and just those with a real value, which might be equal to the default value. Please let me know what you think about it or if this does not make any sense.

Sorry, I didn’t see your update when merging your PR. I see the point in your suggestion, but I think that it might cause an issue.
When using boolean attributes that default to false in JSX, it is common to be able to set the value to false by omitting the attribute (<…>) and set it to true by including it (<… selected>). With your suggestion, the component would behave unexpectedly when used like this:
function MyMarker({ isCurrent }) {
  return isCurrent
    ? (
      // In this case, the marker should never be selected
      <Marker
        // (…a lot of styling properties specific to what the user needs in this case)
        enabled={false}
      />
    ) : (
      // In this case, the marker should always be selected
      <Marker
        // (…a lot of styling properties specific to what the user needs in this case)
        enabled={false}
        selected
      />
    );
}

I’m open to making a breaking change if it improves the developer experience, but I’m worried by it behaving strangely in a situation like this one.

Sorry, I didn’t see your update when merging your PR. I see the point in your suggestion, but I think that it might cause an issue.
When using boolean attributes that default to false in JSX, it is common to be able to set the value to false by omitting the attribute (<…>) and set it to true by including it (<… selected>). With your suggestion, the component would behave unexpectedly when used like this:
function MyMarker({ isCurrent }) {
  return isCurrent
    ? (
      // In this case, the marker should never be selected
      <Marker
        // (…a lot of styling properties specific to what the user needs in this case)
        enabled={false}
      />
    ) : (
      // In this case, the marker should always be selected
      <Marker
        // (…a lot of styling properties specific to what the user needs in this case)
        enabled={false}
        selected
      />
    );
}

I’m open to making a breaking change if it improves the developer experience, but I’m worried by it behaving strangely in a situation like this one.

Thank you so much for your feedback!
And indeed, that is a valid point. Although I personally never use this syntax. However React is taking care of this already as far as I know and does not pass a undefined, but a true instead. If you would however use
const [selected, setSelected] = useState();

...
return (
<Marker selected={selected} />
)

the value would be undefined. And could be set to false using setSelected(false).
I know this is quite a edgy case and quite a made up problem, though rather a general question if this could improve the library maybe.

However React is taking care of this already as far as I know and does not pass a undefined, but a true instead.

React will pass true when the attribute is set, but undefined (and not false) when omitting it. My point was that in some cases, people could expect omitting the attribute to behave the same way as setting it to false, while the proposed change breaks this property.
I tested how React behaves with checkboxes, because it is a similar case. It turns out that when changing checked from true to undefined, React deselects the checkbox, instead of keeping its current state.
For this reason, I think that it is better to keep the current behavior for selected. As you pointed out, the cases where the attribute is always controlled and the case where it is always uncontrolled are already handled well. Thank you a lot for your proposal and research!

However React is taking care of this already as far as I know and does not pass a undefined, but a true instead.

React will pass true when the attribute is set, but undefined (and not false) when omitting it. My point was that in some cases, people could expect omitting the attribute to behave the same way as setting it to false, while the proposed change breaks this property.
I tested how React behaves with checkboxes, because it is a similar case. It turns out that when changing checked from true to undefined, React deselects the checkbox, instead of keeping its current state.
For this reason, I think that it is better to keep the current behavior for selected. As you pointed out, the cases where the attribute is always controlled and the case where it is always uncontrolled are already handled well. Thank you a lot for your proposal and research!

Thank you so much for your feedback!
I would like to note two things as a side note to keep in mind. Omitting a value and setting it to false, doesn't behave the same way if set on initial render. While a <input checked={false} /> is a controlled component, <input/> is not. However, yes if you make a controlled component uncontrolled, the behavior you described is indeed like this. Not sure if you wanted to say this already, but just wanted to point out.
Also React does warn when making an uncontrolled value controlled. Not sure if we should consider implementing a similar warning maybe at some point.

Warning: A component is changing an uncontrolled input to be controlled. This is likely caused by the value changing from undefined to a defined value, which should not happen. Decide between using a controlled or uncontrolled input element for the lifetime of the component. More info: https://reactjs.org/link/controlled-components

Even more precise, React is behaving the exact same way on the inputs as our library currently does. It does actually not set it to false but even resets it to it's defaultvalue. Not saying that I like this behavior, but well I can fully agree on your perspective of staying as close to the React behavior as possible.


Update github-beta to 1.0.9-beta1-b3af5043

After making all changes to the cask:

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

Closing in favour of https://github.com/caskroom/homebrew-versions/pull/4792


Ecto.QueryError when using parent_as/1 in select

Environment
Elixir:
$ elixir --version
Erlang/OTP 23 [erts-11.1.6] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [hipe]

Elixir 1.10.4 (compiled with Erlang/OTP 21)

PostgreSQL:
postgres=# select version();
                                   version
------------------------------------------------------------------------------
 PostgreSQL 13.1 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 10.2.0, 64-bit
(1 row)

Deps:
ecto: v3.5.6
ecto_sql: v3.5.4
postgrex: 0.15.8
Operating System: Arch Linux
$ uname -a
Linux yunmikun2 5.10.11-arch1-1 #1 SMP PREEMPT Wed, 27 Jan 2021 13:53:16 +0000 x86_64 GNU/Linux

Current behaviour
First, we build a subquery that uses parent_as/1 under the :select
key in the Ecto.Query.from/2 macro:
iex(1)> sq = from percent in "percents", where: percent.id == parent_as(:value).id, select: %{value: parent_as(:value).value * percent.percent}
#Ecto.Query<from p0 in "percents", where: p0.id == parent_as(:value).id,
 select: %{value: parent_as(:value).value * p0.percent}>

Then we join this as a subquery with lateral join:
iex(2)> q = from value in "values", as: :value, inner_lateral_join: computed in subquery(sq), select: %{id: value.id, computed: computed.value}
#Ecto.Query<from v0 in "values", as: :value,
 join_lateral: p1 in subquery(from p0 in "percents",
  where: p0.id == parent_as(:value).id,
  select: %{value: parent_as(:value).value * p0.percent}),
 on: true, select: %{id: v0.id, computed: p1.value}>

As far, everything goes normally, but when we try to execute such a
query (or simply translate it into a SQL string), we get an error:
iex(3)> MyApp.Repo.to_sql(:all, q)
** (Ecto.SubQueryError) the following exception happened when compiling a subquery.

    ** (Ecto.QueryError) `parent_as(:value)` can only be used in subqueries in query:

    from p0 in "percents",
      where: p0.id == parent_as(:value).id,
      select: %{value: parent_as(:value).value * p0.percent}

The subquery originated from the following query:

from v0 in "values",
  as: :value,
  join_lateral: p1 in subquery(from p0 in "percents",
  where: p0.id == parent_as(:value).id,
  select: %{value: parent_as(:value).value * p0.percent}),
  on: true,
  select: %{id: v0.id, computed: p1.value}

    (ecto 3.5.6) lib/ecto/adapter/queryable.ex:110: Ecto.Adapter.Queryable.prepare_query/3
    (ecto_sql 3.5.4) lib/ecto/adapters/sql.ex:235: Ecto.Adapters.SQL.to_sql/3

Expected behavior
Regardless of usefullness of this code in real life, one of the
following options should be chosen (I guess):

consider this a bug as there is an equivalent SQL expression
which is valid in SQL;
we mark in the docs that usage of parent_as/1 is dissallowed in
select clause.

Etc
Forementioned SQL expression that's valid:
SELECT v.id,
       c."value"
  FROM "values" v
         JOIN LATERAL (
           SELECT v."value" * p.percent AS "value"
             FROM percents p WHERE p.id = v.id
         ) c
         ON true;

Way to check and test it works if you're lazy:
create database test;
\c test;
create table values (id bigserial primary key, value integer);
create table percents (id bigserial primary key, percent integer);
insert into values (value) values (1), (2), (3);
insert into percents (percent) values (1), (2), (3);

Correct. I have recently commit something that makes it clear this is not currently supported: https://github.com/elixir-ecto/ecto/commit/8d7625e257d6f7b05b6fe1fe6db05c2692e38e31 Thanks!

Correct. I have recently commit something that makes it clear this is not currently supported: https://github.com/elixir-ecto/ecto/commit/8d7625e257d6f7b05b6fe1fe6db05c2692e38e31 Thanks!

However, it works if you are referring to from and not another join, if you are using master: https://github.com/elixir-ecto/ecto/commit/ce90e4eb160a668404bb6921724481367cff8f64

However, it works if you are referring to from and not another join, if you are using master: https://github.com/elixir-ecto/ecto/commit/ce90e4eb160a668404bb6921724481367cff8f64

it works if you are referring to from
Nice. Hope we'll get support for joins in the future too. Thanks!

it works if you are referring to from
Nice. Hope we'll get support for joins in the future too. Thanks!


fixed for insert without columns.

Fixes #3234

resumbit my PR and associate to https://github.com/apache/incubator-shardingsphere/pull/3295.  (recreate the branch to resolve the conflict)

Pull Request Test Coverage Report for Build 686

33 of 35 (94.29%)  changed or added relevant lines in 6 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.02%) to 67.88%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sharding-core/sharding-core-rewrite/src/main/java/org/apache/shardingsphere/core/rewrite/feature/encrypt/token/generator/impl/EncryptForInsertColumnsTokenGenerator.java
4
6
66.67%

Files with Coverage Reduction
New Missed Lines
%

sharding-core/sharding-core-rewrite/src/main/java/org/apache/shardingsphere/core/rewrite/parameter/builder/impl/StandardParameterBuilder.java
1
94.12%

Totals

Change from base Build 489:
0.02%

Covered Lines:
11317

Relevant Lines:
16672

💛  - Coveralls


Add input_data to Event::Called and Event::Instantiated

This PR add input_data to Event::Called and Event::Instantiated, close #13895

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-each-crate
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2683396

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2683382

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2683381

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2829405

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2829406

I don't think this PR addresses the point raised by @athei  here

The tricky part is that we don't limit the maximum amount of input data right now. So order for this to be safe we need to charge a weight for every contract interaction that is based on the size of the input data. This weight will probably be larger that what benchmarks indicate because of the memory allocation implications of emitting big events. Otherwise this could probably be abused to provoke an OOM.

See also this thread on storing unbounded data input https://substrate.stackexchange.com/a/4455


In Chapter 12 Step 6, redirect call from Server Action points to the wrong path

In Chapter 12's Revalidate and Redirect, it says that the redirect call should be to redirect('dashboard/invoices'), however when I run it locally it points to the wrong path.
Server Action code (app/lib/actions.ts):
'use server';

import { z } from 'zod';
import { sql } from '@vercel/postgres';
import { revalidatePath } from 'next/cache';
import { redirect } from 'next/navigation';

const FormSchema = z.object({
  id: z.string(),
  customerId: z.string(),
  amount: z.coerce.number(),
  status: z.enum(['pending', 'paid']),
  date: z.string(),
})

const CreateInvoice = FormSchema.omit({ id: true, date: true });

export async function createInvoice(formData: FormData) {
  const { customerId, amount, status } = CreateInvoice.parse({
    customerId: formData.get('customerId'),
    amount: formData.get('amount'),
    status: formData.get('status'),
  });

  const amountInCents = amount * 100;
  const date = new Date().toISOString().split('T')[0];

  await sql`
    INSERT INTO invoices (customer_id, amount, status, date)
    VALUES (${customerId}, ${amountInCents}, ${status}, ${date})
  `;

  revalidatePath('/dashboard/invoices');
  redirect('dashboard/invoices');
}

This action is being invoked from a button in localhost:3000/dashboard/invoices/create and when it is invoked, it attempts to redirect to localhost:3000/dashboard/invoices/dashboard/invoices which doesn't exist.
Does this mean that redirect calls from Server Actions use relative paths based off of where they are invoked?

Ah! I missed one / here on the redirect call, my bad!


Mingjie2 dpex

Please add a PR description

@mingjie-intel the CI run shows some of the runs errored out. The job is not catching these as they are only reported as warnings.

Hi Dipto, can you please be more specific? Which case is failing? I know gpairs will get a time out sometime, need debugger to get into it. The merge request was intended for Adarsh to take a look the work I have done, since I will be off for couple days. More polishing and debugging on Monday when I am back. Thanks.

Hi Dipto, can you please be more specific? Which case is failing? I know gpairs will get a time out sometime, need debugger to get into it. The merge request was intended for Adarsh to take a look the work I have done, since I will be off for couple days. More polishing and debugging on Monday when I am back. Thanks.

Look at the Validate dpbench step of the build and run workflow. Pasting an excerpt from the log that shows which benchmarks failed.

58
***** Testing numba_dpex with black_scholes on the S dataset *****
59
NumPy - default - validation: 964ms
60
***** Testing Numba with black_scholes on the S dataset *****
61
NumPy - default - validation: 995ms
62
warnings.warn(
63
/home/runner/work/dpbench/dpbench/dpbench/runner.py:103: UserWarning: ERROR: Failed to test the numba_dpex implementation for dbscan.
64
Numba - nopython-mode - first/validation: 194ms
65
Numba - nopython-mode - validation: SUCCESS
66
Numba - nopython-mode - median: 32ms
67
Numba - nopython-mode-parallel - first/validation: 861ms
68
Numba - nopython-mode-parallel - validation: SUCCESS
69
Numba - nopython-mode-parallel - median: 19ms
70
Numba - nopython-mode-parallel-range - first/validation: 405ms
71
Numba - nopython-mode-parallel-range - validation: SUCCESS
72
Numba - nopython-mode-parallel-range - median: 15ms
73
74
warnings.warn(
75
===============================================================
76
77
/home/runner/work/dpbench/dpbench/dpbench/runner.py:103: UserWarning: ERROR: Failed to test the numba implementation for dbscan.
78
warnings.warn(
79
/home/runner/work/dpbench/dpbench/dpbench/runner.py:103: UserWarning: ERROR: Failed to test the numba_dpex implementation for pairwise_distance.
80
warnings.warn(
81
/home/runner/work/dpbench/dpbench/dpbench/runner.py:103: UserWarning: ERROR: Failed to test the numba_dpex implementation for gpairs.
82
warnings.warn(
83
/home/runner/work/dpbench/dpbench/dpbench/runner.py:103: UserWarning: ERROR: Failed to test the numba_dpex implementation for black_scholes.
84
warnings.warn(
85
/home/runner/work/dpbench/dpbench/dpbench/runner.py:103: UserWarning: ERROR: Failed to test the numba_dpex implementation for kmeans.
86

Hi Dipto, can you please be more specific? Which case is failing? I know gpairs will get a time out sometime, need debugger to get into it. The merge request was intended for Adarsh to take a look the work I have done, since I will be off for couple days. More polishing and debugging on Monday when I am back. Thanks.

Look at the Validate dpbench step of the build and run workflow. Pasting an excerpt from the log that shows which benchmarks failed.

61
NumPy - default - validation: 995ms
62
warnings.warn(
63
/home/runner/work/dpbench/dpbench/dpbench/runner.py:103: UserWarning: ERROR: Failed to test the numba_dpex implementation for dbscan.
64
Numba - nopython-mode - first/validation: 194ms
65
Numba - nopython-mode - validation: SUCCESS
66
Numba - nopython-mode - median: 32ms
67
Numba - nopython-mode-parallel - first/validation: 861ms
68
Numba - nopython-mode-parallel - validation: SUCCESS
69
Numba - nopython-mode-parallel - median: 19ms
70
Numba - nopython-mode-parallel-range - first/validation: 405ms
71
Numba - nopython-mode-parallel-range - validation: SUCCESS
72
Numba - nopython-mode-parallel-range - median: 15ms
73
74
warnings.warn(
75
76
77
/home/runner/work/dpbench/dpbench/dpbench/runner.py:103: UserWarning: ERROR: Failed to test the numba implementation for dbscan.
78
warnings.warn(
79
/home/runner/work/dpbench/dpbench/dpbench/runner.py:103: UserWarning: ERROR: Failed to test the numba_dpex implementation for pairwise_distance.
80
warnings.warn(
81
/home/runner/work/dpbench/dpbench/dpbench/runner.py:103: UserWarning: ERROR: Failed to test the numba_dpex implementation for gpairs.
82
warnings.warn(
83
/home/runner/work/dpbench/dpbench/dpbench/runner.py:103: UserWarning: ERROR: Failed to test the numba_dpex implementation for black_scholes.
84
warnings.warn(
85
/home/runner/work/dpbench/dpbench/dpbench/runner.py:103: UserWarning: ERROR: Failed to test the numba_dpex implementation for kmeans.
86

Thanks, Dipto. Is this from new framework or old framework?

Thanks, Dipto. This is surprising. Is this from new framework or old framework? This is the log I got:

@mingjie-intel I am referring to the log generated by the Github CI workflow.

Reran the test locally on nuc04, all the cases passed:
Start Running DPBench
===============================================================
***** Testing numba_dpex with knn on the S dataset *****
NumPy - default - validation: 5570ms
numba_dpex - kernel-mode - first/validation: 945ms
numba_dpex - kernel-mode - validation: SUCCESS
numba_dpex - kernel-mode - median: 13ms
***** Testing Numba with knn on the S dataset *****
NumPy - default - validation: 5713ms
Numba - nopython-mode-parallel-range - first/validation: 1290ms
Numba - nopython-mode-parallel-range - validation: SUCCESS
Numba - nopython-mode-parallel-range - median: 3ms
===============================================================
***** Testing numba_dpex with kmeans on the S dataset *****
NumPy - default - validation: 829ms
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
numba_dpex - kernel-mode - first/validation: 928ms
numba_dpex - kernel-mode - validation: SUCCESS
numba_dpex - kernel-mode - median: 232ms
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
numba_dpex - prange-mode - first/validation: 960ms
numba_dpex - prange-mode - validation: SUCCESS
numba_dpex - prange-mode - median: 13ms
***** Testing Numba with kmeans on the S dataset *****
NumPy - default - validation: 848ms
Numba - nopython-mode - first/validation: 537ms
Numba - nopython-mode - validation: SUCCESS
Numba - nopython-mode - median: 2ms
Numba - nopython-mode-parallel-range - first/validation: 1126ms
Numba - nopython-mode-parallel-range - validation: SUCCESS
Numba - nopython-mode-parallel-range - median: 2ms
===============================================================
***** Testing numba_dpex with black_scholes on the S dataset *****
NumPy - default - validation: 795ms
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
numba_dpex - kernel-mode - first/validation: 249ms
numba_dpex - kernel-mode - validation: SUCCESS
numba_dpex - kernel-mode - median: 10ms
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
numba_dpex - numpy-mode - first/validation: 865ms
numba_dpex - numpy-mode - validation: SUCCESS
numba_dpex - numpy-mode - median: 7ms
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
numba_dpex - prange-mode - first/validation: 366ms
numba_dpex - prange-mode - validation: SUCCESS
numba_dpex - prange-mode - median: 7ms
***** Testing Numba with black_scholes on the S dataset *****
NumPy - default - validation: 801ms
Numba - nopython-mode - first/validation: 128ms
Numba - nopython-mode - validation: SUCCESS
Numba - nopython-mode - median: 24ms
Numba - nopython-mode-parallel - first/validation: 608ms
Numba - nopython-mode-parallel - validation: SUCCESS
Numba - nopython-mode-parallel - median: 1ms
Numba - nopython-mode-parallel-range - first/validation: 290ms
Numba - nopython-mode-parallel-range - validation: SUCCESS
Numba - nopython-mode-parallel-range - median: 1ms
===============================================================
***** Testing numba_dpex with dbscan on the S dataset *****
NumPy - default - validation: 46ms
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
numba_dpex - kernel-mode - first/validation: 1024ms
numba_dpex - kernel-mode - validation: SUCCESS
numba_dpex - kernel-mode - median: 21ms
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
numba_dpex - prange-mode - first/validation: 1197ms
numba_dpex - prange-mode - validation: SUCCESS
numba_dpex - prange-mode - median: 19ms
***** Testing Numba with dbscan on the S dataset *****
NumPy - default - validation: 36ms
Numba - nopython-mode - first/validation: 743ms
Numba - nopython-mode - validation: SUCCESS
Numba - nopython-mode - median: 20ms
Numba - nopython-mode-parallel-range - first/validation: 1062ms
Numba - nopython-mode-parallel-range - validation: SUCCESS
Numba - nopython-mode-parallel-range - median: 5ms
===============================================================
***** Testing numba_dpex with gpairs on the S dataset *****
NumPy - default - validation: 2ms
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
numba_dpex - kernel-mode - first/validation: 579ms
numba_dpex - kernel-mode - validation: SUCCESS
numba_dpex - kernel-mode - median: 23ms
***** Testing Numba with gpairs on the S dataset *****
NumPy - default - validation: 3ms
Numba - nopython-mode - first/validation: 145ms
Numba - nopython-mode - validation: SUCCESS
Numba - nopython-mode - median: 0ms
Numba - nopython-mode-parallel-range - first/validation: 782ms
Numba - nopython-mode-parallel-range - validation: SUCCESS
Numba - nopython-mode-parallel-range - median: 0ms
===============================================================
***** Testing numba_dpex with pairwise_distance on the S dataset *****
NumPy - default - validation: 57ms
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
numba_dpex - kernel-mode - first/validation: 226ms
numba_dpex - kernel-mode - validation: SUCCESS
numba_dpex - kernel-mode - median: 51ms
numba_dpex - numpy-mode - first/validation: 123ms
numba_dpex - numpy-mode - validation: SUCCESS
numba_dpex - numpy-mode - median: 7ms
Unable to join threads to shut down before fork(). This can break multithreading in child processes.
numba_dpex - prange-mode - first/validation: 314ms
numba_dpex - prange-mode - validation: SUCCESS
numba_dpex - prange-mode - median: 42ms
***** Testing Numba with pairwise_distance on the S dataset *****
NumPy - default - validation: 33ms
Numba - nopython-mode-parallel-range - first/validation: 332ms
Numba - nopython-mode-parallel-range - validation: SUCCESS
Numba - nopython-mode-parallel-range - median: 1ms
===============================================================
All the Tests are Finished. DPBench is Done.
===============================================================

Two cases are still failing during the Github CI pipeline, and one warning:

Warning at beginning:

FunctionPointers: Can't translate function pointer:
%arg.n.frozen = freeze i64 %arg.n
FunctionPointers: Can't translate function pointer:
%arg.n.frozen = freeze i64 %arg.n
FunctionPointers: Can't translate function pointer:
%arg.n.frozen = freeze i64 %arg.n
/usr/share/miniconda/envs/dpbench-devel/lib/python3.9/site-packages/numba_dpex/core/passes/lowerer.py:1434: NumbaPerformanceWarning: Failed to offload parfor to opencl:cpu:0. Falling back to default CPU parallelization. Please file a bug report at https://github.com/IntelPython/numba-dpex. To help us debug the issue, please add the traceback to the bug report. Set the environment variable NUMBA_DPEX_DEBUG to 1 to generate a traceback.
File "dpbench/benchmarks/dbscan/dbscan_numba_dpex_p.py", line 68:
def get_neighborhood(n, dim, data, eps, ind_lst, sz_lst, assignments):

nblocks = n // block_size + int(n % block_size > 0)
for i in nb.prange(nblocks):
^
warnings.warn(NumbaPerformanceWarning(msg, parfor.loc))
FunctionPointers: Can't translate function pointer:
%arg.slm_hist_size.frozen = freeze i64 %arg.slm_hist_size
FunctionPointers: Can't translate function pointer:
%arg.slm_hist_size.frozen = freeze i64 %arg.slm_hist_size

***** Testing numba_dpex with dbscan on the S dataset *****

NumPy - default - validation: 196ms
Failed to execute the numba_dpex - kernel-mode implementation.
Command '['llvm-spirv', '-o', '/tmp/tmpg1ul7d33/1-generated-spirv', '/tmp/tmpg1ul7d33/0-llvm-friendly-spir']' returned non-zero exit status 12.
Failed to run numba_dpex validation.
Failed to execute the numba_dpex - kernel-mode implementation.
Command '['llvm-spirv', '-o', '/tmp/tmpx6cb6wn1/1-generated-spirv', '/tmp/tmpx6cb6wn1/0-llvm-friendly-spir']' returned non-zero exit status 12.

3.***** Testing numba_dpex with gpairs on the S dataset *****

NumPy - default - validation: 2ms
Failed to execute the numba_dpex - kernel-mode implementation.
Command '['llvm-spirv', '-o', '/tmp/tmp46pl6o8e/1-generated-spirv', '/tmp/tmp46pl6o8e/0-llvm-friendly-spir']' returned non-zero exit status 12.
Failed to run numba_dpex validation.
Failed to execute the numba_dpex - kernel-mode implementation.
Command '['llvm-spirv', '-o', '/tmp/tmplzl3zjoq/1-generated-spirv', '/tmp/tmplzl3zjoq/0-llvm-friendly-spir']' returned non-zero exit status 12.

@mingjie-intel can you split up the PR into smaller ones? Preferably one PR each benchmark and a separate one for the Github action workflow.
It will make it easy to review. I will like to get the work in this PR merged ASAP.

Two cases are still failing during the Github CI pipeline, and one warning:

@mingjie-intel I believe that these issues are already captured in numba-dpex issue tracker, but it might still be a good idea to log them as numba-dpex issues. i

Tested locally and the changes look good.


Will EF7 run in Windows 8.1 apps?

Hi, I just wanted to ask if there are any plans to make EF7 available on the Windows 8.1 platform?
Cheers,
Dennis

Hey,
Probably not, at this stage we are just focusing on UWP/Windows 10. When we are done we may look at 8.1 and enable it if the work is minimal... but we suspect it will be non-trivial.
~Rowan

FYI, I dug into this a while ago and our dependency on Caching was the first roadblock I hit--AsyncLocal isn't available the older platforms.


CAMEL-20601: Support error handler on Camel JBang bind command

Description
CAMEL-20601

Allow to add error handler to the Pipe resource
Support different error handler types (sink, uri, log, none)
Support user properties on the error handlers

User can add the error handler with new command option --error-handler:
camel bind timer-to-http --source timer-source --sink http-sink --error-handler log-sink

It results in a error handler specification set on the Pipe:
apiVersion: camel.apache.org/v1
kind: Pipe
metadata:
  name: timer-to-log
spec:
  source:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1
      name: timer-source
    properties:
      message: "hello world"
  sink:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1
      name: http-sink
    properties:
      url: http://localhost:8080
  errorHandler:
    sink:
      endpoint:
        ref:
          kind: Kamelet
          apiVersion: camel.apache.org/v1
          name: log-sink

Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

See CAMEL-20601
Tracking

[x] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.

[x] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

modified:   dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/commands/Bind.java

lets merge and rebuild locally


WIP: Ensure we use a keymgmt from the same provider for signatures

If the pkey cannot export then ensure that we fetch a signature alg from
the same provider as the pkey.
If the pkey can export then fetch any signature algorithm, but make sure
we still use a keymgmt from the same provider as the signature
implementation. We will export the key from the original provider and
import it into the new one.
Partialy fixes #16614
I've only attempted to fix the SIGNATURE implementation here. Similar fixes probably also apply to other operations.
There seems to be quite a bit of code duplication between do_sigver_init() and evp_pkey_signature_init() which is probably a target for future refactoring. I've not attempted to do that here since it would almost certainly end up being a bigger change than we should consider for backporting to a stable branch.

I've marked this as draft because there is no test yet.

This is a bit flawed. as there isn't really an obligation to specify the property you're looking at.  We merely do so in our implementations as a courtesy...
I would rather see an internal function where you can fetch from a single provider, given as a pointer.  That would unambiguously fetch from the exact same provider, no matter property definitions or whatever other user data we throw at it.

This is a bit flawed. as there isn't really an obligation to specify the property you're looking at. We merely do so in our implementations as a courtesy...

This did occur to me. I opted for this route in order to minimise the size of the change to be backported to a stable branch. I guess it depends how invasive the alternative is.

I guess it depends how invasive the alternative is.

It might not be that bad, actually...  I'm much too tired to look at it now, but may be up for the challenge tomorrow

Alternative methodology in #16718

@mattcaswell @levitte - please look at this flow chart I made how I believe it should be done:
https://www.zenflowchart.com/docs/view/KWYxk8mepgpZydMyJNjQ

Mostly that flowchart looks ok, except you have it exporting to one keymanager, and then if that succeeds, but the subsequent fetch of the operation fails to return the same provider as the keymanager, to redo it all and export the key a second time. This doesn't seem quite right to me. Surely we should just fetch the operation using the propq, with the additional proviso that it must come from the same provider as the key manager?

Mostly that flowchart looks ok, except you have it exporting to one keymanager, and then if that succeeds, but the subsequent fetch of the operation fails to return the same provider as the keymanager, to redo it all and export the key a second time. This doesn't seem quite right to me. Surely we should just fetch the operation using the propq, with the additional proviso that it must come from the same provider as the key manager?

The provider of the keymgmt that we originally fetched might not support the operation, but we might still be able to fetch the operation from another provider and export the key to it as the key is not unexportable (we are not in the right branch of the first export).

The provider of the keymgmt that we originally fetched might not support the operation, but we might still be able to fetch the operation from another provider and export the key to it as the key is not unexportable (we are not in the right branch of the first export).

So, do it the other way around.

Fetch the operation alg
Fetch the key manager from the same provider as the alg
Try to export to the key manager
If (3) fails then try the fetch for the operation alg again, but this time with the additional proviso that we must use the same provider as the original key manager

So, do it the other way around.
1. Fetch the operation alg

2. Fetch the key manager from the same provider as the alg

3. Try to export to the key manager

4. If (3) fails then try the fetch for the operation alg again, but this time with the additional proviso that we must use the same provider as the original key manager

IMO this does not respect the propq preference properly. Also you need a keymgmt first to query for the operation name.

Also you need a keymgmt first to query for the operation name.

This is actually a flaw in our current interface...  would would have been better if (for example) a signature implementation would say what keytype it supports.

This is actually a flaw in our current interface... would would have been better if (for example) a signature implementation would say what keytype it supports.

Unfortunately that is set in stone now, isn't it?

Unfortunately that is set in stone now, isn't it?

For 3.0, yes.  For 3.1, we can have the additional function to query the signature method for the supported keytype, and use it if it's there.

Unfortunately that is set in stone now, isn't it?

For 3.0, yes. For 3.1, we can have the additional function to query the signature method for the supported keytype, and use it if it's there.

Actually, I may have found a way to put it to good use anyway, i.e. to fetch the signature method or similar before fetching the keymgmt.  I need to ponder this a bit more...

Also you need a keymgmt first to query for the operation name.

It does not seem unreasonable to me to call query_operation_name on the key manager for the pkey, irrespective of the propq. Arguably this could be seen as part of the "export" from the original key manager, i.e. you ask the original key what kind of algorithm this key is suitable for export for use with.

It does not seem unreasonable to me to call query_operation_name on the key manager for the pkey, irrespective of the propq. Arguably this could be seen as part of the "export" from the original key manager, i.e. you ask the original key what kind of algorithm this key is suitable for export for use with.

I am not sure about this. A specialized provider might want to implement only some operations but you might still be able to export the key to another provider for other operations.

I am not sure about this. A specialized provider might want to implement only some operations but you might still be able to export the key to another provider for other operations.

The provider does not need to implement the algs/operations in order for query_operation_name to return that alg name for a given operation. It is just a declaration of what operations/algs the key is suitable for use with.
You have this problem no matter what keymgmt you use, i.e. you might end up in a key manager that doesn't actually implement the operations/algs that we are interested in. It's a fundamental flaw in the design of query_operation_name

Here's a second attempt at this PR which:

Incorporates all of the commits from #16718 and builds on them
Removes the controversial change to prefer the pkey's keymgmt during the init of EVP_PKEY_CTX
Removes the code to concatenate "provider=xxx" onto the query string

Closing this in favour of #16725


Update readme

Update readme to include what is different between ocm and stolostron. highlight what addons we include in stolostron.

/assign @yanmxa


Adding support for styled-components

Styled components is a package to style components with CSS in JS concepts.
As explained in their docs,  the only requirement to use styled-components with third-party components is the following:

Note: styled-components generate a real stylesheet with classes. The class names are then passed to the react component (including third party components) via the className prop. For the styles to be applied, third-party components must attach the passed-in className prop to a DOM node.

You only need to pass this.props.Classname to the wrapper div's className prop on BoostrapTable.js.
classSet('react-bs-table-container', this.props.className, this.props.containerClass)

This is fully compatible with all react-bootstrap-table's customizable classes.

Merged!  Thanks you :)


Create a package for the VS integration tests

This creates a package to be used for VS integration test automation runs.  It's a nonstandard package and only intended for use with the VS automation runs.
This package always uses a version that doesn't contain the prerelease data.  This is only because I couldn't find a way to force the nbgv CLI to respect the PublicRelease environment variable, so the NugetPackageVersion it generates is always prerelease.  This didn't match what was generated by CreateInsertionMetadata.proj which does respect the environment variable.
I also had to update some of the VS dependencies to get the tests running again.

Closing for now as this is really stale, and I don't know if it's worth it.


get hash of encrypted zip file

I need to break a zip file created and encrypted with zip4j.
zip2john says it is corrupted, 7zip shows it is fine, only problem is I don't know the password - is there a possibility to get the hash of the password (for breaking it with for example hashcat)?

I suggest you to read through the zip file format specification and see if you can find the position of the bytes you need and try reading those bytes. The information you ask for, cannot be obtained by zip4j.


🐛 build error on iOS

What were you trying to do?
attempting to build my project
Reproduceable Code
react-native-skia: "0.1.185"
XCode version is 14.3
What happened instead?
I'm receiving the following error when trying to build my project:
Relevant log output
node_modules/react-native-vision-camera/ios/Skia Render Layer/SkiaMetalCanvasProvider.h:13:10)

  11 |
  12 | #include <functional>
> 13 | #include <include/gpu/GrDirectContext.h>
     |          ^ 'include/gpu/GrDirectContext.h' file not found
  14 | #include <mutex>
  15 | #include <memory>
  16 | #include <atomic>

Device
ios
VisionCamera Version
3.0.0-rc.2
Additional information

[X] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

same error how fix these headers no founds?

@R4tch3t see https://github.com/mrousavy/react-native-vision-camera/issues/1376#issuecomment-1525731923 for a (temporary) potential solution

@R4tch3t see #1376 (comment) for a (temporary) potential solution

Thanks work for me!

@vbylen Would you be able to share a template for Expo? Trying to recreate the same and running into issues

@AnomalousLLC you just need to install patch-package and create a file under your patches folder in which you then copy/paste the code shared above.

Closing as this is a stale issue - this might have been fixed with the full rewrite in VisionCamera V3 (🥳) - if not, please create a new issue.
If your issue has been fixed, consider sponsoring me on GitHub to say thanks 💖


You are introducing breaking changes to the API, update the changelog and also update the API documentation.

Done.


Frontend branch

Made a Homepage which is not that great and added a search button which displays table with pagination and sorting options

this PR also works on #4 and #5

Added prettier in package.json and removed the tech debt.


New launcher

https://github.com/sbt/launcher/pull/27
We need to build and release a new launcher.

https://github.com/sbt/sbt/pull/3002/commits/bf8e49edbd106036a82335a946db3771a15dfda6


Support Lightweight Python components in Vertex & KfP runners

We should be able to execute Lightweight Python components with our Vertex & KfP runners.
We can take inspiration from KfP which seems to include the python script as part of the entrypoint of the docker container.

Fixed by #803


Support text config files

Support the specification of dependencies in a text configuration file.
For example:
OLD
<?php
$injector = new Auryn\Injector;
$injector->define('PhpAmqpLib\Connection\AMQPStreamConnection', ['localhost', 5672, 'guest', 'guest']);
$obj = $injector->make('ClassDependingOnAMQPStreamConnection');

NEW
You could define this in yaml/XML/whatever:
# wiring.yaml
wiring:
    - { class: PhpAmqpLib\Connection\AMQPStreamConnection, params: [localhost, '5672', guest, guest] }

<?php
$injector = new Auryn\Injector;
$injector->parseWiring(file_get_contents('wiring.yaml'));
$obj = $injector->make('ClassDependingOnAMQPStreamConnection');

I'm doing this in my bootstrap. I have an array that maps between interfaces and concretes that I loop for alias, then another for share. If this were built into the injector, it would be great to have a format for specifying aliases, shares, and parameter binding.

Would there be an impact on performance - loading and parsing the wiring file for each process?
We tend to use PHP files so they are auto cached by APC/Opcache.

On the performance side, I cache my config files as I do this in my bootstrap as well.
But then we're going into standardising configuration and I'm not sure that's okay. We all know the PSR lot will be all over that soon enough I bet (OMG PLEASE USE CONTAINERINTEROP)...

I would expect details like cache configuration (e.g. memcache/redis connection details) to be part of the Di configuration... chicken/egg ?

I think that the injector as a standalone lib is great, just worried about putting a load of extra bloat around it. That's what bridges or adapters are for; for different frameworks and use-cases.
Don't get me wrong, I'd personally find something like this useful so I write my own. But if Auryn includes it, we're talking including parsing libs, caching libs, setting new standards, the injector isn't just an injector any more.

Re: performance and caching ...
I was thinking something more along the lines of this:
<?php

$cacheDump = "/path/to/dumped/injector.php";

if (!@include $cacheDump) {
    $textConfig = "/path/to/text/config.yml";
    $injector = Auryn\Injector::loadFromTextConfig($textConfig);

    // we only have to do this once
    $injector->dump($cacheDump);
}

// Rest of the application goes here

This way you aren't eating any performance costs. We'd just be providing our own text config format. I think adding support for optimized cache dumping would be a useful (necessary) complement to this functionality.
Thoughts?

Something like that would work for us.
We deploy a lot to environments like Google App Engine, where it's a containerised read-only filesystem.
So we would potentially integrate the cache dump phase into our deployment process and require the dump file to be present in "production" environments.
But, like I said, that could work!

Also, we could just "not use" the text file .. ;)

Cool. I'll add an additional issue for the cache dumping functionality.
FYI the plan is to tag an official v1.0.0 release in a few hours. None of this stuff will be present in that  version ... it wouldn't appear until a fully BC-compatible 1.1 in the future.

The caching idea is great, but more thought needs to be put into "just using" the text file.

I (and I suspect many others), have done this more at the framework level.  One of the things I get very annoyed with, particularly now that composer is more popular is that there are a lot of libraries that feel it necessary to include this type of functionality, but they all have varying support/formats.
I generally want my configurations to be using the same language and the same configuration structures/files so that there's not 10 different points of configuration.
I don't feel this needs to be included or should be.  It could be a separate package if people need a solution because they don't have another, but there are other solutions out there for unified config and bootstrapping.

@mattsah's comment better articulates my point of view :-)

That's fine then. In general I'm of the belief that less is more. The answer is (usually) not more options. If you feel compelled to expose new preferences to the user it's very possible you've made a wrong turn somewhere. Will scrap plans for this now. Folks are free to re-raise the issue in the future if they see fit.

Thanks, I think that's the best call. It is a good idea, but one that is trivial enough to implement by the package consumers in a way that meshes with their own project's conventions.


Does Azure Service Bus Binding Support Sessions?

Does Azure Service Bus Binding Support Sessions?
I see there has been some work regarding Topics here but the outcome of the issue is unclear to me and i also don't see sessions mentioned anywhere in the documentation.
A quick test showed that i don't receive messages with queue input binding on queues using sessions.
We need to receive messages in an ordered way per device (where we use the device id as session id) so sessions are crucial for us.

Currently neither bindings or pubsub support sessions AFAIK. I have a PR to enable the session id to be set on the message metadata when using pubsub with ASB topics. However, the Dapr ASB subscription isn't actually session aware. It's something I've been meaning to look into again when I've got time but I wouldn't expect anything in the near term.

https://github.com/dapr/components-contrib/issues/1532


Visual issue, folder icons not rendering as expected

Description
Every time i set de icon size to medium the folder icons render with a black border and doesn't seems good.

Steps To Reproduce
Go to layout
Click On medium icons

Expected behavior
I expect when i select the medium icon size doesn't show that black border on the folders 😢
Files Version
Version: <IP_ADDRESS> OS Version: 10.0.22000.832
Windows Version
Edition	Windows 11 Pro Version	21H2 Installed on	7/31/2022 OS build	22000.832 Experience	Windows Feature Experience Pack 1000.22000.832.0
Relevant Assets/Logs
debug_fulltrust.log
debug.log

Merging with #6373


graphicsdriver/metal: Reduce syncing texture data

After 2bc1475a151043f8ffca1ba8e3b06c4be743960a, the performance has become bad since this requires syncing texture data to CPU often. Let's optimize this.

Fixed by ebd0e11c0dfa27de8165c5385e764f343790d195


Akai S1000 stuttering audio when using raSCSI

Info

Which version of Pi are you using:  Raspberry Pi Zero 2 W
Which github revision of software:  21.12.01
Which board version: V2
Which computer is the RaSCSI connected to: Windows 10 x64 PC

Describe the issue
When saving or loading any samples from raSCSI onto an Akai S1000, the audio stutters and clicks on playback.  Tried this with multiple emulated drives in different sizes.
The raSCSI is confirmed working, I tried it on my S3000XL and it was working perfectly.
S1000 is confirmed working as well,  I installed a SCSI2SD V5.2 and it worked perfectly.

@ghal30n You have not yet provided feedback. Please use the current release 22.07.02 or the develop branch for further testing.
Please note that we will have to discard this ticket if there is no further feedback.

@ghal30n I would like to remind you to provde feedback, please see my previous comments for details. Otherwise I'm afraid we will have to close this ticket.

its all good! you can close the ticket, I'm way too busy to give this proper attention at the moment

@ghal30n Thank you for your response. I will close the ticket. In case you have more time again (in the future) you might want to get back to this ticket.


add shrink-to-fit=no to viewport meta tag (ios9 fix)

iOS9 has changed the default behaviour when content is pushed off to the side of the screen, shrinking the page to fit all the content. In order for the sidebar to work, you just have to add shrink-to-fit=no to your HTML's viewport meta tag. There's more information on the Apple Developer Forums.
I just added the info to the viewport meta tag, and noted this in the README - since it seems like quite a few people are having trouble with this!

Thanks, I will review this soon!

thx Tao. This had been driving me batty. Not sure why PRs aren't being merged. Would have saved me hours.


tabs should support custom elements

Because tab styles are defined as child -- and not descendant -- selectors:
.nav-tabs > li { ... }

Tabs that are injected via custom elements aren't styled correctly:

  <my-custom-tab-wrapper-element>

Hai Tab

  </my-custom-tab-wrapper-element>

My thoughts on solutions, in order of preference:

Use a descendant selector: .nav-tabs li {...} - Is backwards compatible, and doesn't impose any additional requirements on custom elements. It doesn't seem likely to break anything -- is anyone nesting
 within tabs?
Use a class to represent tabs: .nav-tabs > .tab {...} - Breaks existing tabs. Requires custom elements to express classes, which isn't great -- we might want to keep style rules within templates. But, doesn't risk issues with nested list items. I don't think it's really a big risk.

Thoughts?

@jczerwinski not sure I agree. To my knowledge, and I could be wrong, the only areas that really support components named in that way are third party frameworks such as Angular which offer other options for integrating components such as AngularStrap.
Is there a different method of creating custom components which I'm not aware of?

@kkirsche I do happen to be running into this with Angular and UI-Bootstrap, but I don't think it's limited to this.
You're right that it's third-party libraries providing most of this functionality at the moment. Polymer and React would be other examples.
These frameworks also seem intended as a bridge to/wrapper around the Custom Elements API, which is natively supported in some of the more recent browser releases, so using frameworks to do this isn't strictly necessary.
I can see how this would be a slippery slope -- many other selectors could become less specific to accommodate similar use cases. In this case the risk seems pretty low, but maybe that's not true elsewhere. Button groups are another obvious example where this would happen: <my-custom-button-wrapper>... ad nauseum I'm sure.
Anyway, this isn't too important to me, so don't be afraid to reject. Could be I'm trying to use these things in a uniquely weird way. I get the feeling that this sort of thing will come up again, but I'm happy to wait and see. Keep it in mind, maybe some other requests fit the pattern.

This is fixed in upcoming Bootstrap v4, where the relevant selectors have already been changed to address both of your points: :smile:
https://github.com/twbs/bootstrap/blob/210e2b8100e0a90e097cd98f1abd7c3bfdc72a8b/scss/_nav.scss#L49-L57
We aren't accepting significant changes into Bootstrap v3 anymore, since v4 is coming soon, so this is WontFix for v3.

:+1:


crypto/rand: rand.Read hangs with extremely large buffers [go1.16 backport] - CVE-2022-30634

From Golang security announcement:

On Windows, rand.Read will hang indefinitely if passed a buffer larger than 1 << 32 - 1 bytes.
Thanks to Davis Goodin and Quim Muntal, working at Microsoft on the Go toolset, for reporting this issue.
This is CVE-2022-30634 and Go issue https://go.dev/issue/52561.

Closed by: https://github.com/aws/eks-distro-build-tooling/pull/570


csv examples look weird

csv markdown annotations look weird.
For example, this snippet:
```csv
file_name,text
images/1.jpg,a drawing of a green pokemon with red eyes
images/2.jpg,a green and yellow toy with a red nose
images/3.jpg,a red and white ball with an angry look on its face
images/4.jpg,a cartoon ball with a smile on it's face
```
is displayed like this:

Is it supposed to look like this? Is it possible to do something with it? :upside_down_face:

cc @severo
was noticed here https://github.com/huggingface/hub-docs/pull/1148


Missing Ingress Annotation in Documentation

Hello everybody,
there is a missing annotation in the docs:
ingress.appscode.com/load-balancer-ip: XX.XX.XX.XX can be used to hand over a predefined static ip adress to the outbound service in gke.
I think this should be added to the annotation-page: https://github.com/appscode/voyager/blob/master/docs/user-guide/ingress/ingress-annotations.md
best regards
Lasse

It is documented in https://github.com/appscode/voyager/blob/master/docs/user-guide/ingress/README.md.
But we should merge them into one doc.


Issue with multi gpu dp backend

Describe the bug
I tried to run gpu_template.py from basic_examples but I get an error that says Fatal Python error:Aborted (screenshot below). I am able to use ddp but not dp. Did anyone else face this issue?
Screenshots

what versions are you running?
how are you running it? (cluster?, interactive mode?)
Do you have 2 gpus.

Update - The same code worked when I ran it today. Don't know what the issue might have been.
Versions -
pytorch-lightning: <IP_ADDRESS>
test-tube: 0.7.1
torch: 1.3.0
I'm running it on a cluster in interactive mode. It has 2 gpus.


containerRuntimeExecutor usage needs clarifying before 3.4 release

Checklist

[x] Double-checked my configuration.
[x] Tested using the latest version.
[x] Used the Emissary executor.

Summary
This page of the documentation advises users to use the containerRuntimeExecutor value in the configmap.
This value has been removed in 3.4.
No other alternative is documented. The example configmap implies (but doesn't explictly say) that one can use an arg on the workflow controller, but this doesn't appear to be documented.
What version are you running 3.4-rc2
Diagnostics
Paste the smallest workflow that reproduces the bug. We must be able to run the workflow.

# Logs from the workflow controller:
kubectl logs -n argo deploy/workflow-controller | grep ${workflow}

level=fatal msg="Failed to register watch for controller config map: error unmarshaling JSON: while decoding JSON: json: unknown field "containerRuntimeExecutor""

---
<!-- Issue Author: Don't delete this message to encourage other users to support your issue! -->
**Message from the maintainers**:

Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

containerRuntimeExecutors has the exact same issue. No documentation explaining what I can do instead.

Thank you! Added in https://github.com/argoproj/argo-workflows/pull/9437.


Access Denied when installing an app

Brief description of your issue
When validating installs, periodically the installer fails with access denied.
for example PR  https://github.com/microsoft/winget-pkgs/pull/396
and
Capture file list
query registry
run install
Found Netbeans 11.3 (x64) [Apache.Netbeans]
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://downloads.apache.org/netbeans/netbeans/11.3/Apache-NetBeans-11.3-bin-windows-x64.exe
██████████████████████████████   193 MB /  193 MB
Successfully verified installer hash
An unexpected error occurred while executing the command:
rename: Access is denied.: "C:\Users\kevin\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\TempState\WinGet\Apache.Netbeans.11.3", "C:\Users\kevin\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\TempState\WinGet\Apache.Netbeans.11.3.exe"
failed to install
winget install -m netbeans.txt
Steps to reproduce
try to install PR 396 manually.  same with netbeans
Expected behavior
Actual behavior
Fails to install and aborts
Environment
C:\temp>winget --info
Windows Package Manager v0.1.41331 Preview
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.18363.719
Package: Microsoft.DesktopAppInstaller v1.0.41331.0
Links:
Privacy Statement: https://aka.ms/winget-privacy
License agreement: https://aka.ms/winget-license
3rd Party Notices: https://aka.ms/winget-3rdPartyNotice
Homepage:          https://aka.ms/winget

The Access denied error occurs even when running the installer manually from the folder
C:\Users\{UserName}\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\TempState\WinGet

Duplicate of #
Looks to be a duplicate reactivate if you disagree.

Was having this problem with GIMP and Visual Studio Code.
Found a workaround by right clicking CMD / Powershell and selecting "Run as Administrator", and then installing via winget, after which both installed without problems.

Hi @KevinLaMS ,
Of which issue this is a duplicate ? There is no number in your previous command.
I also get Access Denied windows with some app (like Git or new one I work on https://github.com/microsoft/winget-pkgs/pull/1304)

Any update on the issue that replaced this one?

I believe @KevinLaMS meant to reference issue #189.

@megamorf correct

Sorry, I'll use #189 for tracking


New styling for images and embedded patterns

name: Styling for images and embedded patterns
about: This a pull request to fix styling of images and embedded paterns
title: 'feat: New styling for images and embedded patterns'
labels: ''
assignees: '@delisma'
What does this MR do?
Modify the 2020-12-17 posts to see if the styling approach for images and embedded pattern make sense
General checklist

[ ] Documentation created/updated
[x] Changelog entry added, if necessary
[x] Tests added for this feature/bug
[x] Conforms to the style guides

Preview links
en: Choosing the right button for task success
fr: Choisir le bon bouton pour la réussite des tâches

@Laura Piper, @Arianna The blog posts has been modified to put images and embedded patterns in a <figure class="thumbnail"> tag.
Two things that bother me a bit:

When we hover on images, it looks like images can be clicked. I’ll see if the details/summary can be opened when the image is clicked
The figures expand to the full-width of the page. I can constraint them to the width of the content with custom CSS, but meh.

@LPipes4 , @arianna-merritt The blog posts has been modified to put images and embedded patterns in a <figure class="thumbnail"> tag.
Two things that bother me a bit:

When we hover on images, it looks like images can be clicked. I’ll see if the details/summary can be opened when the image is clicked
The figures expand to the full-width of the page. I can constraint them to the width of the content with custom CSS, but meh.
I was able to make the images about the same length as the text column (85 char vs 65 char) and make the background colour of the details/summary white. We still have to hover effect on the images I'll take another look later today.

@arianna-merritt I think we're good with this new pattern. I've created a CSS class gc-complex-img that you can put on a figure tag and will frame the image inside a white bordered box.


4.15-HBase-1.5-PHOENIX-6243

Hi @fengchen8086 , thanks for the PR. However, our current active branch is 4.x and master. Would you mind close this PR and then raise a PR against the 4.x branch for your hbase1.5 case. Thanks a lot.

@yanxinyi sure.
#1020 is already raised.
I'll close this PR.