Difference between service.machine.initialState and service.initialState

Description
A consumer of xstate-vue2 noticed a bug where there is a critical difference between accessing the initial state on service.machine.initialState and service.initialState when spawning another machine. They put up a fix here.
Expected Result
Accessing service.machine.initialState.context does not cause an extra entry action to run.
Actual Result
The entry action for the spawn logs again. Also its interesting that service.machine.initialState.context logs an ActorRef while service.initialState.context logs an interpreter.
Reproduction
https://codesandbox.io/s/focused-voice-hnuni?file=/src/main.ts
Additional context
I am unsure of whether this is a bug in core or the component packages (@xstate/vue, @xstate/react, ect.). These packages currently access service.machine.initialState in useMachine.

The only difference between service.machine.initialState and service.initialState is that:

service.initialState will return the state with the initial context with actors spawned on the parent
service.machine.initialState is basically machine.initialState which is completely unaware of the parent

The fix that they put up should be fine (most likely).

Thanks for the quick response! I will merge it in and update this issue if any unintended side effects come up!
For book keeping service.machine.initialState is used here, here, and here.

Note that in the React land this would not work properly (at the time). The service.initialState variant is not pure and might execute side-effects at the wrong time: https://codesandbox.io/s/sleepy-almeida-ql101?file=/src/App.js

@ChrisShank Can this be considered answered/solved? Or should we add documentation for this?

@davidkpiano Its answered, but does the vue package still have this bug?

As far as I see it might have that bug - I'll assign myself to this issue, write a test and fix the bug (or just add a test if it turns out that there is no bug after all).

I'm pretty sure this problem is avoided completely in xstate@beta since there is no longer any actor.initialState (rather, actor.getSnapshot() only).
Feel free to reopen if this is still an xstate@beta issue somehow.


User Story 6.2

User Story: ALTA-6.2
As an ALTA user, I want to be able to update my email address so that I can access ALTA with verified credentials.
Description
By logging into the web app of ALTA, the user should be able to update and verify their email address. The updated email address will receive a link to validate the user. Once validated, the system will perform the update and request the user to login using the updated email address. This functionality is not directly applicable to stock-keepers as an organization's inventory manager can update their email address if needed.
Note: the update will only occur once the user has validated the newly submitted email address.
Acceptance Criteria (AT-6.2 - #281)
Given that the user is logged into ALTA as a system administrator or inventory manager,

The user selects the Settings side menu option.
The user is presented with the form containing their previously supplied user information.
The user selects the Edit button to allow the fields to accept input.
The user modifies the email address field and selects the Save button.
The user is presented with an alert message to verify the updated email address.
The newly updated email address receives an email containing the link to verify the modification. The user selects the provided link.
The user is redirected to the Log in page to log into the system using the new email address.

Related Mockups

Log into ALTA

Dashboard page

Profile settings page

Edit profile setting page

Updated email address message - will also display when updating a stock-keeper's email address

Verification email to confirm the update

Login page - user is requested to log back into ALTA using the updated email address

As agreed upon by the stakeholder and team, this user story is scoped-out of the project requirements

Out of scope. No need to update email address. Email addresses don't change at organizational level.


New version: Bitwarden.CLI version 2024.12.0

Pull request has been created with komac v2.8.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

Manual Validation ended with:

2024-12-18 09:43:38.142 [FAIL] Installer failed security check. Url: https://github.com/bitwarden/clients/releases/download/cli-v
2024.12.0/bw-windows-
2024.12.0.zip Result: 0x80004005

(Automated response - build 930.)

@wingetbot run


Don't use FailoverValidatorApiHandler if no failovers configured

PR Description

Essentially use the RemoteValidatorApiHandler instead of the FailoverValidatorApiHandler, when there are no failovers configured. There is a very small overhead and I assume most users don't have failovers configured by default.
In that case, validator_remote_beacon_nodes_requests_total metric would not be used when there are no failovers configured. Added a line to the CHANGELOG. It makes sense because both metrics are replicated in case of a single BN configured and don't provide much value
Includes some refactoring changes in RemoteBeaconNodeApi and SentryBeaconNodeApi

Fixed Issue(s)
N/A
Documentation

[X] I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

[X] I thought about adding a changelog entry, and added one if I deemed necessary.

Closing again until better way to reconcile metrics is found


First Contribution by Bonte Emma Bana

Names: Bonte Emma Bana
Project I was assigned to: Pysal
Project Link: http://pysal.org/
Link to the governance model: https://github.com/pysal/governance
A little bit about PySAL
PySAL is a Python library designed for spatial analysis, with a focus on geographic information systems and spatial econometrics. PySAL provides a wide range of spatial analysis tools and methods for analyzing and modeling spatial data, including spatial autocorrelation, spatial clustering, spatial regression, and spatial visualization. The library is built on top of NumPy, SciPy, and Matplotlib, making it easy to integrate into existing Python workflows. PySAL has an active community of contributors and users, and it is continually updated and improved with new features and capabilities. PySAL is open-source and freely available under the BSD license, allowing for both academic and commercial use. Overall, PySAL is a powerful tool for spatial analysis and modeling in Python, and it is widely used in both academia and industry for a range of applications, including regional planning, environmental analysis, and economic geography.
PySAL governance model:
The PySAL project has a well-defined governance model outlined in their GitHub repository, specifically in the "governance" folder. The model is based on a steering committee consisting of members who have made significant contributions to the project. The steering committee is responsible for making decisions related to project development, releases, and management. The project also has maintainers who are responsible for maintaining specific parts of the project codebase. The decision-making process for the PySAL project is based on consensus among the steering committee members. However, in cases where a decision cannot be made through consensus, voting procedures may be used. The voting process requires a majority vote from the steering committee members. The project also has a code of conduct that outlines the behavior and expectations of all members of the PySAL community. Overall, the PySAL project has a clear and effective governance model in place that ensures community involvement and transparency in decision-making processes.
The PySAL project has several key roles that are essential for its governance and management. The roles include the following:
Maintainers
Contributors
Technical Steering Committee (TSC)
Code of Conduct Committee
PySAL ‘s decision-making process
The PySAL project follows a decision-making process that includes a combination of voting procedures and approval processes. The Technical Steering Committee (TSC) is the main decision-making body for the project, responsible for overseeing the technical direction, strategic planning, and goals of the project. For proposals related to major changes or new features, community members can submit a Request for Comment (RFC) on the project's GitHub repository. The RFC will be reviewed and discussed by the community, and if deemed necessary, revisions will be made to the proposal. Once the RFC has been discussed and revised, it will be put up for a final vote by the TSC. For code changes, contributors submit pull requests which are reviewed by Maintainers. If a pull request meets the project's standards and has been approved by a Maintainer, it is merged into the codebase. The project also has a Code of Conduct Committee responsible for handling any issues related to the project's code of conduct. If a member of the community has concerns or complaints, they can report them to the committee, who will investigate and take appropriate action as necessary.
Finding and Understanding the governance model
The governance model is easily accessible as it is hosted on the project’s github repository; and it is well structured and organized making it easy to navigate and understand the different roles, decision-making processes, and policies that guides the project.

@arliss-NF; This is my task!


Getting can't find soure for Build_doctests error.

Hi,
I followed the doc with the code in Setup.hs taken from the readme.  But I am still getting the following error:
setup: can't find source for Build_doctests in test,
.stack-work/dist/x86_64-linux-nix/Cabal-<IP_ADDRESS>/build/doctests/autogen,
.stack-work/dist/x86_64-linux-nix/Cabal-<IP_ADDRESS>/build/global-autogen
I am using latest stack with Cabal-2.4.0 and cabal-doctests is defined.  This is running on nixos 18.03 and ghc-8.6.*.  Is there any step missing or any test I could do to see what is missing?  Thanks for your help.

@wpoosanguansit you might have a type, do you have your package somewhere publicly viewable?

@phadej thanks for your help.  Unfortunately, we don't have it in a publicly viewable project. Below are the two package and stack yaml files we are using.  Thanks again for  your help.
package.yaml.txt
stack.yaml.txt

I don't see anything obviously wrong with those.
You could try a version in https://github.com/phadej/cabal-doctest/pull/48 which would log the location of generated Build_doctests file. (I though have no idea how make stack to make custom setup verbose, --cabal-verbose doesn't seem to do the trick). Or you could try to find . -name 'Build_depends.hs to see if it's created at all.

find didn't return any result.  So the file was not generated at all I think.  Also, i did use the commit you mentioned.  I also didn't see any print out that is different from my earlier stack test runs.  Any other suggestions?  Thanks.

is generated twinflower.cabal with build-type: Custom
how does your Setup.hs looks like

On 9 Apr 2019, at 23.58, wpoosanguansit<EMAIL_ADDRESS>wrote:
find didn't return any result. So the file was not generated at all I think. Also, i did use the commit you mentioned. I also didn't see any print out that is different from my earlier stack test runs. Any other suggestions? Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

{-# LANGUAGE CPP #-}
{-# OPTIONS_GHC -Wall #-}
module Main (main) where
#ifndef MIN_VERSION_cabal_doctest
#define MIN_VERSION_cabal_doctest(x,y,z) 0
#endif
#if MIN_VERSION_cabal_doctest(1,0,0)
import Distribution.Extra.Doctest ( defaultMainWithDoctests )
import Data.ProtoLens.Setup
main :: IO ()
main = do
defaultMainGeneratingProtos "src/System/Proto"
defaultMainWithDoctests "doctests"
#else
#ifdef MIN_VERSION_Cabal
-- If the macro is defined, we have new cabal-install,
-- but for some reason we don't have cabal-doctest in package-db
-- Probably we are running cabal sdist, when otherwise using new-build
-- workflow
#warning You are configuring this package without cabal-doctest installed.
The doctests test-suite will not work as a result.
To fix this, install cabal-doctest before configuring.
#endif
import Distribution.Simple
import Data.ProtoLens.Setup
main :: IO ()
main = do
defaultMain
defaultMainGeneratingProtos "src/System/Proto"
#endif
I basically copy this from the example you have.  Any suggestion?

On Apr 9, 2019, at 2:44 PM, Oleg Grenrus<EMAIL_ADDRESS>wrote:

is generated twinflower.cabal with build-type: Custom
how does your Setup.hs looks like

On 9 Apr 2019, at 23.58, wpoosanguansit<EMAIL_ADDRESS>wrote:
find didn't return any result. So the file was not generated at all I think. Also, i did use the commit you mentioned. I also didn't see any print out that is different from my earlier stack test runs. Any other suggestions? Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/phadej/cabal-doctest/issues/47#issuecomment-481451806, or mute the thread https://github.com/notifications/unsubscribe-auth/AAFibS2FUfPWOScA6zZ8FABwgHg13cDJks5vfQnIgaJpZM4chMPB.

main = do
    defaultMainGeneratingProtos "src/System/Proto"
    defaultMainWithDoctests "doctests"

That's definitely incorrect. You might take a look into adding hooks with http://hackage.haskell.org/package/cabal-doctest-1.0.6/docs/Distribution-Extra-Doctest.html#v:addDoctestsUserHook
Look how defaultMainWithDoctests or defaultMainAutoconfWithDoctests are implemented.

I do see this in the doc:
defaultMainWithDoctests Source #

:: String
doctests test-suite name
-> IO ()
A default main with doctests:

import Distribution.Extra.Doctest
       (defaultMainWithDoctests)

main :: IO ()
main = defaultMainWithDoctests "doctests"

And I do have this:
import Distribution.Extra.Doctest ( defaultMainWithDoctests )
import Data.ProtoLens.Setup

main :: IO ()
main = do
    defaultMainGeneratingProtos "src/Turgenev/System/Proto"
    defaultMainWithDoctests "doctests"

defaultMainWithDoctests "doctests" will get run, right?  I have to apologize that I didn't see what is missing yet.  Thanks for your help.

I'm pretty sure that defaultMainWithDoctests "doctests" isn't run. Or if it is, it doesn't do anything reasonable.

Whats your test-suite name for doctests in the Cabal file? In the pkg doc case, it is "doctests".

I am so sorry @alissa-tung that I have stop working on the code awhile back and I totally lost the hd that this project was on from encryption.  Thanks for your help.

I am so sorry @alissa-tung that I have stop working on the code awhile back and I totally lost the hd that this project was on from encryption.  Thanks for your help.

You're welcome and sorry to hear that. I ran into this issue because I initially use the name in the example instead the test-suite of the package I am working on and after I made CI passing I thought I can help if it can be the reason in this issue. Hoping someone who indexed the issues in the future can save some time :)


A question on xvfb and running in Google cloud functions

Great work with this library @zfcsoftware.
I see xvfb is a requirement. Does this mean there's no chance at all that we can run this using Google cloud functions, not even with headless = true?

xvfb is absolutely necessary to avoid detection when opened incognito. It creates a virtual screen. For this reason, you can run it anywhere with container support.
Tested many times with Google cloud run.
https://github.com/zfcsoftware/puppeteer-real-browser/blob/main/Dockerfile
Using the dockerfile in the home directory, you can run it on Google Cloud Run without any problems. However, it cannot be run in non-container functions.

Thank you. I've got it working when I create a new project/folder and use this code:
(async () => {
  const { connect } = await import('puppeteer-real-browser');

  connect({
      tf: true, // If a feature you want to use at startup is not working, you can initialize the tf variable false and update it later.
      turnstile: true
  })
  .then(async response => {
          const { page, browser, setTarget } = response

          page.goto('https://nopecha.com/demo/cloudflare', {
              waitUntil: 'domcontentloaded'
          })

          setTarget({ status: false })

          let page2 = await browser.newPage();

          setTarget({ status: true })

          await page2.goto('https://nopecha.com/demo/cloudflare');
  })

  // Use connect as needed here
})();

But when trying to implement it in an existing project (in addition to chrome-aws-lambda which I currently use) I get an error:
var response = !!target.url()
                            ^
TypeError: target.url is not a function

I added a console.log before this line and in the existing project it shows:
target:  {
  targetId: '7665528686C39479243B434C8669808C',
  type: 'page',
  title: 'about:blank',
  url: 'about:blank',
  attached: true,
  canAccessOpener: false,
  browserContextId: '8B0D38451DDF4A5431CF6C4DCFCB806A'
}

While in the new project is shows:
target:  CdpTarget {
  _initializedDeferred: Deferred {},
  _isClosedDeferred: Deferred {},
  _targetId: '84a3c50a-aa77-45cc-8bf3-17dec5ab7c0d'
}
target:  CdpTarget {
  _initializedDeferred: Deferred {},
  _isClosedDeferred: Deferred {},
  _targetId: '865AA8E483FA9DD16AB482B73A7FEC2F'
}

(and more of the same)

Exact same code example just in different folders. May the dependencies of my existing project be conflicting?
And one more question. Can we use async rather than the .then method provided in the example? For example, like this:
async function connectToRealBrowser() {
  const { connect } = await import('puppeteer-real-browser');
  return connect;
}

// later
let connect = await connectToRealBrowser();
const response = await connect({
   headless: 'auto', args: [], customConfig: {}, skipTarget: [],
   fingerprint: true, turnstile: true, connectOption: {}
});

let { page, browser setTarget } = response;

page.goto('https://nopecha.com/demo/cloudflare', {
   waitUntil: 'domcontentloaded'
})

Thanks again.

  var response = null
    try{
      response = !!target.url()
    }catch{
      return false
    }

You can try to use it this way. I have not encountered this error before, but I am looking for a different solution instead of targetFilter.
For your 2nd question, yes you can use it. There will be no problem.
targetFilter is causing a lot of problems. Currently most of the active issues are caused by targetFilter. I will definitely try to find a different solution for this problem in the future.
You are welcome

Thank you. I've got it working when I create a new project/folder and use this code:
(async () => {
  const { connect } = await import('puppeteer-real-browser');

  connect({
      tf: true, // If a feature you want to use at startup is not working, you can initialize the tf variable false and update it later.
      turnstile: true
  })
  .then(async response => {
          const { page, browser, setTarget } = response

          page.goto('https://nopecha.com/demo/cloudflare', {
              waitUntil: 'domcontentloaded'
          })

          setTarget({ status: false })

          let page2 = await browser.newPage();

          setTarget({ status: true })

          await page2.goto('https://nopecha.com/demo/cloudflare');
  })

  // Use connect as needed here
})();

But when trying to implement it in an existing project (in addition to chrome-aws-lambda which I currently use) I get an error:
var response = !!target.url()
                            ^
TypeError: target.url is not a function

I added a console.log before this line and in the existing project it shows:
target:  {
  targetId: '7665528686C39479243B434C8669808C',
  type: 'page',
  title: 'about:blank',
  url: 'about:blank',
  attached: true,
  canAccessOpener: false,
  browserContextId: '8B0D38451DDF4A5431CF6C4DCFCB806A'
}

While in the new project is shows:
target:  CdpTarget {
  _initializedDeferred: Deferred {},
  _isClosedDeferred: Deferred {},
  _targetId: '84a3c50a-aa77-45cc-8bf3-17dec5ab7c0d'
}
target:  CdpTarget {
  _initializedDeferred: Deferred {},
  _isClosedDeferred: Deferred {},
  _targetId: '865AA8E483FA9DD16AB482B73A7FEC2F'
}

(and more of the same)

Exact same code example just in different folders. May the dependencies of my existing project be conflicting?
And one more question. Can we use async rather than the .then method provided in the example? For example, like this:
async function connectToRealBrowser() {
  const { connect } = await import('puppeteer-real-browser');
  return connect;
}

// later
let connect = await connectToRealBrowser();
const response = await connect({
   headless: 'auto', args: [], customConfig: {}, skipTarget: [],
   fingerprint: true, turnstile: true, connectOption: {}
});

let { page, browser setTarget } = response;

page.goto('https://nopecha.com/demo/cloudflare', {
   waitUntil: 'domcontentloaded'
})

Thanks again.

  var response = null
    try{
      response = !!target.url()
    }catch{
      return false
    }

You can try to use it this way. I have not encountered this error before, but I am looking for a different solution instead of targetFilter.
For your 2nd question, yes you can use it. There will be no problem.
targetFilter is causing a lot of problems. Currently most of the active issues are caused by targetFilter. I will definitely try to find a different solution for this problem in the future.
You are welcome

Just a followup question regarding xvfb, I've been trying to get this running on an aws lambda, with custom container image that has xvfb installed, sadly its not working. My guess is xvfb is not designed to work in server-less functions

Just a followup question regarding xvfb, I've been trying to get this running on an aws lambda, with custom container image that has xvfb installed, sadly its not working. My guess is xvfb is not designed to work in server-less functions

https://github.com/zfcsoftware/puppeteer-real-browser/blob/main/Dockerfile
I haven't tried running it on Aws, but this dockerfile worked fine on my private servers and google cloud run. Aws may not allow xvfb to be installed correctly. I recommend using google cloud run. I will try and run it on aws when I have time.

@humanismusic I'm currently encountering the exact same problem you're facing. Need to run a simple puppeteer script on cloud functions but cloudflare turnstile blocks me on login page.
Running the script in headless:true blocks me from accessing the page and headless:false is a no go without xvfb on cloud functions.
Any progress on the issue?

@devanshug2910  I have not had time to try with Google cloud run, but looks like that's the way to go. There's a few more steps vs cloud functions but nothing to complicated it seems: https://cloud.google.com/run/docs/deploying-source-code.

Running this on GCP, what am I doing wrong?

Running this on GCP, what am I doing wrong?

https://github.com/zfcsoftware/puppeteer-real-browser/blob/main/Dockerfile
If you are running with Google Cloud run using this Dockerfile, the problem might be resource consumption. You should make request 1 per instance. You should make cpu 1 ram 1 per instance.

I forked your project, and edited the following to run on cloud run - https://github.com/robtec/puppeteer-real-browser/blob/main/src/test.js
I've set cpu to 1 and ram to 2gb

I forked your project, and edited the following to run on cloud run - https://github.com/robtec/puppeteer-real-browser/blob/main/src/test.js
I've set cpu to 1 and ram to 2gb
You should not do it in while true.
https://gist.github.com/zfcsoftware/0deded42bba6505b714bab0f185e0508
Please try the code above.

After a few tweaks it worked. Thank you for your help


linuxdoc dependency documentation

mmlib documentation generation depends on MindMaze's fork of linuxdoc: https://github.com/mmlabs-mindmaze/linuxdoc
The documentation should be updated to make it known.
Also, let's think about disabling documentation generation by default (and enabling it in the CI instead).

Documentation generation is enabled automatically if possible, and disabled silently otherwise since 8ec3881a0cd11e04f594debd0ab26ecb21abc833
Doc has been updated in aad328fba574da35ccc0200b0904d28b14ab8053


NCDA - SPV report combined with NCDA scoreboard

#513

Patient record:

SPV report:

@AronNovak please review


Available PYPs

Hi, may I know if I am able to find more of the PYPs anywhere? Thanks!

you can check the nus library exam paper repository from here

Hi i think most of the pyp are on cs2030s

hi! I do have a few PYPs from my seniors (some with solutions) ! feel free to pm me if you want them for extra practice!! all the best for finalsss :-))

@jodytng do you mind sending them to me? thanks!


Get home folder without promises

Codecov Report

Merging #1086 into master will decrease coverage by 0.31%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master   #1086      +/-   ##
=========================================
- Coverage   93.11%   92.8%   -0.32%
=========================================
  Files          39      39
  Lines        4273    4338      +65
  Branches      470     738     +268
=========================================
+ Hits         3979    4026      +47
+ Misses        294     291       -3
- Partials        0      21      +21

Impacted Files
Coverage Δ

browser/services/platform.js
98.85% <100%> (+0.08%)
:arrow_up:

browser/pages/location/controller.js
96.05% <100%> (+3.64%)
:arrow_up:

browser/services/data.js
91.5% <100%> (-0.9%)
:arrow_down:

browser/model/devstudio-autoinstall.js
97.29% <0%> (-2.71%)
:arrow_down:

browser/model/helpers/hash.js
85.29% <0%> (-2.59%)
:arrow_down:

browser/pages/install/controller.js
79.85% <0%> (-1.73%)
:arrow_down:

browser/model/helpers/downloader.js
96.13% <0%> (-1.66%)
:arrow_down:

browser/main.js
95.58% <0%> (-1.39%)
:arrow_down:

browser/pages/account/controller.js
82.11% <0%> (-1.33%)
:arrow_down:

browser/model/jbossfusekaraf.js
95.09% <0%> (-0.83%)
:arrow_down:

... and 20 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 e9eebf3...22ed890. Read the comment docs.


Duplicate primary key error returned when saving unmodified object

GORM Playground Link

https://github.com/go-gorm/playground/pull/582
Description

I also encountered the same error. When I using Save method to save the unmodified object I will get the below error.
Error 1062 (23000): Duplicate entry 'xxx' for key 'PRIMARY'.
Confusingly, this occurs in the concurrent case, but not in the serial case.

I think we should revert commit f387433. Before the commit, Save function will examine whether the record exists and only insert it when non-exist.  @jinzhu

It was fixed in #6149  and just merged.

MySQL MariaDB database, same problem.
Save() does not work from version 1.24.6 to latest.
The latest version in which Save() works is v1.24.5.

MySQL MariaDB database, same problem. Save() does not work from version 1.24.6 to latest. The latest version in which Save() works is v1.24.5.
This change has led to problems with the Save() function: f387433

This issue has been fixed in the master branch.


Fault injection and URI rewrite for "self-routing" VirtualService do not work as expected

Bug description
As described in title - fault injection and URI rewrite don't work for "self-routing" VirtualService (ie. both host and destination values are the same).
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Steps to reproduce the bug
Assume there is a Service, dummy-service, that doesn't have any backing pods/endpoints as such:
apiVersion: v1
kind: Service
metadata:
  name: dummy-service
  namespace: services
spec:
  type: ClusterIP
  ports:
    - port: 80
      protocol: TCP
      name: http

Create VS virtualservice-one which routes from the ingressgateway to dummy-service.
apiVersion: networking.istio.io/v1beta1
kind: VirtualService
metadata:
  name: virtualservice-one
  namespace: services
spec:
  gateways:
    - web
  hosts:
    - myhost.com
  http:
    - match:
        - uri:
            exact: /test
      route:
        - destination:
            host: dummy-service.services.svc.cluster.local

Create another VS, virtualservice-two, which is a "self-routing" VS similar to how we configure retries (see https://istio.io/latest/docs/concepts/traffic-management/#retries). This VS uses fault injection to force the return of a 404 http status.
apiVersion: networking.istio.io/v1beta1
kind: VirtualService
metadata:
  name: virtualservice-two
  namespace: services
spec:
  hosts:
    - dummy-service.services.svc.cluster.local
  http:
    - match:
        - uri:
            exact: /test
      fault:
        abort:
          percentage:
            value: 100
          httpStatus: 404
      route:
        - destination:
             host: dummy-service.services.svc.cluster.local

Make an HTTP call to myhost.com/test, and we receive 503 with flag UH, which means fault injection didn't take place.
The same behaviour applies even if dummy-service was replaced by an actual Kubernetes Service with backing endpoints. In that case instead of receiving a 503 UH, we get the same results as we do when we hit /test on the Service. Eg. Receiving 403 RBAC: access denied if we didn't allow the ingressgateway proxy to hit the /test route on the service's proxy.
Additionally, apart from just fault injection, rewrite does not work as well when it is configured in the second VS.
Does this mean that apart from the retry settings, other settings wouldn't work for "self-routing" VS?
Version
Istio
client version: 1.7.4
control plane version: 1.6.13-2259094caeb07b4cf631c99b71ea4a9d3840aa4e
data plane version: 1.6.13 (30 proxies)

Kubernetes: Client Version: v1.16.15
How was Istio installed?
Using istioctl install
Environment where bug was observed (cloud vendor, OS, etc)
AWS EKS

Your virtualservice-two is not on the web Gateway.  It will only be seen be calls within the mesh.

Hi @esnible, thanks for pointing that out! I've added the web Gateway to my virtualservice-two but it still doesn't seem to work as well (both for rewrite and fault injection). When I inspect the routes config for the proxy of my ingressgateway pod, I don't see the fault injection for the /test-cat route at as well.


[OAP-CACHE] Backport 0.7 to 0.8 on April 20th

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

cc @yma11 @HongW2019

@yma11 @HongW2019 Please check it.

LGTM.

LGTM +1


WIP feat(relation-widget): add filter property

Closes #3816.
WIP. Don't merge just yet.
Summary

[X] Add filters property to relation widget
[X] Extract filter logic to lib-widget
[ ] Unify with filter handling for view_filters (#3741)
[ ] Write tests
[ ] Document usage

Test plan
Additional unit tests in the relation widget test spec and new unit tests for filter logic in the lib.

A picture of a cute animal (not mandatory but encouraged)

@hanneskuettner, thanks for this. I'm closing as stale, please re-open/comment when you're ready to continue it.


Update sync_partner_contract

Following #105

It seems that also the function internal_lock_update needs to be updated if we want also our internal Locked event to contain the lock period:
Self::deposit_event(Event::Locked { eth_key: sender, balance: amount });
Should we add this information in it too?


update main example to use eager API

main example reflects one intended use of pipe

Codecov Report
Patch and project coverage have no change.

Comparison is base (19dc125) 99.60% compared to head (b291835) 99.60%.

:exclamation: Current head b291835 differs from pull request most recent head e69a290. Consider uploading reports for the commit e69a290 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #244   +/-   ##
=======================================
  Coverage   99.60%   99.60%
=======================================
  Files         224      224
  Lines        3266     3266
=======================================
  Hits         3253     3253
  Misses         13       13

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Fix a bunch of unhandled errors

...as discovered by "gosec" (many other ones reported, but not all make
a lot of sense to fix).
Signed-off-by: Julius Volz<EMAIL_ADDRESS>

@juliusv @stuartnelson3 What are your thoughts on including https://github.com/kisielk/errcheck in our CI runs?

My initial reaction is that it's probably not necessary. For a project that doesn't have a ton of contributors, I'm guessing we would spend more time dealing with special cases than actual value from this. Is it in CI for prometheus?

Yeah, so gosec also does these checks and produced a ton of errors that I didn't choose to fix because it was either obviously not sensical (like checking the error return of every logging call) or I wasn't sure whether it would make sense. errcheck has a function exclusion list, which would get rid of this, if someone wants to do it and maintain that list.


Chocolatey deploy fix

closes #49

@nex3 Great question. When you deploy a package to Chocolatey, they run a validation script about some things that could be missing. One of them is this verification file, here is the error that shows up without it.
https://github.com/chocolatey/package-validator/wiki/VerificationFileMissing
You can use this to do checksum, but it is optional.
TLDR; It's optional to have checksum verification, but the validator does ask for this file.

@nex3 I believe this needs to be made as a parameter similar to the nuspec file later. I can try to take a look at this at a later time. But I believe you still need a VERIFICATION file even if it's empty.

Looking at that link, it seems like this is intended to be a human-readable file that describes how binary files were generated. In our case, the only "binary" is the zip file containing the package's source code. I wonder if it would be easier to just include the source files directly, since the .nupkg is already a zip file, and avoid needing a VERIFICATION file at all.

If we able to avoid I think it would be great. Makes things a bit cleaner.

@nex3 Please let me know if you want me to try to take a look at your suggestion. Wasn't sure what the next steps are.

Oh I'm sorry, I should have been more clear. Could you modify the code to copy in each source file directly to the Chocolatey package rather than creating a zip file containing all of them?

It looks like the tests are failing...

@nex3 This seems weird. For me it seems that master is also not passing the tests.
This PR https://github.com/google/dart_cli_pkg/pull/59 shows that it did not pass CI for me. Could this have something to do with it?

master seems to be passing on Travis.

This PR #59 shows that it did not pass CI for me. Could this have something to do with it?

I'm not sure why it's not showing up on GitHub, but its build did succeed.

hmm ok will dig deeper

Good news. Silly mistake. Will review the Chocolatey submission process to make sure we are good to go.
However tests still fail on my local windows machine, but it happens on master also, so will check it out later and open another PR if anything.

All validations passed on Chocolatey


New feature: Sound Effects

Proposal:

https://github.com/bbcmicrobit/micropython/pull/753

@dpgeorge let me know if there is anything I can do to facilitate this.

See #106 for an initial implementation.  It's on the audio-sound-effect branch in this repo.

Implemented in 9a5958bbe41dc05ef93a338ff08d4fcc2ef5d886 and 822b3c9e88f6f3faa4af458db7e35e1a818882de

Thanks Damien! I've created https://github.com/microbit-foundation/micropython-microbit-v2/issues/110 to capture the Foundation task to create the predefined SoundEffects.


Updated description.

Just updating the description of the job. Looked like a cut & paste error.

@mikewo,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@mikewo - thanks for the update!


Updates for mc mirror parameters

Closes #1270

Adds some missing parameters to the syntax list.
Adds the --active-active parameter.

Staged:

mc mirror

Note:
mc mirror also has the --encrypt-key parameter that has been replaced.
Those are addressed in #1295.


Fix Durable Object Counter example for concurrent use.

This probably deserves an explainer, I just wanted to get this up before I forgot.
Before this change, concurrent requests to the Actor could easily return some other request's incr/decr'd this.value, after awaiting their own storage.put.

can we do an update to the docs as well w/ the explainer?

Yeah, I'll flesh one out after I finish this other task.

Heh, I guess whether or not this is a bug depends on the use case. If you're trying to assign a unique number to each caller, it's a bug. If you're trying to measure how many times a thing has happened, it's not a bug -- though your fix doesn't hurt.

Yeah, mostly it's that a user tried to load test it and was confused by seeing duplicates on the client side.

@greg-mckeon I added a little explainer, feel free to merge if it works for you.


Moving .cs file in editor clobbers .csproj compile includes

Godot version:
3.2.3 stable.mono.official
OS/device including version:
Windows 10 x64
Issue description:
I have a somewhat lazily customized csproj file which includes all files without having to deal with the "fragility" of Godot's handling of includes.  To handle adding new .cs files to my project, I've included this line:
  <ItemGroup>
    <Compile Include="**\*.cs" />
  </ItemGroup>

This usually survives changes and upgrades to the project format, however, I noticed that moving a cs file in the editor disregards this customization.  The behavior is that it will remove the above snippet and replace it with one including only the moved file.  This obviously breaks a lot of things.  Not sure if I'm using an unrecommended way to include files in my project, but it's easier than forcing myself to create every new cs file in godot when I'd rather just be lazy and do it in vscode.
Steps to reproduce:

Modify a CSProj file where the compile includes itemGroup contains only the above snippet.
In the Godot editor, try moving one of your scripted cs files, the kind that is already linked to a node in the project, to trigger a refactor.
Check csproj file

Minimal reproduction project:

Update:  The default project template seems to have changed a lot between versions 3.2.2 and 3.2.3 and I should note that this requires a project file which has     <EnableDefaultCompileItems> set to false.  This is still not an uncommon scenario when a project has script templates, since these need to be manually excluded from the project.

This issue has returned as of 3.4.3 stable.  The conditions to get it to occur are to simply create a new C# script file.  I normally don't create new scripts from Godot unless I need to use a script template, so I didn't notice the issue before.  I've had to set my csproj file to read-only as a temporary workaround.  Doing this throws up the following message when creating a new script:
 modules/mono/mono_gd/gd_mono_utils.cpp:369 - System.UnauthorizedAccessException: Access to the path "D:\redacted\PhaseEngine.csproj" is denied.
 modules/mono/editor/csharp_project.cpp:64 - Method failed.

Don't know if that will help pinpoint the regression.

I have been unable to reproduce it in 3.4.3 stable.
The code for AddItemToProjectChecked that gets executed when a new script is created checks if there is an item in the csproj that includes the file to be added and if that's the case it won't modify the csproj (so if you have a glob path that already satisfies the path of the newly created script it won't be added to the csproj, otherwise its path will be added).
Also, the code in that file (ProjectUtils) hasn't really been modified since my PR that fixed this issue 5 months ago so it seems odd that it will break without any changes. This means the issue you are describing could be something that I missed or a new/different issue so my PR didn't fix it. Since I don't seem to be able to reproduce it or maybe I'm misunderstanding the steps to do so, could you describe once again the steps required to reproduce this issue in as much detail as you can?
In order to make reproducing the issue easier it'd be great to have a minimal reproduction project that represents the initial state of the project (a simple project with a csproj in its initial state that already contains the compile items with globbing), the csproj in its final state after Godot modifies it (the incorrect result) and the expected csproj (what you expected Godot to do after following the reproduction steps).
After following the steps (I assume it'd be something like adding a C# script in a specific folder that is not included by the glob path) I should get the same csproj as the one that was provided for the final state instead of the one provided as the expected csproj.

Having said all that, if all you need is to exclude some files have you considered adding them to the DefaultItemExcludes? That would allow you to keep EnableDefaultCompileItems enabled and still exclude certain scripts from the compilation. Here is an example:
<Project Sdk="Godot.NET.Sdk/3.3.0">

  <PropertyGroup>
    <TargetFramework>net472</TargetFramework>
  </PropertyGroup>

  <!-- Exclude templates -->
  <PropertyGroup>
    <DefaultItemExcludes>$(DefaultItemExcludes);script_templates/*.cs</DefaultItemExcludes>
  </PropertyGroup>

</Project>

MinimalCSharpProject.zip
Sincerest apologies, I'm currently suffering from some connectivity issues that will make it difficult to address things for the next few days. I'm attempting to attach a minimal reproduction project to this comment.  I may try modifying my project to implement your suggestions, but solving this issue is still important to me.
This project should be set up correctly to replicate the issue. To reproduce it you can do one of two things, and the issues may not be the same but are definitely related. The first is to tried deleting new_script.cs from the editor in the icon view.  This should delete line 8 of the project file.
The second way to reproduce the issue is also from the editors icon item list for the file system.  Right click and select new script.  Select language as c sharp, and use one of the project templates to create another script.  This should replace line 8 with a compiler include reference to the script.

Thank you, I can reproduce the issue with the provided steps.

@nobuyukinyuu I believe #59521 should fix the issue for the two reproduction steps you mentioned.


Add website and description

Currently there is not a description for this repo, as well as a website. I would add the website as the official duck.js landing page.

Done, feel free to edit the description if you see fit.


Tree Shaking isn't working as (I) expected

Prior to stating the issue I want to say that the reason I have installed this package is I am trying to replace our custom icons from https://www.github.com/MerlinLabs/styled-material-components with yours. Also I am currently rewriting the library build process to get tree shaking working. I have been down a rabbit hole and even created a whole new package to test how Tree shaking works in general.
What i've noticed so far...as soon as you introduce styled-components into a file tree shaking fails entirely for that file. I was using your code to forensic analyze my process and realized that tree shaking doesn't work with styled-icons with current version of styled-components (3.4.5, not 4) and create react app.

import React, { Component } from 'react';
import { NewPkgTest } from 'new-pkg';
import { AccountCircle } from 'styled-icons/material';
import logo from './logo.svg';
import './App.css';

class App extends Component {
  render() {
    return (

      <AccountCircle />

Welcome to React

          To get started, edit src/App.js and save to reload.

        <NewPkgTest />

    );
  }
}

export default App;

The only file I have modified from the default create react app stack is the App.js file. I imported a single Icon from the material sub import and it includes all of the material icons in the generated bundle.
In dev mode it looks like the tree shaking is actually working so far as adding the comment to mark unused modules:
/***/ "./node_modules/styled-icons/material/Add.js":
/*!***************************************************!*\
  !*** ./node_modules/styled-icons/material/Add.js ***!
  \***************************************************/
/*! exports provided: Add, AddDimensions */
/***/ (function(module, __webpack_exports__, __webpack_require__) {

"use strict";
/* unused harmony export Add */
/* unused harmony export AddDimensions */

Can you provide me any help figuring this out? Would love to include styled-icons in our library and get our library figured out so tree shaking doesn't result in a huge bundle.

Hey @brad-decker sorry for the late reply - do you have a sample repo or more information about your build environment?  If you are using Webpack 4 tree shaking should work out of the box, and other environments have their own requirements.  I'd be happy to take a look and we should be able to get everything working.
As a side note, the unused harmony export does indicate an export is unused, but won't be sufficient for Uglify to perform the tree shaking - for that, the builder would emit a /*#__PURE__*/ comment, which authorizes Uglify to remove the unused code.

I'm going to close this - if you're using Create React App things will be smoother with CRA v2, and if you're using Gatsby, things will also be smoother with v2.  If just plain Webpack, you should be on Webpack 4 and should not be transpiling ES modules before they arrive at Webpack (i.e. babel should be emitting modules).  Otherwise if that's not an option, the .cjs imports should work, they're just less ergonomic.
Feel free to post back with more details if you'd like though and I'd be happy to check them out!

Yep, if you transpile to CommonJS before Webpack or Rollup or your bundler are able to parse the code, it won't be able to apply the ES modules tree shaking.  Webpack 4 (and therefore Create React App v2+ and Gatsby v2+) and Rollup are able to handle this out of the box.


Changing to MIT license

Heya!
As you might be aware of I forked your project quite some time ago and it has grown to something completely different 😅
Would it be OK if I swap to MIT license?
Thanks for your time.

Is okay for me. I changed it in b5b863e. :)


fix: transaction builder no_input_to_cover_fees

The function no_spendable_input was not checking if the asset_id was the base asset. Coins with other asset_ids can not be used to cover the tx fee.

[x] I have added necessary labels.
[x] I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
[x] I have requested a review from the relevant team or maintainers.

Guys, when do you plan to release this fix?

Guys, when do you plan to release this fix?

It's been published just now: https://github.com/FuelLabs/fuels-rs/releases/tag/v0.55.1


Maxed Social Link dissapeared

Firstly, thank you very much for your hardwork :+1:
And the problem:

Maxed Social link not appeared in the Social Link tab.
Also, after editing and saving the save, loading it again makes the coressponding NPC of the dissapeared Social Link untalkable in the game ( press X but no dialogue)

I'm using Vitamin 1.1 Undub dump if it helps.
The original save file with Chie and Yukiko maxed Social Link:
data0002.zip

Didn't notice this was here whoops lol, I'll look into it.

Similar issue. Chariot, Lovers, and Sun all disappeared. I can add them back manually, but cant get chariot or lovers past level 8, and sun is stuck at level 1.


Update user stories

Once we have decided on our final set of features based on user stories in our meeting, it may be applicable to make any necessary updates to the user stories in the DG. We may categorise them based on whether they were implemented or not.
We may also consider whether any should be documented in the UG / DG category as "coming in a future version", as this may save us during grading. (Guidelines for determining bugs @ https://nus-cs2103-ay2324s1.github.io/website/schedule/week10/project.html.)

From our meeting, we have decided to keep only all the user stories for existing features (green tick in Telegram image), as well as the good ones we picked out (bottom section of image). The rest, including the duplicate, may be removed.
We will need to update user story contents (refer to the new text in their filed issues).

Moving to the last milestone.


Aggregations aren't being serialized when filtered

When trying to serialize a search response using IElasticsearchSerializer, no aggregations are being returned just an empty object in the outputted json.
The aggregations return correctly to the code and are serialized into the class correctly but not out. It serializes correctly when not using a filter aggregation.
Small example
{
  "query": {
    "match_all": {}
  },
  "aggs": {
    "results": {
      "filters": {
        "filters": {
          "filtered": {
            "terms": {
              "my_filter": [
                1
              ]
            }
          }
        }
      },
      "aggs": {
        "distilleries": {
          "terms": {
            "field": "some_field",
            "size": 5
          }
        }
      }
    }
  }
}

Results
{
  "_shards": {
    "total": 1,
    "successful": 1,
    "failed": 0
  },
  "hits": {
    "total": 37130,
    "max_score": 1,
    "hits": [ "... removed for brevity ..." ]
  },
  "aggregations": {
    "results": {}
  },
  "took": 4,
  "timed_out": false,
  "terminated_early": false,
  "highlights": {}
}

@Romanx using a filtered query in the filters aggregation isn't necessary, and doesn't really make sense.  In your case, you can just use a terms filter directly.
Also, the filtered query has been deprecated in 2.0 and can be replaced with a bool query (with a must and filter clause).
That said, I can't quite reproduce this...are you getting results if you run the raw JSON directly against ES (not using NEST)?.

Closing.  Feel free to re-open if this is still an issue @Romanx.


libvirt provider fails with ssh.publicKeyCallback.auth if the SSH key is invalid

System Information
Linux distribution
CentOS stream 9
Terraform version
# terraform -v
Terraform v1.7.5
on linux_amd64

Provider and libvirt versions
0.7.6

Checklist

[ ] Is your issue/contribution related with enabling some setting/option exposed by libvirt that the plugin does not yet support, or requires changing/extending the provider terraform schema?

[ ] Make sure you explain why this option is important to you, why it should be important to everyone. Describe your use-case with detail and provide examples where possible.
[ ] If it is a very special case, consider using the XSLT support in the provider to tweak the definition instead of opening an issue
[ ] Maintainers do not have expertise in every libvirt setting, so please, describe the feature and how it is used. Link to the appropriate documentation

[ ] Is it a bug or something that does not work as expected? Please make sure you fill the version information below:

Description of Issue/Question
Setup
We recently encrypted our SSH keys in our git repo using git-crypt, and when the libvirt provider tried to load it in its crypted state, if failed with a very long and cypted stack trace.
I know that it expected to fail, I just think it should be more informative and give the user a better error message, about the issue that the lib failed to load the SSH key.
Steps to Reproduce Issue
[2024-03-19T09:11:05.546Z]     Planning failed. Terraform encountered an error while generating this plan.
[2024-03-19T09:11:05.546Z]
[2024-03-19T09:11:05.546Z]
[2024-03-19T09:11:05.546Z]
[2024-03-19T09:11:05.546Z]     STDERR:
[2024-03-19T09:11:05.546Z]     Error: Plugin did not respond
[2024-03-19T09:11:05.546Z]
[2024-03-19T09:11:05.546Z]       with provider["registry.terraform.io/dmacvicar/libvirt"],
[2024-03-19T09:11:05.546Z]       on config.tf line 44, in provider "libvirt":
[2024-03-19T09:11:05.546Z]       44: provider "libvirt" {
[2024-03-19T09:11:05.546Z]
[2024-03-19T09:11:05.546Z]     The plugin encountered an error, and failed to respond to the
[2024-03-19T09:11:05.546Z]     plugin.(*GRPCProvider).ConfigureProvider call. The plugin logs may contain
[2024-03-19T09:11:05.546Z]     more details.
[2024-03-19T09:11:05.546Z]
[2024-03-19T09:11:05.546Z]     Stack trace from the terraform-provider-libvirt_v0.6.14 plugin:
[2024-03-19T09:11:05.546Z]
[2024-03-19T09:11:05.546Z]     panic: runtime error: invalid memory address or nil pointer dereference
[2024-03-19T09:11:05.546Z]     [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x6812ea]
[2024-03-19T09:11:05.546Z]
[2024-03-19T09:11:05.546Z]     goroutine 27 [running]:
[2024-03-19T09:11:05.546Z]     golang.org/x/crypto/ssh.publicKeyCallback.auth(0x11, {0xc00018b340, 0x20, 0x20}, {0xc00041460b, 0x4}, {0xfaed10, 0xc0001a8f00}, {0xf9f480, 0xc000092600})
[2024-03-19T09:11:05.546Z]             golang.org/x/crypto@v0.0.0-20220112180741-5e0467b6c7ce/ssh/client_auth.go:235 +0x24a
[2024-03-19T09:11:05.546Z]     golang.org/x/crypto/ssh.(*connection).clientAuthenticate(0xc0000f7000, 0xc0000de540)
[2024-03-19T09:11:05.546Z]             golang.org/x/crypto@v0.0.0-20220112180741-5e0467b6c7ce/ssh/client_auth.go:63 +0x3a9
[2024-03-19T09:11:05.546Z]     golang.org/x/crypto/ssh.(*connection).clientHandshake(0xc0000f7000, {0xc0001dc0f0, 0x11}, 0xc0000de540)
[2024-03-19T09:11:05.546Z]             golang.org/x/crypto@v0.0.0-20220112180741-5e0467b6c7ce/ssh/client.go:113 +0x26a
[2024-03-19T09:11:05.546Z]     golang.org/x/crypto/ssh.NewClientConn({0xfc3a48, 0xc00000f058}, {0xc0001dc0f0, 0x11}, 0xc0004eb800)
[2024-03-19T09:11:05.546Z]             golang.org/x/crypto@v0.0.0-20220112180741-5e0467b6c7ce/ssh/client.go:83 +0x12b
[2024-03-19T09:11:05.546Z]     golang.org/x/crypto/ssh.Dial({0xe238f1, 0x5}, {0xc0001dc0f0, 0x11}, 0xc0004eb800)
[2024-03-19T09:11:05.546Z]             golang.org/x/crypto@v0.0.0-20220112180741-5e0467b6c7ce/ssh/client.go:190 +0x59
[2024-03-19T09:11:05.546Z]     github.com/dmacvicar/terraform-provider-libvirt/libvirt/uri.(*ConnectionURI).dialSSH(0xc0004eb9c8)
[2024-03-19T09:11:05.546Z]             github.com/dmacvicar/terraform-provider-libvirt/libvirt/uri/ssh.go:130 +0x465
[2024-03-19T09:11:05.546Z]     github.com/dmacvicar/terraform-provider-libvirt/libvirt/uri.(*ConnectionURI).DialTransport(0xc000414600)
[2024-03-19T09:11:05.546Z]             github.com/dmacvicar/terraform-provider-libvirt/libvirt/uri/connection_uri.go:83 +0x45
[2024-03-19T09:11:05.546Z]     github.com/dmacvicar/terraform-provider-libvirt/libvirt.(*Config).Client(0xe4d2b3)
[2024-03-19T09:11:05.546Z]             github.com/dmacvicar/terraform-provider-libvirt/libvirt/config.go:35 +0x73
[2024-03-19T09:11:05.546Z]     github.com/dmacvicar/terraform-provider-libvirt/libvirt.providerConfigure(0xc0001aac40)
[2024-03-19T09:11:05.546Z]             github.com/dmacvicar/terraform-provider-libvirt/libvirt/provider.go:68 +0xff
[2024-03-19T09:11:05.546Z]     github.com/hashicorp/terraform-plugin-sdk/helper/schema.(*Provider).Configure(0xc0000f6900, 0xc00000eff0)
[2024-03-19T09:11:05.546Z]             github.com/hashicorp/terraform-plugin-sdk@v1.9.0/helper/schema/provider.go:275 +0xb4
[2024-03-19T09:11:05.546Z]     github.com/hashicorp/terraform-plugin-sdk/internal/helper/plugin.(*GRPCProviderServer).Configure(0xc00000ec58, {0xc0001815c0, 0x516766}, 0xc0001815c0)
[2024-03-19T09:11:05.546Z]             github.com/hashicorp/terraform-plugin-sdk@v1.9.0/internal/helper/plugin/grpc_provider.go:487 +0x1d2
[2024-03-19T09:11:05.546Z]     github.com/hashicorp/terraform-plugin-sdk/internal/tfplugin5._Provider_Configure_Handler({0xdf5140, 0xc00000ec58}, {0xfb64b0, 0xc0001a48d0}, 0xc00019b020, 0x0)
[2024-03-19T09:11:05.546Z]             github.com/hashicorp/terraform-plugin-sdk@v1.9.0/internal/tfplugin5/tfplugin5.pb.go:3251 +0x170
[2024-03-19T09:11:05.546Z]     google.golang.org/grpc.(*Server).processUnaryRPC(0xc000106780, {0xfc3c00, 0xc000106900}, 0xc0000ed300, 0xc0004d53e0, 0x155bf38, 0x0)
[2024-03-19T09:11:05.546Z]             google.golang.org/grpc@v1.27.1/server.go:1024 +0xd1e
[2024-03-19T09:11:05.546Z]     google.golang.org/grpc.(*Server).handleStream(0xc000106780, {0xfc3c00, 0xc000106900}, 0xc0000ed300, 0x0)
[2024-03-19T09:11:05.546Z]             google.golang.org/grpc@v1.27.1/server.go:1313 +0xa56
[2024-03-19T09:11:05.546Z]     google.golang.org/grpc.(*Server).serveStreams.func1.1()
[2024-03-19T09:11:05.546Z]             google.golang.org/grpc@v1.27.1/server.go:722 +0x98
[2024-03-19T09:11:05.546Z]     created by google.golang.org/grpc.(*Server).serveStreams.func1
[2024-03-19T09:11:05.546Z]             google.golang.org/grpc@v1.27.1/server.go:720 +0xef
[2024-03-19T09:11:05.546Z]
[2024-03-19T09:11:05.546Z]     Error: The terraform-provider-libvirt_v0.6.14 plugin crashed!
[2024-03-19T09:11:05.546Z]
[2024-03-19T09:11:05.546Z]     This is always indicative of a bug within the plugin. It would be immensely
[2024-03-19T09:11:05.546Z]     helpful if you could report the crash with the plugin's maintainers so that it
[2024-03-19T09:11:05.546Z]     can be fixed. The output above should help diagnose the issue.

Additional information:
The logs are from 0.6.14 but is happens with latest release as well.

Hi,
thanks for the report. I think this is legit improvement to provider.


[HUDI-1289] Remove shading pattern for hbase dependencies in hudi-spark-bundle

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contributing.html before opening a pull request.

What is the purpose of the pull request
Hbase index currently does not work due to relocation when only using hudi-spark-bundle
Brief change log

Update hudi-spark-bundle pom to not relocate hbase and htrace pattern
Remove codec relocation as this is not included in bundle which was causing error

Verify this pull request

Manually verified the change by running an insert on hbase index table through spark-shell using hudi-spark-bundle

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@rmpifer as a quick check, is it possible to shade all the deps of Hbase, leaving hbase classes themselves unshaded?  The most concern we have is around guava etc conflicting with what spark/presto use

@rmpifer if you can confirm the above, we can land this. otherwise LGTM

@rmpifer A couple of points:

As @vinothchandar mentioned, it would be worth exploring if by just removing the dependency relocation and still continuing to shade, helps avoid the issues with Hbase index, and at the same time not break bootstrap code.
If we do go ahead with removing relocation for Hbase, we may want to remove the relocation in hudi-hadoop-mr-bundle and hudi-presto-bundle to avoid any other issues this might cause. One such issue we ran into with bootstrap was that Hbase was writing the KeyValue Comparator class name in HFile footer. At read time it would expect to see the exact same class. However this was resolved by creating our own comparator class for Hbase. https://github.com/apache/hudi/blob/master/hudi-common/src/main/java/org/apache/hudi/common/bootstrap/index/HFileBootstrapIndex.java#L584
Lets fix the commit message. We are not removing shading, but avoiding relocation as part of shading process.

@vinothchandar Sorry I've been caught up in some other obligations. We would have to explicitly add the dependencies we want to shade from hbase. If the biggest concern is around guava conflicts I think we may just want to include this for now.
@umehrot2 I'm ok with updating this in hudi-hadoop-mr-bundle and hudi-presto-bundle as well as long as there are no other concerns there

@rmpifer  We might need to remove this hbase relocation from hudi-utilities-bundle as well. Ran into this issue  when using  DeltaStreamer without HBASE index and in EMR 5.31.0 with security configs. The job failed as soon as it started. Saw errors similar to https://github.com/apache/hudi/issues/2100 . But was able to quickly verify that on removing this relocation from   the hudi-utilities-bundle bundle, the job ran fine.


Panic: "Triangle edge index out of bounds"

I'm running into this panic:
thread '<unnamed>' panicked at 'Triangle edge index out of bounds.', /Users/jeff/.cargo/registry/src/github.com-1ecc6299db9ec823/ncollide3d-0.15.4/src/shape/triangle.rs:150:18
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::begin_panic
   6: <ncollide3d::shape::triangle::Triangle<N> as ncollide3d::shape::convex_polyhedron::ConvexPolyhedron<N>>::edge
   7: <ncollide3d::pipeline::narrow_phase::contact_generator::ball_convex_polyhedron_manifold_generator::BallConvexPolyhedronManifoldGenerator<N>>::do_update
   8: <ncollide3d::pipeline::narrow_phase::contact_generator::ball_convex_polyhedron_manifold_generator::BallConvexPolyhedronManifoldGenerator<N> as ncollide3d::pipeline::narrow_phase::contact_generator::contact_manifold_generator::ContactManifoldGenerator<N>>::update
   9: <ncollide3d::pipeline::narrow_phase::contact_generator::composite_shape_shape_manifold_generator::CompositeShapeShapeManifoldGenerator<N>>::do_update::{{closure}}
  10: <ncollide3d::shape::trimesh::TriMesh<N> as ncollide3d::shape::composite_shape::CompositeShape<N>>::map_transformed_part_at
  11: <ncollide3d::pipeline::narrow_phase::contact_generator::composite_shape_shape_manifold_generator::CompositeShapeShapeManifoldGenerator<N>>::do_update
  12: <ncollide3d::pipeline::narrow_phase::contact_generator::composite_shape_shape_manifold_generator::CompositeShapeShapeManifoldGenerator<N> as ncollide3d::pipeline::narrow_phase::contact_generator::contact_manifold_generator::ContactManifoldGenerator<N>>::update
  13: <ncollide3d::pipeline::narrow_phase::default_narrow_phase::DefaultNarrowPhase<N> as ncollide3d::pipeline::narrow_phase::narrow_phase::NarrowPhase<N, T>>::update
  14: <ncollide3d::pipeline::world::collision_world::CollisionWorld<N, T>>::perform_narrow_phase
  15: <nphysics3d::world::world::World<N>>::step
  16: <planetkit::nphysics::world_system::WorldSystem as shred::system::System<'a>>::run
  17: <T as shred::system::RunNow<'a>>::run_now
  18: rayon::iter::plumbing::bridge_producer_consumer::helper
  19: <rayon::iter::plumbing::bridge::Callback<C> as rayon::iter::plumbing::ProducerCallback<I>>::callback
  20: std::panicking::try::do_call
  21: __rust_maybe_catch_panic
  22: <rayon_core::job::StackJob<L, F, R> as rayon_core::job::Job>::execute
  23: rayon_core::registry::WorkerThread::wait_until_cold
  24: rayon_core::registry::main_loop
  25: std::panicking::try::do_call
  26: __rust_maybe_catch_panic
  27: <F as alloc::boxed::FnBox<A>>::call_box
  28: std::sys_common::thread::start_thread
  29: std::sys::unix::thread::Thread::new::thread_start
  30: _pthread_body
  31: _pthread_start

The relevant code in triangle.rs (https://github.com/sebcrozet/ncollide/blob/master/src/shape/triangle.rs#L145) looks like:
    fn edge(&self, id: FeatureId) -> (Point<N>, Point<N>, FeatureId, FeatureId) {
        match id.unwrap_edge() {
            0 => (self.a, self.b, FeatureId::Vertex(0), FeatureId::Vertex(1)),
            2 => (self.b, self.c, FeatureId::Vertex(1), FeatureId::Vertex(2)),
            3 => (self.c, self.a, FeatureId::Vertex(2), FeatureId::Vertex(0)),
            _ => panic!("Triangle edge index out of bounds."),
        }
    }

Now I assume I'm just getting confused about something, because there are web demos including meshes etc. that work just fine. However, I am using the same vertex and index data that I'm feeing into ncollide as I also use for a visual mesh (and it works fine for that), and those indices look strange.
Is there any chance this is a bug in fn edge?
If that "0, 2, 3" thing above is actually totally fine and I've misunderstood the intent, I can push the relevant part of my code somewhere. (It'll just be a bit of work to make a minimal reproduction, so figured I'd check this first.)

I'm surprised I did not run into this assertion earlier! This is a bug and should be "0, 1, 2" instead.

Well, that's the happiest possible outcome for me; it means I don't have to track down a mysterious bug in my code! 😎


Missing f prefix on f-strings fix

Fixes #21905

@code-review-doctor is there a way to generate a one-commit-per-rule PR from a specific set of rules that we'd like to apply? I could easily do that if one can run your tool locally.

@timabbott we have internal tools that can do that yep :)
send me an email to<EMAIL_ADDRESS>with what you need and we will do it

Done.

Closing as this isn't useful as written and we've likely done this using ruff transformers already.


Post Agent not working

Hi
First of all, love the project!
I have a problem using a post agent together with a self-hosted instance of browserless
Both hughinn and browserless run as docker containers on the same machine
The post requests towards browserless only fail if coming from huginn's post agent
Basically it seems that the post agent adds an &launch={} parameter at the end of the post string
I can show the difference between a successful request made from curl and the same request using the post agent
curl post request
curl -X POST http://LOCAL_BL_ADDRESS/content?token=MY_TOKEN \
 -H 'Content-Type: application/json' \
 -d '{
  "url": "https://www.google.com"
}'

post agent code
{
  "post_url": "http://LOCAL_BL_ADDRESS/content?token=MY_TOKEN",
  "content_type": "json",
  "method": "put",
  "payload": {
    "url": "https://www.google.com"
  },
  "headers": {},
  "emit_events": "true",
  "parse_body": "false",
  "no_merge": "true",
  "output_mode": "clean"
}

These are the results in the browserless log:

1 is the failed request with huginn
2 is the successful request with curl
The expected result would be to have the post string without &launch{} at the end
Thanks

[!NOTE]
Both LOCAL_BL_ADDRESS and MY_TOKEN are written in clear in the code. I just redacted them

I just ran into this issue, and I was able to fix it by using the following workaround: https://github.com/huginn/huginn/issues/2248#issuecomment-376879963.
For reference, this is my postAgent code:
{
  "post_url": "http://LOCAL_BL_ADDRESS/content",
  "content_type": "application/json",
  "method": "post",
  "payload": "{\"url\":  \"https://www.google.com\"}",
  "headers": {},
  "emit_events":  "true",
  "parse_body": "false",
  "no_merge": "true",
  "output_mode": "clean",
}

I tried with that solution, but I received this error in huginn

[!CAUTION]
1 error prohibited this Agent from being saved:

if provided, payload must be a hash or an array

I just wrapped the payload string with [ ]
{

    "payload": [
    "{\"url\": \"https://www.google.com\"}"
  ],

}

That said
The problem is still there
The post request is sent to http://LOCAL_BL_ADDRESS/content?token=MY_TOKEN&launch={} instead of http://LOCAL_BL_ADDRESS/content?token=MY_TOKEN

I got the same error when I used json as a content type instead of application/json. Have you tried with the following content type ?
{
    "content_type": "application/json",
}

In my case, this also fixes the problem with the post request.

Wow I completely missed it, now it works!!
So for future reference, it is necessary to use both
{

    "content_type": "application/json"
    "payload":  "{\"url\": \"https://www.google.com\"}"

}

using "content_type": "json" doesn't allow to fill the payload with just a string and causes &launch={} to pop up
Thanks @Galaxyor!


The uploadBytes function no longer returns the state in its response …

What's included?
When an issue was being reported an error was being displayed when a screenshot was being taken.
This was because the firebase api had changed and no longer passed back the 'state' in the response for the The uploadBytes function call.
Who should test?
✅ Product owner
✅ Developers
✅ UTG
How to test?

Click the 'Report An Issue' button
Take a screenshot and fiil in the rest of the form and submit it
You should see no errors about the screenshot upload

Risk - how likely is this to impact other areas?
🟢 No risk - this is a self-contained piece of work

PREVIEW:DEVELOP
can be OFF, DEVELOP or STAGING

@drieJAC Receiving this login error:

@drieJAC Receiving this login error:

This is a separate issue @nickaddy which @KoWeiJAC is looking into. For now we have manually added the preview link into the list of authorised domains so it will work now.


RailsAdmin::Extensions::PaperTrail::VersionProxy::AuditingAdapter can't modify frozen Hash

I've recently updated my Rails Admin project to https://github.com/sferik/rails_admin/commit/53eef4fe2ec0953381f4e3197c885adc0423dd49 and i've this error when i try to start the server:
➜  *** git:(master) ✗ rs
/Users/bci20/Sites/***/.gems/gems/bundler-1.12.5/lib/bundler/runtime.rb:89:in `rescue in block (2 levels) in require': There was an error while trying to load the gem 'rails_admin_history_rollback'. (Bundler::GemRequireError)
Gem Load Error is: can't modify frozen Hash
Backtrace for gem load error is:
/Users/bci20/Sites/***/vendor/ruby/2.3.0/gems/rails_admin_history_rollback-0.0.8/lib/rails_admin_history_rollback/extensions/paper_trail/auditing_adapter.rb:13:in `<class:AuditingAdapter>'
/Users/bci20/Sites/***/vendor/ruby/2.3.0/gems/rails_admin_history_rollback-0.0.8/lib/rails_admin_history_rollback/extensions/paper_trail/auditing_adapter.rb:12:in `<module:PaperTrail>'
/Users/bci20/Sites/***/vendor/ruby/2.3.0/gems/rails_admin_history_rollback-0.0.8/lib/rails_admin_history_rollback/extensions/paper_trail/auditing_adapter.rb:3:in `<module:Extensions>'
/Users/bci20/Sites/***/vendor/ruby/2.3.0/gems/rails_admin_history_rollback-0.0.8/lib/rails_admin_history_rollback/extensions/paper_trail/auditing_adapter.rb:2:in `<module:RailsAdmin>'
/Users/bci20/Sites/***/vendor/ruby/2.3.0/gems/rails_admin_history_rollback-0.0.8/lib/rails_admin_history_rollback/extensions/paper_trail/auditing_adapter.rb:1:in `<top (required)>'
/Users/bci20/Sites/***/vendor/ruby/2.3.0/gems/rails_admin_history_rollback-0.0.8/lib/rails_admin_history_rollback.rb:10:in `require'
/Users/bci20/Sites/***/vendor/ruby/2.3.0/gems/rails_admin_history_rollback-0.0.8/lib/rails_admin_history_rollback.rb:10:in `<top (required)>'

I think the problem comes from this commit:
https://github.com/sferik/rails_admin/commit/c94e36a983edd43d8fbbf6bd3243dee8c8844b19
How could we fix it ?
Note: I've rollback to rails_admin v1.0.0.rc to be able to start my project.
Note 2: I've finally rollback to rails_admin ~> 0.8.1 due to others bugs in the rc of Rails Admin.

@bricesanchez Thanks for reporting, I'll take a look at this ASAP.

Having this issue also!

@bricesanchez and @maxexcloo RailsAdmin released v1.0.0 yesterday. I have found and fixed the problem locally, so I'll publish a new version of my gem today and let you know!
Thanks for reporting this guys, really appreciated.

I've release v0.0.9 that solves this problem - update your gems and let me know if all is good your end!
Rikki


new support heroku-20

I tried to upgrade Heroku-20, but Graphviz doesn't support this, it's failed.

This has been automatically closed by the merged pull request #13.
@CyberRex0, if you can, please report if this fixes your problem.


Airbnb Style Guide

Normally we don't close until the PR gets merged just so you know for next time.

This needs to be rebased before a merge. Also it would be nice to squash the commit into one commit for keeping a nice history

After rebase, this looks good for merge to me.

Though one thing is it seems like we are dropping aliasing. I'm also fine with this, but an alternative would be to add the module resolver to eslint as a package: https://www.npmjs.com/package/eslint-plugin-import

I added eslint-plugin-import with the webpack resolver, but I am still getting errors with aliasing. From what I read online it may be an issue with the text editor I am using (Atom). Let me know if it works for you.

 Also the .eslintrc json format was slightly wrong. I fixed it by removing my externals function and replacing it with a npm package, but I also changed the eslint to look at the client config instead of the server config, because the externals function only was used on the server side to prevent a bug in webpack that bundles excessive server code unnecessarily.

Please rebase, fix merge conflicts and then we can merge.


adding the referrerId

[ ] need to add tests

Fixes https://github.com/OpenCollective/OpenCollective/issues/23

This is now month and half old. @xdamman can you pls either add tests or close it and link to the github issue for it for someone else to pick up.


Fix: Incorrect position set on initialization

Method isInScreenBounds implemented to detect if the last known position is valid.

Nice!


Cleanup: fix a inline function style

No logical change.
A comment right after the inline keyword might block clang-format working.

[approve ci clang-analyzer]

Cherry-picked to v9.0.x branch.


Usage with @nanostores/router, type mismatch for @useStores

First of all, thanks a lot for your fine work. Nanostores APIs are a real pleasure to use!
I've some observations regarding usage with router

Same type mismatch for router and searchParams
<…> is missing the following properties from type 'WritableAtom<unknown>': set, notify

It still works perfectly though, despite typing errors.
I could make a "proxy/bridge/wrapper" regular atom maybe? But that would be just "cosmetical" without adding an actual feature.

Hey @JulianCataldo!
Can I ask you to remake the issue at the new repo: https://github.com/nanostores/lit ?
I will try and see if I can resolve the types!

I didn't realised there was old repo, thought I was on the new one I'm used to, confounding them :o
Thank you for tackling this so fast! I will keep you in touch in case I encounter something else.

Published new version to npm which fixes the type issue.


"Showing the errors and logs will help a lot, like in the previous version of Flow Playground

"Showing the errors and logs will help a lot, like in the previous version of Flow Playground

Are you able to see the logs and errors tabs at the bottom of the webapp?

I am talking about logs like this: 'log("empty vault created")'. We are not
able to see the logs that we are executing in the log panel anymore.
On Thu, 6 Apr 2023 at 02:00, Tom Haile @.***> wrote:

Are you able to see the logs and errors tabs at the bottom of the webapp?
[image: 2023-04-05 15 29 18]
https://user-images.githubusercontent.com/3970376/230203428-ee73b259-cfe2-4533-a39c-e6eb6d9231fe.gif
—
Reply to this email directly, view it on GitHub
https://github.com/onflow/flow-playground/issues/628#issuecomment-1498114162,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXICJ3UCM6RB3ZLY22ZVDM3W7XI5ZANCNFSM6AAAAAAWTTUIVY
.
You are receiving this because you authored the thread.Message ID:
@.***>

You can see more problems in this video that I created
https://www.loom.com/share/bdab53f2b48148ba908cac3020eba843
On Thu, 6 Apr 2023 at 12:43, sumit choudhary @.***> wrote:

I am talking about logs like this: 'log("empty vault created")'. We are
not able to see the logs that we are executing in the log panel anymore.
On Thu, 6 Apr 2023 at 02:00, Tom Haile @.***> wrote:

Are you able to see the logs and errors tabs at the bottom of the webapp?
[image: 2023-04-05 15 29 18]
https://user-images.githubusercontent.com/3970376/230203428-ee73b259-cfe2-4533-a39c-e6eb6d9231fe.gif
—
Reply to this email directly, view it on GitHub
https://github.com/onflow/flow-playground/issues/628#issuecomment-1498114162,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXICJ3UCM6RB3ZLY22ZVDM3W7XI5ZANCNFSM6AAAAAAWTTUIVY
.
You are receiving this because you authored the thread.Message ID:
@.***>

@sumitchoudharySEM  Thanks for your video it was very helpful to understand what you are seeing.
There does appears to be a backend like a slow down we were not seeing earlier this week.
Also noticed that the UI isn't giving any indication the code has errors. example imported contracts have not been deployed.
In this simple example, log statements are getting printed out as expected.

Thanks
On Fri, 7 Apr 2023 at 22:16, Tom Haile @.***> wrote:

@sumitchoudharySEM https://github.com/sumitchoudharySEM Thanks for your
video it was very helpful to understand what you are seeing.
There does appears to be a backend like a slow down we were not seeing
earlier this week.
Also noticed that the UI isn't giving any indication the code has errors.
example imported contracts have not been deployed.
In this simple example, log statements are getting printed out as expected.
[image: 2023-04-07 11 25 32]
https://user-images.githubusercontent.com/3970376/230643516-3080f789-7ba0-4ca0-a586-a559754e3159.gif
—
Reply to this email directly, view it on GitHub
https://github.com/onflow/flow-playground/issues/628#issuecomment-1500453818,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXICJ3V422UW77SK2POFKUDXABAIFANCNFSM6AAAAAAWTTUIVY
.
You are receiving this because you were mentioned.Message ID:
@.***>

@sumitchoudharySEM  are you still seeing issues? The backend slowdown has been addressed.


smol fix

📚 $\text{Stack Overview}$
Pulls submitted in this stack:

#123 👈
main

This comment was automatically generated by st.

Codecov Report
Attention: Patch coverage is 0% with 26 lines in your changes missing coverage. Please review.

Project coverage is 27.2%. Comparing base (9a3cc5f) to head (7900861).

:white_check_mark: All tests successful. No failed tests found.

Files with missing lines
Patch %
Lines

bin/node/src/cli.rs
0.0%
26 Missing :warning:

Additional details and impacted files

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Inlay Hints infills illegal return type hints on methods

Environment data

Language Server version: Pylance language server 2022.12.20 (pyright 621d886b)
OS and version: Windows 10 21H2 19044.2251
Python version (& distribution if applicable, e.g. Anaconda): CPython 3.11.1 64-bit

Code Snippet
class Bar:
  def foo(self):
    return Bar()

Repro Steps

Enter snippet
Ensure inlay type hints are enabled (python.analysis.inlayHints.functionReturnTypes)
Double click to infill return type (def foo(self) -> Bar:)
Observe Pylance inform you of its own erroreous infill (Pylance(reportUndefinedVariable))

Expected behavior
There are three acceptable behaviours in Python at current for type hints of a given class within its own methods (in order of reliability):

Stringified infills (def foo(self) -> "Bar":), safe, handled correctly by Pylance and other type checkers, considered awkward
Unchanged infill (def foo(self) -> Bar:), but with a code-action for from __future__ import annotations (for PEP 563 behaviour)
Self infill (def foo(self) -> Self:), which may be considered Pythonic, but only where available, requiring an import not in earlier versions of the standard typing module (but a code-action to import when the Python environment supports it may be viable), or via fallback upon the external typing_extensions module (a backport for Python 3.10 and prior, which may not be available in the given Python environment)

I suspect that 1 and 2 are likely the best solutions, given they are available for all Python from 3.7 onwards (CPython 3.6 being no longer supported), though if further support (Python 3.6) is required then 1 is the only option that can be reliably defaulted to for the infill. If code-actions are provided to help users fix this, then the availability of 2 and 3 is likely desired, though if Self is not already available via the typing or typing_extensions modules already available in the Python environment, then it should probably not be shown. However, while more likely to be available than Self in the immediate future, 2 makes annotation slow (due to stringification) and runtime evaluation even slower on many implementations (requiring eval() for stringified annotations and so forth), whereas 3 does not have this issue (but at the cost of an external module if not on Python 3.11 and above).
Given that resolving type hints like this into legal Python may be required if Pylance is not merely to rely on stringified infills (which users may find unsatisfying), then the ability to treat the double click as a code-action may be necessary in itself; to save double clicking and then triggering a code-action. While a default strategy setting may work to avoid this, naturally any cases may eventually fallback upon stringified input to "at least" infill a syntactically correct annotation.
Alternatively, of course, no solution may be found and Python could simply be waited out on until a resolution to the PEP 563 and PEP 649 situation is resolved.
Actual behavior
The type hint is infilled as a variable (def foo(self) -> Bar:) rather than a string literal (def foo(self) -> "Bar":, as the safe default) or any other chosen/preferred option above. Pylance then correctly reports this as an error, given that Python does not currently support the class (Bar) being referenced in any declaration or annotation within itself (but, of course, may be referenced in its method bodies proper).
Logs
Nothing relevant.

Thanks for the issue and suggestions.
We will look at fixing this.

This issue has been fixed in prerelease version 2023.3.22, which we've just released. You can find the changelog here: CHANGELOG.md

This issue has been fixed in prerelease version 2023.3.22, which we've just released. You can find the changelog here: CHANGELOG.md

Can confirm that in the pre-release version it does stringify the infill as -> "Bar" now, per approach 1. That's probably the best approach, pending future PEPs that improve/resolve typing syntax.