Throw better exception when app might be using old ASP.NET pattern

Describe what is not working as expected.
I expected that the startup registration would allow me to use the EF Tools without implementing a IDbConnectionFactory. I do not have an empty constructor on my context class, but by isn't the tooling using DI to create an instance? Here is my DbContext class:
  public class VacationContext : DbContext
  {
    private IConfiguration _config;

    public VacationContext(IConfiguration config, DbContextOptions builder): base(builder)
    {
      _config = config;
    }

    public DbSet<VacationRequest> VacationRequests { get; set; }
    public DbSet<Employee> Employees { get; set; }

    protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
    {
      base.OnConfiguring(optionsBuilder);

      optionsBuilder.UseSqlServer(_config["Data:MainConnection"]);
    }
  }

If you are seeing an exception, include the full exceptions details (message and stack trace).
d:\courses\PS\aspnetcore2\Examples\Exemplar\VacationPicker>dotnet ef database drop

Build succeeded.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:00:05.15
No parameterless constructor was found on 'VacationContext'. Either add a parameterless constructor to 'VacationContext' or add an implementation of 'IDbContextFactory<VacationContext>' in the same assembly as 'VacationContext'.

Steps to reproduce
Include a complete code listing (or project/solution) that we can run to reproduce the issue.
Partial code listings, or multiple fragments of code, will slow down our response or cause us to push the issue back to you to provide code to reproduce the issue.
<code listing>

Further technical details
EF Core version: (found in .csproj file)
 <PackageReference Include="Microsoft.AspNetCore.All" Version="2.0.0-preview1-final" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.Tools" Version="2.0.0-preview1-final" />
    <DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet" Version="2.0.0-preview1-final" />

Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system: Win10
IDE: VS2017 Preview 1

Dupe of #8164. This will be fixed in 2.0.0-preview2-final.

ASP.NET Core changed the default pattern for applications in 2.0. Instead of having a ConfigureServices call, there is now a Main method with a BuildWebHost method split out. It was explicitly stated by @DamianEdwards that EF does not need to try to keep supporting the old pattern and instead old applications should:

Update their code to the new pattern
or implement an IDbContextFactory

However, our exception message only suggests the latter, which means that people will not be aware that updating their app to the new pattern is a solution. We should update the message with a fwlink (@divega) to documentation on how to update 1.x ASP.NET Core app to the 2.0 pattern.

I have created https://go.microsoft.com/fwlink/?linkid=851728. Currently points to one of the ASP.NET Core walkthroughs, but we should update it as part of https://github.com/aspnet/EntityFramework.Docs/issues/409.

I don't quite get this, does this mean that for separate data projects, we no longer need a startup class to support EF Tooling? Instead we should do what in Main to support it without needing to implement the IDbContextFactory? I'm seeing this is a new 2.0 project, not a converted 1.x project.
This is the program.cs:
namespace VacationPicker
{
  public class Program
  {
    public static void Main(string[] args)
    {
      BuildWebHost(args).Run();
    }

    public static IWebHost BuildWebHost(string[] args) =>
        WebHost.CreateDefaultBuilder(args)
            .UseStartup<Startup>()
            .Build();
  }
}

@shawnwildermuth AFAIR, in 2.0-preview1 we were in an intermediary state in which we didn't support the Program.BuildWebHost method so you had to have an IDbContextFactory. The change to support Program.BuildWebHost is in preview2.


Add hack/cherry_pick_list.sh to list all automated cherry picks

Adds hack/cherry_pick_list.sh to list all automated cherry picks
since the last tag.

Adds a short python script to extract title/author and print it in
markdown style like our current release notes.

Revises patch release instructions to use said script.

No idea who a good reviewer is. I feel bad for picking on @thockin more, but he's reviewed the other cherry pick stuff, so it might be apropos.

Or @jlowdermilk for Python readability, clearly. :P

LGTM but 2nd eyes would help :)
I am honestly a bit anxious about parsing subjects and branch names, but don;t have a better answer

Fixed @jlowdermilk's nit.
@thockin: I tried to make it was picky as possible, in case someone was doing something asinine like merging a commit that happened to mimic my exact format, but yeah. It's a bit cobbled together, but unless we want to move off a GitHub oriented workflow altogether (ha) or other radical suggestions, I think these pulls-as-atomics style tools are probably a decent infrastructure.

lgtm

Merging so @brendanburns has it for 0.21.3.


Gitops example

Create an vela app example for Gitops and Continuous Delivery by using kustomize controller and git repo component
Please see details in README.md.    fix #1562

@yangsoon  please finish the rest as we discussed

prefer #1863


Sidecar send unexpected RST packet to ingress gateway, which result in intermittent 503 at client side during upload files.

Bug Description
We have a storage pod running in our cluster with istio injection enabled and get some intermittent 503 UC errors at client side during upload 300M files.
Our topology is below, we have an ingress gateway to manage all the traffic entering in our mesh.

First, we check the envoy access log in gateway and sidecar, we see the 503 UC response in gateway side, but not see any 503 in sidecar side. So we think the problem maybe occur in the connection between ingress gateway and sidecar.
Then, we tune the evnoy log level to debug and found this: The ingress gateway's connection is terminated by sidecar, the sidecar receive the "Connection reset by peer" msg.

ingress gateway envoy log

2021-12-07T08:37:28.358739Z debug   envoy http2 [C488678497] updating connection-level initial window size to 268435456
2021-12-07T08:37:28.358906Z debug   envoy http  [C488678497] new stream
2021-12-07T08:37:28.358940Z debug   envoy http  [C488678497][S10432259314075048153] request headers complete (end_stream=false):
':method', 'PUT'
':path', '/random300M_1'
':scheme', 'https'
':authority', ''test.example.com:8443'
'user-agent', 'curl/7.58.0'
'accept', '*/*'
'content-length', '314572800'
'content-type', 'application/x-www-form-urlencoded'

2021-12-07T08:37:28.359015Z debug   envoy router    [C488678497][S10432259314075048153] cluster 'outbound|443||storage-internal-svc.test.svc.kubernetes.io' match for URL '/random300M_1'
2021-12-07T08:37:28.359053Z debug   envoy router    [C488678497][S10432259314075048153] router decoding headers:
':method', 'PUT'
':path', '/random300M_1'
':scheme', 'https'
':authority', 'test.example.com:8443'
'user-agent', 'curl/7.58.0'
'accept', '*/*'
'content-length', '314572800'
'content-type', 'application/x-www-form-urlencoded'
'x-forwarded-proto', 'https'
'x-envoy-internal', 'true'
'x-request-id', 'd0784d05-2b65-4121-b309-a28fe69c91b0'
2021-12-07T08:37:28.367909Z debug   envoy router    [C488678497][S10432259314075048153] pool ready
2021-12-07T08:37:28.367956Z debug   envoy http  [C488678497][S10432259314075048153] Read-disabling downstream stream due to filter callbacks.
2021-12-07T08:37:28.430711Z debug   envoy http2 [C488678497] Stream 1 disabled, unconsumed_bytes 0 read_disable_count 0
...
2021-12-07T08:37:29.800316Z debug   envoy http  [C488678497][S10432259314075048153] Read-enabling downstream stream due to filter callbacks.
2021-12-07T08:37:29.800325Z debug   envoy http2 [C488678497] Stream 1 enabled, unconsumed_bytes 239943680 read_disable_count 1
2021-12-07T08:37:29.800409Z debug   envoy router    [C488678497][S10432259314075048153] upstream reset: reset reason: connection termination, transport failure reason:
2021-12-07T08:37:29.800486Z debug   envoy http  [C488678497][S10432259314075048153] Sending local reply with details upstream_reset_before_response_started{connection termination}
2021-12-07T08:37:29.800523Z debug   envoy http  [C488678497][S10432259314075048153] encoding headers via codec (end_stream=false):
':status', '503'
'content-length', '95'
'content-type', 'text/plain'
'date', 'Tue, 07 Dec 2021 08:37:29 GMT'
2021-12-07T08:37:29.800557Z debug   envoy http  [C488678497][S10432259314075048153] doEndStream() resetting stream
2021-12-07T08:37:29.800592Z debug   envoy http  [C488678497][S10432259314075048153] stream reset
2021-12-07T08:37:29.810355Z debug   envoy http2 [C488678497] sent reset code=0
2021-12-07T08:37:29.810375Z debug   envoy http2 [C488678497] stream closed: 0
2021-12-07T08:37:29.828192Z debug   envoy connection    [C488678497] remote close
2021-12-07T08:37:29.828199Z debug   envoy connection    [C488678497] closing socket: 0
2021-12-07T08:37:29.828212Z debug   envoy connection    [C488678497] SSL shutdown: rc=1
2021-12-07T08:37:29.828237Z debug  envoy conn_handler  [C488678497] adding to cleanup list

sidecar envoy log

2021-12-08T09:56:53.295405Z     debug   envoy http      [C3211] new stream
2021-12-08T09:56:53.295478Z     debug   envoy http      [C3211][S10234019614774064697] request headers complete (end_stream=false):
2021-12-08T09:56:53.295613Z     debug   envoy filter    [C3211] validateX509 mode PERMISSIVE: ssl=true, has_user=true
2021-12-08T09:56:53.295616Z     debug   envoy filter    [C3211] trust domain validation skipped
2021-12-08T09:56:53.295676Z     debug   envoy router    [C3211][S10234019614774064697] cluster 'inbound|9000||' match for URL '/random300M_1'
2021-12-08T09:56:53.295711Z     debug   envoy router    [C3211][S10234019614774064697] router decoding headers:
2021-12-08T09:56:53.295729Z     debug   envoy router    [C3211][S10234019614774064697] pool ready
2021-12-08T09:56:53.300136Z     debug   envoy http      [C3211][S10234019614774064697] Read-disabling downstream stream due to filter callbacks.
...
2021-12-08T09:56:53.860992Z     debug   envoy http      [C3211][S10234019614774064697] Read-enabling downstream stream due to filter callbacks.
2021-12-08T09:56:53.862350Z     debug   envoy http      [C3211][S10234019614774064697] Read-disabling downstream stream due to filter callbacks.
2021-12-08T09:56:53.864464Z     debug   envoy http      [C3211][S10234019614774064697] Read-enabling downstream stream due to filter callbacks.
**2021-12-08T09:56:53.865059Z     debug   envoy misc  Unknown error code 104 details Connection reset by peer**
2021-12-08T09:56:53.865079Z     debug   envoy connection        [C3211] remote close
2021-12-08T09:56:53.865081Z     debug   envoy connection        [C3211] closing socket: 0
 2021-12-08T09:56:53.865089Z    debug   envoy misc  Unknown error code 32 details Broken pipe
**2021-12-08T09:56:53.865091Z     debug   envoy connection        [C3211] SSL shutdown: rc=-1**
2021-12-08T09:56:53.865109Z     debug   envoy http      [C3211][S10234019614774064697] stream reset
2021-12-08T09:56:53.865405Z     debug   envoy router    [C3211][S10234019614774064697] resetting pool request
2021-12-08T09:56:53.865633Z     debug   envoy conn_handler      [C3211] adding to cleanup list

The ip <IP_ADDRESS> is the gateway's pod ip, the ip 10.0.02 is the application's pod ip, the application open its 9000 port.
Next, we do the tcpdump in the application node, and find something strange. We fount the first RST packet is sidecar send to the ingress gateway and the sidecar envoy didn't know that.
The sidecar think the ingress gateway close the connection and then send FIN/RST to application.
05:34:34.814254 IP <IP_ADDRESS>.9000 > <IP_ADDRESS>.53304: Flags [R], seq<PHONE_NUMBER>, win 0, length 0
05:34:34.814989 IP <IP_ADDRESS>.9000 > <IP_ADDRESS>.53304: Flags [R], seq<PHONE_NUMBER>, win 0, length 0
05:34:34.815045 IP <IP_ADDRESS>.53304 > <IP_ADDRESS>.9000: Flags [R], seq<PHONE_NUMBER>, win 0, length 0
05:34:34.815536 IP <IP_ADDRESS>.57088 > <IP_ADDRESS>.9000: Flags [F.], seq<PHONE_NUMBER>, ack 912453698, win 256, options [nop,nop,TS val 397913316 ecr 397912839], length 0
05:34:34.826703 IP <IP_ADDRESS>.57088 > <IP_ADDRESS>.9000: Flags [R], seq<PHONE_NUMBER>, win 0, length 0

The frequency of this problem is 2%, we try to minus the sidecar worker num to 1 and disable mTLS, this issue still exist.
Dose this issue occurred before?
Version
istio version: 1.10
kubectl version: 1.18.8

Additional Information
No response
Affected product area

[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Control Plane Revisions

Is this the right place to submit this?

[X] This is not a security vulnerability
[X] This is not a question about how to use Istio

The root cause is the invalid state packets are sent to the application. Let us move to the PR talk about this. https://github.com/istio/istio/pull/36536


refactor(subscription): use unary rpcs for ack/modack requests

[x] Tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

/cc @kir-titievsky

@stephenplusplus I've pushed several commits, one of which moves all the message related functionality to a separate class, this wasn't really necessary here, but it was something I've been meaning to do for a while and I think will help with developing a couple upcoming PubSub features.

@theacodes I must have misunderstood the request, but I thought that the request was to not send the requests over the stream anymore.

Indeed that's the case, but it is still useful to have it be configurable. It's up to you.


API Features

Background
Several years ago Jimmy shared mopac2012 object files along with a few select .F90 source files with Bill Hase and me.  I used these files to create a tight integration with VENUS as well as my own in-house direct dynamics code.
As has been discussed in this project, creating an API for mopac is challenging due to the inherent file-based input.  The technique I implemented creates a dummy mopac input file ('MOPAC input') for initialization purposes only, turns off what output can be easily turned off, and directs the rest to /dev/null.  Calculation results can then be obtained by using mopac subroutines and copying data between user and mopac variables.  While this ad hoc approach is not truly an API, it may be of use to the community.
PR Features
This pull request implements the same approach as that used for mopac2012, but it is more extensive as most of the source was previously not available to me.  (BTW, thank you to all of the contributors to this project - open source mopac is an exciting development!)
Several logical flags have been added to allow for the same code to run calculations on systems of different sizes and/or charge states.
It includes interface routines that initialize mopac for a given system, return the SCF energy, return the SCF energy+gradient, return partial charges, and return bond orders.  There is also a program included that illustrates how to use the new features.
Status

[x] Ready for discussion
[ ] Ready for merge

I welcome contributions like this, and these features might be of immediate use in implementing a first version of the Python interface to MOPAC, as I will be looking to suppress superfluous outputs.
Unfortunately, I'm about to leave on vacation for 3 weeks, so I can't review this PR right now and no one else is reviewing PRs for MOPAC at this time. This will have a high priority when I get back.

Thanks for the heads up and enjoy your vacation!  I start my new position at Illinois State University on Aug 1, so I may be a bit slow to respond around that time.
I had the same thoughts regarding a possible python interface as well.

any update ?

Please let me know if I can assist.

I wasn't clear on who was taking initiative on the discussion implied by the "ready for discussion" radio button in the PR and/or how long you were going to be distracted by starting a new faculty position. I was also distracted by an invited J. Chem. Phys. paper that I've been frantically trying to finish for the last several months.
It's probably a good time to resolve this now. What do we need to discuss, and what actions remain before this PR is ready for merging? Is this ready for a full code review, or are there specific portions of the PR that I should focus on and modify first?
From a brief examination, it seems like the example program is serving in place of any documentation of this interface. Is the example illustrating all of the working functionality, or should it be expanded in some way? I see that you are using targeted reset flags to perform the same reset functionality that is usually performed by globally incrementing the numcal variable - have you been thorough about this, or should I take another pass at looking for all reset points in the code and adding similar reset flags?

Sorry about the confusion on who would take the lead - this is my first PR and contribution to an open-source project.  We both have had a lot going on!
I would be happy to write up more formal documentation if it would be useful - is there a format/style you would like to follow or an example?  The example program does illustrate all of the features that are currently present.
Because of the history of this approach - namely, only having access to a handful of source code files - using the targeted reset flags made sense to 1) avoid having unintended consequences and 2) touch as few mopac variables as possible.
I would have to test if incrementing the numcal variable would work similarly.  One advantage of the targeted reset flags is that specific aspects of the calculation can be reset without reinitializing the entire calculation.
I believe the reset flags have been implemented globally, but I have not tested all calculation types.  Mozyme, in particular, has not been tested.  Having a second set of eyes could be useful.
If the targeted reset flags are acceptable, this should not impact how Mopac functions outside of the "API" and has no current merge conflicts.

While I will eventually request that documentation be provided with the submission of new features in MOPAC, I don't yet have an appropriate place to put such documentation. Ideally, it will go here when the new documentation website is ready for deployment, but it is still a work in progress and not really ready for contributions.
I need to examine what you are doing more closely during the code review, but I'm happy to accept your approach of using reset flags. While it is making a somewhat complicated system even more complicated, it still seems like an improvement in the absence of refactoring the control flow logic in MOPAC, which is unlikely to ever happen. There is another open interfacing request [#52], and I might be able to use your interface to fulfill that request as well.
From this brief discussion, it seems like this PR is ready for a code review, and I will proceed with that soon. I can probably make any pre-merge adjustments myself, but there is a small chance that I will request modifications from you before merging.

Can you explain the API recommendations regarding GEO-OK and NOSYM? I assume that certain observed behaviors led to these recommendations, and I would like to understand that better, especially for future documentation purposes.

If GEO-OK is not included, calculations are halted if two atoms are closer than 0.1 Ang.  For high-energy collision systems, this can occur and would disrupt a direct dynamics simulation.
NOSYM is included to guard against two subsequent calls for a mopac energy/gradient having a different point group for the same molecule due to a change in geometry between calls.

I'm sorry about the very extended delay, but I've finally finished a first draft of a diskless/stateless MOPAC API that was inspired by this PR. Once testing is complete, I expect that the new API will supersede this API, and it should be able to do everything that  this API can do and more. I'm interested in feedback, and I'm happy to include features that I might have overlooked.
I used the same strategy as this API to eliminate disk-based output by piping the output to a dummy location (e.g. /dev/null). I have also eliminated all disk-based input by creating a new, minimal initialization process for the set of features exposed by the API. To avoid confusion, the set of options is very limited and controlled by the input data type, while the raw keyword line is hidden by the API. The goal is to provide simple access to MOPAC's core features to a larger audience that is otherwise unfamiliar with MOPAC and its idiosyncrasies.

I see that you merge the branch any documentation on how to use the API ?

At the moment, the best way to understand the new API would be to look at src/interface/mopac_api.F90 for a summary of the data structures and functions, and tests/mopac_api_test.F90 for an example of a program that calls the API. To access and use the mopac_api module, a Fortran program needs to link with the libmopac shared library and a BLAS/LAPACK library.
Basically, you put all input data into the mopac_system derived type, and all of the accessible property outputs from a calculation are returned in the mopac_properties derived type. The mopac_state/mozyme_state derived types save the electronic ground state at the end of the calculation to initialize the next calculation if you are running a sequence of 1SCF calculations to drive molecular dynamics. Uninitialized mopac_state/mozyme_state correspond to starting a calculation from the default atomic or Lewis-structure initial guesses for the electronic state. The operations supported right now are 1SCF, geometry relaxation, and vibrational calculations, using either MOPAC or MOZYME. I'm satisfied with this API design, but I'm still willing to consider changes upon reasonable request. I'm trying to keep the API as simple as I can.
I still need to test robustness of the API and add error handling (integer error codes with a list of meanings). For example, I'm not presently using GEO-OK on the internal keyword line of the API, and I need to test close approaches of atoms to see if I need to add it or find a different work-around.
Before the release, I will write a thin wrapper for this API in Python, where the different derived types are mapped to Python classes and the Fortran API calls are mapped to Python functions. The plan is to have MOPAC usable in Python through this API after installation through Conda Forge or PyPI, but that will be post-release.
I'll put some temporary documentation for the API somewhere before release (maybe the GitHub Wiki for MOPAC, which is empty right now). The next development activity after the API release will be a new MOPAC website, which is where the API documentation will eventually go. I'm probably going to scrap the Sphinx-based test website and use Hugo.

this is excellent, let me know when I can test the python layer of integration. Really great improvement are coming!

I'm closing this PR now, as I'm just about to release the new major version of MOPAC with the new API. There were some adjustments made in preparing the release when I realized Fortran's poor ABI compatibility situation. The API now has C bindings, which will make it very easy to call from Python but less convenient for Fortran developers. To accommodate Fortran developers, I wrote a Fortran wrapper that is set up like the previous version of the API. The C and Fortran interface specifications are contained in the include directory of this repository. Also, I did add GEO-OK to the hidden keyword line of the API, so it should now be fully compatible with everything you did in your interface.
The new version of MOPAC will be shortly followed (hopefully in a week or so) by a mopactools Python library that will wrap the API for use in Python. mopactools will also be used to distribute the MOPAC shared library in PyPI, whereas mopactools in conda-forge will depend on MOPAC's existing distribution through conda-forge. I will put together some Sphinx documentation alongside the Python library explaining how to use MOPAC in this setting. mopactools is going to be a completely separate project and repository from MOPAC, and it will be released under a permissive license. It's going to be very minimal to start, but mopactools will be open to hosting pre- and post- processing scripts that MOPAC users find useful.
Thank you for providing a foundation, motivation, and set of requirements for the new MOPAC API, and I'm sorry that I was not able to include your software contributions here more directly.


cmake: fix Xcode project generation to include all header files.

This was broken by commit cf1f240534b8fbf2406f4d345fd43c41541d8800.
This commit reverts the 2 lines which broke the inclusion of header files in the generated Xcode project.

@swift-ci smoke test and merge

@swift-ci smoke test and merge


Upgrade the postgresql version to 10.6

Description
This upgrades PostgreSQL to 10.6 from 10.1.  This supports our ability to use IAM authentication to our RDS instance.  The experimental env is already upgraded to postgres 10.6. Upgrading the Makefile will help us test this change with developers. Upgrading the .circleci/config.yml will allow us to test the postgres change in our CI/CD pipeline.
There should be no issue surrounding development and CI/CD in 10.6 and deploying to 10.1.
Reviewer Notes
The postgres client is versioned to the available package on debian stretch.  I don't think this is a problem and I'm not ready to upgrade the version of our docker container here.
Setup
To upgrade locally this will do it:
make db_dev_reset db_dev_migrate

Will have to tell developers to do this after this is merged.
Code Review Verification Steps

[x] Request review from a member of a different team.
[x] Have the Pivotal acceptance criteria been met for this change?

References

Pivotal story for this change

Shouldn't this be 10.5 now?

@dynamike - thanks for catching.  I pushed a change to make it 10.5 and updated the title.
For everyone else: RDS doesn't support 10.6 yet so I'm pushing us to the latest version of postgres it does support (in the 10.X series).

Looks good to me. Though I think the comment on https://github.com/transcom/mymove/pull/1334/files#diff-b67911656ef5d18c4ae36cb6741b7965R160 needs updating, not blocking though.


Add CLI install instruction in dev tools

Preview is available here:http://developers-pr883.previews.kube001.services.stellar-ops.com


correcting names for docker hub location for the image

When the repo was renamed, the new name for the docker image is teliaoss/github-pr-resource but there were a couple of references to it as telia-oss/github-pr-resource which doesn't exist.
The purpose of this PR is to correct that.

Thanks for fixing!


Basic error messages/codes as per the spec

Implement error messages and codes based on the errors spec: https://github.com/prisma/specs/tree/master/errors

Internal note: @mavilein will break this down for backend

We are tracking the backend work in this epic.


very slow boot

On v01.01.01 the example image (kas-iot2050-example.yml) boots very slowly due to crng init:
[   10.066721] pru-rproc b206000.rtu: PRU rproc node rtu@b206000 probed successf                                                                                ully
[   10.279217] icssg-prueth pruss0_eth: TI PRU ethernet driver initialized: dual                                                                                EMAC mode
[   33.846080] tps62363-vout: disabling
[  136.918242] random: crng init done
[  136.921663] random: 7 urandom warning(s) missed due to ratelimiting
is there a way to speed it up?
Thanks

Is this without any network attached? Does the issue vanish when bringing the device online?
Was this a self-built image? Same issue when using the release binary version? Also, can you reproduce this with the latest image release (make sure to update the firmware for that first)?

Is this without any network attached? Does the issue vanish when bringing the device online?
It doesn't matter, it happens at every boot.
Was this a self-built image? Same issue when using the release binary version? Also, can you reproduce this with the latest image release (make sure to update the firmware for that first)?
Yes, it is a self built image. I solved it (temporarily?) by adding -haveged- debian package that seems to speed up entropy accumulation.
One thing I noticed, the ti rng doesn't show up in the device tree and looks disabled.

Is this an advanced or a basic variant?
And, again, do you get the same behavior when using the binary images that was released? I'm still confused that he haven't seen that before.

Its a basic version. I never used the stock image, could you point me to
the download link?
On Mon, Jan 24, 2022, 1:58 PM Jan Kiszka @.***> wrote:

Is this an advanced or a basic variant?
And, again, do you get the same behavior when using the binary images that
was released? I'm still confused that he haven't seen that before.
—
Reply to this email directly, view it on GitHub
https://github.com/siemens/meta-iot2050/issues/251#issuecomment-1020072547,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABUD4THZJWYCOAQJ6YOD5LLUXVEG7ANCNFSM5MSDQ6MA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

Sure: https://support.industry.siemens.com/cs/document/109741799/downloads-for-simatic-iot20x0?dti=0&lc=en-WW#!

Probably solved by now.


embed bio_dgram_data inside bio_dgram_sctp_data

the sctp BIO implementation uses the generic BIO dgram implementation under the covers for some operations.  However, the private data for each bio is incongruous, leading to segfaults when doing things like passing a dgram_sctp_ctrl operation to the underlying dgram_ctrl method.
Fix this by removing the common fields between the two strcutres and embedding a bio_dgram_data as the first member of the bio_dgram_sctp_data struct.  This allows implicit casting when that call path is taken, avoiding any memory mis-use
Fixes #20643

Could we just add enable-asan to run-checker-daily-sctp.yml?

Could we just add enable-asan to run-checker-daily-sctp.yml?

That would probably do it

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Merged to the master branch. Thank you.


help: Simplify instructions for changing a user's name or role.

Drop mostly redundant instuctions tab.
Current:

https://zulip.com/help/change-a-users-name
https://zulip.com/help/change-a-users-role

Updated:

@drrosa Any feedback on this one?


Box-Shadow & Transform

Bug reports:
When using box-shadow, and a transform it seems to not render the box-shadow.
https://jsfiddle.net/dLw6xzby/
Specifications:

html2canvas version tested with: 1.2.1
Browser & version: Chrome 92
Operating system: OSX 11.5.1

Any update/workaround for this issue?

U can try to switch to https://github.com/bubkoo/html-to-image


Added subroutine to run an NLTK Stemmer

So I saw an issue about TextBlob using a lemmatizer but not a stemmer.
Wrote a function for the later.
@sloria

thanks man!
i've pushed changes. i also altered SentenceTokenizer() - i wasn't
particularly aiming for that, just hoping to solve an issue - but those
changes are harmless
Regards,
Nitish Kulshrestha | +91<PHONE_NUMBER>
Core Member
Alumni Affairs Division
BITS Pilani K. K. Birla Goa CampusNH17-B, ZuarinagarGoa- 403726India
On Thu, Feb 9, 2017 at 8:45 AM, Steven Loria<EMAIL_ADDRESS>wrote:

@sloria requested changes on this pull request.
Looking much better! Just need to fix the test.
Also, there are a lot of unnecessary commits here--would you mind
squashing your commits down? If you don't know how or don't have the time,
don't worry too much about it.
In tests/test_blob.py
https://github.com/sloria/TextBlob/pull/149#pullrequestreview-20923457:

@@ -914,6 +918,14 @@ def test_lemma(self):
w = tb.Word("went", "VBD");
assert_equal(w.lemma, "go")

def test_stem(self): #only PorterStemmer tested

   w = tb.Word("cars")

   assert_equal(w.stem(), "car")

   w = tb.Word("wolves")

   assert_equal(w.stem(), "wolv")

   w = tb.Word("went")

   assert_equal(w.stem("v"), "went")

This assertion is failing because of the invalid "v" argument.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sloria/TextBlob/pull/149#pullrequestreview-20923457,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AULAGJrBKcZ8u-uy4mEBrLNR_fLJ3iIzks5raoTpgaJpZM4LztMV
.

The tokenization changes are unrelated to this PR; please remove them.

The added test is failing; can you please look into it?

@sloria I have fixed errors in the stemmer, rest seem to be errors in TextBlob itself. Please look into it.

Yes, the errors are unrelated to this PR. Thanks for making those changes. This looks good to go.


Add Traditional Chinese and update Simplified Chinese prompts

Reference:

https://github.com/PlexPt/awesome-chatgpt-prompts-zh/pull/86
https://github.com/PlexPt/awesome-chatgpt-prompts-zh/pull/183
https://github.com/PlexPt/awesome-chatgpt-prompts-zh/pull/190
https://github.com/PlexPt/awesome-chatgpt-prompts-zh/pull/194

Thank you very much. The PR will be included in next release.


srcset-based retina support

Current approach to retina support is breaking isomorphic rendering: server builds html for non-retina displays and client overrides it with other path to images.
Would you take patch for html5-based support (srcset attribute) instead?
Browser support: http://caniuse.com/#feat=srcset

That sounds like a really good idea. Default to that and then perhaps as a fallback on the JS browser render, check if srcset isn't enabled 'srcset' in createElement('img') and it is a retina screen and in that (now very low-percentage) option, manually switch the src to the retina version.
Thanks!

@KyleAMathews I added pull-request here. please check

@KyleAMathews ping?

This looks great! Will have to implement it in my react-retina-image project as well.

Released a 2.2.1


Write?

It'd be nice to be able to write to the .vox format as well.

Hello
I guess this could be done.
As you can see, I have not worked on this project for 4 years and I'm sorry, but this is not something I'm going to work on anytime soon.


grade.subject : <pronotepy.dataClasses.Subject object at 0x000001D46DA285C0>

When I use grade.subject in a for loop, I get this message instead of something good :
<pronotepy.dataClasses.Subject object at 0x000001D46DA285C0>

It was grade.subject.name


Decentralizing oracles idea

Force every client hosting oracle before it can sumbit contracts.
The more stable oracle runs more contracts. Each oracle has upper limit of quantity of contracts.
Let contract pay fees to its oracles when contract executed successfully.
For each contract, if some oracles of a contract become inactive, keep active orcales' authority and transfer inactive oracles' authority to new oracles.
Exchange or broadcast oracles' and their status through bitmessage and store them at local storage.
Block an oracle for a period if suspected behaviors of that address detected.

HI,
I like your ideas, there are problems with them though; one of them: afaik current mining pools do not except m of n transactions where n>~9 unless something changed very recently
As far as 5. is concerned - we already had Bitmessage protocol implementation for Oracle communications at the beginning, it has proved to be very slow
Thanks for your input!

The limits of m-of-n-transactions won't cause the problem because each contract can be assigned by any quantity (n < 9) of valid oracles chosen from oracles' database and let oracles transfer their authority conditionally as 4. mentioned.
For 5., I don't have any idea right now.
Btw, how to add labels on title? I tried to add ideas label.


Fix isNamespaced check when namespace is string

Apparently, Json.bool returns None when the value is there but not a boolean.

Good catch.


Add Postgres CTAS adapter macro with support for unlogged parameter

This gives the developer the ability to pass in an unlogged parameter in their model config, which is executed during the CTAS.
Issue: #1648

Thanks @boxysean - this looks great! One minor request here -- can you add unlogged as a "known" config in the PostgresAdapter? You can use AdapterSpecificConfigs as shown in the RedshiftAdapter.
By setting this in AdapterSpecificConfigs, dbt will allow users to supply this config in the dbt_project.yml file. If this config were unset, then dbt would require that users specify their configs inline in model {{ config() }} blocks. This feels like the type of config you'd want to apply to all models in a project, so I think it's worth doing here.

Sounds good yeah I'll do it! (Just coming back from vacation.) :-)
On Fri, Aug 2, 2019, 7:35 PM Drew Banin<EMAIL_ADDRESS>wrote:

Thanks @boxysean https://github.com/boxysean - this looks great! One
minor request here -- can you add unlogged as a "known" config in the
PostgresAdapter
https://github.com/fishtown-analytics/dbt/blob/dev/0.14.1/plugins/postgres/dbt/adapters/postgres/impl.py#L15?
You can use AdapterSpecificConfigs as shown in the RedshiftAdapter
https://github.com/fishtown-analytics/dbt/blob/dev/0.14.1/plugins/redshift/dbt/adapters/redshift/impl.py#L11
.
By setting this in AdapterSpecificConfigs, dbt will allow users to supply
this config in the dbt_project.yml file. If this config were unset, then
dbt would require that users specify their configs inline in model {{
config() }} blocks. This feels like the type of config you'd want to
apply to all models in a project, so I think it's worth doing here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fishtown-analytics/dbt/pull/1650?email_source=notifications&email_token=AAEMEM64MJ5HUOUUTE5WTZDQCRV53A5CNFSM4IILBIF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3OMPFQ#issuecomment-517785494,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEMEM44YW4KQNWJJJA25ZDQCRV53ANCNFSM4IILBIFQ
.

Okay @drewbanin, I've added your suggested change and signed the CLA!
For my case, I would NOT add unlogged as a project-wide config. If I were to do so, then all dbt-produced tables would NOT be "logged" and shipped to our read-only replicas (physical replication), which is what our Looker instance queries.
We have a developer convention where we preface intermediate models/tables with an underscore, so I actually have a slightly more complex adapter macro to find those and CTAS them with unlogged. That way I don't have to add unlogged in all the configs.

Thanks @boxysean! I think that's totally fair - thanks for sharing your use case!
@cla-bot check


Update js to 0.7.0

flutter_native_splash requires js version 0.7.0, so it makes it incompatible with wakelock_plus, because it depends on version 0.6.3

@xVemu thanks for bringing that up. I'm gonna upgrade it and raise a PR shortly.

Will show up in version 1.1.5.


Walkthrough bug: Can't snap to intersection during 'lines' step.

While testing the walkthrough, I noticed something is preventing us from snapping the drawing way to an existing street, which is required to proceed through the walkthrough.
Unsure if this is a generic hovering problem or an issue specifically with the walkthrough code.
Pic of the node not snapping to the way:

Note though that I can snap to either of the nodes on the way.

I can get the snapping to work if I add a bunch of debug statements to the rendering code to slow it down, and then ZOOM the mouse to the way as fast as possible before the code can catch up. This makes me think that the problem isn't Pixi, it's that whatever we're drawing is 'blocking' the hover/snap code from firing.

Fixed in 9cb845c89.


Can I use "torch.autograd.grad" in "training_step" funtion?

Hello!
I hope to calculate the  gradient of the loss on the model input every batch when training. The calculated gradients are then processed by some other functions and added into the loss function. The way I do this  in pytorch is like this, with the torch.autograd.grad function:
model_input.requires_grad = True
model.zero_grad()
model.eval()
grads = torch.autograd.grad(loss, model_input, grad_outputs=None, only_inputs=True, retain_graph=False)[0]
model.train()
Can I add these codes directly into the training_step function in pytorch-lightning?
My concern is:

Will this gradient calculation (torch.autograd.grad function)  influence the accuracy of model training since I add it in the training_step function?
Do I need to set model.zero_grad(),   model.eval()  and model.train()  when calculating the gradients on the input?

Thank you very much!

Hey,
I'm not super sure how torch.autograd.grad(...) works, but I would say that you can't backprop the model twice without retrain_graph=True. Also, you don't need to zero_grad() as there are no gradients in the model at this point. My suggestion would be to try and see what happens, as I'm not super sure what will happen.
Also, maybe this is interesting for you https://github.com/pytorch/functorch

Thank you very much for your help!  I will try and see what happens!


Simplify output of {Bit,Byte}MaskedArray

At the moment, v1 calls simplify_optiontype before returning from particular getitem methods in these content types, whilst v2 does not. Is this a planned change, or do we need to restore these?
https://github.com/scikit-hep/awkward-1.0/blob/fca80a69b23b2f5b2d952cc03fee722d9a867665/src/awkward/_v2/contents/bytemaskedarray.py#L161-L210
vs
https://github.com/scikit-hep/awkward-1.0/blob/fca80a69b23b2f5b2d952cc03fee722d9a867665/src/libawkward/array/ByteMaskedArray.cpp#L664-L752

It's not a planned change. Failing to include simplify_optiontype is a bug, and the symptom would be that the operation that's missing the simplify_optiontype has any of the following node types as a direct content of any of the following node types:

UnmaskedArray
BitMaskedArray
ByteMaskedArray
IndexedOptionArray
IndexedArray

That is, any of the 25 combinations like UnmaskedArray(UnmaskedArray(XYZ)), UnmaskedArray(BitMaskedArray(XYZ)), ... IndexedArray(IndexedArray(XYZ)) are all not allowed in arrays that return to the user: they must be eliminated by a call to simplify_optiontype before that happens. (They can't be excluded in the constructors of these types because they're allowed as temporary states in the midst of a calculation, before being returned to the user.)
I can't think of any situation where having an unnecessary simplify_optiontype does harm, but missing one is bad. If we need to implement a generic
class Content:
    ...
    def simplify_optiontype(self):
        return self

so that node types other than the above 5 don't complain about the method not existing, then that's fine. It would be better from a code maintenance point of view to not call simplify_optiontype where we know it's useless, because then the code would be suggesting something false.
Also, there are no situations where we'd want simplify_optiontype in v1 but not v2 or in v2 but not v1. If one of the two versions has this as a bug, the other should get it fixed. We may not be adding major new features to v1, but we are fixing bugs.
(Also also, it might seem strange that IndexedArray is included in the set of node types that simplify_optiontype should be applied to, even though IndexedArray does not have option type. It's because of the way that it mixes with IndexedOptionArray. We don't want arrays with ByteMaskedArray(IndexedArray(XYZ)) because it would use less memory and suffer less indirection to be IndexedOptionArray(XYZ). IndexedArray has the cost of extra indirection, but the benefit of delaying expensive calculations or minimizing memory use or both, but ByteMaskedArray(IndexedArray(XYZ)) doesn't have either of these two advantages.)
Is there a minimal reproducer that demonstrates it, showing a different layout in v1 and v2? (Maybe in #1249 that I haven't looked at yet...)

Yes, uncommenting a ported v1 test in #1249 led me to report this, and fix it in #1259

I was just looking at that, trying to type it up. I was disturbed by this output:
arr1       = <Array [{a: 1, b: 1}, {a: 2, b: None}] type='2 * {a: int64, b: ?int64}'>
arr2       = <Array [{a: 1, b: 1}, {a: 2, b: None}] type='2 * ?{a: int64, b: ?int64}'>

because those are supposed to be different types; a failure of simplify_optiontype would show up as double question marks (??), not this. But now I realize that's not what the test is complaining about, it's just useful information about two variables that are defined at the time of the test—the test is not asserting that they are the same or that they should be.

Here's the reproducer:
>>> v1 = ak.Array(ak.layout.ByteMaskedArray(
...     ak.layout.Index8(np.array([True, True])),
...     ak.Array({"a": [1, 2], "b": [1, None]}).layout,
...     valid_when=True)
... )
>>> v1
<Array [{a: 1, b: 1}, {a: 2, b: None}] type='2 * ?{"a": int64, "b": ?int64}'>
>>> v1.b
<Array [1, None] type='2 * ?int64'>

>>> v2 = ak._v2.Array(ak._v2.contents.ByteMaskedArray(
...     ak._v2.index.Index8(np.array([True, True])),
...     ak._v2.Array({"a": [1, 2], "b": [1, None]}).layout,
...     valid_when=True)
... )
>>> v2
<Array [{a: 1, b: 1}, {a: 2, b: None}] type='2 * ?{a: int64, b: ?int64}'>
>>> v2.b
<Array [1, None] type='2 * ??int64'>

v1 is right and v2 is wrong (double ??).


ActiveGraph::Core::SchemaErrors::CypherError exceptions unused

When we experience e.g. a constraint validation failure, we're getting Neo4j::Driver::Exceptions::ClientException instead of the expected error class, ActiveGraph::Core::SchemaErrors::ConstraintValidationFailedError.
Upon digging deeper, it appears to me that the ActiveGraph::Core::SchemaErrors::CypherError family of exceptions are completely unused. The API to convert from Neo4j driver errors to ActiveGraph errors is present, but never called. The specs only test the ActiveGraph::Core::SchemaErrors::CypherError API as far as I can see, but not that the conversion ever actually takes place.

@klobuczek I may be wrong about my assessment here. Let me know. In any case, I am happy to submit a PR to fix this if you can give me some guidance on where I should fix (base.rb? transaction.rb?  transactions.rb?)


QAWTO-214: update appium python client dependency

As part of the maintenance of the toolium dependency libraries, the update of the appium python client is going to be update to the version 4.
In order to update to this version we identified that the following actions needed to be updated to be compatible with the w3C webdriver:
https://jira.tid.es/browse/QAWTO-178
In order to be fully W3C compatible we need to change the set_value method used in the InputText pagelement to send_keys

reviso los tests cuando tenga un momento

I have tested the new mobile_actions features (Android e iOS) which tests all of the detected changes in Appium 3 , and 4 and also the change in the InputText done in this PR with the following versions:

Appium-Python-Client= 2.11.1 - Selenium=4.11.2
Appium-Python-Client= 3.2.1 - Selenium=4.25
Appium-Python-Client= 4.2.1  Selenium=4.25

And the results have been OK


Update mobile-engagement-how-tos.md

Updating article ownership from v-micada to piyushjo.

Hi @v-micada, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (v-micada). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;


aec_sync should not check whether or not to broadcast block

In the handle_cast clause for received_block, aec_sync checks whether the block exists on the chain; if it does, it doesn't broadcast.
While this is reasonable in principle, a check has already been done in aehttp_dispatch_ext. This function also calls aec_sync (asynchronously), then proceeds to write the block. The check in aec_sync is therefore redundant, but also introduces a race, where a block may erroneously not get re-broadcasted (at least by some nodes).
My suggestion: The check in aec_sync should be removed, and the API documented to clarify that aec_sync assumes that it's already been decided that the block/transaction should be broadcasted.

The code in aehttp_dispatch_ext actually writes the block first and then calls aec_sync so even though this is done asynchronously I would suspect that almost no blocks would be re-broadcasted.
I agree with Ulf's suggestion: aec_sync:received_block should always re-send.


I changed the RaspiBolt from one location to another and now I get rpc issue

I configurated everything in the router as said in the guide, I changed everything but I get this issue
https://pastebin.com/ZpkEDJPq

I guess the getpublicip.sh script is not running properly. What does that say?
$ cat /run/publicip.log
You can always just omit the --externalip in the systemd file. Or just configure it with your external ip directly (replacing the ${PUBLICIP} part).
Your public ip: curl -vv ipinfo.io/ip

This is what it says the
$ cat /run/publicip.log


Translation Api-Endpoints are broken

Currently all translation endpoints are broken.
Example: http://<IP_ADDRESS>/api/v1/product/022ac8c837714abdb964dc629ce4f5f5/translations or http://<IP_ADDRESS>/api/v1/product-manufacturer/01f4b5bf9fef4561b8a9ce3906472136/translations
The error message is: Column not found: 1054 Unknown column 'product_manufacturer_translation.id' in 'field list'

Since translation tables don't need id column it is DAL issue.
See related pull request: https://github.com/shopware/platform/pull/72

We will be looking into this issue.
You are right, this is an issue regarding the DAL.

Hey @ascheider,
i created a ticket and I'll take a look.

@OliverSkroblin Hey Oliver, any updates on this issue?

@ascheider is this the same issue as here? https://issues.shopware.com/issues/NEXT-3822

@mitelg yes. it seems, currently all translation endpoints are broken no matter which endpoint are used. All translation tables have no column id which is correct.
So i guess it is DAL issue. I guess if you can solve the bug for the single endpoint, it will works for all of them.

ok, then I will close the issue here and you can give the existing ticket an upvote, ok?

@mitelg okay. i will give upvote to the existing ticket. I hope it will be fixed soon...


Re-add FNF

I have noticed that your old site has FNF on it. Would it be possible to re-add FNF to this site as well?

probably, the popularity of the game has gone down though. I'll probably wait until they make another update or i can find a build with all the weeks or something.


is tRPC really needed?

I did a little of experimentation with removing tRPC and relying on React Server Components for this project and it works just fine. I'm curious to know if there is something that tRPC provides that I'm missing.

Hi Mohsen, thanks for the comment!
I mainly added tRPC because I enjoy building with it. Blueprint is just meant to be a starting point that you can customize.
To make it easier for people to pick which technologies they want, do you think I should implement a few different versions that people can pick from?


NSwag studio incorrectly generates empty body

I have a spec, where a PUT request has no request body, only a response body defined:
'/redacted':
    put:
      security:
        - BearerAuth: []
      parameters:
        - description: Redacted
          in: path
          name: user
          required: true
          schema:
            $ref: '#/components/schemas/ObjectId'
        - description: The ID of the segment
          in: path
          name: segment
          required: true
          schema:
            $ref: '#/components/schemas/ObjectId'
      responses:
        '200':
          content:
            application/json; charset=utf-8:
              schema:
                $ref: '#/components/schemas/ResponseMessage'
              example:
                message: user removed from segment
          description: OK

Nswag studio generates an empty body for the content with the content type of the response. The generated code looks like this:
 request_.Content = new System.Net.Http.StringContent(string.Empty, System.Text.Encoding.UTF8, "application/json; charset=utf-8");
This causes an exception since the Encoding and mediatype are to be separately defined in the StringContent constructor. Removing the charset=utf-8 manually solved the issue, but I worry that this error will sneak in again when a new spec is generated. Could you solve this issue?
Kind regards

same here https://github.com/RicoSuter/NSwag/issues/4919


Extractor for GCP

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/52
Originally created by @tayloramurphy on 2018-06-18 16:07:26

https://cloud.google.com/billing/docs/
Related to https://gitlab.com/meltano/looker/issues/53

View 25 previous comments from the original issue on GitLab


Using % of the Master Balance

Is it possible to modify the order amount in order for every account use the same percentage as the master?
Example:
Master has 10 BTC and opens a new buy limit of 5BTC at 6500USD (50% of the balance)
Slave 1 has 14 BTC, the script opens a new buy limit of 7BTC at 6500USD (50% of the balance)
Slave 2 has 3 BTC, the script opens a new buy limit of 1.5BTC at 6500USD (50% of the balance)
Maybe changing the value "quantity=order['origQty']" adding the formula for the original percentage?
Thanks for the patience, I'm not very much experienced in developing.

I was working on this feature and stopped due to other priorities, can you help with it?

I’m not a developer but i can try
Sent from my iPhone

On Apr 18, 2020, at 10:43, Mohamed Rashad<EMAIL_ADDRESS>wrote:

I was working on this feature and stopped due to other priorities, can you help with it?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Is the problem still relevant? Maybe I can help.

I’m still looking for a solution, :/
Sent from my iPhone

On May 19, 2020, at 03:03, NickPius<EMAIL_ADDRESS>wrote:

Is the problem still relevant? Maybe I can help.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

@mokolotron I have no time to maintain this project now, can you help in this feature?

I can try it.

thank you. waiting for your update

Update Merged, please test the feature and let me know what do you think


Environment Variables Vault does not support special character in Postgres password

Is there an existing issue for this?

[X] I have searched the existing issues

Kong version ($ kong version)
3.0.1
Current Behavior
In https://github.com/Kong/kong/blob/3.0.1/kong/conf_loader/init.lua#L1478, string with special characters will be modified while loading/parsing environment variables.
Then kong will get the incorrect password if the dereferenced value of KONG_PG_PASSWORD contains special characters like #.
Consider this scenario:
export PG_CREDS='{"username":"user", "password":"p@ss#word"}'
# use vault expression to fetch the password for postgres
export KONG_PG_PASSWORD="{vault://env/pg-creds/password}"

# run migrations and temporary
# set CONF_SENSITIVE.pg_password = false at https://github.com/Kong/kong/blob/3.0.1/kong/conf_loader/init.lua#L548
# to see the result clearly
kong migrations up --vv | grep pg_password

...
2023/01/11 16:47:28 [debug] $refs = {pg_password="{vault://env/pg-creds/password}"}
2023/01/11 16:47:28 [debug] pg_password = "p@s"
...

You can see the expected password should be p@ss#word but it was changed to p@s
Expected Behavior
Not doing check_and_infer() for pg_password
Steps To Reproduce
Described in above

Anything else?
No response

I locally pathed in PR https://github.com/Kong/kong/pull/10099 and it works as expectation. Not sure the PR submission process and I'm interesting in contribution in Kong.

Linking to old quite related issue:
https://github.com/Kong/kong/issues/6360


Add PII Cookbook

Adding the PII cookbook using Presidio in addition to a couple of PII datasets

Closing in favor of https://github.com/wandb/weave/pull/2305


fix: integration tests for RM

PR summary

Fixes: <! -- link to issue -->
PR Checklist
Please make sure that your PR fulfills the following requirements:

[ ] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

These changes have been incorporated via cherry-pick


Change dynamic scope to call for atomic operations

To reduce false positives, we change the dynamic scope of a couple of operations to call.
E.g., writing to the registry is always done in one Windows API call, so we change the scope from thread to call.
Original discussion: https://github.com/mandiant/capa-rules/discussions/951

Thanks for all your suggestions, @jorik-utwente! I'm back this week to work on getting the improvements merged.


resolves STREAMS-346

general improvement to logging
use a predictable file ordering when processing a directory

travis failure is attributable to snapshot deployment failing in Jenkins https://issues.apache.org/jira/browse/BUILDS-88

lazy consensus merge 08/21 12pm


Is there a Babel preset for Ringo (Rhino?)

I'd like to use modern ES features and transpile them. I can easily do so by using @babel/preset-env with no options to transpile everything down to ES5. However, it means I'm missing out on some ES2015 features that are already supported in Ringo, such as for...of loops, arrow functions, etc.
Is there a Babel preset specifically tailored for Ringo (Rhino)? Or perhaps a Babel alternative that can be configured to target Ringo?

Not yet or not known, sorry.

I went and started https://github.com/pastelmind/babel-preset-rhino. Turns out it's a bigger hassle than I expected. I need help. Since RingoJS users may be interested in this project, I figured I'd ask here.
I created a Babel preset that piggybacks onto @babel/preset-env. I intentionally omitted the targets option, which turns on all ES2015+ transformations. Then I disabled any plugins that Rhino doesn't need, such as transform-for-of. I'm going through features listed on Mozilla's compatibility tables and using a test suite to verify that I'm only disabling transforms that I don't need.
Nearly all of the syntactic transforms are covered. I made some major assumptions, though, and I'd appreciate it if someone else reviewed them.
Babel 7 required
I don't want to bother with older versions of Babel.
Promises and async/await
Rhino does not natively support setTimeout(). Since most Polyfills for Promises rely on setTimeout(), they won't work either. I therefore skipped transpiling async/await features entirely.
❓ Question: I don't use RingoJS, but I understand it supports setTimeout() and a library version of Promise. Would you be interested in having async/await transpiled as well?
(Caveat: Babel doesn't know that RingoJS has to import Promise from ringo/promise. If async/await is polyfilled, RingoJS users would have to manually import ringo/promise in every file that uses async/await. Or perhaps write a custom Babel plugin for it.
New RegExp flags
Since Rhino does not support the newer RegExp flags (y, u), I didn't bother transpiling them. See below for more discussion.
Polyfills
I'm struggling with Babel's automatic polyfill import feature (enabled with useBuiltIns: 'usage'). For example, preset-env tries to polyfill Object.keys() even though Rhino supports it. I can easily disable this by excluding individual polyfill packages (es.object.keys). However, there are gotchas:
Some polyfills depend on each other. For example, the es.string.split polyfill is normally not needed, since Rhino already supports String.prototype.split(). However, if you want to use the y and u RegExp flags, es.string.split must be used along with es.regexp.exec to support them. I only discovered this after attempting to transpile String.prototype.split(). This is problematic because such dependencies are non-obvious.
❓ How should I generate a set of polyfills that can be safely excluded, given that polyfills have hidden dependencies?

Also see https://github.com/mozilla/rhino/issues/661 and https://github.com/babel/babel/pull/13448


Add Member Match and Bulk Export Client Prebuilt Services

Purpose

Add member match and bulk export client prebuilt services under regulation/cms-0057-f
fix minor issues identified in the review

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes
Ran FindSecurityBugs plugin and verified report? yes
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

@isuruh15 let's add read me to the pre-built services.

fixing: https://github.com/wso2-enterprise/open-healthcare/issues/1554


Camera zooming itself when right clicking

Description
When right clicking in game, the game camera changing its position as if it's zooming by itself.
To Reproduce
Run the game and right click in order to rotate the camera.
Tasks

[x] Fix game camera rotation control when right clicking

PR to fix this: https://github.com/ko4life-net/ko/pull/104


Is the code real

I tried to run it.
First of all, there are many errors in the code, which looks more like it is not the final version of the code.
For example, GitHub says that it needs to run coveragetask_ 20rob_ large_ 6FOV_ 8STEP_ 10COMM_ 3layer_ 2filtertap_ GNN2layer_ 32_ 128.json file, but actually the file name in the project is called coveragetask_ 20rob_ FIX_ 6FOV_ 20STEP_ 10COMM_ 3layer_ 2filtertap_ GNN2layer_ 32_ 128.json。 There are many such errors, but they are all small problems. The modified code can still run.
Finally, I generated the data set according to the instructions on GitHub and conducted 1500 training (the training command was strictly in accordance with the instructions on GitHub). The final result shows as follows:
Train Accuracy: 99.91666666666667%
Train Loss: 0.009591424837708473
Num agents: 20
(40, 20, 5) (40, 20, 5)
Valid Accuracy: 33.0%
Valid Loss: 18.934585571289062
Num agents: 20
(40, 20, 5) (40, 20, 5)
Test Accuracy: 32.875%
Test Loss: 19.36847686767578
Why? This is completely different from the result of the paper. Isn't it true that the paper has an accuracy rate of about 88%? Why is there only about 33% here?
Seriously, I really hope that this code is true and the final effect is really like that described in the paper. But after I read your source code, I felt deeply worried (your work should be based on the code of Qingbiao Li, and I have carefully read his code)

Thanks for pointing out the issues. The code has been updated to reflect the correct path and options.  We'll also upload the data and pre-trained model before closing the issue. The earlier README was written in an indicative manner. It has also been updated. Apologies for the inconvenience.
About the accuracy: the paper reports coverage performance, which is different from prediction accuracy. Prediction accuracy checks if the predicted action is exactly the same as the expert action. This metric does not consider the efficacy of a suboptimal action, which may cover fewer rewards than expert action, but still perform better compared to other possible actions.  We have updated README to mention this and moved the code to check reward coverage up.
The accuracy you obtained suggests overfitting which we did not observe. We're testing this code and will add updates to the thread.

The link to the model and data have been added to the README.
The code seems to work fine at our end i.e. we were able to train the model without overfitting in 1500 epochs and provide good coverage. The accuracy was around 55% for this model. Please try other checkpoints to see if they provide good performance without overfitting.

Thank you for your patient answer and arrangement : )


Minor change in reqparse

I was having a problem generating parameters using reqparse parser. Sometimes I had a path parameters in my resources and I still want to use the request parser functionality. For that I used the parameters and rerparser properties in @swagger.doc like this:
"reqparser": {
    "name": "User signup info",
    "parser": postreqparse
},
"parameters": [
    {
        "description": "User email",
        "in": "path",
        "name": "email",
        "type": "string",
        "required": True
    }
]

that provoke the following exception 'parameters and reqparser can't be in same spec'.
if 'parameters' in operation:
  raise ValidationError('parameters and reqparser can\'t be in same spec')

For that to work for me I wanted both the method to work together, like a concatenation of parameters and reqparser so the output should be like this
"parameters": [
    {
        "description": "User email",
        "in": "path",
        "name": "email",
        "required": true,
        "type": "string"
    },
    {
        "description": "Request body",
        "in": "body",
        "name": "body",
        "required": true,
        "schema": {
            "$ref": "#/definitions/User signup info"
        }
    }
]

I fix this problem on this commit concatenating the result of reqparse parser and parameters and it worked as expected.
I think that could be useful for someone like that was for me. So thats the reason of this pull request.
Hope I helped,
Thanks for this awesome worked,
Cheers,
Marco Mendão

I think given the scope of this change, and the state of the two projects, I'm going to close this PR.

I'm actually not sure what to do with this one, I'm going to checkout the branch and play around with it.  @Menda0 @soerface what do you guys think, should we try to merge this in still?
Been a long time, but it would be a shame to lose all this work.

Hi again guys, I'm very reluctant to close this PR, but I think it might be best to allow the two repositories to differentiate with the versions of the spec they support.  I'll wait a few days, incase you guys have thoughts on this.

Sorry, didn't realized my commits were in this pull request. My changes are definitely breaking, I realized that pretty much things were different between swagger 1 and 2. So IF we want to merge, it would be more like a "if swagger 1 use this package otherwise use the other package".
Also, I'm currently have no time to support my package, so I also won't be able to contribute to this one, too. I guess co-existents of both packages seems like a good solution.

Sounds good, I'll start redirecting folks looking for this functionality to your project.


chore(Template): improving templates and updating a few areas that were using older alpha api modules

Hopefully this helps :)

@NathanWalker — Thank you Nathan, you rock!!


feat: system diagnostic monitor message

Related Links
https://github.com/autowarefoundation/autoware.universe/issues/3829#issuecomment-1702392865
Description
Add diagnostic graph message.
Remarks

Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[x] Code is properly formatted
[x] Assign PR to reviewer

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code is properly formatted
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets
[ ] Write release notes

CI Checks

Build and test for PR: Required to pass before the merge.
Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

LGTM


feat: import spec from file on editor init

Description
The purpose of this PR is to allow the users of the Studio Docker image to be able to initialise the container with the spec of their choice by providing a Docker bind mount.
Related issue(s)
Resolves #403

@steevehook Hi! Do you need help?


[Feature Request] Center to Screen

It would be pretty cool if there was a configurable option to let the loading window center to the screen for a more seamless transition.

Center to the screen? You mean like open in the center of the screen?


Initialize render target when window size is not specified on Windows

Fix #1426.
As I commented on that issue, When the window size is not specified, WM_RESIZE is not emitted before first WM_PAINT. So, rendering is called without creating the render target.
I tested on Windows 10 Pro 20H2. With this patch, all examples are successfully showing the window without panic.

I'm okay with this patch for the time being. It also fixes #1582.
Reason is that way render_target is created is really unorthodox anyway, I might make a bigger PR to refactor whole render_target creation. Usually it's created on demand during render (e.g. WM_PAINT). RIght now the render function just unwraps the render_target and crashes if it's not there.


Clients are connected but sometimes don't use routes

Describe the problem
We use Netbird in our Org with around 45 users.
It is selfhosted with azure auth (that works great).
The Mac clients have the most problems and don't wake up after sleepmode (there is already a bug ticket for that), but still show that they are connected.
But the Windows Clients have a similar problem. They often simply don't use the routes, but they are visible and active on the client.
They work after reconnecting and using the incognito tab. Clearing the cache every time is no option. We have configured an exit node for some clients for all traffic but they simply are not used many times by the browser (edge, chrome and safari).
Some people started reinstalling the client every time, because even down and up doesn't work.
The Linux client seems to be the only one without any problems.
I really love the system and want to use it, but management already starts to hate it, and I would really love to fix that.
All clients are up to date, everything seems to work except the simple connection itself. It works often, but just stops.
I have tried every tip I found in the Issues and update as soon as a new version comes out (and read the changelog), but the problems keep appearing.
To Reproduce
Steps to reproduce the behavior:

Install Netbird
Use Netbird for some time
Routes stop being used without changing anything

Expected behavior
The Netbird Clients should use the configured routes unless it is deactivated, the clients should reconnect after sleep mode.
If a full-tunnel vpn is configured via an exit node all traffic should go through that, without any leaks.
Are you using NetBird Cloud?
No, selfhosted
NetBird version
Always uptoDate, 0.28.9

We are experiencing the same issue on Windows 11 clients using the Saas Hosting.
netbird status -d shows that peers are connected but no more WireGuard handshakes seems to be made after about one minute from the Last connection update.
Apparently disabling Quantum resistance on the peers seems to solve the issue.

I already tried it with activated and deactivated Quantum Resistence and Network Monitor.
The Network Monitor already improved the experience on Windows Clients but it keeps happening.
For the Macs the obvious bug after going to sleepmode seems to be the main problem, but all clients except the linux systems lose connections after some time even though the network is stable and it shows that it's connected.
And sometimes it still works in an incognito tab oder cleared cache browser, but that's no option. The browser does seem to forget that it should use the provided route.

I am also losing my routes. I have a VPS to check my infrastructure, but it loses routes three times a week.
This is what appears in the logs when it happens:
OPrXKmXCMxZSe2gzzHXXXXX=, endpoint address: 85.xx.xx.xx:51820
2024-09-06T04:53:29+02:00 WARN signal/client/grpc.go:160: disconnected from the Signal service but will retry silently. Reason: rpc error: code = Internal desc = server closed the stream without sending trailers
2024-09-06T04:53:33+02:00 INFO signal/client/grpc.go:147: connected to the Signal Service stream
2024-09-06T04:59:21+02:00 INFO client/internal/peer/conn.go:362: connected to peer nav0xxxxxxxxxxxxx

Both clients are running on Linux: version 0.28.9 - SaaS version.

Same here on Windows, network routes seems to dissappear after a while. Changing then something server side in the routes (like active/deactive on route) seems to trigger a client update and network routes appear again.

@mlsmaycon  Any information you need that can help troubleshoot?


Use stdlib errors instead of github.com/pkg/errors

github.com/pkg/errors is archived, and the README says it is in maintenance mode. The standard library errors package is built-in.

Thanks. I've changed the error strings back. I was changing them a bit mindlessly - but I'd love to change them all, and in doing so make sure they are printed with some adorning context.


CSS

CSS
s a boot camp student
I want the prework notes to be structured on a webpage
So that I can easily find and read the information
GIVEN a Prework Study Guide website
WHEN I view the study guide
THEN I see a dark blue header and footer, and four boxes with a shadow

Added CSS code to my prework study guide


Neeth04/chore/update doc

Description of this change

Change uid to requestID from UUID

Why is this change being made?

[ ] Chore (non-functional changes)
[ ] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How was this tested? How can the reviewer verify your testing?

Will deploy and test on UAT
Related issues

KD-5080
Checklist

[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[x] I have evaluated the security impact of this change, and OWASP Secure Coding Practices have been observed.
[x] I have informed stakeholders of my changes.

Can you run this by @sethyates  as well?

closing this a we have decided to keep the uuid


There is no choice to download without hardware

Describe the bug
There is no choice to download without hardware
Steps to reproduce the behavior

Navigate to https://arcade.makecode.com/beta#editor
Click "Sprites" -> drag block "set sprite to" and put it under block "on start"
Click "Download" and observe this page

Expected behavior
There should have a choice to download without hardware
Actual behavior
There is no choice to download without hardware

Desktop (please complete the following information)
OS: Windows
Machine build: 17763.1.amd64fre.rs5_release.180914-1434
arcade version: 0.3.6
Microsoft MakeCode version: 5.2.38
Additional info
This issue repro on Edge, Chrome, Firefox and IE

This is expected. Save as is in the menu. But I can see the confusion. @riknoll


Not enough amount to return loan error

The following error message is expected when you run flashloan with no arbitrage opportunities.
Fail with error 'Not enough amount to return loan'
When the bot says there's an arbitrage opportunity and run flashloan, the transaction gets reverted because of the above error.

https://github.com/yuichiroaoki/poly-flashloan-bot/discussions/36


Update init.py

preparing release 0.3.2

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

Please upload report for BASE (main@e459e1b). Learn more about missing BASE report.

Files with missing lines
Patch %
Lines

multiurl/__init__.py
0.00%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #18   +/-   ##
=======================================
  Coverage        ?   13.24%
=======================================
  Files           ?       14
  Lines           ?     1034
  Branches        ?        0
=======================================
  Hits            ?      137
  Misses          ?      897
  Partials        ?        0

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


[dv/rstmgr] Fix typo in rstmgr_cascading_sva_if.sv

Fix error flagged by dsim.
Signed-off-by: Guillermo Maturana<EMAIL_ADDRESS>

This is trivial... Funny other simulators don't flag it.


move to sbt 1.x

@adamw please check it out

Needs a rebase

Will rebase today

@adamw rebased

Released in 1.4.11. Thanks!

thank you!


Hard-coded absolute, non-existing cache path in V3 Common-js version

System Info
Transformers.js 3.0.1
running in node 18 using CommonJS
Environment/Platform

[ ] Website/web-app
[ ] Browser extension
[X] Server-side (e.g., Node.js, Deno, Bun)
[ ] Desktop app (e.g., Electron)
[ ] Other (e.g., VSCode extension)

Description
When using transformers.js in a common-js based node application, I'm running into an error message when loading a model. It cannot be written to a local cache.
The reason for this is that somehow the file transformers.cjs has the default path to the cache directory hard-coded to an absolute directory path in DEFAULT_CACHE_DIR, it's set to this path: /home/runner/work/transformers.js/transformers.js/.cache/.
Reproduction
import { pipeline } from '@huggingface/transformers';
const pipe = await pipeline('zero-shot-classification', 'MoritzLaurer/mDeBERTa-v3-base-xnli-multilingual-nli-2mil7', { dtype: 'q8'});

Getting this error message:
  errno: -2,
  code: 'ENOENT',
  syscall: 'mkdir',
  path: '/home/runner'
}

The same error does not happen when using the dynamic import instead.
const pipeline = (await import('@huggingface/transformers')).pipeline;

That's because in that case transformers.mjs is used instead of transformers.cjs and the former does not have the cache path hard-coded

Hi there! Thanks for the report. This seems to be an issue with our webpack setup for building the project in GitHub actions (hence the name). Will look into this.


Fix compatability with fish vi key bindings

PR #420 addressed the existence of pagination in a fish prompt by trying to track when pagination was enabled and disabled. This introduced atuin-specific bindings for common keys: \t, \e, \r, and \n which export a variable and informs the _autiun_search function to not show the TUI.
Fish has a commandline function that will instead tell you whether pagination is enabled so the user doesn't need to keep track of that state. This PR uses this function, commandline -P to replace the prior TUI supression scheme. Removing these extra function calls allows us to remove the additional bindings which were breaking fish vi key bindings.
Replacing the value for bind -M insert \e completely breaks vi mode by blocking the user from exiting insert mode. By removing these extra binds, this PR restores fish vi mode compatability.

Oh nice! Thanks for cleaning this up, this is a nicer solution 🙌


x/tools/cmd/callgraph: calls to interface implementation not reported in cha callgraph

Go version
go version go1.22.1 darwin/arm64
Output of go env in your module/workspace:
GO111MODULE='auto'
GOARCH='arm64'
GOBIN=''
GOCACHE='/Users/usr/Library/Caches/go-build'
GOENV='/Users/usr/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='arm64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/usr/pkg/mod'
GONOPROXY='github.com/redacted-org'
GONOSUMDB='github.com/redacted-org'
GOOS='darwin'
GOPATH='/Users/usr'
GOPRIVATE='github.com/redacted-org'
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/opt/homebrew/Cellar/go/1.22.1/libexec'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/opt/homebrew/Cellar/go/1.22.1/libexec/pkg/tool/darwin_arm64'
GOVCS=''
GOVERSION='go1.22.1'
GCCGO='gccgo'
AR='ar'
CC='cc'
CXX='c++'
CGO_ENABLED='1'
GOMOD='/Users/usr/src/github.com/samuknet/ssa-bug-report/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/q3/l93pryxj2dz39p1d2gy9v2p40000gn/T/go-build1879381070=/tmp/go-build -gno-record-gcc-switches -fno-common'

What did you do?

Create example.go in a temporary package

package example

func EntryPoint(ex exampleInterface) {
	ex.InterfaceFn()
}

type exampleInterface interface {
	InterfaceFn()
}

type exampleA struct{}

func (u *exampleA) InterfaceFn() {}

type exampleB struct{}

func (u *exampleB) InterfaceFn() {}

// NewA() returns an exampleA.  Note return type is exampleInterface.
// Results in exampleA.InterfaceFn() being added to the callgraph, as expected.
func NewA() exampleInterface {
	return &exampleA{}
}

// NewB() returns an exampleB. Note the return type is *exampleB.
// exampleB.InterfaceFn() is not included in the callgraph.
func NewB() *exampleB {
	return &exampleB{}
}

Install latest version of callgraph

go mod init
go get golang.org/x/tools/callgraph
    go: added golang.org/x/mod v0.16.0
    go: added golang.org/x/tools v0.19.0
go install golang.org/x/tools/cmd/callgraph

Run  callgraph -algo=cha . in the directory of example.go

Output is
github.com/samuknet/ssa-bug-report.EntryPoint   --dynamic-9:16-->       (*github.com/samuknet/ssa-bug-report.exampleA).InterfaceFn

What did you see happen?
Output includes just exampleA.InterfaceFn():
github.com/samuknet/ssa-bug-report.EntryPoint   --dynamic-9:16-->       (*github.com/samuknet/ssa-bug-report.exampleA).InterfaceFn

What did you expect to see?
Output to also include exampleB.InterfaceFn() in addition to exampleA.InterfaceFn().
Note this report is similar to this issue,  but more specific to interfaces and reproduces regardless of whether the interface type is exported.
In particular:

if the function signature uses the interface as the return type, then the interface implementation is included in the callgraph. See NewA() example above.
if the function signature uses the concrete struct as the return type, then the interface implementation is not included in the callgraph. See NewB() above.

The issue persists regardless of whether or not the interface type is exported.
Findings so far
We've identified this commit resulted in the change of behaviour.
Prior to this commit, the callgraph for example.go contains both interface implementations. After the commit it includes just exampleA.InterfaceFn() but not exampleB.InterfaceFn().
From the commit I can see  it's now expected for unexported types not to be included in the callgraph by default. Though I'd like to understand whether this change also intended to no longer include interface implementations in the callgraph in the example above.

@taking @adonovan @zpavlinovic

It seems to me that what happens is that the function exampleB.InterfaceFn is not even considered by the core cha algorithm. That is, ssautil.AllFunctions is called first to collect all functions potentially needed by the program in a linker-style fashion and this linker does not pull in exampleB.InterfaceFn.
This linker is conservative, but it will try to remove functions that clearly cannot be called. Here, it figures out that since exampleB is not passed to any interface in the program, then it cannot be called in EntryPoint.  Hence, exampleB cannot be really used anywhere in this particular program.
On the other hand, exampleA is returned as an interface so in principle exampleA.InterfaceFn can be called in EntryPoint.
You can see this if you change the return type of newB to be the interface or you do something like this:
// NewB() returns an exampleB. Note the return type is *exampleB.
func NewB() *exampleB {
        b := &exampleB{}
        var i exampleInterface
        i = b
        fmt.Printf("%v\n", i)
        return b
}

Thanks for the report.
This seems to be a regression introduced by my CL https://go.dev/cl/538357, which caused AllFunctions  to return fewer items in this case. But fundamentally I think the problem is that CHA should not be using AllFunctions: its name is misleading, as it doesn't return all functions, it does (and always has done) a reachability analysis, which is not appropriate for CHA, which wants to return the maximal sound call graph without any reachability filtering at all.
I think the solution is for CHA to (like RTA) stop using AllFunctions.
Even more reduced example demonstrating the significance of exportedness:
package example

func EntryPoint(i I) { i.f() }

type I interface{ f() }

type A struct{}

func (*A) f() {}

func NewA() I { return new(A) }

type b struct{}

func (*b) f() {}

func Newb() *b { return new(b) }

type C struct{}

func (*C) f() {}

func NewC() *C { return new(C) }

$ go run ./cmd/callgraph -algo=cha ./a.go
command-line-arguments.EntryPoint       --dynamic-3:27-->       (*command-line-arguments.A).f
command-line-arguments.EntryPoint       --dynamic-3:27-->       (*command-line-arguments.C).f


chore: trigger CD from CI workflow

So, before, the release workflow was triggered every time the build one was completed, regardless of what triggered the latter.
This was not the intended behavior.
Now, instead of having release 'listening on' the completion of build, build is calling release when its been triggered by a push to main

Why did the lock file changes 🤔 ? npm version ?

It's to be on caution side, there's been a bunch of release done by this issue, I want to ensure everything is 'proper' before going ahead.


"Not authorized: ..." error on web page

I am running the expensive relay from master but unable to generate an invoice via the webpage.
Ive got CLN running, my env variables look correct, postgresql running without any issue, bitcoin-cli and lightning-cli are happy. When I go to http://localhost:7447 and paste in a nostr pubkey to generate an invoice I get:
Not authorized: method does not start with list AND method does not start with get AND method is not equal to summary.  My commando plug in is not reporting any issues. Any clues on how I can troubleshoot this would be appreciated.

You need a rune that is capable of calling both invoice and listinvoices.

Can someone out there tell me if this is a legit bitcoin Receipt?
https://mobile.twitter.com/fightwithmemes/status/1627051224041410561/photo/1


:racehorse: Widen tables for benchmarks

The domain model used for many of the benchmarks only had a few columns
per table, which is probably not representative of the most common
scenarios that EF is used in. This expands them to have more columns.
I also collapsed data seeding into the test fixture, because now it is helpful
to have the helper methods for creating entities with their fields populated
available in the test code.
I did look at using AdventureWorks for all the tests (we use it for the
initialization tests), but it gets hard to zero in on a particular
scenario using the data patterns and counts that are present in the
database.

BTW one side effect of this is that we will need to clear out our benchmark history. There really isn't a way to adjust the existing results to retrospectively adjust for these changes. Unfortunate to loose the nice burn down graph of the perf improvements :-1:

@rowanmiller Re-run the new code against old commits :-P

Or, better, make the new graph go down again soon :-)

:shipit:


Broken Link in Office Container

The section 'Office Container' has a broken GitHub link in the second paragraph.
"[exclude certain data] (configure-office-container-tutorial.md#configure-third-party-exclusions)."

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

ID: 724f8d94-c061-f591-0f64-4fea04b8256d
Version Independent ID: f896ff2e-90d1-5c9e-b2ce-a3e649fb4990
Content: Profile Container vs. Office Container - FSLogix
Content Source: fslogix-docs/profile-container-office-container-cncpt.md
Product: fslogix
GitHub Login: @DougCoombs
Microsoft Alias: docoombs

Links in this document currently appear to be correct, this might have been corrected in an early round of fixes.


UX change.

Do we need to move these a little?

There should be a comma (,) after 36.

we need to apply the right number format depending on the currency/ locale.

Extra space between 10,000 and sats. Also, in some places it mentions t-sats and others it mentions sats. We need to bring in consistency all across.

Text change: "Available after Level 2 Backup"

Remove the red dot for now from Swan.

Verified this issue on dev app v2.0(344)


add test_torch

issue https://github.com/intel/torch-xpu-ops/issues/302

merged at https://github.com/intel/torch-xpu-ops/pull/407


looper: Require Send when adding fd event callbacks on ForeignLooper

ForeignLooper allows (re)registering callbacks on threads that are not the ThreadLooper (current) thread.  Since these calls will be executed on that ThreadLooper thread when the user calls any of the poll() functions, these closures have to pass a thread boundary which requires Send.

Found a way, but I think add_fd_with_callback_assume_send() should be unsafe.


add top level permissions: read-all for openssf

PR Type:
Enhancement

PR Description:
This PR introduces a new top-level permission, 'read-all', for OpenSSF. This permission has been added to the workflows for when a pull request is created and when a pull request is merged. The changes aim to enhance the security and control over the repository by specifying the level of access required for these workflows.

PR Main Files Walkthrough:
 files:
.github/workflows/pr-created.yaml: Added 'read-all' permission at the top level. Also, some formatting changes have been made.
.github/workflows/pr-merged.yaml: Added 'read-all' permission at the top level. Some formatting changes have been made and the condition for the 'pr-merged' job has been updated to skip if not merged.

closes #170


Support parsing DDI 3.x Instance documents

Many service providers offer metadata using DDI 3, and some only offer metadata supporting DDI 3. This issue tracks implementing support for DDI 3.x instance documents (see https://www.ddialliance.org/system/files/DDI 3.2 Best Practices_0.pdf for a description of the difference between DDI instance and fragment documents).
The structure of DDI 3.x is significantly different from DDI 2.x which necessitates a different set of parsing strategies, but basic parsing can be acheived using the existing strategies.

[x] #622
[x] #624
[x] #625
[x] #626
[x] Handle variations beyond the CMM
[ ] #639

DDI 3.x instance documents are now fully supported


docs: deployment

Changes proposed in this pull request

[x] describes how to run and shut down local env
[x] describes how to interact with local env
[ ] describes test env
[ ] describes how to run in prod
[x] describes all possible environment variables

Context

fixes #236
fixes #515
fixes #866
fixes #1121
fixes #1003

Checklist

[ ] Related issues linked using fixes #number
[ ] Tests added/updated
[ ] Documentation added
[ ] Make sure that all checks pass

The production environment section is still WIP and depends on the helm charts.

Should we rename mock-account-provider into mock-account-servicing-entity?

I think that would be a good change, maybe can be held off for a separate PR.
Also, what do you think of
https://github.com/interledger/rafiki/issues/1173#issuecomment-1446772974

does something need to change for this PR in postman?
Yes, the Host headers. But I didn't want to do that prior to merging.

Host header(s) say ""
Where is the value calculated?

@wilsonianb
I meant the Host headers in Postman:

I now have a Postman fork where all of them are updated.
I'll create a Postman PR for that. While updating, I found 2 small bugs in this PR. They are fixed now.

@wilsonianb if you clear the volumes and restart the MAP, does it work then?


Create index.d.ts

Declaration file for use sqlite-parser from Typescript code https://basarat.gitbooks.io/typescript/docs/types/ambient/d.ts.html

Could you please add this file to give type support to typescript apps that uses sqlite-parser?

Hi, @euginio, this is a great idea! I took a look over what you created and there are a few issues. There are three ways to invoke the main parser function. One takes a string and an option options object, and the other two take either a string, an option options, and a callback or just a string and a callback. The latter forms are used to call the parser asynchronously and provide the resulting AST or error to a callback function.
There are also a number of other properties defined on the default function, such a a version string, and some additional things that are exported by the module.
We probably also want a full set of interfaces or just an any type instead of a partial set of typings for the AST.
I believe the current process for releasing 3rd party typings for a library involves releasing them under the @types scope on npm (e.g., @types/sqlite-parser).

Hi, @nwronski, regarding to your suggestions about issues: I'll make the changes you suggest, but I think we don't need to complete all the API the library exposes in the definition file, but it could be done on-demand.
Regarding 3rd party typings: https://github.com/DefinitelyTyped/DefinitelyTyped (aka @types) is the best approach to publish definition types when you can't access to oficial package repo (your repo). But always is better to give your users TS types support from the own repo (adding this d.ts file to the root dir and the line "types": "index.d.ts", to package.json

I think I should go to DefinitelyTyped?