Error while running bench.sh for d_grpc on linux arm64

@LesnyRumcajs, I was trying to run d_grpc_bench for arm64 locally but getting errors while build.sh and bench.sh.
I did the below changes for running build.sh
I found that the image dlang2/ldc-ubuntu:1.26.0 present in the dockerfile is not available for arm64. So, I build the image and updated it in the dockerfile but while building the image from dlang-docker, I have used ldc compiler for dlang because by default it uses dmd and dmd doesn’t support arm64 architecture. Please have a look https://dlang.org/download.html
when I ran build.sh, I was getting error related to dub command because the binary is not present for arm64. I found the binary on ubuntu.pkgs.org and updated it in the dockerfile.
After that I ran build.sh again and getting Error: The LLVMgold.so plugin (needed for LTO) was not found. You can specify its path with -flto-binary=<file>. So, I modified the dub.json file and added the -flto-binary path that is "dflags-ldc": ["-flto=/usr/lib/llvm-10/lib/LLVMgold.so"]
Updated Dockerfile: dockerfile.txt
Now the build.sh for d_grpc_bench is running successfully but bench.sh is failing with the below errors.
ubuntu@ip-172-31-19-230:~grpc_bench$ sudo ./bench.sh d_grpc_bench

==> Running benchmark for d_grpc_bench...

Waiting for server to come up... ready.

Warming up the service for 5s... done.

Benchmarking now...

                done.

                Results:

                    Requests/sec:       5586.37

Error response from daemon: No such container: d_grpc_bench

-----

Benchmark finished. Detailed results are located in: results/221711T054811

/analyze/results_analyze.rb:25:in `block in <main>': undefined method `[]' for nil:NilClass (NoMethodError)

        from /analyze/results_analyze.rb:15:in `each'

        from /analyze/results_analyze.rb:15:in `<main>'

Failed miserably analysing d_grpc.

Analysis fiascoed.

total 12K

drwxr-xr-x  2 root root 4.0K Nov 17 05:48 .

drwxr-xr-x 33 root root 4.0K Nov 17 05:48 ..

-rw-r--r--  1 root root  623 Nov 17 05:48 d_grpc_bench.report

-rw-r--r--  1 root root    0 Nov 17 05:48 d_grpc_bench.stats

results/221711T054811/d_grpc_bench.report

Summary:

  Count:        112868

  Total:        20.20 s

  Slowest:      0 ns

  Fastest:      0 ns

  Average:      10.81 ms

  Requests/sec: 5586.37

Response time histogram:

Latency distribution:

Status code distribution:

  [Unavailable]   112104 responses

  [Canceled]      764 responses

Error distribution:

  [112104]   rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"

  [764]      rpc error: code = Canceled desc = grpc: the client connection is closing

 results/221711T054811/d_grpc_bench.stats

Could you please share your feedback regarding the same.

Hi @odidev. This means that the server could not handle any request - you can see it in the status code distribution. There's not a single success. I admit the error message is rather cryptic.

@LesnyRumcajs I think this issue is because of bench.sh failed to create d_grpc_bench conatiner while running the sudo ./bench.sh d_grpc_bench
Error response from daemon: No such container: d_grpc_bench
I tried to create conatiner  for d_grpc_bench but getting the below error:
ubuntu@ip-172-31-19-230:~/grpc_bench$ docker run -it --name grpc_cont grpc_bench:d_grpc_bench-complex_proto bash

/app/server: error while loading shared libraries: libphobos2-ldc-shared.so.98: cannot open shared object file: No such file or directory

Could you please share your pointers on the same.

@odidev Have you tried installing the missing dependency? Something along the lines of sudo apt-get install -y libphobos2-ldc-shared-dev?

Or perhaps only this one is needed. https://pkgs.org/download/libphobos2-ldc-shared90

@LesnyRumcajs I found that the image that I build for arm64 using dlang-docker for ldc require bin folder so I added it in the dockerfile after that the error related to dub command not found and Error: The LLVMgold.so plugin is resolved while running the build.sh but when I ran bench.sh I am getting the same error.
Please have a look at the updated dockerfile: dockerfile
ubuntu@ip-172-31-19-230:~/priya/grpc_bench$ sudo ./bench.sh d_grpc_bench

==> Running benchmark for d_grpc_bench...

Waiting for server to come up... ready.

Warming up the service for 5s... done.

Benchmarking now...

                done.

                Results:

                    Requests/sec:       5498.17

Error response from daemon: No such container: d_grpc_bench

-----

Benchmark finished. Detailed results are located in: results/220812T103837

/analyze/results_analyze.rb:25:in `block in <main>': undefined method `[]' for nil:NilClass (NoMethodError)

        from /analyze/results_analyze.rb:15:in `each'

        from /analyze/results_analyze.rb:15:in `<main>'

Failed miserably analysing d_grpc.

Analysis fiascoed.

total 12K

drwxr-xr-x  2 root root 4.0K Dec  8 10:38 .

drwxr-xr-x 12 root root 4.0K Dec  8 10:38 ..

-rw-r--r--  1 root root  623 Dec  8 10:39 d_grpc_bench.report

-rw-r--r--  1 root root    0 Dec  8 10:38 d_grpc_bench.stats

results/220812T103837/d_grpc_bench.report

Summary:

  Count:        110513

  Total:        20.10 s

  Slowest:      0 ns

  Fastest:      0 ns

  Average:      11.02 ms

  Requests/sec: 5498.17

Response time histogram:

Latency distribution:

Status code distribution:

  [Unavailable]   109838 responses

  [Canceled]      675 responses

Error distribution:

  [109838]   rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp <IP_ADDRESS>:50051: connect: connection refused"

  [675]      rpc error: code = Canceled desc = grpc: the client connection is closing

results/220812T103837/d_grpc_bench.stats

Now when I am trying to create container for d_grpc_bench I am getting the below error:
ubuntu@ip-172-31-19-230:~/priya/grpc_bench$  docker run -it --name d_grpc_bench grpc_bench:d_grpc_bench-complex_proto bash

/app/server: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /app/server)

/app/server: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /app/server)

/app/server: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /app/server)

I tried the same on amd64, I built the image for dlang2/ldc-ubuntu of latest release 1.30.0 but getting same error on both arch while creating the container.
Could you please share your feedback for the same?

@LesnyRumcajs Could you please share your feedback regarding the above issue.

Sorry, I was on vacation. This error would typically mean that you compiled the binary on a different platform. It would be best if you try to compile a minimal Hello World application in D using the official D lang Dockerfile on your machine.

@LesnyRumcajs I successfully compiled the Hello World application inside the docker container using the docker image that I built for arm64 by their official dockerfile. I have updated the variables in this dockerfile for building the dlang image.
Please have a look at the logs:
ubuntu@ip-172-31-23-20:~/dlang-docker$ sudo docker run -it --name hello ldchello:hello_world bash

root@b8d9f6f4c3ff:/# vi hello.d

root@b8d9f6f4c3ff:/# ldc2 hello

root@b8d9f6f4c3ff:/# ./hello

Hello, World!

Could you please share your feedback regarding the same.

@LesnyRumcajs Could you please share your feedback regarding the above issue?

Not at the moment. I'm a bit pushed for time, and it'd require a longer investigation. Sorry.


Init AC Network

Hi, thank you for your code.
I have a issue with init AC Network for meta bandit:
hidden = tf.concat(1, [self.prev_rewards, self.prev_actions_onehot, self.timestep])
It gave me a error:
TypeError: Expected int32, got list containing Tensors of type '_Message' instead.
Thank you very much for replay

Hi Golly,
That error is the result of the wrong argument order for tf.concat. In Tensorflow 1.0 they rearranged a number of the function arguments. It should be
tf.concat([self.prev_rewards, self.prev_actions_onehot, self.timestep],1)
I just updated the three notebooks, and they should work correctly now.


Setting batch_type to 'single_image'

Hi,
I'm trying to train a model with the batch_type set to 'single_image', but it seems like this part hasn't been implemented so far.
I tried to set shuffle in dataloader to be False, so that each batch has rays only coming from one image. However, it doesn't seem to work as the novel view are just white images.
Any clue what might be a right implementation for 'single_image' mode?
Appreciate any input you might have.

Hi,
'single_image' mode only can be used for 'val' now. If you have RAM limitations I think you can downscale image size https://github.com/hjxwhy/mipnerf_pl/blob/bd88427c206e113d9d6e9d8449d1b8c21d4a8335/datasets/datasets.py#L194. for single scale mode.

Thanks! RAM is actually not the exact issue here. So I wanted to train a model with each batch only have rays/cones coming from a single image. Each batch could have only 1% of total rays of a single image, that is, all rays of an image can be divided into 100 consecutive batches. With that in mind,  and I tried to simply not shuffle in dataloader. So that the rays are being process in order. But the trained model renders only white images.
Would you have any thoughts on what might have gone wrong?

From my understanding, you want to train the model one by one image, and now you have tried split=="train", batch_type=="all_images", shuffle==False in dataloader, but the model can not converge, yes? How about the loss and training PSNR? If the model seems converged, you can render an image from the training set and an image from val set, making sure the model is overfitting or not.

Yes, that what I did. And the model doesn't seem to converge. I plotted out the loss too, it's simply not converging. I tried to shuffle the rays within an image as well, but seems like it doesn't help with making the model converge. Any thoughts?

Such a learning curve is as invalid as I expected, so random sampling is needed during training. I think the network is learning on one image with gradient descent in one direction, but when this image is finished learning and a new image comes, the gradient descent of this image may not be in the same direction as the last one. So the network will jump repeatedly on a local optimum. Have you made sure random shuffle in all data works well?

That makes sense. Yeah, when I shuffle all data, it works well and renders image properly.

Thanks for your input! I'm closing this issue since I was able to fix this issue by shuffle rays within an image. Really appreciate your help!


Why examples changed and now using terraform-aws-modules/eks/aws instead of eks blueprints module

[X ] ✋ I have searched the open/closed issues and my issue is not listed.

Please describe your question here
I was looking at the latest examples and saw you do not use the blueprints module to install EKS cluster and you are using terraform-aws-modules/eks/aws.
Is there a reason for it? I had some issues with the addons and wanted to make sure vpc cni installs before nodes provisioning  and saw it in the examples, but it's with a different module.
How hard is the migration? I see there are some parameters that missing from this. module like map_users.
Thank you!
Provide a link to the example/module related to the question
 PR Link
** I see its related to v5 upgrade but it is not official yet right?

@Tstrul-work we are incrementally making updates to the repo for the v5 changes. We will publish a migration guide as we get closer.


Add more themes

Hi! It would be nice if some cool themes were added! :+1:

@kino90 good idea! We'll think about adding more themes.
Please note that the idea behind JCF is about flexible customization for specific design.
That's why we have only "minimal" theme which is used as a starting point for customization.

Sure, but it would be cool to have some themes like 'bootstrap', 'material design' and similar.. that are extra-cool as you download them, and also easy to import as scss and extend with custom colors and styles!

#57


CVE-2019-12814 related to com.fasterxml.jackson.core:jackson-databind

Hello,
At least one CVE (CVE-2019-12814) is brought up with com.fasterxml.jackson.core:jackson-databind version 2.9.9 included in spring-cloud-cloudfoundry-connector. The corrections were fixed in version <IP_ADDRESS>.
Can the version be updated in a quick upcoming fix?
Thank you,
Simon

See #297

@tremblaysimon Please note that this project is in maintenance mode, in favor of the newer Java CFEnv project. We will continue to make this type of security-related changes, but releases will be fewer and further between.

Thank you for the information I will check that project.

@scottfrederick Do you know if it is possible for you to release a new version of spring-cloud-connectors with #297 since it's merged (and fixed).
In the meantime, I will ask our teams to migrate to new Java CFEnv library as soon as they can. Do you know if the migration guide from spring cloud connectors to Java CFEnv exists somewhere (mentionned in the blog post you shared to me) ?

We haven't published a migration guide yet. For apps using Connectors, it is very simple (most of the migration guide will address Connectors extension libs).

Replace dependencies on Connectors libraries (via direct dependencies like org.springframework.cloud:spring-cloud-cloudfoundry-connector or the Boot starter org.springframework.boot:spring-boot-starter-cloud-connectors) with a dependency on the appropriate Java CFEnv libs
Remove any code that customizes the connections created by Connectors and replace with the appropriate Boot auto-configuration properties


Keep initial drag position

When dragging an object, keep the initial drag position instead of
center the drag image around the pointer.
also keep the object inside the screen until we really try to go outside.

Thanks for this! Would it be possible to provide a bit more detail. Is it likely to affect existing users adversely?

My problem was that we were dragging a table row which occupies ⅓rd the width of the screen, and it can be dragged and dropped into a list to the right. When starting dragging, the row centers around where you drag, so regardless of where you drag from, you end up with half of the row to the right. Directly when you move the row and it's right edge goes pass the browser, it will start rescale the unit (tested in chrome).
to have the object dragged where you press is logical, and unless it's possible to prevent screen swapping, the object should be kept in the browser window while you are still dragging in the browser window.

As I feel I've failed to explain the issue I had, I've created http://embed.plnkr.co/MMPicFqjxvEC4sPGRXr5/ to show what problems I had. the screen scaling issue I had is not reproducible so I assume that's related to some funky css we are using :/

I realize my second problem with the zooming viewport was related to http://stackoverflow.com/questions/14270084/overflow-xhidden-doesnt-prevent-content-from-overflowing-in-mobile-browsers and I assume we could omit the viewport limit in the PR.

I did decide to remove the out of bounds check and only include the drag position code in this pull request.

Closing because this is already contained in the rewrite now released. https://www.npmjs.com/package/mobile-drag-drop


Export as verifiable credential

Verifiable Credentials are a W3C standard for cryptographically-signed digital credentials.
The UI should support exporting attestations in this format. The issuer would be the signer of the attestation.
This would require base64 encoding binary data in some cases.

I have published my notes on the Verifiable Credentials spec here.

Not sure if only the frontend should do this (my original plan) or if the backend should instead/as well.

As mentioned in my notes, the spec allows for VCs to be serialized in formats other than JSON-LD such as CBOR. Since some attestations include binary data, and we already use DAG-CBOR, it might make sense to encode our VCs as DAG-CBOR.
What it comes down to is how accessible we want the output to be; who will be consuming these credentials? This question is also relevant since we are creating our own schema which may or not be public (see notes). Everything is already quite bespoke about this implementation, despite us following the standard. Maybe it's not a big deal to add one more thing to the pile.

Should timestamp information go inside the VC as well?

Here is an example VC, using private schema URNs instead of public documents (see notes). Usage of urn:cid: has precedent, see here.
{
  "@context": [
    "https://www.w3.org/2018/credentials/v1",
    "urn:authattr:vc-schema:1"
  ],
  // CID of "attestation" field in attestation, the part that gets signed
  // Because the credential is just a transformation of this
  "id": "urn:cid:bafyreietqpflteqz6kj7lmdqz76kzkwdo65o4bhivxrmqvha7pdgixxos4",
  "type": ["VerifiableCredential", "AuthAttrCredential"],
  // Maybe like this? Or author name could be used
  "issuer": "urn:authattr:pubkey:82zNiAAng99HblAvTe2mjsC3fQ-gI416b0fNLiNmS8s=",
  // Timestamp from attestation, not timestamp of VC creation
  "issuanceDate": "2023-07-13T14:34:17Z",
  "credentialSubject": {
    // CID of the file, as that is what the claims in this credential are about
    "id": "urn:cid:bafkreif7gtpfl7dwi5nflge2rsfp6vq6q5kkwfm7uvxyyezxhsnde5ly3y",
    // Fields copied from attestation schema:
    "attribute": "description",
    "value": "Web archive foo bar",
    "encrypted": false,
    // Set to true when "value" is base64-encoded DAG-CBOR bytes instead of a
    // regular JSON value. If "encrypted" is set to true then this field is
    // irrelevant as "value" is always base64-encoded as the *encrypted*
    // DAG-CBOR bytes.
    "binary": false
  },
  "proof": {
    "type": "authattr_ed25519",  // Something unique
    "pubKey": "<base64-encoded public key>",
    "signature": "<base64-encoded signature>"
  }
}

PR now exists: #39

Oh cool! The examples remind me of Golda's and others' whitepaper on Linked Trust Credentials, https://github.com/WebOfTrustInfo/rwot11-the-hague/blob/master/final-documents/composable-credentials.md (she was also dealing with web archive attestations etc).

credentialSubject can be an array of objects

While technically true, I don't think any existing VC implementations use more than one credentialSubject.

But proof cannot, so you can't hold the proof for each attestation

So interestingly enough, proof CAN be an array of objects. But the proofs are for the overall VC "envelope", and not for individual attestations inside credentialSubject.
If you're doing that, it probably makes sense to /embed/ smaller VCs inside a larger VC (this is a pattern that CLRv2 (Comprehensive Learner Record) follows, for example).

Also the top-level id refers to the specific attestation and can't be an array

Yeah, the top level id (optional) refers to the whole VC (again, the envelope), not individual claims/attestations. But there's nothing stopping the attestations from having their own IDs!

The solution (if this is needed) is to create a VerifiablePresentation instead, or a bespoke thing like a simple array of VC objects

Yeah, agreed! These are the way to go. Either embed full (if minimal) VCs in a larger object (like an outer VC or a VP), OR have an array of claims/attestations in credentialSubject. (and I'm happy to chat more about when to do which one)


Parallax does not work in swiper element.

Hello,
I am working on a project where I require swiper with parallax.I am using swiper element.I also checked out swiper element demo for parallax. In demo image is not sliding. parallax is working properly in vue & react demo.but is not working in element demo.Here is a link for swiper element demo: https://codesandbox.io/p/sandbox/swiper-parallax-forked-j6jpnf?file=%2Findex.html%3A11%2C7
Is there any mistake with implementation or this is a bug ??
Originally posted by @DeepKumbhare85 in https://github.com/nolimits4web/swiper/discussions/6906

You already have the answer in that discussion


Add rc segment to display the actual return code of the last command

This works as addition to the root segment.

Hey @lazyfrosch, thanks for contributing! Someone opened a pull request for this functionality before you though. See https://github.com/milkbikis/powerline-shell/pull/129


segmentation fault on Context.run() with no queries

The following python script produces a segmentation fault with libgetdns 0.2.0 and python-getdns 0.3.1:
#!/usr/bin/env python
import getdns
ctx = getdns.Context()
ctx.run()

Added a null pointer check to context_run(), in the develop branch.  Please confirm that it works correctly for you.

On Wed 2015-06-17 11:58:25 -0400, Melinda Shore wrote:

Added a null pointer check to context_run(), in the develop branch.  Please confirm that it works correctly for you.

Yep, 5e45f2ace0e515a172706fb94fdebd71fefd6e01 fixes the problem for me.
Attached is a backport of it against 0.3.1.
Thanks,
    --dkg


README.md: clarify that Lima is similar to WSL2 but not similar to WSL1

@AkihiroSuda : I learned that WSL2 is more similar to something like LXD, I think it runs a single shared Hyper-V VM and then does "system containers" for the distributions ? So while it is still more similar to WSL2 than WSL1, not sure "equivalent" - maybe "similar to" ?

Thanks, updated the wording


Unicode and Traling spaces parsing issue, multilines compressed into 1 line

There might be an issue with the generate/parsing of Unicode characters and trailing spaces inside multiline sections, for example:
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: name
  source:
    repoURL: https://yourChart
    chart: chartName
    plugin:
      env:
        - name: HELM_VALUES
          value: |
            test1: 'test1'
            test2: test2

Produces (Correctly)
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: name
  source:
    chart: chartName
    plugin:
      env:
      - name: HELM_VALUES
        value: |
          test1: test1
          test2: test2
    repoURL: https://yourChart

while
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: name
  source:
    repoURL: https://yourChart
    chart: chartName
    plugin:
      env:
        - name: HELM_VALUES
          value: |
            test1: 'test2🍀'
            test2: test2

Produces (Wrongly, due to an Unicode inside the multiline section)
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: name
  source:
    chart: chartName
    plugin:
      env:
      - name: HELM_VALUES
        value: "test1: test2\U0001F340\ntest2: test2\n"
    repoURL: https://yourChart

and
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: name
  source:
    repoURL: https://yourChart
    chart: chartName
    plugin:
      env:
        - name: HELM_VALUES
          value: |
            test1: 'test2 '
            test2: test2

Produces (Wrongly, due to a trailing space inside the multiline section )
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: name
  source:
    chart: chartName
    plugin:
      env:
      - name: HELM_VALUES
        value: "test1: test2\U0001F340\ntest2: test2\n"
    repoURL: https://yourChart

So, multilines get compressed into a single line.
A workaround is to filter out them before the generate/parsing command applies:
... | sed 's/[^\x00-\x7F]//g' | sed 's/[ \t]*$//' | argocd-vault-plugin generate -
What is the cause of this issue ? can it be fixed ?
Thanks

Another way to reproduce the error is by updating the tests files

Update "input/nonempty/deployment.yaml" with the following "env" values and update "output/all.yaml"
env:

name: HELM_VALUES
value: |
test1: "test2🍀"

Run test

the rendered manifest, see below, is not aligned with the expected result:
env:

name: HELM_VALUES
value: "test: "\U0001F340"\n"


Specifying the use of the key variable for Serverside objects in the documentation

I have created a Flask and dash app that uses dash components, including the ServersideOutputTransform, to cache and store large dictionaries of arrays. The component works very well for my requirements.
I recently discovered that specifying the same key string for Serverside objects in different callbacks allows the transform to overwrite the previous pickle files in the specified backend directory. Previously, without any unique key, the transform would create a new pickled object, and this would cause a lot of duplicate data writing to the temporary cache, as well as cause the temporary cache to become populated very quickly with many pickle files.
I would suggest explicitly explaining in the documentation how the key parameter for Serverside objects works, as this can save a great deal of disk space when Serverside objects are constantly being updated from different callbacks. Now, when using a unique key, I can drastically reduce the amount of disk space required for my Serverside objects in session.

I have added the following paragraph to the docs,
Keys
Per default, the Serverside object ge nerates a new unique key for every callback invocation to ensure that data is never shared between invocations and/or sessions. However, if this is not a requirement, using a fixed key will reduce the data usage of the cache significantly, as only one copy of the data will be stored (instead of one per callback invocation).


fix matcher metric and warning

Issue #, if available:
Description of changes:

Support using recall, precision, and mrr as eval_metric in matcher.
Remove one lightning deprecation warning.
Remove the validation step before the fit to make tutorial clean.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

LGTM! Thanks.


Quick Start page

I'm thinking "What is" and "Quick Start" pages would be nice for folks new to Hypha. (see example What Is and Quick Start pages for Gitbook)
QUESTIONS:

There is an "Initial page" that could serve as the basis for the "What Is" page, but it could use some editing/polishing.  @danblah, okay if I make some proposed changes to the page?
Do folks think a "Quick Start" page would be useful?  What priority level would this be (relative to, say, improving existing user documentation or creating non-existent documentation)?

I do think a "Quick Start" page is useful. And I'd guess it would actually be a nice start to the user documentation - so you might even start with it, and then that will possibly support the more in-depth docs?

I think a Quick start page is an excellent idea.

Page created!

Hypha overview page here
Getting started for Staff page here


Add a debug log entry for proof generation hints (second try)

This is the resurrected version of #2636.
This PR tries to add 4 (debug) log entries:

DebugInitialClaim which records the input claim to be proved
DebugInitialPattern which records the initial pattern when trying to prove each claim
DebugFinalPatterns which records the final patterns when each claim is proven
DebugRewriteTrace which records each rewriting step performed on the current configuration during the proof

They are all defined in kore/src/Kore/Log/DebugRewriteTrace.hs.
These entries are disabled by default, and only enabled with the new flag --trace-rewrites <output>.
With this flag, kore will write all of these four entries into a YAML-format file <output>.
For example, when doing a reachability proof, the output YAML file will look something like this
---
claim-id: <UNIQUE'Unds'ID attribute of the claim in kore, if it exists>
claim: <a string with the claim encoded in Kore>
task: reachability
steps:
- initial: { term: ..., constraint: ..., substitution: ... } # the term which the rules are applied to
  applied-rules:
  - rule-id: <UNIQUE'Unds'ID attribute of the rule applied>
    substitution: [ { key: <Kore variable>, value: <Kore term> }, ... ]
    results: [ { term: ..., constraint: ..., substitution: ... }, ... ]
  remainders: <remainder terms when some rule is applied>
- ...

# there could be another claim
---
claim-id: ...
...

Review checklist
The author performs the actions on the checklist. The reviewer evaluates the work and checks the boxes as they are completed.

[x] Summary. Write a summary of the changes. Explain what you did to fix the issue, and why you did it. Present the changes in a logical order. Instead of writing a summary in the pull request, you may push a clean Git history.
[ ] Documentation. Write documentation for new functions. Update documentation for functions that changed, or complete documentation where it is missing.
[ ] Tests. Write unit tests for every change. Write the unit tests that were missing before the changes. Include any examples from the reported issue as integration tests.
[ ] Clean up. The changes are already clean. Clean up anything near the changes that you noticed while working. This does not mean only spatially near the changes, but logically near: any code that interacts with the changes!

these changes have been merged into the latest master in this PR:  #3284


rocfft examples fail on Radeon VII - rocfft 3.5.0

description
I was trying to convert my CUDA code to ROCm. After I had segmentation faults in the FFTs, I tried the examples provided by rocfft which also failed. I mostly tested with this since my original code also needs 3d FFTs.
compiling
hipcc -g -c hipfft_3d_z2z.cpp -o hipfft_3d_z2z.o -I/opt/rocm/include
hipcc -g --amdgpu-target=gfx906 -o hipfft_3d_z2z hipfft_3d_z2z.o -L/opt/rocm/lib -lrocfft

This works without issues or messages.
execution
./hipfft_3d_z2z
hipfft 3D double-precision complex-to-complex transform
input:
(0,0) (10,0) (20,0) (30,0)
(0,1) (10,1) (20,1) (30,1)
(0,2) (10,2) (20,2) (30,2)
(0,3) (10,3) (20,3) (30,3)

(1,0) (11,0) (21,0) (31,0)
(1,1) (11,1) (21,1) (31,1)
(1,2) (11,2) (21,2) (31,2)
(1,3) (11,3) (21,3) (31,3)

(2,0) (12,0) (22,0) (32,0)
(2,1) (12,1) (22,1) (32,1)
(2,2) (12,2) (22,2) (32,2)
(2,3) (12,3) (22,3) (32,3)

(3,0) (13,0) (23,0) (33,0)
(3,1) (13,1) (23,1) (33,1)
(3,2) (13,2) (23,2) (33,2)
(3,3) (13,3) (23,3) (33,3)

[1]    2457 segmentation fault (core dumped)  ./hipfft_3d_z2z

It's failing at hipfftExecZ2Z().
debug
When I try to debug, I'm getting this:
/opt/rocm/bin/rocgdb ./hipfft_3d_z2z
GNU gdb (GDB) 9.1
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./hipfft_3d_z2z...
(gdb) run
Starting program: /home/tinux/dev/cpp/ROCm/fft/hipfft_3d_z2z
warning: The version of the kernel driver does not match the version required by the ROCm debugger library
warning: Could not attach to process 2612
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
hipfft 3D double-precision complex-to-complex transform
[New Thread 0x7fffef53d700 (LWP 2616)]
[New Thread 0x7fffed1ff700 (LWP 2617)]
[Thread 0x7fffed1ff700 (LWP 2617) exited]
[New Thread 0x7fffed77f700 (LWP 2618)]
input:
(0,0) (10,0) (20,0) (30,0)
(0,1) (10,1) (20,1) (30,1)
(0,2) (10,2) (20,2) (30,2)
(0,3) (10,3) (20,3) (30,3)

(1,0) (11,0) (21,0) (31,0)
(1,1) (11,1) (21,1) (31,1)
(1,2) (11,2) (21,2) (31,2)
(1,3) (11,3) (21,3) (31,3)

(2,0) (12,0) (22,0) (32,0)
(2,1) (12,1) (22,1) (32,1)
(2,2) (12,2) (22,2) (32,2)
(2,3) (12,3) (22,3) (32,3)

(3,0) (13,0) (23,0) (33,0)
(3,1) (13,1) (23,1) (33,1)
(3,2) (13,2) (23,2) (33,2)
(3,3) (13,3) (23,3) (33,3)

Thread 1 "hipfft_3d_z2z" received signal SIGSEGV, Segmentation fault.
0x00007ffff7c6ee21 in ?? () from /opt/rocm/hip/lib/libamdhip64.so.3
(gdb) backtrace
#0  0x00007ffff7c6ee21 in ?? () from /opt/rocm/hip/lib/libamdhip64.so.3
#1  0x00007ffff7c76985 in hipLaunchKernel () from /opt/rocm/hip/lib/libamdhip64.so.3
#2  0x00007fffef8e33fd in rocfft_internal_dfn_dp_ci_ci_stoc_4 () from /opt/rocm/lib/librocfft-device.so.0
#3  0x00007ffff7e06fbf in ?? () from /opt/rocm/lib/librocfft.so.0
#4  0x00007ffff7e00b22 in rocfft_execute () from /opt/rocm/lib/librocfft.so.0
#5  0x00007ffff7e03393 in hipfftExecZ2Z () from /opt/rocm/lib/librocfft.so.0
#6  0x0000000000401878 in main () at hipfft_3d_z2z.cpp:106

system

arch linux
kernel 5.7.2-arch1-1

hardware

GPU
AMD Radeon VII (Vega20)

CPU
AMD Ryzen 5 3600X

Software
version

ROCK
v3.5.0

ROCR
v3.5.0

HIPHCC-ROCCLR
v3.5.0

ROCFFT
v3.5.0

other things I have tried
I also stumbled over #224 and therefore tried the mentioned docs/samples/complex_1d.cpp, but I also got a segmentation fault.
I have no idea what else to try atm. Any ideas?

Arch Linux is not on the supported OS list of ROCm.
https://github.com/RadeonOpenCompute/ROCm#Supported-Operating-Systems-and-Documentation-Updates

@t1nux , can you provide the output of pacman -Q, so I can confirm exactly what packages you have installed?
And are you able to launch any kernels?  i.e. if you build a test program like:
#include <hip/hip_runtime.h>

__global__ void kernelfunc(float *x) { *x = 12345.6789; }

int main() {
  float x = 0.0;
  float *x_dev = nullptr;
  hipMalloc(&x_dev, sizeof(float));
  hipMemcpy(x_dev, &x, sizeof(float), hipMemcpyHostToDevice);
  hipLaunchKernelGGL(kernelfunc, 1, 1, 0, 0, x_dev);
  hipMemcpy(&x, x_dev, sizeof(float), hipMemcpyDeviceToHost);
  printf("%0.5f\n", x);
  return 0;
}

does it print something close to 12345.6789, or does it also crash?  That would help indicate whether the problem is in rocfft.

@feizheng10, thanks for your reply. I know arch is not supported, but on the freenode ROCm channel, other people were also unable to run the examples. Can you?
@evetsso Thanks for your reply too.
pacman -Q gives a long list, which you can look at here.
The example you posted compiles and runs fine, however the output is 12345.67871. I used this to compile:
hipcc -g --amdgpu-target=gfx906 -o test test.o
hipcc -g --amdgpu-target=gfx906 -o test.o -c test.cpp

@t1nux , in our local Ubuntu or CentOS env, the sample code runs well.
It will be helpful if you could provide more details on freenode ROCm channel.
Some other thoughts:
(1) Could you try ROCm docker image on top of your system?
(2) Is it work with ROCm 3.3 on your env?

@feizheng10, it's working on ubuntu 20.04. I apologize for the faulty report and wasting your time! Thanks you for your help! I'm closing this.
Some more feedback (probably more for arch people). First, I tried to test with docker which gave me problems all over the place. I got the feeling it was related to rock-dkms and I started to look into this. I found that rock-dkms-3.5 (simple adaptation of the 3.3 PKGBUILD which is now broken due to missing sources) was not working, due to this:
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Install DKMS modules
==> dkms install --no-depmod -m amdgpu-3.5 -v 30 -k 5.7.3-arch1-1
cp: cannot stat '/usr/src/amdgpu-3.5-30/firmware/amdgpu': No such file or directory
Error! Bad return status for module build on kernel: 5.7.3-arch1-1 (x86_64)
Consult /var/lib/dkms/amdgpu-3.5/30/build/make.log for more information.
==> Warning, `dkms install --no-depmod -m amdgpu-3.5 -v 30 -k 5.7.3-arch1-1' returned 10

However, trying rock-dkms-bin-3.5, which did work to install, made X not start at all.
So, in my naive view, it seems simple code does not to require rock-dkms at all (super simple examples like vectoradd_hip.cpp, or the one posted by evetsso), and rocfft does. Is this true?
@evetsso, thank you for your help as well! I guess you're on arch too?!? Should I post this on rocm-arch?

I do use Arch for other things, but not ROCm since it's not one of the supported distros. :)
But since things do appear to work in Ubuntu, it's plausible that this problem is introduced by something in rocm-arch, and it would be better to report the issue there.

@t1nux, no problem!
For your question, technically, no big build difference between a simple code and rocFFT.
Still, both need rocm-dkms and runtime lib support. The complicated part would be rocFFT build has more target build and link options involved, which might cause issue from the dependency.
I hope the oncoming hip-clang improvement could make your work on ROCm more easy and smooth!


feat: base provider

Feels like these props are passed to components which shouldn't be needed anymore? Are you starting to use the provider in the next PR?

sorry wrong button

Feels like these props are passed to components which shouldn't be needed anymore? Are you starting to use the provider in the next PR?

Yes. Two new PR:s are coming after this one.
First which enabled the header menu selections. It's using the app, model and interactions on a component cell level. So lots of prop drilling there.
Second is a refactoring where constraints is replace with interactions. Which affects the DimensionCell component an all it's parent components.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Thread can outilve the main state

This code takes segfault:
extern crate lua;
use lua::*;
fn main() {
    let mut thread = {
        let mut state = State::new();
        state.new_thread()
    };
    thread.do_string(r#"print("Hello, segfault!")"#);
}

Output:
$ cargo run
    Finished debug [unoptimized + debuginfo] target(s) in 0.0 secs
     Running `target\debug\lua-fail.exe`
error: Process didn't exit successfully: `target\debug\lua-fail.exe` (exit code:<PHONE_NUMBER>)
Segmentation fault

This was found with #65.

I experimented a bit with how to solve this issue conceptually. IMO, the cleanest solution is a separate Context type which is responsible for lua_openstate and lua_close, and from which a main State (which would correspond to Lua threads) can be obtained. State would need either a lifetime parameter or to be hidden behind a reference(*) which restricts it to exist no longer than the Context does.
Further, new_thread and to_thread would need to return some sort of guard which pins the Lua-side value (probably in the registry) so that it is not garbage collected by Lua; otherwise, even if the original Context still exists, the specific thread may have been destroyed.
(*) If T is zero-sized, it's legal to produce arbitrary &T and &mut T in unsafe code, since dereferencing them does nothing. Therefore we could produce a &State whose pointer is actually the lua_State. This is needed if we want Context to be able to Deref to State (so State methods can be called on Context directly), but not really important if that ability is not desired.
I have some of this stuff implemented in an experimental branch but it's a little messy; if I know which parts are important I can pick them out into PRs.

It should also be noted that lua_newthread pushes the thread on the stack, but there seems to be no code that pops that value, potentially leading to unbounded stack growth.


⚠ ClamAV has degraded performance

In 83ccc02, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 67 ms

Resolved: ClamAV performance has improved in 5829493.


fix: when osd device is a disk partition

when osd devices is a disk partition, ceph-disk zap "{{ item }}" will not work.
Check the osd device type first, is the osd device is a raw device, using ceph-disk, else using sgdisk

@guits please review

jenkins test jewel-ansible2.2-purge_docker_cluster


Update swizzleAllowedComponents

🐛 Bug Report
The template doesn't really apply, but this issue is just a quick notice that the swizzleAllowedComponents in theme-classic hasn't been updated for long. A lot of small components should be swizzlable without the --danger flag.
Some components that almost certainly should be added:

BackToTopButton;
Details;
EditThisPage;
IconExternalLink;
IconLanguage;
...

Yes, agree.
I'll update this list once I add the "slots/placeholders component" that I mentioned in another issue.
If you want to update it, feel free to submit a PR. As a general rule I'd say we should mark swizzle as not dangerous as long as the comp is purely UI-related, with a small and clean API (props/context usage) and does not contain complicated complex Docusaurus login. (DocSidebar should rather be moved to --danger for example)


Bug: List/ListItem Nodes From DOM results in invalid editor state

I'm working on parsing HTML (from a headless editor) and converting it as the initial state for an editor. I'm getting what looks like a valid json obj back, but providing that value to the editor is giving me a Cannot call set() on a frozen Lexical node map error, thrown by the ListItemNode. I'm comparing what result I get from this process to the value I get from pasting the same html into an editor, and they look real similar, with small exceptions being the format and direction keys of some of the values.
Any ideas here? Maybe a bug with the headless editor? This only happens with the list/listitem nodes. Everything else seems to parse pretty smoothly.
Here's the full stack trace:
Lexical.dev.js:5445 Uncaught Error: Cannot call set() on a frozen Lexical node map
    at nodeMap.set (Lexical.dev.js:5445:1)
    at ListItemNode.getWritable (Lexical.dev.js:6257:1)
    at ListItemNode.setValue (LexicalList.dev.js:657:1)
    at updateChildrenListItemValue (LexicalList.dev.js:279:1)
    at ListItemNode.createDOM (LexicalList.dev.js:473:1)
    at createNode (Lexical.dev.js:1690:1)
    at createChildren (Lexical.dev.js:1772:1)
    at createChildrenWithDirection (Lexical.dev.js:1763:1)
    at createNode (Lexical.dev.js:1710:1)
    at createChildren (Lexical.dev.js:1772:1)

Lexical version: 0.8.1
Steps To Reproduce

See example code below

Link to code example:
Here's a brief example of the process for debug purposes:
  const editor = createHeadlessEditor({
    nodes: [
      AutoLinkNode,
      HeadingNode,
      LinkNode,
      ListNode,
      ListItemNode
    ],
  });

  editor.update(() => {
    const dom = new JSDOM(htmlString);

    const nodes = $generateNodesFromDOM(editor, dom.window.document);
    const root = $getRoot();

    nodes.forEach((node) => {
      root.append(node);
    });
  });

  editor.registerUpdateListener(({ editorState }) => {
    editorState.read(() => {
      const lexicalStructure = JSON.stringify(editorState);
      // save to a db for later use
    });
  });

The current behavior
Returns a stringified state object that looks correct, but breaks when passed to an editor as initial state.
The expected behavior
It works :)

What happens if you set editable: true in the createHeadlessEditor config object? Although, that should be true by default.

What happens if you set editable: true in the createHeadlessEditor config object? Although, that should be true by default.

Yeah, no luck there 😔

I think @thegreatercurve might be close to something, though. Not sure if it's a build issue or there's something else going on, but it looks like the issue is definitely related to the handleDEVOnlyPendingUpdateGuarantees function which is still being called. For instance looking at this guy  in my actual node modules is getting built like this:
    // Make the editorState immutable
    editorState._readOnly = true;
    {
	handleDEVOnlyPendingUpdateGuarantees(editorState);
    }

Without the DEV check. This is in my local environment, but I also ran with a prod build and it's still getting called just to weed out that as a possibility. Is the dev check failing or is there some other build stage thats causing this to be called when it shouldn't be?

I think @thegreatercurve might be close to something, though. Not sure if it's a build issue or there's something else going on, but it looks like the issue is definitely related to the handleDEVOnlyPendingUpdateGuarantees function which is still being called. For instance looking at this guy in my actual node modules is getting built like this:
    // Make the editorState immutable
    editorState._readOnly = true;
    {
	handleDEVOnlyPendingUpdateGuarantees(editorState);
    }

Without the DEV check. This is in my local environment, but I also ran with a prod build and it's still getting called just to weed out that as a possibility. Is the dev check failing or is there some other build stage thats causing this to be called when it shouldn't be?

Update: Found the reasoning... the published package still runs in dev mode based on the actual NODE_ENV running process, not on the actual build script which is what I had originally thought:
const Lexical = process.env.NODE_ENV === 'development' ? require('./Lexical.dev.js') : require('./Lexical.prod.js')

Running my server in prod mode bypasses this issue, but I'm wondering if this should be intended? Forgive my ignorance, but isn't a published NPM package considered "production" and should be treated as such when running in a project, regardless of its own environment? I'm going to have to run our app in prod mode every time moving forward with this now, which is kind of annoying. Any thoughts here?

I have this similar issue when using lists (ListNodes & ListItemNodes) along with createEditor function.

I am also having similar issue, @brianbolnick thanks for reporting it.

Running my server in prod mode bypasses this issue, but I'm wondering if this should be intended? Forgive my ignorance, but isn't a published NPM package considered "production" and should be treated as such when running in a project, regardless of its own environment? I'm going to have to run our app in prod mode every time moving forward with this now, which is kind of annoying. Any thoughts here?

I think the DEV/PROD behavior is as intended, but that means there's probably a bug. Lexical throws these errors in DEV so you can catch them before sending them out to users. You should only be running the app in "PROD" when you would otherwise/normally do so.
I don't see in your code where you're creating the editor with the the state after parsing it from HTML? Is the error being thrown in the update callback in your code above?


Implemented Select Network to enable switching between different deployed Networks

Description
Implemented the ability to select different networks a Dapp is deployed to, so users can easily switch between different networks

Specify the networks the Dapp is deployed to in ~~/services/web3/wagmiConnectors.tsx

When burner wallet is the wallet in use, select network component is hidden

Additional Information

Created scaffoldConfigContext and provider
Refactored/created the following files to use hook from context: -

Created SelectNetwork.tsx
Created SwitchNetwork.tsx
Created AddressQRCodeModal.tsx
Created AddressInfoDropdown.tsx
Refactored RainbowKitCustomConnectButton.tsx
Refactored WriteOnlyFunctionForm.tsx to use configuredNetwork instead of getTargetNetwork()
Refactored useDeployedContractInfo.ts to use configuredNetwork instead of getTargetNetwork()
Refactored useScaffoldEventSubscriber.ts to use configuredNetwork instead of getTargetNetwork()
Refactored useScaffoldContractRead.ts to use configuredNetwork instead of getTargetNetwork()
Refactored useScaffoldContractWrite.ts to use configuredNetwork instead of getTargetNetwork()
Refactored useAccountBalance.ts to use configuredNetwork instead of getTargetNetwork()
Refactored Balance.tsx to use configuredNetwork instead of getTargetNetwork()
Refactored ContractUI.tsx to use configuredNetwork instead of getTargetNetwork()
Added ScaffoldConfigProvider to _app.tsx
Refactored wagmiConnectors.tsx to use configuredNetwork instead of getTargetNetwork()
Refactored useNetworkColor.ts to use configuredNetwork instead of getTargetNetwork()

@carletex, could you please review this pull request?

[x] I have read the contributing docs (if this is your first contribution)
[x] This is not a duplicate of any existing pull request

Related Issues
Closes #599
Note: If your changes are small and straightforward, you may skip the creation of an issue beforehand and remove this section. However, for medium-to-large changes, it is recommended to have an open issue for discussion and approval prior to submitting a pull request.
Your ENS/address: dannithomx.eth

Hey @blahkheart
Thanks for your contribution! It appears, however, that we might have been working a bit in parallel on this issue. I picked it up 5 days ago when I saw no comments on the issue and no assignee, so I didn't know you were interested in looking into it as well.
Since this approach doesn't appear to be compatible with the burner wallet, I think my solution is preferable. I'll leave this open for others reviewers for now, it's always possible I overlooked something in my PR.
For future reference, to avoid similar situations, best to leave a comment on an issue if you'd like to be assigned to it so others know it's being worked on. Again sorry for this.

Hey @blahkheart Thanks for your contribution! It appears, however, that we might have been working a bit in parallel on this issue. I picked it up 5 days ago when I saw no comments on the issue and no assignee, so I didn't know you were interested in looking into it as well.
Since this approach doesn't appear to be compatible with the burner wallet, I think my approach is slightly preferable. I'll leave this open for others reviewers for now, it's always possible I overlooked something in my PR.
For future reference, to avoid similar situations, best to leave a comment on an issue if you'd like to be assigned to it so others know it's being worked on. Again sorry for this.

Thank you @sverps, your feedback on commenting on issues being worked on is well noted and appreciated. Its quite a bummer when things like this happen! Although I had implemented the feature a while ago on one of my builds which I demoed on a BTF some time ago and had a chat with @carletex  about it because it had been in discussion here. I was about to start the process of creating the PR when I got sick and have been out for some time getting treatment. I just fully recovered and went straight back to get it done.
For your note on the burner wallet, it is compatible with my approach, I only included the UI logic to hide the selectNetwork component when on hardhat because the burner wallet is set to only work for localhost in the config file so it made sense to leave it out for live networks. However its something I can easily reverse if it was need.

Hey I looked a bit further into your PR and did find a couple of things that would be a nice addition (such as refactoring some stuff into separate components, the context might work a bit better in some scenario's than just a fleeting useState I used).
I'll have a further look at it tomorrow to see if that can be included in some way with proper attribution. I'll try to merge our branches. We do value all contributions! (and it's always nice to see your name in the list of contributors)

Thanks @sverps That's really chad or you!! And yeah, you are right our approaches isn't all that different.


⚠ Samsung has degraded performance

In 350fd27, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2505 ms

Resolved: Samsung performance has improved in 4bbadde.


Issue with isCreated method

Hi,
There is an issue in isCreated method :
var _isCreated = function(selector) {
       var created = true;
       $(selector).each(function(item) {
              created = created && $(item).data('plugin_' + pluginName) !== undefined;
       });
       return created;
};

"item" can't be transformed as a jQuery object because it's an index.
Can you fix it by using $(this).data(...) inside each loop ? Thx

Oh, I found it. This problem will be fixed soon!
Thank you for helping me figure this out.

This issue is  fixed.


XML documentation file is missing in the NuGet package

Some of the public API has XML documentation comments, but the NuGet package doesn't come with an XML documentation file.
Can you add the file to the NuGet package?

Just added commit 25c88251b756afcb0df40a30976ffe49251a3cc0 to ensure the doc comments are built and included in the package.
I'm not yet at a point where I'm ready to release another version to NuGet, though, but if you clone/build locally you'll now get IxMilia.Dxf.xml placed in the appropriate output directory.


TimePicker SelectedTime

TimePicker should have a property for time-only values (as the name of the control)
TimePicke use a SelectedDateTime property for selected value which use a DateTime?, this is pretty funny because for this kind of value we can user DatePicker (which can show the time part), for time property there's a TimeSpan so why (in an approved PR) you changed this behavior?
In .net Time are represented by TimeSpan, if you wan't break current implementation please add a SelectedTime property to use the correct data type instead of using a converter.

Hi @amellini
this control is meant to select a time of the day which is different from selecting a TimeSpan. A TimeSpan can also be about a longer period. There is another feature request open for a TimeSpan-Control: #3718
Happy coding
Tim

I dont fully agree, TimeSpan in used to represent a time interval (TimeSpan) but "DateTime.Now.TimeOfDay" return a TimeSpan, so its used to represent a generic time of a generic day (not a specific as requested by a DateTime structure).
I think that creating a new usercontrol specific for this kind of data instead using an existing (note that TimePicker is different from DateTimePicker so i expect a generic Time not a specific Time of a specific Day) will be confusing.

Fully agree with the author. Moreover, in version 1.6.5 TimeSpan was used for the SelectedTime property and I don't see a reason why DateTime should be used if the control only allows to work with Time what implies using TimeSpan instead of DateTime.


Update to work with almost-standard leveldb 1.22.

Remove support for suspend and resume compaction as it requires a modified leveldb.
Add leveldb and snappy as submodules so exact versions are specified.
Fix build on OSX.

Sorry, this isn't anywhere near ready to merge - was intending to create the PR just in my own fork as an easy way to point people to it.


feat(login): create login component from login demo and login-box component

fixes https://github.com/patternfly/patternfly-next/issues/928
fixes https://github.com/patternfly/patternfly-next/issues/895
fixes https://github.com/patternfly/patternfly-next/issues/824

In combining the component and demo, I was able to simplify the markup structure a little
I added other components needed in this component to the documentation. Is that a good idea?
Reworked the "login" button and "keep me logged in" text alignment to match designs
Putting everything into this component as we would ship it, and using the demo text instead of dummy text. Is this OK? Adding .pf-c-background-image to this component, for example, implies we might go back and update .pf-c-modal-box and .pf-c-about-modal-box, remove -box from the component names, and add the .pf-l-bullseye, .pf-c-backdrop, and whatever else is in those components' demos.

Deploy preview for pf-next ready!
Built with commit 4caf8908dae208a2ee83b043b87c176f68937806
https://deploy-preview-964--pf-next.netlify.com

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Cookie authentication overrides Cache-Control, Pragma & Expires headers

https://github.com/aspnet/Security/blob/e0ad6ed6b9abbb73e3ca68c6abdf2a0126defec1/src/Microsoft.AspNetCore.Authentication.Cookies/CookieAuthenticationHandler.cs#L360-L362
This overrides values that may have already been set to some specific values in other middleware (for example, Web API).
For instance, in my app that is vitally important to have "Cache-Control" to be set to this: "no-store, no-cache, must-revalidate", but when sliding expiration happens, this value gets overwritten by this middleware to just "no-cache"

This is by design. Responses with auth cookies must not be cached.
Also, WebAPIs should not be using cookie auth. JWT Bearer would be more appropriate.

no-cache implies must-revalidate by making the response immediately stale. This is not a case of "just", it's an upgrade from a security POV.

Thank you for your quick replies. I very appreciate it.
I actually understand the thing about no-cache & must-revalidate but for some reasons (not known to me), the INetCache thing in Windows sometimes caches those results that don't have "must-revalidate" in the Cache-Control header... That is the only reason why it was decided to specify one more option in Cache-Control header...
This Web API is used by a WPF app. This app communicates with the web service using the HttpClient class:
`var webRequestHandler = new WebRequestHandler()
{
UseCookies = true,
CookieContainer = _cookieContainer,
CachePolicy = new RequestCachePolicy(RequestCacheLevel.Default)
};
        _httpClient = new HttpClient(webRequestHandler)
        {
            BaseAddress = baseUrl
        };`

The auth cookie is stored in the app's memory until it is closed. To talk to the Web API, only one instance of HttpClient class is used; and this instance holds the auth token that has been issued during signing in into this WPF app.
Those HTTP responses that should be cached are returned from the Web API to the WPF app with these headers specified (Cache-Control, Pragma, Expires).

Interesting. I wonder if it would work if we were setting the right Expires value. https://github.com/aspnet/Security/issues/1353

I think I may have found the reason of such a behavior...
I am using:

ASP.NET 4.6
Cookie Authentication from Microsoft.Owin.Security.Cookies

I noticed that every time when cookie slides (sliding expiration is turned on), the HttpClient in the WPF app receives a response from the server which contains "Set-Cookie" header + "Cache-Control: private".
It is PRIVATE for some reason! And I am confused why it is so...
I cannot find any extension point neither in ASP.NET nor in OWIN so that I could change "Cache-Control" from PRIVATE to different value (I guess, to "no-cache" value).
Is it expected behavior that the response that contains "Set-Cookie" header has "Cache-Control" set to PRIVATE? To my understanding, it is a bug... Or, I doubt, but maybe something is not configured appropriately in the web service?
Thank you.

The Microsoft.Owin version set the same headers.
https://github.com/aspnet/AspNetKatana/blob/a4ad9a82cde44ac27242a2d23238aada2ec5b4be/src/Microsoft.Owin.Security.Cookies/CookieAuthenticationHandler.cs#L275-L285
There is no private set here. It's possible the header is being overwritten by a separate part of the application.

Tratcher, you were right.
I found that the Web API project uses the SystemWebCookieManager class from http://katanaproject.codeplex.com/wikipage?title=System.Web response cookie integration issues
    public partial class Startup
    {
        public void ConfigureAuth(IAppBuilder app, TimeSpan expirationInMins, bool slidingExpiration)
        {
            app.UseCookieAuthentication(new CookieAuthenticationOptions()
            {
                AuthenticationMode = AuthenticationMode.Active,
                AuthenticationType = DefaultAuthenticationTypes.ApplicationCookie,
                CookieHttpOnly = true,
                CookieSecure = CookieSecureOption.SameAsRequest,
                ExpireTimeSpan = expirationInMins,
                SlidingExpiration = slidingExpiration,
                **CookieManager = new SystemWebCookieManager()**
            }
        }
    }

So, it seems like it may not be enough to use the code from the link above as it is. After I added the following lines to the end of the AppendResponseCookie method, everything began to work. I mean, the "Cache-Control: private" thing is no longer sent in the response when the "Set-Cookie" header is present:
var cache = webContext.Response.Cache;
cache.SetCacheability(HttpCacheability.NoCache);
webContext.Response.AppendHeader("Pragma", "no-cache");
cache.SetExpires(new DateTime(1970, 1, 1, 0, 0, 0, DateTimeKind.Utc));

Interesting, it looks like some of the caching headers are subject to the same System.Web collision issues as the cookies but the symptoms are a lot more subtle so nobody has ever reported it.

Tratcher, you were right.
I found that the Web API project uses the SystemWebCookieManager class from http://katanaproject.codeplex.com/wikipage?title=System.Web response cookie integration issues
    public partial class Startup
    {
        public void ConfigureAuth(IAppBuilder app, TimeSpan expirationInMins, bool slidingExpiration)
        {
            // Enable the application to use a cookie to store information for the signed in user
            app.UseCookieAuthentication(new CookieAuthenticationOptions()
            {
                AuthenticationMode = AuthenticationMode.Active,
                AuthenticationType = DefaultAuthenticationTypes.ApplicationCookie,
                CookieHttpOnly = true,
                CookieSecure = CookieSecureOption.SameAsRequest,
                ExpireTimeSpan = expirationInMins,
                SlidingExpiration = slidingExpiration,
                CookieManager = new SystemWebCookieManager()
            }
        }

It seems it is not enough to use the code from the link above as it is. After I added the following lines to the end of the AppendResponseCookie method, everything began to work:
            var cache = webContext.Response.Cache;
            cache.SetCacheability(HttpCacheability.NoCache);
            cache.SetExpires(new DateTime(1970, 1, 1, 0, 0, 0, DateTimeKind.Utc));
            webContext.Response.AppendHeader("Pragma", "no-cache");


Noncorrect value for get() when adding zero time periods

Code:
import 'sequence.lua'

local sequence = sequence.new():from(10):to(20, 1):to(10, 0)
print(sequence:get(1))

Expected result:
10.0
Actual result:
20.0
Fixed by: https://github.com/NicMagnier/PlaydateSequence/pull/11

Fixed.


Better grammar in readme

Thanks for correcting my grammatical issues. And I think it is your first time contributing, Congrats on your first contribution.


Get rid of "Getting" in titles

I just noticed a handful of lingering "Getting"s around the repo. I'll swing thru and knock them out.

Will be covered by https://github.com/aspnet/Docs/issues/5280.


Plotjuggler --can not looking in dbc folder for dbc files

Describe the bug
When loading a route with plotjuggler, no dbc are shown on the lastest master unless they are copied into the higher level folder for opendbc.
Provide a route where the issue occurs
N/A
openpilot version
master
Additional info
No response

Is this WSL? Make sure the symlink is properly created for opendbc to opendbc_repo/opendbc

Is this WSL? Make sure the symlink is properly created for opendbc to opendbc_repo/opendbc

Ubuntu 20.04 on a VM. If it’s just a me issue I’ll work around it

Also try to update PJ with ./juggle.py --install, this fixed it for incognitojam


ci: Dont run sync wf in non-Envoy repos

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

we could do with a better solution for this that allows workflows to be run in other repos for testing etc
this prevents this newer wf from running consistent with existing workflows

/assign @mum4k


Publish: run custom start logic on Connect

Is there a way to specify additional action to be run when connecting to published observable?
To demonstrate my case imagine the following application:
public sealed class PublishTest
{
    private CancellationTokenSource _cts;

    public event Action<int> Tick;
    public void Start() => Task.Run(() => Generate((_cts = new CancellationTokenSource()).Token));
    public void Stop() { _cts?.Cancel(); }

    private async Task Generate(CancellationToken cancellationToken)
    {
        for (int i = 0; !cancellationToken.IsCancellationRequested; i++)
        {
            Tick?.Invoke(i);
            await Task.Delay(1000, cancellationToken);
        }
    }
}

void Main()
{
    var events = Observable.Defer(() =>
    {
        var p = new PublishTest();
        p.Start();
        return Observable.FromEvent<int>(h => p.Tick += h, h => p.Tick -= h)
                         .Publish()
                         .RefCount();
    });
    events.Dump();
}

Currently the first event will be most certainly missed because ideally p.Start() needs to happen after observers had a change to subscribe - on connect.
It would be very useful to be able to say something like:
return Observable.FromEvent<int>(h => p.Tick += h, h => p.Tick -= h)
                 .Publish(() =>
                 {
                     p.Start();
                     return Disposable.Create(() => p.Stop());
                 })
                 .RefCount();

If I understand correctly, you need to bridge the time window between p.Start and the FromEvent to handle the incoming observer from downstream. This could be done with a so-called UnicastSubject not part of Rx.NET at the moment:
var events = Observable.Defer(() =>
    {
        var p = new PublishTest();

        // us will buffer items until a single observer subscribes,
        // then relays the rest directly
        var us = new UnicastSubject<T>(onTerminate: () => p.Stop());

        // this will link up a receiver (us) for the events before the generator is started
        Observable.FromEvent<int>(h => p.Tick += h, h => p.Tick -= h)
            .Subscribe(us);

        // this is now safe, us will buffer until it gets exposed to the
        // downstream consumer
        p.Start();

        return us;
    })
    .Publish()
    .RefCount();

    events.Dump();

Actually, I realised there is a simpler solution using Observable.Create:
var events = Observable.Create<int>(observer =>
{
    var p = new PublishTest();
    var subscription = Observable.FromEvent<int>(h => p.Tick += h, h => p.Tick -= h)
                                 .Finally(() => p.Stop())
                                 .Subscribe(observer);
    p.Start();
    return subscription;
});


Apply BSD license

It's official! We have a license, and now we can use it.
For https://trello.com/c/cxBJRBkq

Woooo! Chantelle Verhey (she/her) | Research Associate, International Technology OfficeInternational Science Council, World Data System| M<PHONE_NUMBER> | oceannetworks.caUniversity of Victoria — Queenswood Campus — #100-2474 Arbutus Rd Victoria, BC V8N 1V8https://orcid.org/0000-0002-0047-7875 From: Melinda MinchSent: June 3, 2022 1:27 PMTo: nein09/polder-federated-searchCc: Chantelle Verhey; Review requestedSubject: [nein09/polder-federated-search] Apply BSD license (PR #50) It's official! We have a license, and now we can use it.You can view, comment on, or merge this pull request online at:  https://github.com/nein09/polder-federated-search/pull/50Commit Summary2d8f444 Apply BSD licenseb2a6f6c Add license field to package.json and bump versionFile Changes (3 files)A LICENSE (29) M helm/Chart.yaml (2) M package.json (3) Patch Links:https://github.com/nein09/polder-federated-search/pull/50.patchhttps://github.com/nein09/polder-federated-search/pull/50.diff—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because your review was requested.Message ID<EMAIL_ADDRESS>


load issues whose repo has >= 100 stars or forks

…stars >= 100
PR Template 🚀
🐛 Fixed Issue #6
while loading the repo, repos with 0 stars and forks were also been loaded
Issue link: https://github.com/anand346/findissues/issues/6
🛠 Proposed Changes
I made a check on the star and fork on the repo and only added it to the issue list if either of the repo or stars were >= 100
🖼 Screenshots

Checklist ✅

[✅ ] All tests pass successfully.
[✅ ] Code adheres to the project's coding standards.
[ ✅] Documentation is updated to reflect the changes.
[ ✅] No sensitive information is inadvertently exposed.
[ ✅] Commit history is clear and concise.

Hi @KrishavRajSingh , glad to see that you've put your efforts in resolving this issue. Actually the goal is to show 30 issues total on a page but the respective repo of all the issues should not have 0 stars. Star count can be greater than 10 or 20 per repo. Thanks

Hi @KrishavRajSingh , glad to see that you've put your efforts in resolving this issue. Actually the goal is to show 30 issues total on a page but the respective repo of all the issues should not have 0 stars. Star count can be greater than 10 or 20 per repo and there must be total of 30 issues on a single page. Thanks

1> So the main goal is to get 30 issues per page, right??
2> Let's say there are total 25 issues including the 0 star repo, should I include it or remove it from the final list??

Let's say there are 100 total issue per page right including 0 star repo. The main goal is to show only 30 issues from the top which have >= 10 or 20 stars.
The point here is, the API call in this project hasn't defined how many issues to fetch, so by default it is fetching only 30 issues including 0 star repo and to fetch 100 issues you need to specify the parameter in the API endpoint (you can check the github API documentation).

Let's say there are 100 total issue per page right including 0 star repo. The main goal is to show only 30 issues from the top which have >= 10 or 20 stars.
The point here is, the API call in this project hasn't defined how many issues to fetch, so by default it is fetching only 30 issues including 0 star repo and to fetch 100 issues you need to specify the parameter in the API endpoint (you can check the github API documentation).

I am facing issue while adding a query for stars:>10 in the url.
It don't get the expected response from the github api.

Github API doesn't filter issues on the basis of stars and forks.

Github API doesn't filter issues on the basis of stars and forks but it does filtering of repo on the basis of stars and forks

Hey can you help me bit, I am not getting on how to solve this issue.
I am thinking of creating a button which will sort the 30 issues in the list on the basis of stars after fetching them.
If you have any other approach, do share with me.


Add a first JSON macro based on package:json/json.dart.

Adds a minimal JSON macro, lots of TODOs.
Adds return types for fields to the model + (analyzer only) query handling.
Skip golden tests for analyzer/CFE if there are no goldens, instead of failing.
Uses templating for identifiers as suggested in https://github.com/dart-lang/language/issues/1989#issuecomment-2329438841 ... this is just a proof of concept, we should discuss whether we want templating and if so how it fits into the overall design: it could be client side only or we make the template format part of the protocol. (In the sense of "this string has this specified format which won't change, if you want something different add a new type / field").
I didn't look too closely at the augmentation golden file, just make it approximately match the package:json/json.dart output for the same code. I realize we need yet another type of test, to compile the code with macro applications and then test with it, which in this case would test the JSON produced by the JSON macro. I'll look at how to add that...

Filed an issue #70 for the templating discussion, with some initial thoughts on the topic :)

Congratulations 🙌


Detach from fx

Dear @kyoheiu, thank you for creating felix. Foremost, I like the name a lot and I find it very useful and easy to configure. However, would it be possible to implement an option to detach opened windows of imv, mpv, feh, zathura etc. from the running felix application? I can only control felix once I closed the window which I used to view the file.
Thank you!

@felixg3 I created a PR to implement this feature #77 , so if you have time could you build from the new-window branch and give it a try? In my environment (Arch Linux
Kernel: 5.17.9-arch1-1 and MacOS 11.6) this feature just works.
To run:
git clone https://github.com/kyoheiu/felix.git
cd felix
git checkout new-window
cargo run

cargo install --path . will also work.
If you configure like feh = ["jpg"], and press o on a jpg file, feh will appear in a new window and you can still control felix as well.
Note that if you open a text file with nvim for example, no new window appears, item list blank (pressing esc or any key will correct this) and you will get the following error message after exit:
Vim: Error reading input, exiting...

Vim: Finished.

I think this is because apps like Neovim or vim open files in the terminal, and do not consider opening them in a new window.
I'm trying to figure out a way to at least keep the list visible, but would appreciate if you could check out this new feature.

Implemented #82

Thank you very much. Unfortunately, I didn’t see your comment until now :( hence I didn’t help/reply. Sorry!

@felixg3  Hope this will help you!


Update Readme: Compatibility

I don't know this library supports Expo or not or which React-Native versions works without problem, I need to test and learn then update the Compatibility section in README file.

Minimum react-native version: https://github.com/ridvanaltun/react-native-deepar/commit/b9c0415003c293bab86fad7c426a14a29a53c576
I need to test Expo too before close this issue

Expo not supported.


Add setuptools as dependency of the workflow

Description

Adds setuptools as an explicit dependency of the workflow conda environment. This is used for putting together the CSET python package, and is required when installing a local copy of CSET.

Fixes #488
Contribution checklist
Aim to have all relevant checks ticked off before merging. See the developer's guide for more detail.

[ ] Documentation has been updated to reflect change.
[ ] New code has tests, and affected old tests have been updated.
[x] All tests and CI checks pass.
[x] Added an entry to the top of docs/source/changelog.rst
[x] Conda lock files have been updated if dependencies changed.
[x] Marked the PR as ready to review.

Maybe should just drop the regenerated lockfiles to avoid conflicts.

Technical change to just make something more explicit and reliable. Therefore merging without review.


Internal error when using topicctl with MSK IAM auth

Error:
time="2022-12-02 17:27:35" level=error msg="[58] SASL Authentication Failed: SASL Authentication failed: [redacted]: Internal error"

cluster.yaml
meta:
  name: redacted
  environment: redacted
  region: redacted
  description: |
    redacted
spec:
  bootstrapAddrs:
  - "redacted:9098"

  tls:
    enabled: true
  sasl:
    enabled: true
    mechanism: AWS-MSK-IAM

From Cloudwatch:
Failed authentication with INTERNAL_IP/INTERNAL_IP ([redacted]: Internal error) (org.apache.kafka.common.network.Selector)

Not sure what that would be, but I got https://github.com/provectus/kafka-ui working with the same cluster.

Same issue here

Same issue here. I tried it on Kafka 2.8.1, 2.7.2, and 2.6.3. Got the error on all of them. Also tried other versions of topicctl such as 1.8, 1.4, and 1.3 but no luck there.
Have someone ever got this working? And if so, which Kafka and topicctl versions?

That's crazy.... I set the environment variable and it indeed worked. Thanks for the help @ghotiphud

After hunting through the other issues a bit, I ended up on this page: https://docs.aws.amazon.com/sdk-for-go/api/aws/session/
Started trying the Environment Variables listed there to see if maybe there was a config that didn't get passed to the underlying library.  Apparently that was AWS_REGION

Seems like the fix might be passing the region from the cluster config yaml into the connector like:
// Create a Session with a custom region
sess, err := session.NewSession(&aws.Config{
	Region: aws.String("us-west-2"),
})

Thanks @ghotiphud !
Just a friendly reminder for people in different regions: make sure to set the correct region. In my case, it is
export AWS_REGION=us-west-2


Custom inline override no longer works

My custom inline override no longer works:
Juno.render(i::Juno.Inline, f::Fun) = string(f)

It now doesn't display anything inline.

IIRC that's fixed with https://github.com/JunoLab/atom-ink/commit/ce0fdf0454cf3914f536ab61163979037ea86d78.

It now only displays the standard render(::Inline, ::Function) display, not my override.

It looks like this for me:


can't import mesh_core_cython

After building cython module, the error message "ImportError: cannot import name 'mesh_core_cython" was showed.
What can I do??

Could you provide more information like the Python version, import error?

python ver3.6.2
macOS10.14
the errot message
Traceback (most recent call last):
File "main.py", line 25, in
from utils.render import get_depths_image, cget_depths_image, cpncc
File "/Users/(my account)/Desktop/3DDFA/utils/render.py", line 17, in
from .cython import mesh_core_cython
ImportError: cannot import name 'mesh_core_cython'

Is the binary file likemesh_core_cython.cpython-37m-darwin.so generated successfully?

I have done grep, but the file doesn't exit.

You may install Cython first,
sudo pip3 install cython

Then cd into utils/cython, build it
python3 setup.py build_ext -i

If the *.so is generated on current directory, everything will be ok.

already installed Cython
After building it,  ↓error messages was showed.
the error message
""""""""""""""""""""""""
running build_ext
skipping 'mesh_core_cython.cpp' Cython extension (up-to-date)
building 'mesh_core_cython' extension
gcc -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwra
pv -O3 -Wall -Wstrict-prototypes -I/Users/(myaccount)/anaconda3/include -a
rch x86_64 -I/Users/(myaccount)/anaconda3/include -arch x86_64 -I/Users/(m
yaccount)/anaconda3/lib/python3.6/site-packages/numpy/core/include -I/User
s/(myaccount)/anaconda3/include/python3.6m -c mesh_core_cython.cpp -o buil
d/temp.macosx-10.7-x86_64-3.6/mesh_core_cython.o
warning: include path for stdlibc++ headers not found; pass '-std=libc++'
on
the command line to use the libc++ standard library instead
[-Wstdlibcxx-not-found]
In file included from mesh_core_cython.cpp:624:
In file included from /Users/(myaccount)/anaconda3/lib/python3.6/site-pack
ages/numpy/core/include/numpy/arrayobject.h:4:
In file included from /Users/(myaccount)/anaconda3/lib/python3.6/site-pack
ages/numpy/core/include/numpy/ndarrayobject.h:18:
In file included from /Users/(myaccount)/anaconda3/lib/python3.6/site-pack
ages/numpy/core/include/numpy/ndarraytypes.h:1823:
/Users/(myaccount)/anaconda3/lib/python3.6/site-packages/numpy/core/includ
e/numpy/npy_1_7_deprecated_api.h:15:2: warning:
"Using deprecated NumPy API, disable it by "          "#defining
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-W#warnings]
#warning "Using deprecated NumPy API, disable it by "
^
mesh_core_cython.cpp:626:10: fatal error: 'ios' file not found
#include "ios"
^~~~~
2 warnings and 1 error generated.
error: command 'gcc' failed with exit status 1
"""""""""""""""""""""""""""""""""""""""""""

You may update your Command Line Tools on macOS. But I am not sure for it.

I used "iTerm2"
but it is up to date...
so, I can't found the source of the error.

No feedback.

hi，this is my issue with mac ,
(3Dven) zhangxMacBook-Air:3DDFA zhangxiang$ python3 ./main.py -f samples/emma_input.jpg --bbox_init=two --dlib_bbox=false
Traceback (most recent call last):
File "./main.py", line 25, in
from utils.render import get_depths_image, cget_depths_image, cpncc
File "/Users/zhangx/tf/3DDFA/utils/render.py", line 17, in
from .cython import mesh_core_cython
File "init.pxd", line 918, in init mesh_core_cython
ValueError: numpy.ufunc size changed, may indicate binary incompatibility. Expected 216 from C header, got 192 from PyObject
the directory trees :
(3Dven) zhangxdeMacBook-Air:cython zhangxiang$ tree
.
├── init.py
├── pycache
│   └── init.cpython-36.pyc
├── build
│   └── temp.macosx-10.7-x86_64-3.6
│       ├── mesh_core.o
│       └── mesh_core_cython.o
├── mesh_core.cpp
├── mesh_core.h
├── mesh_core_cython.cpp
├── mesh_core_cython.cpython-36m-darwin.so
├── mesh_core_cython.pyx
├── readme.md
└── setup.py
thanks.

Hello, I have encountered the same problem as you. Can you solve it? @

hi，this is my issue with mac ,
(3Dven) zhangxMacBook-Air:3DDFA zhangxiang$ python3 ./main.py -f samples/emma_input.jpg --bbox_init=two --dlib_bbox=false
Traceback (most recent call last):
File "./main.py", line 25, in
from utils.render import get_depths_image, cget_depths_image, cpncc
File "/Users/zhangx/tf/3DDFA/utils/render.py", line 17, in
from .cython import mesh_core_cython
File "init.pxd", line 918, in init mesh_core_cython
ValueError: numpy.ufunc size changed, may indicate binary incompatibility. Expected 216 from C header, got 192 from PyObject
the directory trees :
(3Dven) zhangxdeMacBook-Air:cython zhangxiang$ tree
.
├── init.py
├── pycache
│   └── init.cpython-36.pyc
├── build
│   └── temp.macosx-10.7-x86_64-3.6
│   ├── mesh_core.o
│   └── mesh_core_cython.o
├── mesh_core.cpp
├── mesh_core.h
├── mesh_core_cython.cpp
├── mesh_core_cython.cpython-36m-darwin.so
├── mesh_core_cython.pyx
├── readme.md
└── setup.py
thanks.

Hello, I have encountered the same problem as you. Can you solve it?

Hello, I have encountered the same problem as you. Can you solve it? @zhangdm

Hello, I have encountered the same problem as you. Can you solve it? @yuemengyuan

Sorry if this is a stupid question, but I am having trouble with installing this module and received this error message:
ModuleNotFoundError: No module named 'mesh_core_cython'
How to install it on Ubuntu command line? I also have pip installed.


Fix paths separated by '/' not displaying properly.

Fixes/implements #3073.

There's still an issue with going up when you use '/'.

There's still an issue with going up when you use '/'.


[DO NOT CLOSE] Catch-all PR for Sandbox to verify signatures

This PR is required due to what is arguably a bug in concourse-github-resource.
This PR triggers GitHub to verify signatures so the custom GSP resource can successfully verify commits. This hack is needed to enable us to push to Sandbox directly without having to open PRs. We need to do this until the bug in the resource is fixed.

PR should no longer be required given https://github.com/alphagov/gsp/pull/1053 + https://github.com/alphagov/tech-ops-cluster-config/pull/297


USF-1440: Checkout feature matrix

This pull request (PR) adds a table showing which Adobe Commerce features that the checkout dropin supports.
It also hides incomplete checkout content. We should avoid publishing blank pages in the future.

[!NOTE]
The OptionsTable component doesn't currently support image links. It would be nice to have icons/.svg files for each status similar to this.

I know that we're attempting to finalize the dropin doc template (#41), but since we'll have to refactor the cart docs after that anyway, it seems prudent to get this info out on production. It's unclear how long it will take to get the template finalized.

How about "Supported Commerce features" instead of "Commerce features supported"? That feels more natural to me, but no biggie either way

I converted to the default Starlight table component and added badges. It required some minor style adjustments, which I made in a separate integration branch (now the base branch for this PR):

Approved by Olena in Slack


this.isValid is not a function

I'm trying to make an update during an onChange event but I noticed the validation doesn't fire until after the onChange event, so I thought I'd check to see if the current value was valid by using this.isValid():
changeValue: function () {
      if (this.isValid() === true) {
        var newVal = model.value;
        Actions.receiveValue(newValu);
      }
}

But when I do that, I get:

Uncaught TypeError: this.isValid is not a function

If there's another, better way to check for validity during an onChange event, that would be welcome.

I believe you are calling the method incorrectly. Using class syntax? Make sure you bind the method to the component :-)

@emeeks The issue resolved?


Normalize terminology for root and top

Problem/Opportunity
The idea of adding a helper function top has been proposed several times: #189, #125, #149 and perhaps others. Before making a decision about that feature, I think it would help to clarify what the word "top" means, especially because it currently has a slightly different meaning in rewrite-clj than it does in the wider Clojure community.
In general, in rewrite-clj, "top" or "top-level" refers to the :forms node. In the rest of the Clojure community, "top-level" generally refers to the children of the :forms node.
Proposed Solution
I can imagine several ways to address this ambiguity in terminology. My personal preference would be to use the word "root" to mean the :forms node, reserving the word "top" for its children.
(defn root? [loc]
  (identical? :forms (z/tag loc)))

(defn top? [loc]
  (root? (z/up loc)))

(defn to-root
  "Returns the loc of the root `:forms` node."
  [loc]
  (z/find loc z/up root?))

(defn to-top
  "Returns the loc for the top-level form above the loc, or the loc itself if it
  is top-level, or nil if the loc is at the `:forms` node."
  [loc]
  (z/find loc z/up top?))

I'm not sure whether these need variations with different whitespace/comment handling, and if so, whether that should mean parallel functions to-top*, etc., or whether these functions should have a different arity that accepts the navigation function. The second option might be a little odd, since it would permit nonsensical code like (z/to-root zloc z/down).
Alternative Solutions
Several other approaches are possible. It could simply be a review of the documentation and Issues, clarifying when necessary. Or other terminology might be preferable—"root" is an arbitrary choice.

I think root makes sense. For top-level nodes, maybe top-level? or more explicit?

Interesting. I'm all for defining terms and making things clearer!
One thing to keep in mind is that rewrite-clj is based on Clojure's zipper implementation which in turn is based on Huet's zipper.
Clojure's zip docstrings seem to use the word "top" as an equivalent to "root".

up Returns the loc of the parent of the node at this loc, or nil if at the top
it throws exceptions

Insert at top
Remove at top

prev Moves to the previous loc in the hierarchy, depth-first. If already at the root, returns nil.
etc.

A bit confusing, to me at when first learning anyway, is that it also has fn root which returns the resulting ingested structure. I think a name like root-node would have been clearer to me. But that could just be me.
We could also look into terminology used in Huet's paper on zippers to see if he had clear definitions. A quick search shows "top" used in source snippets and "root" used in text.


Error deserializing nested tuple keys

When using a nested tuple as keys in a Map, the keys cannot be deserialized correctly. Example:
type NestedTuple<'a> = ((&'a str, &'a str), (&'a str, &'a str));

const MAP: Map<NestedTuple, u64> = Map::new("map");

#[test]
fn deserialize_nested_tuple_works() {
    let mut storage = MockStorage::new();

    let ((a, b), (c, d)) = (("larry", "engineer"), ("jake", "shepherd"));

    MAP.save(&mut storage, ((a, b), (c, d)), &123).unwrap();

    // Attempt to deserialize the nested tuple key by iterating the first record in the map
    let (k, _) = MAP
        .range(&storage, None, None, Order::Ascending)
        .next()
        .unwrap()
        .unwrap();

    assert_eq!(
        k,
        ((a.to_string(), b.to_string()), (c.to_string(), d.to_string()))
    );
}

This panics with message:
`at` split index (is 2) should be <= len (is 1)

What version are you using? AFAIK, this was fixed in 2.0.0

What version are you using? AFAIK, this was fixed in 2.0.0

You're right, I was in v1.


need OTA single app mode for economize flash (IDFGH-14256)

Is your feature request related to a problem?
2 app partition is too occupy flash space
Describe the solution you'd like.
app request boot to bootloader
ota in bootloader
if app data verify check success, set flag for jump to  app, otherwise stay in bootloader until success
Describe alternatives you've considered.
No response
Additional context.
No response

The exact mechanism you have described is probably difficult to realize. "Over the air" update typically requires Wi-Fi or Bluetooth stack to work. However, features such as Wi-Fi or BT don't work in the bootloader environment. If your "OTA" process is over some physical interface such as UART, then you can achieve it by implementing a customized bootloader.
Another approach which can help you reduce flash usage is differential OTA: https://github.com/espressif/idf-extra-components/tree/master/esp_delta_ota.

The exact mechanism you have described is probably difficult to realize. "Over the air" update typically requires Wi-Fi or Bluetooth stack to work. However, features such as Wi-Fi or BT don't work in the bootloader environment.

Why can't add Wi-Fi or Bluetooth stack to bootloader?

As it is now, Wi-Fi and BT stacks in IDF both have a number of dependencies: FreeRTOS, various other system components (esp_timer, esp_event, nvs_flash), wpa_supplicant and so on. Once you add together all those things, plus at least a minimal OTA implementation, the binary size is already above 500-700kB. Loading such a huge 2nd stage bootloader would take a long time for a regular (non-OTA) boot.
You can consider the following solution as well:

Have an "OTA updater" app in the "factory" partition. This app in "ota0" partition would only have the OTA functionality.
When the main app needs to perform an OTA, it sets boot partition to "factory" and triggers a reset.
The 2nd stage bootloader boots into the "factory" app.
The "factory" app performs the update of the "ota0" partition, sets the boot partition to "ota0" and reboots.

The downside of this approach is that your factory application doesn't get OTA-updated itself. This could make it vulnerable to newly discovered security issues in Wi-Fi, TLS, and so on. Therefore ideally you should also include OTA functionality into your main app, so that it can update the "factory" app when necessary. However, once you do this, it's not clear if there will be a significant amount of flash size savings.

Thank you for your patient reply.


fix: canonicalize the output directory before checks

fixes #713

Not sure why the test fails on macOS :/

macOS CI can't find pytest for some reason
 pixi run end_to_end_test
✨ Pixi task (default): pytest test/end-to-end -v -s
Error launching 'pytest': No such file or directory (os error 2)

Not sure how that's related to the changes in this PR.

So what is blocking this? I don't see macOS CI fails on it.


Replace k8s.io/apiserver with fork that fixes admission delay

/assign @qiujian16

Duplicated with https://github.com/open-cluster-management/work/pull/52


⚠ RPC server - Celo has degraded performance

In fe88ebd, RPC server - Celo ($CELO_RPC_URL) experienced degraded performance:

HTTP code: 0
Response time: 0 ms

Resolved: RPC server - Celo performance has improved in 6e04a53 after 29 minutes.


Update dependencies to allow latest inline-source

I'm looking to use the latest version of inline-source from the command line.
Updating the semver range appears to be all that is needed, but I'd like to hear your feedback if possible.

Can probably just update to 5, no need to leave it with 4 as well (since its a dep and not a peerDep)

Works for me, I didn't want to tear down a fence without knowing why it was there.

Good reference 👍

Much appreciated!
Could you please publish on NPM so it's available via the registry?  :pray:

Released as 1.2.0!

Thank you, much appreciated.


Custom http client

I've found this article about default golang http client https://medium.com/@nate510/don-t-use-go-s-default-http-client-4804cb19f779. Author recommends using http.Client with tuned timeouts in production environment. This PR allows to pass such custom client to telebot API

Hi! Looks great, thank you!
One point here: maybe it makes sense to implement custom client as a ServerOption, there is already mechanism for it.
I see it something like func WithClient(client *http.Client) ServerOption {...}. What do you think?

Currently bot adapter is created before applying ServerOptions. BotAPI structure allows to redefine http client, so I thought about something like that:
func WithHttpClient(client *http.Client) ServerOption {
	return func(s *Server) {
		s.bot.Client = client
	}
}

However, NewBotAPI function makes one request using http client passed to it (most time the go default one). That might be confusing.
ServerOption does not allow to return an error, so recreating bot adapter through it is not possible without silent failures or panic on errors.
The only solution I see now is to create bot adapter after applying all options (didn't tried to compile it):
// Server is a telegram bot server. Looks and feels like net/http.
type Server struct {
	mux         Mux
        httpClient *http.Client
	middlewares []Middleware
	webhookURL  string
	listenAddr  string
	bot         adapter.BotAdapter
}

func WithHttpClient(client *http.Client) ServerOption {
	return func(s *Server) {
		s.httpClient = client
	}
}

func NewServer(token string, options ...ServerOption) (*Server, error) {
	server := &Server{
   		mux: NewDefaultMux(),
                httpClient: &http.DefaultClient
	}

	for _, option := range options {
		option(server)
	}

        server.bot, err := createBot(token, server.httpClient)
	if err != nil {
		return nil, err
	}

	server.HandleFunc("/help", server.HelpHandler)

	return server, nil
}

The only solution I see now is to create bot adapter after applying all options
totally makes sense to me (except for server.bot, err := is not a valid construction :) ), can you proceed with this solution? I'll merge when you're ready.

Looks good to me, thanks for contribution!


Audit of our Pingdom account

We are at the limit of our licences. We are unable to add new uesrs.
Approach:

Review accounts
Review alarms

Audit completed. No accounts removed.


[v3] Ctrl key has wrong character in kbd

The control/ctrl key has the character ^ instead of ctrl. Caret notation for ctrl is only used on a very small share of operating systems like MacOS as the Classic Mac OS and macOS notation, the majority of OS' use Ctrl/ctrl as an abbreviation for Control.
For most users to recognize it as referencing the Control key, this should be changed to ctrl: 'ctrl',  https://github.com/nuxt/ui/blob/f55194e6f0f942afad212d7f6e7f36afdf657511/src/runtime/composables/useKbd.ts#L8
See https://en.wikipedia.org/wiki/Control_key.

Issue can be closed, this functionality is done in v3