Composer upgrade 2.1.2 => 2.1.3 results in broken CMS, HTTP 500 error

Earlier I have used composer at least once to succesfully upgrade pico.
Now I'm getting this error when I visit my blog. Completely blank page, no code in "View source" either.
I can't see anything in /var/log/nginx/error.log, /var/log/php7.0-fpm.log or /var/log/syslog or in the respective service's systemd status.
I do see the access in /var/log/nginx/access.log:
X.X.X.X - luser [01/Aug/2020:17:35:02 +0300] "GET / HTTP/1.1" 500 5 "-" "Mozilla/5.0 (Windows NT 10.0; rv:78.0) Gecko/20100101 Firefox/78.0"
But that's all.
I removed the server root dirctory and "composed" a completely new instance of pico, and it gives me the same error.
I emptied composer's cache.
I tried this twice, with composer 1.8.4 installed on my system (Debian stable) and composer downloaded straight from their site.
I checked nginx' settings as per http://picocms.org/docs/#nginx, it needed a little adjustment but really I don't think they changed at all since the last version?
What changed between now and then? IDK; a few OS upgrades, editing my custom theme.
Just to prove that the server is serving, I can replace the webroot directory and place a single index.php in it which shows me phpinfo(); - it works. This is the staging version of my blog; all the while the production version, which is still at 2.1.2, works normally.
This is what composer (newest version) told me:
$> php composer.phar --verbose create-project picocms/pico-composer staging
Creating a "picocms/pico-composer" project at "./staging"
Installing picocms/pico-composer (v2.1)
  - Installing picocms/pico-composer (v2.1): Downloading (100%)
 Extracting archiveCreated project in /var/www/html/staging
Loading composer repositories with package information
Updating dependencies (including require-dev)
Dependency resolution completed in 0.023 seconds
Analyzed 2272 packages to resolve dependencies
Analyzed 1969 rules to resolve dependencies
Package operations: 9 installs, 0 updates, 0 removals
Installs: picocms/composer-installer:v1.0.1, erusev/parsedown:1.8.0-beta-7, erusev/parsedown-extra:0.8.0-beta-1, symfony/polyfill-ctype:v1.18.0, symfony/yaml:v2.8.52, twig/twig:v1.43.0, picocms/pico:v2.1.3, picocms/pico-deprecated:v2.1.3, picocms/pico-theme:v2.1.3
  - Installing picocms/composer-installer (v1.0.1): Downloading (100%)
 Extracting archive  - Installing erusev/parsedown (1.8.0-beta-7): Downloading (100%)
 Extracting archive  - Installing erusev/parsedown-extra (0.8.0-beta-1): Downloading (100%)
 Extracting archive  - Installing symfony/polyfill-ctype (v1.18.0): Downloading (100%)
 Extracting archive  - Installing symfony/yaml (v2.8.52): Downloading (100%)
 Extracting archive  - Installing twig/twig (v1.43.0): Downloading (100%)
 Extracting archive  - Installing picocms/pico (v2.1.3): Downloading (100%)
 Extracting archive  - Installing picocms/pico-deprecated (v2.1.3): Downloading (100%)
 Extracting archive  - Installing picocms/pico-theme (v2.1.3): Downloading (100%)
 Extracting archiveWriting lock file
Generating autoload files
> post-autoload-dump: Pico\Composer\Installer\PluginInstaller::postAutoloadDump
Creating Pico plugins file
3 packages you are using are looking for funding.
Use the `composer fund` command to find out more!

I don't see any problem there.
To clarify:
The webroot is ./staging.
This results in a non-working pico CMS, with a generic 500 a.k.a. "Internal Server Error".
Using the installed version of composer also results in a non-working pico CMS.
This is a new install - but the same happened when I updated my current staging site.
But then:
I downloaded the release tarball, extracted it to the webroot, and It Worked!
What is going on?
:o
I would prefer the composer method for easier upgrading, keeping configurations intact etc.

Thank you for removing the "stale" label.
Yes, this is still very moch Not Solved.

Sorry for the late response. A blank page indicates a PHP error. Check your webserver config, it looks like your PHP error log isn't configured properly. See e.g. https://stackoverflow.com/questions/8677493/php-fpm-doesnt-write-to-error-log. You can also set display_errors = 1 in your php.ini temporarily, it should show the error message then
Since Pico doesn't lock the versions of its dependencies, I'd assume that there's some incompatibility between one of the dependencies and your PHP version. Since Pico's release packages are working for you, I'd recommend simply using a release package. It makes no difference, a release package is exactly the same as a Composer-based install. You can try running composer update on a release package, but I'd assume that it stops working again, because the dependencies are upgraded to the same versions as if you created a Composer-based install from the beginning.


Rasa X doesn't load all stories or rules

Raising issue here for visibility, because a forum user brought this to my attention.
Rasa version: 2.1.2
Rasa X version (if used & relevant): 0.34.0
Issue:
Rasa X 0.34.0 only loads 20 of your stories when going to the stories screen. This definitely wasn't an issue in 0.33.0 (I tested it out on the killer-demo instance beforehand). Sara has 200+ stories, and only 20 of them are there in the updated 0.34.0 instance. Take a look at the screen recording here: https://drive.google.com/file/d/1mN4yVx9DjbSsCO0J0cFMl8DaKDivcN8d/view?usp=sharing
You can investigate this issue on the killer-demo instance (website-demo dot rasa dot com).

Firstly, this also appears to affect the rules view also so I've updated the issue.
@federicotdn I've been looking into this and I think this may be because the backend is not returning the correct total value, however, I'm not sure when this changed. I noticed the total value returned for a call to the /stories or /rules endpoints only return the total fetched (so with a limit of 20, total will be 20, even if there are 40 more fetched stories/rules).
Do you know if this changed during 2.0, or at any stage? Acc. to the issue this wasn't a problem in 0.33 but became visible in 0.34.
For comparison, if we call the fetch conversations /conversations endpoint with a limit of 20, we get 20 conversations but total still equals the total number of conversations eg: 202. We use this total value for our virtualised lists in the table, so if the value is reached we don't fetch anymore.

Firstly, this also appears to affect the rules view also so I've updated the issue.
@federicotdn I've been looking into this and I think this may be because the backend is not returning the correct total value, however, I'm not sure when this changed. I noticed the total value returned for a call to the /stories or /rules endpoints only return the total fetched (so with a limit of 20, total will be 20, even if there are 40 more fetched stories/rules).
Do you know if this changed during 2.0, or at any stage? Acc. to the issue this wasn't a problem in 0.33 but became visible in 0.34.
For comparison, if we call the fetch conversations /conversations endpoint with a limit of 20, we get 20 conversations but total still equals the total number of conversations eg: 202. We use this total value for our virtualised lists in the table, so if the value is reached we don't fetch anymore.

@mjaycub I've checked the code for the stories API and it seems like the value of X-Total-Count is always being set as the length of the stories array being returned, see here. Unfortunately that line of code has been shifted around, but the behaviour has always been like that it seems. I've tracked the change back to March 22nd, 2019 here, when we migrated from MongoDB to SQL.
So the fix for this would be on the backend. Note that we did this change (https://github.com/RasaHQ/rasa-x/pull/3940) recently, which means that we are no longer ignoring offset/limit sent by the frontend - I assume these two values will be sent correctly (i.e. they will be paginated correctly) once we fix the X-Total-Count thing.

Thanks for checking this out @federicotdn 🙏  We may have accidentally been solving this since the code hasn't changed, but I think now that we've found it we should fix it properly.
I'll tag this with backend tag and update the description here for our backlog if that sounds good to you?

Closing this as it’s been solved in another Rasa X issue

Hi am facing same issue. I have 38 stories in total but rasa-x UI is showing only 20 and it is training with 20 only.
Please help.

@mishra011 can you let us know what version of rasa and rasa-x you are using?

Hi @mjaycub
Rasa version: 2.1.2
Rasa X version : 0.34.0

@mishra011 according to our changelog, it looks like we fixed this issue in the 0.36.0 release.
Today we're up to version 0.41.0 of Rasa X which I would recommend upgrading to from 0.34.0 to get all of the recent bug fixes and features.

Thanks , @mjaycub  I will try newer version and let you know.


Roadrunner 2.0 Support

Description
Roadrunner 2.0 was released a few days ago, but this project's main.go file is still pointing to github.com/spiral/roadrunner/cmd/rr/cmd (and this folder doesn't exist anymore in the master branch?)
Example
Forgive my ignorance, but to compile my own Go RPC services I've been using:

https://github.com/spiral/framework/blob/master/main.go

The conventions seem to have changed and I don't understand what do to with the Spiral main.go file anymore, ie.

https://roadrunner.dev/docs/beep-beep-build
https://github.com/spiral/roadrunner-binary/blob/master/main.go

So, this feature request is to support roadrunner V2 out-of-the-box and to clarify the docs, example:

https://spiral.dev/docs/cookbook-golang-library

("Read more about RoadRunner services here." links to a beep-beep-service page that is now 404.)

Thank you for your consideration.

In the new мersion of the framework (master aka 2.8), we are preparing support for RR2. Optional, because dependencies of the second RR version requires php 7.4+.
So far, not all plugin functionality is ready (https://github.com/spiral/roadrunner/issues/403), so I'm not ready to provide an exact release date and update installation instructions (i.e. documentation) right now.
However, the current master branch already supports both RR1.9 (spiral binary) and RR2 (rr binary) in HTTP mode.
It should be noted that in subsequent releases there will no longer be direct dependencies of the framework on the RoadRunner, (including main.go), however, it will remain as the recommended application server for the framework and many optional components will use this particular implementation.


[Feature]: Forgot Password is an empty file?

How the project can be improved?
The reset password page is empty, looks like the reset password is missing.
https://github.com/vuestorefront/shopify/blob/main/packages/theme/pages/ResetPassword.vue
Is it something related to a specific integration? Maybe it is different beetwen Shopify, Magento, ... ?
What are the acceptance criteria?

[ ]

Additional information
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Fixed and closed by #335


chore(deps): bump dav-server from 0.5.5 to 0.5.7

Hi, thanks for the PR. But I feel like this PR is meaningless.


Multiplying upsampled features by 2

Could you please explain what is the reason for multiplying feat_up by 2 here https://github.com/EMI-Group/FaPN/blob/main/detectron2/modeling/backbone/fan.py#L66 ?

Hi, thanks for your interest in our work. We enlarge the magnitude of upsampled features in case of suppression.

or your interest in our work. We enlarge the magnitude of upsampled features in case of suppression.

Thanks for your awesome work. Could you explain detailly? What happens if I don't multiply by 2 and have you ever tried to multiply by a learnable variable?

or your interest in our work. We enlarge the magnitude of upsampled features in case of suppression.

Thanks for your awesome work. Could you explain detailly? What happens if I don't multiply by 2 and have you ever tried to multiply by a learnable variable?

Sorry for the late reply. You can have a look at the EDVR


use baseDir for path defined in config file

Quick one-line fix.
In #1820 you have introduced introspection cache functionality, as discussed before.
However, as suggested in PR review, we should use baseDir for the introspectionCache file and not process.cwd().
This is because the file path is defined in Mesh Config file, and not as a command argument.
Anything inside the Mesh Config file should always be relative to the baseDir the same Config file lives in.

Oh I missed that! Thanks @santino !


feat: /price-feeder: main price feeder loop

Description
Implement main price feeder loop
closes: #178

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[x] included the correct type prefix in the PR title
[x] added ! to the type prefix if API or client breaking change
[x] targeted the correct branch (see PR Targeting)
[x] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[x] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed ! in the type prefix if API or client breaking change
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

Codecov Report

Merging #237 (2639677) into main (be6654a) will decrease coverage by 0.45%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #237      +/-   ##
==========================================
- Coverage   27.92%   27.47%   -0.46%
==========================================
  Files          57       57
  Lines        8139     8274     +135
==========================================
  Hits         2273     2273
- Misses       5660     5795     +135
  Partials      206      206

Impacted Files
Coverage Δ

x/leverage/types/query.pb.gw.go
0.00% <0.00%> (ø)

x/oracle/types/query.pb.gw.go
0.00% <0.00%> (ø)

x/peggy/types/msgs.pb.gw.go
0.00% <0.00%> (ø)

x/peggy/types/query.pb.gw.go
0.00% <0.00%> (ø)

Closing this PR to move the client logic into its own


x/tools/gopls: document code actions that gopls supports

From discussion on gophers slack: it would be nice if gopls documented supported code actions, similar to how it documents other parameterized features (such as inlay hints: https://github.com/golang/tools/blob/master/gopls/doc/inlayHints.md).
Supported code actions are provided part of the initialize handshake, but we could document more precisely what we support.

can i work on this...?

@advinsuryavanshi yes, contributions are very welcome!
However, be warned that we may want more than just pure documentation here. As much as possible, we try to generate our documentation from the gopls source. This prevents duplication, and helps ensure that documentation doesn't go stale. It also makes it easier to compile our documentation into JSON that can be read by editors. You can see examples of this in x/tools/gopls/doc/generate.go.
I haven't thought too much about code actions, but we should try to do something similar, basing our documentation off of x/tools/internal/lsp/source.DefaultOptions().SupportedCodeActions. One way to enforce that we have documentation would be to change the type of SupportedCodeActions. For example:
	SupportedCodeActions map[FileKind]map[protocol.CodeActionKind]string // file kind -> action kind -> description

In the future we could also go further and try to refactor such that code actions are parameterized, similarly to inlay hints (see x/tools/internal/lsp/source.AllInlayHints), but I don't think it is wise to undertake that refactoring now.
CC @suzmue @jamalc who may have opinions, having just done this for inlay hints.

Just piping in to ask a naive question: is this intended to replace (the presumedly manually maintained) https://github.com/golang/tools/blob/master/gopls/doc/commands.md ?

@jadekler sorry for missing your question. Code actions may return either workspace edits or commands, so there is a lot of overlap with the command documentation but they are distinct. I think the point of documenting code actions is that users can bind keys to specific code action workflows.
I recently refactored the code action code somewhat for performance reasons (https://go.dev/cl/511995), after which it is slightly easier to see which code action kinds are supported.
I don't think we need to block this issue on perfectly parameterize the code action code. If anyone wants to help out on this, I think it would be suitable to start out with manual documentation:

create a codeActions.md at https://github.com/golang/tools/tree/master/gopls/doc
read through the source code at https://github.com/golang/tools/blob/master/gopls/internal/lsp/code_action.go, searching for protocol.<name> to see where different code action kinds are handled.
document each supported code action kind, and approximately how it is implemented (for example, we can say that organizeImports integrates with goimports).

In the future, it would be nice to have a code action dispatcher similarly to what we have for the executeCommand request. At that point perhaps we could automate documentation.
@adonovan is currently working on refactoring (doing some very exciting work on inlining!), so now is a good time to start revisiting this code and documentation.


🤔 No option for width of dropdown?

Does bootstrap-select offer a width attribute for the content (If you open the select picker)?
Everything I can find is that bootstrap-select offers a data-width="" attribute for the width of the select field. (Before you open it)
In my case the content of the selectpicker is larger than the available width and now it makes my website scrollable horizontally (after opening it), what I don't want.
This feature should already be built in? But I can't find it?
Any help is highly appreciated!

Fix: Use dropdownAlignRight: 'auto'

still need this
No option for width of dropdown?


Update version number

I published artifact to Maven Central as 0.1.0. Version numbers should be changed.

CC @noam-almog


Change: Allow for empty variable values

Updates the Variables tabs to allow for variables to be created/updated with no value defined.
Includes confirm pop-up when adding/updating variable to have a null value.

Displays empty variables with a Tag component:

This looks good for entering, but we need to consider how to display an empty var - having a dash may be confusing, but not sure what the alternatives are

This looks good for entering, but we need to consider how to display an empty var - having a dash may be confusing, but not sure what the alternatives are

Pulled in the Tag component from antd, thoughts?


[SPARK-23099][SS] Migrate foreach sink to DataSourceV2

What changes were proposed in this pull request?
Migrate the foreach sink to the DataSourceV2 API.
How was this patch tested?
existing unit tests, and new test to verify edge case

/cc @tdas

Can one of the admins verify this patch?

Test build #87230 has started for PR 20552 at commit 44de1ea.

Test build #87230 has finished for PR 20552 at commit 44de1ea.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class ForeachWriterProvider[T: Encoder](writer: ForeachWriter[T]) extends StreamWriteSupport
case class ForeachInternalWriter[T: Encoder](
case class ForeachWriterFactory[T: Encoder](writer: ForeachWriter[T], encoder: ExpressionEncoder[T])
class ForeachDataWriter[T : Encoder](

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/87230/
Test FAILed.

Test build #87231 has started for PR 20552 at commit 87d0bc8.

Test build #87231 has finished for PR 20552 at commit 87d0bc8.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/87231/
Test FAILed.

Test build #87241 has started for PR 20552 at commit a33a35c.

It's my intent to say that other data sources built by general developers aren't supposed to use batch ids in the executors for any purpose. In addition to the issue you mentioned, I don't think there's a compelling reason to do so in the DataSourceV2 model, and I worry it's easy to write implementations that seem correct but aren't that way.
Since this interface is still evolving, I think it makes sense to revisit the question if we notice a scenario where it's infeasible to rewrite a piece of transactional logic to not use the batch ID in the executor.

Test build #87241 has finished for PR 20552 at commit a33a35c.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/87241/
Test FAILed.

Filed SPARK-23416 for the unrelated failure in build 87241.

Test build #87417 has finished for PR 20552 at commit 66270c5.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/87417/
Test FAILed.

This is obsolete - we're changing the lifecycle of DataWriter.


Fix Performance Pipeline Profiling when Using Java 17

Fixes/adds support for running performance pipeline profiling when running with both Java 8 and Java 17.

/check-enforcer override


*: support env

Most code are copied from rust-rocksdb/src/env.rs, but with more docs
and refactor.
The most notable differences are:

Use rocksdb::Env directly instead of custom type;
Use rocksdb::Status as error handling;
Files are reorganized following rocksdb's definitions.

can we move the original files with one PR first? so we can get the difference easily.

That will bring a lot of noises. For example, during all the patches, we need to make them pass CI, so many unnecessary changes will be introduced.


Add American Truck Simulator

The game requires additional setup which are linked in the ExtraSetupStepsURI. Linux only or Docker on Windows as there are issues running as NETWORK SERVICE in Windows.
After this is fully reviewed, I'll convert it to work for Euro Truck Simulator 2 as well.

I do own this game and tested on my own client. I was able to connect and it showed in the server browser properly.

To provide some context on this, ATS and ETS2 require you to go into your game files and generate a couple files using developer mode. The official documentation about ATS and ETS2 dedicated servers can be found here: https://modding.scssoft.com/wiki/Documentation/Tools/Dedicated_Server

Thanks! That's already addressed in this wiki article which should be displayed when setting this up within AMP.
https://discourse.cubecoders.com/t/american-truck-simulator-euro-truck-simulator-2-guide/3790


Fixed pixel rounding in PIXI.TilingSprite.prototype._renderCanvas.

Changed "x|0" to "x |= 0" in PIXI.TilingSprite.prototype._renderCanvas.

Thanks for the fix. I can't merge because you issued the PR against master, but have fixed it locally in dev.


ACL rework to avoid "man in the middle" vulnerability

The actual ACL mechanism mainly uses the calling account address to check resource owner/writer rights before doing something. It works well when an account directly calls a world function, but if this account calls a contract which calls a world function, it lets the possibility to this middle contract to use the calling account privileges to do some malicious things.
Today, a world offers 2 kinds of functions:

management functions: to manage resources in the world (deploying/upgrading contracts, registering models and namespaces, grant/revoke roles, ...). These functions are used through sozo.
usage functions: to use these world resources (write/delete data to a model for example). These functions are mainly use through Dojo systems.

This PR implements the following solution to avoid this "man in the middle" vulnerability:

an owner in Dojo is always an account,
a writer in Dojo could be an account or a contract (Dojo systems),
management functions must be directly called from an account (that means, in the called function get_caller_address() must be equal to get_tx_info().unbox().account_contract_address),
In usage functions, we use the caller contract privileges and not the calling account privileges to know if the action can be done.

Here is a summary of possible actions for ower/writer role for each resource:

Owner
Writer

Namespace
grant/revoke owner/writer for the namespaceregister model / deploy contract in the namespace set_entity / delete_entity for models in the namespace
set_entity / delete_entity for models in the namespaceregister model / deploy contract in the namespace

Model
grant/revoke owner/writerupdate modelset_entity / delete_entity for the model
set_entity / delete_entity for the model

Contract
grant/revoke owner/writerupdate contractcheck execution permission*
check execution permission*

World
grant/revoke owner/writerupgrade worldregister model / deploy contractupdate model / contract
N/A

this is a possible future feature to describe later.

Hi @glihm @lambda-0x
If you want to have a look at this ACL rework ;-)
There is an issue with the dojo_init function of mock_token which try to write to the MockToken without the writer role. So, if we agree with this rework, we should find a way to setwriter permissions before the execution of dojo_init.

There is an issue with the dojo_init function of mock_token which try to write to the MockToken model without the writer role.  So, if we agree with this rework, we should find a way to setwriter permissions before the execution of dojo_init.

yeah thats the limitation of dojo_init currently, since we cannot grant access to it before its registered in the world.


[WIP]Support protobuf3.

can support both protobuf3 and protobuf2 now.
close #100

close this pr temporarily.

@MrKingHH master已支持protobuf 3.x


Chart shrinking uncontrollably on browser zoom

Expected behavior
I expect the chart canvas to remain an appropriate size when changing the zoom in the browser (Ctrl + Mousewheel).
Current behavior
The chart initially renders correctly, but then slowly shrinks toward its top-left corner until it disappears, then re-renders at its initial size. This loop repeats indefinitely.
Reproducible sample
https://codepen.io/leelenaleee/pen/WNyJXEe
Optional extra steps/info to reproduce
To reproduce, change the browser zoom to 90% (Ctrl + Mousewheel down).
The chart behavior is different at various zoom levels. At 110% zoom, for example, it only shrinks to a certain point and then stops.
Note that this bug is also active on the chart.js documentation site on every chart example.
This bug does not happen in Firefox 109.0 (64-bit), but it does happen in Google Chrome Version 109.0.5414.75 (Official Build) (64-bit).
Possible solution
No response
Context
No response
chart.js version
v4.2.0
Browser name and version
Google Chrome Version 109.0.5414.75 (Official Build) (64-bit)
Link to your project
No response

Souds like a duplicate of https://github.com/chartjs/Chart.js/issues/10932 which was already fixed and should not happen in this version, I also don't see the behaviour you specified in this version.
Are you sure you are using v4.2.0?

This gif shows the issue I mentioned. It is on the chart.js documentation site. I am assuming the site would be using the latest version of chart.js, and the documentation indicates it is v4.2.0 (visible in the gif). The site is opened using Google Chrome, at 90% zoom.
I reviewed #10932 and it looks like it is exactly this problem.
From what I've gathered, it may be an issue isolated to the combination of a Windows OS and Google Chrome browser. In particular, someone else running Linux does not have the same issue on their Chrome browser, but it does happen on other Windows machines. As I mentioned earlier as well, the behavior does not happen when I try to reproduce it on Firefox.
To be thorough, I double-checked the chart.js version in my project. It was at v4.1.2, which has now been upgraded to v4.2.0, but the issue remains. Considering the example I shared in the gif, however, I don't think my project setup is relevant to the issue.

Same for me in 4.2.0 with browser zoom is set to 116%. It zooms to zero and again when the mouse lay over the chart. I'm using the umd variant.

@TrevorThiessen57 @fly74 Hi. Could you please share OS and browser versions?

@TrevorThiessen57 Sure, Windows 11 latest updates and Edge Version 109.0.1518.69.

@dangreen Windows 10 Pro 64-bit Version 21H2 OS build 19044.1645, and Google Chrome Version 109.0.5414.120 (Official Build) (64-bit)

@fly74 @TrevorThiessen57 Could you also share screen resolution?

@dangreen 3840 x 2160

@fly74 @TrevorThiessen57 Could you also share screen resolution?

3840x2160 (4K)

I don't have access to a screen with that resolution. Anyone knows of a trick to simulate that?

You can use Remote Desktop to another machine and set the resolution via cli. You have then scrollbars in the rdp window.

@gbaron You can use browserstack.com, but I'm already tried and can't reproduce this bug.

It is strange, it only happens when zoom is 116% in my case, 110/125 % works. :/
Maybe a function with round problem ?!?

Could you please share what is the value of Window.devicePixelRatio when
zoom is 116%?
On Sat, Jan 28, 2023 at 13:30 fly74 @.***> wrote:

It is strange, it only happens when zoom is 116% in my case, 110/125 %
works. :/
Maybe a function with round problem ?!?
—
Reply to this email directly, view it on GitHub
https://github.com/chartjs/Chart.js/issues/11089#issuecomment-1407458584,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAICJ3E7EYWQR5TV2OOT4ELWUVQSPANCNFSM6AAAAAAUFGGMGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Could you please share what is the value of Window.devicePixelRatio

How can I get the Window.devicePixelRatio?

I can easily reproduce this on a mac with chart.js 4.1.0, but with 4.2.0 I can't. Played around with a lot of different display settings. But with mac it seems I can only get 1 or 2 as the "base" devicePixelRatio on screens, while in windows it can be something like 1.25 etc

Could you please share what is the value of Window.devicePixelRatio

How can I get the Window.devicePixelRatio?

Open the Developer Tools, then choose the Console and type window.devicePixelRatio. Thanks!

I can easily reproduce this on a mac with chart.js 4.1.0, but with 4.2.0 I can't. Played around with a lot of different display settings. But with mac it seems I can only get 1 or 2 as the "base" devicePixelRatio on screens, while in windows it can be something like 1.25 etc

On my MacBookPro, using an external display and Zoom %110 window.devicePixelRatio is 1.100000023841858
I'm asking because previously, the root cause was mishandling these non-integer values. I'm not sure if this is the case now.

Open the Developer Tools, then choose the Console and type window.devicePixelRatio. Thanks!

Mine is:

Another detail, my dpi zoom is 200% at 4k resolution.

Open the Developer Tools, then choose the Console and type window.devicePixelRatio. Thanks!

Mine is:

Another detail, my dpi zoom is 200% at 4k resolution.

Thank you; I ran some tests but unfortunately, I couldn't reproduce the issue.
How do you set the zoom level to 116%? I only see 110% and 125%...

It seems 116% will only be offered when the resulution is 4k/200%dpi. But I found an edge extension
https://microsoftedge.microsoft.com/addons/detail/vergr%C3%B6%C3%9Fern-f%C3%BCr-microsoft-/akclpjahoedloodjomjhnlmmblikemjj
with this I can reproduce the behavior at any resolution with 116% zoom.

Thank you. I'm now also able to reproduce the issue. The simplest way would be to set a style="zoom %116" on the <body> or <HTML> elements (depends on the setup, some other values may be needed to reproduce the issue).
It is probably a rounding issue.

I am able to reproduce it on Chrome too using "non-standard" zoom levels (i.e 117%)
Here is what I'm seeing:
getMaximumSize @ helpers.dom.ts is calculating the maximum size available for the chart. It starts with the available width and calculates the height based on the chart aspectRatio.
Then, the code below will check if the container's height is large enough. If it isn't, it will set the height to the container height (the width is also updated).
https://github.com/chartjs/Chart.js/blob/23e8f7d378a84dddd17d958a888ffff7f120c38c/src/helpers/helpers.dom.ts#L202
After the chart size is updated the browser will fire the ResizeObserver again. However, the container height is slightly less than the chart height (when zoom is active).
For example, when setting the chart height to be 454, the following invocation of ResizeObserver will return a new height of  453.984375.
As a result, the resize code will run again resulting in a new height of 453...  ResizeObserver fires with 452.984375...
🤦♂
At the moment I can't think of an elegant fix.
@kurkle @dangreen LMK if you can think of anything.

@gbaron Nice analysis, but what is the difference to v3.9.1 were it works?

At the moment I can't think of an elegant fix.

@gbaron Maybe just round values from resize observer ?

@gbaron I don't really know if something is happen with this issue, but Chart.js v4.2.1 don't fix it.

@fly74 that is true. v4.2.1 doesn't include any fixes.
I just submitted a PR (#11132).

@gbaron Can you provide an umd dist file for some tests?

@fly74 unfortunately Github doesn't support these files.
If you want to generate the file yourself:

Clone https://github.com/gbaron/Chart.js.
Run pnpm install
Run pnpm build

The results will be in the /dist directory.

@gbaron First test looks really good!
For those who want to give it a try:
dist.zip

It sounds like you've fixed it. In most of these edge cases with pixels, a good approach is to round down to the nearest e.g. 10 pixels, otherwise it can be easy for 1 pixel either way to cause a problem. You can do that with a simple mod 10.

Can this fix go into the official build?

Nothing seen in the release notes. Maybe anyone can do a test.

Nothing seen in the release notes. Maybe anyone can do a test.

indeed, I was waiting for the new release to update a solution, right now I can't test it on my laptop (not a high dpi screen), this happened with me on a client laptop (an XPS with high dpi) so I had to use @gbaron patch, so I guess i will wait for an official release notes ?!

You can test it with a browser plugin for zoom like described here some posts above or a browser you can set zoom to 116%. It is not depending on a hidpi screen.

This happens to me with 4.3.0.
Settings that produce effect:
display is 3240 x 2160
Scale and Layout in Windows 10 set to 150%
zoom in chrome set to 90% or 110%
It doesn't happen if I change the scaling in chrome or in the windows settings to something other than above...

That's what I said. The fix ist not in the official release.

Would love to see this included in the official release. Signing up for notifications.

What are the blockers to releasing this fix? ( #11132 )
Also, what is the workaround until it is released?

The only workaround for me was to compile the sorce from @gbaron above or use the resulting binary in my zip above. @shuuuuun

Thank you for your reply.
I'm looking for a way to make it as maintainable as possible.
I hope it will be released officially soon...

Is it fixed in 4.3.1?

I am still experiencing this with 4.3

@gbaron @lukos Is this fixed in 4.4.0? The solution is from @gbaron in this thread.

options={{ responsive: true, maintainAspectRatio: false }}  <-- these options solved my issue

@avisek-official But doesn't that mean the chart will no longer keep its aspect ratio if proportions go askew?

@lincolnthree I can't say this a fix for the issue, but it worked for me. Try it once in your project too and test anything breaks in any resolution. In my case it didn't break anytime with any data.

Still experiencing this in 4.3.3, any fixes expected anytime soon?

I really hope so 🙏

Sorry can't wait any longer. Move on to Grafana. :/

The fix is still being reviewed ?
https://github.com/chartjs/Chart.js/pull/11132

Version 4.4.1 and the problem is still there.
Disabling maintainAspectRatio it actually works. However, loading the page at 25% and zooming to 100% produces a way-too-blurry Chart. Not an option to me.

To me a workaround was to force the pixel ratio for charts to 1, by setting the devicePixelRatio: 1 option ( https://www.chartjs.org/docs/latest/configuration/device-pixel-ratio.html ).

We were having a similar issue where opening or closing Chrome's dev console was causing the graph to visually break.
We were able to resolve it by removing this line from options:
devicePixelRatio: 4,

Related threads for convenience:

https://github.com/chartjs/Chart.js/issues/10890
https://github.com/chartjs/Chart.js/issues/11089
https://github.com/chartjs/Chart.js/issues/11224
https://github.com/chartjs/Chart.js/issues/11304
https://github.com/chartjs/Chart.js/issues/11547

Calling mychart.resize() also reproduces the bad scaling issue.


does not auto resetting when we manual control

Does not auto resetting when we manual control by Break().

This change is

Hi @ajwerner,
Could you have time to review this patch?

@ajwerner there is a concurrent issue between setting tripped and reading lastFailure. It make state() to read an invalid lastFailure when there occurs a latency between setting tripped and lastFailure in Trip().
Is it really cause a bug? Yes to original version of circuitbreaker, but no for current version. Because of 79eae79 make the exported Trip() meaningless.
We can think that there are many goroutines invoking Call concurrently, and they will invoke Success() if the Call's  callback return nil. If we want make the breaker open a moment and let it auto recovery, we can invoke the Trip() manually.  And the concurrent issue make the circuitbreaker recovery immediately by reading invalid lastFailure and becoming into halfopen at wrong time.
After 79eae79 we redefinition the mechanism of circuitbreaker and exported Trip() is meaningless, hence the bug scenario is disappeared.
I can delete the comment if you feel confused.

I think I'm willing to merge this, mostly because we don't use Break anywhere outside of testing but this change really could benefit from a unit test so I'll make one more appeal.


Document how to automate detection of changes in GitHub Actions

If you're managing lots of repositories, it can be a lot of effort to check for changes in them. This is an example of getting GitHub Actions to periodically run checks on the repository and creates accept and reject PRs that are ready for review.

This does not work if the template modified the any of the github actions workflows. Github does not allow modifying themselves.

@Zethson can you give an example config/repo of something not working so I can investigate?

See here: https://github.com/scverse/cookiecutter-scverse/issues/138


Fix user settings

Tasks

[X] Remove routes depending on FOSRestBundle

[X] Remove routing configuration
[X] Remove controllers

[X] Remove view listener

[X] Remove view response
[X] Remove view handler
[X] Adapt registration view to form theming changes
[X] Reactivate support of native view annotations

[ ] Reintroduce functional test of user settings controller by extending WebTestCase
[x] Remove FOSRestBundle from composer.lock, composer.json

Bonus

[X] Add command to update permissions (=> ACL might not be applied as expected)
[X] Add command to import perspectives
[X] Add cache / logs directories to VCS ignore list
[X] Remove controllers which are now out of current project scope
[X] Reintroduce functional testing via perspective controller test

i will be back :P


If the cell runs for more than 60 seconds, an additional reminder will be given

In the process of using jupyter notebook, we can see the specific running time of the cell.
I have an idea, if the running time of the cell is too long, such as more than 60 seconds, whether a reminder can pop up on the right side of the running time.

Is there a way to customize this function?
Thanks for any help.

Thanks for filing this feature request, given the fact that there haven't been any upvotes on this issue since it was open, I'm closing this.


Add Subnetwork Variable

@peterdeme Seems the other PR didn't have the subnet stuff D:
Apologies!

@peterdeme Can you cut a release on this bad boi?


extra right margin in donate-card  on mobile

Bug Description
extra right margin in donate-cards on mobile devices
Steps to Reproduce
Steps to reproduce the behavior:

Go to 'https://www.thenewboston.com/donate'
See error
Expected behavior
on donate-cards margin should be equal in left-right on mobile
Actual behavior
on donate-cards right-margin is greater than left-right on mobile
Screenshots/Recordings

OS and Browser

OS: [e.g. Windows 10]
Browser [e.g. Chrome, Safari]
Account Number
dfddf07ec15cbf363ecb52eedd7133b70b3ec896b488460bcecaba63e8e36be5

i'll like to handle this

@vectaaa I have solved this issue.


docs: use dart pub instead of pub in melos.yaml

Description
The pub command was removed. Instead, we should use dart pub.
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (melos run analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I signed the CLA.
[x]  I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[x] No, this is not a breaking change.

CI pipeline fails because of https://github.com/firebase/flutterfire/issues/8644 and #8656


When I use superset to query the connected odps database, the error ODPSEngineSpec.execute() takes 3 positional arguments but 4 were given

Bug description

when i query the connected odps database, the error is as follows

The detailed error log is as follows

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/flask/app.py", line 1484, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/local/lib/python3.10/site-packages/flask/app.py", line 1469, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
  File "/usr/local/lib/python3.10/site-packages/flask_appbuilder/security/decorators.py", line 95, in wraps
    return f(self, *args, **kwargs)
  File "/app/superset/views/base_api.py", line 119, in wraps
    duration, response = time_function(f, self, *args, **kwargs)
  File "/app/superset/utils/core.py", line 1364, in time_function
    response = func(*args, **kwargs)
  File "/app/superset/views/base_api.py", line 91, in wraps
    return f(self, *args, **kwargs)
  File "/app/superset/utils/log.py", line 303, in wrapper
    value = f(*args, **kwargs)
  File "/app/superset/sqllab/api.py", line 409, in execute_sql_query
    command_result: CommandResult = command.run()
  File "/app/superset/utils/decorators.py", line 266, in wrapped
    return on_error(ex)
  File "/app/superset/utils/decorators.py", line 236, in on_error
    raise ex
  File "/app/superset/utils/decorators.py", line 259, in wrapped
    result = func(*args, **kwargs)
  File "/app/superset/commands/sql_lab/execute.py", line 105, in run
    status = self._run_sql_json_exec_from_scratch()
  File "/app/superset/commands/sql_lab/execute.py", line 158, in _run_sql_json_exec_from_scratch
    return self._sql_json_executor.execute(
  File "/app/superset/sqllab/sql_json_executer.py", line 111, in execute
    raise SupersetErrorsException(
superset.exceptions.SupersetErrorsException: [SupersetError(message='odps error: ODPSEngineSpec.execute() takes 3 positional arguments but 4 were given', error_type=, level=, extra={'engine_name': 'ODPS', 'issue_codes': [{'code': 1002, 'message': 'Issue 1002 - The database returned an unexpected error.'}]})]

The relevant database and driver versions are as follows:

Screenshots/recordings
No response
Superset version
4.1.1
Python version
3.10
Node version
I don't know
Browser
Chrome
Additional context
No response
Checklist

[X] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

@dosu please assign this issue to me

@dosu please assign this issue to me

Is there any solution?


Add ceph_infra tag to rolling_update

When the upgrade from Ceph 4 to 5 is performed in the OpenStack context,
ceph-ansible triggers the rolling_update playbook, which is supposed to
rollout new Ceph containers.  The ceph-infra role tries to take care
about firewall, ntp config and logrotate; however, TripleO manages them
through tripleo-heat-templates.  This patch just add an additional tag
to skip the ceph-infra role in the OpenStack context.
Closes: https://bugzilla.redhat.com/2090456
Signed-off-by: Francesco Pantano<EMAIL_ADDRESS>

@guits does it make sense for you?


⚠ GitLab Server has degraded performance

In 753f29b, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 11231 ms

Resolved: GitLab Server performance has improved in 1dc49bb.


Added See Also links

At the bottom of the document (above the footer), I added links to other guides that readers may find to be useful.

Thank you, @diodfr 👍


Disable part of a test that fails with Swift Testing in the toolchain.

Remove some assertions from testSwiftTestXMLOutputWhenEmpty() that aren't strictly necessary and which have started to fail as we add Swift Testing to the toolchain.

@swift-ci test


Set-SPOSite on Group Sites gives parameter error

Running either of these commands:
Set-SPOSite -Identity https://XXXXXX.sharepoint.com/sites/XXXXXX -CommentsOnSitePagesDisabled $true
Set-SPOSite -Identity https://XXXXXX.sharepoint.com/sites/XXXXXX -SocialBarOnSitePagesDisabled $true

on a O365 Group connect site, returns the following error:
Set-SPOSite : https://XXXXXX.sharepoint.com/sites/XXXXXX is a Groups site collection. The valid parameters for this type of site collection are '-Identity', '-AllowSelfServiceUpgrade', '-DefaultLinkPermission', '-DefaultSharingLinkType', '-DenyAddAndCustomizePages', '-DisableCompanyWideSharingLinks', '-DisableSharingForNonOwners', '-LockState', '-Owner', '-ResourceQuota', '-ResourceQuotaWarningLevel', '-SandboxedCodeActivationCapability', '-SharingCapability', '-ShowPeoplePickerSuggestionsForGuestUsers', '-StorageQuota', '-StorageQuotaReset', and '-StorageQuotaWarningLevel'.
At line:1 char:1
+ Set-SPOSite -Identity https://XXXXXX.sharepoint.com/sites/X ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Set-SPOSite], ServerException
    + FullyQualifiedErrorId : Microsoft.SharePoint.Client.ServerException,Microsoft.Online.SharePoint.PowerShell.SetSite

The command runs fine against a Communication site.
This may be realted to "Usage limits for Set-SPOSite cmdlet on Groups site are missing documentation #1555"

@MikeBass13 Thank you for your Feedback. There are some limitations for the group's site collection and I will be updating the document shortly.

Created PR https://github.com/MicrosoftDocs/office-docs-powershell/pull/2934 adding the restrictions to Groups site collection.

@kenwith please review and merge this PR, if you find it suitable.

@VesaJuvonen Please merge this PR if you find it suitable, @kenwith sorry, wrongly tagged.


How to set width for line chart?

I want to set width for my line chart view.

My line chart look like as in above picture. As you can see in the picture with large data's the chart is very hard to see. So I want to know how to extend the width of lone chart view. Thanks.

line.setStrokeWidth(2);


[editor]: Support db in preview

Please add support for .db files to the editor preview.
Generated by adamraichu.zip-viewer

Sorry, but db files are stored in binary format.

update

update

Sorry, what?


Password resets show if account exists

When going to reset a password, if you enter an email address that doesn't exist, it will tell you straight up that there is no record of the account. In my opinion, this is a security concern since a malicious user can continue to enter email addresses until they find one that actually resets. If they're determined enough, they can then go after that email address to try and hack into it and obtain access. I know it sounds ridiculous, especially for a small project like this, but I think the panel should simply say something like If this user account exists, password reset instructions will be emailed to this address. instead. This way, the user has no idea whether the account exists or not.

Hmmm. Some websites do it the way we do, others do it like you prefer it. I'd say it is more secure your way though.

No worries. :) I always like to think big picture. Bogs me down a lot of the time, but some day I'll feel super happy with the end result!

Should add a captcha to that page while we're at it.


Added isDenied method to SPPermission.

Renamed isAllow method to isAllowed.
Fixed internal code names.

Thanks for your work!


java.lang.IllegalArgumentException: Receiver not registered

We're seeing quite a few production crashes with this plugin. Here are the stacks:
com.marianhello.react.BackgroundGeolocationModule.unregisterLocationModeChangeReceiver
BackgroundGeolocationModule.java - line 276
java.lang.IllegalArgumentException: Receiver not registered: com.marianhello.react.BackgroundGeolocationModule$2@58d1045

android.app.LoadedApk.forgetReceiverDispatcher LoadedApk.java:766
android.app.ContextImpl.unregisterReceiver ContextImpl.java:1686
android.content.ContextWrapper.unregisterReceiver ContextWrapper.java:511
android.content.ContextWrapper.unregisterReceiver ContextWrapper.java:511
com.marianhello.react.BackgroundGeolocationModule.unregisterLocationModeChangeReceiver BackgroundGeolocationModule.java:276
com.marianhello.react.BackgroundGeolocationModule.onHostDestroy BackgroundGeolocationModule.java:119
com.facebook.react.bridge.ReactContext.onHostDestroy ReactContext.java:228
com.facebook.react.ReactInstanceManager.moveToBeforeCreateLifecycleState ReactInstanceManager.java:705
com.facebook.react.ReactInstanceManager.onHostDestroy ReactInstanceManager.java:614
com.facebook.react.ReactInstanceManager.onHostDestroy ReactInstanceManager.java:628
com.facebook.react.ReactActivityDelegate.onDestroy ReactActivityDelegate.java:142
com.facebook.react.ReactActivity.onDestroy ReactActivity.java:72
android.app.Activity.performDestroy Activity.java:6200

Our config is:
{
  desiredAccuracy: HIGH_ACCURACY,
  stationaryRadius: 30,
  distanceFilter: 10,
  notificationTitle: I18n.t('background_tracking'),
  notificationText: I18n.t('enabled'),
  debug: false,
  startOnBoot: false,
  stopOnTerminate: true,
  locationProvider: DISTANCE_FILTER_PROVIDER,
  activityType: 'Fitness',
  interval: 2500,
  fastestInterval: 2500,
  activitiesInterval: 5000,
  stopOnStillActivity: false,
};

Your Environment

Plugin version: 0.4
Platform: Android
OS version: 23 - 26
Device manufacturer and model: Wide range
React Native version: 0.51
Plugin configuration options:

Possible Fix
This is quite possibly related to #46, and as stated there – this seems to be caused by a race condition.
We also code pushed a hotfix by setting stopOnTerminate to false, and that fixed the crashing.

Happens to me on 0.5.alpha-19

@reetou can you post crash log. because 0.5.alpha-19 has done quite big refactoring so lines from origin crash doesn't match anymore. I'll take look then on it.

There are already guards to not try unregistered receiver when it was not registered, but apparently there is something strange. So please post configuration options and steps how to reproduce the crash and also crash log from adb logcat.

@mauron85 Happy to test alpha-19, but master install seems broken as the subproject is not included when installed with yarn/npm.

@kristfal Not it should not be. Read my comment https://github.com/mauron85/react-native-background-geolocation/pull/168#issuecomment-380144164


"Out of Memory" Error when Viewing JSONs

The last couple weeks, when trying to edit a json with ArcGIS Online Assistant, after clicking on the item I want to view the json of, AGOL tries to load it, but invariably always ends up giving the Out of Memory error code.

I've been having the same issue attempting to view the json of a massive web map. I'm trying to avoid having to rebuild the webmap just to repoint the itemids. Have you found a work around?

Yes, using it in the Firefox browser worked for me. Also, it looks like there is a new version of AGOL assistant too.


1 hour after we cant do anyting: Temp fix

Interesting option, but a bit of a hack...
When we get the key from login, I'm sure it has an expiry time. Wouldn't it be better to check that on each loop instead?


input: it8xxx2: use the generic keyboard code

Build test only, I don't have any hardware available to test this. @Dino-Li @GTLin08 @RuibinChang could you test this for me?

Split the common keyboard scanning code out of the ITE specific driver and use the generic code instead.
Note that this changes few timing defaults, the change is not significant though so I suspect there's no difference in practice.

Build test only, I don't have any hardware available to test this. @Dino-Li @GTLin08 @RuibinChang could you test this for me?

@fabiobaltieri Okay. We will respond with test results.


Typing problem with the response data

When using TypeScript and trying to add typing to the response data it shows 'data' is of type 'unknown'

It only happens when you call .json() at the end


Copy pasting the table from another site page is not working properly

I checked the copy-pasting from google docs and it works perfectly fine. But If the user copy-paste the content from the website Page which is implemented may give some unwanted behavior.   Here is one I implemented in code sandbox and here you can see that if you copy-paste this table block you will not get the sidebar of table block.
https://codesandbox.io/s/sweet-heisenberg-ord5n?file=/src/App.js
I investigated that there is a difference between how we structure the code of table block and other website pages. Here is the difference
Here is how Another website can implement

              March 2021

{" "}

Here is how we implemented the same text

                March 2021

{" "}

In edit mode for the first one, we will not get the
 tag element. I think that something is related to that.
I found this issue when I am trying to find an issue reported by a user. @tiberiuichim maybe you have some insight into why this occurs.
This is the generated code when the user pasted the table

I don't know why there is no p generated tag. This is the error occurred when the user clicks on the generated table column.

@tiberiuichim Finally found the original table of website. Here is the link. https://www.fz-juelich.de/ibg/ibg-1/EN/Research/SystemicMicrobiology/syncell/syncell_node.html.
Visit this link and try to copy paste the table in volto-slate.

It will able to replicate the table
save it
once again go to edit
try to edit the January to December
You will not able to edit it.

@iFlameing I will try to replicate it in couple of days, Right now caught up with something. Is it urgent?

@nileshgulia1 not so.

@nileshgulia1 any update?

@tiberiuichim can you please take a look regarding this issue.

@tiberiuichim can you please take a look regarding this issue.

@tiberiuichim any update

@tiberiuichim this is the configuration
 "volto-slate:minimalDefault,simpleLink,tableButton",

@tiberiuichim any finding or pr, we really need this now.


feat: hour chime

closes https://github.com/OpenVoiceOS/skill-ovos-date-time/issues/47

Summary by CodeRabbit

New Features

Introduced a "Configuration" section in the README for adjusting skill behavior via settings.json.
Added options for hourly chime notifications and customizable chime sound.

Bug Fixes

Improved error handling for timezone retrieval methods, allowing for optional returns.

Documentation

Updated README to include new configuration options and example usage, along with updated credits for audio files.

Chores

Enhanced resource file handling to include MP3 files in the package data.

Looks like a great new feature. Does anyone has that Casio watch bleep sound?  Do you want me to test this?

Does anyone has that Casio watch bleep sound?

in the PR i am using this https://freesound.org/people/Pablobd/sounds/492481/

Build test failing. Code looks good but I'll need to test it in one of my assistants

no clue what "test manifest" is actually testing and how to solve it, first time i'm running into this workflow. anyone care to explain this automation?

Build test failing. Code looks good but I'll need to test it in one of my assistants

no clue what "test manifest" is actually testing and how to solve it, first time i'm running into this workflow. anyone care to explain this automation?
nvm, got it. but we should standardize this across our repos, i don't recall seeing this one before!

https://github.com/tj-actions/check-manifest
It's disabled by default, but available in Neon test automations: https://github.com/NeonGeckoCom/.github/blob/09f0850847bf45f02a8cd7774097bb570e6a8fd7/.github/workflows/python_build_tests.yml#L12

Build test failing. Code looks good but I'll need to test it in one of my assistants

no clue what "test manifest" is actually testing and how to solve it, first time i'm running into this workflow. anyone care to explain this automation?
nvm, got it. but we should standardize this across our repos, i don't recall seeing this one before!

tj-actions/check-manifest
It's disabled by default, but available in Neon test automations<EMAIL_ADDRESS>
yeah it's a nice one to have! I just missed it until now somehow. I approve adopting that one across more repos :+1:


config: don't precompile everything blindly

Precompiling everything can lead into problems. Instead, since
everything is bundled inside of the application.{css,js} files, then it
should be fine.
Signed-off-by: Miquel Sabaté Solà<EMAIL_ADDRESS>

Don't merge this just yet, it's still work in progress.

lgtm

@madboxkr sorry, forgot to submit a PR with this fix yesterday too :sweat_smile:. PR #1092 provides a fix for this.


Convert to Pascal fails for multine text

I'm trying to run the "Change case 'pascal'" command in this input (all selected at once):
ID_PROP_USER
NUMEF
NUMPROP
NUMBUS
STATUS
USER
TYPEPROCESS
DS_LOG
DT_BIRTH

But I get a warning: Running the contributed command:'extension.changeCase.pascal' failed.
Some other commands work, like dot, constant, and some also fail, like camel.
EDIT: I think I see what I did wrong, if I select all the words with the alt key, it works. Should this work if I select the text as a whole (like ctrl+a) too?

The original idea was for the extension to work on individual words, as selected by the user, like you've described in your edit.
I guess I could implement something so that it works with a multi-line selection, but I'd be concerned it would have do things that the user doesn't expect.
What should happen if the text as a whole is a block of code, which contains dashes and underscores?
And then there's also the issue of handling 'sentence case' in this scenario ...
In any case, the user should get a nice message rather than that warning. I could do that quite quickly, and if you've got further suggestion on how it should work with with a selection that spans lines, I'd be happy to hear it.

I think you are right about the complexities on multi-line selection, I don't see any way to handle these scenarios without frustrating the user.
If I read the README before trying the extension I probably wouldn't try it anyway, so maybe just a nice message will prevent people from thinking this is an issue.
Thanks for the help and for your work on the extension.

Thanks for the feedback. I've implemented an info message, updated the readme in commit 669892ebdd16ccd5a5eadc18ff08a12b63a92e5f, and published version 0.3.0.

Why would you intentionally limit the usability of your extension? If the case conversion fails in some way that's unexpected to the user they can just ctrl+z out of it. I'm migrating from Sublime Text which comes with basic case conversion functionality out-of-the-box.

Why not provided a limited set of features for a block/multiple lines of text?
For instance, if the user selected multiple lines just give them the option for all upper case/all lower case. That shouldn't need a lot of change from the coding logic, and would provide a feature people are looking for.

Ok, I'm looking into it, expect a new release soon.

Thanks all for the feedback. I hope the latest changes satisfy your wishes. If not, you're welcome to open a new issue.


Example doesn't working

Demo example at https://alpsquid.github.io/quizlib/ isn't working.

Oh yeah, would help if I updated it to match the example in the main branch. Should be sorted now, cheers!


bug list

Few things that breaks
Description

added script that was directly ported from portal example to make somewhat physical fps controller
-it was broken obviously but when the error happened there was no way to determine which line was broken, and even after deleting the script the run button was stuck at stop, and shown the last error message. had to recreate the scene. This would be a minor issue but having to recreate everthing from scratch prevents me from thinking about nunustudio for making something bigger than a simple demo.
when adding postfx to camera the antialiasing from the base camera gets overridden and disabled, so even with bloomfx lines look severely jagged
dropping js file on the object does nothing, i have to create new script object and then copy and paste the js file content to it so its pretty useless to import js in most of the times.
it kida sad casuse it will warp me back to the unity or aframe.

Version

0.97.8

Platform

Windows [X]

Hi Thanks a lot for reporting these.
I have been working on more detailed info on the console, and i been workin on solution to link console errors to the script editor for provide detailed code location of the error.
The PostFX in webgl pretty much forces the antialiasing disabled on WebGL 1.0 we cannot render to a buffer with antialiasing on. In postfx you have to use one of the postfx aa solutions.
To be honest with you, if you're doing some significative commercial work, i would prefer to go with one of the libs directly (threejs, babylon, etc) or possibly with one of major engines, unity seems to be the one with best web support. Godot also works pretty well but its more limited in the web.
Currently im working on nunuStudio less than 2H a week, development its going really slow and i cannot provide solutions fast enough for most stuff.
Thanks a lot for the support and for undestanding.

Yeah, didnt mean to sound harsh, and I think Your editor is still one of the better suited for the commercial work, and I think it should be merged somehow to the main three.js editor cause it allows the designers to create better looking scenes.


Vue.js read excel

i tried to read the excel files with vue.js but u can once i read the file the memory start to sky rocket like 5 gb ram and i the excel file is feairly small pls help need to convert the file to json
The vue method to handle the excel file i tried all the type option i saw in the documintation but all send me diffrent errors.
base64: "TypeError: input.replace is not a function"
binary: "TypeError: x.charCodeAt is not a function"
string: "TypeError: data.match is not a function"
array: is the one that cause the memory to get into 5gb
displayFile: function (event) {
      // console.log(event.target.files[0])
      // const file = event.target.files[0]
      // const workbook = XLSX.read(file, {
      //   type: 'string'
      // })
      // console.log(workbook, workbook.SheetNames)

      // const res = XLSX.read(file)
      // console.log(res)
      // const res = XLSX.read(this.file)
      // console.log(res)
      console.log(this.file)
      this.file.text().then(text => {
        const fileType = this.file.type
        console.log(fileType)
        // this.PropceseMethod(this.file, fileType)
      })
      const reader = new FileReader()
      reader.onload = (data) => {
        console.log('HERE')
        console.log(data)
        const workbook = XLSX.read(data, {
          type: 'buffer'
        })
        console.log(workbook)
        workbook.SheetNames.forEach(function (sheetName) {
          console.log(sheetName)
          console.log(workbook.Sheets[sheetName])
          // Here is your object
          const XLRowObject = XLSX.utils.sheet_to_row_object_array(workbook.Sheets[sheetName])
          console.log(XLSX.utils.sheet_to_json(workbook.Sheets[sheetName]))
          console.log(XLRowObject)
          const jsonObject = JSON.stringify(XLRowObject)
          console.log(jsonObject)
        })
      }
      reader.onerror = function (ex) {
        console.log(ex)
      }
      reader.readAsText(this.file)
    }

the actual temeplate i tried two things
<v-file-input
    v-on:change="displayFile($event)"
    v-model="file">
    </v-file-input>
    <input type="file" name="xlfile" id="xlf" v-on:change="displayFile($event)" />

both way did the same thing
when i use buffer it is working but return XLSX.utils.sheet_to_json(workbook.Sheets[sheetName]) return [] like all the method and the rset of the functions

@1shaked Hey, I'm using vuejs as well. I'm facing the same issue here. Did you get it work?

yes i will send you the code.
first is the file function which will get the files from the event and take only the first sheet;
_change (evt) {       const files = evt.target.files       if (files && files[0]) this._file(files[0])     }
the input file
<input type='file' class='form-control' id='file' :accept='SheetJSFT' @change='_change' />
the _file process function,
`
_file (file) {
/* Boilerplate to set up FileReader /
const reader = new FileReader()
reader.onload = (e) => {
/ Parse data /
const bstr = e.target.result
const wb = XLSX.read(bstr, { type: 'binary' })
/ Get first worksheet /
const wsname = wb.SheetNames[0]
const ws = wb.Sheets[wsname]
/ Convert array of arrays /
const data = XLSX.utils.sheet_to_json(ws, { header: 1 })
/ Update state */
this.data = data
const header = data.shift()
    const tbl = []
    for (let rowNum = 0; rowNum < data.length; rowNum++) {
      const row = data[rowNum]
      const objToAdd = {}
      for (let colNumber = 0; colNumber < header.length; colNumber++) {
        objToAdd[header[colNumber]] = row[colNumber]
      }
      tbl.push(objToAdd)
    }
    console.log(tbl)
  }
  reader.readAsBinaryString(file)
}

`
the loop is just for me to wxtract the data but the main thing that cause of the problom is the reader.readAsBinaryString(file) and the make sure const bstr = e.target.result
const wb = XLSX.read(bstr, { type: 'binary' }) . and there is some demos in this repo on how to do this.
i will look in the repo and send you the exmple.


Update air gap installation docs for Rancher 2.5 installs with rancherd

Catherine to follow up with @davidnuzik to find out how Rancherd can be installed in an air gap environment
Denise also said we should include this change:

As part of air gap docs, we also need a note that specifies if you are connecting to an external service through alertmanager or logging, the external service needs to be reachable from the cluster running the tool

Note, tracking for rancherd implementation is here: https://github.com/rancher/rancher/issues/28131 presently there is no rancherd binary/release to work with. Presently standing by for rancherd to be completed.

Removing the staging label because rancherd is not being documented for Rancher v2.5

Closing in favor of #2826


Maybe add information about the never released Apigility one ?

I seem to remember seeing a photo of a prototype on Twitter a few years back (or maybe it was just a drawing).
It was intended for one of the ZendCon conferences. Was a blue elephant with a rocket on its back if I remember correctly.
AFAIK it ended up never getting produced because it was deemed inappropriate as tensions around Israel were flaring up again around the time.

Oh, just thinking, @weierophinney might be able to point you a picture

Actually, @adamculp had the prototype, IIRC.

Yes, still sitting on the shelf with the rest of the PHPamily. http://geekyboy.com/images/apigility_proto.jpg

Haha how cool :) thanks @weierophinney @adamculp - didn't know this cutie exist :+1:

The backstory: We were originally going to produce the Apigility elePHPant for ZendCon 2014. However, leading up to ZendCon there were many rocket attacks over Israel. Someone felt the elePHPant looked like it was launching a rocket, and it was decided that the possibility was too sensitive at the time. So we created the elePHPant with the Z-Ray goggles instead.

Pull request added, for this and other images.

:+1:

Resolved with #30


Integrating with Other components

Hi,
I am using power-select and power-select-multiple with validated-form like :
model ->

{
obj: {
id: null,
name: null
}
}

{{#f.input name='obj'as |fi|}}
{{#power-select-multiple
options=options
searchField='name'
onchange=fi.update
placeholder='Select'
selected obj as |o|}}
{{o.name}}
{{/power-select-multiple}}
{{/f.input}}

With this, I am able to see the dropdown, but selecting a value doesn't render the selected value to the dropdown. Also, I am not able to search using name.
Kindly give some guidance.
Thanks in advance!

Sorry a slight correction. The selected value doesn't render in the field. I am only able to view the placeholder even after selection.

Hi @g8anusha,
thanks for your bug report! I played around with your example a little bit and realized that the only thing you were missing is the proper definition of the selected attribute:
selected=fi.value

I created a twiddle with a basic example.
Just to give some context: Passing fi.update´ to onchangewill update theobjproperty of our model with the currently selected value. In order for that value to be displayed, you'll have to pass it back into the select'sselectedattribute, which can be done viafi.valueor the longer versionf.model.obj`.
Currently, we're clearly lacking documentation for this - I'll leave this issue open until we have proper docs.
Bonus: The twiddle also shows how to integrate fi.setDirty for proper dirty state handling!
I hope that helps! :smile:

Hi, Thanks a lot for the prompt response.
But, it gives the error "newSelection.push(option) is not a function, where I get newSelection as obj"

Hey, am really sorry I changed it to f.model.obj and it worked!!
Many thanks! :)

I'll close this since we have better documentation now :smile:

@czosel sorry for necromancy, but I'm trying to do exacly what this issue describes:
{{#validated-form
   model = (changeset model ItemValidations)
   on-submit = (perform submit)
   as |form|
}}
  <!-- ... other inputs ... -->

  {{#form.input
     label    = "Category"
     name     = "category"
     required = true
     as |input|
  }}
    <!-- categories is an additional model fetched in route via this.get('store').findAll('category'), it uses ember data -->
    {{#power-select
       options     = categories
       searchField = "name"
       placeholder = "Choos category..."
       onchange    = input.update
       selected    = input.value
       onblur      = input.setDirty
       as |category|
    }}
        {{category.name}}
    {{/power-select}}
  {{/form.input}}
  <!-- ... -->
{{/validated-form}}

@czosel OK, it seems I accidentally discovered the cause of the problem :joy:
In my ROUTE I was using this.get('store').createRecord('item') to create an empty model for the form.
This approach has several drawbacks:

if you enter the /items/create route, the empty item is immidietly added to the underlaying model, and may change some other components (eg. if I had "total items counter" somewhere, it would be immidietly incremented)
if you exit the /items/create route, the empty item stays in the storage (even though it was never saved), you have to explicitly unload the item in deactivate hook
when I called save() on item, I was getting Assertion Failed: item was saved to the server, but the response returned the new id '71', which has already been used with another record.'" which resulted in two identical items in the store, except one did not have id (and also required additional handling)

Now for these reasons, I've changed my approach, and I use EmberObject.create({}) as my form model, and will do store.createRecord only when submiting valid form.
To my surprise, suddently power-select works as expected :) So it seems the issue was with the way Ember data proxies its objects.

Hi @ioleo, I'm glad you were able to resolve the issue! I don't think I've run into it before myself, probably because I'm always calling createRecord when the form is submitted for the same reasons you outlined above.


LinkML test error

Running make all on the linkml_yaml branch fails with the following error:

Traceback (most recent call last):
  File "/home/runner/.cache/pypoetry/virtualenvs/oscem-schemas-HjusQlgA-py3.10/bin/linkml-run-examples", line 8, in <module>
    sys.exit(cli())
  File "/home/runner/.cache/pypoetry/virtualenvs/oscem-schemas-HjusQlgA-py3.10/lib/python3.10/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
  File "/home/runner/.cache/pypoetry/virtualenvs/oscem-schemas-HjusQlgA-py3.10/lib/python3.10/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
  File "/home/runner/.cache/pypoetry/virtualenvs/oscem-schemas-HjusQlgA-py3.10/lib/python3.10/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/runner/.cache/pypoetry/virtualenvs/oscem-schemas-HjusQlgA-py3.10/lib/python3.10/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
  File "/home/runner/.cache/pypoetry/virtualenvs/oscem-schemas-HjusQlgA-py3.10/lib/python3.10/site-packages/linkml/workspaces/example_runner.py", line 313, in cli
    runner.process_examples()
  File "/home/runner/.cache/pypoetry/virtualenvs/oscem-schemas-HjusQlgA-py3.10/lib/python3.10/site-packages/linkml/workspaces/example_runner.py", line 138, in process_examples
    self.process_examples_from_list(input_examples, fmt, False)
  File "/home/runner/.cache/pypoetry/virtualenvs/oscem-schemas-HjusQlgA-py3.10/lib/python3.10/site-packages/linkml/workspaces/example_runner.py", line 193, in process_examples_from_list
    raise ValueError(f"Example {input_example} failed validation:\n{e}")
ValueError: Example src/data/examples/EMDataset-001.yaml failed validation:
unhashable type: 'Institution'

This is run by the CI, so PRs like #9 fail.
I think it might be python-specific. Running linkml-lint directly doesn't report errors. The cookie cutter uses the python bindings for testing, but we mostly care about the schema itself as well as the jsonschema derived files

Fixed now


BUG: Covenant out-of-date and broken

Describe the bug and expected behavior
When attempting to use The Covenant, my grunts have trouble executing commands.  It appears this has been fixed in a later build of The Covenant, as updating Covenant fixed this issue.  In order for the latest version to run, I needed to install the DotNet Core 2.2.106 (https://dotnet.microsoft.com/download/dotnet-core/2.2)
To Reproduce
Steps to reproduce the behavior:

Run Covenant and Elite
Execute a launcher to get a Grunt
Attempt to run any command.

Version

OS:  Win10

@IppSec Thank you for the info! I will add this to be completed with the May update (next week)

Update: Will have to push to June update.

Package has been updated and op-tested in the 1.3 release.
Thank you! Let us know if you have anymore issues/suggestions.


Composer installs error in symfony 4.2+

While installing composer it returns error in symfony 4.2 +,
Following is error, please have a look,
Executing script cache:clear [KO]
[KO]
Script cache:clear returned with error code 1
!!
!!  In GosWebSocketExtension.php line 210:
!!
!!    Notice: Undefined index: server
!!

Duplicate of #358


Does tf consider to support mac os + amd gpu?

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Mac OS, Mojave, 10.14.6
TensorFlow installed from (source or binary): source
TensorFlow version: 2.0.0-rc0
Python version: python 3.7

Describe the problem
I try to compile tensorflow from source code with opencl, while it requires computecpp support. However, the official website of computecpp shows that it does not mac os.
Thus, as described by tf official docs, the gpu version cannot run on mac os.
I just want to ask whether tf considers to add gpu support for mac os, now I can only develop models by keras with plaidml backend, or run tf on cpu.

I think @gunan is a better assignee here as this is a request for a new architecture.

I think @gunan is a better assignee here as this is a request for a new architecture.

@mihaimaruseac  thank you

Our GPU support runs through CUDA library, which is supported by NVIDIA themselves.
Until there is an AMD (ROCM)or community supported (for example OpenCL, SYCL) solution for macos, we cannot support this ourselves.

Use the library PlaidML; works fine for more models on a Mac OS with AMD GPU.


Concentrate information about a model

consider a two-part organization, consisting of a C++ object which stores information about the model, and a CUDA code block which handles the calculations

Related is the ability to include new models without compiling gpufit (runtime CUDA compilation) #9

I agree this is an interesting step to consider.
I tried to do a similar thing to what you did here using just PyCuda to make python able to talk with the GPU, avoiding C++ coding. I just made the repo public after submitting a paper using it.
Your LevMar implementation is way beyond mine, but if you are interested I can think of extending the python interface to your library using PyCuda or CuPy as python frontends, and wrap both projects in one. Let me know ...


Improve Encoder and Decoder classes

Add support for padding in Encoder
Add support for padding and output_padding in  Decoder
Improve the docs a bit

@etzinis, you should be able to use these class in to same way you used yours now. Tell me if it doesn't suits you.


Changed map/filter to addCallbacks

Here is an implementation of this issue.
These changes do not include the documentation or example code that will need to be updated. But I wanted to get feedback on the source code changes before dedicating time to updating documentation/examples. I did make some rough changes to example/index.js so that the test suite passes, but more work is needed there.

Nice work! I looked over this for a bit but would like to do some more investigation on my end. There are Javascript features here such as getOwnPropertySymbols and getOwnPropertySymbols that I'd to re-acquaint myself with.

Nice work! I looked over this for a bit but would like to do some more investigation on my end. There are Javascript features here such as getOwnPropertySymbols and getOwnPropertySymbols that I'd like to re-acquaint myself with. I really like where this is going though

That part of the code is heavily inspired by the Copying accessors example from the MDN docs.

Do we want to determine and announce/publicize/document a targed version for removal of the deprecated functions?

Two things regarding this.

There's no reason both map/filter and addCallbacks/removeCallbacks can't exist at the same time. I think the best plan is to put back the map/filter code and do a release with both. Then remove map/filter in the release after that (assuming that's enough time for users to update their code).
I added deprecation flags to the map/filter functions in the README. But I don't know where source code for the docs is. If someone can point me to them, I can update those as well.

source code for docs is the readme essentially... I think @UncleGedd and I will work on an update to the website, which is the only other source. Readme is probably best place for flags, given how NPM is used. IMHO.
Overall, I think we should bring release schedule and potential deprecation over to dev for discussion, and not make it a blocker on getting this PR closed.

Sounds like a plan.
If we like the thought of eventually deprecating/removing, then I'd suggest announcing a targeted release where that would occur [ that could always be pushed back, but without a target it is much less likely to EVER occur ]

I addressed @UncleGedd suggestions here, let me know if that is what you meant.
How about announcing the removal of map and filter with release 2.5? That should give users at least 6 months to update code.


[Diskpool] Fix #19470: az disk-pool: Update version to stable swagger, add commands az disk-pool list-zones, az disk-pool redeploy

Fix #19470, update version to stable swagger.
Add az disk-pool list-zones
Add az disk-pool redeploy
To test run:

az disk-pool list-zones -l {region}
az disk-pool redeploy --name {diskPoolName} --resource-group {rg}

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

Diskpool


Update ADOPTERS.md

I've updated technical blog for flight
(url has been changed)

Hey @JungMinu — thanks for the change. I'm not seeing any Flight-y stuff on your site, and it doesn't seem to be built with Flight. Am I missing something? Sorry if I am!

This looks like your CV — will accept another PR if it's for an app that uses Flight. Thanks!


Borgs can now speak while in Crit

About the PR

Enabled Borgs to speak while in their new Critical state
Why / Balance

The new critical state for borgs has been a point of frustration for many borg players, as you lost the ability to communicate to those around you that you used to have as an MMI. What was a change that was supposed to make it easier for Science to get a borg player back into the game with their body intact has largely ended up as a round end for the Cyborg, as they are forced to sit in their body and watch silently as noone helps them, or perhaps explain that they need to be welded to be repaired.
As it currently stands, Crit is not a true "in-between" state between life and death like Crit usually is, and in many instances it is preferable to die as you regain your ability to speak and interact with those around you. By returning the ability to speak to Crit borgs, there is a more clear transition between Life, Crit, and Death, where you have your full capabilities while healthy, lose everything but your speech when in Crit, and lose access to your radio channels and body in Death (MMI form).
Discord Discussion:
bugs-feedback thread Link
Technical details

If an entity has the Borg Chassis component, they ignore the Action Blocker for Speech
Media

In-game video demonstration

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

tweak: Cyborgs can now speak while in a Critical state.

Can you give them the stuttering trait while in crit as if the voice module damaged?

Can you give them the stuttering trait while in crit as if the voice module damaged? Just add and remove the comp for it when moving from one state to another.

I could but am personally unsure about it, since the MMI/Positronic Brain can speak perfectly fine without a body after dying as is, it would seem to be the voice itself comes from those instead of the Borg body

This would partially fix #21605 .


[BUG] EVM Account nft display issue

There are two issues in EVM account nft:
(1)In Batch move nft page, nft collections not show in selection area.

(2) In nft list, can not choose nft collections
https://github.com/user-attachments/assets/fc31cca8-8efb-42d4-b882-a3ea78c42be4

Cao already fixed this API issue.


slam_toolbox: 1.1.4-1 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository slam_toolbox to 1.1.4-1:

upstream repository: https://github.com/SteveMacenski/slam_toolbox.git
release repository: https://github.com/SteveMacenski/slam_toolbox-release.git
distro file: melodic/distribution.yaml
bloom version: 0.9.1
previous version for package: 1.1.3-1

This pull request has been mentioned on ROS Discourse. There might be relevant details there:
https://discourse.ros.org/t/preparing-for-melodic-sync-2020-06-09/14567/4


feat(observability): store and show the reasons of last N times of recovery

Just note down the idea now. It would be helpful for user to quickly debug.

I'm not sure if #13441 is necessary, which tries to handle corner cases that now I think rarely happen.
Let's first see whether #13624 suffices in practice.

Closed by #13441 and #13624


Limit BCER to interval [0,1]

Signed-off-by: Stefan Weil<EMAIL_ADDRESS>

With the current code lstmtraining reports character error rates larger than 100% when a new training starts. This is fixed here.


cuelang.org: mobile "share this page" UI element renders oddly

What page were you looking at?
https://cuelang.org/docs/concept/how-cue-works-with-json/
What version of the site were you looking at?
https://github.com/cue-lang/cuelang.org/commit/b5df5d4a9876d68820f1378ac125da185bcb5b80
What did you do?
I used a mobile device to read the page: webkit on iOS 17.5.1.
I scrolled to the bottom of the page content and looked at the "share this page" UI element.
What did you expect?
That the element would be rendered with the same broken-rectangle-with-upwards-arrow graphic as on desktop.
What did you see instead?
The graphic is present, but with an additional HTML-details-element, right-pointing arrow:

We checked and it also happens on safari desktop. The problem is with the details/summary html element which by default shows an arrow. We've hidden this arrow using css but apparantly safari/webkit works differently for that so we have to find a way to hide it there too.
See answer for:  https://stackoverflow.com/questions/6195329/how-can-you-hide-the-arrow-that-is-displayed-by-default-on-the-html5-details-e


Add alpha component to luma

I think luma deserves to have an alpha component. This PR adds one.

Probably it's better to make it 1 by default

Probably it's better to make it 1 by default

It is one by default though? Or am I miswing something?

From tests I thought that you should always pass second argument, but i missed one line, where it's not passed, sorry

Thanks!


The extension "Module Creator" should not be part of a base DNNplatform install

Description of problem
The extension "Module Creator" is not needed for the basic DNNPlatform install pack.
Description of solution
The extension "Module Creator" should be removed from DNNPlatform and made available as a separate installable extension.
Description of alternatives considered
None
Screenshots
Additional context
Affected browser

[X] Chrome
[X] Firefox
[X] Safari
[X] Internet Explorer
[X] Edge

Still an issue


[feat]: add variational dropout support for wide feature group

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


feat/create-treasury-wallet

working progress

Looking good @0xdevcollins. Could you just run the following database schema migration scripts for any tables and columns you may have created ?
https://github.com/bitcoin-sv/bsv-faucet?tab=readme-ov-file#database-schema-management

@0xdevcollins could you have another look to resolve the conflicts and also run the https://github.com/bitcoin-sv/bsv-faucet?tab=readme-ov-file#database-schema-management


(WIP) Object store hash algorithm agility

This is a proof of concept implementation for maintaining SHA-256 hashes for the default SHA-1 hashes. The hashes are calculated recursively for all objects, replacing the original SHA-1 hashes where needed in trees, commits, and tags.

Added some scaffolding to support different algorithms. This isn't used yet though because we need to settle the data model for the hash mapping.
This should be compatible with existing gittuf repos, it depends on the workflows where hashes are re-calculated and verified.
This goes back to the data model, certainly things we need to discuss!

I've added tests using Git's experimental implementation of SHA-256 repositories and have confirmed the hashes align with this prototype. :D

Closing as Git has early support for SHA-1 <-> SHA-256 compatibility. We should reevaluate with support for other hash algorithms later.


[Snyk] Upgrade html-snapshots from 4.4.0 to 4.4.1

Snyk has created this PR to upgrade html-snapshots from 4.4.0 to 4.4.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.

The recommended version was released on 5 days ago.

Release notes

Package name: html-snapshots

4.4.1 -<EMAIL_ADDRESS>

4.4.0 - 2024-09-12update devdeps

    from html-snapshots GitHub release notes

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:

🧐 View latest project report
📜 Customise PR templates
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

coverage: 99.245%. remained the same
when pulling 7e27451dee8c7d1fee4586588fbe37e348547312 on snyk-upgrade-90006f50e7120aaf4a2c511817a09189
into 36a2c2289187a195b9d94f2c3433afe62ef818a0 on master.


Adds Helm upgrade limitation to CC RN

Product Version(s):

Issue:

Link to docs preview:

SME review:

[ ] An SME has approved this change.

DOCS review:

[ ] A member of the docs team has approved this change.

Additional information:

Merge checklist:

[ ] Deploy preview inspected wherever changes were made
[ ] Build completed successfully
[ ] Test have passed

@bmckercher123 PTAL


Fixed: eslint range from 0.17 to 0.21 (0.11.2)

Thanks !

That was quick, thanks! :)

Released !

Awesome, thank you!

Thank you. Not me.

some people take quite much longer than this to merge and release, so I think it goes both ways :)


Scrolling support

I figure something like mod+shift+{h,j,k,l} can be used to issue a scroll in that direction.

Oh that's not a bad idea; but what about page down and up? Or are you thinking that mod+shift+{h,j,k,l} could issue a smaller scroll (i.e. one scroll wheel click)?
On 01/11/2017 02:12 PM, Jacob Thomas Errington wrote:
I figure something like mod+shift+{h,j,k,l} can be used to issue a scroll in that direction.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/kevin-li-195/zeno/issues/3, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKkPyyYz7rZo8fBwcpZLXRCQ-E8RCT3wks5rRSmrgaJpZM4Lg9K8.

Yeah, I'm thinking a smaller scroll amount. Page up/down is too much.


Trackpad/mouse affordances

Collecting questions related to supporting non-touchscreen devices with a trackpad or mouse. Eventually any changes should get their own issue.

Deleting items: should right click be available for deleting? Or duplicating? pop up menu would need to be icons, not words
Should cursor turn into pointer finger when over something that you can interact with using a trackpad
scrolling the character list with a mouse scrollwheel, it gets a bit stuck at the top
Are there other hover states that we should add?

Setting up a meeting with design team and DevTech team to figure out these design question.


Error during: Ensure Homebrew is installed

I have this issue on some mac machines, but i didn't find a good way to resolve it. I deleted the homebrew directory on my mac, but now i have problems during the cask installation because the casks are not registered within the new homebrew installation. Is there any solution to this. This came up during the lastest macOS updates.

I've got the same error:
fatal: [macmini62]: FAILED! => {"changed": false, "cmd": "/usr/bin/git clone --origin origin --depth 1 --branch master https://github.com/Homebrew/brew /opt/homebrew", "msg": "fatal: destination path '/opt/homebrew' already exists and is not an empty directory.", "rc": 128, "stderr": "fatal: destination path '/opt/homebrew' already exists and is not an empty directory.\n", "stderr_lines": ["fatal: destination path '/opt/homebrew' already exists and is not an empty directory."], "stdout": "", "stdout_lines": []}