update "breadcrumb_path" in docfx.json

fix broken breadcrumb in java pages

Docs Build status updates of commit 5bfbc2f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@anmeng10101 I am always grateful to see contributions from you!
For this one though, I'm a bit confused.
Example Page on main

Example Page on your PR

To me it seems like it was already working properly...even if that "properly" was ACCIDENTALLY haha.

@scbedd
If we F12 when loading the page, we will see this 404.

And this 404 is happening on every page.
This is what we are seeing for now:

But based on the docfx configuration, it should be display as this:

Docs Build status updates of commit 55a698a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

breadcrumb/toc.yml
:white_check_mark:Succeeded

docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Fix error-prone warnings for google-cloud-platform IO

Really simple PR to fix error-prone warnings in google-cloud-platform IO
( CC @iemejia )

R: @jkff by randomly assigning reviewers for the fixes on error-prone

retest this please

LGTM thanks!

Thanks @jkff


Introduce GAME_SCOPE to avoid dependency on Google Credentials

One more thing to check in future is how global games are held; didn't we break something there in the process. Posting this as a reminder :)


chore(main): release 1.1.4

:robot: I have created a release beep boop
1.1.4 (2024-09-26)
Bug Fixes

kobo: do not try to cast null values (74b49e1)
kobo: support string calculate fields (49a6e63)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/BLSQ/openhexa-toolbox/releases/tag/v1.1.4 :sunflower:


[Feature] Move Mainnet KZG group and Lazy<KzgSettings>

Component
consensus, eips, genesis
Describe the feature you would like
4844 constants in alloy-eips needs the following

KZG constants and files from revm-primitives
Lazy<Arc<KzgSettings>> and other loading methods from reth

Additional context
Should be feature-gated behind c_kzg

#[cfg(feature = "kzg")]
use c_kzg::{Blob, Bytes48, KzgCommitment, KzgProof, KzgSettings};

this is already behind thekzg features flag, do you intend the feature should be changed to c_kzg?

no, use whatever existing feature name 🤝

I don't think,

g1_points
g2_points
trusted_setup

would be necessary in the alloy-eips module, what do you think?
Secondly, I am looking to add;

Re-export EnvKzgSettings from the revm-primitive env_settings.rs
Re-export all public const from revm-primitive trusted_setup_points.rs

what are your thoughts?

@prestwich

all of the utils and constants defined on revm should be moved here, then once we have a release we can replace them in revm with our crate

Alright... that makes sense


Is there a  Swift project?

Is there a  Swift project?

@DeeptiChawla35 nope, you can port it if you wish. I'd be happy to supervise.

@DeeptiChawla35 Have you manage to convert it?
Else, do you still interested in supervising: :) @zavolokas


IronPython does not support calling Rx.NET extension methods

From @glopesdev on January 14, 2017 16:29
Can someone please explain me this really weird observation?
I've been trying to call Rx extension methods from inside IronPython and it is turning out to be simply impossible. I've boiled it down to this simple example:
import clr
clr.AddReference("System.Core")
from System.Linq import Enumerable

def process(value):
  return Enumerable.Select(value, lambda x:x)

In this case we start with normal LINQ. If I call the process function from my hosting environment with an array or any other IEnumerable object, it works totally fine.
So then I tried to simply replace the references to use the Observable extension methods like so:
import clr
clr.AddReference("System.Reactive.Linq")
from System.Reactive.Linq import Observable

def process(value):
  return Observable.Select(value, lambda x:x)

In this case, if I call the process function with an IObservable object, the call crashes with an ugly error message:
expected IObservable[object], got Select[int, int]
Has anyone hit upon something like this? Have I missed something? Is there some special case hack to make Enumerable work with lambda delegates that Observable is missing? I have to admit I'm completely baffled here.
By the way, just as a sanity check, the following example works just fine:
import clr
clr.AddReference("System.Reactive.Linq")
from System.Reactive.Linq import Observable

def process(value):
  return Observable.Sum(value)

I wanted to leave it out there just to make it clear that the problem really is in the method call to Observable.Select.
Copied from original issue: IronLanguages/main#1564

From @glopesdev on January 14, 2017 17:13
More examples that seem to point out that this is some issue with method call resolution in IronPython:
import clr
clr.AddReference("System.Reactive.Linq")
from System.Reactive.Linq import Observable

def process(value):
  return Observable.Count(value, lambda x:True)

This does not work (same as above). But this does:
import clr
clr.AddReference("System.Reactive.Linq")
from System.Reactive.Linq import Observable

def process(value):
  return Observable.Count[int](value, lambda x:True)

Only difference was that the type of the generic method call was specified explicitly. Of course, then the script does not work for any input type.
Interestingly, even this fix fails to correct the behavior with Select. For example:
import clr
clr.AddReference("System.Reactive.Linq")
from System.Reactive.Linq import Observable

def process(value):
  return Observable.Select[int,int](value, lambda x:x)

This case still crashes, but now the error message changes to:
Multiple targets could match: Select(IObservable[int], Func[int, int]), Select(IObservable[int], Func[int, int, int])
These examples I think raise a red flag that there is something wrong with method call resolution and type inference when lambdas are involved. I've also been able to reproduce the same behavior with generic method stubs that I've implemented myself. They crash exactly in the same way as Rx methods so in fact this issue is more general than just with Rx.
Indeed, the question that can now be asked is actually why do the methods from the Enumerable class work at all?

From @glopesdev on January 14, 2017 17:34
By the way, here is a simple hosting test setup to reproduce the issue:
using IronPython.Hosting;
using System;
using System.Collections.Generic;
using System.Linq;
using System.Reactive.Linq;
using System.Text;
using System.Threading.Tasks;

namespace TestPython
{
    class Program
    {
        static void Main(string[] args)
        {
            var engine = Python.CreateEngine();
            var scope = engine.CreateScope();
            var source = engine.CreateScriptSourceFromString(@"
import clr
clr.AddReference(""System.Reactive.Linq"")
from System.Reactive.Linq import Observable

def process(value):
  return Observable.Count(value)");
            source.Execute(scope);

            var process = scope.GetVariable("process");
            var input = Observable.Return(1);
            var output = process(input);
            var result = Observable.Wait(output);
            Console.WriteLine(result);
        }
    }
}

You can replace the script code with different method call variants and see what happens.


Information for Service Providers?

Hi - is there any guidance information for service providers to ensure we can optimise for users on the Google One VPN (e.g. identify and not block requests/connections from the VPN!) similar to that provided by Apple for Private Relay:
https://developer.apple.com/support/prepare-your-network-for-icloud-private-relay

Thank you - is there any suggested frequency with which we should check those IP ranges for updates?
Can we rely on the 304 Not Modified status code if just making HEAD requests or should we make a full GET and keep track of the checksum for any changes?

Hey Josh, although I believe 304 should work on gstatic.com please use the checksum. It is directly tested by our generation infra. We aim to update the file infrequently and long before we start using IPs published within. I'd recommend daily polling to ensure you have a reasonably fresh copy. We can't make any specific promises on rollout timelines at this time.
Hope this helps. Best,
Scott


fix data race problems

close #322

@yangdiangzb Could you please rebase your branch on dev to get rid of the spurious merge commit?

@yangdiangzb Could you please rebase your branch on dev to get rid of the spurious merge commit?

@bryanpkc Fixed.

Hi, sorry for such such late comments, but I am not sure about this PR after diving into the latest code base recently. I think most of the race problems mentioned in this PR lie within the testing methods rather than the functions themselves.
Taking this line for example: https://github.com/AsynkronIT/protoactor-go/blob/69575e77b84f80cd785c01fb397634997f12129d/router/random_router.go#L25-L29
Essentially randomRouterState is the state of RandomRouterActor, which is be guaranteed to be synchronized.
https://github.com/AsynkronIT/protoactor-go/blob/28110571d6a3931291bfc06476f23ec672337dd5/router/routeractor_pool.go#L23-L30
Adding the atomic pointer store to change the state of RouterActor is a bit redundant and it defies the purpose of using actor model, or am I missing something here? @rogeralsing @yangdiangzb @stuartcarnie


Handling NodeLost problems

When node dies kubernetes is not replacing pod from it (it is kinda expected https://github.com/kubernetes/kubernetes/issues/51333 ), so I guess operator can help with that

Codecov Report

Merging #21 into master will decrease coverage by 0.04%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master      #21      +/-   ##
==========================================
- Coverage   37.01%   36.97%   -0.05%
==========================================
  Files          37       37
  Lines        3409     3413       +4
==========================================
  Hits         1262     1262
- Misses       2030     2034       +4
  Partials      117      117

Impacted Files
Coverage Δ

pkg/controller/controller.go
0% <0%> (ø)
: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 1669bf2...3c6fe5a. Read the comment docs.


symfony/psr-http-message-bridge 2.1

Hello!
Thanks for the package! Currently can't install though as the composer.json says it needs symfony/psr-http-message-bridge ^2.1 and composer blocks the install as i have v7.1.1 installed.
Any reason we can't bump the version on that package?
Thanks! :D

I think it should work with the newer versions too, at least the changelog contains nothing which should break the usage in this bundle.
With the release of Symfony 6.4 the version schema of this package was changed and now follows these of symfony. (Before you could use the 2.* versions for all symfony versions).

Fixed with version 2.2.2

Perfect! Installs fine now, thank you!


DateRangePicker onChange callback

Is there a way to fire a callback with startDate and endDate values only when there is a startDate, an endDate and the date picker isn't focused anymore. Something that tells that startDate and endDate are the final values and not something inprogress?

Can you clarify? Because the component is fully controlled, you always have access to date values and focus value in the state of your wrapper component. The onDatesChange and onFocusChange callbacks should give you access to the new values as they change.
What exactly are you trying to do?

I have a similar problem. The use case being that once a user selects start and/or end dates, and the DateRangePicker is closed (i.e. focusedInput === null), then I want to trigger an API call to refresh data in the table. The problem I run into is that setState is not synchronous, so when I check if the focusedInput is null or I try to grab the values for the starteDate and endDate... they are usually old values. Here is how it looks
  onDatesChange({ startDate, endDate }) {
    let {focusedInput} = this.state;
    if (!focusedInput) {
      dispatchAPICall();
    }
    this.setState({ startDate, endDate });
  }

  onFocusChange(focusedInput) {
    this.setState({ focusedInput });
  }

I am trying to fire an ajax call only when the set of [startDate, endDate] is changed and not one or the other. I don't know how to achieve this.
Is the same that davekaro commented.

@soda29 they're never both changed at the same time - each is changed separately by the user, so you yourself have to decide when both changes have come in and you want to make your Ajax call.

We need this too.  There currently isn't a reliable way to know when the picker is being unfocused.
For instance, log out here:
onFocusChange={focused => {
  console.log(focused)
  this.setState({focused})
}}

When you click the start date, you will see this:
'startDate'
null
'startDate'
'startDate'

When you switch to the end date, you will see this:
'endDate'
null
'endDate'
'endDate'

And when you close the datepicker, you will see:
null

That last null is great, and exactly what @davekaro and I are looking for, but the other null that are randomly fired off during the other actions makes this unreliable.

@tannerlinsley There's actually some changes in https://github.com/airbnb/react-dates/pull/217 that will fix the quadruple firing (and make onFocusChange a little bit more reliable) at the least.

@majapw That's good to hear.  Those changes would effectively close this issue :)

@davekaro and everyone else, a temporary workaround that I'm using works okay for now:
onFocusChange={focused => {
  this.setState({focused})
  if (this.state.focused === 'endDate' && !focused) {
    // Dispatch an update
  }
}}

This should only fire when the picker is updating from 'endDate' being focused to not being focused at all.
I have no idea why it doesn't fire during the quadruple events from clicking 'endDate'.  Likely because setState is synchronous, it hasn't updated yet.

@tannerlinsley But it seems like onFocusChange fires before onDatesChange. So when !focused the last onDatesChange has not been called yet.

This is still a problem for us. Hoping that the latest version has fixed
the bug
On Fri, Feb 24, 2017 at 1:18 PM Huarui Wu<EMAIL_ADDRESS>wrote:

@tannerlinsley https://github.com/tannerlinsley But it seems like
onFocusChange fires before onDatesChange. So when !focused the last
onDatesChange has not been called yet.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/airbnb/react-dates/issues/117#issuecomment-282394000,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCQoSAkiaiwoV7GRijyVxuFYtBRWAks5rfzsXgaJpZM4KVQ1w
.

I have the same problem ... would love to get a fix for this.

I've faced a slightly similar problem and this was a workaround. The logic sits in the componentDidUpdate lifecycle hook.
onFocusChange(focusedInput) {
  this.setState({ focusedInput });
}

componentDidUpdate(prevProps) {
  const { focussedInput, startDate, endDate } = this.state;
  if (!focussedInput && (startDate && endDate)) {
     // fire callback
  }
}


Run SQL tests in memory

It would be optimal if the tests for the SQL adapter could be run with the database in memory. This would have better performance and make cleanup easier. Sqlite does support this.
From the documentation (http://docs.sqlalchemy.org/en/latest/core/engines.html):
To use a SQLite :memory: database, specify an empty URL:
engine = create_engine('sqlite://')

Yep, I will change the default behavior of database creation, where if unspecified database file, will always create a sqlite memory a database.

Closes by #745


Responses not validated after redirect

Following a redirect Response.Success is returned even if the requested resource does not exist.  Consider the following tests:
    @Test
    fun failsIfRequestedResourceReturns404() {
        val manager = FuelManager()
        val (_, _, result) = manager.request(Method.GET, "http://www.something.cz/dolly").response()

        assertThat(result, `is`(instanceOf(Result.Failure::class.java)))
    }

    @Test
    fun failsIfRedirectedToResourceReturning404() {
        val manager = FuelManager()
        val (_, _, result) = manager.request(Method.GET,
                "http://httpbin.org/redirect-to",
                listOf("url" to "http://www.something.cz/dolly"))
                .header(mapOf("User-Agent" to "Fuel"))
                .response()

        assertThat(result, `is`(instanceOf(Result.Failure::class.java)))
    }

While the first one passes as Result.Failure is returned as expected the other one fails with
java.lang.AssertionError:
Expected: is an instance of com.github.kittinunf.result.Result$Failure
     but: <[Success: [B@7e0ea639]> is a com.github.kittinunf.result.Result$Success

I believe the issue is the root cause of the issue is line 28 in RedirectionInterceptor.kt which simply returns manager.request(encoding).response().second instead of submitting the result to subsequent interceptors (i.e. validatorResponseInterceptor).
Suggested solution
Change line 28 in RedirectionInterceptor.kt to
next(request, manager.request(encoding).response().second)

Hmm, can you suggest with a PR, and we can continue discussion in there?


fastpath syntax error at or near "Everbody"

When running the fastpath against the 2019-09-20 bucket with (PR#213):
I got the following error at some point:
607244 90663 DEBUG fastpath Loading nested 2019-09-20/20190920T032401Z-US-AS701-web_connectivity-20190920T032402Z_AS701_scLKevrfoDZVa8rlS4Hkf3rlshGXYNt08DZmTSkR8VRLzz4hLw-0.2.0-probe.json
607264 90663 INFO fastpath load_s3_reports remaining time: 0:02:35.805058
607264 90663 DEBUG fastpath Ingesting web_connectivity.16.tar.lz4
607294 90663 DEBUG fastpath Loading nested 2019-09-20/20190920T032422Z-US-AS7018-web_connectivity-20190920T032425Z_AS7018_5Lb65i9oJ0euLgLavUfnYmT6yT06q3TFRQNyUcEzi78FY7C7fu-0.2.0-probe.json
607550 90663 DEBUG fastpath Loading nested 2019-09-20/20190920T032528Z-BR-AS268400-web_connectivity-20190920T032532Z_AS268400_qOouyQ9CspxTSno7kZj6rW6gIRqBB6ezadsSra4ELiqyWCjKZy-0.2.0-probe.json
607886 90663 DEBUG fastpath Loading nested 2019-09-20/20190920T033152Z-ID-AS17974-web_connectivity-20190920T033153Z_AS17974_O107AIiG8Fz0o8Xw7s6GDmrgTvLswaEDaUP088TsInaF1zrBiE-0.2.0-probe.json
608523 90677 ERROR fastpath syntax error at or near "Everbody"
LINE 1: ...st.com\/category\/local_news_articles\/20100518\/'Everbody-D...
                                                             ^
Traceback (most recent call last):
  File "/Users/x/code/ooni/pipeline/af/fastpath/fastpath/core.py", line 485, in msm_processor
    db.upsert_summary(measurement, summary, tid, fn, conf.update)
  File "/Users/x/.virtualenvs/fastpath/lib/python3.6/site-packages/statsd/client/timer.py", line 38, in _wrapped
    return f(*args, **kwargs)
  File "/Users/x/code/ooni/pipeline/af/fastpath/fastpath/db.py", line 121, in upsert_summary
    cur.execute(q)
psycopg2.errors.SyntaxError: syntax error at or near "Everbody"
LINE 1: ...st.com\/category\/local_news_articles\/20100518\/'Everbody-D...
                                                             ^

It did not stall the pipeline, which is great, but is likely something to look into

This is no longer relevant. Closing.


[e2e tests] VM details: Storage tab

Create e2e tests for VM details (Storage tab) functionality

To check here:

ISO attachment/detachment
Volume attachment/detachment
"View all" for snapshots + actions (only presence of actions with links)
Last snapshot
All actions/icons for the last snapshot (here you check that actions work)


chore(Analysis/NormedSpace/OperatorNorm): remove local instance in favor of letI

The former creates defs that are just noise, and have horrible names that the doc linter will complain about if the autogenerated name changes.

Thanks! Once CI is happy, please merge this PR using bors r+
bors d+

bors merge


Low R^2 Scores in KAN Model Regression

I am currently employing the KAN model for a basic engineering regression problem and have observed unexpectedly low R^2 scores, even for the simplest configurations. Given this, I suspect there might be an issue with the implementation in my script.
Would you be able to review my code to identify any potential errors or suggest improvements? I have attached the script for your reference. Any insights or recommendations you could provide would be greatly appreciated as I aim to optimize the model's performance.
@import pandas as pd
import torch
from kan import KAN
from sklearn.model_selection import train_test_split
from sklearn.metrics import mean_squared_error, mean_absolute_error, r2_score, explained_variance_score, max_error
import tkinter as tk
from tkinter import filedialog
def load_data():
root = tk.Tk()
root.withdraw()  # GUI ekranını gizle
filepath = filedialog.askopenfilename(title="Excel dosyası seçin", filetypes=(("Excel files", ".xlsx .xls"), ("All files", ".")))
root.destroy()
if not filepath:
print("Dosya seçilmedi.")
return None, None
data = pd.read_excel(filepath)
X = data.iloc[:, :-1].values
y = data.iloc[:, -1].values
return X, y
def train_and_evaluate(X, y):
X_train, X_test, y_train, y_test = train_test_split(X, y, test_size=0.20, random_state=42)
X_train = torch.tensor(X_train, dtype=torch.float32)
X_test = torch.tensor(X_test, dtype=torch.float32)
y_train = torch.tensor(y_train, dtype=torch.float32).view(-1, 1)
y_test = torch.tensor(y_test, dtype=torch.float32).view(-1, 1)
grids = [5, 10, 20, 50, 100]
for grid in grids:
    model = KAN(width=[X_train.shape[1], 50, 100, 1], grid=grid, k=3, noise_scale=0.1, seed=0)
    model.train({'train_input': X_train, 'train_label': y_train}, opt='LBFGS', steps=50, lamb=0.01)

    y_train_pred = model.predict(X_train)
    y_test_pred = model.predict(X_test)

    print(f"Results for Grid Size: {grid}")
    print_metrics(y_train, y_train_pred, "Training")
    print_metrics(y_test, y_test_pred, "Testing")

def print_metrics(true_values, predicted_values, dataset_type):
mse = mean_squared_error(true_values, predicted_values)
mae = mean_absolute_error(true_values, predicted_values)
r2 = r2_score(true_values, predicted_values)
evs = explained_variance_score(true_values, predicted_values)
max_err = max_error(true_values, predicted_values)
print(f"{dataset_type} - Mean Squared Error: {mse}")
print(f"{dataset_type} - Mean Absolute Error: {mae}")
print(f"{dataset_type} - R^2 Score: {r2}")
print(f"{dataset_type} - Explained Variance Score: {evs}")
print(f"{dataset_type} - Max Error: {max_err}")

def main():
X, y = load_data()
if X is not None and y is not None:
train_and_evaluate(X, y)
if name == "main":
main()

Hi, might be good to run a baseline model (say linear regression) to see how that performs. And then we can have a sense of how hard this problem is, and have a sense of whether it's your implementation error or it's KAN's problem.


Smartphone home page doesn't load properly.

When I go to your website, the main page doesn't show your full name and the green box.

yeah, this is still incomplete . If you would like to make to contribute in this , you can .
You can resolve this issue by making this section responsive


hard-coded registry name/org changed with the step environments

Signed-off-by: Batuhan Apaydın<EMAIL_ADDRESS>
Description
This Pr tries to make the CI jobs similar to the others in Org.
Motivation and Context
Related to openfaas/faas#1643

[ ] I have raised an issue to propose this change (required)
[ ] My issue has received approval from the maintainers or lead with the design/approved label

How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I've read the CONTRIBUTION guide
[x] I have signed-off my commits with git commit -s
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Closing, as fixed in #25


soFromEndOfLine and soToEndOfLine do not work together

When both options are set, alongside soPastEndOfLine, the editor should behave as Delphi's but does not.
When only soFromEndOfLine or soToEndOfLine is used, they work, but together the selection start is "weird": it will visually highlight from the end of the line to where the caret was at the time the selection was started.

When both options are set, it works like the Sublime editor does. So, there must be an option soToEndOfLastLine.

I mean the weird selection highlight, for instance in:

there is a selection highlight that goes from the ';' to where the selection was started, instead of filling the whole width like it usually does.
Come to think of it the issue might actually be that soToEndOfLine affects two different things:

that the selection stops at the end of the line where the mouse cursor is dragged
that the selection highlight stops at the end of the lines rather than filling the width

In Sublime that would look like:

Like said, soToEndOfLine needs a little fix and there must be another option (for example soToEndOfLastLine) that means that the selection is done with the whole width until the end of it. Those options are mutually exclusive.

Fixed.


privy.providerBaseUrl doesn't seem to be used right now - cannot repoint it from local ollama to remote ollama

Describe the bug
I do have ollama running on a remote machine in my network.
With the privvy "Provider Base Url" setting (privy.providerBaseUrl) set to value "http://remotehost:11434/", Privy doesn't work.
I restarted the VSCode, just to make sure.
However, if I ssh-tunnel the remote server port to my localhost (e.g. ssh -L 11434:localhost:11434 <IP_ADDRESS>) Privy starts to work normally. It does seem, that this setting right now doesn't have any effect and Privy always attempts to connect to localhost:11434 when Ollama is set as provider.
How to reproduce
Don't have ollama running locally on port 11434 but have it running elsewhere instead.
Make sure you're able to make curl calls to that remote ollama server and it responds back:
curl http://remotehost:11434/api/generate -d '{
  "model": "deepseek-coder:1.3b-base",
  "prompt": "Why is the sky blue?"
}'

Set "Provider Base Url" setting (privy.providerBaseUrl) to value like "http://remotehost:11434/".
Try to use Privy that way.
Expected behavior
Privy should consider this configuration setting in
Additional information

Version of the extension impacted: v0.2.6, v0.2.5
I'm not the JS programmer myself, but I tried to add consol.log("blah blah") calls inside of getProviderBaseUrl() just to see if it's ever being called and I don't see that string in privy debug console. Probably unrelated and that function is just called too early, when the debug is not being collected & displayed by VSCode

Thanks a lot, @kha84 for putting up a detailed report. This is fixed and released in v0.2.7. Please give it a try.

Amazing, it works just fine now with remote ollama endpoint!
Love and respect


Integration tests should be part of the cargo workspace

Currently the workspace virtual manifest is located in ./crates and workspace members are the crates below the ./crates folder.
None of the integration test crates below ./tests/rust-integration-tests are workspace members. This means that tools like rust-analyzer will basically ignore them. IMO, the whole codebase including the tests should be part of the workspace.
I'm also always a bit irritated if a Rust codebase doesn't have a Cargo.toml (with or without a workspace) at it's root.
Hence, I do suggest to move the virtual manifest from ./crates to the project root and also add the directories below ./tests/rust-integration-tests to the workspace. This will also result in a single target folder for both regular code and integration tests.
WDYT?

Hey,
So the separation of integration tests from the youki crates was a deliberate decision, as the integration test binaries, specifically the runtimetest binary needs to be statically linked, unlike rest of binaries which are dynamically linked. This crates an issue, as then for each compilation, crates which both youki and tests depend on such as oci-spec are compiled twice , once for each linking-type even if it is not strictly necessary. Thus we have separated the integration tests altogether from the youki crates. This separation also provides a nice separation-of-cause (at least in my opinion) as the integration tests are not strictly youki-specific ; they are rust port of OCI tests, and thus should not be directly connected to youki crates.
As for this part, you might want to take a look at #820 , where it was discussed recently.

I'm also always a bit irritated if a Rust codebase doesn't have a Cargo.toml (with or without a workspace) at it's root.

Thanks for the feedback!

Thus we have separated the integration tests altogether from the youki crates. This separation also provides a nice separation-of-cause (at least in my opinion) as the integration tests are not strictly youki-specific ; they are rust port of OCI tests, and thus should not be directly connected to youki crates.

Understood. You might want to consider moving the integration tests into a separate project / repo in order to make the separation explicit and obvious.
Anyways, fell free to close the issue.


Contributing guidelines

Intro
The project has already a lot of contributors and more implementations on the way, but no "Contributing Guidelines". How about creating a related doc that contains all the rules and conventions?
I think we could treat this issue as a place to share ideas about the "Contributing Guidelines" doc.
Initial Ideas
1. I've noticed each published package of the Sessionless implementation has a different description. I don't think it's anything critical, but making one decisive description that can be re-used across packages can help to better "pass the message".

python: Sessionless is an attempt to make authentication handling easier for developers without traditional sessions.
js: Node implementation of the sessionless protocol
swift:
rust: Implementation of the Sessionless protocol.

2. Each implementation has a different structure. This might come from a language specifications and needs, but a README document in each directory (for example: src/js/README.md, src/rust/README.md, src/cpp/README.md) could make it easier to understand and navigate through.
3. This document could also include all the naming conventions decided in #20

Totally agree on these three points. I also think, once we’re ready with testing, we should align on versions for all the implementations. I started down the path of cleaning up the docs a bit, and will do some more with the rainbow test I started working on. If I’m still working on that branch I’ll add what’s decided here. If not we can do so in a follow up PR.

Wanted to just update here that this hasn't been forgotten. @Daniel-J-Mason is updating Java soon, and I'll update Kotlin, and get the cli tests working with both. That'll let us do the rainbow test. The rainbow test will serve to seal all the naming for the combined release, which I, or someone else, can put into the language README's.
And I had a thought on the consistent description. When I think of what Sessionless is trying to accomplish, the metaphor I keep coming to is it's what a drill is to a home, Sessionless is to connected devices. Sure there are plenty of other tools (i.e. the rest of cryptography), but most people just need a drill, and because of that, companies can make things that just need a drill, and there's a whole ecosystem that exists because people have drills.
So maybe we say something like, "Sessionless, the drill of cyberspace." I'll ask RainbowBrite what they think.


Api seems to be down

Hi @ealmansi,
i think there is an issue with your app actually.
Results are always Oops. Something went wrong. in your website.

@jbaubree thanks a lot for reporting this :1st_place_medal:
the API and website should be working normally again now.
please, let me know if you have any further issues :pray:


[AIRFLOW-2122] Handle boolean values in sshHook

This allows passing boolean values in the
extra field of ssh connection
Make sure you have checked all steps below.
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-2122

Description

[x] Here are some details about my PR, including screenshots of any UI changes:

With this change, the user will be able to pass boolean values in the extra field of the
SSH connection.
Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

[x] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

Change looks good, but some tests would be good please


[BUG] Not creating models

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Trying to create models from clipboard
Ctrl+shift+p (open command pallete)
search for JSON to Dart from clipboard
enter the required data (classes name, etc)
And nothing happens
Expected Behavior
Trying to create models from clipboard
Ctrl+shift+p (open command pallete)
search for JSON to Dart from clipboard
enter the required data (classes name, etc)
The models are created in the folder. (like it used to be before)
Steps To Reproduce
Ctrl+shift+p (open command pallete)
search for JSON to Dart from clipboard
enter the required data (classes name, etc)
Version
3.5.1

Relevant JSON syntax
{
"user":"usuario",
"number":"123",
"others":{"color":"yes","enabled":true}
}

Anything else?
No response

@01FC Hi 👋
Thank you for your report. This is a known problem for windows and I hope I have fixed this in the latest version, but am waiting for @hiranthaR when he will update it. For now you can convert from the file until new release.

downgraded to 3.41 until the issue is fixed. Thanks

@01FC Hi 👋
Can you test latest 3.5.3 version to see if no issues?


Infinite captcha loop

From what i can tell, there are some downloads that cannot be downloaded with current system.
Great example: https://tinyurl.com/2fc9suhu
Captcha is solved correctly with auto solver and i even tried a manual one.
But download page always returns title: Pro Pomalé stažení opište kód z obrázku.

Above-mentioned file downloaded with these results:
 and plays well.

version: 3.1.0
python: 3.9.15
os: linux x64
I was able to download that file later, however no other files from list of the same title and same uploader.
I guess this might be something related to the tor network usage and requesting captchas too quickly.
another:
https://tinyurl.com/yx6mvzfs
https://tinyurl.com/43dve2kc
https://tinyurl.com/42fmbmcc

If i change the url (domain) from https://www.uloz.to/file/ to https://ulozto.cz/file/... The downloading work as expected.

classic URL: https://uloz.to/file/ seems to be working fine.

@SpiReCZ great testing!
I tend to think this issue lies out of ulozto-downloader source code.

@zbyna thx, i am just glad i was able to make it working after all. It is not the best thing to do, but if this happens again there is a possibility to rewrite the URL to working one. I will leave the issue open, since the issue is still there.

Closing this old issue, it seems that nowaday wors all URL variants (uloz.to, www.uloz.to, ulozto.cz, ...).
Fixed on the UlozTo side :)


DataProtection Sample NonDISample still uses DI

DataProtectionApi NonDISample references the DataProtectionProvider.Create extension method which still uses dependency injection internally  https://raw.githubusercontent.com/aspnet/DataProtection/master/src/Microsoft.AspNetCore.DataProtection.Extensions/DataProtectionProvider.cs

Why does that matter?

It seems misleading to call it a NonDISample if it actually uses DI.

If it's internal it shouldn't matter. Those are details that shouldn't matter to the consumption. That's why it's called NoDI. VS the public API that relies on a DI container.

It still has a dependency on Microsoft.Extensions.DependencyInjection. Maybe I misunderstood the intent of the sample...I thought it was attempting to show how you could create DataProtectionProviders without using DI. If the intent was to give awareness/show how to use an extension method I'm OK with that.

The example was about using it without requiring your to explicitly use a DI container. The fact that it has a dependency and uses one internally hopefully shouldn't affect your usage.

How would you feel about a PR to https://raw.githubusercontent.com/aspnet/DataProtection/master/src/Microsoft.AspNetCore.DataProtection.Extensions/DataProtectionProvider.cs that doesn't require a reference to Microsoft.Extensions.DependencyInjection at all?

If I'm being honest we probably wouldn't merge it but I would love to see how it work since it needs to work in both cases.

@josephcooney When you make your branch, I'd love to see it (out of curiosity)


Update backup-azure-restore-system-state.md

Correcting the absence of a Hyperlink

@saurabhsensharma,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Rename anti-caching option

Renamed the property for configuration response caching headers
Renamed the options class to avoid conflicts with other type names

Fixes https://github.com/aspnet/Diagnostics/issues/509

/cc @guardrex


Unable to add a new event.

Describe the bug
The calendarJs object cannot be instantiated.
I downloaded the latest version and created a simple html in a local folder adding only the reference of calendar.js and I got
the error "Uncaught TypeError: Cannot read properties of undefined (reading 'addEvent')" when trying to add a new Event to the calendar.
To Reproduce
Steps to reproduce the behavior:

Create a new folder and download on it the dist folder.
Create an html document with the following code:

`

`

Scroll down to '....'
See error in the browser console.

Expected behavior
calendarInstance not to be undefined and be able to add a new event.
Screenshots

Desktop (please complete the following information):

OS: [Windows]
Browser [Brave, Microsoft Edge]

Additional context
Add any other context about the problem here.

  HEAD tags are not supposed to be in the body.
I've just written this for you to get something working:
<!DOCTYPE html>

        <title>Calendar.js</title>
        <link rel="stylesheet" href="../../dist/calendar.js.css" />

Let me know how you get on.  As of now, this is something I cannot recreate.


Add encryption support to sysdump.

Adds a --encrypt flag (defaulting to true) that encrypts the resulting zip file with either the bundled public key or the public key specified via --encryption-key.

It looks like this PR has gone stale and it would now need a rebase. If you are interested in reviving this, it may be worth syncing with @tklauser / @michi-covalent to agree on the approach, then you would be welcome to reopen a PR to submit this feature again.


Not reporting errors when adding attaching additional props

I would expect this to fail:
const StyledLightBulbIcon = styled(Icon).attrs({ iconName: 'light_bulb' })`
  svg-bad-selector {
    height: 50px;
  }
`

However it doesn't.  I passes without an issue.  When I remove the call to the .attrs function, it fails with an error.
const StyledLightBulbIcon = styled(Icon)`
  svg-bad-selector {
    height: 50px;
  }
`

src/components/task/list.jsx
 10:3  ✖  Unexpected unknown type selector "svg-bad-selector"   selector-type-no-unknown

Is there an option that can be passed into the CLI to ensure that it validates the styles when the .attrs function is being used?

Hey @mstarkman thanks for the bug report! This should definitely be default behaviour, shouldn't have any need for CLI options or anything. Thanks for making us aware of it and we'll try having it fixed in the somewhat near future.


revert(#77): incorrect check for existing socket clients

Currently version doesn't work with https://github.com/webpack-contrib/webpack-serve/blob/master/docs/addons/watch-content.config.js, here description why https://github.com/webpack-contrib/webpack-hot-client/issues/93 . Also if you have other additional websocket clients it is also break hot reloading.
We should reopen https://github.com/webpack-contrib/webpack-hot-client/issues/61 for searching better fix
Type

[x] Revert

Issues

Fixes #95

Semver

[x] Patch

@shellscape And? right now hot broken when you try to use https://github.com/webpack-contrib/webpack-serve/blob/master/docs/addons/watch-content.config.js example (just try run and looks how hot broken), also additional websocket break hot, the previous PR implemented the incorrect fix

And what? You're asking to revert a PR that fixed a bug, in order to fix a bug with your config. That will break the previous fix. You're asking to introduce a regression to fix a regression. That is not even remotely OK.

@shellscape my config? Try to use your example from https://github.com/webpack-contrib/webpack-serve/blob/master/docs/addons/watch-content.config.js. You merge incorrect fix and don't wan't fix it?

You're asking to introduce a regression to fix a regression. That is not even remotely OK.

This PR must also contain a fix for #61 to be merged. You may not introduce a regression to fix a regression.

@shellscape This is not possible to fix because developer have two wesockerts in one window (i.e. two hot client). It can be solve only using multi compile mode.

/cc @shellscape I understand correctly that you are ignoring fixing incorrect fix (no tests, no docs, no workarounds) and confirm that the current version does not work with officially documented feature as watch-content?

@shellscape Not wanting to get into the middle of some long going issues you and @evilebottnawi has, but I can +1 on this issue.
HMR does not work for anything but the first listed module in cases like this: https://github.com/webpack-contrib/webpack-serve/issues/119#issuecomment-412071796
To me this seems just as serious as #61 since there's not even a fallback with refresh in this case, it just silently decides there's not any change.

@hedefalk Due to some misunderstanding between developers now solving the question about webpack-serve, it is possible that this project will no longer be supported, shellscape not professionally behaved as a developer in some aspects. We apologize for the current situation, in the near future it will be resolved.

I am running into the same issue as this. Since webpack-dev-server just doesn't work correctly with HTTPS, this project seemed like good and more modern alternative.
Hopefully the misunderstandings @evilebottnawi mentioned, can be resolved. It would be a shame that such a project would be abandoned.

@blackshadev better use webpack-dev-server and create issue about https or mention me if issue already exists. The project will merge with webpack-dev-server in near future.

I mentioned you in both issues on the webpack-dev-server. see issue 1449 and issue 851

@blackshadev thanks!

I hate it when you guys fight.

@j-walker23 this package abadoned, don't use it

@j-walker23 I have moved on from this org a long while ago. it's unfortunate that the webpack-contrib org is unable or unwilling to work on it. if you have any issues feel free to reach out to me personally and I'll be happy to help you work on a fork, or fork and help with any issues much like I did for several other webpack-contrib packages.
(I don't get notifications from this org any longer, so I likely won't see replies. Someone was kind enough to let me know about yours.)

@shellscape Thanks man, very nice offer, I really appreciate that! I just moved from jspm to webpack yesterday, and it's been quite the rollercoaster. Webpack seems awesome. But man, when something doesn't work and no help can be found from google, it's a high learning curve.
Thanks for the heads up too. I am going to fork now, the code in these alternative webpack and HMR packages that you authored are so much easier to read so I really didn't want to go back to default WDS and friends if i didn't have too.
I'm trying to figure out a HMR setup to a existing non js server app (python) and it's proving difficult. I'm not to the point where i could feel smart enough to ask decent questions just wasting your time but maybe if I'm having trouble glueing everything together at the end i might bother you.

Issue addressed in https://github.com/hedgepigdaniel/webpack-hmr-client


version: added command

The version command was added. The version string gets set at compile
time by linker flags. If the build script is not used, the version will
read: "0.0.0+was-not-built-correctly".
Note that the build now fails when there are no git tags.

Addresses https://github.com/appc/acbuild/issues/37

As far as what values to use for the tags of acbuild, I think just having them track the version of the appc spec acbuild uses would be appropriate.

Should be ready for another pass.

ship ittttt


Create mfit_collect_aws_guest_ssm.sh

This adds a script which performs guest collection on all AWS instances connected to SSM.
It will call aws ssm describe-instance-information to generate a list of VMs. All arguments given to the script are passed directly to aws ssm describe-instance-information, so you can set the region by calling mfit_collect_aws_guest_ssm.sh --region eu-north-1, or filter to a specific set of instances by calling mfit_collect_aws_guest_ssm.sh --filters "Key=InstanceIds,Values=<MY_INSTANCE_ID>" as documented here.

@eitanm4a please take a look. Thanks!


Make tests compatible with latest version of AVA

Tests were throwing the 't.end is not supported in this context.' with
latest version of AVA so I removed all the t.end() calls since it seems
to no longer be necessary. May also want to consider specifying a version for AVA
in package.json.

May also want to consider specifying a version for AVA
in package.json.

Nah, this was probably the last breaking change ever. Don't want to have to constantly update AVA of hundreds of tiny modules.

Makes sense. Thanks for all the handy modules!


devonfw documentation still uses the term OASP in some cases

Category: enhancement
Severity: Medium
Expected behaviour (In case of bug)
The term OASP should be used only where the historic context is obvious like in "devonfw is based on OASP, the former Open Application Standard Platform. OASP has now merged into devonfw and is not a separate product any more."
Actual/current behaviour (In case of bug)
On https://github.com/devonfw/devonfw-tutorial-sources/wiki/devonfw-intro I read

devon4ng: the OASP implementation based on Angular framework.

Steps to reproduce (In case of bug)
look at https://github.com/devonfw/devonfw-tutorial-sources/wiki/devonfw-intro
Description of issue / expected enhacement /Comments
search for all ocurrences of "OASP" in the wiki and remove/replace with devonfw if it is not in a historical context
Your environment - windows/Linux, Devonfw version , component
irrelevant

Hello @Jan-PeterRichterCG ,
This issue has been solved by searching and finding the uses of "OASP", this should be the last one, the rest are regarding historic context.

devon4ng: the devonfw implementation based on Angular framework.

i am gonna close this issue since it has been solved,
Thanks for the feedback and regards,
trivesc


an error occur while using subQuery

sql: converting argument $1 type: unsupported type xorm.sqlExpr, a struct

this is my code:
var actList []YActivityModel

err = Engine.Table("y_activity_model").Select("id,title,address").Where("id in (?)", Engine.Table("y_apply_model").Select("activityId").Where("uid = ? and like = 1", uid).QueryExpr()).Find(&actList)

did i miss something?

Can you provide SQL logs?

sorry,delete this feature in an update, and now it's restored

pls update new version

seems caused another error :
Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'like = 1))) AND (deleted_atIS NULL ORdeleted_at=?)' at line 1
following is sql log:

my code
Engine.Table("ycy_activity_model").Select("id,title,adddress,locationDesc,applyStartTime,applyEndTime,activityStartTime,activityEndTime").Where("id in (?)", Engine.Table("ycy_apply_model").Select("activityId").Where("uid = ? AND like = 1",uid).QueryExpr()).Find(&actList)

sorry, my mistake, it works now! thanks for your fantastic job!


NASIC missing images

Interested in NASIC, but it's missing a lot.

@dmbarbour the images were updated on README xD

Thanks!
On Fri, Jun 7, 2019 at 7:51 AM MaisaMilena<EMAIL_ADDRESS>wrote:

@dmbarbour https://github.com/dmbarbour the images were updated on
README https://github.com/moonad/Whitepaper xD
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/moonad/Whitepaper/issues/3?email_source=notifications&email_token=AAHAIVIJJWTDV5S4C3W525LPZJKWXA5CNFSM4HPGVLAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXFXHYA#issuecomment-499872736,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHAIVPOCP5SS2QFJ6WSVYTPZJKWXANCNFSM4HPGVLAA
.


Disable automatic discovery of projects by default

The automatic discovery was a nice idea but seems to lead to too many issues right now.
Projects are detected which should not be detected, people are confused, nix evaluation is crashing, etc.
For most people it's probably better to specify the projects manually.
For the makeFlakeOutputs interface, we could do the following:

introduce a new field apiVersion which defaults to 0 but if set two 1, disables automatic project discovery and forces the user to specify the projects manually. (this will become the default for our flake templates and examples)
introduce a new field discoverProjects which if set to true re-enables automatic project discovery even if apiVersion = 1.
change all examples under ./examples to use apiVersion = 1 and specify projects manually. They should basically use this style instead of this style
provide a CLI utility that discovers projects and dumps them to a projects.toml (just a nix eval wrapper around framework.functions.discoverers.discoverProjects)
change the basic flake template, to read the projects list from the projects.toml file that doesn't exist by default.
if user initializes our basic flake template and does not specify any project, crash and instruct the user on how to use the new CLI urtility to generate the projects.toml.

What do you think about that?
@yusdacra @chaoflow @phaer @hsjobeki

I agree that it's probably I good idea to disable auto discovery at by default.
Personally I wouldn't feel like it's necessary to keep backwards-compatibility as the upgrade should be rather clear and simple, but as I am very new  to this project I might be missing context and/or use cases here.
Whats the rationale behind projects.toml? Is it because toml might be friendlier to users new to nix? Otherwise wouldn't a cli which outputs a nix snippet to include in your flake (or default.nix) work just as well?

They should basically use this style instead of this style

Just a heads-up, the first link is broken due to an extra "x" at the end (fixed in my quote)

I agree with this mostly, but I'd rather not bother with keeping backwards compat. I think instead we should just builtins.throw if projects is not specified and point users to documentation on how to upgrade. And if we are going to add a projects.toml file for the default example, IMO we should consolidate both nix_systems and projects.toml into one file. Having two files (with different formats) is more confusing for users.

I'm unsure about auto-discovery and need a couple of real-world examples before having an opinion as of when auto would be good: single package python project, could be one, however, that feels more like having sane defaults.

I'd disable auto-discover by default, not sure whether to even offer an option to turn it on
also don't see a need for backwards compatibility (there is a clear warning on top of the readme - it could be in bold font, but ...)
We should introduce an api version, once we're ready to support that version alongside a potentially instable api
I'd avoid an extra file and like @phaer 's idea about the nix snippet -- however. How many projects do people have within a repo? If we only have to point at the directories, I would not bother with the snippet but just have people write the couple of lines manually

I'd rather focus on sane defaults and having a minimal flake.nix for standard use cases, then code generation.

Whats the rationale behind projects.toml? Is it because toml might be friendlier to users new to nix? Otherwise wouldn't a cli which outputs a nix snippet to include in your flake (or default.nix) work just as well?

Dumping to toml or json is just quicker to implement. I don't know a library that dumps a data structure to a .nix file. It just requires implementing more logic. Also TOML is a pretty nice format. But I'm fine with nix as well.
OK, then let's implement that change

reviews of my PR much appreciated


interactsh: 1.0.6 -> 1.0.7

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/projectdiscovery/interactsh/releases.
meta.description for interactsh is: "An Out of bounds interaction gathering server and client library"
meta.homepage for interactsh is: "https://github.com/projectdiscovery/interactsh"
meta.changelog for interactsh is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.7 with grep in /nix/store/srrmqw4jaihpb0jpz526l50aiwqmya14-interactsh-1.0.7
found 1.0.7 in filename of file in /nix/store/srrmqw4jaihpb0jpz526l50aiwqmya14-interactsh-1.0.7

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
interactsh

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/srrmqw4jaihpb0jpz526l50aiwqmya14-interactsh-1.0.7 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A interactsh https://github.com/r-ryantm/nixpkgs/archive/9da04518972fd061ecddd8616381f7727a12b0b9.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/srrmqw4jaihpb0jpz526l50aiwqmya14-interactsh-1.0.7
ls -la /nix/store/srrmqw4jaihpb0jpz526l50aiwqmya14-interactsh-1.0.7/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

interactsh

Maintainer pings
cc @HanEmile for testing.

Result of nixpkgs-review pr 192302 run on x86_64-linux 1

1 package built:

interactsh


Remove require-jsdoc

End-of-Life for Built-in JSDoc Support in ESLint

The require-jsdoc and valid-jsdoc rules will be deprecated. These two rules will remain in ESLint but we will no longer add new features or fix bugs for them. These rules may be removed in a future major release of ESLint.

I recommend removing require-jsdoc all together. I find it more a nuisance than useful. If we do want JS Doc stuff, then we can add it back with eslint-plugin-jsdoc

Team keep IF we can customise the rules. Please show me how to turn off some stuff like return 😅

I like having something that pesters me to add documentation, but I would like to relax the rules. For example, sometimes param or return descriptions can be redundant and not all that useful, and you can turn those off with requireParamDescription and requireReturnDescription

I personally don't like the required parameters part of this.

I have trouble remembering the syntax, and
I don't find it to be the most straightforward way to describe a function's purpose. And then a comment can end up having enough technical jargon in it that it's easier to just read the code (because at least it's colorful in the code).

But, I agree with Sandy that if it's a contentious issue, that means we should keep it.

per @nerdpruitt:

I like having something that pesters me to add documentation

I agree. Interestingly, having strict rules here doesn't mean that you add accurate or meaningful documentation. Some a simple "psst, don't forget to document this for future you and your teammates" is probably the best thing we're trying to achieve here.
For me, knowing the type of data expected is helpful. I guess that's why typescript has really taken off, but I don't want that level of forced conformity, so forcing it here feels maybe like the wrong thing.
I don't want to use Ashur's words in a way he might not have intended, but I do think having a team culture of documenting is a good thing. I've been too lax there in the past — just trying to move fast, thinking how I write things is plenty self-documenting, deadlines, etc — and we can see how that has made it harder for people to get up to speed.

tl;dr — I think tooling that enforces some kind of documentation is important as part of our collective code building; whether that's require-jsdoc, or something else that helps us maintain what I see as benefits of documentation, I'm game.

Note — This is primarily in reference to non-TypeScript projects ☺

Benefits of Documentation
Things I really appreciate from documented code:

Showing my work — it's an inline artifact of what I was thinking at the time I wrote that code, and how I intended it to be used
Increased speed of understanding — it's slower the first time to document, sure, but the next time I come back I can just read the CliffsNotes instead of the whole book
Increased speed of usage — I get TypeScript-like autocomplete of those functions and their parameters in my editor, which speeds me up during development

JSDoc is a little goofy and maybe kind of old, but it has a nice, cross-language history and lots of native support in tooling.
In Practice
JSDoc supports a ton of properties, but my ideal block looks something like this:
/**
 * Shortest possible summary of what the function does
 * @param {type} name - optional summary where warranted; use your best judgment
 * @return {type}
 */

Summary
/**
 * Shortest possible summary of what the function does

Helps me understand what the function does without having to read and interpret the code. Sometimes I'm just perusing things rather than using them (reading utility functions, filters, shortcodes, etc.) just to familiarize myself with a codebase.
This can feel redundant for very simple functions. I definitely get that! My personal opinion is to trust your best judgment — can the next developer who looks at your code:

PR reviewers
new folks who are onboarding
you in six months 😅

understand what it does just by reading the function name and its signature?
function addTwoNumbers(a, b) {

If so, then maybe a summary is OK to skip 👍
Parameters

Note — This is an important part of populating editor autocompletion

@param {type} name [- optional summary]

In short, what does this function expect me to pass along when I call it?
Data types are particularly important to me here: I can read through the code to figure out that foo could be a string, or an Object, or an instance of Foo, but it's a lot faster and more reliable to see it documented all in one spot:
@param {string|Object|Foo} foo

(In many, many cases, the variable name is self-documenting. In that case, I think it makes a lot of sense to skip the summary!)
Return Values

Note — This also helps populate editor autocompletion

 * @return {type}
 */

What should I expect when I call this function? An array? A Promise I need to await? Nothing at all?
Again, this is something you can glean from reading over the code, but (in my opinion) relying on that exclusively would tend to decelerate our overall velocity rather than accelerate it.
Personal Notes
I have two snippets in my text editor to make building out a JSDoc block quick and easy:
/** →
/**
 * @param {type} name
 * @return {type}
 */

and @param →
@param {type} name

to quickly add additional @param entries.

TODO Sandy - add writing JSDocs to the UXE Styleguide


Support Symfony 3

Seems fine to me, I would need the Symfony 3 support for my project. So it would be nice to merge it ASAP 👍
cc: @stephanecollot

Lo implemente aqui: https://github.com/MWSimple/AdminCrudBundle
Espero puedan aceptar los cambios si estan bien.
Saludos!

@koprivajakub
Seems fine to me, I would need the Symfony 3 support for my project. So it would be nice to merge it ASAP :+1:
cc: @stephanecollot

@stephanecollot could you merge the changes these guys made? :) I'd be needed to upgrade to Symfony 3 :)

If testing use "mwsimple/datetimepicker-bundle": "2.0.0",

SF3 https://github.com/MWSimple/DatetimepickerBundle/tree/2.0

Gracias!
Use https://github.com/MWSimple/AdminCrudBundle/releases/tag/v3.3.10

New release 2.0 ?
https://packagist.org/packages/stephanecollot/datetimepicker-bundle

For Symphony 3.4, this is also needed: https://github.com/stephanecollot/DatetimepickerBundle/pull/45


Fetch Done Status of Moodle for Learning Elements

User Story
As a User i want to see the status of an Learning Element (Done Status in Moodle)
Acceptance criteria

[ ] Done Status is fetched out of Moodle (Rest API in Moodle)
[ ] Display that an Learning Element is Done (Be it an Icon or any other form of visualisation)

Definition of Ready

[ ] User Story is small enough for Sprint
[ ] User Story is clearly understandable for everyone involved
[ ] User Story effort is estimated
[ ] User Story has acceptance criteria
[ ] User Story has added value for the product or development
[ ] User Story origin is known (stakeholder)
[ ] User Story is assigned to Release
[ ] Backend and Frontend are cloned from GitHub and Running locally
[ ] Basic knowledge of the backend and frontend architecture
[ ] Activity diagram (or sequence diagram) screenshot in issue

Definition of Done

[ ] All acceptance criteria are met
[ ] The implementation of the User Story has been successfully accepted by the Product Owner
[ ] The implementation is in GitHub
[ ] A code review has been performed (or created in pairing program)
[ ] Code conventions are followed
[ ] Unit test coverage must be greater than 90%
[ ] All tests must have passed
[ ] Technical documentation created (Feature documented in GitHub Wiki)
[ ] UML class diagrams and component diagrams created and up-to-date
[ ] Documentation in realization created (source code)
[ ] Changelog created (Clear description in merge request)
[ ] There are no known bugs

Currently there are 3 ways that come to my mind to get the needed information:

Manualy create the tokens in Moodle and save them in a custom Database-Table (Later a Rest-API call for each student is made)
make mariadb-SQL calls to get the needed Information out of the Moodle DB from our Backend and send it to the frontend
Give Moodle the functionality to also create a Token on student-login (if they do not have a token) and send it to our Backend

A possible solution:

There is a REST-Call core_completion_get_activities_completion_status, that returns the done status of a course for a specific userid. That way we could give our backend a Moodle-admin user and send all the statements from our backend for each individual user.


Install CloudSDK task is slow.

My build process took 3.4 minutes, installing gcloud tools took 1.7 minutes.  Is there a way to make it slimmer version for VSTS?

The new version has a new Cloud SDK Tool Installer task (under the Tools tab). It appears to be much quicker, taking under a minute, and allowing tool caching.


May be a django_storage.py bug

I think the last line of the django_storage.py may not correct, because according to the logic description:

Return only statements that are in response to another statement.
A statement must exist which lists the closest matching statement in the
in_response_to field. Otherwise, the logic adapter may find a closest
matching statement that does not have a known response.

The query statement should be "RESPONSE_ID IN ..." but
Statement.objects.filter(in_response__in=responses)

change to "STATEMENT_ID IN ..." and I think the correct coding should be
Statement.objects.filter(responses__in=responses)

@zorrofox see this line is suggesting in_response_to converted into in_response. In this context in_response object referring to another statement, so i think it should be
Statement.objects.filter(in_response__in=responses)

I  don't very understand your meaning. But the test fact is also showing the logic is not correct. Bellow is separately training English Greetings CORPUS with JSON file storage and Django storage adapter logging.basicConfig(level=logging.INFO) output:

@zorrofox Thanks, if possible could you create pull request for this issue?

Sure! I have created one please review.


No more email accounts after upgrading to <IP_ADDRESS>2

I have several other email accounts from my server added to my main email account on rainloop so I can quickly check them all. After I have upgraded to <IP_ADDRESS>2, I can only see my main email account. All other accounts have dissapeared. I had to add them manually. I have upgraded from 1.7.x (last version of that branch).
Any clues?

Version 1.8.1 it is breaking changes. You need to recreate your accounts and identities.

1.8.1 New storage for settings. (You need to recreate your accounts and identities)  (Warning! Breaking changes) - 14.02.2015
#457

Oh, ok. I didn't know that. Thanks for the info.


GIFs not animated while dragging onto canvas

Bug Description
When dragging a Tenor GIF onto the canvas, the GIF is not animated.
Possibly related: #1930, #1979, #5006
Expected Behaviour
GIF should stay animated while dragging.
Steps to Reproduce

Drag GIF from Tenor 3P Media tab onto canvas
Notice it isn't animated anymore

Screenshots

Additional Context

Plugin Version: 1.1.0
Operating System: macOS
Browser: Chrome 86

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

Need to change from native D&D to movable so that the animation can occur during the drag process

Assigning 1 SP to this since it should get fixed by #5335 but we should still track it and test it.

Verified in QA

Looks good.

Looks good.


Minor fix for lighttpd example in README

Fixes #579
Signed-off-by: pixdrift<EMAIL_ADDRESS>

Since this got all the LGTM in other PR. I am just going to merge.
Thanks @pixdrift
@rh-atomic-bot r+

@pixdrift good job


helm: Update Helm chart dependencies

This PR upgrades Prometheus, Alertmanager, and the Prometheus Operator
Helm charts to the latest released versions.
Fixes #1850

Thanks for taking a look @gianrubio.
I also see a WIP PR of the charts here. Is that planned to be the canonical location for the charts going forward? If so and that PR is close to being merged feel free to close this PR.

Sorry for the inconvenience, but the prometheus-operator and kube-prometheus helm charts are currently being migrated to the upstream stable helm charts. Because of this we are currently not accepting any pull requests. We apologize for the inconvenience, but this is necessary for the migration to actually happen. We announced this here: https://github.com/coreos/prometheus-operator/tree/master/helm#warning
You can view the progress and help here and here.
Thank you for your understanding! :slightly_smiling_face:

@gianrubio No problem at all -- I'm thrilled to see the progress on the upstream stable chart and we're looking forward to trying it out. 👍


This is probably not good...

with B:EnableTerraforming=false

Biome Changer is inaccessible with terraforming false.  Though the recipe shouldn't register... will look at that.


enable "Packet socket created in container" by default.

Signed-off-by: Hiroki Suezawa<EMAIL_ADDRESS>
What type of PR is this?
/kind rule-update
Any specific area of the project related to this PR?
/area rules

What this PR does / why we need it:

I want to enable "Packet socket created in container" rule by default.

"Packet socket created in container" rule was created at the end of last year. I think we can say the rule is stable.

https://github.com/falcosecurity/falco/pull/945

The rule can detect ARP spoofing attacks on Kubernetes.

Ref: https://blog.aquasec.com/dns-spoofing-kubernetes-clusters

and new kernel vulnerability(CVE-2020-14386, allow privilege escalation to node) was disclosed recently.

The bug is in net/packet/af_packet.c, so we could detect an attack to the vuln by this rule as far as I read reporter's message and patch.

fyi: the rule can detect socket(AF_PACKET, ... syscall.

This is High severity bug, It's great if Falco can detect it by default!
Ref: https://cloud.google.com/kubernetes-engine/docs/security-bulletins?hl=en#gcp-2020-012

Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

rule(macro consider_packet_socket_communication): enable "Packet socket created in container" rule by default.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign kaizhe
You can assign the PR to them by writing /assign @kaizhe in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

rules/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 7e7268728ce7e5eef378b85cada3e3109cad2f76

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

rules/OWNERS [fntlnz]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Thanks @rung !
@Kaizhe PTAL :)

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz, leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

rules/OWNERS [fntlnz,leodido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

I am on paternity leave now so I will defer to @mstemm , for not blocking the PR review.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz, leodido, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

rules/OWNERS [fntlnz,leodido,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

I'm closing and re-opening this to let GitHub checks start again

This seems to be stuck. I'll look at the web hooks. Thanks for the patience @rung

Thanks! no problem.
if I can do something to resolve the issue, feel free to ask me 👍

The webhook was fine, looks like circleci is not keeping it.

I'm not sure but I think this might be resolved by re-run on CircleCI console.
(I use CircleCI at work)

New changes are detected. LGTM label has been removed.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign fntlnz
You can assign the PR to them by writing /assign @fntlnz in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

rules/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign fntlnz
You can assign the PR to them by writing /assign @fntlnz in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

rules/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign fntlnz
You can assign the PR to them by writing /assign @fntlnz in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

rules/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign fntlnz
You can assign the PR to them by writing /assign @fntlnz in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

rules/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

let me rebase master, and force push to re-run CI 👍

🎉 It seems I had to refresh CircleCI settings. The CI passed finally 😄
@fntlnz @leodido @leogr
Thank you for checking the CI status. Could you review this PR again when you have a time?

LGTM label has been added.  Git tree hash: 6d1bb0195b7edda951fd767232dc55e4a528a081

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

rules/OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

rules/OWNERS [fntlnz,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


[BUG] MediaServices Assets.DeleteAsync "object reference not set"

Describe the bug
On client.Assets.DeleteAsync with Microsoft.Azure.Management.Media including a valid id for the asset in question it throws an object not set error.
Expected behavior
Should delete the asset.
Actual behavior (include Exception or Stack Trace)
Crash.
To Reproduce

Create a client
Create media services asset.
Delete the same asset.

Environment:
nuget: Microsoft.Azure.Management.Media 3.0.3
.net core 5

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

@jhancock4d, is it possible to provide a call stack for the crash? Thanks

@jhancock4d, is it possible to provide a call stack for the crash? Thanks

@jsquire - Are you able to provide a call stack for the crash? If this isn't available, please provide your media services account name and Azure DC location and date that you saw this issue look into investigating this from logs.

@akucer:  Please be aware that I am only serving as first triage.   The reporter of this issue is @jhancock4d;  you'll need their insight on your inquiry.


Fix scripting of tables with index on non first columns (#2424)

Description
When exporting ddl_script for tables with indexes/constraints on columns which are not first in the table definition, wrong table definition in scripted. This is because the scripting tool uses sys.index_columns underneath and we are not returning the correct output currently. We also need to fix the index_id in sys.indexes since index_id is unique id for each index per table. index_id in sys.indexes and sys.index_columns should be same. Also fix sys.generated columns. Currently returns duplicates entries when two tables have same name generated columns.
Cherry Picked From
https://github.com/babelfish-for-postgresql/babelfish_extensions/pull/2424
Issues Resolved
[BABEL-4817],[BABEL-4853]
Sign Off
Signed-off-by: Tanzeel Khan<EMAIL_ADDRESS>Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.005%) to 72.561%

Files with Coverage Reduction
New Missed Lines
%

contrib/babelfishpg_tds/src/backend/tds/tdscomm.c
3
73.33%

Totals

Change from base Build<PHONE_NUMBER>:
-0.005%

Covered Lines:
41131

Relevant Lines:
56685

💛  - Coveralls


Fix compilation on lynx xenial

voxblox did not build on the lynx-xenial jenkins server

test this please (temporarily switch to always build on lynx xenial)


Filtering resources with attribute (WIP)

IMPORTANT: Where possible all PRs must be linked to a Github issue
Fixes for https://github.com/opensrp/fhircore/pull/1899#pullrequestreview-1227145735
Checklist

[ ] I have written Unit tests for any new feature(s) and edge cases for bug fixes
[ ] I have added any strings visible on UI components to the strings.xml file
[ ] I have updated the  CHANGELOG.md file for any notable changes to the codebase
[ ] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
[ ] I have built and run the fhircore app to verify my change fixes the issue and/or does not break the app

adding some tests, will mark PR ready once done.


[Feature Request] support ExtendedSocketOption in highlevelClient

Is your feature request related to a problem? Please describe
Now httpcomponents supports ExtendedSocketOption（TCP_KEEPIDLE, TCP_KEEPINTERVAL, TCP_KEEPCOUNT ） in https://github.com/apache/httpcomponents-core/pull/473, and releases the 5.3.
Describe the solution you'd like
If we can upgrade the httpcore5 version from 5.2.5 to 5.3 and use the ExtendedSocketOption in highlevelClient? I'm pleasure to do it.
Related component
Clients
Describe alternatives you've considered
No response
Additional context
No response

[Catch All Triage - 1, 2,  3,  4]

@kkewwei sure, please go ahead (please don't forget to update the httpclient5 to 5.4.1 or above if available), thank you


hyper-search wont work post last update

hyper-search wont work post last update (v2.1.0).
Error on the console is as follows :
Uncaught TypeError: term.getRowCount is not a function
at HyperSearchTerm.legacySearch
/.hyper_plugins/node_modules/hyper-search/src/containers.js:312:30

[ x] I am on the latest Hyper.app version

[x ] I have searched the issues of this repo and believe that this is not a duplicate

OS version and name: Mojave

Hyper.app version: 2.1.0 (stable)

The issue is reproducible in vanilla Hyper.app:  Yes

Issue
hyper-search wont work post last update (v2.1.0).
Error on the console is as follows :
Uncaught TypeError: term.getRowCount is not a function
at HyperSearchTerm.legacySearch
/.hyper_plugins/node_modules/hyper-search/src/containers.js:312:30

I just happen to install it and it works like a charm on my end.
I have the same setup as you.
Hyper: 2.1
Hyper-search: 0.0.11
OS: Mac OS Mojave 10.14


v5.1.3 requires yarn 3, which removes classic yarn support

Describe the bug
Before the release v5.1.3 there was no yarn version requirement, and the package was working fine with the classic yarn. However, after the upgrade this package now requires yarn 3.
On a side note, I am not really sure but I don't think that yarn v3 even exists.
To Reproduce
Try to install the package @mikro-orm/nestjs with classic yarn (yarn v1).
Expected behavior
I believe there is no need for requirement for yarn v3 (or v2) since the package was working fine with classic yarn.
Versions

Dependency
Version

node
16

typescript
4.8

mikro-orm
5.5

the engines constraint is apparently weird, this sounds more like yarn v1 bug to me, but lets remove it.
note that yarn v1 is a legacy project, yarn stable is v3, the project is in yarn/berry repository. the constrain should be taken into account only for the project collaborators, not for users - in other words, this was never meant to surface when you install it as a dependency...

fixed in 5.1.4

Thank you!


⚠ Bofrost.at has degraded performance

In fbe20ed, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1382 ms

Resolved: Bofrost.at performance has improved in c701562 after 6 minutes.


Update Newtonsoft.Json to 12.0.1.

Merging while we continue to restore CI on the 0.6 release branch.