Can training without a pre-trained weight be an option in any possible case?

Thank toy for sharing this crystal clear implementation here. I have a question regarding the VGG16 base network which may not related to the implementation but to share knowledge.
So, I tried to train from scratch without using a pre-trained weights and after finishing the training, it is clear to me that is not an option but I would like to double check. I have to use weights and stick with the SSD16 structure.
In case if I want to remove VGG16 with another base network, let's say ResNet and in this case I have to train from scratch without any pre-trained weights which will not lead to a satisfying mAP. So what are my options here:

If I don't want to use VGG16, and design my own network like your ssd7, and using the same classification layers. what are the possible solutions to do that?

In case I want to use VGG16 as a base network, and modify the classification layers with different convolutions structure,  how can I get the weights  before let's say fc6 or fc7 and put them on my network?

If I want to design an entire network structure, should I have to train it first (as a classification problem before the detection layers) on a large dataset like ImageNet first and then stick the classification layers to it and see how the detection will perform? I'm asking this because I'm wondering how YOLO were able to perform high mAP without having a base network!

So, I tried to train from scratch without using a pre-trained weights and after finishing the training, it is clear to me that is not an option but I would like to double check.

Correct, trying to train SSD300 or SSD512 from scratch without loading the trained VGG-16 weights is not going to work (at least not with the standard random initialization approaches). Note that the original VGG models were not trainable all at once, the VGG creators had to train them in stages (i.e. layer by layer).

In case if I want to remove VGG16 with another base network, let's say ResNet and in this case I have to train from scratch without any pre-trained weights which will not lead to a satisfying mAP.

Two comments on this statement:

You're making an incorrect inference here. You can't make the same assumptions for two completely different network architectures like VGG-16 and ResNet. Meaning: Just because training a VGG-based SSD model from scratch doesn't work without pre-trained VGG weights doesn't imply that the same is true for a ResNet-based SSD model.
You're confusing two things here: The main reason why loading pre-trained VGG-16 weights into SSD300 or SSD512 is necessary is not because you wouldn't get a "satisfying mAP" otherwise, but because the training wouldn't work at all, i.e. it wouldn't converge at all.

Let's compare VGG and ResNet as an example: The reason why training SSD300 from scratch without loading VGG weights doesn't work is because VGG is too deep to be trainable all at once for the rather "primitive" architecture that it is. This is exactly the reason why the ResNet authors designed ResNet. The whole point of ResNet was to design networks in a way such that they are still trainable end-to-end even if they are very deep. The two main things that ResNet has in this regard which VGG doesn't have are batch normalization and, more importantly, ResNet's "shortcut connections".
The main take-away are these:

Whether or not it works to train a given neural network end-to-end from scratch without any pre-trained weights obviously depends on the network. It cannot be said in general.
You can get pretty much any relevant model with trained ImageNet weights, so the question of whether or not an SSD based on such a given model can be trained without pre-trained weights is secondary.

Hi  Pierluigi Ferrari,
Thank you for explaining.
I am sharing my experience of using your SSD model for two different use
cases with two different way of training.
Use Case 1: Used your model for parking sign detection with VGG model and
pre-trained weighted provided and performing well with accuracy of
detection Parking sign with 85% Accuracy. The input is standard RGB images
(300, 300, 3)
*Use Case 2: Used your model for Bounding Box Aggregation with VGG model no
pre-trained weighted becuase input image size is different than default.
The input image is 300, 300, 4 (fourth channel is weighted average of
bounding boxes. I can't trained used existing pre-trained weights because
the input dimension is different. The dataset for this use case is training
and validation set of COCO. I also got ~85% accuracy for bounding box
aggregation using this SSD model. *
Can you comment on it? If you have any better way to use your model for
bounding box aggregation with input image have different dimension (instead
of 3 channels, either 1 channels or 4 channels).
Best,
-humayun
On Fri, Jul 20, 2018 at 4:10 PM Pierluigi Ferrari<EMAIL_ADDRESS>wrote:

So, I tried to train from scratch without using a pre-trained weights and
after finishing the training, it is clear to me that is not an option but I
would like to double check.
Correct, trying to train SSD300 or SSD512 from scratch without loading the
trained VGG-16 weights is not going to work (at least not with the standard
random initialization approaches). Note that the original VGG models were
not trainable all at once, the VGG creators had to train them in stages
(i.e. layer by layer).
In case if I want to remove VGG16 with another base network, let's say
ResNet and in this case I have to train from scratch without any
pre-trained weights which will not lead to a satisfying mAP.
Two comments on this statement:

You're making an incorrect inference here. You can't make the same
assumptions for two completely different network architectures like VGG-16
and ResNet. Meaning: Just because training a VGG-based SSD model from
scratch doesn't work without pre-trained VGG weights doesn't imply that the
same is true for a ResNet-based SSD model.
You're confusing two things here: The main reason why loading
pre-trained VGG-16 weights into SSD300 or SSD512 is necessary is not
because you wouldn't get a "satisfying mAP" otherwise, but because the
training wouldn't work at all, i.e. it wouldn't converge at all.

Let's compare VGG and ResNet as an example: The reason why training SSD300
from scratch without loading VGG weights doesn't work is because VGG is too
deep to be trainable all at once for the rather "primitive" architecture
that it is. This is exactly the reason why the ResNet authors designed
ResNet. The whole point of ResNet was to design networks in a way such that
they are still trainable end-to-end even if they are very deep. The two
main things that ResNet has in this regard which VGG doesn't have are batch
normalization and, more importantly, ResNet's "shortcut connections".
The main take-away are these:

Whether or not it works to train a given neural network end-to-end
from scratch without any pre-trained weights obviously depends on the
network. It cannot be said in general.
You can get pretty much any relevant model with trained ImageNet
weights, so the question of whether or not an SSD based on such a given
model can be trained without pre-trained weights is secondary.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pierluigiferrari/ssd_keras/issues/157#issuecomment-406713848,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfsUl6BTUbT2z38RHjVS0gBXG0PFwWgKks5uIjlGgaJpZM4VXRth
.

--
Humayun Irshad
Lead Scientist, Machine Learning
T<PHONE_NUMBER>  | @HumayunIrshad https://twitter.com/HumayunIrshad or
LinkedIn https://www.linkedin.com/in/humayunirshad/
O<PHONE_NUMBER>
figure-eight.com
https://figure-eight.com/
The essential Human-in-the-Loop AI platform
for data science and machine learning teams

Perfect! Thank you @pierluigiferrari for your valuable comments.  Now I feel that I'm catching it.
OK, after two weeks of struggling as I'm still new to this problem, I want to start fresh and I hope you have time to bare with me on this as everybody here want to hit 77.4% or any other score before taking the next step. I trained on 07p12 train/val using VGG_ILSVRC_16_layers_fc_reduced.h5 but still I don't see convergence and now I'm in the epoch  65 (maybe I'm still early to ask). Last validation Loss improvement recorded at epoch 34 =8.2286. I want to ask about the correct setting that I should follow in  ssd300_train, for instance data generation or clip boxes to hit 77.4%, so I can consider it as a starting benchmark for comparison on whatever I want to do later.
Another question:
I saw here equations regarding using the variances in Scale Ground-Truth Boxes. Are these equations necessary , if so, are they implemented in the implementation?
Thanks,

I think the issue coming from using python 2 as you mentioned in one comment issue #160 . I will try to reproduce the results with python 3 and see if that is the cause.

This is the results from SSD300 out of the box. I downloaded the code and ran again.


Detect failed tests in ARM CI

This commit fixes ARM testing so that it reports a failure when unit tests fail. This was broken because find -exec was not doing what was expected. To fix this, we now use find | xargs.
See https://apple.stackexchange.com/questions/49042/how-do-i-make-find-fail-if-exec-fails. find -exec returns a 0 exit code unless an error occurred while traversing the directories; the return status of executed commands does not matter.
cc. @tamird

LGTM but seems we have uncovered some failures. Can you make sense of them?

Possibly this QEMU bug? https://gitlab.com/qemu-project/qemu/-/issues/340

Looks like https://github.com/golang/go/issues/20763 was a known issue with Go binaries on QEMU that was fixed for Go1.8, though I still see failures until Go1.9. WDYT @nvanbenschoten ?

Oops, misread. That fix was included in 1.9. The world makes sense.

Thanks for taking a look at the failing tests. Your changes LGTM.


M.textareaAutoResize function missing in the release 2.0.0-alpha

Hi,
The function M.textareaAutoResize() is no longer accessible in the release 2.0.0-alpha
That function is described in the textarea documentation as the function we need to execute when dynamically changing the value of a textarea.
Is it because now the Textfields are css only in 2.0.0-alpha?
In this case, perhaps the documentation should be adapted?
Thank you for this new version and your excellent work,
Olivier

Hello,
The problem is still present with the version 2.0.1-alpha.
The function M.textareaAutoResize() was working properly before the release 2.0.0-alpha.
The function still seems necessary because the height of the textarea is not updated when dynamically changing the value of a textarea.
We can reproduce the issue really simple by navigating to https://materializeweb.com/text-inputs.html
And execute in the console:
document.getElementById('textarea1').value = 'Hello \nMaterialize\nTeam.\nThis\nframework\nis\nawesome!'
Thank you again for your excellent work,
Olivier

Hello,
The function M.updateTextFields() was also removed, but still need to be used.
Thank you

Hello,
I've checked the repo and, in fact, those functions have been removed (probably durin the transition from JS to TS + jQuery removal).
I'll try to reimplement them asap.
Thank you for your feedback :)

Hello, I removed updateTextFields, because it is no needed anymore.
The Label-Animation is now fully done in CSS.
The only thing needed now is a placeholder Attribute in the Inputs. I see that this i missing in the documentation.
This needs a documentation update.

As of #382. this issue must be resolved :smile:

Thank you so much for fixing the issue and updating the documentation!


Change contentContainer selector to more generic of new theme

The current selector was made to fit specifically to the payment methods page, but with PrestaShop/PrestaShop#20737 carriers page is being migrated and this has to use more generic selector. This change generated HTML, but not how the page looks like.

@atomiix This PR doesn't touch PHP at all and PHPStan is what is failing, so this would be out-of-scope for this PR.

@ks129 yep, that's why I approved it anyway :)

Note for reviewers: Code is duplicated because if I move selector selecting outside of done or fail, selector result is undefined.

Sorry for the long delay on this PR.
The v2.x of ps_mbo will only receive security fixes now, so I close this one.
We are wokring on a total revamp of the module.
Anyway, thanks for your contribution :)


Add OpenBioLing to Benchmarking GNNs?

Hi all, not sure if this is possible, but you guys might be interested in checking it
https://github.com/graphdeeplearning/benchmarking-gnns

@nomisto The repository describes new dataset addition procedures here: https://github.com/graphdeeplearning/benchmarking-gnns/blob/master/docs/04_add_dataset.md -- how difficult would this be?
@nomisto Maybe also ask the maintainers of that project first if they would want to officially add OBL to their project. I think only then it would make sense for us to invest effort.


Browserless login support

Fixes #3

Closing this since this is not what the browserless login does. It uses a completely different auth mechanism to retrieve the user token from Railway https://github.com/railwayapp/cli/blob/e3bd751b88d95c71c03252cd94a2bc509e248753/controller/user.go#L171
The default CLI login starts a local server that accepts the token from Railway. Browserless login will show 4 random words in both the CLI and browser and will poll for the token from the API.

Ah, OK.


Update parser tests for new thermostat metainfo

fix FHIaims, check other tests

Hi @JFRudzinski, I see the test_fhiaimsparser.py is failing. This has a very easy fix, as thermostat_parameters is a list, so line 259 should point to the [0] element.
Or are you planning other changes?

@JosePizarro3 Yes exactly. Would you mind making the change? I was planning to do it during the week. I did not anticipate how busy I would be but I have not had a second to breath 😮💨

Sure, I'll quick fix it in #166 .


Removes ConnectedRouter in favor of dispatching in middleware

This is another way to address #4713

What about errors like Warning: Hash history cannot PUSH the same path; a new entry will not be added to the history stack with this implementation?
Example an user is on the page /about and click on a button in the top bar which is a Link and redirect to /about?

@GuillaumeCisco I don't see how this would affect that, as it responds to history changes—it doesn't not trigger them.

I'm asking because I've just tested the code and I've got this use case :)

@inxilpro This is basically the core of what RRR 4.0 is, just without the time traveling support. I want to keep the ConnectedRouter API, so I'll close this one out for now.


AWS Amplify AUTH with Cognito - Social sign in with web UI, returns "Invalid relay state from identity provider"

Describe the bug
I've set up social sign-in with web ui. (Xcode ios SwiftUI)
All of that works fine, till after Login, where the social provider (Google and facebook) returns with error
[ Invalid relay state from identity provider ]
To simplify I ran the CLI 'Amplify Status' to get the test for endpoint. Also there I then get the error [ Invalid state ]
So redirect URI is correct, but obviously something wrong with with the endpoint.
Went to Cognito console to see if I can identify any issues, but clearly I'm missing something.
It does however look like this may be a Cognito identity previously associated with an  earlier app, possibly (although I an not able to categorically say that it is in fact the case).
This does not seem to be a generic bug, but more like situation conditional.
Steps To Reproduce
-In terminal, go to app directory.

-Run'Amplify Status'
-Copy test link from "Test Your Hosted UI Endpoint:" into browser.

-Click Facebook signIn = receive 'Invalid state' response.

-Click Google signIn = receive 'Invalid state' response.

Expected behavior
Would expect a resolve, I suppose.
Issue may be instance specific, but could be worth investigating the link to federated identities arn for amplify projects.
(i may be way off the mark)
If someone can point me to some workflow/checklist for the Cognito federated identities, or know the cause of this state error, it would help a lot
Amplify Framework Version
current?
Amplify Categories
Auth
Dependency manager
Swift PM
Swift version
5.0
CLI version
7.6.11
Xcode version
13.2.1 (13C100)
Relevant log output
'User Cancelled' - The web UI View

Is this a regression?
No
Regression additional context
No response
Device
all
iOS Version
15
Specific to simulators
no
Additional context
No response

Hi @Wazambe
Did you setup amplify using Amplify CLI by calling amplify add auth. Can you provide the following info:

Content of amplifyconfiguration.json after redacting sensitive info
Code sample on how you are invoking webui
Did you setup call back url for the iOS app


New package: Intel.OSPRay version 3.0.0

Description
This package is not an executable application but a C/C++ library installer. No icons will be added to startup menu or desktop.

Resolve https://github.com/microsoft/winget-pkgs/issues/123441

Checks

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

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

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

Microsoft Reviewers: Open in CodeFlow

@wingetbot waivers Add Validation-Executable-Error


script not working

error
[zoom_and_follow_mouse.py] {'monitor_id': '\\?\DISPLAY#BNQ78E4#5&396a6378&0&UID4352#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}'}
[zoom_and_follow_mouse.py] Traceback (most recent call last):
[zoom_and_follow_mouse.py]   File "D:\OBS PYTHON\zoom_and_follow_mouse.py", line 371, in toggle_zoom
[zoom_and_follow_mouse.py]     zoom.update_source_size()
[zoom_and_follow_mouse.py]   File "D:\OBS PYTHON\zoom_and_follow_mouse.py", line 66, in update_source_size
[zoom_and_follow_mouse.py]     data = loads(data)['monitor']
[zoom_and_follow_mouse.py] KeyError: 'monitor'

I'm getting the same Error currently

Same here

i use portable python 3.6 with 28.1.2 and it works well. Both display capture and window capture. You should give it a try!

if you did not use installer version, you can simply download OBS-Studio-28.1.2-Full-x64.zip , unzip and run it, old preferences and scripts are preserved as normal.

If this is still an issue, please reproduce and resubmit with current working versions of python, OBS, script and dependencies.


Unable to select numbers/punctuation at start/end with drag

If the number is between two words, you can select it:

However, you can't make a selection starting or ending with a number:

In this situation, I would like to be able to select 12월에 문을 닫으려했지만, as 12월 means December, so is needed for the meaning (my dictionary translates phrases as well as only words).
This also applies to question marks etc. I believe this is because they don't have the class word, because, well, they're not words. Adding the class "fixes" this:

Is there a workaround, such as a class that enables selection but not saving? Personally I wouldn't even mind if they did count as words/terms and could simply be marked as well known/ignored.
Slight complication: as you can see in the third screenshot, the "word" is actually  12, not simply 12.

Hey @jamesdeluk - you might be able to add the digit range 0-9 in your language "word characters".  Can you give that a shot?

Didn't work, either the digit range or the actual number (e.g. 12). I also tried " 12", but that was automatically trimmed. I guess in the processing numbers are removed.

Checking this briefly.  In my dev db I created an english text 12dog 13 cat mouse42
With the default english word chars a-zA-ZÀ-ÖØ-öø-ȳáéíóúÁÉÍÓÚñÑ it's shown as

When I added 0-9 to the word chars (a-zA-ZÀ-ÖØ-öø-ȳáéíóúÁÉÍÓÚñÑ0-9) things looked as I expected them:

@jamesdeluk can try adding 0-9 to the word chars, and let me know if that works?  Also perhaps you could make a backup of your db and send me the zip so I can check it out.  You might be able to attach a file to this issue.

(and maybe I've misread the question too)

Oh, my mistake, I added them as terms. Adding as word chars work, although now it's not possible to select the letters without the number - although for me I still think that's better. Thanks!

ok, I'll close this for now and if something else comes up we can sort it out. :wave:


jnp.nanmean can overflow in the denominator for large arguments

Description
The following reproduces a phenomenon where the mean of a positive tensor can be negative:
logits = np.random.uniform(size=[2048,64, 32000], low=-4, high=4)
jnp.nanmean(jnp.abs(logits))
=> DeviceArray(-83.333984, dtype=float32)

The reason is that the mean normalizer is summed using np.int32 here: https://github.com/google/jax/blob/540835f979fe13a968f69b894dbafc981f122b36/jax/_src/numpy/reductions.py#L586
The error is silent.
A workaround is to split the mean along two or more axes.
A stopgap fix would be to throw an error if the tensor is too large, so that the user can decide how to deal with it.
Another fix would be to sum in int64.
What jax/jaxlib version are you using?
No response
Which accelerator(s) are you using?
No response
Additional system info
No response
NVIDIA GPU info
No response

Thanks for the report – I vaguely recall this coming up recently in the context of mean as well.
Perhaps since we end up converting to float in the end anyway, a better fix would be to accumulate the normalizer in float to avoid this kind of overflow? I'm trying to think whether there would be any downsides to that.


Timestamp for tempmute messages

It'd be useful if the bot sent a timestamp along with the message sent in chat and the muted user's DMs so that people can easily find out when their mute expires

This is planned, just not for right now. Soon:tm: I promise.


Added escape characters to the Content-Type header and Accept header when sending JSON Post - Version 1.4.9

Hello,
My API requires that a POST request specify 1 of 2 content types: application/json or application/xml.
When performing a request, I add the accept header like so:
public void setupHttpClient() {
    httpClient.addHeader("Accept", "application/json");
    httpClient.addHeader("Content-Type", "application/json");
    httpClient.addHeader("User-Agent", generateUserAgentString());
}

However, when examining the resulting response from my API, I notice that the headers being sent have an escape slash, i.e.
"application\/json"

instead of
"application/json"

This is extremely annoying, and I can't figure out why my header is being escaped. My API is denying every request because it does not match the required header. Please assist in resolving this issue.
If needed, I can supply a full JSON output from my API with the understood request headers for clarification.

@loopj Can you please assist with this issue ASAP?


Can't assign variable "as" in from as=Assessment

I have a tables named "Assessment" and "Appraisal", so I entered the statement above. It generates (obviously) the following SQL:
SELECT
  *
FROM
  "Assessment" AS as

and SQLite throws an error: Result: near "as": syntax error
It's easy enough to work around (from ass=Assessment) but could this be solved in PRQL, perhaps by quoting the variable name? (I don't know enough about SQL...)

My guess is that SQLite is stricter than others.
We currently have some quoting of keywords. For example, if we replace as with from, PRQL should generate:
SELECT
  *
FROM
  assessment AS "from"  # "from" gets quoted

I tried expanding the keywords we quote in #1967. But it quotes a lot of words — temp / close / month / etc. We'd want to change our examples before merging that, as it adds lots of noise to the outputs.
Do we know what the SQLite rules are? What needs to be quoted in that position?

These are the docs for SQLite: https://www.sqlite.org/lang_keywords.html

These are the docs for SQLite: https://www.sqlite.org/lang_keywords.html

Thanks a lot.
What's a good design here?
I guess we could just copy them in and put them on the DialectHandler struct?

Nah, we can add them for all dialects. Quoting too much is not that bad, except if it really buffs up our examples.

The attached closed PR really did mangle a lot of the examples, but that was a much wider set. So agree it's OK to try expanding the set to the SQLite keywords for all dialects if that's easier and the results look fine

I edited the description and added the Good First Issue label. As ever, if you think you might be interested in contributing and anything is unclear, feel free to ask!


[boringssl] Fix pkg-config & update to 2023-04-20

Update BoringSSL to the current master commit.
I specified a filename postfix ("d") in order to enable full compatibility with FindOpenSSL.cmake.
BoringSSL gained a proper install target with an exported config last year. The exported config is highly compatible with the CMake built-in FindOpenSSL.cmake module which is why I added usage information without specifying MODULE/CONFIG.
I fixed the pkg-config platform-specific library name sanitization: Previously it removed the lib prefix for non-MSVC targets, but left them inplace for MSVC targets. Furthermore it removed the Windows dependencies for MinGW which doesn't match the upstream expectations.
The go runtime update is required by the BoringSSL buildsystem.
Lastly I removed the tools feature due to the fact that the BoringSSL buildsystem doesn't offer a corresponding configuration option and always installs bssl (which by the way is not referenced by the CMake configs).

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[x] The "supports" clause reflects platforms that may be fixed by this new version
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Note that ci does not test boringssl.
vcpkg install boringssl:x64-windows fails with:
cmd.exe /C "cd .
LINK Pass 1: command "C:\PROGRA~1\MIB055~1\2022\ENTERP~1\VC\Tools\MSVC\1435~1.322\bin\Hostx64\x64\link.exe CMakeFiles\crypto_test_data.dir\crypto_test_data.cc.obj crypto\CMakeFiles\crypto_test.dir\abi_self_test.cc.obj crypto\CMakeFiles\crypto_test.dir\asn1\asn1_test.cc.obj crypto\CMakeFiles\crypto_test.dir\base64\base64_test.cc.obj crypto\CMakeFiles\crypto_test.dir\bio\bio_test.cc.obj crypto\CMakeFiles\crypto_test.dir\blake2\blake2_test.cc.obj crypto\CMakeFiles\crypto_test.dir\buf\buf_test.cc.obj crypto\CMakeFiles\crypto_test.dir\bytestring\bytestring_test.cc.obj crypto\CMakeFiles\crypto_test.dir\chacha\chacha_test.cc.obj crypto\CMakeFiles\crypto_test.dir\cipher_extra\aead_test.cc.obj crypto\CMakeFiles\crypto_test.dir\cipher_extra\cipher_test.cc.obj crypto\CMakeFiles\crypto_test.dir\compiler_test.cc.obj crypto\CMakeFiles\crypto_test.dir\conf\conf_test.cc.obj crypto\CMakeFiles\crypto_test.dir\constant_time_test.cc.obj crypto\CMakeFiles\crypto_test.dir\cpu_arm_linux_test.cc.obj crypto\CMakeFiles\crypto_test.dir\crypto_test.cc.obj crypto\CMakeFiles\crypto_test.dir\curve25519\ed25519_test.cc.obj crypto\CMakeFiles\crypto_test.dir\curve25519\spake25519_test.cc.obj crypto\CMakeFiles\crypto_test.dir\curve25519\x25519_test.cc.obj crypto\CMakeFiles\crypto_test.dir\ecdh_extra\ecdh_test.cc.obj crypto\CMakeFiles\crypto_test.dir\dh_extra\dh_test.cc.obj crypto\CMakeFiles\crypto_test.dir\digest_extra\digest_test.cc.obj crypto\CMakeFiles\crypto_test.dir\dsa\dsa_test.cc.obj crypto\CMakeFiles\crypto_test.dir\err\err_test.cc.obj crypto\CMakeFiles\crypto_test.dir\evp\evp_extra_test.cc.obj crypto\CMakeFiles\crypto_test.dir\evp\evp_test.cc.obj crypto\CMakeFiles\crypto_test.dir\evp\pbkdf_test.cc.obj crypto\CMakeFiles\crypto_test.dir\evp\scrypt_test.cc.obj crypto\CMakeFiles\crypto_test.dir\fipsmodule\aes\aes_test.cc.obj crypto\CMakeFiles\crypto_test.dir\fipsmodule\bn\bn_test.cc.obj crypto\CMakeFiles\crypto_test.dir\fipsmodule\cmac\cmac_test.cc.obj crypto\CMakeFiles\crypto_test.dir\fipsmodule\ec\ec_test.cc.obj crypto\CMakeFiles\crypto_test.dir\fipsmodule\ec\p256-nistz_test.cc.obj crypto\CMakeFiles\crypto_test.dir\fipsmodule\ecdsa\ecdsa_test.cc.obj crypto\CMakeFiles\crypto_test.dir\fipsmodule\hkdf\hkdf_test.cc.obj crypto\CMakeFiles\crypto_test.dir\fipsmodule\md5\md5_test.cc.obj crypto\CMakeFiles\crypto_test.dir\fipsmodule\modes\gcm_test.cc.obj crypto\CMakeFiles\crypto_test.dir\fipsmodule\rand\ctrdrbg_test.cc.obj crypto\CMakeFiles\crypto_test.dir\fipsmodule\rand\fork_detect_test.cc.obj crypto\CMakeFiles\crypto_test.dir\fipsmodule\service_indicator\service_indicator_test.cc.obj crypto\CMakeFiles\crypto_test.dir\fipsmodule\sha\sha_test.cc.obj crypto\CMakeFiles\crypto_test.dir\hpke\hpke_test.cc.obj crypto\CMakeFiles\crypto_test.dir\hmac_extra\hmac_test.cc.obj crypto\CMakeFiles\crypto_test.dir\hrss\hrss_test.cc.obj crypto\CMakeFiles\crypto_test.dir\impl_dispatch_test.cc.obj crypto\CMakeFiles\crypto_test.dir\kyber\kyber_test.cc.obj crypto\CMakeFiles\crypto_test.dir\lhash\lhash_test.cc.obj crypto\CMakeFiles\crypto_test.dir\obj\obj_test.cc.obj crypto\CMakeFiles\crypto_test.dir\pem\pem_test.cc.obj crypto\CMakeFiles\crypto_test.dir\pkcs7\pkcs7_test.cc.obj crypto\CMakeFiles\crypto_test.dir\pkcs8\pkcs8_test.cc.obj crypto\CMakeFiles\crypto_test.dir\pkcs8\pkcs12_test.cc.obj crypto\CMakeFiles\crypto_test.dir\poly1305\poly1305_test.cc.obj crypto\CMakeFiles\crypto_test.dir\pool\pool_test.cc.obj crypto\CMakeFiles\crypto_test.dir\rand_extra\rand_test.cc.obj crypto\CMakeFiles\crypto_test.dir\refcount_test.cc.obj crypto\CMakeFiles\crypto_test.dir\rsa_extra\rsa_test.cc.obj crypto\CMakeFiles\crypto_test.dir\self_test.cc.obj crypto\CMakeFiles\crypto_test.dir\stack\stack_test.cc.obj crypto\CMakeFiles\crypto_test.dir\siphash\siphash_test.cc.obj crypto\CMakeFiles\crypto_test.dir\test\file_test_gtest.cc.obj crypto\CMakeFiles\crypto_test.dir\thread_test.cc.obj crypto\CMakeFiles\crypto_test.dir\trust_token\trust_token_test.cc.obj crypto\CMakeFiles\crypto_test.dir\x509\x509_test.cc.obj crypto\CMakeFiles\crypto_test.dir\x509\x509_time_test.cc.obj crypto\CMakeFiles\crypto_test.dir\x509v3\tab_test.cc.obj /out:crypto\crypto_test.exe /implib:crypto\crypto_test.lib /pdb:crypto\crypto_test.pdb /version:0.0 /machine:x64 /nologo /debug /INCREMENTAL /subsystem:console crypto\test\test_support_libd.lib crypto\test\boringssl_gtest_maind.lib crypto\test\test_support_libd.lib dbghelp.lib crypto\cryptod.lib ws2_32.lib boringssl_gtestd.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib /MANIFEST /MANIFESTFILE:crypto\CMakeFiles\crypto_test.dir/intermediate.manifest crypto\CMakeFiles\crypto_test.dir/manifest.res" failed (exit code 1120) with the following output:
asn1_test.cc.obj : error LNK2001: unresolved external symbol BASIC_CONSTRAINTS_it

crypto\crypto_test.exe : fatal error LNK1120: 1 unresolved externals

The test target thinks that it exports this variable due to BORINGSSL_IMPLEMENTATION being defined. Ugh, that's what you get for using add_definitions() in the project directory instead of target_compile_definitions.

I've successfully installed the grpc port with boringssl on:

[x] x64-windows
[x] x64-windows-static
[x] x64-linux (Ubuntu-22.04)

I added the vcpkg-tool-go port (inspired by vcpkg-tool-nodejs). Should I revert the vcpkg_find_acquire_program(GO).cmake changes? Currently there is no other official portfile containing vcpkg_find_acquire_program(GO. Does that function need a deprecation marker? If that is the case I'd need some guidance on how to deprecate it.
Btw. IMO it doesn't make much sense that binary caching is enabled for vcpkg-tool-go as recompressing the ~100MiB archive takes a considerable amount of time and disk space.

@BillyONeal I need some feedback on how to proceed.

@BillyONeal I need some feedback on how to proceed.

I'm working on a spec for how we want this going forward, should have something for you in a few days.

Until we get a better workaround, I'm turning this PR into draft status for now. :)

@BillyONeal would it be acceptable if I split the find module compatibility changes (13cd1dcfc186d61a8c070e335e6fdfc5406e7035) into a seperate PR which can be merged independently of the boringssl/go version update?

@BillyONeal any news on the spec?
@FrankXie05 I rebased onto master including #31387 => this no longer depends on a different PR

I added the vcpkg-tool-go port (inspired by vcpkg-tool-nodejs). Should I revert the vcpkg_find_acquire_program(GO).cmake changes? Currently there is no other official portfile containing vcpkg_find_acquire_program(GO. Does that function need a deprecation marker? If that is the case I'd need some guidance on how to deprecate it.
Btw. IMO it doesn't make much sense that binary caching is enabled for vcpkg-tool-go as recompressing the ~100MiB archive takes a considerable amount of time and disk space.

We just separated it out, in order to reduce the pressure of maintaining vcpkg_find_acquire_program. We need to use it.

Btw. IMO it doesn't make much sense that binary caching is enabled for vcpkg-tool-go as recompressing the ~100MiB archive takes a considerable amount of time and disk space.

We just separated it out, in order to reduce the pressure of maintaining vcpkg_find_acquire_program. We need to use it.

This is only loosely related. Instead of installing and creating a real binary artifact, it is possible to provide an individual script function to acquire the tool when needed. The download would still go through asset caching.
It is now possible to add or change tools in vcpkg_find_acquire_program without rebuilding the world. The problem of vcpkg_find_acquire_program is the lack of versioning.

Dropping info:reviewed as this is still pending the tools PR.

I factored the port update into a separate PR and will leave this untouched as it can serve as an implementation reference for a future vcpkg-tool-go port.


Merge hardening bug fixes

Changes in this pull request
Integrate the latest c2pa-rs
Checklist

[x] This PR represents a single feature, fix, or change.
[x] All applicable changes have been documented.
[x] Any TO DO items (or similar) have been entered as GitHub issues and the link to that issue has been included in a comment.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 41.79%. Comparing base (17863bd) to head (1470524).
Report is 20 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

:exclamation:  There is a different number of reports uploaded between BASE (17863bd) and HEAD (1470524). Click for more details.
HEAD has 11 uploads less than BASE

Flag
BASE (17863bd)
HEAD (1470524)

12
1

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #260      +/-   ##
==========================================
- Coverage   48.68%   41.79%   -6.89%
==========================================
  Files           4        4
  Lines         684      756      +72
==========================================
- Hits          333      316      -17
- Misses        351      440      +89

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


Added missing comma to sommer17joss.bibtex

Description
A comma was missing in sommer17joss.bibtex which made the creation of index.html fail.

Closes #3077

Before you get started

[x] ☝ Create an issue to discuss what you are going to do

Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

[x] 🛠 This pull request has a descriptive title
[x] 🛠 Code is written according to the code quality guidelines
[x] 🛠 Documentation is available
[x] 🛠 Tests run successfully
[x] 🛠 The list of authors is up to date
[x] 🛠 Any changed dependencies have been added or removed correctly
[x] 🛠 All checks below this pull request were successful

To help with the number of pull requests:

🙏 We kindly ask you to review two other open pull requests in this repository

@esmvalbot Please run recipe_psyplot.yml


stop parsing symbol: double-quotes parse first, before variable substitution

Steps to reproduce
I am describing a wild use case here, but noticed this while reading about_Parsing doc, referring to the stop-parsing symbol.  The doc states that %% environment variable substitution occurs as well, as well as supports the pipe character to end the command.  I quickly determine that double quotes are also included in the parsing past the stop-parsing symbol.  The double quote parsing seems to apply before the variable substitution.
${env:hello" } = $env:homepath
cmd --% /k %hello" % | write-host

Never mind the /k, this was so I could see the result and test environment variables in CMD.  Funny thing, CMD destroyed the %CMDCMDLINE% dynamic variable, instead filling it with the error message instead of the command line.
Expected behavior
I expected CMD to get called, echo my home path, and then powershell would pipe the result back to write-host, all just for an example.  I expect the double-quote in the variable name to be treated only as part of the variable name, and not for string parsing through the rest of the command line.
Actual behavior
Instead, CMD tells me that write-host is not recognized as an internal or external command, operable program, or batch file.
Task manager indicates the command line to CMD was /k echo \Users\[user] | write-host
This indicates the double-quote in the environment variable expression was treated as capturing the pipe character.
I was attempting to provide support for the pipe handling in a fork of VS Code's PowerShell syntax scoping tmLanguage document, but this makes it really difficult to do right.
Environment data

> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      6.0.4
PSEdition                      Core
GitCommitId                    v6.0.4
OS                             Microsoft Windows 10.0.17134
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Now, this said, I can understand why what I expect is not what I get, but that doesn't help me not expect it.
When I first read about the stop-parsing symbol, I had the understanding that no more parsing occurred past it, and that is how VS Code's PowerShell syntax scoping treats it, but now I know that is not the case, and I actually think the --% symbol is worse at providing the solution than the problem it solves, because there is still behavior I cannot always account for.
At least in CMD scripting when I need to MAKE SURE a '%' gets passed, I can use two '%%', and the variable substitution is not conducted, but that doesn't even happen here; instead I got the substitution surrounded with '%'s.
At least using a regular native command construct in PowerShell, I know exactly how to escape it, and I know I have to do it if I move the command from another scripting engine, but the --% stop parsing symbol doesn't assure me that I can just not translate at all, and in some cases, may not even work.
So, I am not sure there is anything that can be fixed here, as its much more complicated than it would first seem.

Looks like this is the behaviour in Windows PowerShell too.
Compare the following:
> $env:banana = "Hi"
> cmd /c --% echo %banana% | Write-Output -OutVariable x
Hi
> $x
Hi

And
> ${env: " banana} = "Hi"
> cmd /c --% echo % " banana% | Write-Output -OutVariable x
'Write-Output' is not recognised as an internal or external command, operable program or batch file.

If you enter this interactively with PSReadLine enabled you can see that the insertion of a quote before the pipe causes the Write-Output to not register as a command name, so I'm guessing this is a bug where the tokeniser is still looking for a closing quote rather than being in "stop-parsing" mode and looking only for a | or a newline.

If you look in tokenizer.cs:2017 you will see that '"' is processed explicitly to allow '|' and '&&' to be included in the args to cmd.exe.  So there is still some level of processing going on after --%. This is easy enough (but breaking)  to change but is it worth it to lose the ability to use | and && in cmd cmds in favour of allowing double quotes in variables? (Is that really a common thing?). Certainly this is a docs issue as there is nothing about this behaviour in the docs at all: about_Parsing Overall, the doc'ed behaviour - consumes everything up to a newline might be better. You wouldn't be able to stream the output of the command into a pipeline, but you could still capture it in a variable. And | and && would still work for cmd.exe.

I've marked it as Issue-Discussion. Technically it's working as by design. Whether we want to keep that design is an open question. Perhaps this is a candidate for an Experimental flag.


Type guard variable code action adds if-else with parentheses

Description:
$title
In ballerina, the best practice is to avoid using parentheses in if-else.

Describe your problem(s)
Describe your solution(s)
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Fixed by #29337. Hence closing the issue


Add Promise polyfill

A saw, that many uses complaint about Promises. For example, we had issue here: https://github.com/yeoman/generator-gulp-webapp/pull/298#issuecomment-89821413
I think gulp-postcss must have polyfill to make users happy out of box.
/cc @w0rm

What about doing it in postcss itself, you could have something like this `var Promise = global.Promise || require('promise')

I afraid that browsers standalone build become too big.

What is the size of the smallest A+ promise implementation?

Answering my question: https://github.com/jakearchibald/es6-promise minified and gzipped is ~2.2k gzipped

Problem is that it is even not necessary for most browsers. But maybe I can ask standalone build to ignore Promise polyfill.

@w0rm all PostCSS is about 20 KB, so 10% extra size in sensible ;)

Its not extra, it is required to work in some environments. And I generally don't like the idea of having to change the environment itself in order for postcss to work.

Can I at least pass Promise in options instead of changing the globals?

Hm. Yeap, gulp-postcss must change global :(. OK, I will release version with polyfill.

PostCSS 4.1.3 now contains Promise polyfill. You can remove notice from README.md.


Fixed a typo in the readme example

horizontalGridSpacing was mentioned twice, one line should read   verticalGridSpacing: 16, // Vertical space between grid items

Hi,
Nice catch! Thanks for the contribution.


Create docHandle from existing UUID

We (like to) use automerge as addition to an already centrally DB-stored document- and that document has a UUID.
Would it be possible to add a second parameter uuid to
create<T>(initialValue?: T): DocHandle<T> {...}
and when given, then instead of calling
const { documentId } = parseAutomergeUrl(generateAutomergeUrl())
it would call
const { documentId } = createAutomergeUrlFromUuid(uuid)
We can assume that uuid is a UUID - and it can be checked by the repo code.
Or is there some rationale why you need to rely on your own generated UUID and not on externally generated UUIDs?
With the current setup we need to maintain another map to match automergeUrls to our own UUIDs

Hey! I get this question every once in a while. The short answer is that we deliberately do not support this because it created heaps of difficult-to-solve problems for people in the past related to ID reuse. I would recommend you record the automerge URL as a synthetic foreign key instead -- this gives you more flexibility in the event that you want to replace a document and protects you against a future where we change the ID format for whatever reason.
All this said, I totally understand the desire, and it's something we'll continue to consider as we work on the system... just probably not exactly in this way.

@pvh thanks for the details! Was only searching open issues and couldn't find - maybe you can add some comment into the code (and the README) that explains that the ID will always be determined by automerge, and also the explanation you wrote - then - at least I- would not have opened this issue in the first place ;-)


List on stackshare.io

Nice tool. Simplicity of this tool is great. Perhaps, it should be highlighted on stackshare.io

@weaktyper Why not. I just submitted Cabot there, let’s see what they say. Thanks for the suggestion!

Nice. 👍  I'll give it a star. :star:
BTW, Is there a plugin to collect all the logs and present them in a graph?

Nice. 👍  I'll give it a star. :star:
BTW, Is there a plugin to collect all the logs and present them in a graph?


[Feature Request]: A way to get the types for the provided icon collections

I think it would be very helpful if we can import the types of available icons to use to build a wrapper component which contains more logic to it.
<script setup lang="ts">
const props = defineProps<{
  /**
   * Available `Iconify` icons
   */
  name: string // 👈 Need a type to get autocomplete for provided collections icon names

   //.....
}>()

</script>
<template>
  <span :class="name"></span>
</template>

@egoist was this 1.1.3 release really related to this issue? If I understand correctly, @AbdallahAlhaddad was asking about type for icons names, not collections names. This is exactly what I'm trying to achieve. I have button component that has optional icon prop for icon name (icon class to be precise), and I also have this as string type, which is fine but not perfect. It would be great if I could somehow get type for my whole collection for warnings when name is wrong and autocomplete functionality.
For example
'i-solar-case-round-linear' | 'i-solar-scooter-linear' etc

I quickly made this as a "temporary" (wink wink) solution:
import fs from 'node:fs'
import { icons } from '@iconify-json/solar'

const names = Object.keys(icons.icons)

let result = 'declare global {\n'
result += '  type IconClass =\n'
names.forEach((name) => {
  result += `    | 'i-solar-${name}'\n`
})
result += '}\n'
result += 'export {}\n'

fs.writeFileSync('./src/icons.d.ts', result)

console.log('icons.d.ts has been successfully generated.')

So I'm simply generating types file. Again - not ideal, but it will be probably generated just once anyway so it's good enough. Of course this code will work for single collection (this is what I needed).

Update version for multiple collections:
import fs from 'node:fs'
import { getIconCollections } from '@egoist/tailwindcss-icons'

const collections = getIconCollections([
  'solar',
  'fa6-brands',
])

let result = 'declare global {\n'
result += '  type IconClass =\n'

Object.values(collections).forEach((collection) => {
  Object.keys(collection.icons).forEach((name) => {
    result += `    | 'i-${collection.prefix}-${name}'\n`
  })
})

result += '}\n'
result += 'export {}\n'

fs.writeFileSync('./src/icons.d.ts', result)

// eslint-disable-next-line no-console
console.log('icons.d.ts has been successfully generated.')

@chojnicki Thanks for your tip. I just updated README to link this issue.


Fix LICENSE and NOTICE

remove license redundantly mentioned in NOTICE
add disclaimer regarding third party APIs

do not yet merge this PR


Ownership of Feeder in the context of JsonParser

Issue
JsonParser taking a reference to Feeder makes it difficult to write abstractions that contain both the parser and the feeder, as this would cause the struct to be self referential. This brings difficulties in Rust.
Proposals
Proposal 1: Own Feeder
JsonParser should either take ownership of  Feeder, either through exclusive ownership or through shared ownership (Arc).
Proposal 2: Provide feeder at call site of next_event(..)
JsonParser should not own, or have a reference to, a Feeder. Instead the dependency can be provided when JsonParser::next_event(...) is called. This has the additional benefit of making the JsonParser non-generic, merely the next_event(..) method needs to be generic over Feeder.
Pull Request
Proposal 2 has been implemented and a pull request will be made.
Related issues
BufReaderJsonFeeder and AsyncBufReaderJsonFeeder have a similar issue, in that they contain an exclusive reference to a BufReader, instead of taking ownership.

Thanks for the proposals. I've just pushed a commit that implements the first proposal. As discussed in person, the second one will not be implemented.


How you update?

Updated on 14/5/2020: I will update this package by the end of this week

yes I found out that paypal SDK is deprecated https://github.com/paypal/PayPal-PHP-SDK I will try to check there new packages to see how I can re-implement it with the package


Improve sliding window background in README

Ideally, the background in the README should teach some of the basic concepts of sliding window aggregation. This material is covered in the linked tutorial and encyclopedia article, but that should be adapted to this repo.

I could contribute with some slides/images if it is desired. For example:

I have more

(It's from a presentation where I presented some different algorithms)


chore: [one click binding] gsheets query adaptor

Description
Developed Gsheets query generator for one click binding epic.
PR fixes following issue(s)
Fixes #23255
Type of change

New feature (non-breaking change which adds functionality)
Chore (housekeeping or task changes that don't impact user perception)

Testing

How Has This Been Tested?

[x] Manual
[x] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test sha=037900a1f25a640e86bb085a10f7c266a69b9eae

/build-deploy-preview env=release

/ok-to-test sha=c327e3cfdac4882e4001690e80ac2d06bcfd2b10

Observations @vsvamsi1

Not able to create a simple gsheet query via one click binding
https://www.loom.com/share/e516d58e97c34b1d9476a823422c74c1

'Table header Index' field is very compact and also very close to 'Connect Data' button

Sheet name is overflowing from property pane, we should either wrap or display the name of sheet instead of sheet link

"Connect data" button must be inactive until Sheet name is selected, as it is a mandatory field

/ok-to-test sha=472a1c2aba41d1c9394b59977f44a40a1b29218a

/build-deploy-preview env=release

Tested this PR and LGTM

Verified all callouts
Tried and tested with different Gsheets
Overall flow of one-click binding

/ok-to-test sha=5c088370ea28f438cdce42cc6ca64ae68b7f0d6c


Cross domain tracking with Snowplow mini

Hey guys,
Just set up a functionnal snowplow mini interface and can collect data from 2 external sites.
The only issue I have now is to track user between the 2 platforms.
network_userid  values are different and user_id is just empty while I have the  same sp_id in the cookies in debugger tools such as Fiddler or Chrome Console.

Thanks

Hey @mariusgold ! Our Discourse forums are the best place for support: http://discourse.snowplowanalytics.com/


Specifying a group_override dependent on a color_override doesn't work

For example,
local c = require('vscode.colors')
require('vscode').setup({
    color_overrides = {
        vscGray = '#ff0000'
    },
    group_overrides = {
        StatusLine = { fg = c.vscGray, bg = c.vscGray }
    }
}

This will display the status line as grey, not red.
This makes sense as we're accessing the old version of c.vscGray in the group_overrides table, but also it seems sensible to provide a way to add group overrides after adding colour overrides, to avoid this issue.
P.S. I really appreciate this new setup system! Very pleased to be moving my modifications over to the setup function over manually hacking at the files and hackily symlinking my new versions into the cloned repo...

In my opinion this should stay the behavior. When you pass StatusLine and use values from c, the var c still hasnt changed, so essentially you are passing StatusLine = { fg = '#222222', bg = '#222222' } (assuming vscGrey is '#222222').
Supporting something like this would mean that the user would need to pass something like StatusLine = { fg = 'vscGray', bg = 'vscGray' } (strings of color name instead of RGB values). the function would then need to detect if the value is a color name or RGB value and act accordingly.
I find this unintuitive and i personally dont like it when values can mean 2 different things. Adding a second API for this is also meh.
Though im not related to this project so I dont get to decide. just sharing my opinion.
If i were you i would either call the function twice - once for individual values and once for the group values, or just make a local var for every such color.


fix Error econtent to $econtent

econtent (seams to be an typo, throws a Fatal error
correkt ist to $econtent

This was fixed in https://github.com/meet-kinksters/php-matrix-sdk/blame/1efbade52d988bb427584ebfaa488a928246cc27/src/Room.php#L873 - sorry I didn't act on your PR sooner.


:sparkles: Introducing new features. Sentinel Support RedisDataSource…

… Dynamic Rule Configuration
Describe what this PR does / why we need it
Sentinel support  redisdatasource , but spring cloud alibaba  don't support it
https://github.com/alibaba/Sentinel/tree/master/sentinel-extension/sentinel-datasource-redis
Does this pull request fix one issue?
no , There are no related issue
Describe how you did it

RedisDataSourceProperties.  Provide common redis-server attributes,support SentinelMode/Standalone

RedisDataSourceFactoryBean. Construct the RedisDatasource, Sentinel required bean

edit sentinel-core-demo

Describe how to verify it

sentinel-core-example， add

   <dependency>
        <groupId>com.alibaba.csp</groupId>
        <artifactId>sentinel-datasource-redis</artifactId>
   </dependency>

RedisDatasource, Standalone Model

spring.cloud.sentinel.datasource.ds1.redis.host=<IP_ADDRESS>
spring.cloud.sentinel.datasource.ds1.redis.port=6379
spring.cloud.sentinel.datasource.ds1.redis.rule-key=key
spring.cloud.sentinel.datasource.ds1.redis.channel=channel
spring.cloud.sentinel.datasource.ds1.redis.rule-type=param_flow
spring.cloud.sentinel.datasource.ds1.redis.data-type=json

RedisDatasource, Sentinel Model

spring.cloud.sentinel.datasource.ds2.redis.nodes=<IP_ADDRESS>:26379,<IP_ADDRESS>:26380,<IP_ADDRESS>:26381
spring.cloud.sentinel.datasource.ds2.redis.master-id=mymaster
spring.cloud.sentinel.datasource.ds2.redis.rule-key=key2
spring.cloud.sentinel.datasource.ds2.redis.channel=channel2
spring.cloud.sentinel.datasource.ds2.redis.rule-type=flow
spring.cloud.sentinel.datasource.ds2.redis.data-type=json

Special notes for reviews
Redis哨兵（Sentinel）模式

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

cool, nice pr and we need it. I will review it soon.


Add an average time to close report

Add a report that shows, for each repo, how long it takes to close issues and pull requests.

Done.


Seo fixes dec1

Series of SEO fixes and redirects from a review.

:warning: Validation status: warnings

File
Status
Preview URL
Details

:warning:Warning

Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs-ref-conceptual/java-sdk-azure-concepts.md
:white_check_mark:Succeeded

docs-ref-conceptual/java-sdk-azure-get-started.md
:white_check_mark:Succeeded

[Warning] 'W:\rlkj-s\docs-ref-conceptual/java-sdk-azure-install.md' would be overwritten by redirection rule configured in master redirection file .openpublishing.redirection.json. Please remove the original file to resolve this warning.
[Warning] 'W:\rlkj-s\docs-ref-conceptual/java-sdk-azure-overview.md' would be overwritten by redirection rule configured in master redirection file .openpublishing.redirection.json. Please remove the original file to resolve this warning.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Scrolling speed bumps on homepage

/kind bug
Which area this bug is related to?

/area registry

What versions of software are you using?
Operating System:
Mac OS
Bug Summary
Describe the bug:
The devfile.io homepage has a couple scrolling 'speed bumps' or pauses. It slows down scrolling at certain points and helps you to notice the sections, but the effect is too strong and can make users think they can't scroll any further. At first I thought the page was having loading issues and missing the bottom, or that the footer had been removed.
To Reproduce:
Open the homepage in a narrowish browser window or on a phone (where the page will requiring scrolling down), on a device that has a trackpad or gesture control for scrolling (e.g. iPhone).
On my Mac laptop in Safari, if I do the normal gesture for scrolling down it stops with the four column feature section. If I go back to the top and try a little harder it'll actually go a little further but then come back to that section. I have to know there's something else and scroll again to see the bottom of the page.
On my iPhone I have the same problem going down; scrolling back up it stops at Why Devfiles and I have to push hard to see the top of the page.
Ping me if you can't reproduce and I'll screen-share.
Expected behavior
Scrolling should be smoother and never appear like you've reached the bottom or top of a page until you really have.

Closing issue. Tested https://www.devfile.io on my iPhone and didn't experience any snapping to certain sections. It smoothly scrolls the entire time.


[KOGITO-9290] Removing Owner references from generated objects

Description of the change:
In this PR we removed the owner references to the child objects because we can only perform this operating having the owner object ID. Since the workflow is not created yet, we can't possibly know. During the first reconciliation, thou, the operator will add this reference to the properties configMap, which is enough. The other generated CMs shouldn't have this reference since we won't reconcile or own them.
Motivation for the change:
See: https://issues.redhat.com/browse/KOGITO-9290
Checklist

[x] Add or Modify a unit test for your change
[x] Have you verified that tall the tests are passing?

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

@ricardozanini You have to probably regenerate your code.


Sponsor proposal fail request

[ ] Return failed respons if author cant sponsor proposal
[x] Dont add author address to coauthors again

its difficult to know whether a API proposal update is trying to just sponsor a proposal or update the content. Maybe we just only show sponsor proposal if the user is eligible after a frontend query?


Failing tests across all builds due to complex

master branch is failing tests.
I noticed this when building #55 but it seems to apply on master as well. Probably something to do with #99 being merged, although that was rebased prior to merge and the tests were all passing.
@grlee77 @kwohlfahrt any ideas?

dwtn and idwtn don't seem to respect complex data types. I think this is because the changes in #99 modified upcoef and downcoef, but as of #104 these are no longer used by dwtn/idwtn. Perhaps #99 was not rebased onto this prior to merge?

I see now. I got trigger happy with merging and should have waited to merge #99 before I merged #104. @grlee77 did rebase #99, but I merged #104 after he did that, leading to this problem.

should I submit a quick PR to fix complex for dwtn and idwtn based on current master then?

yes please!

Sorry, should've said I'd picked this up.

@kwohlfahrt.  no worries.  thanks for taking the initiative

Thanks both for quick response. I've learned a lesson about merging.


Add support for the list outside collaborators endpoint

I'm glad to hear that 😄

btw @mkobzik do you need a new release incorporating this change?

@BenFradet No, I don't.


Initial attempt at ES6ifing

Here is an unsolicited attempt to make an ES2015-tween. Hope you think it is useful, and would understand if it gets rejected. Included is a naive attempt at benchmarking the reformat, if it is any good it shows no negative impact of the reformating.

feedback @sole ?

@salzhrani Sorry no feedback yet - I have been really busy with something else.
Thanks for the attempt!
Feedback then! :-)

My idea was to separate stuff into other modules and have the top module require those (but I don't really know how I'd do that). So far the main tween.js file is huge and unwieldy and there's no way of knowing what's going on
The way tweens (the objects) work also is perhaps not the clearest; instead of carrying the confusing stuff over, it would maybe be interesting to see if we can use this (re)write to make it better instead of a literal port
I'm not too happy about having to check in a dist/ compiled version as they always get out of date
I'm also not sure about what do we test, do we test the source or the compiled? With which runtime? etc

And then for the obvious:

I would not use bower, let's really shed 'old stuff' for this new version
The README shows things that are outdated

I have updated the PR ... mainly splitting the library into separate modules, update the build and test scripts, use ESlint instead of JSHint.
For me the main issues with the current API are:

User is responsible for advancing the tween, Tween.update unless there is a use case for that the user should not worry about animation frames and updating the tween
Managing tween array, I do not see the benefit of adding and removing tweens from the update array. the user should be concerned with starting, stopping and pausing a tween.

besides that the API seems suffice.

@sole @salzhrani Look at My PR.
On npm using babel and webpack compiling minifed and source version takes less than 2-minutes.
It's time to move to ES6 version.
NOTE: It's starting, when we improve it together it will be better like emit instead of onUpdate, onStart or even new things.


Propose to remove outdated content from the AuthN/AuthZ Concept document

(Commonalities-related issue)
At the bottom of the AuthN/AuthZ Concept document, there are two CAPIF related sections, namely "CAPIF" and "API Gateway pattern and Capif overlap".  Table of content does not include them, and it seems these two sections are not part of Reference as CAPIF/3GPP is not referred to by any other part of the document.
I am not quite sure why these CAPIF related sections are there.  It would be better to remove them if they are not needed, or if they are needed, it would be better to add some explanation why they are there.

Agree that this content can be removed.

As AuthN-AuthZ is now under Id-Consent, I will open a similar issue there & provide a link here

https://github.com/camaraproject/IdentityAndConsentManagement/issues/47

Addressed in above issue, PR done.


nydus-image: add backend-config support to nydus-image unpack

The nydus-image unpack only support reading nydus blob from the blob files on local machine (by the argument blob) by now. This patch adds a new argument backend-config to this command to allow nydus-image unpack to read blob data from all kinds of backends.

How about using "-C, --config " instead? We are going to switch from "--backend-config" to "--config" and "--backend-config" will get deprecated.

How about using "-C, --config " instead? We are going to switch from "--backend-config" to "--config" and "--backend-config" will get deprecated.

@jiangliu But I think this will be conflict with the backend in the Config when load rafs. https://github.com/dragonflyoss/image-service/blob/master/rafs/src/metadata/mod.rs#L685

How about using "-C, --config " instead? We are going to switch from "--backend-config" to "--config" and "--backend-config" will get deprecated.

@jiangliu But I think this will be conflict with the backend in the Config when load rafs. https://github.com/dragonflyoss/image-service/blob/master/rafs/src/metadata/mod.rs#L685

Are you going to support this usage scenario?

nydus meta blob has already been extracted to a local directory
nydus data blobs haven't been downloaded to the local directory

How about using "-C, --config " instead? We are going to switch from "--backend-config" to "--config" and "--backend-config" will get deprecated.

@jiangliu But I think this will be conflict with the backend in the Config when load rafs. https://github.com/dragonflyoss/image-service/blob/master/rafs/src/metadata/mod.rs#L685

Are you going to support this usage scenario?

nydus meta blob has already been extracted to a local directory
nydus data blobs haven't been downloaded to the local directory

Yes.
For example, by now, when we use the coverter.Unpack method in nydus-snapshotter to unpack a nydus image layer, we need to extract both the bootstrap part and the blob data part to the local disk first to allow the nydus-image to read to blob data (use the localfs backend). But with this patch, we can just need to extract the bootstrap part and set up a local http server to serve the blob data part. Then the backend-config can be used to pass the information about this local http server.

How about using "-C, --config " instead? We are going to switch from "--backend-config" to "--config" and "--backend-config" will get deprecated.

@jiangliu But I think this will be conflict with the backend in the Config when load rafs. https://github.com/dragonflyoss/image-service/blob/master/rafs/src/metadata/mod.rs#L685

Are you going to support this usage scenario?

nydus meta blob has already been extracted to a local directory
nydus data blobs haven't been downloaded to the local directory

Yes.
For example, by now, when we use the coverter.Unpack method in nydus-snapshotter to unpack a nydus image layer, we need to extract both the bootstrap part and the blob data part to the local disk first to allow the nydus-image to read to blob data (use the localfs backend). But with this patch, we can just need to extract the bootstrap part and set up a local http server to serve the blob data part. Then the backend-config can be used to pass the information about this local http server.

Can we let nydusd to handle the bootstrap part too?

How about using "-C, --config " instead? We are going to switch from "--backend-config" to "--config" and "--backend-config" will get deprecated.

@jiangliu But I think this will be conflict with the backend in the Config when load rafs. https://github.com/dragonflyoss/image-service/blob/master/rafs/src/metadata/mod.rs#L685

Are you going to support this usage scenario?

nydus meta blob has already been extracted to a local directory
nydus data blobs haven't been downloaded to the local directory

Yes.
For example, by now, when we use the coverter.Unpack method in nydus-snapshotter to unpack a nydus image layer, we need to extract both the bootstrap part and the blob data part to the local disk first to allow the nydus-image to read to blob data (use the localfs backend). But with this patch, we can just need to extract the bootstrap part and set up a local http server to serve the blob data part. Then the backend-config can be used to pass the information about this local http server.

Can we let nydus-image to handle the bootstrap part too? That's a feature I expect, then nydus-image can process remote images.

How about using "-C, --config " instead? We are going to switch from "--backend-config" to "--config" and "--backend-config" will get deprecated.

@jiangliu But I think this will be conflict with the backend in the Config when load rafs. https://github.com/dragonflyoss/image-service/blob/master/rafs/src/metadata/mod.rs#L685

Are you going to support this usage scenario?

nydus meta blob has already been extracted to a local directory
nydus data blobs haven't been downloaded to the local directory

Yes.
For example, by now, when we use the coverter.Unpack method in nydus-snapshotter to unpack a nydus image layer, we need to extract both the bootstrap part and the blob data part to the local disk first to allow the nydus-image to read to blob data (use the localfs backend). But with this patch, we can just need to extract the bootstrap part and set up a local http server to serve the blob data part. Then the backend-config can be used to pass the information about this local http server.

Can we let nydus-image to handle the bootstrap part too? That's a feature I expect, then nydus-image can process remote images.

@jiangliu Yes, I think we can.
We need to implement the logic of extracting the bootstrap and blob data from the whole nydus image layer (which is implemented in nydus-snapshotter by now) and let the caller tell nydus-image the loacation of the image layer by some argument (may be --image-path).
What's your option? @imeoer

How about using "-C, --config " instead? We are going to switch from "--backend-config" to "--config" and "--backend-config" will get deprecated.

@jiangliu But I think this will be conflict with the backend in the Config when load rafs. https://github.com/dragonflyoss/image-service/blob/master/rafs/src/metadata/mod.rs#L685

Are you going to support this usage scenario?

nydus meta blob has already been extracted to a local directory
nydus data blobs haven't been downloaded to the local directory

Yes.
For example, by now, when we use the coverter.Unpack method in nydus-snapshotter to unpack a nydus image layer, we need to extract both the bootstrap part and the blob data part to the local disk first to allow the nydus-image to read to blob data (use the localfs backend). But with this patch, we can just need to extract the bootstrap part and set up a local http server to serve the blob data part. Then the backend-config can be used to pass the information about this local http server.

Can we let nydus-image to handle the bootstrap part too? That's a feature I expect, then nydus-image can process remote images.

How about using "-C, --config " instead? We are going to switch from "--backend-config" to "--config" and "--backend-config" will get deprecated.

@jiangliu But I think this will be conflict with the backend in the Config when load rafs. https://github.com/dragonflyoss/image-service/blob/master/rafs/src/metadata/mod.rs#L685

Are you going to support this usage scenario?

nydus meta blob has already been extracted to a local directory
nydus data blobs haven't been downloaded to the local directory

Yes.
For example, by now, when we use the coverter.Unpack method in nydus-snapshotter to unpack a nydus image layer, we need to extract both the bootstrap part and the blob data part to the local disk first to allow the nydus-image to read to blob data (use the localfs backend). But with this patch, we can just need to extract the bootstrap part and set up a local http server to serve the blob data part. Then the backend-config can be used to pass the information about this local http server.

Can we let nydus-image to handle the bootstrap part too? That's a feature I expect, then nydus-image can process remote images.

@jiangliu Yes, I think we can.
We need to implement the logic of extracting the bootstrap and blob data from the whole nydus image layer (which is implemented in nydus-snapshotter by now) and let the caller tell nydus-image the loacation of the image layer by some argument (may be --image-path).
What's your option? @imeoer

We may discuss offline. I hope we can enhance nydus-image to directly handle remote image, the same to nydusd.

Does this work for you?
nydus-image unpack -C nydusd.conf --outputb image.tar.gz path/to/bootstrap.file

Does this work for you?
nydus-image unpack -C nydusd.conf --outputb image.tar.gz path/to/bootstrap.file

NO. The argument --bootstrap is required.

Does this work for you?
nydus-image unpack -C nydusd.conf --outputb image.tar.gz path/to/bootstrap.file

NO. The argument --bootstrap is required.

With nydus 2.2, the "--bootstrap" option for nydus-image unpack should be optional:)
I simplified it by making "--bootstrap" optional.


Added myself as a developer

Description
Added myself as new developer. (github:CodeMonk, Artifactory:codemonky)
Github Repo: https://github.com/jenkinsci/bitbucket-plugin
Submitter checklist for changing permissions
I need someone to review - I spoke with Felix (https://github.com/fbelzunc), but I can't seem to find him here with a mention.
@aheritier
@imod
@fbelzunc
@ndeloof
Also, if you'd like me to remove any of the mentions above from the permissions file - for example, fbelzunc did not seem to match a user here . . . I'd be happy to.

Always

[x] Add link to plugin/component Git repository in description above

When adding new uploaders (this includes newly created permissions files)

[x] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[x] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[x] All newly added users have logged in to Artifactory at least once

At least the checks passed this time! I was a bit worried ;)

👍


chore(docs): add docs to create a new app route

The type of this PR is: Documentation

This PR adds docs on how to create a new route to the app. It covers global app routes and independent navigation container specific routes
#nochangelog

Warnings

:warning:

✅ No changelog changes

  Generated by :no_entry_sign: dangerJS against 6cf6c3fb49c7fe862f196a0065ba9a77c88a0d52

@pvinis thanks for the comments, I just updated them all

Thanks for adding this Mounir 🙏


Reserve node resources for node services

Not quite ready for review, the ContainerManager needs some work to actually use the new generalized ExternalContainer.
This PR will not set any limits, it will only provide the means to reserve resources for node services.
/cc @rjnagal  @dchen1107
Will ping when more ready for review :)

Ping @rjnagal @dchen1107 this PR is now ready for review.
As it currently is, it is a refactoring that has no functional change. It does, however, set the groundwork for allowing external containers to reserve parts of the machine.
Ran e2e and it came back green!

Depends on #8681 btw, the first 3 commits are from that PR.

Added comments to the new patches.

All comments addressed PTAL @rjnagal and thanks for the review!

Rebased and pushed.

After our offline discussion I removed the last commit (no taking away from the capacity) and removed memory. PTAL @dchen1107 @rjnagal :)

#8681 gives us fully introspection stats on a given node, so that the user can understand the node better when the node is really overcommit through the monitoring pipeline. In a long run, those stats can help with capacity planning too. This one tries to apply some reservation to node services (not kubernetes daemons, not pods managed by kubernetes), but I have a real concerns real concerns, especially including it to 1.0 release:

The initial goal of this one is preventing us from overcommit and keep node stability. But I double this will achieve such goal. Resource limit is not mandatory in 1.0 release, most of users might not provide such information, and we don't have automated system to help them neither. In this case, applying some reservation to node services doesn't help us at all.
Another concern I had is that this PR subtracts reservation of /system from a node capacity at node level, and propagate such information to higher level. I think this will eventually make capacity planning harder. We had some experience with our internal system on this. I think with OSS, this will be even harder to manage for cluster admins.
Since capacity might change based on per node configuration introduced here, if the user does apply limit to their pods, they might wonder why my pods is not scheduled. Hiding such information at kubelet level makes explanation of why much harder. I would rather we have a policy for /system ready and controlled at cluster level, and pushed down to node, so that scheduler will respect /system reservation  against stable node capacity.
...

Edited after talking with @jnagal @vmarmol:
We agreed there is a value of this PR. I introduced LimitRange to cluster by default, which applies default cpu shares to all pods. But this is no way to apply configurable cpu.shares to /system based on node capacity. By default, /system will get 1024 value from kernel. The agreement we had:

Remove capacity change
Remove memory reservation from /system avoid accidentally applying to memory.

LGTM, just one q about the reservation (should be called limit :) ) calculation.
Will let Dawn put her LGTM since she has been looking at it too.

LGTM

Renamed to limit :)

@vmarmo am I right in thinking this is post-1.0

This PR has two features originally:

Allow system containers (e.g.: Kubelet, Docker-daemon, System) to have limits
Remove system container limits from capacity

The second is post v1.0 and was removed from the PR. The first is still relevant and for v1.0

@dchen1107 @rjnagal @erictune I think this PR is ready to be merged, let me know if that is not the case :)

I agree. @vmarmol could you please update the pr title to reflect the real change in it? Thanks!


Fix/not git cache

Codecov Report
Attention: Patch coverage is 20.00000% with 16 lines in your changes are missing coverage. Please review.

Project coverage is 41.90%. Comparing base (96733c3) to head (8dcfc7c).

Files
Patch %
Lines

lib/src/workflows/use_version.workflow.dart
13.33%
13 Missing :warning:

...b/src/workflows/resolve_dependencies.workflow.dart
25.00%
3 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #730      +/-   ##
==========================================
- Coverage   42.04%   41.90%   -0.14%
==========================================
  Files          64       64
  Lines        2985     2997      +12
==========================================
+ Hits         1255     1256       +1
- Misses       1730     1741      +11

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


Found a few problems for Laravel 5.5 + L-RF0.7

If select to "List View" then thumbs image path error
"/" Is missing in front of the thumbs image path

An error will occur if you change the sorting to "Type"
errorinfo:
[DOM] Found 2 elements with non-unique id #form3: (More info: https://goo.gl/9p2vKq)

3.The first time the sub-directory enters, the picture is not displayed,
Return to the upper directory and re-enter the picture to display
But i set filemanager_subfolder: './',  in tinymce.init
Can solve this problem.

Thanks for reporting this.
I don't really understand the relation between your Google link  and this issue.
I fixed your first point. Could you provide a capture or tell me the browser you are using  ? It would be easier to track the issue.
As for your third point :
The first time the sub-directory enters What steps have you done before that, so I could reproduce the error ?

Ok i just found out your second point, there is an issue with the sort function I can reproduce this.
I still don't know how to reproduce your third point.

3.The first time the sub-directory enters, the picture is not displayed,
Return to the upper directory and re-enter the picture to display
But i set filemanager_subfolder: './', in tinymce.init
Can solve this problem.

about  third point
I said earlier that you can set filemanager_subfolder:'./' to make corrections
But later I found out that I could not upload files.
I do not know why either @@


Installation fails on Ubuntu 18.04 running Ruby 2.6.3

The jaro_winkler gem is also failing to install and so I am not sure if the issue is with that gem or with Rubocop but wanted to report it. Rubocop installs just fine if I revert back to Ruby 2.5.3.
Building native extensions. This could take a while...
ERROR:  Error installing rubocop:
	ERROR: Failed to build gem native extension.

    current directory: /home/sjayanna/.rvm/gems/ruby-2.6.3/gems/jaro_winkler-1.5.3/ext/jaro_winkler
/home/sjayanna/.rvm/rubies/ruby-2.6.3/bin/ruby -I /home/sjayanna/.rvm/rubies/ruby-2.6.3/lib/ruby/site_ruby/2.6.0 -r ./siteconf20191018-14011-1xlq2d.rb extconf.rb
creating Makefile

current directory: /home/sjayanna/.rvm/gems/ruby-2.6.3/gems/jaro_winkler-1.5.3/ext/jaro_winkler
make "DESTDIR=" clean

current directory: /home/sjayanna/.rvm/gems/ruby-2.6.3/gems/jaro_winkler-1.5.3/ext/jaro_winkler
make "DESTDIR="
compiling adj_matrix.c
gcc: error: unrecognized command line option '-Wduplicated-cond'
gcc: error: unrecognized command line option '-Wmisleading-indentation'
gcc: error: unrecognized command line option '-Wrestrict'
gcc: error: unrecognized command line option '-Wimplicit-fallthrough=0'
Makefile:243: recipe for target 'adj_matrix.o' failed
make: *** [adj_matrix.o] Error 1

make failed, exit code 2

Gem files will remain installed in /home/sjayanna/.rvm/gems/ruby-2.6.3/gems/jaro_winkler-1.5.3 for inspection.
Results logged to /home/sjayanna/.rvm/gems/ruby-2.6.3/extensions/x86_64-linux/2.6.0/jaro_winkler-1.5.3/gem_make.out```

It seems that jaro_winkler gem installation failed. Could you please open the issue to jaro_winkler?
https://github.com/tonytonyjan/jaro_winkler/issues
/Cc @tonytonyjan

@koic Done. https://github.com/tonytonyjan/jaro_winkler/issues/31


fix dns parse error: rr.data could be nil

In my case, I found that payload
name: a.com
type: CNAME
class: 254(QCLASS None)   # [RFC 2136]
ttl: 0
data-length: 0
data: nil

it will report a error errDNSNameOffsetTooHigh in v1.1.19, and it will regard the next RR's name as this RR's CNAME value in v1.1.18.

@googlebot I signed it!

@googlebot I fixed it.

@googlebot  I fixed it.

Thanks!  And thanks for helping out googlebot :)

Would it be possible to add your original failure as a test case for DNS?

Would it be possible to add your original failure as a test case for DNS?

yes, I have added it.  #839


On MacOS 10.13, does not create config on install, does not index library

Installation completed without errors using Homebrew Python 3.7.5, using local storage as the source. At the end of install I get this message:

Initializing local index...
Synchronized 0 items.

However, the ~/.config/zotcli folder has not been created, and queries do not return any results.

Probably related to #46


markdown support

The issue in the notice is implemented with line break.
The notification format adopts markdown.

Hi, thanks for the PR. I think in markdown a proper line break() requires two spaces before the \n, so wouldn't adding two spaces before the \n be more in line with the markdown specification?

I tried using one line break and it runs fine.
What is the reason for using two line breaks?

I tried using one line break and it runs fine.
What is the reason for using two line breaks?

I don't mean that we need two line breaks, I mean that according to the markdown specs, we should put two spaces before the “\n”, some markdown implementations won't do it if the space is missing. (“line1  \nline2” instead of “line1\nline2”)
Another thing I'm concerned about is that the apprise supports multiple push channels, but if there is a channel that doesn't support markdown, will the send fail or will it be automatically converted to text? I just took a brief look at the apprise code but couldn't find an answer.

I will check if apprise supports converting HTML tags in text mode.

I tested bark, which supports \n newline characters but doesn't support HTML and markdown. Therefore, I think my current approach is not a good solution.
Generally speaking, apprise sets some additional parameters through URLs, but this involves handling the notification format, where it is necessary to distinguish between text and other formats of the body.

I have another question, does uptimeflare now support setting multiple notification types, that is setting multiple apprise URLs?

You should be able to separate multiple Apprise URLs with commas to send notifications to multiple targets at the same time.

As far as markdown support is concerned, I think text-formatted messages are more than enough to get the message across. Some notification channels may not be able to support markdown well (I've had problems with WeCom only being able to view markdown in WeCom client, and Wechat not being able to display markdown at all, which I find annoying).
So until a more advanced solution is introduced (such as allowing users to customize notification templates), I'm closing this PR for now.
Thanks for your contribution anyway!


fix: export types with valid paths

Closes #37

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


The 'Manage Access' dialog for one adls gen2 blob shows unfriendly

Storage Explorer Version: 1.11.1
Build: 20191206.5
Branch: dev/marayerm/electron7/packaging
Platform/OS: Windows 10/ Linux Ubuntu 18.04/macOS High Sierra
Architecture: ia32/x64
Regression From: Previous build (20191206.2)
Steps to reproduce:

Expand one ADLS Gen2 storage account -> Blob Containers.
Select one blob container which contains one blob at least.
Right click one blob and select 'Manage Access...'.
Check the Manage Access dialog.

Expect Experience:
The Manage Access dialog shows friendly.

Actual Experience:
The Manage Access dialog shows unfriendly.

More Info:

For ADLS Gen2 blob container & ADLS Gen2 folder, the Manage Access dialog shows like below.

Fix merged into feature/electron-7


Rework Syncer

What was wrong?

Syncer not started on status
we only query status once

How was it fixed?

syncer only starts on STATUS is acquired
We ask STATUS from all peers every 10 secs

To-Do

[ ] Clean up commit history

[ ] Add entry to the release notes

Cute Animal Picture

I tried a manual two nodes syncing a long-range of blocks and a few finalized epochs behind, the node that is behind will keep restarting the sync even if it has already imported all the blocks. The issue needs #1154 to fix.


Consider integrating with fluxcd for source tracking

If I understand the Pulumi Kubernetes operator correctly, it executes Pulumi updates by pulling code from Git from within Kubernetes.
For this application, you may want to consider integrating with FluxCD v2. It provides the tracking of Git repos for changes that appears to be missing from the Pulumi operator.

This is largely what is being tracking in #50, so I'll close this out as a dupe of that.  I added the more explicit note there that the likely approach we'll want to take is to build on the support for Git polling that already exists in a reusable form in Flux or Argo.

Breaking out the suggestion to use flux etc. from #50 here instead.
Some possibilities here include integrating with https://fluxcd.io/docs/components/source/gitrepositories/. This could allow users to choose to install the Flux Source Controller to use that or the Bucket source as a source for content that triggers reconciliation in the operator.

An added benefit here is to leverage support for a variety of source control providers which have been known to cause problems with go-git - the library that the underlying automation api uses for git integration. See #302 and #286 for instance.

Fixed in https://github.com/pulumi/pulumi-kubernetes-operator/pull/324


Debugging support

We're looking into integration Duktape, and one thing we want to make sure we have is debugging support, at least in the future.
At a basic level, if there were even just mechanisms to set breakpoints, that would be sufficient. We would just the existing facilities to "inspect" the current stack, etc.
Is this something that is on the roadmap, or that you would be agreeable to if somebody added it?

I will just dive in to show my interest in this feature. As @itay I also prefer the second solution allowing you to write remote debuggers and custom GUI as long as you can expose the protocol over a network. But that's what you meant when speaking about a protocol, didn't you?
Anyway, keep the good work up and thanks for this project. :+1:

Yes, the solution will be protocol oriented. The intent is to include a simple debugger GUI with Duktape so that everyone has access to it out of the box (and it can also be used to debug a custom target). But you can also write your own custom GUI which makes more sense when doing tighter integration. Stay tuned :-)

First merge is now in:

https://github.com/svaarala/duktape/commit/35a94045436e45fbc9748b2c0581680be82f3159

See the following to get started:

https://github.com/svaarala/duktape/blob/master/debugger/README.rst
https://github.com/svaarala/duktape/blob/master/doc/debugger.rst

The functionality in this merge is a baseline which includes all the major pieces of the debugger solution. There are a lot of small issues and bugs to round out before Duktape 1.2 release.

Oh god, that's awesome! I expected this to be released in less than a year and now you push the first pieces a day after I started to look into duktape. I will test this as soon as possible. :)

@Acconut Let me know how it works out :) It's quite barebones still. For instance, the web UI is pretty much a placeholder and will need to be reworked (proper syntax highlighting, etc).

I am really looking forward to setting aside some time to dig into this, wow, just WOW!
:+1:  :+1:  :+1:

I'm closing this one now because there's a minimal debugger in master now. Fixes and feature changes in separate issues.


HP-Probook 6470b - No Sound, Brightness Control, Battery display

Hi Chris,
I have been successful in installing Big Sur using the newest Creator tool: https://github.com/chris1111/HP-Probook-EliteBook-Package-Creator-OC/releases/tag/V1 . However, I do not have sound ,Brightness Control, Battery display.
Any idea how to fix it ?
I am really appreciating your work. It really helps the installing process less painful.

what is the exact model of your CPU because somes 6570b works on the HD 3000

CPU: Intel i5-3320M @2.6ghz

Delete EFI from SSD then Reboot from USB and retry, I hope you have an SSD, not a old mechanical toshiba HD
after that post here the EFI folder on ZIP file

I have disable bluetooth  and  wifi kexts. It works very well now . Thanks !


Add Builtin.type_join* family of functions.

These will be used for unit-testing the Type::join functionality in the
type checker. The result of the join is replaced during constraint
generation with the actual type.
There is currently no checking for whether the arguments can be used to
statically compute the value, so bad things will likely happen if
e.g. they are type variables. Once more of the basic functionality of
Type::join is working I'll make this a bit more bullet-proof in that
regard.
They include:
  // Compute the join of T and U and return the metatype of that type.
  Builtin.type_join<T, U, V>(_: T.Type, _: U.Type) -> V.Type

  // Compute the join of &T and U and return the metatype of that type.
  Builtin.type_join_inout<T, U, V>(_: inout T, _: U.Type) -> V.Type

  // Compute the join of T.Type and U.Type and return that type.
  Builtin.type_join_meta<T, U, V>(_: T.Type, _: U.Type) -> V.Type

I've added a couple simple tests to start off, based on what currently
works (aka doesn't cause an assert, crash, etc.).

@swift-ci Please smoke test


Implement RBAC checks on permissions

Privilege escalation is not current checked on permissions to pods, it should be.

any temporary work around for this ?

Reference https://github.com/rancher/rio/issues/378 instead which will be used for testing (duplicate).


SingleFunctionLighting support

This is still a draft.
Adding SingleFunctionLighting device class. Also an attempt to create an API for handling instance lists so I can test.
Not sure if this is the direction the project intends to go, so creating as a draft first to collect feedback.

Just saw the project changed structure; will close for now and reopen again following the new one.