kata-runtime installation dependency for qemu-*  is wrong

The installation dependencies for kata-runtime is not correctly set for RPM based distributions.
Because of this, an upgrade of the kata packages version results in not updating qemu-* packages.
These are the current dependencies for kata-runtime:
$ zypper info --requires kata-runtime
...
Requires       : [12]
    libpthread.so.0()(64bit)
    libpthread.so.0(GLIBC_2.2.5)(64bit)
    libpthread.so.0(GLIBC_2.3.2)(64bit)
    libc.so.6(GLIBC_2.2.5)(64bit)
    /bin/bash
    kata-containers-image >= 1.3.0~rc1-34
    kata-ksm-throttler >= 1.3.0~rc1+git.48a9568-35
    kata-linux-container >= <IP_ADDRESS>-137
    kata-proxy >= 1.3.0~rc1+git.981fef4-34
    kata-shim >= 1.3.0~rc1+git.9b2891c-35
    qemu-lite >= 2.11.0-50
    qemu-vanilla >= 2.11.2-4

When comparing the listed dependency with a former qemu-lite version:
$ zypper vcmp 2.11.0-50 2.11.0+git.a39e0b3e82-48.2.x86_64
2.11.0-50 is older than 2.11.0+git.a39e0b3e82-48.2.x86_6

This means than when upgrading to a new version of kata-runtime, qemu will not be upgraded.
This can potentially lead to errors such as: Failed to check if grpc server is working: rpc error: code = DeadlineExceeded desc = context deadline exceeded, as in kata-containers/runtime#702, kata-containers/runtime#516, kata-containers/runtime#576, kata-containers/runtime#626, ...

Ouch! Good catch @marcov - feel free to assign yourself as well (or unassign @jcvenegas if you have the fix :)

@jodh-intel: I tried that but being a member of kata-containers/packaging is not enough to have admin rights on this repo.

Hi @marcov - I had a check up - yeah, you have admin rights on a few repos, and read on the rest.
I can see the summary at https://github.com/orgs/kata-containers/people/marcov - if you can see that.
I'll assign this to you. I guess the level of repo control for members might need more refining...

@grahamwhaley thanks for checking. Lol that link is 404 for me :disappointed:


Create a code of conduct file

Create a code of conduct file.....assign me this issue and i will make a pr for this issue .

hey I was just thinking the same thing and here you go for your code of conduct file as the backbone (with further modifications)
Code of Conduct for Coders.txt

I'd like to make and update the "code of conduct" file, can you please assign it to me?

Can you assign me this issue?

@geetanj16 You can go ahead and work on it.


Second digit not working on time field after previous data is cleared

Provide a general summary of the issue here
If we fill the minutes field in timepicker and then clear everything using backspace, and then try to fill the date again, the first digit is replaced with the second digit.
🤔 Expected Behavior?
The fields should get updated properly based on the key pressed after clearing.
😯 Current Behavior
After clearing, the first digit of the time picker is replaced by the second digit.
💁 Possible Solution
No response
🔦 Context
No response
🖥 Steps to Reproduce
Goto https://codesandbox.io/s/small-water-y5dgj4?file=/src/TimeField.js
Fill hours and minutes in TimeField
Clear everything in the minutes section using backspace
Refill the minutes section, eg 23
The field will display 3 instead of 23
Version
3.0.0
What browsers are you seeing the problem on?
Chrome, Other
If other, please specify.
Brave
What operating system are you using?
Mac OS Ventura
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response

Interesting. Seems to work if you first focus the hour field and then re-fill the minutes, but not if you backspace and immediately fill out the minutes. 🤔

Seems to be an issue with updating  enteredKeys.current in backspace function of<EMAIL_ADDRESS>Adding this statement after line 97 seems to be fixing the issue
newValue = newValue === '0' ? '' : newValue;

@devongovett

Maybe related to https://github.com/adobe/react-spectrum/issues/5261

Hi, any updates on this @reidbarber @devongovett?

I'm actually still seeing this one reproduce in the storybook on main in the React Spectrum component and the RAC component


Use "nonacademic" entrysubtype in place of "newspaper/magazine" for biblatex-apa

Debug log ID
WMK9XZ9K-refs-euc/6.7.231-7
What happened?
The biblatex-apa package uses the entrysubtype "nonacademic" for newspaper articles and other non-academic articles. (Section 4.2.3 of the biblatex-apa documentation).
Currently, BBT by default would insert entrysubtype = {newspaper} or entrysubtype = {magazine} when exporting respective item types. Since BBT now has a dedicated export option for biblatex-apa, I would propose that the "nonacademic" subtype is used instead if the biblatex-apa option is selected.

Can you post how you think the resulting entry from WMK9XZ9K-refs-euc/6.7.231-7 should look like?

Thank you! As far as I can tell, the exported entry from build 7017 should fit what biblatex-apa expects, and the compiled bibliography matches APA7 prescriptions.


Use 'server:start' instead of 'server:run' when possible

server:start is a better option ... but it's not always possible to run it.

Should be deal with Symfony Version also ? because this command does not exist in older SF version.

@lyrixx you are right! I've improved the condition to check that we're using Sf 2.6.0 or higher. Thanks!


ng serve not working automatically

Versions
Angular CLI: 6.0.8
Node: 8.9.0
OS: linux x64
Angular:
... common, compiler, compiler-cli, core, forms, http
... platform-browser, platform-browser-dynamic, router
Package                      Version
@angular-devkit/architect    0.6.8
@angular-devkit/core         0.6.8
@angular-devkit/schematics   0.6.8
@angular/cli                 6.0.8
@schematics/angular          0.6.8
@schematics/update           0.6.8
rxjs                         6.2.1 (cli-only)
typescript
#1209
ng serve is not working automatically..
For every single changes, I have to run ng serve
Please give solution

There is an open issue about this problem in https://github.com/angular/angular-cli/issues/1610. Please check that issue for reasons why reload might not work.

If I run "sudo ng serve"  it works fine.. Thank you

@akgssivagami that's the solution! Thank you!
There's a lot of people asking about this... I hope they find this issue!


[Feature Request] - Bump without install

To get any results using the program, you have to install the node packages first. We should be able to bump without installing anything.

Nice find - hopefully it's just handling the MISSING output and installing the package at requested version

I can work on this tomorrow unless you fancy it?

@JonShort I'd like to handle it please.


Install lodash and md5.  Add gravatar.js and applicable tests.

Don't use a noah_simone directory. Name your folder what your feature is gravatar


Advanced rocketry

Energy cable from advanced rocketry is not available.  For many advanced rocketry blocks, the advanced rocketry cable is the only compatible cable.  See solar panels.

They are disabled intentionally, the advanced rocketry panel is terrible :P all advanced rocketry machines support rf/rf cables to power them.


Change defaults

I am working on a project where I want to configure some defaults like the default Processor to be used and default Attribute mapping. However I can't seem to find a way to easily change these. Can anyone point me in a direction on how to do this?

See some examples here:
https://github.com/UniversitaDellaCalabria/uniAuth/blob/master/uniauth/processors.py
https://github.com/UniversitaDellaCalabria/uniAuth/blob/master/idp/processors.py
And if you like it please put a star ;)

Thank you for the quick response!
Those examples will definitely help later on. However I did not describe my issue clear enough. I am trying to edit the defaults as displayed in the admin interface, I don't want admin's to have to worry about selecting the correct processor and supplying the correct mapping.

uniAuth started as a djangosaml2idp fork. In uniAuth I use a default value pointing to that's configured in settings.py, as initial value in the form. The SP admin management was first introduced in uniAuth then, later, on djangosaml2idp, so we should wait for an answer from djangosaml2idp dev team


test-infra: use sysctl ansible module in sandbox setup

See https://github.com/nephio-project/test-infra/pull/56#discussion_r1207673304
/assign @electrocucaracha

@johnbelamaric this has been implemented, you can proceed to close the issue


Add stack.yaml environment variable interpolation

Nice work getting this up and running w/ Stack!
This is a small hack to allow env-variable interpolation in the stack.yaml. Private repos that we depend on have been causing some problems in our build structure lately. This allows us to safely include passwords in the git https addresses w/o needing to commit those passwords to a repo.

Opened too early. Needs some more testing.

Hey @ChrisCoffey! I'm trying to understand the motivation behind these changes, what problems you're running into, and how these changes help you out. It sounds like you're referencing private repos for extra dependencies in you're stack.yaml and you want to avoid encoding the secrets in the stack.yaml so you don't check them in? And the solution is to read a stack.vars file that contains the secrets and to template them in to the stack.yaml? Is the stack.vars file with the secrets also not getting committed?
There are environment variables available during compile time that might make things easier without having to pass in a file of secrets - see the section around ENV_DIR and the documentation over here.

@ChrisCoffey will this work for your use case? stack-vars
--- a/bin/compile
+++ b/bin/compile
@@ -63,7 +63,7 @@ speak "Restoring $LIBGMP_VER files from cache"
 rsync -avq "$LIBGMP_DIR/ghc-libs/" "$WORK_DIR/vendor/ghc-libs"

 ########## stack exe ###############################################
-STACK_VER=${STACK_VER:-1.0.4}
+STACK_VER=${STACK_VER:-1.1.2}
 STACK_URL=${STACK_URL:-https://github.com/commercialhaskell/stack/releases/download/v"$STACK_VER"/stack-"$STACK_VER"-linux-x86_64.tar.gz}
 STACK_DIR="$CACHE_DIR/stack-$STACK_VER"
 STACK_EXE="$STACK_DIR/stack"
@@ -76,6 +76,14 @@ speak "Restoring stack-$STACK_VER"
 rsync -avq "$STACK_EXE" "$WORK_DIR/vendor/bin/stack"
 chmod a+x "$WORK_DIR/vendor/bin/stack"

+########## stack vars ##############################################
+if [ -d "$ENV_DIR" ]; then
+  speak "Substituting stack vars"
+  for e in $(ls "$ENV_DIR"); do
+    sed -i "s/{{$e}}/$(cat $ENV_DIR/$e)/g" "$BUILD_DIR/stack.yaml"
+  done
+fi
+
 ########## project build ###########################################
 speak "Running stack"
 cd "$BUILD_DIR"
diff --git a/bin/detect b/bin/detect
index f384356..26a943e 100755
--- a/bin/detect
+++ b/bin/detect
@@ -1,6 +1,6 @@
 #!/usr/bin/env bash

-if [ -n "$(find "$1" -name stack.yaml -print -quit)" ]; then
+if [ -n "$(find "$1" -name stack.yaml -maxdepth 1 -print -quit)" ]; then
   echo "Haskell"
   exit 0
 else

Absolutely, that should do the trick nicely.
Wrt the stack.vars file, that was just a list of environment variables that you want to replace. But I like the idea of just replacing any environment vars present rather than only a subset.

See https://github.com/mfine/heroku-buildpack-stack/pull/9. Let me know if you run into any issues.


Update AWS SQS FIFO queue to allow for setting MessageGroupId and Mes…

Update AWS SQS FIFO queue to allow for setting MessageGroupId and MessageDeduplicationId.  MessageGroupId is required for SQS FIFO queue objects.

@skoncal Hey, thanks for doing this, but next time, can you add tests? I'll do that for now

@jeremydmiller Yeah, my bad on the unit tests.  Thanks for merging this and adding the unit tests!!


eps.json

Command

What occurred

What you expected to occur
CLI Version

CC API Endpoint Version

CF Trace

Platform & Shell Details

Any other relevant information

Hi @jasmasher, could you provide more details about this issue.

Hi @jasmasher I'm closing this issue due to inactivity and lack of details. Please create a new issue with details if you want us to look into your issue. Thanks.


Minimum quantity of cart on checkout

Hi - appreciate anyone's help on this - please take it easy on me, I'm no great programmer!
Is there anyway to add some script to check the minimum quantity on checkout of the cart? (By that I mean the total quantity, not individual quantities of the products).
Many thanks,
Piccante

Hi Piccante,
I put together a quick example for you: http://www.minicartjs.com/examples/cartquantity.html
Just view the source and you can see how I plugged into the onCheckout event and set the minimum quantity to be 2 or else checkout won't happen and an alert is displayed. Hopefully this helps!

Perfect Jeff, quick and accurate reply worked a treat!  Thank you very much!

Awesome Jeff, thank you so much for your help.
I have submitted another "issue" on GitHub as I guess this forum means others can learn as well... I hope it's not too much trouble but this one is regarding a discount based on the total number of products added to the cart.
Many thanks for your quick solution to the min quantity question I had!
Cheers,
Greg (Piccante)
Piccante Web Design
<EMAIL_ADDRESS>On 19 Jan 2012, at 10:24 AM, Jeff Harrell wrote:

Hi Piccante,
I put together a quick example for you: http://www.minicartjs.com/examples/cartquantity.html
Just view the source and you can see how I plugged into the onCheckout event and set the minimum quantity to be 2 or else checkout won't happen and an alert is displayed. Hopefully this helps!

Reply to this email directly or view it on GitHub:
https://github.com/jeffharrell/MiniCart/issues/42#issuecomment-3556980


JDK 11 preparation and jakarta uptake.

Unfortunately it still needs --add-reads com.sun.istack.tools=ALL-UNNAMED for javadoc in istack-commons-tools module because of ant. Rest of TODOs were removed (java.activation related).

Please update codemodel to latest version - org.glassfish.jaxb:codemodel:2.3.2


Go to next placeholder

Hello,
Is it possible to go to the next placeholder with a shortcut?
I have set up my configuration files as indicated in the readme.
I use LuaSnip (vscode-format snippets) with nvim-cmp, and my configuration is as follows
local cmp = require("cmp")
local luasnip = require("luasnip")

require "luasnip.loaders.from_vscode".lazy_load({ paths = { "./snippets" } })

vim.keymap.set('s', "<Tab>", function() require "luasnip".jump(1) end, { noremap = true, silent = true })
vim.keymap.set('s', "<S-Tab>", function() require "luasnip".jump( -1) end, { noremap = true, silent = true })

cmp.setup({
  snippet = {
    expand = function(args)
      luasnip.lsp_expand(args.body)
    end,
  },
  mapping = cmp.mapping.preset.insert {
    ['<C-d>'] = cmp.mapping.scroll_docs( -4),
    ['<C-u>'] = cmp.mapping.scroll_docs(4),
    -- ['<C-Space>'] = cmp.mapping.complete(),
    ['<CR>'] = cmp.mapping.confirm {
      behavior = cmp.ConfirmBehavior.Insert,
      select = true,
    },
    ['<Tab>'] = cmp.mapping.select_next_item(),
    ['<S-Tab>'] = cmp.mapping.select_prev_item(),
  },
  sources = {
    { name = "nvim_lsp" },
    { name = "luasnip" },
  },
})

However, it doesn't seem to work, when I have multiple placeholders, hitting Tab would only insert a tab character.
Thank you :)

I think you might want to try a "super-tab" setup, where if there's a luasnip snippet, then it goes to the next placeholder, else next item, else tab.

That worked like a charm, thank you so much!


Finding ArticulationPoints in Graph Algorithm Added

Related Issue

Added the code for issue #267

Proposed Changes

Added code for finding all the Articulation Points in A-ArticulationPoints  folder which is inside G-GraphAlgorithms folder
file name : ArticulationPoints.cpp
Created readme.md inside A-ArticulationPoints  folder and added all the necessary data regarding Articulation Points in readme.md file

Checklist

[x] ✅ My code follows the code style of this project.
[x] 📝 My change requires a change to the README.
[x] 🎀 I have updated the README accordingly.
[x] 👀 I have read the CONTRIBUTING document.
[x] ✨ I have added tests to cover my changes.
[x] 🚩 All new and existing tests passed.
[x] 🌟 ed the repo

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Make your issue a descriptive one so it is easy for us
mentors to get hold of your contribution and can guide you for further steps.
I would recommend you to go through this tutorial video of the project here , thanks.
///--------------------Pull Requests--------------------///

Short Description or CheckLists

Make sure your Pull Request is descriptive and complete the checklist .
I would recommend you to go through this tutorial video of the project here ,thanks.
///------------------Description -----------------------///
For contribution and more guidelines i would recommend you to go through this
tutorial video of the project here, thanks.
///------------------Description -----------------------///
Let me show you how to check the check list , there should be no space inside brackets like [x]
[x]

[x] Checklist
[ ] Or you can just check them from outside without doing any of these
[x] ✨ I have added tests to cover my changes.
[x] 🚩 All new and existing tests passed.
[ ] 🌟 ed the repo

Starr the repo if you haven't !
Have you watched this video ?

///----------------------PR README --------------------///
You need to follow particular guidelines for your README , please follow
these guidelines click here
also you can see how your README should look like see here
for more please go through these here

I have completed all the require checklist. Is there anything else I can improve?

Hey @Lakhankumawat can you please review.

I am sorry this finds a plagiarism problem of more then 70% can you make change sin the code

any updates?

I am working on it.

Alright kindly work on it


[Chip] Ignore events generated by descendants

Closes #10324

@maxdubrinsky It's a great first-time pull request 👌🏻. Thank you for giving it a shot! It's not every day that we see someone contributing a failing test and fixing it ✨ .

@oliviertassinari Thanks for the help, hope to be around here more!


golangci-lint does not play nice in a check derviation

Describe the bug
while trying to write a flake check for golangci-lint, it became apparent that, while the binary is built correctly, the core structure of golangci-lint and go break fundamental assumptions about sandboxing during the derivation build process.
Steps To Reproduce
Steps to reproduce the behavior:

make a flake inside a repo with go code, and workaround #202592 explicitly:

{
  outputs = { nixpkgs, ... }: let
    system = "x86_64-darwin";
    pkgs = nixpkgs.legacyPackages.${system};
  in {
    checks.${system}.go = pkgs.runCommandLocal "go" {
      builtInputs = [pkgs.go];
    } "${pkgs.golangci-lint}/bin/golangci-lint run ${./.}";
  };
}

nix flake check

2022/11/23 21:13:36 failed to initialize build cache at /homeless-shelter/Library/Caches/golangci-lint: mkdir /homeless-shelter: read-only file system

set GOLANGCI_LINT_CACHE=/tmp/
nix flake check

ERRO Running error: context loading failed: failed to load packages: failed to load with go/packages: err: exit status 1: stderr: failed to initialize build cache at /homeless-shelter/Library/Caches/go-build: mkdir /homeless-shelter: read-only file system

set GOCACHE=/tmp/
nix flake check

ERRO Running error: context loading failed: failed to load packages: failed to load with go/packages: err: exit status 1: stderr: package unsafe is not in GOROOT (/nix/store/1bj9310khph9p26wiad36m8x03qjxdpq-go-1.19.2/share/go/src/>

Expected behavior
it just works:

Additional context
it was required that I work around #202592 during this investigation.
I was able to resolve the two cache failures by explicitly setting GOCACHE and GOLANGCI_LINT_CACHE to a writable temporary directory, /tmp/ may not work well on linux.
I am unclear if setting these via wrapper is the right call, even in stdenv, since there are valid reasons why you would like these to point to a reused cache during normal operation. we could export some helper functions like buildGoModule, say checkGolangCiLint, since we will likely be heavy handed with the solution?
I think there may also be is an actual bug with the GOROOT stuff, but I could not find the root cause, so feel free to fork that off into a separate issue.
Notify maintainers
golangci-lint: @anpryl @manveru @mic92
go: @c00w @kalbasit @mic92 @zowoq
Metadata
 - system: `"x86_64-darwin"`
 - host os: `Darwin 21.6.0, macOS 10.16`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.11.0`
 - channels(user): `"darwin, home-manager"`
 - channels(root): `"nixpkgs"`
 - nixpkgs: `/nix/store/lxfwcg0km6p3rrr307i9k6pgnc4brmzb-source`

This is my setup in sops-nix:
https://github.com/Mic92/sops-nix/blob/f72e050c3ef148b1131a0d2df55385c045e4166b/pkgs/lint.nix#L2
I only had to give it a $HOME to work.

I think a golangciLintHook package could wrap this nicely. I would not add a build hook to the linter itself since this might draw in dependencies i.e. a go compiler.

yeah, as feared the rabbit hole goes one deeper, since golangci-lint basically needs access to the same vendor directory that buildGoModule uses. how did you get this working on sops-nix?


Please update annotation results spreadsheet format

We should move this from FigFams to PLFs and PGFs.

Added in version 1.26 of FigKernelScripts/rast_export_genome.pl in CVS; will propagate to github on next SEED code update.


Hooks?

Any chance the v3 branch could be released if it's ready to go?
Cheers

Its published on npm as an alpha: 3.0.0-alpha.2.

Ah, somehow missed that when I'd looked earlier, cheers.

No worries, if you don't encounter any issues I will release it.


Chinese language in media picker when using not supported languages by WeChat File Picker

Describe the bug
Thank you for a wonderful application. For me, this is just a great replacement for Snapdrop, which connects through the server, and it has been very unstable lately.
I see that it is possible to contribute to the translation of the application and I will definitely do it a little later, but at the moment, I noticed the following thing: if the Ukrainian language is selected, when adding Media, for some reason the untranslated pieces are displayed not in English, but in hieroglyphs.
There are no hieroglyphs in the files strings_uk and _missing_translations_uk, so it's not about the translation itself.
To reproduce

Expected behavior

Screenshots

Desktop (please complete the following information)
No response
Smartphone (please complete the following information)
No response
Additional context
No response

The problem is that the WeChat File Picker lib is defaulting to Chinese Ideograms instead of English for non-supported languages. The current locales supported are:

Chinese
English
Hebrew
German
Russian
Japanese
Arabic
French

The problem is that the WeChat File Picker lib is defaulting to Chinese Ideograms instead of English for non-supported languages. The current locales supported are:

Chinese
English
Hebrew
German
Russian
Japanese
Arabic
French

Oh, that's really bad, especially considering that the app is translated into a much wider list of languages. The English translation in this place is not so bad, but the ideograms are visually uncomfortable. And using the Chinese WeChat File Picker as a media file selection looks like a pretty strange solution.
As an option, perhaps there is a way to trick the library for unsupported languages by indicating that it is supposedly not an unsupported language, but English. Then instead of ideograms, there will be English words, which is a much better option.

I read the documentation a bit and I think there is a way to override it.

I changed the name of the issue because it turned out that the problem is not only with the Ukrainian language. Before publishing this issue, I tried Russian and French languages, and they display everything correctly, so I thought the problem was only with Ukrainian.

@Tienisto Are you ok with setting up the translations for the Asset Picker in Localsend's internal i18n assets?
Like this: https://github.com/TheGB0077/localsend/tree/Asset-Picker-i18n
By the way, how can I refresh the missing_translations files? I tried flutter pub run slang analyze, but that generated one unique file containing the different locales.
Also, I don't know exactly where I should put the asset_picker_translated_text_delegate file in the folder structure. Where should I put it?

Hi @TheGB0077 , thanks for your effort!
The exact command is flutter pub run slang analyze --full.
You can move the delegate to util. These are a lot of translations... but I guess there is no better solution

I'm trying to test the app on android, but I can't sign the apk file, I tried generating a keystore file but that didn't work. There's any way I can create it without the original file?

@TheGB0077 You can change the following line temporarily:
# android/app/build.gradle
buildTypes {
  release {
    signingConfig signingConfigs.debug // using debug signing
  }
}


add support for embedded-hal=1.0.0-alpha.10 - WIP

see individual commit messages for details

@jasta if your HAL already supports embedded-hal=1.0.0-alpha.10 then this should resolve #8 for you. otherwise i'd suggest that you try to get support for it added to your HAL (see https://github.com/stm32-rs/stm32f4xx-hal/pull/663 for how this can look like).
i'll merge this PR once the referenced libraries (stm32f4xx-hal & embedded-hal-mock) have new releases with the relevant code in it (i don't want to depend on git dependencies in a release).

this has been replaced with #25 which has now been released as v0.2.0. note that the new version only supports e-h 1.0.0-rc1


Cannot install 2.9.0rc1, only available for few OS and Python versions

Click to expand!
Issue Type
Build/Install
Source
binary
Tensorflow Version
2.9.0rc1
Custom Code
No
OS Platform and Distribution
Linux Ubuntu
Mobile device
No response
Python version
3.8
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
I cannot install latest 2.9.0rc1 package via pip:
$ pip install --pre tensorflow-cpu==2.9.0rc1
ERROR: Could not find a version that satisfies the requirement tensorflow-cpu==2.9.0rc1 (from versions: 2.2.0, 2.2.1, 2.2.2, 2.2.3, 2.3.0, 2.3.1, 2.3.2, 2.3.3, 2.3.4, 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.6.0, 2.6.1, 2.6.2, 2.6.3, 2.7.0, 2.7.1, 2.8.0, 2.9.0rc0)
ERROR: No matching distribution found for tensorflow-cpu==2.9.0rc1

Installing version rc0 works perfectly fine:
$ pip install --pre tensorflow-cpu==2.9.0rc0
Collecting tensorflow-cpu==2.9.0rc0
  Downloading tensorflow_cpu-2.9.0rc0-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (207.4 MB)
...

Reason is, rc1 is available only for a few OS and Python versions, and manylinux and py38 is not among them: https://pypi.org/project/tensorflow-cpu/2.9.0rc1/#files
Has the release been incomplete?
Standalone code to reproduce the issue
Run with Linux and Python != 3.7:
pip install --pre tensorflow-cpu==2.9.0rc1

Relevant log output
See above.

Hello @EnricoMi ,
I was able to install 2.9.0-rc1.Can you please find the gist here.Also tf v2.9.0-rc1 has been released and please refer this link for the releases.Thanks!

@tilakrayal you probably run macOS with Python 3.7 or 3.8 or Linux with Python 3.7. All other Python ad OS versions do not work.

@EnricoMi,
Since Tf v2.9.0-rc1 is pre release, we can expect Other OS and Python support for stable version Tf v2.9. Thanks!

So I can test Tf v2.9.0rc1 on Linux only with Python 3.7? Please confirm this is intentional.

We had some issues hitting the size limit on the tensorflow-cpu project. We asked for a size limit bump at https://github.com/pypa/pypi-support/issues/1870

@mihaimaruseac thanks for the update, pip install works now as expected.


api_docs: Revise emoji documentation for statuses and reactions.

Makes various improvements to the API documentation around emoji reactions to messages and emoji in user statuses:

Adds and updates changelog documentation for POST /users/me/status feature level 86 addition of new emoji parameters.

Makes description text for emoji reaction_type consistent throughout API documentation and also adds better description of the unicode_emoji namespace for emoji_code.

Redirects links in user_status event to go to the emoji parameters in /update-status endpoint, which was not a documented endpoint when the event documentation was originally created.

Follow-up to #21704. See this CZO conversation for more context.
This is the HTML diff of the API documentation with these updates / changes. Note that any endpoint that returns a message object will be updated for the changes to the EmojiBase schema.
Updated /update-status endpoint documentation

Updated /get-events documentation for user_status event

Updated /get-events documentation for reaction op: add event, which uses shared EmojiBase schema

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Merged, thanks @laurynmm!


Crash when rendering inclusion_tag with takes_context with multiple context processors

I have an inclusion tag that looks something like this:
@register.inclusion_tag("template.html", takes_context=True)
def tag(context, variable):
    context.update({'variable': variable})
    return context

When rendering it I get the following stacktrace deep into floppyforms:
ValueError: dictionary update sequence element #0 has length 6; 2 is required
...because the context that gets sent in via takes_context is a list of dictionaries, not a dictionary. I think it's because that each context_processor adds one dictionary and that Django transparently handles that normally.
Here's the full stacktrace: http://dpaste.com/2FWD49D
It does not happen in floppyforms 1.3.0, but happens in 1.4.1. I think it might have something to do with this commit: https://github.com/gregmuellegger/django-floppyforms/commit/d591b12350af4b734cbcedd6c9becd330204268e
A workaround is to apply flatten_contexts to the inclusion tag:
@register.inclusion_tag("template.html", takes_context=True)
def tag(context, variable):
    from floppyforms.compat import flatten_contexts
    context = flatten_contexts(context)
    context.update({'variable': variable})
    return context

Sorry that I don't have time to write a proper testcase right now.

Hi, thanks for the report. I added some tests in the branch issue/153 (https://github.com/gregmuellegger/django-floppyforms/commit/9baf92328df39ab2a4e9400f149e7a1f4ffa0868) but the tests seem to pass for this.
Do you do anything differently than I do in the tests?

I'll have a look at the tests tomorrow and see if I can make them fail by adding more of my use case in there. I have an {% include "template.html" %} there and I think that context_processors might affect the how the context is returned. But I need to experiment a bit to get to a use case. Thanks for getting me started! :)


[Bug]: Support CSS and css-modules in bundle: false

Version
@rslib/core 0.0.5

Details
https://github.com/web-infra-dev/rslib/issues/140

import "./reset.css"; directly import css will generate a empty chunk reset.mjs by css-extract-rspack-plugin

./dist
└── esm
    ├── CounterButton.d.mts
    ├── CounterButton.mjs
    ├── env.d.mjs
    ├── reset.mjs
    └── static/css
        └── reset.css

// reset.mjs
// CONCATENATED MODULE: ./src/reset.css
// extracted by css-extract-rspack-plugin

import styles from './index.module.css';

./dist
└── esm
    ├── CounterButton.d.mts
    ├── CounterButton.mjs
    ├── CounterButtonStyle.module.mjs
    └── static/css
        └── CounterButtonStyle.module.css

// CounterButtonStyle.module.mjs
// extracted by css-extract-rspack-plugin
/* harmony default export */ const index_module = {
    textRed: "textRed-IhMFNY"
};
export { index_module as default };

expected behavior
./dist
└── esm
    ├── CounterButton.d.mts
    ├── CounterButton.mjs
    ├── CounterButtonStyle.module.mjs
    └── static/css
-      └── CounterButtonStyle.module.css
+      └── CounterButtonStyle_module.css

// CounterButtonStyle.module.mjs
+ import '../static/css/CounterButtonStyle_module.css'
// extracted by css-extract-rspack-plugin
/* harmony default export */ const index_module = {
    textRed: "textRed-IhMFNY"
};
export { index_module as default };

Reproduce link
in the draft pr
Reproduce Steps
in the draft pr examples/react-component-bundle-false

Some additional information:

Do we need to continue using css-extract-rspack-plugin  in Rslib which is used in Rsbuild now? Since the CSS is relative simpler in library building. Keep using css-extract-rspack-plugin to align better with Rsbuild while use experiments.css is more future oriented.

I used to tested that https://www.npmjs.com/package/webpack-remove-empty-scripts could remove the empty chunk with webpack and minicss-extract-plugin. Maybe we need to port the logic to css-extract-rspack-plugin.

@fi3ework

experiments.css

experiments.css is currently difficult to adjust, because it needs to be aligned with webpack and our feature needs to be able to adjust flexibly for now, so we consider the css-extract-rspack-plugin first and may port it to experiments.css in the future

Do we need to continue using css-extract-rspack-plugin  in Rslib which is used in Rsbuild now?

Yes,
I hope to reuse the CSS Modules capability of css-loader, as this can remain as consistent as possible with the build config in the web app. To use the return values of css-loader, css-extract-plugin is the only choice I think.
But at present, css-extract-rspack-plugin can't meet our needs. we still need some patches
e.g:

rename the css module file with this.emitFile in loader

./dist
└── esm
    ├── CounterButton.d.mts
    ├── CounterButton.mjs
    ├── CounterButtonStyle.module.mjs
    └── static/css
-      └── CounterButtonStyle.module.css
+      └── CounterButtonStyle_module.css

add import

// CounterButtonStyle.module.mjs
+ import '../static/css/CounterButtonStyle_module.css'
// extracted by css-extract-rspack-plugin
/* harmony default export */ const index_module = {
    textRed: "textRed-IhMFNY"
};
export { index_module as default };

there are two ways

write a new and simple lib-css-extract-loader (without hmr or css runtime, ...etc of css-extract)

just emit assets with this.emitFile loader api
benefits: simple
drawbacks:  need to replace CssExtractPlugin.loader with lib-css-extract-loader and remove CssExtractPlugin in Rsbuild

do some changes to current  CssExtractPlugin in https://github.com/web-infra-dev/rspack/blob/8f9db27586ebde35908fc0d1f57742b443fa0bb8/packages/rspack/src/builtin-plugin/css-extract/loader.ts#L295

benefits: reuse tools.cssExtract
drawbacks: add some options to cssExtract

I used to tested that npmjs.com/package/webpack-remove-empty-scripts could remove the empty chunk with webpack and minicss-extract-plugin. Maybe we need to port the logic to css-extract-rspack-plugin

in the web app and bundle mode, the empty chunk can be deleted by treeshaking and minifier, 😂our case is quite special.

3. add import
// CounterButtonStyle.module.mjs
+ import '../static/css/CounterButtonStyle_module.css'
// extracted by css-extract-rspack-plugin
/* harmony default export */ const index_module = {
    textRed: "textRed-IhMFNY"
};
export { index_module as default };

Is this code snippet for bundleless mode?


angular 4 permission

Fully featured permission based access control for your angular 4+ applications. This module inspired from angular-permission.

There seems to be some conflicts, please fix before we can merge.


Can Pipeline be run without Docker or Singularity?

Not sure if to put this in bug or enhancement feature, but i don't wish to use docker or singularity to run this analysis, but there does not seem to be any documentation to show how to run this without being virtualized. Can this be run without Docker or Singularity?
I see an option for Conda in the nextflow config file, but there is not documentation on using this profile.

Thank you for changing the label, so it is possible to run the pipeline without docker?

Currently, it is not set up to run one conda environment per process. It just pulls containers (with docker or singularity) for each process. We feel this is best for reproducibility of the pipeline and conda can be unreliable at times. What is the reason for running the pipeline outside of docker or singularity?
 This worked on my end to run PHoeNIx let me know if it works for you. I can't guarantee that we will be able to support this method with all future versions of PHoeNIx as it can be hard to get all the programs dependencies to work together so building a giant environment like this kinda just defeats the point of doing things with conda environments/containers.

Hi @AdrianLimaG can you confirm that this worked for you?

Hi, @jvhagey yes it was thank you for your help!


Component-name: Short summary

1. Detailed description of what you want to happen
...
2. Upload a screenshot or reference an example if possible

3. Describe the context and use case. Why do you need this feature?
...
4. How urgent is this request?
...
5. Email address for contact
...
Additional information
...

fdgdgd


[SYSTEMML-1686] Fix transpose conv2d filter shape & input size

Currently, the transpose conv2d layer (nn/layers/conv2d_tranpose.dml)
has a bug in which the filters tensor W has an incorrect shape, and
the conv2d_backward_data op has an incorrect input shape argument.
This results in an exception when the number of input channels C is
not equal to the number of filters F (i.e. number of output channels).
Since the transpose conv2d op is the gradient of the conv2d op, the
filter tensor needs to have the shape (C, F, Hf, Wf) for F filters,
rather than (F, C, Hf, Wf), in order to map from an input with C
channels to an output with F channels during the input data gradient
function (conv2d_backward_data) that is used in the forward pass.
Additionally, the input_shape argument for conv2d_backward_data
needs to be (N, F, Hout, Wout), rather than (N, C, Hout, Wout) in
order to map from an input with C channels to an output with F
channels.  Our previous test cases did not catch this issue because
the tests used C = F = 1.
This commit fixes these issues, and improves the robustness of the
associated tests.

cc @prithvirajsen, @niketanpansare, @bertholdreinwald

@niketanpansare This will require a change in Caffe2DML for the shape of the filters W, unless you are using the init function already.  We still are using F filters, but the shape of W is now (C, F*Hf*Wf).

Refer to this link for build results (access rights to CI server needed):
https://sparktc.ibmcloud.com/jenkins/job/SystemML-PullRequestBuilder/1575/

I'm having trouble understanding the organization of the numbers within a filter. For the simple case of F=2, C=1, Hf=2, Wf=2 such that the first filter is
1 2 3 4
and the second filter is
5 6 7 8
what should W look like?

@prithvirajsen For that example, W would be a single row that looks like 1 2 3 4 5 6 7 8.  The shape would be (C, F*Hf*Wf) = (1, 2*Hf*Wf).  Essentially, we are just taking the normal (F, C, Hf, Wf) filter tensor, transposing it to (C, F, Hf, Wf) and then flattening the latter three dimensions as usual to (C, F*Hf*Wf).
The motivation here is to think about the shape of W during a regular 2D conv function, i.e. (F, C, Hf, Wf).  In the forward and backward pass of regular 2D conv, W maintains the same (F, C, Hf, Wf)shape.  Specifically, in the backward pass, the data gradient function conv2d_backward_data accepts the same W of shape (F, C, Hf, Wf) to map from gradients wrt the output of shape (N, F, Hout, Wout) to gradients wrt to the input of shape (N, F, Hin, Win).
In a 2D transpose conv function, we use the 2D conv data gradient function as the forward function.  If we use the same size terminology as from regular 2D conv, we would be mapping from an input with F channels to an output with C channels (which seems backward, but is correct since the forward pass of 2D transpose conv is defined as the backward pass of 2D conv), and we would be using the same filter W of shape (F, C, Hf, Wf).  Now, in order to make the terminology of the 2D transpose conv layer consistent with the rest of the library, we would need to swap the variable names F and C so that we are mapping from an input with C channels to an output with F channels.  Thus, we would use a filter W of shape (C, F, Hf, Wf).

I just pushed a fix for a bug in the associated unit test, and in the process have uncovered an optimizer bug.  Essentially, for the conv2d_transpose unit test, the bias_add function in conv2d_transpose::forward is causing the number of rows in out to incorrectly increase from 2 to 3.  If an if (1==1) {} cut is added just before the bias_add function, the issue does not occur.  Interestingly, the gradient check for conv2d_transpose does not have the same issue, despite also calling the same conv2d_transpose::forward function.
cc @mboehm7 Can you look into this?
cc @bertholdreinwald, @niketanpansare

@niketanpansare do you wanna look into this bug described above (as it's likely related to your ConvolutionOp) - just let me know

Sure, will look into it.

Refer to this link for build results (access rights to CI server needed):
https://sparktc.ibmcloud.com/jenkins/job/SystemML-PullRequestBuilder/1578/

@dusenberrymw You answered my question but I am not sure I fully understood the representation.
For the following example W in FCHW format with F=C=Hf=Wf=2:
20 21 22 23 24 25 26 27
30 31 32 33 34 35 36 37
Is this the corresponding CFHW representation?
20 21 22 23 30 31 32 33
24 25 26 27 34 35 36 37
If yes, then I think the above transformation can be achieved with a simple DML function. Do you think that would be useful?

YeahW is a 4D tensor, and it is transformed from shape (F, C, Hin, Win) to (C, F, Hin, Win) by transposing the first two dimensions.
Here's some Python code for demonstration, using your example W.

Create W with shape (F,C,Hin,Win):

import numpy as np
F = C = Hin = Win = 2
w = np.array([20, 21, 22, 23, 24, 25, 26, 27, 30, 31, 32, 33, 34, 35, 36, 37])
w = w.reshape(F, C, Hin, Win)
print(w)

[[[[20 21]
   [22 23]]

  [[24 25]
   [26 27]]]

 [[[30 31]
   [32 33]]

  [[34 35]
   [36 37]]]]

Transpose to (C, F, Hin, Win):

w = w.transpose(1, 0, 2, 3)  # (F,C,Hin,Win) -> (C,F,Hin,Win)
print(w)

[[[[20 21]
   [22 23]]

  [[30 31]
   [32 33]]]

 [[[24 25]
   [26 27]]

  [[34 35]
   [36 37]]]]

Flatten to (C, F*Hin*Win) for SystemML:

w = w.reshape(C, F*Hin*Win)
print(w)

[[20 21 22 23 30 31 32 33]
 [24 25 26 27 34 35 36 37]]

In general, having a DML nn/util::transpose4d(dim1, dim2, dim3, dim4) function would be useful for arbitrary dimension permutations of our (flattened) tensors, as is possible in NumPy.  If we had that function, then this layer could accept the normal filter tensor W of shape (F, C*Hin*Win) and then just transpose it to (C, F*Hin*Win) before usage.  For this layer, the drawback to using that would be having to perform the transposition during every forward & backward call.
TensorFlow follows the same approach of swapping the F & C dimensions for performance reasons (keep in mind that the spatial dimensions come first in TF).  conv2d uses a filter tensor of shape (Hf, Wf, C, F), and conv2d_transpose use a filter tensor of shape (Hf, Wf, F, C).

I wouldn't want to transform W each time forward/backward is called either. The transformation should only be done once and then the transformed W should continue to be used.
If you're referring to a generic reshape that can perform arbitrary reshapes on 4D tensors, then I'm not sure if this can be achieved efficiently in DML (I think the corresponding builtin function would be very useful). A special reshape for FCHW -> CFHW is however, achievable in DML.

ok quick update on the "optimizer issue" - it has nothing to do with the compiler or runtime; the root cause is that CONV2D_BACKWARD_DATA messes up the dimensions during parsing, BIAS_ADD propagates these dims, the nrow is replaced abd never reaches the compiler (which would actually correct these mistakes).

Thanks, @mboehm7.  That fixed the issue.  Does anyone else have any remaining concerns regarding this PR?

looks good to me.

Thanks @dusenberrymw LGTM :+1:

Refer to this link for build results (access rights to CI server needed):
https://sparktc.ibmcloud.com/jenkins/job/SystemML-PullRequestBuilder/1582/


Failure of type inference in autoImplicit

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Check that your issue is not already filed.
Reduce the issue to a minimal, self-contained, reproducible test case. Avoid dependencies to mathlib4 or std4.

Description
def go (decls : Array Nat) (h : 0 < decls.size) : Bool := sorry
theorem go_foo (x : Nat) (decls : Array Nat) : go decls h = true := sorry

This code throws an error in the theorem statement of go_foo while trying to figure out the correct type for h:
application type mismatch
  go decls h
argument
  h
has type
  ?m.56 : Sort ?u.55
but is expected to have type
  0 < Array.size decls : Prop

which is rather surprising given that there are mvars on the one side and concrete values on the other side. The error can be fixed by changing the theorem statement as follows:
theorem go_foo' (x : Nat) (decls : Array Nat) h : go decls h = true := sorry

@nomeata conjectures that this is because autoImplicit variables are inserted at the beginning of the arguments list which makes it impossible to model the dependency on decl.
Context
In my practical code the statement behind h is large so I would like to avoid writing it out, while I can manage to do that with the mentioned workaround it would be nice if we had better UX here.
Expected behavior: If Joachim is right, either addressing this issue to allow for such autoImplicits or producing a more reasonable error for a user is probably the way to go.
Actual behavior: Confusing mvar error.
Versions
"4.7.0-rc2"
Impact
Add :+1: to issues you consider important. If others are impacted by this issue, please ask them to add :+1: to it.

@nomeata conjectures that this is because autoImplicit variables are inserted at the beginning of the arguments list which makes it impossible to model the dependency on decl.

Correct.
Another possible workaround it to use auto implicit for decls too.
theorem go_foo' (x : Nat) : go decls h = true := sorry


Open specific region of image using xywh params

ciao a tutti! i'm new to openseadragon and i wanna implement a feature that open a specific part (region) of an image thanks to xywh params that i get from the urlparams. the logic seems correct but its not working as expected. waiting for ideas!
expected behavior
in the url, i wanna pass a parameter for open the viewer in a specific region: '&xywh=1,1,1000,600'. so, i expect that if i visit a link with this parameter, it opens a region on the right bottom corner with a specific width and height (it can depends on the width of the source image). if the param is: '&xywh=0,0,1000,600' i expect that it opens a region on the upper left corner etc.
actual behavior
not totally wrong but not correct, because when i pass the parameter '&xywh=0,0,1000,600' it opens on the upper left but slightly wrong, because it does not respect the limits of the image, so the region goes out the image (and i want that with x0 and y0 the region starts exactly on the upper left corner of the image). with the parameter '&xywh=0,1,1000,600', i expect that is on the bottom left corner, but is not on the bottom, its on the lowest part of the image but seems not getting the start with 0. it seems that the height/y params are not correct.
code
as u can see im using fitBounds() that should ignore any constraints. im not totally sure that my viewer doesnt get any other indications/something interferes with my logic (did a light check and it seems that is not the case), but im asking here cause maybe my approach/code is not correct.
openSpecificRegion() {
      let x;
      let y;
      let w;
      let h;
      const urlParams = new URLSearchParams(queryString);
      const regionCoordinates = urlParams.get('xywh') || null;
      if (regionCoordinates) {
        const regex = /(\d+(?:\.\d+)?),(\d+(?:\.\d+)?),(\d+(?:\.\d+)?),(\d+(?:\.\d+)?)/;
        const match = regionCoordinates.match(regex);

        if (match) {
          x = +match[1];
          y = +match[2];
          w = +match[3];
          h = +match[4];
        }

        if ([x,y,w,h].every(x => x != undefined)) {
          const newBounds = new OpenSeadragon.Rect(x, y, w / viewer.source.width, h / viewer.source.height);
          return viewer.viewport.fitBounds(newBounds, false);
        }
      }
}

examples of whats happening
here it goes outside in the upper section, and is wrong. its evident from the preview too.

here it doesnt reach the bottom part of the image, but it arrives on the lowest part of the image.

here it goes totally outside lmao the x paramter seems not working at all, u can see it from the preview only

p.s. i tried this approach too
const centerX = ((x + (w/2)) / viewer.source.width);
const centerY = ((y + (h/2)) / viewer.source.height);
const viewportWidth = viewer.viewport.getContainerSize().x;
const zoom = viewportWidth/w;

viewer.viewport.zoomTo(zoom, new OpenSeadragon.Point(centerX, centerY));

Have you familiarized yourself with viewport coordinates?
https://openseadragon.github.io/examples/viewport-coordinates/
One thing to note is that, while the default width is 1, the default height is based on the aspect ratio.
Rather than using big numbers like 1,000 for the width, you might as well just use actual viewport coordinates. For instance, the upper left corner could be &xywh=0,0,0.1,0.1. The lower left corner of a square image could be &xywh=0.9,0.9,0.1,0.1.
Of course you need to keep in mind the aspect ratio of the image... You can do that via viewer.source.width / viewer.source.height if you want. Another approach is to get the image's viewport bounds via viewer.world.getItemAt(0).getBounds(). Note that in either case it's good to wait until the image has been loaded (just the initial load... You don't need to wait for the tiles).
The other thing you need to keep in mind is the aspect ratio of the viewport. If you give a rectangle to fitBounds that isn't the aspect ratio of the viewport, then there willl be extra space visible around the rectangle so that the full rectangle is visible. If what you're taking the user to is a specific region of interest, that's probably the correct behavior, but it's worth being aware of.


Swapping Red Hat partner logo for all white version

Hey, I just made a Pull Request!
Swapping the red/black Red Hat partner logo for a solid white logo that fits better with the page aesthetic. Logo provided is an official Red Hat logo from the brand website.

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

@tudi2d I added some padding around the logo, hopefully that looks better.

nice - thanks corey! lgtm - let's give it a go.

Thank you! Just for reference, how often does the site get republished?

On merge but it's a bit slow and can get reset when other changes get merged: https://github.com/backstage/backstage/actions/workflows/deploy_microsite.yml
Looks to be updated though: https://backstage.io/community

Got it, thanks @awanlin


chore(deps): Included dependency review

Dependency Review GitHub Action in your repository to enforce dependency reviews on your pull requests.
The action scans for vulnerable versions of dependencies introduced by package version changes in pull requests,
and warns you about the associated security vulnerabilities.
This gives you better visibility of what's changing in a pull request,
and helps prevent vulnerabilities being added to your repository.

https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review#dependency-review-enforcement
Signed-off-by: naveensrinivasan<EMAIL_ADDRESS>

Codecov Report

Merging #788 (5fe704a) into main (ed3b98f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #788   +/-   ##
=======================================
  Coverage   47.56%   47.56%
=======================================
  Files          62       62
  Lines        5460     5460
=======================================
  Hits         2597     2597
  Misses       2558     2558
  Partials      305      305

Continue to review full report at Codecov.

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

Thanks! Could you please add version comments to the pinned actions? e.g.
https://github.com/sigstore/rekor/blob/e0b79164f2279ad7c3e723a3ee16afbfcf271188/.github/workflows/build.yml#L55

The dependabot doesn't update the version. It becomes obsolete, and that is why I didn't add one. Let me know.

usually i update the dependabot pr to update the version

usually i update the dependabot pr to update the version

I can add the version. If that is required.

usually i update the dependabot pr to update the version

Included the version.

@cpanato  A friendly ping to merge.


Mocking redis client in tests

Hello!
Is there a possibility or existing gem (I haven't found it so far) which allows to mock real interaction with redis in tests when using redis-client? Analogous to fakeredis or mok_redis for redis-rb.
Thanks in advance.

No there isn't AFAIK, and I wouldn't recommend it.

@byroot why don't you recommend it?

Because:

Redis is fast enough that it doesn't make a big difference
There will always be some small differences between fake_redis and a real redis.

Hence why I never used fake_redis and consort, and always removed it from projects I inherited and I'm not interested in implementing something similar for redis-client.
But folks who feel strongly about it are welcome to do it.
If you really want to do this, you can probably implement a "fake_redis" driver.

Hi! I'm the (ex-)maintainer of fakeredis, I agree with @byroot on this. Back when the project started 12 years ago it was convenient and useful since Redis wasn't widely available on all the CI platforms and tools like Docker didn't exist back then, nowadays using a real Redis instance is trivial.
I would strongly recommend using a real Redis instance instead of fakeredis, IMO it doesn't worth investing a significant amount of time migrating the mocking libraries to use redis-client and if I don't receive any PR for it I'll mark the project as deprecated.

To add to that - mocking redis also means redis shares the same clock as ruby. One of the biggest benefits in my experience to using mock redis is being able to leverage travel_to and test behaviour that may rely on Redis expirationin a simple unit test.

Up until now for rails the only required external dependency was a database, now this is adding a second one. It's doable, but this is asking many devs to have a running redis locally and in CI. It is much easier to add a fake redis as a gem. I understand the lack of interest in providing a mock, but I would very much prefer having a fake.


Fix swarm_labels

Problem: if swarm_labels not defined at all, it fails on the last step with:
fatal: [node2]: FAILED! => {"failed": true, "msg": "'swarm_labels' is undefined"}

Using when swarm_labels is defined doesn't work with with_items. Let's use defaults instead.

Thank you @dzimine!

@dzimine thank you for PR, yep it's good to have backward compatibility, afaik this was fixed in https://github.com/ansible/ansible/issues/14383
@atosatto Probably ansible version should be reflected in Requirements section


HOSTEDCP-1371: Bump Golang to v1.21

What this PR does / why we need it:
Bumps Golang to v1.21 in the main go.mod and hack/tools go.mod
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
HOSTEDCP-1371
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/test verify
/test unit
/test images
/test e2e-aws

/test images
/test verify

/test images
/test verify

/test e2e-aws

/test unit

/test verify
/test unit
/test images
/test e2e-aws

/retest

/test e2e-aws

/retest

/retest

/test verify
/test unit
/test images
/test e2e-aws

/retest

/retest

/lgtm


Fix incorrect order of apiCalls in API latency SLO measurement

Add test to verify log statements (they are on of the interfaces for this
measurement). Also take advantage of t.Run method in tests.
/assign @wojtek-t

/lgtm
Thanks!


Correctly use UTF-8 indices when highlighting diagnostic source

Bug/issue #, if applicable:  https://github.com/apple/swift-docc/issues/678
Summary
Previously, the default diagnostic formatter would crash due to incorrect indices handling when trying to highlight a diagnostic source range.
A diagnostic's SourceRange is the range in the source file that emits the diagnostic. When highlighting a diagnostic source range, we use the column property of the upperBound and lowerBound  to find indices of a source string that should be highlighted.
The column property is The number of bytes in UTF-8 encoding.

/// The number of bytes in UTF-8 encoding from the start of the line to the character at this source location.

However, this was not taken into account previously when calculating the indices.
This pull request fixes this crash by using proper UTF-8 indices.
Testing
This functionally can be tested using the steps mentioned in https://github.com/apple/swift-docc/issues/678.

Clone https://github.com/apple/swift.git
Install a recent development snapshot of Swift
Run DocC from this snapshot this way (assuming swift is the clone from step 1):
docc preview --allow-arbitrary-catalog-directories swift/docs

Alternatively, the issue is easily reproducible by adding an emoji to a source line that would emit a diagnostic.
Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[x] Added tests
[x] Ran the ./bin/test script and it succeeded
[x] Updated documentation if necessary

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test


FEMM mesh & solution extraction

FEATURE INTRODUCTION:
This new feature allows to import the mesh nodes/connectivity/solution into the simulation and/or save these data in several .json file for latter use.
To activate these features, the user have now 2 more attributes in the MagneticFEMM class: is_get_mesh and is_save_FEA.
NEW CLASSES INTRODUCTION:
A new "Mesh" abstract class is created.
The new class MeshMat object is derived from Mesh. It defines a mesh which has its connectivity defined with a matrix (ndarray), because every element has the same type (Exemple: Triangle only).
The new class MeshFEMM object is derived from MeshMat. It has additional attributes specific to FEMM: the magnetic flux density B, the magnetic field H and the permeability mu, defined per element.
A new SubMesh class is also created (but it is not used yet): it contains a Mesh object which should be a smaller part of another Mesh object which is called the parent mesh.

Thank you for your contribution !


The sus function can't compare numbers from yap("")

I'm just trying this thing out, but i can't get trough here.
When the code reaches the sus (if) function it just ignores everything and jumps directly to the last impostor (else).

Am i missing something? I need to convert the input into a number somehow? :D
Any idea how can i resolve this problem?

This has been reported in the Discord server:

I've done some further testing and the problem seems to be the input gotten with yap(). If I set the variable "num" to a number I know will pass, the programm runs without problems. When I use yap() however the input that is recognized as "6" for example returns null after modulo operation.

Unfortunately I don't have time to dive back into this project, if someone is willing to create a pull request with the fix, I might look into it

Thanks for the answer anyway. :)

i had made a pull request back in november which didn’t get a response; i might be able to fix this issue later but only really if face hh cares about the pull requests anyway

i had made a pull request back in november which didn’t get a response; i might be able to fix this issue later but only really if face hh cares about the pull requests anyway

I've checked the pull request before but always forgot to fetch to test it locally, I'll make sure to do that tomorrow


0.4.1 Release

We are tracking towards the release of 0.4.1.  This thread is to discuss what needs to be finalized before we can cut the release.  If there are any PRs or open issues that should be added to the list, please comment below.
0.4.1 Integration Branch - issues ready to merge (#759 #774 #796 #800 #842 #843)
General

[x] #759 [Enhancement] client-side validation @ilanbiala
[x] #796 [Enhancement] http interceptor to handle unauthorized requests @ilanbiala
[x] #843 [Bug] previous state history @lirantal
[x] #811 [Enhancement] code coverage report @lirantal
[x] #836(#813/#814) XHTML compliant e-mail templates @lirantal
[x] #830 [Bug] 6 character pw stored as plain text @lirantal
[x] #853 [Enhancement] Template cache @ilanbiala
[x] #774 Remove data attribute prefix @ilanbiala
[x] #815 CONTRIBUTING.md @lirantal
[x] #842 [Bug/Enhancement] Facebook Authentication @lirantal
[x] #850 naming convention @lirantal
[ ] #636 Best Practices - Style Guide @ilanbiala

Articles

[ ] #800 route refactoring @ilanbiala
[ ] #807 [Enhancement] admin @ilanbiala

rebase after #800 is merged

I don't think the style guide is making it into 0.4.1. Other than that, I'm fine with the rest of the list.

Nice! What do you think about including #639?

@ilanbiala do you recon style guide could do pre 0.5.0? I could start helping with it within a week or so (holidays over).

@ilanbiala other than it requires work, what is the reasoning for not setting styleguide as a stretch goal?

@rhutchison I think the order which the Articles PR's should be merged is important #831
I think development will go a lot fast once we get the Styling guide implemented. We'd end up having to re-do work if we waited.. If there's good reason to wait, then I say push it till after 0.5.0 or as a requirement for 0.5.0.

@rhutchison I'm fine with #800 going in before #807 since it requires a bit more discussion.

Thanks guys for summing this up.
Can you please add the assigned person (me/Ilan) per issue so we can easily navigate to relevant items?
@ilanbiala you're welcome to add/remove items.
@rhutchison I'm overall in agreement with @ilanbiala about not pushing too big items such as the UX work. As you can see we're already doing much better in terms of agile and fast releases so it will be sure to catch up in 0.4.2 or something. The other reason would be to also let the changes quick in the dev cycle, meaning I would want to see UX story merged soon after 0.4.1 is out so we can "test drive" it for a little while on master before 0.4.2 is out.

@lirantal I never had the UX story in this list, I would like to see effort towards ngBestPractices though.  The UX can come in 0.4.3.
BTW, good work keeping the project moving - much improved
Also, I don't think non-contributors can manage/assign issues.

Thanks, we're all doing a great job here, definitely feels like we should meet for some beer somehow ;)
With regards to the issues assigned, I meant to update them in the bullets list above so it's easier to see whose assigned to one in that list you've put up there.

Sorry guys, but I have orientation week until Friday, so I'll be slow to get to these issues, though I will try my best. @lirantal if you want to take the lead on anything, I'm fine with that.

OK then. I'll sync with the guys on each issue to move it further.
On Aug 24, 2015 6:43 AM, "Ilan Biala"<EMAIL_ADDRESS>wrote:

Sorry guys, but I have orientation week until Friday, so I'll be slow to
get to these issues, though I will try my best. @lirantal
https://github.com/lirantal if you want to take the lead on anything,
I'm fine with that.
—
Reply to this email directly or view it on GitHub
https://github.com/meanjs/mean/issues/833#issuecomment-134009127.

Rearranged some issues so the 0.4.1 milestone contains all of the above issues/PRs. Let's try to release this in the next week.

Other than #811 is there anything else left open? @lirantal what is the status on #811?
I would recommend we cut 0.4.1 and move the articles PRs to 0.4.2.
Also starting with 0.4.2, all PRs with angular changes should follow angular-styleguide - if a file is touched, it should be updated.  I will put a larger effort to converting the modules.

Hey guys,
Just merged #811.
@ilanbiala the rest are yours, are we going to merge them for 0.4.1?

@ilanbiala @lirantal please ship this as 0.4.1 and create the proper release tag.  We will start working on 0.4.2

:+1:

@lirantal yes 0.4.1 is good to go. The rest are going into 0.4.2.

:+1: Nice. Great job everyone!

@lirantal do you want to create the release and I'll work on the next PRs?

Added #868 but it is already merged, so it should be good to go.

@ilanbiala sure thing.

@ilanbiala so basically except from tagging master branch as 0.4.1 there isn't anything else to do, right? we don't have an 0.4.1 branch like we had before with 0.4.0 so I don't see any merges required.
Tag created: https://github.com/meanjs/mean/releases/tag/v0.4.1

Yeah I think we are good. @rhutchison what's the integration branch for?

Merged related PRs https://github.com/meanjs/mean/pull/877 and https://github.com/meanjs/mean/pull/876 to update the version number to 0.4.1

@ilanbiala it was to help test a bunch of related PRs.  It's removed now.

Thanks @lirantal.  Please recreate the tag, now that #876 is merged and close this issue when you are done.
We should introduce CHANGELOG.md in next release.

Done.

@rhutchison Chanelog.html is just in the gh_pages branch.

@rhutchison I'd like to start the CHANGELOG.md from 0.4 as the "initial release" so we don't have to compare it against 0.3.

I think we can close this can move the discussion to https://github.com/meanjs/mean/issues/881 and the 0.4.2 issue


Unable to load datasets

Hi, it seems like loading the dataset using:
from datasets import load_dataset

dataset = load_dataset("THUDM/LongCite-45k",split="train")

will cause the following error:
<class 'pyarrow.lib.ArrowInvalid'>: JSON parse error: Column() changed from object to array in row 0

It seems like the dataset are saved in format that are unrecognized by the load_dataset function.
simply re-saved it via:
import json

def process_and_write_jsonl(input_file_path, output_file_path):
    with open(input_file_path, 'r', encoding='utf-8') as infile, \
         open(output_file_path, 'w', encoding='utf-8') as outfile:

        for idx,line in enumerate(infile):
            try:
                data = json.loads(line.strip())
                outfile.write(json.dumps(data[0], ensure_ascii=False) + '\n')
            except:
                break

input_file_path = "/home/jacksIon/longcite_ft/long.jsonl"
output_file_path = "longcite_45.jsonl"

process_and_write_jsonl(input_file_path, output_file_path)

will work.


Cooldowns bar [suggestion]

Cooldowns only shown when champs are visible, so how about a cooldown bar with all champs and their summoner cd's? Porofessor have a good one but without a "haram" options.

I made the spell tracker feature as an example to show that this project can be developed.
The purpose of this project is skin change, it will not serve any other field.
If there is a feature you want, reverse the game and code it.
Please do not create any more issues for the spell tracker I have made as an example.


Add Scurrius' spine to lampCommand

Description:
Scurrius' spines can be traded for combat xp.
Book of arcane knowledge was updated to give more xp in osrs months ago.
Changes:
-Added Scurrius' spine to /lamp, giving 3.5k xp to prayer or 5k exp to other combat skills.
-Updated the magic/rc xp from Book of arcane knowledge from 11->15 and 4->5.
Other checks:

[ ] I have tested all my changes thoroughly.

Don't you have to turn the spine in for a lamp first?

Don't you have to turn the spine in for a lamp first?
https://oldschool.runescape.wiki/w/Antique_lamp_(Historian_Aldo)

Yes, but the lamp is not even bankable, has anyone ever not used it immediately? It was probably done this way in osrs to prevent people from accidentally breaking their builds, I don't see a reason to make it more inconvenient in the bot by adding an extra step.

Don't you have to turn the spine in for a lamp first?
https://oldschool.runescape.wiki/w/Antique_lamp_(Historian_Aldo)

Yes, but the lamp is not even bankable, has anyone ever not used it immediately? It was probably done this way in osrs to prevent people from accidentally breaking their builds, I don't see a reason to make it more inconvenient in the bot by adding an extra step.

I would still opt for adding the lamp, can easily be done with /create. Skipping steps like that ruins the fun for some people, myself included going for unique sac others bank log etc etc. I recently went through something similar with another contrib over if ore pack's from volcanic mine should be auto open or not for "convenience sack".  I don't see a reason to deviate from how it works in game.

Don't you have to turn the spine in for a lamp first?
https://oldschool.runescape.wiki/w/Antique_lamp_(Historian_Aldo)

Yes, but the lamp is not even bankable, has anyone ever not used it immediately? It was probably done this way in osrs to prevent people from accidentally breaking their builds, I don't see a reason to make it more inconvenient in the bot by adding an extra step.

I would still opt for adding the lamp, can easily be done with /create. Skipping steps like that ruins the fun for some people, myself included going for unique sac others bank log etc etc. I recently went through something similar with another contrib over if ore pack's from volcanic mine should be auto open or not for "convenience sake". The bank thing isn't really an issue either since we have alot of non-bankable items in bank and unlimited bank space. I don't see a reason to deviate from how it works in game.

The bank thing was just to say everyone uses it immediately, but the sac log is fair, I forgot it was even a thing. So many other parts of the bot skips steps like this when there's actually a reason not to, so I just didn't think anyone would care if there was no real reason in game.


Gradle build failed with unknown error.

Description
Concern:
I am encountering an issue when attempting to build an app bundle or APK using my Expo project with EAS. The error is related to Gradle and shows problems with React Native Reanimated and React Native Camera.
Error Log:
Running 'gradlew :app:assembleRelease' in /home/expo/workingdir/build/android
Downloading https://services.gradle.org/distributions/gradle-8.0.1-all.zip
10%.
20%.
30%
40%.
50%
60%
70%.
80%.
90%.
100%
Welcome to Gradle 8.0.1!
Here are the highlights of this release:

Improvements to the Kotlin DSL

Fine-grained parallelism from the first build with configuration cache

Configurable Gradle user home cache cleanup

For more details see https://docs.gradle.org/8.0.1/release-notes.html
To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/8.0.1/userguide/gradle_daemon.html#sec:disabling_the_daemon.
Daemon will be stopped at the end of the build

Task :gradle-plugin:pluginDescriptors

Task :gradle-plugin:processResources

Task :gradle-plugin:compileKotlin

Task :gradle-plugin:compileJava NO-SOURCE

Task :gradle-plugin:classes

Task :gradle-plugin:jar

Task :gradle-plugin:inspectClassesForKotlinIC

Configure project :expo-modules-core

Checking the license for package NDK (Side by side) 23.1.7779620 in /home/expo/Android/Sdk/licenses
License for package NDK (Side by side) 23.1.7779620 accepted.
Preparing "Install NDK (Side by side) 23.1.7779620 (revision: 23.1.7779620)".
"Install NDK (Side by side) 23.1.7779620 (revision: 23.1.7779620)" ready.
Installing NDK (Side by side) 23.1.7779620 in /home/expo/Android/Sdk/ndk/23.1.7779620
"Install NDK (Side by side) 23.1.7779620 (revision: 23.1.7779620)" complete.
"Install NDK (Side by side) 23.1.7779620 (revision: 23.1.7779620)" finished.
Checking the license for package CMake 3.22.1 in /home/expo/Android/Sdk/licenses
License for package CMake 3.22.1 accepted.
Preparing "Install CMake 3.22.1 (revision: 3.22.1)".
"Install CMake 3.22.1 (revision: 3.22.1)" ready.
Installing CMake 3.22.1 in /home/expo/Android/Sdk/cmake/3.22.1
"Install CMake 3.22.1 (revision: 3.22.1)" complete.
"Install CMake 3.22.1 (revision: 3.22.1)" finished.

Configure project :expo

Using expo modules

expo-application (5.3.1)

expo-barcode-scanner (12.5.3)

expo-constants (14.4.2)

expo-file-system (15.4.4)

expo-font (11.4.0)

expo-image-loader (4.3.0)

expo-image-picker (14.3.2)

expo-keep-awake (12.3.0)

expo-linear-gradient (12.3.0)

expo-location (16.1.0)

expo-modules-core (1.5.11)

expo-modules-core$android-annotation (1.5.11)

expo-modules-core$android-annotation-processor (1.5.11)

expo-splash-screen (0.20.5)

expo-system-ui (2.4.0)

Configure project :react-native-reanimated

No AAR for react-native-reanimated found. Attempting to build from source.
Android gradle plugin: 7.4.2
Gradle: 8.0.1
WARNING:Software Components will not be created automatically for Maven publishing from Android Gradle Plugin 8.0. To opt-in to the future behavior, set the Gradle property android.disableAutomaticComponentCreation=true in the gradle.properties file or use the new publishing DSL.
FAILURE: Build failed with an exception.

What went wrong:

Could not determine the dependencies of task ':app:lintVitalReportRelease'.

Could not resolve all task dependencies for configuration ':app:releaseRuntimeClasspath'.

Could not resolve project :react-native-camera.

 Required by:

     project :app

  > The consumer was configured to find a component for use during runtime, preferably optimized for Android, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release', attribute 'com.android.build.api.attributes.AgpVersionAttr' with value '7.4.2'. However we cannot choose between the following variants of project :react-native-camera:

      - generalReleaseRuntimeElements

      - mlkitReleaseRuntimeElements

    All of them match the consumer attributes:

      - Variant 'generalReleaseRuntimeElements' capability Perks:react-native-camera:unspecified declares a component for use during runtime, as well as attribute 'com.android.build.api.attributes.AgpVersionAttr' with value '7.4.2', attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release':

          - Unmatched attributes:

              - Provides attribute 'com.android.build.api.attributes.ProductFlavor:react-native-camera' with value 'general' but the consumer didn't ask for it

              - Provides attribute 'com.android.build.gradle.internal.attributes.VariantAttr' with value 'generalRelease' but the consumer didn't ask for it

              - Doesn't say anything about its target Java environment (preferred optimized for Android)

              - Provides attribute 'react-native-camera' with value 'general' but the consumer didn't ask for it

      - Variant 'mlkitReleaseRuntimeElements' capability Perks:react-native-camera:unspecified declares a component for use during runtime, as well as attribute 'com.android.build.api.attributes.AgpVersionAttr' with value '7.4.2', attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release':

          - Unmatched attributes:

              - Provides attribute 'com.android.build.api.attributes.ProductFlavor:react-native-camera' with value 'mlkit' but the consumer didn't ask for it

              - Provides attribute 'com.android.build.gradle.internal.attributes.VariantAttr' with value 'mlkitRelease' but the consumer didn't ask for it

              - Doesn't say anything about its target Java environment (preferred optimized for Android)

              - Provides attribute 'react-native-camera' with value 'mlkit' but the consumer didn't ask for it

    The following variants were also considered but didn't match the requested attributes:

      - Variant 'generalDebugApiElements' capability Perks:react-native-camera:unspecified declares a component, as well as attribute 'com.android.build.api.attributes.AgpVersionAttr' with value '7.4.2':

          - Incompatible because this component declares a component for use during compile-time, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' and the consumer needed a component for use during runtime, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release'

          - Other compatible attribute:

              - Doesn't say anything about its target Java environment (preferred optimized for Android)

      - Variant 'generalDebugRuntimeElements' capability Perks:react-native-camera:unspecified declares a component for use during runtime, as well as attribute 'com.android.build.api.attributes.AgpVersionAttr' with value '7.4.2':

          - Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release'

          - Other compatible attribute:

              - Doesn't say anything about its target Java environment (preferred optimized for Android)

      - Variant 'generalReleaseApiElements' capability Perks:react-native-camera:unspecified declares a component, as well as attribute 'com.android.build.api.attributes.AgpVersionAttr' with value '7.4.2', attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release':

          - Incompatible because this component declares a component for use during compile-time and the consumer needed a component for use during runtime

          - Other compatible attribute:

              - Doesn't say anything about its target Java environment (preferred optimized for Android)

      - Variant 'mlkitDebugApiElements' capability Perks:react-native-camera:unspecified declares a component, as well as attribute 'com.android.build.api.attributes.AgpVersionAttr' with value '7.4.2':

          - Incompatible because this component declares a component for use during compile-time, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' and the consumer needed a component for use during runtime, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release'

          - Other compatible attribute:

              - Doesn't say anything about its target Java environment (preferred optimized for Android)

      - Variant 'mlkitDebugRuntimeElements' capability Perks:react-native-camera:unspecified declares a component for use during runtime, as well as attribute 'com.android.build.api.attributes.AgpVersionAttr' with value '7.4.2':

          - Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release'

          - Other compatible attribute:

              - Doesn't say anything about its target Java environment (preferred optimized for Android)

      - Variant 'mlkitReleaseApiElements' capability Perks:react-native-camera:unspecified declares a component, as well as attribute 'com.android.build.api.attributes.AgpVersionAttr' with value '7.4.2', attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release':

          - Incompatible because this component declares a component for use during compile-time and the consumer needed a component for use during runtime

          - Other compatible attribute:

              - Doesn't say anything about its target Java environment (preferred optimized for Android)

Try:

Run with --stacktrace option to get the stack trace.

Run with --info or --debug option to get more log output.

Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 3m 4s
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/8.0.1/userguide/command_line_interface.html#sec:command_line_warnings
5 actionable tasks: 5 executed
Error: Gradle build failed with unknown error. See logs for the "Run gradlew" phase for more information.

React Native Version
0.72.6
Output of npx react-native info
System:
OS: Windows 11 10.0.22621
CPU: (12) x64 Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz
Memory: 1.57 GB / 7.75 GB
Binaries:
Node:
version: 18.18.0
path: C:\Program Files\nodejs\node.EXE
Yarn: Not Found
npm:
version: 10.2.2
path: C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: AI-223.8836.35.2231.10811636
Visual Studio: Not Found
Languages:
Java:
version: <IP_ADDRESS>
path: C:\Program Files\Common Files\Oracle\Java\javapath\javac.EXE
Ruby: Not Found
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.72.6
wanted: 0.72.6
react-native-windows: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: Not found
newArchEnabled: Not found
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
Steps to reproduce
Try to use React native reanimated 3.3.0 with react native 0.72.6 and react native camera 4.2.1.
My package.json is as follows:
{
"name": "stickersmash",
"version": "1.0.0",
"main": "node_modules/expo/AppEntry.js",
"scripts": {
"start": "expo start",
"android": "expo start --android",
"ios": "expo start --ios",
"web": "expo start --web"
},
"dependencies": {
"@react-native-async-storage/async-storage": "1.18.2",
"@react-native-community/datetimepicker": "7.2.0",
"@react-native-community/progress-bar-android": "^1.0.5",
"@react-navigation/bottom-tabs": "^6.5.8",
"@react-navigation/native": "^6.1.7",
"@react-navigation/stack": "^6.3.17",
"@rneui/themed": "^4.0.0-rc.8",
"axios": "^1.5.1",
"expo": "~49.0.8",
"expo-barcode-scanner": "~12.5.3",
"expo-checkbox": "~2.4.0",
"expo-image-picker": "~14.3.2",
"expo-linear-gradient": "~12.3.0",
"expo-location": "~16.1.0",
"expo-status-bar": "~1.6.0",
"lottie-react-native": "5.1.6",
"react": "18.2.0",
"react-dom": "18.2.0",
"react-native": "0.72.6",
"react-native-camera": "^4.2.1",
"react-native-fontawesome": "^7.0.0",
"react-native-gesture-handler": "~2.12.0",
"react-native-image-crop-picker": "^0.40.0",
"react-native-image-picker": "^7.0.0",
"react-native-linking": "^0.0.0",
"react-native-permissions": "^3.8.4",
"react-native-progress": "^5.0.0",
"react-native-qrcode-scanner": "^1.5.5",
"react-native-reanimated": "~3.3.0",
"react-native-root-toast": "^3.5.1",
"react-native-screens": "~3.22.0",
"react-native-svg": "13.9.0",
"react-native-toast-message": "^2.1.6",
"react-native-url-polyfill": "^2.0.0",
"react-native-vector-icons": "^10.0.0",
"react-native-web": "~0.19.6",
"uuid": "^9.0.0",
"expo-dev-client": "~2.4.11"
},
"devDependencies": {
"@babel/core": "^7.20.0",
"react-native-dotenv": "^3.4.9"
},
"private": true
}
My eas.json:
{
"cli": {
"version": ">= 5.6.0"
},
"build": {
"development": {
"developmentClient": true,
"distribution": "internal",
"ios": {
"resourceClass": "m1-medium"
}
},
"preview": {
"distribution": "internal",
"ios": {
"resourceClass": "m1-medium"
},
"android": {
"buildType": "apk"
}
},
"production": {
"ios": {
"resourceClass": "m1-medium"
}
}
},
"submit": {
"production": {}
}
}
Snack, screenshot, or link to a repository
https://github.com/karimnyumba/Perks_FrontEnd.git

jdk version 11 is not 18

I have the same problem😥
Android build failed:
Gradle build failed with unknown error. See logs for the "Run gradlew" (https://expo.dev/accounts/luisherdeth/projects/wikipadel/builds/98c8e1cc-1ea0-4688-a0a7-e0597cc56346#run-gradlew) phase for more information.

While trying to fix the errors (I am also working on the same project), I used the commands npm outdated then npm  update  to update all packages listed in the package.json file. I then run npx expo-doctor to diagnose and troubleshoot other issues and found none.
We used the code eas build -p android to build the aab file then comverted it into an apk. But now the issue is that the app keeps doesn't open. Any feedback (suggestions, questions, ...) would be greatly appreciated.

I had the same problem when working on a similar project. I have not found a solution.

I've also reached this problem while trying to build the app through expo, I managed to update  the dependencies using expo-doctor and installed some missing dependencies which allowed me to succesfully build it, but after getting the aab file and converting it into an apk file it would not run.

Closing as a Expo related issue. The problem is coming from react-native-camera and you should use Expo's tool to re-aling dependencies

npm install react-native-screens react-native-safe-area-context This command installs the react-native-screens and react-native-safe-area-context packages, which help resolve your issue as work for me

While trying to fix the errors (I am also working on the same project), I used the commands npm outdated then npm update to update all packages listed in the package.json file. I then run npx expo-doctor to diagnose and troubleshoot other issues and found none.
We used the code eas build -p android to build the aab file then converted it into an apk. But now the issue is that the app doesn't open. Any feedback (suggestions, questions, ...) would be greatly appreciated.

npm install react-native-screens react-native-safe-area-context This command installs the react-native-screens and react-native-safe-area-context packages, which help resolve your issue as work for me

I encountered the same problem while working on a similar project. Upon examining the errors, I discovered three significant issues.
1: Gradle build failed with unknown error. See logs for the Run
2: Execution failed for task ':app:mergeReleaseResources'.
3: Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
The following tips resolved my problems.
1: Run these commands and verify for yourself that the packages are updated.
a.	npx expo-doctor
b.	npx expo-doctor --fix-dependencies
c.	npx expo install –check OR npx expo install –fix
2: Log in to the expo.dev dashboard and identify the failed APK. Reset the cache and delete the failed build.
3: Check the file extensions of all your images. In my case, I had imported an image as a .png, but it should have been imported as a .gif.
4: Run the command "eas build --platform android" to successfully build the APK setup.

idk how to fix this problem
Running 'gradlew :app:bundleRelease' in /home/expo/workingdir/build/android
Welcome to Gradle 8.0.1!
Here are the highlights of this release:
 - Improvements to the Kotlin DSL
- Fine-grained parallelism from the first build with configuration cache
 - Configurable Gradle user home cache cleanup
For more details see https://docs.gradle.org/8.0.1/release-notes.html
To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/8.0.1/userguide/gradle_daemon.html#sec:disabling_the_daemon.
Daemon will be stopped at the end of the build
> Task :expo-dev-launcher-gradle-plugin:pluginDescriptors
> Task :expo-dev-launcher-gradle-plugin:processResources
> Task :gradle-plugin:pluginDescriptors
> Task :gradle-plugin:processResources
> Task :expo-dev-launcher-gradle-plugin:compileKotlin
> Task :expo-dev-launcher-gradle-plugin:compileJava NO-SOURCE
> Task :expo-dev-launcher-gradle-plugin:classes
> Task :expo-dev-launcher-gradle-plugin:jar
> Task :expo-dev-launcher-gradle-plugin:inspectClassesForKotlinIC
> Task :gradle-plugin:compileKotlin
> Task :gradle-plugin:compileJava NO-SOURCE
> Task :gradle-plugin:classes
> Task :gradle-plugin:jar
> Task :gradle-plugin:inspectClassesForKotlinIC
> Configure project :app
ℹ  Applying gradle plugin 'expo-dev-launcher-gradle-plugin'<EMAIL_ADDRESS>> Configure project :expo-modules-core
Warning: Errors during XML parse:
Warning: Additionally, the fallback loader failed to parse the XML.
Checking the license for package CMake 3.22.1 in /home/expo/Android/Sdk/licenses
License for package CMake 3.22.1 accepted.
Preparing "Install CMake 3.22.1 (revision: 3.22.1)".
"Install CMake 3.22.1 (revision: 3.22.1)" ready.
Installing CMake 3.22.1 in /home/expo/Android/Sdk/cmake/3.22.1
"Install CMake 3.22.1 (revision: 3.22.1)" complete.
"Install CMake 3.22.1 (revision: 3.22.1)" finished.
> Configure project :expo
Using expo modules
  - expo-constants (15.4.6)
- expo-dev-client (2.4.13)
  - expo-dev-launcher (2.4.15)
  - expo-dev-menu (3.2.4)
  - expo-file-system (16.0.9)
  - expo-font (11.10.3)
  - expo-json-utils (0.7.1)
  - expo-keep-awake (12.8.2)
  - expo-manifests (0.7.2)
  - expo-modules-core (1.11.13)
  - expo-modules-core$android-annotation (1.11.13)
- expo-modules-core$android-annotation-processor (1.11.13)
  - expo-splash-screen (0.20.5)
  - expo-system-ui (2.4.0)
> Configure project :react-native-reanimated
No AAR for react-native-reanimated found. Attempting to build from source.
Android gradle plugin: 7.4.2
Gradle: 8.0.1
WARNING:Software Components will not be created automatically for Maven publishing from Android Gradle Plugin 8.0. To opt-in to the future behavior, set the Gradle property android.disableAutomaticComponentCreation=true in the `gradle.properties` file or use the new publishing DSL.
Checking the license for package Android SDK Build-Tools 30.0.3 in /home/expo/Android/Sdk/licenses
License for package Android SDK Build-Tools 30.0.3 accepted.
Preparing "Install Android SDK Build-Tools 30.0.3 (revision: 30.0.3)".
"Install Android SDK Build-Tools 30.0.3 (revision: 30.0.3)" ready.
Installing Android SDK Build-Tools 30.0.3 in /home/expo/Android/Sdk/build-tools/30.0.3
"Install Android SDK Build-Tools 30.0.3 (revision: 30.0.3)" complete.
"Install Android SDK Build-Tools 30.0.3 (revision: 30.0.3)" finished.
Checking the license for package Android SDK Platform 33 in /home/expo/Android/Sdk/licenses
License for package Android SDK Platform 33 accepted.
Preparing "Install Android SDK Platform 33 (revision: 3)".
"Install Android SDK Platform 33 (revision: 3)" ready.
Installing Android SDK Platform 33 in /home/expo/Android/Sdk/platforms/android-33
"Install Android SDK Platform 33 (revision: 3)" complete.
"Install Android SDK Platform 33 (revision: 3)" finished.
FAILURE: Build failed with an exception.
* What went wrong:
Could not determine the dependencies of task ':expo-modules-core:compileReleaseRenderscript'.
> Could not resolve all task dependencies for configuration ':expo-modules-core:releaseCompileClasspath'.
   > Could not resolve com.facebook.fbjni:fbjni:0.5.1.
     Required by:
         project :expo-modules-core
      > Cannot find a version of 'com.facebook.fbjni:fbjni' that satisfies the version constraints:
           Dependency path 'host.exp.exponent:expo-modules-core:1.11.13' --> 'com.facebook.fbjni:fbjni:0.5.1'
           Constraint path 'host.exp.exponent:expo-modules-core:1.11.13' --> 'com.facebook.fbjni:fbjni:{strictly 0.3.0}' because of the following reason: releaseRuntimeClasspath uses version 0.3.0
           Dependency path 'host.exp.exponent:expo-modules-core:1.11.13' --> 'com.facebook.react:react-android:0.72.10' (releaseVariantDefaultApiPublication) --> 'com.facebook.fbjni:fbjni:0.3.0'
   > Could not resolve com.facebook.fbjni:fbjni:{strictly 0.3.0}.
     Required by:
         project :expo-modules-core
      > Cannot find a version of 'com.facebook.fbjni:fbjni' that satisfies the version constraints:
           Dependency path 'host.exp.exponent:expo-modules-core:1.11.13' --> 'com.facebook.fbjni:fbjni:0.5.1'
           Constraint path 'host.exp.exponent:expo-modules-core:1.11.13' --> 'com.facebook.fbjni:fbjni:{strictly 0.3.0}' because of the following reason: releaseRuntimeClasspath uses version 0.3.0
           Dependency path 'host.exp.exponent:expo-modules-core:1.11.13' --> 'com.facebook.react:react-android:0.72.10' (releaseVariantDefaultApiPublication) --> 'com.facebook.fbjni:fbjni:0.3.0'
   > Could not resolve com.facebook.fbjni:fbjni:0.3.0.
     Required by:
         project :expo-modules-core > com.facebook.react:react-android:0.72.10
      > Cannot find a version of 'com.facebook.fbjni:fbjni' that satisfies the version constraints:
           Dependency path 'host.exp.exponent:expo-modules-core:1.11.13' --> 'com.facebook.fbjni:fbjni:0.5.1'
           Constraint path 'host.exp.exponent:expo-modules-core:1.11.13' --> 'com.facebook.fbjni:fbjni:{strictly 0.3.0}' because of the following reason: releaseRuntimeClasspath uses version 0.3.0
           Dependency path 'host.exp.exponent:expo-modules-core:1.11.13' --> 'com.facebook.react:react-android:0.72.10' (releaseVariantDefaultApiPublication) --> 'com.facebook.fbjni:fbjni:0.3.0'
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
* Get more help at https://help.gradle.org
BUILD FAILED in 2m 55s
10 actionable tasks: 10 executed
Error: Gradle build failed with unknown error. See logs for the "Run gradlew" phase for more information.

🤖 Android build failed:
Gradle build failed with unknown error. See logs for the "Run gradlew"


Running headless apps on IoT Enterprise

How do you invoke / configure a headless app to run at boot on IoT Enterprise?  The document at the link below indicates that IoT Enterprise does support headless apps, however the iotstartup CLI tool does not appear to be available.
http://wincom.blob.core.windows.net/documents/Windows_10_IoT_Platform_Overview.pdf

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: bfeba98b-ce89-613d-f31e-400faf6eb8c2
Version Independent ID: 6aa7fea5-8c12-3306-4a20-f9ed8dc21344
Content: Background Applications - Windows IoT
Content Source: windows-iotcore/develop-your-app/BackgroundApplications.md
Product: windows-iot
GitHub Login: @saraclay
Microsoft Alias: saclayt

Hi there,
At the moment, a fix is coming in the fall with the RS5 update.


Solaris by Cosmiq works

Great list, have suggested it to multiple people that are looking for DL+Geo ressources.
Solaris should def. be added here, great tool! DL framework for remote sensing data a bit similar to rastervision but with some unique very vool features! https://github.com/CosmiQ/solaris
On mobile for some time so no PR sorry :)

Thanks @chrieke have added it now, cheers!


ionoscloud_group not working "user_ids" is not expected here.

Description
I just copied the user / group example from the docs at https://registry.terraform.io/providers/ionos-cloud/ionoscloud/latest/docs/resources/group and adapted it a little bit.
Expected behavior
Working terraform code.
Environment
Terraform version:
Terraform v1.0.10

Provider version:
    ionoscloud = {
      source = "ionos-cloud/ionoscloud"
      version = "= 6.0.0-alpha.3"
    }

Configuration Files
provider "ionoscloud" {}
variable "users" {
  type    = list(map(string))
  default = []
}
resource "ionoscloud_user" "user" {
  for_each       = var.users
  administrator  = false
  force_sec_auth = false
  first_name     = each.value.first_name
  last_name      = each.value.last_name
  email          = each.value.email
  password       = each.value.password
}
resource "ionoscloud_group" "group" {
  name                           = "group"
  user_ids                       = [ionoscloud_user.user.*.id]
}

How to Reproduce

create the tf file
run terraform init
run terraform plan

Error and Debug Output
│ Error: Unsupported argument
│
│   on main.tf line 33, in resource "ionoscloud_group" "group":
│   33:   user_ids                       = [ionoscloud_user.user.*.id]
│
│ An argument named "user_ids" is not expected here. Did you mean "user_id"?
╵

https://github.com/ionos-cloud/terraform-provider-ionoscloud/blob/master/ionoscloud/resource_group.go#L77

Hi @firecyberice,
This is happening because user_ids has been introduced in version 6.2.0, and you are using 6.0.0-alpha.3, in which the argument was named user_id, not having the possibility of adding multiple users into a group.
We would recommend updating your provider to the latest version, since there are more fixes done in the meantime.

Oh ok but I just copied everything from the docs page. https://registry.terraform.io/providers/ionos-cloud/ionoscloud/latest/docs#example-usage
So there is maybe an update on the docs needed.
Thank you for responding so fast.