terraform plan error : command command "sh" produced invalid JSON: unexpected end of JSON input

Issue Report Template
Tectonic Version
Environment
Bare/metal - vmware
Expected Behavior
terraform plan should run without errors
Actual Behavior
fails with unexpected error.
When run from another OS (ubuntu), this error is not present with the same terraform.tfvars file
Reproduction Steps

Generate tfvars file
Run terrarforms plan against this file.

Other Information
Content of tfvars file :
{   "tectonic_admin_email"<EMAIL_ADDRESS>  "tectonic_admin_password": "blahblah",   "tectonic_base_domain": "unused",   "tectonic_cluster_cidr": "<IP_ADDRESS>/22",   "tectonic_cluster_name": "nrb",   "tectonic_container_linux_version": "1632.3.0",   "tectonic_dns_name": "",   "tectonic_kube_apiserver_service_ip": "<IP_ADDRESS>",   "tectonic_kube_dns_service_ip": "<IP_ADDRESS>",   "tectonic_kube_etcd_service_ip": "<IP_ADDRESS>",   "tectonic_license_path": "./license.txt",   "tectonic_metal_controller_domain": "coreosmaster.bbb.com",   "tectonic_metal_controller_domains": [     "aaa.bbb.com"   ],   "tectonic_metal_controller_macs": [     "00:50:56:89:xx:xx"   ],   "tectonic_metal_controller_names": [     "aaa"   ],   "tectonic_metal_ingress_domain": "coreosworkers.bbb.com",   "tectonic_metal_matchbox_ca": "-----BEGIN END CERTIFICATE-----",   "tectonic_metal_matchbox_client_cert": "-----BEGIN -----END CERTIFICATE-----\n",   "tectonic_metal_matchbox_client_key": "-----BEGIN END RSA PRIVATE KEY-----\n",   "tectonic_metal_matchbox_http_url": "http://xxx.bbb.com:8080",   "tectonic_metal_matchbox_rpc_endpoint": "xxx.bbb.com:8081",   "tectonic_metal_worker_domains": [     "aaa.bbb.com",     "bbb.bbb.com",     "ccc.bbb.com"   ],   "tectonic_metal_worker_macs": [     "00:50:56:89:xx:xx",     "00:50:56:89:yy:yy",     "00:50:56:89:zz:zz"   ],   "tectonic_metal_worker_names": [     "aaa",     "bbb",     "ccc"   ],   "tectonic_pull_secret_path": "./pull_secret.json",   "tectonic_service_cidr": "<IP_ADDRESS>/24",   "tectonic_ssh_authorized_key": "ssh-dss " }

Error at the console :
Error refreshing state: 1 error(s) occurred:

module.container_linux.data.external.version: 1 error(s) occurred:

module.container_linux.data.external.version: data.external.version: command "sh" produced invalid JSON: unexpected end of JSON input

You mentioned:

When run from another OS (ubuntu), this error is not present with the same terraform.tfvars file
What is the problematic OS?

Hi, the error is appearing on RHEL 7
I ran terraform on my ubuntu workstation, it's working fine, but when my
VMs boots, they don't find the ipxe.boot file.
So I tought that the problem was maybe that it should run on the same
machine as the matchbox installation, but I'm unable to launch terraform on
this machine due to the mentioned error.
On Tue, Feb 27, 2018 at 4:58 PM, Lucas Servén<EMAIL_ADDRESS>wrote:

You mentioned:
When run from another OS (ubuntu), this error is not present with the same
terraform.tfvars file
What is the problematic OS?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/coreos/tectonic-forum/issues/280#issuecomment-368927272,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AeabyslyrYAApHAME5CeZ2gGbVPHY63oks5tZCYkgaJpZM4SVLR8
.

please note that the module that is failing assumes curl and sed are installed on your host. Does your RHEL box include those packages?

Yes it does.
We are working with various proxies, the one on my workstation is not the
same as the one on the server.
Does this step needs an internet connexion ?
Same for the final process, how is the boot.ipxe provisionned ? is it
provisionned through matchbox if the mac address resquesting is in the
provisionned list, with a link from the assets ?
Or does it needs to be downloaded from internet dynamically ?
[root@ ~]# rpm -qa | grep -E "sed|curl"
sed-4.2.2-5.el7.x86_64
libcurl-7.29.0-42.el7_4.1.x86_64
python-pycurl-7.19.0-19.el7.x86_64
curl-7.29.0-42.el7_4.1.x86_64
On Wed, Feb 28, 2018 at 8:47 AM, Lucas Servén<EMAIL_ADDRESS>wrote:

please note that the module that is failing assumes curl and sed are
installed on your host. Does your RHEL box include those packages?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/coreos/tectonic-forum/issues/280#issuecomment-369149738,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AeabytV9ZpKkGKfha_IWUCy4M_1-g5uYks5tZQR7gaJpZM4SVLR8
.

@oroomans yes, the Terraform step requires a connection to the internet by default in order to determine the latest Container Linux version to select. You can side step this by explicitly declaring the Container Linux channel and version to install. https://github.com/coreos/tectonic-installer/blob/master/config.tf#L282-L302
The serving of all other assets depends on your configuration. If you are using the default Matchbox devnet scripts to run Matchbox and DNSmasq then iPXE (to bootstrap PXE machines) will be served directly by DNSmasq as it is included in that container. The iPXE embedded scripts will be served statically by Matchbox. Note that the nodes will have to download Container Linux images to be able to boot and several containers for Kubernetes so these nodes should have access to the internet. A completely offline Tectonic install is outside of the scope requires more components.

Thanks.
I actually did the bare metal install from this link for matchbox :
https://coreos.com/matchbox/docs/latest/deployment.html.
I also did a dnsmasq config, for pxe,tftp and dhcp.
I actually did specify the version and downloaded it with coreos-get
script, and put it in the matchbox folder as described in the same doc.
If I  understand well the process, the nodes should provisionned the os
trough the pxe, then they will download all their content (containers etc)
from internet ?
Is there a way to make this work with a proxy config or do they require
direct internet access ?
Thanks.
On Wed, Feb 28, 2018 at 9:36 AM, Lucas Servén<EMAIL_ADDRESS>wrote:

@oroomans https://github.com/oroomans yes, the Terraform step requires
a connection to the internet by default in order to determine the latest
Container Linux version to select. You can side step this by explicitly
declaring the Container Linux channel and version to install.
https://github.com/coreos/tectonic-installer/blob/
master/config.tf#L282-L302
The serving of all other assets depends on your configuration. If you are
using the default Matchbox devnet scripts to run Matchbox and DNSmasq then
iPXE (to bootstrap PXE machines) will be served directly by DNSmasq as it
is included in that container. The iPXE embedded scripts will be served
statically by Matchbox. Note that the nodes will have to download Container
Linux images to be able to boot and several containers for Kubernetes so
these nodes should have access to the internet. A completely offline
Tectonic install is outside of the scope requires more components.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/coreos/tectonic-forum/issues/280#issuecomment-369160380,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AeabygHIa40Aa9DDc8FtKxqOXoPcq0Bsks5tZQ_1gaJpZM4SVLR8
.

It does not matter that you already downloaded the Container Linux image for Matchbox; Terraform has no idea about that. The reason you are getting that module error is because Terraform is trying to determine the latest available Container Linux version because it defaults to latest but this HTTP request is failing. If you specify the version and channel in your tfvars then you will no longer see that error.
A complete offline install is more involved and requires you to prefetch all required containers and serve them from a caching proxy, e.g. squid. This is out of the scope of this issue.

That's exactly what I have done in the tfvars :
[root@ tectonic_1.8.4-tectonic.3]# cat build/nrb/terraform.tfvars | grep -E
"stable|version"
"tectonic_container_linux_version": "1632.3.0",
"tectonic_container_linux_channel": "stable",
but the problem still persists.
On Wed, Feb 28, 2018 at 10:13 AM, Lucas Servén<EMAIL_ADDRESS>wrote:

It does not matter that you already downloaded the Container Linux image
for Matchbox; Terraform has no idea about that. The reason you are getting
that module error is because Terraform is trying to determine the latest
available Container Linux version because it defaults to latest but this
HTTP request is failing. If you specify the version and channel in your
tfvars then you will no longer see that error.
A complete offline install is more involved and requires you to prefetch
all required containers and serve them from a caching proxy, e.g. squid.
This is out of the scope of this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/coreos/tectonic-forum/issues/280#issuecomment-369170273,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AeabyvS4dYjb2aU6cajFfnpt3IrplnLDks5tZRiwgaJpZM4SVLR8
.

Yes you’re right; looking at it again I am realizing that because Terraform always evaluates both sides of a ternary expression, the HTTP request will be made regardless. I will submit a PR to modify the module so that we can avoid the request by specifying the versions explicitly. For the time being, the Terraform step of the installer must be run from a machine will outbound internet access.

Ok thanks.
For the pxe part I will try with the container that you provide for this if
possible, to see if this works for the provisionning, as I can run the
terraform from my workstation from now.
On Wed, Feb 28, 2018 at 10:31 AM, Lucas Servén<EMAIL_ADDRESS>wrote:

Yes you’re right; looking at it again I am realizing that because
Terraform always evaluates both sides of a ternary expression, the HTTP
request will be made regardless. I will submit a PR to modify the module so
that we can avoid the request by specifying the versions explicitly. For
the time being, the Terraform step of the installer must be run from a
machine will outbound internet access.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/coreos/tectonic-forum/issues/280#issuecomment-369177251,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AeabyvzHNDcWvIKnRYvJM0lCwaht-OfCks5tZRzTgaJpZM4SVLR8
.

I am trying to install tectonic on aws from ubuntu 14.04. I am getting same kind of error, which I have give below; any help???

LTSmodule.container_linux.data.external.version: data.external.version: command "sh" produced invalid JSON: unexpected end of JSON input


Get feature weights

Hi,
Thanks for sharing this wonderful repository.
I was just wondering if there exists any API or function call which can give me coefficients/importance of features generated by LIME for the local surrogate model.
Thanks!

explanation.as_list, or explanation.as_map

Thanks @marcotcr
That's what I am looking for!


change redis database to string type in readme

https://github.com/bahung1221/cache-all/blob/243249d1e9e4f2f48460921ba78e8de1b81febb2/index.d.ts

Thank you so much 😄


feat: Re-enable the backup process on Android

Hi everyone!
I don't know why, but all the backup process on Android was disabled.
This PR re-enables it + add some missing files.

Being in the backup xml would explain (maybe) why the product hive table was needed even when not anymore in the code?

Being in the backup xml would explain (maybe) why the product hive table was needed even when not anymore in the code?

I'm pretty sure, that is not the case, because when we want to open a Box, this a Future mechanism, meaning it's not already opened. And if it's not opened, the adapter is not called.
So the question is: who opens ID 33 🕵♂

I'm pretty sure, that is not the case, because when we want to open a Box, this a Future mechanism, meaning it's not already opened. And if it's not opened, the adapter is not called.
So the question is: who opens ID 33 🕵♂

@g123k I don't understand your point about Future.
My answer is: we don't open ID 33, but very probably google backup system needs to open a database it's supposed to back up, in order to copy or compare data.

I'm pretty sure, that is not the case, because when we want to open a Box, this a Future mechanism, meaning it's not already opened. And if it's not opened, the adapter is not called.
So the question is: who opens ID 33 🕵♂

@g123k I don't understand your point about Future. My answer is: we don't open ID 33, but very probably google backup system needs to open a database it's supposed to back up, in order to copy or compare data.

No for Google, this is just a very basic copy/paste of raw files.
If the size or date is different, it we will be saved.


Add ppa:raphink/augeas

That is great. Would it be possible to add the "releases" repositories, too?
https://launchpad.net/~raphink
This would allow to test against specific versions of the library.

@emdantrim See for example https://github.com/hercules-team/augeasproviders_shellvar/blob/master/.travis.sh


ParamOverrides: create overrides attr?

Converted from SourceForge issue 2888861, submitted by ceball
Submit Date: 2009-10-29 15:43 GMT
set e.g. .overrides on Parameterized instance, and override getattribute to look in .overrides first; would have to set .overrides=None after call. Or something like that.

I suppose we could do it with a decorator...
class Fn(param.ParameterizedFunction):
    x = param.Number(1)

    def __call__(self,**params):
        p = ParamOverrides(self,params)
        return p.x

could become
class Fn(param.ParameterizedFunction):
    x = param.Number(1)

    @add_overrides
    def __call__(self,**params):
        return self._overrides.x

In some future less polluting api (#154) that might be self.params.overrides.x or something.

I added in #92:
class A2(param.Parameterized):
    path = param.Path(search_paths=['/etc'])
    @overrides
    def __call__(self,**params):
        return self._overrides.path

a2 = A2(path=test_file)
assert a2() == test_path+test_file, a2()
assert a2(path=test_file) == test_path+test_file, a2(path=test_file)

What do people think?

Personally, I prefer the explicit use of ParamOverrides instead of introducing a decorator...

Same; decorator doesn't seem like an improvement.

Not adding this feature

Jim? Are you still logged in as sf-issues?!

Yep, that's me!


Winston on CLI

as a developer I would like to be able to tune the verbosity of my logs

Log Levels

Debug

Verbose

Info

Warn

Error

Default to Info level

Toggle it on the CLI with options like

--info --i

--verbose --v

etc

Todo: Identify what logging things we want to classify at what level,

The easiest way to do this, and avoid checking for mutually exclusive flags (with yargs) is to use multiple -v flags, like some other UNIX commands.
Example:

clusternator defaults to info logging
clusternator -v specifies verbose logging
clusternator -vv specifies debug logging
clusternator -vvv specifies "silly" logging (silly is a Winston term)
clusternator -q specifies errors only
clusternator -q -v -q takes precedence over -v's


[BUG] The images on the Send/Receive completed popup on the Android app  are different than on the web app

Pre-conditions:

The user is logged in
The user has different types of txs cards

Steps to reproduce:

Launch the app
Tap on the Send/Receive Completed card
Pay attention to the image on the opened popup

Actual result: The images on the Send/Receive completed popup on the Android app  are different than on the web app
Expected result: The images on the Send/Receive completed popup on the Android app  should be the same as on the web app
Environment:
Android App [staging] 1.25.1-24 (1558)
QA 1.25.1-24
Device:
Samsung Galaxy S10 / Android 9
Xiaomi Mi 8 / Android 9
Windows 10 // Google Chrome v90
Attachment:
https://www.screencast.com/t/BZ5kAcTVrZyS

@lkilaszewski  @serdiukov-o-nordwhale
The issue is reproduced on the mobile QA. The image on the Send completed popup on the Android app is different than on the web app.
Environment:
Android App [staging] 1.29.1-3 (1704)
QA 1.29.1-3
Device:
Samsung Galaxy A80 // Android 10
Windows 10 // Google Chrome v91
Attachments:
https://www.screencast.com/t/kidMPHMh36t - Recieve is correct
https://www.screencast.com/t/UAfhGLoTk3xt - Send is wrong

@lkilaszewski @serdiukov-o-nordwhale
The issue is not reproduced on the mobile QA. The images on the Send/Receive completed popup on the Android app are the same as on the web app.
Environment:
Android App [staging] 1.29.1-4 (1709)
QA 1.29.1-4
Devices:
Tablet Lenovo TB-X306X (1280x800) // Android 10
Samsung Galaxy A80 // Android 10
Windows 10 // Google Chrome v91
Attachment:
https://www.screencast.com/t/uTn6BvUncb - tablet
https://www.screencast.com/t/4m17eF0e - mobile

@lkilaszewski @serdiukov-o-nordwhale
The issue is not reproduced on the mobile PROD. The images on the Send/Receive completed popup on the Android app are the same as on the web app.
Environment:
Android App [production] 1.30.0 (1744)
Prod 1.30.0
Devices:
Samsung Galaxy A80 // Android 10
Windows 10 // Google Chrome v91
Attachments:
https://www.screencast.com/t/JvnPQManK


Possible enhancement: Git integration

Any thought to integrating in github/gitlab for world backups?  Basically pass in a few variables to reflect the git repo you want snapshots uploaded to, then on scheduled backup run an additional command to upload that backup to git.  On the reverse side adding a variable where you can tell via the docker-compose to pull down the last backup and restore?

Yeah, that’s a cool idea. Similarly I have used this recently backup DB snapshots to cloud storage
https://rclone.org/

As this is docker land, should a backup service run in a separate container with access to the minecraft volume?

I've seen one example run a 'side car' backup container that was able to issue commands one by one to minecraft servers, suspending save operations before backup.


unit test failing with recent Rust version

I wonder if this unit test used to work but more recent rust versions were able to squeeze 8 bytes out of the struct or if the struct has changed but the unit test was no longer being run?
It was a little too hard given the cap file name for me to try to build with older commit versions. So I'll just put this out there and you can try on your system.
I needed to adjust the unit test like so.
diff --git a/src/pact.rs b/src/pact.rs
index 2c015d4..3902142 100644
--- a/src/pact.rs
+++ b/src/pact.rs
@@ -392,13 +392,13 @@ mod tests {
     #[test]
     fn branch_size() {
         assert_eq!(mem::size_of::<ByteTable4<Head<64, IdentityOrder>>>(), 64);
-        assert_eq!(mem::size_of::<BranchBody4<64, IdentityOrder>>(), 64 * 3);
-        assert_eq!(mem::size_of::<BranchBody8<64, IdentityOrder>>(), 64 * 4);
-        assert_eq!(mem::size_of::<BranchBody16<64, IdentityOrder>>(), 64 * 6);
-        assert_eq!(mem::size_of::<BranchBody32<64, IdentityOrder>>(), 64 * 10);
-        assert_eq!(mem::size_of::<BranchBody64<64, IdentityOrder>>(), 64 * 18);
-        assert_eq!(mem::size_of::<BranchBody128<64, IdentityOrder>>(), 64 * 34);
-        assert_eq!(mem::size_of::<BranchBody256<64, IdentityOrder>>(), 64 * 66);
+        assert_eq!(mem::size_of::<BranchBody4<64, IdentityOrder>>(), 64 * 3 - 8);
+        assert_eq!(mem::size_of::<BranchBody8<64, IdentityOrder>>(), 64 * 4 - 8);
+        assert_eq!(mem::size_of::<BranchBody16<64, IdentityOrder>>(), 64 * 6 - 8);
+        assert_eq!(mem::size_of::<BranchBody32<64, IdentityOrder>>(), 64 * 10 - 8);
+        assert_eq!(mem::size_of::<BranchBody64<64, IdentityOrder>>(), 64 * 18 - 8);
+        assert_eq!(mem::size_of::<BranchBody128<64, IdentityOrder>>(), 64 * 34 - 8);
+        assert_eq!(mem::size_of::<BranchBody256<64, IdentityOrder>>(), 64 * 66 - 8);
     }

     proptest! {

Interesting 🤔, could you give me the rust version and arch of your system?

cargo 1.67.1 (8ecd4f20a 2023-01-10)
arch is x86_64

Thanks! This looks like it's related to the architecture, as it works on my stable-aarch64-apple-darwin with rustc 1.67.1 (d5a82bbd2 2023-02-07).
I'm gonna investigate this with MIRI!

Interesting. I suspect the sizes are a little important because of the union and wanting to be sure everything is where it is expected to be but maybe the test should just be disabled? Or whatever size the first one comes up with, the same kind of offset could be required of the rest.

Well the test did what it was meant to do, detect weird size changes in the struct 😅.
It's mostly a sanity check that all the alignments work out, the BranchBody is essentially one (64byte) cache-line of node metadata, one cache-line of a key used for path compression in the trie, and then the hash table where each bucket corresponds to another cache-line.
If the head gets bigger or smaller (as seems to be the case here) then the assumption in the hash table, that iterating over a single bucket is cheap, no longer holds, because the buckets now get pushed across cache lines.

Nice. The test did what it was deigned to do. Glad I could help - totally by accident of course and without knowing what I was seeing. Congrats for digging into what many would have thought an anomaly.

Does this mean the 64 byte parts are not currently cache aligned?

Yeah, that is what it looks like. The buckets themselves don't enforce any alignment, so my guess is that they're currently not well aligned.
They should probably aligned regardless of the context they are used in, and just force some padding bytes as a fallback.

See #4


A&R-> The subArea name go missing when navigating between the facility edit forms.

This issue is part of the ticket: https://github.com/bcgov/bcparks-ar-admin/issues/255
Scenario:

navigate to the A&R on TEST: https://d3ahrzu0mpndj3.cloudfront.net/enter-data?date=202403
Navigate to the Enter data page
Select a Month/Year, a park and a Sub Area with multiple facilities.
Open a facility to edit, now Cancel the edit and select the Discard changes to confirm it.
Open another facility in edit mode.
Check if the sub area is displayed.

Issue:

The sub area name is missing on the facility opened next.

https://github.com/bcgov/bcparks-ar-admin/assets/65190263/edea6bd2-962e-4c37-ac8f-9992800fd2db

Fixed in https://github.com/bcgov/bcparks-ar-admin/pull/320

@manuji I found an additional case where this is occurring and fixed it in #321

Tested on TEST: Passed

Verified that this issue has been fixed.

Thanks @cameronpettit


style: use ellipsis for empty strings

I think it looks nice to have "…" instead of just an empty strings in the example responses. But just for the responses, not for the request bodies.
And the helper generates example request and response bodies. I renamed it: generateResponseContent -> getExampleFromSchema

Yo this looks great


Restart pod when deploying with changes to configmap.yaml

It seemed rude to bump the chart version number unless you think it's appropriate that each change would just be a new release. Maybe that's not so crazy. 🤷

As I understand it, that's best-practice, so go ahead and bump the chart (semver) version for each change ;)

Bumped the chart version. Since you already have two branches going effectively I did the later one. Should I make the PR against your personal repository instead?

ah, never mind. Here's a clean version against the org version. :-)

Thanks @abh ... Since I started using flux to manage my deployments, I'm no longer a fan of the checksum-based approach, since when certain automation (like flux) is used, it generates unnecessary deployment restarts (see https://github.com/minio/minio/pull/14396 for a similar issue).
I'd rather support the ability of the operator to specify custom deployment annotations (see deployment.annotations), and then rely on something like https://github.com/stakater/Reloader to trigger the deployment restarts. Perhaps adding this to the existing documentation could be a new repo issue?
Cheers!
D


SARAALERT-1551: capitalizes "Head of Household" in patient minor notification.

Description
Jira Ticket: SARAALERT-1551
"Head of Household" is capitalized elsewhere in the patient view but not in the notification that a patient is a minor. This capitalizes the phrase in the notification to ensure it remains consistent.
(Bugfix) How to Replicate
Navigate to a patient record where the patient is a minor on another branch. The text should not capitalize "head of household" in the notification under the Contact Info Session.
(Bugfix) Solution
Changes the text in patient.js to capitalize "Head of Household"
Important Changes
Please list important files (meaning substantial or integral to the PR) along with a list of the general changes that should be highlighted for reviewers.
app/javascript/components/patient/Patient.js
Testing Recommendations
Checklists
Submitter:

[x] This PR describes why these changes were made.
[x] This PR is into the correct branch.
[x] This PR includes the correct JIRA ticket reference.
[x] Comment added to the relevant JIRA ticket(s) with a link to this PR
[x] Code diff has been reviewed (it does not contain: additional white space, not applicable code changes, debug statements, etc.)
[x] If UI changes have been made, Chrome Dev Tools Lighthouse accessibility test has been executed to ensure no 508 issues were introduced.
[x] Tests are included and test edge cases
[x] Tests have been run locally and pass (remember to update Gemfile when applicable)
[x] Test fixtures updated and documented as necessary

@sgober  :

[x] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[x] The tests appropriately test the new code, including edge cases
[x] You have tried to break the code
[ ] If applicable, you have tested changes against a large database, and considered possible performance regressions
[x] Tested all recommendations listed in the "Testing Recommendations" section. The application behaves as expected with this PR.

@ :

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code
[ ] If applicable, you have tested changes against a large database, and considered possible performance regressions
[ ] Tested all recommendations listed in the "Testing Recommendations" section. The application behaves as expected with this PR.

@ :

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code
[ ] If applicable, you have tested changes against a large database, and considered possible performance regressions
[ ] Tested all recommendations listed in the "Testing Recommendations" section. The application behaves as expected with this PR.

Any chance we can add a space between the : and the HoH name? I've left suggestions for it. Really small change, but it should be there.

Absolutely, I'll ping you


Prop completion does not work for <NuxtPage>

Environment
- Operating System: `Windows_NT`
- Node Version:     `v18.12.1`
- Nuxt Version:     `3.0.0`
- Nitro Version:    `1.0.0`
- Package Manager<EMAIL_ADDRESS>- Builder:          `vite`
- User Config:      `typescript`
- Runtime Modules:  `-`
- Build Modules:    `-`

Reproduction
https://stackblitz.com/edit/github-lbhhuu?file=app.vue
(Since this issue is related to autocomplete behavior, I originally reproduced it in VS Code)
Describe the bug
<NuxtPage>'s props does not appear to be detectable by IDEs such as VS Code. For example, pageKey is valid prop for <NuxtPage> but does not show up under completion menu.

Additional context
I've tried switching between Volar's Take Over Mode and TypeScript Vue Plugin, along with re-enabling the shim in nuxt.config.ts, but could not resolve this issue.
Logs
No response

Seems to also be an issue on <ClientOnly>.
<Teleport>,<NuxtLoadingIndicator>,<NuxtLayout>,<NuxtLink> all seem to have working auto complete in my IDE.

Is this fixed by https://github.com/nuxt/framework/pull/9204?

Yes, this should be resolved in the edge channel, or in the next release.
Let me know if not and I'll reopen.

I created a project using the edge channel and the issue appears to still be present.
- Operating System: `Windows_NT`
- Node Version:     `v18.13.0`
- Nuxt Version:     `3.0.1-rc.0-27909450.eac787e`
- Nitro Version:    `2.0.0-27909319.113d31e`
- Package Manager<EMAIL_ADDRESS>- Builder:          `vite`
- User Config:      `-`
- Runtime Modules:  `-`
- Build Modules:    `-`


stonith-timeout check mismatch with docs

Hello.
Cluster param: "stonith-timeout" in the docs here:  https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/high-availability-guide-suse-pacemaker
Is suggesting 900s.
In the qualitycheck v2 it is looking for 144s.
As a side note, the crm command can be used to check the value like so:  crm configure get_property stonith-timeout
Darryl

you are correct, there are actually two values documented.
for SBD it is 144s
for Fencing Agent it is 900
I will split the check into SBD and fencing

updated and split SBD and FencingAgent check


Update image src to use path relative to current page

Some of the images in the documentation do not appear because
the img src references the root context, which happens when the
documentation website is hosted on GitHub due to the project
prefix ("Hygieia").
This removes the root prefix ("/") for the affected images.

thanks @uncompiled we don't see images missing in our setup. can you provide some scree shots on what was missing and what was fixed.

No problem!
The documentation pages with missing images are:

http://www.capitalone.io/Hygieia/ui.html
http://www.capitalone.io/Hygieia/chatops_collector.html
http://www.capitalone.io/Hygieia/plugin_webhook.html

Screenshots attached:

You can see the changes on my local fork:

https://uncompiled.github.io/Hygieia/ui.html
https://uncompiled.github.io/Hygieia/chatops_collector.html
https://uncompiled.github.io/Hygieia/plugin_webhook.html

LGTM

LGTM

Thanks @uncompiled


Ensure libvirt manager layout is consistent

This change enforces cifmw_libvirt_manager_configuration as a single source and is consistent. It removes devscripts_layout that tends to change the precedence.
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

/test pre-commit

/approve


test if nest environment can be installed on a base rocker/r-base container

depends on #49

Pretty sure this will fail https://github.com/openpharma/staged.dependencies/issues/60#issuecomment-896632466 so this issue is to make it work...

This depends on PR #69.
Then, you can do the following to install NEST:
docker run \
--name rbaseDocker \
-d --rm \
rocker/r-base:4.1.1 tail -f /dev/null

docker exec -it rbaseDocker bash

apt-get update && apt-get install -y libxml2-dev libcurl4-openssl-dev libssl-dev libgit2-dev

docker exec -it rbaseDocker R

install.packages("remotes")
remotes::install_github("openpharma/staged.dependencies", ref = "46_installFromRemoteRepos")

Sys.setenv(GITHUB_PAT = "<TOKEN>")

staged.dependencies::install_deps(list(list(
  repo = "insightsengineering/utils.nest",
  host = "https://github.com"
)), feature = "main", direction = c("upstream", "downstream"), verbose = 2)


Electron app

[x] auth
[x] notifications
[x] linux build
[x] codesigning mac
[ ] codesigning windows
[x] icon looks bad on mac
[ ] distribution??
[x] singleton window
[x] fix clicking on game invite links navigates app
[ ] CI

layout issue with game header

[ ] issue: login success call doesn't refresh windows client

[ ] task: add "join in desktop" button to game invite screen

Windows code signing is like $200-300/year and isn't strictly required, so I think we're going to skip it for now

we're live on itch and github releases!


When can we expect support for AndroidX

As android has moved on to AndroidX. Old libraries that do not support AndroidX require an extra step during compilation - Jetifier.

Jetifier tool migrates support-library-dependent libraries to rely on the equivalent AndroidX packages instead. The tool lets you migrate an individual library directly, instead of using the Android gradle plugin bundled with Android Studio.

Jetifier takes extra time during compilation. Making it slow.
Most of the libraries have already moved on to AndroidX. But I can't remove Jetifier until and unless all libraries in my project have support for AndroidX.
When can we expect AndroidX support?

Hey @rishabh876 This is planned to be taken up soon. Will update here.


feat(applauncher): add button and div examples

closes #1944
@mcoker @mattnolting what do you guys think about showing a <div> as an example in the menu. Do you know if thats a common case? I don't think we do it in the dropdown.

Deploy preview for pf-next ready!
Built with commit c60a811cebe8a5fc2becb19e1b64fccd0b351e9f
https://deploy-preview-2006--pf-next.netlify.com

@jschuler using a <div> instead of <button>, <a> or <input type="button"> seems inherently wrong to do. Also, I can't find any accessible examples of converting a <div> to an accessible, clickable object. Are you saying use <div> as a wrapper with a nested <a>? In this case, I think it may be ok to support wrapping in this way, but I'm hesitant to show this as an example in core..
@christiemolloy @mcoker @matthewcarleton thoughts?

@mattnolting I left a similar comment in the issue - https://github.com/patternfly/patternfly-next/issues/1944#issuecomment-507443506. I think it depends on how it renders and what classes are applied to what elements as to whether we can even support it currently and if it's something we should show in an example.

+1 on what @mattnolting is saying, it seems most reasonable to stick with just adding a button and dropping the div unless there's something I'm missing as a valid use case.

@mcoker  @mattnolting @matthewcarleton thanks for the input, I also agree with that. Updated

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Set exec bit for build script

Fixes #43

Ooops, did not notice lfs-image. Rebased with both scripts +x'ed

Thank you both!


Basic Export Forwaring

Resolves export forwards.

In Module's _parse_pe, if export points to .rdata store as an export forwarder (only caveat is x64 ntdll.dll's RtlNtdllName which is located in .rdata)
After all modules have been loaded in iterate over modules to then parse the export forwarders, this is done by overwriting the current export address with the resolved forward export's address
If we could not resolve the forwarder leave address to zero and assert we could not resolve the function within find_export

Currently does not resolve API sets, but we can cross that bridge later.

Awesome, thanks a ton!


Create textures and models for all blocks and add them without functionality

Create textures and models (If needed) for all these blocks and add them to the codebase without adding extra functionality for now. They just need to be placeable and breakable in creative mode.
Todo

[ ] Umbral Ore (Overlay for resonating state)
[ ] Deepslare Umbral Ore (Overlay for resonating state)
[ ] Block of Umbral
[ ] Darkdweller Root
[ ] Darkdweller Log
[ ] Darkdweller Stick
[ ] Darkdweller Planks
[ ] Darkdweller Slab
[ ] Darkdweller Stairs
[ ] Darkdweller Fence
[ ] Darkdweller Fence Gate
[ ] Darkdweller Door
[ ] Darkdweller Trapdoor
[ ] Darkdweller Button
[ ] Darkdweller Pressure Plate
[ ] Darkdweller Sign
[ ] Sculk Soil
[ ] Rooted Sculk Soil

In Progress

[ ] Darkdweller Bundle
[ ] Stripped Darkdweller Bundle

Finished

This issue is now obsolete and has been merged

#33
#34


Default service URL should be a global one

Describe the bug
The SDK needs to have a global default service URL of https://us.compliance.cloud.ibm.com. At the moment when a user is running the SDK using terraform they need to declare an endpoint called IBMCLOUD_SCC_ADMIN_API_ENDPOINT in order to run the SDK. This endpoint can vary based on regions but if this endpoint is not declared, the SDK defaults to https://admin-service-api.cloud.ibm.com which returns an error.
To Reproduce
Try running https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/scc_account_location without exporting the IBMCLOUD_SCC_ADMIN_API_ENDPOINT in your environment. You will get an error message as shown in the screenshot below
Expected behavior
The SDK should return the account location, locations, and location details
Screenshots

Must gather (please complete the following information):

SDK Version [1.3.4]
Go Version [e.g. 1.17.2]
Name of service that you're trying to use adminserviceapiv1
Name of operation that you're trying to invoke View locations

Additional context
Add any other context about the problem here.
Were you able to avoid the problem by changing your application code slightly?

Viewing the admin-service code, looks like the code was generated before adding the regional URLs in the API definition document. I'd check the document and it has the regional URLs listed, and looks good to me.
I'd suggest to regenerate the codebase using the latest version of openapi-sdkgen and see if the code has valid DefaultServiceURL and a valid function to get URL corresponding to different regions.

Default service URL is now updated, https://github.com/IBM/scc-go-sdk/blob/main/v3/adminserviceapiv1/admin_service_api_v1.go#L44
Closing this issue. Please feel free to re-open if the problem still persists.


fix(TransitionablePortal): fixed deprecated lifecycle method #2732

removed deprecated componentWillReceiveProps lifecycle

changed it to componentDidUpdate

changed test description to componentDidUpdate

it is worth mentioning that it is not advised to use getDerivedStateFromProps in this case due to the different time this hook is getting called in contrast to componentDidUpdate which also does not require change from any of the test

my circle ci checks are not working because i have setState in componentDidUpdate. I would like to know if this check is missused in the circleci checks or is there an actual reason for it. thanks from ahead.

See https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/no-did-update-set-state.md maybe as to why?

Oops, folks 😿 I missed that this PR exists...
I did an update in #3966 and you can check it if you're interested. In general when there is UNSAFE_componentWillReceiveProps that performs setState() it should be replaced with getDerivedStateFromProps() as otherwise componentDidUpdate() will cause double render.


[Feature Request] : Add Dark Mode toggle

Just as the title states. Sorry to bother vaiya if it was already implemented since i can't find it ;-;
I tried looking around but no avail.
Great job on the app btw, keep it up pls! Thank you for making it Open Sourced!
Hope you consider this feature request!

@NaiveInvestigator Thank you for the suggestion brother. Will try soon. @Tarikul-Islam-Anik Can you please help with this issue #7?

@mahadihassanriyadh Sure!

Closing the issue, the issues has been addressed and resolved through PR #8.
Thank you @NaiveInvestigator for raising the issue and @Tarikul-Islam-Anik for solving it.

minor nitpick, could we also make the app header change color when switching to dark mode?

@NaiveInvestigator Thanks for pointing this out. I'm guessing you're using it in PWA mode. If there's any possible solution for this, It'll be fixed by today.

@NaiveInvestigator I've tried every possible solution for fixing this.
Here's the preview link: https://chicken-coop-5c1vjhp29-mahadihassanriyadh.vercel.app/
Kindly check and let us know the results. If you still facing the issue, kindly share your browser name.

Sorry for the late reply :<< I was outside and just saw your message now.;-;

@NaiveInvestigator Thanks for pointing this out. I'm guessing you're using it in PWA mode. If there's any possible solution for this, then it'll be fixed by today.

I think im not using the PWA, this only happens if i use the  android app linked on the readme.
But I tried using "Add to home screen" of the webapp and it looks as in the screenshot below. So i think it is the apk issue rather than the web app itself. I think just removing the header altogether will be better. if ppl need to refresh we could pull down to refresh just like any browser.

@NaiveInvestigator I've tried every possible solution for fixing this. Here's the preview link: https://chicken-coop-5c1vjhp29-mahadihassanriyadh.vercel.app/ Kindly check and let us know the results. If you still facing the issue, kindly share your browser name.

Sorry but I couldn't try that link in the apk version so cant tell. But I opened it on the browser as the  "Add to home screen option" and it looks the same as below.
The apk im talking about is this btw
https://github.com/mahadihassanriyadh/chicken-coop/raw/main/Chicken-coop-app/apk file/chicken-coop.apk
As an aside I am willing to beta test updates on this project or any project that is related to BRACU. I can't code much so want to contribute in other ways. Just saying if u need lol.

@NaiveInvestigator Thanks for your feedback. I really appreciate your enthusiasm working BRACU related projects. You can try out the PWA version. Here's how you do it:

Visit https://chicken-coop.vercel.app/
Wait for 1-2 seconds for the install button to popup.
Tap on the button and you're ready to go!

Since the dark mode has been implemented, I'm closing this issue. If you encounter any further issues or have additional questions, please don't hesitate to open a new issue, and we'll be happy to assist you.
We appreciate your contribution to our project and your dedication to its improvement. Your feedback is invaluable in making our project better for everyone.
Have a great day! ⚡


Documentation and Examples Update for AgentM Python Migration

Overview
This issue focuses on updating the documentation and examples for the Python version of the AgentM library. The goal is to ensure that all documentation reflects the new Python implementation and provides clear, accurate information for users and contributors.
Tasks

[ ] Update Documentation

[ ] Revise all documentation to reflect the Python implementation, including updated function signatures and usage examples.
[ ] Ensure all docstrings in the Python codebase are comprehensive and follow Python docstring conventions (e.g., Google, NumPy, or reStructuredText style).
[ ] Create a docs/ directory to organize documentation files, including a user guide, developer guide, and API reference.

[ ] Convert Example Scripts

[ ] Translate example scripts from JavaScript to Python, ensuring they demonstrate the same functionality and workflows.
[ ] Test all example scripts to confirm they work as intended in the Python environment.

[ ] Readme and Setup Instructions

[ ] Update the README file with Python-specific setup instructions, usage guidelines, and environment requirements.
[ ] Include sections on how to install dependencies, run the Python scripts, and contribute to the project.

[ ] Contribute.md

[ ] Create a Contribute.md file outlining the process for contributing to the Python version of the library, including coding standards, branching strategies, and how to submit pull requests.
[ ] Include guidelines for writing tests and updating documentation as part of contributions.

Subtasks Overview

Update Documentation:

Revise all existing documentation to align with the Python implementation.
Ensure all code includes comprehensive docstrings, and establish a clear structure for documentation files.

Convert Example Scripts:

Translate JavaScript example scripts into Python, preserving all functionality and ensuring they work correctly in the Python environment.

Readme and Setup Instructions:

Update the README file to reflect the Python setup process, usage, and contribution guidelines.

Contribute.md:

Develop a Contribute.md file that provides clear instructions for contributing to the Python version of AgentM.

Added an INSTALL.md  - for now without the pypi package

I would focus on porting the core components first and then pick an example or two... maintaining examples can easily be a fulltime job on its own

Exactly my plan.
When you look into the INSTALL.md - I've put a structure there.. although I guess the core folder could be moved to src .. or could be an own package..
Will sleep another night over it.

have added the core functionality - although it is not fully dynamic yet.. (some hardcoded stuff in it atm - which I am going to remove when I add the examples)


Build fails; works when retried repeatedly

Issue description
My apologies in advance for a not well-researched issue, but the feedback cycle of multiple days makes it incredibly time-consuming to gather more details.
For testing https://github.com/NixOS/nixpkgs/issues/18538, I added
  nixpkgs.config.packageOverrides = pkgs: {
    libffi = pkgs.stdenv.lib.overrideDerivation pkgs.libffi (attrs: {
      outputs = attrs.outputs or ["out"] ++ ["debug"];
      buildInputs = attrs.buildInputs ++ [<nixpkgs/pkgs/build-support/setup-hooks/separate-debug-info.sh>];
    });
  };

to my /etc/nixos/configuration.nix and ran nixos-rebuild switch.
The build failed, I retried. It failed again, I retried, it eventually worked.
I set nix.useSandbox = true, so I’m not sure why builds are flaky. Are flaky builds a problem which is also observed/tracked elsewhere already?
Unfortunately, I don’t have much more detail than that, and I’m not sure in which logs you might be interested, so please let me know.
Technical details

System: (NixOS: nixos-version, Ubuntu/Fedora: lsb_release -a, ...)

17.03pre95306.a24728f (Gorilla)

Nix version: (run nix-env --version)

nix-env (Nix) 1.11.4

Nixpkgs version: (run nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion)

"17.03pre95306.a24728f"

Possibly related, I have observed transient build failures for dbus after updating the unstable channel. It succeeded on the third attempt.

Useful logs would be to see how it fails and how it succeeds? Are all the failures producing the same or similar log output? I'd just paste all examples of the thing so we can diff to see what's causing the breakage.

Are build logs stored on disk, or are they just printed on stdout?
From what I remember, I did see the same failure twice, but then later on the build passed (did not see the build output).


Join .Net Foundation

This is ongoing. We were accepted. See more in:

https://github.com/dotnet-foundation/projects/issues/47
https://github.com/dotnet/foundation/pull/164
https://github.com/JasperFx/marten/pull/1436

Onboarding completed! https://github.com/dotnet-foundation/projects/issues/47#issuecomment-601756776


JAVA-13939 Fixed pom parsing error

It seems that this fix is already in the main pom, so I'll close the PR here @dkapil


downloading error!!!

Hi @KevCui , I was trying to dl a new ep of Chainsaw man today. Then I encountered this error:

I tried to pull, if there's a recent updates, but mine is already up to date. Also tried cloning a new repo, but still encountered the same error... Any ideas on this?
Thanks :)

Hey @Dwight123-crypto, the latest commit should fix the issue. Please check.

Thanks KevCui! working fine now.
On Wed, Oct 19, 2022 at 4:57 PM K̶e̶v̶i̶n̶ @.***> wrote:

Hey @Dwight123-crypto https://github.com/Dwight123-crypto, the latest
commit should fix the issue. Please check.
—
Reply to this email directly, view it on GitHub
https://github.com/KevCui/animepahe-dl/issues/82#issuecomment-1283663194,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO4ZIICYINQAP4JTSXL4IITWD6ZXHANCNFSM6AAAAAARITTDNM
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Best regards,
尺ㄩ丂丂🝗㇄


Failed to load dynamic library 'SDL2.dll': error code 126)

Erro on windows 11

Hi, natandiasm.
In order for the program to run in the windows environment, DLLs must be in the same directory as the executable.
https://github.com/sansuido/sdl2/blob/main/SDL2.dll
and more...
Download the DLLs and copy it to the same location as the executable file.

Hi, natandiasm. In order for the program to run in the windows environment, DLLs must be in the same directory as the executable. https://github.com/sansuido/sdl2/blob/main/SDL2.dll and more... Download the DLLs and copy it to the same location as the executable file.

Do you plan to add the ability to load the DLLs ourselves? It can be a bit challenging to load all the DLLs in the same directory as exe every time we build an app :)

Currently, I'm not thinking about fixing it with a full path.
If you are in a Windows development environment, consider placing the dll somewhere in your path (in extreme cases, "C:\Windows\System32").
At the command prompt type "where SDL2.dll" and the dll where found is enabled.


Not able to use, directions not very clear.

I am trying to use the directive created by you but the instructions mentioned are not very clear. I added the module "ngEmojiPicker" and it gives me an error Failed to instantiate module ngEmojiPicker due to:. Please add a demo or point to the correct instructions

+1! Same issue here, what files need to be included for this to work? Thank you!


Fix pyrepseq rename

Origin: https://github.com/andim/pyrepseq/commit/7f65081f6841f44a39f2f6a4179832fdb76ff81a

wait for pip's update


An error has ocurred during file processing bug reporter

Game name: (VrChat)
Engine version: (2019.4.29f1 and 2019.4.31f1)
Platform: (specify platform, if known)
Error message: Some data left
Stack trace:    en uTinyRipper.Lz4.Lz4DecodeStream.ReadBuffer(Stream stream, Int64 count)
en uTinyRipper.BundleFileScheme.ReadFileStreamMetadata(Stream stream, Int64 basePosition)
en uTinyRipper.BundleFileScheme.ReadScheme(Stream stream)
en uTinyRipper.GameCollection.ReadScheme(SmartStream stream, String filePath, String fileName)
en uTinyRipper.GameCollection.LoadScheme(String filePath, String fileName)
en uTinyRipper.GameStructure.ProcessPlatformStructure(GameStructureProcessor processor, PlatformGameStructure structure)
en uTinyRipper.GameStructure.Load(List1 pathes, LayoutInfo layinfo)    en uTinyRipper.GameStructure.Load(IEnumerable1 pathes, LayoutInfo layinfo)
en uTinyRipperGUI.MainWindow.LoadFiles(Object data)

uTinyRipper has been abandoned, but you can try my AssetRipper fork. In the event that AssetRipper encounters issues while ripping your files, feel free to post an issue on that repository.
AssetRipper is actively being developed with the intent to recover games as best as possible. Weekly releases are normally on Sunday or Monday. I encourage you to help out if you're able and willing. Code contributions can be submitted via pull requests.
If you like the work I've done and want to see it continue, please consider sponsoring me. It really does help with development. These are some of the notable things I've implemented since taking over development:

2020+ support
APK, XAPK, and IPA reading with SharpZipLib
Dummy shaders (so everything isn't pink when you open the project)
IL2Cpp support via an integration of Cpp2IL
Better game platform support
Full script decompilation with the ILSpy decompiler
Cross-platform support
Multiple configuration options
Numerous performance improvements
Support for all asset types

Sponsorship Links:

GitHub Sponsors
Patreon
Paypal


Scoreboard back button

At scoreboard, the back button doesn't return you to home screen!

Solved


refactor(button): 优化size属性校验

PR
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] The commit message follows our Commit Message Guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?
优化size属性校验

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

@all-contributors please add @LadyChatterleyLover for code


Update deployment-introduction.md

Adding in information for leveraging our FastTrack for Azure program as a deployment method for customers as well.

#sign-off

@alkohli
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@Alpa @.***> is there anything else you need from me to update this?  Or are we waiting for input from others still?
Thank you,
Nathaniel Bahta
Microsoft
Principal Program Manager
@.FastTrack for Azure
Azure Engineering (CXP)
[Title: Mobile - Description: mobile-icon]<PHONE_NUMBER>
[Title: phone - Description: phone-icon]<PHONE_NUMBER>
[Title: Email - Description: email-icon]<EMAIL_ADDRESS>[A logo of microsoft azure  Description automatically generated]https://azure.microsoft.com/en-us/solutions/hybrid-cloud-app/
There is no reason that function should not be beautiful.
In fact, beauty usually makes it more effective." -Spock
From: Jak Koke @.>
Sent: Friday, September 20, 2024 5:32 PM
To: MicrosoftDocs/azure-stack-docs @.>
Cc: Nate Bahta @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-stack-docs] Update deployment-introduction.md (PR #3322)
@alkohlihttps://github.com/alkohli
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-teamhttps://github.com/orgs/MicrosoftDocs/teams/public-repo-pr-review-team

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-stack-docs/pull/3322#issuecomment-2364644843, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BLFZJTWQCXZPUKPY5UFL6KTZXSH53AVCNFSM6AAAAABOSMPUA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRUGY2DIOBUGM.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Adding @Thomas @.***> so he can chime in 😊. Thank you!
From: Nate Bahta @.>
Sent: Wednesday, September 25, 2024 7:26 AM
To: MicrosoftDocs/azure-stack-docs @.>; MicrosoftDocs/azure-stack-docs @.>; Alpa Kohli @.>
Cc: Mention @.>; Nate Bahta @.>
Subject: RE: [MicrosoftDocs/azure-stack-docs] Update deployment-introduction.md (PR #3322)
@Alpa @.***> is there anything else you need from me to update this?  Or are we waiting for input from others still?
Thank you,
Nathaniel Bahta
Microsoft
Principal Program Manager
@.FastTrack for Azure
Azure Engineering (CXP)
[Title: Mobile - Description: mobile-icon]<PHONE_NUMBER>
[Title: phone - Description: phone-icon]<PHONE_NUMBER>
[Title: Email - Description: email-icon]<EMAIL_ADDRESS>[A logo of microsoft azure  Description automatically generated]https://azure.microsoft.com/en-us/solutions/hybrid-cloud-app/
There is no reason that function should not be beautiful.
In fact, beauty usually makes it more effective.” —Spock
From: Jak Koke<EMAIL_ADDRESS>Sent: Friday, September 20, 2024 5:32 PM
To: MicrosoftDocs/azure-stack-docs<EMAIL_ADDRESS>Cc: Nate Bahta<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-stack-docs] Update deployment-introduction.md (PR #3322)
@alkohlihttps://github.com/alkohli
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-teamhttps://github.com/orgs/MicrosoftDocs/teams/public-repo-pr-review-team
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-stack-docs/pull/3322#issuecomment-2364644843, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BLFZJTWQCXZPUKPY5UFL6KTZXSH53AVCNFSM6AAAAABOSMPUA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRUGY2DIOBUGM.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

I had reviewed the PR with Alpa, to confirm if similar offerings have been published, and she pointed me to Azure migrate.
For transparency I had concerns around this call out as i am not sure if this results in advertising if a customer is interested that Fast Track can’t engage with.
This seems to generate a competitive advantage over partners that may escalate.
Did you run this with CELA prior making the first call out?
Thomas
From: Alpa Kohli @.>
Sent: Wednesday, September 25, 2024 5:00 PM
To: Nate Bahta @.>; Thomas Roettinger @.>; MicrosoftDocs/azure-stack-docs @.>; MicrosoftDocs/azure-stack-docs @.>
Cc: Mention @.>
Subject: RE: [MicrosoftDocs/azure-stack-docs] Update deployment-introduction.md (PR #3322)
Adding @Thomas @.***> so he can chime in 😊. Thank you!
From: Nate Bahta<EMAIL_ADDRESS>Sent: Wednesday, September 25, 2024 7:26 AM
To: MicrosoftDocs/azure-stack-docs<EMAIL_ADDRESS>MicrosoftDocs/azure-stack-docs<EMAIL_ADDRESS>Alpa Kohli<EMAIL_ADDRESS>Cc: Mention<EMAIL_ADDRESS>Nate Bahta<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-stack-docs] Update deployment-introduction.md (PR #3322)
@Alpa @.***> is there anything else you need from me to update this?  Or are we waiting for input from others still?
Thank you,
Nathaniel Bahta
Microsoft
Principal Program Manager
@.FastTrack for Azure
Azure Engineering (CXP)
[Title: Mobile - Description: mobile-icon]<PHONE_NUMBER>
[Title: phone - Description: phone-icon]<PHONE_NUMBER>
[Title: Email - Description: email-icon]<EMAIL_ADDRESS>[A logo of microsoft azure  Description automatically generated]https://azure.microsoft.com/en-us/solutions/hybrid-cloud-app/
There is no reason that function should not be beautiful.
In fact, beauty usually makes it more effective.” —Spock
From: Jak Koke<EMAIL_ADDRESS>Sent: Friday, September 20, 2024 5:32 PM
To: MicrosoftDocs/azure-stack-docs<EMAIL_ADDRESS>Cc: Nate Bahta<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-stack-docs] Update deployment-introduction.md (PR #3322)
@alkohlihttps://github.com/alkohli
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-teamhttps://github.com/orgs/MicrosoftDocs/teams/public-repo-pr-review-team
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-stack-docs/pull/3322#issuecomment-2364644843, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BLFZJTWQCXZPUKPY5UFL6KTZXSH53AVCNFSM6AAAAABOSMPUA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRUGY2DIOBUGM.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Hi Thomas,
We are not in competition with partners, we are a free service that is complementary in nature, providing guidance. We also assist partners in the same capacity.  Does that address your concerns?
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Thomas Roettinger @.>
Sent: Wednesday, September 25, 2024 11:41:14 AM
To: Alpa Kohli @.>; Nate Bahta @.>; MicrosoftDocs/azure-stack-docs @.>; MicrosoftDocs/azure-stack-docs @.>
Cc: Mention @.>
Subject: RE: [MicrosoftDocs/azure-stack-docs] Update deployment-introduction.md (PR #3322)
I had reviewed the PR with Alpa, to confirm if similar offerings have been published, and she pointed me to Azure migrate.
For transparency I had concerns around this call out as i am not sure if this results in advertising if a customer is interested that Fast Track can’t engage with.
This seems to generate a competitive advantage over partners that may escalate.
Did you run this with CELA prior making the first call out?
Thomas
From: Alpa Kohli @.>
Sent: Wednesday, September 25, 2024 5:00 PM
To: Nate Bahta @.>; Thomas Roettinger @.>; MicrosoftDocs/azure-stack-docs @.>; MicrosoftDocs/azure-stack-docs @.>
Cc: Mention @.>
Subject: RE: [MicrosoftDocs/azure-stack-docs] Update deployment-introduction.md (PR #3322)
Adding @Thomas @.***> so he can chime in 😊. Thank you!
From: Nate Bahta<EMAIL_ADDRESS>Sent: Wednesday, September 25, 2024 7:26 AM
To: MicrosoftDocs/azure-stack-docs<EMAIL_ADDRESS>MicrosoftDocs/azure-stack-docs<EMAIL_ADDRESS>Alpa Kohli<EMAIL_ADDRESS>Cc: Mention<EMAIL_ADDRESS>Nate Bahta<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-stack-docs] Update deployment-introduction.md (PR #3322)
@Alpa @.***> is there anything else you need from me to update this?  Or are we waiting for input from others still?
Thank you,
Nathaniel Bahta
Microsoft
Principal Program Manager
@.FastTrack for Azure
Azure Engineering (CXP)
[Title: Mobile - Description: mobile-icon]<PHONE_NUMBER>
[Title: phone - Description: phone-icon]<PHONE_NUMBER>
[Title: Email - Description: email-icon]<EMAIL_ADDRESS>[A logo of microsoft azure  Description automatically generated]https://azure.microsoft.com/en-us/solutions/hybrid-cloud-app/
There is no reason that function should not be beautiful.
In fact, beauty usually makes it more effective.” —Spock
From: Jak Koke<EMAIL_ADDRESS>Sent: Friday, September 20, 2024 5:32 PM
To: MicrosoftDocs/azure-stack-docs<EMAIL_ADDRESS>Cc: Nate Bahta<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-stack-docs] Update deployment-introduction.md (PR #3322)
@alkohlihttps://github.com/alkohli
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-teamhttps://github.com/orgs/MicrosoftDocs/teams/public-repo-pr-review-team
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-stack-docs/pull/3322#issuecomment-2364644843, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BLFZJTWQCXZPUKPY5UFL6KTZXSH53AVCNFSM6AAAAABOSMPUA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRUGY2DIOBUGM.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Thank you for clarifying. Sorted
Thomas
From: Nate Bahta @.>
Sent: Wednesday, September 25, 2024 6:06 PM
To: Thomas Roettinger @.>; Alpa Kohli @.>; MicrosoftDocs/azure-stack-docs @.>; MicrosoftDocs/azure-stack-docs @.>
Cc: Mention @.>; Nate Bahta @.***>
Subject: Re: [MicrosoftDocs/azure-stack-docs] Update deployment-introduction.md (PR #3322)
Hi Thomas,
We are not in competition with partners, we are a free service that is complementary in nature, providing guidance. We also assist partners in the same capacity.  Does that address your concerns?
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Thomas Roettinger<EMAIL_ADDRESS>Sent: Wednesday, September 25, 2024 11:41:14 AM
To: Alpa Kohli<EMAIL_ADDRESS>Nate Bahta<EMAIL_ADDRESS>MicrosoftDocs/azure-stack-docs<EMAIL_ADDRESS>MicrosoftDocs/azure-stack-docs<EMAIL_ADDRESS>Cc: Mention<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-stack-docs] Update deployment-introduction.md (PR #3322)
I had reviewed the PR with Alpa, to confirm if similar offerings have been published, and she pointed me to Azure migrate.
For transparency I had concerns around this call out as i am not sure if this results in advertising if a customer is interested that Fast Track can’t engage with.
This seems to generate a competitive advantage over partners that may escalate.
Did you run this with CELA prior making the first call out?
Thomas
From: Alpa Kohli<EMAIL_ADDRESS>Sent: Wednesday, September 25, 2024 5:00 PM
To: Nate Bahta<EMAIL_ADDRESS>Thomas Roettinger<EMAIL_ADDRESS>MicrosoftDocs/azure-stack-docs<EMAIL_ADDRESS>MicrosoftDocs/azure-stack-docs<EMAIL_ADDRESS>Cc: Mention<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-stack-docs] Update deployment-introduction.md (PR #3322)
Adding @Thomas @.***> so he can chime in 😊. Thank you!
From: Nate Bahta<EMAIL_ADDRESS>Sent: Wednesday, September 25, 2024 7:26 AM
To: MicrosoftDocs/azure-stack-docs<EMAIL_ADDRESS>MicrosoftDocs/azure-stack-docs<EMAIL_ADDRESS>Alpa Kohli<EMAIL_ADDRESS>Cc: Mention<EMAIL_ADDRESS>Nate Bahta<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-stack-docs] Update deployment-introduction.md (PR #3322)
@Alpa @.***> is there anything else you need from me to update this?  Or are we waiting for input from others still?
Thank you,
Nathaniel Bahta
Microsoft
Principal Program Manager
@.FastTrack for Azure
Azure Engineering (CXP)
[Title: Mobile - Description: mobile-icon]<PHONE_NUMBER>
[Title: phone - Description: phone-icon]<PHONE_NUMBER>
[Title: Email - Description: email-icon]<EMAIL_ADDRESS>[A logo of microsoft azure  Description automatically generated]https://azure.microsoft.com/en-us/solutions/hybrid-cloud-app/
There is no reason that function should not be beautiful.
In fact, beauty usually makes it more effective.” —Spock
From: Jak Koke<EMAIL_ADDRESS>Sent: Friday, September 20, 2024 5:32 PM
To: MicrosoftDocs/azure-stack-docs<EMAIL_ADDRESS>Cc: Nate Bahta<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-stack-docs] Update deployment-introduction.md (PR #3322)
@alkohlihttps://github.com/alkohli
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-teamhttps://github.com/orgs/MicrosoftDocs/teams/public-repo-pr-review-team
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-stack-docs/pull/3322#issuecomment-2364644843, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BLFZJTWQCXZPUKPY5UFL6KTZXSH53AVCNFSM6AAAAABOSMPUA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRUGY2DIOBUGM.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Signing off @nathanielbahta. Thanks for your contribution and for your patience as we sorted this out!
#sign-off


profiler invalid

Hi, I run everything fine in docker. But how should I use other profilers when running the BERT model. If I set ++workload.profiling.profiler=tf/tensorflow, it will cause the error 'tf' is not a valid Profiler/'tensorflow' is not a valid Profiler. How should I use other profilers correctly?

So we have an inbuilt profiler for all workloads. The steps are as follows:
# create virtual env
python -m venv ./venv
# activate venv
source ./venv/bin/activate
# install dlio_benchmark with profiler
pip install "dlio_benchmark[dlio_profiler] @ git+https://github.com/argonne-lcf/dlio_benchmark.git"

# Generate data
dlio_benchmark workload=bert ++workload.workflow.generate_data=True

# Enable profiler
export DLIO_PROFILER_ENABLE=1
export DLIO_PROFILER_INC_METADATA=1

# run workload
dlio_benchmark workload=bert

This should create an output folder with will have hidden files such as .trace*.pfw*
These are trace files generated per process for the app and can be visualised using https://ui.perfetto.dev/

So we have an inbuilt profiler for all workloads. The steps are as follows:
# create virtual env
python -m venv ./venv
# activate venv
source ./venv/bin/activate
# install dlio_benchmark with profiler
pip install "dlio_benchmark[dlio_profiler] @ git+https://github.com/argonne-lcf/dlio_benchmark.git"

# Generate data
dlio_benchmark workload=bert ++workload.workflow.generate_data=True

# Enable profiler
export DLIO_PROFILER_ENABLE=1
export DLIO_PROFILER_INC_METADATA=1

# run workload
dlio_benchmark workload=bert

This should create an output folder with will have hidden files such as .trace*.pfw* These are trace files generated per process for the app and can be visualised using https://ui.perfetto.dev/

Thank you very much for your reply. I followed your steps, but encountered the following error：
(venv) root@fe46d0627542:/workspace# pip install "dlio_benchmark[dlio_profiler] @ git+https://github.com/argonne-lcf/dlio_benchmark.git"
Collecting dlio_benchmark[dlio_profiler]@ git+https://github.com/argonne-lcf/dlio_benchmark.git
Cloning https://github.com/argonne-lcf/dlio_benchmark.git to /tmp/pip-install-6ktnd6au/dlio-benchmark
Running command git clone -q https://github.com/argonne-lcf/dlio_benchmark.git /tmp/pip-install-6ktnd6au/dlio-benchmark
Installing build dependencies ... done
Getting requirements to build wheel ... done
Installing backend dependencies ... done
Preparing wheel metadata ... done
ERROR: Invalid requirement: 'dlio-profiler-py@ git+https://github.com/hariharan-devarajan/dlio-profiler.git@dev; extra == "dlio_profiler"'

Can you provide a process or method to run dlio code with dlio profiler in docker?

Yes, I ran it in docker. In addition, I found that dlio benchamrk project will generate a trace.ptw file by default, but it does not include the underlying IO events. And there seem to be limitations when using dlio profiler project to analyze BERT, including: data reading will only repeatedly read one file of the data set, and because dliobenchmark does not use the GPU, the analysis will be different from the actual training process. But at least I can run this project in docker. Thank you very much for your timely reply and help. You can close this issue.

Ok @zhenghh04 can u look at the reader. This behavior should not happen.

@xvanQ so yes the io profiling won't happen by default and u have to set the variables that I have in my docker. For the issue of reading same sample I think that's a bug which needs to be fixed. @zhenghh04 can u take a look.

@xvanQ I think there is some unique issue at your end. I ran the following script and I see that workers read all the requested files correctly.
FROM ubuntu:latest
RUN apt-get update && apt-get install -y python3 python3-pip openmpi-bin openmpi-common libopenmpi-dev git cmake default-jre jq
RUN pip install "dlio_benchmark @ git+https://github.com/argonne-lcf/dlio_benchmark.git"
RUN pip install git+https://github.com/hariharan-devarajan/dlio-profiler.git
RUN mkdir -p /dlio/data /dlio/output
RUN mpirun -n 4 --allow-run-as-root dlio_benchmark workload=bert ++workload.dataset.data_folder=/dlio/data ++workload.output.folder=/dlio/output ++workload.workflow.generate_data=True ++workload.workflow.train=False  ++workload.dataset.num_files_train=128 ++workload.dataset.num_samples_per_file=128 ++workload.train.total_training_steps=85
ENV DLIO_PROFILER_ENABLE=1
ENV DLIO_PROFILER_LOG_LEVEL=ERROR
ENV DLIO_PROFILER_INC_METADATA=1
ENV DLIO_PROFILER_ENABLE=1
RUN mpirun -n 4 --allow-run-as-root dlio_benchmark workload=bert ++workload.dataset.data_folder=/dlio/data ++workload.output.folder=/dlio/output ++workload.dataset.num_files_train=128 ++workload.dataset.num_samples_per_file=128 ++workload.train.total_training_steps=85
RUN ls -al /dlio/output/
ENV filename=/dlio/output/.trace*.pfw
RUN cat $filename | grep -v "\["   | awk '{$1=$1;print}' > /dlio/output/combined.json
RUN jq '.' /dlio/output/combined.json > /dev/null
RUN echo "[" >  /dlio/output/combined.pfw
RUN cat $filename | grep -v "\["   | awk '{$1=$1;print}' | jq -R "fromjson? | . " -c >> /dlio/output/combined.pfw
RUN cat /dlio/output/combined.pfw | grep read

when I check the trace file combine.pfw I see the following
root@b3bea77d8d07:/dlio/output# jq ".args.fname" <<< `cat combined.pfw | grep tfrecord` | sort | uniq
"/dlio/data/train/part_000_of_128.tfrecord"
"/dlio/data/train/part_001_of_128.tfrecord"
"/dlio/data/train/part_002_of_128.tfrecord"
"/dlio/data/train/part_003_of_128.tfrecord"
"/dlio/data/train/part_004_of_128.tfrecord"
"/dlio/data/train/part_005_of_128.tfrecord"
"/dlio/data/train/part_006_of_128.tfrecord"
"/dlio/data/train/part_007_of_128.tfrecord"
"/dlio/data/train/part_008_of_128.tfrecord"
"/dlio/data/train/part_009_of_128.tfrecord"
"/dlio/data/train/part_010_of_128.tfrecord"
"/dlio/data/train/part_011_of_128.tfrecord"
"/dlio/data/train/part_012_of_128.tfrecord"
"/dlio/data/train/part_013_of_128.tfrecord"
"/dlio/data/train/part_014_of_128.tfrecord"
"/dlio/data/train/part_015_of_128.tfrecord"
"/dlio/data/train/part_016_of_128.tfrecord"
"/dlio/data/train/part_017_of_128.tfrecord"
"/dlio/data/train/part_018_of_128.tfrecord"
"/dlio/data/train/part_019_of_128.tfrecord"
"/dlio/data/train/part_020_of_128.tfrecord"
"/dlio/data/train/part_021_of_128.tfrecord"
"/dlio/data/train/part_022_of_128.tfrecord"
"/dlio/data/train/part_023_of_128.tfrecord"
"/dlio/data/train/part_024_of_128.tfrecord"
"/dlio/data/train/part_025_of_128.tfrecord"
"/dlio/data/train/part_026_of_128.tfrecord"
"/dlio/data/train/part_027_of_128.tfrecord"
"/dlio/data/train/part_028_of_128.tfrecord"
"/dlio/data/train/part_029_of_128.tfrecord"
"/dlio/data/train/part_030_of_128.tfrecord"
"/dlio/data/train/part_031_of_128.tfrecord"
"/dlio/data/train/part_032_of_128.tfrecord"
"/dlio/data/train/part_033_of_128.tfrecord"
"/dlio/data/train/part_034_of_128.tfrecord"
"/dlio/data/train/part_035_of_128.tfrecord"
"/dlio/data/train/part_036_of_128.tfrecord"
"/dlio/data/train/part_037_of_128.tfrecord"
"/dlio/data/train/part_038_of_128.tfrecord"
"/dlio/data/train/part_039_of_128.tfrecord"
"/dlio/data/train/part_040_of_128.tfrecord"
"/dlio/data/train/part_041_of_128.tfrecord"
"/dlio/data/train/part_042_of_128.tfrecord"
"/dlio/data/train/part_043_of_128.tfrecord"
"/dlio/data/train/part_044_of_128.tfrecord"
"/dlio/data/train/part_045_of_128.tfrecord"
"/dlio/data/train/part_046_of_128.tfrecord"
"/dlio/data/train/part_047_of_128.tfrecord"
"/dlio/data/train/part_048_of_128.tfrecord"
"/dlio/data/train/part_049_of_128.tfrecord"
"/dlio/data/train/part_050_of_128.tfrecord"
"/dlio/data/train/part_051_of_128.tfrecord"
"/dlio/data/train/part_052_of_128.tfrecord"
"/dlio/data/train/part_053_of_128.tfrecord"
"/dlio/data/train/part_054_of_128.tfrecord"
"/dlio/data/train/part_055_of_128.tfrecord"
"/dlio/data/train/part_056_of_128.tfrecord"
"/dlio/data/train/part_057_of_128.tfrecord"
"/dlio/data/train/part_058_of_128.tfrecord"
"/dlio/data/train/part_059_of_128.tfrecord"
"/dlio/data/train/part_060_of_128.tfrecord"
"/dlio/data/train/part_061_of_128.tfrecord"
"/dlio/data/train/part_062_of_128.tfrecord"
"/dlio/data/train/part_063_of_128.tfrecord"
"/dlio/data/train/part_064_of_128.tfrecord"
"/dlio/data/train/part_065_of_128.tfrecord"
"/dlio/data/train/part_066_of_128.tfrecord"
"/dlio/data/train/part_067_of_128.tfrecord"
"/dlio/data/train/part_068_of_128.tfrecord"
"/dlio/data/train/part_069_of_128.tfrecord"
"/dlio/data/train/part_070_of_128.tfrecord"
"/dlio/data/train/part_071_of_128.tfrecord"
"/dlio/data/train/part_072_of_128.tfrecord"
"/dlio/data/train/part_073_of_128.tfrecord"
"/dlio/data/train/part_074_of_128.tfrecord"
"/dlio/data/train/part_075_of_128.tfrecord"
"/dlio/data/train/part_076_of_128.tfrecord"
"/dlio/data/train/part_077_of_128.tfrecord"
"/dlio/data/train/part_078_of_128.tfrecord"
"/dlio/data/train/part_079_of_128.tfrecord"
"/dlio/data/train/part_080_of_128.tfrecord"
"/dlio/data/train/part_081_of_128.tfrecord"
"/dlio/data/train/part_082_of_128.tfrecord"
"/dlio/data/train/part_083_of_128.tfrecord"
"/dlio/data/train/part_084_of_128.tfrecord"
"/dlio/data/train/part_085_of_128.tfrecord"
"/dlio/data/train/part_086_of_128.tfrecord"
"/dlio/data/train/part_087_of_128.tfrecord"
"/dlio/data/train/part_088_of_128.tfrecord"
"/dlio/data/train/part_089_of_128.tfrecord"
"/dlio/data/train/part_090_of_128.tfrecord"
"/dlio/data/train/part_091_of_128.tfrecord"
"/dlio/data/train/part_092_of_128.tfrecord"
"/dlio/data/train/part_093_of_128.tfrecord"
"/dlio/data/train/part_094_of_128.tfrecord"
"/dlio/data/train/part_095_of_128.tfrecord"
"/dlio/data/train/part_096_of_128.tfrecord"
"/dlio/data/train/part_097_of_128.tfrecord"
"/dlio/data/train/part_098_of_128.tfrecord"
"/dlio/data/train/part_099_of_128.tfrecord"
"/dlio/data/train/part_100_of_128.tfrecord"
"/dlio/data/train/part_101_of_128.tfrecord"
"/dlio/data/train/part_102_of_128.tfrecord"
"/dlio/data/train/part_103_of_128.tfrecord"
"/dlio/data/train/part_104_of_128.tfrecord"
"/dlio/data/train/part_105_of_128.tfrecord"
"/dlio/data/train/part_106_of_128.tfrecord"
"/dlio/data/train/part_107_of_128.tfrecord"
"/dlio/data/train/part_108_of_128.tfrecord"
"/dlio/data/train/part_109_of_128.tfrecord"
"/dlio/data/train/part_110_of_128.tfrecord"
"/dlio/data/train/part_111_of_128.tfrecord"
"/dlio/data/train/part_112_of_128.tfrecord"
"/dlio/data/train/part_113_of_128.tfrecord"
"/dlio/data/train/part_114_of_128.tfrecord"
"/dlio/data/train/part_115_of_128.tfrecord"
"/dlio/data/train/part_116_of_128.tfrecord"
"/dlio/data/train/part_117_of_128.tfrecord"
"/dlio/data/train/part_118_of_128.tfrecord"
"/dlio/data/train/part_119_of_128.tfrecord"
"/dlio/data/train/part_120_of_128.tfrecord"
"/dlio/data/train/part_121_of_128.tfrecord"
"/dlio/data/train/part_122_of_128.tfrecord"
"/dlio/data/train/part_123_of_128.tfrecord"
"/dlio/data/train/part_124_of_128.tfrecord"
"/dlio/data/train/part_125_of_128.tfrecord"
"/dlio/data/train/part_126_of_128.tfrecord"
"/dlio/data/train/part_127_of_128.tfrecord"

As u can see the above script correctly reads all the data. I will close this issue for now. But feel free to try this and open another issue if u can still not reproduce the results through docker.


Move KLT Cert Manager into its own repo

Goal
Make the Keptn Certificate Manager a standalone and re-usable project.
Technical Details
The Keptn Certificate Manager is general enough to provide self-signed certificates to any workload that matches the configured labels. It works by having two components:

operator
library

The operator is responsible for watching the workloads that match a specific set of labels and providing them with certificates.
The library is responsible for waiting for a certificate to be available and requesting a new one when it expires.
DoD

[ ] Keptn Cert Manager has its own repo
[ ] Keptn Cert Manager is released independently from any other Keptn artifacts
[ ] The Golang library can be used by other artifacts

Research topic: how does release please work with monorepos?
can you release monorepo parts independently?
what happens to our interdependencies then?

Some open questions from the PR:

how to track and set the cert manager version for the KLT manifest?
thoughts: it should be easy through the helm chart but maybe we need to do some trickery to get the manifest to work with checking out a different version of klt and then rendering the cert manager manifest from there and including it back into the klt manifest


Stores the enum string instead of int for JWT Security Actions.

[#134825047]
https://www.pivotaltracker.com/story/show/134825047

@eldavido PTAL


Changed test case to not depend on unit test of Hyperspace.

Fixes #48

Coverage increased (+0.006%) to 99.186% when pulling d4f1ed72bd29734de47469673885c26f1aad4311 on 48-Fail-to-load-Stargate-v2---Test-Group- into 40ff17870d12d1544c9cd554a3f829bc5e34e288 on release-candidate.


recipe validation

What problem are you trying to solve?
reintroduce sanity checks
What's your suggested solution?
warnings/exceptions that now need to be raised by the recipe validation:

ensemble.py

[x] warn if no rule policy is contained in ensemble           f"'{RulePolicy.__name__}' is not included in the model's "
           f"policy configuration. Default intents such as "
           f"'{USER_INTENT_RESTART}' and '{USER_INTENT_BACK}' will "
           f"not trigger actions '{ACTION_RESTART_NAME}' and "
           f"'{ACTION_BACK_NAME}'.",
           docs=DOCS_URL_DEFAULT_ACTIONS,

[x] warn if there are form names but no rule policy contained             "You have defined a form action, but have not added the "
             f"'{RulePolicy.__name__}' to your policy ensemble. Either "
             f"remove all forms from your domain or add the '{RulePolicy.__name__}' "
             f"to your policy configuration."
         )

[x] warn if priorities are not unique                f"Found policies {v} with same priority {k} "
                f"in PolicyEnsemble. When personalizing "
                f"priorities, be sure to give all policies "
                f"different priorities.",
                docs=DOCS_URL_POLICIES,
            )

rule policy:

[x] assert that it's compatible with the domain (... nearly every component should have that?)
[x]  warn if rule based data exists but isn't used -- and if rule based data is expected but missing

     policy.supported_data()
     in [SupportedData.RULE_DATA, SupportedData.ML_AND_RULE_DATA]
     for policy in ensemble
 )
 contains_rule_tracker = any(
     tracker.is_rule_tracker for tracker in training_trackers
 )

 if consuming_rule_data and not contains_rule_tracker:
     rasa.shared.utils.io.raise_warning(
         f"Found a rule-based policy in your pipeline but "
         f"no rule-based training data. Please add rule-based "
         f"stories to your training data or "
         f"remove the rule-based policy (`{RulePolicy.__name__}`) from your "
         f"your pipeline.",
         docs=DOCS_URL_RULES,
     )
 elif not consuming_rule_data and contains_rule_tracker:
     rasa.shared.utils.io.raise_warning(
         f"Found rule-based training data but no policy supporting rule-based "
         f"data. Please add `{RulePolicy.__name__}` or another rule-supporting "
         f"policy to the `policies` section in `{DEFAULT_CONFIG_PATH}`.",
         docs=DOCS_URL_RULES,
     )

featurizer

[x] validate compatability with tokenizer
[x] validate featurizers can be used together (names must be unique)

[ ]  follow-up task: check whether we can simplify the function application in LexicalSyntacticFeaturizer now (should not have to worry about non existing pos tokens anymore - unless "pos" tokens might still not be added by the SpacyTokenizer)

every component

[x] needs to check whether all required components are contained on the path from input source to itself, e.g. the sklearn intent classifier requires a DenseFeaturizer, other classifiers require just any featurizer, ...
[ ] validation of config - GraphNode only fills in the default values but we do not detect e.g. typos this way
[x] check that language of training data data is supported / matches supported languages of components that need not be trained (e.g. ConveRT tests this - even though it doesn't train)

Examples (if relevant)
No response
Is anything blocking this from being implemented? (if relevant)
No response
Definition of Done

[ ] unit tested

assert that it's compatible with the domain (... nearly every component should have that?)

Done as part of https://github.com/RasaHQ/rasa/pull/9576

ensemble / rule policy checks:  covered by DefaultV1ConfigValidator #9336
language: covered in validation.py
required components: #9677
compatability with tokenizer: implicitly covered by combination of config validator (not more than 1 tokenizer) and requested components

💪🏻


ARROW-1648: C++: Add cast from Dictionary[NullType] to NullType

Travis failure was due to a quay.io problem, otherwise build is fine.

Rebased and fixed this up. Will merge on green build

+1. One of the Travis macOS stalled so merging


"Concurrency" setting in pipeline.yml is ignored when "Global Concurrency Limit" is not set in UI

There are two places to set concurrency. The document, Controlling Concurrency,  doesn't mention, set "Global Concurrency Limit" to 1 in UI is mandatory.
I set  concurrency:  and concurrency_group:  in pipeline.yml file only at first, and found the pipeline doesn't work as I expected.
After digging the problem, I realized finally, I have to manually set  "Global Concurrency Limit"  in UI, then the concurrency in step of pipeline.yml works.
Please confirm if this is a bug or not. If not, please update related document that you have to set Global Concurrency Limit first if you need to enable concurrency feature.
buildkite version is v2.5.1

Sorry you're having a problem with that. You don't have to set the concurrency limit in the UI at all, it should work just fine from your pipeline.yml regardless of what you've set in the UI. If you find there's a build that's not behaving, can you email your pipeline.yml and a link to the build to support? And we can look into it for you!


High CPU acquiring socket, left in stuck state

FTP Server OS: Unix
FTP Server Type: BrickFTP
Client Computer OS: Windows Server 2018
FluentFTP Version: 44.0.1
Framework: .NET 7 (7.0.3 runtime)
We have a task that runs every night. This task creates a small text file and uploads it to the FTP server. Thousands of these tasks are spawned but only a handful run at time; typical runtime per task is a few hundred ms.
3 times now in the last 3 months, we've noticed that one of the servers will experience high CPU usage (>90%) and we see that a few of these tasks are stuck in the queue having been running for several hours. I was able to grab a process dump most recently and it seems that the high CPU usage is spent on the FluentFTP.FtpSocketStream. I can provide the callstacks if helpful. It looks like the thread spins up and tries to acquire a socket and then hangs out in that state for several hours until the thread is killed and the task re-queued (at which point it runs and completes instantly, as it should).
Because multiple threads are running at the same time I'm having trouble separating out the logs for the tasks that got stuck (vs. the ones that continued on), but I can try if that's helpful. I'll improve our logging to avoid this issue in the future.
Has anyone else encountered this?
Logs :

<paste VERBOSE logs here>

You are welcome. Interesting factoid: The error was introduced (by me - sorry about that) quite a few months ago. Reports about this trundled in the first time about one or two weeks ago and I fixed it right away. If anyone had reported this months ago....
One thing you should know: Instead of a "hang" or even a "loop", the operation will timeout (as it should). I assume that your programming reacts to that in some way - you would not have experienced this fault if the transfer (all of them) would not incur  some error of whatever kind.

Also reference: #1222 #1203 #1156

I should have reported it when we first noticed it months ago, but I assumed it was either an issue in our own code (forgetting to dispose somehow) or something in the runtime which is obviously under rapid development. Hate to assume that it's a particular library when my own code is the greater liability.
Thanks again for all your work. Will be sure to circle back with more info if it comes up again.


Add urls namespace as option

Hi. Unfortunately, this PR is no longer valid since the RootView has been completely rewritten. Also every other part of djoser that this PR touches has also changed more or less.
Therefore I'm going to close this, however thank you very much for your work.


Modify github action and publish-chart-yaml.sh to support helm-testing/ branches

Modify github action and publish-chart-yaml.sh to support helm-testing/* branches
Description

Modify github action  to support helm-testing/* branches created for release branches
Modify publish-chart-yaml.sh to support helm-testing/* branches

Motivation and Context

This change will publish helm chart to system test helm registry for release branches
Regression
 No
How Has This Been Tested?
Tested locally

Please squash your commits

I have squashed the commits

bors try

bors try

bors merge


Minecraft 1.21 support

gate currently has no 1.21 support

Added in https://github.com/minekube/gate/commit/a09ea2e126bf87603e280da0e25b764576ac0a33


MWPW-157210 STE Promo card not appearing

On https://www.stage.adobe.com/products/catalog.html call for
https://main--cc--adobecom.hlx.page/cc-shared/fragments/promos/2024/global/test/catalog-promo-test/fragments/catalog-ste.plain.html
fails with error 401.
On https://main--cc--adobecom.hlx.page/products/catalog this works since the hostname is identical.
So I changed the hostname in the card URL to load it from merch-card-collection.js
before localizeLink() is called.
I started with an idea to change the code of localizeLink() to do the same thing but this method is used in too many places, hence too risky.
Can be tested only on https://www.stage.adobe.com/products/catalog.html
Resolves: MWPW-157210
Test URLs:

Before: https://main--milo--adobecom.hlx.page/drafts/bozo/price-cta?martech=off
After: https://mwpw157210catalogste--milo--bozojovicic.hlx.page/drafts/bozo/price-cta?martech=off

@bozojovicic Do you have anything pending here to work on open comments? otherwise have covered regressions and mark it ready for stage

@Roycethan I answered all comments. Nothing pending here. It can be merged to stage.


Update README

[ ] Describe service irm_kmi.get_forecasts_radar
[ ] Update features and options in the list
[ ] Move some parts to the Wiki instead of the README
[ ] Use HACS button for the installation section

I am very new in home assistant...  I installed the IRM-KMI weather application, it worked OK but afterwards I had to restart the unit on a previous configuration and I cannot connect anymore on the IRM server.
The message is


DEBUG jupyter book preview in PRs

This time it should work as expected, I am 100% sure.

Finally it works!


issue with roc_curve_gammness_per_energy legend

Issues with the labels and legend of the random  dashed  line in roc_curve_gammness_per_energy  appearing (n-1) times  and  with  the  energy ranges + _line_n as labels

solved by #87


Charting goreleaser

Hi,
I'm trying to chart goreleaser, from github.com/goreleaser/goreleaser, however, I only get this small chart out of the big package:

I've tried,
gpkg=github.com/goreleaser/goreleaser
go-callvis -group pkg,type -limit $gpkg $gpkg | dot -Tpng -o ~/out.png
# and
go-callvis -group pkg,type -limit github.com/goreleaser $gpkg | dot -Tpng -o ~/out.png

But the results are the same for both cases.
This is big package with many types and sub-folders, how come the chart is so limited, and how can I see the whole picture?
PS. Here is its folder structure:
./context
./checksum
./config
./config/testdata
./pipeline
./pipeline/env
./pipeline/fpm
./pipeline/fpm/testdata
./pipeline/git
./pipeline/brew
./pipeline/brew/testdata
./pipeline/snapcraft
./pipeline/cleandist
./pipeline/release
./pipeline/build
./pipeline/defaults
./pipeline/checksums
./pipeline/archive
./goreleaserlib
./internal
./internal/ext
./internal/name
./internal/testlib
./internal/client
./internal/buildtarget
./internal/archiveformat

Within each folder there at least one or two types define.
Please help. Thanks!

Oh, is it because all non-public functions & types are ignored?
I even tried this:
go-callvis -group pkg,type -nostd $gpkg | dot -Tpng -o ~/out.png

But the result is still rather limited:

If so, the non-public functions & types are equally important (besides the public ones) for people to understand the package, when they are trying to how how things related, which is what go-callvis for and why they are using it.
Please consider adding a switch to output those.
Thx.

I think why you might be confused. I will try to explain.
Both of your examples show expected output. Keep in mind that this tool only shows function calls. For example it won't show types, variables or constants. It can only show relation to a type if it's method is called.
I assume that by non-public functions you meant unexported. The output always shows both unexported and exported functions. Currently there isn't any flag to omit them. In the Reference guide you can see the difference in visualization of such functions.
In your examples you can clearly see unexported function init calling anonymous function init#1. The reason why you don't see any calls from the main package to some unexported function inside other package is because that's impossible in Go, since unexported functions can only be called inside package.
The important flag which controls what is shown in the output is -focus flag. By default it is set to main, that means it will only show function calls from and to the main package. If you want to show calls inside other package you can use -focus flag to change the shown package.
You can find more thorough explanation in the wiki: https://github.com/TrueFurby/go-callvis/wiki/Focusing-packages

Oh, that's the trick. Thanks a lot for the comprehensive explanation, and the wiki example too!
So, FTA, this works,
go-callvis -group pkg,type -focus="" -limit github.com/goreleaser $gpkg | dot -Tpng -o ~/screenshot.png

and generated this chart:


Provide some grammar

Would be great if one would be able to highlight special syntax for bats. Like @test, load, run etc.
What I came up with:
bats.extended.tmLanguage:
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
    <dict>
        <key>scopeName</key>
        <string>source.shell.bats.extended</string>
        <key>injectionSelector</key>
        <string>L:source.shell.bats -string -comment</string>
        <key>patterns</key>
        <array>
            <dict>
                <key>match</key>
                <string>@test\b</string>
                <key>name</key>
                <string>keyword.control.bats</string>
            </dict>
            <dict>
                <key>match</key>
                <string>\b(assertEqual|assertNotEqual|assertContains|run|load)\b</string>
                <key>name</key>
                <string>support.function.bats</string>
            </dict>
            <dict>
                <key>match</key>
                <string>\$(output|status|lines)\b</string>
                <key>name</key>
                <string>support.variable.bats</string>
            </dict>
        </array>
    </dict>
</plist>

package.json:
"grammars": [
			{
				"language": "bats",
				"scopeName": "source.shell.bats",
				"path": "./syntaxes/bats.tmLanguage"
			},
			{
				"scopeName": "source.shell.bats.extended",
				"path": "./syntaxes/bats.extended.tmLanguage",
				"injectTo": [ "source.shell.bats" ]
			}
		],

Hi,
Thank you for the code, nice enhancement.
I've added the update on a new branch (feature/#3-grammar)
I've made some changes
<string>\b(assertEqual|assertNotEqual|assertContains|run|load)\b</string>
to
``\b(run|load|skip)\b```
Regarding to Bats doc, you've forgot the skip item.
I also removed the assert... as I didn't find them on Bats.
I've removed the support.variable.bats item as they are already managed by sh grammar coloration.
I've tested the update with the following bats file, nice job.
Please review it and tell me if it's fine to you so I will update the plugin.
Best regards
Jetmartin

Do you mind creating a PR for discussing the changes? The "resolve discussion" is especially useful.
Besides that I also enhanced my version which looks like below. I included assertions and functions from bats-assert and bats-support which I found helpful and "standard enough". The variables
were included because they are special for bats so it should be possible to highlight them (although e.g. ${lines[...]} is missing :/ ). I'm using the following config for that (in user settings of vscode)
"editor.tokenColorCustomizations": {
        "textMateRules": [
            {
                "scope": "support.function",
                "settings": {
                    "foreground": "#720000",
                    "fontStyle": ""
                }
            },
            {
                "scope": "support.function.bats",
                "settings": {
                    "foreground": "#720000",
                    "fontStyle": "bold"
                }
            },
            {
                "scope": "support.variable.bats",
                "settings": {
                    "foreground": "#329432",
                    "fontStyle": ""
                }
            }
        ]
    }

Current syntax:
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
    <dict>
        <key>scopeName</key>
        <string>source.shell.bats.extended</string>
        <key>injectionSelector</key>
        <string>L:source.shell.bats -string -comment</string>
        <key>patterns</key>
        <array>
            <dict>
                <key>match</key>
                <string>@test\b</string>
                <key>name</key>
                <string>keyword.control.bats</string>
            </dict>
            <dict>
                <key>match</key>
                <string>\b(assert|refute|assert_(equal|success|failure|output|line)|refute_(output|line))\b</string>
                <key>name</key>
                <string>support.function.bats.assertions</string>
            </dict>
            <dict>
                <key>match</key>
                <string>\b(fail|batslib_(is_caller|err|decorate))\b</string>
                <key>name</key>
                <string>support.function.bats.assertions</string>
            </dict>
            <dict>
                <key>match</key>
                <string>\b(run|load|skip)\b</string>
                <key>name</key>
                <string>support.function.bats.builtin</string>
            </dict>
            <dict>
                <key>match</key>
                <string>\$(output|status|lines)\b</string>
                <key>name</key>
                <string>support.variable.bats</string>
            </dict>
        </array>
    </dict>
</plist>

For sure creating a PR could be smart.
Anyway, thinking about it, you probably right about the variables.
I've never used those modules, they looks nice.
I will update the bats.extended.tmLanguage file and test it with the test files provided by the modules later tonight or tomorrow.
...and make a PR.
Thanks for the updated file.

Hi,
Let's continue the conversation here
I've taken a look to the repositories and added more functions. (I guess it's almost exhaustive)
I've also created a quick test file to check the highlights.
I will appreciate your feed-back.
Best.


Implement assignment #57 DataElementResource enhancements

Renamed all classes/variables named "DataElement", "dataElement" " Data Element", "data element", "Data element" to  Phenotype,  phenotype in eureka-webapp, eureka-services, eureka-common projects in java and jsp, js codes.
Also changed liquibase script, so that all table(s), column name(s) that is named "data element" like, changed to phenotype like.

Also implement assignment #58


inbound/odfi: notifications on received file

It's come up in slack that notifications on inbound files would be helpful. These are the notification in slack, PD, etc and the notify package already supports a direction argument, so it should be easy enough to write through.

@adamdecaf
Hello, looking up this issue
is there a more buttressed problem statement to this.

Not really. I haven't heard about this request in quite a while.

Oh, Alright.