treewide: gate elfutils on lib.meta.availableOn stdenv.hostPlatform elfutils

Description of changes
In #298177, @alyssais pointed out that:

stdenv.isLinux is not a sufficient check for whether elfutils is supported, because it's not supported on static Linux.

I went through every mention of elfutils and any that were gated on stdenv.isLinux are moved to lib.meta.availableOn stdenv.hostPlatform elfutils, just as #298177 did for glib.
There are many other ungated uses of elfutils, and I didn't touch those.
I've targeted staging for this PR out of an abundance of caution, though it ought to be a pure refactor.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Fits CONTRIBUTING.md.

Any idea what the source of the rebuilds is?

Any idea what the source of the rebuilds is?

I didn't initially, but I think I do now: it's the order of the libraries being different in the buildInputs list. The list is ordered, and this jiggles it!

Resolved merge conflict and split into separate commits (to make potential additional merge conflicts easier.)

Right you are. Resolved.


Remove logout workaround

The local storage is now properly cleared by solid-client-authn, so this workaround is no longer necessary, and actually introduces a bug because it creates a race condition between solid-client-authn and the component. Should only be merged after https://github.com/inrupt/solid-client-authn-js/tree/1.x is merged into master and released.

[ ] I've added a unit test to test for potential regressions of this bug. -> N/A, the bug is fixed and tested for in solid-client-authn
[X] Commits in this PR are minimal and have descriptive commit messages.

I've pointed this PR at the solid-client-auth@1x branch so that we can merge it together.

Nevermind, it was super messy. I'll implement this over there.

651b6c1


Species archetypes 🎃

Context
This PR started as a question: would it be possible to use the Hugo archetype system to replace our scripts/template directory? A new species would be created with (a wrapper around):
hugo new species/species_name

Experiment
All the experimental changes are found in the following sections:

content/halloween/jacobus_lanternibus for an example species
archetypes/halloween for the archetype
layouts/halloween and partials/halloween for templates

I have kept the file names to ease diffing with the originals to emphasize changes. For example:
diff layouts/{species,halloween}/species_intro.html

Points of interest

The page resources found under assets and data are now grouped in the species page bundle

See in particular how the assembly page (now a leaf bundle) can include a separate contrib.md

The taxonomy is rendered directly from ENA XML in partials/halloween/lineage.html. The idea being that a wrapper script can just curl the file. I don't know if it's good move, but it was fun to practice Hugo-fu 🥷
The assembly metadata and stats are now packed in a single assembly.yaml

I moved the labels from the configuration to the templates (see partials/halloween/assembly_stats.html for example), for better data/display separation of concerns (so that labels can be changed/reordered in a single place, for example).

The front matters uses hugo-reserved keys when possible (ex: resources or lastmod) and group the remaining ones under params for clarity

I may have forgotten some points, but halloween is almost over so I move along :)
Next steps
If you want to create your own halloween species and push it to this branch, feel free ;)
But other than that, this can stay as an experiment. If we do identifies bits and pieces to include, I will think further on how to integrate the changes.
Happy Halloween :)

Thanks for this work, I've learnt a lot from it, and it gave me much to think about! :)
In summary I really like the bundling strategy and benefits it provides and think we should go for it. I'm not completely sold on using archetypes for our use case because I think a Python script can achieve the same thing and provides even more flexibility, when it comes to for example querying an api.
I think the page bundling approach is really nice, because as you said, it allows us to group related content together. We have a lot of files like images/configs that are associated with a single page and I do think this approach would be better for them. I see that methods like Resources.Get also work on page bundles so I can't see any downside with using them which is cool! I think this is something we should try to implement.

The taxonomy is rendered directly from ENA XML in partials/halloween/lineage.html. The idea being that a wrapper script can just curl the file. I don't know if it's good move, but it was fun to practice Hugo-fu 🥷

That was impressive! Glad I got to learn the about the lineage of a field pumkin haha.

The assembly metadata and stats are now packed in a single assembly.yaml
I moved the labels from the configuration to the templates (see partials/halloween/assembly_stats.html for example), for better data/display separation of concerns (so that labels can be changed/reordered in a single place, for example).

I really like this. This also seems like something that would be straight forward to implement as a single JIRA task independent of the other steps which is nice.
A critique:
Something that I wonder about with this PR is setting defaults for things that require some kind of modification (or at least for the developer to check). For example: (taken from hugo/archetypes/halloween/_index.md)
date: {{ .Date }}
title: '{{ replace .File.ContentBaseName `_` ` ` | title }}'
subtitle: Species common name
lastmod: {{ .Date }}

resources:
  - title: '{{ replace .File.ContentBaseName `_` ` ` | title }}'
    name: cover_image
    src: "placeholder.png"
    params:
      attribution: CC-BY-SA
      link: "https://placehold.co/600x400/png"

layout: "species_intro"
weight: 1

params:
  banner_title: "Species overview"
  goat_webpage: "https://goat.genomehubs.org"

  # Map
  gbif_taxon_id: 2874508
  latitude: 60
  longitude: -40
  initialZoom: 1.5

I think this creates the possibility for a mistakes to slip through when a new species is added and some of the params aren't edited. This isn't just about for example having a default gbif_taxon_id (which I guess was for demo purposes) but also about setting things like the attribution or lastmod. With a lastmod autocreated, it would be easy to forget to update this once the species is ready.
I think the placeholder "[EDIT]" in those places makes it clear what needs to be updated by a human and what doesn't and makes it much easier to spot if something has been missed. This becomes more important when a new species hasn't been added for a few months and we are feeling rusty about what should/should not be edited.

You did a lot of work here! It was very educational for me too, thanks for that.
I don't know if this was intended to be inspected in a web browser, but I noticed
cd ./hugo
hugo serve

does not work for me in this branch. Perhaps I should have rebuilt my local hugo dirs from scratch to avoid the errors? So I'm writing my thoughts with the assumption that if and when we go for a refactoring, it would not affect the end-result that the users see in their browsers.
Nevertheless, I see many merits in the new strategy. The page bundling and how it facilitates overview of the hugo directory will be useful for not only for us, but also for reuse of the codebase by people outside of our team.
As for whether it is worth it to fully refactor to the archetype strategy or not (cf. Rory's comment about the merit of the current Python scripts), my view is that we will need a certain degree of flexibility since we have already seen quite a bit of diversity in the data and content needs for the different species. For instance, for the Litorina snail, we got both assembly and annotation BUSCOs and not just the former, being able to deviate from the table outline set by the template was very useful. I've seen quite a few small examples like this by now.
So I guess the bottom line of my review is to ask: to what degree the archetype strategy can accommodate exceptions? I'm happy for us to switch to the archetypes-based setup if it still allows us to tailor individual species pages to each research group's needs and requests.
I also agree with Rory that there is a big benefit of using EDITs and TODOs to bring attention to things that humans might miss. These have helped me several times. The playwright tests that check for them are great for ascertaining that they do not end up in live page.

I also agree with Rory that there is a big benefit of using EDITs and TODOs to bring attention to things that humans might miss

I there are values that we think should not be lacking, I would argue that errors should be reported at build-time rather than during integration tests.
A possible way to achieve this would be through the use labeled warnings to report missing values in templates. See this snippet from assembly_stats.html for illustration:
{{ if not .optional }}
  {{ warnidf "missing-assembly-stat" "%s/assembly.yaml: %s undefined" $.path .key }}
{{ end}}

These warnings can be suppressed during development, but also promoted to errors in production builds. See warnidf
That way both human and computer eyes can be pointed to the issues :)

Thank you for your feedback on this little experiment.
I think there are two independent tracks of changes:

Gathering resources in species page bundles
Using Hugo archetypes to eventually replace add_new_species.py

The first point could be implemented gradually  (as @RMCrean suggested). Example JIRA task: move all images into species page bundles.  An thus tackle scattered resources one by one.
The main reason I see to pursue 2. is that our "Genome Portal Kit" could thus be distributed as a standalone Hugo Module. I will soon commit an iteration that will illustrate some more powerful uses of Hugo templating in order to approach the conveniences provided by add_new_species.py
Stay tuned ;)

In 5e6a61b you have a rough example of how taxonomy information can be embedded in the species .Params through archetype templating. To test: hugo new halloween/cucurbita_pepo. You can imagine how we can extend this to get the GBIF taxon ID, and build external links.

no external taxonomy.xml or taxonomy.json is needed anymore.

Nice work on that! I poked around in the Cucurbita pages and was trying to figure out how the taxonomy keys works. So there is index.md that seem to call on another file (is it linage.default.yaml)?
Maybe because I am at a taxonomy conference as I write this, I am thinking about the fact that biological taxonomy is not always as clear-cut as the text-book schema make it seem. See for instance https://genomes.scilifelab.se/skeletonema_marinoi/ for an example where the remotely fetched data did not match the ranks selected for the Genome Portal. I had to manually curate taxonomy.json and make some semi-subjective decisions as to which ranks from the NCBI taxonomy entry to include. Have the option to do so in the refactored version would be very useful. (perhaps this is already possible and that this might be a matter of me not having figured out how to manipulate the new page structure)
Also, I was confused for while by the alphabetical order of the taxonomic ranks in _index.md and linage.default.yaml. It would be cool of the the hierarchical order used in e.g. config/_default/params.yaml could be retained in these files too 😄

So there is index.md that seem to call on another file (is it linage.default.yaml)?

The source for the taxonomy data is now in the front matter of _index.md, under the .params.lineage key. This can be edited freely. But the cool (all proportions kept) feature is that .params.lineage will be populated with ENA data automatically when doing hugo new halloween/cucurbita_pepo for example. The lineage.default.yaml is provided only as an example, if the aforementioned bootstrap fails and .params.lineage needs to be edited by angry hands.

I had to manually curate taxonomy.json and make some semi-subjective decisions as to which ranks from the NCBI taxonomy entry to include. Have the option to do so in the refactored version would be very useful. (perhaps this is already possible and that this might be a matter of me not having figured out how to manipulate the new page structure)

The taxonomy ranks that are displayed are the same for all species, controlled by config/_default/params.yaml. But I could easily allow to override this on a per-species basis, when .params.taxonomy_ranks is defined in the _index.md front matter. Would that be useful you think ?

The source for the taxonomy data is now in the front matter of _index.md, under the .params.lineage key. This can be edited freely. But the cool (all proportions kept) feature is that .params.lineage will be populated with ENA data automatically when doing hugo new halloween/cucurbita_pepo for example. The lineage.default.yaml is provided only as an example, if the aforementioned bootstrap fails and .params.lineage needs to be edited by angry hands.

I see, that makes sense. With this in mind I think I better understand my test case and the errors I got. Changing the values of scientificNameand taxID of parameters that are rendered by default on the page work, like you described. Yesterday I think I must have changed clade by mistake, thinking it was kingdom by habit of it being the first in the array 😄. I now also understand why there is a hugo error when I try to change the name of a taxonomic rank key. All good!

The taxonomy ranks that are displayed are the same for all species, controlled by config/_default/params.yaml. But I could easily allow to override this on a per-species basis, when .params.taxonomy_ranks is defined in the _index.md front matter. Would that be useful you think ?

Yes, that would be useful to have for edge-cases!
For example: the peculiar edge-case with S. marinoi is that it belongs to three different clades and no kingdom. I have never encountered a case like that before in biology! So I just picked one of the more established clades for the page. Being able to redefine which ranks are displayed, and in which order they are displayed (cf. display_order key in the old taxonomy.json schema) would be needed if we want to update this species with the refactored logic.

Wow, this is really nice. I've just been playing around with it for a few minutes now. I have some catching up to do on all the changes you've made since I last looked! Really impressive work @kwentine!

Sorry for the delay

No need to be, lots of changes to take in at once!

I had assumed some of these things would not be possible with Hugo

Me neither to be honest. I had hoped at best for a small shell wrapper around hugo new to preserve add_new_species.py features. But this is a bit borderline though: the error handling is scant, and should things get more complicated (for our use case at least) I think investing on consolidating add_new_species.py would be safer way forward.

* If the plan is to use` lastmod` in place of `last_updated `param in the markdown I still think it would be better to have it as [EDIT] flagged by default

I don't want EDIT placeholders 😭 Which is quite whimsical, so I will yield to the majority :)

* More general question perhaps just to understand better. Based on Daniel's flow chart about automation's that can be implemented to the species adding process.

Great question. I'm not sure, but what would give is the greater flexibility is an automation pipeline that yields a big species-content.json. That beast could then be accessed and interpolated by the archetype templates. Or equally well be passed to add_new_species.py as an argument.
So either:
# Perhaps not the best location but just to give an idea
cp species-content.json /tmp/tiny_herb/
hugo new species/tiny_herb # Uses resources.Get magic to bake in all species content

Or
add_new_species.py --context=/tmp/tiny_herb/species-content.json

Another dimension to consider is that this is probably very specific to our portal implementation and workflows...
Not a lot of definite answers, but I hope it makes sense elicits interesting design thinking :)


Upgrade byteorder to 0.5.1

If this is ok, would you please release a new version?

Thanks for waking me up, I'll update all dependencies and release a new version. :smile:

Done in feea0c22a5b4f70ec6f2a036f381cb90eeecdbb3

Thanks :)


Avoiding mi_cfree on mac interpose mode

I think you might just need to interpose malloc_default_zone too. This is what asan ends up doing, among other things (I suspect the other things it interposes are related to asan's functionality): https://github.com/llvm/llvm-project/blob/350fafabe9d3bda75e80bf077303eb5a09130b53/compiler-rt/lib/sanitizer_common/sanitizer_malloc_mac.inc#L85
You also can try __attribute__((constructor(0))) to try to get loaded earlier than with normal __attribute__((constructor)). Not sure if that matters for shared libs, probably not, but it can help for static linking.
This is a somewhat messy commit (includes unrelated whitespace changes, XXX comments, and doesn't reuse the existing interpose stuff) that does these and seems to work for me. https://github.com/thomcc/mimalloc/commit/52b5237028a27644ffc4e8a671d7b884a2fa7379
Unfortunately, IDK how to trigger the bad behavior that lead to you using mi_cfree in the first place, so IDK if it fixes it. That said, if you want I can PR it.
Still it's a bummer that doing this in a statically linked build isn't viable how it is on other unixes...

Awesome -- thanks so much. I just got myself a shiny mac mini so I can actually locally test and develop more easily now so I will try this out. It is a hassle on the mac, I wonder why they went to a different loading system and the zone system in the first place since the basic BSD/Linux loading works so nicely :-( ah well.
I forgot how to trigger the bad behavior but I remember it being in one of the mimalloc-bench benchmarks so I let you know how it goes.

Hi @thomcc -- thanks again for this and apologies for the delay; I took the commit above and integrated it -- I also updated all the benchmark suite to run on macOS and it seems to work fine now without the cfree check :-)  Very nice.
Some benchmarking shows that mimalloc is often 2x faster that the system allocator (!) Thanks again


default to RG photos

I think this will cause the taxon photo chooser to default to RG observations instead of all observations.  The idea is to help prevent incorrect taxon photos.

Thanks, but please see https://github.com/inaturalist/inaturalist/blob/master/CONTRIBUTING.md. Feature requests should get worked out in the Forum first, and if there's support someone (probably someone on staff) should make a github issues, and then labeling of the issue indicates that it should get done.

Just realized CONTRIBUTING was not entirely clear on this point, so I just updated it.

We already discussed it repeatedly in the forum and @tiwane said he would get to it.  Seemed like small enough a change to shortcut the red-tape, but I guess I can start back at the beginning of the process.

Ok, #2596 exists now so I'm re-opening this. Still need to confirm that this actually fixes the issue. @jwidness, do you have a working development environment in which this fixed the issue?

No, I currently only have access to a Windows environment and didn't feel like attempting to get things running in Windows.

Roger that. Just gave it a test and it didn't quite work, but I'm pretty sure 4af4782ac67ec8498aa132752df80c753de52a17 will do the trick.

Thanks!  Generally how long is it between a commit and going live on the site?

Between hours and days. This one will be more like hours. Just need to make sure all tests pass.


Move codesign_patched_binary to extend/os/mac/keg.rb

[ ] Have you followed the guidelines in our Contributing document?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same change?
[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

Review period will end on 2022-04-12 at 00:00:00 UTC.

This PR should make it safe for us to define a generic method in keg.rb for codesign_patched_binary that is overridden on macOS.  I've confirmed that codesign_patched_binary still works on my Intel machine by simply adding a debug statement that verified the method in extend/os/mac/keg.rb was called even though it doesn't actually do anything on an Intel system.

Review period ended.


Enhancement/gh 3065 allow undo determinations

Fixes #3065
This adds the ability to undo determinations, sending them back back to external review.  While this doesn't remove the determinations (delete no data), it will add to them. That means, if the submission reaches the determination phase again, it will have multiple determinations.

Whoops, tests broke.  Patch incoming!

Tests updated (removed), as noted in the commit.  I did add one test, but I couldn't get it to work.  I'm not sure what action I should be specifying to execute the new workflow item that was added.  Any help there would be appreciated!


Add brief explanation to Nearby Places UI

I think it currently isn't very clear to a lot of users what Nearby Places does, and there isn't space in the action bar to make the title more explicit. Perhaps we could have an additional UI component (like a subtitle) to explain the feature?

If the explanation text is short enough, we could fit it below the "Nearby Places" text in the actionbar, just like the number of uploads are shown in the home screen below the "My Recent Uploads" text in the actionbar.
Or we could use something like a tooltip that would come up only the first time the user ends up on the screen.

Yeah, text under the actionbar sounds feasible to me (it could say just "nearby places that lack photos", perhaps?). But not sure if that is in line with UI design guidelines. Hopefully someone experienced in UI design can chime in?
The first-time tooltip is a viable idea also. :)

Just attaching a screenshot for reference as to what it could look like:

I have used this library for the tooltip.

Given the wide variations in screen sizes, we cant guarantee that the message in the toolbar will be fully visible.  I think the screenshot is an example of this.
If we're shooting for a "first run" type of experience, would it be better to use a library like MaterialShowcaseView and walk the user through the functionality, highlighting that you can switch between map and list views, and what the screen is all about?

Thumbs up from me for MaterialShowcaseView. :) Not sure how time-consuming it is to implement, but it does seem like the ideal solution.

MaterialShowcaseView looks neat. We could start by using it for NearbyActivity first and probably implement it for other screens as well in time.


Generate static plain html pages

Description
I want to build my website (a simple blog) using wordpress and Gridsome but I have a lot of boilerplate genearted by SSR in my final html.
Steps to reproduce
After building my site with 'gridsome build' I see a lot of js files included along the html generated, also a huge initial_state
Expected result
I'd like to have an option to disable SSR boilerplate and generate plain static html pages with gridsome build
Environment
I'm using the latest gridsome and the latest gridsome wordpress plugin

To add some info to my issue, I'd like to have an option to do that like Nuxt https://github.com/nuxt/nuxt.js/issues/6835
render: {   injectScripts: false }
In Nuxt there are also useful hooks to modify the final rendered html: Nuxt AMP plugin for example removes extra elements before rendering using hooks, like external script tags and js for dom hydration. Is there anything similar in Gridsome?

https://gridsome.org/docs/overriding-index/
You can create your own index.html and remove ${head} and ${scripts} from it. Should still build out the files without any css/metadata/js. You could also keep ${head} to retain the css

Thanks a lot! It works! I think this should solve https://github.com/gridsome/gridsome/issues/990

Sadly, keeping ${head} will still load the javascripts because of the  prefetch. So it will be loaded but not used.

@DerAlbertCom try looking at https://github.com/gridsome/gridsome/blob/master/gridsome/lib/server/createRenderFn.js
It breaks everything out so you can pick and choose. It’s not documented for now but may help.

@courcelan i took some to takle the problem. I understand that i might need a 'handle' to context.meta.inject() to modify that structure so that vueMetaStyle and vueMetaScript may not render anything. But I've read the docs, looked around in the sourcecode (maybe not deeply enough) and i don't find the hook to override, clear or whatever I have to do so that the styles and scripts fetch hints don't get  rendered.

After I wrote that comment, I think I've takled the problem from the wrong side ... (talking out loud helps). We report back.

<!DOCTYPE html>
<html ${htmlAttrs}>
  <head>
    ${title}
    ${base}
    ${hash}
    ${vueMetaTags}
    ${vueMetaLinks}
    ${styles}
    ${vueMetaStyles}
    ${vueMetaScripts}
  </head>
  <body ${bodyAttrs}>
    ${app}
  </body>
</html>

that's the needed index.html.

Being able to publish websites with exactly zero Kb of client-side JS is great in some cases.
Another nice to have in that case would be to remove all the vue data attributes from the output (#813)

Anyone know if it is possible to specify multiple index.html files? For example, index.html (as provided by Gridsome) and plain.html which would be a custom html template used for specific collections?

Massive thanks for the template @DerAlbertCom
Does anyone have a way to only disable the actual SPA part of Vue?
I would love to use gridsome to structure my site and import libraries like Swiper in my components. The one thing I don't need most of the time is the actual Vue SPA that sits on top after generating. If I use the index.html you provided everything that's JS gets wiped out. Perfect would be the other way around: generate the entire thing, use vue to build the site and enable external libraries if used, but dont actually inject the whole vue SPA into the script that gets generated before the body text.

@MrMacStripe You can't use everything depended on Vue with this approach, but you surely you can use "normale" JavaScript Libraries, simple put them in your templates and use them without Vue.


CI failing on release-v1.9.0

A lot of our CIs are failing on release-v1.9.0 (and on main, but less urgent)
https://github.com/meilisearch/meilisearch/actions/runs/9543257463

Due to the new release of rust

Fiiiiiixed
https://github.com/meilisearch/meilisearch/actions/runs/9549769580


how to run it by other trained model

Hello, I would like to try to use my trained model predictions(trained with origin BERT) and convert them from .ckpt to .pb files. But when I call model.tokenize_compute and I got wrong, "The model does not have additional_output_layer, the output logits is wrong.". It seems that I had wrong in my model conversion. Can you tell me how to convert my trained model to pb?

The warning suggest that you do not have
https://github.com/google-research/bert/blob/d66a146741588fb208450bde15aa7db143baaa69/run_classifier.py#L606
in your model.
So, you can change your output_type and output in your python code. Maybe you need cuBERT_POOLED_OUTPUT.

Please have a look at https://github.com/zhihu/cuBERT/blob/master/python/cuBERT_benchmark.py

Thank you for your reply, it is working for me.


Unable to connect from https

Hey,
I have a box set up. I can only access it through https, which I have set up on a nginx server, that just forwards traffic.
It does so normally to all my services except requestrr. It displays a blank page and this message in the docker logs:
Failed to determine the https port for redirect.
Any ideas?

Hey @HeisenbergK,
Thanks for reaching out.
Hmmmm, I am not sure as I have not tried to setup Requestrr like this, I might have to setup a VM and test it...
In theory, as long as you have setup Nginx to proxy the traffic correctly to Requestrr's website (which is http on port 4545) and have the correct SSL certificates...it should work fine but I do not know.
I might test this and see if I can find any issues.  But, might be a little while until I have some spare time.

Found a solution. First set network_mode: host in docker to be able to see Radarr/Sonarr.
Then in nginx, you need to set a new server in sites-enabled, listening to the subdomain set for requestrr in the DNS routing. Example:
server {
  listen 443 ssl http2;
  listen [::]:443 ssl http2;
  server_name requestrr.example.com;

  ssl_certificate /etc/nginx/ssl/example.com/fullchain.pem;
  ssl_certificate_key /etc/nginx/ssl/example.com/key.pem;
  include snippets/ssl-params.conf;
  client_max_body_size 40M; # If uploading large files to application set this to 0 and remove the M
  server_tokens off; # Security

  location / {
    proxy_pass http://<IP_ADDRESS>:4545/; # Docker Container port
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header X-Forwarded-Protocol $scheme;
    proxy_set_header X-Forwarded-Host $http_host;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
  }

  location ~ /\.ht {
    deny all;
  }
}

Hope it helps people set up awesome servers!!

Hey HeisenbergK,
Sorry, I never got a chance to look at this.  What you have found is perfect, I'm glad you found a solution.
Thank you for sharing :)


Erratic behavior when using input methods

Environment
Windows build number: Microsoft Windows [版本 10.0.18363.720]
Windows Terminal version (if applicable): 0.10.781.0

Any other software? no

Steps to reproduce
Open a terminal with Chinese IME on. Now type any pinyin, e.g. "shili" ("example"), and you see the characters suggested by the IME.

(The cursor bar should appear on the right side as mentioned in issue #3730, but it's a minor bug.)
Then hit backspace 5 times to clear the input.

Expected behavior
What you just typed in the IME should be deleted and the IME suggestion box should be closed. There shouldn't be any side effects.
Actual behavior
The suggestion box closes, but an unexpected "s" remains. What's more, while English input is still fine, you're no longer able to use IME to type in this terminal window: the suggestion box works but nothing appears in the terminal.

This also happens when you interrupt the IME, for example by clicking elsewhere, before accepting the characters.

This is a known issue. Related to #5054 and #5110 .

@skyline75489 Thanks for replying! I see now it's a duplicate of #5054 and there seems to be already a fix (#5109). The first-letter thing still exists, though. I'm just a student and I haven't studied much of the source code, but I think I'll fork the repo and try to build and understand it in case my computer hardware permits.

@Knowif Glad to hear that. A good practice before submitting an issue would be checking if there's any duplicate. Contributing is also welcomed.

Thanks for the triage pass @skyline75489!
@Knowif since you're thinking this looks like a dupe of #5054, I'm going to resolve this issue as such. If this ends up coming back after 0.11 comes out, then feel free to ping us here and we can re-open to continue the investigation. Thanks!
/dupe #5054


Fix qgl viewer examples

Fix QGLViewer-based examples.  Notable changes:

Order of some operations in exported CMakeLists.txt was changed to take libraries added by some options into account.  Currently options WithQGLViewer and WithOpenGL specified in the example-specific .cmake file were ignored.
To avoid a segfault on Ubuntu 15.10, I found I needed to compile QGLViewer myself for Qt4, since the version installed by apt-get was compiled for Qt5.  For this, I added the Siconos install path to the paths searched in FindQGLViewer.cmake.
There was an out-of-bounds assertion in SphereLDS.cpp, related to qMemory being checked after initialize, but before anything is inserted.
Had to "#include" SiconosKernel.hpp before SiconosBodies.hpp, otherwise code would not compile, complaining about parameter mismatch for the visitor pattern.

Ah, just realized this is based on 3.8.x.  Should I rebase it on master?

Just rebased it on master, seems to make more sense. Sorry about that.


JSON-RPC Client WebSockets

Task summary

The forest CLI rpc-client needs to be able to make RPC calls using WebSockets.
Specification reference

ACs:

[ ] Supports traditional transactional RPC calls over WS
[ ] Supports streaming responses from ChainNotify

Other information and links

https://github.com/ChainSafe/forest/pull/1100#pullrequestreview-671564178
https://github.com/ChainSafe/forest/pull/1100#issuecomment-850631576
https://github.com/ChainSafe/forest/pull/1100#issuecomment-850633068

hi, you can  to give jsonrpc-core-client a shot?
i wrote a small program, and it works well with a lotus node, for the simple request-response methods

@dtynn No, we built our own, based on jsonrpc_v2:
https://github.com/ChainSafe/forest/blob/main/node/rpc-client/src/lib.rs
We needed more functionality than the Parity client exposed at the time, and it wasn't too hard to implement.


fix(core): Add bin entry

Add bin entry to allow npm run calavera

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Ubuntu 16.04.1 LTS incompatibility

I think I've found an incompatibility with the current version of Ubuntu, related to a conflict between the Cassandra code in Datafari 3.0 and Python 2.7.12 that is used in Ubuntu 16.04.1
Summary: Datafari 3.0 installation is partially successful in a fresh Ununtu 16.04.1 LTS installation. The main search page appears, but attempts to login to the admin page fail with a username/password error. Watching the logs during login attempts, catalina.out complains that:

com.datastax.driver.core.exceptions.InvalidQueryException: Keyspace 'datafari' does not exist

Attempting to investigate this by the command line utility cqlsh (/opt/datafari/cassandra/bin/cqlsh) results in the error:

Connection error: ('Unable to connect to any servers', {'<IP_ADDRESS>': TypeError('ref() does not take keyword arguments',)})

This seems to be a symptom of CASSANDRA-11850, related to an incompatibility with Python 2.7.11+. This issue has been patched and merged into master branch, but the fix does not seem to yet be incorporated into Datafari.
If I could figure out what to change where, I'd create a pull request, but I'm afraid this is a bit beyond my abilities. Hope there are enough clues here to understand the issue, and recommend a fix.
Thanks for all the effort on this project, I'm eager to get it running!

In case others face this same issue: I abandoned Ubuntu 16.04, and started over with a fresh install of Debian 7.11, and that was successful. I did run into a problem when starting Datafari, with an error
GLIBC_2.14 not found
This workaround was successful:
Edit:  /etc/apt/sources.list
Add: deb http://http.us.debian.org/debian/ testing non-free contrib main
apt-get update
apt-get install libc6-dev

Hi Craig,
Thanks for your detailed report. We will try to reproduce the issue you mentioned on Ubuntu 16.04 and let you know.
For the lib not found on Debian, yes it is a mandatory package to install.
The requirements on the readme file are :
Debian environment : requires curl, debconf, unzip, sudo, libc6-dev
Enjoy Datafari !

Regarding the Debian lib -- After initially installing Debian 7.11, I did run
apt-get install curl debconf unzip libc6-dev
I believe that everything installed successfully. After receiving the GLIBC_2.14 error noted above, I added the above note line to sources.list, ran the update and install, and then datafari started without complaints. I think there might have been version problem with the original libc6-dev package.

Hi,
Thanks for the reporting. Indeed for Debian 7, the version of the libc6 is too old in the stable repo.
We will update the documentation with your workaround for Debian 7.
On the other hand, in Debian 8, the libc6 lib in the standard repo is OK.
Best regards,
Olivier

Thanks, that's good to know. It would be helpful to recommend at least one recommended distro and point release in README.txt (it currently says "Debian7 or higher").

Hello, I think upgrading to cassandra 3.9 could solve the problem.

We use now Cassandra 3.10 in Datafari 4. The issue is not present anymore.


Coordinates outside bounds of area of use now return inf

Running the GeoPandas tests with proj 6 / pyproj master, turned up this regression:
In [1]: import pyproj

In [2]: pyproj.__version__
Out[2]: '2.1.3'

In [3]: p1 = pyproj.Proj(init='epsg:26918')
   ...: p2 = pyproj.Proj(init='epsg:4326')

In [4]: pyproj.transform(p1, p2, 0, 0)
Out[4]: (inf, inf)

vs
In [1]: import pyproj

In [2]: pyproj.__version__
Out[2]: '1.9.6'

In [3]: p1 = pyproj.Proj(init='epsg:26918')
   ...: p2 = pyproj.Proj(init='epsg:4326')

In [4]: pyproj.transform(p1, p2, 0, 0)
Out[4]: (-79.48874388438705, 0.0)

So the transform now returns inf instead of an actual value. The coordinates however are out of the area of use (see bounds here http://epsg.io/26918). But previously it did calculate the transformed values nevertheless.
Here, it was a dummy test case in geopandas where we did not check that the tested dummy values were actually properly inside the bounds of the tested CRS. So that is easy to edit. But, it still is a breaking change (I don't know that what extent people run into this in practice).
This seems a bit similar to https://github.com/pyproj4/pyproj/issues/202, but the difference is that here pyproj 1.9.6 actually returned values and not inf.

I think this might need to be tested with PROJ master as well. I believe that they added a fix for that. Did you test it with the latest PROJ?

I think that is what you said already, but just checking to be sure.

No, tested only with pyproj master, but released proj.4 from conda-forge (didn't set up yet dev tooling for proj.4)

Additional comment, there is now the errcheck keyword, which properly raises an error:
In [5]: pyproj.transform(p1, p2, 0, 0, errcheck=True)
...
ProjError: proj_trans_generic error: no system list, errno: 22

but, it's not the most informative error message ... Not sure if we can get more information than that from proj4

Not fixed in the latest version. Probably need to raise issue in PROJ.
>>> import pyproj
>>> p1 = pyproj.Proj(init='epsg:26918')
>>> p2 = pyproj.Proj(init='epsg:4326')
>>> pyproj.transform(p1, p2, 0, 0)
(inf, inf)
>>> pyproj.proj_version_str
'6.1.0'
>>> pyproj.transform(p1, p2, 0, 0, errcheck=True)
....
pyproj.exceptions.ProjError: proj_trans_generic error: no system list, errno: 22

cc @rouault is this an expected change in proj ?

Given the explanation in https://github.com/OSGeo/proj.4/issues/1449 and https://github.com/OSGeo/proj.4/issues/1329, the behaviour of this might have changed again?

Looks like the behavior is restored with the master branch of PROJ:
>>> from pyproj import Transformer, proj_version_str
>>> proj_version_str
'6.1.0'
>>> transformer = Transformer.from_proj("+init=epsg:26918", "+init=epsg:4326")
>>> transformer.transform(0, 0, errcheck=True)
(-79.48874388438705, 0.0)

may be it is out of bounds, but I want to stich some map, How can I force to get the result?
gdal.osr give the result I need, (but pyproj is 2 times faster than osr, and my image is very large, so I need pyproj force to count the point outside)
wkt2 = 'PROJCS["China_Lambert_Conformal_Conic",GEOGCS["GCS_Beijing_1954",DATUM["Beijing_1954",SPHEROID["Krassowsky_1940",6378245,298.3,AUTHORITY["EPSG","7024"]],AUTHORITY["EPSG","6214"]],PRIMEM["Greenwich",0],UNIT["degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic_2SP"],PARAMETER["standard_parallel_1",30],PARAMETER["standard_parallel_2",62],PARAMETER["latitude_of_origin",0],PARAMETER["central_meridian",105],PARAMETER["false_easting",0],PARAMETER["false_northing",0],UNIT["metre",1,AUTHORITY["EPSG","9001"]]]'

wkt1 = 'GEOGCS["WGS 84",DATUM["WGS_1984",SPHEROID["WGS 84",6378137,298.257223563,AUTHORITY["EPSG","7030"]],AUTHORITY["EPSG","6326"]],PRIMEM["Greenwich",0],UNIT["degree",0.0174532925199433],AUTHORITY["EPSG","4326"]]'

prj1 = osr.SpatialReference()
prj1.ImportFromWkt(wkt1)
prj2 = osr.SpatialReference()
prj2.ImportFromWkt(wkt2)

ct = osr.CoordinateTransformation(prj1, prj2)
print(ct.TransformPoint(100.20201515, 40))
# -396193.6266314621, 4808582.335950634, 0.0

prj1 = pyproj.CRS(wkt1,preserve_units=True)
prj2 = pyproj.CRS(wkt2, preserve_units=True)
ct = pyproj.Transformer.from_crs(prj1, prj2)
print(ct.transform(100.20201515, 40))
# inf, inf

@yxdragon, the good news is that there is a simple solution to your problem. In PROJ 6+, they take the axis order into consideration when doing transformations.
In your case, wkt1 has the latitude first longitude second and wkt2 has the east first and the northing second:
>>> from pyproj import CRS, Transformer
>>> wkt2 = 'PROJCS["China_Lambert_Conformal_Conic",GEOGCS["GCS_Beijing_1954",DATUM["Beijing_1954",SPHEROID["Krassowsky_1940",6378245,298.3,AUTHORITY["EPSG","7024"]],AUTHORITY["EPSG","6214"]],PRIMEM["Greenwich",0],UNIT["degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic_2SP"],PARAMETER["standard_parallel_1",30],PARAMETER["standard_parallel_2",62],PARAMETER["latitude_of_origin",0],PARAMETER["central_meridian",105],PARAMETER["false_easting",0],PARAMETER["false_northing",0],UNIT["metre",1,AUTHORITY["EPSG","9001"]]]'
>>> wkt1 = 'GEOGCS["WGS 84",DATUM["WGS_1984",SPHEROID["WGS 84",6378137,298.257223563,AUTHORITY["EPSG","7030"]],AUTHORITY["EPSG","6326"]],PRIMEM["Greenwich",0],UNIT["degree",0.0174532925199433],AUTHORITY["EPSG","4326"]]'
>>> crs2 = CRS(wkt2)
>>> crs2
<Projected CRS: PROJCS["China_Lambert_Conformal_Conic",GEOGCS["GCS ...>
Name: China_Lambert_Conformal_Conic
Axis Info [cartesian]:
- E[east]: Easting (metre)
- N[north]: Northing (metre)
Area of Use:
- undefined
Coordinate Operation:
- name: unnamed
- method: Lambert Conic Conformal (2SP)
Datum: Beijing 1954
- Ellipsoid: Krassowsky_1940
- Prime Meridian: Greenwich

>>> crs1 = CRS(wkt1)
>>> crs1
<Geographic 2D CRS: EPSG:4326>
Name: WGS 84
Axis Info [ellipsoidal]:
- Lat[north]: Geodetic latitude (degree)
- Lon[east]: Geodetic longitude (degree)
Area of Use:
- undefined
Datum: World Geodetic System 1984
- Ellipsoid: WGS 84
- Prime Meridian: Greenwich

Since this is the case, you need to swap the order of your input so that the latitude is first and longitude is second:
>>> transformer = Transformer.from_crs(crs1, crs2)
>>> transformer.transform(40,<PHONE_NUMBER>5)
(-396207.328443438, 4808545.278686934)

Or, if you want it to always have the longitude first and latitude second, you can toggle on the always_xy argument:
>>> transformer = Transformer.from_crs(crs1, crs2, always_xy=True)
>>> transformer.transform(100.20201515, 40)
(-396207.328443438, 4808545.278686934)

For more information about this, I would recommend looking at:

https://pyproj4.github.io/pyproj/stable/examples.html#transformations-from-crs-to-crs
https://proj.org/faq.html#why-is-the-axis-ordering-in-proj-not-consistent

Hopefully this helps.

Also, preserve_units=True is not a valid argument for pyproj.CRS and is only meant for pyproj.Proj.

@snowman2 thanks, and another question, as in china, our map could not use "true coordinate", so we must add some kind of offset. This trans is based on wgs84, and I know the transform fomula. So, can I implements a custom CRS or PRJ? and what should I do? can you give me some advice?

@yxdragon, would you mind opening up a separate issue with your question? That would help us track the issue. Also, when you do, would you mind adding the formula as well as some example points?

@snowman2 It is ok for opening up a new issue, but I think it is not a general question. my question is "does pyproj support custom CRS?" which did not has a geometry meant, just a arbitrary transformation, I think the web Mercator is also not a geometry meaningful prj, just a formula for it could be looking well. So can I specific my prj?

It would be useful to have in another issue so it is easier for someone who has a similar question. I would recommend looking into Transformer.from_pipeline().


Backport 1.2.1 to dev

This PR ports #1704 onto dev
Addresses a security issue when transferring tokens between accounts and purses

bors merge


Personal Gadget - project count gadget showing wrong count

Describe the bug

Type of Object: project
Type of Sub Object: ProjectCount
Query search: Company Avinash Associates

count is mix

like project page and finish project, Review Project

https://www.berrycast.com/conversations/b0607996-6601-56ff-bfe9-ec8fe77d542e


Input box does not take the input

There is a chance that when you drag a new operator the input box does not take any input. You can type the input, but it doesn't save to the backend. As you can see in the screenshot, the validator does not get the input.

@Xiao-zhen-Liu will fix it.


Fix default blueprint by specifying source.

Fixes #72

hold of on this for now, @mike-north and myself are looking into the source of the issue.

the correct solution is actually, omit source and use name without the user/org prefix
 { name: 'ember-cli-test-loader', target: '0.1.3'  }

This will work because ember-cli-test-loader is published to the bower registry. On Ember CLI Mocha we have the issue of relying on ember-cli-shims which is not published to the bower registry and no longer resolves with the repo/project-name format. I think, in that case, that we need source, right?

I've also changed this PR to your suggestion, Stef!

I think, in that case, that we need source, right?

yes, you are correct. For things not published to bower, source should be set.

LVGTM

Thanks for the explanations and quick turnaround on this.

@blimmer sorry for the original issue, it appears are historic usage of bower was in error.
We should release shims to bower and then source is also not needed for that.

heh heh. https://github.com/ember-cli/ember-cli-qunit/pull/71
Thanks, @blimmer


Unable to remove fumadocs fd prefix

To Reproduce
const config: Config = {
  presets: [
    createPreset({
      addGlobalColors: true, // no used adding this
      cssPrefix: 'fd', // replacing this with empty string also doesnot change the classNames
    }),
  ],
  content: [....],
  ...
}

Current vs. Expected behavior
The class names applied should not have fd, but while inspecting we are still able to see the fd prefix.
Provide environment information
Fuma docs version used

{
  "fumadocs-core": "^13.0.1",
  "fumadocs-mdx": "^9.0.0",
  "fumadocs-ui": "^13.0.1"
}

Which area(s) are affected? (Select all that apply)
UI
Additional context
It used to work with the v12 fumadocs ui

addGlobalColors is for adding the colors without prefix so that you can use them in your app, it doesn't change the code of Fumadocs UI


sql-odbc fails to configure

When compiling qt5-core with sql-odbc, unixodbc should be added as a dependency since libs.odbc will fail otherwise
This is handled in #539

commit was cherry picked into master and kirkstone
closing


Unable to build the project on Arm macOS

Hello! I have troubles building the project and I can't figure out why I can't do that. Oh and also I can't run your artifact that you are building in github actions. It fails with the following reason: The application “Eigen” can’t be opened. 🤔
Logs
Installing dependencies:
Analyzing dependencies
Downloading dependencies
Installing AFNetworking (4.0.1)
Installing GZIP (1.3.0)
Installing MatrixSDK (0.23.10)
Installing OLMKit (3.2.5)
Installing Realm (10.27.0)
Installing SwiftyBeaver (1.9.5)
Installing libbase58 (0.1.4)
Generating Pods project
Integrating client project
Pod installation complete! There is 1 dependency from the Podfile and 7 total pods installed.

Running content view preview:
CrashReportError: Eigen crashed because AFNetworking.framework is missing

Process: Eigen[12854]
Date/Time: 2022-07-16 05:03:27 +0000
Log File: <none>

Application Specific Information:
    dyld [
        Library not loaded: @rpath/AFNetworking.framework/Versions/A/AFNetworking
        Referenced from: /Users/possum/Library/Developer/Xcode/DerivedData/Eigen-evebslcpurtsfpgvyeiiqlfvahhh/Build/Intermediates.noindex/Previews/Eigen/Products/Debug/Eigen.app/Contents/MacOS/Eigen
        Reason: tried: '/Users/possum/Library/Developer/Xcode/DerivedData/Eigen-evebslcpurtsfpgvyeiiqlfvahhh/Build/Intermediates.noindex/Previews/Eigen/Products/Debug/AFNetworking.framework/Versions/A/AFNetworking' (no such file), '/usr/lib/swift/AFNetworking.framework/Versions/A/AFNetworking' (no such file), '/Users/possum/Library/Developer/Xcode/DerivedData/Eigen-evebslcpurtsfpgvyeiiqlfvahhh/Build/Intermediates.noindex/Previews/Eigen/Products/Debug/Eigen.app/Contents/MacOS/../Frameworks/AFNetworking.framework/Versions/A/AFNetworking' (code signature in <ACB208E2-E081-3218-B4D5-685B62DD5215> '/Users/possum/Library/Developer/Xcode/DerivedData/Eigen-evebslcpurtsfpgvyeiiqlfvahhh/Build/Intermediates.noindex/Previews/Eigen/Products/Debug/Eigen.app/Contents
    ]

Frames: [
    Frame {
        imageIndex: 0
        imageOffset: 309280
        symbol: __abort_with_payload
        symbolLocation: 8
    }
    Frame {
        imageIndex: 0
        imageOffset: 338400
        symbol: abort_with_payload_wrapper_internal
        symbolLocation: 104
    }
    Frame {
        imageIndex: 0
        imageOffset: 338452
        symbol: abort_with_payload
        symbolLocation: 16
    }
    Frame {
        imageIndex: 0
        imageOffset: 43324
        symbol: dyld4::halt(char const*)
        symbolLocation: 328
    }
    Frame {
        imageIndex: 0
        imageOffset: 24504
        symbol: dyld4::prepare(dyld4::APIs&, dyld3::MachOAnalyzer const*)
        symbolLocation: 3644
    }
    Frame {
        imageIndex: 0
        imageOffset: 20588
        symbol: start
        symbolLocation: 488
    }
]

Images: [
    Image {
        uuid: d9c2a46e-8dc4-3950-9d6a-f799e8ccb683
        base: 80707584
        name: dyld
        path: /usr/lib/dyld
        arch: arm64e
    }
]

==================================

|  FailedToLaunchError: Failed to launch Eigen.app
|
|  /Users/possum/Library/Developer/Xcode/DerivedData/Eigen-evebslcpurtsfpgvyeiiqlfvahhh/Build/Intermediates.noindex/Previews/Eigen/Products/Debug/Eigen.app
|
|  ==================================
|
|  |  HumanReadableSwiftError
|  |
|  |  UnknownApplicationLaunchFailure: UnknownApplicationLaunchFailure()

Compiling the project:
dyld[11211]: Library not loaded: @rpath/AFNetworking.framework/Versions/A/AFNetworking
  Referenced from: /Users/possum/Library/Developer/Xcode/DerivedData/Eigen-evebslcpurtsfpgvyeiiqlfvahhh/Build/Products/Debug/Eigen.app/Contents/MacOS/Eigen
  Reason: tried: '/Users/possum/Library/Developer/Xcode/DerivedData/Eigen-evebslcpurtsfpgvyeiiqlfvahhh/Build/Products/Debug/AFNetworking.framework/Versions/A/AFNetworking' (no such file), '/Users/possum/Library/Developer/Xcode/DerivedData/Eigen-evebslcpurtsfpgvyeiiqlfvahhh/Build/Products/Debug/PackageFrameworks/AFNetworking.framework/Versions/A/AFNetworking' (no such file), '/usr/lib/swift/AFNetworking.framework/Versions/A/AFNetworking' (no such file), '/Users/possum/Library/Developer/Xcode/DerivedData/Eigen-evebslcpurtsfpgvyeiiqlfvahhh/Build/Products/Debug/Eigen.app/Contents/MacOS/../Frameworks/AFNetworking.framework/Versions/A/AFNetworking' (code signature in <E2186F13-E63E-30B9-A8B2-E5B778E8868F> '/Users/possum/Library/Developer/Xcode/DerivedData/Eigen-evebslcpurtsfpgvyeiiqlfvahhh/Build/Products/Debug/Eigen.app/Contents/Frameworks/AFNetworking.framework/Versions/A/AFNetworking' not valid for use in process: mapped file has no Team ID and is not a platform binary (signed with custom identity or adhoc?)), '/Users/possum/Library/Developer/Xcode/DerivedData/Eigen-evebslcpurtsfpgvyeiiqlfvahhh/Build/Products/Debug/Eigen.app/Contents/MacOS/Frameworks/AFNetworking.framework/Versions/A/AFNetworking' (no such file), '/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/macosx/AFNetworking.framework/Versions/A/AFNetworking' (no such file), '/Users/possum/Library/Developer/Xcode/DerivedData/Eigen-evebslcpurtsfpgvyeiiqlfvahhh/Build/Products/Debug/Eigen.app/Contents/MacOS/../Frameworks/AFNetworking.framework/Versions/A/AFNetworking' (code signature in <E2186F13-E63E-30B9-A8B2-E5B778E8868F> '/Users/possum/Library/Developer/Xcode/DerivedData/Eigen-evebslcpurtsfpgvyeiiqlfvahhh/Build/Products/Debug/Eigen.app/Contents/Frameworks/AFNetworking.framework/Versions/A/AFNetworking' not valid for use in process: mapped file has no Team ID and is not a platform binary (signed with custom identity or adhoc?)), '/usr/lib/swift/AFNetworking.framework/Versions/A/AFNetworking' (no such file), '/Users/possum/Library/Developer/Xcode/DerivedData/Eigen-evebslcpurtsfpgvyeiiqlfvahhh/Build/Products/Debug/Eigen.app/Contents/MacOS/../Frameworks/AFNetworking.framework/Versions/A/AFNetworking' (code signature in <E2186F13-E63E-30B9-A8B2-E5B778E8868F> '/Users/possum/Library/Developer/Xcode/DerivedData/Eigen-evebslcpurtsfpgvyeiiqlfvahhh/Build/Products/Debug/Eigen.app/Contents/Frameworks/AFNetworking.framework/Versions/A/AFNetworking' not valid for use in process: mapped file has no Team ID and is not a platform binary (signed with custom identity or adhoc?)), '/Users/possum/Library/Developer/Xcode/DerivedData/Eigen-evebslcpurtsfpgvyeiiqlfvahhh/Build/Products/Debug/Eigen.app/Contents/MacOS/Frameworks/AFNetworking.framework/Versions/A/AFNetworking' (no such file), '/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/macosx/AFNetworking.framework/Versions/A/AFNetworking' (no such file), '/Users/possum/Library/Developer/Xcode/DerivedData/Eigen-evebslcpurtsfpgvyeiiqlfvahhh/Build/Products/Debug/Eigen.app/Contents/MacOS/../Frameworks/AFNetworking.framework/Versions/A/AFNetworking' (code signature in <E2186F13-E63E-30B9-A8B2-E5B778E8868F> '/Users/possum/Library/Developer/Xcode/DerivedData/Eigen-evebslcpurtsfpgvyeiiqlfvahhh/Build/Products/Debug/Eigen.app/Contents/Frameworks/AFNetworking.framework/Versions/A/AFNetworking' not valid for use in process: mapped file has no Team ID and is not a platform binary (signed with custom identity or adhoc?)), '/Library/Frameworks/AFNetworking.framework/Versions/A/AFNetworking' (no such file), '/System/Library/Frameworks/AFNetworking.framework/Versions/A/AFNetworking' (no such file)
(lldb)

If you need some more info please let me know.

Hi, thanks for opening this issue! I appreciate the detail!
When you are running pod install, is it under Rosetta? I have an M1 mac as well and I remember that when I tried to run Cocoapods natively it didn't work right unfortunately. If you would be willing to run arch -x86_64 pod install and see if that works it would be great.
I also need to fix the GH actions builds, they haven't been working properly for a while now.

I'm going to try to run the project from scratch again and see if I encounter this issue

If you'd like, I built a binary here that should work, it's not codesigned though so you may have to right-click and press open to get it to run.
Eigen.zip

It looks like this issue happens when code signing is disabled, since Apple doesn't like loading in libraries that are not code signed. If you are able to add your developer team to the "Signing and Capabilities" section of the project file and build it (you'll probably have to change the bundle id), then everything should work correctly. I'm exploring options right now to try to get it to work without having to code sign.

If you'd like, I built a binary here that should work, it's not codesigned though so you may have to right-click and press open to get it to run. Eigen.zip

Still won't work :(

Log:
report.txt

Hi, thanks for opening this issue! I appreciate the detail!
When you are running pod install, is it under Rosetta? I have an M1 mac as well and I remember that when I tried to run Cocoapods natively it didn't work right unfortunately. If you would be willing to run arch -x86_64 pod install and see if that works it would be great.
I also need to fix the GH actions builds, they haven't been working properly for a while now.

Btw if you install it through homebrew then you don't have to use arch -x86_64 👀
And for some reason it didn't work for me with arch -x86_64 lol, so I reinstalled it from brew

Btw if you install it through homebrew then you don't have to use arch -x86_64 👀 And for some reason it didn't work for me with arch -x86_64 lol, so I reinstalled it from brew

That's great to know, thank you! I had no idea
Here's another shot at it, I've disabled library validation on this build and I was able to extract and run locally:
Eigen.tar.gz
Thanks for your patience

Here's another shot at it, I've disabled library validation on this build and I was able to extract and run locally: Eigen.tar.gz

And now it works!

And also some not related to this issue question: how do I verify the session on this client?

Great!
If you click on your name in the bottom left corner, it'll take you to the settings screen where you can scroll down to the "recovery password" text field and input your recovery password (sometimes called in Element your security key) to download the encryption keys from the homeserver. This will mark your device as verified to others.
I'm going to try to revamp the onboarding process in a few days, because right now it's kinda all over the place lol


Return regular view data if a route is not served by Statamic

Fixes #63

Maybe there is a better way to detect if a route is served by Statamic than checking for the presence of$variables['cp_url'].

What if folks want the augmented data though?

What if folks want the augmented data though?

When do you want to have an array of data instead of the object in Laravel views? Maybe my experience with Statamic and Laravel is too limited to think of a use case for this.

Thank you 😌


Fix code scanning alert - Unsafe expansion of self-closing HTML tag

Tracking issue for:

[x] https://github.com/lourcastillo/lourcastillo.github.io/security/code-scanning/23

Fix code scanning alert


Plugin initialization failed Every 7 days

I always need to renew my refresh token every 7 days.
Is there something I can do to prevent this?
Thanks,
Matthias

I've never seen this before... I've been using the same token for years.  What message do you get?

This typically means your oauth consent screen is set to testing instead of production in the google cloud console. See https://support.google.com/cloud/answer/10311615 for more under Publishing Status and Testing

@Beuk14 : Let us know if this helps.

Yes, this did it for me!
Thank you for the response!


Fix the infinite loop

https://github.com/nandlabs/go-commons/blob/main/clients/rest/request.go#L101 causes an infinite loop on adding content type

Good catch this looks fixed now


What is the purpose of displayFormat ?

The doc states :

Visual format when the input looses focus

Is it supposed to work ?
I checked the source code of inputmask.date.extensions.js and it appears to me that this option is currently ignored.
Thanks for your help !

@gelambert ,
No it is not yet implemented.  The purpose.  Ex while editing you show  23/03/2020, while when you leave the field you show 23 March 2020

@RobinHerbots ,
Understood. Thanks for your quick answer !


[AutoPR hanaonazure/resource-manager] Removing monitoring hana instance API

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6778

(message created by the CI based on PR content)


Refactor configs/const to move most of them into web/app

i have finished it , you can close it now


Adds deploy to heroku button

Makes it possible to deploy app without forking, also requiers user to enter nessecary environment variables.

Greatly improves usability! Really well done @mlonn!
I would request that you decide on what language the descriptions for environment variables are in, English or Swedish.
Technically, we cannot merge this until the changes are approved on the next "sektionsmöte", but I will try to make this happen!


Draft URL Structure (WIP)

/state - CA state data
/state/{electionYear-Month(?)}
/state/{electionYear-Month(?)}/proposition
/cities - all cities in CA with (& without?)data
/city/{cityId}/{cityName} - a city page
/city/{cityId}/{cityName}/{electionYear-Month(?)}
/city/{cityId}/{cityName}/{electionYear-Month(?)}/{position} - overview data for all candidates running for one position in a given election year
/city/{cityId}/{cityName}/{electionYear-Month(?)}/{position}/candidate/{candidateId}/{candidateName} - for a given election only.  will most likely link back to a general 'profile' page for the candidate with info on all elections he/she has run in(?)
/city/{cityId}/{cityName}/{electionYear-Month(?)}/measure/{measureId}
/city/{cityId}/{cityName}/{electionYear-Month(?)}/measure/{measureId}/contributors
/candidate - doesn't resolve
/candidate/{candidateId}/{candidateName} - candidate 'profile' page for any/all elections, city/county/or state level (??)

As we just discussed, adjusting these endpoints to more closely match the API structure will make the client code a lot simpler.
For example: using /locality/{localityId} instead of the city/state prefix will allow for the API client to simply request the API endpoint with the same ID rather than having to resolve the city name back into a locality ID or something.
This comes at the expense of SEO -- your endpoints will definitely have better SEO -- but that is pretty low on our priority list.
As for /candidate, it seems redundant to me to have both the {candidateId} and {candidateName} in the URL

Closing this since I think it's no longer relevant.


Fill Identity deep dive

Description
Fill this document: https://github.com/ipfs/camp/blob/master/DEEP_DIVES/05-identity-for-dapps.md
Acceptance Criteria

[x] Document is filled

PR here: https://github.com/ipfs/camp/pull/66/


IGListBatchUpdates needs header documentation

Pretty barren right now. Even though this is an internal class, we should document what it is and how its used.

going to bump this out of 3.0 since it is internal-only

Hey! I am new here and want to contribute. Since this is starter-task and it is regarding documentation, should I work on it? It will help me understand code too.

@hardikyagnik hell ya!! Docs are an excellent way to get started w/ contributing to a new project. We would absolutely love your help!

Are you still working on this @hardikyagnik, do you mind if I take a stab at this?

@IHEARTCOOKIES No, currently I am not working on this.


Firrtl exception when using firrtl.transforms.Flatten.

Type of issue: bug report

What is the current behavior?

Using the firrtl.transforms.Flatten can sometimes cause the following firrtl exception:
Exception in thread "main" firrtl.FIRRTLException: No EmittedCircuit found! Did you delete any annotations?

@jackkoenig was able to reproduce the error using Flatten as follows:
java -cp ./utils/bin/firrtl.jar firrtl.Driver -i regress/FPU.fir -o out -X verilog -fct firrtl.transforms.Flatten

As for myself, I used InlineInstance in a couple of places, and noticed if I set the custom-transform pass to include Flatten, I also run into this exception:
I have added firrtl.Driver --custom-transforms=firrtl.passes.wiring.WiringTransform,firrtl.passes.InlineInstances,firrtl.transforms.Flatten
In my case, I am using rocket's trait InlineInstance to invoke the InlineAnnotation:
trait InlineInstance { self: chisel3.experimental.BaseModule =>
  chisel3.experimental.annotate(
    new chisel3.experimental.ChiselAnnotation {
      def toFirrtl: firrtl.annotations.Annotation = firrtl.passes.InlineAnnotation(self.toNamed) } )
}

Please tell us about your environment:

firrtl version: 50ba95fe05cc348496425733554be5fc7d797de1
chisel3 version: https://github.com/freechipsproject/chisel3/commit/9a0ce2272c9d5d0a8bdc90e84269749ce054664d

The error:
Total FIRRTL Compile Time: 184664.0 ms
Exception in thread "main" firrtl.FIRRTLException: No EmittedCircuit found! Did you delete any annotations?
... [snip] ...
	at firrtl.CircuitState.getEmittedCircuit(Compiler.scala:48)
	at firrtl.Driver$.$anonfun$execute$1(Driver.scala:260)
	at logger.Logger$.$anonfun$makeScope$2(Logger.scala:138)
	at scala.util.DynamicVariable.withValue(DynamicVariable.scala:58)
	at logger.Logger$.makeScope(Logger.scala:136)
	at firrtl.Driver$.execute(Driver.scala:224)
	at firrtl.Driver$.execute(Driver.scala:302)
	at firrtl.Driver$.main(Driver.scala:318)
	at firrtl.Driver.main(Driver.scala)
make: *** [snip] Error 1

It looks like Flatten, going back to the original PR, would strip all annotations if you ran it without any FlattenAnnotations.
This problem may exist other places. This likely motivates two things going forward:

More attention to coverage (this was a code path that the tests never hit)

A TransformSpec that ensures two related/redundant requirements of all (almost all?) Transforms:

All Transforms are idempotent
All Transofrms are equivalent to IdentityTransform if called with an empty annotation sequence

Good find @ccelio.


Generic constructor with more than one generic type can break syntax highlighting.

JavaScript and TypeScript Nightly version:
Last released - 4/4/2023, 02:09:37
Last updated - 4/4/2023, 18:09:42

Code
export class Foo {
    readonly bar = {
        map: new Map<
            Type1, Type2>([])
    };

    private function() {
        return 1;
    }
}

The code above breaks syntax highlighting, I have also tested in insiders vscode with nightly typescript.

It is fine, if both generics are on the same line as the main type:

If there is only 1 generic, it does slightly better, the highlighting of the generic is wrong, but the rest of the file is ok.

Or if the argument to the constructor is not a list, this it is also recoverable, although both the highlighting of the generic, and the closing angle bracket are wrong.

I just encountered a similar issue in vscode. I noticed that in typescript playground the issue is not present. So I thought the issue is with text mate rules
declare function create<A, B>(action: <A, B>() => Promise<void>): unknown;
declare type A = 'A';
declare type B = 'B';

const obj = {
    func: create<
        A,
        B
    >(async () => { // `>` is highlighted in red.
        const a = 10;
    }),
};

Seems like the issue is with re regent that tries to detect multiline type arguments. Right now it marks the type argument as multiline only if <( <[ <{. Other cases do not. I was trining to fix it but encountered the issue that there are some ambiguous cases with classes.
class First extends Second<
    T
> {

}

// but at the same time we can do

class First extends factoryFunc<
    T
>() {

}

const getFromLS = <T = unknown,>(key: string): T | undefined => {     const value = window.localStorage.getItem(key);     return value ? (JSON.parse(value) as T) : undefined; };
this also break my syntax higlight


chore: standardize npm script names

Prerequisites checklist

[x] I have read the contributing guidelines.

What is the purpose of this pull request?
Refers https://github.com/eslint/eslint/issues/14827

What changes did you make? (Give an overview)
This updates the names of the scripts in package.json to be consistent with the new standard.
Is there anything you'd like reviewers to focus on?
We may need to update the release related scripts on Jenkins before merging this PR.

We may need to update the release related scripts on Jenkins before merging this PR.

Updated.


How to use in programmatically

Hi
Please let me know about using in programmatically.
Thank You

Hi, try the following code
    var avatar : SwiftyAvatar
    avatar  = SwiftyAvatar(frame:CGRectMake(10, 50, 100, 100))
    avatar.background = UIColor.whiteColor()
    avatar.borderColor = UIColor.redColor()
    avatar.borderWidth = 5
    avatar.roundness = 2

    self.view.addSubview(avatar)


HDDS-5318. Intermittent failure in TestOzoneManagerDoubleBufferWithOMResponse

What changes were proposed in this pull request?
TestOzoneManagerDoubleBufferWithOMResponse is flaky because double buffer involves another thread.  flushTransactions updates flushedTransactionCount, then somewhat later also updates lastAppliedIndex.  The test waits for the former, but simply checks the latter with assertion.  We need to wait for this update, too.
https://issues.apache.org/jira/browse/HDDS-5318
How was this patch tested?
Repeated TestOzoneManagerDoubleBufferWithOMResponse 50x:
https://github.com/adoroszlai/hadoop-ozone/runs/2771888499
Regular CI (pending):
https://github.com/adoroszlai/hadoop-ozone/actions/runs/918284218

Thanks @hanishakoneru for the review.


Update references

choonkending/react-webpack-node --> reactGo/reactGo
Should also update the name in app.json and package.json ?

@choonkending The name in package.json and app.json, should I update it, or you'll do it? 😄

It's a race! I probably wont get to it in time cause I'm prepping some slides :P


fix: small errors

Thank you! @all-contributors please add 0xflotus for content

Coverage decreased (-1.4%) to 68.564% when pulling 68da3bc7867430825959d4208d421a14abf2a1a2 on 0xflotus:patch-1 into bfb98e76e8f4a2ba9abe67fd554485db4a5f0b63 on quirrel-dev:main.


ci: download and cache Trivy vulnerability DB

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.007%) to 57.306%

Files with Coverage Reduction
New Missed Lines
%

pkg/config/config.go
2
70.63%

internal/integrations/v4/testhelp/testemit/testemit.go
2
90.63%

Totals

Change from base Build<PHONE_NUMBER>1:
-0.007%

Covered Lines:
15354

Relevant Lines:
26793

💛  - Coveralls


Document best practices for native side of app to communicate with native module

Autolinking will create a ReactPackageProvider for every linked module. However the native side of the app doesn't have a way to access the [native] instance of the native module to negotiate or communicate properties/call APIs.
Workaround: static APIs/properties
It would be good to provide a mechanism to avoid this.

Related to: #333 and #198


Theme is not updated properly

Version
Tried with 1.0.10, it might happen with previous versions.
Reproduction
http://www.webpackbin.com/EyB9mzGWf
Steps to reproduce
Just click the button on the above WebpackBin, open browser console log to see the log.
Expected Behavior
It should update the correct theme.
Actual Behavior
It updates the old theme.
This issue has been raised on gitter.

One clarification that I think will be useful in debugging here is that it doesn't update only on the first click. However, if you click the button again it updates but is always one update "behind".
I haven't had a chance to dive into this bug yet, but my guess is the issue starts with this line of code: https://github.com/styled-components/styled-components/blob/master/src/models/ThemeProvider.js#L50

It works fine if using shouldComponentUpdate instead of componentWillReceiveProps to publish event for new theme.

@mxstbr any idea why shouldComponentUpdate works here and componentWillReceiveProps doesn't?

I have no idea whatsoever.

@gaearon could you please give us a hand on this? what is the difference between componentWillReceiveProps and shouldComponentUpdate in this case?

const theme = passedTheme || this.props.theme

You are reading it from current props. But you want nextProps.

Oh wait, I misunderstood the argument. Never mind.

@gaearon is this a styled-components bug or otherwise?

This should be fixed with #253, will release a new version with that fix shortly!


Update easymock to 5.3.0

About this PR
📦 Updates org.easymock:easymock from 5.2.0 to 5.3.0
📜 Release Notes
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

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

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.easymock", artifactId = "easymock" }
}]

labels: test-library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #2926.

Superseded by #2926.


Transition from SEAL v3.5 to v3.6

According to the SEAL v3.6.0 release notes, there were a number of changes that either introduced new features or (potentially) break the existing API. Therefore, at least all explicitly mentioned major changes should be verified manually in SEAL.jl to make sure that the Julia wrapper is up to date again.
Major API Changes

[x] All C++ enum labels are consistently in lowercase. Most importantly, scheme_type::BFV and scheme_type::CKKS are changed to scheme_type::bfv and scheme_type::ckks.
[x] Changed seal::SEAL_BYTE to seal::seal_byte; all uppercase names are used only for preprocessor macros.
[x] Removed BatchEncoder API for encoding and decoding Plaintext objects inplace. This is because a Plaintext object with slot-data written into the coefficients is (confusingly) not valid to be used for encryption.
[x] Removed IntegerEncoder and BigUInt classes. IntegerEncoder results in inefficient homomorphic evaluation and lacks sane correctness properties, so it was basically impossible to use in real applications. The BigUInt class was only used by the IntegerEncoder.
[ ] All Encryptor::encrypt variants have now two overloads: one that takes a Ciphertext out-parameter, and one that returns a Serializable.
[x] Changed the names of the public key generation functions to clearly express that a new key is created each time, e.g., KeyGenerator::create_public_key.
[x] Removed the KeyGenerator::relin_keys_local and KeyGenerator::galois_keys_local functions.
These were poorly named and have been replaced with overloads of KeyGenerator::create_relin_keys and KeyGenerator::create_galois_keys that take an out-parameter of type RelinKeys or GaloisKeys.
[ ] Renamed IntArray to DynArray (dynamic array) and removed unnecessary limitations on the object type template parameter.
[ ] Added public API for modular reduction to the Modulus class.
[ ] Added API for creating DynArray and Plaintext objects from a gsl::spanstd::uint64_t (C++) or IEnumerable (C#).

Minor API Changes

[ ] Added std::hash implementation for EncryptionParameters (in addition to parms_id_type) so it is possible to create e.g. std::unordered_map of EncryptionParameters.
[ ] Added API to UniformRandomGeneratorFactory to find whether the factory uses a default seed and to retrieve that seed.
[ ] Added const overloads for DynArray::begin and DynArray::end.
[ ] Added a Shake256PRNG and Shake256PRNGFactory classes.
Renamed BlakePRNG class to Blake2xbPRNG, and BlakePRNGFactory class to Blake2xbPRNGFactory.
[ ] Added a serializable UniformRandomGeneratorInfo class that represents the type of an extendable output function and a seed value.
[ ] Added native/src/seal/version.h defining a struct SEALVersion.
This is used internally to route deserialization logic to correct functions depending on loaded SEALHeader version.

Other

[ ] Added seal::util::DWTHandler and seal::util::Arithmetic class templates that unify the implementation of FFT (used by CKKSEncoder) and NTT (used by polynomial arithmetic).

I will close this with the current status. If a user is interested in one of the new features, just create an issue and we will add it here.


Remove usage of deprecated .spec.running field

What this PR does / why we need it:
The .spec.running field is deprecated, therefore we should runStrategy instead.
For more info, look at:
kubevirt/kubevirt#11993i
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note:

/lgtm
But @cwilkers will have to approve. Which brings up the need for us to find some new reviewer/approvers for this repo.


Merge request for disk migrate

As we've changed our fork too far, please look at:
https://github.com/Luceos/OnApp-PHP-Wrapper-External/blob/3.2.0/src/Disk.php#L237 and the related method somewhat further in the code to implement disk migrations to a different store.
This functionality has been tested.

closed, has been impelemented


Can not encrypt backup files.

Whenever I enable encryption using the BACKUP_ENCRYPTION_KEY variable, backup files aren't created and there are errors in the logs.
I think the problem is in the section of the backup script;
  # If a password is provided, run it through openssl   if [ -n "$BACKUP_ENCRYPTION_KEY" ]; then     BACKUP_FILE=$BACKUP_FILE.aes256     tar -czf - -C $SQL_BACKUP_DIR $SQL_NAME -C $DATA $FILES | openssl enc -e -aes256 -salt -pbkdf2 -pass pass:${BACKUP_ENCRYPTION_KEY} -out $BACKUP_FILE   else     tar -czf $BACKUP_FILE -C $SQL_BACKUP_DIR $SQL_NAME -C $DATA $FILES   fi
Here's the error log.
Backup file created at /data/backups/bw_backup_2023-09-08-141200.tar.gz.aes256
Running email backup
Email error: Can't stat /data/backups/bw_backup_2023-09-08-141200.tar.gz.aes256: No such file or directory
/data/backups/bw_backup_2023-09-08-141200.tar.gz.aes256: unable to attach file.

If I disable encryption key, it manages to take backup
Running backup to: email Backup file created at /data/backups/bw_backup_2023-09-08-142800.tar.gz Running email backup Sent e-mail (Bitwarden Backup<EMAIL_ADDRESS>- bw_backup_2023-09-08-142800.tar.gz) to<EMAIL_ADDRESS>Here is my .env file I redacted personal information
### GLOBAL VARIABLES ###

# The fully-qualified domain name for Bitwarden - what address do you want Bitwarden accessible?
# Do not include the protocol (http/https), that is added when needed in docker-compose.yml
# Used for caddy proxy and ddns with Cloudflare
<EMAIL_ADDRESS>
# Timezone - used by some containers for logs / cron
# Find your location on this list and use the value in TZ Database Name, e.g Europe/Rome:
#   https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
TZ=Europe/#####.###

# SMTP settings for Bitwarden and fail2ban
# Uncomment and fill in details if you want to use e-mail invitations from bitwarden and e-mail alerts with fail2ban
# SMTP_SECURITY should be either starttls, force_tls, or off
# (see https://github.com/dani-garcia/vaultwarden/wiki/SMTP-Configuration)

SMTP_HOST=#####.###
SMTP_FROM=#####.###
SMTP_PORT=#####.###
SMTP_USERNAME=#####.###
SMTP_PASSWORD=#####.###
SMTP_SECURITY=#####.###
# For fail2ban, YES or NO
SMTP_TLS=#####.###
SMTP_AUTH_MECHANISM="Login"

### BITWARDEN VARIABLES ###

# Setting up Bitwarden for the first time can be done in two ways:
# Uncomment the method you want to use / comment the one you don't
# Method 1. [RECOMMENDED] because it avoids the admin page entirely; using the admin
#   page overrides these environmental variables which can cause confusion.
#   1. Set up your primary account(s) while SIGNUPS_ALLOWED=true
#   2. Set SIGNUPS_ALLOWED=false
#   3. Set the SMTP details above to enable e-mail invitation
#   4. Invite other users from within Bitwarden
#   Keep ADMIN_TOKEN blank to disable access to the admin page entirely.
SIGNUPS_ALLOWED=false
#ADMIN_TOKEN=
VAULTWARDEN_ADMIN_TOKEN=#####.###
# Method 2. Use the admin page to create your first user(s) then disable it.
#   1. Set ADMIN_TOKEN using gthe command `openssl rand -base64 48`
#   2. Use the admin page (/admin) to create your initial user(s).
#   3. Disable the admin page by clearing the token (ADMIN_TOKEN=)
#SIGNUPS_ALLOWED=false
#ADMIN_TOKEN=
# Note on ADMIN_TOKEN: https://github.com/dani-garcia/vaultwarden/wiki/Enabling-admin-page#secure-the-admin_token

## Enables push notifications (requires key and id from https://bitwarden.com/host)
# PUSH_ENABLED=true
PUSH_INSTALLATION_ID=#####.###
PUSH_INSTALLATION_KEY=#####.###
## Don't change this unless you know what you're doing.
# PUSH_RELAY_BASE_URI=https://push.bitwarden.com

# Specify YUBIKEY info if desired
#YUBICO_CLIENT_ID=
#YUBICO_SECRET_KEY=
#YUBICO_SERVER=

# Specfiy which user email addresses can create organizations
# Leave blank to allow all users
<EMAIL_ADDRESS>
# Bitwarden Backup Options
#
#
# GENERAL OPTIONS:
#
# How often to run the backup script; default is daily at midnight
#BACKUP_SCHEDULE=0 0 * * *
BACKUP_SCHEDULE=*/2 * * * *
# How many days of backups to keep
BACKUP_DAYS=30
# Directory to place backups in (& sync from in rclone)
BACKUP_DIR=/data/backups
# Optional encryption key for backup
BACKUP_ENCRYPTION_KEY="test"
# Email address to send backup (BACKUP=email) or notifications (BACKUP_NOTIFY=true)
BACKUP_EMAIL_TO="#####.###"
# Send email notification for rclone|local backup jobs
BACKUP_EMAIL_NOTIFY=true
#
#
# Backup type is any combination of local|email|rclone - e.g., email,rclone
# If you use rclone, follow the instructions below
BACKUP=email
#
# RCLONE BACKUP OPTIONS:
#
# rclone first time run instructions:
#   1. Uncomment lines below and `docker-compose up -d`
#   2. With the backup container running, configure rclone with the following command:
#      `sudo docker exec -it backup ash -c 'rclone config --config $BACKUP_RCLONE_CONF'`
#   3. Follow the prompts and instructions at https://rclone.org/remote_setup/ - you
#      will most likely need to download a rclone on another computer (it is portable)
#      to authorize.
#   4. The script should run as normal with a working configuration file
#BACKUP_RCLONE_CONF=/data/rclone/rclone.conf
#BACKUP_RCLONE_DEST=/bw_backup

### PROXY / CADDY VARIABLES ###

# EMAIL address to use with Let's Encrypt certificate provisioning
<EMAIL_ADDRESS>

### DDNS VARIABLES ###

# These variables are only necessary if you are using DDNS / comment them out if you don't use ddns
# Enter user id (use `id -u` to determine your user id)
#PUID=
# Enter group id (use `id -g` to determine your group id)
#PGID=

### COUNTRY BLOCKING VARIABLES ###

# Put any countries you want to block here using their ISO 3166-1 alpha-2 code (https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2)
# Defaullt is China (CN), Hong Kong (HK), and Australia (AU) because gcloud free tier charges egress to those countries
# Data is pulled from www.ipdeny.com
COUNTRIES=CN HK AU

# How often to update the ip block list - default is daily at midnight; see https://en.wikipedia.org/wiki/Cron#CRON_expression
COUNTRYBLOCK_SCHEDULE=0 0 * * *

### WATCHTOWER VARIABLES ###

# How often should watchtower check for updated container images? Default is every Sunday at 3am
WATCHTOWER_SCHEDULE=0 0 3 ? * 0

I believe you might be using an older version of docker-compose.yml, I think you're using the built-in backup feature in the bitwarden container. Since a few months ago, the backup feature has been pulled out into its own docker image (https://github.com/dadatuputi/bwgc_backup). So, not running the latest version is probably accounting for some of your issues.
You did prompt me to look into the backup code and test the encryption function, and found a bug, so thanks for that.
I recommend that you pull the latest from the repo and skim the .env.template to make sure no breaking changes have happened since you last pulled.
You may have to update your BACKUP_RCLONE_CONF env var if you're using rclone (see https://github.com/dadatuputi/bitwarden_gcloud/wiki/Backup#troubleshooting-rclone-creation).

@dadatuputi I don't think I have an older version because I just found out about this project. I updated with docker-compose up -d but still got the same problem. I think I also have the openssl package.
Here is terminal log;

$ docker-compose up -d
	proxy is up-to-date
	bitwarden is up-to-date
	ddns is up-to-date
	fail2ban is up-to-date
	watchtower is up-to-date
	countryblock is up-to-date
	Recreating backup ... done
$ docker logs backup
	Removing any existing crontab entries for backup.sh
	Adding backup.sh crontab entry (*/2 * * * *)
	Starting the cron daemon
$ docker logs backup
	Removing any existing crontab entries for backup.sh
	Adding backup.sh crontab entry (*/2 * * * *)
	Starting the cron daemon
	Finished configuring email.
	Running backup to: email
	Backup file created at /data/backups/bw_backup_2023-09-08-162001.tar.gz.aes256
	Running email backup
	Email error: Can't stat /data/backups/bw_backup_2023-09-08-162001.tar.gz.aes256: No such file or directory
	/data/backups/bw_backup_2023-09-08-162001.tar.gz.aes256: unable to attach file.

$ openssl help
	Standard commands
	asn1parse         ca                ciphers           cms
	crl               crl2pkcs7         dgst              dhparam
	dsa               dsaparam          ec                ecparam
	enc               engine            errstr            gendsa
	genpkey           genrsa            help              list
	nseq              ocsp              passwd            pkcs12
	pkcs7             pkcs8             pkey              pkeyparam
	pkeyutl           prime             rand              rehash
	req               rsa               rsautl            s_client
	s_server          s_time            sess_id           smime
	speed             spkac             srp               storeutl
	ts                verify            version           x509

	Message Digest commands (see the `dgst' command for more details)
	blake2b512        blake2s256        gost              md4
	md5               mdc2              rmd160            sha1
	sha224            sha256            sha3-224          sha3-256
	sha3-384          sha3-512          sha384            sha512
	sha512-224        sha512-256        shake128          shake256
	sm3

	Cipher commands (see the `enc' command for more details)
	aes-128-cbc       aes-128-ecb       aes-192-cbc       aes-192-ecb
	aes-256-cbc       aes-256-ecb       aria-128-cbc      aria-128-cfb
	aria-128-cfb1     aria-128-cfb8     aria-128-ctr      aria-128-ecb
	aria-128-ofb      aria-192-cbc      aria-192-cfb      aria-192-cfb1
	aria-192-cfb8     aria-192-ctr      aria-192-ecb      aria-192-ofb
	aria-256-cbc      aria-256-cfb      aria-256-cfb1     aria-256-cfb8
	aria-256-ctr      aria-256-ecb      aria-256-ofb      base64
	bf                bf-cbc            bf-cfb            bf-ecb
	bf-ofb            camellia-128-cbc  camellia-128-ecb  camellia-192-cbc
	camellia-192-ecb  camellia-256-cbc  camellia-256-ecb  cast
	cast-cbc          cast5-cbc         cast5-cfb         cast5-ecb
	cast5-ofb         des               des-cbc           des-cfb
	des-ecb           des-ede           des-ede-cbc       des-ede-cfb
	des-ede-ofb       des-ede3          des-ede3-cbc      des-ede3-cfb
	des-ede3-ofb      des-ofb           des3              desx
	idea              idea-cbc          idea-cfb          idea-ecb
	idea-ofb          rc2               rc2-40-cbc        rc2-64-cbc
	rc2-cbc           rc2-cfb           rc2-ecb           rc2-ofb
	rc4               rc4-40            rc5               rc5-cbc
	rc5-cfb           rc5-ecb           rc5-ofb           seed
	seed-cbc          seed-cfb          seed-ecb          seed-ofb
	sm4-cbc           sm4-cfb           sm4-ctr           sm4-ecb
	sm4-ofb

Here is my docker.yml;

$ cat docker-compose.yml
	version: '3.4'

	x-logging: &default-logging
	  logging:
		driver: "json-file"
		options:
		  max-size: "10m"
		  max-file: "10"
		  compress: "true"

	services:
	  bitwarden:
		# Standard Bitwarden is very resource-heavy and cannot run on micro cloud instances
		# Vaultwarden is a Rust (mostly) feature-complete implementation of Bitwarden
		# https://github.com/dani-garcia/vaultwarden
		image: vaultwarden/server:alpine
		restart: always
		container_name: bitwarden
		depends_on:
		- proxy
		<<: *default-logging
		volumes:
		- ${PWD}/bitwarden:/data
		environment:
		- LOG_FILE=/data/bitwarden.log
		- SHOW_PASSWORD_HINT=false
		- DOMAIN=https://${DOMAIN}          # DOMAIN is set in .env but doesn't have protocol prefix
		- IP_HEADER=X-Forwarded-For
		- ADMIN_TOKEN=${VAULTWARDEN_ADMIN_TOKEN}                       # Value-less variables are set in .env
		- SIGNUPS_ALLOWED
		- SMTP_HOST
		- SMTP_FROM
		- SMTP_FROM_NAME=Bitwarden (${DOMAIN})
		- SMTP_PORT
		- SMTP_SECURITY
		- SMTP_USERNAME
		- SMTP_PASSWORD
		- PUSH_ENABLED
		- PUSH_INSTALLATION_ID
		- PUSH_INSTALLATION_KEY
		- YUBICO_CLIENT_ID
		- YUBICO_SECRET_KEY
		- YUBICO_SERVER
		- ORG_CREATION_USERS
		- TZ

	  backup:
		#build: ./docker/backup                                     # backup, in case container registry is not responsive
		image: ghcr.io/dadatuputi/bwgc_backup:master                # from https://github.com/dadatuputi/bwgc_backup
		restart: on-failure
		container_name: backup
		depends_on:
		- bitwarden
		<<: *default-logging
		volumes:
		  - ${PWD}/bitwarden:/data:ro
		  - ${PWD}/bitwarden/rclone:/data/rclone
		  - ${PWD}/bitwarden/backups:/data/backups
		environment:
		- BACKUP                            # Value-less variables are set in .env
		- BACKUP_SCHEDULE
		- BACKUP_DAYS
		- BACKUP_DIR
		- BACKUP_ENCRYPTION_KEY
		- BACKUP_EMAIL_TO
		- BACKUP_EMAIL_NOTIFY
		- BACKUP_RCLONE_CONF
		- BACKUP_RCLONE_DEST
		- SMTP_HOST
		- SMTP_FROM
		- SMTP_FROM_NAME=Bitwarden Backup (${DOMAIN})
		- SMTP_PORT
		- SMTP_SECURITY
		- SMTP_USERNAME
		- SMTP_PASSWORD
		- TZ

	  proxy:
		# Caddy provides an automatic HTTPS reverse proxy with Let's Encrypt cert provisioning
		# Uses local Dockerfile to include tzdata package
		# https://caddyserver.com/
		#build: ./docker/proxy                              # backup, in case container registry is not responsive
		image: ghcr.io/dadatuputi/bwgc_caddy:master         # from https://github.com/dadatuputi/bwgc_proxy
		restart: always
		container_name: proxy
		<<: *default-logging
		volumes:
		- ${PWD}/caddy/Caddyfile:/etc/caddy/Caddyfile:ro
		- ${PWD}/caddy/data:/data
		- caddycerts:/root/.caddy
		ports:
		- 80:80                             # Port 80 is necessary for Let's Encrypt ACME
		- 443:443
		environment:
		- ACME_AGREE=true                   # agree to ACME for auto HTTPS
		- DOMAIN                            # Value-less variables are set in .env
		- EMAIL
		- TZ

	  ddns:
		# This provides a ddclient dynamic dns updating cron which is as simple as running it
		# and editing the ddns/config/ddclient.conf file
		# https://github.com/linuxserver/docker-ddclient
		image: linuxserver/ddclient
		restart: always
		container_name: ddns
		<<: *default-logging
		depends_on:
		- bitwarden
		volumes:
		- ${PWD}/ddns:/config
		environment:
		- PUID
		- PGID
		- TZ

	  fail2ban:
		# Implements fail2ban functionality, banning ips that
		# try to bruteforce your vault
		# https://github.com/dani-garcia/vaultwarden/wiki/Fail2Ban-Setup
		# https://github.com/crazy-max/docker-fail2ban
		image: crazymax/fail2ban:latest
		restart: always
		container_name: fail2ban
		<<: *default-logging
		depends_on:
		- bitwarden
		volumes:
		- ${PWD}/fail2ban:/data
		- ${PWD}/bitwarden:/bitwarden:ro
		network_mode: "host"
		privileged: true
		cap_add:
		- NET_ADMIN
		- NET_RAW
		environment:
		- F2B_DB_PURGE_AGE=30d
		- F2B_LOG_TARGET=/data/fail2ban.log
		- F2B_LOG_LEVEL=INFO
		- F2B_IPTABLES_CHAIN=INPUT
		- SSMTP_HOST=${SMTP_HOST}
		- SSMTP_PORT=${SMTP_PORT}
		- SSMTP_USER=${SMTP_USERNAME}
		- SSMTP_PASSWORD=${SMTP_PASSWORD}
		- SSMTP_HOSTNAME=Bitwarden (${DOMAIN})
		- SSMTP_TLS=${SMTP_TLS}
		- SSMTP_STARTTLS=YES
		- TZ

	  countryblock:
		# The block script will block any country (defaults to CN and AU)
		# Requires cap_add as listed and privileged because it uses iptables and ipset
		# https://hub.docker.com/_/alpine/
		#build: ./docker/countryblock                       # backup, in case container registry is not responsive
		image: ghcr.io/dadatuputi/bwgc_countryblock:master  # from https://github.com/dadatuputi/bwgc_countryblock
		restart: always
		container_name: countryblock
		<<: *default-logging
		depends_on:
		- bitwarden
		network_mode: "host"
		privileged: true
		cap_add:
		- NET_ADMIN
		- NET_RAW
		environment:
		- COUNTRIES
		- COUNTRYBLOCK_SCHEDULE
		- TZ

	  watchtower:
		# Watchtower will pull down your new image, gracefully shut down your existing container
		# and restart it with the same options that were used when it was deployed initially
		# https://github.com/containrrr/watchtower
		image: containrrr/watchtower
		restart: always
		container_name: watchtower
		<<: *default-logging
		depends_on:
		- bitwarden
		volumes:
		- /var/run/docker.sock:/var/run/docker.sock
		environment:
		- WATCHTOWER_CLEANUP=true
		- WATCHTOWER_SCHEDULE
		- TZ

	volumes:
	  caddycerts:

Oh, you are probably just running into the same error that I did, and fixed about an hour ago. Try a docker-compose pull and you should get the new backup image. Give that a try.

@dadatuputi It's working, thank you so much ❤