Implement SPARQL graph store API

It might be convenient to implement SPARQL 1.1 Graph Store HTTP Protocol in Oxigraph server to allow easily fetching and updating the store content.

I have started to implement it. I consider providing the graph store API under the server /store path. @ktk does it seems relevant to you? I have never been a huge user of the "Graph Store" protocol.

I have started to implement it. I consider providing the graph store API under the server /store path. @ktk does it seems relevant to you? I have never been a huge user of the "Graph Store" protocol.

Good question, I have not seen a common pattern in stores so far.

Fuseki provides SPARQL Graph Store under /data by default while SPARQL Query is under /query.
Stardog supports multiple DBs and provides Graph Store via /dbname while SPARQL query is under /dbname/query.

/store works for me, it fits with the protocol spec name.

Good question, I have not seen a common pattern in stores so far.

Fuseki provides SPARQL Graph Store under /data by default while SPARQL Query is under /query.
Stardog supports multiple DBs and provides Graph Store via /dbname while SPARQL query is under /dbname/query.

/store works for me, it fits with the protocol spec name.

Done and released as part of Oxigraph 0.2. I have opened #72 about a missing feature.

Done and released as part of Oxigraph 0.2. I have opened #72 about a missing feature.


Fix Void's React build script

Right now, we're not able to import global libraries likeimport 'react' or we get an error. We're working around this by bundling all the files in react/src/*.tsx into files in react/out/*.js, and then importing these files elsewhere. See Contributing.md's node build.js for details. This is very annoying, especially because doing this crashes the build script and requires a rebuild.
We have two options to make it easier to compile React:

Figure out how to have global imports like 'react'. This was possible in vscode's previous yarn edition, but they recently changed to npm and removed this ability.
Or, keep our bundling technique and figure out how to make it not crash the build script. Modifying gulpfile.js is probably needed to do this approach.

Is 1. possible? If not, what's the easiest way to do 2.?

See the ui-improvements branch for everything I have so far. I'll keep this updated.

See the ui-improvements branch for everything I have.


az ml job create --set can not override inputs on pipelines

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az ml job create Extension Name: ml. Version: 2.4.1.
Errors:
Met error <class 'marshmallow.exceptions.ValidationError'>:Validation for PipelineJobSchema failed:

 {
  "input": [
    "Unknown field."
  ]
}

 If you are trying to configure a job that is not of type pipeline, please specify the correct job type in the 'type' property.
For a more detailed breakdown of the PipelineJob schema, please see: https://aka.ms/ml-cli-v2-job-pipeline-yaml-reference.
The easiest way to author a specification file is using IntelliSense and auto-completion Azure ML VS code extension provides: https://code.visualstudio.com/docs/datascience/azure-machine-learning
To set up: https://docs.microsoft.com/azure/machine-learning/how-to-setup-vs-code
Please check log in debug mode for more details.

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Use any example in the azureml-examples. In the example: cli\jobs\pipelines-with-components\basics\4a_local_data_input
az ml job create --file .\pipeline.yml --set input.pipeline_sample_input_string="hello parameter string" --web

Expected Behavior
Environment Summary
Windows-10-10.0.22000-SP0
Python 3.10.3
Installer: MSI

azure-cli 2.35.0 *

Extensions:
account 0.2.3
ml 2.4.1

Dependencies:
msal 1.17.0
azure-mgmt-resource 20.0.0

Additional Context

route to CXP team

Hi IsmaelGSerrano, seems the key following --set is wrong, should be inputs instead of input.

az ml job create --file .\pipeline.yml --set input.pipeline_sample_input_string="hello parameter string" --web

Yes, you are right. 😳


[Snyk] Upgrade html-snapshots from 2.9.0 to 2.10.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade html-snapshots from 2.9.0 to 2.10.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 2 versions ahead of your current version.
The recommended version was released 3 days ago, on 2023-09-21.

Release notes

Package name: html-snapshots

2.10.1 -<EMAIL_ADDRESS>

2.10.0 -<EMAIL_ADDRESS>

2.9.0 -<EMAIL_ADDRESS>

    from html-snapshots GitHub release notes

Commit messages

Package name: html-snapshots

3de9c84 Merge pull request #484 from localnerve/rc-2.10.1
5d02875 Merge pull request #485 from localnerve/snyk-upgrade-4b5be6f17a3a8894027be5cb238fb5be
8034c4d fix: upgrade html-snapshots from 2.9.0 to 2.10.0
e263eca @ 2.10.1 -<EMAIL_ADDRESS>bbb1ce0 Merge pull request #482 from localnerve/snyk-upgrade-9ac4fe2c2f40725432bffcd678ec2945
7b11ff7 fix: upgrade html-snapshots from 2.9.0 to 2.10.0
af68022 Merge pull request #481 from localnerve/rc-2.10.0
c5aafd0 @ 2.10.0 -<EMAIL_ADDRESS>e9ad037 Merge pull request #480 from localnerve/snyk-upgrade-eb364e8f89f9fa6a1034c752410930d0
d94b22f fix: upgrade html-snapshots from 2.8.1 to 2.9.0
c16c940 Merge pull request #479 from localnerve/snyk-upgrade-50f061b811e1baba5850edcc85739524
cd288a7 fix: upgrade html-snapshots from 2.8.1 to 2.9.0
166627b Merge pull request #478 from localnerve/snyk-upgrade-6f879d3902978bf16f5e634d6b1c5bf7
f8f8e00 fix: upgrade html-snapshots from 2.8.1 to 2.9.0
2cd015d Merge pull request #477 from localnerve/snyk-upgrade-6be002b032394ab9d66a5be61b010497
ef94a3c fix: upgrade html-snapshots from 2.8.1 to 2.9.0
45ecdde Merge pull request #476 from localnerve/snyk-upgrade-04b95044ac4df7d0265c84e734e7299d
a1ddee5 fix: upgrade html-snapshots from 2.8.1 to 2.9.0
32e7aca Merge pull request #475 from localnerve/snyk-upgrade-12ad006788a730d7609549bf6caaf569
bd6a4f2 fix: upgrade html-snapshots from 2.8.1 to 2.9.0
d91a7d2 Merge pull request #474 from localnerve/snyk-upgrade-d12aab7daaf431a86160a400be05a4c7
607a88c fix: upgrade html-snapshots from 2.8.1 to 2.9.0

Compare

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

coverage: 99.245%. remained the same when pulling 0fd707f995ac283f67b822d782ebc67c477806be on snyk-upgrade-739ff3aece9655af61c2d9651e7c70d2 into c9a32a94c40e5c7f93834a1dd37b70c698c42b73 on master.


Publish to Windows Package Managar (WinGet)

With every new release of Temurin JDKs/JREs, use a GitHub workflow to update manifests at https://github.com/microsoft/winget-pkgs repository.
The workflow will be added to every release repository:

Temurin8: https://github.com/adoptium/temurin8-binaries
Temurin11: https://github.com/adoptium/temurin11-binaries
Temurin16: https://github.com/adoptium/temurin16-binaries
Temurin17: https://github.com/adoptium/temurin17-binaries
Temurin18: https://github.com/adoptium/temurin18-binaries
Temurin19 (beta): https://github.com/adoptium/temurin19-binaries
Temurin20 (beta): https://github.com/adoptium/temurin20-binaries

Prerequisites:

https://github.com/microsoft/winget-pkgs will be required to be cloned under the organization or a personal account of a maintainer/bot like @eclipse-temurin-bot.
A GitHub Personal Access Token (PAT) will be needed to create pull requests to update manifests at https://github.com/microsoft/winget-pkgs. The token needs to be added as a repository secret to every repo. I know it's a bit hectic but it needs to be done only one time ;) Permissions required: public_repo and workflow.

Existing projects which use the action: https://github.com/search?q=vedantmgoyal2009%2Fwinget-releaser+path%3A.github%2Fworkflows%2F+language%3AYAML&type=Code&s=indexed&o=desc
P.S. I can create PRs for every repository.
Edit: Replaced extraneous reference of temurin18 with temurin19 (beta).

I've updated to add JRE too.

ping @gdams and @karianna for this issue

Any thoughts @gdams @karianna - are MSFT willing to support this?

This seems like the logical thing to do here. The manifests are currently being manually updated although it's not something that I've been doing myself.
I would say let's role this out for the 8-18 repos and see how stable it is

@gdams The internal CI which publishes GitHub releases can trigger the WinGet workflow programmatically after all 4 binaries have been published (JDK/JRE x64/x86) and pass the GitHub release tag with it (see https://docs.github.com/en/rest/actions/workflows#create-a-workflow-dispatch-event to how to do it).
References:
2. Docs about workflow_dispatch event: https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch/
3. Updates to workflow_dispatch: https://github.blog/changelog/2022-06-10-github-actions-inputs-unified-across-manual-and-reusable-workflows/

@gdams @karianna From some discussion in https://github.com/adoptium/temurin11-binaries/pull/11, I came to know that not all binaries are published along with the release. So, we might want to trigger the WinGet workflow from the internal CI which uploads Windows MSI binaries to GitHub.
Use GitHub CLI to create workflow_dispatch event: https://cli.github.com/manual/gh_workflow_run (we need to pass release tag to workflow, which we can do via JSON standard input, as mentioned in the docs)
Main Documentation: https://docs.github.com/en/rest/actions/workflows#create-a-workflow-dispatch-event
References:

Docs about workflow_dispatch event: https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch/
Updates to workflow_dispatch: https://github.blog/changelog/2022-06-10-github-actions-inputs-unified-across-manual-and-reusable-workflows/

Any progress on this? Using winget the latest versions are currently not available and therefore contain open CVEs (CVSS 7,5 iirc).

@gdams Let's discuss when we next meet up - not sure where this is these days.

I think this certainly makes sense to me. We'd have to ensure that the workflow supports multiarch packages (x64 and ARM64)


WIP - fix vote bugs

GOAL

fix "if I vote on one CGP, and then want to vote on a second one - cannot do it, just am shown 0 CELO"
fix " vote on a CGP with one wallet and then disconnect, but cant vote on same CGP because old vote is cached"

Current Status
Possibly more broken than before?

This looks good


[BUG] IndexError: list index out of range

I just try on win10 and ubuntu but all get issue IndexError: list index out of range
try to check url all ok

video links, and user home page link is different

video links, and user home page link is different

I use user home page link

video links, and user home page link is different

I use user home page link

do you show me see these home page links, please

video links, and user home page link is different

I use user home page link

do you show me see these home page links, please

Exp: https://v.douyin.com/FfTVJYQ/


Error messages (28)

Previously this code
{
   "indexP" : 0,
   "newparam" : ${indexP}[${indexP}]
}

caused newparam to have string value '0[0]'.
With latest changes of the JsonPreprocessor this changes to newparam having integer value 0.
Both is wrong. The correct error message would be
TypeError: 'int' object is not subscriptable

Hello Holger,
The change for this ticket is pushed to stabi branch.
The error message now is: Exception: Could not resolve expression '${indexP}[0]'. Reason: 'int' object is not subscriptable
Thank you,
Son

Retest successful. Issue can be closed.


expose toggleConversation to the hosting page with js

related to #16
In order to achieve the same behaviour as when a user clicks on the Launcher, it would be awesome to have access to the toggleConversation function as well. Would you be open to that?

Hey @amn41, WebChat.toggle(), WebChat.isOpen(), WebChat.isVisible   already exposed

thanks @znat  - as far as I can tell though, WebChat.toggle just toggles whether the window is open, and doesn't call the actually toggleConversation function which triggers the initPayload . Should it?

@dliuproduction?

@dliuproduction @znat I'm happy to take a look at this if you point me in the right direction :)

@amn41 I think this is going to be de facto fixed with #24


can't add hover style to .mm-counter digits

I can style the counter digits by targeting .mm-counter {color:#333 !important} in the CSS, but I can't for the life of me add a hover style. I want to be able to show a different color when you hover over the digits in the counter.
I've tried styling in CSS:
.mm-counter:hover {color:#F00 !important};
em.mm-counter:hover {color:#F00 !important;}
.mm-menu ul li em:hover {color:#F00 !important;}
...and others that I can't remember at the moment.
I've tried styling it via jQuery like this:
	$('.mm-counter').hover(function(){ 		$(this).css('color', '#F00'); 	});
I've also tried adding a class to .mm-counter via jQuery and applying a hover to it that way. While it does add the class...it ignores the hover style.
Basically, I can style the heck out of the  EXCEPT for hover.
How can I achieve this?
Thanks!

This is because the .mm-counter has a lower z-index than the  (or ). Try adding this CSS:
.mm-counter {
   z-index: 3;
}

Should do the trick.

Ugh - stumbled by something so simple. Perfect - thank you.

Hmm - a side effect to increasing the z-index is that clicking on the counter digits no longer advances into the sub-menu :/ Now you can only see sub-menu by clicking the ::after icon ">"

I don't think you can have both. I'm going to close this issue as it is not an issue with the mmenu plugin but more a general HTML/CSS question.


Import performance metrics and alarm

We need to define a performance metric that is easy to understand and measure and that we can track over time. Then we shall implement an alarm that is raised when crossing a given threshold.
My suggestion is to use the throughput defined as size / time (already in place, but not tracked over time).
Mind that the metric can have a lot of variance.

Ooops, sending a comment I wrote this morning and was lost in one of my tabs. Not really interesting but for the record.
Adding some thoughts from this morning here after several benchmarks:
The CartoDBFytime has a really small variance (1s in about 30 uploads of files of 1M rows) for the same kind of uploaded files, but the total import time has a big variance with the same kind of file and schema. With different schemas the variance keeps growing, and even more with different file types.
We are storing the "type" of the import, which is the format of the file and can suppose time differences. The amount of columns in a table is going to have an effect in the import time also. We somehow can detect the "amount of columns" if we're taking into account the size of the files, but there's other metric we have: importer_rows, so we could even think in terms of "time per row". It's really difficult to get something here because of the different files that can be imported.
We might want also to retrieve ogr2ogr times.
Something interesting could be to get the percentage of failures in terms of error codes, so you can know at a glance if the amount of failures is alarming or not depending on what is failing. (Where you can see if the errors are mostly due to limits, to clear user errors or to other exceptions that can perhaps be improved)

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


Move tags.py to contrib/taggit.py?

Shows taggit support is optional
Gives space for other tagging systems to be supported
Removes non-essential stuff from the core part of modelcluster

PR #22 addresses this


Add proper content-type for local.adguard.org/cert

Content-type header must be application/x-x509-ca-cert for certificate download request.

core/pull-requests/1274


Use a larger runner for Windows test jobs

From 8 to 16 cores, 32 to 64 GB ram. Testing on Windows first because it's the bottleneck.
Previously tested in #2515 to no effect, maybe better now that we have a development drive?

From 9m 21s to 6m 17s, nearly entirely in the cargo test step.


Bad $sourcePath for bower folder

ChosenAsset.php
public $sourcePath = '@vendor/bower/chosen';
ChosenBootstrapAsset.php
public $sourcePath = '@vendor/bower/chosen-bootstrap';
You should use alias '@bower' not '@vendor/bower' because at least my composer installed all bower assets under 'vendor/bower/bower-assets'. And this was the problem because your extension was looking into wrong path (vendor/bower/chosen but actual path is vendor/bower/bower-assets/chosen).
Yii2 creates @bower alias automatically when bootstrapping that corresponds to current application.
All my other third-party extensions are also using '@bower' instead of '@vendor/bower'.

Create a PR, please.

Hey
Sorry but i'm not actually familiar with GIT. I installed this extension
via composer.
2016-06-07 16:30 GMT+03:00 RomeroMsk<EMAIL_ADDRESS>
Create a PR, please.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/RomeroMsk/yii2-chosen/issues/12#issuecomment-224280363,
or mute the thread
https://github.com/notifications/unsubscribe/AD1bFWo40ByHsZT96ESsyaN_Reg4dTd6ks5qJXJigaJpZM4Iv658
.

Fixed.


package:media_kit_native_event_loop

I don't have much time to document how it'd work, implementation should be self-explanatory.
A drop-in solution to resolve the issue. Simply adding the package to pubspec.yaml will allow customers to use more than 8 instances of Player simultaneously without any issues. package:media_kit will switch to this implementation automatically if the shared library generated by this target is found. Otherwise, it will fallback to default Isolate based event handling.
dependencies:
  media_kit_native_event_loop: ^1.0.0

Closes #40.

This also adds a new API to disable events completely. It can further squeeze the performance if you don't rely on events.

Note

You can disable event callbacks for a Player & save yourself few CPU cycles.
By default, events is true i.e. event streams & states are updated.

final player = Player(
  configuration: PlayerConfiguration(
    events: false,                              // default: true
  ),
);

And... yeah obviously we're no longer limited to just 7 simultaneous Players.
The test application is now rendering 20 HD videos simultaneously on my integrated GPU.

@DomingoMG, you should try adding this to your project.
You shouldn't see that 8 Players lag/deadlock anymore. I tried to reach you, maybe you aren't that active on Discord.
Thanks!


[AKS] az aks create/update: Add --nat-gateway-managed-outbound-ip-count and --nat-gateway-idle-timeout to support nat gateway integration

Signed-off-by: MartinForReal<EMAIL_ADDRESS>Description
Add nat gateway integration for aks service
Testing Guide
az aks create -g MyResourceGroup -n MyManagedCluster --nat-gateway-managed-outbound-ip-count 1 --nat-gateway-idle-timeout 4 --outbound-type managedNATGateway

az aks update -g MyResourceGroup -n MyManagedCluster --nat-gateway-managed-outbound-ip-count 2 --nat-gateway-idle-timeout 10`

History Notes
[AKS] az aks create: Add --nat-gateway-managed-outbound-ip-count and --nat-gateway-idle-timeout and Add managedNATGateway and userAssignedNATGateway to supported outbound type

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

acs

@MartinForReal,
Pelease fix style error to pass CI checks.

Sure I will.

/assign @zhoxing-ms Can I get a review for this pr? Thank you!


Make code base compatible with Python 3.

Problem
Code base requires additional alignment to be compatible with Python 3.
Solution

print statement to function.
subprocess.check_output in Python 3 returns result of type bytes,
expected str.

Testing
Added tox configuration to run nose tests for both 2.7 and 3.4.
Run command:
tox

-----------------------------------------------------------------------------
16 tests run in 857.3 seconds (16 tests passed)

...
16 tests run in 672.5 seconds (16 tests passed)
_______________________________________________________ summary _______________________________________________________
  py27: commands succeeded
  py34: commands succeeded
  congratulations :)

Pushed to PyPI as 0.5.9.  Thanks for the tox configuration.  That's a nice touch!

@todddeluca thanks, very cool!
I started to expand tox configuration a bit with prospector tool to make PEP8 and other checks but found strange behaviour in it so postponed =)


replace PSP installation condition

Signed-off-by: Matias Charriere<EMAIL_ADDRESS>
This PR:
Replaces capability check with values param for PSP CR installation
Towards https://github.com/giantswarm/giantswarm/issues/23400

Checklist

[x] Added a CHANGELOG entry

done. thank you!


pkg/fs: staticcheck

Closing this, see my comment here:

https://github.com/perkeep/perkeep/pull/1405#issuecomment-894727096


Add rel="noopener noreferrer" to links with target="_blank"

Hi, is it possible to add support for rel="noopener noreferrer" to links containing target="_blank" so that the Grav syntax can be used instead of something like: Link?
This is a security issue. The new page has access to your window object and can navigate your page to a different URL. More info here if needed: https://mathiasbynens.github.io/rel-noopener/

Just do this:
[your link](/your/link?target=_blank&rel=norefferer,noopener)


New model from same config not equal

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): YES
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): pip
TensorFlow version (use command below): 2.2.0
Python version: 3.7
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:

 nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2019 NVIDIA Corporation
Built on Fri_Feb__8_19:08:26_Pacific_Standard_Time_2019
Cuda compilation tools, release 10.1, V10.1.105

GPU model and memory: Nvidia MX110 2GB

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with:

TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)" v2.2.0-rc4-8-g2b96f3662b 2.2.0

Describe the current behavior
I created a basic model and saved its configuration using get_config()
Describe the expected behavior
I created a new model using the same configuration tf.keras.Sequential.from_config() and compared configurations of both, but both were not equal.
Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
import tensorflow as tf
from tensorflow.keras.models import Sequential
from tensorflow.keras.layers import Dense
import json
import numpy as np

# Build the model

model = Sequential([
    Dense(units=32, input_shape=(32, 32, 3), activation='relu', name='dense_1'),
    Dense(units=10, activation='softmax', name='dense_2')
])
config_dict = model.get_config()

model_same_config = tf.keras.Sequential.from_config(config_dict)
print('Same config:',
      model.get_config() == model_same_config.get_config())
print('Same value for first weight matrix:',
      np.allclose(model.weights[0].numpy(), model_same_config.weights[0].numpy()))

Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.

@ahmadmustafaanis
I have tried in colab with TF version 2.2.Please, find the gist here.You are also seeing the same behavior?.Thanks!

Yes, I am seeing same behavior. Instead, It should be
Same config: True
Same value for first weight matrix: False

Because we are making it from the same configuration

@ahmadmustafaanis
Can you please try with TF nightly versions and i am not seeing any issue.Please, find the gist here.Please verify once and close the issue. Thanks!

Yea, It is working in tf nightly. Can you fix it in tf2.2 too?

@ahmadmustafaanis
It is fixed in TF-2.3-rc0 as well.Please, find the gist here.You can use TF 2.3.Please,close this issue as the issue was fixed with TF 2.3 release.Thanks!


color: #d3d3d3 --really?

Your font color selection is so out of compliance with ADA, or any contrast level readable by anyone with even moderately diminished ability to perceive low contrast letters, it's not funny.
At #d3d3d3, your contrast ratio is 1.5; it should be at least 3.0.

The contrast ratio between #d3d3d3 and #283339 is 8.64, which conforms with WCAG AAA; a ratio of 1.5 would mean that the background would be white, which it isn't supposed to be.

My mistake, thanks for taking to the time to look at it and for your work on this site.


fix(marionette): generi-fy Backbone.Babysitter.map

Backbone.Babysitter.map comes from the Backbone.Collection.map mixin, which comes from the Underscore.map mixin, which has a generic implementation.

@jiaweihli thanks mate!


TracksList keyboard shortcuts are broken

up key
down key
enter key

I probably broke when refactoring TracksList component

Sorry, I've been distracted the past week. I'll take care of this now.


Use ContextVar to track Task-local Lock token

What do these changes do?
The Lock implementation in redis-py uses thread-local storage
so that multiple threads using the same Lock instance can
acquire the Lock from each other.
Thread-local storage ensures that each thread sees a different
token value.
Thread-local storage does not apply in the Task-based concurrency
that asyncio programs use. To achieve a similar effect, we need
to embed a ContextVar instance within each Lock and store the Lock
instance's token within the ContextVar instance. This allows every
Task that uses the same Lock instance to see a different token.
Thus, if both Task A and Task B refer to Lock 1, Task A can "acquire"
Lock 1 and block Task B from acquiring the same Lock until Task A
"releases" the Lock.
NOTE: The Python documentation suggests only storing ContextVar
instances in the top-level module scope due to issues around
garbage collection. That won't work in the current design of
Lock. For lack of a better alternative, and to preserve the
original design of Lock taken from redis-py, we have created
instances of ContextVar within instances of Lock.
Are there changes in behavior for the user?
Different from redis-py:

Users who wish to refer to a Lock's token must do so using lock.local_token.get().
We have to drop support for Python 3.6 to use ContextVar. Python 3.6 is EOL 23 Dec 2021. 🤷

Related issue number
Fixes #1040.
Checklist

[x] I think the code is well written
[x] Unit tests for the changes exist
[x] Documentation reflects the changes [NOTE: The internal state of the Lock, being the token, is not something current documentation discusses]
[x] If you provide code modification, please add yourself to CONTRIBUTORS.txt

The format is <Name> <Surname>.
Please keep alphabetical order, the file is sorted by names.

[x] Add a new news fragment into the CHANGES/ folder

name it <issue_id>.<type> (e.g. 588.bugfix)
if you don't have an issue_id change it to the pr id after creating the PR
ensure type is one of the following:

.feature: Signifying a new feature.
.bugfix: Signifying a bug fix.
.doc: Signifying a documentation improvement.
.removal: Signifying a deprecation or removal of public API.
.misc: A ticket has been closed, but it is not of interest to users.

Make sure to use full sentences with correct case and punctuation, for example:
Fix issue with non-ascii contents in doctest text files.

In the aredis lib, they used a install_requires if condition in the string to install contextvars package (a Python 3.5 port). Not sure if that'll be able to apply in pypy. Would be helpful to note in the README.md at the least

This won't work for the reasons detailed here: https://github.com/aio-libs/aioredis-py/issues/1040#issuecomment-889537152


How do I specify parameters when launching ollama from command line?

I saw something online that said to try ollama run llama2:13b -temperature 0.0  but that does not work. I am also interested in setting the seed, so rerunning will do the same process rather than doing something different each time. (e.g. on a classification task, sometimes it says valid/invalid, sometimes is says correct/incorrect. sometimes is it very verbose explaining why it made its decision. I want to find a terse method and stick with it.
Thanks in advance

I am not sure if there is another way of doing this, but you can make a custom modelfile.
ollama show llama2:13b --modelfile >> modelfile-name

Append settings to modelfile-name
It'll look something like this
# I don't have this model, so I don't know if this is the correct template
# The only important thing here is importing llama2:13b and your changes at the bottom

FROM llama2:13b
# base settings
TEMPLATE """
[INST] <<SYS>>{{ .System }}<</SYS>>

{{ .Prompt }} [/INST]
"""

PARAMETER stop "[INST]"
PARAMETER stop "[/INST]"
PARAMETER stop "<<SYS>>"
PARAMETER stop "<</SYS>>"

# your changes
PARAMETER temperature 0.0
PARAMETER seed 0

For more options check the docs https://github.com/ollama/ollama/blob/main/docs/modelfile.md
After saving run (you can use any name for your model)
ollama create model-name -f ./modelfile-name

thanks I will give that a shot.

Notice that you can set parameters from the prompt, after the chat has started
/set parameter  temperature 0

It would be interesting to pass the parameters directly on the ollama run model command line. Do you plan on implementing this?

Notice that you can set parameters from the prompt, after the chat has started /set parameter temperature 0

This (/set...) didn't work when I used it in a prompt file, that is, a file that gets fed into ollama STDIN instead of using the process interactively. e.g.
ollama run<promptfile.txt
Is instead it was interpreted as a literal prompt and the LLM responds with a summary of Rosa commands for me.
Is it supposed to? It would be a nice feature.


Location issue 86

Codecov Report

Merging #253 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master    #253      +/-   ##
=========================================
+ Coverage   98.59%   98.6%   +<.01%
=========================================
  Files         117     117
  Lines       12489   12561      +72
=========================================
+ Hits        12314   12386      +72
  Misses        175     175

Impacted Files
Coverage Δ

stix2/test/v21/test_location.py
100% <100%> (ø)
:arrow_up:

stix2/v21/sdo.py
93.75% <100%> (+1.91%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 69d2529...edfe0ba. Read the comment docs.

Thanks @khdesai!


Initialize notebook metadata in the correct place and in alphabetical order

For #10544, #10571

[ ] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
[x] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).
[ ] The wiki is updated with any design decisions/details.

Codecov Report

Merging #11016 into master will decrease coverage by 0.03%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master   #11016      +/-   ##
==========================================
- Coverage   60.77%   60.74%   -0.04%
==========================================
  Files         582      585       +3
  Lines       31774    31942     +168
  Branches     4522     4524       +2
==========================================
+ Hits        19312    19403      +91
- Misses      11476    11549      +73
- Partials      986      990       +4

Impacted Files
Coverage Δ

...tascience/interactive-ipynb/nativeEditorStorage.ts
48.48% <0.00%> (ø)

src/datascience-ui/react-common/arePathsSame.ts
75.00% <0.00%> (-12.50%)
:arrow_down:

src/client/common/utils/platform.ts
64.70% <0.00%> (-11.77%)
:arrow_down:

src/client/datascience/jupyter/jupyterWebSocket.ts
8.88% <0.00%> (-6.50%)
:arrow_down:

src/client/languageServices/jediProxyFactory.ts
29.62% <0.00%> (-6.38%)
:arrow_down:

src/client/testing/common/services/discovery.ts
81.81% <0.00%> (-5.69%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.66% <0.00%> (-2.23%)
:arrow_down:

src/client/common/application/applicationShell.ts
6.38% <0.00%> (-1.73%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
76.56% <0.00%> (-1.57%)
:arrow_down:

...client/datascience/kernel-launcher/kernelFinder.ts
75.70% <0.00%> (-0.94%)
:arrow_down:

... and 27 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b0877ca...bdf4940. Read the comment docs.

For the test failures, you might need to merge master.


Fixed 'ImmutableAttributeModification' error in remove_sysctl_param

The 'remove' action is attempting to reduce node['sysctl']['params'] store, which is a read-only store.   This is raising the ImmutableAttributeModification error and failing chef-client run
Description
This change will prevent 'remove' action from failing and correctly update 'sys_attrs' hash, which is used later as the attributes to persist.
Issues Resolved
https://github.com/sous-chefs/sysctl/issues/69

Thanks!


Update tsconfig.json example

React Native 0.63 requires iOS 10.x, and bundles a modern version of JSC on Android, we can update the JavaScript library version to es2017. That brings in declarations for:

Array.prototype.includes
Object.entries and Object.values
String.padStart and String.padEnd

Other links:

@tsconfig/react-native
react-native-community/react-native-template-typescript/tsconfig.json

Preview

https://deploy-preview-2796--react-native.netlify.app/docs/0.63/typescript
https://deploy-preview-2796--react-native.netlify.app/docs/0.64/typescript
https://deploy-preview-2796--react-native.netlify.app/docs/typescript
https://deploy-preview-2796--react-native.netlify.app/docs/next/typescript

@simek done


Add container-local registries

This adds container-local registries as discussed in https://github.com/hynek/svcs/discussions/44.
It needs a bit more docs, but happy to hear feedback on the direction & design @aedify-swi and @Tinche!
Rendered docs: https://svcs--56.org.readthedocs.build/en/56/core-concepts.html#container-local-registries

@aedify-swi sorry for bothering you again, but I've polished up the warning/example to your original problem and would love to know if it makes sense to you: https://svcs--56.org.readthedocs.build/en/56/core-concepts.html#container-local-registries

Splendid, thanks everyone!


Dead link for HikariCP on README

Amendment below:

HikariCP

For some reason I couldn't make a PR for it as I couldn't push change/branch upstream...
remote: Permission to vladmihalcea/flexy-pool.git denied to Aeonitis.

You need to fork the repository, make the change, and then send the Pull Request.


feat: improve font loading strategy

This is my first try on trying to improve loading times on the rebuild branch. What I'm doing is applying what is consider best practice on font loading.
The new observer module doesn't affect the initial bundle since it's dynamically loaded when the site component mounts. I also removed the code web font since is pretty much the same as the system one in Mac and saves as tons of KiBs.
This should eliminate the flash of invisible content that we have on the site right now.
An example here on how it looks when the fonts kicks off:

I've introduced some small css changes to prevent the stacking effect to be huge, but the loading times on the site should improve drastically. Also, once the SPA bundle kicks off, there's no stacking anymore since we are not reloading the site.
TODO:

Fix recalculation on TextRotater component for homepage.
Fix banner styles on mobile.

You'd get a simpler setup by serving the Google fonts from the docs server directly and using font-display: swap;
Further massive improvements can be gained by preloading the woff2 versions of those fonts.
If you want to improve the limbo state of unloaded web fonts, using Monica Dinculescus font style matcher will also get you a much smaller jump in text styles from limbo to loaded fonts

@Munter yeah I thought about all of that. I've used Monica's font swapper to better match this, and as tested in my machine both are pretty close.
About font-display, though it's still missing Edge and support is not that bad, it partially solves the problem I'm mentioning. Serving directly from Google Fonts still presents a render blocking resource, lazy loading the styles with the bundle prevents that and fontfaceobserver gives us all browser wide support for font switching.

I might have been unclear. I'm saying don't serve fonts it their CSS directly from Google fonts. Instead download the fonts to the docs repository and have the font face declaration be a part of the base CSS. Then preload the fonts, which now have a known URL. This will cut away the font loading limbo almost entirely

Oh yeah, sorry maybe I got it wrong @Munter. Yeah I agree though for now it sounds overengineering to me. My intention is for the users to have the content as fast as possible without having to wait for the web font to be loaded. We can later apply preconnect and preload strategies for sure.

I will close this since it was impossible to make the home apge animation work with font changing involved, but will work on it later with more time or maybe if we decide to change the design of the site.


Move repository to resgateio organization

Issue
The resclient respository is currently hosted under jirenius. But with the launch of resgate.io and the stable release, it should be moved to the resgateio organisation.

Resolved in #23


More edits to the workflow notebook

Disable DT pagination when printing drake plans.
Caution users about redundant serialization and suggest a temporary workaround.

cc @edgararuiz

I should probably spell out the more efficient / less convenient approach using file_in()/file_out() to track saved HDF5 model files. New commits forthcoming...

In https://github.com/sol-eng/tensorflow-w-r/pull/8/commits/47ddb29eead6abaf75cd05eccb26b031c57ef28d, I propose an alternative workaround to address https://github.com/richfitz/storr/issues/77#issuecomment-476275570. I think the optimal choice depends on whether serialization really is a bottleneck versus how much of a headache file_in() and file_out() become if we use them for every single model in the plan. I do not have an overall recommendation, so I would prefer to showcase both if that sounds good.

Yes, showcasing both sound good.  Should we merge this PR or do you have more commits to it forthcoming?

Glad we agree, Edgar. I will revisit this when I learn more about how these options play out in practice. I looked over the report again, and it is ready to merge from my end.

Thanks!


Brew installation on Linux

Hi, Homebrow is also an option to install packages on Linux (I personally use it for a lot of my packages).
It seems like stu only supports MacOS for brew installation; is it possible to add Linux support as well?

Added with https://github.com/lusingander/homebrew-tap/commit/cd946cea7543155921ba0e54d297ba876762f988
If we want to add other targets, we will need to consider the build settings separately.

Thank you @lusingander for this; I appreciate it.
I was wondering if it would be possible to install a statically built binary with brew? I'm installing stu on a Linux distribution with old GCC libs, and I'm getting this when I run it:
stu: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by stu)
stu: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by stu)
stu: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by stu)
stu: /lib64/libc.so.6: version `GLIBC_2.29' not found (required by stu)
stu: /lib64/libc.so.6: version `GLIBC_2.33' not found (required by stu)
stu: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by stu)
stu: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by stu)

Thanks for confirming.
And sorry, currently we only build dynamically linked binaries, we need to build and release statically linked binaries, and it would be nice to change the binaries we distribute with brew.


how i can download part of the dataset?

Without more detail I'm not sure I can help, make sure you read the instructions for downloading data: https://github.com/ImageMarkup/isic-cli#downloading-images.

the whole set of images takes tens of gigabytes. Can I upload part of the full data (meta data, mask, etc.)?

That's described in the readme I linked above.


Does this Use Angularjs

Hi
the name suggest AngularJs framework but i do not see any code related to it . Is it my misunderstanding ?

I am working on it.

I have not seen one piece of Angular code... maybe this repo should explain its status a bit more clearly:

"This is a AngularJS branch of the wonderful AdminLTE project, without a single line of Angular implementation yet".

That would save some people some time ;)

I am sorry, just after creation and the idea, I got busy and still its pending in todo list in order. I have plan to move onto AngularJs 2.0 Now.

and now?

Hi
Can you suggest how can we change this repo into angular version?

I have started working on it now. I will add basic app and routing mechanism this weekend. Hold on for a week until you can start pull requests. Thanks

Hi
When should we expect for a working app with the routing? Thanks and keep up with the good work :)

current status?

Just some days to go.. I have successfully added ngApp with Webpack and code will be available in TypeScript too. Yet the conversion of all pages and different components to directives will continue with your helps :-).

how can i inject a service (like my.service) into home.component class?

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @vladdenisov, @ballmdr, @adamBoualleiguie, @mohdhasnain902, @jonathanciapetti, @msp5382, @starbt


Support automatic scaling of workers, based on queue length

Should have hooks for, or provide ability to, scale number of workers up or down depending on number of messages in queue.
Algorithm should probably attempt to maintain a certain average processing time, bounded upwards by a price limit.
Heroku is the most interesting target right now, but support must be general
https://devcenter.heroku.com/articles/scaling
https://devcenter.heroku.com/articles/platform-api-reference#formation

See https://github.com/jonnor/guv


ci(lint): enable nolintlint and remove redundant comments

This PR enables nolintlint linter to check //nolint comments. Also, removes redundant //nolint: directives.

Can you explain a little bit more background why we want this linter and why the comments are redundant, please?

nolintlint is a Go static analysis tool to find ill-formed or insufficiently explained //nolint directives.  In other words, it allows us to search for mistakenly added //nolint comments.
When I enabled nolintlint and run golangci-lint I got the following lint issues:
❯ ./bin/golangci-lint run
cmd/prometheus/main.go:15:1: directive `// nolint:revive // Many unsued function arguments in this file by design.` should be written without leading space as `//nolint:revive // Many unsued function arguments in this file by design.` (nolintlint)
// nolint:revive // Many unsued function arguments in this file by design.
^
cmd/promtool/backfill_test.go:47:113: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
func queryAllSeries(t testing.TB, q storage.Querier, expectedMinTime, expectedMaxTime int64) []backfillSample { // nolint:revive
                                                                                ^
cmd/promtool/main.go:414:1: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
// nolint:revive
^
cmd/promtool/rules_test.go:38:145: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
func (mockAPI mockQueryRangeAPI) QueryRange(_ context.Context, query string, r v1.Range, opts ...v1.Option) (model.Value, v1.Warnings, error) { // nolint:revive
                                                                                ^
discovery/kubernetes/endpoints.go:14:1: directive `// nolint:revive // Many legitimately empty blocks in this file.` should be written without leading space as `//nolint:revive // Many legitimately empty blocks in this file.` (nolintlint)
// nolint:revive // Many legitimately empty blocks in this file.
^
discovery/kubernetes/endpointslice.go:193:28: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
                for e.process(ctx, ch) { // nolint:revive
                                         ^
discovery/kubernetes/ingress.go:91:28: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
                for i.process(ctx, ch) { // nolint:revive
                                         ^
discovery/kubernetes/node.go:99:28: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
                for n.process(ctx, ch) { // nolint:revive
                                         ^
discovery/kubernetes/pod.go:134:28: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
                for p.process(ctx, ch) { // nolint:revive
                                         ^
discovery/kubernetes/service.go:94:28: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
                for s.process(ctx, ch) { // nolint:revive
                                         ^
discovery/zookeeper/zookeeper.go:196:27: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
                        for range pathUpdate { // nolint:revive
                                               ^
promql/engine.go:2019:49: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
                for drop = 0; floats[drop].T < mint; drop++ { // nolint:revive
                                                              ^
promql/engine.go:2041:53: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
                for drop = 0; histograms[drop].T < mint; drop++ { // nolint:revive
                                                                  ^
promql/engine_test.go:1659:2: directive `//nolint:govet` is unused for linter "govet" (nolintlint)
        //nolint:govet
        ^
promql/functions.go:14:1: directive `// nolint:revive // Many unsued function arguments in this file by design.` should be written without leading space as `//nolint:revive // Many unsued function arguments in this file by design.` (nolintlint)
// nolint:revive // Many unsued function arguments in this file by design.
^
promql/parser/ast.go:58:2: directive `// nolint:unused` should be written without leading space as `//nolint:unused` (nolintlint)
        // nolint:unused
        ^
promql/parser/lex.go:14:1: directive `// nolint:revive // Many legitimately empty blocks in this file.` should be written without leading space as `//nolint:revive // Many legitimately empty blocks in this file.` (nolintlint)
// nolint:revive // Many legitimately empty blocks in this file.
^
promql/parser/parse.go:75:1: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
// nolint:revive
^
promql/parser/parse.go:663:94: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
                        for r.Start = n.LHS.PositionRange().End; isSpace(rune(p.lex.input[r.Start])); r.Start++ { // nolint:revive
                                                                                ^
promql/parser/parse.go:665:94: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
                        for r.End = n.RHS.PositionRange().Start - 1; isSpace(rune(p.lex.input[r.End])); r.End-- { // nolint:revive
                                                                                ^
promql/parser/parse_test.go:4039:2: directive `//nolint:govet` is unused for linter "govet" (nolintlint)
        //nolint:govet
        ^
scrape/target.go:148:2: directive `//nolint: errcheck` is unused for linter "errcheck" (nolintlint)
        //nolint: errcheck
        ^
scrape/target.go:150:2: directive `//nolint: errcheck` is unused for linter "errcheck" (nolintlint)
        //nolint: errcheck
        ^
storage/buffer_test.go:214:38: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
        for it.Next() != chunkenc.ValNone { // nolint:revive
                                            ^
storage/memoized_iterator_test.go:115:38: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
        for it.Next() != chunkenc.ValNone { // nolint:revive
                                            ^
storage/remote/azuread/azuread.go:50:29: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
type AzureADConfig struct { // nolint:revive
                            ^
template/template.go:184:32: directive `// nolint:staticcheck` should be written without leading space as `//nolint:staticcheck` (nolintlint)
                        "title":     strings.Title, // nolint:staticcheck
                                                    ^
tsdb/chunkenc/float_histogram.go:106:39: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
        for it.Next() == ValFloatHistogram { // nolint:revive
                                             ^
tsdb/chunkenc/float_histogram_test.go:160:40: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
        for itX.Next() == ValFloatHistogram { // nolint:revive
                                              ^
tsdb/chunkenc/histogram.go:117:34: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
        for it.Next() == ValHistogram { // nolint:revive
                                        ^
tsdb/chunkenc/histogram_test.go:165:35: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
        for itX.Next() == ValHistogram { // nolint:revive
                                         ^
tsdb/chunkenc/xor.go:102:29: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
        for it.Next() != ValNone { // nolint:revive
                                   ^
tsdb/errors/errors.go:28:43: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
func NewMulti(errs ...error) multiError { // nolint:revive
                                          ^
tsdb/head_test.go:14:1: directive `// nolint:revive // Many legitimately empty blocks in this file.` should be written without leading space as `//nolint:revive // Many legitimately empty blocks in this file.` (nolintlint)
// nolint:revive // Many legitimately empty blocks in this file.
^
tsdb/head_wal.go:14:1: directive `// nolint:revive // Many legitimately empty blocks in this file.` should be written without leading space as `//nolint:revive // Many legitimately empty blocks in this file.` (nolintlint)
// nolint:revive // Many legitimately empty blocks in this file.
^
tsdb/ooo_head_read.go:14:1: directive `// nolint:revive // Many unused function arguments in this file by design.` should be written without leading space as `//nolint:revive // Many unused function arguments in this file by design.` (nolintlint)
// nolint:revive // Many unused function arguments in this file by design.
^
tsdb/querier_bench_test.go:270:22: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
                                        for ss.Next() { // nolint:revive
                                                        ^
tsdb/querier_test.go:14:1: directive `// nolint:revive // Many unsued function arguments in this file by design.` should be written without leading space as `//nolint:revive // Many unsued function arguments in this file by design.` (nolintlint)
// nolint:revive // Many unsued function arguments in this file by design.
^
tsdb/wal.go:14:1: directive `// nolint:revive // Many unsued function arguments in this file by design.` should be written without leading space as `//nolint:revive // Many unsued function arguments in this file by design.` (nolintlint)
// nolint:revive // Many unsued function arguments in this file by design.
^
tsdb/wlog/reader_test.go:544:24: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
                        for reader.Next() { // nolint:revive
                                            ^
tsdb/wlog/wlog.go:974:1: directive `// nolint:revive // TODO: Consider exporting segmentBufReader` should be written without leading space as `//nolint:revive // TODO: Consider exporting segmentBufReader` (nolintlint)
// nolint:revive // TODO: Consider exporting segmentBufReader
^
tsdb/wlog/wlog.go:986:1: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
// nolint:revive
^
tsdb/wlog/wlog_test.go:167:20: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
                                for r.Next() { // nolint:revive
                                               ^
util/annotations/annotations.go:94:1: directive `//nolint:revive // Ignore ST1012` is unused for linter "revive" (nolintlint)
//nolint:revive // Ignore ST1012
^
util/runtime/statfs_default.go:75:2: directive `//nolint:unconvert // This ensure Type format on all Platforms` is unused for linter "unconvert" (nolintlint)
        //nolint:unconvert // This ensure Type format on all Platforms
        ^
util/treecache/treecache.go:119:30: directive `// nolint:revive` should be written without leading space as `//nolint:revive` (nolintlint)
                for range tc.head.events { // nolint:revive
                                           ^
util/zeropool/pool_test.go:152:17: directive `//nolint:staticcheck // This allocates.` is unused for linter "staticcheck" (nolintlint)
        pool.Put(item) //nolint:staticcheck // This allocates.
                       ^
util/zeropool/pool_test.go:158:18: directive `//nolint:staticcheck  // New pointer.` is unused for linter "staticcheck" (nolintlint)
                pool.Put(&buf) //nolint:staticcheck  // New pointer.
                               ^
web/api/v1/errors_test.go:14:1: directive `// nolint:revive // Many unsued function arguments in this file by design.` should be written without leading space as `//nolint:revive // Many unsued function arguments in this file by design.` (nolintlint)
// nolint:revive // Many unsued function arguments in this file by design.
^

I fixed all these issues in this PR and removed 19 unnecessary code lines.

Sorry I'm still missing why it is OK to delete the comments as you did.
Maybe we don't run the revive linter any more?

@bboreham you're right. There was a problem with revive's configuration. Fixed in #13068 13068


feat(global id field resolver): add optional id field options argument

accept an optional idFieldOptions argument that gets passed to the id field. allows the id field
complexity to be set

Pull Request Test Coverage Report for Build 146646858

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

Totals

Change from base Build 146633610:
0.09%

Covered Lines:
142

Relevant Lines:
144

💛  - Coveralls

Pull Request Test Coverage Report for Build 146674482
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

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

Totals

Change from base Build 146633610:
0.7%

Covered Lines:
142

Relevant Lines:
144

💛  - Coveralls

Pull Request Test Coverage Report for Build 146674482
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

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

Totals

Change from base Build 146633610:
0.7%

Covered Lines:
142

Relevant Lines:
144

💛  - Coveralls


Optimize collision checks with spatial hash

We should use something like a quad tree or just divide up the space into rectangles (like how DOOM does with blockmaps). This will allow to have enemies bounce off each other without having an O(n^2) time complexity for the checks. We will also be able to do really cool things like get the nearest entity of type "x" without having to check every entity.

I made this low priority because I still think the draw calls trump the collision checks by a lot in terms of resources.


upstream gl.vapi to GNOME/vala-extra-vapis

I think this VAPI should be included in https://gitlab.gnome.org/GNOME/vala-extra-vapis

Here is an alternative version that also looks good at first sight: https://github.com/robinhellen/vldraw/blob/master/vapi/gl.vapi
Either way I would also be very happy about an upstream version


[Feature] Ring implementation

Ring uses consistent hashing with the first key of the command to determine the request location. (Multi-key command will have issue using Ring).
#16 #14

Consistent hashing is meant to be implemented in the server, not in the client
The reasons behind it are:

Better replication management
Finger table management (routing information stored in each node)
Node joins/leaves/crashes

Please consider re-design based on the original consistent hashing if it is possible!

@duynguyen-ori75 Yes we acknowledge that.
However, in the first stage, we want to try to clone "Redis-Ring" feature which is a client sharding only (of course this will not be able to handle data loss due to node join/leave/crash). This is for the "simple thing comes first".
The next stage should be shard and replica on the server-side.
More context on this:
Ref: https://engineering.linecorp.com/en/blog/line-storage-storing-billions-of-rows-in-sharded-redis-and-hbase/

The entire LINE storage system started with just a single Redis cluster constructed from 3 nodes sharded on the client-side.

In 2011, LINE storage team adopt a similar approach "client shard", they then migrate to server-sharding and replication.

LGTM


[BUG] keygen with iOS not working

Describe the bug
When staring a keygen with iOS it is not possible to create a vault.
On windows it fails and on iOS it completes successful.
To Reproduce
Steps to reproduce the behavior:

initiate on windows
pair with iOS
do keygen
See error

Expected behavior
A consistent vault creation with iOS possible
Screenshots

Version 1.0.0

That also happens occasionally on M of N with androids


Export the module to make it RequireJS compatible.

Refer to the comment of @Diyahon here: https://github.com/sroze/ngInfiniteScroll/pull/252#issuecomment-186113787

Hey @sroze, is it possible to merge this pull request ? My current project is waiting for it.
Thanks a lot.

@dsnoeck please rebase/squash your changes

@dsnoeck also can you update the documentation, please

@graingert, I so you already have added the code for exporting the module. What more you want to add in the documentation ?

@dsnoeck sorry, I've already updated the documentation!


support for network congestion/bottlenecking test

OS: universal
Describe
Network Congestion is the situation which occurs when the entire bandwidth of the network is occupied. Any request in a congested network will be bound to get slow and sometimes may lead to time-out, resulting in termination of operations. The implementation can be carried out by using netstat.

To be implemented using Flood Ping here. So, we will kinda reuse the existing utils for Floodping.

@aquibbaig actually, it would be implemented via flood test rather than flood ping.

@Harkishen-Singh I would like to work on this issue. A little brief about a possible approach will be amazing.


Main Activity layout improved

@maniyaom are you able to sign in/signup in app?

@maniyaom are you able to sign in/signup in app?

I was already logged in


Add get Publications by accession end point

you only retrieve journal articles from an entry for getPublicationsByUniprotAccession service in PublicationService. Current website returns all publication beside journalArticle

you also include UniProtReference, need to read more

so you can merge to master


feat: notify users when arbitrum bridge claim is ready

Description
Triggers a one-off toast if ready arbitrum claims are detected. Includes changes to trade page routing (necessary for deep redirect) and improvements transition animations (nice to have).
~Additional effort was made to negate reliance on tx history per #7872 (i.e dig up stupid https://www.youtube.com/watch?v=b97zJxKEqAk )~ Nope we cannot do this yet.
Issue (if applicable)

closes #7835
Risk

High Risk PRs Require 2 approvals

Moderate risk, changes to trade page routing should be the main focus when reviewing.

What protocols, transaction types, wallets or contract interactions might be affected by this PR?

Testing

Can trade without issues
Can initiate a bridge without issues
Can claim without issues
Notification works and button redirects you to the clam page
Notification only fires once per page load

Engineering

Operations

[ ] :checkered_flag: My feature is behind a flag and doesn't require operations testing (yet)

Screenshots (if applicable)
Notification with redirect:
https://jam.dev/c/1bcb434c-0dd1-4657-8a07-05374e154e87
Transition animations hyperactive ADHD clickfest:
https://github.com/user-attachments/assets/6a6ac32c-de01-46c4-96b9-0b13053f4c4c

Couple qs and extremely pick of nits but overall looks perf! Tested locally:

Going from an account without claims to another with claims is happy ✅
https://jam.dev/c/2cab1cde-401d-4ef2-aacc-ea26115ce9db
Going from an account with claims to another is ❓
I guess we shall see in 6 days?

Initial load of an account with claims is happy ✅
https://jam.dev/c/f245bd9b-dca1-49ca-a77a-3c47ef8eb1b0
Pending claims aren't detected as ready ✅
https://jam.dev/c/989d8240-6b1f-409e-bbe3-27176a0fa483
Bridge Txs are still happy ❓ (not a regression)
https://jam.dev/c/184c8c4e-6551-4cea-865b-25a506ad7bb1
Noticing we still have wrong "Asset Received" messaging for Bridges here, which we should definitely tackle:

Good ol' EVM swaps are happy e2e:
https://jam.dev/c/8b256e1f-c689-4dff-beeb-caebbf9acbdc

@woodenfurniture one oddity I've found out on the Arbitrum Bridge dApp, which actually makes a lot of sense conceptually is their "You have x pending/claims" copy is incrementally fetching pending/claims, which may look odd for users there, but actually makes sense from a speed point of view.
Wondering if we could do something similar here in a follow-up: since we don't display the pending/claims count but only a "You have claims" copy, we don't need to fetch all. We could probably implement something fancy where the app-wide hook bails after the first found if any, and only the actual claims tab would fetch all (but still leverage the already incrementally loaded ones from app-wide hook).
We would also need to have granular loading states too (i.e if one/many is found but we're still loading, show them + some static skeletons as we don't know how many more there may be), but think that could reduce the spew/improve loading time for users with many claims, though counterpoint is "many claims" may be a rare enough flow that we don't want to spend more time on this, unless straightforward to implement?

I love this idea. Yes we should do this at some point especially if we remove the dependency on tx history. An more granular loading states would be a decent improvement on UX since users would be able to see their claims as they come in.


:robot: Triggering CI on branch 'release-next' after synching to openshift/master

/test 4.5-e2e

/test 4.5-e2e

/retest

/test 4.6-e2e

OCF Webhook is merging this PR


Fix 4.7 downscaling

Leaving in draft for now to control when we merge/deploy this

I'll deploy and monitor this tonight. It's easy to roll back in case there are problems.


#23 more elegant solution for clever dict.ignore

raise RuntimeWarning if a user tries to use '_aliases' as key word and '_aliases' is not a dict or an instance of AliasesDict
if save or delete are used as keywords the will be displayed in repr if not explicit ignored

Many thanks indeed for contributing Felix!  Really appreciated :)


Serenity.ListRequest not calling Endpoint class

I have a Grid class with this method:
protected onViewSubmit() {
// only continue if base class returns true (didn't cancel request)
if (!super.onViewSubmit()) {
return false;
}
//this.setTitle("Client Search Results");
        let request = this.view.params as Serenity.ListRequest;

}
When i click on the submit button its not sending the request to the endpoint. Its not calling the endpoint. What am i doing wrong here?
This method is not being called as well
protected onViewProcessData(response: Serenity.ListResponse<*****Row>): Serenity.ListResponse<****Row> {
alert('Total Count: ' + response.TotalCount);
return super.onViewProcessData(response);
}

If you don't return true from onViewSubmit it won't call service

Volkan,
the onViewSubmit is returning a true but it still doesnt call the list service. see below..
protected onViewSubmit() {
// only continue if base class returns true (didn't cancel request)
if (!super.onViewSubmit()) {
return false;
}
//this.setTitle("Client Search Results");
        let request = this.view.params as Serenity.ListRequest;
        Q.notifyInfo("Request:" + this.view.params);

        this.StartDate = $('#Tag1').find('input[name="StartDate"]').val();
        this.EndDate = $('#Tag1').find('input[name="EndDate"]').val();
        this.Progid = $('#Tag1').find('input[name="Progid"]').val();
        this.LocationId = $('#Tag1').find('input[name="LocationId"]').val();
        var search: any[] = [];

        //this.view.params = request;
        Q.notifyInfo("Program" + this.Progid);

        Q.notifyInfo("super.onViewSubmit():" + super.onViewSubmit());

        return true;
    }

Check if you have getGridCanLoad or script error somewhere. Grid editors won't call service.

No i dont. Thanks for your quick response. Ok let me explain to you what im trying to do.
I created a form and want to post the selections to server side and display the results in a grid. What would you advise i do?
see attached


Python 3.9 support

What do these changes do?

Add Python 3.8 and 3.9 to test matrix
asyncio.Task.all_tasks moved to asyncio.all_tasks in Python 3.7

Are there changes in behavior for the user?

Related issue number
Fixes #188
Checklist

[x] I think the code is well written
[x] Unit tests for the changes exist
[ ] Documentation reflects the changes
[ ] Add a new news fragment into the CHANGES folder

name it <issue_id>.<type> (e.g. 588.bugfix)
if you don't have an issue_id change it to the pr id after creating the PR
ensure type is one of the following:

.feature: Signifying a new feature.
.bugfix: Signifying a bug fix.
.doc: Signifying a documentation improvement.
.removal: Signifying a deprecation or removal of public API.
.misc: A ticket has been closed, but it is not of interest to users.

Make sure to use full sentences with correct case and punctuation, for example: Fix issue with non-ascii contents in doctest text files.

I was unable to find the CHANGES folder specified in the PR template. Is the template out of date or did I miss something?

Looks like I'm having the same issue here as in #169
Both tests and coverage appear to be quite unstable. Multiple runs produce different failures.

Also, it seems I'm getting ahead of myself - Python 3.9 has not yet been released!

Going to close this PR and open a new one for the fix to Travis that I came up with


Polish translation to push and fetchRebase chapters

Hi,
There's another chunk of Polish translation.
I've found that remote branch on fetchRebase level does not exist. Can you fix it?

Awesome! Thanks for the translation progress 👏

I've found that remote branch on fetchRebase level does not exist. Can you fix it?

What do you mean? are you saying the level has some bad data or that the string isnt translated in any files? can you add a screenshot?

Awesome! Thanks for the translation progress 👏

I've found that remote branch on fetchRebase level does not exist. Can you fix it?

What do you mean? are you saying the level has some bad data or that the string isnt translated in any files? can you add a screenshot?

Sorry, I assumed that remote tree should be visible too. To me 'git clone' command was a little bit misguiding. Now I see because of I need to learn more about git.


Text of moon phase covered by temp chart

8<------------------------ FEATURE REQUEST ------------------------------------
Missing feature
Description of the moon phase could overlap into TempChart. E.g. German "abnehmender Halbmond". Same solution as used for drawCurrentWeather could be applied. I.e. "covering" too long text with white rectangle.
Justification
Easy to fix, looks better.
Workarounds
No, it's just a cosmetical improvement.
8<------------------------ END FEATURE REQUEST --------------------------------

Maybe in this case it might be more sensible to adjust the text. Contrary to the weather description the text is under our control.

agreed


Can't create issue with 🐞 in title

Gogs version (or commit ref):
Git version:
Operating system:
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] SQLite

Can you reproduce the bug at https://try.gogs.io:

[x] Yes (provide example URL)
[ ] No
[ ] Not relevant

Log gist:

Description
This is tested in try.gogs.io. Can't provide link because issues doesn't get created. Easily reproducible, simply create a new issue, starting the topic with an emoji, and it will render a 500.
...

Do you mean Unicode emoji?

Yes, I assume. Like the lady bug on this issue.

Same happens if I try to use an emoji on repository description.

Regarding 500 with emoji on description, I can use it on my test install: https://git.quark.business/david/collantes.us, but on https://try.gogs.io is gives 500. Only difference is I am running <IP_ADDRESS>3 and try is newer. What do you think, @Unknwon?

I think it's MySQL encoding related, demo site is using default, and not all encoding supports Emoji.

@Unknwon ah! Makes sense, I am using SQLite.

I have a same error. And I try change the description column type to utf8mb4. But emoji charaters cause error yet.

this its not complete fix, in sqlite this does not work, and this limit the mysql installations to only mysql recents

Yes, it's fixed MySQL connection only. But the title not supports emoji yet. You can type emoji to the description.

so then the commit are unuseless and limit the installation to only newer ,mysql versions.. puff

Yes. You must change the columns type to utf8mb.


Error on startup

2017-07-08 23:33:50: ERROR[Main]: ModError: Failed to load and run mod "counter":
2017-07-08 23:33:50: ERROR[Main]: counter:init.lua:45: attempt to call field 'register_on_sending_chat_messages' (a nil value)
2017-07-08 23:33:50: ERROR[Main]: stack traceback:
2017-07-08 23:33:50: ERROR[Main]: 	counter:init.lua:45: in main chunk

Client build today, no other CSM loaded.

Changing minetest.register_on_sending_chat_messages  into minetest.register_on_sending_chat_message  fixed that for me and the mod runs well.

Fixed


Fixed random issue for test_one_shot

What does this PR do?

This PR fixed random issue for test_one_shot unit test.
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Might not work with Packer.nvim

@pavanscoding vim-plug is for vim, this is a lua plugin.

@jcdickinson I thought that vim-plug is also used for neovim as well?

@pavanscoding you might have to do something like this in your init:
luaeval("require'wpm'.setup()")

And then follow the suggestions in this: https://github.com/jcdickinson/wpm.nvim/discussions/6
I don't know vimscript at all, so that's all the help that I can offer.


Feature request: preserve permissions option

Basically, the -p flag from (POSIX) cp:

-p  Duplicate the following characteristics of each source file in the corresponding destination file:

The time of last data modification and time of last access. If this duplication fails for any reason, cp shall write a diagnostic message to standard error.
The user ID and group ID. If this duplication fails for any reason, it is unspecified whether cp writes a diagnostic message to standard error.
The file permission bits and the S_ISUID and S_ISGID bits. Other, implementation-defined, bits may be duplicated as well. If this duplication fails for any reason, cp shall write a diagnostic message to standard error.

note that most implementations of cp also specify -a (-a/--archive in GNU), which implies:

-p
-R: recursive (cpz already does this by default)
-P: symlinks in the sources are copied as symlinks, rather than followed (cpz also does this by default)

Also, for reference, GNU's cp -a additionally:

preserves other attributes like SELinux context and extended attributes (from GNU cp -p=all)
"preserves hard links between source files in the copies" (from GNU cp -d)

(if you cp -a two files that are hard-linked, you'll create a separate pair of hard-linked files)

Providing -a (ideally, but perhaps not necessarily, GNU's version) would be very useful for using cpz as a backup tool.

would be very useful for using cpz as a backup tool.

Just a fair warning, cpz uses the copy_file_range syscall which means the physical bytes aren't actually copied on file systems that support it. You'd need to do a cross-fs copy to get a true copy. Though if you're using a FS like bcachefs you can tune the number of physical copies you want on a per file basis.

file permission

cpz copies these by default. I'd consider it a bug if this is not the case (on Linux, for other platforms this doesn't happen).

user ID and group ID

This I'm not willing to do because it would introduce an extra syscall for every file. You should sudo into the uid/gid you want the files to be copied as.

The time of last data modification and time of last access.

Same reasoning here.
In theory a flag could be added for both, but I'm really resisting adding flags because:

I don't know how to deal with cross platform compatibility. One solution here could be to just drop macOS/Windows compat since these tools aren't optimized for those platforms anyway.
Once one flag is added, then everybody wants flags and suddenly I'm trying to be the fastest while also being a coreutils clone which is not the goal.

preserves hard links between source files in the copies

This one is wild! Unless I'm missing something obvious, I think you need to keep track of every hard linked file you've seen so far and then match newly encountered hard links with what you've copied so far. This definitely won't happen flag or not because it requires synchronization between the copy threads.

If your use case is backups, it might actually be faster to first do a cpz pass to pound the NVMe queues, sync, and then run a second metadata + checksum rsync pass. For serious backups, I wouldn't trust the physical media to have written stuff correctly, so you need to use rsync either way.

Ah, I see. I think cp --reflink uses FICLONE. effectively (as far as the filesystem is concerned) the same, right?

Yup!

Thanks for the suggestion though!


Edit GA so that it has craft mode, feedback mode and hybrid mode

GA currently returns array of notes based on desired measured values of metrics in the melody. An idea would be to create feedback mode (or crafting mode) that lets user generate rhythmic values and melodic values separately, but also create fitness function by own feedback (what melodies user prefers).
Also hybrid mode should allow user to mix between these modes. For example perform generation only on melodic qualities (on chosen rhythmic values from before)

idea: hold melody in the left octave, and rate with right octave (higher note - higher rating)

Added craft mode in form of choosing rhythm and apllying melody over it

Added craft mode in form of choosing rhythm and apllying melody over it


Update card-schema.md

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

AdaptiveCards/authoring-cards/card-schema.md
:white_check_mark:Succeeded

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.


navigation bar fixes

improved the navigation bar with dynamic support for different screen sizes bar moved nav-bar it to a new file
fixed duplicate declarations

@LocalTweekez ska jag bara merge:a ?


nixos/swap: add discardPolicy option

Add option for activating discards on swap partitions (none, once, pages and both).
Motivation for this change
Especially when hibernating, many gigs get written to disk. I would have liked to see the possibility of specifying a discard policy in NixOS.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/511

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/376

Tested by building the following derivation manually under different swap options:
nix-build -A config.system.build.etc
Don't know if this suffices

@ThibautMarty I think I applied all your suggestions, retested and everything works. Thank you very much

@ThibautMarty maybe this time I didn't forget anything

:tada:


👷 add docker publish workflow

closes #39
Co-Authored-By: naton<EMAIL_ADDRESS>

Thanks to @jxn-30 and @Ron31 for reviewing PR(s), let's add them. cc @all-contributors


what exactly do i put in my podFile for your latest swift version?

this in my podfile does not work
pod 'SkyFloatingLabelTextField', '~> 2.0.0'

seems it was a cocoapods issue.

Glad it worked out 👌🎉


How shoud we report security issues?

I found some behaviors that seem vulnerabilities in uWebSockets.
However, there is no guide for reporting security issues here.

Where can I report the vulnerabilities?

You can send me a mail

@uNetworkingAB
Thank you for your response.
Which one is better for you, sending one report including all vulnerabilities or sending one report for each vulnerability?

I have Gmail they will end up pretty much the same either way; a thread. So it makes no difference

You haven't sent me anything yet but I can already guess where this is going.
Preemptively I can already say that uWS doesn't, and will probably never, implement all weird edge-cases of http1.1.
This is not a vulnerability. It just means uWS will not have 100% spec compliant behavior in all weird edge-cases of http1.1.
The important here is that uWS works for 99% of real world apps and never leaks encrypted data, never crashes, never goes out of bounds or in any way breaks down or leaks data.
What I'm guessing you will make a big deal of is that two different http servers can make two different interpretations of edge case http 1.1, depending on how strictly they implement these messy http1.1 edge cases.
This is again not a vulnerability.  You're going out of your way to build something broken.
Either you let a proxy interpret the edge cases, sending non-edge case http down, or you put two http servers of the same brand in use if you really require such a fragile behavior. It's pretty obvious that if you send edge-case borderline broken http through one brand of server and expect another brand of server to make the identical exact interpretation in every case possible then you're wishing for failure.
The same idea can be applied to literally any protocol implemented by different vendors. You can have JSON parsers that differ in edge cases producing the same exact problem. You can have Microsoft Word documents produce different interpretations in two different implementations.
This is a natural outcome of having different implementations.

Here is a counter example:

Http1.1 does not define a strict limit on maximum header size. But there obviously needs to be one (call it implementation detail A).

Now, a proxy that limits headers to 16kb and just "ignores and passes the data through" (or whatever it wants to do) when that limit is reached - will very obviously make a different interpretation of the data than a server that picked a limit of 64kb. Now we have caused a "security vulnerability" since the first server ignored some important header and passed the message through and now you have deviated behavior.
Spooooooooky! We just broke the security!
There are tons of these undefined cases in http1.1 where you will have differing behavior so relying on a specific exact behavior is like shooting you in the foot an expecting to win a marathon the next day. It's self inflicted damage.

I still haven't received any of these supposed vulnerabilities. Please send so I can have a look

I don't think there are any issues, been looking at RFC 9112 a bit here and even if we do things sloppily at places none of this should be an issue. If you are referring to (guessing from your github activity) "request smuggling" these are not possible since it is invalid for a proxy to send us both content-length and transfer-encoding, and if the proxy sends us transfer-encoding then it is valid for us to assume the proxy did chunked encoding and either accept it or not. All cases are valid for us according to 9112.
While looking at this spec I've done some changes to uWS to be more spec. compliant (still some changes to do) but I really cannot think of any vulnerability here.
Please send what you have, I still have not received anything. I want to close this as quickly as possible.

Alright I'm closing this as you have not responded or sent me anything.
I've found one class of issue namely the 11.2 part of RFC 9112 which is only an issue if you are using a proxy and you rely on the proxy being able to filter certain URLs. These are fixed in two steps:

More strict use of transfer-encoding and content-length
Making reading of content-length more strict in terms of overflows, same for chunk lengths in chunked encoding.

These are not really "vulnerabilities" when looking at uWS itself, they are more vulnerabilities in a deployment of a proxy and uWS with filter rules not implemented in uWS but in the proxy.
My opinion is that, doing such a set up is begging for issues since it requires all parts being entirely spec. compliant here and the smallest deviation will break the filtering mechanism. I would say if you care about your data, then apply filtering where you have you data or partition your network so that sensitive data is not even reachable from the front-end proxy at all.
I would file these issues more under "spec. compliance" and I will implement all changes needed to make it so.
Kind of like talking to a brick wall here but I guess, thanks for the input. It made me look deeper at this.

@uNetworkingAB
Sorry for not getting back to you sooner.
I sent an email describing my findings..

Thanks. Yeah like I wrote these are all 11.2 compliance issues:

We found three HTTP Request Smuggling (HRS) Vulnerabilities in
uWebSockets.

These aren't vulnerabilities in uWS itself, they apply to set-ups that have proxies that expect to be able to block requests based on url.
These http1.1 spec compliance issues will gradually be fixed as we become more spec compliant with RFC9112.
A recommendation is to not put all your eggs in one basket protected by an inherently fragile blocking mechanism that has been broken in pretty much every http server ever created. Instead use proper network partitions to separate interval traffic from external.
Honestly it boggles my mind how anyone could even think of relying on such a broken feature when you have sensitive data exposed under a separate http route - this way of thinking is new to me, I would never ever rely on two parsers from two different vendors to always parse a text format with 4534 different versions, the identical way.
Honestly, I still wouldn't trust such a feature even if servers claim to be "protected" from it since it just takes ANY differing behavior to completely break that feature.
I would instead just make it so that proxies aren't allowed to block certain URLs since doing so is such a fundamentally broken feature.

I appreciate the detailed reports but the more I look at them the less important they seem:
All three issues are of the form "use uWS as the proxy that forwards to a backend server that does X instead of Y". uWS isn't even a proxy and has no such functionality.
One of the three reported issues is that we don't break when host header is missing, how on earth can that be a "vulnerability".
I'm thankful for the nice work made and I have easy fixes that will be made but this is really stretching the wordage "vulnerability" to its breaking point.
One issue is that we trim whitespace between header key and the colon, instead of rejecting the request. This simply is not a vulnerability. The header is reported to the app trimmed and there is no such functionality that allows forwarding the original untrimmed key, because again uWS is not a proxy and it has no such functionality.
The final issue is that we don't break when a header value contains LF or NULL. This is again an issue on the basis that if uWS was a proxy that forwarded the raw request then some shittily implemented downstream server could interpret that LF as CRLF....
Anyways, will apply these fixes but they are really nit picking spec compliance issues not vulnerabilities.


will support markdown in future?

Will camaleon support markdown in future, I think it's easer way for blogger to write.

yes, I am thinking to include liquid gem.

Great, looking forward to it.
As I know, liquid gem is a template language, Has it got any connecting with markdown?

mmm it is different, could you please send me a link or details about what kind of markup would you like to implement?
regards!

I hope we can write post just like write this comment in github. Type in markdown and can preview.

https://en.support.wordpress.com/markdown/

It appears a good idea, I will apply the next month!