Cannot set geckodriver in code

I'm sure I had this working when I submitted that pull request to update the docs. I've just come back to it after many weeks and now I can't get it to work.
This does work:
java -Dwebdriver.gecko.driver="/home/me/Downloads/geckodriver" \
  -jar ~/Downloads/selenium-server-standalone-3.0.1.jar

with
caps := selenium.Capabilities{
		"browserName":            "firefox",
}

This does not work:
java -jar ~/Downloads/selenium-server-standalone-3.0.1.jar

with
caps := selenium.Capabilities{
		"browserName":            "firefox",
		"webdriver.gecko.driver": "/home/me/Downloads/geckodriver",
}

It gives error:
The path to the driver executable must be set by the webdriver.gecko.driver \
system property; for more information, see https://github.com/mozilla/geckodriver. \
The latest version can be downloaded from https://github.com/mozilla/geckodriver/releases

Thanks for reporting. It's been a while sine I've used Selenium and not that familiar with Selenium 3 to solve this one. Maybe others can help? (@crantok?)

I think this issue and #41 may be related.
I enabled debug logging
	selenium.SetDebug(true)

and added pretty printing of JSON responses (see my pull request #44) to make reading the logs easier.
I tried adding the proxy settings used in #41
    proxy := selenium.Proxy{
        Type:  "manual",
        SOCKS: "<IP_ADDRESS>:1080",
    }

    caps := selenium.Capabilities{
        "browserName": "firefox",
        "proxy":       proxy,
    }

and that silently failed. The JSON response from creating a new session does not include the proxy settings, nor is any error reoprted:
2016/11/18 15:12:30 <- 200 OK [[application/json; charset=utf-8]]
{
    "state": null,
    "sessionId": "b0e31871-eecf-4047-837d-ffce9f4fdadd",
    "hCode":<PHONE_NUMBER>,
    "value": {
        "rotatable": false,
        "raisesAccessibilityExceptions": false,
        "firefoxOptions": {
            "args": [],
            "profile": "..."
        },
        "appBuildId": "20160920074044",
        "version": "49.0",
        "platform": "LINUX",

                             // <--- No Proxy Details!
        "proxy": {},         // <--- No Proxy Details!
                             // <--- No Proxy Details!

        "command_id": 1,
        "specificationLevel": 0,
        "acceptSslCerts": false,
        "processId": 18649,
        "webdriver.remote.sessionid": "b0e31871-eecf-4047-837d-ffce9f4fdadd",
        "browserVersion": "49.0",
        "platformVersion": "4.4.0-38-generic",
        "XULappId": "{ec8030f7-c20a-464f-9b0e-13a3a9e97384}",
        "browserName": "firefox",
        "takesScreenshot": true,
        "takesElementScreenshot": true,
        "javascriptEnabled": true,
        "platformName": "linux",
        "device": "desktop",
        "cssSelectorsEnabled": true
    },
    "class": "org.openqa.selenium.remote.Response",
    "status": 0
}

Unfortunately, when I initialise the use of the geckodriver by passing its path directly to the selenium jar (see OP) I do not see "webdriver.gecko.driver" in the keys of the JSON response :-/

Selenium Server does not support specifying the geckodriver exe location in capabilities. It must either be in a location pointed by the PATH or specified through the JVM system property webdriver.gecko.driver (e.g. by using java -Dwebdriver.gecko.driver=... --jar selenium-server-standalone.jar).

@DrMarcII is correct, of course.
The above commit adds support for specifying the path to Geckodriver when using the provided Service type, which was recently added.


Revert "[QoI] Cleanup AST after trying to shrink constraint system of invalid expression"

Reverts apple/swift#6780

@swift-ci Please smoke test and merge

When reverting a PR can you include a description of why it is being reverted?


login with challenge using Spring Boot

I use Spring Boot and I am trying to log in and perform the instagram challenge in order to get the number of followers from the user, but when I ask for the security code an Exception is thrown.

it is my problem to.

Addressed in rewrite or no longer relevant.


OpenFL install times out even with -notimeout

I'm trying to install OpenFL via terminal on OS X El Capitan. Regardless of whether I run haxelib install openfl or haxelib -notimeout install openfl I get the same error:
Downloading openfl-3,6,0.zip...
Download complete : 0 bytes in 10s (0KB/s)
Http connection timeout. Try running haxelib -notimeout <command> to disable timeout

After taking a look at issue #153, I downloaded openfl-3,6,0.zip from here and unzipped the file to the .current folder like issue #153 suggested:
unzip ~/Downloads/haxe/openfl-3,6,0.zip -d /usr/local/lib/haxelib/openfl/.current

It unzipped without any errors, and I also copied the contents of .current into another folder 3,6,0 in my /usr/local/lib/haxelib/openfl directory
cp -a .current/ 3,6,0

But when I ran haxelib run openfl setup, I got the following response:
[file_contents,/usr/local/lib/haxelib/openfl//.current]

I have no idea why this might be. The command haxelib path openfl gives me the following response:
[file_contents,/usr/local/lib/haxelib/openfl/.current]

In any case, running the openfl command gives me the error:
zsh: command not found: openfl

What might I be doing wrong?

.current should be a file.
Delete the openfl directory and do haxelib install openfl-3,6,0.zip.

Thanks, doing that fixed my problem! I ended up following the manual installation instructions to get everything set up.


Make sure that all compatible examples can be launched

For now we block "launch" on some example because they may fail on the target cluster. We need to make sure it is the case to so we don't miss any example for a wrong reason.

From @ALRubinger :

Allow Istio stuff to show up in local for Launch
Explicitly designate that these examples require Istio support enabled in that cluster
It's just about setting expectations for users and avoiding failures where success is expected

So I'd say we should just show them (they will only show up for people running Minishift anyway, so they are already using a non-trivial setup so we can expect them to be somewhat more knowledgeable) with some kind of "Needs ISTIO configured on target cluster" warning.

The missions are already tagged with istio: true so it should be easy to display that warning: https://github.com/fabric8-launcher/launcher-booster-catalog/blob/master/metadata.yaml#L62

A better solution might be that clusters that have ISTIO installed are marked that way, but of course that would mean manually maintaining that flag in the cluster list.
An even better way would be to detect ISTIO being installed on the cluster, but who knows if that's even possible.

releated to: #1054

I guess it's fixed


runtime: some Go executables broken with macOS 10.12.4 / Xcode 8.3 but fine with Xcode 8.2

See https://github.com/couchbase/sync_gateway/issues/2417 for repro steps.
System:
MacBook Pro (x86_64)
macOS 10.12.3 (Sierra)
go version go1.8 darwin/amd64
Xcode 8.3;  clang -v
Apple LLVM version 8.1.0 (clang-802.0.38)
Target: x86_64-apple-darwin16.4.0
Thread model: posix
What did you do?
See description at
https://github.com/couchbase/sync_gateway/issues/2417
I also found this with some code I am unable to share.
My code does work fine with Xcode 8.2:
clang -v
Apple LLVM version 8.0.0 (clang-8<IP_ADDRESS>)
Target: x86_64-apple-darwin16.4.0
Thread model: posix
and from reading the bug linked above it works fine there as well.

I have the same problem as OP but only for some binaries, not all. When trying to start, it is killed instantly.
$ ./test
Killed: 9

I can't figure out the common pattern for broken programs.

Reproduction:
package main

import (
	"fmt"

	_ "github.com/veandco/go-sdl2/sdl"
)

func init() {
	fmt.Println("init")
}

func main() {
	fmt.Println("Hello, world")
}

 $ ./testx
 fish: './testx' terminated by signal SIGKILL (Forced quit)

Basically, just using cgo and linking against sdl2 causes the crash:
package sdl

// #cgo linux freebsd darwin pkg-config: sdl2
import "C"

If you make the above file the whole go-sdl package, the binary will still crash.

Uhm it looks like lldb is even unable to spawn the binary:
(lldb) run
error: error: ::posix_spawnp ( pid => 24893, path = '/Users/rasky/Sources/go/src/ndsemu/testx/testx', file_actions = 0x7fff555225e8, attr = 0x7fff555225f8, argv = 0x7fd1e92a8150, envp = 0x7fd1e92ad520 ) err = Cannot allocate memory (0x0000000c)

so it seems like the binary is being linked in a way that the OS refuses to run it.
/cc @ianlancetaylor

just the same, cgo make it crash

same here but with github.com/shirou/gopsutil/cpu instead of sdl2.
trying to run the binary with dtruss gives Unknown error.

I'll notice that all Go binaries (including working ones) generate the -67062 error, but I think that's normal because they are not codesigned. The errors I get only when running these crashing cgo binaries is:
default	14:32:47.099750 +0200	taskgated	UNIX error exception: 3
default	14:32:47.099853 +0200	taskgated	no signature for pid=28180 (cannot make code: UNIX[No such process])

@rasky
On my environment (MacOS 10.12.14, Xcode8.3), non-cgo go programs do not generate -67062 errors. In my tests I performed, this error was strictly correlated to (1) crashes with the "signal: killed" message (2) cgo programs.
Additionally, I also get the "UNIX error exception: 3" message in the system logs

getting signal: killed when trying to use go run *.go
go build works, but then i get "Killed: 9" when I try to run the app

same here, dowloaded Xcode 8.2.1, replaced in /Applications and it works again..

For everyone running into this issue, I've been able to build binaries by adding -ldflags -s during the go build phase.

By default on Darwin the linker will invoke dsymutil to put the debug info directly into the executable.  This invocation of dsymutil is disabled by the linker's -s option.  Perhaps this is really a bug in dsymutil, or in how dsymutil deals with files created by the Go linker.  Could somebody with an affected system please try modifying the code in Link.hostlink in cmd/link/internal/ld/lib.go to skip invoking dsymutil, and see if that fixes the problem?  Thanks.

@ianlancetaylor it does.

The call to dsymutil was added to fix #8973.  I suppose the next question is: if we don't call dsymutil, what happens when you try to debug a Go program built with cgo?

I'm seeing this without using cgo, what's the suggested work around - use xcode 8.2?

@cosnicolaou, see above (https://github.com/golang/go/issues/19734#issuecomment-289822644). Does that not work for you?

thanks, it works, from reading the comments I thought this was a cgo only problem/fix. It's also painful for our build/automation for obvious reasons.

would adding these flags to build scripts have any negative repercussions that you're aware of? performance implications or anything like that?

no, it's just a pain to find all of the invocations etc.

agreed :) thanks for verifying they are safe to add though

oh, and all of our reg tests that build go programs also have to changed to work with this... that's a lot of code for us. When do you expect to have a 'transparent' fix done/out? Thanks.

I don't have a Mac.  I'm waiting for an answer to my question about #8973.

I've never used gdb/lldb on a Go program, so it's hard for me to spot patterns that are different from "usual". Is there some specific test that you would like to be performed (e.g.: specific things that you want us to check whether they work or not after dsymutil is taken out), or is it a really a generic question and it requires someone familiar with the matter that can do some sessions and find out if there's something wrong?

It's really a generic question, thanks.

I haven't tested it thoroughly yet but stripping a cgo binary also seems to work.

For building binaries, https://github.com/golang/go/issues/19734#issuecomment-289822644 is the way to go.

I suppose the next question is: if we don't call dsymutil, what happens when you try to debug a Go program built with cgo?

@ianlancetaylor, using which debugger?

@shurcooL I have no idea.  I don't use MacOS.  I'm just trying to help people connect the dots from #8973 to this problem, and trying to understand whether we can just stop calling dsymutil or whether that will cause #8973 to reappear.  #8973 mentions both gdb and lldb.

@ianlancetaylor Built 1.8 from source, commenting out the dsymutil section, ran gdb on a simple program that uses cgo, got this:
Reading symbols from $HOME/go/simple...
warning: `/var/folders/84/p363xh452_b1_f909jm5yw780000gn/T/go-build096684628/runtime/cgo/_obj/gcc_amd64.o': can't open to read symbols: No such file or directory.

warning: `/var/folders/84/p363xh452_b1_f909jm5yw780000gn/T/go-build096684628/runtime/cgo/_obj/gcc_context.o': can't open to read symbols: No such file or directory.

warning: `/var/folders/84/p363xh452_b1_f909jm5yw780000gn/T/go-build096684628/runtime/cgo/_obj/gcc_darwin_amd64.o': can't open to read symbols: No such file or directory.

warning: `/var/folders/84/p363xh452_b1_f909jm5yw780000gn/T/go-build096684628/runtime/cgo/_obj/gcc_libinit.o': can't open to read symbols: No such file or directory.

warning: `/var/folders/84/p363xh452_b1_f909jm5yw780000gn/T/go-build096684628/runtime/cgo/_obj/gcc_setenv.o': can't open to read symbols: No such file or directory.

warning: `/var/folders/84/p363xh452_b1_f909jm5yw780000gn/T/go-build096684628/runtime/cgo/_obj/gcc_util.o': can't open to read symbols: No such file or directory.

warning: `/var/folders/84/p363xh452_b1_f909jm5yw780000gn/T/go-build185537422/mypackage/_obj/_cgo_export.o': can't open to read symbols: No such file or directory.

warning: `/var/folders/84/p363xh452_b1_f909jm5yw780000gn/T/go-build185537422/mypackage/_obj/mypackage.cgo2.o': can't open to read symbols: No such file or directory.

warning: `/var/folders/84/p363xh452_b1_f909jm5yw780000gn/T/go-link-879290217/go.o': can't open to read symbols: No such file or directory.
(no debugging symbols found)...done.

 So consider this reproduced. I'll try to figure it out, since I can't get any work done anymore.

CL 38747 should fix the problem (by not using dsymutil's output), and we'll get that backported into Go 1.8.1. Until then use -ldflags=-s as the workaround.
I filed #19772 to track a non-workaround fix. If that ends up being very simple we might consider it for a backport, but I'm not holding my breath.

in case anyone else ran into this, the go install -ldflags -s doesn't work. You have to go build -ldflags -s and then run that binary.

If anyone has a working Xcode 8.2 system, can you please run
cd go/src/runtime/testdata/testprogcgo
go build

and then post the 'testprogcgo' binary that is built? Here is fine if you can get Github to accept it; anywhere else is fine too. Thanks.

@rsc, testprogcgo.gz

Be the bot you want to see in the world.

I used https://developer.apple.com/download/more/?name=Xcode to download and install Command line tools 8.2 as work around. Remove /Library/Developer/CommandLineTools before installing.

For any gb users who stumble on this, you can apply the same fix from the comment above, except I need to add in the equal sign:
gb test -ldflags=-s

Thank you for the workaround. I was totally stuck until I looked in my update log and noticed XCode had updated yesterday.
Kill signal 9

thanks god ..

I was able to get around this while keeping the latest Xcode installed.  Download Xcode 8.2 from Apple and unpack it if your browser hasn't already.  Rename the extracted bundle, I renamed it to Xcode8.2 then copy it over to /Applications.  From a terminal use xcode-select to set 8.2 as toolchain to use.
sudo xcode-select --switch  /Applications/Xcode8.2.app/

@nicksnyder go install -ldflags -s does work for me but only if I delete the binary in my bin folder first.

@jekriske-lilly That's right, go install doesn't include the gcflags or ldflags when deciding something is out of date. We're planning to change that at some point, but for now that's how it is.

Cherry-picked.

I ran into this problem as well. Simply deleting Xcode 8.3 and replacing it with Xcode 8.2.1 did not downgrade the CommandLineTools. I needed to first remove /Library/Developer/CommandLineTools before installing Xcode 8.2.1. Another (probably better) option is to remove only /Library/Developer/CommandLineTools and download only the 8.2.1 CommandLineTools. See comment by @l0n3r4n83r above. Here is the link again: https://developer.apple.com/download/more/?name=Xcode

Apologies for the commit spam in this thread, I forgot GitHub would do that 😓. Are there any plans to backport the fix beyond 1.8? I can seem to reproduce this using this test code right back to at least 1.5.

At present there are no plans to make any more releases of anything earlier than 1.8.  We'll have to see how it goes.

There are no plans to backport this to Go 1.7 or earlier. Per https://golang.org/doc/devel/release.html#policy, Go 1.7 is no longer supported, since Go 1.8 is released.
If you must still use Go 1.7, the workaround is to compile with -ldflags=-s or to sudo ln -s /usr/bin/true /usr/local/bin/dsymutil, assuming /usr/local/bin is ahead of /usr/bin on your $PATH.

@rsc, I thought in #19069 we decided to support the past two releases. Isn't that what your 86abfbb931312db022ed8437a89219791ced6435 says?

Well, as one datapoint, Kubernetes still hasn't moved from Go 1.7 to Go 1.8, so this means you can't run Kubernetes (even Kubernetes 1.6) on a Mac now.

Er, build, not run. Maybe that's okay.

Right, build, and even then only build with newer Xcode. It's not like the gettimeofday crashes.

This may impact their point release builds, but I'm not sure how Kubernetes does their releases (on an actual Mac, or cross-compiled).
Running file on https://storage.googleapis.com/kubernetes-release/release/v1.6.1/bin/darwin/amd64/kubectl just says kubectl: Mach-O 64-bit executable x86_64.

They can always add -ldflags=-s or update to Go 1.8.1 like everyone else. Also, kubectl at least doesn't appear to have any cgo code in it (otool -l kubectl | grep nundefsym).

Yeah, kubectl seems to be cross compiled (it doesn't use the macOS DNS resolver).

none of the above workarounds worked for me :(

Update to Go 1.8.1, it is fixed now.

Go 1.8.1 Works! 🎉

use  go1.8.1 fixed it  good


feat: show publish date on --verbose

Show publish dates and latest when using --verbose
Bold headers
Dim plugin info

Before

After

Fixes #419
@W-15664257@

QA:
sf plugins link this into sf
✅ it's clear my CLI is not latest
✅ a very old user plugin shows that it was public 942 days ago. 😄
📓 @salesforce/cli/2.41.4 published 13 days ago (Tue Apr 23 2024) (latest is 2.39.6)
I think I'm ok with this being red?  I'm usually on nightly but most people probably aren't.
❓ how do you feel about this PR changing the --json output?
[downgrade to stable, user-install plugin-org to yesterday's release]
✅ warnings
✅ no warning here org 4.1.8 (user) published 1 days ago (Mon May 06 2024)
[switch to an older plugin-org]
❌   org 4.0.1 (user) published 1 days ago (Mon May 06 2024) (latest is 4.1.8) <-- that's the wrong date for that version
[uninstall plugin-org and install via sf plugins install https://github.com/salesforcecli/plugin-org]
✅ in this case, pjson version on main is correct because that's latest?
[uninstall plugin-org and install via sf plugins install https://github.com/salesforcecli/plugin-org#341c60ac3514c436aa8a1fd7431703e622c88ae4]
❌ org 3.5.1 (user) published 1 days ago (Mon May 06 2024) (latest is 4.1.8) that's definitely a wrong datestamp for when that version happened.
❓ if oclif officially supports "install from gh" should those appear different in sf plugins or sf version.

❓ how do you feel about this PR changing the --json output?

I suspect that few people are depending on the json output here, especially since it's not easy to work with (It's just the human readable output put into a json array). If you think we should major version, then I'd recommend switching to a more usable json output, e.g. {name: org, type: user, version: 3.5.1} instead of org 3.5.1 (user).

❓ if oclif officially supports "install from gh" should those appear different in sf plugins or sf version.

I could go either way but I'm leaning towards waiting until someone asks for it

QA notes:
✅  dates are correct now for npm and gh based installs


Any plan to evaluation code？

Thank you very much for your exciting work. Do you have any plan to release evaluation code corresponding to Table 2?

No problem. I will clean and share the evaluation code later (probably after the CVPR conference week).
Our results are obtained on the whole nuScenes validation set, which includes 5369 samples in total. The evaluation code for FID uses FrechetInceptionDistance module of torchmetrics, and the evaluation code for FVD is modified from LVDM. Hope these are helpful if you want to evaluate on your own before our release.

Thank you very much for your helpful reply, looking forward to your further updates.

Hi @ABaldrati, thanks for your interest.

Could you please clarify if you employed any form of action control when generating the videos, or if you used just the pre-trained video model without any action control?

The results in Table 2 are evaluated in action-free mode.

Additionally, could you share any tips or common pitfalls to watch out for that might affect the replication of the results in this table?

There is nothing special about our evaluation. Just make sure you evaluate on all samples from the nuScenes validation set, which may take days with a single GPU.

Hi @Little-Podi,
Thank you immensely for your availability and prompt response!
Before I start running the inference (as it takes quite some time), I just want to ensure that all the hyperparameters are set correctly. Specifically:

--n_rounds = 1
--n_frames = 25
--n_conds = 3? The default value in the sample.py script is 1, but I believe you used 3, correct? Please correct me if I'm wrong.
--cfg_scale = 2.5

I apologize for any inconvenience, but I want to be absolutely certain everything is set correctly.
Thank you again for your help!

Exactly, but I think I used --n_conds = 1 for evaluation. Using --n_conds = 3 may yield similar or better results, just like the effect of using ground truth action controls. You can also disable --rand_gen to automatically go through all validation samples. Besides, remember to take all predicted frames into account during the evaluation.

Thanks so much for your quick response and for your availability. I really appreciate you making the code open-source and releasing the weights.
Thanks again for your help!

No worries, feel free to contact us if you have any further questions.

Hi @Little-Podi,
First of all, thank you very much for your support.
I've successfully generated all the videos for the nuScenes validation set and can replicate the FID numbers reported in Table 2, achieving even slightly lower numbers. However, I'm having difficulty replicating the FVD numbers. Could you please provide more details on the specific parameters you used for computing the FVD? For instance, the resolution, number of frames, resizing strategy, and any other relevant details would be extremely helpful.
Thank you again for your help!

Hi @ABaldrati, thanks for your feedback. Sorry for the late reply. I have returned from CVPR, but I still have lots of things to deal with in the following days.

Could you please provide more details on the specific parameters you used for computing the FVD?

All 25 frames in each clip are used for calculating FVD. I just checked our evaluation script. The frame resolution is resized to (256, 448) when loading the generated images, and is eventually resized to (224, 224) before sending to the I3D model. I don't remember why we conduct resizing twice, but I will check it.

I'm having difficulty replicating the FVD numbers.

May I ask what are the FID and FVD scores you got? In fact, we continue to tune the checkpoint for a few iterations under the setting of phase2_stage2 before its release. I didn't retest it in terms of metrics, but I think it should be close. I will verify later to decide if it is necessary to provide the older checkpoint. Based on the few samples I have seen, I think the current checkpoint is better from the perceptual perspective.

Hi @Little-Podi,
Thank you for your response!
Could you please clarify if the resizing from (256, 448) to (224, 224) is done using non-proportional resizing or a center crop?
For reference, I obtained a FID score of 6.7, which is very close to the 6.9 reported in the paper, indicating that our results are comparable. However, my FVD score is 139, which is significantly different, leading me to believe there might be an issue with my evaluation script.
Thank again!

Could you please clarify if the resizing from (256, 448) to (224, 224) is done using non-proportional resizing or a center crop?

Oh, now I know why we conduct the resizing separately. We did center cropping before resizing from (576, 1024) to (256, 448) via the Pillow package. We didn't use cropping when resizing from (256, 448) to (224, 224) via F.interpolate. Did you evaluate on all 5369 video clips? The FVD score seems to be too high. I will retest the checkpoint and also provide the evaluation code later.

Hi @Little-Podi,
Thank you for the clarification.
I’m a bit confused about the center cropping before resizing from (576, 1024) to (256, 448) since the proportions seem to be maintained in this step. Could you please provide a brief step-by-step description of each resizing step?
Yes, I have evaluated on all 5369 video clips.
Thank you for your assistance!

I’m a bit confused about the center cropping before resizing from (576, 1024) to (256, 448) since the proportions seem to be maintained in this step. Could you please provide a brief step-by-step description of each resizing step?

The aspect ratios are almost the same, but some pixels will leak without center cropping. The implementation is identical to our data preprocessing here.

Hi @Little-Podi,
Thank you for your availability and the detailed information.
Despite following the provided details, I still can't replicate the FVD results. I'll wait for the release of the evaluation code.
Thanks again, and great work on the project!


Some memory initialization option proposals

https://github.com/freechipsproject/treadle/blob/1c67bc846aafc3bdd707f76ead8cefd5f93e0376/src/main/scala/treadle/executable/Memory.scala#L618-L663

One may provide the memory initial data directly from Scala data structures. It might be useful to provide LoadMemoryAnnotation from Seq[BigInt]. With this option, one can write any load memory annotations, for example elf loader, bin loader.

Some Memories may have a type of Vec(n, UInt()), that would make a Vec of memory instances. The row line needs be devided to n slices and load each of the memroy instances. If item 1 in place, one can split the file contents to n slices and load to each memory instances.

Treadle shellOptions could generate the LoadMemoryAnnotation. With the above features, the users can write their own shell options for their projects. For example:
--init-memory circuit.module.component:8x4 --hexfile file.

I can provide a user level example for item 3 if item 1,2 are in place.

Treadle can probably reuse the MemoryInitAnnotation once it is merged in firrtl: https://github.com/freechipsproject/firrtl/pull/1645

checkout https://github.com/freechipsproject/treadle/pull/220


Discussion for Transform.IDENTITY

This is not a major issue, but I find the static IDENTITY field of the Transform class somewhat 'ugly'. I know Java does not have a good mechanism to make immutable objects of mutable classes, but there are probably more ways to approach this. This also (in theory) has some performance implications because when this overridden Transform field is used the call sites with Transform arguments will see a 'new type of transform object' (i.e. JVM is quite good to optimize monomorphic  method calls). So I want to discuss the possibilities:

Remove the Transform.IDENTITY field and add private IDENTITY constants to the (2-3) classes that use this internally. Users can have their own version of this constant since it's construction is trivial (new Transform()). This was my initial test and I actually have a old-ish spare implementation of it minor_tranform branch as a sample implementation
Keep the Transform.IDENTITY field but do not override any methods (i.e. public static final Transform IDENTITY = new Transform();) alongside with a note to the user, as in the Vector2 class ...this vector should not be changed at runtime; used internally...
Do nothing and keep current implementation

In my opinion:

1 is quite feasible; On the user side it should be very easy to refactor the code to use a personal Transform constant (or at least certainly easier that what required by the future of #47)
2 is easy to implement but can lead to some nasty bugs in rare scenarios. I would personally avoid such implementation
3 is totally feasible but bad for my aesthetics :grin:

Agreed, it's ugly.  I'd prefer the 1st option.

Was thinking about something - how do you feel about leaving a public static final Transform IDENTITY = new Transform(); in the Transform class with a @Deprecated attribute on it for compatibility?

Yeah, this sounds even better. I don't even know if it should be marked as deprecated actually.
Since now internally dyn4j uses it's own private instances that cannot be mutated by the user, maybe we can have this public static final Transform IDENTITY = new Transform(); field in the Transform class for uses in user code.
Do you think it should be deprecated, or not?

Ok, how about this - we don't deprecate it but we reiterate the fact that all Transform instances are mutable?  I think if I had my choice I would just deprecate it.

Well, my initial problem was to let it be mutable because it was used internally in dyn4j. So something bad could happen to it and then simple methods that e.g. take no arguments could result to something wrong; this is a hard bug to find.
But since now the field isn't used internally (all classes have a private constant), the worse thing that can happen is only in the user side. My point is: In this case it wouldn't make any difference if the field was declared in user code or in the Transform class (So why not have it there for convinience?).
Just so I can understand the reason better: Do you want to deprecate the field and remove it in the future, or deprecate it and just leave it like that?

I’m not sure.  My original thought was that keeping the public static field would imply immutability and a slightly selfish desire to not have bug reports from users that are hard to troubleshoot.  So I was thinking leave it in, mark it deprecated with a message that explains why, then remove later down the road.
So my thought was more around perception, which we could probably solve with comments too.

Alright, fine with me. Then let's have it like that.
Add the field back as a simple transform instance, deprecate it for removal with corresponding javadoc explanation then remove in future release.

I've added it back with deprecated markers.


SENDING MESSAGE. ERROR 500 - HELP! :(

Hi, I hace an issue. I got an error when I'm trying to send a message, like thiS:
{
"statusCode": 500,
"timestamp": "2023-09-07T09:29:32.339Z",
"exception": {
"stack": "Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'WidFactory')\n    at puppeteer_evaluation_script:2:42\n    at ExecutionContext._evaluateInternal (/app/node_modules/whatsapp-web.js/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:221:19)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async ExecutionContext.evaluate (/app/node_modules/whatsapp-web.js/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:110:16)\n    at async Client.sendMessage (/app/node_modules/whatsapp-web.js/src/Client.js:869:28)\n    at async /app/node_modules/@nestjs/core/router/router-execution-context.js:46:28\n    at async /app/node_modules/@nestjs/core/router/router-proxy.js:9:17",
"message": "Evaluation failed: TypeError: Cannot read properties of undefined (reading 'WidFactory')\n    at puppeteer_evaluation_script:2:42",
"name": "Error"
},
"request": {
"path": "/api/sendText?phone=19285445544&text=hola&session=default",
"method": "GET",
"body": {},
"query": {
"phone": "19285445544",
"text": "hola",
"session": "default"
}
},
"version": {
"version": "2023.9.3",
"tier": "CORE",
"browser": "/usr/bin/chromium"
}
}

We have issue, looking at this.
Subscribe to get notification pls https://github.com/devlikeapro/whatsapp-http-api/issues/200

:warning:
New version 2023.9.7 is out (both core and plus).
If you're experiencing any issues with SCAN_QR state or sending messages doesn't work - please update it, restart containers and try try again!


Update go-autorest to v9.7.0

What this PR does / why we need it:
Update go-autorest to v9.7.0 to address issue #3094 , also good to keep any dependencies as up-to-date as possible.
Which issue this PR fixes: fixes #3094
Special notes for your reviewer:
According the go-autorest's changelog notes on v9.0.0:

IMPORTANT: This release was initially labeled incorrectly as v8.4.0. From the time it was released, it should have been marked v9.0.0 because it contains breaking changes to the MSI packages. We apologize for any inconvenience this causes.

Therefore upgrading from v8.4.0/v9.0.0 to v9.7.0 isn't upgrading across major releases. Also, no breaking changes are indicated in the releases that occurred between these versions.
I manually tested acs-engine generate, deploy, scale and upgrade  to ensure they still run fine.
If applicable:

[ ] documentation
[ ] unit tests
[ ] tested backward compatibility (ie. deploy with previous version, upgrade with this branch)

Release note:

Upgrade go-autorest to v9.7.0

/assign @cecilerobertmichon

FYI @jackfrancis

I see that k8s-linux-default-e2e failed though it seems to have timed out. What's the recommended way to troubleshoot this? Or can I just retrigger the test to see if ti passes?

@gsacavdm this is circle ci being flaky, I just re-triggered the test

k8s-linux-default-e2e passed :)
Not sure what the deal is with the others.
Thoughts @CecileRobertMichon ?

@tariq1890 did you test backwards compatibility? ie. deploy from master, upgrade with your branch

/lgtm

/hold
This PR doesn't actually update vendor/

We'll have to update azure-sdk-for-go as well, the version we're currently pinned to (~v11.0.0-beta) requires go-autorest ~8.4.0. See:
https://github.com/Azure/azure-sdk-for-go/blob/2592daf71ab6b95dcfc7f7437ecc1afb9ddb7360/glide.yaml

@jackfrancis , after making the change locally, I rebuilt ACS engine and confirmed my change did update /vendor and that the AAD endpoint for Azure Government was the newer one (microsoft.com\deviceloginus).

@jackfrancis, as discussed, I updated the azure-sdk-for-go to v12.3.0 which has go-autorest v9.6.0.
I tested acs-engine deploy and confirmed that it uses the right Azure Government AAD endpoint. Deploy failed because the AKS.Linux extension hasn't been published to Azure Government, but outside of that, everything else succeeded and I have a working Kubernetes cluster in Azure Gov.
I'll file a separate issue for the AKS.Linux extension to make that optional.
Can you trigger your tests to see if anything breaks?

@gsacavdm Did you run into any issues w/ the changes described here (from v11 to v12):
https://github.com/Azure/azure-sdk-for-go/releases/tag/v12.0.0-beta
@amanohar @weinong @nicolerenee FYI, this update to go-autorest and azure-sdk-for-go is to protect Fairfax (US Gov) acs-engine use cases against the broken pattern described here:
https://github.com/Azure/acs-engine/issues/3094

Also @gsacavdm FYI I've been rebase/force-pushing to fix some test flakiness, so your local copy will need to be manually re-pulled!

@jackfrancis , I rebased as per your suggestion.
Also, I did look at the release notes, but without looking thoroughly at how acs-engine uses the azure-sdk-for-go, I really can't speculate. My guess is only the first three items have the potential to break things:

Long Running Operations now return a Future type. Go routines and return via channel features have been removed.
Added support for services that make use of polymorphic types.
Operations now make use of the Context Pattern.

It did compile and run without issues (outside of the missing extension issue which is unrelated) I would have expected those three to cause it not to compile at all of they were affecting anything.

@gsacavdm updating go-autorest to v9.10.0 and azure-sdk-for-go to ~v12.4.0-beta to match AKS

Sounds good. What do we need to move this forward. All my tests looked good (I'll retest with your changes but I don't expect issues).


Allow dragging of controls

Would it be possible to modify this condition
if uMsg == WM_LBUTTONUP and control == pLastMouseButtonDownControl
This would allow to trigger a mousebuttonup event on a different control so that a behavior like dragging elements or transference of attributes could be implemented
https://github.com/simonkrauter/NiGui/blob/master/src/nigui/private/windows/platform_impl.nim#L1282

Difficult to say, how to implement drag and drop, I have never tried it.

Hi thank you for your interest I was misunderstanding your code, but I could find the real problem if you return PWndProcResult_True or return PWndProcResult_False at the end of a Mouse ButtonDown message windows will allow a mouseup event to be handled correctly on another control (my problem was that a mouseup event was triggered only on the same control mousedown was triggered)
Example try dragging a button into another button:
import nigui
app.init()
var window = newWindow("Gui")
window.show()
let button = newButton("button")
let button2 = newButton("button2")
let container = newLayoutContainer(Layout_Vertical)
window.add container
container.add button
container.add button2

button.onMouseButtonDown = proc(event: MouseEvent) = echo "mousedown Button"
button2.onMouseButtonDown = proc(event: MouseEvent) = echo "mousedown Button2"
button.onMouseButtonUp = proc(event: MouseEvent) = echo "mouseup Button"
button2.onMouseButtonUp = proc(event: MouseEvent) = echo "mouseup Button2"

app.run()

Then try after adding a return PWndProcResult_False to the end of the WM_LBUTTONDOWN message handling


Python APM agent only sends first HTTP body, rest are [REDACTED]

Using elastic-apm[flask]==5.4.2
Have config item CAPTURE_BODY set to all
Only the first Transaction provides the HTTP Body to APM. All subsequent Transactions are marked as [REDACTED].

@alexchowle Thanks for the report! Are you utilizing remote configuration from kibana? I wonder if it's getting overwritten there?

You're 100% corrent. Thank you.


feat: consent card with custom onSubmit

Related Issue or Design Document
https://github.com/ory/elements/issues/110

Checklist

[ ] I have read the contributing guidelines and signed the CLA.
[ ] I have referenced an issue containing the design document if my change introduces a new feature.
[ ] I have read the security policy.
[ ] I confirm that this pull request does not address a security vulnerability.
If this pull request addresses a security vulnerability,
I confirm that I got green light (please contact<EMAIL_ADDRESS>from the maintainers to push the changes.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have added necessary documentation within the code base (if appropriate).

Further comments

Do the changes in this PR need testing?

yes, i haven't had time to complete it yet. It still requires a bit more e2e testing to make sure this works properly in the example nextjs application.


Add support to enableRemoteModule for electron >= 14

This PR gives the possibility to use karma-electron with electron >= 14 when using remote in renderer process.
This adds @electron/remote@2 dependency and the appropriate calls to enable remote in browserWindow webContents when creating them.
See https://github.com/electron/remote/blob/main/docs/migration-2.md

Hey @jeffcunat, thanks for the PR!
Unfortunately, I think your change will actually break for electron < 14 users who are still using the electron built-in remote module.
i.e. They'd still be using browserWindowOptions.webPreferences.enableRemoteModule so we'd try to load/call require('@electron/remote/main').initialize() which doesn't exist.
After reading through the documentation, it doesn't seem like any changes are needed to karma-electron at all to use the new package
i.e. We provide a require parameter which can invoke the necessary lines (which are in your PR)
https://github.com/twolfson/karma-electron/tree/7.3.0#launcher-configuration
// karma.conf.js
module.exports = function (config) {
  config.set({
    // Specify usage of our custom launcher
    browsers: ['CustomElectron'],

    // Define a custom launcher which inherits from `Electron`
    customLaunchers: {
      CustomElectron: {
        base: 'Electron',
        require: __dirname + '/test/karma-electron-require.js',
    }
  });
};

// test/karma-electron-require.js
require('@electron/remote/main').initialize();
app.on('browser-window-created', function (_, window) {
  require('@electron/remote/main').enable(window.webContents);
});

If you feel that we should have stronger documentation for this, or a convenience flag, then that's totally understandable and we should discuss that in a separate issue =)

It works great as you suggest. Thanks a lot.
So my PR is not useful. Maybe you should mention it in the docs...


Automated code review(codeclimate)

I think, it makes sense to connect this service or alternative

We've used this before but it didn't provide any meaningful insights for me.

It allows you to monitor the quality of the code and enter the code duplication, this can be done locally, but the service allows checking and PR

Locally I use https://github.com/danielstjules/jsinspect and on Semantic-UI he showed not a little duplication of code that is not terrible but not optimal.


tcmu-runner: fix the code style

Signed-off-by: Xiubo Li<EMAIL_ADDRESS>

Thanks for handling that cleanup.


[release-1.20] dedup domains for gateways with case sensitivity

This is an automated cherry-pick of #49674

@hanxiaop I think we should hold this now?

@hanxiaop I think we should hold this now?

@zirain Yes, I think we can hold this until the patch version is released, probably next monday or tuesday.


[BUG]: I don't know what causes this but, I'll link an image of how it looks for me

You must include the following details:

The game simply looks..interesting to say the least
Visual
I9 13900k, RTX 4090

Pretty sure you just don't have a pbr capable resourcepack. Load one in and completely restart the game.

I didn knew that I had to load the resourse pack, and then restart, worked now, all lights have those strange black dots everywhere, but very promising, this has much potential!


Problems: filter action should have aria-expanded set

Environment Details:
VSCode Version : 1.44.2
OS Version : Win10
Additional Details:
Screenreader: NVDA[2019.3.1], JAWS[2020.70]
GitHubTags: #A11yMAS; #A11yTCS; #Win32; #DesktopApp; #A11y_VSCode; #MAS1.3.1; #MAS4.2.1
Repro Steps:
1)Open Visual studio code editor
2)Press ctrl+shift+M
3)Validate it's possible to navigate between items in the problems view
4)Navigate to the Problem tab and then navigate to Filter button.
5)Open Jaws/NVDA and check whether it reads collapsed/Expanded after click enter on the filter button.
Actual:
Screen reader does not announce the state as Collapsed/Expanded when click enter on filter button.
Expected:
Screen reader should announce the state as Collapsed/Expanded when click enter on filter button.
User Impact:
Screen reader will not able to understand whether state of the scroll lock button is lock or unlocked
Attachment For Reference:
97125_A11y_VSCode_Problems Panel_ScreenReaderScreen reader does not announce the state as CollapsedExpanded when click enter on filter button.zip
Does this issue occur when all extensions are disabled?: Yes

@nirmalsahoo good issue. Agree with this.
@sandy081 can you just set aria-expanded: false on the "More Filters..."  button that way users will be aware that they can expand it to get the menu.

Does the value of aria-expanded to be fixed to false or change according to the menu?

You can change according to menu.
But in practice that will not happen -> since you can not have focus on tha action and have the menu open.

@isidorn Does this attribute has to be set on all drop down triggering actions?
https://github.com/microsoft/vscode/blob/ff118340b561fea6184172ffaf3bbf859b21055b/src/vs/base/browser/ui/dropdown/dropdown.ts#L305-L305

@sandy081 yes, that would be great.
Ideally we would set the aria-expanded value according to the menu, since maybe some action in the future will allow to have the menu open and focus somewhere else.

@sandy081 thanks for fixing this! I just tried it out from source and it looks good, thus adding verified label.


release artifact question

I am trying to bump the formula version to the latest, v1.10.4, and we did notice there is artifact change.
-   url "https://github.com/redpen-cc/redpen/releases/download/redpen-1.10.3/redpen-1.10.3.tar.gz"
+   url "https://github.com/redpen-cc/redpen/releases/download/redpen-1.10.4/redpen-distribution-1.10.4-assembled.tar.gz"

Can you educate the difference? Thanks.
Relates to https://github.com/Homebrew/homebrew-core/pull/52961

Bump this issue.

Deeply sorry for the late response @chenrui333. I updated the artifact name.

Thanks a lot, just curious if that is desired :)

Closing the issue now.


creating About , Contribute and Report and issue page

add GSOC ext and Hacktoberfest labels to it.................

? you gonna make templets ? for this contribute n report or what ?

@rahulsainlll i have already done it
assign me


Starting application error [Chapter 1]

i.Steps followed:

Cloned down repository.
cd into root of project.
git fetch --all
git checkout chapter1
npm install (Was successfull)

'npm start' (Seems to have worked properly)

ii.Issues:

Going to the local environment: http://localhost:8080/ (Getting empty response).

Any ideas why?
The npm start command has the right paths, I doubled checked.
I even deleted the repository and cloned it down again to see if I installed it wrong the first time. Same issue is happening.

So.. I cant view this project at localhost:8080, but I can view it at '<IP_ADDRESS>'.

Hi Josh,
I'm glad it works @ <IP_ADDRESS>
Which OS are you using? What's the node version you have installed?

Im using Yosemite. I haven't upgraded to El Capitan yet. Im using 4.4.1 version of node. Why do you ask?

Just to try to understand what could have happened...

It was one of those wonky things.


[Web] make it clear that -d web-server doesn't support debug protocol

When connecting to code-server with the browser(over ssh) or with vs code I can't start the web server debugger
I can for build web and that works without issues.
When I connect with vs code over ssh, the debug page never stops loading and the Dart debug extension stays gray. I can open the devtools on 9100 port, so port forwarding works.
PS C:\Users\mihcs> curl <IP_ADDRESS>:9100

StatusCode        : 200
StatusDescription : OK
Content           : <!DOCTYPE html>

                    <!--
                      Copyright 2018 The Chromium Authors. All rights reserved.
                      Use of this source code is governed by a BSD-style license that can be
                      found in the LICENSE file.
                    -->

                    <html>
                    <hea...
RawContent        : HTTP/1.1 200 OK
                    x-xss-protection: 1; mode=block
                    x-content-type-options: nosniff
                    Accept-Ranges: bytes
                    Content-Length: 5385
                    Cache-Control: max-age=900
                    Content-Type: text/html
                    Date: Tue, 07 Dec 20...
Forms             : {}
Headers           : {[x-xss-protection, 1; mode=block], [x-content-type-options, nosniff], [Accept-Ranges, bytes], [Content-Length, 5385]...}
Images            : {}
InputFields       : {}
Links             : {}
ParsedHtml        : mshtml.HTMLDocumentClass
RawContentLength  : 5385

PS C:\Users\mihcs> curl <IP_ADDRESS>:35731
curl : 404 Not Found
Only WebSocket connections are supported.
At line:1 char:1
+ curl <IP_ADDRESS>:35731
+ ~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
PS C:\Users\mihcs>

Steps to Reproduce

it's set up on an arm64 oracle linux 8 on oracle cloud
just downloaded flutter stable with fvm after downloading the dart sdk
latest code-server 3.12 from github

Logs

Logs

flutter doctor -v
[✓] Flutter (Channel stable, 2.5.3, on Oracle Linux Server 8.5 5.4.17-2136.301.1.4.el8uek.aarch64, locale
    en_US.UTF-8)
    • Flutter version 2.5.3 at /opt/flutter/stable
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18116933e7 (8 weeks ago), 2021-10-15 10:46:35 -0700
    • Engine revision d3ea636dc5
    • Dart version 2.14.4

[✗] Chrome - develop for the web (Cannot find Chrome executable at google-chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

[✗] Flutter IDE Support (No supported IDEs installed)
    • IntelliJ - https://www.jetbrains.com/idea/
    • Android Studio - https://developer.android.com/studio/
    • VS Code - https://code.visualstudio.com/

[!] Connected device
    ! No devices available

! Doctor found issues in 3 categories.

Here is the debug log, I noticed something strange, the log says 36503 port, but vs code opened up the 36375 port and it shows the 404 Not Found Only WebSocket connections are supported. message on that port and nothing listens on 36503. Checked it on the remote server too same situation.
flutter run -d web-server --debug --verbose
[  +60 ms] executing: uname -m
[  +27 ms] Exit code 0 from: uname -m
[        ] aarch64
[   +4 ms] executing: [/opt/flutter/stable/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[   +2 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] 18116933e77adc82f80866c928266a5b4f1ed645
[        ] executing: [/opt/flutter/stable/] git tag --points-at 18116933e77adc82f80866c928266a5b4f1ed645
[  +17 ms] Exit code 0 from: git tag --points-at 18116933e77adc82f80866c928266a5b4f1ed645
[        ] 2.5.3
[   +7 ms] executing: [/opt/flutter/stable/] git rev-parse --abbrev-ref --symbolic @{u}
[   +2 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [/opt/flutter/stable/] git ls-remote --get-url origin
[   +4 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +66 ms] executing: [/opt/flutter/stable/] git rev-parse --abbrev-ref HEAD
[   +2 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[  +43 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +2 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'WindowsUwpEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +50 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'WindowsUwpEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +82 ms] Skipping pub get: version match.
[ +104 ms] Generating
/home/opc/Projects/excercise_timer/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
[  +82 ms] Launching lib/main.dart on Web Server in debug mode...
[ +112 ms] Updating assets
[  +70 ms] Waiting for connection from debug service on Web Server...
[  +86 ms] <- reset
[   +6 ms] /opt/flutter/stable/bin/cache/dart-sdk/bin/dart --disable-dart-dev
/opt/flutter/stable/bin/cache/artifacts/engine/linux-arm64/frontend_server.dart.snapshot --sdk-root
/opt/flutter/stable/bin/cache/flutter_web_sdk/ --incremental --target=dartdevc --debugger-module-names
--experimental-emit-debug-metadata -DFLUTTER_WEB_AUTO_DETECT=true --output-dill
/tmp/flutter_tools.NFZLBQ/flutter_tool.MBMYDL/app.dill --libraries-spec
file:///opt/flutter/stable/bin/cache/flutter_web_sdk/libraries.json --packages
/home/opc/Projects/excercise_timer/.dart_tool/package_config.json -Ddart.vm.profile=false
-Ddart.vm.product=false --enable-asserts --track-widget-creation --filesystem-root
/tmp/flutter_tools.NFZLBQ/flutter_tools.IWJGAW --filesystem-scheme org-dartlang-app --initialize-from-dill
build/b1b715402d823b7fd5c2b68d2edcb2ce.cache.dill.track.dill --platform
file:///opt/flutter/stable/bin/cache/flutter_web_sdk/kernel/flutter_ddc_sdk_sound.dill --sound-null-safety
[  +10 ms] <- compile org-dartlang-app:/web_entrypoint.dart
[+23094 ms] Waiting for connection from debug service on Web Server... (completed in 23.2s)
[        ] Synced 26.4MB.
[        ] <- accept
[   +3 ms] Caching compiled dill
[ +165 ms] lib/main.dart is being served at http://localhost:36503
[        ] The web-server device requires the Dart Debug Chrome extension for debugging. Consider using the
Chrome or Edge
           devices for an improved development workflow.
[   +5 ms] 🔥  To hot restart changes while running, press "r" or "R".
[        ] For a more detailed help message, press "h". To quit, press "q".

Also, from vs code if I start debugging (f5) a white page pops up that never stops loading. If I start without debugging (ctrl+f5) a page pops up with the 404 websocket message.

@mihalycsaba when you say vscode remote are you referring to vscode remote development?
If so that doesn't seem to be an issue with flutter but with the environment, you are running in.

@maheshmnj yes with the remote development extension's ssh connection to code-server, tried to connect to code-server with chrome, but the web server debugging doesn't work there either.
Yeah probably my environment is the problem, I just don't know if it is the setup I did or the host's arm64 architecture. Like I said I can build the app for web, which is all I need. I feel like there is an issue with the web server on arm64.
I just wanted to try the oracle ampere a1, they give you 4 cpus for free and they're super fast. On my intel machine my biggest project sometimes takes minutes to analyze the code, in the ampere vps it's 5 seconds max.

@mihalycsaba this isn't really an issue with flutter but with the environment you are running in. Probably you may try asking about configuring and running flutter in your environment on of the support channels at https://flutter.dev/community.
Closing as this issue doesn't seem to describe a bug or a feature request in flutter, if you disagree feel free to write in the comments and I will reopen it.
Thank you.

@maheshmnj I have found this https://github.com/flutter/flutter/issues/56992 it says web targets are supported on arm64, but does that mean debugging too?

I'm trying to use remote and local vm linux servers for development with vs code. I connect with vs code's remote extension through ssh without problems. Building the app for web works without problems.
Something isn't working with the port forwarding or the web server device. Tried it in 2 different environments (local centos 7 x86_64 vm in vmware, remote oracle linux 8 x86_64 vm on oracle cloud), same results.

When I start the debugging in vs code(f5), a new tab opens in chrome but it never loads just hangs there loading and the Dart Debug extension remains grey.

I believe this is an issue with Remote ssh which must be filed with vscode in its dedicated repository. https://github.com/microsoft/vscode-remote-release/issues , This issue looks related https://github.com/microsoft/vscode-remote-release/issues/2318
Leaving this issue open for further confirmation from the team.

I'm trying to use remote and local vm linux servers for development with vs code. I connect with vs code's remote extension through ssh without problems. Building the app for web works without problems.
Something isn't working with the port forwarding or the web server device. Tried it in 2 different environments (local centos 7 x86_64 vm in vmware, remote oracle linux 8 x86_64 vm on oracle cloud), same results.

When I start the debugging in vs code(f5), a new tab opens in chrome but it never loads just hangs there loading and the Dart Debug extension remains grey.

I believe this is an issue with Remote ssh which must be filed with vscode in its dedicated repository. https://github.com/microsoft/vscode-remote-release/issues , This issue looks related microsoft/vscode-remote-release#2318

I don't believe it's related, in that issue they want port forwarding to work the other way too.
Meanwhile I have created a new ubuntu x86_64 vm on oracle cloud and the web server starts on ubuntu, it crashed a few times yesterday on it's own, but now it works. So I think this could be Red Hat related. Please don't close this issue yet, I want to use it a bit more on ubuntu.

So yeah, just when I posted the response here, it crashed again. Yesterday it crashed faster, sometimes after less than a minute. Please tell me how can I provide a more verbose log.
Launching lib/main.dart on Web Server in debug mode...
lib/main.dart:1
Waiting for connection from Dart debug extension at http://localhost:36031
The web-server device requires the Dart Debug Chrome extension for debugging. Consider using the Chrome or Edge devices for an improved development workflow.
Please click the Dart Debug extension button in the spawned browser window
This app is linked to the debug service: ws://<IP_ADDRESS>:33273/X7QR0U7Y7Rs%3D/ws
Debug service listening on ws://<IP_ADDRESS>:33273/X7QR0U7Y7Rs=/ws
💪 Running with sound null safety 💪
Connecting to VM Service at ws://<IP_ADDRESS>:33273/X7QR0U7Y7Rs=/ws
5
DOM changed detected: Re-initialize code copier
Restarted application in 2,148ms.
DOM changed detected: Re-initialize code copier
Restarted application in 1,779ms.
3
DOM changed detected: Re-initialize code copier
Restarted application in 1,620ms.
DOM changed detected: Re-initialize code copier
Application finished.
Exited (sigterm)

try this flutter run -d web-server -v

Please share complete logs by running flutter run -d web-server -v

Well, it doesn't crash with this command. But this way hot reload doesn't work with ctrl+s. Also I don't have to click the dart debug extension for the page to load.

Tried it in an ubuntu ampere a1 (arm64), crashes there too within a minute, if I start it with f5

Well, it doesn't crash with this command. But this way hot reload doesn't work with ctrl+s. Also I don't have to click the dart debug extension for the page to load.

Running the above command you should be able to hot reload from the terminal by pressing r.
I am not sure if flutter can do anything about it leaving this issue open for further investigation from the team.
cc: @yjbanov

The -d web-server option is meant for a plain browser-server mode with not extra debugging capabilities. There's no guarantee that it will be possible to debug through VSCode. We should probably make attempts to connect to the debug protocol fail more proactively and with better error messages. You can debug in this mode using the browser's devtools and sourcemaps.
Let's repurpose this issue to make it more clear that -d web-server doesn't support the debug protocol, only -d BROWSER does, where BROWSER is chrome or edge.

@yjbanov How we are supposed to run Web tests and get the logs e.g. in Github Actions with in HEADLESS browser mode, if web-server does not support debugging? Thanks ;D

Hi Yegor (@yjbanov), where do you propose we “make it more clear that -d web-server doesn’t support the debug protocol?”—i.e. could you (or anyone) remind us where the -d web-server command line option is even documented?

@rmschindler  and @yjbanov my suggestion would be to document this in https://docs.flutter.dev/testing/debugging as I think Flutter webapp debugging is quite different from debugging mobile and desktop Flutter apps and definitely has its own quirks in regards to only Chrome & Edge being supported as debug targets and issues like this where the d web-server flag can be used to run a debug build and yet not allow for using an external debugger to connect to the running Flutter app.

the help of "flutter run -h" was not clear for the following:
flutter run -d web-server --web-port 8090


Use debug from npm instead of custom debug solutions

This uses npm’s debug module to manage logging.

@ArtOfCode- Why?

@j-f1 Mostly because in all likelihood I did it like that for a reason

^ FDSC approved, other script authors should look at their own stuff

@Ferrybig Does Spamtracker work again?

@j-f1 No, Still the same error.

@ jf After a look through the code, it seems UnsafeWindow is defined as window using the IIFE, for some reason your script is probably included in the global window scope, we can add another argument for this "UserScriptManagerWindow" argument

https://chat.stackexchange.com/transcript/message/37405109#37405109

@ferrybig Are you using Greasemonkey?

@j-f1 tamper monkey on Google chrome.
Could it be the case that it works for you because another userscript is importing the debug library in the window variable, as haven't installed the other userscripts


updated code climate.yml

Updated .codeclimate.yml to work with the new CodeClimate engines
(their next generation engine) vs the existing one. See
http://blog.codeclimate.com/blog/2015/06/19/code-climate-platform/

@AllenBW @himdel for your review :)

@AllenBW added

Looks good, I think :)

@chriskacerguis This did not make it into Euwe branch. Please label euwe/yes or euwe/no, as appropriate.


Native apple wallet button

Fixes #932.
Added native module component.
Need to run pod install.

Did you manage to resolve issues with styling?


Add testing to microservices

Unit testing should be the minimum here. This should be done in such a way that the tests can be automated with a webhook on the repository.
Note: This should include testing of the RediSearch loading script to ensure that data is being loaded as expected.
Thought: Perhaps the data used to test the RediSearch loading script should be a common set of data used to test all the services that consume data from Redis/RediSearch.

This issue is stale and probably merits its own epic when the time comes. Closing for now.


Download a rental video

So I paid for a rental video, but I need to use youtube-dl to download it because my connection is too slow to just watch it on Youtube. Whenever I try to download the video, it gives me an error that "rental" videos are not supported. How can I download this?

I'm genuinely curious about how this DRM is accomplished when YouTube claims to have moved to HTML5. Do the rental videos still use Flash? Or do they use (not yet and hopefully never standard) EME?

I'm genuinely curious about how this DRM is accomplished when YouTube claims to have moved to HTML5. Do the rental videos still use Flash? Or do they use (not yet and hopefully never standard) EME?

I'm genuinely curious about how this DRM is accomplished when YouTube claims to have moved to HTML5. Do the rental videos still use Flash? Or do they use (not yet and hopefully never standard) EME?

To download youtube paid videos, firstly you need to have a paid account.
Then use Allavosft to download them offline with this guide https://www.allavsoft.com/how-to/download-youtube-rental-movies.html

@cbehan Probably widevine.


Add note about skuid-sfdx

@itmightbecody Build failures have been fixed on master, so if you can merge master into this branch, we should be good to go

@zachelrath Build passing 🙌


Add copy & paste shortcut to the container recipe edit menu

When users have a lot of container input slots that all need the same input at once, it can be time-consuming to manually fill all of them. It would nice if I would add a copy (c) and paste (p) shortcut to the container recipe edit menu.

This will be implemented in Editor 10.2.


Plugin generated a warning from the characteristic "Current Relative Humidity" error

Describe The Bug:
Humidifier is not reporting current humidity levels, night light brightness or set to humidity level in Homekit.
To Reproduce:
Check Homekit, shows 0%. I was able to fix this by rolling back to the previous version but yeah..
Expected behavior:
Humidfier reports current humidity levels, night light brightness, and humidity set to level in Homekit.
Logs:
[7/24/2022, 4:45:53 PM] [homebridge-levoit-humidifiers] This plugin generated a warning from the characteristic 'Current Relative Humidity': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
[7/24/2022, 4:45:53 PM] [homebridge-levoit-humidifiers] This plugin generated a warning from the characteristic 'Current Relative Humidity': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
[7/24/2022, 4:45:53 PM] [homebridge-levoit-humidifiers] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
[7/24/2022, 4:46:14 PM] [homebridge-levoit-humidifiers] This plugin generated a warning from the characteristic 'Current Relative Humidity': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
[7/24/2022, 4:46:14 PM] [homebridge-levoit-humidifiers] This plugin generated a warning from the characteristic 'Current Relative Humidity': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
[7/24/2022, 4:46:14 PM] [homebridge-levoit-humidifiers] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
[7/24/2022, 4:46:15 PM] [homebridge-levoit-humidifiers] This plugin generated a warning from the characteristic 'Current Relative Humidity': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
[7/24/2022, 4:46:15 PM] [homebridge-levoit-humidifiers] This plugin generated a warning from the characteristic 'Current Relative Humidity': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
[7/24/2022, 4:46:15 PM] [homebridge-levoit-humidifiers] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
[7/24/2022, 4:46:18 PM] [homebridge-levoit-humidifiers] This plugin generated a warning from the characteristic 'Current Relative Humidity': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
[7/24/2022, 4:46:18 PM] [homebridge-levoit-humidifiers] This plugin generated a warning from the characteristic 'Current Relative Humidity': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
[7/24/2022, 4:46:18 PM] [homebridge-levoit-humidifiers] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "undefined" (undefined). See https://homebridge.io/w/JtMGR for more info.
Show the Homebridge logs here, remove any sensitive information.

Plugin Config:
{
"name": "Levoit Humidifiers",
"email"<EMAIL_ADDRESS>"password": "mypassword",
"accessories": {
"cool_mist": false,
"warm_mist": false,
"sleep_mode": false,
"display": true,
"night_light": true
},
"platform": "LevoitHumidifiers",
"_bridge": {
"username": "macaddress",
"port": port
}
}
Show your Homebridge config.json here, remove any sensitive information.

Screenshots:

Environment:

Plugin Version: 1.7.1
Homebridge Version: 1.5.0
Node.js Version:  16.16.0
NPM Version:  8.11.0
Operating System:  Ubantu

This is fixed in 1.7.2 thanks to @smockle. Thanks for writing this big up!


npm ERR! 404 Not Found - GET https://registry.npmjs.org/@iconify%2Fjson-mdi - Not found

`$ npm i --dev @iconify/json-mdi --dev @iconify/json-uil
npm WARN config dev Please use --include=dev instead.
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@iconify%2Fjson-mdi - Not found
npm ERR! 404
npm ERR! 404  '@iconify/json-mdi@*' is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR!      C:\Users\Vad\AppData\Local\npm-cache_logs\2023-05-16T13_42_24_628Z-debug-0.log`

The documentation has been updated with all package managers 🙂

I am still having trouble displaying the icons. maybe they didnt install correctly.

`$ npm install -D @iconify/json-mdi @iconify/json-uil
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@iconify%2Fjson-mdi - Not found
npm ERR! 404
npm ERR! 404  '@iconify/json-mdi@*' is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR!      C:\Users\Vad\AppData\Local\npm-cache_logs\2023-05-16T19_11_30_280Z-debug-0.log`

It is related to PR I opened - #166 - install commands are incorrect in documentation, as correct definition is iconify-json/{package}


[HUDI-986] Support staging site for per pull request

What is the purpose of the pull request
Support staging site for per pull request.
Brief change log

Modify relative path
Add support staging site docs

Verify this pull request
https://lamber-ken.github.io/hudi-staging-site
Committer checklist

[X] Has a corresponding JIRA in PR title & commit

[X] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@xushiyan are you able to help review this

@xushiyan are you able to help review this

Sure i can help with this.

hello @xushiyan, this pr is ready for review now : )

cc @vingov wondering if we can provide something like this for the new site as well.
Closing this since we have moved off jekyll even since

@vinothchandar - yes, good idea, created this HUDI-2407 Jira to track this work.


Downloading a workflow artifact fails on some machines

Description
We are having an issue with downloading artifacts from a workflow that seems to be machine dependent.
It works fine on one machine but not on the other, where a GitHub server blocks access.
Both of them are Raspberry Pi’s that are configured as self-hosted runners in GitHub.
The message Message:
"Error: request to ... failed, reason: connect ECONNREFUSED <IP_ADDRESS>:443"
Tested Actions:

dawidd6/action-download-artifact@v2
benday-inc/download-latest-artifact@main

The Raspberry Pi where downloading fails is hosted here in a datacenter: https://www.mythic-beasts.com/order/rpi/
Not sure if this is a bug, but the GitHub support directed me here.
Maybe there is a firewall in the way.
Area for Triage:
question
Question, Bug, or Feature?:
"Question"
Virtual environments affected
Not in the list and not a virtual environment:

[X] Raspberry Pi OS 10.8

Image version

Raspberry Pi OS / Debian 10.8

Expected behavior
Action (e.g. dawidd6/action-download-artifact@v2) downloads workflow Artifact sucessfully.
Log from workflow:
==> Workflow: build-workflow.yml
==> Repo: abelikt/thin-edge.io
==> Conclusion: success
==> Branch: continuous_integration
==> RunID: 924219248
==> Artifact: 66618074
==> Downloading: debian-packages-amd64.zip (4.44 MB)
...

Actual behavior
Access fails: "failed, reason: connect ECONNREFUSED <IP_ADDRESS>:443"
Log from workflow:
Run dawidd6/action-download-artifact@v2
==> Workflow: build-workflow.yml
==> Repo: abelikt/thin-edge.io
==> Conclusion: success
==> Branch: continuous_integration
Error: request to
https://api.github.com/repos/abelikt/thin-edge.io/actions/workflows/build-workflow.yml/runs?branch=continuous_integration&event=&status=success failed, reason: connect ECONNREFUSED <IP_ADDRESS>:443

Repro steps
Steps to reproduce:
https://github.com/abelikt/thin-edge.io/blob/continuous_integration/.github/workflows/download_artifact.yml
Fails: hosted_offsite_dawidd6 (in the datacenter)
Passes: hosted_onsite_dawidd6 (local Rpi)
Fails: hosted-offsite-benday-inc (in the datacenter)
Executed workflow:
https://github.com/abelikt/thin-edge.io/runs/2801291666?check_suite_focus=true
Additional Info
I also raised tickes here

https://github.community/t/downloading-a-workflow-artifact-is-refused-some-machines/183951
https://github.com/dawidd6/action-download-artifact/issues/78
GitHub Support

Hi @abelikt!
We are in charge of hosted infrastructure only, so, unfortunately, we can't help you with self-hosted runners and network issues. You can try creating an issue in https://github.com/actions/runner/issues repository, but I'm not 100% sure it's the right place either


User context in laravel 5.4

Hi i would like to ask how you can add user context to sentry's entry when Auth::user() is null. This is related to laravel's auth handling for laravel versions > 5.2. Thanks

Hi!
For adding context we have an example for a middleware (but you can place the code that sets the user context anywhere) that adds user context or any other context you like.

https://github.com/getsentry/sentry-laravel#adding-context

But in Laravel >5.2 nothing should have changed in using Auth::user() so I'm a bit puzzled what it is that is not working, can you elaborate?

thanks @stayallive for you reply. i will be more accurate:

i install sentry via composer, i set providers and alias in config app
i set new report function in Handler.php as it is in install instructions, set env
so far everything is running as it should

next i wanted to add user context by middleware as you have in docs, i did but \Auth::user() is in laravel > 5.2 not created yet here. so let's have example.
when you have some syntax error or so in controller, it goes to sentry middleware and try to add user context, but user does not exists yet and \Auth::user() is null and auth()->check() is null - everytime.
you can see changes in auth (from L 5.3) handling here: https://laravel.com/docs/5.3/upgrade#5.3-session-in-constructors

A syntax error is not something that is easily catched, but I assume on syntax error you don't need the user 😉  How Laravel works I don't think it's possible to add the user context using a middleware since the controller is included before the middleware are run so the syntax error happens before any middleware had a chance to run. I don't think there is a place in Laravel where the session started and initialized before a syntax error is thrown, try it with an Exception.
But for other errors, is your Sentry middleware after the \Illuminate\Session\Middleware\StartSession middleware? You should add the Sentry middleware in your http Kernel (after the session middleware) not in your controller.
I am using the exact code shown in the docs in multiple Laravel 5.4 apps (the example came from me) so it should work for you to.

I think the middleware should be included as part of Sentry then you just add instructions to add it to the middleware list - It's quite confusing that there is a config option for user_context but only seems to work in Laravel 4.2.

Also, it's recommended to add it under a middleware but can't the user just get set inside your exception handler just before you captureException ? Is there any strong reason why you shouldn't do that? Unless some other part of your app uses sentry to capture then it would make sense... but all exceptions should be caught by the handler

The user_context option works for 4.2 and above (tested all the way to 5.4) as long as you want to get the user context from the the default guard. Is it not working for you in 5.x?
Yes you can also add the user context right before you send the errors of the Sentry but that adds an added panelty of setting the user context multiple times (if you get multiple errors in a sessions). And some users sent their app()->log('error', 'Ooops...') to Sentry which does not go through the exception handler, but they do want user context or environment tags/context. That is why we recommend doing it as early as possible so all the ways you can use Sentry work, adapt it for your needs 😉

That's good point about app()->log makes sense to set it in a middleware for that reason. Really wish Laravel had a Session::afterLoad(function().... type thing as an alternative but meh.
And no, the user_context thing does not work in Laravel 5.x for me at least. Inside the service provider there is bindEvents() which gets called on boot which seems to resolve sentry immediately - this may explain why Auth is not available as at that point the session hasn't been loaded. Does it work for you?

Personally I think SentryLaravelEventHandler should be refactored slightly so that it doesn't need the raven client - it should just be a repository of information for the logged events, then when the exception is captured to sentry it "attaches" all the data to the raven client.
At the moment, the information is attached straight away to the raven client as soon as the events are fired - this is kind of a waste because an exception might not even occur or be reported, yet it's still loading sentry and attaching stuff to it!

I see where the problem could be, thanks for pointing it out. I will try to recreate this later in a fresh Laravel install.
The SentryLaravelEventHandler depends on the client so it can add breadcrumbs as they come to make sure breadcrumbs are also sent on app()->log() calls if the user uses that 😄
This way a breadcrumb never get's lost because somehow the breadcrumb collector could not attach it before events get sent.

Log::info()can still be supported too, you could listen forilluminate.log` and then attach all the data to sentry if bound. Ideally exceptions should be a rare occurrence and initialising sentry client every single time even when no logs are produced seems a bit unnecessary to me. Dunno, maybe I'll fork the library and go with a different implementation.

We are accepting PR's @garygreen 😉

Ha ok well maybe I'll send a PR then, though I do think we have fundamental different views on how the flow should be - I'm more of a "delay everything until needed" kinda guy and your approach is "process everything right now just in case" which is the safest way to be, but I think reasonable assumptions can be made about how/when things get reported to Sentry 😄

This is always a thin line to walk, especially for something that could be mission critical like Sentry, if you miss a piece of the puzzle it could set you back hours potentially.
But maybe you have some great ideas on how to not be like the "process it NOW" and more towards the "maybe later". Happy to discuss them in a PR or another issue since we are moving away from the original problem of this issue ;)

@garygreen & @matomoravcik can you guys check out #81, this should fix the problems on Laravel >=5.3 regarding the user context.

@stayallive I'm having issues with user_context as well. Currently on laravel 5.4.30 and created the middleware to add the user context. I have logging in the same location as where I add the user_context so I know its being called, but the user never shows up in the stacktraces in Sentry. I've also tried enabling and disabling the user_context config option, but no change.


change documentat and issues URL

change documentat and issues URL
Fixes #ISSUSE_ID.
Changes proposed in this pull request:

change documentat and issues URL


Consider using ImageBitmapOptions for createImageBitmap

Got a heads-up from @pjcozzi. Looks like there will some way of seeing what createImageBitmap options are available. Consider using this in our createImageBitmap usage(which itself is not in cesium main yet, but has value when streaming image heavy models. See: https://github.com/AnalyticalGraphicsInc/cesium/issues/6624)
whatwg pr:
https://github.com/whatwg/html/pull/4248
From that commit:

Constructs and returns a new ImageBitmapOptions dictionary whose attributes are
initialized to the corresponding attributes of the options dictionary. Only those
attributes which are recognized by the user agent are included in the returned dictionary. This
allows web applications to detect which ImageBitmap creation options are supported.

We've added createImageBitmap. Until this is supported by browsers, we actually attempt to decode a 1x1 image and see if it throws any errors given these options.


Tillerino-Like Bot

Dev-Kun submitted a feature request: Tillerino-Like Bot
well, I'd like him to suggest me some bm and stuff so i can gain pp like on osu! server.

Despite being a smart bot, I can not automagically respond to the user if you have any feedback to give them. Thus, if you wish to tell 'em something, respond here: https://ripple.moe/index.php?p=114&id=53

#ILBUGDEIPP
On 30 March 2016 12:39:03 CEST, Schiavo<EMAIL_ADDRESS>wrote:

Dev-Kun submitted a feature request: Tillerino-Like Bot
well, I'd like him to suggest me some bm and stuff so i can gain pp
like on osu! server.

Despite being a smart bot, I can not automagically respond to the user
if you have any feedback to give them. Thus, if you wish to tell 'em
something, respond here: https://ripple.moe/index.php?p=114&id=53

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/osuripple/ripple/issues/109

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Question about done and failed action creators

Is there a way to skip params in async action results? Something like:
    done: ActionCreator<S>;
    failed: ActionCreator<E>;

Let's say I want to fetch all users. This is kind of what I expected: (pseudocode)
dispatch fetchingAllUsers.started();
// do the fetching
if (error) {
    fetchingAllUsers.failed({ error: error.message });
} else {
    fetchingAllUsers.done({ users: users[] });
}

I'm mostly new to all this so I was wondering if I'm missing something or if there's a better way to utilize this library.
Thanks!

Async action creators are meant to wrap async processes, like a network request. The params are needed to correlate the response with the request arguments. Imagine that you're making many similar requests through a single AAC.
The most convenient way for using AAC is to make a wrapper based on how you do async stuff in your project.
Here's a ready to use wrapper for redux-saga: https://github.com/aikoven/typescript-fsa-redux-saga
There is also a discussion on integrating AACs with redux-thunk: https://github.com/aikoven/typescript-fsa/issues/19

Thanks for the explanation! In your redux-saga example, how does mySaga get triggered in the first place? Do I need to take a startDoSomething action? E.g.

Component wants list of users
Dispatch startFetchingUsers
Outer saga (mySaga) takes this action and calls the boundAsyncAction saga
fetchingUsers.started/done/failed are dispatched respectively

I really like the idea of automatically dispatching actions throughout the lifecycle of a saga, but to me it seems like steps 2-3 are a bit redundant. So in my case I'd want to dispatch fetchingUsers.start, and then have the bound saga take it and report the results through .done/failed
Would you mind clarifying this for me as well? Thanks again!

The AAC.started action is not something that triggers an async process, more like an event that happens once the process is started.
So once you've bound your process with bindAsyncAction you get the same thing but wrapped with actions. You execute it just like you would have done with the original process (with yield call(...)).
To wire it up with the component I'd do this: once a component is mounted, dispatch an action SOME_COMPONENT_MOUNTED. Then use takeEvery/takeLatest in the saga to start the process.
 If a user clicks a button somewhere, just dispatch SOME_BUTTON_CLICKED. This greatly decouples components from the logic which is spread between reducers and sagas.

Great tips, thank you!


Show Auto-Suggest popup only when status type is not NON_TASK

Please check that this issue hasn't been reported before.

[X] I searched previous Bug Reports didn't find any similar reports.

Expected Behavior
The Auto-Suggest popup should only appear as documented in the documentation:

a bullet with a checkbox (- [ ] or * [ ])
and the global filter (if any).

Current behaviour
However, the Auto-Suggest popup appears based on the TaskRegularExpressions.checkboxRegex (Task.ts#L51). Because of that, the popup appears for any of the following lines as well:
- [p] task
- [-] task
- [?] task
// ..

Any characters within the brackets causes the popup to appear, even though it should only appear for - [ ], * [ ] as well as - [x] and * [x] (not in the documentation).
Background
I am using the theme obsidian-things which supports these checkbox icons. Except for - [ ] and - [x] the tasks auto-suggest popup is not necessary.
Steps to reproduce
Enter any of the examples listed in Current behaviour.
Which Operating Systems are you using?

[ ] Android
[ ] iPhone/iPad
[ ] Linux
[ ] macOS
[X] Windows

Obsidian Version
1.1.9
Tasks Plugin Version
1.22.0
Checks

[X] I have tried it with all other plugins disabled and the error still occurs

Possible solution
Rework the regex used for Auto-Suggest.
Either a different regex has to be defined for Auto-Suggest or the existing one can be modified.
The regex could look something like this:
checkboxRegex = /\[([\sx])\]/u; // Matches 'space' and 'x' in the brackets

As far as I can tell different characters within the brackets are not used in Tasks.
Thank you!

Hi @schmjop Thank you for reporting this. I hadn't noticed that condition in the docs, and certainly have sometimes been a bit irritated by the auto-complete menu appearing when I didn't intend to be editing a task.

As far as I can tell different characters within the brackets are not used in Tasks.

That is about to change. I am working on adding support for custom statuses.
Later on, I intend to provide a way for users to indicate any of their custom statuses that should not be treated as tasks.
At that point, I think it would be a good time to adjust the auto-complete code to be more selective about when it pops up the menu.

Hi @claremacrae, thank you for your quick response and your work regarding the Tasks plugin!
The roadmap sounds great and I agree with the points mentioned.

Hi @claremacrae, thank you for your work on this plugin, I really enjoy the new features and improvements.
Since it is now possible to assign different statuses to a status type (TODO, IN_PROGRESS, DONE, CANCELLED and NON_TASK) in the plugin settings, I would like to change the scope of this issue and propose the following idea:

Only show the auto-suggest popup when the task status type is not NON_TASK. Therefore, it is only shown when relevant.

Let me know what you think.

Hi @schmjop - many thanks for improving the issue. I do agree.


the ALSAWidget bar keeps showing after hide_interval time

the bar doesn't auto hide at all

Works absolutely fine for me with that config.
Have you got some app open that could be adjusting volume levels?


Default Version for 2.x

Isn't default version for 2.x is 7.0. I have core Version:   2.2.105 and csc /langversion:? shows 7.0 as default.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5694e62b-c756-1f62-4014-2ceafa54c011
Version Independent ID: 3f01c378-22e4-197c-a862-ab4a924506c7
Content: C# language versioning - C# Guide
Content Source: docs/csharp/language-reference/configure-language-version.md
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

What csc /langversion:? tells you depends on the csc that's in your PATH. But .Net Core isn't using that, so it does not reflect what's going to be used when you build a .Net Core project.
For example, when I open Developer Command Prompt for VS 2017, csc /langversion:? reports 7.0 as default (and 7.3 as latest). But when I run dotnet new console and dotnet run in that same prompt, it uses C# 8.0 preview, because I have .Net Core 3.0 preview installed. And when I edit the csproj to switch to .Net Core 2.1, it uses C# 7.3 instead.
As far as I can tell, this means that the table is correct.

hmm. so csc /langversion:? is not the right way of identifying c# version used by dotnet core.
How did you check that 3.0 is using C# 8.0 and 2.1 is using c# 7.3?

By attempting to use language features from those versions.
You can also try to print the value of LangVersion in csproj, but that doesn't tell you the version directly: for .Net Core 3.0, it's preview and for .Net Core 2.0, it's empty, which means "default for the version of the C# compiler used", in this case, 7.3.
Neither of those options is great, so I think your best option is to trust the table. 🙂

I'm going to close this, as the table is the best information.


atom-text-editor[mini] didn't get correct font size

font size are smaller than setting
Reproduction Steps:

Update this package.
I notice font size in search bar become smaller than previous version, try go to setting to fix it.
When disable this theme font size setting are fine.

Expected behavior:
font size should correct in search bar
Observed behavior:
font size are setting to 12
Screenshots and GIFs

Atom version: 1.17.0
OS and version: Win7
Installed packages:
Atom material UI and syntax theme

Good catch, but you won't get the exact same size.
This feature should probably be renamed because it should affect the entire UI, not just text. Buttons, for example, aren't being correctly resized for the same reason: they are using fixed UI variables (@component-line-height and @component-padding) instead of being based off of this value.

@silvestreh I can confirm on Windows that this setting does not do anything. When I disable the theme, my UI font sizes are fine. When it's enabled, all UI fonts are roughly 12px and almost unreadable. I do not have this problem on my MacBook.


Add forgot password link

Please add forgot password link after user id and password field in the login page.

Good job. 👍


Should markers be erased when the image changes?

I can see arguments both ways, opening to remember to come back to this....

If you work on different exposures of a similar sky FOV, usually you want to keep the markers on (and aligned by RA/DEC, rather than X/Y. That is a common use case I heard of at least here at STScI. If you are just opening exposures of different fields, then it makes more sense to erase them. Perhaps this behavior can be a user configurable setting. 🤔

I would say "no" because in glue-jupyter backend, we want the markers to stay on even when blinking. So this question is backend specific and should be decided by each backend separately.


Create Dependabot config file to let it create automatically PRs about dependency updates

This is already a thing as far as I know.
And if it isn't, doesn't it need to be enabled via repository settings @tmberthold ?

This is already a thing as far as I know. And if it isn't, doesn't it need to be enabled via repository settings @tmberthold ?

Dependabot will automatically open pull requests if they are security-relevant, i.e. direct dependencies have known vulnerabilities.

We do not have Dependabot active for simple version-updates, wich are not considered security-relevant. We decided against this some time ago and will not activate it again. Experience shows that nobody cares about those automatically opened pull requests if they are only opened for version updates.


Trouble fetching fields I specify

I am following the tutorial here  to customise my results and show the fields I specify in the dropdown.
My engine is called AZTwo and I have tried with this code to specify the fields I want. These are the field names given them by SwiftType, as shown in my control panel:
var showQuickResults = function(document_type, item) {
	var out = '
' + item.highlight['title'] + '';
	return out.concat('  -  ' + item.highlight['object_type'] + '');
};

jQuery('#st-search-input').swiftype({
  renderFunction: showQuickResults,
  engineKey: '{my_engine_key}',
  fetchFields : {'aztwo' : ['title', 'object_type', 'excerpt', 'external_id' ] },
  searchFields: { 'aztwo': ['title'] },
});

However, the results I get show 'undefined' instead of the object_type value.
(See attached screenshot).
Can you tell me what I'm doing wrong?
Many thanks
Tim

I think the problem might be that we're trying to access item.highlight['object_type'] which resolves to undefined, because we don't have object_type in highlightFields.
The third code block in this section has an example of using highlightFields.
I see two possible solutions here:

Try setting up highlightFields when you initialize plugin
Instead of item.highlight['object_type'] try accessing item['object_type']

Let us know if it helps!

Thank you. Yes - changing it to item['object_type']   worked perfectly.
I will read up on highlightFields as you suggest.
Many thanks for your speedy help. Much appreciated!


Enforce filename format

We should enforce kebab-case filenames per our style guide. sindresorhus/eslint-plugin-unicorn has a filename-case rule that can do this for JavaScript files. Perhaps we could write an analogous HTMLHint rule.

This is a duplicate of #6 -- but that's nice plugin link.


Add Variable Substitution support for cmake-variants.yaml

Brief Issue Summary

Expected:

Push button
Thing happens

Apparent Behavior:

Push button
Nothing happens

CMake Tools Log

<!-- Paste the log contents HERE -->

Developer Tools Log

<!-- Paste the log contents HERE -->

Platform and Versions

Operating System:
CMake Version:
VSCode Version:
CMake Tools Extension Version:
Compiler/Toolchain:

Other Notes/Information

it's supported
buildType:
  default: debug
  choices:
    debug:
      short: Debug
      long: Emit debug information
      buildType: Debug
    release:
      short: Release
      long: Optimize generated code
      buildType: Release
    relwithdebinfo:
      short: RelWithDebInfo
      long: Debug + Release
      buildType: RelWithDebInfo

os:
  default: win32
  choices:
    win32:
      short: win32
      long: Windows platform
      settings:
        CMAKE_PREFIX_PATH: ${workspaceRoot}/../llvm-release/LLVM


Uncomment pybluez requirement in requirements_all.txt

Description: Uncomment the pybluez requirement in requirements_all.txt
Related issue (if applicable): none
Pull request in home-assistant.github.io with documentation (if applicable): none
Example entry for configuration.yaml (if applicable):
none
Checklist:

[ ] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Hi @nattofriends,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

We don't do drive by PRs


”Brădeni” is listed in the drop-down menu

Description:
"Brădeni" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "Brădeni" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Brădeni, SIBIU".


API involved when scanning a QR code by the WA-App on a mobile device.

Hi there,
thanks to all contributors of this great project!
I'm searching for insights about the API involved when scanning a QR code by the WA-App on a mobile device.
Concretely, I'd like to perform the registration steps between

Turn this string into an image (e.g. using pyqrcode) and scan it using the WhatsApp app.

and

Immediately after you scan the QR code, the websocket receives several important

according to README.md programmatically. Unfortunately, I can not find any related documentation.
Thanks a lot!

Wild guess:

Whatsapp mobile app has registered its public key with whatsapp server before during account setup.
Whatsapp app signs the data in the QR code and send back to server to authorize the client.
Whatsapp server sends data to the web browser after that authorization.