IFile.Open(Read) cannot be mocked with NSubstitute anymore due to System.IO.Abstractions.FileSystemStream

Describe the bug
I am upgrading from System.IO.Abstractions v17.0.18 to v19.2.29.
To Reproduce
using System.IO;
using System.IO.Abstractions;
using System.IO.Abstractions.TestingHelpers;

// ...
        [Test]
        public async Task FileSystemStreamBrokenTest()
        {
            var fileSystem = Substitute.For<IFileSystem>();
            var fileStream = System.IO.Abstractions.FileSystemStream.Null;
            fileSystem.File.OpenRead(default!).ReturnsForAnyArgs(fileStream);

            fileSystem.File.OpenRead("somePath");
        }

This fails with an NSubsitute error though:

Also, Resharper suggests to simplify it in a way that it is essentially the same as this:
        [Test]
        public async Task FileSystemStreamBrokenTest()
        {
            var fileSystem = Substitute.For<IFileSystem>();
            var fileStream = System.IO.Stream.Null;
            fileSystem.File.OpenRead(default!).ReturnsForAnyArgs(fileStream);

            fileSystem.File.OpenRead("somePath");
        }

...which may explain why it fails.
Before all that I had a custom class for fileStream, which just also had the most common stuff implemented, so it was like your mock, except of the special type. Now the types don't match (I guess since v18.0.2) and as such I need to adapt it...
I tried this, too:
        [Test]
        public async Task FileSystemStreamBrokenTest()
        {
            var fileSystem = Substitute.For<IFileSystem>();

            var fileStream = new MockFileStreamFactory(new MockFileSystem()).New("anything.example", FileMode.Open);
            fileSystem.File.OpenRead(default!).ReturnsForAnyArgs(fileStream);

            fileSystem.File.OpenRead("anything.example");
        }

but that (kinda correctly) fails with:

System.IO.FileNotFoundException : Could not find file 'anything.example'.

....but I just wanna mock "any file", I don't care about what content etc.
Expected behavior
System.IO.Abstractions.FileSystemStream.Null should be useful as a wrapper, when you really don't care about your file handle/anything, but just want to mock it. I also don't wanr to mock a whole file system and provide any/all files in it, like I likely could with MockFileSystem.
Additional context
Finally found a workaround as . always exists:
        [Test]
        public async Task FileSystemStreamBrokenTest()
        {
            var fileSystem = Substitute.For<IFileSystem>();

            var fileStream = new MockFileStreamFactory(new MockFileSystem()).New(".", FileMode.Open);
            fileSystem.File.OpenRead(default!).ReturnsForAnyArgs(fileStream);

            fileSystem.File.OpenRead(".");
        }

IMHO there should be a more convenient way though.
System
		<PackageReference Include="System.IO.Abstractions" Version="19.2.29" />
		<PackageReference Include="System.IO.Abstractions.TestingHelpers" Version="19.2.29" />

and NSubstitute 4.4.0

Thanks for the report. I think we should shadow the Stream.Null field in our base class.
Contributions welcome :)

This is how I'm working around the issue, in case it can help anyone else:
/// <summary>
///     Wrapper around a <see cref="Stream"/> with no backing store, which
///     is used as a replacement for a <see cref="FileSystemStream"/>. As
///     such it implements the same properties and methods as a <see cref="FileSystemStream"/>.
/// </summary>
public class NullFileSystemStream : FileSystemStream
{
    /// <inheritdoc cref="Stream.Null" />
    public static new NullFileSystemStream Null { get; } = new NullFileSystemStream();

    /// <summary>
    ///     Initializes a new instance of <see cref="NullFileSystemStream" />.
    /// </summary>
    private NullFileSystemStream() : base(Stream.Null, ".", true)
    { }
}

Thanks for the detailed report!
I think we should shadow the Stream.Null field in our base class.
Contributions welcome :)

@fgreinacher: I don't think it would be a good idea, to add a test helper in the interface project. But we could add an option to simply create a "Null-Stream" similar to the solution from @sheila-stewart  to the TestingHelpers project.

I think we should shadow the Stream.Null field in our base class.

@fgreinacher: I don't think it would be a good idea, to add a test helper in the interface project. But we could add an option to simply create a "Null-Stream" similar to the solution from @sheila-stewart to the TestingHelpers project.

@vbreuss Why do you consider this a test helper? The Null stream is exposed by the base class and we should provide a working wrapper I think?

@vbreuss Why do you consider this a test helper? The Null stream is exposed by the base class and we should provide a working wrapper I think?

@fgreinacher:
The interface wraps a FileStream which does not have a static Null property itself, but only the base type, which returns a Stream and not a FileStream.

If we include this in the interface, we add something that is not there in the real file system.
I think it a good idea to simplify creating a Null-FileSystemStream, but I would add this to the TestingHelper project and not to the interface project itself.

Maybe add the ability to mock a stream with no backing store like this:
var nullStream = new MockFileStreamFactory(new MockFileSystem()).Null;

Awesome, thanks!


Supporting TorchScript?

Hi,
thank you for the great work. Do you plan to provide TorchScript support in the future?
Best regards!

I think it is safe to say this is something we are not exploring unless we have a pressing reason to do so. But others are welcome to add this and submit a PR.

Just want to note that the bigger impediment is DGL supporting it. My understanding is it currently does not, so any effort would need to start there.


Using BuiltinClusterDataSerializable for Buffer, JsonObject and JsonArray instead of Refection implementation

Almost message send via vertx cluster using JsonObject, JsonArray & Buffer.
Implement using BuiltinClusterDataSerializable will improve performance of eventbus AsyncMap
Here is a summary of changes in this PR:

BufferDataSerializable
JsonDataSerializable
JsonArraySerializable

Did you measure the performance improvements ?

This PR has changed the indentation from the normal 2 chars to 4 on every file it has touched making it very hard to see the actual changes. @dinhnn  please change indentation to 2 chars

I think this would also introduce an incompatible change across the cluster.

I agree with @purplefox
I'm a bit concerned with the compatibility with application using the previous format (for a cluster using the same HZ version, for example 3.6.1, clients without this and client with this should still be able to interact).

+1 If there can be shown to be a performance improvement I think there is value in the PR, but not as the default behaviour (it could be enable using a system property for example)

Now I'm busy, but I will create performance test for it, please wait

Reopen if needed.


Update to net471, Moq 4.7.145, xUnit 2.3.1,  Microsoft.NET.Test.Sdk 15.5.0, devirtualize PixelMap

Merging as errors are due to AppVeyor CI configuration


[Event Request] Table 36 Sales Header - Ship-To Code - OnValidate

We would like to execute standard code also for credit doc types. To make this possible we would like to request the following event and changes to the ship-to code validation on sales header to be able to overrule IsCreditDocType.
            if ("Document Type" = "Document Type"::Order) and
               (xRec."Ship-to Code" <> "Ship-to Code")
            then begin
                SalesLine.SetRange("Document Type", SalesLine."Document Type"::Order);
                SalesLine.SetRange("Document No.", "No.");
                SalesLine.SetFilter("Purch. Order Line No.", '<>0');
                if not SalesLine.IsEmpty then
                    Error(
                      Text006,
                      FieldCaption("Ship-to Code"));
                SalesLine.Reset();
            end;

            // START ->
            //if not IsCreditDocType then
            OnProcessShipToCodeChangeForCreditDocuments(Rec: record "Sales Header", VAR ProcessShipToCodeChange: Boolean);
            if (not IsCreditDocType) OR ProcessShipToCodeChange then
            // <- END
                if "Ship-to Code" <> '' then begin
                    if xRec."Ship-to Code" <> '' then begin
                        GetCust("Sell-to Customer No.");
                        if Cust."Location Code" <> '' then
                            Validate("Location Code", Cust."Location Code");
                        "Tax Area Code" := Cust."Tax Area Code";
                    end;

Many thanks.

Use the existing event OnValidateShipToCodeOnBeforeCopyShipToAddress:
                CopyShipToAddress := not IsCreditDocType;
                OnValidateShipToCodeOnBeforeCopyShipToAddress(Rec, xRec, CopyShipToAddress);
                if CopyShipToAddress then


Added note to shortcut documentation for scenarios involving multiple folders

added note for shortcut creation scenarios where multiple folders are involved.

#sign-off


import jest defaults from jest-config

I got a conflict when deleting this from Jest's source tree, so I think it makes sense to remove the hard-coding.
There are some comments at the top of the file about defaults, do you want more from it?

This seems 👍  to me


model.train docstring is out of date

    def train(self, early_stopping_steps=10, min_epochs=30, max_valid_ler=1.0,
              max_train_ler=0.3, max_epochs=100, restore_model_path=None):
        """ Train the model.

            batch_size: The number of utterances in each batch.
            total_size: The number of TIMIT training examples to use.
            num_epochs: The number of times to iterate over all the training
                        examples.
            feat_type:  Is the identifier for the type of features we're using.
                        'mfcc13_d' means MFCCs of 13 dimensions with their first
                        derivatives.
            save_n: Whether to save the model at every n epochs.
            restore_model_path: The path to restore a model from.
        """

Currently there's some parameters that are not matching what is in the docstring.

This is related to #79

Looks like you've fixed this in #147 in commit fe3462a3a2d60cbd261ddbd18767d08fde0b0582

It's best to not close these issues until the code is merged. (The GitHub PR mechanism will automatically close the issues referenced in a merged PR, note how the Closes #... is handled)


Problem with categories that start with the same word

Recently we had a problem when we create the category design-pattern, the existing design category was overeaten by the new category and all the articles of design were removed.
We need to check if that is a problem with Jekyll or with the categories plugin.

Closing as discussed in #119


auto ack

updates and cleans up style
Fix incident view border and window size
Add auto-acknowledge feature

Fixes #43


windows dynamic linking "copy boost dlls to bin/" fails on clion layout

Thanks to @qqiangwu for pointing out the possible bug: https://github.com/biicode/boost/issues/10
Submitting as a separated issue here.

Just copy dlls to ${CMAKE_RUNTIME_OUTPUT_DIRECTORY} which is defined as ${BII_PROJECT_ROOT}/bin. Will this work in all layouts?


Nomalize 'To update, run' advice

Currently when you regenerate a requirements.txt, if you run with syntactically different, but semantically identical command line flags the 'To update, run' advice changes.
The 'To update, run' advice should be normalized by:

expanding short to long,
removing values that are already default,
sorting the arguments
removing arguments that don't change build behaviour like 'verbose'

Hello @graingert,
Thank you for raising this issue. Agree with you. Though it's a challenge since there is no convenient way to implement it via click's API.

Some arguments are also one-off for example --upgrade-package django.

Some arguments are also one-off for example --upgrade-package django.

You are right!

@graingert, @adamchainz
I've prepared PR #800 for this. Please test/review it when you get a chance.


[Epic] Greenhouse installer

Develop a distribution and installer for greenhouse artifacts on a Kubernetes platform.
Tasks:

[ ] Evaluate OCM to describe the SBOM/SBOD.

Closed in favour of #592


Is luarocks command 'make' must based on a local rockspec file?

Like the title,  Did luarocks command 'make' must based on a local rockspec file? What about a net file use like command 'install'?
 ~/Desktop/t-luarocks/ luarocks make https://raw.githubusercontent.com/idevz/vanilla/master/vanilla-0.1.0-1.rockspec --verbose

os.execute: 	'curl' -k -f -L --user-agent 'LuaRocks/2.2.2 macosx-x86_64 via curl' --connect-timeout 30 'https://raw.githubusercontent.com/idevz/vanilla/master/vanilla-0.1.0-1.rockspec' 2> /dev/null 1> '/private/tmp/luarocks_luarocks-rockspec-vanilla-0.1.0-1-2143/vanilla-0.1.0-1.rockspec'
Results: 1
  1 (number): 0

Error: Build error: Failed installing vanilla/spec/runners/response.lua in /usr/local/luarocks-2.2.2/lib/luarocks/rocks/vanilla/0.1.0-1/lua/vanilla/spec/runners/response.lua

the help info didn't  point out this.
 ~/Desktop/t-luarocks/ luarocks help make

LuaRocks 2.2.2, a module deployment system for Lua

NAME
	/usr/local/bin/luarocks make - Compile package in current directory using a rockspec.

SYNOPSIS
	/usr/local/bin/luarocks make [--pack-binary-rock] [<rockspec>]

make does not need a local rockspec; however it does need you to have already downloaded the source for the module.
For reference:

make = build + install
install = download + build + install

@daurnimator ,thanks a lot for your reference.
but, I'm sure that make need a local rockspec, without this it will throw an error like below:
 ~/Desktop/v/ tree ./
./
└── v
    ├── application.lua
    ├── bootstrap.lua
    ├── controller.lua
    ├── dispatcher.lua
    ├── error.lua
    ├── libs
    │   ├── cookie.lua
    │   ├── http.lua
    │   ├── logs.lua
    │   ├── session.lua
    │   ├── shcache.lua
    │   └── utils.lua
    ├── plugin.lua
    ├── registry.lua
    ├── request.lua
    ├── response.lua
    ├── routes
    │   └── simple.lua
    ├── view.lua
    └── views
        └── rtpl.lua

4 directories, 18 files
 ~/Desktop/v/ luarocks make

Error: Argument missing: please specify a rockspec to use on current directory.

luarocks make requires a local rockspec. You can download a rockspec with luarocks download --rockspec my_rock.
But since you're already giving it a full URL, you may simply fetch it with wget.

yes, and make couldn't use a online rockspec like install. @daurnimator 's reference is very image.

luarocks make requires a local rockspec. You can download a rockspec with luarocks download --rockspec my_rock.

It will happily download a rockspec if you give a http URL:
e.g. from my local fifo.lua directory:
$ sudo luarocks make https://luarocks.org/manifests/daurnimator/fifo-0.2-0.rockspec
Warning: falling back to curl - install luasec to get native HTTPS support
Updating manifest for /usr/lib/luarocks/rocks-5.3
fifo 0.2-0 is now built and installed in /usr (license: MIT/X11)

@daurnimator ,which version luarocks did you use? Mine is luarocks 2.2.2, and I couldn't use a online rockspec file.
 ~/Desktop/xx/ sudo luarocks make https://luarocks.org/manifests/daurnimator/fifo-0.2-0.rockspec

Error: Build error: Failed installing fifo.lua in /usr/local/luarocks-2.2.2/lib/luarocks/rocks/fifo/0.2-0/lua/fifo.lua
 ~/Desktop/xx/ luarocks

LuaRocks 2.2.2, a module deployment system for Lua

NAME
	/usr/local/luarocks-2.2.2/bin/luarocks - LuaRocks main command-line interface

@daurnimator ,which version luarocks did you use? Mine is luarocks 2.2.2, and I couldn't use a online rockspec file.

You can use an online rockspec file. but it doesn't download the module's source. Try:
git clone https://github.com/daurnimator/fifo.lua.git
cd fifo.lua
git checkout 0.2
sudo luarocks make https://luarocks.org/manifests/daurnimator/fifo-0.2-0.rockspec


Release 3.3.0

Coverage remained the same at 82.486% when pulling 17ad472dcde26401e14550ffba019f823d5e2386 on release/3.3.0 into f455a779921768186e3cc4229fb8a5186e32ca09 on master.

Coverage remained the same at 82.486% when pulling 17ad472dcde26401e14550ffba019f823d5e2386 on release/3.3.0 into f455a779921768186e3cc4229fb8a5186e32ca09 on master.

Coverage remained the same at 82.486% when pulling 17ad472dcde26401e14550ffba019f823d5e2386 on release/3.3.0 into f455a779921768186e3cc4229fb8a5186e32ca09 on master.


need a help

Hello, I have encountered some problems. I wonder if you can help me.
that:Failed to detect the name of this notebook, you can set it manually with the WANDB_NOTEBOOK_NAME environment variable to enable code saving.
wandb: Currently logged in as: zhouweiqing (use wandb login --relogin to force relogin)
wandb: ERROR Error while calling W&B API: project not found (<Response [404]>)
requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://api.wandb.ai/graphql
i can not solve it

I answered here https://github.com/marlbenchmark/off-policy/issues/5#issuecomment-1049703456

I answered here #5 (comment)

Your answer has helped me a lot. Thank you very much for your help.


params (from LoaderArgs) is not being populated with query params from the incoming request

What version of Remix are you using?
1.7.0, 1.6.7
II tried the latest remix, but also another previous version, which makes me believe this affects more versions
Steps to Reproduce

Make a request to the following resource route: example.com/graphQL?gqlQueryString=query%7BgetSites%7D
Attempt to access the gqlQueryString param in the loader like this:

export async function loader({ request, params }: LoaderArgs) {
   const gqlQueryString = params?.gqlQueryString // ❌ showing up as empty
}

However, if you extract the search param like this, I am able to access my query params
export async function loader({ request, params }: LoaderArgs) {
const gqlQueryString =
    new URLSearchParams(new URL(request.url).search).get('gqlQueryString') // ✅  query{getSites}
}

Expected Behavior
The params object that get exposed to the loader, should contain the same values that is returned from the following:
export async function loader({ request, params }: LoaderArgs) {
   const paramsTest1 = params.gqlQueryString // ❌ should exist but doesnt
   const paramsTest2 =  new URLSearchParams(new URL(request.url).search))).gqlQueryString  //  ✅ exists
}

Actual Behavior
Below is a link to the Codesandbox reproducing the error:
https://codesandbox.io/s/params-object--not-getting-populated-v8whw6?file=/app/routes/api/v1/graphQL/index.ts:638-688
Please look at the server logs:
1. params
Result: {}
❌ ^^^

2. params?.gqlQueryString
Result:
❌ ^^^

3. new URLSearchParams(new URL(request.url).search).get('gqlQueryString')
Result: query{getSites}
✅ ^^^

This is an intended behavior.
The params object doesn't include search/query params, only params on the route/pathname.
If your route is routes/$something.tsx then you will have params.something available there, but all search params needs to be read using the URLSearchParams object.
let { searchParams } = new URL(request.url)
let paramName = searchParams.get("param-name")

but all search params needs to be read using the URLSearchParams object.

Ahhh ok
Followups
So  routes/$something.tsx, the params look like this:
export async function loader({ params }: LoaderArgs) {
   console.log(params) // {something: 'some_value'}

Is there a case where we might multiple entries in the params object?
What the be the case in something like /people/$peopleid/orders/$orderId?
export async function loader({ request, params }: LoaderArgs) {
   console.log(params) // {peopleid: 'some_value', orders: 'some_value'}

Yes, the params object has ALL the params, not just the current route's params. Also note if you use the splat $ route, the params value is accessed as params['*'].


[FEATURE REQ] Add sdk support for DataFactoryExpression

Library name
This applies to management plane and dataplane DataFactory and Synapse libraries.
Please describe the feature.
Summary
In the datafactory API many of the properties have the ability to either be a constant value or an expression which will be evaluated at runtime.  For more information on expressions go here.  The structure of an expression is different that a constant value for example the FolderPath property of an AzureBlobDataset can either be a "string (or Expression with resultType string)".
Json representation
Constant
"folderPath": "foo/bar"

Expression
"folderpath": {
  "type": "Expression",
  "value": "foo/bar-@{ pipeline().TriggerTime}"
}

In this example when the pipeline is run in the first case the folder is always foo/bar, but in the second case the service will append the time the pipeline kicked off to the folder name.
Because the property can have multiple types the only real way to express this in openapi is to set it to an object which gets generated as object for dotnet dataplane and BinaryData for mgmtplane.  This makes it difficult for customers to know how they are supposed to construct these.
If modeled as object
Constant
  azureBlobDataset.FolderPath = "foo/bar";

Expression
  Dictionary<string, object> properties = new Dictionary<string, object>();
  properties.Add("type", "Expression");
  properties.Add("value", "foo/bar-@{ pipeline().TriggerTime}");
  azureBlobDataset.FolderPath = properties;

If modeled as BinaryData
Constant
  azureBlobDataset.FolderPath = BinaryData.FromObjectAsJson("foo/bar");

Expression
  azureBlobDataset.FolderPath = BinaryData.FromObjectAsJson(new { type = "Expression", value = "foo/bar-@{ pipeline().TriggerTime}"});

Solution
The main challenge from a client side is that we need an object that can dynamically serialize and deserialize a primitive or an object based on its current value.  We also should restrict the primitive type in strongly typed languages that can be assigned to the property since because its an object I can easily assign an integer to a field that expects a string.
To solve for this we should introduce a new type DataFactoryExpression<T> which defines which type can be assigned as well as which type the expression must evaluate to aligning with the documentation of the API but moving it from documentation to actual API shape.
This would allow us to use the exact same code whether we are assigning a constant or an expression
If modeled as DataFactoryExpressoin<T>
Constant
  azureBlobDataset.FolderPath = new DataFactoryExpression<string>("foo/bar");

Expresion
  azureBlobDataset.FolderPath = new DataFactoryExpression<string>("foo/bar-@{ pipeline().TriggerTime}");

There a lot of considerations on the API shape of DataFactoryExpression<T> that need to be worked out, but conceptually this would allow us to provide a much more user friendly SDK for libraries like DataFactory and Synapse who use these expression objects.

Hi Michael! Thanks for the detailed summary! I have two comment for this:
1 - Is this just for the "expression" in ADF? Or will it cover other "object" in ADF swagger, e.g. storedProcedureParameters?
2 - As we are trying to make every property to be a possible "expression", wouldn't it be the case that "DataFactoryExpression" being used everywhere? Is it possible that we assign primitive value by direct assignment and assign expression with DataFactoryExpression as below?
Constant
azureBlobDataset.FolderPath = "foo/bar";

Expresion
azureBlobDataset.FolderPath = new DataFactoryExpression<string>("foo/bar-@{ pipeline().TriggerTime}");

This would be for all properties that can be a primitive or expression.  There might be other properties that are untyped schema that wouldn't fall into this category.
The only way to achieve the syntax above in strongly typed languages would be to add an implicit cast
public static implicit operator DataFactoryExpression<T>(T value) => new DataFactoryExpression<T>(value);

For dotnet I don't think this violates any of the recommendations.
The only odd behavior would be for DataFactoryExpression<string> since both the expression and the T are the same type so it might look like you can assign either an expression or a value via the implicit.  This matters because the internal storage on the class needs to be set up correctly in order for serialization to know the difference.  We might have to check the incoming value to see if it has an @ and if so treat it as an expression otherwise treat it as a value.  I don't think any of the other T types have this issue.

You can't (shouldn't be able to) set the "type": "object" in swagger since that would preclude the value from being a string. I believe you intended to say "not specify the "type property". In OpenAPI3, this would presumably have been a oneOf declaration, and in Cadl, it would be a union.

...and for languages that support union types, taking a union of types as input would be perfectly fine.

yes I meant to say its set to any


No error/ warning shows when one Itreation is running and try to start another iteration

No error/ warning shows when one Itreation is running and try to start another iteration
API works fine for this , UI needs to show the Warning on screen
Video : https://drive.google.com/a/redhat.com/file/d/0B1qUq_laG6CObW5RVmdEUHVBQlk/view?usp=sharing

This issue is same as #839


Update badges for Travis CI and Coveralls. Fix #227

@Natim I'm not sure if this is what you have in mind.

Yes thanks.


Fix kwarg deprecation in Ruby >= 2.7

This fixes a kwarg deprecation warning for Ruby >= 2.7.
Motivation

Trying to get rid of deprecation warnings.
Test plan

See included automated tests.

Actually, this was a Problem on our end.


Control becomes dirty when using ngModel and model was changed NOT by the user

Control becomes dirty when using [(ngModel)] and the model being bound to was changed NOT by the user (for example loaded asynchronously from the remote server).
As per Angular documentation:

pristine - true if the user has not changed the value in the UI. Its opposite is dirty.

Plunker demo (inspect the ngOnInitmethod)
Expected:
After 2 seconds the following text line appears in preview:
is form pristine: true
Actual:
After 2 seconds the following text line appears in preview:
is form pristine: false
Why it's important?
It is very common to disable submission of the form based on status of the dirty/pristine property of it. This isssue breaks such a logic.

This should be fixed in the upcoming beta.6 release. Thanks for reporting!


problem

I sent the ETH to the address. But nothing happened. The transfer was lost, the ETH did not come http://prntscr.com/fgszlf http://prntscr.com/fgtphj

Do you have the private key for the 0x6988 address?

Hello I made myetherwallet 2 months ago and 2 times used!!! I am not sure maybe I created 2 wallets because I have saved all informations on my mac(I see now and there are 2 addresses and 1 privatekey.
before when I have putted my privat key I saw one wallet adress but now I see diferrent wallet adress
I have sent etheriums on my old wallet address and what I have to do?thanks

how is it possible use one private key wich could open 2 addresses?

I have sent 17 etheriums

help me with this problem

@pila656345

how is it possible use one private key wich could open 2 addresses?

You mistyped your private key

You are using a different private key today than you were 2 months ago

You are entering the private key information in a different location

In order to regain access to your account, you need to do exactly what you did the time you opened your account. Were you using the keystore file? Handtyping? Scanning a QR code? Do that again.
I also strongly recommend you do a full search for your computer for files named UTC--. These are the keystore files and it may be that you have another one laying around.
The last characters of the file name is your address, without the prefixing 0x
So for example you could search for 7cb57b5a97eabe94205c07890be4c1ad31e486a8 in addition to UTC to see if you find anything that way.
Lastly, look around for files that are created around the same date you created the wallet. Did you take a screenshot? Save a different format as your key? Save your information in a word doc? Password manager?

please listen me. I always use one private key(I know this exactly) and this key have opened wallet adress where I sent etheriums few days ago.i found on my post letters when I bought etheriums and with wallet address(old). I am sure it is mystake. how could I bought and sent etheriums with old wallet address and use same private key?

in my word document I have 2 wallets address and one key but this key now open another addres

all this information I have saved when created wallet

@pila656345 If you want me to assist, please email me at<EMAIL_ADDRESS>and we can talk privately and see what we can do and if there is a way to resolve. We have a couple new scripts I could try to run to eliminate the mistyping issue.
I cannot help you via github though because the last time I did it resulted in someone posting their private key publicly and then you can ensure someone will find your ETH but it's doubtful they will give it back.

There is a new tool at the very bottom that could prove useful for anyone who hand-typed or wrote their private key: https://www.myetherwallet.com/helpers.html
Enter the address you sent to and the private key you saved and see if it can find it


Premium Plan: WEBSITE_CONTENTAZUREFILECONNECTIONSTRING does not seem to support KeyVault integration

Whilst following the above steps in terms of setting up a Premium plan and setting the WEBSITE_CONTENTAZUREFILECONNECTIONSTRING  value to the storage account, I seem to keep running into the following error when I assign it using KeyVault integration (https://azure.microsoft.com/en-us/blog/simplifying-security-for-serverless-and-web-apps-with-azure-functions-and-app-service/)
I have recreated the resource and only changed that value to the actual ConnectionString from the Storage account and this seems to work. Upon then change it back in the ARM template to the KeyVault syntax, it caused the following error.
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"BadRequest","message":"{\r\n \"Code\": \"BadRequest\",\r\n \"Message\": \"The storage URI is invalid.\",\r\n \"Target\": null,\r\n \"Details\": [\r\n {\r\n \"Message\": \"The storage URI is invalid.\"\r\n },\r\n {\r\n \"Code\": \"BadRequest\"\r\n },\r\n {\r\n \"ErrorEntity\": {\r\n \"ExtendedCode\": \"04203\",\r\n \"MessageTemplate\": \"The storage URI is invalid.\",\r\n \"Parameters\": [\r\n \"No valid combination of account information found.\"\r\n ],\r\n \"Code\": \"BadRequest\",\r\n \"Message\": \"The storage URI is invalid.\"\r\n }\r\n }\r\n ],\r\n \"Innererror\": null\r\n}"}]}
Is this a bug or something that is not currently supported?

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

ID: a1ba8817-3e01-7e84-6c71-b98b131f2927
Version Independent ID: a7703386-9e83-1075-72ef-f9e63f3dc4de
Content: Automate resource deployment for a function app in Azure Functions
Content Source: articles/azure-functions/functions-infrastructure-as-code.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@wahyuen Thank you for your feedback! We will review and provide an update as appropriate.

@wahyuen As this is repo is meant for the documentation feedback, I would recommend you to open this issue on Azure Function GitHub Repo for better clarity.
Please note that Elastic Premium Plan Functions are currently in preview.

Linking for reference
https://github.com/Azure/Azure-Functions/issues/1195

Since there is no doc update required at the moment, we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


fix(ci): run full sync test with most size optimisations

Motivation
This could be faster than #3582

Error: buildx failed with: error: failed to solve: error writing layer blob: failed to parse error response 503: *** 'message': 'GitHub Actions is temporarily unavailable. Please visit https://www.githubstatus.com/ for the status of our services.', 'ref': 'Ref A: E079DBED32824FD0934F375F17623027 Ref B: SN1EDGE1816 Ref C: 2022-02-24T23:28:15Z' ***: invalid character ''' looking for beginning of object key string

😢

This was slower than #3582.


Add SonarCloud badges

Pull request type

Documentation content changes and added test
What is the current behavior?

We don't report any SonarCloud metrics in our README
Issue Number: closes #245
What is the new behavior?

Added badge for the SonarCloud badges from the dashboard to the README (Quality Gate, the different ratings and code coverage)
Add test for exiting with unsaved changes warning dialog to get code coverage for the one changed line since the release, otherwise the quality gate will be reported as "failed"

Does this introduce a breaking change?

N/A
Other information

Pull request checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added or the PR is neither a bug fix nor a feature
[x] Docs have been reviewed and added / updated if needed or the PR is neither a bug fix nor a feature
[x] The Unreleased section in CHANGELOG.md has been amended to reflect the changes in this PR if needed
[x] Build (mvn verify) was run locally and any changes were pushed
[x] The pull request is against the correct branch (master for bug fixes, develop for new functionality)
[x] Dependencies and citation templates have been updated where necessary or there are no new dependencies

Checklist for maintainers
Releases

Do NOT push the green merge button on GitHub.
Follow the latest version of the developer/maintainer docs for making releases.
Check that license and citation information for dependencies are complete (each dependency has a folder in /THIRD-PARTY/).

Thanks for merging. I also changed the setting what counts as new code from "last 30 days" to since "Previous Version" in the settings. This is only used for the "Quality Gate" badge as far as I can understand it. Since we now have several releases, and we are probably interested in how well we are doing, it makes more sense to have the quality gate refer to the next release instead of some arbitrary date.


go1.13.10 command not found

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

$ go get golang.org/dl/go1.13.10
$ go1.13.10 download
go1.13.10: command not found
$ go version
go version go1.14.2 linux/amd64

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

What did you do?

What did you expect to see?
I expected to be able to side load 1.13.10

This is likely a problem with your $GOPATH/bin not part of $PATH. And not an issue with Go.
Are you able to "go get" other binaries ? Like go get golang.org/x/perf/cmd/benchstat ?


Documentation on upgrade

Just upgraded from 0.7 to 0.8 and had to re-create my db due to schema changes, a "how-to upgrade" section within project README would be really helpful.

Hi @meesameesa , there isn't much to do in order to upgrade. You just need to start Konga in dev mode. All migrations will be handled automatically.
Check out issue #40


V2 - Sponsor Can Withdraw Unused Funds

As a sponsor who launches a challenge where not all funds are used, I want to be able to reclaim my funds, so that my money isn't lost
The Sponsor should be able to use this function, given the conditions are met:

no claims

OR

review deadline passed

This works in V1, want to make sure it works in V2 as well.
Time Mitigator:

We can still interact with this via Polygonscan
We can add the interaction later


Are Child Containers still relevant? Is there any docs?

Looks like they are alive, but I have no luck trying to find anything about their behavior.

Child containers aren't really documented because it is recommended to use handler selectors and sub dependency resolvers in preference to child containers. There are still edge cases that don't work as people expect with child containers.
Krzysztof wrote a blog series a few years back:

http://kozmic.net/2010/06/01/castle-windsor-and-child-containers/
http://kozmic.net/2010/06/02/castle-windsor-and-child-containers-reloaded/
http://kozmic.net/2010/06/03/castle-windsor-and-child-containers-empire-strikes-back/

Most of the Windsor docs were written during the time when there were some big defects with child containers so I suspect that is why no docs were written at that time.

Lifecycles are incredibly hard to propagate between parent child containers. This is an example of where I tried to submit a PR fixing transient disposals with parent registrations via child container resolution: https://github.com/castleproject/Windsor/issues/324.
The question I have is why is this abstraction necessary?
The Microkernel has so many ways of solving these problems(handler selectors and sub resolvers), what problem are you trying to solve by doing this?
Will add this to the V5 Windsor discussion which was looking more about obsolescence but now feels like we need to delete something that should have never existed.

Please join us over there to voice your thoughts.


[release/0.4] Bump go-fuse to v2.4.1

Issue #, if available:
Fixes #855 in release/0.4
Description of changes:
Backports #922 to release/0.4
Upgrading go-fuse to a tagged revision which contains the bug fix for the sparse file cp/mv/install bug on images with coreutils version >= v9.0.
(cherry picked from commit 192b50eb6b16809f604599585a3a2c7004ac3aa9)
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Reopened PR to pick up workflow changes to allow CI to run on release branches.


Adding quip as a cedar use case

Issue #, if available: N/A
Description of changes: Adding Quip under use cases. Included schema, policies, entity data, and sample authorization calls in a run.sh script.

Thank you for your contribution. I was wondering if this PR should be based on the main branch.

Good point, I've updated the base branch. Thank you!

This is great! I was a little surprised only to see User, Thread, and Folder as entity types -- why are there no Documents ?

Thanks! I modeled the entities off of the official quip documentation: https://quip.com/dev/automation/documentation/current#tag/Threads. Thread is an umbrella term for Documents, Spreadsheets, and Chats.
Note, there are extra attributes in the documentation that I did not include for simplicity.


SVG output lines between paths v3.4

Hi,
I've noticed that outputting the QR code as SVG generates SVG with lines that look like borders on some squares. I haven't managed to figure out what exactly those lines are, stroke, outline or just misalignment of paths, it seems like they are transparent. Here is a screenshot of SVG versus the PNG output so its easier to notice what I'm talking about.

My QR options are:
_
'version'     => 6,
'eccLevel'    => QRCode::ECC_L,
'outputType'  => QRCode::OUTPUT_MARKUP_SVG,
'imageBase64' => false
_
Can you try recreating the issue and looking into it please, maybe I'm doing something wrong. Thank you ahead!

Hey, it seems that's rather a browser issue, specifically rendering. The distance between the blocks should be 0 and there should not be a visible line regardless. I can see these lines too and it also depends on the browser's current zoom and changes with the zoom level, in both, chrome and firefox. As for the generation: at least the blocks of the same color in the same line should be connected and i found a bug that prevents this. I'll look into it as soon as i can but it's low priority as i'm currently revamping some internals. I can leave the issue open and tag it as "help needed" as i don't know too much about SVG to find an easy way how to fix it (one of which would be to connect all modules of the same color). Right now i can only suggest to use png output in case it's bothering.

Hey, it seems that's rather a browser issue, specifically rendering. The distance between the blocks should be 0 and there should not be a visible line regardless. I can see these lines too and it also depends on the browser's current zoom and changes with the zoom level, in both, chrome and firefox. As for the generation: at least the blocks of the same color in the same line should be connected and i found a bug that prevents this. I'll look into it as soon as i can but it's low priority as i'm currently revamping some internals. I can leave the issue open and tag it as "help needed" as i don't know too much about SVG to find an easy way how to fix it (one of which would be to connect all modules of the same color). Right now i can only suggest to use png output in case it's bothering.

Sounds good, thanks for the fast response I'll use the PNG temporary and probably dig a bit more about the issue itself. Again thank you for the help.

Sounds good, thanks for the fast response I'll use the PNG temporary and probably dig a bit more about the issue itself. Again thank you for the help.

I'm currently working on an overhaul of the SVG output module and honestly i have absolutely no idea where these lines come from. I'll check this off as rendering issue which is beyond my powers to fix. In the current iteration I'm rendering each module individually and one would expect the lines between each then, but instead they just seem to appear randomly:

Having individual modules however has its perks: a nice way to circumvent the line issue (and - surprisingly - there are no visible lines between the few square blocks!?)

So I'm going to close this issue for now.

Great! Thank you for taking the time to look into this. Awesome work!


⚠ Processors has degraded performance

In 0273a98, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 72 ms

Resolved: Processors performance has improved in 0cb1530.


Name Method is not working But all method are working why?

// Hi While im trying to learn typescript im getting Confuse with this code..
class Startup {
public static main(): number {
    console.log('Hello World');
    return 0;

}

}
Startup.main(); // works fine
class startUp{
   public static run(){
alert('hellow world run Static')
 }}

startUp.run();     // still works fine
class startup{
   public static name() {
	alert('hellow world');
	}

}
startup.name(); //getting error why i dont understand??
/* i dont understand why its not working.. */

Due to function name.  You can notice if you exec Startup.name you get "Startup". Startup is a function and functions have a name property.
http://i.imgur.com/fEiEu6s.jpg

See #442


Missing reference to Polly in Examples

You fail to mention in the example code that reference to Polly is required.
At this location: "Just for the example sake, you can see one of the above policies in the next code:"
[Enter feedback here]

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

ID: 7b506236-b211-eb9d-b571-5efecdde76c8
Version Independent ID: 24434b0e-0b82-e477-9440-2cc8f135df75
Content: Use IHttpClientFactory to implement resilient HTTP requests
Content Source: docs/architecture/microservices/implement-resilient-applications/use-httpclientfactory-to-implement-resilient-http-requests.md
Product: dotnet-architecture
Technology: microservices
GitHub Login: @nishanil
Microsoft Alias: nanil

Hi @laultman, thank you for reaching out.
This particular article can be considered as an introductory segment for the "IHttpClientFactory" and its benefits. Though "Polly" and it's policies are discussed in detail in Implement HTTP call retries with exponential backoff with IHttpClientFactory and Polly policies but the line The HttpClient can be configured with Polly's policies when registering the IHttpClientFactory in the DI container with the extension method AddHttpClient actually describes the fact that Polly needs to be configured with HttpClient.
Hope this helps !


UI affordance for Returning from History to Service List

To me opening the History View for a service does not feel like a web navigation (it seems I can return by using the browser’s back button) but an app click.
As a consequence I expect to see a button that closes the History View and takes me back to the app list.
Currently I can apparently hit Escape for the same effect (so someone thought of this like a modal dialog that can be dismissed rather than a web navigation as well?), but as I am typically operating with the mouse in that context, a button would seem handy.
I also suspect that the different approaches that work (web navigation as well as escape key) leaves it ambiguous to my mind whether I should think of the History screen as part of the web navigation or more like a modal dialog.

I cannot reproduce the part where ESC exits the history page.
But either way, I agree the scroll context should be preserved.


Conditional recipes

What feature do you want to see added?
The recipes.yml is a quite flat structure of recipes that OpenRewrite can understand.
But we cannot just apply recipes blindly on all plugins because they depend on the context and the nature of the plugin
The idea is to build some simple rules based on PluginMetadata flag
One very simple example (We need to see about the format. File ? Directly on the code ?)
rules:
    - recipe: AddGitHubSecurityWorlfow
      conditions:
         - "not IS_API_PLUGIN"
         - "HAS_SOURCE_FILE"

Upstream changes
No response
Are you interested in contributing this feature?
No response

Great idea, we definitely need something like that. 🚀


fix an exception if table source data is immutable type

If table source data is built by immutable object list, e.g. by seamless-immutable or immutable-js library, the table will be broken if list is empty, which is caused by a push action to the list.

is that cause by the immutable.js can't call the map method on any array?

Immutable list can call map method, but can't call push method on the list. Above PR avoids such case.

ok, thanks, I'll merge after my travel.

Released on v3.1.1, thanks your contributions


Fixed #5492 - Use get_placeholder_conf fallback for PlaceholderModel.get_label

PlaceholderModel.get_label did not implement the get_placeholder_conf fallback
Fix #5492

Ok to merge

Only a minor point to consider, OK to merge.

Coverage increased (+0.8%) to 89.532% when pulling 7087673cde444d1813c67cea52bb543ee313c482 on yakky:feature/fix_5492 into 3844f64b1c8f20157afd11bc488fb797bd26ac8e on divio:release/3.3.x.

Coverage increased (+0.8%) to 89.532% when pulling 7087673cde444d1813c67cea52bb543ee313c482 on yakky:feature/fix_5492 into 3844f64b1c8f20157afd11bc488fb797bd26ac8e on divio:release/3.3.x.

Coverage increased (+0.8%) to 89.532% when pulling 7087673cde444d1813c67cea52bb543ee313c482 on yakky:feature/fix_5492 into 3844f64b1c8f20157afd11bc488fb797bd26ac8e on divio:release/3.3.x.

Coverage increased (+0.8%) to 89.532% when pulling 7087673cde444d1813c67cea52bb543ee313c482 on yakky:feature/fix_5492 into 3844f64b1c8f20157afd11bc488fb797bd26ac8e on divio:release/3.3.x.

Coverage increased (+0.8%) to 89.532% when pulling 7087673cde444d1813c67cea52bb543ee313c482 on yakky:feature/fix_5492 into 3844f64b1c8f20157afd11bc488fb797bd26ac8e on divio:release/3.3.x.

Coverage increased (+0.8%) to 89.524% when pulling 3ed27d58712e6788027ee0822ccfae2cd6a5f9dd on yakky:feature/fix_5492 into 3844f64b1c8f20157afd11bc488fb797bd26ac8e on divio:release/3.3.x.

@yakky Can we merge? Need to wait till all travis tests finish before releasing :)

@czpython sure, this is complete from my side

@yakky Ok, I'll merge to start the release but would be cool if you can take care of forward port to develop.


feat: allow read more one line subtitle with page redirection JB-475

What does this PR do and why?
Provide a description of what this PR does. Link to any relevant GitHub issues, Notion tasks or Discord discussions.
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] (if relevant) I have tested this PR in all supported browsers.
[ ] (if relevant) I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #3756

PR #3757

PR #3758

PR #3759   👈

This comment was auto-generated by Graphite.

@wraeth-eth started a stack merge that includes this pull request via Graphite.

Graphite rebased this pull request as part of a merge.

@wraeth-eth merged this pull request with Graphite.


Use staging devfile registry for integration tests

What type of PR is this?
/kind cleanup
What does this PR do / why we need it:
Use staging devfile registry for integration test with devfile. Using a production registry would result in unnecessary overload.
Which issue(s) this PR fixes:
Fixes https://github.com/openshift/odo/issues/4639
PR acceptance criteria:

[ ] Unit test

[x] Integration test

[ ] Documentation

[ ] Update changelog

[x] I have read the test guidelines

How to test changes / Special notes to the reviewer:

/retest

/assign @rnapoles-rh

@mohammedzee1000 and @rnapoles-rh: please review. Thanks,

/approve
/lgtm


Add way of rejecting input with extra keys

If I have a case class like:
case class FoobarClass(optional_value: Option[String] = None)
And I receive input like:
"{"optional_valeu": "test"}" (note that "optional_value" is misspelled)
It'd be nice to be able to throw an exception immediately instead of silently using the default value for optional_value.  Is there a way to do this without defining my own RootJsonFormat?

Currently there is no way to do this but I agree that such a setting would be a valuable thing to have.
Thanks for the ticket!

@wsong and @sirthias I need the same feature: throw an exception if a field name was not known instead of silently ignoring the object and using the default value of the optional key. Is there any plan to merge [PR #166]?


Add a setter for offset x/y

Add a method that allows modifying the custom offset of a character after it has been added to GridEngine already.

Implemented with v2.30.0


Restoring backup should strip whitespace/tabs in Name field

Triple clicking to highlight will copy extra characters

pvc-5f6b68fc-1194-4580-abfe-3b0e4cc0e007
--

Error message:

Or, better yet, pre-populate with the Volume name instead @yasker

@ainiml original claim name can be chosen when creating PV/PVC for the volume. Just click use previous PVC checkbox.

@ainiml original claim name can be chosen when creating PV/PVC for the volume. Just click use previous PVC checkbox.

I don't think the option comes up if you are mass selecting

@ainiml yeah, though that's another issue.

Thanks for reminding me. Pr has been amended @ainiml

Validation: PASSED
Longhorn UI version: wangsiye/longhorn-ui:c36c682
Steps to test:

Create a volume, attach it to a node
Create a backup
Restore backup, Enter volume name that contains trailing spaces/tabs
Volume should be created successfully, trailing spaces/tabs should be removed. (PASS)


fixed typos in comments for examples

Minor fixes to comments in examples.
BTW, I don't see the examples compiled as part of the tests.
How do you make sure they compile?

Thanks a lot!


pythonPackages.pantable: init at 0.11.1

Motivation for this change
Useful helper tool for working with pandoc tables + dependencies.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
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 nox --run "nox-review wip"
[x] 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)
[x] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Version meanwhile refreshed up to 12.2. AFAIK good to go.


column grouping.

Now row grouping can be done using the level, but there is no functions to group the columns.

Yeah, guys! It will be amazing if 'level' property will appear for Column Object.

How to do row grouping with collapse sign using sheet JS in react


Updated video classification ref example with new transforms

Description:

Added README
Updated example's transforms.py
Updated train.py

Hi @fmassa and @vfdev-5,
I'll fill out these information (and test it out on a distributed cluster) sometime tomorrow before signing it off. :)


Updates to Extension class in common-source.yaml

updates descriptions of the Extension class and its properties to align with those in the original core-im.
added 'value' as a required property (an Extension object is of no use without a value . . . if there is no value available, the data creator should just not create the Extension object in the first place)

re: extensionDescription vs description as a name for this property.  I think description is actually fine . . . change if you want.


Feature/variable method

Not ready to be merged as the code isn't fully tested and there are no test cases or documentation for it yet.
The changes are based on my old code from 3 years back, which adds interesting feature to allow me to create sub-rules as variables and use those to build new rules. Those sub-rules are only compiled once (into true/false) and are very useful if you have a large set of different rules that get used in multiple locations.

Added description.
Sorry about this pull request. I'm not sure why github created a pull request on my changes as I've not yet even fully tested the code. I am 100% sure that I didn't create pull request yet. Maybe I accidentally had wrong upstream...
Are you still maintaining this project? I have also some other interesting things for Ruler, like a simple compiler that compiles lisp-like language into a set of rules (php code atm).

No, I'm not the package maintainer, just an avid user of Ruler.

Oops, I just assumed you were.
Has there been any word from @bobthecow ? He has been quite inactive on this project; should we start maintaining our own version of the library or is he still interested on maintaining it?

@bobthecow do you exist? There are quite a few PRs open including #37 which has been open for 2 years. There were a few things implemented because of the strict adherence to PHP 5.3 because it was the GA release at the time. Because of that, a good refactor and clean up would be nice to use some of the newer language features (only if warranted of course :) ).


Missing DPM++ 2S a Karras sampler

I heard this new sampler should be available thru Auto's. I updated the repo yesterday in colab with a ton of changes. Today it says it is up to date. I have not blown away my SD folder hoping it was part of Auto and not base SD.

Do you have to enable something before we get access?

rename/remove the folder "sd" from your gdrive and do a clean run

Awww man. Thanks!


Stop exporting SceneNode and RootNode

Contents of this Pull Request
This PR makes changes to

[x] The typings in the types folder
[ ] Configuration files (tsconfig.json, jsconfig.json, .gitignore etc.)
[ ] The sample files (e.g., sample.js)
[ ] The README.md or other files containing documentation
[ ] Other

Purpose of this Pull Request
Solve the problem with falsely exported classes SceneNode and RootNode of the scenegraph module.
Issues resolved by this Pull Request

fixes #56

@ericdrobinson any thoughts? Does this work on your end?

@pklaschka It works but there is one major caveat: I think you were a little overzealous in replacing the class name throughout the file. The only places that need the [Type]Class renaming are the actual class and subclass definitions. When you declare the interface for SceneNode and RootNode, you can continue to use those as types for constants, properties, return types, etc.
As the types exist in this PR at present, the type of require('scenegraph').root is RootNodeClass:

However, if you simply revert root's type declaration to export const root: RootNode; then you get the following:

Mind replacing the type annotations in scenegraph.d.ts with the interface versions of RootNode and SceneNode instead of the internally-named class versions?

@pklaschka Any movement on this? Perhaps a notification about the above comment slipped through the cracks?

I'm currently unable to update the repo as I'm in the middle of exams and don't have enough time. Until August 8th, I'll review (and possibly merge) pull requests, view comments, etc., but please understand that I don't have the time to actively update the repo for these next two weeks. Thank you very much for your understanding 🙂

@ericdrobinson I've found the time to fix that today (sorry it took so long, but it went right into my exams at university :sweat_smile:). If you have the time, could you perhaps look over it and see if it now works as expected? Thank you very much in advance.
Other than that, this is now a kind of mega PR also adding the new, panel-API application.editDocument() and fixes for a few other issues...

@pklaschka Awesome! Thanks for getting this done!
It seems that when you replaced the SceneNodeClass with SceneNode you didn't adjust the  definition of the sub-classes to implement SceneNode rather than extends SceneNode. Interfaces can extend classes but not the other way around.
Mind making the following adjustments?
// BEFORE:
export class GraphicNode extends SceneNode{
export class Group extends SceneNode{
export class SymbolInstance extends SceneNode{
export class RepeatGrid extends SceneNode{
export class LinkedGraphic extends SceneNode{
declare class RootNodeClass extends SceneNode{

// AFTER:
export class GraphicNode extends SceneNodeClass {
export class Group extends SceneNodeClass {
export class SymbolInstance extends SceneNodeClass {
export class RepeatGrid extends SceneNodeClass {
export class LinkedGraphic extends SceneNodeClass {
declare class RootNodeClass extends SceneNodeClass {

With the above adjustments, the class structure will work as expected.
I may have more suggestions. The above are the low-hanging fruit that VSCode reported as issues for me.

@ericdrobinson That should all be fixed now, thanks again for your input :slightly_smiling_face: :+1:

Same procedure as every PR :wink:
I'll wait for a few days (specifically, until Tuesday, 8:00 PM UTC), and if there are no objections until then, I'll go ahead and merge this, marking it as release 22.0 of the typings...


Error using intersection type for object rest destructuring

This is using the latest release-2.1 branch. I'm unclear why types B & C would behave differently below when it comes to object rest members, so I am assuming this is a bug. (ping @sandersn & @mhegazy ).
interface A {
    name: string;
    age: number;
}

interface B extends A {
    address: string;
}

type C = A & {address: string};

// Both v1 & v2 appear to have the same members...
var v1: B;
var v2: C;

// ... and assignment in either direction is fine
v1 = v2; // OK
v2 = v1; // OK

// let {name, ...x2} = v1;  // This line is valid (when uncommented)
let {name, ...x3} = v2;  // This line gives the error: Rest types may only be created from object types.

That's by design since (1) I don't know of a scenario that depends on it (2) I expect in 2.2 we'll have real rest and spread types that handle intersections correctly.
Currently intersections of object types are not object types themselves. They stay intersections, which makes it hard to track the difference between an intersection that contains type parameters (not usable with rest) and one that doesn't (could be usable with rest).
If this is a common scenario we can flatten all-object intersections to object types for now and revisit when we add rest types. But I would prefer to do nothing for 3.1 unless it's important.

From: Bill Ticehurst<EMAIL_ADDRESS>Sent: Saturday, November 26, 2016 10:08:04 PM
To: Microsoft/TypeScript
Cc: Nathan Shively-Sanders; Mention
Subject: [Microsoft/TypeScript] Error using intersection type for object rest destructuring (#12520)
This is using the latest release-2.1 branch. I'm unclear why types B & C would behave differently below when it comes to object rest members, so I am assuming this is a bug. (ping @sandersnhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsandersn&data=02|01|nathansa%40microsoft.com|0a5d4ea4cefe487a6b0e08d4168bc057|72f988bf86f141af91ab2d7cd011db47|1|0|636158236852606225&sdata=20%2FmBvybZQkSukFXxP1KJ%2FAWxQhsQP7o12DFeI17bZ4%3D&reserved=0 & @mhegazyhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmhegazy&data=02|01|nathansa%40microsoft.com|0a5d4ea4cefe487a6b0e08d4168bc057|72f988bf86f141af91ab2d7cd011db47|1|0|636158236852616234&sdata=Gf1bAHQIBsY9D6HZbQtY7XamST8TN%2BUo1wfZsfzjGJs%3D&reserved=0 ).
interface A {
name: string;
age: number;
}
interface B extends A {
address: string;
}
type C = A & {address: string};
// Both v1 & v2 appear to have the same members...
var v1: B;
var v2: C;
// ... and assignment in either direction is fine
v1 = v2; // OK
v2 = v1; // OK
// let {name, ...x2} = v1;  // This line is valid (when uncommented)
let {name, ...x3} = v2;  // This line gives the error: Rest types may only be created from object types.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FTypeScript%2Fissues%2F12520&data=02|01|nathansa%40microsoft.com|0a5d4ea4cefe487a6b0e08d4168bc057|72f988bf86f141af91ab2d7cd011db47|1|0|636158236852616234&sdata=JrstfrKUQqryPzc1eYlBfS6unPsbeMGHC3a%2FQ7ZL82E%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAR6Yd0CM42T3JiIj4uFn7DQWqiigFugks5rCR5EgaJpZM4K9Esc&data=02|01|nathansa%40microsoft.com|0a5d4ea4cefe487a6b0e08d4168bc057|72f988bf86f141af91ab2d7cd011db47|1|0|636158236852616234&sdata=MxXhYSVe78x8cC7N5EPACf6a0fqMcI0YF%2FdJclrxKww%3D&reserved=0.

My scenario was in trying to type a tree of React components, whereby (parts of) the model gets passed down, yet some components may also add members for some children (such as event handlers). A simplified/contrived example is below. Without intersection types working, I had to extend an interface each time I wanted to augment the type of the receiving props parameter.
let model = {
    a: "test",
    b: 42,
    c: true
};
type Model = typeof model;

function Comp1(model: Model){
    let clickHandler = (e: Event) => {return true;};
    return <Comp2 onClick={clickHandler} {...model}></Comp2>;
}

function Comp2({...props}: Model & {onClick: Function}){ // <- Gives an error currently
    return

;
}

Note: Subtraction types will be nice too, as often you remove a couple of props from the model then pass down the remainder - which is kind of a pain to describe accurately right now without a lot of forethought (and code).

In cases like these we should just allow it to go through. it is rather artificial that we do not. type parameters should still be disallowed though.


compiling with gcc 7 -> error on bool operator <

when compiling i get
json.hpp:6395:66: error: wrong number of template arguments (1, should be 2)                          return *lhs.m_value.array < *rhs.m_value.array;
and
/usr/include/c++/7/array:94:12: note: provided for ‘template<class _Tp, long unsigned int _Nm> struct std::array’      struct array

Could you provide more information: what do you compile? Are there more error messages with other file locations?

https://github.com/buffos/carnd_projects/tree/master/10.project.mpc
It has few dependencies though.

here is the full output of the compilatio
kostas@kostaslinuxlaptop:~/Code/carnd/CarND-MPC/build$ cmake .. && make -- Configuring done -- Generating done -- Build files have been written to: /home/kostas/Code/carnd/CarND-MPC/build Scanning dependencies of target mpc [ 33%] Building CXX object CMakeFiles/mpc.dir/src/MPC.cpp.o [ 66%] Building CXX object CMakeFiles/mpc.dir/src/main.cpp.o In file included from /home/kostas/Code/carnd/CarND-MPC/src/main.cpp:10:0: /home/kostas/Code/carnd/CarND-MPC/src/json.hpp: In function ‘bool nlohmann::operator<(nlohmann::basic_json<ObjectType, ArrayType, StringType, BooleanType, NumberIntegerType, NumberUnsignedType, NumberFloatType, AllocatorType, JSONSerializer>::const_reference, nlohmann::basic_json<ObjectType, ArrayType, StringType, BooleanType, NumberIntegerType, NumberUnsignedType, NumberFloatType, AllocatorType, JSONSerializer>::const_reference)’: /home/kostas/Code/carnd/CarND-MPC/src/json.hpp:6395:66: error: wrong number of template arguments (1, should be 2)                          return *lhs.m_value.array < *rhs.m_value.array;                                                                   ^~~~~ In file included from /usr/include/c++/7/tuple:39:0,                  from /usr/include/c++/7/mutex:38,                  from /usr/include/uWS/Epoll.h:11,                  from /usr/include/uWS/Backend.h:12,                  from /usr/include/uWS/Networking.h:69,                  from /usr/include/uWS/WebSocketProtocol.h:5,                  from /usr/include/uWS/WebSocket.h:4,                  from /usr/include/uWS/Group.h:4,                  from /usr/include/uWS/Hub.h:4,                  from /usr/include/uWS/uWS.h:4,                  from /home/kostas/Code/carnd/CarND-MPC/src/main.cpp:2: /usr/include/c++/7/array:94:12: note: provided for ‘template<class _Tp, long unsigned int _Nm> struct std::array’      struct array             ^~~~~ CMakeFiles/mpc.dir/build.make:86: recipe for target 'CMakeFiles/mpc.dir/src/main.cpp.o' failed make[2]: *** [CMakeFiles/mpc.dir/src/main.cpp.o] Error 1 CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/mpc.dir/all' failed make[1]: *** [CMakeFiles/mpc.dir/all] Error 2 Makefile:83: recipe for target 'all' failed make: *** [all] Error 2

Could you paste the complete error message? I compiled the test suite of this library with GCC7 without problems.

I just did  above :)

It seems that the compiler tries to parse array as std::array. I can't install all the dependencies right now - can you try to create a smaller example with fewer dependencies?
To rule out a problem with your compiler: can you try to compile the unit tests for nlohmann/json (by just calling cmake/make after cloning nlohmann/json?

I tried  cmake -DCMAKE_C_COMPILER="/usr/bin/gcc-6" -DCMAKE_CXX_COMPILER="/usr/bin/g++-6" .. && make  and it builds fine
So its definitely an issue with the compiler. Probably due to dependencies.

So GCC6 works with your code, but GCC7 does not? This is strange. Then again, can you reproduce the error which fewer dependencies?

I will.

I met the same problem, here's one way to produce it:
a.cc:
#include <string>
using namespace std;

#include "json.hpp"

Compiling it with g++ -c a.cc will produce the error.

I cannot reproduce this issue with

g++-7 (Homebrew GCC 7.1.0) 7.1.0
g++ (GCC) 8.0.0 20170601 (experimental)

I can compile and run the complete test suite from the develop branch.
@whenov What is the OS/version of your compiler, and can you provide the error message?

I'm having the exact same issue when compiling any OpenFrameworks app on Arch Linux since updating gcc to 7.1.1

I tried to help @alberto2000 track this down in IRC earlier. In https://github.com/openframeworks/openFrameworks/blob/master/libs/openFrameworks/utils/ofConstants.h#L435 -- 'using namespace std;' is present and indirectly ahead of the include for json.hpp, which seems to trigger the issue.
@buffos -- your code also has a 'using namespace std;' indirectly before json.hpp is included
@nlohmann -- I did the same as @whenov and had the same error message about template arguments, which goes away if 'using namespace std;' is commented out. The test suite built and ran fine.

@nlohmann
OS: Arch Linux
Compiler: gcc version 7.1.1 20170516 (GCC)
Error message:
json.hpp: In function ‘bool nlohmann::operator<(nlohmann::basic_json<ObjectType, ArrayType, StringType, BooleanType, NumberIntegerType, NumberUnsignedType, NumberFloatType, AllocatorType, JSONSerializer>::const_reference, nlohmann::basic_json<ObjectType, ArrayType, StringType, BooleanType, NumberIntegerType, NumberUnsignedType, NumberFloatType, AllocatorType, JSONSerializer>::const_reference)’:
json.hpp:6057:62: error: wrong number of template arguments (1, should be 2)
                     return *lhs.m_value.array < *rhs.m_value.array;
                                                              ^~~~~
In file included from json.hpp:33:0,
                 from a.cc:4:
/usr/include/c++/7.1.1/array:94:12: note: provided for ‘template<class _Tp, long unsigned int _Nm> struct std::array’
     struct array
            ^~~~~

Ok, now I can also reproduce the error with the following code and GCC-7:
using namespace std;
#include <json.hpp>

int main()
{}

The error is
In file included from std.cpp:2:0:
src/json.hpp: In function 'bool nlohmann::operator<(nlohmann::basic_json<ObjectType, ArrayType, StringType, BooleanType, NumberIntegerType, NumberUnsignedType, NumberFloatType, AllocatorType, JSONSerializer>::const_reference, nlohmann::basic_json<ObjectType, ArrayType, StringType, BooleanType, NumberIntegerType, NumberUnsignedType, NumberFloatType, AllocatorType, JSONSerializer>::const_reference)':
src/json.hpp:6384:62: error: wrong number of template arguments (1, should be 2)
                     return *lhs.m_value.array < *rhs.m_value.array;
                                                              ^~~~~
In file included from src/json.hpp:33:0,
                 from std.cpp:2:
/usr/local/Cellar/gcc/7.1.0/include/c++/7.1.0/array:94:12: note: provided for 'template<class _Tp, long unsigned int _Nm> struct std::array'
     struct array
            ^~~~~
make: *** [std] Error 1

It is very strange that the name array is mistaken as std::array. I wonder if this is a bug in GCC.

Changing the line in json.hpp to read
return (*lhs.m_value.array) < *rhs.m_value.array;

seems to fix the error using that simple test case. It's quite possible this is a GCC bug; I can't understand why .array< should be interpreted as template parameters to array with that . preceding it. Furthermore, clang compiles the snippet without issue in C++11 and in C++14 mode.

Yes, definitely seems like a compiler bug, especially if it worked fine in other GCC7 versions, then it's probably a regression.

@jebrosen Thanks for the fix. I shall implement it. I further try to get a GCC7 working in Travis so such errors can be detected automatically.
As for the bug - it would be great to boil the problem down to a size that is "digestible" by StackOverflow. Any help would be greatly appreciated.

I opened an issue on StackOverflow, see https://stackoverflow.com/questions/44367859/using-stdarray-and-using-array-as-name
It is not sure yet whether this is an issue in the language or the compilers. Nevertheless, adding parentheses fixes the problem, so I close this issue.

This issue seems to have come back with the 3.6.0 release. I guess this was caused by some automatic reformatting: Here's the line that previously had parenthesis
https://github.com/nlohmann/json/blob/release/3.6.0/include/nlohmann/json.hpp#L5731
Also this problem still appears with GCC 8.2.1

Oh, that's a pity! I use GCC 7 and 8 in the CI, but did not catch this issue. Is it just the array comparison?

@nlohmann I haven't tested the commit you linked but adding the parenthesis by hand locally fixes it for me.


Remove @ToBeFixedForInstantExecution from a bunch of tests

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.


Improve LightHouse Score

I've changed several files.Here are the effects.

Before

After

Now,the only thing to improve LightHouse Score left is to set an image of favicon.png.
Fin!

Thanks for the PR. I added a small comment, the rest can be merged after implementing the changes.

Thanks!


Initialize hanami events in hanami projects

We need to think how to use hanami events in hanami projects

I created milestone for this, will close the issue


allow for self signed certs on auth

Auth flow does not work with https and self-signed cert, need to hack it so we can pass verify=False.
One way to make it work is to set env variable before starting the notebook server.
 CURL_CA_BUNDLE="" jupyter lab

Side note: default client for keycloak is now called sd-api - need to fix the notebook example for metadata.

https://github.com/lepture/authlib/issues/239


 This package relies on the iframe name in order to skip the url synch when rendered in modal.
Iframe names are being deprecated as they are unreliable, especially on Mobile, which might not render an iframe at all. It also was always an unadvertised hack added in by 1P developers.
Fix
Use app.getState('context') to figure out whether the app is rendered in a modal
Consuming repo

https://github.com/Shopify/buy-button
https://github.com/Shopify/facebook-marketplace
many more apps: https://github.com/search?q=react-shopify-app-route-propagator&type=Code

@vividviolet I had chatted with @gf3 briefly before about this, but this might be an good opportunity to remove the react-shopify-app-route-propagator package all together and move the implementation into @shopify/app-bridge-react.
What do you think?

Yes, we can take the opportunity to remove this package from quilt. Maybe putting in @shopify/app-bridge-react makes sense. The only thing to note is that we do not support hooks in app-bridge-react yet.
cc @gf3 @iainmcampbell

indeed, however we should 😅

Trish moved route propagator to app bridge react in https://github.com/Shopify/app-bridge/issues/1303


Doubled boot call causes error in destroy

@mikewesthad Here's a PR to fix a double boot call that occurs if the scene is added before the system is booted.
Here's an example of the error. If you load this up and then click the "game" it will throw an error because destroy is called twice and systems is undefined on the second call.
import Phaser from 'phaser';
import PhaserNavMeshPlugin from 'phaser-navmesh/src';

const config = {
  type: Phaser.AUTO,
  width: 800,
  height: 500,
  scale: {
    mode: Phaser.Scale.FIT,
    autoCenter: Phaser.Scale.CENTER_BOTH
  },
  plugins: {
    scene: [
      {
        key: 'PhaserNavMeshPlugin', // Key to store the plugin class under in cache
        plugin: PhaserNavMeshPlugin, // Class that constructs plugins
        mapping: 'navMeshPlugin', // Property mapping to use for the scene, e.g. this.navMeshPlugin
        start: true
      }
    ]
  },
  physics: {
    default: 'arcade',
    arcade: {
      debug: true,
      debugShowBody: true
    }
  }
}

function create(){
  this.input.on('pointerdown', ()=>{
    this.scene.remove('created');
  })
}

const game = new Phaser.Game(config);
game.scene.add('created', {create}, true);

Fixes #29

Good catch - thanks!


Off canvas' sub menus do not have 100% height.

To reproduce: http://jsfiddle.net/c2n46v9t/

Open the left off canvas menu. Notice there are many items, so there is a scroll bar.
Click the first menu item to open the sub menu.
Scroll the off canvas menu downwards and notice that the sub menu does not stretch to cover the parent menu.

We added this to our "known issues" section in our planning board for the next version. A PR would be valuable to the community, otherwise It will be addressed then. You can see and vote on the proposed updates here: https://trello.com/b/QBPKlQqf/foundation-sites


Integration with CI service, e.g. Travis

This should be relatively simple to add once I add the make test target.

Integration will happen after testing will be implemented.


Template fix to show only active builds

On the package details page, it would display both active and inactive builds as there was no filter to only show what was active. This PR attempts to patch the frontend template to address this.
Fixes: #97.

hey @Diaoul, I don't know where you're at with the build but this merged code doesn't appear to be live so the issue it is meant to close is still a problem. should I re-open it?

It's not because 0.2.3 is broken on something else and I had to revert the deployment... I have not time to fix it sadly so it remains "paused".


fix deployment problem for tengine_u8 backend

As mentioned in #166, there is a quantization parameter mismatch problem for the tengine_u8 backend in the deployment stage.
The direct reason is that there is a typo for ONNX ReLU op_type which causes the output quantization parameters of relu cannot be passed to the output quantization parameters of conv in conv+relu fusion pattern.
For example, the following is part of resnet18 computation graph represented with ONNX. And we can see that there is a conv+relu pattern. Because of layer fusion, we will get output quantization parameters for output tensor 550.

After converting to tmfile, we can see that relu operation is erased from graph. In this case, tengine quant_tool_uint8 needs output quantization parameters for tensor 549 but which is missing. So we need to pass quantization parameters of 550 to 549 in MQBench convert_deploy stage.

finally, I test tengine_u8 backend at ImageNet-1k with resnet18. The results are tested in ImageNet-1k full validation sets.

model
mode
top1@quantization_simulation
top1@tengine_u8

resnet18
uint8
69.416
69.400

Approval for this MR. Fell free to squash and merge by yourself!

@Tracin I don't have MR permissions.


When launching code in git-bash, the integrated git-bash terminal won't clear history output properly

VSCode Version: 1.28.1
OS Version: Windows 10 1809, 17763.55

Steps to Reproduce:

launch code in git-bash: code
open integrated terminal(git-bash configured)
make some output in the terminal: ls
try to clean the history output of the opened terminal: hit ctrl + L or clear
The history outputs remain

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

See https://github.com/xtermjs/xterm.js/issues/106#issuecomment-393947437


Wrong SpanRefType mapping in JaegerSpanExporter

I think there is an error in the mapping between the internal trace4cats span model and the Jaeger model.
https://github.com/janstenpickle/trace4cats/blob/82baa78bd7ee1c5e7742d99d4f53477a43bd76f7/modules/jaeger-thrift-exporter/src/main/scala/io/janstenpickle/trace4cats/jaeger/JaegerSpanExporter.scala#L76-L77
Here's the link to an interesting discussion regarding their meaning:
https://github.com/open-telemetry/opentelemetry-specification/issues/65
They both mean "parent" or "ancestor", not a child, but in a bit different way.
The below quote is especially interesting:

Another odd thing about child-of and follows-from is that it's the child span that defines this reference type, even though it talks about parent's dependency on child outcome. If you're a remote server, how do you even know if parent/caller does or does not depend on your outcome? I tend to think of this as the nature of the protocol: producer of a message to Kafka does not respect any response, so the receiver should use follows-from. Sender of HTTP request does expect a response, so the server always uses child-of, even of the sender doesn't care about the outcome - in that case it can internally create a follows-from span first, and then a normal pair of RPC call spans. So it's possible to rationalize this way, but it's still kind of dirty.

I suggest changing it to:
case Link.Parent(_, _) => new SpanRef(SpanRefType.CHILD_OF, traceIdLow, traceIdHigh, spanId)

That is when we add a link Parent(parentTraceId, parentSpanId) we mean that the current span is a child of (parentTraceId, parentSpanId).

Yes, this is confusing, and seems to be open to lots of interpretation. I think it may be better to remove Link.Child for the time being and do the same as open-telemetry

For some reason, CHILD_OF is used as a ref type in the json response of http://localhost:16686/api/traces/ for links to the direct parents in the same trace.
I suggest mapping Link.Parent to FOLLOWS_FROM and use it for linking with indirect/async parents.

I suggest mapping Link.Parent to FOLLOWS_FROM and use it for linking with indirect/async parents.

This is what currently happens for that link type in order to align with the OT implementation. The only difference is the already problematic Link.Child, so I think that should just be removed completely.

But child links are used in the stackdriver exporter.

They are, but as you point out, the Jaeger data model doesn't allow for specifying children on the parent span. So while Stackdriver does support this other systems will either behave in weird ways or drop the link completely.
That said, there isn't a way to have multi-parent spans in datadog or newrelic at all. I'm just not conviced of the utility of being able to specify child spans in the parent span post-hoc, especially as the ability to specify one or more parent is available for a child anyway.

I can do this one.
Do you prefer to leave just case class Link(...) or sealed trait Link with only one case Parent?
Or we still have another option: find all folds on Link and turn them into partial functions, so that if a case is not supported by a tracing backend, we ignore it.

Thanks @catostrophe.I'm struggling to think of a use case for a child link given the open telemetry discussion. While stackdriver supports the concept of a child link, is it something we should support in the API? I'm leaning towards not, given that modifying a parent to add a child link could get complicated. What do you think?
If you think the same, we should probably just go with a single case class Link.

I agree, let's make it case class Link(...). Will do.


Fix reconnect logic for websocket connection errors

Description
This pull request fixes the reconnection logic for the WebSocket client. In case of issues in the protocol upgrade, now the WebSocket client follows the reconnection logic configured on the TcpClient.
Here is a screenshot that shows how the reconnections are done (check the exponential increase of time):

For details about the issue: https://github.com/magicinternet/massivesdk/pull/1369#issuecomment-1924680625

@Dev-vlad After implementing this fix, I reviewed the protocol upgrade specification in RFC 6455. When the protocol upgrade is accepted by the server, it responds with code 101 - SWITCHING_PROTOCOLS. The RFC states:
Any status code other than 101 indicates that the WebSocket handshake
has not completed and that the semantics of HTTP still apply.  The
headers follow the status code.

This means that we can have many different error codes like 300s or 400s. This is why I decided to keep the reconnection logic. In any case, we can abort the reconnection logic if we receive a 403 - FORBIDDEN. This represents the case in which the protocol upgrade is rejected because of an upgrade mismatch.
Wdyt?

Yes, I can confirm that the server will respond with 403 to the Origin validation or any other validation errors.


Extra forward slash when publicOutputDir setting is blank

Description 📖
When publicOutputDir setting is blank, the resulting URLs  have extra forward slash (//) and browser interpretes that as absolute path which is invalid.
Reproduction 🐞
Use the following config/vite.json
{
  "all": {
    "assetsDir": "assets",
    "publicDir": "public",
    "publicOutputDir": "",
    "sourceCodeDir": "app/frontend",
    "watchAdditionalPaths": []
  },
  "development": {
    "autoBuild": true,
    "port": 3036
  },
  "test": {
    "autoBuild": true,
    "port": 3037
  }
}

I did not test setting blank values for assetsDir and publicDir; but I think that they would have the same problem

For a while, the dev server proxy relied on publicDir as a "prefix" to detect requests for the Vite dev server.
Now that Vite has patched bugs related to HMR requests, the proxy can rely on file existence.
I'll consider supporting "publicDir": "", allowing you to have Vite as the only source for frontend assets if that's what you want.

I think the issue here is with publicOutputDir; the documentation does not mention that the value cannot be blank.  However, setting a blank value would generate invalid URLs.

Sorry, typo, publicDir => publicOutputDir.


Honor default pulse ms in opp

Coverage decreased (-0.006%) to 93.131% when pulling 0f8c1a5763538d79c26db4fcf8f07a4d016410fc on honor_default_pulse_ms_in_opp into f055a52a37f8a682120dc4b5ac9af42d84ad69ad on dev.


feat: enable container data relocation

@bowang-666 thanks for review, unfortunate timing as I just readjusted based on the feedback Tony provided here and in https://github.com/Azure/aks-engine/pull/3179#discussion_r423371659.
@xuto2 I've removed all of the struct logic from agentbaker and update aks-engine here to the new version. Would wait to see if you have additional review comments.
Vendor in RP seems to be failing on related toggle issue, working to resolve.

/lgtm


global: release checklist

FIX Adds changes according to release preparation checklist.

Signed-off-by: Paulina Lach<EMAIL_ADDRESS>

As spotted by @remileduc those two lines should contain the module name
https://github.com/inveniosoftware/invenio-logging/blob/master/docs/make.bat#L130-L132
        echo.^> qcollectiongenerator %BUILDDIR%\qthelp\Invenio-Logging.qhcp 	echo.To view the help file: 	echo.^> assistant -collectionFile %BUILDDIR%\qthelp\Invenio-Logging.ghc


Updated default.config.yml

Updated default.config.yml to use more keys for DA settings instead of hard coded paths.

👍
On Jun 6, 2017 11:56 PM, "Ashraf Abed"<EMAIL_ADDRESS>wrote:

Merged #6 https://github.com/debugacademy/drupal-vm/pull/6.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/debugacademy/drupal-vm/pull/6#event-1112937511, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AOQsyXlOp79g3CjiZVKh_iAURk0tk62fks5sBh-FgaJpZM4NS-Va
.


Print OpenSSL version if GOFIPS can't be honored

This PR adds a trace showing the loaded OpenSSL version before panicking in case GOFIPS can't be honored.
It will help debugging OpenSSL configuration issues.

Done in #943


Trouble viewing rasters and PSTHs

I'm new to Neurosift and am trying to view rasters and PSTHs.
I have a table of units here and a table of trials here.  I would like to view raster plots and/or PSTHs of some units aligned to trial events (e.g. "trial_start" or "phase_stimulus_time").
Is this possible?  In the units tab I see an option "Request raster plot", but that doesn't seem to load anything when I click on it.
Thank you!

Source of trouble is the request from https://github.com/flatironinstitute/neurosift/issues/117
Units table is in processing instead of the outer level, but that is unrecognized by the PSTH plugin

@nwatters01 The "request raster plot" option is no longer functional... so I need to remove it.
The links don't work for me -- is this an embargoed dataset?
As Cody says, I think this will be resolved with #117, but I don't think I'll be able to get to that until the beginning of 2024.

The links don't work for me -- is this an embargoed dataset?

It's 000620 - you've been added to it for a while, just make sure to set your API keys

@nwatters01 @CodyCBakerPhD I decided to go ahead and address this before vacation. :)
Starting with your dataset (thanks for giving me temporary access Cody)
https://flatironinstitute.github.io/neurosift/?p=/nwb&url=https://api.dandiarchive.org/api/assets/2fd8e177-ecf6-4d7f-aec4-387da092a4de/download/&dandisetId=000620&dandisetVersion=draft
First select the two items with checkboxes (units and trials table) as shown

Then click on "Open PSTH for selected items" which should appear on the left.
Then you get this

Amazing, thank you so much!  I just tested and it works great!


Validator cannot be override

When I set validator in phone field :
validator: (val) {
if (val == "") {
return "Phone number is required";
} else {
return null;
}
},
The validator won't validate. Only the onChange default validator message "Invalid Mobile Number" works when you type something on the field. What I want is that this field should validate if empty and also can use this field that allow empty field.  Is any one here have the solution?

Same problem.

same problem

same problem.

please fix :(


Add populate-cache-effect

Motivation
We want to push some paths to either the cachix or attic cache, additionaly to the cache configured for herculesCI. We discussed it recently on mlabs slack. If you guys would be interested here's a module doing that to be used like below:
populate-cache-effect = {
      enable = true;
      caches = {
        mlabs-attic = {
          type = "attic";
          secretName = "cardano-nix-attic-token";
          branches = ["master"];
          packages = [test-drv];
        };
        mlabs-cachix = {
          type = "cachix";
          secretName = "karol-cachix-token";
          branches = ["master" "push-to-attic"];
          packages = [test-drv];
        };
      };
    };

it's a flake-parts module producing effects under herculesCI.onPush.default.outputs.effects.populate-cache-effect option.
Questions
It works. But I don't understand the structure of this repository, so I'd like to ask first how to incorporate that into the codebase:

where/how to export this
if it's fine the way it is with default attic-client-pkg cachix-pkg

Maintainer checklist

[ ] Documentation (function reference docs, setup guide, option reference docs)
[ ] Has tests (VM test, free account, and/or test instructions)
[ ] Is the corresponding module up to date?

I don't have access to this repository, so can't push to a branch at mlabs-haskell/hercules-ci-effects.

Closing in favor of https://github.com/hercules-ci/hercules-ci-effects/pull/165


I'm using psych engine 0.5.2h btw(if you ask me.i just wanted to stay with blammed lights)

What is your question?
Hi.I tried to make a modchart and I added zoom for the HUD but it doesn't come back to normal when I started hitting the arrows
How do I fix this?

Ok NVM I figured it out


Change how sonar resources are loaded

The current order is:

Resources in core
Scoped packages (@sonarwhal/XXX)
Prefixed packages (sonar-resourceType-XXX)

The previous way of loading resources was weak and is better to rely
on require when dealing with external resources.
Some improvements of the current code over the previous:

We load only the resources that we need instead of all, and on demand.
sonar.create() is now sync and should load faster.
Validation of rules is done now in sonar (when loading them individually
and not the cli. This fixes a previously unkown issue on rule-runner
where the schema of rules wasn't validated (it showed up in ssllabs.
Remove all code related to plugins until we know how they look like.
Refactor where the code to generate a valid .sonarrc is.
Remove sonar.create() in favor of new Sonar().
Clean up several tests and added @types/sinon.
Refactor ui to cli and move all generators there.

Fix #234

Take 2, let's see if this one goes to the right place.
Can you take a look to double check the code is the same as the original one?

This looks the same as what I had seen in your last PR. Should be fine to merge. I'm not sure how this will affect #296 since your commit is showing up there too.

@sarvaje can probably rebase once this is merged into master and hopefully things will be back to normal.


bhnt-78: add missing hacks

I'm updating the missing hacks and also testing the github workflow action to validate the URLs.

Hey @ligi and @MarlonSchultz ,
I added a cool new github feature to our workflow and wanted you to check it out.
We can add a check to PRs that validate the URLs in any changed files.
For an example of the output see this: https://github.com/berlin-hack-and-tell/berlinhackandtell.rocks/pull/285/checks?check_run_id=677696224#step:5:56

Nice - love it!
Will also try to watch the talk you linked - seen some of satellite - but missed this one


Rolling Challenge fixes

Small improvements in the Rolling challenge

First thing. I think the warning about the beta changing how it works can go from the start (I don't seem to be able to make that a comment on the lines!)


Tailwind config added

https://stackoverflow.com/questions/56683681/this-branch-has-conflicts-that-must-be-resolved-but-its-already-merged


Point trunk c++filt at trunk

See #1942 for why...as compilers start to implement <=> we'll need to use the latest demangler.

I think for this we need to build binutils from trunk as well instead of using the sources from FTP https://github.com/compiler-explorer/gcc-builder/blob/master/build/build.sh#L165

partouf@partouf-VB3:~/Documents/staging/bin$ ./c++filt ZNK3FoossERKS
Foo::operator<=>(Foo const&) const
With git clone --depth=1 https://sourceware.org/git/binutils-gdb.git
and basically the gcc-builder's build.sh

@apmorton has committed changes to build binutils trunk when gcc trunk builds. So when that is available we might be able to use that c++filt.
I was wondering however how we're going to handle the situation when the trunk fails to build or produces a bad build.

I think the plan is to only use trunk c++filt for trunk compilers, so it should be a relative non issue.
Presumably by the time any stable compiler supports the spaceship operator there should be a new stable release of binutils to match.
For completeness sake:
If trunk fails to build nothing bad happens - the site just continues to use the last successful trunk build.
If trunk produces a botched build (for example if all binaries segfault or depend on a missing shared library) - the botched build will get installed and blow things up, but reverting to the previous nightly build is as simple as changing a symbolic link.

Makes sense, thanks.
So I think all there's left to do is to check the current snapshot and change the property file to reflect trunk c++filt for gccsnapshot and clangtrunk

Works on the admin node;
May/05 16:46 admin-node~ $ /opt/compiler-explorer/gcc-snapshot/bin/c++filt _ZNK3FoossERKS_ Foo::operator<=>(Foo const&) const


Watcher stops working when used in cached object

Vue version
3.4.21
Link to minimal reproduction
https://play.vuejs.org/#eNqFVU1v20YQ/StjXiQjMlmgPakU0UQ1kBRoG8QBcghzoMkhzZhaEvshW1D13/t2l0szip1AB3F3ZufzzZtj9HoY4r3haB2lqpTtoEmxNkOWi3Y39FLTkSTXdKJa9jtaQHUxibb9bhjv48QerKXF77nIRZLQ36xU0XAuyl4oTTvV0MbaWi7ectf19KmXXXWxuBzV3/1JRnFFhaJ7PpDuScu2aViS4AcqYb0XLDSVkgvd9njk7bbVaPaXS3iujSitNDx+Y5rlJR1zQVCM90VnmF69guIpF2niM0auOGjeDV2h2Z2I0lYMRtP+atdX3G3yCPHnESUQQ3hrtIaT/VVbQ3TRVhD9UXZteY/jk+s8yj6OSeCUJv6ZN6GGwhrgTnF2a5oQMFcXiAsyr+VKvN75Uk5RrFEhHJzbMaIhuyL3SxPbPHdzo3lQ6+nCdO4fX12bbe8K0TBpfkQJUS7/j5TTBNKZnk2KfODnop+aSJPRJ4K5fhy41Fy9EE8QU9cKVui3ERplAwx2hS7vqCi1KToSZneL6772es96eu1UX/DzyVqDBaX7QdFDL+9b0ZARPPrvDisSvSYzVIAZRN/Ec+4vTWawiVaRVgBl3TbxV9ULzJQDXh5Z9LYdy38Hi02VR2sPSSsrMAsPf7k7LQ2vwj2iLO+fuf+qHu1dHr2XrFjuOY8mmS5kw9qLr2/+QUNmQgDZdND+gfADq74zbrqc2hsjKoQ903PRvnPjj+J8VNePmoUKSdlArebJ6ecR6MAC+KXUn8L9Nf7NvcNcooqBSs5JiToAzg4YzMwJ6sEhZE5RGPAgBancaFPXQRyjZUp7lvIMMkgLhQ1VXKPX7+0pdTGOY7cGWCSytayRLS3LhJfHoKJW1LFotI1iY3nMuRx1QW4OdVT3Mjyg0g0P3hVVZVFeSFkccuFSWYKyNpmPKx4frGg5fjnZPD7leS0ejLqblGywjlpfZDmAuGr3YTSGbORrRXcthkMeaHk8Tlmd/BxcTlNln0jOoBKigBKEuPPz4W1/NyCofawVOjt1Tx8Gpg9cryyLr55vJtppx68uSg57RW0LjIgvBCr81gc9L8vaWk197z5/yZwZp2vxZRzXuOzsrf/yLzzHWH3g0bXPu7LtC61FrMp0OhcdYyVZ8fossP9AKh5RVUDB1q4uBppgILeMYwswbawn1JybCjluLSV4b26h1bR0h3HBEYLSRgqvAaduoMJb79vu0tE/gdTcYg79c2v0qV7Lz18sioLaiITZrh0tf4dtgNqxJ8/q63E9mxa0a8JxKP+4nzdOGvs7n8YqKFbMw4xnHMLP8/OtWfkyUIsmIQf3vQlmpkDm7t3h5ByeFfIUnf4H5UoaSg==
Steps to reproduce

Change text in input
Click button to trigger bug
Change text in input

What is expected?
Demo stores history of typed text in array, watcher monitors that array and updates lines counter.
Expected lines counter to match number of items in array.
What is actually happening?
Watcher unexpectedly stops working
System Info
System:
    OS: macOS 14.3.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 93.69 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.5.0 - /usr/local/bin/node
    npm: 9.8.0 - /usr/local/bin/npm
    pnpm: 8.15.4 - /usr/local/bin/pnpm
    bun: 1.0.25 - ~/.bun/bin/bun

Any additional comments?
How bug is triggered.
Sample has composable useStuff() that:

Creates variable for messages history: Ref<string[]>
Creates variable for number of lines: Ref<number>
Watches history using watch(), updates number of lines.

Very basic composable, nothing special about it. That composable is stored in cache to reuse it when needed without losing old data.
Change text in input, component adds it to history from composable, watcher is triggered and it updates number of lines.
When initially created, it works as expected. However, when retrieved from cache, watcher no longer works.
Bug is triggered by re-creating component by changing key. On initial render it creates new composable, on second render it uses cached composable.

This is not a bug. watchers that were created during a component's setup are removed when that component unmounts. Otherwise, you would end up with memory leaks.
If you intentionally want to keep a watch running beyond a component's lifecycle, but still create it during its setup, you can use a dedicated effectScope