text:
Code Review #1518

Related issue(s)

Checklist

[ ] I have read the contributing guidelines.
[ ] I am following the
contributing code guidelines.
[ ] I have read the security policy.
[ ] I confirm that this pull request does not address a security
vulnerability. If this pull request addresses a security. vulnerability, I
confirm that I got green light (please contact
security@ory.sh) from the maintainers to push
the changes.
[ ] I have added tests that prove my fix is effective or that my feature
works.
[ ] I have added or changed the documentation.

Further Comments

I did a rebase and not merge, which is why you get conflicts

Changed it to a merge commit, so now it's mergable

Thanks @aeneasr I will take a loot at this shortly.

authors: aeneasr harnash

repo: Wikia/kratos


text:
China output fails at d3.makefile topography

When running :
make -f master.makefile ISO2=CN SOV3=CH1 NAME=China WEST=70.58 SOUTH=16.44 EAST=137.83 NORTH=55.33

I eventually get :
WIDTH=1280 node topographic.node.js		# see inside this file for parameters' calls
Topo map, projected: Tue May 02 2017 01:19:14 GMT+0200 (CEST)
[Mon, 01 May 2017 23:19:14 GMT] "GET /output/China/administrative.topo.json" "node-XMLHttpRequest"
[Mon, 01 May 2017 23:19:14 GMT] "GET /output/China/color.jpg.b64" "node-XMLHttpRequest"
[Mon, 01 May 2017 23:19:14 GMT] "GET /output/China/trans.png.b64" "node-XMLHttpRequest"
[Mon, 01 May 2017 23:19:14 GMT] "GET /output/China/waters.topo.json" "node-XMLHttpRequest"
[Mon, 01 May 2017 23:19:14 GMT] "GET /output/China/elevations.topo.json" "node-XMLHttpRequest"

file:///home/cri-ninja/yug/make-modules/js/d3.v3.min.js:3
else for(;(u=n+r*++a)<t;)i.push(u/o);return i},vo.map=function(n){var t=new u;if(n instanceof u)n.forEach(function(n,e){t.set(n,e)});else for(var e in n)t.set(e,n[e]);return t},r(u,{has:function(n){return To+n in this},get:function(n){return this[To+n]},set:function(n,t){return this[To+n]=t},remove:function(n){return n=To+n,n in this&&delete this[n]},keys:function(){var n=[];return this.forEach(function(t){n.push(t)}),n},values:function(){var n=[];return this.forEach(function(t,e){n.push(e)}),n},entries:function(){var n=[];return this.forEach(function(t,e){n.push({key:t,value:e})}),n},forEach:function(n){for(var t in this)t.charCodeAt(0)===zo&&n.call(this,t.substring(1),this[t])}});var To="\0",zo=To.charCodeAt(0);vo.nest=function(){function n(t,a,c){if(c>=o.length)return r?r.call(i,a):e?a.sort(e):a;for(var l,s,f,h,g=-1,p=a.length,d=o[c++],v=new u;++g<p;)(h=v.get(l=d(s=a[g])))?h.push(s):v.set(l,[s]);return t?(s=t(),f=function(e,r){s.set(e,n(t,r,c))}):
TypeError: Cannot read property 'length' of undefined
    at e (file:///home/cri-ninja/yug/make-modules/js/d3.v3.min.js:3:5691)
    at Array.Oo.data (file:///home/cri-ninja/yug/make-modules/js/d3.v3.min.js:3:6504)
    at drawElevations (file:///home/cri-ninja/yug/make-modules/js/wikiatlas.js:583:4)
    at drawElevations (file:///home/cri-ninja/yug/make-modules/js/wikiatlas.js:597:4)
    at makeMap (file:///home/cri-ninja/yug/make-modules/js/wikiatlas.js:797:3)
    at o (file:///home/cri-ninja/yug/make-modules/js/queue.min.js:1:271)
    at file:///home/cri-ninja/yug/make-modules/js/queue.min.js:1:227
    at Object.<anonymous> (file:///home/cri-ninja/yug/make-modules/js/d3.v3.min.js:1:9443)
    at Object.t (file:///home/cri-ninja/yug/make-modules/js/d3.v3.min.js:1:617)
    at u (file:///home/cri-ninja/yug/make-modules/js/d3.v3.min.js:1:8305)
d3.makefile:17: recipe for target 'topographic' failed
make[1]: *** [topographic] Error 1
make[1]: Leaving directory '/home/cri-ninja/yug/make-modules/09_d3'
master.makefile:43: recipe for target 'd3' failed
make: *** [d3] Error 2

Key part seems :
    at drawElevations (file:///home/cri-ninja/yug/make-modules/js/wikiatlas.js:583:4)
    at drawElevations (file:///home/cri-ninja/yug/make-modules/js/wikiatlas.js:597:4)
    at makeMap (file:///home/cri-ninja/yug/make-modules/js/wikiatlas.js:797:3)

2020 sprint.
China tested.
No bug.

source: gharchive/issue

repo: WikimapsAtlas/WikimapsAtlas-generator

license: mit

license_type: permissive

license_source: bigquery


text:
get correct link for PreviewItem and some cleanup of VIEW_BOARDING_PAGE

Related Issue

Fixes #353
Checklist:

[x] I have read the contributor's guide.
[x] I linked an issue in the previous section
[x] I have commented on the linked issue
[x] I was assigned the linked issue (not required)
[x] I have tested the change to the best of my ability against the sandbox or a local build.

Optional items:

[ ] My change adds new text and requires a change to translations.
[ ] My change requires a change to the documentation.
[ ] I have submitted a PR to the documentation repo.
[ ] I was not able to test... (explain below, e.g. you did not have permissions to test a specific feature)
[ ] This change depends O-FISH Realm repository changes (explain below)

Optional: Add any explanations here

removed the incorrect link with null filters in PreviewItem
used get*ViewPage methods from get-data to get link for Vessels, Crews, and Boardings
make sure that PreviewItem is not rendered when item not there yet
added a reusable method getBoardingViewPage to get-data

Additional:

cleanup all usage of VIEW_BOARDING_PAGE into reusable goBoardingViewPage

Optional: Add any relevant screenshots here

Congratulations! 🎉 🙌 🎆 ㊗
This PR is great and has been merged into the code. Thanks so much for contributing! If you'd like, you can request to work on another issue. We really appreciate your effort!
To claim your O-FISH badge, head on over to the MongoDB Community forums, login, and reply - making sure to link to this PR.

source: gharchive/pull-request

authors: Sheeri lenmorld

repo: WildAid/o-fish-web

license_source: github-api


text:
Feedback JWT isAdmin

Bonjour,
Il y a une erreur d'orthographe dans le fichier authController à la ligne 27 :
{ sub: user.id, isAdmin: user.isAdmin } doit être écrit { sub: user.id, isAdmin: user.is_admin } pour que l'ajout d'item fonctionne avec la ligne 44 de l'itemController :   if (!req.auth.isAdmin)
Merci !

Merci @ghispell :)

authors: ghispell rocambille

repo: WildCodeSchool/workshop-js-auth

license: MIT


text:
Add releases

It would be nice to enable users who don't have / don't want a Rust development environment to download a precompiled binary.

Having pre-built binaries would be super-useful, +1

@oguzbilgic homebrew is coming, see #201.

The getting started page in the manual: https://difftastic.wilfred.me.uk/getting_started.html now has a list of packages available for difftastic. Many of these (e.g. Arch Linux) are prebuilt binaries.
Prebuilt binaries is probably nice to have too. We could copy what ripgrep does: https://github.com/BurntSushi/ripgrep/blob/master/.github/workflows/release.yml -- PRs welcome here.

Yup.  Or a least give the right instructions on how to compile it.

cargo install difftastic doesn't work for you?

It dosn't work for me:
error: unexpected token: `include_str`
   --> /home/heilig/.cargo/registry/src/github.com-1ecc6299db9ec823/textwrap-0.15.0/src/lib.rs:200:9
    |
200 | #[doc = include_str!("../README.md")]
    |         ^^^^^^^^^^^

error: aborting due to previous error

error: could not compile `textwrap`.

any suggestions?

Meanwhile, if anyone is ok with running mystery binaries from the interwebz, here is difft (Difftastic 0.25.0) binary built for Ubuntu 18.04:
https://transfer.sh/U4KHW5/difft
Here is the sha256 hash so others can verify its integrity:
fac334aecc614237e39333ef5cd00343340a91813dd6273d4eda0225f4280ea8  difft

Yup.  Or a least give the right instructions on how to compile it.

cargo install difftastic doesn't work for you?

I tried on Windows without success.

OK, GitHub releases are now available.

@schorsch3000 it looks like your Rust version is older than the minimum required for difftastic (1.56).

@Wilfred Don't forget to enable releases on the project sidebar. Enabled by a cog icon next to 'About'. Great job!

authors: Wilfred atipugin littleli mdesantis pvonmoradi schorsch3000

repo: Wilfred/difftastic


text:
Create your own Enumerable

In this project, I did the following:

Created a class MyList that has an instance variable @list.
Implemented a method #each that yields successive members of @list and uses the MyEnumerable module.
Created a module MyEnumerable that implements all, any, and filter methods.
Added a test file to verify solutions on the implemented functionalities.

Please find attached proof of permission from student success for me to do my projects solo. Thanks

@brytebee, thank you very much, sir.


text:
Other Projects

You are free to add the sparkEd, both the main app, mobile and the mobile version(still in progress)
all their links can found here
Good stuff bro

another one is this https://github.com/OlivierJM/meteor-jest-boilerplate

Another project I found today is https://startup.oneziko.com/?fbclid=IwAR28pmqhBI2a5HnYeGL3Q1KkVnHWuXyu2VCWJ2DXj3sxVRsOGQNxa_yvoa8
by Chinyanta Mwenya . will add it

Cool

another one is this https://github.com/OlivierJM/meteor-jest-boilerplate

I have added it. please review that the information is correct

The manual is actually hosted online here

I have added it. please review that the information is correct

Hey @WillzMu! Thanks for considering the Zambian Startups project, though it's still coming soon. On the url, you can remove "/? fbclid...", that must be from Facebook, the sub-domain must be enough. Will update on progress.

The SparkEd-Mobile was duplicated

@WillzMu  can you also include this project on that list?

fbclid

Hey @WillzMu! Thanks for considering the Zambian Startups project, though it's still coming soon. On the url, you can remove "/? fbclid...", that must be from Facebook, the sub-domain must be enough. Will update on progress.

Thanks @Chizzoz . Will need a couple details to add it to the list like description of the project and tools being used.

The SparkEd-Mobile was duplicated

Thanks for noticing that. I have corrected it. Let me know which other projects that can be added with a link.

Cool, I will let you know but also include the "projectZed" there

check out the repos of this guy here https://github.com/DavidTheProgrammer

thanks. Will do so

@WillzMu so I realised Zambian Startups would not really qualify as an open source project, since its more of a service and contribution is more on the content side.
I am and have been working on something else that is more of an open source project, useful to other developers and also open to contribution, modification and improvement. Might take a while, but will share once there's something tangible.

No problem @Chizzoz. I think 'Project Zed' Can highlight all projects done by Zambians not just those that are open source. I have added the open source project you recently added, e-Mpiya OMPS.

Hey @WillzMu! Just checked it out... Thanks!

authors: Chizzoz OlivierJM WillzMu

repo: WillzMu/projectZed


text:
[Bug/Glitch] Chat bug issue on 1.20.4

Legacy4J Version
1.20.4-1.7.2
Mod Loader Version
Fabric Loader 0.15.11
Bug/Glitch Occurrence Context

Crash Report
No response
What happened wrong?
The positioning is wrong and incorrect, thus causing this issue

Issue is 1.20.4 specific, so 1.20.1, 1.20.6 and 1.21 aren't affected

Fixed in version 1.7.3, thanks for reporting.

repo: Wilyicaro/Legacy-Minecraft


text:
How do you upgrade an existing project to 1.1.1?

I uninstalled and then reinstalled Template10 in Visual Studio yesterday before creating a project based on Minimal and yet I was left with this version:
nuget\packages\Template10\1.0.8
Is there a way to upgrade that template in place to 1.1.1?
Other than the build output is there a place within the code to see what version of Template10 is being used?
Why wouldn't the install through Visual Studio use 1.1.1 in the first place?
Thanks,
Rick

Hello Rick,
Right click on your project in Visual Studio and choose Manage NuGet packages. Under the Installed tab, you will see the list of installed packages and their version number. Moreover, if you move to the Updates tab, you will see all the packages which have an update, with the option to go on and perform it.

OK great I found that and upgraded.  I really appreciate the help.  I'm left with a few compile errors like:
Severity	Code	Description	Project	File	Line	Suppression State
Error	CS0115	'DetailPageViewModel.OnNavigatedTo(object, NavigationMode, IDictionary<string, object>)': no suitable method found to override	i3RemoteWP_Universal2
I'm assuming these relate to the breaking news issues on 1.1.1 that Jerry posted and require a manual fix up?
Thanks,
Rick

Correct. The new signature of the method is now:
Task OnNavigatedToAsync(object parameter, NavigationMode mode, IDictionary<string, object> state)

I think I have it, does this change look right?  It did fix a compile error:
Change this:
public override void OnNavigatingFrom(NavigatingEventArgs args)
{
args.Cancel = false;
}
to this:
public override Task OnNavigatingFromAsync(NavigatingEventArgs args)
{
args.Cancel = false;
        return Task.CompletedTask;
    }

Just want to make sure I got it right.
Thanks,
Rick

Yes, it's correct. Just remember that the code:
return Task.CompletedTask;
is required only if, like your case, the method doesn't perform any asynchronous operation (so you're not using the async / await keyword). Otherwise, you can omit it.

That cleared up the existing compile errors but left me one last one I don't see instructions for.  The error is:
Error	CS1503	Argument 1: cannot convert from 'Template10.Services.NavigationService.INavigationService' to 'Template10.Services.NavigationService.NavigationService'	i3RemoteWP_Universal2
In this code:
// runs even if restored from state
public override async Task OnInitializeAsync(IActivatedEventArgs args)
{
// setup hamburger shell
var nav = NavigationServiceFactory(BackButton.Attach, ExistingContent.Include);
Window.Current.Content = new Views.Shell(nav);
await Task.Yield();
}
Any idea what the fix is for that?
Rick

See here https://github.com/Windows-XAML/Template10/issues/556
// Shell.xaml.cs
public Shell(INavigationService navigationService)

I'm getting this error
void DetailPageViewModel.OnNavigatedTo(object parameter, NavigationMode mode, IDictionary<string, object> state)
'DetailPageViewModel.OnNavigatedTo(object parameter, NavigationMode mode, IDictionary<string, object> state)': no suitable method found to override
since I update to 1.1.1

I couldn't find that reference easily in #556 but I did find that line and replaced it.   I then compiled again and got 22 compile errors very similar to this one:
Error	CS0433	The type 'Interaction' exists in both 'Microsoft.Xaml.Interactivity, Version=12.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' and 'Microsoft.Xaml.Interactivity, Version=1.0.2.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'	i3RemoteWP_Universal2
This is so hard, its like a scavenger hunt of pain.  I wish there was just a fixed, ready to go version of a template 10 minimal project ready to go to use as a baseline.
Rick

You need to remove the Behaviors SDK reference you find in the references of your project and keep just the Behaviors NuGet package

By the way, a full list of the changes to do when you upgrade your project is listed in the wiki https://github.com/Windows-XAML/Template10/wiki/Upgrading-from-Template-10-Nuget-Nuget-1.0-to-1.1

Thanks Matteo, I ran through all of the changed and think I did them but was left with 1 last error:
Error		Assembly 'Template10Library' with identity 'Template10Library, Version=1.0.5866.5306, Culture=neutral, PublicKeyToken=d74e748b43bf937b' uses 'Microsoft.Xaml.Interactivity, Version=1.0.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' which has a higher version than referenced assembly 'Microsoft.Xaml.Interactivity' with identity 'Microsoft.Xaml.Interactivity, Version=1.0.2.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'	i3RemoteWP_Universal2
I'll comb through the links you sent to make sure I didn't miss anything.  I did remove the reference to the Behaviors SDK.
Rick

It looks like the project has a dependency on 'Microsoft.Xaml.Interactivity, Version=1.0.3.0' but the NuGet package is dependent on 'Microsoft.Xaml.Interactivity, Version=1.0.2.0,

I never added that dependency though, I installed a fresh copy of Template 10 through VS 2015, I think it was 1.0.8, upgraded that in place to 1.1.1 and did the fix ups.   I didn't make any modifications the to project yet, its pretty much as is based on the Minimal template.  I don't see a reference to 'Microsoft.Xaml.Interactivity so its not clear how to fix it to make it depend on .Xaml.Interactivity, Version=1.0.2.0

I got my solution building again by deleting all my bin and obj folders to get rid of any caches.  Then I changed "Microsoft.Xaml.Behaviors.Uwp.Managed" version="1.0.2"  to "Microsoft.Xaml.Behaviors.Uwp.Managed" version="1.0.3" in the Template10.nuspec file in my .nuget folder.  Now it all builds again.
I know its a bit hacky but the 1.1.1 NuGet package is broken, this just makes it less broken.  Any fix is going to mean a new version of the NuGet package, so I don't mind hacking it as a temporary measure.

Actually the 1.1.1 NuGet Package is not broken. I updated to it recently and you just need to follow the upgrade guide here. Here's what's in my project.json.
"dependencies": {
    "Microsoft.NETCore.UniversalWindowsPlatform": "5.0.0",
    "Microsoft.Xaml.Behaviors.Uwp.Managed": "1.0.3",
    "MvvmLight": "5.2.0",
    "Rx-WinRT": "2.3.0-beta2",
    "Rx-XAML": "2.3.0-beta2",
    "Template10": "1.1.1",
    "Newtonsoft.Json": "8.0.2"
  },

@JustinXinLiu that is a better fix - still getting used to the new project.json files. I'm pretty sure those instructions weren't there when I originally went to that page, I never thought to go back, d'oh!.  However, the Nuget package is still wrong; it shouldn't specify a version of a dependency that is not compatible with the contents of the package.

OK its working.   I edited Template10.nuspec (I had to figure out where that was) and changed the behavior dependency to 1.0.3.  I thought it was odd that in that file it showed dependency for Newtonsoft.Jason for 7.0.1 even though I upgrade that to 8:

In my project.json file I don't even show the dependency for Microsoft.Xaml.Behaviors.Uwp.Managed:
"dependencies": {
"Microsoft.ApplicationInsights": "1.0.0",
"Microsoft.ApplicationInsights.PersistenceChannel": "1.0.0",
"Microsoft.ApplicationInsights.WindowsApps": "1.0.0",
"Microsoft.NETCore.UniversalWindowsPlatform": "5.0.0",
"Newtonsoft.Json": "8.0.2",
"Template10": "1.1.1"
},
I am thrilled that my project is finally alive and running for the first time!
Rick

Oh no, after my post I was about to load the Minimal project in Blend and see how it looked but literally after simply compiling fine, exiting the app in Local Machine and then terminating the app, I was left with an invalid markup error on the designer surface and the error in here of MainPageViewModel not existing in the Viewmodels namespace.  I also noticed that I now have 37 compile errors.   I realized I didn't do the 1.1.1 fixup about the bootstrapper code but I can't find where that code exists to modify it.  I think the release notes need to give more guidance as to precisely where all these change nuggets originate from.
Its amazing that I can get a perfect compile, run the app and then upon completion have a completely new set of failures.   Its a linked list of complications.
Rick

Version 1.1.0 of Microsoft.Xaml.Behaviors.Uwp.Managed has been released and it seems to be breaking. I got this error using version 1.1.0

the assembly version has a public key token that does not match that of the request

So, I need to go back to 1.0.3. And now it is working perfectly.

authors: JustinXinLiu Raamakrishnan edsonsouza92 jhalbrecht pjh1974 qmatteoq rickengle


text:
Wishlist Class

As a Developer
I need to store the structural data of wishlist temporally
So that I can pass wishlist data between functions, to or from database
Assumptions:

Allow creations of instances of Wishlist class with wishlist data
Have private attributes name (name of wishlist), customer (customer ID) and products (a list of products ID)
Provide public method in the form of get_{attribute} to allow access of attribute named {attribute} in any instance
Provide public method in the form of update_{attribute} to allow modification of attribute named {attribute} in any instance

Acceptance Criteria:
When I use wishlist data to initialize a wishlist class
Then I should get an instance where all of these data stored
When I call get_{attribute} method
Then I should get the value of attribute named {attribute}
When I call update_{attribute} with a new value
Then the original value of attribute named {attribute} should be replaced by the new value

Very good class design. A public method toJson might also be useful for returning response.

authors: BlackDavy YQCW

repo: Wishlist-Squad/wishlists


text:
Revert "converted normals to unit vectors to fix #108"

This reverts commit dcbe8cd162e9312b7d80ac4e1ff557af576cd996 which caused Mesh.units to no longer be unit-vectors (i.e. have magnitude of 1.0). Fixes #142.
It's not a true revert as you've made further changes since which caused minor merge conflicts. I've hopefully preserved your further changes.

Coverage decreased (-100.0%) to 0.0% when pulling f1fc0b687e52234614a78fbee49fa2a43debdc0f on bwoodsend:develop into 024b3b85184c509d10c60b6a51a938316669f7ba on WoLpH:develop.

authors: bwoodsend coveralls

repo: WoLpH/numpy-stl


text:
trail: Fix incorrect Mesh constructor call

The constructor of Mesh expects the engine as its first argument. The trail component instead passed the MeshParameters as the only argument. Interestingly enough this doesn't cause any issues during construction, but results in errors when invoking methods on the resulting Mesh that try to call into the engine.

Great catch! Thank you so much 🙏

authors: Squareys mrxz

repo: WonderlandEngine/components


text:
🛑 Personnal website is down

In ec3151b, Personnal website (https://woomy.be) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Personnal website is back up in d7a4a89 after 5 minutes.

repo: Woomymy/status


text:
Namespaced cron_schedules callbacks not detected

Bug Description
The WordPress.WP.CronInterval sniff is producing a warning when a namespaced callback is used: "Detected changing of cron_schedules, but could not detect the interval value."
Minimal Code Snippet

namespace Foo {
	function my_add_every_hour( $schedules ) {
		$schedules['every_hour'] = [
			'interval' => HOUR_IN_SECONDS,
			'display' => __( 'Once every hour' )
		];
		return $schedules;
	}
	add_filter( 'cron_schedules', __NAMESPACE__ . '\my_add_every_hour'); // OK: > 10 min.
}

Environment

Question
Answer

PHP version
7.2.23

PHP_CodeSniffer version
3.5.4

WPCS version
2.2.1

WPCS install type
Composer global

Tested Against develop branch?

[x] I have verified the issue still exists in the develop branch of WPCS.

Added a (failing) test in #1866.
I'm happy to work on a patch, though I'd need some hints. So far I noticed that the value of $callback here is
array(3) {
  ["start"]=>
  int(82)
  ["end"]=>
  int(87)
  ["raw"]=>
  string(36) "__NAMESPACE__ . '\my_add_every_hour'"
}

And token_name( $this->tokens[ $callbackArrayPtr ]['code'] ) around here returns T_NS_C.

@ocean90 Thanks for reporting this.
A lot of the WPCS sniffs at this moment are not adapted yet to handle namespaced code correctly in all situations.
Fixing this for this sniff will not be easy as, in most cases, a file based namespace will be used not a scoped (curly braces) namespace.
And with a file based namespace, the function could be:

declared in another file in the same namespace;
could be imported via a use function statement from elsewhere;
could be in another namespace all together.

While your example code is self-contained, this will not be the reality in most cases.
For this to be fixed, the sniff would need to:

Keep track of the current namespace;
Keep track of import use statements;
Check the second parameter for use of __NAMESPACE__, but also for My\NS\function_name and get the correct function name stripped of the namespace, but keep the namespace separately to check it against the tracked current namespace/namespaces in the file.

In most of the cases I listed above, this would eventually still result in the warning.
And yes, it's a warning, not an error because the sniff did not reach a conclusion.
The warning can be whitelisted using a whitelist comment like this:
// phpcs:ignore WordPress.WP.CronInterval -- Verified > 10 min.
So, yes, for your specific code sample, this could be fixed.
Fixing this will be easier though once we move over to using PHPCSUtils in the near future as it contains a lot of utility functions which will be helpful for this.
Let me know if you still want to work on this already or if you are ok with whitelisting the code for now.

Thank you for the detailed feedback! The scoped namespace was just an example and something that can be used in in the test without the need for a new file (I might be wrong). I got the warning in a file based namespace.
For me, this was actually the first time something was triggered due to the use of a namespace so I wasn't aware of other issues. The whitelist comment is totally fine for now.

repo: WordPress/WordPress-Coding-Standards


text:
screen at breakpoint sm with width 640 › filters are updated when media type changes is flaky

Description

See this run for flaky test: https://github.com/WordPress/openverse-frontend/actions/runs/3420250078/jobs/5694859665
Resolution

[ ] 🙋 I would be interested in resolving this bug.

Yes, this issue seems to be fixed. We can re-open it if it starts showing up again

authors: obulat sarayourfriend

repo: WordPress/openverse-frontend


text:
Use a real migrations management tool for upstream_db and thus for production database

Problem

If changes are made to the upstream_db schema as in #2096, you need to fully rebuild the upstream_db image to get them.
This also has an effect on production database management, where we are required to manually run schema change queries on production (see #2096 has a comment noting this requirement).
Neither of these are good. The first because it creates a confusing and difficult to debug local environment issue if schema changes happen (why aren't I getting this column that is obviously in the SQL file to create the schema). The second because it requires us to manually write queries that change the production schema! The first is bad but the second is downright awful and we should not continue this practice.
Description

Use a real schema migration tool like Alembic to describe the catalog database schema and apply migrations over time.
Alternatives
We could write our own SQL migrations and apply them iteratively by hand but... Alembic is going to be a lot better at doing this, why reinvent the wheel?
Additional context
This is marked stack: mgmt but it's really stack: infra, stack: catalog, and stack: api (basically everything) due to the crossover in local and live environment dependencies on the upstream database schema.

@sarayourfriend this may be a duplicate of or related to https://github.com/WordPress/openverse/issues/1836

It is, thank you! I'll suggest higher prioritisation on that one and close this one.

authors: AetherUnbound sarayourfriend

repo: WordPress/openverse


text:
visual-regression/v-header-internal.spec.ts:36:11 › VHeaderInternal › screen at breakpoint xs with width 340 › mobile-header-internal-modal-ltr is flaky

Description

visual-regression/v-header-internal.spec.ts:36:11 › VHeaderInternal › screen at breakpoint xs with width 340 › mobile-header-internal-modal-ltr is flaky.
It fails in this run: https://github.com/WordPress/openverse/actions/runs/7699638405/job/20981848020
And passes in this run: https://github.com/WordPress/openverse/actions/runs/7699638405/job/20983730568

I had this fail again in another PR and remembered to grab the test results artefact.
It looks like the same font rendering issue that @obulat fixed in the other playwright tests. I bet https://github.com/WordPress/openverse/issues/3713 is too?
storybook_test_results.zip

Yes, @sarayourfriend, this does look like a font rendering issue. We should probably add a wait to this test.

How does that work, Olga? Is there an example to go off of?


text:
Run label check on every commit and label change

Description

Follow up to https://github.com/WordPress/openverse-infrastructure/pull/326 which required label checks for all merges into main, this was causing issues where a maintainer had to add & remove labels to re-trigger the check so a PR could be merged.
This action was previously set up to only run when the labels on a PR change. Since we've made this a required check, it makes sense to have this run unconditionally on every PR commit so that the check can pass (or fail) appropriately prior to a merge.
Testing Instructions

We might be able to see on this PR!
Checklist

[x] My pull request has a descriptive title (not a vague title like
Update index.md).
[x] My pull request targets the default branch of the repository (main) or
a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[ ] I tried running the project locally and verified that there are no visible
errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Shoot, now I'm worried that it'll interfere with the "Label new PR" action since those run quick and it might fail if the PR is submitted without labels but gets them from that action 😭 Let me see if we can actually expand the set of events rather than revert to the default set.

Okay, I think I've got a solution! This should now cover all the default PR actions (commits, opening, reopening, etc) as well as when labels are updated. I'm going to let it run after this push, then try to change the labels to make sure the actions get triggered again.

Worked like a charm! 🥳


text:
Enormous graphical memory allocation when drawing surface shapes on Mali GPU

Enormous graphical memory allocation when drawing surface shapes on Mali GPU.
Each frame GPU allocates new memory for resulting texture and it generated 2GB of VRAM during 5 sec.
Issue can be easily reproduced on MGRSGraticuleActivity example where a lot of surface lines are drown on textures.

Similar issue https://community.arm.com/support-forums/f/graphics-gaming-and-vr-forum/5469/glteximage2d-memory-leak

According to long conversation with ARM.com team, the issue with memory allocator is in Mali GPU driver 32-38.
Should be fixed in 44.
We added workaround for render target textures which allocates 1x1 texture before normal allocation.
This workaround disables AFBC compression on driver side for this texture and as the result fixed abnormal memory allocation.
Workaround added in 6317fbf5ee496e9e27b881fffd1fe07e9efbc3e4

repo: WorldWindEarth/WorldWindKotlin


text:
Make background grid vector based

Currently, the background grid is created using a PNG image. When zooming in and out, the image is distorted.
Replace PNG image with a vector based XAML DrawingImage.
Acceptance criteria:

Image is vector based
Zooming in and out does not distort the background image.

I'm closing this issue as your PR has been merged.

authors: Napa-HP Wouterdek

repo: Wouterdek/NodeNetwork


text:
Issue on android API level11 and above

No media Visible on Gallery Screen at Android API level >=10 required below permission to show media on gallery screen
add Pemission

Thank you @Abhishek1511991 for reporting the issue.
It's been a while working on this library, I will revise it soon.

repo: WrathChaos/MediaPickerLib


text:
Prevent lack of DDLC game files being bypassed by pressing "Ignore"

Essentially, attempting to launch the mod without the base game's files results in a Ren'Py error screen. If you click the "Ignore" button, the screen will be bypassed and the mod can be played as normal.
I've just replaced that screen with a more fitting one that doesn't allow for a bypass.

at the moment it just appends the regular disclaimer to that one which is kinda funny actually

Perfecto.

authors: Pseurae initializesahib


text:
RHS MK V SOC (boat) build radius and protected area overlap

Basic Information
Mission version: 0.96 dev
Map used: Tanoa
Mods used: RHS, ACe
Dedicated or local game? Ded
GitHub or Workshop mission file? GitH
Individual Things
Did you edit anything within the mission files?
Yes, nothing related
If yes, what did you edit exactly?
Short Issue Description
When trying to build a MK V SOC boat (RHS), the player trying to build it is standing in the circle, so you can't build it because there is an object in it.
Expected Behaviour
If the circle is 1 meter smaller or the boat 1 meter further away it would let you build it.
Steps to Reproduce the Issue
Try to build RHS Boat MV V SOC

try to add "Land_MkV_Roadway", into presets>init_presets.sqf>line84 and following.


text:
[bug] When a system has ~ 16GB of RAM only 2/4 cores are used to build

🐛 BUG REPORT
My VPS have 15.8GB of memory but only 2/4 cores are used due to the calculations inside the script (integer numbers)
CPU_THREADS=$(nproc)
RAM=$(awk '/MemTotal/ { printf "%d \n", $2/1024/1024 }' /proc/meminfo)
RAM_CPU_RATIO=$((RAM / CPU_THREADS))
RAM_CPU_RATIO_ALL_CPU_THREADS=4

So in my case RAM_CPU_RATIO is 15/4 that is rounded to 3.
Possible solutions:

Do the calculations with some tweaks for doing the calculations with decimals or rounding the RAM to nearest integer
Lowering RAM_CPU_RATIO_ALL_CPU_THREADS to 3. This is an atypical condition usually not met by VPS providers where the RAM_CPU_RATIO is usually 2 or 4 (or 1 in some rare cases). It's rare to see systems with, for example 12GB and 4 cores (usually is 8GB or 16GB). So changing the condition to 3 will cover also the situation where available RAM is not exactly a round number (15.8 instead of 16 available).

@zachhildreth What do you think? Which solution is preferred?

PS. The solution to this will permit to build things faster on systems like mine

Solved rounding the RAM calculation with %1.f  instead of %d
RAM=$(awk '/MemTotal/ { printf "%1.f \n", $2/1024/1024 }' /proc/meminfo)

Added to https://github.com/X-CASH-official/xcash-dpops/pull/41/commits/66fe81022d16b8099d6f796cfbf4a7f6d2f7b203

repo: X-CASH-official/xcash-dpops


text:
meu app nao quer colocar o jogo do sonic adventure

Please check the troubleshooting guide in the Wiki before submitting an issue.
NOTE! This issue tracker is for bug reports for the SA Mod Manager only. This isn't a place to troubleshoot game crashes with your mods. If you need help with mods, please post on the x-hax Discord instead.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Cool story

authors: Sora-yx souzarz

repo: X-Hax/SA-Mod-Manager


text:
[Snyk] Upgrade: react, react-dom

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to upgrade multiple dependencies.
👯 The following dependencies are linked and will therefore be updated together.

: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.

Name
Versions
Released on

reactfrom 18.2.0 to 18.3.1 | 385 versions ahead of your current version | a month agoon 2024-04-26
react-domfrom 18.2.0 to 18.3.1 | 385 versions ahead of your current version | a month agoon 2024-04-26

Release notes

Package name: react

18.3.1 - 2024-04-26
Export act from react f1338f

18.3.0 - 2024-04-25This release is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19.
Read the React 19 Upgrade Guide for more info.
React

Allow writing to this.refs to support string ref codemod 909071
Warn for deprecated findDOMNode outside StrictMode c3b283
Warn for deprecated test-utils methods d4ea75
Warn for deprecated Legacy Context outside StrictMode 415ee0
Warn for deprecated string refs outside StrictMode #25383
Warn for deprecated defaultProps for function components #25699
Warn when spreading key #25697
Warn when using act from test-utils d4ea75

React DOM

Warn for deprecated unmountComponentAtNode 8a015b
Warn for deprecated renderToStaticNodeStream #28874

18.3.0-next-fecc288b7-20221025 - 2022-10-25

18.3.0-next-fccf3a9fb-20230213 - 2023-02-14

18.3.0-next-fabef7a6b-20221215 - 2022-12-16

18.3.0-next-fa4314841-20230502 - 2023-05-03

18.3.0-next-f828bad38-20230313 - 2023-03-13

18.3.0-next-f0efa1164-20220901 - 2022-09-02

18.3.0-next-f0534ae94-20221202 - 2022-12-05

18.3.0-next-efc6a08e9-20220923 - 2022-09-23

18.3.0-next-ee8509801-20230117 - 2023-01-17

18.3.0-next-edbfc6399-20221128 - 2022-11-29

18.3.0-next-ed545ae3d-20230425 - 2023-04-25

18.3.0-next-e98225485-20221129 - 2022-11-30

18.3.0-next-e7c5af45c-20221023 - 2022-10-24

18.3.0-next-e6a062bd2-20220913 - 2022-09-13

18.3.0-next-e61fd91f5-20220630 - 2022-06-30

18.3.0-next-e40893d09-20221005 - 2022-10-06

18.3.0-next-e225fa43a-20220711 - 2022-07-12

18.3.0-next-e1dd0a2f5-20221115 - 2022-11-16

18.3.0-next-de7d1c907-20221223 - 2022-12-26

18.3.0-next-dd5365878-20230407 - 2023-04-07

18.3.0-next-dd2d65227-20220708 - 2022-07-11

18.3.0-next-d962f35ca-20230418 - 2023-04-18

18.3.0-next-d925a8d0b-20221024 - 2022-10-24

18.3.0-next-d807eb52c-20221205 - 2022-12-06

18.3.0-next-d49e0e0be-20230302 - 2023-03-02

18.3.0-next-d1e35c703-20221110 - 2022-11-10

18.3.0-next-d1bb1c586-20220922 - 2022-09-22

18.3.0-next-d1432ba93-20220628 - 2022-06-29

18.3.0-next-cf665c4b7-20220620 - 2022-06-21

18.3.0-next-cf3932be5-20221027 - 2022-10-28

18.3.0-next-cce18e350-20221023 - 2022-10-23

18.3.0-next-cb5084d1c-20220924 - 2022-09-24

18.3.0-next-ca990e9a7-20220804 - 2022-08-05

18.3.0-next-ca2cf319f-20230223 - 2023-02-24

18.3.0-next-c8b778b7f-20220825 - 2022-08-25

18.3.0-next-c89a83695-20220923 - 2022-09-23

18.3.0-next-c8369527e-20230420 - 2023-04-21

18.3.0-next-c80e54116-20220907 - 2022-09-07

18.3.0-next-c739cef2f-20220912 - 2022-09-12

18.3.0-next-c54e3541b-20221111 - 2022-11-14

18.3.0-next-c3b18571d-20220707 - 2022-07-07

18.3.0-next-c28f313e6-20220908 - 2022-09-09

18.3.0-next-c1f5884ff-20220705 - 2022-07-05

18.3.0-next-c1d414d75-20220923 - 2022-09-23

18.3.0-next-c08d8b804-20221118 - 2022-11-21

18.3.0-next-bfb9cbd8c-20230223 - 2023-02-24

18.3.0-next-b72ed698f-20230303 - 2023-03-03

18.3.0-next-b4204ede6-20220803 - 2022-08-04

18.3.0-next-b14f8da15-20230403 - 2023-04-03

18.3.0-next-b14d7fa4b-20221209 - 2022-12-09

18.3.0-next-b0671f9ea-20230130 - 2023-01-30

18.3.0-next-afe664d9d-20220913 - 2022-09-14

18.3.0-next-ae7ad8b4c-20220927 - 2022-09-27

18.3.0-next-abbbdf4ce-20220930 - 2022-09-30

18.3.0-next-aa9988e5e-20221010 - 2022-10-10

18.3.0-next-a8c16a004-20221012 - 2022-10-13

18.3.0-next-a8875eab7-20230310 - 2023-03-10

18.3.0-next-a6bf46689-20221014 - 2022-10-14

18.3.0-next-a4bed4696-20220627 - 2022-06-28

18.3.0-next-a0619e26c-20221207 - 2022-12-07

18.3.0-next-9ff738f53-20220826 - 2022-08-29

18.3.0-next-9fcaf88d5-20220801 - 2022-08-02

18.3.0-next-9fb2469a6-20230308 - 2023-03-08

18.3.0-next-9e67e7a31-20220823 - 2022-08-23

18.3.0-next-9cdf8a99e-20221018 - 2022-10-18

18.3.0-next-9c54b29b4-20230322 - 2023-03-23

18.3.0-next-9a9da7721-20230409 - 2023-04-10

18.3.0-next-996e4c0d5-20221212 - 2022-12-12

18.3.0-next-992911981-20220718 - 2022-07-19

18.3.0-next-987292815-20221019 - 2022-10-19

18.3.0-next-975b64464-20220914 - 2022-09-15

18.3.0-next-955cad9bc-20220623 - 2022-06-24

18.3.0-next-934177598-20221022 - 2022-10-22

18.3.0-next-8e35b5060-20220706 - 2022-07-06

18.3.0-next-8e17bfd14-20230322 - 2023-03-22

18.3.0-next-8b9ac8175-20230131 - 2023-01-31

18.3.0-next-8951c5fc9-20220915 - 2022-09-16

18.3.0-next-86b0e9199-20230429 - 2023-05-01

18.3.0-next-85de6fde5-20230328 - 2023-03-29

18.3.0-next-85bb7b685-20230406 - 2023-04-06

18.3.0-next-855b77c9b-20230202 - 2023-02-03

18.3.0-next-84a0a171e-20221214 - 2022-12-15

18.3.0-next-8342a0992-20230327 - 2023-03-27

18.3.0-next-8310854ce-20230331 - 2023-03-31

18.3.0-next-81d4ee9ca-20221223 - 2022-12-23

18.3.0-next-819687279-20221208 - 2022-12-08

18.3.0-next-7f8c501f6-20230420 - 2023-04-20

18.3.0-next-7bcc68772-20220811 - 2022-08-11

18.3.0-next-7b25b961d-20220930 - 2022-09-30

18.3.0-next-7b0642bb9-20230412 - 2023-04-13

18.3.0-next-7a4336c40-20220712 - 2022-07-13

18.3.0-next-79c582981-20221021 - 2022-10-21

18.3.0-next-796d31809-20220812 - 2022-08-15

18.3.0-next-790ebc962-20230404 - 2023-04-05

18.3.0-next-758fc7fde-20230207 - 2023-02-08

18.3.0-next-703c67560-20230307 - 2023-03-07

18.3.0-next-7028ce745-20220907 - 2022-09-08

18.3.0-next-7002a6743-20230110 - 2023-01-11

18.3.0-next-6ff1733e6-20230225 - 2023-02-27

18.3.0-next-6fb8133ed-20221116 - 2022-11-17

18.3.0-next-6ef466c68-20220816 - 2022-08-16

18.3.0-next-6eadbe0c4-20230425 - 2023-04-26

18.3.0-next-6ddcbd4f9-20230209 - 2023-02-09

18.3.0-next-6883d7944-20221101 - 2022-11-01

18.3.0-next-67a61d5bd-20230228 - 2023-03-01

18.3.0-next-65e32e58b-20221019 - 2022-10-20

18.3.0-next-65b3449c8-20221005 - 2022-10-05

18.3.0-next-5fcf1a4b4-20221221 - 2022-12-22

18.3.0-next-5f34b051d-20220725 - 2022-07-25

18.3.0-next-5dd90c562-20230502 - 2023-05-02

18.3.0-next-5d60a0b84-20221006 - 2022-10-07

18.3.0-next-594093496-20230209 - 2023-02-09

18.3.0-next-58742c21b-20230411 - 2023-04-11

18.3.0-next-56ffca8b9-20221117 - 2022-11-18

18.3.0-next-56a3c18e5-20230314 - 2023-03-14

18.3.0-next-56389e81f-20220619 - 2022-06-20

18.3.0-next-555ece0cd-20230112 - 2023-01-12

18.3.0-next-55542bc73-20230210 - 2023-02-10

18.3.0-next-54f297a60-20221017 - 2022-10-17

18.3.0-next-5379b6123-20230105 - 2023-01-06

18.3.0-next-522f47345-20220614 - 2022-06-15

18.3.0-next-513417d69-20221007 - 2022-10-10

18.3.0-next-4fcc9184a-20230217 - 2023-02-17

18.3.0-next-4f8ffec45-20230115 - 2023-01-16

18.3.0-next-4ea063b56-20221101 - 2022-11-02

18.3.0-next-4dda96a40-20221213 - 2022-12-13

18.3.0-next-4cd788aef-20220630 - 2022-07-01

18.3.0-next-4bf2113a1-20230206 - 2023-02-06

18.3.0-next-4bd245e9e-20221104 - 2022-11-04

18.3.0-next-4a4ef2706-20230212 - 2023-02-13

18.3.0-next-49f8254d6-20220722 - 2022-07-22

18.3.0-next-49f741046-20230305 - 2023-03-06

18.3.0-next-491aec5d6-20230501 - 2023-05-01

18.3.0-next-47cf4e578-20230315 - 2023-03-15

18.3.0-next-41b4714f1-20230328 - 2023-03-28

18.3.0-next-41110021f-20230301 - 2023-03-01

18.3.0-next-3f3b46c84-20220730 - 2022-08-01

18.3.0-next-3de926449-20220927 - 2022-09-28

18.3.0-next-3ddbedd05-20220719 - 2022-07-20

18.3.0-next-3d615fc14-20220919 - 2022-09-19

18.3.0-next-3d443cad7-20220823 - 2022-08-24

18.3.0-next-3ba7add60-20221201 - 2022-12-01

18.3.0-next-3b814327e-20221014 - 2022-10-14

18.3.0-next-39a3b72c6-20230414 - 2023-04-14

18.3.0-next-3706edb81-20230308 - 2023-03-09

18.3.0-next-3554c8852-20230320 - 2023-03-20

18.3.0-next-353c30252-20221202 - 2022-12-02

18.3.0-next-338e6a967-20221004 - 2022-10-04

18.3.0-next-32baab38f-20220811 - 2022-08-12

18.3.0-next-30eb267ab-20220708 - 2022-07-08

18.3.0-next-2ef24145e-20230202 - 2023-02-03

18.3.0-next-2d80a0cd6-20221003 - 2022-10-03

18.3.0-next-2cf4352e1-20221011 - 2022-10-11

18.3.0-next-2c7dea736-20220726 - 2022-07-26

18.3.0-next-2b1fb91a5-20221220 - 2022-12-21

18.3.0-next-2ac77aab9-20221029 - 2022-10-31

18.3.0-next-28a574ea8-20221027 - 2022-10-27

18.3.0-next-2655c9354-20221121 - 2022-11-22

18.3.0-next-2619886ac-20230105 - 2023-01-05

18.3.0-next-229c86af0-20220616 - 2022-06-16

18.3.0-next-21021fb0f-20230412 - 2023-04-12

18.3.0-next-20a257c25-20220929 - 2022-09-29

18.3.0-next-1f248bdd7-20230419 - 2023-04-19

18.3.0-next-1e5245df8-20220817 - 2022-08-17

18.3.0-next-1e3e30dae-20221108 - 2022-11-08

18.3.0-next-1d3fc9c9c-20221023 - 2022-10-23

18.3.0-next-1a08f1478-20221103 - 2022-11-03

18.3.0-next-19e9a4c68-20220818 - 2022-08-18

18.3.0-next-189f70e17-20230216 - 2023-02-16

18.3.0-next-18282f881-20230428 - 2023-04-28

18.3.0-next-17e2a15be-20220808 - 2022-08-08

18.3.0-next-167853026-20220626 - 2022-06-27

18.3.0-next-1528c5ccd-20230306 - 2023-03-06

18.3.0-next-1308e49a6-20230330 - 2023-03-30

18.3.0-next-12a1d140e-20230321 - 2023-03-21

18.3.0-next-0ffc7f632-20230330 - 2023-03-30

18.3.0-next-0f4a83596-20230110 - 2023-01-10

18.3.0-next-0de3ddf56-20220825 - 2022-08-26

18.3.0-next-0cac4d54c-20220921 - 2022-09-21

18.3.0-next-0c11baa6a-20221022 - 2022-10-22

18.3.0-next-0ba4698c7-20230201 - 2023-02-01

18.3.0-next-0b974418c-20230106 - 2023-01-09

18.3.0-next-0b54e0047-20220914 - 2022-09-15

18.3.0-next-02206099a-20220714 - 2022-07-14

18.3.0-canary-feed8f3f9-20240118 - 2024-01-19

18.3.0-canary-fdc8c81e0-20230707 - 2023-07-07

18.3.0-canary-fdb368d9e-20230725 - 2023-07-26

18.3.0-canary-fda1f0b90-20230509 - 2023-05-09

18.3.0-canary-fc801116c-20230629 - 2023-06-29

18.3.0-canary-fbc9b68d6-20231123 - 2023-11-23

18.3.0-canary-fb10a2c66-20240228 - 2024-02-29

18.3.0-canary-f81c0f1ed-20230927 - 2023-09-27

18.3.0-canary-f359f9b41-20230810 - 2023-08-10

18.3.0-canary-f1039be4a-20240107 - 2024-01-08

18.3.0-canary-f0e808e5b-20240214 - 2024-02-14

18.3.0-canary-efb381bbf-20230505 - 2023-05-05

18.3.0-canary-ee68446ff-20231115 - 2023-11-15

18.3.0-canary-eb33bd747-20240312 - 2024-03-12

18.3.0-canary-ea17cc18f-20230807 - 2023-08-07

18.3.0-canary-e91142dd6-20230705 - 2023-07-06

18.3.0-canary-e61a60fac-20231011 - 2023-10-12

18.3.0-canary-e5205658f-20230913 - 2023-09-13

18.3.0-canary-e3fb7c1de-20230621 - 2023-06-21

18.3.0-canary-e373190fa-20240325 - 2024-03-25

18.3.0-canary-e1d20fc0c-20240122 - 2024-01-22

18.3.0-canary-e1ad4aa36-20230601 - 2023-06-02

18.3.0-canary-df12d7eac-20230510 - 2023-05-11

18.3.0-canary-ddff50469-20230829 - 2023-08-29

18.3.0-canary-dddfe6882-20231005 - 2023-10-05

18.3.0-canary-dd480ef92-20230822 - 2023-08-22

18.3.0-canary-db69f95e4-20231002 - 2023-10-03

18.3.0-canary-d900fadbf-20230929 - 2023-09-29

18.3.0-canary-d803f519e-20231020 - 2023-10-20

18.3.0-canary-d7a98a5e9-20230517 - 2023-05-17

18.3.0-canary-d6dcad6a8-20230914 - 2023-09-14

18.3.0-canary-d445cee60-20230718 - 2023-07-19

18.3.0-canary-d3def4793-20240208 - 2024-02-08

18.3.0-canary-d1c8cdae3-20230619 - 2023-06-20

18.3.0-canary-ce6842d8f-20230610 - 2023-06-12

18.3.0-canary-ce2bc58a9-20231102 - 2023-11-03

18.3.0-canary-cb3404a0c-20230807 - 2023-08-08

18.3.0-canary-cb2439624-20231219 - 2023-12-19

18.3.0-canary-c8deb5db6-20230622 - 2023-06-22

18.3.0-canary-c5b937576-20231219 - 2023-12-21

18.3.0-canary-c47c306a7-20231109 - 2023-11-09

18.3.0-canary-c3048aab4-20240326 - 2024-03-26

18.3.0-canary-c29ca23af-20231205 - 2023-12-05

18.3.0-canary-c17a27ef4-20231127 - 2023-11-28

18.3.0-canary-bff6be8eb-20230925 - 2023-09-26

18.3.0-canary-be67db46b-20231010 - 2023-10-10

18.3.0-canary-bbc8530ed-20230912 - 2023-09-12

18.3.0-canary-bbb9cb116-20231117 - 2023-11-17

18.3.0-canary-bb0944fe5-20240313 - 2024-03-13

18.3.0-canary-ba5e6a832-20240208 - 2024-02-09

18.3.0-canary-b9be4537c-20230905 - 2023-09-06

18.3.0-canary-b8e47d988-20231023 - 2023-10-23

18.3.0-canary-b7972822b-20230503 - 2023-05-03

18.3.0-canary-b5810163e-20230509 - 2023-05-10

18.3.0-canary-b4cdd3e89-20230823 - 2023-08-23

18.3.0-canary-b36ae8d7a-20231207 - 2023-12-07

18.3.0-canary-b30030471-20240117 - 2024-01-18

18.3.0-canary-b2d637128-20240123 - 2024-01-23

18.3.0-canary-b27725923-20230821 - 2023-08-21

18.3.0-canary-b00e27342-20230505 - 2023-05-05

18.3.0-canary-aef7ce554-20230503 - 2023-05-03

18.3.0-canary-aec521a96-20231114 - 2023-11-15

18.3.0-canary-ade82b8dd-20230816 - 2023-08-17

18.3.0-canary-ad720f36e-20240206 - 2024-02-06

18.3.0-canary-aba93acb6-20231205 - 2023-12-06

18.3.0-canary-ab31a9ed2-20230824 - 2023-08-25

18.3.0-canary-a9cc32511-20240215 - 2024-02-16

18.3.0-canary-a9985529f-20231025 - 2023-10-25

18.3.0-canary-a870b2d54-20240314 - 2024-03-14

18.3.0-canary-a6ed60a8e-20230929 - 2023-10-02

18.3.0-canary-a515d753b-20240220 - 2024-02-20

18.3.0-canary-a4939017f-20240320 - 2024-03-20

18.3.0-canary-a41957507-20231017 - 2023-10-17

18.3.0-canary-a3aae7fb0-20231208 - 2023-12-08

18.3.0-canary-a389046a5-20230512 - 2023-05-12

18.3.0-canary-a20eea251-20230809 - 2023-08-10

18.3.0-canary-a1f97589f-20230526 - 2023-05-30

18.3.0-canary-a1c62b8a7-20230627 - 2023-06-28

18.3.0-canary-a17467e7e-20231102 - 2023-11-02

18.3.0-canary-9f4fbec5f-20230717 - 2023-07-18

18.3.0-canary-9ba1bbd65-20230922 - 2023-09-22

18.3.0-canary-9b4f847d9-20230901 - 2023-09-01

18.3.0-canary-9abf6fa31-20231017 - 2023-10-17

18.3.0-canary-9a72e6227-20230525 - 2023-05-25

18.3.0-canary-997f52fbb-20230803 - 2023-08-04

18.3.0-canary-98f3f14d2-20230818 - 2023-08-18

18.3.0-canary-98b8359f6-20240223 - 2024-02-23

18.3.0-canary-971b62f47-20240129 - 2024-01-29

18.3.0-canary-966d17483-20240305 - 2024-03-05

18.3.0-canary-9617d39ec-20231018 - 2023-10-18

18.3.0-canary-95ec12839-20240205 - 2024-02-05

18.3.0-canary-953cb02f6-20230907 - 2023-09-07

18.3.0-canary-9377e1010-20230712 - 2023-07-12

18.3.0-canary-910045696-20230607 - 2023-06-07

18.3.0-canary-8ec962d82-20230623 - 2023-06-23

18.3.0-canary-8c8ee9ee6-20231026 - 2023-10-26

18.3.0-canary-8bb6ee1d3-20240125 - 2024-01-25

18.3.0-canary-88df88f94-20230613 - 2023-06-13

18.3.0-canary-88d56b8e8-20231004 - 2023-10-04

18.3.0-canary-87cb0bf18-20231129 - 2023-11-30

18.3.0-canary-8039e6d0b-20231026 - 2023-10-26

18.3.0-canary-7cd98ef2b-20230509 - 2023-05-10

18.3.0-canary-7ac5e9a60-20230508 - 2023-05-08

18.3.0-canary-77c4ac2ce-20231031 - 2023-11-01

18.3.0-canary-763612647-20240126 - 2024-01-26

18.3.0-canary-7508dcd5c-20231108 - 2023-11-08

18.3.0-canary-746890329-20231108 - 2023-11-09

18.3.0-canary-7118f5dd7-20230705 - 2023-07-05

18.3.0-canary-6f1324395-20231004 - 2023-10-04

18.3.0-canary-6db7f4209-20231021 - 2023-10-23

18.3.0-canary-6c7b41da3-20231123 - 2023-11-24

18.3.0-canary-6c3b8dbfe-20240226 - 2024-02-26

18.3.0-canary-6b3834a45-20231110 - 2023-11-10

18.3.0-canary-6aacd3fa1-20230626 - 2023-06-27

18.3.0-canary-67cc9ba87-20231016 - 2023-10-16

18.3.0-canary-670811593-20240322 - 2024-03-22

18.3.0-canary-6639ed3b3-20240111 - 2024-01-11

18.3.0-canary-640ccebb7-20231201 - 2023-12-04

18.3.0-canary-627b7abd6-20230911 - 2023-09-11

18.3.0-canary-62512bafc-20230928 - 2023-09-28

18.3.0-canary-613e6f5fc-20230616 - 2023-06-16

18.3.0-canary-60a927d04-20240113 - 2024-01-14

18.3.0-canary-5dd35968b-20231201 - 2023-12-01

18.3.0-canary-5c607369c-20240116 - 2024-01-17

18.3.0-canary-5bcade5fc-20231208 - 2023-12-08

18.3.0-canary-59831c98c-20240218 - 2024-02-19

18.3.0-canary-596827f6a-20240205 - 2024-02-05

18.3.0-canary-593ecee66-20231114 - 2023-11-14

18.3.0-canary-587ae49d7-20230720 - 2023-07-20

18.3.0-canary-56e20051c-20240311 - 2024-03-11

18.3.0-canary-546fe4681-20230713 - 2023-07-13

18.3.0-canary-546178f91-20231005 - 2023-10-05

18.3.0-canary-53ac21937-20230703 - 2023-07-03

18.3.0-canary-537228f9f-20231010 - 2023-10-11

18.3.0-canary-535c038d1-20230522 - 2023-05-23

18.3.0-canary-533fc28c1-20230810 - 2023-08-11

18.3.0-canary-5309f1028-20230517 - 2023-05-18

18.3.0-canary-52d542ad6-20231107 - 2023-11-08

18.3.0-canary-51ffd3564-20231025 - 2023-10-25

18.3.0-canary-4ddc019ac-20230614 - 2023-06-14

18.3.0-canary-4cd706566-20230512 - 2023-05-14

18.3.0-canary-4b877b6c6-20230519 - 2023-05-22

18.3.0-canary-4b84f1161-20240318 - 2024-03-19

18.3.0-canary-4b2a1115a-20240202 - 2024-02-02

18.3.0-canary-49eba0193-20230926 - 2023-09-27

18.3.0-canary-493f72b0a-20230727 - 2023-07-27

18.3.0-canary-47beb96cc-20240222 - 2024-02-22

18.3.0-canary-456d153bb-20230828 - 2023-08-28

18.3.0-canary-432b9f1d9-20231110 - 2023-11-13

18.3.0-canary-41f0e9dae-20230907 - 2023-09-08

18.3.0-canary-3ff846d10-20230724 - 2023-07-24

18.3.0-canary-3e00e58a6-20231217 - 2023-12-18

18.3.0-canary-3d9b20132-20240124 - 2024-01-24

18.3.0-canary-3c27178a2-20230920 - 2023-09-21

18.3.0-canary-3bcd2de01-20240227 - 2024-02-27

18.3.0-canary-388686f29-20230503 - 2023-05-03

18.3.0-canary-3808b01b3-20230830 - 2023-08-31

18.3.0-canary-338dddc08-20240307 - 2024-03-08

18.3.0-canary-31603f19d-20240109 - 2024-01-09

18.3.0-canary-2f8f77602-20240229 - 2024-03-01

18.3.0-canary-2e470a788-20240214 - 2024-02-15

18.3.0-canary-2cd19ed1d-20240207 - 2024-02-07

18.3.0-canary-2c338b16f-20231116 - 2023-11-16

18.3.0-canary-2bc7d336a-20240205 - 2024-02-06

18.3.0-canary-2983249dd-20231107 - 2023-11-07

18.3.0-canary-2807d781a-20230918 - 2023-09-18

18.3.0-canary-247738465-20240130 - 2024-01-30

18.3.0-canary-21a161fa3-20230609 - 2023-06-09

18.3.0-canary-2153a2966-20230628 - 2023-06-29

18.3.0-canary-20c91b653-20231018 - 2023-10-18

18.3.0-canary-201becd3d-20230808 - 2023-08-09

18.3.0-canary-1fdacbefd-20230630 - 2023-06-30

18.3.0-canary-1d5667a12-20240102 - 2024-01-03

18.3.0-canary-1cea38448-20230530 - 2023-05-31

18.3.0-canary-1b1dcb8a4-20230920 - 2023-09-20

18.3.0-canary-1a001dac6-20230812 - 2023-08-12

18.3.0-canary-16d053d59-20230506 - 2023-05-07

18.3.0-canary-151e75a12-20231010 - 2023-10-10

18.3.0-canary-14fd9630e-20240213 - 2024-02-13

18.3.0-canary-14898b6a9-20240318 - 2024-03-18

18.3.0-canary-13d0225c7-20230928 - 2023-09-28

18.3.0-canary-1219d57fc-20240201 - 2024-02-01

18.3.0-canary-0fb5b61ac-20230814 - 2023-08-15

18.3.0-canary-0e352ea01-20231109 - 2023-11-10

18.3.0-canary-0cdfef19b-20231211 - 2023-12-11

18.3.0-canary-0c6348758-20231030 - 2023-10-30

18.3.0-canary-0ac3ea471-20240111 - 2024-01-12

18.3.0-canary-0a360642d-20230711 - 2023-07-12

18.3.0-canary-09fbee89d-20231013 - 2023-10-13

18.3.0-canary-09285d5a7-20230925 - 2023-09-25

18.3.0-canary-08cd087ca-20240110 - 2024-01-10

18.3.0-canary-08a39539f-20231031 - 2023-11-01

18.3.0-canary-03d6f7cf0-20240209 - 2024-02-09

18.3.0-canary-035a41c4e-20230704 - 2023-07-04

18.3.0-canary-034130c02-20240303 - 2024-03-04

18.3.0-canary-0210f0b08-20230525 - 2023-05-26

18.3.0-canary-01ab35a9a-20240228 - 2024-02-28

18.3.0-canary-018c58c9c-20230601 - 2023-06-01

18.3.0-canary-0066e0b68-20240306 - 2024-03-06

18.2.0 - 2022-06-14React DOM

Provide a component stack as a second argument to onRecoverableError. (@ gnoff in #24591)
Fix hydrating into document causing a blank page on mismatch. (@ gnoff in #24523)
Fix false positive hydration errors with Suspense. (@ gnoff in #24480 and  @ acdlite in #24532)
Fix ignored setState in Safari when adding an iframe. (@ gaearon in #24459)

React DOM Server

Pass information about server errors to the client. (@ salazarm and @ gnoff in #24551 and #24591)
Allow to provide a reason when aborting the HTML stream. (@ gnoff in #24680)
Eliminate extraneous text separators in the HTML where possible. (@ gnoff in #24630)
Disallow complex children inside <title> elements to match the browser constraints. (@ gnoff in #24679)
Fix buffering in some worker environments by explicitly setting highWaterMark to 0. (@ jplhomer in #24641)

Server Components (Experimental)

Add support for useId() inside Server Components. (@ gnoff) in #24172

    from react GitHub release notes

Package name: react-dom

18.3.1 - 2024-04-26
Export act from react f1338f

18.3.0 - 2024-04-25This release is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19.
Read the React 19 Upgrade Guide for more info.
React

Allow writing to this.refs to support string ref codemod 909071
Warn for deprecated findDOMNode outside StrictMode c3b283
Warn for deprecated test-utils methods d4ea75
Warn for deprecated Legacy Context outside StrictMode 415ee0
Warn for deprecated string refs outside StrictMode #25383
Warn for deprecated defaultProps for function components #25699
Warn when spreading key #25697
Warn when using act from test-utils d4ea75

React DOM

Warn for deprecated unmountComponentAtNode 8a015b
Warn for deprecated renderToStaticNodeStream #28874

18.3.0-next-fecc288b7-20221025 - 2022-10-25

18.3.0-next-fccf3a9fb-20230213 - 2023-02-14

18.3.0-next-fabef7a6b-20221215 - 2022-12-16

18.3.0-next-fa4314841-20230502 - 2023-05-03

18.3.0-next-f828bad38-20230313 - 2023-03-13

18.3.0-next-f0efa1164-20220901 - 2022-09-02

18.3.0-next-f0534ae94-20221202 - 2022-12-05

18.3.0-next-efc6a08e9-20220923 - 2022-09-23

18.3.0-next-ee8509801-20230117 - 2023-01-17

18.3.0-next-edbfc6399-20221128 - 2022-11-29

18.3.0-next-ed545ae3d-20230425 - 2023-04-25

18.3.0-next-e98225485-20221129 - 2022-11-30

18.3.0-next-e7c5af45c-20221023 - 2022-10-24

18.3.0-next-e6a062bd2-20220913 - 2022-09-13

18.3.0-next-e61fd91f5-20220630 - 2022-06-30

18.3.0-next-e40893d09-20221005 - 2022-10-06

18.3.0-next-e225fa43a-20220711 - 2022-07-12

18.3.0-next-e1dd0a2f5-20221115 - 2022-11-16

18.3.0-next-de7d1c907-20221223 - 2022-12-26

18.3.0-next-dd5365878-20230407 - 2023-04-07

18.3.0-next-dd2d65227-20220708 - 2022-07-11

18.3.0-next-d962f35ca-20230418 - 2023-04-18

18.3.0-next-d925a8d0b-20221024 - 2022-10-24

18.3.0-next-d807eb52c-20221205 - 2022-12-06

18.3.0-next-d49e0e0be-20230302 - 2023-03-02

18.3.0-next-d1e35c703-20221110 - 2022-11-10

18.3.0-next-d1bb1c586-20220922 - 2022-09-22

18.3.0-next-d1432ba93-20220628 - 2022-06-29

18.3.0-next-cf665c4b7-20220620 - 2022-06-21

18.3.0-next-cf3932be5-20221027 - 2022-10-28

18.3.0-next-cce18e350-20221023 - 2022-10-23

18.3.0-next-cb5084d1c-20220924 - 2022-09-24

18.3.0-next-ca990e9a7-20220804 - 2022-08-05

18.3.0-next-ca2cf319f-20230223 - 2023-02-24

18.3.0-next-c8b778b7f-20220825 - 2022-08-25

18.3.0-next-c89a83695-20220923 - 2022-09-23

18.3.0-next-c8369527e-20230420 - 2023-04-21

18.3.0-next-c80e54116-20220907 - 2022-09-07

18.3.0-next-c739cef2f-20220912 - 2022-09-12

18.3.0-next-c54e3541b-20221111 - 2022-11-14

18.3.0-next-c3b18571d-20220707 - 2022-07-07

18.3.0-next-c28f313e6-20220908 - 2022-09-09

18.3.0-next-c1f5884ff-20220705 - 2022-07-05

18.3.0-next-c1d414d75-20220923 - 2022-09-23

18.3.0-next-c08d8b804-20221118 - 2022-11-21

18.3.0-next-bfb9cbd8c-20230223 - 2023-02-24

18.3.0-next-b72ed698f-20230303 - 2023-03-03

18.3.0-next-b4204ede6-20220803 - 2022-08-04

18.3.0-next-b14f8da15-20230403 - 2023-04-03

18.3.0-next-b14d7fa4b-20221209 - 2022-12-09

18.3.0-next-b0671f9ea-20230130 - 2023-01-30

18.3.0-next-afe664d9d-20220913 - 2022-09-14

18.3.0-next-ae7ad8b4c-20220927 - 2022-09-27

18.3.0-next-abbbdf4ce-20220930 - 2022-09-30

18.3.0-next-aa9988e5e-20221010 - 2022-10-10

18.3.0-next-a8c16a004-20221012 - 2022-10-13

18.3.0-next-a8875eab7-20230310 - 2023-03-10

18.3.0-next-a6bf46689-20221014 - 2022-10-14

18.3.0-next-a4bed4696-20220627 - 2022-06-28

18.3.0-next-a0619e26c-20221207 - 2022-12-07

18.3.0-next-9ff738f53-20220826 - 2022-08-29

18.3.0-next-9fcaf88d5-20220801 - 2022-08-02

18.3.0-next-9fb2469a6-20230308 - 2023-03-08

18.3.0-next-9e67e7a31-20220823 - 2022-08-23

18.3.0-next-9cdf8a99e-20221018 - 2022-10-18

18.3.0-next-9c54b29b4-20230322 - 2023-03-23

18.3.0-next-9a9da7721-20230409 - 2023-04-10

18.3.0-next-996e4c0d5-20221212 - 2022-12-12

18.3.0-next-992911981-20220718 - 2022-07-19

18.3.0-next-987292815-20221019 - 2022-10-19

18.3.0-next-975b64464-20220914 - 2022-09-15

18.3.0-next-955cad9bc-20220623 - 2022-06-24

18.3.0-next-934177598-20221022 - 2022-10-22

18.3.0-next-8e35b5060-20220706 - 2022-07-06

18.3.0-next-8e17bfd14-20230322 - 2023-03-22

18.3.0-next-8b9ac8175-20230131 - 2023-01-31

18.3.0-next-8951c5fc9-20220915 - 2022-09-16

18.3.0-next-86b0e9199-20230429 - 2023-05-01

18.3.0-next-85de6fde5-20230328 - 2023-03-29

18.3.0-next-85bb7b685-20230406 - 2023-04-06

18.3.0-next-855b77c9b-20230202 - 2023-02-03

18.3.0-next-84a0a171e-20221214 - 2022-12-15

18.3.0-next-8342a0992-20230327 - 2023-03-27

18.3.0-next-8310854ce-20230331 - 2023-03-31

18.3.0-next-81d4ee9ca-20221223 - 2022-12-23

18.3.0-next-819687279-20221208 - 2022-12-08

18.3.0-next-7f8c501f6-20230420 - 2023-04-20

18.3.0-next-7bcc68772-20220811 - 2022-08-11

18.3.0-next-7b25b961d-20220930 - 2022-09-30

18.3.0-next-7b0642bb9-20230412 - 2023-04-13

18.3.0-next-7a4336c40-20220712 - 2022-07-13

18.3.0-next-79c582981-20221021 - 2022-10-21

18.3.0-next-796d31809-20220812 - 2022-08-15

18.3.0-next-790ebc962-20230404 - 2023-04-05

18.3.0-next-758fc7fde-20230207 - 2023-02-08

18.3.0-next-703c67560-20230307 - 2023-03-07

18.3.0-next-7028ce745-20220907 - 2022-09-08

18.3.0-next-7002a6743-20230110 - 2023-01-11

18.3.0-next-6ff1733e6-20230225 - 2023-02-27

18.3.0-next-6fb8133ed-20221116 - 2022-11-17

18.3.0-next-6ef466c68-20220816 - 2022-08-16

18.3.0-next-6eadbe0c4-20230425 - 2023-04-26

18.3.0-next-6ddcbd4f9-20230209 - 2023-02-09

18.3.0-next-6883d7944-20221101 - 2022-11-01

18.3.0-next-67a61d5bd-20230228 - 2023-03-01

18.3.0-next-65e32e58b-20221019 - 2022-10-20

18.3.0-next-65b3449c8-20221005 - 2022-10-05

18.3.0-next-5fcf1a4b4-20221221 - 2022-12-22

18.3.0-next-5f34b051d-20220725 - 2022-07-25

18.3.0-next-5dd90c562-20230502 - 2023-05-02

18.3.0-next-5d60a0b84-20221006 - 2022-10-07

18.3.0-next-594093496-20230209 - 2023-02-09

18.3.0-next-58742c21b-20230411 - 2023-04-11

18.3.0-next-56ffca8b9-20221117 - 2022-11-18

18.3.0-next-56a3c18e5-20230314 - 2023-03-14

18.3.0-next-56389e81f-20220619 - 2022-06-20

18.3.0-next-555ece0cd-20230112 - 2023-01-12

18.3.0-next-55542bc73-20230210 - 2023-02-10

18.3.0-next-54f297a60-20221017 - 2022-10-17

18.3.0-next-5379b6123-20230105 - 2023-01-06

18.3.0-next-522f47345-20220614 - 2022-06-15

18.3.0-next-513417d69-20221007 - 2022-10-10

18.3.0-next-4fcc9184a-20230217 - 2023-02-17

18.3.0-next-4f8ffec45-20230115 - 2023-01-16

18.3.0-next-4ea063b56-20221101 - 2022-11-02

18.3.0-next-4dda96a40-20221213 - 2022-12-13

18.3.0-next-4cd788aef-20220630 - 2022-07-01

18.3.0-next-4bf2113a1-20230206 - 2023-02-06

18.3.0-next-4bd245e9e-20221104 - 2022-11-04

18.3.0-next-4a4ef2706-20230212 - 2023-02-13

18.3.0-next-49f8254d6-20220722 - 2022-07-22

18.3.0-next-49f741046-20230305 - 2023-03-06

18.3.0-next-491aec5d6-20230501 - 2023-05-01

18.3.0-next-47cf4e578-20230315 - 2023-03-15

18.3.0-next-41b4714f1-20230328 - 2023-03-28

18.3.0-next-41110021f-20230301 - 2023-03-01

18.3.0-next-3f3b46c84-20220730 - 2022-08-01

18.3.0-next-3de926449-20220927 - 2022-09-28

18.3.0-next-3ddbedd05-20220719 - 2022-07-20

18.3.0-next-3d615fc14-20220919 - 2022-09-19

18.3.0-next-3d443cad7-20220823 - 2022-08-24

18.3.0-next-3ba7add60-20221201 - 2022-12-01

18.3.0-next-3b814327e-20221014 - 2022-10-14

18.3.0-next-39a3b72c6-20230414 - 2023-04-14

18.3.0-next-3706edb81-20230308 - 2023-03-09

18.3.0-next-3554c8852-20230320 - 2023-03-20

18.3.0-next-353c30252-20221202 - 2022-12-02

18.3.0-next-338e6a967-20221004 - 2022-10-04

18.3.0-next-32baab38f-20220811 - 2022-08-12

18.3.0-next-30eb267ab-20220708 - 2022-07-08

18.3.0-next-2ef24145e-20230202 - 2023-02-03

18.3.0-next-2d80a0cd6-20221003 - 2022-10-03

18.3.0-next-2cf4352e1-20221011 - 2022-10-11

18.3.0-next-2c7dea736-20220726 - 2022-07-26

18.3.0-next-2b1fb91a5-20221220 - 2022-12-21

18.3.0-next-2ac77aab9-20221029 - 2022-10-31

18.3.0-next-28a574ea8-20221027 - 2022-10-27

18.3.0-next-2655c9354-20221121 - 2022-11-22

18.3.0-next-2619886ac-20230105 - 2023-01-05

18.3.0-next-229c86af0-20220616 - 2022-06-16

18.3.0-next-21021fb0f-20230412 - 2023-04-12

18.3.0-next-20a257c25-20220929 - 2022-09-29

18.3.0-next-1f248bdd7-20230419 - 2023-04-19

18.3.0-next-1e5245df8-20220817 - 2022-08-17

18.3.0-next-1e3e30dae-20221108 - 2022-11-08

18.3.0-next-1d3fc9c9c-20221023 - 2022-10-23

18.3.0-next-1a08f1478-20221103 - 2022-11-03

18.3.0-next-19e9a4c68-20220818 - 2022-08-18

18.3.0-next-189f70e17-20230216 - 2023-02-16

18.3.0-next-18282f881-20230428 - 2023-04-28

18.3.0-next-17e2a15be-20220808 - 2022-08-08

18.3.0-next-167853026-20220626 - 2022-06-27

18.3.0-next-1528c5ccd-20230306 - 2023-03-06

18.3.0-next-1308e49a6-20230330 - 2023-03-30

18.3.0-next-12a1d140e-20230321 - 2023-03-21

18.3.0-next-0ffc7f632-20230330 - 2023-03-30

18.3.0-next-0f4a83596-20230110 - 2023-01-10

18.3.0-next-0de3ddf56-20220825 - 2022-08-26

18.3.0-next-0cac4d54c-20220921 - 2022-09-21

18.3.0-next-0c11baa6a-20221022 - 2022-10-22

18.3.0-next-0ba4698c7-20230201 - 2023-02-01

18.3.0-next-0b974418c-20230106 - 2023-01-09

18.3.0-next-0b54e0047-20220914 - 2022-09-15

18.3.0-next-02206099a-20220714 - 2022-07-14

18.3.0-canary-feed8f3f9-20240118 - 2024-01-19

18.3.0-canary-fdc8c81e0-20230707 - 2023-07-07

18.3.0-canary-fdb368d9e-20230725 - 2023-07-26

18.3.0-canary-fda1f0b90-20230509 - 2023-05-09

18.3.0-canary-fc801116c-20230629 - 2023-06-29

18.3.0-canary-fbc9b68d6-20231123 - 2023-11-23

18.3.0-canary-fb10a2c66-20240228 - 2024-02-29

18.3.0-canary-f81c0f1ed-20230927 - 2023-09-27

18.3.0-canary-f359f9b41-20230810 - 2023-08-10

18.3.0-canary-f1039be4a-20240107 - 2024-01-08

18.3.0-canary-f0e808e5b-20240214 - 2024-02-14

18.3.0-canary-efb381bbf-20230505 - 2023-05-05

18.3.0-canary-ee68446ff-20231115 - 2023-11-15

18.3.0-canary-eb33bd747-20240312 - 2024-03-12

18.3.0-canary-ea17cc18f-20230807 - 2023-08-07

18.3.0-canary-e91142dd6-20230705 - 2023-07-06

18.3.0-canary-e61a60fac-20231011 - 2023-10-12

18.3.0-canary-e5205658f-20230913 - 2023-09-13

18.3.0-canary-e3fb7c1de-20230621 - 2023-06-21

18.3.0-canary-e373190fa-20240325 - 2024-03-25

18.3.0-canary-e1d20fc0c-20240122 - 2024-01-22

18.3.0-canary-e1ad4aa36-20230601 - 2023-06-02

18.3.0-canary-df12d7eac-20230510 - 2023-05-11

18.3.0-canary-ddff50469-20230829 - 2023-08-29

18.3.0-canary-dddfe6882-20231005 - 2023-10-05

18.3.0-canary-dd480ef92-20230822 - 2023-08-22

18.3.0-canary-db69f95e4-20231002 - 2023-10-03

18.3.0-canary-d900fadbf-20230929 - 2023-09-29

18.3.0-canary-d803f519e-20231020 - 2023-10-20

18.3.0-canary-d7a98a5e9-20230517 - 2023-05-17

18.3.0-canary-d6dcad6a8-20230914 - 2023-09-14

18.3.0-canary-d445cee60-20230718 - 2023-07-19

18.3.0-canary-d3def4793-20240208 - 2024-02-08

18.3.0-canary-d1c8cdae3-20230619 - 2023-06-20

18.3.0-canary-ce6842d8f-20230610 - 2023-06-12

18.3.0-canary-ce2bc58a9-20231102 - 2023-11-03

18.3.0-canary-cb3404a0c-20230807 - 2023-08-08

18.3.0-canary-cb2439624-20231219 - 2023-12-19

18.3.0-canary-c8deb5db6-20230622 - 2023-06-22

18.3.0-canary-c5b937576-20231219 - 2023-12-21

18.3.0-canary-c47c306a7-20231109 - 2023-11-09

18.3.0-canary-c3048aab4-20240326 - 2024-03-26

18.3.0-canary-c29ca23af-20231205 - 2023-12-05

18.3.0-canary-c17a27ef4-20231127 - 2023-11-28

18.3.0-canary-bff6be8eb-20230925 - 2023-09-26

18.3.0-canary-be67db46b-20231010 - 2023-10-10

18.3.0-canary-bbc8530ed-20230912 - 2023-09-12

18.3.0-canary-bbb9cb116-20231117 - 2023-11-17

18.3.0-canary-bb0944fe5-20240313 - 2024-03-13

18.3.0-canary-ba5e6a832-20240208 - 2024-02-09

18.3.0-canary-b9be4537c-20230905 - 2023-09-06

18.3.0-canary-b8e47d988-20231023 - 2023-10-23

18.3.0-canary-b7972822b-20230503 - 2023-05-03

18.3.0-canary-b5810163e-20230509 - 2023-05-10

18.3.0-canary-b4cdd3e89-20230823 - 2023-08-23

18.3.0-canary-b36ae8d7a-20231207 - 2023-12-07

18.3.0-canary-b30030471-20240117 - 2024-01-18

18.3.0-canary-b2d637128-20240123 - 2024-01-23

18.3.0-canary-b27725923-20230821 - 2023-08-21

18.3.0-canary-b00e27342-20230505 - 2023-05-05

18.3.0-canary-aef7ce554-20230503 - 2023-05-03

18.3.0-canary-aec521a96-20231114 - 2023-11-15

18.3.0-canary-ade82b8dd-20230816 - 2023-08-17

18.3.0-canary-ad720f36e-20240206 - 2024-02-06

18.3.0-canary-aba93acb6-20231205 - 2023-12-06

18.3.0-canary-ab31a9ed2-20230824 - 2023-08-25

18.3.0-canary-a9cc32511-20240215 - 2024-02-16

18.3.0-canary-a9985529f-20231025 - 2023-10-25

18.3.0-canary-a870b2d54-20240314 - 2024-03-14

18.3.0-canary-a6ed60a8e-20230929 - 2023-10-02

18.3.0-canary-a515d753b-20240220 - 2024-02-20

18.3.0-canary-a4939017f-20240320 - 2024-03-20

18.3.0-canary-a41957507-20231017 - 2023-10-17

18.3.0-canary-a3aae7fb0-20231208 - 2023-12-08

18.3.0-canary-a389046a5-20230512 - 2023-05-12

18.3.0-canary-a20eea251-20230809 - 2023-08-10

18.3.0-canary-a1f97589f-20230526 - 2023-05-30

18.3.0-canary-a1c62b8a7-20230627 - 2023-06-28

18.3.0-canary-a17467e7e-20231102 - 2023-11-02

18.3.0-canary-9f4fbec5f-20230717 - 2023-07-18

18.3.0-canary-9ba1bbd65-20230922 - 2023-09-22

18.3.0-canary-9b4f847d9-20230901 - 2023-09-01

18.3.0-canary-9abf6fa31-20231017 - 2023-10-17

18.3.0-canary-9a72e6227-20230525 - 2023-05-25

18.3.0-canary-997f52fbb-20230803 - 2023-08-04

18.3.0-canary-98f3f14d2-20230818 - 2023-08-18

18.3.0-canary-98b8359f6-20240223 - 2024-02-23

18.3.0-canary-971b62f47-20240129 - 2024-01-29

18.3.0-canary-966d17483-20240305 - 2024-03-05

18.3.0-canary-9617d39ec-20231018 - 2023-10-18

18.3.0-canary-95ec12839-20240205 - 2024-02-05

18.3.0-canary-953cb02f6-20230907 - 2023-09-07

18.3.0-canary-9377e1010-20230712 - 2023-07-12

18.3.0-canary-910045696-20230607 - 2023-06-07

18.3.0-canary-8ec962d82-20230623 - 2023-06-23

18.3.0-canary-8c8ee9ee6-20231026 - 2023-10-26

18.3.0-canary-8bb6ee1d3-20240125 - 2024-01-25

18.3.0-canary-88df88f94-20230613 - 2023-06-13

18.3.0-canary-88d56b8e8-20231004 - 2023-10-04

18.3.0-canary-87cb0bf18-20231129 - 2023-11-30

18.3.0-canary-80...

👷 Deploy Preview for radiant-beignet-d1e2e7 processing.

Name
Link

🔨 Latest commit
f435f1896d19375e042d326669b86ccbdb546583

🔍 Latest deploy log
https://app.netlify.com/sites/radiant-beignet-d1e2e7/deploys/66511f6aa04d90000801977a

repo: X-oss-byte/gatsby-starter-minimal


text:
What order do I merge in?

If I want to add Mohak's code to my branch, so I can have access to the Move class, is it
GameLogic -> player-moves
or
player-moves -> GameLogic

My branch is player-moves and Mohak's is GameLogic

GameLogic -> player-moves

Thanks

Did it work? I don't see your merge in the branching diagram

I just added it, encountered one issue but fixed it. Can you see if it's there now?

Not yet. Try committing and syncing

I still see two different branches. Can we both work on the same branch but different classes at the same time?

I want to keep two separate branches, so we can work individually still. The merge thing was just to add your code to mine, not necessarily vice versa.
I committed and synced the changes. I'm even seeing "Merging GameLogic into player-moves …
apprehensivemeerkat authored 5 minutes ago" in the commit log.

When you "merge branches," you don't combine them into one. You just basically copy the first branch's changes onto the second branch. See the branching diagram for a graphical representation of what I mean.
Yes, you can both work on different classes in the same branch.

Byrne, is it still not showing? At least for me, I can see the arrow on the diagram pointing in from GameLogic to player-moves

I see it. You're good

Cool Beans
NetBeans
(this is my new catch phrase, get used to it)


text:
🛑 Board is down

In acbc3bd, Board (https://board.xcpcio.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Board is back up in 8e33065.

repo: XCPCIO/uptime


text:
account 100 is only 67 address

i use xdag -i
account 100
only create 67 address . is not 100.  and account 200 only 67 .
i need more address how to do?

account 100 doesn't create new addresses, you shouldn't use these other addresses that you see because some of these addresses are transaction addresses, not wallet addresses.

how to create new wallet addresses ? i want build user pay functions need more address

@okfirelee  Not possible to create multiple addresses with wallet not. Please try transaction remark in 0.3.1.

authors: okfirelee sgaragagghu xrdavies

repo: XDagger/xdag


text:
Refactor Complete

Fixes

advance entry
revert entry
git logo
refactor

also closes #9

Demo

repo: XDwightsBeetsX/tournament-bracket


text:
Use read by index and check for NaNs

Before you submit this PR: make sure to put all operations-related information in a wiki-note, a PR should be about code and is publicly accessible
Use read by index and check for NaNs
What does the code in this PR do / what does it improve?
Use read by index and check for NaNs see https://github.com/AxFoundation/strax/pull/529
Can you briefly describe how it works?
Can you give a minimal working example (or illustrate with a figure)?
Please include the following if applicable:

[ x] Update the docstring(s)
[x ] Update the documentation
[x ] Tests to check the (new) code is working as desired.
[x ] Does it solve one of the open issues on github?

Notes on testing

Until the automated tests pass, please mark the PR as a draft.
On the XENONnT fork we test with database access, on private forks there is no database access for security considerations.

All italic comments can be removed from this template.

Same comment as in https://github.com/AxFoundation/strax/pull/529#pullrequestreview-746453238

As I said in previously in my opinion we need this for reprocessing, specially because the discussion regarding "to_pe" values modeling

Merging this now that AxFoundation/strax#529 is merged.

authors: WenzDaniel ahiguera-mx ershockley

repo: XENONnT/straxen


text:
No Overall Scale Option

There used to be an option to scale the whole model equally, but it appears to not be possible anymore.

This is intentional. Height scaling/full model scaling should be done with penumbra racial scaling mods, and not with cutsomize+. There is a guide pinned in the discord showing how to do so.

This is intentional. Height scaling/full model scaling should be done with penumbra racial scaling mods, and not with cutsomize+. There is a guide pinned in the discord showing how to do so.

Does that apply to minion/fairy/carbuncle etc? Because the Root option under Advanced works on my character, but not other types of models.

You mentioned a discord, where can I find it to utilize this guide. I also just think it was an overall stupid decision to remove the full body scaling option.

repo: XIV-Tools/CustomizePlus


text:
list index out of range

Workflow used -workflow-ai-made-simple-lora-custom-flux-lora-zhI6ZH2Loc8A9Izk71Ej-seal_harmful_40-openart.ai.json
I am using A5000 24gb gpu
Error details -
Error occurred when executing XlabsSampler:
list index out of range
File "/home/ComfyUI/execution.py", line 316, in execute
output_data, output_ui, has_subgraph = get_output_data(obj, input_data_all, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
File "/home/ComfyUI/execution.py", line 191, in get_output_data
return_values = _map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
File "/home/ComfyUI/execution.py", line 168, in _map_node_over_list
process_inputs(input_dict, i)
File "/home/ComfyUI/execution.py", line 157, in process_inputs
results.append(getattr(obj, func)(**inputs))
File "/home/ComfyUI/custom_nodes/x-flux-comfyui/nodes.py", line 411, in sampling
x = denoise(
File "/home/ComfyUI/custom_nodes/x-flux-comfyui/sampling.py", line 178, in denoise
t = timesteps[t_idx]

I fixed this by putting an empty latent into the Xlabs Sampler instead of a vae-encoded version of the loaded image. My input image was 1024x1024, encoded with the ae.safetensors vae, so I expected it to work.
Having to use an empty latent as input might not be ideal for every use case...

Is there any way to utilize an img2img workflow with the XLabs Sampler or is it only via empty latent?

repo: XLabs-AI/x-flux-comfyui


text:
Click Ribbon

Hi , any example where you are clicking a ribbon button under more commands ? I ve tried using label and data-id, but is not even expanding more commands.
Thanks!

Hi @imartinflores,
that should usually be done automatically. There is a logic when clicking a button, which searches for it and if it does not find it, clicks the more commands button automatically and retries searching your button.
Can you give me a code example of what you're trying to do?
Kind Regards,
Florian

Hi @DigitalFlow ! Thanks for your answer. Sure, here is what I am trying to do:
 await xrmTest.Navigation.openUpdateForm("contact", contactid);   await xrmTest.Button.click({byDataId: "contact|NoRelationship|Form|win.contact.Button22.Button"}, true)
also tried:
await xrmTest.Button.click({byLabel: "General"}, true)
but both returns:   Failed to find button
Thank you!

Hi @imartinflores,
Is it a simple button, or some special one such as a combo button?
Which version of D365-UI-Test and CRM are you using?
Kind Regards,
Florian

Hi @DigitalFlow !
Its a simple ribbon button, inside of more commands, its to create incidents. I know we have the option to openCreateForm()
but this is because we had an issue with ribbon not being clickable, so I would like to check. I am using latest version, just updated it this morning to make sure. And Microsoft Dynamics 365 Online Version 9.1 (9.1.x) (DB 9.1.x) online.
I have tried with another ribbon button, which does not have "More commands" and it works
Thanks!

Hi @imartinflores,
First up: Does the "More Commands" menu even open at your side?
If yes, can you manage to show me the HTML of the button that you are trying to click?
It's a little annoying to get it, you will probably have to add a DOM breakpoint inside the browser debugger, as the more commands overlay will disappear once you click anywhere else (including the debugger).
Kind Regards,
Florian

Hey @DigitalFlow !
From what I could see, is not even opening the more commands.
Sure, here you have the more commands:

And the button I am trying to click:

Let me know if that helps.
Thanks!

Hi @imartinflores,
could you copy the HTML in here? It seems that there is quite some stuff missing.
You can just right click on the nodes and click "Edit as HTML", then you can copy it.
It seems however that your button is not a normal button, but a SplitButton. Might be that there is something special in how the HTML is generated for these.
Kind Regards,
Florian

Sure @DigitalFlow :
This is the more commands HTML:
`
Creates a new case for this playerPress Enter to open flyout`
And this is the one trying to click:

<button id="contact|NoRelationship|Form|win.contact.AddNewCase.Command.General02-button" aria-label="General" role="menuitem" tabindex="0" data-id="contact|NoRelationship|Form|win.contact.Button22.Button" data-lp-id="Form:contact-contact|NoRelationship|Form|win.contact.Button22.Button" type="button" class="pa-oc pa-bh pa-ak pa-fx pa-aj pa-oa pa-ob pa-jd pa-je pa-ah pa-at pa-ld flexbox" style="outline-color: rgb(102, 102, 102);">General</button>

Hope it helps more now, again, let me know if you need more help from me.
Thanks a lot

Hi @imartinflores,
I think there is something wrong with your overflow / "More Commands" button. It should look totally different.
The important part is the data-id="OverflowButton" property on its button HTML element:
    <button id="OverflowButton_button24$button" aria-label="Weitere Befehle für Kontakt" aria-describedby=" openflyout_description_OverflowButton_button24" aria-expanded="false" aria-haspopup="true" role="menuitem" tabindex="0" data-id="OverflowButton" data-lp-id="Form:contact-OverflowButton" type="button" class="pa-ak pa-ka pa-fp pa-fu pa-da pa-aj pa-at pa-pj flexbox">

Can you post a screenshot of what the button that you see as overflow button looks like? Should look something like this:

Kind Regards,
Florian

Sure @DigitalFlow , it does not look like that definitely. Attached you have a screenshot.
That way is clicking the "More Commands" and I need to wait for the "General" button to appear in the flyout before clicking it then. That will help.

Thank you!

Hi @imartinflores,
I see, so this is really a split button, not the overflow button.
Did you try my approach? The code that I sent should first expand your split button, wait for the UI to become idle and then click the General button inside the expanded Panel.
Should do the trick.
Kind Regards,
Florian

Hi @DigitalFlow , yeah, tried that, but seems like I need to add a Wait between clicks (More Commands and General) cause without it, it clicks the More Commands, but then fails cause the General button is not displayed immediately, so I will try to add a wait between. Thanks so much for looking into it, appreciate it!

Hi @imartinflores,
That's strange, usually it should wait at least 2 seconds on its own after clicking the first button.
But ok, adding a wait for the second button should be the way to go then.
Glad to have helped and glad that you're using this framework :).
Please close this issue once you got it working.
Kind Regards,
Florian

authors: DigitalFlow imartinflores


text:
Feature/controller mapping refactor

https://github.com/XRTK/XRTK-Core/pull/508

The number of files changed in this PR is comical, but they're all .asset files and a single script change

repo: XRTK/SDK


text:
Fock state and quadrature plotting

Context:
The functionality to plot the Fock state probability distribution and quadrature probability distributions currently available with SF interactive should be moved to SF.
Description of the Change:
Adds two plotting functions:

plot_fock: plots the Fock state probabilities given a state object, uses the generate_fock_chart auxiliary function;
plot_quad:  given a state object and arrays of x and p discretized quadrature values, uses the generate_quad_chart auxiliary function.

The generate_fock_chart and generate_quad_chart auxiliary functions create plotly compatible json charts.
Benefits:
Fock state probabilities and x and p-quadrature probabilities can be plotted.
Possible Drawbacks:
None
Related GitHub Issues:
None

Thanks for the comments & suggestions @josh146 @thisac! Let me know if there would still be something to adjust.
Added a new entry for plotting to the docs (appears on the sidebar now too):
https://strawberryfields--510.org.readthedocs.build/en/510/code/sf_plot.html

[ch1776] [ch1775]

[ch1776] [ch1775]

repo: XanaduAI/strawberryfields


text:
sscanf() is broken (hangs / stores unexpected values)

This code (taken from Neverball) leads to faulty behaviour:
#ifdef NXDK
#include <hal/video.h>
#include <hal/debug.h>
#else
#define debugPrint(...) printf(__VA_ARGS__)
#endif
#include <stdio.h>

int main() {

#ifdef NXDK
  XVideoSetMode(640, 480, 32, REFRESH_DEFAULT);
#endif

  const char* line = "fullscreen                0";

  int ks, ke, vs;

  ks = -1;
  ke = -1;
  vs = -1;

  debugPrint("Starting scan\n");

  int ret = sscanf(line, " %n%*s%n %n", &ks, &ke, &vs);

  debugPrint("Result %d = %d %d %d\n", ret, ks, ke, vs);

#ifdef NXDK
  while(1);
#else
  return 0;
#endif
}

On my desktop with clang I get:
Starting scan
Result 0 = 0 10 26

On nxdk (in XQEMU) I only get:
Starting scan

(it seems to hang before the second debugPrint is reached)
On nxdk (in XQEMU) I got this with an older revision of the code which didn't retrieve / print int ret:
Starting scan
Result 1701995379 1819047270 10

Probably a bug in pdclib? CC @DevSolar

This was fixed upstream in https://github.com/DevSolar/pdclib/issues/8.
I'm not sure if nxdk-pdclib has the fix yet.

repo: XboxDev/nxdk-pdclib


text:
New Skill Suggestion: Enchantment effects

This might be a lot harder to code, but giving enchantment effects to players without gear (ideally admins could toggle what gear it works with/requires) would really open up builds, and improve upon already existing ones.
For instance, adding something like the following to the Enderman hero would really round out the Enderman:
skill: ENCHANTED
type: SILK_TOUCH
gearType: HAND
For Dolphin it might look something like:
skill: ENCHANTED
type: AQUA_AFFINITY
gearType:
Leaving gearType blank on Dolphin means it works with all tools and armor, or without any, whereas gearType: HAND or whatever would mean Enderman could only silk touch up things with an empty hand unless they had another enchanted item.
Idk i’m not a coder lol, just thought it could be cool.

As far as I know, you can't give literal enchantment effects to players without it going on an item, things like silk touch could be emulated, but I don't think effects like aqua affinity can be as they're mostly client-side. How about an enchantment skill that guarantees a certain enchant on your item when you go to enchant? That could be interesting.

Yeah that could be cool. Very different flavor, but cool.
I’ve actually figured out how to get the effects I wanted on Enderman (using Convert Drops on dirt blocks) and Dolphin (using potion type Conduit_Power) anyway, lol.
Just so you know, i’m basically trying to use your plugin to mimic the Origins mod by Apace100 (link: https://www.curseforge.com/minecraft/mc-mods/origins ) purely server side so it works with vanilla clients.
Other skill/hero ideas that come from that mod would be climbing, place an object when attacking (both from Arachnid), a skill that applies diet limitations (though Consume could be used similarly), and various skills that apply negative effects like burning in daylight, drowning in air, or taking damage from water.

authors: Xemorr vayllonyx

repo: Xemorr/superheroes

license: Unlicense


text:
Add support for OTLP ingestion in datadog-operator

Open telemetry ingestion by the datadog agent was added to the datadog operator in this PR https://github.com/DataDog/datadog-operator/pull/597/files.
To enable this, see example here https://github.com/DataDog/datadog-operator/blob/main/examples/datadogagent/datadog-agent-otlp.yaml
This was added in https://github.com/DataDog/datadog-operator/releases/tag/v1.0.0-rc. We should probably wait with upgrading the datadog-operator until 1.0 is officially released.

Related: https://github.com/XenitAB/terraform-modules/pull/955

Related: #982

Solved in #1000

🥳🥳🥳

repo: XenitAB/terraform-modules


text:
🛑 GiteePage is down

In 2775df1, GiteePage (https://ravelloh.gitee.io) was down:

HTTP code: 0
Response time: 0 ms

Resolved: GiteePage is back up in 80ed227.

repo: Xeocnet-Studio/sitemonitor


text:
Scaling issue

I'm on 1.25x and the window doesn't really work:

Thanks, will patch

authors: XertroV codecat


text:
Reid Quantization Error by pytorch

I used JDAI-CV/fast-reid(https://github.com/JDAI-CV/fast-reid) trained a  model(backbone  resnest ) , when I use  pytorch  quantize the model , The following error occurred :

Does anyone know why?  Thanks.

Hi @jzymessi ,
It seems like there is something wrong with conv channels. Is there any error when you run float model? Can you upload  your torch model or show more details?

Hi @jzymessi
Has the problem been solved?

Hi @jzymessi Has the problem been solved?

Hi @qianglin-xlnx @Alexiazzf
This problem has been solved,Thanks!

authors: Alexiazzf jzymessi qianglin-xlnx

repo: Xilinx/Vitis-AI


text:
any help with starting with VSCODE?

Hi,
I have lots of ESP32 TTGO Lora Modules and want to test this TTGO LILYGO A7670SA now
as per intructions, there is no detail as to what type of board I should declare when importing the project on VSCO
any help?

Just select esp32dev

[env:esp32dev]
platform = espressif32
board = esp32dev
framework = arduino
upload_speed =  961200
monitor_speed = 115200
monitor_filters =
	default
	esp32_exception_decoder

authors: lewisxhe richonguzman


text:
Fix name of current directory

Just a tiny typo

Thanks . @albfan

authors: albfan lewisxhe


text:
🛑 MOMO is down

In 33291ad, MOMO (https://www.momoshop.com.tw/main/Main.jsp) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MOMO is back up in 775ce2e.


text:
🛑 MOMO is down

In a74202d, MOMO (https://www.momoshop.com.tw/main/Main.jsp) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MOMO is back up in 0850cf2.


text:
swagger导入的接口 地址后面少了slash /

版本号
1.10.2
什么问题

如何复现此问题

什么浏览器
chrome
什么系统（Linux, Windows, macOS）
windows

目前是通过Pre-request Script 来解决这个问题
if  (context.method =="POST" |  context.method =="PUT" | context.method =="DELETE"){
context.pathname = context.pathname + "/";
}

repo: YMFE/yapi


text:
开放接口建议免登录访问

我配置了接口的开放接口状态，把接口的url发给一个未注册登录的用户访问，
需要注册登录才能访问到。
例如：
未注册登录访问开放接口的地址http://test.com:3000/project/19/interface/api/699
跳转到了登录页面

我也有同样的需求，下网能够增加该功能

免登录: https://github.com/sazima/yapi

免登录: https://github.com/sazima/yapi

authors: JustinZhangGIS sazima warthur1214


text:
[1299] Clean Up #1271

Resolves #1299

no idea why this is failing, everything's fine locally

Looks like a spec ordering thing; it seems like you're creating a dummy user for a test that doesn't get deleted after the test is run, and therefore there's an extra user floating around later (although I'm not sure how it's related to your code changes). Can you look and see which specs are creating a user with the first name "First" and last name "Last"? Could it have something to do with the feature spec before blocks?

Figured it out -- it was the admin user I was creating

Awesome, I'll review now and then hopefully we can squash merge tomorrow to squeeze this into v5.3.0. Nice work!

Looks great, just a few minor comments. Feel free to squash after those are resolved and I'll double-check / merge tomorrow!

this is almost ready i just messed up git somehow

You can interactively rebase onto master and just delete the line of the extra commit in the selection stage. Let me know if you still have questions!

okay this is good!

awesome, merging!

authors: esoterik orenyk

repo: YaleSTC/reservations


text:
TaskContext feature

TaskContext

At the start of a pipeline execution, we should be able to hydrate some read-only store of configuration values. These values form a TaskContext that is available to every task. e.g. reading url for an endpoint we need to hit, or key vault secrets.
Bonus points: Store hydrators are registerable. By default, the store is hydrated from a local .yml file. Additional hydrators can be registered by client applications that override the default.

We all took a stab in the pair coding session. The yml provider is in place!

repo: YaroBear/task-engine-py


text:
Update contributors.md

updated!

@Yashika1410, done bro
can I add more projects

Yes you can add more project and can you please make a single pr for your project and contributors.md

@Yashika1410 , I added weather web on this branch


text:
Once again, no thumbnail animation, no likes/dislikes on it...

What I did was remove it from the Firefox add-ons page, download the yeppha.github.io
on my desktop and drag it on the Firefox icon just like last time.
I checked some random video page for the animation, likes, dislikes and frame rate and
sadly, nothing, just a boring static one.
What did I do wrong this time?
Please help!

If you haven't used the version 2.1.7 yet then you can download it from here: https://github.com/YePpHa/YouTubeCenter/wiki
Do not choose the link in front of AMO because it leads to an outdated version.
If you already tried the version 2.1.7 then try the latest developer version which can be found here: https://github.com/YePpHa/YouTubeCenter/wiki/Developer-Version
I have tested with the developer version 461 just now and the thumbnail animation, likes/dislikes and quality all displayed correctly.

I don't see the watch later button when I hover over thumbnails on the my subscribtions list
on the default page everythign works fine -> the button is visible

actually there is no difference
the issue is that the hovering function doesn't work anymore
->it only works to set it to show always
I switched the settings but they only took effect after I reloaded the page which elad to a false conclusion on my site -> it happens on all sites: hovering doesn't work

I have used the dev version as suggested and it now works. Thank you very much!
I NEED my thumbnail animation!

@Djfe create a new issue for the hover issue as it's not completely the same as the one @campaignsong reported. Anyway, I can confirm that the issue you're having with i.e. 'watch later' doesn't work when it's not set to Always.

authors: Djfe YePpHa Yonezpt campaignsong

repo: YePpHa/YouTubeCenter


text:
I cannot start video long time when 'prevent auto-play' is enabled and browser use HTML5-player

Browser is waiting response from host 'yt3.ggpht.com' and I cannot start playing video before he don't get it (usually it's about 1 or 2 minutes). But when I disable 'prevent auto-play' in YTC options or choose flash player in YouTube option - I can start video immideately, without waiting response from 'yt3.ggpht.com'.
Browser: Opera 28.0.1750.51
YTC: Developer Version - Build #501

Could you tell us which operating system are you using? Is it windows 8.1?

It's Windows 7

Guys, it's all right today! Maybe it was problem with YouTube hosts with thumbnails and images... YTC works fine today.

authors: Yonezpt okpc-okpc


text:
What's with the new name?

I noticed that, according to Chrome, the extension was renamed to YePpHa Center for YouTube. What brought about the change?

Aaah, it was when I tried to upload it to the webstore to prevent it from being taken down from using the YouTube name. It was allowed to use the for YouTube part.

authors: TheEssemCraft YePpHa


text:
关闭WebSocket

文档中只说明了如何开始，没有说明如何关闭啊！

服务端关闭是 session.close()

authors: YeautyYE cement


text:
I hope to be able to configure alert rule through the web

There are many business applications, each rule corresponds to an application. The configuration file is black box, we can not know the configuration file that can only be accessed by the operation and maintenance staff.

Tools from third parties
Praeco
Set on the web screen. yaml is generated. yaml does not allow direct editing
Send notifications to Slack, MS Teams, Email, Telegram, Jira, Line Notify, Mattermost, Command, Gitter or an HTTP POST endpoint
Supports the Any, Blacklist, Whitelist, Change, Frequency, Flatline, Spike, Cardinality, New Term, and Metric Aggregation rule types
ElastAlert Server
Praeco

You may not meet this need because you cannot edit directly with yaml

We also recommend asking questions on the Gitter channel
https://gitter.im/Yelp/elastalert

Yelp/elastalert is no longer maintained. Please use jertel/elastalert. Questions to the discussion below
https://github.com/jertel/elastalert/discussions

repo: Yelp/elastalert


text:
When run elastalert ,it always fetch documents in one week.

Today is 2016-08-31
$ elastalert --debug --verbose
INFO:elastalert:Note: In debug mode, alerts will be logged to console but NOT actually sent. To send them, use --verbose.
INFO:elastalert:Starting up
INFO:elastalert:Queried rule Status_Code_Check_Daily from 2016-08-25 16:25 CST to 2016-08-25 16:40 CST: 30 hits
INFO:elastalert:Queried rule Status_Code_Check_Daily from 2016-08-25 16:40 CST to 2016-08-25 16:55 CST: 30 hits
INFO:elastalert:Queried rule Status_Code_Check_Daily from 2016-08-25 16:55 CST to 2016-08-25 17:10 CST: 30 hits
How can I let elastalert just fetch recent two days documents.
config.yaml:
run_every:
minutes: 1
buffer_time:
minutes: 15
alert_time_limit:
days: 2

http://elastalert.readthedocs.io/en/latest/elastalert.html?highlight=old_query_limit
Add something like
old_query_limit:
  days: 1

This is a global option, not per rule.
The alternatives would be to delete elastalert_status documents with rule_name=Status_Code_Check_Daily. Or, change the name of the rule.

authors: Qmando jiapengjun


text:
refactored map.ts

!closes #427

This hasn't seen activity in several months; closing. Feel free to let me know if you pick this up again!

repo: Yes-Theory-Fam/yesbot-ts


text:
Open file from my current cursor?

I must say, this is clearly better than fzf. The fact we have cache and don't need to reindex every time is awesome. I am working on projects with over 1 million files. fzf is too slow.
One suggestion/question: is there a way to search file based on my cursor position? Like if I am editing a line like this
ClassName.functionCall()
^
my cursor is at 'a' now. Can we perform a file search of ClassName?

Now you can use LeaderfFileCword.

So awesome! Thanks.

authors: Yggdroot simprince

repo: Yggdroot/LeaderF


text:
Az 455 use component network in data io

Hello, this is an optional contribution to already existing branch which has PR on (https://github.com/Cardinal-Cryptography/aleph-node/pull/276). Feel free to reject or accept it, I don't want to block original PR. When rejected, I'll submit 'normal' PR to CC/aleph-node .
Testing done:

build,
UT,
4 nodes locally run via run_nodes.sh are finalizing blocks

Declining this PR - would raise another one to CC/main.

repo: Yithis/aleph-node


text:
关于新版1.0不强制继承SupportActivity/SupportFragment的咨询

新版不需要强制继承SupportActivity/SupportFragment了，可以通过implements ISupportActivity/Fragment ＋ Delegate形式自己实现自定义SupportActivity/Fragment (可拷贝SupportActivity/Fragment到自己的Support里)
关于这种委托我不是很明白具体怎么操作，是否在demo里也有这种的写法

#401 ， demo可见MySuportActvity/ MySupportFragment（这两个实现里 有部分方法没有实现），完整版直接拷贝SupportActivity/Fragment

repo: YoKeyword/Fragmentation