provision-openssh.ps1 fails when run from autounattend

I noticed OpenSSH not being installed even though the builds ran through fine. In the setupact.log everything seems to be fine. When run manually the script runs through without problems as well. I don't know how to get more verbose logging :/
My workaround so far is to comment it out in provision-autounattend.ps1 and run it as a packer provision step.
Edit: oh, that fails as well with curious reasons for doing so:
==> proxmox-iso.windows-10-21h2-amd64: Provisioning with powershell script: ../scripts/provision-openssh.ps1
2023/04/11 19:48:12 packer-provisioner-powershell plugin: Opening ../scripts/provision-openssh.ps1 for reading
2023/04/11 19:48:12 packer-provisioner-powershell plugin: Uploading env vars to c:/Windows/Temp/packer-ps-env-vars-64359d5c-af82-c4bb-31a9-195b1e873f36.ps1
2023/04/11 19:48:12 packer-provisioner-powershell plugin: [INFO] 118 bytes written for 'uploadData'
2023/04/11 19:48:12 [INFO] 118 bytes written for 'uploadData'
2023/04/11 19:48:12 packer-plugin-proxmox_v1.1.2_x5.0_linux_amd64 plugin: 2023/04/11 19:48:12 Uploading file to 'c:/Windows/Temp/packer-ps-env-vars-64359d5c-af82-c4bb-31a9-195b1e873f36.ps1'
2023/04/11 19:48:22 packer-provisioner-powershell plugin: [INFO] 6062 bytes written for 'uploadData'
2023/04/11 19:48:22 [INFO] 6062 bytes written for 'uploadData'
2023/04/11 19:48:22 packer-plugin-proxmox_v1.1.2_x5.0_linux_amd64 plugin: 2023/04/11 19:48:22 Uploading file to 'c:/Windows/Temp/script-64359d5c-f051-c72a-b84f-495c81f719c3.ps1'
2023/04/11 19:48:57 packer-plugin-proxmox_v1.1.2_x5.0_linux_amd64 plugin: 2023/04/11 19:48:57 [INFO] starting remote command: pwsh -executionpolicy bypass -command "& { if (Test-Path variable:global:ProgressPreference){set-variable -name variable:global:ProgressPreference -value 'SilentlyContinue'};. c:/Windows/Temp/packer-ps-env-vars-64359d5c-af82-c4bb-31a9-195b1e873f36.ps1; &'c:/Windows/Temp/script-64359d5c-f051-c72a-b84f-495c81f719c3.ps1'; exit $LastExitCode }"
2023/04/11 19:48:58 packer-plugin-proxmox_v1.1.2_x5.0_linux_amd64 plugin: 2023/04/11 19:48:58 [INFO] command 'pwsh -executionpolicy bypass -command "& { if (Test-Path variable:global:ProgressPreference){set-variable -name variable:global:ProgressPreference -value 'SilentlyContinue'};. c:/Windows/Temp/packer-ps-env-vars-64359d5c-af82-c4bb-31a9-195b1e873f36.ps1; &'c:/Windows/Temp/script-64359d5c-f051-c72a-b84f-495c81f719c3.ps1'; exit $LastExitCode }"' exited with code: 0
2023/04/11 19:48:58 packer-plugin-proxmox_v1.1.2_x5.0_linux_amd64 plugin: 2023/04/11 19:48:58 [INFO] RPC endpoint: Communicator ended with: 0
2023/04/11 19:48:58 [INFO] 0 bytes written for 'stdout'
2023/04/11 19:48:58 [INFO] 303 bytes written for 'stderr'
2023/04/11 19:48:58 [INFO] RPC client: Communicator ended with: 0
2023/04/11 19:48:58 [INFO] RPC endpoint: Communicator ended with: 0
2023/04/11 19:48:58 packer-provisioner-powershell plugin: [INFO] 0 bytes written for 'stdout'
2023/04/11 19:48:58 packer-provisioner-powershell plugin: [INFO] 303 bytes written for 'stderr'
2023/04/11 19:48:58 packer-provisioner-powershell plugin: [INFO] RPC client: Communicator ended with: 0
==> proxmox-iso.windows-10-21h2-amd64: .: The term 'c:/Windows/Temp/packer-ps-env-vars-64359d5c-af82-c4bb-31a9-195b1e873f36.ps1' is not recognized as a name of a cmdlet, function, script file, or executable program.
2023/04/11 19:48:58 packer-provisioner-powershell plugin: c:/Windows/Temp/script-64359d5c-f051-c72a-b84f-495c81f719c3.ps1 returned with exit code 0
==> proxmox-iso.windows-10-21h2-amd64: Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2023/04/11 19:48:58 packer-provisioner-powershell plugin: [INFO] 511 bytes written for 'uploadData'
2023/04/11 19:48:58 [INFO] 511 bytes written for 'uploadData'
2023/04/11 19:48:58 packer-plugin-proxmox_v1.1.2_x5.0_linux_amd64 plugin: 2023/04/11 19:48:58 Uploading file to 'c:/Windows/Temp/packer-cleanup-64359d5c-9dcd-971a-6265-5b6602982e70.ps1'
2023/04/11 19:49:04 packer-plugin-proxmox_v1.1.2_x5.0_linux_amd64 plugin: 2023/04/11 19:49:04 [INFO] starting remote command: pwsh -executionpolicy bypass -command "& { if (Test-Path variable:global:ProgressPreference){set-variable -name variable:global:ProgressPreference -value 'SilentlyContinue'};. c:/Windows/Temp/packer-ps-env-vars-64359d5c-af82-c4bb-31a9-195b1e873f36.ps1; &'c:/Windows/Temp/packer-cleanup-64359d5c-9dcd-971a-6265-5b6602982e70.ps1'; exit $LastExitCode }"
2023/04/11 19:49:05 packer-plugin-proxmox_v1.1.2_x5.0_linux_amd64 plugin: 2023/04/11 19:49:05 [INFO] command 'pwsh -executionpolicy bypass -command "& { if (Test-Path variable:global:ProgressPreference){set-variable -name variable:global:ProgressPreference -value 'SilentlyContinue'};. c:/Windows/Temp/packer-ps-env-vars-64359d5c-af82-c4bb-31a9-195b1e873f36.ps1; &'c:/Windows/Temp/packer-cleanup-64359d5c-9dcd-971a-6265-5b6602982e70.ps1'; exit $LastExitCode }"' exited with code: 0
2023/04/11 19:49:05 packer-plugin-proxmox_v1.1.2_x5.0_linux_amd64 plugin: 2023/04/11 19:49:05 [INFO] RPC endpoint: Communicator ended with: 0
2023/04/11 19:49:05 [INFO] 0 bytes written for 'stdout'
2023/04/11 19:49:05 [INFO] 303 bytes written for 'stderr'
2023/04/11 19:49:05 [INFO] RPC client: Communicator ended with: 0
2023/04/11 19:49:05 [INFO] RPC endpoint: Communicator ended with: 0
2023/04/11 19:49:05 packer-provisioner-powershell plugin: [INFO] 0 bytes written for 'stdout'
2023/04/11 19:49:05 packer-provisioner-powershell plugin: [INFO] 303 bytes written for 'stderr'
2023/04/11 19:49:05 packer-provisioner-powershell plugin: [INFO] RPC client: Communicator ended with: 0
==> proxmox-iso.windows-10-21h2-amd64: .: The term 'c:/Windows/Temp/packer-ps-env-vars-64359d5c-af82-c4bb-31a9-195b1e873f36.ps1' is not recognized as a name of a cmdlet, function, script file, or executable program.
2023/04/11 19:49:05 [INFO] (telemetry) ending powershell
==> proxmox-iso.windows-10-21h2-amd64: Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
==> proxmox-iso.windows-10-21h2-amd64: Stopping VM

After switching on the debug flags, it shows the script silently exiting after
    proxmox-iso.windows-10-21h2-amd64: DEBUG:   70+  >>>> $windowsOpenSshCapabilities = Get-WindowsCapability -Online -Name 'OpenSSH.*' | Where-Object {$_.State -ne 'NotPresent'}
    proxmox-iso.windows-10-21h2-amd64:
2023/04/12 00:13:00 packer-plugin-proxmox_v1.1.2_x5.0_linux_amd64 plugin: 2023/04/12 00:13:00 [INFO] command 'pwsh -executionpolicy bypass -command "& { if (Test-Path variable:global:ProgressPreference){set-variable -name variable:global:ProgressPreference -value 'SilentlyContinue'};Set-PsDebug -Trace 1;. c:/Windows/Temp/packer-ps-env-vars-6435db5a-c007-eecc-99ad-e36c813e4adf.ps1; &'c:/Windows/Temp/script-6435db5a-586f-9950-b5e0-c9f1c873fcf8.ps1'; exit $LastExitCode }"' exited with code: 0
2023/04/12 00:13:00 packer-plugin-proxmox_v1.1.2_x5.0_linux_amd64 plugin: 2023/04/12 00:13:00 [INFO] RPC endpoint: Communicator ended with: 0
2023/04/12 00:13:00 [INFO] 4119 bytes written for 'stdout'
2023/04/12 00:13:00 [INFO] 0 bytes written for 'stderr'
2023/04/12 00:13:00 [INFO] RPC client: Communicator ended with: 0
2023/04/12 00:13:00 [INFO] RPC endpoint: Communicator ended with: 0
2023/04/12 00:13:00 packer-provisioner-powershell plugin: [INFO] 4119 bytes written for 'stdout'
2023/04/12 00:13:00 packer-provisioner-powershell plugin: [INFO] 0 bytes written for 'stderr'
2023/04/12 00:13:00 packer-provisioner-powershell plugin: [INFO] RPC client: Communicator ended with: 0
2023/04/12 00:13:00 packer-provisioner-powershell plugin: c:/Windows/Temp/script-6435db5a-586f-9950-b5e0-c9f1c873fcf8.ps1 returned with exit code 0
2023/04/12 00:13:00 [INFO] (telemetry) ending powershell
==> proxmox-iso.windows-10-21h2-amd64: Stopping VM

as said, manually, there are no hickups. I wonder which account actually runs the script, a) in the autoattend.xml b) as a packer provisioner step.

That's a strange error. It seems the provision-openssh.ps1 script is not even executed. When the script is executed, and there is an unknown error, it would print a stack trace and wait for 60m, which does not seem to be the case here.
I would try to execute a simple script, and go from there.

Hey Rui, all the other scripts are working, and, at least in the provisioner step, the script gets succesfully executed until the line mentioned above.

To confirm, if you are running that script from packer, which is using the ssh communicator, that might terminate the ssh session when it uninstalls the built in ssh server, which might explain why packer ends up failing. You should change the packer communicator to winrm.
If you are running that script from autounatted, I have no idea why that uninstall might be failing, maybe opening the vm console (which would have a desktop session open in the administrator account), and manually execute it there might give some clue.
The autounatend is running as the administrator user account. It runs in a auto logon desktop session which you can see if you connect to the launched packer vm.

Hey Rui, thanks for your answers!
Packer's communicator has always been set to WinRM so far. Packer builds run through, that script just outputs a premature Exit Code 0, so to speak and thus never exectues the steps after installing rsync.
In autounattend as well as a packer provisioning stop, when lines 70-74 are commented out, everything exexcutes successfully, but old OpenSSH remains installed (obviously).
When I set only the uninstall part as a packer provisioning step (after the majority of the script has run in autounattend) it shows the same faulty behaviour. Packer runs through successfully, but old OpenSSH remains installed with the script being shown as having successfully run.
Hope that was understandable.

There are extra limitations imposed on applications that execute from a remote session, so sometimes, one has to reshort to run the commands indirectly from a high privileged scheduled task (e.g. Run as system). So maybe that's why running from packer might be failing. But, I was expecting things to run without problems from autounatend because those command run locally as you would manually do, so that's quite puzzling to understand why it's failing.
Which windows 10 iso URL are you using? Maybe I can try to reproduce that problem here.

I have been using win10_21h2_EnglishInternational_x64.iso with Windows 10 Pro as Edition, as well as 17763.737.190906-2324.rs5_release_svc_refresh_SERVERESSENTIALS_OEM_x64FRE_en-us_1.iso for Windows 2019 Server Essentials. Both installed without OpenSSH.
My (working) workaround thus far is: running provision-pwsh, -openssh and -psremoting in SynchronousCommands in the specialize pass in my Autounattend and provision-winrm as well as provision-vmtools in the oobe pass. I came to try this as I read, that oobe will be run as the user, while specialize will be run as SYSTEM - apparently openssh need SYSTEM permissions, while vmtools (though I added qemu-ga to that script) and winrm need user permissions.

Thanks for the clarifications.
Maybe, now, when OpenSSH is installed as a windows feature it does something differently than what is available at https://github.com/PowerShell/Win32-OpenSSH/releases. I say "now", because at some point, I've tried to remove the OpenSSH windows feature (using what is in this repo) and it worked, so, it seems something changed in the mean time.
Unfortunately, I do not use or have access the Windows versions/flavors that you've mentioned. I can only use the ones that are in this repository.
Disclaimer: Be aware that this repository is intended to be used to create a vagrant box, that's why some things (like adding the public vagrant key and default vagrant user/password) are configured to work as vagrant normally expects them. YMMV when you take them out-of-context.

Its indeed strange, but I'm afraid I cannot reproduce it. I've just tried Win10 Evaluation 20H2 and it worked here. It uninstalled the OpenSSH Windows feature without any problem. I'm doing this in a Ubuntu 22.04 with the kvm/libvirt builder.


unfreeze blaze (use master instead of an old release branch)

motivation is to get https://github.com/http4s/blaze/pull/213
which makes blaze compile on JDK 9

https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-community-build/3290/ (404 til Jenkins queue clears)

https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-community-build/3301/  (404 for now)

http4s doesn't compile against blaze master, so I think it'll be easier to fork and cherry-pick the JDK 9 change onto the fork

74107db400fee05bd608aeb9fa71fd4e0c6818db


OCR opensource example

Coverage remained the same at 51.632% when pulling b2f8b6bef1885320ff7993aacc1118d6b1b246eb on zimiao/ocr into 0b9f0083bdfe0433581cbf6cf213d07d85616b74 on master.

Coverage remained the same at 51.632% when pulling b2f8b6bef1885320ff7993aacc1118d6b1b246eb on zimiao/ocr into 0b9f0083bdfe0433581cbf6cf213d07d85616b74 on master.


Elementary Arithmetic Operations-Update

Update Elementary Arithmetic Operations for qiskit 0.6

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Muneer seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Monitoring remote host..

Hello @stefanprodan ,
I would like to ask you if there is a way with this stack to monitor a remote host :? For example if I use this stack on one machine can I monitor an other one with different address :? If yes, is it possible to explain how :?

Manage to resolve it.

@kkalugerov : Could you please briefly explain how were you able to resolve this ? I am looking to do the same thing : Setup dockprom on one machine and monitor a remote Docker Host running all the containers/services.


improve optimize group commit select be  logic

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Added argument list for pyximport.

I added the API for pyximport.install(). And also some links.

Nice.


Convert checksec to unix format upon download

Signed-off-by: Elena Reshetova<EMAIL_ADDRESS>

test failure on wifi is unrelated, reports are correct, merging.


Git-Tfs verify fail System.InvalidOperationException: Sequence contains no elements

Hi
I get an exception when running TFS-GIT verify
Repo cloned from TFVC using Latest Git-Tfs
Comparing TFS changeset 1998 to git commit 495a8bb356f2f0ba23b020a46d0b9bae03904ab2
Looking for assembly StructureMap.resources, Version=<IP_ADDRESS>, Culture=en-US, PublicKeyToken=e60ad81abae3c223 ...
Trying to get HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\VisualStudio\14.0|InstallDir
Looking for assembly StructureMap.resources, Version=<IP_ADDRESS>, Culture=en-US, PublicKeyToken=e60ad81abae3c223 ...
Looking for assembly StructureMap.resources, Version=<IP_ADDRESS>, Culture=en, PublicKeyToken=e60ad81abae3c223 ...
Looking for assembly StructureMap.resources, Version=<IP_ADDRESS>, Culture=en, PublicKeyToken=e60ad81abae3c223 ...
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> StructureMap.StructureMapException: StructureMap Exception Code:  207
Internal exception while creating Instance '6b2a339c-158a-4dda-bd76-8d9706a7c2c8' of PluginType GitTfs.Core.TfsChangeset.  Check the inner exception for more details. ---> System.InvalidOperationException: Sequence contains no elements
   at System.Linq.Enumerable.Max(IEnumerable`1 source)
   at GitTfs.Core.TfsChangeset..ctor(ITfsHelper tfs, IChangeset changeset, AuthorsFile authors)
   at lambda_method(Closure , IArguments )
   at StructureMap.Construction.BuilderCompiler.FuncCompiler`1.<>c__DisplayClass2.<CreateBuilder>b__0(IArguments args)
   at StructureMap.Pipeline.ConstructorInstance.Build(Type pluginType, BuildSession session, IInstanceBuilder builder)
   --- End of inner exception stack trace ---
   at StructureMap.Pipeline.ConstructorInstance.Build(Type pluginType, BuildSession session, IInstanceBuilder builder)
   at StructureMap.Pipeline.Instance.createRawObject(Type pluginType, BuildSession session)
   at StructureMap.Pipeline.Instance.Build(Type pluginType, BuildSession session)
   at StructureMap.Pipeline.ObjectBuilder.Resolve(Type pluginType, Instance instance, BuildSession session)
   at StructureMap.BuildSession.CreateInstance(Type pluginType, Instance instance)
   at StructureMap.Container.GetInstance[PLUGINTYPE](ExplicitArguments args)
   at GitTfs.VsCommon.TfsHelperBase.BuildTfsChangeset(Changeset changeset, IGitTfsRemote remote)
   at GitTfs.Commands.TreeVerifier.Verify(TfsChangesetInfo changeset, Boolean ignorePathCaseMismatch)
   at GitTfs.Commands.Verify.RunFromCommitish(String commitish)
   at GitTfs.Commands.Verify.Run()
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at GitTfs.Util.GitTfsCommandRunner.Run(GitTfsCommand command, IList`1 args)
   at GitTfs.GitTfs.Main(GitTfsCommand command, IList`1 unparsedArgs)
   at GitTfs.GitTfs.Run(IList`1 args)
   at GitTfs.Program.Main(String[] args)
StructureMap Exception Code:  207
Internal exception while creating Instance '6b2a339c-158a-4dda-bd76-8d9706a7c2c8' of PluginType GitTfs.Core.TfsChangeset.  Check the inner exception for more details.
Sequence contains no elements

I use the follwing version
GitTfs-0.30.25-5d69e46c.pull_1315_merge
[linkto artifacts]https://ci.appveyor.com/project/pmiossec/git-tfs-v2qcm/build/artifacts

I might be wrong, but this line
Trying to get HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\VisualStudio\14.0|InstallDir
suggests to me that you are using TFS client libraries from Visual Studio 2015.
Can you check if the problem persists if you use the TFS client library from VS2017 setting the environment variable
GIT_TFS_CLIENT=2017 (or GIT_TFS_CLIENT=2013  for testing with Visual Studio 2013?

Where do i set the this parameter
GIT_TFS_CLIENT=2017

It is just an environment variable you need to set

The support of VS2017 has never been implemented (Microsoft changed a lot of things and no one took the time to do it --for few added value now that TFS libraries are no more dependent of the VisualStudio version but are provided through a nuget package--).
So setting explicitly the value will not change anything...

Ah, sorry, I got confused. I have VS 2017 support working  here in a private fork
(even with Checkin Policies, which took me a while), but I need to clean it  before I can
create a PR for it.
This is on my todo list. Hopefully, I have a little spare time over the Xmas holidays.

We are trying to clean up old/stale issues. As this issue hasn't seen any updates (or progress with pull requests) in quite a while, the issue will be closed. In case further information is provided, we can revisit that and reopen the issue again.

We are trying to clean up old/stale issues. As this issue hasn't seen any updates (or progress with pull requests) in quite a while, the issue will be closed. In case further information is provided, we can revisit that and reopen the issue again.


Enable camera (taking screenshots) by default

It might be less confusing if the camera takes screenshots by default.
Additionally, a (map) settings can be added to disable this default state if someone for some reason does not want the camera to be enabled by default (e.g. when changes to the camera/trackers are required before taking screenshots)

There are pros and cons in enabling it by default.
Pro: new users don't have to figure out that they have to enable it, so they will have the recording from the start.
Con: it will produce a considerable amount of image files maybe without the user noticing it. I have 7.4 GB for just one hour of playing in my current save. Flooding the drive like that should at least come with a warning.
My take: disable the camera by default, but add a kind of "greeting message" on a new game to remind users to enable cameras if they want to (or disable the mod if it's active by accident)

Taking screenshots takes space true, this should be clear when loading/installing the mod I guess?
But, starting to take screenshot immediately, does not make sense as the camera is not configured yet (resolution, frame rate, etc), so the screenshots are most likely worthless...
I'll add a warning message to hint (new) players to enable the camera.


feat: add vue support

Hi, thank you for your work on the project.
I just applied https://github.com/Acidic9/prettier-plugin-tailwind/issues/17#issuecomment-752883894 and it just works?
The order mismatch seems to be originated from tailwind-classes-sorter but it has acceptable results.
This commit will close #17

Thanks for this @laziu ! I am sorry I haven't been as active as I'd like on this project.
Really happy to see a PR come in, I'm just sorry it took me so long to get there.


Extending the document class for SQL (move columns out of metadata)?

Opening discussion here @MaximeThoonsen!

Hey @jacoblee93,
To finish this one, I see two decisions:

1 - what do we do with the Document class?

we extend the Document class (my recommendation but I agree we need to agree with the python implem)
we create a new EnrichedDocument class
other option?
I don't want to put everything into metadata for few reasons:

It's a easier for dev to understand columns rather than property inside a JSON object
it's easier to manipulate the data in columns than in a JSON
it will be easier for dev to enforce indexes on columns
SQL visualization tools work out of the box for columns but some of them won't work as fine for Json object

Could we use like a metadataMapping function or something similar to map SQL fields to metadata fields and back? The actual interface in LangChain doesn't actually need to match up with what's stored in SQL.
My worry with adding extra fields to the base class would be reimplementing it for all the providers we have.

Hey @jacoblee93,

Could we use like a metadataMapping function or something similar within the subclassed vector store to map SQL fields to metadata fields and back? The actual interface in LangChain presents a developer doesn't actually need to match up with what's stored in SQL.

I like this idea, it can work. My worry is that we would need to tranform it both ways it makes it a bit more complicated.

My worry with adding extra fields to the base class would be reimplementing it for all the providers we have, and not all of them would support it well.

If we add extra field and make them optionnal it shouldn't break anything right ?
Anyway if you prefer you suggestion (which makes sense 😂), I'll do a PR with this in mind


Request to move from ESLint + Prettier to BiomeJS for a unified formatting and linting approach

I know the project isn't a huge thing but that doesn't mean it can't stand to benefit from a few nice to haves.
Problem
Maintaining and dealing with multiple configurations for ESLint and Prettier tends to be tedious and time consuming despite the wide popularity of the 2 tools.
As complexity and the project size grows, there are well known reports that ESLInt and especially Prettier tend to slow down as more files need to be considered during the linting and formatting process. This is a well known issue and is a major reason why a lot of bigger applications tend to have the auto formatting turned off.
Additionally, having to install multiple packages to add on to ESLint's default configuration tends to be a pain to manage especially when rules need to be updated.
Solution
In my experience using Biome so far, it's streamlined a lot of this for me. 1 package for most things ESLint does and a formatter and linter in the same tool. Adding on to this the tool is light, fast and extremely easy to setup with an emphasis on a great developer experience when working with it.
An extension for biome exists on VSCode (as biomejs.biome) and is a great and light companion.
A full breakdown on the ESLint + Prettier comparison to Biome's configuration can be seen at
https://biomejs.dev/linter/rules/

I'm willing (and already have a branch created that will set this in place)


[EMM-1892] End user has registered his device in Android for work but is required to re-login every time

        After the end user registered himself in android for work in the android agent, the work profile is generated successfully. However, whenever he reopens the android agent app, he is required to re-login and this would sometimes cause re-registering of the same device.
Reference: https://wso2.org/jira/browse/EMM-1892

Fixed with https://github.com/wso2/cdmf-agent-android/pull/49


Event Request Codeunit 5812 Calculate Standard Cost - OnAfterSetProperties

In the SetProperties function, we need a Publisher to record the values that were previously set. It is necessary to do this in order to transfer them to other functions that are required in the other Publishers/Subscibers used. This is what the GlobalVarAccess property in the publishers was intended for, but it is not used anywhere.
SetProperties(NewCalculationDate : Date;NewCalcMultiLevel :....
.....
MaxLevel := 50;
MfgSetup.GET;
GLSetup.GET;
==> New
OnAfterSetProperties(NewCalculationDate : Date;NewCalcMultiLevel : Boolean;NewUseAssemblyList : Boolean;NewLogErrors : Boolean;NewStdCostWkshName : Text[50];NewShowDialog : Boolean)
==> New

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Add elements to drop

small fix when reconstructing cosmic data.

Hi @brownd1978,
You have proposed changes to files in these packages:

JobConfig

which require these tests: build.
@Mu2e/fnalbuild-users, @Mu2e/write have access to CI actions on main.
:hourglass: The following tests have been triggered for cd8bbc9026e44266a5d5998c4e7cdc5958bdbf0a: build  (Build queue is empty)
About FNALbuild. Code review on Mu2e/Offline.

:sunny: The build tests passed at cd8bbc9026e44266a5d5998c4e7cdc5958bdbf0a.

Test
Result
Details

test with
:white_check_mark:
Command did not list any other PRs to include

merge
:white_check_mark:
Merged cd8bbc9026e44266a5d5998c4e7cdc5958bdbf0a at 3e920a2414367b1e3723043bfa7114b471d03cdf

build (prof)
:white_check_mark:
Log file. Build time: 04 min 14 sec

ceSimReco
:white_check_mark:
Log file.

g4test_03MT
:white_check_mark:
Log file.

transportOnly
:white_check_mark:
Log file.

POT
:white_check_mark:
Log file.

g4study
:white_check_mark:
Log file.

cosmicSimReco
:white_check_mark:
Log file.

cosmicOffSpill
:white_check_mark:
Log file.

ceSteps
:white_check_mark:
Log file.

ceDigi
:white_check_mark:
Log file.

muDauSteps
:white_check_mark:
Log file.

ceMix
:white_check_mark:
Log file.

rootOverlaps
:white_check_mark:
Log file.

g4surfaceCheck
:white_check_mark:
Log file.

FIXME, TODO
:white_check_mark:
TODO (0) FIXME (0) in 0 files

clang-tidy
:white_check_mark:
0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at cd8bbc9026e44266a5d5998c4e7cdc5958bdbf0a after being merged into the base branch at 3e920a2414367b1e3723043bfa7114b471d03cdf.
For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.

@oksuzian a gentle reminder that this PR is on your list to review.

@FNALbuild run build test


Fix Mixer CRD store issue https://github.com/istio/istio/issues/14841

https://github.com/istio/istio/pull/12656 removed some code that was actually needed.

🤔 🐛 You appear to be fixing a bug in Go code, yet your PR doesn't include updates to any test files. Did you forget to add a test?
Courtesy of your friendly test nag.

🤔 🐛 You appear to be fixing a bug in Go code, yet your PR doesn't include updates to any test files. Did you forget to add a test?
Courtesy of your friendly test nag.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ozevren
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: geeknoid
If they are not already assigned, you can assign the PR to them by writing /assign @geeknoid in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

mixer/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: kyessenov, ozevren
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

mixer/OWNERS [kyessenov]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

And the original PR for removal did not go through review.
/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: douglas-reid, kyessenov, ozevren
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

mixer/OWNERS [douglas-reid,kyessenov]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


fix bug:when call triggerPullToRefresh, the state will always be SVPu…

…llToRefreshStateLoading

@JadianZheng What's this for?


The best repo ever

Amazing job Ruben here ❤ Keep it up

ahhahahahahahahahaha

behold! my work of the last four weeks


Update issue templates

@ananthanandanan @iammarco11
see if all the fields are necessary for us or not. Let me know if there is something which we should remove so as to get a simple template to get us rolling.


Support for TCP Fastopen

I came across this article, so I'm now curious about TCP Fastopen support when 'Simple Web Server' (SWS) is used on Linux:

Is TCP Fastopen currently supported by SWS?
Are code changes required in SWS to support TCP Fastopen or can it work 'straight out the box'?
Is the Boost library capable of using TCP Fastopen?

Without looking too closely on this, you can maybe use native_handle as shown here: https://stackoverflow.com/a/44308194. We could maybe add an option for this, but it would require a pull request for someone wanting to look into this:)


Add Cognitive Search (Skillset Operations) to the spec

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: jeji1101 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Automation for azure-sdk-for-node

Automation for azure-sdk-for-python

@jeji1101 Please make sure that other folks on your team who are familiar with the Skillset APIs review this.

Automation for azure-sdk-for-java


Fix yaml syntax and add comment to explain the cron syntax

Per the GitHub Actions docs, there is a dash missing in the syntax of the schedule. I also added a more generic execution time and a comment to explain its meaning.

Thanks! :)


Add ConnectionStringParser

Adds ConnectionStringParser, which parses both in-code and environment variable connection strings and combines them based on code > environment variable. Instrumentation key priority is .setup(CS) > .setup(ikey) > CS env var > ikey env var.
@Mikhail-msft
TODOS

[x] Add CS parsing in .setup(...)

Hey @markwolff,
It looks like you covered all the correct use cases in your tests. :)
I don't see many tests for invalid cases; Incorrect delimiters, duplicate keys, spaces in key.
You may want to consider adding some tests to verify that you can detect invalid connection strings without crashing and can provide meaningful error messages so customers can self diagnose.
Otherwise, this LGTM.

Hey @markwolff,
It looks like you covered all the correct use cases in your tests. :)
I don't see many tests for invalid cases; Incorrect delimiters, duplicate keys, spaces in key.
You may want to consider adding some tests to verify that you can detect invalid connection strings without crashing and can provide meaningful error messages so customers can self diagnose.
Otherwise, this LGTM.

Synced with Mothra offline. Will merge PR this in now and bring validation testing&logging to .NET parity in a separate PR.


What the following error code means

In Alamofire i were receiving -1001 if internet is off on device.
in SwiftHTTP I am getting -1004 if internet is off on device.
and getting -1001 if the service i am calling is down?
Please advice with the error codes and their meaning
Any document or blog post available please share.
Thanks

These error codes are from the underlining NSURLSession API that both Alamofire and SwiftHTTP use. -1001 and -1004 suggest you are having issues loading the URL/resource. See this SO post for ideas and the Apple Docs on what the errors mean below:
http://stackoverflow.com/questions/27159510/nsurlerrordomain-code-1001-error-when-a-http-post-request-is-sent
https://developer.apple.com/reference/cfnetwork/cfnetworkerrors
https://developer.apple.com/reference/foundation/1613022-foundation_constants/1508628-url_loading_system_error_codes


Have Swift collection types forward valueForKeyPath to the underlying Objective-C type

This allows key paths containing collection operators to be handled correctly, rather than throwing an unrecognized selector exception.
Fixes #3115.

:+1:

/cc @mrackwitz

:+1: Thanks for tackling that.


Update usage of github.com/dgrijalva/jwt-go

Looks like github.com/dgrijalva/jwt-go has moved to a new location - https://github.com/golang-jwt/jwt
Refer : https://github.com/dgrijalva/jwt-go/issues/462
Update to use the newer location.
CC: @element-of-surprise

Marking as bug as the dependency is archived. Can also investigate if there are other libraries which better fit the bill and which are better maintained.

We should move, but its not a rush.  The other is a clone because the maintainer just couldn't keep up.  But I think for the moment each are mirroring each other.
This brings up the something we should consider, which is having some type of cadence for looking at our dependencies and evaluating if there are any benefits for moving to a new version.  Often the upgrades have no value and its better to stay with what works.  But maybe something is twice as fast or security problems...
John Doak
Manager, Change Management SRE
@.***

From: henrikm @.>
Sent: Friday, July 9, 2021 4:25 PM
To: AzureAD/microsoft-authentication-library-for-go @.>
Cc: John Doak @.>; Mention @.>
Subject: Re: [AzureAD/microsoft-authentication-library-for-go] Update usage of github.com/dgrijalva/jwt-go (#244)
Marking as bug as the dependency is archived. Can also investigate if there are other libraries which better fit the bill and which are better maintained.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzureAD%2Fmicrosoft-authentication-library-for-go%2Fissues%2F244%23issuecomment-877506857&data=04|01|John.Doak%40microsoft.com|85448cba7e2e488d423908d94330cf02|72f988bf86f141af91ab2d7cd011db47|1|0|637614699181884090|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=%2FYEMYyZsbRW9c8XAorc3tzxYuNA%2FJafRfrU4h%2FYqC0M%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKCSL7GEFXERQMP7LN3H75DTW6ANXANCNFSM47VPHE5A&data=04|01|John.Doak%40microsoft.com|85448cba7e2e488d423908d94330cf02|72f988bf86f141af91ab2d7cd011db47|1|0|637614699181894087|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=gC5DSB9PqGXobIC4eKeyIc9njNtOby%2FdAcxiCV6hWGU%3D&reserved=0.


Define other usage monitoring solutions and fix for issue

Define more resource usage monitoring solutions

Also provides fix for #13746

/assign @bradtopol

@thecrudge thanks for your PR! Can you please take the fix for issue 13831 out of this PR, so that we can review content for one issue at a time? 13831 also needs additional triage, so if you could wait on a PR for it, that would also help. Thanks for understanding!
/hold

/hold cancel

/lgtm
/approve


changing public gene clinVar url to point to iobio backend

Keeping logic in place to detect if launched from mosaic for when we want to switch over to use Mosaic clinvar links.  Using iobio backend clinVar links in public gene for consistency, and tested stability.
("If geneinfo and genomebuild are still pointed at backend.iobio.io, it might be best to keep the ClinVar stuff pointed there for consistency. Eventually we should get everything pointed into the PE though I think" - Anders)

quarantest build successful. Demo link at
http://5d15fa58.quarantest.iobio.io


Set installed version in Pipfile when pipenv intall xxx

to resolve #2898
For example:
I ran pipenv install django a year ago, then django 1.19 installed, and django = "*" was added to Pipfile.
Now I run pipenv install in a new empty environment, I want to install django that the version of a year ago, but django 2.x is be installed.
I think pipenv should be similar with npm: when I run npm install xxx, then "xxx": "^1.2.3" will be added to dependencies of package.json
PS: I know the Pipefile.lock will lock the versions of every packages. But I still think that the way like npm is better.

sorry what is PEEP mean?

Sorry I missed your reply. You can read more about PEEP here: https://github.com/pypa/pipenv/blob/master/peeps/PEEP-000.md


Fixes top menu bar links

Refs #203
Refs Pelican-Elegant/documentation#29
Adds defaults when the *_URL references to direct templates are not defined.

I've tested locally and the top bar is working. I'd appreciate a second look to be sure.
This uses the {{ TAGS_URL or 'tags' }} convention, so that we don't need to define the direct template *_URL values. If we want to, we can, but by default the theme should now work.

but by default the theme should now work.

That's the plan.
Thanks a lot @AWegnerGitHub. With contributions from you and @iranzo, Elegant 2.0 is just around the corner.


Sphereflake

Any chance that someone would fix the Sphereflake demo  ? I tried to manually add the raytraced AABB and fix all errors. But still, even after successful compilation, the executable complains and I have truly no idea what's the problem. Or anyone already tried and could point me on the right direction ?
Having that demo running would be astonishing, especially from the claim from the blog of the 48 million spheres...

Thanks for asking. I'm hoping to get back to this code in November. Factor changed considerably, losing the ability for custom intersection shaders, then gaining it again. So, I'd like to use the new Falcor code and get this one going again.

Thanks for your quick reply, that would be fantastic, I am crossing my finger you will have time to look at it.

I had hopes of attacking this one come the new year, now that my Mineways PBR project is wrapping up, but duty calls - I'm getting pulled into a new project. Falcor does have a new version out, and I believe it now (or will) again support custom intersection shaders, such as for sphere intersection. Unfortunately I don't have the cycles to actually move sphereflake to the new Falcor.
But, the moral of this story is that the new Falcor is worth a look.


E0324 00:12:35.222997184       1 thread_pool.cc:253]                   Waiting for thread pool to idle before forking
E0324 00:12:38.223118937       1 thread_pool.cc:253]                   Waiting for thread pool to idle before forking
E0324 00:12:41.223247770       1 thread_pool.cc:253]                   Waiting for thread pool to idle before forking
E0324 00:12:44.223374500       1 thread_pool.cc:253]                   Waiting for thread pool to idle before forking
E0324 00:12:47.223496030       1 thread_pool.cc:253]                   Waiting for thread pool to idle before forking

@Alexander1000 Yes. Those versions are known to be affected. Can you please try the most recent nightly build or the 1.53 prerelease. I've not been able to reproduce at all with these.

@gnossen I'll let you know if anything goes wrong, but I updated the containers with the nightly version of grpc and none of the workers hung. 😄

Of the three issues I identified above (hang, assert, and segfault) - I may have found something that we can do on our side to make the assert and the segfault go away in our test suite. If I make sure that between each test case in the suite we are very careful to wait for any gRPC processes that the test has spun up to fully terminate (i.e. to call .wait() on the subprocess every time), then initial tests suggest that the assert/segfault no longer happen. (To be clear i think this is still a regression on the gRPC side since it wasn't happening before in older versions - but it's not clear how much a real user would hit it outside of stress test / CI).
Sadly that workaround does not seem to help with the hang, which still occurs regularly even if we are very careful to clean up all gRPC server subprocesses between tests.

@gnossen As below:

Using a Google Cloud project with pub/sub and Storage enabled, run gcloud auth
Clone the repository at https://github.com/googleapis/python-storage.git and use the main branch
Create and activate a virtualenv
Run pip install grpcio==1.52.0rc1 pytest pytest-rerunfailures google-cloud-iam "google-cloud-pubsub < 2.0.0" "google-cloud-kms < 2.0dev"
In the python-storage directory, run pip install -e .
In the python-storage directory, run pytest tests/system/test_notification.py tests/system/test_transfer_manager.py (notifications activates pub/sub which uses grpc; transfer_manager then tries to fork and hangs hard)

@andrewsg I pulled down your repro. I was able to reproduce at 1.52.0 (as expected), but 1.53.0 passed 10/10 times. This looks like it's been resolved.
I synced with @gibsondan offline. After our various fixes since 1.52.0, the rate of incidence of fork-related issues outlined has dropped low enough that we can go forward with the 1.53.0 release. It does sound like there are some issues that may arise under stress test-like scenarios, but this should not have a large impact on users.

Great to hear. Thanks for your diligence.
The message thread_pool.cc:253]                Waiting for thread pool to idle before forking for some reason only shows up when I am in pdb, and not when I have logging enabled conventionally, even when the root logger is set to DEBUG. Additionally, this message does not indicate it is related to GRPC in any way and the source code for thread_pool.cc does not seem to be public. If these issues are still cropping up stochastically under stress test conditions, I think it would help a lot if this message was somehow more visible and clearer on what package is responsible and what to do.

This message arises from the C extension that forms the core I/O library of gRPC. As a result, is logged directly to stderr, not through the Python logging system.

Additionally, this message does not indicate it is related to GRPC in any way

I agree that this could be improved. @drfloob and @veblush to comment on the possibility of somehow making gpr_log calls as clearly originating from the gRPC library. Perhaps we could have a global variable that enables all gpr_log invocations to add a prefix?

the source code for thread_pool.cc does not seem to be public

It is indeed public.

I think it would help a lot if this message was somehow more visible and clearer on what package is responsible and what to do.

Under normal circumstances, a user should not be seeing this message at all. My first priority is to make sure that this case never arises.

@gnossen thank you for looking into this. Unfortunately we are still seeing this issue with 1.53.0 Are there any temporary workarounds while this is solved?

Is this issue in anyway linked to #28557 ?
More context:
I am not directly consuming grpc, I am using google's python sdk for text to speech. I am not getting the warning of Waiting for thread pool but my service is hanging. Earlier I was getting this error but it went away when I updated the google cloud and google text to speech python packages. In one of the threads it was said that setting GRPC_POLL_STRATEGY=poll should fix the issue but that doesn't seem to be working.
Also, do we know in what scenarios this causes issues?

We merged a pull request (https://github.com/grpc/grpc/pull/32935) yesterday that should fix at least some of Python fork hanging issue. If you're still experiencing the issue, please try out the latest master branch and let us know if the hanging still exists.

@XuanWang-Amos I tried running our test suite on last night's nightly build after verifying that it included the fix, and sadly we are still seeing the hangs:
2023-04-26T16:39:13Z] PASSED
--
  | [2023-04-26T16:39:16Z] dagster_tests/cli_tests/workspace_tests/test_repository_load.py::test_valid_multi_location_from_module E0426 16:39:16.525341314     189 thread_pool.cc:230]                   Waiting for thread pool to idle before forking
  | [2023-04-26T16:39:19Z] E0426 16:39:19.525439192     189 thread_pool.cc:230]                   Waiting for thread pool to idle before forking
  | [2023-04-26T16:39:22Z] E0426 16:39:22.525537017     189 thread_pool.cc:230]                   Waiting for thread pool to idle before forking
  | [2023-04-26T16:39:25Z] E0426 16:39:25.525635038     189 thread_pool.cc:230]                   Waiting for thread pool to idle before forking
  | [2023-04-26T16:39:28Z] E0426 16:39:28.525733673     189 thread_pool.cc:230]                   Waiting for thread pool to idle before forking
  | [2023-04-26T16:39:31Z] E0426 16:39:31.525838659     189 thread_pool.cc:230]                   Waiting for thread pool to idle before forking
  | [2023-04-26T16:39:34Z] E0426 16:39:34.525946540     189 thread_pool.cc:230]                   Waiting for thread pool to idle before forking
  | [2023-04-26T16:39:37Z] E0426 16:39:37.526054102     189 thread_pool.cc:230]                   Waiting for thread pool to idle before forking
  | [2023-04-26T16:39:40Z] E0426 16:39:40.526160515     189 thread_pool.cc:230]                   Waiting for thread pool to idle before forking
  | [2023-04-26T16:39:43Z] E0426 16:39:43.526259653     189 thread_pool.cc:230]                   Waiting for thread pool to idle before forking
  | [2023-04-26T16:39:46Z] E0426 16:39:46.526364588     189 thread_pool.cc:230]                   Waiting for thread pool to idle before forking
  | [2023-04-26T16:39:49Z] E0426 16:39:49.526478176     189 thread_pool.cc:230]                   Waiting for thread pool to idle before forking
  | [2023-04-26T16:39:52Z] E0426 16:39:52.526574705     189 thread_pool.cc:230]                   Waiting for thread pool to idle before forking
  | [2023-04-26T16:39:55Z] E0426 16:39:55.526675098     189 thread_pool.cc:230]                   Waiting for thread pool to idle before forking
  | [2023-04-26T16:39:58Z] E0426 16:39:58.526772443     189 thread_pool.cc:230]                   Waiting for thread pool to idle before forking
  | [2023-04-26T16:40:01Z] E0426 16:40:01.526868224     189 thread_pool.cc:230]                   Waiting for thread pool to idle before forking

Although - some initial experiments suggest that enabling GRPC_ENABLE_FORK_SUPPORT does seem to make the hang happen much less frequently in our test suite (both before and after the most recent change)

Bumping for attention on this issue. https://github.com/ray-project/ray/issues/31729#issuecomment-1419663996 notes that setting grpcio==1.48.2 has circumvented the issue.

Experiencing this as well on MacOS 13.3.1 (a), Python 3.9.5, grpcio 1.55.0 when calling google.auth.transport.requests.Request() from google.auth except now it indicates line 230:
E0522 17:36:45.653282000<PHONE_NUMBER>78048 thread_pool.cc:230]           Waiting for thread pool to idle before forking

Can also confirm setting grpcio==1.48.2 and grpcio-status==1.48.2 resolves it for me as well.

Can also confirm setting grpcio==1.48.2 and grpcio-status==1.48.2 resolves it for me as well.

I am similarly experiencing this on Mac - but cannot get an earlier install to work, despite various attempts (update setuptools, update pip etc) I always end up with ERROR: Failed building wheel for grpcio ... any suggestion how I can get around this?

Can also confirm setting grpcio==1.48.2 and grpcio-status==1.48.2 resolves it for me as well.

I am similarly experiencing this on Mac - but cannot get an earlier install to work, despite various attempts (update setuptools, update pip etc) I always end up with ERROR: Failed building wheel for grpcio ... any suggestion how I can get around this?

What architecture are you on? If it's ARM, I think macOS ARM isn't supported yet.

Can also confirm setting grpcio==1.48.2 and grpcio-status==1.48.2 resolves it for me as well.

I am similarly experiencing this on Mac - but cannot get an earlier install to work, despite various attempts (update setuptools, update pip etc) I always end up with ERROR: Failed building wheel for grpcio ... any suggestion how I can get around this?

~What architecture are you on? If it's ARM, I think macOS ARM isn't supported yet.~
~Edit: Yup, no ARM wheels for macOS ☹ https://pypi.org/project/grpcio/#files, someone will need to provide guidance on building it for your arch.~
Yet another edit: I was wrong, https://stackoverflow.com/a/74424435/9852671 claims there's Apple Silicon support in newer versions. I didn't see the universal wheels. For older versions you'll want to take a look in https://github.com/pietrodn/grpcio-mac-arm-build @LukasWallrich.

Thanks! The repo by pietrordn starts only from versions past 1.50, so won't help here ... but you pushed me in the right direction. Conda has wheels for 1.48.1 (though not 1.48.2) and with those, the fork errors disappear.

Hello, this is the Google Cloud Storage Python client library team again. This issue has reappeared but is now affecting OS X only (I'm running on Intel, don't have Apple Silicon handy to test). Our grpc prerelease checker didn't catch this issue in advance because it runs on Linux; it is impacting released versions.
This happens with both grpc==1.55.0 and grpcio==1.55.0rc1. Repro steps are as per my previous comments, except with newer versions of grpc.
This is a pretty nasty issue; when the process hangs it hangs hard and doesn't respond to control-c, and must be killed from outside with kill -9. As previously discussed, the stderr output doesn't clearly indicate what package the issue is coming from, making it very hard for users to debug. Pytest captures and doesn't display the stderr at all by default (it would normally show it after the test fails, but because it hangs so hard, it never fails) -- this behavior can be disabled with a -s flag when running pytest.

Just jumping in to say that this issue is now causing some of our users to be unable to use our package since our pin is incompatible with a pin in newer versions of tensorflow.
Offer still stands to do another live debugging session with a debugger session that reproduces the hang if that would be at all helpful to get to the bottom of this (or to run any additional logging against our test suite that reproduces the problem).

@georgthegreat The spinlock issue that you're pointing out should only show up in debug builds, which none of our released artifacts should be. Are you sure you saw this in a release build and not a debug one?

I do! Here it is: https://github.com/tensorflow/tensorboard/blob/master/tensorboard/pip_package/requirements.txt#L20

@gnossen thanks for making this clear.
This indeed looks like our case: we build grpc from source and the problem appeared in debug build.
I assume that we might have fixed another deadlock. Could you, please, provide the issue corresponding to our case?

@shannah https://github.com/grpc/grpc/issues/31772

Looks like 1.56.0 may have fixed this? I was seeing this with 1.55.x, but it's no longer happening on 1.56.0. Python 3.9.16, grpcio==1.56.0 grpcio-status==1.44.0, Mac OS 13.4.1, Applie Silicon.

Seconding the above, the dagster repro of the hang seems to be gone in 1.56.0! Is that expected?

Seconding the above, the dagster repro of the hang seems to be gone in 1.56.0! Is that expected?

Seems to work on 1.56.0, thank you!

Versions grpcio==1.54.0, grpcio==1.56.0, grpcio==1.58.0 appeared to resolve the issue however the issue is back again in grpcio==1.59.0. I filed a new issue https://github.com/grpc/grpc/issues/34672 since this is a recent release


Conflict with Salesforce click-to-call

I have Flex integrated within SF and I can click on phone numbers to call from SF. That was working fine but as soon as I installed the dialpad, this function is overwriting the normal behaviour of outbound calls:
Actions.replaceAction("AcceptTask", (payload, original) => {
So when it runs original(payload); it displays the normal accept and cancel buttons on my task (outbound call) when this call is auto accepted by default. It also gets stuck and if I click any of these buttons nothing happens. I have to go to the console and manually remove it.

This is a known issue. Actions in Flex can only be replaced once. Both plugins are replacing the same action. The only solution would be to use the open-source Salesforce integration (https://github.com/lehel-twilio/plugin-sfdc). This way you have control over which plugin replaces the AcceptTask.

At the end what I did was replaced the function we have for click-to-call and use the one from dialpad instead.
It was a bit messy at beginning because that AccepTask is also replacing other channels we have but at least it's working now.
This is my action:
Actions.replaceAction("AcceptTask", (payload, original) => {
    return new Promise((resolve, reject) => {
      const reservation = payload.task.sourceObject;
      if (
        payload.task.taskChannelUniqueName === "voice" &&
        payload.task.attributes.direction === "outbound"
      ) {
        //Join existing conference as 3rd participant
        if (typeof reservation.task.attributes.conferenceSid !== "undefined") {
          reservation.call(
            reservation.task.attributes.from,
            `https://${runtimeDomain}/agent-join-conference?conferenceSid=${
              reservation.task.attributes.conferenceSid
            }`,
            {
              accept: true
            }
          );
        } else {
          // dialpad outbound
          reservation.call(
            reservation.task.attributes.from,
            `https://${runtimeDomain}/agent-outbound-join?taskSid=${
              payload.task.taskSid
            }`,
            {
              accept: true
              //record: "record-from-answer"
            }
          );
        }
      } else {
        original(payload);
      }
      resolve();
    });
  });


[PORT] doc cleanup

Port this change from botbuilder-dotnet/master branch:
https://github.com/microsoft/botbuilder-dotnet/pull/4162

Description

Removing stale docs. I believe these were part of a bad RI from 4.Future branch.

Not applicable to JS.


I want to search multiple files, can you help me？

I want to search multiple files, can you help me？

Use the UsbFile#listFiles() and then compare the name to what you are looking for, resp. dig deeper recursively if it is a directory.


Openweave Python packages should not depend on Python ABI version

We've noticed that Openweave Python packages on PyPI are only uploaded
for specific Python versions. This was a problem when we switched from
Python 3.7 to Python 3.8, and it was finally solved by uploading a new
Python package to PyPI. But now we've switched to Python 3.9 and the
problem surfaced again... so it's high time for a better solution.
Since Openweave Python package includes, and wraps around, a binary
shared object, it is not a "pure" package.  However, in that case,
Python's "wheel" packer assumes the package uses Python ABI (e.g. it
builds a Python module as a shared object), and tags it with the version
of ABI and the interpreter. Openweave does not use Python ABI, so this
is an unnecessary constraint. This PR removes it.

@googlebot I fixed it.

@googlebot I fixed it.

3rd attempt to get the spuriously failing test to pass.

4th attempt to get happy/tests/standalone/tunnel/test_weave_tunnel_02.py to pass.


Update capdctl subcommands help

Signed-off-by: Ashish Amarnath<EMAIL_ADDRESS>
What this PR does / why we need it:
Keep help messages in sync
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #49
Special notes for your reviewer:
Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
Release note:

NONE

/lgtm
/approve


[Packaged App] Response "Preview" tab cuts long responses

When Response body is long enough, "Preview" tab won't let you scroll till the end of it. Not even when "Toggle size" is enabled!

(There's a lot more text than that on the response, that is nowhere near the last line of it).
(MacOS 10.8)

I still have this issue, except my preview tab is only about 150px tall on OSX Mavericks - it's incredibly frustrating.

@jlem This was fixed a long time ago. Can you link to an HTML page that is causing the issue? Also, which version are you on?


retry failed brp upload (ipfs + proofing) when web3.storage is available again

@sudeepdino008 Fyi - both pipeline tests are failing
rudder        |   1) test returns the cid and hash of the processed block hash (Rudder.PipelineTest)
[3757](https://github.com/covalenthq/rudder/actions/runs/5686257290/job/15412731915?pr=147#step:7:3758)
rudder        |      test/pipeline_test.exs:4
rudder        |   2) test pipeline spawner starts pipeline processes (Rudder.PipelineTest)
[3775](https://github.com/covalenthq/rudder/actions/runs/5686257290/job/15412731915?pr=147#step:7:3776)
rudder        |      test/pipeline_test.exs:22
rudder        |
[3897](https://github.com/covalenthq/rudder/actions/runs/5686257290/job/15412731915?pr=147#step:7:3898)
rudder        | 35 tests, 2 failures
[3898](https://github.com/covalenthq/rudder/actions/runs/5686257290/job/15412731915?pr=147#step:7:3899)
rudder        |
[3899](https://github.com/covalenthq/rudder/actions/runs/5686257290/job/15412731915?pr=147#step:7:3900)
rudder        | Randomized with seed 634818

@sudeepdino008 Fyi - both pipeline tests are failing
rudder        |   1) test returns the cid and hash of the processed block hash (Rudder.PipelineTest)
[3757](https://github.com/covalenthq/rudder/actions/runs/5686257290/job/15412731915?pr=147#step:7:3758)
rudder        |      test/pipeline_test.exs:4
rudder        |   2) test pipeline spawner starts pipeline processes (Rudder.PipelineTest)
[3775](https://github.com/covalenthq/rudder/actions/runs/5686257290/job/15412731915?pr=147#step:7:3776)
rudder        |      test/pipeline_test.exs:22
rudder        |
[3897](https://github.com/covalenthq/rudder/actions/runs/5686257290/job/15412731915?pr=147#step:7:3898)
rudder        | 35 tests, 2 failures
[3898](https://github.com/covalenthq/rudder/actions/runs/5686257290/job/15412731915?pr=147#step:7:3899)
rudder        |
[3899](https://github.com/covalenthq/rudder/actions/runs/5686257290/job/15412731915?pr=147#step:7:3900)
rudder        | Randomized with seed 634818

works now. I also made change to fail if rudder tests executed inside docker fails.

LGTM tested, added a change to improve metrics logging


Amend the Folding Function and Optimize Redeemer Coercion

Include the accumulator in the folding function for counting the input UTxOs
Refine the folding function to expect PSmartHandleDatum instead of PAddress
Switch to punsafeCoerce from pconvert for redeemers as recommended by @colll78

Let's leave pconvert and use ptryFrom for all datums.

Apart from the owner address, the custom validation function now expects an arbitrary PData which allows it to have a more constrained logic on the produced output at the swap address.
As this arbitrary data is essentially an extension to the redeemer, its coercion can be done unsafely


[OTHER] Does this site actually need a nav component?

What would you like to share?
Since there is currently only one page and the nav component links back to itself, this could be confusing for screen reader users.
I suggest we remove the nav component and the Hubber icon can just be a part of the header and not be a link unless it is intended to add more pages.
Additional information
No response

hey I can resolve this issue?

Do you think something like this will work?

I like the idea 👍

I like the idea 👍

Great, I'll get to work then

Hey @Cahllagerfeld now that I am finished with this issue, can I work on #82 ?


Browse, LEDstate, ButtonLockstate

Browse: corrected a bug and added other categories FV: ...
Get/Set LEDstate, Buttonlockstate: removed parameter as provided automatcally
GetVolume, Loudness: removed "Master" as values are provided

Hope, this pull request works for your.

included in https://github.com/svrooij/sonos-api-docs/pull/24

It seems like I missed something, because these changes are not in the documentation


request: please share uvk5digmanager protocol & wsjtx patchset

i love to use all of your modifications includes cw feature, hf mod. and I also ready to make a  c-board & digital features.
but digmanger & modified wsjtx is only released windows version.
can you share the protocol & patch file before final version release to support the linux version?
(and also it would lead to update ft8cn for android devices)

Excellent
I will wsjtx full source and digimanager protocol upload this weekend
Thansks for your interest
Ian kd8cec
2024년 5월 17일 (금) 오후 12:01, Sunguk Lee @.***>님이 작성:

i love to use all of your modifications includes cw feature, hf mod. and I
also ready to make a c-board & digital features.
but digmanger & modified wsjtx is only released windows version.
can you share the protocol & patch file before final version release to
support the linux version?
(and also it would lead to update ft8cn for android devices)
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/63, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPFPKHRZGYQFOF5IY63ZCVXJ7AVCNFSM6AAAAABH3KNPZGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMYDCNZRG4ZTCMY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

thank you a lot!
DS1UFX

Since the development of WSJT-X for UV-K5 has been completed, the entire
source has been compressed and released.
I modified the introduction to the CEC0.3Q version on www.hamskey.com and
added a link.
We will update the communication protocol (frequency conversion, FT8 data
transmission) with UV-K5 as soon as it is organized.
Thank you for your interest.
On Mon, May 20, 2024 at 9:34 PM hspil @.***> wrote:

I don't mean to harass you, but I'm also interested in the same
information and I'm not seeing it posted anywhere yet.
Thanks for all your work on innovating firmware for this platform
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/63#issuecomment-2120372277, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPDMHC56UBTTCHUCLWDZDHUURAVCNFSM6AAAAABH3KNPZGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQGM3TEMRXG4
.
You are receiving this because you commented.Message ID:
@.***>


check maven version before build

Describe your changes

Fixes Issue

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.

@melloware Would you like a video meet? where you told me how to get started with quinoa, a basic react project setup using quinoa. we can do this today or on weekend if you agree then.
Thanks :)

I already have a full React example here including Rest services, Postgres DB, React Query , Quinoa etc.
You need JDK17 and Docker running but you can just run mvn quarkus:dev and see it in action.
https://github.com/melloware/quarkus-monorepo

let me know if you have any issues but as long as you have Docker running and JDK17 the whole thing should just work and show you and end to end example!

no go to localhost:8080


[5.2] fix validateAfter()

$value is an instance of Carbon\Carbon so checking is_string() will always return false, breaking any 'after:some_date' validation.

Why do you think the value is an instance of Carbon\Carbon?

This doesn't work?

@themsaid @GrahamCampbell
here is a simple example you can try to verify this is broken. After can either be a date string of model field.
'required|date|after:start_date'
(where start_date is a model field)
From the Laravel Docs:
Instead of passing a date string to be evaluated by strtotime, you may specify another field to compare against the date


docs(getting-started): add a getting started guide to react-is doc

This PR is mainly done for providing the getting started. Along the way I had change / tweak a few things (that's why there are other files modified). Amongst the different other changes:

The sidebar contains the title of the page
The sidebar is smarter and adapts on the content of the navgroup or the document (if either of them contains only one element, this level is discarded)
The sidebar is a tad wider

While the content of the getting started is mostly done, I need you:

can you review the content itself, make sure I talked every important and I didn't go into too much details for others?
there is no live examples yet. The getting started of the helper have its samples on codepen, but I'm not sure we want to go this. What do you suggest?

there is no live examples yet. The getting started of the helper have its samples on codepen, but I'm not sure we want to go this. What do you suggest?

As for the live examples, we need to have them also for the widget examples.
One possible solution is to use https://github.com/react-toolbox/react-toolbox/blob/dea14144b8969eca748d4899fb05bc8c52734a31/docs/app/components/preview/index.js (babel-standalone).
Basically we would need to create a small Preview component that would take the code sample (that can be obtained via .innerText on a <code> block in DOM) then transform that with babel-standalone, injecting the right context (basically every InstantSearch export).
What do you think?

I've did the tutorial. I find it easy to follow except that the connector part may come too soon, but this will change.
Results with the e-commerce data :)

Regarding the live example, it would have been nice to use those we are going to add in storybook.
We can do that by publishing the storybook and then have en embed iframe using the direct link to a story ?

We can do that by publishing the storybook and then have en embed iframe using the direct link to a story ?

Yep if it works well then why not and is invisible for the user that we are tricking him a bit ;)
But you will first have to be able to create a working /react/storybook to do so.

That would be very cool. And it seems less complex than using the stuff from react-toolbox.


Docs(web): Introduce General Changes into the Migration Guide #DS-1489

Description

Additional context

Issue reference

coverage: 78.782%. remained the same
when pulling 7fd47806a73ad153e0cc47c033105955bd869308 on docs/web-migration-general-changes
into 852b0e666e5248322e6fcd9bbc84759e24d38aca on integration/BC-v3-design-tokens.

coverage: 78.782%. remained the same
when pulling 7fd47806a73ad153e0cc47c033105955bd869308 on docs/web-migration-general-changes
into 852b0e666e5248322e6fcd9bbc84759e24d38aca on integration/BC-v3-design-tokens.


Added support for force_mode, freedrive and tool contact

This commit includes following changes:

New control mode for freedrive
New control mode for when the tool is in contact
Commands for stopping and starting tool contact
Commands for stopping and starting force mode
Added force_mode_damping and force_mode_gain_scaling to the constructor
Force mode gain scaling is only available for e-series and therefore it is removed from the control script, when the robot is not e-series
Tool contact example
Test for script command interface
Updated test for reverse interface

This PR will require some changes to the ROS and ROS2 drivers, in order for them to use the added commands.

This commit includes following changes:

New control mode for freedrive
New control mode for when the tool is in contact
Commands for stopping and starting tool contact
Commands for stopping and starting force mode
Added force_mode_damping and force_mode_gain_scaling to the constructor
Force mode gain scaling is only available for e-series and therefore it is removed from the control script, when the robot is not e-series
Tool contact example
Test for script command interface
Updated test for reverse interface

This PR will require some changes to the ROS and ROS2 drivers, in order for them to use the added commands.

Thank you very much for implementing this! I've been testing some features out and would like to get some clarification about freedrive mode. I tried to call ur_driver_->writeFreedriveControlMessage(urcl::control::FreedriveControlMessage::FREEDRIVE_START);, it succeeded but went back to servo thread right after. I tried to make a noop call but did not help.
So if we want to keep the robot in freedrive, do we need to actively maintain a thread that calls FREEDRIVE_START in the beginning and keeps calling FREEDRIVE_NOOP until we decide to terminate?


Download and Upload csv/yml files are inconsistent

In a lot of cases where there is both a download and upload option for some data (user table, submissions table, etc.) the format that is downloaded is inconsistent with the format that is required for the upload.
For example, sometimes the column orders are swapped or columns are missing entirely as is the case in the user table.
This makes it very difficult to download a csv, make a few changes minor changes and then upload the same file.

From email correspondence:

Under settings/marking scheme the upload yml gags if the description is
delimited by single quote characters.  However, if you download a description
created through the GUI it shows single quote characters.

This should be fixed now.


Newly created resource Page fails to load with "InvalidArgumentException View [{{ view }}] not found."

I've spoken briefly to ryangjchandler about this in the Discord channel.
It looks like when the resource scaffold gets built, that it's including an invalid definition of $view in the page template.
Steps to reproduce:

'artisan make:filament-resource '
Define a basic Form and Table schema in the main Resource php
Try to load the menu item from the Filament Dashboard
Error as per issue subject.

Workaround:
Either comment out the $view in the Pages/List.php file or (presumably) give it a valid custom view to use.

Fixed in v1.5.5.


Request has expired

The moment I run the transcription demo, I get the following error:
Request has expired
Please advise?

That problem still exists

This means you have a problem with your account or connection to AWS or potential an issue with audio encoding  Please confirm your connection, and then post enough information to debug the error, e.g. network traffic, browser console logs, erc

I don't know. A competitor has a better connection


Add License section and add badges to README.md

Really cool library!
I thought the readme could be better by adding a license section and some badges.
What do you think?

😍🙏


Babili not validating values properly

If something like this is put through Babili:
let pre = false;
let array = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10];
let randomNumber = Math.floor(Math.random() * 5);
for(let i = 0; i < array.length; i++)
  if(randomNumber === array[i]){
    pre = true;
    break;
  }
if(!pre)
  console.log("Hello");

Then it splits out:
"use strict";for(var array=[1,2,3,4,5,6,7,8,9,10],randomNumber=Math.floor(5*Math.random()),i=0;i<array.length;i++)if(randomNumber===array[i]){break}pre||console.log("Hello");

The above mentioned code will fail as the variable pre is not defined but is used in a "strict" environment. There are other ways to implement the above code like using a return instead of break. But this methods fails. Looks like a BUG

es2015 scoping issue.

Similar issues - https://github.com/babel/babili/labels/with es2015

Is there any workaround other than changing the code myself?

It should be possible to use babili as a separate pass and not use it alongside preset-es2015. This bug happens only when using babili and es2015 together. There are tools like babili-webpack-plugin if you're using webpack, gulp-babili if you're using gulp, rollup-plugin-babili if you're using rollup, and also you can build your own with other tools as well.

Ok thanks


Windows support

Is windows support planned?
I didn't manage to run the ./configure script of tensorflow. However, by moving the BUILD file to a new name, i could install sonnet by doing a simple
python setup.py install
I did not encounter bugs other than the complicated setup.

It;s not work at last. Although there is not bug while installing, it raised the Import Error while using the verify example.

Check that you did not try the example from the sonnet folder, it often doesn't work.

Not that. It just the example to use the resampler from sonnet.

Hey, after a bit of discussion, Windows support is not on the roadmap at the moment. Of course, PRs are always welcome :)
Just adding a note to this: @leconteur  your installation (without compilation) will not include the C++ bits of our library (currently that is the resampler).


Graceful shutdown of docker containers

Describe the bug
The DockerInteractive class starts a docker container for each instance that's created
Ideally we would stop and remove these containers in the __del__ function, which gets called when the instance is destroyed, or when the python process ends.
Unfortunately, the docker SDK makes a blocking call which isn't allowed during python's shutdown, so you end up with a stack trace.
Steps to Reproduce
To see the lack of cleanup:

PYTHONPATH=pwd python ./opendevin/main.py -d ./workspace -t "write a bash script that prints hello world"
wait for it to finish
docker ps should show sandbox-default

To see the graceless shutdown:

uncomment this line
Follow steps above
note the stack trace when the program finishes
docker ps still shows sandbox-default

Expected behavior
All sandbox containers are removed on shutdown
Actual behavior
Sandbox containers are left running
Additional context

Ideas for how to fix this:

Under normal circumstances (i.e. program finishes naturally, not ctrl+c or crash) we can definitely do the cleanup, e.g. by putting some cleanup logic in controller.py
Is there a way to force the docker SDK to run kill or remove?
Can we use subprocess to send a docker kill command without blocking exit?

Solved!


is creating new topics can increase the load on kafka servers ??

Topics are just metadata, so unless you start sending lots of data to them, causing disk and CPU IO, then no.


feat: split helpers into its own package

Description
To make the mutation and subscription helpers more usable they should be in their own package. I have taken them from the client and also removed some of the logic used by the helpers to helper functions within this package.
Checklist

[x] npm test passes
[x] npm run build works
[x] tests are included
[ ] documentation is changed or added

@StephenCoady I will play with that on master and make release


ComfyUI TIPO custom node fail to import

Here is what the log says at the start of ComfyUI :
Attempting to install LLaMA-CPP-Python
Looking in indexes: https://pypi.org/simple, https://jllllll.github.io/llama-cpp-python-cuBLAS-wheels/AVX2/cu122
Requirement already satisfied: llama-cpp-python in c:\python310\lib\site-packages (0.2.26+cu122)
Requirement already satisfied: typing-extensions>=4.5.0 in c:\python310\lib\site-packages (from llama-cpp-python) (4.9.0)
Requirement already satisfied: numpy>=1.20.0 in c:\python310\lib\site-packages (from llama-cpp-python) (1.23.5)
Requirement already satisfied: diskcache>=5.6.1 in c:\python310\lib\site-packages (from llama-cpp-python) (5.6.3)
WARNING: Error parsing dependencies of omegaconf: .* suffix can only be used with == or != operators
PyYAML (>=5.1.)
~~~~~~^
Requirement already satisfied: tipo-kgen>=0.1.2 in c:\python310\lib\site-packages (0.1.3)
Requirement already satisfied: transformers in c:\python310\lib\site-packages (from tipo-kgen>=0.1.2) (4.44.2)
Requirement already satisfied: huggingface-hub in c:\python310\lib\site-packages (from tipo-kgen>=0.1.2) (0.24.5)
Requirement already satisfied: torch in c:\python310\lib\site-packages (from tipo-kgen>=0.1.2) (2.2.0+cu118)
Requirement already satisfied: filelock in c:\python310\lib\site-packages (from huggingface-hub->tipo-kgen>=0.1.2) (3.13.1)
Requirement already satisfied: fsspec>=2023.5.0 in c:\python310\lib\site-packages (from huggingface-hub->tipo-kgen>=0.1.2) (2023.10.0)
Requirement already satisfied: packaging>=20.9 in c:\python310\lib\site-packages (from huggingface-hub->tipo-kgen>=0.1.2) (23.2)
Requirement already satisfied: pyyaml>=5.1 in c:\python310\lib\site-packages (from huggingface-hub->tipo-kgen>=0.1.2) (6.0.1)
Requirement already satisfied: requests in c:\python310\lib\site-packages (from huggingface-hub->tipo-kgen>=0.1.2) (2.31.0)
Requirement already satisfied: tqdm>=4.42.1 in c:\python310\lib\site-packages (from huggingface-hub->tipo-kgen>=0.1.2) (4.66.1)
Requirement already satisfied: typing-extensions>=<IP_ADDRESS> in c:\python310\lib\site-packages (from huggingface-hub->tipo-kgen>=0.1.2) (4.9.0)
Requirement already satisfied: sympy in c:\python310\lib\site-packages (from torch->tipo-kgen>=0.1.2) (1.12)
Requirement already satisfied: networkx in c:\python310\lib\site-packages (from torch->tipo-kgen>=0.1.2) (3.2.1)
Requirement already satisfied: jinja2 in c:\python310\lib\site-packages (from torch->tipo-kgen>=0.1.2) (3.1.2)
Requirement already satisfied: numpy>=1.17 in c:\python310\lib\site-packages (from transformers->tipo-kgen>=0.1.2) (1.23.5)
Requirement already satisfied: regex!=2019.12.17 in c:\python310\lib\site-packages (from transformers->tipo-kgen>=0.1.2) (2023.10.3)
Requirement already satisfied: safetensors>=0.4.1 in c:\python310\lib\site-packages (from transformers->tipo-kgen>=0.1.2) (0.4.5)
Requirement already satisfied: tokenizers<0.20,>=0.19 in c:\python310\lib\site-packages (from transformers->tipo-kgen>=0.1.2) (0.19.1)
Requirement already satisfied: colorama in c:\python310\lib\site-packages (from tqdm>=4.42.1->huggingface-hub->tipo-kgen>=0.1.2) (0.4.6)
Requirement already satisfied: MarkupSafe>=2.0 in c:\python310\lib\site-packages (from jinja2->torch->tipo-kgen>=0.1.2) (2.1.3)
Requirement already satisfied: charset-normalizer<4,>=2 in c:\python310\lib\site-packages (from requests->huggingface-hub->tipo-kgen>=0.1.2) (3.3.2)
Requirement already satisfied: idna<4,>=2.5 in c:\python310\lib\site-packages (from requests->huggingface-hub->tipo-kgen>=0.1.2) (3.6)
Requirement already satisfied: urllib3<3,>=1.21.1 in c:\python310\lib\site-packages (from requests->huggingface-hub->tipo-kgen>=0.1.2) (2.1.0)
Requirement already satisfied: certifi>=2017.4.17 in c:\python310\lib\site-packages (from requests->huggingface-hub->tipo-kgen>=0.1.2) (2023.11.17)
Requirement already satisfied: mpmath>=0.19 in c:\python310\lib\site-packages (from sympy->torch->tipo-kgen>=0.1.2) (1.3.0)
WARNING: Error parsing dependencies of omegaconf: . suffix can only be used with == or != operators
PyYAML (>=5.1.*)
~~~~~~^
Traceback (most recent call last):
File "B:\AI\img\ComfyUI_4\ComfyUI_windows_portable\ComfyUI\nodes.py", line 2001, in load_custom_node
module_spec.loader.exec_module(module)
File "", line 940, in exec_module
File "", line 241, in call_with_frames_removed
File "B:\AI\img\ComfyUI_4\ComfyUI_windows_portable\ComfyUI\custom_nodes\z-tipo-extension_init.py", line 1, in
from .nodes.tipo import NODE_CLASS_MAPPINGS, NODE_DISPLAY_NAME_MAPPINGS
File "B:\AI\img\ComfyUI_4\ComfyUI_windows_portable\ComfyUI\custom_nodes\z-tipo-extension\nodes\tipo.py", line 40, in
import kgen.models as models
ModuleNotFoundError: No module named 'kgen'
Cannot import B:\AI\img\ComfyUI_4\ComfyUI_windows_portable\ComfyUI\custom_nodes\z-tipo-extension module for custom nodes: No module named 'kgen'

install tipo-kgen library by yourself (use pip)
it looks like your environement have some issues in auto installing


@KafkaListener

@KafkaListener method Unable to receive message， i don't know why.

Closing as invalid - we can't help you without much more information.
Using the discussions tab to start a new discussion, or ask a question on Stack Overflow - you need to show code, configuration, logs etc, and explain exactly what you are seeing.


Soruce for the andorid app?

Hi there,
could you please share the source/reference for the andorid app?
Best

I thought it's required for doing this job. but sounds like it automatically detect. So I close this issue. Thanks


Incorrect revenue for some stocks

When I pull earnings for some stocks the revenue seems incorrect. The Net income is correct but cant figure out why the revenue is off
Example:
tickers = yf.Ticker('td.to')
tickers.earnings
Output:
\n  \n    \n      \n      Revenue\n      Earnings\n    \n    \n      Year\n      \n      \n    \n  \n  \n    \n      2017\n<PHONE_NUMBER>0\n<PHONE_NUMBER>0\n    \n    \n      2018\n<PHONE_NUMBER>0\n<PHONE_NUMBER>0\n    \n    \n      2019\n<PHONE_NUMBER>0\n<PHONE_NUMBER>0\n    \n    \n      2020\n<PHONE_NUMBER>0\n<PHONE_NUMBER>0\n    \n  \n
The revenue differs from whats listed in yahoo. the following stocks also have the same problem: bmo.to, ry.to, bns.to, cm.to. They are all Canadian banks. Not sure if the ending period is causing the problem.
Any insight is appreciated
Thanks.

Found this issue as well.

Found this issue as well.

I also found an issue that Capital Expenditures seem off for Canadian stocks in general.