Provide single hash and pip insall fails

export command provides single hash for yamllint
yamllint==1.28.0 ; python_version >= "3.10" and python_version < "4.0" \
    --hash=sha256:9e3d8ddd16d0583214c5fdffe806c9344086721f107435f68bad990e5a88826b

And pip fails
poetry export -f requirements.txt --with dev | poetry run -- pip install -r /dev/stdin

Please always fill out the bug report, so we can avoid asking a million questions.
Please always use text in bug reports, it makes things much easier to read.
The hash is correct for the source tarball, not for the wheel.

Thank you,
But poetry creates multiple hashes for other packages.
For example
django==4.1.4 ; python_version >= "3.11" and python_version < "4.0" \
    --hash=sha256:0b223bfa55511f950ff741983d408d78d772351284c75e9f77d2b830b6b4d148 \
    --hash=sha256:d38a4e108d2386cb9637da66a82dc8d0733caede4c83c4afdbda78af4214211b
yamllint==1.28.0 ; python_version >= "3.11" and python_version < "4.0" \
    --hash=sha256:9e3d8ddd16d0583214c5fdffe806c9344086721f107435f68bad990e5a88826b

It can be seen wheel hash for Django but It does not provide for yamllint.
https://pypi.org/project/Django/#files
I think, it's about, yamllint supports py2
https://pypi.org/project/yamllint/#files

the yamllint bdist was published a month or so after the sdist, probably you have a stale cache that knows about one but not the other.
Clear your cache, re-lock, try again

I tried but nothing changed

Then you either didn't clear your cache, or didn't re-lock.  Poetry simply does not behave in the way that you are claiming.
If I am wrong then a great way to progress this would be for you to provide a dockerfile that reproduces the behaviour you are seeing

I think you are right.
# https://medium.com/swlh/alpine-slim-stretch-buster-jessie-bullseye-bookworm-what-are-the-differences-in-docker-62171ed4531d
# Choose one of these images if your code is compatible with a specific version of the Debian operating system.

FROM python:3.10.7-slim-buster

ENV PYTHONFAULTHANDLER=1 \
  PYTHONUNBUFFERED=1 \
  PYTHONHASHSEED=random \
  PYTHONDONTWRITEBYTECODE=1 \
  # pip:
  PIP_NO_CACHE_DIR=off \
  PIP_DISABLE_PIP_VERSION_CHECK=on \
  PIP_DEFAULT_TIMEOUT=100 \
  # poetry:
  POETRY_VERSION=1.2.2 \
  POETRY_NO_INTERACTION=1 \
  POETRY_VIRTUALENVS_CREATE=false \
  POETRY_CACHE_DIR='/var/cache/pypoetry' \
  POETRY_HOME='/usr/local'

RUN apt-get update && apt-get upgrade -y \
  && apt-get install --no-install-recommends -y \
  curl \
  # Installing `poetry` package manager:
  # https://github.com/python-poetry/poetry
  && curl -sSL 'https://install.python-poetry.org' | python - \
  && poetry --version

# set a directory for the APP
WORKDIR /app

COPY . /app

RUN poetry export -f requirements.txt | poetry run -- pip install -r /dev/stdin

It works.


It folds anything that is similar to class=""

Let's say I've a variable in js in a vue file
const test_class="Test"

This extension also folds the text inside the quotes.
And becomes like this
const test_class="..."

Hello @RifatMahmudno-1,
Sorry for late response and thanks for pointing that out. I will try fixing this issue. It's worth pointing out that it is considered best practice to have spaces around your infix operators. Both eslint and prettier can help reinforce this behaviour.
// Albin


Fix wrong URL to the OpenStack metadata service

Thank you for contributing to MidoNet! MidoNet uses Gerrithub for code review. Please visit http://wiki.midonet.org/How to contribute and follow the instructions there to upload your change to Gerrithub.

@berendt, thanks for your pull request.
I took your patch and uploaded it to GerritHub: https://review.gerrithub.io/254482


TypeScript server log contains PII and source code

have a tsserver.log file and have the goal of filing an issue
take a look at the file
🐛 file is full of file paths and even source code

We should clearly warn about this before encouraging people to attach that file to an (public) issue.

Yes this is a known concern with both the typescript log and the trace.
Is your suggestion to have better in-product documentation to make this clearer, and/or that we better document this when asking people for the log/trace in github issues?

I added a note on this to the two settings with 1d05d0c. For example:

Enables tracing of messages sent to the TS server. This trace can be used to diagnose TS Server issues. The trace may contain file paths, source code, and other potentially sensitive information from your project.

Let me know if anyone has any suggestions to improve the wording here
We should add a note on this in Github issues too whenever asking for the tsserver trace or log so that people know what they are sharing publicly. They could also send us these files over email instead of uploading them on issues

I like. Thanks


Disable browser autocomplete on autosuggest component

Browser autocomplete is currently appearing at the same time as suggestions in the autosuggest component. After discussion in the 2023/07/12 Paragon WG meeting, it has been decided a good path forward is to disable the browser autocomplete for this component.

Closing this as it will be completed as part of #2435


Update dependencies & enforce consistent formating

fixes #36

Update front end dependencies
Fix front end to work with latest libs
apply consistent code formating
update .gitignore (build assets should not be included in git repo)

Hi,
anyone maintaining this repo?

Hi,
anyone maintaining this repo?

Apparently dead


[feat] Add GitHub Integration System with Event Mapping and Configuration UI

Walkthrough of creating a GitHub integration settings system
https://github.com/user-attachments/assets/916d0bd1-3b46-4193-a82f-f50f5493a424
Walkthrough of integration between GitHub and Giselle
https://github.com/user-attachments/assets/8bdf7451-bf43-4fe3-8e94-92054218e588
Changes

Implement GitHub webhook handler for issue comment processing
Create GitHub integration settings system with improved schema
Add comprehensive event-to-node mapping UI with data assignment capabilities
Build reusable UI components:

New Radix UI-based Select component
Enhanced Block component with hover card support
Improved Popover component

Add repository configuration and event trigger settings
Implement GitHub API client with app authentication
Add data mapping interface for GitHub event data

Database Changes

Added new githubIntegrationSettings table
Deprecated old github_integrations table
Added migration for new table structure

i'll check ci

@satococoa I would like to request a code review for the initial implementation of the GitHub integration that you worked on. 🔍

I did bun drizzle-kit migrate! 🚀


Henry working

Updated make_area function and added an automated_baseline function. I have 2 additional automated baseline algorithms that can be implemented as well.
I am still pretty unfamiliar with git but it says I made many more changes than I did. I only made additions to the spectra.py file and nothing else.

Hey, I'm about to:

Add some small updates from my version that I think will help Anna out with her new issue.
Issue a new release with only those updates, so that'll be pynams version 0.2.0
Make all my olivine code, which uses pynams v0.2.0, public.
Test and merge this pull request.

Hey @whtowbin - I looked at it a little bit. The updates to make_area and documentation look reasonable, but why not just include your automated baselines as options in make_baseline? That way you don't have to keep track of two different functions. I leave it to you and Anna to decide what you want the default to be.
Also, I think it will be a huge help if you could also update EXAMPLES.ipynb to include the new options and defaults for both baselines and areas.
As you're doing this - don't worry too much about legacy support for me. My paper will use v0.2.0, and going forward, you and Anna should make this the best thing you can for yourselves and others.

And don't worry about the conflicts between .pyc files. I think I know how to sort that out when it's all ready to merge.

Thank you for the updates! I agree that is might be easier to just have one baseline function with several options. I left it separate for the time being because I actually have several other types of automated baseline and I was considering if there was a way to role them all into one. The current routine is good for most situations but sometimes conflicts with an automated peak fitting routine I have been working on.
For now it might be best to keep them separate until I figure out how best to sort them out.
I am happy to make examples. I will try to do it in the next few weeks.
Thanks again,
Henry

An automated peak fitting routine! Whoa! That's like the holy grail of pynams. You should check out the open source Matlab program (Google peakfit.m, I think) if you haven't already. There are a couple of commercial programs out there as well - I think one I've read about, maybe in one of Jannick Ingrin's olivine papers, is called PeakFit. I'm all about open-source, but if the existing pynams setup isn't good enough, it might not be worth a lot of your time if you can just buy something satisfactory for maybe not that much money.
I will wait to merge everything into master until you've sorted out what exactly you want to do and added examples (but Anna or whoever can still get the version from your branch if they want it), so just let me know when you want me to look at it again.

Thanks for the tips. I started working on it for my quantitative data analysis class. So far its slow but works well for fitting highly overlapping peaks after you roughly identify the peaks you want to fit in one spectra. It uses Montecarlo methods to sample peak heights and widths and then makes error estimates based on a likelihood function.
At the moment the choice of baseline has a huge effect in my profiles where the baseline varies a lot from spectra to spectra in a profile. This might not be a problem for more straight-forward baselines. After I am done with my master's paper I should try it out on San Carlos.
My ultimate goal is to sample baselines in the Monte Carlo method so thats why I have come up with multiple automated baseline methods.

Super interesting. I look forward to seeing what you come up with.


Known information regarding Swift support

When I try to run the example project, using Swift, the only thing that shows up is the input bar. When inspecting the UI there isn't a table added. Is that happening to you? If so, I'd like to help track down the issue. Know anything worth pointing out?

Right on. I didn't see that!
Tried it out and ran into the issue that I had with the collection view in my project (just using a basic flow layout).  For some reason it doesn't get initialized so we crash out in viewDidLoad. It's not immediately clear where in the the path it is failing.
Comment out those two lines in viewDidLoad and there is an interesting situation when it all loads (2 table views):

I'll try to dig into this more here in a bit.

Excellent!


Add default response case transformation

Hi
It would be nice to allow setting a default casing for response payloads, even without the client setting the accent header.
In my situation I'd like to always send all responses as camelcase

I could see adding a default_case option to Accent.Plug.Response.
Feel free to submit a PR.

Ill try to get around to it next week

#3

Closing due to inactivity.


Attempt remove depends

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@manthey, it seems we have to install setuptools because of: https://github.com/DigitalSlideArchive/tifftools/blob/c2db6409e909fd27bc3746bf0abacda236c42a08/tifftools/init.py#L3
import: 'tifftools'
Traceback (most recent call last):
  File "/home/conda/feedstock_root/build_artifacts/tifftools_1639078131380/test_tmp/run_test.py", line 2, in <module>
    import tifftools
  File "/home/conda/feedstock_root/build_artifacts/tifftools_1639078131380/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeh/lib/python3.10/site-packages/tifftools/__init__.py", line 3, in <module>
    from pkg_resources import get_distribution
ModuleNotFoundError: No module named 'pkg_resources'


Uploading to Thumbor

Not an issue, nor a feature request.  Wanted to start a discussion about this and wasn't sure the best way to go about it.
Anyways, I am trying to get us to adopt Thumbor at my job to replace the archaic gem we use in our rails stack.
To get rid of this gem, I really want thumbor to accept image uploads and be responsible for persisting the image.
The behavior I want is something like:

I do a PUT to a thumbor server (this service would be listening on a different port than the public facing service
The uploader would be configured to use the storage engines.  In my case, i created an S3 storage engine, and would use this to asynchronously upload the file to the URL, but also would use the redis engine to cache it.
It puts it in redis and asynchronously uploads to the S3 bucket that maps to the image

What this means is: I can do a request immediately to thumbor for the S3 URL before it has finished uploading to S3.  Thumbor also becomes responsible for doing the async upload which Tornado is much better at doing than anything in ruby is.
The branch I have in progress is here: https://github.com/mikelikespie/thumbor/tree/uploader
For S3 uploads it may be better to use something similar to the loaders which have async callback.  In this case I don't really care too much because I want the uploading to happen in the background.
Any thoughts?  Could this be something that is useful upstream?
Thanks,
Mike

Not really Mike...
Thumbor is not meant to replace your original images farm. It is A LOT of
work to think of all the possible scenarios for an image upload farm (we at
globo.com cannot do the way you are doing for instance). That's why we use
custom loaders. So people can adapt thumbor to their own image farms.
Let's see what people think of it. I might be wrong and we might still opt
to incorporate it.
Thanks A LOT for the interest anyways.
Cheers,
Bernardo Heynemann
On Fri, Jan 13, 2012 at 5:10 PM, Mike Lewis <
<EMAIL_ADDRESS>
wrote:

Not an issue, nor a feature request.  Wanted to start a discussion about
this and wasn't sure the best way to go about it.
Anyways, I am trying to get us to adopt Thumbor at my job to replace the
archaic gem we use in our rails stack.
To get rid of this gem, I really want thumbor to accept image uploads and
be responsible for persisting the image.
The behavior I want is something like:

I do a PUT to a thumbor server (this service would be listening on a
different port than the public facing service
The uploader would be configured to use the storage engines.  In my
case, i created an S3 storage engine, and would use this to asynchronously
upload the file to the URL, but also would use the redis engine to cache it.
It puts it in redis and asynchronously uploads to the S3 bucket that
maps to the image

What this means is: I can do a request immediately to thumbor for the S3
URL before it has finished uploading to S3.  Thumbor also becomes
responsible for doing the async upload which Tornado is much better at
doing than anything in ruby is.
The branch I have in progress is here:
https://github.com/mikelikespie/thumbor/tree/uploader
For S3 uploads it may be better to use something similar to the loaders
which have async callback.  In this case I don't really care too much
because I want the uploading to happen in the background.
Any thoughts?  Could this be something that is useful upstream?
Thanks,
Mike

Reply to this email directly or view it on GitHub:
https://github.com/globocom/thumbor/issues/59

I suppose I could spin it off into a separate service.  I want to reuse the same configuration logic as well as the storage engines... which I could just import in a separate server.
I was hoping that reusing the existing the storage engines would make it generally useful.
Let's take S3 out of the picture for a sec, and assume the loaders had a dump method (symmetrical to the load method).  For the file one, it would just write to disk.  For the HTTP one, it would probably do a PUT.
For my S3 use case, I would just make a loader similar to the HTTP one that did a PUT with the configured credentials.
Now, for the PUT service, it would be mostly symmetrical to how thumbor does it's image fetching, except that it would populate the redis cache immediately and then do the loader's put operation (probably asynchronously).
Like I mentioned, before, this would be an internal API.
I agree that it's probably not useful for everybody, however.

Hey man,
We (the team) were thinking on your idea and we think it is a nice addition to thumbor. Do you think you can try and implement it?
I was thinking something like a /upload route for it, and calling the put method of the storages.
I'll try to implement it anyways later if you can't.
Cheers,

Awesome!
I started going down implementing it as a separate service (although it could definitely be rolled into thumbor core).
https://github.com/mikelikespie/thumbor-dumper
Basically I added the concept of remote storages.  I implemented an HTTP one that can do a PUT, and then subclassed it to support S3.
The work I started to do with adding it into the core can be found here:
https://github.com/mikelikespie/thumbor/tree/uploader
This was done earlier (before we started this conversation).

As you can see from
https://github.com/globocom/thumbor/commit/31242c357d097a4637995cc467a18939acacf0cc
I've already started working on it.
If you have any feedback, feel free to help! ;)
I'm planning on supporting:
PUT - Places the file at {STORAGE_ROOT_PATH}/year/month/day/filename.ext
If the file already exists, overwrite it silently.
POST - Places the file at {STORAGE_ROOT_PATH}/year/month/day/filename.ext
If the file already exists, raise an exception.
DELETE - Deletes the file at {STORAGE_ROOT_PATH}/year/month/day/filename.ext
You'll have to enable image deletion in your conf file.
Do you think that covers all your scenarios?
Cheers,
Bernardo Heynemann
On Thu, Feb 2, 2012 at 5:37 PM, Mike Lewis <
<EMAIL_ADDRESS>
wrote:

Awesome!
I started going down implementing it as a separate service (although it
could definitely be rolled into thumbor core).
https://github.com/mikelikespie/thumbor-dumper
Basically I added the concept of remote storages.  I implemented an HTTP
one that can do a PUT, and then subclassed it to support S3.
The work I started to do with adding it into the core can be found here:
https://github.com/mikelikespie/thumbor/tree/uploader
This was done earlier (before we started this conversation).

Reply to this email directly or view it on GitHub:
https://github.com/globocom/thumbor/issues/59#issuecomment-3784671


THREE.BufferGeometry.computeBoundingSphere(): Computed radius is NaN. The "position" attribute is likely to have NaN values.

Hello!
There is an exception that happens when loading an ifc file (the one attached):

ifc2.zip
Thank you!

::take

🟢🟢🟢

::take

Hi, @aka-blackboots! Thanks for taking this bounty! The due date is December 19, 2022 UTC.
If you need to submit some pull requests (PR) to complete the tasks, make sure that the last and only the last PR has a title that either starts with the bounty ID or is exactly the same as the bounty name. After the PR is merged, this bounty’s status will automatically changed to done.
If you do not need to make a PR, tell the manager @agviegas to run ::done command after your tasks is confirmed to be done.
Good luck!

::drop

🟢🟢🟢

::drop

Hi, @aka-blackboots! Thanks for giving it a try! It’s now once again available for anyone to take.

NaNs here come from all-0 placedGeometry.flatTransformation


Allow user-friendly name for Expression Matrix output files

@brianraymor wrote:
Laura pinged the matrix team with some demo feedback It looks like the filenames are uuid.loom which strikes me as very unhelpful if you download a file like that and then forget about it you won't necessarily be able to work out what it contained after the fact Is there a good place to put this feedback? Would you have a way of putting say the project shortname or something in so people have a handle on what the file is? I know the short name isn't always short -
Would it make sense for the Data Browser to implement a save/download as ... feature?
┆Issue Number: HCAB-325

@NoopDog Not implemented by Matrix team. Please see https://app.zenhub.com/workspaces/dcp-backlogs-5ac7bcf9465cb172b77760d9/issues/humancellatlas/matrix-service/162.

I also communicated the decision on the data-browser slack channel  - https://humancellatlas.slack.com/archives/CD0PLMWJZ/p1550024946006600

Is it possible for us to do this without them? Like we put the url on the screen and say right click, save as if you want to rename it? Check out the AWS bucket download flow. Is something like this possible with no work from the matrix team?

That's certainly how I download large music purchases from the EU and UK. It's unfortunate that the browser vendors (for security reasons) have broken many of their third party extensions that managed pause-resume and retry like https://www.downthemall.net/.

@NoopDog  @frano-m See branch matrix-file-name.

@noop https://github.com/HumanCellAtlas/data-browser/pull/537


Light Nord theme

Hi,
can you add a light version of the nord theme?
Thanks

nord doesn't have an official light mode palette from what i know

There's the Snow storm palette: https://www.nordtheme.com/docs/colors-and-palettes

Snow Storm is made up of three bright colors that are commonly used for text colors or base UI elements in bright ambiance designs.

It's more of meant to be used in very specific places from what I could tell, but I could be wrong


Callback 'on_dismissed' doesn't work on ventura ?

Desktop Notifier version: 5.0.1
Python version: 3.12
Operating System: MacOS Ventura

Description
I am planning to use this in a script. With following condition

The notifications performs a action when clicked.

The Script must exit after notification has been clicked or dismissed.

What I Did
import os
import sys
import asyncio
import datetime
import functools

from rubicon.objc.eventloop import EventLoopPolicy

# Install the event loop policy
asyncio.set_event_loop_policy(EventLoopPolicy())

from desktop_notifier import DesktopNotifier, Urgency, Button, ReplyField, DEFAULT_SOUND

notifier = DesktopNotifier()

#print (notifier.get_capabilities())

async def waiter(event):
	def fp():
		print ("Ack")
		#os.system("open -a Terminal")
		event.set()

	print('waiting for notification to be clicked or dismissed...')
	await notifier.send(
		title="Julius Caesar",
		message="Et tu, Brute?",
		urgency=Urgency.Normal,
		on_clicked=functools.partial(fp),
		on_dismissed=functools.partial(fp),
		sound=DEFAULT_SOUND,
	)

	await event.wait()

	print('.....Notification has been clicked!')

async def main():
	# Create an Event object.
	event = asyncio.Event()

	# Spawn a Task to wait until 'event' is set.
	waiter_task = asyncio.create_task(waiter(event))

	# Wait until the waiter task is finished.
	await waiter_task

asyncio.run(main())

This works fine with on_clicked. But when I closed the notification by clicking cross button, it doesn't work. Any idea why ?

macOS_notification has something like this which stops the loop when every notification handled.
    while client.get_notification_manager().get_active_running_notifications() > 0:
        time.sleep(1)
    client.stop_listening_for_callbacks()

I wish if we could do something similar here. I tried with
	while len(notifier.current_notifications) < 1:
                await Asyncio.sleep(1)
		event.set()

But didn't work.

I think you are seeing a bug in the currently released version. Could you try with the prerelease 6.0.0.dev0? You can install it with:
pip3 install -U --pre desktop-notifier

@samschott Yes, I have checked. It works with 6.0.0.dev0. Thanks.


Errors in code for importing llama model from Huggingface

System Info

CPU architecture x86_64
Host memory size 32Gb
GPU Nvidia RTX 2060
GPU memory size 12 Gb
TensorRT-LLM v0.10.0

Who can help?
No response
Information

[ ] The official example scripts
[X] My own modified scripts

Tasks

[ ] An officially supported task in the examples folder (such as GLUE/SQuAD, ...)
[ ] My own task or dataset (give details below)

Reproduction

https://github.com/NVIDIA/TensorRT-LLM/blob/v0.10.0/tensorrt_llm/models/llama/convert.py#L1411 - act_range has default value {}
https://github.com/NVIDIA/TensorRT-LLM/blob/v0.10.0/tensorrt_llm/models/llama/convert.py#L631 - act_range has default value []; this function is called from the previous one.
https://github.com/NVIDIA/TensorRT-LLM/blob/v0.10.0/tensorrt_llm/models/llama/convert.py#L749 - no None checks for values of act_range, so it yield Exception if used with default value

https://github.com/NVIDIA/TensorRT-LLM/blob/v0.10.0/tensorrt_llm/models/llama/weight.py#L312 - the only place where layer is being initialized is here https://github.com/NVIDIA/TensorRT-LLM/blob/v0.10.0/tensorrt_llm/models/llama/weight.py#L202 ... and it is initialized with None.
Expected behavior
No exceptions
actual behavior
Code raises an exception
additional notes

Sorry, could u plz share us more details on reproducing issue?
B.T.W, please try main branch instead of previously tag.

Code to reproduce:

from tensorrt_llm.mapping import Mapping
from tensorrt_llm.models import LLaMAForCausalLM
from tensorrt_llm.quantization import QuantAlgo
from tensorrt_llm.models.llama.convert import create_config_from_hugging_face, load_from_hf_checkpoint
from tensorrt_llm.models.modeling_utils import QuantConfig, PretrainedConfig
MODEL_DIR = "path to my locally saved model"
mapping = Mapping()
quantization = QuantConfig(quant_algo=QuantAlgo.W4A16, kv_cache_quant_algo=QuantAlgo.INT8)
config = create_config_from_hugging_face(MODEL_DIR, "float16", mapping, quantization)
pretrained_config = PretrainedConfig.from_dict(config)
llama = LLaMAForCausalLM.from_config(pretrained_config)
weights = load_from_hf_checkpoint(model_dir=MODEL_DIR, mapping=mapping, config=pretrained_config)

It yields another error I've forgot to mention.:

Traceback (most recent call last):
File "C:\Users\1\Projects\ragllm\rag_llm\parsers\llama_to_tensorrt2.py", line 15, in
weights = load_from_hf_checkpoint(model_dir=MODEL_DIR,
File "C:\Users\1\AppData\Local\Programs\Python\Python310\lib\site-packages\tensorrt_llm\models\llama\weight.py", line 298, in load_from_hf_checkpoint
split_v.transpose(), plugin_weight_only_quant_type)
TypeError: transpose() received an invalid combination of arguments - got (), but expected one of:

(int dim0, int dim1)
(name dim0, name dim1)

After I've fixed this one by copying load_from_hf_checkpoint function and editing v.transpose() to v.t(), it began to fail on the second point from my original list.

It looks like u wanna to simplify the process of generating trtllm checkpoint, right?

Yes, kinda. I was trying to convert Huggingface Llama model to TRT format and was cutting all parts unnecessary for me to make code more simple.

It's not our recommend way to use TensorRT-LLM and we don't verify such script yet.
You may have a try with our high-level API example https://github.com/NVIDIA/TensorRT-LLM/tree/main/examples/high-level-api as reference.

from tensorrt_llm.quantization import QuantAlgo
from tensorrt_llm import LLM, ModelConfig
from tensorrt_llm.models.modeling_utils import QuantConfig
MODEL_DIR = "path to local Llama folder"
quant_config = QuantConfig(quant_algo=QuantAlgo.W4A16)
model_config = ModelConfig(model_dir=MODEL_DIR,
quant_config=quant_config)
llm = LLM(config=model_config)

Fails with

[TensorRT-LLM] TensorRT-LLM version: 0.10.0
Loading Model: [1/3]	Load HF model to memory
Traceback (most recent call last):
File "C:\Users\1\Projects\ragllm\rag_llm\parsers\llama_to_tensorrt3.py", line 10, in
llm = LLM(config=model_config)
File "C:\Users\1\AppData\Local\Programs\Python\Python310\lib\site-packages\tensorrt_llm\hlapi\llm.py", line 505, in init
self._build_model()
File "C:\Users\1\AppData\Local\Programs\Python\Python310\lib\site-packages\tensorrt_llm\hlapi\llm.py", line 694, in _build_model
runtime_context = model_loader()
File "C:\Users\1\AppData\Local\Programs\Python\Python310\lib\site-packages\tensorrt_llm\hlapi\llm.py", line 942, in call
step()
File "C:\Users\1\AppData\Local\Programs\Python\Python310\lib\site-packages\tensorrt_llm\hlapi\llm.py", line 1062, in _load_model_from_hf
model2struct[model_arch].quantize(
File "C:\Users\1\AppData\Local\Programs\Python\Python310\lib\site-packages\tensorrt_llm\models\llama\model.py", line 414, in quantize
convert.quantize(
File "C:\Users\1\AppData\Local\Programs\Python\Python310\lib\site-packages\tensorrt_llm\models\llama\convert.py", line 1361, in quantize
with open(os.path.join(output_dir, 'config.json'), 'w') as f:
FileNotFoundError: [Errno 2] No such file or directory: 'C:\Users\1\AppData\Local\Temp\tmppb317z5yllm-workspace/quantized-checkpoint\config.json'


[SUGGESTION] Tools and Best Practices

Based on the recent @JanLin presentation -- it would be helpful if we create  a new wiki page for Tools and Best Practices.
This SHOULD include IndyScan and others.

Performed a pull request with a new page if you want accept it and then merge where you think is relevant.

@vinomaster I tried to fix the image links but could not figure it out. Can you take a look? Thanks

Fxied


Fix dropping fields creating data corruption

The Point is intended to be immutable after being parsed since it
is shared by several goroutines.  When dropping a field (e.g. time),
corrupted data can result if one goroutine is delete the field
while another is marshaling the underlying byte slices.
To avoid this, the shard will just skip invalid fields and series
instead of trying to mutate them by deleting them.
Required for all non-trivial PRs

[ ] Rebased/mergable
[ ] Tests pass
[ ] CHANGELOG.md updated
[ ] Sign CLA (if not already signed)

I fixed this in 1.2 directly because the code in master has diverged quite a bit and requires a different fix now.


Fix inaccurate CodeSonar branding on Jenkins build results screen

Change casing of text: "Codesonar" should be "CodeSonar".
CodeSonar icon is incorrect; it should be the red "g" icon.  We no longer use the old "sonar" icon.


localization example and additional check in load_extensions_from_module

Summary

Two examples for localization added in nextcord\examples\application_commands\localization.py: for slash command and for SlashOption
An additional check is added to the load_extensions_from_module method: when forming a list of submodules, it is checked if submodule is file and not a folder
Checklist

[x] If code changes were made then they have been tested.

[ ] I have updated the documentation to reflect the changes.
[ ] I have run task pyright and fixed the relevant issues.

[ ] This PR fixes an issue.
[ ] This PR adds something new (e.g. new method or parameters).
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[ ] This PR is not a code change (e.g. documentation, README, ...)

This PR has scope creep, please read the contribution guidelines


fix: update vault deposit attempt

Summary

allow fallback for vault with non standard deposit abi

:tada: This PR is included in version 1.18.15 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.18.15 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Switch to "Log in" instead of "Sign in" on submit button

Every where on the site says "Log in" and "Log out" except this one button.

:+1: Nice catch--thanks!


Android: MarkerView changes anchor for a millisecond, when size of child is changed.

Describe the bug
Hi, i have a Problem with changing the width and height of the MakerView child. On Android, when i change the size of the Child it looks like the anchor is moved to the center of the MarkerView for just a millisecond. So it looks like the Marker is jumping.
I didn't figure out why this is happening, in the example below i have just a SVG as Child, in the long run i want the size to be animated, but when i do the same Issue occurs.
On Ios it works fine. I already looked in RCTMGLMarkerView.kt and tried to remove the offset on refresh at all with no luck. At the moment i haver no clue why this is happening.
Thanks in advance
To Reproduce
Change the size of the Child in the MarkerView
Example:
import React from 'react';

import Svg, { Path } from 'react-native-svg';

import MapboxGL from '@rnmapbox/maps';
import { Box, Pressable } from 'native-base';

type Props = {
  tourId: string;
  poi: any;
  selected: boolean;
  onSelect?: () => void;
};

export const PoiMarker: React.FC<Props> = ({
  tourId,
  poi,
  selected,
  onSelect,
}) => {
  return (
    <MapboxGL.MarkerView
      key={`${tourId}-${poi.id}`}
      id={`${tourId}-${poi.id}`}
      coordinate={[poi.lng, poi.lat]}
      anchor={{ x: 0.5, y: 1.0 }}
      selected={selected}
      /* @ts-ignore */
      style={{ zIndex: selected ? 99 : undefined }}>
      <Box
        style={{
          width: 32 * (selected ? 2 : 1),
          height: 50 * (selected ? 2 : 1),
        }}>
        <Pressable onPress={onSelect}>
          <Svg
            width={'100%'}
            height={'100%'}
            viewBox="0 0 37 50"
            fill="none"
            style={{
              shadowColor: '#000',
              shadowOffset: {
                width: 2,
                height: 2,
              },
              shadowOpacity: 0.25,
              shadowRadius: 3,
              zIndex: 1,
              width: '100%',
              height: '100%',
            }}
            stroke={'transparent'}
            strokeWidth={3}>
            <Path
              d="M34.849 18.182c0 7.725-4.29 15.345-8.776 21.163a71.52 71.52 0 0 1-6.119 6.926 63.182 63.182 0 0 1-1.772 1.699 63.338 63.338 0 0 1-1.772-1.699 71.507 71.507 0 0 1-6.12-6.926c-4.486-5.819-8.775-13.438-8.775-21.163 0-9.205 7.462-16.667 16.667-16.667 9.205 0 16.667 7.462 16.667 16.667Z"
              fill={selected ? '#fff' : '#5856D6'}
              stroke={'transparent'}
              strokeWidth={3}
            />
          </Svg>
        </Pressable>
      </Box>
    </MapboxGL.MarkerView>
  );
};

Expected behavior
The size should change without looking like the anchor is changed for a millisecond
** Environment **

Platform: Android
Platform OS: Android 9
Device: Galaxy S8
Emulator/ Simulator: no
Dev OS: OSX 12.3.1
@rnmapbox/maps Version: 10.0.0-beat.19
Mapbox: v10
React Native Version: 0.67.4

import { Box, Pressable } from 'native-base';
import MarkerSVG from '../../../Base/svg/MarkerSvg';

Hi, please remove those dependencies, as it makes complicated to just copy your code into our BugRepExample.js and try out.
The simpler to reproduce the issue the more likely we can look into it. Thanks for the understanding.

Hi @mfazekas i've updated the original file above. Thanks for looking into this.

Hi @mfazekas i've updated the example and removed other package dependencies. Thanks for looking into this.

@danielknorn thanks! It's still missing a MapView component and require parameters.

@mfazekas yeah sorry you are right. In my Project it is in another File. Updated it for a full Example. Thanks

@danielknorn so what happens is that, when you change the size of view it's rendered (1). And we detect the change, and adjust the position, anchor(2). Then mapbox updates the MarkerView position(3), and it's rendered. Ideally we'd do it as an atomic thing (1-3) with no render in between, but we cannot really do. So it's possible that a non consistent state appears in the view.


Paper Discussion 14b: Beetle: Flexible Communication for Bluetooth Low Energy

Please provide critique and review for the paper.
I would appreciate if you could also add a note about the parts you thought were rather dense (or if you thought the paper was simple enough).
Edits
@jacobcannizzaro asks if Beetle is introducing more vulnerabilities and if it would be possible for legacy applications to use Beetle without significant code change. He also raises the point that Beetle's performance is slower than raw access and that the applications are not novel enough.

Reviewer: Jacob Cannizzaro
Review Type: Critical
Problem Being Solved
Bluetooth Low Energy is one of the primary protocols for connecting many peripheral devices common in IoT, such as heart monitors. Current operating system support for this bluetooth protocol is supports only one-to-one communication for the most part. This means one peripheral device could not be streaming data directly to two seperate applications attempting to connect to it at the same time.
Main Contributions
This paper introduces Beetle, a hardware interface that treats all periphery devices as a virtual device abstraction. Beetle is implemented as an operating system service using GATT, the application-level protocol for Bluetooth Low Energy. Beetle is able to abstract any peripheral device so that instead of one GATT connection directly from application to device, there is a virtual device that can handle the many-to-many communication between other virtual devices without the physical devices needing to know about the abstraction. They are able to use this hardware interface for use cases that are currently impossible using implementations of Beetle within Linux and Android.
Questions

Even if Beetle is supporting fine grain security policies enforced with bluetooth's low enerygy structure, would the devices and applications now have more vulnerabilities do deal with if they are now potentially connected in a many-to-many fashion?
Is it possible at this point to begin to use a new os embedded hardware interface such as this? I imagine it would be very hard keeping legacy systems in the loop as new peripheral devices were manufactured in accordance with Beetle's protocols.

Critiques

The paper mentions that speed is not the main point of Beetle, but that it should not slow down normal use of operation. While it did seem to perform well, it was shown in section 7 that connection times were slower than connections made without Beetle. While this is fine for a proof of concept, I don't know how this would scale when thinking of the sheer number of connected peripheral devices on the internet of things.
I think they could have given more examples of use cases. I was thinking of countless while reading, and I think they could have given some ideas more "novel", as they say, than they in fact provide.

Reviewer: Jacob Cannizzaro
Review Type: Critical
Problem Being Solved
Bluetooth Low Energy is one of the primary protocols for connecting many peripheral devices common in IoT, such as heart monitors. Current operating system support for this bluetooth protocol is supports only one-to-one communication for the most part. This means one peripheral device could not be streaming data directly to two seperate applications attempting to connect to it at the same time.
Main Contributions
This paper introduces Beetle, a hardware interface that treats all periphery devices as a virtual device abstraction. Beetle is implemented as an operating system service using GATT, the application-level protocol for Bluetooth Low Energy. Beetle is able to abstract any peripheral device so that instead of one GATT connection directly from application to device, there is a virtual device that can handle the many-to-many communication between other virtual devices without the physical devices needing to know about the abstraction. They are able to use this hardware interface for use cases that are currently impossible using implementations of Beetle within Linux and Android.
Questions
1. Even if Beetle is supporting fine grain security policies enforced with bluetooth's low enerygy structure, would the devices and applications now have more vulnerabilities do deal with if they are now potentially connected in a many-to-many fashion?

2. Is it possible at this point to begin to use a new os embedded hardware interface such as this? I imagine it would be very hard keeping legacy systems in the loop as new peripheral devices were manufactured in accordance with Beetle's protocols.

Critiques
1. The paper mentions that speed is not the main point of Beetle, but that it should not slow down normal use of operation. While it did seem to perform well, it was shown in section 7 that connection times were slower than connections made without Beetle. While this is fine for a proof of concept, I don't know how this would scale when thinking of the sheer number of connected peripheral devices on the internet of things.

2. I think they could have given more examples of use cases. I was thinking of countless while reading, and I think they could have given some ideas more "novel", as they say, than they in fact provide.

The questions here are that Beetle is introducing more vulnerabilities and if it would be possible for legacy applications to use Beetle without significant code change. As for the first question, I doubt that would happen since the only vulnerability that Beetle would introduce in the system is within its own code. As for legacy applications, it's a little more difficult to gauge. But if these applications were using GATT, I don't see why not!
The slower performance point is valid. But my understanding is that most of the latency is introduced in the system when many-to-many communication between peripherals are involved and I don't think we can really compare that.

Reviewer: Marcus Young
Review Type: Skim
Problem being solved
Current operating system abstractions are not designed to handle many different Bluetooth Low Energy peripherals. Beetle is a new hardware interface that virtualizes peripherals at the application layer and allows applications to exist that previously were impossible, such as a door lock that can be accessed by different types of users.
Important contributions
Beetle allows more than one application to access a peripheral. Currently, only a single process can access a BLE peripheral. Beetle also mediates access between applications and mobile peripherals, providing access control that is non-existent in current operating systems.

Reviewer: Alvaro Albero
Review Type: Skim
Problem Domain
The number of Bluetooth Low Energy devices is increasing rapidly. Current communications that do not follow well defined standards require the OS to expose the peripheral as a raw hardware channel, not allowing to multiplex access or enforce security policies. It forces peripherals into vertical silos and you cannot have two applications accessing them at the same time or having different access levels.
Main Contributions
The authors propose Beetle, an OS service that virtualizes peripherals at the application layer. Beetle uses GATT, the application-level protocol for Bluetooth Low Energy. It provides an interface to allow safe access without knowledge of the underlying hardware. It also provides isolation and security policies to control access. They build some simple applications in Linux and Android to show the potential of their service, these applications are impossible with the current communication system. They show they can access peripherals from multiple applications simultaneously, they are able to enforce different access levels to these applications and they show that the performance does not decrease.

Reviewer: Sam Frey
Review Type: Critical
Problem
There is an ever increasing amount of peripheral devices using Bluetooth Low Energy, but the nature of Bluetooth Low Energy is such that an OS typically cannot discern the function of a peripheral or multiplex it to applications. This means only one application can communicate with a peripheral at a time, limiting what can be done with a Bluetooth Low Energy peripheral.
Contributions
The authors created an OS tool called Beetle for communicating with Bluetooth Low Energy Devices. Beetle uses the Generic Attribute Protocol provided by Bluetooth Low Energy to allow for fine-grained management of peripheral devices. With Beetle, multiple applications can access the same peripheral device with varied levels of privilege instead of one application having complete control.
Questions

The authors mention that changing the units of measure or sampling rate on a peripheral may interfere with other applications communicating with the device. They elaborate on this in footnote 2 stating that for now, GATT standardizes units of measure. Could they test for this interference by changing the sample rate of a simulated peripheral device instead?
Regarding the battery monitoring example, Apple offers this feature in iOS for certain peripheral devices. For example, you can track the battery life of an Apple Watch and Apple-manufactured headphones simultaneously on an iPhone. Apple is notoriously closed-source, but do you think they are using a similar protocol to Beetle or relying on proprietary hardware instead?

Critiques
Since Beetle is built based on GATT, I would've liked a bit more detail into the protocol. In my reading of the paper, I pretty much treated it as a black box (i.e. instead of device -> GATT -> application, device -> GATT -> Beetle -> application). Otherwise, I found the paper very informative and easy to follow where the biggest shortcoming was my lack of knowledge about networking.

Reviewer: Gregor Peach
Review Type: Skim
Problem Being Solved
Bluetooth low energy is a new protocol for communication between hardware peripherals. It's super cool and useful for the IoT. However, current operating systems and middleware make it incredibly difficult to use. This leaves its potential unleveraged.
Main Contributions

Analysis of uses for BLE
Creation of middleware (Beetle) for interacting with it
Creation of test applications of Beetle
Evaluation of how Beetle performs in these test applications

Reviewer: Sam Frey
Review Type: Critical
Problem
There is an ever increasing amount of peripheral devices using Bluetooth Low Energy, but the nature of Bluetooth Low Energy is such that an OS typically cannot discern the function of a peripheral or multiplex it to applications. This means only one application can communicate with a peripheral at a time, limiting what can be done with a Bluetooth Low Energy peripheral.
Contributions
The authors created an OS tool called Beetle for communicating with Bluetooth Low Energy Devices. Beetle uses the Generic Attribute Protocol provided by Bluetooth Low Energy to allow for fine-grained management of peripheral devices. With Beetle, multiple applications can access the same peripheral device with varied levels of privilege instead of one application having complete control.
Questions
* The authors mention that changing the units of measure or sampling rate on a peripheral may interfere with other applications communicating with the device. They elaborate on this in footnote 2 stating that for now, GATT standardizes units of measure. Could they test for this interference by changing the sample rate of a simulated peripheral device instead?

* Regarding the battery monitoring example, Apple offers this feature in iOS for certain peripheral devices. For example, you can track the battery life of an Apple Watch and Apple-manufactured headphones simultaneously on an iPhone. Apple is notoriously closed-source, but do you think they are using a similar protocol to Beetle or relying on proprietary hardware instead?

Critiques
Since Beetle is built based on GATT, I would've liked a bit more detail into the protocol. In my reading of the paper, I pretty much treated it as a black box (i.e. instead of device -> GATT -> application, device -> GATT -> Beetle -> application). Otherwise, I found the paper very informative and easy to follow where the biggest shortcoming was my lack of knowledge about networking.

Regarding your first question, that part of the paper was, in my mind, the author's pointing out something quite wrong with their assumptions. They do mention a lot of things that can be done to work around this and it looks like they did do experiments. But not really sure!
As for your second question, again very difficult to say what Apple did. I am tempted to say yes, but it's not possible to be sure!
Regarding GATT, hopefully the presentation tomorrow will make it a little clear as to how GATT works!

Reviewer: Andrew Nguyen
Review Type: Critical
Problem Being Solved
Bluetooth Low Energy allows versatile connection for multiple peripheral devices. The paper introduces Beetle which would allow the virtualization of the components and peripherals at the application layer that won't bog down the operating system of the other devices to try to look into the hardware, the fine-grained access control to peripheral device resources, and transparent access to peripherals connected over the network.
Main Contributions
Beetle is an operating system service that mediates access between applications and mobile peripherals using GATT (Generic Attribute Profile). Like mentioned in the Problems Being Solved section, it helps faciliate the connections without having to be caught up in the specifics and things of that nature. It's for low power networks and functionality paves the way for its connection-oriented interface, hierarchy, and transactional methods which in turn give it sufficient structure for an OS to maintain, understand, and manage application behavior and accessibility. Beetle helps facilitate multiple devices having a say and place for their participation in the greater scheme of the devices.
Questions

They said one of the challenges is to " honor GATT semantics regarding handle ordering and continuity" and " Simply removing a characteristic from the middle of a service would create a “hole” in the service, violating the protocol" How would this be done given the idea that Beetle can hide characteristics of a service and that it maps from different GATT servers? I might be misunderstanding the idea of it.
Can Beetle run into a dead end when it cannot meet the proper identification and discovery of certain parts of devices? Not all devices are going to be open and if Beetle would like to facilitate these connections how can it approach it?

Critiques
This paper did a great job on covering how the entire functionality of Beetle would work along with its GATT protocols. It is really fleshed out. However, it seems to briefly mention the security parts of it. The paper does urge the reader to look into another paper but a brief paragraph would have been nice in order to counter or cushion the questions that could arise. Next, it seems to touch on energy sparingly and it makes me worried how potentially consuming this would be.

Reviewer: Andrew Nguyen
Review Type: Critical
Problem Being Solved
Bluetooth Low Energy allows versatile connection for multiple peripheral devices. The paper introduces Beetle which would allow the virtualization of the components and peripherals at the application layer that won't bog down the operating system of the other devices to try to look into the hardware, the fine-grained access control to peripheral device resources, and transparent access to peripherals connected over the network.
Main Contributions
Beetle is an operating system service that mediates access between applications and mobile peripherals using GATT (Generic Attribute Profile). Like mentioned in the Problems Being Solved section, it helps faciliate the connections without having to be caught up in the specifics and things of that nature. It's for low power networks and functionality paves the way for its connection-oriented interface, hierarchy, and transactional methods which in turn give it sufficient structure for an OS to maintain, understand, and manage application behavior and accessibility. Beetle helps facilitate multiple devices having a say and place for their participation in the greater scheme of the devices.
Questions
1. They said one of the challenges is to " honor GATT semantics regarding handle ordering and continuity" and " Simply removing a characteristic from the middle of a service would create a “hole” in the service, violating the protocol" How would this be done given the idea that Beetle can hide characteristics of a service and that it maps from different GATT servers? I might be misunderstanding the idea of it.

2. Can Beetle run into a dead end when it cannot meet the proper identification and discovery of certain parts of devices? Not all devices are going to be open and if Beetle would like to facilitate these connections how can it approach it?

Critiques
This paper did a great job on covering how the entire functionality of Beetle would work along with its GATT protocols. It is really fleshed out. However, it seems to briefly mention the security parts of it. The paper does urge the reader to look into another paper but a brief paragraph would have been nice in order to counter or cushion the questions that could arise. Next, it seems to touch on energy sparingly and it makes me worried how potentially consuming this would be.

Good questions. As for your first question, I do hope that the presentation tomorrow will clear up any confusion. Regarding the second question, Beetle depends completely on the services that are being published by the peripheral. My guess is that if a peripheral combines two services and publishes them as one, for example, there would be no way for Beetle to get at them. The way to think about this is that Beetle (a GATT client) takes complete ownership of all peripherals. And then, in essence, uses kernel level constructs (virtual devices) behind GATT servers to expose them to user level applications. I would encourage you to reread the Linux implementation part for a detailed understanding of this.
As for your critiques, my feel of the paper is that it looks at access control for security and basically nothing else.

Reviewer: Niko Reveliotis
Review Type: Critical
Problem Being Solved
Bluetooth Low Energy is a primary means of communication for many embedded devices with mobile/gateway devices. Unfortunately, these devices have their limitations with this communication protocol. This paper seeks to eliminate the 1-to-1 limitation between applications and a peripheral of the Bluetooth Low Energy protocol, and allow for different bluetooth devices to communicate with each other simultaneously. On top of this, this paper discusses their OS Beetle which will optimize communications on the application-level to increase capabilities of communication between a bluetooth devices with multiple mobile/gateway devices. They are trying to allow for continued use of Bluetooth Low Energy as it is incredibly efficient and cheap to implement.
Main Contributions

"This paper presents Beetle, an operating system service that mediates access between applications and mobile peripherals using GATT (Generic Attribute Profile), the application-level protocol of Bluetooth Low Energy"
Three applications for Beetle implemented in Android and Linux

"A battery monitoring application that collects battery levels from all nearby peripherals, The monitoring application is restricted to reading only battery levels but other applications can simultaneously have more permissive access."
Two applications concurrently read the current heart rate from a heart-rate monitor. Both applications can make configuration changes (such as turning notifications on or off) without impacting the other.
A door-lock that can be accessed by different types of users—residents can lock and unlock the door while observers can only see whether the door is currently locked. The door-lock connects through a generic home gateway, rather than one built specifically for the lock.

Three Questions

How does the increased roundtrip latency from the overhead of Beetle affect specific bluetooth devices (or how would it)? Do devices have an automatic retry/reconnect when a request is made without a response after a certain amount of time? For example, I hit play on my phone when connected to a bluetooth speaker, if the song doesn't start playing/no confirmation is received by the phone, my phone tells me I've lost connection or tries reconnecting to my bluetooth speaker.
When it comes to home security devices, they usually come with a central gateway that all devices connect to (like a keypad for entry that connects to door/window sensors). In terms of connecting this device to the network, would the individual devices/sensors be connected, or simply the hub allowing multiple security systems to be accessed and "combined".
Off topic from the paper, but many people are "against" bluetooth since it interferes with the 2.4Ghz band of Wi-Fi. Are there any competitive wireless communications like bluetooth which are able to benefit from the same power and cost benefits?

Three Critiques

Although the many-to-many communication protocol is a great feature, Beetle isn't specifically coded for particular bluetooth devices (keyboards/speakers/etc). Devices being connected through Beetle are limited to "service discovery, notifications and read/write".
This paper aims to create a solution that will streamline bluetooth connections by overcoming the 1-to-1 limitation, but in terms of implementation they're currently limited to Android and Linux. I understand this is a concept, but if you are seeking to change the standard, implementations are going to be needed across the board. And they stated the Android and Linux versions are very different, which makes me believe implementing Beetle in other OSs is going to be a difficult task.
The increased round-trip latency is concerning. For most applications this wouldn't be an issue: it's not a serious problem if your bluetooth speaker takes an extra half second to turn down the volume. Yet when it comes to more critical devices, such as pacemakers/blood sugar monitors/etc, this seems more important to address. Also outlined in question 1, are there any side-effects created by the increased latency?

I apologize for the late submission, I was taking care of some work at home and completely forgot to submit this morning.

Reviewer: Niko Reveliotis
Review Type: Critical
Problem Being Solved
Bluetooth Low Energy is a primary means of communication for many embedded devices with mobile/gateway devices. Unfortunately, these devices have their limitations with this communication protocol. This paper seeks to eliminate the 1-to-1 limitation between applications and a peripheral of the Bluetooth Low Energy protocol, and allow for different bluetooth devices to communicate with each other simultaneously. On top of this, this paper discusses their OS Beetle which will optimize communications on the application-level to increase capabilities of communication between a bluetooth devices with multiple mobile/gateway devices. They are trying to allow for continued use of Bluetooth Low Energy as it is incredibly efficient and cheap to implement.
Main Contributions
* "This paper presents Beetle, an operating system service that mediates access between applications and mobile peripherals using GATT (Generic Attribute Profile), the application-level protocol of Bluetooth Low Energy"

* Three applications for Beetle implemented in Android and Linux

  * "A battery monitoring application that collects battery levels from all nearby peripherals, The monitoring application is restricted to reading only battery levels but other applications can simultaneously have more permissive access."
  * Two applications concurrently read the current heart rate from a heart-rate monitor. Both applications can make configuration changes (such as turning notifications on or off) without impacting the other.
  * A door-lock that can be accessed by different types of users—residents can lock and unlock the door while observers can only see whether the door is currently locked. The door-lock connects through a generic home gateway, rather than one built specifically for the lock.

Three Questions
1. How does the increased roundtrip latency from the overhead of Beetle affect specific bluetooth devices (or how would it)? Do devices have an automatic retry/reconnect when a request is made without a response after a certain amount of time? For example, I hit play on my phone when connected to a bluetooth speaker, if the song doesn't start playing/no confirmation is received by the phone, my phone tells me I've lost connection or tries reconnecting to my bluetooth speaker.

2. When it comes to home security devices, they usually come with a central gateway that all devices connect to (like a keypad for entry that connects to door/window sensors). In terms of connecting this device to the network, would the individual devices/sensors be connected, or simply the hub allowing multiple security systems to be accessed and "combined".

3. Off topic from the paper, but many people are "against" bluetooth since it interferes with the 2.4Ghz band of Wi-Fi. Are there any competitive wireless communications like bluetooth which are able to benefit from the same power and cost benefits?

Three Critiques
1. Although the many-to-many communication protocol is a great feature, Beetle isn't specifically coded for particular bluetooth devices (keyboards/speakers/etc). Devices being connected through Beetle are limited to "service discovery, notifications and read/write".

2. This paper aims to create a solution that will streamline bluetooth connections by overcoming the 1-to-1 limitation, but in terms of implementation they're currently limited to Android and Linux. I understand this is a concept, but if you are seeking to change the standard, implementations are going to be needed across the board. And they stated the Android and Linux versions are very different, which makes me believe implementing Beetle in other OSs is going to be a difficult task.

3. The increased round-trip latency is concerning. For most applications this wouldn't be an issue: it's not a serious problem if your bluetooth speaker takes an extra half second to turn down the volume. Yet when it comes to more critical devices, such as pacemakers/blood sugar monitors/etc, this seems more important to address. Also outlined in question 1, are there any side-effects created by the increased latency?

I apologize for the late submission, I was taking care of some work at home and completely forgot to submit this morning.

Interesting questions! I would hazard a guess about the first question and say Beetle does not introduce that kind of latency. The max latency, 2x, is introduced when using many-to-many communication between peripherals. And frankly, those kind of applications do not exist in the wild. Regarding the second question, your intuition is correct; Beetle aims to become a "hub" gw. Question 3, I honestly don't know.
Critique 1 - not really! Hope I can make it clear tomorrow. Critique 2 - Beetle talks about Windows and Mac solutions, albeit briefly. The crux of the increased RTT lies in many-to-many peripheral communication. I am not sure what the issue here is but I would guess that it's more of a BLE limitation where the communication between peripherals are time synchronized - the whole reason why they are so energy efficient.


Deprecate and Remove Postgres Backend

Tinkerbell has numerous pieces of functionality that are unsupported, poorly maintained and/or no longer used. This project seeks to clean up the Tinkerbell codebase by dubbing functionality deprecated and removing it.
Proposals
https://github.com/tinkerbell/proposals/tree/main/proposals/0029
Project
https://github.com/orgs/tinkerbell/projects/18

All relevant Tinkerbell repositories have now had their Tinkerbell backends stripped. Additionally, all the cacher and packet backends have been removed.


Adding screenshot to README

Coverage remained the same at 70.787% when pulling ddaa0ba2e911b7c33fb5ba29a1f35b4439d4c2c1 on update-readme into 9e0c0ec3b3ec6354be084df1cd0840bef6f62429 on develop.

Coverage remained the same at 70.787% when pulling e92e5edfdf9df6f90ef3a14e846ee7b5fd64c2d7 on update-readme into 31398f0956a3ee45c3c9e28d173fea36b0ff74e5 on develop.


Implemented the option to specify the payment intent

Hi,
as the native PayPal SDKs support PaymentIntents already this change does only add an public API to do so with PayPal.Forms.
The default behavior while not specifying an PaymentIntent remains PaymentIntent.Sale. This means, that this merge request does not introduce a breaking change.
So a typical call with a custom PaymentIntent will look like this:
using PayPal.Forms;
using PayPal.Forms.Abstractions;
using PayPal.Forms.Abstractions.Enum;

...

var item = new PayPalItem("My cart item", 5M, "USD");
var result = await CrossPayPalManager.Current.Buy(item, 0M, intent: PaymentIntent.Authorize);

...

best regards

Looks nice

Hey your changes are in version 2.16.1 witch is now live


⚠ Bofrost.com has degraded performance

In 61263ce, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 1272 ms

Resolved: Bofrost.com performance has improved in 460faca.


Run Current Query not behaving as expected

Issue Type: Bug
Ctrl+F5: Run Current Query executes al statements in the editor after upgrading to May 2020 version
Azure Data Studio version: azuredatastudio 1.18.0 (2acd37a1b1cff34b64fbb4ea2d40715d7e2accac, 2020-05-19T23:54:30.554Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz (8 x 2394)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.89GB (1.76GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (10)

Extension
Author (truncated)
Version

admin-pack
Mic
0.0.2

agent
Mic
0.47.0

azuredatastudio-postgresql
Mic
0.2.6

import
Mic
0.15.0

powershell
ms-
2020.4.0

profiler
Mic
0.11.0

query-history
Mic
0.1.0

schema-compare
Mic
1.4.0

server-report
Mic
0.2.2

azdata-sanddance
msr
1.3.9

I'm on macos and have swapped Run Query (originally F5) and Run Current Query (originally cmd-F5), so Run Query is cmd-F5 and Run Current Query F5.
Now F5 executes Run Query !!! Tried to assign F9 to Run Current Query but it doesn't work: it also executes Run Query.
This happens (F5 or F9) when having the cursor inside the query. If I select the whole statement of a single query then the shortcut works fine and executes the selected query.
I'm also on 1.18.0, this worked fine in 1.17.x
Azure Data Studio version: azuredatastudio 1.18.0 (2acd37a1b1cff34b64fbb4ea2d40715d7e2accac, 2020-05-19T23:48:48.510Z)
OS version: Darwin x64 18.7.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz (4 x 2500)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
1, 3, 7

Memory (System)
8.00GB (0.13GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (1)

Extension
Author (truncated)
Version

azuredatastudio-postgresql
Mic
0.2.6

This has been fixed - if you update to the 18.1 hotfix build this should be resolved. Thanks for the report!


hmm..fixed now

https://github.com/jima80525/ctypes_example/blob/07e89a10b5b933212932473f6f7f47c38e2a01d0/tutorial2/testWrappedPoint.py#L21
Good to see you fixed the __init__ for your point wrapper. I was reading the post, and upon finding the attribution self = get_point() here, I came here to file the bug at once.  :-)
self is just a normal variable inside a method, and attributing to it will just make it point to another object, not "self" anymore.

Yes.   Thanks!  I'll admit that a different contributor fixed that for me the day the article was published.


MODE-2495 Fixes how user transactions are handled

The previous code made the incorrect assumption that a user transaction is "confined" to the thread that started it. This is obviously not the case, since the same transaction can be suspended & resumed subsequently off different threads.

Amended the commit with a broader refactoring of the SynchronizedTransactions#begin method.

Very nice improvement: the updated method is indeed more straightforward. Thanks! Looks great!


ESP-IDF monitor cannot neither be opened nor closed from VSCode

Probably not your fault, but running
make flash monitor
run as build command under Visual Studio Code just runs compile and flash. The monitor does not start. It terminates with
termios.error: (102, 'Operation not supported on socket')
make: *** [monitor] Error 1

If one is running
make monitor
from integrated VSCode terminal he is unable to terminate it by CTRL-]
I'm sure Atom will show the same behaviour (not tested).
I'm aware, that these problems might be related to VSCode. But because both commands run well in a Mac OSX terminal, I thought it might be of interest for you.

That's unfortunate, thanks for reporting it. Apparently IDF Monitor runs under Eclipse on OS X, so it's possible it will work under Atom.
It will depend a lot on how faithfully VSCode (or any other IDE/host) emulates a terminal, or whether it treats "make" as a non-interactive process (not an unacceptable assumption, really).
There might be something that can be done to detect non-terminal environments and disable some of the keyboard shortcut behaviour (which relies on terminal support), while keeping the basic monitor functionality.

Just to double-check: I'm guessing this is with the new idf_monitor functionally that was added yesterday? Is it the same if you "make simple_monitor" instead?

No, I guess it is the old one, because I don't currently have the "make simple_monitor" command. Need to upgrade later on. Will let you know.
Thanks for now

Well, the description on the ESP-IDF website regarding the new monitor seems to be a bit ahead the reality. I have cloned the github repositories again, but there is no
make simple_monitor
So I can't really say, whether there is the "old monitor" or the "new monitor" running. At least also the new monitor seems to require CTRL-[ to be terminated. On my MacBook this is "CTRL-ALT-6", but this combination is not working in the VSCode terminal yet.
Only unplugging the ESP32 dev board terminates the monitor.

I can confirm: It does not work with the latest IDF release (the one which contains the new monitor). Same behaviour as initially reported.

Hi @neilyoung,
Thanks for reporting this initially and being patient about it.
Since this issue was opened we have developed a new VSCode extension dedicated to IDF that includes monitoring functionality along with a lot of other features:
https://github.com/espressif/vscode-esp-idf-extension/
This is now the best option for using VSCode with ESP-IDF including monitoring device output.


Add Ipaddress support

Hi, I find ipaddress support is already in code, it's only need to add a little code to mapping the value, so I write it and test it in my server. Thanks.

@null64 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@null64 Thank you for signing the Contributor License Agreement!


Fixed Liquid warning on Interlock

Proposed changes
Fixed Liquid warning on Interlock introduced by https://github.com/docker/docker.github.io/commit/e692cd29c77396197e03b5ac67a363748d057ea3
Unreleased project version (optional)

Related issues (optional)

Deploy preview for docsdocker ready!
Built with commit 8b6d1b103bd05780ae1efc3e77f8a5ba6330b498
https://deploy-preview-9603--docsdocker.netlify.com


Python bindings

Originally opened by @jtrakk in https://github.com/cuelang/cue/issues/162
I'm wondering if CUE might support Python bindings.
As far as I know, the simplest and most widely supported interfaces are via CFFI, as in this Go example. Binaries can be distributed in the wheel format on PyPI.

There's this https://github.com/philipdexter/pycue which I created a long time ago


templates cleanup

Description
Cleanup of templates. Some better usage of filters like where_exp. cgi_escape for IDs.
Also removed continue statement inside of game.html which assumed it was being included inside of a for loop.
And inside rando.html fixed the standalone games list not being sorted.
If you merge https://github.com/video-game-randomizers/rando-list/pull/32 then you don't need to review this one,

this PR was obsoleted by https://github.com/video-game-randomizers/rando-list/pull/32


Integrate PHYTOS 31 leaf wetness sensor

Describe the Enhancement
Read a voltage measurement from the leaf wetness sensor and upload over LoRa to Dirtviz.
Benefits
Add a new sensor to the platform
Possible Drawbacks
N/A
Additional Context
The scope of the work is the following:

Measure voltage from the sensor
Add protobuf message for leaf wetness sensor
Integrate with sensor library to TX measurements

Will need to coordinate with Dirtviz team to add capabilities to display data.
Also @jmadden173 will update the issue with fields required for the leaf wetness sensor. Currently will just be voltage, but maybe some calibration or offset to convert 24 bit ADC reading to 16 bit to save space. It looks like we only need a 12 bit measurement according to the datasheet.
Link to sensor page: https://metergroup.com/products/phytos-31/
Manual: https://library.metergroup.com/Manuals/20434_PHYTOS31_Manual_Web.pdf
^ the sensor page is broken for me so here's the manual if that's the case
Issues #53 #50 are blockers.

Tagging @cjosephson
Caden is going to take a look at this once a sensor is available (invite to Github is in progress). Depending on progress @jmadden173 or @stevegtaylor will assist as needed.

I talked with Cristian who's doing the materials aspect of the leaf wetness sensor and it sounds like we should transmit the raw voltage reading and have another field for some future calibrated measurement. I guess both should be doubles after our experience with inconsistent float input parameters?

@gxjacobs Steve is working on the 58-integrate-phytos-31-leaf-wetness-sensor this Friday, if you have the free time to work it on it merge from that branch in order to not duplicate work.


Replacing the value of a field of a structured box can keep parts of the replaced value

Describe the bug
{box_name}.{field_name} = {value}. replaces the field {field_name} of box {box_name} created from a struct without considering the size of {value}. This issue tracks the bug when parts of the replaced value remain after replacing it with a byte array of a smaller size than the current value.
To Reproduce
#pragma version 8

struct UserInfo:
    favourite_colour: bytes[20]
end

if Txn.ApplicationID == 0:
    exit(1)
end

box<UserInfo> info_box = CreateBox("foo")
info_box.favourite_colour = "yellow"
info_box.favourite_colour = "red"
exit(1)

Expected behavior
Field favourite_colour of box with key "foo" should have a value of "red" but is instead "redlow".
Additional context
Related issue: #75

Discussed on Discord but want to mention here for visibility; this is being worked on as part of the current type checks work.


fix: invoke onProgress callback with DHT queries during routing

Allow passing an onProgress callback to the peer/content routers that can receive DHT query events.
Refs #1574

Converted to draft because we need to be a bit cleverer about how we expose the ProgressEvent types.
If we don't expose them all we get errors:
await name.resolve(key, {
  onProgress(evt) {
    if (evt.type === 'content-routing:get:dht:event') {

    }
  }
})

This comparison appears to be unintentional because the types '"ipns:resolve:start" |
"ipns:resolve:success" | ..(more events here).. and '"content-routing:get:dht:event"'
have no overlap.

The problem is we want to avoid exposing all the ProgressEvent types for all the content routing/peer routing implementations at the content routing/peer routing interface level.  Better to somehow aggregate the types based on the configuration passed to the libp2p factory function in a similar way to #1563

Closing in favour of #1975


Warn for dbt snapshot configurations containing target_schema or target_database

Describe the feature
Warn whenever the target_schema or target_database is configured for a dbt snapshot.
This is because the best practice in dbt v1.9+ for dbt snapshots is to use schema and database configs rather than target_schema or target_database. See "Additional context" below for more details.
Describe alternatives you've considered
Leave things as-is with no warning.
Who will this benefit?
This will benefit folks that want to use the best practices as it relates to configuring dbt snapshots.
Additional context
The feature for schema and database configs on snapshots is in https://github.com/dbt-labs/dbt-core/issues/10301, and this will be released as part of v1.9.
https://github.com/dbt-labs/docs.getdbt.com/issues/5805 describes the following changes this introduces for dbt snapshots:

target_schema is now optional for snapshots
if you do not set target_schema, your snapshot will respect generate_schema_name macro
if you do not set target_database, your snapshot will respect generate_schema_name macro
old behavior continues to work for backwards compatibility: so you can still set target_schema and/or target_database and that will be where your snapshot is built, but these are "old" configs
new configs for snapshots: you can now set database, schema, alias for your snapshots to be used by the generate_x_name macros

Is it really the remit of this package?
I feel like it should come as a warning from dbt Core directly, no?
I view this package more as a modelling best practice packages, not so much of a configuration best practice one.

If it doesn't go in either Core or dbt-project-evaluator, is there any other place you think it could go?
When @grace, Gerda, Michelle and myself discussed this, we decided not to raise a warning in dbt Core. We were hoping/thinking that project evaluator might be a good mechanism for this particular best practice (read below for more details).
More details
If we were going to deprecate target_schema and target_database, then we'd just raise a deprecation warning in dbt Core. But we're planning to continue to support these indefinitely, which would make them an optional "best practice" instead.
dbt Core has generally not raised warnings for best practices, and we've typically reserved WarnLevel warnings within dbt Core for things like:

deprecations (ex. PackageMaterializationOverrideDeprecation)
behavior changes (ex. SourceFreshnessProjectHooksNotRun)
invalid values (ex. InvalidValueForField)
configuration that won't have any affect and will be ignored (ex. UnusedResourceConfigPath)
configuration with potentially surprising consequences (ex. DepsUnpinned)

I definitely don't want to have to define new rules every time a field is not a best practice anymore but could maybe buy creating one single rule where we would bundle all the config that used to be standard and is not recommended anymore.
But one of the problems with this approach is that I guess that most dbt users don't install this package in their project.
Alternatives I am thinking of (which also could be put in addition of providing the feature in this package):

should we surface this in dbt Cloud somewhere? the same way that dbt Explorer shows recommendations
should we create a new subcommand in dbt-core, dbt best-practice or dbt recommendation that would list such changes (and maybe the recommendation to move from test to data_test as well. The advantage is that every use of dbt would have access to this, without installing a third party package

should we surface this in dbt Cloud somewhere? the same way that dbt Explorer shows recommendations

Good idea!

should we create a new subcommand in dbt-core

There's a really high threshold to add new subcommands to dbt-core, so we probably wouldn't for this. Instead, we're looking for linting of best practices to go into third party tooling.

I think this falls into the same category as the data_tests issue! we are not likely to pursue this warning in this package


remove needless circle ci cache

Issue

close #ISSUE_NUMBER

Overview (Required)

apparently caching license agreement files is old custom. It's needless now.

Links

Screenshot

Before
After

Thanks 👍


Add support for Unity Package Manager

Just by adding a package.json with the details as described here could allow zenject to be put in the new packages folder. This would allow the source code to not get in the way of projects.
Ideally a sub module with just the zenject code would go along way with frequent updates, especially when unity start supporting custom git manifest with their package manager UI.

I did some research on the topic and it seems that it is not as easy as adding a simple package.json file.
UPM does not support subdirectories at the moment and this requires us to have the exported project at the root directory (currently for unity it is located under UnityProject/Assets/Plugins/Zenject).
UPM, on the other hand, supports branches using a #branch suffix.
I did get it to work doing the following:

[ ] Cloning the repository into Packages/ of my project
[ ] Removing UnityProject/Assets/Plugins/Zenject/OptionalExtras
[ ] Adding package.json under UnityProject/Assets/Plugins/Zenject
[ ] Adding dependency in the manifest.json

"me.svermeulen.zenject": "file:./Zenject/UnityProject/Assets/Plugins/Zenject",

This is the "local file" way of doing. This is not fully equal to the "git" way of doing. These changes are significantly modifying the project in whole and should only be done in cooperation with @svermeulen
At this point I offer my help with this topic as this is a super important feature (for me at least).
Everything I know comes from https://forum.unity.com/threads/git-support-on-package-manager.573673/

Hopefully, the will add an option for subdirectories when they officially release the git support for UPM.
Then just moving the UnityProject/Assets/Plugins/Zenject/OptionalExtras folder up or moving assembly definition and package.json to the UnityProject/Assets/Plugins/Zenject/Source folder should be required.

Could you please add the package.json file?
I would like to use it as @MeikelLP mentioned.
Then at least this step is done.

If you approve I can integrate simple Travis Ci script that pushes required files to separate branch so you can use it with UPM:
https://github.com/Hermesiss/unity-package-manager-ci

I made a fork which seems to work. I can at least call Zenject code from within my code (after referencing the .asmdef file).
You can use it like this:
"com.modesttree.zenject": "https://github.com/MeikelLP/Zenject.git#upm",


Dual Licence

Hi, as there are thoughts about getting lessjs under dual licence (gplv2 compatible), do you want to go the same road ? It would be awesome if we could use less.php in GPLv2 projects (like Joomla).

Would you consider dual licensing so that the php is compatible with MIT/GPL (towards OSS CMS's) and Apache (towards the less.js).
PS: GPL is not so strict towards js/css files. It is strict towards mainly php (and other server side code).

Hi this can be licenced to what ever you want without having to wait for less.js to do it since https://github.com/leafo/lessphp has a dual license.

It can be dual licensed I added MIT and GPL version 2 and 3.

this can be licenced to what ever you want without having to wait for less.js to do it since https://github.com/leafo/lessphp has a dual license

Note, aside from the lessc adaptor, our project has nothing to do with leafo/lessphp.


fix: change the way of creating host name which is an id in the database

This is the fix of following issue.
In the database we store data with host _id of structure -> ip_address:port
For now we save two things to mongo, MIB-REAL-TIME-DATA and MIB-STATIC-DATA. It looks like:
{      "_id" : "<IP_ADDRESS>:161",      "MIB-REAL-TIME-DATA" : {         "<IP_ADDRESS>.<IP_ADDRESS>.0" : {             "value" : "125535155",              "type" : "TimeTicks"         }     },      "MIB-STATIC-DATA" : {         "IF-MIB" : [             {                 "interface_index" : [                     "1",                      "2"                 ]             },              {                 "interface_desc" : [                     "lo",                      "eth0"                 ]             }         ]     } }
During first walk operation, firstly host id is being added along with MIB-REAL-TIME-DATA. In case of enricher presence MIB-STATIC-DATA is inserted to the "ip_address:port" structured host id which - we assume - exists.
But in scheduler-inventory.yml host with or without port can be provided. In case user typed bare ip address, in mongo db id was exactly the same:
{      "_id" : "<IP_ADDRESS>",
and then in enrichment phase we encountered problem with absent hostname "<IP_ADDRESS>:161".

:tada: This PR is included in version 1.5.0-develop.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Please publish for Scala 2.13.15

which is now on Maven Central, as per https://contributors.scala-lang.org/t/scala-2-13-15-release-planning/6649/11

Released in Ammonite 3.0.0


editor.formatOnType does not respect editor.insertSpaces setting

VSCode Version:
1.6.1
OS Version:
OSX (10.11.6)

Searchable description
VS Code keeps changing some lines to have spaces instead of tabs in the leading whitespace.
Steps to Reproduce:
Use these settings:
"editor.tabSize": 4,
"editor.insertSpaces": false,
"editor.detectIndentation": false,
"editor.formatOnType": true,
Type some code that triggers formatOnType to activate a format change.
Expected behaviour:
Line is formatted using tabs for leading whitespace, because of the insertSpaces setting.
Actual behaviour:
Line is formatted with spaces instead of tabs for the leading whitespace.

Is this in an html file? Could be #13563

No, this is while editing C#

Related @aeschli?

This issue was moved to OmniSharp/omnisharp-vscode#834


updated to work with bevy 0.13

There' s a problem, maybe. In material.rs, line 349, the type Opaque3d now has an asset_id field. I set it to AssetId::default(), which seems wrong, as that would point to nothing.
Despite this, all the examples ran correctly.
¯_(ツ)_/¯

Closed in favor of #61


Result not produced

First of all great contribution and thanks for sharing the code. I tried to  use it both building locally and using the docker version, but in both cases I don't see any file created with the compensated point cloud. There is just the folder which is supposed to contain the corrected files.
Thanks for the attention

Thanks for trying out the project! I just ran the current docker pipeline and it worked as I expected.
I would recommend that you get the latest version of the master, make sure your kitti dataset is installed as expected and try again.
If it still does not work please describe the problem as explicitly as you can, and what exact steps I can take to reproduce it.
Good luck!


bug: button-bar not styled correctly

The button-bar component is no longer being styled correctly in the latest version 1.2.4.
See example here:
http://codepen.io/anon/pen/VepBEQ?editors=100
Compare this:

To the documentation:

+1, We are also facing the same issue. Its introduced newly from 1.2.0.

Fixed, thanks!

I think the underlying issue here may actually be related to the button-style mixin as I'm seeing the same issue on other buttons. Please see this issue
https://github.com/driftyco/ionic/issues/5576


Rebase/develop with main

Description
Rebased develop branch with the main branch.

Closing this pull request to create a new one