RSA private key DER decode fails without CRT components

I'm trying to decode the RSA private key which was DER encoded earlier without p, q, and CRT components (dmp1, dmq1 and iqmp is NULL). I'm using same openssl version for both encoding and decoding, encoding works fine but decode fails. In decode we call EVP_PKCS82PKEY() function, this is failing with below error:
469393408:error:0D078079:asn1 encoding routines:asn1_item_embed_d2i:field missing:crypto/asn1/tasn_dec.c:425:Field=p, Type=RSAPrivateKey
The above error is because field p is NULL, but with same p is NULL encoding is success. Any idea why encode is Success but decode fails?
The openssl version I tested is 1.1.1d.
The sample code:
To Encode RSA private key I used below code:
int encode_priv_key(EVP_PKEY * pkey, unsigned char *data, size_t * len)
{
    BIO *bio = NULL;
    BUF_MEM *bptr = NULL;
    PKCS8_PRIV_KEY_INFO *p8inf = NULL;

    if (NULL == len) {
        printf("%s:%d\n", __FILE__, __LINE__);
        return -1;
    }

    p8inf = EVP_PKEY2PKCS8(pkey);
    if (!p8inf) {
        printf("%s:%d\n", __FILE__, __LINE__);
        goto end;
    }

    bio = BIO_new(BIO_s_mem());
    if (!bio) {
        printf("%s:%d\n", __FILE__, __LINE__);
        goto end;
    }

    if (i2d_PKCS8_PRIV_KEY_INFO_bio(bio, p8inf) < 0) {
		printf("%s:%d\n", __FILE__, __LINE__);
        goto end;
	}

    BIO_get_mem_ptr(bio, &bptr);
    if ((*len < bptr->length) && data) {
        *len = bptr->length;
        printf("%s:%d\n", __FILE__, __LINE__);
        goto end;
	}
    *len = bptr->length;

    if (NULL != data)
        memcpy(data, bptr->data, *len);

    PKCS8_PRIV_KEY_INFO_free(p8inf);
    BIO_free(bio);
    return 0;
end:
    if (p8inf)
        PKCS8_PRIV_KEY_INFO_free(p8inf);
    if (bio)
        BIO_free(bio);
    return -1;
}

For decode we use below code:
EVP_PKEY *decode_priv_key(unsigned char *data, size_t len)
{
    BIO *bio = NULL;
    PKCS8_PRIV_KEY_INFO *p8inf = NULL;
    EVP_PKEY *pkey = NULL;

    bio = BIO_new_mem_buf(data, len);
    if (!bio) {
        printf("%s:%d\n", __FILE__, __LINE__);
        goto end;
    }

    p8inf = d2i_PKCS8_PRIV_KEY_INFO_bio(bio, NULL);
    if (!p8inf) {
        printf("%s:%d\n", __FILE__, __LINE__);
        goto end;
    }

    if (!(pkey = EVP_PKCS82PKEY(p8inf))) {
        printf("%s:%d\n", __FILE__, __LINE__);
        goto end;
    }

    PKCS8_PRIV_KEY_INFO_free(p8inf);
    BIO_free(bio);
    return pkey;

end:
    if (p8inf)
        PKCS8_PRIV_KEY_INFO_free(p8inf);
    if (bio)
        BIO_free(bio);
    if (pkey)
        EVP_PKEY_free(pkey);
    return NULL;
}

EVP_PKCS82PKEY() is failing with error reported above.

Slight correction: parameters p and q are not CRT components.

yeah agree, I mean p and q and missing CRT components.

The "successful" encoding is due to a bug. See https://github.com/openssl/openssl/issues/16026. OpenSSL 3.0 will have that bug fixed. Sadly, the bugfix had to be reverted in 1.1.1 because it was discovered that some TPM applications misused the i2d_X509 API to encode a different, non-X.509, structure.
The serialization for RSA private keys is defined here. It only works for RSA keys with CRT parameters. RSA keys without CRT parameters are not serializable in any standard format that I'm aware of.
https://datatracker.ietf.org/doc/html/rfc8017#appendix-A.1.2

RSA keys without CRT parameters are not serializable in any standard format that I'm aware of

Yet you might be surprised what variations libraries are prepared to accept, due to the long history. See Tbl 1 and Appx A here.

I'm not sure where you got this implication.

I don't think it's meant to be taken that way, although I see how you get that.
I read it as "our experiments tell us a lot of code is doing this", rather than "if you're not doing this, your code is wrong".
If you go back through the history of RFC 8017, you'll notice it pre-dates (by far) "SHOULD" "SHALL" etc considerations from RFC 8174.
 I'll send a scathing email to the authors now. Let me go find out who they are.

I think we can all agree that if an RSA key is claimed to be DER serialized according to PKCS#1 / RFC8017, it must serialize the structure of RSAPrivateKey or RSAPublicKey.  Otherwise, that serialization is something else, it simply isn't PKCS#1 / RFC8017 compliant.

I think we can all agree that if an RSA key is claimed to be DER serialized according to PKCS#1 / RFC8017, it must serialize the structure of RSAPrivateKey or RSAPublicKey

Totally
I'm derailing the original issue. My apologies, @bkommanaboyina
Please continue like normal

@levitte one of the points is exactly that, and the recent discussion at OTC that resulted in reverting #16027 in 1.1.1 (see #16308) is a perfect example. OpenSSL, and many other libraries, often err on the side of legacy compatibility or historical interoperability when faced with bugfixes: this means that buggy or not conformant behavior is tolerated (or even defaulted to) in input and output, and non-standard things become de-facto standards.
The long and twisted story of RSA gave us multiple instances of this as discussed above!

@romen I think you are mixing up parsing and serialization, as well as backwards compatibility with historical errors vs. introducing new errors.
I don't know of any version of that OpenSSL tolerated missing fields when parsing an RSAPrivateKey, so there's not actually a backwards-compatibility problem. While #16027 had to be reverted, that was for serialization. Serialization was broken in old OpenSSL. Fixing that ran into a backwards-compatibility problem in one particular consumer. That one particular consumer was misusing the API in a context that happened to work for their particular use case. It is not a generally applicable strategy. Omitting fields in ASN.1 does not work generally work. It ends up syntactically ambiguous if there is a run of fields with the same tag.
Indeed RSAPrivateKey is one such case. If you delete a field in the middle vs. at the end, there's no way to tell which field was deleted.

@davidben I was mixing it deliberately to stay on the general side and reiterate that across libraries and products "uncommon" serialization output and tolerance for "uncommon" encodings on parsing is not that unusual after all, and usually justified by interoperability, legacy baggage, historical reasons, despite what the standards encourage, recommend, mandate or forbid!

Either way, this issue is about decoding, and the example code is correctly demonstrating that OpenSSL serialization could be made to produce utter shite.
The take away lesson here is really, don't misuse OpenSSL bugs :wink:

I would say that this issue can be closed at this point.  I hope I sprinkled enough response labels...

Up to PKCS#1 v1.5 there was additional text included that made it clear what you were meant to do for portability if you did not have the CRT components. Unfortunately this text was omitted in later versions. It makes it exceedingly clear that you aren't expected to omit values or place in substitute values in the ASN1 representation - if you don't have the CRT values you need to calculate them. The syntax explicitly and deliberately requires the CRT values.

An RSA private key logically consists of only the
modulus n and the private exponent d. The presence
of the values p, q, d mod (p-1), d mod (p-1), and
q-1 mod p is intended for efficiency, as
Quisquater and Couvreur have shown [QC82]. A
private-key syntax that does not include all the
extra values can be converted readily to the
syntax defined here, provided the public key is
known, according to a result by Miller [Mil76].


Sprite pack backgrounds don't import into the gallery

The sprite packs seem to be working great in the gallery for regular images, but when choosing a background (scene category) the gallery of background images doesn't look at the 160x120 images in the sprite extension.

We need to use "background" tag to make this happen


Environment variable doesn't get used in control panel

When using an .env variable for Cloud Name, it doesn't get replaced in the control panel for thumbnails, previews, etc.
Source from a thumbnail in the control panel:
<img src="https://res.cloudinary.com/$CLOUDINARY_CLOUDNAME/image/upload/c_crop,g_center,h_22,w_34/q_auto/f_auto/v1/testwerk/cover-2019_06_23_ML_bezoekers_kinderen_label_boom.jpg?_a=BAAAROAI 34w, https://res.cloudinary.com/$CLOUDINARY_CLOUDNAME/image/upload/c_crop,g_center,h_45,w_68/q_auto/f_auto/v1/testwerk/cover-2019_06_23_ML_bezoekers_kinderen_label_boom.jpg?_a=BAAAROAI 68w">

Hi Bart,
Thank you for letting me know. This should now be fixed and released in version 1.0.1.


fix(KubeAPIErrorBudgetBurn): change variable name

this way when copy pasting, you can set the var once and the command will suceed

/lgtm


snap: -U argument implies -u.

Currently, in order to cause snap to upgrade itself, one must use
./snap -uU. Further, the current behavior of specifying -U without -u is
unexpected: no snap upgrade checks are performed and the running OS itself
is upgraded.
This diff changes the behavior of specifying -U in isolation such that
snap both checks for an upgrade to itself and performs the upgrade if one
exists. From testing, there is no pathological change to specifying -u in
isolation or -uU together.

This is good, and makes the citizens happy.


Replace to node20

Resolves #526

https://github.com/github/dependency-submission-toolkit/blob/5c95689837aba319e0b9c810a3581acc53c0c2f8/package.json#L63
No activity in upstream 🙄


MEV

Describe your changes and provide context
Testing performed to validate your change

FIrst passing build of an mev module!


error

Laravel Version: Laravel Framework 5.6.25
Voyager Version: #.#.#
PHP Version: 7
Database Driver & Version: mysql

hi. i have error with mysql in this commnad-> php artisan voyager:install
this is error text:
Illuminate\Database\QueryException  : SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 1000 bytes (SQL: alter ta
ble users add unique users_email_unique(email))
Steps To Reproduce:

Please search before opening a new issue.
Duplicate of https://github.com/the-control-group/voyager/issues/3035, #1840, #901
There are a few other links and solutions here https://github.com/the-control-group/voyager/issues/2540#issuecomment-360172218


[Improvement] Disable Oceanbase schema comment and properties as  it's unsupported operation in oceanbase catalog

What would you like to be improved?

How should we improve?
No response

@LauraXia123 Can you take a look at this improvement?

By the way , "ADD PROPERTIES" button in "Edit Schema" page is also needed to disable


Disable and re-enable invalid opensuse 15.1 repo

Ignore this pull request, workaround is no longer needed as package repo has been fixed


dynamic data population

How can I add data from a json?
Thanks.

I'm sure you can figure this out.

Yea, but it loads into the underlying select, but not the tree-multiselect


Can't watch JS files for changes

When I run eleventy with eleventy --serve I would like to make changes in my JS file and have Rollup automatically pick up those changes, rebuild the destination JS file, and have browsersync refresh the browser. This doesn't work - Rollup doesn't pick up changes to the JS file. I have to restart eleventy --serve on the command line each time I make changes to JS files.
https://rollupjs.org/guide/en/#watch-options specifies that Rollup will watch the specified input files for changes, but:
These options only take effect when running Rollup with the --watch flag, or using rollup.watch.

How do I run Rollup in watch mode?
My .eleventy.js file reads:
eleventyConfig.addPlugin(rollupPlugin, {
  rollupOptions: {
    output: {
      format: 'es',
      dir: 'dist/js',
    },
    watch: {
      include: [
        'src/js/*'
      ]
    }
  },
});

However, I can't see how to invoke Rollup via eleventy-plugin-rollup in watch mode.

Hi @BurningDog,
this plugin does not use the rollup watch mode on purpose, as it's supposed to be highly integrated into the 11ty workflow.
This means that for each build (and watch build of 11ty) a new rollup build instance is created.
You should be able to resolve this issue by adding a watch target to your js files in your eleventy config.
You can see the 11ty docs here
Code example:
// .eleventy.js
module.exports = function(eleventyConfig) {
  eleventyConfig.addWatchTarget("src/js/");
};

Please add a short response wether this helped you so I can close the issue or otherwise can investigate further.

Ah brilliant, this worked perfectly, thank you! Will close the issue. It would be great to have this added to the README too.

Just FYI:
Version 1.1.0 of this plugin now does a best effort to parse the rollup config watch target - the approach described above is still the recommended way of doing things.


新增数据时，滚动条变为0

Can you explain the issue??
This library does not support dynamic lists, so when the items change it should reset the calculations (as of now I only check the list length to check for changes)

Closed due to unactivity


IMU hangs on close (Unity3D)

Required Info

Camera Model
D435i & D455

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
Windows 10

Kernel Version (Linux Only)
-

Platform
PC

SDK Version
2.45.0 }

Language
C#/Unity3D

Segment
Computer application

Issue Description
If the IMU (accelerometer and/or gyroscope) is enabled in Unity3D, the application hangs for about 20 seconds when closing.
Unity Editor
The camera starts properly and works fine. I can access the color, depth, and IMU data. However, when I click the Stop button in Unity3D, the Editor hangs for about 20 seconds.
Unity Build
If I export the project as a Windows standalone executable, the executable also works fine. However, when I click the Close X button, the window hangs for about 20 seconds.
Steps to reproduce

Create an empty Unity project and import the official RealSense Unity package.
Open the TexturesDepthAndColor sample.
In the RSDevice Editor field, add the Accel and Gyro streams.
Click Play.
Notice that the demo works fine.
Click Stop.
Hangs!

Here's the Editor configuration:

Execution time
I've measured the execution time when disposing of the pipeline in the RsDevice.cs file:
var sw = new System.Diagnostics.Stopwatch();
sw.Start();

m_pipeline.Dispose();
m_pipeline = null;

sw.Stop();

Debug.Log($"Elapsed milliseconds: {sw.ElapsedMilliseconds}");

If the IMU is enabled, the code above prints 21057 milliseconds. If the IMU is not enabled, the code prints 1072 milliseconds.

Hi @Vangos  This issue with a 20 second delay when closing a Unity session that had been using the IMU has been reported before in 2020.
https://github.com/IntelRealSense/librealsense/issues/5993
At the time, the possibility that it was a bug was considered but as there were no further reports of the issue from other RealSense users, no further action was taken.
The RealSense user who created that case provided a method for recreating the issue.
https://github.com/IntelRealSense/librealsense/issues/5993#issuecomment-598290523
As more than one person has now reported this problem, I will seek advice from Intel about it.  Thanks for the report!

Thanks for your response. Just to address potential questions:

Using the latest SDK (2.45.0).
Using the latest firmware.
No custom calibration.

Thanks again @Vangos - I will update here when I have received a response from Intel.

Hi @Vangos  After discussion with Intel, I have filed an official feature request with Intel to investigate this IMU time-delay issue with the Unity wrapper.  This case should be kept open whilst the feature request is active.  You do not need to take further action though.  Thanks for the report!

Thank you very much :-)

I have also experienced this problem as described, using a D455.
An even easier way to reproduce it is to remove all streams from the RsDevice "Profiles" list. This causes the device to default to sending all 4 streams (Color, depth, gyro, accel), and you'll see the 20 second hang when you stop the editor.

Version 2.49 has resolved this issue for me, both regarding the Unity Editor and reading a standalone build.
Tested on Windows, macOS, and Linux. Works fine!
Anyone facing this issue should update to version 2.49.
@MartyG-RealSense Thank you for your support!

Hi @Vangos  It's excellent to hear that SDK 2.49.0 resolved your problem!
As there is an active internal Intel report involving IMU delay in Unity that is linked to this case, the case should be kept open until that report is concluded.  You do not need to take any further action though, and I will update Intel about your success.  Thanks again!

I tried updating the Unity plugin to 2.49.0 but am still seeing the issue unfortunately, at least in the Editor:

Hi @BlueprintBen   Can you confirm whether you updated the Unity files to 2.49.0 by downloading and running the Intel.RealSense.unitypackage file from the 'Assets' file list on the SDK 'Releases' page, please?
https://github.com/IntelRealSense/librealsense/releases/tag/v2.49.0

If you did use this Unity package and the delay on exit remained, would it be possible to upgrade to the new SDK 2.50.0 and similarly use the Unity package from its Assets list to see whether it makes a positive difference?
https://github.com/IntelRealSense/librealsense/releases/tag/v2.50.0

Thanks very much @BlueprintBen for your report.  I have updated the internal Intel report about this issue with details of your experience of delay in 2.49.0 and 2.50.0.  There is no further advice that can be provided about the issue at this time.


[ko] Update apt repo GPG key URL

English PR https://github.com/kubernetes/website/pull/42156/files

Explicit hold to avoid accidental merges of (current) incorrect changes.
/hold

Yes, there is something wrong.

/remove-area blog release-eng
/remove-language de en es fr hi id it ja pl pt ru uk vi zh
/remove-sig release


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_bc79b97d-5c02-4b88-a6af-4d203c4d55d4/pull/1 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target_bc79b97d-5c02-4b88-a6af-4d203c4d55d4.git

Docs Build status updates of commit c29645d:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-UserAccountBuildPermissionInsufficientError] Owner v-alji no longer has Read permission of the repository https://github.com/opstest2/docs-archive-test-source. It might be due to recent GitHub changes on SSO. Please ask the owner v-alji to logon to Docs Portal https://ops.microsoft.com once again. If it is not the case, please ask anyone of Admin permission of the repo to assign a new owner via Docs Portal https://ops.microsoft.com

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Datetime time zone issue

When displaying datetime in KIP, I selected the local timezone (Central US, i.e. "America/Chicago") which shows correctly.   But when I view KIP remotely in another time zone (Eastern US), the KIP display shows my local time (Eastern US) even though the setting clearly has another time zone selected (Central US).  This behavior is the same for both the Safari and Chrome browsers. I tried selecting a west cost time zone (Pacific US) and still the time reverts to local.   It appears that this is true for all time zones except for "UTC" which when selected shows the proper zulu time.

Hi. Thanks for the report!
Could you share how and where you set the origine time zone?
Note that the date/time conversion   Ruled uses the browser and OS configuration on the computer running KIP. Maybe the other computer, or the one running Signal K are not configured with the same time zones?
Think of it this way: if the SK server is configured as a computer  located in Japan, and its physically recording time in the US. The date will appear ok in SK and when running KIP on that server. But if you access KIP from another computer set to a different time zone then the SK box, the base date from SK will be from Japan, the computer will adjust to its OS time zone, then KIP will translate to the time zone you set in the widget.

We need to check all settings first and see where the problem is.

One way is to share the string SK sends.

Hi,
When adding the time field to KIP, I used the Widget Options field for “Adjust Value to Time Zone” and selected “America/Chicago”.    I then saved the configuration and load that configuration from another remote browser.  On the remote browser, the Widget Options field still lists “America/Chicago” but I am now located in Eastern Time which is what it defaults to.
My fix was to just change the widget lable to “Local Time” rather than “Central Time”.   It not a problem, I thought I would point out the quirkiness of this.
Thank to all  for all you do.
--
Paul
￼

On Feb 14, 2024, at 8:09 PM, David G @.***> wrote:
Hi. Thanks for the report!
Could you share how and where you set the origine time zone?
Note that the date/time conversion Ruled uses the browser and OS configuration on the computer running KIP. Maybe the other computer, or the one running Signal K are not configured with the same time zones?
Think of it this way: if the SK server is configured as a computer located in Japan, and its physically recording time in the US. The date will appear ok in SK and when running KIP on that server. But if you access KIP from another computer set to a different time zone then the SK box, the base date from SK will be from Japan, the computer will adjust to its OS time zone, then KIP will translate to the time zone you set in the widget.
—
Reply to this email directly, view it on GitHub https://urldefense.com/v3/__https://github.com/mxtommy/Kip/issues/301*issuecomment-1945205174__;Iw!!PhOWcWs!3fFk5PeD_qW1h6EHRF39VbwXR9TiCa96KN-CFeaFIPxa9fvSt1FWFuF0oormmjA7C1LzOVfqzUj9_tc-LwLbNVI$, or unsubscribe https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ADDHBGZXB7HBB6IXDC5OYXTYTVN6PAVCNFSM6AAAAABDINTZCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBVGIYDKMJXGQ__;!!PhOWcWs!3fFk5PeD_qW1h6EHRF39VbwXR9TiCa96KN-CFeaFIPxa9fvSt1FWFuF0oormmjA7C1LzOVfqzUj9_tc-71pz6rw$.
You are receiving this because you authored the thread.

Oh. You mean the default widget label when you add the widget?
If this is what you mean, what do you think would be more obvious to indicate it should be adjusted according to the users setup? Just Widget label?
I'm all for making things more obvious!


Add custom id as field to the events table

Closes: #49
As Ralf suggested me did I last the combined primary field for the events table as it is.

I guess it only makes sense to store it in the database if we reuse it in the relay:
https://github.com/trustlines-protocol/relay/blob/master/src/relay/blockchain/events.py#L18
Probably instead of using
@property
    def id(self) -> hexbytes.HexBytes:

we should init the value of id in init to what the database gives us, or to keccak(self.transaction_id + self._block_hash + bytes([self._log_index])) if we receive nothing (in the case of pending blocks events). This will allow us to avoid computing the hash all the time.

At the moment I don't see a good reason to add this feature here anymore. Due to the combination of streamed and indexed events in the relay, it would require to duplicate the identifier calculation. Having such in two different repos would be obviously bad... The question is if there is an advantage having this field in the database. And such would exist only (in my eyes) if the clientlib/app would ask for indexed events by their identifier. Since they don't (I asked the app developer), I don't see a reason to add it to the database (having in mind that the app uses the transaction has as ID so far).
@cducrest any thoughts by you?

My thoughts is that it makes sense to store it in the database to avoid the work of computing it multiple times to the relay (every time the event is fetched). Even though the app / clientlib does not ask for historical events by their ids, the relay has to compute them to return them.
But since we will change the id anyway, we can close this.


Atalhos para Textos/Imagens

Description of the new feature / enhancement
Seria interessante ter atalhos no teclados para imagens e textos pré-definidos.
Scenario when this would be used?
Todos os cenários possiveis.
Supporting information
No response

(if I understand correctly) AutoHotkey is ideal to quickly insert pieces of text

/dup #1758

It is a good idea, just already captured by some other users. Check out this list of common issues. If you have more ideas, then you can see if anyone else has already suggested it and +👍 their issue.
https://github.com/microsoft/PowerToys/wiki/Common-Triage-Issue


[QBO] Ensure the actions to Add or Delete are not allowed on all imported coding pages

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v1.4.68-0
Reproducible in staging?: Y
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @trjExpensify
Slack conversation: https://expensify.slack.com/archives/C036QM0SLJK/p1714438462878199?thread_ts=1714400674.229349&cid=C036QM0SLJK
Action Performed:

Create a workspace on NewDot
Go to More Features > Tags > Enable (you need this step for now because otherwise Tags won't show in the LHN after you connect to QBO to see the imported coding, apparently that's going to be worked on here)
Enable Accounting in More Features as well
Go to Accounting in the workspace settings LHN
Connect to QBO
Go to Categories
Select a couple of category in the table
Click the [2 selected v] button in the page header
Observe the Delete categories button that shouldn't be there
Close the RHP modal
Click on a category in the table
Observe the three dot overflow menu in the category settings page in the RHP that shouldn't be there
Click the overflow menu
Observe the Delete category menu item that shouldn't be there.
Close the modal
Go to the Tags page
Observe the Add tag button in the page header that shouldn't be there
Repeat steps 7-14 above and observe that the admin can also delete imported tag values

Expected Result:
When coding features (Categories, Tags, Taxes) are imported from QBO, you shouldn't be able to Add or Delete the imported values. As such:

The green Add X button should be hidden in the page header
The Delete X menu item should be hidden in the bulk selection menu, only Disable X || Enable X should be shown.
The overflow menu in the category setting page should be hidden as the only menu item within it is to Delete x which shouldn't be allowed

Note: Untested but likely true given the above so please check on dev, and make sure we apply the same fix to Taxes imported to the workspace as well.
Actual Result:
Admins can Add and Delete imported coding values when connected to QBO
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
N/A
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/16232057/1e086d82-7aa1-49ef-a2a7-6af94534750b
View all open jobs on GitHub

CC: @aldo-expensify @hayata-suenaga @zanyrenney @narefyev91 @teneeto

we need to fetch connections data on those pages. Let me create a custom hook to do that. We cannot use the existing HOC as that is going to break the offline pattern on those pages.

we need to fetch connections data on those pages. Let me create a custom hook to do that. We cannot use the existing HOC as that is going to break the offline pattern on those pages.

Out of curiosity, how are we hiding the Add category button already when connected to QBO? 🤔

Out of curiosity, how are we hiding the Add category button already when connected to QBO? 🤔

because we're already fetching the connections data with HOC. But we decided to remove this HOC as it breaks the offline pattern on Categories and Tags pages.
I'm creating the custom hook so that we don't have to block the screen when the user is offline.
anyway, I can work on this issue while waiting for that PR to be merged.

Sounds good!

@hayata-suenaga did your PR also take care of imported tax rates as well?

My PR doesn't prevent the user form deleting taxes
@SzymczakJ is working on the PR linked above. @SzymczakJ can you handle the prevention of tax deletion when there is QBO connection (QBO connection and the country is not US)

My PR doesn't prevent the user form deleting taxes

What about adding tax values manually as well?

My PR doesn't prevent the user form deleting taxes

What about adding tax values manually as well?

That's also something we have to do. Thank you for reminding me of that 🙇

Couple of things to close this out, Melv:

This PR for taxes: https://github.com/Expensify/App/pull/41785
A PR follow-up from Hayata for removing Add tags when connected to an accounting solution

A PR follow-up from Hayata for removing Add tags when connected to an accounting solution

@trjExpensify, hiding Add tags button when there is an accounting connection is going to be handled in this PR

Hm, oh really? @SzymczakJ can you confirm?

@trjExpensify, the following change from the linked PR makes the Add tags button hidden when there is an accounting connection 😄

@SzymczakJ can double confirm

@SzymczakJ can you confirm?

I'm confirming 😃. I'll reopen that PR tomorrow morning

@SzymczakJ can you confirm?

I'm confirming 😃. I'll reopen that PR tomorrow morning

@SzymczakJ, do you mean this PR that was closed? I took the screenshots above from the PR.

Yep, we're working through this PR now: https://github.com/Expensify/App/pull/42192
The merge free branch getting merged closed the original one.

The PR for this issue was deployed and the taxes follow-up is being taken care of in Xero, so we're good to pay this tomorrow and close it out.

Alright, so payment summary:

$250 to @s77rt for the C+ review of this PR.

I've sent an offer.

@trjExpensify Accepted! Thanks!

Paid!


Add variable substitution to refer to a specific root folder of a multi-root workspace

Currently, the settings provide the substitution ${workspaceFolder} for finding the root of the currently active folder. For some projects, you may wish to refer to a different root folder of a multi-root workspace; an example of this: ~/projects/myApp depends on ~/projects/myNpmPackage.
With the above scenario, the myApp.code-workspace will look as follows:
{
    "folders": [
        {
            "name": "my-npm-package",
            "path": "~/projects/myNpmPackage"
        },
        {
            "name": "app-that-deps-on-package",
            "path": "~/projects/myApp"
        }
    ]
}

It would be nice to have the ability to reference another workspace root for things such as source mapping with the msjsdiag.debugger-for-chrome extension. A syntax for this could be along the lines of ${workspaceFolder:<folder-name>}.
Using the aforementioned syntax in ~/projects/myApp/.vscode/launch.json could look like this:
{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Debug My App in Chrome (Launch)",
            "type": "chrome",
            "request": "launch",
            "preLaunchTask": "build-npm-package",
            "sourceMaps": true,
            "webRoot": "${workspaceFolder}",
            "pathMapping": {
                "/myApp/node_modules/myNpmPackage": "${workspaceFolder:my-npm-package}",
                "/myApp": "${workspaceFolder}/public"
            }
        }
    ]
}

This yields the following advantages:

I no longer have to worry about the relative location of the myNpmPackage folder when writing tasks, and can instead simply update myApp.code-workspace
In tasks.json, I can now create the build-npm-package task to build myNpmPackage and copy any changes into the node_modules folder of myApp, avoiding having to manually copy anything
I no longer have to open two copies of source files from myNpmPackage while debugging, and am less likely to accidentally edit the node_modules version since it won't open when stepping through
I can use workspace settings that can refer to multiple root folders in myApp.code-workspace
These substitutions would make consolidating task.json or launch.json files into a single config easier if desired (or if a multi-root workspace supports a workspace-wide tasks.json or launch.json in the future)

Yes, support for root-folder based variables is planned under this umbrella item: #38134

My search skills failed me when trying to find if that was already submitted. Thanks!

Closing as duplicate of the umbrela.
@winglerw28 we will keep your feedback in mind when we look into closing the umbreal item. Thank you


feat!: Update kube dependency to v0.94

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Files with missing lines
Coverage Δ

src/manager.rs
97.83% <ø> (ø)


Execute_script doesn't wait for argument elements to exist

Expected Behavior -
Browser#execute_script waits for argument elements to exist.
Actual Behavior -
Browser#execute_script doesn't seem to wait for its argument elements to exist.
It calls wd that calls assert_exists. assert_exists raises an error if element isn't found.
I think it would make sense to wait for elements to exist.

This seems reasonable. Any chance you want to make a PR? :)

I'll take a look at this and try to raise a PR.


Add CloneWithAddedFields method to logger

This lets us use structured logging.
For now, just use these fields in TestLogger,
as they'll be used in tests.
Also pare down TestLogBackend interface.

Can one of the admins verify this patch?

See https://github.com/keybase/kbfs/pull/1069 for where this'll be used.

@strib fyi

Can we just use context tags (and enable them in TestLogger) instead of adding a new mechanism?

I thought of that, but not everything uses contexts with logging -- in particular, the fuse debug logger doesn't. I suppose we could fix that, but that seems like a bigger job.
Also, this method moves us closer to structured logging, like what we do on the server side ( https://github.com/Sirupsen/logrus ), which seems easier to manage long-term. I was thinking that fields would be the general-purpose log concept, and context tags would be one way (but not the only way) of adding fields to a log entry.
What do you think?

Ok.  I didn't realize we wanted structured logging on the client.  I personally find readable logs easier to deal with while actively debugging a given device (fewer extraneous characters), but I can see other viewpoints.
For what it's worth, I think it should be relatively straightforward to make the fuse logger use CDebugf instead of Debugf -- just rearrange this function to create ctx before setting fuse.Debug, and change it to call CDebugf instead.  The resulting logs wouldn't have the right per-request ID, but this way doesn't solve that problem either.  But it should solve the use case in https://github.com/keybase/kbfs/pull/1069.
I could see fields as being most useful in situations where a context is not being originated, such as the module name usage for FBO, if you prefer structured logging to human-readable lines.
Anyway, I'm ok with this concept, I just think it's overkill for the task at hand.

Okay, I'll rework this PR to just make TestLogger print out tags and do what you suggested about fuse.Debug, and see how far that gets me...

I think this is long superseded now; TestLogger already prints out tags.


Fallback for SKU if VariantName and attributes are missing

Variant's __str__ fallsback for sku if its name or display_attributes are missing.
close #1846
Pull Request Checklist
(Please keep this section. It will make maintainer's life easier.)

[ ] Privileged views and APIs are guarded by proper permission checks.
[ ] All visible strings are translated with proper context.
[ ] All data-formatting is locale-aware (dates, numbers, and so on).
[ ] Database queries are optimized and the number of queries is constant.
[ ] The changes are tested.
[ ] The code is documented (docstrings, project documentation).
[ ] Python code quality checks pass: pycodestyle, pydocstyle, pylint.
[ ] JavaScript code quality checks pass: eslint.

It was intended to be empty. We use display_product() method from variant to get product representation saved to OrderLine and it returns product name if variant's representation is empty. It prevents displaying duplicated SKU in order details view. But maybe we should find better solution to correctly display variants in many different places.

Recently we've been talking about dropping the variant name field as it doesn't seem to be very useful. A variant representation should be constructed of its attributes. Although our model allows it, I think having a variant without attributes doesn't make sense. I wouldn't change this behavior for now, but I think SKU is good fallback here.

@Pacu2 Is this PR still valid or does #2026 fix this by any chance?

@elwoodxblues this solves the problem until we make at least 1 attribute required per variant

@Pacu2 Could you fix the tests here?


Migrating Computers to New Site

When I move a computer, it only adds the entry on the new Jamf Pro, Is shows up as managed but I don't seem to be able to do anything with it.
Is there a way to push the new Jamf Pro MDM profile to the computer from the old Jamf Pro side ?  Or how are you completing the client side migration to the new MDM ?

Much like packages only the record is migrated to the new server.  Unenrolling/re-enrolling is outside the scope of jamf-migrator.  There are a variety of ways to do this, the following might provide some ideas:
ReEnroller


Update to last version (v3.6.0)

Especially the associated ReadTheDocs: https://biobb.readthedocs.io/en/latest/

Done


Not working, but few clues

I've had great success with Eventgen in the past, but recently I've had problems with 6.2.1 on a Mac. This all started when I updated from Splunk 6 to 7. I've blown away my Splunk install and have tried multiple different 7.x versions. Eventgen seems to start. Modinput_eventgen.log has entries and I can see Eventgen in settings/data input, but no eventgen.log is ever started - thus, I'm not sure what to look at. I've tried both the sample data sources and others. I've reinstalled several times with no success.

Just to clarify, eventgen on splunk 7, you've gone to "Settings > Data Inputs > Eventgen Mod Input" and made sure to hit "Enable" on it.  You also have TA's set to "GLOBAL".  Eventgen.log is now basically 3 logs, all placed in _internal.  You can actually just search them in splunk by doing: "index=_internal source=eventgen.log"

I also want to make sure you installed the eventgen from splunk base, or you downloaded this git repo and used the "build" command to create the SPL file that goes inside of splunk

Thanks Brian. I think my problems were two-fold. First, my company started
using SPlunk to monitor our laptops. For months, it didn't seem to
interfere, but I think now that something changed and there were conflicts
with port 8089. I went into SA-Eventgen's eventgen.conf and changed the
management port. The second issue was that I don't remember ever having to
enable anything under the Data Inputs... it just worked in the past. So, it
seems to be generating events now.
THanks for your help!
John
John Kruse<EMAIL_ADDRESS> 781.333.8349

"A complex system that works is invariably found to have evolved from a
simple system that worked. A complex system designed from scratch never
works and cannot be patched up to make it work. You have to start over with
a working simple system." – John Gall*

On Fri, Aug 17, 2018 at 11:03 PM Brian Bingham<EMAIL_ADDRESS>wrote:

I also want to make sure you installed the eventgen from splunk base, or
you downloaded this git repo and used the "build" command to create the SPL
file that goes inside of splunk
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/splunk/eventgen/issues/85#issuecomment-413987560, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACtpnwvEOfpveh7GDANUWDyh87WDApMiks5uRy-QgaJpZM4WBK1g
.

Understand John, to the point about "The second issue was that I don't remember ever having to
enable anything under the Data Inputs...", you're correct, it used to be enabled by default.  We had several customers accidentally send "eventgen" to a clustermaster, and would have an enabled modinput be pushed out to their indexers.  Eventgen 6 is the first time we've changed to having the modinput disabled by default.  As to the port issue, eventgen shouldn't be requiring any ports, so I'm not quite sure what you have going on there.

Thanks Brian. To be more specific, I wasn't able to run Splunk with the the
management port at 8089 as somehow my company's IT shop was binding that
port. So, I changed it to run on 8090. Then Eventgen wasn't working. In the
eventgen.conf file, there was a line splunkPort = 8089, so I changed it
to 8090 thinking that it was likely looking to align with the management
port.
Say, I've run into another snag. All of my old data sources used to be set
up on a 10 min cycle for replay purposes. Now, the events are not spaced
out per the original times embedded in each line, but all of them are
pretty much dumped within a second or so every 9 min. I thought that on
Replay, Eventgen was just reading thru the input file and parsing the time
and replaying with the same breaks between events as originally
experienced. This is happening with every Replay source. As a test, I shut
them all down and tried the included "sample.tutorial1" to see if I'd get
the same behavior. I changed the timeMultiple = 1, but otherwise left
everything alone. It seems to be doing the same thing every 16ish min. I
took a quick look and it seems that the events are spread over 15 min in
tutorial1. There also seem to be far more events than the 2019 lines in the
sample file.
*Any idea why Replay would be doing these big dumps on the approximate
periodicity of the entire file? *I never had to set anything special to get
this working and I'd assume that the tutorial1 files would work without any
fuss.
Thanks, John
[image: Screen Shot 2018-08-27 at 12.07.42 PM.png]
John Kruse<EMAIL_ADDRESS> 781.333.8349

"A complex system that works is invariably found to have evolved from a
simple system that worked. A complex system designed from scratch never
works and cannot be patched up to make it work. You have to start over with
a working simple system." – John Gall*

On Wed, Aug 22, 2018 at 11:31 AM Brian Bingham<EMAIL_ADDRESS>wrote:

Understand John, to the point about "The second issue was that I don't
remember ever having to
enable anything under the Data Inputs...", you're correct, it used to be
enabled by default. We had several customers accidentally send "eventgen"
to a clustermaster, and would have an enabled modinput be pushed out to
their indexers. Eventgen 6 is the first time we've changed to having the
modinput disabled by default. As to the port issue, eventgen shouldn't be
requiring any ports, so I'm not quite sure what you have going on there.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/splunk/eventgen/issues/85#issuecomment-414972120, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACtpnyWkZUUacbhs_tO413JQBwNBhOJ2ks5uTSTbgaJpZM4WBK1g
.

in eventgen 6 we clarified the meaning of "replaytimestamp" and changed the old logic of trying to "guess" which timestamp to actually use for event spacing.  Chances are your samples don't have a token with "replaytimestamp" in eventgen 6, and you just need to update the sample with the proper token / regex for your timestamp.  Let me know if you hit more issues on that.

Thanks Brian! That fixed my Replay sources, but now I have a question about
Sample sources.
In the past, I just set the interval=X and then would make sure there was
a field (e.g., a random integer) that would ensure each event was unique so
that Splunk wouldn't just ignore the events as redundant (I have a
predictable cycle of events for my testing). Has something changed with
that too? Each one of the Sample sources seems to execute when I first
restart Splunk, but then they seem to ignore my set interval.
I wouldn't keep bothering you, but frankly, the documentation and examples
on Github don't put the changes that have been made front and center. For
instance, only in Tutorial4 is "replaytimestamp" used, and it isn't really
featured in critical pages (e.g., the Configuration File section in
Tutorial.md). Basics.md also point to the old Clint Sharp Youtube video
that doesn't mention it. I am afraid that I'm missing another simple
setting that might have changed.
Thanks much, John
============================================
John Kruse<EMAIL_ADDRESS> 781.333.8349

"A complex system that works is invariably found to have evolved from a
simple system that worked. A complex system designed from scratch never
works and cannot be patched up to make it work. You have to start over with
a working simple system." – John Gall*

On Mon, Aug 27, 2018 at 1:06 PM Brian Bingham<EMAIL_ADDRESS>wrote:

in eventgen 6 we clarified the meaning of "replaytimestamp" and changed
the old logic of trying to "guess" which timestamp to actually use for
event spacing. Chances are your samples don't have a token with
"replaytimestamp" in eventgen 6, and you just need to update the sample
with the proper token / regex for your timestamp. Let me know if you hit
more issues on that.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/splunk/eventgen/issues/85#issuecomment-416333850, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACtpn9UY64TrvUu1Em60urxVI7NKIsEyks5uVEMygaJpZM4WBK1g
.

interval = how long to sleep to repeat the selection in seconds.  Meaning everytime you run a sample, there is a random selection of events out of the total number of events in sample mode.  Interval will just dictate how frequently to do it.  So if you have 2 events in your "sample" file, each time "interval" is called, eventgen will randomly select "count" out of that sample.  So if you set "count=1", you'd have a 50/50 shot of getting event 1 or event 2.  Set interval to 10, you have a 50/50 shot of getting event 1 EVERY 10 seconds, meaning by upping interval, you weren't decreasing the chance of seeing duplicate events, your just lowering/raising the cycle of selection.  Adding a higher count, will ALWAYS reduce the chances of selecting the same event, as it's not allowed to reselect the same event UNTIL every event has been used once.  So if your sample has 2 events, and you said "count=3", you're guaranteed that each event in the sample will be used 1 time, and 1 will be used twice.  Setting count to 0 will just cause sample mode to dump the entire sample every interval.  Hope that answers that question (and this logic really hasn't changed at all, it's much better about it's selection, and does things faster, but the same basic concept exists in eg5 and eg6)
Yeah I hear you about replaytimestamp.  It's actually something that's "only" mentioned in the spec files, as it was added over time (I want to say in eg5???) and quite frankly, the docs were never updated.
We're working a lot on the tutorials and docs just due the sure amount of questions we've gotten.  Don't feel bad, it's what i'm here for :D  Clint's video is definitely outdated, and I'll probably remove the link to youtube, sorry bout that :(

Lol so that actually has to do with the max_out, which we did change in 6.  Long story short, there was an internal event queue that would build up events then drop them all at once.  In eg 6 that queue still exists, but now is only used when you have like "count=100000" and is flushed after every completed interval.  Have I thrown enough wrenches at you to catch yet?  And yeah, this was part of the major pieces of EG6, was to provide way more clarity and structure to how EG works.  Now the next step is to get all these nice neat structures defined and listed for you guys in the documentation. ;)

Actually, I don't think that's it. My files are tiny - like 50 lines. Our
data sources are from device status reports generated every few min by
management tools (e.g., Solarwinds). Thus, I just want to do some
substitutions on certain fields and do a batch dump every 2 min using the
sample file over and over.
In the past, I think this worked because (according to the spec file) count
defaults to 0. Now, however, it is stopping after the sample is completed a
single time.
Any thoughts on why the Sample wouldn't start over? I was looking at the
Break parameter, but I'm not understanding what it does. I don't think
Bundlelines is what I want, as it isn't really a single "event".
Thanks, John
John Kruse<EMAIL_ADDRESS> 781.333.8349

"A complex system that works is invariably found to have evolved from a
simple system that worked. A complex system designed from scratch never
works and cannot be patched up to make it work. You have to start over with
a working simple system." – John Gall*

On Thu, Aug 30, 2018 at 12:55 PM Brian Bingham<EMAIL_ADDRESS>wrote:

Lol so that actually has to do with the max_out, which we did change in 6.
Long story short, there was an internal event queue that would build up
events then drop them all at once. In eg 6 that queue still exists, but now
is only used when you have like "count=100000" and is flushed after every
completed interval. Have I thrown enough wrenches at you to catch yet? And
yeah, this was part of the major pieces of EG6, was to provide way more
clarity and structure to how EG works. Now the next step is to get all
these nice neat structures defined and listed for you guys in the
documentation. ;)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/splunk/eventgen/issues/85#issuecomment-417429502, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACtpn8qEdYV20ZQyv4dwfqiJAs7LXuRzks5uWDU3gaJpZM4WBK1g
.

post your .conf if you can (or the entire app). To me that should just be a count 0, interval 120.  Make sure you don't have a "end" key, as "end=1" means only repeat the sample one time.  Also make sure to check the .log files from eventgen, and make sure it didn't thrown an exception.  There's a bug in 6.2 where if the timestamp can't be parsed on 1 row, it bails.

Hey Brian,
I tried to really boil down my eventgen.conf to the three Sample sources
that I'm having the most trouble with. They are now indexing and all seems
to be OK, but I had some odd problems. I wanted to tell you about my oddest
ones that I discovered just by doing some detective work with the conf and
sample files.

I had an old static date field that came right before the
Replaytimestamp field in a SAMPLE type source. It was formatted as such
"11/05/17 12:00". Despite the next field being the replaytimestamp, and I
had not set up a token to recognize that format, it kept indexing based on
those old 2017 date/times. It finally started working correctly when I
changed the field to the form "11/05/17T12:00". I don't know why the
inclusion of the "T" would cause it to not use the date for indexing, but
it worked.
I started adding my sources to the eventgen.conf one by one to figure
out what was going wrong. I have found that I can have a bunch of SAMPLE
types in a conf file and it works well. I can have a bunch of REPLAY types
together and they work fine. But if I put them together in the same conf
file, the SAMPLES will run once upon starting and then will stop, and the
REPLAYs will continue to chug along fine.

For this one, I'm going to try setting up a new app so that I have
one for SAMPLEs and one for REPLAYs.

If I have a file with just SAMPLE type, I have to make count=0 to
sample everything in the file. If I set a different number, it will just
keep sampling the same events over and over. So, if I set count=5, I can go
in after a few minutes and there will be multiple indexed events for the
same 5 source events and the rest will be ignored.

THanks for all of your help, John
John Kruse<EMAIL_ADDRESS> 781.333.8349

"A complex system that works is invariably found to have evolved from a
simple system that worked. A complex system designed from scratch never
works and cannot be patched up to make it work. You have to start over with
a working simple system." – John Gall*

On Thu, Aug 30, 2018 at 3:34 PM Brian Bingham<EMAIL_ADDRESS>wrote:

post your .conf if you can (or the entire app). To me that should just be
a count 0, interval 120. Make sure you don't have a "end" key, as "end=1"
means only repeat the sample one time. Also make sure to check the .log
files from eventgen, and make sure it didn't thrown an exception. There's a
bug in 6.2 where if the timestamp can't be parsed on 1 row, it bails.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/splunk/eventgen/issues/85#issuecomment-417474535, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACtpn12GUjfiIkW0x9TO3ZpzXchLZx2Uks5uWFp8gaJpZM4WBK1g
.

Here you go. The REPLAY entries for Eventgen.conf are in a file called
"eventgen.conf.hold". Each source has its own index, and they are
associated with an app that I can't share with you. They are listed below.
Have a great weekend and Thanks!
John
Name
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
ActionsType
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#App
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#Current
Size
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#Max
Size
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#Event
Count
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#Earliest
Event
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#Latest
Event
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#Home
Path
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#Frozen
Path
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Status
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
x_node_status_sw
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_node_status_sw?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_node_status_sw&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_node_status_sw?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_node_status_sw&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 402 MB 3.91 GB 12.1M 3 years ago an hour ago
$SPLUNK_DB/x_node_status_sw/db N/A
Enabled
x_ipsla_udpj_sw
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_ipsla_udpj_sw?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_ipsla_udpj_sw&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_ipsla_udpj_sw?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_ipsla_udpj_sw&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 16 MB 1.95 GB 725K 12 days ago an hour ago
$SPLUNK_DB/x_ipsla_udpj_sw/db N/A
Enabled
x_ipsla_tcpc_sw
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_ipsla_tcpc_sw?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_ipsla_tcpc_sw&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_ipsla_tcpc_sw?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_ipsla_tcpc_sw&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 16 MB 1.95 GB 730K 12 days ago an hour ago
$SPLUNK_DB/x_ipsla_tcpc_sw/db N/A
Enabled
x_ex_svrs_scom
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_ex_svrs_scom?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_ex_svrs_scom&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_ex_svrs_scom?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_ex_svrs_scom&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 2 MB 2.44 GB 5.44K 10 months ago a minute ago
$SPLUNK_DB/x_ex_svrs_scom/db N/A
Enabled
x_dc_util
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_dc_util?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_dc_util&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_dc_util?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_dc_util&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 5 MB 2.15 GB 29.9K 5 years ago a minute ago
$SPLUNK_DB/x_dc_util/db N/A
Enabled
x_dc_scom
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_dc_scom?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_dc_scom&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_dc_scom?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_dc_scom&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 6 MB 1.95 GB 43.2K a year ago a minute ago
$SPLUNK_DB/x_dc_scom/db N/A
Enabled
x_cto
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_cto?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_cto&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_cto?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_cto&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 4 MB 1.95 GB 28.3K 12 days ago a minute ago
$SPLUNK_DB/x_cto/db N/A
Enabled
x_crewstatus
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_crewstatus?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_crewstatus&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_crewstatus?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_crewstatus&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 3 MB 1.95 GB 13.7K 12 days ago a minute ago
$SPLUNK_DB/x_crewstatus/db N/A
Enabled
x_asi
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_asi?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_asi&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_asi?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_asi&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 3 MB 1.46 GB 21.5K 12 days ago a minute ago
$SPLUNK_DB/x_asi/db N/A
Enabled
John Kruse<EMAIL_ADDRESS> 781.333.8349

"A complex system that works is invariably found to have evolved from a
simple system that worked. A complex system designed from scratch never
works and cannot be patched up to make it work. You have to start over with
a working simple system." – John Gall*

On Fri, Aug 31, 2018 at 3:22 PM Brian Bingham<EMAIL_ADDRESS>wrote:

Some of these sound like I'll need to actually research, can you send me
your current app?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/splunk/eventgen/issues/85#issuecomment-417792477, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACtpn5qyER4SDVwJa3Xqruh3iCIGg7I6ks5uWakDgaJpZM4WBK1g
.

Brian,
I just tried moving all of the REPLAY sources into a separate app. It still
shows the same behavior as the SAMPLE sources run once, but the REPLAYs
continue.
Hope you had a good holiday.
Thanks, JOhn
John Kruse<EMAIL_ADDRESS> 781.333.8349

"A complex system that works is invariably found to have evolved from a
simple system that worked. A complex system designed from scratch never
works and cannot be patched up to make it work. You have to start over with
a working simple system." – John Gall*

On Fri, Aug 31, 2018 at 3:45 PM John Kruse, PhD<EMAIL_ADDRESS>wrote:

Here you go. The REPLAY entries for Eventgen.conf are in a file called
"eventgen.conf.hold". Each source has its own index, and they are
associated with an app that I can't share with you. They are listed below.
Have a great weekend and Thanks!
John
Name
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
ActionsType
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
App
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#Current
Size
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#Max
Size
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#Event
Count
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#Earliest
Event
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#Latest
Event
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#Home
Path
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#Frozen
Path
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Status
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
x_node_status_sw
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_node_status_sw?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_node_status_sw&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_node_status_sw?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_node_status_sw&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 402 MB 3.91 GB 12.1M 3 years ago an hour ago
$SPLUNK_DB/x_node_status_sw/db N/A
Enabled
x_ipsla_udpj_sw
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_ipsla_udpj_sw?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_ipsla_udpj_sw&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_ipsla_udpj_sw?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_ipsla_udpj_sw&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 16 MB 1.95 GB 725K 12 days ago an hour ago
$SPLUNK_DB/x_ipsla_udpj_sw/db N/A
Enabled
x_ipsla_tcpc_sw
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_ipsla_tcpc_sw?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_ipsla_tcpc_sw&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_ipsla_tcpc_sw?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_ipsla_tcpc_sw&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 16 MB 1.95 GB 730K 12 days ago an hour ago
$SPLUNK_DB/x_ipsla_tcpc_sw/db N/A
Enabled
x_ex_svrs_scom
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_ex_svrs_scom?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_ex_svrs_scom&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_ex_svrs_scom?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_ex_svrs_scom&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 2 MB 2.44 GB 5.44K 10 months ago a minute
ago $SPLUNK_DB/x_ex_svrs_scom/db N/A
Enabled
x_dc_util
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_dc_util?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_dc_util&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_dc_util?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_dc_util&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 5 MB 2.15 GB 29.9K 5 years ago a minute ago
$SPLUNK_DB/x_dc_util/db N/A
Enabled
x_dc_scom
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_dc_scom?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_dc_scom&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_dc_scom?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_dc_scom&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 6 MB 1.95 GB 43.2K a year ago a minute ago
$SPLUNK_DB/x_dc_scom/db N/A
Enabled
x_cto
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_cto?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_cto&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_cto?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_cto&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 4 MB 1.95 GB 28.3K 12 days ago a minute ago
$SPLUNK_DB/x_cto/db N/A
Enabled
x_crewstatus
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_crewstatus?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_crewstatus&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_crewstatus?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_crewstatus&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 3 MB 1.95 GB 13.7K 12 days ago a minute ago
$SPLUNK_DB/x_crewstatus/db N/A
Enabled
x_asi
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_asi?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_asi&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_asi?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_asi&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 3 MB 1.46 GB 21.5K 12 days ago a minute ago
$SPLUNK_DB/x_asi/db N/A
Enabled
John Kruse<EMAIL_ADDRESS> 781.333.8349

"A complex system that works is invariably found to have evolved from a
simple system that worked. A complex system designed from scratch never
works and cannot be patched up to make it work. You have to start over with
a working simple system." – John Gall*

On Fri, Aug 31, 2018 at 3:22 PM Brian Bingham<EMAIL_ADDRESS>wrote:

Some of these sound like I'll need to actually research, can you send me
your current app?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/splunk/eventgen/issues/85#issuecomment-417792477,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACtpn5qyER4SDVwJa3Xqruh3iCIGg7I6ks5uWakDgaJpZM4WBK1g
.

Brian,
I've been trying to move all of my sources over to being SAMPLEs just to
get things up and running. I'm getting this error consistently. I'm not
intentionally doing anything with Jinja (but maybe it is hidden behind the
scenes).
THanks, JK
9/5/18
9:04:38.000 AM
2018-09-05 09:04:38 eventgen ERROR MainProcess No module named jinja2
Traceback (most recent call last): File "/Applications/Splunk/etc/apps/SA-
Eventgen/lib/splunk_eventgen/eventgen_core.py", line 437, in _
initializePlugins module = imp.load_module(base, mod_name, mod_path, mod_
desc) File "/Applications/Splunk/etc/apps/SA-Eventgen/lib/splunk_eventgen/
lib/plugins/generator/jinja.py", line 9, in  from jinja2 import
nodes ImportError: No module named jinja2
John Kruse<EMAIL_ADDRESS> 781.333.8349

"A complex system that works is invariably found to have evolved from a
simple system that worked. A complex system designed from scratch never
works and cannot be patched up to make it work. You have to start over with
a working simple system." – John Gall*

On Tue, Sep 4, 2018 at 7:37 AM John Kruse, PhD<EMAIL_ADDRESS>wrote:

Brian,
I just tried moving all of the REPLAY sources into a separate app. It
still shows the same behavior as the SAMPLE sources run once, but the
REPLAYs continue.
Hope you had a good holiday.
Thanks, JOhn
John Kruse<EMAIL_ADDRESS> 781.333.8349

"A complex system that works is invariably found to have evolved from a
simple system that worked. A complex system designed from scratch never
works and cannot be patched up to make it work. You have to start over with
a working simple system." – John Gall*

On Fri, Aug 31, 2018 at 3:45 PM John Kruse, PhD<EMAIL_ADDRESS>wrote:

Here you go. The REPLAY entries for Eventgen.conf are in a file called
"eventgen.conf.hold". Each source has its own index, and they are
associated with an app that I can't share with you. They are listed below.
Have a great weekend and Thanks!
John
Name
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
ActionsType
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
App
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#Current
Size
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#Max
Size
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#Event
Count
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#Earliest
Event
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#Latest
Event
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#Home
Path
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#Frozen
Path
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Status
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
x_node_status_sw
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_node_status_sw?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_node_status_sw&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_node_status_sw?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_node_status_sw&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 402 MB 3.91 GB 12.1M 3 years ago an hour
ago $SPLUNK_DB/x_node_status_sw/db N/A
Enabled
x_ipsla_udpj_sw
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_ipsla_udpj_sw?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_ipsla_udpj_sw&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_ipsla_udpj_sw?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_ipsla_udpj_sw&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 16 MB 1.95 GB 725K 12 days ago an hour ago
$SPLUNK_DB/x_ipsla_udpj_sw/db N/A
Enabled
x_ipsla_tcpc_sw
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_ipsla_tcpc_sw?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_ipsla_tcpc_sw&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_ipsla_tcpc_sw?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_ipsla_tcpc_sw&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 16 MB 1.95 GB 730K 12 days ago an hour ago
$SPLUNK_DB/x_ipsla_tcpc_sw/db N/A
Enabled
x_ex_svrs_scom
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_ex_svrs_scom?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_ex_svrs_scom&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_ex_svrs_scom?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_ex_svrs_scom&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 2 MB 2.44 GB 5.44K 10 months ago a minute
ago $SPLUNK_DB/x_ex_svrs_scom/db N/A
Enabled
x_dc_util
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_dc_util?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_dc_util&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_dc_util?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_dc_util&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 5 MB 2.15 GB 29.9K 5 years ago a minute ago
$SPLUNK_DB/x_dc_util/db N/A
Enabled
x_dc_scom
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_dc_scom?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_dc_scom&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_dc_scom?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_dc_scom&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 6 MB 1.95 GB 43.2K a year ago a minute ago
$SPLUNK_DB/x_dc_scom/db N/A
Enabled
x_cto
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_cto?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_cto&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_cto?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_cto&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 4 MB 1.95 GB 28.3K 12 days ago a minute ago
$SPLUNK_DB/x_cto/db N/A
Enabled
x_crewstatus
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_crewstatus?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_crewstatus&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_crewstatus?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_crewstatus&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 3 MB 1.95 GB 13.7K 12 days ago a minute ago
$SPLUNK_DB/x_crewstatus/db N/A
Enabled
x_asi
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_asi?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_asi&ns=LeaderSA-App-624thAOC&action=edit
Edit
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes/x_asi?uri=%2FservicesNS%2Fnobody%2FLeaderSA-App-624thAOC%2Fdata%2Findexes%2Fx_asi&ns=LeaderSA-App-624thAOC&action=edit
Delete
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Disable
http://localhost:8000/en-US/manager/LeaderSA-App-624thAOC/data/indexes#
Events LeaderSA-App-624thAOC 3 MB 1.46 GB 21.5K 12 days ago a minute ago
$SPLUNK_DB/x_asi/db N/A
Enabled
John Kruse<EMAIL_ADDRESS> 781.333.8349

"A complex system that works is invariably found to have evolved from a
simple system that worked. A complex system designed from scratch never
works and cannot be patched up to make it work. You have to start over with
a working simple system." – John Gall*

On Fri, Aug 31, 2018 at 3:22 PM Brian Bingham<EMAIL_ADDRESS>wrote:

Some of these sound like I'll need to actually research, can you send me
your current app?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/splunk/eventgen/issues/85#issuecomment-417792477,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACtpn5qyER4SDVwJa3Xqruh3iCIGg7I6ks5uWakDgaJpZM4WBK1g
.

You can ignore that one, that's a traceback on an import, but it catches it safely.  "that's expected" when running inside of splunk.  If you want it to go away, download jinja2, and place it in your lib folder of sa-eventgen

Thanks. If it isn't hurting anything, I'm happy forgetting it.
On Wed, Sep 5, 2018, 10:29 Brian Bingham<EMAIL_ADDRESS>wrote:

You can ignore that one, that's a traceback on an import, but it catches
it safely. "that's expected" when running inside of splunk. If you want it
to go away, download jinja2, and place it in your lib folder of sa-eventgen
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/splunk/eventgen/issues/85#issuecomment-418795157, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACtpnxExVsSpLUe2PCNQMVaaN5WUR_gVks5uX_wDgaJpZM4WBK1g
.

Thanks Brian
On Thu, Sep 6, 2018, 17:20 Brian Bingham<EMAIL_ADDRESS>wrote:

Hey John, Haven't forgot about you, just trying to get some cycles to take
a look! Sorry but with .conf around the corner, we're all a little hectic
here :(
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/splunk/eventgen/issues/85#issuecomment-419272284, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACtpn49fDU9oJ_me4pbbaG31bEnzOP_pks5uYa3IgaJpZM4WBK1g
.

Hey Brian,
I went to your final session at .conf18. You had a good crowd for a final
session. I was going to say hi, but I had to get going to meet a colleague.
By way of feedback, it was a great conference and everything ran far
smoother than I would ahve imagined given the number of attendees.
I was wondering if you've had a chance to do check out any of this. If not,
I think I might roll back to an older version of Eventgen. I don't know if
there is a stable copy of 6.1 out there. Any ideas?
Thanks, John
John Kruse<EMAIL_ADDRESS> 781.333.8349

"A complex system that works is invariably found to have evolved from a
simple system that worked. A complex system designed from scratch never
works and cannot be patched up to make it work. You have to start over with
a working simple system." – John Gall*

On Thu, Sep 6, 2018 at 6:02 PM John Kruse, PhD<EMAIL_ADDRESS>wrote:

Thanks Brian
On Thu, Sep 6, 2018, 17:20 Brian Bingham<EMAIL_ADDRESS>wrote:

Hey John, Haven't forgot about you, just trying to get some cycles to
take a look! Sorry but with .conf around the corner, we're all a little
hectic here :(
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/splunk/eventgen/issues/85#issuecomment-419272284,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACtpn49fDU9oJ_me4pbbaG31bEnzOP_pks5uYa3IgaJpZM4WBK1g
.

I’m actually looking at it today / tomorrow! lol funny you should ask!  I’m trying to get prepped to ship out 6.3, and I want to make sure there’s nothing in this issue that would hold it up

On Oct 16, 2018, at 1:14 PM, John Kruse<EMAIL_ADDRESS>wrote:
Hey Brian,
I went to your final session at .conf18. You had a good crowd for a final
session. I was going to say hi, but I had to get going to meet a colleague.
By way of feedback, it was a great conference and everything ran far
smoother than I would ahve imagined given the number of attendees.
I was wondering if you've had a chance to do check out any of this. If not,
I think I might roll back to an older version of Eventgen. I don't know if
there is a stable copy of 6.1 out there. Any ideas?
Thanks, John
John Kruse<EMAIL_ADDRESS>781.333.8349

"A complex system that works is invariably found to have evolved from a
simple system that worked. A complex system designed from scratch never
works and cannot be patched up to make it work. You have to start over with
a working simple system." – John Gall*

On Thu, Sep 6, 2018 at 6:02 PM John Kruse, PhD<EMAIL_ADDRESS>wrote:

Thanks Brian
On Thu, Sep 6, 2018, 17:20 Brian Bingham<EMAIL_ADDRESS>wrote:

Hey John, Haven't forgot about you, just trying to get some cycles to
take a look! Sorry but with .conf around the corner, we're all a little
hectic here :(
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/splunk/eventgen/issues/85#issuecomment-419272284,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACtpn49fDU9oJ_me4pbbaG31bEnzOP_pks5uYa3IgaJpZM4WBK1g
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/splunk/eventgen/issues/85#issuecomment-430363507, or mute the thread https://github.com/notifications/unsubscribe-auth/ACJUgQaNi0TpOF2Lnt6HGjNDVDZ0aSdcks5uljAlgaJpZM4WBK1g.

Sometimes my psychic powers are astounding!
Thanks
On Tue, Oct 16, 2018, 14:06 Brian Bingham<EMAIL_ADDRESS>wrote:

I’m actually looking at it today / tomorrow! lol funny you should ask! I’m
trying to get prepped to ship out 6.3, and I want to make sure there’s
nothing in this issue that would hold it up

On Oct 16, 2018, at 1:14 PM, John Kruse<EMAIL_ADDRESS>wrote:
Hey Brian,
I went to your final session at .conf18. You had a good crowd for a final
session. I was going to say hi, but I had to get going to meet a
colleague.
By way of feedback, it was a great conference and everything ran far
smoother than I would ahve imagined given the number of attendees.
I was wondering if you've had a chance to do check out any of this. If
not,
I think I might roll back to an older version of Eventgen. I don't know
if
there is a stable copy of 6.1 out there. Any ideas?
Thanks, John
John Kruse<EMAIL_ADDRESS>781.333.8349

"A complex system that works is invariably found to have evolved from a
simple system that worked. A complex system designed from scratch never
works and cannot be patched up to make it work. You have to start over
with
a working simple system." – John Gall*

On Thu, Sep 6, 2018 at 6:02 PM John Kruse, PhD<EMAIL_ADDRESS>wrote:

Thanks Brian
On Thu, Sep 6, 2018, 17:20 Brian Bingham<EMAIL_ADDRESS>wrote:

Hey John, Haven't forgot about you, just trying to get some cycles to
take a look! Sorry but with .conf around the corner, we're all a
little
hectic here :(
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/splunk/eventgen/issues/85#issuecomment-419272284
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/ACtpn49fDU9oJ_me4pbbaG31bEnzOP_pks5uYa3IgaJpZM4WBK1g

.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <
https://github.com/splunk/eventgen/issues/85#issuecomment-430363507>, or
mute the thread <
https://github.com/notifications/unsubscribe-auth/ACJUgQaNi0TpOF2Lnt6HGjNDVDZ0aSdcks5uljAlgaJpZM4WBK1g
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/splunk/eventgen/issues/85#issuecomment-430381481, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACtpnyqLar_Yqla-7qxKNj4NTkxuz5mxks5uljxEgaJpZM4WBK1g
.

6.3. has been shipped. Would appreciate if you can reconfirm the issue on that version.

@JohnKruse were you still having an issue?  Or we good to close this one out?

Closing this issue since we haven't heard back in a few months.  Feel free to reopen if I didn't get your issue fixed!


Use --no-prompt as appropriate and cap the maximum number of azure.yaml files to autodiscover

Fixes #1688
Also fixes an issue found by @weikanglim where, when this repository was opened, a huge number of azd processes were started up to get information about the "apps" (the azure.yaml files) in the workspace--from the templates.

VSCode Extension Installation Instructions

Download the extension at https://azuresdkreleasepreview.blob.core.windows.net/azd/vscode/pr/1933/azure-dev-0.6.0-alpha.1.vsix
Extract the extension from the compressed file
In vscode
a. Open "Extensions" (Ctrl+Shift+X)
b. Click the ...\ menu at top of Extensions sidebar
c. Click "Install from VSIX"
d. Select location of downloaded file

@weikanglim @vhvb1989 just for your awareness: the VS Code extension is making increased use of --no-prompt option

@karolz-ms Noted. Did discuss and mentioned this with @bwateratmsft recently.


How do I ... Build a release version of my binary

This seems like a silly question but I have tried passing options to vcpkg and cmake but my binary always comes out as x64-linux with debug.
How do I get my project to compile with CMAKE_CXX_FLAGS_RELEASE?
This is my process
cd vcpkg ./bootstrap-vcpkg.bat ./vcpkg install --triplet x64-linux cpprestsdk libmysql paho-mqtt openssl cd .. cmake -B build -DCMAKE_TOOLCHAIN_FILE=./vcpkg/scripts/buildsystems/vcpkg.cmake -DCMAKE_BUILD_TYPE=RELEASE cmake --build build
An example of the output is:
james@vm:~/dev$ file build/CMakeFiles/proj.dir/src/PROJ.cpp.o build/CMakeFiles/proj.dir/src/PROJ.cpp.o: ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV), not stripped

a) Did you try -DCMAKE_BUILD_TYPE=Release?  RELEASE will use CMAKE_CXX_FLAGS_RELEASE, but for cmake commands that compare the type literally, the case may matter - for example for selecting library variants.
b) What do you expect to see PROJ.cpp.o with regard to the build type? It is not an installed executable.
c) You may set environment variable VERBOSE=1 when you want to see verbose output from cmake --build build.
This seems to be mostly CMake aspects, not vcpkg aspects.

Apologies for spamming this project, it is all to do with CMake (a port from msbuild).  The verbose build prints the build command and -DCMAKE_BUILD_TYPE=Release does seem to be working but there are some default options that are conflicting with my own.
Thanks for pointing me in the right direction


Support other file types besides .html

The generator has built in assumptions about all generated files being MD --> HTML.
However a website may have other files such as XML, SVG, or a simple robots.txt
It is desirable to support other formats as well with the data from schema (probably not quite with the markdown to content)

@KajKandler Sorry for the delay on this one, but I had some time today and got this working nicely. I'm getting a new release together now!


Editing host ip list is not recognized by scheduler

Rancher Versions: v1.4.0-rc8
Steps to Reproduce:

Add host
Edit host and add 2 IPs
Create load balancer to use both IPs

Results: Load balancer fails cause it thinks there is only 1 ip

Tested with v1.4.0-rc9. Adding/Editing scheduler IPs from the edit host option works correctly.
The IPs are reflected correctly in the UI and API and are recognized by the scheduler.


Want to use branches for next version

I installed the package today and used the howto to get started, didn't work. The documentation is based on the main branch, not the released nuget package. To avoid this I want to start using a branch for development, to keep the documentation in par with the released bits.

Using a development branch now


pcie: Remove deprecated functions

pcie_probe() and pcie_bdf_lookup() where deprecated before Zephyr 3.3. Time to remove them.

@dcpleung I had forgotten the release notes for this. Can you refresh your approval ?


Questions regarding user specific data

I have a question regarding setting up the data needed for GRF prediction based on user specific data. Regarding the acceleration data such as Sample_test_data.csv, I would like to know how that should be formatted. Is there a specific part of the leg that should be identified as the shank and what are the formatting requirements for the .csv. Regarding formatting requirements is there a sampling rate range, can multiple shanks be added...etc? Regarding footstrike I was hopping you could let me know how to create a footstrike file that the program can use based of acceleration data, a video, and subject information. Lastly, how can I get the grf data to be outputted as a excel file, or .trc, or csv?
In summary I basically would like to know how to format my files and data for the program if I have raw acceleration data, a video of the movement for two angles, and subject info like height and weight. I'd also like to know how to get the grf prediction results in a raw data format like excel, csv, or .trc.
Thank you for your time.

Regarding the acceleration data such as Sample_test_data.csv, I would like to know how that should be formatted.

I'm unclear on what your question is. Sample_test_data.csv is the example for how to format the data you'd like to test the prediction model with. Test_LSTM.ipynb utilizes this data file and provides more info about what it contains.

Is there a specific part of the leg that should be identified as the shank and what are the formatting requirements for the .csv.

README.md links to the manuscript with information about the location of the accelerometers.

Regarding formatting requirements is there a sampling rate range, can multiple shanks be added...etc?

Sure, but you'll need to retrain your prediction model to utilize this added signal.

Regarding footstrike I was hopping you could let me know how to create a footstrike file that the program can use based of acceleration data, a video, and subject information.

I think this is beyond the scope of a github issue.

Lastly, how can I get the grf data to be outputted as a excel file, or .trc, or csv?

The model output can already be exported to any text file format you'd like.


[BUG]:   AzureFileCopy@5 crashed with "The term 'New-AzStorageContext' is not recognized as the name of a cmdlet .."

New issue checklist

[X] I searched for existing GitHub issues
[X] I read pipeline troubleshooting guide
[X] I checked how to collect logs

Task name
AzureFileCopy@5
Task version
5.234.0
Issue Description
Ussing the following code:

task: AzureFileCopy@5
inputs:
SourcePath: '$(System.DefaultWorkingDirectory)/App.zip'
Destination: 'AzureBlob'
storage: 'name_of_the_storage'
ContainerName: 'name_of_the_container'
azureSubscription: 'ServicePrincipalName'
CleanTargetBeforeCopy: true

I only managed to get the following error:
##[error]The term 'New-AzStorageContext' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
Environment type (Please select at least one enviroment where you face this issue)

[X] Self-Hosted
[ ] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows Server
Relevant log output
Import-Module -Name C:\Users\abcdabcd\Documents\WindowsPowerShell\Modules\Az.Resources\1.9.0\Az.Resources.psd1 -Global
Disconnect-AzAccount -Scope Process -ErrorAction Stop
Clear-AzContext -Scope Process -ErrorAction Stop
##[error]The term 'New-AzStorageContext' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
Finishing: AzureFileCopy

Full task logs with system.debug enabled

 [REPLACE THIS WITH YOUR INFORMATION]

Repro steps
No response

I also encountered the same situation :(

Also facing the same issue with AzureFileCopy@6

Also facing the same issue with AzureFileCopy@6

The fix is mentioned in https://github.com/Azure/Azure-Sentinel/issues/10525

Also facing the same problem. How is everyone working around this?

The fix is mentioned in Azure/Azure-Sentinel#10525


Support Location Providers

Closes #861.
As the issue suggests, introduces a LocationProvider interface with the default and object-store-optimised implementations (the latter can be enabled via the newly-introduced table properties). This is pluggable, just like FileIO.
Largely inspired by and consistent with the Java implementation.

@Fokko (maybe @kevinjqliu also?) I've smoke-tested these changes locally with a catalog (hashing is the same as the Java implementation too), would love to get a first pass of this if you have a moment!
Tests will come soon of course - can't seem to get integration tests to work locally, that's all. Maybe unit-tests for hashing is all that's required, but I feel like an integration test(s) would be nice to make sure it's wired up correctly.

@Fokko, think this is ready for review now!
I've implemented this for write codepaths - add_files seems like it should just add the files specified without transforming locations.