Proxy support ?

Hello,
I have some trouble using the Grammarly VSCode extension on a host behind a corporate proxy.
Extension version: v0.23.6 Pre-Release / Preview
The extension is installed on a Linux host I access through the "Remote-SSH" extension.
On the remote host is installed a local proxy (CNTLM), which is configured in VSCode through the http.proxy configuration variable.
None of the values in the option http.proxySupport seem to be used by the extension, it only seems to retrieve the JS using a direct connection :
Ready!
[Error - 11:00:31 AM] Server initialization failed.
  Message: Request initialize failed with message: request to<EMAIL_ADDRESS>failed, reason: connect ETIMEDOUT <IP_ADDRESS>:443
  Code: -32603
[Error - 11:00:31 AM] Starting client failed
  Message: Request initialize failed with message: request to<EMAIL_ADDRESS>failed, reason: connect ETIMEDOUT <IP_ADDRESS>:443
  Code: -32603

Additional analysis :
After having checked /proc/<pid of the znck.grammarly-0.23.6/dist/server/index.node.js process>/environ, I can see the following environment variables are set :

http_proxy
HTTP_PROXY
https_proxy
HTTPS_PROXY
ftp_proxy
FTP_PROXY

Would it be possible for the extension to handle the proxy configuration ?
Thanks,
BR

Similar here
Ready!
[Error - 12:43:17 PM] Server initialization failed.
  Message: Request initialize failed with message: request to<EMAIL_ADDRESS>failed, reason: self signed certificate in certificate chain
  Code: -32603
[Error - 12:43:17 PM] Starting client failed
  Message: Request initialize failed with message: request to<EMAIL_ADDRESS>failed, reason: self signed certificate in certificate chain
  Code: -32603

Similar here
Ready!
[Error - 16:42:55] Server initialization failed.
  Message: Request initialize failed with message: request to<EMAIL_ADDRESS>failed, reason: socket hang up
  Code: -32603
[Error - 16:42:55] Starting client failed
  Message: Request initialize failed with message: request to<EMAIL_ADDRESS>failed, reason: socket hang up
  Code: -32603

+1
I am also getting the same error on a Linux host running behind a corporate proxy.
[Error - 10:27:08] Server initialization failed.
  Message: Request initialize failed with message: request to<EMAIL_ADDRESS>failed, reason: connect ETIMEDOUT <IP_ADDRESS>:443
  Code: -32603
[Error - 10:27:08] Starting client failed
  Message: Request initialize failed with message: request to<EMAIL_ADDRESS>failed, reason: connect ETIMEDOUT <IP_ADDRESS>:443
  Code: -32603

This is a much-needed feature as it is otherwise unusable in a corporate environment...

Anyone can submit a PR?

Another user (on linux and in the company) seeing this error. What exactly changed in last few releases that we are observing this issue?


Join button in Upcoming Events section is dislocated [FEATURE]

Detailed description
The join button in the Upcoming Events section is dislocated, I want to resolve this issue, kindly assign me this issue.
Context
I want to resolve the issue by align the button on right place , It improve the UI of website
Possible implementation
No response
Additional information

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Where do you plan to fit the content placed in the top right section?

Where do you plan to fit the content placed in the top right section?

I just want to align  second join btn with the first btn

Alright, I have talked with our UI designer and if you want to make a ui change for the button make it something like this

at the bottom of the card

hey @HimanshuNarware do you still want to work on this issue or should i re-assign it?

@J-Harsh every time i try to install yarn it stuck

look up the documentation of yarn, and try installing it

look up the documentation of yarn, and try installing it

ok


Refine statement to make difference between different CNIs in azure-cni-overview.md

Users can be confused because customer prefer to believe these three CNIs works as same in the scope of network flow because they are all "Azure CNI".
For the fact check:

You can see even from different VNet, Pod IP is still act as src IP if using Pod subnet feature (dynamic IP allocation feature).

#sign-off


Fix Jupyter publisher ID in stable gallery files.

A repeat of this other PR, but for the RC1 branch. https://github.com/microsoft/azuredatastudio/pull/19144
I noticed that the Jupyter publisher ID was wrong in the .NET Interactive dependencies list. This doesn't affect install at all, which is why I didn't notice it before, but it does mean there won't be any extension dependencies listed for Interactive on its gallery page.

there is only updating the metadata of the extension, no need to go through the Ask mode process. I am merging it directly.


Cannot import a new application edition if the current user is not the manager of the app

If you try to import an existing application and the logged user is not the same as the manager of the application you get a Walkback. (Even when MonticelloLoader  appSuperGroupSetting: #world ) .
See attached stack trace:
Manager-stack.txt
Steps to reproduce:

Create and version an application with the same of some app to import (by default it will be managed by LibrarySupervisor) and change the privileges so superGroup = #world.
Create a new user and login with it
Configure  MonticelloLoader  appSuperGroupSetting: #world
Try importing a package that will end up in that application, and you will get something like: 'Base edition for BuoySUnitModel is managed by Supervisor. You are currently gcotelli and cannot create new editions of the application.'

It seems that the importer doesn't take into account the privileges, just check that the current user is the same as the application manager, even if the current user will have the required permissions to create and release editions in the app.

I did a few changes for supporting this.
If you evaluate this:
aTonelLoader settings appSuperGroupSetting: #world

It will honor the SuperGroup setting of the application when checking privileges, and also set the newly created edition with the setting defined in the TonelLoader or the previously existing setting if it's absent in the setting.

Hi @gcotelli, we're doing a cleanup pass on pending issues and this seems already solved.
Did you try loading from a Tonel repository with the above mentioned setting?


Some Issues with Youtube Videos Playing

Hi,
First of all, great work. Had been looking for something like this for a very long time. I have few requests for features and some issues that I am encountering while trying to play Youtube videos with this. So, will divide this post in two parts, requests and issues.
Requests:

In the readme file can you add some properties that are with this package and we can play with. Currently I am unable to find anything close to it.
Can you add full screen view option in the videos.
Can you add some identifier to the seek bar, like a bubble over the slider of seek bar.

Issues encountered:

Youtube videos don't have any volume. Tried on android simulator and real device as well, but volume doesn't seem working at all.
Very limited youtube videos are playing. Some videos that I tried and didn't worked are

https://www.youtube.com/watch?v=LKZcT-syexg
https://www.youtube.com/watch?v=UJWk_KNbDHo
https://www.youtube.com/watch?v=zc8hbSM1zVo

Looking forward to your response, mate.
Once again, keep up the good work.

Hi , Same issue is here. Youtube videos are playing but there are no sound coming.

D/        ( 7494): HostConnection::get() New Host Connection established 0x93277740, tid 7516
D/        ( 7494): HostConnection::get() New Host Connection established 0x82d2a540, tid 7640
I/cr_LibraryLoader( 7494): Using linker: org.chromium.base.library_loader.ModernLinker
E/BluetoothAdapter( 7494): Bluetooth binder is null
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
D/EGL_emulation( 7494): eglMakeCurrent: 0x932b5920: ver 3 0 (tinfo 0x911fe660)
D/        ( 7494): HostConnection::get() New Host Connection established 0x93318640, tid 7675
D/EGL_emulation( 7494): eglCreateContext: 0xa6e53380: maj 3 min 0 rcv 3
D/EGL_emulation( 7494): eglMakeCurrent: 0xa6e53380: ver 3 0 (tinfo 0x8512ddd0)
I/VideoCapabilities( 7494): Unsupported profile 4 for video/mp4v-es
W/cr_MediaCodecUtil( 7494): HW encoder for video/avc is not available on this device.
D/EGL_emulation( 7494): eglCreateContext: 0x933a1740: maj 3 min 0 rcv 3
D/EGL_emulation( 7494): eglMakeCurrent: 0x933a1740: ver 3 0 (tinfo 0x8512ddd0)
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
D/        ( 7494): HostConnection::get() New Host Connection established 0x93318440, tid 7665
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
I/zygote  ( 7494): NativeAlloc concurrent copying GC freed 17569(1226KB) AllocSpace objects, 28(964KB) LOS objects, 49% free, 3MB/7MB, paused 501us total 124.167ms
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 7494): Attempt to remove non-JNI local reference, dumping thread

Hi , Same issue is here. Youtube videos are playing but there are no sound coming.

@rahulairsky did any of these video links work for you?
https://www.youtube.com/watch?v=LKZcT-syexg
https://www.youtube.com/watch?v=UJWk_KNbDHo
https://www.youtube.com/watch?v=zc8hbSM1zVo

No, these are not playing

did anyone found a solution to it?????

Youtube audio issue fixed check version 0.0.3


Making ipfs.io gateway writable

0.3.9 was just released, and it carried @mildred + @cryptix's patch to make the gateway writable.
I would like to make ipfs.io/api offer a writable portion, so that applications can be built against that as they would any other web service. This is mostly a crutch until the protocol is deployed in end user browsers + devices. But it likely will be useful for a long time as that way systems with HTTP support can easily add things to IPFS.
Concerns:

how long to cache things (ideally should cache >10m, may be up to luck).
should rate limit uploads (per IP addr) to prevent DOSing the system. (prob something like 100MB?)
should have denylists in place

Once this is in place, things like IPFSBin and ipfs.pics could be just frontend webapps (+ pinning)

Question regarding this. If the content is only stored for 10m (or really, less than permanent), I'm not sure people are gonna be using this exclusively because they want to be able to make sure that the content stays on the site.
If I'm gonna be able to remove any IPFS daemon or backend from IPFSBin, I need to store content permanently, and it doesn't seem like this solves that really. Maybe I'm misunderstanding.
Pinging @cloutier (ipfs.pics) to have another opinion about this.

@VictorBjelkholm I may be wrong, but I suspect that the idea is that the gateway will only be used for getting content into the IPFS network, and then it's up to some other node to make sure it's stored permanently.

@VictorBjelkholm

write through ipfs.io
pin with a pinning service (like openipfs, other ipfs-cluster things, etc)

need a way to force --pin=false for all ops on the gateway. another option is to blow out all pins periodically that are not from a special separate list.

@jbenet: need a way to force --pin=false for all ops on the gateway.

How would you like to set this? Config option oder flag on 'ipfs daemon' ?

@didiercf has made a working prototype of our backup system that pins every picture from our server to our local computers. Right now it requests hashes to our database, but it could be made to work directly with the ipfs api. It wasn't super high in our priority list, but if people are interested, we could release its source code sooner.
@VictorBjelkholm I think it would be a good idea to keep our nodes running anyway. It would be more resilient to keep them and use ipfs.io only as a failover.
@jbenet are you talking about an IP denylist or a content deny list? We have a list of hashes we banned. We could release that, maybe not as is (it would be a bit counterproductive) but maybe as a variant of the bloom filter. If multiple lists agree on a hash, ipfs could automaticaly refuse to store it. This could be abused a lot though.

@cloutier:
A bloom filter-only solution sounds scary. They should only be used as an optimization step before checking against actual hashes (which are expected to identify data uniquely, not just probabilistically).
An alternative to publishing a list of hashes for all censored content is to publish the hashes of the hashes. You are not pointing to the content directly but checking a known hash against the list is easy.

I would like to put https://github.com/jbenet/http2ipfs-web on ipfs.io -- what do we need to finish this issue? just enabling it?

I'd like to get #1917 and pin=false before making ipfs.io writable

@lgierth :+1:


Compilation instructions for one example platform

Suggestion: Could you add example commands to install the dependencies and get the binary compiled for a single example platform (e.g., some Ubuntu LTS version)? Just something like:
"Under Ubuntu 18.04, you could install the required dependencies with: apt-get install ...".
I would really like to give gproshan a try for our research, but I am not an expert in building C/C++ applications and I spend hours trying to compile it and have not succeeded yet. I tried different Linux versions, but there always seems to be some library or compiler version wrong, a dependency missing, or whatever.

We will add some guides to install the dependencies.
You can install them with sudo apt-get install libarmadillo-dev libeigen3-dev libopenblas-dev libsuitesparse-dev freeglut3-dev libgles2-mesa-dev cimg-dev libcgal-dev it must work.
The current code need cuda >= 10.1 and g++ >= 8, if not you can get some errors.

Readme updated.

Thanks a lot, it worked fine after that under Ubuntu 19.04.
(On a fresh install, one will have to add build-essential and cmake to the list of dependencies, but that's quite obvious and not the hard part. Just to let others who may come here know.)


fix: Wrong STS audience in OIDC provider in China partition

Description
Change STS Audience service endpoint to point to the correct partition.
Motivation and Context
When deploying EKS cluster in china partition you have to specify the following variable because the EKS have amazonaws.com not amazonaws.cn  dns_suffix:
cluster_iam_role_dns_suffix = "amazonaws.com"

Unfortunatelly, this variable is also used to determine STS Audience in OIDC provider when IRSA is enabled.
The correct STS endpoint in China partion is sts.amazonaws.com.cn not sts.amazonaws.com and should not depend on cluster_iam_role_dns_suffix variable.
Breaking Changes
The OIDC provider will be forcfully replaced but because of the wrong STS audience it wasn't usable anyway.
How Has This Been Tested?

[ ] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[ ] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

I believe what we have is correct - you can see the history here:

https://github.com/terraform-aws-modules/terraform-aws-eks/issues/1904
https://github.com/terraform-aws-modules/terraform-aws-eks/pull/2026

@bryantbiggs I disagree. IMO #2026 introduced a bug. I've got multiple environments in China partition and the correct way is to have the following trust relationship for the cluster IAM role:
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "EKSClusterAssumeRole",
            "Effect": "Allow",
            "Principal": {
                "Service": "eks.amazonaws.com"
            },
            "Action": "sts:AssumeRole"
        }
    ]
}

and sts.amazonaws.com.cn in the audience in the OIDC provider.
They cannot have the same DNS suffix.
Thus, it is also required to this annotation to ServiceAccount:
eks.amazonaws.com/audience: "sts.amazonaws.com.cn"

Even if it is possible to use the sts.amazonaws.com audience and specify the corresponding annotation to ServiceAcount, the change introduced in #2026 is backward incompatible and will result in all Pods not being to authenticate to AWS for the time ServiceAccount's token is refreshed (also there would be a need to change all ServiceAcount manifests on the cluster).
Maybe it would be reasonable to introduce a separate variable for the default STS audience?


Must define unused DLL functions

Missing info on DLL functions.
I need to understand if DLL functions specifically targeting import or export functionality can be left out entirely in those plug-ins that won't use them — i.e. if these functions still require defining DLLProcedures that do nothing, or if they can simply be omitted since PM wouldn't try to call them after having acknowledged the plug-in supported features via the registration functions.
For example, an import plug-in shouldn’t expect any calls to beginWrite() or
writeNextImage(), and an export plug-in shouldn’t expect any calls to getTransparentColor() or isAlphaEnabled().
For more info, see also:

Cosmigo Forum » HELP: More File I/O Interface Clarifications
tajmone/pmotion-purebasic#2

Yes, the check functions should be optimized. At the moment these functions must be there. We could change this with V7.3 to and make them to be required conditionally.


adding set_default_xd_interp() methods for ReversibleEnergyStorage and adding Altrios battery maps

@calbaker here's my earlier teams message copied here:
here's the pr for the battery maps/corresponding methods. I added an example for how to use the methods to the demo_bev.py file, so you can play around with that if you want to convince yourself that it works as intended. I didn't add any tests on the rust side -- just confirmed on the python side that the methods worked, but I can add those tests if you'd like (the only rust test I can think of would be confirming that the res fields are updated as desired, but that can be easily checked by running the method in python as in the example I wrote). In order to store the default values, I created an efficiency_values.rs file with some constants stored, since the arrays get pretty big and I didn't want them gunking up the reversible_energy_storage.rs file. I also added a prepare_eff_values.py file to the same folder (wasn't sure where to add it), since I wanted to document how to transition the Altrios arrays to fastsim -- they needed to be transposed in a specific way to work given how the arrays in the interpolator need to be structured. That file can be moved or gotten rid of if desired. Finally, for some reason when I run sh build_and_test.sh I am getting the following failed test:

  assert t_fsim2_mean / t_fsim3_no_save_mean > min_speed_ratio_si_none, \

        f"`min_speed_ratio_si_none`: {min_speed_ratio_si_none:.3G}, achieved ratio: {(t_fsim2_mean / t_fsim3_no_save_mean):.3G}"

E       AssertionError: min_speed_ratio_si_none: 4, achieved ratio: 3.8
E       assert (0.0006711803337869545 / 0.00017681933301597988) > 4.0
python/fastsim/tests/test_speedup.py:138: AssertionError
=================================================================================================== short test summary info ===================================================================================================
FAILED python/fastsim/tests/test_speedup.py::test_conv_speedup - AssertionError: min_speed_ratio_si_none: 4, achieved ratio: 3.8
so in short: the methods seem to work, and the altrios battery maps are added. However, I'm getting one failed test and I'm not sure why. The test doesn't seem to affect compilation or the ability of the methods to work on the python side

@robinsteuteville To resolve merge conflicts, you probably just need to delete the .subtrees folder in this branch and re-merge the lastest fastsim-3 changes. There may be some minor other changes to address but they shouldn't be difficult.

@robinsteuteville To resolve merge conflicts, you probably just need to delete the .subtrees folder in this branch and re-merge the lastest fastsim-3 changes. There may be some minor other changes to address but they shouldn't be difficult.

@robinsteuteville , FYI, you had deleted a single file in the ./.subtrees/ folder, but the whole folder should have been deleted, and merging fastsim-3 into this branch took care of that, except for the conflict created by your deletion of the single file, which I've now fixed.  Merge conflicts usually should be resolved by pulling from the upstream branch (fastsim-3) rather than repeating the operation that was performed in that branch independently in your working branch.

@robinsteuteville , since I fixed the conflicts, is this now ready for review?

@robinsteuteville , since I fixed the conflicts, is this now ready for review?

@calbaker Last time we checked in about this, you were going to think some things through and perhaps change some things related to how the code was structured. If you've thought things through and feel it is good to go, then yes.


Tensorflow 2 update

Do the unit tests over in candidate_models still pass with these changes? https://github.com/brain-score/candidate_models/blob/bd545585ba5ccf16c80f8cb3a1f83ca874c6c8e3/tests/test___init__.py#L162-L173 If yes, then it looks good to me.
(would probably be preferable to move precomputed-feature versions of those tests into this repository)


Define a ParseShares API

Context
celestia-node currently parses shares depending on the type of share (see here). Universal share encoding should enable us to expose one API where any type of share can be parsed. As a result, it may be possible to stop exporting
https://github.com/celestiaorg/celestia-app/blob/f67bb6ba30e1d4886c5248efef12df5a7b6d5173/pkg/shares/share_merging.go#L125
https://github.com/celestiaorg/celestia-app/blob/f67bb6ba30e1d4886c5248efef12df5a7b6d5173/pkg/shares/share_merging.go#L78
https://github.com/celestiaorg/celestia-app/blob/f67bb6ba30e1d4886c5248efef12df5a7b6d5173/pkg/shares/share_merging.go#L95

I still think we will need to export these functions, but also expose a ParseShares api. Perhaps something like this.
type ShareSet [][]byte

func ParseShares(shares [][]byte) []ShareSet

then we can parse depending on namespace

Does this proposal imply an additional mechanism to convert from []ShareSet => coretypes.Messages, coretypes.Txs, or coretypes.EvidenceData?
Is the type ShareSet meant to describe that shares in this set are of a particular type. In other words, all share in this ShareSet are coretypes.Txs?

One alternative proposal that comes to mind:
func ParseShares(shares [][]byte) (coretypes.Messages, coretypes.Txs, coretypes.EvidenceData, error)

However this has the disadvantage that the return signature must be updated if/when we introduce more types.

ParseShares should perform only the universal shares parsing logic, which means splitting up some set of data using only the namespace and the message start byte.
Now we have some universal and purposefully ambiguous (potentially called a ShareSet) data that we can do something with. If we're celestia-node, and we just want to serve some complete set of shares, then we can do that, if we actually want to parse the shares into a data structure, then we can do that using the namespace and the version portion of the info byte.

If we are wanting to parse the entire square into block data, then we already have the Merge function to do that.

ParseShares should perform only the universal shares parsing logic, which means splitting up some set of data using only the namespace and the message start byte.

Agreed. How about?
// ShareSequence represents a contiguous sequence of shares that are part of the
// same namespace and message. For compact shares, one share set exists per
// reserved namespace. For sparse shares, one share sequence exists per PFD.
type ShareSequence struct {
	ID     namespace.ID
	Shares []NamespacedShare
}

func ParseShares(shares [][]byte) []ShareSequence {
	// TODO
	return []ShareSequence{}
}

I don't have any qualms with using word sequence over set, but why use NamespacedShares and namespace.ID? isn't one of our goals to get rid of NamespaceShares? #721
In the past this has just felt like fighting the type system with middleware.

sequence over set

Sounds good. I opted for sequence to indicate that the order of the shares in this struct are important and I think set conveys lack of ordering.

isn't one of our goals to get rid of NamespaceShares?

Sorry I forgot about #721 but just commented there. I'm not strongly opinionated on keeping vs removing the NamespaceShares type. If we remove, we can definitely remove NamespaceShares from the ShareSequence struct and use []Share instead.

Opted to remove the NamespaceShares type so I updated the proposed API in https://github.com/celestiaorg/celestia-app/issues/723#issuecomment-1252518254
The implementation of this API should split the provided shares into sequences based on the last bit in the info byte (a.k.a the message start indicator). Note: its possible to rename message start indicator to sequence start indicator given this API is public and "sequence start" is more precise given this applies to non-message shares.


Minor documentation issue: unclear docstring in Scipy's minimize

Docstring of scipy_optimizer's minimize method is unclear: parameters initialize and initialize_optimizer have identical explanations.
See: https://github.com/GPflow/GPflow/blob/develop/gpflow/training/scipy_optimizer.py#L75
        :param initialize: If `True` model parameters will be re-initialized even if they were
            initialized before for gotten session.
        :param initialize_optimizer: If `True` model parameters will be re-initialized even if they were
            initialized before for gotten session.

Happy to fix it, once I understand their correct usage.

I propose we close this issue as in gpflow2/tf2 the whole thing is a lot easier... objections?


Link to example code broken

Commit 560ef6856d8b ("example: remove examples from this repo") removed the example code.
This broke the links in README section "How can I use it ?"

Duplicate of #63?


Cast to float before aggregation

PostgreSQL / GreenPlum doesn't cast integers to float before aggregation. This could lead to incorrect results.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (6f92ccb) to head (f66ca6b).
Report is 40 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #93   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           13        13
  Lines          958       958
=========================================
  Hits           958       958

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fix fish support

Although fish-shell support was implemented in https://github.com/kislyuk/argcomplete/pull/260, I think some parts are wrong.

Probably if-condition for _ARC_DEBUG in shell_integration.py is reversed

It seems to output to /dev/null when _ARC_DEBUG is set.

Fish Support section in README.rst is different from comments in register-python-argcomplete

README

register-python-argcomplete --shell fish ~/.config/fish/completions/my-awesome-script.fish

register-python-argcomplete

register-python-argcomplete --shell fish my-favourite-script.py > ~/.config/fish/my-favourite-script.py.fish

@kislyuk @volkov Could you please take a look? Thank you.

Looks good! There was bugs.

Looks good! There was bugs.

I think there is some difference in bash and fish around this place
When I run echo test 8>&1 9>&2 1>/dev/null 2>&1 in fish I see test in console output.
When I run same command in bash there is no output.

I think there is some difference in bash and fish around this place
When I run echo test 8>&1 9>&2 1>/dev/null 2>&1 in fish I see test in console output.
When I run same command in bash there is no output.

The changes look correct to me. set -q returns the number of queried variables that were undefined, i.e. a return code of 0 means the variable was defined. I'm not able to reproduce the issue @volkov is seeing; echo test 8>&1 9>&2 1>/dev/null 2>&1 correctly outputs nothing for me (fish version 2.7.1).

The changes look correct to me. set -q returns the number of queried variables that were undefined, i.e. a return code of 0 means the variable was defined. I'm not able to reproduce the issue @volkov is seeing; echo test 8>&1 9>&2 1>/dev/null 2>&1 correctly outputs nothing for me (fish version 2.7.1).

Thanks for the PR!

Thanks for the PR!

I'm not able to reproduce the issue @volkov is seeing; echo test 8>&1 9>&2 1>/dev/null 2>&1 correctly outputs nothing for me (fish version 2.7.1).

Look's like it's only 3.1.2 feature (or bug), also can't reproduce on 2.7.1, report it as https://github.com/fish-shell/fish-shell/issues/7646

I'm not able to reproduce the issue @volkov is seeing; echo test 8>&1 9>&2 1>/dev/null 2>&1 correctly outputs nothing for me (fish version 2.7.1).

Look's like it's only 3.1.2 feature (or bug), also can't reproduce on 2.7.1, report it as https://github.com/fish-shell/fish-shell/issues/7646

Thanks for reporting that issue @volkov, if it turns out more changes are required in argcomplete, feel free to open a new issue and/or PR to address it.

Thanks for reporting that issue @volkov, if it turns out more changes are required in argcomplete, feel free to open a new issue and/or PR to address it.

It looks like this issue may not be fixed any time soon in fish, so in the meantime you could choose to use the tempfile-based IPC mechanism we included for Git Bash on Windows: https://github.com/kislyuk/argcomplete/blob/9e2c6712c761d05f64f4d558a381d9be9fa13988/README.rst#git-bash-support

It looks like this issue may not be fixed any time soon in fish, so in the meantime you could choose to use the tempfile-based IPC mechanism we included for Git Bash on Windows: https://github.com/kislyuk/argcomplete/blob/9e2c6712c761d05f64f4d558a381d9be9fa13988/README.rst#git-bash-support


subprocess_test: gracefully handle rlim.rlim_cur < kNumProcs

Instead of expecting that the number of open files is well above kNumProcs, simply "skip" the test in that case, still printing the message about the test limit (adding the current system limit too).
Theoretically, the SubprocessTest.SetWithLots test could be re-enabled on Mac OS X (whose soft file limit is less than 1025, according to the comment), but I don't have a Mac OS X system to test.

Ah I see you CI passes --gtest_filter=-SubprocessTest.SetWithLots to ninja_test, which I guess could be dropped once this patch is in...

You can try modifying .travis.yml to remove that flag in this branch (I'm not sure if it'll work!).

Current, running tests doesn't produce any output (except on Windows), which I think is a nice property. So I wouldn't reenable the test on OS X, and also wouldn't change .travis.yml.
(But this change looks fine to me as-is, I can merge it as-is if you want.)

(But this change looks fine to me as-is, I can merge it as-is if you want.)

Yes please.

Done, thanks for the patch.


Update the JS template to correctly handle idempotency key when undefined

Better fix of #273

Fixed by https://github.com/svix/svix-webhooks/pull/277


-p isn't mentioned anywhere

An example shows you can use -p to set the build parameter, but it's not mentioned in the top section of parameters.

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

ID: 910cd365-d63a-00dc-417c-db017f83bf6f
Version Independent ID: 5e495ddd-140e-de5c-a793-d4a9f88be51e
Content: dotnet build command - .NET Core CLI
Content Source: docs/core/tools/dotnet-build.md
Product: dotnet-core
Technology: dotnet-cli
GitHub Login: @mairaw
Microsoft Alias: mairaw

Hi @3686,
The possibility of passing MSBuild parameters is mentioned here:
https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-build#msbuild
I can just add a clarification to the example introduction that this is using a MSBuild option.


Not all water sources have a delay when drinking from them

Description

Example, you can drink from a bucket, or a hydroponics bay with no delay.
Screenshots

Additional context

Probably fixed in https://github.com/space-wizards/space-station-14/pull/6406

Closing, appears to be fixed by #6406 (tested bucket for example, has delay now)


Doesn't read body parameters

Is there any way to get the body parameters to get into the api doc automatically?

you mean the request's body, like some JSON data?
If so, you'd need to make requests with the data in order to include them. I myself have automatic unit tests to do just that: https://github.com/sarpik/turbo-schedule/tree/master/server/src/test

Yes, i ment raw json data in the body. I have made requests with raw json in body, but they don't seem to appear in the docs. Am i not sending the data correctly?

It is possible that the midlewares chain is broken somewhere, could you please check this comment.
Please reopen the issue if it doesn't solve the problem.


[HUDI-5469] Hive doesn't respect the space at the end of partition path, so remove it to avoid dupl…

…icate keys error
Change Logs
let's say there are two partition paths:

"partition_path"
"partition_path "

the second one has a space at its end, the HMS will throw an error when doing hive sync since HMS treats them as the same
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry 'partition_path' for key 'UNIQUEPARTITION'
Impact
no
Risk level (write none, low medium or high below)
low
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[x] Read through contributor's guide
[x] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@fengjian428 : Thanks a lot for the contribution. We think making changes to user data inside Hudi should not happen. Happy to hear thoughts otherwise.

Closing this PR.


Add new school

http://www.licmcostin.ro/

@iacobeduard Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Does the EVA2.0 dataset overlap with the LCCC dataset? If so, what percentage?

Does the EVA2.0 dataset overlap with the LCCC dataset? If so, what percentage? I am curious about this. Could anyone tell me? Thanks!

EVA2.0 dataset contains LCCC dataset. LCCC dataset accounts for 20%.

Understood. Thanks!

Correction:  about 3% (20%)


Error attempting to install on rpi based OpenMediaVault

Hi
I was hoping to get this to run on my OMV server as it looks like a superb piece of work!
However if I do it via your image in the docker run command in the readme: muppet3000/growatt-charger:latest I receive:
Status: Downloaded newer image for muppet3000/growatt-charger:latest WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm/v8) and no specific platform was requested
And if I attempt it via the DockerFile in this repo via a git clone, I receive the following error: when it attempts to build the cffi package.
gcc -pthread -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DFFI_BUILDING=1 -DUSE__THREAD -DHAVE_SYNC_SYNCHRONIZE -I/usr/include/ffi -I/usr/include/libffi -I/usr/local/include/python3.11 -c c/_cffi_backend.c -o build/temp.linux-aarch64-cpython-311/c/_cffi_backend.o             c/_cffi_backend.c:15:10: fatal error: ffi.h: No such file or directory                15 | #include <ffi.h>                   |          ^~~~~~~             compilation terminated.             error: command '/usr/bin/gcc' failed with exit code 1
I assume that both of these are due to it running on a RPi4 (armv8 not aarch64)?
Anyway just wondering if you had encountered this, and had any quick way of fixing or whether this is likely to be a big rabbit hole!?
Best wishes and thanks for the excellent work!
Jim

Hi @jimwormold thanks for reaching out. You're right, this is down to the fact you're running on an RPI. I haven't run into this issue because I've always run this on fully-fledged Linux VMs.
When you attempted to build from the dockerfile did you remember to change the FROM line here so that it uses an ARM python image? e.g. FROM arm64v8/python:3-slim
Assuming you are using an ARM image, the specific error you're getting is a compilation error (I assume it happens during one of the apt steps) it looks like it's missing a dependency file which implies the dependencies aren't 100% aligned between the amd64 image and the arm image.
Based on this if you add libffi-dev after gcc on line 6 then you should have what you need to continue.
Good luck, let me know how you get on, bonus points if you share the Dockerfile with me afterwards to I can add it to this repo.

Hah! Completely missed that! Yes it runs perfectly now after trying out a few python images until one worked ...
FROM arm32v7/python:3.7-slim-buster

COPY requirements.txt /tmp/

RUN apt-get update && \
    apt-get install -y gcc libffi-dev && \
    pip install -r /tmp/requirements.txt && \
    rm /tmp/requirements.txt && \
    apt autoremove -y gcc && \
    apt-get clean

RUN mkdir /opt/growatt-charger

COPY defaults /opt/growatt-charger/defaults
COPY bin /opt/growatt-charger/bin

VOLUME /opt/growatt-charger/conf
VOLUME /opt/growatt-charger/output
VOLUME /opt/growatt-charger/logs

ENTRYPOINT ["/opt/growatt-charger/bin/growatt-charger.py"

Excellent job and thanks for the swift help.


pre-commit-make-rst git hook generates warnings and errors related to the limboai documentation

This is a minor issue but thought I'd report it.
The following warnings and errors will ensue when pre-commit-make-rst executes:
Running hook: pre-commit-make-rst
Checking for errors in the XML class reference...
Generating the RST class reference...
WARNING: Blackboard.xml: Found a code string "p_key" that matches one of the parameters in method "has_var" description.
WARNING: BTAction.xml: Found a code string "BTAction" that matches one of the known classes in class "BTAction" description.
ERROR: BTCheckTrigger.xml: Unresolved member reference "blackboard" in property "variable" description.
WARNING: BTCondition.xml: Found a code string "BTCondition" that matches one of the known classes in class "BTCondition" description.
WARNING: BTPlayer.xml: Found a code string "p_status" that matches one of the parameters in signal "behavior_tree_finished" description.
WARNING: BTPlayer.xml: Found a code string "p_status" that matches one of the parameters in signal "updated" description.
WARNING: BTRandomWait.xml: Found a code string "min_duration" that matches the BTRandomWait.min_duration member in class "BTRandomWait" description.
WARNING: BTRandomWait.xml: Found a code string "max_duration" that matches the BTRandomWait.max_duration member in class "BTRandomWait" description.
WARNING: BTTask.xml: Found a code string "BTTask" that matches one of the known classes in class "BTTask" description.
WARNING: BTTask.xml: Found a code string "custom_name" that matches the BTTask.custom_name member in property "custom_name" description.
WARNING: BTTask.xml: Found a code string "p_child" that matches one of the parameters in method "add_child" description.
WARNING: BTTask.xml: Found a code string "p_child" that matches one of the parameters in method "add_child_at_index" description.
WARNING: BTTask.xml: Found a code string "p_idx" that matches one of the parameters in method "add_child_at_index" description.
WARNING: BTTask.xml: Found a code string "p_child" that matches one of the parameters in method "has_child" description.
WARNING: BTTask.xml: Found a code string "p_task" that matches one of the parameters in method "is_descendant_of" description.
WARNING: BTTask.xml: Found a code string "p_task" that matches one of the parameters in method "is_descendant_of" description.
WARNING: BTTask.xml: Found a code string "p_child" that matches one of the parameters in method "remove_child" description.
WARNING: LimboHSM.xml: Found a code string "p_event" that matches one of the parameters in method "add_transition" description.
WARNING: LimboHSM.xml: Found a code string "p_from_state" that matches one of the parameters in method "add_transition" description.
WARNING: LimboHSM.xml: Found a code string "p_to_state" that matches one of the parameters in method "add_transition" description.
WARNING: LimboState.xml: Found a code string "p_event" that matches one of the parameters in method "add_event_handler" description.
WARNING: LimboState.xml: Found a code string "p_callable" that matches one of the parameters in method "call_on_enter" description.
WARNING: LimboState.xml: Found a code string "p_callable" that matches one of the parameters in method "call_on_exit" description.
WARNING: LimboState.xml: Found a code string "p_callable" that matches one of the parameters in method "call_on_update" description.
WARNING: LimboState.xml: Found a code string "p_event" that matches one of the parameters in method "dispatch" description.
WARNING: LimboState.xml: Found a code string "p_cargo" that matches one of the parameters in method "dispatch" description.

Steps to reproduce:

Install the git hooks at https://github.com/godotengine/godot/tree/master/misc/hooks in .git/hooks within the Godot repository.
Run git commit --verify

Thanks!


Font visibility

Describe the bug
Font cant be visible to read
To Reproduce
Steps to reproduce the behavior:

look at webpage to find issue

Expected behavior

Text should be displayed in a readable font style, size, and color that contrasts appropriately with the background. This ensures that users can easily perceive and comprehend the text content.

Screenshots

Desktop (please complete the following information):

windows
chrome

@Its-Aman-Yadav
please assign this issue to me.
Thank You!

After going through the website I realised the font of the website is not clearly visible and has font size issues.
I would love to contribute to this issue. Kindly assign it to me.

The font is not visible  properly making the website unattractive, good font visibility is essential in the website as it plays a crucial role I want to work on this issue kindly assign this issue to me

This was a technical issue, thank for considering it


ChannelFileSendWithComplex

What's a better way of doing this? Reflect? Generator? I'm open to suggestions

Just put an io.Reader as an arg in SendMessageParams? We don't need another complex method.

I would agree, but it uses a completely different request method, and content type.

Then message send complex needs to get a bit more complex :)
On Apr 30, 2017 9:39 AM, "legolord208"<EMAIL_ADDRESS>wrote:

I would agree, but it uses a completely different request method, and
content type.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bwmarrin/discordgo/pull/370#issuecomment-298242618,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABdVgotUQA4v3xqQjBGeEYF6kMeDvjzLks5r1LksgaJpZM4NMm4s
.

@iopred You mean detecting if file is set, and if so use a completely different method? o_o
Though, how would the name be set? Have a file struct?

We're likely to have a SetFile method on SendParams like we did on edit. So
I think it's fine to have Filename and FileReader on the params
On Apr 30, 2017 9:47 AM, "legolord208"<EMAIL_ADDRESS>wrote:

@iopred https://github.com/iopred You mean detecting if file is set,
and if so use a completely different method? o_o
Though, how would the name be set? Have a file struct?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bwmarrin/discordgo/pull/370#issuecomment-298243027,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABdVgrK55tnzgPCWd5bh6qHs-ahw_0Mfks5r1LsXgaJpZM4NMm4s
.

I'll see what I can do tomorrow

@iopred :bell:


Error when using @mention at people in the owner organization as external contractor

When invited to a Shared Channel in another tenant, the host tenant users can tag me in chats, mentions, and comments. When I try to mention them back (comment in Lists) I'm getting the error in the attached image

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

ID: 138ac890-8786-c6e6-db7e-1e90a94e6c9b
Version Independent ID: 138ac890-8786-c6e6-db7e-1e90a94e6c9b
Content: Shared channels errors in Microsoft Teams - Microsoft Teams
Content Source: Teams/shared-channels-errors.md
Service: msteams
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


Same post shown twice in the blog list

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[X] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
I noticed one of my blog posts showing twice in the main blog list. One time rightfully, the other time taking the spot of another post. I managed to get a minimal setup to reproduce it:

Reproducible demo
https://stackblitz.com/edit/github-bmgrpn
Steps to reproduce
From a fresh Docusaurus install, empty the blog folder and create the two folders and files that are in it now.
On the website, in the blog, there are two posts: Post 1 and Post 2. We can see them in the list of recent posts. However, Post 1 is not present in the main list, and Post 2 is present twice:

We also notice this React error in the console:
react-dom.development.js?ac89:67 Warning: Encountered two children with the same key, `/blog/post2`. Keys should be unique so that components maintain their identity across updates.

Note: it is still possible to build the site with yarn build, the error won't be present in the output.

Other observations:

Renaming any of the two blog post folders (simply changing one character) fixes the issue (it looks like hashes colliding, so I tinkered in docuHash in docusaurus-utils/src/hashUtils.ts but it didn't do anything conclusive).

Changing the 4th line of the Post 2 index.mdx file from tags: [tag] to tags: [] makes now Post 1 being present twice instead of Post 2:

Expected behavior
No duplicate post.
Actual behavior
See above.
Your environment

Public source code: https://stackblitz.com/edit/github-bmgrpn or https://github.com/Zwyx/docusaurus-bug-demo
Public site URL: N/A — building the site works, it's only when running in dev mode that the issue appears
Docusaurus version used: 2.2.0
Environment name and version (e.g. Chrome 89, Node.js 16.4): Chrome 108, Node 18.
Operating system and version (e.g. Ubuntu 20.04.2 LTS): Ubuntu 22.04.1 LTS

Self-service

[ ] I'd be willing to fix this bug myself.

Nice construction—we have a hash collision! The culprit is in this function:
https://github.com/facebook/docusaurus/blob/e8a07633ba033dbe456839e45fdcef30cfb62c08/packages/docusaurus/src/server/routes.ts#L66-L88
Here are two inputs and outputs:
[Arguments] {
  '0': '@site/blog/2022-11-18-bye-medium/index.mdx?truncated=true',
  '1': 'content',
  '2': '/blog'
} => content---blogc-99-485
[Arguments] {
  '0': '@site/blog/2019-10-05-react-nfc/index.mdx?truncated=true',
  '1': 'content',
  '2': '/blog'
} => content---blogc-99-485

I think we need to have to append an incrementing suffix to avoid collision.


Firestore plugin compilation fails because of missing header files

Bug report
I cannot compile macOS application using cloud_firestore 0.15.0 and latest master.
ld: warning: dylib (/Users/sma/Work/tellorium_poc/build/macos/Build/Products/Release/BoringSSL-GRPC/openssl_grpc.framework/openssl_grpc) was built for newer macOS version (10.12) than being linked (10.9)
/Users/sma/.pub-cache/hosted/pub.dartlang.org/cloud_firestore-0.15.0/macos/Classes/FLTFirebaseFirestorePlugin.m:8:9: fatal error: 'Private/FLTDocumentSnapshotStreamHandler.h' file not found
#import "Private/FLTDocumentSnapshotStreamHandler.h"
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
note: Using new build system
note: Building targets in parallel
note: Planning build
note: Constructing build description
** BUILD FAILED **

I checked the folder and the header file is indeed missing.
The previous version 0.14.4 did work.
Steps to reproduce
Steps to reproduce the behavior:

my flutter version:
 [✓] Flutter (Channel master, 1.26.0-2.0.pre.288, on macOS 11.1 20C69 darwin-x64, locale de-DE)
 [✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
 [✓] Xcode - develop for iOS and macOS (Xcode 12.3)
 [✓] Chrome - develop for the web
 [✓] Android Studio (version 4.0)
 [✓] VS Code (version 1.52.1)
 [✓] Connected device (2 available)

my pubspec.yaml includes:
 dependencies:
   cloud_firestore: ^0.15.0
   firebase_core: ^0.6.0

run flutter build macos

Expected behavior
It should successfully compile.
Additional info
contents of Private folder:
-rw-r--r--  1 sma  staff   401 13 Jul  2020 FLTFirebaseFirestoreReader.h
-rw-r--r--  1 sma  staff  1856 13 Jul  2020 FLTFirebaseFirestoreUtils.h
-rw-r--r--  1 sma  staff   396 13 Jul  2020 FLTFirebaseFirestoreWriter.h

headers included in FLTFirebaseFirestorePlugin.m:
#import "Private/FLTDocumentSnapshotStreamHandler.h"
#import "Private/FLTFirebaseFirestoreUtils.h"
#import "Private/FLTQuerySnapshotStreamHandler.h"
#import "Private/FLTSnapshotsInSyncStreamHandler.h"
#import "Private/FLTTransactionStreamHandler.h"

It looks like the above file is not the only one that is missing.

@sma  Please run "pod install" in the ios folder & try again.

@sma  Please run "pod install" in the ios folder & try again.

My project has only a macos folder. I have Cocoapods 1.10.1 installed. I ran pod install in macos but this changes nothing. Running flutter build automatically runs pod install, I think.
Here is the relevant portion of the Podfile.lock file that changed from since I used the previous version:
- cloud_firestore (0.15.0):
    - Firebase/CoreOnly (~> 7.3.0)
    - Firebase/Firestore (~> 7.3.0)
    - firebase_core
    - FlutterMacOS
  - Firebase/CoreOnly (7.3.0):
    - FirebaseCore (= 7.3.0)
  - Firebase/Firestore (7.3.0):
    - Firebase/CoreOnly
    - FirebaseFirestore (~> 7.3.0)
  - firebase_core (0.6.0):
    - Firebase/CoreOnly (~> 7.3.0)
    - FlutterMacOS
  - FirebaseCore (7.3.0):
    - FirebaseCoreDiagnostics (~> 7.0)
    - GoogleUtilities/Environment (~> 7.0)
    - GoogleUtilities/Logger (~> 7.0)
  - FirebaseCoreDiagnostics (7.3.0):
    - GoogleDataTransport (~> 8.0)
    - GoogleUtilities/Environment (~> 7.0)
    - GoogleUtilities/Logger (~> 7.0)
    - nanopb (~> 2.30906.0)
  - FirebaseFirestore (7.3.0):
    - abseil/algorithm (= 0.20200225.0)
    - abseil/base (= 0.20200225.0)
    - abseil/memory (= 0.20200225.0)
    - abseil/meta (= 0.20200225.0)
    - abseil/strings/strings (= 0.20200225.0)
    - abseil/time (= 0.20200225.0)
    - abseil/types (= 0.20200225.0)
    - FirebaseCore (~> 7.0)
    - "gRPC-C++ (~> 1.28.0)"
    - leveldb-library (~> 1.22)
    - nanopb (~> 2.30906.0)
  - FlutterMacOS (1.0.0)
  - GoogleDataTransport (8.1.0):
    - nanopb (~> 2.30906.0)
  - GoogleUtilities/Environment (7.1.1):
    - PromisesObjC (~> 1.2)
  - GoogleUtilities/Logger (7.1.1):
    - GoogleUtilities/Environment

I still think that the this folder https://github.com/FirebaseExtended/flutterfire/tree/master/packages/cloud_firestore/cloud_firestore/macos/Classes/Private is missing the private header files mentioned in my previous posting. Just compare it with https://github.com/FirebaseExtended/flutterfire/tree/master/packages/cloud_firestore/cloud_firestore/ios/Classes/Private which contains more files. Furthermore, the missing files where added 4 days ago I my guess is, you forget to commit them for the macos folder.

My project has only a macos folder. I have Cocoapods 1.10.1 installed. I ran pod install in macos but this changes nothing. Running flutter build automatically runs pod install, I think.
Here is the relevant portion of the Podfile.lock file that changed from since I used the previous version:
- cloud_firestore (0.15.0):
    - Firebase/CoreOnly (~> 7.3.0)
    - Firebase/Firestore (~> 7.3.0)
    - firebase_core
    - FlutterMacOS
  - Firebase/CoreOnly (7.3.0):
    - FirebaseCore (= 7.3.0)
  - Firebase/Firestore (7.3.0):
    - Firebase/CoreOnly
    - FirebaseFirestore (~> 7.3.0)
  - firebase_core (0.6.0):
    - Firebase/CoreOnly (~> 7.3.0)
    - FlutterMacOS
  - FirebaseCore (7.3.0):
    - FirebaseCoreDiagnostics (~> 7.0)
    - GoogleUtilities/Environment (~> 7.0)
    - GoogleUtilities/Logger (~> 7.0)
  - FirebaseCoreDiagnostics (7.3.0):
    - GoogleDataTransport (~> 8.0)
    - GoogleUtilities/Environment (~> 7.0)
    - GoogleUtilities/Logger (~> 7.0)
    - nanopb (~> 2.30906.0)
  - FirebaseFirestore (7.3.0):
    - abseil/algorithm (= 0.20200225.0)
    - abseil/base (= 0.20200225.0)
    - abseil/memory (= 0.20200225.0)
    - abseil/meta (= 0.20200225.0)
    - abseil/strings/strings (= 0.20200225.0)
    - abseil/time (= 0.20200225.0)
    - abseil/types (= 0.20200225.0)
    - FirebaseCore (~> 7.0)
    - "gRPC-C++ (~> 1.28.0)"
    - leveldb-library (~> 1.22)
    - nanopb (~> 2.30906.0)
  - FlutterMacOS (1.0.0)
  - GoogleDataTransport (8.1.0):
    - nanopb (~> 2.30906.0)
  - GoogleUtilities/Environment (7.1.1):
    - PromisesObjC (~> 1.2)
  - GoogleUtilities/Logger (7.1.1):
    - GoogleUtilities/Environment

I still think that the this folder https://github.com/FirebaseExtended/flutterfire/tree/master/packages/cloud_firestore/cloud_firestore/macos/Classes/Private is missing the private header files mentioned in my previous posting. Just compare it with https://github.com/FirebaseExtended/flutterfire/tree/master/packages/cloud_firestore/cloud_firestore/ios/Classes/Private which contains more files. Furthermore, the missing files where added 4 days ago I my guess is, you forget to commit them for the macos folder.

@sma yes that makes sense. I was relying on the CI to warn me. Will issue a PR asap. Thank you for reporting.
@Salakar FYI

@sma yes that makes sense. I was relying on the CI to warn me. Will issue a PR asap. Thank you for reporting.
@Salakar FYI

@sma yes that makes sense. I was relying on the CI to warn me. Will issue a PR asap. Thank you for reporting.
@Salakar FYI

Oh, I missed this as well, just needs relative symlinks creating in the macos folder for the missing files ln -s

@sma yes that makes sense. I was relying on the CI to warn me. Will issue a PR asap. Thank you for reporting.
@Salakar FYI

Oh, I missed this as well, just needs relative symlinks creating in the macos folder for the missing files ln -s

PR is up, with CI changes that should pick this up as well now in future 🙈
Waiting on CI and if all good then will do a release.

PR is up, with CI changes that should pick this up as well now in future 🙈
Waiting on CI and if all good then will do a release.

FYI: CI being broken has highlighted a couple of other issues, so the version to fix this is gonna have to be a major version as the new Firebase iOS SDK also has a new minimum deployment target for osx.

FYI: CI being broken has highlighted a couple of other issues, so the version to fix this is gonna have to be a major version as the new Firebase iOS SDK also has a new minimum deployment target for osx.


Output to stdout as json

I want to be able to use jtd-codegen as an part of a larger generator, right now you are dumping to a folder (at least in TS as an index.ts) which is not ideal.  Would like to have something like
jtd-codegen --typescript-out test req.json --log-format json --export-to-logs
Which would no write out files but the output would contain the results ala
{
  "TypeScript": {
    "out_dir": "test",
    "root_name": "Req",
    "definition_names": {},
    "output":"// Code generated by jtd-codegen for TypeScript v0.2.1\n\nexport type..."
}

While I agree this could be useful for many folks, I can't commit to doing this work, as it would require a pretty considerable change to how the generator works. That said, I am open to reviewing a PR that attempts to implement this.

Closing for triage purposes.


Set a minimum rust-version

Objective
Trying to compile Bevy on Rust 1.61 or below causes compile errors because deriving 'Default' on enums is experimental, which is confusing to users who don't realize that they need to update their toolchain to fix it.
Solution
Set rust-version = 1.62 so that Cargo gives a clearer error.

This is controversial because, as discussed in #288, we follow a "latest stable Rust" policy. I've made a prominent note in the readme in https://github.com/bevyengine/bevy/pull/4274, but perhaps we could do better.

Understandable, but there's a reasonable amount of users who get into Rust and Bevy at the same time, so I think it makes sense to make it clearer for them. (That said, I only noticed a handful of users on Discord get confused by the error, so maybe it's not that common.)
... also, I completely missed that message in the README, whoops. 😅 I haven't had reason to look at it in a while.

Understandable, but there's a reasonable amount of users who get into Rust and Bevy at the same time

I agree, but a) they typically just download the latest Rust and b) they won't know to look for an MSRV :)

b) they won't know to look for an MSRV :)

Cargo refuses to run if the local Rust version is not recent enough, with a more explicit message than the usual "hey you're using nightly features on stable"
Maybe we could have the field... but I would like to avoid PR just updating that field because another PR that introduce a dependency on a newer version of Rust forgot to update it. That would mean adding a job to CI actually checking that version

Error message like in https://github.com/bevyengine/bevy/issues/5520 is so confusing for someone not used to them

Is there really a need to worry about this on main?
I would expect this to affect people using bevy from crates.io the most and I don't see a downside to updating the rust-version to the latest stable before each Bevy release.
Maybe as a part of the automatic PR that bumps the version of all bevy crates.
It would be nice to add this to the 0.8.1 milestone.

If we add the field in the Cargo.toml, it's value must be true. Updating it only on release means it would sometimes be false on main, which is not good.

It's still possible to remove the line after release during development and adding it back with a new rust version just before releasing a new version.

Closing in favor of #6852, which automates this further.


Adding a new page is not seem by wagtail

I have added a new page to wagtail. I do not see this page in the editor even though I have migrated. Any insight on this would be great!

Hi @alan-unravel - please use the Google group for support queries.


Added multithreading test that hangs.

Added a unit test in order to reproduce a deadlock when executing synchronous SET and DEL commands concurrently. (You might argue why we do synchronous commands concurrently, but that's the nature of our applications at the moment). Anyways, this looks like a serious issue that needs fixing.
I have added some output files containing more information:
pstack.output: Contains the pstack output of the test_redox process after it deadlocks. From the thread stacks, it's clear that one thread (#2) deadlocks in a wait of the condition_variable (line 43 in command.cpp).
monitor.output: Contains the redis monitor output. This shows that the thread executing the SET commands executes to completion, but the thread executing the DEL command deadlocks.
redis.output: Contains the output of executing SET and DEL commands concurrently using redis-cli. This doesn't show a deadlock (as expected).
Executing the unit test reliably reproduces the deadlock on my machine.

It may be worth investigating/implementing (as an addition to a proper bugfix for this issue) a timeout while waiting for the redis result (use condition_variable::wait_for(...) instead of condition_variable::wait()?). Note I do not mean this as a proposed bug fix, but rather as an improvement on top of a proper bugfix.

I added a commit that fixes the issue in the unit test. An atomic variable was increased, but the value after increase wasn't stored, which may lead to multiple commands having the same id. By using fetch_add (which is used by the operators (++, --, etc.) of std::atomic<...>), the value after increase is stored and is unique for each command. I haven't checked for other usages of std::atomic<...> throughout the redox codebase, but there may be other places where similar issues occur.

Thank you for doing this! I unfortunately don't get to use redox in my job, and so haven't had time to make some long-needed improvements. I will review your change and look for other similar cases as soon as I can.

Hi Hayk,
Apparently bdallas and Collin Hockey have also run into some concurrency
problems, and uploaded a pull request. I suggest you take their pull request, as
it contains a similar fix for the command id and some other good fixes as well.
One thing I'd like to add to their pull request is the fact that by using
mutexes and locks to guard the access to some of the atomic variables, I think
those can be changed into regular non-atomic variables.
When do you think you can pull the changes from bdallas in? (I could work with a
temporary branch, but I prefer to wait until the changes have been merged into
your main branch).
Many thanks!
Kind regards,
Bram Veldhoen

Op 3 september 2015 om 18:25 schreef Hayk Martirosyan
<EMAIL_ADDRESS>Thank you for doing this! I unfortunately don't get to use redox in my job,
and so haven't had time to make some long-needed improvements. I will review
your change and look for other similar cases as soon as I can.
—
Reply to this email directly or view it on GitHub
https://github.com/hmartiro/redox/pull/25#issuecomment-137502997 .

Hi Bram, I am hoping to bring in these changes this week. Thanks for the suggestions.

Hey, check out https://github.com/hmartiro/redox/pull/27. I added your test and it passes in the branch. I will merge that in in a couple of days, letting you and bdallas take a look. Thanks. I did switch to non-atomic variables.
With regards to the wait_for, a synchronous command with a timeout could be a useful feature, I agree.


[Snyk] Upgrade @nguniversal/express-engine from 10.0.1 to 10.1.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @nguniversal/express-engine from 10.0.1 to 10.1.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 3 versions ahead of your current version.
The recommended version was released 3 years ago, on 2020-09-03.

Release notes

Package name: @nguniversal/express-engine

10.1.0 - 2020-09-03commit 3f841ef
Author: Keen Yee Liau<EMAIL_ADDRESS>Date:   Wed Sep 2 21:17:50 2020 -0700
release: v10.1.0

commit f92baae
Author: dependabot[bot] <49699333+dependabot[bot]@ users.noreply.github.com>
Date:   Wed Sep 2 17:35:00 2020 +0000
bl from 4.0.2 to 4.0.3.

Release notes
Commits

Signed-off-by: dependabot[bot] <support@github.com>">build(deps): bump bl from 4.0.2 to 4.0.3
Bumps bl from 4.0.2 to 4.0.3.

Release notes
Commits

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>
commit 09ae8c0
Author: Renovate Bot<EMAIL_ADDRESS>Date:   Wed Sep 2 16:51:20 2020 +0000
build: update karma to version 5.2.1

commit 132de1e
Author: Keen Yee Liau<EMAIL_ADDRESS>Date:   Thu Aug 27 10:42:25 2020 -0700
release: v10.1.0-rc.0

commit 756d0b1
Author: Alan Agius<EMAIL_ADDRESS>Date:   Thu Aug 27 10:08:22 2020 +0200
build: update Angular packages to 10.1.0-rc.0

commit 0eb7253
Author: Alan Agius<EMAIL_ADDRESS>Date:   Wed Aug 26 10:20:21 2020 +0200
build: update @ types/hapi__hapi to version ^20.0.0

commit b8a0040
Author: Alan Agius<EMAIL_ADDRESS>Date:   Wed Aug 26 08:23:46 2020 +0200
build: update to TypeScript 4.0

commit e47dbc8
Author: Renovate Bot<EMAIL_ADDRESS>Date:   Sat Aug 22 05:05:28 2020 +0000
build: update ts-node to version 9.0.0

commit f3efa35
Author: Renovate Bot<EMAIL_ADDRESS>Date:   Sat Aug 15 05:04:27 2020 +0000
build: update rollup to version ~2.26.0

commit 7bdd58d
Author: Renovate Bot<EMAIL_ADDRESS>Date:   Fri Aug 14 05:04:39 2020 +0000
build: update rollup to version ~2.25.0

commit 1b2ddbb
Author: Renovate Bot<EMAIL_ADDRESS>Date:   Thu Aug 13 05:05:04 2020 +0000
build: update karma-jasmine to version 4.0.1

commit d45d9b1
Author: renovate[bot] <29139614+renovate[bot]@ users.noreply.github.com>
Date:   Wed Aug 12 01:29:03 2020 -0400
build: update karma-jasmine to version 4.0.0 (#1798)
Co-authored-by: Renovate Bot<EMAIL_ADDRESS>

10.1.0-rc.0 - 2020-08-27commit 132de1e
Author: Keen Yee Liau<EMAIL_ADDRESS>Date:   Thu Aug 27 10:42:25 2020 -0700
release: v10.1.0-rc.0

commit 756d0b1
Author: Alan Agius<EMAIL_ADDRESS>Date:   Thu Aug 27 10:08:22 2020 +0200
build: update Angular packages to 10.1.0-rc.0

commit 0eb7253
Author: Alan Agius<EMAIL_ADDRESS>Date:   Wed Aug 26 10:20:21 2020 +0200
build: update @ types/hapi__hapi to version ^20.0.0

commit b8a0040
Author: Alan Agius<EMAIL_ADDRESS>Date:   Wed Aug 26 08:23:46 2020 +0200
build: update to TypeScript 4.0

commit e47dbc8
Author: Renovate Bot<EMAIL_ADDRESS>Date:   Sat Aug 22 05:05:28 2020 +0000
build: update ts-node to version 9.0.0

commit f3efa35
Author: Renovate Bot<EMAIL_ADDRESS>Date:   Sat Aug 15 05:04:27 2020 +0000
build: update rollup to version ~2.26.0

commit 7bdd58d
Author: Renovate Bot<EMAIL_ADDRESS>Date:   Fri Aug 14 05:04:39 2020 +0000
build: update rollup to version ~2.25.0

commit 1b2ddbb
Author: Renovate Bot<EMAIL_ADDRESS>Date:   Thu Aug 13 05:05:04 2020 +0000
build: update karma-jasmine to version 4.0.1

commit d45d9b1
Author: renovate[bot] <29139614+renovate[bot]@ users.noreply.github.com>
Date:   Wed Aug 12 01:29:03 2020 -0400
build: update karma-jasmine to version 4.0.0 (#1798)
Co-authored-by: Renovate Bot<EMAIL_ADDRESS>

10.0.2 - 2020-08-11 Read more

10.0.1 - 2020-06-30commit 8a32f27
Author: Keen Yee Liau<EMAIL_ADDRESS>Date:   Tue Jun 30 13:57:38 2020 -0700
release: v10.0.1

commit c262c72
Author: Alan Agius<EMAIL_ADDRESS>Date:   Fri Jun 26 13:00:45 2020 +0200
build: update lock file and @ types/node resolutions

commit 2dbe674
Author: Alan Agius<EMAIL_ADDRESS>Date:   Fri Jun 26 10:52:35 2020 +0200
fix(express-engine): RenderOptions is not assignable to object
Closes #1744

commit 0ebf846
Author: Alan Agius<EMAIL_ADDRESS>Date:   Fri Jun 26 10:45:56 2020 +0200
fix(express-engine): fix return type for app method

commit 9024f1c
Author: Alan Agius<EMAIL_ADDRESS>Date:   Fri Jun 26 10:41:24 2020 +0200
test: enable strict mode testing

commit ea49db1
Author: Alan Agius<EMAIL_ADDRESS>Date:   Thu Jun 25 12:14:20 2020 +0200
tests: update tests to work with version 10

    from @nguniversal/express-engine GitHub release notes

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

Checkmarx One – Scan Summary & Details – f62643a3-98e1-4161-8394-1cf6f04cc018
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

CVE-2023-46233
Npm-crypto-js-3.3.0
Vulnerable Package

Passwords And Secrets - Generic Password
/users.yml: 195
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/users.yml: 132
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/users.yml: 186
Query to find passwords and secrets in infrastructure code.

CVE-2023-44270
Npm-postcss-7.0.39
Vulnerable Package

Fixed Issues

Severity
Issue
Source File / Package

CVE-2023-2251
Npm-yaml-1.10.2

Cx6b921f00-d395
Npm-vm2-3.9.11


[CI] Enable b2963 wasi_nn-ggml plugin

Hello, I am a code review bot on flows.network.
It could take a few minutes for me to analyze this PR. Relax, grab a cup of coffee and check back later. Thanks!


hide functions that have been deprecated

various sort.Xxxx functions have been deprecated
how can we hide them from toolset without actually deleting them so that we stay backward compatible

see assets/core/modules/list.ts

create a config file that will replace certain functions with new functions
it should include teh possibility to change some of arg order
for example, lets say
oldFunc(arg1, arg2, arg3) -> newFunc(arg1, arg2, 123, arg3)
this be specified as some JSON data, maybe something like this
{
old_func: {
name: "oldFunc",
args: [arg1, arg2, arg3]
},
new_func: {
name: "newFunc",
args: [arg1, arg2, 123, arg3]
}
}

done


[BUG] Hover tooltips not working

I remember being able to hover over the pie chart pieces and on the graph to see complete numbers for each category. Doesn't seem to work anymore on different OS's or browsers. Was this feature removed?
The filesChecked and hashMismatches are similar in color and I like to make sure, see what I'm looking at with the tooltips, and get exact numbers if possible.
I guess a related feature request would be to have a table showing exact numbers for each category next to the charts.

OS: MacOS, Windows
Browser: Firefox, Safari
checkrr Version: docker, aetaric/checkrr:lates

The charts are all chart.js, looks like something changed back in 3.2.0 when chart.js was bumped to 4.3.0 from 4.1.2. I'll have to poke around and see what changed, if I can fix it, and if I can improve the data display somewhat.
To solve your problem temporarily, if you click on items in the legend, it should hide them from the data display. The stats are also displayed at the end of each run, so you should be able to get the exact numbers there.


how to recover wallet?

Hi everyone,
I'm trying to regain access to the wallet I created years ago and need some help getting pointed in the right direction.
I believe I remember parts of the password I used at the time so I've created a script to test them out (essentially a worldlist to use as a dictionary in a bruteforce attack).
I have the recovery QRcode but would like to know how I can get access to the actual wallet file so I can try and bruteforce it with my list offline.
Any ideas?
Thanks

@petervnv
I have powerful machine to crack all  wallets from 2012-2022 and can recover many wallet password.
for fast response text me in telegram or gmail
Telegram: @walletrecover
<EMAIL_ADDRESS>

Hi @petervnv,
We have new in house tools to open HOLDER Wallets 100% of the time. Please contact us at<EMAIL_ADDRESS>or visit our page and fill the form in here: https://www.unciphered.com/letsgo
We look forward to chatting shortly with you.
-Unciphered Team


cmd/go/internal/auth: the .netrc parser doesn't understand passphrases with spaces

What version of Go are you using (go version)?

$ go version
go version go1.14.3 linux/amd64

Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="off"
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/ainar/.cache/go-build"
GOENV="/home/ainar/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/tmp/g"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/ainar/go/go1.14"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/ainar/go/go1.14/pkg/tool/linux_amd64"
GCCGO="/usr/bin/gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build748023900=/tmp/go-build -gno-record-gcc-switches"

What did you do?
With this in my .netrc:
machine my.git.host login ainar-g password "very long and secure passphrase"

I did:
$ go get my.git.host/go-package

What did you expect to see?
Package in my GOPATH.
What did you see instead?
401 from the server.  I assume that it's because the .netrc parser doesn't understand quoted passphrases with spaces.  IIRC, they're not standard, but are a common extension.

How would it affect users that happen to have a double quote character in their password?

Good question.  According to
this StackOverflow answer
the two widely-used .netrc parsers that allow spaces are
GNU ftp and the Net::Netrc module in Perl.  The
C source code
of the first one suggests that it simply scans until the next double
quote.  My Perl and PCRE are a bit rusty, but the
regexp in the Perl source code
seems to suggest a similar behaviour.  So, if the user has
a double-quote inside the password, they're probably fine, but if the
password starts with a double-quote, there is no way to express that in
.netrc.

The Go .netrc parser is based on the description in https://www.gnu.org/software/inetutils/manual/html_node/The-_002enetrc-file.html, which says:

[Tokens] may be separated by spaces, tabs, or new-lines:

That implies that, for example,
machine a.example.com password "hunter2 machine b.example.com password opensesame"

should be parsed as
machine a.example.com
password "hunter2
machine b.example.com
password opensesame"

You could argue that real passwords should not contain quote characters, but that's not particularly different from arguing that real passwords should not contain spaces...

So the question is: is there an authoritative (or semi-authoritative) reference for quote-escaping in .netrc files, and/or for why passwords should prefer   over "?

@bcmills  Who was supposed to add more info?  I apologise if it was me, because as far as I know, there aren't any more authoritative references than the current implementations I mentioned.

(Answering for @bcmills since he's out of office today)
My understanding is that The .netrc file is the best source on this format. If there's a more authoritative source though, please let us know.
I think we should stick to the spec, such as at is. If every tool has its own interpretation of this file, that's not a good situation for anyone.

@jayconrod  The thing about that file is that it uses two words that may or may not mean the same thing: “name” and “string”.  This “string” may be just another name for a non-space string of characters or it may mean that "a b c" is a “string” and a “token” in and of itself.  The source code of GNU ftp, which I linked above, seems to think that it's the latter and not the former.
I don't think there is a good solution here, to be honest.  I assume, that passphrases with spaces are more common than those with double quotes, but there are already implementations that don't allow spaces.

The following tokens are recognized; they may be separated by spaces, tabs, or new-lines:
...
‘login name’
...
‘password string’
Supply a password. If this token is present, the auto-login process will supply the specified string if the remote server requires a password as part of the login process. Note that if this token is present in the .netrc file for any user other than anonymous, ftp will abort the auto-login process if the .netrc is readable by anyone besides the user.

This doesn't seem ambiguous to me: name and string are just descriptive names. Tokens may be separated by spaces, tabs, or newlines; there's no other restriction on characters within tokens; nothing says quotes should have special meaning.
Is GNU ftp implementing something else? I don't think their source code alone is convincing.

Space is a valid character for a password. More common these days would be people using them with a passphrase, which is totally valid. However as others have said, the current spec doesnt account for this situation at all. It assumes all tokens are separated by whitespace, so if your password has a space, then it would be considered two tokens.
I think what OP was getting at, is that this is a poor spec, which I agree it is.  However until if an when its updated, it will be hard to justify deviating from the spec. One popular implementation is cURL, which as can be seen just assumes tokens are separated by whitespace:
https://github.com/curl/curl/blob/33ba0ecf/lib/netrc.c#L87


Postal worker issue

Hi
I have added into postal.yml
workers:
quantity: 4
threads: 4
and then restarted server as well postal but when i check the postal status... status show's worker quantity is 1 only... why?
Can you please help me with this matter

you'll have to check the log files, also do you have enough memory available?

yes... i have 8GB RAM

have you looked in the log files? have you checked htop or something to see how much available memory you have?

htop information
https://paste.pics/e06c8fe9be9c01a1cb45e41ebb9b9c33
Please check

have you looked in the log files?


Listing Directory

When i try to open my html file with the 'Live Server' extension it opens a page that is titled "listing directory /" and shows some files...
What do I do?

The best way to do is:

Right click on the file
Click on Open with Live Server


Add Conway example based on llbuild2 build system with SwiftUI

Poor Conway, brilliant mathematician and apparently all we can't even call this GameOfLife :p


404 item not found on /me/drive/

Developer.microsoft.com graph-explorer shows
{
"error": {
"code": "itemNotFound",
"message": "Item not found",
"innerError": {
"date": "2022-09-18T02:21:45",
"request-id": "dc6b81ef-f007-4c54-9914-ee1ed5d01b30",
"client-request-id": "bf17bc4a-6fc9-f73d-e099-538568226436"
}
}
}

@zeroday17 could you provide more details about this file, does it show up in the UI? but is not returning via the aPI?
what API are you call?
if this is still occurring please provide a requestId and timestamp of a recent failure


LIBHYDRA-204. Select All bug fix.

https://issues.umd.edu/browse/LIBHYDRA-204

@mohideen There are a couple Rubocop errors on line 24.


SUG: Make Web Viewer more known publicly

Issue
It is quite hard to know that there is a Web viewer for MaterialX.
Suggestion
Unless you go into the github repo or know of the site, the WebViewer is quite hard to discover / find the site
(https://academysoftwarefoundation.github.io/MaterialX/)
Suggestion is to make a link to this more public so users can find and try it out to expose MaterialX more broadly,
perhaps by adding a mention at the top level github but also in the materialx.org site (which only mentioned the desktop viewer and not the node editor either).

Great suggestions, @kwokcb, and I agree these changes would be valuable.  If developers in the community have the bandwidth to make these adjustments to the MaterialX and materialx-website GitHub repositories, feel free to write up pull requests.

Looking at www.materialx.org, I see that we mention the MaterialX Web Viewer very briefly and provide a link, but this application definitely deserves its own section on the page:
https://materialx.org/Tools.html

I've had a chance to refine our tools documentation for MaterialX, adding sections on the Graph Editor and Web Viewer:
https://materialx.org/Tools.html#WebViewer
I'll close out this original issue for now, though there's still plenty of room for future improvement in this area.


Update the Sample configuration in Gmail as the email OTP provider

In the documentation [1] we are providing wso2 IS as the OTP provider's configuration as a reference for configuring Gmail as the email OTP provider (step 14 in - [2])  . Instead of that better to provide a relevant sample configuration
[1] [ Configuring Email OTP](https://is.docs.wso2.com/en/latest/learn/configuring-email-otp/#option2-configure-gmail-as-the-email-otp-provider)
[2] https://is.docs.wso2.com/en/latest/learn/configuring-email-otp/#option2-configure-gmail-as-the-email-otp-provider

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Change the linter message to more appropriate one

Description
When there are no errors in the linter, it shows in the following message. Seems this is not matching the theme of the product.

Steps to Reproduce
Go to publisher portal and open api definition editor page
Affected Component
APIM
Version
4.2.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response

Update 2023-02-14

Reproduced this issue.
Changed the linter message appropriately


Button is completely grey in Asana integration

OS version: 10.15.6
Browser version: Chrome 85
Extension version: 1.66.1

Relevant integration (if any):
Asana (same behavior in Todoist)

🐛 Describe the bug

The button is entirely grey until you click on it and it turns purple

Expected behaviour

The button show correctly with our logo
Other details or context

Case reference

Case reference

Seems to be a duplicate of https://github.com/toggl/toggl-button/issues/1862


Add ICMP6 Support to Shaper

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Is your feature request related to a problem? Please describe.
I investigated an issue where my IPv6 gateway experienced packet loss and goes offline whenever I saturate my uplink. IPv4 dpinger (under 23.1) showed no issues. I have a shaper catchall rule that sends all upload IP packets to an FQ_CoDel queue. Under a higher priority, I send ICMP packets to a separate FIFO pipe so it does not fall into the catchall.
60001 pipe 10004 icmp from any to any via lagg0 // 1b5cdc2d-f045-4c2a-a085-1eab471e4125 wan: PipeFIFO-1M

Apparently icmp does not include IPv6 ICMP packets. These packets were falling through this ICMP rule and hitting the FQ_CoDel catchall, resulting in “packet loss” when the algorithm properly discards packets to shape uplink traffic.
Describe the solution you like
Add ‘icmp6’ to shaper protocols that creates ipv6-icmp rules in order to handle IPv6 ICMP packets.  I was able to test by adding the rule below with ipfw.
60002 pipe 10004 ipv6-icmp from any to any out via lagg0 // c7ac91ad-ec86-47db-b835-25b78a82332c wan: PipeFIFO-1M

The existing icmp protocol should be renamed into icmp4 to remove ambiguity.
Describe alternatives you considered
I put a workaround by breaking up my catchall into 4 separate rules. I send the following protocols to FQ_CoDel: ipv4, udp, and tcp. Then, my last rule sends ip protocol packets to the FIFO pipe.

adding ipv6-icmp to the list isn't an issue, done in https://github.com/opnsense/core/commit/fd6c824a5b0a070a939a7d2cfc7ca59623bb3af6. We're not going to rename icmp though as this is the original protocol name (https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml)

Thank you for your consideration @AdSchellevis.


feat(helm): output flag for helm inspect to provide data as json values

output flag is added to helm inspect, so the output format type can be
set to json or yaml
eg: helm inspect chart mychart/ --output=json
closes: 5070
Signed-off-by: Mohan Prasath<EMAIL_ADDRESS>

Sorry for not getting back to you sooner. The team has been focusing for the past few months on getting Helm 3 out the door, and that has meant it's been harder to find time to review feature additions for Helm 2.
Helm 2.15 is soon to be released, and will be the last feature release for Helm 2. Because of the time commitment required to rebase this and test it, we won't be able to find the time to review this. That being said, if you want to try again by implementing this for Helm 3, that would be much appreciated. I'd hold off for a few weeks until 2.15 is out as we are planning to move the dev-v3 branch over to be the new master branch, so there will be some shuffling around for a bit, but once that's done we'd be happy to consider this for the 3.1.0 release.
Thanks again!


removeObsoleteConnections delete all connections that are alive after 2 minutes when messages are being sent to clients

So this has bugged me for a while, but I finally got it!
After some time (exactly two minutes) the library stopped sending me messages because Laravel Echo/Pusher-js doesn't ping-pong in case there's traffic going on. So the lastPongedAt doesn't get updated, which in turn, deletes the client from the channel connections list and stops sending the messages to that client. I can ping-pong manually, but I feel this is a wider problem and I am shocked nobody actually pointed it out. This should be at least a big red in the documentation.

You may want to take a look at this PR
https://github.com/beyondcode/laravel-websockets/pull/778

Having the same issue. Did you find any fix?

I changed it in the vendor folder to not remove them for a day (I am resetting the websocket once a day)
I started ping ponging manually


Google Map not showing in prod release

Hi,
I developed cross platform app in Ionic 3, and added this plugin, Map showing perfect in debug build, but showing empty in prod release, please see the attached file.
Version:
cordova-plugin-googlemaps:  1.4.3
Please help me, my prod release is stuck now
Thanks

maybe this #1517 can help

Yes, your API key is wrong.

@ypkkhatri ping

Hi, sorry for delay will update here tomorrow, thanks

Hi,
It's perfectly fine now, I have used by mistaken SHA-1 fingerprint of android.keystore and app build release from my own keystore file so it was stuck.
Thank you


Fix up behavior of Code Coverage GH Action

Code Coverage GH Action: Remove unnecessary merge commit by rebasing
Just run git push, not something fancy
change readme to trick it
Fix git push
Be better about getting current branch
Use built in feature to get branch name

@jbonzo are you still working on this branch or is this ready for review?

@jbonzo are you still working on this branch or is this ready for review?

This is still WIP, I couldn't get it to work exactly so not ready for review.


Missing Code of Conduct & Contribution.md

This repository has no Code of conduct & Contribution.md file. any open-source project needs to set clear standards for behavior. It promotes inclusivity, prevents misconduct, fosters accountability, and maintains a positive environment.
Please assign this issue to me.

@Dhruv-Pattel thanx,but unfortunately, I withdraw this project from GirlScript Summer of code . It will be removed within few days


Error Message when Missing a License is Asking for Characters

I noticed that when a license is not selected, it will show an error message asking for characters.  (License - Should be at least 1 characters)
I expected that the error message would show "Required".

A very small bug, but I wanted to put it out there!

Thanks Nami! That's good feedback 😊
@all-contributors add @nsunami for bug


API GW should adhere to "Accept" header dictates as much as possible

Here is one specific example, although other scenarios likely have the same issue.

Create an API that is configured with "Require applications to authenticate via API key" enabled.
Invoke the API using curl, but specifying the "Accept" media type as something besides application/json
A 401 is returns with a JSON body and "Content-Type" value of application/json

>curl https://service.us.apiconnect.ibmcloud.com/gws/apigateway/api/API-UNIQUE-ID/API-PATH -H "Accept: application/xml"

{"status":401,"message":"Error: Unauthorized"}

So, in your scenario, let's say you pass an Accept header of text/html. If an API key is required, the gateway responds with 401, but what Content-Type is the response body?

I guess the server might be able to support a few "standard" media types and respond with the one that matches the request Accept header.  If a server is unable to adhere to the requests Accept set of media types, should it return a 406?

I think 406 isn't terribly useful, since we don't know exactly what types are allowable and it would be preferable to tell the caller why the call failed even if it's in a format they didn't ask for. Since we'd set the Content-Type to whatever is being returned (which would be application/json by default), then the caller should be prepared to handle that case.


Tune control and add cmd/status converters

Clearly breaking (and acceleration) longitudinal control is not tight, especially when slowing down before occlusion spots. It is shown in the following plot:

Added raw_vehicle_cmd_converter and accel/brake maps for more smooth and accurate longitudinal control.
Now it is better:


missing 1.21 package as RPM

Steps to Reproduce:
Go to: https://packages.microsoft.com/yumrepos/vscode/
Latest release is "code-1.20.1-1518536126.el7.x86_64.rpm"

duplicate of https://github.com/Microsoft/vscode/issues/45500
just hard to find that one with github search because neither "yum" nor "rpm" find it.

https://github.com/Microsoft/vscode/issues/45868


Applications installed not appearing in Spotlight Search

Not a critical issue, but it in frustrating.  Due to the caskroom and symlinking to appdir none of my managed apps installed this way appear to show up in Spotlight Search.
In my case I am using the following configuration:
export HOMEBREW_CASK_OPTS="--caskroom=/Applications/.cask --appdir=/Applications"

I don't have any privacy rules preventing Spotlight from indexing any locations.

Ah, nevermind.  It appears the version I was on did this but it has since been changed.  I jsut had to uninstall and reinstall all my casks and now they work.