[xDai] - Create "generic network configuration"

The aim of this task is to create a configuration setup that will ease the addition of networks to the Safe.
an initial sketch:
const xDai = {
  dev: {},
  staging: {},
  production: {
    NETWORK_LABEL: 'xDai STAKE',
    NETWORK_COLOR: '#48A8A6',
    NETWORK_ID: 100,
    // mocks the structure of `Token` in `src/logic/tokens/store/model/token.ts`
    NATIVE_COIN: {
      // address mocks the ETH_ADDRESS in `src/logic/tokens/utils/tokenHelpers.ts`
      address: '0x000',
      name: 'xDai',
      symbol: 'xDai',
      decimals: 18,
      logoUri: '',
    },
    // something around this to display or not some critical sections in the app, depending on the network support
    // I listed the ones that may conflict with the network.
    // If non is present, all the sections are available.
    DISABLE: {
      SAFE_APPS: true,
      COLLECTIBLES: true,
      CONTRACT_INTERACTION: true,
    },
    TX_SERVICE_HOST: 'https://safe-transaction.xdai.gnosis.io/api/v1/',
    // Shall we keep a reference to the relay?
    RELAY_API_URL: null,
    // won't be used in xDai, for the first iteration
    SAFE_APPS_URL: null,
    // mainnet+rinkeby: ethgasstation,
    // xDai: Ask Richard about the oracle for the gasPrice
    GAS_PRICE_ORACLE_URL: '',
    // mainnet+rinkeby: infura,
    //    for infura there's a REST API Token required stored in: `REACT_APP_INFURA_TOKEN`
    // xDai: `rpc.xdaichain.com` among others
    //    see: https://www.xdaichain.com/for-developers/developer-resources#json-rpc-endpoints
    RPC_SERVICE_URL: '',
    // mainnet+rinkeby uses etherscan,
    // xDai uses:
    //  - `blockscout.com/poa/xdai/api`
    //  - `blockscout.com/poa/xdai/api/eth-rpc`
    //        This API is provided to support some rpc methods
    //        in the exact format specified for ethereum nodes
    NETWORK_EXPLORER_URL: '',
  },
}

An example of how the current configurations would look with the said "generic network configuration".
const mainnet = {
  dev: {
    [TX_SERVICE_HOST]: 'https://safe-transaction.mainnet.staging.gnosisdev.com/api/v1/',
    [RELAY_API_URL]: 'https://safe-relay.mainnet.staging.gnosisdev.com/api/v1/',
    [SAFE_APPS_URL]: 'https://safe-apps.dev.gnosisdev.com/',
  },
  staging: {
    [TX_SERVICE_HOST]: 'https://safe-transaction.mainnet.staging.gnosisdev.com/api/v1/',
    [RELAY_API_URL]: 'https://safe-relay.mainnet.staging.gnosisdev.com/api/v1/',
    [SAFE_APPS_URL]: 'https://safe-apps.staging.gnosisdev.com',
  },
  production: {
    [TX_SERVICE_HOST]: 'https://safe-transaction.mainnet.gnosis.io/api/v1/',
    [RELAY_API_URL]: 'https://safe-relay.gnosis.io/api/v1/',
    [SAFE_APPS_URL]: 'https://apps.gnosis-safe.io/',
  },
}

Finally, the env variables (the ones listed in the .env.example file), need to be revisited along with this change too.
A commented list of the env vars:
/*
 * .env file
 */
const envVariables = {
  // mainnet | rinkeby | xdai | ewc | volta
  // defaults to? rinkeby
  REACT_APP_NETWORK: '',

  // should we add analytics_ids for every network?
  REACT_APP_GOOGLE_ANALYTICS_ID_RINKEBY: '',
  REACT_APP_GOOGLE_ANALYTICS_ID_MAINNET: '',

  // we should add the required tokens for every RPC that requires one.
  REACT_APP_INFURA_TOKEN: '',

  REACT_APP_IPFS_GATEWAY: '',
  PUBLIC_URL: '',
  REACT_APP_BLOCKNATIVE_KEY: '',
  REACT_APP_INTERCOM_ID: '',
  REACT_APP_PORTIS_ID: '',
  REACT_APP_SQUARELINK_ID: '',
  REACT_APP_FORTMATIC_KEY: '',

  // This will be deprecated in favor of gnosis tx-service, see https://github.com/gnosis/safe-react/issues/1408
  REACT_APP_OPENSEA_API_KEY: '',
  // OpenSea | gnosis?
  REACT_APP_COLLECTIBLES_SOURCE: '',

  // we should add required tokens ver every explorer that requires one.
  REACT_APP_ETHERSCAN_API_KEY: '',

  REACT_APP_LATEST_SAFE_VERSION: '',
  REACT_APP_APP_VERSION: '',

  // depends on REACT_APP_GNOSIS_APPS_URL_PROD and REACT_APP_GNOSIS_APPS_URL_STAGING. See .travis.yml
  // also is used in .github/workflows/release.yml
  REACT_APP_GNOSIS_APPS_URL: '',
}

Maybe adding one more level to the configs, makes a bit more sense (added environments and generics).
/*
 * xDai
 */
const xDai = {
  generics: {
    NETWORK_LABEL: 'xDai STAKE',
    NETWORK_COLOR: '#48A8A6',
    NETWORK_ID: 100,
    // mocks the structure of `Token` in `src/logic/tokens/store/model/token.ts`
    NATIVE_COIN: {
      // address mocks the ETH_ADDRESS in `src/logic/tokens/utils/tokenHelpers.ts`
      address: '0x000',
      name: 'xDai',
      symbol: 'xDai',
      decimals: 18,
      logoUri: '',
    },
    // something around this to display or not some critical sections in the app, depending on the network support
    // I listed the ones that may conflict with the network.
    // If non is present, all the sections are available.
    DISABLE: {
      SAFE_APPS: true,
      COLLECTIBLES: true,
      CONTRACT_INTERACTION: true,
    },
  },
  environments: {
    dev: {},
    staging: {},
    production: {
      TX_SERVICE_HOST: 'https://safe-transaction.xdai.gnosis.io/api/v1/',
      // Shall we keep a reference to the relay?
      RELAY_API_URL: null,
      // won't be used in xDai, for the first iteration
      SAFE_APPS_URL: null,
      // mainnet+rinkeby: ethgasstation,
      // xDai: Ask Richard about the oracle for the gasPrice
      GAS_PRICE_ORACLE_URL: '',
      // mainnet+rinkeby: infura,
      //      for infura there's a REST API Token required stored in: `REACT_APP_INFURA_TOKEN`
      // xDai: `rpc.xdaichain.com` among others
      //      see: https://www.xdaichain.com/for-developers/developer-resources#json-rpc-endpoints
      RPC_SERVICE_URL: '',
      // mainnet+rinkeby uses etherscan,
      // xDai uses:
      //  - `blockscout.com/poa/xdai/api`
      //  - `blockscout.com/poa/xdai/api/eth-rpc`
      //        This API is provided to support some rpc methods
      //        in the exact format specified for ethereum nodes
      NETWORK_EXPLORER_URL: '',
    },
  }
}


[YUNIKORN-274] app definition and example added

According to https://kubernetes.io/docs/concepts/overview/working-with-objects/names/. Object UID should be unique across the cluster. Maybe we can use that as the applicationID. That means the user only needs to specify a namespace-unique name for each app-CRD. Also, metadata has generateName field, so if the user doesn't specify any name, K8s will generate one with that as the prefix. What do you think about this?

We can track these discussions later. It is not a blocker for this PR now. Let's get this merged. Thanks @kingamarton


Replace highcharts with cdn

For security reasons, delete highcharts from codebase and add a cdn to relevant pages .


The package is slowing down application booting time

Hey there, I'm fighting with my Laravel app since a few days, as my app got way slower to boot (we are talking from 200ms to 3000ms to load a simple livewire page).
After diving in and disabling package discovery one by one, I found that this package was in cause.
Do you think there is a way to boost SVG loading performance, or is it simply because there are too much icons for my machine resources ?
I've been trying to make use of blade cache, but it does seems to be helping. Thanks for you help!

I totally not tried as I didn't see this, my bad!
Thanks for sharing, I'll give it a go ! :)


JavaScript Support - Addresses #42

🤔 What's changed?
Adds support for JavaScript
⚡ What's your motivation?
Fixes #42
After the review, will update the document, changelog and https://github.com/cucumber/vscode/blob/main/README.md

🏷 What kind of change is this?

:zap: New feature (non-breaking change which adds new behaviour)

♻ Anything particular you want feedback on?
The tree-sitter-javascript was not working well. Hence using tree-sitter-typescript with jsx support for JavaScript as well as TS grammar is super set of JavaScript. Kindly provide feedback.

📋 Checklist:

[x] I agree to respect and uphold the Cucumber Community Code of Conduct
[X] I've changed the behaviour of the code

[X] I have added/updated tests to cover my changes.

[X] My change requires a change to the documentation.

[X] I have updated the documentation accordingly.

[X] Users should know about my change

[X] I have added an entry to the "Unreleased" section of the CHANGELOG, linking to this pull request.

This text was originally generated from a template, then edited by hand. You can modify the template here.

Thanks for contributing this! I'll have more feedback when I've done a thorough review, but at first glance this looks great.

Thanks for contributing this! I'll have more feedback when I've done a thorough review, but at first glance this looks great.

Hi @aslakhellesoy following up to check on the feedback

Hi @rvramesh,
Thanks for your making your first contribution to Cucumber, and welcome to the Cucumber committers team! You can now push directly to this repo and all other repos under the cucumber organization! 🍾
In return for this generous offer we hope you will:

✅ Continue to use branches and pull requests. When someone on the core team approves a pull request (yours or someone else's), you're welcome to merge it yourself.
💚 Commit to setting a good example by following and upholding our code of conduct in your interactions with other collaborators and users.
💬 Join the community Slack channel to meet the rest of the team and make yourself at home.
ℹ Don't feel obliged to help, just do what you can if you have the time and the energy.
🙋 Ask if you need anything. We're looking for feedback about how to make the project more welcoming, so please tell us!

On behalf of the Cucumber core team, Aslak Hellesøy Creator of Cucumber

Thank you for accepting the PR and the kind words


IaC for OKE

The changes to make it work with OCI OKE

The comments are inline.
--
Sergey
From: Thomas S. Pangborn @.>
Date: Thursday, January 6, 2022 at 11:09 AM
To: sassoftware/viya4-deployment @.>
Cc: Sergey Shulgin @.>, Author @.>
Subject: [External] : Re: [sassoftware/viya4-deployment] IaC for OKE (PR #176)
@thpang requested changes on this pull request.
Changes and comment.s

In docker-entrypoint.shhttps://urldefense.com/v3/__https:/github.com/sassoftware/viya4-deployment/pull/176*discussion_r779660126__;Iw!!ACWV5N9M2RV99hQ!bc2zOaqQJrfu42mXVTW7ODDNGZztrU5R3VWR2CdYNK0hBOsqiJo8YsKRiK1ujyRHSBo$:

+echo "viya4-deployment:x:$(id -u):$(id -g):Viya4:/viya4-deployment:/bin/bash" >> /etc/passwd

+echo "viya4-deployment:x:$(id -G | cut -d' ' -f 1):" >> /etc/group
This cannot be changed. What is the need here to alter what's currently in place?
The change is mostly cosmetic as the proper format for those files in Linux OS is in the example below
@.*** viya4-deployment]$ uname -a
Linux fedora 5.15.10-100.fc34.x86_64 #1 SMP Fri Dec 17 14:51:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
@.*** viya4-deployment]$ grep sshulgin /etc/passwd
sshulgin:x:1000:1000:Serg:/home/sshulgin:/bin/bash
@.*** viya4-deployment]$ grep sshulgin /etc/group
wheel:x:10:sshulgin
sshulgin:x:1000:

In docs/user/DockerUsage.mdhttps://urldefense.com/v3/__https:/github.com/sassoftware/viya4-deployment/pull/176*discussion_r779660455__;Iw!!ACWV5N9M2RV99hQ!bc2zOaqQJrfu42mXVTW7ODDNGZztrU5R3VWR2CdYNK0hBOsqiJo8YsKRiK1uFqS19ts$:

+#or

+sudo docker build -t viya4-deployment .
If you've setup docker correctly you do not need sudo. This needs to be removed.
The only alternative to run sudo docker on Fedora 34, I found, is to use podman which did not work well for me.
So, I am telling from my own experience but if you point me to specific way to make non-root docker work on Fedora as generic Linux OS I will include it in some reference doc.

In docs/user/DockerUsage.mdhttps://urldefense.com/v3/__https:/github.com/sassoftware/viya4-deployment/pull/176*discussion_r779660787__;Iw!!ACWV5N9M2RV99hQ!bc2zOaqQJrfu42mXVTW7ODDNGZztrU5R3VWR2CdYNK0hBOsqiJo8YsKRiK1uokLXQts$:

@@ -82,7 +84,7 @@ Any number of tasks can be run at the same time. An action can run against a sin

 viya4-deployment --tags "baseline,viya,cluster-logging,cluster-monitoring,viya-monitoring,install"

-- I have a custom built cluster and want to baseline and deploy viya only

+- I have a custom built cluster and want to install baseline and deploy viya only

Not needed.
Not insisting.
________________________________

In docs/user/DockerUsage.md<https://urldefense.com/v3/__https:/github.com/sassoftware/viya4-deployment/pull/176*discussion_r779661557__;Iw!!ACWV5N9M2RV99hQ!bc2zOaqQJrfu42mXVTW7ODDNGZztrU5R3VWR2CdYNK0hBOsqiJo8YsKRiK1uRtAHWLw$>:

> +- I have a new cluster, deployed in OCI using https://github.com/oracle-quickstart/oke-sas-viya-public<https://urldefense.com/v3/__https:/github.com/oracle-quickstart/oke-sas-viya-public__;!!ACWV5N9M2RV99hQ!bc2zOaqQJrfu42mXVTW7ODDNGZztrU5R3VWR2CdYNK0hBOsqiJo8YsKRiK1ujhpCPQw$> project, and I want to install baseline and deploy viya only

+- I run as non-root user

+

+  ```bash

+  sudo docker run --rm -t \

+    --group-add root \

+    --user $(id -u):$(id -g)  \

+    --volume $HOME/repos:/data:Z  \

+    --volume $HOME/repos/viya4-deployment/ansible-vars.yaml:/config/config:Z \

+    --volume $HOME/repos/oke-sas-viya-public/terraform.tfstate:/config/tfstate:Z  \

+    --volume $HOME/.ssh/id_rsa:/config/jump_svr_private_key:z  \

+    --volume $HOME/repos/viya4-deployment/.oci:/viya4-deployment/.oci:Z \

+    viya4-deployment --tags "baseline,viya,install"

+  ```

+

Can you explain the :Z you have at the end of each of these lines. Thx
I did a lot of debugging of docker run and found the volumes specified on the command line were not accessible inside the container until I added :Z at the end. I found this solution on the internet, and it might be related to running sudo docker run.

—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/sassoftware/viya4-deployment/pull/176*pullrequestreview-845787135__;Iw!!ACWV5N9M2RV99hQ!bc2zOaqQJrfu42mXVTW7ODDNGZztrU5R3VWR2CdYNK0hBOsqiJo8YsKRiK1u6eJg7Lk$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AWNDOXKL4QPQ4SH4KAC3LIDUUW5CTANCNFSM5LMSRMRQ__;!!ACWV5N9M2RV99hQ!bc2zOaqQJrfu42mXVTW7ODDNGZztrU5R3VWR2CdYNK0hBOsqiJo8YsKRiK1uCwutC7M$>.
Triage notifications on the go with GitHub Mobile for iOS<https://urldefense.com/v3/__https:/apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675__;!!ACWV5N9M2RV99hQ!bc2zOaqQJrfu42mXVTW7ODDNGZztrU5R3VWR2CdYNK0hBOsqiJo8YsKRiK1uzK68HxY$> or Android<https://urldefense.com/v3/__https:/play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign*3Dnotification-email*26utm_medium*3Demail*26utm_source*3Dgithub__;JSUlJSU!!ACWV5N9M2RV99hQ!bc2zOaqQJrfu42mXVTW7ODDNGZztrU5R3VWR2CdYNK0hBOsqiJo8YsKRiK1uSVsQA0Y$>.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

Discussed this with @thpang, support for OKE is not on the roadmap at this time. Closing this.


Fix service CMD to return an error if device discovery failed

The service should not silently ignore the discovery error.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
5 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.04%) to 38.362%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cmd/sriov-network-config-daemon/service.go
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

controllers/generic_network_controller.go
5
74.53%

Totals

Change from base Build<PHONE_NUMBER>:
-0.04%

Covered Lines:
4801

Relevant Lines:
12515

💛  - Coveralls


Implement Durations validators

https://github.com/envoyproxy/protoc-gen-validate#durations

Implemented


Add -d dis debug output option

See commits for more details.
Checklist

[ ] Language changes are updated in man/adoc/bpftrace.adoc
[ ] User-visible and non-trivial changes updated in CHANGELOG.md
[ ] The new behaviour is covered by tests

This is the backport: https://pastes.dxuuu.xyz/whuenq

Updated man page

Yeah, you're right. libbpf takes care to not hold onto the elf file past call to bpf_object__open_mem(). So it's not a UAF.
That being said, the change is still needed for the second commit. Lemme reword the commit msg

Now we don't need to backport the first commit, right?

Now we don't need to backport the first commit, right?

Right.

That being said, the change is still needed for the second commit. Lemme reword the commit msg

Could we enable this debug output without always making a copy of the ELF file? e.g. do it as part of emit() or a new emit_and_disas() function.
The debug option will be rarely used so it'd seem nicer to add overhead (CPU + memory) to this new code path rather than to the common code path.

I think debug builds only is fine. Shelling out is, of course, ugly. Probably good to not get into habit of asking users to run that.


did i use wrong with the TextEditingController?

before i explain my issues, please check out its ok about the offical example.
https://api.flutter.dev/flutter/widgets/TextEditingController-class.html
This example doesn't seem to work.
just like this:

Steps to Reproduce

i just copy the code from the example, and run it.
I also have another problem. In my own code, I instantiate a _controller. When I assign a value to the controller property of TextField, the following problem occurs:

Open simulator;
Open keyboard;
Input values;
Click done;
The value in the TextField disappears;

I don't know why, but when I remove _controller, the problem disappears.
just a line code about the controller:
  TextEditingController _controller = TextEditingController();

Logs

[✓] Flutter (Channel stable, v1.7.8+hotfix.3, on Mac OS X 10.14.5 18F203, locale zh-Hans-CN)
• Flutter version 1.7.8+hotfix.3 at /Users/hejingguo/flutter
• Framework revision b712a172f9 (13 days ago), 2019-07-09 13:14:38 -0700
• Engine revision 54ad777fd2
• Dart version 2.4.0
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.0)
• Android SDK at /Users/hejingguo/Library/Android/sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-29, build-tools 29.0.0
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 10.2.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 10.2.1, Build version 10E1001
• CocoaPods version 1.7.3
[✓] iOS tools - develop for iOS devices
• ios-deploy 1.9.4
[✓] Android Studio (version 3.4)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 37.1.1
• Dart plugin version 183.6270
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
[✓] IntelliJ IDEA Ultimate Edition (version 2019.1.1)
• IntelliJ at /Applications/IntelliJ IDEA.app
• Flutter plugin version 36.1.4
• Dart plugin version 191.7830
[✓] VS Code (version 1.36.0)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.2.0
[✓] Connected device (1 available)
• iPhone 6s • 4AE27175-9674-443D-B05D-0B437F6A927C • ios • com.apple.CoreSimulator.SimRuntime.iOS-12-2 (simulator)
• No issues found!

why nobody respond to me... please...

is this a real problem? could anybody respond me a massege?

你有看输出日志么？

is this a real problem? could anybody respond me a massege?

建议用android studio 调试一下，看看日志，或者你贴出你的代码

Hi @dumplings
Are you still experiencing this issue?
Thank you

@dumplings
I can't reproduce it with flutter v1.16.1 and iOS simulator 13.3.
I hope it's fixed, closing.
Comment please if it's not so and I'll reopen the issue
Thank you


Add new JVM Middleware alerts on miq fresh start

This task is following the JMAN4-233.
It adds the following 3 new middleware alerts:

Middleware GC > 10 sec/minute
Middleware Heap Max > 90%
Middleware Non Heap Max > 90%

It is added in the seed process in order to have it right after MIQ setup.

@abonas could you please check it out?

@israel-hdez please review

+1 to @israel-hdez remark on sync. excellent catch!

@agrare

title still mentions profile

Done! Glad to here from reviewers @israel-hdez @blomquisg @agrare

@loicavenel fyi

@miq-bot add_label gaprindashvili/yes

@israel-hdez please re-review

@gmcculloug can you do a quick check on this one?  I don't know much about the miq_alerts configs.

@lfu Please review

This is good to merge after I get a thumbs up from @lfu

any updates on this one?

@lfu any review please?

As @israel-hdez says, It seems that when it is added a Hawkular Alert on MIQ it needs to be notified to Hawkular Alerts service first:
https://github.com/ManageIQ/manageiq-providers-hawkular/blob/master/app/models/manageiq/providers/hawkular/middleware_manager/alert_manager.rb#L10
Then to have this feature done, we need to add some more logic. One thing it would work, would be to create a initializer/seeder like the one here in the core but adding the sync logic.

As @israel-hdez says, It seems that when it is added a Hawkular Alert on MIQ it needs to be notified to Hawkular Alerts service first:
https://github.com/ManageIQ/manageiq-providers-hawkular/blob/master/app/models/manageiq/providers/hawkular/middleware_manager/alert_manager.rb#L10
Then to have this feature done, we need to add some more logic. One thing it would work, would be to create a initializer/seeder like the one here in the core but adding the sync logic.

shouldn't this be done only after a profile is created with specific servers to apply to (and when a provider exists)?
isn't this PR about an empty definition only that does not apply to anything?

@abonas you are right. This PR is only for the empty definition of those alerts.
I'll check what @israel-hdez says and make another PR/issue if there are problems.
Waiting for @lfu, then.

@abonas you are right. This PR is only for the empty definition of those alerts.
I'll check what you and @israel-hdez says and make another PR/issue if there are problems.
Waiting for @lfu, then.

great.
Making sure we are on the same page here:
If this is not usable 'as is' in this PR and needs more PRs, then we have to exclude it from gaprindashvili.

@miq-bot remove_label gaprindashvili/yes

@miq-bot add_label gaprindashvili/no

in order to have this properly functioning, this bug has to be resolved:
https://bugzilla.redhat.com/show_bug.cgi?id=1510421

@abonas it sounds like we're waiting on https://bugzilla.redhat.com/show_bug.cgi?id=1510421 based on your comment.  Is that right?

@blomquisg yes, we are waiting for that bug. Otherwise the feature won't be fully working.

Thanks @xeviknal

Sorry for the late comments. Just came back from vacation.
Other than the two comments, it looks good to me.

@miq-bot add_label wip

Thank you everybody for you time.
Closing it because related bugs dont have to be fixed.


colorization task not work well

Hi, bro, nice jobs! I am interested in it and I try I repeat the experiment. When I run these script:
MODEL_FLAGS="--attention_resolutions 32,16,8 --class_cond False --diffusion_steps 1000 --image_size 256 --learn_sigma True --noise_schedule linear --num_channels 256 --num_head_channels 64 --num_res_blocks 2 --resblock_updown True --use_fp16 True --use_scale_shift_norm True" python sample_x0_color.py  $MODEL_FLAGS --use_img_for_guidance --start_from_scratch --save_png_files
It doesn't work in some pictures. could you help me about it?
In the pic, the first example seems work, but the orders didn't. (The pictures come from imagenet/val/n03781244)

Thanks! Since colorization is not a trivial task, maybe you can try to modify the weight of loss and guidance scale to solve this problem.
https://github.com/Fayeben/GenerativeDiffusionPrior/blob/116b875db9b4b6c3bcc8adcfc7dbaedb607e1edb/scripts/sample_x0_color.py#L112
https://github.com/Fayeben/GenerativeDiffusionPrior/blob/116b875db9b4b6c3bcc8adcfc7dbaedb607e1edb/scripts/sample_x0_color.py#L252

ok. I will give it a try, thanks!

Since there are no more questions, I'll mark it closed. If you still have some questions, please feel free to ask. Thanks!


Add 1password 8's bundle identifier

In the exclusion list

In the exclusion list

Would you by any chance know how to build this app out native for Apple Silicon? Looks like the original dev hasn't updated this in a while.

Would you by any chance know how to build this app out native for Apple Silicon? Looks like the original dev hasn't updated this in a while.

No idea! sorry


feat(llm): OpenLLM

Signed-off-by: Aaron<EMAIL_ADDRESS>cc @parano
Description
🎉 OpenLLM 🤝 Llama_index
OpenLLM is an open-source platform designed to facilitate the deployment and operation of large language models (LLMs) in real-world applications. With OpenLLM, you can run inference on any open-source LLM, deploy them on the cloud or on-premises, and build powerful AI applications.
It includes supports for a wide range of open-source LLMs and model runtimes, including but not limited to Mistral, Llama2, StableLM, Falcon, Dolly, Flan-T5, ChatGLM, and StarCoder.
It also has support for token streaming, quantization, and continuous batching (via vLLM), which can significantly increase the total throughput of LLMs.
With this in mind, this integration to Llama_index brings in two new LLM: OpenLLM and OpenLLMAPI.
For running locally with OpenLLM, it will requires user to install openllm[vllm] on GPU and openllm if running on CPU.
from llama_index.llms.openllm import OpenLLM
llm = OpenLLM('HuggingFaceH4/zephyr-7b-alpha')

llm.complete('I love you')
await llm.acomplete('I love you')

for it in llm.stream_chat(
    [
        ChatMessage(
            role="system", content="You are acting as Ernest Hemmingway."
        ),
        ChatMessage(role="user", content="Hi there!"),
        ChatMessage(role="assistant", content="Yes?"),
        ChatMessage(role="user", content="What is the meaning of life?"),
    ]
):
    print(it.message.content, flush=True, end="")

async for llm.astream_complete("The meaning of life is"): print(it.delta, flush=True, end='')

With an OpenLLM server running elsewhere or on BentoCloud, users will need to install openllm-client and use OpenLLMAPI:
from llama_index.llms.openllm import OpenLLMAPI

llm = OpenLLM(address='remote.server:3000')

[!NOTE]
For OpenLLMAPI, if OPENLLM_ENDPOINT is set, then the following can be achieved:
llm = OpenLLMAPI()

All async and sync variation of chat and completeion message is supported for both OpenLLM and OpenLLMAPI.
Type of Change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Added new unit/integration tests
[x] Added new notebook (that tests end-to-end)
[x] I stared at the code and made sure it makes sense

Suggested Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added Google Colab support for the newly added notebooks.
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] I ran make format; make lint to appease the lint gods

Haizz, I do not like mixing async and sync. Stream_chat and stream_complete is partially working right now. I will take another look on this. Maybe it should be openllm responsibility to provide a sync generation.
for OpenLLM best for users to use acomplete, astream_complete, achat, astream_chat to fully get continuous batching.

@aarnphm awesome, thanks for adding this!
As you know, Open-Source LLMs require a many different input formats depending on the LLM
Is OpenLLM handling the prompt formating under the hood for each model?

We dont handle and leave the prompt format for the user. For local llm we will rely on apply_chat_templates for chat API.

stream_chat and stream_complete is now ready for review.

Looks like some typing issues around LLM -- I would fix it myself right now, but I can't seem to push to this PR

Looks like some typing issues around LLM -- I would fix it myself right now, but I can't seem to push to this PR

Oh let me fix the type

cc @logan-markewich

Cool! Looks good, thanks for the patience with the CI haha


[dns] add helper methods to append/parse DNS domain names

This commit adds DomainName type which provides a set of helper
methods to encode/decode DNS domain names. AppendName() method
encodes and appends a full name (e.g., "test.example.com") to a
message. Other helper methods enable appending labels (or groups of
labels) and/or constructing a compressed domain name (using pointer
labels). ParseName() method parses and skips over a full domain name
in a message. ReadLabel() method reads labels one by one and works
whether the encoded domain name is compressed or not. The new
methods are used in Dns::Client.
This commit also add a unit test test-dns covering the behavior of
the newly added helper methods.
Finally, this commit adds few helper methods in ResourceRecords to
get the size and check the type of a DNS record.

In the new push, added ReadName() which read a full domain name from a message (returning it as dot "." seperated sequence of labels).
To share the common parsing code, the new commit also adds a private sub-type LabelIterator definint some helper methods which are then used by ReadLabel(), ReadName() and ParseName(). Unit test also covers the ReadName()


Update README.md

Add note to README explaining YT Music premium is required

Hi Marvin. I will add a note to the How Do I as well. If you ever wanted to update that document in the discussions area I think you should have access as well.


Support for Grpc System Task

As Grpc is slowly gaining adaption as a rpc mechanism especially between internal micro service class, It would help provide OOB support for grpc as a WorkflowSystemTask similar to http

@ramaraochavali This is something we have in our radar, but not scheduled for any of the immediate releases.

@v1r3n  good to know that. Do you have some thing already working? or is it open for contributions?

@ramaraochavali we have not started working on it.  Might be something we pick up later in the year.  Not sure about the contributions.


Ability to pass different number of parameters to the same test case using data provider

For details please visit the stackoverflow link here.

@prasanta-biswas - Re-iterating your question. You would like TestNG to start being agnostic with the parameters length when dealing with data driven test methods i.e., TestNG should ignore the number of parameters that are to be expected by a data driven test method, and forcibly try to bind the @Test method with its dataprovider.
Please refer to the answers to your question.
IMHO, this is not a use case that maybe addressed by TestNG. You would need to adopt one of the following approaches (all of them have been provided as answers to your stack overflow question)

Inspect the Method object that TestNG injects into the @DataProvider annotated method and based on it, toggle between the data to be sent back.
Wrap your parameters inside a custom Object and then extract out values from within it.

I'm not sure to understand the need but as suggested on SO, you can wrap the parameter logic into interfaces/objects.

I thought this could be a great feature in terms of reusability.

@prasanta-biswas - Yes I hear you and understand the intent. Its just that, this is already possible currently in TestNG without the TestNG codebase going through any changes, if you follow one of the options that were called out in StackOverFlow as answers to your question. I hope that answers your question and you can close this issue.

yes as a workaround your answer there solves it.

What values should TestNG put when the data provider doesn't provide them? And why don't your data provider providing all parameters of the method?
@DataProvider(name="dp")
public Object[][] dp(Method m) {
  Class<?>[] params = m.getParameterTypes();
  // return appropriate values according `params`
}

@juherr - We can close this issue I guess.

@prasanta-biswas Your use case looks too specific to be integrated into TestNG and you have workarounds to do it, then I close the issue.
But thanks for the idea and feel free to propose things if you think it could be interesting for others :)


Add link to buildbot results

When the "test-with-buildbots" label is applied, Bedevere posts a comment to notify that builds have been scheduled, but the comment is quite unhelpful as it doesn't say how the results can be accessed.
It should be possible to add a hyperlink to the buildbot results page for the particular commit, or at least the given PR (for example https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F30617%2Fmerge or https://buildbot.python.org/all/#/changes/14341 in the case above).

When the "test-with-buildbots" label is applied, Bedevere posts a comment to notify that builds have been scheduled, but the comment is quite unhelpful as it doesn't say how the results can be accessed.

But I think adding a link to https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F30617%2Fmerge is a good idea that we can explore 👍


Permissions support for Workbooks, Datasources, Projects

Addresses #41
@t8y8 previously commented in the conversation.
My approach here was to minimize the duplication of code as Projects, Datasources, and Workbooks all have the same remote access model.  The two bigger classes, PermissionsItem and EndpointWithPermissions are more like mixins which add the functionality.
Other classes added are GranteeCapabilityItem which stores the actual permissions for a single group and Permission which stores all the constants.
I tried to closely follow the way the data and naming conventions are represented in the API.  One thing to note: group permissions and user permissions are stored in the same list.  The previous partial implementation suggested that we keep user and group permissions separate.  I wanted to keep them together to match the API.  In addition, the permissions collection is a list so there is a chance for users of this client library might have two separate GranteeCapabilityItems for the same entity.
I also added a couple of test cases to validate reading.  I tested reading permissions and updating permissions for both users and groups on a Tableau Server 10.1 deployment.

Unit tests have been failing due to some other external thing.  Last time I checked trunk is actually broken at the following unit test
======================================================================
ERROR: test_populate_preview_image (test.test_workbook.WorkbookTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/travis/build/tableau/server-client-python/test/test_workbook.py", line 313, in test_populate_preview_image
    self.assertEqual(response, single_workbook.preview_image)
AttributeError: 'WorkbookItem' object has no attribute 'preview_image'

@t8y8, I see your point.  I believe this shouldn't be too bad to rework.
Regarding your update, are you ok with the way permissions are organized?  I could do something like put the PermissionsItem inside another dictionary to ensure duplication doesn't happen.

@t8y8, I have addressed the inheritance issue by replacing with composition.  There is _PermissionsEndpoint which other Endpoints can instantiate and pass calls to.  In addition, I managed to fix the unit test problem.  For some reason whenever I checkout the development branch and commit, my local git client removes the workbook.preview_image endpoint.  Now all the checks pass.
Let me know if there is anything else you want changed.
class _PermissionsEndpoint(Endpoint):
    ''' Adds permission model to another endpoint

    Tableau permissions model is identical between objects but they are nested under
    the parent object endpoint (i.e. permissions for workbooks are under
    /workbooks/:id/permission).  This class is meant to be instantated inside a
    parent endpoint which has these supported endpoints
    '''

@DepthDeluxe I played with some things a bit, and here is the high level API I like for setting permissions. It matches the conceptual model of the UI, and I think feels pretty clean. It's quite different from the underlying XML though:
PermissionsRule(grantee : Union[UserItem, GroupItem], capabilities : Dict[Capability, Mode])
server.projects.update_permission(permissions : List[PermissionsRule])

cool_guy_permissions = {Perms.Caps.Read: Perms.Mode.Allow, Perms.Caps.Write: Perms.Mode.Allow}

tyler_permissions = PermissionsRule(tyler_user_item, cool_guy_permissions)
all_user_permissions = PermissionsRule(all_users_group, {Perms.Caps.Read: Perms.Mode.Deny})

permissions = [tyler_permissions, all_user_permissions]

I need to think through delete a little more, but what do you think?

@DepthDeluxe Just wanted to ping you for your thoughts and see if you were still interested in working on this? We'd really love to get this ready to merge and fill the gap in the library :)

@DepthDeluxe I don't quite follow what you mean by call magnification, can you provide an example?
We could lazy load attributes, we basically do that for anything that requires a populate_x call, just depends on what you mean exactly.
I think a PermissionsRule is just your ItemWithPermissions except we simplify the Capabilities a bit, and we just hold a single grantee object instead. Oh, is this what you mean by magnification, where the grantee object only holds the ID and you want more attributes from it?

@t8y8, yes I'm concerned about making a lot of requests.  This wouldn't be the case if we kept the mapping based on IDs like below.
permissions: {
    "$USER_ID": {
        "Read": "Allow",
        "Modify": "Deny"
    },
    "$GROUP_ID": {
        "Modify": "Allow"
    }
}

where $USER_ID and $GROUP_ID are the ids of the target.  This way we can ensure that there aren't multiple PermissionsRules for the same ID. The only thing I don't like about this is mixing the two IDs together, if we just have the IDs how do we know if we are referring to a user or a group?
Also I'm leaving out an important thing here: my primary use-case is an automated scanning process that will check the All Users group permission and set them to a predefined value if it isn't what its supposed to be.  Our current discussion is more around how to set permissions but reading them is just as important.
I guess then the approach would be

Get the All Users group id
Get the permissions for each workbook
Check if All Users id is present in the collection
a. If it is, then check to see if it is the right value.  If it isn't set properly, then set the permission to proper value
b. If it isn't set the permissions

Perhaps the structure should be more like this:
group_permissions: {
    "$USER_ID": {
        "Read": "Allow",
        "Modify": "Deny"
    },
}
user_permissions: {
    "$GROUP_ID": {
        "Modify": "Allow"
    }
}

This way we only get what we are looking for.  Thus the class would be more like
PermissionsItem(group_permissions: Dict[GroupId, Dict[Capability, Mode]], user_permissions: Dict[UserId, Dict[Capability Mode]])

My gut feeling says that it would be nice to have a helper function to make it easy to get the actual UserItem and GroupItem objects from these dictionaries (primarily to see object names to make sense of who is getting assigned permissions) even though it is one quick call away via server.groups.get_by_id().  For example, if you are trying to display what users have what permissions, you are going to have to mentally jump back and forth between traversing this structure/parsing permissions and pulling the object from the server via its ID to get the human readable name of the object.  Does that make sense?

@t8y8, I have done another draft of the API implementation.  Simplified naming conventions and the way that capabilities are stored.  GranteeCapabilityItem is now CapabilityItem.  Now the PermissionsItem contains a map consisting of
(GranteeType, Server_ObjectId) -> CapabilityItem

I also addressed some of the above comments in particular places where the code didn't change.
Please let me know what you think.

Thanks, I will take a look as soon as aI can, definitely this week.

Pinging myself -- Haven't forgotten you.

@t8y8 bumping, did you forget me now? 😭

I have not, just flooded with the 'day job' :(
Would you be willing to give me 'push' on your fork? I'd love to clone it and play around with a few scripts and try and collaborate there before merging back in here?

@t8y8 no problem, been there 😅
I have granted you collaboration access to my repo, feel free to play around with it.

@DepthDeluxe thanks! I'm beginning to play around with it, sorry this is taking time... you know how open source goes :/

@t8y8 any updates?

class PermissionsGrantee:
grantee_type = xpath-to-find-element-name
grantee_id = xpath-to-get-id
class WorkbookItem:
permissions: PermissionsCollection
class PermissionsCollection:
# __init__(self, rules):
# rules: List[PermissionsRule]

class PermissionsRule:
grantee_type: PermissionsGrantee
grantee_id: str
permissions_map: Dict[Capability: Mode])
class Capability:
# capability_name: str
# mode: str

class _PermissionsEndpoint:
def update(self, item, permissions): -> Item
def delete(self, item, permissions): -> Item
# This would iterate and call delete on the map,
# so calling update then delete then update would even out.
Based on your 'development' branch, I believe this is pretty close to what you have.
Rename PermissionsItem to PermissionsCollection.
Rename CapabilityItem to PermissionsRule.
Let's make a PermissionsGrantee class that's responsible for parsing out the element name and for serializing itself
I think we can use xpath to get the type based on the tag name, rather than the try/except dance and then the ('Item').split.lower() dance
capabilities[(grantee_type, grantee_id)] = capability_item
This logic to construct your list of rules is currently in the parser, and I think that should maybe move to business logic of the PermissionsCollection class
but I haven't really cracked that yet, it just took me a long time to figure out how the list was getting built (line 109 of permissions_item). Open to ideas there.
So overall, I actually think this is close, and I have some ideas for how to move forward quickly:

I will try to hack on this more tomorrow; but I actually would be available for a call/screen share to run through ideas with you
I think you should trim the PR down to just the workbook type for now, so the reviews look less scary; once we feel good it's mostly copy paste for the other types
What do you think of the comments above?

@DepthDeluxe I tried pushing my in-progress tweaks to your fork in a new branch, but it says I'm still denied push

@t8y8 I think what you are suggesting is definitely close to what I already have and seems good.  I would be open to a call sometime this week to discuss details if necessary.  Send me an email at<EMAIL_ADDRESS>to organize the call.

@t8y8 Made some extensive additions around permissions.  Closing this old pull request.


problem with "dotnet restore"

accroding to instructions when i use "dotnet restore" in  AspNetCoreSpa folder (step3)
i get this error:
warn : The folder 'C:\test\AspNetCoreSpa' does not contain a project to restore.
and
dotnet run
The current project is not valid because of the following errors:
C:\test\AspNetCoreSpa(1,0): error DOTNET1017: Project file does not exist 'C:\test\AspNetCoreSpa\project.json'.

can you provide result of:
dotnet --info

@webnegar can this issue be closed?


Unable to connect peers in standalone mode

I had started one rippled server in standalone mode in LAN.
Now I want to connect peers to that server, I had already tried using [ips]:
[ips]
<IP_ADDRESS> 51235

But, it always connect to main server https://vl.ripple.com.
So, how can I configure one pc as server and another pc as peer?

I think I remember something about rippled usually refusing to connect to IPs in local ranges (since often this would be peers leaking local IPs instead of their public ones).
Maybe try [ips_fixed]?

You cannot connect to anyone when in standalone mode; the server is literally running by itself and will not attempt to make any outgoing connections nor will it allow incoming connections to other rippled servers.
https://vl.ripple.com is not a rippled server; it's a web server.

So, how can I configure one pc as server and another pc as peer?

It's not clear to me what the difference is between a "server" and a "peer". rippled is a server and connects to other rippled instances ("peers"). What exactly are you trying to achieve?

@MarkusTeufelberger, I had already tried [ips_fixed] but it doesn't work.
@nbougalis, I want rippled to connect standalone server with other rippled instance (peer).

I also see that [port_peer] is not starting in standalone mode.

That's the definition of "standalone", yes. As was already explained, you will not be able to do what you are trying to do ("I want rippled to connect standalone server with other rippled instance (peer)."). Maybe you have some misunderstandings about what you want to achieve? A server that is not clustered doesn't need to be in standalone mode for example.

Precisely what @MarkusTeufelberger said: the definition of "standalone" mode is that it does not connect to any peers.
If you want to connect a server only to specific other peers, use private peering instead.


Cover existing functionality with unit tests

Pull Request
Description

Controllers and service classes has been covered with unit tests

Database server was moved inside a docker container

Related Issue
#14
Checklist
Please review and check all applicable items:

[x] I have tested my changes thoroughly
[x] My code follows the project's coding standards and guidelines
[x] I have added necessary documentation (if applicable)
[x] I have updated relevant tests (if applicable)
[x] I have reviewed my changes to ensure there are no unnecessary changes
[x] My pull request has a descriptive title and includes a detailed description of the changes

Additional Notes
I would recommend to now open 'backed' directory in Intellij IDEA to prevent possible issues with application runs. Docker compose file is not found consistently by idea when using root folder ((
Screenshots (if applicable)

Aaaand we now have build and test runs integrated into github ci 🎉

Hey-hey :)))
Thanks a million 🥹
I tried my best, will be happy to get the questions answered and explained ❤
ps literally my mood every time after reading your PR comments
https://www.instagram.com/reel/C2DIESNMbk8/?igsh=MWw5NXNxMTF0MGk5ZA==
😂


App installer Update fails.

Describe the bug
When running the utility to install programs winget is used but if winget doesn't exist or is outdated the utility tries to install it. It fails to do so.
To Reproduce
Run utility program installer.
app installer window pops up with "This app package is not supported for installation by App Installer because it uses certain restricted capabilities."
Expected behavior
Installs/Updates winget and proceeds with install of subsequent applications selected.
Screenshots
N/A (already updates the app installer from the windows store before making this report)
Additional context
This is not a new issue; I have seen this time and time again using this script over the past year and find it frustrating having to go update the app installer manually through the Microsoft store.

I'm going to look into adding a --unknown version that should update it, but winget is imperfect for grabbing everything.


[YUNIKORN-2490] update PMC and committers

What is this PR for?
Adding new committers and PMC member
What type of PR is it?

[X] - Documentation

What is the Jira issue?

https://issues.apache.org/jira/browse/YUNIKORN-2490

How should this be tested?
NA

@brandboat: you did not show up in the reviewer list yet. Please check if I set the correct details.

@brandboat: you did not show up in the reviewer list yet. Please check if I set the correct details.

Thank you for the reminder. I've just finished setting up the related GitHub configurations.
And my personal detail is correct. Thank you @wilfred-s


Wrong dependencies download folder when specify spec.distribution.common.relativeVendorPath

spec:
  # This section describes how the KFD distribution will be installed
  distribution:
    # This common configuration will be applied to all the packages that will be installed in the cluster
    common:
      relativeVendorPath: ./barebone/vendor
      provider:
        type: eks

furyctl-ng create cluster -c barebone.yml --distro-location 'git::git@github.com:sighupio/fury-distribution.git?depth=1&ref=feature/furyctl-next'
INFO Downloading distribution...
INFO Validating configuration file...
INFO Downloading dependencies...
INFO Validating dependencies...
INFO Creating cluster...
INFO Running infrastructure phase...
INFO Creating cloud resources, this could take a while...
INFO Connecting to VPN, you will be asked for your SUDO password...
INFO Running kubernetes phase...
INFO Creating cloud resources, this could take a while...
INFO Storing cluster config...
INFO Running distribution phase
INFO Checking that the cluster is reachable...
ERRO error while creating cluster: error while executing distribution phase: error running terraform init: command execution failed: ~/.furyctl/bin/terraform/0.15.4/terraform ~/.furyctl/bin/terraform/0.15.4/terraform init: command failed - exit status 1
out: Initializing modules...
- cert_manager_iam_role in
- cluster_autoscaler_iam_role in
- ebs_csi_driver_iam_role in
- external_dns in
- load_balancer_controller_iam_role in
- velero in

err: ╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.
╵

╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat barebone: no such file or
│ directory
╵

╷
│ Error: Failed to read module directory
│
│ Module directory  does not exist or cannot be read.

relativeVendorPath is an internal field, this should be addressed in https://github.com/sighupio/product-management/issues/140


Fix NaN value in returned JSON

Changes CSV parsing logic to not create NaN values since these cannot be converted to JSON.
Fixes #29

Was there error handling to alert the user of a missing URL? IIRC, it skips the row?

It doesn't skip the row the row is still returned with an empty value for the URL field instead of an invalid JSON value. The front end code then shows the item without drawing an image.


Investigate new Test Coverage API from VSCode

This is now released in VSCode v1.88
https://code.visualstudio.com/api/extension-guides/testing#test-coverage

@adam-fowler What are your thoughts on bumping the engine version?

I can add this to my queue of things to investigate.

I'm happy to up the vscode version. It would require people to have VSCode from February (I think). But VSCode pretty much expects you to upgrade every month.

We're on the same page then. Thanks!


Adding quantize fake quant per channel to TFlite

Hello! I was faced with the fact that in the current version of TFlite the operation FakeQuantWithMinMaxVarsPerChannel was not implemented when quantized by means of the utility TFLiteConverter.
In this regard, the question is, is it planned to implement this operation and this type of quantization in TFlite?
And are there any known difficulties in realizing this quantization?

@synchro10  - Hi, please refer to this issue #21526 for the operations need to be added to TFLite.

These type of questions are better asked on StackOverflow since it is not a bug or feature request. There is also a larger community that reads questions there.


chore (litmus-portal): fixed userData persisting problem, logout bug fixes and cookie expiration problem

Signed-off-by: arkajyotiMukherjee<EMAIL_ADDRESS>
Proposed changes

Clearing data on logout was not happening (fixed)
User was unable to login due to token not being set properly (fixed)
Persistor was not storing the userData immediately (fixed)

Summarize your changes here to communicate with the maintainers and make sure to put the link of that issue
Types of changes
What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

[ ] New feature (non-breaking change which adds functionality)
[x] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices applies)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I have read the CONTRIBUTING doc
[ ] I have signed the commit for DCO to be passed.
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[ ] I have added necessary documentation (if appropriate)

Dependency

Please add the links to the dependent PR need to be merged before this (if any).

Special notes for your reviewer:

/preview

/preview 10


Update: AdoptOpenJDK.OpenJDK.17 version <IP_ADDRESS>

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Does your manifest conform to the 1.1 schema?

Adds installation notes that say that AdoptOpenJDK has been replaced by Eclipse Temurin.
Microsoft Reviewers: Open in CodeFlow

@wingetbot run

@wingetbot run


Issue in IE 11

Getting a syntax error in line 883
findXMPinJPEG(file)
var domDocument = dom.parseFromString( xmpString, 'text/xml' );
exif.js - version 2.2.1

Hello,
We have a similar issue. When using this image https://drive.google.com/file/d/0BzWzsJnWxQkAQ25pd0RIcHFwMWM/view we get the error that was mentioned above:

Getting a syntax error in line 883
findXMPinJPEG(file)
var domDocument = dom.parseFromString( xmpString, 'text/xml' );

This error occurs in IE11, while the functionality works fine in Chrome.


feat: build with tsc

References https://autoricardo.atlassian.net/browse/CAR-9284
Motivation and context
Moving away from pika/pack, following up on the RFC in https://github.com/carforyou/carforyou-docs/discussions/147 - this POC creates an esm and commonjs build with esm. similar result to what we had before, just without the bloat of pika/pack

this has proven the point for the POC, but I'll start over fresh


Basic validation onscripts tasks in package.json

There should be some basic validation on the build tasks providing a warning if the recommended tasks aren't being used.
For example, if you run npm run build on a package.json and the build script is pointing to febs. It would then validate the rest of the tasks as well as the buid task its self.
This will help any accidental miss configurations and in the future provide easier upgrade paths.
It will also make best practice / recommended build scripts clear.

I'm a little unclear on this one. What would an "accidental misconfiguration" look like? Could you give some examples?

I've encountered some internal customers who had some misconfigurations which prompted me to create this task. Unfortunately I don't remember what the configuration was, maybe it was from an early version?
Example code of how to configure the scripts in package.json might also be good for developer usability #16, I know I love to copy-pasta.
It might also be useful for major upgrade paths, for example for #23 we plan on changing the task api. We could warn that the task doesn't match the recommended one.
For example, when we switch the task configuration instructions to say:
NODE_ENV=prod febs prod
to:
febs prod
I think it would be handy if it had a message like "The FEBS task seems to be misconfigured, you can update it to the recommended task" [link to docs would be a nicity]. If we wanted If we wanted to be really fancy we can show the misconfigured value and the recommended value
It could not actually be a continued point of confusion but we can close and re-open if it ends up being a thing. Seems like it could be excessive? Any thoughts?

Another usecase could be that the user may just add the build task and dev task but forget to add the rest of the tasks. We may add a new task and the user may not know about the new task.
But again, i think this all could be excessive and if we even decided to do it would be low priority

Closing for now, let's reopen if misconfiguration of scripts is reported again.


OnlyM thumbnail border to have 16:9 aspect ratio

@AntonyCorbett This would be helpful as the thumbnail will look exactly as the image displayed on the screen. Thank you.

the thumbnail will look exactly as the image displayed on the screen.

@LvDaniel Not necessarily - it depends on the aspect ratio of the monitor and on any applied margins.

@AntonyCorbett true, but I think most of us use 16:9 monitors.

@LvDaniel I don't think this will ever be important enough to change. I understand the request and am always hesitant to turn down good ideas, but I need to be pragmatic too. Thanks for your continuing help and please keep the idea flowing!

@richfrantz the image will be as it is, won't be changed. Just the border will be 16:9. Now the border has ~14:9 format.

@AntonyCorbett you may have right. It's just a nice to have as most of the content is in 16:9 format. For me makes sense, but  I respect your decision. Thanks also.


[T4A6][W11-B3] Fan Weiguang

Ready for review

Some comments added. Please close the PR after reading comments. Good job.

Comments reviewed. Thank you very much!


Problem using Metal delegate on iPhone 13 mini

System information
Code written:
TFLGpuDelegateOptions options;
options.wait_type = TFLGpuDelegateWaitType::TFLGpuDelegateWaitTypePassive;
options.enable_quantization = true;
TfLiteDelegate * gpu_delegate = TFLGpuDelegateCreate(&options);
interpreter->ModifyDelegateWithGraph(gpu_delegate);

Using an iPhone 13 mini, on iOS 15.5
Tensorflow lite is compiled from source, using 2.9.1
Cross compiled from m1 mac using cmake, and bazel 5.0.0 for the required frameworks
Compiled using apple-clang 13.1
XCode version 13.4.1

Describe the problem
There is a problem trying to use Metal delegate on this specific phone (or perhaps the whole iPhone 13 family, confirmed to be happening on mini and pro). Have tested on iPhone 12 and below, and there isn't a problem with that.
Logs
Error printed by tflite. Also, returned with TfLiteStatus of 2
ERROR: TfLiteMetalDelegate Prepare: newLibraryWithSource: program_source:35:3: error: use of undeclared identifier 'simdgroup_matrix'; did you mean 'simdgroup_barrier'?
  simdgroup_matrix<FLT, 8, 8> dst_sp0_8_ch0_8(0.0f);
  ^~~~~~~~~~~~~~~~
  simdgroup_barrier
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: 'simdgroup_barrier' declared here
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:35:3: error: 'simdgroup_barrier' does not name a template but is followed by template arguments
  simdgroup_matrix<FLT, 8, 8> dst_sp0_8_ch0_8(0.0f);
  ^               ~~~~~~~~~~~
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: non-template declaration found by name lookup
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:36:3: error: use of undeclared identifier 'simdgroup_matrix'; did you mean 'simdgroup_barrier'?
  simdgroup_matrix<FLT, 8, 8> dst_sp0_8_ch8_16(0.0f);
  ^~~~~~~~~~~~~~~~
  simdgroup_barrier
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: 'simdgroup_barrier' declared here
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:36:3: error: 'simdgroup_barrier' does not name a template but is followed by template arguments
  simdgroup_matrix<FLT, 8, 8> dst_sp0_8_ch8_16(0.0f);
  ^               ~~~~~~~~~~~
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: non-template declaration found by name lookup
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:37:3: error: use of undeclared identifier 'simdgroup_matrix'; did you mean 'simdgroup_barrier'?
  simdgroup_matrix<FLT, 8, 8> dst_sp8_16_ch0_8(0.0f);
  ^~~~~~~~~~~~~~~~
  simdgroup_barrier
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: 'simdgroup_barrier' declared here
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:37:3: error: 'simdgroup_barrier' does not name a template but is followed by template arguments
  simdgroup_matrix<FLT, 8, 8> dst_sp8_16_ch0_8(0.0f);
  ^               ~~~~~~~~~~~
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: non-template declaration found by name lookup
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:38:3: error: use of undeclared identifier 'simdgroup_matrix'; did you mean 'simdgroup_barrier'?
  simdgroup_matrix<FLT, 8, 8> dst_sp8_16_ch8_16(0.0f);
  ^~~~~~~~~~~~~~~~
  simdgroup_barrier
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: 'simdgroup_barrier' declared here
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:38:3: error: 'simdgroup_barrier' does not name a template but is followed by template arguments
  simdgroup_matrix<FLT, 8, 8> dst_sp8_16_ch8_16(0.0f);
  ^               ~~~~~~~~~~~
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: non-template declaration found by name lookup
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:39:3: error: use of undeclared identifier 'simdgroup_matrix'; did you mean 'simdgroup_barrier'?
  simdgroup_matrix<FLT, 8, 8> dst_sp16_24_ch0_8(0.0f);
  ^~~~~~~~~~~~~~~~
  simdgroup_barrier
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: 'simdgroup_barrier' declared here
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:39:3: error: 'simdgroup_barrier' does not name a template but is followed by template arguments
  simdgroup_matrix<FLT, 8, 8> dst_sp16_24_ch0_8(0.0f);
  ^               ~~~~~~~~~~~
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: non-template declaration found by name lookup
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:40:3: error: use of undeclared identifier 'simdgroup_matrix'; did you mean 'simdgroup_barrier'?
  simdgroup_matrix<FLT, 8, 8> dst_sp16_24_ch8_16(0.0f);
  ^~~~~~~~~~~~~~~~
  simdgroup_barrier
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: 'simdgroup_barrier' declared here
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:40:3: error: 'simdgroup_barrier' does not name a template but is followed by template arguments
  simdgroup_matrix<FLT, 8, 8> dst_sp16_24_ch8_16(0.0f);
  ^               ~~~~~~~~~~~
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: non-template declaration found by name lookup
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:41:3: error: use of undeclared identifier 'simdgroup_matrix'; did you mean 'simdgroup_barrier'?
  simdgroup_matrix<FLT, 8, 8> dst_sp24_32_ch0_8(0.0f);
  ^~~~~~~~~~~~~~~~
  simdgroup_barrier
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: 'simdgroup_barrier' declared here
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:41:3: error: 'simdgroup_barrier' does not name a template but is followed by template arguments
  simdgroup_matrix<FLT, 8, 8> dst_sp24_32_ch0_8(0.0f);
  ^               ~~~~~~~~~~~
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: non-template declaration found by name lookup
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:42:3: error: use of undeclared identifier 'simdgroup_matrix'; did you mean 'simdgroup_barrier'?
  simdgroup_matrix<FLT, 8, 8> dst_sp24_32_ch8_16(0.0f);
  ^~~~~~~~~~~~~~~~
  simdgroup_barrier
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: 'simdgroup_barrier' declared here
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:42:3: error: 'simdgroup_barrier' does not name a template but is followed by template arguments
  simdgroup_matrix<FLT, 8, 8> dst_sp24_32_ch8_16(0.0f);
  ^               ~~~~~~~~~~~
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: non-template declaration found by name lookup
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:60:5: error: use of undeclared identifier 'simdgroup_matrix'; did you mean 'simdgroup_barrier'?
    simdgroup_matrix<FLT, 8, 8> w_o0_8_i0_8;
    ^~~~~~~~~~~~~~~~
    simdgroup_barrier
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: 'simdgroup_barrier' declared here
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:60:5: error: 'simdgroup_barrier' does not name a template but is followed by template arguments
    simdgroup_matrix<FLT, 8, 8> w_o0_8_i0_8;
    ^               ~~~~~~~~~~~
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: non-template declaration found by name lookup
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:61:5: error: use of undeclared identifier 'simdgroup_matrix'; did you mean 'simdgroup_barrier'?
    simdgroup_matrix<FLT, 8, 8> w_o8_16_i0_8;
    ^~~~~~~~~~~~~~~~
    simdgroup_barrier
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: 'simdgroup_barrier' declared here
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:61:5: error: 'simdgroup_barrier' does not name a template but is followed by template arguments
    simdgroup_matrix<FLT, 8, 8> w_o8_16_i0_8;
    ^               ~~~~~~~~~~~
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: non-template declaration found by name lookup
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:62:5: error: use of undeclared identifier 'simdgroup_matrix'; did you mean 'simdgroup_barrier'?
    simdgroup_matrix<FLT, 8, 8> w_o0_8_i8_16;
    ^~~~~~~~~~~~~~~~
    simdgroup_barrier
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: 'simdgroup_barrier' declared here
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:62:5: error: 'simdgroup_barrier' does not name a template but is followed by template arguments
    simdgroup_matrix<FLT, 8, 8> w_o0_8_i8_16;
    ^               ~~~~~~~~~~~
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: non-template declaration found by name lookup
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:63:5: error: use of undeclared identifier 'simdgroup_matrix'; did you mean 'simdgroup_barrier'?
    simdgroup_matrix<FLT, 8, 8> w_o8_16_i8_16;
    ^~~~~~~~~~~~~~~~
    simdgroup_barrier
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: 'simdgroup_barrier' declared here
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:63:5: error: 'simdgroup_barrier' does not name a template but is followed by template arguments
    simdgroup_matrix<FLT, 8, 8> w_o8_16_i8_16;
    ^               ~~~~~~~~~~~
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: non-template declaration found by name lookup
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:65:20: error: use of undeclared identifier 'w_o0_8_i0_8'
    simdgroup_load(w_o0_8_i0_8, f_offseted_x1 + 0, 8);
                   ^
program_source:66:20: error: use of undeclared identifier 'w_o8_16_i0_8'
    simdgroup_load(w_o8_16_i0_8, f_offseted_x1 + 64, 8);
                   ^
program_source:67:20: error: use of undeclared identifier 'w_o0_8_i8_16'
    simdgroup_load(w_o0_8_i8_16, f_offseted_x1 + 128, 8);
                   ^
program_source:68:20: error: use of undeclared identifier 'w_o8_16_i8_16'
    simdgroup_load(w_o8_16_i8_16, f_offseted_x1 + 192, 8);
                   ^
program_source:73:5: error: use of undeclared identifier 'simdgroup_matrix'; did you mean 'simdgroup_barrier'?
    simdgroup_matrix<FLT, 8, 8> mat_src;
    ^~~~~~~~~~~~~~~~
    simdgroup_barrier
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: 'simdgroup_barrier' declared here
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:73:5: error: 'simdgroup_barrier' does not name a template but is followed by template arguments
    simdgroup_matrix<FLT, 8, 8> mat_src;
    ^               ~~~~~~~~~~~
/System/Library/PrivateFrameworks/GPUCompiler.framework/Libraries/lib/clang/31001.518/include/metal/metal_compute:67:17: note: non-template declaration found by name lookup
METAL_FUNC void simdgroup_barrier(mem_flags flags)
                ^
program_source:74:20: error: use of undeclared identifier 'mat_src'
    simdgroup_load(mat_src, tmp_src_x1 + 0, 8);  // loading sp[0_8] src_ch[0_8]
                   ^
program_source:75:9: error: use of undeclared identifier 'dst_sp0_8_ch0_8'
    MMA(dst_sp0_8_ch0_8, mat_src, w_o0_8_i0_8, dst_sp0_8_ch0_8);
        ^
program_source:75:26: error: use of undeclared identifier 'mat_src'
    MMA(dst_sp0_8_ch0_8, mat_src, w_o0_8_i0_8, dst_sp0_8_ch0_8);
                         ^
program_source:75:35: error: use of undeclared identifier 'w_o0_8_i0_8'
    MMA(dst_sp0_8_ch0_8, mat_src, w_o0_8_i0_8, dst_sp0_8_ch0_8);
                                  ^
program_source:75:48: error: use of undeclared identifier 'dst_sp0_8_ch0_8'
    MMA(dst_sp0_8_ch0_8, mat_src, w_o0_8_i0_8, dst_sp0_8_ch0_8);
                                               ^
program_source:76:36: error: use of undeclared identifier 'w_o8_16_i0_8'
    MMA(dst_sp0_8_ch8_16, mat_src, w_o8_16_i0_8, dst_sp0_8_ch8_16);
                                   ^
program_source:76:50: error: use of undeclared identifier 'dst_sp0_8_ch8_16'
    MMA(dst_sp0_8_ch8_16, mat_src, w_o8_16_i0_8, dst_sp0_8_ch8_16);
                                                 ^
program_source:76:9: error: use of undeclared identifier 'dst_sp0_8_ch8_16'
    MMA(dst_sp0_8_ch8_16, mat_src, w_o8_16_i0_8, dst_sp0_8_ch8_16);
        ^
program_source:76:27: error: use of undeclared identifier 'mat_src'; did you mean 'tmp_src'?

ERROR: Restored original execution plan after delegate application failure.

Hi @zhihuiloke !
Could you try with below Gpu delegate initialization and let us know.
// Set up interpreter.
auto model = FlatBufferModel::BuildFromFile(model_path);
if (!model) return false;
tflite::ops::builtin::BuiltinOpResolver op_resolver;
std::unique_ptr<Interpreter> interpreter;
InterpreterBuilder(*model, op_resolver)(&interpreter);

// NEW: Prepare GPU delegate.

auto* delegate = TFLGpuDelegateCreate(/*default options=*/nullptr);
if (interpreter->ModifyGraphWithDelegate(delegate) != kTfLiteOk) return false;

// Run inference.
WriteToInputTensor(interpreter->typed_input_tensor<float>(0));
if (interpreter->Invoke() != kTfLiteOk) return false;
ReadFromOutputTensor(interpreter->typed_output_tensor<float>(0));

// Clean up.
TFLGpuDelegateDelete(delegate);

Reference
Thank you!

Some additional info:

CMake is compiled with c++17, so .bazelrc is also patched the same way to avoid the absl::string_view issue

Some stuff I have tried, but didn't work:

Adding these at the top of GeneratedConvolution

c += "#include <metal_stdlib>\n";
c += "#include <metal_simdgroup_matrix>\n";
c += "using namespace metal;\n";

Forced minimum iOS version to be 14.0, ensuring it is building for metal 2.3

@mohantym this is exactly how we are using the GPU delegate right now. Parts of it are redacted, but in general, the flow is exactly as described.

Hi @sachinprasadhs !
Could you please look at this issue.
Thank you!

Update: I managed to fix it, so here is one for you guys.
Looking at the newest Metal Shading Language specification, we see that simdgroup_matrix is only available from Metal 2.3 and above. I patched common.mm CreateFunction function to use Metal 2.3 for my use case, and it worked.
I have only resolved the symptom on my side, have yet to know why it is happening for iPhone 13 family. Will be willing to provide more information if needed.

Could you try with Minimum IOS version as 10 and let us know if that helps.
Tensorflow's implementation with c++ 17 is very recent and that could be the problem as well.
Let us know your findings as well. Thanks!

I don't think setting the Minimum iOS versioned to 10.0 worked. It is still having the same errors as above.

Also, compiling tflite 2.9.1 with cpp14 didn't help either.

Experienced the same issue on an iPad mini (6th gen) running iOS 15.5 built using Xcode 13.4.1.
I was running the Mobilenet_1.0_224(float) model from the iOS performance benchmarks page.
In order to get it to work, I had to use the following patch on top of v2.9.1:
https://github.com/tensorflow/tensorflow/blob/v2.9.1/tensorflow/lite/delegates/gpu/metal/common.mm
diff --git a/tensorflow/lite/delegates/gpu/metal/common.mm b/tensorflow/lite/delegates/gpu/metal/common.mm
index 51337768a09..5ce3e8917e5 100644
--- a/tensorflow/lite/delegates/gpu/metal/common.mm
+++ b/tensorflow/lite/delegates/gpu/metal/common.mm
@@ -126,7 +126,9 @@
   MTLCompileOptions* options = [[MTLCompileOptions alloc] init];

   // Runtime checks for the iOS version independently of minimum target iOS.
-  if (@available(macOS 10.14, iOS 12.0, tvOS 12.0, *)) {
+  if (@available(macOS 11.0, iOS 14.0, tvOS 14.0, *)) {
+    [options setLanguageVersion:MTLLanguageVersion2_3];
+  } else if (@available(macOS 10.14, iOS 12.0, tvOS 12.0, *)) {
     [options setLanguageVersion:MTLLanguageVersion2_1];
   } else if (@available(macOS 10.13, iOS 11.0, tvOS 11.0, *)) {
     [options setLanguageVersion:MTLLanguageVersion2_0];

Looks like a similar patch is already in master: https://github.com/tensorflow/tensorflow/commit/af256daa1495792613156192c02e92685337173e

"Looks like a similar patch is already in master: https://github.com/tensorflow/tensorflow/commit/af256daa1495792613156192c02e92685337173e
Edit: actually, it looks like that patch fixes the bug that allows simdgroup_matrix to be used for Metal 2.2."
This is correct. Initially similar patch was submitted together with kernel that uses simd matrix multiplication. But it was reverted due to internal reasons.
I also would like to add that this kernel indicates that fp32 precision was used.
Fp32 is fully supported, but fp16 has better performance and highly recommended when possible.

Closing as there seems to be a fix at 2.10 onwards


Update to version 0.2.1

MNT: Re-rendered with conda-build 3.21.8, conda-smithy 3.19.0, and conda-forge-pinning 2<IP_ADDRESS>.31.58

Checklist

[x] Used a personal fork of the feedstock to propose changes
Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Add support for JOINs

It seems only the first table is extracted, right?  Would it be possible to add support for JOINs?

@otisg what did you imagine that the output would be? Something like SELECT FROM foo, bar, baz or?

@watson Yes, that's the sort of thing I was imagining.  Maybe with tables sorted in the same fashion all the time to avoid having both SELECT FROM foo, bar and SELECT FROM bar, foo.

@otisg It's a pretty complicated thing to parse given the complexity of SQL, so I don't know when I will have time to do this. In the meantime you are of cause welcome to submit a pull request :smiley:

Perhaps https://www.npmjs.com/package/node-sqlparser could be used?

@otisg I was looking at it before making this module, but it's really really complicated (no critique... it has to because it parses the entire SQL query). I wanted a simpler module for a simpler purpose that wouldn't have that big an overhead. But there might be something in there I can use though - thanks for reminding me :smiley:


dont mask error when running a grouped task

Without this a grouped task with a failing task won't stop and will keep running the rest of the tasks in the same group. For instance:
def grouped_tasks(task):
     task.run(task=this_task_fails)
     task.run(task=another_task)

brigade.run(task=grouped_tasks)

Without this patch another_task will run even if this_task_fails. With this patch, you have to catch if if you want to keep going.

Pull Request Test Coverage Report for Build 566

2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
5 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.5%) to 86.905%

Files with Coverage Reduction
New Missed Lines
%

brigade/core/init.py
5
85.05%

Totals

Change from base Build 560:
-0.5%

Covered Lines:
876

Relevant Lines:
1008

💛  - Coveralls

Pull Request Test Coverage Report for Build 566

2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
5 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.5%) to 86.905%

Files with Coverage Reduction
New Missed Lines
%

brigade/core/init.py
5
85.05%

Totals

Change from base Build 560:
-0.5%

Covered Lines:
876

Relevant Lines:
1008

💛  - Coveralls

Looks good to me.


Problems with code completion after adding submodules to ROPE_PREFS/extension_modules

From ccordoba12 on 2011-11-27T22:39:39Z
While working with scipy.stats, I noticed that code completion for it was very slow the first time it was called. After reading your discussion with Ali about the numpy completion slowness, I decided to add it to 'extension_modules'.
Things worked great (time was reduced from about 6 seconds to milliseconds) but then I couldn't get completions for the distribution methods (cdf, pmf, entropy, etc). So I turned on DEBUG on sourcecode/codeeditor and got this traceback while trying to get the completion of scipy.stats.binom:
Traceback (most recent call last):
File "/home/carlos/Projects/spyder/trunk/spyderlib/widgets/sourcecode/codeeditor.py", line 135, in get_completion_list
source_code, offset, resource)
File "/home/carlos/Projects/spyder/trunk/rope/contrib/codeassist.py", line 33, in code_assist
return assist()
File "/home/carlos/Projects/spyder/trunk/rope/contrib/codeassist.py", line 325, in call
completions = list(self._code_completions().values())
File "/home/carlos/Projects/spyder/trunk/rope/contrib/codeassist.py", line 404, in _code_completions
result.update(self._dotted_completions(module_scope, inner_scope))
File "/home/carlos/Projects/spyder/trunk/rope/contrib/codeassist.py", line 340, in _dotted_completions
for name, pyname in element.get_attributes().items():
File "/home/carlos/Projects/spyder/trunk/rope/base/utils.py", line 10, in _wrapper
setattr(self, name, func(self, *args, **kwds))
File "/home/carlos/Projects/spyder/trunk/rope/base/builtins.py", line 115, in get_attributes
return _object_attributes(self.builtin, self)
File "/home/carlos/Projects/spyder/trunk/rope/base/builtins.py", line 128, in _object_attributes
pyobject = BuiltinFunction(builtin=child, parent=parent)
File "/home/carlos/Projects/spyder/trunk/spyderlib/rope_patch.py", line 99, in init
self.argnames = getargs(self.builtin)
File "/home/carlos/Projects/spyder/trunk/spyderlib/utils/dochelpers.py", line 134, in getargs
args = getargsfromdoc(func_obj)
File "/home/carlos/Projects/spyder/trunk/spyderlib/utils/dochelpers.py", line 119, in getargsfromdoc
return getargsfromtext(obj.doc, obj.name)
AttributeError: 'vectorize' object has no attribute 'name'
Then I printed the func_obj variable in utils/dochelpers/getargs and I got even more startling results while trying to do the same thing:
<function call at 0x4732398>
<built-in method format of nbinom_gen object at 0x472fed0>
<function init at 0x4731488>
<built-in method new of type object at 0x84e6a0>
<built-in method reduce of nbinom_gen object at 0x472fed0>
<built-in method reduce_ex of nbinom_gen object at 0x472fed0>
<built-in method sizeof of nbinom_gen object at 0x472fed0>
<built-in method subclasshook of type object at 0x4803df0>
<function _argcheck at 0x4732d70>
<function _cdf at 0x4732ed8>
<function _cdfsingle at 0x4731848>
<function _construct_default_doc at 0x4731500>
<function _construct_doc at 0x4731578>
<function _entropy at 0x47322a8>
<function _fix_loc at 0x46829b0>
<function _fix_loc_scale at 0x4682938>
<function _isf at 0x4731b18>
<function _logcdf at 0x4731938>
<function _logpmf at 0x4732e60>
<function _logsf at 0x4731a28>
<function _munp at 0x4731c08>
<function _nonzero at 0x4731668>
<function _pmf at 0x4732de8>
<function _ppf at 0x4733050>
<function _rvs at 0x4732cf8>
<function _sf at 0x47319b0>
<function _sf_skip at 0x4732f50>
<function _stats at 0x47330c8>
<numpy.lib.function_base.vectorize object at 0x472ff10>
<function cdf at 0x4731de8>
<function entropy at 0x4732320>
<function expect at 0x4732410>
<function freeze at 0x4732230>
<numpy.lib.function_base.vectorize object at 0x472fc10>
After a couple of hours of investigation I came to the conclusion that PatchedBuiltinFunction and PatchedBuiltinName in rope_patch are the culprits for messing things up in this weird way. If I comment them then completion works as expected although (obviously) calltip generation doesn't work anymore.
I bring the issue because it seems that to get decent code completion times we will need to add a lot of modules and submodules to extension_modules.
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=853

From ccordoba12 on 2013-02-13T09:39:30Z
Blocking: spyderlib:1272

From ccordoba12 on 2011-11-27T20:06:35Z
Labels: Cat-CodeCompletion

From ccordoba12 on 2013-02-13T11:34:49Z
Labels: MS-v2.2

From ccordoba12 on 2013-02-22T08:14:37Z
This issue was updated by revision 985cd5d48d95 .
Status: Fixed


Update language identifiers and styleguide.

Title
Update language identifiers and style guide for supported languages.
Summary
Added a list of supported languages with language IDs and markdown labels to the style guide. Fixed language identifiers for C#, F# and PHP in all files to match the supported markdown labels.
Fixes #1737
Suggested Reviewers
@mairaw

@tompratt-AQ,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot


fix: d(str, str, throwable) was logging v(str, str)

when copied, mistakenly not changed the verbose to debug
added unit test to validate the fix

Coverage increased (+0.6%) to 75.143% when pulling 81aa3f1cb3f892eee48e3dccea9e3432eac956a5 on fix/debugLogWithError into b8eade3f40806ddf5ea01ad0f1cdcf83c794c1a9 on master.


Rainbow artifacts when increasing video resolution - Quest 2

I'm unable to increase the video resolution as when I pick something over 100%, I get the following video artifacts:
https://www.youtube.com/watch?v=uTwGrkk0Q-U
Weirdly enough it only occurs inside the headset, it doesn't appear if i record a video using the headset.

are you using polygraphene ALVR or the quest optimized fork:
https://github.com/alvr-org/ALVR

I'm using the quest optimized fork that you linked

In that case please open a support request on the fork.

Thanks, will do.


Refactor: Replace Traditional Switch Statements with Switch Expressions

This PR refactors several components to replace traditional switch statements with the new switch expressions.
This change enhances code readability, reduces the risk of fall-through errors, and allows for a more concise syntax.
Changes Made
Files Updated:
AzureAiSearchFilterExpressionConverter
MilvusFilterExpressionConverter
RedisFilterExpressionConverter
RedisVectorStore
TypesenseFilterExpressionConverter
WeaviateFilterExpressionConverter

Key Modifications:
Replaced traditional switch statements with switch expressions in the listed files.
Improved syntax by utilizing arrow (->) syntax for case actions, removing the need for explicit break statements.
Added default cases to handle unknown message types more cleanly.
Benefits
Improved Readability: The new switch expressions simplify the code structure, making it easier to follow.
Reduced Errors: Eliminating fall-through behavior minimizes the potential for bugs.
Direct Value Assignment: The ability to return values directly enhances code clarity and intent.

Thanks!
merged in 6a3c54888385a91168f8408c43f428bc469e30f5


Remove Secure Score Changes from AAD

🐛 Summary
The Secure Score Graph cmdlet Get-MgSecuritySecureScore was implemented for MS.AAD.7.2v1 but needs to be removed because of implementation problems. It may be investigated further in Flipper. See #548 for more details.
Steps to Remove Secure Score from MS.AAD.7.2v1

Remove Get-MgSecurityScore call in the AAD provider and its key in the resulting JSON
Remove Microsoft.Graph.Security in the RequiredVersions.ps1 and utils\UninstallModules.ps1 files
Remove Some of the updates to the MS.AAD.7.2v1 test (those integrating secure score, but leave the PolicyID update)
Remove all of the unit test updates

Acceptance Criteria

[ ] Run the tool against AAD and ensure MS.AAD.7.2v1 shows as Not Implemented (i.e., manual check required)

Close issue as PR was merged into emerald.


implemented keepOpen and item refresh after click

Implemented two features:

If a menu item includes the keepOpen option which evaluates to true, the menu is not closed after an item is clicked.
If a menu is kept open, the clicked item is refreshed by reapplying the current values of iconImage and iconCssClass. This way we can dynamically change the appearance, e.g. to mark that some items were filtered out.

No point in keeping this open.

thanks @berislavlopac you do realise this repo is dead? Current repo is at https://github.com/6pac/SlickGrid

That's fine, but I'm not working with Javascript any more. 😊 Please feel free to reuse this PR there is you find it useful.


FIK751 and FIK752 Payment Slip setup for Configurable Business Documents

I have a customer where we would like to implement Configurable Business Documents (CBD) for Free Text Invoice and Sales Invoice.
We have setup everything in relation to Free Text Invoice, and it works with CBD, but if I setup on the invoice or the customer to print FIK751 payment slip, it prints the same free text invoice regardless, which results in no payment slip being printed.
Also in the "Free Text Invoice (Excel)" template I havent found anything related to this.
Is there a separate template for this, and also any advise on how to implement this functionality which i guess should be related to danish globalisation.
With regards
Bo Jensen

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

ID: 0928bf9e-9734-1099-0eb1-a41407fa4647
Version Independent ID: a670e9fb-684d-a01d-9bca-f7bf767a62b0
Content: Set up payment slip format - Finance | Dynamics 365
Content Source: articles/finance/localizations/tasks/set-up-payment-slip-format.md
Service: dynamics-ax-applications
Product: ****
Technology: ****
GitHub Login: @EvgenyPopovMBS
Microsoft Alias: epopov

Thank you for the feedback. The described issue is a known functional gap. It is already registered in the backlog for a further product improvement.
Best regards,
Ilya Kondratenko
_An internal reference: https://msdyneng.visualstudio.com/FinOps/workitems/edit/446462.


Register

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/95970
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.15 -m "<description of version>" ad0b47b2a8a8db2ecbf700676bc05a483cb552e0
git push origin v0.1.15

Also, note the warning: This looks like a new registration that registers version 0.1.15.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/95970
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.15 -m "<description of version>" a5d7838f374fe9e6b9895b27e4fcba2f13c426e5
git push origin v0.1.15

Also, note the warning: This looks like a new registration that registers version 0.1.15.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.


Watch contract configmap in channel controller

Fixes #

Proposed Changes

Watch contract configmap in channel controller
Add unit tests for the channel controller

Release Note

Docs

/lgtm

/test pull-knative-sandbox-eventing-kafka-broker-integration-tests