Checksum Algorithm mismatch

Checksum Algorithm
Although, the checksum algorithm is discovered and decompiled here, the implemented method in python always returns a wrong result.
Description of  the algorithm
The call which is done in BuildSADPPacket() is the following:
 uVar7 = Checksum(
    *(ushort **)(buffer + 0x14),
    (uint)*(byte *)((int)*(ushort **)(buffer + 0x14) + 3)
 );

Note, that the conversion to unsigned short * will produce a pointer that combine
two bytes each position. Therefore, +3 at the end has the following effect:
  ubyte *buf = [0x10, 0x20, 0x30, 0x40];
  ushort *dest = (ushort *)buf;
  //           = [0x1020, 0x3040]

The next step is to convert the returned unsigned short value into a single byte value:
  ushort *buf = [0x1020, 0x3040]
  byte dest = *((byte *)buf)
  //        = 0x10

The input buffer is the following:
  ┌───────────────────────────────────────────────┐
  │Buffer Structure                               │
  ├─────────┬─────────┬─────┬─────┬─────────┬─────┤
  │0x21 0x02│0x01 0x42│.. ..│.. ..│0x06 0x04│.. ..│
  └─────────┴─────────┴─────┴─────┴─────────┴─────┘

Basically, the algorithm adds the uint16 values starting from position 0 until a index variable is reaching 0. Even if the values are copied from a packed which was sent by the SADP Tool there is a checksum mismatch.

This issue has been fixed since patch version 1.1.0. The main algorithm implementation was correct, only the input parameters were interpret wrong. See checksum.h for details on the
arguments.


Get Email Label

Is it possible to get the labels associated with a Gmail::Message object?
I find a serious lack of documentation on how to handle single emails. Something like:
puts email.subject #prints the email subject
could be useful. I found out the most obvious by trial and error, some other by looking at the  source, but this does not make easy to get started. Thanks for your work.

This issue was moved to gmailgem/gmail#84


Unable to spawn in pet mobs in creative on server

This may or may not be a PetAI issue, but I noticed cats, horse, and dogs are missing from inventory in creative mode on our server. When loading the current set of mods and current save file into single player they show up fine. Since the animals from all three of the pet mods we are using were missing my best guess was the issue was central to PetAI. Is this a bug or am I just missing a setting somewhere?
Mod versions currently using of each are:
PetAI 1.3.5
Cats 1.3.3
Feverstone Horses 1.2.5
Wolf Taming 1.3.2

Do you have any other mods installed that might patch some things?
Are there any error logs regarding pets?
When I test (admittedly I only have a singleplayer run for testing right now) everything seems fine.

Creative mode on my test server with a lot of mods and the creatures are listed just fine


Importing pygsti.extras.devices fails.

Describe the bug
import pygsti.extras.devices fails.
Environment

pyGSTi version <IP_ADDRESS>
python version 3.8
OS X

This is due to a reference to a non-existent analysis.py file.  Commit 454b42f876c925fbf6cd43e7bc55c1e8282808a7 fixes this issue.  Let's leave this issue open until this commit makes it into a release.

Version 0.9.10 fixes this issue.


MyPy/typing stubs for docopt.

I have some mypy/typing stubs here for Docopt. Would this be something that Docopt is interested in doing? I can always use these locally, but I wanted to at least ask if you were open to the idea of adding this stub file to Docopt. It doesn't add any dependencies or anything, or change the way Docopt behaves.  It's an opt-in feature that only benefits people that want to use it (see mypy and pep-484).
There is another possible route for people that want to type check with the Docopt module, which is typeshed. They can be added there instead of this repo, but it still requires consent from the Docopt team.
This would catch type errors such as this:
mypy -c "
> from docopt import docopt
> usage = '''usage:
>     myscript
> '''
> argd = docopt(usage, version=True)"

<string>:6: error: Argument 2 to "docopt" has incompatible type "bool"; expected "str"

The stubs would need to be updated when function/method signatures change, or new ones are added. I wouldn't mind chipping in if no one else wants to.
I've tried to be as precise as possible with the types, and I've been running it against test_docopt.py. The tests use more of the docopt module than most projects I think. So far mypy doesn't generate any warnings/errors. You can check it out yourself in this branch:
# Using --verbose to make sure docopt.pyi is being parsed,
# and --silent-imports to quiet a warning about pytest's missing stubs.
# test_docopt.py doesn't have any stubs (probably not needed),
# so I'm telling mypy to check the function bodies anyway (against docopt.pyi).
mypy -s -v --check-untyped-defs test_docopt.py

What do you think? Is it too much for a simple library like Docopt?

Merged at https://github.com/bazaar-projects/docopt/pull/1, thanks!


Internal server error when creating App Configuration using Azure SDK for Go

I'm currently implementing a new Terraform resource to be able to create App Configuration instances. Using the Azure SDK for Go, creating works fine but requesting the operationsStatus I end up with following error response:
{"id":"/subscriptions/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx/providers/Microsoft.AppConfiguration/locations/westeurope/operationsStatus/1acc3289-3f22-ce0d-e6a2-185a8e1d8576","name":"1acc3289-3f22-ce0d-e6a2-185a8e1d8576","status":"Failed","error":{"code":"InternalServerError","message":"Cannot serve the request. Please retry."}}

Below you can find the response from the creation request:
{"type":"Microsoft.AppConfiguration/configurationStores","properties":{"provisioningState":"Creating","creationDate":"2019-11-06T23:22:58.6
592674+00:00","endpoint":"https://foobarz.azconfig.io"},"sku":null,"id":"/subscriptions/xxxxxxxxxxxxxxxxxxxxxxxxx/resourceGroups/test/providers/Microsoft.AppConfiguration/
configurationStores/foobarz","name":"foobarz","location":"westeurope","tags":{}}

For more information you can read through my code.

Hello @brennerm,
It looks like this issue is caused by specifying a non-valid SKU in the sku parameter of the configuration store resource. You can help confirm this by providing a valid SKU ("free" or "standard") and seeing if that fixes the issue.
Two questions may come up from this:

Where do you get the list of SKUs that are supported.

We are still in preview and expect most customers will use "free" as their SKU. We are currently adding a standardized Azure API which will allow all the SKUs available for each region to be listed. As we move forward we will ensure to document the available SKUs, which are a required parameter, as appropriate. There are descriptions for the two SDKs available here:

Why did the error message say "InternalServerError".

Looks like you helped us find a bug! The wrong error message is being returned. Thanks!
It looks like you jumped onto using the new Go SDK pretty quickly. Thanks for that.

Hey @jimmyca15, thanks for coming back to me.
I had indeed trouble finding the correct SKU names so thanks for the explanation. Using free as the SKU resolved my problem and the deployment went through. :tada: Documenting these somewhere appropriate would definitely help other people to work with your API/SDK.
Always happy to help out, thanks for your support. :+1:


Sort entity list

Hey Mirco, thats me again with another feature idea (does not know how to set a 'feature' label for a new issue).
I saw that my configured entity list (10 positions at the moment) has a random sort order in watch app - I suspect this is results from first get first serve, so whenever I run the app on the watch there is in fact no sorting mechanism applied for the entity list.
It would be nice to initially create an array of entities within companion app (fetchEntity) that is connected to some kind of ID (sort key) and always fetched with this order. I wish every time I run the app to have the same entity order (could be the order from settings list or at least to sort by entity name).
What do you think?
Cheers

Sounds useful, I agree :). Will consider that for v0.6 (v0.5 is already almost done).


Please add a reload command

A reload command would be a pretty useful addition to the plugin.

I'll look into adding one with the next update.

I've looked at this, and there will be a reload command for next update, though it might not work for everything.  The way this plugin was written makes it difficult to fully reload everything without major changes, so this is all I can offer.  If you want to fully reload the plugin, I'd suggest installing a plugin like plugman.

closing


Release notes for 2.3.0

hey! In the current master we don't announce Python 2.7 support in setup.py, but still install six, and still say 2.7 is supported in the README. Are there any changes regarding Python version support in this release?

@kmike :heavy_check_mark:


Allow publisher to be undefined

To make the extension authoring smoother for first time users, it would be nice if we no longer require the 'publisher' to be filled out.

fixed by https://github.com/Microsoft/vscode/commit/941c11cfc15f1d3039de4203b287138c32df93b0


package ‘qiime2r’ is not available (for R version 3.6.2)

Hi! I hope you can make this available for 3.6 soon.
Thanks!

so sorry, my mistake, it's all good now!


No values shown in chart from CSV

original.csv.txt
Hi,
I have a (moderately complicated) csv which I tried binjr on. The CSV loads fine, I see all column values, but when I drag and drop (which I assume is the right way) some columns over to a chart area, nothing is shown. The vertical axis of the chart area is adjusted fine, only the chart stays empty.
I wonder, do you not recognize quotes?
I attached the example csv.
Thanks, Thomas

Hi,
The CSV file you attached does indeed reveal a bug in binjr's CSV data adapter, which becomes visible when you drop two series from csv sources with the same name on a single chart.
This will be addressed in the next release.
Also, as noted in #87, please make sure the time range of the worksheet is set so it includes the period your csv has got samples for. You can change the time range by clicking on it, at the top of the worksheet.
Thanks for your report.
Fred

Thanks a lot! This was actually a bug in our SapMachine (https://github.com/SAP/SapMachine/issues/560). I now see my charts just fine.


[BUG] Graph viewer slowly drifts to top left

Describe the bug
When the graph viewer is left alone for a while, the graph slowly drifts to the top left.
To Reproduce
Steps to reproduce the behavior:

Open up a Graph Viewer for any compiler output
Wait. The graph will slowly drift to the top left corner

Expected behavior
It should stay in the same place.
Link
If applicable, please provide a link to Compiler Explorer to help explain your problem.
Screenshots

Desktop (please complete the following information):

OS: Ubuntu 18.04
Browser: Firefox
Version 73.0

Additional context
Add any other context about the problem here.

Interesting one: thanks! @cppchedy I know you're super busy at the moment, but any thoughts?

@mattgodbolt sorry for the late reply, I only saw the github notification(email) now.
@the-emerald  I couldn't  reproduce it  on my machine, maybe I am missing something?
I am using firefox 73.0.1 on fedora 31.
I checked for changes of version, but from what I saw it appears that there were no upgrades to vis.js. Also, looked at the cfg network configuration and compared it to previous state, nothings seems suspicious.
I think most likely that  it has to do with the library it self, not with something we have control over.
As can be seen from https://github.com/visjs/vis-network/releases, the libraries is now actively maintained and many bugs are being fixed. @the-emerald feel free to open an issue.

Not directly related to this bug, but since you are here...
I looked at the vis library not too long ago when bumping other dependencies. It seems the project is under new management and has restructured into a collection of smaller libraries.
Have you used the newer versions? Do you think upgrading would be painful?

@apmorton the last time I used vis.js was for compiler explorer cfg feature so my knowledge is pretty old. but reading through the release I spot many breaking change but I am not certain how (or if it affects) the way we are handling it.

Do you think upgrading would be painful?
if they changed the way nodes and edges are encoded, yes I think it will be painfull.

@cppchedy cheers. For some reason I couldn't reproduce it again either. Something's up. If you'd like I can open an issue in vis-network as well?

@the-emerald yes that will be awesome. please note that we are using version 4.20 of vis.js.


UX: Add "Refresh" data button

Background
Currently, our treasury app relies on other services for fetching data such as account balances. If a user is logged in with a previous cached session, they might not always see the latest data or changed they performed, unless they perform a hard refresh.
UX Need
We need to design a simple "Refresh" button to put on all pages. When a user clicks on it, it will force refresh the data, ensuring that users see the latest data.
Acceptance Criteria

[ ] Create a mockup showing what the Refresh button should look like
[ ] Create a follow up development ticket (with Ori) to implement new button

@ori-near @Megha-Dev-19
I think its the best place for this button. What do you thin?

hey @FREZZZBE, to be honest it took me a while to look at that refresh button, and wasn't this supposed to be specific to dashboard page?

hey @FREZZZBE, to be honest it took me a while to look at that refresh button, and wasn't this supposed to be specific to dashboard page?

We had a problem only with dashboard?
I agree but you need to find it only once and i bealeve you need it in rare cases. Do you have any idear of better places? @Megha-Dev-19 @ori-near

@FREZZZBE – I think this refresh button is a good solution for now, and we can revisit in the future based on feedback.
@Megha-Dev-19 – I think we need this button on all pages ... is that ok?

@ori-near add the dev ticket


Doc: Format example

Changes proposed:

Updated format of the example in the main README

Upgrade Path (for changed or removed APIs):
Acceptance Checklist:

[x] The commit message follows the guidelines in CONTRIBUTING.md.
[x] Documentation (README.md) and examples have been updated as needed.
[x] If this is a code change, a spec testing the functionality has been added.
[x] If the commit message has [changed] or [removed], there is an upgrade path above.

Coverage remained the same at 84.737% when pulling 3a43abcc7848c3767bfc50be0c4b13b82e242970 on PepijnSenders:doc/format-example into 0847049f19eaed81715e1263705564a569577774 on reactjs:master.


Update links.py

in line 15 the value of the variable was too long so you would have to scroll aside, I lowered half of it.
hope its ok :)

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is ordered alphabetically
[x] My submission has a useful description
[x] The description does not have more than 100 characters
[x] The description does not end with punctuation
[x] Each table column is padded with one space on either side
[x] I have searched the repository for any relevant issues or pull requests
[x] Any category I am creating has the minimum requirement of 3 items
[x] All changes have been squashed into a single commit

Hi @svg-mn
Thanks for your contribution ;)
We have some problems with Public APIs, so we won't be able to review/add this improvement right now.
Read this issue for more information, please: https://github.com/public-apis/public-apis/issues/3104


[chip-test,sival] SPI host events

Test point name
chip_sw_spi_host_events
Host side component
Rust
OpenTitanTool infrastructure implemented
Yes
Silicon Validation (SiVal)
Yes
Emulation Targets

[ ] None
[ ] CW310
[X] Hyperdebug + CW310

Contact person
marnovandermaas
Checklist
Please fill out this checklist as items are completed. Link to PRs and issues as appropriate.

[ ] Check if existing test covers most or all of this testpoint (if so, either extend said test to cover all points, or skip the next 3 checkboxes)
[ ] Device-side (C) component developed
[ ] Bazel build rules developed
[ ] Host-side component developed
[ ] HJSON test plan updated with test name (so it shows up in the dashboard)
[ ] Test added to dvsim nightly regression (and passing at time of checking)
[ ] For SiVal test cases, test is running relevant FPGA or silicon regression

Silicon validation effort estimation in days. There is a bit more effort here because of checking interrupts, etc:

estimate 4

Based on PR: https://github.com/lowRISC/opentitan/pull/19786

Fixed by #21221


curl: fix build issue on haas200, fix #1741

感谢提交 Pull Requests！
Thanks for submitting a pull request.

Security Check : b7db1bda32d07cf16dc5b7b63a5ea21162f090f9

auto build success,number:179

autotest fail,number:1410


Issues loading RedPajama Models?

@marella Is it possible to load and run any of the RedPajama variants? I have tried several variations of the following in Google Colab, but all of them cause the session to crash:
from ctransformers import AutoModelForCausalLM
llm = AutoModelForCausalLM.from_pretrained('keldenl/RedPajama-INCITE-Instruct-3B-v1-GGML',
                                           model_type = 'gpt_neox',
                                           #local_files_only = True,
                                           #lib = 'basic',
                                           )

Hey just wanted to say this worked well, thank you very much for the clarification!


TrigInterface simultaneous trig presses not all registering.

I noticed in chromatic node, playing chords some notes won't get played.
Further investigation reveals that this is an issue with the trig interface.
I think the problem could be on the MD side.
Simultaneous button presses. Some of the trigs dont get register
@yatli can you confirm ?

Alright. Drop turbo speed to 2x and problem is gone.
Sysex end_immediate is not fast enough to pick up all messages at 8x.

Debug mode off, problem goes away.
Nothing to see here.


TypeError: undefined is not an object ('_this.swiper=swiper')

It seems there is something wrong in here:
ref={ swiper => {
this.swiper = swiper
}}

What is wrong exactly?

I am getting the same error when I try to incorporate this project into my existing code or even just run the demo itself. I don't know enough about JavaScript to know what's wrong, just that I always get the "TypeError: undefined is not an object ('_this.swiper=swiper')" error each time, likely at that line cited in the comment above,
<CardStack style={styles.content} ref={swiper => { this.swiper = swiper }}>
      <Card style={[styles.card, styles.card1]}><Text style={styles.label}>A</Text></Card>
      <Card style={[styles.card, styles.card2]}><Text style={styles.label}>B</Text></Card>
      <Card style={[styles.card, styles.card1]}><Text style={styles.label}>C</Text></Card>
</CardStack>

What exactly is going with that ref? And why don't I see "ref" anywhere in the CardStack source code?

Ya I'm seeing the same thing.

I am seeing the very same error, Have any one of you figured it out ?

I ended up not using this library but it seems like it’s just trying to keep track of variable references. if you make an empty object and then assign the swipes variable to that it seems to work.

I think that because of the arrow function if you used the regular function then it wouldn't complain cause arrow functions don't create it's own context

Do you use that in a functional component or a class component?

For a functional component the proper way to use it may be more:
const [swiper, setSwiper] = useState<CardStack | null>(null)

  return (
    <CardStack
      style={styles.container}
      ref={(newSwiper): void => {
        setSwiper(newSwiper)
      }}>
      <Card style={[styles.card, styles.card1]}>
        <Text style={styles.label}>A</Text>
      </Card>
      <Card style={[styles.card, styles.card2]}>
        <Text style={styles.label}>B</Text>
      </Card>
      <Card style={[styles.card, styles.card1]}>
        <Text style={styles.label}>C</Text>
      </Card>
    </CardStack>
  )
}

For a functional component the proper way to use it may be more:
const [swiper, setSwiper] = useState<CardStack | null>(null)

  return (
    <CardStack
      style={styles.container}
      ref={(newSwiper): void => {
        setSwiper(newSwiper)
      }}>
      <Card style={[styles.card, styles.card1]}>
        <Text style={styles.label}>A</Text>
      </Card>
      <Card style={[styles.card, styles.card2]}>
        <Text style={styles.label}>B</Text>
      </Card>
      <Card style={[styles.card, styles.card1]}>
        <Text style={styles.label}>C</Text>
      </Card>
    </CardStack>
  )
}

You should add this to the docs then.

For a functional component the proper way to use it may be more:
const [swiper, setSwiper] = useState<CardStack | null>(null)

  return (
    <CardStack
      style={styles.container}
      ref={(newSwiper): void => {
        setSwiper(newSwiper)
      }}>
      <Card style={[styles.card, styles.card1]}>
        <Text style={styles.label}>A</Text>
      </Card>
      <Card style={[styles.card, styles.card2]}>
        <Text style={styles.label}>B</Text>
      </Card>
      <Card style={[styles.card, styles.card1]}>
        <Text style={styles.label}>C</Text>
      </Card>
    </CardStack>
  )
}

You should add this to the docs then.

Even though state gets updated with the ref of CardStack, if you try invoking any of the swipeRight or swipeLeft actions I'm seeing it not doing anything.

I ended up not using this library but it seems like it’s just trying to keep track of variable references. if you make an empty object and then assign the swiper variable to that it seems to work. I'm not really sure how or why this is helpful though so it may be fine just to remove.
const t = {};
// and then

<CardStack style={styles.content} ref={swiper => { t.swiper = swiper }}>

EDIT: I see it's used in instances like this below where you want to use methods on the swiper. Seems like this may also be a fix: #73
<CardStack style={styles.content} ref={swiper => { this.swiper = swiper }}>
    <Card style={[styles.card, styles.card1]}><Text style={styles.label}>A</Text></Card>
    <Card style={[styles.card, styles.card2]}><Text style={styles.label}>B</Text></Card>
  </CardStack>

  <TouchableOpacity onPress={ () => { this.swiper.swipeLeft() }}>
    <Text>Left</Text>
  </TouchableOpacity>

Bro, you've have just saved my life. 👍


Add pab-local-cluster

Add a pab-local-cluster tool that starts up a local cluster (private testnet) with wallet, chain index, PAB

Parts of it are copied from cardano-wallet

Split up the chain index project into

plutus-chain-index-core: The chain index libraries (used to be the plutus-chain-index project)
plutus-chain-index: A new library that implements the executable /  app. This was done so that we can import the code in other places, which wasn't possible when it was an executable.

Running the integration tests:

cabal build plutus-pab-local-cluster cardano-node cardano-wallet
Clone https://github.com/input-output-hk/cardano-wallet/ and set the SHELLEY_TEST_DATA environment variable to the absolute path of the plutus-pab/local-cluster/cluster-data/cardano-node-shelley in your local clone of the plutus-apps repository.
cabal exec plutus-pab-local-cluster
Wait until the message Starting PAB backend server on port 9080 appears
Run curl -H "Content-Type: application/json" -v -X POST -d '{"caID":{"tag":"IntegrationTest"},"caWallet":{"getWalletId":"2d4cc31a4b3116ab86bfe529d30d9c362acd0b44"}}' localhost:9080/api/contract/activate to start the test. A couple of log messages appear, the last one should say something like fbca6236-f532-43d9-89db-6ddc7002336e: "Tx confirmed. Integration test complete."

Notes

The node configuration used by the local cluster has much shorter epoch / slot times than the public testnet or mainnet
It also seems to have more frequent rollbacks than those nets (which is good for us because this makes it easier to test the code in the presence of rollbacks)

TODO / Plans:

[x] Figure out a better way to get the test data from cardano-wallet --> add it to this PR
[x] Start up chain index
[x] Start up PAB with correct wallet config
[x] Add a test that creates and spends a script output
[ ]  PR to cardano-wallet
[x] Reduce log levels for wallet client

Pre-submit checklist:

Branch

[ ] Tests are provided (if possible)
[ ] Commit sequence broadly makes sense
[ ] Key commits have useful messages
[ ] Relevant tickets are mentioned in commit messages
[ ] Formatting, materialized Nix files, PNG optimization, etc. are updated

PR

[ ] Self-reviewed the diff
[ ] Useful pull request description
[ ] Reviewer requested

@james-iohk Updated the PR description

Thanks @j-mueller. I think it'd be worth adding these details to the plutus-pab/README.md. Although, it's already quite large so maybe just mention the local-cluster there and add details in a new plutus-pab/local-cluster/README.md.

When running the cabal build plutus-pab-local-cluster cardano-node cardano-wallet command I had problems building the lzma-<IP_ADDRESS> (lib) dependency. The error was that it could not find the lzma.h file. This file is apart of the XZ package. To fix, download the XZ package, and use the ./configure -> make -> make install commands. I hope this helps someone out!


fixfix mysql MTMV do not automatically refresh even if the refresh method is COMPLETE

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall


Allow commenting on commit file changes

Current behavior:
If I want to review the PR commits I can't comment on the files, I opened through the commits view, I must find these changes in the Files view and comment on them there.
Example:
I cant comment in the StakeModalValidatorInfo if I opened it through commits but I can if I opened it through files(containing all the changes)

FYI: It seems there is no problem if there is only one commit.

Hi, any updates on this? I suppose that reviewing commit by commit is pretty standard procedure, until this is resolved it's basically impossible.

(Duplicate of #2793?)

Thank you for the duplicate tagging!


Implicit Flow - Javascript Client without User

Hello,
I am implementing implicit flow for my javascript client. The only purpose of client is accessing API which is protected by IdentityServer4. I just see examples of implicit flow including user interaction. But in this case, there is no user but the client is javascript . So, can I use implicit flow like this or must I implement client credentials flow?

In this case you would use client credentials flow.
But that means that you either need to hard code the client secret in the JS code, or use no secret at all.

Okay thank you.


Update 2.1.0

WIP: Currently testing and debugging builds

Linter check found the following problems:
The following problems have been found:
ERROR: build.sh:187: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:42: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:87: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:113: build_tools_must_be_in_build: The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build.sh:187: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:42: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:87: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:113: build_tools_must_be_in_build: The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build.sh:187: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:42: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:113: build_tools_must_be_in_build: The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build.sh:187: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:42: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:87: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:113: build_tools_must_be_in_build: The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build.sh:189: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:42: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:87: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:113: build_tools_must_be_in_build: The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build.sh:191: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:42: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:87: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:113: build_tools_must_be_in_build: The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build.sh:191: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:42: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:87: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:113: build_tools_must_be_in_build: The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build.sh:191: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: clone/recipe/meta.yaml:91: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:117: build_tools_must_be_in_build: The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build.sh:191: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:44: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:89: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:115: build_tools_must_be_in_build: The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build.sh:191: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:44: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:89: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:115: build_tools_must_be_in_build: The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build.sh:191: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:44: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:89: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:115: build_tools_must_be_in_build: The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build.sh:195: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:44: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:89: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:115: build_tools_must_be_in_build: The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build.sh:195: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:44: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:89: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:115: build_tools_must_be_in_build: The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build.sh:195: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:44: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:89: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:115: build_tools_must_be_in_build: The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build.sh:195: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:44: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:89: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:115: build_tools_must_be_in_build: The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build.sh:195: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:44: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:89: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:115: build_tools_must_be_in_build: The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build.sh:195: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:44: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:89: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:115: build_tools_must_be_in_build: The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: bld_pytorch.bat:65: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: build_pytorch.sh:195: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-cpu": No tests were found.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-gpu": No tests were found.
ERROR: clone/recipe/meta.yaml:23: patch_unnecessary: patch should not be in build when source/patches is not set
ERROR: clone/recipe/meta.yaml:35: version_constraints_missing_whitespace: output "pytorch-cpu": Packages and their version constraints must be space separated
ERROR: clone/recipe/meta.yaml:43: version_constraints_missing_whitespace: output "pytorch-gpu": Packages and their version constraints must be space separated
WARNING: clone/recipe/meta.yaml:113: build_tools_must_be_in_build: output "pytorch": The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:139: build_tools_must_be_in_build: output "pytorch": The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: bld_pytorch.bat:65: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: build_pytorch.sh:195: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-cpu": No tests were found.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-gpu": No tests were found.
ERROR: clone/recipe/meta.yaml:22: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:67: build_tools_must_be_in_build: The build tool pkg-config is not in the build section.
ERROR: clone/recipe/meta.yaml:92: version_constraints_missing_whitespace: output "pytorch-cpu": Packages and their version constraints must be space separated
ERROR: clone/recipe/meta.yaml:101: version_constraints_missing_whitespace: output "pytorch-gpu": Packages and their version constraints must be space separated
WARNING: clone/recipe/meta.yaml:172: build_tools_must_be_in_build: output "pytorch": The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:198: build_tools_must_be_in_build: output "pytorch": The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: bld_pytorch.bat:65: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: build_pytorch.sh:195: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-cpu": No tests were found.
ERROR: clone/recipe/meta.yaml:23: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:113: build_tools_must_be_in_build: output "pytorch": The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:139: build_tools_must_be_in_build: output "pytorch": The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: bld_pytorch.bat:65: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: build_pytorch.sh:195: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-cpu": No tests were found.
ERROR: clone/recipe/meta.yaml:23: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:112: build_tools_must_be_in_build: output "pytorch": The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:138: build_tools_must_be_in_build: output "pytorch": The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build_pytorch.sh:195: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-gpu": No tests were found.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-cpu": No tests were found.
ERROR: clone/recipe/meta.yaml:23: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:112: build_tools_must_be_in_build: output "pytorch": The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:138: build_tools_must_be_in_build: output "pytorch": The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build_pytorch.sh:195: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-gpu": No tests were found.
ERROR: clone/recipe/meta.yaml:30: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:119: build_tools_must_be_in_build: output "pytorch": The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:145: build_tools_must_be_in_build: output "pytorch": The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build_pytorch.sh:195: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-cpu": No tests were found.
ERROR: clone/recipe/meta.yaml:30: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:119: build_tools_must_be_in_build: output "pytorch": The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:145: build_tools_must_be_in_build: output "pytorch": The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build_pytorch.sh:195: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-gpu": No tests were found.
ERROR: clone/recipe/meta.yaml:30: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:119: build_tools_must_be_in_build: output "pytorch": The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:145: build_tools_must_be_in_build: output "pytorch": The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build_pytorch.sh:197: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-gpu": No tests were found.
ERROR: clone/recipe/meta.yaml:30: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:129: build_tools_must_be_in_build: output "pytorch": The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:155: build_tools_must_be_in_build: output "pytorch": The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build_pytorch.sh:197: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-cpu": No tests were found.
ERROR: clone/recipe/meta.yaml:30: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:129: build_tools_must_be_in_build: output "pytorch": The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:155: build_tools_must_be_in_build: output "pytorch": The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build_pytorch.sh:198: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-cpu": No tests were found.
ERROR: clone/recipe/meta.yaml:30: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:129: build_tools_must_be_in_build: output "pytorch": The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:156: build_tools_must_be_in_build: output "pytorch": The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: bld_pytorch.bat:73: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: build_pytorch.sh:197: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-cpu": No tests were found.
ERROR: clone/recipe/meta.yaml:28: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:127: build_tools_must_be_in_build: output "pytorch": The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:153: build_tools_must_be_in_build: output "pytorch": The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build_pytorch.sh:197: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-gpu": No tests were found.
ERROR: clone/recipe/meta.yaml:29: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:128: build_tools_must_be_in_build: output "pytorch": The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:154: build_tools_must_be_in_build: output "pytorch": The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: build_pytorch.sh:197: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-gpu": No tests were found.
ERROR: clone/recipe/meta.yaml:29: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:128: build_tools_must_be_in_build: output "pytorch": The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:154: build_tools_must_be_in_build: output "pytorch": The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/bld_pytorch.bat:73: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/build_pytorch.sh:197: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-cpu": No tests were found.
ERROR: clone/recipe/meta.yaml:29: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:128: build_tools_must_be_in_build: output "pytorch": The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:154: build_tools_must_be_in_build: output "pytorch": The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/bld_pytorch.bat:73: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/build_pytorch.sh:197: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-cpu": No tests were found.
ERROR: clone/recipe/meta.yaml:28: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:128: build_tools_must_be_in_build: output "pytorch": The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:154: build_tools_must_be_in_build: output "pytorch": The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: bld_pytorch.bat:79: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-cpu": No tests were found.
ERROR: clone/recipe/meta.yaml:29: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:155: build_tools_must_be_in_build: output "pytorch": The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: bld_pytorch.bat:79: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-cpu": No tests were found.
ERROR: clone/recipe/meta.yaml:29: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:155: build_tools_must_be_in_build: output "pytorch": The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/bld_pytorch.bat:85: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/build_pytorch.sh:197: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-cpu": No tests were found.
ERROR: clone/recipe/meta.yaml:30: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:130: build_tools_must_be_in_build: output "pytorch": The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:156: build_tools_must_be_in_build: output "pytorch": The build tool ninja is not in the build section.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/bld_pytorch.bat:82: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/build_pytorch.sh:197: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-cpu": No tests were found.
ERROR: clone/recipe/meta.yaml:30: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:130: build_tools_must_be_in_build: output "pytorch": The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:156: build_tools_must_be_in_build: output "pytorch": The build tool ninja is not in the build section.
Errors were found

The builds here were done with python 3.10 only (by accident). They will most likely work with other pythons too, but I'd rather save another 1-day build cycle. If reviewers are ok with approving based on these build results, that would be helpful

@M-Waszkiewicz-Anaconda @JeanChristopheMorinPerso @cbouss if I've addressed all your comments, is an approval possible?

Thanks JC :)

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/bld_pytorch.bat:83: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/build_pytorch.sh:197: pip_install_args: output "pytorch": pip install should be run with --no-deps and --no-build-isolation.
ERROR: clone/recipe/meta.yaml:1: missing_tests: output "pytorch-cpu": No tests were found.
ERROR: clone/recipe/meta.yaml:30: patch_unnecessary: patch should not be in build when source/patches is not set
WARNING: clone/recipe/meta.yaml:129: build_tools_must_be_in_build: output "pytorch": The build tool pkg-config is not in the build section.
WARNING: clone/recipe/meta.yaml:155: build_tools_must_be_in_build: output "pytorch": The build tool ninja is not in the build section.
Errors were found


More transaction modal cleanup

Changes

Funds tab scroll content under top bar so view details button stays fixed
Cleaned up the submit complete order form
Complete order form now slides into the top section
Fixes #751
Fixes #753
Fixes #814
textareas should render the correct typeface across operating systems now
Cleaned up notifications
Changed the way unread notifications display
Added tooltip next to minimum price in Add/Edit listing

@jjeffryes you can merge whenever. I'm going to go spend some time working on website stuff and will start a new branch to clean up transaction modal tomorrow morning.

This PR has been updated with various bugfixes and enhancements.

hitting the enter key sends transaction discussion messages
notifications are sorted in reverse chronological order
missing notification types added
problem with user banner css fixed
duplicate confirmation form removed from transaction modal template
Closes #843


warning: PICT rendering failed (mask region rect Rect(x1=-27892, y1=26790, x2=0, y2=256) is not same as source rect

I got a new one for you 😊
Most of the PICT resources in Dude 2000 v2.71 fail to decode. (Disclaimer: I wrote this game when I was like, 11)
... dudenew/Dude 2000 v2.71_PICT_1118.pict
warning: PICT rendering failed (mask region rect Rect(x1=-27892, y1=26790, x2=0, y2=256) is not same as source rect Rect(x1=152, y1=163, x2=398, y2=388)); attempting rendering using picttoppm
picttoppm: Invalid PICT: compressed line of 63232 bytes for Row 0 is too big to represent a 256-byte padded row, even with worse case compression.
warning: failed to decode resource: picttoppm failed (256)

PICT 1118 totally fails both resource_dasm and picttoppm. I will raise this issue separately with the NetPBM guy. The picttoppm error here doesn't make sense to me, since the entire PICT is only 6826 bytes.
... dudenew/Dude 2000 v2.71_PICT_1119.pict
warning: PICT rendering failed (mask region rect Rect(x1=-27892, y1=26790, x2=0, y2=256) is not same as source rect Rect(x1=152, y1=163, x2=398, y2=388)); attempting rendering using picttoppm

PICT 1119 fails in resource_dasm, and picttoppm does not have an error but I still don't get the BMP output for some reason?
Actually, now I'm confused, because for 1120 I did get a BMP file, but the program output looks identical to 1118, which failed totally and gave me the raw PICT output?
... dudenew/Dude 2000 v2.71_PICT_1120.bmp
warning: PICT rendering failed (mask region rect Rect(x1=-27892, y1=26790, x2=0, y2=256) is not same as source rect Rect(x1=27, y1=163, x2=523, y2=388)); attempting rendering using picttoppm
picttoppm: Invalid PICT: compressed line of 1153 bytes for Row 0 is too big to represent a 496-byte padded row, even with worse case compression.
warning: failed to decode resource: picttoppm failed (256)

I ran resource_dasm again with skip-decode and the 3 PICTs (1118, 1119, 1120) are in the attached ZIP. The entire game is available here, use The Unarchiver to decompress: https://mikerichardson.name/graveyard/dude2000_271.sit
3 picts.zip
Even weirder: 1118 and 1119 render fine in Catalina (Preview, QuickLook, etc). 1120 does not (just shows white). The BMP output I got from (whatever managed to decode it) is correct (just shows blue).

My build of resource_dasm is from master on July 11, 2022. If any PICT stuff changed since then let me know and I'll try with the latest sources. (It's not super easy to build for me, for some reason.)

I was using a December 2021 build at first, which gave the first title, then I ran again with July 2022 build.
This is on Intel and Catalina, btw.

There were some recent changes to PICT decoding; if I recall correctly, some coordinates were computed incorrectly if the bounds rect wasn't anchored at (0, 0), and the region model was entirely rewritten to handle egregiously large regions gracefully. The new code is a bit slower in certain cases but substantially more correct; many more PICTs now render properly.
I downloaded the copy of Dude 2000 that you linked, and it appears that all of the PICTs are correctly decoded with the latest version. (Except for PICT 3001, which uses vector drawing commands... I'll get around to implementing those someday.)

Yeah I just built the latest version (because I noticed that the machine code disassembly stuff was separate, so I thought the build size of resource_dasm would be smaller). I opened a separate issue for that.

New Nov 12 2022 build confirmed, decodes everything except 3001.
You know what's wild? Catalina does render something for 3001... It's even sort of correct.  I know it handles text opcodes because I have other games that use that for the about window).
Catalina rendering PICT

Example of default button

#59 for the build size stuff, closing this one


Double left click does not show benchmark in WPF

Issue:
Just tried version 5.0.45 and realized that double left click does not show benchmark, both in my own code and in the ScottPlot WPF Demo.
It is working for WinForms. Triggering UserInputProcessor.DoubleLeftClickBenchmark(true) also does not help.
ScottPlot Version: 5.0.45

both in my own code and in the ScottPlot WPF Demo

It may be that many of the demo windows intentionally disable this feature.
I created a new .NET 8 WinForms project according to the directions in https://scottplot.net/quickstart/winforms/ and it works as expected. Maybe start there and confirm it works for you too?

It is working for WinForms

My bad, I just now realized this is specifically discussing WPF. Taking a closer look...

It looks like the issue is here:
https://github.com/ScottPlot/ScottPlot/blob/11231f95d0caf55d3a2c5d60909e74fb3af95c67/src/ScottPlot5/ScottPlot5 Controls/ScottPlot.WPF/WpfPlot.cs#L46
After click 1 the focus is lost, resetting memory of the first click, then click 2 is treated like a single click

Got it resolved! Thanks again for reporting this @onur-akaydin. That was a sneaky one to track down, but I'm happy to know that it will be fixed in the next release I intend to publish to NuGet tomorrow 🚀


[C++] Build fail with Clang 19-rc2 "arithmetic on a pointer to an incomplete type"

Describe the bug, including details regarding any error messages, version, and platform.
Compiling Arrow 15.0.0 with Clang 19 results in error: arithmetic on a pointer to an incomplete type 'FileInfo' in FileSystemDatasetFactory class.
Can't test latest Arrow right now.
A complementary issue to https://github.com/llvm/llvm-project/issues/102293, more info there.
Component(s)
C++

Tested with 17.0.0, same issue

Can you please post the full error trace? Otherwise it's not possible to understand what happens here.

Issue fixed on Clang side, forgot about this one.


Set class to main element

Hello, how can i change style of main element?
<main class="kanban-drag"></main>

I mean i want to set different classes to each main elements.

Hi @vetash ,
Do you mean the board's class property?
[
    {
        "id"    : "board-id-1",               // id of the board
        "title" : "Board Title",              // title of the board
        "class" : "class1,class2,...",        // css classes to add at the title
        "dragTo": ['another-board-id',...],   // array of ids of boards where items can be dropped (default: [])
        "item"  : [                           // item of this board
            {
                "id"    : "item-id-1",        // id of the item
                "title" : "Item 1"            // title of the item
            },
            {
                "id"    : "item-id-2",
                "title" : "Item 2"
            }
        ]
    },
    {
        "id"    : "board-id-2",
        "title" : "Board Title 2"
    }
]

Yes, but class param affect only for board title not body.


VRAM Requirements to Fine-tune SVD

Hi,
Found your repo very useful.
I was wondering whether you know how much VRAM is necessary to train/fine-tune SVD in the normal setting (without mask)?
Thank you,
Miguel

Finetuning the whole model requires 80G VRAM. If you just finetune the temporal layers, and reduce the resolution, 32G is also enough.


Updating a Json field in postgresql does not remove properties from the json in the DB

Describe the bug
Let's say that I have a document table in PostgreSQL with a column named metadata of type jsonb.
And I have a Document entity in mikro-orm with a metadata property of type any like this:
class Document {
    @Property({ nullable: true, type: 'jsonb' })
    public metadata?: any;
}

I do an update on the table for a record, and send the following json in the metadata:
{
      "propa": "test",
      "propb": "test",
      "propc": "test",
}

After that I do another update:
{
      "propa": "test",
      "propd": "test",
}

The result in the DB is:
{
      "propa": "test",
      "propb": "test",
      "propc": "test",
      "propd": "test",
}

It appears the properties get merged instead of replaced. Is there a way to influence this?
Reproduction
see description.
What driver are you using?
@mikro-orm/postgresql
MikroORM version
6
Node.js version
18+
Operating system
windows
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Slack.
[X] The provided reproduction is a minimal reproducible example of the bug.

Please provide reproduction as code, its not clear what you are doing.


Disable channel if bandwidth below channel reserve and configured value

Description
To disable or enable a channel depending on if it has sufficient bandwidth this PR adds an additional check of public channels with each sample tick in the Channel Status Manager.
It will disable a channel with a balance lower than the channel reserve, as the channel will be incapable of routing HTLCs. The channel will be enabled again should the bandwidth become above the required value and if the last status update was a disable due to low bandwidth.
A channel status can only go from ChanStatusEnabled -> ChanStatusBandwidthDisabled; and only reverse if the ChanStatusBandwidthDisabled was not overridden due to other automatic or manual interventions.
Additionally, the bandwidth requirement can be increased with a new option chan-required-bandwidth, which allows to define a minimum value for the actual amount available for routing below which the channel must be disabled (so the amount must be equal or greater than the sum of the reserved amount and the amount defined with required bandwidth).
Notes
For the integration tests the channel balances had to be slightly adjusted to not trigger the automatic disabling on one side due to a balance of 0. New integration tests have not been added, as I think the unit tests added are sufficient.
Finally, I also took the liberty to add a short sentence to the updatechanstatus CLI due to #5375. However, I will remove it if it is not considered to be in the scope of this PR.
Fixes #3717

How can the balance dip below the reserve?

How can the balance dip below the reserve?

With an initial channel open from a remote peer the local balance will be zero. You can receive sats below this reserved value, but you can first send out when the balance is above it. Also the reserved value may (I am not sure) be fluctuating depending on mempool, etc. to be able to pay for fees, etc.

In 0.13.0 there will be full control for the user of the disable status so any heuristic desired may be applied

@alexbosworth Do you suggest to remove the configurability of required bandwidth? Because I think it would still make sense to automatically disable channels that have no bandwidth (balance below channel reserve). Just like when the remote is disconnected a channel is also automatically disabled to let the noise it that channel cannot route in advance.

@alexbosworth Do you suggest to remove the configurability of required bandwidth? Because I think it would still make sense to automatically disable channels that have no bandwidth (balance below channel reserve). Just like when the remote is disconnected a channel is also automatically disabled to let the noise it that channel cannot route in advance.

I think it would make sense to take control of your own disable strategy. A problem with disable is that if you start a channel and then balance it after starting, the gossip might be slow that it is enabled and then you can't use the new channel for 24h
Another way to go about it is setting a bit of a higher fee if you have a lower balance, this discourages traffic for a while so it minimizes errors

I think your specific example could be handled similar to how channels are already disabled with a delay when the remote peer goes offline. But more generally think that exhausted channel sides that cannot route are a problem for path finding. I therefore felt that having LND turn them off by default would be a net-benefit, since a routing node should ensure that it has sufficient bandwidth by re-balancing and rarely/never enter a state where it would be disabled automatically.
I may revisit this issue in future if automatically setting a higher fee on channels that have no bandwidth is considered more desirable.

I think your specific example could be handled similar to how channels are already disabled with a delay when the remote peer goes offline. But more generally think that exhausted channel sides that cannot route are a problem for path finding. I therefore felt that having LND turn them off by default would be a net-benefit, since a routing node should ensure that it has sufficient bandwidth by re-balancing and rarely/never enter a state where it would be disabled automatically.
I may revisit this issue in future if automatically setting a higher fee on channels that have no bandwidth is considered more desirable.

Another way this could go wrong: use rebalancing to control liquidity to toggle channels on and off until the rate-limiting kicks in and no more updates are allowed for 24h, now you have a button to press to disable someone else's channel

Ah yes, I see! Thanks for the discussion and explaining it.


First implementation to Fix Issue #590

Ok @lmcinnes so, following on your comment on the ugliness of the first workaround implementation (and I totally shared the feeling), here is a different attempt to fix the function and to also get rid of code duplications with a more compact implementation covering the two cases.
Issue: The issue was indeed related to the result array being allocated differently (as in different shapes) within the two alternative if branches - this upsets numba for some reason. Still not quite sure why.
Therefore, another quick workaround implementation is provided, and tested as pytest.fixture
(please see here)
Specifically, a new dedicated test module has been created to verify the proposed compact implementation and the original workaround.
Of course, it goes without saying that both implementations allow all tests in test_umap_metrics to PASS.
Please see below the description of the commit:

This commit includes a new implementation for the chunked_parallel_spatial_metric in distances to fix issue #590 causing Python 3.8 to fail tests in the case when X and Y parameters are passed.
In more details, this new implementation addresses the issue and also provides a more compact version to avoid code duplications on the two branches (i.e. Y is|is not None).
In order to tests the two implementations, a special fixture/decorator is created to compare calculations with a quick-fix implementation of the previous original chunked_parallel_special_metric as implemented by Leland.

Feel free to send feedback on the compact implementation: personally I tried to replicate the same logic in your initial idea.
However, I am not necessarily convinced that adding those if clauses for the symmetrical cases is indeed more performant than doing the iteration loop (in parallel) in all locations, anyway.
It is indeed true that in the case of very big matrices, lots of computation can be saved - at the price of if clauses which are notoriously costly.
I would love to hear your comments on this! Thank you :)

Hello @leriomaggio! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file umap/tests/test_chunked_parallel_spatial_metric.py:

Line 5:1: E302 expected 2 blank lines, found 1
Line 8:89: E501 line too long (116 > 88 characters)
Line 52:89: E501 line too long (112 > 88 characters)
Line 56:89: E501 line too long (111 > 88 characters)
Line 81:89: E501 line too long (106 > 88 characters)
Line 86:89: E501 line too long (115 > 88 characters)
Line 92:89: E501 line too long (114 > 88 characters)
Line 97:89: E501 line too long (104 > 88 characters)
Line 98:89: E501 line too long (110 > 88 characters)
Line 103:89: E501 line too long (101 > 88 characters)

I like what you manage to do the clean things up from the first fix you posted to the issue! It looks a lot cleaner now. I'll have to do some benchmarking and see how performance compares because, as you note, the if statements now introduce some extra overhead.

So the good news is that it works; the bad news is that, at least in my quick benchmarking, it is very slow. I suspect the added if statements create a lot of overhead in what are tight inner loops, so the whole thing slows down a lot. I'll try and see if I can come up with an alternative formulation that still works, but runs as fast as the old version.

Great @lmcinnes thanks a lot for the feedback and the quick benchmarking - I was indeed too curious to see whether our initial guess about the if-clause were indeed correct.
So I setup a quick benchmark tests (using pytest-benchmark - first time, lots of fun indeed!!) and run it on two alternative implementations (I simply tried the same getting rid of the if clauses).
I could indeed try the "ugly" workaround too for comparison 👍
I also pushed the benchmark report - thought it was the quickest to share it, we will remove it before merging.
Here is the link to the benchmark report
Note: I've done a bit of editing to testing function names to allow for an easier-to-read report!
Quick legend: test_with_IF_ refers to the implementation with the IF clause checks (implementation);
test_FULL_it_ refers to the alternative implementation with no control, and full iterations (implementation).
Suffices _x_only or x_y are self-explanatory and refers to the function called with either X and X, Y respectively.
Results are indeed interesting, now I'm intrigued how the workaround behaves.
At a very first glance, it looks that we were right!
Looking forward to receiving your impressions too! 🙌
Thanks a lot for testing on Py3.9 & Numba as well!

Ah btw, "RE: pytest-benchmark
Forgot to say: the great thing about that plugin was that I was able to specify a "group" name for tests so it automatically grouped runs for comparison. It seems very well done, indeed.

I wouldn't mind the "ugly workaround" for comparison, although your new alternative approach to remove the if looks pretty good.
The pytest-benchmark looks pretty useful! I wonder if we should have some benchmark reports produced for a few standard datasets so we can check for performance regressions. It would probably be a matter of setting that up as a separate run on azure pipelines. Certainly something for the future.

Brilliant!
The "ugly workaround" is running - it should take less time than the other, and I should be able to post results soon! 🙌
RE: Performance Regression tests: ➕ 1
I personally think that this is a wonderful idea! Should also allow to keep track of performance through the different numba versions in the backend.

Report pushed: the two implementations are indeed pretty close! (the ugly is still winning slightly)
In this benchmark I also changed the input data size, ranging from a matrix [100x100] up to [1000x1000].
They ran on my laptop (with no GPU acceleration). Performance are not that bad, after all :)
Intrigued to test on a GPU - will try that later, if I have time.

The two options look pretty much comparable, so I would suggest you go with whichever you prefer.

Brilliant, thanks! So I already updated distances.py with the new implementation in my last commit.
The last thing I would like to discuss with you is what to do with the test and the reports in the repository, before merging into main.
I shall assume I can get rid of performance reports, and that's fair.
What about performance testings?
My suggestion right now would be to keep them in the test suite, but skip them - similarly to what we do now when skipping tests for unmet dependencies (e.g. Tensorflow).
So, if no BENCHMARK variable is set in os.environ, we are going to skip those tests - so that we can enable that variable in the future if we aim at including performance regression testing.
Does this make any sense?
Thanks, Valerio

Sounds good to me!

Sounds good to me!

Brilliant, thanks! I've just pushed those changes, and a bit of refactoring - polishing the tests a bit.
It should be ready for MERGE :)

Coverage decreased (-1.6%) to 88.507% when pulling cde7245ffbaec7d062108c1f836ec61e2a4a5854 on quickfix_chunked_parallel_special_metric into 18c4e759aa125d4f97f16807aca42c3254e7d86b on master.


docs: update siteConfig documentation for publishing with GitHub Pages

Updated publishing docs to resolve #1029
Motivation
I had trouble publishing my first Docusaurus built site to GitHub pages (as detailed in #1029) and this PR has the updates to the documentation that were needed in order for me to publish my site.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Only docs were changed. Run the site an ensure formatting is correct

Related PRs

Many thanks @alexdriedger! 🎉
Looking forward to future contributions from you 😄


docs: add vite-plugin-react-pages to plugin list

Ugh, this actually asks you to submit your plugin to awesome-vite instead of here 😅
This is mostly to separate the concerns and avoid getting too many PRs in this repo.

Ugh, this actually asks you to submit your plugin to awesome-vite instead of here 😅
This is mostly to separate the concerns and avoid getting too many PRs in this repo.


Add support for URL-encoded form parameters?

This is referring to the parameters that are typically found in the body of POST requests when you submit a <form> on a website.
HttpClientMock client = new HttpClientMock();

//request body looks like: username=John&password=secret%21
//content type is: application/x-www-form-urlencoded

client.verify().post("/login")
  .withBodyParameter("username", "John")
  .withBodyParameter("password", "secret!")
.called();

//or maybe

client.verify().post("/login")
  .withBody(
    new BasicNameValuePair("username", "John"),
    new BasicNameValuePair("password", "secret!")
  )
.called();

I have started looking at the codebase and working on a solution. Do you think this would be useful? Can HttpClientMock already do this?

Merged in #20


midline facial cleft - synonym and EQ

midline facial cleft MP:0000108
NEW SYN: median facial cleft
NEW SYN: mid-face cleft
NEW SYN: mid-facial cleft
NEW SYN: midfacial cleft
SUGGESTED EQ:
has part some ('split medially' and ('characteristic of' some face) and ('has modifier' some abnormal))

Added EQ:
has part some ('split medially' and ('characteristic of' some face) and ('has modifier' some abnormal))


Insiders closed with crash. When opened - Untitled files are duplicated in separate window

VSCode Version: 1.25.0-ins
OS Version: win7x64

I've just got an update to version:
Version: 1.25.0-insider
Commit: b4a18da6e78f95295ea6538f5ae8dd0c9f0869a9
Date: 2018-06-19T07:49:07.900Z
Electron: 2.0.2
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64

And at the same time, 10 minutes before update, I've set a setting "files.hotExit" to "onExitAndWindowClose" in the Settings
So, I don't what caused this crash, update or this setting.
And then the strange thing happened after launch - all my 8 Untitled files were duplicated to separate window with Plain text language mode in all of them. (I've had different: css, js, xml, etc.)
Talking about workspace - it's been saved before all these actions.
img:

console message:

INFO no standard startup: not just one window   ---   log.ts:159

AppData\Roaming\Code - Insiders\logs:
logs.zip

This is odd, I haven't seen it before. I notice you have the following:

You're in a multi-root workspace
You're on Windows 7
You're running as admin

I tried to repro and failed using a multi-root workspace on macOS as I'm away from my Windows machine atm. @user3323 does this repro consistently when you crash the window via task manager? Also does running VS Code not as admin fix it?

@Tyriar  hi there.
I'm not quite sure what do you mean by "multi-root" workspace.
Do I use files from different folders in my workspace? Yes.
Windows 7 x64
I don't know how to force launch app without Administrator mode. They all run with it. Do you have an advice?
And I've crashed VS Code on purpose via task manager.... and it really strange. First crash (after your comment) - it DID repro, then 4 more force crashes - and it did NOT repro. Really strange behavior.

I'm not quite sure what do you mean by "multi-root" workspace.
Do I use files from different folders in my workspace? Yes.

That's what I mean, by root I mean root folder.

I don't know how to force launch app without Administrator mode. They all run with it. Do you have an advice?

Windows 7 shouldn't do that...? ctrl+shift+enter or right click is needed to force admin mode doesn't it 😕

@Tyriar

right click is needed to force admin mode

are we talking about forcing admin mode or forcing NON admin mode?
you asked me:
Also does running VS Code not as admin fix it?
so, not as admin, means NON admin mode right?
and I answered, that I don't know how to force launch VSCode with NON admin mode

Normally Windows will run nothing as administrator, you need to right click the application and select Run as Administrator in the context menu. That's what's confusing me.

@chrmarti  @Tyriar  hey, it's happened again. But now - behavior even MORE strange.
I had all my Untitled files in workspace, named "WSPACE 1".
I closed it.
Then, drag and drop'ed folder into VS Code, and saved this new workspace, as "WSPACE 2".
Closed VS Code.
Start VS Code..... and I'm getting my WSPACE 2 opened, with ..... those 8 Untitled files from WSPACE 1.
Console log error:
INFO  no standard startup: not just one window   /C:/Program Files/VS Code Insiders/resources/app/out/vs/workbench/workbench.main.js:1375
Any thoughts?


Add "help wanted" instructions to site

Content
I would like the instructions on "how to open source" to include information on how to use the Code.gov "help wanted" labels so that GH issues can be displayed on the Code.gov site. Instructions for using these labels can be found on the "code-gov" repo.
Page(s) Affected
https://www.code.mil/how-to-open-source.html
But maybe also https://www.code.mil/frequently-asked-questions.html ?

I'd like to help here. I'd also like to mention that the site shows some closed issues under "Open Tasks."

Sounds great! I'm thinking that we may need a separate page for this. We have a "how to open source" which is more about the path to open sourcing a project. I foresee this (and other content) on a page about how to maintain an OSS project. Thoughts?

@jordangov That's what I thought the intent was. Not so much "how to open sources" as "How to contribute" -- like for Hacktoberfest (starting in a few days) participants. Basic instructions on forking, requirements, etc. -- am I correct?
Should we, along with this issue, open an issue to tag appropriate issues with "Hacktoberfest" as others do?

Sounds good. on the tagging, I don't think we'll be adding the Hacktoberfest labels. That would imply support of the event by the Federal Government, which I'm not ready to do. :)

I would be glad to just on this one and help out 😎 👍

Thanks @petercr! PR review is always welcome, and once we have a first pass, additions are always good.

Working on this and #240 today.

I am including screenshots. Should they be stored in /assets/images?

Hello,
Is this still an open issue?


Lerna - add non-core elements to version.

In initial idea, pulsetile-core package includes only Core part of project (without non-core plugins, with default styles etc.). All non-core plugins should be located separately and be added to Core in versions, where they should be presented.
But our plugins aren't self-sufficient components. We can unite all plugin files to separate directory but we can't build it as package.
For example, lets look at Vaccinations. It consists of five files: pages (list, create, edit, show) and action. Lets look at List:
import React from "react";
import { Route } from "react-router";
import { DateField, TextField } from "react-admin";

import ListTemplate from "../../../core/common/ResourseTemplates/ListTemplate";
...

It include component ListTemplate, which is presented in Core and can't be available inside Vaccination-plugin.
@fzaninotto
Francois, I see two ways, how to do this. But each of them has disadvantages. Could you please advice me, which method should be used.

First way: each package is self-sufficient, and includes all required plugins.
|---packages/
|------pulsetile-core/
|------pulsetile-helm/
|------pulsetile-scotland/
|------pulsetile-showcase/

Disadvantage: if we'll do some changes in core or in some plugins - we should copy this change to each package.

Second way:

separate our code at self-sufficient components. I mean the components, which are independent on other custom components, like this: https://github.com/PulseTile/PulseTile-RA/blob/master/src/core/common/Buttons/CancelButton.js
create sub-package for each of them.
create sub-packages for custom components, which depends on other custom components, like this one: https://github.com/PulseTile/PulseTile-RA/blob/master/src/core/common/ResourseTemplates/ListTemplate.js
create non-core plugin from this sub-packages

Advantage: we will have only ONE example for each plugin.
Disadvantage: it isn't difficult, but it'll spend more time.
Francois, could you please tell me, which variant is better?
Or probably you know more optimal way?

Third way: create only one package and store eveything in it, including plugins.
There must be something I don't understand about your publishing strategy, because I don't see any advantage in releasing the code split across several packages, whether for the development team (you) or the integrators.

@fzaninotto
OK, but different version will have different plugins lists.
It will be necessary to hide all plugins, which shouldn't be in current version.
Can we solve this by the way:

Create one package with all possible plugins, pages and features;
Create something like config file in version, like:

/// versions/helm/config.js
export const visiblePlugins = [
     "feeds",
     "vaccinations",
     "topThreeThings"
]

and
// versions/helm/App.js
<Core visiblePlugins={visiblePlugins} />

and hide all plugins, which are absent in config.js.
Can we use this way to hide plugins, features and pages, which aren't used in the current version?

I realize I don't know what a version is. I though, from the other discussion, that versions were to be removed? Now you tell me they are here to stay, I'm confused.

need to cross reference this issue
https://github.com/PulseTile/PulseTile-RA/issues/49


Error in viewer app

Not sure how I did this, but I was going between L2A-1C:
Traceback (most recent call last):
  File "/home/user/.local/lib/python3.11/site-packages/reacton/ipyvue.py", line 23, in handler
    callback_ref.current(*args)
  File "/home/user/.local/lib/python3.11/site-packages/solara/components/button.py", line 84, in <lambda>
    ipyvue.use_event(btn, click_event, lambda *_ignore: on_click and on_click())
                                                                     ^^^^^^^^^^
  File "/app.py", line 54, in update_image
    ret = map_to_image(m, return_centre=True, return_gridcell=True, l2a=(s2_level.value=='L2A'))
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/helpers/functional.py", line 72, in map_to_image
    bbox = map.get_bbox()
           ^^^^^^^^^^^^^^
  File "/home/user/.local/lib/python3.11/site-packages/leafmap/leafmap.py", line 4324, in get_bbox
    bbox = [bounds[0][1], bounds[0][0], bounds[1][1], bounds[1][0]]
            ~~~~~~^^^
IndexError: tuple index out of range

We've spotted this recently - usually happens after multiple clicks in a row.
Should be simple to fix, so hopefully we can update that soon!
Thanks for bringing this up!

@robmarkcole - it should work now! (the app view will reset if too many multiple find sample are called at the same time)


Created analyzer for the situation

I don't know how to handle the code fix? What should be done when this happens? I did not get it from the test cases
Plus, even though the logic seems fine looking at the gather visitor, I am unable to test the analyzer for some reason...

Code fix provider to come. I'm going to start working on this today !

@mkrueger

Could you help me out a bit with some advice on how to deal with the situation. Code fix almost done (in my opinion) @mkrueger

What's your take on this ? @mkrueger
How can  transform the ArgumentSyntax into an ExpressionSyntax ?

@christophwille you too, I'd like your opinion on this if it's possible ! :-)

Can be merged ! @mkrueger

Will remove test code from the analyzer class and push updated file later on today.

Now it can be integrated in the solution @mkrueger  !


Allow arrows keys for textarea element.

I wasn't sure about #82 but problems seems similar.

@oleg-cnnr thank you :)


predicting peak memory of a large run

Hi Ivan!
I am trying to polish a 6.2 Gbp assembly using racon 1.3.1. I would like to feed it 301 Gb of Fastq long reads (PromethION) and a 15 Gb PAF file (without CIGAR).
I tried this with 32 cores and 200G memory, but it crashed due to memory capping out after about two days.
I can request more memory, but I would like to get it right. Could you advise on how much memory usage and wall-clock time you'd expect this to take and how many cores I should use?
Many thanks and I hope you are staying safe.
Peter

Hi Peter,
the memory is bound by the cumulative size of all three files needed as input plus some epsilon. For your case, I would say that 500Gb of RAM should be more than enough. Regarding the execution time, not sure how long it will take :/
Best regards,
Robert
P.S. I would advise you to upgrade to the lastest Racon version (1.4.12) at https://github.com/lbcb-sci/racon.


DSA 1.2 Created Readme.md for Analysis of Algorithms

Description 📜
I've created a README.md file for Analysis of Algorithms.
Fixes #494

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] DSA

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Hey @pjdurden, @Subhradeep10, please review my PR and let me know if any change is required.

@HassanRahim26 I did'nt assign you this task.. It has already been merged

@HassanRahim26 I did'nt assign you this task.. It has already been merged
Then what is this ↓

@HassanRahim26 Ohh am really sorry.. I just forget about this..
I thought of some other issue..Am really apologizing for my mistake

@HassanRahim26 Ohh am really sorry.. I just forget about this..
I thought of some other issue..Am really apologizing for my mistake

That's okay @Subhradeep10, no need to apologise. There is no PR related to this issue and it's still open. Would you mind merging my PR

@HassanRahim26 Just a min..It's shows problem with the rendering

@HassanRahim26 Yups perfect..Just mention the reference of the images..that's it

@HassanRahim26 Yups perfect..Just mention the reference of the images..that's it

So do I need to make some changes?

@HassanRahim26 Yes..Add the reference of the images

Hey @Subhradeep10, I've added reference to those images from where I've used it. The rest images which you'll see of math equations, those are created by me using an online math tool.
So, please review my PR

Hey @pjdurden, Can you please merge my PR, if it's good to go.


Complete LExSIS transpilation

Currently it only works with rps.l4, am in the process of completing it for r34.l4
Will be logging progress here, along with any issues that pop up.

The current LExSIS transpilation process takes class definitions as defined in l4, and transforms them into the necessary data elements as specified by the LExSIS specification.
The current version of r34.l4 existing in the baby-l4/l4 folder is encoded in a way that does not translate into the expected LExSIS output. The main issue is that relationships between classes is not properly defined. There is also the fact that there are attributes that have s(CASP) encodings that contain clingo variables not encoded within the l4 file (see "detracts from legal profession" within the LExSIS file), and that some encodings of child elements are unary, while some are binary, without any indication as to which should be which.
I'm currently trying to rewrite the class definitions in a way that make sense, but find myself wanting a graph-like structure that would clearly delineate relationships between classes.
To tackle the unary/binary encoding issue, a naive idea that class attributes can have an un_ or bi_ prepended would help with determining the arity of the associated s(CASP) encodings. This feels like a band-aid measure, but perhaps it'll hold as a stopgap for now until a better solution can be decided on.

At this point i've further refined the class definitions for r34.l4 and added some lines regarding declarations in preparation for support of output enum lexsis types.
The output for the cardinality/arity headers has also been updated slightly (thank you nlg-team for the arity tip),Boolean type blocks no longer output a cardinality header, while current behavior for String type blocks has been retained.
"type" header output has also been fixed, and no longer outputs "type: string" for all blocks. At this point we have support for "string" and "boolean", and further support for the other types will progressively be added.
The current source header behavior is slightly different from that of the r34 yml file in smucclaw/docassemble-l4. The r34 yml file replicates the "position" data element entirely, twice, within the file. However, the l4 transpilation generates the "position" datablock as a root block of its own, and any blocks that require "position" data would refer to it with the "source: position" header-value pair. I'm not sure if this behavior functions properly within the lexsis -> docassemble process, some testing is needed.


Intelligent Document Service doc and Receipt Processing doc

Intelligent Document Service (IDS)
Invoice Processing (IP)
Receipt Processing (RP)

The release date for these app services is set to be November 30, 2021.

This PR contains the docs for the three app services, originally from #3621

The Invoice Processing app service will be released later than the Intelligent Document Service and the Receipt Processing app services.
Therefore, I made a new PR for the Invoice Processing doc. From now on, all the work for this doc should be done in this new PR: PR4025.