So here are some of my findings. Take this file:

html

 Column Test

function fail() {
 throw new Error();
}

function logColumn(c, e) {
 const lines = e.stack.split(/\r?\n/g);
 if (lines[0] === 'Error') {
 lines.shift();
 }
 console.log(c, parseInt(lines[1].match(/:\d+:(\d+)/)[1]));
}

try {
 /* xxxxx */fail();
} catch (e) {
 logColumn("x", e);
}
try {
 /* ☃☃☃☃☃ */fail();
} catch (e) {
 logColumn("☃", e);
}
try {
 /* 🔥🔥🔥🔥🔥 */fail();
} catch (e) {
 logColumn("🔥", e);
}
try {
 /* 👩👩👧👩👩👧👩👩👧👩👩👧👩👩👧 */fail()();
} catch (e) {
 logColumn("👩👩👧", e);
}

The calculated offsets of the `throw` keyword are the following (utf-8 offset, utf-16 offset, unicode character offset):

/* xxxxx */: 14/14/14
/* ☃☃☃☃☃ */: 39/19/19
/* 🔥🔥🔥🔥🔥 */: 29/19/14
/* 👩👩👧👩👩👧👩👩👧👩👩👧👩👩👧 */: 99/49/34

What browsers report:

**Safari:**
* x – 18
* ☃ – 23
* 🔥 – 23
* 👩👩👧 – 53

**Firefox:**
* x 14
* ☃ 19
* 🔥 14
* 👩👩👧 34

**Chrome:**
* x 14
* ☃ 19
* 🔥 19
* 👩👩👧 49

**Edge:**
* x 14
* ☃ 19
* 🔥 19
* 👩👩👧 49

**Node:**

* x 14
* ☃ 19
* 🔥 19
* 👩👩👧 49


Really nice data and +1 for the set of test cases! Since Chrome/Edge/Node/Deno are all V8 under the hood, their consistent behavior is expected. I'm pretty sure the JS engines populate this property without involvement (by default) from embedding runtimes/browsers. It's really:

* V8 (UTF-16)
* JavaScriptCore (UTF-16 + "what's a call site" 4)
* Spidermonkey (UTF-32)

So no two engines actually agree in this case, although V8 and JavaScriptCore disagree on something not related to column offset calculations.

Btw, I'm not sure if it's still maintained but eshost-cli could be a nice way of running these test cases across runtimes: URL If nothing else, the page with Supported Hosts is a nice potential checklist.


Fixed in 0.69 which was released in the start of April 2023.


Turns out I needed to upgrade the other `@storybook` deps too. For anyone solving this issue, here is what I needed.

 "@storybook/addon-actions": "^7.0.9",
 "@storybook/addon-knobs": "^7.0.2",
 "@storybook/addon-links": "^7.0.9",
 "@storybook/addon-ondevice-actions": "^6.5.3",
 "@storybook/addon-ondevice-knobs": "^6.5.3",
 "@storybook/react-native": "^6.5.3",
 "@storybook/react-native-server": "^6.5.3",

 "react-native": "0.69.8",

In `metro.config.js`:

`config.resolver.resolverMainFields = ['sbmodern', 'react-native', 'browser', 'main'];`

The last 3 values are the default for React Native.

And for the record, this is an ejected Expo app. Now working fine without any errors. Thank you for your work on this! ❤


I'm going to close this issue in favour of #128, however feel free to keep replying here if necessary.


BRAW Toolbox v1.1.1 is now on the Mac App Store with the following changes:

<img width="1415" alt="image" src=" URL


Given that this is mostly determined by browsers I will skip evaluating what the generators currently output. From my experience at processing a lot of source maps at Sentry, the general consensus is pretty strong for it to be counted in UTF-16 offsets.


If someone is available to volunteer, it'd be great to see this analysis of generators. The goal is to get in the habit of testing sourcemap generators anyway, so we can file bugs against them and get everyone aligned. Also this is something of an edge case, so I wouldn't be shocked to see someone who we should already file a bug against (as soon as we agree on the definition)--so this testing should be directly useful for that.


OK, so I'd venture and dare to say: don't use McAfee. There are better AV solutions out there.
I know it's not what some people want to hear, though :-)


@jsafrane the nfs one should run as `--set feature.enableVolumeMountGroup=false --set feature.fsGroupPolicy=File`, maintaining two drivers would cost more efforts while it should be more compliant, since you are the openshift owner, it's up to you.


@glharper
I've tried version 1.28 but I get the same error. I have contacted Cloudflare on Discord, but no luck!


Can users impacted provide the trace following the steps below to help us understand why the process launches are slow on your device, thanks!

* Open `Windows Performance Recorder` from system start menu
* Have the following settings

Screenshot 2022-08-23 200440

* Start the recorder
* Open the application
* Once the editor has completely loaded, stop the recorder and save the profile
* Send the profile to Deepak.Mohan@microsoft.com instead of attaching to this issue, since it will contain sensitive information.


@rodbs I'm closing this issue, as it's morphed beyond anything that the SDK itself can address. If you come up with any code-resolvable issues, feel free to open a new issue. Thanks again.


Also running into these deadlocks on recent versions of nixpkgs.


So has btdig implented something to detect jacket searches somehow? What is the relation to domflow.it?

Seems to me that btdigg is intentionally redirecting jackett searches to a dummy domain, probably to force people to use their site directly. It's possible that the redirect is happening at the cloudflare level. To fix this will probably require changing the way jackett indexes btdigg to avoid detection.

Can someone point me in the right direction on where in the jackett repository we should be looking in order to modify the code for how jackett uses btdigg? I'd like to take a crack at this. Thanks


Slow and unresponsive startup is temporarily solved by excluding the code.exe file from mcafee realtime scanning. This has to be done daily though. I just bought mcafee for another year, what to do?


Honestly, I would uninstall it and install Avast Free from the offline installer URL
But YMMV.


@Johng117 this didn't happened with me. Once I excluded the code.exe file I didn't need to do it again. but I remember that I only need to do that when I update vscode then I need to exclude it again. it's not a big deal for me and I am okay with it.


Yeah, its not that big a deal. VsCode seems to update daily for me though. I might try and see if I can limit the uploads to once a week?


@shae128 @pmrussell892 If possible you be able to share the definition / sample definition where this issue is still reproducible?

It's still possible to have this error if there is too much nesting in the data. i.e. more than 30 levels. But many cases are now generat8ing collection without this. For example, Here's Stripe API which used to have this limitation but with this change, generated collection from this now does not contain such error.


I haven't received any profiles yet, asked in URL it would be great if the affected users can provide one to help us move this issue forward, thanks!


Would you consider making it opt-in with some mechanism? Probably with an annotation like `@ByContent` or `@ContentBased` or something?


Yeah I'll consider it. I've held on to a "just do what data classes do except for the one thing" approach for this long, but there's an ever-growing list of interesting features to consider adding so maybe it's time to bite that bullet.

One small challenge is that I currently include the `poko-annotations` dep by default, but allow substituting a custom annotation. If I add more annotations, do I want to allow them to all be customizable, or just drop that feature and force the default annotations dep? Probably the latter but that's a breaking change.

Is Redwood using arrays for performance or another reason? I had the thought of wrapping your arrays in value classes with custom `equals` overrides, but that isn't supported yet and may be syntactically annoying for your use case.


It is for performance, yes. Some of our code runs inside a JS engine where `Array` translates directly to JS's native array whereas `List` is a few Kotlin classes wrapped around an `Array` which adds a lot of copies for things like expansion. Since the only types which interact with these arrays are generated classes, we don't need to worry about the ergonomics as much.


So Poko being JVM-only is probably going to block your adoption too? 😬


Well, yes. But that's fixable with some PRs!

Wanted to make sure use cases were covered first. Although we only need this for two or _maybe_ three types so writing equals/hashCode manually for them wouldn't have been the end of the world.


We validate the OpenAPI file using the validator at URL and it passes that validation. If there is a specific different validation tool that you are running or specific places where you think the indentation should be changed, please let us know.


Okay so for `/deposit_switch/get` and `/income/verification/documents/download` would you say that parameters is correctly indented, or indeed necesarry?

Even within the same file, the indentation is different to all the other endpoints featuring `parameters: []`

`/beta/credit/v1/bank_employment/get` has an `x-hidden-from-docs: true` which is not within a http method under a path. Is that correct?

I don't doubt you have automation. These endpoints are documented, but don't seem to work with URL when passed through URL being told to use examples.

Also when I try to use these endpoints using swagger generator I get errors like the following

{
 "message": "unknown format \"datetime\" is used in schema at path \"#/properties/initiated_date\""
}

which is a http 500 error.


Other tooling used (problematically) are things like postman

 "
 },
 "client_id": {
 "value": " "
 },
 "secret": {
 "value": " "
 }
}

which is what happens if I try to import ` URL (currently `master`)


None of this is intended to be problematic. When I asked about OpenAPI2 support, I accepted that OAS3 is what we should work with. I Also accept this is difficult and new and a hard area and that PR's are not really worth it, as they then need to be translated to some program that generates that file. I Just want things to work and not cause issues. Using swagger generator and verifying calls to plaid via postman are two ways of troubleshooting that implementations in code match the API-spec contract as well as making calls direct to plaid to gain visibility.


Thanks, that is super helpful detail.

The `x-hidden-from-docs: true` I can fix (it doesn't even do anything, so we can delete that line)
The `parameters` indentation is also an easy fix (and again, I'm not sure it's even doing anything)
The `format: datetime` thing is something we already caught internally and it's fixed on master, so that should be rolled out with next month's release.

The Postman error seems like unfortunately a limitation in Postman rather than anything wrong with the API specification, so I don't think there's anything we can do about that. There are some suggested workarounds floating around online, e.g.: URL


From correspondance with @PipBrewer:

More from @kimstp :


After talking this through with @Sosannah we came to the following:

About half of the required metadata fields are already supported by Specify out of the box (see mapping table below).
The other half could in principle be added as singular records in the `attachmentmetadata` table of which multiple entries can be associated with a single attachment record. In the following, these will be referred to as "extra metadata" records.

| **Metadate field** | **Specify Table** | **Specify Field name** |**Notes** | **DarwinCore (Simple Multimedia extension)** |
|-------------------|-----------------|-------------------|----|----|
| Copyright owner | attachment | CopyrightHolder | | URL |
|Copyright license | attachment | License | | URL |
| Whether the attachment will be visible externally | attachment | IsPublic | | |
|Persistent identifier for media which is resolvable (link) | attachment | AttachmentLocation | Only the terminal end of a "persistent" identifier prefixed by the URL of the attachment server + collection name e.g. URL | URL |
|Date media created | attachment | FileCreatedDate | | URL |
|File format (jpeg, tiff etc) | attachment | MimeType | | URL | |
|Type/description of attachment (CT scan, specimen image etc) | attachment | Remarks / Type | | URL |
|Type of exception (see data access policy) | | | | |
|Person responsible for exception | | | | |
|Details of exception – e.g., requested by for x reason, authorized by | | | how big must the field be? | |
|Exception review date | | | |
|Date media deleted | | | |
|Deletion reason | | | how big must the field be? | |

**Generation of extra metadata records**
The question is how these extra metadata records can be created. We understood that the mass digitization pipeline process can be adapted to do that, and in principle we could add these extra metadata fields to the Specify Interface to enable manual editing. However, otherwise we can't think of an automatic process for doing that.

**Publication**
Although we are unsure of how many of these metadata fields will be parsed and visible on sites like GBIF, in principle the information _is_ published digitally online as the DarwinCore Archive generated by Specify7 (retrieved by GBIF). The DarwinCore (DwC) Archive is a zip file of csv files and can be both machine read and human read. The images are published in the archive as links that are accessible through the web asset server. _However_ only fields that can be mapped to DarwinCore fields can be made public this way. The currently used DwC Extension Simple MultiMedia does not (see above table), but Audubon Media Description may have better options.

**"Deletion"**
After discussion the matter of "deletion" with @PipBrewer it turned out that instead of actual deletion of attachments, rather a kind of modal "hiding" is meant where the actual image would be replaced by a thumbnail. However, we cannot see how an images is represented externally by a thumbnail yet internally by the actual image. Perhaps the replacement of the web asset server can be adapted to provide that functionality. For instance, the replacement web asset server could be programmed to represent the "deleted" image as a thumbnail to the outside, but as the actual image when requests originate internally.


@3nids would you be willing to compile the QEP discussions this year again?


Super helpful thanks. The workaround I'm picking out from that little thread might be

openapi2postmanv2 -s root.yaml -o collection.json -p -O folderStrategy=Tags,includeAuthInfoInExample=false,optimizeConversion=false,stackLimit=50

I've applied the fixes locally and just did a find replace for the hyphenation of date-time; It's more that I'd sooner not write automated tools; it's not just plaid, every vendor has... insert quirky thing 👍


Kotlin's decision to avoid special array-handling in data class equals functions is for JVM-specific reasons. Is it the case that JS native arrays are also not compared by content? Or are the Redwood classes targeting JVM along with JS?


Now with this issue on the horizon, we need to also think about how to proceed with the changes:
* opensearch-project/opensearch-dashboards#3601

This means:
* We have to deprecate ci image that uses centos7 or al2.
* Our ci and release docker images have to move from al2 to al2023
* #3351
 * Python upgrade from 3.7 to 3.9 must follow as al2023 is default to newer version of python
 * AL2 has python 3.7 by default but AL2023 is already bundled with 3.9. It would take longer time just try to compile Python 3.7 on AL2023.
* KNN will 100% break for certain old OS users if we still use the same docker image for 1.x / 2.x / 3.x, as centos7 is the pinnacle of KNN, as it has the oldest glibc version which does not support Node18.
 * URL
 * Unless we add a new jenkinsfile just for 1.x, we cannot tweak the existing dist-build-dashboards jenkinsfile too much as it is near the size limit of Jenkinsfile max size.
 * Adding a new jenkinsfile just for 1.x will break a lot of the internal hardcoded folder structure on S3
 * One way to avoid this is that OS has to use centos7 to build and OSD has to use al2023 to build, which is very unformalized and hard to maintain.
* This has to happen after Jenkins Upgrade complete
 * URL
* This is a major breaking change and seems like they are trying to backport to 2.x as well due to node14 is deprecated and we cannot ship a deprecated product.


Hello Everyone,

Thanks for the guidance. I have included `code.exe` file in the `excluded files` list in McAfee but i feel its not a good practice to do so. The purpose of antivirus is to scan the system for viruses etc.

Is there is a more feasible solution for this ?


I tested with extensions settings and starting up VS Code via `code --disable-extensions` is actually lot more faster even without including `code.exe` file in the `excluded files` list in McAfee. The above command temporarily disables extensions and clicking on `reload and enable extensions` as shown in screenshot below is loading all extensions as before.

Please see the screenshot below:
Extensions-Settings

I also tried with `Help: Start Extension Bisect` from Command Palette and opened this issue cmake related to cmake plugin

Thanks everyone


Correct. They mirror the JVM semantics. You must use contentEquals/HashCode/ToString to get the contents rather than the array reference to be used.

We target JVM, JS, and many native targets with this code, yes. The efficiency gains are paltry on non-JS platforms.


Even with a remote cache, if someone is running bazel locally and running bazel test would continue to generate runfiles right?

These runfiles would then accumulate and eventually bazel would halt? If anyone has a workaround besides pruning based on mtime and using a remote cache, would greatly appreciate the suggestion!


Following discussion with @FedorSteeman today:

1. We need to test whether we can easily import image records with a mixture of information from the main attachment record and the extra attachment metadata records (key/value pairs).

2. The publication information provided above is acknowledged. If the image metadata can't be accomodated by a publisher, I'm not concerned. If it can be acccomodated, we should try to map it.

3. There are 2 associated issues regarding attachments which should not be viewable on the web. For attachments which have been deleted in our storage system (web asset server), it sounds like we can still publish the attachment records (the metadata), but with a stand in thumbnail. This is "tombstoning" the record and meets our needs. For attachments where we would like to embargo or not show the attachment itself, but would like to show the metadata/attachment record, Specify does not currently support this. This is something that should be requested by the Specify community on behalf of DiSSCo. In the meantime, the DaSSCo website, could provide details on the number of records embargoed for transparency purposes.

I also discussed the two additional requirements needed - For all new attachment records that are created:
• If it is an image it should automatically be given a CC-BY licence unless it is associated with an exception in the metadata, or this is later changed manually.
• If it is a document, the attachment itself will not be visible externally.

4. Fedor advised that when anyone creates a new attachment record we could always default the licence to CC-BY. This we should be able to manually change after the effect if necessary.

5. For documents, there is no way to automatically mark new attachment records that are documents are to be not pushed to the web. For published datasets, this is being selected manually (i.e., only images and ones which are selected as being pushed to the web are) during the mapping phase.

WOuld it be possible to get an idea of timeline as to when A. the additional metadata fields can be added to teh attachment records and B. when we can test that we can do a workbench import using mutliple attachment tables (e.g., including the extra metadata fields)? Adding the licence automatically can come after them.


Follow on.

Fedor advised that You can't map attachment data in Workbench and neither attachment metadata
also need to add extra attachment fields to the data entry form

So additional work required:

- Add extra attachment fields to data entry form in Specify - will need doing
- Potentially script an import of attachment metadata into Specify BUT not until we have a concrete example and use case


cs
record struct SomeRecord(int X)
{
 // IDE0251:
 public bool Equals(CacheKey? other) => false;

 // IDE0251:
 public override int GetHashCode() => 0;
}


That's tough to answer with a yes or no, as there are really three questions with this one:

1. Does j2objc support all Java 17 language features?
2. Does j2objc support new Java 17 JRE API?
3. Does j2objc run on Java 17?

1) AFAIK, j2objc supports the latest language features, like text blocks and switch expression statements. Much of that support is free, because j2objc uses javac as its front-end; for example, javac converts text blocks into regular strings, so j2objc didn't need to be updated to support that feature.

2) No, J2ObjC's JRE is a fork of Android's libcore library (its JRE), so if it's not available in Android, it's not available on iOS. That's intentional, as the purpose of J2ObjC is to support shared Java across an app's clients, not to be a complete Java platform (that's why we don't/can't call it "Java").

3) No, because the javac team (see 1)) keeps changing access to its packages. So it works on Java 11, but it is currently broken on Java 17 until someone fixes the necessary flags (contributions welcome!).

The Android Gradle Plugin should be able to run command-line tools like j2objc in a separate shell (and likely already does). So try installing both Java 17 and Java 11 on your system, with the j2objc action defined by the flags in the j2objc.sh script. That script is also where the flags aren't correct for Java 17, so if you can fix them, great!


A hack I came up with was to wrap cells in an `mbox`. For example this style specification

 row{1} = {font=\itshape, cmd=\mbox}

causes every cell on row 1 to be wrapped in an mbox, thus suppressing hyphen breaking for any hyphens on row 1. Alternatively, `cmd = \exhyphenpenalty10000` also works, at least until the bug is fixed.


Some notes as I dive deeper – everything I mention here for data classes is also true for Poko classes:
* Data classes do consider content for array-typed properties when computing `hashCode` and `toString`. `equals` is the only one for which array content is ignored.
* Data classes do *not* consider content for `Any`-typed properties that are arrays at runtime when computing `hashCode` and `toString`, so Poko would need to implement its own handling for this.
* Data class handling of `hashCode` and `toString` for arrays is specifically built in to the IR compiler. Poko would need its own `arrayMemberEqualsSymbol`, and figure out how to map that to the platform-specific `Array.equals` equivalent (I think this is called "lowering"?).
* Need to decide whether to handle nested array types (`Array >`) – that would be `Arrays.deepEquals` on JVM, and the `hashCode` and `toString` implementations would need to be updated to do this too since they currently don't handle nested arrays. Incidentally, `deepEquals` *does* handle Array members even if they are typed `Any`.
* Kotlin's stdlib has `contentEquals` and friends defined in common code, so mayyybe this can be referenced without any platform-specific handling?

I added #135 to test the current handling of arrays in the sample project.


@stuartmorgan have you some expectation about a date to implement this feature?


For the Node 18 upgrade, we're targeting 2.8. This is important as Node 14 no longer will receive security updates (as of April 2023). Is there an ask to delay to solve the above?


Thanks for the answer 👍 We'll try it out in the coming weeks and see how we get on with it.


KNN support on the native code compilation:

node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by node)
node: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by node)
node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by node)
node: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by node)
node: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by node)
node: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by node)

# CentOS8/RockyLinux8
ldd (GNU libc) 2.28

# CentOS7
ldd (GNU libc) 2.17

# AL2
ldd (GNU libc) 2.26

# AL2023
ldd (GNU libc) 2.34

Seems like if we want to switch from CentOS7 to CentOS8, we will need to remove support of CentOS7 and AL2 from our support matrix on our website as well, since CentOS8/RockyLinux8 is the baseline of node18 with glibc 2.28.
 URL

 URL
cc: @krisfreedain


I would agree @peterzhuamazon - if we test on CentOS8/RockyLinux8 the compatibility matrix needs to be updated to accurately reflect that for the community


Hi @peterzhuamazon we will bump the node.js to version `18.16.0`


For first contributors to work on this you can do the next:
1. 🔍 Search for the keyword in the broken button (View On OpenSauced)
2. 🤔 Try to understand the component and code written within it.
3. 💭 Figure out where did we use this component Solution/spoiler 😄 The needed function: injectViewOnOpenSaucedButton
4. 👍 When you find the function related to this component, you can add extra logic to check whether it's the same logged-in user profile. (you can do this by finding a unique selector for user profile) Solution/spoiler 😄
You can do this by checking the Edit profile button, Solution/spoiler 😄
the related class selector: js-profile-editable-edit-button

@bdougie @Anush008 @diivi, what's your input about this? I am considering labeling it as a good-first-issue if it's clear and not blocking any business logic.


I tried but I have not found a place in the browsers where columns are displayed for CSS source maps, thus I was unable to determine based on observation in the browser how columns are handled. However libsass produces UTF-16 columns:

**foo.scss**

css
body {
 /*🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥*/background:/*🔥*/red;
 /*🔥🔥🔥*/color:/*🔥*/blue;
}

**foo.css**

css
body{background:red;color:blue}/*# sourceMappingURL=foo.css.map */

**foo.css.map**

json
{"version":3,"sourceRoot":"","sources":["foo.scss"],"names":[],"mappings":"AAAA,KAC8B,eAClB","file":"foo.css"}%

Decoded:

 0:0 -> foo.scss:0:0
 0:5 -> foo.scss:1:30
 0:20 -> foo.scss:2:12

If you look at the tokens referenced:

1:30 -> background:/*🔥*/red;
2:12 -> color:/*🔥*/blue;


tak už se nám to zase rozbilo - asi s tou opravou posouvání lišty. Když přesunu strany, uložím a dám zavřít, tak mám v úložišti krásně šedé prázdno - až po F5 se obsah načte.


I am affected by the same issue.

Unity project
Visual Studio Code 1.78.2
C# for Visual Studio Code (powered by OmniSharp) 1.25.7
Microsoft.Unity.Analyzers 1.15.0

Empty text for IDE0251 in "PROBLEMS" window, see attached screenshot, caused by the following code:

public struct DummyStruct
{
 public int DummyValue;

 // the "get" in the following line causes an IDE0251 notification
 public int GetDummyValue { get => DummyValue; set => DummyValue = value; }
}

IDE0251-empty-text


Funguje to dal. Akorat je tam vterina v sede. Nesouvisi to s tim posouvanim.
Stava se kdyz mam editor metadat. Hledam pricinu


@peterzhuamazon want to clarify, you are saying that node 18 requires 2.28, correct? Then doesn't this break compatibility with AL2 and centos 7? So, regardless of k-NN libs, upgrading to Node 18 would require us to remove centos 7 and AL2 from the compatibility matrix.

If this is not the case, we could also elect to compile k-NN libs in separate docker image to maintain compatibility.


@peterzhuamazon not sure if you saw this URL

unlike chromium, it is possible to do a custom build of nodejs on centos 7 to lower glibc dependencies (I also saw musl builds somewhere, which can be another possibility to workaround this issue). I've not looked into performance or other issues might be caused by downgrading glibc, but if OS upgrade is difficult maybe this would be easier?


Did anyone confirm node 18 with AL2? @seanneumann

We noticed some glibc related compatibility issues. Not sure if it's an isolated incident.


That is likely not an option because CentOS7 is going to be out of support in 1 year, and we are also on track to move to al2023 anyway. Manually rebuild nodejs18 would add another dep on our side, which is not going to scale on the long run.

Thanks.


Node 18 will not run on AL2; I tried it.

OSD 2.8 will be compatible with Node 14, 16, and 18. OSD 2.8 will also bundle Node 18 and a Node 14 for fallback; with this OSD 2.8 can run on AL2 by using the bundled Node 14.


1. It does, al2/centos7 have older libs than 2.28.
2. Agreed that we need to move out of centos7 and al2 at some point.


If node14 out of support can we even bundle a 14 alongside 18 together?


@peterzhuamazon I hate it but being a minor release, we have to.


No ona to nebyla vteřina, bez refreshe nám to nešlo. Ale dneska už je to OK, tak nevím, jestli už jsi s tím něco dělal, nebo se ProArc jen potřeboval prospat.


Zatim nic nedelal, ale chci to zlepsit. Ten editor metadat ted se nacita hodne dlouho. To je kvuli to rozbaleni...


Sounds good.

And can we demonstrate how to use it to create, say, a division or department meeting, where all Engineering specialists are invited ?


Yes we can build on it. A test drive mission encapsulates the key parts of a generic Mission.


Confirmed that calling common-code stdlib functions from generated IR code is supported, which simplifies this a lot. 🎉

I plan to:
1. Add the new annotation as an experimental API.
2. Implement `contentEquals` for all typed and primitive array types.
3. Handle `contentDeepEquals` for nested array types, updating `hashCode` and `toString` accordingly.
4. Handle `Any` properties that are arrays at runtime.
5. Flesh out the path forward for custom annotation consumers – probably deprecate this feature.


Can you put together an example by codes on how to create a team meeting ?


/duplicate

Marking as duplicate of URL Please let us know if McAfee is not installed on your PC, else use the instructions to resolve.


Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!


@venkatrahul-software-development please see URL

Indeed **anyone** with the problem could help by responding to that call for information by @deepak1556


Done, feel free to ask for help if you got stuck or needed any support, good luck 👍


Ted se pri obnoveni objevuje "loading bar" nahore, aby bylo jasne, ze obrazovka neztuhla, jen dumaaa :)


I have same issue
in locally it work perfectly but when i copy it into docker i have got an error

cmd
Error: Unable to launch browser, error message: Failed to launch the browser process!
 /usr/src/node_modules/puppeteer/.local-chromium/linux-1022525/chrome-linux/chrome: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory


This seems like an upgrade on urllib3 libs due to not supporting openssl version lower than 1.1.1+, where centos7 does not have now. We would need to speed up the process to upgrade to rockylinux8.


Need to move the integTest runner to rockylinux8 as well:
* URL


The newer version of requests cause a requirement update on openssl, from 1.1.0 to 1.1.1+, this means CentOS7 is not able to run newer version of request on any activities related to our python code.


Hi,

Option 1: Revert #3544 and keep using CentOS7 for this release
Option 2: Move all the changes to RockyLinux8 and remove CentOS7 support.

Consider our decision on the AL2023/NodeJS18/PythonUpgrade 3.9 has already made in this comment: URL

We will go ahead with option 1 and revert #3544.

cc: @bbarani @gaiksaya

Thanks.


Our test in #3544 is running in ubuntu-latest thus does not have the openssl issue in centos7, therefore, not caught.


hey @emerzon

Apologies thought I'd already replied to this one, I guess I wrote the comment but forgot to hit submit 😅

Internally the Provider has a number of expectations/requirements where a Provider Instance has a 1:1 relationship with a Subscription - as such whilst this has come up a few times over the years, unfortunately this isn't something we plan to implement at this point in time.

That said I totally understand the use-case here, and there's a feature request on Terraform Core which I think will solve this for you in a different manner - as such whilst this isn't something we plan to support at the Provider level, I'd encourage you to comment on/subscribe to this upstream issue tracking support for Dynamic Providers, since once support for this is implemented there then this should be usable with every Provider rather than just being tied to AzureRM.

Whilst I appreciate that's probably not the answer you're looking for, since this isn't something we plan to implement within the Provider I'm going to close this issue for the moment - but when this functionality is supported in Terraform (Core) then this should be usable across all Providers, which'll fix this in a different manner.

Thanks!


These three will need to get baseOS change to rockylinux8 before adding node18.
These are the only ones do not have node18 on docker images, AMI not affected.

docker/ci/dockerfiles/current/build.centos7.opensearch-dashboards.x64.arm64.dockerfile
docker/ci/dockerfiles/current/release.centos.clients.x64.arm64.dockerfile
docker/ci/dockerfiles/current/test.centos7.performance-test.x64.arm64.dockerfile


#929 is landing in a moment, after which I'll release it with a major version bump 🎉


Simple array content support is enabled in the latest `0.14.0-SNAPSHOT`, implemented in #141. Not sure if it's possible for Redwood to try it out on just the JVM, otherwise I filed #142 for multiplatform support.


It's possible you could do it in Firefox by having CSS that uses non-base-plane characters and then provokes a warning later on the same line. Then, look at the warning in the console. IIRC (it's been a while) the devtools will apply source maps in this case.


To drive this discussion forward, here is my proposal of what should be added to the spec:


Tested this today, and calling the API currently causes a runtime error when I call the API in Wing Console: "Unknown error: Missing environment variable: API_HANDLE_5f3a2e5e"


**REPRO:** I'm also getting the IDE0251 with no message, but no suggested fix after VS2022 upgrade to Version 17.6.2. This is the code fragment that's frowned upon (^^ mark the dotted underscores):

c#
record struct VoiceMarker(uint Start, uint Length) : IComparable {
 public uint End => Start + Length;
// ^^
 public int CompareTo(VoiceMarker v) =>
// ^^
 Comparer .Default.Compare(Start, v.Start); // Length is irrelevant.
}

The project file is unremarkable:

xml

 Exe
 net7.0
 disable
 enable
 True
 False


To suppress the message, add to `.editorconfig`:

ini
[*.cs]
# URL
dotnet_diagnostic.IDE0251.severity = none


This is related to: URL and URL

# Suggested solution:

1. 🔍 find a unique identifier for the profile menu, by doing the next:
2. 🕵 inspect the profile page, the bio and the edit button.
3. 👍 see if we can find a unique identifier to use it.
4. 🏥 review the code and the JS query selector to use that identifier

# Challenge

Let this work on your profile and other people's profiles.
For your profile, it will be under the bio information on top of the edit profile,
For other people's profiles

 😄 Hint

You might find a unique selector for the edit profile button
 Your own profile selector: show the selector

`btn-block js-profile-editable-edit-button`

 Other people profile selector:

`user-following-container`

 Use a condition maybe
You can check if the selector is not provided for your profile to trigger the selector for other people profiles, and add the button, in cases it will be need to be prepended.


@kiss81 It should be possible if we knew the zigbee commands for it. Sadly we don't. Someone with an official ECU can provide this data with a zigbee sniffer, so far no volunteer has come forward.


Would it be possible to get an updated timeline of when things can be implemented in Specify, so I can update the DaSSCo Steering Group in the next couple of weeks and inform KU management when we can implement the policy?


Many of these questions are answered here:
 URL

Extra attachment fields to data entry form in Specify can be created/tested on this week, preferably not later than 1st of June.

Next step will be investigating the existing DarwinCore (DwC) extensions to publish the metadata (or at least part of it) as a DarwinCore Archive.


Dear devs, please have a look at the mini summaries of your proposals above and let me know if any need to be changed.

cc @gioman @elpaso @nyalldawson @m-kuhn @Koyaani @lbartoletti @wonder-sk @alexbruy


@m-kuhn To avoid any doubt, please add a note to the QEP that indicates the deviations between the submitted proposal and the (potentially larger) full extent of the QEP. As in previous years, the voting members make their decisions based on the short summaries and the QEPs.


Just wanted to pop in here and see if my issue might be related. I've got an N64 with the Gamebox Systems 64HD. When I try to use my BlueRetro adapter (from Retrotime) in controller slot 1, I am getting graphical glitches only on my HDMI out (regular composite output is unaffected). Other controller slots do not have the issue. It's almost as if (and this is just a guess) the OSD menu is being interacted with even though I haven't brought it up. I haven't tried your firmware posted here yet though, I'll give it a try tomorrow.


From what I heard from other users (I don't have a 64HD) the Gamebox 64HD definitely has the same issue as N64Digital and other mods that tap into the controller lines. Unfortunately the known fix was not implemented from the get go on the N64HD.


Oh no, too bad, I forgot to deprecate PySys_ResetWarnOptions() in Python 3.11.


Rockylinux:8

gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-18)
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Will switch to devtooset8 on centos7 to match with rockylinux:8 which we will eventually switch to.


Using scl and devtoolset might be a problem because it requires running `source scl_source enable devtoolset8` either through rc or through profile.

With us locking docker images to non-interactive shell this is not the best option.
Exploring manually compile gcc 8 from source.


I updated my device with v1.8-push_pull_port1_hw1_n64.zip and it did not resolve the graphical glitches :(


To be clear, with the 64HD I am NOT getting issues with F-Zero or Tony Hawk as reported here for N64 Digital and Ultra HDMI mods.

I am just getting graphical glitches when my BlueRetro adapter is in controller port one. The glitches usually look like a bunch of random colors flash across the bottom half of the screen. The game I have found it most noticeable on is Snowboard Kids. Here is a video: URL


Falco's repo lifecycle doesn't mention forks and it seems it's more targeted for "big projects" something that we would be expecting to see for things like hubble, tetragon, cilium-cli. However, we might need to define a process for smaller projects similar to URL URL and URL for example.


Setting `wantAuthnResponseSigned` to false "solved" the issue so far. But I would really like to keep it active, to grant the highest security possible.


What did you get when testing over at URL If you got it to work, what options did you select on their web page?


Both Request and Response are valid. Do you have any other specific test in mind?


The error comes not from upgrading of a previous version.
Thank you for your hint about the behavior of Azure AD. I will take a deeper look at the configuration of Azure AD to enable response signing.
This indeed looks like it is not a bug in the first place but rather a configuration error now.
So we likely can close this issue, but please wait until I looked the config tomorrow.


@srd90 I've created a Wiki page that summarized this. Hopefully that will save you some time. Feel free to edit it, or let me know in an issue reply if you'd like some text added to it and I'll do it.

 URL


I've investigated and identified the cause and a potential fix for this issue, which I have captured in the new issue #7121.


Thank you very much with your help.
I've looked at the SAML configuration and found the option to enable the response and assertion signing option.
It can be found, when editing the SAML certificate.


Thank you so much, the issue is resolved. Turns out it was McAfee that was slowing the application.


we were using azure web apps
after some restart we need to execute above
in order make puppter working


Extra attachment fields are available without using extra metadata table (in Exhibition collection of the test database).
Deletion reason is missing, but maybe that information can be placed under the Details of exception.

proposed_attachment_form

The fields above are visible and searchable.
Changing some of them to drop-down lists (for instance Type of exception or Licence) is possible.

Using of metadata table needs one more step (if it's necessary) - waiting for an answer from Kansas.

image

Investigation of existing DarwinCore (DwC) extensions to publish the metadata (or at least part of it) as a DarwinCore Archive is still needed.


@ammen99 I found this thread URL and decided to include

[autostart]
01_xdp=/usr/libexec/xdg-desktop-portal
02_xdpg=/usr/libexec/xdg-desktop-portal-gtk
03_xdpw=/usr/libexec/xdg-desktop-portal-wlr

in my config file.

It seems that it works now! though I really don't know why. Does it change the way things are getting rendered on the screen in general?

(If there is a section in the documentation that talks about this, could you please redirect me?)

So far wayfire is really boosting my production and I can't be thankful enough for that, if there is anyway we can make donations, please let me know.


Glad to hear it works :)

For screen recording/sharing/etc. Wayfire and most wlroots-based compositors (Sway too) have a semi-private protocol, called wlr-screencopy. However, after we had this protocol, another way for this was standardized, which is also supported by GNOME and KDE (via xdg-desktop-portal). There is `xdg-desktop-portal-wlr` which basically translates from the wlroots' protocol to the xdp one, and OBS will not work unless this bridging component runs in the background (since OBS uses the standard xdp recording protocol).


I heard from people with a N64 HD that it has problems with signal integrity as it is, without using blueretro simultaneously. Reason is most likely the flex-pcb design thats not up to industry standards (ground return path). So likely when using blueretro this amplifies the issue.


Yea, I have noticed very infrequently some visual issues, but mostly it is fine. BlueRetro is increasing the frequency by like 100x or 1000x though.


@ammen99 Well... I think it is somehow related but do you happen to know why file picker doesn't show up? For instance when I click "upload a file" in browser, a window should open so I can choose a file on my local machine, but for some reason it doesn't show up.

I thought autorun the portals would fix this issue but it doesn't.


Do you run xdg-desktop-portal-gtk? It should be autostarted if you have the dbus/systemd env vars exported by autostart, the wiki has a section on that iirc.


@amartya3ac, the issue is assigned to you. Feel free to take issues to check the contributor guide as well:

 URL


@ammen99 yes here's the `[autostart]` section in my config file

[autostart]
autostart_wf_shell = true
00_dbus = dbus-launch
01_xdp=/usr/libexec/xdg-desktop-portal
02_xdpg=/usr/libexec/xdg-desktop-portal-gtk
03_xdpw=/usr/libexec/xdg-desktop-portal-wlr
portal=/usr/libexec/xdg-desktop-portal-gtk

Maybe I shouldn't use all the portals at once?

Also I have the problem in chrome right now, but file chooser seems to work in Firefox. Maybe I should open a new issue for that?


Here's my config (no need for a new issue, this isn't a Wayfire issue anyway, it is all about the dbus stuff):

[autostart]
0_0 = systemctl --user import-environment
portal = sleep 1 && (XDG_SESSION_TYPE=wayland XDG_CURRENT_DESKTOP=sway /usr/libexec/xdg-desktop-portal --replace & /usr/libexec/xdg-desktop-portal-wlr)

You can either set `XDG_*` before starting Wayfire, or replace the already-running portals like I do here.

You do need the systemctl command, or at least `dbus-update-activation-environment WAYLAND_DISPLAY DISPLAY XAUTHORITY` for all dbus-activated stuff to work, that includes file chooser dialogs.


And now 7.3.2 has started to gen seg faults ~5 1/2 months after installing 7.3.2. 🤷♂

I tried @daxian-dbw suggestion to remove the `StartupProfileData-NonInteractive` file and that fixes it. Not sure how long the fix will last but my CI/CD builds are running again on this M1 mini.


worked on this in 851e956 and a20ce5c

need to restore DefeatScoreTallyModal buttons


oops, actually, political capital is no longer mentioned on the scoretallymodal, but it's still in the save data.

i need to replace political capital with high scores


actually no i don't. all i still need to do for this ticket is search the codebase for mentions of political capital and gut what needs to be gutted.

a high score system is a separate feature which i have notated in #56 (though i dont think it will be prioritized)


Is the following code relevant? In URL

I was trying to skim through the code for jackett to figure out how btdig could be identifying requests coming from jackett. Maybe this will give some clues. I don't think the definitions will be helpful. The core code probably needs to be modified in order to avoid detection for this indexer. Perhaps btdig is able to identify the requests coming from jackett via referer or request type? Or maybe when emulateBrowser is null? Possibly a combination of things including the user-agent.

Hard to say, but the code is a bit steep for me since I am not proficient in CS. I'm curious how the requests coming from jackett look in cloudflare because that's probably where the redirect is coming from. Admins of btdig probably setup some redirect rules to match requests coming from jackett. Someone with more knowledge will have to investigate further.

cs
 protected virtual async Task RequestWithCookiesAsync(
 string url, string cookieOverride = null, RequestType method = RequestType.GET,
 string referer = null, IEnumerable > data = null,
 Dictionary headers = null, string rawbody = null, bool? emulateBrowser = null)
 {
 var request = new WebRequest
 {
 Url = url,
 Type = method,
 Cookies = cookieOverride ?? CookieHeader,
 PostData = data,
 Referer = referer,
 Headers = headers,
 RawBody = rawbody,
 Encoding = Encoding
 };

 if (emulateBrowser.HasValue)
 request.EmulateBrowser = emulateBrowser.Value;
 var result = await webclient.GetResultAsync(request);
 CheckSiteDown(result);
 UpdateCookieHeader(result.Cookies, cookieOverride);
 return result;
 }


I did try playing with UA and `EmulateBrowser` but didn't get anywhere. I assume that's where the issue lies, but 🤷


We should also add how handle experimental and unmaintained/archived repos.


@pwei1018 @PCC199 there are two active ops tickets related to this investigation, can we please reopen for grooming.

 URL
 URL


@rkeithhill-keysight The root cause is in .NET, see URL Please try collecting a dump when the crash happens, and share the dump in the .NET issue -- they need a dump to further investigate the issue (see URL


I read the .NET issue **after** I had fixed it. 🤦♂ Next time this happens, I'll collect a dump and post it there.


Is their any plans to allow users to change the stack limit using Postman settings?


I'm having a look into this issue now. Should hopefully have more details and potentially a PR up soon.


Added nanmin and nanmax function for PyTorch, Numpy, Jax, TensorFlow and Paddle backend. Additionally, implement api functions for ivy array and ivy container. #16328 #16327


Add `suntools` package as a dependency once it is published on CRAN


@tangierc - You'll find this interesting...

Apple has gotten back to us after reviewing this, and believe it or not, it's actually got nothing to do with BRAW Toolbox itself, it's because we're applying it to a static generator! If you add keyframes to the generator or if you replace the generator with something like "Clouds" it'll fix the issue!

We'll investigate a proper fix in BRAW Toolbox soon, and try and find a solution for fixing existing libraries - which should be easy, as we can just replace the static generator with Clouds, etc.


I've played around with this a bit and it isn't specific to moving lines with alt+up/alt+down, ordered lists item numbers don't update in general when altering them in some way (For example, if you have list 1 2 3 4 5 6, and you copy element 6 to clipboard then paste it above element 2, the list is now ordered 1 6 2 3 4 5) (The same behaviour as described above, but occurs in general when moving items around in existing lists).


I did a test installation with the classes for distributed installation and found several problems:

It was necessary to declare each of the nodes and they were fixed, so I opted to modify the code of the `indexer_dist.pp` class so that it does not configure any parameters of the `opensearch.yml` template except the default values and that they are assigned in the installation manifest

The config.yml file for the creation of the certificates has fixed values assigned and I am investigating how to be able to assign these values of each node by means of an array, which should have a pair of values for each item (node name, ip) So I continue with the investigation to review how to assign these values to the creation template of the `config.yml` file.

Modifying the `indexer_dist.yml` manifest allowed me to deploy an AIO environment, but it requires a different configuration of the install manifest than what we currently have:

$discovery_type = 'single'
stage { 'certificates': }
stage { 'repo': }
stage { 'indexerdeploy': }
stage { 'securityadmin': }
stage { 'dashboard': }
stage { 'manager': }
Stage[certificates] -> Stage[repo] -> Stage[indexerdeploy] -> Stage[securityadmin] -> Stage[manager] -> Stage[dashboard]
Exec {
 timeout => 0,
}
node "ip-172-31-35-35.us-east-2.compute.internal" {
 class { 'wazuh::certificates_dist':
 stage => certificates,
 }
 class { 'wazuh::repo_use':
 stage => repo,
 }
 class { 'wazuh::indexer_dist':
 stage => indexerdeploy,
 }
 class { 'wazuh::manager':
 manage_repos => false,
 stage => manager,
 }
 class { 'wazuh::filebeat_oss_dist':
 stage => manager,
 }
 class { 'wazuh::dashboard_dist':
 stage => dashboard,
 }
}


@bevans2000

How would you enable a player commander to adjust the weight of certain tasks to take place in a settlement ?


Two things. Firstly the demand calculation may be wrong and in your example above it should have a higher value.

I would look to define a "weights" ability to the Settlement class. Then when scoring Task in the TaskMeta classes a weight can be applied to the Task score. Weights greater than 1 obviously become a multiplier. But I would look to define the weights as a Map and not explicitly use any Task property. Then we could use the weights for many things but just have a single table, e.g. for Missions as well. We could potentially create a dedicated
WeightKey
 class containing a tuple of _key type_ & _key name_. where key type is Mission, Type, Trading etc etc. You get the idea.
Use the TaskMeta name as the key in this situation.
Then add a new Tab to the Settlement UI that maintains/displays the weight. When adding offer the user a list of OnShift Tasks. There is no point showing the OffShift Task since these are about Persons/Robots having "me" time.

Sounds a nice feature to influence how a Settlement behaves and is reusable elsewhere.

Potentially, could pre-fill the weights based on the Objectives of the Reporting Authority. Now that is cool.


I've plowed through the supply chain to find out why concrete is not being produced in the last couple commits.

It works reasonably well now in response to constructing foundation.

Still the concept of having commander's high priority tasks would be a great addition in near future.

For now, I use assignTask() in BuildingConstructionMission to add a task to a person. It's not a good way.

RoverMission is using assignTask() as well.

Can you show me how to implement your approach in RoverMission and/or BuildingConstructionMission ?


The RFC seems a bit unclear on if the filename must end with `.rs` or not?

If we (a) don't require `.rs`, and (b) don't require an explicit command line option, would that mean `cargo runc myprog` (misspelling `run` as `runc`) would be intepreted as "treat the runc executable as rust source and try and compile it, then run it"?


Yes, good idea. It is a Settlement based score so a good match. I'll do it under the control of #910


Assigning a Task directly to a Worker as part of the Mission is fine. THe Worker would not be calling the Mission methods if they have a Task already assigned.

Sure, why don't I try and put something together tonight/tomorrow. I can put #890 on hold; a change would be good as that is hard going.


We can combine the science and mission modifiers on the ReportingAuthority into this same single solution. This will have the advantage of all these being editable as well.
Secondly, the enabled Mission flags in Settlement can be handled by the logic, setting the weight to zero will disable the mission for that Settlement.
I've got a simple version working and need to add an editable UI screen


But say we define the base score as non-sero. Then when we modify this score by multiplication, it won't result in zero.

Say if the base score is 1, and your modifier is 0.5. Then 1 x 0.5 is 0.5


Can we add this to under one of 7 division tabs in Command Dashboard ?


According to the events record, the NR checked in right before refund. It is good:
image.png


We could but it is per Settlement and prefilled according to the objective of the Reporting Authority.


So, the problem come from checkin/checkout process. Should the name states back to previous, the same as request state, when checkin?


Thanks for using Corrfunc *and* for reporting the issue. I have been meaning to add the compilation-on-m1/m2 fix from the `arm64` branch into the `master` branch and this gives me the reminder to do so now.

Even after the compilation is fixed, you still will have another issue with the non-detection of python/numpy. Can you add a bit more detail about your python/numpy setup - are you using conda/macports/brew?


@quasars100 Will you please do the following to check if the new commits fix your compilation issue? The steps would be:

 1. git clone
 2. git checkout -b fix-compile-on-apple-soc
 3. make clean
 4. make

This should compile all of the command-line executables. If you encounter any warning/errors, please report back.


I've opened a pull request #4406 to fix this issue. However, for now, I have only addressed the case of moving lines with alt+up/alt+down. There is another pinned issue #937 open since 2020 which addresses the issue of fixing list numbers when deleting / copy-pasting items in an ordered list. As such, I'd suggest this issue could be safely closed if the above pull request is found to be sufficient.


@atul-devopswarriors
Could you please update the ticket with the below format and provide more information? Thank you.

## Describe the bug (🐛 if you encounter this issue)

A clear and concise description of what the bug is.

## To Reproduce

Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Perform '....'
4. See error

## Expected behavior

A clear and concise description of what you expected to happen.

## Log or Support bundle

If applicable, add the Longhorn managers' log or support bundle when the issue happens.
You can generate a Support Bundle using the link at the footer of the Longhorn UI.

## Environment

 - Longhorn version:
 - Installation method (e.g. Rancher Catalog App/Helm/Kubectl):
 - Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version:
 - Number of management node in the cluster:
 - Number of worker node in the cluster:
 - Node config
 - OS type and version:
 - CPU per node:
 - Memory per node:
 - Disk type(e.g. SSD/NVMe):
 - Network bandwidth between the nodes:
 - Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
 - Number of Longhorn volumes in the cluster:

## Additional context

Add any other context about the problem here.


Plus is emits the "make it readonly" for a property that **has a setter**. Making that one actually `readonly` surely makes IDE0251 go away, but gives "CS1604 cannot set write protected field" instead.

To me it looks pretty much as if the emitted IDE0251 is also incorrect in some cases ...


CRAN bioRad_0.6.2.tar.gz fails CMD check with `_R_CHECK_SUGGESTS_ONLY_=true` and forthcoming `sp` 2.0-0; adding `sf` to Suggests: remedies. I couldn't test properly with your Github HEAD which has `sf` because I don't have `vol2birdR`. `sp` 2.0-0 is coming during June.


Thank you so much for the quick reply. My python version is Python 3.10.12 (installed using brew) and NumPy version is 1.24.3 (installed using pip). Local environment (no virtualenv), terminal, packages installed using brew (no condo/macports).


I tried running the code block above and unfortunately got the following error:

In file included from ../../utils/cpu_features.c:13:
../../utils/cpu_features.h:41:10: error: couldn't allocate output register for constraint 'a'
 __asm("cpuid" : "=a"(a),"=b"(b),"=c"(c),"=d"(d) : "a"(functionnumber),"c"(0) );
 ^
../../utils/cpu_features.h:41:10: error: couldn't allocate output register for constraint 'a'
../../utils/cpu_features.h:69:10: error: couldn't allocate output register for constraint 'a'
 __asm("xgetbv" : "=a"(a),"=d"(d) : "c"(ctr) : );
 ^
../../utils/cpu_features.h:41:10: error: couldn't allocate output register for constraint 'a'
 __asm("cpuid" : "=a"(a),"=b"(b),"=c"(c),"=d"(d) : "a"(functionnumber),"c"(0) );
 ^
../../utils/cpu_features.h:41:10: error: couldn't allocate output register for constraint 'a'
5 errors generated.
make[2]: *** [../../utils/cpu_features.o] Error 1
make[1]: *** [DD] Error 2
make: *** [theory] Error 2


@tomekzaw
 Invalid `RNReanimated.podspec` file: [react-native-reanimated] Reanimated 3.2.0 supports the New Architecture only on the latest minor release of React Native. Please upgrade to React Native 0.72.0+ or downgrade to an older version of Reanimated v3.

I am getting this message . only thing i did was new react native init , and pod install with fabric, and then installed reanimated all . by default react native is coming with .71 version. and reanimated asks for .72, i think its not stable yet so is there any solution to this.


@Commaando Yeah, Reanimated 3.1.0 and 3.2.0 support Fabric only with React Native 0.72 which is not stable yet (currently latest pre-release is 0.72.0-rc.5). Sorry for this, we were just too fast. If you really need to use Reanimated with React Native 0.71, please use `react-native-reanimated@3.0.2`.


That is odd - those lines of code should never be seen by the compiler *if* the environment variable `__ARM_NEON` is defined - which is supposed to be the case. For reference, I just did a fresh repo clone and tried out my instructions and those worked. I also notice that there is line number mis-match between what I see and what you have reported in the error - is it possible that you accidentally skipped the checkout branch line? There was an error in what I quoted - you should do `git checkout fix-compile-on-apple-soc` (i.e., without the `-b` )

If you were indeed in the correct branch, will you please report back on the following steps:

- please copy-paste the output generated during the (unsuccessful) compilation process. Should look something like this:

clang -DOUTPUT_RPAVG -DENABLE_MIN_SEP_OPT -DCOPY_PARTICLES -DLINK_IN_DEC -DLINK_IN_RA -DDOUBLE_PREC -DUSE_OMP -DVERSION=\"2.5.0\" -DUSE_UNICODE -std=c99 -m64 -g -Wsign-compare -Wall -Wextra -Wshadow -Wunused -fPIC -D_POSIX_SOURCE=200809L -D_GNU_SOURCE -D_DARWIN_C_SOURCE -O3 -fopenmp=libomp -funroll-loops -fno-strict-aliasing -Wformat=2 -Wpacked -Wnested-externs -Wpointer-arith -Wredundant-decls -Wfloat-equal -Wcast-qual -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wstrict-prototypes -Wno-unused-local-typedefs -I../../io -I../../utils -I/opt/local/include -I../../mocks/DDrppi_mocks -I../../mocks/DDsmu_mocks -I../../mocks/DDtheta_mocks -I../../mocks/vpf_mocks -c run_correlations_mocks.c -o run_correlations_mocks.o

And then, can you please report back on these two things at the command-line:
- `which ` (where you replace the with whichever compiler that you are using).
- ` -mcpu=apple-m1 -dM -E - < /dev/null | grep -i ARM`


This has been happening to me consistently for over a year. The cause seems to be due to what I've described in URL

I used (a simplified version of) @ju1m's workaround, but using the workaround from URL seems to be even better. However, I don't know how to include that in my system configuration rather than running it manually when needed.


@bevans2000

This tab is awesome. I'm playing with the modifier score below for "Digging Local Ice" TASK :
image

@Urwumpe How do you like this new UI ?

I was gonna say one thing I'll like to see in future is to clearly disclose to players how each MISSION/TASK/SCIENCE score is computed.

And we know this sort of transparency is needed and highly desired in strategy games out there.

For instance, say the birth rate of a city is -0.7. Why would it be negative ? That means people in this city won't give birth to babies and it would be disaster for growth. So the player would like to know how this composite penalty score of -0.7 is computed.

It turns out
1. the city only allocates 80% of funding (thus -0.2; say, each 1% is -0.01 penalty) for the medical category needs of this city.
2. the road to medical clinic is broken (thus -0.1) in this city.
3. the city only has one clinic while there are 10,000 population. Say each 2,000 pop needs one clinic. So it's missing 4 clinics and thus the penalty of -0.4 (=4 * -0.1)

Similarly, we could show in the detail breakdown of each row of score with a short individual reason with a sub-score in the form of tooltip or other UI elements.

Can we do that ?


I first want to say "Hell, no!". Sorry.

Especially since attribution science is one of the hardest and interpretation rich sciences in the world.

Thinking a bit further, maybe we can simplify things in our simulated world enough to "gamify" it. I have no good answer there yet, but for now, maybe the following idea is not as crazy as it sounds.

1. There are multiple different approaches to write a study, which are limited by the field of science. Social sciences vs natural sciences vs engineering...
2. The scientist picks one approach for a new study.
3. Depending on approach, there can be one or more data sources.
4. Also there are one or more methods to interact with the data sources
5. There are also methods that turn objects (e.g. soil samples, interviews with settlers) into data sources, which might be the usage of certain tools
6. The data sources have an interface that fits to the method
7. Methods can create new derived data sources
8. Data sources can be interpreted according to models/theories/collaries/etc.
9. Interpretations on input data and derived data can classify these and with a interpretations of the results turned into a new theory/model.
10. Models can be tested by other science projects, especially if there might be different methods/tools available to produce the same kind of data source used.
11. Still a lot of magic happening there, this is no good algorithm.


You are one step ahead of me.

Actually I mean: Telling that a certain change has a clear root cause. Like creating a fishbone diagram and interpreting it.


Glad you like it. I feel it consolidates and cleans up a few different areas into a single approach. And it uses the the ReportingAuthority to load it to start with which I like.
Plus I've done it so we could add other types later.


This is quite important.

Single stream HTTP/1.1 with TLS 1.2/1.3 (AESGCM128 afaik), can do about 360MB/s (3600Mbps) on a single core (no ktls). C (openssl, wget, curl), Go (`net/http`), Python (`requests`) all show me about 350MB/s one way over single stream (Python about 220MB/s). I was not able to reach 25Gbps, not even close.

In theory QUIC maybe could do even better by exploiting more CPU parallelism. But very fat streams are a bit niche. Still, QUIC should not regress compared to HTTP/1.1 with TLS 1.3.

AMD Threadripper 2950X, Zen+, 3.2GHz. So a bit dated.


Can someone who could reproduce this bug before try again with latest master which includes #50135? Although I'm not sure it's the same as #48187 because as far as I understand the error message is different, although the timeline looks similar.


I'll fix this, it's the same issue with accessing FFTW internals. This should be the last occurrence


Ah gotcha, good catch. Guessing this requires someone else's weigh in -- I don't object to what you're describing.


i should do #57 first so i dont brick my ability to test on ios (ios doesnt give me a way to clear an app's save data, tho i could just uninstall the whole thing)


I think this is fixed now, tests seem to pass using the latest julia nightly on Windows in the PR URL

Thanks a lot!


Hey @roblourens, this issue might need further attention.

@brianjmurrell, you can help us out by closing this issue if the problem no longer exists, or adding more information.


@vtjnash long shot, but since this involves threading can this possibly be fixed by #50135? Also #48907 reported an `EXCEPTION_ACCESS_VIOLATION` error, but I don't know if this test would involve `libgomp` at any point.


Hi @YasCoMa, the two functions you are referencing seem to have been reserved already. Please make sure you follow our ToDo issues policy explained here every time you intend to start working on a function.


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


@l3r8yJ this is your task now, please go ahead. Deadline (when this ticket should be closed) is ``2023-06-22T16:19:05.771309``.

Estimation here is ``60 minutes``, that's how much you will be paid.

Remember, you don't have to solve everything in this ticket - you can solve it partially and leave ``todo`` markers in the code, which will become future tasks.

If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.

If you don't have time or simply don't want to work on this, you can always resign.


Hello I'm facing the same issue of extremely high loading time. I don't use McAfee. Does this issue also reproduce for Windows Defender.


@h1alexbel ok, I've removed this task from scope. I'm not managing it anymore.


@h1alexbel I've just registered this ticket as a task and will assign it to someone soon. Thanks!


@h1alexbel this is your task now, please go ahead. Deadline (when this ticket should be closed) is ``2023-06-22T20:09:04.176448``.

Estimation here is ``60 minutes``, that's how much you will be paid.

Remember, you don't have to solve everything in this ticket - you can solve it partially and leave ``todo`` markers in the code, which will become future tasks.

If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.

If you don't have time or simply don't want to work on this, you can always resign.


Here is what the output is after the following steps.
In terminal, in the ~/Corrfunc directory:

 _(1. git clone ) --> already cloned and in the Corrfunc directory_
 2. git checkout fix-compile-on-apple-soc
 3. make clean
 4. make

Output (in terminal):

In file included from ../../utils/cpu_features.c:13:
../../utils/cpu_features.h:41:10: error: couldn't allocate output register for constraint 'a'
 __asm("cpuid" : "=a"(a),"=b"(b),"=c"(c),"=d"(d) : "a"(functionnumber),"c"(0) );
 ^
../../utils/cpu_features.h:41:10: error: couldn't allocate output register for constraint 'a'
../../utils/cpu_features.h:69:10: error: couldn't allocate output register for constraint 'a'
 __asm("xgetbv" : "=a"(a),"=d"(d) : "c"(ctr) : );
 ^
../../utils/cpu_features.h:41:10: error: couldn't allocate output register for constraint 'a'
 __asm("cpuid" : "=a"(a),"=b"(b),"=c"(c),"=d"(d) : "a"(functionnumber),"c"(0) );
 ^
../../utils/cpu_features.h:41:10: error: couldn't allocate output register for constraint 'a'
5 errors generated.
make[2]: *** [../../utils/cpu_features.o] Error 1
make[1]: *** [DD] Error 2
make: *** [theory] Error 2
achen@MAC0008879 Corrfunc %


Just to confirm: there are *no* matches to the ARM grep command for either of the compilers?


Hi All,

We are going to stay with node16 for 2.9, and plan to move to node18 for 2.10.
This would ensure us to have enough time for the upgrade.
As well as compensate the changes for multiple teams.

We can also start the Python3.9 upgrade process as Python3.7 is about to be eol by 2023/06/23.

Once we go to node18 in 2.10, the support matrix of our product will need to remove these OSes:

* RHEL7&CentOS7 / AmazonLinux2 (glibc2.17 / glibc2.26)
* Ubuntu 16.04 / Ubuntu 18.04 (glibc2.23 / glibc2.27)
(Note: we still bundle node14 as fallback so technically above can still run, but 14 is eol and we do not officially support them anymore)

This also requires that the 2.x branch stays on 16.20.0 in .nvmrc, and have no node18 specific code committed until 2.9.0 is released to the public.

Infra will take care of the node18 upgrade once after 2.9.0.

Thanks.

cc: @CEHENKLE @dblock @seanneumann @AMoo-Miki @ananzh @seraphjiang @vamshin @jmazanec15 @bbarani @hdhalter


Also, what happens if you do make CC=gcc (after a make clean)

What’s happening is that the compiler is not supposed to see that chunk of code on ARM, based on a variable usually defined by the compiler. That assumption of defined variable seems to break down on your setup. Since I don’t use brew (macports person) here, I hadn’t encountered this issue before


Since @quasars100 probably ran the original instructions with `git checkout -b fix-compile-on-apple-soc`, they probably have a local branch that's not tracking the remote. I think the steps to fix this are:

$ git checkout master
$ git branch -d fix-compile-on-apple-soc
$ git checkout fix-compile-on-apple-soc

I think at that point, you'll have a local branch that's tracking the remote, which you can confirm with `git branch -vv` or `git status`. Then hopefully the code will compile.


Do you have the logs from other pods (longhorn-manager, longhorn-driver-deployer, longhorn-ui). Do they share the same crashing error message above?


@khushi-411 Hey, Kushi . I have an idea in mind about implementing `erfc` for `ivy` function API but you're tagged in-that hence, pining you in-here .

Also, I see that you've already made a **PR** URL but it is showing as closed!

In case you're allowed to work with other people or just want to discuss it ; feel free to ping me !
Writing it in here as I can't find you on discord!


Hey, @akshatvishu! My PR is still open, just that I was on leave for a couple of days, so I kept it draft (i.e., work in progress). I'll make sure to finish that soon. Thanks for your kind interest!

If interested, please feel free to pick any other exciting open issues at Ivy! Thanks.


Hi! Looks similar to URL
Currently, there are two solutions: either enable aarch64 cross-compilation on a machine you're deploying from (by setting `boot.binfmt.emulatedSystems = [ "aarch64-linux" ]`), or using `remoteBuild = true;` in case your target machine is powerful enough


@0pdd 2 puzzles #292, #293 are still not solved; solved: #364.


However, when I check my python version, it was 3.10, which is > python2.7

achen@MAC0008879 Corrfunc % which python
python: aliased to /opt/homebrew/bin/python3.10

And numpy:

Python 3.10.12 (main, Jun 7 2023, 00:37:42) [Clang 14.0.0 (clang-1400.0.29.202)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

'1.24.3'

which is >numpy 1.7.

Sorry for how long this issue seems to be, and thank you all again for all your help.


Thank you, and after running these steps, the code did seem to compile, however, this was the end output:

Makefile:7: Not compiling C extensions for mocks. Either python or numpy not available
/Library/Developer/CommandLineTools/usr/bin/make -C DDrppi_mocks
make[2]: Nothing to be done for `all'.
/Library/Developer/CommandLineTools/usr/bin/make -C DDtheta_mocks
make[2]: Nothing to be done for `all'.
/Library/Developer/CommandLineTools/usr/bin/make -C DDsmu_mocks
make[2]: Nothing to be done for `all'.
/Library/Developer/CommandLineTools/usr/bin/make -C vpf_mocks
make[2]: Nothing to be done for `all'.
for dir in DDrppi_mocks DDtheta_mocks DDsmu_mocks vpf_mocks examples; do \
 /Library/Developer/CommandLineTools/usr/bin/make -C $dir lib; \
 done
make[2]: Nothing to be done for `lib'.
make[2]: Nothing to be done for `lib'.
make[2]: Nothing to be done for `lib'.
make[2]: Nothing to be done for `lib'.
make[2]: Nothing to be done for `lib'.
/Library/Developer/CommandLineTools/usr/bin/make -C examples
make[2]: Nothing to be done for `all'.
achen@MAC0008879 Corrfunc %

Also, when I try calling "Corrfunc" in python and using its commands, I get the following error:

Traceback (most recent call last):
 File "/Users/achen/Corrfunc/Corrfunc/theory/xi.py", line 187, in xi
 from Corrfunc._countpairs import countpairs_xi as xi_extn
ModuleNotFoundError: No module named 'Corrfunc._countpairs'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
 File " ", line 1, in
 File "/Users/achen/Corrfunc/Corrfunc/theory/xi.py", line 191, in xi
 raise ImportError(msg)
ImportError: Could not import the C extension for the correlation function.

The package does import in python without issue, it's just when I try running the commands they don't work.
Thanks again, and sorry for the myriad of issues this seems to have on brew.


Bonjour @baby-scarf ,

Regardons cela ensemble.

**1ère erreur**
La première erreur tout d'abord, en soit elle n'a rien d'inquiétant. Chaque ligne sur la connexion série possède à la fin un checksum pour valider l'intégrité de la ligne (et permettre de détecter une ligne invalide et éviter la remontée d'une mauvaise information). Cela peut arriver de temps en temps d'avoir une ligne invalide pour diverses raisons (mauvaise qualité du lien série, perturbation électromagnétique changeant la valeur d'un bit, etc...). L'important est simplement de ne pas en avoir trop souvent (sinon le câble ou le module série devrait être examinés voir remplacés).

En y regardant de plus près, le checksum remonté par l'erreur semble être `0x7f` ce qui est normalement (c'est à dire d'après le standard Enedis)... impossible : celui-ci de devrait se trouver qu'entre `0x20` et `0x5f`. Il semble donc que la perturbation ait impacté les bits composant le checksum (le nom du tag `ISOUSC` et sa valeure `45` semblent elles être normales) et l'intégration a donc décidé de ne pas prendre en compte cette dernière ne pouvant la vérifier. Comportement normal donc.

**2eme erreur**
Concernant la seconde erreur, c'est elle qui vous cause problème dans le sens où elle arrête le thread de série car l'erreur n'est pas prévue. Cette dernière prend racine lors de la formation d'une erreur de lecture série (comme la première) mais n'arrive pas à finaliser la remontée de cette erreur (où vous auriez eu une erreur du même format que la première).

Le détails de la seconde erreur semble indiquer que cette fois ci le tag comporte des bits invalides, amenant la définition d'un seul caractère (`in position 2`) hors des valeurs possibles de l'encoding ASCII utilisé par ENEDIS sur le lien TIC.

**Donc ?**
Je vais regarder pour publier rapidement une nouvelle version gérant correctement la seconde erreur pour éviter le crash du thread de gestion de la connexion série (je n'avais encore jamais eu de problèmes à ce niveau là) : cela ne corrigera pas l'erreur en elle même mais, comme pour la première, cela permettra de mettre la ligne de côté et de continuer à traiter les suivantes : l'intégration continuera de fonctionner malgré ces erreurs.

Par contre... Je ne vous cache qu'il est hautement inhabituel d'avoir autant d'erreurs sur un lien série et en aussi peu de temps. Quel module TIC/série utilisez vous ? La connexion série entre le TIC du Linky et le module est-elle bien en place ? Le câble n'est-il pas abimé ? Y a-t-il une source de pollution électromagnétique proche ? (des câbles trop fins pourraient être simplement trop sensibles par rapport a des câbles gainés).


Pouvez-vous essayer la version 2.0.5 ? Elle devrait éviter l'arrêt de fonctionnement de l'intégration pour les cas comme votre seconde erreur.

Je vous encourage tout de même à surveiller les logs de l'intégration et les erreurs de validation de lignes (comme votre première erreur) : il peut arriver d'en avoir mais cela est sensé être des cas rares et isolés et non fréquents (cf mon dernier message).


Hoorrray - that's definitely progress! At least the code seems to be compiling (which I am surprised by, given the lack of the (usually) defined `ARM` variables but I will put that down to a bad `grep` implementation).
@quasars100 Please don't apologize - you are helping us improve Corrfunc, and that, in turn, helps everyone - so thank you!

@lgarrison Not really sure why `python` is not being detected - the detection is simply a shell calling `python`! I see that the output says ` /bin/sh: python: command not found`. My guess is that `python` is defined as an **alias** and, therefore, only available on the interactive terminal (i.e., where @quasars100 is working but not through the non-interactive terminal invoked by `make`).
@quasars100 What do you get if you try `alias python`? And regardless of the alias status, using `python -m pip install -e . --verbose` should work. Even if `python` is aliased, that specific command should use the correct python.

Related, I see that OpenMP is not enabled; ideally, that also needs to be fixed. @quasars100 Will you please run `brew install llvm` to install the OpenMP-enabled version of `clang` and then recompile (after `make clean`) by invoking `make` (or equivalently, `make CC=clang`)


@quasars100 To explicitly clarify, as long as `python` and `numpy` is not detected at compile time, the Corrfunc C extensions will **not** be compiled, and therefore, you will not be able to use Corrfunc from python


I am thinking if this error is related to Longhorn PSP not being enabled causing the problem in your cluster.
By default, in Longhorn v1.3.2 we don't ship Longhorn PSP. If your cluster requires this to work, you will need to deploy it.

Could you provide the output of `kubectl get psp` ?


Could also provide some audit logs to see if there is any issue with SELinux?

ausearch -m AVC -ts recent


Is there a reason `remoteBuild = true` doesn't solve this issue? I understand in some cases you want to build on the deploying machine with qemu, but as @tennox suggests, using remote build still throws an error complaining about the capabilities of the deploying machine.


Bonjour,

merci pour votre efficacité et rapidité, je vais essayé de répondre à vos questions.
J’utilise un module fabriqué par moi à base optocoupleur 814 et quelques résistances relié au linky avec du câble fin téléphone, pourtant ce module même fonctionné très bien avec domoticz.
si c’est vraiment mon module après plusieurs essais je le remplacerai par la suite.
Tous mon matériel est branché au niveau de tableau général proche de la freebox, un Rflink.
J’ai mis en place votre correction ce matin je vous tiens informer de la suite .

une question : est il possible de branché mon module directement sur le port GPIO du raspberry comme je fesais avant pour domoticz ?


Un log après 1 heure de fonctionnement :

Logger: custom_components.linkytic.serial_reader
Source: custom_components/linkytic/serial_reader.py:112
Integration: Linky TIC (documentation, issues)
First occurred: 06:44:57 (66 occurrences)
Last logged: 07:51:54

Failed to validate the checksum of line 'b'ISOUSC 45 \x7f'': ISOUSC -> 45 (None) | s1 607 0b1001011111 | truncated 31 0b11111  | computed 63 0b111111 ? | expected 127 0b1111111
Failed to validate the checksum of line 'b'\xbfPTARIF HC.. -> HC.. (None) | s1 908 0b1110001100 | truncated 12 0b1100  | computed 44 0b101100 , | expected 60 0b111100 HC.. (None) | s1 740 0b1011100100 | truncated 36 0b100100 $ | computed 68 0b1000100 D | expected 60 0b111100 HC.. (None) | s1 780 0b1100001100 | truncated 12 0b1100  | computed 44 0b101100 , | expected 60 0b111100 -> 000000 (None) | s1 1000 0b1111101000 | truncated 40 0b101000 ( | computed 72 0b1001000 H | expected 66 0b1000010 B


The activation script still needs to be built on the deploying machine, as far as I understand.


Il est possible que domoticz mettait simplement de côté les lignes invalides silencieusement quand j'ai décidé de les faire remonter (justement pour aider l'utilisateur a détecter un mauvais module ou lien). Mais je ne peux le dire avec certitude, je n'ai pas regardé le code de domoticz.

Je ne saurais dire, malheureusement mon domaine (software) commence là où le hardware fini :)

~1 erreur/minute sur le lien série c'est clairement beaucoup

tag ok, valeur ok, checksum ko

Failed to validate the checksum of line 'b'?PTARIF HC.. HC.. (None) | s1 780 0b1100001100 | truncated 12 0b1100  | computed 44 0b101100 , | expected 60 0b111100 <

tag ko, valeur ok, checksum inconnu

Cela confirme ma conclusion précédente, vous avez beaucoup de lignes incorrectes en provenance du lien série. Mon intégration doit pouvoir les gérer tout en continuant de fonctionner, c'était le but de la mise à jour et si vous avez de nouveau une erreur de type `Uncaught thread exception` (celle-ci stoppant l'execution de l'intégration) prévenez moi que je rajoute un correctif.

Maintenant concernant vos erreurs/trames incorrectes en provenance du lien série, je ne saurais dire... Est-ce votre Linky qui est défectueux ? Votre connexion TIC ? Votre module série ? Le cablage ? J'ai bien peur que le seul moyen de le savoir serait de changer un élément après l'autre jusqu'à identifier le coupable. Ou alors simplement conserver l'ensemble tel quel et laisser l'intégration mettre de côté les lignes problématiques :)


Oh, AFAICS, build failure happens during checks build, which indeed needs target system capability for building the profile locally as a part of the check. A solution to this is to provide `--skip-checks` option


I am not able to fetch the long of any longhorn pod because non of pods are active or running state, However i can share describe logs.


Please check the below output from above command

` ausearch -m AVC -ts recent

`


If this can be any help, I have the exact same error from Prowlarr.
So it seems this comes from BTDigg, rather than Jackett itself.
As someone suggested, it may be on purpose.


@0pdd the puzzle #373 is still not solved; solved: #292, #293, #364.


Here is what I get when running "alias python" in terminal:

alias python
python=/opt/homebrew/bin/python3.10

(which python
python: aliased to /opt/homebrew/bin/python3.10 )

So prior to opening this issue, I actually ran "brew install llvm", and that is the version of clang my current clang compiler is aliased to, which is why the warning of "OpenMP is not available with apple clang" was confusing, since clang should be aliased away from Apple clang now.

After running "make CC=clang", OpenMP is enabled, but I still get this error:

/bin/sh: python: command not found
/bin/sh: python: command not found
/bin/sh: line 0: [: too many arguments
/bin/sh: line 0: [: too many arguments
../common.mk:497: Found python version .. but minimum required python is 2.7
../common.mk:502: Found NUMPY version .. but minimum required numpy is 1.7

However when I check the python version:

which python
python: aliased to /opt/homebrew/bin/python3.10
achen@MAC0008879 Corrfunc % python
Python 3.10.12 (main, Jun 7 2023, 00:37:42) [Clang 14.0.0 (clang-1400.0.29.202)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

'1.24.3'

Python > 2.7 and numpy > 1.7. Do you know if this is something to be changed in "common.mk" or my local environment?

Thank you again so much for all your help!


$ kubectl get psp
Warning: policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
NAME PRIV CAPS SELINUX RUNASUSER FSGROUP SUPGROUP READONLYROOTFS VOLUMES
longhorn-psp true SYS_ADMIN RunAsAny RunAsAny RunAsAny RunAsAny false configMap,downwardAPI,emptyDir,secret,projected,hostPath


Ohh good - so python *is* defined as an alias. No wonder `make` can't find python.

Try and run `export CC=clang && python -m pip install -e .` - that should do the trick


Yes, that worked! (Has to be in the Corrfunc cloned directory though).
Thank you so much!


implemented in:
- eccf122960cbb15ef3c68fbe0670b261a5d8ba61
- 09e5f28222c91772c1776f6c45b4d1faabf2a5bb
- b3b5fa039f57194bb1d550fa1844a28242ab668c
- other surrounding commits


Thanks @atul-devopswarriors !

The PSP looks good.

For audit logs, did you run `ausearch -m AVC -ts recent` on the node `t1-prm-wrk1` yet?


Great - glad this all worked :)! Can you confirm that you have OpenMP support, i.e., that you can use multiple threads now?

Sidenote: The reason why you were facing the compilation and non-detection of `llvm-clang/python/numpy` is all because you (or `homebrew`) have the relevant aliases set. The aliases work fine for you since you are always accessing from an interactive terminal - i.e., a terminal where you can send keyboard input to. The shell sessions spawned by `common.mk` are non-interactive and, therefore, **do not** know about the aliases.

I also suspect your `PATH` variable does not contain `/opt/homebrew/bin` (for `llvm-clang`) ahead of `/usr/bin` (for `apple-clang`), and thus, when the non-interactive shell resolves `clang` as `/usr/bin/clang`. Since I don't use `homebrew`, I am unsure if it is an intentional design that `/opt/homebrew/bin` is not added to your `PATH` environment variable. If you ever run into such odd issues of not-detecting-the-correct-tool, then it might be worthwhile adding the full path to whichever tool that you are wanting to detect (or equivalently, add `/opt/homebrew/bin` to `PATH` either in the terminal you are working in, or in the startup shell file - `.bashrc/.zshrc` etc)


@0pdd all 4 puzzles are solved here: #292, #293, #364, #373.


Ran into this issue extending EditorNode3DGizmoPlugin so can confirm it works with that too.


From ticket #221:

Additional work required:
* Add extra attachment fields to data entry form in Specify (done)
* Potentially script an import of attachment metadata into Specify BUT not until we have a concrete example and use case


@Sosannah and I agreed that this issue is covered and therefore subsumed by #222 and will therefore be closed.


There are available Darwin Core fields for publishing metadata of our assets, see in the attached sheet:
attachment_metadata_fields.xlsx


@johanjino

I created an issue on GitHub for the NCE loss function implementation. Could you link the NCE issue with the latest comment on this page?

Here is the link for that issue page


Just discovered that this is missing! I thought it was working until I renamed the file that was referenced by relative-to-repo-root syntax. Looking forward to a fix.


Here you can find instructions on how to link your issues to our ToDos URL


In the current implementation, it looks like adding/renaming a function will trigger a whole re-compliation including all dependencies. Changing/Adding function signature is not rare in scripting. I wonder if this is expected and if this could be resolved.


In #12268, the whole scheme is being removed. In future PRs, we'll being some of it back but yes, one of the thing I'll be changing is that the target dir should have a hash of the path, not the content. People change the content more than they change the location.


Wasabi Wallet heavily relies on rapid blame rounds happening one after another. The current speed is already much worse than it should be.

Clients behave properly. Excuse me for not digging into the code, but when we worked it out, the only issue remaining was the UI feedback, the clients do not mess up their registrations, because the request randomization does not fill out the entire phase time, but only the beginning of it.

There are some, sometimes. Which is not a bug, but a feature, because clients those have unreliable connections (be it Tor or local) are more likely to disrupt rounds later on, so penalization is in order.

If you get the exact numbers, then we can potentially increase this with that number. It would probably not slow things down much.


*sigh* I forget what all keywords github looks for that I have to avoid


My instance of this issue is indeed caused by a wireguard interface, but adding the interface to `networking.networkmanager.unmanaged` (via name or `type:wireguard`) did not change a thing. Having done some more digging online, I believe I know why: prior to udev initialization completing for a link, NM cannot be sure what the name or type of the link will be (as udev may make changes), and so it is *not possible* to filter a device prior to udev marking it as configured.

I'm still looking for a workaround.


As I've also written in the PR: There is this function that can automatically correct list markers for those lists that are touched by any of the selections within the editor.

Under the assumption that this function works as expected (which I'd love to have another person double check), then we could simply write a `transactionExtender` that *always* triggers if the document contents have been changed. This includes, but is not limited to, exchanging lines, adding new ones, deleting items, pasting content, and so on. This would also eliminate the current "sonderweg" we have to do with the tab character (list item indentation).


according to CoinjoinClient.cs randomization takes 80% of the time:

var remainingTime = roundParameters.OutputRegistrationTimeout - RoundStatusUpdater.Period;
var outputRegistrationEndTime = now + (remainingTime * 0.8); // 80% of the time.
var outputRegistrationScheduledDates = GetScheduledDates(outputTxOuts.Length, outputRegistrationEndTime, MaximumRequestDelay);

which in case of 6 minutes of OutputRegistrationTimeout is 4:48 min.
and this value exceeds shortened timeout by 1:48 min (more than 50% of FailFastOutputRegistrationTimeout)

We were debugging specific round (`eebc32ea...` see integrations chat) and noticed that almost 10% of the amount from the sum of all registered inputs didn't managed to register their outputs leading to 23 banned inputs at the end of that round.
I'm not sure if they might be considered as some and sometimes.
We could assume that all of them are trezor/suite users which didnt deliver final signatures because of missing affiliate data at the end, but are they really? 🤷

Round (eebc32ea8208ba6ca1389a75f395e76ed403e6d322ba0e64b56bb8949d701c15): Removed 23 alices, because they didn't sign. Remaining: 169

Maybe coordinator should end this round and immediately create a blame round instead of using "FailFast timeouts" and forcing clients to sign "reasonable transactions" which most likely will not be broadcasted anyway?


Same issue here. It was really painful to start vs code. And I'm working on a Next.js project, and it was taking ages to refresh it on the page after saving a file. I tried different things to solve this problem here, but nothing worked (I have McAfee installed on my machine, but didn't realize this could be the problem) ... but then, two or three days ago, after an vs code update was launched (not sure) the problem was gone. It's staring real fast and everything works fine now! Thanks a lot! 😁👍


As already expressed in the pre-RFC, I think that wrapping the manifest into
cargo shouldn't be needed. Would a PR be accepted that implements "option 5: comments" (without a HEREDOC)? Ideally, this should become possible:

Rust
#!/usr/bin/env cargo
/*
[package]
edition = "2018"
*/

fn main() {}

The rules would be:

* any `/*` comment directly at the top gets interpreted as a toml snippet
* adding any blank lines, or lines with content (including `//` comments) between the shebang and the comment disqualifies that comment from being the toml snippet.

Comments would still be supported in toml fashion via a `#`.

Personally I think as we are treading new ground here, one should reduce the overhead that the eval system adds, and
cargo adds such overhead. Once we stabilize cargo-script support, the option to add treatment of comments in such a fashion is gone.

Regarding the implementation, correct me if I'm wrong, syn seems to not parse comments. Maybe one could switch to using `rustc-lexer`? It should reduce the overhead a bit I think.


TREND security agent also has this problem

Disable TREND security agent can solve


Check out how those things are used. Every random scheduling is corrected to maximum 10 seconds:

cs
private static readonly TimeSpan MaximumRequestDelay = TimeSpan.FromSeconds(10);
var outputRegistrationScheduledDates = GetScheduledDates(outputTxOuts.Length, outputRegistrationEndTime, MaximumRequestDelay);

With this information in mind. I assume you're not doing this? If so, then your "banned issue" can be easily solved by starting to do this as well?


well, to be honest trezor suite currently has (intentionally) disabled output-registration delays (with a todo to enable them)
but i wasn't aware that the delay is limited to 10 sec. only, thanks for explanation, we will implement the same mechanism :+1:

in mentioned round suite instance which provided the logs was able to successfully finish the whole process in ~17 seconds (5x credential-issuance, 5x output-registration, 3 ready-to-sign) and at the end it was banned only because of missing affiliate data issue

it was someone else who didn't managed to register mentioned outputs (either other suite or wasabiwallet) and this is why we focused on your code


one alternative option is to do something like Java's jar files...scripts would be a zip file with a different file extension and a unix `#!` line prefixed


Thank you, this is what we were doing wrong.

Closing this issue in favour of URL and URL


@pmrussell892 We're looking more into this. Meanwhile, you can make use of our open-source collection generator from OpenAPI definition.

Here is more on how this tool can be installed and used. This conversion will take place on your machine so it'll be private. Do provide your feedback if increasing this limit is generating collection as expected or not.


Hi...happy to help 😁.

Regarding the flags, I added code.exe back to Mcafee scanning and ran the above command. The launch was still laggy and made no difference.


Thanks for confirming, in your traces the processes were all sandboxed. The flags were to confirm if disabling the sandbox made any difference, but seems like it doesn't which is good to know. Apart from the launch delay, do you see any `The window is not responding` messages and is the application responsive as when excluding the binary from Mcafee ?


Made all documentation changes in the URL branch and created the PR URL pull/6186 for approval.


+1 to this issue as well, I'm trying to POC out bazel as a new build system on my team, and setting up a cache server for a prototype seems overkill


Hey, @hirwa-nshuti I don't see the API specification of modf in docstring, is there any other doc that can help me write the Extended Ivy Functional API of modf.


@tjgq and I had several brainstorm sessions about garbage collection for disk cache in the past days and we now have a solid design for that! We don't have a timeline to work on the implementation yet, but Q3 looks like a reasonable slot.


Investigation of existing DarwinCore (DwC) extensions to publish the metadata as a DarwinCore Archive is accomplished:
attachment_metadata_fields.xlsx


There were two important questions for our design of the garbage collector:

1. How to decided which blob in the disk cache should be removed?
2. How/when to run the garbage collection for a shared disk cache?

The answer to the first question is similar to the workaround you have posted here: use `mtime`. However, since we now have the lease service which will extend the leases of blobs required by Bazel during the invocation, we can let disk cache update the `mtime` of referenced blobs during lease extension. This allows us to do the garbage collection based on the real access pattern. And combining with `--experimental_remote_cache_ttl`, we won't delete blobs that are still needed by Bazel. On that other hand, even if the blobs were accidentally deleted causing remote cache eviction error, lease server can help Bazel recover from it.

We don't want the garbage collection have impact on the build performance, nor users should be aware of it. So it happens in the background between invocations. The garbage collection should be interruptible and resumable, so that upon a new invocation, we can cancel it immediately without blocking the invocation and continue it afterwards. Since the CAS is sharded by the first byte of the blobs' digest, we define the unit of work for the garbage collection as shard, i.e. we can resume the garbage collection on the shard basis.

We don't want to run garbage collection after every invocation. We store the global state (e.g. when did last garbage collection finish) in the disk cache and schedule the garbage collection based on that (e.g. once per day).

We want to continue supporting the use case that multiple Bazel instances share the same disk cache. To prevent from having concurrent garbage collections, we use a lockfile created inside the disk cache by `open(O_CREAT | O_EXCL)` (and equivalent one on Windows. However, it might not work on some `NFS`s. We do have a plan B for that but we don't want to make it complicate now. Consider using a real remote cache server if you want to share cache across machines). The `mtime` of the lockfile is updated continuously during the garbage collection to indicate it is still in progress in case of Bazel server crashed (or `Ctrl-C`ed).

cc @tjgq in case I missed something.


It's really awesome to see progress on this issue :)

Would that work in the context of continuous integration / Github Actions? In that context, there isn't really any or much time "between invocations": a VM comes up, downloads the cache, builds a bunch of stuff, and uploads the updated cache. Example workflow.

This seems to be a common use case cited in this thread, e.g. see @chandlerc's commented I linked.