text:
Check that GGIR version in parallel processes is identical to GGIR version from machine that runs GGIR

In a project I am working on the GGIR version centrally installed by the admin of a computing cluster was different from the user installed GGIR version and when using parallel processing inside GGIR the parallel processes used the centrally GGIR version while the part of GGIR that does not run parallel used the user GGIR version.
Although we could argue that it is the user's responsibility to make sure that the correct GGIR version is available it may help to run a quick check prior to running GGIR in parallel and warn the user if there are any inconsistencies.
Proposal:

Add a short parallel process in GGIR.R prior to all the actual data processing which only compares the GGIR and R versions between central process and the parallel processes.

I have been exploring this today. If we add this chunk of code then all unit tests that do not specify do.parallel = FALSE will run it somehow testthat does not like this causing the test to fail without providing clear error messages that the cause is this additional bit of code.
I think this is too risky as we cannot always remember to turn do.parallel to FALSE inside a unit test. Implementing this inside each part would be a lot extra lines and duplicated testing for the same thing. So, my conclusion for now is that it is better to not do this and leave this up to the responsibility of the suer. They need to ensure that they export they library paths such that their user library is used.
Therefore, I am now closing this issue.


text:
bug: WebSocket connection failed for URL: wss://relay.walletconnect.com

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
0.12
Current Behavior
Latest wagmi update (0.12.0 - https://github.com/wagmi-dev/wagmi/releases/tag/wagmi%400.12.0) breaks WS on WalletConnect.
On 0.11 we have no problems.
When using any of the connectors of the wallets with WalletConnect () we are having these issues:

No issues on wagmi@0.11
We're not using wallet connect v1, as you might imagine.
Expected Behavior
Don't raise the error
Steps To Reproduce
No response
Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)
No response
Anything else?
No response

same here after update to latest

After upgrade I had the same error with WalletConnect v1 because of using the WalletConnectConnector. I fixed it and now both versions work correctly. My code:
import { WalletConnectConnector } from 'wagmi/connectors/walletConnect';
import { WalletConnectLegacyConnector } from 'wagmi/connectors/walletConnectLegacy';

const walletConnectV1 = new WalletConnectLegacyConnector({
  chains,
  options: {
    qrcode: true,
  },
});

const walletConnectV2 = new WalletConnectConnector({
  chains,
  options: {
    qrcode: true,
    projectId: process.env.REACT_APP_WALLETCONNECT_PROJECT_ID,
    name: 'My app',
    relayUrl: 'wss://relay.walletconnect.org'
  },
});

const client = createClient({
  autoConnect: true,
  provider,
  webSocketProvider,
  connectors: [walletConnectV1, walletConnectV2],
});

Hope this helps!

Yep, have a look at the migration guide for 0.12: https://wagmi.sh/react/migration-guide#012x-breaking-changes
If the error still occurs, please open a minimal reproducible example via https://new.wagmi.sh!

I started using wagmi from v0.12 and WalletConnectConnector() causes this issue.

source: gharchive/issue

authors: hiromaily jxom marsidorowicz maxaleks nfts2me

repo: wagmi-dev/wagmi

license: MIT

license_type: permissive

license_source: github-api


text:
Java deserialization vulnerability

Java deserialization vulnerability

Reviewed and approved

source: gharchive/pull-request

authors: CharlesRN DamoOne

repo: wagov/wasocshared


text:
Add receivers and publishers folder

I added a receivers and publishers folder replacing the adapters folder.
I also reorganized the static files and updated the docs.

Codecov Report

Merging #87 (b6c194c) into main (40f7890) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #87   +/-   ##
=======================================
  Coverage   98.79%   98.80%
=======================================
  Files          20       22    +2
  Lines         833      837    +4
  Branches       81       81
=======================================
+ Hits          823      827    +4
  Misses          5        5
  Partials        5        5

Impacted Files
Coverage Δ

src/wagtail_live/receivers/telegram/utils.py
100.00% <ø> (ø)

src/wagtail_live/publishers/base.py
100.00% <100.00%> (ø)

src/wagtail_live/publishers/polling.py
100.00% <100.00%> (ø)

src/wagtail_live/receivers/base.py
98.47% <100.00%> (ø)

src/wagtail_live/receivers/slack/__init__.py
100.00% <100.00%> (ø)

src/wagtail_live/receivers/slack/receivers.py
99.09% <100.00%> (ø)

src/wagtail_live/receivers/telegram/__init__.py
100.00% <100.00%> (ø)

src/wagtail_live/receivers/telegram/receivers.py
100.00% <100.00%> (ø)

src/wagtail_live/utils.py
95.83% <100.00%> (ø)

src/wagtail_live/webapp/receiver.py
100.00% <100.00%> (ø)

... and 2 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 40f7890...b6c194c. Read the comment docs.

authors: Tijani-Dia codecov-commenter

repo: wagtail/wagtail-live


text:
Fix nightly CI job

This job failed last night because, in https://github.com/wagtail/wagtail-newsletter/pull/21/files, I forgot to add mailchimp to the --extras list in nightly.yml:
https://github.com/wagtail/wagtail-newsletter/actions/runs/9105242838/job/25030492062

This got merged as part of https://github.com/wagtail/wagtail-newsletter/pull/29. I've opened https://github.com/wagtail/wagtail-newsletter/pull/30 to fix another issue with nightlies.

repo: wagtail/wagtail-newsletter


text:
Wagtail allows users to create accounts using the same email multiple times

Issue Summary
The found issue relates to the system allowing a user to register an account with an email that is already in use by another user.
Steps to Reproduce

Execute the docker script for wagtail development in https://github.com/wagtail/docker-wagtail-develop
Enter the admin interface
Click "Settings" and then click "Users"
Click "Add user"
Create two users with the same e-mail

This affects the functionality of recovering the password for a logged-out user since this functionality requires the email. If the option to create multiple accounts with the same email is intentional, then the login recovery should be done using the username, just like the login process. If the option to create multiple accounts with the same email is not intentional, then validation should be implemented in the email field, similar to the username field.

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: yes

Technical details

Python version: 3.8.19
Django version: 4.2.11
Wagtail version: 6.1a0
Browser version: Chrome 122

Working on this
I have thoughts on skills needed and I am keen to work on this myself once the issue has been accepted.
Anyone can contribute to this. View our contributing guidelines, add a comment to the issue once you’re ready to start.

Hi @Victor-oss - thanks for the report.
This is the standard out-of-the-box behaviour of the Django framework. If you want to use email rather than username as the unique identifier for a user, you can define a custom user model:
https://docs.djangoproject.com/en/5.0/topics/auth/customizing/#specifying-a-custom-user-model
https://docs.wagtail.org/en/stable/advanced_topics/customisation/custom_user_models.html#custom-user-models

authors: Victor-oss gasman

repo: wagtail/wagtail


text:
Migrating from ImageChooserBlock to ImageBlock fails

Issue Summary
While I don't think we explicitly documented it, replacing instances of ImageChooserBlock with ImageBlock in your own blocks should be as straightforward as just swapping the blocks in your own block definitions. No data migration is necessary, as there is some defensive coding in place to make this possible
While trialing Wagtail 6.3 release candidate 2 on the Wagtail.org codebase, I swapped a couple ImageChooserBlock with ImageBlock without a data migration as it should just work. See my branch: https://github.com/wagtail/wagtail.org/pull/478
I encountered a crash viewing the homepage though.
<snipped, for brevity>
  File "/Users/storm/projects/wagtail/wagtail.org/venv/lib/python3.13/site-packages/wagtail/blocks/stream_block.py", line 716, in _prefetch_blocks
    converted_values = child_block.bulk_to_python(raw_values.values())
  File "/Users/storm/projects/wagtail/wagtail.org/venv/lib/python3.13/site-packages/wagtail/blocks/struct_block.py", line 215, in bulk_to_python
    converted_values = child_block.bulk_to_python(raw_values)
  File "/Users/storm/projects/wagtail/wagtail.org/venv/lib/python3.13/site-packages/wagtail/images/blocks.py", line 173, in bulk_to_python
    struct_values = super().bulk_to_python(values)
  File "/Users/storm/projects/wagtail/wagtail.org/venv/lib/python3.13/site-packages/wagtail/blocks/struct_block.py", line 211, in bulk_to_python
    if name in val:
       ^^^^^^^^^^^
TypeError: argument of type 'NoneType' is not iterable

Here is some of the ImageBlock code referenced in the above stack trace
https://github.com/wagtail/wagtail/blob/f1ee2f5c73056095cdfb9b1a6c72f936619bbe8c/wagtail/images/blocks.py#L148-L175
Looking at the code paths referenced in above stack trace, we see we are skipping right past the defensive coding and it hitting super().bulk_to_python(values) which then tries and fails to do something with values.
Setting a breakpoint, I figured out values = [None] which really surprises me. This should be just None but somehow it is not? I am really not sure what the cause of this is, but I've seen it happen elsewhere in other client projects. I've always attributed it to weird migration issues and built defensive coding to work around it.
Reproducing
Check out https://github.com/wagtail/wagtail.org/pull/478 and pull a copy of the staging database
Suggested fix
I suggest changing the defensive coding to pick up on this weird condition as well. Unless there is a bigger picture issue I'm missing.
-if not values:
-    return []
+if not values or values[0] is None:
+    return []

Technical details

Python version: Python 3.13.0
Django version: 5.0.9
Wagtail version: 6.3rc2
Browser version: Firefox 131

cc @Chiemezuo

Thanks @Stormheg! Replicated on bakerydemo as follows:

Edit the ImageBlock in bakerydemo/base/blocks.py to have image = ImageChooserBlock(required=False)
Edit a blog page, add an image block with caption filled in but image left blank, and publish
Change image to a wagtail.images.blocks.ImageBlock:

from wagtail.images.blocks import ImageBlock as WagtailImageBlock

class ImageBlock(StructBlock):
    image = WagtailImageBlock(required=False)
    caption = CharBlock(required=False)
    attribution = CharBlock(required=False)

Revisit the edit view, receive TypeError: argument of type 'NoneType' is not iterable

Ha! Our bug hunt uncovered a bug. Thank you for chasing this down @Stormheg. And thank you @gasman for the quick fix suggestion.

Re the ability to directly replace ImageChooserBlock with ImageBlock not being documented - the sentence in the release note saying "This can be used as a direct replacement for ImageChooserBlock" was intended to communicate that. However, maybe that's being too subtle - it is a feature worth shouting about, after all :-)
Up to now I was inclined to avoid mentioning it in the main documentation for ImageBlock, as it's only relevant to people upgrading existing sites rather than learning about the block from the ground up - but again, maybe that's being too conservative. Will see what I can come up with, and I'm open to suggestions for how we can communicate this better.

Thanks for spotting this! @Stormheg
And thanks for fixing this! @gasman

@gasman It might bear repeating at least once in the ImageBlock section of the documentation. I feel like the sentence you had in the release notes was pretty clear but some folks might eagerly click away to read about the new block before the point sinks in.

Thanks all!

FWIW; we worked on upgrading Wagtail.org to 6.3 again yesterday during office hours and determined the issue isn't resolved with Matthew's fix.
The original reproduction instructions still give the same crash, as the fix does not handle the case where values = [None]. Which - for reasons I do not entirely understand - is the case for Wagtail.org's database.
We worked on a fix together, the result being #12571.
I'm going to reopen this, as the issue is not fixed.

authors: Chiemezuo Stormheg gasman vossisboss


text:
Update results.html

Close anchor tag.
Note though that the missing closing tag is inside a blocktrans!

Thanks @cho-leukeleu!
We should also add a ? after the closing tag, for consistency with other messages (e.g. https://github.com/wagtail/wagtail/blob/master/wagtail/wagtailimages/templates/wagtailimages/images/results.html).

Merged in d2baa4ba05acc92fff3369dbb8cb344ffdd7a70b - thanks!

authors: cho-leukeleu gasman


text:
Implemented facet() method on search results

This PR implements a facet() method on the SearchResults class for all search backends. It takes a field name and returns an ordered dict containing all the values used in that field with the number of results that contain each value (in descending order). This is useful for taxonomy filters on search pages.

Ignore that codecov stuff, this PR has good coverage. codecov doesn't run any of the Elasticsearch tests

By the way, I tested it manually on some of my projects, it appears to work flawlessly :)

Thanks for the review!

it could be great to have the possibility to facet against a foreign key instead of doing it against the foreign key ID

This is the same behaviour as Django's .aggregate() function. I think their reason for doing it this way was to avoid generating an extra hidden query.

authors: BertrandBordage kaedroho


text:
Apply correct pluralisation to minimap error count

Fixes #9497

4.1 stable 92f4796c8853834c5340325841ca40cb2970c228

authors: gasman lb-


text:
🛑 cyconet.org is down

In 3214cdb, cyconet.org (https://www.cyconet.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cyconet.org is back up in f1af4ec after 43 minutes.

repo: waja/cyconet-upptime


text:
EIP-3085: Wallet Add Ethereum Chain

Description

Add EIP-3085 addEthereumChain method

Heck yeah!

authors: Benjythebee fan-zhang-sv

repo: walletlink/walletlink


text:
Error:  Uncaught TypeError: Cannot read property 'tabIndex' of undefined

I downloaded the current version and installed in our AWS account.  I am testing the example and it doesn't display the transcript.
AWS - Example version v0.8.1 - 2017-04-21
The console shows the following error:
Uncaught TypeError: Cannot read property 'tabIndex' of undefined
at createLine (videojs-transcript.js:379)
at createTranscriptBody (videojs-transcript.js:406)
at videojs-transcript.js:401

I am experiencing the same problem here. Any update on this?

I think it is the problem with options. Just pass the options
var options = {};
var transcript = vjs.transcript(options);
Notice the options, this works for me.

This worked for me as well.
var options = {};
var transcript = this.transcript(options);

Where do I put these lines?

Where do I put these lines?

authors: HKAB eneiner ggmendez laiconsulting maricel0422

license: mit

license_source: bigquery


text:
texture2D functions and others aren't in spec anymore

the names are rather used as sampled image types in Vulkan

Can you be more specific?

authors: Super-Pizza walt-grace

repo: walt-grace/glsl-plugin-idea


text:
[Feature]: Add Direct Command Agent For Launch Just like the agent in sweeps doing.

Description
I recently encountered challenges while working with the mm-segmentation library, which necessitated running pip install -v -e . to install the source code as a development Python package. Consequently, explaining how to configure the Python environment in the Dockerfile proved complex. Additionally, I lack sudo access, preventing me from installing Docker on my server.
Currently, I'm utilizing sweeps to search for hyperparameters. I've observed that the agent in sweeps merely requires specifying the start command in the sweeps configuration file, which suits my situation well.
Is there a way to create a Queue with features like Launch, enabling me to use different hyperparameters to sequentially launch experiments? This would eliminate the need to wait and manually initiate the next experiment in some ablation studies.
Suggested Solution
I'd like the "Launch" feature to seamlessly utilize the existing Python environment and execute experiments sequentially,  configuring the start command within a specific location, enabling the use of different hyperparameters for each experiment. Furthermore, I want the flexibility to either specify which agent to run this process with or allow WandB to automatically select the most suitable option.
Alternatives
No response
Additional Context
If there is a feature already available that meets my requirements, please let me know. Thank you very much! 😃

I attempted to use Prefect for this task, but I found it challenging to use and it necessitated a Python script, rather than allowing for configuration directly through the Web UI.

Hi @steven12138, thank you for reaching out with your question. When you mention:

enabling me to use different hyperparameters to sequentially launch experiments

Are you trying to run sequential experiments testing different values for a number of hyperparameters, but rather than using one of the Sweep search methods, you would like to be able to select for each iteration of the experiment the values manually and have these running in a sequential manner?

Yeah, it's kind of that
Even more I just want the launch can use the similar settings as the sweeps function.
That means i can queue the difference experiment (even different code)

Hi @steven12138, as mentioned in our documentation Launch is a product designed to scale training runs to remote resources rather than running them locally. I will report your feedback to our engineering team about having the chance to launch jobs locally without having to use Docker for environments like yours where can't be installed.
My recommendation in your case would be:

Create the sweeps for each of the hyperparameter searches you have to run
Create the training function for each of the sweep
Have a script that loops through the sweeps id starting the sweeps for each task sequentially

I'd be happy to setup an example and provide the required code if needed.

Hi @steven12138, I wanted to follow up on this request. Please let us know if we can be of further assistance or if your issue has been resolved.

Hi @steven12138, as mentioned in our documentation Launch is a product designed to scale training runs to remote resources rather than running them locally. I will report your feedback to our engineering team about having the chance to launch jobs locally without having to use Docker for environments like yours where can't be installed.
My recommendation in your case would be:
* Create the sweeps for each of the hyperparameter searches you have to run

* Create the training function for each of the sweep

* Have a script that loops through the sweeps id starting the sweeps for each task sequentially

I'd be happy to setup an example and provide the required code if needed.

Genius! I really hadn't thought of that approach. Thank you so much for your help!

You are welcome 😄 - I will mark this as solved now but feel free to reach out in the future if you have any further questions or feedback!

repo: wandb/wandb


text:
There is a case that the loss becomes to Nan value

Hello
How are you?
Thanks for contributing to this project.
Have u ever tried to train a model with ONLY this loss?
In the case, I found a case that this loss becomes to Nan value.

ABL is used to supervise the boundary alignment rather than the classification accuracy. Thus, another loss (like CE) that ensures classification accuracy is necessary.
In our experiments, CE+lovász-softmax loss+ABL was the best combination, as the quantitative results of the paper show.
And the reason for introducing the lovász-softmax loss can be found in the last paragraph of Chapter Training Loss in the paper.

Thanks


text:
这个报错是什么问题呢

/home/fred/patch_ncmi_deb.sh: 第 32 行： cd: vlc-3*: 没有那个文件或目录
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|diff --git a/modules/access/http/resource.c b/modules/access/http/resource.c
|index 9a28bb50f3..4919cb3a05 100644
|--- a/modules/access/http/resource.c

+++ b/modules/access/http/resource.c

File to patch:

主要是deb-src没打开

license: WTFPL


text:
Bug in TCC

มีข้อผิดพลาดในการแบ่งกลุ่มคำ

fix in https://github.com/wannaphongcom/pythainlp/commit/856603103681ad0abcd014d9027d07f4b770e3a9

repo: wannaphongcom/pythainlp


text:
Default Language Route

Hi,
Everything works superb as URL based Lang Switch; But  If somebody access url without language,  we need to redirect always to english URL.
example.com/  =>  example.com/en - Not Working
example.com/about => example.com/en/about  -  Working
Where can change that Or Is it missed feature ?

you should be able to do this by setting $default_uri in MY_Lang

authors: sajumani waqleh


text:
:white_check_mark: add: tests for the methods to use cheerio

I added the test codes.
+if set the Links
+if set the imgs
+if set the body

Thank you.

repo: waricoma/email-to-slack


text:
First steps towards DB Connection

I've split this into many small commits :D
~I'm now stuck with handle_execute because Sqlite3 expects a SQL statement, but prepare returns a reference. Haven't looked into this yet.~ I finally figured it out in #3 🙄
I'm following myxql somewhat closely, but currently only implementing the most barebone functionality. Also see inline #TODO comments
I've tested what I have so far manually.

If you go take a look at #1 you'll see that I follow myxql closely, but I also pulled bits and pieces out of sqlite_ecto2. That PR is more just a big glob of changes as I try to understand and work through some of the decisions made in ecto_sql

authors: dmitriid warmwaffles

repo: warmwaffles/exqlite


text:
Add Rust workflow specs

Discord username (optional) please include so we can attribute you with our Contributor role (like so elvis#4747)
suttycups#2826
Description of changes (updated or new workflows)
New workflows for Rust-related development involving cargo and rustup, including but not limited to:

build/check/test
adding dependencies and installing binaries
generating docs
toolchain information, installation, updates, and overrides
configuring backtraces

@suttonbradley Thanks so much for doing this. Our team uses Rust as well and so these will also be directly helpful to us too.

@suttonbradley Friendly ping on these comments! We'd love to either merge this in or close it out if it's no longer relevant. Thanks!

authors: alokedesai elviskahoro suttonbradley

repo: warpdotdev/workflows


text:
[FEATURE] OTEL over NATS

OTEL Traces and Metrics over NATS
Can the NATS Connectivity used to encapsulate the transport of the OTEL trace and later metrics data?
It would be good to use the NATS lattice to forward the telemetry data regardless of the topology and
not rely on 1:1 HTTP connections.

Hi @hwinkel! So for many of the things inside of the wasmcloud host we use this crate to put the otel data in the NATS headers. However, we were planning on removing it from everything except for the NATS provider as we use a field in our Invocation type to send the trace data. Can you give me a little more info on your use case? If there are some good reasons why we shouldn't remove it, it would be great to know!

So we will likely be adding support back for otel NATS headers via our forthcoming wRPC work in #1128

@brooksmtownsend We can mark this as closed now, right?

repo: wasmCloud/wasmCloud


text:
Wdr 07 14

Description
WDR Changes:

Set dynamic text to a series like the SDI, since we weren't otherwise seeing the series showing up
Initialize the label for SDI correctly
Fix series loading being extremely slow. Code is left as a comment because it's a feature that could theoretically exist but needs more optimization to work.
Catch division by zero in RLCS
Disable mouse resizing plots, as it seems to be quite glitchy and we don't want to take risks
Calculate heater resistance correctly
Add rocket power field

Developer Testing

Here's what I did to test my changes:

Changes were validated at WDR and work. Not going to change it if it works.

Reviewer Testing

Here's what you should do to quickly validate my changes:

N/A

This change is

Disables resizing of plots, since it seemed to be causing some DAQ issues.

repo: waterloo-rocketry/omnibus


text:
Compile error

I use the gradle docker image to compile the application. The following are the error I got. Can anyone offer some help? Thanks.
[1] https://hub.docker.com/_/gradle/
angular2@2.0.0-beta.21 node_modules/angular2
:gulp_build
[18:45:01] Using gulpfile /conversation-with-discovery/gulpfile.js
[18:45:01] Starting 'build-ts'...
[18:45:01] Starting 'build-css'...
[18:45:01] Starting 'build-img'...
[18:45:01] Starting 'build-fonts'...
[18:45:01] Starting 'build-locale'...
[18:45:03] Finished 'build-locale' after 1.48 s
[18:45:03] css all files 33.7 kB
[18:45:03] Finished 'build-css' after 1.73 s

events.js:141
      throw er; // Unhandled 'error' event
      ^
Error: spawn /conversation-with-discovery/node_modules/gulp-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/vendor/gifsicle ENOENT
    at exports._errnoException (util.js:873:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
    at onErrorNT (internal/child_process.js:344:16)
    at nextTickCallbackWith2Args (node.js:442:9)
    at process._tickCallback (node.js:356:17)
:gulp_build FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':gulp_build'.
> Process 'command '/conversation-with-discovery/.gradle/nodejs/node-v4.4.7-linux-x64/bin/node'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

The build also failed using the official websphere liberty image [2]
[2]  https://hub.docker.com/_/websphere-liberty/
[19:18:10] Starting 'build-img'...
[19:18:10] Starting 'build-fonts'...
[19:18:10] Starting 'build-locale'...
[19:18:12] Finished 'build-locale' after 1.48 s
[19:18:12] css all files 33.7 kB
[19:18:12] Finished 'build-css' after 1.74 s

events.js:141
      throw er; // Unhandled 'error' event
      ^
Error: spawn /conversation-with-discovery/node_modules/gulp-imagemin/node_modules/imagemin/node_modules/imagemin-gifsicle/node_modules/gifsicle/vendor/gifsicle ENOENT
    at exports._errnoException (util.js:873:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
    at onErrorNT (internal/child_process.js:344:16)
    at nextTickCallbackWith2Args (node.js:442:9)
    at process._tickCallback (node.js:356:17)
:gulp_build FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':gulp_build'.
> Process 'command '/conversation-with-discovery/.gradle/nodejs/node-v4.4.7-linux-x64/bin/node'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 2 mins 19.993 secs

Not quite sure what your problem is here, can you clone or download and build localy

After applying this change , the program can be compiled with locally.

Okay great

authors: huikang stevenpkg


text:
Ox version says v0.11.2 but it is v0.11.3

When running ox version we get the following output:
ox version v0.11.2

Thanks @danoviedo91! Will patch this one on v0.11.4

Will be solved in v0.11.4, thanks @danoviedo91. Change has been merged now.

repo: wawandco/ox


text:
Sending SIGHUP twice to swhkd crashes with Failed to set init groups: EPERM

Version Information:

Linux arch-dktp-alexis 5.19.5-arch1-1 #1 SMP PREEMPT_DYNAMIC Mon, 29 Aug 2022 15:51:05 +0000 x86_64 GNU/Linux
swhkd 1.2.1 (installed from the swhkd-git AUR package)

Describe the bug:
Sending SIGHUP twice in a row crashes swhkd. It then outputs: Failed to set init groups: EPERM
Expected behavior:
Sending SIGHUP twice (i.e., reloading swhkd's config) should not cause the daemon to exit.
Actual behavior:
The first SIGHUP sent reloads the config as expected, the second one crashes the daemon.
To Reproduce:
Start swhkd. Send SIGHUP (sudo pkill -HUP swhkd), wait a bit, send SIGHUP again.
I have tried to wait for as long as 1 minute (just in case reloading the config lasted some time).
Additional information:
From what I can tell, this error is logged in the set_initgroups function: https://github.com/waycrate/swhkd/blob/d21e613d83a6049f3856a50d5f8eff8bcc29e91f/swhkd/src/perms.rs#L21-L30
I am not sure if this error happens in the call from the drop_privileges function or the raise_privileges function.
swhkd and swhks are usually started from my xinitrc:
swhks &
pkexec swhkd --config "$XDG_CONFIG_HOME/swhkd/swhkdrc" --device "USB-compliant keyboard" &

I have also tried to start swhkd from the tty, with a dummy config file and without specifying a device (just in case), but to no avail.

Hi, thank you so much for putting in the effort. This bug has been known for a while now ever since we developed the drop_priv function to patch a CVE.
I haven't gotten around to patching this yet but contributions are welcome! If you'd like more info on what's going wrong here, I'm more than happy to explain!

Thank you for your quick answer!
I have taken a look at it, and I think I understand what is happening: the first SIGHUP drops privileges, but swhkd never raises them again afterwards.
From my understanding and my testing, raising back privileges right after reading the config file is enough to fix the issue:
        match config::load(&config_file_path) {
            Err(e) => {
                log::error!("Config Error: {}", e);
                exit(1)
            }
            Ok(out) => {
                // Escalate back to the root user after reading the config file.
                perms::raise_privileges();
                out
            }
        }

From: https://github.com/waycrate/swhkd/blob/d21e613d83a6049f3856a50d5f8eff8bcc29e91f/swhkd/src/daemon.rs#L84-L90
Is there something I am missing here where this would be undesirable, especially regarding the CVE?
This passes tests run from make check on my end and also solves the issue. If this is fine with you, I can write a PR!

Awesome! Please go ahead and send a PR!
I didn't think this approach would work after dropping our privileges but oh well!
Here's the CVE if you're interested: https://www.cvedetails.com/cve/CVE-2022-27814/

authors: Shinyzenith ajanon

repo: waycrate/swhkd


text:
Fix Hyperlinks in README.md

The referenced links can’t be reached, since there are typo in the URLs.

Thanks for your contribution and thanks for fixing the doc issues!

authors: ptrstn waza-ari

repo: waza-ari/fastapi-keycloak-middleware


text:
Praise!

I use this all the time every single day of my work.
It is just a piece of software that does one job, and does it well.
Thank you for creating this piece of art.
https://github.com/wbolster/emacs-python-pytest#contributing mentions using the issue tracker for praise.

you're welcome. thanks for taking the time to send this! nice counterbalance to the ‘something does not work’ issues my projects usually receive 😄

authors: olavbm wbolster

repo: wbolster/emacs-python-pytest


text:
🛑 reader is down

In f31479b, reader (http://reader.wbsnpc.repl.co/#/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: reader is back up in e81065c.

repo: wbsnpc/upptime


text:
Fix: Permanently fixes #69 by forcefully shutting down hanging child process

I ran into the issues described in #69 and I found that none of the proposed solutions were working for me.
In order to reproduce the issue I made sure to trigger a change in my node_modules before my application had fully started up. This seemed to always result in the SIGTERM being swallowed by some other listener instead of properly shutting down the application. This results in ts-node-dev perpetually hanging.
The solution here is to simply send a SIGINT after a preset delay if the SIGTERM does not result in the application exiting on it's own.

This has definitely fixed the issue for us where it wouldn't restart if you made changes too quickly, thank you 🙇♀

@wclr could we get this bad boy merged in and deployed by any chance?

authors: m-abboud zanemcca

repo: wclr/ts-node-dev


text:
Metrics for Dynamo capacity

Part of https://github.com/weaveworks/monitoring/issues/12

This change is

Parametrized polling interval (and fixed a lint warning while I was there).
Leaving metrics as-is.

repo: weaveworks/cortex


text:
Auto updating failing memcached issue

I noticed that some of our new docker tags weren't pulled automatically like they should have been.
I didn't see any errors in the flux logs.
So I upgraded from 1.10.1 to 1.11.1 and no change.
Then I increased the memcached settings and restarted both:
      - name: memcached
        image: memcached:1.4.25
        imagePullPolicy: IfNotPresent
        args:
        - -m 256    # Maximum memory to use, in megabytes. 64MB is default.
        - -p 11211    # Default port, but being explicit is nice.
        - -I 10m

That made it work.
An error message would be really helpful! https://github.com/weaveworks/flux/issues/1720 is related, and having that SERVER_ERROR message was very helpful.

Thanks a lot for the report. We should increase the memory defaults of memcached (like you did)

If this is caused by memcached evicting entries (which is what it would normally do, to stay within the maximum memory), that will be tricky to detect -- an evicted entry just looks like it's expired. But fluxd should also cope, since it'll just fetch any missing entries again.
It's possible that there's a point where fluxd will seldom (or even never) be able to assemble a full set of images from memcached, because some are evicted before it has all of them. That might be a bit easier to detect, since fluxd will be able to see when things are repeatedly failing.

We've set it to 512MB in https://github.com/weaveworks/flux/pull/1900/commits/d3615f513ab44bfd8a098b61c0d8dee60edd769a

authors: 2opremio montyz squaremo stefanprodan

repo: weaveworks/flux


text:
Container view, detail panel, info table, ID & IMAGE ID fields contain truncated text as tooltip

Per https://github.com/weaveworks/scope/issues/1059.
The truncated text is not indicated with '...' and the tooltip is truncated text rather than untruncated text.
Same applies to the image id field.

The ID was truncated in the backend after it was agreed that we show container IDs in the same format as docker ps does.
Please reopen if new reasons exist why we should change this again.

For completeness: imageID render issues will be handled in #1058

The ID was truncated in the backend after it was agreed that we show container IDs in the same format as docker ps does.

What was the basis of the decision to have the field truncated in the tooltip? And where was that decision recorded? I have searched the issues and PRs but cannot find it. #924 and #930, which introduced this, don't even mention the truncation, let alone the rationale.

Please reopen if new reasons exist why we should change this again.

Unless there is a very good reason, whenever we truncate information, the complete information should be contained in the tooltip.
Btw, note that docker ps has a --no-trunc option.

What was the basis of the decision to have the field truncated in the tooltip? And where was that decision recorded?

There was no decision. The backend provides one value per field. The frontend renders that value, the browser provides the ellipsis if there is not enough space. The tooltip shows the same field value, but is not shortened by the browser because there is no space restriction.

Unless there is a very good reason, whenever we truncate information, the complete information should be contained in the tooltip.

It's been decided in the last scop sync to remove the backend truncation. Then the full value will appear in the backend again.

I know the commit/issue/pr where the truncation was introduced?

Anyone know the commit/issue/pr where the truncation was introduced?

See my comment above from a few months ago.

authors: davkal foot pidster rade

repo: weaveworks/scope


text:
Request for grouping by AWS attributes

e.g. group by availability zone.  Mentioned by a visitor to our DockerCon booth.

I think this would be an excellent idea for a plugin.
On Tuesday, 17 November 2015, Bryan Boreham notifications@github.com
wrote:

e.g. group by availability zone. Mentioned by a visitor to our DockerCon
booth.
—
Reply to this email directly or view it on GitHub
https://github.com/weaveworks/scope/issues/682.

Making post-1.0 along with all dsl and plugin work.

I am broadening this...

collect/show more AWS-specific info, such as AZ, VPCs, security groups. Add to details panel and make searchable
AWS-specific views/modes/toggles, e.g. grouping by AZ or VPC

authors: bboreham rade tomwilkie


text:
Generate documentation PRs against main

When the code and the docs were stored in separate repos, this would happen by default, as the release workflow would checkout the docs repo using its main branch, which the create-pull-request action would pull in as a default base. Now that we're running this workflow from a release tag (which has no concept of which branch it's on), we have to be explicit about where the documentation updates go.

From a previous failed release:
/usr/bin/git symbolic-ref HEAD --short
fatal: ref HEAD is not a symbolic ref
/usr/bin/git rev-parse HEAD
a809033e549154425170e935ab1c1d5e6d307490
Working base is commit 'a809033e549154425170e935ab1c1d5e6d307490'
Error: When the repository is checked out on a commit instead of a branch, the 'base' input must be supplied.

repo: weaveworks/weave-gitops


text:
web-animations-next-lite flicker

On specific versions of chrome stable (53.0.2785.x) we have noticed that some KeyframeEffect translateX transforms seem to be causing flickers at the end of each animation when something within the animating node is focused (PolymerElements/neon-animation#205).
example:

Interactive:
https://output.jsbin.com/denafe/1
We have been using web-animations-next-lite.min.js as the polyfill, but this is not reproducible using web-animations-next-lite.dev.js. I tried concatenating the files in the dev build and even minifying it, but was unable to reproduce it. I believe that there may be something gone awry in the build step.
This does not seem to be reproducible in Canary.

Based on the above, using dev or concatenating the files is probably forcing the polyfill to be used rather than falling back to the native implementation. We should probably refile this as a chromium bug and get a bisect, @alancutter.

@e111077 @dstockwell Can confirm, replaced direct usage of web-animations-next-lite.min.js with an include of web-animations-next-live-dev.html and all was well. This is a pretty kludgy workaround seeing as it would require me to localmod two different bower dependencies. So hopefully it gets resolved somewhat soon

This is definitely a Chrome bug rather than the polyfill.
Continuing investigation in: https://bugs.chromium.org/p/chromium/issues/detail?id=649195

BTW a workaround that doesn't involve using the dev polyfill would be to set Element.prototype.animate = null before you load the polyfill. This might save you having to mess with bower configs and restrict the workaround to the affected page.

authors: alancutter dstockwell e111077 shawncplus

repo: web-animations/web-animations-js


text:
perf: use mimalloc

Before:
┌────────┬────────────┐
│ Name   │ Time Spend │
├────────┼────────────┤
│ mdx-js │ 4,656ms    │
├────────┼────────────┤
│ mdx-rs │ 2,838ms    │
└────────┴────────────┘

After:
┌────────┬────────────┐
│ Name   │ Time Spend │
├────────┼────────────┤
│ mdx-js │ 4,564ms    │
├────────┼────────────┤
│ mdx-rs │ 1,887ms    │
└────────┴────────────┘

Thank you

repo: web-infra-dev/mdx-rs-binding


text:
[Bug]: monorepo 项目中使用 pnpm 代码检查 eslint 无法正确工作

版本信息
System:
    OS: macOS 13.4.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 3.96 GB / 64.00 GB
    Shell: 5.9 - /bin/zsh
  Browsers:
    Chrome: 114.0.5735.198
    Edge: 114.0.1823.67
    Safari: 16.5.1
  npmPackages:
    @modern-js/eslint-config: 2.25.1 => 2.25.1
    @modern-js/monorepo-tools: 2.25.1 => 2.25.1
    @modern-js/plugin-garfish: 2.25.1 => 2.25.1
    @modern-js/tsconfig: 2.25.1 => 2.25.1

问题详情
pnpm 并不会在当前 workspace root 下依赖 eslint 的 cli
如果手动通过 pnpm add eslint -w -D 则 webstorm 会提示 eslint 无法加载 eslint-plugin-import 插件。

root 下并未依赖 eslint

lint-staged 读取了 node_modules/eslint 中的内容

如果手动添加 pnpm add eslint -D -w 则通过 webstorm 打开应用会出现 eslint-plugin-import 不存在。
复现链接
https://github.com/StringKe/modern-monorepo-eslint-error
复现步骤
提交任意 git 触发 husky 即可

我看了下是另一个报错，这里报错信息是找不到 typescript，因为 ESLint 里有一些 typescript 相关的规则。

提了一个修复 PR，添加 typescript 和 tsconfig.json，你可以参考下
https://github.com/StringKe/modern-monorepo-eslint-error/pull/1

你能截图一下你 node_modules 文件夹么？

我用的 pnpm v8

I will close this issue because it is no longer active, feel free to reopen it if you have any further questions.

authors: StringKe chenjiahan


text:
support AMD module format

What problem does this feature solve?

#2787

What does the proposed API of configuration look like?
https://webpack.js.org/configuration/other-options/#amd

I see that it has already been supported.

Nope, I mean analyze dependencies from an AMD module and bundle its dependencies, for now Rspack only support output an AMD format library if I remember correctly

用systemJs应该都会遇到这个问题，因为systemJs要求引入umd模块必须提前引入amd extra来提供amd环境

I would like to contribute. May I try this?

Hi, I have started working on this issue last weekend. After some research I realised the change is much bigger than I expected. I feel we'd better break it down into 3 stages. Smaller PRs are also easier to review. My plan is to

add AMD dependencies
implement AMD plugin and integrate with bundler
add test cases to verify and fix bugs

So far I have finished stage 1, I will create a draft PR. We can discuss the implementation there.
I will use my branch as feature branch for stage 2 and stage 3.

Great to hear that someone is into that @nilptr That's basically the only thing that's missing and messing the hustle free switch from webpack. We have a bunch of jquery-ui imports that don't work out of the box. Do you know how to fix it before you implement this?

Is this the place to report AMD issues or should I open a new issue?
I'm struggling with Rspack output regarding an AMD build breaking at runtime because of Rspack including the umd wrapper from a dependency:
"../../../../../node_modules/json-logic-js/logic.js": (function (module) {
 /* globals define,module */
 /*
 Using a Universal Module Loader that should be browser, require, and AMD friendly
 http://ricostacruz.com/cheatsheets/umdjs.html
 */
 ;(function(root, factory) {
   if (typeof define === "function" && define.amd) {
     define(factory);
   } else if (true) {
     module.exports = factory();
   } else {}
 }(this, function() {
   "use strict";
   /* globals console:false */
// ... module code

Where as webpack output contains this instead (which doesn't use the global define function):
  /***/ "../../../../../node_modules/json-logic-js/logic.js":
  /*!**********************************************************!*\
    !*** ../../../../../node_modules/json-logic-js/logic.js ***!
    \**********************************************************/
  /***/ (function(module, exports, __webpack_require__) {

  var __WEBPACK_AMD_DEFINE_FACTORY__, __WEBPACK_AMD_DEFINE_RESULT__;/* globals define,module */
  /*
  Using a Universal Module Loader that should be browser, require, and AMD friendly
  http://ricostacruz.com/cheatsheets/umdjs.html
  */
  ;(function(root, factory) {
    if (true) {
      !(__WEBPACK_AMD_DEFINE_FACTORY__ = (factory),
      __WEBPACK_AMD_DEFINE_RESULT__ = (typeof __WEBPACK_AMD_DEFINE_FACTORY__ === 'function' ?
      (__WEBPACK_AMD_DEFINE_FACTORY__.call(exports, __webpack_require__, exports, module)) :
      __WEBPACK_AMD_DEFINE_FACTORY__),
      __WEBPACK_AMD_DEFINE_RESULT__ !== undefined && (module.exports = __WEBPACK_AMD_DEFINE_RESULT__));
    } else {}
  }(this, function() {
    "use strict";
    /* globals console:false */

The bundle is built with output.library.type = 'amd' but the environment the bundle is loaded in uses SystemJS and it's AMD extra. As the rspack output uses global define() this breaks as SystemJS creates a System.Register module under the hood which results in the json-logic-js module being empty.

This is the place, we already have contributor working on AMD format support

authors: ahabhgk jackw nilptr olhapi shaodahong sunft1996

repo: web-infra-dev/rspack


text:
fix some comments

Summary

Require Documentation?

[x] No
[ ] Yes, the corresponding rspack-website PR is __

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

authors: CLAassistant hishope


text:
docs: improve externals plugin doc

Summary

Fix #7006
Checklist

[ ] Tests updated (or not required).
[ ] Documentation updated (or not required).

Nice 👍

authors: SyMind chenjiahan


text:
perf!: use browserslist-rs for lightningcss

Summary
use browserslist-rs instead of browserslist on js side, so that we can gain slightly more initial setup performance
breaking change
not supports browserslist as parameters now

Checklist

[ ] Tests updated (or not required).
[ ] Documentation updated (or not required).

Note: This is a breaking change (targets?: Targets | string[] | string -> string[] | string)
But I think nobody uses the Targets type, which depends on installing the lightningcss package and makes no sense.

authors: JSerFeng chenjiahan


text:
Restrict total label count to satisfy new limit

Duplicate of https://github.com/web-platform-tests/wpt-pr-bot/pull/37 with branch rebased and in this repo.

Merged via gh-37

authors: foolip jugglinmike

repo: web-platform-tests/wpt-pr-bot


text:
GMP extension in AWS Elastic Beanstalk

Is there an alternative to GMP extension for this library to use? I cannot find a way to install it on an Elastic Beanstalk instance in AWS.

Hello,
You could try to polyfill it? That's not the scope of this library though ;)

Closing this. Please follow-up if you found a way to solve your problem, it might help others!

authors: Minishlink jorgerenteral

repo: web-push-libs/web-push-php


text:
Webpush encryption draft changes

Hello @Minishlink,
I don't know if you have seen the new draft from yesterday, but to me it seems like it modified some things which could require changes in the web-push-php lib: https://www.ietf.org/rfcdiff?url2=draft-ietf-webpush-encryption-05
Thanks for your work :)

Newest draft is https://tools.ietf.org/html/draft-ietf-webpush-encryption-08
@jrconlin @gauntface Are there any deadlines for Firefox or Chrome?

It's best to consider that your target may be running older versions. There are still quite a few installs of older firefox out there even though we do our best to make sure folks upgrade.
Mozilla is a bit "resource constrained" at the moment, and we've not yet implemented "aes128gcm" draft for desktop.

Ok, thanks! I guess the endpoint versions will change when the "aes128gcm" content coding is implemented?

Probably not, since the push service doesn't do the decryption. It passes the information through opaquely. More than likely, there would be some bit of information passed along via the User Agent registration call.
I've proposed a modification to the working group to get buy in. (It's a good idea so that various vendors standardize on something.)
https://mailarchive.ietf.org/arch/msg/webpush/uDR2PzpChfn24TwNWZBfR6fuKp0
thanks!

I see, thanks for the info :)

Available in v4.0.0 :)

authors: Minishlink PascalReintjens jrconlin


text:
App: add error placeholder

When an object fails to load in the world, we should replace it with some sort of error-indicating model. This should probably be something like a red X or some error text.
The error object should also have some sort of grabbable physics so you can delete the bad object.

Avaer have implemented Error placeholder and it is merged.

authors: avaer skaljac

repo: webaverse/app


text:
Filter option for bridge tables and UI fixes

Summary of changes

Adds error notification when an invalid notes is pasted
Updates amount selector UI changes in bridge
Updates chains ring component text size
Adds filter option to available spend notes and shielded assets table
Adds token amount format function to show token amount with 2 decimal places if the value is greater than 0.001

Proposed area of change

[x] apps/bridge-dapp
[ ] apps/stats-dapp
[ ] apps/webbsite
[ ] libs/webb-ui-components

Reference issue to close (if applicable)

Closes #993
Closes #982
Closes #981
Closes #947
Closes #725

Screen Recording
1. Error notification paste notes
https://user-images.githubusercontent.com/53374218/218415566-6d6563b2-dafa-479b-82ed-2b499cadf56b.mov
2. Amount selector and utility buttons bg and size update
https://user-images.githubusercontent.com/53374218/218416311-86fd2003-43fe-4e05-b114-97e23c092cff.mov
3. Chains ring component text size

4. Filter option
https://user-images.githubusercontent.com/53374218/218417600-ae05b1fc-6af0-43bf-9f07-23e85dfd86b2.mov
5. Token amount format

Code Checklist

[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)

The dapp still crashes when uploading the tamp note @devpavan04 😢

Here is the note that crashes the dapp (with double quotes)

"webb://v1:vanchor/1099511632779:1099511632778/0x6595b34ED0a270B10a586FC1EA22030A95386f1e:0x91eB86019FD8D7c5a9E31143D422850A13F670A3/000001000000138a:00000000000000008ac7230489e80000:2d6509c767408462b88dfe93d684aae1e546974e9e2cf7f4fa0d41bbe32e001c:009ee5c31e25ed5d085abdf9b866843b2bcde2fd967122b881ca39c91e2a9744/?curve=Bn254&width=5&exp=5&hf=Poseidon&backend=Circom&token=webbDEV&denom=18&amount=10000000000000000000"

https://user-images.githubusercontent.com/60747384/218768413-5d162a97-5194-4d05-a5f3-2ba8077fddb4.mp4

@AtelyPham @dutterbutter Paste note issue was resolved with this approach:
User can now paste raw note with or without the quotes(single/double) as they will be removed from the string before doing any further calculations. Any thoughts?
<FileUploadList title="Paste spend notes below:">
        {Object.entries(rawNotes).map(([id, note]) => (
          <FileUploadField
            key={id}
            value={note}
            onChange={(value) => {
              setRawNotes((prev) => ({
                ...prev,
                [id]: value.replace(/['"“”‘]/g, ''), // Remove quotes from the string
              }));
            }}
            onUpload={() => handleUpload(id)}
          />
        ))}
</FileUploadList>

@devpavan04 Instead of only checking the quotes, we can write a regex to check a valid note (e.g. only containing the alphanumeric values, &, :, ...etc, etc). Let me know if you still need help creating the regex.
cc: @dutterbutter

@AtelyPham @dutterbutter
https://user-images.githubusercontent.com/53374218/219414417-e87b2250-8a7d-42d6-b383-d3ad3a8c8342.mov

repo: webb-tools/webb-dapp


text:
Setup Statistic Page as separate react app

Summary of changes

Move the tailwind config to root to sharable between repos
Setup separate react app for page-statistics
Setup the Keys page for the demo

Reference issue to close (if applicable)

Closes

Code Checklist

[x] Tested
[x] Documented

Screenshot
https://user-images.githubusercontent.com/60747384/189996825-b620277c-f073-4790-9070-d6f5bada0f7f.mp4

Once this PR is merged, we ready to merge the webb-ui-kit into develop, then continue the work on the statistic page on the develop branch.

It's http://localhost:3000 with our mixer @AhmedKorim. And please use yarn start:stats instead of yarn start:localDapp.

Can we have this in the readme?

Ok, let me update the README as well 👍

This works for me it seems the issue was in my setup, Great job @AtelyPham

authors: AhmedKorim AtelyPham


text:
IL2CPP support for Standalone

Describe the solution you'd like
I would like to be able to build my project with IL2CPP
And you could also add an option to delete the _BackUpThisFolder_ButDontShipItWithYourGame folder.
Describe alternatives you've considered
I went back to a Mono build
Additional context
With / Without IL2CPP

This will need to be supported in the docker images. Here's a related issue:
https://gitlab.com/gableroux/unity3d/-/issues/66

@knxrb With they, you mean the person you're talking to above? 😄
Anyway, the linked issue seems to be clear and the last comment indicates it's working.
I guess the next step is for Unity Builder to allow for a parameter that allows selecting il2cpp images. Probably the image functionality has to be extended for this. Anyone is free to send a PR with the required changes.

Oh yeah >.< I didn't notice that it's the same guy for the images. I've only just started looking at and using these actions this afternoon.
I'll have a look at what's needed for this tomorrow and see if I can get it working.
Thanks for the info :+1:

@webbertakken I've had a quick look at this and from what I understand: this can't be done yet as there's only linux IL2CPP images?
The image suffix is being set to windows when building StandaloneLinux64:
https://github.com/webbertakken/unity-builder/blob/master/src/model/image-tag.js#L54

Linux support for IL2CPP should work out of the box, same for Android and iOS builds, whereas macOs and Windows will require these platforms to be used in the base image. This is currently not planned but a welcome addition to the repo that holds the docker images here.

authors: 06Games GabLeRoux knxrb webbertakken

repo: webbertakken/unity-actions


text:
[IE] Support 'roundingType' and 'outputSizes' options for pool2d operations

Align to latest change of pool2d operations: https://github.com/webmachinelearning/webnn/pull/208

Fixed by #185

authors: BruceDai mingmingtasd

repo: webmachinelearning/webnn-native


text:
[BUG] Notice: Trying to get property of non-object in Utils/ASTDefinitionBuilder.php on line 421

I am using the graphql schema files to define my types, etc. Using the Parser::parse/AST::toArray to convert the schema files. However the comments give me a PHP notice in as of version 0.12
Notice: Trying to get property of non-object in Utils/ASTDefinitionBuilder.php on line 421
The node description is a string not an Object (Line 421):
if ($node->description) {
     return $node->description->value;
}

Can you add more info how to reproduce the issue? Just run tests and there always is StringValueNode. Some examples:

@simPod Sorry, found it. I was using a cached AST from 0.11, so with a 0.12 AST it works 👍🏻

FYI, I added a note in UPGRADE.md for 0.11 -> 0.12 upgrade about AST cache incompatibility. Thanks for brining this up!

authors: simPod steffans vladar

repo: webonyx/graphql-php


text:
Weird result using  in HTML

Hi,
while using your loader, I am struggling with weird issue, which prevents me from using it.
I am using Webpack v.2.2.1.
In HTML I've got:

And after compiling and bundling, using your loader, it ends up like this:

<path d="M1611 832q0 53-37 90l-651 652q-39 37-91 37-53 0-90-37l-651-652q-38-36-38-90 0-53 38-91l74-75q39-37 91-37 53 0 90 37l294 294v-704q0-52 38-90t90-38h128q52 0 90 38t38 90v704l294-294q37-37 90-37 52 0 91 37l75 75q37 39 37 91z"></path>
" alt="test_svg">

And in my webpack config, options for this plugin:
{
  loader: 'svg-inline-loader',
  options: {
    mimetype: 'image/svg+xml',
    removeTags: false,
    removingTags: ['title', 'desc', 'defs', 'style'],
    removeSVGTagAttrs: false,
    removingTagAttrs: [],
    classPrefix: 'icon',
    idPrefix: 'icon-[name]',
  },
},

Edit. Close. I understood the purpose of this loader wrongly. Sorry about that.

@xeho91 I'm trying to achieve what you were trying, how did you solve your issue?

repo: webpack-contrib/svg-inline-loader


text:
New source entries in Firefox Developer Tools after each HMR trigger

Operating System: Windows 10 x64 1809
Node Version: 10.14.1
NPM Version: 6.4.1
webpack Version: 4.27.1
${package} Version: 2.24.3
Firefox Version: 64.0

Expected Behavior
Single client.js entry in Firefox Developer Tools. It is single in Chrome.
Actual Behavior
Multiple client.js entries are present in Firefox Developer Tools:

Code
From this repo's example.
Question for Dev
Is this Firefox issue or is there something in the webpack.config.js that can be changed to resolve it? It is difficult to debug otherwise, since Firefox remembers breakpoints for the specific "version" of the file / hot update.

I think this might be a firefox issue, or possibly even a firefox issue caused by a workaround for an old chrome issue!
Either way, it's related to the core of webpack's source map generation, so not an issue with this module.
You'll need to raise this issue with firefox and/or https://github.com/webpack/webpack/ as a problem with the source map updating during hot reloading.

@glenjamin Will do, thank you.
As a side note, changing to devtool: "eval" (good for development, not for production) works as expected even in Firefox.

I'd have thought devtool: eval would leave you with no source maps?

You are correct. I had old source maps on the disk!

authors: glenjamin vladeck

repo: webpack-contrib/webpack-hot-middleware


text:
[tba] Add Documentation for migrating to webpack-cli v.4

Feature to document
Webpack-CLI v.4

Author(s)
Even Stensberg, N/A
Additional information
We are releasing a new version of webpack-cli soon, which will mean that some sections of the docs would need to be updated. I'd like to point this out to the documentation team so that you are ready for the change.
At first, the only thing that is needed is to add a how to migrate post at the docs site, which will help users upgrading to the newest cli version. This is because we are removing a lot of flags and it might cause confusion.
Later (Maybe after 2months of LTS), we will gracefully start to migrate the CLI options section to reflect the new CLI.
My proposal is to have 2 posts, one with the old CLI version, one with the new. When webpack 5 is released, we will remove or depreciate those docs and replace it with the new CLI documentation.
I'd like feedback on this to avoid a mass amount of traffic for people asking questions. What would be the best approach?
I'll write the migration post/site, but feedback is good for syncing as well as we know that we aren't making a lot of people angry.

We are releasing an alpha in the end of the year, beta maybe in mid-January and v.4 in february/march

webpack 5 specific docs are now living in next branch, the things you want people to migrate should go to migration guide of webpack 5. i really wouldn't wanna see different migration guides for webpack and its cli, thats one tool, having cli in separate repository shouldn't add complexity for users imo.
@sokra thoughts?

I think different migration guides for core and cli made sense, since you can migrate individually. Made even recommend to migrate one at a time.

how much content do you think that would be in cli migration @evenstensberg ?

My main concern is that user dont usually care about implementation details, and finding two+ migration guides to up v4 to v5 of webpack might trigger some negative tweets and comments (again)

if CLI update come out with breaking changes before webpack v5, that would have no negative impact imo. So that users would migrate to new CLI and later that year to webpack v5 when it comes out

@EugeneHlushko one page perhaps, not that much

I'm suggesting this:
- webpack-CLI 4
    - overview
    - flags
        -a
        -b
    - commands
        -a
        -b
    - how to migrate
    - summary

authors: EugeneHlushko evenstensberg sokra


text:
docs(config) improve documentation about [contenthash]

add contenthash to the table
fixes #3209

Thanks!

authors: EugeneHlushko montogeek


text:
docs(format) single quotes in js spotted, minor grammar

While reviewing recent PR i spotted mis- formatting on api pages, just cleared the occurrences and found another grammar improvement

can we add .vscode config to work with eslint and prettier and remove it from .gitignore ?

can we add .vscode config to work with eslint and prettier and remove it from .gitignore ?

I don't think that's a good idea given not everyone uses the same lint/format config. Having a single config in the project should be sufficient.

I don't think that's a good idea given not everyone uses the same lint/format config. Having a single config in the project should be sufficient.

I think vscode wont look for global config if .vscode is present in the project. so in that way, we all will be using same vscode config and wont get formatting issues.
just that we need to configure prettier well with linters in the project config,

Yes linter should've caught this but its tricky in .md and .mdx files in different snippets. Therefore possible inconsistencies. Keep eye out for them since all the PRs require review

eslint + prettier works like a charm 🚀

its tricky in .md and .mdx files in different snippets.

Yea, this might be an issue, but there is an eslint plugin for mdx and for .md  but there is no rules and support for .mdx from markdownlint's side.
So if we are considering consistent formatting using prettier, then I think we may need to remove markdownlint and use eslint-plugin-markdown and eslint-mdx instead.
Even removing markdownlint right now isnt a good idea either

Keep eye out for them since all the PRs require review

Yes .

Another thing is that there might be a need for double quotes in those files e.g. JSON and regular quotes in plain text, so yeah its tricky

authors: EugeneHlushko anikethsaha anshumanv


text:
Dynamic Import Retry

Feature request

What is the expected behavior?
When regular JS resources fail to load, retrying their errors is quite straightforward - you can simply listen to the window.error event. However, this approach does not work for JS resources that are dynamically imported.
To achieve this, one would need to perform complex hacks on webpack's internal functionality, such as defining a plugin to manipulate RuntimeGlobals.require.
What is motivation or use case for adding/changing the behavior?
There is a desire for a standardized way to address this issue.
https://stackoverflow.com/questions/56772771/how-to-manually-load-webpack-async-chunks-when-any-dynamic-import-fails-to-load
https://stackoverflow.com/questions/62063737/what-is-the-best-practice-for-dealing-with-a-failed-dynamic-import-in-webpack
https://github.com/mattlewis92/webpack-retry-chunk-load-plugin/blob/master/src/index.ts
How should this be implemented in your opinion?
Add a webpack configuration option, such as dynamic.hosts. When a request for a dynamically imported JS resource fails, it will automatically retry requests to other CDN domains in the hosts.
Are you willing to work on this yourself?
no

Duplicate of https://github.com/webpack/webpack/issues/5115#issuecomment-310213277, you can make a small helper to implement this or yes, you can use create a plugin for this, I don't think we should implement it in the core, because fallback logic can be very different
Anyway feel free to feedback

authors: alexander-akait childrentime

repo: webpack/webpack


text:
Unable to disable comment preserving in uglifyjs plugin

Trying to do this: new webpack.optimize.UglifyJsPlugin({ comments: false })
Setting will be overwritten because of this:
https://github.com/webpack/webpack/blob/master/lib/optimize/UglifyJsPlugin.js#L79
Other reference:
https://github.com/mishoo/UglifyJS2/blob/master/lib/output.js#L62

I have the inverse problem. Uglify is removing comments inside an HTML string and "comments":"all" is having no effect. Any idea when I'll be able to configure this properly?

Oops, apparently it was the html loader who was realizing there was minification going on and turned it's own minification processes on. I have manually disabled it and everything works.

Found this post while searching for the same issue.
@sokra gave a workaround, which still works. Does it mean it's the right way now and it's not a bug?

@tleunen Should be resolved with https://github.com/webpack/webpack/pull/1298.

I'm still seeing this issue in latest version of webpack. @sokra's workaround does the trick

Can confirm that @sokra's workaround is still required for this

btw. it's intended that webpack preserves some comment. This is for legal reasons. By default comments with @license, @preserve or starting with /*! are preserved.

@WickyNilliams @NomNomCameron  I tested using v1.12.6 on jquery source, and it seems to work just fine (with or without the workaround). The test I provided in my PR (https://github.com/webpack/webpack/pull/1298) didn't fail.
Are you sure you're using latest webpack version for both local and global?

@sokra intersting! what legal reasons?

@ccorcos you typically want to preserve licenses which are usually at the top as a multi-line comment.

That's what I'm reading here, but why is that?

@ccorcos some licenses require it.

Look at this mess:
!function(e){function t(n){if(r[n])return r[n].exports;var o=r[n]={i:n,l:!1,exports:{}};return e[n].call(o.exports,o,o.exports,t),o.l
  !*** ./~/lodash/lodash.js ***!
  \****************************/
function(e,t,n){(function(e,r){var o;(function(){function i(e,t){return e.set(t[0],t[1]),e}function a(e,t){return e.add(t),e}function
  !*** ./src/client/environment.ts ***!
  \***********************************/
function(e,t,n){"use strict";Object.defineProperty(t,"__esModule",{value:!0}),t.default=null},/*!************************************
  !*** ./src/client/components/Component.ts ***!
  \********************************************/
function(e,t,n){"use strict";var r=this&&this.__extends||function(){var e=Object.setPrototypeOf||{__proto__:[]}instanceof Array&&func
  !*** ./~/react/react.js ***!
  \**************************/

So many comments that I dont need!

Comments in bundle can result in issue like this one when wrong line number is reported in tools like Sentry
https://github.com/getsentry/sentry-javascript/issues/2550#issuecomment-769909629

authors: Dashed NomNomCameron WickyNilliams ccorcos chestozo dashed firstdoit sokra tleunen


text:
webpack_public_path does not work in webpack 2

I'm submitting a bug report
Webpack version:
2.1.0-beta.25
Please tell us about your environment:
OSX 10.x
Current behavior:
set __webpack_public_path__ doesn't work
Expected/desired behavior:
I set __webpack_public_path__ = 'assets' in entry.js,then use System.import('xxxx'), the require path doesn't contain 'assets

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Language: [ES6/7]

It does work. Could you add a complete example? Check twice that __webpack_public_path__ =  is executed before importing the modules that reference it. imports are hoisted.

@leaves4j have you been able to verify this, otherwise I'll close this until you come across a concrete example.

similar issue here. __webpack_public_path__ only work for lazily-load chunks. the entry point - app.js , common-chunks - vendor.js, and  manifest.js are not effected.

should I open a new issue ?
question about imports are hoisted,
// app.js
__webpack_public_path__ = 'assets/'

require('./module-a')
...

// module-a.js
import './components'

is __webpack_public_path__ =  executed before import './components

my webpack config.
var path = require('path')
var webpack = require('webpack')
var ExtractTextPlugin = require('extract-text-webpack-plugin')
var HtmlWebpackPlugin = require('html-webpack-plugin')

module.exports = {
  entry: {
    app: [ './client/bootstrap/app.js' ]
  },
  output: {
    path: path.resolve(__dirname, '../dist'),
    filename: '[name].[chunkhash:6].js',
    chunkFilename: '[name].[chunkhash:6].js',
    publicPath: '/'
  },
  externals: {
    'jquery': '$',
    'angular': 'angular'
  },
  module: {
    rules: [
      {
        test: /\.(png|jpe?g|gif|svg)$/,
        use: [
          {
            loader: 'url-loader',
            options: {
              limit: 10000,
              name: 'assets/[name].[hash:7].[ext]'
            }
          }
        ]
      },
      {
        test: /\.(woff2?|eot|ttf|otf)(\?.*)?$/,
        use: [
          {
            loader: 'url-loader',
            options: {
              limit: 10000,
              name: 'assets/[name].[hash:7].[ext]'
            }
          }
        ]
      },
      {
        test: /\.html$/,
        use: [
          {
            loader: 'html-loader',
            options: {
              root: '~',
              ignoreCustomFragments: [/\{\{.*?}}/],
              minimize: true
            }
          }
        ]
      },
      {
        test: /\.js$/,
        exclude: /node_modules/,
        use: [
          {
            loader: 'babel-loader'
          }
        ]
      },
      {
        test: /\.json$/,
        use: [
          {
            loader: 'json-loader'
          }
        ]
      },
      {
        test: /\.(sass|scss)$/,
        loader: ExtractTextPlugin.extract({
          fallbackLoader: 'style-loader',
          loader: [
            {
              loader: 'css-loader'
            },
            {
              loader: 'sass-loader',
              query: {
                sourceMap: true,
                includePaths: ['node_modules'],
                indentedSyntax: true
              }
            }
          ]
        })
      }
    ]
  },
  resolve: {
    modules: [
      'client',
      'client/assets',
      'node_modules'
    ]
  },
  plugins: [
    new webpack.DefinePlugin({
      'process.env.NODE_ENV': '"production"'
    }),

    new HtmlWebpackPlugin({
      filename: 'index.html.etpl',
      template: 'client/bootstrap/index.html.etpl.ejs',
      inject: false,
      chunksSortMode: 'dependency',
      excludeChunks: ['manifest']
    }),

    new webpack.optimize.CommonsChunkPlugin({
      name: 'vendor',
      minChunks: function(module) {
        const userRequest  = module.userRequest

        if (typeof userRequest !== 'string') {
          return false
        }

        return userRequest.indexOf('node_modules') >= 0
      }
    }),

    new webpack.optimize.CommonsChunkPlugin({
      names: ['vendor', 'mainifest']
    }),

    new webpack.optimize.UglifyJsPlugin({
      sourceMap: true
    }),

    new webpack.LoaderOptionsPlugin({
      minimize: true
    }),

    new ExtractTextPlugin({
      filename: '[name].[contenthash:6].css',
      allChunks: true
    })
  ]
}

@lili21 That's the solution you're looking for: https://github.com/webpack/webpack/issues/2776#issuecomment-233208623

Looks like my issue is related to html-webpack-plugin. issue

Per https://webpack.js.org/guides/public-path/#set-value-on-the-fly:

Another possible use case is to set the public path on the fly. webpack exposes a global variable that let's you do that, it's called webpack_public_path.

However if APIPlugin does what I think it does, any usage of __webpack_public_path__ gets replaced by __webpack_require__.p. Which is fixed to the build-time publicPath value.
This then breaks file-loader which correctly attempts to use __webpack_public_path__.

Reassigning __webpack_require__.p appears to fix this issue. Presumably it could be set to __webpack_public_path__ || "" if there is no configured publicPath.

I've been able to remove my workarounds after upgrading to webpack@3 and file-loader@0.11.2.

@novemberborn Comments seems correct to me but I still have the issue with  "webpack": "3.5.5" and "file-loader": "1.1.4". The quick workaround was to make the webpack_public_path global in my code like:
__webpack_public_path__ = 'my custom path';
window.__webpack_public_path__ = __webpack_public_path__;

But this should be avoided. So shouldn't file-loader use __webpack_require__.p instead of __webpack_public_path__ ?


text:
refactor Dependency.js to es6

What kind of change does this PR introduce?
refactor
Did you add tests for your changes?
current tests should pass
If relevant, link to documentation update:
N/A
Summary
upgrade Dependency.js to es6
Does this PR introduce a breaking change?
No
Other
Dont expose compareLocations as Dependency attribute anymore as its only used internally anyways

should the file be moved to /dependencies ?

@timse so this one is a little more involved to switch over because it is a top level superclass there are multiple levels of inheritance between this one and any other file that ends in Dependency.
So to refactor this one, you would also need to first refactor any file that ends in Dependency. Good example is Dependency => NullDependency => ConstDependency. If your not quite up for that much refactoring that is okay, feel free to close this PR and work on the lower level (in the hierarchy) Dependency subclasses like anything in the dependency folder. Let me know if any of this is unclear.

i guess i need to start at the top of the foodchain here to make this work :)

now dependes on #3812 and #3818

Closed and reopened to kick off a new build.

checking why this fails!

found it. The only user of Dependency.compare seams to be Compilation, maybe we can inline that actually?

Well freaking done!!! That was a huge one.

Wow thank you so much. Would you mind shooting me an email? You can find it on my profile page. I'd like to chat with you briefly <3

authors: TheLarkInn timse


text:
Feature/main template type support

What kind of change does this PR introduce?
Typing JSDocs

Did you add tests for your changes?
N/A

If relevant, link to documentation update:
N/A

Summary
Add's Type support via JSDocs for MainTemplate class.

Does this PR introduce a breaking change?
No

Other information
This PR although may include TS nightly change in package.json actually relies on official version bump PR #7115

@sokra these errors look like legitimate bugs, I only seeing Module subclasses inheriting this._source, unless its RawModule which has this.sourceStr.
Is there something here I'm missing? cc @ooflorent maybe you've come across this

Rerunning CI with new TypeScript nightly now in master (which this was dependent on)

Merging now that type errors and lint failures are gone, and with @ooflorent approval.


text:
First stab at SourceMapDevToolPlugin exclude option

per @gaearon suggestion, see issue #650 raised by @davidtheclark: "The problem with this is that the vendor file can get pretty big, and its gigantic sourcemap then severely slows down dev tool initialization on page reload. I would much prefer to only have a sourcemap for my app chunk (and not to have a sourcemap for my vendor chunk)."
This is a first stab at the corresponding exclude options.
Note that it might get tedious to have to explicitly instantiate SourceMapDevToolPlugin, maybe a more global option such as output.sourceMapExcludeChunks could be introduced as well.
	plugins: [
		new webpack.SourceMapDevToolPlugin({
			filename: "[file].map",
			excludeChunks: ["vendors"]
		})

Not sure why the Travis Cl build failed.
 1) NodeWatchFileSystem should register a file change (watch delayed):
Error: timeout of 10000ms exceeded
at [object Object].<anonymous> (/home/travis/build/webpack/webpack/node_modules/mocha/lib/runnable.js:159:19)
at Timer.listOnTimeout (timers.js:110:15)

Please make it behave like the UglifyJsPlugin which has similar options: test include exclude https://github.com/webpack/webpack/blob/master/lib/optimize/UglifyJsPlugin.js#L43

@sokra ha, I didn't know about these options, there is not much documentation for include or exclude on UglifyJsPlugin, neither was I able to find tests stressing out these features. Nevertheless, here is the revised version.

The way SourceMapDevToolPlugin handles options looks very different than the way UglifyJsPlugin does it; the former copies the options back to member variables (this.cheapMode = options.cheapMode) while the latter is just content with assigning them to an object of the same name (this.options = options). I didn't want to completely break SourceMapDevToolPlugin so I didn't rewrite that behavior, I just made sure a this.options var now exists, so that it can be passed to SourceMapDevToolPlugin.prototype.matchObject.

I've only added the exclude option. I can easily put the test and include options back, just like UglifyJsPlugin, but I'm not sure how this would make sense. Let me know.

I've only added the exclude option. I can easily put the test and include options back, just like UglifyJsPlugin, but I'm not sure how this would make sense. Let me know.

Yes please add them back. (Both plugins should share the same logic)

The way SourceMapDevToolPlugin handles options looks very different than the way UglifyJsPlugin does it; the former copies the options back to member variables (this.cheapMode = options.cheapMode) while the latter is just content with assigning them to an object of the same name (this.options = options). I didn't want to completely break SourceMapDevToolPlugin so I didn't rewrite that behavior, I just made sure a this.options var now exists, so that it can be passed to SourceMapDevToolPlugin.prototype.matchObject.

Previously the SourceMapDevToolPlugin didn't use a options object. This was refactored latter.

Alright, here you go, factorized code, which brings back include and test in the process.

Anything else you want me to add?

Anything else you want me to add?

No looks good... I'll merge it once I have some free time...

Thanks, was just checking. Keep up the good work.

Thanks

authors: sebastienbarre sokra


text:
HookMap: replace .tap() with .for().tap()

Tapable will deprecate HookMap's tap tapAsync tapPromise API, so I make this PR to replace the HookMap instance use .tap() API with .for().tap() API.
What kind of change does this PR introduce?
This PR is refactoring the HookMap API.
Did you add tests for your changes?
Yes.
Does this PR introduce a breaking change?
No.
What needs to be documented once your changes are merged?
The pr has no perception of the user, do not need to be documented.

Thanks

Thank you for your amazing work!

authors: sokra yvanwangl


text:
edge: remove rtx from recv encoding parameters

Edge 14942 throws errors if the rtx field is present in the receiving encoding parameters.

@KaptenJansson ping ;-)

LGTM

authors: KaptenJansson fippo

repo: webrtc/adapter


text:
🛑 Jeff with Susan is down

In 2691a04, Jeff with Susan (https://www.jeffwithsusan.com) was down:

HTTP code: 521
Response time: 143 ms

Resolved: Jeff with Susan is back up in ce4fce5 after 415 days, 12 hours, 34 minutes.

repo: webworldview/uptime


text:
🛑 DragonBoat Times is down

In 0a1b972, DragonBoat Times (https://www.dragonboattimes.com) was down:

HTTP code: 521
Response time: 146 ms

Resolved: DragonBoat Times is back up in 6f2db1d after 419 days, 6 hours, 44 minutes.


text:
Unity转微信小游戏 中文字体无法显示

如题，编辑器试过2019、2020都不行

不要用unity的默认字体，自己另外弄个字体文件试试

用的系统里的黑体 真的可以，非常感谢

authors: Mrangor duogudeve


text:
大文件无法发送的问题

我在使用wechaty 企业微信版的过程中 发现发送大小为17M 的文件消息用的时间过长  但是还是能够发出去 ，我尝试发送一个 403M的文件时 无响应 文件无法发送 尝试直接用企业微信发送是可以发送的

目前不支持大文件发送，建议发送50M以下的文件。

authors: luyulong-em su-chang

repo: wechaty/puppet-supports


text:
Week-4 added the Wechaty environment variables

This PR contains the details about the environment variable in Wechaty
Will be adding more environment variables as soon as I get more information about it
Link #890

I am approving this PR for style and I have proofread this, someone from the org should verify that the content of the doc is correct or not.

I am approving this PR for style and I have proofread this, someone from the org should verify that the content of the doc is correct or not.

yes sure @Rohitesh-Kumar-Jain  thank you

@lijiarui mam can you please check this and merge it too?Huan sir has also approved it

hi @shraddhavp As GSoD Project PR Review Rules in https://github.com/wechaty/wechaty.js.org/issues/1045
This PR should follow our rules and get enough approval, then I will review this PR. So I remove the ready to merge tag and feel free to add this tag when it gets enough approval.

hi @shraddhavp As GSoD Project PR Review Rules in #1045
This PR should follow our rules and get enough approval, then I will review this PR. So I remove the ready to merge tag and feel free to add this tag when it gets enough approval.

mam @lijiarui  but this PR has got 3 approvals right? any other changes I should make ?

hi @shraddhavp As GSoD Project PR Review Rules in #1045
This PR should follow our rules and get enough approval, then I will review this PR. So I remove the ready to merge tag and feel free to add this tag when it gets enough approval.

mam @lijiarui but this PR has got 3 approvals right? any other changes I should make ?

You should got the following approval as #1045 showed
For writers:
Writers who are in the same team are REQUIRED to review each other’s PR, and give “Request changes” or “Approve”
Writers are encouraged to give “Request changes”, “Approve”, or “Comment” to any PRs. (please contribute to the whole team by doing it!)
Your team member is @Soumi7, so you should git @Soumi7 approval first.
For volunteers:
Volunteers are REQUIRED to review all PRs created by writers and give “Request changes” or “Approve”
We have two volunteers, so you should both got @Rohitesh-Kumar-Jain and @proudofsimin approval, there is no problem for this part.

hi @shraddhavp As GSoD Project PR Review Rules in #1045
This PR should follow our rules and get enough approval, then I will review this PR. So I remove the ready to merge tag and feel free to add this tag when it gets enough approval.

mam @lijiarui but this PR has got 3 approvals right? any other changes I should make ?

You should got the following approval as #1045 showed
For writers:
Writers who are in the same team are REQUIRED to review each other’s PR, and give “Request changes” or “Approve”
Writers are encouraged to give “Request changes”, “Approve”, or “Comment” to any PRs. (please contribute to the whole team by doing it!)
Your team member is @Soumi7, so you should git @Soumi7 approval first.
For volunteers:
Volunteers are REQUIRED to review all PRs created by writers and give “Request changes” or “Approve”
We have two volunteers, so you should both got @Rohitesh-Kumar-Jain and @proudofsimin approval, there is no problem for this part.

ok mam

@Soumi7 We would be glad if you may once go through the PR, and either request for changes or approve the PR.

@lijiarui  mam can you please review the PR and give us the feedback?

authors: Rohitesh-Kumar-Jain lijiarui shraddhavp


text:
🛑 Landing page is down

In 10cbe00, Landing page (https://wectrl.io) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Landing page is back up in ee02927 after 43 minutes.

repo: wectrl-io/upptime


text:
added authentication permission to swagger request

swagger can now send authenticated requests to backend services if authentication and authorization is enabled

fixed react, generator regarding swagger auth

repo: wedaa-tech/jhipster-blueprints


text:
pnnx does not exist

Hello There, this is my problem, I just download from higginface for model but it still doesnt work what can i do?

You need to download pnnx.

Thanks for reply my message that I already complete fixed it. It is my Models and config.JSON problem. I would like to request that do you have another models with JSON please? I test all my models with problems there which shows many problems there. if you don't want to share your data and just ignore it! Appreciate!

authors: blueokanna weirdseed

repo: weirdseed/vits-ncnn-convert-tool


text:
在MEDIUM以及更粗的字重里头，“烟”字没有拔去左边的引脚。

拔脚很难做到十分完美……

repo: welai/glow-sans


text:
fix the decode bug in NumpyArrayDecoder

get real data with "ptr" field of WeldVec

Thanks @hustnn, merging this in.

repo: weld-project/weld


text:
As a library member I want to know if an item is available for requesting

What is it and who's it for?
Library users
User story
Feature: 1. As a library member I want to know if an item is available for requesting
Acceptance criteria
Scenario: I'm viewing a work page
Given the work has a requestable item
And it’s available to request
Then I can see a that it's requestable
Scenario: I'm viewing a work page
Given the work has a requestable item
And it’s unavailable to request
Then I can see a that it's temporarily unavailable
Scenario: I'm viewing a work page
Given the work has no requestable items
Then I can see a that it's not requestable and why (closed or open shelves or unknown)
Implementation
Testing and tracking

Have you talked to Tacey?
Test plan
Will you need to set up additional tracking?
What is the expected life span for tracking?

Measurement
Related KPIs (e.g. breadth of collection accessed, reading time, etc.)
Other considerations
<---Delete as appropriate--->

Impact on URL design
Cardigan documentation

Links to zeplin wireframes
Scenario 1 (item available): https://app.zeplin.io/project/5aab926b4b6efde01259e959/screen/5e568a35deafd9662acdd215/
Scenario 2 (item temporarily unavailable):
https://app.zeplin.io/project/5aab926b4b6efde01259e959/screen/5e568a3572ead876e1493115/
Scenario 3 (open shelves/closed):
https://app.zeplin.io/project/5aab926b4b6efde01259e959/screen/5e568a35f9503e7360d94a55/
https://app.zeplin.io/project/5aab926b4b6efde01259e959/screen/5e568a35bb57d361c1de3950/

@gestchild Can this be closed now?

authors: DominiqueMarshall jennpb pollecuttn


text:
Drop images from the API that don’t have technical metadata

What is this PR trying to achieve?
Discard images from the API that don’t have technical metadata – i.e., no underlying file.
Related: #759.
Who is this change for?
An Experience team who don’t want broken image links.
Have the following been considered/are they needed?

[ ] Deployed new versions

Transformer tests are failing (no, I don’t know why) – but I think this patch is ready for review.

repo: wellcometrust/platform-api


text:
Who is asking for PNGs as JPEGs?

We keep getting Loris alarms in Slack about somebody trying to request images like this:
/wordpress:2016/04/viral-nova.png/full/320,/0/default.jpg
If you try to fetch that image from Loris, it complains because it can’t convert an RGBA PNG to an RGB JPEG. What should it do with the transparent regions? The IIIF Image spec doesn’t seem to mention this possibility.
That it’s appearing early in the morning (UK time) suggests that maybe this is an automated crawler?
Whatever it is, we should find out and shut it up, so it stops spamming Slack with alarms!

Inspecting the ALB logs from today’s error:
760097843905_elasticloadbalancing_eu-west-1_app.api.e87a4a5f32874d8b_20170926T0730Z_52.51.25.193_5f7glel8.log:531:https 2017-09-26T07:28:03.894196Z app/api/e87a4a5f32874d8b 35.167.191.134:27087 10.30.0.99:32790 0.001 0.219 0.000 500 500 527 483 "GET https://iiif-origin.wellcomecollection.org:443/image/wordpress:2016/12/victoria_and_albert_christmas_tree.png/full/320,/0/default.jpg HTTP/1.1" "Mozilla/5.0 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm)" ECDHE-RSA-AES128-GCM-SHA256 TLSv1.2 arn:aws:elasticloadbalancing:eu-west-1:760097843905:targetgroup/loris/137b9ef8b7bbfbf8 "Root=1-59ca0183-578d8d20733d06387e5799c3" "iiif-origin.wellcomecollection.org" "session-renegotiated-or-reused"

and pulling out the user agent string:
Mozilla/5.0 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm)

Blergh. Wait it out, I guess? 😕

At this point, these alerts have died down, and we have enough alarm visibility to see if this is the cause of a particular alarm or something else. I don’t think we need to do anything else here for now.

Closing again, I haven’t seen these errors in quite a while.

repo: wellcometrust/platform


text:
Promo for Image Gallery as Main Article

Here's Tomi's first go at a design. Team should discuss before getting started.

Title
Lead image
Summary
Total number of images
Format index: Image gallery > aggregate on /image-galleries

pinging @Heesoomoon and @GarethOrmerod - a stale idea for an image gallery card.

Noted. It will be good to explore an option of displaying more than one image to represent the image gallery. Hinting there are more to see but not fully exposing everything.

I'm going to close this one now as it's too stale!

authors: Heesoomoon jennpb


text:
gigaspeech  LM  notworking with gigaspeech U2PP model

I am using pre-trained/gigaspeech/20210728_u2pp_conformer_libtorch as  acoustic model  and  want to use gigaspeech LM from https://huggingface.co/wgb14/gigaspeech_lm while decoding. I built TLG.fst using  the instructions from https://github.com/wenet-e2e/wenet/blob/main/docs/tutorial_librispeech.md (Stage 7)  I have used  the  lexicon from the same source  and  using a bpe model to split it.
./build/bin/decoder_main
--chunk_size -1
--wav_path $wav_path
--model_path $model
--unit_path $units
--rescoring_weight $rescoring_weight
--ctc_weight $ctc_weight
--reverse_weight $reverse_weight
$wfst_decode_opts
--result  $result/youtube.txt   &> $result/out.log
Howver, I am getting  a  totally wrong  junk text, onlly  few words  are meaningful.   When I decode the model  without LM, it is ok. What is happening here ?

Did you get the right output when LM is not used?

Yes.

There must be some error when you building the FST. please make sure the modeling units of gigaspeech model(the model you download) is used for building the FST.

This may help you https://github.com/wenet-e2e/wenet/issues/1673

Thanks. Now  working

May I ask how did you work in the end? and must use the bpe model. where can i get the bpe model? thanks

The  bpe  model  is  trained  using the train text. You refer  the  run.sh  under  examples/gigaspeech/s0

authors: jayakrishnanmm naomibb robin1001 xingchensong


text:
Question: While Developing, Reload Package changes?

Sorry this is more of a question of actually attempting to fix bugs (adding features) for PR. I'm curious if I clone this solution and use the example folder as the sort of container project to visualize changes, should I be able to see updates to the package rendered within the example app? Is there something I need to Enable?
I noticed the example project is just referencing Kalender library as if it was a relative import (up a folder structure). I dont even know of a way to build the Kalendar package such that I can import the changes into the example app, as flutter/dart cli tools seem to want to spit out a new executable (mobile/web/windows).
So far I opened the Kalendar project, and then just have a debug configuration that just starts ./example project.

Hi, yes it is setup so that when you make changes in the package lib/.. it will reflect in the example app.
You can start the example app with:

cd example && flutter run
Using VS code's run and debug tab.

You can then make changes in the package lib/... and use hot reload to reflect those changes.

just a note I'm currently working on the calendar_rework branch which might fix a lot of the current issues, it is a rewrite basically but it is still a while before it will be done.

well one of the reasons I was looking into this, is I'd actually like to specifically use it with fluentui without the material ui stuff. I have that part working, but some of the styles are not correct.

Hi, I don't have experience working with fluent ui, so if you don't mind can you let me know which parts are not working for you.
The best solution I see for this is to allow overrides for all the UI widgets in the package.

Essentially fluentui replaces the sources of a lot of types. They keep the same name in a lot of cases, but come from fluentui packages. Most of the styles are not there as well. I'm not sure how worth making the UI framework pluggable would be (I suspect it would be unnecessary for your needs...)

I see, yeah not really worth it for me. However you should be able to override all the default widgets to use custom ones that use fluentui quite a bit of work though.

authors: ronnyek werner-scholtz

repo: werner-scholtz/kalender


text:
imprv: Commonize full-text and custom search result schema

Redmine: https://redmine.weseek.co.jp/issues/82548
現在の検索ページで NamedQuery による検索と、通常の検索をできるようにしました(検索で返ってくるデータの形を揃えた)
一旦 delegatorName で reshape するかどうかを判断しています。対象の関数は checkIsReshapable です

dev/5.0.x に page tree と search 関連の変更を反映させた上で再度 PR 依頼してください

authors: hakumizuki yuki-takei

repo: weseek/growi


text:
Make the cell’s datatype nil when setting a BigDecimal.

This will mean that BigDecimal objects are treated the same as other numeric objects.

Thanks, @weshatheleopard!

repo: weshatheleopard/rubyXL


text:
Update sbt-native-packager to 1.9.7

Updates com.typesafe.sbt:sbt-native-packager from 1.8.1 to 1.9.7.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.typesafe.sbt", artifactId = "sbt-native-packager" } ]

labels: sbt-plugin-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #181.

repo: weso/shacl-s


text:
Passing config through parameters doesn't work

Describe the bug
I tried passing config through parameters to hooks (outside of WagmiContext), but it throws WagmiProviderNotFoundError. Parameters aren't pass down to hooks called inside hooks, which causes the error and, to me, conceptually doesn't make sense.
https://github.com/wevm/wagmi/blob/8e9ee793c4f378de523239bb8db63cbf09cc980e/packages/react/src/hooks/useReadContract.ts#L88
Not sure if this is intended use case :shrug:
Link to Minimal Reproducible Example
No response
Steps To Reproduce
No response
Wagmi Version
2.5.18
Viem Version
2.9.9
TypeScript Version
No response
Check existing issues

[X] I checked there isn't already an issue for the bug I encountered.

Anything else?
No response

Nice find! Looks like there were multiple places where config wasn't passed through directly. https://github.com/wevm/wagmi/pull/3793 addresses this.

authors: tmm youPickItUp

repo: wevm/wagmi