Specifying config for cluster up missing tag in README

Creating Your First Cluster
Assuming you have a configuration built (as described above), you're ready to create your first cluster. Run the following command.
If you have used the default config location:
kraken cluster up

Or you can specify the location of the config file:
kraken cluster up ${HOME}/krakenlibconfigs/config.yaml

Last line should include --config tag
kraken cluster up --config ${HOME}/krakenlibconfigs/config.yaml

While in the README:

Fix the link under Optional configuration changes (more advanced) from https://samsung-cnct.github.io/k2/ to https://samsung-cnct.github.io/kraken-lib
Add https:// to the link under Working with Your Cluster (Using kraken) so that github renders it correctly. quay.io/samsung_cnct/k2
Without the full link, Github will think it is an internal link and give a 404


Autopilot reset Important text

This sentence makes no sense to me: "The feature for Autopilot Reset will stay grayed out, unless you reset the device using Autopilot (either using Fresh Reset or manually sysprep the device)."
Maybe it's trying to clarify that Autopilot Reset is only available for devices that have an actual Autopilot device object in Intune?
Also, Fresh Reset should be Fresh Start, but I don't see just executing that or syspreping it does not magically create an Autopilot device object (at least, not in all scenario's).

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 98a662f1-c2aa-33ad-0e71-d0cbb288d053
Version Independent ID: 196f1c8d-3179-c173-194f-08bf3a6f82ca
Content: Windows Autopilot Reset - Windows Deployment
Content Source: windows/deployment/windows-autopilot/windows-autopilot-reset.md
Product: w10
Technology: windows
GitHub Login: @greg-lindsay
Microsoft Alias: greglin

Thank you for pointing out the possible misinterpretation of the document text.
Have I understood you correctly, that you would like to see the text below added somewhere in the page?
"Autopilot Reset is only available for devices that have an actual Autopilot device object in Intune."
Do you have a suggestion or recommendation where on the page that text should be placed?

I’d prefer not to have to be the one to choose that, it’s not completely clear to me what the original intention of that remark is, so I would prefer not to make the same mistake 😊
Maybe PG can help out?
From: Trond B. Krokli<EMAIL_ADDRESS>Sent: Friday, 21 February 2020 01:13
To: MicrosoftDocs/windows-itpro-docs<EMAIL_ADDRESS>Cc: Wout Vergauwen<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/windows-itpro-docs] Autopilot reset Important text (#6063)
Thank you for pointing out the possible misinterpretation of the document text.
Have I understood you correctly, that you would like to see the text below added somewhere in the page?
"Autopilot Reset is only available for devices that have an actual Autopilot device object in Intune."
Do you have a suggestion or recommendation where on the page that text should be placed?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/windows-itpro-docs/issues/6063?email_source=notifications&email_token=AMAHJ5H6ZO247WCYQGDBLZDRD4L7PA5CNFSM4KV2ORL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMRBEPI#issuecomment-589435453, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMAHJ5AIOC7AENFQSPF46NTRD4L7PANCNFSM4KV2ORLQ.

I’d prefer not to have to be the one to choose that, it’s not completely clear to me what the original intention of that remark is, so I would prefer not to make the same mistake 😊 Maybe PG can help out?

Fair enough. I am not sure what "PG" means, but I am guessing it is similar to PM in the Microsoft Docs teams. Very well, I will wait for more feedback.

Product Group 😊
From: Trond B. Krokli<EMAIL_ADDRESS>Sent: Friday, 21 February 2020 11:47
To: MicrosoftDocs/windows-itpro-docs<EMAIL_ADDRESS>Cc: Wout Vergauwen<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/windows-itpro-docs] Autopilot reset Important text (#6063)
I’d prefer not to have to be the one to choose that, it’s not completely clear to me what the original intention of that remark is, so I would prefer not to make the same mistake 😊 Maybe PG can help out?
Fair enough. I am not sure what "PG" means, but I am guessing it is similar to PM in the Microsoft Docs teams. Very well, I will wait for more feedback.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/windows-itpro-docs/issues/6063?email_source=notifications&email_token=AMAHJ5E6FTVSTKKGRO75DX3RD6WLDA5CNFSM4KV2ORL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMSJVCI#issuecomment-589601417, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMAHJ5DLSSJCWAW5EALLZIDRD6WLDANCNFSM4KV2ORLQ.

Hi, I'm getting clarification now about this comment. You're right it doesn't make sense.

The original author of the comment is no longer with the company and nobody understand what is being conveyed here so I'm removing the statement.  I've read about the reset option being greyed out, but only when the OS version is not sufficient, and there is a note about that already.


Fix formatting with cargo fmt --check

My other PR (#1530) fails because of formatting errors not related to my changes, decided to open a new PR that only fixes formatting

Codecov Report

Merging #1532 (1c2b27f) into main (3675a51) will decrease coverage by 0.01%.
The diff coverage is n/a.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1532      +/-   ##
==========================================
- Coverage   68.74%   68.74%   -0.01%
==========================================
  Files         120      120
  Lines       13094    13094
==========================================
- Hits         9002     9001       -1
- Misses       4092     4093       +1

decided to open a new PR that only fixes formatting

:100: I love your idea.


More dev-cmd tests cleanup

Test dev-cmd *_args methods. These are fast and improve coverage

Add a few missing *_args.parse invocations.

Separate tap tests into separate, correct (i.e. in cmd) files. Extracted from https://github.com/Homebrew/brew/pull/5925

[x] Have you followed the guidelines in our Contributing document?

[x] Have you checked to ensure there aren't other open Pull Requests for the same change?

[x] Have you added an explanation of what your changes do and why you'd like us to include them?

[x] Have you written new tests for .qfgyour changes? Here's an example.

[x] Have you successfully run brew tests with your changes locally?

@scpeters This has dev-cmd up to 39% again 🎉


Set up to host the semantic-reranker plugin in the root

Description
This PR sets up the semantic-reranker plugin to be hosted in the root of the repo, updates standard documentation, moves the original README.md to RELEVANCE.md, and begins to describe future use case for this plugin and repo.
Issues Resolved
Fixes #20
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

It looks like there are a few editor swap files (with names ending in ~) that snuck into the commit.
We should delete those before merging.


Explore current landscape of bulk deconvolution methods

To expand the manuscript with biological analysis of portal data, we have discussed a goal of exploring the cell type landscape between bulk and single-cell data on the portal. It has been observed (for example) that cell types detected in bulk may not be detected in single-cell. To what extent is this case in ScPCA data?
As a first step, we would like to understand more about bulk deconvolution methods in the first place, including:

What tools are commonly used these days?
What kind of information/output do these tools provide?

For any analysis we proceed with on this front, we'll want to be able to compare results a) across cell types within a sample, and b) across samples, so we need to ensure any method we use provides information that can meaningfully & interpretably be used for these comparisons (e.g., proportions that actually are proportions are good, and scores with no universal scale are not good).

Do we have the data to run these methods? If there are any methods which rely on fastq/bam, those aren't going to work for us.

This issue tracks exploration into these methodologies, which I will comment about here as I explore and break out additional issues as needed.

Additional context: https://github.com/AlexsLemonade/OpenScPCA-admin/issues/287

Here's some of what I found on methods that do not use/require scRNA-seq references. The literature may refers to these as "first generation deconvolution" methods; "second generation" methods are those that leverage scRNA-seq for a cell type reference.
For this, I began by looking through 2 benchmarking papers to get a sense of what methods are out there, and then looking more closely at the individual methods themselves that seemed potentially useful:

Benchmarking of cell type deconvolution pipelines for transcriptomics data https://doi.org/10.1038/s41467-020-19015-1
Comprehensive evaluation of transcriptome-based cell-type quantification methods for immuno-oncology https://doi.org/10.1093/bioinformatics/btz363

Of the methods I poked around with, I identified a few that meet these criteria:

They do not require scRNA-seq references
They appear to be maintained, or at least not unmaintained! We have some evidence that folks are at least checking in to maintain these methods, even if not further develop them
They estimate a quantity which can be used to compare across cell types within samples as well as between samples.

It's additionally worth noting the immunedeconv R package which wraps several methods for immune deconvolution, which broadly corresponding to bulk deconvolution methods in general. Two of the methods I list below can be run via immunedeconv, but they can also be run standalone.
EPIC

https://doi.org/10.7554/eLife.26476.001
https://github.com/GfellerLab/EPIC/

Infers absolute cell proportions, and will indeed return "other" when other is merited
Requires input TPM or RPMK with gene symbol identifiers
Available in immunedeconv

quanTIseq

https://github.com/icbi-lab/quanTIseq & https://icbi.i-med.ac.at/software/quantiseq/doc/index.html
https://doi.org/10.1186/s13073-019-0638-6

Provides an absolute score which can be interpreted as a fraction
Worth noting we used this via immunedeconv in OpenPBTA https://github.com/AlexsLemonade/OpenPBTA-analysis/blob/e854738b57b16c3725673ad63b4ffd20ec48ad19/analyses/immune-deconv/01-immune-deconv.R#L99-L103

CIBERSORTx

https://www.nature.com/articles/s41587-019-0114-2
https://pmc.ncbi.nlm.nih.gov/articles/PMC7695353/
https://cibersortx.stanford.edu/

The new(-sh) CIBERSORTx version is distinguished from the original CIBERSORT by a) its batch correction framework, and b) its ability to estimate cell type composition from bulk, and cell proportions can be imputed from that
This software is (notoriously it seems?) less than straightforward to obtain, but I believe it is mostly a standalone R script (though it's also worth noting this preprint ran CIBERSORTx via docker container with a token from the authors, so this might be an option for us too). While it is open source for non-commercial use, it is directly disseminated by the authors; I have registered for the software and am currently awaiting approval to be able to obtain this script.
This method can be alternatively run with scRNA-seq reference profiles, so it may be a useful apples-to-apples comparison
I am not 100% sure if this can be run with immunedeconv, which implements a previous version of this method CIBERSORT (sans x). This discussion seemed to suggest that it might be the CIBERSORT abs (absolute) mode, but section 5.2 of this methods paper implies that the absolute mode is actually part of the original CIBERSORT algorithm; this makes more sense to me based on publishing dates.

Either way, because of versioning challenges with how this software is disseminated, it's probably best to run this method as standalone if we want to use it, rather than from within immunedeconv.

Next steps
I would like to test running an ScPCA dataset through each method in order to:

Make sure we have a precise sense of the inputs and outputs for each method, including method parameterizations which may be relevant to us
Determine which method(s), if any, we would want to use in a scientific analysis.

I will open an issue per method so comments don't get too bloated here, and I will leave further comments on those method-specific issues.
Note that the scope of this exploration doesn't currently include looking at further methods (or variations on these methods, e.g. with CIBERSORTx) that use scRNA-seq reference profiles, but we may complement this exploration with those at a future time.

Closing this in favor of next steps in the method-specific issues. If we want to explore additional methods, we can re-open this or open a new issue for them.


pip install batterydataextractor failed

Hi, I use pip install batterydataextractor on a mac m1 computer. I am using python version 3.9.13, and it prompts that the installation failed.

The error message is as follows:
 Running setup.py install for nmslib ... error
  error: subprocess-exited-with-error

  × Running setup.py install for nmslib did not run successfully.
  │ exit code: 1
  ╰─> [25 lines of output]
      Dependence list: ['pybind11<2.6.2', 'psutil', "numpy>=1.10.0,<1.17 ; python_version=='2.7'", "numpy>=1.10.0 ; python_version>='3.5'"]
      /Users/rzht/Documents/workspace/batterydataextractor_v1/lib/python3.9/site-packages/setuptools/dist.py:717: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead

example
from batterydataextractor.doc.text import Paragraph text = '1H NMR spectra were recorded on a Varian MR-400 MHz instrument.' doc = Paragraph(text) doc.add_general_models(["apparatus"], confidence_threshold=0.1, original_text=True) for record in doc.records:     print(record.serialize())
error:
/home/gaoxzh/anaconda3/envs/py39/lib/python3.9/site-packages/torch/cuda/__init__.py:141: UserWarning: CUDA initialization: The NVIDIA driver on your system is too old (found version 9000). Please update your GPU driver by downloading and installing a new version from the URL: http://www.nvidia.com/Download/index.aspx Alternatively, go to: https://pytorch.org to install a PyTorch version that has been compiled with your version of the CUDA driver. (Triggered internally at ../c10/cuda/CUDAFunctions.cpp:108.)   return torch._C._cuda_getDeviceCount() > 0 /home/gaoxzh/anaconda3/envs/py39/lib/python3.9/site-packages/torch/__init__.py:696: UserWarning: torch.set_default_tensor_type() is deprecated as of PyTorch 2.1, please use torch.set_default_dtype() and torch.set_default_device() as alternatives. (Triggered internally at ../torch/csrc/tensor/python_tensor.cpp:451.)   _C._set_default_tensor_type(t) Traceback (most recent call last):   File "/home/gaoxzh/workspace/main.py", line 5, in <module>     for record in doc.records:   File "/home/gaoxzh/anaconda3/envs/py39/lib/python3.9/site-packages/batterydataextractor/doc/text.py", line 334, in records     return ModelList(*[r for sent in self.sentences for r in sent.records])   File "/home/gaoxzh/anaconda3/envs/py39/lib/python3.9/site-packages/batterydataextractor/utils.py", line 26, in fget_memoized     setattr(self, attr_name, fget(self))   File "/home/gaoxzh/anaconda3/envs/py39/lib/python3.9/site-packages/batterydataextractor/doc/text.py", line 228, in sentences     spans = self.sentence_tokenizer.span_tokenize(self.text)   File "/home/gaoxzh/anaconda3/envs/py39/lib/python3.9/site-packages/batterydataextractor/nlp/tokenize.py", line 81, in span_tokenize     self._tokenizer = spacy.load(self.model)   File "/home/gaoxzh/anaconda3/envs/py39/lib/python3.9/site-packages/spacy/__init__.py", line 50, in load     return util.load_model(   File "/home/gaoxzh/anaconda3/envs/py39/lib/python3.9/site-packages/spacy/util.py", line 324, in load_model     return load_model_from_package(name, **kwargs)   File "/home/gaoxzh/anaconda3/envs/py39/lib/python3.9/site-packages/spacy/util.py", line 357, in load_model_from_package     return cls.load(vocab=vocab, disable=disable, exclude=exclude, config=config)   File "/home/gaoxzh/anaconda3/envs/py39/lib/python3.9/site-packages/en_core_sci_sm/__init__.py", line 10, in load     return load_model_from_init_py(__file__, **overrides)   File "/home/gaoxzh/anaconda3/envs/py39/lib/python3.9/site-packages/spacy/util.py", line 517, in load_model_from_init_py     return load_model_from_path(   File "/home/gaoxzh/anaconda3/envs/py39/lib/python3.9/site-packages/spacy/util.py", line 392, in load_model_from_path     nlp = load_model_from_config(config, vocab=vocab, disable=disable, exclude=exclude)   File "/home/gaoxzh/anaconda3/envs/py39/lib/python3.9/site-packages/spacy/util.py", line 429, in load_model_from_config     nlp = lang_cls.from_config(   File "/home/gaoxzh/anaconda3/envs/py39/lib/python3.9/site-packages/spacy/language.py", line 1672, in from_config     nlp.add_pipe(   File "/home/gaoxzh/anaconda3/envs/py39/lib/python3.9/site-packages/spacy/language.py", line 774, in add_pipe     pipe_component = self.create_pipe(   File "/home/gaoxzh/anaconda3/envs/py39/lib/python3.9/site-packages/spacy/language.py", line 660, in create_pipe     resolved = registry.resolve(cfg, validate=validate)   File "/home/gaoxzh/anaconda3/envs/py39/lib/python3.9/site-packages/thinc/config.py", line 746, in resolve     resolved, _ = cls._make(   File "/home/gaoxzh/anaconda3/envs/py39/lib/python3.9/site-packages/thinc/config.py", line 795, in _make     filled, _, resolved = cls._fill(   File "/home/gaoxzh/anaconda3/envs/py39/lib/python3.9/site-packages/thinc/config.py", line 850, in _fill     filled[key], validation[v_key], final[key] = cls._fill(   File "/home/gaoxzh/anaconda3/envs/py39/lib/python3.9/site-packages/thinc/config.py", line 849, in _fill     promise_schema = cls.make_promise_schema(value, resolve=resolve)   File "/home/gaoxzh/anaconda3/envs/py39/lib/python3.9/site-packages/thinc/config.py", line 1057, in make_promise_schema     return create_model("ArgModel", **sig_args)   File "pydantic/main.py", line 990, in pydantic.main.create_model   File "pydantic/main.py", line 299, in pydantic.main.ModelMetaclass.__new__   File "pydantic/fields.py", line 411, in pydantic.fields.ModelField.infer   File "pydantic/fields.py", line 342, in pydantic.fields.ModelField.__init__   File "pydantic/fields.py", line 451, in pydantic.fields.ModelField.prepare   File "pydantic/fields.py", line 550, in pydantic.fields.ModelField._type_analysis   File "/home/gaoxzh/anaconda3/envs/py39/lib/python3.9/typing.py", line 852, in __subclasscheck__     return issubclass(cls, self.__origin__) TypeError: issubclass() arg 1 must be a class


Add new schemas from platform

What are the schemas that are affected by the issue
n/a, only add new schemas
What are examples of products that are impacted by the issue
platform xdm tooling

Can you give a bit more background? What are the schemas that you want to add?

These are newly added schemas from platform PMs since last merge. We need to sync them into the central repo. @cdegroot-adobe
-identity
-namespace
-times
-openinghours
-segment
-store
-propensity

Close for now as this is duplicate.


rolling_update: add any_errors_fatal

If a failure occurs in ceph-validate, the upgrade playbook keeps running
where we expect it to fail.
Signed-off-by: Guillaume Abrioux<EMAIL_ADDRESS>

jenkins test centos-container-update

jenkins test centos-non_container-update


Show only selected keybindings

I really like this package, but I miss some of its functionality. As I have many packages, I have a lot of keybindings and my cheatsheet is very long. And some of them I remember, some of them I don't use. So, I would be glad to be able to choose only subset of keybindings that will be shown on my cheatsheet. Or at least to have an option to show only User keybindings.

I had a similar issue, and I addressed this here https://github.com/jkasky/atom-keybinding-cheatsheet/pull/14.  It is implemented how I wanted it, but hopefully you find it useful.


drivers: adc: stm32: enable channel preselection for stm32u5

In STM32U5 ADC1 PCSEL register must be set before conversion.
Signed-off-by: Wojciech Slenska<EMAIL_ADDRESS>

See https://github.com/zephyrproject-rtos/zephyr/pull/48770

already fixed


Update README.md

Please add this code at the end of the 'Save Palestine' section, just above the picture.
[Don't watch this video!](https://youtu.be/O5fbyEV36pU)

Please assign me this task

@brion4 Issue assigned as requested. Thank you for your willingness to contribute.


[Task] Update the docs thanks to the first onboarding feedbacks

What should be done
In order to make the Lenra onboarding more simple do some changes:

[x] Add style and refactor the Principles page
[x] Make the install page clearer
[x] Change the template description
[ ] translate to french (not enough time)
[x] upgrade CLI and components API versions
[x] syntax colorisation for code

:tada: This issue has been resolved in version 1.0.0-beta.20 :tada:
The release is available on:

GitHub release
v1.0.0-beta.20

Your semantic-release bot :package::rocket:


HTTPd : Being able to navigate through logs from the web interface.

It would be a good thing to be able to visualise logs from the webpages.

Implement by 53e65e5ee268c6ebab7c71188f26536c86014354


Trace user feedback with FastAPI

Hello everyone,
Congratulations on your work, I am in love with Langtrace!
However, I have a problem when I follow the documentation on traceuserfeedback
Is it ready to work with FastAPI? Could the main function be an endpoint? If it is an endpoint, spanId and traceId are input parameters that the client has to fill in, and I think this is not the purpose...
Note: I am working with FastAPI, using @with_langtrace_root_span and inject_additional_attributes.

Hey, I take a look at the package code and I discover that with_langrace_root_span expects span_id and trace_id and not spanId and traceId. So the example works like a churm if you update this.
Please update the documentation.
Thank you very much!

Hey @bukosabino,
Apologies for the confusion and really nice catch!
will definitely update the docs thanks for pointing out.

I have created a pull request: https://github.com/Scale3-Labs/langtrace-docs/pull/45

Thanks @bukosabino for correcting it.


feat: add withMargin prop to Input and DateTime

withMargin is default to true to keep the current behavior intact
withMargin with a false value will add marginless CSS class to
ngx-input and ngx-date-time elements

Summary
Before

After

Checklist

[ ] *Added unit tests
[x] *Added a code reviewer
[x] Added changes to /projects/swimlane/ngx-ui/CHANGELOG.md under HEAD (Unreleased)
[x] Updated the demo page
[x] Included screenshots of visual changes

*required

Not ready

Please hold off on merging


Properly credit me

You may be making the store from Scratch, but the whole idea of a Minecraft 3DS Unistore is from me. This whole Unistore was made to replace mine, so it is based off of it.

You are indeed credited properly, because you discovered the idea of unistore. We won't credit you more, because you dont have any items in our store. I am closing this and please do not open another request.


feat: Add Dependency Control Pattern

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1069  👈
#1068
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @technoplato and the rest of your teammates on  Graphite


pull request for e2e test at 01/03/2017 09:15:18

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Document the Schema

I'd like to document the schema to help myself and other better understand the roles of the tables and various fields.

Sure, go ahead. Such documentation uses the normal Markdown syntax.
Just do as much as you need, and I'll review it or move it to a better place once it's ready.

cool.  I've been doing docfx documents at work and I can contribute them over here as well.

awesome. Then try to get started and ping me if you have it working.
BTW: As of now the docs were still built using Oqtane 1, I haven't been able to build w/v2 because of .net 5 and I'm not sure if this is a general problem, or just something with my PC where I may have misconfigured MSBuild.

Was any progress ever made on this issue? @markdav-is mentioned some documents he had. Were they actually integrated. If there is no objection, I'm willing to work on this issue so that we have the v5 schema documented.

@iJungleboy I believe I resolved the build issue #12 with pull request #15 as I was able to build this project after fixing an issue I had.  However not sure it is the same build issue.  I had 2 successful builds and left it at that after using dotnet tool restore command using terminal in Visual Studio.
I also went ahead and updated the Oqtane 5 information, updated the project to .NET 8 and changed .config json file to latest version of docFX and put out a few other PRs and ideas along the way.
@GregStevenson and @markdav-is it would be nice to see some coordination reviewing and improving docs by submitting pull requests.  Contributing to discussions and issues here would be nice as well by everyone.  The blog has a lot of great helpful information as with all the open and closed Oqtane.Framework discussions, issues and pull requests if browsing around and find some things worthy of including.
I would like to see the structure more presented as shown in issue #16 I created to discuss how I feel we could make a clear path for anyone looking to get somewhere fast with well thought out documentation.  It is just an idea for where to put even more pages as needed to help showcase and explain all parts of the Oqtane Framework worth noting.
I will do my best to contribute a fair share to start with and improve upon down the road for most all these pages/sections.  Combined with what has already been done to get us here and what is being offered by the others in the community we should get a fairly decent documentation solution for Oqtane v5 by next major release.
I am hoping the build issue is resolved with PR #15.  I can submit a PR for what I feel could be an acceptable solution as described in issue #16.  I maybe off in left field here not sure until I get my feet a little more wet helping with this.  Some things I want documented for my own reference later which is my main interest along with helping this community when I can.
Cheers!

Anyone moving forward here?

@markdav-is are you still interested in performing this task?  Or @GregStevenson?  Discord could be used to collaborate potentially if you two can connect on this topic.  I can probably do it eventually if no one gets around to it after I knock out the other issues I created.  It is kind of lonely here ;)

@iJungleboy can close with #91 ?!


fix the release script

platform flag is supplied by hack/release.sh lib
/assign @carlisia

/lgtm
/approve

/cherry-pick release-1.6


RFE - meta modules should be ignored

G'day,
Consider the following:
'''
{-# OPTIONS_HADDOCK hide, prune #-}
module Foo (module X) where
import Foo.Bar as X
import Foo.Zar as X
'''
Haddock throws the following warning:
"Warning: foo-<IP_ADDRESS>:Foo: Could not find documentation for exported module: X"
However, clearly here X is a meta module to make things neat. Could we make Haddock respect this tricky please?
Kind Regards,
Edward O'Callaghan.

This is duplicate of issue #121 so I am closing. It's good to see interest in it however.


Exit codes?

The cli now exits with non-zero when a README or fair badge is missing in README.  To me having no README is not a fatal error it just mean your are non-compliant. Can we check when a non-zero exit is expected?

Related: https://github.com/fair-software/howfairis/issues/47

We only return zero if we have a README with the correct fair-software badge.


FORMAT/DPR has too many values

#247 added FORMAT/DPR fields. However, they should be marked as Number=R (which probably means bumping your output VCF version to 4.2). At the moment it is marked as Number=A and outputting one too many values leading to issues like samtools/bcftools#364.
Alternatively change the annotation to FORMAT/AD which is the same thing (Number=R) but standardised in the spec as of 4.3 to represent per-allele depth.

I guess we should go for v4.3. Heads up @nikete.
On Sat, Apr 2, 2016, 15:39 Shane McCarthy<EMAIL_ADDRESS>wrote:

#247 https://github.com/ekg/freebayes/pull/247 added FORMAT/DPR fields.
However, they should be marked as Number=R (which probably means bumping
your output VCF version to 4.2). At the moment it is marked as Number=A
and outputting one too many values leading to issues like
samtools/bcftools#364 https://github.com/samtools/bcftools/issues/364.
Alternatively change the annotation to FORMAT/AD which is the same thing (
Number=R) but standardised in the spec as of 4.3 to represent per-allele
depth.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/ekg/freebayes/issues/267

Maybe combine with other related things to VCF 4.3 and the output format:

https://github.com/ekg/freebayes/issues/238
https://github.com/ekg/freebayes/issues/244
https://github.com/ekg/freebayes/issues/227
https://github.com/ekg/freebayes/issues/142

@mcshane I think the actual implementation outputs the total depth not the reference allele depth:.  See: https://github.com/ekg/freebayes/blob/3ed4094c278b8f54c97b2071364b5e612df7a8ba/src/ResultData.cpp#L522
Total depth:
sampleOutput["DPR"].push_back(convert(sample.observationCount()));
If it was reference depth:
sampleOutput["DPR"].push_back(convert(sample.observationCount(refbase)));
For me, this is causing bugs in using bcftools view - a - in the BCBIO pipeline, so is a blocking bug.


TPLink Switch component discovery support

Component/platform:
switch/tplink
Description of problem:
The upstream pyHS100 library that this component depends on added a discovery capability about a month ago...  The HA should implement this removing the requirement to specify host addresses.
Additional info:
Example of TPLink switch discovery using pyHS100: https://github.com/GadgetReactor/pyHS100/blob/master/examples/discover.py

Feature requests should go in the forum.


Add Export Command Feature

Export current view of AddressBook into specified filepath with or without password feature
Modify ImportCommand to accept no password argument

Refer to issue #115

Pull Request Test Coverage Report for Build 344

15 of 68 (22.06%) changed or added relevant lines in 9 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.6%) to 85.349%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/seedu/address/model/UserPrefs.java
3
4
75.0%

src/main/java/seedu/address/logic/parser/AddressBookParser.java
0
1
0.0%

src/main/java/seedu/address/model/ModelManager.java
0
5
0.0%

src/main/java/seedu/address/logic/parser/ExportCommandParser.java
0
12
0.0%

src/main/java/seedu/address/storage/XmlAddressBookStorage.java
2
14
14.29%

src/main/java/seedu/address/logic/commands/ExportCommand.java
0
22
0.0%

Totals

Change from base Build 339:
-1.6%

Covered Lines:
2336

Relevant Lines:
2737

💛  - Coveralls


Update CLI extensions available doc

Update CLI extensions available doc.
Triggered by Azure/azure-cli-extensions - TRAVIS_BUILD_ID=626896711
https://github.com/Azure/azure-cli-extensions/commit/bea9d979ecd0eb4ce6058a742669679861e7a774

Docs Build status updates of commit 27b7b73:
:clock10: Full build: the average full build time is 7 min(s) 10 sec(s), this is based on the last 313 build(s) for this repository.

Docs Build status updates of commit 27b7b73:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-extensions-list.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


No documentation or examples for how to override defaults for rules or rule groups

I need to set the capitalisation.keywords rule so that the capitalisation_policy is "upper". This will enforce a rule that keywords are in upper case.
There is no documentation for how to do this in settings.json file. I'm assuming it is in the "sqlfluff.rules": [] section of settings.json. I need to know how to enter json to get the desired behavior.
Please update your documentation to include guidance on how to configure specific rules.

@cvbriggler it is not possible to set that in settings.json. you will have to create a .sqlfluff configuration file to configure specific rules. There is more information about sqlfluff config files on the sqlfluff website

Thanks Robert. I'll take that track. We can close this issue.
On Thu, Mar 21, 2024 at 3:46 PM Robert Ostermann @.***>
wrote:

@cvbriggler https://github.com/cvbriggler it is not possible to set
that in settings.json. you will have to create a .sqlfluff configuration
file to configure specific rules. There is more information about sqlfluff
config files on the sqlfluff website
—
Reply to this email directly, view it on GitHub
https://github.com/sqlfluff/vscode-sqlfluff/issues/131#issuecomment-2013979793,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFQRPZ5WJLJ7T4LPZH6XQ7LYZNPN5AVCNFSM6AAAAABFCKGMS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJTHE3TSNZZGM
.
You are receiving this because you were mentioned.Message ID:
@.***>


Reconsider xDS API lifecycle clock

The move to the v3 APIs has exposed some pain points that control plane authors are facing. It's not cheap to switch major version, in particular when lacking some of the generic API migration tooling that we have developed inside of Envoy.
The existing API lifecycle is described at https://github.com/envoyproxy/envoy/blob/master/api/API_VERSIONING.md. We cut a new major version every year, turn down an old one each year and any major version lives at most 2 years.
This means that any technical debt in API and associated code can live up to 2 years. If we change the clock cycle to every 2 years for a new major version, we might end up having technical debt live 3 or 4 years. This seems pretty significant for a fast moving project like Envoy.
@mattklein123 has proposed that we postpone cutting a new version until we have enough technical debt built up. Arguably we could keep the existing lifecycle with that approach, but instead of cutting a new API exactly every year, we have >= 1 year between major versions and have Envoy maintainers vote on whether to cut a new major version at every quarter after the year mark. This gives us both flexibility in cutting new major versions, potentially longer periods before inflicting cost on control plane authors, stability guarantees to other xDS clients, a predictable deprecation cycle, while leaving technical debt management under the control of maintainers.
This issue can track discussion, will add this to the coming community call agenda.
CC @mattklein123 @envoyproxy/api-shepherds @alyssawilk @markdroth @dfawley

+1 to the sentiment.  Major version bumps in APIs are costly for the entire ecosystem.  If there is a capability to use "experimental" tags to allow new features to be exempted from backward compatibility guarantees, then you should almost never need to release a new major version.
You call Envoy "fast moving", yet it has been GA for 3.5 years and is used by many major companies for critical services - at what point will it be considered "mature", and plan for no major version bumps?

I'm also in favor of not imposing the overhead of a major version bump without compelling justification.  It's become clear that this change is extremely expensive.
I agree with @dfawley that in principle, we should never need to bump the major version number to add new features, because new features can instead be triggered by client capabilities.  So it seems like the only reason we would ever have to bump the major version would be to eliminate deprecated fields, so that management servers can stop supporting old fields.  And for that, we could just wait until enough deprecated fields have built up that it makes sense to get rid of a whole bunch of them at a time.
@ejona86 may also have thoughts here.

I'm also in favor of not imposing the overhead of a major version bump without compelling justification.  It's become clear that this change is extremely expensive.
I agree with @dfawley that in principle, we should never need to bump the major version number to add new features, because new features can instead be triggered by client capabilities.  So it seems like the only reason we would ever have to bump the major version would be to eliminate deprecated fields, so that management servers can stop supporting old fields.  And for that, we could just wait until enough deprecated fields have built up that it makes sense to get rid of a whole bunch of them at a time.
@ejona86 may also have thoughts here.

I'm also in favor of not imposing the overhead of a major version bump without compelling justification.  It's become clear that this change is extremely expensive.
I agree with @dfawley that in principle, we should never need to bump the major version number to add new features, because new features can instead be triggered by client capabilities.  So it seems like the only reason we would ever have to bump the major version would be to eliminate deprecated fields, so that management servers can stop supporting old fields.  And for that, we could just wait until enough deprecated fields have built up that it makes sense to get rid of a whole bunch of them at a time.
@ejona86 may also have thoughts here.

I'm also in favor of not imposing the overhead of a major version bump without compelling justification. It's become clear that this change is extremely expensive.

Agreed, though I think at this point we should agree as a community to push through with v2 -> v3 since we don't know what we don't know until we do it once, and arguably the longer we wait to try this the more painful it will get.

And for that, we could just wait until enough deprecated fields have built up that it makes sense to get rid of a whole bunch of them at a time.

+1 this is my thinking as well.

I'm not convinced that it actually makes sense to go through with the v2 -> v3 migration right now.  I agree that we would learn something from the exercise, but until we actually need to bump the version for some reason, it seems like this is an awful lot of work just to gain theoretical knowledge.  It seems better to wait until we actually need to make the change, because then it will be much easier to devote the resources to make it happen.

I'm not convinced that it actually makes sense to go through with the v2 -> v3 migration right now.

If this is an opinion held by many I think we need to urgently discuss this as a lot of plans would need to change and be communicated.

(Also note that if we abandon the v3 force upgrade we need to actually go back and backfill recent API changes that have been v3 only, so again this needs urgent attention if there is going to be a change here in the PR)

@markdroth are you talking about for gRPC or Envoy? I think it wold be a major disruption to back out from v3 now in Envoy, since:

The ecosystem is in the process of moving to v3.
Envoy has internally migrated to v3, any v2 config needs to be converted first to v3.
We risk losing credibility when stating plans around APIs.
We abandon the v3 migration, process and tooling put in place for major version bumps. We have to start this all again at some point in the future once these have rotted and the community has lost the ability to deal with major version changes.

This should be tempered with the real cost of the v3 migration, but I think this is the wrong point in an API major version shift to be debating this. Ideally this happens at the start.

I agree that there are a lot of implications here and that we need to resolve this quickly, and I'm not dead-set against continuing the migration to v3.  We'll have some offline discussions and try to come to consensus on this.


Question about default source camera and the render camera setting.

I noticed that only when source camera following the setting that azimuth=270, elevation=0, the triplane would render the same image as input under input pose.
My question is, when I have a image under pose $T_0$, and I want to render a image under pose $T_1$. How should I adjust the render camera?
I've tried to get the ref_pose $T_2 =  T_dT_0^{-1}$ where $T_d$ is the default pose, and convert $T_1$ with ref_pose, but it totally gives an wrong image.
In my setting, the camera distance is 1.5, and the input azimuth is 2.3562(rad), elevation is -0.1317(rad)
the target azimuth is 0, elevation is 0.52359878.
The input image

And the target image

Both two image are rendered by blender.

I have the same problem. Have you solved it yet?


Make an uninstall process to restore previous environment

I remember seeing that beakerx installed some things in jupyter's folder. After doing some tests, I would like to uninstall it, but I didn't find any references to how to delete those files.
I realized that pip uninstall beakerx is not enough, because it left some config files behind, making old jupyter notebook broken.
After removing both .jupyter and .ipython config folders, I managed to get a cleaner error output.
$ jupyter notebook
[W 18:50:10.914 NotebookApp] Error loading server extension beakerx
    Traceback (most recent call last):
      File "python_path/lib/python3.6/site-packages/notebook/notebookapp.py", line 1343, in init_server_extensions
        mod = importlib.import_module(modulename)
      File "python_path/lib/python3.6/importlib/__init__.py", line 126, in import_module
        return _bootstrap._gcd_import(name[level:], package, level)
      File "<frozen importlib._bootstrap>", line 978, in _gcd_import
      File "<frozen importlib._bootstrap>", line 961, in _find_and_load
      File "<frozen importlib._bootstrap>", line 948, in _find_and_load_unlocked
    ModuleNotFoundError: No module named 'beakerx'
[I 18:50:10.937 NotebookApp] [jupyter_nbextensions_configurator] enabled 0.2.8
[I 18:50:10.997 NotebookApp] Serving notebooks from local directory: /home/paulo/Documents/work/scorer-svc
[I 18:50:10.997 NotebookApp] 0 active kernels
[I 18:50:10.997 NotebookApp] The Jupyter Notebook is running at:
[I 18:50:10.997 NotebookApp] http://localhost:8888/?token=4261729b3fb906e6e2d70259a809e4429646eec24e031792
[I 18:50:10.997 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
[C 18:50:10.999 NotebookApp]

    Copy/paste this URL into your browser when you connect for the first time,
    to login with a token:
        http://localhost:8888/?token=4261729b3fb906e6e2d70259a809e4429646eec24e031792
[I 18:50:12.073 NotebookApp] Accepting one-time-token-authenticated connection from <IP_ADDRESS>
[14437:14477:0115/185012.104051:ERROR:browser_gpu_channel_host_factory.cc(107)] Failed to launch GPU process.
Created new window in existing browser session.
[W 18:50:13.006 NotebookApp] 404 GET /nbextensions/beakerx/tree.js (<IP_ADDRESS>) 10.89ms referer=http://localhost:8888/tree

Running jupyter notebook --debug, I could manage to backtrack the following config files:

python_env_path/etc/{jupyter,ipython}
python_env_path/share/jupyter/kernels/{groovy,clojure,sql,scala,java,kotlin}
python_env_path/share/jupyter/nbextensions/beakerx

As I had no previous configuration in them, I deleted all of them and then I got my Jupyter again.

I had very frustrating experience with uninstalling beakerx. What helped, was to remove the file /usr/etc/ipython/ipython_config.py .  Nothing from above helped. I wrote this, in case someone has similar  troubles.

Hi sorry it gave you trouble.
Can you say how you installed it, how you uninstalled it and what error did you get?

I'm getting the following error when I try to install packages with pip after installing beakerx. The command beakerx-install --disable is not recognized. How can I make this error go away?
FileNotFoundError: [Errno 2] No such file or directory: '/anaconda3/lib/python3.6/site-packages/beakerx-1.4.1.dist-info/METADATA'


fix indents

see diff

Thanks! Could you create the PR onto the develop branch (the guides are under docs/guides/?

#201


Implement GET /channels/{id}/pins

This endpoint is not yet implemented - currently the only way of getting pinned messages is checking the messages individually for the IsPinned property, so only works for messages that have been downloaded/cached.

Pull request got merged, so I'll close this


Programmable/Advanced Surveys [Tower]

Proposal:
Allow the user to create advanced surveys in Tower with an 'Advanced' option, that when run can facilitate the construction of complicated blocks of variables at run time. Right now, you can only use the survey for basic variables at runtime. The advanced survey should allow for:

basic variables
dictionaries of variables
dictionaries of dictionaries of variables
lists of dictionaries

And so on.
Something along these lines:
config:
  EU:
    DC:
      FR4:
        SC0102:
          - agent:
            vlan:
          - agent:
            vlan:
        SC0304:
      LD5:
        SC0102:
        SC0304:
  US:
    DC:
      LA2:
        SC0102:
        SC0304:
      NY1:
        SC0102:
        SC0304:

This can be achieved by allowing the engineer to assign a survey question to a block of variable text that they specify when constructing the survey in the EDIT SURVEY option.
You could also allow a survey to pull file names from specific directories to auto-fill the available options. Hence why it should be programmable. The possibilities are endless.
Author: ilyashusain IRC: handle (if different)
Date: 2020-09-26

Status: New
Proposal type: Ansible Tower
Targeted release: future release
Associated PR: n/a
Estimated time to implement: 20 days

Motivation
This will be extremely useful to many organizations.
Problems
What problems exist that this proposal will solve?

Problem #1
Makes the end users experience a lot more streamlined in that they do not need to modify code in git/another scm for a task and then refresh the tower project to sync the git repo, and then run the template... this is quite tedious. They can instead construct that code at runtime by means of a survey by directly running the template.

Problem #2
Current survey is too basic.

Or just describe the problem if there is just one.
n/a.

Solution proposal

Describe your suggested solution here.
Flexibility here. Up to you how you want to achieve this.

Insert code in snippets if you would like as shown.
n/a.

Be sure to explain how this solves problems.
See '### Problems' above.

Dependencies (optional)
Explain any dependencies. This section is optional but could be helpful.

Dependency #1
n/a.
Dependency #2
n/a.

Testing (optional)
Does / should this require testing, and if so, how? Describe here. This section is optional but could be helpful.
n/a.
Documentation (optional)
Does / should this require documentation? If so, describe here. This section is optional but could be helpful.
n/a.
Anything else?
More attention needs to be directed towards the survey feature.

This is for 'proposals' issue queue is for Ansible itself, not awx/tower, that has it's own location for enhancements/proposals
Also, there is already an RFE that covers this https://github.com/ansible/awx/issues/20


fix(API): assign contribution_id is of type ContributionId

Codecov Report

Merging #142 (accaf9f) into main (2631805) will increase coverage by 0.34%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##             main     #142      +/-   ##
==========================================
+ Coverage   55.25%   55.59%   +0.34%
==========================================
  Files          73       78       +5
  Lines        1933     2018      +85
==========================================
+ Hits         1068     1122      +54
- Misses        865      896      +31

Impacted Files
Coverage Δ

src/domain/entities/contribution.rs
100.00% <ø> (ø)

...e/domain_implementations/application/repository.rs
0.00% <0.00%> (ø)

...ructure/database/domain_implementations/project.rs
0.00% <ø> (ø)

src/infrastructure/starknet/model.rs
100.00% <ø> (ø)

src/routes/dto/hex_prefixed_string/tests.rs
100.00% <ø> (ø)

src/routes/dto/uuid.rs
100.00% <ø> (ø)

src/routes/dto/u256/mod.rs
33.33% <33.33%> (ø)

src/dto/u256.rs
58.33% <58.33%> (ø)

src/domain/entities/application.rs
85.71% <66.66%> (+73.21%)
:arrow_up:

src/routes/dto/hex_prefixed_string/mod.rs
32.25% <66.66%> (-20.25%)
:arrow_down:

... and 11 more

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


syntax highlight messed up after a point

reduced from /Users/timothee/git_clone/nim/Nim/lib/pure/hashes.nim
proc hashData() =
  when false:
    asm """`baz`;"""

proc hash(): Hash =
  when false:
    asm """
    """
  else:
    result = 0

proc foo() = discard

I am not sure I understand... nimline does not provide syntax highlighting or multi line editing... did you mean to open this on another project?

sorry!! confused it with nimlime again... ; moved to https://github.com/Varriount/NimLime/issues/104


Manually added users to hub.jupytearth.org

For convenience in the short term while the automation and such to manage users via GitHub is setup, I suggest students and instructors are added via https://hub.jupytearth.org/hub/admin but also that any such manual addition of users is documented here.
When documenting it here, clarify username, full name, and if the user is a student, instructor, or something else. I'm providing the template below that can be copy-pasted into a comment.
I've added users manually at https://hub.jupytearth.org/hub/admin and here maintain a list of those that I've added in this comment that I'll update over time.

GitHub username | Full name | Role
-|-|-
username1 | Alice Bobsson | Instructor

I've added users manually at https://hub.jupytearth.org/hub/admin and here maintain a list of those that I've added in this comment that I'll update over time.

GitHub username
Full name
Role

lcgasque
Claire Gasque
Instructor

Excellent, thanks @abbyazari and @consideRatio!

I've added users manually at https://hub.jupytearth.org/hub/admin and here maintain a list of those that I've added in this comment that I'll update over time.
GitHub username | Full name | Role | Comment
-|-|-
ian-r-rose | Ian Rose | dask-labextension developer | Added for helping out in https://github.com/dask/dask-labextension/issues/203#issuecomment-888177777.

As this thread seems inactive, what do you think if we move the documentation elsewhere, remove the personal information, and close this issue @consideRatio ?

Yes it's inactive. We can remove user names and details or move privately. Fine on my end.

We haven't kept track of our user list overall, but i think it was great that you kept track of the larger group of temporary accounts to be added/removed @abbyazari! Thank you!
If we are to add a group of temporary accounts again, I suggest we do the same.


How to make a snapshot of the screen?

I would like to use the snapshot-functionality to capture all screens during test, but it is unclear what I should do besides installing this npm-package.
Any recommendations?

according to puppeteer exposeFunction doc
you can call the exposed functions directly in .spec file, something like:
  describe('Login Process', () => {
    ...

    afterEach(() => {
      window['capturePage']('login step')
    })
  })


Xcode Firebase "library not loaded" -- Crash running Simulator

Description
My app crashes trying to run in Xcode's Simulator. The error says basically:
dyld[70392]: Library not loaded  @rpath/GTMSessionFetcher.framework/GTMSessionFetcher, but goes on to complain that  "file does not start with MH_MAGIC[_64], fat file, but missing compatible architecture (have 'i386,x86_64,arm64', need 'arm64')"
I posted a Stack Overflow question first: https://stackoverflow.com/questions/78293837/xcode-firebase-library-not-loaded-problem-running-simulator
I am mystified by this: "file does not start with MH_MAGIC[_64], fat file, but missing compatible architecture ..."
I am trying to build on a new M3 (Apple silicon) machine. Had problems so just removed the frameworks, according to the Readme.md, and started new. I had commented out all the Firebase code too, except for one line, to get things going. Builds ok, but running with the Simulator crashes and produces this (below) in the console. It's an older Objective-C app and cannot generate an empty OBJC app anymore with Xcode so couldn't reduce this down to a simple reproducible app.
dyld[70392]: Library not loaded: @rpath/GTMSessionFetcher.framework/GTMSessionFetcher
  Referenced from: <FFFF9F7B-88DA-3D82-B1CA-419DB7B97C71> /Users/newm3laptop/Library/Developer/CoreSimulator/Devices/C6358852-2298-4226-8839-F15331073CD2/data/Containers/Bundle/Application/F3C202F4-900E-4214-A3E1-F922CB071CA9/ASSIST for iPad.app/ASSIST for iPad
  Reason: tried: '/Users/newm3laptop/Documents/iOS_Projects/ASSIST-main/assist_ios/DerivedData/ASSIST for iPad/Build/Products/Debug-iphonesimulator/GTMSessionFetcher.framework/GTMSessionFetcher' (file does not start with MH_MAGIC[_64], file does not start with MH_MAGIC[_64], file does not start with MH_MAGIC[_64], fat file, but missing compatible architecture (have 'i386,x86_64,arm64', need 'arm64')), '/Library/Developer/CoreSimulator/Volumes/iOS_21E213/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 17.4.simruntime/Contents/Resources/RuntimeRoot/usr/lib/swift/GTMSessionFetcher.framework/GTMSessionFetcher' (no such file), '/usr/lib/swift/GTMSessionFetcher.framework/GTMSessionFetcher' (no such file, not in dyld cache), '/Users/newm3laptop/Library/Developer/CoreSimulator/Devices/C6358852-2298-4226-8839-F15331073CD2/data/Containers/Bundle/Application/F3C202F4-900E-4214-A3E1-F922CB071CA9/ASSIST for iPad.app/Frameworks/GTMSessionFetcher.framework/GTMSessionFetcher' (file does not start with MH_MAGIC[_64], file does not start with MH_MAGIC[_64], file does not start with MH_MAGIC[_64], fat file, but missing compatible architecture (have 'i386,x86_64,arm64', need 'arm64')), '/Users/newm3laptop/Library/Developer/CoreSimulator/Devices/C6358852-2298-4226-8839-F15331073CD2/data/Containers/Bundle/Application/F3C202F4-900E-4214-A3E1-F922CB071CA9/ASSIST for iPad.app/Frameworks/GTMSessionFetcher.framework/GTMSessionFetcher' (file does not start with MH_MAGIC[_64], file does not start with MH_MAGIC[_64], file does not start with MH_MAGIC[_64], fat file, but missing compatible architecture (have 'i386,x86_64,arm64', need 'arm64')), '/Library/Developer/CoreSimulator/Volumes/iOS_21E213/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 17.4.simruntime/Contents/Resources/RuntimeRoot/usr/lib/swift/GTMSessionFetcher.framework/GTMSessionFetcher' (no such file), '/usr/lib/swift/GTMSessionFetcher.framework/GTMSessionFetcher' (no such file, not in dyld cache), '/Users/newm3laptop/Library/Developer/CoreSimulator/Devices/C6358852-2298-4226-8839-F15331073CD2/data/Containers/Bundle/Application/F3C202F4-900E-4214-A3E1-F922CB071CA9/ASSIST for iPad.app/Frameworks/GTMSessionFetcher.framework/GTMSessionFetcher' (file does not start with MH_MAGIC[_64], file does not start with MH_MAGIC[_64], file does not start with MH_MAGIC[_64], fat file, but missing compatible architecture (have 'i386,x86_64,arm64', need 'arm64')), '/Users/newm3laptop/Library/Developer/CoreSimulator/Devices/C6358852-2298-4226-8839-F15331073CD2/data/Containers/Bundle/Application/F3C202F4-900E-4214-A3E1-F922CB071CA9/ASSIST for iPad.app/Frameworks/GTMSessionFetcher.framework/GTMSessionFetcher' (file does not start with MH_MAGIC[_64], file does not start with MH_MAGIC[_64], file does not start with MH_MAGIC[_64], fat file, but missing compatible architecture (have 'i386,x86_64,arm64', need 'arm64')), '/Library/Developer/CoreSimulator/Volumes/iOS_21E213/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 17.4.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/GTMSessionFetcher.framework/GTMSessionFetcher' (no such file)
Logging Error: Failed to initialize logging system. Log messages may be missing. If this issue persists, try setting IDEPreferLogStreaming=YES in the active scheme actions environment variables.

Reproducing the issue
The only way I know to reproduce this now is with my app. :(
Firebase SDK Version
8.15
Xcode Version
15.3
Installation Method
Zip
Firebase Product(s)
Authentication, Database
Targeted Platforms
iOS
Relevant Log Output
dyld[70392]: Library not loaded: @rpath/GTMSessionFetcher.framework/GTMSessionFetcher
  Referenced from: <FFFF9F7B-88DA-3D82-B1CA-419DB7B97C71> /Users/newm3laptop/Library/Developer/CoreSimulator/Devices/C6358852-2298-4226-8839-F15331073CD2/data/Containers/Bundle/Application/F3C202F4-900E-4214-A3E1-F922CB071CA9/ASSIST for iPad.app/ASSIST for iPad
  Reason: tried: '/Users/newm3laptop/Documents/iOS_Projects/ASSIST-main/assist_ios/DerivedData/ASSIST for iPad/Build/Products/Debug-iphonesimulator/GTMSessionFetcher.framework/GTMSessionFetcher' (file does not start with MH_MAGIC[_64], file does not start with MH_MAGIC[_64], file does not start with MH_MAGIC[_64], fat file, but missing compatible architecture (have 'i386,x86_64,arm64', need 'arm64')), '/Library/Developer/CoreSimulator/Volumes/iOS_21E213/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 17.4.simruntime/Contents/Resources/RuntimeRoot/usr/lib/swift/GTMSessionFetcher.framework/GTMSessionFetcher' (no such file), '/usr/lib/swift/GTMSessionFetcher.framework/GTMSessionFetcher' (no such file, not in dyld cache), '/Users/newm3laptop/Library/Developer/CoreSimulator/Devices/C6358852-2298-4226-8839-F15331073CD2/data/Containers/Bundle/Application/F3C202F4-900E-4214-A3E1-F922CB071CA9/ASSIST for iPad.app/Frameworks/GTMSessionFetcher.framework/GTMSessionFetcher' (file does not start with MH_MAGIC[_64], file does not start with MH_MAGIC[_64], file does not start with MH_MAGIC[_64], fat file, but missing compatible architecture (have 'i386,x86_64,arm64', need 'arm64')), '/Users/newm3laptop/Library/Developer/CoreSimulator/Devices/C6358852-2298-4226-8839-F15331073CD2/data/Containers/Bundle/Application/F3C202F4-900E-4214-A3E1-F922CB071CA9/ASSIST for iPad.app/Frameworks/GTMSessionFetcher.framework/GTMSessionFetcher' (file does not start with MH_MAGIC[_64], file does not start with MH_MAGIC[_64], file does not start with MH_MAGIC[_64], fat file, but missing compatible architecture (have 'i386,x86_64,arm64', need 'arm64')), '/Library/Developer/CoreSimulator/Volumes/iOS_21E213/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 17.4.simruntime/Contents/Resources/RuntimeRoot/usr/lib/swift/GTMSessionFetcher.framework/GTMSessionFetcher' (no such file), '/usr/lib/swift/GTMSessionFetcher.framework/GTMSessionFetcher' (no such file, not in dyld cache), '/Users/newm3laptop/Library/Developer/CoreSimulator/Devices/C6358852-2298-4226-8839-F15331073CD2/data/Containers/Bundle/Application/F3C202F4-900E-4214-A3E1-F922CB071CA9/ASSIST for iPad.app/Frameworks/GTMSessionFetcher.framework/GTMSessionFetcher' (file does not start with MH_MAGIC[_64], file does not start with MH_MAGIC[_64], file does not start with MH_MAGIC[_64], fat file, but missing compatible architecture (have 'i386,x86_64,arm64', need 'arm64')), '/Users/newm3laptop/Library/Developer/CoreSimulator/Devices/C6358852-2298-4226-8839-F15331073CD2/data/Containers/Bundle/Application/F3C202F4-900E-4214-A3E1-F922CB071CA9/ASSIST for iPad.app/Frameworks/GTMSessionFetcher.framework/GTMSessionFetcher' (file does not start with MH_MAGIC[_64], file does not start with MH_MAGIC[_64], file does not start with MH_MAGIC[_64], fat file, but missing compatible architecture (have 'i386,x86_64,arm64', need 'arm64')), '/Library/Developer/CoreSimulator/Volumes/iOS_21E213/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 17.4.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/GTMSessionFetcher.framework/GTMSessionFetcher' (no such file)
Logging Error: Failed to initialize logging system. Log messages may be missing. If this issue persists, try setting IDEPreferLogStreaming=YES in the active scheme actions environment variables.

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

Thanks

Hi @SergiusPaulus, does updating the SDK version makes any difference?

@rizafran Thanks.  I was finally able to get things going by removing all the frameworks and using cocoapods.  I can try to do that if you think it will be useful to anyone reading this ticket. I wonder though if it makes sense to spend any more time on this. Your thoughts?

No need. The most likely explanation is trying to link with a version built before Arm simulators were supported.


Feature Request: Collapsible PowerShell Regions

VSCode Version: 1.10
OS Version: Win10

Regions currently cannot be collapsed in PowerShell scripts, this is available in PowerShell ISE currently.

My mistake!


The parameter can't have a value of 'null' because of its type

Following the instructions on https://flutter.dev/docs/development/ui/interactive , I have tried setting up the GestureDectector example.  I keep getting the following error, even though the code is the same.

My Flutter is 2.2.0-10.1.pre
Dart Version: Dart 2.13.0

https://stackoverflow.com/questions/64560461/the-parameter-cant-have-a-value-of-null-because-of-its-type-in-dart#:~:text=The reason this happens is,calculate() or Foo() .

Hi @JamesVanWaza
Thanks for filling the issue, the code needs an update on the website, please file an issue flutter/website.
Meanwhile, you can make it nullable to get rid of the error
Closing as this is related to the website. If you disagree, please write in the comments and I will reopen it.
Thank you


Project Settings, OS, and String, not respecting OS path conventions correctly

Godot version:

3.2 Stable
OS/device including version:

Win 10
Issue description:

extends PanelContainer
"""
	FileBrowser Scene Script
"""

const STORY_FILE_PATH_INTERNAL: String = "res:/Game/Stories/"
var STORY_FILE_PATH_EXTERNAL: String = ""

func _init() -> void:
	var ex: String = OS.get_executable_path()
	ex = ex.get_base_dir()
	STORY_FILE_PATH_EXTERNAL = ex.plus_file("Game").plus_file("Stories")
	print(STORY_FILE_PATH_EXTERNAL)

	var a = ProjectSettings.globalize_path("res://").plus_file("Game").plus_file("Stories")
	print(a)

Shitty example from a live project of mine, testing this. Print output:
D:\SoftwarePortable\Godot_v3.2-stable_win64.exe/Game/Stories
D:/Projects/NEMETON/Nemeton/Game/Stories

Of course, Windows is nice enough not to care about which type of slash you use. But that is not given behavior.
It also seems that this inconsistency causes get_base_dir() to fail with paths returned by the OS singleton.
Steps to reproduce:
Minimal reproduction project:

AFAIK Godot only works with / paths for consistency, and corrects them automatically for Windows. In that case, I'd say the unexpected behaviour is actually get_base_dir returning paths with \.


SourceKitLSP: add new dependency introduced in SwiftSyntax

Add a dependency on IDEUtils that is missing in the build.

Please test with following PRs:
apple/swift-syntax#1029
@swift-ci please test


CVEs in 0.10.7 image

Hi,
The following CVEs exist 0.10.7 image.  Can you please patch them?

GHSA-4xcv-9jjx-gfj3
MEDIUM
mem-1.1.0
1.1.0
4.0.0

CVE-2024-3651
MEDIUM
idna-3.6
3.6
3.7

CVE-2024-28085
MEDIUM
bsdutils,libblkid1,libblkid-dev,libmount1,libmount-dev,libsmartcols1,libuuid1,mount,util-linux,util-linux-extra,uuid-dev
2.38.1-5+b1
2.38.1-5+deb12u1

CVE-2024-21503
MEDIUM
black-23.12.0
23.12.0
24.3.0

GHSA-g95f-p29q-9xw4
LOW
braces-1.8.5
1.8.5
2.3.1

Could you upgrade the dependencies with poetry and submit a pull-request?

Hi, can I have permission to do the PR?
`[devenvx2] ~/s/celery-exporter ❯❯❯ git push --set-upstream origin patching-cves                                         ✘ 128 patching-cves
ERROR: Permission to danihodovic/celery-exporter.git denied to ryanh-orca.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
[devenvx2] ~/s/celery-exporter ❯❯❯`

You will have to fork the repository and submit a PR.
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request

https://github.com/danihodovic/celery-exporter/pull/311
I can't upgrade mem and braces packages for https://github.com/advisories/GHSA-4xcv-9jjx-gfj3 and https://github.com/advisories/GHSA-g95f-p29q-9xw4. Hitting "Because prometheus-exporter-celery depends on mem (^4.0.0) which doesn't match any versions, version solving failed."
Can you please help to patch these 2 packages?

Where are you getting the list of CVEs from?
I've merged your PR and made another batch of dependency updates in #312. I've released it as v0.10.8

The dockerfile doesn't have any Nodejs process in it. It seems like it's copied from my local machine. I can remove it from the image, but I don't think there is any security problem present.

Can you please remove them? We really appreciate it.

Is it to check the box for your vulnerability software or is this an actual vulnerability?

If this package is installed as it's shown in the package-lock.json, then it is an actual vulnerability.

The package is never installed. There is node Nodejs process in the image. https://github.com/danihodovic/celery-exporter/blob/master/Dockerfile

Thanks for the confirmation. We will mark it as FP in our scanner.

The package.json and package-lock.json will be removed from the Docker image in the next release, but I'm too lazy to make a release now when no code has been merged since the last release.


Sharded multiresolution meshes index file size error

Hi @jbms ,
I'm currently trying to implement sharded multi level meshes.
As per the documentation, I have added fragment data first and then appended the manifest data next and then compute shards from there on. However, when I try to see them in neuroglancer I get an error  in the developer tools like
Error retrieving chunk 200: Error: Invalid index file size for<PHONE_NUMBER> lods: 35636

I think I'm making a simple mistake in offsets here, can you please help out.
I have attached the sharded multilevel mesh here
The unsharded multilevel implementation that works fine is attached here

Some additional details:
The sample code that I use was adapted from here #272
# start with some settings..
    quantization_bits = quant_bits
    lods = np.array([0, 1, 2])  # number of level of details, keep 3 for now..
    # set the chunk shape, grid origin acc to vertex data, so there is no need for offsets later on..
    chunk_shape = (vertices.max(axis=0) - vertices.min(axis=0))/2**lods.max()
    grid_origin = vertices.min(axis=0)
    lod_scales = np.array([2**lod for lod in lods])
    num_lods = len(lod_scales)
    vertex_offsets = np.array([[0., 0., 0.] for _ in range(num_lods)])

    fragment_offsets = []
    fragment_positions = []

    fragmentdata = BytesIO()

    # write the mesh fragment data file first..
    # for each level now decompose the mesh into submeshes with lower resolution..
    for scale in lod_scales[::-1]:
        # start with lod-0, which is the highest resolution possible..
        lod_offsets = []
        nodes, submeshes = decompose_meshes(vertices.copy(), faces.copy(), scale, quantization_bits)
        # convert each submesh into google draco format and append them..
        for mesh in submeshes:
            draco = trimesh.exchange.ply.export_draco(mesh, bits=quant_bits)
            fragmentdata.write(draco)
            lod_offsets.append(len(draco))

        fragment_positions.append(np.array(nodes))
        fragment_offsets.append(np.array(lod_offsets))

    num_fragments_per_lod = np.array([len(nodes) for nodes in fragment_positions])

    offsetvalue = len(fragmentdata.getvalue())

    # write the mesh manifest file now..
    fragmentdata.write(chunk_shape.astype('<f').tobytes())
    fragmentdata.write(grid_origin.astype('<f').tobytes())
    fragmentdata.write(struct.pack('<I', num_lods))
    fragmentdata.write(lod_scales.astype('<f').tobytes())
    fragmentdata.write(vertex_offsets.astype('<f').tobytes(order='C'))
    fragmentdata.write(num_fragments_per_lod.astype('<I').tobytes())
    for frag_pos, frag_offset in zip(fragment_positions, fragment_offsets):
        fragmentdata.write(frag_pos.T.astype('<I').tobytes(order='C'))
        fragmentdata.write(frag_offset.astype('<I').tobytes(order='C'))

after this, I make shards, minishards using the data in fragmentdata

If it helps, here was my attempt: https://github.com/davidackerman/multiresolutionMeshes.

I haven't had chance to debug this in detail, but since you say that the unsharded multi-level meshes work, then it sounds like the problem is surely in the conversion from non-sharded format to sharded format, for which you haven't included your code.  I'd recommend modifying your generation code to output the relevant offsets, and then checking the Range headers in chrome dev tools network tab to see which byte ranges Neuroglancer requests, and compare to the expected byte ranges, so that you can see where it is going wrong.


Issue with  in multi level route

When using a route like /about or / or /contact - the page renders just find using bootstrap. However, when using a multi-level route like /projects/photos - bootstrap fails to render.
Upon using the browser inspection tool (right click --> inspect in chrome) it shows that there are no errors for a single level route (/about).  But for a multi level route there is an error and it highlights the '<' of the  line.

the way I am doing the routes is:
Flight::route('*', array('Layout', 'buildLayout'));
class Layout{
    public static function buildLayout(){
      //> script / css includes
      Flight::render('head', array('whatis' => 'stuff inside head tag'), 'head_content');

      //> build nav bar
      Flight::render('nav', array('site_name' => 'Bootstrap Template'), 'nav_content');

      //> build page Data
      Flight::render('page', array('whatis' => 'dynamic page content'), 'page_content');

      //> build full layout
      Flight::render('layout', array('show_footer' => 'yes'));
    }
  }

Does anyone have any thoughts as to what I may be doing wrong?

It sounds like you are including the Bootstrap CSS file with a relative path instead of an absolute one. Can you show the HTML you're using to include the CSS?

I am including it as a relative path to the index.php file.

<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1,chrome=1">

<link rel="stylesheet" href="./framework/css/bootstrap.min.css" type="text/css">
<link rel="stylesheet" href="./framework/css/bootstrap-theme.min.css" type="text/css">
<link rel="stylesheet" href="./framework/css/source-code-pro.css" type="text/css">
<link rel="stylesheet" href="./framework/css/style.css" type="text/css">

// this code renders that head content in the layout
//> script / css includes
Flight::render('head', array('whatis' => 'stuff inside head tag'), 'head_content');

//>Layout.php
<!DOCTYPE html>

    //> data from the head.php file
    <?php echo $head_content; ?>
    <title>Bootstrap Template</title>

    <?php echo $nav_content; ?>

      <?php echo $page_content; ?>

    <?php if($show_footer == "yes"){?>

© <?php echo date("Y") . " " . $site_name; ?>

    <?php } ?>

Axe the dots and use the absolute path, I imagine that will resolve the issue. The web browser is looking for domain.com/framework/ when you're loading "single level routes" like domain.com/foo and domain.com/bar but when you're loading up a "multi level route" like domain.com/foo/bar it's looking for domain.com/foo/framework which doesn't exist.

gave that a shot and it still wasn't working
<link rel="stylesheet" href="framework/css/bootstrap.min.css" type="text/css">
<link rel="stylesheet" href="framework/css/bootstrap-theme.min.css" type="text/css">
<link rel="stylesheet" href="framework/css/source-code-pro.css" type="text/css">
<link rel="stylesheet" href="framework/css/style.css" type="text/css">

even tried:
<link rel="stylesheet" href="/framework/css/bootstrap.min.css" type="text/css">
<link rel="stylesheet" href="/framework/css/bootstrap-theme.min.css" type="text/css">
<link rel="stylesheet" href="/framework/css/source-code-pro.css" type="text/css">
<link rel="stylesheet" href="/framework/css/style.css" type="text/css">

could it be the fact that I am developing locally on my machine using MAMP instead of on an actual web server?

If you right click the background and go "View page source", when you click on those links, do they load? It's a quick way to see if you're including them correctly, and also to see which URL it brings you to when you do click them (where it thinks they should be).

I think you're onto something. When I click the link for style.css it doesn't load it reverts back to the page but the url becomes:
http://localhost/bootstrap_template/**projects**/framework/css/style.css
it is looking in the /projects folder for the framework folder. So it does appear to be something path related.
could it be something with the way I set the route up?
  Flight::route('*', array('Layout', 'buildLayout'));

What does your .htaccess file look like?
If you're using one that looks similar to this:

RewriteEngine On
RewriteBase /
RedirectMatch 301 ^(.+)/$ $1
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule . /index.php [L]

The rewrite condition states that if the requested URL does not point to a file it knows exists (for example, your CSS files), to forward the request to Flight. So, Flight should not be handling anything to do with your includes. It's a pathing issue, you need to specify the full absolute path to your CSS files. I don't know the folder structure you have setup, or if you're working in a subdirectory, etc... but that is the issue (or you need to fix your .htaccess file to include the rewrite condition).

here is my .htaccess:

RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php [QSA,L]

here is my folder structure:

Let me know if this works:
<link rel="stylesheet" href="/bootstrap_template/framework/css/bootstrap.min.css" type="text/css">
<link rel="stylesheet" href="/bootstrap_template/framework/css/bootstrap-theme.min.css" type="text/css">
<link rel="stylesheet" href="/bootstrap_template/framework/css/source-code-pro.css" type="text/css">
<link rel="stylesheet" href="/bootstrap_template/framework/css/style.css" type="text/css">

Yup that works!

So you're technically working out of a subdirectory. MAMP is running and looking at your root directory as whatever folder bootstrap_template is residing in. So the absolute path has to include the subdirectory you're running the project out of (bootstrap_template).
If you're only working on one project it might be easier to move it all up a directory outside of that bootstrap_template folder.
On any note, glad it's working for you - happy coding!

Yup that is exactly right - So i will need to figure out a way to create the subdir path and set it to a variable. Nonetheless, thank you again.


[Feature]: Support flashdecoding++ heuristic dataflow and profiling optimization

Q3 Collaboration Plan of Infra and IaaS Labs: https://bytedance.us.larkoffice.com/docx/HKXfdRh1noMrbAxcgL2ureGasdQ

FlashDecoding++ Summary: https://bytedance.larkoffice.com/wiki/WbqXwRL3qi0x18kJVkAcU0HZnte, including Asynchronized Softmax, Double Buffering, Heuristic Dataflow, and more profiling-related optimizations.

The new kv cache memory layout and performance benchmarks is also needed.

Inference Improvement Weekly Status and Progress: https://bytedance.us.larkoffice.com/docx/RGnPdj5gfoBN3YxuY3yuLtlQsjb

Profling heuristic dataflow: https://github.com/vllm-project/vllm/blob/df845b2b46c3e30f5bd3e3be286285ed148323fc/vllm/worker/worker.py#L248

Implemented the flat gemm and support heuristic dataflow with small batch decoding using flat gemm.

https://code.byted.org/inf/dAttention/merge_requests/18 Code merged.


chore: add infrastructure for Grit engine

Summary
This PR implements the basic infrastructure on top of which to implement the bindings for the Grit engine. All implementations are merely todo!() so far, so this doesn't really do anything, but it gives an idea where the work will happen :)
Lays the foundation for work on https://github.com/biomejs/biome/issues/2582.
Note the Grit crate dependencies still point to my own fork, since the PR hasn't been merged yet. I'll wait with merging this one until the upstream PR is merged first.
Test Plan
Everything should stay green.

Looks like we cannot rely on the repository directly if we want things to build on Windows :sweat_smile:
Caused by:
  failed to load source for dependency `grit-core-patterns`

Caused by:
  Unable to update https://github.com/arendjr/gritql.git?branch=grit-core-patterns-crate#327c1489

Caused by:
  path too long: 'C:/Users/runneradmin/.cargo/git/checkouts/gritql-696dcc358c4a514c/327c148/resources/language-metavariables/tree-sitter-typescript/node_modules/tree-sitter-javascript/build/Release/.deps/Release/obj.target/tree_sitter_javascript_binding/bindings/node/


Add requestOptions to customize Tika server request

Closes #217. Instead of just adding a timeout I added the ability to pass any additional params to the requests call in case others might be required.

Coverage increased (+0.6%) to 42.88% when pulling e71c2b1194fa658d09b16674da885938fa29bd93 on sheldonreiff:feature/request-options into 32082696c822eb0d9e999b425626da434e7b30cf on chrismattmann:master.

thanks this PR rules!


Fatal Python error: Illegal instruction when running on MacOS

Hi, I am using CTransformers with LangChain to perform inference on Llama 2 (https://huggingface.co/TheBloke/Llama-2-7B-Chat-GGML)
When running tests on GitHub Actions it works on Linux and Windows, but not MacOS, giving the error:
Fatal Python error: Illegal instruction

Current thread 0x0000000101bf8600 (most recent call first):
  File "python3.11/site-packages/ctransformers/llm.py", line 207 in __init__
  File "python3.11/site-packages/ctransformers/hub.py", line 157 in from_pretrained
  File "python3.11/site-packages/langchain/llms/ctransformers.py", line 73 in validate_environment

Which seems to be when CTransformers create the LLM: https://github.com/marella/ctransformers/blob/main/ctransformers/llm.py#L207
     self._llm = self._lib.ctransformers_llm_create(
            model_path.encode(),
            model_type.encode(),
            config.context_length,
            config.gpu_layers,
        )

Workflow run failing: https://github.com/vemonet/libre-chat/actions/runs/5694749918/job/15436518518
Any idea why this fails only on Mac? Is it due to the file I downloaded? Wrong format, wrong encoding? Because it seems like ctransformers is tested successfully on MacOS using GitHub Action, so the environment should not be the problem

Hi, looks like this run was from a week ago and using an older version of ctransformers, so if you update to latest version it should work.
In older versions of ctransformers, AVX2 instructions were used by default but GitHub Actions for macOS run on old CPU which don't support them and causing this error. In my workflow I exclude AVX2 for macOS. So in older versions the fix was to pass lib="avx" to tell it to not use AVX2.
In recent versions (0.2.17 or newer) it automatically selects AVX2/AVX based on CPU.

Hi @marella , thanks for the quick answer, indeed I just ran it too soon. It works without issue with >=0.2.17
Thanks a lot for the great work!


Can't connect to API with python3.5 / openssl 1.1

Required information

Distribution: Debian
Distribution version: 9.12

config:
  core.https_address: <IP_ADDRESS>:8443
  core.trust_password: true
api_extensions:
- storage_zfs_remove_snapshots
- container_host_shutdown_timeout
- container_stop_priority
- container_syscall_filtering
- auth_pki
- container_last_used_at
- etag
- patch
- usb_devices
- https_allowed_credentials
- image_compression_algorithm
- directory_manipulation
- container_cpu_time
- storage_zfs_use_refquota
- storage_lvm_mount_options
- network
- profile_usedby
- container_push
- container_exec_recording
- certificate_update
- container_exec_signal_handling
- gpu_devices
- container_image_properties
- migration_progress
- id_map
- network_firewall_filtering
- network_routes
- storage
- file_delete
- file_append
- network_dhcp_expiry
- storage_lvm_vg_rename
- storage_lvm_thinpool_rename
- network_vlan                                                                                [146/13830]
- image_create_aliases
- container_stateless_copy
- container_only_migration
- storage_zfs_clone_copy
- unix_device_rename
- storage_lvm_use_thinpool
- storage_rsync_bwlimit
- network_vxlan_interface
- storage_btrfs_mount_options
- entity_description
- image_force_refresh
- storage_lvm_lv_resizing
- id_map_base
- file_symlinks
- container_push_target
- network_vlan_physical
- storage_images_delete
- container_edit_metadata
- container_snapshot_stateful_migration
- storage_driver_ceph
- storage_ceph_user_name
- resource_limits
- storage_volatile_initial_source
- storage_ceph_force_osd_reuse
- storage_block_filesystem_btrfs
- resources
- kernel_limits
- storage_api_volume_rename
- macaroon_authentication
- network_sriov
- console
- restrict_devlxd
- migration_pre_copy
- infiniband
- maas_network
- devlxd_events
- proxy
- network_dhcp_gateway
- file_get_symlink
- network_leases
- unix_device_hotplug
- storage_api_local_volume_handling
- operation_description
- clustering
- event_lifecycle
- storage_api_remote_volume_handling
- nvidia_runtime
- container_mount_propagation
- container_backup
- devlxd_images
- container_local_cross_pool_handling
- proxy_unix
- proxy_udp
- clustering_join
- proxy_tcp_udp_multi_port_handling
- network_state
- proxy_unix_dac_properties
- container_protection_delete
- unix_priv_drop
- pprof_http
- proxy_haproxy_protocol
- network_hwaddr
- proxy_nat
- network_nat_order
- container_full
- candid_authentication
- backup_compression
- candid_config
- nvidia_runtime_config
- storage_api_volume_snapshots
- storage_unmapped
- projects
- candid_config_key
- network_vxlan_ttl
- container_incremental_copy
- usb_optional_vendorid                                                                                [70/13830]
- snapshot_scheduling
- container_copy_project
- clustering_server_address
- clustering_image_replication
- container_protection_shift
- snapshot_expiry
- container_backup_override_pool
- snapshot_expiry_creation
- network_leases_location
- resources_cpu_socket
- resources_gpu
- resources_numa
- kernel_features
- id_map_current
- event_location
- storage_api_remote_volume_snapshots
- network_nat_address
- container_nic_routes
- rbac
- cluster_internal_copy
- seccomp_notify
- lxc_features
- container_nic_ipvlan
- network_vlan_sriov
- storage_cephfs
- container_nic_ipfilter
- resources_v2
- container_exec_user_group_cwd
- container_syscall_intercept
- container_disk_shift
- storage_shifted
- resources_infiniband
- daemon_storage
- instances
- image_types
- resources_disk_sata
- clustering_roles
- images_expiry
- resources_network_firmware
- backup_compression_algorithm
- ceph_data_pool_name
- container_syscall_intercept_mount
- compression_squashfs
- container_raw_mount
- container_nic_routed
- container_syscall_intercept_mount_fuse
- container_disk_ceph
- virtual-machines
- image_profiles
- clustering_architecture
- resources_disk_id
- storage_lvm_stripes
- vm_boot_priority
- unix_hotplug_devices
- api_filtering
- instance_nic_network
- clustering_sizing
- firewall_driver
- projects_limits
- container_syscall_intercept_hugetlbfs
- limits_hugepages
- container_nic_routed_gateway
- projects_restrictions
- custom_volume_snapshot_expiry
- volume_snapshot_scheduling
- trust_ca_certificates
- snapshot_disk_usage
- clustering_edit_roles
- container_nic_routed_host_address
- container_nic_ipvlan_gateway
- resources_usb_pci
- resources_cpu_threads_numa
- resources_cpu_core_die
- api_os
- container_nic_routed_host_table
- container_nic_ipvlan_host_table
- container_nic_ipvlan_mode
- resources_system
- images_push_relay
- network_dns_search
- container_nic_routed_limits
- instance_nic_bridged_vlan
- network_state_bond_bridge
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
- tls
environment:
  addresses:
  - <IP_ADDRESS>:8443
  architectures:
  - x86_64
  - i686
  certificate: |
    -----BEGIN CERTIFICATE-----
    MIICEDCCAZWgAwIBAgIQDQoPS6wCnbRDTTa4i81/YDAKBggqhkjOPQQDAzA4MRww
    GgYDVQQKExNsaW51eGNvbnRhaW5lcnMub3JnMRgwFgYDVQQDDA9yb290QHdlYmNv
    bkZpcmUwHhcNMjAwNjEzMTgyODE4WhcNMzAwNjExMTgyODE4WjA4MRwwGgYDVQQK
    ExNsaW51eGNvbnRhaW5lcnMub3JnMRgwFgYDVQQDDA9yb290QHdlYmNvbkZpcmUw
    djAQBgcqhkjOPQIBBgUrgQQAIgNiAATOQMmcLb0RhQFomfP6WAK5cBuSR2x51kqt
    2nKXjNQpBvFuHMgcbgKr6ewisjUVD/r6s+8W48m1AsyAmOLHBWtxsxyYjyVk9uXb
    Hp3pBXM3kmVSySQRzocY4TAzMRpd3bijZDBiMA4GA1UdDwEB/wQEAwIFoDATBgNV
    HSUEDDAKBggrBgEFBQcDATAMBgNVHRMBAf8EAjAAMC0GA1UdEQQmMCSCCndlYmNv
    bkZpcmWHBH8AAAGHEAAAAAAAAAAAAAAAAAAAAAEwCgYIKoZIzj0EAwMDaQAwZgIx
    ALPPXrI0JXY2w2adDDtSapnDDM+/Ovh2one/YObGnqIwOfH3+V8faLRaiIBFg+ny
    AAIxALjstUKjJXV+eyPRLMev8tAw3sU/qnJvqxT3kqTqlKKdSkus3f8oHaRhyNFb
    y0+vdw==
    -----END CERTIFICATE-----
  certificate_fingerprint: 3b16c0a9b94cd442711b7077166bc75ec65f2248a692105ae96154e05f65655a
  driver: lxc
  driver_version: 4.0.2
  firewall: xtables
  kernel: Linux
  kernel_architecture: x86_64
  kernel_features:
    netnsid_getifaddrs: "false"
    seccomp_listener: "false"
    seccomp_listener_continue: "false"
    shiftfs: "false"
    uevent_injection: "false"
    unpriv_fscaps: "false"
  kernel_version: 4.9.0-12-amd64
  lxc_features:
    cgroup2: "true"
    mount_injection_file: "true"
    network_gateway_device_route: "true"
    network_ipvlan: "true"
    network_l2proxy: "true"
    network_phys_macvlan_mtu: "true"
    network_veth_router: "true"
    pidfd: "true"
    seccomp_notify: "true"
  os_name: Debian GNU/Linux
  os_version: "9"
  project: default
  server: lxd
  server_clustered: false
  server_name: X
  server_pid: 20945
  server_version: "4.2"
  storage: btrfs
  storage_version: 4.15.1

Issue description
Tried using pylxd on a fresh Debian 9.12 install. Authentication of new key fails because no connection can be opened to the API: https://github.com/lxc/pylxd/issues/403
Steps to reproduce

Install debian 9.12
install lxd from snap
Try to authenticate according to https://pylxd.readthedocs.io/en/latest/authentication.html

Information to attach
According to testssl, only ECDHE_ECDSA_* ciphers are supported:
 Testing all 143 locally available ciphers against the server, ordered by encryption strength

Hexcode  Cipher Suite Name (OpenSSL)       KeyExch.  Encryption Bits
------------------------------------------------------------------------
 xc02c   ECDHE-ECDSA-AES256-GCM-SHA384     ECDH 253   AESGCM    256
 xc00a   ECDHE-ECDSA-AES256-SHA            ECDH 253   AES       256
 xc02b   ECDHE-ECDSA-AES128-GCM-SHA256     ECDH 253   AESGCM    128
 xc009   ECDHE-ECDSA-AES128-SHA            ECDH 253   AES       128

I think this is because of the cipher list in https://github.com/lxc/lxd/blob/bc9af2a6adef1f01fc4f60dfcbce4ee87d8bdeb0/lxd-agent/network.go#L65 but I only took a cursory glance at the code.

LXD allows:
			tls.TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
			tls.TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,
			tls.TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
			tls.TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,
			tls.TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
			tls.TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,
			tls.TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
			tls.TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,

We don't have any plans to allow anything else at this point.

Right, but TLS_ECDHE_RSA_* isn't actually enabled for some reason.

Our policy is to not allow unsafe versions of TLS or ciphers which do not provide forward secrecy.
Ideally we'd also drop the AES_128 ciphers so we don't allow anything below 256 but that has the annoying side effect of disabling HTTP/2 which some of our clients can benefit right now. We're hoping that things will change a bit on that side so we can further restrict the list of ciphers.
As for your problem, the best would be for your distro to fix the python3/openssl interaction which is causing your cipher list to be that limited. If that's not possible, you may be able to cheat by using something like haproxy/nginx/netcat/... to get from LXD's strict TLS to an insecure TLS that you'd expose only on localhost (and so avoid most issues from it).
I suppose you could maybe even use something like socat to forward from TLS to a plain unix socket that you can connect to as if it was /var/snap/lxd/common/lxd/unix.socket.

Hmm, so pylxd not working on 3.7 (or advertised to not be working) sounds like a separate problem and something that the pylxd team certainly should be addressing.

(All of this should only ever be an issue if connecting to LXD over the network. If you're connecting through the local unix socket, TLS isn't used so none of this would be a problem.)

I'm not sure I understand why ciphers such as DHE-RSA-AES256-GCM-SHA384 are supposed to be insecure. Sure, EC ciphers might be faster, but I don't see the problem with allowing non-EC ciphers if they are secure.
However, regarding you second comment, I actually wasn't aware that pylxd also uses the sockets since I took the authenticate snippet from the linked page. If I just remove the endpoint parameter, it works as expected, so I guess the issue is "worked around" in my case.


ci: Cancel previous workflows on the same ref

Cancel previous workflows if they are the same workflow on the same ref (branch/tags)
with the same event (push/pull_request) even if they are in progress.
This setting will help reduce the number of duplicated workflows.
Fix #664
Signed-off-by: Xuanwo<EMAIL_ADDRESS>

Oh, my IDE cleaned all space in workflow files too. Although they are not intended to be changed in this PR but seem cool?

I think remove those unintended spaces is good even didn't relate to current topic.

Is there a way to exclude manually retried workflows?
I think the user might not want to pause the current workflow while retrying some workflow.

Github doesn't support retry workflow (entirely or partly) without canceling the current workflow.
I guess what you mean is retry some jobs in the workflow. Retry failed jobs will work as expected without breaking already succeeded jobs.

Thanks. Actually what I want to say is a special case:
In PR a:

commit 1 first ci run failed, manual retry running
commit 2 running

But I think maybe this is very rare, so it is not something this PR needs to consider.

commit 1 first ci run failed, manual retry running
commit 2 running

It doesn't make sense to me to retry a previous workflow after new commits have been pushed. Canceling them is a good choice for me.

It doesn't make sense to me to retry a previous workflow after new commits have been pushed. Canceling them is a good choice for me.

Yeah, I agree that in most cases just running the last commit is good.


[Android] [Teams] Button is not rendered properly when relative width is specified in the Column.

Target Platform

iOS
Android

Target Application
Host - Teams Mobile
Problem Description
Button is not rendered properly when relative width is specified in the column for the card given below. It is working fine in Desktop.
I have done some initial analysis in Android. In the below payload, it has a root ColumnSet which has two Columns with equal widths (50% & 50%). Inside the second Column (50% width), another ColumnSet is defined which again has two Columns. The first Column contains Input.Date field which takes up 75% width and the second Column contains Button field which takes up 25% width.
On the whole, the button only getting around 14% width of the entire row's total width. Android button's has minimum width defined and has some padding as well. So, the 14% width is not enough for the button and it is getting cut-off on the right.
I guess, the button has to goto the second row if there isn't any space available.
Screenshot

Card JSON
{
  "type": "AdaptiveCard",
  "body": [
	{
	  "color": null,
	  "horizontalAlignment": null,
	  "isSubtle": false,
	  "maxLines": 0,
	  "size": "large",
	  "text": "Time off balance(s)",
	  "weight": "bolder",
	  "wrap": false,
	  "separator": false,
	  "type": "TextBlock"
	},
	{
	  "columns": [
		{
		  "width": "stretch",
		  "items": [
			{
			  "color": null,
			  "horizontalAlignment": null,
			  "isSubtle": false,
			  "maxLines": 0,
			  "size": "medium",
			  "text": "View your balance(s) as of:",
			  "weight": "bolder",
			  "wrap": false,
			  "separator": false,
			  "type": "TextBlock"
			}
		  ],
		  "separator": false,
		  "type": "Column"
		},
		{
		  "width": "stretch",
		  "items": [
			{
			  "columns": [
				{
				  "width": "75",
				  "items": [
					{
					  "value": "",
					  "isRequired": false,
					  "id": "date",
					  "spacing": "default",
					  "separator": false,
					  "type": "Input.Date"
					}
				  ],
				  "separator": false,
				  "type": "Column"
				},
				{
				  "width": "25",
				  "items": [
					{
					  "actions": [
						{
						  "data": {
							"nwCommand": "ASSISTANT_TIME_OFF_BALANCE"
						  },
						  "title": "Update",
						  "type": "Action.Submit"
						}
					  ],
					  "separator": false,
					  "type": "ActionSet"
					}
				  ],
				  "separator": false,
				  "type": "Column"
				}
			  ],
			  "separator": false,
			  "type": "ColumnSet"
			}
		  ],
		  "separator": false,
		  "type": "Column"
		}
	  ],
	  "separator": false,
	  "type": "ColumnSet"
	},
	{
	  "color": null,
	  "horizontalAlignment": null,
	  "isSubtle": false,
	  "maxLines": 0,
	  "size": null,
	  "text": " ",
	  "weight": null,
	  "wrap": false,
	  "separator": true,
	  "type": "TextBlock"
	},
	{
	  "color": null,
	  "horizontalAlignment": null,
	  "isSubtle": false,
	  "maxLines": 0,
	  "size": null,
	  "text": "As of today, these are your available balances:   \n   \n* Floating Holiday (Floating Holiday (Hours), Paid Time Off Adjustment (Hours)): **0.0 Hours**   \n   \n* Paid Time Off (Paid Time Off Adjustment (Hours), Sick (Hours), Vacation Sell, Vacation (Hours)): **-13.22 Hours**   \n   \nThe following requested and approved time off has not been subtracted from your available balances:   \n   \n**Vacation (Hours):**   \nAug 2–3, 2021 (16 Hours - Submitted)   \n   \n**Paid Time Off Adjustment (Hours):**   \nAug 24, 2021 (8 Hours - Submitted)   \nAug 26, 2021 (8 Hours - Submitted)   \nAug 30, 2021 (8 Hours - Submitted)   \n   \nYou can also view your balance for a future date or request time off.",
	  "weight": null,
	  "wrap": true,
	  "separator": false,
	  "type": "TextBlock"
	}
  ],
  "actions": [
	{
	  "data": {
		"nwCommand": "TEAMS_NOOP_MODAL_CLOSE_COMMAND"
	  },
	  "title": "Close",
	  "type": "Action.Submit"
	}
  ],
  "version": "1.2"
}

Sample Code
Tested it on the sample app in the SDK.
Version of SDK
latest main.

hi @karthikgopal36 - based on your ask, in order to get the button on the next line it would need to be removed from the ColumnSet. The Card is being rendered correctly based on the JSON you provided...you can achieve the result you want by moving the Action.Submit button outside of the ColumnSet


python311Packages.hap-python: 4.7.1 -> 4.8.0

Diff: https://github.com/ikalchev/HAP-python/compare/refs/tags/4.7.1...4.8.0
Changelog: https://github.com/ikalchev/HAP-python/blob/4.8.0/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 259448 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.homekit
python310Packages.hap-python
python310Packages.hap-python.dist
python311Packages.hap-python
python311Packages.hap-python.dist


Update lsa-lookup-performance-counters.md

adding minor edit to trigger co-author update.

#sign-off

LGTM merging now.