set log4j root logger thru variable

Description
Same as #598 for 6.1.0 branch

Hi @piif ! Thanks for all your interest/improvements! Please review https://github.com/confluentinc/cp-ansible/pull/572
Which I believe covers the work you just did. Also we try to make all of our PRs into .x branches (ie 6.1.x). I should add that into our contribution guide.

Hi @domenicbove, #572 contains actually what I need and much more, thus it seems perfect as a replacement of mine !
I note for future contributions to work on .x branches instead of -post ones, thanks.

Yes sorry for the confusion. the .x branches are our "future release" branches, ie 6.0.x will become 6.0.3-post on our next release. It's our best way to keep things versioned. And we try to keep only minor features/ bugfixes on the 6.0.x and 6.1.x ... for major features those would go onto 6.2.x and get released with our next major version.
I think this PR can be closed bc the logic is already committed to 6.1.x branch, wdyt?

I agree, we can close.
Thank you for your help


Setup linting/husky hooks, CI job and run prettier on full project

@pavanjoshi914 can you help us with this one? you did it on a few projects already.
Currently we get random changes in our PR diffs which make it harder to see what actually changed.
From https://github.com/getAlby/go/pull/106

Fixed in #139 and #169


Certificates for double proxy (mTLS)

Title: Certificates for double proxy (mTLS)
Description:
The envoy docs has an example of running double proxy using Envoy for postgres. However, the docs does not cover which certificate is to be used where. The guide generates 2 certificates with the same key. The docker-compose file in the repo refers to the certificates in a different name, making it not clear on which certificate to use on which machine(container).
A section to clarify that in the guide would be helpful.
I am following the same guide and have generated certificates for AWS EC2's internal DNS name. However I get the error TLS error: 268435581:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED on the client side and TLS error: 268436502:SSL routines:OPENSSL_internal:SSLV3_ALERT_CERTIFICATE_UNKNOWN on the server side.
Server Envoy TLS config section -
transport_socket:
        name: envoy.transport_sockets.tls
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.DownstreamTlsContext
          require_client_certificate: true
          common_tls_context:
            validation_context:
              trusted_ca:
                filename: /home/ubuntu/certs/ca.crt
            tls_certificates:
              - certificate_chain: { filename: "/home/ubuntu/certs/ip-10-0-101-153.ap-south-1.compute.internal.crt" } # ip-10-0-101-153 is the IP of the server machine
                private_key: { filename: "/home/ubuntu/certs/ap-south-1.compute.internal.key" }

Client Envoy TLS config section -
transport_socket:
        name: envoy.transport_sockets.tls
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.UpstreamTlsContext
          common_tls_context:
            tls_certificates:
            - certificate_chain:
                filename: /home/ubuntu/certs/ip-10-0-101-74.ap-south-1.compute.internal.crt # ip-10-0-101-74 is the IP of the client machine
              private_key:
                filename: /home/ubuntu/certs/ap-south-1.compute.internal.key
                #tls_params:
                #tls_minimum_protocol_version: TLSv1_2
                #tls_maximum_protocol_version: TLSv1_2
            validation_context:
              match_subject_alt_names:
                - exact: ip-10-0-101-74.ap-south-1.compute.amazonaws.com
              trusted_ca:
                filename: /home/ubuntu/certs/ca.crt

[optional Relevant Links:]
https://www.envoyproxy.io/docs/envoy/latest/start/sandboxes/double-proxy

re the docs - i would be more than happy to review a PR to clarify how the certs are used
to give some context - the Dockerfile where the certs are loaded is here https://github.com/envoyproxy/envoy/blob/main/examples/shared/envoy/Dockerfile#L49
it may be helpful to add some comment in the compose file about looking there
for how the certs are used you need to look in the envoy frontend/backend yaml files
the sandbox is pretty focused on explaining how to setup and use the certs so would be good if we can make this clearer

hmm - you may be right - this needs to set TLS termination in the "frontend" envoy
that would break using postgres i think (not 100% sure) so it would also require changing what was used as a backend
definitely open to a PR to update this - otherwise i will look further when i have time


the vibe amd wave

https://patch-diff.githubusercontent.com/raw/Homebrew/homebrew-core/pull/97741.patch

Hello @money5240, can you add more details please? :) How did you get this issue?

def fibonacci(n)
return n if ( 0..1 ).include? n
(fibonacci(n - 1) + fibonacci(n - 2)) #recursive calls
end

@curquiza that's spam, can you prevent this user from posting here again?


Require MemPostings.Commit() to actually index the series

This changes the way we interact with MemPostings, by batching the additions into "pending" state, and then actually creating them in the "Commit" phase.
Anyone can call Commit at any moment, which will add all pending postings, not just the ones from that caller.
This is intended to reduce lock contention on very high churn instances, where lots of Add() calls compete with the reads: this way there will be only one Add() call that will create all pending to be created postings.

I did not update tests because I'd like to get some feedback from the reviewers on the logic first.
There are a lot of tests that call Add() or getOrCreateSeries() that will need a Commit() call.

Updated the tests, added one for the Delete when deleted series are still pending (which is very unlikely)

@bboreham suggested that if we do this, we might be able to do EnsureOrder more efficiently.
I did that in a separate commit, without adding it to this branch: https://github.com/colega/prometheus/commit/b90d6da1359b4eaa302b1977d95dc4d1f3ff2a60
I think it should improve the performance (as we now don't need to sort lists for each label, just one pending list), but it should be benchmarked separately IMO.

I tested the first approach on a real environment, and saw an increase in both append latencies and mutex contention times.
After thinking twice, that made sense: now every append had to wait on MemPostings.Commit(), regardless of whether they created series or not.
I've pushed two more commits.
One of them adds a pendingWatermark marker to MemPostings and the highestCreatedSeriesRef to the appender, so the appender can skip committing if it didn't create series, or if the series that it created are already committed.
The other one adds a TryCommit method, that tries to grab the pendingMtx, but skips it if it's already taken: which is most likely indicating that someone is committing, and retries the commit later.
I'll now test this approach.

I've tested this under production-like load and the results were quite deceptive. The latencies and the mutex contention metrics look exactly the same as before the change, so it's definitely not worth the change.
Thank you for the review, @codesome, I'm sorry to have wasted your time.
I'm testing two more approaches in our fork now: https://github.com/grafana/mimir-prometheus/pull/750 and https://github.com/grafana/mimir-prometheus/pull/752 (this one is quite radical and I'm skeptical), I'll bring them here once I've confirmed that they are improving the situation.


Update description.md

test case

Hi, @MSKSamurai . This PR does not seem to contribute any fixes. Please review and reopen it if necessary. Thanks!


Theme & Font info

It is a great project & You guys have done a great job.
Sorry to ask this question here.
May i know the theme , font used in the below snapshot? It is just awesome

Check out this. 😊

@robertohuertasm  Thank you sir


cattle-global-data namespace which has resources relating to Global DNS is not part of any project.

Rancher server version - Build from master - Jan 21
Setup - HA setup with 2 clusters.
Steps to reproduce the the problem:

Create Multicluster App - mcapp1 for cluster1 and cluster2 with Global DNS enabled Ingress for fqdn - "test1.test.com"
Create globalDnsProvider with root domain - "test.com"
Create a globalDns entry with fqdn - "test1.test.com" pointing to Multicluster App - mcapp1.

There is cattle-global-data namespace created in the local cluster which has resources relating to Global DNS.
It would be better to have this namespace moved to "System" project which has other namesapaces like cattle-system which has rancher specific resources.

Tested with latest build from master - Feb 13,
cattle-global-data ns is now created as part of system  project in local cluster. field.cattle.io/projectId get set in labels and annotations.
        "annotations": {
            "cattle.io/status": "{\"Conditions\":[{\"Type\":\"ResourceQuotaInit\",\"Status\":\"True\",\"Message\":\"\",\"LastUpdateTime\":\"2019-02-14T04:06:13Z\"},{\"Type\":\"InitialRolesPopulated\",\"Status\":\"True\",\"Message\":\"\",\"LastUpdateTime\":\"2019-02-14T04:06:18Z\"}]}",
            "field.cattle.io/projectId": "local:p-475rj",
            "lifecycle.cattle.io/create.namespace-auth": "true"
        },
        "labels": {
            "cattle.io/creator": "norman",
            "field.cattle.io/projectId": "p-475rj"
        },

Did the following basic check:

Create a multicluster app with targets in 2 projects from 2 different clusters with fqdn set.
Create Global DNS provider using route53 DNS entry.
Create Global DNS entry for the multicluster app .
DNS entries get created successfully in route53 with node ips of the cluster were the multicluster apps are deployed.


Update metadata and polish testing and linting config

Update URLs to github.com/globalizejs.
Add package-lock.json file.
Remove redundant grunt-cli.
Switch from JSHint+JSCS to ESLint, and make test/ pass.
Build: Remove or mark newly-found unused variables.

See individual commit messages for more details and smaller diff.

Thanks for the updates @Krinkle!

At the moment, I am waiting for the CLA to pass for merging it.

@rxaviers Oops, done!

Thanks


"time" scale axis but ordered by "dataset". Is this possible somehow?

Version
5.3.3
Link to Minimal Reproduction
https://codesandbox.io/s/echarts-playground-forked-ulq2zv
Steps to Reproduce
In the codesandbox is the code. You can see there are 2 charts. All the same. The only difference is:
First chart has in xAxis type of time

☝ with time we lost sorting of data
Second chart has in yAxis type of category

☝ with category we lost axis formatting as time and time scale nice spacing (Look that nice Dec month in first chart).
If you check the small dataset you'll see it's ordered in ASC order.
const dataset = [
  ["date", "amount"],
  ["2022-11-01", "1"],
  ["2022-11-02", "2"],
  ["2022-11-05", "3"],
  ["2022-11-13", "4"],
  ["2022-11-20", "5"],
  ["2022-12-07", "6"],
  ["2022-12-04", "7"],
  ["2022-11-10", "8"],
  ["2022-12-15", "9"],
  ["2022-12-24", "10"]
];

Current Behavior
First chart where xAxis is of type time the order of the dataset is not respected.
Expected Behavior
I'm not sure if this is possible or even expected but I would love to be able to have the nice work Echarts does with time scale axis formatting and deciding the right amount of ticks based on volume but respecting the order of the dataset.
Environment
- OS:
- Browser:
- Framework:

Any additional comments?
What I would want is to have a time series axis with formatting and tick spacing but the order would be mark by dataset.

This is by design.
When xAxis is type='time',  X axis values are sorted automatically b/c they need to be in (time) order.
  Result: "2022-12-07" shows after "2022-12-04" correctly.
When xAxis is type='category', order does not matter and X axis values appear as they are in the dataset.
  Result: "2022-12-07" shows before "2022-12-04", which is incorrect.
Y values ('amount') show always in their original dataset sequence. That's why after sorting the dataset with source: dataset.sort(), we get a different polyline, even though the individual values remain the same.
Demo Code

This is by design.

That was my suspicion.
My question is if it's possible to get the benefits of time scale cascading automatic formatted time based without enforced time sorting on X axes

But "Cascading Templates: to adopt different formatters for different time granularity" - is just 'makeup' (formatting) of the values, it does not affect the axis-values order.
If you want "without enforced time sorting on X axes", the answer is already in your example - use xAxis type='category'.
Could you provide a desired output chart to clarify your goal ?

So I guess my question is how I can use cascading templates on a category type axis?

In fact Cascading Templates are for time type axis only.
For category type axis one could use Callback Functions formatting.
Demo Code

I know I can use a callback function. I was asking for a way of using cascading templates without reimplementing it myself : ) . Thanks anyway


"Commit" and "PR" are obfuscated

Instead of showing the actual commit hash and the PR number, random useless characters are being displayed:

These almost look like base64 encoded strings... and sure enough, they are:
» echo "MDY6Q29tbWl0ODY4Mzg3NzI6YjQ5NTY3ZTg1MDVhMjU0ZmZhNGIxZjM5ZGI2ZjFjZmI3ZmUyMDYxZA==" | base64 --decode
06:Commit86838772:b49567e8505a254ffa4b1f39db6f1cfb7fe2061d

» echo "MDExOlB1bGxSZXF1ZXN0MTkyNzk2ODMy" | base64 --decode
011:PullRequest192796832

Any idea how we can get the actual commit hash and PR number to display instead?

Hi and thanks for raising an issue!
The strings you see there are the Github Commit ID and PR ID, which are as you say base64 obfuscated. I just kept them like that because the commit hash and PR number (and more) is output in the metadata on get and put steps.
That being said, we can always base64 decode and output non-obfuscated strings as well.
What do you think?

+1 for showing the actual PR#.  I don't see a ton of value in seeing something like pr MDExOlB1bGxSZXF1ZXN0MTkyNzk2ODMy on the UI.

I'll take a look at this in the morning; I believe it will require switching from the GraphQL API for get and put, but I don't think it will affect cost (rate limit) in any way. And pull request number + commit ref actually means something, so why not 😄

@jacob-hd and @billimek - Merged #27 just now and versions are now represented as:

pr: <number>
commit: <sha>
committed: <committed date>

Docker hub should be building a new image as I write this, so the dev tag should include the latest changes from master. Would you mind testing the changes and seeing if they work for you?
(PS: Overall it makes the versions more readable as was the goal, and also requires one less API call in a get step. The change introduced one more "caveat" which is noted in this TODO. Think I'll fix that one when someone runs into it and files and issue?).

Released in v0.5.0 - closing this issue. Feel free to resubmit if needed.


python.analysis.extraPaths setting supported?

Hi. Pylance looks great.
Is the "python.analysis.extraPaths" setting in settings.json supported by the pylance extension? I can't seem to get it working and wanted to check it is actually used by pylance. Or is there another way to tell pylance about other paths to search for imports?  Does pylance make use of the pyrightconfig.json file for example?
Thanks.
More info...
I have some pypi packages downloaded in a separate directory called vendor and I'm trying to get pylance to search this extra directory.
More specifically, I have the directory /home/myusername/myrepo/vendor/py_deps/pypi_beautifulsoup4/ which contains the py4 beautiful soup package downloaded from pypi.
I can successfully run my python program by adding /home/myusername/myrepo/vendor/py_deps/pypi_beautifulsoup4/ to PYTHONPATH, as an import such as import py4 is then resolved correctly.
However with pylance I get a 'reportMissingImports error'. I've tried adding the path to my vendor/pydeps/pypi_beautifulsoup4 directory to "python.analysis.extraPaths" but I get the same error and can't tell if pylance is using this particular setting.
# /home/myusername/myrepo/src/somepackage/main.py

import bs4 # Import "bs4" could not be resolved Pylance (reportMissingImports)

def main():
    pass

The same here. What i have tried:

.env in workspace root
PYTHONPATH=./lib/python:${PYTHONPATH}

.vscode/settings.json

{
    "terminal.integrated.env.linux": {
        "PYTHONPATH": "${workspaceFolder}/lib/python:${env:PYTHONPATH}"
    },
    "python.envFile": "${workspaceFolder}/.env",
    "python.analysis.extraPaths": ["${workspaceFolder}/lib/python"]
}

my workspace structure is:
| .vscode
| .env
| lib
- | python
--- | local
------ | __init__.py
------ | somePackage
---------| __init__.py
---------| ...

and during import
from local.somePackage import something
still have warning:
import could not be resolved

Thanks for the feedback.
The setting is supported.
I'm not sure what is happening in @mikelnrd 's case, but for @htarnacki it looks like the issue is that we don't support replacing variables such as $(workspaceFolder}. Since the path is relative to the workspace folder, you should be able to change it to;
"python.analysis.extraPaths": ["lib/python"]

The variables are something that the Python extension does, but isn't in the VS Code API or LSP. (microsoft/python-language-server#1783)

"python.analysis.extraPaths": ["lib/python"]
and this has resolved my problem. thx! ;-)

It doesn't work for me with ..
"python.analysis.extraPaths": ["../../lib/"]

Hi folks, Pylance looks great. I just want to report the problem in my own project.
I have written several packages in my project, i.e., base, 'utils', 'dataset', where each package is built with __init__.py. But Pylance still couldn't resolve the imports, nor the functions or classes in there. Just a screenshot here:

Pylance needs to know which import resolution paths to use. By default, it uses the root of your workspace. You will need to add these additional paths using the "python.analysis.extraPaths" setting like this:
"python.analysis.extraPaths": ["base", "utils", "dataset", ""]
Note that these paths are relative to your workspace root directory.

This means that I need to include the extraPaths for each workspace I opened? If I do this, then will it have any impact on another different workspace? Thanks!

And I added the settings as follows (with restart of vscode), but the same problem still occurs. Could you please tell me what else should I do?

It depends on which settings.json you place the setting. If you want it to apply to all your workspaces, you can place it in the user settings. I would probably avoid doing this for python.analysis.extraPaths though, unless it really applies to all your Python projects on that machine.
https://code.visualstudio.com/docs/getstarted/settings

It doesn't look like python.analysis.extraPaths is documented on the README or the marketplace entry, so at the very least we should document it.

extraPaths is not working for me with Pylance.
My VSCode workspace is setup like this
<WorkspaceRoot>/tools/python_lib/mypkg/*.py

With the original language server  the following works for me in the workspace settings.
I can navigate between files using F12
You will notice i dont prefix the paths with . If i do prefix, it does not work.
   "python.autoComplete.extraPaths": [
         "tools/python_lib",
      ],

With Pylance I have tried putting entries in the workspace settings and the folder settings. and nothing works.
This is from workspace settings
      "python.autoComplete.extraPaths": [          "tools/python_lib/mypkg",          "tools/python_lib",       ],
And i tried this in folder settings
      "python.autoComplete.extraPaths": [
         "tools/python_lib/mypkg",
         "tools/python_lib",
      ],

Thanks

The name of the setting has changed to "python.analysis.extraPaths". We're trying to standardize on "python.analysis.x" for all type analysis features. Please give that a try and let us know if it works for you.

that resolved it. thank you.

Documentation was added to our README for python.analysis.extraPaths!

Finally, I was able to resolve the annoying import could not be resolved message.  I have no idea why I have to take this extra step of specifying additional paths.
Anyway, for me, I decided to place "python.analysis.extraPaths": ["\\workspace_root\\allprojects\project1"] into the main settings.json for VS Code.  Also, on Windows, remember to escape the backslashes \\ for the directory structure.  Also, I didn't need to muck around by creating .env file within .vscode folder, and adding a bunch of time wasting code.

I have the same issue. When I use a visual python environment and "import tensorflow.keras", I get the error: Import "tensorflow.keras" could not be resolved. But the code can run.
ps: I have added "my env path/Scripts" and "my env path/Lib/site-packages" in the python.analysis.extraPaths.

You should never need to set extraPaths to resolve something installed in your environment. Please file a new issue (or see if #99 covers your problem).

You should never need to set extraPaths to resolve something installed in your environment. Please file a new issue (or see if #99 covers your problem).

Thanks

I have been trying to use PyLance with the latest public release of Code, and I am also experiencing problems using python.analysis.extraPaths.
I have a few folders of skeleton python files containing simple classes, methods, and functions without any of the arguments or anything provided (the skeletons just use *args, **kwargs as the arguments).  These are generated stand-ins for code completion as the libraries only ship as binaries with the application they come from. However, PyLance still reports that the modules cannot be found when trying to use code completion or looking at code that uses these libraries.  I tried using complete paths, relatively pathing from the base of the workspace folder, and I could never get PyLance to pick up these directories and start using them for code completion or code checking.
I did however, find that taking all of these various skeletons and copying their modules and files into to a single directory, and pointing python.analysis.stubPath to that path, does get the auto-completion to kick in, and code analysis too.  This might be a new issue or a regression, I'm just taking stabs in the dark and offering what I have found, if anyone else is still running into issues using PyLance.  It's too bad stubPath only accepts a single string a not a list but at least I'm up and running for now!
I hope some of this is helpful, I'd be happy to spin up a separate issue with more details

Yes, that sounds like a separate issue as well. Typically the skeletons you've described are just type stubs; pyi files that describe the signatures of another library. The default place to put these is in the typings folder if they don't exist in the libraries themselves, but you're free to put your stubs wherever makes sense for your project and override the config. A stub path is the intended thing to use here (stubs only), as compared to extraPaths (which points to real code).

Apparently ${workspaceFolder}  and ${workspaceFolderBasename} are not working with python.analysis.extraPaths

@maurokenny That's #548. Relative paths work in extraPaths.

I've read several tickets on this issue and haven't seen much advice on how python.analysis.extraPaths integrates with Conda. There's lots about how to link up a library that's in your workspace or project. But, when using Conda, I find that I end up with lots of Conda environments, none of which are in my current workspace. If you play around with ML projects on Github, almost every one of them specifies its own environment.
I'm using a multi-root workspace. So I thought that if I added an entry for python.analysis.extraPaths at the folder (per project) level, I'd be able to get rid of the Pylance import errors. You can do this in the VSCode GUI by typing Ctrl-Shift-P, then 'Open Workspace Settings.' Then type python.analysis.extraPaths, click the 'Folder' tab and enter your path.
But it's much easier to edit the vscode/settings.json file in your project to include:
{
    "python.analysis.extraPaths": [
        "/home/username/anaconda3/envs/conda-env-name/lib/python2.7/site-packages/"
        /* Obviously, replace username and conda-env-name with real values. */
    ]
}

In my case I have to do this for each project in a multi-root workspace, as each has its own environment.
It's a shame that Pylance can't use variables like ${workspaceFolder} - hardcoding this path is kind of a drag. It's also a drag to have to do this for pretty much every project. But as of now, that's what seems to be required. Hopefully this will help someone out.

You should never need to set extraPaths to resolve an import coming from your interpreter or its installed packages. If imports are not resolving, that is a separate bug and we'd appreciate a separate issue of that. Note that we don't support (or plan to support) Python 2, if that affects things.
We respect the interpreter chosen by the Python extension; are you saying you need a different interpreter per workspace and the core extension doesn't do that? You may also be interested in a pyrightconfig with executionEnvironments: https://github.com/microsoft/pyright/blob/master/docs/configuration.md

"are you saying you need a different interpreter per workspace"
I often have to set different interpreters per project, not just workspace. If you look at the Conda environment.yml files of various ML projects, they specify different python versions because, usually, they implement different Tensorflow or Pytorch versions that require those versions of Python.
These projects are all in one multi-root workspace (seemed like a good idea - maybe not!). Until I set extraPaths in a vscode/settings.json file at the project level, Pylance would not resolve Tensorflow and Scipy imports.
I want to say that I've seen these problems with Python 3 projects, but now that I think about it, I'm not sure. I'll look into it and will post an update here. The fact that Pylance doesn't support Python 2 would at least explain the problem I'm seeing. If I only have to mess with vscode/settings when Python 2 is involved, that's not so bad.

I think that if you need that level of control and a wide range of environments even within the same workspace, you'd likely benefit from setting up execution environments.

pico8 import only works when the folder containing that file is opened, even with this in settings.json:
    "python.analysis.extraPaths": [
        "${fileDirname}",
        "."
    ]

pico8 import only works when the folder containing that file is opened, even with this in settings.json:
    "python.analysis.extraPaths": [
        "${fileDirname}",
        "."
    ]

Pylance doesn't support all of the different settings templates. See #548.

Pylance doesn't support all of the different settings templates. See #548.

I have set
"python.analysis.extraPaths": [
        "C:\\Program Files\\Side Effects Software\\Houdini 18.5.445\\houdini\\python2.7libs"
    ]

in my settings.json (also tried with forward slashes), but it seems to be completely ignored. It's still claiming that module hou could not be resolved. Used to work with a different VSCode extension.

I have set
"python.analysis.extraPaths": [
        "C:\\Program Files\\Side Effects Software\\Houdini 18.5.445\\houdini\\python2.7libs"
    ]

in my settings.json (also tried with forward slashes), but it seems to be completely ignored. It's still claiming that module hou could not be resolved. Used to work with a different VSCode extension.

This issue is old and closed; it's unlikely your issue is related. You may want to open an new issue with trace logs so we can examine some of the import paths being used, though I will point out that we do not support Python 2.

This issue is old and closed; it's unlikely your issue is related. You may want to open an new issue with trace logs so we can examine some of the import paths being used, though I will point out that we do not support Python 2.

Yea I found out it's because the thing only works when opening a folder but not on single files for some reason.

Yea I found out it's because the thing only works when opening a folder but not on single files for some reason.

I've read several tickets on this issue and haven't seen much advice on how python.analysis.extraPaths integrates with Conda. There's lots about how to link up a library that's in your workspace or project. But, when using Conda, I find that I end up with lots of Conda environments, none of which are in my current workspace. If you play around with ML projects on Github, almost every one of them specifies its own environment.
I'm using a multi-root workspace. So I thought that if I added an entry for python.analysis.extraPaths at the folder (per project) level, I'd be able to get rid of the Pylance import errors. You can do this in the VSCode GUI by typing Ctrl-Shift-P, then 'Open Workspace Settings.' Then type python.analysis.extraPaths, click the 'Folder' tab and enter your path.
But it's much easier to edit the vscode/settings.json file in your project to include:
{
    "python.analysis.extraPaths": [
        "/home/username/anaconda3/envs/conda-env-name/lib/python2.7/site-packages/"
        /* Obviously, replace username and conda-env-name with real values. */
    ]
}

In my case I have to do this for each project in a multi-root workspace, as each has its own environment.
It's a shame that Pylance can't use variables like ${workspaceFolder} - hardcoding this path is kind of a drag. It's also a drag to have to do this for pretty much every project. But as of now, that's what seems to be required. Hopefully this will help someone out.

it work！

Thanks for the feedback.
The setting is supported.
I'm not sure what is happening in @mikelnrd 's case, but for @htarnacki it looks like the issue is that we don't support replacing variables such as $(workspaceFolder}. Since the path is relative to the workspace folder, you should be able to change it to;
"python.analysis.extraPaths": ["lib/python"]

Is there any timeline for supporting $(workspaceFolder} in python.analysis.extraPaths ?

There are no plans to support this because it's unnecessary. The extraPaths setting assumes all paths are relative to your workspace folder, so there's no need to include this variable in the path.

this seems to solve it
{
"python.analysis.extraPaths": [
    "\\\\wsl$\\Ubuntu-22.04\\home\\anyFolder"
  ],
}

@fschiffers, this issue was closed long ago. If you have a bug to report, please open a new issue. If you have a general question, the discussions forum is a better place to post.


fix: changing link to button

I have also changed the link to a button with some CSS brutallism. I have also added an external CSS file for better writing in future. infile CSS was hard to navigate

Thanks! I'm waiting to merge this until we finish up with #35 because that might wind up rewriting this page anyway.


⚠ Processors has degraded performance

In 8cbe4a9, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 55 ms

Resolved: Processors performance has improved in b7ad710.


Power calculation won't work with cascaded PDUs

Environment

Python version: 3.8.10
Nautobot version: v1.1.3

Steps to Reproduce

create a power-panel
create a power-feed
create a Site & Rack
create two or more devices with a power-port and power-outlets (example: "pdu1", "pdu2")
Add 1VA to "pdu1" and "pdu2" power-port, Issue: (https://github.com/nautobot/nautobot/issues/816)
create a device which should be powered with max- and allocated draw (example "server", Power: 210 max, 210 allocated draw)
Connect the following: Panel -> Feed -> (port) pdu1 (outlet) -> (port) pdu2 (outlet) -> (port) server

What did you expect to happen?
In Rack View: "Power Utilization" should show "210" (server draw)
In Feed View: "Utilization (Allocated)" should show "210" (server draw)
In pdu1 View: "Power Utilization Input" should show "210" (server draw)
In pdu2 View: "Power Utilization Input" should show Available and Utilization and "210" allocated (server draw)
The Rack-View should show the combined value of all devices in it.
The Feed should show all devices which are connected to both pdus on the feed.
What happened instead?
In Rack View: "Power Utilization" shows 1 (power value from pdu2)
In Feed View: "Utilization (Allocated)" shows 1 (power value from pdu2)
In pdu1 View: "Power Utilization Input" shows 1 (power value from pdu2)
In pdu2 View: "Power Utilization Input"Available and Utilization are empty and allocated is the "power-port value (1)"
INFO:
There was an open Netbox issue, which should be the same problem:
https://github.com/netbox-community/netbox/issues/3377

So this is "working as expected" today in that we explicitly don't support recursive calculations on PDUs due to the complex nature of said calculations in the data model.
That being said, we are happy to leave this open if anyone can come up with a reasonable way to do it that does not involve raw SQL.


Fix NPE in setViewOriginalText

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/5745/
Test PASSed.

alluxio-bot, merge this please.


Added the algorithmic environments and performed restructuring

I've added the algorithmic environments with this PR. A lot of time was devoted trying to make the step! function differentiable. Feedback on that is highly appreciated.
In addition to that, a little restructuring was also performed, specially in the rendering function. Since different categories of environments are going to have different render options, I felt it was better for the definition of the render Contexts to be placed in a vis/utils.jl, that should be provided for every category of environment. A :no_render mode was also added and made the default value for the render_mode argument, for when the rendering is not required and to enable faster prototyping. This has two additional benefits-1) Faster loading time for the package, 2) The rendering dependencies for an environment category are only loaded when a user loads an environment from that category. If a rendering option is not supported by a system, the user can still work with the package, if he wants to load an environment from a different category.
Commits up till 0d8467e are covered in #29 , so please ignore them.

@tejank10 Can you please review the step!() to make sure that it's differentiable? The step!() is common for all the environments so I'm not sure, so it should be easy.

These few PRs have become a mess. Going to purge them all and create a new single PR with the latest code and work my way from there


Renaming SteamVR folder on launch?

There has been a long-lasting issue with Roblox where regardless if the player has VR mode enabled or disabled, SteamVR would launch with Roblox (even when Steam itself is closed!!), causing an inconvenience to users using lighthouse-based tracking (turning on and off the base stations repeatedly can considerably shorten the lifespan).
This has been reported to Roblox for a while now (like this post on devforum in 2022), but the issue keeps appearing or related fixes causing other regressions with VR support in general.
https://github.com/pizzaboxer/bloxstrap/assets/95180094/fca887ce-79a5-4fbf-badb-0c813a2a90ac
Would it be possible to implement a native toggle for renaming the SteamVR folder on launch? This would especially be useful regardless if you want to use desktop or VR since SteamVR locks the path when running, so you can actually start SteamVR on your own accord.
Thanks in advance.

Maybe not renaming the folder, I wouldn't expect that to be very reliable. However, you could try setting your rendering mode as Vulkan through the Bloxstrap menu? It wouldn't be the best solution as Roblox would crash when you minimize, but it would work for now. I could take a look into what else can be done.

Renaming the folder is what other clients unrelated to Roblox (e.g., BSManager) do, but I can try running on Vulkan.

Using Vulkan does fix the issue of launching Roblox without SteamVR, but also seems to break VR functionality altogether. When launching the client, a stretched VR-like loading screen will appear, but then show the desktop view (no output to VR)

but also seems to break VR functionality altogether.

Yeah, I kinda thought that was the goal...
Renaming it may work, but things can become ugly if it's not cleaned up properly, like if Bloxstrap encounters an exception, doesn't exit properly, etc. Also, it would mean for Bloxstrap to stay running in the background until Roblox is closed. I'm sure there's at least some better way to do it.

Yeah, I kinda thought that was the goal...

Maaaaaybe for some people, but I do like using Roblox VR sometimes unfortunately 😭
For what it's worth, in my testing renaming the SteamVR folder back to "SteamVR" after the Roblox client itself has launched works fine, even when it goes back into the desktop app view and joining another. It's just on initial startup of the Roblox client would the folder need to be renamed. Not sure if that'd help any?

in my testing renaming the SteamVR folder back to "SteamVR" after the Roblox client itself has launched works fine

Oh, that's great then. My last concern would've been filesystem permissions, but that might not be a problem since all users system users appear to have full access to it. Shouldn't be too hard to add this as a feature.

Can confirm full control is given to all users.

Thank you so much!!

This would be a big hack. I'd prefer finding a better solution than going through with this.

This would be a big hack.

On the other hand, if we can make this approach stable enough then it shouldn't be a problem.

This would be a big hack.

On the other hand, if we can make this approach stable enough then it shouldn't be a problem.

I would kill the SteamVR process instead of renaming the SteamVR folder. If Bloxstrap unexpectedly crashes/closes, chances are that the SteamVR folder will not be renamed back.

The last I looked into this problem, it was that Roblox will launch SteamVR if it's not running, and killing the process for it while it had already registered with Roblox wouldn't cause things to play out nicely. If I'm misremembering or if it's changed now and killing the process doesn't cause any issues, then we'll go with that.

killing the process for it while it had already registered with Roblox wouldn't cause things to play out nicely.

That's unfortunately how it is. That's how it works with all VR experiences (outside of Roblox; if I'm not mistaken, the Oculus client does this too for other apps, but otherwise that's definitely how SteamVR functions).
If Bloxstrap crashing is a concern, you can probably make a detached console process that waits a certain amount of time before renaming the folder back? Probably far fetched, but just an idea

We could, but then what if the system unexpectedly shuts down in the middle of gameplay?
Y'know, it's been so long that I've completely forgotten the details of this issue, and so I've completely forgotten that none of this is really an issue, because as you've said:

renaming the SteamVR folder back to "SteamVR" after the Roblox client itself has launched works fine

It would only need to be renamed back like a few seconds after Roblox has launched.

Assuming your SteamVR folder is in it's default location you can make a batch script in the same folder as the roblox folder with this in it, (or adapt the SteamVR path if necessary) and make a shortcut for it on your desktop.
@echo off
cd "C:\Program Files (x86)\Steam\steamapps\common\"
rename SteamVR SteamVR.bak
start "" "%~dp0RobloxPlayerBeta.exe"
timeout /t 5 /nobreak > nul
rename SteamVR.bak SteamVR
exit

Assuming your SteamVR folder is in it's default location you can make a batch script in the same folder as the roblox folder with this in it, (or adapt the SteamVR path if necessary) and make a shortcut for it on your desktop.

Thank you so much @iPixelGalaxy, this actually put me in the right direction of a little workaround. I still launch Roblox via Bloxstrap, but Bloxstrap also has its own method of launching external programs in parallel with Roblox

I went ahead and modified this batch script so it wouldn't launch Roblox, and added an if/else to check if the folder existed in the first place (TIL this was actually a thing with batch scripts).
@echo off
cd "C:\Program Files (x86)\Steam\steamapps\common\"
if exist SteamVR\ (
   rename SteamVR SteamVR.bak
   timeout /t 5 /nobreak > nul
   rename SteamVR.bak SteamVR
   exit
) else (
   echo folder no exist
   exit
)

I know it's taken me a year to get around to doing this... for some reason. Is anyone able to confirm that this is still an issue?

I know it's taken me a year to get around to doing this... for some reason. Is anyone able to confirm that this is still an issue?

  I can check again

Alright, good to know it's doable without having to do this workaround. @sylviiu if you can check that'd be great.

Assuming this can be marked as resolved now


[ALLUXIO-2523]correct a typo in KeyValueMasterClient.java

https://alluxio.atlassian.net/browse/ALLUXIO-2523

Can one of the admins verify this patch?

use my computer instead! forget to change username


Create Links “tiktok-16”

Automatically generated by Netlify CMS

👷 Deploy Preview for distracted-hoover-7b89cc processing.
🔨 Explore the source changes: 116c93e1d501a88bf66930b282f7411fe68d0d8d
🔍 Inspect the deploy log: https://app.netlify.com/sites/distracted-hoover-7b89cc/deploys/610d844a1262f60008491b41


Fix: use recommended nonce in the nonce warning

What it solves
Resolves #3506
How this PR fixes it
The condition to show a nonce warning was relying on lastTxNonce, whereas the warning itself was displaying a recommendedNonce.
Now it's using recommendedNonce in both places, so it should never show the absurd message from the bug report.
I've also renamed the useRecommendedNonce hook.
How to test it

Try to create transactions with a nonce out of order.
Try a nonce in future
Try a nonce in the past

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

14 of 15 (93.33%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 33.598%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/routes/safe/components/Transactions/helpers/EditTxParametersForm/index.tsx
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
3235

Relevant Lines:
8612

💛  - Coveralls

Issue:
The warning is popping up even if a tx was not executed.
The warning should be there if the nonce that is tried to be used is from an already executed tx.
In this snapshots I've created the tx 141, which cannot be executed because the tx 140 needs to be executed first.
Also when I try to create the 140 (which at this point doesn't exist yet) the warning tells me that it has already been used.

In this snapshots I've created the tx 141, which cannot be executed because the tx 140 needs to be executed first.

I think the warning in this case still makes sense. You can only execute them in order, so 140 -> 141 -> 142.
I would change the wording tho, to smth like:
A transaction with nonce 140 has already been queued. Are you sure you want to replace that transaction?

Oh, now I get it. You skipped 140 and created 141 by overriding the nonce of the previous tx.
Still, the backend returns 142 as the recommended nonce, and the warning message relies on that.

@francovenica does this fix solve the issue described in #3506 though?

I've rephrased the warning a bit, so that it doesn't assert that nonce has been used necessarily.

We still have issues. This is the attempt of execution of the current tx. It seems that, because the recommended nonce (the one that will be suggested when I create a new tx) is 1 more, the warning message is shown.
I think the message should not be shown at all if the tx will be an execution

Great catch, @francovenica!
I'll adjust it to not show the warning in existing transactions unless the nonce was edited.

The message looks fine, and the message not popping up if the nonce is non-editable is fine too.
I think we can merge it
Still, we should discuss further the issue of the warning message telling users that creating the tx that can actually be executed is not recommendable:
In this image tx 94 is the next nonce to be executed in this safe, but tx 95 already exist, ergo the warning message


Culling support

Culling currently doesn't work.
Implementing at least view frustum culling would be awesome for performance with lots of particles.
View frustum culling means not rendering particles outside the player's view.

That's sad. I thought view frustum culling could work because it just needs the FOV, window size, camera location and angle.
Effekseer itself supports it.

Oh I see a Java function that can accept camera parameters. Maybe calling it will enable frustum culling

Try 1.3.1

This sadly didn't fix anything. It's not on Modrinth (which doesn't matter at this point) and the version number is messed up.

You can close this as not planned if you want.

Not planned,
btw 1.3.1 is on Modrinth now :)


feat: GitHub packages

Congrats! The repository doesn't have any security vulnerability issues.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[10.x] Enable use of non global morph mappings for MorphTo & related

In certain cases it is useful to have morph mappings that are disconnected from the global mappings - eg working in a db structure where the same custom key means a different class in different tables (thank you external provider).
I have added an option to pass custom mappings to the morph methods I could find which will then override the global mapping for that segment of the query/relationship rather then having to set and unset the global mapping state.

This is breaking change, it could be added only to the next major release (master branch).

It has been intergrated in a way that doesn't require a breaking change in form of argument shifting in the hopes it can go in sooner then next year. The other option is placing the mappings parameter to the back of the parameter lists but I felt it was batter situated before closures etc but happy to take pointers here.

There are changes in public method signature. It's a breaking change, because they may be overridden in some cases


MSI MPG X570 Gaming Pro Carbon [WiFi ATX]

Not working with this. However, there is a nct6775 present:
[    4.981683] nct6775: Found NCT6797D or compatible chip at 0x4e:0xa20
I can call ./msi-rgb without any error, but nothing is happening.
Any advice how to get this working?

Can you try to add nct6775 at the end of your /etc/modules file and reboot?

The nct6775 module is loaded and working, sensors-detect took already care of it.

If you have a dual-boot with windows, you can try to turn off the lights in mystic light.
If not or it doesn't work, you can try to clear your cmos.


NEED HELP

Hi i have problem with winutil.ps1
When i click on Run Tweaks i get this error
My OS is Windows 11

Checking if Chocolatey is Installed...
Chocolatey Already Installed
Changing system to allow multiple restore points per day
Exception calling "ShowDialog" with "0" argument(s): "The running command stopped because the preference variable "Erro
rActionPreference" or common parameter is set to Stop: Cannot find path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVer
sion\SystemRestore' because it does not exist."
At line:5976 char:1

$sync["Form"].ShowDialog() | out-null

  + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
  + FullyQualifiedErrorId : ActionPreferenceStopException

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

me too i also getting the same
plz recomment when find the solution
if i do i will comment here

Hi i found the solution
You need to enable Changing system to allow multiple restore points per day and this is command
REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SystemRestore" /V "SystemRestorePointCreationFrequency" /T REG_DWORD /D 0 /F
https://www.elevenforum.com/t/change-system-restore-point-creation-frequency-in-windows-11.3613/


inboxer-1.1.5 fails to start

Inboxer-1.1.5 fails to start in my machine with the following error:
A JavaScript error occurred in the main process
Uncaught Exception:
Error: Cannot find module 'tmp'
    at Module._resolveFilename (module.js:543:15)
    at Function.Module._resolveFilename (/usr/lib/electron/resources/electron.asar/common/reset-search-paths.js:35:12)
    at Function.Module._load (module.js:473:25)
    at Module.require (module.js:586:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/usr/lib/inboxer/node_modules/insight/node_modules/external-editor/main/index.js:15:10)
    at Object.<anonymous> (/usr/lib/inboxer/node_modules/insight/node_modules/external-editor/main/index.js:229:4)
    at Object.<anonymous> (/usr/lib/inboxer/node_modules/insight/node_modules/external-editor/main/index.js:231:3)
    at Module._compile (module.js:642:30)
    at Object.Module._extensions..js (module.js:653:10)

Version 1.1.4 was working fine. This problem was introduced by commit 8310e21643b10123e60416e6ea341bc3713fc005, which updated dependency package insight to version 0.10.1. Reverting to version insight-0.8.4 fixes the problem for me.

I'm going to check it

I checked it on Xubuntu 18.04 and Windows 10, I have no problem with 1.1.5 version. What's your OS?

Sorry, I should have provided more details about my system.
I'm running ArchLinux with these packages:
electron 2.0.8
nodejs 10.10.0
semver 5.5.1
node-gyp 3.8.0
npm 6.4.1

Thanks @jmarino ,
I'm going to check in order to get it fixed. Could you help me doing tests after changes?

@jmarino
Check these install files
https://drive.google.com/file/d/1-7rcUcYBonF1kzUrvpHvr9byH-ZVSWKt/view?usp=sharing
Let me know how was it

I'm getting this now w/ 1.1.5 "upgraded"... related? I uninstalled too.

I downloaded your dist1.1.6. Inside I found a .deb package and a .AppImage. I was able to run the AppImage file and it worked as expected, no problems. I was not able to do anything with the .deb file.
I looked inside the .deb file and the .AppImage and things look very different from my local installation here. The way inboxer gets installed in my system is by running npm install --production as shown in the package's build script. Perhaps we're installing things wrong in ArchLinux? I confess I don't know much about electron apps.

@jmarino Would you like using the .deb instead of .AppImage? I'm a newbie at linux. I'm going to install your distro in order to test the app.

Wow, that sounds a bit overkill @jonorozcoc.
I can't use the .deb file because that's a package for debian related linux distros. I prefer not to use the self contained AppImage because it comes bundled with libraries and stuff that I already have in my system, plus it has to extract itself everytime it's run.
Before you go down the ArchLinux rabbit hole let me explore more closely what's inside the .AppImage file and see if I can figure anything out. I used --appimage-extract to extract the contents of the .AppImage and I see that the app is packed as an .asar package. I'll look inside and see how it differs from my local installation.

I extracted the contents of the .AppImage you sent me:
./inboxer-1.1.6-beta1-x86_64.AppImage --appimage-extract
Then I extracted the contents of the squashfs-root/resources/app.asar file and looked at the package.json file, which has this section:
"dependencies": {
    "electron-context-menu": "^0.9.1",
    "electron-dl": "^1.10.0",
    "electron-is-dev": "^0.3.0",
    "electron-log": "^2.2.11",
    "electron-store": "^1.3.0",
    "electron-updater": "^3.0.3",
    "first-run": "^1.2.0",
    "insight": "^0.8.4",
    "minimatch-all": "^1.1.0"
  }

That looks a lot like the 1.1.4 version. Indeed, the version requested for the dependency insight is 0.8.4 (like Inboxer-1.1.4) instead of 0.10.1 (like Inboxer-1.1.5). So it's no wonder this AppImage worked for me, it uses the older version of package insight.
In case you can't extract the .asar file, you can look inside it without having to extract it:
grep -a -A27 '1.1.6-beta1' squashfs-root/resources/app.asar
The command above shows a partial dump of the file package.json file from Inboxer.

It looks like you're building version 1.1.4 by mistake. Maybe you didn't
sync your local repo and are applying your changes on top of 1.1.4 instead
of 1.1.5.
Send me an AppImage of plain 1.1.5 and I'll test it.
On Wed, Sep 12, 2018, 8:20 PM Jonatan David Orozco Cantillo <
<EMAIL_ADDRESS>wrote:

Ok, I'm taking a look on Arch package are made in order to update inboxer
package
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/denysdovhan/inboxer/issues/72#issuecomment-420860864,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADIREvKQcJFzIWCZDgVy-u73ShK0Nzkks5uacDqgaJpZM4Whun9
.

 I can go ahead and download the 1.1.5 AppImage myself from the release page.
So I did that, and I can confirm that the 1.1.5 AppImage works fine in my machine. So I only have the problem when I run a local build of inboxer-1.1.5. I'll try to get more info about what's different between my local build and the official one.

Alright, I figured it out. As expected it's not a bug in inboxer but a bug in the ArchLinux package. As part of the packaging process it was deleting the node_modules/tmp folder where the tmp package was installed. D'oh!


C code formatting

I ran clang-format on the code (whithout having a look at the settings).
It looks nicer now.

Cool, I am very much in favor of using some formatter, like we also use black for python (xref https://github.com/pygeos/pygeos/issues/129#issuecomment-603996645), so +1.
For Apache Arrow, we specify to use Google style, and a slightly larger line length: https://github.com/apache/arrow/blob/master/.clang-format


(#40): Add prettier

All PRs should be based on an issue
WHY?
See issue #40
WHAT?
Add precommit hook to run prettier on SASS and TS files. Also run prettier on all existing files

[x] I have considered (and possibly added) tests
[ ] I have updated the documentation (gitbook)

[Optional] Resolves #40
As it is a very large commit, updated documentation will be on a separate PR later on

Changes Unknown when pulling cbd43f1ef160527abe50d68547867ff7b5f22ae0 on feature/prettier into ** on master**.

Changes Unknown when pulling 5e51c2794198c413bc337b87e2aa26c7dced6a22 on feature/prettier into ** on master**.

Coverage increased (+0.07%) to 90.345% when pulling 06ddb4ab90e33d41305cae922f789a0bef56eadd on feature/prettier into d0d232f6a2709a2a44886080d582dfa6fe143c41 on master.


bug(stepper): Linear mode does not allow skipping valid steps

As far as I understand the linear mode of the horizontal / vertical stepper should disallow advancing to steps that have not yet been completed.
However when presenting an already prefilled form (such as on an edit page) to the user where most of the info is already filled out, I would expect the stepper to allow the user to skip steps which are valid based on the form validations.
Reproduction
https://stackblitz.com/edit/angular-se74ga
Steps to reproduce:

Open page
(notice that the components in step 1 and step 2 have been autofilled, and reload the page to reset state)
Click on the 3rd step, without going to step

Expected Behavior
The stepper should allow switching to step 3. The stepControls in step 1 and 2 are valid
Actual Behavior
It's not.
Environment

Angular: 9.0.0
CDK/Material: 9.0.0
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): N/A

I don't think it's because of invalid form state but rather an unvisited step.
I suppose you could set the override completed flag of the individual mat-steps in the event you have auto-fill data available.
<mat-step completed = "true" [stepControl]="firstFormGroup" [editable]="isEditable">
What I think is happening is that your form control is neither invalid nor pending, but rather that you haven't interacted with step 2 which seems to be a condition for linear mode.
https://github.com/angular/components/blob/b6358b2e32d6cbd3646411fc576e46dc55bcf512/src/cdk/stepper/stepper.ts#L503

Thanks for linking in the releavant code. Setting the completed step brings in other issues indeed (such as changing the icon to the crayon instead of the step numbers), but I would argue that the requirement of the !step.interacted is what is causing the issue. And as far as I understand it's not possible to override this value, becuase it's not an Input().
Not sure what the rationale is behind it being there, I feel like it should be removed.

I am currently working around this like this:
  @ViewChildren(MatStep) steps: QueryList<MatStep>;

  ngOnInit(): void {
    setTimeout(() => { this.steps.forEach(s => s.interacted = true) });
  }

Yeah if I had to guess it's a design choice, maybe this is an opportunity to document the linear input better in the Material docs to also say that interaction with the elements is required regardless.
Could simplify that to:
ngAfterViewInit(): void {
    this.steps.forEach(s => s.interacted = true)
}

I think this is probably working as intended, but it could use better documentation at least


Remove Debian 8 support, is EOL

Pull Request Checklist

Description

Remove Debian 8 support as it's EOL: https://www.debian.org/News/2020/20200709#:~:text=The Debian Long Term Support,security updates for Debian 8.

README reference to Debian 8 is removed


[FLINK-938] Automatically configure the jobmanager address when using start-cluster.sh

Thanks for the PR. I've looked into the other approach (#248) and I think you can safely close this on now.


custom history name duplicates history?

Parallel test execution does save time, but ideally we'd also be able to execute in a parallel across more than one device type.  From what I see in flank.yml, it's currently only possibly to execute on one device at a time.  Is that correct?

thanks so much @bootstraponline. unfortunately not working for me, but perhaps I'm missing something??  I have 31 tests I'm executing across 2 devices, but flank skips the first device listed and only executes 31 tests (on 31 shards) against 1 device.  Afterwards it outputs the results and quits
# https://cloud.google.com/sdk/gcloud/reference/firebase/test/android/run
gcloud:
  results-bucket: tmp_flank_rpapa
  record-video: true
  timeout: 60m
  async: false
  project: my-gnarly-proj

  # RPX
  results-history-name: tmp_parallel

  # test and app are the only required args
  app: ./app/build/outputs/apk/demoX86/debug/app-demo-x86-debug.apk
  test: ./app/build/outputs/apk/androidTest/demoX86/debug/app-demo-x86-debug-androidTest.apkdemo
  auto-google-login: true
  use-orchestrator: true
  environment-variables:
    clearPackageData: true
  directories-to-pull:
    - /sdcard/screenshots
  performance-metrics: true

  test-targets:
    - class org.rpappalax.demo.activity.AccessAboutAndYourRightsPagesTest#AboutAndYourRightsPagesTest
    - class org.rpappalax.demo.activity.AccessSettingsTest#AccessSettingsTest
    - class org.rpappalax.demo.activity.AddToHomescreenTest#AddToHomeScreenTest
    - class org.rpappalax.demo.activity.AddToHomescreenTest#NonameTest
    - class org.rpappalax.demo.activity.AddToHomescreenTest#SearchTermShortcutTest
    - class org.rpappalax.demo.activity.BadURLTest#BadURLcheckTest
    - class org.rpappalax.demo.activity.ChangeSearchEngineTest#SearchTest
    - class org.rpappalax.demo.activity.CustomTabTest#testCustomTabUI
    - class org.rpappalax.demo.activity.DownloadFileTest#DownloadTest
    - class org.rpappalax.demo.activity.EraseAllUserDataTest#TrashTest
    - class org.rpappalax.demo.activity.EraseAllUserDataTest#systemBarTest
    - class org.rpappalax.demo.activity.EraseAllUserDataTest#systemBarHomeViewTest
    - class org.rpappalax.demo.activity.FirstRunDialogueTest#FirstRunDialogueTest
    - class org.rpappalax.demo.activity.ImageSelectTest#ImageMenuTest
    - class org.rpappalax.demo.activity.ImageSelectTest#ShareImageTest
    - class org.rpappalax.demo.activity.ImageSelectTest#DownloadImageMenuTest
    - class org.rpappalax.demo.activity.MultitaskingTest#testVisitingMultipleSites
    - class org.rpappalax.demo.activity.OpenInExternalBrowserDialogueTest#OpenInExternalBrowserDialogueTest
    - class org.rpappalax.demo.activity.PullDownToRefreshTest#pullDownToRefreshTest
    - class org.rpappalax.demo.activity.SettingsBlockToggleTest#SettingsToggleTest
    - class org.rpappalax.demo.activity.ShareWebsiteTest#ShareWebsiteTest
    - class org.rpappalax.demo.activity.SwitchContextTest#ForegroundTest
    - class org.rpappalax.demo.activity.SwitchContextTest#eraseAndOpenTest
    - class org.rpappalax.demo.activity.SwitchLocaleTest#EnglishSystemLocaleTest
    - class org.rpappalax.demo.activity.SwitchLocaleTest#FrenchLocaleTest
    - class org.rpappalax.demo.activity.ToggleBlockTest#SimpleToggleTest
    - class org.rpappalax.demo.activity.URLAutocompleteTest#CompletionTest
    - class org.rpappalax.demo.activity.URLAutocompleteTest#CustomCompletionTest
    - class org.rpappalax.demo.activity.URLAutocompleteTest#DisableCCwithSiteTest
    - class org.rpappalax.demo.activity.URLAutocompleteTest#DuplicateACSiteTest
    - class org.rpappalax.demo.activity.URLMismatchTest#MismatchTest

  device:
    - model: Nexus6P
      version: 23

  device:
    - model: Pixel2
      version: 26

flank:
  # test shards - the amount of groups to split the test suite into
  # set to -1 to use one shard per test.
  testShards: -1
  # repeat tests - the amount of times to run the tests.
  # 1 runs the tests once. 10 runs all the tests 10x
  repeatTests: 1
  # always run - these tests are inserted at the beginning of every shard
  # useful if you need to grant permissions or login before other tests run
  #test-targets-always-run:
    #- class com.example.app.ExampleUiTest#testPasses
    # - class org.rpappalax.demo.activty.SwitchContextTest#testPasses

Also, for some reason the tests show up in the Firebase console in 3 separate groups all with the same "results_history_name"
one tab shows 28 tests, another 2 and the last one 1 test respectivily 🤔

hey, you are using the wrong yaml format.
try this:
 device:
    - model: Nexus6P
      version: 23
    - model: Pixel2
      version: 26

also join https://firebase.community #flank channel, will be faster to discuss in real time.

discussed on slack:

multi-device is working
custom history name appears to duplicate the history?

talked with FTL, history name duplicate is a feature. web UI may be revised in the future to show the underlying package name in addition to the history name.

reopening... looks like duplicates for the same package name are indeed a potential bug.


Small things

Changes

:broom: Small code style refactors that I noticed while looking at the repo, commit messages should be self explanatory. Unit tests are all passing locally. Could not get conformance tests to run sadly :/

/kind cleanup
Release Note
Small code refactors

Docs

What errors are you facing when trying to run conformance tests locally?

/ok-to-test

@gabo1208
Yes I tried make test-conformance locally this is the error I kept on getting:
BROKER_TEMPLATES=/Users/clyu/workspace/eventing-rabbitmq/test/conformance/testdata/with-operator \
	BROKER_CLASS=RabbitMQBroker \
	go test -v -tags=e2e \
		-count=1 -parallel=12 -timeout=20m \
		-run TestBrokerConformance /Users/clyu/workspace/eventing-rabbitmq/test/conformance/...
{"level":"info","ts":1642430963.129856,"logger":"fallback","caller":"injection/injection.go:61","msg":"Starting informers..."}
level All, state Any, feature

=== RUN   TestBrokerConformance
2022/01/17 14:49:24 Using base gcr.io/distroless/static:nonroot for knative.dev/reconciler-test/cmd/eventshub
2022/01/17 14:49:26 Building knative.dev/reconciler-test/cmd/eventshub for linux/amd64
2022/01/17 14:49:30 Loading kind.local/eventshub:7f87812e19d9044cf261237a73736c08b5d8a2b297018aa77d5250786042f734
Error: failed to publish images: error publishing ko://knative.dev/reconciler-test/cmd/eventshub: no nodes found for cluster "kind"
2022/01/17 14:49:30 error during command execution:failed to publish images: error publishing ko://knative.dev/reconciler-test/cmd/eventshub: no nodes found for cluster "kind"
error attempting to ko publish: exit status 1
--- FAIL: TestBrokerConformance (7.73s)
panic: exit status 1 [recovered]
	panic: exit status 1

I do have a local kind cluster created and targeted. Is there some other setup that I missed?

How is your local cluster called? If it is not called kind try settting the KIND_CLUSTER_NAME VARIABLE to the cluster's name

@gabo1208 Yes my kind cluster is called kind. I set KIND_CLUSTER_NAME_VARIABLE to kind just in case, but it's the same failure.

@gabo1208 Yes my kind cluster is called kind. I set KIND_CLUSTER_NAME_VARIABLE to kind just in case, but it's the same failure.

No, he meant KIND_CLUSTER_NAME. An unfortunate choice in the Makefile is that it sets that variable if it's not set, so rather than defaulting to kind it defaults to eventing-rabbitmq-e2e.

@benmoss I can run conformance tests and e2e tests locally now and they are all passing after running necessary make commands. What should we do with this PR? Would it be fine to merge it now or should we wait til this is fixed: https://github.com/knative-sandbox/eventing-rabbitmq/pull/577

I'd ask @gabo1208

/approve
/lgtm


How to set up Typescript in Lambda function

Amplify CLI Version
10.5.1
Question
I'm trying to set up a Typescript lambda function by following these instructions https://docs.amplify.aws/cli/function/build-options/, but keep getting errors. As alternatives, I looked at issues 9113, 8668, 6398, 659, and 6414, all of which is rather confusing and appears to boil down to the instructions being wrong.
My folder structure is
     .gitignore
     tsconfig.json
     /src
        package.json
     /ts
        index.ts
        event.json

.gitignore
/src/*
tsconfig.json
{     "compilerOptions": {         "allowSyntheticDefaultImports": true,         "esModuleInterop": true,         "lib": [             "dom",             "esnext"         ],         "module": "commonjs",         "moduleResolution": "node",         "noUnusedLocals": true,         "noUnusedParameters": true,         "skipLibCheck": true,         "resolveJsonModule": true,         "typeRoots": [             "./src/node_modules/@types"         ],         "outDir": "./src",         "baseUrl": "./",         "rootDir": "./ts",         "paths": {             "src": [                 "./ts"             ]         }     } }
package.json
{   "name": "econapploadindustrialproduction",   "version": "2.0.0",   "description": "Lambda function generated by Amplify",   "main": "index.js",   "license": "Apache-2.0",   "devDependencies": {     "@types/aws-lambda": "^8.10.92",     "typescript": "^4.9.3"   },   "dependencies": {     "csv-parse": "^5.3.3"   } }
index.ts
`import type { APIGatewayProxyHandler } from 'aws-lambda';
import { version } from 'node:process'
export const handler: APIGatewayProxyHandler = async (event, _context) => {
console.log(EVENT: ${JSON.stringify(event)});
console.log(NodeJS Version: ${version});
return {
    statusCode: 200,
    //  Uncomment below to enable CORS requests
    //  headers: {
    //      "Access-Control-Allow-Origin": "*",
    //      "Access-Control-Allow-Headers": "*"
    //  },
    body: JSON.stringify('Hello from Lambda!!!'),
};

};`
I added "amplify:econappLoadIndustrialProduction": "cd amplify/backend/function/econappLoadIndustrialProduction && tsc -p ./tsconfig.json" to the project package.json (I left out the trailing cd - as it causes an error).
Upon amplify push, I get these errors:

ts/index.ts(8,45): error TS2307: Cannot find module 'aws-lambda' or its corresponding type declarations.
ts/index.ts(10,25): error TS2307: Cannot find module 'node:process' or its corresponding type declarations.

So is the documentation wrong? If so, what is the recommended way because the above-mentioned discussions are all over the place. I'm not familiar with CDK; ought I be using that instead?
Secondly, what is the recommended way to import API.ts and the graphql functions from the project folder into the lambda folder?
Any help is very much appreciated.

Hey @klaeuiM :wave: thanks for raising this! Do you have the corresponding @types/node and @types/aws-lambda packages installed? If so, it is possible the types are not found as node_modules are installed in the defined outdir (src). Can you try manually pointing types to src/node_modules/?

So is the documentation wrong? If so, what is the recommended way because the above-mentioned discussions are all over the place. I'm not familiar with CDK; ought I be using that instead?

I do think the documentation here is confusing, however the TypeScript support for functions can definitely be improved.

Secondly, what is the recommended way to import API.ts and the graphql functions from the project folder into the lambda folder?

This experience can also be improved. In the meantime you can use a command hook to manually copy these files to your funciton's directory after they are updated.
For what it's worth when creating functions with Amplify everything in the src directory will be zipped and that archive is placed in dist. What is needed for the function to run should be accessible from within src. It is possible to write functions elsewhere in the project and output the bundle to amplify/backend/function/<function-name>/src, or also manually copy the package.json and lockfile if you need external dependencies.

Thanks! I was missing the node types. Regarding aws-lambda, this works:
import type { APIGatewayProxyHandler } from '../src/node_modules/@types/aws-lambda';
but this does not:
import type { APIGatewayProxyHandler } from 'aws-lambda';

Ah @klaeuiM I believe what is happening is the function's build command is running after the CLI installs production dependencies, which is why those are missing on push and the build. As a workaround, can you remove the npm script in favor of using a pre-push.sh command hook to build your TypeScript function?

Yes, and I've added this issue to our "Function build redesign" project board to track alongside our work to improve the function category and subsequently TypeScript support. Instead of the npm script were you able to execute the build with a pre-push hook?
"amplify:econappLoadIndustrialProduction": "cd amplify/backend/function/econappLoadIndustrialProduction && tsc -p ./tsconfig.json"

I have not used hooks before and I use Windows; I get a "Hooks runtime not found: Bash" error message.
But this misses the point that in this setup with parallel directories the imports cannot access the function node_modules. To address that I successfully made these changes:

moved all files from the /ts folder to the /src folder and eliminated the /ts folder
moved tsconfig.json into the src folder
changed the .gitignore file to:

/src/*.js /src/node_modules/*

changed tsconfig.json to (ie, removed outDir, baseUrl, rootDir, paths; added exclude):

{     "compilerOptions": {         "allowSyntheticDefaultImports": true,         "esModuleInterop": true,         "lib": [             "dom",             "esnext"         ],         "module": "commonjs",         "moduleResolution": "node",         "noUnusedLocals": true,         "noUnusedParameters": true,         "skipLibCheck": true,         "resolveJsonModule": true,     },     "exclude": [         "src/node_modules",         "src/**/*.spec.ts"     ] }

changed the script in the project package.json to (ie, pointed it to the src directory):

"amplify:econappLoadIndustrialProduction": "cd amplify/backend/function/econappLoadIndustrialProduction/src && tsc -p ./tsconfig.json"
This setup may have the added advantage that something like the following actually works (whether that's a good idea I don't know yet, but probably worth pursuing):
import type * as API from '../../../../../src/API';
The issue with the deleted types I solved by moving them into the production dependencies.
Obviously the src is a jumble of stuff that really does not belong into a src folder, but that was already the base case--just adding to it.

Unrelated to that, do you happen to know how to get amplify mock function to use a node version other than v14.18.1? I have v18.12.1 installed on my computer and the cloudformation template for the function is set to runtime nodejs18.x

Hey @klaeuiM

Unrelated to that, do you happen to know how to get amplify mock function to use a node version other than v14.18.1? I have v18.12.1 installed on my computer and the cloudformation template for the function is set to runtime nodejs18.x

This behavior is currently documented as a feature request https://github.com/aws-amplify/amplify-cli/issues/10940, where the CLI is using the version of Node it is built with rather than the Node executable found on your system.
Glad to hear you found a suitable workaround!

Thanks! I appreciate the help


Unclear behaviour on vmid_bits detection in Bare translation mode

Quote the spec, section 8.2.10 on page 109, regarding hgatp. hgatp must be all zeros in Bare translation.

When MODE=Bare, guest physical addresses are equal to supervisor physical addresses, and there is no further memory protection for a guest virtual machine beyond the physical memory protection scheme described in Section 3.7. In this case, the remaining fields in hgatp must be set to zeros.

and page 110, about the vmid_bits detection process, indicating that this detection can only be done in non-Bare modes since we need to csrw hgatp and read it back.

The number of VMID bits is unspecified and may be zero. The number of implemented VMID bits, termed VMIDLEN, may be determined by writing one to every bit position in the VMID field, then reading back the value in hgatp to see which bit positions in the VMID field hold a one. The least-significant bits of VMID are implemented first: that is, if VMIDLEN > 0, VMID[VMIDLEN- 1:0] is writable. The maximal value of VMIDLEN, termed VMIDMAX, is 7 for Sv32x4 or 14 for Sv39x4, Sv48x4, and Sv57x4.

However, spike/qemu allow for Bare-mode vmid bits detection and KVM relies on that. In particular, a new hart boots and kvm detects vmid bits when the old hgatp is ZERO(Bare). Thus KVM works with spike/qemu yet violates the spec book.
We want to clarify the intended behaviours of vmid_bits detection in Bare translation mode. If hgatp is zero and we detect vmid bits, should the CPU raise an exception or disregard the write (remain 0) or return the actual vmid bits (spike/qemu way)?

There is also this statement in the spec:

If hgatp.MODE is changed for a given VMID, an HFENCE.GVMA with rs1=x0 (and rs2 set to either x0 or the VMID) must be executed to order subsequent guest translations with the MODE change -- even if the old MODE or new MODE is Bare.

Which implies that VMID is significant even for MODE=Bare.
[Also @mingyuan-xia you should use a permalink when linking to a specific line of code.]

Yeah, the TLB flush is standard and the implication is valid. Yet, still feel that the three quotes are related but a bit complicated.
Would it be better to clarify that bare-mode hgatp must be zero when the translation is on after the TLB flush. Or, VMIDLEN detection can be done in any mode.
Permalink replaced, thx.


Inspect hovered node while dragging

Allow to edit in the inspector the hovered node while dragging other node(s) over it for 1 second in the editor scene tree dock.
This is to avoid having to rely on the workaround and add the missing piece mentioned here : https://github.com/godotengine/godot/pull/89406
It also propagate the notification to the inspector dock to highlight the valid properties for the drop

Just passing through a node will change the inspector will modify the inspector to edit this node after a few seconds
https://github.com/godotengine/godot/assets/66184050/36819ef2-02d4-4526-bd8b-e6b6d93475fe
Moreover I'm wondering why just modify the inspector and not directly select the node in the SceneTreeEditor?  this would give better visibility on which node the inspector is and would be a more local solution (don't need a new include)

Moreover I'm wondering why just modify the inspector and not directly select the node in the SceneTreeEditor? this would give better visibility on which node the inspector is and would be a more local solution (don't need a new include)

Well, what you have selected are the nodes you want to drag already. And the target node that you hover already have the accent color as border, I just have to make sure to restart the timer if . Actually selecting them would make the them fully colored which would be more confusing I feel like.

Thanks!


Update ErrorReporting API suffix from api to client

The build failed because the gem yard-doctest has a new release today that changes how those document tests are run. If we can't fix the tests to work with the new release today we will pin the dependency to the previous version so we can unblock this PR.
Sorry for the bad timing.

@blowmage Can you please directly merge this PR when you're done with that?

@swcloud I'm working on the fix right now, and will merge this PR ASAP (as soon as we get green on circle ci).

When the build passes for this PR I will manually rebuild the master docs.

Actually, the master branch docs are rebuilt automatically.
The updated docs from this PR and its predecessor #1192 can be seen here:
master/google/cloud/errorreporting/v1beta1
master/google/cloud/monitoring/v3


Add From Vec for BytesMut

This impl exists for Bytes but not BytesMut, you have to use a &[u8] which calls to_vec again when it could just use the original vec.

I think it's intentional that From<Vec<u8>> has not been provided.
https://github.com/tokio-rs/bytes/blob/7daa7fe05364f347539a35d182dc964b9e8e2ecc/src/bytes_mut.rs#L735-L742

Right okay. There's a From<&[u8]> impl, that already uses that method though, but does an extra allocation, how would a From<Vec<u8>> be more expensive than that? Feel free to close this if it's not wanted.

@taiki-e If I understand it correctly, you don't want to enable From<Vec<u8>>, because although it is fast now, it may become silently slow in the future. But by doing this you anyway force people to use the slow variant From<&[u8]>, just sooner than it's required (maybe the internal representation won't even change).
Couldn't this be handled with a deprecation warning instead, if such internal representation change occurs in the future? In that way we could get a fast solution now and a warning if it slows down in the future. I'm asking because we assumed that Vec<u8> -> BytesMut is cheap in our codebase, so it would be nice to have this method as long as it is possible.

Sorry for the late response.

how would a From<Vec<u8>> be more expensive than that?

For example, if we add From<Vec<u8>> in the current implementation, the following two are equivalent:
BytesMut::from(slice.to_vec());
BytesMut::from(&slice);

However, if the implementation of BytesMut is changed, From<Vec<u8>> may be equivalent to From<&[u8]>.
As a result, the first line becomes equivalent to BytesMut::from(&slice.to_vec()), which is inefficient (to_vec called twice).

Couldn't this be handled with a deprecation warning instead, if such internal representation change occurs in the future? In that way we could get a fast solution now and a warning if it slows down in the future. I'm asking because we assumed that Vec<u8> -> BytesMut is cheap in our codebase, so it would be nice to have this method as long as it is possible.

Unfortunately, deprecation doesn't work with trait impl and its items: playground

There could be a special method from_vec outside any From trait impl, which could be easily deprecated. But I guess that you don't want that either?

@Kobzol Even if it's deprecatable, I don't think it's preferable to add a new API that is known likely to be deprecated in the future.
(Unless it makes available functionality that is not currently available. In this case, Vec to MytesMut conversion is already available via From<&[u8]>.)

Well it would enable a faster version of this functionality for now, and would also preserve backwards compatibility with users that were already assuming that this fast conversion exists. But I understand if you don't think that's worth it.


Add sourcemaps & emulator debugging support

Generate sourcemaps so the debugger can find the .ts files
Enable --inspect-functions so

Caveat

Debugger disconnects when saving files (because everything recompiles & emulators seem to restart).
I didn't test this yet, I just added the flags where it made sense (adding them works in a real project though)
I wrote no documentation for this for now

This PR looks good, thanks for the contribution.
I would like to propose that further additions are needed before we could release this feature:

e2e tests should verify that build output does indeed generate *.js.map files in dist
Since this feature changes the project.json schema, we should update the plugin migration tool to add these changes to existing plugin users workspace firebase projects.
Discuss if map files should be deployed or ignored

If they are deployed, we'd need to document how plugin users can use them such as described here
If not, we'd need to add ignore rules to function configs for *.map files

As you already mentioned, we should also document these new enhancements.

I'm going to hold this PR here for now, while I plan out what is needed in the next release, and if this feature can be included with all of the above.

I have no clue how to add the remaining stuff like e2e tests and schema migrations

Has this been merged ? I am trying to debug functions with no success

I've moved tests around so I'll resolve the conflict/merge from master.

@ciriousjoker I would like to merge your PR, but because it is merging commits directly to main I cannot accept it.
If you could please sync your fork with the latest from my repo, then re-create your changes on a separate PR branch on your fork and re-submit the PR I'll merge it, and you will keep the contribution credit for this change.
Thanks

@simondotm there you go


bootstrap-buttons ignores data-loading-text

No matter what you specify in 'data-loading-text' on your 'button' tag, the JS always uses the default "loading...".
I believe the error is located at line 32:
$el.html( data[state] || $.fn.button.defaults[state] )
should be something like
$el.html( $el.data(state) || $.fn.button.defaults[state] )
$el.data()['something'] does not behave the same as $el.data('something')

I'm using the data-loading-text on a site right now, and it is working as expected.  Can you provide a jsfiddle with your issue?

http://jsfiddle.net/W4CUT/
The button should say "Test Message..." and not "loading..."

@matthewbjones you forgot "=" http://jsfiddle.net/W4CUT/1/

Haha, my bad. Here is an updated version that does not work.
http://jsfiddle.net/W4CUT/2/
Looks like my Rails project is using jQuery v1.4.4, which appears to be not compatible with the current code for the buttons JS. My code fix makes it work in v1.4.4.

Yep, you need to use a newer version of jquery.


Remove implicit availability of Foundation from future manifest versions

This changes all imports of Foundation in the PackageDescription module to be implementation-only, making it so that it needs to be explicitly imported if being used. To avoid breaking existing packages, we inject an explicit import into manifests with tools-version 5.7 or earlier. In the next tools-version, Foundation will no longer be implicitly available.
rdar://92879696

@swift-ci please smoke test

/home/build-user/swiftpm/Sources/PackageLoading/ManifestLoader.swift:68:24: error: cannot use class 'DispatchQueue' here; 'Dispatch' has been imported as implementation-only
        delegateQueue: DispatchQueue,

Interesting...

Should a note about this be added to CHANGELOG.md, as it is a relatively significant change?

Should a note about this be added to CHANGELOG.md, as it is a relatively significant change?

+1

@swift-ci please smoke test

[1016/1064] Emitting module PackageLoading
/home/build-user/swiftpm/Sources/PackageLoading/ManifestLoader.swift:68:24: error: cannot use class 'DispatchQueue' here; 'Dispatch' has been imported as implementation-only
        delegateQueue: DispatchQueue,

Not entirely sure why I am not seeing these locally 🤔

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please test package compatibility


None recovering Redis command timed out

Expected behavior
the expected behaviour is that with periodic_refresh, the issue does not persist.
Actual behavior
we have started to use aws redis serveless, since the switch from redis cluster-mode enabled to redis serverless, out of the blue one client from many tasks running starts to have command timed out continuously. Depending on the service and size of objects and if put or get commands are being timed out, we see different side effects, sometimes it results in OOM, sometimes only increased latency.
Note that in the services this happens, usually there are more than 12 tasks running, and only one container has this issue.
I could correlate any CPU spike with the event causing the timeouts.
Steps to reproduce
this is reoccurring in production env in different services, but I don't know how this can be reproduced.
Versions and Config
<lettuce.version>6.3.2.RELEASE</lettuce.version>
<netty.version>4.1.109.Final</netty.version>
related configurations:
ssl: true
timeout: 5s
connect-timeout: 500ms
additional:
dns-ttl: 5s
periodic-refresh: 10s
reconnect-delay-min: 100ms
reconnect-delay-max: 5s
read-from: replicaPreferred
Possible related issues
RedisCommandTimeoutException intermittently:
in some cases this could be related, as we sometimes see timeouts for a minute, and they are recovered, however in this case it persists.
Lettuce cannot recover from connection problems:
maybe setting TCP_USER_TIMEOUT would help, default is 1 minutes, so for the recovering case, maybe this helps, but for the cases that this continues and gets stacked probably not.

This is a Lucette question / issue

This is a lettuce question / issue

no this is a bug, what do I need to provide ?


Pop!_OS 22.04 is not supported

When I test
distribution=$(. /etc/os-release;echo $ID$VERSION_ID) && curl -s -L https://nvidia.github.io/libnvidia-container/$distribution/libnvidia-container.list,
(knowing that $distribution is here pop22.04)
It return always
# Unsupported distribution!
# Check https://nvidia.github.io/libnvidia-container.
So I have to manually specify this variable distribution to ubuntu22.04 for it to work

Yes, pop22.04 is not an officially supported distribution in that we don't qualify it as part of our release process. With that said, the ubuntu18.04 packages are generally forward-compatible on all newer ubuntu-based distributions. Here the key is that the the glibc version available on the platform should be at least that used to build the libnvidia-container* packages for the system.


fix: add missing types files in build

What kind of change does this PR introduce (bug fix, feature, docs update, ...)?
Fix build by adding missing files.
What is the current behaviour (you can also link to an open issue here)?
Projects using this package may not build correctly because of missing files.
What is the new behaviour (if this is a feature change)?
They should build correctly
Closes #26

To sum it up here as well:

https://github.com/dethcrypto/TypeChain/issues/430

Upgrading TypeChain to v6 solves the issue.


Expecting value: line 1 column 1 (char 0) [-] Unable to find stream url.

as of today I got this error output a few times. Restarted my pc and same thing happened. Worked on a few tiktok users but most got this respone.  Tried with and without ffmpeg

Check out the new release
https://github.com/Michele0303/TikTok-Live-Recorder/releases/tag/3.7


Find a way to copy docker-compose-prod.yml using github actions

There will be no need to touch it anymore I think.


Is there a limit to the number of particle colors?

I am using 5 colors on one of my projects:
"color": {
    "value": [
        "#FF6961",
        "#FFD300",
        "#90EE90",
        "#4DC9FF",
        "#C311E7"
    ]
},

I was wondering if there is a limit to the number of colors that could be specified?
Further, do more colors require more computation/processing power?

Hi @adamalston,
There’s no limit on particles colors array length, the color will be picked randomically from 0 to length-1 when the particle is created so a longer array has the same performance of a shorter one.
If you have a performance drop let us know, I’ll inspect it deeply

Thanks for the clarifications.
The only performance issues I am running into seem to be rooted in Chrome. I don't believe the particles are responsible for the performance drop however since the site runs fine on every other browser. Also, this article from the WSJ detailed how unoptimized Chrome is in terms of memory management.

@matteobruni Another question. Is there a list somewhere of every option that can be set?
I am trying to set a minimum size for the particles. I have looked at tsParticles and I cannot get any of these objects to work for minimum size.
Here is the current size object that I have:
        "size": {
            "value": 4,
            "random": true,
            "anim": {
                "enable": false,
                "speed": 30,
                "size_min": 2,
                "sync": true
            }
        },

You can see https://particles.js.org (I'm working on that site to add more documentation as possible, and samples) that is the website containing all the objects used in the tsParticles project.
Actually there are two minimum size, one for random and one for animation.
You can set it like this
        "size": {
            "value": 4,
            "random": {
                "enable": true,
                "minimumValue": 2
            },
            "animation": {
                "enable": false,
                "speed": 30,
                "minimumValue": 2,
                "sync": true
            }
        },

Works now, thanks!


Adding missing package_data entries

This was missed during initial migration

For posterity, I sped this up significantly by using the following command to help me find all instances of package_data in the former command_module structure:
 git diff azure-cli-2.0.67 upstream/dev -- **setup.py | grep package_data


Give clown overall and security playtime requirements

About the PR
Clown now requires 30 hours of overall playtime and 10 hours of security playtime.
Why / Balance
Too many clowns just slip everyone non-stop and laugh all alone while the entire crew hates them. Most of the time they also cause problems to security and are in general a huge nuisance.
If you're the only one laughing you've failed as a clown, this pr's purpose is to give them some time on the receiving end of unfunny jokes.
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes
Changelog
:cl:

tweak: Clown now requires security playtime to make them understand how much of a pain slipping everyone nonstop is.

i'm not that type of clown but not based, too much time to wait

A new player interested in Clown won't care to play Security Cadet properly just to get to it.

based tbh

not enough, make the clown more difficult to unlock then the captain /j

this actually kind of makes sense

Alternatively we could also nerf slipping, like making thrown items not slip people anymore. I mean those objects are in the air how are they ending up beneath peoples feets?
If someone wishes to try and understand, what are they affecting when slipping an officer who is clearly chasing someone, they could do that on their first round of the game; if they don't, then even a playtimer of 1000h won't resolve the issue.
Is a 10h sec playtimer funny? Kind of, it's ironic that you need sec playtime to play someone who is considered to be sec's nemesis.

if they can’t grief as a clown they’ll grief as a passenger

Service roles intentionally have no role timers to allow new players to easily access low-stakes roleplay roles. Furthermore, clown doesn't have any kind of complex knowledge that justifies needing security playtime, like det or warden. As such, I'm opting to close this PR.

clown mains stay winning 💪


CORS issues for static / media files behind proxy

While investigating issues related to https://github.com/inventree/InvenTree/pull/6399 I stumbled across an existing issue which may need addressing.
When serving media and static files behind a proxy (e.g. Caddy as per our docker setup), and requesting from a different host (i.e. a CORS request) the files are not served - due to failed CORS checks.
The /api/ requests are honoured - these are handled by django and our configured CORS whitelist / etc.
However the /static/ and /media/ endpoints do not observe these allowed CORS hosts:
    handle_path /static/* {
        root * /var/www/static
        file_server
    }

    handle_path /media/* {
        forward_auth {$INVENTREE_SERVER:"http://inventree-server:8000"} {
            uri /auth/
        }
        root * /var/www/media
        file_server
    }

To demonstrate this, spool up the local vite server and point to the demo server: https://demo.inventree.org:

@matmair @wolflu05 any idea how to tackle this? https://github.com/inventree/InvenTree/pull/6662 fixes the issue with static files in development mode, but not behind the proxy.
Ideally the best solution here would be to forward the cors headers from our server, based on the configured CORS whitelist values. Not sure if that is possible using Caddy?
Second idea might be to adjust the caddy configuration file itself, to explicitly set which origins are valid? Again, not sure if this is possible and it has the disadvantage of requiring double input of data. Ideally, would like it all to run from our existing config file or env variables.

Some useful references:

https://kalnytskyi.com/posts/setup-cors-caddy-2/
https://gist.github.com/ryanburnette/d13575c9ced201e73f8169d3a793c1a3
https://enable-cors.org/server_caddy2.html

Not sure we can use config.yaml, env should work


Consider renaming centroid-0/1 to x/y

especially for graph exports

Won't fix for consistency with regionprops


it should be possible to remove config without a successful deploy

Right now it is impossible to remove config values if the build fails.

We can't update environment variable within a running container or process, so we do in fact have to restart new containers in order to update the environment variables exposed to running containers.
Doing so requires successfully re-deploying the app, but note that it does not require re-building the app image (in this regard the title of the issue and your comment mean different things — feel free to clarify as to which one you meant).
Did you mean to say that you'd like to be able to remove a variable from an app configuration without even exposing the updated value to containers? I'm not sure that would be a feature we'd want to support: obviously, app containers are the primary consumers of app configurations, so it could be quite confusing if we allowed updating the configuration without deploying it to app containers (but on the other hand... we have a few environment variables that we accept in app config but expose somewhere else, like the Nginx parameters, or the private Docker image ones, so I could see how it might be useful).
Did you want to expand a little bit on your use case here? It's a little hard to provide a better answer in the abstract / without an understanding of what you're trying to do. Thanks!

The private docker environment variables you set cannot be removed if you having a failing build. That was my specific use case the other night.

Thanks; this is helpful.

Closing this, this is possible now: https://www.aptible.com/documentation/enclave/reference/apps/configuration/synchronized-deploys.html


Cannot read property 'length' of null on Ionic 3.7.1

Still worked, But error show up on startup.

@angular version 4.4.3
@ionic-angular 3.7.1
ionic2-super-tabs 4.1.3
> ionic info

cli packages: (D:\path\to\project\node_modules)

    @ionic/cli-utils  : 1.13.1
    ionic (Ionic CLI) : 3.13.2

global packages:

    cordova (Cordova CLI) : 7.1.0

local packages:

    @ionic/app-scripts : 3.0.0
    Cordova Platforms  : android 6.2.3
    Ionic Framework    : ionic-angular 3.7.1

System:

    Android SDK Tools : 25.2.5
    Node              : v6.11.3
    npm               : 3.10.10
    OS                : Windows 10

Misc:

    backend : legacy

I didn't try on Production build yet.

@ihadeed can you take a look at this issue?

@ihadeed can you please take a look, it's super annoying.
Thank you.

Has anyone got a fix for this?? @ihadeed

This guy is busy for now?

Sorry for the delay.
What versions are you guys using?
I just tested with latest Ionic version & Ionic super tabs and it seem to be working fine.

@ihadeed It's been happening in all versions starting with 3.7.1.
I'm upgrading to 3.9.2 will report back if it happens again.

@ihadeed yup, issue still there. Also tabs not working correctly.

Thanks, I'll try to reproduce this issue.
I wasn't getting it when running the example project.

Also getting this same issue with 4.1.5. Works after downgrading to 4.1.4:
localhost:marit-mtg-ionic lb3$ ionic info

cli packages: (/Users/lb3/projects/maritlabs/marit-mtg-ionic/node_modules)

    @ionic/cli-utils  : 1.19.0
    ionic (Ionic CLI) : 3.19.0

global packages:

    cordova (Cordova CLI) : 7.1.0

local packages:

    @ionic/app-scripts : 3.1.2
    Cordova Platforms  : android 6.4.0 ios 4.5.4
    Ionic Framework    : ionic-angular 3.9.2

System:

    ios-deploy : 1.9.2
    ios-sim    : 5.0.8
    Node       : v9.0.0
    npm        : 2.15.12
    OS         : macOS Sierra
    Xcode      : Xcode 9.2 Build version 9C40b

Environment Variables:

    ANDROID_HOME : not set

Misc:

    backend : legacy