Running under Linux

Hi,
I'm running Fall Guys with Proton. The FallGuyStats.exe start without an error and the overlay is show as well when activated. But no stats are collected. What can I do to do some more troubleshooting? It looks like the player.log file is in the correct folder.
Edit
Judging from strace, it tries to open the log file in steamapps/compatdata/1097150/pfx/dosdevices/c:/users/steamuser/Local Settings/Application DataLow/Mediatonic/FallGuys_client/Player.log, but the file actually lies in steamapps/compatdata/1097150/pfx/pfx/dosdevices/c:/users/steamuser/AppData/LocalLow/Mediatonic/FallGuys_client/Player.log.

I don't have much experience with Linux, but I do plan to add a settings screen soon with a bunch of options.
I may try adding a way to set the location then, which hopefully will take care of it.

That would be great! For now I just made a symlink and everything seems to work fine.


Propegate forwardOut error

Throwing the error provides no means of catching it somewhere.

throw will be removed in the next release.


Repo has two stix2arango installs

One in root:
https://github.com/muchdogesec/arango_taxii_server
One nested here
https://github.com/muchdogesec/arango_taxii_server/tree/main/arango_taxii_server
Can we remove the one that is not needed

already removed in test tree


خطای AD0001

بعد از افزودن خط زیر خطای زیر مشاهده می شود
           services.AddSingleton(typeof(ICacheManager<>), typeof(BaseCacheManager<>));
Warning	AD0001	Analyzer 'Microsoft.CodeAnalysis.CSharp.Analyzers.MetaAnalyzers.CSharpDiagnosticAnalyzerApiUsageAnalyzer' threw an exception of type 'System.NullReferenceException' with message 'Object reference not set to an instance of an object.'.

This issue is not related to this library.
It has been reported here: https://github.com/dotnet/roslyn/issues/32287
And probably you should update your Visual Studio to fix it.


Prefer else over inverse.

Requires Yields to use else, but still allows for {{yields to="inverse"}}

See also https://github.com/glimmerjs/glimmer-vm/pull/1296

Thanks @wagenet (and apologies for immediately creating a merge conflict!)
Can you add a note to the README where we talk about Yields mentioning that inverse is an alias for else (and that you should use the latter in your types?)


fix: ipam variable octet

Signed-off-by: Mohammed Zeeshan Ahmed<EMAIL_ADDRESS>

Note that Octet field present api is currently not used by us. Should I still add it to our api and tests like ipamoctet.
Note ipamoctet is deprecated


code example doesn't actually approve events

The python code example simply prints the event. It does not approve them with a POST message.  Please fix.

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

ID: 479d877a-81a0-5436-76d9-898303c5bbec
Version Independent ID: f352ae78-1d3f-a780-554c-fc304ada5a69
Content: Scheduled Events for Linux VMs in Azure - Azure Virtual Machines
Content Source: articles/virtual-machines/linux/scheduled-events.md
Service: virtual-machines
Sub-service: scheduled-events
GitHub Login: @EricRadzikowskiMSFT
Microsoft Alias: ericrad

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing, so we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary. #please-close


Issues about multi_uav ltl motion planning

Hello author, your  repository is about path planning under the temporal logic constraints of robots. Do you have any recommended papers on multi machine robot systems？Thanks！

There was no error reported, but there was an error in the above image. I only have Mona that has not been prepared yet. May I ask if the author knows the reason for the above error.

Now that I have prepared Mona, I can basically confirm the three mosek issues. May I know where to put the license specifically

May I ask if the author knows the reason for the above error.

I suspect the error has to do with Mona not being properly installed.
As far as MOSEK goes, the mosek.lic license file usually goes somewhere like ~/mosek/mosek/lic. See the Drake documentation for more details.

I suspect the error has to do with Mona not being properly installed.
As far as MOSEK goes, the mosek.lic license file usually goes somewhere like ~/mosek/mosek/lic. See the Drake documentation for more details.

Thanks! It solves my problem.
After downloading the source code of mona from https://www.brics.dk/mona/download.html and installing it (following the instructions in the INSTALL file in the repo), and restarting my server, the problem is solved!


thesisForm handling

Coverage decreased (-1.1%) to 54.545% when pulling e807297ca5dc5ada758bf1ffb65220e9159af84a on Jakousa:trunk into 58f33ce4bff07cf9666bf00d7d49ada01d33a89f on OhtuGrappa2:trunk.

Changes Unknown when pulling a9b7c5573be776d4a67bed0e5f9c3203e30736a7 on Jakousa:trunk into ** on OhtuGrappa2:trunk**.


Update Configuring URL forwarding or redirects with Page Rules.md

Hey @jedecf , would it be possible for you to approve and merge this one?


drivers/sensors/gnss: Add suffix to macro of geofence index

Summary
Add suffix to macro of geofence index, just keep the same style(suffix)
Impact
N/A (internal used macro)
Testing

NuttX CI

@Donny9 Could you review this PR please?


Get result from launchNativeReviewDialog (Success/No Success)

Is your feature request related to a problem? Please describe.
I would like to track with my analytics whenever a user rated the app using the NativeReviewDialog (for both iOS and Android) but so far it seems like it's not possible. I ideally want to be able to track how many stars I got from the review dialog, or in the case that is not possible, at least whether or not the app was rated or the dialog was dismissed.
Describe the solution you'd like
Return a response with either the number of stars given in the NativeReviewDialog or if the dialog was dismissed
Describe alternatives you've considered
So far no alternatives have been considered

I would like to track with my analytics whenever a user rated the app using the NativeReviewDialog (for both iOS and Android)

It's not possible. Google and Apple doesn't provide any callback in their dialogs.


Transitive edges

Hi all, sorry for an unsolicited PR. In our project it is useful to look at the dependencies including the transitive ones.
I thought it will be helpful to push to the upstream. Also @er1c helped with some sbt-related settings.
Not sure about the scripted test though, was not able to make it working locally.
Included a little cleanup of the unused variables. Hope this is alright.

@dwijnand anything I can add to move it forward?

Hey @dot-vlad, sorry.  My blocker here is that CI isn't working on Travis CI anymore and I don't have the bandwidth to fix that.  Do you know of an easy way to migrate a Travis CI setup to GitHub Actions?

@dwijnand after 10 minutes of googling, I didn't find anything outstanding but re-writting the yaml files.

Hey @dot-vlad, found an ice-breaker for migrating to GitHub Actions (by bootstrapping my setup with a run of sbt-github-actions).  So that's all running properly it seems (without CI publishing for now).  I rebased and this is failing, do you think you could look at what's going on?


CLI tools onboarding

There is the client server present as part of the HELM installation (https://github.com/securesign/sigstore-ocp/blob/main/charts/trusted-artifact-signer/templates/clientserver-deployment.yaml). We should add this functionality to the operator too. Ensure that the the ConsoleCliDownloads for rekor, cosign and gitsign are created.

+1

@lance is there an update for this? Does this work need to be done?

@tommyd450 could you provide the latest snapshot images

@JasonPowr sorry - I should have updated sooner. The Konflux team will not have binary distribution ready by TP2, so this should be done.


Resolve issues with Spark HDFS codecs

See discussion here: https://github.com/slamdata/purescript-quasar/pull/26#discussion_r107148530
Looks like there is a mismatch with the encoder and decoder.

https://github.com/slamdata/purescript-quasar/blob/71c25f2116802356968fa46bd08650755e0f1852/src/Quasar/Mount/SparkHDFS.purs#L57

Opened an issue on Quasar, as the correct value is not documented currently: https://github.com/quasar-analytics/quasar/issues/1995


Build error on template

I get this error when trying to build the new template Android project.
Can not resolve reference: Microsoft.Bcl.AsyncInterfaces, referenced by System.Text.Json. Please add a NuGet package or assembly reference for Microsoft.Bcl.AsyncInterfaces, or remove the reference to System.Text.Json.	FirstMobileBlazorBindingsApp.Android
Can not resolve reference: System.Diagnostics.EventLog, referenced by Microsoft.Extensions.Logging.EventLog. Please add a NuGet package or assembly reference for System.Diagnostics.EventLog, or remove the reference to Microsoft.Extensions.Logging.EventLog.	FirstMobileBlazorBindingsApp.Android

I'm trying to build within Visual Studio on Windows.
Visual Studio 16.4.3
Xamarin   <IP_ADDRESS>8 (d16-4@4755fb3)
Xamarin Designer   <IP_ADDRESS>5 (remotes/origin/d16-4@ac250f5aa)
Xamarin Templates   16.4.25 (579ee62)
Xamarin.Android SDK   <IP_ADDRESS> (d16-4/d66aed0)
Xamarin.iOS and Xamarin.Mac SDK   <IP_ADDRESS> (5f802ef)
This is the result of dotnet --info
.NET Core SDK (reflecting any global.json):
Version:   3.1.101
Commit:    b377529961
Runtime Environment:
OS Name:     Windows
OS Version:  6.3.9600
OS Platform: Windows
RID:         win81-x64
Base Path:   C:\Program Files\dotnet\sdk\3.1.101\
Host (useful for support):
Version: 3.1.1
Commit:  a1388f194c
.NET Core SDKs installed:
2.1.508 [C:\Program Files\dotnet\sdk]
2.1.509 [C:\Program Files\dotnet\sdk]
2.1.801 [C:\Program Files\dotnet\sdk]
2.2.300 [C:\Program Files\dotnet\sdk]
2.2.401 [C:\Program Files\dotnet\sdk]
3.0.100 [C:\Program Files\dotnet\sdk]
3.1.100 [C:\Program Files\dotnet\sdk]
3.1.101 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.13 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.15 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.13 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.15 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.0.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.13 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.0.0 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 3.1.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Hi @Kahbazi thank you for the additional info, I will take a closer look. On the surface I would have expected it to work, so I'll think about it some more and try to figure out what's going on.

@Eilon I opened Visual Studio as administrator and the Android project built successfully, but I still get the same error when running Visual Studio with non-admin user.

Hi @Kahbazi I've asked some colleagues and this issue does not seem familiar to anyone.
So you ran the dotnet new command from the command line, then opened the SLN in VS, and when you try to build, you get this error? Are there any other steps?

Thanks @Eilon. Yes this is exactly what I'm doing. There are no more steps.
Feel free to close this issue since I am able to build with Visual Studio running as Administrator.
Nevertheless I am curios on why I can't build the project with normal user.

@Eilon what steps needed for troubleshoot this issue? I have exact same issue. This is similar to https://github.com/xamarin/xamarin-android/issues/4074 or https://github.com/xamarin/xamarin-android/issues/4182 and I actually have similar issue with Generic Host in Xamarin see https://github.com/dotnet/extensions/issues/1631
I willing to do debugging, but need some guidance in which places to start looking first.

@Kahbazi does by a chance you have NUGET_PACKAGES env variable set?

@kant2002 yes I have nuget in environment variable for my user. This is probably the issue since I have no problem when I switch to another account.
So I think this issue has nothing to do with this project. Perhaps the issue is with how nuget works or Xamarin itself. @Eilon where should we transfer this issue?

@Eilon I check that xamarin#4171 somewhat fix the issue. It is fixed it for me, but PR is not fully completed. so maybe not work for all. One caveat is that I manually build the Xamarin from sources.

Hi folks, sorry for the large delay on this.
I agree this issue doesn't seem specific to Mobile Blazor Bindings because the projects it generates are all common types of .NET projects used in Visual Studio.
I also agree that it makes sense to find a better place to log this issue, but without being able to reproduce it myself to investigate, I recommend trying to find or log a new bug in one of these locations:

Xamarin.Forms: https://github.com/xamarin/Xamarin.Forms
Xamarin Android: https://github.com/xamarin/xamarin-android
NuGet: https://github.com/NuGet/Home
.NET Core: https://github.com/dotnet/sdk

As such, I'm closing the issue here because there is no further action planned as part of Mobile Blazor Bindings.


reduce the binary with the -s, -w ldflags

Added the -s -w ldflags to the build step. This reduced the broker binary size from 27M to 15M.
Old build command: go install -ldflags="-s -w" ./cmd/broker
-rwxrwxr-x. 1 jesusr jesusr 27704824 May 11 19:32 /home/jesusr/dev/bin/broker

New build commands go install -ldflags="-s -w" ./cmd/broker
 -rwxrwxr-x. 1 jesusr jesusr 15619712 May 12 13:01 /home/jesusr/dev/bin/broker

I also verified that stack traces still print out useful information.
2017/05/12 13:11:40 http: panic serving [::1]:56910: runtime error: invalid memory address or nil pointer dereference
goroutine 35 [running]:
net/http.(*conn).serve.func1(0xc420132c80)
        /usr/lib/golang/src/net/http/server.go:1491 +0x12a
panic(0xcde6c0, 0xc420012150)
        /usr/lib/golang/src/runtime/panic.go:458 +0x243
github.com/fusor/ansible-service-broker/pkg/broker.AnsibleBroker.Bootstrap(0xc4203b5a40, 0xc4201f56b0, 0xc4202d8220, 0xf, 0xc4202d8248, 0x4, 0xc4202d8268, 0x4, 0x14a7b60, 0xc42040a540, ...)
        /home/jesusr/dev/src/github.com/fusor/ansible-service-broker/pkg/broker/broker.go:68 +0x66
github.com/fusor/ansible-service-broker/pkg/broker.(*AnsibleBroker).Bootstrap(0xc4203b5bc0, 0x14a94c0, 0x14e7700, 0xc4202a1c30)
        <autogenerated>:4 +0x77
github.com/fusor/ansible-service-broker/pkg/handler.handler.bootstrap(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0xc4201f5b30, 0x0, 0x14af640, ...)
        /home/jesusr/dev/src/github.com/fusor/ansible-service-broker/pkg/handler/handler.go:64 +0x6b
github.com/fusor/ansible-service-broker/pkg/handler.(handler).(github.com/fusor/ansible-service-broker/pkg/handler.bootstrap)-fm(0x7f89255a2990, 0xc420155080, 0xc4200c7680, 0xc4201550b0)
        /home/jesusr/dev/src/github.com/fusor/ansible-service-broker/pkg/handler/handler.go:47 +0x80
github.com/fusor/ansible-service-broker/pkg/handler.createVarHandler.func1(0x7f89255a2990, 0xc420155080, 0xc4200c7680)
        /home/jesusr/dev/src/github.com/fusor/ansible-service-broker/pkg/handler/handler.go:33 +0x65
net/http.HandlerFunc.ServeHTTP(0xc4202d97a0, 0x7f89255a2990, 0xc420155080, 0xc4200c7680)
        /usr/lib/golang/src/net/http/server.go:1726 +0x44
github.com/fusor/ansible-service-broker/vendor/github.com/gorilla/mux.(*Router).ServeHTTP(0xc420523a88, 0x7f89255a2990, 0xc420155080, 0xc4200c7680)
        /home/jesusr/dev/src/github.com/fusor/ansible-service-broker/vendor/github.com/gorilla/mux/mux.go:114 +0x10d
github.com/fusor/ansible-service-broker/pkg/handler.handler.ServeHTTP(0x0, 0x0, 0x0, 0x0, 0xc420317500, 0x8, 0x8, 0xc4201f5b30, 0x0, 0x14af640, ...)
        /home/jesusr/dev/src/github.com/fusor/ansible-service-broker/pkg/handler/handler.go:69 +0x52
github.com/fusor/ansible-service-broker/pkg/handler.(*handler).ServeHTTP(0xc420336660, 0x7f89255a2990, 0xc420155080, 0xc4200c74a0)
        <autogenerated>:2 +0x96
github.com/fusor/ansible-service-broker/vendor/github.com/gorilla/handlers.loggingHandler.ServeHTTP(0x14a45e0, 0xc420038010, 0x14a51e0, 0xc420336660, 0x14ab5e0, 0xc4204f5ee0, 0xc4200c74a0)
        /home/jesusr/dev/src/github.com/fusor/ansible-service-broker/vendor/github.com/gorilla/handlers/handlers.go:69 +0x121
github.com/fusor/ansible-service-broker/vendor/github.com/gorilla/handlers.(*loggingHandler).ServeHTTP(0xc42027e900, 0x14ab5e0, 0xc4204f5ee0, 0xc4200c74a0)
        <autogenerated>:8 +0x8b
net/http.serverHandler.ServeHTTP(0xc420132c00, 0x14ab5e0, 0xc4204f5ee0, 0xc4200c74a0)
        /usr/lib/golang/src/net/http/server.go:2202 +0x7d
net/http.(*conn).serve(0xc420132c80, 0x14ac6a0, 0xc4201a6880)
        /usr/lib/golang/src/net/http/server.go:1579 +0x4b7
created by net/http.(*Server).Serve
        /usr/lib/golang/src/net/http/server.go:2293 +0x44d

TEST
Build master and make note of the broker size.
git checkout master
make clean
make build
ls -l ../bin/broker

Now rebuild with my patch
git checkout reduce-binary-size
make clean
make build
ls -l ../bin/broker


Unsupported Map version 279

it wont work for any of my maps im trying to find this dang planterra bulb

Install the latest version.


New version: Mozilla.Firefox.DeveloperEdition.nl version 132.0 (132.0b4)

Created by 🥟 Dumplings.
Microsoft Reviewers: Open in CodeFlow

Verify by proxy: https://github.com/microsoft/winget-pkgs/pull/179431#issuecomment-2400690391


/etc/init.d/procps: line 22: apply_sysctl: command not found

On a RHEL 6.1 test node (Test Kitchen), I get the following error:
 Recipe: sysctl::service

           ================================================================================
           Error executing action `restart` on resource 'service[procps]'
           ================================================================================

           Mixlib::ShellOut::ShellCommandFailed
           ------------------------------------
           Expected process to exit with [0], but received '127'
           ---- Begin output of /sbin/service procps restart ----
           STDOUT:
           STDERR: /etc/init.d/procps: line 22: apply_sysctl: command not found
           ---- End output of /sbin/service procps restart ----
           Ran /sbin/service procps restart returned 127

           Resource Declaration:
           ---------------------
           # In /tmp/kitchen/cache/cookbooks/sysctl/recipes/service.rb

            26: service 'procps' do
            27:   supports :restart => true, :reload => true, :status => false
            28:   case node['platform']
            29:   when 'freebsd'
            30:     service_name 'sysctl'
            31:   when 'arch', 'exherbo'
            32:     service_name 'systemd-sysctl'
            33:     provider Chef::Provider::Service::Systemd
            34:   when 'centos', 'redhat', 'scientific'
            35:     if node['platform_version'].to_f >= 7.0
            36:       service_name 'systemd-sysctl'
            37:       provider Chef::Provider::Service::Systemd
            38:     end
            39:   when 'fedora'

           Compiled Resource:
           ------------------
           # Declared in /tmp/kitchen/cache/cookbooks/sysctl/recipes/service.rb:26:in `from_file'

           service("procps") do
             action [:enable]
             updated true
             supports {:restart=>true, :reload=>true, :status=>true}
             retries 0
             retry_delay 2
             default_guard_interpreter :default
             service_name "procps"
             enabled true
             pattern "procps"
             declared_type :service
             cookbook_name "sysctl"
             recipe_name "service"
           end

Could it be due to this line, https://github.com/svanzoest-cookbooks/sysctl/blob/master/templates/default/procps.init-rhel.erb#L14, being flawed?

I needed to upgrade initscripts, which fixed this problem.
initscripts-9.03.49-1.el6_7.4.x86_64


cuda runtime error (10)

Dear all,
I have a issue when using the cutorch package
I install Torch7 with self-contained Lua on the redhat machine. No error occurs during the installation. Then I installed cutorch, and the output in the shell is below:

-- Installing: /home/liuxuebo/distro/install/include/THC/generic/THCTensorSort.cu
cd build
Updating manifest for /home/liuxuebo/distro/install/lib/luarocks/rocks
cutorch scm-1 is now built and installed in /home/liuxuebo/distro/install/ (license: BSD)

which seems normal. Then I try to import cutorch in th shell and the output is ok. However, when I ran a torch program using GPU, I met an error:

THCudaCheck FAIL file=/tmp/luarocks_cutorch-scm-1-8352/cutorch/init.c line=720 error=10 : invalid device ordinal
/home/liuxuebo/distro/install/bin/luajit: main.lua:282: cuda runtime error (10) : invalid device ordinal at /tmp/luarocks_cutorch-scm-1-8352/cutorch/init.c:720
stack traceback:
[C]: in function 'setDevice'
main.lua:282: in function 'main'
main.lua:354: in main chunk
[C]: in function 'dofile'
...ebo/distro/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main chunk
[C]: at 0x00405810

I wonder that do the settings of cuda or the way I install torch cause this problem?
(P.S., version of cuda is 7.0)

invalid device ordinal
means you are accessing a GPU device index that is not accessible to the program

How to solve this problem?

I get the same problem. Any help on how to solve this problem ?

I'm new to torch but the way I got this working is
$th
th> require 'cutorch'
th> cutorch.getDevice()

Then plugging the output from above into cutorch.setDevice in the code that isn't working. More experienced torch devs could point out if there is a better way


Replace deprecated include by a include_tasks

@jperera Done. I've also updated #41, and #29 is still merge pending!

Hm, the build is failing, there are some inconsistencies across Ansible versions, let's put this on WIP

It's fixed but maybe Travis is not able to finish the phase of compiling PHP:


Migrating getUniqueUserWithClaimValues Adaptive function signautre in 5.12.0

Describe the issue:
Because of this issue https://github.com/wso2/product-is/issues/11777 , we need to alter the method signature of adaptive function getUniqueUserWithClaimValues  , via https://github.com/wso2-extensions/identity-conditional-auth-functions/pull/70
Modified Parameters can be found here : https://github.com/wso2/product-is/issues/5152#issuecomment-846831139
This Issue opened to track the Migration process

Added to docs with https://github.com/wso2/docs-is/pull/2991, https://github.com/wso2/docs-is/pull/2997


(co)products/(co)equalizers for Fincats and Diagrams

Main goal: implement the constructions described in Peschke and Tholen (2020) remark 2.8. This involves developing a lot of other prerequisite functionality.
Main contributions:

Currying FinDomFunctors into C-Set as FinDomFunctors into Set
pushout-based chase

Collage of functor
Conversion between C-Set and SpanC-Set (a model for C-Rel)
left kan extensions of FinDomFunctors into Set (or C-Set) + universal property

Limits/colimits the category of FinCats

Products and coproducts of FinCat presentations (including treatment of equations)
No treatment of equations yet for equalizers/coequalizers

Limits/colimits the category of FinCats

Products/coproducts of Diagram{id} and Diagram{op}, equalizers for the former and coequalizers for the latter
Universal properties for the above (co)limits
Left kan extension used to compute coequalizers for Diagram{id}

To-do:

Left kan extension to compute equalizers for Diagram{op}
Universal property of coequalizers (id) / equalizers (op).

Caveats:

Code for (co)limits of FinCats is stored in Limits.jl to avoid circular dependency. Tests are still in test/.../FinCats.jl
For simplicity, FinCatPresentations are treated (but, ideally, code generically would work with FinCatGraphs as well)
Because of the makeshift way dynamic acsets are implemented, rather than MyCSetType() it's safer to use Base.invokelatest(MyCSetType)
Rebasing on master included a bunch of unrelated commits for some reason. The relevant files are Chase.jl, Limits.jl, CSets.jl, Diagrams.jl.
Left kan extensions are abysmally slow (possibly in large part due to the dynamic acset hack)

cleaned up commit history and resubmit as https://github.com/AlgebraicJulia/Catlab.jl/pull/615


Update Stripe Sample

Update to new Stripe Payments APIs and Stripe Elements
Change to Vanilla HTML and JavaScript
Update Stripe libraries
Change to node 10 engine

You can test it here: https://cloud-functions-stripe-sample.web.app/

no 3D Secure required:<PHONE_NUMBER>424242
3D Secure required:<PHONE_NUMBER>003220

@googlebot I signed it!

@googlebot I fixed it.

@jhuleatt any idea what's going wrong here? It looks like the bot doesn't like the merging in of the changes from master. Any idea why that is?

It looks like the CLA bot is confused. I'm going to manually set the CLA label

Added some small comments, but looks good to me overall!

Thanks a mill for the review, I'll look into the needed changes :)
Regarding the No such setupintent error, it looks like you're using the default publishable key from the Stripe docs, rather than your Stripe account's publishable key. Updating the STRIPE_PUBLISHABLE_KEY in the app.js file with the one in your Stripe Dashboard should do the trick 👍
To help others avoid this mistake, do you remember where you copied the publishable key from?

Thanks a mill for the review, I'll look into the needed changes :)
Regarding the No such setupintent error, it looks like you're using the default publishable key from the Stripe docs, rather than your Stripe account's publishable key. Updating the STRIPE_PUBLISHABLE_KEY in the app.js file with the one in your Stripe Dashboard should do the trick 👍
To help others avoid this mistake, do you remember where you copied the publishable key from?

Thanks Thor, that was it! I copy + pasted from a draft update of this page that will go along with this PR, and forgot to replace the default key with my own. I'll make a note on the draft to use something like <YOUR STRIPE PUBLISHABLE KEY> instead of the default publishable key.


LEGO: Pull request from lego/hb_2939_20201013110552560 to master

LEGO: Pull request from lego/hb_2939_20201013110552560 to master with localized lcls

testing build, https://github-private.visualstudio.com/microsoft/_build/results?buildId=13554&view=results


Sorting broken on 0.3.2

Just upgraded from 0.2.13 to 0.3.2 to benefit from the latest data.index fix on b-table (which works) but the sorting seems now broken
<template>
    <b-table
        :items="items"
        :fields="formFields"
        v-model:sort-by="sortBy"
        v-model:sort-desc="sortDesc">
    >
      <template v-slot:cell(name)="data">
        <span :class="`name_${data.index}`">{{ data.value }}</span>
      </template>
    </b-table>
</template>

<script>

export default {
  data(){
    return {
      sortBy: 'name',
      sortDesc: false,
      formFields: [
        {key: "name", sortable: true, label: "Name"},
        {key: "status", sortable: true, label: "Status"},
      ],
      items: [
        { name: "Jack", status: "Used" },
        {name: "Frank", status: "Unused"},
        {name: "Larry", status: "Used" },
      ],
    }
  },
}
</script>

I suggest waiting for 0.3.3 as many BTable systems were overhauled.

I don't think that sorting is broken, You are missing the sort-internal(boolean) prop which allows you to sort the displayed items internally instead of re-fetching your data using the sorted event

What exactly does the sort-internal prop do?

I don't think that sorting is broken, You are missing the sort-internal(boolean) prop which allows you to sort the displayed items internally instead of re-fetching your data using the sorted event

What exactly does the sort-internal prop do?

Determine if the table will sort its internal items or you will sort the given items prop yourself which is useful when you want to sort the table through API request within the sorted event
It was mentioned in this PR https://github.com/cdmoro/bootstrap-vue-3/pull/594
And its default value changed to false based on this comment
https://github.com/cdmoro/bootstrap-vue-3/pull/609#discussion_r959044777

Determine if the table will sort its internal items or you will sort the given items prop yourself which is useful when you want to sort the table through API request within the sorted event It was mentioned in this PR #594
And its default value changed to false based on this comment #609 (comment)

https://github.com/cdmoro/bootstrap-vue-3/commit/aac2b68f7bc8672246107c650e7c928dd336c201 Yeah, I turned it to true. I think my point was that it didn't have a default value... But did not fully understand how it worked, default true is better since most people don't need to sort by apis and stuff.

Update to 0.3.3 as sortInternal is default true, (fixes your issue). Or manually set prop sortInternal to true.


choose color with palette options "lose" focus

When I chose a color palette with, it works perfectly, the 2nd test, the cursor returns to the beginning of the line, I do not understand at all ...
Another person had the same problem, but had no response:
http://plnkr.co/edit/xSA66CWfeXQMMzLlJ3Tm?p=preview
Please help me out on this.

hey thanks for the plunker. i can reproduce the issue. strange thing
not sure if i have time in the next future but i have it on my list

could you add a reference to "the other person with the same problem"?

Thanks for your answer.
http://stackoverflow.com/questions/36762189/text-angular-color-picker-spectrum-pallet-issue here you can find the issue of the other person.
I tried to contact him, but no answer :(

from what I see, the plunker you submitted and that is from the referred stackoverflow issue contains two colorpickers. the first one is from this lib and works fine, the second one is from ruhley/angular-color-picker and resets the input.
closing here since i assume this is not caused by our library

Sorry but don't understand, you said
`taRegisterTool('fontColor-spectrum', {
display: "",
action: function (color) {
var me = this;
if (!this.$editor().wrapSelection) {
setTimeout(function () {
me.action(color);
}, 100)
} else {
return this.$editor().wrapSelection('foreColor', color);
}
},
options: {
replacerClassName: 'fa fa-font', showButtons: false, showPaletteOnly: true
},
color: "#000"
});
works fine ? i tried and don't work :/ it reset input`

the code above seems not to be related to this library

Yes ok.. But i used your library with bower install angular-spectrum-colorpicker and I have the same problem... But well, maybe i did an error

i'd be happy to help there but the plunker you provided seems to not demonstrate the problem you're talking about. Which leaves me in a "can not reproduce" state

I can reproduce a plunker, but the one I gave you, in the first colorpicker which using directiver spectrum color-picker, when choosing a color for the 2nd time, the cursor returns to the beginning of the line, right? (or maybe it depends of navigator ..)

Ah i get it!

Nice, and you think you can figure out where the problem?

Not sure if I find time in the near future. I'd be happy to get some help here


Cannot find module 'express'

Ember-cli 0.2.0 removes express from package.json, and this addon assumes it'll be there.. so somehow this addon needs to get express into the picture
(Well, technically it's the ember init from ember-cli 0.2.0 that removes this)

Is this still being looked at?

you're sure you have npm installed?
On Thu, May 28, 2015 at 9:04 AM, Devonte<EMAIL_ADDRESS>wrote:

Is this still being looked at?
—
Reply to this email directly or view it on GitHub
https://github.com/joostdevries/ember-cli-remote-inspector/issues/8#issuecomment-106446696
.

Just put some more work in #7. Once I have feedback on that, I'll merge + release. Sorry for the delay guys.


Anax sidebarfix cli

Added article on using cURL to troubleshoot CLI to sidebar

Closing this b/c this item has already been added to the sidebar.


test: debug failing unit test

Summary
Debug failing test in release process
Checklist

[x] Does your PR title have the correct title format?
Does your PR have a breaking change?: No

Close, see: https://github.com/amplitude/Amplitude-Kotlin/pull/53


"Punch card" visualization of a boolean-valued plan

inspired by Figure 2 of this paper
Weakly Supervised Source-Specific Sound Level Estimation in Noisy Soundscapes
Aurora Cramer, Mark Cartwright, Fatemeh Pishdadian, Juan Pablo Bello
https://arxiv.org/abs/2105.02911

punch card  with Na with demo with boolean factors
this must also be used for multipleplan and default values

I think I came up with a reasonable solution

@mathieulagrange great work !! thank you 🙏🏻


fix: update deployment script names to match latest

What :computer:

Update mentions of 01_deploy_vendor.js to 01_deploy_vendor.ts

Why :hand:

These scripts are now TypeScript files and this provides more clear instructions

Thank you @MexicanAce !


Allow struct predeclaration (master)

Problem
Structs were declared like so
typedef struct {
} sFoo;

which made it impossible to predeclare them.
Solution
Do it like so
typedef struct sFoo {
} sFoo;

Could you re-target that to develop?


xwayland/selection: ignore incr transfer requests during incr transfer

Currently, if:

an X11 application requests the contents of the clipboard
the contents are too large to be sent in one go, so incr transfer
starts
wlroots registers an fd to write the chunks to in the event loop

If

the X11 application requests the contents of the clipboard again
(before the transfer completed)

Then

wlroots registers the same fd with the same void *data into the event
loop

Finally, when

the "first" transfer completes
wlroots frees the void *data, removes one instance of the fd from the
event loop
one is still there; if it fires due to closing, wlroots accesses the
freed void *data and segfaults

This commit makes the request in 4. a no-op, preventing the segfault.
I do not know if this makes any sense from a protocol perspective, or if
this should be disallowed in a different way elsewhere (or if it's
somehow allowed!)
Closes #2548.

the X11 application requests the contents of the clipboard again

Shouldn't that queue a new transfer?

the X11 application requests the contents of the clipboard again

Shouldn't that queue a new transfer?

Shouldn't that queue a new transfer?

I'm not sure. At least, I think I'm not using precise enough terminology.
Outgoing transfers are queued up in xwm_selection_send_data, whose only caller is xwm_handle_selection_request, which is the handler for XCB_SELECTION_REQUEST. This outgoing path is not what triggers this bug.
The issue is in the incoming path, in xwm_write_property. The incoming path can only have a single ongoing transfer, and performs no sort of queuing like the outgoing path. However, xwm_write_property has no guard against starting a second transfer while one is already running. It can double-add the same transfer->source_fd into the epoll loop — this is the eventual cause of the crash.
From the logs provided by the OP in https://github.com/swaywm/wlroots/issues/2548, what's happening is xwm_get_incr_chunk is called during an incoming transfer, for the same transfer that's already running. This causes xwm_write_property to be called again for the same transfer, eventually leading to the crash.
xwm_get_incr_chunk is just called in response to XCB_PROPERTY_NOTIFY, and there's no logic on that path preventing this issue.

Shouldn't that queue a new transfer?

I'm not sure. At least, I think I'm not using precise enough terminology.
Outgoing transfers are queued up in xwm_selection_send_data, whose only caller is xwm_handle_selection_request, which is the handler for XCB_SELECTION_REQUEST. This outgoing path is not what triggers this bug.
The issue is in the incoming path, in xwm_write_property. The incoming path can only have a single ongoing transfer, and performs no sort of queuing like the outgoing path. However, xwm_write_property has no guard against starting a second transfer while one is already running. It can double-add the same transfer->source_fd into the epoll loop — this is the eventual cause of the crash.
From the logs provided by the OP in https://github.com/swaywm/wlroots/issues/2548, what's happening is xwm_get_incr_chunk is called during an incoming transfer, for the same transfer that's already running. This causes xwm_write_property to be called again for the same transfer, eventually leading to the crash.
xwm_get_incr_chunk is just called in response to XCB_PROPERTY_NOTIFY, and there's no logic on that path preventing this issue.

As per the IRC discussion today, I'll close this PR in favor of reworking xwm to use a per-transfer window, which would prevent (this entire class of) bugs in a less hacky way. $DAY_JOB permitting, I'll hopefully have some patches up in the next little while.

As per the IRC discussion today, I'll close this PR in favor of reworking xwm to use a per-transfer window, which would prevent (this entire class of) bugs in a less hacky way. $DAY_JOB permitting, I'll hopefully have some patches up in the next little while.


fix: suspense granularity for better ux

Introduce more granular Suspense wrappers to improve ux (static header/footer visible while dynamic modules are loading).

👍🏻


Support for samples from different lineages?

It doesn't seem like this code is able to handle samples from different lineages:
https://github.com/nhhaidee/scovtree/blob/d9295d05a0f64d08af35d292dac7e50e2ad4ef92/bin/filter_gisaid_sequences.py#L79-L84
https://github.com/nhhaidee/scovtree/blob/d9295d05a0f64d08af35d292dac7e50e2ad4ef92/bin/filter_gisaid_sequences.py#L111
It looks like it is assumed that all samples have the same lineage assignment, which is not always the case.

Fixed by https://github.com/nhhaidee/scovtree/pull/17/commits/fa18e8ed8f4538c5719a907ddce00c8f6a4fb3d7

Hi @nhhaidee
In the future if possible, can you address each issue in a separate PR? It would make it much easier to track what changes address what issues.

For changes to bin/filter_gisaid_sequences.py in fa18e8e:

Can you update your tests? Maybe add a sequence from a different lineage to your test dataset input sequences file?
How does GISAID sequence filtering and tree pruning work with samples from multiple lineages? Are GISAID sequences from each lineage sampled equally up to a certain limit?
Why are both sample_lineage and lineage_report required options yet have default values of "" (empty string)? Doesn't that mean that they are optional parameters? What if both are set to None/""?

It looks like bin/prune_down_tree.py needs to be updated since it looks like it is assumed that all user input samples are related and belong to the same lineage:
https://github.com/nhhaidee/scovtree/blob/fa18e8ed8f4538c5719a907ddce00c8f6a4fb3d7/bin/prune_down_tree.py#L26
It also looks like user sequences could be pruned out of the final tree.

The drop_duplicates is typically used to get rid of duplicate entries in a Pandas DataFrame and pd.read_csv should be used with a CSV file instead of pd.read_table with sep='\t':
https://github.com/nhhaidee/scovtree/blob/fa18e8ed8f4538c5719a907ddce00c8f6a4fb3d7/bin/filter_gisaid_sequences.py#L78-L84
If you want the unique lineages you can either use the Pandas Series method unique or convert the Series to a Python set:
df_lineage_report = pd.read_csv(lineage_report)
lineages = set(df_lineage_report['lineage']) - set('None')

"None" is sometimes returned as the Pangolin lineage assignment when sequence quality is poor (too many Ns; sequence too short), so it may be a good idea to filter that value out just in case.

@peterk87 I updated the test with multiple lineages, the workflow is fine with small of numbers of taxa (< 100) because we don't need to filter and prune tree.
And yes, the prune tree down step has to be updated to handle multiple lineages., I have found the issue with that

@peterk87 What do you think when multiple lineages presented in the different part (different sub tree) in phylogenetic tree? For example, samples with lineage B.1.618 and B.1.1.7 will be in the different subtrees. The tree will be large when we visualise them together with shiptv.
Is it ok, if we visualise separate tree for each lineage?

shiptv_phylogenetic_tree.zip
Here is the result for small tree for you reference.

How do you think if we do sample with equally probabilities as below:
df_sample= df.groupby('Pango_lineage').apply(lambda x: x.sample(int((len(x)/len(df))*total_sample_size))) where total_sample_size=10000

I don't think that will work since it would be dropping small lineages, e.g.
# 10 samples in lineage
# around 500k samples belonging to all lineages filtered for
# only getting up to 10k total samples
int((10/500000)*10000)
# => 0
# no samples retrieved for this small lineage

I think it would be more appropriate to be biased towards including samples from the low abundance lineages before the larger lineages.

Is it ok, if we visualise separate tree for each lineage?

That would be a good output as well as well as showing all user sequences in the same tree.

Could you suggest quantity to determine low abundance lineages? I am thinking < 10% of total number of samples is considered as low abundance
I updated code to get all leaflist for user sequences so shiptv can visualize different subtrees together
https://github.com/nhhaidee/scovtree/blob/f45df37b278241cf110b06b0abf5bb77e3f15493/bin/prune_down_tree.py#L28-L38

It looks like the first taxa in the list will be preferentially added to the clade_neighbors set. Also the user's sequences may be excluded if clade_neighbors is filled up.
It may be better if neighboring taxa could be added in a kind of round-robin style one at a time until the max taxa to show is reached. I think this would require computing the distance of each user sequence taxon to neighboring taxa up to max_taxa (similar code to above to generate distances; see Phylo Tree/Clade distance method (looks very slow so you probably want to limit how many distances are calculated as much as possible)). Iteration through all user taxa adding nearest neighboring taxon until number of taxa equals max_taxa.

FYI I am testing the workflow with my own data to see if it does what I expect it to. I'm also working on a PR with some changes I'd like you to review.

Test cases:
Sample Lineages in GISAID  B.1.2 (> 100,000 sequences); B.1.617.2 ( > 37,000 sequences); B.1.618 ( > 180 sequences)
Input sequences: B.1.2 has 2 sequences, B.1.617.2 has 1 sequence, B.1.618 has 1 sequence
Test Case 1: 2 input consensus sequences belong to B.1.2 lineage (Passed)
Test Case 2: 1 input consensus sequence belong to B.1.617.2 lineage (No Run)
Test Case 3: 1 input consensus sequence belong to B.1.618 lineage (Passed)
Test Case 4: Mix consensus sequences (B.1.2 + B.1.617.2) (No Run)
Test Case 5: Mix consensus sequences (B.1.2 + B.1.618) (No Run)
Test Case 6: Mix consensus sequences (B.1.617.2 + B.1.618) (Failed)
Test Case 7: Mix consensus sequences (B.1.2 + B.1.617.2 + B.1.618) (Passed)
Test Case 8: test_gisaid, test_gisaid_custom (Passed)
Test Case 6 Failed with SHIPTV Process with error RecursionError: maximum recursion depth exceeded while calling a Python object. Please see log file
comman_shiptv.log
I will double check test case 6 again.


Issue with xchain-litecoin and xchain-dogecoin

I often receive these error in spite of having enough balance, most of the time with litecoin.
And also receiving no provider able to get GetUnspentTx

@hippocampus-web3
are you able to have a look at this one pls

Yes, let me review it @Thorian1te

Hello @sectionshankar,
Which data provider are you using for Litecoin and Dogecoin?
The error message no provider available for GetUnspentTx suggests that there's an issue with the data provider, probably the rate limits on their endpoints on the free tier.
By default, if you don't specify a provider when initializing the client, you'll be using Blockcypher. If you're not using a paid API key, you might be hitting their rate limit. You can review the limitations of their service here.
You have three options:

Modify your code to reduce the number of requests per second/day to stay within the free tier's rate limits.

Purchase a Blockcypher API key with a higher rate limit. Note that Xchain allows you to set a custom API key for data providers.

Alternatively, you can use Sochain in place of Blockcypher. However, keep in mind that they don't offer a free tier, so you'll need to purchase an API key.

Please let me know if this clarifies things for your situation. If you need assistance with any of these solutions, don't hesitate to reach out.

I closed the issue, if you have any problem related to that don't hesitate to reopen it. Thanks! @sectionshankar

I think the reason is the same, the problem with rate limit in API providers but the error message 'Insufficient balance' is not descriptive we will improve the error message for that case

@hippocampus-web3 @Thorian1te any work on this? Fixing or improving the message?

Thanks for the reminder. Let me reopen this issue and address an improvement on the messages right now

@sectionshankar Finally a deeper problem with UTXOs spending has been found and solved, there is still a bug to be solved in case you want to spend the total funds in the wallet but for the rest of the cases you should no longer get the error message 'Insufficient funds' if there are funds in the wallet. The change will be published with the next version, Thanks for reporting this bug 🙏


GraphQL subscriptions code

TODO:

[x] Update CHANGELOG.md with your change
[x] Make sure all of the significant new logic is covered by tests
[x] Rebase your changes on master so that they can be merged easily
[x] Make sure all tests and linter rules pass

Why close this?

I'm just doing some npm shenanigans with it right now, so I figured I'd reopen the PR when it's presentable again


[IMPROVEMENT] CI validates conventional commits

Is your improvement request related to a feature? Please describe (👍 if you like this request)
Longhorn currently doesn't have rules for titles and messages of commits. To make the commit more organized, we can support conventional commits. More information is in https://www.conventionalcommits.org/en/v1.0.0/.
Furthermore, we can introduce GitHub Actions for conventional commits.
Describe the solution you'd like

Describe alternatives you've considered

Additional context

cc @longhorn/dev

All are merged.


Call from Home Assistant and GPU issue

Hi there all,
I have just installed the docker version os FWS and if I understand is use uses faster-whisper as its backend.
Before I had installed faster-whisper and was working for calls from Home Assistant.
But this time the calls is not working...
Is there something I miss please ?
Can be that the Faster Whisper Server don't have the Wyoming protocol ?
Also it didn't find my GPU using same compose script like in faster-whisper (where the GPU it's work?
Thanks a lot.
Denis

Can be that the Faster Whisper Server don't have the Wyoming protocol ?
Correct, this project doesn't support it. Instead this project provides an OpenAI-compatible API

Also it didn't find my GPU using same compose script like in faster-whisper (where the GPU it's work?
If you are using Docker, you'll need to configure it to detect GPUs. See this


feb 26 updates

added 1042 data/model/script
redid initialization step with gamma=2
such that the initial model is changed
the positions are changed (origin of coordinate system changed)
gamma is sampled from a prior gamma=2.0\pm0.1 in the scripts

Hi Ryan, I can't merge these commits because of the conflicts with the main branch. Can you please resolve them by copying the psj1606.py file in the main branch into your fork, and then pushing this version to github? I don't think you need to change anything in those files

@rekeeley you don't need to update the 1606 model class as I already included an approrpriate initial lens model based on the JWST image positions and the satellite galaxy (when you include the satellite galaxy the Einstein radius is 0.63). please just copy the 1606 model class from the main branch


Exception with Multi-Lang

Hi
I use Imager for every CraftCMS project and I'm really in love with your plugin. Thanks for this!
Today I started a new project with Multi-Lang. After the installation and setup of the languages (DE is default and EN is 2nd), I'm running every time in this exception (image):

For a better insight in my problem, I reproduced a example in this repo: imagerMultiLang.
I really hope you can help me, because it's a customer project and I'm already in delay. ;-)
Thanks and Cheers from Switzerland,
Selim

There seems to be a problem with the setup of your asset sources. The error indicates that Imager can't find the source file in .../imagerMultiLang/public/en/uploads/images/content/. I guess what you want is to have the uploads in .../public/uploads/..., not .../public/en/uploads.., .../public/de/uploads... etc?
How is your file system path and url set up on this asset source?

I use HeartyConfig for CraftCMS. In my general.php is this UploadPath defined:
'uploadPath' => PUBPATH . 'uploads',
'uploadUrl' => CRAFT_SITE_URL . 'uploads',

And in this setup is in the AssetSource:

I figured it out with some help. With this settings in general.php, it works:
'uploadPath' => BASEPATH . 'public/uploads',
'uploadUrl' => CRAFT_SITE_URL . 'uploads',

Thanks anyway,
Selim

I figured it out with some help. With this settings in general.php, it works:
'uploadPath' => BASEPATH . 'public/uploads',
'uploadUrl' => CRAFT_SITE_URL . 'uploads',

Thanks anyway,
Selim


Replace existing plots

To prepare for pool-plotting, many ppl will replace they current pools with new ones that are poolable.
We need an easy setup that allows to delete a plot shortly before one is finished, so that we utilize available space most efficiently.

Main logic:

Define "DenomForOutDrivesToReplot" in config

Define "Replot" = "true" in config

Upon Start-PlotoSpawns, it launches the function "Get-PlotoReplots:

It monitors for active Jobs that are about to finish.
When a jobs reaches Phase 4 and it has "Replot" option enabled and its OutDrive matches denom for
"DenomForOutDrivesToReplot":
It deletes the oldest plot on that Drive to make space for the new one.


Validation errors on discriminated unions reference the union subtype

Discussed in https://github.com/samuelcolvin/pydantic/discussions/3918
After thinking about this a bit more, it feels to me like this is probably a bug, so creating a new issue out of it.

Originally posted by senko March 20, 2022
If there's a validation error for a sub-model in a tagged union, the error location includes the sub-model name. Is this intentional?
Code:
from typing import Union, Literal, List
from typing_extensions import Annotated
from pydantic import BaseModel, validator, Field

class CharField(BaseModel):
    type: Literal["char"]
    txt: str

    @validator('txt')
    def validate_str(cls, v):
        raise ValueError("some error")

class IntField(BaseModel):
    type: Literal["int"]
    value: int = 0

MyField = Annotated[Union[CharField, IntField], Field(discriminator='type')]

class MyModel(BaseModel):
    fields: List[MyField] = []

data = {
  "fields": [
    {
      "type": "char",
      "txt": "whatever"
    }
  ]
}

MyModel(**data)

This results in a validation error (that's expected) with a location that references CharField (that's unexpected):
pydantic.error_wrappers.ValidationError: 1 validation error for MyModel
fields -> 0 -> CharField -> txt
  some error (type=value_error)

For comparison, if I use the submodel directly:
class MyModel(BaseModel):
    fields: List[CharField] = []

the error is like this:
pydantic.error_wrappers.ValidationError: 1 validation error for MyModel
fields -> 0 -> txt
  some error (type=value_error)

I believe that code that does this is here, it appends the subtype.
Now my question is: is adding the subtype the expected (intentional) behaviour? I can't any specific reference to that in the docs so I'm not sure if that's fine or a small bug. If it's a bug, I'd be happy to make a PR to fix it.
Thanks!

i'm facing a similar issue, and it makes it hard to create nice error messages from the pydantic.ValidationError.errors(), since the loc is messy. i'm not 100% sure if it is a bug or intended, but for my use case i would say it's a bug. toy exmaple:
import typing as t

import pydantic

class RedCat(pydantic.BaseModel):
    type: t.Literal["cat"] = "cat"
    subtype: t.Literal["red"] = "red"
    age: int

class BlueCat(pydantic.BaseModel):
    type: t.Literal["cat"] = "cat"
    subtype: t.Literal["blue"] = "blue"
    age: int

Cat = t.Annotated[t.Union[RedCat, BlueCat], pydantic.Field(discriminator="subtype")]

class RedDog(pydantic.BaseModel):
    type: t.Literal["dog"] = "dog"
    subtype: t.Literal["red"] = "red"
    age: int

class BlueDog(pydantic.BaseModel):
    type: t.Literal["dog"] = "dog"
    subtype: t.Literal["blue"] = "blue"
    age: int

Dog = t.Annotated[t.Union[RedDog, BlueDog], pydantic.Field(discriminator="subtype")]

Pet = t.Annotated[t.Union[Cat, Dog], pydantic.Field(discriminator="type")]

class Person(pydantic.BaseModel):
    pets: tuple[Pet, ...]

try:
    Person.parse_obj({"pets": [{"type": "cat", "subtype": "red", "age": "eleven"}]})
except pydantic.ValidationError as e:
    print(e.json())

output is
[
  {
    "loc": [
      "pets",
      0,
      "Union[RedCat, BlueCat]",
      "RedCat",
      "age"
    ],
    "msg": "value is not a valid integer",
    "type": "type_error.integer"
  }
]

whereas i was hoping for
[
  {
    "loc": [
      "pets",
      0,
      "age"
    ],
    "msg": "value is not a valid integer",
    "type": "type_error.integer"
  }
]

We are using Pydantic to validate configuration in yaml files, and are using loc to figure out the line number something was wrong.
We have configuration in the style of:
auth:
  identificationBackends:
    - type: local
      path: /some/file.txt
    - type: ldap
      host: localhost
      port: 389

When reading the yaml, we have a dictionary looking like:
{
  'auth': {
    'identificationBackends': [
    {
      'type': 'local',
      'path': '/some/file.txt',
      '__line__type': 5,
      '__line__path': 6
     }.
     {
      'type': 'ldap',
      'host': 'localhost',
      'port': 389,
      '__line__type': 11,
      '__line__host': 12,
      '__line__port: 13,
     }
    ]
  }
}

where the items in the identificationBackends are a discriminated union based on type.
If, for example, the port is 'asd', we'd expect the error to look like
[ { "loc": ["identificationBackends", 1, "port" ] },
which allows us to easily step through the structure we have containing line numbers. Instead we get
[ { "loc": ["identificationBackends", 1, "LdapConfiguration", "port" ] },
which makes things a great deal messier.
The only solution I can currently think of is to simply keep a list of all the class names that are used in discriminated unions and then skip that index of loc. That would presumably work, but this will obviously not scale well.

This is intentional behavior, it can be useful to have the class name in there as well. I'm not sure we want to change this without broad community consensus, someone would be unhappy either way.

Would it be feasible to make this a configurable feature (even defaulting to the current behavior of including the class names if that's the broader community desire)
We have a similar use case where we'd like to index through a validation error associated with an api request object to identify which section of the error was at fault.
loc almost solve this case with the key exception being discriminated union subtypes being injected as non-traversable elements into the loc tuple.
Eg. something like
class Config:
   skip_non_traversable_keys_in_error_loc = True

@senko did you find at least any workaround? Currently it is completely not working for us as we cannot return to the client error like "__root__.MyDiscriminatedModel.field" cannot be None instead of "field" cannot be None

I'm not working around the issue at the moment since it's in our internal API so it's not a big problem, but we do some postprocessing to remove __root__ and if it was something we wanted to publish/document to externals, I'd similarly remove the extra referenece as a workaround.
As per @adriangb 's comment, if it's intended behavior, I think it's okay for us (users who need to change the output) to rely on this working as it is currently working and manually post-process the error. I can empathize with not being able to satisfy everyone :)


Test

This PR/issue should be against a repo in the org of your module e.g.,  nus-cs2103-AY1819S1 or nusCS2113-AY1819S1, not against the repo in se-edu org :-)
Closing...


Migrate perf-tests to Go modules

Yesterday I tried to release new version of perfdash, but failed to build a binary locally due to a missing dependency. I had a look into dependencies and it's a mess. We still use Godeps, which are now deprecated in favor of Go modules. We should migrate to go modules fully, drop support for Godeps and possibly ditch 'vendor/' dirs too (@mm4tt is there any reason we keep them?).
There are couple of reasons for migrating to Go modules fully and dropping support for Godeps.

perfdash can't be built without local changes to Makefile.
Little visibility into dependencies version (Godeps.json is way less readable).
Vast majority of dependencies is old. perfdash code still relies on v1.11.0-alpha.0-2155-g80bd7510df of k/k
godep is required to run perfdash tests. With Go modules we can use bare go.
Tests run via Makefile under perfdash/ are run differently than ones in presubmit.

The only issue with migrating to go modules might be with relying on k/k as a module (https://github.com/kubernetes/kubernetes/issues/79384). There are existing workaround though.
/priority critical-urgent

In general, I'm in favor of this change.
I don't think it's critical-urgent, though. Everything seems to be working (I'm quite sure that building perfdash works if you use proper go version and disable GOMODULES). And it definitely works without any issues for clusterloader2.
Downgrading the priority to important-soon
/priority important-soon
IIRC, we still have vendor dirs in some places because of the travis presubmits. But we know what to do to solve that problem (we should migrate our presubmits to prow, @jprzychodzen created one for building stuff that allowed us to get rid of vendor dir for probes/ and access-token util).
Janek, do you want to do it? Alternatively, I think it could be a good first issue (assuming we limit the scope somehow, e.g. to starting with perf-dash). In that case we should lay out a better plan.

/remove-priority critical-urgent
With https://github.com/kubernetes/perf-tests/pull/1100 merged, this is indeed not that urgent, as we will be able to again build perfdash at HEAD.
I tried to check if this can be done with a simple PR, but I think there is more work needed to make sure we don't break anything. I could prepare a plan on how to do it, what is exactly in the scope (e.g. migration off Travis to Prow) and then we can discuss timeline. I suspect most of the work from the plan, could be a "good first issue" then.

Sounds good, thanks!

/remove-lifecycle stale
@mm4tt - has this been finished?

I know we migrated some things (like ClusterLoader), but the question is whether we upgraded all.

We haven't migrated all. There are some that we'll probably never migrate, like benchmark or compare tools. But, we should definitely migrate perf-dash as we're using (building) it a lot.

/remove-lifecycle stale
/lifecycle frozen

@mm4tt @wojtek-t I would like to take stab at it.
/assign

Note that it's partially done already - most of dirs are already migrated. There are one or two remaining IIRC.

In perf-tests currently I just see go.mods everywhere, although there is a /vendor directory in dns/dnsperfgo.
Is there more to do here still, or can this issue be closed?


New Terminator package using Python 3

Project description
terminator is already packaged in nixpkgs, but the upstream project has been taken over by new maintainers who have ported it to Python 3 and are continuing development. As far as I know this new version is also used by Debian/Ubuntu (it has python3 dependencies in those distros).
I have a local attempt at a new derivation and it Works For Me™, but it has a patch in it which I don't think it should need. Also, maybe the original maintainer @bjornfor may want to do the update? If desired I can open a PR with my current state of affairs.
Metadata

homepage URL: https://github.com/gnome-terminator/terminator
license: GPL2
platforms: Linux

I have limited spare time these days (months), so please be my guest 😀


Rev proxy loses user information?

@scottx611x : Does this sound right?
With revproxy, django user information is being lost: If I remember correctly, the first request against an app works, but subsequent requests have lost their user, and so on Refinery they don't have privs any longer.
My thinking is that there are two first steps that can be done in parallel:

What exactly is going wrong with the requests on Refinery? Capture the headers of a conversation that works, and of one that fails. (@scottx611x : could you help with this part?)
Add users to the demo, and try to capture the same problem in a simpler context.

Believe this was actually a probably with how requests were made in one particular application. Resolved here: https://github.com/hms-dbmi/higlass/pull/270


Fix docs error

😳

Coverage remained the same at 97.418% when pulling 2f75c72fc9971a0e2d9357f4f41fcda65d68905f on docs-patch into 80916636eca9472ed1b3c3129cee07028f36ca5d on master.

oops


feat(Algebra/BigOperators/Order): prod_lt_prod

Add a product variant of mul_lt_mul, following the pattern of Finset.prod_lt_prod'. This fills in a gap between Finset.prod_le_prod, Finset.prod_le_prod' and Finset.prod_lt_prod'.

I'm fine with both options 1 and 3. Let's merge this now, and feel free to open a new PR doing 3.
bors merge


fixes #205

I did not ran the lesson7-wgan notebook to not lose the outputs, but it should be working.
I remove the _ from the files, since they are now working =)

There are a bunch of changes in the files, but I think that's because it was a while since the notebooks were built. The only I think I changed was adding ds_idx=0 to show_results

Thanks for the fixes!


center_x not working with MDLabel

Description of the Bug
While setting the center_x in pos_hint for the MDLabel, the MDLabel does not move to the correct place.
Code and Logs
from kivy.lang import Builder

from kivymd.app import MDApp
from kivymd.theming import ThemeManager

KV = """
FloatLayout:
    Label:
        text: "Kivy"
        pos_hint: {"center_x":.5,"center_y":.5}
    MDLabel:
        text: "KivyMD"
        pos_hint: {"center_x":.5,"center_y":.5}

"""

class Test(MDApp):
    def build(self):
        ThemeManager.theme_style = "Dark"
        return Builder.load_string(KV)

Test().run()

Screenshots

Versions

OS: Windows
Python: 3.7
Kivy:  v2.0.0rc3
KivyMD: v0.104.1

@RealHarmZ halign: 'center'


Use filenames to compute set of files to publish line coverage for

Use file names instead of paths to match coverage entries with changed files from diffs
More reliable for projects like Android that do not use the full file path in the coverage.xml to specify classes

Tests?

Added tests

Also tested locally via mvn hpi:run before and after this change on an android project. The current state of the plugin is good for java/groovy/go projects. Only android coverage xmls had this issue which the PR fixes

Looks good, feel free to merge after travis


Training the Phenaki - RuntimeError: CUDA error: device-side assert triggered

I have created a notebook and pasted the training code from the README.md file so that I can experiment with training the model, but I encounter the following error when training the Phenaki. is there anything I'm doing wrong.
The same error emerges both on Google Colab and  AWS EC2 - p4d instance with 8 A100 GPUs.
Here's the error I getting:
<@beartype(phenaki_pytorch.phenaki_pytorch.Phenaki.forward) at 0x7fd70d61cf70> in forward(__beartype_object_94770277747520, __beartype_getrandbits, __beartype_get_violation, __beartype_conf, __beartype_func, *args, **kwargs)

[/content/phenaki-pytorch/phenaki_pytorch/phenaki_pytorch.py](https://localhost:8080/#) in forward(self, videos, texts, video_codebook_ids, video_frame_mask, text_embeds, cond_drop_prob, only_train_generator, only_train_critic)
    642         if not only_train_critic:
    643             loss = F.cross_entropy(
--> 644                 logits[mask_token_mask],
    645                 video_codebook_ids[mask_token_mask]
    646             )

RuntimeError: CUDA error: device-side assert triggered
CUDA kernel errors might be asynchronously reported at some other API call, so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.
Compile with `TORCH_USE_CUDA_DSA` to enable device-side assertions.

how did you fix this error

who is a legendary python coder here?

how did you fix this error

When you're setting up the Phenaki, you need to specify the correct number of num_tokens  in the MaskGit instance.
maskgit = MaskGit(
    num_tokens = 5000,  #This is the source of error if not set correctly for the corresponding cViViT.
    max_seq_len = 1024,
    dim = 512,
    dim_context = 768,
    depth = 6,
    unconditional = False
)

phenaki = Phenaki(
    cvivit = cvivit,
    maskgit = maskgit
).cuda()

I replaced the 5000 with codebook_size from cViViT.  the error was gone.


Add helpers methods for opening message boxes, prompts and confirms programatically

Having used the Element component library in the past, it would be nice if uiv would offer some helpers methods for displaying message boxes, prompts and confirms like in http://element.eleme.io/#/en-US/component/message-box. Ideally, the methods would return a promise that is rejected on cancel / dismiss and resolved on OK; in case of a prompt, with the entered user value as argument.

Hi.
I'm a fans of element ui! I also love this feature. It will be implemented.

ref commit: 2b787e07418ef7bebcac0a86b44e12053dc6d9df
just forgot to add issue ref while commit (not finished yet).
It will be released on next MINOR version.

One more thing, can you add the possibility to customize the classes of the buttons? For delete prompts, I want to make the confirm button red for example by giving it the btn-danger class. :)

It's done. Release comming in this weekend.


Fixed duplicate employee bug

Coverage decreased (-0.4%) to 56.28% when pulling 3b5a24345be2b52f78dfb8c88366a353a79e9244 on kianhong95:DuplicateEmpBug into f32dce64fbfbb543dec660df3deca223995e1414 on CS2113-AY1819S1-F09-2:master.

Resolve #162, #159
Please update UG-DG to state that duplicate employee names are not allowed


update catalog name to match item name in CentOS source comlilation with english version

Modify the catalog name and the name of the small project is consistent with the reader is clearer

direct translation won't make the expression better
thanks for your contribution


fix: downgrade poetry to 1.1.4

Issue #, if available:
Description of changes:

Checklist

[ ] Meet tenets criteria
[ ] Update tests
[ ] Update docs
[ ] PR title follows conventional commit semantics

Breaking change checklist

RFC issue #:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@heitorlessa i assume you will track this regression bug and revert this when it is fixed.


Enhancement to delete_snapshots

This will not work on SunOS platforms, so I've changed some bits:

the timestamps used in snapshots list are UNIX timestamps now (-p parameter) for easy comparison
the absolute oldest date computation is added for SunOS platform
the "from " is not outputted anymore, because it is not in the snapshots list

--- delete_snapshots.sh Sat Dec  5 10:03:02 2015
+++ /opt/custom/sbin/delete_snapshots   Sat Dec  5 10:02:00 2015
@@ -79,6 +79,8 @@
   platform='bsd'
 elif [[ "$unamestr" == 'Darwin' ]]; then
   platform='bsd'
+elif [[ "$unamestr" == 'SunOS' ]]; then
+  platform='sunos'
 else
   echo -e "unknown platform $unamestr 1>&2"
   exit 1
@@ -93,6 +95,8 @@

 if [[ "$platform" == 'linux' ]]; then
 compare_timestamp=`date --date="-$(echo $compare_seconds) seconds" +"%s"`
+elif [[ "$platform" == 'sunos' ]]; then
+compare_timestamp=$((`date +"%s"` - $compare_seconds))
 else
 compare_timestamp=`date -j -v-$(echo $compare_seconds)S +"%s"`
 fi
@@ -99,7 +103,7 @@

 # get a list of snapshots sorted by creation date, so that we get the oldest first
 # This will allow us to skip the loop early
-snapshots=`zfs list -H -t snapshot -o name,creation -s creation | grep $pattern`
+snapshots=`zfs list -H -t snapshot -o name,creation -s creation -p | grep $pattern`

 if [[ -z $snapshots ]]; then
   echo "no snapshots found for pattern $pattern"
@@ -112,14 +116,8 @@
 IFS=$'\n'
 for line in $snapshots; do
   snapshot=`echo $line | cut -f 1`
-  creation_date=`echo $line | cut -f 2`
+  creation_date_timestamp=`echo $line | cut -f 2`

-  if [[ "$platform" == 'linux' ]]; then
-    creation_date_timestamp=`date --date="$creation_date" "+%s"`
-  else
-    creation_date_timestamp=`date -j -f "%a %b %d %H:%M %Y" "$creation_date" "+%s"`
-  fi
-
   # Check if the creation date of a snapshot is less than our compare date
   # Meaning if it is older than our compare date
   # It is younger, we can stop processing since we the list is sorted by
@@ -130,10 +128,10 @@
       echo "DELETE: $snapshot from $creation_date"
       zfs destroy $snapshot
     else
-      echo "WOULD DELETE: $snapshot from $creation_date"
+      echo "WOULD DELETE: $snapshot"
     fi
   else
-    echo "KEEP: $snapshot from $creation_date"
+    echo "KEEP: $snapshot"
     echo "No more snapshots to be processed for $pattern. Skipping.."
     break
   fi

Would you mind pasting a copy of the script with the changes?
This is breaking for me when trying to run on Solaris 11.4 December 2020 SRU.

I've moved away from Illumos for 5 years now :)


Spark configuration for local deployment

Identify key configuration for Spark running local on a container. Adjust the JVM spin up cost ,maximize the memory capacity in AWS Lambda and reduce the container size.

Best architecture to deploy a set of spark configuration to Script
Decision at conf file or conf setting in the pyspark script. Ensure that the spark configuration is not overwritten
JVM spin up, Memory/storage fraction, Serializer
Caching and checkpointing to reduce memory foot print. Ensure that it spillover to disk instead of memory.
Dynamically assign the CPU and memory based on the machine that AWS Lambda picks up.

Closing this


checkout branch

According to the code in the book, git checkout branch failed. Only two branches now. Having you executed git checkout code-3.1 ????

code-3.1是一个 tag   看了一下是有的，你可以再试试，看看是不是没有把tag 信息拉下来


mini.files: file deletion upon undoing rename operation

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md
[X] I have updated 'mini.nvim' to latest version

Module(s)
files
Description
After renaming a file and confirming the change, attempting to undo and then reconfirming will result in the file being deleted. This has led to many issues in large-scale codebase refactoring, among others.
Neovim version
NVIM v0.10.0-dev+1974-g714b07519
Steps to reproduce

Create two files, hello.c and hello.h.
Rename hello.c to main.c and confirm the change.
Undo the previous rename operation and confirm.
Observe that our file is now deleted.

Expected behavior
Undoing a file rename should not result in file deletion; rather, main.c should revert to being hello.c.
Actual behavior
Screencast from 2024-01-15 11-54-09.webm

Thanks for the issue!
I can indeed confirm. The reason this happens is because of how 'mini.files' tracks which operation need to be done. Here is what is going on:

Initially explorer contains lines of something like /1/hello.c and /2/hello.h. Here 1 and 2 are unique path identifiers which are stored for each session.
First renaming is deduced when synchronizing the following lines: /1/main.c and /2/hello.h. 'mini.files' sees that the file 1 doesn't match what it has stored and deduces that file should be renamed. And successfully renames. Lines after that are /2/hello.h and /3/main.c as 'main.c' is a different path on disk.
Now, after undo lines are the same as they were initially. During synchronization 'mini.files' sees that file 3 was present and now is missing thus deciding it needs to be deleted. I think it should also suggest creating file 2 in this situation, but it does not.

I'll see what is the best approach in this situation.

Thanks again for opening the issue! This should be fixed on latest main.

Thanks again for opening the issue! This should be fixed on latest main.

I confirm, thank for the quick fix!


Comments AwsLimit variable to conform with Go linting best practices

Adds a comment to exported variable AwsLimit to conform with Go linting best practices.
Also removes a single trailing white space.
Signed-off-by: Christopher Collins<EMAIL_ADDRESS>

/assign @jharrington22
James, would you mind approving this when you get a chance, no rush.  Just cleaning up a linter issue.


Add random cheatcode

#423 adds managed_random infrastructure which exposes deterministic and externally configurable PRNG for entire test run.
With it, it is very trivial to expose Pythonic Random object in hints, so that users can reliably use low level random APIs in their tests.
Question: Is there a legitimate use case for this cheatcode though?
func test_random():
    local a
    %{ ids.a = random.uniform(1, 10) %}
    assert_not_eq(a, 0)
end

Not needed. Python's random module is already usable.


Enable insecure connections to DICOMweb endpoints

Hi,
it would be really nice to add an verify_ssl attribute to the DICOMwebClient for servers with self-signed certificates.
This should be pretty straightforward to do by adding the verify=True/False parameter to all requests calls.

From the requests documentation:

Note that when verify is set to False, requests will accept any TLS certificate presented by the server, and will ignore hostname mismatches and/or expired certificates, which will make your application vulnerable to man-in-the-middle (MitM) attacks.

Given the security vulnerabilities, I am reluctant to expose that functionality via the API and thereby encourage users to do that. However, you should be able to set verify=False yourself on the session object before passing it to the DICOMwebClient constructor. Have you tried that?

Closing this issue due to inactivity.


Fix threaded loading issues

Race condition related to semaphore when a task is switching to another resource.
Lack of a way to await for load tasks started in non-thread-aware contextxs.

Slimmer alternative to #73647. That one was likely more efficient, but it probably will not be noticeable in practice.
Fixes #71726.

@mrTag, taking advantage of your kindness, would you test this one, please?

@RandomShaper I ran the scene loading in our game around 50 times with this branch now. The "referenced nonexistent resource" didn't occur once. So the "Lack of a way to await for load tasks started in non-thread-aware contexts" seems to be fixed.
I did run into the race condition ONCE, in the beginning of my testing. I wanted to reproduce it and attach a debugger to check the threads, but it didn't occur again, even though I tried it lots of times.
So I would say: this commit definitely fixes problems and the (very) rare possibility of a race condition shouldn't deter you from including it in 4.0 (plus: the race condition occurs more often without this commit)
I will use https://github.com/godotengine/godot/pull/73647 for our game, though, since I really like the solution with the conditional and didn't have any problems with it in our concrete case.
Thanks @RandomShaper!

@mrTag, thank you very much for testing it!
Whether it will be included in 4.0 or not is now up to Project Management, so to speak. I wanted to offer a safer path with this PR, but I will trust their judgement on how to proceed.

I think the original PR was better, since using a RefCounted just for a semaphore is a bit overkill.

Superseded by #73647.


Allow stubgen recursively from CMake

As always, pypy3.9 decides to randomly fail during test ¯_(ツ)_/¯

Looks like pypy has newer release (v7.3.15), perhaps updating it in ci.yml would solve this problem?

Good idea, I will try 🤞
Regarding the PR: RECURSIVE does not necessarily require OUTPUT_DIR to be specified. In that case, stubgen will place the generated stub directly into the module directory, which I daresay is usually what you want. Perhaps you could mention this in the documentation RST file?

But what if user specify both --output-dir and --output-file?

That combination doesn't make sense. And output file with recursive also doesn't make sense. (Indeed, stubgen also has some checks for this inside). I was just referring to a part of the text in the docs you wrote that seemed to suggest that RECURSIVE requires OUTPUT_DIR.

Please check!

I'm still pondering the best API to expose stub generation in Python.
For example, I think that there is a way of getting RECURSIVE to work even when not using INSTALL_MODE. However, CMake would need to be told which output files are generated as part of the traversal. So in that case, there would be two main ways of building stubs:
nanobind_add_stub(
    ...
    MODULE my_ext
    OUTPUT_FILE my_ext/__init__.pyi
)

and
nanobind_add_stub(
    ...
    MODULE my_ext
    RECURSIVE
    OUTPUT_FILES my_ext/__init__.pyi my_ext/submodule/__init__.pyi
)

If INSTALL_TIME is specified, then OUTPUT_FILE or OUTPUT_FILES is optional.
Once things are tracked at that level of granularity, here is nothing against allowing more modules as input even in non-recursive mode, e.g.:
nanobind_add_stub(
    ...
    MODULES my_ext_1 my_ext_2
    OUTPUT_FILES my_ext_1/__init__.pyi my_ext_2/__init__.pyi
)

You have mentioned that...

Some of my own nanobind-based projects are designed to be importable/usable from the build directory without requiring an extra install step

Do you have any examples of those projects?
I am not sure how those kind of project work, but maybe calling a python script from nanobind-config.cmake that recurse and find out what stub files should be generated would help?

In my opinion,

nanobind_add_stub(
   ...
   MODULE my_ext
   RECURSIVE
   OUTPUT_FILES my_ext/__init__.pyi my_ext/submodule/__init__.pyi
)

is less clean than
nanobind_add_stub(
   ...
   MODULE my_ext my_ext.submodule
   ...
)

If we cannot figure out how to find out what output files need to be generated for non-INSTALL_TIME, I think it is better for us to not implement RECURSIVE for that mode. Instead, we require user to specify MODULE one-by-one, and find out the OUTPUT_FILES automatically based on MODULE suplied by user. This should be easy with something like:
set(OUTPUT_FILES "")
foreach(M ARG_MODULE)
   string(REPLACE "." "/" M_NEW1)
   string(CONCAT ${M_NEW1} "/init.pyi" M_NEW2)
   set(OUTPUT_FILES "${OUTPUT_FILES} ${M_NEW2}")
endforeach()

There is a problem I see with the loop you posted:

set(OUTPUT_FILES "")
foreach(M ARG_MODULES)
   string(REPLACE "." "/" M_NEW1)
   string(CONCAT ${M_NEW1} "/__init__.pyi" M_NEW2)
   set(OUTPUT_FILES "${OUTPUT_FILES} ${M_NEW2}")
endforeach()

In a submodule my_ext.sub, how will you know whether to generate my_ext/sub/__init__.pyi or my_ext/sub.pyi? The difference is important especially in larger binding projects containing a mixture of Python and C++ code.
You were interested in knowing about a project that creates a build-time importable library. See the nanobind_v2 branch of the Dr.Jit project: https://github.com/mitsuba-renderer/drjit/tree/nanobind_v2. This is a project with very complicated bindings, it uses essentially all features of nanobind and is what caused me to start writing nanobind in the first place.

The first idea worked! Now it should be possible to recursively generate stub even for non-install time, and only generated if the source was changed.
I have made a new commit. To test, clone my fork, change tests/CMakeLists.txt
https://github.com/wjakob/nanobind/blob/df8996aafed8d891cbf1ac21bb828afc3f900ae1/tests/CMakeLists.txt#L70-L76
To the following:
nanobind_add_stub(
  py_stub
  MODULE py_stub_test
  # OUTPUT ${PYI_PREFIX}py_stub_test.pyi
  OUTPUT_DIR ${PYI_PREFIX}
  RECURSIVE
  VERBOSE
  PYTHON_PATH $<TARGET_FILE_DIR:test_stl_ext>
  DEPENDS py_stub_test.py
)

Now cmake build nanobind with test. py_stub_test.pyi should be regenerated only if py_stub_test.py was changed.
Only catch for this method is if py_stub_test.pyi was deleted, it would not be regenerated unless cmake from clean or changes done to py_stub_test.py

Interesting, I guess that makes sense and is reminiscent of dummy timestamp files used in Makefiles. One thing this won't do is clean up things correctly. (e.g. ninja --clean)

To mark file for deletion during ninja clean, the GENERATED property should be set for the .pyi file. Normally it is set if it is specified in OUTPUT of add_custom_command, but since we did not (could not) set OUTPUT, the property is absent  and the generated .pyi file is not deleted during clean.
One way is to use set_property() to set GENERATED for .pyi file, but I can't think of how. Thinking about this has used more time than I wanted to spend, and I am too busy to think about this problem further...
If there is no way we can mark the .pyi file for deletion during clean, would you still prefer this method? Or would you prefer the method of adding execute_process() before add_custom_command() and add_custom_target()?

This article saved us: https://discourse.cmake.org/t/how-to-cleanup-random-byproducts/3154
Please try the latest commit. Recursively generated files should be cleaned.

After some thought, seems like the second method of calling execute_process() before running add_custom_command() and add_custom_target() is not an option, as execute_process() is run during configuration time, which .py file and nanobind python modules are absent in the build directory, hence cannot be used for stubgen during configuration time.
Seems like the first idea is the best we can do...

Hi @laggykiller,
sorry about leaving this dormant for a long time. This PR went through a few different phases and I was wondering:

What are the benefits and downsides of the current approach? As far as I can tell, you write a dummy file that helps compute the staleness of outputs. This makes it unnecessary to specify an output file during stub generation. Are these dummy files only used in certain circumstances or always?
You mentioned having added a solution for cleaning files but with some limitations ( Recursively generated files are cleaned reliably (Ninja) or from second time onwards (Unix Makefile)) -- is that still part of the PR? It's a downside if things aren't cleaned up but not a deal-breaker.
Is it still possible to specify explicit file outputs and retain the current functionality?
Why does the commit mention that recursive mode is only available at install time?

What are the benefits and downsides of the current approach?

Currently this PR allow RECURSIVE mode to be used whether INSTALL_TIME is set or not (Sort of), which is a benefit.
The downsides are:

Recursively generated files are cleaned reliably (Ninja) or from second time onwards (Unix Makefile), which may feel buggy.
file(GLOB) has bad rep of being slow (https://discourse.cmake.org/t/is-glob-still-considered-harmful-with-configure-depends/808), but in my opinion the performance cost should not be significant?

Are these dummy files only used in certain circumstances or always?
Dummy files only used for non-INSTALL_TIME.

You mentioned having added a solution for cleaning files but with some limitations ( Recursively generated files are cleaned reliably (Ninja) or from second time onwards (Unix Makefile)) -- is that still part of the PR?
Yes it is part of the PR (5982f36)

Is it still possible to specify explicit file outputs and retain the current functionality?
Yes, if user uses OUTPUT instead of OUTPUT_DIR

Why does the commit mention that recursive mode is only available at install time?
I forgot to remove that sentence in the PR, fixed.

I was very busy and many things happened after my last comment here, so I may not remember all the details about the PR.

What is the status for this feature? This would be very useful for me and I hope you can find time to add it soon.


Update emoji list

data came from:
https://github.com/carloscuesta/gitmoji/blob/master/src/data/gitmojis.json

Thank you for your contribution ! ✨


SDK shutdown handling

Shutdown TODO notes extracted from "start.js":
// TODO sdk shutdown: also SIGINT?
// TODO sdk shutdown handlers: better log on err
// TODO sdk shutdown: make these handlers configurable?
//  - If so, could move these into sdk.js and it could use its logger for logging an error.
//  - Note, only want luggite.warn over console.warn if errSerializer gets
//    all attributes (console.warn shows more data for ECONNREFUSED)
// TODO sdk shutdown beforeExit: skip this for Lambda (also Azure Fns?)
// TODO sdh shutdown: call process.exit?
// TODO: Whether we have a signal handler for sdk.shutdown() is debatable. It
// definitely *can* change program behaviour. Let's reconsider.
// Note: See https://github.com/open-telemetry/opentelemetry-js/issues/1521
// for some thoughts on automatic handling to shutdown the SDK.

These should all be worked through.
My current thoughts are:

We should have shutdown handling by default for our basic/default use case.
We should provide a configuration option to turn off the signal handler(s) and mention this in troubleshooting and/or in the advanced/details section of the user guide.  This is because users can have legitimate other uses for SIGTERM, etc. and ours will conflict.  The docs for this option should show how a user using the golden path or a custom "instrumentation.js" can setup shutdown signal handlers.
We should add an equivalent handler for SIGINT and/or document why not.
We should document limitations on Windows and have separate later work to support controlled shutdown on Windows. Note (https://nodejs.org/api/process.html#signal-events) that SIGTERM and SIGINT are not supported on Windows. There is SIGBREAK, but I'm not sure of the default handler behaviour there.
Multiple shutdowns: When a MeterProvider is involved (and possibly in other cases), shutdown adds async tasks, so we get beforeExit again later. That results in calling sdk.shutdown() twice. Currently that isn't problematic (there may be a diag warn about this?), but we should be able to do better with a module-level global to only attempt to shutdown once.
The logging-related issues for shutdown handling and perhaps the Windows-related issues should be moved to a separate issue for later work.

Separate thing:

SHould we forceFlush metrics on shutdown? Currently upstream sdk-metrics does not, but it probably should and likely eventually will. See https://github.com/open-telemetry/opentelemetry-js/issues/5116#issuecomment-2459653864 https://github.com/open-telemetry/opentelemetry-specification/issues/2983#issuecomment-1458303448


John's data not appearing

Hi,
While running a job with JTR, the application is not able to pick up the status as its trying to find the .rec file. For some reason this file is not created in the right location and is also deleted automatically (somehow). This causes the resourced to return exit status 1 as its not able to find task with UUID (error 0093) even though the folder with the the UUID exists and there is a pot file with the cracked passwords.

@jmmcatee - Any thoughts on this one?

If you are referring to the time left to crack, then that is a bug I'm not sure how to fix at the moment. It might require us to drop Windows support because of how John handles Stdin. If you are talking about any status information, then it is likely an issue with the default john.ini file. I need to complete some testing on john and update the documentation.

Is this still an issue for you @roo7break ?

So there were a few things wrong here. One is that there was a bug in the John status code. Basically if you are only cracking one hash, then once you find it the job stops. This then breaks the command that checks status, so the hash was never checked. The latest commit  (a8c4692d19678aee67a0f42a5f5da7469772b424) should fix this. Additionally, status information should be work assuming you made some very poorly documented changes to the john.conf file. More information these changes can be found in the new tutorial John Tutorial. I will add them below for convienience.
The next step is to change the john.conf file that is used with one that will allow Cracklord to get status information from John.

Change Idle to Y
Change Save to 15
Change LogCrackedPasswords to Y

If those changes are made and you are running the latest code, then this should now work. Please note that John takes about 1-2 minutes to start display ETA, so that will not appear right away but my tests found it did come up after a bit. Please test and send me feedback.
Thanks!

In my tests, I can't show the ETA and progress with John the ripper. If I execute "john --status=example.rec" the output is similar to
StatusMatch=[0g 0:00:08:30  0g/s 11531p/s 11531c/s 11531C/s 0 0:00:08:30   11531 C/s]
But if I execute directly the command, the output is similar to:
Loaded 1 password hash (md5crypt, crypt(3) $1$ [MD5 128/128 SSE4.1 12x])
Will run 2 OpenMP threads
Press 'q' or Ctrl-C to abort, almost any other key for status
0g 0:00:00:26 0.00% (ETA: 2018-06-19 03:36) 0g/s 26988p/s 26988c/s 26988C/s Verdant..Verism
I tested in Windows and Ubuntu.

The status will not show up in Windows. For Ubuntu can you confirm you made
the necessary changes to the John.conf file? Also how long did the crack
run?
On May 30, 2016 9:36 AM, "klingsor83"<EMAIL_ADDRESS>wrote:

In my tests, I can't show the ETA and progress with John the ripper. If I
execute "john --status=example.rec" the output is similar to
StatusMatch=[0g 0:00:08:30 0g/s 11531p/s 11531c/s 11531C/s 0 0:00:08:30
11531 C/s]
But if I execute directly the command, the output is similar to:
Loaded 1 password hash (md5crypt, crypt(3) $1$ [MD5 128/128 SSE4.1 12x])
Will run 2 OpenMP threads
Press 'q' or Ctrl-C to abort, almost any other key for status
0g 0:00:00:26 0.00% (ETA: 2018-06-19 03:36) 0g/s 26988p/s 26988c/s
26988C/s Verdant..Verism
I tested in Windows and Ubuntu.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jmmcatee/cracklord/issues/83#issuecomment-222494309,
or mute the thread
https://github.com/notifications/unsubscribe/AAoUHHYZeWEVDln30MqG6DIXO639BFhwks5qGufugaJpZM4F9k43
.

Yes. I installed the deb with the version 1.0-beta-29-gc5e2878_amd64.deb.
Also, I recompiled John 1.8.0-jumbo-1 following your setup tutorial and I changed the john.conf with the values you indicated in the tutorial.
For testing, I used a simple md5-crypt: $1$364e1d82$hlPgM93BJY/PpJbJ/fdJT/ (plaint text is fr1endly).
With these changes, in the time to completion field I only see the message "Not Available".

Do you see "StatusStdout" in your logs? If your logs are set to debug then this should have the actual stdout of the john status call. I can see if you have some edge case for our parsing logic.

Here are my logs:

[2016-06-01 17:24:04.141983754 +0200 CEST debug] (johndict-tasker.go:261) Gathering task status                                              task=b9112e36-cab6-4a4e-8aa5-ff3a276fb622
[2016-06-01 17:24:04.224136581 +0200 CEST debug] (johndict-tasker.go:277) Stdout status return of john call                                  StatusStdout=0g 0:00:11:45  0g/s 42101p/s 42101c/s 42101C/s

[2016-06-01 17:24:04.224536766 +0200 CEST debug] (johndict-tasker.go:282) Regex match of john status call                                    StatusMatch=[0g 0:00:11:45  0g/s 42101p/s 42101c/s 42101C/s 0 0:00:11:45   42101 C/s]
[2016-06-01 17:24:04.224799975 +0200 CEST debug] (johndict-tasker.go:330) Speed calculated.                                                  mag=1 speed=42101

So the John output does not have an ETA there. Are you sure you are using
the same john.conf file for both? Cracklord runs as a different user. If
you 'su' into cracklord and execute John, does it give you the same output
as if you run it as your own user?
On Jun 2, 2016 2:40 AM, "klingsor83"<EMAIL_ADDRESS>wrote:

Here are my logs:
2016-06-01 17:24:04.141983754 +0200 CEST debug Gathering task status
task=b9112e36-cab6-4a4e-8aa5-ff3a276fb622
2016-06-01 17:24:04.224136581 +0200 CEST debug Stdout status return of
john call StatusStdout=0g 0:00:11:45 0g/s 42101p/s 42101c/s 42101C/s
2016-06-01 17:24:04.224536766 +0200 CEST debug Regex match of john status
call StatusMatch=[0g 0:00:11:45 0g/s 42101p/s 42101c/s 42101C/s 0
0:00:11:45 42101 C/s]
2016-06-01 17:24:04.224799975 +0200 CEST debug Speed calculated. mag=1
speed=42101
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jmmcatee/cracklord/issues/83#issuecomment-223208345,
or mute the thread
https://github.com/notifications/unsubscribe/AAoUHKTZpaf1hnP6fzxWBSD5EiHqidzwks5qHnrbgaJpZM4F9k43
.

I created the user cracklord and if I execute the same command that the app.., I can get the ETA. This is the example:

cracklord@dev-92-2-crk:/var/cracklord/87e35388-5c3f-4317-9489-e19577a8f7ea$ /usr/bin/jtr/john --format=md5crypt --session=87e35388-5c3f-4317-9489-e19577a8f7ea --pot=87e35388-5c3f-4317-9489-e19577a8f7ea.pot --wordlist=/mnt/dicts/languages/english/english.txt --rules=all /var/cracklord/87e35388-5c3f-4317-9489-e19577a8f7ea/hashes.txt
Loaded 1 password hash (md5crypt, crypt(3) $1$ [MD5 128/128 SSE4.1 12x])
Will run 2 OpenMP threads
Press 'q' or Ctrl-C to abort, almost any other key for status
0g 0:00:00:05  0g/s 3455p/s 3455c/s 3455C/s ascript..ashlar's
0g 0:00:00:10 0.00% (ETA: 2029-11-27 06:43) 0g/s 6171p/s 6171c/s 6171C/s cotillion..cottonizes
0g 0:00:00:12 0.00% (ETA: 2029-05-26 01:15) 0g/s 6478p/s 6478c/s 6478C/s diorthosis..diphthonged


Length of Longest sub array without repeating characters (Window Sliding)

Description 📜
To find the Length of Longest sub array without repeating characters by Window Sliding method.
Fixes #1283

Type of change 📝

[x] Doc#umentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] Competitive #Programming

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

@ravireddy07 Please review my PR.