text:
Fixed Navbar

The issue is navbar was scrolling above the page, so I have added css to navbar component to make it fixed.

Eventhough you've worked well on the issue #99 but I have already assigned someone else so won't be able to merge this PR.

Uploading DoodleCollab (1).mp4…
I have made the navbar fixed, kindly check in the video

Hi @sudeepkudari0, make sure to have a valid syntax while giving the PR Title "fix: Navbar #109" so that check will be done successfully.

repo: WikiPortal/DoodleCollab


text:
first child of ShadowDOM cannot be a custom component

We get the error message: "ReactShadow: Passed child must be a concrete HTML element rather than another React component."
/*
index.js {

	import React from 'react'
	import {init} from "./ShadowDomBug"
	init();

	// expected  output
	// hello, world

	// actual output error
	// ReactShadow: Passed child must be a concrete HTML element rather than another React component.
}
*/

import React, {Component} from 'react';
import ReactDOM from 'react-dom'
import ShadowDOM from 'react-shadow'

class MyComponent extends Component {
	render() {
		return (
{this.props.children}
);
	}
}

export class ShadowDomBug extends Component {
	render() {
		return (
			<ShadowDOM>
				<MyComponent>

						hello, world

				</MyComponent>
			</ShadowDOM>
		);
	}
}

export const domRootId = 'ShadowDomBug';

export function init() {
	let root = document.getElementById(domRootId);
	if (!root) {
		root = document.createElement('div');
		root.id = domRootId;
		root.setAttribute('id', domRootId);
		document.body.appendChild(root);
		console.log('ini')
		ReactDOM.render(<ShadowDomBug/>, root);
	}
}

Yes, the immediate child of <ShadowDOM /> cannot be <MyComponent />, but rather a concrete HTML node:
<ShadowDOM>

    <MyComponent>

        hello, world

    </MyComponent>

</ShadowDOM>

source: gharchive/issue

authors: Wildhoney javadoug

repo: Wildhoney/ReactShadow

license: mit

license_type: permissive

license_source: bigquery


text:
[Snyk] Security upgrade @angular/cli from 15.2.10 to 17.0.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

frontend/package.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

823/1000  Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 8.6
Server-side Request Forgery (SSRF) SNYK-JS-IP-6240864
Yes
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: @angular/cli
    The new version differs by 250 commits.

f9527ce release: cut the v17.0.0 release
180dfa3 build: update Angular packages to version 17 stable
8bae6ad release: cut the v17.0.0-rc.5 release
8a9def5 test: add timeout to vite re-use cache
9d4d11c fix(@ angular-devkit/build-angular): allow SSR compilation to work with TS allowJs option
ec5e302 refactor(@ schematics/angular): add fallback fonts
3c6d2d8 refactor(@ schematics/angular): remove unused CSS
abb1c6f refactor(@ schematics/angular): use control flow to reduce code
81e4917 fix(@ angular/pwa): replace Angular logos
ecdcff2 fix(@ schematics/angular): add missing icons in ng-new template
569b714 build: lock file maintenance
303c98c fix(@ angular-devkit/build-angular): normalize exclude path
455aed8 Revert "test: temporary disable Jest E2E tests"
278bfa0 test(@ angular-devkit/build-angular): add test to validate vite cache re-usage
a8f041f release: cut the v17.0.0-rc.4 release
ae45c4a feat(@ schematics/angular): update `ng new` generated application
e10f49e fix(@ angular-devkit/build-angular): convert AOT compiler exceptions into diagnostics
1b38430 fix(@ angular-devkit/build-angular): disable parallel TS/NG compilation inside WebContainers
f87f22d fix(@ angular-devkit/build-angular): keep dependencies pre-bundling validate between builds
d46fb12 fix(@ angular-devkit/build-angular): disable dependency optimization for SSR
4733cd3 refactor(@ angular-devkit/build-angular): clean externalMetadata arrays on every rebuild
a02db0a refactor(@ angular-devkit/build-angular): allow JS transformer result reuse for application dev-server builder
323b005 build: update angular
59c22aa perf(@ angular-devkit/build-angular): start SSR dependencies optimization before the first request

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Server-side Request Forgery (SSRF)

Checkmarx One – Scan Summary & Details – 274ead7e-a2f8-4e2d-8cb8-aa4ad47da113
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

Cxab55612e-3a56
Npm-braces-3.0.2
Vulnerable Package

Cxab55612e-3a56
Npm-braces-2.3.2
Vulnerable Package

Cxca84a1c2-1f12
Npm-micromatch-4.0.5
Vulnerable Package

Cxca84a1c2-1f12
Npm-micromatch-3.1.10
Vulnerable Package

source: gharchive/pull-request

repo: WilfridBlanc/juice-shop

license: MIT

license_source: github-api


text:
Replace long HTTP request with websocket

I'm working on re-doing the client-server communication for letmein with WEBSOCKETS! I think it provides for much cleaner, more straightforward client JS and server Golang, and also allows the client and server to talk in a more "session-based" way, so it's easier to identify individual clients if I want to do neat tricks™

Oops. That last commit should have been three. It might be buggy. I need to go to bed.

Pretty sure that's it. Merging!


text:
add initial state of codereview pages

Adding pages for Code Review SE, starting with 2 pages

That second page could use a little more detail, but nice!

Okay thanks! Do I need to create an issue before the changes will be visible on the site?

Hey I still don't see the Code Review items listed... would you have any time soon to look at it? It would be nice to use this site for more than just SO...

Okay, so I figured out what the problem is... nothing got pulled into the repo because

WillSullivan merged commit 7b29360 into WillSullivan:idownloadedbecouse 27 days ago

idownloadedbecouse
I have no idea what's going on here. I don't have a repo called idownloadedbecouse. I got this repo, tho. If you want to submit a pull request to this repo we could get this done. But as it stands now,
dafuq.

Ah, I've figured it out. Okay, so you forked off some branch that I have no idea what's going on. I've nuked that branch. If you could fork from my master and then pick over your changes and submit another pull request? I've got no idea how all this got so screwed up :/

Ah yes - I merged my changes from that branch into master and submitted a new pull request #107

repo: WillSullivan/idownvotedbecause


text:
On confidence intervals and uncertainty intervals

Given that this is a Bayesian method, it is strange that the uncertainty is summarized using confidence intervals as opposed to Bayesian uncertainty/probability/credibility intervals via, for instance, HDIs and also taking the mean instead of the median as the point estimate. @WillianFuks, I am curious to hear your thoughts on what is in compile_posterior_inferences:
https://github.com/WillianFuks/tfcausalimpact/blob/master/causalimpact/inferences.py#L52
Having computed samples of the target time series, it should be straightforward to summarize them pointwise via, say, hdi in arviz.  Or do I miss something?

Hi @IvanUkhov ,
The intervals computed not only in this package but in the original R's already are the credible intervals. In fact, the original paper even compares confidence intervals with their credible ones at page 265 (or 19 in this pdf). Before latest paragraph, it says "The  latter  is  expected,  given  that  our intervals represent prediction intervals, not confidence intervals...".
What probably happened here is that throughout the code I wrote "confidence" instead of "credible" which is really a typo. The tensorflow_probability used in this package also returns credible intervals.
One point to consider though is that for this package I computed the lower and upper pointwise predictions using a similar approach as described by tfp comment referenced above, i.e., using z-scores with their means and stddevs whereas the original R package do so by selecting the proper percentiles via the posterior trajectory samples.
I'll see what happens by doing the same (I'm not expecting results to change much but it's probably worth the trial).
As for the mean vs median, as the model is built upon Kalman filters then posterior at each point t follows a normal distribution so it'd probably give the same results IIUC.

Thank you for the extended answer! Yes, I was referring to the logic based on a critical value and a standard deviation, which gives the right interval only if the underlying distribution is Gaussian. There is a lot of Gaussianity everywhere, but then the priors are non-Gaussian, which should lead to non-Gaussian posteriors in general. I suppose, if fitted via variational inference, the resulting posterior is indeed a product of independent Gaussian, but with MCMC, it is not the case. It seems to be an unnecessary assumption.
Please do not get be wrong. I am by no means criticizing. It is a great package, and I simply wanted to discuss to make it better.

Hi @IvanUkhov ,
Please feel free to ask as many questions as you like :)!
I think I better understand now what you mean. Notice that despite of which distribution we choose for the initial state model (in fact, default model of this package uses an inverse gamma for local level component) the probability of y` (prediction of observed time series) will always follow a normal distribution.
This is as per implementation of the LinearGaussian which holds for both Python and R packages. You can see that for TFP the probability of the state for time t is already a normal from samples taken from the chosen priors.
So extracting credible intervals either with z-scores or percentiles could be considered safe operations as it's guaranteed they'll be applied on Gaussians, regardless of the posterior of the state model we choose.

Hi @IvanUkhov ,
Newest version of tfcausalimpact is already publicly available. Any issues please let me know :)

Hello, thank you for the answers! I was hoping to get more answers before I share this, but my reasoning is as follows:
https://github.com/tensorflow/probability/issues/1252
What are your thoughts? Would you agree that the predictive distribution is non-Gaussian?

That's an interesting question, I'm not quite sure now what's the answer.
AFAIK, the predictive posterior follows something like (considering local level as an example):

(these equations were taken from Wei Yi's medium post).
So the predictive posterior should follow a normal from the posterior of the computed states. But then when we see in the tfp.sts.forecast code as you mentioned there's indeed the returning of the MixtureSameFamily which uses as input a previous state model already fitted with the posterior samples of the parameters. In the comments they state something like: "build a batch over state space models (...)" so I'm not sure if this is some technique to improve precision (just guessing).
I'm also awaiting (and hoping) the TFP team will give us some help here :)

The above formula is fo one particular assignment of the model parameters, and it is simply the Kalman filter. But from the inference, we get a full posterior for the parameters in the form of samples. For each sample, we get the above expression, and the final distribution is a mixture of these Gaussian ones. Recall what distinguishing structural time series from Bayesian structural time series. It is one extra component: Bayesian model averaging.
But again, this is just my interpretation. Yes, let us hope someone will answer in https://github.com/tensorflow/probability/issues/1252 🙂

Maybe  steve-the-bayesian can also help on this. He's the original creator of the R bsts package.

I have also asked on Stack Exchange:
https://stats.stackexchange.com/questions/512666/on-the-predictive-distribution-of-a-bayesian-structural-time-series-model

Here we have got an answer from the author of forecast:
https://github.com/tensorflow/probability/issues/1252
The conclusion is that the predictive distribution is non-Gaussian in general.

I ended up writing a custom function for summarizing inferences, as I wanted to have medians and HDIs instead of means and quantile intervals. I will leave it here in case it might be helpful some time in the future:
def _summarize_original(
    data_before: pd.DataFrame,
    data_after: pd.DataFrame,
    posterior: tp.distributions.Distribution,
    predictive: tp.distributions.Distribution,
    standardization: Tuple[float, float],
    alpha: float = 0.05,
    draw_count: int = 1000,
    random_state: int = 42,
) -> pd.DataFrame:
    from causalimpact.inferences import build_cum_index
    from causalimpact.misc import maybe_unstandardize

    def _hdi(data: np.ndarray) -> np.ndarray:
        from arviz.stats import hdi
        return np.array([hdi(data, 1 - alpha) for data in data.T]).T

    y_before = predictive.sample(draw_count, seed=random_state)
    y_before = maybe_unstandardize(y_before.numpy().ravel(), standardization)
    y_after = posterior.sample(draw_count, seed=random_state)
    y_after = maybe_unstandardize(y_after.numpy().ravel(), standardization)

    pre_preds_means = np.median(y_before, axis=0)
    pre_preds_lower, pre_preds_upper = _hdi(y_before)
    pre_preds_means = pd.Series(pre_preds_means, index=data_before.index)
    pre_preds_lower = pd.Series(pre_preds_lower, index=data_before.index)
    pre_preds_upper = pd.Series(pre_preds_upper, index=data_before.index)

    post_preds_means = np.median(y_after, axis=0)
    post_preds_lower, post_preds_upper = _hdi(y_after)
    post_preds_means = pd.Series(post_preds_means, index=data_after.index)
    post_preds_lower = pd.Series(post_preds_lower, index=data_after.index)
    post_preds_upper = pd.Series(post_preds_upper, index=data_after.index)

    complete_preds_means = pd.concat([pre_preds_means, post_preds_means])
    complete_preds_lower = pd.concat([pre_preds_lower, post_preds_lower])
    complete_preds_upper = pd.concat([pre_preds_upper, post_preds_upper])

    data = pd.concat([data_before, data_after])
    point_effects_means = data.iloc[:, 0] - complete_preds_means
    point_effects_upper = data.iloc[:, 0] - complete_preds_lower
    point_effects_lower = data.iloc[:, 0] - complete_preds_upper

    z_after = np.cumsum(data_after.iloc[:, 0].values - y_after, axis=1)
    post_cum_effects_means = np.median(z_after, axis=0)
    post_cum_effects_lower, post_cum_effects_upper = _hdi(z_after)
    index = build_cum_index(data_before.index, data_after.index)
    post_cum_effects_lower = pd.Series(
        np.concatenate([[0], post_cum_effects_lower]).ravel(),
        index=index,
    )
    post_cum_effects_means = pd.Series(
        np.concatenate([[0], post_cum_effects_means]).ravel(),
        index=index,
    )
    post_cum_effects_upper = pd.Series(
        np.concatenate([[0], post_cum_effects_upper]).ravel(),
        index=index,
    )

    data = dict(
        complete_preds_means=complete_preds_means,
        complete_preds_lower=complete_preds_lower,
        complete_preds_upper=complete_preds_upper,
        point_effects_means=point_effects_means,
        point_effects_lower=point_effects_lower,
        point_effects_upper=point_effects_upper,
        post_cum_effects_means=post_cum_effects_means,
        post_cum_effects_lower=post_cum_effects_lower,
        post_cum_effects_upper=post_cum_effects_upper,
    )
    return pd.DataFrame(data)

authors: IvanUkhov WillianFuks

repo: WillianFuks/tfcausalimpact


text:
Licensing

Hi, I can't see any license, could you set one? Without it, this is technically proprietary software with all rights reserved.

I added a MIT License in b084367, if anything looks wrong let me know!

Great!

authors: Wilnath libre-hackerman

repo: Wilnath/asetroot


text:
When I run python app.py, it keeps loading the log but it doesn't finish loading and can't do anything next

Hi @D-Mad ,
I've thoroughly tested the code on an alternate device and have indeed identified the peculiar phenomenon you mentioned. It's quite perplexing, given that the code runs seamlessly on my original device and HuggingFace. I'm inclined to attribute this anomaly to differing environments, possibly stemming from variations in package versions. Despite repeated attempts, I've been unable to pinpoint the precise trigger causing the 'stuck' issue.
As a temporary workaround, you can navigate around this problem by adjusting the Gradio version to '3.37.0'. Please be aware that this might entail sacrificing certain UI functions, such as the log display. Nonetheless, it should facilitate successful execution.
I hope this solution proves helpful, and kindly inform me if you come across any alternative, more effective resolutions for this issue.

authors: D-Mad WindVChen

repo: WindVChen/INR-Harmonization


text:
Python input formatter built into the compiler

Description
The addition of a built-in python code string formatter for the JMC.python module would allow users to have an arbitrary amount of indentation whitespace when coding python in a JMC file. This would prevent always needing to format the python code to align directly with the left-most column.
It should be noted that all subsequent indentation should still align with python's indentation protocol, but as long as each line is indented relative to the same uniform length, it should still work just fine.
Example of current implementation:

Example of desired implementation:

I've written up a mock-up example of how this formatting function could be written, although of course use your own discretion.
python_string = """
        a = 2
        def hello():
            print("Hello!")
            print("World!")
        hello()
"""

def indent_format(inp: str) -> str:
    _type = _minimum = None
    res = ""

    for ln in inp.splitlines():
        if not ln:
            continue

        _count = 0
        for i,c in enumerate(ln):
            if c == " " or c == "\t":
                _type = c if _type is None else _type
                if _type != c:
                    raise IndentationError("Mismatch use of spaces and tabs")
                _count += 1
            else:
                _minimum = _count if _minimum is None else _minimum
                if i < _minimum:
                    raise IndentationError("Left indentation not aligned properly")
                break

        res += ln[_minimum:] + "\n"

    return res

fmt_string = indent_format(python_string)

print("Unformatted code:")
print(python_string)

print("Formatted code:")
print(fmt_string)

print("Executing code:")
exec(fmt_string)

Implemented in https://github.com/WingedSeal/jmc/commit/037d50fe56368d493e2c260ed2b2018ee6cf5af4

    def clear_indent(self, string: str, indent: str) -> str:
        if not string:
            return string
        if string.startswith(indent):
            return string[len(indent):]
        raise JMCSyntaxException(
            "Invalid indentation when trimming indentation",
            self.raw_args["pythonCode"].token,
            self.tokenizer, suggestion=string, col_length=False, display_col_length=False)

    def call(self) -> str:
        if not self.args["pythonCode"]:
            return ""

        python_lines = self.args["pythonCode"].split("\n")
        indent = python_lines[0][:len(
            python_lines[0]) - len(python_lines[0].lstrip())]
        if not indent:
            python_code = self.args["pythonCode"]
        else:
            python_code = "\n".join(self.clear_indent(line, indent)
                                    for line in python_lines)

Ended up using different implementation

repo: WingedSeal/jmc


text:
🛑 Replit (Bot) is down

In 3a5c7fa, Replit (Bot) (https://replit.com/@WitherSkello/Minecraft-247-V2#README.md) was down:

HTTP code: 500
Response time: 27282 ms

Resolved: Replit (Bot) is back up in 6e011be after 14 minutes.

repo: WitherSkell/pingus


text:
[HELP] The localhost with the port does not work for me.

Hello, excuse my ignorance but I have tried to put the Alpha 3 in Docker-compose but it does not work for me, I would like to know if there is another way to install it, when installing it I enter with the port localhost:5690 but it does not enter, any help please, best regards.
CONTAINER ID   IMAGE                                  COMMAND                  CREATED              STATUS                          PORTS     NAMES
3af07d4d1a66   ghcr.io/wizarrrr/wizarr:v3-alpha-vue   "sh -c 'nginx && gun…"   About a minute ago   Exited (3) About a minute ago             agitated_banach

Could you get it to work?

Please use ghcr.io/wizarrrr/wizarr:v3-beta

Please use ghcr.io/wizarrrr/wizarr:v3-beta

2.6 GB? 💀

Wait I messed something, didn't I

We have had some issues with dialing in the right Github Actions Workflow for building out images, we are also trying to get image sizes down aswell

This is fixed in the latest ghcr.io/wizarrrr/wizarr:latest build

authors: DumberSoft ogkimra realashleybailey

repo: Wizarrrr/wizarr


text:
croc-hunter-jenkinsx to 0.0.136

Promote croc-hunter-jenkinsx to version 0.0.136

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

repo: Woap/environment-howlerglacier-staging


text:
cookie有刷新

cookies似乎有时间限制，当发送cookies给机器人群聊里已经绑定完米游社id和原神id，发送签到机器人提示签到失败，请检查Cookies是否失效。

点了退出登录Cookies会刷新

authors: RemKeeper chenshoyuan


text:
Wooting Double Movement Error

Everytime i try to download or start Wooting double movement i get this error: https://gyazo.com/10271442c5be3f969be0c6ec350a6979
I dont know whats caused it since wooting used to work but then out of nowhere it stopped working.

That's quite strange, maybe a reinstall of the ViGEmBus failed.
Have you tried downloading and installing it manually or following this troubleshooting guide relating to ViGEm install

Thanks so much, installing vigembus manually worked for me! thank you so
much!
Den sön 23 maj 2021 kl 21:54 skrev Simon W @.***>:

That's quite strange, maybe a reinstall of the ViGEmBus failed.
Have you tried downloading and installing it manually
https://github.com/ViGEm/ViGEmBus/releases/tag/setup-v1.17.333 or
following this troubleshooting guide
https://github.com/WootingKb/wooting-double-movement/wiki/Troubleshooting#-vigembus-failed-to-install---error-code-2503
relating to ViGEm install
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/WootingKb/wooting-double-movement/issues/21#issuecomment-846615752,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMUG5727RQG6WGY6LHWAC6DTPFMPXANCNFSM45L65Q4A
.

Glad it's sorted :+1:

authors: dynobeats simon-wh

repo: WootingKb/wooting-double-movement


text:
Split Vip.RestrictedFunctions Sniff into logical groups

Parts of the Vip.RestrictedFunctions Sniff could be highly re-usable in other sniff sets. This is currently not possible as all these function sniff are within one sniff file.
I'd suggest splitting this file into several sorted by group.
Initial grouping proposal:

PHPRestricted (ereg, eval and the like)
PHPDeprecated (ereg and the like)
PHPAlternativePreferred (create_function, curl, split and the like)
WPAlternativePreferred (parse_url and the like)
VIPAlternatives (all those which have wpcom_...() alternative functions)
WPCacheRestricted (get_pages, get_post_terms and the like)
BatcacheRestricted (cookies and the like)

Opinions ?

Closing as duplicate of #582 - seems we had the same idea at the same time ;-)


text:
WordPress.Security.ValidatedSanitizedInput.MissingUnslash does not accept stripslashes()

This is weird, but WordPress.Security.ValidatedSanitizedInput.MissingUnslash sniff accepts only stripslashes_deep (type-ignorant) or stripslashes_from_strings_only (type-ignorant) and does not accept the plain type-strict stripslashes.

but what if the type is not an array?

repo: WordPress/WordPress-Coding-Standards


text:
Incorrect styles on reporting form close button

Description

The content reporting form shows the incorrect button styles, with a pink background that should not be present.
Reproduction

Submit a mature content report.
Observe the incorrect button styles

Screenshots

I can't able to reproduce this issue.
https://www.awesomescreenshot.com/image/24991137?key=531cf1e9486250863294ffb82672770b

@HILAYTRIVEDI this change is not live in production yet, but can be seen in staging and locally.

authors: HILAYTRIVEDI zackkrida

repo: WordPress/openverse-frontend


text:
updates eslint ts-node and sass-loader

Fixes

Fixes #1086 by @krysal
Description

updates the dev dependencies ->
eslint
ts-node
sass-loader

Testing Instructions

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.
[x] I added or updated tests for the changes I made (if applicable).
[x] I added or updated documentation (if applicable).
[x] 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.

Hey I am not sure why the PLayright Tests , storybook build and next build is failing... can someone help me out ? thanks

@obulat I just reverted sass-loader back to the original version, getting this error now, should I update eslint as well ?

@kb-0311 , thank you for reverting sass-loader change.
ESlint upgrade is great! Could you please also update ESLint-related development dependencies?

getting some other ESLint error ... should I revert other oslint plugins back to their original version ?

Actually, those are good warnings that surface some incorrect code. I am going to add comments inline.

@obulat Thanks, that seems to resolve the linter errors but getting translation files error.
Should I run pnpm i18n:generate-pot and commit ?

Should I run pnpm i18n:generate-pot and commit ?

@kb-0311 that sounds excellent!

@zackkrida still getting the same error even after adding the POT file ... the problem is the date change or something ?

@zackkrida Thank you so much! I guess the problem with my pot file was with date creation and line changes.
Thanks again  :+1:

@obulat I think this is what was supposed to be done, right ?

should I go ahead and recommit the pot file and fix the linter issue ?

@obulat I recommitted the potfile and fixed the linter error please check...

Thank you so much for your contribution, @kb-0311 !
I've removed the unnecessary line so that the lint check is now passing.

@obulat There are still some playright errors and I don't know how to resolve them

Thanks a lot for your help @obulat @zackkrida !👍

authors: kb-0311 obulat zackkrida


text:
Fix authenticated logins for the label PR action

Description

Recent runs of the label_pr action were failing, but only against the infra repo with the following exception:
Traceback (most recent call last):
  File "/home/madison/git-a8c/openverse/automations/python/label_pr.py", line 104, in get_authenticated_html
    browser.form["otp"] = pyotp.TOTP(os.getenv("GH_2FA_SECRET")).now()
  File "/home/madison/.local/share/virtualenvs/python-d7ZGB4cT/lib/python3.10/site-packages/mechanize/_form_controls.py", line 1963, in __setitem__
    control = self.find_control(name)
  File "/home/madison/.local/share/virtualenvs/python-d7ZGB4cT/lib/python3.10/site-packages/mechanize/_form_controls.py", line 2355, in find_control
    return self._find_control(name, type, kind, id, label, predicate, nr)
  File "/home/madison/.local/share/virtualenvs/python-d7ZGB4cT/lib/python3.10/site-packages/mechanize/_form_controls.py", line 2448, in _find_control
    raise ControlNotFoundError("no control matching " + description)
mechanize._form_controls.ControlNotFoundError: no control matching name 'otp'

After doing some digging, it appears that this is because the OTP login form's input field name changed from otp to app_otp. I've added a more specific exception message for if this happens in the future:
Traceback (most recent call last):
  File "/home/madison/git-a8c/openverse/automations/python/label_pr.py", line 104, in get_authenticated_html
    browser.form["otp"] = pyotp.TOTP(os.getenv("GH_2FA_SECRET")).now()
  File "/home/madison/.local/share/virtualenvs/python-d7ZGB4cT/lib/python3.10/site-packages/mechanize/_form_controls.py", line 1963, in __setitem__
    control = self.find_control(name)
  File "/home/madison/.local/share/virtualenvs/python-d7ZGB4cT/lib/python3.10/site-packages/mechanize/_form_controls.py", line 2355, in find_control
    return self._find_control(name, type, kind, id, label, predicate, nr)
  File "/home/madison/.local/share/virtualenvs/python-d7ZGB4cT/lib/python3.10/site-packages/mechanize/_form_controls.py", line 2448, in _find_control
    raise ControlNotFoundError("no control matching " + description)
mechanize._form_controls.ControlNotFoundError: no control matching name 'otp'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/madison/git-a8c/openverse/automations/python/label_pr.py", line 206, in <module>
    main()
  File "/home/madison/git-a8c/openverse/automations/python/label_pr.py", line 182, in main
    linked_issues = get_linked_issues(pr.html_url)
  File "/home/madison/git-a8c/openverse/automations/python/label_pr.py", line 134, in get_linked_issues
    text = get_authenticated_html(url)
  File "/home/madison/git-a8c/openverse/automations/python/label_pr.py", line 108, in get_authenticated_html
    raise ValueError(
ValueError: Unable to locate form 'otp' on login page, perhaps its name has changed?

Testing Instructions

The new script has worked to successfully label https://github.com/WordPress/openverse-infrastructure/pull/375 !
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).
[x] I added or updated documentation (if applicable).
[x] 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.

Interesting, the lint is failing on an unrelated file 🤔 I'll try a rebase

That didn't address it 🤷🏼♀ Not sure how that got into main with lint failing but ah well.

repo: WordPress/openverse


text:
Set up deploy to ECS. Contributes to #46

Sets up deploy to ECS Cluster on commit to develop or master.
Will push to different clusters based on the branch.

@danielfdsilva Should be good to go. Change requests are addressed.


text:
Typo in ReadMe

New Issue Checklist

[x] Updated RangeSeekSlider to the latest version
[x] Checked Gitter

Issue Description
the example code in Carthage section:
@IBDesignable class CustomRangeSeekSlider: RangeSeedSlider {}
should be
@IBDesignable class CustomRangeSeekSlider: RangeSeekSlider {}

@aalenliang Thank you! I fixed it.

authors: WorldDownTown aalenliang

repo: WorldDownTown/RangeSeekSlider


text:
[Client] Unavailable server causes client to freeze

Expected Behavior
Connection would fail within reasonable time period then log it as an error and disable the plugin or something along these lines
Actual Behavior
Client is stuck in a connection loop and is unresponsive
Could be disruptive if server reboots happen unattended

This is fixed in new versions, thanks for your report.

repo: WorldQL/mammoth


text:
Aligned folders with the namespace used in the test classes

Moved classes to a folder matching the namespace used.
Fixed namespace for NameSpaceHandlerTest to match the location the file is located

I agree, the classes under test are in the WsdlToPhp\DomHandler namespace. The original namespace used in the test classes is wrong. Updated the branch and squash commits in the branch.

repo: WsdlToPhp/DomHandler


text:
Files still locked after dumping

Guess this has to do with the new update? Never had this issue before.
Talking about Forza Horizon 3 btw.

I noticed from hw2 that they still show the lock icon for files and folders act as if still locked but if you try copying the files from folder elsewhere to take a look, it probably works fine.

Some of the more recent updates should fix your issue. Be sure to download the latest build from AppVeyor

Getting this a couple times when I try to copy the folder

Fastest way around it is to tar then and move the tar elsewhere, as most likely the folder is taken over by NTFS inheritance / encryption

how do I tar?

I use 7zip

Getting this a couple times when I try to copy the folder
Fastest way around it is to tar then and move the tar elsewhere, as most likely the folder is taken over by NTFS inheritance / encryption

Oh yeah, just saying, if you for some reason can't use 7Z, then try copy-pasting the files. The folders don't work. But you have to do everything manually.

authors: Apollo-X Mask-Ninja RT-EB Scrxtchy Wunkolo umustbeloggedintododat

repo: Wunkolo/UWPDumper


text:
Recipe Confict Blood Magic

Rune of Dislocation and Rune of Augmented Capacity have the same recipe

This issue / recipes will be fixed within the next release of the modpack.

authors: Servovicis Wurmatron

repo: Wurmcraft/WurmTweaks


text:
Releases no longer available for AppVeyor deployement

 Issue by chrisofspades
Wednesday Mar 04, 2020 at 18:02 GMT
Originally opened as https://github.com/Wyamio/Wyam/issues/9

I'm using AppVeyor to deploy my site as described here:
https://wyam.io/docs/deployment/appveyor
And it's failing on the step to download the latest release. See log here:
https://ci.appveyor.com/project/chrisofspades/chrispeoples-com/builds/31172904
Looks like all releases/tags were removed from the repo. Any chance of bringing those back?

 Comment by daveaglick
Wednesday Mar 04, 2020 at 18:23 GMT

Looks like all releases/tags were removed from the repo. Any chance of bringing those back?

Yes, absolutely. It's on the top of my to-do list - hoping to get some time tonight to work on it. The releases was an unexpected goof-up on my part when I moved the original project to https://github.com/statiqdev/Statiq.Web. I transferred relevant issues back here but totally forgot about the releases. Shouldn't be too hard to write a little script to open them back up here where they should be and delete them over there.

 Comment by daveaglick
Thursday Mar 05, 2020 at 02:53 GMT

All releases have been moved back, sorry for the mixup!


text:
Legal Error

Okay - before you dismiss this issue saying it's not illegal, let me explain.
You decided to license someone else's code under The MIT License. Someone else's code. Not yours. You need to have legal binding authority to the code or at the very least this will get DMCA'd and your account suspended. You should probably remove the license.
Oh, and legally this is not legal advice
P.S. It's a really bad idea to decompile someone's game and put it on a public code repository.

The more and more I think about this the more and more I think you don't care.

repo: Wyliemaster/GD-Decompiled


text:
[Snyk] Upgrade gatsby from 5.11.0 to 5.13.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade gatsby from 5.11.0 to 5.13.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 25 versions ahead of your current version.
The recommended version was released a month ago, on 2023-12-22.

The recommended version fixes:

Severity
Issue
PriorityScore (*)
Exploit Maturity

Heap-based Buffer Overflow SNYK-JS-SHARP-5922108
694/1000  Why? Mature exploit, CVSS 9.6
Mature

Denial of Service (DoS) SNYK-JS-SOCKETIOPARSER-5596892
694/1000  Why? Mature exploit, CVSS 9.6
No Known Exploit

Denial of Service (DoS) SNYK-JS-GRAPHQL-5905181
694/1000  Why? Mature exploit, CVSS 9.6
Proof of Concept

Denial of Service (DoS) SNYK-JS-MSGPACKR-6140431
694/1000  Why? Mature exploit, CVSS 9.6
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Release notes

Package name: gatsby

5.13.1 - 2023-12-22gatsby-transformer-yaml@5.13.1

5.13.0 - 2023-12-18

5.13.0-next.3 - 2023-12-04

5.13.0-next.2 - 2023-11-16

5.13.0-next.1 - 2023-08-22

5.13.0-next.0 - 2023-07-25

5.13.0-alpha-fix-pnpm.21 - 2023-12-20

5.13.0-alpha-fix-pnpm.17 - 2023-12-15

5.13.0-alpha-fix-pnpm.16 - 2023-12-14

5.13.0-alpha-alt-image-cdn.38 - 2023-11-03

5.12.12 - 2023-12-07

5.12.11 - 2023-11-22

5.12.10 - 2023-11-21

5.12.9 - 2023-10-26

5.12.8 - 2023-10-20

5.12.7 - 2023-10-17

5.12.6 - 2023-10-09

5.12.5 - 2023-09-27

5.12.4 - 2023-09-05

5.12.3 - 2023-08-28

5.12.2 - 2023-08-28

5.12.1 - 2023-08-24

5.12.0 - 2023-08-24

5.12.0-next.1 - 2023-07-03

5.12.0-next.0 - 2023-06-15

5.11.0 - 2023-06-15

    from gatsby GitHub release notes

Commit messages

Package name: gatsby

366b54c chore(release): Publish
4b892c5 chore(gatsby-cli,gatsby-source-wordpress): bump clipboardy (#38775) (#38776)
2c0622c chore(release): Publish
5d6bb65 fix(docs): update remote url docs (#38768) (#38770)
18ffcfa chore(release): Publish
1953e5c fix(gatsby): allow gatsby-adapter-netlify@">=1.0.0 <=1.0.3" for gatsby@<5.12.10 (#38758)
4a780fb feat: image and file cdn url generator adapter implementation (#38685)
f8c207b chore: move gatsby-plugin-netlify-cms to deprecated-packages (#38755)
6d1d97e chore(gatsby-plugin-netlify-cms): add deprecation notice  (#38753)
7a7fa5f chore(deps): update dependency @ types/jscodeshift to ^0.11.11 for gatsby-codemods (#38595)
8919982 fix(deps): update dependency gatsby-plugin-webpack-bundle-analyser-v2 to ^1.1.32 (#38722)
d148295 chore(deps): update [dev] minor and patch dependencies for gatsby-cli (#38592)
37f2288 chore(deps): update dependency rimraf to ^5.0.5 (#38596)
0faf0fe chore(deps): update dependency rimraf to ^5.0.5 for gatsby-telemetry (#38597)
31272e9 chore(deps): update dependency rimraf to ^5.0.5 for gatsby-worker (#38598)
edcb035 chore(deps): update dependency start-server-and-test to ^2.0.3 (#38599)
956e30c chore(deps): update dependency wait-on to ^7.2.0 (#38724)
c1138ad chore(deps): update dependency fs-extra to ^11.2.0 (#38723)
aa60f1c chore(changelogs): update changelogs (#38749)
649a5a0 fix(deps): update starters and examples gatsby packages to ^5.12.12 (#38748)
268a640 chore: update gatsby-adapter-netlify version manifest (#38745)
5e8d2bb fix(deps): update starters and examples - gatsby (#38582)
0d7d6af chore(changelogs): update changelogs (#38743)
7f349ff chore(release): Publish next

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

👷 Deploy Preview for sage-dragon-9196d9 processing.

Name
Link

🔨 Latest commit
c39de3fccadf471dfdb0f7ca86aa749feb2d973c

🔍 Latest deploy log
https://app.netlify.com/sites/sage-dragon-9196d9/deploys/65b35e7acd2bef00080d9ca7

repo: X-oss-byte/gatsby-starter-minimal-ts


text:
Return on single detele

When we delete a single run, we should return from main()

Coverage increased (+0.03%) to 93.667% when pulling 9cbb10d5307e046ebc3dbf5b187169b4f4e1706e on ajax-return into 1c0e8695239194d91f8ad2fcdd23d5f0c0029419 on master.

authors: JoranAngevaare coveralls

repo: XENONnT/straxen


text:
Explicitly set infer_dtype=False for all Options

Due to a bug fixed in strax PR #569 many config options in straxen will now produce warnings. This PR suppresses these warning by explicitly setting the infer_dtype to False wherever the type of the config Option would have been inferred from the default value in the future.
This breaks backward compatibility with older strax versions since the infer_dtype keyword did not exist before, so not sure this is the best way to suppress these warnings. Maybe a better option would be to have a global setting in strax that suppresses them. Its open for discussion, but the PR is here in case we decide to use it.

Looks fine to me. We can updated the individual option whenever we change something else. I think for most of the int/float options you could also set it already to true. Btw I also noticed that you forgot to updated the doc-string here: https://github.com/AxFoundation/strax/blob/d23a605ab8171d89209aeb10f9d2f86b456a212e/strax/config.py#L66

@WenzDaniel Indeed you are correct! I also realized when adding the docstring that infer_dtype is a bit misleading and renamed it to infer_type in this draft. Until that is resolved, ill convert this to a draft.

Thanks @jmosbacher , let's merge sooner rather than later to prevent conflicts, I don't see any issue with this 👍

Any idea why it is just failing for this DAQReader option. I cannot spot the mistake.

@WenzDaniel I think the installation test is done with the latest version of strax and not master right? so wouldn't expect it to succeed

@jmosbacher maybe we should also do this on WFSim, the logs also contain quite a few warnings there.

Good point, ok ill take a look at the WFSim code

@jmosbacher we are also going to have some fun in cutax

@jmosbacher I'm merging this for now, although I still fill feel inclined to just not type-check options but I want to get a release out.

authors: JoranAngevaare WenzDaniel jmosbacher


text:
Weapon Scaling (Main and Off-hand) don't seem to work with C+

Body scaling works perfectly fine for me in C+, however when I try to scale the weapons of my character (Both Main and Off-hand), there seems to be no change in C+.
Specifically, I am trying to increase the size of the shield for PLDs by modifying these two bones in Anamnesis:
"Shield (Left)" bone (Unsheathed shield)
"Oh_n_hara" bone (Sheathed shield)
I also tried to modify the Mainhand weapon size (Just to check), but ran into the same problem

#84

authors: StoiaCode Syuqaa

repo: XIV-Tools/CustomizePlus


text:
feat: add support for Batch amendment

High Level Overview of Change
This PR:

Adds models for the Batch transactions
Updates definitions.json to handle the new field types
Adds support to the binary codec to properly sign multi-account Batch transactions
Adds helper functions for signing and combining multi-account Batch transactions
Adds support to autofill for filling in the BatchTxn and TxIDs fields
Adds support for Batchnet to the faucets
Fixes a side issue where multisigned transactions weren't properly autofilled

Context of Change
https://github.com/XRPLF/rippled/pull/5060
Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Refactor (non-breaking change that only restructures code)
[x] Tests (You added tests for code that already exists, or your new feature included in this PR)
[ ] Documentation Updates
[ ] Release

Did you update CHANGELOG.md?

[x] Yes
[ ] No, this change does not impact library users

Test Plan
Added tests for the new features.

Summary by CodeRabbit
Release Notes

New Features

Introduced support for batch transactions, including new transaction types and models.
Added functionality for ledger state fixes.
Enhanced spell-checking capabilities by recognizing the term "multisigned."

Bug Fixes

Improved transaction validation logic for batch transactions.

Tests

Expanded test coverage for batch transaction functionality and multisigned transactions.
Standardized naming conventions for test methods.

Documentation

Updated transaction type definitions to include new batch processing and ledger state fix types.

cc @dangell7 @tequdev

repo: XRPLF/xrpl-py

license: ISC


text:
should sites.js just be json?

it would make more sense, given the array of sites is the only thing it returns

As someone who has multiple tools hooked into the webring, I get what you're saying since they break every time this changes structure, or someone puts an entry in which is valid in JS, but not following the right pattern. It's also just data, so it's appropriate. However...
I think this was possibly discussed before somewhere on here, but I know it's an important value of @neauoire to keep this working locally with no build process, and also acting the same that it does live when running locally. Mainly meaning that switching this file to be JSON would sort of not work since there would either need to be some sort of build step to incorporate it, or we'd need to fetch it. There may be other ways to do this, but I'm not aware of how to do it, and I've tried. So, if there is a way to make this JSON without a build process or without having to fetch it, let's do it. However, if there isn't, then we are stuck with it just being an array.

just load json in a <script> tag 🤷♂
https://stackoverflow.com/a/7956249

ok, upon further investigation, <script src='sites.json' type='application/json'></script> did not work.
also, local fetch of a json file trows an error -- needs CORS on http(s) and refuses to handle file:/// for security concerns.

So I also did a bit of digging in this over the past couple days. There just isn't a good way to do this without hosting the file somewhere as you said. At that point, again, we are sort of getting away from the just cloning and running the ring. I'm going to assume @neauoire doesn't want to something to serve this separately, and I wouldn't even be in favor of doing that.
For now, I think we should just leave as is. I'll just update my parsers to accommodate the new format. I'll wait for @neauoire to confirm before closing the issue.

dont really see the point of keeping raw file:/// functionality here, since any action after loading the page will require internet connection, be that browsing portal or opening wiki or hallway :)
adding each .ndtl and twtxt file from sites list to appcache.manifest would be a probable solution, but that will be fairly tedious w/o git-hooks/github-actions/other kind of build process.

I've looked into this as well, we ought to keep this simple and stupid.
The webring will ever have a build step.

that's my point, there is no way to make/keep it "offline first" w/o crawling every peer while online.
so, by converting sites.js to json we are not really lose any offline capability, since there isn't any atm.

Will it require to spin localhost?

well, yes, but that can be done with a doube-clickable script file

authors: ckipp01 dym-sh neauoire

repo: XXIIVV/Webring


text:
Rename Observables to be in tune with PennyLane

Observables in PennyLane have been renamed to reflect changes in PennyLane:

MeanPhoton -> PhotonNumberOperator
Homodyne -> QuadOperator
NumberState -> FockStateProjector

These changes also have to implemented in PennyLane-SF.
See this issue on PennyLane.

Solved by #19

repo: XanaduAI/pennylane-sf


text:
Fix bundle signing (properly) & other build/CI improvements

This fixes the CI and my Cmake skills

I just noticed that sandboxing + the CLI options for input files don't work well together. I'll search a bit to see whether there is a proper way of solving this, but that's a bug related to this pull request at the moment I suppose.

@jelmervdl they can still use stdin/stdout. We can  write this in the limitation and if anyone wants files, they can do it through translatelocally-bin?

I've added a hint to the output when an error occurs that could have been caused by the sandbox. I've also mentioned it in the readme.
I didn't document how to compile on macOS yet in README because I couldn't easily figure out how to install Intel MKL? Has it been renamed or something? It should probably also note that if you want to make a version that can be shared, you should use Qt's own distribution, and not homebrew. You still need homebrew to get libarchive though 🤔

On MacOs we don't use MKL. We use apple accelerate framework by default when we detect MacOS, as it is installed practically everywhere.

authors: XapaJIaMnu jelmervdl

repo: XapaJIaMnu/translateLocally


text:
README.md的照片是pdimu的

Hello，It appears that the README.md in the docs contains an image that is not hosted by this repository. It should be moved in here. This repository should rely on itself:
## Screenshots 🪟
<img src="https://github.com/pdimu/pdimu/blob/main/image0_EN.png">

That image should not be used. It contains your username. @natsurainko should generate the image and put it in the docs. It is improper to use that image.

also @Lamparter i told natsuraink this on #252:

i might need to make another pr, as i moved the screenshot and the link there isn't correct
the link in the readme is https://github.com/pdimu/pdimu/blob/Fluent-Launcher/image0_EN.png which is the old location of the image. the right link is https://github.com/pdimu/pdimu/blob/main/image0_EN.png

Okay...?

so he technically knew that the image was somewhere else

did you check if you can upload files in docs?

That image should not be used. It contains your username. @natsurainko should generate the image and put it in the docs. It is improper to use that image.

You know I can create a new offline account and name it as xinxing2008 (natsurainko's mc username, but Microsoft account instead)? Then I take the screenshot and everything looks fine. But I think that if I took the screenshot I deserve to have my username on it, don't you think?

You know I can create a new offline account and name it as xinxing2008 (natsurainko's mc username, but Microsoft account instead)? Then I take the screenshot and everything looks fine. But I think that if I took the screenshot I deserve to have my username on it, don't you think?

No. Taking a screenshot is easy - doesn't mean you deserve credit. You already get credit by being in the contributors list! You should take a picture with a generic account name such as 'Steve' or 'Alex' and upload them to the repository using a fork. If you want help doing this feel free to contact me on discord! 😁

did you check if you can upload files in docs?

You can using a fork 😅

did you check if you can upload files in docs?

You can using a fork 😅

fr? damn how didn't i know

fixed

authors: Lamparter natsurainko pdimu


text:
新增 useMutationObserver 方法；修正 useResizeObserver 文档

[中文版模板 / Chinese template]
🤔 This is a ...

[x] New feature
[ ] Bug fix
[x] Site / documentation update
[ ] Demo update
[ ] TypeScript definition update
[ ] Bundle size optimization
[ ] Performance optimization
[ ] Enhancement feature
[ ] Internationalization
[ ] Refactoring
[ ] Code style optimization
[ ] Test Case
[ ] Branch merge
[ ] Other (about what?)

🔗 Related issue link

💡 Background and solution

📝 Changelog

Language
Changelog

🇺🇸 English

🇨🇳 Chinese

☑ Self Check before Merge
⚠ Please check all items below before review. ⚠

[x] Follow our Code of Conduct
[x] Read the Contributing Guidelines
[x] Read the docs
[x] Doc is updated/provided or not needed
[x] Demo is updated/provided or not needed
[x] TypeScript definition is updated/provided or not needed
[x] Changelog is provided or not needed

add new hook useMutationObserver
update useResizeObserver doc

repo: XiaoDaiGua-Ray/vue-hooks-plus