[Snyk] Upgrade @spectrum-web-components/field-label from 0.40.5 to 0.41.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @spectrum-web-components/field-label from 0.40.5 to 0.41.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 23 days ago, on 2024-02-13.

Release notes

Package name: @spectrum-web-components/field-label

0.41.0 - 2024-02-13v0.41.0

0.40.5 - 2024-02-05v0.40.5

    from @spectrum-web-components/field-label GitHub release notes

Commit messages

Package name: @spectrum-web-components/field-label

0bf38fd chore: release new versions #publish
40701ac docs: move Menu Item out of mobile critical path loading
782560d fix(slider): high contrast improvements for filled track (#3952)
485a67c fix: support generating random IDs outside of secure contexts
124dd0d ci: expand lighthouse usage and reporting (#4027)
29866b4 test: leverage latest playwright (#4029)
0b80d7b test(coachmark): use locally cachable 64bit encoded images to ensure availability at VRT time (#4028)
4f9aa4a fix(tray): only allow "click" events when they "pointerdown"ed on the Underlay (#4020)
a94389c feat(coachmark): rename "sp-coachmark" to "sp-coachmark-indicator", add "sp-coachmark" (#3639)
80d2228 ci: add lighthouse benchmark in Github Actions (#3708)
4ff403e fix(popover): correct tip delivery size (#4018)
b49862f chore: bump @ spectrum-css/quickaction from 3.1.0 to 3.1.1
5cf1dec chore: bump cssnano from 5.1.14 to 6.0.3
01610c6 ci: update golden images cache
a11ef6b feat(icon): use core tokens
0b79d67 chore: bump pretty-quick from 3.1.3 to 3.3.1
c5e533f chore: bump @ spectrum-css/slider from 4.3.0 to 4.3.1
026a9c6 chore: bump @ types/prismjs from 1.26.0 to 1.26.3
b69b972 chore: use latest floating-ui and remove local plug-in work (#4012)
c78de32 docs: place demos at the top of each docs page (#3957)
a55342f docs(overlay): expand API coverage and demos (#3971)
3dc5b1f perf(combobox): prevent initial list render and update tests to prove that reduces render time

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Updated dependency manually


multisig addr based on the same repeated pubkey

If i have the multisig account created based on the repepated the same public key, so the coinbin signs the transaction as many times as the pubkey was used, however for funds release less signatures could be required and the transaction will not be accepted by the network.
Example: I have the 3/5 multisig address created on 5 times repeated public key Q (with the private key x to it). For funds release only 3 signatures are required (as it is 3/5 multisig account). While signing with your coinbin tool, it adds 5 signatures to the transactions (as founds 5 related public keys), and finally creates 5/5 multisig transaaction (signed 5 times). But network does not accept such transaction because only 3 signatures are required.
Can you fix it? (for example, add the choice for signature quantity if there are repeated public keys in multisig account).

Hi,
Can you share the redeem script and I'll look into this. If you dont want to make it public, please message or email me.
Thanks


docker integration

docker compose file addition for the application

please link the relevant github-issue to the PR description.

Overall looks good.
Just 2 pointers.

Can you add HMR support in the docker for the frontend and backend apps ? That would really help during development.
Add a new section for app setup using docker instructions in the readme.md file

yes sure

@aadeshkulkarni added the two points


Error installing shelly plugin after updating matterbridge to 1.5.4

Hi, last night I have seen the yellow label to update matterbridge to 1.5.4 and shelly plugin to 0.9.5.

Hi,
is a well known issue with npm that sometime comes out.
Maybe updating node and npm on the host machine can also help.
See https://github.com/Luligu/matterbridge/issues/100


feat: add ability to localize common characters

I had some trouble figuring out how best to integrate this, so definitely interested in feedback and other ideas.
The big downside to this approach is that every component that wires up to a localizer via the LocalizeMixin is going to have these "common" terms merged into their collection. That's why I needed to use the intl-common prefix on all their keys to avoid a potential collission.
~It also means that the common terms will always be fetched once on every page, even if they're not used. Both localize and localizeHTML are synchronous, so I couldn't think of a way to defer the loading of the common stuff.~ That's no longer true now that loadCommon: true must be set in the config.

The big downside to this approach is that every component that wires up to a localizer via the LocalizeMixin is going to have these "common" terms merged into their collection. That's why I needed to use the intl-common prefix on all their keys to avoid a potential collission.

If more than one collection is fetched, does that mean they are effectively multiple copied of it in memory? It's probably not going to be a huge set, but doesn't seem ideal. Maybe there is a way to share one set? Or, maybe there could be a way for those components to indicate whether to include the common terms in the set? I'm not too familiar with how the terms are fetched, so maybe none of those things are possible.

It also means that the common terms will always be fetched once on every page, even if they're not used. Both localize and localizeHTML are synchronous, so I couldn't think of a way to defer the loading of the common stuff.

I think async localize could potentially complicate things quite a bit for consumers.

If more than one collection is fetched, does that mean they are effectively multiple copies of it in memory?

I think that might be true currently, but we should be able to shift things around a bit to avoid that. The set might actually grow quite a bit so we should be sure about that.
Otherwise this all looks really good to me.


What about if the real cardinality return by db is zero?

How would CEB handle this?

In general, we treat 0 as 1 in evaluation (when evaluating q-error, or plan-error) / and also when training neural nets / generating features etc.

Understood, Thanks~


Support recyclable permebufs

Dynamically allocation messages and remapping them in the destination's address space is slow. We could speed up rpc performance by utilizing shared memory.
I'm thinking: opening a channel between two processes, and send messages back and forth via recyclable shared buffers.
(This would be different to a future streaming interface where we could fire-and-forget messages in a circular buffer. Instead this would still wait for a response.)
One idea is that when you have a channel between two processes, you could grab a buffer from a channel, and it would be a pool of shared memories. The request would be written to the beginning, the message would be sent to the receiver, which would write the response to the same shares buffer, and then send a ping back.
I also thought about using separate sending and receiving buffers but I'm leaning against it because the original sender would have to signal back to the receiver that it was done with the response buffer.
Technically, we could do this without channels. Each pair of {sender, receiver} could have a set of shared buffers, which would be more efficient memory wise, but there wouldn't be a way to "close" the channel between two processes. Perhaps we could have a "clean up" method to deallocate all channels between two processes.


File name containing special characters(including Chinese characters) got garbled when sending text to terminal

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
Version: 1.73.0 (user setup)
Commit: 8fa188b2b301d36553cbc9ce1b0a146ccb93351f
Date: 2022-11-01T15:34:06.111Z
Electron: 19.0.17
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: No

OS Version:
Win11

Steps to Reproduce:
My .py file named ② 必须第一次就运行 PkgHelper.py，when running it with  VS Code, I saw the name cannot be recognized correctly , it becomes garbled like the following :
PS F:\BaiduNetdiskDownload\SoftwareProject\LYYDownloader-dev> & C:/Users/22815/AppData/Local/Programs/Python/Python39/python.exe "f:/BaiduNetdiskDownload/SoftwareProject/LYYDownloader-dev/ 必须第一次就运行PkgHelper.py"
C:\Users\22815\AppData\Local\Programs\Python\Python39\python.exe: can't open file 'f:\BaiduNetdiskDownload\SoftwareProject\LYYDownloader-dev\鎵撳
寘\ 蹇呴』绗竴娆″氨杩愯PkgHelper.py': [Errno 2] No such file or directory

Please install the pre-release version of the extension:

And provide the logs as mentioned in the issue template, after attempting to run the file.

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

The same to the pre-release version.
No output since [Errno 2] No such file or directory

It was not supposed to fix the issue, but I would need the full Python logs asked here before we can proceed.

It was not supposed to fix the issue, but I would need the full Python logs #20168 (comment) asked here before we can proceed.

Sorry! I didn't pay much attentive to your instruction before,
I run it two times , the output is :
Experiment 'pythonSurveyNotificationcf' is active
LSP Notebooks experiment is enabled
LSP Notebooks interactive window support is enabled
Python interpreter path: ~\AppData\Local\Programs\Python\Python39\python.exe
Starting Pylance language server.
Send text to terminal: f:
Send text to terminal: cd f:/BaiduNetdiskDownload/SoftwareProject/LYYDownloader-dev/打包
Send text to terminal: & C:/Users/22815/AppData/Local/Programs/Python/Python39/python.exe "f:/BaiduNetdiskDownload/SoftwareProject/LYYDownloader-dev/打包/② 必须第一次就运行PkgHelper.py"
Send text to terminal: f:
Send text to terminal: cd f:/BaiduNetdiskDownload/SoftwareProject/LYYDownloader-dev/打包
Send text to terminal: & C:/Users/22815/AppData/Local/Programs/Python/Python39/python.exe "f:/BaiduNetdiskDownload/SoftwareProject/LYYDownloader-dev/打包/② 必须第一次就运行PkgHelper.py"

Thank you. As you can see in the logs the extension sends the correct command to terminal using the Terminal.sendText API, but VSCode itself truncated the actual path. Transferring to VSCode as the issue is on their end.


support middleware

please support middleware and route group

What's route group?

o, like go-chi/chi

Nothing stops you from using chi's router with go-web. You can specify a handler to go-web.

i get it, thank you


Compiler error

Compiler doesn't seem to read html file correctly (Windows 10), see below
svelte compile HelloWorld.html > HelloWorld.js
svelte version 1.22.4
compiling HelloWorld.html...
Expected valid tag name
1: ��< h 1 > H e l l o   { { n a m e } } < / h 1 >
^

Oh, old issue. Sorry


Robot Page follow up

nit: For a follow-up: add an on hover style when you are trying to pick a robot from the robot list. On the following list

Replace current implementation with updated robot endpoints / robot query api

Merged


MLP jobs can raise an error when launched in a multi-threading mode

Details about the quacc environment

quacc version: 0.6.2
Python version: 3.11.7

What is the issue?

config = Config(
    executors=(
        ThreadPoolExecutor(
            max_threads=64,
        ),
    ),
    app_cache=False

With a for loop over jobs will lead to a weird error: "raise NameError("module is not installed as a submodule")".  (torch/fx/_symbolic_trace.py:441)

      for n, atoms in enumerate(atoms_list):
          time.sleep(n*10).  <--- Adding this solve the issue.
          results = mace_relax_job(atoms)
          write_to_db(results)
          all_results.append(results)

I cannot reproduce the issue on all my machines, my M1 does it sometimes while HPC will do it all the time.
How can we easily reproduce the issue?
mace_relax_job = partial(
    relax_job,
    method="mace",
    model="large",
    device="cpu",
    opt_params={"optimizer": SciPyFminBFGS, "fmax": 0.1},
)
@flow
def workflow(atoms_list):

    @subflow
    def relax_atoms_list(atoms_list):
        all_results = []

        for n, atoms in enumerate(atoms_list):
            all_results.append(mace_relax_job(atoms))

        return all_results

    relaxed = relax_atoms_list(atoms_list)

    return relaxed

atoms_list = [molecule("H2O") for i in range(128)]

futures = workflow(atoms_list)

Thanks for the report!
Unsolicited Advice
First, I will note that you can most likely simplify your situation here (I'm not sure how much was abstracted away for the issue report, so maybe this won't be relevant for you). The @subflow decorator is really only necessary if you are launching a dynamic job where the number of jobs is not known a priori. At least here, that value is known (maybe it is not known in practice though). The @flow decorator also doesn't do anything with Parsl, just as a head's up.
The above example could likely be done as follows, like shown in the docs:
from concurrent.futures import as_completed

from ase.build import molecule
from ase.optimize.sciopt import SciPyFminBFGS
from quacc.recipes.mlp.core import relax_job
from tqdm import tqdm

atoms_list = [molecule("H2O") for i in range(128)]
futures = []

for atoms in atoms_list:
    future = relax_job(
        atoms,
        method="mace",
        model="large",
        device="cpu",
        opt_params={"optimizer": SciPyFminBFGS, "fmax": 0.1},
    )
    futures.append(future)

for future in tqdm(as_completed(futures), total=len(futures)):
    task_doc = future.result()
    print(task_doc)

Of course, I don't know the context, so maybe you're already aware and this is irrelevant for you.
The Issue
I am going to make a guess here of what's going on, which could certainly be wrong. In your scenario, you are running in multi-threaded mode where multiple Python processes are being launched on a compute core. Looking at the culprit in pytorch, it seems to be a method that is doing some filesystem crawling. My hunch is that one process on the compute core is changing the current working directory (e.g. in calc_setup or calc_cleanup) in the midst of PyTorch crawling the filesystem in the other, concurrent process (since threads on the same compute core share a common working directory). Unfortunately, at this time, there is no way to remove the os.chdir calls in calc_setup and calc_cleanup because not all ASE calculators currently respect their directory keyword argument, so we have to cd into the necessary directory as a precaution to ensure the calculations are run in the correct place.
If you are running a compute node with, say, 32 physical cores each of which has 2 hardware threads, I would recommend that your quacc calculations run on all 32 physical cores but only one thread each. That is the distinction between physical cores (32) and logical cores (64). This does mean that the ThreadPoolExecutor would potentially not be the executor of choice in this scenario since that executor is meant for multi-threading (e.g. if you set max_threads = 2, it will distribute work over two threads on the same compute core, not two separate compute cores). It would likely be better to figure out how to distribute the work over the physical cores on a node via the HighThroughputExecutor in the context of Parsl.

Thanks for this descriptive answer, the code I have posted is indeed part of a bigger workflow. Also I like to use @subflow because they resolve list of futures automatically. In any case, your example is nice because it reminds me that using @flow is always optional.
I thought about using the HighThroughputExecutor but as you mentioned on the Parsl stack (thanks for asking there btw) I didn't think of using it for multiple Apps on the same node! It seems that it is totally doable and it's probably a much cleaner option.
After having a quick look at the code after the grid_phonon_flow catastrophe I thought that all cd's were removed from quacc (I can see them now), I will think twice before using Threads like a savage.

I thought about using the HighThroughputExecutor but as you mentioned on the Parsl stack (thanks for asking there btw) I didn't think of using it for multiple Apps on the same node! It seems that it is totally doable and it's probably a much cleaner option.

Yup, it should be! In fact, I imagine this is a pretty common use case for both Parsl and Dask users. I haven't done it myself though.

After having a quick look at the code after the grid_phonon_flow catastrophe I thought that all cd's were removed from quacc (I can see them now), I will think twice before using Threads like a savage.

Sadly not! I was able to get rid of all instances of relative file paths causing issues, but I ultimately couldn't remove the cd calls. Too many broken things upstream in ASE at the moment, and not much I can do without involvement from those above me... :(
Threads are definitely a "go at your own risk" approach for now!

Coming back on your suggestions, right now I am writing a workflow which is 3 steps:

Relax base structures
Construct alloys based on them
Relax the alloys

The alloy construct part is nothing fancy, a few numpy operations, although the input depends on a future (relaxed base structure)
What is the recommended best practice in this case?

construct_alloy function should be a @job in the workflow because it takes futures as input and it does a simple operation which do not call other @job.
I should first resolve the futures from the first relax and then send this to a simple non-@job construct_alloy function.

Also, my mental representation is that my whole workflow should be located into a @flow but I don't know if that's necessary really.

This is essentially the same thing as the Running a User-Constructed Dynamic Workflow example in the documentation, which has: 1) relax a base structure; 2) Construct slabs from them; 3) Relax the slabs. So, you can likely refer to that example and the underlying functions for the structure.
There are many ways to achieve this goal, but the most efficient is probably something like this:

Make a @flow. Let's call it alloy_flow here for the sake of clarity. With Parsl, the @flow decorator does not have any function, but we'll include it anyways for full compatibility with other workflow engines.
This alloy_flow will call two functions: a) a relax_job @job function to relax the input structure; b) a @subflow that will generate the alloys and do a relax on each. Parsl will know to resolve Futures automatically if given as inputs, so you can pass in the output["atoms"] of job "a" to the input of "job" b without calling a blocking .result().
The relax_job is fairly self-explanatory. The @subflow coming after will look almost exactly the same as bulk_to_slabs_subflow. In essence, you'll have a function in there that will generate alloys, and then you'll use a for loop over each to call individual relax jobs, and you'll return a list[RunSchema].

construct_alloy function should be a @job in the workflow because it takes futures as input and it does a simple operation which do not call other @job.

You certainly could do this if you chose to. But if you wanted to save a dispatched job, you could pack this into the @subflow, which will automatically resolve the input future for you.

I should first resolve the futures from the first relax and then send this to a simple non-@job construct_alloy function.

In general, it is wise to avoid any blocking calls in the intermediate steps of the workflow to ensure full concurrency is achieved. The above example should make that possible.

Also, my mental representation is that my whole workflow should be located into a @flow but I don't know if that's necessary really.

Recommended but not strictly necessary for Parsl.

Thanks for all the advice, this is actually really helpful. I will probably copy that somewhere since I end up coming back to it a lot 😅


can't use scvi.dataset, etc.

Hi,
I am trying to use scvi, but as long as I use scvi.* (for example, scvi.dataset, scvi.inference, ....), it doesn't work at all. However, if I directly import scvi, it works fine.
from scvi.dataset import CsvDataset
import urllib.request
import os

remote_csv_dataset = scvi.dataset.CsvDataset("chr1_scvae.csv",
                                save_path = "/u/s/s/sshen82/Documents")

Traceback (most recent call last):
File "scvi.py", line 1, in
from scvi.dataset import CsvDataset
File "/afs/cs.wisc.edu/u/s/s/sshen82/Documents/scvi.py", line 1, in
from scvi.dataset import CsvDataset
ModuleNotFoundError: No module named 'scvi.dataset'; 'scvi' is not a package

Can you describe how you installed scvi?

I use "pip install scvi".

This is a bit odd, I just double checked on my end and have no issues on a fresh virtualenv. What version of python do you have? Are you installing in a virtualenv?

Python: 3.7.4
I am not sure what virtualenv is, but I wrote "virtualenv --version" and it responded 15.1.0.

how did you install python? You may need to use pip3?

I tried to install that using pip3 as well, and it doesn't work. I also tried to clone the one in github, but it doesn't work as well...

I believe this is a python configuration issue on your end. It would be helpful if you installed scVI in a virtual environment and reported back if you still have the same issue.

Also, there is a bug in the code snippet you sent. It should be:
from scvi.dataset import CsvDataset
import urllib.request
import os

remote_csv_dataset = CsvDataset("chr1_scvae.csv",
                                save_path = "/u/s/s/sshen82/Documents")


SDK for 26 RFI connectors, and other small fix on some properties

Description

https://github.com/Azure/azure-rest-api-specs/pull/2016
https://github.com/Azure/azure-rest-api-specs/pull/1995
This checklist is used to make sure that common guidelines for a pull request are followed.

[x] Please add REST spec PR link to the SDK PR
[x] I have read the contribution guidelines.
[x] The pull request does not introduce breaking changes.

General Guidelines

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[x] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

@Eva-Xiao resolve merge conflicts

@shahabhijeet conflicts are resolved.


"OS type not recognized" when provisioning a host on Windows 10

An error occurs when running the following command on windows 10:
docker-machine create -d generic --generic-ip-address <ip> --generic-ssh-user <user> --generic-ssh-port <port> <machine-name> (the ip points to a VPS with Ubuntu 16.04 installed with a valid SSH key added to authorized_keys and passwordless sudo)
Output:
Running pre-create checks...
Creating machine...
(<machine-name>) No SSH key specified. Assuming an existing key at the default location.
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available... <--- This takes a long time
Detecting the provisioner...
Error creating machine: Error detecting OS: OS type not recognized

Docker version 1.12.3, build 6b644ec
docker-machine.exe version 0.8.2, build e18a919
This works when I run the same command on MacOS 10.10.5.

turn on debug ( -D)

the same to me,how to deal with?

我也遇到了同样的问题，，，请问您解决了吗？

You can dig into the code and enhance post debug (-D output)

Apparently, docker-machine panics when it can't find a ssh client. Try the solution in #3840

For me it the solution was to follow the setup of hyper-v switch external switch example here

If you're using PowerShell as terminal command on window 10, they might be some problems with ssh command. I switch to GitBash for resolving my pb. Before you need to copy your key to the remote machine with ssh-copy-id {username root}@{remote-host}. I follow this tutoriel as well http://www.kevinkuszyk.com/2016/11/28/connect-your-docker-client-to-a-remote-docker-host/

it's works after i  restart pc

As described in docker troubleshooting documentation, you can try :
Regenerate certificates then restart docker host.
or
Create a new docker-machine
Worked for me.


Investigate and reconcile differences in how different langauges encode URLs and the C SDK

Currently, we only URL encode (using percent encoding) the following characters, which follows RFC 3986 and only leaving unreserved characters un-encoded https://tools.ietf.org/html/rfc3986#section-2.3:
https://github.com/Azure/azure-sdk-for-c/blob/2b649d3d657e13cc8f9afbc8911afc4a93f65cd0/sdk/core/core/src/az_span.c#L695-L707
Other languages behave differently and we should make sure that either we have specific reasons for the discrepancy, OR we try to mimic what other languages do after figuring out what precedent to follow (since there isn't clear consensus).
Things to consider:

What about following the IRI spec, i.e. RFC 3987 - https://tools.ietf.org/html/rfc3987#section-2.2
~Do we want to escape white space (' ') as '%20' or as '+'?~ No

C#: https://dotnetfiddle.net/TH7z7h
using System;
using System.Text.Encodings.Web;

public class Program
{
	public static void Main()
	{
		string query = "Hellö Wörld@Some lang$!*()+;";
		string encodedQuery = UrlEncoder.Default.Encode(query);
		// Hell%C3%B6%20W%C3%B6rld@Some%20lang$!*()%2B;
		Console.WriteLine(encodedQuery);

		// Hell%C3%B6%20W%C3%B6rld%40Some%20lang%24%21%2A%28%29%2B%3B
		Console.WriteLine(Uri.EscapeDataString(query));
	}
}

https://source.dot.net/#System.Text.Encodings.Web/System/Text/Encodings/Web/UrlEncoder.cs,123
https://docs.microsoft.com/en-us/dotnet/api/system.uri.escapedatastring?view=netcore-3.1
https://docs.microsoft.com/en-us/dotnet/api/system.net.webutility.urlencode?view=netcore-3.1#remarks
https://github.com/Azure/azure-sdk-for-net/pull/11657
Golang: https://play.golang.org/p/BMrXEtoFR_K
package main

import (
	"fmt"
	"net/url"
)

func main() {
	query := "Hellö Wörld@Some lang$!*()+;"
	// Hell%C3%B6+W%C3%B6rld%40Some+lang%24%21%2A%28%29%2B%3B
	fmt.Println(url.QueryEscape(query))
}

Java: https://repl.it/repls/VapidMealyKeygens
import java.net.URLEncoder;
import java.nio.charset.StandardCharsets;
import java.io.UnsupportedEncodingException;

class Main {

  // Method to encode a string value using `UTF-8` encoding scheme
    private static String encodeValue(String value) {
        try {
            return URLEncoder.encode(value, StandardCharsets.UTF_8.toString());
        } catch (UnsupportedEncodingException ex) {
            throw new RuntimeException(ex.getCause());
        }
    }

  public static void main(String[] args) {
    String query = "Hellö Wörld@Some lang$!*()+;";
    String encodedQuery = encodeValue(query);
    // Hell%C3%B6+W%C3%B6rld%40Some+lang%24%21*%28%29%2B%3B
    System.out.println(encodedQuery);
  }
}

https://docs.oracle.com/javase/7/docs/api/java/net/URLEncoder.html
https://github.com/Azure/azure-sdk-for-java/pull/10273
cc @antkmsft, @JeffreyRichter, @gilbertw, @alzimmermsft

We are not building a generic HTTP stack; we are building an HTTP stack that only needs to talk to Azure services. For the blob service, see https://docs.microsoft.com/en-us/rest/api/storageservices/naming-and-referencing-containers--blobs--and-metadata
If we need to encode characters in addition to the reserved ones, that's fine and we should do it.
I can tell you for sure that we should NOT encode spaces as a '+'. Java does this and it has caused us enormous problems with the Storage service; we ended up having to write our own URL encoder for Java and not use the Java-built-in encoder.

I can tell you for sure that we should NOT encode spaces as a '+'.

Sounds good and that makes sense. Looks like the "path" component of the URL should never encode space as '+' but the query string part can. However, it is simpler to avoid that all together.
So, as it stands, we are currently over-encoding as some of the characters we encode aren't strictly necessary. This will result in slightly larger payload sizes, but for simplicity, it is fine to do so.
If we want to revisit this, the action item would be to follow RFC 3987 for IRI (https://tools.ietf.org/html/rfc3987#section-2.2) and let some of the characters (such as from the set @$!*();) through without encoding.
For now, this issue is not actionable. We can close this unless reducing size is important.

We are not building a generic HTTP stack; we are building an HTTP stack that only needs to talk to Azure services. For the blob service, see https://docs.microsoft.com/en-us/rest/api/storageservices/naming-and-referencing-containers--blobs--and-metadata

From that link:

However, there are certain characters that are not valid in URL paths even when encoded. These characters cannot appear in blob or container names. Code points like \uE000, while valid in NTFS filenames, are not valid Unicode characters, so they cannot be used. In addition, some ASCII or Unicode characters, like control characters (0x00 to 0x1F, \u0081, etc.), are also not allowed.

@JeffreyRichter, do we validate that the container name doesn't contain such characters? I am not sure, but I don't think it the responsibility of the url encoder to reject these, but we should try to adhere to these restrictions somewhere in the stack.

The Azure SDK team's policy (for all languages) is that clients do NOT validate values that are sent to a service; the service does the validation. The reason is that characters the service considers invalid today might be valid in the future and we don't want the SDK to block the service request. So, we should encode as required by RFCs but do not validate as required by services.

Thanks, closing.

FYI @CIPop


CRD Extractor utility inspects API group and organizes schemas by subdirectory

I think it would be helpful if the tool could have a look at the value of the spec.group attribute, create a subdirectory for it under $HOME/.datree/crdSchemas, and organize the corresponding schemas underneath it. This will help with avoiding to manually organize the schemas before providing the pull request for this repository.

@bmuschko good idea, we will prioritize and implement it 👍

Perfect, thanks!


Populate "sample-org-contoso" with Test Data and Integrate with CS-System

We want to create a robust and diverse set of test data within the sample-org-contoso repository to facilitate effective development and testing of the CS-System. This repository will act as a dedicated sandbox environment, allowing us to simulate various organizational structures and scenarios and ensure seamless data synchronization and integration within the development database.
In this sandbox repository, we want to include two types of data:

Badges: JSON files that adhere to predefined structures. These are badges that members can get in their specific organization.
Documents: Standard Markdown (.md) files that are for that specific organization.

These data should be organized into two folders named docs and badges.
Objectives
Test Data Creation

Populate the repository with a diverse range of documents and badges following our predefined structures.
Include complex scenarios, such as nested folders, badges requiring multiple approval steps, badges with multiple approval methods, etc...
Standard structure of badges and examples of test files we want to have in our test repository:

Example Document
Badge Structure
Example Badge

Integration and Synchronization

Configure the CS-System database to connect with the "sample-org-contoso" repository.
Validate that all test data is accurately retrieved and integrated into the development database during synchronization of the "sample-org-contoso" organization.

Steps to Participate

Comment: Comment on this issue with your estimated timeframe for completing the task.
Review: The administrators will review your proposed timeline.
Assignment: If approved, the issue will be assigned to you.
Reward: Receive the issue reward upon completing the task within the agreed timeframe.

Contribution Guidelines

Please refer to the Contribution Guidelines for detailed instructions on contributing to the project.

Deliverables

The PR for this issue should be approved by @mehrandvd. He will announce his approval on this issue.

Reward

The reward will be $10, which will be paid in $USDC (ERC20).

@Ali-Sdg90 The final repo would have these 2 folders: docs, badges.

@mehrandvd Thanks, I have updated the issue.


Checkboxes squish when their parent container's width shrinks

Describe the bug
We have an extension in VSCode called "Visual Studio Code for Education". In our VSCode extension's webview, when a checkbox's div shrinks in width, the width of the checkbox also shrinks in width.
To reproduce

https://vscodeedu.com (account is free, just need a msft account)
https://vscodeedu.com/courses/intro-to-python -> Start Course
On the left hand side Table of Contents, navigate to
4. Unit 3 - If
5. Lesson 4 - If Statement Patterns
6. "And vs Nested If"
7. Scroll down
8. Verify by expanding the right file over the left

Expected behavior
Checkboxes should retain their dimension
Current behavior
Checkboxes width's shrink as their containing div's width shrinks.
Screenshots
Notice how the checkboxes on the left squish as I reduce the width of our webview.
Desktop (please complete the following information):

OS Version: Windows 11 22621.3007
Toolkit Version: 1.4.0

Additional context
The element containing these checkboxes are vscode-checkbox, and the checked-indicator seems to be the checkbox itself. Both of these come from the toolkit.

We've been able to work around this by adding this to our main App.scss
vscode-checkbox::part(checked-indicator) {
    min-width: 16px;
}

Thanks for the heads up @benvillalobos! I'll definitely add this to backlog to look into and fix


Add file case change recognition mention to the release notes

Related to:

https://github.com/gradle/gradle/pull/9663
https://github.com/gradle/gradle/pull/9689

Merged, thanks for the input. If other changes are needed, let me know and I'll open a new PR.


Support flit.scripts

I need this to package flit.

@mgorny of the issues I opened this is the one I would like to see solved first, as it is blocking me from packaging slit.

Yeah, I've already written tests, now to make the code work ;-).

It's good all these new build systems just rename stuff from setuptools.
Do you need me to make a release now or can it wait until I tackle the other bug?

Yes, if you could make a release that would be great. I am installing flit_core with https://github.com/FFY00/python-build and https://github.com/FFY00/python-install as it doesn't require entrypoint script generation, which is not yet supported by https://github.com/FFY00/python-install.

Now in v6.


Implement --dry-run for ipc-cli commands

Subnet operators want to manage subnets from multisigs (concretely altering the federated validator power). Currently, all our ipc-cli commands send messages to the network using the a wallet EOA. We have two options:

Support various kinds of multisigs as senders (Filecoin native multisig, Gnosis multisig, etc.)
Simply print the message we would send instead of actually submitting it. The user can then use existing tools (e.g. lotus msig or Glif wallet) to craft the msig proposal by copying and stitching together the right values.

From internal discussion:


Using the $APP_ID variable on the WidgetExtension and OpenAction targets

Task/Issue URL: https://github.com/duckduckgo/iOS/issues/713
Tech Design URL: N/A
CC: N/A
Description:
Steps to test this PR:

Follow the steps to set up an external developer account from the repo readme - https://github.com/duckduckgo/iOS
You should be able to create an App Id that is unique to your developer account and run the project.

Copy Testing:

[x] Use of correct apostrophes in new copy, ie ’ rather than '

Orientation Testing:

[ ] Portrait
[ ] Landscape
[x] N/A

Device Testing:

[ ] iPhone SE (1st Gen)
[ ] iPhone 8
[ ] iPhone X
[ ] iPad
[x] N/A

OS Testing:

[ ] iOS 11
[ ] iOS 12
[ ] iOS 13
[x] iOS 14

Theme Testing:

[ ] Light theme
[ ] Dark theme
[x] N/A

Internal references:
Software Engineering Expectations
Technical Design Template

Thanks for this! It's been a busy couple of weeks so we're starting to pick these up now.

Hi @gholias - this certainly seems to work for DDG developers, so no problems/breakages there.
The problem is we have a new managed entitlement in the app  (com.apple.developer.web-browser) which will not be available to external developers, see DuckDuckGo.entitlements
Do you have any thoughts on the best approach for managing that with external developers?
Thanks!

Hi @brindy - My idea to fix the entitlement problem would be having a script that uses Fastlane to generate the App Identifiers in the developer Apple Developer Account.
This is my idea for the script:
#!/usr/bin/env bash
# exit if a command fails
set -e

export FASTLANE_USER="-"
export FASTLANE_PASSWORD="-"
export FASTLANE_TEAM_ID="XXXXX"

export APP_ID="com.externaldeveloper.duckduckgo.mobile.ios"
export GROUP_ID_PREFIX="group.${APP_ID}"

declare -A IDS

IDS["DuckDuckGo"]=$APP_ID
IDS["BookmarksTodayExtension"]="${APP_ID}.BookmarksTodayExtension"
IDS["QuickActionsTodayExtension"]="${APP_ID}.QuickActionsTodayExtension"
IDS["OpenAction"]="${APP_ID}.OpenAction2"
IDS["WidgetsExtension"]="${APP_ID}.Widgets"

for ID in "${!IDS[@]}"; do

    BUNDLE_ID="${IDS[$ID]}"
    APP_NAME="${ID}"

    echo "(i) Producing app $ID with bundleId $BUNDLE_ID and group $GROUP_ID_PREFIX"

    fastlane produce --app_identifier $BUNDLE_ID --app_name "$APP_NAME" --skip_itc
    fastlane produce enable_services --app-group --app_identifier $BUNDLE_ID
    fastlane produce associate_group --app_identifier $BUNDLE_ID $GROUP
done

The problem with that approach is that the developer will need to have Fastlane installed in their machine.
Also, I'm having some issues with xcode12 and automatic signing for the project. I will try to make it work if you think that is a viable approach to the problem.
What do you think?

Thanks @gholias - let me think on that.  In the meantime thanks for this PR!


Property IndentationControl

The Property IndentationControl seems to have no effect anymore.

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

ID: b4833ee8-8e6f-cd0e-5abe-e81ea823089c
Version Independent ID: b8e59ef9-ecc6-effe-8d94-dbe7003d2a3c
Content: Designing Indented Hierarchy Lists - Business Central
Content Source: dev-itpro/developer/devenv-indented-hierarchy-lists.md
Service: dynamics365-business-central
GitHub Login: @jswymer
Microsoft Alias: solsen

Hello, Thanks for the feedback.
This issue seems to be a duplicate of issue 1336. So, I will close this issue, and use 1336 for tracking.

@jswymer: I wanted to make sure that all articles get updated.


Build in Fedora 22

On Fedora: All of this be easily installed with dnf/yum:
dnf install -y cmake SDL2 SDL-devel boost-system boost-filesystem boost-date-time boost-locale boost-devel freeimage freeimage-devel freetype freetype-devel eigen3-devel libcurl libcurl-devel texlive-droid.noarch

Then, generate and build the Makefile with CMake:
cd YourEmulationStationDirectory
cmake .
make

This seems to work decently on Fedora 26 Beta


use an iconset

Right now I'm exporting logos individually from figma/sourcing from online, but it might be more productive to leverage an existing website
the old one used fontawesome, which seemed to work fine

@RachitMalik12 @srijonsaha any of y'all used a different iconset that might be better than fontawesome's

@RachitMalik12 @srijonsaha any of y'all used a different iconset that might be better than fontawesome's

I think fontawesome is good!

I like this one: https://antonreshetov.github.io/vue-unicons/. The icons look simple and clean.

I am not too picky with this stuff but here is how font awesome looks on the modal..

Wow the Vue unicons look amazing! It also has a CDN option, which imo makes this an obvious win over fontawesome:
<link rel="stylesheet" href="https://unicons.iconscout.com/release/v2.1.6/css/unicons.css">

Wow the Vue unicons look amazing! It also has a CDN option, which imo makes this an obvious win over fontawesome:
<link rel="stylesheet" href="https://unicons.iconscout.com/release/v2.1.6/css/unicons.css">

https://iconscout.com/unicons/getting-started/line
That said, I don’t mind (and would personally prefer) the npm install option when it comes to icons

https://github.com/antonreshetov/vue-unicons/issues/21 this has issues with typescript. @srijonsaha have you used it with typescript before? I'll use the cdn for now in the case we can't find a workaround..

https://github.com/antonreshetov/vue-unicons/issues/21 - there are issues with vue-unicons and typescript. There was a PR up to add type declarations and I tried using those but it lead to whole host of issues on trying to import the icons file. In order to not be blocked I'll use the cdn for now.
@srijonsaha have you used this with typescript before? any ideas?

@RachitMalik12 @srijonsaha I've got the icon set working in https://github.com/ubclaunchpad/new/pull/80


Rename zcl_abapgit_file_status

Change name from  zcl_abapgit_file_status=>status to  zcl_abapgit_repo_status=>calculate.
Ref https://github.com/abapGit/abapGit/issues/6178
Todo: https://docs.abapgit.org/development-guide/api/api.html#status

looks like this breaks something in abapGit/background_modes

this is a step binding the code more towards repo instead of decoupling repo?

or can the input be replaced with zif_abapgit_repo ? or out of scope for this change?

yes, small steps. next PR:

Replace calculate( io_repo ) with calculate( ii_repo type ref to zif_abapgit_repo ) and
Move zcl_abapgit_repo->status/mt_status/reset_status to zcl_abapgit_repo_status


Can not run with omniconfig==0.1.7

I have run into issues when running the following CLI, and I find that if I use omniconfig==0.1.5, this problem is solved.
I guess, there are some problems within omniconfig==0.1.7?
What I observed is that "parser.parse_known_args(args)" returned four items within omniconfig==0.1.7, but we are only expecting three items.
python -m lmquant.llm.run
configs/llm.yaml configs/qoq/gchn.yaml
--model-name llama2-7b --model-path /PATH/TO/LLAMA2-7B
--smooth-xw-alpha 0 --smooth-xw-beta 1
--smooth-yx-alpha 0.5 --smooth-yx-beta 0

Hi,
If you installed lmquant-v0.0.0, please fix ominconfig package to version 0.1.5.


GEOMESA-2638 HBase 2.2 support

New artifacts for use with HBase 2:

geomesa-hbase-distributed-runtime-hbase2_2.11
geomesa-hbase-spark-runtime-hbase2_2.11

Default HBase version updated to 2.2.2
Maven profile hbase1 for testing against HBase 1.4

Signed-off-by: Emilio Lahr-Vivaz<EMAIL_ADDRESS>

@elahrvivaz Ok, I made it through a first skim.  Is there anything I should focus on?  I imagine that we could ship this and the stacked merges, and then kick the tires with lots of testing.

rebased to fix merge conflicts


Failed generating BasicString from std::string

Brief Description
When generating a cs String from std::string (originally as a class field), it fails generating BasicString in Std.cs.

cc @ddobrev

Confirmed by @tritao :

Looks related to TrimSpecializationsPass
It only looks in parameters and return types to see if a particular specialization is needed

An a tempo workaround is suggested by @tritao :
public virtual void SetupPasses(Driver driver)
{
    driver.Context.TranslationUnitPasses.Passes.Remove(
        driver.Context.TranslationUnitPasses.Passes.Find(m => m.GetType() == typeof(TrimSpecializationsPass))
    );
}

OS: Windows / OS X / Linux (include version and/or distro)

Windows

Used headers
Used settings
Target: MSVC/GCC/Clang
Other settings
Stack trace or incompilable generated code

@ddobrev This one has affected another user yesterday, @thejuskambi.
Take a look when you can.


IOS Safari: Seeking does not work with custom HTML on audio element

Expected behaviour
Audio player seeks to touched part of the input range
Actual behaviour
Audio player pauses briefly and does not seek
Steps to reproduce
Create a plyr instance using custom HTML controls from the documentation here
Test with IOS Safari, the player does not seek
Environment

Browser: Safari
Version: 12
Operating System: iOS
Version: 12.1

Console errors (if any)
Link to where the bug is happening
https://codepen.io/bichan17/pen/wZReQK

Hi @sampotts, any chance you could look into this? Are you able to reproduce?

I have same problem :(

I had same problem and I use RangeTouch of @sampotts https://github.com/sampotts/rangetouch to fixed, just add
const ranges = RangeTouch.setup('input[type="range"]', {});
after created Plyr instance


use latest tifffile

I noticed that installing this package had downgraded my tifffile, meaning that my scripts using from tifffile import tiffcomment had broken.
Quick superficial test seems to show no problems with this change, I don't expect any are likely.

@xinaesthete Hope all is well.  I will merge this.

Very well thanks... I might want to discuss a potentially bigger PR on Viv soon...

Whenever you're ready! You know where to find me :)


vscode-ssh server has too many instance so that the server is on heavy load

VSCode Version: 1.43.2
OS Version: VSCode runs on Win10 and server runs on arch linux

Steps to Reproduce:

Open a ssh connection

Does this issue occur when all extensions are disabled?: Yes
Even when I close the connection the vscode-ssh-server remains. I have the feeling this multiplies everytime I log in again eventually taking every last bit of ram.

What extensions do you have installed on the remote? What processes are taking high cpu/ram?


OT Failures

Hi Jason,
The README states that "The DITA-OT Swagger plug-in has been tested against DITA-OT 3.x.
However, your mentioning how to install DITA 4.0 in the next few paragraphs.
Ever since we upgraded our Docker image to use Java 11 and OT 3.7.4, any use of a topicref with format="swagger" fails. It's been running just fine for a couple years prior to that.
Are there any other compatibility issues which we should be aware of? It looks like you updated some dependencies recently, so were they related to compatibility with DITA 4.x? We plan to move to 4.1 in our next release of our internal pipeline, but for the moment we're running on 3.7.4.
I noticed that you made changes last week to some dependencies, but you haven't issued a new release.

The plugin is was originally written and should work with DITA-OT 3.x - that is part of the original README.
The plugin is regularly updated to run against latest DITA-OT. So far it is usually just the tests and test dependencies that have needed to be updated - for example when a PanDoc release alters the HTML. Since I'm only testing this against latest DITA-OT 4.x I would always recommend that version.
Since I'm not regularly re-testing against DITA-OT  3.x I couldn't guarantee against regression errors, but the best formatting will occur with a 4.x engine.


Compatibility with tokio

Hey :)
So serde_json's serializer and deserializer support Write and Read respectively, but unfortunately they aren't compatible with tokio.
The basic rule of I/O with tokio (I should contribute some docs somewhere) is that any downstream I/O operation can fail with WouldBlock, which means "come back later". So any operations must be retryable. That isn't the case with serde_json right now, though. For example:

In deserialize_enum, remaining_depth will not be incremented again if visit_enum fails. To avoid general issues of this kind, an RAII-style lock/guard pattern might help.
The serializer heavily uses write_all, which is incompatible with tokio. Instead, you'd need to use an internal buffer.

I'd personally say just documenting the incompatibility is fine for now.
I'll soon be open sourcing a library to help out with testing I/O operations, so hopefully you'll find that of use here :)

The library is now available as partial-io on crates.io, (repo at https://github.com/facebookincubator/rust-partial-io). You could use quickcheck to do roundtrip tests and hopefully find bugs pretty easily.

This coupled with any improvements we can make to from_reader would make me very happy.
Do you have any thoughts on this @dtolnay? I wouldn't mind spending some time in the near-future (vague GitHub commitment) experimenting with this.

My impression was that for streaming serialization and deserialization use cases you typically want the data to be framed, as with tokio-serde-json. You mostly only care about JSON processing time if your server is CPU-bound, in which case you don't want to spend extra CPU time on incremental parsing if you can parse faster from a complete buffer all at once. If the server is not CPU-bound, JSON processing time would not meaningfully affect latency. Can you explain more about the use case where you care about this or #160?
I might approach this by building a resumable serde_json::Value parser. Resumable meaning it can make some progress, hit a WouldBlock, and resume later from the previous incomplete state. I don't see us solving the general case of resumable parser for an arbitrary implementation of Deserialize. But going through serde_json::Value, most of the branching and processing (interpreting string escape sequences, decimal-to-binary conversion of numbers) can happen while waiting on I/O and later turning Value into T will be fast.

Sorry @dtolnay I may have overstated my 'need' for this. It's more something I'd be interested to explore. I found my way here while playing with async response bodies in reqwest. Since the response can return WouldBlock if a chunk hasn't been received, we need to buffer it completely before handing over to serde_json. Chunks don't necessarily correspond to a frame in a codec. There are strategies around that with the current status-quo, like collecting the chunks first without buffering, or just accepting the copy which is probably going to be faster anyways.
But if serde_json did support non-blocking reads in some way then I'd like to see what that would mean for general response deserialisation, since it probably wouldn't result in more code than buffering first on my end. Having a resumable Value parser only sounds reasonable to me.
So that's a bit of a flimsy motivation, but I'd like to play with it.

Triage: I still think a resumable/nonblocking way to deserialize specifically a serde_json::Value is the way to go; we don't need to solve the much bigger challenge of resuming an arbitrary implementation of Deserialize. I would be interested to have an implementation of this that we can benchmark.
Since I haven't worked with tokio myself -- what's the most obvious API that would support nonblocking deserialize of Value from a byte stream? If one of you could provide a sketch of the public API here, I'll file the idea in https://github.com/dtolnay/request-for-implementation (or you can file it directly).

@dtolnay it’s been a while since I’ve thought about this 🙂 So will post on the tokio dev channels, give it some thought and circle back here, unless somebody else beats me to it.

@KodrAus I don't want to beat you, I just wanna say it's still a wanted feature 😉

I feel like we might be able to leverage async/await to deal with the progress tracking/continuation state rather than make the deserializer support re-entry. That would also allow arbitrary Deserialize implementations. Here's what I'm thinking:

Copy de::Deserializer to a new type de::AsyncDeserializer.
Specialize it to de::IoRead by replacing any uses of de::Read with the concrete implementation in IoRead. The whole type should be generic over AsyncRead.
Replace any blocking I/O calls with the equivalent AsyncReadExt call, await it, and mark the containing function async.
Follow the compiler errors up the stack, adding .await and making methods async as you go.
Find any bits between de::Deserializer and de::AsyncDeserializer that are still the same and factor them out.
Profit?

You mostly only care about JSON processing time if your server is CPU-bound, in which case you don't want to spend extra CPU time on incremental parsing if you can parse faster from a complete buffer all at once. If the server is not CPU-bound, JSON processing time would not meaningfully affect latency.

@dtolnay in situations when JSON doesn't fit into RAM, and you fetch it in an async manner via streams, what is the expected solution then?

Is there any progress on this issue?


Move the validate logic to form request

As explained in this video
https://www.youtube.com/watch?v=W0jyphqYkdk
Docs
https://laravel.com/docs/9.x/validation#form-request-validation

That's a good suggestion. I've been thinking of doing this myself for some time. Let's see if I can get some time this weekend


Leo 3

Checks

[ ] Your YAML file has required fields as listed in Specs
[ ] All checks have passed yaml-lint passed
[ ] You agree to contribute your work under MIT license

closing


When I try to connect to WampServer by Web Socket Client , WampServer…

… send a ’Hello Message’ to client.
I think that I do not need. So comment out Hello Message.
https://developer.mozilla.org/en/docs/Web/API/WebSocket#Example

The welcome message is part of the WAMP protocol. The client expects to receive it.

Oh, I see.


add support for Api proxy

In order to support running the RackHD on-taskgraph and on-http services on a host that does not have Layer-2 network access to the PXE network we need a host that does have access to the PXE network and can proxy requests to the southbound API endpoint over a management network.
The proxy server, nginx in my POC, adds headers to the requests coming from the PXE client that contain headers that will be used during profile, template, and task rendering.
The headers are
X-Real-IP - the actual IP address of the PXE client
X-RackHD-api-proxy-ip - The IP address of the API proxy server
X-RackHD-api-proxy-port - The port of the API proxy server
The proxy server URL is added to the lookup record for the PXE client so that it can be used during task rendering since the original HTTP request is not available at that time.
This is one of three pull requests. There will also be subsequent changes to on-core  and on-tasks to support this.
on-core PR: https://github.com/RackHD/on-core/pull/131
on-tasks PR: https://github.com/RackHD/on-tasks/pull/185
test-coverage.tar.gz

@RackHD/corecommitters please review.

@shanemsully sorry for the merge delays here, looks like all these are ready to go, just need another rebase here.

@shanemsully : Could you please fix the unit-test problem? I checked the log it is caused by your code.

@yyscamper, The failures are due to dependencies with code changes in my on-core review (https://github.com/RackHD/on-core/pull/131)  I changed package.json locally to pull on-core from my forked repo end the unit tests pass.

@shanemsully : OK, thanks

:+1:

Dependent PRs have been merged, so Jenkins test this please

Coverage decreased (-0.1%) to 91.031% when pulling bd28a60753eb0f15dd8e82f64af6ec19cf516d9f on shanemsully:http-proxy into 73711ef561df60ce0df73f9d8fe58d7f87d8e31a on RackHD:master.

Coverage decreased (-0.1%) to 91.001% when pulling 1545ca2dc0e79de56c6736299deab6908087492f on shanemsully:http-proxy into 73711ef561df60ce0df73f9d8fe58d7f87d8e31a on RackHD:master.

Coverage decreased (-0.1%) to 91.001% when pulling 263eb334ef204090c98213972b671c490ffa48dc on shanemsully:http-proxy into 874756b10e8aede2708114c79637f656e0382880 on RackHD:master.

:+1: Looks good.  Thanks for the contribution!  FYI - on-http unit tests occasionally fail with timeouts which is what happened during the last Travis run.  I've restarted Travis, I expect it to pass this time.

Coverage decreased (-0.03%) to 91.067% when pulling 263eb334ef204090c98213972b671c490ffa48dc on shanemsully:http-proxy into 874756b10e8aede2708114c79637f656e0382880 on RackHD:master.

ok to test


postWebMessage failed

Hello, I would like to send a message to JavaScript using the postWebMessage method:
WebviewController kWebController=WebviewController();
//Several initialization tasks for WebWiew
........
_ Subscriptions. add (kWebController. loadingState. listen ((state)){
DebugPrint ('Loading state: $state ');
If (state==LoadingState. navigation Completed){
KWebController.executeScript（
"Window. addEventListener ('message ', event=>{console. log ('Received message:', event. data);});";
KWebController. postWebMessage ("hello world");
}
});
After completion
KWebController. postWebMessage ("hello world");
There was an error in this call:
[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: PlatformException(not_supported, Posting the message failed., null, null)
#0      StandardMethodCodec.decodeEnvelope (package:flutter/src/services/message_codecs.dart:652:7)
#1      MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:310:18)

How should I solve it? Looking forward to your reply!

same issue.
And can you post msg from web ?


BigQuery table refresh

In BigQuery we added Job#refresh! to update the data for the job. This has proven to be very useful, we should extend this to Table and View.

I kinda wonder if we should refresh all the things... Thoughts?

The question is where to stop... I know Table makes sense because I find myself trying it in console, and feeling frustrated that it's not there. I say we add it to Table for now, and see where else we wish we had it.

I meant being able to refresh a Storage Bucket and File, a Pub/Sub Topic and Subscription, and a Datastore Entity. Extending this pattern to more than just BigQuery.

Agreed. If you know where it's needed, let's do it.
Question: Any chance you want to go with reload! instead of refresh! if we are going to do this widely? Fewer characters and similar to http://api.rubyonrails.org/classes/ActiveRecord/Persistence.html#method-i-reload

Currently Storage ACL and BigQuery Job use refresh!. Nothing in the public API uses reload!, although we can add an alias for it.

OK, I vote for adding a reload! alias.


Tracking issue: Document public API (introduce #[warn(missing_docs)])

According to https://docs.rs/probe-rs/0.10.1, only 26.77 % of the public API of the 0.10.1 releas eof probe-rs is documented. To improve this,
we should start improving the documentation, and add the #![warn(missing_docs)]] lint to modules which are fully documented, so that the documentation doesn't deteriorate over time.
I suggest this approach to avoid introducing the lint for the whole crate, and then having hundreds of warnings until the documentation is fixed.
To-Do

[ ] probe_rs::architecture
[ ] probe_rs::core
[ ] probe_rs::debug
[ ] probe_rs::error
[ ] probe_rs::flashing
[ ] probe_rs::memory
[ ] probe_rs::probe
[x] probe_rs::session (see #456)

That is terrible stats :/ Thanks for opening this tracking issue :)


Need to support escrow service

For safe service transactions, we need a utility service with the following requirements:

Customer’s money can be reserved to guarantee payment when the service is provided successfully
If the service was provided successfully, the money is safely transferred to the service provider
Otherwise, the money is safely refunded to the customer
The decision on the success can be made by either the customer, the service admin, or the service provider, and it’s configurable.

Fixed with https://github.com/ainblockchain/ain-blockchain/pull/262


Cannot Open R Interactive Window

I attempted to open the R interactive Window and instead I received the following error message (screenshot attached):

I repaired Visual Studio 2017 and still it did not work.
Additional information:
OS Information
Version:       Microsoft Windows NT 10.0.16199.0
RTVS Information:
Assembly: Microsoft.VisualStudio.R.Package, Version=1.1.30413.947, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a

If you're using R 3.4, this is a known issue.

This means that for some reason dependency (interactive window) was not installed. As a workaround, try adding .NET workload since it installs the component.

This looks identical to the error that some PTVS users are getting.
https://github.com/Microsoft/PTVS/issues/2534

@smj389 please let us know if adding the .NET workload solves the issue. Some Python users have had the same issue, and uninstall/reinstall of VS 2017 was the only way to get it working (see my link above).
We haven't been able to reproduce this issue. Was this a clean install of VS 2017, or an update of a previous build?  If an update, what build did you have installed prior to this?

Merging into #3537, there is more info there.


acquireTokenSilent always bypasses the cache when no scope is passed

Core Library
MSAL.js (@azure/msal-browser)
Core Library Version
3.7.1
Wrapper Library
MSAL Angular (@azure/msal-angular)
Wrapper Library Version
3.0.11
Public or Confidential Client?
Public
Description
When trying to acquire a token silently (with acquireTokenSilent), passing an empty aray of scopes, the token is obtained successfully, but the cache is bypassed: a request to the token endpoint is sent every time before returning the token.
Adding a useless scope ('User.Read') fixes the issue.
Error Message
No response
MSAL Logs
No response
Network Trace (Preferrably Fiddler)

[ ] Sent
[ ] Pending

MSAL Configuration
{
    auth: {
      clientId: 'ad42dfc7-d1df-450e-aab5-2f1c34c4741d',
      authority: 'https://login.microsoftonline.com/6981636a-c14f-494e-8722-38ba9f8aabab/',
      redirectUri: '/',
      postLogoutRedirectUri: '/',
      navigateToLoginRequestUrl: false,

    },
    cache: {
      cacheLocation: BrowserCacheLocation.LocalStorage
    },
    system: {
      allowNativeBroker: false, // Disables WAM Broker
      loggerOptions: {
        loggerCallback,
        piiLoggingEnabled: false
      }
    }
  }

Relevant Code Snippets
import { HttpInterceptorFn } from '@angular/common/http';
import { inject } from '@angular/core';
import { MsalService } from '@azure/msal-angular';
import { switchMap } from 'rxjs';

export const authInterceptor: HttpInterceptorFn = (req, next) => {
  const msalService = inject(MsalService);
  let activeAccount = msalService.instance.getActiveAccount();
  if (activeAccount) {
    return msalService.acquireTokenSilent({
      account: activeAccount,
      scopes: []
    }).pipe(
      switchMap(authenticationResult =>
        next(req.clone({ setHeaders: { Authorization: `Bearer ${authenticationResult.accessToken}` }}))
      )
    );
  } else {
    return next(req);
  }
};

Reproduction Steps
Use the above HTTP interceptor and, after being logged in, send requests every N seconds. Each request causes a POST request to https://login.microsoftonline.com/6981636a-c14f-494e-8722-38ba9f8aabab/oauth2/v2.0/token to be sent before the actual request.
Expected Behavior
acquireTokenSilent should return the token from the cache.
Identity Provider
Entra ID (formerly Azure AD) / MSA
Browsers Affected (Select all that apply)
Chrome, Firefox, Edge, Safari
Regression
No response
Source
External (Customer)

Hi @jnizet,
This is expected behavior. If you enable MSAL trace logging you will see the following error message in the logs: Scopes cannot be passed as null, undefined or empty array because they are required to obtain an access token. This makes MSAL.js bypass cache lookup and make a network call to acquire a new token. Please refer to the error message source and the corresponding unit test. Also, please keep in mind that MSAL.js adds openid, profile and offline_access scopes to every network request by default. Please refer here for more details.

Hi @konstantin-msft
Thanks for responding.
I'd argue that

the error message is wrong since, as you said, if we pass no additional scope, a network request is done and successfully acquires an access token. It's thus perfectly possible to get one without passing additional scopes. It's just that MSAL won't let you get it from the cache.
if the intention is really for MSAL to forbid getting a token without passing additional scopes even though the server allows it, then it should fail immediately and throw rather than swallow the error and make a network request every time.

I tend to agree. That's not the best user experience. Let me create an item for tracking. Appending default scopes for the cache lookup looks like a good solution to me.
Meanwhile, please use a workaround by passing one of the default scopes.


Add start and end events for collapse and expand transitions.

There are plenty of use cases where one would need to know when a collapse or accordion section is finished expanding/collapsing. This PR adds some simple start and end events that are emitted around the expand/collapse transistions. This will allow users of the collapse or accordion widgets to know when the animation is done so that they can take further action.

@chrisirhc I see you added this to the 'Purgatory' milestone. Does that mean it is in limbo and is pretty much being ignored? Any idea when it might get looked at?

Hopefully @chrisirhc will chime in shortly - my additional thoughts on this - Is there some documentation that would also need to be updated?  Can that be added to this PR?

I put this as Purgatory as I don't see it resolving any existing issues (hence, it's not a priority) and because this introduces a possible breaking API change in the future.
The current plan is to convert the collapse module to use the $animate service which would have a $animate:close event. This is to make use of the services provided by Angular to keep it consistent with its animation APIs.
I was working on #1444 before, but now it seems that the $animate service has changed since and there might be a more concise way of using the $animate service.

Since we migrated to ngAnimate for this, I am closing this as superceded - as @chrisirhc mentioned, $animate has events you can hook into if necessary.


argocd-autopilot v0.2.24 hangs on repo uninstall

k3s v1.21.5+k3s2
argocd-autopilot v0.2.24
argocd-autopilot repo uninstall hangs on waiting for 'autopilot-bootstrap' to be finish syncing.. until I hit ctrl+c & then it hangs on secret "autopilot-secret" deleted & never finishes.
Before executing argocd-autopilot repo uninstall I've previously successfully deleted the only project with argocd-autopilot project delete argocd-demo
INFO cloning repo: https://github.com/vainkop/argocd-autopilot-demo.git
Enumerating objects: 18, done.
Counting objects: 100% (18/18), done.
Compressing objects: 100% (14/14), done.
Total 18 (delta 1), reused 18 (delta 1), pack-reused 0
INFO pushing changes to remote
waiting for 'autopilot-bootstrap' to be finish syncing.. ^Cgot signal: interrupt

INFO Deleting cluster resources
application.argoproj.io "argocd-demo-new-app" deleted
application.argoproj.io "argocd-demo-new-app-2" deleted
application.argoproj.io "cluster-resources-in-cluster" deleted
application.argoproj.io "root" deleted
application.argoproj.io "argocd-demo-demoapp" deleted
application.argoproj.io "autopilot-bootstrap" deleted
application.argoproj.io "argo-cd" deleted
secret "autopilot-secret" deleted

Hey @vainkop, can you check if it's still reproduces for you?
Also I added a workaround that should make it easier. I exposed the --force flag on the repo uninstall command. This flag should ignore some steps that may fail during the installation and will try to leave the cluster and repo as clean as possible. You can take a look here #243 .

same issue here, force doesnt help either.


XSF integration

I've updated the tests and made various bugfixes and tweaks to the XCrySDenStructureFormat.jl package to better integrate into AtomsIO.jl.
I'm still missing one lammps.xyz file referenced in mfherbst/AtomsIO.jl/xsf. @mfherbst do you know why this is referenced / should I remove that test for now?

See the file in #23

I noticed that sometimes the extXYZ tests fail; seems like the comparison is right on the edge and depends on some noisy numerics.


Opened projects won't be back at launch

Hello,
I'm sorry I don't have much idea how to report the problem, and I never done that before, so I'll try my best.
I learned from this issue tracker that "Opened projects" was recently added to Atom. While it requires obviously some technical precisions (no command line option must be used), the exemple is given of a shortcut in a OSX Dock, but I'm on windows... So I tried to delete anything unnecessary in the windows atom short cut (there were like ../update.exe -open atom.exe) so I just let ../atom.exe
It doesn't seem to work.... at all.
I don't have many pluggins only essentials (I guess), here is the list : atom-alignment, atom-color-highlight, autocomplete-plus, emmet, file-icons, linter, minimap, Sublime-style-columns-selection.
Should I disable any pluggin to test ? And reactivate one by one. Or is this a common known problem ?
I've seen the update is fairly recent, so I may be the first to get the problem.
I hope this'll help you, I'm open to any question if you need anything more
Windows 8.1(Pro)
Atom 0.194

Duplicate of #6466, please subscribe there for updates.


week 27 review ticket

final project plan
space and time hacks
Individual Blog
Space and Time implementation
Pair Coding

Github Contributions:

2.7+
Created team plan, organized scrum board, did all space and time hacks and scored over 0.9 on the college board quiz

.45 for Pair Scoring

2.7+ - GH commits, good analysis of big idea 2 quiz questions, final project plan, cpt outline, completed space time hacks.


Move logo to the bottom

Moves the logo to the bottom of the sidebar rather than the top.

Looks better IMO. Doesn't indent the title / not have a full-logo.

:+1: , Nice looking now :)


fix: long email address on create Identity

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR Type

[x] Bugfix
[ ] Feature
[x] Refactoring

Context

[x] Closes #4835

Details:

[x] move IdentityForm outside rmrk folder

[x] use native html verification

[x] BasicInput "max" 32chars prop

[x] Vue 3 refactoring

Before submitting pull request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </bsx/collection>
[ ] I've tested PR on mobile
[ ] I've written unit tests 🧪
[ ] I've found edge cases

Had issue bounty label?

[x] Fill up your KSM address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot 📸

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.

mfw I see a form without <form> tag
small note

remove unused code in IdentityForm
could you fix/remove box class issue in darkmode
can we have full width submit button? 🥺

Thanks. I have updated all of them.

on the other hand I just saw that the limit of 32 characters must be set on all fields :/

Good catch! I have updated it.

pay 50 usd

😍 Perfect, I’ve sent the payout
💵 $50 @ 36.79 USD/KSM ~ 1.359 $KSM
🧗 Caiv9TbPz68q5dC8EcHu5xKYPRnremimGzqmEejDFNpWWLG
🔗 0x3b1343d0c447a89f6a6ac36d02ab28986a8c3da1603554225f472ab1590e5532
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


FloatingHint-Style for more controlls

The floating hint style seems to only exist for a small number of controlls.
I found one for the TextBox and the ComboBox but it seems for example to be unavailable for the DatePicker and PasswordBox.
I would really like to use this style but it looks not good if you mix it with controls that don't support this style. Is such a style planned? Is there a road map for such things? This would allow me to use it and wait for the missing styles if the are not so far away.

OK, yeah, can add that to the list.

[ ] DatePicker
[ ] TimePicker
[ ] PasswordBox

I think it would also be nice to have this style for the textblock and the checkbox/radiobutton.
The Textblock looks kind of out of place at the moment if used next to texboxes to display unchangable data. The workaround is to use a disabled textbox.
Checkboxes and radiobuttons look also out of place because they need a top margin.
On this controls it would be enough to give them the same distance to the top like for example a textbox.
I believe having a Floating hint style for both would make it significant easier to use all these controlls in a single gui without the need to "move" some of them with margins.

@FrTerstappen
Margin issues aside, I'm not sure I understand.  How do you envisage a radio/checkbox looking with an animated floating hint.  And a TextBlock?
Maybe you could post a screenshot/mock-up?

@ButchersBoy
Okay i think i did not make my point clear. I made some screenshots to make it more clear.
Both controls are in a grid with row set to auto and colum width="*".
This is a check box next to a text box on font size 16:

The checkbox is clearly out of line.
Beside that you can see the check box is not centered in front of the text on other font sizes.
I can fix this with a Margin="0,15,0,0" but this depends on the font size and is very annoying if you have a lot of controls.

The check box being not centered in front of its text can be fixed with VerticalContentAllignment="Center"

The floating hint style would in this case not include a floating hint. It would more be a BeInLineWithTheFloatingHintControls-Style.
The same goes for the text block except that the text block need to display a hint.

Bit more complicated than that, as we have validation (below) which also comes in two different forms; below and popup-below.  So if I was gonna cover all angles I'd end up with a lot of noise.  I'll have a think about it, but I suggest for now you use style inheritance based on of the MaterialDesignTheme.TextBlock.xaml styles, customize for your margin, and apply that in a local resource dictionary (for example Grid.ResourceDictionary).

@ButchersBoy
Thanks for the suggestion but i think that this is not really applicable. The margin changes with the font size and i would end up with a few styles.
I can see that it would require you to cover many cases. The workaround is so easy that i think this is very low priority compared to the other controls.

I have extended the PasswordBoxTheme based on the TextBoxTheme to support floating like the TextBox. Maybe i forgot something, but it was a quick workaround for me until this control is supported.
FloatingPasswordBox.zip

@4ipalino if you want to open up a PR I'll code review it and we can pull it in?

@l1pton17 is working on a PR which will add the missing styles.
https://github.com/ButchersBoy/MaterialDesignInXamlToolkit/pull/303

Any FloatHint update on DatePicker?

Yeah it's in 2.0

Thanks a lot, any time to release to NuGet?

It's already there...use -pre (pre release)


With version  2.0.2 getting react-native-quick-base64:generateJsonModelDebug error

Hi,
with the update 2.0.2 android build is failing with the following error. Can you please check
Execution failed for task ':react-native-quick-base64:generateJsonModelDebug'.

C:\Users\aj\work\node_modules\react-native-quick-base64\android\CMakeLists.txt : C/C++ debug|armeabi-v7a : CMake Error at C:\Users\aj\work\node_modules\react-native-quick-base64\android\CMakeLists.txt:14 (add_library):
Syntax error in cmake code when parsing string

  C:\Users\aj\work\node_modules/react-native/ReactCommon/jsi/jsi/jsi.cpp

Invalid character escape '\U'.

Can you reproduce it with example?

Related: https://github.com/mrousavy/react-native-mmkv/issues/280

Related: mrousavy/react-native-mmkv#280

Had the same issue building windows. The solution in this thread worked for me.

Related: mrousavy/react-native-mmkv#280

I was experiencing the same issue on windows, but the solution in this thread worked.


exit codes for --version and --help

--version should return a 0 exit code, currently it returns 1
--help should return a 0 exit code or 22 which is EINVAL 22 Invalid argument
this allows commands that check to see if the command is actually working to do so:
https://github.com/bevry/dorothy/blob/master/commands/command-working

Thank you.
I will work on it next version.

@balupton Hi,
This behavior has been fixed at v1.2.2.
$ teip --version
teip 1.2.2
$ echo $?
0
$ teip --help &> /dev/null
$ echo $?
0

If you have any other issues, please let me know.


Install the grpc optional deps.

Merging with the failure. See #232 for details.

@geigerj I have proven this eliminates all remaining dependency problems locally.
There is still a problem with the language-v1beta2 tests, but I think the issue is with the tests themselves. After this is merged, I can prove that by merging it into pubsub (which was my local test case when @eoogbe was working on the tests before).

I have proven that this is an insufficient fix (pubsub is giving me local failures), so holding off on merging.

The problem is with installing all of the packages into the virtualenv.
Just pubsub alone, pip freeze:
(775478c5) lukesneeringer@lukesneeringer0:~/Code/Google/api-client-staging/generated/python:pubsub-python-v1-2fa65afd$ pip freeze
appdirs==1.4.3
coverage==4.3.4
dill==0.2.6
enum34==1.1.6
future==0.16.0
gapic-google-cloud-pubsub-v1==0.15.4
google-gax==0.15.8
googleapis-common-protos==1.5.2
grpc-google-iam-v1==0.11.1
grpcio==1.2.1
httplib2==0.10.3
mock==2.0.0
oauth2client==3.0.0
packaging==16.8
pbr==3.0.0
ply==3.8
proto-google-cloud-pubsub-v1==0.15.4
protobuf==3.2.0
py==1.4.33
pyasn1==0.2.3
pyasn1-modules==0.0.8
pyparsing==2.2.0
pytest==3.0.7
pytest-cov==2.4.0
rsa==3.4.2
six==1.10.0

With everything, pip freeze:
(775478c5) lukesneeringer@lukesneeringer0:~/Code/Google/api-client-staging/generated/python:pubsub-python-v1-2fa65afd$ pip freeze
appdirs==1.4.3
coverage==4.3.4
dill==0.2.6
enum34==1.1.6
future==0.16.0
gapic-google-cloud-datastore-v1==0.15.3
gapic-google-cloud-error-reporting-v1beta1==0.15.3
gapic-google-cloud-functions-v1beta2==0.15.3
gapic-google-cloud-language-v1==0.15.3
gapic-google-cloud-language-v1beta2==0.15.3
gapic-google-cloud-logging-v2==0.14.0
gapic-google-cloud-monitoring-v3==0.15.3
gapic-google-cloud-pubsub-v1==0.15.4
gapic-google-cloud-spanner-admin-database-v1==0.15.3
gapic-google-cloud-spanner-admin-instance-v1==0.15.3
gapic-google-cloud-spanner-v1==0.15.3
gapic-google-cloud-speech-v1==0.15.3
gapic-google-cloud-speech-v1beta1==0.15.3
gapic-google-cloud-vision-v1==0.90.3
google-gax==0.15.8
googleapis-common-protos==1.5.2
grpc-google-iam-v1==0.11.1
grpcio==1.2.1
httplib2==0.10.3
mock==2.0.0
oauth2client==3.0.0
packaging==16.8
pbr==3.0.0
ply==3.8
proto-google-cloud-datastore-v1==0.90.3
proto-google-cloud-error-reporting-v1beta1==0.15.3
proto-google-cloud-functions-v1beta2==0.15.3
proto-google-cloud-language-v1==0.15.3
proto-google-cloud-language-v1beta2==0.15.3
proto-google-cloud-logging-v2==0.91.3
proto-google-cloud-monitoring-v3==0.15.3
proto-google-cloud-pubsub-v1==0.15.4
proto-google-cloud-spanner-admin-database-v1==0.15.3
proto-google-cloud-spanner-admin-instance-v1==0.15.3
proto-google-cloud-spanner-v1==0.15.3
proto-google-cloud-speech-v1==0.15.3
proto-google-cloud-speech-v1beta1==0.15.3
proto-google-cloud-vision-v1==0.90.3
protobuf==3.2.0
py==1.4.33
pyasn1==0.2.3
pyasn1-modules==0.0.8
pyparsing==2.2.0
pytest==3.0.7
pytest-cov==2.4.0
rsa==3.4.2
six==1.10.0

Odd. Versions are identical. Something does not make sense here.

I figured it out. The bogus logging-docs protos were the problem.


operator/ingress: Add unsupportedConfigOverrides

Add a spec.unsupportedConfigOverrides field to the IngressController API to accommodate unsupported configuration overrides.
This PR resolves NE-549.

operator/v1/types_ingress.go (IngressControllerSpec): Add an UnsupportedConfigOverrides field with type runtime.RawExtension.
operator/v1/0000_50_ingress-operator_00-ingresscontroller.crd.yaml:
operator/v1/zz_generated.deepcopy.go:
operator/v1/zz_generated.swagger_doc_generated.go: Regenerate.

This new API field supersedes the feature gate that https://github.com/openshift/api/pull/872 proposed, based on discussion with @deads2k, @derekwaynecarr, and @sgreene570.

/lgtm

Rebased.

Rebased.  And inexplicably, go.mod and go.sum again needed to be regenerated.

I ran go mod tidy, and then verify-deps complained  that I needed to run go mod tidy, so I'll try dropping the changes that go mod tidy made.

I had been using Go 1.15.10, and after I updated to Go 1.16.3 and reran go mod vendor and go mod tidy, I didn't see any changes in go.mod or go.sum.  Maybe it was the Go version or the old Go version's cache that caused the spurious changes.

/lgtm
/approve

This old canard:
time="2021-04-05T13:33:47Z" level=info msg="Error: unable to parse option \"output:dir=/tmp/tmp.0812HhB7no\": [invalid digit '8' in octal literal (at <input>:1:10)]"

/retest


Allow "describe" first parameter an array

I am pretty sure it is a common pattern to have a single file per subject function, e.g.
./tests/utilities/fixText.js
describe('utilities', () => {
    describe('fixText', () => {
        context('unrecognized syntax', () => {
            it('throws an error', () => {
                expect(() => {
                    fixText('', {
                        syntax: 'java'
                    });
                }).to.throw(Error, 'Unknown syntax "java".');
            });
        });
        context('JavaScript syntax', () => {
            context('invalid syntax', () => {
                it('throws an error', () => {
                    expect(() => {
                        fixText('let foo;<>;;', {
                            syntax: 'js'
                        });
                    }).to.throw(Error, 'Parsing error: Unexpected token (line: 1, column: 10).');
                });
            });
            it('fixes syntax error', () => {
                const report = fixText('let foo;;;', {
                    syntax: 'js'
                });

                expect(report).to.equal('let foo;\n');
            });
        });
    });
});

I'd have a separate test file for each utility.
I am using describe blocks to categorize tests (utilities, fixText, ...), which gives a grouped output, e.g.
  utilities
    fixFiles
      no file paths
        ✓ generates empty report
      JavaScript syntax
        ✓ fixes syntax error (554ms)

  utilities
    fixText
      unrecognized syntax
        ✓ throws an error
      JavaScript syntax
        ✓ fixes syntax error (88ms)
        invalid syntax
          ✓ throws an error

  utilities
    lintFiles
      no file paths
        ✓ generates empty report

  utilities
    lintText
      unrecognized syntax
        ✓ throws an error

The problem with this pattern is that my tests are nested in many functions, requiring a lot of levels of indentation. It could be made a lot simpler if describe would accept an array of descriptions that describe different levels, e.g. original code could be re-written to be:
describe(['utilities', 'fixText'], () => {
    context('unrecognized syntax', () => {
        it('throws an error', () => {
            expect(() => {
                fixText('', {
                    syntax: 'java'
                });
            }).to.throw(Error, 'Unknown syntax "java".');
        });
    });
    context('JavaScript syntax', () => {
        context('invalid syntax', () => {
            it('throws an error', () => {
                expect(() => {
                    fixText('let foo;<>;;', {
                        syntax: 'js'
                    });
                }).to.throw(Error, 'Parsing error: Unexpected token (line: 1, column: 10).');
            });
        });
        it('fixes syntax error', () => {
            const report = fixText('let foo;;;', {
                syntax: 'js'
            });

            expect(report).to.equal('let foo;\n');
        });
    });
});

I agree that you can end up with quite a bit of nesting, but is style/formatting exacerbating the problem a bit in the example above?
describe('utilities', () => {
    describe('fixText', () => {
        context('unrecognized syntax', () => {
            it('throws an error', () => {
                expect(() => {
                    fixText('', {
                        syntax: 'java'
                    });
                }).to.throw(Error, 'Unknown syntax "java".');
            });
        });
        context('JavaScript syntax', () => {
            context('invalid syntax', () => {
                it('throws an error', () => {
                    expect(() => {
                        fixText('let foo;<>;;', {
                            syntax: 'js'
                        });
                    }).to.throw(Error, 'Parsing error: Unexpected token (line: 1, column: 10).');
                });
            });
            it('fixes syntax error', () => {
                const report = fixText('let foo;;;', {
                    syntax: 'js'
                });

                expect(report).to.equal('let foo;\n');
            });
        });
    });
});

// =>

describe('utilities', () => {
  describe('fixText', () => {
    it('throws an error given unrecognized syntax', () => {
      expect(() => {
        fixText('', {syntax: 'java'});
      }).to.throw(Error, 'Unknown syntax "java".');
    });

    context('JavaScript syntax', () => {
      it('throws an error given invalid JS syntax', () => {
        expect(() => {
          fixText('let foo;<>;;', {syntax: 'js'});
        }).to.throw(Error, 'Parsing error: Unexpected token (line: 1, column: 10).');
      });

      it('removes redundant semicolons', () => {
        const report = fixText('let foo;;;', {syntax: 'js'});
        expect(report).to.equal('let foo;\n');
      });
    });
  });
});

Library use must not depend on style of coding.

Library use must not depend on style of coding.

100% agree. But it seems as though some of that nesting is superficial?

Define "superficial" in the context of this code example.

Hope I'm not stepping on your toes here. Perhaps style was the wrong choice of word. It just seems some of the extra nesting was rather deliberate.
context('invalid syntax', () => {
    it('throws an error', () => {
        expect(() => {
            fixText('let foo;<>;;', {
                syntax: 'js'
            });
        }).to.throw(Error, 'Parsing error: Unexpected token (line: 1, column: 10).');
    });
});

Until you introduce a second spec that falls under that context, it could be rewritten as:
it('throws an error given invalid syntax', () => {
    expect(() => {
        fixText('let foo;<>;;', {syntax: 'js'});
    }).to.throw(Error, 'Parsing error: Unexpected token (line: 1, column: 10).');
});

Furthermore,
// Your suggestion:
describe(['utilities', 'fixText'], () => {});
describe(['utilities', 'fixFiles'], () => {});
describe(['utilities', 'lintText'], () => {});
describe(['utilities', 'lintFiles'], () => {});

// Could be written as:
describe('utilities.fixText', () => {});
describe('utilities.fixFiles', () => {});
describe('utilities.lintText', () => {});
describe('utilities.lintFiles', () => {});

The array syntax didn't seem to improve the original example much. And its benefits are pretty limited in scope. It only helps at eliminating nesting when a describe/context has at most a single child context.
// Single child
// Will eliminate one nested call

describe('utilities', () => {
  describe('fixTextt', () => {
    it('spec', () => {});
  });
});

describe(['utilities', 'fixText'], () => {
  it('spec', () => {});
});

// Multiple children
// Can't help at all

describe('utilities', () => {
  describe('fixText', () => {
    it('spec', () => {});
  });

  describe('fixFiles', () => {
    it('spec', () => {});
  });
});

Until you introduce a second spec that falls under that context, it could be rewritten as:
Thats nonsense:

it is used to describes an expectation and must not include context.
context is used to describes context and must not include expectation.

Furthermore,

The two achieve different result. Depending on the output style, when you write test cases such as:
describe('utilities', () => {
    describe('fixText', () => {
        // ...
    });
});

describe('utilities', () => {
    describe('fixFiles', () => {
        // ...
    });
});

the output will be grouped as:
utilities
    fixText
        ...
    fixFiles
        ...

Using:
describe('utilities.fixText', () => {
    // ...
});

describe('utilities.fixFiles', () => {
    // ...
});

will achieve no such thing.

it is used to describes an expectation and must not include context.
context is used to describes context and must not include expectation.

RSpec guidelines also suggest:

When describing a context, start its description with "when" or "with".

I don't think either of us are following that :)

the output will be grouped as:

That isn't default behavior though?
describe('utilities', () => {
    describe('fixText', () => {
        it('spec');
    });
});

describe('utilities', () => {
    describe('fixFiles', () => {
        it('spec');
    });
});

With both parent describes in the same file, or different files, the output is not grouped by default. This is the same behavior as you showed in the mocha output of the original post.
$ mocha test1.js test2.js

  utilities
    fixText
      - spec

  utilities
    fixFiles
      - spec

Anyway, going back to the proposed solution. it optimizes for a very limited subset of cases: suites with only a single nested suite. I don't see it being included in mocha core as a result. But it would be easy to either write an extension to the UI (feel free to add it to the wiki if so!) or monkeypatch mocha during your test suite bootstrap.
// In your bootstrap file
_describe = describe;

function monkeypatch() {
  describe = context = function(title, fn) {
    if (!(title instanceof Array)) {
      return _describe(title, fn);
    }

    var i = 0;
    var recurse = function() {
      if (i + 1 === title.length) {
        return _describe(title[i], fn);
      }

      describe(title[i++], recurse);
    };

    recurse();
  };
}

function restore() {
  describe = _describe;
}

monkeypatch();

// Your test suite
describe(['utilities', 'lintFiles', 'no file paths'], () => {
  it('spec');
});

// Results
$ mocha test.js

  utilities
    lintFiles
      no file paths
        - spec


Merge histories with Cornelius's Hyper fork

@corneliusroemer I guess they can't be merged because of the restriction that all commits be signed. Did you turn that off on your fork?

What can't be merged? The conflicts?

@corneliusroemer Sorry, the conflicts appeared after I left that comment. Those are manageable, but the other issue is the commits in this branch authored by you are not signed (contrast with Dependabot's commits which are signed and display the green "verified" badge; in order to merge all commits must have the green verified badge):

I think I can always sign them myself. But in case you want to sign your own commits, these were the instructions I followed, fairly simple process, just about configuring a gpg agent and git to work together on your local machine: https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification#gpg-commit-signature-verification

@corneliusroemer I ended up having to rebase and make some slight conflict resolutions as well as sign the commits. But the changes you made will be very helpful, thanks!


ANY TITLE

NOT REQUIRED

/agent-action your query here

/agent-action your query here

/agent-action help with math

/agent-action help with math


Sometimes Outline shows incorrect information about queries from sql editor on frequent changes in a script

Description
I can't reproduce it easily but you can copy-paste and move simple queries many times and quickly.
Notice what Outline shows.
After some time it will show incorrect data (in my case, one of the query is not shown).
DBeaver Version
Community Edition <IP_ADDRESS>407122322
Operating System
Windows 10
Database and driver
PostgreSQL 16
PostgreSQL JDBC Driver 42.7.2
Steps to reproduce
https://github.com/user-attachments/assets/397b2ec0-12b8-4e79-b926-88f9d133b430
Additional context
No response

Thank you for bug report.


Processed files not found in results

eg:
  {
   "name": "Pannawonica",
   "processed_date": "2023-07-30T08:24:06.289758",
   "announced": false,
   "announced_date": null,
   "address_count": 372
  },

No file in output results/WA/pannawonica.geojson
Apart from the zero-address suburbs, this looks like a single GHA run failed
    for state, suburb_list in suburbs.read_all_suburbs().items():
        for s in suburb_list:
            file_generated = geojson.get_geojson_file_generated_from_name(s.name, state)
            if file_generated is None:
                print(state, s.name, 'MISSING')

# zero addresses
QLD Barwidgi MISSING
QLD Lumholtz MISSING
QLD Waverley MISSING
QLD West Wellesley Islands MISSING
SA Abminga Station MISSING
WA Balla Balla MISSING
WA Dundas MISSING
# missing
WA Ora Banda MISSING
WA Orange Springs MISSING
WA Orchid Valley MISSING
WA Ord River MISSING
WA Osmington MISSING
WA Pallinup MISSING
WA Palmdale MISSING
WA Palmer MISSING
WA Pannawonica MISSING
WA Paraburdoo MISSING
WA Paradise MISSING
WA Parker Range MISSING
WA Parkeston MISSING
WA Parryville MISSING
WA Paulls Valley MISSING
WA Paynedale MISSING
WA Paynes Find MISSING
WA Peaceful Bay MISSING
WA Peedamulla MISSING
WA Peerabeelup MISSING
WA Pemberton MISSING
WA Perillup MISSING
WA Peron MISSING
WA Perup MISSING
WA Petrudor MISSING
WA Piawaning MISSING
WA Pickering Brook MISSING
WA Picton MISSING
WA Picton East MISSING
WA Piesse Brook MISSING
WA Piesseville MISSING
WA Pindar MISSING
WA Pingaring MISSING
WA Rocklea MISSING
WA Rockwell MISSING
WA Rocky Gully MISSING

I'll reprocess them manually now, and add them to the NBN-date PR (which has too much in it already)

Added to https://github.com/LukePrior/nbn-upgrade-map/pull/221/commits/6c33fd323a139696caeb3066ebb60011732edfa0

Fixed


Included Build, tests, fixed few bugs

Formatted code as per Google Style
Included unit tests & Cloud build file
Fixed issues - NPE when COUNT using MapReduce and Error while querying an empty table

/gcbrun


[core] allow cofiguring throttlingRetryPolicy max retries

~Should we support exponential backoff retry for throttlingRetryPolicy?~
~Or we might just merge 429 to the retriable status codes in exponentialRetryPolicy and remove throttlingRetryPolicy. Note current throttlingRetryPolicy supports custom handler though so users could provide their own retry logic.~
~We should allow multiple retries for 429 by porting https://github.com/Azure/ms-rest-js/pull/417~
We currently allow hard-coded 3 retries

cc @bterlson, @xirzec

I thought the purpose of throttling retry policy was that the service provided a retry-after header?

I thought the purpose of throttling retry policy was that the service provided a retry-after header?

I have the exact the same thought. Just want to ensure we have discussions on whether there are any improvements we could do.

we could support retry on 429 multiple times by porting https://github.com/Azure/ms-rest-js/pull/417

The only pending thing here is to configure the hard-coded retry attempt of 3 which will be done as part of #9569


Is there a way we can alter / add new fields

Hi,
Thanks for the library, and I like the flexibility it offers to make use any where. Good work.
Have one question which I didn't get or noticed in documentation or in the opened / closed issues. Some of them resembles but move a bit differently.
So the question is
Is there a way we can alter / add new fields to the comment form ?
Currently it is only a text area, and it looks only if the user is logged in we can get the necessary information. But I would like guests also to add comments so that they can enter a few more details like email, name etc.
EDIT :
Also a way to add dislikes :) .
Thank you

Unfortunately the plugin does not support altering or adding new fields to the comment form. We tried to implement the plugin so that it would suit the needs of majority and for this reason such customizations have been left out of the plugin.
Dislike, on the other hand, will be supported in the future as soon as we can find time to implement that. However, I don't believe that this is going to happen any time soon so feel free to implement the feature on your own and create a pull-request.


The Helm Chart is not published as Helm Chart

The current Helm Chart was not published on any Helm Chart repository, nor the git repository is not a Helm Chart repository. It makes the only way to install the helm chart is by cloning the Git repository and launching Helm using the Helm Chart folder as Helm Chart.

related https://github.com/elastic/apm-mutating-webhook/issues/6

Closing this issue as being duplicated and tackled in #6 .


Two Scroll to top Button appears

Describe the bug
In provide image on right bottom corner you can see two scroll to top button appears only one required.
To Reproduce
Steps to reproduce the behavior:

Go to any page
Scroll down little
See error

Expected behavior
only one button required.
Screenshots

already being fixed in a PR


aud claim might be an array

https://www.rfc-editor.org/rfc/rfc7519.html#section-4.1.3

In the general case, the "aud" value is an array of case-sensitive strings, each containing a StringOrURI value.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 19 (21.05%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 56.989%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

jwt/jwt.go
4
19
21.05%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
1741

Relevant Lines:
3055

💛  - Coveralls