text:
Replaced unique_together with models.UniqueConstraint in TranslatableMixin

Django unique_together may be deprecated in the future. models.UniqueConstraint is recommended in Django documentation as a good replacement as it also offer more functionality. This pull request resolves this issue #11098
Please check the following:

[ ] Do the tests still pass?[^1]
[ ] Does the code comply with the style guide?

[ ] Run make lint from the Wagtail root.

[ ] For Python changes: Have you added tests to cover the new/fixed behaviour?
[ ] For front-end changes: Did you test on all of Wagtail’s supported environments?[^2]

[ ] Please list the exact browser and operating system versions you tested:
[ ] Please list which assistive technologies [^3] you tested:

[ ] For new features: Has the documentation been updated accordingly?

Please describe additional details for testing this change.
[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

I would need to modify some tests so the checks can run successfully.

@lb- I have a test__migrations (wagtail.tests.test_migrations.TestForMigrations) failure. Not sure what to do. I can't find manage.py in wagtail.tests, so I am not sure whether create one to create the migration files for this test to be successful.
this is the specific error I am getting:

Traceback (most recent call last):
File "/home/danajayi/wagtail/wagtail/tests/test_migrations.py", line 63, in test__migrations
self.fail("Model changes with no migrations detected:\n%s" % migrations)

Sorry @Temidayo32  this is not my area of expertise, my guess is that there could be some cross database issues with using UniqueConstraint.
See the call outs linked under this section
https://docs.djangoproject.com/en/4.2/ref/models/constraints/#uniqueconstraint

Functional unique constraints have the same database restrictions as Index.expressions.

https://docs.djangoproject.com/en/4.2/ref/models/indexes/#django.db.models.Index.expressions - then says there are some restrictions.
But that could be wrong, there may be something else going on here.

@lb- Hmmm, this is interesting. Thanks for pointing out that aspect of the docs. But it is a little surprising functional Uniqueconstraint might be up against some cross database restrictions. Because the docs also points out unique_together might be deprecated and be replaced by UniqueConstraint.
As regards the failed checks, they aren't a result of the restrictions, that's if there is any. They are actually a result of the tests written by Wagtail for the database. Currently, there are two test failures. Locally, I have fixed one of them. The second has to do with the tests_migration. The test is setup to throw error if there are model changes and there aren't any migration for them yet. Since I modified TranslatableMixin and changed some of its attributes, new migrations need to be made. Unless the migrations are made, the error would remain.

The main thing here is we want to handle both unique_together and UniqueConstraint as can't guarantee what existing implementations will use

@zerolab Yeah, I thought of doing that too. Better still, let me just do that. Initially, I thought it might be unnecessary duplication.

@zerolab Yeah, I have done that (I mean added back unique_together). But since I added a new attribute to the model which is UniqueConstraint the migration test still won't pass. Any idea on how to proceed with that?

@laymonage I have made the requested changes. I  I have made the suggested change above. But I am aware this would cause a failing test with the migration, partcularly, wagtail.tests.test_migrations.TestForMigrations. test__migration, since I would now have to define constraints in the meta class . Let me know if you want me to create the necessary migration files. I haven't done that yet since my most recent changes haven't been reviewed yet. Thanks so much.

@laymonage I added 3 new tests. The third test is the one you were considering we add. This:

Now I'm wondering whether we should also test when both are used 🤔 We don't want developers to do this, so maybe it's worth adding the check.

Let me know if there is anymore correction to be made. Thanks.

@laymonage Thanks so much for helping with this PR. I really appreciate!

authors: Temidayo32 lb- zerolab


text:
Can not get wakatime-cli --today

Expected behavior (what should have happened): show the time today
Actual behavior (what went wrong): get an error SIGSYS: bad system call PC=0x16030 m=8 sigcode=1
Environment:

OS: Android
Platform: arm

Logs: {"caller":"cmd/run.go:98","func":"cmd.Run","level":"debug","message":"command: today","now":"2023-10-07T14:12:34Z","os/arch":"linux/arm64","version":"v1.85.1"}

I install wakatime with neovim on termux(android) and if i run wakatime-cli --today i got an error like this
So how to fix it?

@holiq the wakatime-cli was built excluding Android and the vim plugin needs to correctly download the new Android Build added in this PR. @alanhamlett will take care of the vim part and let you know.

I don't know what's wrong, but it still not work on me (Android 13, Termux 0.118.0)

Your screenshot shows you're using the Linux version. You need to download the wakatime-cli-android.

Oh yeah, now that work on me, thank you

source: gharchive/issue

authors: alanhamlett gandarez holiq

repo: wakatime/wakatime-cli

license_type: permissive

license_source: github-api


text:
When listing available dependencies, only explicit dependencies are shown [0.2.4]

Would be nice if it would also list the implicit dependencies gathered from sibling projects

This is another side-effect of the presence of a checkouts folder.

repo: walmartlabs/shared-deps

license_source: bigquery


text:
SD-JWT VC spec

As I just looked through the verifiable-credential lib, I noticed the W3CVC class is issuing W3C credentials as SD-JWT with the vc+sd-jwt type, which is not entirely correct.
The vc+sd-jwt credential format is NOT the same as a W3C credential issued as SD-JWT, as pointed out in the SD-JWT VC spec:
... Note: This specification does not utilize the W3C's Verifiable Credentials Data Model v1.0, v1.1, or v2.0.

yes

What about now, @severinstampler ? May we close it?

Closing after talking to @severinstampler

authors: alegomes severinstampler

repo: walt-id/waltid-identity


text:
[Q] Is it possible to recursively upload a tensorboard directory?

I don't see a way to do this in the docs, but could just be missing it.

wandb sync path_to_tensorboard_dir.  If you have multiple experiments, you'll want to call wandb sync for each experiment directory.  You can also do this via python with:
api = wandb.Api()
api.sync_tensorboard(path_to_tensorboard_dir)

Here's a link to the SDK method: https://github.com/wandb/client/blob/master/wandb/apis/public.py#L259

authors: cinjon vanpelt

repo: wandb/client

license: MIT


text:
[Q] Disabling Symlinks in wand.settings.py doesnt work?!

Hi all,
i tried to use the windows setting in wandb_settings.py
(https://github.com/wandb/wandb/blob/06117d9651d6e466819b8cac0701ef32364e1586/wandb/sdk/wandb_settings.py#L1503-L1511)
but it doesnt work and using this settings doesnt disable the creation of symlinks? Is this an Issue?

Hi @maba1337, are you getting an error when using wandb or are you asking if this has the potential to cause problems?

@maba1337 if you are on windows we disable symlink by default you can see in the code you linked, so you don't actually need to do anything to disable it. Do you have by any chance an environment variable  WANDB_SYMLINK set to True? Also could you check what you get when you run:
import platform
print(platform.system())

Hi @maba1337, you should be able to echo %WANDB_SYMLINK% to see if this has been set

Hi @maba1337, did you get a chance to see if this was set?

since we didn't hear from the user closing the issue. re-open if you still facing this issue.

authors: kptkin maba1337 nate-wandb

repo: wandb/wandb


text:
FileNotFoundError [WinError 3] when running on Windows

Describe the bug

After creating an artifact and trying to call log_artifact() an exception is thrown for a file not found error.

dataset_artifact = wandb.Artifact("test", "test", incremental=true)
wandb.log_artifact(dataset_artifact)
dataset_artifact = dataset_artifact.wait()

[2024-01-24T18:34:02.813Z] Exception in thread Thread-14 (_thread_body):
[2024-01-24T18:34:02.816Z] Traceback (most recent call last):
[2024-01-24T18:34:02.818Z]   File "C:\Users\dsaffie\AppData\Local\Programs\Python\Python311\Lib\threading.py", line 1038, in _bootstrap_inner
[2024-01-24T18:34:02.819Z]     self.run()
[2024-01-24T18:34:02.821Z]   File "C:\Users\dsaffie\AppData\Local\Programs\Python\Python311\Lib\threading.py", line 975, in run
[2024-01-24T18:34:02.824Z]     self._target(*self._args, **self._kwargs)
[2024-01-24T18:34:02.827Z]   File "C:\Users\me\AppData\Local\Programs\Python\Python311\Lib\site-packages\wandb\filesync\step_checksum.py",
line 81, in _thread_body
[2024-01-24T18:34:02.828Z]     filesystem.mkdir_exists_ok(os.path.dirname(path))
[2024-01-24T18:34:02.829Z]   File "C:\Users\me\AppData\Local\Programs\Python\Python311\Lib\site-packages\wandb\sdk\lib\filesystem.py", line 30, in mkdir_exists_ok
[2024-01-24T18:34:02.830Z]     os.makedirs(dir_name, exist_ok=True)
[2024-01-24T18:34:02.832Z]   File "<frozen os>", line 215, in makedirs
[2024-01-24T18:34:02.833Z]   File "<frozen os>", line 215, in makedirs
[2024-01-24T18:34:02.834Z]   File "<frozen os>", line 215, in makedirs
[2024-01-24T18:34:02.835Z]   [Previous line repeated 7 more times]
[2024-01-24T18:34:02.836Z]   File "<frozen os>", line 225, in makedirs
[2024-01-24T18:34:02.837Z] FileNotFoundError: [WinError 3] The system cannot find the path specified: 'C:\\Users\\me\\AppData\\Local\\Temp\\tmpcl35an_vwandb\\zhpqp9ix-../AppData'

Additional Files
No response
Environment
WandB version: 0.16.2
OS: Windows 10 Enterprise
Python version: 3.11.4
Versions of relevant libraries:
Additional Context
No response

Hey @dsaffie, thanks for reporting this! Would you mind sharing if this happened after upgrading the wandb package or has it always been the case?

@ luisbergua the issue ended up being setting the save_code flag to True in init()

Thanks for confirming this @dsaffie!

authors: dsaffie luisbergua


text:
🛑 poe-replit-反代_poe is down

In 8b46f54, poe-replit-反代_poe (https://poe.wang5.repl.co) was down:

HTTP code: 0
Response time: 0 ms

Resolved: poe-replit-反代_poe is back up in 7528d03.

repo: wang-task/upptime


text:
希望安卓版可以增加：开机自动后台启动且执行功能。

安卓版如果可以增加：开机自动后台启动且执行功能。就完美了！

如果需要安卓开机自启软件，可以看下系统有没有类似的设置


text:
更新

更新

source: gharchive/pull-request


text:
'EfficientNet' object has no attribute 'extract_textures'

Hey , I compared the code with your other repository "m2tr", I found that your deleted the def extract_textures in efficientnet.py, and this caused the code to report an error —— 'EfficientNet' object has no attribute 'extract_textures'

Hi, @Kidleyh
Thank you very much for pointing out this issue. We had found this problem and should have fixed it. Please pull the latest code and check.
Best regards

Thank you, I have pulled the latest code and can run m2tr successfully

authors: Kidleyh zhangchaosd


text:
include infos about which software is available in which room

like the printer list, but for rooms. maybe get infos from http://www.hft-stuttgart.de/Einrichtungen/IZ/IZ-Basisdienste/Rechnerraeume/Lageplan/Bau2_EG/index.html/de

waiting for better data source...

license: mit


text:
BUG: Properties('uniform-sampling') is deprecated

This property was dropped sometime recently, this patch removes that
property.
Related post:
https://github.com/qiime2/q2-feature-table/issues/108#issuecomment-316460800

Thanks! I didn't like that property too...

authors: ElDeveloper wasade


text:
CHORE: Provide error when non-empty values are used for buckets with kvredis provider

Affected project(s)

[ ] documentation
[ ] examples
[ ] wasmCloud host
[ ] wasmCloud CLI (wash)
[ ] wasmCloud dashboard UI (washboard)
[X] capability providers
[ ] provider bindgen
[ ] control interface client
[ ] other / not sure

Is your feature request related to a problem? Please describe.
Per discussion with @rvolosatovs the kvredis provider currently accepts differentiated names for buckets, and this may foster an incorrect perception that the provider uses multiple, separate buckets when it in fact uses a single global bucket.
Describe the solution you'd like
The provider should error if anything other than an empty string is used.
Describe alternatives you've considered
No response
Additional context
No response

What are our thoughts on a warning log here? I'm concerned that existing applications using wasi-keyvalue may unexpectedly fail if they were using a bucket before

I think the Right™ answer here is to error because the thing providing is saying "I don't know what you're referring to." Maybe start with a warning message for the next release and then turn it into a hard error after that

repo: wasmCloud/wasmCloud


text:
build: build Rust examples as part of test

Feature or Problem

Build Rust examples as part of normal testing procedure, while keeping the examples in their own workspaces
Related Issues

Release Information

Consumer Impact

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification

After thinking a bit about this, let's just update test_actors and write unit tests like in #1929


text:
chore(examples): enable template for password checker

Feature or Problem

Related Issues

Release Information

Consumer Impact

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification

This is mildly annoying, but can I ask that this be closed and reimplemented against the new typescript monorepo?

authors: lachieh vados-cosmonic


text:
add 地理院津波データ

輪島西津波浸水域データを追加
https://x.com/gsi_cyberjapan/status/1745717812088439239?s=20

追加完了


text:
Option to turn "Command exited with 0" back on

I think this was present in older version of cargo-watch, and I noticed it's still present in watchexec that it shows some text after the child terminated.
The latest version of cargo-watch doesn't do this by default and I couldn't figure out how to turn it back on. Without this text it's difficult to tell from the output if the command completed or hangs. :)
Thanks!

Specifically this was disabled on powershell in windows due to bugs, but still exists elsewhere. Watchexec has a different mechanism for it so it still works there for all platforms.

authors: kpcyrd passcod

repo: watchexec/cargo-watch


text:
decomp: the majority of navigate and rolling-lightning-mole

Remaining issues not solved here / skipped:

[ ] One function's CFG fails to construct - (method 27 nav-mesh)
[ ] (method 18 nav-mesh) and (method 17 nav-mesh) deal with a weird element that originates on the stack in 17, and is recursively propagated in 18.  I'm still bad at reading the assembly around these kinds of things.
[ ] (method 29 nav-mesh) -- Failed to match product_with_constant inline array access 2.
[ ] some other functions are skipped -- will be much easier to figure out once usages get involved

Pull Request Test Coverage Report for Build 1642059135

29 of 92 (31.52%)  changed or added relevant lines in 7 files are covered.
26 unchanged lines in 6 files lost coverage.
Overall coverage decreased (-0.07%) to 53.365%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

decompiler/IR2/OpenGoalMapping.cpp
16
19
84.21%

decompiler/IR2/AtomicOp.cpp
2
6
33.33%

goalc/compiler/compilation/Asm.cpp
0
12
0.0%

decompiler/util/data_decompile.cpp
3
24
12.5%

decompiler/IR2/FormExpressionAnalysis.cpp
3
26
11.54%

Files with Coverage Reduction
New Missed Lines
%

decompiler/IR2/OpenGoalMapping.cpp
1
63.24%

decompiler/util/data_decompile.cpp
1
48.56%

goalc/debugger/Debugger.cpp
1
72.86%

goalc/listener/Listener.cpp
3
84.35%

decompiler/IR2/FormExpressionAnalysis.cpp
8
68.67%

decompiler/IR2/bitfields.cpp
12
56.2%

Totals

Change from base Build 1639497888:
-0.07%

Covered Lines:
40836

Relevant Lines:
76522

💛  - Coveralls

Pull Request Test Coverage Report for Build 1642059135

29 of 92 (31.52%)  changed or added relevant lines in 7 files are covered.
26 unchanged lines in 6 files lost coverage.
Overall coverage decreased (-0.07%) to 53.365%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

decompiler/IR2/OpenGoalMapping.cpp
16
19
84.21%

decompiler/IR2/AtomicOp.cpp
2
6
33.33%

goalc/compiler/compilation/Asm.cpp
0
12
0.0%

decompiler/util/data_decompile.cpp
3
24
12.5%

decompiler/IR2/FormExpressionAnalysis.cpp
3
26
11.54%

Files with Coverage Reduction
New Missed Lines
%

decompiler/IR2/OpenGoalMapping.cpp
1
63.24%

decompiler/util/data_decompile.cpp
1
48.56%

goalc/debugger/Debugger.cpp
1
72.86%

goalc/listener/Listener.cpp
3
84.35%

decompiler/IR2/FormExpressionAnalysis.cpp
8
68.67%

decompiler/IR2/bitfields.cpp
12
56.2%

Totals

Change from base Build 1639497888:
-0.07%

Covered Lines:
40836

Relevant Lines:
76522

💛  - Coveralls

authors: coveralls xTVaser

license: ISC


text:
missing profanity filter param added

Summary
profanity filter can be set in settings but it's not sent to the server. so it always takes default value true. so there is no way to set profanity filter false.

 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.

Great catch, thanks @mitulgolakiya! We'll merge this in as soon as you sign the CLA.

authors: CLAassistant glennrfisher mitulgolakiya

repo: watson-developer-cloud/ios-sdk


text:
Fix the IAM access issues

When I run the Watson speech2text demo in my local and cloud CF, and encountered several issues related to the IAM authentication. Part of the issues are recorded in these two issues:
https://github.com/watson-developer-cloud/speech-to-text-nodejs/issues/265
https://github.com/watson-developer-cloud/speech-to-text-nodejs/issues/264
And finally I resolved the issues by this code change.
Hope you can review and merge the change.
BTW, I didn't test regression on the watson-token access, but I think this already deprecated.
Thanks,
Bali

@apaparazzi0329 can you review this and the issue and see if it can be merged?

authors: leibaogit repjarms


text:
Add multi-line string literals

It can be really useful to embed multi-line string content for things like SQL queries or HTML/CSS blobs. Heredocs are always a little too tricky, so I think something like Python's "triple-quoted strings" would be good.
let css = """
.foo {
  font-family: "Comic Sans";
}
"""
in ...

Maybe \ could escape newlines to swallow them, like the typical Python-ism of doing """\ on the opening line to not get an extra newline at the beginning.

I think it would probably make sense to say the multiline string starts with """\n, so that the initial newline is not added in. Trailing newline can easily be controlled based on where the ending """ is on its own line or butting up against the content.

repo: wavebeem/squiggle


text:
camera.record_sequence and annotate text as date time doesn't work?

import picamera
import itertools
import datetime

def get_file_name():   # File Name and times to record
    for i in itertools.count(1):
        yield datetime.datetime.now().strftime("/home/pi/vid/%Y-%m-%d_%H.%M.%S.h264")

with picamera.PiCamera() as camera:

    def annotate():
        while True:
            camera.annotate_text = datetime.datetime.now().strftime('%Y-%m-%d %H:%M:%S')

    camera.resolution = (1920, 1080)
    camera.framerate = 30
    camera.start_preview()
    camera.preview.fullscreen = False
    camera.preview.window = ( -80, 0, 900, 480)
    start = datetime.datetime.now()
    camera.annotate_text_size = 50

    def record():
        for filename in camera.record_sequence(get_file_name(), quality=20, bitrate=750000):
            camera.wait_recording(60)

	annotate()
 	record()

having annotate causes record to not do anything. Why is that so?
I can't do python well, so most of the code is a mix from the recipes that are from the picamera api info sites.

I'm not a Python expert, but to me it looks like your annotate function will just spin continuously, constantly updating the annotate text. Depending on how threading works on Python, that is going to starve other processes from doing anything (eg collecting the encoded data).
Try amending annotate to:
import time
....
    def annotate():
        while True:
            camera.annotate_text = datetime.datetime.now().strftime('%Y-%m-%d %H:%M:%S')
            time.sleep(1)

so that the text is only updated once a second.
I'm not sure that will do what you want anyway, as I would expect your code to wait on the camera.wait_recording(60) for the recordings to finish, and then call annotate to update the annotation text. I'm guessing you want to update it whilst the recording is in progress. How to achieve that is not something I know the answer to.


text:
Formalise into a library

This pull request turns the codebase and repo from a hobby project into a usable library.

Convert to a Maven project
Split out edge, point, triangle classes into separate files
Remove main() example method
Other source changes: add collection <types>, convert stateless methods to static methods, etc...
Amend readme
Reformat source to conventional Java style
Move images to \resources + add Jitpack badge (to host the code as a maven artifact for usage in other projects)

very thanks ! :-)


text:
careers

Description
Resolves #7
Type of Change

[ ] Bug Fix
[x] New Feature
[ ] Breaking Change
[ ] Refactor
[x] Documentation
[ ] Other (please describe)

Checklist

[x] I have read the contributing guidelines
[x] Existing issues have been referenced (where applicable)
[x] I have verified this change is not present in other open pull requests
[x] Functionality is documented
[ ] All code style checks pass
[x] New code contribution is covered by automated tests
[x] All new and existing tests pass

i've removed the mobility doc because much of how it helps careers is in there. It doesn't feel like enough content to warrant a whole document though I've written drafts a couple times on mobility through aux. Feels too ethereal / unproven / not good grounding in examples for me to paint a meaningful picture. That closes #8

repo: wayfair-incubator/aux-eng-playbook


text:
Improve vscode dev container experience

Describe the problem you are trying to solve
Currently the dev container support for tremor is good but working natively on OS X
and natively in the dev container requires some compromises which cost developer
time. The enhancements below should reduce the context switching overheads
Describe the solution you'd like

[x] Add support for linux-tools perf
[x] Add support for Brendan Gregg's flamegraph
[x] Add support for valgrind
[x] Allow Mac OS X and vsc dev container to co-exist with different cargo target paths
[x] Integrate perf/flame/valgrind with benchmark system
[x] Investigate dev container setup tweaks for Mac Os X dev environments

Notes

[ ] Optional. Consider adding convenience scripts as appropriate

Resolved by #99 with convenience scripts to be added

closing this as it's marked as resolved in the prior comment

authors: Licenser darach

repo: wayfair-tremor/tremor-runtime


text:
search panel size issue on Ipad Pro viewport

The search panel should be properly resized if viewed on Ipad pro.

Done #20


text:
你好，请问下，这版固件可以获取到WAN口的IPV6地址吗？

你好，对于编译方面我不太懂，只会把文件下载下来去烧录使用，我想了解一下：IPV6这个功能已经编译进去了吧，可以设置获取到网口的IPV6地址吧？

好像可以吧，我这里没有ipv6可以测试


text:
Panic during init on Windows

When trying to start a binary on Windows that uses this library the program panics during the init stage.
It looks to be because go-chart sets up time zone helpers, except it ignores the error from
_eastern, _ = time.LoadLocation("America/New_York")

This casues _eastern to be nil.
The error returned here is
UTC open /usr/local/go\lib\time\zoneinfo.zip: The system cannot find the path specified.

Note this only happens on systems that do not have Go installed because a Go installation contains the required zoneinfo.zip. https://golang.org/pkg/time/#LoadLocation.
Is it possible to defer initialisation of time zone helpers until they are actually needed? It seems you cannot rely on accurate time zone information in Go.

good catch; annoying that here is a cross platform issue around this, but should be easy to mitigate

refactored the helper constants (NYSEOpen etc.) to be functions for lazy eval, further we're now using build flags to set up the correct tzi names on windows vs. posix

authors: relvacode wcharczuk

repo: wcharczuk/go-chart


text:
[3] Store last directories

Store the last directories so that the default directory for the directory dialog used to select the spawnlist folder is the parent directory of where it was last. Do a similar thing for the file dialog in charge of selecting the VPK.

Addressed by Pull Request #6

repo: wciesialka/spawnlist-generator


text:
Mesos Guide: update environment variable for .25

After following the tutorial, using the "executor_environment_variables" to set {"DOCKER_HOST":"unix:///var/run/weave/weave.sock"} so mesos uses weave, which worked well with mesos 0.23, I tried it in the staging environment where we're testing mesos 0.25, where it didn't work at all.
Looking at the logs, I saw it was containers were started using /var/run/docker.sock or whatever the default docker socket was.
I don't know when exactly this changed, but in 0.25, I was able to get it working by writing "/var/run/weave/weave.sock" to "docker_socket".
Thought you'd like to note this in your docs (if you haven't already).

This doesn't depend on the version of Mesos, but the version of Weave instead. However, I though the socket path has changed in master (and about to be part of 1.2 release), but will check now.

Ok, so Weave v1.1.1 maintains compatibility and has a symlink from /var/run/weave.sock to /var/run/weave/weave.sock...

I don't know when exactly this changed, but in 0.25, I was able to get it working by writing "/var/run/weave/weave.sock" to "docker_socket".

I've overlooked this... Basically they just have added --docker_socket flag now, which is passed as -H and precedes DOCKER_HOST.

MESOS-3187

I have tried to use the --docker_host option to start the slave, as per MESOS-3187 and that doesn't work. Mesos 0.25 says that is an unrecognized option.
I have the same issue trying to attach the Weave socket.

@stephentknight thanks for your comment... We've been back and forth on this, I've checked the code and it currently sets MESOS_DOCKER_SOCKET=/var/run/weave/weave.sock as an environment variable, so that should definitely work.

authors: abuehrle errordeveloper stephentknight

repo: weaveworks/guides


text:
Conntrack XML parsing is consuming a lot of CPU

See https://github.com/weaveworks/scope/pull/1985#issuecomment-258826860

@alban Suggests replacing the conntrack command (and in turn parsing it's XML output) by talking to the kernel directly through a Netlink socket.

Found https://github.com/typetypetype/conntrack but the status is not really reassuring ...

Using netlink is going to be a bit more work than I originally expected due to the incomplete Golang support and my almost total ignorace about netlink until yesterday.

https://github.com/vishvananda/netlink doens't support Conntrack directly (I created https://github.com/vishvananda/netlink/issues/171)
https://github.com/typetypetype/conntrack/ is in dubious state (I tested it and seems to work though) and doesn't fully support flows either. There's Follow() which reads flows into Conn. However Conn lacks the Orig side of the flow and there is no simple or public way to send commands to conntrack.

My plan is to fork https://github.com/typetypetype/conntrack/ to reuse all the parsing but it may be more sensible to bite the bullet and implement https://github.com/vishvananda/netlink/issues/171 (which I think would take a much longer time). @awh Thoughts?

After an offline discussion with @awh I've confirmed that implementing a netlink protocol is a non-trivial task and that we should instead try improving parsing first. I will proceed in the following order, reevaluating performance after each step:

Try to find a better performing XML library
Try parsing the textual output of conntrack (i.e. without -o xml)
Use netlink

Try to find a better performing XML library

I have failed to find an alternative XML library at all. Moving on to parse the conntrack text manually.

Huh, I thought codec did it, but it doesn't.
https://godoc.org/github.com/ugorji/go/codec
On Tue, 15 Nov 2016 at 12:53, Alfonso Acosta notifications@github.com
wrote:

Try to find a better performing XML library
I have failed to find an alternative XML library at all. Moving on to
parse the conntrack text manually.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/weaveworks/scope/issues/1991#issuecomment-260633194,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAbGhQ1NpJUVmd3I1U4XyyBHu7u5WPDsks5q-aspgaJpZM4KrLIo
.

Parsing the line-based output of conntrack is a pain in the ass because some (at least 4) fields are optional. This means I cannot simply use Scanf.
I started coding a manual parser for it, but I am not sure it's worth the effort compared to spending time on https://github.com/vishvananda/netlink

Does https://github.com/lucsky/go-exml help?  Do you know what bit of the
xml parsing is the overhead?
On Thu, Dec 15, 2016 at 12:35 PM, Alfonso Acosta notifications@github.com
wrote:

Parsing the line-based output of conntrack is a pain in the ass because
some (at least 4) fields are optional. This means I cannot simply use Scanf.
I started coding a manual parser for it, but I am not sure it's worth the
effort compared to spending time on https://github.com/vishvananda/netlink
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/weaveworks/scope/issues/1991#issuecomment-267317377,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAbGhU18Q3lWAs1rPOkDdknkxZs60PxPks5rITP-gaJpZM4KrLIo
.

Do you know what bit of the xml parsing is the overhead?

IIRC string allocation/gc is the issue. Due to golang's lack of interns or a proper generational GC.

If that is the case, you could parse the IPs straight into unit32s (or
net.IPs), and the Proto, Direction and State into a enum etc
On Thu, Dec 15, 2016 at 12:43 PM, Matthias Radestock <
notifications@github.com> wrote:

Do you know what bit of the xml parsing is the overhead?
IIRC string allocation/gc is the issue. Due to golang's lack of interns or
a proper generational GC.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/weaveworks/scope/issues/1991#issuecomment-267318701,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAbGhYoIbW2w4x1VwNx_0H7mJEE3Lsjaks5rITXegaJpZM4KrLIo
.

Note that in previous cases of encoding / decoding overhead, its been the
reflection thats the problem, not allocations (cf report structure).
On Thu, Dec 15, 2016 at 1:11 PM, Tom Wilkie tom@weave.works wrote:

If that is the case, you could parse the IPs straight into unit32s (or
net.IPs), and the Proto, Direction and State into a enum etc
On Thu, Dec 15, 2016 at 12:43 PM, Matthias Radestock <
notifications@github.com> wrote:

Do you know what bit of the xml parsing is the overhead?
IIRC string allocation/gc is the issue. Due to golang's lack of interns
or a proper generational GC.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/weaveworks/scope/issues/1991#issuecomment-267318701,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAbGhYoIbW2w4x1VwNx_0H7mJEE3Lsjaks5rITXegaJpZM4KrLIo
.

As I understand it, for the xml parsing the string allocation/gc happens mainly due to tags and attribute keys, e.g. if you have a document containing 500 <meta> tags, that's 500 allocations, and 500 items of garbage, not one.

How dumb: https://golang.org/src/encoding/xml/xml.go?s=6817:6857#L1146
On Thu, Dec 15, 2016 at 1:16 PM, Matthias Radestock <
notifications@github.com> wrote:

As I understand it, for the xml parsing the string allocation/gc happens
mainly due to tags and attribute keys, e.g. if you have a document
containing 500  tags, that's 500 allocations, and 500 items of
garbage, not one.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/weaveworks/scope/issues/1991#issuecomment-267324869,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAbGhf_UqOIgCYYkkyWessfFFa77aJsuks5rIT2-gaJpZM4KrLIo
.

I could create a parser with something like https://github.com/prataprc/goparsec
Maybe I could also give https://github.com/moovweb/gokogiri a try

Does https://github.com/lucsky/go-exml help?

It doesn't promise any performance improvements plus sits on top of a standard Go encoding/xml/Decoder  so I am doubtful

authors: 2opremio rade tomwilkie

repo: weaveworks/scope


text:
OpenShift Wrong Kubelet Port

Hi tried running through the install instructions for OpenShift and there were a few issues:

I had to modify all the scope.yaml namespace instances to weave-scope instead of weave
The agent is hard coded to look for the kubelet on port 10255 when on OpenShift it runs on 10250.

I was able to get past the first issue by manually changing the YAML, but there's no ConfigMap or Env Variable etc to modify what kubelet port the agent tries to use.

Hi, thanks for the report!
Can you clarify why you needed to change the namespace?  We run all Scope probes in the weave namespace in our own clusters, but we don't run OpenShift.
Would you like to make a PR to improve the docs for OpenShift?
If you set KUBERNETES_NODENAME it won't bother trying to call kubelet - you can do it in the yaml something like this:
    spec:
      containers:
        env:
        - name: KUBERNETES_NODENAME
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: spec.nodeName

This way is more efficient too.

@bboreham , You can find the solution here on the OpenShift Documentation. https://docs.openshift.org/latest/architecture/infrastructure_components/kubernetes_infrastructure.html

Sorry, @mikerr1111, I couldn’t connect that to any of the foregoing. Please explain how it fits.

The agent is hard coded to look for the kubelet on port 10255 when on OpenShift it runs on 10250.

You can configure the kubelet port to connect to with --probe.kubernetes.kubelet-port.

authors: Mikerr1111 bboreham johnfosborneiii rade


text:
Offensive project name

Please consider renaming this project. The term "spack" (from the etymology "spastic" -> "spacker") is a highly offensive term for someone with cerebral palsy, in British English.
Naming your project "r spack" is far too close to this insulting term for such differently able people, and puts your project in breach of its own code of conduct.
Thank you for your consideration on this matter.

you can treat it as rs-pack

We took your tip very seriously, consulted with a number of relevant linguists, and investigated the situation of similarly named open source projects. We don't think it's necessary to change the project name at this time.

authors: ghost hardfist

repo: web-infra-dev/rspack


text:
chore: use zx to replace xtask

Related issue (if exists)

Summary

🤖 Generated by Copilot at 5abf645
This pull request removes the xtask crate and replaces its functionality with node scripts for benchmarking the rspack crate with different versions of the three.js library. It also updates the code owners file, the TypeScript config file, and the cargo config file to reflect the changes. Additionally, it adds a utility script to check the workspace root and a typecheck script to verify the scripts folder.

Walkthrough

🤖 Generated by Copilot at 5abf645

Remove xtask crate and replace its commands with node scripts for benchmarking (link, link, link, link, link, link, link, link, link)
Refactor code owners specification to use cargo config feature (link, link)
Add utility and type checking scripts for node scripts (link, link, link, link)
Improve TypeScript compiler options for scripts (link, link, link, link)

!bench

!bench

@IWANABETHATGUY The benchmark CI runs successfully. You are free to review this PR.

@IWANABETHATGUY The benchmark CI runs successfully. You are free to review this PR.

Are you sure ? baseline now is 861 times slower than current branch


text:
perf: optimize dependencies size

Summary

delete tailwindcss in @rspress/core, save 11.2MB space.
delete @modern-js/utils in default document scene, save 6.14MB space.
add fs-extra(109 kB), chalk(42.7kB), execa(293kB) in @rspress/shared, which were provided by @modern-js/utils before.
change globby to pre-compiled output in @rspress/core, size: 585 kB -> 141 kB

Related Issue

Checklist

[ ] I have added changeset via pnpm run change.
[ ] I have updated the documentation.
[ ] I have added tests to cover my changes.

@rspress/core still depend on tailwindcss, should we delete it?

@rspress/core still depend on tailwindcss, should we delete it?

Yeah, https://github.com/web-infra-dev/rspress/pull/471

repo: web-infra-dev/rspress


text:
Migrate to V2 version

Only for public dashboard and charts

https://app.web3go.xyz/#/MoonbeamPublicDashboard

[X] Dapp Activity

https://app.web3go.xyz/#/MoonriverPublicDashboard

[x] Dapp Activity

In progress moonriver

Finished moonriver


text:
pre-commit: SwiftLint: Disable failing tests

Summary of Changes
Fixes # (if applicable - add the number of issue this PR addresses)
Enable SwiftLint in GitHub Actions but disable the failing tests that cannot be auto-fixed so that we do not backslide on the tests that currently pass.
Test Data or Screenshots
By submitting this pull request, you are confirming the following:

I have reviewed the Contribution Guidelines.
I have performed a self-review of my own code.
I have updated my repository to match the develop branch.
I have included test data or screenshots that prove my fix is effective or that my feature works.
I have checked that all tests work and swiftlint is not throwing any errors/warnings.

I'm not sure I understand these changes in combination with the description you gave:

disable the failing tests so that we do not backslide on the tests that currently pass

I do not see anything being disabled here.

Yes.  Moving to Draft status so I can see/fix/disable errors in GHA runs.

GitHub Actions can run pre-commit in 25 seconds if we remove SwiftLint
SwiftLint can run n 25 seconds on the macOS-12 GHA job.
Future pull requests can remove more items from disabled_rules in .swiftlint.yml.

Please let me know what changes should be made.

On --fix GitHub Actions will not write the fixed code into a commit (like pre-commit.ci would) so the fixes done in GitHub Actions are being lost in the ether. If swiftlint is confident that it can make a simple text correction (add a whitespace, etc.) then the error is probably not worth disabling.

I see only one really useful use case for the pre-commit.ci and its feature of fixing and pushing the results of swiftlint --fix back to the branch: if we will have contributions from other people that will not follow the code style requirements it can be fixed to some extent by the CI.

Correct.

What else is required on this pr?

What else is required on this pr?

Reviewing now. Will let you know soon.

@yaroslavyaroslav Please, be informed about the pros of using pre-commit CI: https://github.com/web3swift-team/web3swift/pull/781#issuecomment-1435706681

@cclauss Done with the review. Looks good.
Now waiting for CI to complete.

Nice.  It will be good to have guardrails in place on those SwiftLint tests that already pass.

authors: JeneaVranceanu cclauss


text:
inline css support

 test
Is it possible to support inline style declarations?

Its working inside html in inline style tag, but sometime color disappearing. @vigo

authors: Bulforce arturparkhisenko

repo: webBoxio/atom-color


text:
add this image full screen to the value of values slide

And also create a slide under close with this, which we will follow up with slide on our discussion site. Maybe you can come up with a screen shot of our discourse site for that too?
https://pixabay.com/en/milky-way-andromeda-stars-galaxy-923801/

Got it! See #100, commit d0fc0e7.
PR includes redpill (FRAG) notes and the above ticket. 🛠

authors: webappzero whilei

repo: webappzero/the-value-of-learning


text:
Корректное закрытие HTTP соединений

Исправление, корректно закрывающее HTTP соединение к серверу dadata.
Без него можно легко получить ошибку httpErr: socket: too many open files при обработке больших объемов данных.

I agree, thanks.

repo: webdeskltd/dadata


text:
[TASK]: Authentication middleware

Task Summary
Next Auth's middleware should be implemented to protect frontend and backend API routes.
Acceptance criteria

[ ] The creation of src/middleware.ts and exporting next-auth/middleware from that file
[ ] Applying the middleware on respective paths (ex., dashboard, and backend API routes)

Any Additional Context

References

Next Auth middleware
Next.js middleware

I can tackle this issue a bit later in the week with more time off. However, feel free to get started on this if anyone wishes!

I will work on it

repo: webdevcody/code-racer


text:
applyPrototype corrupts prototype chain of native objects

Return value of saveScreenshot (Buffer) is incorrect due to adding an object to the prototype chain via Object.create. This makes all the native methods on Buffer fail, including the writeFileSync example in the docs. Adding Buffer.isBuffer(result) to the early-return condition fixes this case, though avoiding Object.create might be more robust. :-p

@acthp thanks for filing the issue. I made sure that we don't overload buffer results.

though avoiding Object.create might be more robust

I don't think we can do that. It allows us to inspect command results directly:
console.log(browser.click(".selector"));
// returns { "status": 0, ... }

and chain results:
browser.click(".selector").getTitle();

However I believe this could be limited for element commands only since you usually only work with those results to chain with calls with other commands. I am not sure though yet if this limits other features. However overwriting the prototype of the plain result object shouldn't bring any side effects.

authors: acthp christian-bromann

repo: webdriverio/wdio-sync


text:
Logo sizing bug in Firefox

Firefox: super small

Chrome: normal size

I checked Edge and Safari too, logo is normal size, so it seems to be Firefox.

The latest homepage update fixed this issue.


text:
Remove copy webpack-stats from dockerfile

Trying to copy webpack-stats.json fails CI on deploy now that webpack is no longer used

Revert this if you don't like it. Merging without approvals as its a veery minor fix and I'm not expecting that many people to be active atm.

repo: webkom/committee-admissions


text:
Face recognition example does not work locally on latest Chrome Canary: Invalid signature.

Hi! This is a really cool project and I am rewriting https://github.com/prouast/heartbeat-js using the face recognition example.
However, when getting started with the code at https://github.com/webmachinelearning/webnn-samples/blob/master/face_recognition/ - I ran into the following bug:

Specifically, Invalid signature. displays at the top of Chrome Canary.
Steps I followed:

forked the repository
git clone
npm install to install vite dependencies
npm run start

Then navigate to https://localhost:5173/ in Chrome Canary, and receive the error.
Any help on debugging this to enable remote vital signs monitoring with WebNN? Thank you!

@jaanli, WebNN-Samples requires to access to  weight files located at test-data which is a submodule of this repo.
I suppose you forgot download the test-data to local,
git clone --recurse-submodules https://github.com/webmachinelearning/webnn-samples

That solved it, thanks so much @Honry !!

authors: Honry jaanli

repo: webmachinelearning/webnn-samples


text:
Clean up attribute DOM.js src empty checks

Cleanup/code reduction from https://github.com/webmixedreality/exokit/pull/491.

looks good

authors: modulesio ngokevin

repo: webmixedreality/exokit


text:
Custom Webpack CSS-loader “localIdentName” Query Tag Placeholders

I originally asked this question on Stack Overflow but it seems like a lot of people keep pointing me back to asking the questions on the loader's repo, so hopefully this is a good place to ask.
I'm looking to run my :local style class names through a custom method that I've written.  In the documentation, I see I can use query tag placeholders like: [path], [name], [local], and [hash:base64], but I couldn't find any information on how to write my own.
Is this possible?

I created my own, [dir] and [sourceHash] in a fork: https://github.com/Aluxian/css-loader
Take a look at the last commit to see what I changed.

I was afraid of that.. to the fork machine...
Thanks for the comments/head-start @Aluxian, appreciate it!

I would love to have a [dir] tag. My folder structure for a notional ButtonControl component consumed from an private npm package looks like this,
/button-control
  - index.js
  - index.css

I'd like a generated classname scheme that was at least somewhat human readable in dev tools. It's not use using [name] since that always comes out as index which is not unique. I can use [path] but since this is coming from node_modules I end up with class names like,
node_modules--npm-scope-private-package-some-sub-sub-folder-button-control-label-h4sh

... which is a bit, erm, verbose. So I need [dir] tag that resolves to the enclosing folder. Then I could have a classname like [dir][local][hash]:
button-control-label-h4sh

Would this project be open to a PR that added [dir]?

I have the same problem as @jedrichards, would appreciate that feature!

I asked if they'd be willing to accept a PR this, but no response :(

@jedrichards @caesarsol according to this issue: https://github.com/webpack/css-loader/issues/246
it looks like [folder] already provides the parent directory name

Thanks! [folder] does indeed work. We should document this, its obviously a common question...

@jedrichards Interally, css-loader uses webpack/loader-utils#interpolateName.
You might want to peruse your own node-modules directory to determine the exact version you're using, but here are the current (0.2.15) features it supports:

The following tokens are replaced in the name parameter:

[ext] the extension of the resource
[name] the basename of the resource
[path] the path of the resource relative to the context query parameter or option.
[folder] the folder of the resource is in.
[emoji] a random emoji representation of options.content
[emoji:<length>] same as above, but with a customizable number of emojis
[hash] the hash of options.content (Buffer) (by default it's the hex digest of the md5 hash)
[<hashType>:hash:<digestType>:<length>] optionally one can configure

other hashTypes, i. e. sha1, md5, sha256, sha512
other digestTypes, i. e. hex, base26, base32, base36, base49, base52, base58, base62, base64
and length the length in chars

[N] the N-th match obtained from matching the current file name against options.regExp

Aha loader-utils. Didn't even know that was a thing. Now makes sense it should be the place to look for such information. Thanks for the tip off.
Do you think it would be worth linking to that part of the loader-utils docs from this part of the readme?

You can configure the generated ident with the localIdentName query parameter (default [hash:base64]). Example: css-loader?localIdentName=[path][name]---[local]---[hash:base64:5] for easier debugging.

I think at least some reference to the possible options would be great, and linking might be the best way to avoid drift between the css-loader README and loader-utils implementation.

There is a way to convert [folder] name from CamelCase (I prefer this for component folders... ) to kebab-case (... and this for css classes)?
Can we provide a custom handler?

Is it at all possible to include the entry point name as part of the localIdentName? Currently [name] refers to the file name rather than the entry point being built out.

@Splact @navgarcha I think these questions (and any further questions about localIdentName) might receive a better response on https://github.com/webpack/loader-utils#interpolatename, the actual source of name interpolation.

I've had a look around the interpolateName stuff and im still none the wiser how to get the entry chunk name as part of the localIdentName - could some one point me in the right direction?

With Webpack 2 my use case has been solved with the ability to set a custom getLocalIdent function.  Closing the issue.

@soluml can you please show the code?

Sure.. from the docs:
  test: /\.css$/,
  use: [
    {
      loader: 'css-loader',
      options: {
        modules: true,
        localIdentName: '[path][name]__[local]--[hash:base64:5]',
        getLocalIdent: (context, localIdentName, localName, options) => {
          return 'whatever_random_class_name'
        }
      }
    }
  ]
}```

Ah, okay. I wanted to use this options with extract-text-webpack-plugin, but seems like it is not possible now.

I'm also wondering the same, why localIdentName is still needed. On a side note, I don't see anyone using something like ```return '_' + (nextLocalIdent++).toString(36)` to drastically reduce class name length.

localIdentName gets passed as a parameter to the getLocalIdent function. So it seems reasonably possible that someone may want their getLocalIdent function to behave differently depending on what localIdentName is set to, e.g. to do something similar to what the existing localIdentName generator does, but with one or more differences.

authors: Aluxian Splact bendman caesarsol dpoineau jdunk jedrichards mikeaustin mqklin navgarcha soluml

repo: webpack/css-loader


text:
Unexpected behaviour during error handling

From @s-panferov on July 8, 2015 14:42
I am the author of https://github.com/s-panferov/awesome-typescript-loader and I have a problem with my async loader:
Pseudo-code:
let callback = this.async();

/* inside promise handler */
try {
    callback(null, result.text, sourceMap);
} catch(e) {
    console.error('Caught', e)
    // I'm here! What I need to do in that case?
}

Console output:
Caught { [ModuleParseError: Module parse failed: /Users/panferov-s/Workspace/arui/node_modules/react-hot-loader/index.js!/Users/panferov-s/Workspace/awesome-typescript-loader/dist/index.js?compiler=ntypescript&rewriteImports=arui&module=commonjs!/Users/panferov-s/Workspace/arui/src/popup/common/popup.ts Line 112: Unexpected token ,
You may need an appropriate loader to handle this file type.
|             || nextAttachment !== attachment) {
|             this.setState({
|                 attachment: ,
|                 targetAttachment: ,
]             });

/** stripped */

Versions:
    "webpack": "^1.10.1",
    "webpack-dev-server": "^1.10.1"

The big problem here is that compilation freezes in webpack-dev-server
Copied from original issue: webpack/webpack#1232

From @shama on July 14, 2015 21:59
It is because you're informing the loader that it is async. Which means it will wait for you to call callback() to continue. Upon an error, you're not calling the callback() so it hangs waiting for it.
The 1st argument of the callback is for errors: callback(err) instead of null. Although it is likely you can just remove that try catch and let webpack deal with the error though.

From @s-panferov on July 15, 2015 7:56
@shama 	you don't understand the problem. I call the callback, but the call throws an exception that takes place in some other loader or inside webpack core (e.g. if syntax error is in the file) and the error propagates inside my loader (I can catch it with try-catch or with Bluebird's catch handler). But I can't call the callback another one time with this error, because it throws an exception (callback was already called) in that case!
If I leave the error as-is, Bluebird thows an Unhandled exception error.
In each case webpack freezes and I don't know what to do.

From @shama on July 15, 2015 15:25
Ah you're right sorry. Could you post a full stack trace or even better an example repo that duplicates the issue so I can take a look? Thanks!

From @s-panferov on July 15, 2015 16:45
@shama, ok, I'll try to provide some example.

From @s-panferov on July 18, 2015 9:39
I was because bail: true was written in my config file.
So I have to write https://github.com/s-panferov/awesome-typescript-loader/blob/master/src/index.ts#L357-L362 inside my async loader. The problem is solved, but I thing that the behaviour of the callback function in bail mode must be documented somewhere.

From @bebraw on November 14, 2015 18:5
@s-panferov Can you look at that documentation bit so we can get this closed?

From @shama on July 18, 2015 15:2
@s-panferov Oh nice find! The documentation is openly editable to anyone. Would you mind adding a note about it here http://webpack.github.io/docs/configuration.html#bail? Thanks!

Same section under discussion on webpack.js.org -- editable here.

Let's close.

authors: bebraw pksjce skipjack


text:
Move module.exports to syntactically valid positions

Fixes #228

Moves module.exports to syntactically valid positions (e.g. after const config = {...} is defined).
In some cases, removes module.exports line entirely when it has already been written at least once in the doc (as per @timdorr 's suggestion)

Thanks. 👍

authors: bebraw tizmagik


text:
How can I solve watching problem in webpack?

I really hope, you can help me.
When I import a module in the index.js in a following way: ( import Test from './src/test'; ) Webpack recognizes the .web.js extension and uses it. However, if I make changes in the file system for instance I delete or rename this file, the webpack will notice that the file is missing. Nevertheless, it doesn't recompile and doesn't use the other file opportunity (test.js).
I have used webpack 3.6.0 and I tried to use in Watch mode, too. But unfortunately it doesn't work.

It looks like you just deleted/ignored our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please open a new issue with filled issue template. Also make sure your issue is not a question. Questions should be posted on Stack Overflow.

repo: webpack/webpack


text:
Allow rules/Conditions to be included/excluded based on package.json contents

Feature request

Currently, webpack's resolver requires the package.json of every file that is imported (module). This data is however not exposed to the user through the configuration. So module.rules can't be configured based on for example a certain flag in package.json, or based on engines.
What is the expected behavior?
The Condition logic should allow for something like package or packageJson which gets the package.json contents passed in and works similar to issuer.
Another case for this is the externals configuration key, if a function is passed it should receive the package.json contents as a parameter.
What is motivation or use case for adding/changing the behavior?
In Next.js we want to transpile node_modules based on their usage in React components, but it might not be the best idea to run Babel over every possible import, for example when the user imports a gigantic library that doesn't need compilation at all). So we're investigating alternatives like providing a key in package.json of a module to opt-in to compilation using Babel.
How should this be implemented in your opinion?
As defined above in expected behavior. The naming can be better though 👍
Are you willing to work on this yourself?
yes

implemented in https://github.com/webpack/webpack/releases/tag/v5.0.0-beta.23
add Rule.descriptionData to allow matching data from the package.json

I saw, awesome work 🎉

authors: timneutkens vankop


text:
Add error callback support to require.ensure

What kind of change does this PR introduce?
Fixes https://github.com/webpack/webpack/issues/758 by adding support for an error handling callback to require.ensure

Did you add tests for your changes?
Yes, tests added in test/cases/parsing/issue-758
These were borrowed/adapted from https://github.com/webpack/webpack/pull/3247.

If relevant, link to documentation update:

Summary

System.import already supports error callbacks, but require.ensure is still useful for a couple of reasons:

Supports chunk naming (https://github.com/webpack/webpack/issues/3132)
Supports recursive code splitting (https://github.com/webpack/webpack/issues/3364#issuecomment-273983958)

Does this PR introduce a breaking change?
No. require.ensure still supports chunk naming with the old 3 argument style.

Other information

I was thinking it'd also be good to add a couple of tests to test/cases/chunks possibly under test/cases/chunks/named-chunks but I could use some pointers on how the sync stuff is working in the existing tests.
I'm not quite sure what these lines are doing:
var sync = false;
//...
sync.should.be.ok();

Wow what an incredible first PR to take on btw.

I've been percolating on this issue for quite a while! I had actually forked the awesome work of @richardscarrott (https://github.com/richardscarrott/require-error-handler-webpack-plugin/pull/5) and adapted/rewritten his work to make it work with Webpack 2.1.0-beta.25 a few months ago, and then realized it totally broke with the changes made Webpack internals since then.
This motivated me to make a new PR for require-ensure error callbacks so I don't have to keep maintaining the fork! :-)
If this PR gets approved, I'd also really love to make a PR on the bundle-loader to also add error callback support there. @richardscarrott already reworked the bundle-loader to handle this (https://github.com/richardscarrott/require-error-handler-webpack-plugin/blob/master/src/BundleLoader.js) and I have a corresponding fork created (https://github.com/jharris4/bundle-loader)

Is there anything else I can do to push this along to get it merged?
We're already using the require.ensure error callbacks in production, so to allow us to move from Webpack 1.x to 2.2 I've created this plugin which enables the changes: https://github.com/jharris4/require-ensure-error-webpack-plugin.
It has a standalone example of the changes in action if anyone's curious...

@TheLarkInn @sokra Still curious to know if there's a reason for not merging this... :-)
I'd be happy to take on any related doc updates, or adding tests for other features that depend on require.ensure if that'd help move things along.

Thanks

Awesome! I think the bundle-loader needs a PR to work with this now though.
I'll try to get to that when I have some spare time.

authors: TheLarkInn jharris4 sokra


text:
Duplicate import removed

There  were two lines in the code for the same  purpose. Also added an additional if condition to check whether there is more than one CLI is installed. If there is more than one CLI , the new code will bypass else if condition from the old code.

What kind of change does this PR introduce?
code refactoring

Did you add tests for your changes?
N/A

Does this PR introduce a breaking change?
N/A

What needs to be documented once your changes are merged?

This has no benefit and is worth in my opinion, because of additional nesting introduced

authors: codognito sokra


text:
Improve browserDetection logic/structure

Description
Clean up the browserDetection structure in utils.js

apparently this also mis-detects safari as chrome. Now imo it is rather silly for safari/webkit to use the same prefixed webkitRTCPeerConnection that Chrome uses...

Since I found this to be related to the issue I found thought of just commenting in here. Looks like adapter_core.js breaks on IE. If the utils returns browserDetails null it breaks if (browserDetails.version < browserDetails.minVersion). Possibly in the switch statement that follows as well. Need to deal with unsupported browsers a tad better.

authors: KaptenJansson fippo vganapathy-lifesize

repo: webrtc/adapter


text:
Support for WKWebView?

Browsers and versions affected
WKWebView on ios 11
Description
I see that ios Safari 11 is now supported but I have an ionic app that I believe uses WKWebView. So I am still unable to get getUserMedia which also causes PeerJS to fail. I'm not super savvy in this area but I'm wondering if there is currently support, a workaround, or plans to support WKWebView.
Steps to reproduce
Open inspector on ionic app. Trying to find getUserMedia on navigator.
Expected results
See getUserMedia
Actual results
getUserMedia is not a member of navigation.

getUserMedia is not supported in WKWebView right now: https://bugs.chromium.org/p/chromium/issues/detail?id=783220

While safari just added support to it, Apple gives usually one release (one year) before releasing the corresponding framework. Do not expect the web view framework to support webrtc before fall next year.

authors: agouaillard fippo pdxwebdev


text:
Frozen string error during pull

After updating WTI CLI to 3.0.0, I now get an error trying to pull strings for an iOS project. Everything works fine when rolling back to version 2.8.4.
Console output:
# Pulling files on iOS
can't modify frozen String: "..."
can't modify frozen String: "..."
can't modify frozen String: "..."
can't modify frozen String: "..."
can't modify frozen String: "..."
can't modify frozen String: "..."
Pulled 55 files at 247 files/sec, using 10 threads.

Ruby version: 3.0.6
CLI version: 3.0.0

Looks like all string literals were implicitly frozen here without calling "".dup before using the << operator.

Thanks for reporting the issue, it’s been fixed in #288. I'll cut a new release momentarily.

Wow, that was fast ⚡, thank you!

authors: antoinelamy edouard

repo: webtranslateit/webtranslateit


text:
[Feature Requirement] Deployment without domain name

. /webvirtcloud.sh env

Requires the user to enter the domain name
I don't want to use a domain name and only use an IP address with different ports to display the page that corresponds to your
BASE_DOMAIN=webvirtcloud.app
API_DOMAIN=api.webvirtcloud.app
ASSETS_DOMAIN=assets.webvirtcloud.app
CLIENT_DOMAIN=client.webvirtcloud.app
MANAGE_DOMAIN=manage.webvirtcloud.app
CONSOLE_DOMAIN=console.webvirtcloud.app

I don't want to use a domain name either. What should I do？
@retspen

Hello,
Give me some time. I'm working on a new feature right now, when I'm done with it I can focus on this feature.

ok, thank you

This would be a nice feature, as of now is there a workaround for this ?

Haven't seen any progress on the adaptation for a while

This would be a nice feature, as of now is there a workaround for this ?

Can you to try last release? We moved all setting to one domain or IP address. Let us know if it works.
Thanks!

I will test later

First, there was no problem during the installation, but the problem appeared after the installation
If I install Controller using the IP address of this server, then it forces HTTPS but shows error reporting SSL_ERROR_INTERNAL_ERROR_ALERT.

Caddy doesn't support IP address and self-signed certificate but I added some trick with service nip.io. Added info to README

Can't it support https similar to PVE's default install? Even if the certificate is not secure.

This is a limitation of the Caddy revere proxy server. You can use Nginx with self-signed certificates on top of it

I tested using nip.io and everything works fine, but using a pure IPV4 address still forces the https display to be an exception, maybe because I didn't enter an IP address and used the default localhost directly? For the time being I have no other questions or needs, this thread is closed.

As an additional note, the instructions at https://webvirt.cloud/docs/installation/setup-controller are somewhat outdated and need to be updated accordingly.

authors: TVKain retspen spiritLHLS ytjoe

repo: webvirtcloud/webvirtcloud


text:
🛑 DragonBoat Times is down

In 725c00d, DragonBoat Times (https://www.dragonboattimes.com) was down:

HTTP code: 521
Response time: 107 ms

Resolved: DragonBoat Times is back up in 2dbd6c6 after 1 hour, 8 minutes.

repo: webworldview/uptime


text:
🛑 Jeff with Susan is down

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

HTTP code: 521
Response time: 119 ms

Resolved: Jeff with Susan is back up in 6300854 after 1 hour, 41 minutes.


text:
fix(editor): make the form update correctly

What is the PR about?
Fix the error with removing the item from array type property.
What is the code about?

Change the properties update logic
Before, it will call FieldModel.prototype.update when remove a property of array or object. But, it just update the value by keys instead of removing the key. So now I change to put the existed keys and values to new array or object, then the others will be removed.
Make the form can be controlled
When remove the items of array, the sort of items are changed but the form would not be updated.

have conflict

authors: MrWindlike tanbowensg

repo: webzard-io/sunmao-ui


text:
[FEAT]WorkPro:FileBox

Please make sure you have read the Wechaty Puppet Service: WorkPro from Wechaty Official Website before you continue writing this issue.
IMPORTANT
DO NOT post your token in the issue. If we need to investigate the behavior of certain token, we will provide a private contact route.
Describe the bug
A clear and concise description of what the bug is.
Info

Platform[e.g. Windows/Mac/Linux]:
Runtime version[e.g. node/JAVA]:
Wechaty version:
Wechaty Puppet version:

To Reproduce
Steps to reproduce the behavior:

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

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Please describe your problem.

因为没有描述问题内容，关闭issue。

repo: wechaty/puppet-supports


text:
added a blog

Fixes # .
Make sure these boxes are checked before creating your pull request -- thank you!

[ ] Add Blog Header, including title, author, date.
e.g.

---
title: "'Score Your Face Photo' a ML&Wechaty practice"
author: huyingxi
image: /assets/2020/your-blog-title/teaser.jpg
---

YOUR_FIRST_SENTENCE_SHOULD_BE_A_SUMMARY_FOR_YOUR_POST

[ ] Keep all filenames & url as lowercase, and use - to connect words instead of space. e.g. 2017-10-06-wechat-pc-impactor instead of 2017-10-06-WeChat PC Impactor,
[ ] Embed the photo & video before publishing, save all external file to the blog /assets/2020 directory.
[ ] Add teaser image for the blog
[ ] Add your self as an author to the author data file at https://github.com/wechaty/wechaty.js.org/blob/master/_developers/YOUR_GITHUB_USERNAME.yml with your GitHub username. And please also remember to reference yourself with the Github username in your blog post, so that we can have nice author information besides your blog after we published it!

See more

 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 ovarte


text:
添加博客链接

Please make sure to check the following boxes creating your pull request, thank you very much!

[x] Add Blog Header, including title, author, image, categories, tags, etc.
For example:
---
title: Your Great Blog Title
author: your_github_id
categories: project
tags:
  - python
  - padlocal
image: /assets/2021/02-your-blog-slug/teaser.jpg
---

One line bio

Your blog post content Your blog post content
Your blog post content Your blog post content
Your blog post content Your blog post content

It will be easier to start drafting your post by using a existing post file as your template, for example, this one

[x] Keep all filenames lowercase, and use - to connect words instead of space. e.g. 2017-10-06-wechat-pc-impactor.md instead of 2017-10-06-WeChat PC Impactor.md

[x] Embed video/pdf from YouTube/Bilibili/local (if there's any) by using {% include iframe.html src="URL_or_PATH" %}. (Learn more about how to embed file/url in the post by reading this blog post

[x] Save photo to local before publishing, to a folder named by ${MONTH}-${YOUR_BLOG_SLUG}/ under /assets/2021/ directory.

[x] Select a beautiful and meaningful teaser image for your blog

[x] Create your contributor profile (if you are a first time contributor)
For excample:

jekyll/_contributors/lijiarui.md

---
name: Jiarui LI (李佳芮)
site: https://lijiarui.github.io
bio: 句子互动创始人 & CEO，微软人工智能最具价值专家 (AI MVP)
avatar: /jekyll/assets/contributors/lijiarui/avatar.png
email: rui@juzi.bot
twitter: https://weibo.com/u/2175505900
---

Here is the example file:

lijiarui.md: https://github.com/wechaty/wechaty.js.org/blob/master/jekyll/_contributors/lijiarui.md
It will shown like this on wechaty website: https://wechaty.js.org/contributors/lijiarui/

To learn more about the contribute guideline, visit: https://wechaty.js.org/docs/contributor-program/

Thanks for adding the link for your great blog post to make new developers easy to getting started!

authors: dchaofei huan


text:
自动同意入群报错，提示不支持

Error handling room invitation: GError: Wechaty Puppet Unsupported API Error. Learn More At https://github.com/wechaty/wechaty-puppet/wiki/Compatibility
at WechatyImpl. (file:///D:/java/getting-started/server.js:247:26)
at WechatyImpl.emit (node:events:517:28)
at WechatyImpl.emit (file:///D:/java/getting-started/node_modules/wechaty/dist/esm/src/wechaty-mixins/gerror-mixin.js:31:30)
at PuppetWechat4u. (file:///D:/java/getting-started/node_modules/wechaty/dist/esm/src/wechaty-mixins/puppet-mixin.js:262:34)
at PuppetWechat4u.emit (node:events:517:28)
at PuppetWechat4u.emit (file:///D:/java/getting-started/node_modules/wechaty-puppet/dist/esm/src/puppet/puppet-skeleton.js:84:26)
at Wechat. (file:///D:/java/getting-started/node_modules/wechaty-puppet-wechat4u/dist/esm/src/puppet-wechat4u.js:365:26) {
code: 2,
details: 'Error: Wechaty Puppet Unsupported API Error. Learn More At https://github.com/wechaty/wechaty-puppet/wiki/Compatibility\n' +
'    at Module.throwUnsupportedError (file:///D:/java/getting-started/node_modules/wechaty-puppet/dist/esm/src/throw-unsupported-error.js:3:11)\n' +
'    at PuppetWechat4u.roomInvitationAccept (file:///D:/java/getting-started/node_modules/wechaty-puppet-wechat4u/dist/esm/src/puppet-wechat4u.js:673:23)\n' +
'    at WechatifiedUserClass.accept (file:///D:/java/getting-started/node_modules/wechaty/dist/esm/src/user-modules/room-invitation.js:66:39)\n' +
'    at WechatyImpl. (file:///D:/java/getting-started/server.js:247:26)\n' +
'    at WechatyImpl.emit (node:events:517:28)\n' +
'    at WechatyImpl.emit (file:///D:/java/getting-started/node_modules/wechaty/dist/esm/src/wechaty-mixins/gerror-mixin.js:31:30)\n' +
'    at PuppetWechat4u. (file:///D:/java/getting-started/node_modules/wechaty/dist/esm/src/wechaty-mixins/puppet-mixin.js:262:34)\n' +
'    at PuppetWechat4u.emit (node:events:517:28)\n' +
'    at PuppetWechat4u.emit (file:///D:/java/getting-started/node_modules/wechaty-puppet/dist/esm/src/puppet/puppet-skeleton.js:84:26)\n' +
'    at Wechat. (file:///D:/java/getting-started/node_modules/wechaty-puppet-wechat4u/dist/esm/src/puppet-wechat4u.js:365:26)'
}

8月来发现不支持了

bot.on('room-invite', async roomInvitation => {
try {
console.log("roomInvitation",roomInvitation)
await roomInvitation.accept()
console.log("同意")
} catch (error) {
console.error('Error handling room invitation:', error);
}
});

repo: wechaty/wechaty


text:
Delete typings.d.ts

Fix #2314

 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.

Thank you very much for your contribution!
You are welcome to join Wechaty Contributor Program
1. Join Wechaty Organization

You've invited System233 to Wechaty! They'll be receiving an email shortly. They can also visit https://github.com/wechaty to accept the invitation.

I have invited you to join our Wechaty GitHub Organization, please accept it by following the above message. (See also: wechaty/PMC#16)
2. Update Your Wechaty Contributor Profile

Please open Contributor Hall of Fame and add yourself to the end of the list, so that other contributors will know you better!
Please add yourself to our Website Contributors by creating a PR and refer to this PR link as well.

3. Join The Contributor Only WeChat Room
We also have a WeChat room for contributors only which can discuss Wechaty at a deeper level, you are welcome to join and if you are interested.
Please add @lijiarui wechat: ruirui_0914 and send her this pr link. She will invite you into Wechaty Contributor Room
Cheers!

authors: CLAassistant System233 huan


text:
ERROR in index.web.js from UglifyJs

通过weexpack  创建项目后，在执行npm run serve 时报以下错误
ERROR in index.web.js from UglifyJs
Unexpected token: name (urlParts) [index.web.js:3700,4]
已经创建 .babelrc文件 加入{ "presets": ["es2015"] }也不可用

一样，好像几个月前还可以的

我也遇到这个问题
weexpack create 项目名
cnpm install
weexpack run web
也出现
ERROR in index.web.js from UglifyJs
Unexpected token: name (urlParts) [index.web.js:3309,4]
ERROR in index.web.js from UglifyJs
Unexpected token: name (urlParts) [index.web.js:3311,4]
webpack: Failed to compile.
未找到解决办法

升级一下weex-toolkit
npm i weex-toolkit@latest -g
再执行weex update weexpack@latest就可以解决了，亲测有效

@erha19 还是不行。
weexpack -V
0.4.3
ERROR in index.web.js from UglifyJs
Unexpected token: name (urlParts) [index.web.js:3700,4]
Child html-webpack-plugin for "index.html":
chunk    {0} index.html 963 bytes [entry]
+ 1 hidden modules
webpack: Failed to compile

每次升级，会改进一些问题，缺又出现一些新问题。。。

在webpack配置项里把UglifyJsPlugin注释就行了
// new webpack.optimize.UglifyJsPlugin({minimize: true}),

Fixed https://github.com/weexteam/weex-toolkit/issues/165

现在是2017年12月16日，这个问题还没解决？

repo: weexteam/weex-pack


text:
Allocation Data Controller Methods Not Consistently Defined

Expected Behavior
Classes should have identical method names and definitions (e.g., same number/name of parameters).
Actual Behavior
The Allocation data controllers has the following methods:
1. request_calculate(self, node_id)
2. request_children(self, hardware_id)
3. request_delete(self, hardware_id)
4. request_insert(self, revision_id, **kwargs)
5. request_select(self, node_id)
6. request_update(self, definition_id)
7. request_update_all(self)

These should be re-defined as:
1. request_calculate(self, **kwargs)
2. request_select_children(self, node_id)
3. request_delete(self, node_id)
4. request_insert(self, **kwargs)
5. request_select(self, node_id, **kwargs)
6. request_update(self, node_id)
7. request_update_all(self, **kwargs)

Steps to Reproduce the Problem
Not applicable for requirements/code quality errors.
Proposed Solution

Rename the Allocation methods as outlined above.
Update the Allocation data controller methods to extract arguments from **kwargs.
Update calls to the Allocation methods to pass arguments as **kwargs.
Update the Allocation data controller tests to reflect the new method definitions.

Operating Environment
Not needed for requirements/code quality errors.

Fixed in commit 9faefd0377f59445f943954b063a8e0c93600fce

repo: weibullguy/rtk


text:
RSyntaxTextArea theme not applied correctly

Text color is not correct.

DarkRSyntaxTheme syntaxTheme = new DarkRSyntaxTheme(editor, Theme.load(
                    MainFrame.class.getResourceAsStream("/org/fife/ui/rsyntaxtextarea/themes/dark.xml")));
syntaxTheme.apply(editor);
LafManager.addThemeChangeListener((ThemeInstalledListener) e -> syntaxTheme.apply(editor));

Applying the theme without DarkRSyntaxTheme wrapper works.

Haven’t looked at the code for while. On a hunch I guess that it is because the constructor you are using is not actually supported. I will have a look.

authors: octo-kumo weisJ

repo: weisJ/darklaf-extensions


text:
是否可以让某一个弹幕对齐顶部或底部

实现类似公告的效果，让某些重要的弹幕永远对齐在顶部。

如果是要长期不消失的弹幕，那直接自己写个 div 覆盖在 container 上就好了；如果要和普通弹幕相同的存活时间，DOM 引擎可以通过 style 里设置 translateY 和 z-index 实现，Canvas 引擎大概没办法。

你是需要在顶部滚动的弹幕？还是顶部静止的弹幕？
如果是要顶部的滚动，那你说的碰撞是指什么的碰撞？
我感觉，如果要让「公告」这种弹幕显示在顶部，那应该就是要覆盖其他普通弹幕的，然后你可以从样式上对公告和普通弹幕作区分。

???????????????????Zhenye Wei notifications@github.com?2018?12?6? ????10:40??????????????????????????
????????????????????????
???????????????????????????????????????????????????????????
?You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.

了解了，我一开始想的可能有问题，我试试。

authors: Qquanwei weizhenye

repo: weizhenye/Danmaku


text:
build wheel

steps to build and publish test wheel:
Write ~/.pypirc file:
--------------------
[distutils]
index-servers =
   testpypi

[testpypi]
repository=https://test.pypi.org/legacy/
username=**
password=**
----------------------

Commands:
python setup.py sdist bdist_wheel
twine upload -r testpypi dist/*.whl
Installing the test wheel:
pip install --index-url https://test.pypi.org/simple/ weld

Hey Rahul, can you fix this up? There should be a way to reference libraries without doing the directory change...see how NumPy etc. do this stuff

Yea I'm waiting on #229 to be fixed and merged so I can rebase this.
The directory change is so libweld can find libweldrt - but with #229 it becomes trivial. I'll modify the pr so it loads in only libweld and remove the extra junk that were remnants of failed attempts.

All right so currently the packaging works with osx.
pip install --index-url https://test.pypi.org/simple/ pyweld
pip install --index-url https://test.pypi.org/simple/ grizzly
Note that the pip command being used cannot be the system pip.
You need to use a brew installed python or conda installed python.
The reason is that the system python uses an outdated openssl version which pypi rejects when pulling its packages. Manually upgrading openssl does not cause the system python to use the updated openssl.

authors: rahulpalamuttam sppalkia

repo: weld-project/weld


text:
Add support for i16 type

Need int16 for my project and this seems to work fine.
Maybe having 'h' for the int16 literal (as in numpy) would be better?

This looks good -- I think merging in one of the other PRs created a conflict though. Can you fix that? And then I'll merge it in :)

Seems to be good now 👍

Awesome, looks great!

authors: radujica sppalkia


text:
How to train recipe wenetspeech dataset

Describe the bug
I want to train the recipe of wenetspeech dataset(examples/wenetspeech/s0), but torchaudio failed to load opus format file after wenetspeech dataset is downloaded.
I also use 'process_opus.py' to process 'train_l' subset of wenetspeech, and change step2 as following, but still got an error '*_seg0004 not in key dict'

I cannot find any docs on the internet. Any advice to solve this problem? I will appreciate it very much.
To Reproduce
Steps to reproduce the behavior:

download wenetspeech dataset
python process_opus.py data/train_l/wav.scp data/train_l/segment data/train_l/out_wav.scp
change wenetspeech path in run.sh , bash examples/wenetspeech/s0/run.sh
error file *_seg0004 not in key dict'

Screenshots
I will put it later
Desktop (please complete the following information):

OS:  ubuntu20

算cmvn可以不用全部数据集，采样一点数据就行，没有的key可以忽略

authors: liziru xingchensong


text:
import librosa

import librosa

https://github.com/wenet-e2e/wespeaker/blob/1baf64260d54f41d64931170409a8355e38524f5/wespeaker/cli/speaker.py#L140-L143
这部分功能还没做，后续会删掉librosa

ok~


text:
Question: Are the sentences prior to rewriting available?

Hi Wenhu, thanks for making all of these open-source! I was wondering if the positive sentences that were rewritten into negative ones are available in the repo as well, or if you would consider doing so, since I think it would be an interesting (albeit different) task as well.

Yes, I do. I can re-download the data from Mechanical Turk interface, I will share with you once I have it ready.

Hi, I just crawled the data from the AMT interface and upload it to the repo with the link "https://github.com/wenhuchen/Table-Fact-Checking/tree/master/pairwise_data". Please note that the data is pretty raw without much preprocessing, but I'm sure you can handle them well.

Awesome, thank you so much!

authors: eisenjulian wenhuchen

repo: wenhuchen/Table-Fact-Checking


text:
Can't build image based on 'scratch'

Hi, guys.
WERF can't build image, which can be build with DOCKER call. I have problem with empty image (scratch), hope this information is this information is enough:
werf.yml
configVersion: 1
project: scratch-testing
---
image: ~
dockerfile: Dockerfile

Dockerfile:
FROM scratch

Build output with docker (BUILDKIT is enabled):
➜  docker build -t scratch_example .
[+] Building 0.0s (3/3) FINISHED
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load build definition from Dockerfile                                                                     0.0s
 => => transferring dockerfile: 37B                                                                                0.0s
 => exporting to image                                                                                0.0s
 => => writing image sha256:71de1148337f4d1845be01eb4caf15d78e4eb15a1ab96030809826698a5b7e30                             0.0s
 => => naming to docker.io/library/scratch_example                                                                       0.0s

Build output with werf:
➜  ./werf-linux-amd64-v1.1.22+fix32 build --stages-storage :local
Version: v1.1.22+fix32
Using werf config render file: /tmp/werf-config-render-134467294

┌ ⛵ image ~
└ ⛵ image ~ (1.28 seconds) FAILED

Running time 1.28 seconds
Error: phase build on image ~ stage dockerfile handler failed: unable to fetch dependencies for stage ~/dockerfile: get repo image scratch config file failed: reading image "scratch": GET https://index.docker.io/v2/library/scratch/manifests/latest: MANIFEST_UNKNOWN: manifest unknown; map[Tag:latest]

For my case, i have 'docs-export' stage in multi-stage dockerfile(see docs)

repo: werf/werf


text:
Feature Request: Additional list modifiers

I am really enjoying this zipper library. I was wondering about adding in functionality such as append and cons.
I'm not entirely sure what the api design would look like, I am open to discussion on this.
My use case is for a static list. For example, if I want to make a Zipper that is not empty, and will never be empty, I would have to construct it like:
        Maybe.withDefault (Zipper.singleton item1) <|
            Zipper.fromList
                [ item1
                , item2
                , item3
                ]

Instead of something maybe like
        (Zipper.singleton item1) |>
            Zipper.appendList
                [ item2
                , item3
                ]

Or maybe there's a different better way than this?

I was wondering about adding in functionality such as append and cons.

That would definitely be a good idea! As a Zipper always "points" to an element in a list, we could add
insertBefore : a -> Zipper a -> Zipper a
insertAfter : a -> Zipper a -> Zipper a
insertAllBefore : List a -> Zipper a -> Zipper a
insertAllAfter : List a -> Zipper a -> Zipper a

I think these newly produced Zippers should keep pointing at the same element, or would you rather have them point at the newly inserted element (in case of insertBefore and insertAfter)?

My use case is for a static list. For examp...

Is this a separate request? If so, we would do best to open a separate issue for this. If I understand you correctly, you are interested in a Zipper for something like List.NonEmpty (http://package.elm-lang.org/packages/mgold/elm-nonempty-list/3.0.0/List-Nonempty)?

I didn't know about non-empty list, that is neat to see.
I like the idea of insertBefore and insertAfter. Maybe we should wait on the insertAll functions unless there is more demand for them. They would be easier to add later than to remove. I was trying to find a similar case in the core libs, and it looks like Dict has some similarities. You can convert from list, and add a single value, but not add a list. What do you think?

I didn't know about non-empty list, that is neat to see.

I think you'll need something like List.NonEmpty to tell the compiler that the List is not empty, otherwise we have no choice but to return an Maybe (Zipper a) from fromList. I would rather not add a dependency to List.NonEmpty, but I would be happy to create another library List.NonEmpty.Zipper (or something similar).

I like the idea of insertBefore and insertAfter. Maybe we should wait on the insertAll functions unless there is more demand for them. They would be easier to add later than to remove. I was trying to find a similar case in the core libs, and it looks like Dict has some similarities. You can convert from list, and add a single value, but not add a list. What do you think?

I agree! Do you think you would rather have the newly produced Zippers point to the newly inserted elements, or rather at the "old" focus point?

I thought it would be good to look around to see what other zipper libraries do.
Looking at a Haskell lib: https://hackage.haskell.org/package/ListZipper-1.2.0.2/docs/Data-List-Zipper.html
It has "insert" to insert before the cursor, and moves the cursor to the new item
It has "push" to insert before the cursor, and keeps the cursor the same
clojure looks like it never moves the cursor: https://clojure.github.io/clojure/clojure.zip-api.html
in "insert-child", "insert-left", "insert-right"
So it looks like there are different ways of doing insert. I would be happy if the library just did whatever was easiest to implement and documented the behavior.
Also, if we are going to add some way to insert, we should probably have some way to delete, right?
In the case of delete, I assume it would delete at the cursor. Delete seems tricky. We can go to the right, but what if there's nothing to the right? Go left if there's nothing to the right? We would have to return a Maybe zipper. Thoughts on this?

I think letting insertBefore behave like :: is most intuitive (see insert in Haskell). That means that insertBefore moves the focus to the newly inserted element.
What would also be expected is:
delete (insertBefore 1 someZipper) == someZipper

This means that delete should move the focus to the right. But what do we do when there is no element to the right?
I'm not sure yet as to the direction we should take...
Thinking outside the box, maybe we could distinguish between a Zipper pointing at an element and a Zipper pointing between elements. Only in the latter case would inserting make sense. Deleting the current focus would then result in a Zipper pointing between the previous element and the next element.

I like the insertBefore, that makes sense to me.
delete would have to return a Maybe, since there is no such thing as an empty Zipper here, right? If a list has one item, and we call delete, we would have to return Nothing.
So we would have to use the signature delete : Zipper a -> Maybe (Zipper a)
Also, it seems to makes most intuitive sense to delete the element the pointer is at.
With this in mind, the cases seem to be:

delete moves to the right, returns Nothing if there's nothing to the right. Pro's: makes intuitive sense when there is an element to the right. Con's: it can be confusing that calling delete on a Zipper that still has elements returns Nothing.

delete moves to the right, if there's nothing to the right, moves left, if there's nothing left, returns Nothing. Pro's: delete only returns Nothing when the list is empty. Con's the behavior is inconsistent (sometimes moving left, sometimes right) which can be confusing.

delete points at an element between the previous elements (your new proposal). Pro's: something like insert a (delete zipper) == zipper would make sense. Con's: what would current (delete zipper) return if it is pointing between two items? Or between an item and nothing if it's at the end?

Personally, I like # 1 since it is simple and easy to grasp. But, since I currently only have the need for appending to a zipper, I think it would be the elm way to wait on implementing the delete function. Elm seems to stay away from adding anything until the need arises in real-life cases.

I need exactly this feature for a 0.18 project

Personally, I like # 1 since it is simple and easy to grasp. But, since I currently only have the need for appending to a zipper, I think it would be the elm way to wait on implementing the delete function. Elm seems to stay away from adding anything until the need arises in real-life cases.

There's one thing we should keep in mind when making our decision: how safe is it to change this behavior later. If we switch from #1 to #2 later, the type signatures stay the same but the behavior changes which might cause bugs for projects where the upgrade is done "sloppily". We can solve this by creating a second version of delete which takes a second argument that determines what to do when there's no element to focus on.

I need exactly this feature...

Would you be willing to make a PR? I haven't done any work in Elm for quite some time, so my Elm is a little rusty.

...for a 0.18 project

If you want, we could create a 0.18 fork (like listzipper-compat or something) that supports 0.18 for a while longer. Or is there a better approach to supporting multiple versions of Elm?

repo: wernerdegroot/listzipper


text:
是不是还需要每天手动运行一次

用gitub拉完项目后，再每天手动运行一次run.yml签到才完成是吗，因为一天后看Actions日志是空白的

不需要的，每天是定时会自己跑的，可能是你的github action没有设置好，先检查下。


text:
Added GNOME Compose Key

As requested in #41, this commit fixes the issue.

Ack, it looks like someone made it first. Never mind then! :ok_hand:

Thanks anyways :)

authors: wesbos zonck

repo: wesbos/keycodes


text:
Failed to rebuild an index with MongoDB 4.2

Environment
Host

item
version

OS

GROWI
4.1.2

MongoDB (MongoDB Atlas)
4.2.8

Elasticsearch (SearchBox)
6.8.8

Using Docker
yes

Using growi-docker-compose
yes

(Accessing https://{GROWI_HOST}/admin helps you to fill in above versions)
Client

item
version

OS
Windows 10

browser
Chrome

How to reproduce? (再現手順)

Deploy to HerokuボタンでHerokuにデプロイ
MongoDB AtlasでMongoDB 4.2のクラスタを作成
MONGO_URI を2で作成したクラスタのものに編集してHeroku Appを再起動
HerokuにデプロイしたGrowiにアクセスした後、全文検索管理でインデックスのリビルドを実行

※docker-composeでMongoDBのバージョンを4.0以降にした場合も同様
What happens? (症状)

インデックスのリビルドに失敗し、下記のログが出力される

Uncaught Exception:  MongoError: Failed to parse: { find: "pages", filter: { $and: [ { redirectTo: null } ] }, projection: {}, returnKey: false, showRecordId: false, snapshot: true, lsid: { id: UUID("2885dbb9-1d56-4447-946d-53688a971e31") }, $clusterTime: { clusterTime: Timestamp(1598076774, 1), signature: { hash: BinData(0, 193CDFF16299DD5B5B620B345B5F36D3080719BC), keyId: 6854399949057032195 } }, $db: "growi" }. Unrecognized field 'snapshot'.
    at MessageStream.messageHandler (/app/node_modules/mongodb/lib/cmap/connection.js:261:20)
    at MessageStream.emit (events.js:314:20)
    at processIncomingData (/app/node_modules/mongodb/lib/cmap/message_stream.js:144:12)
    at MessageStream._write (/app/node_modules/mongodb/lib/cmap/message_stream.js:42:5)
    at writeOrBuffer (_stream_writable.js:352:12)
    at MessageStream.Writable.write (_stream_writable.js:303:10)
    at TLSSocket.ondata (_stream_readable.js:713:22)
    at TLSSocket.emit (events.js:314:20)
    at addChunk (_stream_readable.js:303:12)
    at readableAddChunk (_stream_readable.js:279:9)
    at TLSSocket.Readable.push (_stream_readable.js:218:10)
    at TLSWrap.onStreamRead (internal/stream_base_commons.js:188:23) {
  operationTime: Timestamp { _bsontype: 'Timestamp', low_: 2, high_: 1598076774 },
  ok: 0,
  code: 9,
  codeName: 'FailedToParse',
  '$clusterTime': {
    clusterTime: Timestamp { _bsontype: 'Timestamp', low_: 2, high_: 1598076774 },
    signature: { hash: [Binary], keyId: [Long] }
  }
}

What is the expected result? (期待される動作)

インデックスのリビルドが成功する

Note
サポート対象はMongoDB 3.xですが、HerokuのmLabプラグインが2020年11月で提供終了かつmLabが移行推奨としているMongoDB Atlasが基本的に4.2以降のみをサポートしているという状況のため、起票しました。
例外が発生している箇所は src/server/service/search-delegator/elasticsearch.js の下記の行です。
    const readStream = findQuery
      // populate data which will be referenced by prepareBodyForCreate()
      .populate([
        { path: 'creator', model: 'User', select: 'username' },
        { path: 'revision', model: 'Revision', select: 'body' },
      ])
      .snapshot()
      .lean()
      .cursor();

この snapshot() によって、MongoDB 3.2から非推奨となっている$snapshotオペレータを呼び出しているようですが、MongoDB 4.0以降で上記の例外が発生します。

@rshindo ご報告ありがとうございます。MongoDB の最新バージョンにもだいぶ置いて行かれているので、4系への対応に着手しようと思います。次のバージョンリリースまで少々お待ちください。

進捗報告です。snapshot を含むクエリを廃した v4.1.3 をリリースしました。
手元では MongoDB 3.6 での正常動作を確認するに留まっていますが、今後4.x系への動作確認を終え次第、https://github.com/weseek/growi-docker-compose が依存している MongoDB も4.x系に切り替えていく予定です。

自分の手元での動作確認の結果です。
GROWI 4.1.5+MongoDB 3.6.19の環境をMongoDB 4.0.20→4.2.2.9→4.4.1の順番に更新してみました。
それぞれのバージョンで以下の操作を試しましたが、正常に動作しているようです。

ページの閲覧
ページの編集
インデックスのリビルド
ログイン/ログアウト

開発チームでの動作確認結果も問題ないようなのでこの issue は close します。
Confirmed versions

GROWI
MongoDB

v4.1.2 <=
v3.3, v3.6

<= v4.1.3
v3.3, v3.6, v4.0, v4.2, v4.4

authors: rshindo shield-9 yuki-takei

repo: weseek/growi


text:
Updated images not propagating

Hello,
Thank you for providing this fantastic service, it's very generous of you to do so and benefits more people than you can imagine. ❤
We've been using it for a few years now and just noticed that user profile images, which are automatically renamed to always be the same file name, are not updating when requested via https://images.weserv.nl/. For example, the old version of one can be seen at https://images.weserv.nl/?url=https://www.guggenheim.org/wp-content/uploads//userphoto/285.jpg with the new one at https://www.guggenheim.org/wp-content/uploads//userphoto/285.jpg
Any thoughts on what may be causing this?

I've closed this issue as the new image has propagated to Weserv, after about 1.5 hours, and we're suspicious that the issue may be with our web host as opposed to your service.

I had thought the cause of this issue was a small typo on our end, the image path that we were generating had two forward slashes in it, but correcting that did not resolve this.

Hi, there are some layers of caching on our end, please read the 3/4 sections that explain this from this link: https://images.weserv.nl/faq/#if-images-are-modified-do-you-refresh-them-after-a-certain-period-of-time
Not only do we cache, CloudFlare does too, and your browser. It saves your webserver some work, and the internet would be a lot slower without caching.
It is best practice that you change the URL when the content changes, this is what the big guys do too (social networks etc).

Hello @andrieslouw. Thank you for the detailed response!

authors: andrieslouw betweenbrain

repo: weserv/images


text:
Rbootstrap

Starting to work towards a more standard build system.
Open questions:

How should I automate the copying of feather into this package? Ideally it'd be part of the configure/build process so that install_github() can work. I think that will require checking in of the generated flatbuffers header file so the user doesn't need a big dependency chain

How can we tweak file selection in Makevars so I don't need to manually update it each time I add a new cpp file, or when the files in feather change.

cc @jjallaire

Squash your commits – GitHub Blog

I turned off merge commits as an option.
I still think the ASF patch tool does a better job of producing nice patches (especially with multiple authors), so we can always bug github about reconciling the differences. Let's see how it goes

authors: denji hadley wesm

repo: wesm/feather


text:
'kind' and 'order' are ignored by Series.sort

Is this desired? Is Series.sort needed when we have Series.order?

Alright I have this one all "sorted" (ha!)

authors: craustin wesm

repo: wesm/pandas


text:
Separate Document to a standalone module or repository

The Document code could be separated to a standalone module and even a repository.
Some tests should be added to increase coverage.

As mentioned in the mail I think could be a very good option to separate it to a new repo and many weso the maintainer.

I have already done it here.

authors: labra thewilly

repo: weso/utils


text:
Started auth & retrieve tweets

This barely works and is a total hack but it more proves the concept of what I'm trying to achieve.

[ ] Is there a way to get the stored twitter credentials from the model rather than re-authorizing? (I poked around a bit but figured it's probably better to just ask)
[x] The tweepy API function user_timeline() has a optional parameter for limiting the number of tweets returned but, as far as I can tell it's positional and I can't specifying it as a kwarg. I'll dig a little further into this later, as it's late right now so I'm probably overlooking something obvious.

Pull request approved! 👍
Hi @eayoungs, regarding your question "Is there a way to get the stored twitter credentials from the model rather than re-authorizing? (I poked around a bit but figured it's probably better to just ask)"
You can look up the latest authorization session from the WeVoteServer/import_export_twitter/models.py TwitterAuthResponse table. There is a function in the TwitterAuthManager called "retrieve_twitter_auth_response" that returns the latest twitter_auth_response for the current voter_device_id.

Thanks for the Review @DaleMcGrew :)

Hey, that rimes! ;-)
Thanks, Dale!

Hey, Dale; I'm having trouble finding where I can access the voter_device_id. It doesn't seem to be available in either voter/models.py or organization/models.py.

authors: DaleMcGrew bharathdn eayoungs

repo: wevote/WeVoteServer