"Add using" quick fix does not appear in error squiggle toolsip

Issue Description
According to: https://github.com/OmniSharp/omnisharp-vscode/issues/1117 there should be a "Add using" quick fix.
Steps to Reproduce
dotnet new console -n test
cd test
code .

Choose the Program.cs file and write Socket socket; in the Main method.
Expected Behavior
A quick fix should be available to add the missing using System.Net.Sockets directive.
Actual Behavior

Logs
OmniSharp log

Starting OmniSharp server at 25.8.2019 21.41.34
    Target: /tmp/test
OmniSharp server started.
Path: /home/kristian/.vscode-oss/extensions/ms-vscode.csharp-1.21.1/.omnisharp/1.34.2/run
PID: 14417
    Starting OmniSharp on arch 0.0 (x64)

    DotNetPath set to dotnet

    Located 1 MSBuild instance(s)
        1: StandAlone 16.0 - "/home/kristian/.vscode-oss/extensions/ms-vscode.csharp-1.21.1/.omnisharp/1.34.2/omnisharp/.msbuild/Current/Bin"

    MSBUILD_EXE_PATH environment variable set to '/home/kristian/.vscode-oss/extensions/ms-vscode.csharp-1.21.1/.omnisharp/1.34.2/omnisharp/.msbuild/Current/Bin/MSBuild.dll'

    Registered MSBuild instance: StandAlone 16.0 - "/home/kristian/.vscode-oss/extensions/ms-vscode.csharp-1.21.1/.omnisharp/1.34.2/omnisharp/.msbuild/Current/Bin"
        MSBuildExtensionsPath = /home/kristian/.vscode-oss/extensions/ms-vscode.csharp-1.21.1/.omnisharp/1.34.2/omnisharp/.msbuild
        BypassFrameworkInstallChecks = true
        CscToolPath = /home/kristian/.vscode-oss/extensions/ms-vscode.csharp-1.21.1/.omnisharp/1.34.2/omnisharp/.msbuild/Current/Bin/Roslyn
        CscToolExe = csc.exe
        MSBuildToolsPath = /home/kristian/.vscode-oss/extensions/ms-vscode.csharp-1.21.1/.omnisharp/1.34.2/omnisharp/.msbuild/Current/Bin

    Detecting Cake files in '/tmp/test'.

    Could not find any Cake files

    No solution files found in '/tmp/test'

    Queue project update for '/tmp/test/test.csproj'

    Detecting CSX files in '/tmp/test'.

    Could not find any CSX files

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpFormattingWorkspaceOptionsProvider, Order: 0

    Loading project: /tmp/test/test.csproj

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.RenameWorkspaceOptionsProvider, Order: 100

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.EditorConfigWorkspaceOptionsProvider, Order: 200

    Configuration finished.

    Omnisharp server running using Stdio at location '/tmp/test' on host 14301.

    Successfully loaded project file '/tmp/test/test.csproj'.

    Adding project '/tmp/test/test.csproj'

    Update project: test

    Solution initialized -> queue all documents for code analysis. Initial document count: 3.

C# log
Not relevant
Environment information
VSCode version: 1.37.1
C# Extension: 1.21.1
Mono Information
        OmniSharp using built-in mono
Dotnet Information
.NET Core SDK (reflecting any global.json):
 Version:   2.2.108
 Commit:    33ed5b90ce
Runtime Environment:
OS Name:     arch
OS Version:
OS Platform: Linux
RID:         arch-x64
Base Path:   /opt/dotnet/sdk/2.2.108/
Host (useful for support):
Version: 2.2.6
Commit:  7dac9b1b51
.NET Core SDKs installed:
2.2.108 [/opt/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.NETCore.App 2.2.6 [/opt/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

Visual Studio Code Extensions

Extension
Author
Version

csharp
ms-vscode
1.21.1

@klausenbusk Can you try putting the caret on the line with the error and pressing "ctrl-."? I think this is a presentation issue (we show up in the lightbulb but not the error tooltip)

It works, thanks! It isn't very intuitive though.

Adding some screenshots for clarity. The tooltip shows no quick fix:

But there is one with the lightbulb:

Cannot reproduce this with the current release.


Added shebang so it's executable

Otherwise I see the following:
$ roslaunch depthai_examples stereo_inertial_node.launch enableMarkerPublish:=true
process[rosout-1]: started with pid [10394]
started core service [/rosout]
process[oak_state_publisher-2]: started with pid [10402]
process[stereo_inertial_publisher-3]: started with pid [10403]
process[nodelet_manager-4]: started with pid [10404]
process[depth_image_convertion_nodelet-5]: started with pid [10405]
process[depth_image_to_rgb_pointcloud-6]: started with pid [10412]
RLException: Unable to launch [markerPublisher-7].
If it is a script, you may be missing a '#!' declaration at the top.

If it is a script, you may be missing a '#!' declaration at the top.
The traceback for the exception was written to the log file

Thanks for the PR!


Spec and TestDescriptor modifications

Is it possible to change the io.kotlintest.Spec class to use canonicalName instead of simpleName as default? I'm talking about the Class<out Spec>.displayName() extension. If there is no issue with that breaking something, I'll gladly submit a merge request.
Also, can source class be included in TestDescriptor created in method fun createTestCaseDescriptor(description: Description, type: TestType): TestDescriptor from class JUnitTestRunnerListener. TestDescriptor from this method doesn't have set source which I need.
Can I submit these changes or are there any issues I'm not aware of? Thanks.

I'm not sure about changing the display name, it's used by gradle and other things.
As for the source class, yes I think it could be included, I don't see why not.

So can I add another method that will return the canonicalName? I really need it in my use case.

Absolutely.


Better rule validation

Closed via https://github.com/rancher/opni/pull/952 . We can revisit adding more prometheus validation to the cortex admin APIs in the future if this becomes an Issue.


perf: cache storage and calldata

From the preliminary audit:

the processFailedWithdrawal() function reads FailedWithdrawalRecord values from storage multiple times, consider using a local variable instead.
the processFailedWithdrawalsFromPointer() function reads numberOfFailedWithdrawals value from storage multiple times, consider using a local variable instead.
the processFailedWithdrawalsFromPointer() function reads failedWithdrawalsPointer value from storage multiple times, consider using a local variable instead.
the processFailedWithdrawalsFromPointer() function reads FailedWithdrawalRecord values from storage multiple times, consider reading it into memory once instead.
the executeSystemWithdrawals() function reads _addresses[i] from calldata multiple times, it would be cheaper to store it in a local variable.
the executeSystemWithdrawals() function reads numberOfFailedWithdrawals value from storage multiple times, consider using a local variable instead.

Pedantic comment, is cachedFailedWithdrawalRecord variable name the common idiomatic way for this pattern?

I honestly have no idea. I'm not very happy with the name myself... 😅

Closing for now


[Enhancement] Metadata typing

Health Connect docs indicate for ExerciseSessionRecords, metadata field is @NonNull but we type metadata to optional for every record (code):
export interface BaseRecord {
  metadata?: Metadata;
}

Do we do this because some record types don't include metadata? Is there a way we can correct it?

Because I am using the base recording both for inserting and result data it is optional by default. When you are trying to insert a record metadata is optional but after the data insertion the metadata field will be populated. I need to use a separate base interface for results and inserts.
You can fix it and open a pull request if you want have some time.


Make build title link to the build itself

Currently, to view a particular build from the pipeline view, you have to find the corresponding job in the build list. To make things more convenient, make the build title link to the build itself, just as each build is in the build list.
Here is an example how it looks like:

Oh, I like this, and you included a screenshot too -- excellent!
Need to do some manual testing to cover different browsers and screen resolutions (might be a little while before there's time) but if everything looks good, it'll get merged in.

@martinmine  Thank you for the contribution!  I was just able to loop back to test, and it looks good to me, so merging this and it'll be in the next release.


Enforce Activity params to op field override isolation by type

There are a couple corner cases which need to be made explicit in terms of type checking and documentation.

When multiple driver type are active in an activity, and they have multiple possible overrides, the config model for the activity may allow activity params to leak to op field when there is a common name between to different drivers. This should be gated against the config model of the given driver for each op template.
When there are multiple drivers active which may have the same param names, then there is a naming collision. In this case, the parameters may need to have a driver name qualifier. This should be supported as a general mechanism, but required to be used in these cases. Simply using a driver prefix should be sufficient, as in cqld4.consistency_level.

Please check if this is still a valid issue.

I think that the proper approach to this is to assure that NBCLIScenarioPreprocessor is properly handling the scope of the params:
                // consume each of the parameters from the steps to produce a composited command
                // order is primarily based on the step template, then on user-provided parameters
                for (SCNamedParam cmdarg : parsedStep.values()) {

                    // allow user provided parameter values to override those in the template,
                    // if the assignment operator used in the template allows for it
                    if (usersCopy.containsKey(cmdarg.getName())) {
		        cmdarg = cmdarg.override(usersCopy.remove(cmdarg.getName()));
                    }

                    buildingCmd.put(cmdarg.getName(), cmdarg.toString());
                }

I think that the Advisor could report on  user provided parameter values that are in the command stream, but are unused by the template.

OpField in the template along the flat map of CmdParams are two separate sets and need to be de-conflicted when multiple adapters are used. Use set intersection on all parameters of both types. Results can show errors.

In this case is it possible that a block parameter along with a driver parameter should take precedence? That seems like a reasonable approach because for this to happen the other driver must be specified in the yaml adjacent to the driver....

When this is the case then TEMPLATEs should be used to take special command parameters in to set the parameters in the block or ops. This approach is already in use like this:
  rampup:
    params:
      cl: <<write_cl:LOCAL_QUORUM>>
      instrument: TEMPLATE(instrument_writes,TEMPLATE(instrument,false))
      idempotent: true
...
  main_read:
    params:
      ratio: <<read_ratio:1>>
      cl: <<read_cl:LOCAL_QUORUM>>
      instrument: TEMPLATE(instrument_reads,TEMPLATE(instrument,false))

Regarding the case where different adapters use the same parameters, it's true that every adapter uses the BaseAdapter parameters. Detecting possible conflicts between such models is a more complex situation and will require looking at the new labeling while comparing between adapters when more than one is included.

This clearly how the parameters sections work and get aggregated together.
A much better approach to disaggregation of this is to:

Always specify all of the driver adapters parameters.
Block using TEMPLATE overrides as adapter config model / parameter values.

Always specify all of the driver adapters parameters. (Convention)
Can you show examples of this for clarity?

Block using TEMPLATE overrides as adapter config model / parameter values. (Add a Strict mode)
For this, there have been specific cases in the past where it created frustration for users, when the parameters would logically and coherently serve double duty. For example, in specifying K for metrics labeling and validator config.
I think there are still cases where we want it to work like this.

As a separate item, I'm going to document the parameter precedence rules that I am aware of, since it is important to the core issue.

TEMPLATE variables are applied to the raw text of the workload template. (This can be format agnostic)
Standard activity params are allocated to the base activity configuration.
Op template fields which are defined on the op directly take precedence in the op.
Op template fields which are defined in the block are used as fallback values. (params)
Op template fields which are defined in the doc are used as fallback values. (params)
Specifically tagged activity params which are allowed to stand-in for op template field values, and these are used as fallback values when none of the above are present.
Op template fields may have values imposed by the op mapper which are used when none are provided above.

Of these op template fields, some are standard across all adapters, and these are taken from the op template before the adapter-specific mapper logic gets to see them. (Implemented in BaseOpDispenser in the super ctor, and in peripheral op wrappers, coming soon in a PR)

Always specify all of the driver adapters parameters. (Convention)

Can you show examples of this for clarity?

Everything that the adapter needs is available via 2.-7. and TEMPLATE variables are used as now, but with a warning.

Block using TEMPLATE overrides as adapter config model / parameter values. (Add a Strict mode)

This would be an explicit mode that would prevent TEMPLATE variables from use by 2-7 while still modifying the workload content.

That sounds good, as long as it is a "strict" setting only and not the default. There are test cases which people use now which we had to enable by rolling back the strict mode. (It was originally the default)


The {{.ID}} formatting string is missing from the table of formatting options

The docker node ps --format " {{.ID}}" is valid but not part of the documentation
File: engine/reference/commandline/node_ps.md, CC @johndmulhausen
Signed-off-by: Dan Finneran<EMAIL_ADDRESS>

Thanks, @thebsdbox.
@thaJeztah , should we add .ID to the table under "Formatting" here: https://docs.docker.com/engine/reference/commandline/node_ps/#formatting

Placeholder | Description
.ID                  | Container ID

If you want to have the unique identifier for the container than this is pretty much a requirement.

Thanks, @thebsdbox. Some of these reference docs are auto-generated from other repos so we just need to get the update to the right channels.

Yes, looks like that's missing. The easiest way to get a list of available fields is to output as JSON;
docker node ps --format '{{json .}}' | jq .
{
  "CurrentState": "Running 20 hours ago",
  "DesiredState": "Running",
  "Error": "",
  "ID": "qxf9cwioii26",
  "Image": "debian:stretch-slim",
  "Name": "tmpfstest.1",
  "Node": "linuxkit-025000000001",
  "Ports": ""
}
{
  "CurrentState": "Running 20 hours ago",
  "DesiredState": "Running",
  "Error": "",
  "ID": "jhz1t968jk0m",
  "Image": "nginx:alpine",
  "Name": "mystack_web.1",
  "Node": "linuxkit-025000000001",
  "Ports": ""
}

@thebsdbox the Markdown file that's used to generate that part of the docs is in the docker/cli repository: https://github.com/docker/cli/blob/master/docs/reference/commandline/node_ps.md
Are you interested in opening a PR to fix?

Sure thing @thajeztah, I'll do it on Monday when I get home.

Thanks!

Closing this ticket due to its age, and the impending refactor. If you think this is in error, feel free to reopen. Thanks!

Opened https://github.com/docker/cli/pull/1598 to fix


NestJS adapter

Is your feature request related to a problem? Please describe.
An adaper for Nest will let you use tinyhttp inside of Nest instead of Express.
Describe the solution you'd like
A Nest.js adapter package, something like @tinyhttp/nest-adapter
Additional context

NestJS platform-express
nestjs-platform-polka

Hey @talentlessguy I see this issue is opened for quite some time.
I would like to see tinyhttp integrated with NestJS; do you mind if I take a closer look at this if it is not already implemented / worked on?
Also, I am wondering how would one test the underlying implementation of the mentioned adapter?
Should a dummy application be made (or perhaps taken from NestJS samples) or some sort of tests should be written to cover this implementation?
Do you have any guidelines / preferences about this?

@ognjenjevremovic you could either create the separate repo with your own rights and else, or create a pull request
to test the implementation you can create an example in examples folder and of course write a bunch of unit tests

if anyone wants to work on that, I'll create a new repo for NestJS

Hey, I'd love to give it a shot, but I'm kinda new to open source and was hoping for some guidance on how to do it?

@KaviiSuri I'll create a new repo in the org and will assign you as a contributor
does this sound good for you?

Yeah, sounds good!!
Also, I'm new to tinyhttp and beginner with nestjs, so could you give me some resources to get started too?

@KaviiSuri there's tinyhttp documentation website
regarding Nest, it's the same, I mean there is also docs

Okay, thanks, I'll get to it

Hey, I'm going through the docs and code samples you refrenced
As of now, it seems like I need to implement the AbstractHTTPAdapter interface along with creating a ITinyHTTPNestApplication interface that extends INestApplication
Is that it? Is there something I've missed?

@KaviiSuri no idea, I haven't ever used Nest :/

Hey man, I'm not home this week, I'll start working the adapter the coming week. Just wanted to keep you in the loop.

Has there been any progress on the NestJS adapter @KaviiSuri? I am unable find the repo, @talentlessguy was it deleted or made private?

Hey @talentlessguy even I couldn't see the repo so I thought I shouldn't continue..
Anyway, i have enough time to contribute now, could you just create one so I could get started?

@KaviiSuri made the package public https://github.com/tinyhttp/nest

Thanks, will get started on this asap.
I may need help on testing it though, I'll contact when I get to it.

Hey @talentlessguy , I started implementing the adapter and I need a little help.
How can I start tinyhttp with https?
I tried doing it with the standard https package from node but it doesn't respond with anything.
I was unable to find it in the docs

Why do you want to do that?

@KaviiSuri HTTPS doesn't work in tests I think, it's a GitHub Actions issue

@talentlessguy can i work on it

@rubiin yes

I have a simple workable solution ready. Maybe you can publish the package under @tinyhttp/nestjs-platform-tinyhttp after i submit my pr

@rubiin  please do a PR to this repo


Icons for folders & files

In 0.4.6

In which commit is this done? I'm interested to see how you did this.

https://github.com/bazaarlabs/gitdocs/commit/96154463c93a92d0f22a426eef2e3e6d237c032b is most of it

Ah sorry, I thought this was about having emblems on the files in the file manager :)

Oh, that'd be cool, this feature was a lot less exciting, sorry :)


idea: change aw .connect api

any-wallet thinks of ENABLING and CONNECTING wallets as 2 separate things.

shall we move .connect logic into any-wallet
should .connect take different args than enable?

arg 1: wallet id (optional, defaults to only enabled wallet if none)
arg 2: init params (optional, defaults to init params set in enable or true)

ideas:
enable
enableWallet('inkey');
enableWallet(WALLET_ID.Pera);
enableWallet(WALLET_ID.Mnemonic, 'twenty five words ...');

connect
let accts = await algonaut.connect('inkey', {
  src: 'localhost:5200'
});

? should .connect also enable the wallet if its not enabled? what enable really does it sets init params IF connect is called w/out a 2nd init params arg. so... there should only be 1 method for ease for devs and better overall api

did most of this work here:
https://github.com/thencc/any-wallet/pull/25
left TODO... update algjs to use the latest aw + remove the .connect() api complexity in algjs

this happened.
https://github.com/thencc/algonautjs/commit/b56d59225a92f5662a29a4a9a81824ef28794319


[NeuviemeArt] Broken

The url now redirects to a different url.
http://rss-bridge.org/bridge01/?action=display&bridge=NeuviemeArt&format=Html
@ORelio

Thanks for reporting this. 9emeart.fr has been bought by bubblebd.com so 9emeart.fr no longer exists.
A different bridge could be made for bubblebd.com if anyone want one, altough wordpress bridge might work.
I'd suggest to remove the NeuviemeArt bridge.


Simplifies and improves exposure control, more testing needed

I have had some issues with the auto exposure functionality with the DFM 25GX236-ML board camera. The exposure time seems to be set to 10% of what is the maximal, so it is 4 ms when it could be 40 ms for a framerate of 25 Hz. As a result gain is much higher that it needed be, and I get flickering in the video from the fluorescent light in my office.
Indeed there seems that there is a factor 10 error in a constant when determining the maximal exposure time with aravis. Yet fixing this alone did not solve the problem. I found the code a bit cumbersome to understand, so I spent some hours rewriting the exposure control parts.
The deviation from the reference brightness is now called offset and is a floating point number with value (y - r) / r where y is the measured brightness and r is the reference. It is (normally) in the range -1.0 to 1.0 where positive is too bright and negative is to dark.
If the offset is above a threshold the brightness will be reduced, either by reducing the gain with (K_g * offset),  or if the gain is at min, reduce the exposure time with (K_e * offset).
If the offset is below a threshold the brightness will be increased, either by increasing the exposure time with -(K_e * offset),  or if the exposure time is at max, increase the gain with -(K_g * offset).
If the offset is withing the acceptable range it will be tried to reduce gain and increase exposure time with K_ge and K_eg respectively.
I done some simple testing of this solution, and it seems quite responsive. The following graph shows the first test, where I turned off lights in the office, covered the camera several times with my hand and jacked, and the turned on the lights in the office again. Here offset is in %, and exposure is in milliseconds for scale.

I also tested the adjustment by setting the gain high and exposure time low, and as can be seen it swings in rather fast.

Notice that this code is not complete and production ready, it is the results of a few hours of coding and testing. The constants K_e, K_g, K_ge and K_eg needs tuning to specific cameras for instance. I would very much like to have your feedback (pun intended) on it.

Hello Gregerts
thank you for your pull request, we are currently looking into it.
The factor 10 issue at
self->default_exposure_values.max = 1000000 / (self->framerate_numerator / self->framerate_denominator);
is not as easy to handle. The "1000000" depends on the unit the used camera uses for exposure. USB cameras must not necessarily use 1000000, but can use 100000. The current auto exposure algorithm is used for all cameras and here you found a problem how to get the unit of a property.
Stefan

Hi Stefan,
It may have been an error to submit it as a pull request, as it is not general for all cameras and thoroughly tested. My main intention was that you would have a look at it and provide feedback, or use parts of it as you like.
We in SINTEF ICT will use the mentioned camera in a rescue robot demo in a few weeks time, and needed to fix the auto exposure quickly.
I look forward to you comments.
-Kristoffer

Hi Kristoffer,
Sorry for the late reply.
Your solution is definitely quicker and a smoother approach.
However the current gst-0.10 solution does not consider the possibility that different cameras have different exposure units. This is something that is done in the upcoming release for gstreamer-1.0.
You can find an older preview here:
https://github.com/TheImagingSource/tiscamera/tree/beta-release
Since renaming, etc. already took place a direct merge will not be possible.
Would you be OK with me taking the patch and integrating it into the upcoming release and adding a CONTRIBUTERS file mentioning your work?
-Edgar

Hi Edgar,
Feel free to use the patch for the coming gstreamer-1.0 version. I am keen to start using 1.0 for our robot project as soon as possible.
One thing, we tested the robot in the field yesterday and it was very sunny and bright light conditions. When the brightness reached a certain level the patched autoexposure started to oscillate quite rapidly. I am now looking into whether this is an overflow in the brightness measurement or something about the control algorithm. Just so that you know.
-Kristoffer

Hi Kristoffer,
Thank you for your permission. I can not yet say when the official release will be done, so it will probably still take a few months.
If we can help you with your brightness problem, please let me know.
I am unable to produce an oscillation.
Does changing the brightness-reference help?
-Edgar

Hi Kristoffer,
I am very sorry for the long period you had to wait.
I used your patches to rework the algorithms in the gstreamer-1.0 autoexposure module which is now online.
The changes occured in commit<PHONE_NUMBER>e4881078b5ad66a6e1cabc8927fd59 if you want to take a look. I also added you to the contributions.txt.
Unless you have any objections I would consider this pull request settled.
Cheers,
Edgar

Hi Edgar,
Real-world testing of the algorithm with our rescue robot has resulted in some oscillations in very bright conditions. Have you tested this branch properly in different conditions?
Cheers,
Kristoffer

Hi Kristoffer
I must admit, we did not test all cameras with the new sources under all conditions. However, if the image is very bright, then very small exposure times are in use. That means, very small register values in the sensor, so a change of one bit has a bigger effect, than on long exposure times.
Stefan


Add pandas as dependency

@smilesun I have included pandas to the pyproject.toml and requirements.txt.
However, I'm unsure on how to update the poetry.lock. Would you might do this?

@smilesun
I do also use a pandas dataframe for the plotting. And, as the plots are done by seaborn, it seams to be not that easy to replace pandas with some other package.

@smilesun I do also use a pandas dataframe for the plotting. And, as the plots are done by seaborn, it seams to be not that easy to replace pandas with some other package.

ok,  since pandas exsit 10 years ago and still in use today, looks to be stable enough and no problem for us to integrate.


Support request: tf2.0 KFAC optimizer

Anyone can implement KFAC optimitzer with tf2.0 api please

TF 2.0 is unlikely to happen as this repository is no longer supported. I recommend stable-baselines.


Fixed spelling of names

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Docs

What is the current behavior? (You can also link to an open issue here)

JavaScript and Node.js are spelled wrong.

What is the new behavior (if this is a feature change)?

javascript → JavaScript
nodejs → Node.js

Other information:

Can you please rebase this on top of develop branch? Thanks! If not let me know and I'll pull in your commit by hand.

@askmike Should be okay now?! 👍

Yep, great thanks!


Allow Regex for ignoreAnnotated on UnusedPrivateMember

Expected Behavior of the rule
Instead of a fixed string, using a regex would be nice. E.g.
  UnusedPrivateMember:
    ignoreAnnotated: ['\w*Previews?']

Context
The docs for usage with Jetpack Compose state that one should set ignoreAnnotated to ['Preview'] to have detekt ignore composable previews. Jetpack Compose allows you to create custom annotation classes to combine multiple @Preview annotations, but then each multipreview annotation class needs to be added to the ignored list. A regex would allow one to cover all of their various preview annotations.

but then each multipreview annotation class needs to be added to the ignored list

I would actually argue that having all the annotations listed will make the config more explicit and less error prone.

Fair enough! I'll close this issue for now unless I can come up with a more compelling reason than "it's slightly more convenient"


Minor refactor of update shadow

UpdateShadow now uses the shadow term constants from downstream. This works towards making it easier to remove the hard shadow term in HDRP.

Looks good!

Thanks!


How to implement a custom dataset with Fairseq?

Hi, I recently want to implement an image caption model with Fairseq, but I am comfused about how to prepare a custom dataset with Fairseq. I have defined a simple seq2seq model according to the official tutorial ,
the code of seq2seq model shows as follows:
@register_model_architecture('crnn', 'image_caption')
def base_architecture(args):
    pass

@register_model('crnn')
class CRNNModel(FairseqModel):
    def __init__(self, encoder, decoder):
        super().__init__(encoder, decoder)

    @staticmethod
    def add_args(parser):
        """Add model-specific arguments to the parser."""
        pass

    @classmethod
    def build_model(cls, args, task):
        """Build a new model instance."""
        # make sure that all args are properly defaulted (in case there are any new ones)
        base_architecture(args)

        encoder = CRNNEncoder(
            args,
            in_size=DIM_FEATURE,
            cnn_cnls=DIM_HIDDENS,
            cnn_depth=BCONV_DEPTH,
            rnn_layers=RNN_DEPTH,
            dropout=DROPOUT
        )
        decoder = LSTMDecoder(
            dictionary=task.target_dictionary,
            hidden_size=args.decoder_hidden_size,
            ...
        )
        return cls(encoder, decoder)

It is worth noting that I cannot load the whole dataset into the RAM, since the training data is extremly huge. Then, I already have a batch iterator like:
class MyDataset(object):
    def __init__(self, data_path):
        # data_path:  root directory path that contains all h5 files, where each h5 file denotes a batch
        self.data_path = data_path
        self.files = get_files_of_dir(data_path, file_type='.h5', is_full_path=True)

    def __iter__(self):
        for f in self.files:
            imgs, labels, img_widths, label_lens = _load_h5(f)
            yield torch.from_numpy(imgs).float().cuda(), # [batch_size, channels, height, width]
                    torch.from_numpy(labels).transpose(0, 1).long().cuda(), # [batch_size, label_max_length]
                    torch.from_numpy(img_widths).int()   # [batch_size, ]

So, my question is how should I re-write the class  ``MyDataset'', then I can train the defined model with the command line in the tutorial like
python train.py data-bin/datas \
  --arch image_caption\
  --encoder-dropout 0.2 --decoder-dropout 0.2 \
  --optimizer adam --lr 0.005 --lr-shrink 0.5 \

Unfortunately, the documentation seems not have mentioned how to construct a custom dataset. So, any suggestions/helps would be greately appreciated. Thanks.

Hey, I'm facing the same issue, have you found a solution?

@Ceralu The whole system is too complicated, so I end with up with other simpler implementations.

Thanks @ganji15 ! Could you share with me the other implementations you found?

@Ceralu You can refer to this simpler implementation:  https://github.com/MaximumEntropy/Seq2Seq-PyTorch.

Thanks @ganji15 !


multiple tags

I have a few tests:
    #[tag("fast")]
    #[test]
    fn outputs_help() -> Result<()> {
        // some assertions
        Ok(())
    }

    #[tag("slow")]
    #[test]
    fn outputs_something_else() -> Result<()> {
        // some assertions
        Ok(())
    }

when I run this:
TTAG=slow,fast cargo test

It won't any both tests, both outputs_help and outputs_something_else will be ignored. Let's allow multiple tags to be provided

@h1alexbel the puzzle #11 is still not solved.


Run date with command to bypass aliases.

I have an alias for date in my ~/.bash_aliases file:
alias date='gdate "+%b %e %Y %l:%M:%S %P"'

When I run z, I get an error:
> z deve
gdate: extra operand ‘+%s’
Try 'gdate --help' for more information.

That's because z uses the aliased date, and ends up trying to run gdate "+%b %e %Y %l:%M:%S %P" +%s instead of date +%s
This PR updates the references to date to use command, so that it bypasses the alias and executes /bin/date directly.

Related #264


Add ineligible pages

We route people to one of these two pages if they are not eligible for the service.
https://trello.com/c/XPHkrCje/52-ineligible-screen-2
Supplies:

https://trello.com/c/ojiB4TUg/51-ineligible-screen-1
Medical:

@leenagupte thanks for spotting those, I was on autopilot.


ROI via principal point shift and focal length scaling

Here I have MVSNet camera information for a 4000x3000 image:
extrinsic
0.999804 -0.019096 -0.00518646 -1.1364
0.0189494 0.999457 -0.0269683 -1.71932
0.00569863 0.0268648 0.999623 1.65699
0.0 0.0 0.0 1.0

intrinsic
4806.29 0 2000
0 4806.29 1500
0 0 1

2.56448 0.0640064

The focal length (4806.29 pixels) and principle point (centered) are shown in bold in the above intrinsic matrix:
4806.29 0 2000
0 4806.29 1500
0 0 1
Next we crop the input image to its top left quadrant (one quarter of our original image, now 2000x1500) and compensate in the intrinsics by doubling the focal length and shifting the principal point as follows:
9612.58 0 0
0 9612.58 0
0 0 1
The idea is to break the existing camera into parts, creating an arbitrary region of interest.
When I run MVSNet on the above, I get sensible results for the initial pose but unexpected results for the upper left quadrant intrinsics.
Is this a sound approach?  Does MVSNet need all input images to be the same size?

@KevinCain MVSNet I did not explicitly handle different image sizes, so you may pay attention to this part when using the provided script.
If you are using the top-left image, I think you only need to change the image size but the intrinsic should remain unchanged?
BTW for the top-right image patch, the intrinsic is:
4806.29 0 0
0 4806.29 1500
0 0 1

Thanks, @YoYo000, you're correct in both cases.  ;-)
I assume that when using the principal point to shift the ROI, during sparse reconstruction I should not try to estimate the principal point.

While the principal point in camera space is near image center, the image coordinates (u, v) origin is often in top left (OpenCV) or bottom left.
What assumption does MVSNet make for the principle point origin for image space?
As shown below, I believe I'm incorrectly assuming that it's the bottom right.  Considering 2054x1502 quadrants from 4108x3004 images, for the four quadrants I have the following intrinsics, which seem to be wrong:
Top left quadrant:
4714.29 0 2054
0 4714.29 1502
0 0 1
Top right quadrant:
4714.29 0 0
0 4714.29 1502
0 0 1
Bottom left quadrant:
4714.29 0 2054
0 4714.29 0
0 0 1
Bottom right quadrant:
4714.29 0 0
0 4714.29 0
0 0 1

The estimated u, v are not necessarily equal to W/2, H/2.

Assuming W=4108, H=3004, u=2054, v=1502, your formulas match the values I give above.
Using these intrinsic values with MVSNet yields incorrect results except in top left quadrant (same intrinsics, as you pointed out).  Note that the results look wrong whether I'm doubling the focal length (see quote below) as I noted before, or using the same focal length for the cropped images as for the original images.
Should the source image be the image cropped to a quadrant, or the full sized input for which the camera pose was computed?

Top left - W=4108, H=3004, u=2054, v=1502:
9428.58 0 2054 (u = 2054)
0 9428.58 1502 (v = 1502)
0 0 1
Top right - W=4108, H=3004, u=2054, v=1502:
9428.58 0 0 (u - W/2 = u - 2054 = 2054 - 2054 = 0)
0 9428.58 1502 (v = 1502)
0 0 1
Bottom left - W=4108, H=3004, u=2054, v=1502:
9428.58 0 2054 (u = 2054)
0 9428.58 0 (v - H/2 = 1502 - 3004/2 = 1502 - 1502 = 0)
0 0 1
Bottom right - W=4108, H=3004, u=2054, v=1502:
9428.58 0 0 (u - W/2 = u - 4108/2 = 2054 - 2054 = 0)
0 9428.58 0 (v - H/2 = 1502 - 3004/2 = 1502 - 1502 = 0)
0 0 1

To illustrate my above confusion, here are MVSNet results for the familiar DTU 'scan9' dataset.
Image (left), vis (center), and prob-vis (right):

The camera file is as follows (note no attempt to estimate principal point):

extrinsic
0.910293 0.164153 -0.380028 1.48815
-0.226191 0.966094 -0.124497 -0.872257
0.346706 0.199288 0.916558 1.33805
0.0 0.0 0.0 1.0
intrinsic
2888.84 0 800
0 2888.84 600
0 0 1
4.41871 0.0212743

Below, my attempt to process a quadrant of the image above.  The top left quadrant uses the same intrinsics, as @YoYo000 notes above.
Top left quadrant
Cropped input image (left), initial vis for readability (center) and prob-vis (right):

intrinsic
2888.84 0 800
0 2888.84 600
0 0 1

Top right quadrant
Cropped input image (left), initial vis for readability (center) and prob-vis (right):

intrinsic
2888.84 0 800
0 2888.84 0
0 0 1

The top full size and top left quadrant depths look reasonable to me, but not the top right.
Clearly I'm making a fundamental mistake -- if possible, can you attempt to duplicate?

Do you crop the source images as well?

As I noted above, @YoYo000's principal point offsets are correct -- my results above reflect incorrect intrinsics for some of the neighbors involved in the depth computation.


git should not be set back to master if that was not the branch checked out

I was using thrust recently while working on a feature branch and found that every time I invoked rake build_ipa:my_scheme_name that git was returned to the master branch. Sure enough, I poked around in the source code and thrust invoked git checkout master. This is unfortunate, because sometimes people want to be able to use thrust from a feature branch.
Git allows users to check out the n-th last branch or commit they had checked out, with the command git checkout @{-n}. This can be shortened to git checkout -, but I didn't think that was readable enough.
This seemed like a reasonable enough change, but I thought it would be worth opening a pull request just to get some eyes on it first.

Very much in favour of this change. Encountered this recently and thought for a few minutes that I'd uploaded a build from the wrong branch.

Same here.
On Wed, Apr 22, 2015 at 5:11 AM, pivotal-ryan-mcleod
<EMAIL_ADDRESS>wrote:

Very much in favour of this change. Encountered this recently and thought for a few minutes that I'd uploaded a build from the wrong branch.
Reply to this email directly or view it on GitHub:
https://github.com/pivotal/thrust/pull/43#issuecomment-95152052

there. :)

Addendum (for any interested parties) : the change in this PR only makes sense if you have thrust configured to build from a tag. When Thrust builds from a tag in git, it executes git checkout $TAG before building the ipa. In the absence of a tag in your thrust.yml it just builds from HEAD, so we shouldn't need to checkout any branch at all.
The relevant commit that fixes the case for buidling from HEAD is https://github.com/pivotal/thrust/commit/1778d1465f587d58e5aeb469028c4a59c1289614.


Remove phantomjs headless browser

hi
PhantomJS is a headless web browser scriptable with JavaScript. The package is no longer maintained and does not even support ES6 features of Javascript. Chrome launched ChromeHeadless which works very similar to PhantomJs. The fix will require Karma to use ChromeHeadless as the web browser instead of PhantomJs
link [ambari-web-ui)
How was this patch tested?
Please review Ambari Contributing Guide before opening a pull request.

Hi @aghazeh,
We need to port AMBARI-25985.
Will do for next release, do you need it ?
Best regards

hi @lucasbak
YES I need it.


Compatibility with jenssegers/mongodb 3.6

Are there plans to upgrade the package to make it compatible with jenssegers/mongodb 3.6. Currently getting this message when installing on Laravel 6
designmynight/laravel-mongodb-passport v1.2.7 requires jenssegers/mongodb 3.3.* || 3.4.* || 3.5.* -> satisfiable by jenssegers/mongodb[v3.3.0, v3.3.0-alpha, v3.3.1, v3.4.0, v3.4.1, v3.4.2, v3.4.3, v3.4.4, v3.4.5, v3.4.6, v3.5.0, v3.5.1, v3.5.2, v3.5.3] but these conflict with your requirements or minimum-stability

This looks like a detached and updated fork: https://github.com/narwy/laravel-mongodb-passport

@alasdairmackenzie can you create new release?


kmer model for PromethION?

Hi Jared,
Is there a different kmer model for the PromethION technology or is it the same kmer model as that for minION.
Thanks,
Dhaivat

No, we use the same model for both. It may be desirable to make one but I haven’t had the time.

On Apr 16, 2020, at 8:26 PM, joshidhaivat<EMAIL_ADDRESS>wrote:

Hi Jared,
Is there a different kmer model for the PromethION technology or is it the same kmer model as that for minION.
Thanks,
Dhaivat
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Thanks! Can you also let me know or point me to some reference of how you generate the kmer model?

It’s not well documented but the new method is called ‘nanopolish train’ in the r10 branch. I’ll try to write a description for it when I find a bit of time.

On Apr 16, 2020, at 8:38 PM, joshidhaivat<EMAIL_ADDRESS>wrote:

Thanks! Can you also let me know or point me to some reference of how you generate the kmer model?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Thank you!


AccountTx reported ledger ranges

Is it safe to honor the ledger ranges returned by account_tx these days? I vaguely recall an issue and Chris Clark (RippleAPI author) working around it by using a RangeSet implementation and looking at the reported ledger ranges:
https://github.com/ripple/ripple-lib/blob/develop/src/ledger/transactions.ts#L119
https://github.com/ripple/ripple-lib/blob/develop/src/common/connection.ts#L382
https://github.com/ripple/ripple-lib/blob/develop/src/common/connection.ts#L44
https://github.com/ripple/ripple-lib/blob/develop/src/common/rangeset.ts#L54
What's going on here? I checked, and at a quick glance it seems to report only validated ledger ranges, but I'm not confident in a "quick glance":
https://github.com/ripple/rippled/blob/develop/src/ripple/app/ledger/impl/LedgerMaster.cpp#L384
Was rippled updated since that ripple-lib code was written?
Was the issue unreported?
Is the issue still there?
I'm helping someone with ripple, that isn't using RippleAPI, and it's nagging in the back of my head, but I don't have the time to dive into it myself.

@mDuo13 can you take a look at this to see if its purely a documentation or do we need to work this?

@carlhua I do not know and I can't read the C++ code with enough confidence to find out.


[BUG] no error when component links to itself

When the source and target of a link are the same, the application status should surface an error. This should be considered an invalid link.
❯ wash app status test

test@ - Deployed

  Name                                                             Kind                   Status
  component1                                                  SpreadScaler   Deployed
  component1 -(test:foo)-> component1     LinkScaler         Deployed
  component2                                                 SpreadScaler    Deployed
  httpserver -(wasi:http)-> component1      LinkScaler         Deployed
  httpserver                                                     SpreadScaler    Deployed

@ricochet to play devils advocate, is there a legitimate use case for recursion with the same component? I tend to agree that this is probably always invalid (especially if not running with a certain scale, since it would just timeout) but figured before we make it an error it would be good to consider if this is a real use case

I couldn't come up with a reason this would be valid, especially not where the solution had to involve recursion over the same component (vs making another component for fan-out-fan-in even if they have the same logic, both components serve as logically different nodes in the DAG).
If we're looking to replicate linking but distributed, then note that circular linking is disallowed in the component model.

Yeah, I think that if it's something that's not allowed with just regular composition, then it's not something we want to encourage. Maybe there's a real use case here, but we can address that when it comes up


Can't login after a fresh install

Hi, this is the error when I access to login page. I followed the instructions "Local Quickstart".

reply@Jarvis-M1 chatbot-ui % npm run chat

<EMAIL_ADDRESS>chat
supabase start && npm run db-types && npm run dev

supabase start is already running.
Run supabase status to show status of local Supabase containers.

<EMAIL_ADDRESS>db-types
supabase gen types typescript --local > supabase/types.ts

(node:1) ExperimentalWarning: Import assertions are not a stable feature of the JavaScript language. Avoid relying on their current behavior and syntax as those might change in a future version of Node.js.
(Use node --trace-warnings ... to show where the warning was created)
(node:1) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time

<EMAIL_ADDRESS>dev
next dev

▲ Next.js 14.1.0

Local:        http://localhost:3000
Environments: .env.local

[PWA] Compile server
[PWA] Compile server
[PWA] Compile client (static)
[PWA] Custom worker found: /Users/reply/Developer/repository/Reply/chatbot-ui/worker/index.js
[PWA] Build custom worker: /Users/reply/Developer/repository/Reply/chatbot-ui/public/worker-development.js
[PWA] Auto register service worker with: /Users/reply/Developer/repository/Reply/chatbot-ui/node_modules/next-pwa/register.js
[PWA] Service worker: /Users/reply/Developer/repository/Reply/chatbot-ui/public/sw.js
[PWA]   url: /sw.js
[PWA]   scope: /
[PWA] Build in develop mode, cache and precache are mostly disabled. This means offline support is disabled, but you can continue developing other functions in service worker.
✓ Ready in 2.5s
⚠ GenerateSW has been called multiple times, perhaps due to running webpack in --watch mode. The precache manifest generated after the first call may be inaccurate! Please see https://github.com/GoogleChrome/workbox/issues/1790 for more information.
⚠ GenerateSW has been called multiple times, perhaps due to running webpack in --watch mode. The precache manifest generated after the first call may be inaccurate! Please see https://github.com/GoogleChrome/workbox/issues/1790 for more information.
○ Compiling /middleware ...
⚠ GenerateSW has been called multiple times, perhaps due to running webpack in --watch mode. The precache manifest generated after the first call may be inaccurate! Please see https://github.com/GoogleChrome/workbox/issues/1790 for more information.
⚠ GenerateSW has been called multiple times, perhaps due to running webpack in --watch mode. The precache manifest generated after the first call may be inaccurate! Please see https://github.com/GoogleChrome/workbox/issues/1790 for more information.
⚠ GenerateSW has been called multiple times, perhaps due to running webpack in --watch mode. The precache manifest generated after the first call may be inaccurate! Please see https://github.com/GoogleChrome/workbox/issues/1790 for more information.

⚠ metadata.metadataBase is not set for resolving social open graph or twitter images, using "http://localhost:3000". See https://nextjs.org/docs/app/api-reference/functions/generate-metadata#metadatabase
⚠ GenerateSW has been called multiple times, perhaps due to running webpack in --watch mode. The precache manifest generated after the first call may be inaccurate! Please see https://github.com/GoogleChrome/workbox/issues/1790 for more information.
⚠ GenerateSW has been called multiple times, perhaps due to running webpack in --watch mode. The precache manifest generated after the first call may be inaccurate! Please see https://github.com/GoogleChrome/workbox/issues/1790 for more information.
⚠ GenerateSW has been called multiple times, perhaps due to running webpack in --watch mode. The precache manifest generated after the first call may be inaccurate! Please see https://github.com/GoogleChrome/workbox/issues/1790 for more information.
⚠ metadata.metadataBase is not set for resolving social open graph or twitter images, using "http://localhost:3000". See https://nextjs.org/docs/app/api-reference/functions/generate-metadata#metadatabase
⨯ app/[locale]/login/page.tsx (45:12) @ Login
⨯ Error: JSON object requested, multiple (or no) rows returned
at Login (./app/[locale]/login/page.tsx:51:19)
43 |
44 |     if (!homeWorkspace) {

45 |       throw new Error(error.message)
|            ^
46 |     }
47 |
48 |     return redirect(/${homeWorkspace.id}/chat)
⨯ app/[locale]/login/page.tsx (45:12) @ Login
⨯ Error: JSON object requested, multiple (or no) rows returned
at Login (./app/[locale]/login/page.tsx:51:19)
digest: "4037407642"
43 |
44 |     if (!homeWorkspace) {
45 |       throw new Error(error.message)
|            ^
46 |     }
47 |
48 |     return redirect(/${homeWorkspace.id}/chat)

Fixed cleaning browser data on localhost.


Unable to receive to address been choozen on Receive buttom

Hi, guys!:)
It may be bug...
If I sending UFO to one of addresses from "My active addresses" - the everything is ok.
But it's impossible receive coins to address choozen by "RECEIVE" buttom.
Help me please.
Thank you.

You would see an address while u click "receive" button. But the address is not in your wallet now, so you can not send UFO to this address.
You should click "copy transaction address" button or "save" button at the same page, and then this address will be stored into your wallet database, and then you can use this address as your receiving address.


Added really simple test to see if rails credentials are working for CI.

Coverage remained the same at 92.95% when pulling 8df7597ac55d2f6ff0564f72d0d08f23c98fa34e on test-secrets into 81e53b882afc5d1e1dc90015a3feda4360af1077 on master.


updates column width length check

converts any cell value to string before performing length check to ensure length check works.
In chrome (78.0.3904.70), I was trying to paste in some content that must have had some characters that the length check didn't like.  Oddly enough, when performing the row[columnIndex].length check in the debugger it worked, but it only threw an error at runtime.  The error I received was
Uncaught TypeError: Cannot read property 'length' of undefined
    at script.js:5
    at Array.map (<anonymous>)
    at columnWidth (script.js:4)
    at script.js:28
    at Array.map (<anonymous>)
    at HTMLTextAreaElement.<anonymous> (script.js:27)

@mhlavacek thank you for the contribution, sorry I didn't see it sooner. I'll add you as a contributor to the README.

@mhlavacek thank you for the contribution, sorry I didn't see it sooner. I'll add you as a contributor to the README.


new generic proxy extension to contrib

Signed-off-by: wbpcode<EMAIL_ADDRESS>Commit Message: new generic proxy extension to contrib
Additional Description:
Ref #18209 for more background information.
This PR is under active development. It's only used to make the maintainers and sponsor can give a quick review to the key API or interface.
This is a huge feature, so I chose to add it to contrib instead of the main extension repository. If its value and stability are verified later, we can consider moving it to the main extension repository.
Risk Level: N/A.
Testing: N/A.
Docs Changes: N/A.
Release Notes: N/A.
Platform Specific Features: N/A.

new PR: #18944


Getting rid of "isolated" GPS bad readings

@jamesmontemagno  (sorry really don't know where else to contact you to ask this).
I have been using your plugin successfully on Android and iOS, but sometimes when using my app I get weird readings (which I think are a result of going close to tall buildings which affect the signal quality or precision of the GPS), showing up as "weird spikes" (isolated points) when looked at a map. Then when the signal reestablishes it starts reading everything right 👍
Looking up at the code of "MyDriving" which you gave me as a reference to run the Android Service on the background, I can't seem to find how you fixed this (if you did). I thought to use the GPS signal quality but really cant find a way to do so on Xamarin Forms. Do you know a way I can get rid of this "bad readings"?
pd: Also thought about using the compass, but not all devices have compass so it wouldn't work.. Right now I am calculating the acceleration as a magnitude and using that to eliminate some of those wrong readings but if you know a better way I would really appreciate it.
Also if you need more information please let me know!

Just realized that the returned object has "Accuracy" (my bad). Which do you think would be the sweet spot for measuring car positional data (from your experience). Meaning the "maximum tolerable accuracy value".

Does the problem go away if you change the device location settings to GPS Only?  Having mixed results using the Network assisted Location.

@istoff Will check on the weekend and report back.


Jenkinsfile: add quietPeriod for all triggered builds

When a K PR gets merged, a lot of builds are triggered. These almost always completely saturate our CI machines. This should stagger them a bit so that their updates happen a little less intensely.
The quietPeriod for this job is set to 120s. I would like to set it to 1200s, but then they will never get scheduled because the build-killer runs ever 240s. So I think setting it to 120s should have them staggering by roughly 240s at a time, which will at least let some of the faster semantics test-suites get most of the way through before the slower ones start.

I don't understand. why would the build killer be killing pending builds for which no newer build exists? That sounds dangerous to me.

The build killer runs every 4 minutes, so that maximum quiet period this triggered job ever sees is 4 minutes. So setting it to a quiet period of 20 minutes would mean that these jobs never get scheduled.
Note that the jobs being scheduled here are rv-devops/master jobs, which is the same job which runs the build killer.
The build killer will not kill builds that no newer build exist for.

Staggering even by 2 minutes minimum here (more realistically by 4 minutes in some cases, and up to 6 minutes in others) will already be a big improvement.

Hmmm, actually, it would appear that builds with different parameters on the same job are given different quiet periods: https://github.com/eclipse/codewind/issues/2408
So this will be useless anyway.


V2510: Broken link

Hello @mashamsft,
there is a broken link in the page in this string:
For more information about enabling Windows PowerShell scripts, see Running Windows PowerShell Scripts.
Please review and merge the proposed file change to fix to target versions. If you make related fix in another PR then share your PR number so we can confirm and close this PR.
Many thanks in advance.

@v-makoud : Thanks for your contribution! The author, @mashamsft, has been notified to review your proposed change.

Hi @v-makoud - The changes in the PR should have been made via the private repository, azure-docs-pr. The private repo has better validation and QA, so Microsoft contributors are expected to use that channel. Please submit future updates through the private repo.
Read about authors working in the public repo for more information.
Thanks.

Hi @v-makoud , this should have gone through the private repo. I am closing this PR, and making this change within PR 8075. Thanks!


Eaten exception causing empty result

Hi,
I just finished extensive debugging and found that if Jackson's Deserialization Exception  happens (in form of AlgoliaException) when Browsing indexes, the exception is eaten and empty result is returned.
It's here: https://github.com/algolia/algoliasearch-client-java-2/blob/master/algoliasearch-common/src/main/java/com/algolia/search/IndexIterator.java#L66
Line 66 in IndexIterator.java .
In my opinion the AlgoliaExeption should be thrown and at least LOG.error should be printed.
BR,
Gregory

Thanks for the report.
Indeed the exception is eaten. But apart from throwing a RuntimeException, I don't see what to do.
I prefer not to have Logs in the API clients are it would need to expose a way to configure, tweak it.
So would a Runtime would be ok with you?

For me better to throw RuntimeException or AlgoliaException from there, so it does not hide the real problem of jackson's deserialization.

I can not throw a typed exception because the method the interface Iterator do not throw exceptions. So it must be a runtime

Good for me.


Improve messaging about unknown artifact refs

See original issue on GitLab
In GitLab by [Gitlab user @tristanvb] on Apr 1, 2019, 09:06
We usually use the ???????? key (cache key length filled in with question marks) to indicate artifact refs that are as yet unknown, and most of the time this makes sense (like before an element gets tracked).
When attempting to pull artifacts in non-strict mode however, it only half makes sense.
Looking at these messages:
[--:--:--][????????][ pull:core-deps/spice-gtk.bst       ] STATUS  Pulling artifact ???????? <- https://cache.gitlab.gnome.org:11001
[--:--:--][????????][ pull:core-deps/spice-gtk.bst       ] INFO    Remote (https://cache.gitlab.gnome.org:11001) does not have ???????? cached

What makes sense to me is the left hand [????????] portion of the log lines; BuildStream is basically saying that we dont yet know what the actual key will be - this is to say that even though we might have a local artifact which matches the weak key, we still try to pull a remote artifact and when we do that, we try to prefer the strong key.
What doesnt make sense here is "Pulling artifact ???????? ....", and "... does not have ???????? cached" - clearly we do know what artifact we are trying to pull, but we are blindly using the element's artifact display key in this message and this is confusing/misleading.

In GitLab by [Gitlab user @abderrahimk] on Apr 21, 2019, 21:40
mentioned in commit 1262937fbc08ea5a6e5f3621695d062579daf950

In GitLab by [Gitlab user @abderrahimk] on Apr 21, 2019, 21:59
mentioned in commit caa5563cc61a74cd57e0618c0007bf1855bf3c80

In GitLab by [Gitlab user @abderrahimk] on Apr 21, 2019, 21:59
mentioned in commit 025138d14b40272b0852f0574e3ccbb74178d126

In GitLab by [Gitlab user @abderrahimk] on Apr 22, 2019, 16:20
mentioned in merge request !1304

In GitLab by [Gitlab user @abderrahimk] on Apr 22, 2019, 16:20
mentioned in commit e32ea9d08a971eb53d481cd8ce54d9464af321e4

In GitLab by [Gitlab user @abderrahimk] on Apr 22, 2019, 16:22
mentioned in merge request !1305

In GitLab by [Gitlab user @abderrahimk] on Apr 22, 2019, 16:24
mentioned in commit ebf21f3c0faa7ef81125628b2b8b2c3cd1326055

In GitLab by [Gitlab user @abderrahimk] on May 1, 2019, 08:28
mentioned in commit 40348ce402cbc3c6ee6110a01326b9131e524512

In GitLab by [Gitlab user @abderrahimk] on May 1, 2019, 10:21
mentioned in commit aa97cd57163a5d3cfe01de0f4062c08b62f39f3c

In GitLab by [Gitlab user @marge-bot123] on May 1, 2019, 11:03
closed via merge request !1304

In GitLab by [Gitlab user @marge-bot123] on May 1, 2019, 11:03
mentioned in commit bccb4f15a784a80561c32665ced44554dbd9b5ce

In GitLab by [Gitlab user @abderrahimk] on May 4, 2019, 05:49
mentioned in commit 98d9ba255907a2d6d96095392c37b71700ccff1e


ci: use time param for reboot

Currently we had the reboot function on SUT with a hardcoded timeout
which was hitting its limits on the raw disk test
This modifies the reboot function so it acceps a timeout and passes it
to the EventuallyConnects function
Signed-off-by: Itxaka<EMAIL_ADDRESS>

According to the serial logs I checked a while ago on some failed tests I saw that first boot took around 250 seconds and it was failing due to a timeout on reboot. So increasing the reboot time might definitely help to fix the issue, even though more 180s for a single reboot without having to install anything at boot time is close to the unacceptable area, but we can analyze that later on.

@mudler the raw image deploy test passed. I'd say there is no need to wait for all the tests, if possible I'd force merge this PR as it has potential to unblock others.


Remove adjancency matrix code

Closed by mistake, a stash caused the close.

This code has been removed


offline storage of audio, video

How to have offline storage of audio, video from third party servers like aws s3?

Do you want to ask a question? Are you looking for support? The Framework7 forum and Stack Overflow are the best places for getting support

Please, don't use GitHub issues for questions


Implement notebook filtering and refactor search handlers

Implements notebook filtering which can be enabled in the settings page.
Also refactors note searching to be more extendible and allow for common search constraints.

Addresses #20


TLS Provider document generation

@justinvp / @chrsmith I am going to merge this now so I can check it out on staging - we can do something with that duplicate config.toml before production


chore: add headful support for Firefox

So far there is only the npm run test:firefox command available that runs Puppeteer tests in Firefox with headless mode. To stay in par with Chrome this PR enables the headful mode for Firefox as well so that the following commands are available:

test:firefox:headless
test:firefox:headful
test:firefox

@OrKoN as it looks like headful tests are working perfectly fine now. There is only one additional test that I had to mark as skipped.


Shape of a vector is ambiguous

From reading the spec, it seems that it's ambiguous what we should put under the key shape when the format is DVEC.  Do we want shape: 100?  shape: [100]?  Or shape: [100, 1]?
In order to work well with tensors, I'm guessing we want shape: [100], but we need to make sure it's unambiguous in the spec, and preferably add some examples.

My opinion: clarify that vectors (including DVEC) are shape e.g. [100] (not 100).

Yes! This allows scalars to be shape []


[rp2040] Buffer Full Assertion

sending a bunch of LED on and off commands, eventually, get a buffer full message:
assertion "buf_ctrl & USB_BUF_CTRL_FULL" failed: file "C:\Users\balde\Documents\Pico\pico-sdk\lib\tinyusb\src\portable\raspberrypi\rp2040\rp2040_usb.c", line 225, function: sync_ep_buffer

Newer version of the TinyUSB library seems to have fixed the assertion. (Or is it still commented out?)

Unclear, but I don't think we've had this issue recently.

Rev 3b is working very well, not sure if this is still an issue. Need to investigate later.


Not Updated for 1.21

Hi there,
Is there any chance you'll be updating this for 1.21?
Best regards,
Jay

I'm also anticipating :)


Deserializing borrowed strings with escape sequences in custom deserializer

I'm currently writing a deserializer with serde for a file format.
In strings, I want to replace some escape sequences.
The code for parsing these strings is the following:
impl<'de> crate::de::Deserializer<'de> {
    pub(crate) fn parse_string(&mut self) -> Result<String> {
        let (start, end) = self.collected.map(Ok).unwrap_or_else(|| {
            let (line, col) = self.get_line_column();
            Err(Error::new(ErrorCode::ExpectedString, line, col))
        })?;
        let src_slice = &self.source[start..end];
        let collected = src_slice
            .replace("`[", "[")
            .replace("`]", "]")
            .replace("``", "`");
        Ok(collected)
    }
}

This code returns an owned string, so when I try to implement the deserialize_str method:
impl<'de, 'a> de::Deserializer<'de> for &'a mut Deserializer<'de> {
    //...
    fn deserialize_str<V>(self, visitor: V) -> Result<V::Value>
    where
        V: de::Visitor<'de> {
        visitor.visit_borrowed_str(self.parse_string()?)
    }
}

I get an error because the string has to be borrowed for 'de. How could I fix this issue? I've found a few issues regarding something similar, but none seemed to fix the issue.

Change parse_string definition to return Cow<'de>. If you doesn't make any replaces, return a Borrowed variant, otherwise return an Owned variant.
You also can try to make in-place replacements in your string and always return a borrowed string from parse_string

Does that answer your questions? If not, you can usually get quicker help in the forum or the discord (see https://www.rust-lang.org/community for links)


Foxx Manager CLI should provide usage examples for commands

Currently it's not at all obvious what the arguments for certain commands of the Foxx Manager CLI should look like. Ideally every command that takes arguments should at least provide a usage example.
Via #1427.

I'll look into this further when I'm in office tomorrow.
Ideally foxx-manager should support a more detailed help command, e.g.:
$ foxx-manager help set-dependencies
Usage: foxx-manager set-dependencies mountpoint alias1=mountpoint1 alias2=mountpoint2 ...
Some more detailed description goes here.

:+1:

@pluma has this been solved?

@fceller Not that I know of.

Closing in favour of https://github.com/arangodb/foxx-cli


Does ObserverQuery work when app is killed?

It is not clear by the documentation, if observerQuery works when app is killed.
My current understanding is that it doesn't work. If that is true, do you think you will support it in the future?

Hi @spiritinlife
According to the Apple Documentation related to background updates, the observing queries should be initilized in ** didFinishLaunchingWithOptions** of ** AppDelegate** file. This background delivery and observing queries combination will allow you to get notifications from Apple Health even if your app is killed. The idea is that whenever a new value appears/disappears in Apple Health, the observerQuery's update handler will be triggered, and the code you provide there will be executed. But, unfortunately this works only natively.
I am afraid there is no chance for now to do the same in Flutter part of the library, i.e put observation in "main" function.
Because events handling between the native part and the flutter part starts when the subscription is set on the flutter side.
Although the observer query will be still running when the app has "Not Running" lifecycle state, the stream subscription on the flutter side will be canceled when the app will be killed by the system.
I will try to adjust the explanation in README

Btw, in order to see how ObserverQuery is actually working, you can check out a native example of the HealthKitReporter. It is the base library for this flutter wrapper

I will also present some changes in event handling in new version

@VictorKachalov thx for the quick response.
This library seems to be able to do it https://github.com/nanoglobal/nano_healthkit.
Also https://github.com/fluttercommunity/flutter_workmanager should be doing something similar.

Ok, it appeared, that it was suppose to work all the time :) but was a lack of an appropriate Capability for background fetch and an argument exceptions in enabling background deliveries. You may try again. In the example app I added some local notifications, which should be triggered if some data is changes. The version is 1.0.5 now.

hi @spiritinlife
Have you already tried to use this package with observing queries on and while the app is in background/killed?

Haven't had the time to test it unfortunately.
On Thu, 4 Mar 2021 at 16:00, kvs<EMAIL_ADDRESS>wrote:

hi @spiritinlife https://github.com/spiritinlife
Have you already tried to use this package with observing queries on and
while the app is in background/killed?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/VictorKachalov/health_kit_reporter/issues/3#issuecomment-790637902,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABRDBJ64NG6YH4NWY6GZYVTTB6HABANCNFSM4UR4DIZQ
.

@VictorKachalov I've been testing ObserverQuery while the app is killed but I can't make it work properly. I already enable background capabilities and even init the observer as an isolated function in the main method of the app. I can say it was working a few times while the app is killed but after waiting some time it stops working properly. Thanks in advance

I tried this https://github.com/nanoglobal/nano_healthkit, and it working fine even when the app killed
However, it is too old and has been a long time didn't update

Hi all
Is there any update one this issue? Having background functionality even when the app is killed would be extremely useful. I see the README states it should work when the app is killed (is that still true?), because I have tested when the app is killed but the ObserveryQuery doesn't seem to work then. Only when the app is either open or in the background.

I am also wondering if the background functionality is working realiably?


Consider the Linux template stable

Description
Remove the version checking and associated warnings. The Linux template
and build process will now be subject to more typical Flutter breaking
change policy, and should no longer require regularly deleting and
recreating the platform directory.
Related Issues
None.
Tests
I added the following tests: None; removed tests associated with this check.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change.

Started Google testing for this PR

Google testing passed!


UI: No "visible" shadow effect in dark mode at "Search the docs"

There is a shadow effect around the "search the docs" when the website is used in light mode. But when used in a dark mode, there is no "visible" shadow effect.

Related issue on compose theme repo, https://github.com/onweru/compose/issues/70


Support 'keysIgnoreAccents' feature to ignore accents in keys?

I have a use case where people could input accent or not in keys and I want a specific version of my keys.
You could use theKey.normalize('NFD') to do such a job, see this SO answer to remove accents in javascript strings.

Feel free to submit a PR, as long as it's behind a flag and includes unit tests I'll accept it.
I would call it keysAutoNormalized.

Here it is, with unit tests, what do you think about this PR? (I added a TODO inside in order to later on think of a way to boost key searches with some cache...)

Looks pretty good.

Remove the TODO comments. If there's an optimization there (not sure there is) feel free to create an issue to track it. Any performance improvements should have benchmarks to prove it.

Update the unit tests to ensure both read and write access work correctly. You currently have:

o.schéma = 'a string';
o.schema.should.equal('a string');

We need to check all cases. So, for example:
o.schéma = 'a string';
o.schéma.should.equal('a string');
o.schema.should.equal('a string');

o.schema = 'new string';
o.schéma.should.equal('new string');
o.schema.should.equal('new string');

I don't understand, I think, given the following code:
            var SO = new SchemaObject({
                schema: String
            }, {
                keysAutoNormalized: true
            });

            var o = new SO();
            o.schéma = 'a string';
            o.schema.should.equal('a string');

I would expect:
            should.equal(o.schéma, null);

The same happens with keysIgnoreCase:
            var SO = new SchemaObject({
                profileURL: String
            }, {
                keysIgnoreCase: true
            });

            var o = new SO();
            o.profileUrl = 'a string';
            o.profileURL.should.equal('a string');

            should.equal(o.profileUrl, null); // which is currently the case by the way


Django-REST integration?

Would this be able to pick up DRF interactions, like Serializer -> ORM -> DB ?

@tomchristie do you have any thoughts on this?

@SEJeff Only that instrumenting the ORM queries really is the most important aspect.

I would also argue that having ability to customize route -> trace tags mapping would be desirable. Anyhow, I take it you guys would consider this a valid feature?

@ror6ax I just figured out how to fix the route bit I believe. I'll send some PR's soon, but it uses this class more or less like this.
It results in the route (for a DRF app that uses rest_framework.routers.DefaultRouter for the url routing that looks like this:
alert-app-service-name: /api/alert/{pk}/

Bonus points that raven-python is also licensed under the 3 clause BSD, so we could potentially lift the code if necessary to this project.

Any news on this?


Make kernel version detection code in EpollReuseAddrTest more robust

Motivation:
When we try to parse the kernel version we need to be careful what to
expect. Especially when a custom kernel is used we may get extra chars
in the version numbers. For example I had this one fail because of my
custom kernel that I built for io_uring:
5.8.7ioring-fixes+
Modifications:

Try to be a bit more lenient when parsing
If we cant parse the kernel version just use 0.0.0

Result:
Tests are more robust

@chrisvest yah didn't want to go to fancy here...


Central media replacement

Many municipalities use files (especially PDF) and replace them regularly (example: menu) and then have to replace them in every language. It would be useful to be able to do this at a central location for the corresponding documents.

This could include linking documents in different languages together?!


[bn] Localize /docs/concepts/overview/working-with-objects

Completed localization of k8s working with object index file. More specfically file path is  [concepts/overview/working-with-objects
/_index.md]
Fixes Issue : https://github.com/kubernetes/website/issues/44993
Related PR : https://github.com/kubernetes/website/pull/45009
Tracking Issue: https://github.com/kubernetes/website/issues/31677

/retitle [bn] Localize /docs/concepts/overview/working-with-objects

Good work @cloudwithtanvir  vaia ❤

Great work @cloudwithtanvir


Add documentation on feature class at start of class

Issues to cover:

Explanation of feature class
Calculation of data matrix (if applicable)
Small matrix example
Possible custom settings (none necessary for currently implemented feature classes)
References (Article / Wiki / Other URLs)

Last references added by #181


Error While Setting Up JVCProjector

Love this addon! I disabled my projector config yesterday to troubleshoot something, and now it's not reconnecting to my projector. Was working great for months beforehand. I don't believe anything has changed on the projector, IP is the same, can telnet to IP and 20554. Not sure what I'm missing. Tried all available version(including master), and all have the same or very similar error. Any ideas? Here's the HASS log:
Error while setting up jvcprojector platform for remote
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/jvc_projector_remote/jvccommands.py", line 109, in __verify_ack
    ACK = sock.recv(COM_ACK_LENGTH)
TimeoutError: timed out

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 281, in _async_setup_platform
    await asyncio.shield(task)
  File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/jvcprojector/remote.py", line 40, in setup_platform
    JVCRemote(name, host, password, port, delay, timeout, retries),
  File "/config/custom_components/jvcprojector/remote.py", line 71, in __init__
    self._jvc = JVCProjector(self._conf_host, self._conf_password, self._conf_port, self._conf_delay, self._conf_timeout, self._conf_retries)
  File "/usr/local/lib/python3.10/site-packages/jvc_projector_remote/jvcprojector.py", line 55, in __init__
    self.validate_connection()
  File "/usr/local/lib/python3.10/site-packages/jvc_projector_remote/jvcprojector.py", line 174, in validate_connection
    self._send_command(Commands.nullcmd)
  File "/usr/local/lib/python3.10/site-packages/jvc_projector_remote/jvcprojector.py", line 153, in _send_command
    command.write(jvc_sock)
  File "/usr/local/lib/python3.10/site-packages/jvc_projector_remote/jvccommands.py", line 173, in write
    self.__verify_ack(sock, command)
  File "/usr/local/lib/python3.10/site-packages/jvc_projector_remote/jvccommands.py", line 127, in __verify_ack
    raise JVCCommunicationError(
jvc_projector_remote.jvccommands.JVCCommunication
Error: Timeout when waiting for the specified ACK: `b'\x06\x89\x01\x00\x00\n'` for command: `nullcmd` with bytes: `b'!\x89\x01\x00\x00\n'`

Thank you!

1.0.2 seems to work. 2.0.0a2 seems to break it. Must not have been up to date for a while... But I swear I was...

Hi guys, what model projector do you have? Looks like it is not responding as expected to the nullcmd that is used to verify communications.
I have removed this check in the latest master branch (allow pre-release in hacs and select "master" for the version). Try it out and it if works, I'll backport it to v2.0.0. You'll have to set up via the config flow by adding the integration through the UI, not via configuration.yaml

I have the JVC DLA-NP5 (lamp based instead of laser)Op 13 dec. 2022 om 10:25 heeft Shahzeb Imran @.***> het volgende geschreven:
Hi guys, what model projector do you have? Looks like it is not responding as expected to the nullcmd that is used to verify communications.
I have removed this check in the latest master branch (allow pre-release in hacs and select "master" for the version). Try it out and it if works, I'll backport it to v2.0.0. You'll have to set up via the config flow by adding the integration through the UI, not via configuration.yaml
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

Thanks Bezmi! I'm running an NX7 projector.
New Master branch gives me the following when trying to add through the UI:
`
Unexpected exception
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/jvc_projector_remote/jvccommands.py", line 109, in __verify_ack
ACK = sock.recv(COM_ACK_LENGTH)
TimeoutError: timed out
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/config/custom_components/jvcprojector/config_flow.py", line 64, in async_step_user
info = await validate_input(self.hass, user_input)
File "/config/custom_components/jvcprojector/config_flow.py", line 42, in validate_input
mac = format_mac(await hass.async_add_executor_job(projector.get_mac))
File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.10/site-packages/jvc_projector_remote/jvcprojector.py", line 208, in get_mac
return self._send_command(Commands.macaddr)
File "/usr/local/lib/python3.10/site-packages/jvc_projector_remote/jvcprojector.py", line 156, in _send_command
result = command.read(jvc_sock)
File "/usr/local/lib/python3.10/site-packages/jvc_projector_remote/jvccommands.py", line 188, in read
self.__verify_ack(sock, command)
File "/usr/local/lib/python3.10/site-packages/jvc_projector_remote/jvccommands.py", line 127, in __verify_ack
raise JVCCommunicationError(
jvc_projector_remote.jvccommands.JVCCommunicationError: Timeout when waiting for the specified ACK: b'\x06\x89\x01LS\n' for command: macaddr with bytes: b'?\x89\x01LSMA\n'
`

Just installed 'latest' master release, still not connecting in my case.

How to troubleshoot?

11 days is correct. I removed the bit of code mentioned in your initial error, so it no longer sends the nullcmd to check the connection. This time it's failing at the command that fetches the MAC address.
Are you saying that 2.0.0a3 worked previously but doesn't anymore? That's odd. v2.0.0 (no suffix) is actually more recent than the alpha ones. You can try that and report and error messages back here . I've also re-published the very first alpha - v2.0.0a1, same drill.
Sometimes the connection to the projector gets borked and it won't accept new communication from your Hass IP. This has worked to fix it for me in the past:
Full power cycle of the projector at the wall. Reset the network by assigning a (different) static IP in the projector network settings, apply these settings and then change them back to the previous values. Just don't pick the same IP as another device on the network.
Now as for why v1 works - there is no information fetched from the projector in this version. Only one way commands are sent to the device and all return communication is disregarded. v2a1, v2a2, v2a3 and v2.0.0 (latest) all rely on return info to get the state attributes and validate the connection in some way.

Well you called that… changed the IP by 1 digit and connected right away on Master! Strange…
Would be a good troubleshooting step to post in the readme! Thank you:-) I’ll send ya a donation in a sec here.

Awesome and thanks in advance for the donation! I would suggest staying on the latest V2.0.0 until V2.1.0 which will be based on the current master.
Unfortunately these projectors seem to be quite quirky with the communications protocol - or some details are missing from the official protocol documentation. We always have hacky workarounds I guess 😅

Awesome and thanks in advance for the donation! I would suggest staying on the latest V2.0.0 until V2.1.0 which will be based on the current master.
Unfortunately these projectors seem to be quite quirky with the communications protocol - or some details are missing from the official protocol documentation. We always have hacky workarounds I guess 😅

Absolutely! I would've never guessed it just didn't like the IP anymore haha. I'll rollback to the current v2.0. Thank you!

Same here, by changing IP to another and back to the original, the problem disaappeared!
Thanks!

Great, I'll leave this open pending investigation into why it happens and any possible fixes.

Thanks for your work and patience.
The problem seems to be back again :-(
This error originated from a custom integration.
Logger: custom_components.jvcprojector.remote
Source: custom_components/jvcprojector/remote.py:128
Integration: jvcprojector (documentation)
First occurred: 12:52:35 (1 occurrences)
Last logged: 12:52:35

The projector is not connected, cannot send command

Logger: jvc_projector_remote.jvcprojector
Source: /srv/homeassistant/lib/python3.10/site-packages/jvc_projector_remote/jvcprojector.py:177
First occurred: 11:29:39 (167 occurrences)
Last logged: 12:52:39

Couldn't verify connection to projector at the specified address: cinema-projector.flissinger.local:20554.

This error originated from a custom integration.

Logger: custom_components.jvcprojector.remote
Source: custom_components/jvcprojector/remote.py:106
Integration: jvcprojector (documentation)
First occurred: 11:29:39 (167 occurrences)
Last logged: 12:52:39

Couldn't connect to the projector at the specified address: cinema-projector.flissinger.local:20554. Ensure the configuration is correct.

Try staying on the master branch for a little bit and see how it goes with stability. It should be a little better for this particular issue. You can also try increasing the delay parameter.

Switched back to the 'master' release and increased the delay.

Not sure if I'm having the same issue, but I recently updated via HACS last night and my automations broke.  I was on a 1. Release before.
What is odd is that I can turn the projector off and on via toggle in the overview, but when calling things like masking from the service in the developer section or a pre existing automation fail.  If it was a connectivity thing, wouldn't everything fail?
I'll try changing the IP to something and back, and see if that helps.  The integration was rock solid before the update.

Okay I sorted it.  The command names have changed.  Instead of memory2 it is now memory-2
Thanks for keeping this alive.  Expect some support coming your way.

Yep, command format change was the reason the version numbering went from 1 -> 2. Appreciate the long term use and support :)

Hi, this could be caused by many things - when the projector sends "PJNAK", it's refusing to connect with you.
here are some suggestions:

remove the "timeout" entry from your config, or make it a larger integer (2-10). The docs are wrong to suggest 0.5 seconds. The default is actually 2 seconds. I will correct the docs on this
Increase the delay setting to 700 or 800ms.

If it still doesn't work, you should try the "master" branch (enable beta versions in HACS), which has a few updates and relies on a config flow to set up the projector rather than configuration.yaml.

Hi,
Changing settings in configuration.yaml did not work, but moving to the master branch with beta updates worked through the UI.  Thanks for the quick response.


Supported Debugging through VSTEST_DATACOLLECTOR_DEBUG env variable.

Added support for debugging DataCollector process through VSTEST_DATACOLLECTOR_DEBUG env variable.
Related to : https://github.com/Microsoft/vstest/issues/309

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


fix(review): Fix typo in review script

Fixes a minor typo in the bats review output when the orb-tools identifies a long line not imported.

Bump!  cc @KyleTryon

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/circleci/orb-tools?version=dev:5c242d2d803092292beb2517f46c73af262d032b


feat: 3D portal helpers

Portal helpers but 3D using box portals.
(I don't know how to explain it further lmfao)

There is MiniScaled mod that helps creating scale boxes https://github.com/qouteall/MiniScaledMod/blob/1.18/README.md

I was thinking about having more sizes than 1x1 -> yxy

Making scale box is tricky so it's recommended to use MiniScaled mod


“account_tx” with invalid ledger_index_max returns "invalidParams" instead of "lgrIdxsInvalid"

The request specifies a ledger_index_max that is before the ledger_index_min.
Expected response:lgrIdxsInvalid
Actual response: invalidParams
Sample request:
{    "method": "account_tx",    "params": [        {            "account": "r4s7P9WUU6AZ9DB315GWKtBaaDji9Zst8h",            "binary": false,            "forward": false,            "ledger_index_max": 21085176,            "ledger_index_min": -1        }    ] }

“account_tx” with Either the request specifies a ledger_index_max that is before the ledger_index_min, and the server does not have a validated ledger range because it is not synced with the network.
Expected response: lgrIdxsInvalid
Actual response: invalidParams
Sample request:
{    "method": "account_tx",    "params": [        {            "account": "r4s7P9WUU6AZ9DB315GWKtBaaDji9Zst8h",            "binary": false,            "forward": false,            "ledger_index_max": 19399132,            "ledger_index_min": -1        }    ] }

as of 29f1f860d860433913278784a5361379e8cc69a4
"method": "account_tx", "params": [{"account": "rhYtqWeTaAiMv8qTnke98HsTxy9XZBdp5X", "binary": false, "forward": false, "ledger_index_ma
x": 21085176, "ledger_index_min": -1, "Fee": "20"}]}'

returns lgrIdxMalformed and the error_messages are different:
rippled: "Ledger indexes invalid."
clio: ledgerSeqMaxOutOfRange
{"result":{"error":"lgrIdxMalformed","error_code":58,"error_message":"ledgerSeqMaxOutOfRange","status":"error","type":"response","request":{"method":"account_tx","params":[{"account":"rhYtqWeTaAiMv8qTnke98HsTxy9XZBdp5X","binary":false,"forward":false,"ledger_index_max":21085176,"ledger_index_min":-1,"Fee":"20"}]}},"warnings":[{"id":2001,"message":"This is a clio server. clio only serves validated data. If you want to talk to rippled, include 'ledger_index':'current' in your request"}]}

@officialfrancismendoza looks like all we need to do is remove "ledgerSeqMaxOutOfRange" in RPCHelpers.cpp.

@legleux Ok, so apparently the response from rippled is completely different from clio atm.:
"error": "lgrIdxsInvalid",
"error_code": 57,
"error_message": "Ledger indexes invalid.",

@officialfrancismendoza Let's use rpcLGR_IDXS_INVALID without custom message instead so we get exactly what rippled responds with.


Download of user comments

Checklist

[X] I'm requesting a feature unrelated to a specific site
[X] I've looked through the README
[X] I've verified that I'm running yt-dlp version 2022.06.29 (update instructions) or later (specify commit)
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
I would like yt-dlp to download user comments and discussions related to the downloaded videos.
https://youtubecommentsdownloader.com/ is an example of one way of doing this.
Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

Continue conversation in #4285 if u need to. Opening a new issue doesnt change the fact that comments are already being extracted!


Bring back Ledger

@kcole16 @Patrick1904 merging this as is for now as need to enable Ledger's review process.


feat(snapshot): LEP for Snapshot Checksum Calculation and Bit Rot Detection

Longhorn 4210
Longhorn 3198
Signed-off-by: Derek Su<EMAIL_ADDRESS>

@PhanLe1010
The feature willl resync snapshots periodically. Do you have any concern for the resync and the period?

I think SnapshotDataIntegrityInterval might not be user-friendly.
If we use SnapshotDataIntegrityCron instead, users can specify the off-peak time for hashing/verifying snapshots. WDYT? @shuo-wu @innobead

I think SnapshotDataIntegrityInterval might not be user-friendly. If we use SnapshotDataIntegrityCron instead, users can specify the off-peak time for hashing/verifying snapshots. WDYT? @shuo-wu @innobead

Good idea! It's nice to have this feature!

I think SnapshotDataIntegrityInterval might not be user-friendly. If we use SnapshotDataIntegrityCron instead, users can specify the off-peak time for hashing/verifying snapshots. WDYT? @shuo-wu @innobead

Do you mean users could have more control to decide how often or frequently to run those operations? If YES, would we have any validation to avoid too aggressive execution? I assume we will do the same for interval if still using SnapshotDataIntegrityInterval.

I think SnapshotDataIntegrityInterval might not be user-friendly. If we use SnapshotDataIntegrityCron instead, users can specify the off-peak time for hashing/verifying snapshots. WDYT? @shuo-wu @innobead

Do you mean users could have more control to decide how often or frequently to run those operations?

Yes, for exmaple, set 0 0 * * SUN for one execution at 00:00 on Sunday.

If YES, would we have any validation to avoid too aggressive execution?

If the previous verification is not finished yet, the new job won't start. Then, we can avoid the aggressive execution.

I assume we will do the same for interval if still using SnapshotDataIntegrityInterval.

Yes,. But users have to calculate the interval and set the value at a specific moment, then the next job can run at the next desired moment. I think it is not friendly and intuitive enough.

@derekbit then, LGTM

Please help review again. Thank you.
cc @shuo-wu @c3y1huang @innobead @joshimoo

Add volume.spec.snapshotDataIntegrity. The value can be global, disabled, enabled and fast-check.
global means the setting will following the value in the global setting snapshot-data-integrity.
@innobead

The enum of value should be ignored, enabled, disabled, and fast-check.


adds missing index.html file from jsoncanvas.org

this is only a curl pull from the jsoncanvas.org website as the index.html file seemed to be missing from the repository

The index file is automatically generated by Jekyll


updating the holopin.yml to use the sdk badge by default

Description
updating the holopin.yml to use the sdk badge by default
Issue reference
#1032
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[x] Extended the documentation

@mukundansundar any idea why some builds failed? In case the errors are transient, could you re-run them?

@holopin-bot @ecabrerar Enjoy the Dapr SDK badge!


DistilBert gs demo benchmarking

GS e2e Demo
test uses batched real inputs and produces batched outputs
this test is looped (takes several batches of inputs, produces several batches of outputs)
test evaluates results of TT model against validation data in selected data set
test is documented
how to run test (commands to execute)
what does the model do (high-level explanation in a couple of sentences)
description of what is input and what is output
this demo should load inputs and expected outputs from a data set on Weka (TBD which one)

This commit contains benchmarking of Distilbert for Question and Answering using SQUAD dataset.

Exact Match : 62.0
F1 Score : 74.24285714285713

Corresponding commit - commit

Distilbert GS demo Benchmarking is completed and it is merged with mail. All the CI tests passed.


Autofocus wrong prop type

Just started using this library and I am seeing this error in the console. It's not present in 3.1.0
[Vue warn]: Invalid prop: type check failed for prop "autofocus". Expected String, got Boolean with value false.

Should the prop type be Boolean rather than String?

Thanks @palfaro91, it's fixed in v3.2.1.


[QHC-32] QDevil QDAC-II

Hello. You may have forgotten to update the changelog!
Please edit changelog-dev.md with:

A one-to-two sentence description of the change. You may include a small working example for new features.
A link back to this PR.


Possibly Feature Request: track for tag

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

Expected Behaviour

Looking for a way to annotation an activity in a video (say somebody doing jumping jacks) so that by the end I have an annotation that says Person started jumping jacks at 0:35 and finished jumping jacks at 0:37
possible have a track option for tag.
Current Behaviour

Currently using bounding box (although could have used any of the other drawing options.
Possible Solution

Possible idea, is to allow tag with tracking option?
Context

Having to draw an object to track an activity which sometimes doesn't need spacial information can cause an annotator to use unnecessary time trying to annotate. If annotators goal is just finding start and stop time for activity, they should have the ability to focus on that only.
Your Environment
unedited docker-compose up

Hi @hollowgalaxy , I agree. It can be useful. We have a similar issue on github: https://github.com/opencv/cvat/issues/1228


How to assign young Modulus for material in mfem example 2?

Hello there,
  How can I assign young modulus to mfem example 2 material.

I have a seperate ex2.cpp which I have modified to do linear elasticity analysis for a single material beam. Here is my ex2.cpp
ex2.zip
I am using this msh file with my ex2.cpp
newRefinedTestBeam.zip
Also, I wanted to clarify how I could assign a value pull force so that basically assign weight of the material and it does the linear elasticity calculation. in my ex2.cpp I wanted to be able to assign weight of beam as pullforce array value, and be able to assign young modulus depending on the type of material I am analysing.
How can I accomplish that? Maybe the way I am trying to do this is wrong. If I could get some more guidance on it it will be super helpful.

@Raghavendra0117 Do you have any insight on this?

Hi @NikhilPurbey , i am not very sure about the following answer but worth trying.
λ and μ are the material Lame constants and can be evaluated using the following formulae.
$$ \lambda = \frac {E \nu}{\left(1- 2 \nu \right) \left(1+ \nu \right)}  $$
$$ \mu = \frac{E}{2 \left( 1+ \nu \right)} $$
E = Elasticity modulus
μ = poisson ratio.
Ref:https://mfem.org/examples/.
https://en.wikipedia.org/wiki/Lam%C3%A9_parameters

Hi @Raghavendra0117,
I think you meant μ means Shear Modulus. But that was really helpful. Thanks!
I need some guidance. The results seems to be different than the calculations I actually make. This is the calculation I did.
For example, lets assume the mesh is 10m X 1m X 1m steel bar. Density of the steel is 7850kg/m^3. Young Modulus (E) = 200 * 10^9 GPa. Moment of Area is 1/12 because cross section is 1m * 1m. If I calculate the bending of steel bar under its own weight, using the formula for beam fixed between two points, using formula delta = FL^3/(192EI) I get delta as 0.0002404m.
But if I try to do same thing in the my modified ex2.cpp along with my modified mesh the delta comes as 0.0002668m. I was wondering is this normal error that I should expect? Also to get the value closer to answer I had to input the value of pullforce as Distributed load acting over the whole boundary. for example, The weight of steel bar would be mass * 9.8 = 769300. but if I add this it would give a huge value. So I figured maybe I should converted it into distributed load. Hence I divided the weight by 10 (length of the bar) and it gave me around double the correct answer. I thought maybe this is because as This force is acted on the boundary, hence it is not only acting on the upper surface but lower surface as well. Hence I did 769300/(10*2) and got 38465 as my pull force value.
The thing is I am not sure if all the assumptions I made are correct, and I am not sure if the difference in my calculation and mfem solution is acceptable, especially in the cases of structural mechanics.
Here I have attached my version of example2.cpp and the mesh file I am using.
ex2_and_msh.zip
Thanks,
Nikhil