Docker

Problem description

Problem location

I saw a problem on the following URL:

I couldn't find the information I wanted. I expected to find it near the following URL:

Other:

Project version(s) affected

Suggestions for a fix

Closed for lack of response


Meta_named_parameters issue

Hi,
I tried the simple CNN network provided in this repo, however, model.meta_named_parameters() gives only the parameters of MetaBatchNorm2d() and fully ignore MetaConv2d() and MetaLinear(). I checked model.named_parameters() and it is able to output all the parameters of the model.
My torchmeta version is 1.8.0 and pytorch version is 1.8.1.
Could you please give me a hand about this? Thanks

Sorry, I figure out the reason, since I defined these metaconv2d and metalinear by myself in some places and I accidently call these functions as well, so these my own functions mess with yours of the same name.


feat(examples): Add a simple FlashAttention Implementation.

Draft. Don't review

I want to merge this part of the code first. Although it hasn't undergone rigorous correctness verification, it's already quite substantial. I will add test code in the next PR.


use canonical link as path, if available

The GoatCounter docs note that if a canonical link is provided, then that will be used instead of building the path.
<link rel="canonical" href="https://example.com/path">

This package ignored the canonical link and always sends the querystring and hash. I've added a case to fetch it, if available.

This change introduces some potentially odd behavior. On a page with anchor tags that users jump between, we'll send a lot of duplicate pageviews, inflating the count. The way to mitigate this is to compare location and prevLocation in onRouteUpdate and bail if they're the same. I'm happy to add this too, but figured I'd ask first. That behavior should probably be controlled by a setting.

Hey David, just now saw the PR.
I don't use Gatsby nor Goatcounter anymore, as I switched to Remix and this repo could actually be archived as I merged the content with CanRau/CanRau.com.
Would you be interested in taking ownership of the gatsby-plugin-goatcounter package?
If not you might be better of just forking it and maintaining your own version.
Let me know what works best for you

Ah, no worries!
I think I'll start fresh with the package, since my use case is decidedly a simple one. I may reach out to you in the future to take over the npm package though, if you're willing.

Sure just let me know 🤝


Data loading error when & character is present in sq-text

Hi,
when there is an xml file where there is sqlLog node and in a sql node there is '&' character, on loading errors page, it gives me "loading error" and does not load anything.
for example if you add a file with this node:

I am having a similar issue when there was an exception uploading a file. I downloaded the source code and put a breakpoint to find out the api was trying to parse a binary character and therefore throwing an exception and swallowing it, returning no items to the page.
Maybe there's a way to create a filter to ignore the request body when you are uploading files.

@Luca7993  did you provide a sample? I can't see anything after node:  in your comment.?


[SPARK-35735][SQL][FOLLOWUP] Fix case minute to second regex can cover by hour to minute

What changes were proposed in this pull request?
When cast 10:10 to interval minute to second,  it can be catch by hour to minute regex, here to fix this.
Why are the changes needed?
Fix bug
Does this PR introduce any user-facing change?
No
How was this patch tested?
Added UT

Test build #140733 has started for PR 33242 at commit 5982d35.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45243/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45243/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45243/

Test build #140746 has started for PR 33242 at commit 12e83e6.

Test build #140733 has finished for PR 33242 at commit 5982d35.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45257/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45257/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140733/

Test build #140746 has finished for PR 33242 at commit 12e83e6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140746/


[C++][Dataset][Parquet] Support parquet modular encryption in the new Dataset API

In order for the new Dataset API to fully support PME, the same writer properties that include file_encryption_properties shouldn’t be used for the whole dataset. file_encryption_properties should be per file, for example in order to support key rotation ARROW-9960 .
Design document: https://docs.google.com/document/d/13EysCNC6-Nu9wnJ8YpdzmD-aMLn4i2KXUJTNqIihy7A/edit#
Reporter: Maya Anderson / @andersonm-ibm
Related issues:

https://github.com/apache/arrow/issues/25986 (Dependency)
https://github.com/apache/arrow/issues/32564 (supercedes)
https://github.com/apache/arrow/issues/31410 (is depended upon by)

PRs and other links:

Design document

Note: This issue was originally created as ARROW-13593. Please see the migration documentation for further details.

@tolleybot if you could answer here on this comment, I can assign the issue to you (some strange limitation of github that this is required .. ;))


Default form (getGlobalDocument) is confusing when editing content

Opening the sidebar to edit on a page (like /about) opens the getGlobalDocument form. It's not immediately obvious what this form is for.
There are a few changes that might help:

Default to the getPagesDocument form, as content edits are more frequent than global edits
Label each form with a user friendly name
Provide help context within each form about their purpose

TODO: check that formifyCallback is firing

I think we need a better API for this https://github.com/tinacms/tina-cloud-starter/pull/128

If this can't be solved quickly, Is there a work-around that we can use just for the starter site? Perhaps we could move header/footer/theme editing to global plugins and just leave getPagesDocument?
Tagging @spbyrne

@scottgallant - @dwalkr implemented a simpler API for this here. That's merged so we can add it tomorrow.

Should be fixed by https://github.com/tinacms/tinacms/pull/1985/files I guess?


⚠ Bofrost.lu has degraded performance

In bcf90a9, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1374 ms

Resolved: Bofrost.lu performance has improved in 9520b6b after 6 minutes.


Move features inside core modules root to /features folder

According to modules guide .ts files that are now in the root of the modules should be in a features folder.
So for example for a core/api/cart module we have files like addToCart.ts etc in a root of the module. They should be moved to the core/api/module_name/features folder to not confuse other ppl working on a modules.
The task involves

[ ] moving modules features from all modules to core/api/module_name/features folder
[ ] correcting all the pathes pointing to the old location of this features

@filrak what's the preferred way to add custom / new modules on the extension / theme layer or via npm module? I think we should have a way for doing so as a third option for having vue storefront extendable

Currently it's just importing appropiate features since we have only them in the modules. I want to stick with it as long as we don't have most of the features separated to be backward compatible (from the developer PoV nothing changes). Once we have the main modules we will change the way we are currently registering it's parts and move it to one place


Revert "Revert "Merge pull request #40595 from hamishknight/straw-bales""

Reverts apple/swift#40623

@swift-ci please test and merge

@swift-ci please test

With workaround 7bff9da, CI should pass even if for some reason the repo is not checked out or is empty.

@swift-ci please test


(at least) enum identifiers not being enforced by unixcase / snake case rule

Describe the bug
(at least) enum identifiers accepting upper case characters
Erroneous code
enum	e_resultCodes	{
C3D_OK
};
➜  include git:(master) ✗ norminettev2 c3d_error.h
Norme: ./c3d_error.h
Error (line 37, col 0): e_resultCodes not unixcase
➜  include git:(master) ✗ norminette c3d_error.h
c3d_error.h: OK!
Additional infos

OS: Ubuntu 20.04 (Focal Fossa)
python --version: Python 3.9.0
norminette -v: norminette 3.2.5

Hello,
This is expected for now. Librairies such as mlx contains identifiers which do not respect the norm, so i've disabled the check on this.


Quickstart of image signing and enable verification

Change Log

Added guide to sign an image with cosign.
Added guide to configure policy.json to enable signature verification to specific image repository.
Added guide to add cosign verification key and policy to Offline-Fs-KBC's resources.

Hi @sameo @fitzthum @stevenhorsman could you give some suggestions about this? thanks!

I think we have some work to do (maybe covered in confidential-containers/community#63) to help enable users to modify their guest images if required (such as when using offline_fs_kbc to test out features like signatures, encrypted images without remote attestation/on non-CC hardware) and some of this information will be great for this, but I'm not sure we are ready for it yet.

Thanks for you reply Steve! I've checked the link and I'm quite not sure about that. Are you referring that if we add new signatures, it is hard for a user to produce a new guest image which contains the signature?
If so, cosign does not need the image to be modified, because its signatures are stored in the registry where the image lies.

I need to go through this more closely and set-up the cosign, but at a high-leve I'm wondering if the quickstart.md isn't the correct place for the docs at the moment (maybe somewhere in image-rs, or a separate doc page?).

Yes I agree with that. I also found that this doc is too long for me to start when editting this.

Thanks for you reply @stevenhorsman ! I've checked the link and I'm quite not sure about that. Are you referring that if we add new signatures, it is hard for a user to produce a new guest image which contains the signature?

Yes - exactly this point that we don't have a good method for updating the guest image, which the link talks about adding for the sample (option 4), which we could re-use to modify the file. The good news is that with the extra kernel_params exposed in CoCo 0.2 this is becoming a lot easier and the agent-config.toml isn't required now.

If so, cosign does not need the image to be modified, because its signatures are stored in the registry where the image lies.

So my understanding (which might be wrong) is that with cosign you still need to provide the policy and cosign key via the get_resources endpoint. For remote attestation I think we now don't need to modify the image for this, but the doc made references to offline_fs_kbc, which means we need to modify the guest image to add the aa-offline_fs_kbc-resources.json in. I hope that helps clarify?

Thank you for writing all of this out, I have found it incredibly helpful!
I have been consulting it enough that I figured I should leave some fixes for typos and such.

So my understanding (which might be wrong) is that with cosign you still need to provide the policy and cosign key via the get_resources endpoint. For remote attestation I think we now don't need to modify the image for this, but the doc made references to offline_fs_kbc, which means we need to modify the guest image to add the aa-offline_fs_kbc-resources.json in. I hope that helps clarify?

For this disadvantage, I think there may be still a way to avoid modify guest image frequently.

Use verdictd-eaa instead of offline-fs-kbc until we finally turn to generic KBS&CC-KBC.
Use cosign instead of simple signing

cc @arronwy

I've put a pr in image-rs for this. https://github.com/confidential-containers/image-rs/pull/87
When it passes, I will change this pr to a single link


Other ways to split chunks for federated modules for application code?

As of today, I know of two ways to split federated chunks:

Using shared settings (only for packages/libraries)
Using a dynamic import with next/dynamic

Is there any other way to split federated chunks for application code? I noticed that splitChunks is explicitly deleted on the childCompiler, so that isn't an option. I also don't know of a way to leverage shared settings for application code and not packages/libraries.

chunk splitting is tricky in federation becuase it messes with the plugins own use of chunk splitting. So i generally turn it off to prevent users from breaking their own builds.
It is possible to enable it, but we would need any custom split rules to use enforce: true in order to override federation chunk split rules.
theres a git issue about chunk splitting on federation examples repo.
Im happy to enable it again if you have a PR that doesnt break functionality of the MFP. usually id delete nexts chunk splitting defaults so i could just remove the default keys and pass any user configured rules through

Thanks for the response. I was able to find the git issue you mentioned in the federation examples repo.
After altering the Next.js MF plugin to accept values from splitChunks and removing the next defaults, I was able to get a chunk split. However, my split chunk is not being used by my federated chunks.
This is the optimization.splitChunks object I'm passing to the childCompiler in the Next.js MF plugin:
{
  cacheGroups: {
    testGroup1: {
      test: [Function: test],
      chunks: 'all',
      reuseExistingChunk: false,
      enforce: true
    }
  },
  defaultSizeTypes: [ 'javascript', 'unknown', 'css/mini-extract' ],
  hidePathInfo: true,
  chunks: 'async',
  usedExports: true,
  minChunks: 1,
  minSize: 0,
  minRemainingSize: undefined,
  enforceSizeThreshold: 0,
  maxAsyncRequests: 30,
  maxInitialRequests: 30,
  automaticNameDelimiter: '-'
}

I also changed other fields like minSize since my test component is too small. Is there something obviously missing from the configuration above for optimization.splitChunks? I can create a shareable reproduction if the information above isn't enough.
When you say PR, I'm assuming you are talking about a PR that reintroduces the ability to pass splitChunks while handling next defaults and making sure MFP doesn't break? Is it possible to see the git history for this? I wasn't able to find an old repo with the git history before the NX move.

Hi @ScriptedAlchemy just wanted to know if you could provide some feedback to the above or point me to the right folks.

You have to use SplitChunksPlugin - child compiler dont do much on their own.

The SplitChunksPlugin options I shared above are what I set in the main webpack configuration. In addition to that, I removed this line and removed the Next.js defaults.
The child compiler is not splitting anything at all. It completely ignores what I passed in. The main compiler respects the configuration I passed in for SplitChunksPlugin.
A repro might be helpful, so please let me know if a minimum viable repro is useful here.

new SplitChunksPlugin(options).apply(childCompiler)
Child compilers are bare.

Sorry for the delay @ScriptedAlchemy. I did a test by applying the SplitChunksPlugin to the childCompiler, and the chunk splitting works for me.
I'm happy to submit a PR to allow us to pass in options for SplitChunksPlugin. I see two approaches:

Users define their options normally, and the Next.js MF plugin carefully remove the Next.js default options before applying SplitChunksPlugin.
Have users define their splitchunks options somewhere else within the options for the Next.js MF plugin and apply them with SplitChunksPlugin.

Based on the history of this thread, it seems like we prefer option #1.
Most likely want to include documentation on this as well.


Script base path does not exist or is not a directory when running the example locally.

Hello, I'm having some trouble running the example fragfold job.
I installed localcolabfold (and tested it), then installed FragFold, no errors there either.
I'm trying to run the example job locally just to test that everything works, however I am not able to do so.
I edited the "General Parameters" as described under Setting system-specific variables. Then I replaced all labels for each process with standard in FragFold/nextflow/modules.nf. I then set NEXTFLOWDIR and WORKDIR.
It's not very clear where to get the ftsZ_homomeric_example.nf file in order to start the job. In my testing I just pointed this to a dummy file to pass the initial check.
When looking at the log however, I get:
DEBUG nextflow.Session - Script base path does not exist or is not a directory: /home/ubuntu/FragFold/nextflow/bin
Where /home/ubuntu/FragFold/nextflow is $NEXTFLOWDIR (I tried changing it)
Any ideas of what I'm doing wrong?

Hi Alessandro!
My apologies, I updated the code recently, but forgot to fix this section in the README. The major change in the repo is that I made a general nextflow script for all fragfold jobs and use the yaml files in params/ to define the job-specific details. Make sure to pull the newest version of the repo before trying this. If it doesn't run, let me know and I can look into it further.
To get this to run, you will need to set WORKDIR and also edit two lines in the yaml file (protein_query_seq and experimental_data are absolute paths to those files on your system, both files are in the repo)
NEXTFLOWDIR=/home/ubuntu/FragFold/nextflow
WORKDIR=? #directory where results will be stored
NF_CFG=${NEXTFLOWDIR}/nextflow.config
PARAMS=${NEXTFLOWDIR}/params/ftsZ_monomeric_example.yaml
nextflow run ${NEXTFLOWDIR}/main.nf -w $WORK_DIR -c $NF_CFG -params-file $PARAMS -resume

Recently I've been running these as batch scripts, this example may be helpful for you: https://github.com/swanss/FragFold/blob/main/scripts/submit/submit_nextflow.sh

First of all, thank you for the prompt response! I know that this response is a lot, but I think I found a couple more problems while running the default example:
Now after following the instructions I get:
Caused by:
  Process `process_msa` terminated with an error exit status (1)

Command executed:

  python /home/ubuntu/FragFold/fragfold/create_fragment_msa.py         --fragment_a3m_input ftsZ.a3m         --fragment_ntermres_start 260         --fragment_ntermres_final 264          --fragment_length 30         --protein_a3m_input /home/ubuntu/FragFold/-c/89/7e336efad89f96ab168983e7662c83/mmseqs2_a3m/ftsZ.a3m         --protein_ntermres 10         --protein_ctermres 316         --protein_copies 1

Command exit status:
  1

Command output:
  (empty)

Command error:
  Traceback (most recent call last):
    File "/home/ubuntu/FragFold/fragfold/create_fragment_msa.py", line 7, in <module>
      from fragfold.src.colabfold_create_msa import createIndividualMSAsFullLengthFragment,createIndividualMSAsFullLengthFragmentHeteromeric
  ModuleNotFoundError: No module named 'fragfold.src'

And if I activate the fragfold4 environment (the one specified in my nextflow.config) and type
from fragfold.src.colabfold_create_msa import createIndividualMSAsFullLengthFragment,createIndividualMSAsFullLengthFragmentHeteromeric

in the python console, it only works if I'm in the fragfold directory (meaning that it's just using the local python path).
I also noticed that the default installation script doesn't work on a default ubuntu-bash setup. The correct script should be:
#!/bin/bash

source $(conda info --base)/etc/profile.d/conda.sh

conda create -n fragfold4 -c bioconda python==3.9 nextflow -y && \
    conda activate fragfold4 && \
    pip install . && \
    echo "Installation complete"

I can make a PR with this if you would like. (bash doesn't like && on a newline by itself, and bash doesn't necessarily load the conda profile on new spawned shells).
I don't have too much experience with pyproject.toml, so I don't really know what leads to this. I do see the line that says include = ["fragfold","src"] in the pyproject, however in the full pip install . output, there isn't one mention of the string src. (I can provide the full output if you would like)

Please go ahead and provide the full output from your pip install. I'll attempt a fresh reinstall tonight and see if I replicate the error. Again, sorry about the bugs, and thanks a bunch for trying it out and providing detailed feedback!

No problem, I'm very eager to provide any kind of help to the project and can spin up fresh environments very easily.
Here is the full output:
// NOTE: Above here is the first step of the install script, where it's just creating the conda env.
// The line the says: Processing /home/ubuntu/FragFold is the beginning of the pip install output

.
.
.
# To activate this environment, use
#
#     $ conda activate fragfold4
#
# To deactivate an active environment, use
#
#     $ conda deactivate

Processing /home/ubuntu/FragFold
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting biopython (from fragfold==0.0.1)
  Using cached biopython-1.83-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (13 kB)
Collecting jupyter (from fragfold==0.0.1)
  Using cached jupyter-1.0.0-py2.py3-none-any.whl.metadata (995 bytes)
Collecting numpy (from fragfold==0.0.1)
  Downloading numpy-2.0.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (60 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 60.9/60.9 kB 5.2 MB/s eta 0:00:00
Collecting pandas (from fragfold==0.0.1)
  Downloading pandas-2.2.2-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (19 kB)
Collecting scipy (from fragfold==0.0.1)
  Using cached scipy-1.13.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (60 kB)
Collecting seaborn (from fragfold==0.0.1)
  Using cached seaborn-0.13.2-py3-none-any.whl.metadata (5.4 kB)
Collecting notebook (from jupyter->fragfold==0.0.1)
  Using cached notebook-7.2.1-py3-none-any.whl.metadata (10 kB)
Collecting qtconsole (from jupyter->fragfold==0.0.1)
  Using cached qtconsole-5.5.2-py3-none-any.whl.metadata (5.1 kB)
Collecting jupyter-console (from jupyter->fragfold==0.0.1)
  Using cached jupyter_console-6.6.3-py3-none-any.whl.metadata (5.8 kB)
Collecting nbconvert (from jupyter->fragfold==0.0.1)
  Using cached nbconvert-7.16.4-py3-none-any.whl.metadata (8.5 kB)
Collecting ipykernel (from jupyter->fragfold==0.0.1)
  Using cached ipykernel-6.29.4-py3-none-any.whl.metadata (6.3 kB)
Collecting ipywidgets (from jupyter->fragfold==0.0.1)
  Using cached ipywidgets-8.1.3-py3-none-any.whl.metadata (2.4 kB)
Collecting python-dateutil>=2.8.2 (from pandas->fragfold==0.0.1)
  Using cached python_dateutil-2.9.0.post0-py2.py3-none-any.whl.metadata (8.4 kB)
Collecting pytz>=2020.1 (from pandas->fragfold==0.0.1)
  Using cached pytz-2024.1-py2.py3-none-any.whl.metadata (22 kB)
Collecting tzdata>=2022.7 (from pandas->fragfold==0.0.1)
  Downloading tzdata-2024.1-py2.py3-none-any.whl.metadata (1.4 kB)
Collecting matplotlib!=3.6.1,>=3.4 (from seaborn->fragfold==0.0.1)
  Using cached matplotlib-3.9.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (11 kB)
Collecting contourpy>=1.0.1 (from matplotlib!=3.6.1,>=3.4->seaborn->fragfold==0.0.1)
  Using cached contourpy-1.2.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (5.8 kB)
Collecting cycler>=0.10 (from matplotlib!=3.6.1,>=3.4->seaborn->fragfold==0.0.1)
  Using cached cycler-0.12.1-py3-none-any.whl.metadata (3.8 kB)
Collecting fonttools>=4.22.0 (from matplotlib!=3.6.1,>=3.4->seaborn->fragfold==0.0.1)
  Using cached fonttools-4.53.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (162 kB)
Collecting kiwisolver>=1.3.1 (from matplotlib!=3.6.1,>=3.4->seaborn->fragfold==0.0.1)
  Using cached kiwisolver-1.4.5-cp39-cp39-manylinux_2_12_x86_64.manylinux2010_x86_64.whl.metadata (6.4 kB)
Collecting packaging>=20.0 (from matplotlib!=3.6.1,>=3.4->seaborn->fragfold==0.0.1)
  Using cached packaging-24.1-py3-none-any.whl.metadata (3.2 kB)
Collecting pillow>=8 (from matplotlib!=3.6.1,>=3.4->seaborn->fragfold==0.0.1)
  Using cached pillow-10.3.0-cp39-cp39-manylinux_2_28_x86_64.whl.metadata (9.2 kB)
Collecting pyparsing>=2.3.1 (from matplotlib!=3.6.1,>=3.4->seaborn->fragfold==0.0.1)
  Using cached pyparsing-3.1.2-py3-none-any.whl.metadata (5.1 kB)
Collecting importlib-resources>=3.2.0 (from matplotlib!=3.6.1,>=3.4->seaborn->fragfold==0.0.1)
  Using cached importlib_resources-6.4.0-py3-none-any.whl.metadata (3.9 kB)
Collecting six>=1.5 (from python-dateutil>=2.8.2->pandas->fragfold==0.0.1)
  Using cached six-1.16.0-py2.py3-none-any.whl.metadata (1.8 kB)
Collecting comm>=0.1.1 (from ipykernel->jupyter->fragfold==0.0.1)
  Using cached comm-0.2.2-py3-none-any.whl.metadata (3.7 kB)
Collecting debugpy>=1.6.5 (from ipykernel->jupyter->fragfold==0.0.1)
  Using cached debugpy-1.8.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (1.1 kB)
Collecting ipython>=7.23.1 (from ipykernel->jupyter->fragfold==0.0.1)
  Using cached ipython-8.18.1-py3-none-any.whl.metadata (6.0 kB)
Collecting jupyter-client>=6.1.12 (from ipykernel->jupyter->fragfold==0.0.1)
  Using cached jupyter_client-8.6.2-py3-none-any.whl.metadata (8.3 kB)
Collecting jupyter-core!=5.0.*,>=4.12 (from ipykernel->jupyter->fragfold==0.0.1)
  Using cached jupyter_core-5.7.2-py3-none-any.whl.metadata (3.4 kB)
Collecting matplotlib-inline>=0.1 (from ipykernel->jupyter->fragfold==0.0.1)
  Using cached matplotlib_inline-0.1.7-py3-none-any.whl.metadata (3.9 kB)
Collecting nest-asyncio (from ipykernel->jupyter->fragfold==0.0.1)
  Using cached nest_asyncio-1.6.0-py3-none-any.whl.metadata (2.8 kB)
Collecting psutil (from ipykernel->jupyter->fragfold==0.0.1)
  Using cached psutil-6.0.0-cp36-abi3-manylinux_2_12_x86_64.manylinux2010_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (21 kB)
Collecting pyzmq>=24 (from ipykernel->jupyter->fragfold==0.0.1)
  Using cached pyzmq-26.0.3-cp39-cp39-manylinux_2_12_x86_64.manylinux2010_x86_64.whl.metadata (6.1 kB)
Collecting tornado>=6.1 (from ipykernel->jupyter->fragfold==0.0.1)
  Using cached tornado-6.4.1-cp38-abi3-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (2.5 kB)
Collecting traitlets>=5.4.0 (from ipykernel->jupyter->fragfold==0.0.1)
  Using cached traitlets-5.14.3-py3-none-any.whl.metadata (10 kB)
Collecting widgetsnbextension~=4.0.11 (from ipywidgets->jupyter->fragfold==0.0.1)
  Using cached widgetsnbextension-4.0.11-py3-none-any.whl.metadata (1.6 kB)
Collecting jupyterlab-widgets~=3.0.11 (from ipywidgets->jupyter->fragfold==0.0.1)
  Using cached jupyterlab_widgets-3.0.11-py3-none-any.whl.metadata (4.1 kB)
Collecting prompt-toolkit>=3.0.30 (from jupyter-console->jupyter->fragfold==0.0.1)
  Using cached prompt_toolkit-3.0.47-py3-none-any.whl.metadata (6.4 kB)
Collecting pygments (from jupyter-console->jupyter->fragfold==0.0.1)
  Using cached pygments-2.18.0-py3-none-any.whl.metadata (2.5 kB)
Collecting beautifulsoup4 (from nbconvert->jupyter->fragfold==0.0.1)
  Using cached beautifulsoup4-4.12.3-py3-none-any.whl.metadata (3.8 kB)
Collecting bleach!=5.0.0 (from nbconvert->jupyter->fragfold==0.0.1)
  Using cached bleach-6.1.0-py3-none-any.whl.metadata (30 kB)
Collecting defusedxml (from nbconvert->jupyter->fragfold==0.0.1)
  Using cached defusedxml-0.7.1-py2.py3-none-any.whl.metadata (32 kB)
Collecting importlib-metadata>=3.6 (from nbconvert->jupyter->fragfold==0.0.1)
  Using cached importlib_metadata-7.2.1-py3-none-any.whl.metadata (4.6 kB)
Collecting jinja2>=3.0 (from nbconvert->jupyter->fragfold==0.0.1)
  Using cached jinja2-3.1.4-py3-none-any.whl.metadata (2.6 kB)
Collecting jupyterlab-pygments (from nbconvert->jupyter->fragfold==0.0.1)
  Using cached jupyterlab_pygments-0.3.0-py3-none-any.whl.metadata (4.4 kB)
Collecting markupsafe>=2.0 (from nbconvert->jupyter->fragfold==0.0.1)
  Using cached MarkupSafe-2.1.5-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (3.0 kB)
Collecting mistune<4,>=2.0.3 (from nbconvert->jupyter->fragfold==0.0.1)
  Using cached mistune-3.0.2-py3-none-any.whl.metadata (1.7 kB)
Collecting nbclient>=0.5.0 (from nbconvert->jupyter->fragfold==0.0.1)
  Using cached nbclient-0.10.0-py3-none-any.whl.metadata (7.8 kB)
Collecting nbformat>=5.7 (from nbconvert->jupyter->fragfold==0.0.1)
  Using cached nbformat-5.10.4-py3-none-any.whl.metadata (3.6 kB)
Collecting pandocfilters>=1.4.1 (from nbconvert->jupyter->fragfold==0.0.1)
  Using cached pandocfilters-1.5.1-py2.py3-none-any.whl.metadata (9.0 kB)
Collecting tinycss2 (from nbconvert->jupyter->fragfold==0.0.1)
  Using cached tinycss2-1.3.0-py3-none-any.whl.metadata (3.0 kB)
Collecting jupyter-server<3,>=2.4.0 (from notebook->jupyter->fragfold==0.0.1)
  Using cached jupyter_server-2.14.1-py3-none-any.whl.metadata (8.4 kB)
Collecting jupyterlab-server<3,>=2.27.1 (from notebook->jupyter->fragfold==0.0.1)
  Using cached jupyterlab_server-2.27.2-py3-none-any.whl.metadata (5.9 kB)
Collecting jupyterlab<4.3,>=4.2.0 (from notebook->jupyter->fragfold==0.0.1)
  Using cached jupyterlab-4.2.2-py3-none-any.whl.metadata (16 kB)
Collecting notebook-shim<0.3,>=0.2 (from notebook->jupyter->fragfold==0.0.1)
  Using cached notebook_shim-0.2.4-py3-none-any.whl.metadata (4.0 kB)
Collecting qtpy>=2.4.0 (from qtconsole->jupyter->fragfold==0.0.1)
  Using cached QtPy-2.4.1-py3-none-any.whl.metadata (12 kB)
Collecting webencodings (from bleach!=5.0.0->nbconvert->jupyter->fragfold==0.0.1)
  Using cached webencodings-0.5.1-py2.py3-none-any.whl.metadata (2.1 kB)
Collecting zipp>=0.5 (from importlib-metadata>=3.6->nbconvert->jupyter->fragfold==0.0.1)
  Using cached zipp-3.19.2-py3-none-any.whl.metadata (3.6 kB)
Collecting decorator (from ipython>=7.23.1->ipykernel->jupyter->fragfold==0.0.1)
  Using cached decorator-5.1.1-py3-none-any.whl.metadata (4.0 kB)
Collecting jedi>=0.16 (from ipython>=7.23.1->ipykernel->jupyter->fragfold==0.0.1)
  Using cached jedi-0.19.1-py2.py3-none-any.whl.metadata (22 kB)
Collecting stack-data (from ipython>=7.23.1->ipykernel->jupyter->fragfold==0.0.1)
  Using cached stack_data-0.6.3-py3-none-any.whl.metadata (18 kB)
Collecting typing-extensions (from ipython>=7.23.1->ipykernel->jupyter->fragfold==0.0.1)
  Using cached typing_extensions-4.12.2-py3-none-any.whl.metadata (3.0 kB)
Collecting exceptiongroup (from ipython>=7.23.1->ipykernel->jupyter->fragfold==0.0.1)
  Using cached exceptiongroup-1.2.1-py3-none-any.whl.metadata (6.6 kB)
Collecting pexpect>4.3 (from ipython>=7.23.1->ipykernel->jupyter->fragfold==0.0.1)
  Using cached pexpect-4.9.0-py2.py3-none-any.whl.metadata (2.5 kB)
Collecting platformdirs>=2.5 (from jupyter-core!=5.0.*,>=4.12->ipykernel->jupyter->fragfold==0.0.1)
  Using cached platformdirs-4.2.2-py3-none-any.whl.metadata (11 kB)
Collecting anyio>=3.1.0 (from jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached anyio-4.4.0-py3-none-any.whl.metadata (4.6 kB)
Collecting argon2-cffi>=21.1 (from jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached argon2_cffi-23.1.0-py3-none-any.whl.metadata (5.2 kB)
Collecting jupyter-events>=0.9.0 (from jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached jupyter_events-0.10.0-py3-none-any.whl.metadata (5.9 kB)
Collecting jupyter-server-terminals>=0.4.4 (from jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached jupyter_server_terminals-0.5.3-py3-none-any.whl.metadata (5.6 kB)
Collecting overrides>=5.0 (from jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached overrides-7.7.0-py3-none-any.whl.metadata (5.8 kB)
Collecting prometheus-client>=0.9 (from jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached prometheus_client-0.20.0-py3-none-any.whl.metadata (1.8 kB)
Collecting send2trash>=1.8.2 (from jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached Send2Trash-1.8.3-py3-none-any.whl.metadata (4.0 kB)
Collecting terminado>=0.8.3 (from jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached terminado-0.18.1-py3-none-any.whl.metadata (5.8 kB)
Collecting websocket-client>=1.7 (from jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached websocket_client-1.8.0-py3-none-any.whl.metadata (8.0 kB)
Collecting async-lru>=1.0.0 (from jupyterlab<4.3,>=4.2.0->notebook->jupyter->fragfold==0.0.1)
  Using cached async_lru-2.0.4-py3-none-any.whl.metadata (4.5 kB)
Collecting httpx>=0.25.0 (from jupyterlab<4.3,>=4.2.0->notebook->jupyter->fragfold==0.0.1)
  Using cached httpx-0.27.0-py3-none-any.whl.metadata (7.2 kB)
Collecting jupyter-lsp>=2.0.0 (from jupyterlab<4.3,>=4.2.0->notebook->jupyter->fragfold==0.0.1)
  Using cached jupyter_lsp-2.2.5-py3-none-any.whl.metadata (1.8 kB)
Requirement already satisfied: setuptools>=40.1.0 in /home/ubuntu/anaconda3/envs/fragfold4/lib/python3.9/site-packages (from jupyterlab<4.3,>=4.2.0->notebook->jupyter->fragfold==0.0.1) (69.5.1)
Collecting tomli>=1.2.2 (from jupyterlab<4.3,>=4.2.0->notebook->jupyter->fragfold==0.0.1)
  Using cached tomli-2.0.1-py3-none-any.whl.metadata (8.9 kB)
Collecting babel>=2.10 (from jupyterlab-server<3,>=2.27.1->notebook->jupyter->fragfold==0.0.1)
  Using cached Babel-2.15.0-py3-none-any.whl.metadata (1.5 kB)
Collecting json5>=0.9.0 (from jupyterlab-server<3,>=2.27.1->notebook->jupyter->fragfold==0.0.1)
  Using cached json5-0.9.25-py3-none-any.whl.metadata (30 kB)
Collecting jsonschema>=4.18.0 (from jupyterlab-server<3,>=2.27.1->notebook->jupyter->fragfold==0.0.1)
  Using cached jsonschema-4.22.0-py3-none-any.whl.metadata (8.2 kB)
Collecting requests>=2.31 (from jupyterlab-server<3,>=2.27.1->notebook->jupyter->fragfold==0.0.1)
  Using cached requests-2.32.3-py3-none-any.whl.metadata (4.6 kB)
Collecting fastjsonschema>=2.15 (from nbformat>=5.7->nbconvert->jupyter->fragfold==0.0.1)
  Using cached fastjsonschema-2.20.0-py3-none-any.whl.metadata (2.1 kB)
Collecting wcwidth (from prompt-toolkit>=3.0.30->jupyter-console->jupyter->fragfold==0.0.1)
  Using cached wcwidth-0.2.13-py2.py3-none-any.whl.metadata (14 kB)
Collecting soupsieve>1.2 (from beautifulsoup4->nbconvert->jupyter->fragfold==0.0.1)
  Using cached soupsieve-2.5-py3-none-any.whl.metadata (4.7 kB)
Collecting idna>=2.8 (from anyio>=3.1.0->jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached idna-3.7-py3-none-any.whl.metadata (9.9 kB)
Collecting sniffio>=1.1 (from anyio>=3.1.0->jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached sniffio-1.3.1-py3-none-any.whl.metadata (3.9 kB)
Collecting argon2-cffi-bindings (from argon2-cffi>=21.1->jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached argon2_cffi_bindings-21.2.0-cp36-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (6.7 kB)
Collecting certifi (from httpx>=0.25.0->jupyterlab<4.3,>=4.2.0->notebook->jupyter->fragfold==0.0.1)
  Using cached certifi-2024.6.2-py3-none-any.whl.metadata (2.2 kB)
Collecting httpcore==1.* (from httpx>=0.25.0->jupyterlab<4.3,>=4.2.0->notebook->jupyter->fragfold==0.0.1)
  Using cached httpcore-1.0.5-py3-none-any.whl.metadata (20 kB)
Collecting h11<0.15,>=0.13 (from httpcore==1.*->httpx>=0.25.0->jupyterlab<4.3,>=4.2.0->notebook->jupyter->fragfold==0.0.1)
  Using cached h11-0.14.0-py3-none-any.whl.metadata (8.2 kB)
Collecting parso<0.9.0,>=0.8.3 (from jedi>=0.16->ipython>=7.23.1->ipykernel->jupyter->fragfold==0.0.1)
  Using cached parso-0.8.4-py2.py3-none-any.whl.metadata (7.7 kB)
Collecting attrs>=22.2.0 (from jsonschema>=4.18.0->jupyterlab-server<3,>=2.27.1->notebook->jupyter->fragfold==0.0.1)
  Using cached attrs-23.2.0-py3-none-any.whl.metadata (9.5 kB)
Collecting jsonschema-specifications>=2023.03.6 (from jsonschema>=4.18.0->jupyterlab-server<3,>=2.27.1->notebook->jupyter->fragfold==0.0.1)
  Using cached jsonschema_specifications-2023.12.1-py3-none-any.whl.metadata (3.0 kB)
Collecting referencing>=0.28.4 (from jsonschema>=4.18.0->jupyterlab-server<3,>=2.27.1->notebook->jupyter->fragfold==0.0.1)
  Using cached referencing-0.35.1-py3-none-any.whl.metadata (2.8 kB)
Collecting rpds-py>=0.7.1 (from jsonschema>=4.18.0->jupyterlab-server<3,>=2.27.1->notebook->jupyter->fragfold==0.0.1)
  Using cached rpds_py-0.18.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (4.1 kB)
Collecting python-json-logger>=2.0.4 (from jupyter-events>=0.9.0->jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached python_json_logger-2.0.7-py3-none-any.whl.metadata (6.5 kB)
Collecting pyyaml>=5.3 (from jupyter-events>=0.9.0->jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached PyYAML-6.0.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (2.1 kB)
Collecting rfc3339-validator (from jupyter-events>=0.9.0->jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached rfc3339_validator-0.1.4-py2.py3-none-any.whl.metadata (1.5 kB)
Collecting rfc3986-validator>=0.1.1 (from jupyter-events>=0.9.0->jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached rfc3986_validator-0.1.1-py2.py3-none-any.whl.metadata (1.7 kB)
Collecting ptyprocess>=0.5 (from pexpect>4.3->ipython>=7.23.1->ipykernel->jupyter->fragfold==0.0.1)
  Using cached ptyprocess-0.7.0-py2.py3-none-any.whl.metadata (1.3 kB)
Collecting charset-normalizer<4,>=2 (from requests>=2.31->jupyterlab-server<3,>=2.27.1->notebook->jupyter->fragfold==0.0.1)
  Using cached charset_normalizer-3.3.2-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (33 kB)
Collecting urllib3<3,>=1.21.1 (from requests>=2.31->jupyterlab-server<3,>=2.27.1->notebook->jupyter->fragfold==0.0.1)
  Using cached urllib3-2.2.2-py3-none-any.whl.metadata (6.4 kB)
Collecting executing>=1.2.0 (from stack-data->ipython>=7.23.1->ipykernel->jupyter->fragfold==0.0.1)
  Using cached executing-2.0.1-py2.py3-none-any.whl.metadata (9.0 kB)
Collecting asttokens>=2.1.0 (from stack-data->ipython>=7.23.1->ipykernel->jupyter->fragfold==0.0.1)
  Using cached asttokens-2.4.1-py2.py3-none-any.whl.metadata (5.2 kB)
Collecting pure-eval (from stack-data->ipython>=7.23.1->ipykernel->jupyter->fragfold==0.0.1)
  Using cached pure_eval-0.2.2-py3-none-any.whl.metadata (6.2 kB)
Collecting fqdn (from jsonschema[format-nongpl]>=4.18.0->jupyter-events>=0.9.0->jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached fqdn-1.5.1-py3-none-any.whl.metadata (1.4 kB)
Collecting isoduration (from jsonschema[format-nongpl]>=4.18.0->jupyter-events>=0.9.0->jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached isoduration-20.11.0-py3-none-any.whl.metadata (5.7 kB)
Collecting jsonpointer>1.13 (from jsonschema[format-nongpl]>=4.18.0->jupyter-events>=0.9.0->jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached jsonpointer-3.0.0-py2.py3-none-any.whl.metadata (2.3 kB)
Collecting uri-template (from jsonschema[format-nongpl]>=4.18.0->jupyter-events>=0.9.0->jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached uri_template-1.3.0-py3-none-any.whl.metadata (8.8 kB)
Collecting webcolors>=1.11 (from jsonschema[format-nongpl]>=4.18.0->jupyter-events>=0.9.0->jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached webcolors-24.6.0-py3-none-any.whl.metadata (2.6 kB)
Collecting cffi>=1.0.1 (from argon2-cffi-bindings->argon2-cffi>=21.1->jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached cffi-1.16.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (1.5 kB)
Collecting pycparser (from cffi>=1.0.1->argon2-cffi-bindings->argon2-cffi>=21.1->jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached pycparser-2.22-py3-none-any.whl.metadata (943 bytes)
Collecting arrow>=0.15.0 (from isoduration->jsonschema[format-nongpl]>=4.18.0->jupyter-events>=0.9.0->jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached arrow-1.3.0-py3-none-any.whl.metadata (7.5 kB)
Collecting types-python-dateutil>=2.8.10 (from arrow>=0.15.0->isoduration->jsonschema[format-nongpl]>=4.18.0->jupyter-events>=0.9.0->jupyter-server<3,>=2.4.0->notebook->jupyter->fragfold==0.0.1)
  Using cached types_python_dateutil-<IP_ADDRESS>40316-py3-none-any.whl.metadata (1.8 kB)
Using cached biopython-1.83-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (3.1 MB)
Using cached jupyter-1.0.0-py2.py3-none-any.whl (2.7 kB)
Downloading numpy-2.0.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (19.3 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 19.3/19.3 MB 74.0 MB/s eta 0:00:00
Downloading pandas-2.2.2-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (13.1 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 13.1/13.1 MB 92.7 MB/s eta 0:00:00
Using cached scipy-1.13.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (38.6 MB)
Using cached seaborn-0.13.2-py3-none-any.whl (294 kB)
Using cached matplotlib-3.9.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (8.3 MB)
Using cached python_dateutil-2.9.0.post0-py2.py3-none-any.whl (229 kB)
Using cached pytz-2024.1-py2.py3-none-any.whl (505 kB)
Downloading tzdata-2024.1-py2.py3-none-any.whl (345 kB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 345.4/345.4 kB 24.1 MB/s eta 0:00:00
Using cached ipykernel-6.29.4-py3-none-any.whl (117 kB)
Using cached ipywidgets-8.1.3-py3-none-any.whl (139 kB)
Using cached jupyter_console-6.6.3-py3-none-any.whl (24 kB)
Using cached nbconvert-7.16.4-py3-none-any.whl (257 kB)
Using cached notebook-7.2.1-py3-none-any.whl (5.0 MB)
Using cached qtconsole-5.5.2-py3-none-any.whl (123 kB)
Using cached bleach-6.1.0-py3-none-any.whl (162 kB)
Using cached comm-0.2.2-py3-none-any.whl (7.2 kB)
Using cached contourpy-1.2.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (304 kB)
Using cached cycler-0.12.1-py3-none-any.whl (8.3 kB)
Using cached debugpy-1.8.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (3.1 MB)
Using cached fonttools-4.53.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (4.6 MB)
Using cached importlib_metadata-7.2.1-py3-none-any.whl (25 kB)
Using cached importlib_resources-6.4.0-py3-none-any.whl (38 kB)
Using cached ipython-8.18.1-py3-none-any.whl (808 kB)
Using cached jinja2-3.1.4-py3-none-any.whl (133 kB)
Using cached jupyter_client-8.6.2-py3-none-any.whl (105 kB)
Using cached jupyter_core-5.7.2-py3-none-any.whl (28 kB)
Using cached jupyter_server-2.14.1-py3-none-any.whl (383 kB)
Using cached jupyterlab-4.2.2-py3-none-any.whl (11.6 MB)
Using cached jupyterlab_server-2.27.2-py3-none-any.whl (59 kB)
Using cached jupyterlab_widgets-3.0.11-py3-none-any.whl (214 kB)
Using cached kiwisolver-1.4.5-cp39-cp39-manylinux_2_12_x86_64.manylinux2010_x86_64.whl (1.6 MB)
Using cached MarkupSafe-2.1.5-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (25 kB)
Using cached matplotlib_inline-0.1.7-py3-none-any.whl (9.9 kB)
Using cached mistune-3.0.2-py3-none-any.whl (47 kB)
Using cached nbclient-0.10.0-py3-none-any.whl (25 kB)
Using cached nbformat-5.10.4-py3-none-any.whl (78 kB)
Using cached notebook_shim-0.2.4-py3-none-any.whl (13 kB)
Using cached packaging-24.1-py3-none-any.whl (53 kB)
Using cached pandocfilters-1.5.1-py2.py3-none-any.whl (8.7 kB)
Using cached pillow-10.3.0-cp39-cp39-manylinux_2_28_x86_64.whl (4.5 MB)
Using cached prompt_toolkit-3.0.47-py3-none-any.whl (386 kB)
Using cached pygments-2.18.0-py3-none-any.whl (1.2 MB)
Using cached pyparsing-3.1.2-py3-none-any.whl (103 kB)
Using cached pyzmq-26.0.3-cp39-cp39-manylinux_2_12_x86_64.manylinux2010_x86_64.whl (912 kB)
Using cached QtPy-2.4.1-py3-none-any.whl (93 kB)
Using cached six-1.16.0-py2.py3-none-any.whl (11 kB)
Using cached tornado-6.4.1-cp38-abi3-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (436 kB)
Using cached traitlets-5.14.3-py3-none-any.whl (85 kB)
Using cached widgetsnbextension-4.0.11-py3-none-any.whl (2.3 MB)
Using cached beautifulsoup4-4.12.3-py3-none-any.whl (147 kB)
Using cached defusedxml-0.7.1-py2.py3-none-any.whl (25 kB)
Using cached jupyterlab_pygments-0.3.0-py3-none-any.whl (15 kB)
Using cached nest_asyncio-1.6.0-py3-none-any.whl (5.2 kB)
Using cached psutil-6.0.0-cp36-abi3-manylinux_2_12_x86_64.manylinux2010_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (290 kB)
Using cached tinycss2-1.3.0-py3-none-any.whl (22 kB)
Using cached anyio-4.4.0-py3-none-any.whl (86 kB)
Using cached argon2_cffi-23.1.0-py3-none-any.whl (15 kB)
Using cached async_lru-2.0.4-py3-none-any.whl (6.1 kB)
Using cached Babel-2.15.0-py3-none-any.whl (9.6 MB)
Using cached exceptiongroup-1.2.1-py3-none-any.whl (16 kB)
Using cached fastjsonschema-2.20.0-py3-none-any.whl (23 kB)
Using cached httpx-0.27.0-py3-none-any.whl (75 kB)
Using cached httpcore-1.0.5-py3-none-any.whl (77 kB)
Using cached jedi-0.19.1-py2.py3-none-any.whl (1.6 MB)
Using cached json5-0.9.25-py3-none-any.whl (30 kB)
Using cached jsonschema-4.22.0-py3-none-any.whl (88 kB)
Using cached jupyter_events-0.10.0-py3-none-any.whl (18 kB)
Using cached jupyter_lsp-2.2.5-py3-none-any.whl (69 kB)
Using cached jupyter_server_terminals-0.5.3-py3-none-any.whl (13 kB)
Using cached overrides-7.7.0-py3-none-any.whl (17 kB)
Using cached pexpect-4.9.0-py2.py3-none-any.whl (63 kB)
Using cached platformdirs-4.2.2-py3-none-any.whl (18 kB)
Using cached prometheus_client-0.20.0-py3-none-any.whl (54 kB)
Using cached requests-2.32.3-py3-none-any.whl (64 kB)
Using cached Send2Trash-1.8.3-py3-none-any.whl (18 kB)
Using cached soupsieve-2.5-py3-none-any.whl (36 kB)
Using cached terminado-0.18.1-py3-none-any.whl (14 kB)
Using cached tomli-2.0.1-py3-none-any.whl (12 kB)
Using cached typing_extensions-4.12.2-py3-none-any.whl (37 kB)
Using cached webencodings-0.5.1-py2.py3-none-any.whl (11 kB)
Using cached websocket_client-1.8.0-py3-none-any.whl (58 kB)
Using cached zipp-3.19.2-py3-none-any.whl (9.0 kB)
Using cached decorator-5.1.1-py3-none-any.whl (9.1 kB)
Using cached stack_data-0.6.3-py3-none-any.whl (24 kB)
Using cached wcwidth-0.2.13-py2.py3-none-any.whl (34 kB)
Using cached asttokens-2.4.1-py2.py3-none-any.whl (27 kB)
Using cached attrs-23.2.0-py3-none-any.whl (60 kB)
Using cached certifi-2024.6.2-py3-none-any.whl (164 kB)
Using cached charset_normalizer-3.3.2-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (142 kB)
Using cached executing-2.0.1-py2.py3-none-any.whl (24 kB)
Using cached idna-3.7-py3-none-any.whl (66 kB)
Using cached jsonschema_specifications-2023.12.1-py3-none-any.whl (18 kB)
Using cached parso-0.8.4-py2.py3-none-any.whl (103 kB)
Using cached ptyprocess-0.7.0-py2.py3-none-any.whl (13 kB)
Using cached python_json_logger-2.0.7-py3-none-any.whl (8.1 kB)
Using cached PyYAML-6.0.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (738 kB)
Using cached referencing-0.35.1-py3-none-any.whl (26 kB)
Using cached rfc3986_validator-0.1.1-py2.py3-none-any.whl (4.2 kB)
Using cached rpds_py-0.18.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.1 MB)
Using cached sniffio-1.3.1-py3-none-any.whl (10 kB)
Using cached urllib3-2.2.2-py3-none-any.whl (121 kB)
Using cached argon2_cffi_bindings-21.2.0-cp36-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (86 kB)
Using cached pure_eval-0.2.2-py3-none-any.whl (11 kB)
Using cached rfc3339_validator-0.1.4-py2.py3-none-any.whl (3.5 kB)
Using cached cffi-1.16.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (443 kB)
Using cached h11-0.14.0-py3-none-any.whl (58 kB)
Using cached jsonpointer-3.0.0-py2.py3-none-any.whl (7.6 kB)
Using cached webcolors-24.6.0-py3-none-any.whl (14 kB)
Using cached fqdn-1.5.1-py3-none-any.whl (9.1 kB)
Using cached isoduration-20.11.0-py3-none-any.whl (11 kB)
Using cached uri_template-1.3.0-py3-none-any.whl (11 kB)
Using cached arrow-1.3.0-py3-none-any.whl (66 kB)
Using cached pycparser-2.22-py3-none-any.whl (117 kB)
Using cached types_python_dateutil-<IP_ADDRESS>40316-py3-none-any.whl (9.7 kB)
Building wheels for collected packages: fragfold
  Building wheel for fragfold (pyproject.toml) ... done
  Created wheel for fragfold: filename=fragfold-0.0.1-py3-none-any.whl size=28331 sha256=a25663eeb7a50899d392b4b45adcc5c164e523a1c468794b49f35041dc076e7d
  Stored in directory: /tmp/pip-ephem-wheel-cache-wi66b6ym/wheels/93/9a/a2/e8fa8d1bdd31e8a43cc95d6eb09621f46e31fd1ccf45a7f263
Successfully built fragfold
Installing collected packages: webencodings, wcwidth, pytz, pure-eval, ptyprocess, fastjsonschema, zipp, widgetsnbextension, websocket-client, webcolors, urllib3, uri-template, tzdata, typing-extensions, types-python-dateutil, traitlets, tornado, tomli, tinycss2, soupsieve, sniffio, six, send2trash, rpds-py, rfc3986-validator, pyzmq, pyyaml, python-json-logger, pyparsing, pygments, pycparser, psutil, prompt-toolkit, prometheus-client, platformdirs, pillow, pexpect, parso, pandocfilters, packaging, overrides, numpy, nest-asyncio, mistune, markupsafe, kiwisolver, jupyterlab-widgets, jupyterlab-pygments, jsonpointer, json5, idna, h11, fqdn, fonttools, executing, exceptiongroup, defusedxml, decorator, debugpy, cycler, charset-normalizer, certifi, babel, attrs, terminado, scipy, rfc3339-validator, requests, referencing, qtpy, python-dateutil, matplotlib-inline, jupyter-core, jinja2, jedi, importlib-resources, importlib-metadata, httpcore, contourpy, comm, cffi, bleach, biopython, beautifulsoup4, async-lru, asttokens, anyio, stack-data, pandas, matplotlib, jupyter-server-terminals, jupyter-client, jsonschema-specifications, httpx, arrow, argon2-cffi-bindings, seaborn, jsonschema, isoduration, ipython, argon2-cffi, nbformat, ipywidgets, ipykernel, qtconsole, nbclient, jupyter-events, jupyter-console, nbconvert, jupyter-server, notebook-shim, jupyterlab-server, jupyter-lsp, jupyterlab, notebook, jupyter, fragfold
Successfully installed anyio-4.4.0 argon2-cffi-23.1.0 argon2-cffi-bindings-21.2.0 arrow-1.3.0 asttokens-2.4.1 async-lru-2.0.4 attrs-23.2.0 babel-2.15.0 beautifulsoup4-4.12.3 biopython-1.83 bleach-6.1.0 certifi-2024.6.2 cffi-1.16.0 charset-normalizer-3.3.2 comm-0.2.2 contourpy-1.2.1 cycler-0.12.1 debugpy-1.8.1 decorator-5.1.1 defusedxml-0.7.1 exceptiongroup-1.2.1 executing-2.0.1 fastjsonschema-2.20.0 fonttools-4.53.0 fqdn-1.5.1 fragfold-0.0.1 h11-0.14.0 httpcore-1.0.5 httpx-0.27.0 idna-3.7 importlib-metadata-7.2.1 importlib-resources-6.4.0 ipykernel-6.29.4 ipython-8.18.1 ipywidgets-8.1.3 isoduration-20.11.0 jedi-0.19.1 jinja2-3.1.4 json5-0.9.25 jsonpointer-3.0.0 jsonschema-4.22.0 jsonschema-specifications-2023.12.1 jupyter-1.0.0 jupyter-client-8.6.2 jupyter-console-6.6.3 jupyter-core-5.7.2 jupyter-events-0.10.0 jupyter-lsp-2.2.5 jupyter-server-2.14.1 jupyter-server-terminals-0.5.3 jupyterlab-4.2.2 jupyterlab-pygments-0.3.0 jupyterlab-server-2.27.2 jupyterlab-widgets-3.0.11 kiwisolver-1.4.5 markupsafe-2.1.5 matplotlib-3.9.0 matplotlib-inline-0.1.7 mistune-3.0.2 nbclient-0.10.0 nbconvert-7.16.4 nbformat-5.10.4 nest-asyncio-1.6.0 notebook-7.2.1 notebook-shim-0.2.4 numpy-2.0.0 overrides-7.7.0 packaging-24.1 pandas-2.2.2 pandocfilters-1.5.1 parso-0.8.4 pexpect-4.9.0 pillow-10.3.0 platformdirs-4.2.2 prometheus-client-0.20.0 prompt-toolkit-3.0.47 psutil-6.0.0 ptyprocess-0.7.0 pure-eval-0.2.2 pycparser-2.22 pygments-2.18.0 pyparsing-3.1.2 python-dateutil-2.9.0.post0 python-json-logger-2.0.7 pytz-2024.1 pyyaml-6.0.1 pyzmq-26.0.3 qtconsole-5.5.2 qtpy-2.4.1 referencing-0.35.1 requests-2.32.3 rfc3339-validator-0.1.4 rfc3986-validator-0.1.1 rpds-py-0.18.1 scipy-1.13.1 seaborn-0.13.2 send2trash-1.8.3 six-1.16.0 sniffio-1.3.1 soupsieve-2.5 stack-data-0.6.3 terminado-0.18.1 tinycss2-1.3.0 tomli-2.0.1 tornado-6.4.1 traitlets-5.14.3 types-python-dateutil-<IP_ADDRESS>40316 typing-extensions-4.12.2 tzdata-2024.1 uri-template-1.3.0 urllib3-2.2.2 wcwidth-0.2.13 webcolors-24.6.0 webencodings-0.5.1 websocket-client-1.8.0 widgetsnbextension-4.0.11 zipp-3.19.2
Installation complete

Could you please clone this branch, reinstall, and try running the example? https://github.com/swanss/FragFold/tree/fix_install
If you're curious here's some documentation here on finding dependencies in pyproject.toml files. https://setuptools.pypa.io/en/latest/userguide/package_discovery.html#finding-simple-packages
I will admit that while I think these commits fixed the install, it's very difficult to test, because once its been installed successful, even if I uninstall the package and revert pyproject.toml back to the previous state (where src was not being found) and then try reinstalling, it still works (e.g. I can import the packages from within any dir). I tried purging the pip cache and using --no-cache-dir, but that didn't work. If you know more about this I would be curious to hear about it.
Thanks for your help!

I figured it out, it was simply that there was no __init__.py file in fragfold/src. I added it in this PR

Thanks for adding it! I forgot to track the file when making my commits.

Great! Glad we could figure this out

Please let me know if/when you complete the example! If you run into other problems feel free to open a new issue.

Everything seems to be working now. Unfortunately I'm running into memory limitations with colabfold, but since I'm even getting to that point everything should be working on the FragFold side.
Also just to clarify: my PR was to the fix_install branch. I intended it this way in case you would like to apply more changes, if not it should be merged into master in order for other people to also get the fix.
Have a great day, I'll open a new issue if anything arises.

Okay, since at least the pip-installed package is working for you, I'll go ahead and merge the branch.


cmake: using MD5_INFILE variable instead of ZephyrPackagePath.txt

Running west zephyr-export creates an entry in the CMake User package
registry.
During this process, a temporary file current_path.txt is created.
This commit ensure the file is removed when no longer needed.
Signed-off-by: Torsten Rasmussen<EMAIL_ADDRESS>

Reported on slack.


i keep getting this how do i fix it?

npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path C:\Users\s\OneDrive\Desktop\SupportBot-release\SupportBot-release/package.json
npm ERR! errno -4058
npm ERR! enoent ENOENT: no such file or directory, open 'C:\Users\s\OneDrive\Desktop\SupportBot-release\SupportBot-release\package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR!      C:\Users\s\AppData\Local\npm-cache_logs\2023-09-24T00_30_42_906Z-debug-0.log
PS C:\Users\s\OneDrive\Desktop\SupportBot-release\SupportBot-release>

Are you sure the package.json is located in that directory. Did you try to use it out the onedrive?
If you still have this error, can you please create a ticket on our discord server? https://discord.gg/p8bxKEwfdE
This would help us better understand your error and help you with it.


stride can support ios for metal？？

stride can support ios for metal？？

https://github.com/stride3d/stride/issues/63#issue-347781715
Stride supports metal API throught MoltenVK.


Unfriendly error when just calling module from python

Traceback (most recent call last):
  File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/home/mark/.local/lib/python3.8/site-packages/spimdisasm/__main__.py", line 12, in <module>
    exit(spimdisasm.frontendCommon.FrontendUtilities.cliMain())
  File "/home/mark/.local/lib/python3.8/site-packages/spimdisasm/frontendCommon/FrontendUtilities.py", line 257, in cliMain
    args = parser.parse_args()
  File "/usr/lib/python3.8/argparse.py", line 1780, in parse_args
    args, argv = self.parse_known_args(args, namespace)
  File "/usr/lib/python3.8/argparse.py", line 1812, in parse_known_args
    namespace, args = self._parse_known_args(args, namespace)
  File "/usr/lib/python3.8/argparse.py", line 2047, in _parse_known_args
    ', '.join(required_actions))
TypeError: sequence item 0: expected str instance, NoneType found```

What spimdisasm version do you have installed?

ah close this. guess I was on 1.11.x sorry :)


Support self-hosted Github Actions for integration/e2e testing

/kind feature
Describe the solution you'd like
Current CI is supporting only Unit testing (and linting). as the project is getting bigger, it would be helpful if we can support integration/e2e test in the CI.
Since integration/e2e testing need to work with ProxmoxVE, CI may need to be self-hosted.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

Cluster-api-provider-proxmox version:
Proxmox VE version:
Kubernetes version: (use kubectl version):
OS (e.g. from /etc/os-release):

it seems self-hosted runners are not recommended for public repos
https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners
need to consider other way


Add support .net standard 1.5 for CacheManager.SystemRuntimeCaching nuget

Hi Micha,
Thanks a lot for your huge effort in order to make this package public.
Want to ask about your plans to add support of .net standard 1.5 or even newer for nuget CacheManager.SystemRuntimeCaching?
Thanks

Yes, System.Runtime.Caching was added back to netstandard2.0 I think. That target will be added soon


[C++][Parquet] Parquet-cpp fails to link when included in multiple TUs

When reader.h is included in multiple cpp files, it causes a linker error
because ScanAllValues is defined in multiple TUs
The solution is to move the definition of ScanAllValues to a separate cc file.
Reporter: Florian Scheibner / @flode
Assignee: Florian Scheibner](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=florian.scheibner) / @flode
Note: This issue was originally created as PARQUET-720. Please see the migration documentation for further details.

Wes McKinney / @wesm:
Issue resolved by pull request 163
https://github.com/apache/parquet-cpp/pull/163


[Feature Request] Improve confd affinity scripting with metadata service

http://rancher-metadata/latest
http://rancher-metadata/latest/self/host/containers returning container objects running on self/host
would greatly help with affinity programming of confd configuration files.
This is a feature request.
At present the only available link is:

/self/host/uuid
/stacks/%s/services/%s/containers/*/host_uuid

I mean to avoid something awkwards like this:
{{ $host_container := getv "/self/host/uuid" }}
{{ gets "/stacks/*/services/*/labels/co.devco.nginx" }}
{{ range gets "/stacks/*/services/*/labels/co.devco.nginx" }}{{ $elem := split .Key "/" }}
  {{ range gets (printf "/stacks/%s/services/%s/containers/*/host_uuid" (index $elem 2) (index $elem 4))  }}{{ $elem := split .Key "/" }}
    {{ if eq $host_container .Value }}
      name-of-nginx-containers-on-this-host: {{getv (printf "/stacks/%s/services/%s/containers/%s/name" (index $elem 2) (index $elem 4) (index $elem 6))}}
    {{end}}
  {{end}}
{{end}}

I link: https://github.com/kelseyhightower/confd/issues/469

@mishak87 I've seen you on this as well in the forum.
https://forums.rancher.com/t/sidekick-how-detect-primary-service-container/1992

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


Night CI 2023-12-11: Failed

action url: https://github.com/spidernet-io/egressgateway/actions/runs/7162294576

for  test, closed


ERROR: Could not find a version that satisfies the requirement sas-kernel

The full error is as follows and occurs after 5 connection timeouts:
Retrying (Retry(total=4, connect =None, read=None, redirect=None)) after connection broken by 'ConnectTimeoutError<<pip._vendor.requests.packages.urlib3.connection.VerifiedHTTPSConnection object at 0x00000000040412E8>, 'Connection to pypi.python.org timed out. '>': /simple/sas-kernel/
Could not find a version that satisfies the requirement sas-kernel (from versions: )
No matching distribution found for sas-kernel
Don't really know what to do about this, hoping someone can help me resolve the issues. Thanks!

I haven't seen that error before. Can you enter the command you're running? Can you also run the following commands just to be sure pip is the right version that your running.
pip --version
pip list
I just installed and upgraded ass-kernel on my system and didn't have any issues so I'm not sure if it might be a problem with pypi or the version you're running.
We'll figure it out!
Tom

Also, is this a system you already have (python, pip) or, did you follow one of the install paths in the sas_kernel Readme; (pip, python, jupyter) or  anaconda, to install all of this,and if so, which one? Is this your first time trying to download and install sas_kernel? We recently upgraded the saspy package (V1.2 from 1.1.1) and the kernel is still at 1.1.1 (just what to expect to find when it works)
Sorry, don't want to sound like level-1 (is it plugged in?), but I don't know what could cause this, so more details will only help. Even 'which pip' command will be sure the pip you're running is the one you expect.
Thanks,
Tom

So I have anaconda installed with Python 3.5 on a Windows 7 OS.
The pip version is pip 8.0.3 and I am using Anaconda Prompt to execute the
following code:
pip install sas_kernel
I think that covers all your questions, let me know what else you think I
should try.
-Jake
On Mon, May 16, 2016 at 9:13 PM, Tom Weber<EMAIL_ADDRESS>wrote:

Also, is this a system you already have (python, pip) or, did you follow
one of the install paths in the sas_kernel Readme; (pip, python, jupyter)
or anaconda, to install all of this,and if so, which one? Is this your
first time trying to download and install sas_kernel? We recently upgraded
the saspy package (V1.2 from 1.1.1) and the kernel is still at 1.1.1 (just
what to expect to find when it works)
Sorry, don't want to sound like level-1 (is it plugged in?), but I don't
know what could cause this, so more details will only help. Even 'which
pip' command will be sure the pip you're running is the one you expect.
Thanks,
Tom
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/sassoftware/sas_kernel/issues/12#issuecomment-219593911

Oh, this isn't supported on windows. This is a linux package only. I suppose that's why it's saying it can't find a valid version.
From: Jacyle<EMAIL_ADDRESS>Sent: Tuesday, May 17, 2016 9:35 AM
To: sassoftware/sas_kernel<EMAIL_ADDRESS>Cc: Tom Weber<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [sassoftware/sas_kernel] ERROR: Could not find a version that satisfies the requirement sas-kernel (#12)
So I have anaconda installed with Python 3.5 on a Windows 7 OS.
The pip version is pip 8.0.3 and I am using Anaconda Prompt to execute the
following code:
pip install sas_kernel
I think that covers all your questions, let me know what else you think I
should try.
-Jake
On Mon, May 16, 2016 at 9:13 PM, Tom Weber <notifications<EMAIL_ADDRESS>wrote:

Also, is this a system you already have (python, pip) or, did you follow
one of the install paths in the sas_kernel Readme; (pip, python, jupyter)
or anaconda, to install all of this,and if so, which one? Is this your
first time trying to download and install sas_kernel? We recently upgraded
the saspy package (V1.2 from 1.1.1) and the kernel is still at 1.1.1 (just
what to expect to find when it works)
Sorry, don't want to sound like level-1 (is it plugged in?), but I don't
know what could cause this, so more details will only help. Even 'which
pip' command will be sure the pip you're running is the one you expect.
Thanks,
Tom
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/sassoftware/sas_kernel/issues/12#issuecomment-219593911

—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHubhttps://github.com/sassoftware/sas_kernel/issues/12#issuecomment-219718910

boooo. Well that was pretty easy to solve haha.
Don't suppose you have any suggestions for how to work with sas datasets in
python using sql commands. I found the sas7bdat module and I can use the
dataframes in pandas to work with the sas dataset, but my work uses a lot
of SQL, so I was hoping to be able to work with sql code within python.
Thought this sas_kernel would have been a good work around.
Thanks for the quick responses by the way, much appreciated.
-Jake
On Tue, May 17, 2016 at 9:37 AM, Tom Weber<EMAIL_ADDRESS>wrote:

Oh, this isn't supported on windows. This is a linux package only. I
suppose that's why it's saying it can't find a valid version.
From: Jacyle<EMAIL_ADDRESS>Sent: Tuesday, May 17, 2016 9:35 AM
To: sassoftware/sas_kernel<EMAIL_ADDRESS>Cc: Tom Weber<EMAIL_ADDRESS>State change <
<EMAIL_ADDRESS>Subject: Re: [sassoftware/sas_kernel] ERROR: Could not find a version that
satisfies the requirement sas-kernel (#12)
So I have anaconda installed with Python 3.5 on a Windows 7 OS.
The pip version is pip 8.0.3 and I am using Anaconda Prompt to execute the
following code:
pip install sas_kernel
I think that covers all your questions, let me know what else you think I
should try.
-Jake
On Mon, May 16, 2016 at 9:13 PM, Tom Weber<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:

Also, is this a system you already have (python, pip) or, did you follow
one of the install paths in the sas_kernel Readme; (pip, python,
jupyter)
or anaconda, to install all of this,and if so, which one? Is this your
first time trying to download and install sas_kernel? We recently
upgraded
the saspy package (V1.2 from 1.1.1) and the kernel is still at 1.1.1
(just
what to expect to find when it works)
Sorry, don't want to sound like level-1 (is it plugged in?), but I don't
know what could cause this, so more details will only help. Even 'which
pip' command will be sure the pip you're running is the one you expect.
Thanks,
Tom
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
<
https://github.com/sassoftware/sas_kernel/issues/12#issuecomment-219593911>

—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub<
https://github.com/sassoftware/sas_kernel/issues/12#issuecomment-219718910>
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/sassoftware/sas_kernel/issues/12#issuecomment-219719633

Yeah, sorry bout that. If you had this on linux, you can use proc sql (in SAS) to do SQL against SAS Data Sets; I use that a ton myself as I find SQL usually is the quickest way to interact with tables for most things.

Since this issue is resolved; can't run this on windows. I'm going to go ahead and close this. If you have access to Linux SAS, even via ssh (remotely), you could try this out from a linux VM on your windows box. If no Linux SAS, then I don't have anything at this time to try. That's another interface to write.
Thanks,
Tom

Please see issue #28 or the SASPy documetation (https://sassoftware.github.io/saspy/install.html#configure-saspy) for details of how to run on PC SAS and virtually all other SAS 9.4 versions.


Windows 10 Subreddit probably doesnt exist

so this program is up to date on 1.8.3 and like I still get this error. I love your app but it only changes the wallpaper when I start my computer. Its a real bummer cause I love my wallpaper to change every 10 minutes. It says that the subreddit doesnt exist for all the favorite subreddits whether its on random or hot or anything. I am on charter communications as a service provider. I also have ran spybot antibeacon and spybot immunizer but it shouldnt stop me from grabbing wallpapers cause it does it right as I login. What can I do to fix this issue?

Hay, could you post the full lost of subs in your subreddit filed please? Also if you could copy the log file and stick it somewhere liek pastebin so I can take a look, it would be appreciated. :)

Do'h! Wrong button!

wallpapers+wallpaper+earthporn+spaceporn+skyporn+technologyporn+imaginarystarscapes
On Tue, Jan 31, 2017 at 1:57 PM, Paul Rawnsley<EMAIL_ADDRESS>wrote:

Do'h! Wrong button!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Rawns/Reddit-Wallpaper-Changer/issues/12#issuecomment-276505713,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYQBXdOidXcyamsXMdSLRLUUOms5c30_ks5rX64ygaJpZM4LxJJn
.

it seems to be changing now after 1.8.4 update so I will email you back if
I keep having issues. You guys rock :D love my wallpaper changer and have
loved it for a long time now since 1.6
On Tue, Jan 31, 2017 at 9:15 PM, Taylor Clark<EMAIL_ADDRESS>wrote:

wallpapers+wallpaper+earthporn+spaceporn+skyporn+technologyporn+
imaginarystarscapes
On Tue, Jan 31, 2017 at 1:57 PM, Paul Rawnsley<EMAIL_ADDRESS>wrote:

Do'h! Wrong button!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Rawns/Reddit-Wallpaper-Changer/issues/12#issuecomment-276505713,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYQBXdOidXcyamsXMdSLRLUUOms5c30_ks5rX64ygaJpZM4LxJJn
.

Awesome! Glad it's working again. 👍

I'm still getting this issue on <IP_ADDRESS>. I believe it's related to reddit search being down/overloaded since every time this shows up in the log its immediately preceded by another error that says Reddit Server Unavailable.
3/8/2017 11:29:22 AM - WIN-3ANMC1H9IUV: Changing wallpaper.
3/8/2017 11:29:22 AM - WIN-3ANMC1H9IUV: The background worker started successfully and is looking for a wallpaper.
3/8/2017 11:29:22 AM - WIN-3ANMC1H9IUV: Sellected sub to search: wallpapers
3/8/2017 11:29:22 AM - WIN-3ANMC1H9IUV: Full URL Search String: http://www.reddit.com/r/wallpapers/search.json?q=2560x1440+OR+1440p+OR+WQHD+NOT+(title%3a+car+OR+title%3a+lamborghini+OR+BMW)+self%3Ano+((url%3A.png+OR+url%3A.jpg+OR+url%3A.jpeg)+OR+(url%3Aimgur.png+OR+url%3Aimgur.jpg+OR+url%3Aimgur.jpeg)+OR+(url%3Adeviantart))&sort=top&restrict_sr=on&t=all
3/8/2017 11:29:22 AM - WIN-3ANMC1H9IUV: Searching Reddit for a wallpaper.
3/8/2017 11:29:35 AM - WIN-3ANMC1H9IUV: Reddit Server Unavailable, try again later.
3/8/2017 11:29:35 AM - WIN-3ANMC1H9IUV: Subreddit probably does not exist.


Store the project and task names in the timer

📒 Description
This PR makes the timer widget store the current task and project names for when the timer widget needs to be repainted (on window size change, especially)
🕶 Types of changes

Bug fix (non-breaking change which fixes an issue)

🤯 List of changes

Linux - Project and Task information in the Timer no longer disappears on window size change

👫 Relationships
Closes #3102
Closes #3103
🔎 Review hints
Check if the project and task names in the running timer widget are displayed as expected, even when you change the size of the window.

Well done, Sir!


To-expire secret builtin

Developers usually have to deal with broken jobs due to expired secrets (usually API tokens). Ideally, all tokens should be automatically rotated, but this is hard (sometimes even impossible) to do.
From Makes it would not be possible for us to support builtins for rotating tokens for X, Y and Z stacks.
I propose creating a generic builtin for tracking token expiration dates:
validateSecretExpiration = {
  integrates = {
    expirationDate = "01/08/2020";
    minimumDaysToExpire = 7;
  };
  bugsnag = {...};
};

That way developers would be forced to rotate the token by the CI before it expires.

As discussed in #502, we will no longer support specific-purpose builtins


NoSuchMethodException

Trying to create a Giftcard using the BuycraftAPI, I ran into this error:
[12:53:28 ERROR]: Caused by: java.lang.reflect.UndeclaredThrowableException
[12:53:28 ERROR]:       at jdk.proxy5/jdk.proxy5.$Proxy21.createGiftCard(Unknown Source)
[12:53:28 ERROR]:       ... 47 more
[12:53:28 ERROR]: Caused by: java.lang.NoSuchMethodException: java.lang.invoke.MethodHandles$Lookup.<init>(java.lang.Class,int)
[12:53:28 ERROR]:       at java.base/java.lang.Class.getConstructor0(Class.java:3517)
[12:53:28 ERROR]:       at java.base/java.lang.Class.getDeclaredConstructor(Class.java:2691)
[12:53:28 ERROR]:       at retrofit2.Platform$Java8.invokeDefaultMethod(Platform.java:102)
[12:53:28 ERROR]:       at retrofit2.Retrofit$1.invoke(Retrofit.java:145)
[12:53:28 ERROR]:       ... 48 more

Apparently, this method has been removed since Java 14
Environment:
Java 16
Bungeecord
Windows 10

Hi there,
Thanks for taking the time to report this issue, I'm sorry it's been slow to get resolved — we're working on it!
Unfortunately, this issue is old enough that we've had to close it. But if you see any other issues (especially ones with the same or similar symptoms), please reply here and I'll look into getting them fixed.
We are currently planning a recode of the Buycraft plugin at some point in Q2 of this year, and we would love to know what issues still exist so they can be fixed for the new plugin.
Apologies for the issues you have faced!


Potential memory leak in Bellatrix merge fork

There have been reports from users about unusual memory spikes abnormal to other networks. Issue #3861 addresses the need to increase memory from the default Docker setting of 2.0GB to a minimum recommended minimum setting of 4.0GB.
This issue will track the issue specifically related to the potential memory leak on our Bellatrix merge tests.

Did some basic investigation with memory dumps and comparing them over 5,10,60 minutes window, didn't find anything weird going on related to merge/post merge. (snapshots size varies ~ 460-560 range)

Here is the process heap graph of our own lodestar <> geth setup validation with around ~500 validators:

Lodestar seems to be using ~1.8GB of heap memory, total setup : lodestar + geth + 2 validator instances running on kiln ~3.2GB:

@philknows any specific pointers by the users? to help narrow this down?

closest I have come to is to find a bit of correlation between inbound peer connections and heap. The starting of this graph is just after merge transition (when the metrics collection was started on our kiln testnet server).
Noteworthy thing is: there were chaos around the merge transition as a subset of prysm (i think) related nodes were proposing invalid payloads, which might be resulting into some peer turbulence.

Pari's Kiln dashboard had a bad query that plotted data wrong. The reported memory usage was of 95% of 8GB, but it was really 4GB. After manually checking each instance, every Lodestar process takes ~1.8GB max with constant memory through 7 days.
Since there's no hard evidence of a leak anymore, closing


chore: bdd-spring-1576024206 to 0.0.1

chore: Promote bdd-spring-1576024206 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


The "Run all tests" icon doesn't change (to red "Stop" icon) while the tests are running.

This was working yesterday.
(Since I refactored my code totally and changed vscode-test-adapter-api version too.)
Now:
"vscode-test-adapter-api": "^1.0.1"
Test Explorer UI: 2.0.1
(Maybe it is just me, 3th day with TS/JS and with VS Code)
What other relevant informations can I give?
(I will publish my source in a couple of days.)

The icon changes when the Test Explorer receives the TestRunStartedEvent and changes back when it receives the TestRunFinishedEvent, so you could experiment with that.
You could also package and install (using the menu entry "Install from VSIX...") your extension and then debug this extension. The icon is changed to "Stop" here and back to "Play" here.

I will publish my source in a couple of days

I could have a look when you do that.

I just found a bug (and published a fix) that would explain this if you have another Test Adapter extension installed.

I'm sending the events you've mentioned. Still..
I've installed the Google Test Explorer, but uninstalled it after. Could it affect me?

Nah, still it isn't works.
Do I need a Test Controller?
My main is like:
export async function activate(context: vscode.ExtensionContext) {
  const testExplorerExtension = vscode.extensions.getExtension<TestHub>(
    testExplorerExtensionId
  );

  if (testExplorerExtension) {
    if (!testExplorerExtension.isActive) {
      await testExplorerExtension.activate();
    }

    const registeredAdapters = new Map<vscode.WorkspaceFolder, Catch2TestAdapter>();

    if (vscode.workspace.workspaceFolders) {
      for (const workspaceFolder of vscode.workspace.workspaceFolders) {
        const adapter = new Catch2TestAdapter(workspaceFolder);
        registeredAdapters.set(workspaceFolder, adapter);
        testExplorerExtension.exports.registerTestAdapter(adapter);
      }
    }

    vscode.workspace.onDidChangeWorkspaceFolders(event => {
      for (const workspaceFolder of event.removed) {
        const adapter = registeredAdapters.get(workspaceFolder);
        if (adapter) {
          testExplorerExtension.exports.unregisterTestAdapter(adapter);
          registeredAdapters.delete(workspaceFolder);
        }
      }

      for (const workspaceFolder of event.added) {
        const adapter = new Catch2TestAdapter(workspaceFolder);
        registeredAdapters.set(workspaceFolder, adapter);
        testExplorerExtension.exports.registerTestAdapter(adapter);
      }
    });
  }
}

If you can see your tests in the Test Explorer, then your main is definitely fine.
Could you attach a TestLoadFinishedEvent and a TestRunStartedEvent?

I just thought I may need a controller too.

The Test Explorer UI is a TestController, you don't need another one.

When can it get an array with more than 1 elements?

Currently this never happens, but in the future it could be used to e.g. implement something like "Run all failed tests", in that case the tests array would contain the IDs of the failed tests (instead of the ID of the top suite).

If the tests are started, I can't start another with the AllTests "Play" button, but I can start with the "Play" button next to the test. I should handle it, shouldn't I?

Yes, Test Adapters should make sure that only one test run is active at a time. This used to be the responsibility of the Test Explorer, but with the new API, there can be multiple controllers, so this needs to be handled by the adapters.

Such a noob mistake.

It sounds to me like you're making fast progress for a "noob" :)

Thank You for your support. ^^

Hey!
I published my extension (version 0.1.0).
You can check it here.
Bests,
Mate

@matepek Nice! I wonder if your implementation would naturally be supported by the Live Share integration. It would be amazing to support collaborative C++ test running in a Live Share session.

@matepek  Awesome!
@lostintangent There's no reason why it shouldn't, any Test Adapter should work with the Live Share integration out-of-the-box.

@hbenl Would you add my extensions link to the README.md? ^^
Catch2 Test Explorer

@matepek Of course :)


Add Bazel build support for macOS

Desired behaviour
Build the ignition libraries with Bazel on macOS.
Alternatives considered
Not applicable
Implementation suggestion
Prototype changes to Bazel build files in the following forks - these are macOS only at present.

https://github.com/srmainwaring/ign-bazel/tree/bazel-macos
https://github.com/srmainwaring/ign-common/tree/bazel-macos/ign-common3
https://github.com/srmainwaring/ign-math/tree/bazel-macos/ign-math6
https://github.com/srmainwaring/ign-plugin/tree/bazel-macos/ign-plugin1
https://github.com/srmainwaring/ign-transport/tree/bazel-macos/ign-transport9
https://github.com/srmainwaring/ign-tools/tree/bazel-macos/ign-tools1

The Bazel build for these libraries do not require changes

https://github.com/ignitionrobotics/ign-msgs
https://github.com/ignitionrobotics/ign-physics
https://github.com/ignitionrobotics/ign-utils
https://github.com/ignitionrobotics/sdformat

The libraries will build up to ignition-physics. To build ign-rendering and the libraries that depend on it needs a larger number of changes to the Bazel build files for ogre2, and to be useful this will need to be updated to ogrev2.2 with Metal support.
Additional context
See https://community.gazebosim.org/t/python-bindings-for-gazebo-ignition/360/12?u=srmainwaring

Hi @mjcarroll, bindings for publishing using ign-transport are working (on macOS) on this branch https://github.com/srmainwaring/python-ignition/tree/bazel-macos/python-ignition.
For example the publisher from the ign-transport Messages tutorial looks like this in Python:
import time

from ignition.msgs.stringmsg_pb2 import StringMsg

from python_ignition.ignition_transport import AdvertiseMessageOptions
from python_ignition.ignition_transport import Node
from python_ignition.ignition_transport import Publisher

def main():
    # Create a transport node and advertise a topic
    node = Node()
    topic = "/foo"
    msg_type_name = StringMsg.DESCRIPTOR.full_name
    pub_options = AdvertiseMessageOptions()
    pub = node.advertise(topic, msg_type_name, pub_options)
    if pub.valid():
        print("Advertising {} on topic[{}]".format(msg_type_name, topic))
    else:
        print("Error advertising topic [{}]".format(topic))

    # Prepare the message
    msg = StringMsg()
    msg.data = "hello"

    try:
        while True:
          if not pub.publish(msg):
              break

          print("Publishing hello on topic[{}]".format(topic))
          time.sleep(1.0)

    except KeyboardInterrupt:
        pass

if __name__ == "__main__":
    main()

It's a bit fiddly to assemble at present because I have not updated the bazel.repos file which is required from macOS. On Ubuntu you should only need the external build file ign-msgs9.BUILD, but I have not tested on that platform.


Regenerate Key Vault and record re-tests for service version 7.4

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-security-keyvault-administration


RC Spot-Check Test: Ratio And Proportion 1.2.0-rc.4

RC Spot-Check Test
Mentions:  @emily-phet @terracoda @BLFiedler
previous test: https://github.com/phetsims/qa/issues/874
Simulation links

github repository for issues
phet top level directory
sim: all_phet.html

Test Matrices
General Test:

[ ] Tester =  , Platform =  , Time =
[ ] Tester = , Platform = , Time =

Additional Features Test:

[ ] Tester = , Platform = , Time =
[ ] Tester = , Platform = , Time =

Features included

[ ] PhET-iO
[x] Alternative Input
[x] UI Sound
[x] Sonification
[x] Description
[x] Voicing

Focus and Special Instructions

Issues to Verify
These issues should have the "status:ready-for-cherry-pick" label. Please feel free to close all below if they look good.

[ ] https://github.com/phetsims/joist/issues/895
[x] https://github.com/phetsims/ratio-and-proportion/issues/548
[ ] https://github.com/phetsims/ratio-and-proportion/issues/546
[ ] https://github.com/phetsims/ratio-and-proportion/issues/542
[ ] https://github.com/phetsims/ratio-and-proportion/issues/541

For QA...

General features

What to Test

Click every single button.
Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.

If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
Test some query parameters. (See QA Book for a list of query parameters.)
When making an issue, check to see if it was in a previously published version.
Try to include version numbers for browsers.
If there is a console available, check for errors and include them in the Problem Description.
As an RC begins and ends, check the sim repo. If there is a maintenance issue, check it and notify developers if there is a problem.
As the RC ends, notify the developer of any new QA credits that need to be added.

PhET-iO features

What to Test

Make sure that public files do not have password protection. Use a private browser for this.
Make sure that private files do have password protection. Use a private browser for this.
Make sure standalone sim is working properly.
Make sure the wrapper index is working properly.
Make sure each wrapper is working properly.
Launch the simulation in Studio with ?stringTest=xss and make sure the sim doesn't navigate to youtube
For newer PhET-iO wrapper indices, save the "basic example of a functional wrapper" as a .html file and open it. Make
sure the simulation loads without crashing or throwing errors.
Load the login wrapper just to make sure it works. Do so by adding this link from the sim deployed root:/wrappers/login/?wrapper=record&validationRule=validateDigits&&numberOfDigits=5&promptText=ENTER_A_5_DIGIT_NUMBER

Further instructions in QA Book
Conduct a recording test to Metacog, further instructions in the QA Book. Do this for iPadOS + Safari and one other
random platform.
Conduct a memory test on the stand alone sim wrapper (rc.1).
Test one platform combination with ?phetioDebug=true on the Studio and State wrapper.
If Pan/Zoom is supported, make sure that it works when set with PhET-iO State.
Test that the sim works offline:

Click the link to the phet-io zip file (at top of issue) to download the zip file.
Unzip it to a spot locally.
Open index.html by double clicking it on your desktop or in a Finder-view.
It should look like the standalone version of the sim in PhET-iO brand.

Accessibility features

What to Test

Specific instructions can be found above.

Make sure the accessibility (a11y) feature that is being tested doesn't negatively affect the sim in any way. Here is
a list of features that may be supported in this test:

Alternative Input
Interactive Description
Sound and Sonification
Pan and Zoom
Mobile Description
Voicing

Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.
Test all keyboard navigation inputs (if applicable).
Test all forms of input with a screen reader (if applicable).

If this sim is not in this list or up to date there, make an
issue in website to ask if PhET research page links need updating. Please
assign to @terracoda and @emily-phet.

Screen Readers
This sim may support screen readers. If you are unfamiliar with screen readers, please ask Katie to introduce you to
screen readers. If you simply need a refresher on screen readers, please consult the
QA Book, which should have all of the information
you need as well as a link to a screen reader tutorial made by Jesse. Otherwise, look over the a11y view before opening
the simulation. Once you've done that, open the simulation and make sure alerts and descriptions work as intended.

Platforms and Screen Readers to Be Tested

Windows 10 + Latest Chrome + Latest JAWS
Windows 10 + Latest Firefox + Latest NVDA
macOS + Safari + VoiceOver
iOS + Safari + VoiceOver (only if specified in testing issue)

Critical Screen Reader Information
We are tracking known screen reader bugs in
here. If you find a
screen reader bug, please check it against this list.

Keyboard Navigation
This sim supports keyboard navigation. Please make sure it works as intended on all platforms by itself and with a
screen reader.
Magnification
This sim supports magnification with pinch and drag gestures on touch screens, keyboard shortcuts, and mouse/wheel controls. Please test magnfication and make sure
it is working as intended and well with the use cases of the simulation. Due to the way screen readers handle user input, magnification is NOT expected to
work while using a screen reader so there is no need to test this case.

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

The build queue is a bit large right now so the sim isn't published yet, when the links work, then the sim is published :)

https://github.com/phetsims/ratio-and-proportion/issues/542 is closed, does that mean it can be checked off?

Calling QA here

Thanks! I'll make sure get the QA credits in before publishing. CLosing


ln_db_lmdb: fix to not close dbs

for forward and payment
mdb_dbi_close is not thread-safe
we do not do it because it is not necessary

fix #1373


Fix/usage within dir rtl elements

The usage/rendering logic is broken when the component is used inside a html element which has layout direction set to rtl.
Change the rtl prop to enable the container usage in an element which has rtl enabled. Adding rtl to html element can be done by two ways (html-attribute dir or styles direction) and both are handled properly.
The downside of this approach is, that the usage of rtl-prop is changed. This, on the other hand should be a depreaction step worth taking. The benefit of being able to use the component without hacks in rtl-layouts is considerable.
The demos represent the differences usage. Both blocks represent adding direction by different means and should behave identically.

Hey,
I was working in a commercial project which utilized this component and had support for rtl-layout as a requirement. This pull request changes the usage of rtl-prop to facilitate the usage of the component inside of elements with rtl.

Could you please not use so many examples?

Sure thing! It was for testing mainly. I am glad to make changes. Will do
it soon. Did not mean to annoy.
to 1. maalisk. 2018 klo 14.36 lavee singh<EMAIL_ADDRESS>kirjoitti:

Could you please not use so many examples?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/akiran/react-slick/pull/1069#issuecomment-369578370,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA2pPgkJvi9_w04SLAaG8SrVp9fXsO9hks5tZ-s3gaJpZM4SVGge
.

I think I found a very simple solution: 6395faa52f908b9e023b51a77ef3e38f0d5300fb
Let me know if you think otherwise.


Should the  Interlocked class be used?

I was learning more about threads last week, and found out that the Interlocked class is the thread safe way for increment and decrement.
So instead of _waiters++; it should be
Interlocked.Increment(ref _waiters);
and instead of _waiters—; it should be
Interlocked.Decrement(ref _waiters);
Have you had any problems with the _waiters variable in your tests?

Not yet, but your suggestion seems reasonable enough: I can patch the code accordingly, it seems like a solid suggestion.


Handle mismatching container digests in Console UI

Feature description
The Kabanero stack CR is going to have a digest key/value added to it. This digest value will be set at the time the stack was activated.
The Operator will manage that new field for each stack.
The CLI will need to be updated to give the current digest for a stack. If the digest in the stack CR doesn't match one from CLI we have a problem.
What needs to be done is the console needs to compare those 2 digests and display a warning on the stacks page if they do not match. The warning can be a yellow warning triangle next to the stack name.
Feature design or visual mockup
https://github.com/stephenkinder/kabanero-foundation/blob/digest/design/digest.md
Operator has finished their work - info on how to get the digest from the CRD is in this operator PR comment
Additional context
Why this is a problem
Example scenario:
A developer will have configured Appsody to point at tag 0.3 and 0.3 tag points to 0.3.2, but Kabanero doesn't have the 0.3.2 stack activated.
Today, when this happens we currently "warn" - saying hey we're going to give you the 0.3.2 stack, even though the stack maintainer didn't say it was explicitly okay to use it (they would explicitly say okay by activating the stack)
Currently, this takes away the whole point of activating/deactivating stacks - if we just ignore if they're active or not.

The Kabanero CR will have a policy for what to do when we hit mismatching digests: warn, fail, no action. (console may allow users to change this via UI in future, but is not a part of this work
the update would be a Global policy change for all configured stack indexes due to how the CLI handles stacks as 1 big group)

@stephenkinder Did we decide to move this out of 070 and into 080?

Blocks https://github.com/kabanero-io/docs/issues/371

From Dave, an example of output from the list stacks endpoint from the CLI API
"kabanero stacks": [
        {
            "name": "java-microprofile",
            "status": [
                {
                    "digest check passed": true,
                    "version": "0.2.26",
                    "image digest": "5c7bec7fc901b88aef6da457144873657640cbe520504379731d856c480deb9a",
                    "kabanero digest": "5c7bec7fc901b88aef6da457144873657640cbe520504379731d856c480deb9a",
                    "status": "active"
                }
            ]
        },

PR #209 has the code written that it needs to:

Allow users to update the digest policy according to https://github.com/kabanero-io/docs/pull/366/files#diff-6388a1bc1f22f42dd9d1b77b20bbc730R12-R18

Use the output from the CLI API to display on the console UI if the digest check passed or not.

CLI Services did a check for the strictDigest policy and released that so we can start testing. I talked to Dave and they will need to implement the check for the other 3 policies. Once they finish that we’ll do a final test with all the policy options.


Lost ability to place calls and text messages on Galaxy A52 5G.

Commands seemed to work great on my Galaxy A52 5G except for the fact that the phone now shows no bars of service with an "x" through the signal strength meter. I still get data services (5G, LTE) but I cannot place a call or text messages. I've played around with the mobile network settings and manually selected my provider to no avail . I've also factory reset the phone and repeated the process with the same results. The problem occurs following the first restart of the device following the debloat process which seems interesting - I successfully made a test call immediately after performing the process but could no longer place a call after the reboot. I also made sure to omit the commented out command "pm uninstall -k --user 0 com.wsomacp" so there must be something else at play here.
Regardless, thank you so much for this process. This work is hugely appreciated.

NEVERMIND. I got it working by uninstalling the packages in a more peacemeal fashion - I went through the list about 100 packages at a time and restarted the phone between each process. Ultimately everything in the master list has been removed and phone calls and texts still appear to work. I guess the lesson is not to do everything at once.


Properly scope the cache for each image build

in order to avoid cache pollution between different images, we need to scope the cache for each image build. See documentation of that feature here:
https://docs.docker.com/build/cache/backends/gha/#scope
Changes

Submitter Checklist

[ ] 📝 Please ensure your commit message is clear and informative. For guidance on crafting effective commit messages, refer to the How to write a git commit message guide. We prefer the commit message to be included in the PR body itself rather than a link to an external website (ie: Jira ticket).

[ ] ♽ Before submitting a PR, run make test lint to avoid unnecessary CI processing. For an even more efficient workflow, consider installing pre-commit and running pre-commit install in the root of this repository.

[ ] ✨ We use linters to maintain clean and consistent code. Please ensure you've run make lint before submitting a PR. Some linters offer a --fix mode, which can be executed with the command make fix-linters (ensure markdownlint and golangci-lint tools are installed first).

[ ] 📖 If you're introducing a user-facing feature or changing existing behavior, please ensure it's properly documented.

[ ] 🧪 While 100% coverage isn't a requirement, we encourage unit tests for any code changes where possible.

[ ] 🎁 If feasible, please check if an end-to-end test can be added. See README for more details.

[ ] 🔎 If there's any flakiness in the CI tests, don't necessarily ignore it. It's better to address the issue before merging, or provide a valid reason to bypass it if fixing isn't possible (e.g., token rate limitations).

/retest


[#12] [#30] using shorter representation for protobuf map in output and sorted by key

add the feature for #12
fixed #30

tested it... looks good from a functional point of view