Test projects are not running or failing

Question, Bug, or Feature?
Bug
Enter Task Name: VSTest@2
- task: VSTest@2
  condition: and(succeeded(), eq(variables['skipTests'], 'false'))
  displayName: 'Test Assemblies'
  inputs:
    testSelector: 'testAssemblies'
    testAssemblyVer2: |
      **\$(BuildConfiguration)\**\*test*.dll
      !**\obj\**
    searchFolder: '$(System.DefaultWorkingDirectory)'
    testFiltercriteria: 'TestCategory=Unit&TestCategory!=ToBeFixed&TestCategory!=DataDriven'
    runOnlyImpactedTests: false
    vsTestVersion: 'toolsInstaller'
    runInParallel: true
    codeCoverageEnabled: true
    platform: '$(buildPlatform)'
    configuration: '$(buildConfiguration)'
    diagnosticsEnabled: false

Environment
Azure Pipelines

Agent - Hosted or Private:

Private
Issue Description
Projects are not unit tested because of a System.IO.FileNotFoundException error while trying to find the tests in a test project.
Worse, these errors don't fail the test task. I have multiple test projects that aren't even running their tests.
If tests for a project fail to run due to an error, the task should NOT be marked as successful.
Task logs
Example1:
No test matches the given testcase filter `TestCategory=Unit&TestCategory!=ToBeFixed&TestCategory!=DataDriven` in C:\BuildAgent\_work\1\s\src\Clients\Clients2.Common.Tests\bin\Debug\netcoreapp3.1\cs\Microsoft.TestPlatform.CrossPlatEngine.resources.dll
[MSTest][Discovery][C:\BuildAgent\_work\1\s\src\Clients\Clients2.Common.Tests\bin\Debug\netcoreapp3.1\Rhyous.WebFramework.Clients2.Common.Tests.dll] Unable to load types from the test source 'C:\BuildAgent\_work\1\s\src\Clients\Clients2.Common.Tests\bin\Debug\netcoreapp3.1\Rhyous.WebFramework.Clients2.Common.Tests.dll'. Some or all of the tests in this source may not be discovered.
Error: System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

Example2:
No test matches the given testcase filter `TestCategory=Unit&TestCategory!=ToBeFixed&TestCategory!=DataDriven` in C:\BuildAgent\_work\1\s\src\WebServices\Webservices.Wcf.Tests\bin\Debug\net48\Microsoft.VisualStudio.TestPlatform.MSTest.TestAdapter.dll
No test matches the given testcase filter `TestCategory=Unit&TestCategory!=ToBeFixed&TestCategory!=DataDriven` in C:\BuildAgent\_work\1\s\src\WebServices\Webservices.Wcf.Tests\bin\Debug\net48\Microsoft.TestPlatform.AdapterUtilities.dll
2.2271
[MSTest][Discovery][C:\BuildAgent\_work\1\s\src\WebServices\Webservices.Wcf.Tests\bin\Debug\net48\Ivanti.Tools.UnitTestFramework.dll] Unable to load types from the test source 'C:\BuildAgent\_work\1\s\src\WebServices\Webservices.Wcf.Tests\bin\Debug\net48\Ivanti.Tools.UnitTestFramework.dll'. Some or all of the tests in this source may not be discovered.
Error: System.IO.FileNotFoundException: Could not load file or assembly 'Autofac, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=17863af14b0044da' or one of its dependencies. The system cannot find the file specified.

Troubleshooting
n/a
Error logs
n/a

It is still happening. Has anyone taken a look at this?

Why are we closing something without looking at it?

Looks like I'm not the only one reporting this issue: https://github.com/Microsoft/vstest/issues/1899

See also #14328.


Quicklook and clear current object doesn't reset to global search

If I navigate, select an object and quicklook (at) it, after pressing ⌃U or twice ⌫ I can only further search in that hierarchy where the object is located instead of globally.
https://groups.google.com/forum/?fromgroups=#!topic/blacktree-quicksilver/CzognL03dMk

I’m not sure when it changed, but I just tried navigating, Quick Looking something, clearing with ⌫⌫ or ⌃U, and searching was using the global catalog.
Can you confirm @1-61803 (and close this if it’s no longer an issue)?

I wish I could, but since I'm still using 1.2.0 I cannot. Close it if it's been solved in the latest release.

So I tested this:
⌃U and ⌫⌫ both clear the object but I can still only search in the same folder.
Still seems 'broken'

I can still only search in the same folder.

Hmm. I can’t reproduce it.

Call up Quicksilver
Type DL/ to get into ~/Downloads
Search for something
Clear with ⌫⌫
Search for something else

In step 5, I’m searching the catalog. Hitting ↓ to show the results list confirms this (by showing “Filter Catalog” in the top right).
Am I missing something? To we need to each make videos to compare?

Hmm…. it’s a problem specifically with opening Quicklook
Try this:

Call up QS
Type DL/ to get into ~/Downloads
Search for something
Use ⌘Y to open quicklook, then dismiss it again with ⌘Y
Clear with double delete
search for ‘downloads’, it’s not found.

On 27 Jul 2016, at 11:13, Rob McBroom<EMAIL_ADDRESS>wrote:
I can still only search in the same folder.
Hmm. I can’t reproduce it.
Call up Quicksilver
Type DL/ to get into ~/Downloads
Search for something
Clear with ⌫⌫
Search for something else
In step 5, I’m searching the catalog. Hitting ↓ to show the results list confirms this (by showing “Filter Catalog” in the top right).
Am I missing something? To we need to each make videos to compare?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/quicksilver/Quicksilver/issues/1494#issuecomment-235471388, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJLn0_g7nDJ2VqXSWmTf3jiXM6RUKNkks5qZszDgaJpZM4ApZsP.

Oh, yeah. Quick Look. I did try that earlier today before asking. But still, can’t reproduce…
https://dl.dropboxusercontent.com/u/2214419/Quicksilver/QuickLookScope.mov

OK, in that case I’ll debug it.

On 27 Jul 2016, at 12:13, Rob McBroom<EMAIL_ADDRESS>wrote:
Oh, yeah. Quick Look. I did try that earlier today before asking. But still, can’t reproduce…

I'm pulling my hair out to try and debug this. I think it might has something to do with the fact that in QSSearchObjectView the search mode is saved before the quicklook window is opened and then put back to what it was once it's closed. (search for savedSearchMode in QSSearchObjectView.m) but I still can't figure out what's wrong.
Can you compare your settings to mine?
https://www.dropbox.com/s/pvlmjgbnlwipiq8/P-Quicklook.mov?dl=0

Can reproduce with @pjrobertson steps above. It seems the scope isn't restored after 4, so you're still browsing ~/Downloads (hence searching for it doesn't return anything). Just reading at the code, I'm suspecting that opening the QL panel triggers -resignFirstResponder, which clears the search string but not the "scope".

My money was on “Show other results”, but we both use “Never”. I notice your results say “Filter Catalog”, but clearly don’t mean it.
Hold the phone… I have good news and bad news. The bad is that I wasted your time. I wasn’t running from master. I was using my personal testing build. The good news is that this is “fixed” (assuming this behavior was wrong) somewhere. I’ll try to figure out what did it.

Looks like @tiennou got it in the result controller cleanup somewhere.


1.2.0

1.2.0

Coverage increased (+2.9%) to 97.571% when pulling ce04ca605a02b2284d96695afd2c68fa0a036892 on development into 67f7bb178807633323fc3777b1bb73d95176b04f on master.


Silently fails when specifying jpg as output

Running latest Go on Windows 10, specifying
primitive.exe -i file.jpg -o otherfile.jpg -n 100 -v

fails to write the output file with no error, verbose output ends with writing otherfile.jpg.
Switching to -o otherfile.png works.

I see that jpg is not listed in the output formats section in the README, but even so, the program should crash when specifying an unsupported output format

I get the same result, running Ubuntu 14.04 and go version go1.5 linux/amd64.

jpgs seem to work for me but I have the same issue with (not) writing gifs...


clustermesh: Add local systemd-resolve --status wait on External Workload install

Check the status of systemd-resolved after modifying it to use
kube-dns. Wait until kube-dns becomes the current DNS server. This should
mitigate errors like this in the CI:
Verify cluster DNS on VM

Run gcloud compute ssh cilium-cilium-2158039822-vm --zone us-west2-a \
 gcloud compute ssh cilium-cilium-2158039822-vm --zone us-west2-a \
    --command "nslookup -norecurse clustermesh-apiserver.kube-system.svc.cluster.local"
...
Server:		<IP_ADDRESS>
Address:	<IP_ADDRESS>#53

** server can't find clustermesh-apiserver.kube-system.svc.cluster.local: NXDOMAIN

Error: Process completed with exit code 1.

Signed-off-by: Jarno Rajahalme<EMAIL_ADDRESS>

Looks good to me. Can you fix the conflicts?


Error while building for OS X: "/usr/local/go/pkg/tool/linux_amd64/cgo: exit status 2"

Hi,
I'm encountering this problem on Debian Wheezy stable:
Checking docker installation...

Cross compiling github.com/kabukky/journey...
Fetching dependencies...
Fetching github.com/kabukky/journey...
Compiling for linux/amd64...
Compiling for linux/386...
Compiling for linux/arm...
Compiling for windows/amd64...
Compiling for windows/386...
Compiling for darwin/amd64...
go build github.com/mattn/go-sqlite3: /usr/local/go/pkg/tool/linux_amd64/cgo: exit status 2
Compiling for darwin/386...
go build github.com/mattn/go-sqlite3: /usr/local/go/pkg/tool/linux_amd64/cgo: exit status 2

It worked fine in a previous version of xgo (I had to create a new VM so I installed the latest xgo version today).
The Windows and Linux binaries are compiling fine.

Just a heads up: It works fine on my other Debian Wheezy VM that I set up a few weeks ago, even after doing a fresh
docker pull karalabe/xgo-latest

Here's the output:
Checking docker installation...

Cross compiling github.com/kabukky/journey...
Fetching dependencies...
Fetching github.com/kabukky/journey...
Compiling for linux/amd64...
Compiling for linux/386...
Compiling for linux/arm...
Compiling for windows/amd64...
Compiling for windows/386...
Compiling for darwin/amd64...
Compiling for darwin/386...
Moving binaries to host...

The interesting thing is that in the first instance (the failing one) Go tries to cross compile with the linux toolchain for osx, whicn obviously won't work. Though I've no clue why it would do that. I'll try and look at it a bit later.

Ok, I think I know what the issue was. Docker uses fairly new CPUs to build the images, and the OSX build tools are compiled while building the images. So the OSX cross compilers will actually use fairly modern CPU instructions, which will fail if running (the cross compilation) on an old CPU. Apart from some black magic restrictions to limit the CPU feature set allowed, the only way around this is to build the containers locally on your own machine, which will circumvent the issue.

I'm encountering this exact same issue: building for OS X fails without much detail.
 $ xgo --targets=darwin/* github.com/mattn/go-sqlite3/_example/simple
Checking docker installation...
Client:
 Version:      1.8.2
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   0a8c2e3
 Built:        Thu Sep 10 19:19:00 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.8.2
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   0a8c2e3
 Built:        Thu Sep 10 19:19:00 UTC 2015
 OS/Arch:      linux/amd64

Checking for required docker image karalabe/xgo-latest... found.
Cross compiling github.com/mattn/go-sqlite3/_example/simple...
Fetching main repository github.com/mattn/go-sqlite3/_example/simple...
github.com/mattn/go-sqlite3 (download)
Compiling for darwin/amd64...
go build github.com/mattn/go-sqlite3: /usr/local/go/pkg/tool/linux_amd64/cgo: exit status 2
2015/10/21 22:31:24 Failed to cross compile package: exit status 1.

Similar to @kabukky, building for windows/linux works just fine.

Apart from some black magic restrictions to limit the CPU feature set allowed, the only way around this is to build the containers locally on your own machine, which will circumvent the issue.
@karalabe

I'm attempting this workaround right now... It's going to take a while on my sad little laptop, so I figured I'd report this while I waited. Keeping my fingers crossed!
Your xgo project is a huge lifesaver. I'm sincerely grateful for all your work!

Glad it worked :D So, then indeed the issue is that the OSX cross compiler suite in the docker image assembled by docker hub contains newer CPU instructions, that will plain crash on an older CPU. When I find the time, I'll write up a small section about this in the readme so people will be aware and I'll also try to incorporate your detailed writeup about the needed steps. Thanks a lot for taking the time to experiment with the issue and detail the exact steps other might need. Cheers :)

I tried @harrytruong suggestions and darwin builds are now failing with a different error message.
Compiling for darwin/amd64...
WORK=/tmp/go-build348372251
mkdir -p $WORK/github.com/jessevdk/go-flags/_obj/
mkdir -p $WORK/github.com/jessevdk/
mkdir -p $WORK/github.com/pksunkara/cbind/parser/_obj/
cd /go/src/github.com/jessevdk/go-flags
/usr/local/go/pkg/tool/linux_amd64/compile -o $WORK/github.com/jessevdk/go-flags.a -trimpath $WORK -p github.com/jessevdk/go-flags -complete -buildid 64ee345c1d8c958df2a261cc29ac0dc3a4ab6aac -D _/go/src/github.com/jessevdk/go-flags -I $WORK -pack ./arg.go ./closest.go ./command.go ./completion.go ./convert.go ./error.go ./flags.go ./group.go ./help.go ./ini.go ./man.go ./multitag.go ./option.go ./optstyle_other.go ./parser.go ./termsize.go ./termsize_unix.go
mkdir -p $WORK/github.com/pksunkara/cbind/
cd /go/src/github.com/pksunkara/cbind/parser
CGO_LDFLAGS="-g" "-O2" /usr/local/go/pkg/tool/linux_amd64/cgo -objdir $WORK/github.com/pksunkara/cbind/parser/_obj/ -importpath github.com/pksunkara/cbind/parser -- -I. -I $WORK/github.com/pksunkara/cbind/parser/_obj/ parser.go
o64-clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -print-libgcc-file-name
o64-clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -I. -I $WORK/github.com/pksunkara/cbind/parser/_obj/ -g -O2 -o $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_main.o -c $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_main.c
o64-clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -I. -I $WORK/github.com/pksunkara/cbind/parser/_obj/ -g -O2 -o $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_export.o -c $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_export.c
o64-clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -I. -I $WORK/github.com/pksunkara/cbind/parser/_obj/ -g -O2 -o $WORK/github.com/pksunkara/cbind/parser/_obj/parser.cgo2.o -c $WORK/github.com/pksunkara/cbind/parser/_obj/parser.cgo2.c
o64-clang++ -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -I. -I $WORK/github.com/pksunkara/cbind/parser/_obj/ -g -O2 -o $WORK/github.com/pksunkara/cbind/parser/_obj/Bind.cc.o -c ./Bind.cc
o64-clang++ -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -I. -I $WORK/github.com/pksunkara/cbind/parser/_obj/ -g -O2 -o $WORK/github.com/pksunkara/cbind/parser/_obj/cbind.cc.o -c ./cbind.cc
o64-clang++ -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -o $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_.o $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_main.o $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_export.o $WORK/github.com/pksunkara/cbind/parser/_obj/parser.cgo2.o $WORK/github.com/pksunkara/cbind/parser/_obj/Bind.cc.o $WORK/github.com/pksunkara/cbind/parser/_obj/cbind.cc.o -g -O2
/usr/local/go/pkg/tool/linux_amd64/cgo -objdir $WORK/github.com/pksunkara/cbind/parser/_obj/ -dynpackage parser -dynimport $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_.o -dynout $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_import.go
o64-clang++ -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -o $WORK/github.com/pksunkara/cbind/parser/_obj/_all.o $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_export.o $WORK/github.com/pksunkara/cbind/parser/_obj/parser.cgo2.o $WORK/github.com/pksunkara/cbind/parser/_obj/Bind.cc.o $WORK/github.com/pksunkara/cbind/parser/_obj/cbind.cc.o -g -O2 -Wl,-r -nostdlib
/usr/local/go/pkg/tool/linux_amd64/compile -o $WORK/github.com/pksunkara/cbind/parser.a -trimpath $WORK -p github.com/pksunkara/cbind/parser -buildid 35701231d9dfeef99a7d3d46cf8e682c6059d87b -D _/go/src/github.com/pksunkara/cbind/parser -I $WORK -pack $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_gotypes.go $WORK/github.com/pksunkara/cbind/parser/_obj/parser.cgo1.go $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_import.go
pack r $WORK/github.com/pksunkara/cbind/parser.a $WORK/github.com/pksunkara/cbind/parser/_obj/_all.o # internal
mkdir -p $WORK/github.com/pksunkara/cbind/_obj/
mkdir -p $WORK/github.com/pksunkara/cbind/_obj/exe/
cd /go/src/github.com/pksunkara/cbind
CGO_LDFLAGS="-g" "-O2" /usr/local/go/pkg/tool/linux_amd64/cgo -objdir $WORK/github.com/pksunkara/cbind/_obj/ -importpath github.com/pksunkara/cbind -- -I $WORK/github.com/pksunkara/cbind/_obj/ main.go
o64-clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -I $WORK/github.com/pksunkara/cbind/_obj/ -g -O2 -o $WORK/github.com/pksunkara/cbind/_obj/_cgo_main.o -c $WORK/github.com/pksunkara/cbind/_obj/_cgo_main.c
o64-clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -I $WORK/github.com/pksunkara/cbind/_obj/ -g -O2 -o $WORK/github.com/pksunkara/cbind/_obj/_cgo_export.o -c $WORK/github.com/pksunkara/cbind/_obj/_cgo_export.c
o64-clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -I $WORK/github.com/pksunkara/cbind/_obj/ -g -O2 -o $WORK/github.com/pksunkara/cbind/_obj/main.cgo2.o -c $WORK/github.com/pksunkara/cbind/_obj/main.cgo2.c
o64-clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -o $WORK/github.com/pksunkara/cbind/_obj/_cgo_.o $WORK/github.com/pksunkara/cbind/_obj/_cgo_main.o $WORK/github.com/pksunkara/cbind/_obj/_cgo_export.o $WORK/github.com/pksunkara/cbind/_obj/main.cgo2.o -g -O2
/usr/local/go/pkg/tool/linux_amd64/cgo -objdir $WORK/github.com/pksunkara/cbind/_obj/ -dynpackage main -dynimport $WORK/github.com/pksunkara/cbind/_obj/_cgo_.o -dynout $WORK/github.com/pksunkara/cbind/_obj/_cgo_import.go
o64-clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -o $WORK/github.com/pksunkara/cbind/_obj/_all.o $WORK/github.com/pksunkara/cbind/_obj/_cgo_export.o $WORK/github.com/pksunkara/cbind/_obj/main.cgo2.o -g -O2 -Wl,-r -nostdlib
/usr/local/go/pkg/tool/linux_amd64/compile -o $WORK/github.com/pksunkara/cbind.a -trimpath $WORK -p main -buildid 84a9c22e1c580296a9a3f6beaf9d37bd990b4828 -D _/go/src/github.com/pksunkara/cbind -I $WORK -I /go/pkg/darwin_amd64 -pack $WORK/github.com/pksunkara/cbind/_obj/_cgo_gotypes.go $WORK/github.com/pksunkara/cbind/_obj/main.cgo1.go $WORK/github.com/pksunkara/cbind/_obj/_cgo_import.go
pack r $WORK/github.com/pksunkara/cbind.a $WORK/github.com/pksunkara/cbind/_obj/_all.o # internal
cd .
/usr/local/go/pkg/tool/linux_amd64/link -o $WORK/github.com/pksunkara/cbind/_obj/exe/a.out -L $WORK -L /go/pkg/darwin_amd64 -extld=o64-clang++ -buildmode=exe -buildid=84a9c22e1c580296a9a3f6beaf9d37bd990b4828 -s -extldflags -static $WORK/github.com/pksunkara/cbind.a
# github.com/pksunkara/cbind
/usr/local/go/pkg/tool/linux_amd64/link: running o64-clang++ failed: exit status 1
ld: warning: option -s is obsolete and being ignored
ld: library not found for -lcrt0.o
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Btw, I've pushed a osx wrapper fix that should now avoid any native CPU optimisations (i.e. it shoulnd't fail with illegal instruction errors any more). The updates are still building.

@karalabe So, we should rebuild our xgo again from our local repo? Or can we use docker's directly?

I just confirmed that I was able to build @pksunkara's cbind test repo by (1) using my locally built docker image, and also by (2) using @karalabe's latest docker image.
@pksunkara -- try again with the latest docker image? make sure you run docker pull karalabe/xgo-latest first, before running your usual xgo command.
I'm testing the latest docker image against my personal projects now... will report back later. Great work @karalabe!

@harrytruong There seem to be some very strange quirk with running docker on osx. I've got a separate report too about linker errors like the one reported in here, but they never occur on my machine, only reported by people running docker on osx. Also that error (that -s is not recognized) isn't produced by the linux ld, as the gnu ld supports it. So i'm a bit puzzled how the wrong ld is called, or even where the wrong ld comes from.

@harrytruong Weird. I will try again using the latest master branch of xgo and report back. By the way, I am using docker on Ubuntu 15.10. Not OS X.

@pksunkara Really? I'm sorry, don't know where I saw darwin. Could you try and report back on your results?

@karalabe Rebuilt the xgo image from this repository. This is the error I am getting:
My system: ubuntu 15.10
pksunkara@codecave [~] #18  →  xgo --image=xgo -ldflags='-extldflags "-static"' -targets='darwin/*' -x github.com/pksunkara/cbind
Checking docker installation...
Client:
 Version:      1.8.3
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   f4bf5c7
 Built:        Mon Oct 12 05:42:26 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.8.3
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   f4bf5c7
 Built:        Mon Oct 12 05:42:26 UTC 2015
 OS/Arch:      linux/amd64

Checking for required docker image xgo... found.
Cross compiling github.com/pksunkara/cbind...
Fetching main repository github.com/pksunkara/cbind...
github.com/pksunkara/cbind (download)
github.com/jessevdk/go-flags (download)
Compiling for darwin-10.6/amd64...
WORK=/tmp/go-build695569170
mkdir -p $WORK/github.com/jessevdk/go-flags/_obj/
mkdir -p $WORK/github.com/jessevdk/
cd /go/src/github.com/jessevdk/go-flags
/usr/local/go/pkg/tool/linux_amd64/compile -o $WORK/github.com/jessevdk/go-flags.a -trimpath $WORK -p github.com/jessevdk/go-flags -complete -buildid 64ee345c1d8c958df2a261cc29ac0dc3a4ab6aac -D _/go/src/github.com/jessevdk/go-flags -I $WORK -pack ./arg.go ./closest.go ./command.go ./completion.go ./convert.go ./error.go ./flags.go ./group.go ./help.go ./ini.go ./man.go ./multitag.go ./option.go ./optstyle_other.go ./parser.go ./termsize.go ./termsize_unix.go
mkdir -p $WORK/github.com/pksunkara/cbind/parser/_obj/
mkdir -p $WORK/github.com/pksunkara/cbind/
cd /go/src/github.com/pksunkara/cbind/parser
CGO_LDFLAGS="-g" "-O2" /usr/local/go/pkg/tool/linux_amd64/cgo -objdir $WORK/github.com/pksunkara/cbind/parser/_obj/ -importpath github.com/pksunkara/cbind/parser -- -I. -I $WORK/github.com/pksunkara/cbind/parser/_obj/ parser.go
o64-clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -print-libgcc-file-name
o64-clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -I. -I $WORK/github.com/pksunkara/cbind/parser/_obj/ -g -O2 -o $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_main.o -c $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_main.c
o64-clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -I. -I $WORK/github.com/pksunkara/cbind/parser/_obj/ -g -O2 -o $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_export.o -c $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_export.c
o64-clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -I. -I $WORK/github.com/pksunkara/cbind/parser/_obj/ -g -O2 -o $WORK/github.com/pksunkara/cbind/parser/_obj/parser.cgo2.o -c $WORK/github.com/pksunkara/cbind/parser/_obj/parser.cgo2.c
o64-clang++ -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -I. -I $WORK/github.com/pksunkara/cbind/parser/_obj/ -g -O2 -o $WORK/github.com/pksunkara/cbind/parser/_obj/Bind.cc.o -c ./Bind.cc
o64-clang++ -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -I. -I $WORK/github.com/pksunkara/cbind/parser/_obj/ -g -O2 -o $WORK/github.com/pksunkara/cbind/parser/_obj/cbind.cc.o -c ./cbind.cc
o64-clang++ -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -o $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_.o $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_main.o $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_export.o $WORK/github.com/pksunkara/cbind/parser/_obj/parser.cgo2.o $WORK/github.com/pksunkara/cbind/parser/_obj/Bind.cc.o $WORK/github.com/pksunkara/cbind/parser/_obj/cbind.cc.o -g -O2
/usr/local/go/pkg/tool/linux_amd64/cgo -objdir $WORK/github.com/pksunkara/cbind/parser/_obj/ -dynpackage parser -dynimport $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_.o -dynout $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_import.go
o64-clang++ -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -o $WORK/github.com/pksunkara/cbind/parser/_obj/_all.o $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_export.o $WORK/github.com/pksunkara/cbind/parser/_obj/parser.cgo2.o $WORK/github.com/pksunkara/cbind/parser/_obj/Bind.cc.o $WORK/github.com/pksunkara/cbind/parser/_obj/cbind.cc.o -g -O2 -Wl,-r -nostdlib
/usr/local/go/pkg/tool/linux_amd64/compile -o $WORK/github.com/pksunkara/cbind/parser.a -trimpath $WORK -p github.com/pksunkara/cbind/parser -buildid 35701231d9dfeef99a7d3d46cf8e682c6059d87b -D _/go/src/github.com/pksunkara/cbind/parser -I $WORK -pack $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_gotypes.go $WORK/github.com/pksunkara/cbind/parser/_obj/parser.cgo1.go $WORK/github.com/pksunkara/cbind/parser/_obj/_cgo_import.go
pack r $WORK/github.com/pksunkara/cbind/parser.a $WORK/github.com/pksunkara/cbind/parser/_obj/_all.o # internal
mkdir -p $WORK/github.com/pksunkara/cbind/_obj/
mkdir -p $WORK/github.com/pksunkara/cbind/_obj/exe/
cd /go/src/github.com/pksunkara/cbind
CGO_LDFLAGS="-g" "-O2" /usr/local/go/pkg/tool/linux_amd64/cgo -objdir $WORK/github.com/pksunkara/cbind/_obj/ -importpath github.com/pksunkara/cbind -- -I $WORK/github.com/pksunkara/cbind/_obj/ main.go
o64-clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -I $WORK/github.com/pksunkara/cbind/_obj/ -g -O2 -o $WORK/github.com/pksunkara/cbind/_obj/_cgo_main.o -c $WORK/github.com/pksunkara/cbind/_obj/_cgo_main.c
o64-clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -I $WORK/github.com/pksunkara/cbind/_obj/ -g -O2 -o $WORK/github.com/pksunkara/cbind/_obj/_cgo_export.o -c $WORK/github.com/pksunkara/cbind/_obj/_cgo_export.c
o64-clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -I $WORK/github.com/pksunkara/cbind/_obj/ -g -O2 -o $WORK/github.com/pksunkara/cbind/_obj/main.cgo2.o -c $WORK/github.com/pksunkara/cbind/_obj/main.cgo2.c
o64-clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -o $WORK/github.com/pksunkara/cbind/_obj/_cgo_.o $WORK/github.com/pksunkara/cbind/_obj/_cgo_main.o $WORK/github.com/pksunkara/cbind/_obj/_cgo_export.o $WORK/github.com/pksunkara/cbind/_obj/main.cgo2.o -g -O2
/usr/local/go/pkg/tool/linux_amd64/cgo -objdir $WORK/github.com/pksunkara/cbind/_obj/ -dynpackage main -dynimport $WORK/github.com/pksunkara/cbind/_obj/_cgo_.o -dynout $WORK/github.com/pksunkara/cbind/_obj/_cgo_import.go
o64-clang -I . -fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common -o $WORK/github.com/pksunkara/cbind/_obj/_all.o $WORK/github.com/pksunkara/cbind/_obj/_cgo_export.o $WORK/github.com/pksunkara/cbind/_obj/main.cgo2.o -g -O2 -Wl,-r -nostdlib
/usr/local/go/pkg/tool/linux_amd64/compile -o $WORK/github.com/pksunkara/cbind.a -trimpath $WORK -p main -buildid 84a9c22e1c580296a9a3f6beaf9d37bd990b4828 -D _/go/src/github.com/pksunkara/cbind -I $WORK -I /go/pkg/darwin_amd64 -pack $WORK/github.com/pksunkara/cbind/_obj/_cgo_gotypes.go $WORK/github.com/pksunkara/cbind/_obj/main.cgo1.go $WORK/github.com/pksunkara/cbind/_obj/_cgo_import.go
pack r $WORK/github.com/pksunkara/cbind.a $WORK/github.com/pksunkara/cbind/_obj/_all.o # internal
cd .
/usr/local/go/pkg/tool/linux_amd64/link -o $WORK/github.com/pksunkara/cbind/_obj/exe/a.out -L $WORK -L /go/pkg/darwin_amd64 -extld=o64-clang++ -buildmode=exe -buildid=84a9c22e1c580296a9a3f6beaf9d37bd990b4828 -s -extldflags -static $WORK/github.com/pksunkara/cbind.a
# github.com/pksunkara/cbind
/usr/local/go/pkg/tool/linux_amd64/link: running o64-clang++ failed: exit status 1
ld: warning: option -s is obsolete and being ignored
ld: library not found for -lcrt0.o
clang: error: linker command failed with exit code 1 (use -v to see invocation)

2015/11/05 16:03:46 Failed to cross compile package: exit status 2.

I have even tried adding the flag --go=1.5.1 and also changing targets to darwin-10.9/amd64. Both are giving the same error.

@pksunkara Remove -ldflags='-extldflags "-static"', there is no static version of crt0.o.

@karalabe I understand that. But I want to build a static binary for darwin. Can we make xgo do that?

"Apple does not support statically linked binaries on Mac OS X. A statically linked binary assumes binary compatibility at the kernel system call interface, and we do not make any guarantees on that front. Rather, we strive to ensure binary compatibility in each dynamically linked system library and framework." ~Apple Developer Website

@pksunkara Remove -ldflags='-extldflags "-static"', there is no static version of crt0.o.

I ran into this issue, but how can i build static binaries for everything except darwin within a single xgo call?


Feature/Add Sharepoint graphSearchQuery function

Add Sharepoint graphSearchQuery function

📦 Published PR as canary version: Canary Versions

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>

:rocket: PR was released in<EMAIL_ADDRESS><EMAIL_ADDRESS>:rocket:


New post: production code coverage

closes https://github.com/caarlos0/w/issues/1

👏 👏 👏

Random websites are failing the SSL check. Dunno why. Should be some temporary thing, merging anyway.

https://carlosbecker.com/posts/production-code-coverage-jacoco/ +)


What does "archive all checked tasks" really do?

There's a settings toggle to "archive all checked tasks".
But examples shown on the setting suggest it will archive all checked tasks that signify an "end state" (i.e., done, cancelled, delegated, etc.).
So my question is, will this option archive a task marked, for instance, as "[/]" (i.e., in progress), or "[b]" (i.e., bookmark?
Ideally, it would be possible for a user to specify which special characters trigger the archiving operation, but I don't see that in the settings.

You can define which chars trigger archiving by creating a rule like so:

Thanks very much. That'll work fine for me.


On traffic lights, what units are the min/max times in?

Game ticks? Milliseconds? Seconds? Days?
Wiki doesn't seem to define the units, nor does the UI.

1 unit equals 64 game ticks.

I suspect most end-users will think more in terms of real-life seconds.
Would it be possible to estimate the number of seconds for the entered value and display it alongside the setting?
Or, better, have user input number of seconds and the mod works out, for current speed setting and fps, etc., how many game ticks that equates to (ie. silently converts from RL seconds to game ticks in the background at the instant the user updates the value).

Time values should not depend on simulation speed. This would force players to continually increase the times to account for degradation in simulation speed that occurs due to city growth. Ticks are the in-game time resolution, not frames/seconds. For example, a vehicle with a certain velocity travels the same distance given a fixed number of ticks. Simulation speed not only depend on ticks but on the player's system performance and city progress.


Adding a custom coder test

This test has been ported from an internal Dataflow test to a general test in Beam.
r: @boyuanzz

Ah dang we don't have tests... that's terrible. FWIW, this passes :beam-sdks-java-core:check and :beam-runners-direct-java:needsRunnerTests.

Currently these tests will run only over direct runner, but should be enabled to run on the ULR, which should give the test coverage we're looking for.

Run Java PreCommit

Run Gradle Publish

gradle rat failed: https://scans.gradle.com/s/nzwfwj6iqlgrg/console-log?task=:rat

@boyuanzz you ran gradle publish before I added the license. The newest precommit already runs rat, and it passed.

friendly ping for review!

@boyuanzz


Dev build running into multiple issues.

 However, coming across this turbo repo, I was able to fall into some issues.
docker compose VS docker-compose
First of all docker command on Mac seems like does not have compose command available, so it's docker-compose that needs to be run instead.

Posgresql instructions

Seems unclear to set up postgresql db as the readme doesn't state what is to be used as creds – default postgres user is run on docker compose up command.
then, this command, that i have not solved yet:

altough permission denied error is a common warning to fix, what seems confusing to me is that all apps from docker-compose.yaml – db, api, web seem to be second version of themselves – api-1, db-1, web-1 – correct me if wrong.
What's the easiest spin up of this turbo repo without extra work?

make sure that you are using most recent version of Docker. Instead of docker-compose it is using docker compose (without hyphen)
regarding postgres, there should be no extra steps to configure it. Maybe it is because you are using older version of Docker on Mac. Sometimes playing with "Choose file sharing implementation for your containers" in your Docker settings helps.


Add HTTP Basic Auth

Implement this

Here's how you add HTTP Basic Auth with caddy as a reverse proxy to localhost:11434, and also handle HTTPS automatically:

Install caddy# Mac, Linux
curl https://webi.sh/caddy | sh

# Windows
curl.exe https://webi.ms/caddy | powershell

Put your password (which could be an API Token) in a password.txt
Digest the passwordcaddy hash-password < ./password.txt

Put the username and digest in an ENV file
caddy.env:BASIC_AUTH_USER='apitoken'
BASIC_USER_AUTH='$2a$14$sI1j0RbhzKHMZ4cHU8otHOkB3Dgl9egF2D.CXB6C0/Qk5dtaMHS/u'

Create a Caddyfile with basic auth using the ENVsapi.example.com {
    handle /* {
        basicauth {
            {env.BASIC_AUTH_USERNAME} {env.BASIC_AUTH_DIGEST}
        }
        reverse_proxy localhost:11434
    }
}

Run caddycaddy run --config ./Caddyfile --envfile ./caddy.env

And if you want to run it as a system service, or without HTTPS or need other details, I've got a bunch of snippets up at https://webinstall.dev/caddy.

Originally posted by @coolaj86 in https://github.com/jmorganca/ollama/issues/849#issuecomment-1773697189

Sorry wrong repo


Validating master merge to wasm.simd against CI

This PR is to validate the merge of master to wasm.simd branch against Jenkins CI in preperation of updating wasm.simd.

Please ignore this PR

closing this PR.


Allow setting favicon in a theme

Is your feature request related to a problem? Please describe.
I'd like to be able to specify a custom favicon image from within a theme. This image would override the default DSpace favicon.
Describe the solution you'd like
I expect there would be two steps to this:

Place the custom favicon.ico image in the /images directory of the active theme
Specify the path to the new favicon image in a way that it replaces the default favicon path

Step 2 could be omitted if an automated step were added which looked for a file named favicon.ico in the active theme and either replaced the default favicon image or updated the favicon path to point to this image.
Describe alternatives or workarounds you've considered
The current work-around is to place the favicon image in the theme, then update the top-level index.html value to change:
<link rel="icon" type="image/x-icon" href="assets/images/favicon.ico" />

to:
<link rel="icon" type="image/x-icon" href="/assets/<my-theme>/images/favicon.ico" />

This method is effective, it simply breaks the theme model by requiring changes to the look of a site to be made outside of the active theme.
Additional context
Add any other context or screenshots about the feature request here.

@artlowel : Per today's meeting, assigning you/your team to work on and adding your 4hr estimate.

@tdonohue I've looked into this in more detail now, and I'd like to change my estimate to 8 hours. The reason is that instead of just adding support for a single favicon.ico file, I'd like to include more high res icons for iOS and Android, or SVG favicons for browsers that support it. This means adding multiple configurable tags per theme to the <head> instead of just one hardcoded one. I'd also like to apply the extends mechanism for themes we added in 7.1 to favicons as well.

Sounds fine, @artlowel .  Thanks for the update.  Bumping this up to 8hrs then.


[SP-3520] Backport of PDI-14625 - Different behavior of spoon when cr…

[SP-3520] Backport of PDI-14625 - Different behavior of spoon when creating duplicate database connections in repository (6.1 Suite)

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f ui/build.xml clean-all resolve jacoco && ant -f ui/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  ui/src/org/pentaho/di/ui/spoon/delegates/SpoonDBDelegate.java

License header violations

:heavy_exclamation_mark: Copyright year is not the current year on ui/src/org/pentaho/di/ui/spoon/delegates/SpoonDBDelegate.java. Found 2013. Was expecting 2017

@stanislau-strelchanka please fix license header

@mchen-len-son thanks, updated


Update Main.hx

Added BAE shape render and parameterized as much of the numbers i could see 8-S

Because of merge conflict, just committed by hand


Replaced Result with scala.util.Try

scala.util.Try can be used instead of com.gilt.aws.lambda.Result.

That looks reasonable, the sealed trait we're using looks isomorphic to Try. Thanks for the PR!


Autofocus on the popup password field

For the individual tiddler (i.e not the plugin panel), clicking the lock icon so the popup shows, should also set focus on it so one can type right away.

I'm not sure how to implement it, but definitively a good idea.


Use classes and objects in Kotlin: Android Basics with Compose

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-compose-classes-and-objects?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-compose-unit-2-pathway-1%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-compose-classes-and-objects#6
In which task and step of the codelab can this issue be found?
Override superclass methods from subclasses
Describe the problem
The word "method" in this line ("To provide this device-specific behavior, you need to override the turnOn() and turnOff() method defined in the superclass.") should be plural. This is the second line of the section
Steps to reproduce?

Go to URL of the codelab
Scroll to Override superclass methods from subclasses section
Check the word "method" in the second line of the first paragraph

Versions
Android Studio version:  NA
API version of the emulator: NA
Additional information

Hi @Kalyan19111999
Thank you for writing in and bringing this issue to our attention.
The lesson has been updated to address it and the revised lesson will be republished again in the near future.
Hope you are enjoying the course!
Regards.


iOS Blue links for dates and times

How can we reproduce this bug?
Dates and times on iOS become hidious blue regardless of the base link color. Let's fix that :)
This article has a great snippet in it that prevents that, can we do this or something similar by default in F4E?
http://blog.emailwizardry.co/2016/04/the-absolute-easiest-way-to-beat-blue-links-in-emails-on-ios/

Encountered the same issue. Unfortunately I don't think this is an issue with foundation-emails but rather that a helper should be provided.
I created this helper...
// iOS hack to ensure its 'smart' linking doesn't mess our styles
@media only screen {
  .unlink {
    a {
      color: inherit;
      text-decoration: inherit;
    }
  }
}

Then on the container element of the text that is causing the problem, simply add a class unlink and it will take care of the rest.
For example... 09:00 will become 09:00. The great advantage of this approach is that if you've got large blocks of text that you don't want styled, it works on that as well. This is needed for things such as addresses, 'Today', dates, times, websites without links (your brand might be SomeBrand.com but don't want to link it for some reason).

@davidhouweling Do you think the link @zurbrandon added above would do the trick as well? Looking for a universal reset that we can add to the framework.

I just had a scenario where my designer wanted me to leave in the iPhone smart linking for 1 specific scenario. So really we would need to have a way to stop it from doing it as well? However, the way it is outlined in the link (instead of my approach), there is not a way for you to pick and choose.

Another thing worth considering is that Gmail also adds links to dates and addresses and I don't think those would be addressed with the CSS in the link that @zurbrandon included.

Have you tried using meta tags to disable these:

Here is a fix:
add the following to a custom sass file:
`/* uncss:ignore */
@media screen {
a[x-apple-data-detectors] {
color: inherit !important;
text-decoration: none !important;
font-size: inherit !important;
font-family: inherit !important;
font-weight: inherit !important;
line-height: inherit !important;
}
}
/* this rule will be ignored */`
Thanks to http://removebluelinks.com


Pressing Cmd+S with inline chat active should accept it and save the document

create code with inline chat
press cmd+s
you get the save consent message

IMO it would be OK to treat saving as consent

You get a prompt once but basically this is how it now works


update rust secret connection to match golang

Note this is untested, since for some reason integration.rs isn't compiling on my machine.

The second commit adds a file of test vectors for "derive_secrets_and_challenge".
The format is Hex(diffie_hellman secret),loc_is_least,Hex(expected_recv_secret),Hexx(expected_send_secret),Hex(expected_challenge)

Note this is untested, since for some reason integration.rs isn't compiling on my machine.

My understanding is that integration.rs doesn't compile because it includes rpc.rs (via include!("../src/rpc.rs")) which itself depends on types::* and its dependencies. We'd need to properly import it as a module. Was there a version in the code where this actually worked?

It should work on master

The only reason this previously worked on master is that rpc.rs didn't use the types module, it does in this PR (see the changes in rpc.rs). We still need to restructure this.


Clean up: protocol

MINOR changes:

improved instructions
establish alphabetical order within a property

MAJOR changes:
none
SPECIAL ATTENTION:
none
CHANGELOG:

describedIn links to WebResource instead of URL
replaced link to technique for relevantFor with new category technique (which includes techniques, analysisTechniques and stimulationTechniques); see https://github.com/HumanBrainProject/openMINDS_controlledTerms/pull/393

@apdavison OR @Peyman-N feel free to merge if you also approve

@aeidi89 feel free to merge if you also approve


Add DateTime, Timer, Duration & Instant

This significantly extends the time module with a proper, somewhat thought through design of how to work with time in Acton.
I think a lot of Python code uses datetimes to compute timedeltas when they really should be using monotonic time. It's a haphazard design, probably because things have been built over time. Many other languages place a much stronger emphasis on the difference between measuring elapsed time and telling wall clock time. Rust has Instants and Durations. Those are the basic classes I copied here but I think Zig did a much better job of wrapping that up in a user friendly interface. They call it a Timer. We have a Timer now too. Compare:
t1 = time.Instant.now()
t2 = time.Instant.now()
diff = t2 - t1
print("Elapsed time:", diff)

With a Timer, which I think is more intuitive:
t = Timer()
print("Elapsed time:", t.elapsed())

Many things are not implemented, like Calendars, Clocks, Precision or Timezones but we have the basic structure of it. A lot of inspiration from Swift, though they seem to have a needlessly complicated solution. I'd like to strike a balance of their expressiveness but avoiding boilerplate code.
There are various bugs in the compiler or language shortcomings (no u64 for example) so there are a few workarounds in the code that we need to sort out but the overall module design is pretty set I think.

These are some of my thoughts and considerations going into this

design for correctness but also something that's easy to use

I like progression, like simple interface perhaps with implied defaults (reading your locale)!?, for doing common things, but if you need more flexibility, then you add more information (which you then have to understand, like different Calendar or computing between timezones)
this way, users are not forced to research all 13 arguments up front but can get a naive implementation right away in a simple way

big question around split between wall clock and elapsed time, like this means users have to know up front if they are going to use a timestamp for logging or for measuring elapsed time and use the right functions

I've chosen a separation between wall clock time and elapsed time

to correctly measure elapsed time, one should use a monotonic clock, clearly for wall clock one should read from ... the wall clock (real clock)
while Python has monotonic time available (there is clock_gettime from C wrapped), I think a lot of Python code uses two datetimes (which are read from wall clock) to compute timedeltas. This is wrong and bad but it's how a lot of Python code looks, I think... I'd like to have an interface that encourages users to do the right thing
most fast languages with high precision timing use monotonic time for measuring elapsed time and make a clear distinction between monotonically measured durations vs wall clock

clock_gettime in C with monotonic
Rust has Instant & Duration times which are only for measuring elapsed time, then separate datetime stuff for wall clock
Zig wraps it up in what they call a Timer, I think this is genius because it naturally leads users to use the right thing
Go has an interesting compromise where getting a Time gets you both a monotonic timestamp and wall clock time, for subtraction (i.e. computing duration) it compares the monotonic times only

I've adopted the Timer idea from Zig. I think it's genius as it naturally leads users into using the right thing. What do you use to measure elapsed time? A timer of course!
otherwise, the standard way is to get timestamp t1 and t2 then subtract to get the diff, which you can obviously do regardless if you grab those timestamps from a monotonic or real clock, but yeah, I think the Timer interface invites you to do the right thing
calendars are complex, converting from a seconds-from-unix-epoch to year, month, day etc is a really hard problem and in particular if we want support for more than gregorian calendar
Swift is very ambitious and gets this seemingly correct, however the interface isn't super inviting (or maybe I'm not used enough to Swift and their documentation - it looks messy)
we have these more basic classes, like how to represent a point in time / timestamp? with a split between monotonic and real clock, should they be comparable? if we also keep track of which clock we got the timestamp from, we can make them not comparable
keeping track of clock, not just by name but by some "id", we could also use this for detecting if an actor which has a timestamp is migrated

like if an actor takes monotonic timestamp t1 while running on RTS node 1, then gets migrated to RTS node 2 and takes monotonic timestamp t2, those are likely going to be wildly different so computing a duration from t2-t1 is going to be incorrect
for such a case, the real clock is actually better to produce the duration since they are going to be reasonable in sync between computers, but suddenly the precision falls from nanosecond level to probably around milliseconds

should such a comparison throw an exception? or do we signal the precision in the produced result? say a function was repeatedly called, it means you could get thousands of iterations where the timestamp is nanosecond precision, then there's an actor migration and suddenly you get a timestamp with millisecond precision, good or not?

a user that cares about precision could always inspect the result object, or we could perhaps have an argument to Timer saying that we want minimum X precision, so that normally it just gives you the best it can (which would be ~millisecond sometimes) but if you said "I want microsecond precision) then it will throw an exception after an actor migration... or maybe if we get a handle on how good our time source is (maybe all computers are PTP synchronized) then you'd get that precision

the high level objects are different, like Timer vs DateTime, but the lower level, like Instant (which is what we call our timestamp / point in time) can be reused, but should we?
Instant holds seconds as int64 and attoseconds as u64, gives us range of +-2800 billion years and attoseconds is 1*10^-18
actually, all are int now, but we should change once i64 is a sub-type of int!?
the wide range and high precision means these classes can be used for a wide range of computations, like short time scale scientific work as well as things on a very long time scale - pretty cool I think
obviously comes at a cost in performance - we could offer lower precision classes as well for someone that cares about that, like CoarseInstance?
to convert an Instant to a calendar time, we need to know according to what calendar, so we need calendar information
Swift seems to do this very correctly and I feel our ambition should be on par, but for now we take shortcuts  (I added a Calendar class but it's empty)

Feel free to comment. If you think the whole thing is rubbish, feel free to start over and make a completely separate proposal :)
We are nowhere near Acton 1.0, so this is by no means frozen. We have plenty of opportunity to make changes, but naturally as we start using this module in other places, changing it is going to hurt, so better get the broad strokes correct at least :)

Also, the deadline to feedback on this proposal isn't really for this pull request. I'd like to merge something fairly soon as I have other modules that depend on this and I want something that works, but we can totally change all of this after this PR is merged too... and there's also a point in merging this because there are some bugs I'd like @nordlander to be able to easily work on which are exposed by this code.

I like the idea, separating durations from wall clock time is spot on. And the complexity of calendars can of course be dealt with in due time.
We might want to ponder a little more on the effect annotations, though. A function/method that measures its execution time can't be pure, so we should turn those into mut or proc. But a more philosophical issue concerns whether a computation without any links to the outside world should still be able to observe the speed of the platform on which it executes, and thus give different results for different runs despite having no environment dependencies. The pragmatist in me says "why not?", but I also see the risk that we might regret this someday when it stops some desireable compiler optimization from being applied. Anayway, there's nothing wrong in revisiting this issue if and when the need arises, so let's not complicate things in advance.
I can imagine that a reset() method could be useful in the Timer class, for the case where the time measurements should start at some specific event that's distinct from when the Timer object was created. And while we're on it, events could be measured even more precisely if we somehow could get hold of the baseline that the rts maintains for each actor message. The baselines for external events are set as close to their actual occurrence as possible, so they are independent of the time the corresponding message has to wait before actually being scheduled. (This "platform independent timing" concept was actually one of the main cornerstones of Timber language I used to work on, together with an accompanying notion of event deadlines.)

I'll take a look at the bug that stops the outcommented code, of course.

@nordlander what do you think of Go's Time that stores both a monotonic time and the real clock? I'm sort of leaning towards that since it allows Timer() to work even after actor migration between machines. The result is much lower precision, but that could be OK (needs to be indicated though).

@plajjan That seems like a good idea, although I'm not really aware of the details.

@nordlander Go captures two timestamps (monotonic & real clock) in their Time structure so that when you do subtraction to get elapsed time that happens on the monotonic part etc. Quite clever. However, it doesn't go all the way for Acton since we can migrate actors. The monotonic clock does not have a known start time so it cannot be used for comparison with anything besides itself and only during the same boot. I have now implemented support for this in the Acton time module (I just pushed a new commit). An Instant is still only one measurement, but since we have the Timer class, that is a very natural place to do this, so it now holds both monotonic and real clock time. It will prefer using the monotonic time, when possible, but if that's incomparable it will fall back to real clock. It does this by track which Clock a Instant is from. The Clock has both a type (monotonic vs real and also "unknown" for naive timestamps) and an "instance id" where the instance (maybe it should be called incarnation?) is in practice the boot-id, like if we reboot a machine, this gets reset. On Linux we can get the boot_id while on other platforms (macos) we can't, so the monotonic clock will only be useful within the same Acton RTS invocation. I want to somehow expose the precision and accuracy of these clocks too...
I also added a PTimer which only relies on monotonic time for measuring elapsed time. If the monotonic clock is incomparable, it will instead fail, so for anyone writing precision sensitive applications this would be the way to go.

 Rust had a CVE around this if someone was mucking with env vars while running localtime_r or somesuch. What a mess.

I've dealt quite a bit with timezone aware calculations on the wall clock in Python and found this module to be super logical as a user: https://pendulum.eustace.io/docs/
It defaults to UTC for DateTime, except when calling now() where it defaults to local time, can do conversions between time zones, TZ aware arithmetic, handy helpers on Periods/Durations etc..

@klambrec so I'm not really going much into various conversions, shifting etc right now. Although I've considered a lot of it, I've not spent any time on implementation. That'll come later. I did see pendulum and put it on the reading list for future time related work (#1190). I believe the proposal in this PR is essentially compatible with all those ideas and I think we share certain design traits, like having TZ aware everything per default (unlike Python which is naive in most cases) and making it easy to do the right thing. Pendulum really does nothing for measuring elapsed time, where I think we have a very strong story

I think the UnknownClock should be removed. It's really not "unknown", I gave the example of a timestamp read from a text file would be from an unknown clock, but that's not really true. What we mean by the realtime clock is a clock that is synchronized to the UTC standard. If it is not in sync it is as uncomparable as any other timestamp... what the "type" of the clock really means is which time standard it uses and having it be in sync is a criteria for it to be comparable... the question more becomes with what precision / error.

I am going to go ahead and merge this. We can revise things later on, there are some sort of unusual things about this design but I figure it's useful as is, so let's get it merged.


add Shoogle

Hi,
cool and awesome list!
Just want to add one of my major projects which uses Hugo for static site generation.
Have a nice week
midzer

Thanks!


Download windows do not appear

Describe the bug
I have a bug in hydra that does not appear in the download windows I try to download another version and also give this bug
Steps to Reproduce
1 Open Hydra 2 Wait 3 Ready

Expected behavior
that the download windows appear
Additional information and data
logs.txt
Operating System
windos 11
Hydra Version
v3.0.2
Before opening this Issue

[X] I have searched the issues of this repository and believe that this is not a duplicate.
[X] I am aware that Hydra team does not offer any support or help regarding the downloaded games.

Could you upload all your logs file? You uploaded only one. The two most important are info.txt and error.txt in your case. But, upload all files if possible


Only use PHRASE simple syntax in query

The syntax uses a whole bunch of stuff researches might be looking for.
We also don't make this clear anywhere.
https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-simple-query-string-query.html#simple-query-string-syntax
We could do something like Kibana if we wanted to add special syntax.

@alexwlchan any clearer?

Merging, happy to make further changes requests on this PR as and when.


Update dev data and triangulum version

Purpose
Update dev data and triangulum version to optionally load dev data on build.
Testing
clojure -M:build-db build-all --dev-data

README.org
150-151: These lines can now be removed.
155-156: "This will build the proper database functions as well as add some dummy development data to the database." This line can be removed.
165: "since the database has been built," This portion of the sentence can be removed.

150: Can't this line be removed since the call to build-all on line 43 should take care of this?
162: "you only usually only" Remove the extra "only"


chore: fix unaligned navigation bar

chore: fix unaligned navigation bar
What does this PR do?
The icons are not aligned because the "faBookOpen" icon is actually
576x512 and not the usual 512x512, causing the icons to be misaligned.
Inspection of faBookOpen:
<svg aria-hidden="true" role="img" xmlns="http://www.w3.org/2000/svg" class="svelte-fa svelte-fa-base mr-4 svelte-l34xo3" viewBox="0 0 576 512">

This PR modifies the icon size to actually be 512px width to avoid
misalignment
Screenshot / video of UI

Look at the "open book" icons and text vs the ones below
Before:

After:

What issues does this PR fix or reference?

Closes https://github.com/containers/podman-desktop-extension-ai-lab/issues/989
How to test this PR?

See that it has been aligned
Signed-off-by: Charlie Drage<EMAIL_ADDRESS>

@benoitf updated!

fixed formatting (pnpm format:fix), setting as auto-merge now!


refactor(fs): simplify CopyContents

We can simplify the following code
dir, err := os.Open(dirname)
if err != nil {
	return err
}
defer dir.Close()

dirs, err := dir.Readdir(-1)

with just os.ReadDir(dirname)
Reference: https://pkg.go.dev/os#ReadDir

/test

/test all

/lgtm

/approve


Note that AS::Duration.new API differs from ActiveSupport::Duration.new API

I was looking into optionally using AS::Duration instead of ActiveSupport::Duration for Sequel's pg_interval extension, but I found the constructors for the two classes are different, so it is not possible to simply swap ActiveSupport::Duration for AS::Duration.  This difference isn't mentioned in the README, and it probably should be, since the README gives the impression that the 'AS::Duration` is compatible except in cases listed explicitly.
Alternatively, you may want to support ActiveSupport::Duration's constructor API. That would increase compatibility.

Thank you for reporting this. For some reason I assumed that no one would be instantiating ActiveSupport::Duration directly, and later I forgot to mention it in the readme. There was no good reason to change it, I could easily just keep ActiveSupport's one. I released version 0.1.0 with the fix.


Added a temporary landingpage

Please use dashes - instead of spaces in filenames, else we have %20 appearing in URLs.


Skipped Tests with DataProvider appear as failed

TestNG Version
7.7.1
How to reproduce?
Context: I don't want a DataProvider to execute if the test is going to be skipped

Create a TestListener that implements both IDataProviderListener and ITestListener
Override the onTestStart method to skip if certain conditions are matched (ex: the test contains a specific group)
Also override the beforeDataProviderExecution method to skip the DataProvider if the test contains a skip condition
Create a TestFile that uses TestListener as Listener
Add a test with a DataProvider that meets the skip condition
(Optional) Add a test without a DataProvider that meets the skip condition to compare
Run the test/s

Expected behavior
Skipping a test with a DataProvider should skip the test and the DataProvider, the test result should show that the test was Skipped.
The test with the DP and one without it should behave the same, everything should be skipped
Actual behavior
The test with the DataProvider is shown as failed with a SkipException
Is the issue reproducible on runner?

[ ] Shell
[x] Maven
[ ] Gradle
[ ] Ant
[ ] Eclipse
[x] IntelliJ
[ ] NetBeans

Test case sample
Here you have a small IntelliJ project containing a test file with two tests, one has the dumb DataProvider:
https://github.com/jmoreira18/TestNG-DataProvider-issue-demo
Code comments
This part of the code is not taking into account that it could be a SkipException, then it's treating it as a failure and failing the test
boolean bubbleUpFailures =
        m_configuration.isPropagateDataProviderFailureAsTestFailure() || bag.isBubbleUpFailures();

if (throwable instanceof TestNGException || bubbleUpFailures) {
        tr.setStatus(ITestResult.FAILURE);
        m_notifier.addFailedTest(arguments.getTestMethod(), tr);
} else {
        tr.setStatus(ITestResult.SKIP);
        m_notifier.addSkippedTest(arguments.getTestMethod(), tr);
}

Thanks in advance!

@jmoreira18 Would you like to create a pull request for this ? We can help you with review and merge.

@krmahadevan Sure! Sounds cool

@jmoreira18 - Thank you for taking the time to create a PR and contribute. We look forward to more contributions from you :)


Fix: PDF/UA-1 validation: If the table's structure is not determinable via Headers and IDs, then structure elements of type TH shall have a Scope attribute

Source issue: https://github.com/metanorma/xmlgraphics-fop/issues/4
Original issue: https://github.com/metanorma/mn2pdf/issues/292

Done in the branch fix/pdf_ua.


feat(w-timeline): added infusion rate tooltip [SO-2677029]

What feature or fix was requested?
Infusion rate hover tool tip.

Is there any specific condition to reproduce the scenario?
The conditions are mentioned in this PR https://github.com/philips-emr/tasy-framework/pull/23033
After getting the infusion rate hovering on it should show the tool tip.

Which functions have you tested your implementation?
I have checked in demo component for flowsheet should work fine in application as well

As the file is too big to load the difference pasting the changes here


feat(checks/sql): GCP_SQL_006: backups are multi-regional

Codecov Report

Merging #20 (0097c58) into main (cab38d2) will increase coverage by 2.25%.
The diff coverage is 61.90%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main      #20      +/-   ##
==========================================
+ Coverage   16.41%   18.67%   +2.25%
==========================================
  Files          10       10
  Lines         402      423      +21
==========================================
+ Hits           66       79      +13
- Misses        333      341       +8
  Partials        3        3

Impacted Files
Coverage Δ

gcp/sql/sql.go
0.00% <0.00%> (ø)

gcp/sql/sqlConditions.go
89.83% <100.00%> (+2.87%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


GraphQL support

I'm developing an app that exposes a GraphQL API. What would it take to be able to upload my graphql schema when setting up superflows for my app? I'd rather not have to create a REST API just to integrate.

Hi @nloum, thanks so much for reaching out! :smile:
Sadly, we don't support GraphQL yet, although it's on our roadmap
I would be really interested in understanding your usecase better - quite possible it will lead to this being bumped heavily up the priority list, since only 1 other company we've spoken to have explicitly requested GraphQL. If you're happy to, get in touch on Slack or via email - whichever is easier for you :smile:

@nloum, thought I'd bump here - would be great to better understand your usecase & can totally see this being highly prioritised if you do :smile:


DateRangePicker: selecting date less than startDate causes startDate to be cleared

With the default configuration of DateRangePicker, if you select a date, then select an end date that is earlier, the startDate is cleared. From that point onward, you can select ranges spanning backwards in time (as is probably the expected behaviour).
A related quirk (which may be the desired behaviour), is that clicking the same date over and over causes the date to swap (clear startDate and set endDate, and vice versa). Though this does make it impossible to set same-day intervals with the default configuration.

Thanks for pointing that out. The first thing you mention is expected behavior, but the second one isn't.
When you select a start date and go to select an end date, the start date should be disabled. It was like this but I accidentally undid it with a recent change, will update it and add tests for it.
About same-day intervals selection, I will add an option to allow it.

Hey, i also need to be able to select the same Date twice for a single-day selection. Would be very nice if you could add that soon.
Greetings


Node 4 is no longer supported because of a dependency

The debug transitive dependency pulled by (at least) the send dependency dropped support for Node 4. This causes express to no longer support Node 4 as well. This should either be fixed or the minimum version should be bumped to Node 6.
See https://github.com/visionmedia/debug/releases/tag/4.0.0

The send module is not pulling in the 4.0.0 of debug, it pulls in the 2.x line of debug module, which does support Node.js 4.

Yes, sorry about that, it seems it was an older Express version. If anyone else gets this issue, simply update Express.

A brand new install of express shows the versions of the debug module that will be installed from a new installation:
$ $ npm i express
+<EMAIL_ADDRESS>added 50 packages from 47 contributors and audited 119 packages in 4.173s
found 0 vulnerabilities

$ npm ls debug
└─┬<EMAIL_ADDRESS>  ├─┬<EMAIL_ADDRESS>  │ └──<EMAIL_ADDRESS>deduped
  ├──<EMAIL_ADDRESS>  ├─┬<EMAIL_ADDRESS>  │ └──<EMAIL_ADDRESS>deduped
  └─┬<EMAIL_ADDRESS>    └──<EMAIL_ADDRESS>deduped

Ah. The version of express wasn't listed, but it seems likely to have been a pre-4.x version, at least i.r.t send, as all the required send versions in the 4.x series has fixed debug versions as well. Very, very old express versions (1.x and likely 2.x) did have debug: * in the deps until I removed them all over time.

It was actually 4.0.0. For our use case, we need to install both the first and last version in a semver range (in this case 4,x) since we test for compatibility of our integrations. I ended up wrapping the require and skipping the test if there is an error on require.

Ah yea, I see that now. The 4.0.0 release depends on send 0.2.0 which depends on debug *.

send 0.3.0 is the first send release I made and it pins debug to 0.8.0.
express 4.1.0, the first express 4.x release I made, depends on send 0.3.0, where the debug is pinned. Depending on your needs, that could be another possible solution.
I hope that helps!


Unable to start jupyter python interactive window

VS Code Version
Version: 1.36.1 (system setup)
Commit: 2213894ea0415ee8c85c5eea0d0ff81ecc191529
Date: 2019-07-08T22:59:35.033Z
Electron: 4.2.5
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.17134
Python Extension Version
2019.6.24221
Error
Activating Python 3.7.3 64-bit ('base': conda) to run Jupyter failed with Error:
Error Python Extension: 2019-07-30 21:26:26: getActivatedEnvironmentVariables, Class name = b, completed in 4674ms, Arg 1: undefined, Arg 2: {"architecture":3,"path":"C:\Users\wanha\Anaconda3\python.exe","version":{"raw":"3.7.3-final","major":3,"minor":7,"patch":3,"prerelease":["final"],"build":[],"version":"3.7.3-final"},"sysPrefix":"C:\Users\wanha\Anaconda3","fileHash":"74bb711c8b882ee808520612deb69c009054e45641e11814c243333ecc429a11905779169f611eb3768d3efe7712e01e04b0af40de5a23fe6931588a83efcf88","companyDisplayName":"Anaconda, Inc.","type":"Conda","envName":"base","envPath":"C:\Users\wanha\Anaconda3","displayName":"Python 3.7.3 64-bit ('base': conda)"}, Arg 3: true [Error: StdErr from ShellExec, �Ҳ����ļ�
�Ҳ����ļ�
at b.getActivatedEnvironmentVariables (C:\Users\wanha.vscode\extensions\ms-python.python-2019.6.24221\out\client\extension.js:75:701724)]
Logs
Log.log

Your log is hard to read but it looks like running 'python -m jupyter notebook --version' is crashing.
Do you have jupyter installed?

@rchiodo
I have no idea why my log is garbled. Jupyter is installed and 'python -m jupyter notebook --version' runs successfully in my terminal(cmd).

I would guess your log has non ascii characters in it. Can you save it as utf-8?
When we run python in the environment you have picked it's crashing. The non-ascii characters likely have the reason.

I tried to open my log file in different encoding methods, but failed.

Is the error visible when being shown in the Console tab of the Developer Tools? Or is it a bunch of [][][][]?

@rchiodo the error is still unclear in the Console tab of the Developer Tools.

Are you using anaconda or miniconda? This might be a dupe of https://github.com/microsoft/vscode-python/issues/6802
Otherwise not sure why node is not encoding the stderr result as utf-8. That should be the default.

@rchiodo I reinstalled my anaconda and it works finally. Thanks.

Thanks @wanhanwan for trying out a new anaconda.


feat: add number format

Added a sample function to format a number using different locale parameters. An enumeration has been created to easily manage different locales. However, the URL of the locales has been included in the documentation.
Refs: #71

That's great! Could you just add some simple and quick test units for the new function you add, please?
Also, do not hesitate to credit your work and add your info in the authors section in README ;)

That's great! Could you just add some simple and quick test units for the new function you add, please? Also, do not hesitate to credit your work and add your info in the authors section in README ;)

Oh I didn't see the tests folder, I'll add some tests and I'll add the name to the contributors, thanks!

@Zhykos I've finished the tests<PHONE_NUMBER>573e2d1efd2d2e5a48a6194232e81f). Since this is my first time with deno on js/ts, feel free to correct if there are problems. I run the tests locally and everything works. And I also add my name to the contributors, thanks! (8099ecf97ada48cb6637fe0d07500ddf585b536c)

@Zhykos I've finished the tests (3460531). Since this is my first time with deno on js/ts, feel free to correct if there are problems. I run the tests locally and everything works. And I also add my name to the contributors, thanks! (8099ecf)

Don't worry, it could be a great time to learn ;) It's pretty much like Jest/Chai is you know it from Node.js. It's so more integrated and simple to use, IMHO. I thought I've set Github to launch tests on PRs, but it's only on branches. In the end, it's controlled ever way ;)
I will make some suggestions on the PR about how I think it would be better. Don't hesitate to discuss ;)

In the past I see Jest framework, and I agree with you, Deno is very easy to use.
However, yes, I see that the CI is set only for push, you need to add (but I think you know it):
on:
  pull_request:
    branches:
      - branch_name

@Zhykos I've finished the tests (3460531). Since this is my first time with deno on js/ts, feel free to correct if there are problems. I run the tests locally and everything works. And I also add my name to the contributors, thanks! (8099ecf)

Don't worry, it could be a great time to learn ;) It's pretty much like Jest/Chai is you know it from Node.js. It's so more integrated and simple to use, IMHO. I thought I've set Github to launch tests on PRs, but it's only on branches. In the end, it's controlled ever way ;)
I will make some suggestions on the PR about how I think it would be better. Don't hesitate to discuss ;)

In the past I see Jest framework, and I agree with you, Deno is very easy to use.
However, yes, I see that the CI is set only for push, you need to add (but I think you know it):
on:
  pull_request:
    branches:
      - branch_name

Right! I love Deno since I've discovered it!
I created an issue to execute on PRs, so thank you :) So this is an answer for #73


GPG support

Hello Added GPG support
Closes #5065
I have added a new Git Config git.enableCommitSigning that will tell vscode smartCommit to pass the -S flag to git. This way all commits menu items, UI commit features will take advantage of this.
You still need to set the git up to signing which can be found here: https://help.github.com/articles/signing-commits-using-gpg/
What will not take advantage is if someone uses the terminal to commit (that they will need pass the -S themselves)
I have made all changes that I can tell are needed.
If there is anything missing please let me know and I will make changes.
Please note that I didn't find any git tests in the extension.

@dmportella,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

@dmportella, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot

I fixed the conflicts

i have made changes to keep up with master
Its running the build now.
This ticket was on the june milestone but it was removed. still no feedback and i am going to start losing the interest of keeping it synced with master.
I know busy oss projects are huge lots of people talking asking for stuff etc.
So it is cool just let me know if there is anything else I can do to help or just close pull request if you the project is not interested on this change.
kind regards

All good @dmportella, I'll take a look at this in due time. 👍  Thanks!

Thanks a lot! 🍻

naisu... i can see its been released thank you

Is this still working?
error: gpg failed to sign the data
fatal: failed to write commit object

git commit --quiet --allow-empty-message --file - -S
gpg: cannot open tty `no tty': No such file or directory
error: gpg failed to sign the data
fatal: failed to write commit object

Yup, this issue is still present.

There would be a few reasons for this to occur typically it its the environment that is not setup correctly, vscode only cares and passed just the required flag to tell git to use signing if git is not setup correct for signing or gpg is not setup correctly you will see errors like this.
git configs need to be setup properly (vscode doesnt do that for you it require you to set it up first).
gpg needs to be setup correctly with the right key to allow git signing to work.
https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work might be good start to just verify that your system is setup correctly if it is I heard sme times where the system is allowing the pass-phase dialog to open so the signing fails. The later is a bit harder to troubleshoot.
If you describe your environment and setup it will be easier to diagnose

I have been using this feature since it was release is 3 difference setups (linux mint, ubuntu 17, 18 and windows) it has worked for me. I have now added support to my local environment to use yubikey to sign my work. Every time  of course i had to setup git to use gpg for signing etc.
Let me know about you system and i can help

just having a look around it might be that your setup is not allowing the system passphase dialog to open. try with another key as a test only that doesnt need any passphase. Just to isolate the issue.

I can confirm i get the same problem with @Ryonez too. I used password-protected PGP, and there's no way gpg ask for password in vscode.
I'm able to commit via terminal, and it's annoying that you should commit via terminal, while you stage the changes on the vscode.
I'm on Ubuntu.
> git commit --quiet --allow-empty-message --file - --all -S
gpg: cannot open tty `/dev/tty': No such device or address
error: gpg failed to sign the data
fatal: failed to write commit object


Trick to getting into discord group?

Is there a trick to getting into the Music Assistant discord channel?  It says to click on the Thumbs Up reaction to get verified.  What does that mean?   Clicking on the icon did nothing.

There is no trick. When you click on that you should then see a bunch of new channels. People are joining everyday without issue. If you can’t get in then tell me your discord nickname and I will have a look.

My nickname is johnd126.  I'm connecting using the newest version of Firefox.

I don’t know why clicking the thumbs up isn’t working for you but I have done it manually. You should be able to see all the channels now.


can't resize window in macos

Inlyne crashes if i try to resize its window.
Macos Ventura, Inlyne 0.3.2

I'm assuming this is the same issue that I've been seeing locally lately. Here's the crash report that I get for it (ignoring the duplicates since this winds up panicking while panicking)
"name" = "inlyne"
"operating_system" = "Arch Linux Rolling Release [64-bit]"
"crate_version" = "0.3.2"
"explanation" = """
Panic occurred in file '/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-core-0.17.1/src/resource.rs' at line 207
"""
"cause" = "Map callback was leaked"
"method" = "Panic"
"backtrace" = """

   0: 0x5582515c7a69 - <unresolved>
   1: 0x55825161155a - <unresolved>
   2: 0x5582516ae951 - <unresolved>
   3: 0x558250cfe669 - <unresolved>
   4: 0x558250ce29ee - <unresolved>
   5: 0x558250ce3724 - <unresolved>
   6: 0x558250ce246f - <unresolved>
   7: 0x55825103cbf5 - <unresolved>
   8: 0x558250ccdec3 - <unresolved>
   9: 0x558251032e67 - <unresolved>
  10: 0x7f882a158cd0 - <unresolved>
  11: 0x7f882a158d8a - __libc_start_main
  12: 0x558250ccdc55 - <unresolved>
  13:        0x0 - <unresolved>"""

You can see that the crash is happening in wgpu_core. It seems like this was already fixed in newer versions, but we're stuck on older versions since wgpu_glyph is unlikely to be updated. Looks like we'll have to downgrade the wgpu version we're using in v0.3

This should be fixed in the v0.3 branch now. I'll backport some other things and try to release a v0.3.3 tomorrow

This should be fixed with the v0.3.3 release
https://github.com/trimental/inlyne/releases/tag/v0.3.3


Pagination itemsPerPage resets to initial value on refresh

Hello,
I'm using ng-tasty with a rather heavily customized table that includes custom pagination templates. The templates work wonderfully, but I noticed that refreshing the page will always reset itemsPerPage to whatever its initial setting is in the angular controller. I am trying to find a solution that will allow me to capture the itemsPerPage value when it changes, then save it in $rootScope so it persists when the page is refreshed via something like this:
if ($rootScope.itemsPerPage) {
    $scope.itemsPerPage = $rootScope.itemsPerPage;
} else {
    $scope.itemsPerPage = 5;
}

Because the pagination template is controlled by ng-tasty, I'm at a loss for how I would go about doing this.

I would try solving this problem with local/session storage.  There's a few angular modules that make it pretty easy out there.
ngStorage
angular-local-storage


Migrate tests to TypeScript

We should migrate all the tests to TypeScript. This will let us test our TypeScript definitions as we use them to write Puppeteer tests. It will also unify the codebase and let us write all new tests in TypeScript. We'll get nicer type-checking and so on which will help when authoring tests.
I think we can do this in a few steps:

Rename each file to *.ts
For any files with few errors, fix them.
For any files with large errors, put a @ts-nocheck comment at the top of the file to disable the type checking in that file.
Ship this change, having done the work to have Mocha compile the TS before running the tests.
Go through each file that was @ts-nocheck'd and fix the errors.

Done!


fix ns issue with tasks get_by_id

This method is missing the namespace parameter.

@ajbosco thank you for the report!
The fix looks good to me, but I can't recall if you've submitted the CLA with us before; have you had a chance to do so?

I haven't submitted the CLA. What's the process for that?

https://tableau.github.io/contributing.html outlines the process.
Basically sign the PDF and email in!
Once we have that we can accept the PR and get this merged

I reviewed our tests and realized that this also could use a test case that would have caught the miss.
Would you be able to add a test case? You can model it off of (https://github.com/tableau/server-client-python/blob/ada7dbcc74838da2f9620f5a61135cea0e677014/test/test_workbook.py#L75)

This would be helpful to merge -- currently running off this commit


How can I install Types?

I got a lot of error messages like this one:
Cannot find module 'llama-node/dist/llm/llama-rs' or its corresponding type declarations.
How can I install the types?

hi, not sure which version did you install? I tried version 0.0.21, the type definition is working actually.

Me too, I have 0.0.21 versión :( Maybe some config file(?
tsconfig.json
{
  "compilerOptions": {
    "outDir": "./dist",
    "target": "es2022",
    "module": "nodenext",
    "strict": true,
    "esModuleInterop": true,
    "skipLibCheck": true,
    "forceConsistentCasingInFileNames": true,
    "types": ["node"]
  },
  "include": ["./"]
}

Changed "module": "nodenext" to "module": "CommonJS". And it worked.

Can you show me what tsconfig.ts do you use? I still getting errors because tsc change commonjs imports to ES.

https://github.com/hlhr202/llama-node/tree/main/example
Updated full examples here.


Is this documentation complete

I would have thought accessing configuration settings from anywhere should be basic functionality? I am looking down a lot of source code that seems to need to be added to get things out of appsettings.json.
I remember the happy old days of web.config where you could put settings in and pull them out with a single line of code, from anywhere in your app.
I am sure there is a good reason we now need a whole bunch of code to do this, but is this really progress? Surely one of the basic starting points for any new platform should be to consider the kind of things we need to do routinely in every app, and put those in for us. If we're being encouraged to put settings into appsettings.json, it would be really nice if there was functionality to pull those settings out without me having to write it all myself.

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

ID: 0eb4d762-3910-2c57-8741-3306c15537b6
Version Independent ID: ba2254a0-ea8e-9b28-e94b-edd0fc58c043
Content: Configuration in ASP.NET Core
Content Source: aspnetcore/fundamentals/configuration/index.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Hello @cactusoft ... We only work on the docs here. To provide product feedback, open an issue on the PU ("product unit") repo ...
https://github.com/dotnet/aspnetcore/issues
... and btw WRT your remarks: I think it's fair to say that we'd generally disagree with you on it being at all challenging to simply pull values out of app settings for configuration purposes. The base case to merely provide the key-value pairs in the app settings file ...
{
  "MyKey":  "My appsettings.json Value"
}

... and then inject IConfiguration (say as Config) (namespace: Microsoft.Extensions.Configuration) and then read Config["MyKey"]. There are more advanced config scenarios that require more code, but the base use case is simple imo.
So, I'm not sure what you're referring to when you remark that you need to "write it all myself."


Add Grant Teams Emergency Calling

Docs Build status updates of commit 13c1ae5:
:clock10: Full build: the average full build time is 11 min(s) 49 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 13c1ae5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Grant-CsTeamsEmergencyCallRoutingPolicy.md
:white_check_mark:Succeeded

Grant-CsTeamsEmergencyCallingPolicy.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@danny-levin - just noticed these are being submitted to the root folder. Please put them in the skype folder. Each cmdlet module has its own folder. Here is the one for Skype: https://github.com/MicrosoftDocs/office-docs-powershell/tree/master/skype/skype-ps/skype

Docs Build status updates of commit 52a1042:
:clock10: Full build: the average full build time is 11 min(s) 49 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 52a1042:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Grant-CsTeamsEmergencyCallRoutingPolicy.md
:white_check_mark:Succeeded

Grant-CsTeamsEmergencyCallingPolicy.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Closing this one so it doesn't mess up your next PR you are submitting.


Seeking community feedback on potential new feature: Standardize labels for next major release

Is this a new feature, an improvement, or a change to existing functionality?
New Feature
Please provide a clear description of the problem this feature solves
From this comment there was a request to standardize the labels coming from DCGM-Exporter to make them prometheus compliant. This would be a breaking change, which could be done in the next major release (4.0) coming this fall. We are seeking feedback on how the community views this type of breaking change that helps standardize and cleanup the product. Please let us know your opinion.
(Note this is not a commitment to make any changes, simply a request for feedback on potential changes)
Feature Description
Standardize all labels to follow prometheus best practices
Describe your ideal solution
All labels are prometheus compliant.
Additional context
No response

Thanks @glowkey for picking up on my question in this way! I really appreciate it.
Apart from the different casing style for the labels, there are some collisions with labels also coming from Prometheus' kubernetes_sd, e.g.:

namespace
pod
container

So labels from the exporter will end up being prefixed with exported_ depending on honor_labels:
# honor_labels controls how Prometheus handles conflicts between labels that are
# already present in scraped data and labels that Prometheus would attach
# server-side ("job" and "instance" labels, manually configured target
# labels, and labels generated by service discovery implementations).
#
# If honor_labels is set to "true", label conflicts are resolved by keeping label
# values from the scraped data and ignoring the conflicting server-side labels.
#
# If honor_labels is set to "false", label conflicts are resolved by renaming
# conflicting labels in the scraped data to "exported_<original-label>" (for
# example "exported_instance", "exported_job") and then attaching server-side
# labels.
#
# Setting honor_labels to "true" is useful for use cases such as federation and
# scraping the Pushgateway, where all labels specified in the target should be
# preserved.

(https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config)
There are two implications and approaches to this matter.

If you set honor_labels the metrics are nicely mapped to the actual pod they are about and joining on those labels with other pod metrics is straightforward (see https://github.com/prometheus/prometheus/issues/2204 for the hoops currently required to join metrics on different labels).

But you lose the strict pattern of these labels coming only from kubernetes_sd and indicated which pod they were scraped from.

If you go with approach one, please make the documentation more explicit and even consider changing the default for HonorLabels in the Helm Chart of the gpu-operator (https://github.com/NVIDIA/gpu-operator/blob/d4316a415bbd684ce8416a88042305fc1a093aa4/deployments/gpu-operator/values.yaml#L326C1-L326C23)
of the serviceMonitor (https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api.md#scrapeconfigspec)

@frittentheke , The best place to suggest changes in the gpu-operator is to raise the issue here: https://github.com/NVIDIA/gpu-operator/issues.

@frittentheke , Regarding labels that are coming from the DCGM-Exporter, such as namespace, pod, and container, how would you like to see such metrics? Maybe we need to add a prefix, such as "gpu_", for example: "gpu_namespace", "gpu_pod", etc. What do you think?

@frittentheke , Regarding labels that are coming from the DCGM-Exporter, such as namespace, pod, and container, how would you like to see such metrics?

I have no strong opinion on using either of the two options - but I do tend to like option 1 (keep using  namespace, pod and container, but then also switch to honor_labels=true) a little more
Just go one path and document this clearly:

If you keep the label names the same as how they come from the kubernetes_sd metadata, it just makes sense to use honor_labels=true by default - because that is what makes the most sense.

If you are at it, I'd also change the Hostname label to be node as this is the term Kubernetes uses. Again, this also aligns nicely with other metrics in case one wants to joint metrics.

Maybe we need to add a prefix, such as "gpu_", for example: "gpu_namespace", "gpu_pod", etc. What do you think?

If you rather NOT override the labels namespace, pod and container having a static prefix for all labels does make sense. This follows the call to standardize the labels which this issue is about, so this effort should then cover ALL gpu related labels.

gpu  -> gpu_id
modelName -> gpu_model
GPU_I_ID-> gpu_i_id

something that is annoying about this exporter is that each nvlink metric is reported as an individual metric as opposed to the same metric with individual labels (nvlink=....) -- can we fix that at some point?

something that is annoying about this exporter is that each nvlink metric is reported as an individual metric as opposed to the same metric with individual labels (nvlink=....) -- can we fix that at some point?
Can you provide an example?


Unit_Test

Unit test command lines in GUI_CI.yml added to test our code on the Linux system.
Resolves #53
Closes #53
Co-authored-by: @bassamEldesouki<EMAIL_ADDRESS>

Does that mean you are planning to add unit tests? 🎉

@platisd yes :) we are working on it, it will be the next Issue to add for this (CI_Implementation) Milestone :)

Will be nice to also test the code, not just build it 🧪
You will have to explain exactly what it does though 😆 and more importantly, how we can implement the tests (if they are not automatically done with gradle, totally new to that.)
Otherwise, the code seems good based on what I know on CI 😄

Well, the testing part is not done yet and it takes time since it is new to us as well. We still need to implement the testing units. I believe Bassam mentioned earlier. Explaining the implementation can't be done here so it is better we explain what we understood about it so far in the next meeting :)

Well, the testing part is not done yet and it takes time since it is new to us as well. We still need to implement the testing units. I believe Bassam mentioned earlier. Explaining the implementation can't be done here so it is better we explain what we understood about it so far in the next meeting :)

Sounds good! 😊


Update Routing to 2.2 endpoint routing.

[ ] Update to 2.2 endpoint routing
[ ] Update to be RP friendly. Replaces #8190

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

ID: 32374077-e02e-d6a6-1cea-05e58447b7cd
Version Independent ID: 86aeab13-1c25-9fc1-4e56-0390cb40c242
Content: Routing in ASP.NET Core
Content Source: aspnetcore/fundamentals/routing.md
Product: aspnet-core
GitHub Login: @ardalis
Microsoft Alias: riande

Another dup of #8763


Add config to set ENVVAR to manifest

Problem
Certain packages require setting envvar for a working installation (e.g. go needs to set GOROOT).
Suggestion
Allow specifying envvars to set in manifest. Sample go manifest from scoop
{
    "env_set": {
        "GOROOT": "$dir"
    }
}

Good idea! It seems like we could add a folder called shell in the webman dir that has webman_zshrc, webman_bashrc, etc. that a user could source in their own shell config. The tricky part is Windows...

In the .bat file that runs the binaries if you can add the 'set' command in windows
set GO_ROOT=C:\goroot\
set OTHER_ENV=value
runcomand...

On linux it would be to edit the .bashrc and .zshrc file
@candrewlee14

That's super clever, great idea.
Do you want to write a PR for that?

Should use setx instead of set for persistence? Otherwise the envvar is only applied for the executable and not detectable by other tools (e.g. for java, JAVA_HOME needs to be persisted so other tools can detect it).
I think a better approach is support some sort of post-install hooks where you can do those kinds of things:

setting envvar
modifying registry (e.g. for adding Context Menu entry)
run some init commands
etc

@tbnguyen1407 You’re right, a way to permanently set an envvar would definitely be better. I think there are commands that do that for Powershell if we can call into it. It may not be so easy to remove from path, I’m not sure.
I’m coming around to the idea of post-install hooks, I just don’t like the idea that package maintainers could potentially write the post-install script to run anything. I wouldn’t allow obvious pull requests like that, but I can’t perfectly vet every command. Is there a way we could better secure that route but still allow it?

Instead of post-install hooks, what about post-install instructions?

So I've got an idea, but I need a little help to think it through.
Let's say we manage webman.zsh, webman.bash, webman.fish, and webman.ps1 shell profile files that users can source. Here's a relevant link about how to make that work with Windows.
Packages can have a shell_map that has bash, zsh, fish, andpowershell objects that have lists of single line strings to add to the corresponding shell profile.
When these lines are added, we can append comments specific to the package & version, making it easy to search for and remove when uninstalling.
I think this would allow us to both set envvars and have additional scripts to add in our shell profiles, so we can set GO_ROOT and we can add a package for something like https://github.com/wfxr/forgit. It'd be nice also to add a convenience feature for an env_map of key-value pairs, which would add to those same profile scripts likely.
Would love to hear all of your thoughts. Its a tradeoff of security and convenience here. I think this convenience feature would be worth it, and would open up the door to a lot of new packages that currently can't be supported.
As we go forward, we can talk about what kind of checks we can do to automatically vet these shell scripts.

I think this approach is specific to shell usage, which activates the envvars per session. A run-once way to permanently set the envvar is still required for non-shell applications like IDEs to detect the installation.


Add workshop payment page

Adding a payment page for the workshops.  This is just a draft for now - please don't merge.

Thanks @grimbough - let me know when this is ready to merge!

Simone gave the go-ahead, so I think this can now be merged. Thanks!


[INTERNAL] Upgrade package-lock.json to v2

As introduced with npm v7

Coverage remained the same at 92.901% when pulling 5c7d7cb5dccb796f0bce4d9040dfc4756d6f2866 on lockfile-v2 into c8508dae511aa8b0c6a4b114c7c7dfe96b72709c on master.