Dependabot nuget issue with Directory.Packages.props

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
nuget
Package manager version
No response
Language version
net6.0
Manifest location and content before the Dependabot update
Directory.Packages.props
dependabot.yml content
version: 2
updates:
  - package-ecosystem: "nuget"
    directory: "/"
    schedule:
      interval: "daily"
    open-pull-requests-limit: 1
    target-branch: "main"
    labels:
      - "nuget dependencies"
      - "dependabot"
      - "minor"

Updated dependency
AutoMapper
What you expected to see, versus what you actually saw
I would expect an pr with the Automapper update, but I'm seeing:
updater | 2023/12/14 15:35:02 ERROR <job_762373268> Error processing AutoMapper (RuntimeError)
updater | 2023/12/14 15:35:02 ERROR <job_762373268> UpdateChecker found viable dependencies to be updated, but FileUpdater failed to update any files
updater | 2023/12/14 15:35:02 ERROR <job_762373268> /home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:136:in `check_and_create_pull_request'
updater | 2023/12/14 15:35:02 ERROR <job_762373268> /home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:60:in `check_and_create_pr_with_error_handling'
updater | 2023/12/14 15:35:02 ERROR <job_762373268> /home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:35:in `block in perform'
updater | 2023/12/14 15:35:02 ERROR <job_762373268> /home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:35:in `each'
updater | 2023/12/14 15:35:02 ERROR <job_762373268> /home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:35:in `perform'
updater | 2023/12/14 15:35:02 ERROR <job_762373268> /home/dependabot/dependabot-updater/lib/dependabot/updater.rb:64:in `run'
updater | 2023/12/14 15:35:02 ERROR <job_762373268> /home/dependabot/dependabot-updater/lib/dependabot/update_files_command.rb:41:in `perform_job'
updater | 2023/12/14 15:35:03 ERROR <job_762373268> /home/dependabot/dependabot-updater/lib/dependabot/base_command.rb:53:in `run'
updater | 2023/12/14 15:35:03 ERROR <job_762373268> bin/update_files.rb:24:in `<main>'
updater | 2023/12/14 15:35:03 INFO <job_762373268> Finished job processing
updater | 2023/12/14 15:35:03 INFO Results:
updater | Dependabot encountered '1' error(s) during execution, please check the logs for more details.
updater | +-------------------------------+
updater | | Dependencies failed to update |
updater | +---------------+---------------+
updater | | AutoMapper    | unknown_error |
updater | +---------------+---------------+
updater | time="2023-12-14T15:35:03Z" level=info msg="task complete" container_id=job-762373268-updater exit_code=0 job_id=762373268 step=updater

Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
https://github.com/jenivial/net-dependabot-test
Smallest manifest that reproduces the issue
No response

I have being testing this, first time with dependabot and I have found that this is failing on /dependabot/common/lib/dependabot/pull_request_creator/message_builder.rb
It seems that it is passing a files array empty and since it is making an first it fails.
      def pr_name_directory
        return "" if files.first.directory == "/"

        " in #{files.first.directory}"
      end

I will try to make a pr, but if someone with more experience takes this it would be great since I'm actually not sure were this files should be passed.

same error here (https://github.com/jhipster/jhipster-dotnetcore/network/updates/766570175) :

updater | 2023/12/26 12:02:17 INFO <job_766570175> Updating Microsoft.AspNetCore.Components.Authorization, Microsoft.AspNetCore.Components, Microsoft.AspNetCore.Components.WebAssembly, System.Text.Json, Microsoft.AspNetCore.Components.WebAssembly.DevServer, Microsoft.AspNetCore.Components.WebAssembly.Server, Microsoft.AspNetCore.SpaServices.Extensions, Microsoft.AspNetCore.Mvc.NewtonsoftJson, Microsoft.AspNetCore.Authentication.JwtBearer, System.IdentityModel.Tokens.Jwt, Microsoft.AspNetCore.Authentication.OpenIdConnect, Microsoft.AspNetCore.Mvc.Testing
updater | 2023/12/26 12:02:17 INFO <job_766570175> Sending event dcc0fa22990449fab6b200e400edf2f1 to Sentry
  proxy | 2023/12/26 12:02:17 [080] POST https://sentry.io:443/api/1451818/store/
  proxy | 2023/12/26 12:02:17 [080] 200 https://sentry.io:443/api/1451818/store/
updater | 2023/12/26 12:02:17 ERROR <job_766570175> Error processing Microsoft.AspNetCore.Authentication.OpenIdConnect (RuntimeError)
updater | 2023/12/26 12:02:17 ERROR <job_766570175> UpdateChecker found viable dependencies to be updated, but FileUpdater failed to update any files
updater | 2023/12/26 12:02:17 ERROR <job_766570175> /home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:136:in `check_and_create_pull_request'
updater | 2023/12/26 12:02:17 ERROR <job_766570175> /home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:60:in `check_and_create_pr_with_error_handling'
updater | 2023/12/26 12:02:17 ERROR <job_766570175> /home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:35:in `block in perform'
updater | 2023/12/26 12:02:17 ERROR <job_766570175> /home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:35:in `each'
updater | 2023/12/26 12:02:17 ERROR <job_766570175> /home/dependabot/dependabot-updater/lib/dependabot/updater/operations/update_all_versions.rb:35:in `perform'
updater | 2023/12/26 12:02:17 ERROR <job_766570175> /home/dependabot/dependabot-updater/lib/dependabot/updater.rb:64:in `run'
updater | 2023/12/26 12:02:17 ERROR <job_766570175> /home/dependabot/dependabot-updater/lib/dependabot/update_files_command.rb:43:in `perform_job'
updater | 2023/12/26 12:02:17 ERROR <job_766570175> /home/dependabot/dependabot-updater/lib/dependabot/base_command.rb:53:in `run'
updater | 2023/12/26 12:02:17 ERROR <job_766570175> bin/update_files.rb:24:in `<main>'
updater | 2023/12/26 12:02:17 INFO <job_766570175> Checking if Microsoft.AspNetCore.Authentication.JwtBearer 7.0.4 needs updating

Looks like this is also what's breaking dependabot on all my projects, for example: https://github.com/Zastai/MetaBrainz.MusicBrainz.CoverArt/network/updates/767826561:
updater | /opt/nuget/NuGetUpdater/NuGetUpdater.Cli update --repo-root /home/dependabot/dependabot-updater/repo --solution-or-project /home/dependabot/dependabot-updater/repo/MetaBrainz.MusicBrainz.CoverArt/MetaBrainz.MusicBrainz.CoverArt.csproj --dependency MetaBrainz.Common.Json --new-version 6.0.1 --previous-version 6.0.0  --verbose
...
updater |   No global.json files found.
updater |   No dotnet-tools.json files found.
updater | Running for project [/home/dependabot/dependabot-updater/repo/MetaBrainz.MusicBrainz.CoverArt/MetaBrainz.MusicBrainz.CoverArt.csproj]
updater |   Running for SDK-style project
updater |     Package [MetaBrainz.Common.Json] Does not exist as a dependency in [/home/dependabot/dependabot-updater/repo/MetaBrainz.MusicBrainz.CoverArt/MetaBrainz.MusicBrainz.CoverArt.csproj].
updater | Update complete.
...
updater | 2023/12/29 18:39:16 ERROR <job_767826561> Error processing MetaBrainz.Common.Json (RuntimeError)
updater | 2023/12/29 18:39:16 ERROR <job_767826561> UpdateChecker found viable dependencies to be updated, but FileUpdater failed to update any files
...

updater | 2023/12/29 18:39:17 INFO <job_767826561> Finished job processing
updater | 2023/12/29 18:39:17 INFO Results:
updater | Dependabot encountered '1' error(s) during execution, please check the logs for more details.
updater | +----------------------------------------+
updater | |     Dependencies failed to update      |
updater | +------------------------+---------------+
updater | | MetaBrainz.Common.Json | unknown_error |
updater | +------------------------+---------------+

Now, it is correct that the csproj does not itself contain an updatable reference - but the process should also be looking in any files it includes, implicitly or explicitly - or at the very least, in Directory.Packages.props.
Wasn't the updating previously done using Ruby, just like the scanning is/was? Perhaps there should have been a better spread of test cases for the new implementation...

Also ran into this in a project where the PackageReference is in a .cproj (a project file for a custom MSBuild SDK of mine, which Dependabot understandably does not support). But the PackageVersion is in Directory.Packages.props, so it should still be able to work.

There have been some pretty big changes come through the NuGet updater recently, is this an issue that people are still seeing?

Small note though: there seems to be an excessive reliance on the ManagePackageVersionsCentrally property.
If it's present (and set to true), then Directory.Packages.props appears in its own DirectoryPackagesProps section in the JSON info in the log.
If it's not present, Directory.Packages.props appears under the Projects section.
So its contents do seem to get processed either way.
However, the presence of Directory.Packages.props defaults ManagePackageVersionsCentrally to true, so it's unclear to me why it's picked up differently in that case.
Note: I have not checked what happens when the props file is present, but ManagePackageVersionsCentrally is explicitly set to false. My expectation is that the .NET SDK will not use its contents.
Now as long as Dependabot does the right thing in these circumstances, it doesn't really matter what section of the JSON a file is in; it's just something that stood out.


0.14.0 issue in createResolveable?

Working on upgrading a project I have in progress to latest Deno and library versions. What was working fine earlier (sadly I do not recall the Deno version), is now not compiling, and I do not think I am the cause (though I will admit to not being a Typescript expert by any stretch!!)
Deno version is:
deno 1.6.2 (release, x86_64-apple-darwin)
v8 8.8.278.2
typescript 4.1.3
The error trace is:
error: TS2322 [ERROR]: Type '(value: T | PromiseLike) => void' is not assignable to type '(value?: T | PromiseLike | Promise | undefined) => void'.
Types of parameters 'value' and 'value' are incompatible.
Type 'T | PromiseLike | Promise | undefined' is not assignable to type 'T | PromiseLike'.
Type 'undefined' is not assignable to type 'T | PromiseLike'.
resolveFun = resolve;
~~~~~~~~~~
at https://deno.land/x/amqp@v0.14.0/src/resolvable.ts:13:5

Grabbing master and running deno test src/   produces the very same error:
$ deno test src/
Check /amqp/$deno$test.ts
error: TS2322 [ERROR]: Type '(value: T | PromiseLike) => void' is not assignable to type '(value?: T | PromiseLike | Promise | undefined) => void'.
Types of parameters 'value' and 'value' are incompatible.
Type 'T | PromiseLike | Promise | undefined' is not assignable to type 'T | PromiseLike'.
Type 'undefined' is not assignable to type 'T | PromiseLike'.
resolveFun = resolve;
~~~~~~~~~~
at /amqp/src/resolvable.ts:13:5

Created PR https://github.com/lenkan/deno-amqp/pull/18 to potentially fix this. CI build failed but not due to my deleted character.


[🚀] Change issue template to what I would use

🚀 Feature Request
Generally, the issue templates are quite general now.
Think about and implement issue templates I would use in projects

Superseded by #10


Responsive image sizes

We need to be using picture and src set to be serving bigger and smaller images depending on device screen size.

Completed this as part of Svelte rewrite and image hosting implementation.


Restrict maxZoom of the static-image example

Upscaling the image to zoom levels > 8 does not make sense, and it may even cause canvas transformations to fail.
Fixes #4274.
Fixes #3712.

LGTM


Performance optimization concerning huge pages

Hello,
first of all: thanks a lot for this nice swiper! I'm currently using it for about 20 pages, each of the pages being quite big. Is there any way to optimize the rendering (e.g. render only some pages next to the currently active page), as the initial loading is taking about 3 seconds in my case at the moment.
Regards
Philipp

I'm having a similar issue with large-ish image per page with 100 pages.

#35 is the same. i'm also having these problems.

duplicate track in #35


Not prompt me to pick what package manager to use everytime im copying the command

Describe the feature
The gesture is nice, but it gets annoying and I've mistakenly pasted the same thing in the command line multiple times because I thought that I had copied it but in reality, it still wants me to pick the package manager. How often does one switch what package manager you want to use?
Ask me once, remember, and have the option to change below the code block would be my suggestion.

I'd love to fix this! In fact, I was just thinking about suggesting it myself. I think using cookies should definitely work for this, and I'm happy to make a pull request to implement it.

All you! @Michael-Obele could probably use a svelte-persisted-store for this

I've made a PR, and I'd love comments on the chosen implementation and design choice.

I made a new PR: Implemented the suggestions using the Stripes UI and added svelte-persisted-store (missed it last time).

Very cool @Michael-Obele!
This is basically exactly how I imagined it, although I had two thoughts:

Design: maybe that wasn't the proposed final design, but it sticks out a little bit, especially with the border, and I think it should be a bit more muted.

The command text: currently it's always showing the npm command, but wouldn't it be better if it was showing the command that is the users preferred package manager. So many times, even though there is a copy button, I find myself just selecting the text in the code block and copying, but maybe it's just me.

Those are just my two cents, but functionality wise this solves the problem I was facing when I first presented the idea.
So good job :)

Thanks, @tryggs. The first point is very valid; I'll change the code to make the border a little more mutted. The second point is also an excellent idea, but I'm hesitant about implementing it because I still believe it falls outside the scope of the main issue. I'll be making some adjustments to include the first (and hopefully the second) suggestion.
Thank you for your time reviewing this.

That is very true @Michael-Obele

@tryggs and @huntabyte I have made the recommended changes; please check it out and tell me what you think.
FYI: I didn't implement the second suggestion; it'll be best to open a different issue for it, and if it is approved, we can work towards implementing it.

@Michael-Obele As I said before, I'm not used to the whole open-source workflow so this is on me, but where can I see the changes you made?

@Michael-Obele As I said before, I'm not used to the whole open-source workflow so this is on me, but where can I see the changes you made?

That's perfectly okay.
In the PR I created, look for 'Files Changed.' From there, you can either click 'Review in CodeSpace' or go to 'Code > Codespace > Create Codespace. You will need to cd into sites/docs, and from there you should be able to run pnpm i and pnpm dev and the rest should be easy.

@Michael-Obele As I said before, I'm not used to the whole open-source workflow so this is on me, but where can I see the changes you made?

That's perfectly okay. In the PR I created, look for 'Files Changed.' From there, you can either click 'Review in CodeSpace' or go to 'Code > Codespace > Create Codespace. You will need to cd into sites/docs, and from there you should be able to run pnpm i and pnpm dev and the rest should be easy.

Thank you for that little guide, very helpful :)
If @huntabyte approves the design I think that everything is working exactly like it should. However, if I may be a little annoying I'd say that the text in the select box should be either thinner, muted, smaller, or all, but that is not the important thing!
I believe that the command in the code block should* be whatever package manager that is selected, but that is something that absolutely can wait and be dealt with separately, to as you said avoid falling outside the scope of the current issue.
But I would say that it is ready!


how to use on linux vm/chrome os

Your .zip won't work with Chrome OS because it's an incompatible file type, even using the linux vm. Please try to make this compatible with Chrome OS. Thx

It currently only works for windows anyway, so if you want to try fixing it for linux, go ahead. The problem is the file path for chromedriver. All you have to do is switch out C;/Perflogs/chromedriver.exe for whatever works. I'm not gonna invest too much time in it at this point, because I don't even have a working linux pc at the moment, so I'm either gonna have to set up a vm or fix it, which I also don't have time for. Good luck!


Method cards in User doesn't show all cards for user_id

Hi, I am using the Pay-In method in my application but when I want to create a new card and to pay with it, the payment is done but the card isn't registrated for the user. Then if I search with the console to find the user_id for the card of the transaction made before, I find the good one. When I do : MangoPay::User.cards(user_id), it doesn't give me the last card used for that transaction... Do you have any idea?

It was the default pagination.. my bad


SPI suspend not handled in blocking mode Receive

Hi,
After having trouble to receive big packet through SPI using HAL_SPI_Receive (clock @12MHz), I enabled the SPI_MASTER_RX_AUTOSUSP_ENABLE feature to avoid overflow.
But, now, i have another issue due to the fact this feature is not handled in the blocking form of Receive..
I know we should use DMA.
For whatever reason, the dev could wants to use the blocking version, which is almost not usable as is at high SPI frequencies (caused by other tasks/IRQ premption, or even slow CPU speeds)
So, it could be also good to add the SUSP bit clear in the blocking receive function too..
This way user is free to use DMA, IT or blocking receive functions

Hello @rickou,
Thank you for the report.
In fact, this enhancement has already detected and implemented internally, and it will be available ASAP within the driver.
With regards,

ST Internal Reference: 167877

Fixed in commit: https://github.com/STMicroelectronics/stm32u5xx-hal-driver/commit/5f3b1924e386eb80963e1a8ec382ad08902e2a0d


Add Wagtail 6 support + extra way to create a sharing link

This changeset adds support for Wagtail 6, with which the current version of wagtaildraftsharing does not work, because of changes to the History view and the switch of some parts of the UI to use Stimulus JS. It also expands the functionality of the app to make it more user-friendly in terms of generating a sharing link.
(Don't worry too much if this is not a familiar project to you - the testing section below should cover it.)
Wagtail 6 support
This changeset mirrors the current functionality for Wagtail 5 in Wagtail 6 by creating a Stimulus JS controller and hooking it into Wagtail in a similar way as done for Wagtail 5.
For the page history view, the HTML templating in Wagtail 6 is different and DOMContentLoaded is no longer a reliable event for attaching custom behaviour to the page. The previous approach overrode wagtailadmin/pages/revisions/_actions.html to slot in custom markup with JS touchpoints. For Wagtail 6 we do something similar, extending wagtailadmin/generic/history/action_cell.html and mark it up in a way that suits a Stimulus controller. This change remains in the mode/spirit of the project while moving in the direction of Wagtail's UI improvements.
Existing sharing links are registered by wagtaildraftsharing as Snippets, and these remain browsable via a dedicated view. This changeset updates the HTML output for the share_url method to hook in the new Stimulus controller. The change is only applicable to Wagtail 6, and the code remains the same for versions below 6.
The JS in the new Stimulus controller is deliberately very similar to the original JS. I wondered about refactoring into a shared module the main duplicated code. However, for now - and with a view potentially to deprecating pre-Wagtail 6 behaviour - I've gone with some repetition rather than DRY code.
Note that we don't load both JS files into the browser - we only load the appropriate JS file based on the version of Wagtail in use.
New functionality
This changeset also adds a new button to the Action Menu (the green combo button/menu thing at the bottom of the page when editing). If the page has a unpublished draft saved, clicking the option will generate a new sharing URL and copy it to the clipboard - just the same as doing it from the history view, but from this place, too. If the page has no unpublished draft, the button is not shown.
Testing

You'll need a project that's using wagtaildraftsharing. (If that means Bedrock - see setup instructions in https://github.com/mozilla/bedrock/pull/15232 then come back here]. install this branch's code into the active virtualenv for your projeect wtih pip install -U -e git+https://github.com/mozmeao/wagtaildraftsharing.git@add-wagtail-6-support#egg=wagtaildraftsharing

Edit a page in your site in a way you'll easily notice and save the changes as a Draft.

Go to the history view of the page

Pick a revision (e.g. the latest one) and click the three-dots menu, then click on 'Copy external sharing URL' - you'll see it change to 'Copied' then back to the original text.

You've made a 'draft sharing link' and your clipboard now contains a URL - paste that into a new tab, to confirm it shows you the draft you generated a link to

Try the same in a private tab to prove that the page works without CMS authentication

All sharing links are discoverable via the CMS admin - go to the Draftsharing links panel in the sidebar:

You'll see the sharing link you just made

You can edit this link here like a regular Django model, including changing its expiry or deleting it - but don't delete it yet.

Clear/flush/put something different in your clipboard buffer. Now click the 'Copy' button for the "Share URL" - this will put the sharing link back into your buffer - a handy way to get an existing sharing link

You can also make new sharing links from the main edit page.  Afterwards, use the 'Create draft sharing links` button in the action menu to create a new sharing link.

Verify that the new link is also listed in the main list of sharing links (step 7)

Return to your test page and publish it, so that there is no unpublished draft for the page. Confirm that the action menu now no longer contains the option to link to a draft.

Pinging @alexgibson for an early review, both of the code and also the general UX/behaviour

cc @KIRA009 - Hi Shohan! Just to keep you in the loop, this is the core of the changes I'm making. I'll be adding more tests etc and would happily submit this branch as a PR for the main project if you want it

Thanks for the review and test drive @alexgibson. A high-level look-over the JS was all I was expecting yeah, as Stimulus is new to both of us, but also we're just dipping a toe in, really

@KIRA009 This is ready for a review if you wish

@robhudson If you could give this a further look over, that'd be great. Thanks!


Comparing two opening hours strings

Is it possible to use this library to compare whether two opening hours strings have effectively the same meaning?
I wanted to use this for import verification/checking but it seems that it would be impossible - there is oh.intervals() but it would not help as iterating over infinite iterator has obvious problems.
Is it possible to generate canonical form already? Or add functionality to do this?

That certainly sound like an interesting feature.
Is there already some kind of specification for a canonical form?

AFAIK not really, it is mostly matter of taste :(
maybe it would be possible to expose parsed structure of opening hours? Not just infinite oh.intervals()? (or maybe it is accessible somehow and I have not figured out how?)

With 0.8.0 OpeningHours implements __eq__ (and __hash__ btw) which should help to identify very basic variations of the same expressions. I might spent time improving this but any suggestion is welcome, maybe we should close this issue and create new issues if any suggestion comes to your mind?
There is now also a __str__ if you prefer to work with strings.
Also, exposing the parsed AST would require its own issue, I'm not super into it if you don't specifically need it. It would require a wrapper for most Python types which is not trivial as there are many algebraic types involved. Although, note that the Rust core does expose the AST in a small parsing crate : https://docs.rs/opening-hours-syntax/0.8.0/opening_hours_syntax/

I'm closing this issue, I'd recommend something like str(OpeningHours(expr_1)) == str(OpeningHours(expr_2)).
For any issue are suggestion for rules in this feature, issues are welcome.


Update docs in Bamboo.Phoenix

After looking through this I think "template" might be the more correct word here

LGTM

Thanks for the review!


Track memory usage of tasks

In order to better design future tasks, it would be useful to have information on total/mean/peak memory usage. Thanks!

Completed a while back. The jobs page now shows a CPU and MEM utilization plot for the duration of the run.


Meetup Suggestion: Example Bitcoin Meetup

Thanks for making a suggestion for a new meetup.
Please note: Only suggest bitcoin-only meetups.
Meetups which promote any coin or token other than Bitcoin are not suitable for listing.
Altcoin's are only mentioned in the context of warnings or lessons learnt for bitcoin.
Required:

Name of Meetup: Pleb Say
Location Of Meetup: El Camino San Antonio Texas
At least one of the following:

Meetup Page (or similar): https://www.meetup.com/sanantoniobitcoinclub/
Telegram Group (or similar): San Antonio Bitcoin Club
Website: sanantoniobitcoinclub.com

Optional

Name of Organiser(s) & Twitter Handle: @SABTCclub
Links showing public support: >>>  example
Tweet your commitment

As the organiser of [>>>XXX<<<] Meetup I can confirm that the meetup is bitcoin-only
-The meetup is bitcoin focused.
-'Altcoins' are scams and are not promoted in talks/presentations at our meetups.
#bitcoinonlymeetups @bitcoinonly_

Thanks Merged


Page.goto response is null on some websites when using request interception

Steps to reproduce
Tell us about your environment:

Puppeteer version: 6.0.0-8.0.0 (tried several, but this was a problem on older versions too)
Platform / OS version: MacOS 11.2, Alpine/Debian Linux inside Docker
Node.js version: 14.x-15.x, tried several

What steps will reproduce the problem?
Use the following class (typescript) create an instance, call the start method and observe the log.
export class Crawler {

    public _browser: puppeteer.Browser;

    public async start(): Promise<void> {
        this._browser = await puppeteer.launch();

        for(var i=0; i<10; i++) {
            var response = await this.openPage('customer-user-agent', 'https://www.lights.ie/ceiling-lights/');
            this.logResult(response);
        }
    }

    public async openPage(userAgent: string, url: string): Promise<puppeteer.HTTPResponse> {
        const page: puppeteer.Page = await this._browser.newPage();
        await Promise.all([page.setUserAgent(userAgent), page.setViewport(VIEWPORT), page.setRequestInterception(true)]);

        page.on('request', (request: puppeteer.HTTPRequest) => request.continue());

        var response = await page.goto(url, {
            timeout: 60000,
            waitUntil: []
        });

        await page.waitForTimeout(5000);
        await page.close();

        return response;
    }

    private logResult(response: puppeteer.HTTPResponse) {
        if (response == null) {
            console.dir('Failure getting response');
        } else {
            console.dir('Successfully navigated to website');
        }
        return response;
    }
}

First of all, this does not seem to appear with all websites. It also seems that sometimes you can open the same URL twice or thrice before the error appears. But once it appears, it never goes away until you restart the browser. My best guess is a caching issue, but I couldn't find the problem. Without the page.waitForTimeout, the issue also doesn't seem to occur.
What is the expected result?
I should be able to receive the initial response the server sends.
What happens instead?
The response is null. I need both the final URL (after potential redirects) as well as the status code and in some cases the body of the initial response.

Same issue with Node16, Puppeteer10, Windows10
against url
original dynamic url
which transforms into :
redirected url
what solution to apply to page.goTo ?


Replace NetworkSettings and GetSendInterval with NetworkBehaviour.syncInterval

Codecov Report

Merging #202 into master will increase coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master    #202      +/-   ##
=========================================
+ Coverage    6.94%   6.94%   +<.01%
=========================================
  Files          29      29
  Lines        5934    5914      -20
  Branches      830     828       -2
=========================================
- Hits          412     411       -1
+ Misses       5509    5489      -20
- Partials       13      14       +1

Impacted Files
Coverage Δ

Mirror/Runtime/CustomAttributes.cs
0% <ø> (ø)
:arrow_up:

Mirror/Runtime/NetworkTransform.cs
0% <0%> (ø)
:arrow_up:

Mirror/Runtime/NetworkAnimator.cs
0% <0%> (ø)
:arrow_up:

Mirror/Runtime/NetworkTransformChild.cs
0% <0%> (ø)
:arrow_up:

Mirror/Runtime/NetworkBehaviour.cs
0% <0%> (ø)
:arrow_up:

Mirror/Runtime/SyncList.cs
83.26% <0%> (-0.43%)
:arrow_down:

Continue to review full report at Codecov.

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

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Integrate Pipeline Parser into FOSCommentBundle

It's good idea to integrate functionality for pipeline parsing that I did in this bundle:
https://github.com/smilesrg/PipelineParserBundle

I think the parser bundle you wrote looks interesting. How about you suggest a PR for documentation on how to use it with FOSCommentBundle? Or are you interested in maintaining the functionalty as part of the bundle?

I think the parser I wrote should be integrated into FOSCommentBundle. I'll create a PR as soon as I have a free time. Of course, I can maintain this functionality as a part of the bundle.

https://github.com/FriendsOfSymfony/FOSCommentBundle/pull/579

@tarjei please look at my PR

#606

Merged, thanks!


Error generating when token not provided (version 0.1.27)

I have this error when i start my project with the latest version (0.1.27).
I found this line was the cause
https://github.com/Diizzayy/nuxt-graphql-client/blob/main/src/module.ts#L83
More specific v.token.type where token is undefined :)
ERROR  Cannot restart nuxt:  Cannot read properties of undefined (reading 'type')                                                                                17:15:01

  at setup (node_modules/nuxt-graphql-client/dist/module.mjs:220:76)
  at Object.normalizedModule (node_modules/@nuxt/kit/dist/index.mjs:637:29)
  at async installModule (node_modules/@nuxt/kit/dist/index.mjs:456:3)
  at async initNuxt (node_modules/nuxt/dist/index.mjs:1606:7)
  at async load (node_modules/nuxi/dist/chunks/dev.mjs:6778:9)
  at async _applyPromised (node_modules/nuxi/dist/chunks/dev.mjs:6713:10)

Thanks for your hard work

@aspitrine Thank you for pointing out this regression! An immediate fix is on the way.


[firebase_ml_vision 0.9.4] Unable to detect faces in image on real iOS device in debug or release mode - works on ios emulator

Describe the bug
The api is unable to detect a face in any image when run on a real iOS device either in debug or release mode.  Detecting faces works fine when run from an emulator.  Note that it works when run on a real Android device or Android emulator so the issue is just on real iOS devices.
I believe I have followed the installation and configuration steps outlined in the package readme which include:

Setting up a new firebase project
Adding pod 'Firebase/MLVisionFaceModel' to the pod file and running pod update after
Updated the ios target to '9.0'

Note that I was able to get the sample app in this repository to detect a face once but it would never worked again after the first time.  I tried mimicking all the settings in that project but could not get it to work via the published package.
To Reproduce
See example repository that reproduces the error (this is as simple as can possibly be)
https://github.com/jonsamwell/flutter_firebase_face_detect_ios_device_bug
Run the example project on a real iOS device and try and detect a face from a gallery or camera image. (Note the example app just allow picking an image from the gallery)
Expected behavior
Faces are detected when run on real iOS devices
Flutter doctor
Run flutter doctor and paste the output below:
[✓] Flutter (Channel stable, v1.17.5, on Mac OS X 10.15.6 19G73, locale en-GB)
    • Flutter version 1.17.5 at /Users/jon/Documents/Development/flutter
    • Framework revision 8af6b2f038 (4 weeks ago), 2020-06-30 12:53:55 -0700
    • Engine revision ee76268252
    • Dart version 2.8.4

[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, set ANDROID_SDK_ROOT to that location.
      You may also want to add it to your PATH environment variable.

[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.6, Build version 11E708
    • CocoaPods version 1.9.3

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).

[✓] VS Code (version 1.47.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.12.2

[✓] Connected device (4 available)
    • Jon’s iPhone               • 80b49de737eca92b5d537d0e6404ccc0ad17941a • ios • iOS 13.6
    • iPhone 8                   • 0AE72832-B53B-43C5-A2E5-AC5059EE2BC0     • ios • com.apple.CoreSimulator.SimRuntime.iOS-13-6 (simulator)
    • iPhone 11                  • D86528A6-4654-44F1-A7BC-BBA645DD03FF     • ios • com.apple.CoreSimulator.SimRuntime.iOS-13-6 (simulator)
    • iPhone SE (2nd generation) • 7F7DEB7C-7C62-4AFC-9303-BA9553487C7D     • ios • com.apple.CoreSimulator.SimRuntime.iOS-13-6 (simulator)

I am also having this issue in my project. The demo build for the plugin does not work on iOS. This extends to Flutter 1.20.0-7.2.pre on the beta as well as Flutter 1.17.5 on the stable channel. I switched to the beta channel because it fixes memory leak issues for physical devices using the camera stream.
I've been messing with it for the last couple days and it seems to be exclusive to physical iOS devices.
Can you open the Runner project in XCode and add the -FIRAnalyticsDebugEnabled build flag and paste the debug output when you run the app? The barcode scanner outputs the following and I want to see if it's the same across different ML models.
2020-07-26 18:10:25.786434-0400 Runner[2918:154429] [VERBOSE-2:ui_dart_state.cc(166)] Unhandled Exception: PlatformException(Error 13, com.firebase.ml, Barcode engine is nil.)
#0      StandardMethodCodec.decodeEnvelope (package:flutter/src/services/message_codecs.dart:572:7)
#1      MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:161:18)
<asynchronous suspension>
#2      MethodChannel.invokeMethod (package:flutter/src/services/platform_channel.dart:334:12)
#3      MethodChannel.invokeListMethod (package:flutter/src/services/platform_channel.dart:347:40)
#4      BarcodeDetector.detectInImage (package:firebase_ml_vision/src/barcode_detector.dart:200:38)
#5      _CameraAppState.detect (package:phi/main.dart:524:25)
#6      _CameraAppState._setupCameras.<anonymous closure>.<anonymous closure> (package:phi/main.dart:482:9)
#7      CameraController.startImageStream.<anonymous closure> (package:camera/camera.dart:412:20)
#8      _rootRunUnary (dart:async/zone.dart:1198:47)
#9      _CustomZone.runUnary (dart:async/zone.dart:1100:19)
#10     _CustomZone.runUnaryGuarded (dart:async/zone.dart:1005:7)
#11     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:357:11)
#12     _DelayedData.perform (dart:async/stream_impl.dart:611:14)
#13     _StreamImplEvents.handleNext (dart:async/stream_impl.dart:730:11)
#14     _PendingEvents.schedule.<anonymous closure> (dart:async/stream_impl.dart:687:7)
#15     _rootRun (dart:async/zone.dart:1182:47)
#16     _CustomZone.run (dart:async/zone.dart:1093:19)
#17     _CustomZone.runGuarded (dart:async/zone.dart:997:7)
#18     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:1037:23)
#19     _rootRun (dart:async/zone.dart:1190:13)
#20     _CustomZone.run (dart:async/zone.dart:1093:19)
#21     _CustomZone.runGuarded (dart:async/zone.dart:997:7)
#22     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:1037:23)
#23     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#24     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
2020-07-26 18:10:25.859900-0400 Runner[2918:154421] 6.25.0 - [Firebase/MLKit][I-MLK006006] Barcode engine is nil.

The relevant exception being Barcode engine is nil

@breadbored thanks for the reply, output below.  I can't see anything related to the engine
2020-07-28 12:01:43.087527+1000 Runner[283:6138] Metal API Validation Enabled
2020-07-28 12:01:43.247528+1000 Runner[283:6138] Configuring the default Firebase app...
2020-07-28 12:01:43.263878+1000 Runner[283:6138] Configured the default Firebase app __FIRAPP_DEFAULT.
2020-07-28 12:01:43.337829+1000 Runner[283:6281] 6.28.0 - [Firebase/Core][I-COR000004] App with name __FIRAPP_DEFAULT does not exist.
2020-07-28 12:01:43.354661+1000 Runner[283:6299] flutter: Observatory listening on http://<IP_ADDRESS>:50048/NmGqVQLAGXQ=/
2020-07-28 12:01:43.371161+1000 Runner[283:6281] 6.28.0 - [Firebase/Installations][I-FIS002000] -[FIRInstallationsIDController createGetInstallationItemPromise], appName: __FIRAPP_DEFAULT
2020-07-28 12:01:43.371491+1000 Runner[283:6281] 6.28.0 - [GULReachability][I-REA902003] Monitoring the network status
2020-07-28 12:01:43.371817+1000 Runner[283:6281] 6.28.0 - [GULReachability][I-REA902003] Monitoring the network status
2020-07-28 12:01:43.383721+1000 Runner[283:6277] 6.28.0 - [Firebase/Analytics][I-ACS024000] Debug mode is on
2020-07-28 12:01:43.383998+1000 Runner[283:6277] 6.28.0 - [Firebase/Analytics][I-ACS005000] The AdSupport Framework is not currently linked. Some features will not function properly. Learn more at http://goo.gl/9vSsPb
2020-07-28 12:01:43.384214+1000 Runner[283:6277] 6.28.0 - [Firebase/Analytics][I-ACS031025] Analytics screen reporting is enabled. Call +[FIRAnalytics setScreenName:setScreenClass:] to set the screen name or override the default screen class name. To disable screen reporting, set the flag FirebaseScreenReportingEnabled to NO (boolean) in the Info.plist
2020-07-28 12:01:43.384950+1000 Runner[283:6277] 6.28.0 - [Firebase/Analytics][I-ACS023007] Analytics v.60602000 started
2020-07-28 12:01:43.385335+1000 Runner[283:6277] 6.28.0 - [Firebase/Analytics][I-ACS023008] To disable debug logging set the following application argument: -noFIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r)
2020-07-28 12:01:43.385821+1000 Runner[283:6277] 6.28.0 - [Firebase/Analytics][I-ACS023009] Debug logging enabled
2020-07-28 12:01:43.385878+1000 Runner[283:6277] 6.28.0 - [Firebase/Analytics][I-ACS023207] To enable verbose logging set the following application argument: -FIRAnalyticsVerboseLoggingEnabled (see http://goo.gl/RfcP7r)
2020-07-28 12:01:43.461857+1000 Runner[283:6286] 6.28.0 - [Firebase/Analytics][I-ACS002002] APMExperimentAlarm scheduled to fire in approx. (s): 9.999987006187439
2020-07-28 12:01:43.588986+1000 Runner[283:6286] 6.28.0 - [Firebase/Analytics][I-ACS800023] No pending snapshot to activate. SDK name: app_measurement
2020-07-28 12:01:43.589571+1000 Runner[283:6286] 6.28.0 - [Firebase/Analytics][I-ACS029017] Configuration was not found in database. The configuration will be fetched from the network when necessary
2020-07-28 12:01:43.589886+1000 Runner[283:6286] 6.28.0 - [Firebase/Analytics][I-ACS023016] Analytics is ready to receive events
2020-07-28 12:01:43.609960+1000 Runner[283:6277] 6.28.0 - [Firebase/Analytics][I-ACS032003] iAd framework is not linked. Search Ad Attribution Reporter is disabled.
2020-07-28 12:01:43.612019+1000 Runner[283:6283] 6.28.0 - [Firebase/Analytics][I-ACS023012] Analytics collection enabled
2020-07-28 12:01:43.860506+1000 Runner[283:6283] 6.28.0 - [GULReachability][I-REA902004] Network status has changed. Code:1, status:Disconnected
2020-07-28 12:01:43.860844+1000 Runner[283:6283] 6.28.0 - [GULReachability][I-REA902004] Network status has changed. Code:2, status:Connected
2020-07-28 12:01:43.860974+1000 Runner[283:6283] 6.28.0 - [GoogleUtilities/AppDelegateSwizzler][I-SWZ001008] Successfully created App Delegate Proxy automatically. To disable the proxy, set the flag GoogleUtilitiesAppDelegateProxyEnabled to NO (Boolean) in the Info.plist
2020-07-28 12:01:43.861519+1000 Runner[283:6283] 6.28.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): -228.9423390626907
2020-07-28 12:01:43.861671+1000 Runner[283:6283] 6.28.0 - [Firebase/Analytics][I-ACS002001] Measurement timer fired
2020-07-28 12:01:43.862015+1000 Runner[283:6283] 6.28.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2020-07-28 12:01:43.942715+1000 Runner[283:6283] 6.28.0 - [Firebase/Analytics][I-ACS900001] Downloading data. Host: https://app-measurement.com/config/app/1:820162923558:ios:3fad3422217aecd4c06ae7?platform=ios&app_instance_id=500D16F5539740EE98C6E8AB4C0A2B09&gmp_version=60602
2020-07-28 12:01:44.519105+1000 Runner[283:6283] 6.28.0 - [Firebase/Installations][I-FIS002001] -[FIRInstallationsIDController installationWithValidAuthTokenForcingRefresh:0], appName: __FIRAPP_DEFAULT
2020-07-28 12:01:44.519579+1000 Runner[283:6283] 6.28.0 - [Firebase/Analytics][I-ACS002002] Engagement timer scheduled to fire in approx. (s): 3600
2020-07-28 12:01:44.521471+1000 Runner[283:6283] 6.28.0 - [Firebase/Analytics][I-ACS901006] Received SSL challenge for host. Host: https://app-measurement.com/config/app/1:820162923558:ios:3fad3422217aecd4c06ae7?platform=ios&app_instance_id=500D16F5539740EE98C6E8AB4C0A2B09&gmp_version=60602
2020-07-28 12:01:44.524029+1000 Runner[283:6283] 6.28.0 - [Firebase/Analytics][I-ACS031010] Tracking view controller. Class, ID: FlutterViewController, -4535294027302068888
2020-07-28 12:01:44.524479+1000 Runner[283:6283] 6.28.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -4535294027302068888
2020-07-28 12:01:44.524783+1000 Runner[283:6283] 6.28.0 - [Firebase/Installations][I-FIS001001] Sending request: <NSMutableURLRequest: 0x2835601e0> { URL: https://firebaseinstallations.googleapis.com/v1/projects/fir-face-detect-test/installations/ }, body:{"appId":"1:820162923558:ios:3fad3422217aecd4c06ae7","fid":"cFAxeHO8HUBOp1L5wbdAkh","authVersion":"FIS_v2","sdkVersion":"i:1.5.0"}, headers: {
    "Content-Type" = "application/json";
    "X-Goog-Api-Key" = "AIzaSyBPcxdyY3g_8lcuPl86ChyMBvIJZag2Jd8";
    "X-Ios-Bundle-Identifier" = "com.example.firebaseFaceTest";
    "X-firebase-client" = "apple-platform/ios apple-sdk/17G64 fire-analytics/6.6.2 fire-install/1.5.0 fire-ios/6.9.1 fire-ml-cmn/0.21.0 fire-ml-vis/0.21.0 flutter-fire-ml-vis/0.9.4 swift/true xcode/11E708";
    "X-firebase-client-log-type" = 0;
}.
2020-07-28 12:01:44.529030+1000 Runner[283:6283] 6.28.0 - [Firebase/Analytics][I-ACS023051] Logging event: origin, name, params: auto, screen_view (_vs), {
    ga_event_origin (_o) = auto;
    ga_screen_class (_sc) = FlutterViewController;
    ga_screen_id (_si) = -4535294027302068888;
}
2020-07-28 12:01:44.531456+1000 Runner[283:6283] 6.28.0 - [Firebase/Analytics][I-ACS023073] Debug mode is enabled. Marking event as debug and real-time. Event name, parameters: screen_view (_vs), {
    ga_debug (_dbg) = 1;
    ga_event_origin (_o) = auto;
    ga_realtime (_r) = 1;
    ga_screen_class (_sc) = FlutterViewController;
    ga_screen_id (_si) = -4535294027302068888;
}
2020-07-28 12:01:44.535886+1000 Runner[283:6283] 6.28.0 - [Firebase/Analytics][I-ACS023072] Event logged. Event name, event params: screen_view (_vs), {
    ga_debug (_dbg) = 1;
    ga_event_origin (_o) = auto;
    ga_realtime (_r) = 1;
    ga_screen_class (_sc) = FlutterViewController;
    ga_screen_id (_si) = -4535294027302068888;
}
2020-07-28 12:01:44.544110+1000 Runner[283:6282] 6.28.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 0.9330509901046753
2020-07-28 12:01:44.801563+1000 Runner[283:6282] 6.28.0 - [Firebase/Analytics][I-ACS023130] Configuration not found. Using default configuration
2020-07-28 12:01:44.810300+1000 Runner[283:6282] 6.28.0 - [Firebase/Analytics][I-ACS023105] Event is not subject to real-time event count daily limit. Marking an event as real-time. Event name, parameters: first_open (_f), {
    ga_conversion (_c) = 1;
    ga_event_origin (_o) = auto;
    ga_realtime (_r) = 1;
    ga_screen_class (_sc) = FlutterViewController;
    ga_screen_id (_si) =<PHONE_NUMBER>586357581;
    previous_first_open_count (_pfo) = 1;
    update_with_analytics (_uwa) = 0;
}
2020-07-28 12:01:44.815263+1000 Runner[283:6283] 6.28.0 - [Firebase/Analytics][I-ACS012018] Saving bundle. size (bytes): 381
2020-07-28 12:01:44.815346+1000 Runner[283:6283] 6.28.0 - [Firebase/Analytics][I-ACS023116] Bundle added to the upload queue. BundleID, timestamp (ms): 1,<PHONE_NUMBER>931
2020-07-28 12:01:44.824347+1000 Runner[283:6283] 6.28.0 - [Firebase/Analytics][I-ACS023105] Event is not subject to real-time event count daily limit. Marking an event as real-time. Event name, parameters: screen_view (_vs), {
    ga_debug (_dbg) = 1;
    ga_event_origin (_o) = auto;
    ga_realtime (_r) = 1;
    ga_screen_class (_sc) = FlutterViewController;
    ga_screen_id (_si) =<PHONE_NUMBER>20402813;
}
2020-07-28 12:01:44.826121+1000 Runner[283:6282] 6.28.0 - [Firebase/Analytics][I-ACS023087] User property set. Name, value: lifetime_user_engagement (_lte), 259475
2020-07-28 12:01:44.826379+1000 Runner[283:6282] 6.28.0 - [Firebase/Analytics][I-ACS023087] User property set. Name, value: session_user_engagement (_se), 259475
2020-07-28 12:01:44.828520+1000 Runner[283:6282] 6.28.0 - [Firebase/Analytics][I-ACS012018] Saving bundle. size (bytes): 565
2020-07-28 12:01:44.828670+1000 Runner[283:6282] 6.28.0 - [Firebase/Analytics][I-ACS023116] Bundle added to the upload queue. BundleID, timestamp (ms): 2,<PHONE_NUMBER>917
2020-07-28 12:01:44.838848+1000 Runner[283:6282] 6.28.0 - [Firebase/Analytics][I-ACS023105] Event is not subject to real-time event count daily limit. Marking an event as real-time. Event name, parameters: screen_view (_vs), {
    ga_debug (_dbg) = 1;
    ga_event_origin (_o) = auto;
    ga_realtime (_r) = 1;
    ga_screen_class (_sc) = FlutterViewController;
    ga_screen_id (_si) = -4535294027302068888;
}
2020-07-28 12:01:44.842129+1000 Runner[283:6282] 6.28.0 - [Firebase/Analytics][I-ACS012018] Saving bundle. size (bytes): 424
2020-07-28 12:01:44.842175+1000 Runner[283:6282] 6.28.0 - [Firebase/Analytics][I-ACS023116] Bundle added to the upload queue. BundleID, timestamp (ms): 3,<PHONE_NUMBER>476
2020-07-28 12:01:44.851430+1000 Runner[283:6282] 6.28.0 - [Firebase/Analytics][I-ACS023039] Measurement data sent to network. Timestamp (ms), data:<PHONE_NUMBER>848, <APMPBMeasurementBatch: 0x283560b10>
2020-07-28 12:01:44.854459+1000 Runner[283:6284] 6.28.0 - [Firebase/Analytics][I-ACS900000] Uploading data. Host: https://app-measurement.com/a
2020-07-28 12:01:45.003725+1000 Runner[283:6283] 6.28.0 - [Firebase/Analytics][I-ACS901006] Received SSL challenge for host. Host: https://app-measurement.com/a
2020-07-28 12:01:45.202245+1000 Runner[283:6277] 6.28.0 - [Firebase/Analytics][I-ACS023044] Successful upload. Got network response. Code, size: 204, -1
2020-07-28 12:01:45.206597+1000 Runner[283:6277] 6.28.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2020-07-28 12:01:45.207051+1000 Runner[283:6277] 6.28.0 - [Firebase/Analytics][I-ACS002002] Measurement timer scheduled to fire in approx. (s): 0.26963210105896
2020-07-28 12:01:45.218542+1000 Runner[283:6277] 6.28.0 - [Firebase/Analytics][I-ACS002003] Measurement timer canceled
2020-07-28 12:01:45.569890+1000 Runner[283:6284] 6.28.0 - [Firebase/Installations][I-FIS001003] Request response received: <NSMutableURLRequest: 0x2835601e0> { URL: https://firebaseinstallations.googleapis.com/v1/projects/fir-face-detect-test/installations/ }, error: (null), body: {
  "name": "projects/820162923558/installations/cFAxeHO8HUBOp1L5wbdAkh",
  "fid": "cFAxeHO8HUBOp1L5wbdAkh",
  "refreshToken": "2_ZDr5fK6WDkq5xgDrouI5LOYbq3yfy2w97UkrAvyISOgi7e6ui0dRkTCZ9igrPEu_",
  "authToken": {
    "token": "eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJmaWQiOiJjRkF4ZUhPOEhVQk9wMUw1d2JkQWtoIiwicHJvamVjdE51bWJlciI6ODIwMTYyOTIzNTU4LCJleHAiOjE1OTY1MDY1MDUsImFwcElkIjoiMTo4MjAxNjI5MjM1NTg6aW9zOjNmYWQzNDIyMjE3YWVjZDRjMDZhZTcifQ.AB2LPV8wRQIgPDkRhOaCJ8Obv33U4qDcwgQWvF5kGVhRJhc5dPpzW8YCIQC0uemXzE_J7-NhfcSkSzprxyrjRmt0kwrtfmdFRShPBw",
    "expiresIn": "604800s"
  }
}
.
2020-07-28 12:01:45.573800+1000 Runner[283:6284] 6.28.0 - [Firebase/Installations][I-FIS001005] Parsing server response for https://firebaseinstallations.googleapis.com/v1/projects/fir-face-detect-test/installations/.
2020-07-28 12:01:45.574584+1000 Runner[283:6284] 6.28.0 - [Firebase/Installations][I-FIS001007] FIRInstallationsItem parsed successfully.
2020-07-28 12:01:50.814562+1000 Runner[283:6277] 6.28.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -4535294027302068888
2020-07-28 12:01:52.949259+1000 Runner[283:6277] [core] "Error returned from daemon: Error Domain=com.apple.accounts Code=7 "(null)""
2020-07-28 12:01:53.413 Runner[283/0x1016e1840] [lvl=3] +[FBMLx_CCTClearcutUploader crashIfNecessary] Multiple instances of CCTClearcutUploader were instantiated. Multiple uploaders function correctly but have an adverse affect on battery performance due to lock contention.
2020-07-28 12:01:53.449465+1000 Runner[283:6138] Initialized TensorFlow Lite runtime.
2020-07-28 12:01:53.462853+1000 Runner[283:6277] 6.28.0 - [Firebase/Analytics][I-ACS002001] APMExperimentAlarm fired
2020-07-28 12:01:53.509873+1000 Runner[283:6277] 6.28.0 - [Firebase/Analytics][I-ACS002003] APMExperimentAlarm canceled
2020-07-28 12:01:53.605049+1000 Runner[283:6277] 6.28.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -4535294027302068888
2020-07-28 12:01:53.605613+1000 Runner[283:6277] 6.28.0 - [Firebase/Analytics][I-ACS031006] View controller already tracked. Class, ID: FlutterViewController, -4535294027302068888
2020-07-28 12:01:54.120578+1000 Runner[283:6302] 6.28.0 - [Firebase/Analytics][I-ACS002002] APMExperimentAlarm scheduled to fire in approx. (s): 14399.98486602306

Any update on this?


引用对应错误

Do you need to file an issue?

[X] I have searched the existing issues and this bug is not already filed.
[X] My model is hosted on OpenAI or Azure. If not, please look at the "model providers" issue and don't file a new one here.
[X] I believe this is a legitimate bug, not just a question. If this is a question, please use the Discussions area.

Describe the bug
感觉References里面的id对应不上，好像应该对应Entity对象里的short_id
Entity (1) 相关回答

原代码结果

尝试修改并添加Title

Entity.title

修改结果

Steps to reproduce
No response
Expected Behavior
No response
GraphRAG Config Used
# Paste your config here

Logs and screenshots
No response
Additional Information

GraphRAG Version: v0.2.0
Operating System: Windows 11
Python Version: 3.12.4
Related Issues: References

感谢 我会详细看一下

@zczlr12 Thanks, 我已经修复了，包括其他实体或者关系的错误引用问题。若遇到其他bug，欢迎再次提交或者提PR


How can I clear cached users?

How can I clear user memory storage, fetch latest data of users and store in cache?

Hi @tranngoclinh88
We are planning to add force user update (in cache) parameter in a near future. But there is no any ETA for now.
Here is a solution for you:

Perform cache removal first:

/**
 *  Delete all users
 *
 *  @param completion Completion block that is called after the delete operation has completed.
 */
- (QB_NONNULL BFTask *)deleteAllUsers;

Nil the the loadFromCacheTask ivar in QMUsersService file:

@implementation QMUsersService {
    BFTask* loadFromCacheTask;
}

And now just load users as usual. Let me know if it works for you.

Thank @Raikerian

Hi @Raikerian
I'm getting -[NSManagedObjectContext saveToPersistentStoreAndWait]: unrecognized selector sent to instance for deleteAllUsers

Hi @yishus
Check that you have -ObjC flag in other linker flags of your project. And if that doesn't help, create a separate issue with any information you think will be helpful for us.


TypeScript training first run

What comes up at the first run of the TypeScript training?

presentation
Scoop.sh for installing NodeJS, Yarn
Git installed including Application Token or SSH key
Commit message formatting
Yarn


Consistent Documentation

Use this format to automatically create documentation: https://readthedocs.org/

I added some docstrings and a config file for Sphinx docs in #41.
the documentation is not perfect but enough to start with.  I'm closing this issue for now.


ENH: Improve association handling, send c-cancel when appropriate

Codecov Report

Merging #8 (9a5c298) into main (b3f4e4c) will decrease coverage by 0.69%.
The diff coverage is 75.32%.

@@            Coverage Diff             @@
##             main       #8      +/-   ##
==========================================
- Coverage   77.71%   77.01%   -0.70%
==========================================
  Files          25       25
  Lines        6407     6282     -125
==========================================
- Hits         4979     4838     -141
- Misses       1428     1444      +16

Impacted Files
Coverage Δ

dcm/util.py
76.64% <61.11%> (-0.51%)
:arrow_down:

dcm/cli.py
70.50% <71.42%> (-0.73%)
:arrow_down:

dcm/net.py
81.51% <77.51%> (-1.52%)
:arrow_down:

dcm/filt.py
40.70% <0.00%> (-1.43%)
:arrow_down:

dcm/store/__init__.py
68.95% <0.00%> (-1.32%)
:arrow_down:

dcm/route.py
76.57% <0.00%> (-1.04%)
:arrow_down:

dcm/store/net_repo.py
77.06% <0.00%> (-0.62%)
:arrow_down:

dcm/sync.py
81.26% <0.00%> (-0.40%)
:arrow_down:

... and 12 more

Continue to review full report at Codecov.

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


<EMAIL_ADDRESS>hash check failed

This is how the installation fails:
❯ scoop install pass-winmenu-nogpg
Installing 'pass-winmenu-nogpg' (1.13.1) [64bit] from extras bucket
Loading pass-winmenu-nogpg.zip from cache.
Checking hash of pass-winmenu-nogpg.zip ... ERROR Hash check failed!
App:         extras/pass-winmenu-nogpg
URL:         https://github.com/Baggykiin/pass-winmenu/releases/download/v1.13.1/pass-winmenu-nogpg.zip
First bytes: 50 4B 03 04 14 00 00 00
Expected:    8fe430ea26881241287237ee2f3f8573ebbea31ccafa620d14ac4c023790c6aa
Actual:      b88b07d711712986ac0367d80a60f42adf18f82693ee23df1874c91b366b1f29

Please try again or create a new issue by using the following link and paste your console output:
https://github.com/ScoopInstaller/Extras/issues/new?title=pass-winmenu-nogpg%401.13.1%3a+hash+check+failed

Scoop Configuration
{
    "aria2-warning-enabled":  false,
    "scoop_branch":  "master",
    "last_update":  "2022-10-22T15:17:23.8812307+05:30",
    "scoop_repo":  "https://github.com/lukesampson/scoop"
}

I was going to a file a PR for this but from the PR template it looked like I was expected to create an issue first.
I have updated the hash here: https://raw.githubusercontent.com/kartikynwa/ScoopExtras/bugfix-passmenu-hash/bucket/pass-winmenu-nogpg.json
Have tested by installing and running the updated template.
Let me know if this is satisfactory. I will file a PR once I get the go ahead.

Oh wow. That was pretty cool.


betterlockscreen 3.2.0 -> 4.0.0

(cherry picked from commit 2f59b54e3f1318c4e0a6079baebf621b9b402880)
Please note changes from 3.2 to 4.0 are breaking, depending on how/how intense Betterlockscreen is used. But as there are multiple fundamental bugs in v3.2 we are not able to provide fixes for this.
Motivation for this change
Backport new major release after taking-over maintenance for the project
Things done
Adjusted derivation and included all dependencies

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Also, this doesn't look like it works if i have i3lock also installed: here's a relevant bit from bin/betterlockscreen:
    if ! cmd_exists "i3lockcolor_bin" && cmd_exists "i3lock"; then
        i3lockcolor_bin="i3lock"
    fi

where I think it means to say cmd_exists "$i3lockcolor_bin... currently it's going to replace that with i3lock since no package provides i3lockcolor_bin.

Thanks for your Feedback, split the commits and fixed the wrong hook. Please also note #133417 to fix it in master which got already merged.

Also, this doesn't look like it works if i have i3lock also installed: here's a relevant bit from bin/betterlockscreen:
    if ! cmd_exists "i3lockcolor_bin" && cmd_exists "i3lock"; then
        i3lockcolor_bin="i3lock"
    fi

where I think it means to say cmd_exists "$i3lockcolor_bin... currently it's going to replace that with i3lock since no package provides i3lockcolor_bin.

It's really wanted that way because Arch Linux populates i3lock-color as i3lock and this caused a high support come up...

Thanks for your Feedback, split the commits and fixed the wrong hook. Please also note #133417 to fix it in master which got already merged.

Gah! I missed that this was a backport. Ah well; sorry. I think the hook change should also be backported? I'm not a release manager; probably someone with merge bits will have to opine here.

It's really wanted that way because Arch Linux populates i3lock-color as i3lock and this caused a high support come up...

Hm fair; I think you just need to add that $ to i3lockcolor_bin so it checks for the right thing (i3lock-color not i3lockcolor_bin)

Oh, I didn't got that thanks for pointing out!

since it has breaking changes lets not backport it


Wiring up TouchOSC is still confusing and too opaque

Document this or use MDNS to discover the OSC sender.
What follows is a current support/debugging scenario.

John Leone wrote:
Hi Ray,
My name is John and I'm just getting into microcontrollers and computer music. I came across your TouchOSC addition to the transmorgriFX and I was having trouble creating an OSC connection between my computer and the Bela.
Would it be okay if I asked you a few questions? The documentation I've found only talks about OSC while using PureData not C++.
Thank,
John

Ray wrote:
Hi John.  Some initial notes:
You should use the "osc" branch of https://github.com/rhaleblian/transmogriFX_bela .
https://github.com/rhaleblian/transmogriFX_bela/blob/osc/src/osc.h is the interface to the code that listens for OSC events.
https://github.com/rhaleblian/transmogriFX_bela/blob/osc/etc/touchosc/transmogriFX.touchosc is the TouchOSC layout that works with it.
Look at the code for the port number you need to set in TouchOSC to reach the Bela.  It can be confusing.

John wrote:
Ray,
Thank you so much for your response. I've pushed the repository with the respective osc.h code. I'm still having trouble linking touchOSC and Bela due to my lack of networking knowledge. Could you specify where exactly in the code I would change the port number and where in touchOSC I would match it?
image.png
I see this osc.ini file and I'm not sure if I should change the remoteip to my own local ip or the generic <IP_ADDRESS>
image.png
In touchOSC I'm not sure which port corresponds to localport and remoteport in the osc.ini file.
I feel like I'm very close to figuring this out, just this last networking problem I have to deal with.
Thank you again Ray.

Ray wrote:
You are probably close.  Bear with me because I also still get this wrong.
The IP address to put into TouchOSC is the address of your Bela.
The TouchOSC Send Port is the "localport" as set on the Bela side.
The TouchOSC Receive Port is "remoteport".
I actually wish the port numbers in osc.ini were starting out switched.
A way to get a feel for this is to use a some app on a regular desktop computer that uses OSC and get TouchOSC to work with it.  Then you have an analogue working example you can map to the Bela.
There is another project I have that listens for OSC senders all over your LAN so there is less setup (with Avahi/Bonjour) but that bit isn't broken out to just run on a Bela.  Would be nice though, right?


Problem while trying to convert AA to 3Diaa

Hi! First of all many thanks for developing such a useful tool.
I am running into the following problem while executing the code provided in this repository to convert AA to 3Diaa (I paste a screenshot below).

Due to my GPU, which is compatible with CUDA 11.5, I am trying to run ProstT5 with PyTorch 1.11.0, is this possible or the error might be related to this?
Many thanks in advance and sorry if I am being not very specific in my answer, I am new to this field.

Hi! - thanks a lot for your interest in our tool :)
On your error: I do not think that its related to the CUDA/Pytorch version you are using as the error sounds more fundamental (wrong datatype of some tensors during generation - probably either input_ids or attention_mask?).
Could you cross-check whether you might simply use the CLI script that we provide to go from AA to 3Di (called  predict_3Di_encoderOnly.py here: https://github.com/mheinzinger/ProstT5/tree/main/scripts)?
This should work (no datatype issues expected), so it might minimally help debugging, or, depending on your use-case solve the issue.

Using that script solved the issue quite fast! I had tried with the one named translate.py and it had crashed, but this one worked smoothly.
Again, many thanks for this tool, I used it to translate a huge amount of sequences (~200000) and it did it in quite an impressive time :D. Really looking forward to see this published and its evolution, seems to be a magnificent tool.
Cheers,
Mauricio


[Rust] End-to-End testing for AOT Interface API

(This includes #13707, which is being blocked)

Adds functionality to generate Rust files within Model Library Format
Adds tests for Rust AOT with USMP
Updates AOT test utils to optionally generate Rust

We need to eventually clean up the bunch of if/else in the AOT test utils - this would be a good candidate for an RFC to manage AOT interfaces once this has landed.
Co-authored-by: Ashutosh Parkhi<EMAIL_ADDRESS>

Thank you for the contribution. As noted in the other thread and the RFC.
Please resolve the goal of scoping different interface conventions. Specifically, given that there are multiple rust interfaces available in the TVM codebase, being able to do so would help to give space for general community.

G0: Avoid confusion with the normal rust API usage given there are multiple possibilities under a different API.

One possible minimum approach would be renaming the file to interface_embedded_rust.cc, or move to a subfolder that signals such intent, feel free to rename interface_c.cc together if there is an urge to keep things consistent

Thank you for the contribution. As noted in the other thread and the RFC.
Please resolve the goal of scoping different interface conventions. Specifically, given that there are multiple rust interfaces available in the TVM codebase, being able to do so would help to give space for general community.

G0: Avoid confusion with the normal rust API usage given there are multiple possibilities under a different API.

One possible minimum approach would be renaming the file to interface_embedded_rust.cc, or move to a subfolder that signals such intent, feel free to rename interface_c.cc together if there is an urge to keep things consistent

Hi @tqchen,
I clearly stated that this is pending the PR you are blocking, please re-visit https://github.com/apache/tvm/pull/13707#issuecomment-1428217041 as to why the goal you've outlined is inappropriate and why the renaming is the wrong action to take. As evidenced by this PR, there are more things to resolve around AOT interfaces APIs than simply renaming one file.
I've also already stated I would be happy to do the follow up work to properly resolve this situation, you've articulated in many threads that you'd prefer a more agile culture yet it's clear that this isn't being applied in this case.

Agility is realized based on proper scoping of the changes.
For example, the changes are reasonably scoped under a subfolder, sub-namespace, or branch that do not breaches into other things, then we would definitely love to enable such agility, knowing that changes won't create confusions in cases like multiple namespace.
That is why I made such suggestions from the beginning, so such followup developments can be proceeded without breaching into other interfaces.
Happy to  review what comes along as well once you think they are ready.

Agility is realized based on proper scoping of the changes.
For example, the changes are reasonably scoped under a subfolder, sub-namespace, or branch that do not breaches into other things, then we would definitely love to enable such agility, knowing that changes won't create confusions in cases like multiple namespace.
That is why I made such suggestions from the beginning, so such followup developments can be proceeded without breaching into other interfaces.

Please refer back to my previous comment https://github.com/apache/tvm-rfcs/pull/96#issuecomment-1372661932, this is aligned with the existing architecture, demonstrating that this is reasonably scoped for the files that exist pending further changes to better remedy the situation. Please also refer back to that conversation as to why we shouldn't be introducing the inconsistency for one file.

Happy to review what comes along as well once you think they are ready.

I'm indeed intending to raise additional pull requests to finish upstreaming this work, you are welcome to request changes on them all - as unwelcoming as this has become, I want to surface the user value even if it remains in a fork. As I've illustrated, this work is ready for review, trusting in myself as a committer to follow up and fix the area of the codebase I have already contributed much to.

In this case I would come one step further and say existing architecture (if you were referring to target/interface_c) was also not properly scoped and would benefit from scoping. I did not review that particular change, nor did the scoping proposal included the RFC in the relevant changes.
I (lazily) approved the RFC(including previous ones related to such embedded interface) based on the assumption that there would be proper scoping, as it were a common practices in the TVM project for most of the modules. Apparently there wasn't such a consideration, or a proposal when being asked.
That merged code however, can also be revisited, and in the course of continuous conversation. Doing proper scoping would be necessarily for different contributors to operate in their subareas without having to step onto each other.
While the perhaps the code implements the feature that was intended in the area that you contributed to, the current scoping of the module breaches other concurrent APIs. As a result that impacts grows to the overall architecture level of the project. From the standpt of overall project architecture, I would kindly request a proper scoping for the proposed module only.
Please feel free to continue development in a way that is reasonably scoped, it can be a branch, a new namespace, sub folder or any other approach that would satisfied that goal, which was the course of action that most developers in the community would happily take.

That part of merged code however, can also be revisited, and in the course of continuous conversation -- rather than being used as a simple golden rule. Remember it is only part of the code(that was not consistent with the rest of the architecture), and being consistent only with that one part of the code simply ignores the architecture as a whole.

I'm simply demonstrating that the code already exists, and it would be architecturally consistent rather than introducing another inconsistency. I never said it was a golden rule, nor did I state it was in a good state, in fact I suggested we should do a larger piece of work to remedy it properly.

Please feel free to continue development in a way that is reasonably scoped, it can be a branch, a new namespace, sub folder or any other approach that would satisfied that goal, which was the course of action that most developers in the community would happily take.

It's better to make any new interface as consistent with the old interface as possible, as I've highlighted in previous conversations, this is standard practice when interacting with existing code. I've also stated I would follow up to remedy the overall architecture, taking into account more than a single file, you've made it clear you do not trust me to do such a follow up.

In this case, what was being demonstrated was an item x("old interface") in the overall architecture, which was not scoped under the context of overall architecture A (including "other older interfaces").
When proposing a new item y here. y may be consistent with x, but it is not consistent with A, which are also part of the overall architecture. Obviously there is a tradeoff here.
The ask is that considering the overall architecture, please start with a way that is consistent with A (where all other modules are properly scoped), it would indeed introduce inconsistency with x. From the overall project's pov this tradeoff is the right step forward, and what one would normally recommend.

Just to be clear, either actions being taken there will be some levels of further inconsistency of some form in the code base. Either in the form of

F0: y being in consistent to A (adding inconsistency to the overall architecture) and another less scoped item.
F1: y being slightly inconsistent with x.

I am merely stating that when considering the overall project, we should prioritize F0.

Just to be clear, either actions being taken there will be some levels of further inconsistency of some form in the code base. Either in the form of

F0: y being in consistent to A (adding inconsistency to the overall architecture) and another less scoped item.
F1: y being slightly inconsistent with x (which was inconsistent with A).

I am merely stating that when considering the overall project, we should prioritize F0.

I would suggest that being welcoming of this change and encouraging the follow up would prioritise the health of the overall codebase, as you've suggested in other threads.

I am not sure which other thread were referred, but I believe most of the other threads have changes that are properly scoped in their respective modules as a result such agility can be enabled.
I certainly try to accommodate the set of changes that was why the suggestion was minimum while still prioritizes F0

I've been following all these discussions about the Rust API proposed improvements and I'm surprised by how this is being dealt with.
The disagreement seems to be on the way files are named, and the blocking request is to make it explicit the proposed changes only applies to embedded devices and (subject to confirmation) not doing that would have a detrimental effect in causing confusion to developers.
My Rust knowledge is quite basic, so I'd like to understand how the proposed change is only applicable for embedded use cases, that it is being required to be explicitly named this way. Names of things are very subjective, unless we have some written naming convention written somewhere, which I'm not aware of.
I guess the important question is: @Mousius is there something proposed here that fundamentally only applies to embedded Rust? If not, then I think the proposed patch is fine to be approved and merged, and we should proceed this way.
As we've been discussing a lot recently in the threads (e.g. Unity) and in the forum (e.g. Code Review Guidelines thread), the argumentation line of trusting, empowering the community and welcoming ideas seems to be conditionally applicable to some proposals and not others. This is one case it seems we are not applying those, therefore, letting contributors down and making them less inclined to make future contributions.
So I suggest in the current direction of being welcoming and empowering the community to take decisions, that we accept and iterate over the proposed API, and in case we notice it is causing confusion to developers, we re-evaluate.

Thanks, everyone, for chiming in so far. We have spent quite a bit of time over this. I think we are getting closer to more clarity so I would like to provide a digest of my verdict so far.
Importance of Scoping
Here scoping refers to clearly naming and differentiating the overall modules with other means. For example, when there is already a module (tvm rust api) that interfaces with the users. It would be appropriate to find ways to structure it clearly in the codebase so that it differentiates with existing modules.
This does not mean  that the proposed new module should not overlap with the features provided by existing modules. It does not limit the scope of what the API can do but asks for clarification of API and implementation such that they signal the difference to the user. It only means that the proposed API and related code sit in a way that signals the difference and structure. Nor does it specify the way the API is named.
For example, naming it nostd_rust_interface would also be accurate, not restricting the setting to embedded but also signaling that it is a different module from the current rust API. Naming it tvm_awesome_xyz_rust.cc also works as long as awesome_xyz conveys the intent of the code.
There are many approaches to scoping, including, but not limited to:

naming of the respective files
subfolder structures
namespace
These practices are also common practices in software development.

Scoping is a Necessary Precondition  for Agility
We are a project that comes with a lot of different modules and developer communities. Each one of us may care about a different subarea. In order for the modules to be sufficiently developed concurrently. Clarity of scoping (again, not in terms of what they can do, but simply in terms of clear organization, naming, and namespacing along with existing architecture) is a necessary condition for us to empower each other so as to avoid one module stepping into another one.
Usually, proper scoping needs to be done once – e.g. placing things in a proper subfolder(and/or) namespace would allow agile development of any APIs under that namespace without much intervention from the broader community. This is because the scope of impact is also isolated in such a way.
After proper scoping, there will be great flexibility. Naming the API as a namespace_x::awesome_xyz is fine as long as the community members of respective areas agree. One would have great flexibility as long as the namespace differentiates it from existing namespace, and additional folder structure that helps to signal clear organizations.
That does not mean we cannot bring changes to the root namespace, they do mean that would certainly need more deliberations in consideration along with existing APIs and an evaluation from an overall architecture standpoint.
Scoping is the Standard Practice in Almost All Modules in TVM
Scoping is a standard practice, and necessary condition for software to scale and is the standard practice in the TVM project. We can easily name a few: meta_schedule (so name differentiates from autotvm), uma, crt.
This is a standard practice that most of us follow in the project. They do not diminish the value, or what the module can do, they just help to bring a clear structure. I worked on these properly scoped modules daily. When reviewing and accepting RFCs, we always keep assuming that the code will be properly scoped, or feedback being taken to resolve that goal.
Verdict of This Particular Case
In this particular case, the items of interest includes three things
A: the overall architecture, which already includes a rust API that interacts with the standard tvm runtime.
y: proposed interface_rust, which has an scoping issue mainly to have possible confusions with the existing rust API.
x: interface_c , the “old architecture” that was referred to in this case, which unfortunately was not properly scoped, as it can cause confusion with the c_runtime_api. Since interface_c is not compatible with all variants of runtimes and is reasonably strongly coupled with crt(for a good reason). Naming it as something like interface_c_for_crt, interface_c_tiny would have been better.
I have not reviewed x’s code change unfortunately, and the respective RFCs did not discuss scoping. Still the priority in terms of architecture should be prioritizing y to be consistent with A, even if it may come at the cost of slight inconsistency with x.
The suggestion has nothing to do with whether or not to restrict the usage to embedded only. But instead to clearly signal the difference in the space. For example, nostd_rust would be another accurate description that also works, as it does not depend on the larger standard runtime (including object system) that TVM provides (for a good reason). Any other proper namespacing or folder structure also works.
There is also no inconsistency with the recent rationales for agility and empowerment. As all of the other threads are pre-conditioned on proper scoping of such related modules.
It is also not an issue that will arise in the future, as the rust API already exists in the codebase now. Putting the changes in a reasonable subfolder, namespace, or at least proper naming would enable us to iterate the proposed API in an flexible way. In this way we can empower not only this PR, and other community developers (who also follow the same scoping principle).
Because the proposal has a need for scoping, it becomes a case of overall TVM architecture. I have volunteered my energy over years to help coordinate the overall architecture and hopefully the overall input gives more clarity here. I also explained the rationale. Hopefully the recommendations are clear and they are made on the basis of the state of scoping and the overall architecture.
If there is a goal to continue code review and iterate without addressing the scoping, then a branch could be a good starting point. Other ways to achieve the same goal also helps here. Again I am not being fixated on only one way to name the file, but instead offering suggestions to help the scoping of the module. I have no doubt that the module could be useful to intended users and developers, just that for the module to co-exist with other modules in the project some minimum requirement of scoping is needed to clear it from overall architecture pov.
I would be more than happy to review future proposals. To give extra clarity, I marked the PR as need-scoping. Please copy me on future proposals related to the module as I would like to help on  the scoping part.


feather installation failed with "big endian" issue

I am trying to install R packages on AIX7.2 server. My feather installation failed with following error. According to my google search, this issue should have been fixed long time ago: https://github.com/tidyverse/tidyverse/issues/36. My version is feather_0.3.5.tar.gz. Can someone please tell me how to fix it?
* installing *source* package 'feather' ...
** package 'feather' successfully unpacked and MD5 sums checked
** using staged installation
Platform is big endian. This is currently unsupported.
ERROR: configuration failed for package 'feather'
* removing '/software/R/site-library/feather'

Can you install the "arrow" package on this system?

Yes, I have installed arrow package successfully.  There is a note to run "arrow::install_arrow()" after installation.  But I received the following another note:
> library(arrow)

Attaching package: 'arrow'

The following object is masked from 'package:utils':

    timestamp

> arrow::install_arrow()
Refer to the R package README <https://github.com/apache/arrow/blob/master/r/README.md> and `vignette('install', package = 'arrow')` for installation guidance.


2023 10 06 changes

Running List of bug fixes/feature improvements:

[ ] freeze headers on BSM table
[ ] cannot change default intersection parameters without intersection id
[ ] draw crosswalks in a different color
[x] set an end time for MAP message query
[ ] After you click on the “Sign in with Keycloak” button, and the login screen pops up, can you change “CONFLICT VISUALIZER’ TO “Connected Intersections Message Monitoring System”

[ ] style login page

[x] Would like to hold query results in memory so user can still see previous query results after navigating to the map visualization
[x] When Using the Map to search for BSM's, SPaT, Map. Can the map also query events, and notifications in the time range and show them on the side?

[x] show in side panel
[ ] show on map when possible

[x] Instead of making the user populate a text box for the road regulator ID and intersection ID, could this be a drop down menu with a pre-populated list of unique road regulator ID / intersection ID combinations?

[x] roadRegulatorId: grab all unique road regulator ID
[x] intersectionId: all possible intersection IDs for current roadRegulatorId

[x] There are a few issues changing settings from the configuration menu. It looks like changing the default config is actually changing the intersection config.
[x] SPAT visualization does not change before event time
[x] SPAT visualization time does not change as often as it should
[x] give indication that query selector is loading
[x] in query selector, the number of records shown increases the number on screen
[x] sometimes, query results contain results from the previous query
[x] set intersection ID when mapping an event/BSM
[ ] display events on query selector in 2 columns
[ ] download message sender csv script data from the open map

[ ] Ivan has code in the test-message-sender/message-sender resources/script-utilities.js
[ ] https://github.com/usdot-jpo-ode/jpo-conflictmonitor/blob/develop/test-message-sender/message-sender/src/main/resources/static/script-utilities.js

[x] Map Visualization

[x] Talk through event state line colors on next call to confirm.
[x] SPaT issue – SPaT visualization does not change when scrolling before the event time
[x] SPaT and BSM – most recent BSM should sync with current SPaT.

[x] Data table page navigation issues

[x] When continuing to select next page (right arrow), the number of displayed rows eventually starts to grow by X number of rows, rather than only showing the next X number of rows.
[x] After selecting the next page (right arrow) several times, and running a new query, the row numbers displayed does not reset properly
[x] When running a new query, after having already run a previous query, I find that the results sometimes contain results from the previous query.

[x] When multiple event types are contained in results, the download button does not work
[x] Can results be sorted by date (or allow user to select column to sort by date)?

[x] Automatically sort by date
[ ] Sort by custom column

[x] When selecting the map icon next to an event, the map shows data from the intersection that is selected from the drop-down at the top of the page (which may not be the intersection where the event came from). Is there a way to automatically change this to the intersection id where the event is?
[x] Would like to hold query results in memory so user can still see previous query results after navigating to the map visualization
[x] Drop down to select road regulator ID and intersection ID
[ ] Looks terrible on laptop screen
- [x] Shrink/collapse UI elements
- [ ] Make UI elements scale better with size
- [ ] Fully optimize for smaller screens
- [ ] Optimize for mobile devices
[ ] rotate icons with map
[ ] new signal icons (with arrows)
[x] more notification summaries

I am making a few final changes and validating these updates, but this will be ready shortly

@John-Wiens This PR is ready, I want to get this deployed to Utah and test it out if possible! There are a few minor updates to the API, fixing some Long conversion bugs


Add support for Laravel 9

This adds support for Laravel 9 and also updates the GitHub workflow to test against PHP 8.1.

May not be as simple as appears, but I will look into this soon as I can :) cheers for the PR

Any updates on the PR?

My bad, crazy busy. I have started work on it. Thanks for reminder. :)

Hey @nicekiwi - any news on the progress? I don't want to annoy you, I understand you're busy. If you point me towards what needs to be updated to make this package work with L9, I can also help with this PR.

Hey @nicekiwi, just wondering if you had been able to take a look at this or if you would like me to make some changes?

@nicekiwi any updates on this?

@bensherred sorry for the super slow responses. I've implemented Laravel9 support in the laravel9 branch, could you try that? "syntax/steam-api": "dev-laravel9"

Hey @nicekiwi, that’s great! I’ll take a look over the weekend and let you know

Hey, any news on a stable release for L9?


Add Signing Entity Name for Corporate DocuSign Workflows

Summary
Add Signing Entity Name for Corporate DocuSign Workflows
Background
Per stakeholder feedback, the product should allow the user to create and set a Signed Entity Name and carry the attribute through the various corporate signing agreement workflows.
Tasks

[ ] Review Python routes.py -> request_corporate_signature POST request payload, add/include a concept of Signing Entity Name signing_entity_name field/attribute.
[ ] review and update Python signing.py -> request_corporate_signature - update as necessary
[ ] review and update Python docusign_models.py -> request_corporate_signature - update as necessary
[ ] review and update Python docusign_models.py -> handle_signing_new_corporate_signature - update as necessary
[ ] review and update Python docusign_models.py -> create_default_company_values - update as necessary to ensure user's provided company/entity name is set in the DocuSign form
[ ] Legal entity name should be marked as read-only on the DocuSign form

User Story

As a project manager, I want users to specify the proper legal entity name when signing corporate agreements.

Acceptance Criteria
The "done" criteria when this feature or problem is resolved. Such as:

Unit Tests added and running in CI
Functional Tests updated to cover feature, if applicable
Demonstrate the set of capabilities to the product team while the code is running in the STAGING environment.

References

Corresponding CLA frontend ticket is as follows:
https://app.zenhub.com/workspaces/easycla-5ed619832c71a855a76ef404/issues/communitybridge/easycla/2429

Corresponding CLA frontend ticket is as follows:
https://app.zenhub.com/workspaces/easycla-5ed619832c71a855a76ef404/issues/communitybridge/easycla/2429

Merged PR https://github.com/communitybridge/easycla/pull/2442 which includes the initial wave of changes to support the new Signing Entity Name attribute.

Merged PR https://github.com/communitybridge/easycla/pull/2442 which includes the initial wave of changes to support the new Signing Entity Name attribute.

Merged org service PR to fix typo: https://github.com/LF-Engineering/organization-service/pull/243

Merged org service PR to fix typo: https://github.com/LF-Engineering/organization-service/pull/243

This is just the backend ticket - functionality is being QA tested through 2429. So, closing this one.

This is just the backend ticket - functionality is being QA tested through 2429. So, closing this one.


College Website

Title and Issue number
Added a  new project in Front-End project ,which is made with Html,Css and javaScript-->
Close #<issue_no>

Checklist:

[] I have mentioned the issue number in my Pull Request.
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have created a helpful and easy to understand README.md

Inactive


how TIPS ladders, other bond ladders, CD ladders should be represented in portfolio

Forum comment by me: https://www.bogleheads.org/forum/viewtopic.php?p=7685300#p7685300

This exchange reminds me that I have recently been thinking through how TIPS ladders, other bond ladders, CD ladders should be represented in portfolio spreadsheets or tools. Haven't come to a conclusion in my mind yet...but my current favorite is: allow marking some assets as "not part of portfolio". Asset Allocation calculations, net worth views, and some other views of your portfolio would ignore those assets.
However, this points to the need of tracking your future expected income, which different spreadsheets and tools do many different ways. Social Security, pensions, ladders, annuities, etc...

watchnerd reply (https://www.bogleheads.org/forum/viewtopic.php?p=7685364#p7685364):

I treat the LMP TIPS ladder as a completely separate portfoflio.

In addition to having the goal of providing an income stream similar to SS, it's also non-rolling, so will get consumed over time.
This ends up leading to a rising equity glide path, rather than a static AA.
But from an AA tracking POV, I mostly ignore the TIPS ladder.

afan replied to watchnerd:

Pretty much what I do. I do not ignore the TIPS in tracking my AA. I recognize that they represent the bulk of bond holdings. But since there are TIPS and SS, I do not rebalance my allocations. I keep saving money and it goes into stocks. So, like you my equity allocation continues to increase on its own.


Grab and Drag entire Window

What feature or improvement do you think would benefit Files?
So, as with every Windows program, you can usually use the uppermost bar to move things around and reorder them. It works with Files too, unless... you got too many tabs open. No matter where you grab, you will always end up selecting a tab or a button. No area to grab and drag is left. That's super annoying because you either have to enlarge (stretch) the window to be able to move it around or close tabs.
Requirements

This proposal will accomplish a reliable grab & drag function

Files Version
<IP_ADDRESS>
Windows Version
10.0.19045.3930
Comments
No response

Thanks for the feedback, I've added this to the project board.


Not able to start session

Hello, I have setup this driver using WebdriverIO, but I am not able to start session always getting error below
[0-0] 2023-09-20T13:08:27.637Z ERROR @wdio/runner: Error: Failed to create session.
[0-0] An unknown server-side error occurred while processing the command. Original error: Command '/Users/pauliusguzas/tizen-studio/tools/sdb -s <IP_ADDRESS>\:26101 shell 0 debug my.cool.app.id' exited with code 1. Stdout was: ''. Stderr was: 'closed '

These are my capabilities:
      {
            platformName: 'TizenTV',
            'appium:options': {
                automationName: 'TizenTV',
                deviceName: '<IP_ADDRESS>:26101',
                chromedriverExecutable: '/Users/pauliusguzas/Downloads/chromedriver',
                appPackage: 'my.cool.app.id',
                app: 'path/to/my/app.wgt',
                fullReset: true,
            },
        },

Versions used:
        "@wdio/allure-reporter": "7.19.5",
        "@wdio/appium-service": "7.19.5",
        "@wdio/cli": "7.19.5",
        "@wdio/local-runner": "7.19.5",
        "@wdio/mocha-framework": "7.19.5",
        "@wdio/selenium-standalone-service": "7.19.5",
        "@wdio/spec-reporter": "7.19.5",
        "allure-commandline": "2.17.2",
        "appium": "2.0.0",
        "appium-mac2-driver": "1.7.2",
        "appium-uiautomator2-driver": "2.29.5",
        "appium-xcuitest-driver": "4.32.11",
        "appium-tizen-tv-driver": "0.8.1",
        "appium-lg-webos-driver": "0.0.6",
        "chromedriver": "102.0.0",
        "wdio-chromedriver-service": "7.2.2",
        "wdio-image-comparison-service": "5.0.3",
        "wdio-native-app-compare-service": "2.1.0"

cc @jlipps

What happens if you try to run that command on your own? If it doesn't work then the driver won't be able to do its thing

command simply returns closed whatever that means

Yep that means it didn't work. You'll need to go through whatever troubleshooting you need to do with your app or the device to make that command work. Maybe the app is not built in debug mode?


Added 'slow' command.

This command slows down animations. Works like 'Toggle Slow Animations' from iOS Simulator but this command works also on the device and user is able to select animation speed.

Thank you @bartoszj :+1:
Would you mind signing Facebook's Contributor License Agreement? If you have any questions I'd be happy to help answer. https://code.facebook.com/cla

Done.

@bartoszj Thanks for submitting this! I have a couple comments above.
What do you think about adding two commands, one to turn this on, one to turn if off. All of our other commands work this way, so we should be consistent unless there's a good reason not to be. If we have two commands, they can both have a default speed, with the undo command having a speed of 1.

Isn't this the same as 'slowanim' and 'unslowanim' or have we not merged that, @kastiglione ?

@kastiglione I agree with two commands. slowanim and unslowanim would be OK? Also I'll check slow animation on all windows.

Great! :bow:

Updated.

Thanks @bartoszj! I left a couple comments, the main one is about giving slowanim a default speed value so that it could be typed without having to provide an explicit speed.

I've found that iOS Simulator is using 0.1 as speed value and I've set it in theslowanim command.

:boom:
Looks good. I'll checkout this branch and give it a try and merge if all goes well. Thanks!

Thanks for this contribution! And thanks for being patient and awesome :+1:


Hidden "Sign In" button

Describe the bug
In the home page at top right corner the "Sign in" button is hidden.
Expected behavior
The "Sign in" button should be displayed properly.
Screenshots
If applicable, add screenshots to help explain your problem.

Are you working on this issue? (Yes/No)
Yes

Hey, this could be done so that button is differentiable then links by adding some backgrounds colors .

@pankaj-2503 If you add background to the button it will look odd in the navbar.

@Priyanshu-su30   i thought  button should look different than  links  .


Maven Docker Build improvements

Included changes:

One mvn deploy command to deploy all docker images in the repository.
Unified and simplified docker-maven-plugin configuration.
Allow having different namespace and username.
Added missing docker healthcheck.
Changed wrong java version of registry-aas from 11 to 17.

Thanks a lot for your contribution! However, the Eclipse Contributer Agreement check is failing. Did you link your GitHub account with your Eclipse account? Are you using the same mails?

The build is failing on aas registry - probably because I increased the java version to from 11 to 17.
The image being used is java-17. I would suggest we either downgrade the docker image to java-11 or try fixing this error.
I also noticed that submodel registry is already on java-17.

Since Spring 3 is using Java 17 would a downgrade really help?

Since Spring 3 is using Java 17 would a downgrade really help?

It makes probably more sense to fix the errors instead of downgrading.