support phi 3

@davidgxue  We have validated this PR with modfications on real model quant with pre/post PPL. Ready for merge. Thank you for the Phi3 code!

Test Result:
Phi-3-medium-4k-instruct
Native PPL: 4.189669132232666
Format gptq_v2, Quantized PPL: 4.834439754486084

Awesome work and thank you for adding me on here haha! AutoGPTQ library still seems glitchy? Both LLAMA 3 and Phi3 quants from AutoGPTQ has gibberish output issues when using with transformers... Hopefully this repo is better maintained!

@davidgxue Phi3 appears to contain fused modules and from our experience, any fused modules, will result in less than ideal calibration. That's why you see the Phi-3 post quant much higher (diff vs pre-quant) than other models. As such,  worse output is expected but I still do an issue with bad/gibberish.
If you can provide me with examples of gibberish (are these generated on native or gptq qunated) models? I would highly reocmmend you to re-quant them use GPTQModel as our internal code vs AutoGPTQ will in many cases by default generate higher quality quants due to the optimizations we have made.

Hopefully this repo is better maintained!

This is our pledge, mission statement, and core reason why I pushed our team to fork AutoGPTQ.

Oh yeah the fused modules part is definitely expected.
What I meant is LLAMA 3 and Phi 3 (well i guess they are both llama family maybe) literally not working. I have had this issue open for a long time on AutoGPTQ repo, and im not the only one cuz I released a few GPTQ quants on huggingface and im being spammed in DM or huggingface issues about people experiencing the exact same thing.
https://github.com/AutoGPTQ/AutoGPTQ/issues/657

This is our pledge, mission statement, and core reason why I pushed our team to fork AutoGPTQ.

Love it! Will follow you guys and see if there are stuff I can help out on!


1.3.2 zksolc not compatible with 0.8.18 Solidity

I've been trying to get the zksync compiler to compile contracts which use 0.8.18 but I consistently get this error:
Error: write EPIPE
    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)
error Command failed with exit code 1.

I tried multiple versions but it happens even with all the latest  zksync tools and 1.3.2 zksolc compiler binary.

Support for Solidity 0.8.18 is fixed with 1.3.5 release of the zksync compiler.

How do you think I could fix it? I encountered this issue when building contracts with zksolc-1.3.16 and solc-0.8.17.

@mpopovac-txfusion
Hi, maybe you can help me with this. I just have a MBP on Sonoma.
I follow the instructions from this link - https://docs.zksync.io/build/quick-start/hello-world.html#prerequisites I can compile the contract with solc but with zksolc I always get this error. I tried this same code on my PC. it works as expected just only this laptop that doesn't work :(
I tried using different node version, different zksolc/solc version but still got the same error.
Please advise

Just add an explicit solc dependency to your package.json @zouguangxian - the underlying error comes from require(undefined)

@janjakubnanista Thanks! adding solc to the dependencies worked.


Fix DynamoDB TrackerStore

Proposed changes:

The "old" DynamoDB TrackerStore implementation created one table entry per Tracker update resulting in many objects/rows per user and session. This was caused because of the use of a timestamp (session_date) as part of the table's index. This fix drops the index session_date and only uses the sender_id when creating/updating DB entries.

The PR includes a backward compatibility check to continue usage for DynamoDBs tables with the old schema. It also introduces a deprecation warning for these kind of tables.

Changes we tested together with @tmbo on a private project connecting to DynamoDB.

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[x] updated the changelog (please check changelog for instructions)
[x] reformat files using black (please check Readme for instructions)

@tczekajlo do you have a commit for the CI that I can cherry pick onto this branch to get the build working? (failing due to the github deprecation)

@tczekajlo do you have a commit for the CI that I can cherry pick onto this branch to get the build working? (failing due to the github deprecation)

@tmbo Alas, nothing that would fit the 1.10.x, but here is a PR with the fix https://github.com/RasaHQ/rasa/pull/7367 for the 1.10.x

@hotzenklotz we've fixed the build on RasaHQ:1.10.x, can you please update this PR with the changes on that base branch

@tmbo I updated the base branch. Now all check pass. :-)


Vite template doesn't detect the .server modules

Reproduction
Go to https://stackblitz.com/edit/remix-run-remix-g5iaoj (this is a clone of the Vite template).
Run pnpm run typecheck
We will have 2 issues:
First, we will have an error: error TS2688: Cannot find type definition file for 'node'..
Do we need the node types declaration? If yes, then we need to include @types/node in the devDependencies of package.json. If not, then we need to remove node from the types on tsconfig.json.
Second, if we've already fixed the issue above, then look at the file app/.server/example.ts. It has an error, but when we're running the pnpm run typecheck, it doesn't detect the error. The reason is that TypeScript by default is ignoring hidden files.
System Info
This is Stackblitz system info:

  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.18.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.14.0 - /usr/local/bin/pnpm
  npmPackages:
    @remix-run/dev: ^2.7.2 => 2.7.2
    @remix-run/node: ^2.7.2 => 2.7.2
    @remix-run/react: ^2.7.2 => 2.7.2
    @remix-run/serve: ^2.7.2 => 2.7.2
    vite: ^5.1.4 => 5.1.4

Used Package Manager
pnpm
Expected Behavior
TypeScript should detect errors on the .server directories.
Actual Behavior
It's ignoring the .server directories.

For .server folders, you'll need to explicitly add it to the include array in tsconfig.json. This only applies to files/folders starting with . It will work if you name it something like models.server.
{
  "include": ["env.d.ts", "**/*.ts", "**/*.tsx", "app/.server/**/*.ts"],
  "compilerOptions": {
  }
}

https://github.com/microsoft/TypeScript/issues/49555
As for Node types, that's interesting. In my remix-vite-template, I don't include the types option in my tsconfig.json file. I asked ChatGPT what it thought, and the Cons outweigh the Pros, in my opinion.
🤖 Ask ChatGPT 4
❓ What are the pros and cons of including the types option in tsconfig.json?
Including the types option in tsconfig.json for a TypeScript project can significantly impact how the TypeScript compiler recognizes and uses type definitions in your project. Here are the pros and cons of using this option:
Pros:

Explicit Control Over Available Global Types: By specifying which types are included, you can limit the global type declarations that are available in your project. This is particularly useful in large projects or when using multiple libraries that might define conflicting global types.

Performance Improvement: Limiting the types loaded into your project can lead to faster compilation times, as the TypeScript compiler has fewer type definitions to process. This is especially noticeable in projects with many type declaration files.

Avoiding Type Conflicts: In projects where multiple libraries might define similar global types, specifying which types to include can help avoid conflicts and ambiguous type errors. This makes your type environment more predictable and stable.

Better Code Autocompletion: By controlling which types are available, you can ensure that the code autocompletion features in your IDE are more relevant and less cluttered with types from libraries that are not used in parts of your project.

Cons:

Manual Management: You need to manually manage which types are included in your project. This can become cumbersome, especially as your project grows or as you add and remove dependencies.

Risk of Missing Types: If you forget to include a necessary type definition, you might encounter hard-to-debug errors due to the missing type information. This requires a good understanding of which types your project actually needs.

Overhead in Large Projects: For large projects with many dependencies, configuring and maintaining the types option can become a significant overhead. This might require regular updates to tsconfig.json as dependencies evolve.

Potential for Incomplete Type Safety: Excluding certain types can lead to a false sense of security if parts of your codebase rely on types that are not included. This might result in parts of your code not being fully type-checked.

In summary, using the types option in tsconfig.json gives you more control over your project's type environment, potentially leading to performance improvements and better developer experience. However, it requires careful management and a good understanding of your project's dependencies to avoid missing or conflicting types. The decision to use this option should be based on the specific needs and complexity of your project.
https://chat.openai.com/share/892bd94c-076c-4a5d-9224-f7feeca3d794


Status bar for links in iframes doesn't appear

If you hover a link on an iframe embedded in a page, the minimal status bar doesn't appear.
Here's a example; the MailOnline Video is the embed.

released in v1.13


Extra Blessing

Being able to get an additional Blessing as a Mythic Ability would be nice for Warpriests.

Isn't that just Impossible Domain?


Less error prone way to read frames

Currently you got a reader and a buffer that needs to stay together wherever you read stuff. If you read only from the reader, it works most of the time in small tests, but in the real world you will get a bug whenever there are some bytes in the buffer.
This style is very error prone. Here is a proposed solution:
we have a DerpFrameReader which takes a reader and a buffer and implements Stream<io::Result<(FrameType, Bytes)>> or something. Internally it does all the usual buffer stuff, but then it splits off the bytes.
If the returned Bytes go out of scope before the next call to .next(), this will be just as zero copy as the (&mut reader, &mut buffer) version, but much less error prone, because you get an immutable Bytes where you don't have to remember to drag it along, clear it etc.

Implemented in https://github.com/n0-computer/iroh/pull/1386


Vue config needs VueLoaderPlugin

https://vue-loader.vuejs.org/guide/#manual-configuration
The VueLoaderPlugin is required as part of the default config. I had a go at using this config in a project and I couldn't add sass-loader because the plugin was missing.

Hey Lewis, we're currently running Vue Loader v14, which does not require the plugin. Renovate has opened an automated PR from the branch "renovate/vue-loader-15.x" to upgrade to Vue Loader v15, but I haven't merged this PR because the demo project doesn't build any more on this branch. Would you like to take a look at the migration steps from v14 to v15, which would include adding the plugin?

Hey Keegan, makes sense to me. I'll take a look and make sure we're not breaking anything by migrating.

Fixed by https://github.com/DeloitteDigitalAPAC/webpack-config/pull/11/


Adding stackFromEnd attribute to AtlasMessagesRecyclerView.

AtlasMessageRecyclerView stacks messages from the botton when true
and stacks messages fro top when false
Usage:
<com.layer.atlas.AtlasMessagesRecyclerView
    android:id=@+id/messages_list
    android:layout_width=match_parent
    android:layout_height=match_parent
    app:stackFromEnd=false/>```

Thanks for the pull request. This looks good but there is one issue. Auto scroll to the bottom of the message list is broken. When displaying messages where there are more messages than the height of the screen the RecyclerView stays at the top and doesn't scroll to the newest message. Once this is fixed I would be happy to merge this.

@smpete I wen through the autoscroll and found this piece of code
private void autoScroll() {         int end = mAdapter.getItemCount() - 1;         if (end <= 0) return;         int visible = findLastVisibleItemPosition();         // -3 because -1 seems too finicky         if (visible >= (end - 3)) {             scrollToPosition(end);         }     }
What is doing is only autoscroll if the user is seeing the last 3 messages, if there is more messages than the height of the screen and the user is not seeing any of the the latests 3 will not scroll. That is good to prevent the scroll if the user is reading old messages.
I can't see the problem with that and my change, probably I'm missing something?
Thanks!

The problem is when you initially open the messages view it is not scrolled to the bottom. This has two issues:

It shows the oldest messages instead of the newest messages
When the autoScroll() method is called due to a new message, it will be a no-op since it is not at the bottom of the list

You can see this effect if you have a conversation that has enough messages that it requires a scroll to see them all.

Thanks @smpete I saw the problem. Yes, the scroll remains in the top and I'm afraid we will need a big refactor to solve this situation.
I tried doing a manual scroll after layout the childs, but there is a jump when the list is opened because we can't scroll to bottom before the view is draw.
` getViewTreeObserver().addOnGlobalLayoutListener(new ViewTreeObserver.OnGlobalLayoutListener() {
@Override
public void onGlobalLayout() {
            if(!mStackFromEnd && mAdapter.getItemCount() > 0) {
                scrollToPosition(mAdapter.getItemCount()-1);
                if (Build.VERSION.SDK_INT < Build.VERSION_CODES.JELLY_BEAN) {
                    getViewTreeObserver().removeGlobalOnLayoutListener(this);
                } else {
                    getViewTreeObserver().removeOnGlobalLayoutListener(this);
                }
            }
        }
    });`

The concept in RecyclerView of stackFromEnd = false will not allow us to have the scroll at the bottom and unfortunately we can't know how many items do we have in the list in drawing time :-(

If we could know on initialisation, the number of childs, we could change the AtlasRecyclerView to be stacked from end or not, but that implies to couple the code. Or if we could hide the view until scrolled.. but I don't know how.. Any advice?

We won't be able to know the size at initialization because the query is run asynchronously. Hiding the view until the data is loaded for the first time may be a viable solution but there has to be a cleaner way of doing it. I'll try to find some time in the next few days to work on a solution.

I'm going to close this as we are making major changes to the internals of this recycler view over then next two months. This feature will be included in that work so expect availability in the coming months. If this is needed before that then please re-open.
Thanks!


Tensorboard is down after upgrading to the tensorflow 1.8.0

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
No

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Linux Ubuntu 16.04

TensorFlow installed from (source or binary):
binary

TensorFlow version (use command below):
1.8.0

Python version:
2.7.12

Bazel version (if compiling from source):
No

GCC/Compiler version (if compiling from source):
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609

CUDA/cuDNN version:
CUDA 9.0
cuDNN 7.0

GPU model and memory:
Nvidia Geforece GTX 1080

Exact command to reproduce:
type

sudo pip install tensorboard

and then get

tensorflow 1.4.1 requires tensorflow-tensorboard<0.5.0,>=0.4.0rc1, which is not installed.

But my tensorflow or tensorflow object detection api works.
Describe the problem
Cannot install tensorboard from pip.
Source code / logs
N/A

Something seems amiss with your installation, since the error message says tensorflow 1.4.1, but it seems you're installing 1.8.0?
Can you try upgrading both with:
pip install --upgrade tensorflow tensorboard

Hello @asimshankar ,
Sorry for the late response.
when I type pip install --upgrade tensorflow tensorboard,
I got the following messages and the same error message:

Requirement already up-to-date: tensorflow-gpu in /usr/local/lib/python2.7/dist-packages (1.8.0)
Requirement already up-to-date: tensorboard in /usr/local/lib/python2.7/dist-packages (1.8.0)
Requirement not upgraded as not directly required: mock>=2.0.0 in /home/garmin/.local/lib/python2.7/site-packages (from tensorflow-gpu) (2.0.0)
Requirement not upgraded as not directly required: grpcio>=1.8.6 in /usr/local/lib/python2.7/dist-packages (from tensorflow-gpu) (1.11.0)
Requirement not upgraded as not directly required: enum34>=1.1.6 in /usr/local/lib/python2.7/dist-packages (from tensorflow-gpu) (1.1.6)
Requirement not upgraded as not directly required: numpy>=1.13.3 in /usr/local/lib/python2.7/dist-packages (from tensorflow-gpu) (1.14.3)
Requirement not upgraded as not directly required: termcolor>=1.1.0 in /usr/local/lib/python2.7/dist-packages (from tensorflow-gpu) (1.1.0)
Requirement not upgraded as not directly required: backports.weakref>=1.0rc1 in /usr/local/lib/python2.7/dist-packages (from tensorflow-gpu) (1.0.post1)
Requirement not upgraded as not directly required: absl-py>=0.1.6 in /usr/local/lib/python2.7/dist-packages (from tensorflow-gpu) (0.2.0)
Requirement not upgraded as not directly required: wheel in /usr/local/lib/python2.7/dist-packages (from tensorflow-gpu) (0.31.0)
Requirement not upgraded as not directly required: six>=1.10.0 in /usr/local/lib/python2.7/dist-packages (from tensorflow-gpu) (1.11.0)
Requirement not upgraded as not directly required: gast>=0.2.0 in /usr/local/lib/python2.7/dist-packages (from tensorflow-gpu) (0.2.0)
Requirement not upgraded as not directly required: protobuf>=3.4.0 in /usr/local/lib/python2.7/dist-packages (from tensorflow-gpu) (3.5.2.post1)
Requirement not upgraded as not directly required: astor>=0.6.0 in /usr/local/lib/python2.7/dist-packages (from tensorflow-gpu) (0.6.2)
Requirement not upgraded as not directly required: bleach==1.5.0 in /usr/local/lib/python2.7/dist-packages (from tensorboard) (1.5.0)
Requirement not upgraded as not directly required: futures>=3.1.1; python_version < "3" in /usr/local/lib/python2.7/dist-packages (from tensorboard) (3.2.0)
Requirement not upgraded as not directly required: html5lib==0.9999999 in /usr/local/lib/python2.7/dist-packages (from tensorboard) (0.9999999)
Requirement not upgraded as not directly required: markdown>=2.6.8 in /usr/local/lib/python2.7/dist-packages (from tensorboard) (2.6.11)
Requirement not upgraded as not directly required: werkzeug>=0.11.10 in /usr/local/lib/python2.7/dist-packages (from tensorboard) (0.14.1)
Requirement not upgraded as not directly required: funcsigs>=1; python_version < "3.3" in /home/garmin/.local/lib/python2.7/site-packages (from mock>=2.0.0->tensorflow-gpu) (1.0.2)
Requirement not upgraded as not directly required: pbr>=0.11 in /usr/local/lib/python2.7/dist-packages (from mock>=2.0.0->tensorflow-gpu) (4.0.2)
Requirement not upgraded as not directly required: setuptools in /usr/local/lib/python2.7/dist-packages (from protobuf>=3.4.0->tensorflow-gpu) (39.1.0)
tensorflow 1.4.1 requires tensorflow-tensorboard<0.5.0,>=0.4.0rc1, which is not installed.

when typing python -c 'import tensorflow as tf; print(tf.__version__)'
it shows 1.8.0
Please let me know if any other information you need. Thank you.

I'm confused about why the error message talks about TensorFlow 1.4.1.
Perhaps you have conflicting installs for tensorflow and tensorflow-gpu?
Could you try pip list to see what all you have installed and remove all TensorFlow packages and then reinstall?

Hello @asimshankar ,
The 1.4.1 error is because I have tensorflow-gpu 1.8.0 and tensorflow 1.4.1 installed.
After uninstalling tensorflow 1.4.1, the error is gone.
And here is the output after pip install --upgrade tensorflow-gpu tensorboard

Requirement already up-to-date: tensorflow-gpu in /usr/local/lib/python2.7/dist-packages (1.8.0)
Requirement already up-to-date: tensorboard in /usr/local/lib/python2.7/dist-packages (1.8.0)
Requirement not upgraded as not directly required: mock>=2.0.0 in /home/garmin/.local/lib/python2.7/site-packages (from tensorflow-gpu) (2.0.0)
Requirement not upgraded as not directly required: grpcio>=1.8.6 in /usr/local/lib/python2.7/dist-packages (from tensorflow-gpu) (1.11.0)
Requirement not upgraded as not directly required: enum34>=1.1.6 in /usr/local/lib/python2.7/dist-packages (from tensorflow-gpu) (1.1.6)
Requirement not upgraded as not directly required: numpy>=1.13.3 in /usr/local/lib/python2.7/dist-packages (from tensorflow-gpu) (1.14.3)
Requirement not upgraded as not directly required: termcolor>=1.1.0 in /usr/local/lib/python2.7/dist-packages (from tensorflow-gpu) (1.1.0)
Requirement not upgraded as not directly required: backports.weakref>=1.0rc1 in /usr/local/lib/python2.7/dist-packages (from tensorflow-gpu) (1.0.post1)
Requirement not upgraded as not directly required: absl-py>=0.1.6 in /usr/local/lib/python2.7/dist-packages (from tensorflow-gpu) (0.2.0)
Requirement not upgraded as not directly required: wheel in /usr/local/lib/python2.7/dist-packages (from tensorflow-gpu) (0.31.0)
Requirement not upgraded as not directly required: six>=1.10.0 in /usr/local/lib/python2.7/dist-packages (from tensorflow-gpu) (1.11.0)
Requirement not upgraded as not directly required: gast>=0.2.0 in /usr/local/lib/python2.7/dist-packages (from tensorflow-gpu) (0.2.0)
Requirement not upgraded as not directly required: protobuf>=3.4.0 in /usr/local/lib/python2.7/dist-packages (from tensorflow-gpu) (3.5.2.post1)
Requirement not upgraded as not directly required: astor>=0.6.0 in /usr/local/lib/python2.7/dist-packages (from tensorflow-gpu) (0.6.2)
Requirement not upgraded as not directly required: bleach==1.5.0 in /usr/local/lib/python2.7/dist-packages (from tensorboard) (1.5.0)
Requirement not upgraded as not directly required: futures>=3.1.1; python_version < "3" in /usr/local/lib/python2.7/dist-packages (from tensorboard) (3.2.0)
Requirement not upgraded as not directly required: html5lib==0.9999999 in /usr/local/lib/python2.7/dist-packages (from tensorboard) (0.9999999)
Requirement not upgraded as not directly required: markdown>=2.6.8 in /usr/local/lib/python2.7/dist-packages (from tensorboard) (2.6.11)
Requirement not upgraded as not directly required: werkzeug>=0.11.10 in /usr/local/lib/python2.7/dist-packages (from tensorboard) (0.14.1)
Requirement not upgraded as not directly required: funcsigs>=1; python_version < "3.3" in /home/garmin/.local/lib/python2.7/site-packages (from mock>=2.0.0->tensorflow-gpu) (1.0.2)
Requirement not upgraded as not directly required: pbr>=0.11 in /usr/local/lib/python2.7/dist-packages (from mock>=2.0.0->tensorflow-gpu) (4.0.2)
Requirement not upgraded as not directly required: setuptools in /usr/local/lib/python2.7/dist-packages (from protobuf>=3.4.0->tensorflow-gpu) (39.1.0)

However,
when trying to use tensorboard, I got

tensorboard: command not found

In /usr/local/lib/python2.7/dist-packages
I have

tensorboard
tensorboard-1.8.0.dist-info
tensorflow
tensorflow_gpu-1.8.0.dist-info

And I cannot find main.py in tensorboard, like this discussion feed.
Any suggestion?
Thank you for helping!

Hello @asimshankar
After

sudo pip uninstall tensorflow-gpu

pip install tensorflow-gpu

Both tensorflow and tensorboard work.
Thank you for helping.


Add more dynamic inputs to DynamicConvOp

Request description
Currently DynamicConvOp supports computed padding. We will also need computed window_strides, lhs_dilation and rhs_dilation.
I also notice that the op takes padding both as an input and as an attribute. JAX does not use the padding attribute, but I thought I'd point this out in case it is a mistake.

I noticed that JAX's batching rules will end up making batch_group_count and feature_group_count dynamic if some of the input dimensions are dynamic. Hence, we need dynamic support for these also.


signup failed

hi , when I click "Next" btn , I got below issue , anyone know what cause ? thanks.

You need to apply latest database migrations. Run:
supabase migration up

hi @vnktsh  thanks for U reply , but after your suggest , I still got same error.

did you run git pull

yes , I using newest code with main branch

It's a little strange. I don't have a problem if I don't use Chrome. I can access it normally if I change to use Safrai.
@vnktsh

oh , issue cause I installed CORS plugin in Chrome, thanks for help


Update the Profile README for the organization

Feature details?
The current README is good enough & I made some subtle changes to it by adding more info like;

What the community is & what does it stand for?
Where are the members of the community from?
How can one become a member of the community and/or server it?

Feel free to take a look at the modified example.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

In becoming the part of the community section, we have mentioned GOI, I don't think we should do that right now considering we have no accreditation whatsoever,
Let's remove that for now, apart from that, everything looks good, just need some paragraph separations

....I don't think we should do that right now considering we have no accreditation whatsoever.

Yeah totally makes sense, so +1 on that.
I'll prep a PR for this issue in a couple of days & send it for review then.


number type should no longer differentiate between integer and decima…

…l notation when used in indexes. (Issue inmanta/inmanta-core#6526, PR #6772)
Description

create the float type which is like a float in python. Update documentation to mention number will be deprecated

add testcases for following scenario and fix it

entity A:
    float x
end

implement A using std::none

index A(x)

std::print(A(x=0) == A(x=0.0))

This will still not work with the number type

index lookup on float with int should work

closes https://github.com/inmanta/inmanta-core/issues/6526
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[x] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Merged into branches iso6 in 26d8f2e94aa089dba33177b75b63b6e29dd6e5e1


iOS 11 Location Permissions

Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)

[x] iOS
[] Android
[] UWP
[] .NET Standard

Version of OS(s) listed above with issue
11+
Version of Library
2.0
Expected Behaviour
If I have some time, I may send you a pull request to help make supporting the "'WhenInUse" Location Services permission.
Actual Behavior
If applicable, please include entire exception - type, message, stacktrace
Suggesting that you might want to update the setup nsection that the this plugin requires iOS 11 "Location Always" permission rather than just the regular location services permission from iOS 10 and earlier.
As a result, all three of these are required in info.plist:
NSLocationAlwaysUsageDescription
Your message
NSLocationWhenInUseUsageDescription
your message
NSLocationAlwaysAndWhenInUseUsageDescription
your message
James M's Permissions Plugin added support for this 9 days ago.
https://www.nuget.org/packages/Plugin.Permissions
Code of Conduct

No Library Update Requests
No Timeline Requests
Please read through the documentation and FAQs
Please be respectful of my time. I put a lot of effort into my libraries.  I try to support the issue requests within a day.  I'm not psychic, so please take the time to fill out the above form as complete as possible

Did I mention this plugin great? ;-)

I appreciate the offer.  This library doesn't directly call for permissions.  Android and uwp make use of the geolocation plugin which does this.


Testpmd benchmark fails: Testpmd pod keeps crashing and trex pod runs for few seconds then goes in error state

I am testing testpmd DPDK app as a benchmark on Intel NICs (XXV710) with OpenShift cluster 4.6. Upon running the benchmark as given below:
oc create -f dpdkapp.yaml
apiVersion: ripsaw.cloudbulldozer.io/v1alpha1
kind: Benchmark
metadata:
  name: testpmd-benchmark
  namespace: my-ripsaw
spec:
  clustername: mycluster
  workload:
    name: testpmd
    args:
      privileged: true
      pin: true
      pin_testpmd: "worker1"
      pin_trex: "worker1"
      networks:
        testpmd:
          - name: testpmd-sriov-network
            count: 2  # Interface count, Min 2
        trex:
          - name: testpmd-sriov-network
            count: 2

The benchmark gets created, the testpmd pod keeps restarting by going into crashloopback, error states. Whereas, trex pod runs for few seconds then it goes into error state.
The logs for trext pod are given below:
$ oc logs -f trex-traffic-gen-pod-1760b18a-z54q9
2021-08-12T10:12:30Z - INFO     - MainProcess - run_snafu: logging level is INFO
2021-08-12T10:12:30Z - INFO     - MainProcess - _load_benchmarks: Successfully imported 1 benchmark modules: uperf
2021-08-12T10:12:30Z - INFO     - MainProcess - _load_benchmarks: Failed to import 0 benchmark modules:
2021-08-12T10:12:30Z - INFO     - MainProcess - run_snafu: Not connected to Elasticsearch
2021-08-12T10:12:30Z - INFO     - MainProcess - wrapper_factory: identified trex as the benchmark wrapper
2021-08-12T10:12:30Z - INFO     - MainProcess - trigger_trex: Starting TRex Traffic Generator..
Traceback (most recent call last):
  File "/usr/local/bin/run_snafu", line 33, in <module>
    sys.exit(load_entry_point('snafu', 'console_scripts', 'run_snafu')())
  File "/opt/snafu/snafu/run_snafu.py", line 166, in main
    for i in process_generator(index_args, parser):
  File "/opt/snafu/snafu/run_snafu.py", line 194, in process_generator
    for action, index in data_object.emit_actions():
  File "/opt/snafu/snafu/trex_wrapper/trigger_trex.py", line 68, in emit_actions
    documents = self._json_payload(stdout)
  File "/opt/snafu/snafu/trex_wrapper/trigger_trex.py", line 33, in _json_payload
    payload = json.loads(data)
  File "/usr/lib64/python3.6/json/__init__.py", line 354, in loads
    return _default_decoder.decode(s)
  File "/usr/lib64/python3.6/json/decoder.py", line 339, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib64/python3.6/json/decoder.py", line 357, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

I have run these testpmd and trex separately as pods using their base images and they work fine. But my use case is to test the DPDK app as a benchmark using the operator.
Help from the community will be highly appreciated.

I have asked @mukrishn to check this out, but looking at the log, it would seem the issue is that you didn't provide a Elasticsearch URL. This would be a bug, as we shouldn't require a ES URL to be passed. If my assumptions are correct.
To verify this, you could use our development ES instance to try this. https://search-perfscale-dev-chmf5l4sh66lvxbnadi4bznl3a.us-west-2.es.amazonaws.com:443

@jtaleric  I have tried running on your test cluster but facing the same issue. The details are given below:
apiVersion: ripsaw.cloudbulldozer.io/v1alpha1
kind: Benchmark
metadata:
  name: testpmd-benchmark
  namespace: my-ripsaw
spec:
  elasticsearch:
    url: "https://search-perfscale-dev-chmf5l4sh66lvxbnadi4bznl3a.us-west-2.es.amazonaws.com:443"
  workload:
    name: testpmd
    args:
      privileged: true
      pin: true
      pin_testpmd: "worker1"
      pin_trex: "worker1"
      networks:
        testpmd:
          - name: testpmd-sriov-network
            count: 2  # Interface count, Min 2
        trex:
          - name: testpmd-sriov-network
            count: 2

Pods (testpmd and trex) goes in error state. Logs are attached below:
Testpmd pod
Events:
  Type     Reason          Age                            From               Message
  ----     ------          ----                           ----               -------
  Normal   Scheduled       <invalid>                      default-scheduler  Successfully assigned my-ripsaw/testpmd-application-pod-ae0f8c98-28wnk to r192bc2.oss.labs
  Normal   AddedInterface  <invalid>                      multus             Add eth0 [<IP_ADDRESS>/23]
  Normal   AddedInterface  <invalid>                      multus             Add net1 [<IP_ADDRESS>/24] from my-ripsaw/testpmd-sriov-network
  Normal   AddedInterface  <invalid>                      multus             Add net2 [<IP_ADDRESS>/24] from my-ripsaw/testpmd-sriov-network
  Normal   Pulled          <invalid>                      kubelet            Successfully pulled image "registry.redhat.io/openshift4/dpdk-base-rhel8:v4.6" in 1.099241488s
  Normal   Pulling         <invalid> (x2 over <invalid>)  kubelet            Pulling image "registry.redhat.io/openshift4/dpdk-base-rhel8:v4.6"
  Normal   Created         <invalid> (x2 over <invalid>)  kubelet            Created container testpmd
  Normal   Started         <invalid> (x2 over <invalid>)  kubelet            Started container testpmd
  Normal   Pulled          <invalid>                      kubelet            Successfully pulled image "registry.redhat.io/openshift4/dpdk-base-rhel8:v4.6" in 1.050182689s
  Warning  BackOff         <invalid> (x2 over <invalid>)  kubelet            Back-off restarting failed container

Trex pod
$ oc logs -f trex-traffic-gen-pod-ae0f8c98-7k8xm
2021-08-12T12:42:31Z - INFO     - MainProcess - run_snafu: logging level is INFO
2021-08-12T12:42:31Z - INFO     - MainProcess - _load_benchmarks: Successfully imported 1 benchmark modules: uperf
2021-08-12T12:42:31Z - INFO     - MainProcess - _load_benchmarks: Failed to import 0 benchmark modules:
2021-08-12T12:42:31Z - INFO     - MainProcess - run_snafu: Using elasticsearch server with host: https://search-perfscale-dev-chmf5l4sh66lvxbnadi4bznl3a.us-west-2.es.amazonaws.com:443
2021-08-12T12:42:31Z - INFO     - MainProcess - run_snafu: Using index prefix for ES: ripsaw-testpmd
2021-08-12T12:42:31Z - INFO     - MainProcess - run_snafu: Turning off TLS certificate verification
2021-08-12T12:42:31Z - INFO     - MainProcess - run_snafu: Connected to the elasticsearch cluster with info as follows:
2021-08-12T12:42:32Z - INFO     - MainProcess - run_snafu: {
    "name": "510fddd9ea3242aefad127567cffc68e",
    "cluster_name": "415909267177:perfscale-dev",
    "cluster_uuid": "Xz2IU4etSieAeaO2j-QCUw",
    "version": {
        "number": "7.10.2",
        "build_flavor": "oss",
        "build_type": "tar",
        "build_hash": "unknown",
        "build_date": "2021-05-21T20:25:46.519671Z",
        "build_snapshot": false,
        "lucene_version": "8.7.0",
        "minimum_wire_compatibility_version": "6.8.0",
        "minimum_index_compatibility_version": "6.0.0-beta1"
    },
    "tagline": "You Know, for Search"
}
2021-08-12T12:42:32Z - INFO     - MainProcess - py_es_bulk: Using streaming bulk indexer
2021-08-12T12:42:32Z - INFO     - MainProcess - wrapper_factory: identified trex as the benchmark wrapper
2021-08-12T12:42:32Z - INFO     - MainProcess - trigger_trex: Starting TRex Traffic Generator..
Traceback (most recent call last):
  File "/usr/local/bin/run_snafu", line 33, in <module>
    sys.exit(load_entry_point('snafu', 'console_scripts', 'run_snafu')())
  File "/opt/snafu/snafu/run_snafu.py", line 139, in main
    es, process_generator(index_args, parser), parallel_setting
  File "/opt/snafu/snafu/utils/py_es_bulk.py", line 171, in streaming_bulk
    for ok, resp_payload in streaming_bulk_generator:
  File "/usr/local/lib/python3.6/site-packages/elasticsearch/helpers/actions.py", line 320, in streaming_bulk
    actions, chunk_size, max_chunk_bytes, client.transport.serializer
  File "/usr/local/lib/python3.6/site-packages/elasticsearch/helpers/actions.py", line 155, in _chunk_actions
    for action, data in actions:
  File "/opt/snafu/snafu/utils/py_es_bulk.py", line 117, in actions_tracking_closure
    for cl_action in cl_actions:
  File "/opt/snafu/snafu/run_snafu.py", line 194, in process_generator
    for action, index in data_object.emit_actions():
  File "/opt/snafu/snafu/trex_wrapper/trigger_trex.py", line 68, in emit_actions
    documents = self._json_payload(stdout)
  File "/opt/snafu/snafu/trex_wrapper/trigger_trex.py", line 33, in _json_payload
    payload = json.loads(data)
  File "/usr/lib64/python3.6/json/__init__.py", line 354, in loads
    return _default_decoder.decode(s)
  File "/usr/lib64/python3.6/json/decoder.py", line 339, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib64/python3.6/json/decoder.py", line 357, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

@MuhammadMunir12 so you mentioned that your testpmd pod kept restarting and got in to crashloopback that worries me much, if testpmd pod isn't running trex would definitely fail. Could you paste the error from testpmd pod?
I am assuming the pods are pinned to a different worker node although your referred CR has same, just checking because we have the pod Antiaffinity check here

@mukrishn I have pinned them on different worker nodes this time but still the issue is same. Logs for testpmd pod are attached.
$ oc logs -f testpmd-application-pod-f28e6493-m4t2t
EAL: Detected 72 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Auto-detected process type: PRIMARY
EAL: Multi-process socket /tmp/dpdk/pg/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: PCI device 0000:d8:0a.2 on NUMA socket 1
EAL:   probe driver: 8086:154c net_i40e_vf
EAL: PCI device 0000:d8:0a.3 on NUMA socket 1
EAL:   probe driver: 8086:154c net_i40e_vf
testpmd: No probed ethernet devices
Fail: input rxq (1) can't be greater than max_rx_queues (0) of port 0
EAL: Error - exiting with code: 1
  Cause: rxq 1 invalid - must be >= 0 && <= 0

@jtaleric That is not requirement for running this as benchmark btw, may be it's required in Uperf. But i'm not sure about it.

It shouldn't be a requirement. However, some things do slip through the cracks. However, it would be good to catch this issue, vs drop a traceback.

Hi, I filed https://github.com/cloud-bulldozer/benchmark-wrapper/pull/322 to help debugging the json parsing issues. As soon is merged, mind you try running the workload again adding debug: true in the Benchmark YAML?

@mukrishn  I have added socket_memory from Numa 1, then tried other parameters like:
memory_channels: 4
    forwarding_cores: 4
    rx_queues: 1
    tx_queues: 1
    rx_descriptors: 1024
    tx_descriptors: 1024
    forward_mode: "mac"
    stats_period: 1
    disable_rss: true

But still the issue is still there.

@MuhammadMunir12 could you share the SRIOV and PAO policies you used ?

@rsevilla87 Kindly verify if I've added debug flag at the right place. With this CR, the issue still persists.
$ cat dpdk-app.yaml
apiVersion: ripsaw.cloudbulldozer.io/v1alpha1
kind: Benchmark
metadata:
  name: testpmd-benchmark
  namespace: my-ripsaw
spec:
  clustername: r192b
  workload:
    name: testpmd
    debug: true
    args:
      socket_memory: 0,1024
      memory_channels: 4
      forwarding_cores: 4
      rx_queues: 1
      tx_queues: 1
      rx_descriptors: 1024
      tx_descriptors: 1024
      forward_mode: "mac"
      stats_period: 1
      disable_rss: true
      privileged: true
      pin: true
      pin_testpmd: "r192bc2.oss.labs"
      pin_trex: "r192bmw.oss.labs"
      networks:
        testpmd:
          - name: testpmd-sriov-network
            count: 2  # Interface count, Min 2
        trex:
          - name: testpmd-sriov-network
            count: 2

@mukrishn The DPDK node policy is:
$ cat intel-dpdk-node-policy.yaml
apiVersion: sriovnetwork.openshift.io/v1
kind: SriovNetworkNodePolicy
metadata:
 name: intel-dpdk-node-policy-for-testpmd
 namespace: openshift-sriov-network-operator
spec:
 resourceName: intelnics
 nodeSelector:
   node-role.kubernetes.io/worker-cnf: ""
 numVfs: 5
 nicSelector:
   pfNames: ["ens3f1"]
   rootDevices: ["0000:d8:00.1"]
 deviceType: netdevice
 isRdma: false

The PAO manifest is:
$ cat pao.yaml
apiVersion: v1
kind: Namespace
metadata:
  name: openshift-performance-addon-operator
  labels:
    openshift.io/run-level: "1"
---
apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
  name: openshift-performance-addon-operator
  namespace: openshift-performance-addon-operator
spec:
  targetNamespaces:
  - openshift-performance-addon-operator
---
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: openshift-performance-addon-operator-subscription
  namespace: openshift-performance-addon-operator
spec:
  channel: "4.6"
  name: performance-addon-operator
  source: redhat-operators
  sourceNamespace: openshift-marketplace

The performance profile is:
$ cat perf-profile.yaml
apiVersion: performance.openshift.io/v1
kind: PerformanceProfile
metadata:
  name: r192b-performanceprofile
spec:
  additionalKernelArgs:
    - nmi_watchdog=0
    - audit=0
    - mce=off
    - processor.max_cstate=1
    - idle=poll
    - intel_idle.max_cstate=0
  cpu:
    isolated: "2-35,38-71"
    reserved: "0,1,36,37"
  hugepages:
    defaultHugepagesSize: 1G
    pages:
    - size: "1G"
      count: 16
  realTimeKernel:
    enabled: true
  numa:
    topologyPolicy: "restricted"
    # topologyPolicy: "best-effort" # May change performance, but this can be used
  nodeSelector:
    node-role.kubernetes.io/worker-cnf: ""

The only strange thing is that I have used "netdevice" driver with Intel NICs because "vfio-pci" was not creating VFs.

@MuhammadMunir12, debug: true is nested under args

@MuhammadMunir12 It has to be vfio-pci for Intel XXV710 cards, as you can see the testpmd application tries to load VFIO modules. We have documented in SR-IOV configuration for different cards.
Also make sure you have Hugepages allocated on NUMA Socket 1 on the worker nodes. cat /sys/devices/system/node/node*/meminfo | fgrep Huge

@rsevilla87 That doesn't change anything with debug flag set to true.

Hey, I just merged the debug patch, can you try again?

@rsevilla87 That doesn't change anything with debug flag set to true.

Hey, I just merged the debug patch, can you try again?

@mukrishn Using vfio-pci for node policy doesn't create VFs on the given interface.
And yes hugepages are allocated to both Numa sockets.
Node 0 HugePages_Total:     8
Node 0 HugePages_Free:      8
Node 0 HugePages_Surp:      0
Node 1 HugePages_Total:     8
Node 1 HugePages_Free:      8
Node 1 HugePages_Surp:      0

@rsevilla87 Thank you. I have checked but it's not working. As @mukrishn  mentioned that for Intel driver must be vfio-pci but with this driver I'm unable to create VFs using node policy, VFs are created only when I use netdevice driver type which is for Mellanoc NICs.  I don't understand why it's behaving like this.

@MuhammadMunir12 May be you can try, netdevice with isRdma: true.

@mukrishn That can be tried, but it's set to true in Mellanox NICs for DPDK.

@mukrishn Didn't work on netdevice with isRdma: true.
@jtaleric  Any updates at your end regarding this issue?

@jtaleric  Can we see which dpdk version is used by benchmark operator for running the dpdk apps?

@MuhammadMunir12  testpmd pod image - registry.redhat.io/openshift4/dpdk-base-rhel8:v4.6, it runs dpdk-19.11-5.el8_2.x86_64, you can also find the packages here
You can also use your own image - ref


Support to collapse/expand account subscriptions in Account Management Panel

Storage Explorer Version: 1.5.0
Platform/OS Version: Windows 10/ Linux Ubuntu 16.04/ MacOS High Sierra
Architecture: ia32/x64
Build Number:20180828.2
Commit: ca058b20
Regression From: Not a regression
Background:
There added several accounts which included multiple subscriptions, we think it is convenient to apply required subscriptions of one specific account if we can collapse the unused account subscriptions.

Will be tracked together with #1326


E2e test fixes

Fix and enhance e2e tests to not block on watch feature of draft up. They were previously hanging.
Ensure we clean the right helm chart and get some clearer output.

@didrocks,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

@didrocks, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot


(gh-646) Create random keypair

Can one of the admins verify this patch?

@anodelman done

ok to test

:red_circle: Test failed.
Refer to this link for build results: http://jenkins-beaker.delivery.puppetlabs.net/job/Beaker Combined Smoketest/458/

@puppetlabs-jenkins retest this please

:red_circle: Test failed.
Refer to this link for build results: http://jenkins-beaker.delivery.puppetlabs.net/job/Beaker Combined Smoketest/488/

retest this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/Beaker Combined Smoketest/489/
:red_circle: Test failed.

Failure unrelated to patch.

@anodelman missing @param added

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/Beaker Combined Smoketest/509/
:green_heart: Test passed.

:+1:

@anodelman fixed

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/Beaker Combined Smoketest/551/
:red_circle: Test failed.

retest this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/Beaker Combined Smoketest/565/
:red_circle: Test failed.

Known deb7 foss test failures.


[0.76.0] fresh install - ios doesn't build

Description
a fresh install of react native 0.76 can't build on ios
Steps to reproduce

create a fresh 0.76 project npx @react-native-community/cli init reaswipeable --version 0.76.0
npx react-native run-ios

i also tried, cd ios && bundle exec pod install before running the app
React Native Version
0.76.0
Affected Platforms
Build - MacOS
Areas
Other (please specify)
Output of npx react-native info
info Fetching system and libraries information...
(node:65073) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
System:
  OS: macOS 14.6.1
  CPU: (10) arm64 Apple M1 Max
  Memory: 3.74 GB / 64.00 GB
  Shell:
    version: 3.7.1
    path: /opt/homebrew/bin/fish
Binaries:
  Node:
    version: 21.6.2
    path: ~/.local/state/fnm_multishells/1047_1729280623995/bin/node
  Yarn:
    version: 1.22.22
    path: /opt/homebrew/bin/yarn
  npm:
    version: 10.2.4
    path: ~/.local/state/fnm_multishells/1047_1729280623995/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /Users/jbrodriguez/.rbenv/shims/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.5
      - iOS 17.5
      - macOS 14.5
      - tvOS 17.5
      - visionOS 1.2
      - watchOS 10.5
  Android SDK: Not Found
IDEs:
  Android Studio: 2023.1 AI-231.9392.1.2311.11255304
  Xcode:
    version: 15.4/15F31d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.12
    path: /usr/bin/javac
  Ruby:
    version: 3.3.0
    path: /Users/jbrodriguez/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 15.0.0-alpha.2
    wanted: 15.0.0-alpha.2
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.76.0
    wanted: 0.76.0
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: true
  newArchEnabled: true

### Stacktrace or Logs

```text
###  directly running npx react-native run-ios

╰─❯ npx react-native run-ios
(node:79530) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
info Found Xcode workspace "reaswipeable.xcworkspace"
info Found booted iPhone 15 Pro
info Building (using "xcodebuild -workspace reaswipeable.xcworkspace -configuration Debug -scheme reaswipeable -destination id=3A2F2FE5-F16E-4A17-A676-0B03EB072ACB")

info 💡 Tip: Make sure that you have set up your development environment correctly, by running npx react-native doctor.  To debug build logs further, consider building your app with Xcode.app, by opening 'reaswipeable.xcworkspace'.
info Run CLI with --verbose flag for more details.

running cd ios && bundle exec pod install
╰─❯ npx react-native run-ios
(node:80506) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
info A dev server is already running for this project on port 8081.
info Found Xcode workspace "reaswipeable.xcworkspace"
info Found booted iPhone 15 Pro
info Building (using "xcodebuild -workspace reaswipeable.xcworkspace -configuration Debug -scheme reaswipeable -destination id=3A2F2FE5-F16E-4A17-A676-0B03EB072ACB")

info 💡 Tip: Make sure that you have set up your development environment correctly, by running npx react-native doctor. To read more about doctor command visit: https://github.com/react-native-community/cli/blob/main/packages/cli-doctor/README.md#doctor

error export CLANG_WARN_DOCUMENTATION_COMMENTS\=YES
error export CLANG_WARN_QUOTED_INCLUDE_IN_FRAMEWORK_HEADER\=NO
error export GCC_WARN_UNDECLARED_SELECTOR\=YES
error export VALIDATE_PRODUCT\=NO
error Failed to build ios project. "xcodebuild" exited with error code '65'. To debug build logs further, consider building your app with Xcode.app, by opening 'reaswipeable.xcworkspace'.
info Run CLI with --verbose flag for more details.

### Reproducer

https://github.com/jbrodriguez

### Screenshots and Videos

_No response_

@jbrodriguez Thanks for the issue.
after running bundle install and bundle exec pod install, can you try opening the reaswipeable.xcworkspace file with Xcode and try to build from there?

@cipolleschi sure, here are the last few lines of the xcode output
/Users/jbrodriguez/code/reaswipeable/ios/Pods/../.xcode.env.local: line 1: export: `Support/fnm/node-versions/v21.6.2/installation/bin/node': not a valid identifier
Node found at: /Users/jbrodriguez/Library/Application
/Users/jbrodriguez/Library/Developer/Xcode/DerivedData/reaswipeable-cgsxwhbkujbpstcvtyvnadbxkcve/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/hermes-engine.build/Script-46EB2E00018FC0.sh: line 9: /Users/jbrodriguez/Library/Application: No such file or directory
Command PhaseScriptExecution failed with a nonzero exit code

so, something about node paths

@cipolleschi ok, i quoted the node binary in .xcode.env.local and it works now

seems like this file is generated, just need to escape the path

oh... because you have a space in the path! 🤦
Thanks for figuring this out!

It's fixed by this commit: eeaa3ff458a3e5c902075bb45161d6ccde31fe53
Next week we will release 0.76.1 and we will pick the commit in it: https://github.com/reactwg/react-native-releases/issues/592

Hello, i try all soluce, and all not work for me. Xcode: Version 16.1 (16B40), react-native: 0.76.1

@gh-pro sorry to hear that. I, this morning, run an app on a real device using Xcode 16.1 and react native 76.1.
What happens when you try to build on a real device? Do you see any error?


validator: work around mysterious behavior of maven-assembly-plugin

The problem is that somehow directories in dependency jars become empty
files in the -jar-with-dependencies jars.  Not an issue when invoked via
java -jar, but Guilhem reports that this prevents the web app from
starting.
Good:
   0  Stored        0   0% 05-26-2014 21:18 00000000  META-INF/maven/commons-beanutils/

Bad:
   0  Defl:N        2   0% 05-26-2014 21:18 00000000  META-INF/maven/commons-beanutils

So the affected directories were found with

unzip -v validator/target/odfvalidator-1.0.0-BETA2-SNAPSHOT-jar-with-dependencies.jar | grep "Defl:N *2 "

The jars in odfdom, xslt-runner are also affected.
Bisecting shows this started with:
commit 2a6d4fc2b45eed57f83604c5de92941629508ece
Merging the ODF collaboration work from https://github.com/svanteschubert/odftoolkit/tree/odf-changes

... and bisecting in that git repo gives:
commit b04c5828ba32987adde85396d3ec82374c255124
Merge of collaboration feature branch with main trunc. Becoming 1.0.0-SNAPSHOT of the ODF Toolkit at The Document Foundation (TDF)

... but it's not obvious what change caused this.
The only obvious work-around is not actually obvious but at least it's
quite undeniably ridiculous, and i disclaim any insight of why it
appears to give the correct result.
Note: i hope somebody has a better idea than this nonsense? Maybe @sebkur :)

Fixed this with Michael in Mathml01 PR


help: Fix help center loading scrolled down.

We were trying scroll the highlighted element but it also scrolls the parent elements leading to scrolling of the help doc.
We don't need to scroll here at all actually since focused element is scrolled to be visible by default. Tested in chrome, firefox and safari on mac by going to http://aman.zulipdev.org:9991/help/support-zulip-project
fixes: https://chat.zulip.org/#narrow/stream/9-issues/topic/.F0.9F.8E.AF.20landing.20low.20on.20help.20pages
dones't fix: https://chat.zulip.org/#narrow/stream/9-issues/topic/.F0.9F.8E.AF.20anchor.20link.20partially.20hidden.20in.20help.20center (which I still cannot reproduce)

Merged, thanks @amanagr!


missing json file

I've attempted to run this project but getting a #404 on /json/offsets.json
Can you commit this file to project? Or is it a private config file that we need to create ourselves - if so...what's the structure?

this morning my subconscious tipped me off that I should look in your demo and sure enough I found the missing json and the images I needed to recreate this awesome demo. I've forked it - are you open to pull a request?
offsets
data
settings


[ISSUE-2687] fix insert NaN bug

Fix the issue #2687 part 2.

This PR has:

[ ] been self-reviewed.

[ ] concurrent read
[ ] concurrent write
[ ] concurrent read and write

[ ] added documentation for new or modified features or behaviors.
[ ] added Javadocs for most classes and all non-trivial methods.
[ ] added or updated version, license, or notice information
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious
for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold
for code coverage.
[ ] added integration tests.
[ ] been tested in a test IoTDB cluster.

Key changed/added classes (or packages if there are too many classes) in this PR

Fix the issue #2687 part 2.
This PR has:

[ ]  been self-reviewed.

[ ]  concurrent read
[ ]  concurrent write
[ ]  concurrent read and write

[ ]  added documentation for new or modified features or behaviors.

[ ]  added Javadocs for most classes and all non-trivial methods.

[ ]  added or updated version, license, or notice information

[ ]  added comments explaining the "why" and the intent of the code wherever would not be obvious
for an unfamiliar reader.

[ ]  added unit tests or modified existing tests to cover new code paths, ensuring the threshold
for code coverage.

[ ]  added integration tests.

[ ]  been tested in a test IoTDB cluster.

Key changed/added classes (or packages if there are too many classes) in this PR

Hi, @HTHou:
Something like the pic below also should be modified:

+1


PyTest: Evaluate integration of a priority matrix

What would you like to be added:
We should evaluate the integration of a priority matrix or priority system for running PyTests. Currently, some issues without having a priority system can be solved by fixtures but it may be needed in the future.
Why is this needed:
It might be a problem when having the same test with different test options from combined features.
Example:
It might be a problem having a test that gets called from different features with different options at the same time.
feature-foo:
test -> NTP -> server -> check for: <IP_ADDRESS>
feature-aws:
test -> NTP -> server -> check for: <IP_ADDRESS>
One if this tests might fail. However, last one or highest feature priority could win.

This could be solved by:

Last one wins
Adapting priorities from features (flag -> element -> platform)
Priority mapping within a dedicated matrix file
Priority mapping within features YAML config
[...]

We should check if there are already such tests which would overwrite each other or if this might be a problem in future. Having a test in multiple features can be problematic but it can also work especially if the tests don't need to check specific values but could test something differently.
The question is, if we are able to implement such a priority system and how much effort it would take. Someone could for example also try to adjust the affected tests in such a way that they can run multiple times in different features. If we take a look at the NTP example of this issue, one could test the existence of working NTP instead of checking a specific value set, so that the test doesn't check for an actual NTP Server but if the NTP daemon is able to get a proper time and is up and running. In most cases, it isn't important what NTP Server is configured but if NTP is running properly.
Before implementing a priority system, we should verify the latter one first.

As discussed, we may close this issue due to the already mentioned workaround and do not waste any efforts here anymore. If this should get urgent in any way (e.g. by upcoming feature implementations) we may reopen this anytime.


[Bug]: GSheets with only header cannot be used for page generation

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
A GSheet datasource with only headers on the sheet cannot be used for page generation. Dummy data would need to be added for to activate Generate Page button.

Steps To Reproduce

Create a Google Sheet with only headers and use this to generate a page
Observe that the button is inactive until dummy data is added to the column headers

Environment
Production
Version
Cloud

Stats

Stat
Values

Reach
50

Effort (months)
0.5


How can I automatically generate a thumbnail right after video exported using ffmpeg ?

Checklist

[x] I'm asking a question
[x] I've looked through the README and FAQ for similar questions
[x] I've searched the bugtracker for similar questions including closed ones

Question

Hi I'm using PHP to download the videos and I was wondering how can I automatically  generate a thumbnail using ffmped right after the video finished downloading?
    shell_exec( "yt-dlp -f --windows-filenames --restrict-filenames --replace-in-metadata title '#' ' ' 'bestvideo[ext=mp4]+bestaudio[ext=m4a]/bestvideo+bestaudio' $name -v --merge-output-format mp4 -f 137+140" );
I'm wondering if there is a way to integrate ffmpeg into the command to create a thumbnail after the video output?
If there is no way, there is a way to export a jpg instead of a webp image using --write-thumbnail  ?

Yes, --exec ..., but as you are using yt-dlp ask there. yt-dlp has more options relevant to your question.


[Timeline] Skip performances check when not in debug mode

Currently performances are checked even if the mode debug is not enabled.
Debug mode is taken into consideration only when logging to the console.
Extend the check to the performances check as well.
The function executeWithPerfomanceCheck at src/utils/utils.ts should only return the result of function execution if the debug mode is not enabled, otherwise it should be surrounded by all the log and timing features.
To understand how to dermine if the app is in debug mode or not, please give a look to the logDebug function.

:tada: This issue has been resolved in version 1.15.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Implement Token Introspection Endpoint

Issue https://github.com/spring-projects-experimental/spring-authorization-server/issues/52
Added support to the Token Introspection Endpoint as per the description in the ticket above.

Hey @jgrandja I prepared this PR for the Token Introspection Endpoint.
I've made a few comments in the PR to discuss a few aspects, but first I want to point out I have quite a few formatting changes even though I'm sticking to the .editorconfig file we have in the root of the project. Should I revert all these changes to make the PR more readable?

Thanks for the PR @rozagerardo!
I'm a bit backlogged at the moment so I'll try to review this mid to end next week.
I did take a quick glance and noticed quite a bit of formatting changes. Can you please revert all formatting changes that are not directly related to the changes required for this PR. Thanks!

Hey @jgrandja sure, that was in fact my question just above:
https://github.com/spring-projects-experimental/spring-authorization-server/pull/161#issuecomment-729284018
Sounds good, I'll fix that in the next few days and resolve all the conflicts that arise too, thanks or the heads up!

@rozagerardo Thanks for reverting the formatting changes.
I took a look at OAuth2TokenIntrospectionEndpointFilter and it doesn't follow the general pattern within Spring Security's Filter and AuthenticationManager / AuthenticationProvider architecture.
As a next step, I would encourage you to review the reference documentation to gain a deeper understanding:

Servlet Security: The Big Picture
Authentication

After you review that, please review the Token Revocation implementation in detail as it will follow the general pattern as Token Introspection.
This PR contains OAuth2TokenIntrospectionEndpointFilter but is missing OAuth2TokenIntrospectionAuthenticationToken and OAuth2TokenIntrospectionAuthenticationProvider.
Let me know if you have any questions.

Hey @jgrandja sorry for the delay here, the last couple of weeks have been quite busy for me.
Also, thanks for the heads up with the last comment, naturally I had read these sections before on a couple of occasions, but it's certainly different from a "framework developer" perspective :) and yes, I now understand the approach we should follow.
All right, I now added the missing classes and adapted the code I had been working on. I have also added a couple of comments to the PR.
However, I see an error in the CI build (a 401 retrieving a dependency), but it's definitely not related to my changes:

What went wrong:
Could not determine the dependencies of task ':spring-security-oauth2-authorization-server-docs-manual:unzipDocumentationResources'.

Could not resolve all dependencies for configuration ':spring-security-oauth2-authorization-server-docs-manual:detachedConfiguration2'.
Could not resolve com.fasterxml.jackson:jackson-bom:2.+.
Required by:
project :spring-security-oauth2-authorization-server-docs-manual

The build is running ok locally, let me know if I can help with anything to fix this CI issue. I think it might be a temporary issue, but I can't trigger the CI plan manually.
Looking forward to the next comments Joe!

Just a quick note about the last comment I made: https://github.com/spring-projects-experimental/spring-authorization-server/pull/161#issuecomment-737469164
The issue with the ci build seems to be solved, so this should be ready to be reviewed @jgrandja 👍

I now addressed all the comments, or commented back to discuss a few of them @jgrandja .
I tried to create a commit for each comment, to analyze the change easier. I'll squash them before merging.
Looking forward to your next comments.
Cheers, and hope you had a great end of year!

Happy New Year @rozagerardo !
Just a heads up that I have a couple of higher priority items that are targeted for the 0.1.0 release at end of month so I'll come back to review this in a couple of weeks.

Happy New Year @rozagerardo !
Just a heads up that I have a couple of higher priority items that are targeted for the 0.1.0 release at end of month so I'll come back to review this in a couple of weeks.

no problem @jgrandja, take your time and let me know if I can help with anything 👍

no problem @jgrandja, take your time and let me know if I can help with anything 👍

Hey @jgrandja just a quick update here, I now updated my code with the latest changes we have in master, this is ready to be reviewed again, and I'll keep an eye to keep the branch updated.
Also, a quick reminder for whenever you get back to this task, these discussions are still open:
https://github.com/spring-projects-experimental/spring-authorization-server/pull/161#discussion_r538767537
https://github.com/spring-projects-experimental/spring-authorization-server/pull/161#discussion_r538771618
https://github.com/spring-projects-experimental/spring-authorization-server/pull/161#discussion_r538776479

Hey @jgrandja just a quick update here, I now updated my code with the latest changes we have in master, this is ready to be reviewed again, and I'll keep an eye to keep the branch updated.
Also, a quick reminder for whenever you get back to this task, these discussions are still open:
https://github.com/spring-projects-experimental/spring-authorization-server/pull/161#discussion_r538767537
https://github.com/spring-projects-experimental/spring-authorization-server/pull/161#discussion_r538771618
https://github.com/spring-projects-experimental/spring-authorization-server/pull/161#discussion_r538776479

Thanks for the reminder @rozagerardo.
This PR is at the top of my priority list as soon as I release 0.1.0 on Feb 11.

@rozagerardo I finally circled back to this PR and have replied to the 3 outstanding comments.

Cool, thanks for the clarifications @jgrandja, all the comments make sense 👍
I now updated the branch with the latest changes in master and addressed the comments. This is ready for a new review, looking forward to your comments :)

Thanks for the updates @rozagerardo !
Can you please squash all commits. I'm going to do a full review from fresh.
I realize this will likely remove references to the existing comments but I'm fine with that.
Thanks.

Sure @jgrandja the PR now contains only one commit, and I think you can see the comments in the files.
Let me know that's ok, or if I should change anything else :)

Quick ping @jgrandja just to make sure you didn't miss my last comment:
https://github.com/spring-projects-experimental/spring-authorization-server/pull/161#issuecomment-786202371
Although I know you probably are just busy with something else 👍

@rozagerardo Apologies for the delay. I'm quite backlogged right now and trying to catch up with Spring Security issues and Spring Security OAuth (legacy) issues/PR's. I'm getting close to catching up and I'm planning on circling back to this PR this week. Then I will focus on getting it merged before end of month.

Cool, this is now ready for a new round @jgrandja .
Regarding the comments you made, I now addressed them all, but please have a look at this discussion before marking it as resolved:
https://github.com/spring-projects-experimental/spring-authorization-server/pull/161#discussion_r592711912
(I also made a small comment on some of the other points, but nothing important.)
Also, let me know if you want me to squash the commits again before reviewing them.
Looking forward to the next comments Joe 👍

@rozagerardo Thanks for all your work ! This is now merged to master.
FYI, I applied some updates with a follow-up polish commit. Please review and let me know if you have any questions.


Greetings responses could be more accurate.

A simple 'hi jarvis' was given a response 'everything wrapped up..would there be anything else'..
A more appropriate response from the greetings list could have been a 'hello sir' response or 'what can I do for you'..
I would certainly want to help on this regards.
We can certainly work on the responses to be more appropriate.

This is my first open source project. .Please guide me on this..I have gone through the readme file and some of the src and templates files as well..to know about jarvis. .

Here are the current responses: https://github.com/swapagarwal/JARVIS-on-Messenger/blob/master/modules/src/hello.py#L8-L14
Feel free to modify them. 😄


vale: 2.2.2 -> 2.3.0

Motivation for this change
https://github.com/errata-ai/vale/releases/tag/v2.3.0
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[X] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 94914 1

1 package built:
- vale


({}).toString.call(null) returns [object Window] for ES6 only builds

🐞 Bug report
Command (mark with an x)

[ ] new
[x] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] xi18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?
Unsure.
Description
On a project with a browserslist that only ends up targeting ES6 browsers, the result of ({}).toString.call(null) is "[object Window]", not "[object Null]" as expected.
I came across this bug as our project only targets ES6 and we recently upgraded to Bootstrap 4.4 which uses this method for checking the type of parameters. In https://github.com/twbs/bootstrap/pull/29251 an new option was added which has a default value of null, which returns a type of window in their type checker which causes an error with this CLI configuration.
🔬 Minimal Reproduction

ng new toStringRepo
ng serve
Open console of served app
Execute ({}).toString.call(null) and observe that it returns "[object Null]"
Stop serving
Change content of browserslist to last 2 Chrome versions
ng serve
Open console of served app
Execute ({}).toString.call(null) and observe that it returns "[object Window]"

🔥 Exception or Error
None
🌍 Your Environment
$ ng version

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/

Angular CLI: 8.3.21
Node: 10.15.3
OS: win32 x64
Angular: 8.2.14
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.803.21
@angular-devkit/build-angular     0.803.21
@angular-devkit/build-optimizer   0.803.21
@angular-devkit/build-webpack     0.803.21
@angular-devkit/core              8.3.21
@angular-devkit/schematics        8.3.21
@angular/cli                      8.3.21
@ngtools/webpack                  8.3.21
@schematics/angular               8.3.21
@schematics/update                0.803.21
rxjs                              6.4.0
typescript                        3.5.3
webpack                           4.39.2

Anything else relevant?
Upgrading the test project to Angular 9 with ng update @angular/core @angular/cli --next resolves the issue.

This seems to be cause by zone.js version 0.9.x,  Angular 9 uses zone.js 0.10.x where the issue was solved.
Please update to zone.js version 0.10.2.


Multiple exports for a model

Linz's default model export functionality is pretty good, but there are times when you just want to do something different.
This PR provides the ability to either completely overwrite the default export capability, or supplement it with another export option for your users.
Todo

[x] Update Linz to accept either an object or an array
[x] Update the model index to show a drop-down list if there are multiple exports
[x] Ensure that custom export routines can't use action with a value of export (this has been reserved for Linz)
[ ] Update the tests to ensure we have test coverage for this

Usage
To use this functionality, add an export property to your model's grid property:
    grid: {
        export: [
            {
                label: 'Custom export',
                action: 'url/endpoint'
            }
        ]
    }

To use a custom export, along with Linz's default export:
    grid: {
        export: [
            {
                label: 'Export',
                exclusions: 'fields,to,exclude'
            },
            {
                label: 'Custom export',
                action: 'url/endpoint'
            }
        ]
    }

Providing an export definition with an action value of export will error, for example:
    grid: {
        export: [
            {
                label: 'Export',
                action: 'export'
            }
        ]
    }

This PR has been superseded by #78.


Raw Event Data Preview not displaying correctly for LF-terminated lines

A series of line-feed separated lines of source data display as a single long line within Data Preview although View Source and stepping show the lines correctly formatted.

Can you provide a few lines of some example raw data pls

Raised in error.  Problem is actually because data is incorrectly parsed as XML.  Previously raised as #2867.


Can I add Chinese here? a new language!

China has a huge mobile game market,because of the unity event , more and more people need to understand this elegant engine, This may attract more game developers.

Hi @Arc-huangjingtong. Thank you for your interest in adding a Chinese translation.
Adding a new language requires a significant amount of work. It's not just about translating the existing documentation; it also involves maintaining it. Every time we update the English documentation, the changes need to be reflected in the translated versions as well. This means continuous updates and checks to ensure all versions are synchronized.
Maintaining the documentation in multiple languages is a complex and ongoing effort. It requires a dedicated team of translators and maintainers who can keep the non-English docs up-to-date with the latest changes.
Are you aware of more Chinese-speaking developers who could help with maintaining the docs? A community effort would make this much more feasible. I know there are many!🙂
Let's keep this conversation open, as I need to make some adjustments to our docs generation script to better support multiple languages. Also, we can track people willing to help with the translation.
Also, could you clarify your intention? Are you looking to translate individual pages or just the navigation menus to start with?
Thank you again for your enthusiasm and support! 😊

Thank you! I want to know the inclusiveness of the stride team. I will need to take time to prepare.
the clarify is : i want translate all the page in Learn manual

I can know that the stride team is willing to accept Chinese, so I can prepare with confidence.

Thank you! I want to know the inclusiveness of the stride team. I will need to take time to prepare.
the clarify is : i want translate all the page in Learn manual

everything, everyone is included, its just about resources
the japanese docs are existing but it is halted as nobody is maintaining it

Yes, the Stride team is open to any language 🙂. However, we are concerned about translated docs becoming outdated if they are abandoned. Ideally, there should be at least 2-3 community members supporting each language to ensure it stays updated with future versions. If there are no language maintainers, we might just remove the language.

thank you , I understand that this is a difficult choice, and I will consider this matter carefully.

You are welcome.
If anyone else would like to help with the Chinese translation, please let us know.


Error while logining: auth is failed

Error while logining: auth is failed

Most likely you specified the wrong referral link


[Storage] Queue Typing Release APIView Feedback

As titles states 😄

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-storage-queue

/azp run python - storage - ci

/azp run python - storage - ci

Verified the following:

All content inputs are object
All content outputs are Any
No Mypy errors


Group RGB support

Hi Peter - I see you've started implementing this, but there's a chunk commented out.
If you can quickly help me understand:

What the complexity is with RGB specifically wrt groups
The way you'd planned on tackling it

...I'll see if I can get it finished off this weekend, and can send you a PR?

Hi,
It is not particularly practical to tackle this problem in the way I have started it, as it would result in multiple invocations of the end points on the bridge, which would not be good from a user perspective, as they would see multiple lights potentially turn on/change state in a staggered way from a single call from the API.
What hue do offer around this, that solves this issue is the creation of scenes, which you can invoke with a group filter. The type of activity that this code was looking to handle would be well suited by the creation of a scene, that of course presets the light states, which is always valid for the lights, and then use the group filter to trigger those states on the lights you actually want to respond.
It is my intention to provide documentation and examples around this, and remove the commented out group code.

I think that this is no longer relevant in today's hue implementation. The scenes system makes this for groups less relevant and the desire can be achieved using that system (although not in a single call).


SSU-9: Create modal component

JIRA TASK: SSU-9
Behaviour

https://user-images.githubusercontent.com/8185973/186724690-1e8e4464-a945-4ae3-88ab-68ccf6b8b058.mov

The video actually got worse, but it's kinda slow, I'll try to see what's going on 🤔


[IS-5.10.0] [UX] Pop-up messages are not displayed during user creation in management console

Describe the issue:
Pop-up messages are not shown in UI for following scenarios:

User creation with weak password - No error message displayed in UI as a popup. There are errors logged in carbon log.
Successful user creation - No info is shown in UI even though the user is created successfully.

How to reproduce:

Enable the password complexity
Create a user with weak password (with correct length and w/o special characters)
Create user with strong password

Expected behavior:
Display proper INFO / ERROR popup messages.
Environment information

Product Version:  IS 5.10.0
WUM:<PHONE_NUMBER>692
OS: Linux
Database: Oracle 11g

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Fixes crash described in issue 7945 (Duplicated [self drawView] in iphone gl_view)

This patch fixes https://github.com/godotengine/godot/issues/7945.
I have removed both [self drawView] calls in layoutSubviews method, because I was able to reproduce the crash if I eliminated only the second (duplicated) call.

Thanks!

I guess this PR should likely not be cherry-picked for 3.1, but its follow up #33154 should likely be.

I am experiencing this crash with 3.2 beta 5 on iOS 13.1.1


Follow-up from "Resolve "convert stellarator.f90 to Python""

In GitLab by @timothy-nunn on Apr 26, 2023, 13:55
The following discussion from !847 should be addressed:

[ ] @jonmaddock started a discussion:  (+3 comments)

I don' think this is a good idea: the model running differently because it's aware of which constraints are being applied to it. I believe the returned values will be zero in the case where the constraint isn't active, which I find confusing, and this isn't done anywhere else to my knowledge. If it's purely performance reasoning, then I think this should probably be removed.

Has this been dealt with already @timothy-nunn ?

@jonmaddock no. https://github.com/ukaea/PROCESS/blob/main/process/stellarator.py#L161

I will say this issue was annoying when we first encountered it. power_at_ignition_point had some side effects that changed the results for a Stellarator that did not enforce icc 91, hence why myself and JL opted to leave this logic alone.


Improve support for short-lived processes

Short-lived processes aren't well supported, this also affects processes that might run for several seconds, but that exit before collecting the metadata for the processes.
Besides this bug, we have another bug that results in samples being sent without mapping information, resulting in broken stacks

Addressing the former should fix most of the instances we see as it would minimise the race condition window.

We've made a lot of progress here -- leaving closing it to @kakkoyun and @brancz


Tag a release?

Hello,
Could you please tag a release here so we could use it to have choose in Homebrew core?
Thanks!

Tagged 0.1 and thank you for making a recipe (if that is the write term in homebrew)!

Thanks a lot! That’s called a formula, actually :wink:


Short solution needed: "ufw reset to default" (ufw)

Please help us write most modern and shortest code solution for this issue:
ufw reset to default (technology: ufw)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

Reset ufw to default


Performance concurrency issue

https://github.com/eo-cqrs/xfake/blob/ecd9054d28728e9b8653e61b70c4b81580ca3d56/src/main/java/io/github/eocqrs/xfake/InFile.java#LL99C5-L99C5
same as #22

@l3r8yJ thank you for reporting this. I'll assign someone to take care of it soon.

@h1alexbel this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-06-05T06:12:24.304410.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@h1alexbel thank you for resolving this ticket. I've just added it to your active invoice. You can always check all your invoices and more on the Contributor Dashboard.


https://ts.gluon.ai/ website link broken

Description
https://ts.gluon.ai/ returns 'page not found'

FWIW, current link response is:
<Error>
AccessDenied
<Message>Access Denied</Message>
<RequestId>8J284NJB4MJGF0MZ</RequestId>
<HostId>tULYqBu6ilnV4HBLHEGA5mGhrqquYMdFnjlVPmeyvMJmrWAKmZlDxgiaqQ0Wu2kT9U+QgcHqI2A=</HostId>
</Error>

The issue should be fixed; pages should be accessible once again, as soon as the CloudFront cache expires.

I'm getting a different behavior- while there is no error, clicking the ts.gluon.ai link on the right side of the https://github.com/awslabs/gluon-ts page invokes a download, it does not display a new page.

Web link confirmed to be working now, thanks.


wayland-protocols: 1.31 -> 1.32

Release announcement:
https://lists.freedesktop.org/archives/wayland-devel/2023-July/042836.html

This release includes 3 new staging protocols:

ext-foreign-toplevel-list - get information about toplevels,
security-context-v1 - allow race free identification of sandboxed
clients,
cursor-shape-v1 - set cursor sprite using a shape enum instead of
surface.

The xdg-shell protocol also now has a 'suspended' toplevel state,
usually sent when a toplevel is "out of sight" to the user, meant
to communicate to a toplevel can for example take power saving measures.
This release also include the usual set of straightening of question
marks and clarifications of ambiguities.

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

@ofborg test tinywl

Bisect says 7247d3fe7c4f2e6eb32967e0a24e664afdcbed5d wayland-protocols: 1.31 -> 1.32 broke foot build on staging:
$ nix build --no-link -f. foot -L
...
foot> ../wayland.c: In function 'xdg_toplevel_configure':
foot> ../wayland.c:655:9: error: enumeration value 'XDG_TOPLEVEL_STATE_SUSPENDED' not handled in switch [-Werror=switch]
foot>   655 |         switch (*state) {
foot>       |         ^~~~~~
foot> cc1: all warnings being treated as errors

Possibly fixed upstream by https://codeberg.org/dnkl/foot/commit/72bc0acfbd4b002ebf26d65368bb65601452353e

@trofi thanks a lot for noticing and reporting this regression! :)
And sorry for my delayed response...
I just tested this by cherry-picking this commit/PR on top of nixos-unstable and could quickly reproduce this with extremely few rebuilds. It worked again after cherry-picking https://github.com/NixOS/nixpkgs/pull/243976 (already merged) as that new release contains your linked commit so it should be fine again :)


How to configure the time interval of airnode's detection request?

About every minute, airnode will pull block information to check whether there is a request, can I change this time for my airnode? For example, check once every five minutes, which can save cloud functions costs.
[2023-08-02 07:16:00.866] INFO Created initial coordinator state                                                Coordinator-ID:b1ae12376432b71a
[2023-08-02 07:16:00.868] INFO Forking to initialize providers                                                  Coordinator-ID:b1ae12376432b71a
[2023-08-02 07:16:04.284] INFO Pending requests: 0 API call(s), 0 withdrawal(s)                                 Coordinator-ID:b1ae12376432b71a, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:16:04.286] INFO Authorizing all requests because all authorizer arrays are empty                 Coordinator-ID:b1ae12376432b71a, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:16:04.294] INFO Pending requests: 0 API call(s), 0 withdrawal(s)                                 Coordinator-ID:b1ae12376432b71a, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:16:04.294] INFO Authorizing all requests because all authorizer arrays are empty                 Coordinator-ID:b1ae12376432b71a, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:16:05.614] INFO Pending requests: 0 API call(s), 0 withdrawal(s)                                 Coordinator-ID:b1ae12376432b71a, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:16:05.614] INFO Authorizing all requests because all authorizer arrays are empty                 Coordinator-ID:b1ae12376432b71a, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:16:05.962] INFO Pending requests: 0 API call(s), 0 withdrawal(s)                                 Coordinator-ID:b1ae12376432b71a, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:16:05.963] INFO Authorizing all requests because all authorizer arrays are empty                 Coordinator-ID:b1ae12376432b71a, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:16:09.971] INFO Pending requests: 0 API call(s), 0 withdrawal(s)                                 Coordinator-ID:b1ae12376432b71a, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:16:09.971] INFO Authorizing all requests because all authorizer arrays are empty                 Coordinator-ID:b1ae12376432b71a, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:16:09.978] INFO Forking to initialize providers complete                                         Coordinator-ID:b1ae12376432b71a, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:16:09.978] INFO Initialized EVM provider:darwiniaHostedPangolin                                  Coordinator-ID:b1ae12376432b71a, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:16:09.978] INFO Initialized EVM provider:darwiniaHostedCrab                                      Coordinator-ID:b1ae12376432b71a, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:16:09.978] INFO Initialized EVM provider:dwellirCrab                                             Coordinator-ID:b1ae12376432b71a, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:16:09.978] INFO Initialized EVM provider:darwiniaHostedDarwinia                                  Coordinator-ID:b1ae12376432b71a, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:16:09.978] INFO Initialized EVM provider:dwellirDarwinia                                         Coordinator-ID:b1ae12376432b71a, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:16:09.978] INFO No actionable requests detected. Returning                                       Coordinator-ID:b1ae12376432b71a, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:16:09.979] INFO Coordinator completed at 2023-08-02 07:16:09. Total time: 9114ms                 Coordinator-ID:b1ae12376432b71a, Chain-ID:46, Provider:dwellirDarwinia
crond[16]: USER airnode-client pid 108 cmd node /app/src/cli/invoke.js&
[2023-08-02 07:17:00.873] INFO Created initial coordinator state                                                Coordinator-ID:b61d7c70484febe7
[2023-08-02 07:17:00.875] INFO Forking to initialize providers                                                  Coordinator-ID:b61d7c70484febe7
[2023-08-02 07:17:04.137] INFO Pending requests: 0 API call(s), 0 withdrawal(s)                                 Coordinator-ID:b61d7c70484febe7, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:17:04.140] INFO Authorizing all requests because all authorizer arrays are empty                 Coordinator-ID:b61d7c70484febe7, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:17:04.250] INFO Pending requests: 0 API call(s), 0 withdrawal(s)                                 Coordinator-ID:b61d7c70484febe7, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:17:04.250] INFO Authorizing all requests because all authorizer arrays are empty                 Coordinator-ID:b61d7c70484febe7, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:17:04.258] INFO Pending requests: 0 API call(s), 0 withdrawal(s)                                 Coordinator-ID:b61d7c70484febe7, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:17:04.258] INFO Authorizing all requests because all authorizer arrays are empty                 Coordinator-ID:b61d7c70484febe7, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:17:04.667] INFO Pending requests: 0 API call(s), 0 withdrawal(s)                                 Coordinator-ID:b61d7c70484febe7, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:17:04.668] INFO Authorizing all requests because all authorizer arrays are empty                 Coordinator-ID:b61d7c70484febe7, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:17:04.678] INFO Pending requests: 0 API call(s), 0 withdrawal(s)                                 Coordinator-ID:b61d7c70484febe7, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:17:04.678] INFO Authorizing all requests because all authorizer arrays are empty                 Coordinator-ID:b61d7c70484febe7, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:17:04.680] INFO Forking to initialize providers complete                                         Coordinator-ID:b61d7c70484febe7, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:17:04.680] INFO Initialized EVM provider:darwiniaHostedPangolin                                  Coordinator-ID:b61d7c70484febe7, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:17:04.680] INFO Initialized EVM provider:darwiniaHostedCrab                                      Coordinator-ID:b61d7c70484febe7, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:17:04.680] INFO Initialized EVM provider:dwellirCrab                                             Coordinator-ID:b61d7c70484febe7, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:17:04.680] INFO Initialized EVM provider:darwiniaHostedDarwinia                                  Coordinator-ID:b61d7c70484febe7, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:17:04.680] INFO Initialized EVM provider:dwellirDarwinia                                         Coordinator-ID:b61d7c70484febe7, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:17:04.680] INFO No actionable requests detected. Returning                                       Coordinator-ID:b61d7c70484febe7, Chain-ID:46, Provider:dwellirDarwinia
[2023-08-02 07:17:04.680] INFO Coordinator completed at 2023-08-02 07:17:04. Total time: 3808ms                 Coordinator-ID:b61d7c70484febe7, Chain-ID:46, Provider:dwellirDarwinia

That is not currently exposed as a parameter. As a workaround, you can check out the commit tagged with the Airnode version you're using, change this (AWS) or this (GCP) value, build the docker images locally and use the deployer image you've built instead of the one we've pushed to dockerhub. One thing to note here is that you will now need to configure your Airnode to look for requests from the last 5 minutes, which means you should increase this value accordingly. This means that your Airnode will make eth_getLogs calls with a wider range, which your blockchain provider may not support.
Users typically want to increase the frequency (for example, have it run every 15 seconds) rather than decreasing it. We need to change the architecture significantly to support that, which is planned for the release after the next one (so it will either be called 0.14 or 1.0). That will also support decreasing the frequency. However, we're planning to implement that by keeping a cloud function always running, which means this will not reduce the compute time of your cloud function (though it would reduce your blockchain provider load).

Tracked by https://github.com/api3dao/airnode/issues/1478


chore(package.json): remove engines field

It warns on iojs and 0.12

@stevemao Thanks!
We also should fix documentation where we describe which version of node we supported.
I prefer explicitly add stable version of node which we supported, instead remove them.(IMHO)
/cc @karma-runner/contributors

I agree with @maksimr on this. However I find it confusing to mix the node.js and io.js engine versions in such case (~0.8 || ~0.10 || ~0.12 || ~1). So @stevemao's solution could actually be the best.

As we don't support 0.6 or lower we should at least do something like >= 0.8.

Can we write something like
"engines": {
  "node":  "~0.8 || ~0.10 || ~0.12",
  "iojs": "~1"
}

or
"engines": {
  "node":  ">=0.8 <=0.12",
  "iojs": "~1"
}

This could be worth a try.

Thanks, before I sent this I looked at many other node projects, many of them removed this field. Some using >= 0.10 similar to what @Dignifiedquire pointed out. In fact not many support 0.8 any more. I personal like @maksimr 's solution :+1:


Deal with the case when an admin is leaving the lobby

closed https://github.com/sopra-fs24-group-12/PeekSeek-server/commit/7cf8e393c8ac6d0b60b0bf0b8d70c59f2ab1e954


fix: prevent qthrottled and qdebounced from holding strong references with bound methods

I hit a cleanup issue and eventually traced it back to qdebounced/qthrottled holding a strong reference when used on a bound method.  This ensures that those two decorators don't hold strong refs

review from @Czaki would be appreciated


Alpha and Beta states for PDF417 and Aztec respectively

Hey everyone,
I wanted to get an idea of the stability/maturity of the PDF417 and Aztec encoding features at this time as I noticed they are marked as alpha and beta respectively.
I tested out the PDF417 generating functionality and it seemed to work as expected for the most part...
Thanks for the clarification!

Basically Aztec and PDF417 are labeled alpha and beta because that's how they're labeled in ZXing, from which ZXingObjC is ported. PDF417 has gotten some improvements recently in ZXing and is now labeled "beta" by them. I'm hoping to port over some of their more recent changes (including to PDF417) so that ZXingObjC will have them too.


Replace deprecated 'compile' gradle configuration with 'implementation'

Description
See http://d.android.com/r/tools/update-dependency-configurations.html for more details
Compatibility
This is a build-specific change for Android. No updates to implementation.
Checklist

[x] I have tested this on a device/simulator for each compatible OS
[ ] I added the documentation in README.md.
[ ] I mentionned this change in CHANGELOG.md.

Done in #520, thank you!