Add Select() variant that exposes metadata

For operator telemetry in https://github.com/thanos-community/promql-engine we would like to have metadata about the Select() function such as how much data and how fast it was retrieved from each StoreAPI. I suggest adding something like SelectWithMetadata() that returns extra information. This later could be used by promql-engine if query analysis is enabled.

Hey @GiedriusS , can you please suggest files through which I can debug the process ?
Thank you

@GiedriusS I have also sent you an email :)

Hey @GiedriusS I'll take this up for LFX :)
Any docs or past references to understand the implementation logic better ?

Hello @GiedriusS 👋
I'm Pranit Patil, a student pursuing a Bachelor's degree in Computer Science at Mumbai University. Recently, I completed my internship at hubx.ai, where I worked as a full-stack developer intern. Prior to that, I gained experience as a front-end developer intern at Tech Cryptors.
My skills include JavaScript, ReactJS, Node, Express, MongoDB, and CSS libraries, such as Bootstrap. Through various projects, including full-stack ones, I have honed my expertise in full-stack development
I'm keen on participating in the LFX mentorship program and becoming an active community member. I kindly request your assistance in guiding me through project discussions.
Thank you.

Thanks for everyone's interest! I suggest first of all trying to compile and run Thanos & Prometheus locally. Then, you can try improving the documentation if you see any problems with it. You can also take a look at https://github.com/thanos-io/thanos/issues?page=1&q=is%3Aissue+is%3Aopen+label%3A"help+wanted", maybe https://github.com/thanos-io/thanos/issues/4664 looks like a good candidate for starters. :smile:

Hey! @GiedriusS , I am Shashank Mittal pursuing my undergrad at IIT BHU (Indian Institute of Technology (BHU) Varanasi). I am highly interested in Open Source and Software Development. I would love to contribute to Thanos and participate in this LFX Fall'23!


Honda Accord EX 2018 “Vehicle Parameter Identification Failed” error on Comma 3

Describe the bug
Having issue with “Vehicle Parameter Identification Failed” error on Comma 3. Error happens randomly pretty often (<30 min between triggers) mostly appear as red screen error, but sometimes as gray preventing from activating OP. Never happened on Comma 2 before on same car.
What hardware does this issue affect?
comma three
Which car does this affect?
Honda Accord EX 2018
Provide a route where the issue occurs
c8aab54281c1f4db|2021-10-18--20-51-31--11
openpilot version
any release3 thru 0.8.10
Additional info
I believe issue is similar to that ticket https://github.com/commaai/openpilot/issues/21909
Dongle id c8aab54281c1f4db
drives:
c8aab54281c1f4db|2021-10-18--20-51-31--11 at 21:03:25
c8aab54281c1f4db|2021-10-22--22-04-22--2 at 22:07:01
c8aab54281c1f4db|2021-10-25--18-41-45—5 at 18:47:27

Updated to released today 0.8.10, still having issue.
c8aab54281c1f4db_2021-11-01--18-40-09--17--rlog.bz2.zip ~18:57:21
c8aab54281c1f4db_2021-11-01--20-25-06--26--rlog.bz2.zip ~ 20:53:00
Also I've noticed broken pixels on videos, is that something I should worry about?

No need to worry about those dead subpixels. Won't affect driving.
Your old dongle ID was 0a27f45fa0ef0d41, which had similiar offsets of -8 degrees (e.g. 0a27f45fa0ef0d41|2021-10-05--22-01-19).  When driving straight, does your steering wheel look straight?

Not really, steering wheel looks few degrees to the left, but it's been like that for awhile maybe a year. I imagine it's not something I can check myself this sensor? I have a bluedriver, but not a dealership level scan tool. Ok, so I go do wheels alignment somewhere and see if that helps?

If you can see the steering wheel being offset it's probably not the sensor. An alignment will probably fix your issues. Make sure they also take care of making sure the steering wheel is straight.

Did alignment, drove ~300 miles so far no error, thank you! It seems like not the most uncommon issue, maybe add suggestion to do alignment except just “Vehicle Parameter Identification Failed” which doesn't tell much to unexperienced users. Really appreciate all the help!

Great to hear. Your new angle offset looks about -1.5 deg, which is fine!
I'll think about a separate alert that just looks at large average angle offset and recommend alignment


error: unresolved import std::os::macos::fs::MetadataExt. Could not find macos in `std::os

Hello!
I'm trying Iron Framework and have such error during compiling it's https://github.com/iron/staticfile.git middleware. There is filetime 0.1.2 dependence and as I see, main reason is in this library.
Os: Mac Os X 10.10.3
Error log from cargo:
/Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/filetime-0.1.2/src/lib.rs:83:29: 83:57 error: unresolved import std::os::macos::fs::MetadataExt. Could not find macos in std::os
/Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/filetime-0.1.2/src/lib.rs:83                         use std::os::$i::fs::MetadataExt;
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/filetime-0.1.2/src/lib.rs:77:9: 96:10 note: in expansion of birthtim!
/Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/filetime-0.1.2/src/lib.rs:98:9: 104:10 note: expansion site
error: aborting due to previous error
Thank you!

Thanks for the report! Unfortunately this library currently only compiles on the nightly channel of Rust due to its usage of unstable features. These features will soon make their way into beta, however, and they're likely to be stable for 1.1, so this shouldn't be required for too long!

@alexcrichton , thank you!
curl https://static.rust-lang.org/rustup.sh > rustup.sh;
rustup.sh --channel=nightly;
Helped =)

Is this still a feature requiring Rust nightly?

As of 1.1 this library should work on stable (it just doesn't work on 1.0)


unable to retrieve app info

I love the idea of running this in an action; I actually found my way here because I have something in my settings config that is causing probot/settings to fail, but debugging that is incredibly frustrating since I can't get any negative feedback from the app.
Unfortunately, I've run into some fatal issues that are blocking me using this too.
When I attempt to run this, using a workflow definition essentially identical to the one in the readme[1], I get the following error: Probot is unable to retrieve app information from GitHub for event subscription verification[2].
Looking at where probot raises that error[3], it looks like this is caused by failing to get credentials. The comments talk about credentials needed when it is running as an app, but it's not clear to me (node is not my jam) whether it requires that or will work equally well with a github token as shown in this project's readme.
Any ideas what might be going on here?
[1] https://github.com/mattsb42/rhodes/blob/7ac0b11b2044356b680cdcfedf666b8a44add245/.github/workflows/settings.yaml
[2] https://github.com/mattsb42/rhodes/commit/672e3eb469cf3eaa5d08bc299c780d95116d40a1/checks?check_suite_id=381214232
[3] https://github.com/probot/probot/blob/28a4d43185b57620508563e07df295b41e92423a/src/webhook-event-check.ts

i am facing same issue. :(

@abhithakre, you might be interested in repo-manager[1]. After playing around with this project and Probot for a while I ended up making that to give a full native GitHub Actions experience.
[1] https://github.com/marketplace/actions/repo-manager

+1


Error message when deploying flists (ubuntu) while flist does get deployed and operates as expected

Description
Used online 3bot to deploy ubuntu flist (version 20) and manually selected node to deploy on.  Deployment is functional (see screenshot) but does present an error message.  repeated the process twice (same everything, including farm etc) and got the same response.

@muhamadazmy seems it's the same here

Verified after merging the TRC container with 3Bot flist

Verified after merging the TRC container with 3Bot flist


Installing and running IReS

Hi,
I just tried to make a local installation. I cloned the GitHub repo, defined the IRES_HOME env. var, run install.sh, giving the YARN_HOME when requested.
So far, ok. Then, when I start the server, I get:
./install.sh -r start
IReS-Platfrom home folder is /Users/philippe/IRES/IReS-Platform
start-ing ASAP server
/Users/philippe/IRES/IReS-Platform/asap-platform/asap-server/src/main/scripts/asap-server: line 24: cd: /Users/npapa/Documents/workspaceASAP/IReS-Platform/asap-platform/asap-server/target: No such file or directory
So, there is some harcoded path somewhere. I have a Mac Book. I' like to stabilize the installation process before asking my team to try again on the cluster.
Thx
Philippe

Hi Phillipe,
Due to an issue related to the sed command, several issues may occur during the installation in a Mac Book. Such errors occurs because an Ubuntu-based OS provides a GNU sed while the OS X provides a BSD sed. Check this related topic in StackOverflow: http://stackoverflow.com/questions/16745988/sed-command-works-fine-on-ubuntu-but-not-mac
Finally we made some changes (see commit https://github.com/project-asap/IReS-Platform/commit/6723ae1f8ec2f9ca0a2cda337c954c56d69ef868) in order to make the script work in both systems. We tested it both in a Mac Book and an Ubuntu Server and everything works well.
Please try to install IReS again as follows:

git clone git@github.com:project-asap/IReS-Platform.git
cd IReS-Platform
./install.sh
4 ./install.sh -r start

Best,
Victor

Yes, it works! Bravo.
Ok, let's try now on our Debian cluster.
Many thanks

Solved.


Installing procedure of Azure CLI is completing, and then again the install option is coming. I tried repair option as well, but nothing happened.

Related command

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

Thank you for opening this issue, we will look into it.

Please provide detailed error info.

If you see the repair option, it means you have installed the cli. You can try to run az command in PowerShell.

Thanks for the help. I was already using powershell. Actually, I am learning it which is why trying to access using CLI and other methods.


Stale alerts for pods/nodes that don't exist (5.5.52+)

Description
We have 2 tickets open regarding high memory alerts on pods that either do not exist (SE-19032 "gravity status is showing alerts for pods which do not exist", SE-19128 "When are Gravity alerts cleared?").
Though the pod alerts are custom TICK scripts by the customer, I've managed to reproduce this with our shipping high memory alerts for nodes.
What happened: gravity status shows alerts for pods/nodes that do not exist, ex. Cluster alerts: * [CRITICAL] CRITICAL / ... pod ...-...-container-UUID has high memory usage: 90.01%".
In SE-19128, customer sees the alert for more than a month even though the apps are not running.
What you expected to happen: No alerts for pods/nodes that do not exist after 10+ minutes.
How to reproduce it (as minimally and precisely as possible):

Install a 3 node gravity 5.5.52+ cluster (tested with 5.5.56)
Install stress test from https://github.com/giantswarm/kube-stresscheck
watch sudo gravity status.  Wait 5 minutes.  You will start seeing high memory usage alerts for the node with the stress check pod.
While you still have the high memory alerts present, sudo gravity remove node containing the stress-test pod.  (do not evict pods manually or remove the stress test pod, just run the gravity remove.
Keep watching gravity status.  Note the shrink operation completes, but you'll continue to see the high memory usage alert on the removed node's IP.  You will even get a NEW alert for the removed node saying br_netfilter module not loaded, after the node is already removed.  You can shut down the node and the alerts will remain.  Also note that in this case, the removed node did not have kapacitor on it.
Even after 1 hour, you will still see stale alerts in gravity status:

Every 2.0s: sudo gravity status                                                                                node2: Wed Jan 27 00:43:27 2021

Cluster name:           awesomewescoff5340
Cluster status:         active
Application:            cluster-image, version 0.0.2
Gravity version:        5.5.56 (client) / 5.5.56 (server)
Join token:             vagrant_install
Last completed operation:
    * operation_shrink (6198670a-3e8d-495c-853d-89f8cb611c86)
      started:          Tue Jan 26 23:38 UTC (1 hour ago)
      completed:        Tue Jan 26 23:39 UTC (1 hour ago)
Cluster endpoints:
    * Authentication gateway:
        - <IP_ADDRESS>:32009
        - <IP_ADDRESS>:32009
    * Cluster management URL:
        - https://<IP_ADDRESS>:32009
        - https://<IP_ADDRESS>:32009
Cluster nodes:
    Masters:
        * node2 (<IP_ADDRESS>, node)
            Status:             healthy
            Remote access:      online
        * ubuntu-focal (<IP_ADDRESS>, node)
            Status:             healthy
            Remote access:      online
Cluster alerts:
        * [WARNING] WARNING / Node <IP_ADDRESS> has high memory usage: 80.56850242888261%
        * [CRITICAL] br_netfilter module is not loaded on node <IP_ADDRESS>
        * [WARNING] WARNING / Node <IP_ADDRESS> was rebooted

Can attach gravity report and kapacitor info, if needed.
Environment

Gravity version [e.g. 7.0.11]: 5.5.56, also first seen by customer in 5.5.52, when #2039 was added
OS [e.g. Redhat 7.4]: Ubuntu 20.04
Platform [e.g. Vmware, AWS]: AWS, local

Workaround
Manual workaround to remove the stale alert (side effect: removes alert history)

Inspect the kapacitor pod and look at the alerts
kubectl -n monitoring exec kapacitor-74bdc655-m4thr -c alert-loader -- kapacitor --url http://localhost:9092 list topics
Show the alert details for the alert you want to delete:
kubectl -n monitoring exec kapacitor-74bdc655-m4thr -c alert-loader -- kapacitor --url http://localhost:9092 show-topic main:uptime:alert9
Delete the alert you want to remove:
kubectl -n monitoring exec kapacitor-74bdc655-m4thr -c alert-loader -- kapacitor --url http://localhost:9092 delete topics main:uptime:alert9
Ref: https://docs.influxdata.com/kapacitor/v1.5/working/cli_client/#delete-topics

Quick bash script that implements the workaround and can be scheduled via cron.  You will need to modify the alert topic name (in the case below, it's main:high_memory:alert9)
#!/bin/bash
#
# quick way to delete high memory alerts (also deletes alert history)
# see https://docs.influxdata.com/kapacitor/v1.5/working/cli_client/#delete-topics for usage examples
# use list topics to see current alerts, and show-topic to show the alert contents
# can also use globs, such as delete topics "*high_memory*"
#
POD=$(kubectl get pod -l app=monitoring,component=kapacitor -n monitoring -o jsonpath="{.items[0].metadata.name}")
kubectl -n monitoring exec -ti $POD -c alert-loader -- kapacitor --url http://localhost:9092 delete topics main:high_memory:alert9

This actually seems like a kapacitor problem:
https://community.influxdata.com/t/kapacitor-stateless-alerts/1647
https://community.influxdata.com/t/how-to-delete-an-alert-event/6941/7

This actually seems like a kapacitor problem:
https://community.influxdata.com/t/kapacitor-stateless-alerts/1647
https://community.influxdata.com/t/how-to-delete-an-alert-event/6941/7

One thing suggested today that we could do to the old 5.5.x version is rollback #2039 and move the alerts to something like gravity status --alerthistory with a note that mentions that due to kapacitor limitations, some of these alerts may be for resources that no longer exist.

One thing suggested today that we could do to the old 5.5.x version is rollback #2039 and move the alerts to something like gravity status --alerthistory with a note that mentions that due to kapacitor limitations, some of these alerts may be for resources that no longer exist.


Issues with Saving and Loading

Thanks for this awesome library!  I'm still quite new at all this, so this is probably something simple.  I'm just trying to simply train and load the categorizer. I'm using Python 3.9.
import spacy
import classy_classification
import json

data = json.load(open('./../aitrain_small.json', 'r'))
nlp = spacy.load("en_core_web_md")
nlp.add_pipe(
    "text_categorizer",
    config={
        "data": data,
        "model": "spacy"
        }
)

print(nlp("Ability to multi-task in a fast paced detail oriented environment.")._.cats)
nlp.to_disk('small_text_cat')

This seems to save successfully.

Trying to load this separately is when the error happens.
import spacy
import classy_classification

nlp = spacy.load("small_text_cat")
print(nlp("Ability to multi-task in a fast paced detail oriented environment.")._.cats)

Here's the error:
Traceback (most recent call last):
File "/Users/manicho/Mine/Projects/AIVizi/trainingData/usesaved.py", line 6, in
nlp = spacy.load("small_text_cat")
File "/opt/homebrew/lib/python3.9/site-packages/spacy/init.py", line 51, in load
return util.load_model(
File "/opt/homebrew/lib/python3.9/site-packages/spacy/util.py", line 422, in load_model
return load_model_from_path(Path(name), **kwargs)  # type: ignore[arg-type]
File "/opt/homebrew/lib/python3.9/site-packages/spacy/util.py", line 488, in load_model_from_path
nlp = load_model_from_config(
File "/opt/homebrew/lib/python3.9/site-packages/spacy/util.py", line 528, in load_model_from_config
nlp = lang_cls.from_config(
File "/opt/homebrew/lib/python3.9/site-packages/spacy/language.py", line 1783, in from_config
nlp.add_pipe(
File "/opt/homebrew/lib/python3.9/site-packages/spacy/language.py", line 792, in add_pipe
pipe_component = self.create_pipe(
File "/opt/homebrew/lib/python3.9/site-packages/spacy/language.py", line 674, in create_pipe
resolved = registry.resolve(cfg, validate=validate)
File "/opt/homebrew/lib/python3.9/site-packages/thinc/config.py", line 746, in resolve
resolved, _ = cls._make(
File "/opt/homebrew/lib/python3.9/site-packages/thinc/config.py", line 795, in _make
filled, _, resolved = cls._fill(
File "/opt/homebrew/lib/python3.9/site-packages/thinc/config.py", line 867, in _fill
getter_result = getter(args, **kwargs)
File "/opt/homebrew/lib/python3.9/site-packages/classy_classification/init.py", line 41, in make_text_categorizer
return classySpacyInternal(
File "/opt/homebrew/lib/python3.9/site-packages/classy_classification/classifiers/spacy_internal.py", line 22, in init
self.set_training_data()
File "/opt/homebrew/lib/python3.9/site-packages/classy_classification/classifiers/classy_skeleton.py", line 113, in set_training_data
self.X = self.get_embeddings(X)
File "/opt/homebrew/lib/python3.9/site-packages/classy_classification/classifiers/spacy_internal.py", line 36, in get_embeddings
embeddings = [self.get_embeddings_from_doc(doc) for doc in docs]
File "/opt/homebrew/lib/python3.9/site-packages/classy_classification/classifiers/spacy_internal.py", line 36, in
embeddings = [self.get_embeddings_from_doc(doc) for doc in docs]
File "/opt/homebrew/lib/python3.9/site-packages/spacy/language.py", line 1576, in pipe
for doc in docs:
File "/opt/homebrew/lib/python3.9/site-packages/spacy/util.py", line 1602, in _pipe
yield from proc.pipe(docs, **kwargs)
File "spacy/pipeline/transition_parser.pyx", line 230, in pipe
File "/opt/homebrew/lib/python3.9/site-packages/spacy/util.py", line 1551, in minibatch
batch = list(itertools.islice(items, int(batch_size)))
File "/opt/homebrew/lib/python3.9/site-packages/spacy/util.py", line 1602, in _pipe
yield from proc.pipe(docs, **kwargs)
File "spacy/pipeline/pipe.pyx", line 53, in pipe
File "/opt/homebrew/lib/python3.9/site-packages/spacy/util.py", line 1602, in _pipe
yield from proc.pipe(docs, **kwargs)
File "spacy/pipeline/pipe.pyx", line 53, in pipe
File "/opt/homebrew/lib/python3.9/site-packages/spacy/util.py", line 1602, in _pipe
yield from proc.pipe(docs, **kwargs)
File "spacy/pipeline/trainable_pipe.pyx", line 73, in pipe
File "/opt/homebrew/lib/python3.9/site-packages/spacy/util.py", line 1551, in minibatch
batch = list(itertools.islice(items, int(batch_size)))
File "/opt/homebrew/lib/python3.9/site-packages/spacy/util.py", line 1602, in _pipe
yield from proc.pipe(docs, **kwargs)
File "spacy/pipeline/transition_parser.pyx", line 230, in pipe
File "/opt/homebrew/lib/python3.9/site-packages/spacy/util.py", line 1551, in minibatch
batch = list(itertools.islice(items, int(batch_size)))
File "/opt/homebrew/lib/python3.9/site-packages/spacy/util.py", line 1602, in _pipe
yield from proc.pipe(docs, **kwargs)
File "spacy/pipeline/trainable_pipe.pyx", line 73, in pipe
File "/opt/homebrew/lib/python3.9/site-packages/spacy/util.py", line 1551, in minibatch
batch = list(itertools.islice(items, int(batch_size)))
File "/opt/homebrew/lib/python3.9/site-packages/spacy/util.py", line 1602, in _pipe
yield from proc.pipe(docs, **kwargs)
File "spacy/pipeline/trainable_pipe.pyx", line 79, in pipe
File "/opt/homebrew/lib/python3.9/site-packages/spacy/util.py", line 1621, in raise_error
raise e
File "spacy/pipeline/trainable_pipe.pyx", line 75, in spacy.pipeline.trainable_pipe.TrainablePipe.pipe
File "/opt/homebrew/lib/python3.9/site-packages/spacy/pipeline/tok2vec.py", line 125, in predict
tokvecs = self.model.predict(docs)
File "/opt/homebrew/lib/python3.9/site-packages/thinc/model.py", line 315, in predict
return self._func(self, X, is_train=False)[0]
File "/opt/homebrew/lib/python3.9/site-packages/thinc/layers/chain.py", line 54, in forward
Y, inc_layer_grad = layer(X, is_train=is_train)
File "/opt/homebrew/lib/python3.9/site-packages/thinc/model.py", line 291, in call
return self._func(self, X, is_train=is_train)
File "/opt/homebrew/lib/python3.9/site-packages/thinc/layers/chain.py", line 54, in forward
Y, inc_layer_grad = layer(X, is_train=is_train)
File "/opt/homebrew/lib/python3.9/site-packages/thinc/model.py", line 291, in call
return self._func(self, X, is_train=is_train)
File "/opt/homebrew/lib/python3.9/site-packages/thinc/layers/concatenate.py", line 44, in forward
Ys, callbacks = zip([layer(X, is_train=is_train) for layer in model.layers])
File "/opt/homebrew/lib/python3.9/site-packages/thinc/layers/concatenate.py", line 44, in
Ys, callbacks = zip([layer(X, is_train=is_train) for layer in model.layers])
File "/opt/homebrew/lib/python3.9/site-packages/thinc/model.py", line 291, in call
return self._func(self, X, is_train=is_train)
File "/opt/homebrew/lib/python3.9/site-packages/thinc/layers/chain.py", line 54, in forward
Y, inc_layer_grad = layer(X, is_train=is_train)
File "/opt/homebrew/lib/python3.9/site-packages/thinc/model.py", line 291, in call
return self._func(self, X, is_train=is_train)
File "/opt/homebrew/lib/python3.9/site-packages/thinc/layers/with_array.py", line 30, in forward
return _ragged_forward(
File "/opt/homebrew/lib/python3.9/site-packages/thinc/layers/with_array.py", line 90, in _ragged_forward
Y, get_dX = layer(Xr.dataXd, is_train)
File "/opt/homebrew/lib/python3.9/site-packages/thinc/model.py", line 291, in call
return self._func(self, X, is_train=is_train)
File "/opt/homebrew/lib/python3.9/site-packages/thinc/layers/concatenate.py", line 44, in forward
Ys, callbacks = zip([layer(X, is_train=is_train) for layer in model.layers])
File "/opt/homebrew/lib/python3.9/site-packages/thinc/layers/concatenate.py", line 44, in
Ys, callbacks = zip(*[layer(X, is_train=is_train) for layer in model.layers])
File "/opt/homebrew/lib/python3.9/site-packages/thinc/model.py", line 291, in call
return self._func(self, X, is_train=is_train)
File "/opt/homebrew/lib/python3.9/site-packages/thinc/layers/chain.py", line 54, in forward
Y, inc_layer_grad = layer(X, is_train=is_train)
File "/opt/homebrew/lib/python3.9/site-packages/thinc/model.py", line 291, in call
return self._func(self, X, is_train=is_train)
File "/opt/homebrew/lib/python3.9/site-packages/thinc/layers/hashembed.py", line 61, in forward
vectors = cast(Floats2d, model.get_param("E"))
File "/opt/homebrew/lib/python3.9/site-packages/thinc/model.py", line 216, in get_param
raise KeyError(
KeyError: "Parameter 'E' for model 'hashembed' has not been allocated yet."
Looking at the KeyError, it looks it's something with the Tok2Vec pipeline, but I'm unsure how to rectify this.  I'm guessing I'm doing something wrong in general for saving and loading, and hoping you can point me in the right direction?  Thanks in advance!

@manuelnelson thanks for the reproducible example. It is not working since i haven't spend time on creating correct serialization methods for the classification models. I won't spend time on this any time soon, but maybe one day in the future, I will add it.

I also don't fully understand why you need to save the actual model since the approach is heavily focused on creating a low-key few/zero-shot approach, which relies on the input data and not the actual training. Meaning that saving the data should be enough for reasonably reproducing the model predictions.


fix: can move object up and down, corrected use of iterators

Branched from #334, so that must be merged first.

Thank you for your work Gerard! I left some questions, but the code looks great. I will check now that everything is fixed

Any idea why this stopped working? It is weird that it previously worked but now it only works when an GameObject has an actual child.

Looking at the history, I think it was some of the changes David did optimizing the window. Previously we checked the children of the parent, but he changed it to check your own children. Easy to mix up with so many game objects to consider ^^'


New version: GitKraken.cli 1.0.7

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/112345&drop=dogfoodAlpha

@wingetbot run


Adding images to labels

I need to add images to labels area.
As here

I created bar chart
    /**
     * Init persons chart
     */
    var data = {
        labels: [
            ' Person name',
            ' Person name',
            ' Person name',
            ' Person name',
            ' Person name',
            ' Person name',
            ' Person name',
            ' Person name',
            ' Person name',
            ' Person name',
        ],
        series: [
            [1, 2, 3, 4, 5]
        ]
    };

But see this, and inline styles dont working

@codev0 Sorry for the late reply. Did you figured out a solution yet? I can definitely take a look and see help you find the best option.

Hi.
No, I did't. It would be nice

+1

+1

+1

+1

+1

I'm sorry this took so long. After a bug which needed to be fixed for namespaced attributes, this can now be done relatively easy. http://jsbin.com/dilojuh/1/edit?js,output

Closing this for now, you should use SVG to draw this kind of chart.

Hello gionkunz,
I am trying to adapt your code to add similar photos in a horizontal stacked bar taking the svg images from my disk but I get the same error than codev0 and I cannot even show stacked bars. Could you please help?


How to get current release version from client?

Client will report the release key to tracer everytime the config is updated, see RemoteConfigRepository
For spring boot apps, we are considering to write a custom infoContributor so that more information could be seen via /info endpoint.

reference https://github.com/apolloconfig/apollo/issues/5113


Typo in debuglog configuration

statsd-client
https://github.com/msiebuhr/node-statsd-client/blob/691a15dca90ad49d31b3aae6bddbf94b19193c43/lib/TCPSocket.js#L2

Released as 0.4.5


MSYS2 package update for guile-2.2.2

New package setup with several fixes. Works fine for me.
guile-readline is also working.

It passes AppVeyor x86_64-pc-msys but hangs on tea during configure:
checking what kind of threads to support... pthreads
err:seh:setup_exception stack overflow 7344 bytes in thread 01c6 eip 000000007bc99c63 esp 00000000ffff8950 stack 0xffe00000-0xffffa000-0x100000000
I assume this due to a tea vm issue but not the guile package under test. How to proceed?

Tea is basically Cygwin under Wine, ignore it.


Flow doesn't refine arrays using instanceof Array

/* @flow */

function wrapArray(x: Array<number> | number): Array<number> {
  if (x instanceof Array) {
    return x;
  } else {
    return [x];
  }
}

Expected: No errors!
Actual:
test.js|3 col 23 error|  array type
|| This type is incompatible with
test.js|3 col 54 error|  number
||

Workaround: Array.isArray instead of instanceof

Here's the problem: this also happens instanceof check.
var phony = Object.create(Array.prototype);
phony instanceof Array // true
Array.isArray(phony) // false

And this most certainly is not an Array instance. I doubt this is ever going to get fixed.

Closed by 05697a1.
I think Object.create(Array.prototype) instanceof Array already "worked" since Object.create(Array.prototype) creates an InstanceT of the Array class and instanceof's job is to see if the RHS is in the prototype chain of the LHS, which it is in that case. On the other hand, Array<T> is special-cased to create an ArrT, and flow didn't know the relationship between ArrT and the Array class.
Fixing this also refines away other things that are clearly not possible, like number in the example above so I think it's worth doing.

:clap:


Changing the primary color?

Is there any chance to change the primary color?
With /styles/sidebar.scss I could change the color of the sidebar.
But the rest is always in blue.
Is there any efficient way?

https://github.com/PanJiaChen/vue-element-admin/blob/master/src/styles/element-variables.scss
https://element.eleme.cn/#/en-US/component/custom-theme


ARM Support

It would be really nice to have a debian package compiled for arm. I tried really hard to compile it on my own on my chromebook running debian jessie but i failed -.-. maybe there is somone with more expertise who could build brackets for arm.

Thanks @leoek . our expertise in Linux on ARM is a bit inadequate and there is not enough users to justify a large scare ARM push from the core team. Perhaps you could help with porting https://github.com/adobe/brackets-shell into ARM.
Duplicate of https://github.com/adobe/brackets/issues/10298
Closing.


Error: Invariant failed: WalletLink / Coinbase connector not found, please make sure it is provided to your

Out of nowhere I started getting this error being thrown in my Next.js project.  Even with just the JS starter project, immediately after adding in useCoinbaseWallet hook. Have a solid app that has been under testing last two weeks with no issue. ive had varying different configs for the ThirdWebProvider, but it fails even with the defaults?  Any suggestions?

thanks for the report @alaaan, this is fixed in 2.0.7: https://github.com/thirdweb-dev/react/releases/tag/v2.0.7


fix: detect mainnet fork correctly

This changes how development network is detected to a recommended method and fixes a bug with mainnet-fork being considered a live network.

👍🙏


edupont04 from OPS portal: Merge from master to live

Docs Build status updates of commit df4276a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

dynamics-gp/payroll/W-2-statement.md
:white_check_mark:Succeeded
View

dynamics-gp/payroll/us-year-end.md
:white_check_mark:Succeeded
View

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.


README.md for each subdirectory

https://github.com/scylladb/alternator-load-balancing now has an overall README.md explaining the purpose of the repository, but we also need a separate README.md in each subdirectory to explain how to use the support for the individual languages. We have some explanations in comments, but they should be in a README file, so the user doesn't need to guess which file to look at for comments.
Requested by @slivne

The the above merge and two commits added all the missing README.md's.


Update ViewStub margin if doesn't have ActionBar

In the actual setup, if you hide the ActionBar, the ViewStub keeps the margin top, that generates a blank space above the content.
This PR implements a margin reset in case ActionBar is hidden.
This probably fix #59 and #104.

@renatoagds Can you provide screen shots before and after?

@henrikra for sure! Let's use a GIF to explain the interaction before and after my patch.
The second screen is register with this config:
Navigator.registerScreen('OrderDetail', () => require('./order-detail'), {
  initialConfig: {
    hidden: true
  }
});

Before

After

Oh nice! And iOS side does not have this problem?

@henrikra I can't say about iOs env, I'm not working with directly with it.

@gpeal Could we merge this? :D Looks like it is working

@lelandrichardson Any updates on this? Would love to see this pr merged!

🍰


Add configurable UI filter for null providers

Overview
Makes showing null data providers in the UI optional (doesn't apply to newly added providers which haven't yet been assigned a type).
This becomes important for filtering provider types in the UI, since filtering happens via the attribute (incoming in #9670). If the type isn't loadable, the attribute isn't loadable, and the type is unfiltered in the UI and can be confusing.
For debugging purposes, the checkbox in settings can be enabled to make all providers visible.
Changes

Part of #9419

/azp run


Create Navbar component (?)

Navbar component can render the login component where users can put information (except if you prefer to render the login in the middle of the page).
It can render links such as 'Medium', which could lead to a drop-down menu / another page where we'd have a list of the mediums: "Painting",  "Print", "Sculpture" which would, in turn, lead to a list of the products filtered by that property.
Can be done later on after we set up the cart, logins, etc. correctly.


[Packager] Support ES6 re-export in the dependency resolver

I found out that the packager failed at resolving dependencies using the re-export syntax:
export { default as MyLib } from 'src/mylib';

I've updated the resolver to understand the fromClause from the spec and updated the resolver tests.

Thanks for your contribution. We're in the process of moving the packager to it's own github repo and we'll be able to accept contributions like this much faster (we can just use the Github merge button). I'm hoping we can release it some time this week, and I'll ping you so we can move this PR there.

@vjeux I saw you imported the other es6 issue #1940. Any chance we could get this resolved as well?

@amasad now that we can easily import diffs, do you mind doing a real review?

I tagged this as needs-revision since this needs to be rebased.

@vjeux @ide if I rebase this and submit a new PR, can we get this merged? This is a super glaring issue in support es6 modules in the packager. With https://github.com/facebook/react-native/commit/535ee40818bf0826e24994bdc4696834b9ebdc15, we have only partial support.

@skevy yes please!

@vjeux #3465

Thanks @skevy!

@ide this can be closed, btw, given #3465. One less PR to have open when there are hundreds :)

Thanks for the heads up.


Quicker certificate expiry and rotation

Components currently generate TLS certificates that expire after a year. For improved security, we should shorten this time and (automatically) rotate the certificates.
Requires #369

Won't do this for v2. In v3 we'll work with CA-signed certificates (usually from Let's Encrypt, which are currently issued for 3 months)


Additional decom note

Shouldn't we uninstall the monitoring agent from the machine too?
I don't recall seeing that on the page.  I see the registry cleanup and the portal cleanup of the v1, but not the software removal.
Thanks.

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

ID: e46cfd4e-9663-145f-dd23-28effd108738
Version Independent ID: f5126582-7211-65c9-0817-cef899f6aee5
Content: Migrate an existing agent-based hybrid workers to extension-based-workers in Azure Automation
Content Source: articles/automation/migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md
Service: automation
Sub-service: process-automation
GitHub Login: @SnehaSudhirG
Microsoft Alias: sudhirsneha

@JFBDO2022
Thanks for your feedback! We will investigate and update as appropriate.

@JFBDO2022 Thanks for your question. If you are using Log Analytics agent(monitoring agent) to collect logs and performance data from Azure virtual machines or hybrid machines hosted outside of Azure. Then it's not suggested to remove the log analytics agent from the azure virtual machine. Kindly note that Log analytics agent is being deprecated by August 31,2024. Its highly recommended to use Azure Monitor Agent for monitoring your vm.
As there are no further documentation changes, we will close the issue for now. If there are further questions , please revert and we will be glad to assist you.


⚠ Secret Website 3 has degraded performance

In 876239b, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2184 ms

Resolved: Secret Website 3 performance has improved in 179d90b.

Resolved: Secret Website 3 performance has improved in 179d90b.


Update Transactions List for Last look

We'll be tracking transactions by Swap events, so there will not be an Etherscan link, but there will be an expiry time so it's possible to include a timer.

linked to #214


Add test cases

Add new test cases to increase the testing coverage

Need to add some comments to the test cases.


Rule: duplicated settings

Is this rule only related to duplicated settings or any section?

Is this rule only related to duplicated settings or any section?

I know realized that it may be related to settings for specific section, e.g. [Tags] under specific test case, right? :)

Is this rule only related to duplicated settings or any section?

It's related to this situation:
Metadata  identical
Metadata  identical
Resource  common.robot
Resource common.robot
Suite Teardown  same
Suite Teardown  other but still teardown

Duplicated [Tags] should be detected by ParsingErrorChecker but of course we need to list such cases and test them to confirm it

Repeated settings are parsing errors:
Force Tag  tag
Force Tag  tag2

Robot Framework syntax error: Setting 'Force Tags' is allowed only once. Only the first value is used.
Permittable duplicates are Resource, Library, Metadata and Variables.
I will only add duplicate check for those (if we're not importing the same library, with the same args twice etc)


Show a message when opening a file change redirects to GitHub

If you open a file from a PR that contains an unsupported file type, it automatically opens your browser and navigates to the GitHub website and shows the preview. This is quite jarring and we should provide a better experience by showing a message and giving the user an option to preview on the web.
Repro steps

Navigate to PR that has changes to an svg/ttf/unsupported file type (i.e. https://github.com/jesseweed/seti-ui/pull/504)
Click on file in the GitHub PR Viewlet
You are re-directed to the GitHub that shows the file

Expected

Show a message that explains that file is not supported with a link to preview on the web

Updated the title, since there are other situations where we open the file on GitHub that we should explain, for example when it's too large. The GitHub API doesn't actually return a reason for why the patch isn't include, so we can either try to infer it or have a more generic message

Yeah I 100% agree on this. It definitely breaks my flow when doing a peer review in VSCode to unexpectedly have my browser open when clicking on the next file in the directory. In my case it was purely a renamed file - I see no reason why it can't just be shown in VSCode, or at the very least - a message saying something along the lines of This has solely been renamed and is accordingly not available here. Do you wish to view it on GitHub?

Unsupported types are one thing, but for a file that is too large (or doesn't have the patch included), can't you just get the whole contents of the file at that version to provide the diff?

@Maskime Thanks for your feedback! This sounds similar to https://github.com/microsoft/vscode-pull-request-github/issues/1160.
I've previously reached out to GitHub to try to clarify what the exact circumstances are for patches not being returned and am still waiting for a response. This is definitely a pain point! With some refactoring we may be able to handle this by just making additional network calls when trying to open the diff to resolve the whole file contents of both sides instead of working with a patch.


Dynamic GraphQL Schema

There may be some benefits to being able to dynamically generate the GraphQL schema for Juniper. This is not yet currently possible. I will keep an eye on https://github.com/graphql-rust/juniper/issues/7 and other Juniper issues like it.

Is this ultimately a desired feature? Alternatively we could run Hasura over the main RCOS API.

Is this ultimately a desired feature? Alternatively we could run Hasura over the main RCOS API.

We could do that honestly. It's desired if we intend to continue exposing an API as part of telescope but we could separate that concern to another service (temporarily or permanently) and there are definitely valid reasons why we might do that.

We could do that honestly. It's desired if we intend to continue exposing an API as part of telescope but we could separate that concern to another service (temporarily or permanently) and there are definitely valid reasons why we might do that.

I would really push Hasura, just because then it's all pulled from Postgres itself.
However the REST vs GraphQL debate is something @Apexal and I went into a lot, and we eventually settled on REST with PostgREST. We ultimately came to the conclusion that while GraphQL adds a lot of features, PostgREST has similar versions of the most important features and uses a much more well understood and ubiquitous REST interface. This API has to outlast us, so we have to be extremely conservative about our technical decisions.

I would really push Hasura, just because then it's all pulled from Postgres itself.
However the REST vs GraphQL debate is something @Apexal and I went into a lot, and we eventually settled on REST with PostgREST. We ultimately came to the conclusion that while GraphQL adds a lot of features, PostgREST has similar versions of the most important features and uses a much more well understood and ubiquitous REST interface. This API has to outlast us, so we have to be extremely conservative about our technical decisions.

That makes sense.
It seems like whatever we do, having to manually build out a GraphQL API in rust is not a great option currently. It would take a lot of work and might not be as featureful as as Hasura or as conservative as a REST API.
With that in mind I'm gonna make a branch removing juniper and GraphQL from this project for now. If we decide later that we do want Telescope to expose an API then we can add them back then.

That makes sense.
It seems like whatever we do, having to manually build out a GraphQL API in rust is not a great option currently. It would take a lot of work and might not be as featureful as as Hasura or as conservative as a REST API.
With that in mind I'm gonna make a branch removing juniper and GraphQL from this project for now. If we decide later that we do want Telescope to expose an API then we can add them back then.


Metal: Texture arrays with 1 layer don't work

It looks like Metal backend infers the type of the image at the call site of create_image, and considers images with 1 array layer 2D:
https://github.com/gfx-rs/gfx/blob/master/src/backend/metal/src/device.rs#L2083-L2117
Unfortunately, this doesn't work with texture arrays with 1 layer. For these, the application needs to create an image with arrayLayers=1, and create an image view with viewType = VK_IMAGE_VIEW_TYPE_2D_ARRAY. In Metal, what should happen is that a MTLTextureType2DArray is created.
Failure to do this produces validation errors like this:

validateFunctionArguments:3377: failed assertion `Fragment Function(main0): incorrect type of texture (MTLTextureType2D) bound at texture binding at index 1 (expect MTLTextureType2DArray) for NormalMap[0].'

These happen because the application creates an array shader view (VK_IMAGE_VIEW_TYPE_2D_ARRAY), the pipeline layout uses an array descriptor, the shader uses an array image, but Metal backend substitutes a 2D image instead.
There might not be a nice solution to this. I think MoltenVK delays the creation of the image until the creation of the view and has to deal with several different possible ordering situations; it may also assume that an image view is created before the data is uploaded to the image?

Thanks for filing the issue and expression your investigation notes!
I think we'll force the backing texture to have 2D array type if VK_IMAGE_CREATE_2D_ARRAY_COMPATIBLE_BIT was provided. One can always create regular 2D views from an array, but not the other way around.

The spec says that this flag doesn't work for 2D images unfortunately:

If flags contains VK_IMAGE_CREATE_2D_ARRAY_COMPATIBLE_BIT, imageType must be VK_IMAGE_TYPE_3D

Oops, I missed that bit. Can't we always create a 2D array texture then, just in case?

Actually... am I off base here? I realized that the validation error was related to another issue that was misleading me. It looks like gfx-rs creates a texture view for a Vulkan image view, and that seems like it correctly creates 2D array view for a 2D texture in this case? Let me double check this but I feel like maybe the issue was a red herring. https://developer.apple.com/documentation/metal/mtltexture/1515409-newtextureviewwithpixelformat?language=objc seems to suggest you can reinterpret between 2D and 2D arrays in both directions.

Uh, I instantly assumed Metal doesn't allow you to have an array view out of a non-array texture. cc @msiglreith Thanks for clarifying this, looking forward for more info.

I've double checked this and I believe gfx-rs is working correctly here. The validation issue was a red herring that was related to some Vulkan-on-macOS-packaging on our end (shaders were stale I think). We've seen something sort of similar on MoltenVK so I jumped to conclusions, sorry about that. I'll close this.


Test different input types for ML model

Changed the model input from image tensor to base64 encoded string, relieving the preprocessing bottleneck that we were seeing previously.  10 new detections using this scheme should now be present in the DB.


Update Links due to navigation issue for Projects Page

Currently the buttons on the community page take you to the desired page but to the middle or bottom of the desired page and never to the top of the desired page as shown in the screenshots. This arises due to error in navigation.
Kindly request you to assign me this issue so that i can rectify the same.

@EbonyLouis I'd love to work on this

@EbonyLouis I'd love to work on this

Hey @unkletayo I am currently i=on this issue and would close the same during the weekend...so kindly take up and other open issue!

this has been fixed


when creating a ray reflection, a laser pointer is created in the top-left corner

steps to reproduce:

place a mirror
place a laser using "c"
rotate the laser to look at the mirror
unclick the laser
observe a new laser pointer appear

resolved a while ago


MIDI program changes not working

Tested on macOS Monterey 12.6.1 with a 2020 M1 Silicon MacBook Pro using Bitwig 4.4.2.
Tested with multiple u-he plugins.
MIDI bank change messages are arriving at the wrapped plugin.
But program changes don't seem to enter the plugin at all.
Not even the plugin's MIDI activity led is reating.
Maybe this is related to the other MIDI issue (CC data being received on channel 16)?

This is not related to #32.

Doesn’t vst3 turn program changes into internal patch list traversals? I thought program change and vst3 rarely worked

merged to 0.8.0


New pre-release version of package

Hi @vojtasvoboda
could you check this beta version and confirm that everything is ok at your end?
Thank you
https://github.com/pionl/smart-emailing-v3/issues/18

Hi @pionl, updated to v0.4.1 and tested on production. I'm sorry for not getting back to you sooner.

No worries @vojtasvoboda , thank you your time and have a good day!


API Proposal: Remove queryAllDOM

Summary
While queryAllDOM is a valuable tool for selecting deeply nested elements, it is antithetical to the encapsulation traditionally associated with web-components.
Often cases where we use queryAllDOM could be supported by using queryAllSelector(), and making sure that the web-components that are queried expose a meaningful amount of data that they intend to expose.
For example, in the todo-list.js example (notably the only instance where we use queryAllDOM), instead of the following:
function updateTotalAndCompletedLabel(todoList) {
  // query all list items to determine new completed and total
  const todoItems = queryAllDOM('todo-item', todoList);
  todoList.setAttribute('total', todoItems.length);
  const completedItems = queryAllDOM('input:checked', todoList);
  todoList.setAttribute('completed', completedItems.length);
}

We could:
function updateTotalAndCompletedLabel(todoList) {
  // get all todo-items from the shadow-root
  const todoItems = todoList.shadowRoot.queryAllSelector('todo-item');
  todoList.setAttribute('total', todoItems.length);

  // get all todo-items that are checked (an attribute that is already exposed)
  const completedItems = todoList.shadowRoot.queryAllSelector('todo-item[checked]');
  todoList.setAttribute('completed', completedItems.length);
}

Completed as part of the v3 release


needed documentation

residual degrees of freedom
page on solvers/regularizers (what we have available, options for args that a user can play around with)

unified glossary page?


Cow: Watch treeserviceseugeneor.com

Cow requests the watch of the watch_keyword treeserviceseugeneor\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

treeserviceseugeneor\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Can't override pinned package  in ~/.doom.d/package.el

What did you expect to happen?

I added the following to ~/.doom.d/package.el in order to use the latest revision of lsp-mode, however it is not applied. After doom sync it says that it checked out the new version, however it still builds/uses the specified version in modules/tools/lsp/package.el

(package! lsp-mode :pin "f6317d74c54b0ee4ba4d1743f798ba595e07be78")
;; (package! lsp-mode :recipe (:host github :repo "emacs-lsp/lsp-mode"))

    - Checked out f6317d74c54b0ee4ba4d1743f798ba595e07be78
    → Building lsp-mode...
    → Building lsp-mode...done

System information:

emacs   version    28.0.50
        features   JPEG TIFF GIF PNG RSVG GLIB NOTIFY KQUEUE ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS NS MODULES NATIVE_COMP THREADS JSON PDUMPER LCMS2
        build      Aug 12, 2020
        buildopts  (--disable-silent-rules --without-dbus --without-imagemagick --without-x --prefix=/Users/st21371/gccemacs --enable-locallisppath=/usr/local/share/emacs/site-lisp --with-nativecomp --with-ns --disable-ns-self-contained --with-gnutls --with-modules --with-rsvg --with-harfbuzz --with-pdumper --with-xml2 --with-json --with-cocoa 'CFLAGS=-g3<EMAIL_ADDRESS>-I/usr/local/opt/gcc/include -I/usr/local/opt/libxml2/include -I/usr/local/opt/giflib/include -I/usr/local/opt/jpeg/include -I/usr/local/opt/libtiff/include -I/usr/local/opt/gnutls/include -I/usr/local/opt/jansson/include -I/usr/local/opt/nettle/include -I/usr/local/opt/libtasn1/include -I/usr/local/opt/p11-kit/include ' 'CPPFLAGS=-g3<EMAIL_ADDRESS>-I/usr/local/opt/gcc/include -I/usr/local/opt/libxml2/include -I/usr/local/opt/giflib/include -I/usr/local/opt/jpeg/include -I/usr/local/opt/libtiff/include -I/usr/local/opt/gnutls/include -I/usr/local/opt/jansson/include -I/usr/local/opt/nettle/include -I/usr/local/opt/libtasn1/include -I/usr/local/opt/p11-kit/include ' 'LDFLAGS=-L/usr/local/lib/gcc/9<EMAIL_ADDRESS>-L/usr/local/opt/gcc/lib -L/usr/local/opt/libxml2/lib -L/usr/local/opt/giflib/lib -L/usr/local/opt/jpeg/lib -L/usr/local/opt/libtiff/lib -L/usr/local/opt/gnutls/lib -L/usr/local/opt/jansson/lib -L/usr/local/opt/nettle/lib -L/usr/local/opt/libtasn1/lib -L/usr/local/opt/p11-kit/lib ')
        windowsys  ns
        daemonp    server-running
doom    version    2.0.9
        build      HEAD -> develop, origin/develop, origin/HEAD 03162466c 2020-08-11 19:22:32 -0400
        dir        ~/myfiles/dotfiles/config/home/.doom.d/
system  type       darwin
        config     x86_64-apple-darwin19.5.0
        shell      /bin/zsh
        uname      Darwin 19.5.0 Darwin Kernel Version 19.5.0: Tue May 26 20:41:44 PDT 2020; root:xnu-6153.121.2~2/RELEASE_X86_64 x86_64
        path       (~/.gvm/pkgsets/go1.13.7/global/bin ~/.gvm/gos/go1.13.7/bin ~/.gvm/pkgsets/go1.13.7/global/overlay/bin ~/.gvm/bin ~/gccemacs/bin ~/bin /Applications/MiniZincIDE.app/Contents/Resources<EMAIL_ADDRESS>~/.pyenv/shims ~/.pyenv/bin ~/.cargo/bin /usr/local/bin /usr/bin /bin /usr/sbin /sbin /Library/TeX/texbin /usr/local/share/dotnet /usr/local/munki /opt/X11/bin ~/.dotnet/tools /Library/Apple/usr/bin /Applications/Wireshark.app/Contents/MacOS /usr/local/opt/llvm/bin /usr/local/opt/curl/bin /usr/local/opt/binutils/bin ~/.gem/bin ~/scripts /usr/local/opt/gnu-time/libexec/gnubin /usr/local/opt/coreutils/libexec/gnubin ~/.emacs.d/bin ~/.cabal/bin ~/.ghcup/bin ~/.local/bin /usr/local/sbin ~/Library/Android/sdk/tools ~/Library/Android/sdk/platform-tools /usr/local/opt/go/libexec/bin ~/go/bin ~/myfiles/dotfiles/bin ~/n/bin ~/gccemacs/libexec/emacs/28.0.50/x86_64-apple-darwin19.5.0/)
config  envfile    envvar-file
        elc-files  0
        modules    (:completion (company +childframe) (ivy +fuzzy +prescient +icons) :ui deft doom doom-dashboard hl-todo hydra indent-guides (modeline +light) nav-flash ophints (popup +all +defaults) treemacs unicode (window-select +numbers) workspaces :editor (evil +everywhere) file-templates fold multiple-cursors rotate-text snippets word-wrap :emacs dired electric ibuffer undo :term vterm :checkers syntax spell :tools (debugger +lsp) direnv docker editorconfig (eval +overlay) gist (lookup +dictionary +offline +xwidget +docsets) (lsp +peek) macos magit make pdf :lang (cc +lsp +rtags) common-lisp data emacs-lisp (go +lsp) (haskell +ghcide) (javascript +lsp) (markdown +pandoc) nix (org +dragndrop +gnuplot +journal +pandoc +pomodoro +present +roam +noter) (python +lsp) rest (rust +lsp) sh (yaml +lsp) (json +lsp) web :app (rss +org) :config (default +bindings +smartparens))
        packages   ((exec-path-from-shell :disable t) (flycheck-popup-tip :disable t) (flycheck-posframe :disable t) (modus-operandi-theme) (modus-vivendi-theme) (s) (org-pdftools :recipe (:host github :repo fuxialexander/org-pdftools :files (org-pdftools.el))) (org-noter-pdftools :recipe (:host github :repo fuxialexander/org-pdftools :files (org-noter-pdftools.el))) (org-noter-pdftools) (org-drill :recipe (:host github :repo zeronone/org-drill)) (oj) (pipenv :disable t) (company-tabnine) (company-try-hard) (package-lint) (lsp-pyright :recipe (:host github :repo emacs-lsp/lsp-pyright)) (lsp-mode :pin f6317d74c54b0ee4ba4d1743f798ba595e07be78))
        unpin      (n/a)
        elpa       (n/a)

~/.doom.d/package.el

That should be ~/.doom.d/packages.el.

Oh sorry, it was a typo in my description. I used the correct file ~/.doom.d/packages.el.

Doing doom sync -u worked. I guess I need to pass in the -u option.


Android-Java 3.5: Fragment LifeCycle

Description
Android Fragments and Fragment Lifecycle
Fragment manager
Fragment lifecycle states and callbacks
Example
Domain
Android Dev (Java)
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

/assign

/assign


Move init_logging to tauri-plugin-log

https://github.com/tauri-apps/tauri/blob/50f6dd87b1ac2c99f8794b055f1acba4ef7d34d3/core/tauri/src/lib.rs#L281-L331
This does not belong here

I'll take care of this. I need some time to cleanup the tags though.

I'll take care of this. I need some time to cleanup the tags though.

Great! If you want me to jump into anything and help let me know

See https://github.com/tauri-apps/plugins-workspace/pull/96 and #6081


Unable to Connect to TIM781

I am attempting to connect to two different TIM781 lidars. If the lidars are configured for ASCII, I get errors about unexpected ASCII datagrams. However, if I configure the lidars to use binary and change the launch file config to binary, I get the following timeout on both sensors (excerpt from the end of the log because it produces a bunch of other data as well):
[INFO] [1643225657.236905141] [sick_scan]: Safety field 41, type 2 : (0,0), (-7.85398e-05,-1), (1.2491,-0.999872), (1.24957,0.999283), (0.000392588,1)
[INFO] [1643225657.236938302] [sick_scan]: Safety field 42, type 2 : (0,0), (-0.00011781,-1.5), (2.25021,-1.49939), (2.25092,1.49833), (0.000588882,1.5)
[INFO] [1643225657.236970942] [sick_scan]: Safety field 43, type 2 : (0,0), (-9.81748e-05,-1.25), (1.8749,-1.24931), (1.87549,1.24842), (0.000490735,1.25)
[INFO] [1643225657.237004782] [sick_scan]: Safety field 44, type 2 : (0,0), (-7.85398e-05,-1), (1.49959,-0.999223), (1.50006,0.998516), (0.000392588,1)
[INFO] [1643225657.237038062] [sick_scan]: Safety field 45, type 2 : (0,0), (-0.00011781,-1.5), (2.62647,-1.49673), (2.62717,1.49549), (0.000588882,1.5)
[INFO] [1643225657.237071502] [sick_scan]: Safety field 46, type 2 : (0,0), (-9.81748e-05,-1.25), (2.18858,-1.24719), (2.18917,1.24616), (0.000490735,1.25)
[INFO] [1643225657.237104542] [sick_scan]: Safety field 47, type 2 : (0,0), (-7.85398e-05,-1), (1.75069,-0.997653), (1.75116,0.996828), (0.000392588,1)
[INFO] [1643225657.237161662] [sick_scan]: Sending  : <STX><STX><STX><STX><Len=0032>sWN LMDscandatacfg 0x01 0x00 0x01 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x01 0x00 0x01 CRC:<0x43>
[INFO] [1643225657.238867029] [sick_scan]: Receiving: <STX>sWA LMDscandatacfg <ETX>
[INFO] [1643225657.238920949] [sick_scan]: Sending  : <STX><STX><STX><STX><Len=0018>sRN LMDscandatacfg CRC:<0x67>
[INFO] [1643225657.240016553] [sick_scan]: Receiving: <STX>sRA LMDscandatacfg \x01\x00\x01\x01\x00\x00\x00\x00\x00\x00...
[INFO] [1643225657.240238474] [sick_scan]: Sending  : <STX><STX><STX><STX><Len=0018>sWN FREchoFilter 0x00 CRC:<0x7f>
[WARN] [1643225777.242375258] [sick_scan]: Timeout during waiting for new datagram
[WARN] [1643225777.242564218] [sick_scan]: sendSOPASCommand: no full reply available for read after 120000 ms
[INFO] [1643225777.242652619] [sick_scan]: Receiving: <STX><ETX>
[INFO] [1643225777.242696339] [sick_scan]: SOPAS Communication -Error unexpected Sopas answer for request <STX><STX><STX><STX><Len=0018>sWN FREchoFilter 0x00 CRC:<0x7f>

[INFO] [1643225777.242757379] [sick_scan]: Failed to init scanner Error Code: 1
Waiting for timeout...
If the communication mode set in the scanner memory is different from that used by the driver, the scanner's communication mode is changed.
This requires a restart of the TCP-IP connection, which can extend the start time by up to 30 seconds. There are two ways to prevent this:
1. [Recommended] Set the communication mode with the SOPAS ET software to binary and save this setting in the scanner's EEPROM.
2. Use the parameter "use_binary_protocol" to overwrite the default settings of the driver.
[ERROR] [1643225777.242853259] [sick_scan]: ## ERROR in mainGenericLaser: init failed, retrying...
[INFO] [1643225777.242890539] [sick_scan]: Start initialising scanner [Ip: <IP_ADDRESS>] [Port:2112]
[WARN] [1643225777.242924820] [sick_scan]: Disconnecting TCP-Connection.
[ERROR] [1643225777.243033860] [sick_scan]: Tcp::readInputData: Read 0 bytes, connection is lost!
[INFO] [1643225777.243194301] [sick_scan]: SickThread TcpRecvThread finished (flags: threadShouldRun=0, endThread=0).
sick_scan driver closed.
[ERROR] [1643225777.253615459] [sick_scan]: ## ERROR in mainGenericLaser: exception parameter 'diagnostic_updater.period' has already been declared

Thanks for reporting! Did you use the latest sick_scan_xd release? This problem is solved with the most recent version of this driver (#15 also for TiM7xx). Please update sick_scan_xd to the latest version and retry. I'll close the ticket for now; but don't hesitate to reopen the issue in case the problem persists.

Thank you! The latest version did indeed fix the problem.


docs(basic-auth) add 2 new endpoints to list basic-auths

/basic-auths/ to paginate through all basic-auth credentials
/basic-auths/:credential_id_or_username/consumer to retrieve the
Consumer associated with a credential

See: https://github.com/Kong/kong/pull/2998

Manually merged with some minor edits, thanks! On to the others!


Add method to print metadata from dictionary returned by getdata

Reported by andrew wittenberg on 22 Apr 2011 18:57 UTC
Add method to print metadata from dictionary returned by getdata.  Could become the str method of an object derived from this dictionary.  Method from Andrew pretty much meets the requirements:
for (k,v) in var.items():
    if k == "data":
        pass
    elif k == "axis_coords":
        print k + ":"
        for (i,c) in enumerate(v):
            print "   '" + var["axis_names"][i] + "': " + str(c)
    else:
        print k + ": " + str(v)

Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1844

Comment by karl.smith on 23 Apr 2011 01:01 UTC
Added the metastr method.  This returns a string that can be printed (akin to 'str') rather than printing the information directly.  So 'print pyferret.metastr(var)'
Made the output a little easier to read (better indentation) and understand.


BiasTorrent anomaly

Why does the gap between Followers and Leaders remain so big even after topology change?
Possible reasons:

tit-for-tat
picker strategy

It was Tit-for-Tat.


Contradicting points regarding X-Flow-ID

Section 183 gives an example of an x-flow-id: GKY7oDhpSiKY_gAAAABZ_A
Section 233 dictates the charset of x-flow-id to be base64: [a-zA-Z0-9/+]. The example given in section 183 is of an invalid x-flow-id.
Since these points are contradicting, it would be good to correct the example or expand the allowed charset.
As a sub-question: Does 233 mean UUIDs cannot be used as an x-flow-id?

Good catch!
The regex and reference to base64 is incorrect and confusing at best.
I believe we should be more forgiving and allow for the following formats:

base64
base64url
UUID
underscores (as in the example in rule 183)

Regular expression could be changed to ^[\w\/\-+=]+$


[Feature Request]: Please split mvvm off into a separate package

I have been hunting for an up to data MVC/MVP / Mvvm packages and was almost going to use your core, when I found it has requirement for NLog, is not .net 48 and has loads of other stuff that my app does not need.
So please separate the Core into a code base that just performs MVxxx style code, and produce a nuget for that.
Please also include some of the Bindable style stuff from Winforms down into that package as well (i.e. remove it from WindowsBase!)

In 8.0.0 (not 7.0.0), We are planning the following:

We will create a new package and transfer the code that depends on NLog to that package.
We will split the current Cube.Forms.dll into new Cube.Forms.dll and Cube.Forms.Controls.dll. The latter includes view components and separates it from the MVVM code base.

What about splitting core as well, so that there is just an mvvm implementation ?

OK, not right now, but I will try to reconstruct the contents of Cube.Core package.

Version 8.0.0 for Cube.Core, Cube.Forms, Cube.Xui, and other additional packages have been released.

Cube.Core
Cube.Forms
Cube.Xui

Removed the NLog dependency from Cube.Core and added a new package (Cube.Logging.NLog) to enable the functionality. We also splitted the custom view components of WinForms into the Cube.Forms.Controls package.


[FEATURE] Add hover effect to home button

Description
Currently, the home button doesn't have any hover effect, so add it to make it more user interactive.
I'm contributing under GSSoC'23 program.
Do assign this issue to me.
Screenshots
No response
Additional information
No response

Hi @accodes21 , I am assigning this task to you. Kindly complete within 2 day. Good luck!

If this work not done yet.
Please assign this work to me.
I want to work on this issue.

I want to work on this issue by adding some animated hover effect on buttons, can you assign this to me?


Fix doc format

Signed-off-by: jwcesign<EMAIL_ADDRESS>What type of PR is this?
Fix doc format

/kind documentation
What this PR does / why we need it:

Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:

@Poor12

Can you help update the following docs as well?

current i18n/zh  https://github.com/karmada-io/website/tree/main/i18n/zh/docusaurus-plugin-content-docs/current
version-v1.3.0 https://github.com/karmada-io/website/tree/main/versioned_docs/version-v1.3.0
version-v1.3.0(i18n/zh) https://github.com/karmada-io/website/tree/main/i18n/zh/docusaurus-plugin-content-docs/version-v1.3.0


Tokenization for common models

In order to run the distill.py, we need an nltk/allen's tokenizer for other basic models.

Closing duplicate issue (See https://github.com/castorini/hedwig/issues/4)


💡[Feature]: Analyze Molecular Structures using GNN

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
The main goal is to implement a Graph Neural Network (GNN) for predicting molecular properties by utilizing r-radius subgraphs for enhanced molecular representation.
Use Case
It can be used to predict drug efficacy and photovoltaic efficiency, aiding in drug discovery and material science research by leveraging molecular fingerprint representations.
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Kindly assign this issue to me.


Apply dirmode to top-level cache directory, too

Due to the cache directory already created in the constructor, if it doesn't exist already it will be created with wrong permissions. The fluent setter for dirMode is only applied after the directory was created.
This re-applies the directory permissions once on withDirectoryMode() if they don't match the default.
Fixes #46
Also added a specific test case for checking the cacheDir permissions.
It would seem to me that doing this in the withDirectoryMode() setter is probably the best solution, since it won't require checking the mode on every set/get/gc, and only sets it once on init.

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Fixed issues
#46

May be use another way: add second optional parameter to constructor $directoryMode?

May be use another way: add second optional parameter to constructor $directoryMode?

That's definitely an option, though imho it would lead to confusing usage, as the fluent setter would not affect that top level dir,
and you have two ways to set the directoryMode. Maybe remove the setter, too?

If value will be changed by withDirectoryMode, this will only affect newly created directories.

True, though that would always be the case, I doubt it makes sense anywhere (in code) to go over all existing subdirs and change the mode. The whole initialization flow with the withDirectoryMode() is only usable if it's called very early in application startup. Otherwise, on high traffic applications, accessing the cache might hit it in-between the constructor and the setter, and mix up modes completely.

Maybe remove the setter, too?

Mark as deprecated and remove in next major release.

Alright, removed the previous change to withDirectoryMode() and fixed the issue via constructor parameter instead.
I kept the new constant (even though it's technically no longer necessary, since the single use in constructor default param would be enough). The directoryMode property is now set before calling createDirectoryIfNotExists(), which fixes the issue, too.
Renamed the old test since it now tests a deprecated method, and added a new test case, which tests both subdirectory and top-level directory permissions.

@particleflux Thanks! Good job 👍


Rename cluster unit test function

Makes future tests, related to shard mapping, clearer.

Cosmetic test change only, merging on green.


[Bug] In MPR mode, SR localization jumps to wrong instances sometimes

Describe the Bug
In MPR mode, SR localization jumps to wrong instances (since it can become an inverted image stack) sometimes. Eg., default 1x1 viewport instance 1 is legs. Once in MPR mode, instance 1 is head in WB CT.
Phantom study that exhibits the bug without anatomy (pwd: "secrecy"):
https://fileshare.uhn.ca/download/39c5d602-6f95-4882-8cff-e3c2fe7e38bf
Steps to Reproduce

CT with default 1x1 viewport instance 1 is legs. Once in MPR mode, instance 1 is head in WB CT.

Default viewport see legs on i=1.

Make 2 measurements corresponding to i=1 (legs) and i=end (head).

Load MPR mode.

Axial MPR mode i=1 shows head.

SR localization becomes inverted/wrong

The current behavior

Localize to measurement for legs, but viewport jumps to head. Measurement at this location stays yellow (ie, not current).

Localize to measurement for head, but viewport jumps to legs. Measurement at this location stays yellow (ie, not current).

Exiting MPR mode to Common Hanging protocol 1x1 does not fix this, only dragging series into 1x1 viewport does.

The expected behavior

Localize to measurement for legs, and viewport jumps to legs. Measurement at this location is green (ie, current).
Localize to measurement for head, and viewport jumps to head. Measurement at this location is green (ie, current).

OS
Windows 10
Node version
000000
Browser
Chrome 126.0.0

I think i know what is happening

I think this is fixed now, check latest
Can you check the latest OHIF viewer, which now includes Cornerstone 3D 2.0?
Here are the migration guides:
Try OHIF locally: https://viewer-dev.ohif.org/localbasicTry Cornerstone3D 2.0 locally: https://www.cornerstonejs.org/live-examples/local.html
https://docs.ohif.org/migration-guide/3p8-to-3p9/


Added pkgConfig information for C ZMQ library import

I'm not sure if this is something that you want upstream, but it's worth a shot.
This just adds a pkgconfig label for libzmq that SwiftPM can use to find the include and link paths.

Of course we want this! Thanks so much for the pr 😃

Tagged 1.0.3


python311Packages.tesla-fleet-api: init at 0.2.3

Python library for Tesla Fleet API and Teslemetry
https://github.com/Teslemetry/python-tesla-fleet-api
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
24.05 Release Notes (or backporting 23.05 and 23.11 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.

Add a :+1: reaction to pull requests you find important.

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

2 packages built:

python311Packages.tesla-fleet-api
python311Packages.tesla-fleet-api.dist


Missing Biome warning should be optional

I work with several projects and some of them do not (yet!) use Biome. Currently the extension shows this warning every time a project without Biome is loaded:
Could not find Biome in your dependencies. Either add the @biomejs/biome package to your dependencies, or download the Biome binary.

I propose that a biome.warnIfDependencyMissing setting be added that allows disabling this warning, and a "Don't remind me again" option be added to the warning that sets this setting to false.
I'd be happy to work on this if it's something others want 👌

Hey @GRA0007,
Thanks for opening this issue.
We're working on an improved detection mechanism and new options that should solve this issue. I will keep you informed.

I came here to report a similar issue with this warning, but triggered in a different context. Since it's similar enough, I'll put it here rather than creating a new issue.
I have Biome specified in my package.json's devDependencies (not dependencies, since it's not needed for the actual app`). Every time I reload the window, I see this warning pop up even though I have Biome in my dependencies.

This will no longer be an issue in v3. Closing since we've started publishing the nightly.

Is there a plan for when v3 with this fix might be released?

We don't really have ETAs for when stuff will get released. We're still kinda feeling it out and gathering bug reports for v3. If you want this right now, you can switch over to the prerelease in vscode by clicking the "switch to prerelease" button.


Upgrade bare example to RN 0.76.2

Description
This PR upgrades RN to 0.76 and tests example apps against it
Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?

Checklist: (Feel free to delete this section upon completion)

[x] I have included a changeset if this change will require a version change to one of the packages.
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have run all builds, tests, and linting and all checks pass
[x] I have added tests that prove my fix is effective or that my feature works
[x] My changes generate no new warnings
[x] Any dependent changes have been merged and published in downstream modules

Upgraded dependent libraries to support new RN version


dplay.es and others like dplay.it dplay.no etc

[x] I'm reporting a new site support request
[x] I've verified that I'm running youtube-dl version 2020.09.06
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that none of provided URLs violate any copyrights
[x] I've searched the bugtracker for similar site support requests including closed ones

Example URLs
https://www.dplay.es/series/5-por-sorpresa

Single video: There is no single video now, its javascript.
Playlist: https://www.dplay.es/series/5-por-sorpresa

Description
dplay.es (and other country domains) network updated it's website, now it needs a login that i think only with a cookie.txt can be bypassed. In the pas whas es.dplay.com or it.dplay.com etc, now they have its own domain but same tecnology for all of them.
Now season and chapter are loaded by a javascript, not anymore an individual page ofr each chapter.
Could be nice using cookies.txt to download the compelte show.

it has drm protection
youtube-dl cannot download this
ask here https://forum.videohelp.com/forums/48-Video-Streaming-Downloading

it has drm protection
youtube-dl cannot download this
ask here https://forum.videohelp.com/forums/48-Video-Streaming-Downloading

Manually is easy with just firefox there is no drm just code obfuscation. The goal is to automate.

there is  in the menifest
but i am more curious how did you download that firefox?

there contentprotection is in the menifest
did you downloaded video with drm?
but i am more curious how did you download that with firefox?

there contentprotection is in the menifest
did you downloaded video with drm?
but i am more curious how did you download that with firefox?

as I said there is not drm, just obfuscation. Just search for the m3u in the browser traffic.

I am not sure if it would be enough to add support for new urls in regex or if there is also some logic change.


Nextjs useLayoutEffect warnings

After running yar dev in terminal there are lots of useLayoutEffect warnings:
Warning: useLayoutEffect does nothing on the server, because its effect cannot be encoded into the server renderer's output format. This will lead to a mismatch between the initial, non-hydrated UI and the intended UI. To avoid this, useLayoutEffect should only be used in components that render exclusively on the client. See https://reactjs.org/link/uselayouteffect-ssr for common fixes.

Seems fixed on staging


"undefined" language name

Closed in https://github.com/minhducsun2002/miyu/commit/00ef424d08b7b078ce30235c5232a90379420287.


Feat: Add new game : Code-quizzy

https://github.com/iamnijat/code-quizzy
Makes coding a fun !

@ashitaprasad I want to add this game , please assign it to me


Fixed asset locations for GH Pages

feature requests are merged to develop branch not to master. Please do correct the PR

feature requests are merged to develop branch not to master. Please do correct the PR

Changed branch name to develop, should be merged into master ASAP. Sorry for the wrong PR target


Changes to support Vantage Vue

I was super happy to find this project to start working with the data from my Vantage Vue.  I tried the default mapping and was getting a "Not a broadcast packet" error for both my RainMapping and my WindMapping in the DEBUG logs.  If I remove
        if packet.data_source != PacketSource.WEATHER_PUSH:
            self._log_mapping_notResponsible("Not a broadcast packet")
            return

from lines 199-201  and 238-241 in the mappers.py file, I am then able to successfully parse my rain and wind data.  These must be there for supporting some devices.  Is there some way we could integrate a change like this to support Vantage Vue for others to use?
Thank you,
Craig

The log message you're seeing is absolutely normal and not an error. These lines are there to ignore the wind and rain data from the "complete" packets, because these values get sent every 2.5 seconds anyway.
If you put those removed lines back in, are you getting rain and wind values?

Sorry, I was not clear in my first note.  I do not get any rain or wind values from my WeatherLink unless I comment out those lines.

Ah, ok. That sounds like the driver isn't receiving the 2.5 seconds "live" updates.
How is your local network set up? Are the WeatherLink and the WeeWX device on the same LAN? The network has to allow broadcast packets to pass between the two devices.

FWIW I've been using a Vantage Vue successfully with 4.5.1. In my case it took me a while to figure out the UDP broadcast packets, but things finally worked once I had ensured that WeeWX was reachable on the same subnet as the WeatherLink Live. I wrote up some troubleshooting info via this PR: https://github.com/michael-slx/weewx-weatherlink-live/pull/21


Update grpc-netty to 1.52.1

Updates io.grpc:grpc-netty from 1.52.0 to 1.52.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.grpc", artifactId = "grpc-netty" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "io.grpc", artifactId = "grpc-netty" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Codecov Report

Merging #2344 (2677c5b) into main (fb995ad) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2344   +/-   ##
=======================================
  Coverage   78.14%   78.14%
=======================================
  Files         439      439
  Lines       14997    14997
  Branches     2083     2083
=======================================
  Hits        11719    11719
  Misses       3278     3278

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


ISPN-6997PessimisticTxPartitionAndMergeDuringRuntimeTest

.testOriginatorIsolatedPartition random failures
https://issues.jboss.org/browse/ISPN-6997
On one node, transactionTable.cleanupLeaverTransactions was being
called only before the split and after the merge, never with the list
of members during the split.

I've looked some more into this issue and it's more complex than I thought: a remote tx command can create a new remote transaction even when the tx originator is in another partition. If the partitions merge immediately afterwards, neither the originator nor the remote node's TransactionTable will clean up the transaction.

@danberindei Shall we close this PR until you've found a better solution?

One last call @danberindei :)

I'm giving it one more try today @slaskawi

And that day was gone... a while back. Closing for now. Reopen when this is ready.


Added link to "Systemwide example with X..." example config

Added link to "Systemwide example with X..." example config
This is because this way, it's easier to find the information you are looking for. Without this link, it can be confusing if you mean an example within this repository, or one of the examples in the main repository (https://github.com/xremap/xremap/).
This way, users can immediately find the configuration you're referring to by following the link.

Oh that’s odd..? I didn’t have that when I was looking on my GitHub.
However I like your solution much better to be honest! I have time to update my PR tomorrow!

Hm. That is odd indeed, after checking your fork I can see what I'd expect happenning:

Looks good after merging. Thanks for the PR!

Ah cool, cheers!


support Ethersocial Network

Description
add Ethersocial Network (ESN) support

Homepage: https://ethersocial.org/
Block Explorer : https://ethersocial.net
API node: https://api.esn.gonspool.com
BIP44 / Chainid 31102 ( satoshilabs/slips#277 )
Ticker: ESN
CMC: https://coinmarketcap.com/currencies/ethersocial/

Testing instructions
./bootstrap.sh or make -C build tests
Types of changes
Ethersocial Network support added
Checklist

[x] Add tests to cover changes as needed.
[ ] Update documentation as needed.

squashed and rebased.

only coin type and chain id are different?

only coin type and chain id are different from ethereum?

yes,
like as Callistio or GoChain that already supported by TrustWallet.


Rate Limit Per Route Behaviour strange / misunderstood?

Title: Rate Limit Per Route Behaviour strange / misunderstood?
Description:
I've been trying to get Rate Limit Per Route filters working in envoy 1.30.1.  I have it working, but the method by which it is working seems a little odd and a little by accident. Maybe somebody can clarify if this is a bug or by design.
I have a rate limit service deployed and I have a Rate Limit filter set to point to that rate limit service via a cluster.  This is fine!  I then tested this using rate_limits on the route explicitly:
Rate Limit Filter
http_filters:
  - name: "envoy.filters.http.ratelimit"
    typed_config:
      "@type": type.googleapis.com/envoy.extensions.filters.http.ratelimit.v3.RateLimit
      domain: somedomain
      timeout: 1s
      failure_mode_deny: true
      rate_limit_service:
        grpc_service:
          envoy_grpc:
            cluster_name: some-rate-limit-service
            authority: some-rate-limit-service.com
        transport_api_version: V3

Route Configuration
route:
  cluster: some-cluster
  host_rewrite_literal: "somewhere.com"
  rate_limits:
  - actions:
    - generic_key:
      descriptor_value: some_value
      descriptor_key: some_key

This worked fine and applied rate limits using the domain set on the Rate Limit Filter.  I then needed to override the domain on the route the rate limit was applied and found that there is no configuration for that on route.rate_Limits.  I then looked at the RateLimitPerRoute filter and configured as so:
Rate Limit Per Route
route:
  cluster: jsonplaceholder
  host_rewrite_literal: "jsonplaceholder.typicode.com"
typed_per_filter_config:
  "envoy.filters.http.ratelimit":
    "@type": type.googleapis.com/envoy.extensions.filters.http.ratelimit.v3.RateLimitPerRoute
    domain: overridewiththis
    rate_limits:
    - actions:
      - generic_key:
          descriptor_value: some_value
          descriptor_key: some_key

What I found is that requests were not fired to the rate limit service at all with the above route configuration using a RateLimitPerRoute filter. After some trial and error, the following is what I did to get it to work, which seems odd:
Working
route:
  cluster: jsonplaceholder
  host_rewrite_literal: "jsonplaceholder.typicode.com"
  rate_limits:
  - actions:
    - generic_key:
        descriptor_value: some_value
        descriptor_key: some_key
typed_per_filter_config:
  "envoy.filters.http.ratelimit":
    "@type": type.googleapis.com/envoy.extensions.filters.http.ratelimit.v3.RateLimitPerRoute
    domain: overridewiththis
    # These rate limit descriptors don't seem to apply and instead are taken from route.rate_limits[].actions
    #rate_limits:
    #- actions:
    #  - generic_key:
    #      descriptor_value: b
    #      descriptor_key: g

What I found is that I need to defined route.rate_limits with actions for the descriptors for it to fire against the rate limit service.  I then also need to apply the RateLimitPerRoute filter, but only for the purpose of overriding the domain used on the route.rate_limits.  Any actions defined in the RateLimitPerRoute filter seem to be ignored and have no impact on the request to the rate limit service.
Is this intentional, am I doing something wrong / misinterpreting the config, or is this a bug?
Repro steps:

Deploy a rate limit service (https://github.com/envoyproxy/ratelimit)
Start Envoy with the below YAML (updating rate limit service details)
Observe the rate limit service and see no requests being sent

Full Config
admin:
  address:
    socket_address: { address: <IP_ADDRESS>, port_value: 9901 }

static_resources:
  listeners:
  - name: listener_0
    address:
      socket_address: { address: <IP_ADDRESS>, port_value: 10000 }
    filter_chains:
    - filters:
      - name: envoy.filters.network.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          stat_prefix: ingress_http
          codec_type: AUTO
          route_config:
            name: local_route
            virtual_hosts:
            - name: local_service
              domains: ["*"]
              routes:
              - match: { prefix: "/" }
                route:
                  cluster: jsonplaceholder
                  host_rewrite_literal: "jsonplaceholder.typicode.com"
                  #rate_limits:
                  #- actions:
                  #  - generic_key:
                  #      descriptor_value: a
                  #      descriptor_key: general
                typed_per_filter_config:
                  "envoy.filters.http.ratelimit":
                    "@type": type.googleapis.com/envoy.extensions.filters.http.ratelimit.v3.RateLimitPerRoute
                    domain: overridewiththis
                    rate_limits:
                    - actions:
                      - generic_key:
                          descriptor_value: b
                          descriptor_key: g
          http_filters:
          - name: "envoy.filters.http.ratelimit"
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.ratelimit.v3.RateLimit
              domain: override-at-route
              timeout: 1s
              failure_mode_deny: true
              rate_limit_service:
                grpc_service:
                  envoy_grpc:
                    cluster_name: some-rate-limit-service
                    authority: some-rate-limit-service.com
                transport_api_version: V3
          - name: "envoy.filters.http.header_mutation"
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.header_mutation.v3.HeaderMutation
          - name: envoy.filters.http.router
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router

  clusters:
  - name: jsonplaceholder
    connect_timeout: 1s
    type: LOGICAL_DNS
    lb_policy: ROUND_ROBIN
    dns_lookup_family: V4_ONLY
    load_assignment:
      cluster_name: google
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: jsonplaceholder.typicode.com
                port_value: 80
  - connect_timeout: 1s
    http2_protocol_options: {}
    name: some-rate-limit-service
    type: LOGICAL_DNS
    load_assignment:
      cluster_name: some-rate-limit-service.com
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: some-rate-limit-service.com
                port_value: 9999

cc @esmet @mattklein123 as codeowners, and @wbpcode who may be able to assist.

https://github.com/envoyproxy/envoy/blob/b87da3fa9f008d87ab02df53840c5246f1ba6209/api/envoy/extensions/filters/http/ratelimit/v3/rate_limit.proto#L394
The "not-implemented-hide" option is enabled, so the rate limits configuration in RateLimitPerRoute is not applied.


LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20210717094535063 to main

LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20210717094535063 to main with localized lcls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 42.571%

Totals

Change from base Build<PHONE_NUMBER>:
0.002%

Covered Lines:
26721

Relevant Lines:
56890

💛  - Coveralls


Add No Proxy settings to not proxy IBM Cloud endpoints for PowerVS

What this PR does / why we need it:
fixes #1738
fixes https://issues.redhat.com/browse/MULTIARCH-2795
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #
Checklist

[x] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/cc @mkumatag

/assign @csrwng

/retest-required

/retest-required

Please use
https://github.com/openshift/hypershift/blob/cb7c55daf7f06d46eddbdbaa529c1593ace58640/konnectivity-socks5-proxy/main.go#L263
consistently with other platforms.
See https://issues.redhat.com/browse/HOSTEDCP-568

We had a discussion regarding adding ibmcloud endpoints to exceptional list in the quoted func. But @relyt0925

@enxebre I have added cloud.ibm.com into konnectivity isCloudAPI func(), ptal!

/approve
cc @csrwng @relyt0925 https://github.com/openshift/hypershift/pull/1741#issuecomment-1254883243

/lgtm

/retest-required

/retest-required


feat: short adjective generation algorithm

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

54 of 54 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 92.577%

Totals

Change from base Build<PHONE_NUMBER>:
0.2%

Covered Lines:
1682

Relevant Lines:
1760

💛  - Coveralls

Superseded by #64.


Add deprecated annotations on shorthand functions for deprecated operations

Motivation
If an operation is marked as deprecated in the OpenAPI document then the generated protocol requirement is annotated as deprecated. However, the shorthand overload for this function, in the protocol extension, was missing this annotation.
Modifications
Add deprecated annotation to the generated function in the protocol extension for deprecated API operations.
Result
If an operation is marked as deprecated in the OpenAPI document then both variants of the generated function (the protocol requirement and the protocol extension) are annotated as deprecated.
Test Plan
Updated the snippet test to include a path with one deprecated operation and one non-deprecated operation.
Related Issues

Fixes #367.

I just met this one today :-)

@groue we published a release today with the fix


Healthcheck not working with ALLOWED_HOSTS

The HEALTHCHECK does not work if you set the ALLOWED_HOSTS environment variable.
If set calling http://localhost:8000 will result in a 400 Bad Resuest and the container won't start. removing ALLOWED_HOSTS from environment fixes it, but is not permanent solution in my opinion.

@samuel-p Can you check what happens if you add localhost to the ALLOWED_HOSTS list?

@galexrt yes, if I add localhost to the ALLOWED_HOSTS list, it works.

@samuel-p Do you see that as a valid solution to add localhost to the examples, etc, to include localhost by default?

For me it's a valid solution, but I think it would be important to add a small note to the setup docs, if someone else has the same problem.

@samuel-p I have updated the README and examples to have localhost included in the examples + added a note to the ALLOWED_HOSTS var description table.
Resolved by 6681abc607d4d1003a9d00a05ece3b80a71ccd87.


Breathing effect is active even when player is dead.

Maybe add ply:Alive() check for breathing effect emitting?

Sorry for the slow answer .. fixed in next version.


The security of running arbitrary code in docker containers

I couldn't really find any documentation on how the security regarding docker containers is addressed. As far as I was aware, the consensus was that the isolation provided by them ought not to be considered as secure. Does openwhisk take any measures to address that; or maybe there are specific reasons why this is not a concern in this context?

Container security is handled from outside - access to resources and network isolation are of course necessary. There was a push to integrate AppArmor into the openwhisk code base (I’ll link for posterity) but the work wasn’t completed.


Multiple selects spill out of container in v4-docs

The example multiple select on v4-docs is off for me. The numbers spill out of the container.
Here is an image
It seems like problems with overflow: hidden. You can fix it with select.form-control { overflow-y: hidden; } in your CSS.

Duplicate of #20384. Please search more in the future! Thanks.


@orta => fix for sale artworks

Fixes #133
As can be seen in https://github.com/artsy/eigen/commit/de193e8917e526c43f12448d92d6ba7a6f7d8160 this makes it so that when you select ‘for sale’ artworks it actually only shows those that are for sale.

It was an interesting fail before, wonder what was up there.


Change all events to allow forwarding the sender

The SteamVR and Oculus SDK repos also need updating as they use Actions too


100% CPU load

ETS_Dashoboard.exe uses all teh CPU time that is left from other programms, creating a permanent 100% CPU load. This affects everything on my Windows system, even when the Truck Simulator is not running (ATS or ETS2).
The used Funbit.Ets.Telemetry.Server already uses 6 up to 15% of my CPU time. Both together have a severe impact on The Windows System as well as thon the Truck Simulators (ATS and ETS). I am not using the newest Hardware, but with ETS_Dashboard and the Telemetry Server disabled I have a quite good gaming experience.
PC-Specs:
CPU: Intel Core I7 860 @2.80GHz
RAM: 16GB RAM
GPU: nVidia Geforce GTX1060 6GB
SSD: Crucial MX500 2TB + 1TB (SATA)
OS: Windows 10 Pro, Version 22H2, Build 19045.2486
ETS2 and ATS steam Version, several Mods.
Task-Manager before starting ETS_Dashboard.exe:

Task-Manager after starting ETS_Dashboard.exe, Truck Simulator not yet started:

Other Programm Running are:
Google Chrome
Firefox
Discord
and of course: Touch Portal

Sorry for the late reply:
If you still have this problem, you can try this:
I have added a web page where you can disable unneeded "modules". As an example: TruckersMP. This will result in lower "refresh rates" and this will result in lower CPU usage.
This plugin is not suitable for low-spec PCs. I am working on optimizing it, but my time is quite small. You can also try changing the refresh interval to something larger. Just go to the plugin folder -> Config and open "cfg.json" and change the "refreshinterval" number to something larger. This number is in ms. So 1000 would be 1 second.
Hope it helps until I have an optimized version.

Thanks for the answer. I will try this out and let you know if this helps. At the time when I bought that PC it was almost the best you could get. Well, now an Core I3 is faster... time passes ;-)


Update ecmaVersion to 'latest' in esnext.js in eslint-plugin to ensure it's esnext.

Description
This PR updates a simple config in esnext.js in eslint-plugin, it prevents some potential problems.
It updates
  parserOptions: {
    ecmaVersion: '2018',
    sourceType: 'module',
  }

to
  parserOptions: {
    ecmaVersion: 'latest',
    sourceType: 'module',
  }

so to ensure it always be esnext latest version.
Here is the official docs mentioned: https://eslint.org/docs/user-guide/configuring/language-options#specifying-parser-options.
Also updates env es6 to es2021.

Type of change

[x]  Patch: Bug (non-breaking change which fixes an issue)
[ ]  Minor: New feature (non-breaking change which adds functionality)
[ ]  Major: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[ ] I have added a changelog entry, prefixed by the type of change noted above (Documentation fix and Test update does not need a changelog as we do not publish a new version for these changes)

@iamyoki I think you added it twice by mistake, heh :)