vmware / .github Goto Github PK

Describe the bug

In file included from /tmp/modconfig-bkTSUb/vmmon-only/./include/cpu_types.h:29,
from /tmp/modconfig-bkTSUb/vmmon-only/./include/modulecall.h:33,
from /tmp/modconfig-bkTSUb/vmmon-only/common/moduleloop.c:33:
/tmp/modconfig-bkTSUb/vmmon-only/./include/vm_basic_defs.h:779: warning: "DO_ONCE" redefined
779 | #define DO_ONCE(code)
|
In file included from ./include/linux/prandom.h:12,
from ./include/linux/random.h:153,
from ./include/linux/nodemask.h:97,
from ./include/linux/sched.h:23,
from /tmp/modconfig-bkTSUb/vmmon-only/common/moduleloop.c:31:
./include/linux/once.h:46: note: this is the location of the previous definition
46 | #define DO_ONCE(func, ...)
|
In file included from /tmp/modconfig-bkTSUb/vmmon-only/./include/cpu_types.h:29,
from /tmp/modconfig-bkTSUb/vmmon-only/./include/modulecall.h:33,
from /tmp/modconfig-bkTSUb/vmmon-only/common/vmx86.h:33,
from /tmp/modconfig-bkTSUb/vmmon-only/common/vmx86.c:38:
/tmp/modconfig-bkTSUb/vmmon-only/./include/vm_basic_defs.h:779: warning: "DO_ONCE" redefined
779 | #define DO_ONCE(code)
|
In file included from ./include/linux/prandom.h:12,
from ./include/linux/random.h:153,
from ./include/linux/nodemask.h:97,
from ./include/linux/sched.h:23,
from /tmp/modconfig-bkTSUb/vmmon-only/common/vmx86.c:31:
./include/linux/once.h:46: note: this is the location of the previous definition
46 | #define DO_ONCE(func, ...)
|
In file included from /tmp/modconfig-bkTSUb/vmmon-only/./include/cpu_types.h:29,
from /tmp/modconfig-bkTSUb/vmmon-only/./include/modulecall.h:33,
from /tmp/modconfig-bkTSUb/vmmon-only/linux/hostif.c:58:
/tmp/modconfig-bkTSUb/vmmon-only/./include/vm_basic_defs.h:779: warning: "DO_ONCE" redefined
779 | #define DO_ONCE(code)
|

In file included from ./include/linux/prandom.h:12,
                 from ./include/linux/random.h:153,
                 from ./include/linux/nodemask.h:97,
                 from ./include/linux/sched.h:23,
                 from ./include/linux/binfmts.h:5,
                 from /tmp/modconfig-bkTSUb/vmmon-only/linux/hostif.c:31:
./include/linux/once.h:46: note: this is the location of the previous definition
   46 | #define DO_ONCE(func, ...)                                                   \
      | 
  CC [M]  /tmp/modconfig-bkTSUb/vmmon-only/bootstrap/monLoaderVmmon.o
  CC [M]  /tmp/modconfig-bkTSUb/vmmon-only/bootstrap/vmmblob.o
In file included from /tmp/modconfig-bkTSUb/vmmon-only/./include/cpu_types.h:29,
                 from /tmp/modconfig-bkTSUb/vmmon-only/./include/modulecall.h:33,
                 from /tmp/modconfig-bkTSUb/vmmon-only/./common/vmx86.h:33,
                 from /tmp/modconfig-bkTSUb/vmmon-only/linux/driver.h:32,
                 from /tmp/modconfig-bkTSUb/vmmon-only/linux/driver.c:47:
/tmp/modconfig-bkTSUb/vmmon-only/./include/vm_basic_defs.h:779: warning: "DO_ONCE" redefined
  779 | #define DO_ONCE(code)                                                   \
      | 
In file included from ./include/linux/prandom.h:12,
                 from ./include/linux/random.h:153,
                 from ./include/linux/nodemask.h:97,
                 from ./include/linux/list_lru.h:12,
                 from ./include/linux/fs.h:13,
                 from ./include/linux/highmem.h:5,
                 from /tmp/modconfig-bkTSUb/vmmon-only/linux/driver.c:25:
./include/linux/once.h:46: note: this is the location of the previous definition
   46 | #define DO_ONCE(func, ...)                                                   \
      | 
/tmp/modconfig-bkTSUb/vmmon-only/common/task.o: warning: objtool: .text: unexpected end of section

Reproduction steps

1. on debian compile the deb kernel packages nice make -jnproc bindeb-pkg
2. install the headers and libc debs first and then the image an image debug ones
3. reboot
4. vmware-modconfig --console --install-all
   ...

Expected behavior

the source compiles cleanly without warnings

Additional context

oot@ghost:~# uname -a                                
Linux ghost 6.2.0-rc2 #1 SMP PREEMPT_DYNAMIC Tue Jan  3 09:06:34 CET 2023 x86_64 GNU/Linux
root@ghost:~# gcc --version
gcc (Debian 12.2.0-13) 12.2.0
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

root@ghost:~# ld --version
GNU ld (GNU Binutils for Debian) 2.39.90.20230104
Copyright (C) 2022 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) a later version.
This program has absolutely no warranty.

root@ghost:~# cat /etc/debian_version 
bookworm/sid

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

Hi guys, I would like to create a powercli script to validate the guest VM directly from the vcenter by opening the remote console.

Describe the solution you'd like

Hi guys, I would like to create a powercli script to validate the guest VM directly from the vcenter by opening the remote console. I want to login the guest VM through invoking it , check the services and then log off. Can you guys help it

Describe alternatives you've considered

Powercli script (powershell scripting also preferred)

Additional context

No response

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

I got locked out of [email protected] and my alternative GitHub I also switched to iOS rather than android so it’s been a bit of a pain in the ass getting everything back together suggestions? For owner accounts?

Describe the solution you'd like

All of my things sent to my iphone synced for me. Owner administrative user account.

Describe alternatives you've considered

Started working with Apple and sued their asses for 52% ownership.

Additional context

My name is Nicholas Liennear Wardle and it’s a variation of owner account spread across McIntosh google Google Junior, Microsoft Apple IBM, American microchip corporation on semiconductor and NASA kind of important for me to get back in. Need some help. I’m a bit out of the loop these days as my dad and Stoker are with me any help?

GitHub now has a feature whereby default community files can be set for all repos under an org using the special .github repo.

Tasks:

• Create .github repos for all organizations that VMware manages
• CODE_OF_CONDUCT.md
• SECURITY.md
• CONTRIBUTING.md

Creating a default community health file

The test in the Code-of-conduct.md looks like it was copied twice.

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

The following description could be improved and also the link to FAQ is missing:

Before you start working with {{ project }}, please read and sign our Contributor License Agreement CLA. If you wish to contribute code and you have not signed our contributor license agreement (CLA), our bot will update the issue when you open a Pull Request. For any questions about the CLA process, please refer to our FAQ.

Describe the solution you'd like

Add link to https://cla.vmware.com/faq

Describe alternatives you've considered

No response

Additional context

No response

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

Github automatically applies issue templates from https://github.com/vmware/.github/ to all projects under the VMware org. This introduces a level or bureaucracy that is not suitable for all projects and that cannot be easily opted out of (to the best of my knowledge).

Describe the solution you'd like

Issue templates are useful in large projects with many external contributors in order to help streamline bug diagnostics and reduce the load on maintainers. However, such projects use highly customized templates designed to capture project-specific information. For a smaller project like ours, I prefer to make it as easy as possible for people to send their questions, requests, and bug reports by not imposing any structure. Speaking from personal experience, even a relatively simple form introduces an unnecessary barrier. And if the form has mandatory fields, I start to feel like it's the tax season :)

While github does allow us to override the set of templates per repo, I don't see a way to disable templates altogether once they are enabled for the org.

I would like to ask the maintainers of the vmware org to please reconsider the use of issue templates. Folks who want to use templates for their repos can add them with two clicks.

Describe alternatives you've considered

No response

Additional context

No response

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

Currently I don‘t see a way in the NSX API Client to keep the session alive after creating the client. My current workaround is to periodically lock the client via custom mutex in a struct, perform a call to GetDefaultHeaders and unlock the client.

Describe the solution you'd like

Automatic keep-alive of the session after initial setup of the NSX API client.

Describe alternatives you've considered

Do it myself as described above (error-prone, not user friendly IMHO).

Additional context

No response