text:
Failed to send command to swhks through IPC.

Version Information:

Distribution Information ( run uname -a ): Linux revise-arch 6.0.12-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 08 Dec 2022 11:03:38 +0000 x86_64 GNU/Linux
swhkd version ( swhkd -V ): swhkd 1.2.1

Describe the bug:
A clear and concise description of what the bug is.
None of the keypresses work - error code 2: failed to send command to swhks through IPC.
Expected behavior:
A clear and concise description of what you expected to happen.
Upon pressing a hotkey keypress, the function should activate - e.g. Prnt takes a screenshot.
Actual behavior:
A clear and concise description of the behavior.
Nothing happens, and this is the output log:
[2022-12-16T05:34:59Z ERROR swhkd] Failed to send command to swhks through IPC.
[2022-12-16T05:34:59Z ERROR swhkd] Please make sure that swhks is running.
[2022-12-16T05:34:59Z ERROR swhkd] Err: Os {
        code: 2,
        kind: NotFound,
        message: "No such file or directory",
    }

To Reproduce:
Steps to reproduce the behavior.
Start swhkd:
swhks &
sudo pkexec swhkd --device "AT Translated Set 2 keyboard" --device "Compx 2.4G Wireless Receiver"  # added sudo to bypass silly pkexec thing which requests for authentication even when I changed settings, worked fine previously.

Additional information:
Anything else you'd like us to know?
This happened after changing shell to zsh, so at first I thought it was a zsh issue, but it persists even after changing shell back to bash.

The policy file appears to still be there, though I edited some of the permissions since it would ask for password manually each time I restarted my WM.
Some logs I think that might be relevant - a majority of the log files were empty:
(zenity:17846): dbind-WARNING **: 12:54:29.962: Couldn't connect to accessibility bus: Failed to connect to socket /run/user/1000/at-spi/bus: No such file or directory

(swappy:17870): dbind-WARNING **: 12:54:38.243: Couldn't connect to accessibility bus: Failed to connect to socket /run/user/1000/at-spi/bus: No such file or directory

We don't interact with at-spi accessibility bus so those logs are not relevant. Would you mind sharing the version information of your polkit installation?

Output of pacman -Q | grep "polkit":
polkit 122-1
polkit-gnome 0.105-9
polkit-qt5 0.114.0-1

I have figured out the problem. Since you are using sudo pkexec , the PKEXEC_UID env var is being set to 0 and hence its looking for swhks sock file in /run/user/0.... So the first course of action would be to get pkexec working with our policy file.
Can you send the output of which swhkd?

Ahh I see. Policy file default asks for authentication which is pretty annoying, and the only way around it I have found to have "worked" is with sudo. I also did try changing the settings to "yes" for all actions (which I believe meant no authentication) but that also prompted me for authentication.
Output of which swhkd: /sbin/swhkd.

This is the source of the problem. which swhkd should point to /usr/local/bin else the policy file won't take effect and skip authentication. It should be removed from sbin.
@ajanon do you think we can automatically change the path in policy file with make according to some variable such as BIN_PATH etc? That will remove this problem entirely where swhkd might get installed in different directories.

We already have a TARGET_DIR path in our Makefile, we should be able to do this automatically.
Tentative implementation (in install target):
--- a/Makefile
+++ b/Makefile
@@ -25,6 +25,7 @@ install:
        @touch /etc/$(DAEMON_BINARY)/$(DAEMON_BINARY)rc
        @cp ./target/release/$(DAEMON_BINARY) $(TARGET_DIR)
        @cp ./target/release/$(SERVER_BINARY) $(TARGET_DIR)
+       @sed -i 's#/usr/bin/swhkd#$(TARGET_DIR)/$(DAEMON_BINARY)#' $(POLKIT_POLICY_FILE)
        @cp ./$(POLKIT_POLICY_FILE) $(POLKIT_DIR)/$(POLKIT_POLICY_FILE)
        @chmod +x $(TARGET_DIR)/$(DAEMON_BINARY)
        @chmod +x $(TARGET_DIR)/$(SERVER_BINARY)

Alternatively, we could have a small script generating the policy file:
#!/bin/bash
declare -r SWHKD_PATH="$1"

cat << EOF > com.github.swhkd.pkexec.policy
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE policyconfig PUBLIC "-//freedesktop//DTD PolicyKit Policy Configuration 1.0//EN" "http://www.freedesktop.org/standards/PolicyKit/1/policyconfig.dtd">
<policyconfig>
  <action id="com.github.swhkd.pkexec">
    <message>Authentication is required to run Simple Wayland Hotkey Daemon</message>
    <defaults>
      <allow_any>no</allow_any>
      <allow_inactive>no</allow_inactive>
      <allow_active>yes</allow_active>
    </defaults>
    <annotate key="org.freedesktop.policykit.exec.path">${SWHKD_PATH}</annotate>
  </action>
</policyconfig>
EOF

We could then call it in the Makefile:
build:
  ./build-policy-file $(TARGET_DIR)/$(DAEMON_BINARY)

Both seem fine to me, I don't have a strong preference for one or the other.
Side note: our PKGBUILD should probably use our Makefile.

I already thought of the above but sed -i is a gnu extension to sed and not portable. The script you demonstrated seems better.

I am very surprised to learn that this flag is not part of POSIX!
Should I change the script to be POSIX-compliant too? As-is, it is not and should only work on bash.

That would be great, yep!

I will submit a PR later then!

#184 and #185 should help in avoiding this kind of issue in the future.
Unless @Shinyzenith has any better idea, I unfortunately don't see a way out of your troubles except cleaning up all swhkd related stuff and reinstalling once the above two PRs get merged (and the AUR package gets updated).

authors: Shinyzenith ajanon evesdropper

repo: waycrate/swhkd


text:
Change theme color for mobile devices

Description

It Changes the browser color for mobile devices.

Screenshots
BEFORE

AFTER

Changelog

Change theme color(same as header) 258d36e
Remove top-border e0a5ccf

Related Issues
#77

Looks good to me! @Cooperbuilt Is this a good color for the browser? I realize now that we might want some color contrast between the browser and the top navigation. @pyymenta can we see how it looks with the hex value #00a7ba or #455A81? Just screenshots will do, you don't need to commit anything yet.

Looks good to me! @Cooperbuilt Is this a good color for the browser? I realize now that we might want some color contrast between the browser and the top navigation. @pyymenta can we see how it looks with the hex value #00a7ba or #455A81? Just screenshots will do, you don't need to commit anything yet.

Yeah, of course!
With #00a7ba

With #455A81

Honestly, I prefer with #2A416E. Although #455A81 looks good to me too. What do you think?

Looks good to me! @Cooperbuilt Is this a good color for the browser? I realize now that we might want some color contrast between the browser and the top navigation. @pyymenta can we see how it looks with the hex value #00a7ba or #455A81? Just screenshots will do, you don't need to commit anything yet.

Yeah, of course!
With #00a7ba

With #455A81

Honestly, I prefer with #2A416E. Although #455A81 looks good to me too. What do you think?

Thinking about contrast, I think #455A81 is a better choose.

I prefer the #455A81 option

Looks like we have a consensus. @pyymenta can we use the version with #455A81 and commit that? Then we'll get you merged in!

Looks like we have a consensus. @pyymenta can we use the version with #455A81 and commit that? Then we'll get you merged in!

Cool! I'll change it right now.

source: gharchive/pull-request

authors: Cooperbuilt SheaBelsky pyymenta

repo: wayfair/awesome-learning

license_type: permissive

license_source: github-api


text:
How do I undo this command?

wakatime --write --plugin zsh-wakatime/0.0.1 --entity-type app --project Terminal --entity ...

Could you give more details? what you mean of "undo this command"?

I do not use zsh, I use bash so I did this command and now wakatime tracking my terminal as a zsh. I want to make as if I didn't do this command in the first place. Is it possible? Thanks for responding @wbingli !

I don't think so you can undo it. It just sent out a tracking data point to the wakatime.com.  If you are concerning about the data you sending to wakatime.com, you may reach their support to see if they can remove it.

I see, thanks.

source: gharchive/issue

authors: niyonx wbingli

repo: wbingli/zsh-wakatime

license: MIT


text:
Source handle's position changes do not cause the position of the edge connecting to the source handle to change

Describe the Bug
Here is the example: https://codesandbox.io/s/sandpack-project-forked-m7lt57?file=/ColorSelectorNode.js
When I click the button, the source handle's position changes, but the edge won't change.
Your Example Website or App
https://codesandbox.io/s/sandpack-project-forked-m7lt57?file=/ColorSelectorNode.js
Steps to Reproduce the Bug or Issue

click the button

Expected behavior
I hope the edge will change with the source handle
Screenshots or Videos
No response
Platform

OS: macOS
Browser: Chrome
Version: 10.3.4

Additional context
No response

Hey @JasonWu008
you need to use useUpdateNodeInternals when you programatically change the handles. I updated your example: https://codesandbox.io/s/sandpack-project-forked-u6tx30

Thanks! It helps a lot. The React-Flow is amazing! I hope more and more developers can benefit from it. Best wishes!

Nice to hear that :)

repo: wbkd/react-flow


text:
Events for creating new edge

Hi, I am trying to add custom behavior when a user starts (and stops) creating a new edge.
Right now there is only onConnect event that fires when the connection is created. I think that it would be great to add events that will fire when a user starts and stops creating the new edge. For example something like onEdgeDragStart({ source }) and onEdgeDragStop(). Stop event is needed because onConnect is not fired when a user stopped dragging but did not created a new edge.

Hey @pitkes22
thanks for your input!
I added the handlers onConnectStart({ nodeId, handleType }) and onConnectStop(). It's released in v4.9.0

Awesome! Thank you for the fast response and for your work on this absolutely awesome library :+1:


text:
Panel do not change until manual reloading of the page

Hi,
litte annoyng isssue. I have a Combo2 panel similar configuration.
On browser Chrome, when I change one of the parameter like from of panel, page/panel do not refresh automatically, but I have to refresh manually with reload button of the browser.
In Android App, instead, panel is reloaded if one of parameter change.
Is this normal behaviour or there is a way to avoid this?
Many Thanks
marco

Are these newly added items and did you try to restart openHAB to see if that fixes it? If restarting solves the issue it may be related to https://github.com/eclipse/smarthome/issues/2706 which should be fixed in  openHAB 2.1.

I have the same issue. I am using a combo 3 webview and it does not reload when changing a parameter.
I am using Firefox and tried restarting OH2. Any way to provide you debug infos?

@Andirs55 The browser debug console may show some helpful errors or warnings:

Enter the Basic UI URL in your browser and navigate to page with the Grafana Webview
Open the Developer (Tools) windows from your browser menu or by pressing F12
Then reload the Basic UI page with the Grafana webview
Changing the values of some parameters

The developer console will then show any warnings/errors.
The browser developer tools also have a helpful "Network" view where you can monitor all page request and see the response result or error.

Ok the problems seem to start at 3.
Firefox can not connect to the server at http://192.168.1.20:8080/rest/sitemaps/events/dda51951-da34-49fe-bbf0-779db473af87?sitemap=default&pageid=0101. smart home grafana.js: 1: 1334
The connection to http://192.168.1.20:8080/rest/sitemaps/events/e3aa0fad-fda2-405c-9c46-2bf6d7f51d05?sitemap=default&pageid=default was interrupted while the page was loaded. smarthome.js:1:20867

What to do now?

Firefox can not connect to the server at http://192.168.1.20:8080/rest/sitemaps/events/dda51951-da34-49fe-bbf0-779db473af87?sitemap=default&pageid=0101. smart home grafana.js: 1: 1334
The connection to http://192.168.1.20:8080/rest/sitemaps/events/e3aa0fad-fda2-405c-9c46-2bf6d7f51d05?sitemap=default&pageid=default was interrupted while the page was loaded. smarthome.js:1:20867

Those errors seem to be "normal" with Firefox when you reload the page. I see them too while everything still works with openHAB 2.1.
Did you also test if it works Chrome?
Does openHAB properly update items on a page when they are updated? E.g. when you open the same Basic UI page in two tabs and then update items on one, the changes should also be updated in the other tab.
Do you use openHAB behind a webserver like Nginx or Apache2? It may not be properly configured for proxying websockets to openHAB. These are used for streaming item updates to your browser.

Ok i also tested with chrome and there is the same behaviour :( However it does not give that error when reloading the page. But when changing a parameter (e.g. time frame to display) the chrome console gives me that:
Uncaught DOMException: Blocked a frame with origin "http://192.168.1.20:8080" from accessing a cross-origin frame. VM226 smarthome-grafana.js:1
    at b (http://192.168.1.20:8080/static/grafana/smarthome-grafana.js:1:3606)
    at e (http://192.168.1.20:8080/static/grafana/smarthome-grafana.js:1:4717)
    at f (http://192.168.1.20:8080/static/grafana/smarthome-grafana.js:1:1265)
    at EventSource.<anonymous> (http://192.168.1.20:8080/static/grafana/smarthome-grafana.js:1:1656)
b @ VM226 smarthome-grafana.js:1
e @ VM226 smarthome-grafana.js:1
f @ VM226 smarthome-grafana.js:1
(anonymous) @ VM226 smarthome-grafana.js:1

OpenHAB properly updates items (switches etc.) on the page with the diagram across tabs and even across the two browsers Firefox and Chrome.
To the last point i would say no because did not setup something special. Just a normal OH package install (2.1 stable) on an ubuntu server and accessing the OH webview with a Win10 machine.
Thanks :)

@Andirs55 That sounds like a "Same origin policy" violation. You need to use a reverse proxy like nginx or apache2 to prevent it. Browser blocks the connection because the request is to a different port and therefore it violates the policy.
To fix this with a reverse proxy:
Your OH address should be http://192.168.1.20 not http://192.168.1.20:8080
Grafana address should be http://192.168.1.20/grafana instead of http://192.168.1.20:3000.

@Terehi thanks a lot, that works

Great that setting up a reverse proxy resolved this issue @Andirs55, @marcolino7! I'll add some notes about this in the documentation.

I had to restart my openHAB 2.1.0 to get the dynamic reloading of the Webview. So the issue still exists in openHAB 2.1.0.

I'm having the same issue... and cant get it to work....
can someone please post a example here, what i need to add to the nginx conf file to get this to work?
Thanks

@KugeLSichA  This is one of the server { .. } blocks I use nowadays with openHAB, htaccess and SSL in a Docker setup, you most likely need to change the hostnames and ports of course:
server {
	listen                          443 ssl;
	server_name                     _;

	ssl_certificate                 /etc/nginx/certs/live/super.secret.domain.com/fullchain.pem;
	ssl_certificate_key             /etc/nginx/certs/live/super.secret.domain.com/privkey.pem;

	auth_basic                      "Username and Password Required";
	auth_basic_user_file            /etc/nginx/htpasswd;

	location / {
		proxy_pass                            http://openhab:8080/;
		proxy_set_header Host                 $http_host;
		proxy_set_header X-Real-IP            $remote_addr;
		proxy_set_header X-Forwarded-For      $proxy_add_x_forwarded_for;
		proxy_set_header X-Forwarded-Proto    $scheme;
	}

	location /grafana/ {
		proxy_pass http://grafana:3000/;
	}
}

Thanks for your quick reply @wborn ... :)
i tried with multiple parameters... but cant get it to work... :(
so i try again with as much infos i can provide,,, maybe you see the problem in my setup...
openhabianpi:8080 this is my openhabian adress
openhabianpi:3000 this is my grafana adress
both accessable in the browser
i'm running openhabian snapshot build #1143
my file in etc/nginx/sites-enabled/openhab
`
#################################
openHABian NGINX Confiuration
#################################
Redirection
#server {
listen                          80;
server_name                     localhost;
return 301                      https://$server_name$request_uri;
#}
Reverse Proxy to openHAB
server {
listen                          80;
listen                          443 ssl;
server_name                     localhost;

add_header                      Strict-Transport-Security "max-age=31536000; includeSubDomains";
Secure Certificate Locations
ssl_certificate                 CERTPATH;
ssl_certificate_key             KEYPATH;
location / {
    proxy_pass                              http://openhabianpi:8080/;

proxy_buffering                         off;  # openHAB supports non-buffering specifically for SSEs now
    proxy_set_header Host                   $http_host;
    proxy_set_header X-Real-IP              $remote_addr;
    proxy_set_header X-Forwarded-For        $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto      $scheme;

Password Protection
auth_basic                              "Username and Password Required";
auth_basic_user_file                    /etc/nginx/.htpasswd;
}

location /grafana/ {
    proxy_pass      http://openhabianpi:3000/;
}

Let's Encrypt webroot location
location /.well-known/acme-challenge/ {
root                                    /var/www/localhost;
}
}
vim: filetype=conf
`
for the value server_name i tried 127.0.0.1 / localhost / the fixed network IP of openhab
my smarthome-grafana-user-default.js file
`
// the prefix that is used for each Grafana panel URL
SMARTHOME_GRAFANA_DEFAULTS["urlPrefix"] = "http://openhabianpi:3000";
// use "false" so actual pages are loaded (or comment the line)
SMARTHOME_GRAFANA_DEFAULTS["debug"] = "false";
// use "default" for the default Eclipse SmartHome sitemap (or comment the line)
//SMARTHOME_GRAFANA_DEFAULTS["sitemap"] = "grafana";
if (SMARTHOME_GRAFANA_DEFAULTS["debug"] === "true") {
console.log("Using SMARTHOME_GRAFANA_DEFAULTS = " + JSON.stringify(SMARTHOME_GRAFANA_DEFAULTS));
}
`
my .sitemap file
    	Text item=HF_SMETER_KWH { 			Selection item=Combo3_From mappings=["now-1h"="One hour ago", "now-1d"="One day ago", "now-1w"="One week ago", "now-1M"="One month ago", "now-1y"="One year ago"] 			Selection item=Combo3_To mappings=[now="Now", "now-1h"="One hour ago", "now-1d"="One day ago", "now-1w"="One week ago", "now-1M"="One month ago", "now-1y"="One year ago"] 			Switch item=Combo3_Theme mappings=[light="Light", dark="Dark"] 			Webview url="/static/demo.html?dashboard=test&fromItem=Combo3_From&toItem=Combo3_To&themeItem=Combo3_Theme&panel=4" height=13     	}

@KugeLSichA
If you really access openHAB in your browser via http://openhabianpi you should use:
SMARTHOME_GRAFANA_DEFAULTS["urlPrefix"] = "http://openhabianpi/grafana";
If you use another hostname in your browser you should use that instead of openhabianpi.
So also make sure you really use the proxy in your browser by using the port 80 in the URL instead of 8080 (or by just omitting the port from the URL).
You also may need to reload/restart Nginx for the changes to be applied. :wink:

Thanks again @wborn for helping me to get this fixed...
yeah i noticed that i need to restart nginx... and also did always the test param before...
so now i'm a bit closer... but still not working...
As you can see here... someting with the path seems to be broken...  it seems to be missing the /grafana folder in the URL
if i access the red GET error files... via http://openhabianpi/grafana/public.....   then the script ist loaded

this is how it looks on my sitemap

In Debug mode... the URL seems to be okay... but if i click on it... i get the same error like in pic 1

i did not changed any openhab folder through setup... still all basic installations...
even i started (hmm i guess today more than 20 times today) the nginx and also the OH server... just to be sure ...

@KugeLSichA You most likely also need to update the Grafana configuration file (/etc/grafana/grafana.ini) so it contains something like:
# The full public facing url you use in browser, used for redirects and emails
# If you use reverse proxy and sub path specify full url (with sub path)
;root_url = http://localhost:3000
root_url = %(protocol)s://%(domain)s/grafana/

I don't use port 80 myself so maybe also need to uncomment (remote ; from the protocol) in:
[server]
# Protocol (http or https)
;protocol = http

Awesome!!!
Thank you sooooooo much.... after these changes to the grafana.ini and a restart of OH Server... it works now...!

I've finally made a little write-up about all of this in the README.md. So you are welcome review this in #6. :smile:

authors: Andirs55 KugeLSichA Terehi kleini marcolino7 wborn

repo: wborn/smarthome-grafana

license: mit

license_source: bigquery


text:
ng2 alpha.53 support

Hi @wbuchwalter
Getting this ERROR in ./~/ng2-redux/lib/components/provider.js Module not found: Error: Cannot resolve module 'angular2/angular2' in ...node_modules/ng2-redux/lib/components  @ ./~/ng2-redux/lib/components/provider.js 15:24-52 when angular 2 version is .53
Any plan to fix this soon? Solution would be replace angular2/angular2 with angular2/core

Fixed in 2.0.2 release.
Thanks.

authors: lanocturne wbuchwalter


text:
Adds the ability to draw an XY scatter plot.

This PR introduces two new fields on Style: DotWidth and DotColor. It also tweaks some aspects of the raster renderer, namely the .Circle function and some of the inner workings of the drawing package.
Important consideration; so far only Draw.LineSeries uses these new fields, support in other types of plots is ongoing.
Also adds an example for scatter plots in _examples/scatter/main.go.

Looking good when I specify the full style like you did in your sample.
However the default rendering without style seems to have regressed. I get a black and white filled graph ... not auto color assignment.
See graphs ....  from master with default style

and scatter with default style:

Another thing (which could be my misunderstanding) ..  I also wanted to get auto-color for the scatter so deleted the explicit Red color from the sample and the nothing was rendered.   Is this related to the above, or do I need to ask explicitly for auto-coloring?

good catch on the regressions, i really need to add tests to validate the draw functions.
i do auto coloring for the series stroke colors, can for sure do that for the dot colors using the same method.

@mattdoran can you do a pull and try rendering that chart again; i've tweaked LineSeries and added auto coloring, going to add some regression tests now to make sure that doesn't happen again

Looking good @wcharczuk
Default style draws lines auto colored properly.
The scatter also auto colors too now.
👍
PS: I have other issues/suggestions to raise ... is there a better place to do this than just in an issue?   Hint what's on my mind: Smarter tick marker positioning (I've been looking at matplotlib's algorithm) ... and performance plotting lots of points is slow and I've started some profiling.

cool!
if you have other suggestions, log them as issues so i'm aware of them, but feel free to hack away.
re: performance, yeah there is a huge discrepancy between SVG and PNG rendering. my hunch is it's because the drawing library internally calls into font apis to do actual painting. any help here would be greatly appreciated!
going to merge this branch once i get a regression test in place for the drawing colors

authors: mattdoran wcharczuk

repo: wcharczuk/go-chart


text:
Why is "The requested URL returned error: 404 Not Found" displayed?

Hi.
If you know about the following two questions, please teach.

【Purpose of question】
Q1.

Why is the warning text displayed with yellow letters when making vagrant up?
Q2.

Why does an error appear in red letters when vagrant box update is given?
【Supplementary explanation】
1
In common with the two questions, the following message will be displayed.
The requested URL returned error: 404 Not Found

I confirmed my network environment, but there are no abnormalities.
I restarted the PC and WiMAX and connected to another website, but you can browse the page as usual.
2
After starting vagrant, you can launch WordPress site by executing the following command.
$ vagrant ssh
wocker ~$ wocker start test

Thank you for your review.

Hi @echizenyayota ,
It is a bug in Vagrant.
Please refer to "vagrant box update - Fails with 404 Not Found error · Issue #9442 · hashicorp/vagrant" https://github.com/hashicorp/vagrant/issues/9442 .
At this moment, you have to edit the file ~/.vagrant.d/boxes/ailispaw-VAGRANTSLASH-barge/metadata_url manually.
FROM:
https://atlas.hashicorp.com/ailispaw/barge?access_token=xxxxxxxxxxxxxxxxxxxx

TO:
https://vagrantcloud.com/ailispaw/barge?access_token=xxxxxxxxxxxxxxxxxxxx

Thank you.

Hi,@ailispaw .
Thank you for your comment!

Based on your advice and #9442, I corrected it with the following three steps.
However, this time, a yellow note is displayed as "Illegal". Is there anything else I need to do?
Illegal characters found in URL

1. Vagrant update
version1.9.1 → version2.0.2
$ vagrant plugin update
Updating installed plugins...
Fetching: vagrant-hostsupdater-1.0.2.gem (100%)
Fetching: micromachine-2.0.0.gem (100%)
Fetching: vagrant-vbguest-0.15.1.gem (100%)
Updated 'vagrant-vbguest' to version '0.15.1'!

2. metadata_url modified

$ vi ~/.vagrant.d/boxes/ailispaw-VAGRANTSLASH-barge/metadata_url
# https://atlas.hashicorp.com/ailispaw/barge
https://vagrantcloud.com/ailispaw/barge?access_token=pMcxxxxxxxxxxxxxxxxxxxx

3.　Vagrantfile added
$ vi Vagrantfile
# -*- mode: ruby -*-
# vi: set ft=ruby :

# echizenya added
Vagrant::DEFAULT_SERVER_URL.replace('https://vagrantcloud.com')

# A dummy plugin for Barge to set hostname and network correctly at the very first `vagrant up`
module VagrantPlugins
  module GuestLinux

Thank you for your review.

I meant that you had to replace just atlas.hashicorp.com with vagrantcloud.com.
Please check the URL in metadata_url.
I didn't do any step 1,2 and 3.

@ailispaw
Thank you for your comment.

I meant that you had to replace just atlas.hashicorp.com with vagrantcloud.com.
Please check the URL in metadata_url.

Should I interpret the comment as follows?
1. ailispaw → echizenya modified

$ vi ~/.vagrant.d/boxes/ailispaw-VAGRANTSLASH-barge/metadata_url
https://vagrantcloud.com/echizenya/barge?access_token=pMcxxxxxxxxxxxxxxxxxxxx

2. "Vagrantfile added" delete
$ vi Vagrantfile
# -*- mode: ruby -*-
# vi: set ft=ruby :

# echizenya added ← delete

# A dummy plugin for Barge to set hostname and network correctly at the very first `vagrant up`
module VagrantPlugins
  module GuestLinux

Thank you for your review.

Please refer to my first comment.
I guess that your ~/.vagrant.d/boxes/ailispaw-VAGRANTSLASH-barge/metadata_url looked like
https://atlas.hashicorp.com/ailispaw/barge?access_token=xxxxxxxxxxxxxxxxxxxx.
After you replace the domain atlas.hashicorp.com with vagrantcloud.com,
it should look like https://vagrantcloud.com/ailispaw/barge?access_token=xxxxxxxxxxxxxxxxxxxx.

Thanks for frequent comments.

After you replace the domain atlas.hashicorp.com with vagrantcloud.com,
it should look like https://vagrantcloud.com/ailispaw/barge?access_token=xxxxxxxxxxxxxxxxxxxx.

Should I interpret the comment as follows? I added "sed" command.
$ cd ~/.vagrant.d/boxes/ailispaw-VAGRANTSLASH-barge
$ cat metadata_url
https://atlas.hashicorp.com/ailispaw/barge
$ cp metadata_url metadata_url.org
$ sed -i -- 's/atlas.hashicorp/vagrantcloud/g' ~/.vagrant.d/boxes/*/metadata_url
$ ls
metadata_url-- metadata_url.org metadata_url
$ vi metadata_url
# "?access_token=pMcxxxxxxxxxxxxxxxxxxxx" added
https://vagrantcloud.com/ailispaw/barge?access_token=pMcxxxxxxxxxxxxxxxxxxxx

but,  a yellow character "Illegal characters found in URL" is displayed...

Therefore I will write unclear points about this issue on my Japanese blog, post it on Facebook and I will give advice from my friends. Or I would like to ask someone to tell me in person.
What do you think?

$ cat metadata_url
https://atlas.hashicorp.com/ailispaw/barge

まず、これがおかしいですね。?access_token= 以降の文字列もあったはずです。
なので、?access_token=pMcxxxxxxxxxxxxxxxxxxxx を後から追加する必要はありません。
Illegal characters found in URL ということは、何か修正に失敗して変な文字コードが入ってしまったのかも知れません。
metadata_url.zip
念の為、私のものを添付します。これをそのまま使っても大丈夫だと思います。たぶん。

@ailispaw  さん。
日本語によるコメントありがとうございます。またファイルの添付もありがとうございます！
1と2のいずれも試してみましたが、やはりIllegal characters found in URLが表示されてしまいます...

1.

なので、?access_token=pMcxxxxxxxxxxxxxxxxxxxx を後から追加する必要はありません。

https://vagrantcloud.com/ailispaw/barge のみaccess_tokenは使わずにvagrant up
2.

念の為、私のものを添付します。これをそのまま使っても大丈夫だと思います。たぶん。

https://vagrantcloud.com/ailispaw/barge?access_token=xxxxxxxxxxxxxxxxxxxxでaccess_tokenを使ってvagrant up

ひょっとしたら、私のPCでWocker以外のどこかで不具合が出ているのかもしれません。
Wockerに詳しい知人に連絡を取ってみて対面で確認してみようと思いますが、いかがでしょうか？
せっかくたくさんのコメントをいただいたにも関わらず、解決させることができず誠に申し訳ありません。

authors: ailispaw echizenyayota

repo: wckr/wocker


text:
Update the app to morph

As Flas was, this very useful application deserves not to disappear and to be also updated to Morph because the vivid support won't last...

I'm pretty sure Shoutcast doesn't use Oxide so we're fine :)
Flas uses a webview for reasons far too long to be interesting ;)

@cibersheep If there is nothing to be done on this side, then so much the better because this good application should not be forgotten !! Flas and Shoutcast make a great pair !

@gbdomubpkm as @cibersheep said there is no imminent problem with Oxide or Morph.

Ok understood.

authors: cibersheep gbdomubpkm wdehoog

repo: wdehoog/shoutcast-ubports


text:
Error: Incorrect padding

ERROR in the tokenizer Cell

你可以试试这个：https://colab.research.google.com/drive/11MQb8Bn4Ck707VEcqqGVdytqOk3OrQQK?usp=sharing
直接运行就行，需要去外网

但是为什么本地就不能报错， Incorrect padding

检查一下是不是tiktoken版本的问题，我暂时没有遇到

你好，想请问一下，这种大模型能够像小模型一样添加自己设计的模块吗？

添加是可以添加，主要是训练是难点，需要的显存太多了。所以基本就是两种方法添加模块：

lora算法，冻结主干网络，在模型的线性层添加一些旁路参数；
类似RM模型的方法，冻结主干网络，替换lm_head，比如做分类之类的任务，只训练lm_head，但是这样显存要的也不小。

authors: KeepFaithMe shenyewei virus188 wdndev


text:
Sample app crashes when tapping on Date

java.lang.IllegalStateException: Can't change tag of fragment DatePickerFragment{16de943 #1 id=0x7f0c0071 android:switcher:2131492977:1}: was android:switcher:2131492977:1 now android:switcher:2131492977:2

That's possible, I'll check this out

authors: amanzan wdullaer

repo: wdullaer/MaterialDateTimePicker


text:
Create command for theme boilerplate

Ich habe ein neuen Template Repo erstellt wearerequired/wordpress-theme-boilerplate.
@ocean90 Wie könnte ich es Testen bevor ich auf npm zu veröffentlichen?
https://github.com/wearerequired/default-wordpress-theme/issues/44

Lokal testen kannst du es mit npm link.

repo: wearerequired/js


text:
Add onClick handler to pay/save button

Describe the feature you'd like to request
Context: Trying to add an onClick listener to the save button, but there isn't a way to do that.
I see there's the submit prop (added here), which I thought would be triggered on submission (i.e. on click), but the official SDK docs say this event is only emitted by pressing "Enter" while editing a field (crucially, not on click). I have verified this by adding a log into my submit handler:
<CreditCardInput
  text="Text"
  submitButtonId={submitButtonId}
  children={isCardProcessing ? <LoadingIcon/> : null}
  submit={(e) => {
    console.log('executing submit callback') // never logged on click. does log on `enter`
    setIsCardProcessing(true)
  }}
/>

Describe the solution you'd like
Add an onClick field to the buttonProps prop of the CreditCardInput (a la what you proposed here). From there, pass it to the button.
Describe alternatives you've considered
Passing the callback to the submit prop, but that's only triggered when you hit Enter.

Hi @man-of-seafood currently in the canary version we support all kind of props for the button element, so you can write it and will appear all the methods that support it. Can you give it a try on canary and see if it's working?

We consider the canary version right now as "stable" now we are writing all the new docs

New version is published https://github.com/weareseeed/react-square-web-payments-sdk/releases/tag/v3.0.0

authors: danestves man-of-seafood


text:
Different service target port

Hi,
the current behaviour when "duplicating" services is to use the canary.Spec.Service.Port for both the service port and the target port.
In all our apps we currently configure our services on port 80, and on container ports on something else (like 8080 for example).
I'd like to create a PR to allow a TargetPort in the canary spec, but before I wanted to check with you if there is a reason for using the same port for both the service and the container.
thanks

The reason is simplicity. Flagger also does port discovery and maps all container ports in the ClusterIP service. I'm ok with adding service.portTarget as an optional field but please make sure this change doesn't break AppMesh, Linkerd and all the other integrations.

ok, thanks

We also need this and I'd be happy to help testing the AppMesh side of things

Happy to test out with Linkerd here

I've implemented this in #327 and added e2e tests for Istio, Linkerd and Kubernetes CNI. NGINX should probably work if the ingress is mapped to the service port instead of the container port.
I'm pretty confident using target port breaks:

App Mesh due to virtual nodes and virtual routers
Gloo due to upstream groups

great, thanks @stefanprodan!

authors: hollinwilkins nilscan stefanprodan vbehar

repo: weaveworks/flagger


text:
Add webhookUrl env parameter

Proposal for @stefanprodan s suggestion to secure the event webhook Url: https://github.com/weaveworks/flagger/issues/426#issuecomment-584153872

Thank you @stefanprodan
When are you planning the next release?

The next release will take a while, the APIs haven been promoted to v1beta1 and there is a lot of documentation I need to write to cover the new CRDs.

authors: heubeck stefanprodan


text:
Ordering of installation.

So, it appears that I must install CRD definitions before their use.  This places an ordering constraint on helm installations.  However, I cannot control the order of helm installations in the Helm operator.
For example, I am trying to use the Bitnami Sealed Secrets Controller.  I need to install it before I provide a SealedSecret CRD.  To do so, I cannot simply create a HelmRelease for the Controller (w/ CRDs).  Instead, I must install the Controller outside of the Operator.
Is this correct?  Is there a way to impose an ordering?

The helm-op will retry the installation every 3 minutes. If you have a release with the Sealed Secrets Controller and another one that contains SealedSecrets, the 2nd one will fail at first but at the next run, the CRD is installed and it will succeed.

Thank you.

I had the same question. Should this be in the documentation proper? Also, is that 3 minutes configurable? In particular, can it be force retried from fluxctl (say a quick fix was known and performed to release a blocking item)?

authors: derrickburns hlascelles stefanprodan

repo: weaveworks/flux


text:
Git commit signing

This adds support for flux to sign git commits made to the central config repo. This is important for security-minded users who want to make sure that all commits to the config repo come from an authenticated source, and is the first step towards the larger goal of optionally having flux only apply changes if the latest config has a valid signature from a trusted key.

@scjudd, this PR has been stale for a while now and we would like to get it merged!
Are you still interested in finishing it up or do you want me to take over the remaining part? In case of the latter, can you please flip the setting which lets us push to the PR branch? Thanks in advance :medal_sports:

Rebased -- almost all the conflicts were trivial (unrelated changes that happened to touch adjacent lines). The exceptions:

in git/operations.go, there's a new argument introduced here for environment entries, while in master, there were changes to how environment entries were prepared. I've made those mesh again, in
fe8046e.
I elided the changelog update, because in the meantime I decided it was better for people to just suggest the entry in their PR and for it to be collated later. The suggested entry is this:

- Flux is now capable of signing commits made to the user git repo
  [Git commit signing](https://github.com/weaveworks/flux/blob/master/site/git-commit-signing.md)

Please feel free to finish this up, sorry for not being able to contribute recently! Thank you all!

Looks good -- I am evaluating at a second or third derivative, now -- Fons, mind having a fresh look?

Will do! I am off today though.

Let's go for the envelope variable then!
On Fri, Mar 1, 2019, 22:45 Hidde Beydals notifications@github.com wrote:

@hiddeco commented on this pull request.
In git/working.go
https://github.com/weaveworks/flux/pull/1394#discussion_r261782468:

SetAuthor   bool

SkipMessage string

GPGHomeDir  string

I have been playing around with the idea (after the brief discussion we
had in private) and I think GNUPGHOME should still be configurable from
outside the package.
Overwriting the var in a test in the git package is great but prevents
packages using the machinery to sign commits as they have no control over
GNUPGHOME.
This leaves us with two options; we either put it into the Config struct
or we allow inheritance of the GNUPGHOME env variable. The latter being a
lot cleaner and even helpful to our users as they now have control over
where their imported keys are stored.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/weaveworks/flux/pull/1394#discussion_r261782468, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACQOJFJSwOGj7K2oO-UMoFPnZz0sOZFBks5vSa2lgaJpZM4W67cE
.

@scjudd it only took us 5 months but this has finally landed in master. Thanks a lot for your initial work on this, much appreciated :100: :1st_place_medal:

authors: 2opremio hiddeco scjudd squaremo


text:
don't print env variable values in the logs (some are sensitive)

Happy new year friends!!! 👏🏼 🍾 😄
While testing out v1.9.0, I realized I made a mistake in https://github.com/weaveworks/kured/pull/464 PR that prints in the log the value of the Environment Variables that are being bound to command flags, since some of these are sensitive (like KURED_NOTIFY_URL) we don't want their values to end up in the logs.
This PR addresses it, I think this is relatively important to merge in and perhaps worth cutting a v1.9.1 since currently it leaks sensitive details to the logs.
apologies for not catching this sooner.
/cc @ckotzbauer @evrardjp @jackfrancis (just tagging you folks for awareness as you've had the chance to review the original PR)

Thanks @ckotzbauer & @jackfrancis for taking a look and approving 🙏🏼  do you think we can go ahead and merge this?

repo: weaveworks/kured


text:
Conntrack fails if net.netfilter.nf_conntrack_acct = 1

This adds more information to the conntrack lines ("packets" and "bytes") which breaks the line parser introduced in #2095:
Error parsing dumped flow "tcp      6 9 CLOSE src=127.0.0.1 dst=127.0.0.2 sport=45294 dport=9091 packets=3 bytes=164 src=127.0.0.2 dst=127.0.0.1 sport=9091 dport=45294 packets=2 bytes=112 mark=0 use=1 id=305795136": input does not match format

Well spotted! PR?

It also fails on Fedora because of SELinux being enabled:

Error parsing dumped flow "tcp      6 116 TIME_WAIT src=192.168.35.122 dst=172.217.18.211 sport=40748 dport=443 src=172.217.18.211 dst=192.168.35.122 sport=443 dport=40748 mark=0 secctx=system_u:object_r:unlabeled_t:s0 use=1 id=3032703296": input does not match format

All these just seem to add some stuff to the end. Is our parser really so sensitive to trip over that?

After #2095, the parser is 3 different Sscanf():
https://github.com/weaveworks/scope/pull/2095/files#diff-fdef364be5b01b6b4b78a0eaa1d0a241R269
But unfortunately, we need the last field (id=), that's why the Sscanf() is sensitive to additions in the middle of the line.
I could try to parse differently (with strings.Split, etc.) and check if the performance does not regress to how it was before with xml.

authors: alban iaguis rade

repo: weaveworks/scope


text:
Fix e2e make targets and issues uncovered

While debugging, I found that the make targets used by e2e test were not using the latest image built. After fixing them, I uncovered two issues that weren't previously discovered. These issues are fixed in this PR.

The mtls certificate secret was using flux-system as its namespace. This could be problematic if the user does not have flux-system namespace and want to install in another namespace. This caused the controller in CrashLoopBackOff state with the following error.

{"level":"error","ts":"2022-02-10T21:22:23.106Z","logger":"setup","msg":"problem running manager","error":"creating secret to update certificates: namespaces \"flux-system\" not found","errorVerbose":"namespaces \"flux-system\" not found\ncreating secret to update certificates\ngithub.com/weaveworks/tf-controller/mtls.(*CertRotator).refreshCertIfNeeded.func1\n\t/workspace/mtls/rotator.go:128\nk8s.io/apimachinery/pkg/util/wait.ConditionFunc.WithContext.func1\n\t/go/pkg/mod/k8s.io/apimachinery@v0.23.1/pkg/util/wait/wait.go:220\nk8s.io/apimachinery/pkg/util/wait.runConditionWithCrashProtectionWithContext\n\t/go/pkg/mod/k8s.io/apimachinery@v0.23.1/pkg/util/wait/wait.go:233\nk8s.io/apimachinery/pkg/util/wait.runConditionWithCrashProtection\n\t/go/pkg/mod/k8s.io/apimachinery@v0.23.1/pkg/util/wait/wait.go:226\nk8s.io/apimachinery/pkg/util/wait.ExponentialBackoff\n\t/go/pkg/mod/k8s.io/apimachinery@v0.23.1/pkg/util/wait/wait.go:421\ngithub.com/weaveworks/tf-controller/mtls.(*CertRotator).refreshCertIfNeeded\n\t/workspace/mtls/rotator.go:160\ngithub.com/weaveworks/tf-controller/mtls.(*CertRotator).Start\n\t/workspace/mtls/rotator.go:90\nsigs.k8s.io/controller-runtime/pkg/manager.(*runnableGroup).reconcile.func1\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.0/pkg/manager/runnable_group.go:218\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1581"}

The liveness and readiness probe health check endpoints were previously removed, causing the controller not becoming ready. @phoban01 please correct me if there was a reason those have been removed and what the correct fix should be.

This PR also adds outputting terraform version in the e2e flow.
Fix: https://github.com/weaveworks/tf-controller/issues/91

The e2e failure is related to runner pod not working.
pod/helloworld-auto-approve-runner      0/1     ImagePullBackOff   0          3m59s

I guess we are okay with this error until the runner implementation is finished, right?

Thanks @tomhuang12; you are correct these were inadvertently removed by me when adding the rotator.

repo: weaveworks/tf-controller


text:
[UI] Update Table FilterOptions Color

Depends on #2585

repo: weaveworks/weave-gitops


text:
gossip can be sent back to neighbour from which it was received

When weave picks random neighbours to send gossip to, it excludes the gossip source. Which is fine, but really we want to exclude the peer from which we received it, which in an incomplete mesh is not necessarily the same as the source.
The question then is whether we should exclude both the source and the sender. IMO the former is an unnecessary optimisation. And it is the only reason we cart around the source peer name in gossip. So I reckon we should only exclude the sender.

it is the only reason we cart around the source peer name in gossip

Though arguably interpretation of gossip should be possible w/o reference to the transport. Which means that if we want to exclude the sending peer then that is what we should cart around in the gossip.

Turns out that this problem actually only exists on #1695, not master. oops. Fixed on the branch.

repo: weaveworks/weave


text:
Add Anthropic module to client

Hey,
The anthropic module isn't accessible in the new release's type system. Refer to the screenshot below.

Has this been release with 3.1.4?
I think #197 might be related to this.

authors: ffleandro malgamves

repo: weaviate/typescript-client


text:
refactor(cli): use bpaf instead clap

binary size
We have a nice CI job for tracking binary sizes: https://github.com/web-infra-dev/oxc/actions/workflows/bloat.yml
main 63.8MiB vs PR (59.7MiB), which is one of the main reasons I wanted this change.
But even nicer, bpaf have colored output:

And I removed so much code from managing clap command and arguments!

Codecov Report
Patch coverage: 65.82% and project coverage change: +0.01% :tada:

Comparison is base (3110490) 92.20% compared to head (1ae2bcc) 92.22%.
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #756      +/-   ##
==========================================
+ Coverage   92.20%   92.22%   +0.01%
==========================================
  Files         203      202       -1
  Lines       41465    41312     -153
==========================================
- Hits        38233    38098     -135
+ Misses       3232     3214      -18

Files Changed
Coverage Δ

crates/oxc_cli/src/runner.rs
0.00% <ø> (-38.95%)
:arrow_down:

crates/oxc_cli/src/type_check/mod.rs
0.00% <0.00%> (ø)

crates/oxc_cli/src/command.rs
44.11% <44.11%> (ø)

crates/oxc_cli/src/lint/mod.rs
57.92% <94.87%> (-1.58%)
:arrow_down:

... and 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: Boshen codecov-commenter

repo: web-infra-dev/oxc


text:
[Bug Report]: Postcss-loader with Tailwindcss HMR not work

System Info
System:
OS: macOS 13.2.1
CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Memory: 319.28 MB / 16.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 18.12.0 - ~/.nvm/versions/node/v18.12.0/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v18.12.0/bin/yarn
npm: 8.19.2 - ~/.nvm/versions/node/v18.12.0/bin/npm
Browsers:
Chrome: 111.0.5563.64
Edge: 110.0.1587.69
Safari: 16.3
Details
Rspack did not trigger the update of src/styles/main.css (tailwind registered dependencies through postcss loader)
Reproduce link
https://github.com/skywalker512/rspacksse-lite
Reproduce Steps
pnpm i
pnpm dev
change tailwind css

Thanks for reporting, but since this issue is duplicated with https://github.com/web-infra-dev/rspack/issues/2177, closed

repo: web-infra-dev/rspack


text:
feat: loader

Summary
Almost the last missing piece of the webpack loader implementation.
In older version of rspack, rspack does not support dispatching
JavaScript pitching loader and native pitching loader at the same time.
This PR refactored the original loader-runner to use a state machine
sharing across native and JavaScript runtimes. Loader runners on both
JavaScript and native side will yield to each other if the next loader has
a different type.
closes https://github.com/web-infra-dev/rspack/issues/5735
closes https://github.com/web-infra-dev/rspack/issues/6457

Checklist

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

!bench

!eco-ci

!bench

!eco-ci

!eco-ci

!bench


text:
Updates note to v2 format

Overview
This updates the note to the new format discussed in the engineering meeting.
Namely the note is structured similarly to a web URL. It will look like
webb://v2:anchor/2:3/2:3/376530663462666132363364386239333835343737326339343835316330346233613961626133386162383038613864303831663666356265393735383131306237313437633339356565396266343935373334653437303362316636323230303963383137313235323064653062626435653761313032333763376438323962663662643664303732396363613737386564396236666231373262626231326230313932373235386163613765306136366664353639313534386638373137/?curve=Bn254&width=5&exp=5&hf=Poseidon&backend=Arkworks&token=EDG&denom=18&amount=0

webb://v2:anchor/2:3/2:3/376530663462666132363364386239333835343737326339343835316330346233613961626133386162383038613864303831663666356265393735383131306237313437633339356565396266343935373334653437303362316636323230303963383137313235323064653062626435653761313032333763376438323962663662643664303732396363613737386564396236666231373262626231326230313932373235386163613765306136366664353639313534386638373137/?curve=Bn254&width=5&exp=5&hf=Poseidon&backend=Arkworks&token=EDG&denom=18&amount=0

@nepoche @AhmedKorim  we should create a branch in the dapp that uses this update and when both are working together merge this in.
@filiplazovic @dutterbutter we should also bump the version in protocol-substrate and anywhere else we're using this and ensure tests pass before merging this.


text:
WIP: Create tests

Hello @obetomuniz,
First for all, congrats for slush package. It's very useful :)
This PR has some changes finished and another are in progress, like:

[x] Update version of dependencies
[x] Create tests for default task
[ ] Create tests for repo task

I plan to finish the job soon but wanted to share what I'm doing for you can see if have something to improve :)

@obetomuniz OMG, I see only now the current versions at continuous integration. Do you have any idea do upgrade that? If not, let me know because I go fix this Pull Request 👍

Hey @ceasbz, nice job with the tests, so please, go ahead to fix it, just keep in mind that before I accept this PR you'll need sync yours insertions in the webcomponents/generator-element project too.

authors: ceasbz obetomuniz

repo: webcomponents/slush-element


text:
Require documentation incorrect since v1.0.0

Referring to the documentation here:
https://github.com/webdriverio/wdio-cucumber-framework#require
It suggests I can require entire directories like this:
    require: [
        './path/to/steps'
    ]

This works fine in v0.3.1.
But in v1.0.0 it looks like Node's module resolution is now used, so the require paths have to be exact filenames or directories with an index.js or package.json file.
E.g.
    require: [
        './path/to/steps/example.js'
    ]

Shall I open a pull request to fix the documentation or is this a bug?

it's more of a lack of a feature I'd say, feel free to create a PR

Thanks for adding https://github.com/webdriverio/wdio-cucumber-framework/commit/562d2a37b841120ca9b9eeda4b8ac83c465f2b7a 👍

authors: colinrotherham lgandecki

repo: webdriverio/wdio-cucumber-framework


text:
TBB path issue

I'm having some issues with the basic usage path if someone can assist.
from tbselenium.tbdriver import TorBrowserDriver
with TorBrowserDriver("/path/to/TorBrowserBundle/") as driver:
driver.get('https://check.torproject.org')

/path/to/TorBrowserBundle/ << what should it be exactly.

My TorBrowser is installed in C:\Test software\Tor Browser, I've tried that directory and in addition I've tried "C:\Test software\Tor Browser\Browser" and "C:\Test software\Tor Browser\Browser\firefox.exe". Please clarify this part.

Unfortunately, Windows is not supported at the moment.

authors: DanailKazakov gunesacar

repo: webfp/tor-browser-selenium


text:
A-Buffer sample fails on some Android devices

On both a Pixel 4 and Pixel 6 (but not a Pixel 7) the A buffer sample fails with the following error:
Binding size (171606624) of [Buffer "linkedListBuffer"] is larger than the maximum binding size (134217728).
 - While validating entries[2] as a Buffer.
Expected entry layout: { binding: 2, visibility: ShaderStage::Fragment, buffer: { type: BufferBindingType::Storage, hasDynamicOffset: 0, minBindingSize: 32 } }
 - While validating [BindGroupDescriptor "translucentBindGroup"] against [BindGroupLayout]
 - While calling [Device].CreateBindGroup([BindGroupDescriptor "translucentBindGroup"]).

Given that the size of the linkedListBuffer only differs between devices based on the canvas size, I went searching as was surprised to find that the Pixel 4 and 6 had a devicePixelRatio of 3.5, but the Pixel 7 I was testing only had a  devicePixelRatio of 2.5.
The buffer size/canvas resolution for this sample should be capped to stay under the binding limit.

I think another option here is scissor the scene and keep each section under the limit. I’ll work on a PR to do that so we can match the native resolution.

I think the option to scissor the scene is great! But it's also one that comes with performance tradeoffs and increased code complexity. It would be nice if it could be implemented in such a way that helps developers understand that it's not a required aspect of the technique, but instead a workaround to enable higher quality within the base limits.
Would it be feasible to make the scissor-for-full-res technique toggleable with a checkbox?

Totally feasible - i'll look into it.

repo: webgpu/webgpu-samples


text:
Github Topics

Please add github topics like shopware-plugins :)

done, thanks ;)

authors: dneustadt shyim

repo: webmatch/WbmQueryManager


text:
Pass options through to fallback

Hello! Thanks for the great plugin.
When setting a file size limit for url-loader, I'd like to also set my own file naming pattern for files exceeding the limit. The default fallback (file-loader) has a name option which I've used in the past but, looking at line 44 of index.js, it seems that there's no attempt to pass any options through to the fallback loader.
Is this something that could easily be added?

@djbingham can you describe use case?

Basically, I wanted to add a hash into the file name for cache-busting, like this:
{
    loader: 'file-loader',
    options: {
        name: '[path][name].[hash].[ext]'
    }
}

However, I've since realised that invalidates all of the caching within the build process, which is absolutely not what I want, so that seems like a bad idea. I'll have to rethink my cache-busting strategy.

@evilebottnawi  @michael-ciniawsky
Hey, guys, I have the same problem
Is it possible to pass options to the fallback loader? For example to the file-loader in case if I want to set name option.
This code not working:
_fileLoaderName =
  name: (
    if forProduction
      '[name].[ext]?[hash]'
    else
      '[name].[ext]'
  )

urlLoader =
  test: /\.(jpe?g|png|gif|ico)$/
  use: [
    loader: 'url-loader'
    options: {
      limit: 8192 # 8 Kb
      fallback: "file-loader?#{JSON.stringify(_fileLoaderName)}"
    }
  ]

I've seen code here, should we update logic of the url-uploader to support this feature or how can we achieve same result?
To support something like this:
_fileLoader =
  loader: 'file-loader'
  options: {
    name: (
      if forProduction
        '[name].[ext]?[hash]'
      else
        '[name].[ext]'
    )

urlLoader =
  test: /\.(jpe?g|png|gif|ico)$/
  use: [
    loader: 'url-loader'
    options: {
      limit: 8192 # 8 Kb
      fallback: _fileLoader
    }
  ]

Is this issue solved? Why did it be closed?

¯_(ツ)_/¯

authors: djbingham evilebottnawi milushov vipcxj

repo: webpack-contrib/url-loader


text:
Update util to v0.11

This adds the promisify and callbackify methods.
This is not a breaking change.

@sokra any feedback?

Thanks

authors: goto-bus-stop sokra yeliex

repo: webpack/node-libs-browser


text:
Docs refer to deprecated webpack.optimize.UglifyJsPlugin

https://webpack.js.org/configuration/plugins/#plugins
I don't know if there's other stuff that needs to be updated here, or if maybe the documentation's been updated but it's just not published...

The UglifyJsPlugin itself isn't, but accessing webpack.optimize.UglifyJsPlugin is, because you're supposed to add it as a dependency and pass it to optimization.minimizer

Uhmm, using it as a plugin triggers a warning or something?
I think it works just fine as a plugin.

webpack.optimize.UglifyJsPlugin isn't exposed anymore, one has to explicitly import it since webpack >= v4.0.0
- const UglifyJsPlugin = webpack.optimize.UglifyJsPlugin
+ const UglifyJsPlugin = require('uglifyjs-webpack-plugin')

It ships with webpack and options can be passed to the 'build-in' plugin via config.optimization.minimize removing the need to import it at all in most cases

Please send a PR to this page (https://webpack.js.org/configuration/plugins/#plugins) updating it with your findings.

You just need to remove it from the plugins https://webpack.js.org/configuration/plugins/#plugins page
It is documented here btw: https://webpack.js.org/configuration/optimization/

Also presumably the CommonsChunkPlugin usage should be updated to show requireing it, and likely other stuff is outdated. I don't want to work on this; I've never used the plugins option, and so I hope someone with at least that qualification can pick this up.

@1j01 ok, in that case im picking it up

authors: 1j01 EugeneHlushko michael-ciniawsky montogeek


text:
chore(rebuild): re-incorporate header links

Src code patched until
https://github.com/ben-eb/remark-autolink-headings/pull/41 is merged, if
ever, we should probably use a fork.

Ohh, seems Ben isn’t very active in remark anymore. Let me see and check in with him if he’s interested in moving it to @remarkjs

@montogeek not seeing any links pop up in the h* elements... do I need to install the package from that fork in order for it to work?

Nvm used @rigor789's fork, @rigor789/remark-autolink-headings, which works. Cleaning up the styling slightly and then pushing/merging and knocking another one down 🎉. Thanks for digging into this @montogeek.

@skipjack Yep, I patched it locally applying same changes as that fork

authors: montogeek skipjack wooorm


text:
Improve HMR docs

This PR improves the HMR docs.
There were two pages that were duplicate ("HMR with React" and "HMR"). I removed the "HMR" page because it only explained HMR for React. After that I fixed lots of minor errors in the "HMR with React" page.

I also added a HMR concepts page based on @sokra's answer on StackOverflow. That content can probably use a diagram or something, but this is a good start.


text:
docs(Content) --> improve configuration-languages,configuration-types,entry-context,index,output

Improved the documentation for better developer experience .

@snitin315 , hope you take a look!

@snitin315  hope its all fine now and could you add a hactoberfast tag or something i am actually participating this year and i just got started with open source and i am loving it

If you are looking for contributing to hactoberfast, you should search the hactoberfast tag first instead of adding it later, this is not how it works. As far as I know, there's no plan for this project to participate the hactoberfast.

If you are looking for contributing to hactoberfast, you should search the hactoberfast tag first instead of adding it later, this is not how it works. As far as I know, there's no plan for this project to participate the hactoberfast.

Ok :-)

authors: Biki-das chenxsan


text:
Hook for modifying entrypoint from plugin

Feature request

What is the expected behavior?
There should be a function that allow entrypoint to be changed after the compiler is created, but before compilation has started.
What is motivation or use case for adding/changing the behavior?
See this issue in webpack-serve. In short, iterating entrypoints from a compiler, process, and calling compiler.hooks.entryOption with the new value does not works well with runtimeChunk: single as the old entrypoint plugin will still exists.
How should this be implemented in your opinion?

Plan A: Creating a registry of active entrypoint plugin instances (MultiEntryPlugin/SingleEntryPlugin/DynamicEntryPlugin), then when EntryOptionPlugin trigger again:

A: Ask the old instance of the same entrypoint to deregister.
B: Recreate all instances. This allow entrypoints to be removed, but caller now has to send list of ALL entrypoints which is a breaking change.

Plan B: Investigate in why RuntimeChunkPlugin does not work with duplicated entrypoints. This might resolve this issue, but could run into more issues in the future.

Are you willing to work on this yourself?
If I have some guideline.

IMHO it's flawed that creating a compiler instance automatically creates and applies entry plugins at that point in the process. There are some reasons for it as I understand it, but it's still flawed. I'd also consider it a flaw that we cannot examine or modify entrypoints after the chosen type of entry plugin has been applied. Too much black-box here.

authors: shellscape whs

repo: webpack/webpack


text:
fix(ProfilingPlugin): crash under watch mode (fix #9114)

fix #9114 , allow ProfilingPlugin works under watchMode. It will keep recording until stop watching.

What kind of change does this PR introduce?

bugfix
Did you add tests for your changes?

No, but I can add in following commits. 😀
Does this PR introduce a breaking change?

No.
What needs to be documented once your changes are merged?
The plugin will listen to ctrl + c and throw an error to exit process (maybe there's a better way to do this) and it may affect plugins after it.

Now a new tracer will be created on watchRun hook except the first time because the tracer has been created at the very beginning.

[x] test added

Don't know why Travis failed 😅

Fixed https://github.com/webpack/webpack/pull/15157, very very very big sorry for delay


text:
docs(types): Add docs for compilation.afterChunks hook

Summary

🤖 Generated by Copilot at 1b6b741
Document the afterChunks hook in lib/Compilation.js with a JSDoc comment. This improves code quality and helps developers who use the hook.
Details

🤖 Generated by Copilot at 1b6b741

Document the afterChunks hook in lib/Compilation.js with a JSDoc comment (link)

Note for @chenxsan: the specific piece that needs to be documented here is adding of the hook itself into compilation and the recommendation.
You can also provide the following source code: https://github.com/webpack/webpack/blob/main/lib/wasm-sync/WebAssemblyModulesPlugin.js#L114-L137 as the educational example of how the hook is used by webpack today.
You can leverage the comments I added to the type itself as the content for the documentaiton.


text:
Use a WeakMap instead of mutating objects in NMF

NormalModuleFactory was mutating dependency objects if the unsafeCache option was set. This PR uses a WeakMap to cache dependencies and avoid the mutation (and de-opt).
What kind of change does this PR introduce?
refactoring
Did you add tests for your changes?
no
Does this PR introduce a breaking change?
no
What needs to be documented once your changes are merged?
nothing

Thanks

authors: ooflorent sokra


text:
Documentation or pointers in using release-it in javascript (node 8)

Hi,
After reading the issues it appears that it is supported to call the release-it in javascript using node v8 or later.
Could anyone let me know some further info, any documentation?
I saw this in the issues, anything else I can do ?
Or is it a case of looking inside the javascript file ?
I presume this is the same package as the cli ?
const ReleaseIt = require("release-it").default
ReleaseIt({
  "non-interactive": true,
  npm: {
    publish: false
  }
}).then(…)

Thanks in advance

Yes, this is an undocumented feature indeed. Feel free to use it though, I'll document it shortly.
For now, this is the object the promise resolves with when release-it is done: https://github.com/webpro/release-it/blob/c6d079f7d6bce287b6bf5b48dbf250ab6aed27c8/lib/tasks.js#L213-L217
I'll keep this issue open until it is documented.

authors: appsolutegeek webpro

repo: webpro/release-it


text:
Add initial e2e tests

This is a first crack at issue https://github.com/webrtc-rs/webrtc/issues/42.
This is also my first crack at writing Rust, so I'm looking for feedback and suggestions. My code is almost certainly not idiomatic and I've probably made some simple mistakes with ownership, particularly across async calls.
See the tests README for general info.
See https://github.com/webrtc-rs/webrtc/pull/47 for the original pull request

@littlebenlittle thanks for the pr, will be reviewing shortly.

@littlebenlittle thanks for the pr, will be reviewing shortly.

@littlebenlittle this PR is bulky can this PR only Implement basic_e2e so we can sort out all issues?
Also, we should make all test files standalone if possible, structs and enums not needed across multiple files can be defined in a single file. We should do away with test_mod.rs if possible.
We also need to define integration tests in cargo.toml
[[test]]
name = "basic"

more here https://doc.rust-lang.org/cargo/reference/cargo-targets.html#tests

@littlebenlittle this PR is bulky can this PR only Implement basic_e2e so we can sort out all issues?
Also, we should make all test files standalone if possible, structs and enums not needed across multiple files can be defined in a single file. We should do away with test_mod.rs if possible.
We also need to define integration tests in cargo.toml
[[test]]
name = "basic"

more here https://doc.rust-lang.org/cargo/reference/cargo-targets.html#tests

@littlebenlittle seem dtls::ConfigBuilder is not defined

@littlebenlittle seem dtls::ConfigBuilder is not defined

authors: littlebenlittle metaclips

repo: webrtc-rs/dtls


text:
package.repository is set to archived repos in many Cargo.tomls

Clicking links on crates.io or docs.rs redirects to these old repos instead of here.

Came here to report the same thing for https://github.com/webrtc-rs/webrtc/blob/master/sctp/Cargo.toml#L10

authors: JonahPlusPlus mauricelam

repo: webrtc-rs/webrtc


text:
[question] SyntaxError: Unexpected token '.'

After fresh installation from the guide, I get this error:
$ wscat
/usr/local/lib/node_modules/wscat/node_modules/https-proxy-agent/dist/index.js:55
        this.proxyHeaders = opts?.headers ?? {};
                                 ^

SyntaxError: Unexpected token '.'
    at wrapSafe (internal/modules/cjs/loader.js:915:16)
    at Module._compile (internal/modules/cjs/loader.js:963:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:85:18)
    at Object.<anonymous> (/usr/local/lib/node_modules/wscat/bin/wscat:7:25)
    at Module._compile (internal/modules/cjs/loader.js:999:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)

Looks like my installation is broken

I'm using Ubuntu 22.04 LTS.
Installed npm from apt with sudo apt install npm
Then installed wscat, as guide said, globally sudo npm install -g wscat
Looks like I have this node-js version:

$ node
Welcome to Node.js v12.22.9.

got same error here, does https://github.com/websockets/wscat/commit/d27706110bc9566b938204934f2a9d029ca04cff released?

repo: websockets/wscat


text:
fix SelectQuery for casandra > V2

For Cassandra > V2, if a SelectQuery with WHERE clause calls consistencyLevel_=, the WHERE clause will appear twice and rejected by Cassandra.

This was for 1.11. Looks like V2.2 support is already in master so I'll close this. Looking forward for the new release.

repo: websudos/phantom


text:
Optimize sizing and spacing

Updates sizing and spacing where it seems appropriate, includes some minor additional style fixes, removals / updates.

Mobile Current

Mobile Proposal

Desktop Current

Desktop Proposal

the last commit optimizes the spacing below the Contribute to the WebUI project using your preferred programming language sentence in the footer - not visible on the screenshots.

repo: webui-dev/website


text:
Create unbind function

Line 1251 fixes a preexisting memory leak. That line dynamically allocates a pointer which we never use. Since it is passed as a void*, we cannot free that memory. Deleting a void pointer is undefined behavior.
The rest of the code is based on https://github.com/CptWesley/webview/commit/9e8794dc67f56d6c7dc060e85d10b77a98e626c3, though I needed to fix some memory leaks.
This library provides a way to bind JS and C functions, but it does not allow the user to unbind. As noted in issue https://github.com/webview/webview/issues/644, that is a security issue, so I believe this PR should be merged.

Since this is an API change, it may also affect bindings. This is a major change I'm not prepared to consider merging.
@nothingismagick @abeMedia @zserge Could any of you look at this?

Confirm if I'm understanding it correctly.
This API change isn't a "breaking" one. It provides an extension to the current API and, initially, doesn't seem to affect existing bindings. @dandeto any feedback on this regard?
If you still prefer to not merge this PR, is this case, would you agree to Dandeto in creating a new one with at least the memory leak fix?

@paulocoghi That is correct, it only adds functionality. It will not change anything about the bindings themselves, it just allows a programmer to remove a binding.

It would be helpful to have Go bindings for this as well, if anyone would like to work on them.

authors: dandeto justjosias paulocoghi

repo: webview/webview


text:
🛑 Member Genesis is down

In 36b4fc2, Member Genesis (https://www.membergenesis.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Member Genesis is back up in fd6b17d.

repo: webworldview/uptime


text:
Auto complete, part 1

#225
demo:
https://user-images.githubusercontent.com/13651389/151004594-8562fa49-a4f8-411e-b79c-89bb5f717553.mp4

Some todos have been tracked.
@tanbowensg There are two FIXME marks in this PR that need review comments, thanks!

CI passed

Can I merge this now or wait part2?

@tanbowensg sure

repo: webzard-io/sunmao-ui


text:
Mac 上压缩纹理卡死

描述Bug
在Mac上执行压缩纹理，在【阶段2/2】中卡死
运行环境
Mac

TextToolDatas.zip

使用Arm芯片？

是的，苹果芯片

如果还有问题，请联系小助手详细排查：https://wechat-miniprogram.github.io/minigame-unity-webgl-transform/Design/IssueAndContact.html

authors: Oooocean liuxinyumocn zgc0911


text:
workPro在与vue3结合提示包有问题。

我在将workPro 与vue3的hello world 结合时候，提示包有问题，我按操作将，etcd3、aws-sdk等包重新安装后依旧出错。
我是按vue3的官方文档执行命令：npm create vue@latest,然后添加了 workPro的依赖包“ @grpc/grpc-js": "^1.8.12",
"@juzi/wechaty": "^1.0.65",
"@juzi/wechaty-puppet": "^1.0.61",
"@juzi/wechaty-puppet-service": "^1.0.69",
"qrcode-terminal": "^0.12.0",
"vue": "^3.4.21",
"wechaty": "^1.20.2""。在没有添加依赖包的时候，是可以启动 vue3的demo的。添加之后，运行错误如下，
`
(base) daifeng@daif-MacBook-Pro wechaty-vue3 % npm run dev

wechaty-vue3@0.0.0 dev
vite

VITE v5.2.9  ready in 684 ms
➜  Local:   http://127.0.0.1:5173/
➜  Network: use --host to expose
➜  press h + enter to show help
✘ [ERROR] Could not resolve "etcd3"
node_modules/memory-card/dist/esm/src/storage/etcd.js:1:22:
  1 │ import { Etcd3 } from 'etcd3';
    ╵                       ~~~~~~~

You can mark the path "etcd3" as external to exclude it from the bundle, which will remove this
error and leave the unresolved path in the bundle.
✘ [ERROR] Failed to resolve entry for package "jimp". The package may have incorrect main/module/exports specified in its package.json. [plugin vite:dep-pre-bundle]
node_modules/esbuild/lib/main.js:1374:21:
  1374 │         let result = await callback({
       ╵                      ^

at packageEntryFailure (file:///Users/daifeng/workerspace/html/wechaty-vue3/node_modules/vite/dist/node/chunks/dep-_QLjGPdL.js:48316:17)
at resolvePackageEntry (file:///Users/daifeng/workerspace/html/wechaty-vue3/node_modules/vite/dist/node/chunks/dep-_QLjGPdL.js:48313:5)
at tryNodeResolve (file:///Users/daifeng/workerspace/html/wechaty-vue3/node_modules/vite/dist/node/chunks/dep-_QLjGPdL.js:48083:20)
at Context.resolveId (file:///Users/daifeng/workerspace/html/wechaty-vue3/node_modules/vite/dist/node/chunks/dep-_QLjGPdL.js:47833:28)
at Object.resolveId (file:///Users/daifeng/workerspace/html/wechaty-vue3/node_modules/vite/dist/node/chunks/dep-_QLjGPdL.js:51110:64)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async file:///Users/daifeng/workerspace/html/wechaty-vue3/node_modules/vite/dist/node/chunks/dep-_QLjGPdL.js:68299:21
at async file:///Users/daifeng/workerspace/html/wechaty-vue3/node_modules/vite/dist/node/chunks/dep-_QLjGPdL.js:48656:34
at async requestCallbacks.on-resolve (/Users/daifeng/workerspace/html/wechaty-vue3/node_modules/esbuild/lib/main.js:1374:22)
at async handleRequest (/Users/daifeng/workerspace/html/wechaty-vue3/node_modules/esbuild/lib/main.js:732:11)

This error came from the "onResolve" callback registered here:
node_modules/esbuild/lib/main.js:1293:20:
  1293 │       let promise = setup({
       ╵                     ^

at setup (file:///Users/daifeng/workerspace/html/wechaty-vue3/node_modules/vite/dist/node/chunks/dep-_QLjGPdL.js:48636:19)
at handlePlugins (/Users/daifeng/workerspace/html/wechaty-vue3/node_modules/esbuild/lib/main.js:1293:21)
at buildOrContextImpl (/Users/daifeng/workerspace/html/wechaty-vue3/node_modules/esbuild/lib/main.js:979:5)
at Object.buildOrContext (/Users/daifeng/workerspace/html/wechaty-vue3/node_modules/esbuild/lib/main.js:788:5)
at /Users/daifeng/workerspace/html/wechaty-vue3/node_modules/esbuild/lib/main.js:2224:68
at new Promise (<anonymous>)
at Object.context (/Users/daifeng/workerspace/html/wechaty-vue3/node_modules/esbuild/lib/main.js:2224:27)
at Object.context (/Users/daifeng/workerspace/html/wechaty-vue3/node_modules/esbuild/lib/main.js:2048:58)
at prepareEsbuildOptimizerRun (file:///Users/daifeng/workerspace/html/wechaty-vue3/node_modules/vite/dist/node/chunks/dep-_QLjGPdL.js:52839:35)

The plugin "vite:dep-pre-bundle" was triggered by this import
node_modules/file-box/dist/esm/src/qrcode.js:4:17:
  4 │ import Jimp from 'jimp';
    ╵                  ~~~~~~

✘ [ERROR] Could not resolve "aws-sdk"
node_modules/memory-card/dist/esm/src/storage/s3.js:1:20:
  1 │ import AWS_SDK from 'aws-sdk';
    ╵                     ~~~~~~~~~

You can mark the path "aws-sdk" as external to exclude it from the bundle, which will remove this
error and leave the unresolved path in the bundle.
✘ [ERROR] Could not resolve "esdk-obs-nodejs"
node_modules/memory-card/dist/esm/src/storage/obs.js:2:22:
  2 │ import ObsClient from 'esdk-obs-nodejs';
    ╵                       ~~~~~~~~~~~~~~~~~

You can mark the path "esdk-obs-nodejs" as external to exclude it from the bundle, which will
remove this error and leave the unresolved path in the bundle.`

以我的了解vue3是针对浏览器环境的前端框架，而Wechaty是运行在node中的，无法简单结合。

无反馈，问题关闭。

@qcfengdaai We have planned to build Wechaty in the browser before, and we have an Angular component (under construction) at https://github.com/chatie/angular if you are interested.
I think the latest Angular component can be compiled to be compatible with VUE so that it can also be loaded in VUE.
Please join our Discord for future discussion (I'd love to support it in the future) if you want to run Wechaty directly in the browser.
Wechaty Discord: https://discord.gg/7q8NBZbQzt

authors: hcfw007 huan qcfengdaai

repo: wechaty/puppet-supports


text:
How to get the talker_id?

Is the talker_id uniqule?
THX

talker instance is a type of Contact, and every Contact instance has a contact_id attribute, which is the unique for contacts.

repo: wechaty/python-wechaty


text:
Add retry strategy for Token Service Discovery

A very simple retry policy will be enough for the most common errors, for example, the DNS timeout, or the connect has not succeeded for the first time.

大神你好，想申请一个token用！我是小白，仰慕大神已久，想体验一下wechaty的功能，谢谢大神！

authors: Tajra huan

repo: wechaty/token


text:
fix: 🐛 remove swc dependencies

https://github.com/wechaty/wechaty/issues/2549

Why isn't CI running...

repo: wechaty/wechaty


text:
The predict page is harder to see in the docs.

There is a predict page, but iuts hard to find.

Because the predict pages were split into 'getting started', there isn't a 'prediction' page in the user guide. We should duplicate some information from https://deepforest.readthedocs.io/en/v1.4.1/getting_started/intro_tutorials/index.html into a single prediction page after
https://deepforest.readthedocs.io/en/v1.4.1/user_guide/01_Reading_Writing_data.html
in the doc tree.

repo: weecology/DeepForest


text:
CompileC build/Build/Intermediates.noindex/WeexDemo.build/Debug-

The following build commands failed:
CompileC build/Build/Intermediates.noindex/WeexDemo.build/Debug-iphonesimulator/WeexDemo.build/Objects-normal/x86_64/UIViewController+WXDemoNaviBar.o WeexDemo/WeexScanner/UIViewController+WXDemoNaviBar.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)
13:36:20 : Error:Error: Command failed: xcodebuild -workspace WeexDemo.xcworkspace -scheme WeexDemo -configuration Debug -destination id=----**********
-sdk iphonesimulator -derivedDataPath build clean build
2018-03-10 13:35:47.642 xcodebuild[12627:340520]  DTDeviceKit: deviceType from************ was NULL
** BUILD FAILED **
The following build commands failed:
CompileC build/Build/Intermediates.noindex/WeexDemo.build/Debug-iphonesimulator/WeexDemo.build/Objects-normal/x86_64/UIViewController+WXDemoNaviBar.o WeexDemo/WeexScanner/UIViewController+WXDemoNaviBar.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)
at checkExecSyncError (child_process.js:575:11)
at Object.execSync (child_process.js:612:13)
at _buildOnSimulator (/Users/sudeepiorta/.xtoolkit/node_modules/weexpack/lib/run/ios.js:328:18)
at /Users/sudeepiorta/.xtoolkit/node_modules/weexpack/lib/run/ios.js:300:7
at new Promise (<anonymous>)
at buildApp (/Users/sudeepiorta/.xtoolkit/node_modules/weexpack/lib/run/ios.js:289:10)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:118:7)

@sudeepdk see https://github.com/weexteam/weex-toolkit/issues/300#issuecomment-370652227.

repo: weexteam/weex-pack


text:
0.9.18

Is your feature request related to a problem? Please describe.
Merged fixes for

https://github.com/weichsel/ZIPFoundation/issues/306
https://github.com/weichsel/ZIPFoundation/issues/304
are not easily accessible for SPM consumption

Describe the solution you'd like
Publishing a new GitHub release that contains the changes for the two fixed issues mentioned above
Describe alternatives you've considered
Using branch or commit as dependency rule to resolve package version

Hi, thank you for the wonderful library
I also hope this issue gets resolved.

repo: weichsel/ZIPFoundation


text:
關於 occupancy resolution 和 ground truth 中的動態物體

你好，首先感謝開源這麼厲害的一個專案，跑過 training 之後有幾點問題想請教一下你們組的看法：

目前 SurroundOcc 的 output 是固定解析度的 voxel grid (XYZ)，在 Tesla AI Day 有提到他們最後除了 fixed-size voxel grid 以外還有 per voxel feature map 可以再遞給 MLP 透過 3D spatial point query 達到理論無限解析度的 continuous occupancy probability，像請問你們組關於這段的模型有什麼看法或相關實驗嗎？

目前 ground truth occupancy voxel grid 是透過將多偵 lidar point cloud 合併在一起，並透過 3d bbox label 將動態物體摳出對齊。不過這樣的做法實務上會面臨一個問題是，occupancy network 的一大優勢在於可以感知異形體或是沒有被 bbox 標注的複雜物體，但目前 SurroundOcc 生成 ground truth 的方法對於 dynamic object 只受限在已知的 bbox。想請問關於這點你們組有什麼想法或實驗嗎？

你好，关于你的两个问题我们有以下想法：

虽然我们没有在surroundocc里实现无限分辨率，但很容易在现有框架中加入这个功能，只需要对最后输出的occupancy进行三线性插值然后过个mlp即可，可以参考TPVFormer中的实现方式。但需要注意的是，虽然这种方式可以实现无限分辨率，但需要高分辨率的ground truth，使用低分辨率的真值可能会导致效果不好。
在surroundocc里我们利用bbox的ground truth将场景和物体（包括静态和动态）分隔开。我们认为网络具备泛化能力，对于没被bbox覆盖的动态异型物，网络也可以重建出来。除此之外，其实用bbox的ground truth去区分动静态只是一种方式，还可以利用一些更加low-level的方式例如场景流去区分。

@weiyithu  感謝你的回覆

看了一下 TPVFormer 的作法，的確是可以很容易套用到 surroundocc 上。在 TPVFormer 裡面過 mlp 的輸出是由單一 frame 的 lidar 稀疏點來進行監督，所以沒有分辨率的問題，如果无限分辨率也要套用 dense occupancy 監督這的確是要注意的一個點。
關於這個問題，比較擔心的不是泛化能力的問題，而是產生真值得時候，如果有动态异型物沒有被bbox覆盖，那會導致 voxel grid 的ground truth 會有這些异型物的殘影。不過透過其他像场景流的方法來區別静动态的確也是一個方向。

repo: weiyithu/SurroundOcc


text:
Restricted link to items

What does this change?
For #11310
Always shows a link to the item page for restricted things if the user has the correct role. This is mainly for audio/video which we would normally show on the work page. The restricted things won't play on the work page, but they do on the item page if the user is logged in and has the correct role.
How to test
Visit http://localhost:3000/works/esd6gs3s while not logged in/logged in with a user whose role !== 'StaffWithRestricted'.
There should be no 'available online' section present.
Visit http://localhost:3000/works/esd6gs3s while logged in with a user whose role === 'StaffWithRestricted'.
There should be an 'available online' section present and it should contain a link to the item page:
How can we measure success?
Can play the audio and video files of restricted items when logged in and have a role of 'StaffWIthRestricted'
Have we considered potential risks?
Limited risk, will only affect users with a role of 'StaffWithRestricted'

For me going to http://localhost:3000/works/esd6gs3s  and clicking View opens two tabs to Submit ?

The double quotes in the bottom left aren't there in prod, maybe just a typo somewhere?

For me going to http://localhost:3000/works/esd6gs3s and clicking View opens two tabs to Submit ?

Probably related to running in strict mode in dev:
"Your components will re-run Effects an extra time to find bugs caused by missing Effect cleanup."
I tried changing the next.config.js so it didn't run in strict mode, but it still happened. However, building the app then running stops it happening so I think this is fine to go in.
Not sure why changing the config didn't work, but will look into that another time.

The double quotes in the bottom left aren't there in prod, maybe just a typo somewhere?

It's inconsistent whether it displays or not. I can delete the entire page template and it can still show?!
However, I can also make it happen occasionally on prod, so I don't think it is something I've introduced. Do you mind if I just merge this?

However, I can also make it happen occasionally on prod, so I don't think it is something I've introduced. Do you mind if I just merge this?

Not at all, like you said it's unrelated and therefore not a blocker. I'll have a second go at running this locally.

authors: gestchild rcantin-w


text:
Use new storage/messaging libraries in the storage service

Follow-up notes:

[ ] StorageManifestVHS needs renaming, and to error if you try to put a different record than is already stored
[ ] Use an ObjectStore in BagService/StorageManifestService
[ ] Push more Dao stuff in IngestTracker

This is done! I've created separate tickets to track the other work.

repo: wellcometrust/platform


text:
Change grab_section to not capitalise section name

In https://github.com/wellcometrust/policytool/blob/master/policytool/pdf_parser/main.py we look for sections titles listed in https://github.com/wellcometrust/policytool/blob/master/policytool/resources/section_keywords.txt, and add them to a dictionary.
Currently we capitalise the names of these from the dictionary, and use this as the dictionary keys. The code is
if section:
   section_dict[title.title()] = section
   if section_dict.get(title.title()):
        section_dict[title.title()].append(section)
  else:
        section_dict[title.title()] = [section]

but we shouldnt capitalise since it causes confusion when comparing to 'section_keywords.txt'
if section:
   section_dict[title] = section
   if section_dict.get(title):
        section_dict[title].append(section)
  else:
        section_dict[title] = [section]

This will cause knock-on effects where we try to access 'References' in places (which has it's own issues since we should be looking for anything in 'section_keywords.txt' rather than explicitly looking for 'References').

@lizgzil make sure you use the right keyword to automatically close the github issues when you merge a PR https://help.github.com/en/articles/closing-issues-using-keywords
In this case, adding issue between fixes and the issue number probably broke it

authors: lizgzil nsorros

repo: wellcometrust/policytool


text:
Include sorting

The parser is responsible for preserving order inside blocks. However, the parser can't see the output of includes. There needs to be a subsequent pass after includes are resolved inside a block to sort the result of calling includes.
After resolving include/mixins inside a block, re-sort the entire block then walk the resulting block body. This requires significant refactoring of how rules are printed. Each time a block is encountered, record the block Node, print anything inside a block to a block buffer. If no includes are encountered, flush the buffer. Otherwise, truncate the buffer, resolve includes then start over walking the block.

Done

repo: wellington/sass


text:
Unable to start the package

After installing packages I ran yarn start to run this project, I got the following error:
).server(dirRoot, () => { ^ SyntaxError: Unexpected token )
Please help

see https://github.com/wellyshen/react-cool-starter/issues/108 for fix :)

@AbhayShiro Fixed this issue by the latest master branch, please try it.

authors: AbhayShiro iamacup wellyshen

repo: wellyshen/react-cool-starter


text:
Trying to deploy to AWS Elasticbeanstalk

I'm following the instructions provided here and I keep getting this error in aws console:
Failed to find package.json. Node.js may have issues starting. Verify package.json is valid or place code in a file named server.js or app.js.
Do I need to rename the root index file to app.js or something else? Everything has worked fine up until this point.

@redlinecodes Did you pack the package.json file to the cloud?

Close due to inactive.

authors: redlinecodes wellyshen


text:
Parameters when adding LM

Hello, I would like to ask which parameters will greatly affect the recognition results when adding a language model trained by myself, such as what is the appropriate setting of acoustic_scale?

Is the rescoring weight will affect, I think reducing the rescoring weight will increase the weight of wfst

authors: fclearner fuguanyu


text:
[fix] prepare_dict support english and chinese in one lexicon.txt

tools/fst/prepare_dict.py, it can't split chinese phrase into character when bpemodel given issus.  Now It can process english and chinese in one lexicon.txt .

please fix the lint problem.

./tools/fst/prepare_dict.py:44:125: B950 line too long (124 > 80 characters)


text:
Limit possibilities dictionary (ie: numbes only)

I have two apps that use voice. The first one the users are saying one of 300 items. Is it possible to limit the voice recognition to only return closest elements to ones in an array?
In another application, the users are saying a single number, or multiple numbers. Anyway to limit to just numbers?

Custom language model is usually provided with paid services (e.g., IBM
Watson). The default speech recognition, to my knowledge, does not provide
this feature.
However, you might calculate the closest word of the recognized word using
EDIT distance. Although this is a rough approximation, I guess it should
work in a practical level.
I also think that this kind of custom tuning is something which would not
be provided in this library level.
Does it answer your question?
On Mon, 1 Jan 2018 at 6:00 AM Noitidart notifications@github.com wrote:

I have two apps that use voice. The first one the users are saying one of
300 items. Is it possible to limit the voice recognition to only return
closest elements to ones in an array?
In another application, the users are saying a single number, or multiple
numbers. Anyyay to limit to just numbers?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/wenkesj/react-native-voice/issues/53, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABQzu2YocwiU78550-EUi9aol5BLPvzqks5tF_XwgaJpZM4RP7uR
.

--

Jeungmin Oh (오정민) | CEO & Founder
HayanMind Inc.

Try Mimiking app on iPhone https://goo.gl/Xrr3yz & Android
https://goo.gl/k77XVW

Darn. Thnks very much for your quick reply. Yes it answers very well, I understand that it makes sense that this library doesnt support it because this feature is paid. If it ever comes out for free it would be awesome if this was available. Thanks for leaving this open for me to close.

@Noitidart For your information, for the paid services, you can even add more words on your own. For example, usually proper nouns like a person's name or brand name. I would love to help support those features if the default speech recognition library provides those features in the future.

Thank you sir very much for such a positive and optimistic reply! :)

@Noitidart Did you solved your problem?

authors: Noitidart lfoliveir4 ohtangza

repo: wenkesj/react-native-voice


text:
Find a way to improve error messages for errors in yaml

(<unknown>): did not find expected key while parsing a block mapping at line 19 column 9

Related to linting: https://github.com/flant/werf/issues/2204
Related to golang yaml library: https://github.com/go-yaml/yaml/releases

outdated

authors: alexey-igrychev distorhead

repo: werf/werf


text:
chore: release 1.2.227

:robot: I have created a release *beep* *boop*
1.2.227 (2023-04-26)
Bug Fixes

stapel/imports: processing of includePaths/excludePaths with globs in file/directory name (7046ca7)
update ruby gems (e51e7b6)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/werf/werf/releases/tag/v1.2.227 :sunflower:


text:
Adding Potluck Submission btn

For #71 .
Desktop

Mweb

Hover state:

Let me know if you want me to squish my commits

this looks great! thank you :)

repo: wesbos/Syntax


text:
Bug: 公開範囲を選択するとエラーが発生する

Environment
Host

item
version

OS
CentOS 7.9.2009

GROWI
4.2.15

node.js
14.16.1

npm
6.14.12

Using Docker
yes

Using growi-docker-compose
yes

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

item
version

OS
Windows10

browser
Google Chrome 89.0.4389.128

How to reproduce? (再現手順)

任意のページを新規作成、または編集する
公開範囲で「特定のグループのみ」を選択する

What happens? (症状)

下記のエラーが発生します

Error occured in t
TypeError: this._mountContainer.removeChild is not a function

詳細
    in t
    in Ms
    in n
    in t
    in ForwardRef
    in withI18nextTranslation(Unknown)
    in div
    in div
    in Is
    in n
    in t
    in ForwardRef
    in withI18nextTranslation(Unknown)
    in form
    in div
    in div
    in Fs
    in n
    in t
    in ForwardRef
    in qs
    in n
    in t
    in ForwardRef
    in t
    in n
    in p
    in i
    in B

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

正常に指定できる

Note

デモ版でも再現しました。

@hide-o-mvd ご報告ありがとうございます。修正完了しました。v4.2.16 リリースをお待ちください。

authors: hide-o-mvd yuki-takei

repo: weseek/growi


text:
Imprv/options selector restyle

やったこと

options selectorのスタイルを新デザインにした

懸念点

コーディングのポリシーを100%キャッチアップできていないので、書く場所/書き方が合っているか不安
btn-outline-secondaryのクラスのスタイルを上書きしたので、他の箇所にも影響がある。

スコープ外なので、ここだけに影響するようにすべきか
いや、しかし最終的にはbtn-outline-secondary全てはこのスタイルにしたいのが、デザイナーとしてのの要望

XD

https://xd.adobe.com/view/e529ceaa-c408-4561-97c7-ba52cee9791b-b07a/screen/487d7250-5b76-422a-9bc2-7a1f38cd75e8/specs/

以下、レビュー依頼出す前に毎回やってください。今この PR はレビューできない状態です。

Files changed タブを split view で確認
自分が加えた変更以外の差分が出ていないことを確認

scss の修正が多いのでなんとなくダメそう(という感想)

いや、しかし最終的にはbtn-outline-secondary全てはこのスタイルにしたいのが、デザイナーとしてのの要望

をやるときに今回の編集がゴミになっちゃうのはなんかいやなので、やるならそこまでやってほしい。
そして scss は1行でも少なく、!important は極力使わない。

最終的にはbtn-outline-secondary全てはこのスタイルにしたい
から拡張して、「最終的にはbtn-outline-#{$color}はこれにしたい」というモチベーションで変更を加えました。
（スコープは拡大してしまったが、各行数も変わらないと思ったので）

変更後の見た目

hover時/クリック時の見た目が変わってます
primary

secondary

FB対応しました。
やったこと

要らないコメントアウトを削除
!important を使わない記述に変更
.btn-outline-#{$color}  ... の記述を scss/theme/_reboot_bootstrap-theme-colors.scssに移動

Light時のみ当てはめたいスタイルが、Darkに当てはまっていたので、記述箇所変更しました

authors: shukmos yuki-takei


text:
How to add HTTPS support

Hi team,
I followed the install steps from https://github.com/weserv/images/blob/5.x/docker/README.md
and install via docker worked like a charm.
However, I can only access it via http.
Could you please explain to a noobie how to add such support ?
I use Ubuntu 20.04 TLS, with OpenLiteSpeed.

Duplicate of #116

authors: hycday kleisauke

repo: weserv/images


text:
Update sbt-ci-release to 1.6.1

About this PR
📦 Updates com.github.sbt:sbt-ci-release from 1.5.10 to 1.6.1
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.sbt", artifactId = "sbt-ci-release" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.github.sbt", artifactId = "sbt-ci-release" }
}]

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

Superseded by #284.

repo: weso/utils


text:
Russian language support (encoding issue)

Russian language is not working properly in chat, probably encoding issue.

I uploaded a new version which converts all message strings to the utf-8 format, that should fix it.
Since i don't speak/write russian, please let me know if you can find more problems.

Still the same in 1.7.3.0

Hm, if i set my windows keyboard locale to russian it works fine for me.

I'll search for another solution.

I uploaded an update, it should display the characters right now. I did a quick test with a russian stream and it seems like it works. The text currently does not look the same as before, but i put that in later.

The issue is still there, can it be on client side only?

That is weird. It was working for me yesterday and today it doesn't. I'll have another look.

Sorry for the long wait, but i wasn't feeling too well recently.
I may have finally found a solution. I added a java parameter to set the encoding to utf8 which should work. Problem is only the .exe version has it built in, so if you are using the .jar version you should use a
shortcut that looks like this "java -Dfile.encoding="UTF-8" -jar livestreamergui.jar".

Hey, dude, no problem. I hope you do well now. Get better anyway.
Your fix is working perfectly.

authors: biozz westerwave


text:
Eighth pass at instr. for voterGuidePossibilityHighlightsRetrieve

I found my problem.  retrieve_candidates_from_non_unique_identifiers takes two seconds to execute, and it gets called 14 times for a page with 14 possible highlights.   The function does un-indexed searches on 12 text fields over 76,000 records.  I could try indexing all of those fields, and see if it improves.  Indexes take some CPU to maintain, but we probably add candidates pretty rarely.  First I am going to run explains and see more detail.

👍  Great catch!

authors: DaleMcGrew SailingSteve

repo: wevote/WeVoteServer


text:
automatic setClickable / jQuery Mobile info

This is not an issue, maybe a tiny contribution to the docs.
Regarding the setClickable feature and JQM panels, maybe it would be good to add in the documentation that this can be automatically achievable using:
	$(panelSelector).on("panelbeforeopen",function(){
		map.setClickable( false );
	});
	$(panelSelector).on("panelbeforeclose",function(){
		map.setClickable( true );
	});

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/9495433-automatic-setclickable?utm_campaign=plugin&utm_content=tracker%2F637500&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F637500&utm_medium=issues&utm_source=github).

Thanks, I've changed the title and closed the issue, so it will be still searchable for those who search for it.

authors: Hirbod siran


text:
alert duration not working

        <alert  placement="top" duration="3000" type="danger" width="400px"  dismissable  v-if="error" >

            Warning

{{ error }}

        </alert>

The alert will show but the duration seems not working. Anything else needs to be set?
Thanks.

I find the reason, its the v-if reason. Not the source problem.

repo: wffranco/vue-strap


text:
🛑 Mumble (JP) is down

In 1a6437a, Mumble (JP) (jp.mumble.winterco.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Mumble (JP) is back up in 3108046 after 2 hours, 21 minutes.

repo: wfjsw/status-winterco-org


text:
Shorten target mount timeout

We currently wait for an hour for a target to mount which may be a bit excessive.
Instead wait for 10 minutes.

Codecov Report

Merging #956 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #956   +/-   ##
=======================================
  Coverage   95.42%   95.42%
=======================================
  Files           2        2
  Lines         153      153
=======================================
  Hits          146      146
  Misses          7        7

Continue to review full report at Codecov.

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

authors: codecov-io jgrund

repo: whamcloud/integrated-manager-for-lustre


text:
ライセンス情報の表示を追加

対応内容
https://www.keisuke69.net/entry/2021/06/30/081709

https://www.keisuke69.net/entry/2021/06/30/195328

repo: wheatandcat/memoir


text:
Create LinearSearch.java

LinearSearch in Java.

LinearSearch in Java.


text:
feat: access resolvers

Add abstract access resolver + refactor existing
Also fixes #35

tas ir BC, pareizi un sanāk izlaist 0.22? To vajadzētu skaidri afišēt, jo sanāk Raitim būs jāvelta laiks, lai saprastu + pielāgotu Vegu (Valtek vēl šis nav ieviests, tāpēc būs vieglāk).
Viena lieta ir tā, ka turpmāk notiks pārbaude, vai visām lomām ir norādīts tiesību līmenis. Tas savukārt prasīs izveidot configu un norādīt lomu enumu. Tas jau ir PR pats par sevi.
AbstractResolver - tāds iepriekš nebija, vajadzētu paskaidrojumu, kas un kā. Piemēram nesaprotu, kāpēc tur metode "isOwnerPropertyNested" - jo OWNER jēdziens turpmāk ir tikai viens no daudziem veidiem, kā limitēt piekļuvi resursiem. Tikpat labi, var būt loma, kura var piekļūt resursam 5dienās no rīta, bez nekāda sakara ar owner. Šeit varbūt es ko palaidu garām, jo @Raitis Rasmanis taisīja AcessResolvers - viņš arī varētu šo PR nokomentēt.
Jaunais config nav iekļauts README.md

repo: whitedigital-eu/entity-resource-mapper