PR pileup

The list of pull requests seems quite long, with several PRs numbering in the thousands of lines changed. Can someone work on getting these worked into various branches or closed with at least a "Thanks for your contribution, but now's not the right time" response? I am aware a lot of energy is going into the core CLR support, and the community agrees that is very important. However, I fear this repo is in danger of dissuading OSS contributions due to perceived futility. It is no fun trying to keep a PR up-to-date with a moving target, and it is no fun trying to merge stale PRs.
Several possible directions for moving forward, most mentioned elsewhere:

Split VS tooling, the compiler, and other parts to make it easier to maintain each repo.
@KevinRansom has mentioned to me many times that MS has to handle certain things, e.g. Core CLR, templates, etc. If this is the case, then perhaps we should focus external contributions on https://gihtub.com/fsharp/fsharp with a clear migration path between that repo and this one.
Create a community branch and assign community members to merge PRs into that branch and keep it consistent with master or another, MS maintained branch so that we are at least keeping things moving.
Create a Kanban-style goal of a maximum number of allowed open PRs and commit to merging or closing them daily or weekly.
Treat all branches as equals. Core CLR is very important, but it should not shut down all work in the repository or it becomes a terminal disease. Each feature branch should merge in master until it is ready to merge into the main branch. That may delay important features a bit, but I think that's worth the effort.
I'm sure other good ideas will avail themselves.

Projects get a lot of excitement by managing their contributions well. Rust does this well. @forki is regularly praised on Twitter for his amazing success with PRs and issues. Please make visualfsharp a success, as well.
NOTE: I wasn't entirely sure where to post this, so I'm going with an issue here.

Agreed, having to keep a PR open and working for months is frustrating!

:+1: some pr are ready, these should go in or closed.
But the close reason should not be "there is no time for merge/testing", that's deadly for community.
If a pr it's a good feature/bugfix, it's reviewed, should go in, in master branch.
Having only a master branch, it's better because everyone try the same branch. Who try coreclr branch? we are only delaying issues to next merge. And i need to build multiple times to test the compiler.
If the problem it's the fear of bugs before rtm, let's use a stabilization branch (like roslyn) or a relase branch before rtm. If now the coreclr it's the developmente branch, all pr should target it.

about split, see #861 or #441 , it's really a big repo, let's make it easier to manage it.
about two repositories ( fsharp/fsharp and visualfsharp ) please dont do it. Not if they are the same codebase, It's tons of time wasted on merge ( see #853 from fcs, or the multiple merge into fsharp/fsharp ). From visualfsharp -> fsharp it's easy, @dsyme and community can help ( they are merging already from visualfsharp ). The problem from fsharp -> visualfsharp it's the same problem as having pr to merge, but worse because merge are going to be bigger. Lot bigger. If @dsyme say that visualfsharp it's the gold repository to contribute to compiler/fsharpcore/etc, we should make pr there. fsharp/fsharp it's only packaging. If the policy change, ok, but having two released compiler/fsharpcore versions (community and ms ) with different features/fixes it's a bad idea, really bad. The gold repository should be only one. Same for FSharp.Core nuget. We are really going to have two different nuget packages for coreclr/desktop and mono/etc ( ref #861) ?
community branch = unstable = it's the master branch. I dont understand how that can help if the release it's from ms. What we do if ms doesnt want to merge a commit from community branch? that's more work, who can be done with review inside a pr.
promise to close/merge x pr each week it's good.
i think coreclr branch should be merged inside master. There is no need for a different branch. It's the developmente branch. For example i want to add responsefiles, i need to wait merge in master, and sync from master -> coreclr. Now coreclr branch it's stable, move it inside master branch, the codebase it's going to be merged anyway. Less time wasted on merge, more time for review pr.

@enricosada, I agree. I just thought I would throw out some options for the sake of argument. You have fulfilled my hopes. :dancer:

@panesofglass I get what you're saying. @enricosada is an active contributor to the repo and makes some important points.
Equally, it's very important that we don't put pressure on repo owners to merge anything that might risk regressions or be destabilizing - or at least to fully evaluate the cost/benefits.  I do feel that some "please merge" pressure was part of what led us to do inadequate code reviews on an optimization PR for Visual Studio 2015 update 1, which led to a regression. I don't want to see further regressions like that, and I'd prefer a PR pile up (ultimately resolved by the contributors) than regressions.  If necessary, PRs can stay open for as long as needed until we're 100% comfortable with merging them.

@dsyme that's a fair point. Is there a strategy that can be put in place to alleviate the effort to keep PRs up to date though? A PR staying alive for months means that typically the contributor has to ensure that it keeps up to date with the latest master lest it be disregarded later on for being too old (something we have seen happen before).
I'm not saying the team should be accepting PRs willy nilly or feeling pressure from the community - that's not the right option either - but is there some way to meet in the middle?

@isaacabraham  Well, in some sense there's no meet-in-the-middle w.r.t. stability and quality :)
But yes, I understand what you're saying. If we deem a PR is unsuitable for an update release, then it will necessarily be delayed until the branch is ready for the next major revision.  (We should probably encourage a process where PRs can be brought up-to-date by people apart from the submitter, though GitHub doesn't make that particularly easy since the PR has to be resubmitted).
One way we can get PRs in is to open "next major version" branches.  However branch management takes significant time and can itself be error prone and a cause of fragmentation in the repo - again making it harder to contribute. Until a "next major revision" branch is open, it is better to keep the PR open and incrementally update it. This may be likely to happen with any major language work, or major optimizations.  It's in the nature of the beast.
I do think splitting the repos into IDE tooling and Compiler would be helpful.  I'm less concerned about splitting out FSharp.Core though that could also be done.
I don't like seeing any PRs closed because they are "too old" unless they truly bring no value and should be closed anyway, or have truly diverged to the point that they can't be rescued.  If you see examples of this please from the past please link to them.
We all want F# to both progress, evolve and yet be stable and reliable.  But generating excitement via a high rate of PRs is not a goal in and of itself - only where it achieves other goals.

Perhaps one thing could be for a "quick review" up front by someone in the team and at least provisionally give a go-ahead in principle for acceptance of a PR. In this way, if a PR is unsuitable because e.g. feature not needed / implementation or whatever - it can be closed off quickly. On the other hand, ones with value can then be grouped into a bucket for review - and a process can be put in place to deal with them (somehow).
This is somewhat akin to how you deal with UV feature requests - a quick review to identify ones of value in principle, and then a more detailed review later on.
Not saying that that is a perfect solution, but maybe a start?

Regarding the "too old" comment - I thought that some of the work on unit tests was held off for a long time in the run up to F#4 and then eventually rejected as out of date => risk of merge too high. I might be completely wrong here though.

@isaacabraham I think that may eventually have been merged.  But if not I suspect the repo owner may have been more worried about churn, scale of change and so on.
The same could well happen with any piece of work. My experience making contributions to different projects over the years is that the larger the piece of work the longer it takes to be integrated, the harder it is to find a suitable place to integrate it, and the more at risk it is of eventually being bumped.

Perhaps one thing could be for a "quick review" up front by someone in the team

I think that happens already.

Thanks for your reply, @dsyme. I don't have any recent contributions waiting. I submitted a PR a long time ago for the web project templates when the fsharp source was on Codeplex. I was told someone would move them over and that a lot of work was required on the MS side and that I would be unable to help much more. I've never seen those merged or even brought over into this repo. I know templates are wanted, but I have no motivation to do anything more given what I know about the template contribution process (in that it doesn't appear to exist).
I raised this issue b/c 1) I was made aware of the large number of outstanding PRs and 2) I have seen some frustration and heard comments indicating that future contributions were going to be forfeited. That's a really sad plight to an OSS project, and I hoped to identify some way to help move things along.
Another option I did not yet propose would be someone maintaining a community fork that would assimilate community contributions into a single, ever-growing PR for the owners of this repo to review and merge. This option puts the onus of verifying contributions on the community first, thereby hopefully cutting the time required by the owners of this repo. At present, this would represent both a massive effort and a massive PR, which I agree would be very difficult to merge. The bright side is that once this is done, the community could provide a single stream of community contributions for review by this repository. I suggested fsharp/fsharp above b/c that would at least provide a more direct line to releasing testable alphas on NuGet. However, since it is not a fork of this repo, moving contributions back becomes more difficult (unless something has changed).

Also, fixing the testing situation could help address the problem of regressions by allowing us to add more tests more easily.

@dsyme nobody is asking for bad quality pr, or fast track merge, but i think 3 weeks is enough time for multiple reviews and feedback. If after three weeks a pr is not ready, should be dropped.
I think more people should contribute to review, that's a really important part.
That mean repo owner too, if possibile not only @KevinRansom but also @NumberByColors and @otawfik-ms .
Everytime i wrote better code (bug, cleanup, perf) in my prs with review feedback from you @dsyme, @KevinRansom and community.
And i learned a lot too.
If a pr is too big that can be split in multiple smaller pr, easier to review, and let some time pass between each.
For example i have one pr for in memory compilation, that's a refactoring only, with minimized diff. After that pr is merged i'll continue with another with the api for in memory compilation, and another with files in memory like source files.
I understand everything can break (i wrote a regression for binary compatibility with f# 4 last time, so i understand), but having a more fluid release process and beta, can help a lot.
If v4.1.0 break something, the v4.1.1 can fix it. it's better is we can do that fast, like having a separate fsharp.core nuget package => faster release than compiler. The full packaged release inside visualstudio can release the latest nuget.
There were some occasion with single line diff pr, to fix compilation, with more than > 1 week before merge.
That's very annoying for contributors
But that doesnt mean we should lower the bar for quality, the opposite, more review and smaller commit.
I am happy ms maintains this repo, but it should be easier to contribute. It's a lot easier with roslyn or dotnetcli ( my experience at least ).
the real issue i see a lot of time is wasted on merge, instead of make easier to contribute to this repo.
The community can help a lot, not all features are coreclr/top priority, but everyone want to improve different areas, that's the real :+1: ihmo, if guided/reviews by msteam and @dsyme . Make it easier to do it

We can always leverage the power of git cherry-pick -x ... to pull in specific commits for a stable branch, too.

I have ... heard comments indicating that future contributions were going to be forfeited

That is simply incorrect, so you can ignore it.

@dsyme I meant the potential contributors were going to stop submitting or working on contributions. Apologies for the unclear wording.

@panesofglass OK, thanks.  I think the best way to help is to do more code review, and to help keep PRs up-to-date.  Also bring over your previous submissions from CodePlex.

It's not clear that I can help you out with this.  The bulk of the commits are Don's.and so he is the most inconvenienced by this, and it doesn't seem to have slowed him down any.  There are a couple from Enrico, which are in the nice to have rather than commited feature, etc.
What feature are you working on @panesofglass that requires one or more of these PR's and which PR does your feature need?
Kevin

One thing that makes it difficult for me is I work on OSX, to to make prime commits that will be accepted and I have to PR here. But ... I have to work in fsharp/fsharp to use and test my patch, cherry pick to FCS to test tool integration, then port to visualfsharp to make the PR so that the whole lot can be back merged into FCS and fsharp/fsharp so that it can be publicly consumed.  That's quite painful!!

On 19 Jan 2016, at 23:31, Kevin Ransom (msft<EMAIL_ADDRESS>wrote:
It's not clear that I can help you out with this. The bulk of the commits are Don's.and so he is the most inconvenienced by this, and it doesn't seem to have slowed him down any. There are a couple from Enrico, which are in the nice to have rather than commited feature, etc.
What feature are you working on @panesofglass that requires one or more of these PR's and which PR does your feature need?
Kevin
—
Reply to this email directly or view it on GitHub.

@7sharp9 being able to develop on OSX and Linux is definitely a goal, and we are tiptoing towards that.  However right now it is not yet doable.  But it will eventually.

@KevinRansom, I'm not working on anything related to this repo currently. I had hoped to help out with some things previously but was unable to build any branch for quite some time. Only today did I discover that master builds on my VM.
I'm not sure of the state of the web templates PRs. I assume they are out-of-date (targeting VS2013) and lost somewhere on CodePlex.

@panesofglass Your PR to codeplex is here. Please bring it across, rebase, and submit to github. https://visualfsharp.codeplex.com/SourceControl/network/forks/riles01/webtemplates/contribution/7650

@7sharp9 being able to develop on OSX and Linux is definitely a goal, and we are tiptoing towards that. However right now it is not yet doable. But it will eventually.

How? can we create an issue with problems and roadmap about osx/linux? I am pretty sure exists already.
Can we help?
For example, my next pr can be:

import build script from fsharp/fsharp? use an add appveyor-build.sh, like .cmd but bash (like dotnet/cli does, duplicated script)
make fsprojs and solution work with monodevelop?
add travisci build meanwhile jenkinsosx doesnt work?

just ask, make a possible roadmap and ask community to help

Just being able to build visualfsharp from osx would be a great start.

Just being able to build visualfsharp from osx would be a great start

:+1: about that, with a simple travisci. @7sharp9 can you open an issue?

I've been through the PRs and only 6 remain that are not Work In Progress (WIP) https://github.com/Microsoft/visualfsharp/pulls.   I'll close this since things are in fairly good state.

Thanks for your work on this, @dsyme.

The vast majority of the work was done by @KevinRansom. Please take the time to give feedback to Microsoft management as requested in #877 :)

Thank you for your work here, @KevinRansom!


Using multiple Swagger JSON

What would be the strategy to consume 2 or more Swagger JSON and serving them on same/different port, since graphQLSchema function does not take an array of proxyUrls/SwaggerPaths.
Is it even possible?
I tried with two ports which works fine but not sure if it's the recommended way:
graphQLSchema('./swagger1.json', proxyUrl, customHeaders).then(schema => {
  app.use('/graphql', graphqlHTTP(() => {
    return {
      schema,
      graphiql: true
    };
  }));
}).catch(e => {
  console.log(e);
});

graphQLSchema('./swagger2.json', proxyUrl, customHeaders).then(schema => {
  app.use('/graphql2', graphqlHTTP(() => {
    return {
      schema,
      graphiql: true
    };
  }));
}).catch(e => {
  console.log(e);
});

app.listen(4000, 'localhost', () => {
  console.info('http://localhost:4000/graphql or http://localhost:4000/graphql2');
});

That would be challenging, since schemas can overlap.
I would probably recommend convert each of the schemas separately and then use the schema stitching GraphQL tool or Federation from Apollo

I think the schema stitching is what I'm doing right now which can be used in Angular this way: https://www.apollographql.com/docs/angular/features/multiple-clients/
Can federation be used along with swagger-to-graphql? If yes, any example code?

I am just curious whether this tool is to be used in order to generate Types for GraphQL from Swagger JSON (where you have to write resolvers by hand) or directly swallow the Swagger JSON with express-graphql?

Also feeding the service to gateway throws Error: Apollo Server requires either an existing schema or typeDefs. Any idea why?
  serviceList: [
    { name: 'pet', url: 'http://localhost:4001' }
  ],
});
const server = new ApolloServer({
  gateway,

  // Currently, subscriptions are enabled by default with Apollo Server, however,
  // subscriptions are not compatible with the gateway.  We hope to resolve this
  // limitation in future versions of Apollo Server.  Please reach out to us on
  // https://spectrum.chat/apollo/apollo-server if this is critical to your adoption!
  subscriptions: false,
});

server.listen().then(({ url }) => {
  console.log(`🚀 Server ready at ${url}`);
});```

I managed to make it work since the documentation was not updated. However, I had to write custom resolvers and use generated Graphql schemas by this tool since Federation is not compatible with it.
const { ApolloGateway } = require("@apollo/gateway");

const gateway = new ApolloGateway({
  serviceList: [
    { name: "pets", url: "http://localhost:5001/graphql" },
    { name: "automation", url: "http://localhost:5002/graphql" },
  ]
});

(async () => {
  const { schema, executor } = await gateway.load();

  const server = new ApolloServer({ schema, executor });

  server.listen({port: 5000}).then(({ url }) => {
    console.log(`🚀 Server ready at ${url}`);
  });
})();```


BUILD: Docker cleanup.

Add ENTRYPOINT so image is useful by default
Simplify Dockerfile
Document ports via EXPOSE
Add basic .dockerignore

The only functional difference is that you do not need to give it a command to be useful, making the following work:
docker run avaplatform/gecko will start the Gecko node with no flags.
docker run avaplatform/gecko -log-level=verbo -api-ipcs-enabled=true will start the Gecko node with the given flags.
Note: I did not touch scripts/build_image.sh or the scripts/Docker.deploy that it uses. I'm not sure exactly what these are for but afaict they're obsoleted by the removal of Salticidae and the addition of go modules.

I'm not sure why this test is failing; I'll have to debug it.

This is very out of date. Closing and making a new PR off a more up to date parent.


Members enhanced

Moving the member search map out of this epic since it won't be completed in this round and — as we now know — needs to be an epic of its own. Closing since all other members enhanced features were completed in the 1.0 release.


boards: arm: Fix for STM32373C-EVAL

This board has an ST-LINK/V2, but OpenOCD config for it seems incorrect,
nor it has an DFU bootloader like newer NUCLEO boards (maybe copy/paste
error in original implementation?)
Fixes #4295
Signed-off-by: Jose F. Fernandez<EMAIL_ADDRESS>

@jffernandez: If ok with you, I propose to close this PR and proposes a solution with board revision as a Kconfig option (or dts). If not possible for now, you can raise a github issue and request this as an improvment

@erwango: Of course, no problem! I use our repo for everyday work, so having it there is enough for me, just contributed in case it can help others that can have the same issue.
Thank you!


Delserver arguments

I'd like to be able to delete a server from the list by ID.
Example  delserver 1 would delete the first entry.
I use one znc to join random networks to assist users all the time, sometimes i add ip's or long url's and it is always just one server added and i delete it shortly after. It would be really nice to be able to just delserver 1 and go on, otherwise i'll have to listservers and copy it and then delete it.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

This continues to be a feature request of interest.  From #znc-dev on libera.chat:
<Wollino> DarthGandalf hi :) I have a request for you. could you implement within the addserver command the possibility of automatically adding a sequential identification number of the server just added to be able to then delete it later in a simple and quick way in bulk if it is deemed necessary?
<Wollino> How can you do it with services to eliminate channel access lists. for example "delserver 1-9" or "delsever 1,3,7,9" or "delserver *" to empty the whole list.
<KindOne> Open an issue on github about it?
<MetaNova> ^
<MetaNova> not a bad suggestion
<Wollino> MetaNova: can you make it to me please?
<MetaNova> you don't have a github account?
<Wollino> in this time I no have access
<MetaNova> looks like it's already an issue
<MetaNova> https://github.com/znc/znc/issues/335
<ZNC-Linker> https://github.com/znc/znc/issues/335 “Delserver arguments” (open)
<MetaNova> I'll bump it

Specifically, as desired:
delserver 1-9 deletes server IDs 1 through 9
delserver 1,3,7,9 deletes server IDs 1, 3, 7, 9
delserver * deletes all server IDs for the attached network


Contributing actions API

Signed-off-by: Liam Barry Allan<EMAIL_ADDRESS>Changes
Allow other extensions to register actions. Needs testing.
Closes #755.
Test list

[ ] Local actions continue to work (validator changed)
[ ] Command to add actions

Checklist

[ ] have tested my change
[x] updated relevant documentation
[x] Remove any/all console.logs I added
[x] eslint is not complaining
[ ] have added myself to the contributors' list in CONTRIBUTING.md
[x] for feature PRs: PR only includes one feature enhancement.

Speaking of actions, I noticed the other day that when you define a user action it copies the entire default set into the user config, rather than just adding the user defined one.
Is it worth amending that behaviour so the user actions add to the defaults (just in case new default ones are added)?

@priceaj There was a reason we update the global config. It was to do with when the user changes a default and how the config stores it. I personally think actions need an overhaul to be connection specific too.
Lots of room for improvement here.


Wrong predicted density/depth

Hi author, thanks for sharing this great work! I am training with a Chinese person video
https://github.com/yerfor/GeneFacePlusPlus/assets/9716015/7156e937-cdf8-4826-bcbb-5960c8ee2430
. And I found that after only 20k steps of training head_nerf, the predicted depth/density of nerf becomes wrong. As shown here
. This has a bad influence on the final rendering quality of the background, in which the bg is weird dynamic
https://github.com/yerfor/GeneFacePlusPlus/assets/9716015/1e0c7be3-dd62-41de-88ed-00f828617da0
. Could you help provide some comments on how to resolve this issue? Many thanks.
.

Found the issue: we should use 'com_imgs' instead of 'gt_imgs' as the GT for training. Closed.

Hi, thanks for pointing out this, I have update the binarizer, it now points gt_img_name to the com_imgs.

Looks like updating the binarizer breaks torso training – no predicted depth on torso. Working around this by binarizing again before torso training, but FYI

Looks like this is causing torso training to fail, as the torso background is now the same for everything. Easily fixed by rerunning the binarizer with gt_imgs for training, but heads up

what's the difference between com_imgs and gt_imgs @yerfor


Multiple Roles on Organization Member

Is this suited for github?

[X] Yes, this is suited for github

Is your feature request related to a problem? Please describe.
For my use-case, I need organization support, which I have in Auth0 and now also in Better Auth, very happy about that. But for members of these organizations, I need to have roles. This is possible, but unfortunately limited in an important sense. In Auth0 I can have multiple roles per member, say this person is the "project manager but also the accountant" (just an example). This is not possible right now with the organization plugin, where one member can only have a singular role. I'm using this extensively, and would require it in order to fully move to Better Auth.
Describe the solution you'd like
I'd like the option of having multiple roles per member in organizations.
Describe alternatives you've considered
Customizing the member in the betterAuth() call, unfortunately it's not supported in the same way as user is ("additionalFields").
Customizing the member schema directly, as recommended in discord. But this is unfortunately not a perfect solution since it seems like this would become quite problematic since that custom property won't be included in the BetterAuth built-in calls. Doing this seems like a ticking timebomb since I'm not a solo-developer on this project.
Considered a kind of merge in the role name, like having it more like "owner:member:etc" but this won't scale and I've got quite a lot of roles, where I'd need all possible combinations... Not feasible.
Additional context
No response

Since it's not relevant to the feature request, I wanted to add here instead: thank you for this framework. It's a joy to work with and it smells of quality.


Parallel For in the Recursive Blueprints

Benchmark to see if Parallel For is quicker in the benchmarks. There could be thread safety issues to worry about here.

Wasn't worth it.


RECON: Add Stacks Support

Determine steps needed to add Stacks support.

repo's moving!
https://github.com/omnisat/lasereyes-mono


Menu perf simulations

A few changes in this PR.
To test it run it against stacks-java which has an out the box working backend connecting to a cosmos db in the cloud.
Please refer to the readMe because running the tests has slightly changed.

here is the comment


Update class diagrams in DG and rename some classes

Fixes https://github.com/AY2223S1-CS2103T-F12-3/tp/issues/210, fixes https://github.com/AY2223S1-CS2103T-F12-3/tp/issues/67

Codecov Report

Merging #218 (471a90a) into master (0b9da51) will not change coverage.
The diff coverage is 78.57%.

@@            Coverage Diff            @@
##             master     #218   +/-   ##
=========================================
  Coverage     68.54%   68.54%
  Complexity      607      607
=========================================
  Files           101      101
  Lines          1879     1879
  Branches        194      194
=========================================
  Hits           1288     1288
  Misses          527      527
  Partials         64       64

Impacted Files
Coverage Δ

src/main/java/seedu/address/MainApp.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/model/Model.java
100.00% <ø> (ø)

.../java/seedu/address/model/util/SampleDataUtil.java
15.00% <0.00%> (ø)

.../seedu/address/storage/JsonAddressBookStorage.java
100.00% <ø> (ø)

...u/address/storage/JsonArchivedTaskListStorage.java
100.00% <ø> (ø)

...ain/java/seedu/address/storage/StorageManager.java
96.29% <ø> (ø)

src/main/java/seedu/address/ui/TaskCard.java
0.00% <ø> (ø)

...rc/main/java/seedu/address/model/ModelManager.java
92.59% <83.33%> (ø)

...rc/main/java/seedu/address/logic/LogicManager.java
68.00% <100.00%> (ø)

...ava/seedu/address/logic/commands/ClearCommand.java
100.00% <100.00%> (ø)

... and 6 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Adding HTTPS link for Beeceptor

Proposing to add HTTPS link for Beeceptor under Webhooks documentation.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hello @ankitjaininfo,Thanks again for the PR! We want to show our appreciation by sending                                              you some swag. Could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


Bazel auto-configured xcode_version is flaky: ERROR: /private/var/tmp/_bazel_runner/c2342bca25695567c8c3f3be166b56b3/external/local_config_cc/BUILD:87:24: in cc_toolchain_config rule @local_config_cc//:darwin_x86_64:

This issue is plaguing the CI and also local developers.  It calls xcode-select -s each time ( although doesn't have a developer directory ).
ERROR: /private/var/tmp/_bazel_runner/c2342bca25695567c8c3f3be166b56b3/external/local_config_cc/BUILD:87:24: in cc_toolchain_config rule @local_config_cc//:darwin_x86_64:
75
Traceback (most recent call last):
76
	File "/private/var/tmp/_bazel_runner/c2342bca25695567c8c3f3be166b56b3/external/local_config_cc/cc_toolchain_config.bzl", line 495, column 61, in _impl
77
		flags = _deterministic_libtool_flags(ctx) + [
78
	File "/private/var/tmp/_bazel_runner/c2342bca25695567c8c3f3be166b56b3/external/local_config_cc/cc_toolchain_config.bzl", line 53, column 38, in _deterministic_libtool_flags
79
		if _can_use_deterministic_libtool(ctx):
80
	File "/private/var/tmp/_bazel_runner/c2342bca25695567c8c3f3be166b56b3/external/local_config_cc/cc_toolchain_config.bzl", line 45, column 25, in _can_use_deterministic_libtool
81
		if _compare_versions(xcode_version, _SUPPORTS_DETERMINISTIC_MODE) >= 0:
82
	File "/private/var/tmp/_bazel_runner/c2342bca25695567c8c3f3be166b56b3/external/local_config_cc/cc_toolchain_config.bzl", line 38, column 15, in _compare_versions
83
		return dv1.compare_to(apple_common.dotted_version(v2))

Here's a related Bazel issue: https://github.com/bazelbuild/bazel/issues/13509

Details in here on current status https://github.com/bazel-ios/rules_ios/pull/362 and upstream fix


A solution to reference image in CSS

With CSS file, you could reference images using relative path, it will use the relative path to the CSS file location.
With in JS file, this is not the case. If you reference an image using relative path, the path will be relative to displayed page which won't work with image files.
Will there be a solution to resolve this?

This isn't Radium-specific, but you have a few options:

Use absolute paths (I would recommend this in general)
Use a build system that will handle your image paths for you, like Webpack (this would convert them to absolute paths under the hood, anyway)

I think this topic deserves attention in the docs (at least in the FAQs). Most, if not all, build systems are made to handle static assets through CSS files. Trying to figure out how to do this when there are no .css files isn't a trivial task for a beginner. A few pointers in the right direction might be a great start.

Fair enough. Have you figured out anything so far that would be useful to add?


Bring latest live changes back into main

Deploy latest ZoomIt corrections

Docs Build status updates of commit a0be4b7:
:warning: Validation status: warnings
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Adding support for 'scp' claim in addition to 'scope' claim for scopes

Some IDPs like Okta and Microsoft call scopes claim "scp" instead of "scope". Adding this enhancement to look for "scp" claim for scopes if "scope" claim is missing.

@jaswalkiranavtar Thanks a lot for your help.

 Adding support for 'scp' claim in addition to 'scope' claim for scopes light-rest-4j master


[Bug] Class org.apache.hadoop.fs.s3a.S3AFileSystem not found

Describe the bug
I am trying to use minio as a s3 storage with the following configs:
        "hadoop.fs.s3a.aws.credentials.provider": "com.amazonaws.auth.DefaultAWSCredentialsProviderChain",
        "hadoop.fs.s3a.access.key" : "admin",
        "hadoop.fs.s3a.secret.key" : "password",
        "hadoop.fs.s3a.endpoint" :  "http://minio:9000",

But when trying to run the connector it fail with Class org.apache.hadoop.fs.s3a.S3AFileSystem not found
To Reproduce
Steps to reproduce the behavior:

Install the connector the following configurations:

        "hadoop.fs.s3a.aws.credentials.provider": "com.amazonaws.auth.DefaultAWSCredentialsProviderChain",
        "hadoop.fs.s3a.access.key" : "admin",
        "hadoop.fs.s3a.secret.key" : "password",
        "hadoop.fs.s3a.endpoint" :  "http://minio:9000",

Expected behavior
The connector should be loaded correctly
Screenshots
N/A

Never mind, I should be using the cloud version.


Pipenv REQUIRES 3.7 and refuses to run on 3.8

Issue description
pipenv install fails when the only versions of python I have are 2.7 or 3.8.x
Expected result
That pipenv supports python 3.8+
Actual result
Warning: Python 3.7 was not found on your system…
You can specify specific versions of Python with:
  $ pipenv --python path/to/python
:~/$ python --version
Python 3.8.5

This wouldn't be so problematic if it weren't so difficult to specifically instal python 3.7 these days.

Can you describe better what you want to accomplish?
Do you have an existing Pipfile and Pipfile.lock (e.g. from cloning a repository from colleges), or do you execute the command in a fresh empty directory?

If you start with a fresh directory, have you tried the suggestion that you got with the warning?
pipenv --python path/to/python

If you already have a Pipfile / Pipfile.lock, I could imagine that you have the line
[requires]
python_version = "3.7"

in the Pipfile, and corresponding locks in the Pipfile.lock.
You can still use a different version, with the same command pipenv --python path/to/python, or by changing the line in the Pipfile.
However be warned, it is probably not a good idea as dependencies for 3.7 and 3.8 might differ.
If you want to collaborate on this project with colleges, you should all use the same version.

And btw, how difficult is it to install different Python versions today? It's simpler than ever before. Just install them with pyenv.
# installation
pyenv install 3.7.9
# activate it in this directory
# (optional, pipenv should find 3.7 automatically if installed with pyenv)
pyenv local 3.7.9

Can you describe better what you want to accomplish?
Do you have an existing Pipfile and Pipfile.lock (e.g. from cloning a repository from colleges), or do you execute the command in a fresh empty directory?

If you start with a fresh directory, have you tried the suggestion that you got with the warning?
pipenv --python path/to/python

If you already have a Pipfile / Pipfile.lock, I could imagine that you have the line
[requires]
python_version = "3.7"

in the Pipfile, and corresponding locks in the Pipfile.lock.
You can still use a different version, with the same command pipenv --python path/to/python, or by changing the line in the Pipfile.
However be warned, it is probably not a good idea as dependencies for 3.7 and 3.8 might differ.
If you want to collaborate on this project with colleges, you should all use the same version.

And btw, how difficult is it to install different Python versions today? It's simpler than ever before. Just install them with pyenv.
# installation
pyenv install 3.7.9
# activate it in this directory
# (optional, pipenv should find 3.7 automatically if installed with pyenv)
pyenv local 3.7.9

Firstly, pipenv has been so so useful for me so I want to underscore how
amazing it’s been handling multiple projects. Truly fantastic. Thank you to
all involved!
Can you help me understand why pipenv doesn’t run with recent / default
versions of python out of the box? If I have time I shall try to test it
against 3.8 & 3.9.
The suggestions about installing through pyenv doesn’t make much sense to
me personally: pyenv isn’t included in any distros I’m aware of but maybe
it’s more common than my own limited experience.
At the very least if pipenv is firmly not to support 3.8, 3.9. or future
versions, it’d be great if when it failed that it provided clear
instructions on how to get it going. What do you think? It could be simply
“please install pyenv so you can then install python 3.7…? Though maybe the
install process could be simpler.
On Sun, 17 Jan 2021 at 21:36, Jakob Kogler<EMAIL_ADDRESS>wrote:

Can you describe better what you want to accomplish?
Do you have an existing Pipfile and Pipfile.lock (e.g. from cloning a
repository from colleges), or do you execute the command in a fresh empty
directory?
If you start with a fresh directory, have you tried the suggestion that
you got with the warning?
pipenv --python path/to/python

If you already have a Pipfile / Pipfile.lock, I could imagine that you
have the line
[requires]
python_version = "3.7"
in the Pipfile, and corresponding locks in the Pipfile.lock.
You can still use a different version, with the same command pipenv
--python path/to/python, or by changing the line in the Pipfile.
However be warned, it is probably not a good idea as dependencies for 3.7
and 3.8 might differ.
If you want to collaborate on this project with colleges, you should all
use the same version.
And btw, how difficult is it to install different Python versions today?
It's simpler than ever before. Just install them with pyenv.
installation
pyenv install 3.7.9# activate it in this directory# (optional, pipenv should find 3.7 automatically if installed with pyenv)
pyenv local 3.7.9
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pypa/pipenv/issues/4590#issuecomment-761884229, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABD62JT6F4OOTCUUUXCXKLS2NJ5LANCNFSM4WGFTD4Q
.

Firstly, pipenv has been so so useful for me so I want to underscore how
amazing it’s been handling multiple projects. Truly fantastic. Thank you to
all involved!
Can you help me understand why pipenv doesn’t run with recent / default
versions of python out of the box? If I have time I shall try to test it
against 3.8 & 3.9.
The suggestions about installing through pyenv doesn’t make much sense to
me personally: pyenv isn’t included in any distros I’m aware of but maybe
it’s more common than my own limited experience.
At the very least if pipenv is firmly not to support 3.8, 3.9. or future
versions, it’d be great if when it failed that it provided clear
instructions on how to get it going. What do you think? It could be simply
“please install pyenv so you can then install python 3.7…? Though maybe the
install process could be simpler.
On Sun, 17 Jan 2021 at 21:36, Jakob Kogler<EMAIL_ADDRESS>wrote:

Can you describe better what you want to accomplish?
Do you have an existing Pipfile and Pipfile.lock (e.g. from cloning a
repository from colleges), or do you execute the command in a fresh empty
directory?
If you start with a fresh directory, have you tried the suggestion that
you got with the warning?
pipenv --python path/to/python

If you already have a Pipfile / Pipfile.lock, I could imagine that you
have the line
[requires]
python_version = "3.7"
in the Pipfile, and corresponding locks in the Pipfile.lock.
You can still use a different version, with the same command pipenv
--python path/to/python, or by changing the line in the Pipfile.
However be warned, it is probably not a good idea as dependencies for 3.7
and 3.8 might differ.
If you want to collaborate on this project with colleges, you should all
use the same version.
And btw, how difficult is it to install different Python versions today?
It's simpler than ever before. Just install them with pyenv.
installation
pyenv install 3.7.9# activate it in this directory# (optional, pipenv should find 3.7 automatically if installed with pyenv)
pyenv local 3.7.9
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pypa/pipenv/issues/4590#issuecomment-761884229, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABD62JT6F4OOTCUUUXCXKLS2NJ5LANCNFSM4WGFTD4Q
.

pipenv does support 3.8 and later.
Maybe try answering the questions that I asked and give a more detailed problem description.
And post the output of pipenv --support, and the Pipfile (if you have any).

pyenv is included in my distro :grinning: . But even if it's not, you should be able to install it it within one or two minutes. It's just one git clone, and adding a couple of lines to the .bashrc. And there's even an automatic installer.

pipenv does support 3.8 and later.
Maybe try answering the questions that I asked and give a more detailed problem description.
And post the output of pipenv --support, and the Pipfile (if you have any).

pyenv is included in my distro :grinning: . But even if it's not, you should be able to install it it within one or two minutes. It's just one git clone, and adding a couple of lines to the .bashrc. And there's even an automatic installer.

I tried running it with /usr/bin/python pointing at 3.8 but it would not
run. Only when I installed 3.7 did it work.
On Sun, 17 Jan 2021 at 22:02, Jakob Kogler<EMAIL_ADDRESS>wrote:

pipenv does support 3.8 and later.
Maybe try answering the questions that I asked and give a more detailed
problem description.
And post the output of pipenv --support, and the Pipfile (if you have
any).
pyenv is included in my distro 😀 . But even if it's not, you should be
able to install it it within one or two minutes. It's just one git clone,
and adding a couple of lines to the .bashrc. And there's even an
automatic installer.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pypa/pipenv/issues/4590#issuecomment-761888045, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABD62MDBKNLSXR4BO6UM5LS2NNBDANCNFSM4WGFTD4Q
.

I tried running it with /usr/bin/python pointing at 3.8 but it would not
run. Only when I installed 3.7 did it work.
On Sun, 17 Jan 2021 at 22:02, Jakob Kogler<EMAIL_ADDRESS>wrote:

pipenv does support 3.8 and later.
Maybe try answering the questions that I asked and give a more detailed
problem description.
And post the output of pipenv --support, and the Pipfile (if you have
any).
pyenv is included in my distro 😀 . But even if it's not, you should be
able to install it it within one or two minutes. It's just one git clone,
and adding a couple of lines to the .bashrc. And there's even an
automatic installer.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pypa/pipenv/issues/4590#issuecomment-761888045, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABD62MDBKNLSXR4BO6UM5LS2NNBDANCNFSM4WGFTD4Q
.

@boxabirds That is because you have the line in your Pipfiile:
[requires]
python_version = "3.7"

@boxabirds That is because you have the line in your Pipfiile:
[requires]
python_version = "3.7"

Pipenv's Python version detection is weird af. When I use 3.8 then it tells me that it does use 3.8 while creating virtualenv and then puts 3.9 in the Pipfile. But when I use 3.9, it tells me that it uses 3.9 but puts 3.8 in Pipfile. The only way to make do what you want is to set it explicitly as argument to first run command.

Pipenv's Python version detection is weird af. When I use 3.8 then it tells me that it does use 3.8 while creating virtualenv and then puts 3.9 in the Pipfile. But when I use 3.9, it tells me that it uses 3.9 but puts 3.8 in Pipfile. The only way to make do what you want is to set it explicitly as argument to first run command.

This is an older issue and we know that pipenv definitely runs fine on newer versions of Python, so I am closing this down.


Update the <IP_ADDRESS> download link for hub sync

After it's merged, I'll cherry-pick it to branch-2.8.0

@Jennifer88huang PTAL again


Email registration links open and then immediately close.

Here's two cases I've found on zulipchat.com:

Create a new Zulip organization via https://zulipchat.com/new by providing an email address. Receive the email with the subject line 'Activate your Zulip account', and click on the 'Complete registration' button. On my browser (Chrome), a new tab opens and then immediately closes before any contents load.
On a realm already created via zulipchat.com, invite a new user. The registration link in the invitation email has the same behavior - a new tab opens and then immediately closes.

@zulipbot label "area: emails"

@zulipbot add "area: emails"

@jackrzhang what precise browser are you using?  I cannot reproduce, but this sounds quite serious so we should figure out what's happening/

I'm using Chrome, Version 70.0.3538.77 (Official Build) (64-bit).

I just tried Safari 12.0 (13606.2.11) - the invitation link works on that browser.

Other facts that might be relevant are that I cleared all of my browsing data around 3 weeks ago when I upgraded Chrome, and that I created both realms on the same browser prior to the upgrade.

Hm, this still reproduces within an incognito window, though, so perhaps it's something else.

Here's a screenshot:

Fascinating, this doesn't reproduce anymore... 😕
@timabbott Should the high priority tag be removed for now?

Probably we should close it as not reproducible; it's probably a browser bug that they fixed via a browser update.


Fix typo in RegexRegisteredService

Just a small typo.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Google play warning about auth data

Google play developer console has waring about private auth data in my app.
"com.getsentry.raven.dsn.Dsn: noop://user:password@localhost"
Could you please provide more friendly class member?
public static final String DEFAULT_DSN = "noop://user:password@localhost:0/0";
Thanks.

@olegsm Can you post the warning? I'm not sure how I need to change it in order to not trigger the warning.

@bretthoerner I saw it before, Google refers to their doc for more info.
To sum up, basically they search for the URL pattern for Basic Auth, not exactly words, but the URL pattern itself.

Thanks @Hazer, I'll fix.


[FEATURE] Add script_score to query DSL

Is your feature request related to a problem?
Script Score query was added to OpenSearch 2.9 and current query DSL does not support it.
I use script score a lot in my case, so I would want to add it in current query DSL.
What solution would you like?
Add script_score to query DSL
Do you have any additional context?
OpenSearch document on script_score: https://opensearch.org/docs/latest/query-dsl/specialized/script-score/

Related, we've been working on https://github.com/opensearch-project/opensearch-api-specification. For this client we need help for someone to pickup https://github.com/opensearch-project/opensearch-ruby/issues/233 and other generator-related work.
@quangcap Now that you're very familiar with this API, would you be able to contribute it to the spec as well? https://github.com/opensearch-project/opensearch-api-specification

Clkosed via https://github.com/opensearch-project/opensearch-ruby/pull/254.

@dblock Sorry for the late reply!
About #233: I tried out the ApiGenerator, and it throws a lot of errors, probably because the current parser doesn’t support OAS 3.1 yet. I’ve seen some work being done on the parser (https://github.com/kevindew/openapi3_parser/pull/22), but I don’t think it’ll be ready anytime soon.
As for adding script_score to the spec: Absolutely, I’d love to help out!

FWIW, I've been able to load the spec with the current openapi3_parser:
require 'open-uri'
require 'openapi3_parser'

openapi_url = "https://github.com/opensearch-project/opensearch-api-specification/releases/download/main-latest/opensearch-openapi.yaml"
openapi_path = "opensearch-openapi.yaml"
File.write(openapi_path, URI.open(openapi_url).read) unless File.exists?(openapi_path)
puts "Loading #{openapi_path} (#{File.size(openapi_path)} byte(s)) ..."

doc = Openapi3Parser.load_file(openapi_path)
puts "Loaded #{openapi_url} with #{doc.paths.size} path(s)."

doc.paths.keys.each do |key|
   puts key
end

I've been able to load it with the current openapi3_parser. However, running .valid? and .errors, I can print out a lot of errors.
...
doc = Openapi3Parser.load_file(openapi_path)
puts "Loaded #{openapi_url} with #{doc.paths.size} path(s)."
puts "Spec is valid: " + doc.valid?.to_s

puts "Errors:"
doc.errors.each do |err|
  puts err
end

which prints:
Spec is valid: false
Errors:
#/components/parameters/_global%3A%3Aquery.pretty does not resolve to a valid object
#/components/parameters/_global%3A%3Aquery.human does not resolve to a valid object
#/components/parameters/_global%3A%3Aquery.error_trace does not resolve to a valid object
#/components/parameters/_global%3A%3Aquery.pretty does not resolve to a valid object
#/components/parameters/_global%3A%3Aquery.human does not resolve to a valid object
#/components/parameters/_global%3A%3Aquery.error_trace does not resolve to a valid object
#/components/parameters/_global%3A%3Aquery.pretty does not resolve to a valid object
#/components/parameters/_global%3A%3Aquery.human does not resolve to a valid object
#/components/parameters/_global%3A%3Aquery.error_trace does not resolve to a valid object
...

@quangcap Do you know whether those are legit errors? If they are, please do open an issue in https://github.com/opensearch-project/opensearch-api-specification.


IE11 throws exception on iD load. Object doesn't support property or method 'find'

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/find#Browser_compatibility

Thanks!   We realized that we're using a not-standard find in the code that picks the best imagery.  I didn't catch this before because it was on a separate branch from the IE work.. Will release a fix today.


DQNAgent: AttributeError: 'Beta' object has no attribute 'state_action_value'

Trying to use DQNAgent in #dev results in the following error. Culprit being tf_q_value, comment indicates the line's specialized for NAF, maybe causes problems with vanilla Q?
(btc3) lefnire@lefnire-ubuntu:~/Sites/btc$ python tforce/single.py
[2017-10-18 11:54:26,451] Making new env: BTC-v0
2017-10-18 11:54:26.530395: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:892] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2017-10-18 11:54:26.530617: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1030] Found device 0 with properties:
name: GeForce GTX 1080 Ti major: 6 minor: 1 memoryClockRate(GHz): 1.582
pciBusID: 0000:01:00.0
totalMemory: 10.90GiB freeMemory: 3.65GiB
2017-10-18 11:54:26.530626: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1120] Creating TensorFlow device (/device:GPU:0) -> (device: 0, name: GeForce GTX 1080 Ti, pci bus id: 0000:01:00.0, compute capability: 6.1)
Traceback (most recent call last):
  File "tforce/single.py", line 15, in <module>
    env_args=dict(is_main=True)
  File "/home/lefnire/Sites/btc/agent_conf.py", line 385, in conf
    config=conf
  File "/home/lefnire/Sites/btc/tmp/tensorforce2/tensorforce/agents/dqn_agent.py", line 159, in __init__
    super(DQNAgent, self).__init__(states_spec, actions_spec, config)
  File "/home/lefnire/Sites/btc/tmp/tensorforce2/tensorforce/agents/memory_agent.py", line 51, in __init__
    super(MemoryAgent, self).__init__(states_spec, actions_spec, config)
  File "/home/lefnire/Sites/btc/tmp/tensorforce2/tensorforce/agents/agent.py", line 177, in __init__
    config=config
  File "/home/lefnire/Sites/btc/tmp/tensorforce2/tensorforce/agents/dqn_agent.py", line 166, in initialize_model
    config=config
  File "/home/lefnire/Sites/btc/tmp/tensorforce2/tensorforce/models/q_model.py", line 52, in __init__
    config=config
  File "/home/lefnire/Sites/btc/tmp/tensorforce2/tensorforce/models/distribution_model.py", line 98, in __init__
    config=config
  File "/home/lefnire/Sites/btc/tmp/tensorforce2/tensorforce/models/model.py", line 177, in __init__
    deterministic=self.deterministic
  File "/home/lefnire/Sites/btc/tmp/tensorforce2/tensorforce/models/model.py", line 550, in create_output_operations
    reward=reward
  File "/home/lefnire/anaconda3/envs/btc3/lib/python3.6/site-packages/tensorflow/python/ops/template.py", line 278, in __call__
    result = self._call_func(args, kwargs, check_for_new_variables=False)
  File "/home/lefnire/anaconda3/envs/btc3/lib/python3.6/site-packages/tensorflow/python/ops/template.py", line 217, in _call_func
    result = self._func(*args, **kwargs)
  File "/home/lefnire/Sites/btc/tmp/tensorforce2/tensorforce/models/q_model.py", line 91, in tf_loss_per_instance
    q_value = self.tf_q_value(embedding=embedding, distr_params=distr_params, action=actions[name][:-1], name=name)
  File "/home/lefnire/Sites/btc/tmp/tensorforce2/tensorforce/models/q_model.py", line 64, in tf_q_value
    return self.distributions[name].state_action_value(distr_params=distr_params, action=action)
AttributeError: 'Beta' object has no attribute 'state_action_value'

originally defined at:
  File "/home/lefnire/Sites/btc/tmp/tensorforce2/tensorforce/models/model.py", line 147, in __init__
    self.initialize(custom_getter=custom_getter)
  File "/home/lefnire/Sites/btc/tmp/tensorforce2/tensorforce/models/q_model.py", line 56, in initialize
    super(QModel, self).initialize(custom_getter)
  File "/home/lefnire/Sites/btc/tmp/tensorforce2/tensorforce/models/distribution_model.py", line 102, in initialize
    super(DistributionModel, self).initialize(custom_getter)
  File "/home/lefnire/Sites/btc/tmp/tensorforce2/tensorforce/models/model.py", line 319, in initialize
    custom_getter_=custom_getter

Something else at play here, likely on my end. Will re-open otherwise.

Hey @lefnire, this is actually a more experimental feature that is currently not supported for the Beta distribution (hence actions with min_value and/or max_value). we are planning to blog about it soon-ish, it's related to more recent papers about a kind of equivalence between policy gradient and q-models, but for now best consider DQN only working with discrete actions -- unbounded continuous also 'work', but not (yet) a proper feature.

Gotcha. Right, I had something wonky on my end - was trying to use DQN vanilla, didn't mean to mess with distributions

Not exactly false alarm, just straight into uncovering some 'potentially' new features... ;-)  as you've maybe seen, q_model also inherits from distribution_model, so in fact uses a distribution, which is something we've not seen before, but it nevertheless seems to make sense and is along the lines of quite a few papers recently. but this is a part we want to discuss at some point soon... anyway, DQN with discrete actions should work as expected, but feel free to play around with continuous DQN if you're curious (and in that case let us know what you think).


Lightweight fix for unexpected category behavior when multiple series…

… are used.
Fixes #1643

LGTM, thanks for the PR! I've merged it into the dev branch.


how can i make dataset and  Linked to deepdfa data?

hello?
I would like to try deepdfa.
stated in the paper
Using joern 1.1.1072
We created cpg, nodes, and edges.
However, its content is slightly different from what exists in the before.zip file.
=> Could you tell me the command you used in joern?
Together
If I create a before file, I am curious how I can abstract the preprocessing embedding and train it in deepdfa.
I'm so curious about the process, so I'm leaving a post here.

here is my try note.
https://agencies.tistory.com/238
https://agencies.tistory.com/244?category=1174818


Re-add C++ Unit Test to Android Studio Project

Closed by https://github.com/maplibre/maplibre-native/pull/2563


Unable to open vs code terminal

Issue Type: Bug
Hello, I'm getting this error of 'cmd.exe' does not exist whenever i try open vs code terminal. I have removed all the extenstions, deleted all the settings in settings.json file by putting empty { } but still it shows the same error.
VS Code version: Code 1.47.1 (485c41f9460bdb830c4da12c102daff275415b53, 2020-07-13T22:42:53.386Z)
OS version: Windows_NT x64 6.3.9600

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz (4 x 2394)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
3.92GB (0.92GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none

Deleting extension folder from vscode will solve this issue.


async support

It would be great if this had async support, for example:
gulp.src('*.js')
.pipe(map(function(content, filename, done){
  doSomethingAsync(content, function(err, result){
    done(result);
  });
}))
.pipe(gulp.dest('output'))

Agreed!

I eventually forked this project and added the async support it, here --> https://www.npmjs.com/package/vinyl-map2


rust: update toolchain to fix missing rls

What is changed and how it works?

Issue Number: Close #11953
What's Changed:
Update to rust nightly 2022-02-14 which is presented with rls, see https://rust-lang.github.io/rustup-components-history/

Check List
Tests

No code

Release note
None

Please fix the lint errors.

PTAL

PTAL @5kbpers

/merge

/test

/test

/test

I see test_read_index_retry_lock_checking fails because of failing to transfer leader. But I can always pass the test at my dev env...
Looks strange...

/test


add term tracker item

address #7027

At this point, it is not clear how we will proceed with these Mondo terms, therefore, I am holding on to this PR until we have an idea of how to proceed.

@sabrinatoro do you plan to revisit this or should we close it?


Running hermes

Description
Goal of this issue is to properly link Hermes for visionOS.
Resources:

https://gitlab.kitware.com/cmake/cmake/-/merge_requests/8581

Hermes is correctly building, #26


optimize Router::checkRoutes() : remove unneded uri check when routes is empty

Checklist:

[x] Securely signed commits

Now we really don't waste any time 👍


Improve support for multipart subscriptions

This should allow for SSE to be used in the future.

Handled in #3554


Include energy and hardware requirements to benchmarked metrics.

Hello The Yard! Thank you for this initiative and for sharing such a benchmarking infrastructure.
I'd like to take this opportunity to extend the notion of performance (as in "the thing we want to optimize in our pipeline") beyond the speed/memory/UX/quality: assessing the requirement of an engine in terms of energy expense and choice of hardware is getting increasingly important (you might be aware of eco-conditionality of CNC funding), yet there is (not?) suprisingly very few resource available on the topic when it comes to VFX digital infrastructure.
Your benchmark has the opportunity to become a pioneer in providing such information about environmental impacts, which will with no doubt become valuable in the near future. Happy to help about this, would you want to expand in that direction!

Hey, that's a cool idea! How would you go about measuring the energy consumption of the system running the benchmark?

If running on Linux, I'd recommend PowerAPI. If not, it is a bit of a pain (I am still actively working on figuring out a good measurement pipeline TBH), you can hack something up using vendor specific tools like Intel PCM, the nvidia-smi command (or underlying NVML library), AMD uProf, etc.

The USD Render Benchmark is, for now, expected to run on Linux only, so PowerAPI sounds like a great fit. I’d definitely welcome any contributions if you're familiar with PowerAPI and would like to extend the benchmark in this direction. Feel free to submit a pull request whenever you’re ready!


copr: add non-vectorized uuid

Signed-off-by: chacha923<EMAIL_ADDRESS>PCP #5751
What have you changed?
Add non-vectorized uuid
What is the type of the changes?

New feature (a change which adds functionality)

How is the PR tested?

Unit test

Does this PR affect documentation (docs) or should it be mentioned in the release notes?
no
Does this PR affect tidb-ansible?
no
Refer to a related PR or issue link (optional)
#3275

Signed-off-by: chacha923<EMAIL_ADDRESS>

/run-all-tests

/test

/merge


Add Getting Starting section to README

README Update
Please add a getting started section to the README so folks know how to start with this project.

Added Getting Started section in README file.


derive(Deserialize) generates a lot of code for a many-variant enum

One of the top functions in the output of cargo llvm-lines for Servo’s script crate (https://github.com/servo/servo/issues/26713) is this:
  Lines           Copies         Function name
  -----           ------         -------------
  6982790 (100%)  177169 (100%)  (TOTAL)
[…]
    47048 (0.7%)       4 (0.0%)  <keyboard_types::key::_IMPL_DESERIALIZE_FOR_Key::<impl serde::de::Deserialize for keyboard_types::key::Key>::deserialize::__Visitor as serde::de::Visitor>::visit_enum

That function code is generated by serde_derive for this enum: https://docs.rs/keyboard-types/0.5.0/keyboard_types/enum.Key.html
This enum has 286 variants so some code size is expected, but 47k lines still seems like a lot. Is there something we can do to reduce it?
The enum has one Character(String) variant, and all others variants are unit variants (without fields). This is only a random guess but would the generated code be simpler/smaller if the enum only had unit variants? (With the String case moved to a separate type)
CC @pyfisch, author of the keyboard-types crate

This doesn’t seem ideal in terms of run-time cost

This doesn’t seem ideal in terms of run-time cost

Which additional runtime cost do you foresee?
@dtolnay suggested a way for both deserialization and serialization to avoid allocating another string.
FromStr likely searches linearly for the matching string (I didn't check the asm) but this can be improved by applying binary search.

Probably the string comparisons and the impact on serialized size. Bincode would otherwise serialize only a small integer for the unit variants.

Right, that’s what I meant.
@dtolnay The offending function is a method of the Visitor trait, which (looking at the code generated by derive with --pretty=expanded) is passed to https://docs.rs/serde/1.0.111/serde/trait.Deserializer.html#tymethod.deserialize_enum which is documented as a "hint". Is it possible to give fewer hints to serde and have the serialization still based on integers? (Even if slightly less efficient)

I opened https://github.com/pyfisch/keyboard-types/pull/6 to cut the code size without affecting behavior.

The numbers in that PR look great, thanks!
I was wondering if the 47k lines from serde_derive were due to some quadratic behavior (which could potentially be improved), so I used Python to generate Rust code for 10 enum variants per line to easily comment out. I tried a few numbers of variants between 10 and 500, and the number of LLVM lines turned out perfectly linear.
print(''.join('    %s,\n' % ', '.join('V%s' % (i+j*10) for i in range(10)) for j in range(50)))

In a minimal bincode program based on the one in https://github.com/pyfisch/keyboard-types/pull/6 I also noticed that __Visitor::visit_enum has four copies/monomorphizations reported by cargo llvm-lines, where I would have expected one since we’re only using one (bincode) deserializer. Are multiple copies necessary?

I would also expect only one copy. It's worth looking in bincode for where those instantiations happen and hopefully fixing it.

It looks like bincode 1.3 fixed this and only generates one copy: https://github.com/servo/servo/pull/27063. Possibly in https://github.com/servo/bincode/pull/310, which I learned about via https://dos.cafe/blog/bincode-1.3.html.
visit_enum for Key still has the same size, but with one copy instead of four it goes from the 7th largest contributor of LLVM lines in Servo’s script crate to the 56th or so.
At this point I’m happy to close this issue. Maybe serde_derive could generate code closer to that in https://github.com/pyfisch/keyboard-types/pull/6 (is there a trade-off?) but to some extent being monomorphization-heavy and generating non-trivial code size is inherent to serde’s fundamental design, compared to something like miniserde.


Getting Error When Trying to Run Command "yarn install"

yarn install v1.22.15
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[###############################----------------------------------------------------------------------------] 731/2526node:_tls_wrap:411
        owner._tlsOptions.isServer ? 'server' : 'client', err,
                          ^

TypeError: Cannot read properties of undefined (reading 'isServer')
    at TLSWrap.onerror (node:_tls_wrap:411:27)

There isn't enough context here to understand the issue. That's what the bug report template you are asked to fill out when reporting a bug is for!
Please create a new issue and fill it out. Providing a link to a repo that has this issue will help, I'm happy to take a look at it.


Question: why would I be fired for using React.__SECRET_DOM_DO_NOT_USE_OR_YOU_WILL_BE_FIRED?

https://github.com/Lucifier129/react-lite/blob/master/dist/react-lite.common.js#L1395

While I appreciate the humor, I see two reasons to consider changing this:
First, it's inefficient.  It's a very long variable name that isn't replaced during minification, so it's technically wasting bandwidth.  Not much, of course, but when else in programming would you intentionally do something less efficient for no apparent gain?  __SECRET_DOM would be 72.7% smaller.  If there really is a problem with developers using it, __SECRET_DOM_DO_NOT_USE would be 47.7% smaller.  Even at a small scale, I couldn't pass up that kind of savings.
Second, if someone considering employment with a company views that company's source, sees that variable name, and thinks it's something the company added themselves... maybe not so great.

Hi, I am new in this app.

lol


Component doesn't render childs if it's set to 'use client'

Describe the issue you're facing
Hello,
I am having this problem currently.
Whenever I have a component which is in use client mode. It cannot render his childrens.
Here in the demo it will keep saying Component feature doesn't exist. as I defined Grid as a client component.
Any idea on how to solve this ?
Thanks for helping.
Reproduction
https://stackblitz.com/edit/github-h5bwfm?file=components%2FGrid.js
Steps to reproduce
No response
System Info
System:
    OS: macOS 13.5.1
    CPU: (12) arm64 Apple M2 Pro
    Memory: 2.00 GB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.17.1 - ~/.volta/tools/image/node/18.17.1/bin/node
    Yarn: 4.0.0-rc.50 - ~/.volta/tools/image/yarn/4.0.0-rc.50/bin/yarn
    npm: 9.6.7 - ~/.volta/tools/image/node/18.17.1/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Safari: 16.6

Used Package Manager
npm
Error logs (Optional)
Component feature doesn't exist.
Validations

[X] Follow our Code of Conduct

Hey @anthonyhexium !
The reason it doesn't work is because you have your Storyblok Initalization on the server side, and then you're using the component on the client side. In this case, if you're rendering grid - it is being rendered but since it is a client component the Storyblok Components map doesn't have anything as the it is on the server side.
An ideal fix would be to have a component map (for storyblok) on the client side, either by registering the library or by using a new function we recently implemented - setComponents.
A quick fix would be to have this in your Grid file -
  setComponents({     feature: Feature,   });
You need to import setComponents from the library itself, I see you're using an older version - you just need to update your library to the latest version to make it work.
cc - @fgiuliani

Thanks @arorachakit, I confirmed that your solution fixed our problem!

Good to know @b-derouet !
I will close the issue then :)


Populating initial data in the DB from the environment file

Right now, every time UpGrade starts, we take some initial values (users, exp point/IDs, group keys) from the environment file and populate the DB with those values (DB only gets users for now, but we will be storing point/ID, etc. when we deal with #62). If these initial entries in the DB are modified/deleted, the init values defined in the env file will get populated again in the DB when the server restarts. To get around this, maybe we can only populate env file values in the DB when the DB is blank, otherwise, ignore the init values in the env file.

@amurphy-cl no progress yet since there were other priorities.

@nirmalpatel Do you think we still need this or shall we close?

@danoswaltCL @nirmalpatel do we still need this change?


Changes impact on Eslint test cases from 2.0 to latest

Use content checksum instead of mtime and fsize, as @royriojas suggested, this should be optional.
Also the changes above use the fs.readFileSync to replace the fs.statSync

closed by https://github.com/royriojas/file-entry-cache/commit/b0f9ae05b47ed73aef9e208af4f135ff6f1b453d

thanks @Teamop, you were right. Now that is reverted also in version 5.0.1


/usr/lib/libvips.so.42: undefined symbol: rsvg_handle_get_intrinsic_size_in_pixels

Possible install-time or require-time problem
Summary
Technically the issue does not happen when I am installing it. However, on runtime, the error message shows up as an installation issue. Therefore I open an issue as installation issue. Here is the full console of the error:
/home/tony/JS/project/node_modules/sharp/lib/sharp.js:37
  throw new Error(help.join('\n'));
        ^
Error:
Something went wrong installing the "sharp" module

/usr/lib/libvips.so.42: undefined symbol: rsvg_handle_get_intrinsic_size_in_pixels

Possible solutions:
- Install with verbose logging and look for errors: "npm install --ignore-scripts=false --foreground-scripts --verbose sharp"
- Install for the current linux-x64 runtime: "npm install --platform=linux --arch=x64 sharp"
- Consult the installation documentation: https://sharp.pixelplumbing.com/install
    at Object.<anonymous> (/home/tony/JS/project/node_modules/sharp/lib/sharp.js:37:9)
    at Module._compile (node:internal/modules/cjs/loader:1103:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1155:10)
    at Object.require.extensions.<computed> [as .js] (/home/tony/JS/project/node_modules/ts-node/src/index.ts:1608:43)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/home/tony/JS/project/node_modules/sharp/lib/constructor.js:11:1)
    at Module._compile (node:internal/modules/cjs/loader:1103:14)

[x] I have read the documentation relating to installation.
[x] I have ensured that the architecture and platform of Node.js used for npm install is the same as the architecture and platform of Node.js used at runtime.

Are you using the latest version of sharp?

[x] I am using the latest version of sharp as reported by npm view sharp dist-tags.latest.

I am currently using 0.32.0. Also tried it with 0.29.3 and various version from 0.30.x, all had the same issue.
If you cannot confirm this, please upgrade to the latest version and try again before opening an issue.
If you are using another package which depends on a version of sharp that is not the latest, please open an issue against that package instead.
Is this a problem with filesystem permissions?
No
If you are using npm v6 or earlier and installing as a root or sudo user, have you tried with the npm install --unsafe-perm flag?
If you are using npm v7 or later, does the user running npm install own the directory it is run in?
Yes
If you are using the ignore-scripts feature of npm, have you tried with the npm install --ignore-scripts=false flag?
Yes
What is the complete output of running npm install --verbose --foreground-scripts sharp in an empty directory?

npm verb cli [
npm verb cli   '/home/gaara/.nvm/versions/node/v16.14.0/bin/node',
npm verb cli   '/home/gaara/.nvm/versions/node/v16.14.0/bin/npm',
npm verb cli   'install',
npm verb cli   '--verbose',
npm verb cli   '--foreground-scripts',
npm verb cli   'sharp'
npm verb cli ]
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm timing npm:load:whichnode Completed in 0ms
npm timing config:load:defaults Completed in 1ms
npm timing config:load:file:/home/gaara/.nvm/versions/node/v16.14.0/lib/node_modules/npm/npmrc Completed in 1ms
npm timing config:load:builtin Completed in 1ms
npm timing config:load:cli Completed in 2ms
npm timing config:load:env Completed in 0ms
npm timing config:load:project Completed in 2ms
npm timing config:load:file:/home/gaara/.npmrc Completed in 1ms
npm timing config:load:user Completed in 1ms
npm timing config:load:file:/home/gaara/.nvm/versions/node/v16.14.0/etc/npmrc Completed in 0ms
npm timing config:load:global Completed in 0ms
npm timing config:load:validate Completed in 0ms
npm timing config:load:credentials Completed in 1ms
npm timing config:load:setEnvs Completed in 1ms
npm timing config:load Completed in 9ms
npm timing npm:load:configload Completed in 10ms
npm timing npm:load:setTitle Completed in 0ms
npm timing config:load:flatten Completed in 2ms
npm timing npm:load:display Completed in 7ms
npm verb logfile /home/gaara/.npm/_logs/2023-04-03T09_33_31_158Z-debug-0.log
npm timing npm:load:logFile Completed in 4ms
npm timing npm:load:timers Completed in 0ms
npm timing npm:load:configScope Completed in 0ms
npm timing npm:load Completed in 21ms
npm timing arborist:ctor Completed in 0ms
npm timing arborist:ctor Completed in 0ms
npm timing idealTree:init Completed in 21ms
npm timing idealTree:userRequests Completed in 2ms
npm http fetch GET 200 https://registry.npmjs.org/sharp 1004ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/detect-libc 44ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/simple-get 105ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/node-addon-api 108ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/semver 109ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/prebuild-install 113ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/color 116ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/tunnel-agent 115ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/tar-fs 116ms (cache revalidated)
npm timing idealTree:#root Completed in 1138ms
npm http fetch GET 200 https://registry.npmjs.org/color-string 58ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/color-convert 62ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/github-from-package 60ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/napi-build-utils 60ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/mkdirp-classic 60ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/minimist 64ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/pump 64ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/simple-concat 79ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/tar-stream 85ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/rc 94ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/once 94ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/lru-cache 100ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/safe-buffer 100ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/node-abi 108ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/decompress-response 867ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/expand-template 913ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/chownr 912ms (cache revalidated)
npm timing idealTree:node_modules/sharp Completed in 935ms
npm http fetch GET 200 https://registry.npmjs.org/color-name 32ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/simple-swizzle 33ms (cache revalidated)
npm timing idealTree:node_modules/color Completed in 37ms
npm timing idealTree:node_modules/color-convert Completed in 1ms
npm timing idealTree:node_modules/color-name Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/is-arrayish 26ms (cache revalidated)
npm timing idealTree:node_modules/color-string Completed in 29ms
npm timing idealTree:node_modules/detect-libc Completed in 0ms
npm timing idealTree:node_modules/node-addon-api Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/ini 34ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/end-of-stream 36ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/deep-extend 36ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/strip-json-comments 36ms (cache revalidated)
npm timing idealTree:node_modules/prebuild-install Completed in 49ms
npm timing idealTree:node_modules/expand-template Completed in 0ms
npm timing idealTree:node_modules/github-from-package Completed in 0ms
npm timing idealTree:node_modules/minimist Completed in 0ms
npm timing idealTree:node_modules/mkdirp-classic Completed in 0ms
npm timing idealTree:node_modules/napi-build-utils Completed in 0ms
npm timing idealTree:node_modules/node-abi Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/wrappy 31ms (cache revalidated)
npm timing idealTree:node_modules/pump Completed in 35ms
npm timing idealTree:node_modules/end-of-stream Completed in 0ms
npm timing idealTree:node_modules/once Completed in 1ms
npm timing idealTree:node_modules/rc Completed in 2ms
npm timing idealTree:node_modules/deep-extend Completed in 0ms
npm timing idealTree:node_modules/ini Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/yallist 32ms (cache revalidated)
npm timing idealTree:node_modules/semver Completed in 35ms
npm timing idealTree:node_modules/lru-cache Completed in 1ms
npm http fetch GET 200 https://registry.npmjs.org/mimic-response 871ms (cache revalidated)
npm timing idealTree:node_modules/simple-get Completed in 876ms
npm timing idealTree:node_modules/decompress-response Completed in 5ms
npm timing idealTree:node_modules/mimic-response Completed in 0ms
npm timing idealTree:node_modules/simple-concat Completed in 0ms
npm timing idealTree:node_modules/simple-swizzle Completed in 4ms
npm timing idealTree:node_modules/is-arrayish Completed in 0ms
npm timing idealTree:node_modules/strip-json-comments Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/fs-constants 48ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/inherits 48ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/bl 51ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/readable-stream 54ms (cache revalidated)
npm timing idealTree:node_modules/tar-fs Completed in 71ms
npm timing idealTree:node_modules/chownr Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/util-deprecate 35ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/string_decoder 37ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/buffer 40ms (cache revalidated)
npm timing idealTree:node_modules/tar-stream Completed in 49ms
npm http fetch GET 200 https://registry.npmjs.org/ieee754 37ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/base64-js 44ms (cache revalidated)
npm timing idealTree:node_modules/bl Completed in 48ms
npm timing idealTree:node_modules/buffer Completed in 10ms
npm timing idealTree:node_modules/base64-js Completed in 0ms
npm timing idealTree:node_modules/fs-constants Completed in 0ms
npm timing idealTree:node_modules/ieee754 Completed in 0ms
npm timing idealTree:node_modules/inherits Completed in 0ms
npm timing idealTree:node_modules/readable-stream Completed in 7ms
npm timing idealTree:node_modules/string_decoder Completed in 3ms
npm timing idealTree:node_modules/safe-buffer Completed in 0ms
npm timing idealTree:node_modules/tunnel-agent Completed in 0ms
npm timing idealTree:node_modules/util-deprecate Completed in 0ms
npm timing idealTree:node_modules/wrappy Completed in 0ms
npm timing idealTree:node_modules/yallist Completed in 0ms
npm timing idealTree:buildDeps Completed in 3353ms
npm timing idealTree:fixDepFlags Completed in 1ms
npm timing idealTree Completed in 3380ms
npm timing reify:loadTrees Completed in 3381ms
npm timing reify:diffTrees Completed in 2ms
npm timing reify:retireShallow Completed in 0ms
npm timing reify:createSparse Completed in 7ms
npm timing reify:loadBundles Completed in 0ms
npm timing reifyNode:node_modules/chownr Completed in 172ms
npm timing reifyNode:node_modules/strip-json-comments Completed in 174ms
npm timing reifyNode:node_modules/ini Completed in 174ms
npm timing reifyNode:node_modules/wrappy Completed in 174ms
npm timing reifyNode:node_modules/once Completed in 174ms
npm timing reifyNode:node_modules/color-name Completed in 174ms
npm timing reifyNode:node_modules/end-of-stream Completed in 174ms
npm timing reifyNode:node_modules/mkdirp-classic Completed in 174ms
npm timing reifyNode:node_modules/simple-swizzle Completed in 175ms
npm timing reifyNode:node_modules/fs-constants Completed in 178ms
npm timing reifyNode:node_modules/inherits Completed in 178ms
npm timing reifyNode:node_modules/mimic-response Completed in 179ms
npm timing reifyNode:node_modules/decompress-response Completed in 179ms
npm timing reifyNode:node_modules/lru-cache Completed in 180ms
npm timing reifyNode:node_modules/ieee754 Completed in 181ms
npm timing reifyNode:node_modules/util-deprecate Completed in 182ms
npm timing reifyNode:node_modules/base64-js Completed in 182ms
npm timing reifyNode:node_modules/tunnel-agent Completed in 179ms
npm timing reifyNode:node_modules/string_decoder Completed in 183ms
npm timing reifyNode:node_modules/yallist Completed in 183ms
npm timing reifyNode:node_modules/expand-template Completed in 182ms
npm timing reifyNode:node_modules/simple-concat Completed in 185ms
npm timing reifyNode:node_modules/napi-build-utils Completed in 184ms
npm timing reifyNode:node_modules/deep-extend Completed in 185ms
npm timing reifyNode:node_modules/pump Completed in 184ms
npm timing reifyNode:node_modules/safe-buffer Completed in 188ms
npm timing reifyNode:node_modules/is-arrayish Completed in 187ms
npm timing reifyNode:node_modules/color-convert Completed in 186ms
npm timing reifyNode:node_modules/detect-libc Completed in 187ms
npm timing reifyNode:node_modules/tar-stream Completed in 193ms
npm timing reifyNode:node_modules/simple-get Completed in 193ms
npm timing reifyNode:node_modules/buffer Completed in 196ms
npm timing reifyNode:node_modules/rc Completed in 199ms
npm timing reifyNode:node_modules/bl Completed in 201ms
npm http fetch GET 200 https://registry.npmjs.org/color-string/-/color-string-1.9.1.tgz 157ms (cache miss)
npm timing reifyNode:node_modules/color-string Completed in 205ms
npm http fetch GET 200 https://registry.npmjs.org/color/-/color-4.2.3.tgz 153ms (cache miss)
npm timing reifyNode:node_modules/color Completed in 211ms
npm http fetch GET 200 https://registry.npmjs.org/prebuild-install/-/prebuild-install-7.1.1.tgz 185ms (cache miss)
npm timing reifyNode:node_modules/prebuild-install Completed in 237ms
npm http fetch GET 200 https://registry.npmjs.org/node-abi/-/node-abi-3.33.0.tgz 207ms (cache miss)
npm timing reifyNode:node_modules/node-abi Completed in 245ms
npm http fetch GET 200 https://registry.npmjs.org/github-from-package/-/github-from-package-0.0.0.tgz 210ms (cache miss)
npm timing reifyNode:node_modules/github-from-package Completed in 257ms
npm timing reifyNode:node_modules/tar-fs Completed in 257ms
npm http fetch GET 200 https://registry.npmjs.org/minimist/-/minimist-1.2.8.tgz 217ms (cache miss)
npm timing reifyNode:node_modules/minimist Completed in 262ms
npm timing reifyNode:node_modules/semver Completed in 269ms
npm http fetch GET 200 https://registry.npmjs.org/readable-stream/-/readable-stream-3.6.2.tgz 250ms (cache miss)
npm timing reifyNode:node_modules/readable-stream Completed in 285ms
npm http fetch GET 200 https://registry.npmjs.org/node-addon-api/-/node-addon-api-6.0.0.tgz 232ms (cache miss)
npm timing reifyNode:node_modules/node-addon-api Completed in 292ms
npm http fetch POST 200 https://registry.npmjs.org/-/npm/v1/security/advisories/bulk 299ms
npm timing auditReport:getReport Completed in 301ms
npm timing auditReport:init Completed in 0ms
npm timing reify:audit Completed in 303ms
npm http fetch GET 200 https://registry.npmjs.org/sharp/-/sharp-0.32.0.tgz 246ms (cache miss)
npm timing reifyNode:node_modules/sharp Completed in 309ms
npm timing reify:unpack Completed in 313ms
npm timing reify:unretire Completed in 0ms
npm timing build:queue Completed in 3ms
npm timing build:link:node_modules/rc Completed in 1ms
npm timing build:link:node_modules/semver Completed in 2ms
npm timing build:link:node_modules/prebuild-install Completed in 3ms
npm timing build:link Completed in 3ms
npm info run<EMAIL_ADDRESS>install node_modules/sharp (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)

<EMAIL_ADDRESS>install
(node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)

sharp: Detected globally-installed libvips<EMAIL_ADDRESS>install node_modules/sharp (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)
sharp: Building from source via node-gyp
gyp info it worked if it ends with oknfo run<EMAIL_ADDRESS>install node_modules/sharp (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)
gyp verb cli [
gyp verb cli   '/home/gaara/.nvm/versions/node/v16.14.0/bin/node',
gyp verb cli   '/home/gaara/.nvm/versions/node/v16.14.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js',
gyp verb cli   'rebuild'
gyp verb cli ]
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| linux | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb find Python Python is not set from command line or npm configurations/sharp (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)
gyp verb find Python Python is not set from environment variable PYTHON
gyp verb find Python checking if "python3" can be used
gyp verb find Python - executing "python3" to get executable path
gyp verb find Python - executable path is "/usr/bin/python3"
gyp verb find Python - executing "/usr/bin/python3" to get version
gyp verb find Python - version is "3.10.10"n<EMAIL_ADDRESS>install node_modules/sharp (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)
gyp info find Python using Python version 3.10.10 found at "/usr/bin/python3"
gyp verb get node dir no --target version specified, falling back to host node version: 16.14.0
gyp verb command install [ '16.14.0' ]
gyp verb install input version string<EMAIL_ADDRESS>install node_modules/sharp (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)
gyp verb install installing version: 16.14.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version is already installed, need to check "installVersion"s/sharp (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)
gyp verb got "installVersion" 9
gyp verb needs "installVersion" 9
gyp verb install version is good
gyp verb get node dir target node version installed: 16.14.0
gyp verb build dir attempting to create "build" dir: /home/gaara/node_modules/sharp/build
gyp verb build dir "build" dir needed to be created?

System:
OS: Linux 6.2 Arch Linux
CPU: (8) x64 Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
Memory: 22.73 GB / 31.25 GB
Container: Yes
Shell: 5.1.16 - /bin/bash
Binaries:
Node: 16.14.0 - ~/.nvm/versions/node/v16.14.0/bin/node
Yarn: 1.22.17 - ~/.nvm/versions/node/v16.14.0/bin/yarn
npm: 8.3.1 - ~/.nvm/versions/node/v16.14.0/bin/npm
npmPackages:
sharp: ^0.32.0 => 0.32.0

sharp: Detected globally-installed libvips v8.14.2
sharp: Building from source via node-gyp

It looks like you are using globally-installed libvips and librsvg shared libraries. An undefined symbol error at runtime usually suggests there are multiple or conflicting versions present on the same machine, so please ensure you're using the latest librsvg and that there is one version only.

@gaara4896 Were you able to make any progress with this?

Closing due to inactivity but please feel free to reopen with more details if further help is required.


Updated cli client doc with added commands

Description
Same as title
Test Plan
Local

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] protocol change
[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

If you do Laura, just update this page in the docs folder, and not the other in the doc folder.


Subpixel antialiasing

A noob one: looking at pathfinder and linux FF side by side

For small-ish font size is it the subpixel rendering that makes Firefox's output looking so much better?
How much does the HDPI alleviate the difference?

The main issue here is that lorem-ipsum snaps to the nearest pixel. Fixing this requires some API and batching changes.

This is implemented now. Please feel free to open more issues for bad-looking text :)


Added a flag to the install script to skip download and build

The added --conf flag is the complement of --bin.
I added this flag since I wanted shell autocomplete without downloading or building fzf (already provided by my distribution at /usr/bin/fzf).

Thanks, but the installer already checks if fzf is in your $PATH, and skips downloading if the version of the binary is the latest, so I don't think we need this flag. Also, it's not a good idea to allow only installing the latest scripts without making sure that you have the latest binary because the scripts may require the new features from the latest version.


cex.io backfill depth problem

Hi,
z@zcex:~/zenbot$ ./zenbot.sh -V
4.1.0
I dont have problems backfill with any exchange except of cex.io.
z@zcex:~/zenbot$ ./zenbot.sh backfill poloniex.BTC-USDT --days=1
(node:30320) DeprecationWarning: collection.save is deprecated. Use insertOne, insertMany, updateOne, or updateMany instead.
skipping 24 hrs of previously collected data
poloniex.BTC-USDT saved 200 trades 0 days left
download complete!
But cex.io:
z@zcex:~/zenbot$ ./zenbot.sh backfill cexio.BTC-USD --days=1
(node:30580) DeprecationWarning: collection.save is deprecated. Use insertOne, insertMany, updateOne, or updateMany instead.
skipping 10457 hrs of previously collected data
cexio.BTC-USD saved 1000 trades 1473 days left
I wanted only 1 day, but you see.
Also.. that ends with following:
z@zcex:~/zenbot$ ./zenbot.sh backfill cexio.BTC-USD --days=1
(node:30580) DeprecationWarning: collection.save is deprecated. Use insertOne, insertMany, updateOne, or updateMany instead.
skipping 10457 hrs of previously collected data
cexio.BTC-USD saved 1000 trades 1473 days left
.
error: getTrades() returned duplicate results
{ product_id: 'BTC-USD', from: 376024 }
{ product_id: 'BTC-USD', from: 376024 }
Thank you.

The depth problem is just the way the Cex.io API is constructed, they don't let you specify a date range, so zenbot will get all the data it can. There's nothing that can be done about that.
The duplicate results is a bug with the Cex.io data, 375024 and 376024 return the same exact data which causes the backfill to fail.
https://cex.io/api/trade_history/BTC/USD/?since=375024
and
https://cex.io/api/trade_history/BTC/USD/?since=376024
I created a pull request with a fix for this issue. https://github.com/DeviaVir/zenbot/pull/1982


Rename helpers

Rename helper modules for consistency with Rails naming. “Checkbox” is technically one word, and “Style Sheet” is technically two words, but Rails gets this wrong, and the adapters should match.

Rename Checkbox → CheckBox
Rename StyleSheet → Stylesheet

We decided against this because Javascript just looks awful. Everyone knows it's blatantly JavaScript.


where is  /opt/nvidia/tao/tao-converter

I use  the command  pip3 install nvidia-pyindex and pip3 install nvidia-tao  to install it ,but in my computer didn't appear   /opt/nvidia/tao/tao-converter. Can you explain this step in detail.

We expect you to do the conversion inside the isaac_ros dev container. Inside the container you should find the toa-converter in that location.

did this work?


HAD-8830: Adding Support for PySpark in Geo-Addressing SDK

Added Guidelines to use PySpark Geo-Addressing SDK for:

Databricks Cluster
Snowflake Connector for Databricks and EMR

A new directory is created named 'pyspark' containing all the information about Databricks-Addressing and Snowflake Connector.

Merging into Dev as PySpark <IP_ADDRESS> release process is completed.


Can the reading of results be speed up?

I am making a power logger to log the power consumption for a esp32 BME280 sensor that's is active less than 350ms thanks to ESPNOW to a SD card and are with your great library getting really good measurement speeds since it can set the ADC to 9-bit unlike other libraries. I get a full sampling every 1700us (shunt, busvoltage, current and voltage) and have seen that I get varied values between the measurements so its not just the same INA219 reading read twice.
I noticed that each "get_value" request is taking way more (300-700us) than the 84us the 9-bit conversion in the datasheet states and started to think it about and remembered that I read that Sparkfun BME280 library (in pull request 50) is using burst reading according to bme280 datasheet section 4 and reads all registers at one time and then divides them up. Would this be possible to do here as well and will it speed up the reading and minimise the risk that two "get" is from different samplings? I noticed that this is way over my head and I do not have the knowledge myself to do it but thought it might be something you know how to do and was interested in?
Just an idea... that might be totally stupid but thought it was worth asking you.
Best regards, Albin

Duplicate. Got a 404 when saving the first time but it saved twice apparently.

Duplicate. Got a 404 when saving the first time but it saved twice apparently.