"globalThis" is not compatible with older browser

at file @azure/core-util/dist-esm/src/uuidUtils.browser.js

@freedom-git thanks for reporting? what version of browsers are you using?  We generally only support latest versions of browsers.

chrome version is "69.0.3497.128",
in this line:
https://github.com/Azure/azure-sdk-for-js/blob/e2b3c14fa865d81d2a736ad835019d0aa762f287/sdk/core/core-util/src/uuidUtils.browser.ts#L16C51-L16C51
It seems your code is trying to cover the situation that "globalThis" isn't exist. but it not working.

@freedom-git globalThis is available in chrome 71.  chrome 69 was released in September 2018.  We don't want to encourage old browser usages.  If you really need to use old browsers ould you add a polyfill by yourself before loading azure sdk module?  Something like
if (typeof globalThis !== "object") { global.globalThis = this; } or window.globalThis = window; }

@samirkatyar Node v10 reached End of Life on April 30 2021. Soon we will stop supporting Node V14 which reached EOL on earlier this year.  We recommend that you migrated to a supported version of NodeJS.
If you really want, you may try setting global.globalThis = global?


How to return a list?

It's nice that you can define a Pydantic model and pass it to the decorator's responses param:
@app.get( "/foo", responses={ "200": MyPydanticModel } )

However, Pydantic models turn into JSON objects.  What if you want to return a JSON array response instead of a JSON object?

see discussions #57


Options for better browser support?

Currently Tink is using a lot of features from ES6 but some of these are not supported by most browsers.  Default values, for instance, is only supported by Firefox at the moment.  It's not supported until Chrome v49, which hasn't been released yet.  Are there any tools similar to Tink that would be recommended until browser support catches up?

The source code is written in ES6, but in the bin folder you'll find the compiled ES5 code which should work in current browsers.

Ah, great, thank you for pointing that out.  I didn't notice anything in the readme and went straight to src.


Find a way to ping if markets are open, or tighten time restrictions to be more exact.

Fixed with time constraint


Let's Implement a Plugin System

This is more of an idea for a new feature rather than an issue with any existing software.
I think Bitcoin needs a reference client that is politically neutral by default and allows the full node operator to easily make any kind of a soft fork for their personal use. Typically in software development context such ability could be referred to as a plugin system. I don't think everyone should make their own fork of the original Satoshi's Bitcoin Wallet just to change a couple of small rules.
Example use case would be to add custom filters between the raw incoming data from the network and the mempool of TXs. The power of the full node is to decide which TXs and blocks they wish to relay and which not. So let's bring that power to the full node operators. I would be more than happy to write a custom block and TX filter for myself that would reject SegWit TXs and blocks containing or allowing to contain SegWit TXs. This is such a small adjustment that it does not seem rational to make my own branch of the reference client just for that.
With such a plugin system everyone could make simplex soft forks rather easily. It is one more reason for people to run full nodes and it incentivizes full node operators to maintain a well-connected node on the network.

This is not a bad idea.
I personally think that the full node software should do the minimum amount of things, and do those really really well. And this makes a plugin system go out of scope very quickly.
I do agree with your suggestions that this would be great to have and as such I was thinking about how this could be done cleanly.
An idea came up where the full node uses Classics AdminServer to notify listeners of new transactions that are accepted in the mempool.
It would be much easier to have such a "plugin" interface based on top of a simple protocol where any application in any programming language can then register itself and "filter" transactions just like you suggest.
I'd welcome such innovation.

Yes, perhaps there should be some kind of TX and block propagation proxy/wrapper as a separate application which will essentially sandbox the full node. The full node itself would have to be configured to connect ONLY to that proxy which will most likely run on localhost. The proxy would have to do the p2p networking. I think most full node implementations allow the node to connect to only a predefined set of hosts (-connect command line parameter?) This approach should comply to the principles of modular design quite well.

that is roughly the same idea I wrote about, but the suggestion I wrote is much simpler as it doesn't require you to proxy p2p traffic (which is not exactly trivial as the p2p layer is very proprietary).

Perhaps a less portable way of achieving this would be to capture the packets of bitcoind with the help of the OS similarly to how wireshark does it. The custom soft fork filters could be applied on that level then. I'm not familiar with AdminServer though. But anyway, wouldn't it make sense to start a Bitcoin hub project which main purpose is to relay/proxy the p2p data without doing any validation and without storing anything on disk? Such a hub would be a perfect application where to stick the soft fork rules.

I'm not familiar with AdminServer though.

There is some more information about it here; https://bitcoinclassic.com/devel/AdminServer.html

There are more people that are interested in this topic, so I want to suggest an approach that I think will be useful.
Using a networked client ("The Plugin") that communicates with Bitcoin Classic over the Admin Server (unix socket) that client can subscribe to events. Events like a block that's coming in.
Then when Classic gets a block it validates its header and then notifies the plugin via the admin server. Probably inserting some meta data like the header, the amount of transactions and the size of the block. The admin server replies either Ok or Cancel. Causing this block to be accepted or rejected.
Notice that The Plugins lives in a different process, or even on a different machine, from the Bitcoin Classic node. I think that is a smart design to keep the client lean and easy to maintain.

@zander
this is an excellent idea. If the plugin could potentially even live on a different machine it could easily be shared as a "service" in a company's private network. That way a single machine will dictate the soft fork policies for the whole company that could be running many full nodes. could turn useful in some cases.
perhaps this architecture would also make it possible to easily implement your own mempool rules to determine which unconfirmed TX chains are kept in mempool and which ones get kicked out when no more memory could be allocated for the mempool. Miners could then implement their own custom logic more easily. For example, a miner would be interested in confirming the chain on TXs that pays the most fees per byte even if the oldest TX in that chain is dust.
What is more, making the plugin a completely separate process allows easier contribution to the project because the contributors don't have to dive into the reference client's own source code.


TS-4978: illegal memory access with ticket_key.filename

Avoiding illegal memory access by checking the return value of readConfigStringAlloc .

Please review @SolidWallOfCode

Looks good.

Looks like we have merge conflicts now.

I will do a local merge and then make a new  PR

The conflict is resolved. Please check


Add CONTRIBUTING.md

Magic file with contribution notes.
See https://help.github.com/articles/setting-guidelines-for-repository-contributors/ .

Fantastic, thanks! Any chance you can squash the commits?

@yupferris good to know that you can also squash them when you merge the PR (directly in the GitHub UI when you select merge -> drop down and squash commits)

@yupferris, done. @emoon, thanks, I didn't know that.

Oh wow I also didn't know that, haha. Thanks for the tip @emoon and thanks for squashing @roshats :)
Normally I wait until the next stream to accept PR's but since this doesn't affect the code I think I'll take it now (and mention it on the next stream ofc).

np :) I found out about it like two days ago also :)


correct dead links in the basic usage documentation

I was setting up rubocop on something this morning and found a pair of dead links in the documentation, so I figured I'd pay it forward and update them. This corrects some references in basic_usage.md that point to what's now in different documentation files.
I THINK this is in line with the contributing guidelines (and since there's not really a programming change there's no need for a changelog entry? I think) but if I guessed wrong, apologies!

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[na] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[na] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[x] Run rake default or rake parallel. It executes all tests and RuboCop for itself, and generates the documentation.

These links were changed when a part of the README divided into the manuals. rubocop-hq/rubocop@d40e8a9
This PR reproduces the original links. Also, it is okay without additional writing to changelog.
Thank you for opening a good PR!


feat: add StackedPanel

Please check if the PR fulfills these requirements

[x] The commit(s) message(s) follows our guidelines
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

What is the current behavior? (You can also link to an open issue here)
This is a missing component and it's not specified in frontify.
What is the new behavior?
We are adding here a new component which is a way to stack actions.
What is a stacked action ?
You are filling a form with a select input which display a list of whatever you want.
But the value is missing and you can add a new value -> stack a form which let's you add this value to your database.
Example of stacked forms:
Add User -> Add Contact -> Add Company

is it intended to allow the user to use both small/large panels  in the same stacked panel component ?

small panel setting is glitched on storybook

not anymore needed . Use Layout.drawers


lints: add lint for TorServiceDescriptorHash ext.

The new lints/lint_ext_tor_service_descriptor_hash_invalid.go lint validates that certificates with .onion subjects issued after July 28th, 2017 include a well formed TorServiceDescriptor extension with a TorServiceDescriptorHash entry for each onion eTLD+1 subject as expected by CAB forum Ballot 201.
E.g. a certificate with three onion subjects (a.example.onion, b.example.onion, c.other-example.onion) should have two TorServiceDescriptorHash entries in the TorServiceDescriptor
extension:

One with URI https://example.onion
One with URI https://other-example.onion

Only the eTLD+1 is relevant for Onion sites. Subdomains are resolved by the hidden server based on the HTTP layer Host header.
Unlike the previous PR I opened for this lint the parsing work is now done in zcrypto (requiring a change to the go.mod version pin for zlint).  See https://github.com/zmap/zcrypto/pull/189 for more background/discussion
The new linter will return a fail result if:

There is no TorServiceDescriptor extension present.
There were no TorServiceDescriptors parsed by zcrypto
There are TorServiceDescriptorHash entries with an invalid Onion URL (unparseable, missing hostname, non-HTTPS protocol, etc).
There are TorServiceDescriptorHash entries with an unknown hash algorithm or incorrect hash bit length.
There is a TorServiceDescriptorHash entry that doesn't correspond to an onion subject in the cert.
There is an onion subject in the cert that doesn't correspond to a TorServiceDescriptorHash.

Resolves https://github.com/zmap/zlint/issues/14

This looks solid. Thank for you the time to pull this all together in both ZLint and ZCrypto. These PRs have been the dream to review.

@zakird Thanks! :-)


Authentication for API users

Description

There's a need for authentication to be implemented for API users.
More descriptions coming soon...
DoD (Definition of Done)

A metadata submitter API user can be authenticated through API so that he can submit his metadata through an API.
Testing

Coming soon...

We would need to restrict access so that users cannot create new users, or have permissions we were not expecting them to.


Fix completion handling on background thread

Description
While testing the framework within an app we noticed that the completion handler is called on a background thread which causes the an app crash. To prevent this we should move the completion handler calling to the main thread.

This is closed since we implemented it in adjustments branch.


Allow setting extension as .md instead of .snap

I think .md extension is quite flexible
it is also possible to print language specific within code blocks
```yaml
```
```rust
```

Benefit of this is that it can be used as documentation.
Especially for macros libraries, that get input as code generate code.

The downside is that the system assumes that files named .snap are snapshots. If the extension were .md we would be picking up unrelated files and tried to process them as snapshots.


Allow members to have access to all CF repos

tldr; we're proposing that all CF Members be allowed to create and push to (non-main) branches in all CF repositories. This would prevent unnecessary forking, and a given an extra permission layer to members to incentivize joining the community.
Reduce Forking
Many teams will continue to pair program, and while pair programming it is significantly easier to manage permissions and access via branch than via fork. The pain that we are describing leads to potential contributors creating forks in organizations like cloudfoundry-incubator, which leads to problems as described in this message:

People that aren't on the project teams have a hard time finding where work of that project team is actually happening.
The team specific orgs are not typically setup to ensure CLA's for any inbound pull requests.
Use of the cloudfoundry-incubator for these forks is confusing to observers, and completely different from what the incubator is supposed to be.

Member Rights
Currently there's not much distinguishing Members from non-Members. We want to empower our Members somewhat in order to incentivize folks to join the community. Creating branches and pushing to repos is a cheap and effective way to make Members feel more like first-class citizens.
Potential Problems
Protecting the Main Branch
In the past, there was a concern around members with push access pushing to main branches without the buy-in of the project maintainers. In the working group model it is already assumed that the main branches will be protected so that only Approvers have the ability to push and merge PRs to that branch.
Branch Cruft
There is a concern that having so many more community members with the ability to create branches will lead to an explosion of new branches on repositories, and that many will become stale and linger around. We think that although this is a concern, the proposed changes are worth that risk.

This is a super smart idea IMO!

Is this a proposal that will have to wait for the TOC to be elected? What can I do to bring it to the community's attention and potentially get it accepted?

I have a few thoughts on this - I'm one of the bosh maintainers for context. We have three patterns of codebase.

Just a master/main branch which we care about (which this pattern seems designed for)
A develop -> main pattern
Multiple prod branches that we care about and patch (stemcell lines being a prime example)

There is a slight risk that the org opens up push permissions without all teams adequately protecting key branches and potentially malicious code slips though and gets published. Considering we're automating publishing of releases on some repos, there may be no human eyes on a chunk of code once it's in a "safe" branch. I think this risk can be mitigated but should be thought through.
On the branch cruft side, it may be relatively cheap to build out a github app that deletes all stale branches older than a year (or something long)

It really lowers the barrier for contributions, for example when contributing as a team, where forked repos need to be made accessibly to others. It would be much cleaner to have a branch in the target repo, which can still be reviewed and merged based on a PR.
Not sure whether GitHub provides such capabilities, but there could be a special branch namespace, like contrib/*, which is open to everyone, while all other branches are only accessible for maintainers. This would also reduce the risk to accidentally create new branches that are not protected, but should be.
Another question would be how that interferes with the current CLA process? With the option to directly push to a branch, anybody can add code to the project without anybody else checking. Even though the code of such a branch is not relevant for the release of the project and is not used at all, legally it might still be part of the project and would be an issue?

Like the contrib/* convention. This would address the concern around Multiple prod branches. This should be relatively save to roll out, just not sure if it is possible allow a team to only create branches which match a wildcard.
Maybe a singed CLA should be added to the requirements for becoming a Member.

Wrt, the logging and metrics repos, I've been trying to push a few things. But one of them that can help is that pr's are limited to approved pull requests and approvals mostly seem to go away when new commits are pushed(this is something that's possible easily with concourse, and github settings). If you setup approval requirements, it should be easier to limit potential vulnerabilities, but also rate limit the ability of community prs to consume expensive iaas resources.
I've also gotten rid of the develop -> master pattern. I don't this is very oss friendly, or in line with where we want to take the org.
I havn't worked to protect older release branches yet, and that would probably be necessary, but shouldn't be that hard.
As far as branch cruft, I think @mrosecrance's point is very good in this repsect.

I think it'd be interesting to try out this proposal for a small subset of repos in the App Runtime. @ctlong, since you mentioned that this proposal would help out some of your workflows substantially, is there a short list of repos that would be most valuable on which to try this out?
If GitHub doesn't allow branch policies to match a wildcard such as contrib/*, another option could be to have canonical contribution forks for repos in the https://github.com/cloudfoundry-community organization, which already has a liberal membership policy.
Also, 👍 to adding CLA acceptance as a membership requirement in the new governance rules. We'll likely want to add some nuance that this may be via a corporate CLA and an individual's association with that corporation. @christopherclark may also be able to tell us what the current state of affairs is with regard to CLAs and members.

@emalm yes! My short list of repos would be:

cloundfoundry/routing-release
cloundfoundry/gorouter
cloundfoundry/routing-perf-release
cloundfoundry/cloud_controller_ng
cloundfoundry/capi-release

Thanks, @ctlong ! Could you coordinate with @christopherclark, @sethboyles, and @ameowlia about how we could arrange an access experiment on those repos? Maybe we could give this proposal a trial for a month to see what problems arise.

Turns out that base member permissions can only be applied at the org-level (not per repo), which doesn't dispose itself well to implementing this proposal on a trial basis. For now, @sethboyles and I created a "General Contributors team" with write permissions to cloud_controller_ng and capi-release. We can reuse this team for networking too.
Not yet sure how to batch add all CF members to that team though 🤔 .

I should have updated a vast majority of the logging/metric releases to have:

pr rules requiring reviews to run the pipelines

only allow pushing from admins

This is the case on both the main branch and the v[0-9]* branches.
This seems necessary, but I'm not sure if it's sufficient to gain protections. Anyone know if there's anything I should be concerned about?

update: I think I want to ensure that approvals are limited before making these changes in logging and metric repos and that's not done.

update: I think I want to ensure that approvals are limited before making these changes in logging and metric repos and that's not done.

@Benjamintf1 can you elaborate on the problem? Is it that you want to limit approvals to only specific repo members (ie. admins)?

Reading the settings, it seems like pr approvals are allowed to anyone with write permissions. This seems less then ideal/like it would make any branch permissions null/pointless.

That's not ideal. I don't think that makes branch permissions pointless though, as the restriction on who can push to matching branches also prevents anyone without those permissions from merging PRs into those branches. @sethboyles and I tested that.

@Benjamintf1 after you pointed out the extra permissions attached to write access I did some more research and it turns out that there's a lot more permissions attached to it that we might not want to give, for example:

Close, reopen, and assign all issues and pull requests
Edit and delete anyone's comments on commits, pull requests, and issues
Create and edit releases
Create, edit, run, re-run, and cancel GitHub Actions workflows

(See the Github org roles and their repository permission levels here)

@ameowlia and @sethboyles also pointed out the following:

Based on the proposed community roles there are the following roles per working group:

Member
Approver - has write permissions to repos (presumably to all branches), can allow PRs to be merged.
Leads - can manipulate issues/PRs

Giving write permissions to members are incongruent with those proposed roles. There might be space to edit the proposed roles, but it does seem like we would be forced to open up more permissions than we would like to. Not sure who came up with the proposed roles, but maybe they have thoughts on how the general intent of your proposal can be integrated with the Working Group model?

It doesn't fit perfectly (ex: approvers would be able to manipulate issues/PRs), but the following seemed the most logical current mapping for the proposed community roles based on their descriptions:

Member -> Read access
Approver -> Write access
Leads -> Admin access

@chipchilders @emalm does that look right? If that is the case, should the roles doc be amended to include that information?
As for this specific proposal, it essentially proposes changing the mapping to:

Member -> Write access (w/o access to protected branches)
Approver -> Write access (w/ access to protected branches)
Leads -> Admin access

That change doesn't sound as optimal to me as I previously believed it to be. What do folks think? It may be worth waiting for Github to release new RBAC features for Github Enterprises, which is planned for relatively soon: https://github.com/github/roadmap/issues/111 (it's been pushed back several times already though).

Would a cloudfoundry-contributions org with relaxed permissions, like member -> write access, be able to get us 80% to where we want to be?
I.e. no need for personal forks, it's clear where contributions happen, members have slightly privileged access.
WDYT?

I feel like once you have to work on a fork, it's not any more or less convenient for that to be a personal fork(or a org fork for a group of people) then any other org/repository.

The TOC discussed this on 30th August 2022, along with @ctlong. In summary, we don't feel that GitHub's authorisation model is sufficiently granular for us to implement this safely. There's nothing on the horizon that would enable it either, so we feel this has hit a dead end, and we're closing it off.


Navbar Upgradation

Updated Navbar as per Requirement :-
Thanks

Give here a screen shot of the updated navbar, you can do a short video of the whole web-page and share here also

Give here a screen shot of the updated navbar, you can do a short video of the whole web-page and share here also

Nice work due.
Give a star to our repository and stay connected with our MESSI_MANIA family
Thank-you


Question: Install Postgresql Problem

Hi, I always get a blank page when trying to install with Debian Wheezy, Apache and Postgres.
Any hints?
thank you
tekuton

Check the apache/php error logs, you should see the exact error.

The setup of a postgres is something to be better supported elsewhere.
My setup is working now. Anyone in need of little help with a psql set-up - may drop me message.
Thx


Loading spinner before loading image

I have a sildeshow build with v-repeat

I want to show spinner before the image is loaded in the browser memory and show the image afterwards.
Any ideas?

You should ask on the forum
https://github.com/yyx990803/vue/blob/dev/CONTRIBUTING.md#issue-reporting-guidelines


Remove terra-mixins

Description of Issue
Remove terra-mixins.
I don't think we need terra-mixins with css-modules: https://github.com/cerner/generator-terra-module/blob/master/generators/app/templates/src/projectName.scss#L1

Resolved with pr #65


Remove breakpoints

I am using the library directly (no copy) in my project. This has made my project difficult to debug since there appears to be breakpoints in the library, and so the debugger keeps stopping on those remote breakpoints. Please clear?

Thank you for reporting. I'll check it. However, I don't set it. It is curious.

I confirm this.

Thank you @larvanitis . I try to remove all breakpoints.

I am getting this issue also with latest version

Hello, I made the new version 11 of Google App Scripts for this project.
But it does not solve this issue, of course, there are no breakpoints I set.
@stubar Thank you for giving the idea. I still wonder that...

Hi there! Google App Script support V8 runtime. Please upgrade your script and this library to version 12.
We can debug as well.


extarce data

How to extrace data?How to perform this step?

You simply need to download the data, make a directory called exp_output and place the downloaded directories at that location. For a quicker response, you may want to use the forum on the grand challenge website.


Changing 'jakarta.activation.jar' to 'jakarta.activation-api.jar' in …

…start script to run with JDK 12.
Signed-off-by: Svante Schubert<EMAIL_ADDRESS>There is a small typo in the naming of the jakarat.activion JAR in all batch files, see
https://mvnrepository.com/artifact/jakarta.activation/jakarta.activation-api/1.2.1

It should actually be without the -api, there is wrong jar inside jaxb-ri.zip/mod, fix is on the way.

fixed by #1318


Add vehicle of interest coloring.

Allows specifying a vehicle of interest pattern. For now this only .
I am trying not to be too intrusive with this since it would otherwise complicate merging #1687.

[ ] Follow up with issue to expose vehicles of interest in low dimension observations.

@qianyi-sun Please confirm that this works for you.

@qianyi-sun Please confirm that this works for you.

@Gamenot Thanks, I have tested on my side, it works as expected.


sc-2189 verification RPC test

This adds a test for the GDS Verification RPC.

Codecov Report

Merging #242 (f9167b8) into main (3bf948a) will increase coverage by 0.37%.
The diff coverage is 100.00%.

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

@@            Coverage Diff             @@
##             main     #242      +/-   ##
==========================================
+ Coverage   42.97%   43.34%   +0.37%
==========================================
  Files          53       53
  Lines        6157     6157
==========================================
+ Hits         2646     2669      +23
+ Misses       3044     3020      -24
- Partials      467      468       +1

Impacted Files
Coverage Δ

pkg/gds/gds.go
33.57% <100.00%> (+8.30%)
:arrow_up:

Continue to review full report at Codecov.

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


fix: avatar alpha blending

What does this PR change?
fixes #418
This change fixes the last two avatar issues with alpha clipping that Alvaro found. I've added the 2 offending avatars into the Avatar Randomiser to make it easier to test.
How to test the changes?
Load into game, load 30 test avatars from the Avatar Randomizer
Find the 2 avatars and check the alpha issues highlighted in the issue.
Our Code Review Standards
https://github.com/decentraland/unity-renderer/blob/master/docs/code-review-standards.md

The alpha is now fixed, but the textures look too pixelated, I dont know if its because we are using alpha clip or we dont have any kind of filtering on the textures?
Unity Renderer

Explorer Alpha

Unity Renderer

Explorer Alpha

I've added some shader changes, but for some reason whatever I do the sampling front on the texture arrays I'm unable to move it away from Anisotropic x9, and we're currently not utilising mipmaps, so it's trying to use Mips for the sampling, so without them it's limited to what it can handle. Juani and I have discussed Mips generation on the asset bundler when we validate the texture formats & resolutions.
Should be alright now though.


Copying a file doesn't update the active file that is in focus, but the Explorer focus does change, which is confusing

VS Code Version: 1.55.2
OS Version: Mac 11.3

Steps to Reproduce:

Copy a file from the Explorer
Paste the file
The highlighted file in Explorer will be the copy
The focus in the edit pane will be the old file
Since the focus in the Explorer is the new copy, you assume you are editing your new copied file, when in fact you are editing the original, resulting in an annoyance where you edit the file and save, and you actually over-wrote the original and not the new copy

Does this issue occur when all extensions are disabled?: Yes

Duplicate of https://github.com/microsoft/vscode/issues/120882 which i missed when searching


[Bug] Any error log on widget is not restored once widget deletion is undone

Description
Once user deletes a widget with errors and undoes the delete operation, logs for the error are no longer displayed on the
debugger while widget still displays the error
Steps to reproduce the behaviour:

Add table widget (or any other), type in an incorrect JS code to show an error in the debugger
Observe error logs in debugger
Delete widget and undo delete
Observe the error log clear once widget is restored but widget still shows an error (red state of property pane)

Important Details

Version: Cloud
OS: Win10
Browser: Chrome
Environment: Release & Production

@ramsaptami  Could you clarify how you were able to undo, because the error says until the undo toast is present?

@akash-codemonk That's right. Technically, if the widget is restored then the errors should be restored too but I guess it's cleared by the delete operation


Improve model serialization

The transactions currently implement the From trait in a very weird way to convert the flags. It doesn't really make sense. The From trait should be implemented for the ...Flag enum.

resolved with comiit: restructure transactions and request modules


No unused vars not working

First of all thanks for this nice configuration i really love it :) !
I need to customize few rules and it works great except one : no-unused-vars.
In your configuration you set it to : 'no-unused-vars': 2.
In my tests i used should like this :
import shouldHttp from 'should-http';

describe('...', () => {
   it('...', done => {
      request.get('...', (err, res, body) => {
         res.should.have.status(200);
         done();
      });
   });
});
...

eslint think that i do not use shouldHttp.
I customized xo rules in package.json (according to http://eslint.org/docs/rules/no-unused-vars.html) with this rule : "no-unused-vars": [2, {"args": "after-used", "argsIgnorePattern": "shouldHttp"}] and i also tried  "no-unused-vars": [2, {"args": "all", "argsIgnorePattern": "shouldHttp"}] but nothing worked i had to make this :
import shouldHttp from 'should-http'; // eslint-disable-line

Maybe it's not a problem with xo but eslint ? (or me ...)

Are you using the main rule or the esnext one? Are you using babel-eslint?

I do have "esnext": true in my package.json

Then it might be a babel-eslint issue. It already has a bug with no-unused-vars: [2, {vars: local}].

All right i'll search there then :) Thanks for pointing it out


Basic implementation example

Hello,
Do you have an example you could post or link to a bare bones implementation?

Hey there!
A very contrived and bare bones example is the integration test for this package.
But of course, this package mostly makes sense for more complex business domains which are hard to show in a small contrived example :wink:
To give you a basic overview:
space-cqrs is a very simple implementation of a (non-distributed) version of the DDD + CQRS + Event Sourcing patterns. It provides a base class for event-sourced [Aggregates] (http://martinfowler.com/bliki/DDD_Aggregate.html) and ProcessManagers as well as serializable ValueObjects to model your business domain. It is not a full-blown CQRS framework with a distributed messaging service bus etc. but tries to keep everything as simple as possible and only supports messaging per-process.
It also provides a (currently) extremely basic implementation of a MongoDB based EventStore which works a little bit different than "normal" event store implementations because MongoDB doesn't support transactions. To circumvent this downside of MongoDB space-cqrs uses the concept of a commit which bundles multiple events and commands together into one "transaction" commit. Here is a short blog article talking about the basic concept.
It heavily uses the space-messaging package for Meter EJSON and runtime-checked domain events and commands that are automatically serialized into the MongoDB and restored for you. So you don't have to deal with serialization concerns anywhere but within your value objects.
My plan is to write more about all these topics as soon as I get a little bit more spare time beside my current project Prisma, at the moment there is a lot todo for the launch on 1st of April :wink:
Maybe you could tell me a little bit more about your background with these topics?

Hi, I'm interested in this as well. I've implemented pretty large CQRS implementations in C#, and am looking for a good js implementation. The service bus isn't important, but this looks like a pretty nice implementation. Any chance you could go over your integration test in "literate coffeescript"? While its pretty clear what's going on, it takes some experimenting to get things right when actually implementing it.

Thanks for the overview @DominikGuzei. Your response would be great to integrate into the existing readme, as is does fill in the gaps nicely. I understand it's one of those situations, but I guess a small example application to neatly demonstrate the setup with a folder structure that you would likely see in say the smallest projects of this nature would be a good reference hurdle. I found the demo app in the UI package, so maybe that can be extended to include the CQRS and EventSourcing elements, even though it's overkill in a real-world scenario. Like @withinboredom mentioned, maybe some comments in the integration test would also help.

Hey guys, thanks for your feedback – I guess you're right, this package needs some small real-world example that shows the interaction of client / server with real value objects and event-sourced aggregates etc. The problem with the integration test is, that it only shows a pure server-side app.
I will think about the best way to add something :wink:

:+1: Spot on

Also regarding:

It is not a full-blown CQRS framework with a distributed messaging service bus etc. but tries to keep everything as simple as possible and only supports messaging per-process."

Do you think meteorhacks:cluster could help with establishing DDP-based distributed messaging via RPCs?

@rhyslbw I would suggest using a truly distributed messaging system like Amazon SQS or Azure ServiceBus. That way you don't have to rewrite the wheel and handle guaranteed once delivery, deduplication, etc.

Yeah, as @withinboredom said I would also go with something really stable and well known for this functionality. Distributed messaging is non-trivial and there is a little bit more to it than "just" sending messages between servers :wink:
That's also the reason why this package doesn't include this functionality. I try to avoid distributed architectures as much as possible, its a lot of complexity added to your system and you really need to be sure that you can handle the trade-offs. Also CQRS is not about distributed systems, its just a simple pattern to model your read and write model separately to optimize the read for the UI and the write for business logic. Although this package promotes event-sourcing for your write side, it is actually not necessary for CQRS.

Thanks guys, understood.
I'm working through the space-ui sample app, and it does seem to be an ideal base to fork and enhance with the clear notice indicating this is just to demonstrate the concepts of CQRS and Event Sourcing.
If you could give me a quick paragraph on how you manage projections I'll leave you alone to get your product launched! :smile:

Hey @rhyslbw this is the easiest part! Just extend Space.messaging.Controller and handle the events:
(This is a simple contrived example for an order system)
class OrdersProjection extends Space.messaging.Controller

  Dependencies:
    orders: 'Orders' # Your mapped orders collection (this is not default -> change for your case!)

  @on OrderCreated, (event) ->
    @orders.insert
      _id: event.sourceId # All events have a sourceId which is the id of the aggregate they belong to
      version: event.version # All events have a version with event-sourcing
      status: Order.STATES.created # Implementation detail
      product: event.productId
      quantity: event.quantity
      # etc ...

  @on OrderCompleted, (event) ->
    @orders.update event.sourceId, $set:
      version: event.version # All events have a version with event-sourcing
      status: Order.STATES.completed # Implementation detail
      # etc ...

Ah right I see the example now in the integration test, thanks. I'll definitely have more questions, but in the attempt to keep this thread on track, I'll post separate topics as new issues.

Ok I'm going to close this as I agree that a sample application or "basic implementation example" is just not practical.


Field length adjustment to LIKE() reference converts only to CHAR() type.

If I have a field with a +/-#  for a LIKE() field definition, the conversion makes the field type become CHAR(+/-#).
The +/_# value needs to be part of the LIKE() keyword or a comment added about not being able to convert properly.
Before
     D OTitems         DS                  Inz
     D  Otwkdt                             Like(Phdteow)
     D  Ottyp                              Like(Phtyp)
     D  Otstn                              Like(Phstn)
     D  Otdpt                              Like(Phdpt)
     D  Otearnings                   15p 5
     D  Othours                      +2    Like(Phhrs)
     D  Otwghtavgrt                  15p 5

After
       Dcl-Ds Otitems Inz;
         Otwkdt          Like(Phdteow);
         Ottyp           Like(Phtyp);
         Otstn           Like(Phstn);
         Otdpt           Like(Phdpt);
         Otearnings      Packed(15:5);
         Othours         Like(Phhrs: +2);
         Otwghtavgrt     Packed(15:5);
       End-Ds;

Notes on the fork I've tagged.
The original scenario would be handled now, also tested with multiple keywords on a single line (for example adding an inz('test') still gives the correct result.)
     D  Othours                      -2    Like(Phhrs) inz('test')
          Othours                   Like(Phhrs: -2) inz('test');
One scenario it doesn't handle is if the 'Like' keyword is on another line.
Below example would still end up defining Othours as a char(+2)
 D OTitems         DS                  Inz
 D  Otwkdt                             Like(Phdteow)
 D  Ottyp                              Like(Phtyp)
 D  Otstn                              Like(Phstn)
 D  Otdpt                              Like(Phdpt)
 D  Otearnings                   15p 5
 D  Othours                      +2
 D                                     Like(Phhrs)
 D  Otwghtavgrt                  15p 5

Thoughts are welcome on if it's worth doing a pull request now for a partial-fix, or wait until I can also think of a way to handle that scenario.

Sorry for my multiple commits related to this issue.  I kept thinking I was doing something wrong in my commit message as the issues were linked, but not closed.  I think linking to an issue will auto-close only if you are the creator of the issue.  So, the pull request #79 from the BrianGodsend/vscode-rpgfree fork does fix this issue.


npm ERR! Error: ENOENT, readdir

When nvm install'ed and nvm use'ed version 0.8.0 or 0.11.0, npm fails to find its man pages.
npm ERR! Error: ENOENT, readdir 'C:\Users\andrew\AppData\Roaming\nvm\v0.8.0\node_modules\npm\man\man1'
npm ERR!  { [Error: ENOENT, readdir 'C:\Users\andrew\AppData\Roaming\nvm\v0.8.0\node_modules\npm\man\man1']
npm ERR!   errno: 34,
npm ERR!   code: 'ENOENT',
npm ERR!   path: 'C:\\Users\\andrew\\AppData\\Roaming\\nvm\\v0.8.0\\node_modules\\npm\\man\\man1' }
npm ERR! You may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR<EMAIL_ADDRESS>
npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js"
npm ERR! cwd C:\Users\andrew\src\node-ios7crypt
npm ERR! node -v v0.8.0
npm ERR! npm -v 1.1.32
npm ERR! path C:\Users\andrew\AppData\Roaming\nvm\v0.8.0\node_modules\npm\man\man1
npm ERR! code ENOENT
npm ERR! message ENOENT, readdir 'C:\Users\andrew\AppData\Roaming\nvm\v0.8.0\node_modules\npm\man\man1'
npm ERR! errno 34
npm ERR! 34 errno
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     C:\Users\andrew\src\node-ios7crypt\npm-debug.log
npm ERR! not ok code 0

System:

nvm-windows 1.1.1
Windows 10 Professional x86_64

Since these are version-specific, I believe the problem is in the downloaded npm/node installation files, not within NVM4W. I believe the may have been patched after the binaries were released, because building from source works with npm for these versions of node.
That said, I don't have time to cherry-pick through versions to rebuild/manage... and NVM can't rely on the end user having all of the dependencies required to build from source. I'll leave this open for investigation. If someone comes up with a clever solution, I'd certainly accept a PR.

I don't think that NPM Was patched after the binaries were released. You get the same error if you reinstall NPM from the repository directly, pointing to a tag. For example, on Node 0.7.9 (Yes, I'm using an ancient version at the moment.) which comes with NPM 1.1.23, you can reinstall it using
npm install -g git://github.com/npm/cli#v1.1.23

Installation then works fine, but you get the error if you try to run npm --help after that. So it appears that they were built using some kind of default, built in process with NPM that generates a broken install, rather than however you were building it.

Closing due to age.


任勇闯week1 finish

What problem does this PR solve?
这是任勇闯week1作业的总结，包括mysql、mongodb、redis、janusgraph的实验完成记录
What have you done or changed in this PR?
提交week1作业
What test did you complete before submitting the PR?
提交wee1作业

What problem does this PR solve?
这是任勇闯week1作业的总结，包括mysql、mongodb、redis、janusgraph的实验完成记录
What have you done or changed in this PR?
根据评论修改小部分内容
What test did you complete before submitting the PR?
提交wee1作业


Minor tweaks to ResultItem component

... to be styled a bit better and not hardcode the right-aligned text type as a duration.

@reviewbybees esp. @sophistifunk @i386

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

LGTM 💯


Prominently display hash id

The hash id is not displayed to the user, but it is actually quite important because it is the Id they will use to execute the analysis. Let's display this ID to users relatively prominently (if we can find a nice place for it), or at least when the analysis becomes compiled under "Status'

For now I can add it right next to the lock icon.

cool. also would be cool to display it in the browser (when you can see multiple analyses)


Fix for error on second 'disable'

When adding a 'disable' instance action on a button, it is possible to disable a module twice in a row.
The second time throws an error on already deleted objects.

While this prevents errors on a double 'disable' of the qlab-advance module, the way modules are created can't prevent a double 'enable'.


lax.while_loop within jax.disable_jit() should not silently fall back to the primitive version.

https://github.com/google/jax/blob/b43ca61a93aec9a638b5fd6b04518869d45201aa/jax/_src/lax/control_flow.py#L279-L288
It should emit a warning or raise an error.

Can you say more about why you think the behavior is problematic?

Okay. I don't really think this behavior is a bug, thus I use enhancement label.
But I think a good program should not surprise users, i.e. users should be informed if anything doesn't behave as expected, especially when jax.disable_jit is intended for debugging.
For example, a user may assume that within jax.disable_jit, any "memory leak" should have nothing to do with jit cache, and doesn't realize the "memory leak" is actually not a leak but a cache.

Sure.
Actually it isn't a memory leak, but a cache. (the number of live buffers will stop increasing at 2048)
import jax
from jax import lax
from jax import numpy as jnp

def f(max):
    def cond(val):
        return val < max

    def body(val):
        return val + 1
    return lax.while_loop(cond, body, 0)

def print_num_live_buffers():
    bs = jax.lib.xla_bridge.get_backend().live_buffers()
    print(len(bs))

for _ in range(3):
    x = jnp.full((), 2)
    f(x)
    print_num_live_buffers()

Out:
1
2
3

disable_jit works:
import jax
from jax import lax
from jax import numpy as jnp

def f(max):
    def cond(val):
        return val < max

    def body(val):
        return val + 1
    return lax.while_loop(cond, body, 0)

def print_num_live_buffers():
    bs = jax.lib.xla_bridge.get_backend().live_buffers()
    print(len(bs))

for _ in range(3):
    x = jnp.full((), 2)
    with jax.disable_jit():
        f(x)
    print_num_live_buffers()

Out:
1
1
1

disable_jit silently doesn't work:
import jax
from jax import lax
from jax import numpy as jnp

@jax.vmap
def f(max):
    def cond(val):
        return val < max

    def body(val):
        return val + 1
    return lax.while_loop(cond, body, 0)

def print_num_live_buffers():
    bs = jax.lib.xla_bridge.get_backend().live_buffers()
    print(len(bs))

for _ in range(3):
    x = jnp.full(1, 2)
    with jax.disable_jit():
        f(x)
    print_num_live_buffers()

1
2
3

@jakevdp friendly ping.
and WDYT about:
https://github.com/google/jax/issues/9714#issuecomment-1079405996

But there may be an enhancement to have a more flexible cache.

Would it be better to raise a warning or error here?

I think I'm still confused about what this issue is proposing. Are you saying we should not catch the error here? https://github.com/google/jax/blob/fe035f56fcd68be88999c03d283a079165720d97/jax/_src/lax/control_flow.py#L285-L288

@jakevdp Actually I want to re-raise some warning here, e.g. log the comment to stderr.


Upgrade torch to 1.13.0

Describe the issue
Let's upgrade to torch 1.13.0 (and to 1.13.1 as soon as it is released) to prepare for speed improvements coming with version 2.0.
@mayankjobanputra tracked changes between 1.13.1 and 2.0. It seems that the changes from there aren't big. If we upgrade to 1.13 now it will hopefully allow us to make the jump to 2.0 quickly.
Additional context
Add any other context about the problem here.

In case someone is interested in reading further about torch-2.0 and torch-1.13,
Here is nice FAQ: https://pytorch.org/get-started/pytorch-2.0/#faqs

Sorry, let's track this in the Haystack repo instead: https://github.com/deepset-ai/haystack/issues/3683


Breaking change in 6.7.0: Saml2AuthenticationContext.DeclarationReference no longer allows null values

See https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/commit/0567929e7c7f4a299925f16a26d43ad5f8c60dc1#diff-d904bfa7b70e16ce90571f9a418a9362L123-L128, from #1458.
Even if this is intentional (which I'm not sure about, given that the previous version explicitly allowed nulls), 6.7.0 should be retracted and republished as 7.0.0 to be semver-compliant (as recommended by your own docs: https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/versioning).
/cc @catn8r

@teozkr the logic was that setting the value to null indicated an error.  The issue came to light when we realized the the default constructor would just fail.
It may be best, in this case to move back to the original case where the value 'value' is checked only when non-null and release 6.7.1.
I would rather roll back that than move to 7.x.
Does that make sense to you?

Sounds good to me.

@teozkr cool, will make that happen.

@teozkr we dropped 6.7.1 with this rolled back. We will de-list 6.7.0.

Thanks!

@teozkr thank you! As our SDK is used by other SDK's and used by other SDK's ...
These type of breaks cause issues for users and we want to avoid that.
We as a team have realized that when we miss something like this, we have to leave it as is.


fix(uiSelectController): invoke onRemove callback method for single s…

…elect on clear selection
Closes #1225

Are we waiting an anniversary for this to be solved? It's really annoying there is no way to know when clear is called...


[5.2] BelongsToMany : fix pivot timestamps docblocks.

Fix pivot timestamps docblocks for \Illuminate\Database\Eloquent\Relations\BelongsToMany::$pivotCreatedAt and \Illuminate\Database\Eloquent\Relations\BelongsToMany::$pivotUpdatedAt.
Note: these were added in #8715

Please send to 5.1.


[ALLUXIO-1718] Delete block metadata when a file is deleted.

https://tachyon.atlassian.net/browse/ALLUXIO-1718
Currently the block metadata is not deleted when a file is deleted, and therefore block master regards the blocks as lost. This handling slows the system down, because the lost block will trigger lost file detection, which will in turn lead to a FileNotFound exception in inodetree look up.
Therefore, we should distinguish between freeing and deleting files in Alluxio.

@yupeng9 @gpang

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8642/
Test PASSed.

Merged build finished. Test PASSed.

LGTM. Thanks for the bug fix!

I left a few small questions/comments. Thanks!

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8664/
Test FAILed.

Thanks @gpang, updated, can you PTAL?

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8665/
Test PASSed.

Updated and added comment for the different logic between free and delete.
PTAL.
Will add integration tests for this in a following PR.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8667/
Test FAILed.

Jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8669/
Test PASSed.

LGTM


Setting OMP_DYNAMIC=true ruins training on TF-MKL

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): no
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Debian
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: NA
TensorFlow installed from (source or binary): source
TensorFlow version (use command below): git
Python version: 3.9
Bazel version (if compiling from source): 4.2.1
GCC/Compiler version (if compiling from source): 11
CUDA/cuDNN version: NA
GPU model and memory: NA

Describe the current behavior
Some background: I notices a big (several times) time difference between TF-Eigen and TF-MKL. With Eigen being faster. Trying to tune MKL to better performance I experimented with OMP environment variables.  While I was able to get much faster times with TF-MKL, I discovered that the convergence is ruined (the same code does not converge anymore). It seems that the offensive flag is OMP_DYNAMIC=true
Just to give some numbers, running with and without the variable set:
OMP_DYNAMIC=true ./demo.py

Epoch 1/100
   1020/Unknown - 37s 36ms/step - loss: nan - accuracy: 0.0928

And without it:
./demo.py
Epoch 1/100
   1003/Unknown - 112s 111ms/step - loss: 12.1739 - accuracy: 0.9124

Note how much faster the first run is (37ms vs 111ms). However, its accuracy and loss are much worse. At some point, the loss becomes NaN...
Describe the expected behavior
Convergence should not be affected by OMP flags.
Contributing

Do you want to contribute a PR? (yes/no): no
Briefly describe your candidate solution(if contributing):

Standalone code to reproduce the issue
Unfortunately it is not easy to provide a short code that can reproduce the problem. I hope the developers would be able to run some internal tests.

@vpirogov can you please have a look at this.
Thanks.

Some additional info (MKL_VERBOSE=1) that looks suspicious.
OMP_DYNAMIC=true MKL_VERBOSE=1 ./demo.py

MKL_VERBOSE oneMKL 2021.0 Update 3 Product build 20210617 for Intel(R) 64 architecture Intel(R) Advanced Vector Extensions 2 (Intel(R) AVX2) enabled processors, Lnx 3.10GHz lp64 intel_thread
MKL_VERBOSE SDOT(2,0x55c50c00b6e0,1,0x55c50c00b6e0,1) 1.24ms CNR:OFF Dyn:1 FastMM:1 TID:0  NThr:4
OMP: Error #15: Initializing libiomp5.so, but found libomp.so already initialized.
OMP: Hint This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://www.intel.com/software/products/support/.
Fatal Python error: Aborted

Preloading Intel's libiomp5.so (via LD_PRELOAD)  removes the error of two omp libraries loaded, but does not solve the main issue with poor convergence.

@eli-osherovich, based on the messages it looks like your TF build has two OpenMP libraries linked, as the message indicates this may (and usually does) lead to nasty consequences. How do you build Tensorflow?
+@agramesh1

Thanks @vpirogov, @agramesh1
I use the standard building procedure:
bazel build --verbose_failures  --config=nogcp --config=nonccl  --config=noaws --config=nohdfs --config=mkl  -c opt --copt=-march=native --copt="-O3" -s //tensorflow/tools/pip_package:build_pip_package

Is it really two omp libraries? Since preloading Intel's libiomp.so does not solve the problem. I also tried to set KMP_DUPLICATE_LIB_OK, but it does not help. Namely, the command below still produces very poor convergence.
KMP_DUPLICATE_LIB_OK=TRUE OMP_DYNAMIC=true MKL_VERBOSE=1 ./demo.py

@vpirogov , @agramesh1
The issue is reproduced with Intel's TF (installed in a clean conda environment)
This is definitely a bug.

hi @eli-osherovich, is it possible to share your demo.py with us to properly investigate the issue?

@preethivenkatesh  I can share with specific people from Intel/Google.

Thanks, @preethivenkatesh , unfortunately, after a long discussion, I cannot release our company's code.

Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space.


[Clarification] Skipped slots in /eth/v1/beacon/blocks/{block_id} endpoint

Should skipped slots return a 404 in the /eth/v1/beacon/blocks/{block_id} endpoint? In Lighthouse we return information about the most recent non-skipped slot presently.  I don't see it explicitly in the spec.
Relevant lighthouse issue: https://github.com/sigp/lighthouse/issues/2186

For the record Teku will return a 404 in this case.
I dislike it being a 404 though as that suggests the user has made a mistake and it becomes impossible to tell if the block didn't exist or if you just got a part of the URL wrong (most often for me /block/ instead of /blocks/).
Might be too invasive to change now but I'd have gone with something like No Content which confirms we understood the request, found the slot you were asking about but didn't have any block there.

I dislike it being a 404 though as that suggests the user has made a mistake and it becomes impossible to tell if the block didn't exist or if you just got a part of the URL wrong (most often for me /block/ instead of /blocks/).

Agreed. Something else that's worth distinguishing between is:

There is no block at this slot
The node did a weak-subjectivity start and has not yet synced back this far.

Might be too invasive to change now but I'd have gone with something like No Content which confirms we understood the request, found the slot you were asking about but didn't have any block there.

Agree for both points.

A more general comment, but does it make sense to start a v2 version of the API that contains enhancements such as those suggested above, as well as the alterations required for HF1?  The structural items such as this can be handled now, and those that are dependent on the structures and processes in HF1 follow on afterwards.
Main reason is that I'd hate for solutions like the above to be unimplemented, but it appears to be generally felt that v1 is now final so cannot accommodate such enhancements.

Adding proper response message and error code to 404 response to indicate whether it's a skip slot or simply node doesn't have it would be more appropriate?

Adding proper response message and error code to 404 response to indicate whether it's a skip slot or simply node doesn't have it would be more appropriate?

As per @ajsutton , I think 204 No Content would be ideal. It could be accompanied with a message to distinguish between @paulhauner's scenarios.
4xx codes indicate a client error, but it's not an error to request info about a skip slot (imo).

This is older, so in current context it sounds like what we want is:

add 204 to /eth/v2/beacon/blocks/{block_id}
add 204 to /eth/v1/beacon/blinded_blocks/{block_id}

and

fetch block_id and not found == 204 response, this might be a slot number or a root realistically
invalid block_id like foo would remain a 400...

QUESTIONS:

also add 204 to: /eth/v1/beacon/blocks/{block_id}/root?
also add 204 to: /eth/v1/beacon/blocks/{block_id}/attestations ?
does this extend to /eth/v1/beacon/headers/{block_id}?


Error plotting single setup animated mode shapes

Describe the bug
Hi there. I hope you're having a good week. It's just that when I ran the second example, Example2.ipynb, it was not able to plot the animated mode shapes as was expected.
To Reproduce
Just run the Example2.ipynb
Expected behavior
In previous versions this was not an issue and mode shapes were plotted accordingly.
Desktop (please complete the following information):

pyoma2 version: latest
OS: Windows 11
Version 24H2

Additional context or possible solutions
This is the message I received:
Pali_ss.anim_mode_geo2(algo_res=ssicov.result, mode_nr=1, scaleF=3)
Traceback (most recent call last):
Cell In[4], line 1
_ = Pali_ss.anim_mode_geo2(algo_res=ssicov.result, mode_nr=1, scaleF=3)
AttributeError: 'SingleSetup' object has no attribute 'anim_mode_geo2'
also when plotting the mode shapes the following warning persist:
pyoma2\functions\gen.py
FutureWarning: Downcasting behavior in replace is deprecated and will be removed in a future version. To retain the old behavior, explicitly call result.infer_objects(copy=False). To opt-in to the future behavior, set pd.set_option('future.no_silent_downcasting', True)
df_phi_map = sens_map.replace(mapping).astype(float)

Hi @Ayubirad, so the rename of method from anim_mode_g2 to anim_mode_geo2 is still to be released (see the changelog CHANGELOG.md)
I guess somehow you are using the Example script from the main branch and not from the last v1.0.0 release tag.

Exactly! I used pip install pyOMA-2, please would you tell me what command should be used to install v1.0.0 of the package?

Yes it is correct, you installed last released version that is v1.0.0 so here you find the corresponding code of that version (Examples are not included in the downloaded package, so copy them from the source code of the relative tag linked here v1.0.0


ToTestWellFormattedTests.cs:40: 60m/DEV Implement rule:...

The puzzle 5-de36cb8b from #5 has to be resolved:
https://github.com/DenisZhukovski/ObjectToTest/blob/4384f5ace376f98c7be30409f039f16cc4891621/tests/ObjectToTest.UnitTests/ToTestWellFormattedTests.cs#L40-L40
The puzzle was created by Denis Zhukovski on 28-Nov-22.
role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 5-de36cb8b has disappeared from the source code, that's why I closed this issue.

@0pdd 10 puzzles #150, #151, #152, #153, #154, #155, #156, #157, #158, #159 are still not solved.

@0pdd 9 puzzles #150, #152, #153, #154, #155, #156, #157, #158, #159 are still not solved; solved: #151.

@0pdd 10 puzzles #150, #152, #153, #154, #155, #156, #157, #158, #159, #168 are still not solved; solved: #151.

@0pdd 9 puzzles #150, #152, #153, #154, #155, #156, #157, #158, #159 are still not solved; solved: #151, #168.

@0pdd the puzzle #152 is still not solved; solved: #150, #151, #153, #154, #155, #156, #157, #158, #159, #168.


Deprecate ignore_treesitter as a global option, since you can just handle it through keybindings

Removed ignore_treesitter from README to discourage its use.

Comment added: https://github.com/andrewferrier/debugprint.nvim/issues/25#issuecomment-2081407774


Fix/union near miss

Lots of fixed tests and additional tests. When calculating intersections, the direction of the intersection (path moving into other path, or moving out of other path, or tangent to path) is now tracked. a path moves into the other path if it's tangent is to the right, out of the path if it moves left, and tangent otherwise.
also made some changes to the ClippingExampleApp. copy any two paths you're debugging into the debug1 and debug2 methods, and then run the app. can hold down a finger or click to zoom, and can swap between the different algorithms.
there were also quite a few tests that i'd never really defined correct behavior for. I've moved these failing tests to MMClippingBezierTodoTests to fix later. this way, any changes we make we can easily see new failed tests that are not in MMClippingBezierTodoTests and make sure no new failed tests slip through.

closing - wrong repo merge


TypeScript compiler gives incorrect error for large extension chain

TypeScript Version:  1.8.10
Code
export class BaseModel
{
    public someBaseModeloMethod(): void { }
}

export class BaseView
{
    public someBaseViewMethod(): void { }
}

export class CollectionView<TChildView extends BaseView, TModel extends BaseModel>
    extends BaseView
{
    public someCollectionViewMethod(): void { }
}

export class ItemView<TModel extends BaseModel>
    extends BaseView
{
    public setItem(model: TModel): void { }
}

export interface IGridView<TChildView extends ItemView<TModel>, TModel extends BaseModel>
    extends CollectionView<TChildView, TModel>
{
    someGridViewMethod(): void;
}

export class GridView<TChildView extends ItemView<TModel>, TModel extends BaseModel>
    extends CollectionView<TChildView, TModel>
    implements IGridView<TChildView, TModel>
{
    public someGridViewMethod(): void { }
}

function bind<TInterface>(key: string, implementation: new (...args: any[]) => TInterface) {
    // do some bindings here
}

bind<IGridView<ItemView<BaseModel>, BaseModel>>("IGridView", GridView);

Expected behavior:
The code should compile correctly, because GridView is a constructor for an IGridView<ItemView<BaseModel>, BaseModel>
Actual behavior:
The GridView part of the final line (bind statement) gives me the following error:
TS2345 Argument of type 'typeof GridView' is not assignable to parameter of type 'new (...args: any[]) => IGridView<ItemView<BaseModel>, BaseModel>'.
	Type 'CollectionView<any, any>' is not assignable to type 'IGridView<ItemView<BaseModel>, BaseModel>'.
		Property 'someGridViewMethod' is missing in type 'CollectionView<any, any>'.

As you can see, it is expecting someGridViewMethod to be on CollectionView. However, GridView extends CollectionView, so why is it expecting to find GridView methods on the CollectionView class?

I've updated my question - this works fine in 2.0.3 but not in 1.8.10.

Seems to have been fixed


CCIP-4474 manual exec lbtc

Add lbtc manual exec feature.
If destTokenData is more than 32 bytes - attestation is disabled onchain
else - call lombard attestation api for a proof and include it as offchain token data

Can you add a CHANGELOG entry, please?


DS-4006: Embed membership groups on EPerson REST object

This is a fix for https://jira.duraspace.org/browse/DS-4006. This also relates to https://github.com/DSpace/dspace-angular/issues/292.
This is still work in-progress as there still seem to be some issues with the link values. But some early testing can already be done.

The relations section looks good after all. So this is ready for review and testing.

I tested your PR with our current master to see if DSpace/dspace-angular#292 has been resolved. Unfortunately there's still an issue with parsing the Groups. Not just EPersons have embedded Groups, but Groups themselves also have embedded Groups. These last ones are not part of the _links section of Groups yet, which results in the same issues in the frontend as before.

Hi @LotteHofstede, I've added specifc checks that test your requirement, see the changes in GroupMatcher
It seems that your issue is fixed now. Can you please retest to see if this fixes the problems you encountered on the Angular side?

Hi @LotteHofstede, did you already have some time to look at this?

Hey @tomdesair
I had tested your changes against the UI last month, but because I ran into some issues forgot about it. After testing it a second time, I found out the remaining issue lies in the Angular frontend, not in your PR.
@tdonohue, I will create a PR with some small fixes on the Angular side to make sure users can log in properly when this PR is merged. I would suggest to merge both PRs simultaneously to make sure everything still works as expected.


Docs: When the API references will be added?

What is the improvement or update you wish to see?
Hi, when the turbopack will be ready to use as a standalone bundler outside nextjs? I have project that use esbuild to bundle, but since esbuild don't support HMR, I'm thinking to move to turbopack.  Thanks!
Is there any context that might help us understand?

Does the docs page already exist? Please link to it.
No response

Today, the focus for Turbopack is on being an excellent bundler for the Next.js Compiler.
We're getting close to a stable release for the development server and are beginning to put thought into Next.js builds.
Once those things are done, we will take a step back and look at the needs of users and the larger ecosystem to see what next steps will be.


Update 2.15.x branch

Backport a number of recent commits to 2.15.x in preparation for backporting #1591
Most of these backports are pre-commit updates.
#1518 resulted in a large number of changes, primarily removing # noqa that are no longer needed.
#1528 and #1467 removed astropy and specutils from downstream testing
#1532 fixes a test that relied on astropy.io.misc.asdf
#1556 drops python 3.8 support
#1568 increases the minimum numpy version
#1567 #1585 #1611 apply some docs fixes
the test_version_map_support test was dropped, this change occurred in main in #1474 but we likely don't want to backport the other changes in that PR
One relatively major change is the inclusion of #1605 (changing numpy scalar handling), this is needed to fix the devdeps jobs but if we'd prefer to not backport it we can drop this commit
Following the merge of this PR the changelog on the main branch will need to be updated to reflect the changes included here (and in 2.15.1).
Some notes on CI failures:

#1610 (included in the backports) removed the label checker CI job (which will still fail as it appears to run from the destination branch)
codecov diff failures are unavoidable as they failed for #1518 as well

@eslavich Do you have a chance to give this a quick sanity check? I'm inclined to wait until #1609 is approved and merged, then add that to this PR, update 2.15.x, then release 2.15.1 but I'm open to suggestions. Thanks!

Roman regtests show no new errors: https://plwishmaster.stsci.edu:8081/blue/organizations/jenkins/RT%2FRoman-devdeps/detail/Roman-devdeps/360/tests

jwst regtests passed with no errors: https://plwishmaster.stsci.edu:8081/blue/organizations/jenkins/RT%2FJWST-Developers-Pull-Requests/detail/JWST-Developers-Pull-Requests/838/pipeline/202


Add file cache of DTFile

What problem does this PR solve?
Issue Number: ref #6827
What is changed and how it works?
This PR add file cache of dtfile in cloud native mode:

Cache granularity: column file.
Cache missing: if get column file from file cache failed, the read request is read directly from S3, and the file cache asynchronously downloads the corresponding file from the background and caches it.
Cache evicting:

Distinguish cache priority according to file type. The larger the file type, the lower the priority.
Each type of file is maintained in a LRUFileTable to facilitate access to files that have not been used recently.
Basic eviction idea:

First, try to evict files which not been used recently with the same type. => Try to evict old files.
Second, try to evict files with lower priority. => Try to evict lower-priority files.

Add configuration storage.remote.cache.dtfile_cache_min_age_seconds that prevent files being read within dtfile_cache_min_age_seconds seconds from evicting by files with the same priority. Default value is 1800.

TODO:

[ ] Pass file size and data type to file cache. (Currently, we use a estimate size to reserve space. This can cause some troublesome problems.)

Check List
Tests

[x] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-unit-test

/merge


"istioctl x analyze" show name.namespace style origins

Resolves https://github.com/istio/istio/issues/17924 by outputting analysis problem origin locations as <type> <name>.<namespace> instead of <type>/<namespace>/.<name>.

@esnible: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_istio
e7a935600b0223974bb435c882a2b74cbac88787
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
aab5e91e26bc5667fe4df9322c9afe3d1313e6fd
link
/test integ-new-install-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@esnible: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
aab5e91e26bc5667fe4df9322c9afe3d1313e6fd
link
/test integ-new-install-k8s-tests_istio

integ-mixer-k8s-tests_istio
aab5e91e26bc5667fe4df9322c9afe3d1313e6fd
link
/test integ-mixer-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/cherry-pick release-1.4

@nrjpoddar: new pull request created: #18168

In response to this:

/cherry-pick release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Introduce bal graph command

Description:
https://github.com/ballerina-platform/ballerina-spec/issues/928

AFAIU, the purpose of this command is to be able to troubleshoot package resolution issues. The normal behavior of a user would be that he/she executes bal build/run/test and then if the command fails, he would run bal graph to see if there is an issue with the resolution.
As per the last meeting, we decided the following:
i. Introduce bal graph - implementation is to run upto resolution, print the graph, exit
ii. Remove the hidden="true" for --dump-graph, --dump-raw-graphs in bal build run and test
The reason to provide the 2nd option is that, if there are code generators and modifier plugins engaged, then the resolution is run twice and there can be changes to the dependencies in the 2nd run. So the bal graph would not produce the correct result for this case.
So I see two options to go forward with this:

Change the implementation of bal graph to be able to reproduce the same resolution outputs as the bal build/run/test

This means we should run compiler extensions in bal graph command and generate the graphs before and after
Since many packages are using code generators and modifiers now (e.g. http, graphQL, websub, log, azure_functions) the probability of the bal graph command being relevant is quite low

Drop i and implement only ii

The graph will be dumped even if the compilation fails

IMO, approach 2 is would be enough since the purpose of the user is to check why the build/runtime fails and the flag can be a option that can be passed to troubleshoot. @sameerajayasoma @hevayo WDYT?

I agree that we should dump the final graph for every execution of bal graph command.
Even though the main purpose of this utility is to troubleshoot dependencies resolution related problems, there can be other usages such as analyzing and visualizing the dependencies of a package. We discussed having such a view in Choreo.
I prefer to have a separate command. This gives us the ability to customize the graph output, and change representations to help developers to identify issues easily. See https://doc.rust-lang.org/cargo/commands/cargo-tree.html and https://go.dev/ref/mod#go-mod-graph

We discussed and agreed on the following:

Introduce PackageResolution.dumpGraph(PrintStream)
Remove the System.out from the PackageResolution and maintain a custom stream to dump all graphs
When the API user calls PackageResolution.dumpGraph(PrintStream), we write the content from the resolution stream to the user's stream.


ENH: Automate build

Closes #76
Nightlies are being pushed to:
https://pypi.org/project/tfa-nightly/
Will set up a nightly cron once this is merged into master. This is also a big help for the 0.4 release which should be happening shortly after TF2 release candidate

I'll also be adding a RELEASE.md in tensorflow/community with the now manageable steps needed for a release

@WindQAQ great question. So we can create a python3.7 for macos right now, but py37 will not install on the custom-op docker image for ubuntu 14.04. We could patch the docker image similar to how SIG-IO has done but I wanted to stick with the custom-op image provided so if there is any ABI issues etc. then we will be able to push that issue upstream.
SIG-Build has mentioned they will be providing build environments which will solve #75 and #119 which is great and from doesn't seem to be too far away.


Not able to perform real time VAD detection

I have a system where I am getting audio in realtime. I want to perform VAD on it to determine if the audio being sent is speech or not. For doing that I have written the below code -
import torch

torch.set_num_threads(1)
USE_ONNX = False # change this to True if you want to test onnx model
self.model, utils = torch.hub.load(repo_or_dir='snakers4/silero-vad',
                            model='silero_vad',
                            force_reload=True,
                            onnx=USE_ONNX)

(get_speech_timestamps,
save_audio,
read_audio,
VADIterator,
collect_chunks) = utils

self.vad_iterator = VADIterator(self.model)

speech_decoded = base64.b64decode(text_data_json.get("media").get("payload"))
print(self.vad_iterator(speech_decoded, return_seconds=True))
print(self.model(speech_decoded, 8000).item())

When I perform the first print, I am getting the following error - Audio cannot be casted to tensor. Cast it manually
Can someone help me fix this error? speech_decoded is basically the audio received in a decoded base64 string.
UPDATE:
I changed the implementation to the below code:
import torch

torch.set_num_threads(1)
USE_ONNX = False # change this to True if you want to test onnx model
self.model, utils = torch.hub.load(repo_or_dir='snakers4/silero-vad',
                            model='silero_vad',
                            force_reload=True,
                            onnx=USE_ONNX)

(get_speech_timestamps,
save_audio,
read_audio,
VADIterator,
collect_chunks) = utils

self.vad_iterator = VADIterator(self.model)

speech_decoded = base64.b64decode(text_data_json.get("media").get("payload"))
audio_int16 = np.frombuffer(speech_decode, np.int16)
audio_float32 = self.int2float(audio_int16)

print(self.vad_iterator(audio_float32, return_seconds=True))
print(self.model(audio_float32, 8000).item())

On running the above code I am getting the below error
The following operation failed in the TorchScript interpreter.
Traceback of TorchScript, serialized code (most recent call last):
  File "code/__torch__/vad/model/vad_annotator.py", line 98, in forward
    _16 = torch.gt(torch.div(sr1, (torch.size(x2))[1]), 31.25)
    if _16:
      ops.prim.RaiseException("Input audio chunk is too short", "builtins.ValueError")
      ~~~~~~~~~~~~~~~~~~~~~~~ <--- HERE
    else:
      pass

Traceback of TorchScript, original code (most recent call last):
  File "/home/keras/notebook/nvme_raid/adamnsandle/silero-models-research/vad/model/vad_annotator.py", line 364, in forward

        if sr / x.shape[1] > 31.25:
            raise ValueError("Input audio chunk is too short")
            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ <--- HERE

        return x, sr
builtins.ValueError: Input audio chunk is too short

The length of the audio which I am sending is of 20ms. Is this not supported? If not, then are there any workarounds?
I tried concatenating multiple audio packets so that the duration increases but then I get the below error -
Error while processing frame

@snakers4 any sort of help for the above issue would be appreciated

The error message is clear enough,in your case,if you want to use this code self.vad_iterator(audio_float32, return_seconds=True) you better change to self.vad_iterator(audio_float32, return_seconds=True,sampling_rate=8000) and make sure len(audio_float32 ) == 256 and evrything would be fine then. Little advice: you should concatenate your payload first and iterate them 256 by 256

@Simon-chai, thanks for the help. I will try to implement this and get back to you if I face any difficulties. Till then, I am closing this issue.


Update cypress version

Signed-off-by: Maggie Chen<EMAIL_ADDRESS>https://github.com/open-cluster-management/backlog/issues/16681

/test e2e-cluster

/cc @KevinFCormier @fxiang1

/lgtm


Added 2 options:

select_all_onclick - if true - it select all text inside field, when you click on it. It helps if u preffer enter date by hand.
hide_onenter - hides date picker if you press Enter, while cursor inside input box

Changing default date format is not a good idea, many people may rely on it, the same about default value of hide_on_select
and 3) Can be really easily implemented without changing plugin's code at all

Since your code doesn't use any internals of plugin there is really no need to accept this as built-in feature. There are many of such features that can be potentially used, but they are not so popular to worth increasing codebase size.


Lottery Smart Contract - Enter Function Updated!

Hey Jonathan Spruance!
I was watching your lottery smart contract video. And I noticed why you were not able to test with 0.1 ETH. As you didn't add = with > you were not able to put 0.1 ETH. I updated the Github repo. I hope this small contribution of mine, helps your community :)
Thanks,
AB Dee.

Sorry for the delay and thanks for the contribution!


Move phone number to after email

Is this referring to the dashboard under the Account Info tab?

This is for the admin user table.


Upgrading Highcharts

Upgrade to Highcharts 6
Moving from gevgeny/angular2-highcharts to cebor/angular-highcharts .

Completed by 360c7c3


bug: links don't work in feed posts

Describe the bug
Pressing on a feed post always opens the thread, even if you're trying to press a mention or link
To reproduce
Try and press on a mention or link on the skyline
Additional information
@hs4man21 do you know if this might be related to some of the work you've been doing?

Fixed with latest patch


flow: introduce simplectype type creator.

Changes since v1:

"samples/flow: fix API so they compile and run" was merged to master.
removed type checking functions, added a SOL_TYPE_CHECK() macro instead
fixed style issues (forgot to run check-style.py)

LGTM

merged.


Fixed Flaky Test in jackson-databind

Created this PR to fix flaky test SimpleFilterProviderTest.testAddFilterLastOneRemainsFlip.
The test can be found here.

How was this test identified as flaky?
This test was identifies as flaky by using an open-source research tool named NonDex which is responsible for finding and diagnosing non-deterministic runtime exceptions in Java programs.

Why does the test fail?
When jsonString is created using the bean object, the order of elements in the jsonString is not deterministic. The test assumes that the jsonString will be {"[a":"1a","b":"2b]"}. However, the order of elements in the jsonString is shuffled sometimes, due to which it is {"[b":"2b","a":"1a]"} sometimes instead of {"[a":"1a","b":"2b]"}. Due to this, the test fails some times.

How I fixed the test?
I fixed the test by creating map objects from the two json strings that we were being compared. Then, I compared the map objects in the assertion. This ensures that the two jsons are equivalent, irrespective of the order of elements within them.

You can run the following command to run the test using the NonDex tool:
mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -Dtest=com.fasterxml.jackson.databind.ser.filter.SimpleFilterProviderTest#testAddFilterLastOneRemainsFlip

Test Environment:
java version <IP_ADDRESS>
Apache Maven 3.6.3

Let me know if this fix is acceptable
Thank you!

The fix looks ok to me and feel free to open PRs without going through me since it's very close to the ddl already.
One general suggestion for the description: you might want to avoid using the word "flaky" since some developers don't like this phrase. Try to use phrases like "nondeterministic" or directly describe the un-ordered nature of the hashmap.


New BabyBeast Asset and Animations – Fire Theme🔥 (Horse)

Scope
We need to create a new BabyBeast asset with a Fire Theme🔥 for a Baby Horse. The design must maintain consistency, while introducing unique fiery and energetic features.

What is a BabyBeast?
BabyBeasts are designed as cute magical animals with a consistent style: rounded proportions, soft tones, and minimal yet expressive details.
You can use this one as an example of a Fire Theme: Assets/BabySprites/babybeast new dragon.gif

Requirements
Design the Fire BabyBeast🔥:

Use the Assets/BabySprites/babybeast new dragon.gif as a base for style and proportions.
Add fiery features, such as:

Vibrant orange and red tones with glowing gradients. 🔥🟠
Flaming mane and tail. 🐴⚡
Brighter, ember-like hooves. ✨💥

Create Animations:

Idle Animation (breathing):

Gentle movement of the flaming mane and tail, with subtle glowing hooves.

Additional Animations:

Eating animation: Lifting its head with embers flickering around the mouth.
Sleeping animation: Laying down as flames reduce to a soft flicker.
Happiness animation: Energetic galloping in place with flames intensifying briefly.
Bathing animation: Flames interacting with a mist-like water effect.

Maintain Consistency:

Match the proportions, color palettes, and aesthetic logic of the current BabyBeasts.
All animations should feel smooth and aligned with the game’s magical and fiery theme.

How to Implement?

Use any pixel art or sprite animation toolkit of your choice.
Create and animate the Fire BabyBeast (Horse).
Save all assets to the Assets/BabySprites folder in this repository, ensuring proper naming conventions for the files.

Cool Tools to Use

Aseprite: A powerful tool for creating and animating sprites and pixel art.
Piskel: A free online tool for sprite creation and animation.
Feel free to use any toolkit that works best for you.

How to Apply?

Follow the contribution guidelines provided in the README file.
Submit your pull request with the asset and animations in their respective folders.
Ensure all animations are properly tested before submission.

We’re excited to see your contribution! 🐴🔥

I'd like to handle this task.

Can I tackle this one?

To address this issue, I would design a Fire BabyBeast Horse using the dragon asset provided as a starting point, adding a fiery mane, tail, ember-like hooves, and vibrant orange/red tones. Create animations including idle (mane and tail flickering), eating (embers flickering), sleeping (flames reducing), happiness (galloping with intensified flames), and bathing (flames interacting with mist). Ensure consistency with the BabyBeasts style and save all assets in the Assets/BabySprites folder with proper naming conventions.

I would love to take on this issue.

I'd love to give this a go.

Is it okay if I take this?

Can I contribute to this one?
I have a solid background with animation libraries and I implemented the dragon babybeast used here as reference, I will be glad to contribute to this project.

Could I take on this issue?

@Steph3097 hi steph any updates here?

@Steph3097 hi steph any updates here?

@jimenezz22 Hello! I already create the PR, let me know if you have more changes or questions!


Swap JDBC for Arrow ADBC

Leveraging the Arrow ADBC Driver has a number of advantages:

A single, universal driver would replace all existing, proprietary drivers (mssql, postgres...)
Better performance due to not processing each row separately and tapping into pyarrow to avoid serialization/deserialization

Additional context
https://arrow.apache.org/docs/dev/format/ADBC.html
P.S. Please do not attach files as it's considered a security risk. Add code snippets directly in the message body as much as possible.

The implementation for this is in progress for Postgresql (see development branch). However, we are currently blocked by this bug in Pandas: https://github.com/pandas-dev/pandas/issues/57539


Font

I am in Fedora I built from opengl branch & when I run ./target/release/neovide
I got this :
thread 'main' panicked at 'called Option::unwrap() on a None value', src/renderer/fonts/caching_shaper.rs:59:14

Interesting. I think this means that the font set in the vim config (or defaulted to Noto Sans Mono) isn't installed. Do you have a guifont variable set in your vim config? If not, can you try installing Noto Sans Mono font? https://www.google.com/get/noto/

It was my mistake i set guifont and itis working


Can I customize the box when I finish selecting the text? Are there any callbacks for table/picture clicks?

Is there a selectArea for selecting text on macos? Can you open the callback after selecting the text, so that you can customize the pop-up box when selecting the text. Are there any callbacks for table/picture clicks?

1.0.54 introduces `PdfViewerParams.perPageSelectionAreaInjector to customize text selection behavior:
perPageSelectionAreaInjector: (page, child) {
  return SelectionArea(
    contextMenuBuilder: (context, selectableRegionState) {
      return AdaptiveTextSelectionToolbar.selectableRegion(
         selectableRegionState: selectableRegionState,
      );
    },
    child: child,
  );
},

Thanks!

You can inject any widget other than SelectionArea so that do some special trick.
But I understand that it is just the first step and could not customize everything (I don't know what should be customizable) so far.


Use logging for apphook reload

There are some places in the apphooks reload module that use print statements instead of logging.
https://github.com/divio/django-cms/blob/develop/cms/utils/apphook_reload.py#L96
These should use logging instead.
Related to https://github.com/divio/django-cms/issues/5084

Was just about to open a ticket for this. I agree it should use logging as well, but I'd also like to improve what is logged so it's as useful as possible. For instance, it's very unclear why I see this kind of output or what I'm supposed to do with this information:
New revision!!!! RELOAD!
   074c568c-1ce0-49fe-afe2-1027ddcaff0b (<class 'str'>)
-> None (<class 'NoneType'>)

Or:
reverse('my_test_app_view'): Reverse for 'my_test_app_view' with arguments '()' and keyword arguments '{}' not found. 0 pattern(s) tried: []

In the hopes someone can tackle this, here's the explanation:
When an apphook is attached to a page, if the project has the ApphookReloadMiddleware middleware installed, the cms will trigger a reload of the configured url conf module.  This allows the content manager to continue to use the page with the apphook urls already applied.
Without the ApphookReloadMiddleware middleware installed, content managers would not be able to see the attached app until a sys admin restarts the wsgi process.
Example, user attaches the blog apphook to a page called blog.
If ApphookReloadMiddleware middleware is installed, content manager can start adding and editing articles, also the article detail pages would work fine like /en/blog/django-cms-part-1/
If ApphookReloadMiddleware middleware is not installed, content manager can probably add and edit articles via the admin (depending on the app) but if the content manager visits an article detail page (/en/blog/django-cms-part-1/) he'll get a 404 because the url conf module was loaded on memory when the wsgi process first started and so does not know about the article urls.
To manage this, there's a global revision and local revision records.
The global revision is stored in the database and the local one in thread.
The first message:
New revision!!!! RELOAD!
   074c568c-1ce0-49fe-afe2-1027ddcaff0b (<class 'str'>)
-> None (<class 'NoneType'>)

Tells that a new local revision is being created because a change has been detected and so url conf will be reloaded.
After the url conf module is reloaded, it's necessary to trigger a reverse() call in order to make sure django loads all included urls.
The second message:
reverse('my_test_app_view'): Reverse for 'my_test_app_view' with arguments '()' and keyword arguments '{}' not found. 0 pattern(s) tried: []

Simply informs that we've tried to reverse the my_test_app_view url and if threw an error.

I have the same "problem"...
How can I hide this annoying message??
"""
New revision!!!! RELOAD!
8b8be4b3-1fce-469a-bb04-bca63091de22 (<type 'unicode'>)
-> None (<type 'NoneType'>)
"""

This message is very annoying... please hide it soon!! :(

Agreed, stuff like this should be in the debug log, info at worst
It's basically just informing the admin that it's working properly, whereas should only inform them if it's not working properly. If everything logged something on normal operation we would be in trouble!
It detracts from the django cleanliness that I have been enjoying up until now..

I came across this as the message is really confusing, I'm working with a codebase that has some strange corners already and the message coming from djangocms itself is the last thing I expected.

The following PR will fix this issue.

Looks like the only issue it has is a merge issue with the ChangeLog.

@stuaxo fixed, thanks for reporting

Thanks all.


Add option to pass JSON file as configuration to feeder.

I made a change to make it possible to pass a JSON file as argument to the runner/application.  That keeps the shell script to start clean.  This makes it also possible to use a single shell script to start feeders with multiple configurations.

Thanks, I have added a modified change to the noriver branch (next version) https://github.com/jprante/elasticsearch-jdbc/commit/72bd34c484d07b85bb35414a0db43f40b1ebce51
(documentation follows)


Fix position format

This was discovered by using helix, code editor. For reference the issue is here: https://github.com/helix-editor/helix/issues/2029.
In the Position documentation it says:

Position in a text document expressed as zero-based line and zero-based character offset. A position is between two characters like an ‘insert’ cursor in an editor. Special values like for example -1 to denote the end of a line are not supported.

So this is binding it to be 0 if the position - 1 returns less.
I'm not sure this is the only place that the change needs to be done, so I'm open to some guidance so we can make this work as it should.
Thanks!

I'm against meging it in thisf form as it hides the real bug (why position is 0 when it is 1 based).
Furthermore, this is far from covering all the places where it can return invalid results. In fact https://github.com/helix-editor/helix/issues/2029#issuecomment-1093019962 suggests that character can be also negative.
@the-mikedavis @andreicek do you have a repro (or a full LSP protocol message dump) for that issue?

I managed to reproduce the -1 line-number in the test suite: https://github.com/elixir-lsp/elixir-ls/commit/5b0dabc0f7c4e470908fe53ab6612aae076b6565. I'll see if I can come up with a fix 👍

It seems 0 is a legit response, see https://hexdocs.pm/mix/1.13.4/Mix.Task.Compiler.Diagnostic.html#t:position/0

Thanks @lukaszsamson for taking this on!

Thanks @andreicek for the initial work but the problem turned out more complicated


Drag-drop of StructureView node onto empty area throws exception

Version: 0.0.18
Drag-drop of StructureView node onto empty area throws exception

Fixed in 0.0.19 by doing nothing in that case
we could have add though to StructureView a (probably false by default) boolean property to allow switching GUIRoot when we do this action (and reparent the current GUIRoot under the dropped item), but should have event to notify client code about this GUIRoot change


Setup consumer delta dispatching

DL-4165
In this PR we :

Add the necessary data to be able to dispatch triples
Configure the consumer to dispatch the triples in the correct graphs defined by business rules

To do if the logic is validated and when edge cases are handled :

Setup initial sync

@claire-lovisa thanks! A said, based on your work, we migrated the logic to a separate service