Write support

This is a proposal for adding write-support to LDflex.
It requires three new handles:

AdditionHandler: binds to add and addAll.
DeletionHandler: binds to delete and deleteAll.
UpdateHandler (optional): binds to update and updateAll.

Addition
This requires a straightforward handler that intercepts the add and addAll functions
that take one mandatory argument.
Adding a single value:
await user.friends.add('https://rubensworks.solid.community/profile/card#me')

SPARQL:
INSERT DATA
{
  <https://rubensworks.solid.community/profile/card#me> foaf:knows <https://rubensworks.solid.community/profile/card#me>.
}

Adding the first of multiple values:
await user.friends.add(user.friends.friends)

SPARQL:
INSERT DATA
{
  <https://rubensworks.solid.community/profile/card#me> foaf:knows
      <http://example.org/A>.
}

Adding multiple values:
for await (const addedFriend of user.friends.add(user.friends.friends)) {
    console.log(addedFriend)
}

SPARQL:
INSERT DATA
{
  <https://rubensworks.solid.community/profile/card#me> foaf:knows <http://example.org/A>.
}
INSERT DATA
{
  <https://rubensworks.solid.community/profile/card#me> foaf:knows <http://example.org/B>.
}
INSERT DATA
{
  <https://rubensworks.solid.community/profile/card#me> foaf:knows <http://example.org/C>.
}

Adding multiple values in bulk:
await user.friends.addAll(user.friends.friends)

SPARQL:
INSERT DATA
{
  <https://rubensworks.solid.community/profile/card#me> foaf:knows
      <http://example.org/A>,
      <http://example.org/B>,
      <http://example.org/C>.
}

Note: We can not trap = via the proxy (set), as this requires a synchronous operation, and you can not play around with return values.
Deletion
This requires a handler that intercepts the delete and deleteAll functions
that take one optional argument.
Deleting a single value:
await user.friends.delete('https://rubensworks.solid.community/profile/card#me')

SPARQL:
DELETE DATA
{
  <https://rubensworks.solid.community/profile/card#me> foaf:knows <https://rubensworks.solid.community/profile/card#me>.
}

Deleting the first of a list of values:
await user.friends.delete(user.friends.friends)

SPARQL:
DELETE DATA
{
  <https://rubensworks.solid.community/profile/card#me> foaf:knows
      <http://example.org/A>.
}

(maybe this can be done with a DELETE WHERE?)
Deleting a list of values:
for await (const deletedFriend of user.friends.add(user.friends.friends)) {
    console.log(deletedFriend)
}

SPARQL:
DELETE DATA
{
  <https://rubensworks.solid.community/profile/card#me> foaf:knows <http://example.org/A>,
}
DELETE DATA
{
  <https://rubensworks.solid.community/profile/card#me> foaf:knows <http://example.org/B>,
}
DELETE DATA
{
  <https://rubensworks.solid.community/profile/card#me> foaf:knows <http://example.org/C>,
}

Deleting a list of values in bulk:
await user.friends.deleteAll(user.friends.friends)

SPARQL:
DELETE DATA
{
  <https://rubensworks.solid.community/profile/card#me> foaf:knows
      <http://example.org/A>,
      <http://example.org/B>,
      <http://example.org/C>.
}

Deleting first or all possible values:
await user.friends.delete()
await user.friends.deleteAll()

Internally, this corresponds to await user.friends.delete(user.friends) or await user.friends.deleteAll(user.friends), because SPARQL DELETE does not allow blank nodes or variables
Note: We can not trap the delete operator via the proxy (deleteProperty), as this requires a synchronous operation, and you can not play around with return values.
Update
This corresponds to a delete followed by an insert.
This is merely convenience functionality that combines deletion and addition (optimizable with a combined SPARQL query: https://www.w3.org/TR/2013/REC-sparql11-update-20130321/#deleteInsert).
This requires a handler for set and setAll that take one mandatory argument.
Updating a single value:
await user.name.set('Ruben')

Translation:
await user.name.delete() # Delete a single value
await user.name.add('Ruben') # Add a single value

Updating the first of multiple value:
await user.name.set(user.friends.name)

Translation:
await user.name.delete()
await user.name.add(user.friends.name)

Updating multiple values:
for await (const newName of user.name.set(user.friends.name)) {
    console.log(newName)
}

SPARQL:
await user.name.deleteAll()
await user.name.add(name0) # add calls are separated by for-await iterations.
await user.name.add(name1)
await user.name.add(name2)
...

Updating multiple values in bulk:
await user.name.setAll(user.friends.name)

SPARQL:
await user.name.deleteAll()
await user.name.addAll(user.friends.name)

Good stuff, great as starting point for discussions.

Adding the first of multiple values:
await user.friends.add(user.friends.friends)

I don't find this intuitive; to me, the above syntax should be for adding all friends. For adding one friend (not the first BTW, no ordering), I'd say:
await user.friends.add(user.friends.friends.random)

So I'd be against for await and addAll.

Deleting the first of a list of values:
await user.friends.delete(user.friends.friends)

Deleting a list of values in bulk:
await user.friends.deleteAll(user.friends.friends)

I find the duplication confusing. I would propose
await user.friends.random().delete()
await user.friends.delete() // deletes all

Too bad that we cannot do
await delete user.friends

Because the delete trap is supposed to return a Boolean.
That said, we might be able to do it if that Boolean also is a thenable! (untested)

Updating a single value:
await user.name.set('Ruben')

Can we also wire up the following alternative?
user.name = 'Ruben'

Also, there is no such cases as "single value", because anything might have multiple.
How about
user.name.set('Ruben') // removes all names and add one 'Ruben'
user.name.replace('ruben', 'Ruben') // remove all matching names and add one 'Ruben'

Adding the first of multiple values:
await user.friends.add(user.friends.friends)

I don't find this intuitive; to me, the above syntax should be for adding all friends. For adding one >friend (not the first BTW, no ordering), I'd say:
await user.friends.add(user.friends.friends.random)

Sure, that makes sense as well.
On the other hand, this may be confusing, as await user.friends.friends returns only a single value. Perhaps await user.friends.friends.random or await user.friends.friends.random() should be a thing then as well?

So I'd be against for await and addAll.

Agreed. I was just writing out the possibilities :-)
What might be useful though, is to implement addAll like this:
await user.friends.addAll([ 'uri-a', 'uri-b', ... ])

The advantage of this is that a single bulk SPARQL query can be created, instead of having to send one for each addition separately.

await user.friends.random().delete()
await user.friends.delete() // deletes all

👍

Too bad that we cannot do
await delete user.friends
Because the delete trap is supposed to return a Boolean.
That said, we might be able to do it if that Boolean also is a thenable! (untested)

Hmm, maybe, I'll look into that.

Can we also wire up the following alternative?
user.name = 'Ruben'

We have the same problem here as with delete.
The return value of proxy's set should be a boolean value.
Since a regular assignment returns its assigned value, we won't be able to promisify this.
We could definitely support this, but any rejections would be uncaught.
(A babel plugin might be possible here as well though)

How about
user.name.set('Ruben') // removes all names and add one 'Ruben'
user.name.replace('ruben', 'Ruben') // remove all matching names and add one 'Ruben'

👍

On the other hand, this may be confusing, as await user.friends.friends returns only a single value.

Yes, but there's no await in front of it when adding, so I think we're good.

Perhaps await user.friends.friends.random or await user.friends.friends.random() should be a thing then as well?

Definitely; I suggest the former.
The difference being that a for await over random would also only give at most one element.

What might be useful though, is to implement addAll like this:
await user.friends.addAll([ 'uri-a', 'uri-b', ... ])

Possibly, or we could just splat it:
await user.friends.add(...array)

Can we also wire up the following alternative?
user.name = 'Ruben'

We have the same problem here as with delete.
The return value of proxy's set should be a boolean value.
Since a regular assignment returns its assigned value, we won't be able to promisify this.
We could definitely support this, but any rejections would be uncaught.

You just gave me a really interesting idea.
Recall how Node has this thing about uncaught Promise rejections.
What if we similarly allow such sync calls, which indeed have not completed yet, but give the option to manually sync? Example:
// Do data things
data.user.name = 'Ruben';
data.user.brother.name = 'Niels';
data.user.sister.name = 'Muriel';
delete data.user.daughter;

// Wait until all of the above is done
await data.pending;

Above, data.pending is a Promise to an array of results for each of the currently pending operations.
You're free to await or not await it, knowing that if you don't, you might miss completion and/or rejection (and rejections would become global rejection errors).
Additionally, this gives us the possibility of bundling setters internally, and writing them all at once.
Note that, upon accessing data.pending, all of the currently pending promises are returned and then forgotten. For example:
data.user.name = 'Ruben';
data.user.brother.name = 'Niels';
data.user.sister.name = 'Muriel';
const p1 = data.pending;
const p2 = data.pending;
console.log(await p2); // empty array
console.log(await p1); // three items

This allows explicit scoping of pending promises.

Stumbled upon this by accident. Would be great to have it in the official documentation

Ok, I see there is https://github.com/RubenVerborgh/LDflex/issues/10 already :)


'autosub' is not recognized as an internal or external command, operable program or batch file

I have followed the installation but when I try running autosub -h I get the above error. I've already installed ffmpeg and I've added it to the PATH. I've also run pip install autosub. However autosub -h only prints the above error in the terminal. I've also run it on both the windows cmd and bash cmd to no avail.

What OS are you using? If you are using windows, you have to use follow the instructions described in #31.


Single Select / Empty level option is not working as expected

When I select/deselect the 'Single Select' option, the 'Empty Leafs' option also is enabled/disabled.

Fixed in v1.1.5


Refactor element state references

Rather than having multiple state properties attached to the element, I think it would be helpful to keep them all in one object. That should help with debugging, modules don't have to worry about a property namespace, and it's easy to remove the state properties if needed (useful for features I'm working on).

Very nice, I agree.
Will be merged.

This has now been merged to branch 0.4.0.

For the record: The PR is rejected since I want this in branch 0.4.0 (and GitHub does not allow me to change), but your commits has been merged into 0.4.0, as seen here: https://github.com/wnr/element-resize-detector/commits/0.4.0


Update imessage-2fa extension

Description
Resolves an issue where only "read" messages are shown when ignoreRead option is disabled
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@d3chapma https://github.com/raycast/extensions/commit/3938c68ec9733e5d53f7c4f17e274e4290951c37#r134887249


[RHPAM-3689] Add JBPM Cluster jar in Kieserver image

See: https://issues.redhat.com/browse/RHPAM-3689
Main branch
Signed-off-by: desmax74<EMAIL_ADDRESS>Thanks for submitting your Pull Request!
Please make sure your PR meets the following requirements:

[ ] Pull Request title is properly formatted: [RHPAM-XYZ] Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket
[ ] Attached commits represent units of work and are properly formatted
[ ] You have read and agreed to the Developer Certificate of Origin (DCO) (see CONTRIBUTING.md)
[ ] Every commit contains Signed-off-by: Your Name<EMAIL_ADDRESS>- use git commit -s

@spolti main branch


Rename fields -> input_fields to make pydantic happy

Description of changes:
Newer versions of pydantic reserve the name "fields" internally. Rename to input_fields to avoid conflicts.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-183/1 is complete.
Docs are uploaded to http://gluon-ts-staging.s3-accelerate.dualstack.amazonaws.com/PR-183/1/index.html

I think we did similar changes in #108 already.

I think we did similar changes in #108 already.

Good point. These changes are already in so I will close this.


sidebar should not cover the other elements (z-index) in push and slide mode

Steps to Reproduce:

Open this https://codesandbox.io/s/filtering-devextreme-data-grid-6zs9y?fontsize=14
click on "Invoice Number" header filter icon

Results You Received:
filter panels opens in wrong position

Results You Expected:
filter panel opens in correct position
Note:
I solved the issue in my app by adding these to styles
::ng-deep .ng-sidebar.ng-sidebar--opened.ng-sidebar--push,
::ng-deep .ng-sidebar.ng-sidebar--opened.ng-sidebar--slide {
  z-index: 1;
}

I am not sure if that changes is correct, because it was correct if the mode was "over", so that changes only needed for push and slide

There's basically no winning since I'll never know what the sites that are using the component are like.
Regardless, users are free to override the z-index like the workaround you provided as well.

@arkon I tried to create a branch and do pull request but I got access denied. I would suggest the below code
    .ng-sidebar {
      -webkit-overflow-scrolling: touch;
      overflow: auto;
      pointer-events: auto;
      position: absolute;
      touch-action: auto;
      will-change: initial;
      z-index: 1;
    }

    .ng-sidebar.ng-sidebar--over {
      z-index: 99999999;
    }


2021.0.x release for cve-2022-22965

Describe the bug
Will there be a 2021.0.x release for cve-2022-22965 and https://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement, it looks like there will be based on the latest commit to this branch, interested to know if you have a timeline on when this could be made available?
Many Thanks
Sample
If possible, please provide a test case or sample application that reproduces
the problem. This makes it much easier for us to diagnose the problem and to verify that
we have fixed it.

Spring Cloud does not manage Spring version. It comes from Spring Boot. It's enough for you to upgrade your Spring Boot version.

The spring boot version used is driven from this right? https://github.com/spring-cloud/spring-cloud-release/blob/1afd865c144737764f64776e82c1f73558f72193/spring-cloud-starter-parent/pom.xml#L8

Only for building. If you go to https://start.spring.io you'll see that the boot version is managed independently for users of spring cloud


Ubuntu: Project root directory selecting issues.

Did a fresh install on ubuntu.  However, when I try to open a directory to get a tree listing on the left, or set the default project directory in the preferences, both are ignored.  Instead, it only shows a project using my /home/userName/ folder as it's root.  This is somewhat problematic because there's a lot of unnecessary cruft in my home directory that get picked up (for instance, running a search makes it try to index).  And, of course, it's also a problem because I can't get a useful listing of files that -aren't- located in my home directory, and have an unusably long project file tree instead.
version: .deb version 0.138.0
Ubuntu version: Ubuntu 12.04.5 LTS (64 bit)
How to reproduce: Install the .deb from a directory under your /home/ folder.
developer console: No logged errors in the developer console.

+1 I have the same issue.  It is taking more than a quarter to get this fixed on a next gen Editor? Come on guys

@vumaasha what Atom version are you using?  Are you on Ubuntu as well?  Can you reproduce this in safe mode (atom --safe)?

atom version 0.182.0
No. it does not happen in safe mode.
Ubuntu version: ( with all latest updates)
Distributor ID:	Ubuntu
Description:	Ubuntu 12.04.5 LTS
Release:	12.04
Codename:	precise

All right, since it doesn't happen in safe mode, that means that one of your installed community packages is causing the issue.  You could try out the package-cop package by @mark-hahn to try to resolve your issue or just manually disable packages to find the culprit.

@50Wliu  I do not have any community packages installed. I am testing this in a fresh atom installation. It has only core packages in settings page

If you can't reproduce it in safe mode, that means you have a package somewhere interfering with Atom.  Safe mode and non-safe mode should perform identically with no community packages.

Closing this out since it seems to be a 3rd party package issue and hasn't been reported when running in safe mode.


Replication lag

Is there a way to see how far behind the replica is? I tried the same approach as for geo-replicas using dm_geo_replication_link_status but got nowhere. dm_hadr_database_replica_states doesn't work in Azure SQL Database.

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

ID: 7a2961d1-4448-11b7-2dc2-3b738bd70939
Version Independent ID: 206eb022-25c4-66d7-7285-0d53a84956e3
Content: Azure SQL Database - read queries on replicas
Content Source: articles/sql-database/sql-database-read-scale-out.md
Service: sql-database
GitHub Login: @anosov1960
Microsoft Alias: sashan

@LuisGonzalezLT We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

It worked fine for a geo-replica, but didn't work for the replica opened up
by read scale out.
On Mon, Aug 27, 2018 at 3:20 PM Mike Ubezzi<EMAIL_ADDRESS>wrote:

@LuisGonzalezLT https://github.com/LuisGonzalezLT I am showing that sys.dm_geo_replication_link_status
(Azure SQL Database)
https://docs.microsoft.com/en-us/sql/relational-databases/system-dynamic-management-views/sys-dm-geo-replication-link-status-azure-sql-database?view=azuresqldb-current
is to return "Show replication lags and last replication time of my
secondary databases." Example:
https://docs.microsoft.com/en-us/sql/relational-databases/system-dynamic-management-views/sys-dm-geo-replication-link-status-azure-sql-database?view=azuresqldb-current#example
SELECT
link_guid
, partner_server
, last_replication
, replication_lag_sec
FROM sys.dm_geo_replication_link_status;
What is sys.dm_geo_replication_link_status not providing you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/13693#issuecomment-416338027,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AolEIgjRxeYzrUDgFwFETrUHQ_h7GWp4ks5uVEZ4gaJpZM4WEZus
.

@LuisGonzalezLT Thanks for the feedback. I will look into read-out scale Powershell cmdlets.

@LuisGonzalezLT Please let me know if the above does not meet your needs. I can reopen this issue and continue the investigation or have you create a feature request in the Azure SQL  User Voice. Thanks, ~Mike

Coming back to revisit this after a long hiatus. Sorry for the delay.
sys.dm_operation_status isn't what I need.
What I am specifically looking for is a version of:
SELECT * FROM sys.dm_geo_replication_link_status
that reports on the read scale-out replica, not the geo-replica, so I can see what the lag time is of the read scale-out replica.
sys.dm_geo_replication_link_status only reports on geo-replicas.

This is a forum question but looking into this now. The MSDN and Stack Overflow forums have more eyeballs looking at questions. This channel is specific to correcting/enhancing the documentation. If this information is something that could enhance the documentation, we can look into adding it, etc. Thanks, Mike!

Yeah - I put a formal feature request in for it over in the "How can we
improve Azure SQL Database?" forum.  Thanks :-)
On Mon, Dec 17, 2018 at 12:45 PM Mike Ubezzi<EMAIL_ADDRESS>wrote:

This is a forum question but looking into this now. The MSDN and Stack
Overflow forums have more eyeballs looking at questions. This channel is
specific to correcting/enhancing the documentation. If this information is
something that could enhance the documentation, we can look into adding it,
etc. Thanks, Mike!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/13693#issuecomment-447933992,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AolEIrSI6CRfhe_HKEfIAELjO26Zy69eks5u59hCgaJpZM4WEZus
.

I have a question out to an individual. I will get back with you....

Much appreciated.
On Mon, Dec 17, 2018 at 1:05 PM Mike Ubezzi<EMAIL_ADDRESS>wrote:

I have a question out to an individual. I will get back with you....
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/13693#issuecomment-447940558,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AolEIp3h4y28MGq0AQMSL-f738DLX5_iks5u59zdgaJpZM4WEZus
.

@LuisGonzalezLT Okay, so there is no solution to this at the moment. The User Voice is the best channel to address this. Thanks for following up!

OK. Thanks for checking into it. It didn't seem like there was a way so
that confirms what I thought.
On Mon, Dec 17, 2018 at 4:16 PM Mike Ubezzi<EMAIL_ADDRESS>wrote:

@LuisGonzalezLT https://github.com/LuisGonzalezLT Okay, so there is no
solution to this at the moment. The User Voice is the best channel to
address this. Thanks for following up!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/13693#issuecomment-448001629,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AolEIuuTdQDQdZWkUEqpO1aEarn8QlTtks5u6AmfgaJpZM4WEZus
.

Just in case anyone else wants to vote, here is the uservoice - https://feedback.azure.com/forums/217321-sql-database/suggestions/36299335-provide-insight-into-the-replication-lag-between-a


fix on remove global layout listener

There's no advantage switching between these two. One calls the other on the newer platforms. When we reach minSdk 16 we'll just switch to calling the new method.


Be able to run Lean 3 and Lean 4 buffers (with corresponding LSP clients) simultaneously

(A prerequisite here is PRing a change to nvim-lspconfig and/or doing the appropriate dispatch here within this repo.)

Implemented by @rish987 in #52, hooray!


HikariCP keeps all connection open, and holds it.

Hi,
I'm using hikariCP from the long time, and pretty much knows its behavioral advantages. i know that CP fills connections on startup and periodically refresh the CP by retiring old connection and filling with new one.
recently i used it with sybase, and the connection provided by servers are quite low, as the CP start it fills the connection directly to maximumPoolSize and hold it no matter what its getting used by application or not. my application is getting used only for 2 hours a day with huge requests but it must be keep running as few request comes any time. can there be a auto scaling feature or kinda timeout like if pool is not getting use for 10 min it will lower number of connection from the pool and if request keeps on coming it will fill it up to the max?

You can set minimumIdle to a lower value than maximumPoolSize or you can even set it to zero. Combine that with a shorter idleTimeout and the pool will adjust itself based on the app usage.

Thanks @jnehlmeier ,but this is not a default behavior, default connections are always to max. cant it be at auto-scaling by default settings?

No, HikariCP prefers a fixed sized pool as default.
If you want auto-scaling you need to configure HikariCP to your needs using the properties I mentioned above.

The default (target) for HikariCP is optimal performance under constant load. Users with periodic workloads or capacity constraints will need to tune accordingly.


*: rename repo from pingcap/ticdc to pingcap/tiflow

What problem does this PR solve?
Finish step-3 in #3749
What is changed and how it works?
Run the following script
sed -i "s/github.com\/pingcap\/ticdc/github.com\/pingcap\/tiflow/g" $(find . -type f|grep -vE "bin/|.git")
sed -i "s/pingcap\/ticdc/pingcap\/tiflow/g" $(find . -type f|grep -vE "bin/|.git")
make fmt

Check List
Tests

Unit test
Integration test

Release note
None

/run-all-tests

/run-leak-test

/run-all-tests

/run-all-tests

/run-all-tests

/verify

/run-verify

/run-dm-integration-test

/merge

/merge

/run-integration-test


PostgreSQL Container for Docker Cluster

This introduces support for PostgreSQL for the Docker Cluster.
As discussed in  #26
It's important to mention that the DBD::Pg Perl Module required PostgreSQL development libraries on the Web Service container which are only available for the PostgresSQL Version 11
The databases of Version 10 and 11 are incompatible so the version of the PostgreSQL container is 11.13
According to the End of Life Policy at Postgres this seems to be a reasonable versioning:
Postgres Versioning Chart

The access from the Web Service container is documented as correct
according to the Mojolicious documentation:
https://docs.mojolicious.org/Mojo/Pg#SYNOPSIS
per1_web@b2046f460754:~$ perl -I ~/perl5/lib/perl5/ perldoc-browser.pl index all
pg 0 dmp:
bless({
  dsn => "dbi:Pg:dbname=perldoc;host=db",
  options => {
    AutoCommit          => 1,
    AutoInactiveDestroy => 1,
    PrintError          => 0,
    PrintWarn           => 0,
    RaiseError          => 1,
  },
  password => "secret",
  username => "perldoc",
}, "Mojo::Pg")
pg version: 'PostgreSQL 11.13 on x86_64-pc-linux-musl, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 64-bit'

also in the PostgreSQL container the entries can be found correctly:
$ docker-compose exec db /bin/sh
/ $ psql -h db -U perldoc perldoc
Password for user perldoc:
psql (11.13)
Type "help" for help.

perldoc=# \dt
             List of relations
 Schema |      Name       | Type  |  Owner
--------+-----------------+-------+---------
 public | faqs            | table | perldoc
 public | functions       | table | perldoc
 public | mojo_migrations | table | perldoc
 public | perldeltas      | table | perldoc
 public | pods            | table | perldoc
 public | variables       | table | perldoc
(6 rows)

perldoc=# select count(*) from pods;
 count
-------
  1456
(1 row)

to resolve the permission conflict at image build time I added the .dockerignore
as documented at
Conflict about persistent Database Storage Location


Mod Menu not saving settings upon close

specifically with soundtrack menu, changes made to settings reset upon game close. mods like minimap api keep settings though

Mod Config Menu Pure is not responsible for saving the configuration data of other mods. Doing that is up to the other mods. Thus, if another mod's settings are not being properly saved, then you need to take that issue to the specific mod's developer.


quality

better

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

ID: 0420c638-1d2b-0348-1106-ee51f3000c38
Version Independent ID: c7be09e7-9c66-5c5f-6c5b-28164f14bc7d
Content: Azure CLI Samples
Content Source: articles/virtual-machines/linux/cli-samples.md
Service: virtual-machines-linux
GitHub Login: @cynthn
Microsoft Alias: cynthn

@nurleni please provide more specific information if you have any feedback on this specific doc

@nurleni I will close for now. Please let me know more details if you have any feedback on this particular doc.


Why comment rules???

Can I ask why do we have the capitalized-comments and line-comment-position rules active in default setting? Do we really need them? How they improve the code? What they bring except shitload of warning messages? And they are not autofixable...

capitalized-comments
I concur, I should have waited with this rule until it was fixable (it is as of ESLint 3.12 🎉). The intention was to make comments proper English, nothing more. :) I apologise if this made your day worse - I will be more careful with similar new rules in the future.
line-comment-position
This rule's configuration goes hand-in-hand with max-length rule. Let me first explain why we have that rule set to 100.
There have been studies about the optimal line length for humans to make reading easy and fast. For too long lines, the following issues occur (among others):

The eye has to move much more, causing unnecessary strain
Readers tend to skip to incorrect line when returning to the beginning
For code specifically:

Long lines usually imply there are too many statements in that line
You are the victim of callback hell
You are the victim of too much branching

Some might argue that this can be easily avoided by having your IDE soft-wrap the code. However, this has the same problems as using tabs instead of spaces for formatting - it is application-dependent, sometimes it is unavailable and in my personal experience, it never formats the code as well as a human would do it.

That's why there is a soft limit of 100 characters per line. Having this explained, it is quite easy to explain why we have line-comment-position set to only allow comments above code:

Comments are usually used to explain something important -> it should not be at the end of the line where it might be missed, either when reading the code or during refactoring
Inline comments increase the line length (see previous reasons why this is bad)
Inline comments reduce the available space for actual code

Of course, if the team you work with decides that all of this is BS and you do not care, feel free to override these rules to a different setting. 😇

C'mon... we are writing source code, not a novel. But if the capitalized-commens rule is auto-fixable now and everyone else think it's necessary, I can probably live with it. But I still think we should have as few rules in default setting as possible and this is perfect example of a rule that should not be there.
For line-comment-position... I have no problem with max-length rule. It's one of really useful rules. But I don't see any connection between it and line-comment-possition. I guess you assume every comment needs to be full sentence, but again - it's source code, not a novel. I personally prefer comments as short as possible, just couple words, so you don't spent much time reading it. And for these short comments there is plenty of room in 100 characters. I'm not forcing anybody to write comments in this way, but I don't see any value in disabling it globally. Sometimes it might be useful and the max-length rule is enough to be sure code or comments are not overflowing of the screen.

Ultimately I must say I was wrong about enabling capitalized-comments rule - it's disabled now, will be released when new ESLint version gets out. See #14.
As for line-comment-position... you made a point. After sleeping on it for several days I agree with you - my original intent should be covered by max-length rule and there is no real necessity to enforce comment placements. Yay. 🎉
As for the idea of having as few rules in the default config as possible... The intention of this repository is to enforce a consistent coding style across all projects (mainly within STRV). You cannot do that with everything disabled - quite the contrary. You have to enable every possible rule and then selectively disable those who bring no value or do not quite work as we would like (like these comment rules, ie.).
Thanks for all your feedback.

Awesome! Thanks for reconsidering these rules.

Now released as 6.3. 🎉


Crouch and Sprint not recognizing Input Map

I created Input Maps (project settings) for all key bindings, all work fine with the exception of crouch and sprint. The string values I originally chose were "CROUCH" and "SPRINT". I attempted changing the string value thinking it might be conflicting with something, but any string value returns the error. I made sure my spellings matched up as well.
With the code:
@export var CROUCH : String = "CROUCH"
@export var SPRINT : String = "SPRINT"

I receive the push error that comes default to the FPC add-on:
E 0:00:00:0304   character.gd:117 @ check_controls(): No control mapped for crouch. Please add an input map control. Disabling crouching.
  <C++ Source>   core/variant/variant_utility.cpp:1091 @ push_error()
  <Stack Trace>  character.gd:117 @ check_controls()
                 character.gd:95 @ _ready()

I have traced what I believe is all the crouching and sprinting code without finding the root cause, if I suppress the error from disabling crouching and sprinting respectively I get repeating errors from the following processes:
E 0:00:02:0741   character.gd:250 @ handle_state(): The InputMap action "crouch" doesn't exist.
  <C++ Error>    Condition "!InputMap::get_singleton()->has_action(p_action)" is true. Returning: false
  <C++ Source>   core/input/input.cpp:292 @ is_action_just_pressed()
  <Stack Trace>  character.gd:250 @ handle_state()
                 character.gd:162 @ _physics_process()

E 0:00:02:0757   character.gd:231 @ handle_state(): The InputMap action "sprint" doesn't exist.
  <C++ Error>    Condition "!InputMap::get_singleton()->has_action(p_action)" is true. Returning: false
  <C++ Source>   core/input/input.cpp:287 @ is_action_pressed()
  <Stack Trace>  character.gd:231 @ handle_state()
                 character.gd:162 @ _physics_process()

I am running Godot 4.2 Stable.

Confirmed that rolling back to a previous version, one that doesn't do states, solves the issue. I do not know exactly what version I have on my old project but looking at the version history it seems to be the previous release.

With the error line:
character.gd:250 @ handle_state(): The InputMap action "crouch" doesn't exist.

It seems like either the FPC or the engine is getting "crouch" as a lowercase value, while you have CROUCH in the input map.
From a first glance, I can't see what the error is (I know, crazy) but I have a few things for you to try.

Change the InputMap names to lowercase ("crouch", "sprint") (just for debug, if this fixes it we need to find the underlying bug)
Try to recreate this bug with the latest release in a new project
If you changed any of the code in the FPC, either try reverting those lines in a separate branch of your project, or inspect those changes closely

You mentioned reverting to an older version that doesn't use states. This project has always used a state machine, ever since version one. It started out with a more primitive one though. The new state machine (26f7e773e2a322c42416113a9ed9cd1a490cf3ef) slightly changed how the state controls were handled.
A possible cause is that I accidentally hardcoded the string "crouch" into the Input.is_action_pressed function in that commit on line 127, 138, 149, and 155, but @ItWinVis pointed this out in issue #4 and I fixed it in (01ff47493c715fd925a45fd566a7297d2fb4d62a) and (a1729c1cd554112254573b3dd6554dbbb61f66c4).

Good news, but also a bit of bad news, using lowercase in the InputMap clears up the errors and it now switches states appropriately. This works with the string being lowercase or uppercase in the script. (Super weird)
The only code I changed according to my history is uncommenting the full controller support code and changing the string names to my own InputMap names instead of the default UI ones.
I have attached a zip file with the recreated error in its fixed state using lowercase InputMap strings and uppercase strings in the script. I started by using uppercase for both and it gave the same error.
In the recreation I left all other code alone.
testing_fpc.zip
Below is the code mentioned that you fixed and I confirm that I do have the updated, fixed version for all instances of the function call.
if Input.is_action_pressed(SPRINT) and state != "crouching":
if Input.is_action_pressed(CROUCH) and state != "sprinting":

And all others...

Based on what I am finding it may be a bug on Godot's side with specifically the words crouch and sprint not being recognized while uppercase in InputMap, all other strings are upper case and they work fine for me.

Here is a screenshot of all my Input Maps and a code snipped for the script.
@export_group("Controls")
@export var JUMP : String = "JUMP"
@export var LEFT : String = "LEFT"
@export var RIGHT : String = "RIGHT"
@export var FORWARD : String = "FORWARD"
@export var BACKWARD : String = "BACKWARD"
@export var PAUSE : String = "PAUSE"
@export var CROUCH : String = "CROUCH"
@export var SPRINT : String = "SPRINT"

Everything works as it should with this.

I tested the project with all the inputs uppercased and sure enough, it had an issue with just the sprint and crouch inputs.
There are two possibilities that I can see for this:

If it is a problem in the FPC, it would probably be in the handle_state function since that's where both of them are handled and they are done quite similarly. I've combed through this function multiple times and there is no hardcoding nor any alternate button detection systems. If this is the case, it has to be really well hidden.
If it is a problem with the engine, then the InputMap code is doing something with the sprint and crouch inputs, or it is somehow saving the original values of the export variable and not accepting the changed code.

I know there is either a bug in the physics engine or a feature of InputMap where if a crouch button is pressed, you cannot fall off of a platform. Just try to walk off of the main test platform in the FPC, it won't let you. I didn't add any code to the FPC to do this, this is Godot Engine itself. This also happened in QFPC V1.
I'll probably have to go through the Godot engine code for InputMap to see if it handles sprint and crouch inputs differently and maybe do a bug report or a PR.

I checked the stack to see what the variables CROUCH and SPRINT were initializing as and the values that I input have no effect, they always init as lowercase crouch and sprint. I don't know where it would be as I have checked all the files in the add-on, but, somewhere it is hard coded. Unless there is another way to get this to occur.

I checked the Input.cpp and Input_Map.cpp files for Godot located here: https://github.com/godotengine/godot/tree/master/core/input
I found that the error code from the engine is directly from the exact_match method but there is nothing to do with crouch and sprint respectively.

UPDATE: https://github.com/ColormaticStudios/quality-godot-first-person-2/pull/20
PR for fix, closing issue with above PR.


Validate source and target states against model "choices"

(minor feature request)
It seems that one can declare transitions that arrive to states that are not values listed in FSMField "choices" parameter.
Always using enums here prevents most of the trouble, but wouldn't it be feasible to ensure, at app loading, that all transitions are valid with regards to this list of choices ?

implemented in viewflow.fsm - https://docs.viewflow.io/fsm/index.html


Use a red bar instead of the dot

It would be cool if we could use a red bar instead of the dot. A thin bar, which could be even better than the dot, filling the entire reading area, to help identify the beginning and end of the barcode reading

Hello.
Do you mean just some line (horizontal)?

Hi.
Yes, a horizontal red bar, to help show the user where to focus, instead of the red dot

I agree with @Ghostbird that using a bar is a bit archaic especially in context of 2D codes. But I also acknowledge that for some people are more used to old barcode scanners that displayed a red bar when scanning. As all aiming features are optional you can easily enable or disable whatever suits you.
No ETA for now tho...

@afriscic I agree with your conclusion, thought you seem to have misunderstood my reason.
My point was that there's no inherent relation between the rotational of the device, and the target barcode. In the face of an auto-rotate option that keeps the line horizontal (or at least prevents verticality) it can make certain real-world uses impossible or impractical. This harms the user experience, especially when there's no reason to view the barcode under a certain rotation to an inherently 2D camera scanner.
Summarised: The horizontal line is a fake throwback to historic limitations of 1D scanners, that confuses the UX.

@afriscic I agree with your conclusion, thought you seem to have misunderstood my reason.
My point was that there's no inherent relation between the rotation of the device, and the target barcode. The horizontal line is a fake throwback to historic limitations of 1D scanners, that confuses the UX. To the user it evokes a limitation that they must work to overcome, even though there actually is no such limitation
The addional actions it may make the user perform might be harmful to the user (RSI), device (unnescessary maipulations increase chance of drop/hitting things) and functioning of the software (harder to scan while the user is in the progress of unnecessary device manipulations).


⚠ Bofrost.lu has degraded performance

In 0632ac1, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 3555 ms

Resolved: Bofrost.lu performance has improved in 662a431 after 54 minutes.


Cache proving keys

Right now the prover downloads the proving and verifying keys every time it verifies or proves. We need to cache these files locally to avoid excessive network requests.

Wont' fix due of sunsetting this project.


Swipe gestures are conflicting with zoom gestures

I use the latest version of Extended Image (1.2.0), flutter 1.22. Tried both on physical and simulator.

Sometimes swipe left/right gesture doesn't work.
Open image from gallery. Try to swipe it right or left with a huge velocity.

Expected results: image is being changed to the next one.
Actual results: image is being closed like I swiped up or down.

When image is zoomed in, it's too easy to accidentally close or swipe it.
Open any image and zoom it. Then, try to move your zoom by swiping it up/down or left/right.

Expected results: zoomed image should move with my gestures
Actual results: image is closed or changed to another one.
My code:
https://github.com/Zchandev/iChan/blob/master/lib/pages/gallery_item_page.dart#L81

https://github.com/fluttercandies/extended_image/issues/152

#152

Its not a duplicate. I have recorded videos to show you the problem.
#1 - https://yadi.sk/i/M9LU-jXjPujQEw
#2 - https://yadi.sk/i/oaI2XuU82Hlqjg

please provide an simple runnable demo.

please provide an simple runnable demo.

Check it out. I really like your plugin, if you could help me to fix these issues, I would rate it 10/10
import 'package:flutter/cupertino.dart';
import 'package:flutter/material.dart';
import 'package:extended_image/extended_image.dart';

class Media {
  Media({this.url});

  factory Media.fromUrl(String url) {
    return Media(url: url);
  }

  final String url;
}

List<Media> mediaList = [
  Media.fromUrl('https://disco.scrolller.com/media/21551f.jpg'),
  Media.fromUrl('https://disco.scrolller.com/media/23d95b.jpg'),
  Media.fromUrl('https://disco.scrolller.com/media/2392c2.jpg'),
  Media.fromUrl('https://disco.scrolller.com/media/249d85.jpg'),
  Media.fromUrl('https://disco.scrolller.com/media/20a361.jpg'),
  Media.fromUrl('https://disco.scrolller.com/media/21551f.jpg'),
  Media.fromUrl('https://disco.scrolller.com/media/23d95b.jpg'),
  Media.fromUrl('https://disco.scrolller.com/media/2392c2.jpg'),
  Media.fromUrl('https://disco.scrolller.com/media/249d85.jpg'),
  Media.fromUrl('https://disco.scrolller.com/media/20a361.jpg'),
];

final gestureConfig = GestureConfig(
  initialScale: 1.0,
  minScale: 1.0,
  animationMinScale: 0.9,
  maxScale: 10.0,
  animationMaxScale: 11,
  speed: 1.0,
  inertialSpeed: 100.0,
  inPageView: true,
  cacheGesture: false,
  initialAlignment: InitialAlignment.center,
);

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return CupertinoApp(
      title: 'Cupertino App',
      home: Home(),
    );
  }
}

class Home extends StatelessWidget {
  const Home({Key key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return GridView.builder(
      itemCount: mediaList.length,
      gridDelegate:
          SliverGridDelegateWithFixedCrossAxisCount(crossAxisCount: 3, childAspectRatio: 1 / 1),
      itemBuilder: (_, index) {
        final media = mediaList[index];
        return GestureDetector(
          behavior: HitTestBehavior.translucent,
          onTap: () {
            final pageRoute = FadeRoute(page: ImageItem(index: index));
            Navigator.of(context).push(pageRoute);
          },
          child: ExtendedImage.network(media.url),
        );
      },
    );
  }
}

class ImageItem extends StatefulWidget {
  ImageItem({this.index});

  final int index;

  @override
  _ImageItemState createState() => _ImageItemState();
}

class _ImageItemState extends State<ImageItem> {
  PageController pageController;

  @override
  void dispose() {
    pageController.dispose();
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    pageController = PageController(initialPage: widget.index);

    return ExtendedImageSlidePage(
      slideAxis: SlideAxis.vertical,
      slideType: SlideType.onlyImage,
      slidePageBackgroundHandler: (offset, pageSize) => defaultSlidePageBackgroundHandler(
          offset: offset,
          pageSize: pageSize,
          color: CupertinoColors.black.withOpacity(0.5),
          pageGestureAxis: SlideAxis.vertical),
      slideEndHandler: (offset, {details, state}) {
        final minDistance = 15.0;
        return offset.dy >= minDistance;
      },
      child: ExtendedImageGesturePageView.builder(
        controller: pageController,
        itemCount: mediaList.length,
        itemBuilder: (context, pos) {
          final nextMedia = mediaList[pos];
          return ExtendedImage.network(
            nextMedia.url,
            fit: BoxFit.contain,
            cache: true,
            mode: ExtendedImageMode.gesture,
            enableSlideOutPage: true,
            filterQuality: FilterQuality.high,
            initGestureConfigHandler: (state) => gestureConfig,
          );
        },
      ),
    );
  }
}

class FadeRoute<T> extends PageRouteBuilder<T> {
  FadeRoute({
    this.page,
  }) : super(
          transitionDuration: const Duration(milliseconds: 300),
          pageBuilder: (
            BuildContext context,
            Animation<double> animation,
            Animation<double> secondaryAnimation,
          ) =>
              page,
          transitionsBuilder: (
            BuildContext context,
            Animation<double> animation,
            Animation<double> secondaryAnimation,
            Widget child,
          ) =>
              FadeTransition(
            opacity: animation,
            child: child,
          ),
        );

  final Widget page;

  @override
  bool get opaque => false;
}

can't reproduce at my side. and by the way
this code is wrong, you should create it at initState method.
Widget build(BuildContext context) {
pageController = PageController(initialPage: widget.index);

can't reproduce at my side. and by the way
this code is wrong, you should create it at initState method.
  Widget build(BuildContext context) {
    pageController = PageController(initialPage: widget.index);

To reproduce, try to do a fast swipe from the corner. You need to swipe it FAST, its only occured in that way. If you swipe slowly, it works.
Thanks for correction, I moved it to initState in my app

I have the same problem. Image is being closed when swiping too fast

Slide Out Page or Swipe Photo, It's hard to tell the difference

Slide Out Page or Swipe Photo, It's hard to tell the difference with FAST operation. The only way is that change Slide Out condition by yourself.

Swipe photo is the main problem

Slide Out Page or Swipe Photo, It's hard to tell the difference with FAST operation. The only way is that change Slide Out condition by yourself.

Swipe photo is the main problem

It's hard to tell the difference between Slide Out Page and Swipe Photo at that moment. you feel you are swipe page, but flutter tell you this is slide out gesture.

Slide Out Page or Swipe Photo, It's hard to tell the difference with FAST operation. The only way is that change Slide Out condition by yourself.

Swipe photo is the main problem

It's hard to tell the difference between Slide Out Page and Swipe Photo at that moment. you feel you are swipe page, but flutter tell you this is slide out gesture.

Is there an existing issue on flutter's github? I can create it if you provide more details

read more flutter gesture arena

HorizontalDrag or onScaleUpdate are not base on your feel. if you swipe not on Horizontal (but you feel it is ), system may thought it's not a horizontal drag behavior,  it's vertical drag  and you swipe quickly , this is reach the condition to Slide Out Page

HorizontalDrag or onScaleUpdate are not base on your feel. if you swipe not on Horizontal (but you feel it is ), system may thought it's not a horizontal drag behavior, it's vertical drag, one gesture will not be changed util it's end. And you swipe quickly , it reaches the condition to Slide Out Page.

Thanks. I have created the issue: https://github.com/flutter/flutter/issues/68960

同样的问题


Proposal: Introducing higher-level struct and abstractions for the RPC MEV-Share client

Hello,
After noticing @zeroXbrock's request for a Rust MEV-Share client on X/Twitter, I began working on an implementation.
Now that I'm aware of this repo, I'm unsure whether to publish mine on crates.io. I'm concerned about contributing to DX confusion or decision fatigue. I'm considering whether it makes more sense to refactor my code into a higher-level struct on top of this modular implementation (which is of top quality, by the way) or simply PR the diffs here and archive mine.
The benefits I'd like to retain in the client include:

The ability to client.send_bundle(params).await?.inclusion().await?
The ability to initialize a client without the use of a tower::ServiceBuilder and to abstract the signing away.

Regarding 1: Your implementation currently returns Ok() when the bundle is accepted by the relayer. However, I find it useful to keep the inclusion logic abstracted within the client lib.
You can view my take on it here. With this, usage can be extended to:
client
    .send_bundle(params)
    .await? // relayer accepted the bundle
    .inclusion()
    .await?; // bundle was included in a block

Regarding 2: Since there's only one signing logic/method, it makes sense to abstract it.
Unsure if I should retain these enhancements in my repo or if they're better suited here.
I'd be happy to draft a PoC PR if you think this is a good direction: I’m considering introducing a higher-level mev_share_rpc::RpcClient in a new mev-share-rpc crate which would operate using mev-share-rpc-api, and maintain the same abstraction level as the existing mev_share_sse::EventClient.
Of course, if you have a different direction in mind or feel the other approach would be more suitable, I'm entirely open to that as well.
Cheers

cool,
having a better client dx would be great.
I'm okay with enhancing/revamping client trait completely


chore(deps): update common-dev-assets digest to da96396

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
b1b2455 -> da96396

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 6.4.0 :tada:
The release is available on:

GitHub release
v6.4.0

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 7.0.0 :tada:
The release is available on:

GitHub release
v7.0.0

Your semantic-release bot :package::rocket:


[BUG] onFinish promise is never rejected

Describe the bug
If there is a mutation error, the onFinish promise is supposed to be rejected but right now the Promise never finishes because the reject function is not called:
https://github.com/refinedev/refine/blob/ae34559a5e44a878e85514d4cc137539e060aeae/packages/core/src/hooks/form/useForm.ts#L461-L464
(same applies for the error handler of update)
I think either the reject function should be passed to the onMutationError handler or the reject function should be called in every case.
Steps To Reproduce

Submit a form that throws a mutation error
Check if the onFinish handler rejects

Expected behavior
The onFinish handler should not only resolve but also reject in case of any errors.
Packages
@refinedev/core@latest
Additional Context
No response

Hi @jaulz ,
I would be happy to contribute to this bug. I would want to know more details on how we can test this and call this Promise function.
Can you assign this to me?

@prabhanshjn I just raised a PR at https://github.com/refinedev/refine/pull/5697 but feel free to contribute.

Thanks @jaulz ,
I think what has to be done is,
we remove the return statement from onMutationError, as that is why reject() will never be called.
What we can do is instead is add return in reject statement and that will solve the problem.

Closing in favor of https://github.com/refinedev/refine/issues/5702, we'll be handling this and similar other cases with this issue.


[WFLY-19472] Upgrade WildFly Preview to jakarta.security.enterprise-a…

…pi 4.0.0
https://issues.redhat.com/browse/WFLY-19472
Draft against EE11 branch to get WFP-focused CI.

CI passed so I'm closing this.


Error broadcasting transaction

Hi Blockcypher team,
I got some help earlier on the correct way to format a transaction using the TX skeleton, so I decided to try it again when I got home. I created a new, un-broadcasted, transaction, and I got this error when posting:
{ error: 'Error validating transaction: Transaction 02b1be3be0a6a4f7d8e369cca88520443b3fc0993d3660d4d52e5f383d505650 has an input referencing an unknown transaction: d69adc7c6a355ea4297755350f86c52710a6ebd72a150215c276f3cd4c659d5e.' }
The transaction referenced in the error has 6 confirmations after about an hour:
https://live.blockcypher.com/btc/tx/d69adc7c6a355ea4297755350f86c52710a6ebd72a150215c276f3cd4c659d5e/
Is there a minimum amount of transactions needed for the API to broadcast? Thanks again for helping me earlier!
Here's the raw transaction hash and a gist of the script I'm using:
var axios = require('axios')
axios.post('https://api.blockcypher.com/v1/bcy/test/txs/push',
        {"tx": "01000000015e9d654ccdf376c21502152ad7eba61027c5860f35557729a45e356a7cdc9ad6000000008a47304402201f06d4679b3f835215c338bace1d8b317aeade5346309389b60f4d7753f5a710022033d9e5aafdd4154889b6ab71eb927b8879eeb3dc9c6c2e665e665485f71a4e0b014104f0087a849a6e9ebc5b3fb9090849a22b72c71564e165458a9957150a7dd24639f1f60746cbfa25950ec9bc7064a77141a78c5a309ff7cc0b90050e8a6a1a8ed7ffffffff02da210000000000001976a914fed9eb51a9d13032e4cf2d6a4856fe8bde18b18c88ac0000000000000000546a4c5177723335322d33316472342d4141412d30322d31362d31352d32336f6c2d313030303030303030302d33323132322d333435352d363933352d323334392d323334302d31323333322d30322d31302d313500000000"}
      )
      .then(function (response) {
        console.log(response.data);
      })
      .catch(function (response) {
        console.log(response.data);
      });

Hi there,
It looks like you're pushing to our bcy/test chain endpoint. This is a different chain than bitcoin main with entirely different transactions. To build a bcy/test transaction, you'll need to reference a previously unspent blockcypher testnet transaction- our faucet will help you get started there. Check out  http://dev.blockcypher.com/#testing for more information.

@LAMike310: Closing this issue now, if you still have trouble feel free to reopen with new information.


Fix Windows

Please add vc features and please correct the python test dependency on Windows. Also please bump the build number after doing these things.
xref: https://github.com/conda-forge/staged-recipes/pull/3199#pullrequestreview-47693013
xref: https://github.com/conda-forge/staged-recipes/pull/3199#pullrequestreview-47693621

In my TODO list. Will do today, thanks =)

Have pulled the packages that were built without the vc feature as they were not compliant. As the new packages for Windows are out and using the vc feature correctly, this shouldn't cause any issues. One merely needs to upgrade to them.


Update backend README to reflect all the env var needed to access it in local

Description of changes:
Backend README enrichment.
Added USER_POOL_ID and CLIENT_ID env vars who is needed to access the admin section in the swagger/redoc.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

LGTM,Docs for development is not arranged well, so your contribution is helpful. Thank you!


Add FFI integration against pyarrow

As it is being done in arrow-pyarrow-integration crate on the arrow repo.

Done in #67


Possibly unwanted Entries in Index

Thanks for this really cool plugin! I have some questions or feature requests though:
I was looking into the after save events and recognized that there is no check against the index criteria. So in theory it would be possible that an unwanted entry could appear in a collection.
For example if I defined my index criteria to include a check if a Lightswitch Field 'includeInSearch' was true that wouldn't be checked in the after save event, wouldn't it? So eventually if I unchecked this field in an entry and saved it, that entry would still be sent to the index.
Also it seems to me that an entry which could match the criteria for more than one collection would only be updated in one collection automatically. For such cases it would actually be necessary to check against all collections and update the entry in all matching collections.
Besides that I think it would be nice to have another console command to check for expired events like the scheduled posts command. Right now expired entries don't get deleted automatically because Craft doesn't fire an event for that. So it's necessary to have the sync commands run as cron jobs to ensure that expired entries get deleted.
Also, I was having issues because I didn't stick to the naming schema for the 'section' attribute. I didn't recognize until today that it was more or less mandatory to name it like 'section.type'. It would be nice to have this mentioned in the Readme or docs.

Just a quick update because I actually observed unwanted Entries in my index now. I'm using this criteria:
->criteria(function (EntryQuery $query) {
        return $query->section('members')->level(1);
    });

but still there were Entries from lower levels in my index.

Thank you for mentioning. We are doing quite some rework on Typesense at the moment to improve it, we will definitely investigate your issue.


[Bug]: Sublime Text 4 shows "unknown" version after installation

Brief description of your issue
When I try to install Sublime Text 4 via winget, winget list always shows "unknown" for the version of the installed program, which makes it unable to apply updates via winget upgrade.
Steps to reproduce

Remove "Sublime Text 4" via the Control Panel
Search Sublime Text 4 via winget search sublime
Install with winget install -e --id SublimeHQ.SublimeText.4
Check the version with winget list

Expected behavior
The version shows correctly and winget should be able to update Sublime Text 4 via winget upgrade.
Actual behavior
winget list shows (the header is "Name ID Version Source" in Chinese)
名称                                          ID                                            版本                源
-----------------------------------------------------------------------------------------------------------------------
Sublime Text                                  Sublime Text_is1                              Unknown

winget upgrade --all does not apply upgrade to Sublime Text 4.
Environment
winget --info
Windows Package Manager (Preview) v1.2.3411-preview
Windows: Windows.Desktop v10.0.19044.1387
Package: Microsoft.DesktopAppInstaller v1.17.3411.0

@Icarusradio this is likely caused by the entry reported in Apps & Features. Can you check to see if the program version is reported there?

Apps & Features

Yeah, I checked Apps & Features in settings, it does not show the version of Sublime Text.

That's what's causing the unknown. The Sublime Text installer isn't reporting the version. They will need to update their installer to report the version. We may be capturing the version based on the file version which isn't necessarily the correct version for the program.

I looked at their website. It looks like you can submit a "support" request to ask them to make the change.

Duplicate of #126287


paths.py - replacing space with slash+space

Hi!
First of all, thanks for the library. Very useful!
Second, I wanted to ask you why do you replace space with slash+space in paths.py? Is this a bug or something you've done on purpose?
imagePath = os.path.join(rootDir, filename).replace(" ", "\\ ")
PS: I'm using Windows and Python3.

It's not a bug. It's to escape file paths that have spaces in them. If you're on a Unix machine try to auto-tab complete a file path that has spaces in them.
It will change:
$ cd Foo Bar
To:
$ cd Foo\ Bar

Yes. You are write on Unix System. Try reading an image with the path escaped on Windows. It will return None because "C:\ugly path\image.jpg" is transformed into "C:\ugly\ path\image.jpg" and that path does not exists.
Please, don't get me wrong, I hate spaces in paths!
Cheers.

Got it, I see the issue. I'll re-open this in case any user wants to take a crack at it. Spaces in file paths are a pain. I try to avoid them whenever possible and they really shouldn't be used.
I'm tempted to say "it's a feature not a bug" to make people stop using spaces in file paths; however, that's not entirely fair ;-)

There's no reason to manually add the slash in there with that replace operation. os.path handles that for you automatically. For example, this works fine (assuming the directory and file exist):
import os

file_path = os.path.join('.', 'folder name with spaces', 'somefile.txt')

if not os.path.isfile(file_path):
    raise ValueError(f'Cannot read file at {file_path}')
with open(file_path) as f:
    print(f.read())

results in
≫ python file_test.py
this is some file

I don't have a Windows computer to test that on, but according to the docs it should be fine. If you were targeting only python 3.4+ you could use the pathlib module instead.

Hi Adrian, note that b.slash + space doesn't work in OSX either, running python3 in Sierra 10.12.6.
I'm talking about the file names, so I had to remove the backslash with another replace.
About the spaces that shouldn't exist, well, this is a limitation we programmers learned to live with but time goes on and issues like that are supposed to be eliminated, don't they?

It doesn't work on Kubuntu 18.04 either. At least cv2.imread doesn't understand paths that are escaped this way (cv2.imread just returns None). After commenting out the escaping part, cv2.imread can read the image just fine.
I have OpenCV 3.4.1 and Python 3.6.5.

Maybe my simple solution can be useful to you too. I made an inverse replacing. It converts to the original version the paths edited by paths.py adding a slash before the spaces:
working_path = slash_space_path.replace("\\ ", " ")
where slash_space_path is a path edited in paths.py, where spaces have been replaced by \


feat(python): improve metadata of jsii package

Commit Message
feat(python): improve metadata of jsii package (#1587)
Add references to the GitHub repository, etc... in order to improve the
detail page experience on https://pypi.org/project/jsii/. Interestingly,
we already produce some of these metadata entries (where relevant) in
the packages generated by jsii-pacmak but failed to include those in
the runtime library's package descriptor.
End Commit Message

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 3738839a4444753d9baca9938cdc4b6456c409db
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 4f0180411825d8d7449f1f7b05b13acab82a683b
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Check if formValuesInput is defined

PR Type
What changes does this PR include (check all that apply)?
[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build process changes
[ ] Documentation changes
[ ] Other... please describe:
Related issue / current behavior
When changing layout and data of the form then the following error occurs:
    at SafeSubscriber._next (angular2-json-schema-form.es5.js:63440)
    at SafeSubscriber.__tryOrUnsub (angular2-json-schema-form.es5.js:583)
    at SafeSubscriber.next (angular2-json-schema-form.es5.js:530)
    at Subscriber._next (angular2-json-schema-form.es5.js:470)
    at Subscriber.next (angular2-json-schema-form.es5.js:434)
    at Subject.next (angular2-json-schema-form.es5.js:6167)
    at JsonSchemaFormService.validateData (angular2-json-schema-form.es5.js:6479)
    at JsonSchemaFormService.buildFormGroup (angular2-json-schema-form.es5.js:6494)
    at OWNCODE.JsonSchemaFormComponent.activateForm (angular2-json-schema-form.es5.js:63427)
    ....

It seems that formValuesInput are undefined in this line and therefore it will call emit() on undefined:
     if (this.formValuesInput && this.formValuesInput.indexOf('.') === -1) {
        this.jsf.dataChanges.subscribe(data =>
          this[`${this.formValuesInput}Change`].emit(this.objectWrap ? data['1'] : data)
        );
      }

New behavior
It will now check that formValuesInput is defined before calling emit().
Does this PR introduce a breaking change?
[ ] Yes
[x] No

I don't understand. formValuesInput is checked on line 696, before setting up the subscription to dataChanges:
696: if (this.formValuesInput && this.formValuesInput.indexOf('.') === -1) {
697:   this.jsf.dataChanges.subscribe(data =>
698:     this[`${this.formValuesInput}Change`].emit(this.objectWrap ? data['1'] : data)
699:   }
700: }

Why is it necessary to check it again inside the subscription?

It happens when initializeData() functions set the value formValuesInput to null. Then if dataChanges Subject is notified then formValuesInput can be null. It was subscribed to when formValuesInput was not null.

Got it. Thanks for the explanation.
I'll merge it.


Ionic iOS

I use this lib a ionic project.
The animation works on android, but not on iOS.
Any solution to iOS?

Sorry, it works with ios too


[client] Decide the fate of multi-peer communication

Currently, the game is still coded to run either multi-peer ("nearby only") or server-based (via a group).  I'm not sure multi-peer still works, even.   There are two possibilities in the short to mid-term.

Eliminate multi-peer and collapse the Communicator abstraction into its now-only instance.   Go all in with server-based.
Keep multi-peer working, fixing any rot that has crept into it.  Preserve the abstraction and something like the current model for managing groups with the "nearby only" case being sort of like a group.

Of course (1) is the easier path but (2) could have the advantage of making it easier to quickly test UI changes without the overhead of creating groups and using the server.   There will be a longer-term disadvantage in trying to preserve (2) because, as the server becomes more involved in enforcing game-model state machines the peer communication won't be able to maintain parity.    Thus the "short to mid-term" sccope.

It does appear that multi-peer is broken.    When I execute 'Find Players' under the simulator it appears to do the right thing.  But, when I execute it on my actual iPad I get an error: 'Error Domain=NSNetServices Error Domain Code = -72008 "null"'

Yes.   That works, and the version with the fix in it is now installable via the ad hoc method.   Will leave this open pending the resolution of issue #11. since it would be nice to have at least one more tester on this.

It's now pretty clear to me that this is fixed so I'm closing this.   Issue #11 remains open until I can verify that the ad hoc distribution technique works for users other than me.


Default to MVC 3.0 when we can't detect the Razor configuration

https://github.com/aspnet/AspNetCore/issues/13291
Working on verifying it in VS (As soon as I can build Razor on my borked machine)

Hmm, just thinking out loud, do we have any MSBuild bits that default to non-3.0 for projects that aren't explicit? Could be a total goose chase but i'm thinking of the Razor build server and such on how it decides to build Razor bits where the Razor configuration isn't clear.

I don't think we have that yet, we'd need a 5.X sdk.

I don't think we have that yet, we'd need a 5.X sdk and 5.X TFM since language version default is tied to TFM for us.

I see

Verified this in VS. It defaults to 3.0 when Razor configuration could not be determined.


Contributing

Introduction of a 'feedback to API3 docs' page
Review and build of 'contribute to API3 DAO' section

@KenCarvAPI
You have some heading tags that do not make sense.

(Heading1) should only be used once per page at the top of the page: # {{$frontmatter.title}}
Heading2 (as many as needed) must be after a (# Heading1). These really separate the page into new subject matter related to (# Heading1)
Heading3 can only be nested after a (# Heading2) and are related to the subject matter of the proceeding (## Heading2)

I will merge this then pull and fix the links and re-build the indexes.

Thanks @wkande


Gradients are being updated on the augmented data, according to the paper this shouldn't be the case

According to the paper:

Specifically,following VAT [44], we choose to minimize the KL divergence between the predicted distributions on an unlabeled example and an augmented unlabeled example:
minθ JUDA(θ) = E x∈U E xˆ∼q(ˆx|x) DKL pθ˜(y | x) pθ(y | xˆ)) , (1)
where q(ˆx | x) is a data augmentation transformation and ˜θ is a fixed copy of the current parameters θ indicating that the gradient is not propagated through ˜θ, as suggested by Miyato et al

So basically, when we do a forward pass on the model on unlabel2 we need to do with torch.no_grad() so we don't update the gradients for the forward pass on the augmented data.
I also think that we might want to do model.eval() for both unlabel1 and unlabel2 to turn off dropout (if any is being used) and to stop batch norm statistics being updated. Not 100% sure on this though.

Actually, I think I have that the wrong way round. Gradients should be propagated through the augmented but not the unlabeled augmented examples. Either way, we definitely should not be doing both.

@safekidda Do you mean this? : https://github.com/ildoonet/unsupervised-data-augmentation/blob/master/train.py#L62
I detached unlabel data tensor, where detaching means no gradient will be calculated on the tensor.

Thanks, I didn't spot this. I also wasn't aware that detach exhibited this behavior.
With regards my other point on model.eval() to disable dropout and batch norm, I've been in touch with one of the authors of the paper on Reddit, and he ran experiments with both and it was better leaving any regularizer and batch norm updates in place, so I'll close this issue.

Thanks. I also have a same result of batch norm disabling on unlabel data.

Okay, you've tested it? Was there much difference?

I got slightly worse result when disabling bn.


Check ground truth annotations in GT job

Motivation and context

Update ground truth job test by covering the case in https://github.com/cvat-ai/cvat/pull/7714
How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[ ] I have created a changelog fragment
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[x] I have linked related issues (see GitHub docs)
[ ] I have increased versions of npm packages if it is necessary
(cvat-canvas,
cvat-core,
cvat-data and
cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

Please, add also a check that we have object menu for GT objects in GT job, and does not have, in a regular job.


Regression in 0.12.7 for migration:make

Prior to 0.12.7 you could run knex migrate:make without a config option. It is now required so running knex migrate:make from the command line errors (however, it is not necessary for this function to run correctly).

I'm guessing this refers to #1822 . I consider this a bug from the start, not as as current regression. Knex's documentation has always stated:
 The client parameter is required and determines which client adapter will be used with the library

The bug in reality was that the client parameter was not being validated as required.
I can see why this may be an annoyance, but technically writing any code that does not supply the client parameter has been coding 'agaist' the knex documentation from the start. I think it should always be validated as a required field as stated by the docs.
Your description makes it sound like knex should consider config options as required/optional depending on the function that is going to be called, which to me makes no sense at all.
@elhigu What's your view on this?

I would say that it was a bug that it worked earlier.

Your description makes it sound like knex should consider config options as required/optional depending on the function that is going to be called, which to me makes no sense at all.

I would consider that normal behaviour for CLI sub-functions to separate it's concerns, but I understand your decision (though it is a backward incompatibility so I would have bumped the minor version so users don't get caught out like this).

@eddieajau pretty much every change we do, breaks some backwards compatibility in some degree (at least almost every item in this release's changelog).
So if we are very strict about always updating minor version when changing any functionality even when the change is bugfix, we would just end up to always bump minor version and put all changelog entries to breaking changes section...
To draw a line for not having to do always minor version update we've decided that only those changes which change documented functionality are considered as breaking changes worth of minor version update.
ps. though this change actually was changing documented functionality (there was inconsistent documentation about client attribute being required and not being required so). So it was error on my side not to spot that and update the minor.

@elhigu that's fine and that's your call, however there are developers like me that rely on other developers honouring Semver to the best of their ability. Can I suggest putting a moratorium on any more breaking changes in 0.12 so that we can just stay on this version if we want.  Thanks in advance for your consideration.
And yeah, I get it's a huge pain when you find what you know is a defect, but people think it's a feature :)


Anchor links

First I want to tell you that Menu is awesome.
I have one issue, found it today. I add some anchor links elements in menu. Everything is fine while menu is inline. But clicking an anchor link in "toggle" menu, will result with the page scrolls to the correct part of the page BUT the menu stays open. With "regular" links everything works fine.
For now I make a trick, instead of anchor #anchor-link I put absolute url http://domain/path/page-name.asp/#anchor-link and it works at all devices. For sure there is more elegant way to close the toggle ;)
Thanks in advance
Best
Ivana

Well, I decidet that I don't need anchor links in toggle menu layout (mobile viewport). It's ok in inline menu layout but in toggle there is no point ti have anchor links ;) (it's eaisier to scroll than cliks on menu links few times...

Hi, I could add a click event for all navigation links except the ones that have the submenu class, and have it collapse the menu. I'll try to look into it this week. :)

You helped me twice ;-) Navigation works fantastic plus I realized that it makes no sense to have anchor links within the sub-menu (when navigation prepend to a menu icon). So I hide that sub-menu when the browser viewport is smaller than a specific width. But adding click event sound great, for some future projects because I want use your responsive-nav forever. It works so good! Thank you!


Tests

to be confident in updates we need test
@jamesplease want to ideate on what we might to cover

I'd be keen to contribute some tests using react-hooks-testing-library, if you'd take a PR.

@nickcox that would be great, would really apprecite iti


New Project Contents Not Populating

Nightcode isn't recognizing any files or folders in a project it created.  Likely this is due to either leading capital letters in the name.
I started a Web App project from the Start menu.
The specified project name was: NC-2_0_0-web
A folder was created with different capitalization in the name:
nc-2_0_0-web
The originally capitalized project name appears in the side menu; but no files or folders are listed.  Shutting down and restarting Nightcode didn't have an effect.

Fixed in 335721df37a1d12a5478242a4e9290c87da56240


feat(build): move to circleci

Our a11y tests recently started failing with the Chrome version TravisCI provides. Travis integrations for a11y were also more complicated with Github checks. This PR:

Replaces .travis.yml with .circleci/config.yml and split up test steps to allow testing in parallel and nicer Github status checks
Fixes our our a11y Selenium script to not have Travis integrations
Uploads PR previews to https://surge.sh on every pushed commit (no need for Netlify to also build a preview)
Still updates the Github Pages with a new npm run publish:docs target on merges to master.

Deploy preview for pf-next ready!
Built with commit 1d5430c2e9c68e5b0ee455848f561f771d4c7c6f
https://deploy-preview-2121--pf-next.netlify.com

PatternFly-React preview: https://patternfly-next-pr-2121.surge.sh

PatternFly-React preview: https://patternfly-next-pr-2121.surge.sh

PatternFly-React preview: https://patternfly-next-pr-2121.surge.sh

PatternFly-React preview: https://patternfly-next-pr-2121.surge.sh

@redallen  - looks like the pf accessibility reporter was removed from the scripts, can you replicate this within circle?

@dgutride It's now a CircleCI check called test_ally. You can see it running here.

:tada: This PR is included in version 2.25.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Lockfile issue - invalid email addresses

I have been receiving a few messages from our mail system about emails trying to be sent from our Xerte server. Looking at one of these messages shows:
A message that you sent contained one or more recipient addresses that were
incorrectly constructed:
<EMAIL_ADDRESS>missing or malformed local part (expected word or "<")
As can be seen the recipient part of the address is '09:37:20),' which is obviously wrong.
Looking at the code this seems to come from a 'lockfile.txt' file which seems to be created to prevent multiple editors of a template. So, if the file exists the user cannot edit the template, but their username is added to the lockfile and they will be emailed when the template becomes free for editing.
The problem is the format of the lockfile. As an example we have:
user1 (2020-05-29 13:22:46)*user2 (2020-06-09 09:37:20),
where 'user1' is the creator of the lockfile, the user currently editing the template. 'user2' is a user who has tried to edit the template, failed, and their username added to the lockfile.
However, looking at the code in the 'website_code/php/versioncontrol/template_close.php' file, the lockfile creator is extracted by 'exploding' the file based on the asterisk(*) character. The user email addresses are obtained by exploding the rest of the file based on the space character.
But looking at the example above, this would gives the users as 'user2', '(2020-06-09' and '09:37:20), ' - the last two of which are obviously wrong.
This seems to come from the 'edithtml.php' file. The commit adding in the date to the lockfile is ('Add date to lockfile' -  Tom Reijnders committed on 5 Apr 2018 ) https://github.com/thexerteproject/xerteonlinetoolkits/commit/1b95c7b027aa19e7a95dcdc4551f3bf60438d9ce#diff-9093bd6670cd6396b8318cc62d2847cb
I don't know why the date is added - it doesn't seem to be used - but for non-creator users it seems like it shouldn't be included. After the asterisk it should just be a space-separated list of usernames.
I'll see if I can do some testing without the date being added
John.

@jayaich I don't know what the original idea was to do it like this. I don't know if the lock date was added at that time, or all the dates. However, it is important to make sure this works properly, because we intend to use the lockfile more (even to lock oneselve, to try and prevent users from opening the editor window more than once (in a different tab, or a different browser).
I could also imagine that we use the dat in the email, to indicate when the request was made (when the user tried to edit the file).
So, for me the explode on space in template_close.php should have been an explode on ',' and than an explode on space to get the username.
Hope this helps.

Pull request #914 merged.


Create Project updates

@Ruthie2018 all the tickets in this done from a DEV standpoint. I also remember @EdemD saying that he finished testing on the last ticket #1067 . So, if he is done, you can close this epic


Fix typo

Github -> GitHub

@changeworld : Thanks for your contribution! The author, @ShubhaVijayasarathy, has been notified to review your proposed change.

Merging typo fix


Include EntityRelationship (ER) diagram to DownloadMenu

is there any psql command to create the ER diagram?

This will be fulfilled by #181


Header cells changed CSS after update

Hi,
After I updated the version from 3.7.0 to 3.7.7 my table headers CSS changes to button CSS (For example: on hover there is a grey background, etc..)
Is that a correct behavior should it affect my default CSS of the table header cell?

Also some header cells are bold, some are not. This is not the case with 3.7.4


[WIP] moving my improvements upstream

The intent is not merging this PR as is, but using it as a big todo list.

The intent is not merging this PR as is, but using it as a big todo list.

Ok, I'll take a look this evening. Thanks for putting this together!


Add Araxis Merge 2024.6001

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Hi @gjmatthews,
This manifest adds a DisplayVersion to the AppsAndFeaturesEntries that isn't present in previous manifest versions. This entry should be added to the previous versions, or removed from this version.
(Automated response - build 895.)

Hi @gjmatthews,
This manifest adds a DisplayVersion to the AppsAndFeaturesEntries that isn't present in previous manifest versions. This entry should be added to the previous versions, or removed from this version.
(Automated response - build 895.)

I have added the AppsAndFeaturesEntries to the previous manifest versions. Please see:

https://github.com/microsoft/winget-pkgs/pull/173755
https://github.com/microsoft/winget-pkgs/pull/173756

We have added the AppsAndFeaturesEntries entry to our manifests to hopefully fix a winget upgrade problem we are seeing. winget upgrade doesn't appear to be able to correctly match the installed version of Merge, such that repeated calls to winget upgrade continuously re-install the same version of Merge. This problem also occurs when testing a local copy of the updated manifest files: winget upgrade --manifest <MANIFEST_DIR>. Do our manifest files look correct with regards upgrade version checking?

@stephengillie Please kill this PR; see my comment on the related PR: https://github.com/microsoft/winget-pkgs/pull/173756#issuecomment-2356586001


Fix : Fix the height of whole application [fixes #39]

Fix the height of whole application [fixes #39]

it's still scrolling a little, reducing the number of those genre and top charts didn't do much because those are fixes sizes so after reducing the number of genre of top charts makes extra space only and not change the height, what we have to do is decrease padding and gap and make things a little smaller and that'll go away

yeah makes sense, we'll look into it again after the top charts section is done

see, if you don't limit the number of Genre, then the list will go down and down. it will not help to keep the height fixed.
and there is a see all button also. that's why i fixed the Genre list. the same applicable to top charts.
if you still want to fit in a single screen, then the design will be affected. we need to reduce images sizes and spaces.

We can fix the genre section and can make it scrollable from inside..what do u say? Just an opinion of mine

see, if you don't limit the number of Genre, then the list will go down and down. it will not help to keep the height fixed.
and there is a see all button also. that's why i fixed the Genre list. the same applicable to top charts.
if you still want to fit in a single screen, then the design will be affected. we need to reduce images sizes and spaces.

We can fix the genre section and can make it scrollable from inside..what do u say? Just an opinion of mine

yeah ig that would be best because top-charts component is definitely gonna take much more vertical space so we can make both scrollable

i dont think it will help the cause. then why do we have a "see all" button ?

"see all" is for their separate pages, where there'll be much more genres and separate listings of songs of those genres

"see all" is for their separate pages, where there'll be much more genres and separate listings of songs of those genres

That's what i'm saying. at the home page, why we need to display every genre tags if there is a separate page for displaying it all.

"see all" is for their separate pages, where there'll be much more genres and separate listings of songs of those genres

That's what i'm saying. at the home page, why we need to display every genre tags if there is a separate page for displaying it all.

Yeahh I think you're right!! We can just limit our genre on the homepage..

yeah we keep it like that, we'll look into it after we have top-charts component done


Initial implementation of metadata indexing

metadata indexing
also updated syntax of elasticsearch dependency injection

If it's possible we might to think about what will the search interface of metadata looks like. Right now the query syntax of search works; but because the record for metadata is so different than "dataset" or "file", how can we display the result?

If it's possible we might to think about what will the search interface of metadata looks like. Right now the query syntax of search works; but because the record for metadata is so different than "dataset" or "file", how can we display the result?

I agree that it looks different. We can probably discuss this and address this in a separate PR.

Could we index enough information about the file or datasets in the metadata index? If a user searches for metadata, they probbaly just want to see the file or dataset it belongs to.

Right now, we have dataset_id and file_id in the metadata index. we can ad more info or just retrieve the info from mongo using the id

When I first add metadata to a dataset, the elasticsearch document has the contents under doc.contents. But if I update that entry, the new value is stored under 'contents. For example, this is what it looks like for a field called alternateName.

Looking into this.

@lmarini I addressed the above issue. Great find, thanks! We don't need 'doc' while inserting record but need that while updating it.


Select Spell Alerts

Spell Activation Overlays (SAOs) could be selected individually.
These options would be set in the Interface > AddOns > SpellActivationOverlay panel, with a new subcategory for each class.
This issue is the SAO counterpart of the GAB evolution described in #61.

Implemented in #90.
Each class only sees its own Spell Alerts.
They are setup in the top-right corner of the options panel.
Spell Alerts are grayed out if the Spell Alert Opacity slider is set to "Off". This behavior is identical to when the "Toggle Test" button is grayed out.


Fix default arrow build

Which issue does this PR close?
Built on https://github.com/apache/arrow-rs/pull/532 so review that one first
Closes https://github.com/apache/arrow-rs/issues/529
Rationale for this change
Arrow does not build today unless rand 0.8 is included as another dependency of the project; I introduced this in #488 when I upgraded the rand dependency but disabled the default features (which require sys which mean arrow can't be built on webasm anymore)
Since the only use of the sys part of the rand dependency is in benchmarks  and testing code, I propose simply not building that part of of the arrow crate if default features are turned off
What changes are included in this PR?

Bring enough of the rand crate in by default to build, and #ifdef out their use when arrows default features are disabled

Are there any user-facing changes?
There is a test_utils feature flag now, enabled by default, that gates what parts of arrow are compiled if the default features are turned off

It would be nice to have all this test only code somewhere that wasn't the actual arrow crate at all, but since the test code has a backwards dependency on arrow -- (arrow <--> test_util) -- we would have to break that cycle as well, which is a lot of code churn

FYI @ritchie46  and @joshuataylor

Codecov Report

Merging #533 (abd8cfe) into master (f1fb2b1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #533   +/-   ##
=======================================
  Coverage   82.60%   82.60%
=======================================
  Files         167      167
  Lines       45984    45984
=======================================
  Hits        37984    37984
  Misses       8000     8000

Impacted Files
Coverage Δ

arrow/src/util/bit_util.rs
100.00% <ø> (ø)

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 f1fb2b1...abd8cfe. Read the comment docs.

I have tested this by removing rand from my Cargo.toml and then changed arrow to this:
arrow = { git = "https://github.com/alamb/arrow-rs", branch = "alamb/fix-arrow-default-build" }

And everything works well. :+1:


Support publishing/management of function versions

& aliases, I guess.

Simplest thing would be to have deploy take a boolean :publish arg, have it output the version, and then support an alias creation command (could have this be data-driven from project file, eventually).  Need to make sure invoke works w/ ARNs which have the version embedded also.

0.5.0-SNAPSHOT


Use DiceBear API to create a random avatar and display it in the Lobby and Profile

https://github.com/sopra-fs23-group-40/Client/commit/db185913a69a7a2f99dff413c81fd6b2e6d1416d


Mysterious fuchsia/sdk/core.tar.gz showing up in license checker runs

In https://github.com/flutter/flutter/issues/126441 it was noted that the license checker was failing against .rom files inside of the fuchsia/sdk/core.tar.gz file.  @aam mentioned that those files shouldn't even be there.
https://github.com/flutter/engine/pull/41900 made it so that those files aren't erroneously read as utf8 files, but for performance reasons we should identify where core.tar.gz is coming from.

Looking at the DEPS file, gclient doesn't appear to put anything directly in fuchsia/sdk.  There is code to fill in fuchsia/sdk/mac and fuchsia/sdk/linux.  https://github.com/flutter/engine/blob/7ad6470717e61938cfe57b56deb168ef7fae2abe/DEPS#L880

Could it be coming from https://flutter.googlesource.com/recipes/+/refs/heads/main/recipes/engine/femu_test.py#998 ?
Hypothesis is that the buildbot that gets license script task had this femu script run at some point in the past, which polluted fuchsia sdk folder with this core.tar.gz file.
Running this license task with clobbering enabled might solve this too.

Sounds plausible, looking at the history of that bot that failed, it does have some executions of fuchsia tests: https://chromium-swarm.appspot.com/bot?id=flutter-try-ubuntu-us-central1-a-41-nglc

@aam note that you are pointing to the recipe for the old engine.  The failing check was on an engine_v2 run.  The way we determine to clobber files with engine_v2 is a bit different.

Found the root cause(s):
@aam is correct, fuchsia femu test is leaving behind <cache>/builder/src/fuchsia and engine_v2 optimizes the clobber logic to only delete <cache>/src/out. E.g. https://ci.chromium.org/p/flutter/builders/prod/Linux linux_license/20
The second issue is related to web_engine builds wich generate files inside <cache>/src/flutter. E.g. https://ci.chromium.org/p/flutter/builders/prod/Linux linux_license/16
We have two different options:

Clobber the entire /builder as in the legacy builder
Optimize the workflows placing the fuchsia artifacts inside <cache>/builder/src/out. Deleting  <cache>/builder/src/out is the first step on every build and will ensure the fuchsia folder does not impact any other builder. In addition to that we'll need to run a hard reset to ensure all the web_engine artifacts are removed. An optimization will be to generate the engine artifacts in out.


Where is exe file?

I cant find exe file.

On the release page, if you click on the TPFC2_2.1.5.zip link, it will download the .zip file that includes both fancontrol.exe executable and TPFanControl.ini config file, make sure to have both of them in the same directory in order for it to run properly.
Also, make sure to have tvicport installed in order for the program to function, you can find it here


harmonoid: Fixed install-harmonoid-associations.ps1 so it can correctly install associations.

Relates to https://github.com/ScoopInstaller/Extras/pull/10637

[x] I have read the Contributing Guide.

@rashil2000


Zigzag encoding fix for signed integer

This PR applies the changes according to this topic https://developers.google.com/protocol-buffers/docs/encoding#signed-ints
Signed Original	Encoded As
0	            0
-1	            1
1	            2
-2	            3
2147483647<PHONE_NUMBER>
-2147483648<PHONE_NUMBER>

fyi @Rantanen

Thanks! Sorry for slow reaction. Broke my arm a while ago, but fortunately this PR looks good enough to merg as is!

Aw. Unfortunately rust fmt checks are failing. Can you run cargo fmt, commit changes and push that? (Might need rustfmt component to be installed).

For some reason that fmt pass did not follow the rustfmt.toml in the crate root.

Still doesn't look right. A simple cargo fmt should do it, if executed in the crate root:
~/protofish$ cargo fmt

Not sure what is causing the issue on your end. I'll do it myself (mostly to avoid typing more with one hand). :)

(Not sure when the line endings had changed, that didn't help things - your fmt pass definitely made those better though!)

thank you Mikko for amazing library and review!
sorry, looks like I have too old rust tools on my personal laptop:
Warning: can't set `brace_style = AlwaysNextLine`, unstable features are only available in nightly channel.

Oh, could be I'm also reöying on nightly fmt myself so I'll take part of the blame there! Unfortunately I don't want to drop that rule until fmt stops dropping empty lines at start of functions.
In any case it's merged now! Thanks for the contribution!

Published 0.5.2 on crates.io.


Fixed wrong delegation for ns()

Thanks very much for the bug fix @rhuss, that was a nasty copy/paste error.


Dapr uninstall -k does not remove the CRDs

Expected Behavior
dapr uninstall -k remove the CRDs
Actual Behavior
$ dapr uninstall -k
ℹ  Removing Dapr from your cluster...
✅  Dapr has been removed successfully
$ kubectl get crds
NAME                     CREATED AT
components.dapr.io       2021-03-31T01:24:00Z
configurations.dapr.io   2021-03-31T01:24:00Z
subscriptions.dapr.io    2021-03-31T01:24:01Z

Steps to Reproduce the Problem

install dapr using dapr init -k.
run kubectl get crds
run dapr uninstall -k
run kubectl get crds
the crds still exist.

Release Note

RELEASE NOTE: RESOLVED dapr uninstall -k does not remove CRDs

Closing this as removing CRDs also removes any components, configurations and subscription CRs from the cluster.

Can we at least add a flag or something?

Adding an --all flag.