[bug] save settings dialog triggers on exit even if no changes were made

0.14.1
win 1909
Slide a FZ-setting to on, then to off, so no change was being done.
Expected behaviour:
Sliding something "on" will make the grey save-button blue.
Sliding it off again will color it grey again.
You may close the window without being molested.
Observed behaviour:
Sliding something "on" will make the grey save-button blue.
Sliding it to "off" again and the button will still be blue.
If you try to exit settings now, you'll be accosted by a nonsensical prompt about saving changes.
video documentation:
https://www.loom.com/share/05f00a4e2dc74e29899fe8b8b1daca20

This will be fixed in Settings v2.

if you want to do an early test drive, https://github.com/microsoft/PowerToys/tree/dev/settingsV2 is the working branch

thanks for the invitation. Will check it out this this week.

Sorry, can't build this. The devdocs aren't made with people in mind who have no experience with those tools. They aren't thorough enough.
[a simple video recording of the process of the process would be fine, but I can't deal with ambiguity, random unaccounted dialogs and Net-framework issues, when I'm not exactly sure what a Net-framework even is]

Good feedback. This is something we are striving for, project F5 ready and better docs. Feature branches get a bit more leeway as stuff is under flux.

Changed title to indicate we are not going to fix it for Settings v1.

The new Settings in 0.18 https://github.com/microsoft/PowerToys/releases have resolved the issue.


Pin golang image in nb tests

@lukasz-antoniak is working on a fix for the nb tests on a separate PR, closing this


Add an option for CA to append DNS to cert for webhook injector service

@yusuoh: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
567530aca96174c4a6a728ca7aa2b74a6d9726c0
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Please hold on the submission per Wencheng's suggestion in the email thread.

And the test coverage seems dropping, please help to fix it before submission, thanks

@yusuoh: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
384c00ea34c12ad96d3982b7806e99dc2f3851a3
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yusuoh: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
384c00ea34c12ad96d3982b7806e99dc2f3851a3
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
384c00ea34c12ad96d3982b7806e99dc2f3851a3
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yusuoh: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
384c00ea34c12ad96d3982b7806e99dc2f3851a3
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
384c00ea34c12ad96d3982b7806e99dc2f3851a3
link
/test e2e-bookInfo

prow/istio-pilot-e2e-v1alpha3.sh
384c00ea34c12ad96d3982b7806e99dc2f3851a3
link
/test istio-pilot-e2e-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@yusuoh: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
384c00ea34c12ad96d3982b7806e99dc2f3851a3
link
/test e2e-bookInfo

prow/istio-pilot-e2e-v1alpha3.sh
384c00ea34c12ad96d3982b7806e99dc2f3851a3
link
/test istio-pilot-e2e-v1alpha3

prow/istio-pilot-e2e.sh
384c00ea34c12ad96d3982b7806e99dc2f3851a3
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yusuoh: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
384c00ea34c12ad96d3982b7806e99dc2f3851a3
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
384c00ea34c12ad96d3982b7806e99dc2f3851a3
link
/test istio-pilot-e2e

prow/istio-pilot-e2e-v1alpha3.sh
384c00ea34c12ad96d3982b7806e99dc2f3851a3
link
/test istio-pilot-e2e-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Added the namespace parameter. PTAL

@yusuoh @ayj This PR breaks prow/e2e-simpleTests.sh
Please fix it.
kubectl logs -n simple-auth-test-6498f9f8b3e2401c9d37   istio-ca-5bfc5489c7-jzfkm
Error: unknown flag: --append-dns-names
Usage:
  istio_ca [flags]
  istio_ca [command]
Available Commands:
  help        Help about any command
  probe       Check the liveness or readiness of a locally-running server
  version     Prints out build version information
Flags:
      --cert-chain string                          Path to the certificate chain file
      --grpc-hostname string                       The hostname for GRPC server. (default "localhost")
2018-03-30T11:38:00.929005Z     error   unknown flag: --append-dns-names
      --grpc-port int                              The port number for GRPC server. If unspecified, Istio CA will not server GRPC request.
  -h, --help                                       help for istio_ca
      --istio-ca-storage-namespace string          Namespace where the Istio CA pods is running. Will not be used if explicit file or other storage mechanism is specified. (default "istio-system")
      --kube-config string                         Specifies path to kubeconfig file. This must be specified when not running inside a Kubernetes pod.
      --listened-namespace string                  Select a namespace for the CA to listen to. If unspecified, Istio CA tries to use the ${NAMESPACE} environment variable. If neither is set, Istio CA listens to all namespaces.
      --liveness-probe-interval duration           Interval of updating file for the liveness probe.
      --liveness-probe-path string                 Path to the file for the liveness probe.
      --log_as_json                                Whether to format output as JSON or in plain console-friendly format
      --log_callers                                Include caller information, useful for debugging
      --log_output_level string                    The minimum logging level of messages to output, can be one of "debug", "info", "warn", "error", or "none" (default "info")
      --log_rotate string                          The path for the optional rotating log file
      --log_rotate_max_age int                     The maximum age in days of a log file beyond which the file is rotated (0 indicates no limit) (default 30)
      --log_rotate_max_backups int                 The maximum number of log file backups to keep before older files are deleted (0 indicates no limit) (default 1000)
      --log_rotate_max_size int                    The maximum size in megabytes of a log file beyond which the file is rotated (default 104857600)
      --log_stacktrace_level string                The minimum logging level at which stack traces are captured, can be one of "debug", "info", "warn", "error", or "none" (default "none")
      --log_target stringArray                     The set of paths where to output the log. This can be any path as well as the special values stdout and stderr (default [stdout])
      --max-workload-cert-ttl duration             The max TTL of issued workload certificates (default 168h0m0s)
      --probe-check-interval duration              Interval of checking the liveness of the CA. (default 30s)
      --root-cert string                           Path to the root certificate file
      --self-signed-ca                             Indicates whether to use auto-generated self-signed CA certificate. When set to true, the '--signing-cert' and '--signing-key' options are ignored.
      --self-signed-ca-cert-ttl duration           The TTL of self-signed CA root certificate (default 8760h0m0s)
      --self-signed-ca-org string                  The issuer organization used in self-signed CA certificate (default to k8s.cluster.local) (default "k8s.cluster.local")
      --signing-cert string                        Path to the CA signing certificate file
      --signing-key string                         Path to the CA signing key file
      --upstream-auth string                       Specifies how the Istio CA is authenticated to the upstream CA. (default "mtls")
      --upstream-ca-address string                 The IP:port address of the upstream CA. When set, the CA will rely on the upstream Istio CA to provision its own certificate.
      --upstream-ca-cert-file string               Path to the certificate for authenticating upstream CA.
      --workload-cert-grace-period-ratio float32   The workload certificate rotation grace period, as a ratio of the workload certificate TTL. (default 0.5)
      --workload-cert-min-grace-period duration    The minimum workload certificate rotation grace period. (default 10m0s)
      --workload-cert-ttl duration                 The TTL of issued workload certificates (default 19h0m0s)
Use "istio_ca [command] --help" for more information about a command.


Improvement for k8s.io/zh/docs/tasks/debug-application-cluster/audit/

don‘t know how to do
how to setup audit as newbe

close


Figure out what's wrong with sourcemaps

See https://github.com/facebookincubator/create-react-app/pull/1101#issuecomment-264184436 for details (and other related comments).
Please let me know if you're interested in this.

Fixed -- waiting on https://github.com/webpack/source-list-map/pull/3 to land.

Landed, awesome!


Calculated property typo require fixing.

Hi mate, there is a slight typo in the Calculated Property:
Old code with a comma:
$STATES = ($JOBS | Select-Object Id, Name, IsScheduleEnabled, @{ N = "IsSchedulable", E = { $_.IsSchedulable() } })
Updated code with a semicolon:
$STATES = ($JOBS | Select-Object Id, Name, IsScheduleEnabled, @{ N = "IsSchedulable"; E = { $_.IsSchedulable() } })
I hope that helps.

Thanks, it is fixed


Roll Plugins from 152ae1f7b80d to 09e2d5c2610a (1 revision)

https://github.com/flutter/plugins/compare/152ae1f7b80d...09e2d5c2610a
2021-06-24<EMAIL_ADDRESS>[url_launcher] Fix test button check for iOS 15 (flutter/plugins#4088)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-plugins-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


When the camera view is unmounted with frameProcessor enabled, there was a view not found error

What were you trying to do?
I use react navigation to open a barcode scanning page. After I pressed the back button on Android, there was the ViewNotFoundError.
Reproduceable Code
No response
What happened instead?

Relevant log output
No response
Device
Sharp Aquos S2 (Android 8)
VisionCamera Version
2.12.0
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

All right, there are similar issues: https://github.com/mrousavy/react-native-vision-camera/issues/626#issuecomment-1004699011

Hiding the header and using the back button can avoid the error from happening.
<Root.Group screenOptions={{ headerShown: false }}>
  <Root.Screen name="BarcodeScanner" component={BarcodeScanner} />
</Root.Group>

My header is disabled (headerShown: false) and I get the same error.
This is how my App is composed.
   <Tab.Navigator
      screenOptions={{
        headerShown: false,
        tabBarShowLabel: false,
      }}>
      <Tab.Screen
        name={i18n.t('navigation.finder')}
        component={List}
      />
      <Tab.Screen
        name={i18n.t('navigation.finder')}
        component={Finder}
      />
      <Tab.Screen
        name={i18n.t('navigation.more')}
        component={More}
      />
    </Tab.Navigator>

The Camera is mounted in the central tab (Finder), I get the error randomly when I switch between these tabs.

I don't have an Android 11 device. You can try this example: https://github.com/xulihang/react-native-barcode-overlays

I am also getting this error: Can't perform a React state update on an unmounted component.
It seems that the frame processor is still running and performing a React state update which I write in the processor.
I am trying to avoid this with this commit: https://github.com/xulihang/react-native-barcode-overlays/commit/81d6c81b93875fd3704c9ae3ec27e7fae74d761f
But the warning will come up occasionally.

Hey! Does v2.13.1 fix the issue for you?

Yes, it works! Thanks @mrousavy


Please invite me to the Recode-Hive GitHub Community Organization

Name
Sundaram Agnihotri
Discord Username (if applicable)
No response
Additional Context
No response

Invitation sent to join the GitHub Organisation. Welcome to the community 🎉
Don't forget after accepting to make it public so it appears on your GitHub profile for everyone else to see. You can do this by finding your name in the GitHub organisation list and change the dropdown to public https://github.com/orgs/recodehive/people

My name is not mention in the list

pls have a look on it


Use JPA in Custom Logic

Tutorial URL: https://developers.sap.com/tutorials/cp-apm-05-using-jpa.html
Please specify the step you are referring to: Step 3 - enable JTA support and container management.
There is no such folder named "gen" thus I cannot change the "persistence.xml" file.
Therefore at the statement:
import com.sap.demo.bookshop.jpa.my.bookshop.Books;
import com.sap.demo.bookshop.jpa.my.bookshop.Orders;
I see the error message: "error: JAVA: the import com.sap.demo cannot be resolved".
Best Regards,
Pietro

Hi Pietro,
In Step 1: Generate JPA classes, sub-step 10 requires you to build the project. If this sub-step was successful, then the JPA classes in the message would have been generated, including the gen folder. You can also perform the build by right-clicking the srv folder and selecting Build. Please let me know if you got any errors when performing this step.
Best regards,
Jijo

Hi @JijoRoyJacob,
I went through all the sub-steps of step 1 and at the end a rebuilt the whole project.

Right-clicked the main root folder and refreshed the workspace but even so I see no gen folder.

I have attached the whole project in case you might see something wrong or missing.
Best Regards,
Pietro
bookshop.zip

Hi Pietro,
I checked your project and cannot see the root cause of the problem. I'll share the project with the dev team and I'll get back to you on what I learn from them.
Best regards,
Jijo

Hi Pietro,
Sorry for the late response. The dev team colleague, I was following up with, could not replicate and also could not determine the cause of the issue you're facing. I created a brand new project followed the JPA tutorial and I was able to see the gen folder and all the succeeding steps worked as well. Kindly retest with a new project and please let me know if you still see the issue. If you still face the issue, please let me know the environment you're testing in (trial or productive).
Best regards,
Jijo

Hello Jijo,
I had struck up with the same issue mentioned by Pietro during the build. (step 10 of Use JPA in Custom Logic)
import com.sap.demo.bookshop.jpa.my.bookshop.Books;
import com.sap.demo.bookshop.jpa.my.bookshop.Orders;
I see the error message: "error: JAVA: the import com.sap.demo cannot be resolved".
There is something missing or misleading in the documentation.
Regards,
Benu

Hi Benu,
Are you testing this from your trial account?
Best regards,
Jijo

Hi Jiyo,
I have exactly the same issue that Pietro and Benu have. For me yes I use my trial account.
There is something missing here. Appreciate any guidance.
Thanks,
Tuncay

Hi Tuncay,
The order of steps listed is important. In Benu's case, we found that the order wasn't followed and so the JPA classes never got generated as part of Step 1. If you successfully execute step 1, you should be able to see the following files in the path indicated:

Try starting from scratch:

Create a new bookshop app
Add the database
Add Custom Logic
Follow the JPA tutorial. Pay special attention to Step 1.

Hope this helps.
Best regards,
Jijo

Hi Jijo,
There is definitely something missing in steps. Initially in the Step 1, I was not able to build successfully with the below error:

So I re-ran Maven with -X and enabled full debug logging. After that I have executed the Maven Goal 'generate-resources' and then the source directory /src/gen/java has been added and the build was successful:

Regards,
Sai

But my project build still fails. Please let me know what am I missing. I'm at the step 1 and followed all the steps in the sequence.

Hi Sai,
Kindly share your project so that I can take a look. And please let me know which environment you're testing this in.
Best regards,
Jijo

Hi Jijo,
Thanks for the response. I have invited you to the project and here is the link: https://github.com/balajii7/scp-demos/invitations
Regards,
Sai

Hi Sai,
I noticed that in srv/pom.xml, the dependencies are listed under the  tag. It should be listed outside the  tag. Kindly refer the screenshot and folder structure in the tutorial for more details. Rerun the build after making the changes.
Best regards,
Jijo

Hi Jijo,
I have made changes to the pom.xml, sorry for that mistake. But the build still fails with the below error:

Regards,
Sai

Hi Sai,
I see that you have these two additional dependencies slf4j-api and ngdbc specified in pom.xml. In the JPA tutorial, I have mentioned three dependencies that you'll need. I'm not sure about these two.  If its not needed for your project, remove them (at least ngdbc) and try building again.
Best regards,
Jijo

Hi Jijo,
I guess those additional dependencies were there when the project has been created, and I left them as is and added the other dependencies as mentioned in the tutorial. I removed them and the build is successful. Thanks a lot for the help.
Regards,
Sai

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.


[Proto] Keep track of ongoing allocations

What does this PR do?
Prototype to track non-freed allocations
Motivation
Ensure we can help with leak detection
Additional Notes
This is the section to put technical guidance/constraints, call out potential regressions, cite sources, and in general offer some exposition on the how of the PR.  This section doesn't need to be incredibly detailed, but it makes life easier for reviewers!
How to test the change?
Describe here in detail how the change can be validated.  This is a great section to call out specific tests you've added or improved, or to acknowledge code sections which are particularly difficult to test.

Closing in favour of : https://github.com/DataDog/ddprof/pull/177


If list --details and --diagnostic are both set, just do --diagnostic

There is considerable overlap between the --details and --diagnostic output (--diagnostic includes everything --details does). At the same time, the --diagnostic output should separate out ID3V1 and ID3V2 content. And it should provide user-friendly names for common ID3V2 fields.

Decided to simply drop the --details flag


updates and bug fixes

steps i did from the bare example:

meteor update ->
Errors while initializing project:          While loading package<EMAIL_ADDRESS>error: Command failed: /home/mbrodmann/.meteor/packages/meteor-tool/.<IP_ADDRESS>r5f63.geku++os.linux.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.linux.x86_64/dev_bundle/bin/npm rebuild --update-binary Cannot download "https://github.com/sass/node-sass/releases/download/v4.7.2/linux-x64-72_binding.node"
Solution:
replace angular-compilers with<EMAIL_ADDRESS>

npm start ->
Error: Cannot find module '/home/mibto/WebstormProjects/bare/.meteor/local/build/programs/server/node_modules/@babel/runtime/helpers/objectSpread2
Solution:
update "@babel/runtime": "7.13.7"

update Angular -> no problems

update core-js ->
Unable to resolve some modules: core-js/es7/reflect" in /home/mibto/WebstormProjects/bare/client/imports/polyfills.js (web.browser)
Solution:
replace in polyfills.ts "import 'core-js/es7/reflect'" with "import 'core-js/proposals/reflect-metadata'"

npm start -> no problems

npm run start:prod ->
Error: You must supply options.input to rollup   at Graph.generateModuleGraph (/home/mibto/.meteor/packages/digicore_angular-compilers/.<IP_ADDRESS>oov9wg.x32y++os+web.browser+web.browser.legacy+web.cordova/plugin.Angular_Compilers.os/npm/node_modules/meteor/digicore_angular-typescript-compiler/node_modules/rollup/dist/shared/rollup.js:18780:19)
Solution:
remove ROLLUP=1

npm run build:prod ->
<EMAIL_ADDRESS>(27, 25): Expected 1 arguments, but got 3.
client/imports/app/app.module.ngfactory.ts (40, 25): Expected 1 arguments, but got 3.
No Solution ( Application works but for the User this message does not feel good )

npm run test ->
Unable to resolve some modules: core-js/es7/reflect" in /home/mibto/WebstormProjects/bare/client/imports/polyfills.js (web.browser)
Solution:
replace in polyfills.spec.ts "import 'core-js/es7/reflect'" with "import 'core-js/proposals/reflect-metadata'"

TODOs:

[ ] Include changes from digicore:angular-compilers to this package and replace in .meteor/packages
[ ] Fix ROLLUP and add to start:prod and build:prod
[ ] Angular Ivy support
[ ] Define preferred solution of todos in todo-list.component.ts
[ ] Auto recompile when server code changes. ( it only works if change are in server/main.ts but not within server/imports )
[ ] Fix meteor AOT build ( app.module.ngfactory.ts (40, 25): Expected 1 arguments, but got 3 )

Thanks @mibto ! Please let us know if we can help to get this merged.

I'm merging this for now. We can continue with other small PRs for the rest :)


add university of phayao

Add University of Phayao to allow students to use JetBrains for free during their studies

@ozoneaik I am sorry, the domain up.ac.th is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).

I would like to know the details of the violation. Can you tell me?


is fake prime will be like a true prime ?

sorry for my english
but is fake prime match with true prime ?

no

No, its client sided, same as inventory changer.


COLIBRI: almost finish handling requests

Segment request operations are complete
E2E request operations with the exception of the admission one are complete

Pending:

[x] Rebase after #3855 is merged. First real commit is b8776afe

This change is

/rebase

/rebase


Can't find the p5.js lessons "11" on the website?

Sorry to post here, couldn't find a way to do it on the site.
As written above, I'm looking for the p5.js Lesson #11 (and sublesson) bit they're not on the p5.js tutorials (jumps from 10 to 12) and there's no search funtion.
What I'm actually looking for is the PROCESSING example, so I can compare the speed (vc p5.js code which is available right here, of course)
Thanks in advance

Hey Wagedu!
I checked and can't seem to find it in the current repo either, we'll be moving to a new website design and repo, when this happens I'll add this video to the list of things that seem to be missing!
P.S. you should join our community discord for questions in the future, we don't tend to use the issue feature for this!


Async validation not being called on submit after supplying initialValues

When I enter some details in my form for the first time, async validation is called and working as expected. I save these values to localstorage, so when the user refreshes the page, the values are still filled in.
If the user enters a wrong value, async validation is called, and the field is marked as an error. However, if the user refreshed, the value is still there, but the validation is never ran so the user can submit the form just fine.
I set up the form like this:
@reduxForm({
  form: 'userdataTop',
  validate,
  asyncValidate,
  asyncBlurFields: ['car_licenceplate', 'user_zipcode']
})

and I fill the form by dispatching the initialize action creator from redux-form:
dispatch(initialize('userdataTop', initialValues));

initialValues is an key-value object, with the key being the name of the field to be filled.

Look here http://redux-form.com/6.0.2/docs/api/ReduxForm.md/  at shouldAsyncValidate.
You can customise the behaviour to fit what you want.

If you are using handleSubmit correctly, it should run async validation before submitting.

@ruiaraujo nailed it.

Found my problem, hadn't to do anything with this function. I have switch in my async validation, because I do not want to do unnecessary API calls. I only want to do the call for the field that's blurred. But when the trigger is submit, there isn't a blurredField, so none of the validations is called. Thanks for pointing me in that direction!


Use posts.node.list instead of posts.list

I was stepping through the getting started docs and noticed the conditional to display the list of posts has a bug.
posts && posts.node && posts.list should be posts && posts.node && posts.node.list as list is nested under node.

Thanks for reporting! Closed by c6544dafe25f41d83163c6645ebc93f4af598aff


Cannot bind IPv6 loopback address inside container

vsts-agent creates its own network for container jobs, as per the comments:
https://github.com/microsoft/azure-pipelines-agent/blob/ed9d7ce56cfbf4447d7e77a7e3e52c07b58034d7/src/Agent.Worker/ContainerOperationProvider.cs#L104-L107
The code this equates to is in src/Agent.Worker/Container/DockerCommandManager.cs:
https://github.com/microsoft/azure-pipelines-agent/blob/ed9d7ce56cfbf4447d7e77a7e3e52c07b58034d7/src/Agent.Worker/Container/DockerCommandManager.cs#L220-L232
However, a side effect of this call is it does not explicitly enable IPv6 on the new network, and as a result, there is no IPv6 availability (even just accessing the loopback interface) inside the VM which there would otherwise be if using a correctly configured default network:
builder@xam-emag-02:/srv/azdo/a$ /usr/bin/docker network create --label d71aa1 vsts_network_3fa15cd94bfa4326962fd6ee394e83cf
9a77f434d18347035e0fe3017828428ec874429a8aaae00ccb8d1991e24c4e25
builder@xam-emag-02:/srv/azdo/a$ /usr/bin/docker run -it --network vsts_network_3fa15cd94bfa4326962fd6ee394e83cf arm64v8/ubuntu /bin/bash
root@144590f4397c:/# apt update && apt -y install net-tools
[..]
root@144590f4397c:/# ifconfig -a | grep inet6
root@144590f4397c:/#

vs
builder@xam-emag-02:/srv/azdo/a$ /usr/bin/docker run -it --network bridge arm64v8/ubuntu /bin/bash
root@7e0d7d38019b:/# apt update && apt -y install net-tools
[..]
root@7e0d7d38019b:/# ifconfig -a | grep inet6
        inet6 fe80::42:acff:fe11:2  prefixlen 64  scopeid 0x20<link>
        inet6 2001:db8:1::242:ac11:2  prefixlen 64  scopeid 0x0<global>
        inet6 ::1  prefixlen 128  scopeid 0x10<host>

This is preventing us from running some of our test suites on Azure DevOps, e.g. CoreFX tests which explicitly bind the IPv6 loopback address, not the V4 loopback address
I agree with the motivation for using a fresh network for each job run - however, there should be some code to detect whether Docker has been started with IPv6 capability, and pass an --ipv6 flag appropriately during the network create

Hi @directhex would it work for you if there will be an ability to pass --ipv6 to this command on agent? (e.g. by setting up some pipeline/environment variable)?

@anatolybolshakov yeah, trusting the user (e.g. exposing a network-options: value which is passed to docker network create as well as options: passed to docker create/run) would put the onus on me, and i'm okay with that!

This is not fixed yet, please keep it open.

This is not fixed yet, please keep it open.

I've just bumped into this via AWS ECS.  I have much less control over the networking and to the best of my knowledge creating a network for the "ECS Task" isn't an option.  It uses bridge.  I can set it to host but I'd prefer not to for security reasons.
It looks like, by default, many linux distributions have an /etc/hosts entry:
::1         localhost

So any call to bind() to localhost is going to fail.
I've tried adding /etc/docker/daemon.json
{
  "ipv6": true
}

But this has no obvious effect.
Note I'm not trying to enable IPv6 on the docker network, I just want the loopback device to have ip address ::1.  It seems weird in that in 2022 we're not enabling this by default when most desktops, laptops, servers, IOT devices will have it.

@anatolybolshakov
This is a bug not an enhancement
As far as I can tell docker is supplying /etc/hosts which, for example looks like this:
<IP_ADDRESS>	localhost
::1	localhost ip6-localhost ip6-loopback
fe00::0	ip6-localnet
ff00::0	ip6-mcastprefix
ff02::1	ip6-allnodes
ff02::2	ip6-allrouters
<IP_ADDRESS>	00d3337c986f

This isn't supplied by the host running docker and it's not supplied by the image... it must be coming from docker (somehow).
Notice that it contains the entry for ::1 localhost.  So docker is supplying the hostname localhost pointing to the address ::1 but then never creating the IP address ::1 on the loopback device.
Docker should either create ::1 or it should NOT supply this entry in /etc/hosts.  I think it's rather broken to supply any IPv6 addresses in /etc/hosts when there's no IPv6 networking.

@anatolybolshakov I see there was a PR that referenced this issue, is that enough to implement this or are we still missing something?

Hi @directhex and @akoeplinger
We already have this knob, you can use any network related arguments as env variable like --ipv6.
You need to set AZP_AGENT_DOCKER_ADDITIONAL_NETWORK_OPTIONS env variable for this.
Please, note that using --ipv6 without any subnet pool (if is not set on host machine yet) will not take effect, just use it with subnet argument together, like this  --ipv6 --subnet=2002:db8:1:1::/64
Closing this ticket, feel free to ask any other questions or let us know if it's still relevant for you.

@ismayilov-ismayil thanks, I tried setting that both as a job-level and global variable but it doesn't work. I can see the docker network command in the log is missing my values.
I think this is because the env variables get set inside of the container not outside so they have no effect.
Am I missing something?

@akoeplinger you need to set this variable on Host machine where docker network is created, rather than container inside

@ismayilov-ismayil hmm so there's no way to do this with the hosted pool then? that'd be unfortunate


Turtlebot battery monitoring

ISSUE TEMPLATE ver. 0.3.0

Which TurtleBot3 you have?

[x] Burger
[ ] Waffle
[ ] Waffle Pi

Which ROS is working with TurtleBot3?

[x] ROS 1 Kinetic Kame
[ ] ROS 1 Melodic Morenia
[ ] ROS 2 Dashing Diademata
[ ] ROS 2 Eloquent Elusor
[ ] etc (PLEASE, WRITE DOWN YOUR ROS VERSION HERE)

Which SBC(Single Board Computer) is working on TurtleBot3?

[x] Raspberry Pi 3
[ ] Intel Joule 570x
[ ] etc (PLEASE, WRITE DOWN YOUR SBC HERE)

Which OS you installed in SBC?

[x] Raspbian
[ ] Ubuntu MATE 16.04 or later
[ ] Ubuntu Server 18.04 or later
[ ] etc (PLEASE, WRITE DOWN YOUR OS)

Which OS you installed in Remote PC?

[x] Ubuntu 16.04 LTS (Xenial Xerus)
[ ] Ubuntu 18.04 LTS (Bionic Beaver)
[ ] Linux Mint 18.x
[ ] Linux Mint 19.x
[ ] etc (PLEASE, WRITE DOWN YOUR OS)

Write down software version and firmware version

Software version: [x.x.x]
Firmware version: [x.x.x]
I am not sure where I would find this info.

Write down the commands you used in order
roscore
roslaunch turtlebot3_bringup turtlebot3_core.launch
rqt

Copy and Paste your error message on terminal
not really an error

Please, describe detailedly what difficulty you are in
Hi, I would mainly like to confirm on how the voltage is being read. Is it because due to the fact that OpenCR could be treated like an arduino, there is a specific function in the code that is reading the voltage or is there an internal voltage sensor?
In addition, is it possible to change the provided code so that current can be read and recorded by the turtlebot or the remote PC? Or would a seperate current sensor be required in order to read the current?
This is mainly because i need information on power used by the turtlebot.
Thank you.

@AGmochi
Hi, the battery voltage is read from OpenCR and delivered to RPi via rosserial. You can read the topic /battery_state to check the voltage.
Publishing the battery status code is written in Arduino code here.
Unfortunately, OpenCR does not have current sensing feature, but by evaluating the voltage level, you can assume the power consumption during certain period of time.
Thank you.

Hi,
Then is it possible to add a separate current sensor to the OpenCR to let it read current?
Thank you.

@AGmochi
Yes, you can add additional sensors on OpenCR as there are multiple GPIO and ADC as well as serial ports available.
http://emanual.robotis.com/docs/en/parts/controller/opencr10/#layoutpin-map

Hi
I am slightly confused in relation to the coding. I have a current sensor connected to the OpenCR, so if I want to let ros read and save the current data, does that mean I am editing the core code for the OpenCR through the Arduino IDE? Or is there another method?

@AGmochi
If you connected the sensor output to the OpenCR input pin, you should modify the Arduino code so that the current reading from OpenCR can be sent to the RPi.

This issue will be closed as there was no activity on this thread. Please feel free to reopen the issue whenever needed.


Domain in binary format even when not set.

Hello,
I tried to setup iodine, everything seems working. However when I try to check what domains are coming to the server, they all appear to be in binary format. I've started the client to not run in binary format. I'd like to know if it is possible to make the client query domains which container only ascii characters allowed in the domain name? I've tried using -O with different encoding but still in tcpdump I saw binary domains like so:
<EMAIL_ADDRESS>Command to start the client:
iodine -r -f  -P password <IP_ADDRESS> t.iodine.com

The client automatically tests different encodings when logging in, to find the most efficient way to send data upstream.
See https://github.com/yarrick/iodine/blob/master/src/client.c#L1601
The -O flag controls downstream codec (server -> client). There is currently no flag for forcing a specific upstream codec.
What do you mean with "I've started the client to not run in binary format." ?

The query you see is still a valid DNS query (testing the limits of validation). If raw mode is used then it is just sending the raw packets instead, and the domain name you use will not be included anywhere.

Why do you think that the query is valid if the domain does not meet the domain name standard. to my knowledge characters like ? and @ are not permitted in a domain name.

Because if it works, transfers from the client to the server will be twice as fast. If you saw these domain names in the server, that means that it worked (or that you have no intermediate servers).
DNS server(s) between the client and the server only need to parse the end of the domain name - they just need enough to find the server to send it to. So the end of the domain name is still valid.

I understand this.
Would it be possible to disable this behaviour and decrease the performance in order to get domains that are "parseble". In the sense that tools like tcpdump might get those domains in a human readable domain names?
The reason I'm asking for this is that I'd like to build a dns tunneling classifier and I'd need some domains for that.

You can still parse domain names. They are encoded with length first, and then that many bytes, then repeat, following jumps for compression and ending when length is zero.
I will not change the code, but you can test with skipping parts of handshake_upenc_autodetect() in src/client.c


command runs, but nothing happens

Hi,
I have followed the instructions in the readme file, but when i run this command:

nothing happens in the magento 2 directory. Also I couldn't understand all the instructions, if anyone could make an instruction video it would be very helpfull.
thanks,
Gerben

Hi Gerben, did you add full code of extensions that you want to convert to convertm1m2-master/source folder?

Hi unirgy,
I added this files to the convertm1m2-master:
convertm1m2-master/magento (the magento 1 package with the extension i want to convert in app/code/community/VendorName/ExtensionName)
convertm1m2-master/Magento2 (the magento 2 package)
convertm1m2-master/source (where i have my extension in /vendorName/ExtensionName)

Can someone please tell me what I am doing wrong?


[ERROR] building deepspeed using bdist_wheel on Rocm 5.7 (gfx1030)

Hi,
I'v got an issue while trying to build deepspeed on ubuntu 20.20
with Rocm5.7 and gfx1030 (6900xt)
using command
DS_BUILD_OPS=1 DS_BUILD_SPARSE_ATTN=0 PYTORCH_ROCM_ARCH=gfx1030 DS_BUILD_RANDOM_LTD=0 DS_BUILD_EVOFORMER_ATTN=0  python3 setup.py bdist_wheel;

error log:
!!
  check.warn(importable)
/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'deepspeed.ops.csrc.cpu.adam' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'deepspeed.ops.csrc.cpu.adam' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'deepspeed.ops.csrc.cpu.adam' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'deepspeed.ops.csrc.cpu.adam' to be distributed and are
        already explicitly excluding 'deepspeed.ops.csrc.cpu.adam' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'deepspeed.ops.csrc.cpu.comm' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'deepspeed.ops.csrc.cpu.comm' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'deepspeed.ops.csrc.cpu.comm' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'deepspeed.ops.csrc.cpu.comm' to be distributed and are
        already explicitly excluding 'deepspeed.ops.csrc.cpu.comm' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'deepspeed.ops.csrc.cpu.lion' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'deepspeed.ops.csrc.cpu.lion' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'deepspeed.ops.csrc.cpu.lion' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'deepspeed.ops.csrc.cpu.lion' to be distributed and are
        already explicitly excluding 'deepspeed.ops.csrc.cpu.lion' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn' to be distributed and are
        already explicitly excluding 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn.epilogue' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn.epilogue' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn.epilogue' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn.epilogue' to be distributed and are
        already explicitly excluding 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn.epilogue' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn.gemm' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn.gemm' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn.gemm' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn.gemm' to be distributed and are
        already explicitly excluding 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn.gemm' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn.iterators' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn.iterators' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn.iterators' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn.iterators' to be distributed and are
        already explicitly excluding 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn.iterators' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn.transform' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn.transform' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn.transform' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn.transform' to be distributed and are
        already explicitly excluding 'deepspeed.ops.csrc.deepspeed4science.evoformer_attn.transform' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'deepspeed.ops.csrc.includes' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'deepspeed.ops.csrc.includes' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'deepspeed.ops.csrc.includes' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'deepspeed.ops.csrc.includes' to be distributed and are
        already explicitly excluding 'deepspeed.ops.csrc.includes' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'deepspeed.ops.csrc.lamb' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'deepspeed.ops.csrc.lamb' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'deepspeed.ops.csrc.lamb' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'deepspeed.ops.csrc.lamb' to be distributed and are
        already explicitly excluding 'deepspeed.ops.csrc.lamb' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'deepspeed.ops.csrc.lion' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'deepspeed.ops.csrc.lion' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'deepspeed.ops.csrc.lion' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'deepspeed.ops.csrc.lion' to be distributed and are
        already explicitly excluding 'deepspeed.ops.csrc.lion' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'deepspeed.ops.csrc.quantization' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'deepspeed.ops.csrc.quantization' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'deepspeed.ops.csrc.quantization' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'deepspeed.ops.csrc.quantization' to be distributed and are
        already explicitly excluding 'deepspeed.ops.csrc.quantization' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'deepspeed.ops.csrc.random_ltd' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'deepspeed.ops.csrc.random_ltd' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'deepspeed.ops.csrc.random_ltd' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'deepspeed.ops.csrc.random_ltd' to be distributed and are
        already explicitly excluding 'deepspeed.ops.csrc.random_ltd' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'deepspeed.ops.csrc.sparse_attention' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'deepspeed.ops.csrc.sparse_attention' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'deepspeed.ops.csrc.sparse_attention' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'deepspeed.ops.csrc.sparse_attention' to be distributed and are
        already explicitly excluding 'deepspeed.ops.csrc.sparse_attention' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'deepspeed.ops.csrc.spatial.csrc' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'deepspeed.ops.csrc.spatial.csrc' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'deepspeed.ops.csrc.spatial.csrc' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'deepspeed.ops.csrc.spatial.csrc' to be distributed and are
        already explicitly excluding 'deepspeed.ops.csrc.spatial.csrc' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'deepspeed.ops.csrc.spatial.includes' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'deepspeed.ops.csrc.spatial.includes' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'deepspeed.ops.csrc.spatial.includes' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'deepspeed.ops.csrc.spatial.includes' to be distributed and are
        already explicitly excluding 'deepspeed.ops.csrc.spatial.includes' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'deepspeed.ops.csrc.transformer' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'deepspeed.ops.csrc.transformer' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'deepspeed.ops.csrc.transformer' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'deepspeed.ops.csrc.transformer' to be distributed and are
        already explicitly excluding 'deepspeed.ops.csrc.transformer' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'deepspeed.ops.csrc.transformer.inference.csrc' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'deepspeed.ops.csrc.transformer.inference.csrc' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'deepspeed.ops.csrc.transformer.inference.csrc' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'deepspeed.ops.csrc.transformer.inference.csrc' to be distributed and are
        already explicitly excluding 'deepspeed.ops.csrc.transformer.inference.csrc' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'deepspeed.ops.csrc.transformer.inference.includes' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'deepspeed.ops.csrc.transformer.inference.includes' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'deepspeed.ops.csrc.transformer.inference.includes' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'deepspeed.ops.csrc.transformer.inference.includes' to be distributed and are
        already explicitly excluding 'deepspeed.ops.csrc.transformer.inference.includes' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'deepspeed.ops.csrc.utils' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'deepspeed.ops.csrc.utils' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'deepspeed.ops.csrc.utils' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'deepspeed.ops.csrc.utils' to be distributed and are
        already explicitly excluding 'deepspeed.ops.csrc.utils' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
running build_ext
building 'deepspeed.ops.quantizer.quantizer_op' extension
/opt/rocm-5.7.1/bin/hipcc -Icsrc/includes -I/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/torch/include -I/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/torch/include/torch/csrc/api/include -I/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/torch/include/TH -I/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/torch/include/THC -I/home/****/miniconda3/envs/llama-python/lib/python3.10/site-packages/torch/include/THH -I/opt/rocm-5.7.1/include -I/home/****/miniconda3/envs/llama-python/include/python3.10 -c csrc/quantization/dequantize.hip -o build/temp.linux-x86_64-cpython-310/csrc/quantization/dequantize.o -fPIC -D__HIP_PLATFORM_HCC__=1 -DUSE_ROCM=1 -DCUDA_HAS_FP16=1 -D__HIP_NO_HALF_OPERATORS__=1 -D__HIP_NO_HALF_CONVERSIONS__=1 -O3 -std=c++17 -U__HIP_NO_HALF_OPERATORS__ -U__HIP_NO_HALF_CONVERSIONS__ -U__HIP_NO_HALF2_OPERATORS__ -DROCM_VERSION_MAJOR=5 -DROCM_VERSION_MINOR=7 -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE=\"_gcc\" -DPYBIND11_STDLIB=\"_libstdcpp\" -DPYBIND11_BUILD_ABI=\"_cxxabi1011\" -DTORCH_EXTENSION_NAME=quantizer_op -D_GLIBCXX_USE_CXX11_ABI=0 --offload-arch=gfx1030 -fno-gpu-rdc
In file included from csrc/quantization/dequantize.hip:8:
In file included from csrc/includes/dequantization_utils_hip.h:7:
In file included from csrc/includes/conversion_utils_hip.h:9:
In file included from csrc/includes/ds_kernel_utils_hip.h:24:
In file included from /opt/rocm-5.7.1/include/hip/hip_cooperative_groups.h:38:
/opt/rocm-5.7.1/include/hip/amd_detail/amd_hip_cooperative_groups.h:638:3: error: static assertion failed due to requirement 'integral_constant<bool, false>::value': Tile size is either not a power of 2 or greater than the wavefront size
  static_assert(is_valid_tile_size<size>::value,
  ^             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/rocm-5.7.1/include/hip/amd_detail/amd_hip_cooperative_groups.h:704:55: note: in instantiation of template class 'cooperative_groups::thread_block_tile_base<64>' requested here
class thread_block_tile_type<tileSize, void> : public thread_block_tile_base<tileSize>,
                                                      ^
/opt/rocm-5.7.1/include/hip/amd_detail/amd_hip_cooperative_groups.h:781:43: note: in instantiation of template class 'cooperative_groups::thread_block_tile_type<64, void>' requested here
class thread_block_tile_internal : public thread_block_tile_type<size, ParentCGTy> {
                                          ^
/opt/rocm-5.7.1/include/hip/amd_detail/amd_hip_cooperative_groups.h:807:46: note: in instantiation of template class 'cooperative_groups::impl::thread_block_tile_internal<64, void>' requested here
class thread_block_tile<size, void> : public impl::thread_block_tile_internal<size, void> {
                                             ^
csrc/includes/reduction_utils_hip.h:362:44: note: in instantiation of template class 'cooperative_groups::thread_block_tile<64>' requested here
        data[0] = element<Op>(data[0], warp.shfl_xor(data[0], i));
                                           ^
csrc/includes/reduction_utils_hip.h:371:46: error: no member named 'shfl_xor' in 'cooperative_groups::thread_block_tile<64>'
        data[0] = element<Op1>(data[0], warp.shfl_xor(data[0], i));
                                        ~~~~ ^
csrc/includes/reduction_utils_hip.h:372:46: error: no member named 'shfl_xor' in 'cooperative_groups::thread_block_tile<64>'
        data[1] = element<Op2>(data[1], warp.shfl_xor(data[1], i));
                                        ~~~~ ^
csrc/includes/reduction_utils_hip.h:381:46: error: no member named 'shfl_xor' in 'cooperative_groups::thread_block_tile<64>'
        data[0] = element<Op1>(data[0], warp.shfl_xor(data[0], i));
                                        ~~~~ ^
csrc/includes/reduction_utils_hip.h:382:46: error: no member named 'shfl_xor' in 'cooperative_groups::thread_block_tile<64>'
        data[1] = element<Op2>(data[1], warp.shfl_xor(data[1], i));
                                        ~~~~ ^
csrc/includes/reduction_utils_hip.h:383:46: error: no member named 'shfl_xor' in 'cooperative_groups::thread_block_tile<64>'
        data[2] = element<Op3>(data[2], warp.shfl_xor(data[2], i));
                                        ~~~~ ^
csrc/includes/reduction_utils_hip.h:392:46: error: no member named 'shfl_xor' in 'cooperative_groups::thread_block_tile<64>'
        data[0] = element<Op1>(data[0], warp.shfl_xor(data[0], i));
                                        ~~~~ ^
csrc/includes/reduction_utils_hip.h:393:46: error: no member named 'shfl_xor' in 'cooperative_groups::thread_block_tile<64>'
        data[1] = element<Op2>(data[1], warp.shfl_xor(data[1], i));
                                        ~~~~ ^
csrc/includes/reduction_utils_hip.h:394:46: error: no member named 'shfl_xor' in 'cooperative_groups::thread_block_tile<64>'
        data[2] = element<Op3>(data[2], warp.shfl_xor(data[2], i));
                                        ~~~~ ^
csrc/includes/reduction_utils_hip.h:395:46: error: no member named 'shfl_xor' in 'cooperative_groups::thread_block_tile<64>'
        data[3] = element<Op4>(data[3], warp.shfl_xor(data[3], i));
                                        ~~~~ ^
csrc/includes/reduction_utils_hip.h:431:22: error: no member named 'thread_rank' in 'cooperative_groups::thread_block_tile<64>'
        if (warp_arg.thread_rank() == 0) {
            ~~~~~~~~ ^
csrc/includes/reduction_utils_hip.h:442:26: error: no member named 'thread_rank' in 'cooperative_groups::thread_block_tile<64>'
            if (warp_arg.thread_rank() < running_warps) {
                ~~~~~~~~ ^
csrc/includes/reduction_utils_hip.h:446:68: error: no member named 'thread_rank' in 'cooperative_groups::thread_block_tile<64>'
                        data + i, reduce_buffer + elems * warp_arg.thread_rank() + i);
                                                          ~~~~~~~~ ^
csrc/includes/reduction_utils_hip.h:456:82: error: no member named 'thread_rank' in 'cooperative_groups::thread_block_tile<64>'
                mem_access::store_shared<bytes>(reduce_buffer + elems * warp_arg.thread_rank() + i,
                                                                        ~~~~~~~~ ^
In file included from csrc/quantization/dequantize.hip:8:
In file included from csrc/includes/dequantization_utils_hip.h:7:
In file included from csrc/includes/conversion_utils_hip.h:9:
In file included from csrc/includes/ds_kernel_utils_hip.h:24:
In file included from /opt/rocm-5.7.1/include/hip/hip_cooperative_groups.h:38:
/opt/rocm-5.7.1/include/hip/amd_detail/amd_hip_cooperative_groups.h:837:3: error: static assertion failed due to requirement 'integral_constant<bool, false>::value': Tiled partition with size > wavefront size. Currently not supported
  static_assert(is_valid_tile_size<size>::value,
  ^             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
csrc/includes/dequantization_utils_hip.h:101:52: note: in instantiation of function template specialization 'cooperative_groups::tiled_partition<64U, cooperative_groups::thread_block>' requested here
    cg::thread_block_tile<hw_warp_size> warp = cg::tiled_partition<hw_warp_size>(tb);
                                                   ^
csrc/includes/dequantization_utils_hip.h:168:9: note: in instantiation of function template specialization 'dequantize::_to_global<__half, 8, quantize::Type::Symmetric, 8, 512>' requested here
        _to_global<T, numBits, qType, unroll, threads>(
        ^
csrc/quantization/dequantize.hip:20:17: note: in instantiation of function template specialization 'dequantize::to_global<__half, 8, quantize::Type::Symmetric, 8, 512>' requested here
    dequantize::to_global<T, numBits, qType, unroll, threads>(
                ^
csrc/quantization/dequantize.hip:48:9: note: in instantiation of function template specialization 'dequantize_kernel<__half, 8, quantize::Type::Symmetric, 8, 512>' requested here
        LAUNCH_DEQUANT_KERNEL(8, quantize::Type::Symmetric);
        ^
csrc/quantization/dequantize.hip:25:25: note: expanded from macro 'LAUNCH_DEQUANT_KERNEL'
   hipLaunchKernelGGL(( dequantize_kernel<T, num_bits, q_type, unroll, threads>), dim3(grid), dim3(block), 0, stream,  \
                        ^
In file included from csrc/quantization/dequantize.hip:8:
In file included from csrc/includes/dequantization_utils_hip.h:7:
In file included from csrc/includes/conversion_utils_hip.h:9:
In file included from csrc/includes/ds_kernel_utils_hip.h:24:
In file included from /opt/rocm-5.7.1/include/hip/hip_cooperative_groups.h:38:
/opt/rocm-5.7.1/include/hip/amd_detail/amd_hip_cooperative_groups.h:814:9: error: type 'impl::thread_block_tile_internal<64U, void>' is not a direct or virtual base of 'cooperative_groups::thread_block_tile<64>'
      : impl::thread_block_tile_internal<size, void>(g) {}
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/rocm-5.7.1/include/hip/amd_detail/amd_hip_cooperative_groups.h:801:12: note: in instantiation of function template specialization 'cooperative_groups::thread_block_tile<64>::thread_block_tile<cooperative_groups::thread_block>' requested here
    return thread_block_tile<size, void>(*this);
           ^
csrc/includes/dequantization_utils_hip.h:101:48: note: in instantiation of member function 'cooperative_groups::thread_block_tile<64, cooperative_groups::thread_block>::operator thread_block_tile' requested here
    cg::thread_block_tile<hw_warp_size> warp = cg::tiled_partition<hw_warp_size>(tb);
                                               ^
csrc/includes/dequantization_utils_hip.h:168:9: note: in instantiation of function template specialization 'dequantize::_to_global<__half, 8, quantize::Type::Symmetric, 8, 512>' requested here
        _to_global<T, numBits, qType, unroll, threads>(
        ^
csrc/quantization/dequantize.hip:20:17: note: in instantiation of function template specialization 'dequantize::to_global<__half, 8, quantize::Type::Symmetric, 8, 512>' requested here
    dequantize::to_global<T, numBits, qType, unroll, threads>(
                ^
csrc/quantization/dequantize.hip:48:9: note: in instantiation of function template specialization 'dequantize_kernel<__half, 8, quantize::Type::Symmetric, 8, 512>' requested here
        LAUNCH_DEQUANT_KERNEL(8, quantize::Type::Symmetric);
        ^
csrc/quantization/dequantize.hip:25:25: note: expanded from macro 'LAUNCH_DEQUANT_KERNEL'
   hipLaunchKernelGGL(( dequantize_kernel<T, num_bits, q_type, unroll, threads>), dim3(grid), dim3(block), 0, stream,  \
                        ^
16 errors generated when compiling for gfx1030.
error: command '/opt/rocm-5.7.1/bin/hipcc' failed with exit code 1

Hi @ahmedashraf093 - are you able to build with DS_BUILD_OPS=0 first?  If so, could you help narrow down what op is failing?   I believe you may also need to disable the DS_BUILD_QUANTIZER op.  Could you also share your DeepSpeed git tag that you are building from, or latest source?

@ahmedashraf093 , could you please let us know the image you are using?

@rraminen I'm running it on my machine directly.
====
python 3.10
====
conda 23.5.2
=======
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.6 LTS
Release:        20.04
Codename:       focal

@ahmedashraf093 - I believe pre-compiling those two ops are not supported yet on ROCm - so this is a feature that we are still working on.  Everything else works but not those I believe - @rraminen or @jithunnair-amd to confirm?

quantizer, random_ltd  and transformer_inference  extensions are not supported on ROCm yet.


Cleanup stale port docs

The option to change a port is no longer displayed in the dev menu.
We don't need to call out specific apps that use port 8081.
People can now use React DevTools to debug on Chrome.

People can now use React DevTools to debug on Chrome.

This is not exactly right. They can do so — but not from the Chrome extension.


Any update on DX12 and Vulkan support

We're currently working on RHI support which will bring with it DX12 and Vulkan. No ETA but it is in progress.


Update tiled to 1.1.2

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

The website ( http://www.mapeditor.org/ ) says 1.1.1, but I don't think it's been updated because the github release has 1.1.2 ( https://github.com/bjorn/tiled/releases ) from 2 days ago.


HTML hidpi mouse scaling issue (with fix)

When manually setting scaleFactor to 1 on a hidpi device (MacBook Pro Retina 2015), mouse input coordinates become broken. I found the reason for this in HtmlGraphics:
mouseScale = config.scaleFactor / HtmlPlatform.devicePixelRatio();
disabling this workaround (and setting mouseScale to 1) actually fixes my issue. However my game is using a custom scaling method to always fully occupy the available window/space so I'm not sure if that intereferes with this workaround.
If I don't change scaleFactor and leave it on its local default value of 2, then I have no problem with mouse coordinates.
Based on this it seems to me that this mouseScale workaround is unnecessary.
Tested on Google Chrome and Safari.

Looking more deeply into the HiDPI support on the HTML backend, it's not doing what I intended, which is probably why it's broken.
If you are running on a HiDPI display that uses 2 real pixels for every "logical" pixel, then the default scale factor is 2.  But that's not what the HTML backend is doing right now. Instead it's just shrinking the framebuffer and then the web browser scales up that small framebuffer to fill the whole space and everything is blurry.
So I'll fix the HTML backend to do the "right" thing, and then maybe you can let me know if I've totally broken your use case. :)

OK, I pushed the fix to the HTML backend. So now if you set scaleFactor to 1 in your HtmlPlatform.Config you get 1 logical pixel for 1 physical pixel (everything will look really small). The mouse scaling is necessary because in that mode, we're now "undoing" the HiDPI scaling that the browser naturally does.
Anyhow, give it a whirl and let me know if things make sense in this new setup. This should now mirror the behavior that would happen if you ran your game on the iOS backend and manually set the scaleFactor to 1.
I'm going to reintroduce a scale factor override to the Java backend (it now does the right thing with HiDPI displays by default but doesn't support overriding the scale factor), so then you should be able to see things behave the same way on Java, iOS and HTML when running on a Retina MacBook Pro.

Oh, looking at the iOS backend, it looks like I nixed custom scale factor setting there too. It does get complicated to juggle the device scale factor and user scale factor along with all of the different things that each platform does to try to "hide" all the scale factor stuff from you. But I'll try to get that working too, so that we can test a "just give me all the pixels" mode on all the platforms that should ostensibly support it.

Hi, thanks for the update.
I originally wanted to change the scale factor for two reasons (both on hidpi devices):

all textures created were 4x the size for no good reason (if the original image is the same size, upscaling it and putting it into a higher res texture seems pointless)
rendering was slow on my MBP and the reason seemed to be fillrate related

In the previous versions, changing scaleFactor to 1 (and changing the mouse scale factor) fixed both of these (although you may not consider lower res rendering a fix, it solved the performance issue and the game looks fine regardless).
In the current version setting scaleFactor to 1 solves the texture size issue, but not the rendering/framebuffer size issue.
So I guess at this point I'm looking for a way to forcibly downscale the game's backing framebuffer to make rendering faster. Is there a way to do this?

There isn't, but I can add it. More complexity! I'll look into how to do it without making things even more crazily complicated.

Thank you! I am grateful for you maintaining this project, it's an awesome tool. Since the last version of scaleFactor did exactly this, I'm hoping this is possible to implement as a small change :)

OK, I added another configuration to HtmlPlatform.Config: frameBufferPixelRatio. By default that and scaleFactor are set to whatever the browser reports for the device pixel ratio (2 on HiDPI displays, 1 on normal displays).
You can change scaleFactor to 1 and leave frameBufferPixelRatio at the default to get a "raw" display where you get all the pixels and do what you want with them. Or you can set both of them to 1 to get a "normal" DPI display on both normal and HiDPI screens. On a HiDPI screen, the "normal" DPI frame buffer will be scaled up automatically by the web browser to fill the expected space, so it might be blurry, but it will use 1/4th the pixels.

I'll look into replicating this level of control on the Java and iOS backends at some point.


Add files via upload

@ajithgk This domain is blacklisted because the college allows to register an email address there even if you are not a student of the college. If you are the student of this college, please apply with official document ("OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students).


⚠ Samsung has degraded performance

In 634b4f1, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2385 ms

Resolved: Samsung performance has improved in f92f875.