CCE-543, refactor the section inline level help tooltip classes

to reduce amount of classes used for styling the refactoring was made, mainly only for the section 5.8 (Section Inline Level help for read-only fields)

@xak I'm merging this, since it looks to be fine and it's seating here since a couple days now


fix(API): Normalize response status to type str under py27

While not specified in the spec that the status must be of type str
(not unicode on Py27), some WSGI servers can complain when it is not.

Current coverage is 100% (diff: 100%)

Merging #986 into master will not change coverage

@@           master   #986   diff @@
====================================
  Files          31     31
  Lines        2055   2056     +1
  Methods         0      0
  Messages        0      0
  Branches      334    334
====================================
+ Hits         2055   2056     +1
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last update 21722fd...f1045c3


Consolidate how we check for MiqTask completion

There are multiple way different controllers check for MiqTask being successfully built and for it having the data available. Let's have a single way how to check completion and let's push that down to the model.
Fixes #9184
@miq-bot add_label refactoring, core, wip

@miq-bot remove_label wip
(I am done with manual testing).

Closing/opening for new magic merge commit for travis.  @isimluk Please ping me if it's green and this is ready to go.  Thanks!

Thanks @jrafanie!
The tests are green now. This is ready to be merged.


Change next random char code

Currently we use random.choices() to choose the next random char.  This means we need python 3.6 which is not compatible with pyinstaller latest.
Change the method of weighting the choice of the next random char.  Copy the active Koch charset into a temp and then add characters with < 90% proficiency OR less than the 50 samples.  This means the doubtful chars would appear twice in the temp.  Then use random.choice() on the temp to get the next char.

This has been done.  There should be no problem reverting to python 3.5 now.


Feature/use setter

I added an attribute that goes through a property setter instead of setting the value of the field directly.
This allows one to have arbitrary reactions to the entered value, from invoking an event after setting it to outright rejecting it.
It automatically looks for a property that matches the display name of the field, and one can explicitly give the property's name instead.
Let me know if you're interested in merging it. I haven't documented it in the readme in case it doesn't get merged anyway, but I'll be happy to document it if you want.

The current method relies on somewhat hardcoded logic that looks at the serialized type, attributes and stuff to figure out how to draw the property, esentially a re-write of many attributes.
I'm working on making it work with EditorGUILayout.PropertyField(), which would remove the need for that hardcoded logic.

Done.

It's compatible with all existing attributes (both Naughty and built-in) except other PropertyDrawers (as only one can be used at a time).
Supports Undo.
Automatically finds the matching property.
Shows a warning box if the property isn't found.

Hello mate. I am working on version 2.0.0 of the project. I am rewriting it from scratch. I will probably not be merging this into master, but I will make sure to implement your changes in the new version.

Oooohhh, interesting! What do you plan on changing for v2?
If you don't mind a feature request, this would be a perfect time to fix an issue I've had.
The way the AttributeDatabase works, it's not possible to make custom attributes without making them part of package. They must all be in the same assembly as the database.
I'm not sure of how this could be fixed, mind you. Maybe there is no other way.
Anyway, thank you for making NaughtyAttributes! It's an insta-add for all of my projects.

There are a lot of issues related to the structure of the project. I am scrapping the custom solution and will rewrite everything with Unity's CustomPropertyDrawers. The main issue is that nesting is not supported in v1, and a lot of people including me really want it. I tried to somehow make nesting support with recursively drawing elements, but I had some major issues and it didn't work quite well. With Unity's API nesting will work out of the box. There will be some exceptions, unfortunately. The [Button] attribute, for example, will not support nesting, because CustomPropertyDrawers can't target functions. [ShowNonSerializedField] and [ShowNativeProperty] will also not support nesting for the same reason (CustomPropertyDrawers can't target non-serialized members). These 3 will require a custom solution, but I will try to make it more simple this time. I created a custom solution, because I had some limitations with CustomPropertyDrawers back when I was developing v1, but I am gonna try to work my way around.
BTW, I will reopen the merge request so that I don't forget to implement it.

Cool! Not overriding the default inspector sounds great, and so do nested attributes.

Same as #74


Sidekick Release Candidate

This PR has been auto-generated from https://github.com/adobe/helix-sidekick/.

Changes:

https://github.com/adobe/helix-sidekick/pull/295


Fixed example code. It was missing a return block.

Currently the example code gives errors because there is no return block. This patch fixes that.

@ethanwillis Thx 4 your PR !


pull request for e2e test at 12/18/2016 18:26:17

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


使用latset镜像无法注册到nacos

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

nacos版本2.0.3，使用docker-compose拉取lastest镜像后启动无法注册到nacos
使用1.4.2版本可以正常注册
seata-server    | 10:21:53.261  INFO --- [                     main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 7091 (http) seata-server    | 10:21:53.284  INFO --- [                     main] o.a.coyote.http11.Http11NioProtocol      : Initializing ProtocolHandler ["http-nio-7091"] seata-server    | 10:21:53.288  INFO --- [                     main] o.apache.catalina.core.StandardService   : Starting service [Tomcat] seata-server    | 10:21:53.289  INFO --- [                     main] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.55] seata-server    | 10:21:53.574  INFO --- [                     main] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext seata-server    | 10:21:53.574  INFO --- [                     main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 4654 ms seata-server    | 10:21:55.891  INFO --- [                     main] o.s.b.a.w.s.WelcomePageHandlerMapping    : Adding welcome page: class path resource [static/index.html] seata-server    | 10:21:56.649  INFO --- [                     main] o.s.s.web.DefaultSecurityFilterChain     : Will secure Ant [pattern='/'] with [] seata-server    | 10:21:56.650  INFO --- [                     main] o.s.s.web.DefaultSecurityFilterChain     : Will secure Ant [pattern='/**/*.css'] with [] seata-server    | 10:21:56.651  INFO --- [                     main] o.s.s.web.DefaultSecurityFilterChain     : Will secure Ant [pattern='/**/*.js'] with [] seata-server    | 10:21:56.663  INFO --- [                     main] o.s.s.web.DefaultSecurityFilterChain     : Will secure Ant [pattern='/**/*.html'] with [] seata-server    | 10:21:56.663  INFO --- [                     main] o.s.s.web.DefaultSecurityFilterChain     : Will secure Ant [pattern='/**/*.map'] with [] seata-server    | 10:21:56.669  INFO --- [                     main] o.s.s.web.DefaultSecurityFilterChain     : Will secure Ant [pattern='/**/*.svg'] with [] seata-server    | 10:21:56.670  INFO --- [                     main] o.s.s.web.DefaultSecurityFilterChain     : Will secure Ant [pattern='/**/*.png'] with [] seata-server    | 10:21:56.671  INFO --- [                     main] o.s.s.web.DefaultSecurityFilterChain     : Will secure Ant [pattern='/**/*.ico'] with [] seata-server    | 10:21:56.672  INFO --- [                     main] o.s.s.web.DefaultSecurityFilterChain     : Will secure Ant [pattern='/console-fe/public/**'] with [] seata-server    | 10:21:56.672  INFO --- [                     main] o.s.s.web.DefaultSecurityFilterChain     : Will secure Ant [pattern='/api/v1/auth/login'] with [] seata-server    | 10:21:56.750  INFO --- [                     main] o.s.s.web.DefaultSecurityFilterChain     : Will secure any request with [org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter@5bda157e, org.springframework.security.web.context.SecurityContextPersistenceFilter@541afb85, org.springframework.security.web.header.HeaderWriterFilter@5efe47fd, org.springframework.security.web.authentication.logout.LogoutFilter@3dc68586, io.seata.console.filter.JwtAuthenticationTokenFilter@67e0fd6d, org.springframework.security.web.savedrequest.RequestCacheAwareFilter@7db40fd5, org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter@44b940a2, org.springframework.security.web.authentication.AnonymousAuthenticationFilter@21390938, org.springframework.security.web.session.SessionManagementFilter@7fe8c7db, org.springframework.security.web.access.ExceptionTranslationFilter@66d25ba9, org.springframework.security.web.access.intercept.FilterSecurityInterceptor@6aa5974e] seata-server    | 10:21:56.873  INFO --- [                     main] o.a.coyote.http11.Http11NioProtocol      : Starting ProtocolHandler ["http-nio-7091"] seata-server    | 10:21:56.918  INFO --- [                     main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 7091 (http) with context path '' seata-server    | 10:21:56.941  INFO --- [                     main] io.seata.server.ServerApplication        : Started ServerApplication in 10.721 seconds (JVM running for 12.844) seata-server    | 10:21:57.856  INFO --- [                     main] i.s.core.rpc.netty.NettyServerBootstrap  : Server started, service listen port: 8091 seata-server    | 10:21:57.935  INFO --- [                     main] io.seata.server.ServerRunner             : seata server started in 989 millSeconds
registry.conf
`
registry {
file 、nacos 、eureka、redis、zk、consul、etcd3、sofa
type = "nacos"
nacos {
application = "seata-server"
serverAddr = "IP:8848"
namespace = "dev"
cluster = "default"
username = "nacos"
password = "nacos"
}
}
config {
file、nacos 、apollo、zk、consul、etcd3
type = "nacos"
nacos {
serverAddr = "IP:8848"
group = "DEFAULT_GROUP"
namespace = "dev"
username = "nacos"
password = "nacos"
dataId = "seata-server.properties"
}
}
docker-compose.yml
version: '3'
services:
seata-server:
image: seataio/seata-server
hostname: IP
container_name: seata-server
ports:
- "8091:8091"
environment:
TZ: Asia/Shanghai
SEATA_IP: IP
SEATA_PORT: 8091
SEATA_CONFIG_NAME: file:/root/seata-config/registry
volumes:
- /docker/seata/config:/root/seata-config
privileged: true
restart: always
`
nacos配置中心文件已创建

用1.4.2

1.4.2 设置SEATA_IP为外网ip后，nacos内的地址还是容器地址

用1.4.2

1.5.1也注册不了，我nacos版本2.1.0

用1.4.2

1.5.1也注册不了，我nacos版本2.1.0

ok,我切换挂载springboot配置文件可以了


Error when Uploading MS Office files through Graph API to sharepoint online

We get an error when we upload MS files via Graph API to sharepointonline.  Stating that the size is different. I understand sharepoint add meta data to the file as soon as it is uploaded. The quesiton is, how can we upload the files and not receive that error?

Could you please provide more information about your issue? We'll tag so our bot replies with what we would require.


fix expire after default value

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


Does not match "unreleased" section

I am trying to create unstable releases and use the Unreleased section in a CHANGELOG.md.
I was hoping that instead of grepping for ## headers that match a v1.2.3-style semantic version, that when the version was missing, this action would simply pick the first sub-header, regardless of its title.
What do you think about this? Either, supporting "Unreleased" (and similar) as valid version identifier or just taking the versions[0] instead of running it through findVersionById?

It could be a good improvement of the action.
I am thinking about the default behavior which is currently to get the last version of the file. To keep this default behavior it could be better to support "Unreleased" version. Also it'll allow project's maintener to add other second level title without the risk of finding it in the version list.

@bjeanes Hi! You should now be able to use "Unreleased" as version number in your workflow.yml file.


add purge support for vpk

Is your feature request related to a problem? Please describe.
During testing velopack, i of course created alot of versions, which everyone has a -full and -delta .nupkg
This made me think
a) do i really need all the -full ? since my clients usually update fast, and even if they fail to update in time, they still can install to the latest feature, so -full is actually only needed for the last version ,maybe 2nd to last to calculate the -delta?
b) after some delta updates, like 5 or 10, it's not really necessairy to keep all older, in my estimate the patching (even if the files are smaller), will take longer then downloading the latest version
Describe the solution you'd like
a command like vpk pack purge --channel x --version-to-keep 1.1.0
which would
a) change the existing json files
b) remove uneccessary files
Describe alternatives you've considered
i will try to implement similar logic through my python support scripts, but i think this would be also helpful to other users.
Additional context
-None-

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

The pattern for releasing velopack software can start with an empty local directory and consists of vpk download -> vpk pack -> vpk upload. This way you do not need to store any local releases and delta releases can be created in CI etc where previous releases are not available.
The vpk upload commands have a --keepMaxReleases <COUNT> argument which will allow you to prune old releases when publishing your new releases.
See also:

https://docs.velopack.io/distributing/deploy-cli
https://docs.velopack.io/distributing/overview

To answer your other question b (which I missed the first time). Velopack already makes a calculation on whether it should try with delta's or with full releases. Delta's are pretty small and quick these days (in Squirrel days they were a lot slower) but your clients may still end up downloading full releases if Velopack thinks it will be faster.

Thanks, totally missed that you can use vpk upload local --keepMaxReleases
will try this right now!

Works like a charm
Retention policy about to delete 57 release(s)...


add increment, increment!, decrement and decrement! to model

Similar to ActiveRecord::Persistence.increment and decrement, this will add or subtract the value passed as by (default is 1) without calling save. There's also corresponding increment! and decrement! versions which save the resource afterwards.
page = Page.first # => #<Page(pages/1) id=1 views=5>
page.views # => 5
page.increment(:views)
page.views # => 6
page.increment(:views, 4)
page.views # => 10

page.reload.views # => 5
page.increment!(:views) # Saved via PUT "/pages/1"
page.views # => 6
page.decrement!(:views) # Saved via PUT "/pages/1"
page.views # => 5

@zacharywelch sorry - maybe I've introduced these conflicts in orm.rb with earlier merges? Can you clean up? Thanks :-)

rebased 👍


Call an External Endpoint to Retrieve Additional Information

Tutorial URL: https://developers.sap.com/tutorials/cp-integration-consume-external-api.html
In Step 1 after deploying the iFlow I get the message (several times now) Deployment failed.  Furthermore in the monitoring the artifact continues to have the status starting.  It never changes to failed although a popup came  which stated the deployment has failed.
Another thing is that in monitoring there isn no Ebdpoint ( There are no endpoints configured.)
In the iFlow itself there is a warning for the filter step. It says:
ontent Modifier may not pass Xml message to Filter. Filter supports Xml input only.
Any idea what is wrong here ? I followed the steps accurately and went over them several times.
UPDATE: My mistake. I had put java.lang Strong in stead of java.lang.String :-(

My mistake it was a typo


Godot 4?

Any chance you'd be interested in an upgrade?

Oh ok I see that this does everything needed anyway 👍
https://docs.godotengine.org/en/stable/classes/class_workerthreadpool.html

Hmm, they don't really cut it sadly :(

Well, shouldn't be too hard, the refactor for supporting Godot 4 should be simple enough.

Oh ok I see that this does everything needed anyway 👍

For fire-and-forget tasks, Godot 4's WorkerThreadPool is perfect. I don't know if there is a good way for handling continuations on the tasks dispatched to it, like this addon provides 🤔

Alright, Godot 4 support is done! The teste scene embedded in the project seems to be working flawlessly.
The main branch is now with the updated code, feel free to use it. I still need to upload a new asset to the Asset Library with it, but I won't look into it it right now.
I'm closing this issue, but feel free to open more issues if you find anything.
Cheers \o/

Wow thank you so much for the prompt response and PR ❤
I will try this out and make some suggestions & PRs if I find bugs!


Allow handling nil values in custom type

I had a similar type as mentioned: in https://github.com/elixir-ecto/ecto/issues/2576
Although the documentation clearly states that nil is bypassed, it's not clear why?
It is clearly an edge case, but  I'd still like to propose an opt in mechanism to allow custom types to handle nil values if they really want to.

The problem is that this change makes everything else slower since we are adding an extra check on all operations and loading all of the data is often the hotspot when loading thousands of entries at the same. It is unlikely we are going to change the behaviour regarding nil. Why does nil have to be handled in your case?

The problem is that this change makes everything else slower
Hm, ok that makes sense... I didn't think of that kind of scale

I really like how Ecto can transform data and safeguard the boundaries in my program.
I'd like to transform nil values into a maybe type
https://package.elm-lang.org/packages/elm/core/latest/Maybe
https://hexdocs.pm/algae/Algae.Maybe.html
So it  the have to be dealt with explicitly.
Any pointers on getting there in another way, would be appreciated

Hrm, I see. Unfortunately the nil assumption is ingrained in Ecto. There are places in changesets and associations that check for nil and change this will break it and make Ecto do things it is not supposed to. So I don't think a custom type would be enough, sorry.

No problem, at least I have a better understanding of the choices made now.


doc: apache/skywalking-ui:8.8.0 does not exist

Replace it with apache/skywalking-ui:8.8.1 which is the closest one
See the records from the Docker Hub:

[ ] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
[ ] Update the CHANGES log.

If you want to update this, it should  be 9.5.0 or x.y.z
All 8.x are EOL.

Thanks for the quick review!!!


Add .nvmrc

Since the contribution guidelines advise on a specific version of node,
it adding .nvmrc for those that use nvm will automatically let them use the
correct version of node if they do nvm use
just a small QOL thing for devs.

This PR fixes #

I just noticed my terminal automatically switching to the correct npm version and I thought "wait, did they add .nvmrc?"
That's great, thank you for the PR! :D


Allowing file format .glb to be inscribed.

A GLB file (. glb), which stands for “GL Transmission Format Binary file”, is a standardized file format used to share 3D data.
This file format allows for 3D objects to be viewed with a web based viewer. I suggest < model viewer > if we do want the ordinal website itself to display these. If not then just having .glb assets that could be called by other ordinals would allow for that experience too! Would love to be able to inscribe them now though until that issue is solved.

Resolved by #1666
Issue created after resolving PR
@BLE77 please close or include additional work required.

On my phone, but could someone follow up with an issue to create a .glb viewer? You can currently create .glb inscriptions, but not view them, which is not ideal.

https://github.com/casey/ord/issues/1707


Gather Extension

Rename extension id to the new DS Extension
API is no longer under exports.datascience..., its under exports.

@DavidKutu This isn't working for me? At least the one in the marketplace.

what happens? does it not activate? is the button not showing up?

Activation crashes. Gather threw an exception during activate

Oh no wait, now it's working. WTF. Let me try a different version (was using insiders)

Works now. I do need to reload but it gathers just fine.


DAP completions request line is 0-based from the debug console

I was debugging and noticed that the line in the completions request appears to be 0-based. The column is 1-based. DAP doesn't specify the base of the completions request, so I assume it should respect linesStartAt1  given in the initialize request, which vscode sets as true.

I tried reproducing this and I could not.
My steps use the new node debugger to debug the following file:
debugger; console.log('hello');
Once stopped, open debug console and type con and notice how the lineNumber: 1 is sent to the debug adapter for the completions since I am in the first line.
If I try it for other lines in a multi line console input it works just fine. 0 is never sent.

Nevermind, we converted internally to 0-based for some reason 🤦♂


Including postal envelope header resolverNoCache.

This should fix #74. Postal's tests already include test coverage for the resolverNoCache option. If you really want this to be covered in wascally, let me know (I didn't think it made sense for wascally's to worry about postal's internal cache in its tests).

Thanks so much, @ifandelse!


PDF files detected as plain/text

I faced the same issue #12 as reported in the original repository.
The proposed change was to run the file signature detection first, and then plain text detection.
That would definitely fix the issue and be more reliable.
Would you consider making this change?
If so, it might then be possible to improve the plain text detection to detect the file encoding.

@superjulius do you have a sample pdf that replicates this? I wasn't able to replicate it using a pdf generated by Microsoft Print to PDF on Windows 10. Improving handling of plan text files, is on my todo list.

@clarkis117 I unfortunately cannot share the PDF with which I faced the issue but you can definitely used the one referenced (http://www.orimi.com/pdf-test.pdf) in the issue mentioned above.

@superjulius I was not able to replicate this behavior on my dev branch for 0.6.0; therefore, it seems fixed. Just in case, I'm adding more data tests around pdfs.


Tagging versions / creating releases

I think it would be a great improvement if you start tagging versions :)

done


[gui error report] Error: Initializing daemon...

👉 Please describe what you were doing when this error happened.
Specifications

OS: win32
IPFS Desktop Version: 0.20.1
Electron Version: 17.1.0
Chrome Version: 98.0.4758.102

Error
Error: Initializing daemon...
go-ipfs version: 0.12.0
Repo version: 12
System version: amd64/windows
Golang version: go1.16.12
Found outdated fs-repo, migrations need to be run.
Looking for suitable migration binaries.
Need 1 migrations, downloading.
Downloading migration: fs-repo-11-to-12...
Fetching with HTTP: "https://ipfs.io/ipfs/QmdaCHYBDHEhXCMoynH5UcohEay6m1XayZCcxWZzKAHNVN/fs-repo-11-to-12/versions"
Fetching with HTTP: "https://ipfs.io/ipfs/QmdaCHYBDHEhXCMoynH5UcohEay6m1XayZCcxWZzKAHNVN/fs-repo-11-to-12/v1.0.2/fs-repo-11-to-12_v1.0.2_windows-amd64.zip"
Fetching with HTTP: "https://ipfs.io/ipfs/QmdaCHYBDHEhXCMoynH5UcohEay6m1XayZCcxWZzKAHNVN/fs-repo-11-to-12/v1.0.2/fs-repo-11-to-12_v1.0.2_windows-amd64.zip"
Fetching with HTTP: "https://ipfs.io/ipfs/QmdaCHYBDHEhXCMoynH5UcohEay6m1XayZCcxWZzKAHNVN/fs-repo-11-to-12/v1.0.2/fs-repo-11-to-12_v1.0.2_windows-amd64.zip"
Error fetching: exceeded number of retries. last error was http.DefaultClient.Do error: Get "https://ipfs.io/ipfs/QmdaCHYBDHEhXCMoynH5UcohEay6m1XayZCcxWZzKAHNVN/fs-repo-11-to-12/v1.0.2/fs-repo-11-to-12_v1.0.2_windows-amd64.zip": dial tcp <IP_ADDRESS>:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connect

That's basically what happened to me in https://github.com/ipfs/ipfs-desktop/issues/2017. Just a bad connection for a while, and it won't retry on the next start.

Duplicate of https://github.com/ipfs/ipfs-desktop/issues/2023


wluma: init at 2.0.1

Motivation for this change
wluma is a tool for wlroots-based compositors that automatically adjusts screen brightness based on the screen contents and amount of ambient light around you.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

I can't test this, but if it works for you @yevhenshymotiuk then I'll merge it.

I can't test this, but if it works for you @yevhenshymotiuk then I'll merge it.

Yes, it works for me. I've been using it for a few weeks already with no problems


Deduplication

PR moves loc_get_id into common.c. This solution uses the id position within the corresponding structs (at the beginning), which can be a bit tricky. The alternative solution with common.h and macro controlled getter was explored as well, but it was way too complicated (we use both make and cmake + Windows behave differently than sane OSs).
I'm not sure we want to merge this – maybe it would be better to accept some duplication so I'm opening this as a draft.

(I've just rebased to the latest main.)


Can't configure roles

"roles" written in end of file(or after plugins) can't configure.
Only when written at the beginning(or before plugins) is valid.
$ cat /etc/mackerel-agent/mackerel-agent.conf

apikey = "apikey"
include = "/etc/mackerel-agent/conf.d/*.conf"

[plugin.metrics.linux]
command = "mackerel-plugin-linux"
[plugin.metrics.nginx]
command = "mackerel-plugin-nginx"
[plugin.metrics.multicore]
command = "mackerel-plugin-multicore"
[plugin.metrics.uwsgi-vassal]
command = "mackerel-plugin-uwsgi-vassal --socket unix:///var/run/uwsgi/stats.sock"
[plugin.metrics.accesslog]
command = "mackerel-plugin-accesslog /var/log/nginx/access.log"

roles = [ "My-Service:app", "Another-Service:db" ]

rolesがpluginの後に書かれた場合、設定が反映されません。
apikeyの下など、先頭に書かれたときのみ有効となりました。

This is an expected behavior not a bug due to the TOML's spec. I'd appreciate if you understand.
See https://github.com/toml-lang/toml for reference.


ParticleEmitter copy constructor does not copy premultiplied alpha attribute

I discovered this while trying to use a ParticleEffect that has ParticleEmitters with premultiplied alpha with a ParticleEffectPool.
Not sure why the comment "Backwards compatibility" is used in reference to loading premultiplied alpha state in the load (BufferedReader reader). Is premultiplied alpha not really supported? Premultiplied alpha is super helpful for particle effects. It opens up a lot of possibilities that alpha blending and additive blending don't offer.

This was already fixed:
https://github.com/libgdx/libgdx/commit/80b37dfe893cef4aada205828669cdaad74a55cc
The backwards compatibility note was so files created prior to the addition of premultipliedAlpha could still be loaded.

Oops! Didn't turn up in my search.


Typescript includes installation directory typings (in AppData)

TypeScript Version:  3.4.0-dev.201xxxxx

Search Terms:
Code
// A *self-contained* demonstration of the problem follows...
// Test this by running `tsc` on the command-line, rather than through another build tool such as Gulp, Webpack, etc.

Expected behavior:
Local module 'alt' uses local declaration file
Correction: importing 'alt' never resolves to TypeScript installation
Actual behavior:
Importing alt resolves to<EMAIL_ADDRESS>Playground Link:
Related Issues:

We would need a complete repro to try to investigate this.

@RyanCavanaugh  I believe I started seeing this when I installed VS 2019. And now<EMAIL_ADDRESS>is conflicting with VSCode's (or the node module in my project anyway<EMAIL_ADDRESS>Is it safe to delete the AppData Typescript folder?

Reproduction:
import alt from 'alt';

in a file named test.js

For the reference this goes into typescript, not just vscode - no error logged (or in my use case, I'd see false errors due to the wrong package):

I would like for this issue to be reopened, since I provided a clear reproduction.

@rsxdalv What exactly is wrong here?

@rsxdalv turn on the option "typescript.disableAutomaticTypeAcquisition" to disable automatically getting types from @types


Problem installing Design System package from npm

I'm trying to install the design system package from https://www.npmjs.com/package/@iqss/dataverse-design-system to use in the demo repository.  I have .npmrc defined as
legacy-peer-deps=true

# design-system registry
//registry.npmjs.org/:_authToken=<github token>
@iqss:registry=https://registry.npmjs.org/

# js-dataverse registry
//npm.pkg.github.com/:_authToken=<github token>
@iqss:registry=https://npm.pkg.github.com/

When I install with just the package name, it's not found, because it's looking for it in github
 npm install @iqss/dataverse-design-system
npm ERR! code E404
npm ERR! 404 Not Found - GET https://npm.pkg.github.com/@iqss%2fdataverse-design-system - npm package "dataverse-design-system" does not exist under owner "iqss"
npm ERR! 404
npm ERR! 404  '@iqss/dataverse-design-system@*' is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

 TAR_BAD_ARCHIVE: Unrecognized archive format

This is the demo repository where I'm trying to install: https://github.com/ekraffmiller/js-dataverse-vite-demo

This was caused by the .npmrc file needing to refer to two different registries.  It will be fixed when the new js-dataverse is published in npm: https://github.com/IQSS/dataverse-client-javascript/issues/113


Update store rewrite and new task API

This tracking issue follows the development of the update store rewrite of the update store and the introduction of the new task API.
Goals
The goals for this project are:

re-designing the update store with the insights from #1679
introduce the task API
Making all write operation asynchronous
Preparing for HA
Preparing for auto-batching

Steps
Since this is a large task, I have identified multiple sub-parts to the project. The project will be merged continuously on a time frame spanning to release cycles, and will be only accessible with the feature flag task-api.

[ ] Introduce a new crate in the workspace: meilisearch-tasks.
[ ] Define the update API.
[ ] Implement core functionalities (push update, pop and perform update)
[ ] Implement listing of update, and state query
[ ] Introduce new routes in meilisearch-http
[ ] Connect the new update store to meilisearch-http

Specifications

https://github.com/meilisearch/specifications/blob/develop/text/0060-refashion-updates-apis.md

Unresolved question
tbd.

This issue follows this spec: Refashion the Updat API
It impacts the @meilisearch/docs-team and the @meilisearch/integration-team


How to point to correct folder?

Hi, The form I have is located at https://dar-us-salam.com/kids/games-toys/ . When subscribing it displays this error "There was an error please try again." and in the browser inspect log it shows this:
404 Error
GET https://dar-us-salam.com/kids/modules/sendynewsletter/subscribe.php
The problem is that it should be going one folder back to this URL:
https://dar-us-salam.com/modules/sendynewsletter/subscribe.php
Can you please let me know where I can correct this?

I figured it out. It was a line in the sendynewsletter.js file in the sendynewsletter\views\js folder.
I changed the line 13
url: '../modules/sendynewsletter/subscribe.php',
to the full URL:
url: 'https://dar-us-salam.com/modules/sendynewsletter/subscribe.php',
And now it works flawlessly. Alhamdulillah


Ability = None issue

{'is_local': True, 'code': 11, 'ability': None, 'is_init': False, 'is_camera_movement': False, 'frame': 37612, 'pid': 1, 'player': Player 1 - xxxxx (Terran), 'second': 2350, 'is_unknown': False, 'type': 1, 'is_player_action': True}
Replay ability set to None.
The replay testes can be downloaded here: http://www.sc2replayed.com/replays/176215-1v1-terran-taldarim-altar-le
Same is also the case for this:
http://www.sc2replayed.com/replays/176213-1v1-terran-protoss-backwater-gulch
which is another build.

The root issue with the Ability not being passed through the constructor was resolved months ago.


STY: fix a couple of formatting issues in roadmap doc.

[ci skip]
trivial commit, but http://scipy.github.io/devdocs/roadmap.html looks ugly now.

Thanks Ralf


[Intel MKL] Add FP32 fusion of MatMul and Relu.

This the 2nd part of Enable FP32 FusedMatMul(MatMul with BiasAdd) for MKL-DNN backend(https://github.com/tensorflow/tensorflow/pull/31782). It will fuse Relu/Relu6/Elu with FusedMatMul and rewrite it to MklFusedMatMul.
Modified:

tensorflow/core/graph/mkl_layout_pass.cc
tensorflow/core/kernels/mkl_fused_ops_test.cc
tensorflow/core/kernels/mkl_matmul_op_fused.cc
tensorflow/core/kernels/mkl_matmul_ops_common.h

Signed-off-by: Lu Teng<EMAIL_ADDRESS>

The previous PR(#31782) will fuse MatMul and BiasAdd into FusedMatMul, and rewrite it to MklFusedMatMul, but it will prevent 2 situations:

Attribute transpose_a is false.
FusedMatMul must has only one post op(default is BiasAdd, but it will be fused with BiasAdd and Relu if possible).

The 2nd rule will impact performance of some models like NCF because FusedMatMul wasn't rewritten to MklFusedMatMul and went into Eigen path. This PR will optimize it to MKL-DNN and remove the 2nd limitation by fusing it with Relu/Relu6/Elu.

@penpornk please let us know if we can do anything for the PR to merge. We are thinking to have this PR merged before TF 2.1 cutoff.

Hi @penpornk ,thanks for your suggestion, we've found an internal issue related to Elu in MKL back-end:
We used SetRandom() in UT to test the fusion ops, but it only generate positive value so that Elu become the same as Relu, then we weren't aware the typo error in UT. Besides, I found that we set wrong alpha for Elu and got wrong result after I corrected UT. Alpha in Elu should be 1 but not 0: https://github.com/intel/mkl-dnn/blob/master/src/common/math_utils.hpp#L189
Now  I have fixed it with this PR, please take a look at the new changes, thanks!

Close this PR because migrated to GitLab: https://gitlab.devtools.intel.com/TensorFlow/Direct-Optimization/private-tensorflow/merge_requests/30

I made a new change after an internal discussion - separate the Conv correction part from this PR and will fix it in another PR. It will make bug fix and feature implementation more clear.


TE-3.7: update with changes from #1135

Implements changes described in #1135 by @xw-g

Implement TODOs
Add implicit in-place add scenario.
Add implicit in-place remove scenario.
Update implicit in-place replace scenario.

This code is a Contribution to the OpenConfig Feature Profiles project ("Work") made under the Google Software Grant and Corporate Contributor License Agreement ("CLA") and governed by the Apache License 2.0. No other rights or licenses in or to any of Nokia’s intellectual property are granted for any other purpose. This code is provided on an "as is" basis without any warranties of any kind.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 56.84%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1234

Relevant Lines:
2171

💛  - Coveralls

@mojiiba The code changes are to implement #1135, and the code looks good to me. Can you help take another look if any concerns blocking the merge?
For additional "deviations" needed by your team, please help open another PR later. Thanks.

@mojiiba The code changes are to implement #1135 (to close some testing gaps), and the code looks good to me. Can you help take another look if any concerns blocking the merge?
For additional "deviations" needed by your team, please help open another PR later. Thanks.

sure, @manan-patel is reviewing it.

@LimeHat, we will need an existing deviation (GRIBIMACOverrideWithStaticARP), Can you please integrate the below code
git diff
diff --git a/feature/gribi/ate_tests/base_hierarchical_nhg_update/base_hierarchical_nhg_update_test.go b/feature/gribi/ate_tests/base_hierarchical_nhg_update/base_hierarchical_nhg_update_test.go
index be0981c..543c06f 100644
--- a/feature/gribi/ate_tests/base_hierarchical_nhg_update/base_hierarchical_nhg_update_test.go
+++ b/feature/gribi/ate_tests/base_hierarchical_nhg_update/base_hierarchical_nhg_update_test.go
@@ -86,6 +86,17 @@ var (
IPv4Len: 30,
}

  dutPort2DummyIP = attrs.Attributes{

          Desc:    "DUT Port 2",

          IPv4:    "<IP_ADDRESS>",

          IPv4Len: 30,

  }

  dutPort3DummyIP = attrs.Attributes{

          Desc:    "DUT Port 3",

          IPv4:    "<IP_ADDRESS>",

          IPv4Len: 30,

  }

  atePort1 = attrs.Attributes{
          Name:    "atePort1",
          IPv4:    "<IP_ADDRESS>",

@@ -135,12 +146,31 @@ func TestBaseHierarchicalNHGUpdate(t *testing.T) {
dutP2 := dut.Port(t, "port2").Name()
dutP3 := dut.Port(t, "port3").Name()
t.Logf("Adding gribi routes and validating traffic forwarding via port %v and NH ID %v", dutP2, p2NHID)

  addInterfaceRoute(ctx, t, gribic, p2NHID, dutP2)

  if deviations.GRIBIMACOverrideWithStaticARP(ondatra.DUT(t, "dut")) {

          d := gnmi.OC()

          p2 := dut.Port(t, "port2")

          p3 := dut.Port(t, "port3")

          gnmi.Update(t, dut, d.Interface(p2.Name()).Config(), dutPort2DummyIP.NewOCInterface(p2.Name()))

          gnmi.Update(t, dut, d.Interface(p3.Name()).Config(), dutPort3DummyIP.NewOCInterface(p3.Name()))

          gnmi.Update(t, dut, d.Interface(p2.Name()).Config(), configStaticArp(t, p2, "<IP_ADDRESS>", pMAC))

          gnmi.Update(t, dut, d.Interface(p3.Name()).Config(), configStaticArp(t, p3, "<IP_ADDRESS>", pMAC))

  }

  if deviations.GRIBIMACOverrideWithStaticARP(ondatra.DUT(t, "dut")) {

          addInterfaceRoute(ctx, t, gribic, p2NHID, dutP2, "<IP_ADDRESS>")

  } else {

          addInterfaceRoute(ctx, t, gribic, p2NHID, dutP2)

  }
  addDestinationRoute(ctx, t, gribic)
  validateTrafficFlows(t, ate, []*ondatra.Flow{p2flow}, []*ondatra.Flow{p3flow}, nil, pMACFilter)

  t.Logf("Adding a new NH via port %v with ID %v", dutP3, p3NHID)

  addNH(ctx, t, gribic, p3NHID, dutP3, pMAC)

  if deviations.GRIBIMACOverrideWithStaticARP(ondatra.DUT(t, "dut")) {

          addNH(ctx, t, gribic, p3NHID, dutP3, pMAC, "<IP_ADDRESS>")

  } else {

          addNH(ctx, t, gribic, p3NHID, dutP3, pMAC)

  }
  t.Logf("Performing implicit in-place replace with two next-hops (NH IDs: %v and %v)", p2NHID, p3NHID)
  addNHG(ctx, t, gribic, interfaceNHGID, []uint64{p2NHID, p3NHID})
  validateTrafficFlows(t, ate, nil, nil, []*ondatra.Flow{p2flow, p3flow}, pMACFilter)

@@ -153,9 +183,12 @@ func TestBaseHierarchicalNHGUpdate(t *testing.T) {
}
// addNH adds a GRIBI NH with a FIB ACK confirmation via Modify RPC
-func addNH(ctx context.Context, t *testing.T, gribic *fluent.GRIBIClient, id uint64, intf, mac string) {
+func addNH(ctx context.Context, t *testing.T, gribic *fluent.GRIBIClient, id uint64, intf, mac string, nhip ...string) {
nh := fluent.NextHopEntry().WithNetworkInstance(*deviations.DefaultNetworkInstance).
WithIndex(id).WithInterfaceRef(intf).WithMacAddress(mac)

  if len(nhip) > 0 {

          nh = nh.WithIPAddress(nhip[0])

  }
  gribic.Modify().AddEntry(t, nh)
  if err := awaitTimeout(ctx, gribic, t, time.Minute); err != nil {
          t.Fatalf("Await got error for entries: %v", err)

@@ -233,9 +266,12 @@ func addDestinationRoute(ctx context.Context, t *testing.T, gribic *fluent.GRIBI
// addInterfaceRoute creates a GRIBI route that points to the egress interface defined by id,
// port, and nhip.
-func addInterfaceRoute(ctx context.Context, t *testing.T, gribic *fluent.GRIBIClient, id uint64, port string) {
+func addInterfaceRoute(ctx context.Context, t *testing.T, gribic *fluent.GRIBIClient, id uint64, port string, nhip ...string) {
inh := fluent.NextHopEntry().WithNetworkInstance(*deviations.DefaultNetworkInstance).
WithIndex(id).WithInterfaceRef(port).WithMacAddress(pMAC)

  if len(nhip) > 0 {

          inh = inh.WithIPAddress(nhip[0])

  }
  inhg := fluent.NextHopGroupEntry().WithNetworkInstance(*deviations.DefaultNetworkInstance).
          WithID(interfaceNHGID).AddNextHop(id, 1)
  ipfx := fluent.IPv4Entry().WithNetworkInstance(*deviations.DefaultNetworkInstance).

@@ -435,3 +471,13 @@ func validateTrafficFlows(t *testing.T, ate *ondatra.ATEDevice, good, bad, lb []
}
}
}
+
+func configStaticArp(t *testing.T, p *ondatra.Port, ipv4addr string, macAddr string) *oc.Interface {

  i := &oc.Interface{Name: ygot.String(p.Name())}

  i.Type = oc.IETFInterfaces_InterfaceType_ethernetCsmacd

  s := i.GetOrCreateSubinterface(0)

  s4 := s.GetOrCreateIpv4()

  n4 := s4.GetOrCreateNeighbor(ipv4addr)

  n4.LinkLayerAddress = ygot.String(macAddr)

  return i

+}

@LimeHat We need the following deviation "GRIBIMACOverrideWithStaticARP", can you please add it.
TE-3.7-deviation.log

Thanks for the review @xw-g & @manan-patel , updated according to the comments/discussion.

@manan-patel any further concern? Please help approve this PR if there is no further concerns.
Note that when one vender needs a deviation I strongly prefer another incremental PR to be filed by that vendor to iterate the code, instead of asking the PR author to do it. Since @LimeHat already did it, I'm ok to proceed.
Also. @cprabha any concerns with this PR? Thanks.

@xw-g
Not all the provided diffs are merged by @LimeHat, this TC will start failing once PR is merged for some vendors. To address that we should submit another deviation PR right away
Adding @vosipchu @prinikasn @guoshiuan to keep in loop

@manan-patel could you elaborate on what is missing?
I think the only part I didn't add is the "dummy IP" configuration, but I'm not sure what is the purpose of using it (if you only need a static ARP entry?)
Or it has to be a static arp pointing to a new IP address?

@LimeHat
As a part of the deviation, if we just configure static arp on port 2 and port 3 it will end up not establishing a connection between DUT<>ATE.
By having a dummy ip, we configure static arp to those addresses and use them for gribi programming, while the link between DUT<>ATE gets resolved by dynamic arp.

Alright, I added the dummy ip cfg as well.

@manan-patel I prefer your team to file a quick PR to iterate, once this is merged. I'm not expecting one vendor to know all details about another vendor's deviation behavior and addressed it in the same PR.
So, do you have other non-deviation related concerns? ok to merge?

@LimeHat Thank you for addressing it
@xw-g Acknowledged

/gcbrun


Replace Usage-Logging with orchestrator specific logging docs?

The stuff in Usage-Logging https://github.com/tigera/calico/blob/master/master/using-calico/troubleshooting/logging.md is container-centric.
For example, in Openstack: there's no calico-node container, bird is not configured using calicoctl, felix log-level is not set using calicoctl, there's no confd and it doesn't use calico ipam.
Perhaps this info should move to an -Logging document?

Yeah, that page needs work.  I think it's fine to keep a "Configuring log levels" type usage page, but it needs to be clear which components are relevant for which types of deployments.
@tmjd do you want to try to tackle this one?

Yeah I'll add that to my list.  I think this is a good thing because we do regularly get questions asking where do I find logs.  That may not specifically go in this page but there should maybe be a couple logging pages (configuring, viewing) and will need some orchestrator specific info too.

The usage/logging documentation needs a few things:

[ ] Review to make sure it's up-to-date
[ ] Change title from "Logging" to "Configuring logging"
[ ] Add in any missing configuration dials.

Can I request that we don't lose the original spirit of this Issue and add "makes sense for all orchestrators" to the list of requirements please?


DICOM images are wrongly displayed

Hi OHIF Community,
DICOM images are shown in the wrong way, half of the image is reversed, shared in the screenshot below. Maybe, we're doing something wrong with configurations?

[ SOLVED ] it was an issue from the PACS side


Fix running error by reverting import with type json

When running the tool, the following error is returned:
npx --yes gitlab-ci-local@latest
file:///Users/username/.npm/_npx/3f18f2096def1b34/node_modules/gitlab-ci-local/src/index.js:13
import packageJson from "../package.json" with { type: "json" };
                                          ^^^^

SyntaxError: Unexpected token 'with'
    at ESMLoader.moduleStrategy (node:internal/modules/esm/translators:119:18)
    at ESMLoader.moduleProvider (node:internal/modules/esm/loader:468:14)
    at async link (node:internal/modules/esm/module_job:68:21)

Node.js v18.18.2

Minimal .gitlab-ci.yml illustrating the issue
---
job:
  script:
    - echo "Heya"

Expected behavior
Tool to run
Host information
MacOs
gitlab-ci-local 4.55
Containerd binary
Are you using docker
Additional context
This seems related to #1331 and #1337
My installed typescript version is 5.6.3, so I don't think it's that.
Still trying to figure out why this doesn't work.

Locally, if I compile with npm run esbuild and run ./bin/index.cjs it works fine.
But if I compile with npm run build and run node src/index.js I get the error.

i am using NODE_OPTIONS="$NODE_OPTIONS --experimental-vm-modules" to run locally
i am guessing you're trying to do some local dev..
i'll actually recommend using tsx directly, or not npm run dev is nice too

You can set NODE_OPTIONS="$NODE_OPTIONS --experimental-vm-modules"
the error should be gone

I'll give it a go

i am guessing you're trying to do some local dev..

No actually, I was using npx gitlab-ci-local@latest to run the project without directly installing it, I'm not sure what happens when I install it normally

No actually, I was using npx gitlab-ci-local@latest to run the project without directly installing it, I'm not sure what happens when I install it normally

It still does fail.

# needs at least node:18.20
FROM node:18.20

WORKDIR /app

RUN apt-get update && \
  apt-get install -y rsync git && \
  rm -rf /var/lib/apt/lists/*

RUN cat <<EOF > .gitlab-ci.yml
---
job:
  script:
  - echo "hello world" \
EOF

RUN  npx gitlab-ci-local@latest

seemed like you'll need to upgrade your node to 18.20 and beyond

and to be honest, i am not sure what value does the  with { type: "json" }; adds

and to be honest, i am not exactly sure what value does the  with { type: "json" }; adds

After building, running node src/index.js fails with:

node:internal/errors:496
    ErrorCaptureStackTrace(err);
    ^

TypeError [ERR_IMPORT_ASSERTION_TYPE_MISSING]: Module "file:///Users/username/work/gitlab-ci-local/package.json" needs an import assertion of type "json"
    at new NodeError (node:internal/errors:405:5)
    at validateAssertions (node:internal/modules/esm/assert:95:15)
    at defaultLoad (node:internal/modules/esm/load:91:3)
    at nextLoad (node:internal/modules/esm/loader:163:28)
    at ESMLoader.load (node:internal/modules/esm/loader:603:26)
    at ESMLoader.moduleProvider (node:internal/modules/esm/loader:457:22)
    at new ModuleJob (node:internal/modules/esm/module_job:64:26)
    at #createModuleJob (node:internal/modules/esm/loader:480:17)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:434:34)
    at async ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:79:21) {
  code: 'ERR_IMPORT_ASSERTION_TYPE_MISSING'
}

and to be honest, i am not exactly sure what value does the  with { type: "json" }; adds

opps, i was'nt saying that it's not good.. was actually about to approve it
but yeah anyways, don't really have too much opinion on the way to import the json file...

And with the latest commit, it fails with
undefined:1
./schema.json
^

SyntaxError: Unexpected token . in JSON at position 0
    at JSON.parse (<anonymous>)
    at Object.<anonymous> (/Users/username/work/gitlab-ci-local/bin/index.cjs:157:7577)
    at Module._compile (node:internal/modules/cjs/loader:1256:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
    at Module.load (node:internal/modules/cjs/loader:1119:32)
    at Module._load (node:internal/modules/cjs/loader:960:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:86:12)
    at node:internal/main/run_main_module:23:47

Node.js v18.18.2

I suspect because ./schema.json doesn't exist when built together (and that I'm not sure how to fix)

https://github.com/firecow/gitlab-ci-local/blame/master/README.md#L391
most effortless change would be update to node 18.20 + 😂

I agree it's a good idea to update the required version.
On my end, that'll take some time, and I've managed to get the branch in a state where everything is passing.
I'd appreciate the acceptance of an interim solution for us.

I can't re-open this PR, but I can make a new one if you can't either.


Scroll up

Would be nice to have ability to scroll up.
Eg. Facebook chat, where you scroll up to see your previous messages.
Any ideas on that or any Forks I could use?

@joserivera12 and i made a pr to make this you can check in https://github.com/ankeetmaini/react-infinite-scroll-component/pull/207

This is now added in the latest version. Thanks to @osmarpb97


accept rule as anónymous function

Current:
var TextLintEngine = require("textlint").TextLintEngine;
var engine = new TextLintEngine({
    rules: ["textlint-rule-spellcheck-tech-word"]
});

var TextLintEngine = require("textlint").TextLintEngine;
var engine = new TextLintEngine({
    rules: [require("textlint-rule-spellcheck-tech-word")]
});

Good?

This feature prevent rule options #15 .
So, we want to syntax more reasonable.

This function will not implemented. :(


cli/common: make the USR mountpoint a runtime flag

This updates common CLI logic so that the USR mountpoint (usually at
/usr) can be adjusted at runtime via the TORCX_USR_MOUNTPOINT
environment flag.

/cc @euank @squeed for review

@euank thanks, I'll queue your additional comments in the next PR.


Query fixes

Simplifies number of users querying. Also correct printf 0-padding format to better reflect the original intention.
May solve issue #65

Thanks for the merge.

Thanks for the patches!

I just noticed your new pull request.  This issue is fixed there.


RFC7591: Use default values for 'response_types' and 'grant_types'

The RFC7591 dynamic client registration indicates default values for response_types and grant_types:

If omitted, the default is that the client will use only the "code" response type.
If omitted, the default behavior is that the client will use only the "authorization_code" Grant Type.

What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

[x] You consent that the copyright of your pull request source code belongs to Authlib's author.

I am not so sure of the implementation of this PR. I will reopen it soon.


Reverse mask for numbers

Is it possible to reverse the filling of the input mask for numbers, like currency?
Example: 0,00 mask:
Input 1 results in 0,01
Input 1234 results in 12,34
Input 12 results in 0,12

Hello Caio, I need to know why do you need that feature at a global level, because I'm not sure such a functionality is useful, if you have a 2 decimal mask would it fit your need ? You could always divide/multiplicate it by 100 after the input.

The thing is the way it works you always need to input leading zeros to reach the end of the mask. When you type in currency leading zeros are insignificant. You don’t want to force leading zeros on your user. That’s where filling from right to left becomes relevant. It’s a feature present/requested in other libraries and language as well:Input Mask Currencycodepen.iohttps://github.com/sanniassin/react-input-mask/issues/120Money question · Issue #644 · RobinHerbots/Inputmaskgithub.comIt’s not just for money too. Any number with insignificant leading zeros and a significant information at the end of the mask could benefit from it. Thanks for replyingCaioEm 9 de dez. de 2023, à(s) 08:54, Raphaël Desalbres @.***> escreveu:
Hello Caio, I need to know why do you need that feature at a global level, because I'm not sure such a functionality is useful, if you have a 2 decimal mask would it fit your need ? You could always divide/multiplicate it by 100 after the input.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Hi Caio,
Unfortunately it's a too much specific question for me to handle.
Please refer to https://imask.js.org as this is the component BlazorInputMask uses. Their mask plugin has infinite use cases.  If necessary you can open an issue with them, and after include BlazorInputMask in your project and adapt it to fit your need as it's open source.
Regards,
Raphaël

Thanks for replying anyway. I ended up managing to use robinherbots library. It has the numeric input setting that does what I need (fill from right to left). Imask doesn’t implement it. CaioEm 10 de dez. de 2023, à(s) 15:57, Raphaël Desalbres @.***> escreveu:
Hi Caio,
Unfortunately it's a too much specific question for me to handle.
Please refer to https://imask.js.org as this is the component BlazorInputMask uses. Their mask plugin has infinite use cases.  If necessary you can open an issue with them, and after include BlazorInputMask in your project and adapt it to fit your need as it's open source.
Regards,
Raphaël
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


Some fixes

Fixes #6781, #6789
I'll attempt to cherry-pick, but as this is "just" a failure-branch, if it doesn't work I'm not going to worry.

Merged to master.  Cherry-picked to 1.1.0  The EC part was cherry-picked to 1.0.2
Thanks for the review, closing this.


Database connectivity problem: {"cache_timeout":["Not a valid integer."]}

I don't have this fully figured out but opening to establish a record for others.
How to reproduce the bug
Go to Databases -> Edit database -> Performance.  Leave the first two cache timeouts blank (chart, schema) and put 3600 for the last one.  Click Finish.
Expected results
Values save.
Actual results
Error on screen:

Accompanied by a PUT request resulting in 400 in the logs.
Workaround
Put values of 300, 300 (in one instance Superset changed this to 299??) and 14400 for the cache timeout values.  Those are accepted.
Environment
-Superset 2.0.0, docker-compose deployed
-MSSQL database
Additional context
I was troubleshooting a problem where my table list wouldn't refresh, despite being able to query a new table in SQL Lab.  First the table list didn't refresh, then I changed a timeout setting and afterward would get this error when it tried to list tables:
2022-09-22 18:19:59,211:ERROR:superset.views.base:value is not an integer or out of range
Traceback (most recent call last):
  File "/app/superset/views/base.py", line 185, in wraps
    return f(self, *args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/flask_appbuilder/security/decorators.py", line 175, in wraps
    return f(self, *args, **kwargs)
  File "/app/superset/utils/log.py", line 245, in wrapper
    value = f(*args, **kwargs)
  File "/app/superset/views/core.py", line 1122, in tables
    for datasource_name in database.get_all_table_names_in_schema(
  File "/app/superset/utils/cache.py", line 146, in wrapped_f
    cache.set(cache_key, obj, timeout=kwargs.get("cache_timeout"))
  File "/usr/local/lib/python3.8/site-packages/flask_caching/__init__.py", line 267, in set
    return self.cache.set(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/flask_caching/backends/rediscache.py", line 163, in set
    result = self._write_client.setex(
  File "/usr/local/lib/python3.8/site-packages/redis/client.py", line 1822, in setex
    return self.execute_command('SETEX', name, time, value)
  File "/usr/local/lib/python3.8/site-packages/redis/client.py", line 901, in execute_command
    return self.parse_response(conn, command_name, **options)
  File "/usr/local/lib/python3.8/site-packages/redis/client.py", line 915, in parse_response
    response = connection.read_response()
  File "/usr/local/lib/python3.8/site-packages/redis/connection.py", line 756, in read_response
    raise response
redis.exceptions.ResponseError: value is not an integer or out of range

couldn't reproduce with latest master (last commit sha 31895f412eba60e274c7158a39cf0a8455ffd671)
able to save that timeout for postgre db.


Integrate a Large Language Model when merging pull requests

Feature Description
Merge conflicts can get quite hairy. It would be nice if you could just use an LLM - like Copilot - to automatically resolve them.
Screenshots
No response

How can a LLM do that?

you can often ask chatgpt to "Given these patches as context: ... Please take this file: ... And apply this patch: ..." or so

This sounds like a job for CI.

↑
You do know that these things make mistakes, and cannot adequately tell what the correct code should be, right?
At the moment, the technology is not ready for something like that yet. Wait another 10-15 years before asking again.


Feat: Adding the forgot password page

Describe the feature
forgot password page not propely configured
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@Kalivarapubindusree please assign me this issue to me!

@Its-Aman-Yadav @Kalivarapubindusree please assign me this issue to me!


You are being redirected...JavaScript is required.

Before creating an issue, first upgrade cfscrape with pip install -U cfscrape and see if you're still experiencing the problem. Please also confirm your Node version (node --version or nodejs --version) is version 10 or higher.
Make sure the website you're having issues with is actually using anti-bot protection by Cloudflare and not a competitor like Imperva Incapsula or Sucuri. And if you're using an anonymizing proxy, a VPN, or Tor, Cloudflare often flags those IPs and may block you or present you with a captcha as a result.
Please confirm the following statements and check the boxes before creating an issue:

[✓] I've upgraded cfscrape with pip install -U cfscrape
[✓] I'm using Node version 10 or higher
[✓] The site protection I'm having issues with is from Cloudflare
[✓] I'm not using Tor, a VPN, or an anonymizing proxy

Python version number
Run python --version and paste the output below:
Python 3.7.4

cfscrape version number
Run pip show cfscrape and paste the output below:
Name: cfscrape
Version: 2.0.8
Summary: A simple Python module to bypass Cloudflare's anti-bot page. See https://github.com/Anorov/cloudflare-scrape for more information.
Home-page: https://github.com/Anorov/cloudflare-scrape
Author: Anorov
Author-email<EMAIL_ADDRESS>License: UNKNOWN
Location: c:\users\imfit\appdata\local\programs\python\python37-32\lib\site-packages
Requires: requests
Required-by:

Code snippet involved with the issue
import cfscrape

scraper = cfscrape.create_scraper(delay=10)

response = scraper.get(
    "https://ogusers.com/",
    cookies = {
        "mybbuser": "REMOVED_COOKIE_BECAUSE_PRIVACY"
    }
).content

Complete exception and traceback
(If the problem doesn't involve an exception being raised, leave this blank)

URL of the Cloudflare-protected page
https://ogusers.com/
URL of Pastebin/Gist with HTML source of protected page
https://pastebin.com/raw/290xW9a6
This code was working perfectly for ~5 days and then stopped recently. I'm still able to visit the website via browser without captcha or anything.

After further research, this is not related to Cloudflare or cfscrape. The website I listed is now using Sucuri. I found a fix by using Chrome Dev Tools to find the required cookie and added it to my GET request. I used Python's request library for this as cfscrape is no longer needed.


Does this add a custom tooltip and if yes, how do I disable it?

I actually made a custom tooltip style for myself, but I think this package adds its own tooltip style too. How do I disable it?

Yes. https://github.com/lepoco/wpfui/blob/main/WPFUI/Styles/Controls/ToolTip.xaml

Apparently merging the package's dictionary in the app.xaml does change the tooltip style. How do I disable it? I have my own tooltip style.

Hey @Zopenzop, the question is rather about how to style the controls, which you can find in the WPF documentation. Tooltip in WPF UI overrides the default style. You can either create your own style and modify the imports to make your custom /Styles/WPFUI.xaml alternative. Or you can add a Key to your custom Tooltip style that you will use later.
https://docs.microsoft.com/en-us/dotnet/desktop/wpf/controls/how-to-create-apply-style?view=netdesktop-6.0#relationship-of-the-targettype-property-and-the-xkey-attribute
https://docs.microsoft.com/en-us/dotnet/desktop/wpf/controls/tooltip-styles-and-templates?view=netframeworkdesktop-4.8


Improvement for k8s.io/docs/tasks/manage-hugepages/scheduling-hugepages/

i would like to see how and where these hugepages are apllocated..     i set 1 pod to use 1GB  and i see 2GB is used  im thinking it is one of longhorn pods,  however i am unable to check an verify which one

/language en
/sig docs

Page related to the issue: https://kubernetes.io/docs/tasks/manage-hugepages/scheduling-hugepages/

You can use kubectl get pods -A and look for the pod with hugepages resource.

And for the longhorn, you can check with kubectl get pods -A -l app = longhorn

You can use kubectl get pods -A and look for the pod with hugepages resource.

lol I use that every day  ,   you should test ya commands before replying


[db-bootstrapper] use read-only for waypoint generation

Motivation
(Write your motivation for proposed changes here.)
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
(Share your test plan here. If you changed code, please provide us with clear instructions for verifying that your changes work.)
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/libra/website, and link to your PR here.)

/land


Accuracy on Kinetics Validation Set

Hello,
I test the Kinetics-400 pretrained model (models/rgb_imagenet.pt) on  Kinetics-400 validation set, only use rgb as input. The accuracy is top1-51.3%, top5-74.36%, which is not as good as reported in (Kinetics pretrained model test on Kinetics-400 test set with only rgb as input 68.4 / 88.0)
https://github.com/deepmind/kinetics-i3d
I wonder what might cause such gap?

There are several possible differences.

You can't directly compare the validation set to the test set. The validation set may be harder or easier than the test set.
You may be preprocessing the videos differently than the authors of I3D did. They did no release preprocessing code, but describe the method. Any differences could result in different performance using the pretrained models.
The results reported in the paper may be from a different model than the publicly released one.
Or many other possible reasons.

I personally have not tested I3D on kinetics. All I can guarantee at this point is that is that input to the deepmind tensorflow version gives the exact same output as this converted pytorch version.

@JieChen91 Most probably they perform multi-crop testing. Do you do the same?


Improved the FreedesktopNotifications widget

Instead of having a separate current notification in noteCurrent, we can just take the current notification to be the first one in noteQueue. This greatly simplifies the code.
Allowed notifications to never timeout by wrapping notificationMaxTimeout in a Maybe.
Set Nothing to be the default.
We can pass the whole sequence to the formatter to do interesting things with it.
Changed the default formatter so that it displays the number of pending notifications.
The displayThread now only handles displaying the notification, in particular the timeout thread is started by notify instead.

@drdo @u11gh can you guys fix the merge conflicts?

Looks like the conflicts can be solved easily.

Conflicts fixed.


proposal: spec: extend contracts to include member variables

Contracts proposal includes only member functions.
contract stringer(T) {
	T String() string
}

this means "type T shall have a method named String that returns string". A natural extension could be like:
contract sortable(S) {
	S Key int
}

sortable contract means "type S shall have a member named Key that is int". A better extension could be:
contract ordered(T) {
	T int, int8, int16, int32, int64, uint, uint8, uint16,
		uint32, uint64, uintptr, float32, float64, string
}

contract sortable2(S, T) {
	ordered(T)
	S Key T
}

sortable2 contract means "type S shall have a member named Key that is ordered". This contract could be used like:
func Sort(type S sortable2) (x []S) {
	...
	if x[i].Key < x[j].Key {
		...
	}
	...
}

Also I think this syntax is better for methods and members:
contract stringer(T) {
	T.String() string
}

contract sortable(S) {
	S.Key int
}

A further extension could be like:
type Person struct {
	Name string
	Age int
}

Say, I would like to sort a []Person w.r.t Age somewhere in my app, and w.r.t. Name at some other place in my app. I dont even want to dictate a member name "Key" to the user of my Sort() function. So I want to:
contract orderedMember(S, M) {
	ordered(S.M)
}
// or
contract orderedMember(S, M, T) {
	ordered(T)
	S.M T
}

this contract means "type S has a member M that is ordered". So that could be used like:
func Sort(type S orderedMember) (x []S){
...
	if x[i].M < x[j].M { // use M in code
...
}

var x []Person
...
Sort(M=Age) (x)
Sort(M=Name) (x)

There are many ways we could extend the design draft.  Let's start by seeing whether it works at all.

we didn't end up with contracts.


Why client repeat call ajax to server ?

Hello guys,
I just started meteor, and I use this boilerplate to study.
My problem: it looks like client (browser) auto use websocket and ajax call to server (localhost) repeatly.
Is it default of meteor or boilerplate?
Can I turn off them?
thank you,
Best Regards

This is part of Meteor and isn't a probem specific to this boilerplate.

So what was the suggestion to turn this off ?

I'm not sure but I probably think it has to do with the pub/sub system of Meteor.


Replace calls to SharedPreferences.commit() with .apply()

apply() is faster (commits changes asynchronously), and available
from API level 9. Replacing commit() with apply() is safe in all
cases where the return value from commit() was already being ignored.
Ref: https://developer.android.com/reference/android/content/SharedPreferences.Editor#apply()

This suppresses the ApplySharedPref lint warning (http://tools.android.com/tips/lint-checks)

Thanks!


Why does the multi-scale test have no effect?

The configuration file is as follows：
base =[
'../base/models/faster_rcnn_r50_fpn.py',
'../base/datasets/x.py',
'../base/schedules/schedule_1x.py', '../base/default_runtime.py'
]
model = dict(
pretrained='open-mmlab://resnext101_32x4d',
backbone=dict(
type='ResNeXt',
depth=101,
groups=32,
base_width=4,
num_stages=4,
out_indices=(0, 1, 2, 3),
frozen_stages=1,
norm_cfg=dict(type='BN', requires_grad=True),
style='pytorch',
dcn=dict(type='DCN', deformable_groups=1, fallback_on_stride=False),
stage_with_dcn=(False, True, True, True)))
img_norm_cfg = dict(
mean=[123.675, 116.28, 103.53], std=[58.395, 57.12, 57.375], to_rgb=True)
test_pipeline = [
dict(type='LoadImageFromFile'),
dict(
type='MultiScaleFlipAug',
img_scale=[(1333, 640), (1333, 672), (1333, 704), (1333, 736),
(1333, 768), (1333, 800)],
flip=True,
transforms=[
dict(type='Resize', keep_ratio=True),
dict(type='RandomFlip'),
dict(type='Normalize', **img_norm_cfg),
dict(type='Pad', size_divisor=32),
dict(type='ImageToTensor', keys=['img']),
dict(type='Collect', keys=['img']),
])
]
data = dict(
test=dict(pipeline=test_pipeline)
)
optimizer = dict(type='SGD', lr=0.02, momentum=0.9, weight_decay=0.0001)
optimizer_config = dict(grad_clip=None)
learning policy
lr_config = dict(
policy='step',
warmup='linear',
warmup_iters=500,
warmup_ratio=0.001,
step=[14, 24, 30])
total_epochs = 36
data = dict(
samples_per_gpu=2
)
Is there anything wrong?

What do you mean by saying Why does the multi-scale test have no effect? Is performance not as high as what you expected or what? Please be more specific, e.g., what is the baseline, what do you expect.

what advices do you provide when choose the img_scale in test cfg? appreciate for your reply! @ZwwWayne

@ZwwWayne
I have found the problem, because I repeatedly defined data in the configuration file. In addition, I would like to ask if the results obtained by multi-scale training and testing are not good, is it the problem of my scale selection? Are there any recommended Settings？

faster rcnn  coco datasets @ZwwWayne

@ZwwWayne
I have found the problem, because I repeatedly defined data in the configuration file. In addition, I would like to ask if the results obtained by multi-scale training and testing are not good, is it the problem of my scale selection? Are there any recommended Settings？

I have the same problem. The results of applying the sigle scale (1333,800) is as same the multi-scale [(1400,800),(1400,600),(1400,400)] setting on coco. Would you please tell me the change of the performance when you remove the repeatedly definition of the data set?

The setting is hyper-parameter need to be tuned for different models on different datasets. Usually, it depends on how the model is trained. For example, if the model is trained by multi-scale images, the testing scale could vary in a greater range. This also depends on the dataset and the model itself.


Sprint planning content v1

First iteration for the description of the sprint planning.
Fixes #56

Fixed the markdown issues :)

Forgot to submit my review comments that I made a few days ago. Unfortunately, I'm out for the next 2 weeks, hence I just submitted them as comments (neither waiting for author nor approving). Treat them as nice to have or food for thoughts.

Made some updates, still have some 2 conversations opened.
Let me know what you think is right.


nucleo_wb55rg: Partition update required to use 0.13.0 BLE firmware

Describe the bug
Following recent update of hal_stm32 module with recent STM32Cube package done in https://github.com/zephyrproject-rtos/zephyr/pull/41612, STM23WB based targets are compatible with V1.13.0 Cube package, which includes BLE firmware update.
Though, when updating target BLE core with V1.13.0 BLE firmware (specially the default one: stm32wb5x_BLE_Stack_full_fw.bin);
This is due to f/w footprint increase which is now incompatible with parttion defined in nucleo_wb55rg
To Reproduce
Steps to reproduce the behavior:

Update C0 core on nucleo_wb55rg with stm32wb5x_BLE_Stack_full_fw.bin v0.13.0
west build -p -b nucleo_wb55rg samples/bluetooth/peripheral
See error (Zephyr Fatal error)

Expected behavior
From Zephyr V3.0.0, STM32WB based targets should be compatible with v0.13.0 BLE f/w files
Impact
Prevent use of latest BLE f/w
Environment (please complete the following information):
Zephyr V3.0.0

Following partition will fix the issue on nucleo_wb55rg
		boot_partition: partition@0 {
			label = "mcuboot";
			reg = <0x00000000 0xc000>;
		};
		slot0_partition: partition@c000 {
			label = "image-0";
			reg = <0x0000C000 0x5a000>;
		};
		slot1_partition: partition@66000 {
			label = "image-1";
			reg = <0x00066000 0x5a000>;
		};
		scratch_partition: partition@c0000 {
			label = "image-scratch";
			reg = <0x000c0000 0x4000>;
		};
		storage_partition: partition@c4000 {
			label = "storage";
			reg = <0x000c4000 0x2000>;
		};


Fix path to kserve.yaml in quick_install.sh script

What this PR does / why we need it:
The current quick install script is broken. It will install Istio, KNative, and Cert Manager, but the KServe install itself will fix.
The script is attempting to install KServe from a local filesystem location (install/${KSERVE_VERSION}/${KSERVE_CONFIG}). This path does not exist. It appears to want to refer to the release GH release file (https://github.com/kserve/kserve/releases/download/${KSERVE_VERSION}/${KSERVE_CONFIG}).
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
I could not find an existing issue.
Special notes for your reviewer:
To validate/reproduce:

Create a new  / empty Kind / Minikube install (on MacOS 4GB / 4CPU seems to do the trick).
cd into an empty directory.
(To reproduce) Run the quick install instructions: https://kserve.github.io/website/get_started/#install-the-kserve-quickstart-environment
(To validate) Run the patched script in the PR.

ALSO - the existing quick start needs to be patched to get new users up and running once the fix is confirmed.
Release note:

NONE

@iamahern Did you install from the KServe root directory?

@yuzisun - No. I followed the instructions on the KServe website here:
https://kserve.github.io/website/get_started/
Based on the instructions, I should not need to download/run from the root of the code repo.

@yuzisun - No. I followed the instructions on the KServe website here: https://kserve.github.io/website/get_started/
Based on the instructions, I should not need to download/run from the root of the code repo.

Ah make sense! Thanks for the fix!

/lgtm
/approve

/ok-to-test


Add instructions for building with ROCM.

@rsanthanam-amd

LGTM.  Adding @jayfurmanek for further commentary.

One question I have is: when is it necessary to use the AMD fork of TF? I'm toying with the idea of setting up a ROCM CI build (build only, we don't have the GPU hardware) and it would be very helpful if we could just use upstream TF.

Currently, JAX will not build with upstream TF so the AMD fork must be used.
I need to discuss a plan with my team to enable ROCm JAX to build with upstream TF.

Currently, JAX will not build with upstream TF so the AMD fork must be used.

The fix is likely fairly simple. Getting it merged in TF is another story. We'd love to work mostly upstream but we have some difficulties getting getting approvals and merges unfortunately for various reason. For example the PR for ROCM5.2 support has been bouncing around since early July:
https://github.com/tensorflow/tensorflow/pull/56762]
That one will be needed if we want the CI to build on ROCM 5.2 or later.

I created an issue to track JAX ROCm CI development


Add DG section on task addition optional start date/time

Pull Request Test Coverage Report for Build 281

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 65.165%

Totals

Change from base Build 270:
0.0%

Covered Lines:
1635

Relevant Lines:
2509

💛  - Coveralls


PHP 8.0 PDO::rollback() now throws PDOException after implicit commit

Laravel Version: 8.x
PHP Version: 8.0RC5
Database Driver & Version: MariaDB

Description:
As this is a difficult subject I will try my best to explain it properly, it is an issue that needs to be addressed properly.
PHP 8.0 changes
In PHP 8.0, the pdo transaction logic was rewritten to some extend.
When issuing a PDO::rollback(), this will now throw a PDOException if the transaction was already closed.
* I was not able to find any official documentation on this yet, but was able to confirm this with the different PHP versions
Background Implicit Commits with Transactions
MySQL has a thing called implicit commits, to demonstrate what this does I have created the following example. I have used MariaDB as this has access to the in_transaction session var to demonstrate the working.

create table Table1
(
    name varchar(10) null
);

START TRANSACTION;

SHOW VARIABLES WHERE Variable_name = 'in_transaction' # Returns 1

INSERT INTO Table1 (name) values ('before');

SHOW VARIABLES WHERE Variable_name = 'in_transaction' # Returns 1

create table Table2
(
    name varchar(10) null
);

SHOW VARIABLES WHERE Variable_name = 'in_transaction' # Returns 0

INSERT INTO Table1 (name) values ('after');

SHOW VARIABLES WHERE Variable_name = 'in_transaction' # Returns 0
ROLLBACK ;

# Table 1 now contains both rows.

So imagine a UnitTest executing any Implicit commit commands, then it commits the transaction. So when running Migration command in a test, or stored procedures, or seeders that have implicit commands in them, a rollback is no longer possible as the transaction was already closed.
In php <=7.4.12 no exception was thrown, so most of the times, you would have no idea why you have data leakage in your test
PHP 8.0 now throwns an exception.
Laravel
How does this affect Laravel?

Many applications use DatabaseTransactions or RefreshDatabase traits, which no longer work when implicit commits have been issued in a test.
When a rollback is happening with DB::transaction, a new PDOException is thrown.

Consider the following test file:
use Illuminate\Foundation\Testing\DatabaseTransactions;
use Illuminate\Support\Facades\DB;
use Tests\TestCase;

class MyTest extends TestCase
{
    use DatabaseTransactions;

    public function testMe()
    {
        DB::unprepared('CREATE TABLE a (col varchar(1) null)');
    }
}

This will generate the following error when running the test:
There was 1 error:

1) Tests\Unit\MyTest::testMe
PDOException: There is no active transaction

/app/vendor/laravel/framework/src/Illuminate/Database/Concerns/ManagesTransactions.php:258
/app/vendor/laravel/framework/src/Illuminate/Database/Concerns/ManagesTransactions.php:237
/app/vendor/laravel/framework/src/Illuminate/Foundation/Testing/DatabaseTransactions.php:31
/app/vendor/laravel/framework/src/Illuminate/Foundation/Testing/TestCase.php:237
/app/vendor/laravel/framework/src/Illuminate/Foundation/Testing/TestCase.php:153

Dump of the exception object:
PDOException {#4783
  #message: "There is no active transaction"
  #code: 0
  #file: "./vendor/laravel/framework/src/Illuminate/Database/Concerns/ManagesTransactions.php"
  #line: 258
  +errorInfo: null
  trace: {
    ./vendor/laravel/framework/src/Illuminate/Database/Concerns/ManagesTransactions.php:258 { …}
    ./vendor/laravel/framework/src/Illuminate/Database/Concerns/ManagesTransactions.php:237 { …}
    ./vendor/laravel/framework/src/Illuminate/Foundation/Testing/DatabaseTransactions.php:31 { …}
    ./vendor/laravel/framework/src/Illuminate/Foundation/Testing/TestCase.php:237 { …}
    ./vendor/laravel/framework/src/Illuminate/Foundation/Testing/TestCase.php:153 { …}
    ./vendor/phpunit/phpunit/src/Framework/TestCase.php:1188 { …}
    ./vendor/phpunit/phpunit/src/Framework/TestResult.php:730 { …}
    ./vendor/phpunit/phpunit/src/Framework/TestCase.php:883 { …}
    ./vendor/phpunit/phpunit/src/Framework/TestSuite.php:669 { …}
    ./vendor/phpunit/phpunit/src/Framework/TestSuite.php:669 { …}
    ./vendor/phpunit/phpunit/src/Framework/TestSuite.php:669 { …}
    ./vendor/phpunit/phpunit/src/TextUI/TestRunner.php:667 { …}
    ./vendor/phpunit/phpunit/src/TextUI/Command.php:148 { …}
    ./vendor/phpunit/phpunit/src/TextUI/Command.php:101 { …}
    ./vendor/phpunit/phpunit/phpunit:61 { …}
  }
}

Laravel code
Laravel calls the PHP's rollback command as follows:
https://github.com/laravel/framework/blob/6ecfdb53f6aff9d94ee980fff21f43716cc56c5f/src/Illuminate/Database/Concerns/ManagesTransactions.php#L236-L240
https://github.com/laravel/framework/blob/6ecfdb53f6aff9d94ee980fff21f43716cc56c5f/src/Illuminate/Database/Concerns/ManagesTransactions.php#L274-L281
What has changed?
This exception was not thrown on PHP7.4.12, it is thrown on PHP 8.0RC5
I encountered this issue myself when trying to run my application on 8.0RC5, I can imagine a lot of others will encounter this exception.
Next steps?
Now the question arises what to do with the new Exception that is thrown? As it is currently quite vague as to why it is happening by just looking at the error message, and it cost me a lot of research to find out the cause of it.
I think we need to do at least the following:

Warn users that their test contains implicit commits leading to leaked data during test runs which greatly reduces their isolation.
Still have a way to "ignore" the exception to make sure there will be a smooth transition when moving to 8.0.
Think carefully about the effect of this new exception, how will this affect DB::transaction() when a rollback is initiated?

Please let me know if I can help you out in any way with this issue.
Steps to reproduce
Run the following on PHP 8:
use Illuminate\Foundation\Testing\DatabaseTransactions;
use Illuminate\Support\Facades\DB;
use Tests\TestCase;

class MyTest extends TestCase
{
    use DatabaseTransactions;

    public function testMe()
    {
        DB::unprepared('CREATE TABLE a (col varchar(1) null)');
    }
}

I'm investigating this.

So, I've investigated this with the team and want to reply to some of your proposals:

Warn users that their test contains implicit commits leading to leaked data during test runs which greatly reduces their isolation.

We'd need to list every possible implicit commit trigger for MySQL/MariaDB. This is unfeasible and a lot of work. It's probably also quirky since we'd not be relying on the behavior of the engine directly.

Still have a way to "ignore" the exception to make sure there will be a smooth transition when moving to 8.0.

Your code was already broken on PHP <8.0. It's just more explicit right now. I think the exception being exposed right now is a good thing.

Think carefully about the effect of this new exception, how will this affect DB::transaction() when a rollback is initiated?

The effect of the exception is correct. It throws a fatal error because you're ending a transaction prematurely with an implicit commit.
I think atm I'm more leaning towards doing nothing since it's good that PHP 8 is finally exposing this explicitly. We can't catch the exception and modify it because we don't know what caused the transaction to be closed. It could be the unprepared statement from above or something else. We'd have no way of knowing.
If we'd really want to solve this codewise then listing implicit statements and checking those when a transaction is active and then throw an exception is the best way to go but that would be a lot of work and get cumbrsome.
The best course of action here, I believe, would be to just document the use of DB::unprepared better with an explicit note about transactions and a link to the MySQL page you shared.
I'll let @taylorotwell decide on this.

Thanks for looking into this @driesvints, I completely agree, it is actually good it is throwing an explicit exception since the code was already broken.

The best course of action here, I believe, would be to just document the use of DB::unprepared better with an explicit note about transactions and a link to the MySQL page you shared.

I used unprepared as it's good for PoC's in issue descriptions because it goes straight to the DB, however, it can also be a migration command or some other thing that triggers an implicit command.
Personally, I am fine with your proposal, I agree this should be properly documented on all transaction-related documentation, for example:

DatabaseTransactions and RefreshDatabase trait
DB::transaction, DB::beginTransaction DB::rollback etc.

If we'd really want to solve this codewise then listing implicit statements and checking those when a transaction is active and then throw an exception is the best way to go but that would be a lot of work and get cumbrsome.

Yes, it will be almost impossible to do this, as you will never be able to 100% cover all cases(ie stored procedures)
Note
The effect of the above is that packages that use migrations inside a transaction ie orchestral/testbench/RefreshDatabaseTest.php and laravel-excel/FromQueryTest.php can no longer do this. This has to be handled outside of the transaction now, correct?

It shouldn't affect RefreshDatabase since migration occured before calling $this->beginDatabaseTransaction();

It shouldn't affect RefreshDatabase since migration occured before calling $this->beginDatabaseTransaction();

Oops, you are correct. It only affects the DatabaseTransactions trait then.

Yes, this only affects the DatabaseTransactions trait indeed.
Thanks for your help here @stemis. I'll try to end in a PR to the docs shortly.

Here it is: https://github.com/laravel/docs/pull/6599

@driesvints so the only solution to this is to close the transaction before any implicit commit query ?
like :
// commit previous transaction
\DB::commit();
// run autocommit query
Model::truncate();
// open a new transaction
\DB::beginTransaction();

Sorry for resurrecting this, but this can not be avoided if users will have a way to run statements on a separate PDO session/connection?
DB::isolatedConnection('mysql')->statement('CREATE TABLE ....')

// or

DB::freshConnection('mysql')->statement('CREATE TABLE ...')

I am thinking that running the above statement on a separate PDO connection it will not interfere with transactions started on default/resolved connection.
Even the migrate command might use this. As in, to run migrations always on a separate connection because it executes statements which trigger implicit commit
But i am not sure if this is possible in the framework