App starts but RenderDoc fails to find PID and timeouts

Description
When I try to launch app with renderdoc, It launches app but timeouts (I think due to failed to find PID).
Steps to reproduce
1- Connect to replay context
2- RenderDoc app shows on Android device
3- Launching app from RenderDoc
4- App launches on Android device
5- RenderDoc waits until timeout and shows error "Error launching xx for capture RenderDoc injection failed: Timeout was reached waiting for app to start."
Environment

RenderDoc version: 1.29
Operating System: Windows 10
Graphics API: OpenGL ES 3.1
Android 12
Xiaomi POCO X3 Pro (I also enabled USB Debugging Security developer setting)

RenderDoc Log:
https://gist.github.com/tanisman/2735860872a373bd6bb19ca54fc9a908

Hi there
I think this is a problem with the Xiaomi Android 12 version. Android 12 should come with the standard "ps".
If possible it would be helpful to run the adb command manually from a terminal and see the output after launching your application manually outside of RenderDoc i.e.
See what version of ps is running
"C:\Program Files\RenderDoc\plugins\android\adb.exe" -s d348e5c5 shell ps --help
Then look at the running processes
"C:\Program Files\RenderDoc\plugins\android\adb.exe" -s d348e5c5 shell ps -A
"C:\Program Files\RenderDoc\plugins\android\adb.exe" -s d348e5c5 shell "ps -A | grep DefaultCompany"
Alternatively try to use RenderDoc with a different Android device.

I was able to debug the same application with the Xiaomi Redmi Note 9 Pro (Android 12)  on Windows 11 but I have no longer access to that setup.

Just to clarify, you're saying the same RenderDoc version and same application worked correctly on a different device? That reinforces the idea that the device itself that you're using now is indeed the problem. Do you have any different device to test with now?

well it previously worked on windows 11 and xiaomi redmi note 9 pro (android 12)
I switched back to windows 10 and I'm currently using xiaomi poco x3 pro (android 12) but RenderDoc is failing to find PID. I have attached the logs on first post:
RDOC 126956: [09:50:19]    win32_network.cpp( 347) - Warning - recv blocking failed: WSAECONNRESET: An existing connection was forcibly closed by the remote host. RDOC 126956: [09:50:19]    android_tools.cpp( 321) - Log     - COMMAND: C:\Program Files\RenderDoc/plugins/android/adb '-s d348e5c5 shell ps -A | grep com.DefaultCompany.TerrainShader'
when I manually run adb '-s d348e5c5 shell ps -A | grep com.DefaultCompany.TerrainShader' it works perfectly fine but RenderDoc timeouts.

Those are not error messages and there is no sign that there's any problem finding the app's PID. The logs are only intended for RenderDoc developers and not for general users to interpret.
Does this happen with any apk or only your one? Are you able to share your APK with me so that I can test it on a known working device, and can you try with these simple test APKs:
jake-kart-vk.apk
jake-runner-gles3.apk
You also didn't answer my question from above - are you able to try keeping everything exactly the same and testing with a different device to try to eliminate the device as the problem? Ideally one that is not from Xiaomi if you have a different device available, as those devices have caused problems in the past.

Closing this due to lack of activity from the reporter and no further information to investigate.
If you are the reporter and this bug is still a problem for you, or you are someone finding this issue and you believe this bug is still a problem and you have more information to share, please do not comment here and instead please open a new issue. You can reference this issue if you wish, but opening a new issue prevents confusion of accidentally linking two unrelated bugs and means that each issue can be handled in a clean process.


cgroup question regarding number of cpu's and hard/soft limit

I'm not sure this is the correct place for this but its a fairly simple question,
If i supply an app with 0.1 cpu and its the only container running on a mesos-slave does it get "hard" limited to 0.1 by default or is this a "soft" limit and it will burst to available cpu.
If its the later then if there are more containers running but not using cpu will it still burst and if every container is using cpu will it then grant shares based on the number of cpu's specified in the config?
Having trouble finding concrete documentation on this anywhere so some help would be appreciated :)

Hey Antony,
Marathon is only forwarding the information on limits for a process. cgroups isolation is implemented in the mesos slave.
AFAIK, there is no hard limit if there is plenty CPU available, meaning that your process can go crazy if there's nothing else going on. Please head for the mesos community to ask for implementation details about what exactly happens to processes with arbitrary cgroups limitations when a need for throttling arises. An educated guess would be that the configured CPU limit will be enforced, as this configuration is the basis for ressource scheduling.
Best regards
Matthias


Add support for Markdown extended

I have added support for markdown extended format.

Thanks! :ok_hand:


Wiki page edit restrictions

Add wiki coordinator role
Admin/coord can set page as editable by anyone or wiki coord only
Only wikiist or above can set this permission

Originally created by Tom Smyth at 2017-12-27 00:10, migrated from redmine-#7708

Description updated (diff)

By Tom Smyth at 2017-12-27 21:24

Status changed from New to Closed

By Tom Smyth at 2017-12-27 21:25


Add option to include additional files to bump

Description
I'd like to suggest a new option to include additional files to bump commit. This would be especially useful to include changelog or similar release-related files.
Currently, I use --allow-dirty. But that doesn't ensure the changelog is included to the git stage. This may cause the commit/tag to be created without necessary files.

I understand your request. Could you provide some thoughts on how you would like it to work (configurations/settings, failure handling, etc)?

It seems that could work, I have to try that sometime. Thanks for pointing it out.

OK, I tried hook like:
pre_commit_hooks = [
    "git add CHANGELOG.rst",
]

which works fine. The only problem is that I still have to use --allow-dirty to prevent bump-my-version from failing on changes in repository.

Then there must be other modified files. Add the hook 'git status' to see the state. Might need to run bump my version with -vvv

Nope. It's an inherent feature of the process.
The order of events is:

Change the CHANGELOG.rst
bump-my-version bump ...
check dirty files
run pre_commit_hooks - would add CHANGELOG.rst

It's the same with setup_hooks.
I think it's OK to have check of dirty files before anything else to prevent unwanted changes to the code. But an option to list files which may be dirty would help. Something like:
# These files are ignored in dirty check, event if --no-allow-dirty.
allow_dirty_files = ['CHANGELOG.rst', 'docs/changelog/*']

Thank you for the two PRs. I've given you write permission to the repository.
Do you think you could create a branch with the changes? It would help us both out.


[Pirk-66] - Fix Website To Indicate Pirk's Use of Java 8

This is a one-byte change. Heck, it's a one-bit change, from a certain pov.

+1 merging now


This lsfmq github includes object files.  They should be removed

I noted when browsing the various source, that we are including a compiled version of the message queue stuff in the source repos.  Before committing, you should have done a 'make clean'.  Can you please cleanup these source locations of the object code and binaries?

@PlatformLSF, I assigned you to this one.

The unexpected object and binary files have been cleaned.

Thanks!


Adding google auth in the backend

Can I work on this?

Hello, can I help ?

I want to work in this feature
But never implemented Google Auth before .
Can I give it a try?
On Mon, 27 Sep 2021, 03:32 Ayoub Boulahtar, @.***>
wrote:

Hello, can I help ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nehakalbande/Vision-Voice-Test/issues/2#issuecomment-927375150,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANJ6NSAO3XBMPXOCC7PBWALUD6GO7ANCNFSM5EXUNA3A
.

We can use Firebase Authentication to do so.

Yes @PriyanshX1902 firebase authentication can also help, if you can do let us know.

Hi @AyoubBoulahtar will you be able to do google auth ?

Sure, I can implement it. We can also use firebase realtime database to store a user's past results.

Correct! Ok then go ahead @PriyanshX1902 Will create a issue for it and do comment on that firebase issue.

After authentication, logout button should also appear in the navbar

@AyoubBoulahtar Please see other issues as well for backend part. Will be able to assign you then.

@PriyanshX1902 i'll be available for any help ..

@AyoubBoulahtar Sure, I'll ping you


Download database

Download database
Downloading of the soccer match statistics database for the purpose of uploading it to our future pipeline.

Pull request status - Accepted


[Ubuntu] Remove azcopy 7

Description
AzCopy 7 was released in 2018 and has never been updated since then. Version 10 is recommended to use since it is in active development and receives regular updates.
Related issue:
https://github.com/actions/virtual-environments/issues/2724
Check list

[x] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

Please remove changes related to azcopy7 in SoftwareReport.Tools.psm1 script.

Please remove changes related to azcopy7 in SoftwareReport.Tools.psm1 script.
@al-cheb Thanks for the point!


updated framer-studio (62)

Changes to a cask
Editing an existing cask

[x] Commit message includes cask’s name (and new version, if applicable).
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.

Great - just needs a squash, I can do that for you. (Next time, running brew update before cask-repair will  prevent this problem :)

Thank you for the contribution. It needed some fixes, so they were made in ef55f39b5bc0622e0e3a4a070443552f84294141. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.


Change MultiNodeEvaluator to object patching from proxy pattern

With Chainer #3952 current proxy implementation cannot handle
class attributes of Chainer's latest Evaluator.name, thus move
to just wrap the evaluate() method with multi-node support.
With this and #149 merged, ChainerMN will work with Chainer 4.0.
Note: consequence of this issue is, validation evaluator cannot have it's name validation and key validation/main/loss and validation/main/accuracy does not exist; which has two unexpected effects:

instead the evaluator overwrites main/loss and main/accuracy, printing no result in LogReport
due to the unexpected lack of validation/main/loss or accuracy user codes may fail (and following functionality such as saving actual models, might fail)

Although CircleCI is failing, but it is on test phase and not ready to use in reviewing and testing branches. This pull request is ready for review.

I agree this changes behaviour of create_multi_node_evaluator which is not suitable for its name and the new behaviour can even be considered not compatible. However, I still think patching the evaluator object is the best way to fix Chainer 4.0.0 compatibility issue and I propose following actions on this:

Add new patching function with new name like bless_evaluator_for_multi_node or sth like that.
For create_multi_node_evaluator, we have several possible options:

Option 1: We would say for 1.1 it does not work with Chainer 4.0.0b2 or later (works fine with b1), But mark the function as to-be-deprecated at 1.1, leaving the bug as it is. And deprecate it at 2.0.
Option 2: We add a kludgy patch to it as a quick fix but mark as to-be-deprecated at 1.1 and at 2.0.
Option 3: apply a kludgy patch that fix this issue and not add evaluator-patching new feature.

A kludgy patch I mentioned above would be something like this:
    class MultiNodeEvaluator(type(actual_evaluator)):
  ...
        def __setattr__(self, attr_name, value):
            if hasattr(self.actual_evaluator.__class__, attr_name):
                setattr(self.actual_evaluator.__class__, attr_name, value)
            else:
                setattr(self.actual_evaluator, attr_name, value)

After discussion with @iwiwi patching approach is fine, but just preserved the name actual_evaluator . Also, fixed types.MethodType but to use six. Will be included in 1.1 release with the new design.

Thanks, I will merge after Travis tests


Combine two Spring boms into one, spring-cloud-azure-dependencies.

In the next major version of Spring, we plan to combine the current two boms into one, the azure-spring-boot-bom and azure-spring-cloud-dependencies.

Closed in #24826.


Build error in 0.1.6

[11/25] Compiling C++ object src/libpercetto.so.p/percetto.cc.o
FAILED: src/libpercetto.so.p/percetto.cc.o
ccache c++ -Isrc/libpercetto.so.p -Isrc -I../src -Iperfetto-sdk -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -Wextra -Werror -std=c++2a -g -fPIC -fvisibility=hidden -fdata-sections -ffunction-sections -Os -MD -MQ src/libpercetto.so.p/percetto.cc.o -MF src/libpercetto.so.p/percetto.cc.o.d -o src/libpercetto.so.p/percetto.cc.o -c ../src/percetto.cc
../src/percetto.cc: In static member function ‘static bool {anonymous}::PercettoDataSource::Register(const percetto_category* const*, const percetto_category* const*, bool)’:
../src/percetto.cc:366:13: error: ‘UpdateDescriptor’ is not a member of ‘{anonymous}::PercettoDataSource::Base’ {aka ‘perfetto::DataSource<{anonymous}::PercettoDataSource, {anonymous}::PercettoDataSourceTraits>’}
  366 |       Base::UpdateDescriptor(dsd);
      |             ^~~~~~~~~~~~~~~~

Looks like new code in https://github.com/olvaffe/percetto/commit/8af1898a4823d911a1fce9bfe1c85a5dc26fa255 - was there a missing part of this change that didn't get committed? I'm testing with my adjacent perfetto directory checked out at releases/v23.x

Hmm. It seemed to work ok later when I used my CMake build. My guess is that the Meson build copied an old version of Perfetto and kept using it despite the updates. However, the CMake build in #26 uses the files from perfetto without copying them, so it should be resistant to this issue.

My guess is that the Meson build copied an old version of Perfetto and kept using it despite the updates.

Meson doesn't copy anything.
The build rules for this project seem to erroneously do so: https://github.com/olvaffe/percetto/blob/22f649055e15ff07cea4c73a8337c0ffdb06d566/perfetto-sdk/meson.build#L35-L47
However, those also depend on the original files from the directory get_option('perfetto-sdk') so updates to those files will result in the cp command specified by this project, being re-run.

Well, the issue happened not just to me but also to a coworker. No problem when using CMake though.


Consider removing entity constructor which accepts ID

Having the constructor just adds to the derived code. We can easily have protected final setter and check that the field is initialized only once.  And throw NullPointerException in getId() if the field is not initialized.

Entities now have two constructors: default and the one which accepts ID. The constructor with ID provides additional flexibility for initialization which needs to know an ID. This is especially useful for Process Managers.


Good idea or bad ?

Compile all the little know and possible more well known piracy sites and print them all in an easy list for  ANYONE to see ,mmmmm...........
Good idea or bad ?

No pirates, no piracy.  No new pirates, no pirates, no piracy.  No piracy, no piracy sites.


update 1.15.1

☆ Onnxruntime 1.15.1 Update ☆
Jira Ticket
Upstream
Dependencies
Changes

Updated version number and sha256
Updated pinnings on dependencies
A bit of reformatting of the meta.yaml
removed abs.yaml
Removed outdated patching, updated relevant ones
Updated bld.bat and bld.sh for successful builds on archectures
Onnxruntime is available for python versions 3.7 - 3.10 so a skip has been added for versions greater than 10. See here.

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_a3vcr_cr49/clone/recipe/meta.yaml:24: no_git_on_windows: git should not be used as a dependency on Windows.
ERROR: /tmp/abs_a3vcr_cr49/clone/recipe/meta.yaml:33: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a3vcr_cr49/clone/recipe/meta.yaml:34: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a3vcr_cr49/clone/recipe/meta.yaml:35: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a3vcr_cr49/clone/recipe/meta.yaml:37: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a3vcr_cr49/clone/recipe/meta.yaml:38: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_a3vcr_cr49/clone/recipe/meta.yaml:47: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:59: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_48jluuu_1j/clone/recipe/meta.yaml:24: no_git_on_windows: git should not be used as a dependency on Windows.
ERROR: /tmp/abs_48jluuu_1j/clone/recipe/meta.yaml:34: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_48jluuu_1j/clone/recipe/meta.yaml:35: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_48jluuu_1j/clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_48jluuu_1j/clone/recipe/meta.yaml:38: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_48jluuu_1j/clone/recipe/meta.yaml:39: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_48jluuu_1j/clone/recipe/meta.yaml:48: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:77: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_26a3jcc79e/clone/recipe/meta.yaml:25: no_git_on_windows: git should not be used as a dependency on Windows.
ERROR: /tmp/abs_26a3jcc79e/clone/recipe/meta.yaml:35: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_26a3jcc79e/clone/recipe/meta.yaml:36: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_26a3jcc79e/clone/recipe/meta.yaml:37: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_26a3jcc79e/clone/recipe/meta.yaml:39: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_26a3jcc79e/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_26a3jcc79e/clone/recipe/meta.yaml:49: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:65: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_9bpb03leln/clone/recipe/meta.yaml:31: no_git_on_windows: git should not be used as a dependency on Windows.
ERROR: /tmp/abs_9bpb03leln/clone/recipe/meta.yaml:36: patch_must_be_in_build: patch must be in build when source/patches is set.
ERROR: /tmp/abs_9bpb03leln/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9bpb03leln/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9bpb03leln/clone/recipe/meta.yaml:43: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9bpb03leln/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9bpb03leln/clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_9bpb03leln/clone/recipe/meta.yaml:55: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:65: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_638a2a9sv7/clone/recipe/meta.yaml:31: no_git_on_windows: git should not be used as a dependency on Windows.
ERROR: /tmp/abs_638a2a9sv7/clone/recipe/meta.yaml:35: patch_must_be_in_build: patch must be in build when source/patches is set.
ERROR: /tmp/abs_638a2a9sv7/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_638a2a9sv7/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_638a2a9sv7/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_638a2a9sv7/clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_638a2a9sv7/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_638a2a9sv7/clone/recipe/meta.yaml:54: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:53: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

@Arishamays1 I took a look at the logs and made some changes that will hopefully get the build working:

We can't build the package tests with our current setup. I faced this problem the last time too but unfortunately I couldn't find the time to locate and fix the problem. So the tests have been disabled and removed.
You need to call the build script with the allow_running_as_root option, as our CI workers do have root privileges. This is fine, and has no effect on the rest of the build process.
You need to remove libprotobuf from the build environment, as that (and other protobuf related dependencies) are vendored in at the moment.
I haven't looked at the patches yet, so I am not sure if you need those.

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_a62nwh2k8f/clone/recipe/meta.yaml:31: no_git_on_windows: git should not be used as a dependency on Windows.
ERROR: /tmp/abs_a62nwh2k8f/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a62nwh2k8f/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a62nwh2k8f/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a62nwh2k8f/clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a62nwh2k8f/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_a62nwh2k8f/clone/recipe/meta.yaml:54: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:53: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_dflfyz09el/clone/recipe/meta.yaml:31: no_git_on_windows: git should not be used as a dependency on Windows.
ERROR: /tmp/abs_dflfyz09el/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_dflfyz09el/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_dflfyz09el/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_dflfyz09el/clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_dflfyz09el/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_dflfyz09el/clone/recipe/meta.yaml:54: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:53: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_3975qbzphl/clone/recipe/meta.yaml:31: no_git_on_windows: git should not be used as a dependency on Windows.
ERROR: /tmp/abs_3975qbzphl/clone/recipe/meta.yaml:35: patch_must_be_in_build: patch must be in build when source/patches is set.
ERROR: /tmp/abs_3975qbzphl/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3975qbzphl/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3975qbzphl/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3975qbzphl/clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3975qbzphl/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_3975qbzphl/clone/recipe/meta.yaml:54: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:53: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_a8_okz6c6l/clone/recipe/meta.yaml:31: no_git_on_windows: git should not be used as a dependency on Windows.
ERROR: /tmp/abs_a8_okz6c6l/clone/recipe/meta.yaml:35: patch_must_be_in_build: patch must be in build when source/patches is set.
ERROR: /tmp/abs_a8_okz6c6l/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a8_okz6c6l/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a8_okz6c6l/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a8_okz6c6l/clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a8_okz6c6l/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_a8_okz6c6l/clone/recipe/meta.yaml:54: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:53: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Seems like ninja was misbehaving a bit on win-64, so I removed it; hopefully win-64 is able to build fully now (it did build correctly the last time, but the incorrect makefile behavior was causing setup.py to fail). Make sure to adjust the meta.yaml accordingly.

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_b3v48lc4kn/clone/recipe/meta.yaml:32: no_git_on_windows: git should not be used as a dependency on Windows.
ERROR: /tmp/abs_b3v48lc4kn/clone/recipe/meta.yaml:35: patch_must_be_in_build: patch must be in build when source/patches is set.
ERROR: /tmp/abs_b3v48lc4kn/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_b3v48lc4kn/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_b3v48lc4kn/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_b3v48lc4kn/clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_b3v48lc4kn/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_b3v48lc4kn/clone/recipe/meta.yaml:54: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:53: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_4co7mxpdoy/clone/recipe/meta.yaml:32: no_git_on_windows: git should not be used as a dependency on Windows.
ERROR: /tmp/abs_4co7mxpdoy/clone/recipe/meta.yaml:35: patch_must_be_in_build: patch must be in build when source/patches is set.
ERROR: /tmp/abs_4co7mxpdoy/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_4co7mxpdoy/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_4co7mxpdoy/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_4co7mxpdoy/clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_4co7mxpdoy/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_4co7mxpdoy/clone/recipe/meta.yaml:54: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:53: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_da7ddsohg2/clone/recipe/meta.yaml:32: no_git_on_windows: git should not be used as a dependency on Windows.
ERROR: /tmp/abs_da7ddsohg2/clone/recipe/meta.yaml:35: patch_must_be_in_build: patch must be in build when source/patches is set.
ERROR: /tmp/abs_da7ddsohg2/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_da7ddsohg2/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_da7ddsohg2/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_da7ddsohg2/clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_da7ddsohg2/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_da7ddsohg2/clone/recipe/meta.yaml:54: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:53: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_1294uxukty/clone/recipe/meta.yaml:32: no_git_on_windows: git should not be used as a dependency on Windows.
ERROR: /tmp/abs_1294uxukty/clone/recipe/meta.yaml:35: patch_must_be_in_build: patch must be in build when source/patches is set.
ERROR: /tmp/abs_1294uxukty/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1294uxukty/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1294uxukty/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1294uxukty/clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1294uxukty/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_1294uxukty/clone/recipe/meta.yaml:54: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:53: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_cb838tgdz1/clone/recipe/meta.yaml:32: no_git_on_windows: git should not be used as a dependency on Windows.
ERROR: /tmp/abs_cb838tgdz1/clone/recipe/meta.yaml:35: patch_must_be_in_build: patch must be in build when source/patches is set.
ERROR: /tmp/abs_cb838tgdz1/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_cb838tgdz1/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_cb838tgdz1/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_cb838tgdz1/clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_cb838tgdz1/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_cb838tgdz1/clone/recipe/meta.yaml:54: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:53: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
Traceback (most recent call last):
  File "/opt/conda/envs/linter/bin/conda-lint", line 11, in
    sys.exit(main())
             ^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/anaconda_linter/run.py", line 107, in main
    result = linter.lint(
             ^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/anaconda_linter/lint/__init__.py", line 620, in lint
    msgs = self.lint_file(
           ^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/anaconda_linter/lint/__init__.py", line 684, in lint_file
    recipe = _recipe.Recipe.from_file(
             ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/anaconda_linter/recipe.py", line 340, in from_file
    raise exc
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/anaconda_linter/recipe.py", line 331, in from_file
    recipe.load_from_string(text.read())
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/anaconda_linter/recipe.py", line 214, in load_from_string
    self.render()
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/anaconda_linter/recipe.py", line 421, in render
    self.meta = yaml.load(yaml_text)
                ^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/ruamel/yaml/main.py", line 434, in load
    return constructor.get_single_data()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/ruamel/yaml/constructor.py", line 119, in get_single_data
    node = self.composer.get_single_node()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/ruamel/yaml/composer.py", line 76, in get_single_node
    document = self.compose_document()
               ^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/ruamel/yaml/composer.py", line 99, in compose_document
    node = self.compose_node(None, None)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/ruamel/yaml/composer.py", line 143, in compose_node
    node = self.compose_mapping_node(anchor)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/ruamel/yaml/composer.py", line 223, in compose_mapping_node
    item_value = self.compose_node(node, item_key)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/ruamel/yaml/composer.py", line 143, in compose_node
    node = self.compose_mapping_node(anchor)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/ruamel/yaml/composer.py", line 223, in compose_mapping_node
    item_value = self.compose_node(node, item_key)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/ruamel/yaml/composer.py", line 141, in compose_node
    node = self.compose_sequence_node(anchor)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/ruamel/yaml/composer.py", line 185, in compose_sequence_node
    node.value.append(self.compose_node(node, index))
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/conda/envs/linter/lib/python3.11/site-packages/ruamel/yaml/composer.py", line 117, in compose_node
    raise ComposerError(
ruamel.yaml.composer.ComposerError: found undefined alias '*/api-ms-win-core-path-l1-1-0.dll'
  in "", line 26, column 7:
        - **/api-ms-win-core-path-l1-1-0.dll
          ^ (line: 26)
ERROR conda.cli.main_run:execute(47): conda run conda-lint /tmp/abs_f8f6273tqa/clone failed. (See above for error)

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_ebrus3f4_x/clone/recipe/meta.yaml:32: no_git_on_windows: git should not be used as a dependency on Windows.
ERROR: /tmp/abs_ebrus3f4_x/clone/recipe/meta.yaml:35: patch_must_be_in_build: patch must be in build when source/patches is set.
ERROR: /tmp/abs_ebrus3f4_x/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ebrus3f4_x/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ebrus3f4_x/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ebrus3f4_x/clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_ebrus3f4_x/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_ebrus3f4_x/clone/recipe/meta.yaml:54: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:53: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_a2e_e86owg/clone/recipe/meta.yaml:33: no_git_on_windows: git should not be used as a dependency on Windows.
ERROR: /tmp/abs_a2e_e86owg/clone/recipe/meta.yaml:36: patch_must_be_in_build: patch must be in build when source/patches is set.
ERROR: /tmp/abs_a2e_e86owg/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a2e_e86owg/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a2e_e86owg/clone/recipe/meta.yaml:43: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a2e_e86owg/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_a2e_e86owg/clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_a2e_e86owg/clone/recipe/meta.yaml:55: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:53: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_3axyy0_4le/clone/recipe/meta.yaml:32: no_git_on_windows: git should not be used as a dependency on Windows.
ERROR: /tmp/abs_3axyy0_4le/clone/recipe/meta.yaml:35: patch_must_be_in_build: patch must be in build when source/patches is set.
ERROR: /tmp/abs_3axyy0_4le/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3axyy0_4le/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3axyy0_4le/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3axyy0_4le/clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3axyy0_4le/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_3axyy0_4le/clone/recipe/meta.yaml:54: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:53: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

An error on osx-64:
dyld[1064]: Library not loaded: @rpath/libzstd.1.dylib

  Referenced from: <72742B14-65A8-3066-A0E4-314A22D5ECE8> /private/var/folders/c_/qfmhj66j0tn016nkx_th4hxm0000gp/T/abs_ddtlf7r4qf/pkg_dirs/cmake-3.26.4-hbb7d193_0/bin/cmake

  Reason: tried: '/private/var/folders/c_/qfmhj66j0tn016nkx_th4hxm0000gp/T/abs_ddtlf7r4qf/pkg_dirs/cmake-3.26.4-hbb7d193_0/bin/../lib/libzstd.1.dylib' (no such file), '/private/var/folders/c_/qfmhj66j0tn016nkx_th4hxm0000gp/T/abs_ddtlf7r4qf/pkg_dirs/cmake-3.26.4-hbb7d193_0/bin/../lib/libzstd.1.dylib' (no such file<EMAIL_ADDRESS>(no such file), '/private/var/folders/c_/qfmhj66j0tn016nkx_th4hxm0000gp/T/abs_ddtlf7r4qf/pkg_dirs/cmake-3.26.4-hbb7d193_0/bin/../lib/libzstd.1.dylib' (no such file), '/private/var/folders/c_/qfmhj66j0tn016nkx_th4hxm0000gp/T/abs_ddtlf7r4qf/pkg_dirs/cmake-3.26.4-hbb7d193_0/bin/../lib/libzstd.1.dylib' (no such file), '/usr/local/lib/libzstd.1.dylib' (no such file), '/usr/lib/libzstd.1.dylib' (no such file, not in dyld cache)

An error on osx-64:
dyld[1064]: Library not loaded: @rpath/libzstd.1.dylib

  Referenced from: <72742B14-65A8-3066-A0E4-314A22D5ECE8> /private/var/folders/c_/qfmhj66j0tn016nkx_th4hxm0000gp/T/abs_ddtlf7r4qf/pkg_dirs/cmake-3.26.4-hbb7d193_0/bin/cmake

  Reason: tried: '/private/var/folders/c_/qfmhj66j0tn016nkx_th4hxm0000gp/T/abs_ddtlf7r4qf/pkg_dirs/cmake-3.26.4-hbb7d193_0/bin/../lib/libzstd.1.dylib' (no such file), '/private/var/folders/c_/qfmhj66j0tn016nkx_th4hxm0000gp/T/abs_ddtlf7r4qf/pkg_dirs/cmake-3.26.4-hbb7d193_0/bin/../lib/libzstd.1.dylib' (no such file<EMAIL_ADDRESS>(no such file), '/private/var/folders/c_/qfmhj66j0tn016nkx_th4hxm0000gp/T/abs_ddtlf7r4qf/pkg_dirs/cmake-3.26.4-hbb7d193_0/bin/../lib/libzstd.1.dylib' (no such file), '/private/var/folders/c_/qfmhj66j0tn016nkx_th4hxm0000gp/T/abs_ddtlf7r4qf/pkg_dirs/cmake-3.26.4-hbb7d193_0/bin/../lib/libzstd.1.dylib' (no such file), '/usr/local/lib/libzstd.1.dylib' (no such file), '/usr/lib/libzstd.1.dylib' (no such file, not in dyld cache)

Perhaps we need zstd package? It seems osx-64 was previously built succesfully? Perhaps something else provided zstd?

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_7d_t1_qm7_/clone/recipe/meta.yaml:32: no_git_on_windows: git should not be used as a dependency on Windows.
ERROR: /tmp/abs_7d_t1_qm7_/clone/recipe/meta.yaml:35: patch_must_be_in_build: patch must be in build when source/patches is set.
ERROR: /tmp/abs_7d_t1_qm7_/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_7d_t1_qm7_/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_7d_t1_qm7_/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_7d_t1_qm7_/clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_7d_t1_qm7_/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_7d_t1_qm7_/clone/recipe/meta.yaml:54: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:53: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_34yq26b0kq/clone/recipe/meta.yaml:32: no_git_on_windows: git should not be used as a dependency on Windows.
ERROR: /tmp/abs_34yq26b0kq/clone/recipe/meta.yaml:35: patch_must_be_in_build: patch must be in build when source/patches is set.
ERROR: /tmp/abs_34yq26b0kq/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_34yq26b0kq/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_34yq26b0kq/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_34yq26b0kq/clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_34yq26b0kq/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_34yq26b0kq/clone/recipe/meta.yaml:54: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:53: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_43tqcxy_86/clone/recipe/meta.yaml:35: patch_must_be_in_build: patch must be in build when source/patches is set.
ERROR: /tmp/abs_43tqcxy_86/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_43tqcxy_86/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_43tqcxy_86/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_43tqcxy_86/clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_43tqcxy_86/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_43tqcxy_86/clone/recipe/meta.yaml:54: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:53: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_c0aq72mwu4/clone/recipe/meta.yaml:34: jinja_render_failure: The recipe could not be rendered by Jinja2
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_75dd5jjp0b/clone/recipe/meta.yaml:47: jinja_render_failure: The recipe could not be rendered by Jinja2
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_fb9ii9hope/clone/recipe/meta.yaml:32: patch_must_be_in_build: patch must be in build when source/patches is set.
ERROR: /tmp/abs_fb9ii9hope/clone/recipe/meta.yaml:37: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_fb9ii9hope/clone/recipe/meta.yaml:38: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_fb9ii9hope/clone/recipe/meta.yaml:39: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_fb9ii9hope/clone/recipe/meta.yaml:40: build_tools_must_be_in_build: The build tool patch is not in the build section.
ERROR: /tmp/abs_fb9ii9hope/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_fb9ii9hope/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_fb9ii9hope/clone/recipe/meta.yaml:40: build_tools_must_be_in_build: The build tool m2-patch is not in the build section.
ERROR: /tmp/abs_fb9ii9hope/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_fb9ii9hope/clone/recipe/meta.yaml:43: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_fb9ii9hope/clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_fb9ii9hope/clone/recipe/meta.yaml:53: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:53: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_3by91yop59/clone/recipe/meta.yaml:39: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3by91yop59/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3by91yop59/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3by91yop59/clone/recipe/meta.yaml:43: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3by91yop59/clone/recipe/meta.yaml:44: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_3by91yop59/clone/recipe/meta.yaml:53: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:53: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_18q2e_a9l2/clone/recipe/meta.yaml:38: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_18q2e_a9l2/clone/recipe/meta.yaml:39: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_18q2e_a9l2/clone/recipe/meta.yaml:40: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_18q2e_a9l2/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_18q2e_a9l2/clone/recipe/meta.yaml:43: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_18q2e_a9l2/clone/recipe/meta.yaml:52: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:53: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_bdr6xn65le/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_bdr6xn65le/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_bdr6xn65le/clone/recipe/meta.yaml:43: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_bdr6xn65le/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_bdr6xn65le/clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_bdr6xn65le/clone/recipe/meta.yaml:55: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:53: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_6cw3m6qwj7/clone/recipe/meta.yaml:41: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_6cw3m6qwj7/clone/recipe/meta.yaml:42: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_6cw3m6qwj7/clone/recipe/meta.yaml:43: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_6cw3m6qwj7/clone/recipe/meta.yaml:45: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_6cw3m6qwj7/clone/recipe/meta.yaml:46: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_6cw3m6qwj7/clone/recipe/meta.yaml:55: python_build_tool_in_run: The python build tool packaging is in run depends
ERROR: build.sh:53: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
Errors were found


Allow change of database engine and location in config.py

Example:
db_engine = 'sqlite'

or
db_engine = 'postgresql'

fixed with https://github.com/PeerAssets/papi/pull/14


CRUD operation for Reminder

Is your feature request related to a problem? Please describe.
NA
Describe the solution you'd like

Create necessary code like ReminderDao, ReminderEntity, and ReminderRepositiry that facilitate CRUD operation for different screens.

Describe alternatives you've considered
NA
Additional context
NA

Assigned to @geetgobindsingh team as Siddu left the team.


Remove unused xmlEscaped String extension

Bug/issue #, if applicable: rdar://75712710
Summary
Removes an extension to String (xmlEscaped) that is not being used.
Dependencies
None.
Testing
Confirm that existing unit tests continue to pass.
Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[ ] Added tests N/A. This is entirely code removal.
[x] Ran the ./bin/test script and it succeeded
[x] Updated documentation if necessary

@swift-ci please test


Fixed IllegalStateException: Cache is already released

Can you please review this and update if there is any issue or should i close this one?

hi,
Any update on this?

Thanks,
Any thought on the hibernate 3.6.10 compatibility PR?
On Fri, Dec 28, 2018 at 4:34 PM Jonathan Knight<EMAIL_ADDRESS>wrote:

Merged #3
https://github.com/coherence-community/coherence-hibernate/pull/3 into
master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/coherence-community/coherence-hibernate/pull/3#event-2047076493,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFD1kv3PKCwmCfDtAAJz1mIyYqAKZp_rks5u9fOdgaJpZM4LqTGy
.

--
Thank You
Mohammad Al- Mubin Sultan
Senior Software Engineer
+8801708518062


⚠ Samsung has degraded performance

In 409fff8, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2922 ms

Resolved: Samsung performance has improved in 087ed3b.


unable to exclude channels when using k-means clustering to find neighborhoods

Please refer to our FAQ and look at our known issues before opening a bug report.
Describe the bug
when running the example neighborhood analysis script to perform k means clustering using the spatial_analysis.generate_cluster_matrix_results function, I encountered a key error stating the specified channel to exclude is not found in axis" even though I specified the correct channel column name in my spatial enrichment input cell table (attached). In addition, I would like to know the way to perform k means clustering with no channels excluded (include all channels). I tried setting excluded_channels = [""] or excluded_channels = None but neither of the methods worked.
Expected behavior
the jupyter cell runs and k-means clustering results are generated
To Reproduce

reg001_X05_Y05_final_cell_type_assignment_for_neighborhood.csv

Hi Nancy! In settings.py (this file is located in ark-analysis/ark), can you make sure that PRE_CHANNEL_COL and POST_CHANNEL_COL are set to the correct values? These should be the column names in your data table right before and after all the channel names. In the csv you linked, I think PRE_CHANNEL_COL = "centroid-1" and POST_CHANNEL_COL = "label". Hopefully that will allow you to specify excluded channels.
If you don't want to exclude any channels, I just opened a pull request for that fix. While we are waiting for someone to review that code and merge it into the main branch, you can checkout that branch using "git checkout kmeans_nh_no_excluded_channels_fix" - which should let you set excluded_channels = None.

@ngreenwald should we put somewhere in the documentation to make sure settings.py matches with the data table? Specifying PRE_CHANNEL_COL and POST_CHANNEL_COL in settings was Adam's code (and I think is used elsewhere, not just in the kmeans notebook). I don't think it currently handles the case where a channel column is either the first or last column in the table (i.e. if there is no pre or post channel column).

I think our assumption is that anyone using the spatial analysis scripts will have generated their cell table with Mesmer/Pixie. Is there a scenario where that would produce a cell table without a pre-channel or post-channel column?

If the assumption is that everyone's cell table was generated with Mesmer/Pixie, then probably not necessary unless people manually change their cell table for some reason. I think it would be good to document somewhere that settings.py can be changed to accommodate different cell tables (maybe readthedocs somewhere?)


Check why label status for build is red

Label status for circleci is red on gitbug but on circle page is green !!
Can you check why?

check is done!!


Latest commit (46155ed) causes crash when entering keybinds menu

As in title, commit 46155ed appears to cause a crash when accessing the keybinds menu via [ESC] -> Options -> Controls -> Key Binds. Crash log attached.
crash-2023-05-01_20.14.16-client.txt

PR #93 fixes this


install-package-by-b64

The PackageInstallationSpec already accepts a package binary via the myPackageContents field - Why not just use that?


pull request for e2e test at 02/01/2017 04:15:11

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


posts folder is not recognized

I have a posts folder in my website. I have few posts inside that folder which are .md files. But when I see the RSS it does not show any posts.

Do you have a link to your site we can take a look at?
Posts should be in a _posts folder and post filenames must conform to the pattern YYYY-MM-DD-title.md.


[Bug report] Webpack doesnt compile vuepress components in a Vue CLI application

Bug report
First I want to thank you all for the great job you do, and apologize in advance if my issue form is lacking anything. Its the first time I ever fill an issue on an OSS repository so I kinda have no clue what I'm doing but I did my best to fill everything up correctly.
Description
When creating a Vue 3 application with the latest version of the Vue CLI, and adding vuepress@next to the project, the vue components outputed by vuepress are generated from Markdown properly, but can't be compiled by webpack and served.
Steps to reproduce
Install the latest version of the Vue CLI (4.5.11 on my machine)
yarn global add @vue/cli

Create a new vue 3 project
vue create my-project

Add vuepress to the project according to this documentation (starting at step 3 since we already have a vue project)
Serve the vuepress documentation
yarn docs:dev

You can find a reproduction here, this is a quick example and I used a custom Vue CLI preset I use all the time. (Basically Vue 3 with TypeScript and test)
Expected behavior
The Vue components generated by vuepress should compile successfuly and be available on the development server.
Console output
Output of yarn docs:dev :
$ vuepress dev docs
info Initializing VuePress and preparing data...
√ Compilation finished in 574ms
ERROR in<EMAIL_ADDRESS>2:0-28
Module not found: Error: Can't resolve 'style-loader' in 'C:\Users\pierr\Documents\Code\kerunix\Bug Repros\test-version'

ERROR in<EMAIL_ADDRESS>3:0-35
Module not found: Error: Can't resolve 'style-loader' in 'C:\Users\pierr\Documents\Code\kerunix\Bug Repros\test-version'

ERROR in<EMAIL_ADDRESS>4:0-33
Module not found: Error: Can't resolve 'style-loader' in 'C:\Users\pierr\Documents\Code\kerunix\Bug Repros\test-version'

ERROR in<EMAIL_ADDRESS>5:0-29
Module not found: Error: Can't resolve 'style-loader' in 'C:\Users\pierr\Documents\Code\kerunix\Bug Repros\test-version'

ERROR in ./docs/.vuepress/.temp/pages/readme.vue
Module Error (from ./node_modules/vue-loader/lib/index.js):
[vue-loader] vue-template-compiler must be installed as a peer dependency, or a compatible compiler implementation must be passed via options.

ERROR in ./docs/.vuepress/.temp/pages/readme.vue
Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (C:\Users\pierr\Documents\Code\kerunix\Bug Repros\test-version\node_modules\@vue\component-compiler-utils\dist\parse.js:15:23)
    at Object.module.exports (C:\Users\pierr\Documents\Code\kerunix\Bug Repros\test-version\node_modules\vue-loader\lib\index.js:67:22)

ERROR in ./docs/.vuepress/.temp/pages/404.html.vue
Module Error (from ./node_modules/vue-loader/lib/index.js):
[vue-loader] vue-template-compiler must be installed as a peer dependency, or a compatible compiler implementation must be passed via options.

ERROR in ./docs/.vuepress/.temp/pages/404.html.vue
Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (C:\Users\pierr\Documents\Code\kerunix\Bug Repros\test-version\node_modules\@vue\component-compiler-utils\dist\parse.js:15:23)
    at Object.module.exports (C:\Users\pierr\Documents\Code\kerunix\Bug Repros\test-version\node_modules\vue-loader\lib\index.js:67:22)

ERROR in<EMAIL_ADDRESS>Module Error (from ./node_modules/vue-loader/lib/index.js):
[vue-loader] vue-template-compiler must be installed as a peer dependency, or a compatible compiler implementation must be passed via options.

ERROR in<EMAIL_ADDRESS>Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (C:\Users\pierr\Documents\Code\kerunix\Bug Repros\test-version\node_modules\@vue\component-compiler-utils\dist\parse.js:15:23)
    at Object.module.exports (C:\Users\pierr\Documents\Code\kerunix\Bug Repros\test-version\node_modules\vue-loader\lib\index.js:67:22)

ERROR in<EMAIL_ADDRESS>Module Error (from ./node_modules/vue-loader/lib/index.js):
[vue-loader] vue-template-compiler must be installed as a peer dependency, or a compatible compiler implementation must be passed via options.

ERROR in<EMAIL_ADDRESS>Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (C:\Users\pierr\Documents\Code\kerunix\Bug Repros\test-version\node_modules\@vue\component-compiler-utils\dist\parse.js:15:23)
    at Object.module.exports (C:\Users\pierr\Documents\Code\kerunix\Bug Repros\test-version\node_modules\vue-loader\lib\index.js:67:22)

ERROR in<EMAIL_ADDRESS>Module Error (from ./node_modules/vue-loader/lib/index.js):
[vue-loader] vue-template-compiler must be installed as a peer dependency, or a compatible compiler implementation must be passed via options.

ERROR in<EMAIL_ADDRESS>Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (C:\Users\pierr\Documents\Code\kerunix\Bug Repros\test-version\node_modules\@vue\component-compiler-utils\dist\parse.js:15:23)
    at Object.module.exports (C:\Users\pierr\Documents\Code\kerunix\Bug Repros\test-version\node_modules\vue-loader\lib\index.js:67:22)

ERROR in<EMAIL_ADDRESS>Module Error (from ./node_modules/vue-loader/lib/index.js):
[vue-loader] vue-template-compiler must be installed as a peer dependency, or a compatible compiler implementation must be passed via options.

ERROR in<EMAIL_ADDRESS>Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (C:\Users\pierr\Documents\Code\kerunix\Bug Repros\test-version\node_modules\@vue\component-compiler-utils\dist\parse.js:15:23)
    at Object.module.exports (C:\Users\pierr\Documents\Code\kerunix\Bug Repros\test-version\node_modules\vue-loader\lib\index.js:67:22)

ERROR in<EMAIL_ADDRESS>Module Error (from ./node_modules/vue-loader/lib/index.js):
[vue-loader] vue-template-compiler must be installed as a peer dependency, or a compatible compiler implementation must be passed via options.

ERROR in<EMAIL_ADDRESS>Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (C:\Users\pierr\Documents\Code\kerunix\Bug Repros\test-version\node_modules\@vue\component-compiler-utils\dist\parse.js:15:23)
    at Object.module.exports (C:\Users\pierr\Documents\Code\kerunix\Bug Repros\test-version\node_modules\vue-loader\lib\index.js:67:22)

ERROR in<EMAIL_ADDRESS>Module Error (from ./node_modules/vue-loader/lib/index.js):
[vue-loader] vue-template-compiler must be installed as a peer dependency, or a compatible compiler implementation must be passed via options.

ERROR in<EMAIL_ADDRESS>Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (C:\Users\pierr\Documents\Code\kerunix\Bug Repros\test-version\node_modules\@vue\component-compiler-utils\dist\parse.js:15:23)
    at Object.module.exports (C:\Users\pierr\Documents\Code\kerunix\Bug Repros\test-version\node_modules\vue-loader\lib\index.js:67:22)

ERROR in<EMAIL_ADDRESS>Module Error (from ./node_modules/vue-loader/lib/index.js):
[vue-loader] vue-template-compiler must be installed as a peer dependency, or a compatible compiler implementation must be passed via options.

ERROR in<EMAIL_ADDRESS>Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (C:\Users\pierr\Documents\Code\kerunix\Bug Repros\test-version\node_modules\@vue\component-compiler-utils\dist\parse.js:15:23)
    at Object.module.exports (C:\Users\pierr\Documents\Code\kerunix\Bug Repros\test-version\node_modules\vue-loader\lib\index.js:67:22)

webpack compiled with 22 errors
success VuePress webpack dev server is listening at http://localhost:8081/

What I tried
I tried to fix the above errors by installing the dependencies that were required with
yarn add -D style-loader
yarn add -D vue-template-compiler

I also believes the issue was related to a conflicting version of vue-loader so I installed version 16.1.2 in my project without any success.
Both solutions changed the error messages outputed in the console but I did not include them in the provided reproduction because I figured maybe you wanted to tinker with it.
Environment info

Browser: Not relevant here
Output of vuepress info:

  System:
    OS: Windows 10 10.0.19041
    CPU: (8) x64 Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
    Memory: 3.68 GB / 15.96 GB
  Binaries:
    Node: 12.18.4 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.12.3 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.14.6 - C:\Program Files\nodejs\npm.CMD
  Utilities:
    Git: 2.16.2. - /mingw64/bin/git
  Browsers:
    Chrome: 88.0.4324.182
    Edge: Spartan (44.19041.423.0), Chromium (88.0.705.68)
  npmPackages:
    @vuepress/bundler-webpack:  2.0.0-alpha.24
    @vuepress/cli:  2.0.0-alpha.24
    @vuepress/client:  2.0.0-alpha.24
    @vuepress/core:  2.0.0-alpha.24
    @vuepress/markdown:  2.0.0-alpha.24
    @vuepress/plugin-active-header-links:  2.0.0-alpha.24
    @vuepress/plugin-back-to-top:  2.0.0-alpha.24
    @vuepress/plugin-container:  2.0.0-alpha.24
    @vuepress/plugin-debug: Not Found
    @vuepress/plugin-docsearch: Not Found
    @vuepress/plugin-git:  2.0.0-alpha.24
    @vuepress/plugin-google-analytics: Not Found
    @vuepress/plugin-medium-zoom:  2.0.0-alpha.24
    @vuepress/plugin-nprogress:  2.0.0-alpha.24
    @vuepress/plugin-palette-stylus:  2.0.0-alpha.24
    @vuepress/plugin-pwa: Not Found
    @vuepress/plugin-pwa-popup: Not Found
    @vuepress/shared:  2.0.0-alpha.24
    @vuepress/theme-default:  2.0.0-alpha.24
    @vuepress/theme-vue: Not Found
    @vuepress/utils:  2.0.0-alpha.24
    vue: ^3.0.0 => 3.0.5
    vue-loader:  15.9.6 (16.1.2)
    vue-router:  4.0.4
    vuepress: ^2.0.0-alpha.24 => 2.0.0-alpha.24

Seems you are using vue-cli v4, which is depending on webpack v4.
VuePress v2 is using webpack v5, so you'd better try vue-cli v5 (currently 5.0.0-alpha.4)

BTW, the<EMAIL_ADDRESS>is for vue2 only, and you should always use<EMAIL_ADDRESS>for vue3 project.

Upgrading Vue CLI to version 5.0.0-alpha fixed the issue, did not realize that Vue CLI v4 and VuePress v2-alpha were using different versions of Webpack. Thank you very much for your help !


Clarify that breaking the Pointer Aliasing Rules requires an access

This clarifies that you must access a pointer to violate LLVM's Pointer Aliasing Rules.
From a discussion today on #rust with @ubsan and @rkruppe

This is a good change, imo.

Thanks!


Control video player using tv remote

Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have updated the app to the latest version.
[X] I will fill out all of the requested information in this form.

Describe your suggested feature
i've tested aniyomi preview on android tv. It's working fine but inability to control video player using remote control is really annoying i need to use mouse to control video player.
Other details
No response

#162 is the same, closing this to avoid clutter


Issues with the integration with the AZ PACS service.

Hello there, I am trying to integrate the OHIF renderer with the hosted Azure service where all my Dicom files are dumped, I have replaced the DicomWeb endpoints but I don't have any clue on where can I place the access token so that the request from the viewer can be authorised.

@adamwimmj Can you guide me more on how I can set up OIDC in the local viewer, I have AZ services deployed and configured and have creds.

Look here https://docs.ohif.org/deployment/authorization


[Sample 14][C#] Made README note about adding subscriptionKey prominent

Fixes #1211
Proposed Changes
This is a simple README change to make the note about adding the subscriptionKey to the dispatch service in the .bot file more prominent. User missed it and I did as well while testing.

I've pushed this into master, but FWIW, this sample has been updated significantly for the 4.4 release.  among other things, we no longer are promoting the use of .bot files.  samples-work-in-progress contains the pending 4.4 release work.


FIX: Cast thumbnail size to integer

1. Why is this change necessary?
Currently it is possible to call getWidth() or getHeight() on MediaThumbnailEntity and get the error "Shopware\Core\Content\Media\Aggregate\MediaThumbnail\MediaThumbnailEntity::getWidth(): Return value must be of type int, string returned"
2. What does this change do, exactly?
This change make sure that width and height are assigned as integer instead of string
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Checklist

[x] I have rebased my changes to remove merge conflicts
[ ] I have written tests and verified that they fail without my change
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

Greetings. We noticed, that your change is breaking. We can't just merge it into master because of that.
Know, I would like to deprecate the changes in entity, so they can be introduced in 6.7. Would that be fine for you?

Greetings. We noticed, that your change is breaking. We can't just merge it into master because of that. Know, I would like to deprecate the changes in entity, so they can be introduced in 6.7. Would that be fine for you?

Hey 😄 that's totally fine with me

Your Pull Request has been merged! :tada:
Thanks for your contribution! :blue_heart:


Delint project

Currently there are a vast amount of rubocop errors and warnings that are thrown (over 1k).  This should be addressed to gain adherence to proper code formatting and current Ruby suggestions where possible.  If there are specific smells that we decide to avoid, we need to create a rubocop config file to ignore them.

We need to be a little cautious with this.
Rubocop if nothing if not HIGHLY opinionated and sometimes it actually suggests doing stuff that breaks the ruby styleguide (just look what happens if you try to use method missing to make a facade, it suggests solutions for refactor that actively change the outward behavior of your code.)
If we want to rely on it more heavily, we need to ensure we've got a good profile configured for it.
Current problems it detects in the oz codebase itself tend to be:

ABC Complexity: This refers to assignment, branching and conditions.  It basically means that your method is probably breaking the single responsibility principle.  Router's get_routes_between method falsely throws this because it assigns a lot of local variables, uses a loop and has multiple exits, including a guard statement. (This could theoretically be fixed but requires a pretty big rewrite, not refactor, of how router works.)

Method Has too many lines: This is a FUN one.  Rubocop simultaneously likes to yell about this while ALSO telling you that guard statements need an extra line after them among other things that force a longer method. It also discourages you from saving variables to give the results of various method calls a more.

Too many instance variables: Right then.  So don't use model classes at all?


AdvSample > Wind Turbine DataView > Type/Stream Creation

Added notebook entries at the end, just before the prediction data is written to OCS, that create the type and the stream using the OCSClient library. Creating the type and stream makes logical sense within the notebook after the ML portion that builds the model since, theoretically, only at that point do you know from the ML model which fields are important for the prediction.
The type/stream creation demonstrates OCS Client library usage, pulled mostly from the basic samples > SDS.

I haven't look at the notebook diff but you may want to do the following within this PR:

remove the autosave notebook directory .ipynb_checkpoints (good candidate for .gitignore)
delete the binary model file WT_ActivePower_model.sav generated by the notebook

Suggestion: to make output easier to scroll, you could replace "data" by "data[:5]" in cell[3] to truncate it yourself (it's already truncated but arbitrarily and kept too long, imho)

Figured out why the tests were failing, and we need to discuss it further on how to best approach it, but this most recent commit should (?) pass the tests (or at least not fail the same way). I also truncated the output at each step (except for the weather json response) to keep the notebook shorter, per @cfoisy-osisoft recommendation.

as a reminder, this is not ready for PR review yet, but should be soon. Rather than close the PR, I'll make a couple more commits this week and we should be good.

for some reason the dataview.json did not create the data view successfully, but it did create the other types and streams, and it uploaded all the (meta)data. I'll look into this tomorrow.

this PR should (finally) be ready for review.

I removed the Type and Stream for the created predicted power values from the bulkuploader section and moved them into the jupyter notebook itself following the creation of the power prediction algorithm.
Also changed the default appsettings file for this sample's bulk uploaded data since it was missing the property for the dataview, so the data view did not get created.
I truncated some of the outputs to keep the notebook a little shorter

@derekendres you're right, I forgot to switch the two sections like I had intended. I moved the Data Overview section to be underneath the Getting Started section, so that if you jump to the Getting Started section right off the bat, you still get to the Data Overview section


New article for System Diagnostics

Status
Ready/In Progress/In Hold (Reason for hold)
Related Issues
fixes: link to the issue
Description
A few sentences describing the overall goals of the pull request's commits.
Screenshots
Paste here any images that will help the reviewer

@MariaBord Please approve this again.  Thanks,


Allow to specify alternate server name for postfixadmin

https://github.com/zuazo/postfix-dovecot-cookbook/blob/master/recipes/postfixadmin.rb#L22 explicitly sets the node['postfixadmin']['server_name'].
On some configurations I do want to be able to override it looks like it is not possible at the moment.

If you are having problems with that, you can always overwrite it using node.override:
node.override['postfixadmin']['server_name'] = 'postfixadmin.example.com'

https://docs.chef.io/attributes.html#attribute-types

Nope, it does not work. What I'm trying to achieve is to set it to nil. node.override['postfixadmin']['server_name'] = nil does not work for me. But when I remove the line mentioned above it starts working just fine.

Why do you want to set it to nil instead of other value? What error gives you?

I'm getting 403 Forbidden for postfixadmin URL due to hostname mismatch. I can work around it, though.


[Feature]: Implement CI validation of shell scripts using shellcheck

According to its docs, the shellcheck tool already comes pre-installed in Github runners, so we could add a workflow that will validate all build scripts we use.
Currently running it against our scripts produces 83 warnings, so first we'd need to review them and fix the issues (or disable some lint checks), before we can enable the linter in CI.
$ shellcheck scripts/*sh | grep '^In ' | wc -l
      83

hi @yurishkuro  i would like to take on this issue, i am a beginner here so can you please guide how do i approach this issue

@yurishkuro which issues should i fix and on which should i disable lint checks

@yurishkuro can I also work on this issue ?

/assign


Create integration test to check KongUpstreamPolicy status gets properly set

Problem Statement
The KongUpstreamPolicy controller builds and enforce the status in the KongUpstreamPolicy resources. We need to add an integration test that checks the following

an HTTPRoute references two services: both services reference the same policy. The Policy Status must reflect this situation by setting proper ancestors conditions
an HTTPRoute references two services: service A references policy A and service B references policy B. The Policy Status must reflect this situation by setting proper ancestors conditions
an Ingress references two services: both services reference the same policy. The Policy Status must reflect this situation by setting proper ancestors conditions
an Ingress references two services: service A references policy A and service B references policy B. The Policy Status must reflect this situation by setting proper ancestors conditions

Acceptance Criteria

[ ] the above tests are added

Blocked by https://github.com/Kong/kubernetes-ingress-controller/issues/4932


Use tables to represent markdown parameters

The parameters in the previous markdown view were pretty ugly, and did not show the scope parameters. I made is so parameters are now rendered in a markdown table instead.
I ran into one hitch, I could not for the life of me make the cucumber spec pass. I manually ran:
be rspec app_spec.rb --require ./app.rb --format RspecApiDocumentation::ApiFormatter
Against a copy and pasted app_spec.rb and app.rb, and then diffed the outputs. They were exactly the same. I have no idea how to debug these cucumber tests, so I am probably doing it wrong. Any tips would be hugely appreciated :smile:
Thanks for maintaining such a useful project!
EDIT: Looks like the specs passed on CI! Must be a local bug.

Here is what it looks like:
Imgur

@oestrich any chance we can get this merged?

Ping.

@zipmark Ping.

👍

Sorry for just getting around to this. Looks good. Thanks!


Relative path as parameter values for -source and -destination

Currently we have to pass the whole path of the files as values to the flags -source and -destination.
eg:
mockgen -source=D:\go_project\library_management\src\core\ports\repository.go -destination=D:\go_project\library_management\src\core\mocks\respository_mock.go
(In windows)
To reduce this redundancy in type, we can use the relative path.
Assuming mockgen is used from the targeted codebase.

Hey @Abhishekkarunakaran, I see examples of relative paths being passed to the --source and --destination options for the mockgen command in the //go:generate comments of multiple files in the repository.

In my understanding, the relative path is only available in reflect mode, not in source mode.

In Windows, to avoid passing the full path like -source=D:\go_project\library_management\src\core\ports\repository.go you can pass the relative path between quotes like this -source="src\core\ports\repository.go".


Added coding platform - codewars for DSA

Pull Request
Description
Added coding platform - codewars for DSA
@jfmartinz Please review and merge this PR.
Closes #1580
Type of change

[x] Adding a new Resource
[x] Adding a new Category
[x] Documentation enhancement or fixes
[x] Website enhancement or fixes

Checklist:

[x] I read carefully CONTRIBUTING.md
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation

@jfmartinz Please review and merge this PR.

@sanjay-kv  Please merge this PR as soon as possible.

I can't merge on somebody's repos.
I suggested a in news letter to raise this Pr on specified repo
So don't tag me and spam

I can't merge on somebody's repos. I suggested a in news letter to raise this Pr on specified repo So don't tag me and spam

@sanjay-kv Ok sir. I am not spamming. I have raised this PR on the specified repo.
Sorry for this inconvenience.


Producing a CHANGELOG for MOSRS vn0.10.0

I'm going to use this issue to develop a CHANGELOG (for inclusion in our repository) of the changes recently put on MOSRS. The aim is to indicate which changes are bugs vs features and where there are breaking changes

Below is copied from email from Adrian Hill

As I have already stated, this commit includes many more changes in addition to the solver change and we have been attempting to keep track of these changes with the trac ticket system. The main summary ticket is https://code.metoffice.gov.uk/trac/monc/ticket/344, which covers

Significant changes to CASIM so that it includes the optimisations and science changes that have been developed as part of general global and regional science configurations for the UM - https://code.metoffice.gov.uk/trac/monc/ticket/337
*   It is  important to note that the new head of the MONC trunk (r8146) will not work with the CASIM trunk. Instead it only works with the CASIM package branch (https://code.metoffice.gov.uk/trac/monc/browser/casim/branches/pkg/adrianhill/vn0.3.4_ra_ga_package). Likewise, vn0.9.0 will work with the CASIM trunk but not work the CASIM package branch.  Vn0.3.4_ra_ga_package is the candidate for the next CASIM trunk commit and it is being tested and reviewed now in prep for commit so that it works with both the UM and MONC. I hope this makes sense and I am sorry I was not able to make a smooth transition in which CASIM at all versions work with all MONC version, but the updates for CASIM so that it works with a cloud fraction scheme the UM required a change to the argument list.   Hope this makes sense
Fixes to the model_core to allow MONC to build with the latest cray compilers and intel 17. I have performed limited testing with other versions of intel compiler and there are issues but it is unclear whether these issues relate to associated libraries, compiler bugs or MONC coding issues. Having said that,this is the first time that MONC is working with intel compiler since about 2014!
*   An outstanding issue with this commit is a restart issue/seg fault with the gfortran, which is being investigated
Significant changes and improvements from Reading (thanks to Todd Jones for implementing these) https://code.metoffice.gov.uk/trac/monc/ticket/345

It is important to note that all these changes will change answers compared to old simulations because of the new fft solver and the CASIM changes. The changes related to the fft are small but changes related to CASIM will be more significant.

Summary of changes:

external requirement changed: CASIM on MOSRS "package branch" https://code.metoffice.gov.uk/trac/monc/browser/casim/branches/pkg/adrianhill/vn0.3.4_ra_ga_package

FEAT, (not breaking?): support for intel compiler

BREAKING: restart/segfault issue with gfortran

what is the status on this?

BREAKING: FFTW no longer available and replaced with FFTE

what changes to input files are required?


Remove reindex and vacuum scripts

No longer needed after https://github.com/ManageIQ/manageiq/pull/16940 and https://github.com/ManageIQ/manageiq/pull/16929
@miq-bot assign @carbonin

This is dependent on https://github.com/ManageIQ/manageiq-appliance_console/pull/32, so I'm going to hold off on merging this one as well.


0.25.1 (#1245)

0.25 hotfixes

More fixes

Manifest and changelog

Does not fix this error:
https://github.com/foundryvtt-starfinder/foundryvtt-starfinder/blob/de533d14e09c791f0966cc4c9f017fdd063eb7ab/src/module/rules/actions/actor/calculate-encumbrance.js#L11
encumbrance is called before it is created. It should be data.encumbrance


Documentation for cwlpack and WDL-equivalent

Is your feature request related to a problem? Please describe.
Workflows with HTTP imports are not very reproducible. It should be discouraged.
Describe the solution you'd like
Add to the best practices documentation for CWL/WDL or registration to avoid HTTP imports. Point to cwlpack and wdl equivalent.
Describe alternatives you've considered
Having this somehow displayed in the frontend instead during registration
Additional context
See https://docs.google.com/document/d/1HbyMKKVGP8ELL0dG3Pq_GXDPT22qip5nv3ZgFmi2tK4/edit
┆Issue is synchronized with this Jira Story
┆Issue Number: DOCK-1980
┆Sprint: Backlog
┆Issue Type: Story

Even if we put reproducibility aside, I'm of the opinion that imports have security implications.
Let's say I had no affiliation with Dockstore or any other institution that could reign me in, but I made some pretty swell WDLs, and someone from the Broad imported my array comparison WDL into a GATK workflow like this:
import https://raw.githubusercontent.com/aofarrel/Stuart-WDL/main/arraycheck_simple.wdl

This seems to have three big issues:

The Broad assumes that I, random GitHub user aofarrel, am not going to covertly turn the stuart_arraycheck_simple task into a bitcoin miner
The Broad assumes that I, random GitHub user aofarrel, do not leave my GitHub password on a sticky note in Starbucks which may allow a bad actor to turn stuart_arraycheck_simple into a bitcoin miner
By not linking to a specific tagged commit, the workflow is not immutable -- you will pull the latest commit from main, which could be broken in a no-fault scenario, or in a bad actor scenario, a bitcoin miner

We could get philosophical about "well, can you really trust anybody?" but what I'm getting at here is that us having no guidelines at all seems to open the door to everything from "importing within the same GitHub repo's tagged commit" to "importing from some random guy's /dev/ branch". This question of imports has come up, and will likely come up again, in discussions surrounding workflow verification (eg discussion about bronze/silver/gold for BDC).
Any WDL can of course could be maliciously written, but imports in particular seem to provide an opportunity. Let's be real, who among us has pulled up a Python script, noticed it imports pandas, and then decided to read the entirety of pandas? I think it's safe to say that people treat WDL imports the same way -- they will at least do a quick visual scan of the WDL, but it's unlikely that they'll look at the tasks being imported.

This is all true.
In fact, I would go a little further and say that even linking to a tagged commit may be insufficient. Tags can be deleted and re-created. SHA-1s can be attacked and duplicated.
We need to get to the point where snapshots are complete packed representations of a workflow and then that signals that they are complete and production-ready in TRS.
The question in the storytime was whether we need to help users do the packing (and to what degree) or whether it makes sense to put that burden on the user (with the upside that they also test that packed version).

Quick note: I changed the title of this ticket as cwlpack is technically part of sbpack and doesn't always show up on search on its own.


Need more info regarding PR template

Looking at your PULL_REQUEST_TEMPLATE.md some questions come to my mind:

How Has This Been Tested?

Um, it's documentation. What is to be tested here? What format do you expect? Payload from postman?

Screenshots (if appropriate)

When would that be appropriate? We are basically talking about requests and responses here. I am struggling understanding, how a screenshot should help here.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)

What kind of functionality does a documentation have? :-)
Was that copy-pasted from other Adobe projects?

My code follows the code style of this project.

Where can I find the style guide?

My change requires a change to the documentation.
I have updated the documentation accordingly.

My change would be an update to the documentation. Or am I missing here something?

I have added tests to cover my changes.
All new and existing tests passed.

See above.

I've updated the template files via fbe1f5773ee576d571f9e3494e7b3d010f1d3a6d so that they apply to API docs instead of Adobe's generic open source template.


bootupd: Don't require /boot mount point

I'd like to change bib to just drop the separate /boot partition by default because it isn't doing anything useful right now.
A separate /boot is only useful with things like LUKS or LVM, but since bib doesn't do those now and it's not in the near term roadmap clearly either, let's just not add the complexity of a separate /boot by default.

Can you please run gofmt on pkg/osbuild/bootupd_stage.go? It complains about whitespace.


Date_Format isnt working

hello i have been trying to use query . This works fine
SELECT DATE_FORMAT(startDateTime, '%T') as time  FROM doctorAtDoor.appointments;
but when i use in objection
 Appointments
                    .query()
                    // .select("startDateTime")
                    .select("DATE_FORMAT(startDateTime, '%T') as time ")
                    .where('doctorId', '=', doctorId)
                    .andWhere('dayId', '=', dayId)
                    .debug()

i get in debug

{ method: 'select',
  options: {},
  timeout: false,
  cancelOnTimeout: false,
  bindings: [ 1, 1 ],
  __knexQueryUid: '9196b4e5-b096-47d0-a99b-eb880b514fda',
  sql: 'select `DATE_FORMAT(startDateTime, \'%T\')` as `time` from `appointments` where `doctorId` = ? and `dayId` = ?' }
 query seems fine but i am getting error

`Unhandled rejection Error: ER_BAD_FIELD_ERROR: Unknown column 'DATE_FORMAT(startDateTime, '%T')' in 'field list'`

You need to use raw to use SQL functions in your select.

Your query should look something like ...
const { raw } = require('objection');

Appointments
    .query()
    .select(raw("date_format(??, '%T') as time", ['startDateTime']))

... and so on.
Since startDateTime is case sensitive, you're probably also going to need to quote the identifier as above.
See http://vincit.github.io/objection.js/#raw-queries for more.

Objection and knex escape all inputs by default to prevent SQL injection attacks. You need to use raw just like jordansexton suggested.

thx. it works