Code crashes before reaching main function

Hi,
I have tried to build tensorflow_cc on a new system (I've already got it on two), These are the last lines of the "make" command:
Target //tensorflow:libtensorflow_cc.so up-to-date:   bazel-bin/tensorflow/libtensorflow_cc.so INFO: Elapsed time: 6615.420s, Critical Path: 914.46s INFO: Build completed successfully, 5743 total actions find: ‘./bazel-tensorflow/external/cub_archive/tune’: No such file or directory find: ‘./bazel-tensorflow/external/cub_archive/.settings’: No such file or directory find: ‘./bazel-tensorflow/external/cub_archive/.cproject’: No such file or directory find: ‘./bazel-tensorflow/external/cub_archive/LICENSE.TXT’: No such file or directory find: ‘./bazel-tensorflow/external/cub_archive/eclipse code style profile.xml’: No such file or directory find: ‘./bazel-tensorflow/external/cub_archive/test’: No such file or directory find: ‘./bazel-tensorflow/external/cub_archive/WORKSPACE’: No such file or directory find: ‘./bazel-tensorflow/external/cub_archive/common.mk’: No such file or directory find: ‘./bazel-tensorflow/external/cub_archive/cub’: No such file or directory find: ‘./bazel-tensorflow/external/com_google_absl’: No such file or directory find: ‘./bazel-tensorflow/external/png_archive’: No such file or directory find: ‘./bazel-tensorflow/external/local_jdk’: No such file or directory find: ‘./bazel-tensorflow/external/eigen_archive’: No such file or directory find: ‘./bazel-tensorflow/external/snappy’: No such file or directory find: ‘./bazel-tensorflow/external/jemalloc’: No such file or directory find: ‘./bazel-tensorflow/external/jpeg’: No such file or directory find: ‘./bazel-tensorflow/external/farmhash_archive’: No such file or directory find: ‘./bazel-tensorflow/external/local_config_git’: No such file or directory find: ‘./bazel-tensorflow/external/local_config_sycl’: No such file or directory find: ‘./bazel-tensorflow/external/bazel_tools’: No such file or directory find: ‘./bazel-tensorflow/external/gemmlowp’: No such file or directory find: ‘./bazel-tensorflow/external/llvm’: No such file or directory find: ‘./bazel-tensorflow/external/nasm’: No such file or directory find: ‘./bazel-tensorflow/external/com_googlesource_code_re2’: No such file or directory find: ‘./bazel-tensorflow/external/jsoncpp_git’: No such file or directory find: ‘./bazel-tensorflow/external/nsync’: No such file or directory find: ‘./bazel-tensorflow/external/gif_archive’: No such file or directory find: ‘./bazel-tensorflow/external/org_tensorflow’: No such file or directory find: ‘./bazel-tensorflow/external/lmdb’: No such file or directory find: ‘./bazel-tensorflow/external/zlib_archive’: No such file or directory find: ‘./bazel-tensorflow/external/local_config_cuda’: No such file or directory find: ‘./bazel-tensorflow/external/org_sqlite’: No such file or directory find: ‘./bazel-tensorflow/external/fft2d’: No such file or directory find: ‘./bazel-tensorflow/external/protobuf_archive’: No such file or directory find: ‘./bazel-tensorflow/bazel-out’: No such file or directory find: ‘./bazel-tensorflow/tensorflow’: No such file or directory find: ‘./bazel-tensorflow/third_party’: No such file or directory [ 87%] No build step for 'tensorflow_shared' [ 93%] No install step for 'tensorflow_shared' [100%] Completed 'tensorflow_shared' [100%] Built target tensorflow_shared
I have no idea about the lines like "find: ‘./bazel-tensorflow/third_party’: No such file or directory" but anyway I tried to build a cpp code with it (the one that I'm using on other systems without a problem), It builds all right but the code crashes before it even reaches the main which makes me think that the problem is with the tensorflow fuctions and libraries being linked.
I would appreciate any help. Thank you.

Hi, this is probably not an error.
There is an "unlink" process at the end of the build, and those lines only mean that the parent directory was already "unlinked". I also encounter this, but it does not break anything. What if you do make install and than build and run the example? Does it work for you?

Well, I have issued the make install command and the thing I'm talking about (program crashing before main) occurs after that. I have no idea what could cause this problem.

Can you try the v1.8.0 branch please?

And also provide the output of the actual failure of the program.

Would also be nice to know what is your build method? I assume it's not Docker ...

I'm not using the Docker. I git cloned the repository yesterday and then followed the instructions provided for building the project as a shared library. How can I try the 1.8.0 version? should I change the tf version in CmakeList.txt?
About the actual failure of the program, it doesn't give me anything special just that when I run it I get this output:
Illegal instruction (core dumped)
And when I debug it, the code crashes before even entering the main function.

I think 1.8.0 is a branch. Try git checkout v1.8.0.

Also, it would help if you paste the steps to reproduce the issue. That way we can try to replicate them on our side.

If it gives Illegal instruction, I suppose that you have a CPU older than haswell, right? I addressed this by a note in the readme in the v1.8.0 branch:
Warning: Optimizations for Intel CPU series >=haswell are enabled by default. If you have a
processor that is older than haswell series, you may wish to run export CC_OPT_FLAGS="-march=native" before the build.

OK, my CPU is Core i7, I think then it's older than Haswell right? So do I
still need to move to 1.8.0 version or try that line you mentioned in this
same version I got now?
On Fri, May 11, 2018 at 6:28 PM, Filip Matzner<EMAIL_ADDRESS>wrote:

If it gives Illegal instruction, I suppose that you have a CPU older than
haswell, right? I addressed this by a note
https://github.com/FloopCZ/tensorflow_cc/pull/86/files#diff-04c6e90faac2675aa89e2176d2eec7d8R96
in the readme in the v1.8.0 branch:
Warning: Optimizations for Intel CPU series >=haswell are enabled by
default. If you have a
processor that is older than haswell series, you may wish to run export
CC_OPT_FLAGS="-march=native" before the build.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/FloopCZ/tensorflow_cc/issues/97#issuecomment-388371793,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APaJX8wDkZEZFShkUlfO-9fpuxXxXZaHks5txZkMgaJpZM4T6xJl
.

It depends on what is the generation of the processor. You might have i7 Ivy Bridge that is older, or i7 Kaby Lake that is newer. So hard to say. :-)
Unless you want to migrate the built library between computers (probably not), use the
export CC_OPT_FLAGS="-march=native"`

before build. It should fix your issue, you don't need to use TensorFlow 1.8.0.
The v1.8.0 branch is now merged in master.

Thank you very much! I cloned the newest version and then issued the
command you said, before build. Now everything works perfectly!
On Fri, May 11, 2018 at 8:28 PM, Filip Matzner<EMAIL_ADDRESS>wrote:

It depends on what is the generation of the processor. You might have i7
Ivy Bridge that is older, or i7 Kaby Lake that is newer. So hard to say. :-)
Unless you want to migrate the built library between computers (probably
not), use the
export CC_OPT_FLAGS="-march=native"`
before build. It should fix your issue, you don't need to use TensorFlow
1.8.0.
The v1.8.0 branch is now merged in master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/FloopCZ/tensorflow_cc/issues/97#issuecomment-388406683,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APaJX-nh3BgaIn00eJdJ8yJXoTN15GVFks5txbUngaJpZM4T6xJl
.


Create POST endpoint to create geneset dataset links

Needs POST endpoint) /dp/v1/dataset/{dataset_uuid}/genesets

Expected body {“add”: [list of geneset uuids], “remove”: [list of geneset uuids]}
Return list of genesets that belong to the dataset (name, description, uuid)

Approach

Only possible if the linked collection is private
The request body should contain a list of geneset_uuids to link to the dataset to (under add)
In the backend retrieve a list of genesets the dataset is already linked to (from the db), if not already linked for genesets in request body create a row in the geneset_dataset_link table with the geneset and dataset ids

DOD

If no dataset exists return 403
If user is not owner of linked collection return 403
If linked collection is public return 403
If geneset does not exist or does not belong to the collection return 404 code with message “Invalid gene sets” - if FE sees that error message it will invalidate the geneset cache

Questions

If we remove genesets that don't exists do we fail silently? It makes sense to throw a 404 if we try adding a geneset that doesn't exist.
What do we return in the positive response?
Is this an all or nothing operation? If things partial fail do we roll back all of the changes?
What is the response if all of the genesets exist in the dataset?

We throw a 404.

For now, it's an all-or-nothing operation, but we should check with Harley and Brian. @hthomas-czi @brianraymor
Should be a 200.

all-or-nothing.


After installation, completion not being offered

I'm using a freshly installed version of VSC: 1.41.1 on linux.
After installing the extension and restarting VSC, completion for the boilerplate is not being offered.
I open a new file, save it with an .html suffix and start typing 'html5-boilerplate'.
Emmet completions are offered for the string 'html', but nothing is offered for 'html5-boilerplate'.

Please make sure the file extension in the bottom right corner says 'HTML'. If not, you can click on it and see it to HTML and then it should work.


web: initial slot end to end support

Ensure supports from create, link to git, swap, to deploy. Those are still the minimum, but enough to get basic functions. In the next period, we should consider to

enable private git repo.
create slot from existing configuration sources
extend slot delete to support auto delete site, etc

@derekbekoe @mayurid, this is low risk, and webapp specific change. Would you review it and consider included in the upcoming release?


tiller api return coded error

use  grpc status to return coded error for tiller grpc api
like we can change error define in release_server.go
var (
	// errMissingChart indicates that a chart was not provided.
	errMissingChart = errors.New("no chart provided")
        ...
)

into
import (
       "google.golang.org/grpc/status"
       "google.golang.org/grpc/codes"
)

var (
       errMissingChart = status.Errorf(codes.NotFound, "chart not found")
       ...
)

and the tiller client side can process the coded error like

resp, err := client.GetReleaseContent(ctx, req)
if err != nil {
    if s, ok := status.FromError(); ok {
        // check s.Code()
    }
}

this won't change the current tiller grpc api, but will return a coded error for client program to process.
I can open a pr to change the related tiller error into grpc status.Status error.
@technosophos  what do you think?

This would not require existing clients to change code at all, right?
If no changes are required for existing clients, I like this change.

Yes, this would not require existing clients to change code.

For helm cmd, the existing clients would not need to change, since the current tiller grpc api return a normal golang error, and the grpc.Status satisfy the Error interface can be used as a error.

For other developers, who may use tiller grpc api directly, I am not sure if they check the error like

resp, err := client.GetReleaseContent(ctx, req)
if err != nil && strings.HasPrefix(err.Error(), "invalid release name") {
    ...
}

for this kind of usage, the err.Error() is not stable by itself, I think there's no need to be compatible with this kind of usage.

As per @bacongobbler's comment in https://github.com/helm/helm/pull/2900#issuecomment-536683461, we are no longer adding new features to Helm 2, and Tiller is no longer present in Helm 3. Thank you for your issue; I am closing it at this time.


How to fix android error, when creating custom plugin❓

Question
I been working on an example app for android using this library, which will need some  native code for a frame processor plugin. I managed to make everything work with a community plugin (https://github.com/rodgomesc/vision-camera-face-detector), but now when I'm trying to create my own plugin, following the tutorial in the docs for kotlin (https://mrousavy.com/react-native-vision-camera/docs/guides/frame-processors-plugins-android) I get this error:

`

Task :app:compileDebugJavaWithJavac FAILED

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.3.3/userguide/command_line_interface.html#sec:command_line_warnings
86 actionable tasks: 80 executed, 6 up-to-date
Warning: This version only understands SDK XML versions up to 2 but an SDK XML file of version 3 was encountered. This can happen if you use versions of Android Studio and the command-line tools that were released at different times.
Warning: unexpected element (uri:"", local:"base-extension"). Expected elements are <{}codename>,<{}layoutlib>,<{}api-level>
/<BASE_DIR>/RNCamera0/android/app/src/main/java/com/rncamera0/MainApplication.java:31: error: cannot find symbol
packages.add(new QRCodeFrameProcessorPluginPackage());
^
symbol: class QRCodeFrameProcessorPluginPackage
Note: /<BASE_DIR>/RNCamera0/android/app/src/debug/java/com/rncamera0/ReactNativeFlipper.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
1 error
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.

Compilation failed; see the compiler error output for details.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 54s
error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup.
Error: Command failed: ./gradlew app:installDebug -PreactNativeDevServerPort=8081
Warning: This version only understands SDK XML versions up to 2 but an SDK XML file of version 3 was encountered. This can happen if you use versions of Android Studio and the command-line tools that were released at different times.
Warning: unexpected element (uri:"", local:"base-extension"). Expected elements are <{}codename>,<{}layoutlib>,<{}api-level>
/<BASE_DIR>/RNCamera0/android/app/src/main/java/com/rncamera0/MainApplication.java:31: error: cannot find symbol
packages.add(new QRCodeFrameProcessorPluginPackage());
^
symbol: class QRCodeFrameProcessorPluginPackage
Note: /<BASE_DIR>/RNCamera0/android/app/src/debug/java/com/rncamera0/ReactNativeFlipper.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
1 error
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.

Compilation failed; see the compiler error output for details.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 54s
at makeError (/<BASE_DIR>/RNCamera0/node_modules/execa/index.js:174:9)
at /<BASE_DIR>/RNCamera0/node_modules/execa/index.js:278:16
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async runOnAllDevices (/<BASE_DIR>/RNCamera0/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/runOnAllDevices.js:109:5)
at async Command.handleAction (/<BASE_DIR>/RNCamera0/node_modules/@react-native-community/cli/build/index.js:192:9)

info Run CLI with --verbose flag for more details.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
`
(THIS IS THE END OF THE ERROR)

The only thing I did following the basic example I'm not sure about is, I wrote the files for the plugin and the package in the same folder as MainActivity.java, is that okay? Also I didn't have the option to directly create a java or kotlin file, I had to click new scratch file to create both of them. (See image) I don't know if that could be related to the fact that the directory isn't mark in any specific way such as module or resources root.
Disclaimer: it's my first time interacting with android native code, so it could be something really basic, I apologize in advance if that's the case.

.
Thanks for reading and for any help any of you could give me!
What I tried
I tried following the tutorial a few times, first customizing some stuff, but then following every part including the names of the plugins and packages.
I tried I few things searching for this part of the error:
error: cannot find symbol           packages.add(new QRCodeFrameProcessorPluginPackage());
But nothing worked.
VisionCamera Version
2.13.5
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar questions in the issues page as well as in the discussions page and found none.

the documentation and tutorials are assuming that you're installing a packaged plugin from outside your project.
when you write your own local plugin, first need to declare it in android/settings.gradle and then add as a dependency to android/app/build.gradle.
first start by creating a directory located at /android/app/src/main/java/com/rncamera0/qrcodeframeprocessor
inside that directory add your custom frame processor files:
/android/app/src/main/java/com/rncamera0/qrcodeframeprocessor/QRCodeFrameProcessorPlugin.kt
/android/app/src/main/java/com/rncamera0/qrcodeframeprocessor/QRCodeFrameProcessorPluginPackage.kt
the top line of both of those files should read:
package com.rncamera0.qrcodeframeprocessor
in your /android/app/main/java/com/rncamera0/MainApplication.java file, import the package:
import com.rncamera0.qrcodeframeprocessor.QRCodeFrameProcessorPluginPackage
add it inside the getPackages() block:
@Override
        protected List<ReactPackage> getPackages() {
          @SuppressWarnings("UnnecessaryLocalVariable")
          List<ReactPackage> packages = new PackageList(this).getPackages();
          // Packages that cannot be autolinked yet can be added manually here, for example:
          // packages.add(new MyReactNativePackage());
          packages.add(new QRCodeFrameProcessorPluginPackage());  // <-- ADD THIS LINE
          return packages;
        }

in your /android/settings.gradle add these two lines after include ':app':
...
include ':app'

include ":qrcodeframeprocessor" // <-- ADD THIS LINE
project(":qrcodeframeprocessor").projectDir = new File(rootProject.projectDir, '/app/src/main/java/com/rncamera0/qrcodeframeprocessor') // <-- ADD THIS LINE

in your /android/app/build.gradle add this line to dependencies block:
dependencies {
   ... // other dependencies
  implementation project(':qrcodeframeprocessor') // <-- ADD THIS LINE
}

the documentation and tutorials are assuming that you're installing a packaged plugin from outside your project.

That makes sense, actually that was the alternative I was trying while I couldn't solve this, since I knew it worked with the community plugins.
I did what you wrote above and for the first time in more than a week I got a different error while building:
error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup.
Error: Command failed: ./gradlew app:installDebug -PreactNativeDevServerPort=8081

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':app:mergeDebugAssets'.
> Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'.
   > Could not resolve project :qrcodeframeprocessor.
     Required by:
         project :app
      > No matching configuration of project :qrcodeframeprocessor was found. The consumer was configured
      to find a runtime of a component, preferably optimized for Android, as well as attribute
      'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' but:
          - None of the consumable configurations have attributes.

I found a few similar errors online that were solved by adding missingDimensionStrategy 'react-native-camera', 'general' or missingDimensionStrategy 'store', 'play' in the defaultConfig of android/app/build.gradle, so I tried that, and also missingDimensionStrategy 'qrcodeframeprocessor', 'general', but none of that worked. So I will be trying to fix this new error.
@skam22 Thanks you so much for the help! And if you have any further recommendation I will be happy to read them.

Did you try to use the template for a new RN library? That's how the QR Code plugin was made

since you're using kotlin files (.kt) don't forget to have this line towards the top of your android/app/build.gradle
apply plugin: "kotlin-android"

that could be the missing link for you since you're using a .kt frame processor.  Unless you specifically tell the compiler to include kotlin files it's not going to be able to find the class declaration.

@mrousavy don't worry! Regarding to this issue, no, I didn't use any template, since I was trying implement the plugin for the frame processor inside the same project code.
However, I was working on creating an external package that could fulfill my needs (in parallel/another branch), which I did with bob, but it didn't work for me (my IDE didn't even recognize the example function). Is that (bob) what you mean when talking about the template? If that's not the case, were could I find the template?
Anyway for the moment I'm testing some basic functionalities with some code I forked from a community library that already included kotlin (vision-camer-ocr), so I'm just editing its code, but I know that's not the best long term solution.
@skam22 I actually tried that before, but for some reason now the build process worked, probably because I changed some other configs in build.gradle files thanks to you and other person in reddit. Nevertheless, now the Camera preview is black (before it was wroking fine), so I will be trying to check which change make it stop working, and I hope that wasn't necessary to make it build.
Thanks again for all the help!

@mrousavy building a plugin is such a painful process, I think this is important to invest some time at to make it a bit easier

I think this is important to invest some time at to make it a bit easier

Sure, I think it is important to invest some money so I can work on this! :)

If I remember correctly I think I did not solve it.
On Sun, 26 Mar 2023 at 5:11 PM michealChin @.***> wrote:

May I know are you manage to solve the problem? I have the exact same
problem as you when trying to implement the plugin for the frame processor
inside the same project code.
—
Reply to this email directly, view it on GitHub
https://github.com/mrousavy/react-native-vision-camera/issues/1124#issuecomment-1484126237,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHLS26HOK4ZJI443ITWWTDTW6BMBNANCNFSM523GBTYQ
.
You are receiving this because you commented.Message ID:
@.***>

Yes - the process I laid out above is how we’re using a locally defined frame processor.

What went wrong:
Could not determine the dependencies of task ':app:mergeDebugAssets'.

Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'.
Could not resolve project :qrcodeframeprocessor.
Required by:
project :app
No matching configuration of project :qrcodeframeprocessor was found. The consumer was configured
to find a runtime of a component, preferably optimized for Android, as well as attribute
'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' but:
- None of the consumable configurations have attributes.

I follow exactly like what you say to update the android/settings.gradle and then add as a dependency to android/app/build.gradle but I encounter below error message.

What went wrong:
Could not determine the dependencies of task ':app:mergeDebugAssets'.

Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'.
Could not resolve project :qrcodeframeprocessor.
Required by:
project :app
No matching configuration of project :qrcodeframeprocessor was found. The consumer was configured
to find a runtime of a component, preferably optimized for Android, as well as attribute
'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' but:
- None of the consumable configurations have attributes.

I then trying to follow the sample code from "https://github.com/mrousavy/Colorwaver", which is using a locally defined frame processor but he didn't do what you have suggested but also end up with the same error message. I have been struggling for this for a weeks, searching for the answer in stackoverflow and this forum, some time I think maybe migrating to flutter will be a good choice, however I want to give a one last chance before making such decision.

I don’t think that’s a good decision as every framework has its own pros
and cons. Being struggling for weeks doesn’t mean that rn very poor however
you can try to reach to the owner and ask for guidelines to solve the
problem
On Sun, 26 Mar 2023 at 6:08 PM michealChin @.***> wrote:

What went wrong:
Could not determine the dependencies of task ':app:mergeDebugAssets'.

Could not resolve all task dependencies for configuration
':app:debugRuntimeClasspath'.
Could not resolve project :qrcodeframeprocessor.
Required by:
project :app

No matching configuration of project :qrcodeframeprocessor was found.
The consumer was configured
to find a runtime of a component, preferably optimized for Android, as
well as attribute
'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' but:

None of the consumable configurations have attributes.

I follow exactly like what you say to update the android/settings.gradle
and then add as a dependency to android/app/build.gradle but I encounter
below error message.

What went wrong:
Could not determine the dependencies of task ':app:mergeDebugAssets'.

Could not resolve all task dependencies for configuration
':app:debugRuntimeClasspath'.
Could not resolve project :qrcodeframeprocessor.
Required by:
project :app

No matching configuration of project :qrcodeframeprocessor was found.
The consumer was configured
to find a runtime of a component, preferably optimized for Android, as
well as attribute
'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' but:

None of the consumable configurations have attributes.

I then trying to follow the sample code from "
https://github.com/mrousavy/Colorwaver", which is using a locally defined
frame processor but he didn't do what you have suggested but also end up
with the same error message. I have been struggling for this for a weeks,
searching for the answer in stackoverflow and this forum, some time I think
maybe migrating to flutter will be a good choice, however I want to give a
one last chance before making such decision.
—
Reply to this email directly, view it on GitHub
https://github.com/mrousavy/react-native-vision-camera/issues/1124#issuecomment-1484144773,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHLS26FFLP3V4T6U2UVZJDTW6BSWRANCNFSM523GBTYQ
.
You are receiving this because you commented.Message ID:
@.***>

Closing as this is a stale issue - this might have been fixed with the full rewrite in VisionCamera V3 (🥳) - if not, please create a new issue.

Hey!
JFYI; VisionCamera V3 now includes a QR/Barcode Scanner! 😍  Check out the CodeScanner Documentation 🚀
Try upgrading to V3 if you can, it has a much more stable yet flexible foundation.
If you appreciate me dedicating my free time to improving VisionCamera and implementing features like the Code Scanner, please consider sponsoring me on GitHub 💖 to show your support.


Warn about no-metadata

The git svn clone commands use --no-metadata without explaining it. That's not technically wrong, and the article title does start with "Migrate", but I feel there should be a warning of the consequences.
--no-metadata (permanently) removes the ability to reconstruct the original SVN revisions, meaning:

stuff like docs, issues, etc. that point to those revisions can no longer as easily be referred to
some git svn commands are limited afterwards

The docs recommend against it:

This option is NOT recommended as it makes it difficult to track down old references to SVN revision numbers in existing documentation, bug reports, and archives. If you plan to eventually migrate from SVN to Git and are certain about dropping SVN history, consider git-filter-repo instead.

So, I would suggest there should at least be some kind of warning panel about this.

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

ID: edd6cbc8-5e3b-c3a1-4672-d42510cc058b
Version Independent ID: 8fe81fb5-7c2d-2562-5659-55fccbb3126c
Content: Migrate from Subversion (SVN) to Git - Azure Repos
Content Source: docs/repos/git/perform-migration-from-svn-to-git.md
Product: devops
Technology: devops-code-git
GitHub Login: @vtbassmatt
Microsoft Alias: macoope

@chucker Thank you for the feedback.
This issue has previously been reported under https://github.com/MicrosoftDocs/azure-devops-docs/issues/5132.
Please refer there for further updates regarding changes to the documentation.


Automated cherry pick of #10922: fix(keystone): tag list for keystone service

Cherry pick of #10922 on release/3.7.
#10922: fix(keystone): tag list for keystone service

Codecov Report

Merging #10923 (962e19b) into release/3.7 (0ff3997) will increase coverage by 5.20%.
The diff coverage is 0.00%.

@@               Coverage Diff                @@
##           release/3.7   #10923       +/-   ##
================================================
+ Coverage         5.98%   11.19%    +5.20%
================================================
  Files              848      147      -701
  Lines           131795    16921   -114874
================================================
- Hits              7887     1894     -5993
+ Misses          123206    14834   -108372
+ Partials           702      193      -509

Flag
Coverage Δ

aFlag
11.19% <0.00%> (+5.20%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/apis/const.go
0.00% <0.00%> (ø)

pkg/apis/input.go
0.00% <ø> (ø)

pkg/apis/list.go
0.00% <ø> (ø)

pkg/baremetal/tasks/baseprepare.go
0.00% <0.00%> (ø)

pkg/baremetal/tasks/bm_register.go
0.00% <0.00%> (ø)

pkg/baremetal/tasks/ipmiprobe.go
0.00% <0.00%> (ø)

pkg/baremetal/tasks/stop.go
0.00% <0.00%> (ø)

pkg/cloudcommon/validators/validators.go
62.39% <0.00%> (-0.69%)
:arrow_down:

pkg/monitor/alerting/conditions/reducer.go
77.27% <0.00%> (-13.94%)
:arrow_down:

pkg/util/imagetools/imagetools.go
40.50% <0.00%> (-2.74%)
:arrow_down:

... and 717 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ef9a9b2...962e19b. Read the comment docs.


README file installation instructions update

Version Reports:
Terraform v0.11.3
terraform-provider-libvirt-0.0.0+git20180220.f2cef405-1.1.x86_64
libvirt-3.3.0-4.28.x86_64
Now, according to the terraform documentation, this is the procedure to install :
https://www.terraform.io/docs/configuration/providers.html#third-party-plugins
On all other systems, in the sub-path .terraform.d/plugins in your user's home directory.
terraform init will search this directory for additional plugins during plugin initialization.
The naming scheme for provider plugins is terraform-provider-NAME_vX.Y.Z, and Terraform uses the name to understand the name and version of a particular provider binary.

I think the old system still works (doing a go install as described in our installation instructions), but I agree it would be a good idea to update the README and explain how to install it using this new mechanism...

@markostanojlovic  feel free to spend a PR for this :+1:


Ov feature/feature fixes

Tickets fixed:
https://trello.com/c/kY4Akwzi/93-make-an-indicator-in-the-player-invitations-if-player-has-already-joined-the-tournament
https://trello.com/c/i18N8iJT/92-show-the-password-to-invited-players-automatically-in-the-invite
https://trello.com/c/J5F1ZfdT/76-design-suggestion-for-ongoing-and-competed-round-robin-tournament-matches-section
https://trello.com/c/MFHnC0xH/84-ability-to-change-tournament-password
https://trello.com/c/XMd3ySAg/85-ability-to-remove-the-tournament-password
https://trello.com/c/KJOZNXa2/106-add-invitations-tabs-to-the-profile-navbar-dropdown
https://trello.com/c/4JRKqMUo/121-tabs-rendering-too-late-to-dropdown-mode-in-smaller-screens
https://trello.com/c/m1hx8xMn/122-tabs-not-rendering-to-dropdown-in-smaller-screens
https://trello.com/c/3N3D3R1B/118-showpassword-for-tournament-passkey-in-tournament-creation
https://trello.com/c/Q9Emchti/123-make-tabs-smaller
https://trello.com/c/NAyNrdYD/120-navbar-rendering-wrongly-in-smaller-screens
https://trello.com/c/WsPnenOn/124-tabs-are-not-scrollable
https://trello.com/c/DdmtetEN/125-phone-navigation-drawer
https://trello.com/c/1ZYxKQtj/126-create-tournament-button-problems
https://trello.com/c/Alb4WEoT/104-in-profile-info-section-anything-can-be-inputted-to-the-country-box
https://trello.com/c/kHZ3s8fZ/116-create-tournament-button-text-overlap-in-created-tournaments
https://trello.com/c/J9Nd3uOI/115-tournament-invitation-text-overlap

Great effort 💯


Bug: GitHub login prompt closes instantly

Description
Hello!
When I attempt to login with github, it ususally closes the settings modal and does nothing, but I have discovered that it is actually just flashing the login modal really fast then closing it.
Steps To Reproduce

Download and install
Attempt to login to github
Sad.

Requirements

Be able to login to github
Modal stays open
More logs

Files Version
<IP_ADDRESS>
Windows Version
10.0.22631.3085
Log File
debug.log

Thanks for the report, I've added this to the project board. Also how are you attempting to log in to GitHub?

Thanks for the report; I've added this to the project board. Also, how are you attempting to log in to GitHub?

This button is in settings.
I think it has something to do with the settings, as I have imported the settings from a device I barely got it working on, and it worked on the first try. So there is something conflicting in there.

This issue is fixed in our dev branch and will be included in the next release. In the meantime, trying to push to a Git repo will display a prompt to login so you won't miss any functionality.


added click action to iimage

Thank you for doing this. I will test it out as soon as I can.
If I can ever help you or Semabit out by adding or changing something with this slideshow (within reason of course) please let me know!

Any reason for not merging this. I would really like to use the click function to switch to fullscreen slideshow.

@jaysaikia I've been putting it off. Available in v1.2.3

Thanks man. Like the component. 👍
On Mon, Jul 9, 2018 at 2:56 AM Richard Jeffords<EMAIL_ADDRESS>wrote:

@jaysaikia https://github.com/jaysaikia I've been putting it off.
Available in v1.2.3
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dockleryxk/ng-simple-slideshow/pull/23#issuecomment-403300990,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGfzMhCkVEZDs44ZxF7kbVKanPqv4cjdks5uEjm-gaJpZM4UN-eg
.


GitHub Repository

[ ] Plan out Readme

[ ] "Code Structure"
[ ] How to use?
[x] git-badges?
[ ] contributers Bot?
[ ] ??

[ ] Templates

[x] Issue
[ ] PR

[ ] dev branch

Hey, i would love to contribute to your project, do let me know if you are interested.


Error on V14

Thank you for the amazing script to easy install.
I tried it for v14 and it errors out when doing bench restart.
bench restart
$ supervisorctl restart frappe-bench-web:
frappe-bench-web:frappe-bench-frappe-web: stopped
frappe-bench-web:frappe-bench-node-socketio: stopped
frappe-bench-web:frappe-bench-frappe-web: ERROR (spawn error)
frappe-bench-web:frappe-bench-node-socketio: started
ERROR: supervisorctl restart frappe-bench-web:
subprocess.CalledProcessError: Command 'supervisorctl restart frappe-bench-web:' returned non-zero exit status 7.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/frappev14/.local/bin/bench", line 8, in <module>
    sys.exit(cli())
  File "/home/frappev14/.local/lib/python3.10/site-packages/bench/cli.py", line 132, in cli
    bench_command()
  File "/home/frappev14/.local/lib/python3.10/site-packages/bench/commands/utils.py", line 41, in restart
    Bench(".").reload(web, supervisor, systemd)
  File "/home/frappev14/.local/lib/python3.10/site-packages/bench/utils/render.py", line 126, in wrapper_fn
    return fn(*args, **kwargs)
  File "/home/frappev14/.local/lib/python3.10/site-packages/bench/bench.py", line 152, in reload
    restart_supervisor_processes(bench_path=self.name, web_workers=web, _raise=_raise)
  File "/home/frappev14/.local/lib/python3.10/site-packages/bench/utils/bench.py", line 342, in restart_supervisor_processes
    failure = bench.run(f"{sudo}supervisorctl restart {group}", _raise=_raise)
  File "/home/frappev14/.local/lib/python3.10/site-packages/bench/bench.py", line 48, in run
    return exec_cmd(cmd, cwd=cwd or self.cwd, _raise=_raise)
  File "/home/frappev14/.local/lib/python3.10/site-packages/bench/utils/__init__.py", line 169, in exec_cmd
    raise CommandFailedError(cmd) from subprocess.CalledProcessError(return_code, cmd)
bench.exceptions.CommandFailedError: supervisorctl restart frappe-bench-web:

This does not get resolved even when I do almost everything mentioned on forum.
23  git clone https://github.com/flexcomng/erpnext_quick_install.git
   24  cd erpnext_quick_install/
   25  sudo chmod +x erpnext_install.sh
   26  source erpnext_install.sh
   27  bench setup socketio
   28  bench setup supervisor
   29  bench setup redis
   30  sudo supervisorctl reload
   31  bench restart
   32  sudo bench restart
   33  sudo reboot now
   34  cd frappe-bench/
   35  sudo service supervisor stop
   36  sudo service supervisor start
   37  bench restart
   38  bench start
   39  sudo ln -s `pwd`/config/supervisor.conf /etc/supervisor/conf.d/frappe-bench.conf
   40  bench setup supervisor
   41  sudo vim /etc/supervisor/supervisord.conf
   42  sudo bench setup production frappev14
   43  sudo supervisorctl restart all
   44  bench restart
   45  python --version
   46  python -V
   47  python --V
   48  python
   49  python3
   50  ls -la env/bin/python3
   51  sudo apt purge python3.12
   52  killall -9 node
   53  supervisorctl restart all
   54  bench restart
   55  bench doctor
   56  bench update --requirements
   57  bench setup redis
   58  bench setup socketio
   59  bench retry-upgrade
   60  sudo service nginx restart
   61  sudo supervisorctl reload
   62  bench restart
   63  sudo bench setup production frappev14
   64  bench restart
   65  bench setup socketio
   66  bench setup supervisor
   67  bench setup redis
   68  sudo supervisorctl reload
   69  sudo systemctl enable socketio --now
   70  sudo systemctl enable sockeio --now
   71  sudo systemctl start socketio --now
   72  sudo systemctl status *
   73  sudo systemctl status supervisor
   74  sudo systemctl start supervisor  --now
   75  sudo systemctl restart supervisor  --now
   76  bench restart
   77  sudo supervisorctl restart all
   78  sudo systemctl status redis
   79  sudo systemctl restart redis --now
   80  sudo systemctl restart socketio --now
   81  sudo systemctl restart supervisorctl --now
   82  sudo systemctl restart supervisor --now
   83  bench restart --web --supervisor
   84  sudo nano /etc/supervisor/supervisord.conf
   85  bench setup supervisor
   86  sudo ln -s `pwd`/config/supervisor.conf /etc/supervisor/conf.d/frappe-bench.conf
   87  sudo rm -rf /etc/supervisor/conf.d/frappe-bench.conf
   88  sudo ln -s `pwd`/config/supervisor.conf /etc/supervisor/conf.d/frappe-bench.conf
   89  sudo service supervisorctl reload
   90  sudo service supervisor reload
   91  bench restart

Whole command list history attached above.  I will try to search more and if I find a solution then I will share it here and on forum.
UDPATE: Found the issue. It was cpu instruction causing core dump.
19:50:14 web.1         | Illegal instruction (core dumped)

Yes i reported already that its the cpu issue over proxmox when avx/avx2 is not active.
Also posted in forum.
Will close this issue but will make pr to update readme to add this as documentation for such issue.


Add support for SQL query caching

TODO

[ ] Rename QueryCacher to something better.
[ ] Add documentation tutorial for using this functionality.

Codecov Report

Merging #51 (b7c72ec) into main (164ebed) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              main       #51    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files            7         8     +1
  Lines          956      1083   +127
  Branches       224       241    +17
==========================================
+ Hits           956      1083   +127

Impacted Files
Coverage Δ

src/patito/validators.py
100.00% <ø> (ø)

src/patito/__init__.py
100.00% <100.00%> (ø)

src/patito/caching.py
100.00% <100.00%> (ø)

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


fix(DocsCrawler): Add response.ok check and improve link splitting

Description

Added skip for 404 errors in the page parsing logic
Resolved incorrect handling of relative URLs in link splitting

Checklist

[x] The base branch of this PR is dev, rather than main
[x] The relevant docs, if any, have been updated or created

Screenshots

Testing
I checked several documentation sources for libraries for Python, one of them

Closes #2448


Edit User Guide to fix documentation for some commands

Fixes #190, #193.

Codecov Report

Merging #202 (698e33d) into master (51aaa7d) will decrease coverage by 2.22%.
The diff coverage is 0.00%.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 51aaa7d...698e33d. Read the comment docs.


Additional compiler flags maybe needed

Hi,
thank you for your efforts and sharing your code.
In order to compile the tests i had to add two additional compiler flags: -lstdc++ and -lm
CXX_FLAGS 	:= -ansi -pedantic -Werror -Wall -O3 -std=c++17 -fext-numeric-literals -flto -lffts -L$(CURDIR)/../lib -lpitch_detection -I$(CURDIR)/../include -Wl,-R$(CURDIR)/../lib -fopenmp -larmadillo -lmlpack -lstdc++ -lm

The missing -lstdc++ flag caused the following error:
/usr/bin/ld: /tmp/test.0Oc2eo.ltrans0.ltrans.o: undefined reference to symbol '_ZTVN10__cxxabiv121__vmi_class_type_infoE@@CXXABI_1.3'
//usr/lib/x86_64-linux-gnu/libstdc++.so.6: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
Makefile:8: recipe for target 'test' failed
make: *** [test] Error 1

The missing -lm flag caused the following error:
/usr/bin/ld: /tmp/test.Vf3wcq.ltrans0.ltrans.o: undefined reference to symbol 'roundf@@GLIBC_2.2.5'
//lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
Makefile:8: recipe for target 'test' failed

My knowledge of C++ is very limited and i think there's a great probability that these issues are toolchain dependent. In any case this may be helpful to some other ppl trying to compile the tests.
Running the test gives me the following console output. Which leads to the question: are failing tests expected?
Running main() from gtest_main.cc
[==========] Running 76 tests from 13 test cases.
[----------] Global test environment set-up.
[----------] 1 test from MpmSinewaveTestManualAlloc
[ RUN      ] MpmSinewaveTestManualAlloc.OneAllocMultipleFreq
[       OK ] MpmSinewaveTestManualAlloc.OneAllocMultipleFreq (7 ms)
[----------] 1 test from MpmSinewaveTestManualAlloc (7 ms total)

[----------] 1 test from YinSinewaveTestManualAlloc
[ RUN      ] YinSinewaveTestManualAlloc.OneAllocMultipleFreq
[       OK ] YinSinewaveTestManualAlloc.OneAllocMultipleFreq (5 ms)
[----------] 1 test from YinSinewaveTestManualAlloc (5 ms total)

[----------] 5 tests from YinInstrumentTest
[ RUN      ] YinInstrumentTest.Violin_A4_44100
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
[  FAILED  ] YinInstrumentTest.Violin_A4_44100 (20 ms)
[ RUN      ] YinInstrumentTest.Piano_B4_44100
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
[  FAILED  ] YinInstrumentTest.Piano_B4_44100 (10 ms)
[ RUN      ] YinInstrumentTest.Piano_D4_44100
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
[  FAILED  ] YinInstrumentTest.Piano_D4_44100 (1 ms)
[ RUN      ] YinInstrumentTest.Acoustic_E2_44100
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
[  FAILED  ] YinInstrumentTest.Acoustic_E2_44100 (0 ms)
[ RUN      ] YinInstrumentTest.Classical_FSharp4_48000
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
[  FAILED  ] YinInstrumentTest.Classical_FSharp4_48000 (0 ms)
[----------] 5 tests from YinInstrumentTest (31 ms total)

[----------] 5 tests from MpmInstrumentTest
[ RUN      ] MpmInstrumentTest.Violin_A4_44100
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
[  FAILED  ] MpmInstrumentTest.Violin_A4_44100 (1 ms)
[ RUN      ] MpmInstrumentTest.Piano_B4_44100
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
[  FAILED  ] MpmInstrumentTest.Piano_B4_44100 (0 ms)
[ RUN      ] MpmInstrumentTest.Piano_D4_44100
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
[  FAILED  ] MpmInstrumentTest.Piano_D4_44100 (0 ms)
[ RUN      ] MpmInstrumentTest.Acoustic_E2_44100
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
[  FAILED  ] MpmInstrumentTest.Acoustic_E2_44100 (0 ms)
[ RUN      ] MpmInstrumentTest.Classical_FSharp4_48000
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
[  FAILED  ] MpmInstrumentTest.Classical_FSharp4_48000 (0 ms)
[----------] 5 tests from MpmInstrumentTest (1 ms total)

[----------] 5 tests from PYinInstrumentTest
[ RUN      ] PYinInstrumentTest.Violin_A4_44100
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
[  FAILED  ] PYinInstrumentTest.Violin_A4_44100 (0 ms)
[ RUN      ] PYinInstrumentTest.Piano_B4_44100
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
[  FAILED  ] PYinInstrumentTest.Piano_B4_44100 (0 ms)
[ RUN      ] PYinInstrumentTest.Piano_D4_44100
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
[  FAILED  ] PYinInstrumentTest.Piano_D4_44100 (0 ms)
[ RUN      ] PYinInstrumentTest.Acoustic_E2_44100
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
[  FAILED  ] PYinInstrumentTest.Acoustic_E2_44100 (0 ms)
[ RUN      ] PYinInstrumentTest.Classical_FSharp4_48000
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
[  FAILED  ] PYinInstrumentTest.Classical_FSharp4_48000 (0 ms)
[----------] 5 tests from PYinInstrumentTest (0 ms total)

[----------] 5 tests from PMpmInstrumentTest
[ RUN      ] PMpmInstrumentTest.Violin_A4_44100
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
[  FAILED  ] PMpmInstrumentTest.Violin_A4_44100 (0 ms)
[ RUN      ] PMpmInstrumentTest.Piano_B4_44100
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
[  FAILED  ] PMpmInstrumentTest.Piano_B4_44100 (0 ms)
[ RUN      ] PMpmInstrumentTest.Piano_D4_44100
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
[  FAILED  ] PMpmInstrumentTest.Piano_D4_44100 (0 ms)
[ RUN      ] PMpmInstrumentTest.Acoustic_E2_44100
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
[  FAILED  ] PMpmInstrumentTest.Acoustic_E2_44100 (0 ms)
[ RUN      ] PMpmInstrumentTest.Classical_FSharp4_48000
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
[  FAILED  ] PMpmInstrumentTest.Classical_FSharp4_48000 (0 ms)
[----------] 5 tests from PMpmInstrumentTest (0 ms total)

[----------] 4 tests from MpmEdgeCase
[ RUN      ] MpmEdgeCase.EmptyData
[       OK ] MpmEdgeCase.EmptyData (0 ms)
[ RUN      ] MpmEdgeCase.SmallData
[       OK ] MpmEdgeCase.SmallData (2 ms)
[ RUN      ] MpmEdgeCase.InvalidAlloc
./test_edge_cases.cpp:18: Failure
Expected: pitch_alloc::Mpm<double> ma(-1) throws an exception of type std::bad_alloc.
  Actual: it throws a different type.
[  FAILED  ] MpmEdgeCase.InvalidAlloc (14 ms)
[ RUN      ] MpmEdgeCase.EmptyAlloc
[       OK ] MpmEdgeCase.EmptyAlloc (0 ms)
[----------] 4 tests from MpmEdgeCase (16 ms total)

[----------] 5 tests from YinEdgeCase
[ RUN      ] YinEdgeCase.EmptyData
[       OK ] YinEdgeCase.EmptyData (0 ms)
[ RUN      ] YinEdgeCase.TooSmallData
[       OK ] YinEdgeCase.TooSmallData (1 ms)
[ RUN      ] YinEdgeCase.SmallData
[       OK ] YinEdgeCase.SmallData (0 ms)
[ RUN      ] YinEdgeCase.InvalidAlloc
./test_edge_cases.cpp:45: Failure
Expected: pitch_alloc::Yin<double> ya(-1) throws an exception of type std::bad_alloc.
  Actual: it throws a different type.
[  FAILED  ] YinEdgeCase.InvalidAlloc (0 ms)
[ RUN      ] YinEdgeCase.EmptyAlloc
[       OK ] YinEdgeCase.EmptyAlloc (0 ms)
[----------] 5 tests from YinEdgeCase (1 ms total)

[----------] 7 tests from PYinSinewave/PYinSinewaveTest
[ RUN      ] PYinSinewave/PYinSinewaveTest.GetFreqManualAlloc/0
[       OK ] PYinSinewave/PYinSinewaveTest.GetFreqManualAlloc/0 (15 ms)
[ RUN      ] PYinSinewave/PYinSinewaveTest.GetFreqManualAlloc/1
[       OK ] PYinSinewave/PYinSinewaveTest.GetFreqManualAlloc/1 (15 ms)
[ RUN      ] PYinSinewave/PYinSinewaveTest.GetFreqManualAlloc/2
[       OK ] PYinSinewave/PYinSinewaveTest.GetFreqManualAlloc/2 (13 ms)
[ RUN      ] PYinSinewave/PYinSinewaveTest.GetFreqManualAlloc/3
[       OK ] PYinSinewave/PYinSinewaveTest.GetFreqManualAlloc/3 (17 ms)
[ RUN      ] PYinSinewave/PYinSinewaveTest.GetFreqManualAlloc/4
[       OK ] PYinSinewave/PYinSinewaveTest.GetFreqManualAlloc/4 (15 ms)
[ RUN      ] PYinSinewave/PYinSinewaveTest.GetFreqManualAlloc/5
[       OK ] PYinSinewave/PYinSinewaveTest.GetFreqManualAlloc/5 (19 ms)
[ RUN      ] PYinSinewave/PYinSinewaveTest.GetFreqManualAlloc/6
[       OK ] PYinSinewave/PYinSinewaveTest.GetFreqManualAlloc/6 (16 ms)
[----------] 7 tests from PYinSinewave/PYinSinewaveTest (111 ms total)

[----------] 6 tests from PMpmSinewave/PMpmSinewaveTest
[ RUN      ] PMpmSinewave/PMpmSinewaveTest.GetFreqManualAlloc/0
[       OK ] PMpmSinewave/PMpmSinewaveTest.GetFreqManualAlloc/0 (6 ms)
[ RUN      ] PMpmSinewave/PMpmSinewaveTest.GetFreqManualAlloc/1
[       OK ] PMpmSinewave/PMpmSinewaveTest.GetFreqManualAlloc/1 (5 ms)
[ RUN      ] PMpmSinewave/PMpmSinewaveTest.GetFreqManualAlloc/2
[       OK ] PMpmSinewave/PMpmSinewaveTest.GetFreqManualAlloc/2 (5 ms)
[ RUN      ] PMpmSinewave/PMpmSinewaveTest.GetFreqManualAlloc/3
[       OK ] PMpmSinewave/PMpmSinewaveTest.GetFreqManualAlloc/3 (5 ms)
[ RUN      ] PMpmSinewave/PMpmSinewaveTest.GetFreqManualAlloc/4
[       OK ] PMpmSinewave/PMpmSinewaveTest.GetFreqManualAlloc/4 (6 ms)
[ RUN      ] PMpmSinewave/PMpmSinewaveTest.GetFreqManualAlloc/5
[       OK ] PMpmSinewave/PMpmSinewaveTest.GetFreqManualAlloc/5 (9 ms)
[----------] 6 tests from PMpmSinewave/PMpmSinewaveTest (36 ms total)

[----------] 12 tests from MpmSinewave/MpmSinewaveTest
[ RUN      ] MpmSinewave/MpmSinewaveTest.GetFreq/0
[       OK ] MpmSinewave/MpmSinewaveTest.GetFreq/0 (4 ms)
[ RUN      ] MpmSinewave/MpmSinewaveTest.GetFreq/1
[       OK ] MpmSinewave/MpmSinewaveTest.GetFreq/1 (3 ms)
[ RUN      ] MpmSinewave/MpmSinewaveTest.GetFreq/2
[       OK ] MpmSinewave/MpmSinewaveTest.GetFreq/2 (3 ms)
[ RUN      ] MpmSinewave/MpmSinewaveTest.GetFreq/3
[       OK ] MpmSinewave/MpmSinewaveTest.GetFreq/3 (3 ms)
[ RUN      ] MpmSinewave/MpmSinewaveTest.GetFreq/4
[       OK ] MpmSinewave/MpmSinewaveTest.GetFreq/4 (4 ms)
[ RUN      ] MpmSinewave/MpmSinewaveTest.GetFreq/5
[       OK ] MpmSinewave/MpmSinewaveTest.GetFreq/5 (3 ms)
[ RUN      ] MpmSinewave/MpmSinewaveTest.GetFreqManualAlloc/0
[       OK ] MpmSinewave/MpmSinewaveTest.GetFreqManualAlloc/0 (4 ms)
[ RUN      ] MpmSinewave/MpmSinewaveTest.GetFreqManualAlloc/1
[       OK ] MpmSinewave/MpmSinewaveTest.GetFreqManualAlloc/1 (3 ms)
[ RUN      ] MpmSinewave/MpmSinewaveTest.GetFreqManualAlloc/2
[       OK ] MpmSinewave/MpmSinewaveTest.GetFreqManualAlloc/2 (4 ms)
[ RUN      ] MpmSinewave/MpmSinewaveTest.GetFreqManualAlloc/3
[       OK ] MpmSinewave/MpmSinewaveTest.GetFreqManualAlloc/3 (3 ms)
[ RUN      ] MpmSinewave/MpmSinewaveTest.GetFreqManualAlloc/4
[       OK ] MpmSinewave/MpmSinewaveTest.GetFreqManualAlloc/4 (4 ms)
[ RUN      ] MpmSinewave/MpmSinewaveTest.GetFreqManualAlloc/5
[       OK ] MpmSinewave/MpmSinewaveTest.GetFreqManualAlloc/5 (3 ms)
[----------] 12 tests from MpmSinewave/MpmSinewaveTest (42 ms total)

[----------] 6 tests from SwipeSinewave/SwipeSinewaveTest
[ RUN      ] SwipeSinewave/SwipeSinewaveTest.GetFreq/0
[       OK ] SwipeSinewave/SwipeSinewaveTest.GetFreq/0 (4 ms)
[ RUN      ] SwipeSinewave/SwipeSinewaveTest.GetFreq/1
[       OK ] SwipeSinewave/SwipeSinewaveTest.GetFreq/1 (4 ms)
[ RUN      ] SwipeSinewave/SwipeSinewaveTest.GetFreq/2
[       OK ] SwipeSinewave/SwipeSinewaveTest.GetFreq/2 (4 ms)
[ RUN      ] SwipeSinewave/SwipeSinewaveTest.GetFreq/3
[       OK ] SwipeSinewave/SwipeSinewaveTest.GetFreq/3 (3 ms)
[ RUN      ] SwipeSinewave/SwipeSinewaveTest.GetFreq/4
[       OK ] SwipeSinewave/SwipeSinewaveTest.GetFreq/4 (4 ms)
[ RUN      ] SwipeSinewave/SwipeSinewaveTest.GetFreq/5
[       OK ] SwipeSinewave/SwipeSinewaveTest.GetFreq/5 (5 ms)
[----------] 6 tests from SwipeSinewave/SwipeSinewaveTest (24 ms total)

[----------] 14 tests from YinSinewave/YinSinewaveTest
[ RUN      ] YinSinewave/YinSinewaveTest.GetFreq/0
[       OK ] YinSinewave/YinSinewaveTest.GetFreq/0 (4 ms)
[ RUN      ] YinSinewave/YinSinewaveTest.GetFreq/1
[       OK ] YinSinewave/YinSinewaveTest.GetFreq/1 (3 ms)
[ RUN      ] YinSinewave/YinSinewaveTest.GetFreq/2
[       OK ] YinSinewave/YinSinewaveTest.GetFreq/2 (4 ms)
[ RUN      ] YinSinewave/YinSinewaveTest.GetFreq/3
[       OK ] YinSinewave/YinSinewaveTest.GetFreq/3 (4 ms)
[ RUN      ] YinSinewave/YinSinewaveTest.GetFreq/4
[       OK ] YinSinewave/YinSinewaveTest.GetFreq/4 (4 ms)
[ RUN      ] YinSinewave/YinSinewaveTest.GetFreq/5
[       OK ] YinSinewave/YinSinewaveTest.GetFreq/5 (3 ms)
[ RUN      ] YinSinewave/YinSinewaveTest.GetFreq/6
[       OK ] YinSinewave/YinSinewaveTest.GetFreq/6 (3 ms)
[ RUN      ] YinSinewave/YinSinewaveTest.GetFreqManualAlloc/0
[       OK ] YinSinewave/YinSinewaveTest.GetFreqManualAlloc/0 (5 ms)
[ RUN      ] YinSinewave/YinSinewaveTest.GetFreqManualAlloc/1
[       OK ] YinSinewave/YinSinewaveTest.GetFreqManualAlloc/1 (4 ms)
[ RUN      ] YinSinewave/YinSinewaveTest.GetFreqManualAlloc/2
[       OK ] YinSinewave/YinSinewaveTest.GetFreqManualAlloc/2 (4 ms)
[ RUN      ] YinSinewave/YinSinewaveTest.GetFreqManualAlloc/3
[       OK ] YinSinewave/YinSinewaveTest.GetFreqManualAlloc/3 (4 ms)
[ RUN      ] YinSinewave/YinSinewaveTest.GetFreqManualAlloc/4
[       OK ] YinSinewave/YinSinewaveTest.GetFreqManualAlloc/4 (4 ms)
[ RUN      ] YinSinewave/YinSinewaveTest.GetFreqManualAlloc/5
[       OK ] YinSinewave/YinSinewaveTest.GetFreqManualAlloc/5 (3 ms)
[ RUN      ] YinSinewave/YinSinewaveTest.GetFreqManualAlloc/6
[       OK ] YinSinewave/YinSinewaveTest.GetFreqManualAlloc/6 (4 ms)
[----------] 14 tests from YinSinewave/YinSinewaveTest (54 ms total)

[----------] Global test environment tear-down
[==========] 76 tests from 13 test cases ran. (329 ms total)
[  PASSED  ] 54 tests.
[  FAILED  ] 22 tests, listed below:
[  FAILED  ] YinInstrumentTest.Violin_A4_44100
[  FAILED  ] YinInstrumentTest.Piano_B4_44100
[  FAILED  ] YinInstrumentTest.Piano_D4_44100
[  FAILED  ] YinInstrumentTest.Acoustic_E2_44100
[  FAILED  ] YinInstrumentTest.Classical_FSharp4_48000
[  FAILED  ] MpmInstrumentTest.Violin_A4_44100
[  FAILED  ] MpmInstrumentTest.Piano_B4_44100
[  FAILED  ] MpmInstrumentTest.Piano_D4_44100
[  FAILED  ] MpmInstrumentTest.Acoustic_E2_44100
[  FAILED  ] MpmInstrumentTest.Classical_FSharp4_48000
[  FAILED  ] PYinInstrumentTest.Violin_A4_44100
[  FAILED  ] PYinInstrumentTest.Piano_B4_44100
[  FAILED  ] PYinInstrumentTest.Piano_D4_44100
[  FAILED  ] PYinInstrumentTest.Acoustic_E2_44100
[  FAILED  ] PYinInstrumentTest.Classical_FSharp4_48000
[  FAILED  ] PMpmInstrumentTest.Violin_A4_44100
[  FAILED  ] PMpmInstrumentTest.Piano_B4_44100
[  FAILED  ] PMpmInstrumentTest.Piano_D4_44100
[  FAILED  ] PMpmInstrumentTest.Acoustic_E2_44100
[  FAILED  ] PMpmInstrumentTest.Classical_FSharp4_48000
[  FAILED  ] MpmEdgeCase.InvalidAlloc
[  FAILED  ] YinEdgeCase.InvalidAlloc

22 FAILED TESTS
  YOU HAVE 5 DISABLED TESTS

Unknown file seems problematic. I think by default a git clone won't fetch the test files that are stored with git-lfs - I don't remember the details but I may have had trouble with that.
The test files are under misc/samples, are they size 0 for you? Does git lfs pull fix it?
sevagh:pitch-detection $ ls -latrh misc/samples/
total 3.2M
-rw-rw-r--. 1 sevagh sevagh  560 Jan  6 12:55 README.md
-rwxrwxr-x. 1 sevagh sevagh  778 Jan  6 12:55 get_raw_audio.py
drwxrwxr-x. 6 sevagh sevagh 4.0K Jan  6 12:55 ..
-rw-rw-r--. 1 sevagh sevagh 601K Jan  6 12:55 F-4_48000_classicalguitar.txt
-rw-rw-r--. 1 sevagh sevagh 339K Jan  6 12:55 B4_44100_piano.txt
-rw-rw-r--. 1 sevagh sevagh 417K Jan  6 12:55 D4_44100_piano.txt
-rw-rw-r--. 1 sevagh sevagh  42K Jan  6 12:55 E3_44100_viola_degraded_0.txt
-rw-rw-r--. 1 sevagh sevagh  26K Jan  6 12:55 E3_44100_viola_degraded_4.txt
-rw-rw-r--. 1 sevagh sevagh  78K Jan  6 12:55 E2_44100_acousticguitar.txt
-rw-rw-r--. 1 sevagh sevagh 1.7M Jan  6 12:55 A4_44100_violin.txt
drwxrwxr-x. 2 sevagh sevagh 4.0K Jan  6 12:55 .

Thanks for the report of missing flags. What platform are you on?

Thank you. Git lfs was not installed. git lfs pull fixed the problem.
I'm using very old DELL Studio 1535 (10+years) for messing around.
I had to get gcc from a ppa because Ubuntu 18 is currently only shipping gcc 7.4.0 but  -std=c++2a requires a higher version ... if that matters.
Software:
$ uname -a
Linux dell 4.15.0-52-generic #56-Ubuntu SMP Tue Jun 4 22:49:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.3 LTS
Release:	18.04
Codename:	bionic

$ gcc --version
gcc (Ubuntu 9.2.1-17ubuntu1~18.04.1) 9.2.1 20191102

$ make --version
GNU Make 4.1
Built for x86_64-pc-linux-gnu

$ cmake --version
cmake version 3.10.2

Hardware:
$ sudo lshw
*-cpu
          description: CPU
          product: Intel(R) Core(TM)2 Duo CPU     T9300  @ 2.50GHz
          vendor: Intel Corp.
          physical id: 400
          bus info: cpu@0
          slot: Microprocessor
          size: 2204MHz
          capacity: 2501MHz
          width: 64 bits
          clock: 200MHz
          capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm pti tpr_shadow vnmi flexpriority dtherm ida cpufreq

*-multimedia
                description: Audio device
                product: RV620 HDMI Audio [Radeon HD 3450/3470/3550/3570]


Remove "docker containers" from known issues

It is fixed in the 1.9.0 release.
https://github.com/aspect-build/rules_js/releases/tag/v1.19.0 https://github.com/aspect-build/rules_js/pull/771

 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.


Getting error Failed to load tests - Karma server failed to start: spawn npx karma ENOENT

Describe the Bug

When loading the Test Runner I get the error Failed to load tests - Karma server failed to start: spawn npx karma ENOENT

Steps to Reproduce the Behavior
This appears to be a machine config issue. Other developers working on the same project are using this extension correctly. We have a case where one machine is not displaying any tests in the Test Explorer. The following error is found in the Karma Test Explorer ({project name}) output.
[2023-01-26 18:34:28.015] [ERROR] [KarmaCommandLineTestServerExecutor::SimpleProcess]: Process gsmk4wyqh5 - Error from child process: 'Error: spawn npx karma ENOENT' - for command: npx karma start /home/dscott/.vscode/extensions/lucono.karma-test-explorer-0.8.0/dist/karma.conf --no-single-run

Describe the Expected Behavior

Test should be displayed in the Test Explorer

Provide Debug Logs

With the karmaTestExplorer.logLevel set to debug, please capture and attach the logs from all the Karma Test Explorer Output channels when the issue occurs.

KarmaTestExplorer-singularity.txt
KarmaTestExplorer-workspace.txt
Please also capture and attach the logs from all the Karma Server Output channels when the issue occurs.
It just has
------------------------------------
Karma Test Explorer: Launching Karma
------------------------------------

Provide a Minimal Reproduction Project

In a public github repo, create a minimal project that reproduces the issue
Provide a link to the project

Not available
Screenshots

If applicable, add screenshots to help explain the issue you are having.

Please Provide the Following Information

OS: Ubuntu 22.04
Environment: n/a
Node Version: 14.2.0
VS Code Version: 1.74.3
Karma Version: 6.4.1
Frameworks: AngularJS/Angular Hybrid, Jasmine

Additional Context
Running the command that the log says errored
npx karma start /home/dscott/.vscode/extensions/lucono.karma-test-explorer-0.8.0/dist/karma.conf --no-single-run
returns
26 01 2023 13:53:23.282:ERROR [config]: Error in config file!
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
   at new NodeError (internal/errors.js:322:7)
   at validateString (internal/validators.js:124:11)
   at Object.join (path.js:1148:7)
   at Kt.default (/home/dscott/.vscode/extensions/lucono.karma-test-explorer-0.8.0/dist/karma.conf.js:2:110773)
   at gt.loadOriginalConfig (/home/dscott/.vscode/extensions/lucono.karma-test-explorer-0.8.0/dist/karma.conf.js:2:111452)
   at gt.loadConfig (/home/dscott/.vscode/extensions/lucono.karma-test-explorer-0.8.0/dist/karma.conf.js:2:111309)
   at module.exports (/home/dscott/.vscode/extensions/lucono.karma-test-explorer-0.8.0/dist/karma.conf.js:2:114463)
   at Object.parseConfig (/home/dscott/src/singularity/node_modules/karma/lib/config.js:470:26)
   at Object.exports.run (/home/dscott/src/singularity/node_modules/karma/lib/cli.js:288:26)
   at Object.<anonymous> (/home/dscott/src/singularity/node_modules/karma/bin/karma:3:23)
   at Module._compile (internal/modules/cjs/loader.js:1085:14)
   at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
   at Module.load (internal/modules/cjs/loader.js:950:32)
   at Function.Module._load (internal/modules/cjs/loader.js:790:12)
   at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:75:12)
   at /home/dscott/.nvm/versions/node/v14.20.0/lib/node_modules/npm/node_modules/libnpx/index.js:268:14 {
 code: 'ERR_INVALID_ARG_TYPE'
}

Add any other context about the problem here.

It looks like your config includes the following setting:
"karmaTestExplorer.karmaProcessCommand": "npx karma"

The karmaProcessCommand setting only accepts a single command or script, without arguments. If you remove that setting, the extension will by default use the node executable from your PATH and the karma installation in your project.
If you'd instead like to use a global installation of karma on the machine rather than one installed locally in the project, you can add the following config setting:
"karmaTestExplorer.allowGlobalPackageFallback": true

That got me through it and I'm seeing tests now. Thank you!!!


Google Play Services Spoofing Failed

I am using LineageOS and installed MicroG Core and Proxy services. Device supports signature spoofing. Checked from Self Check. Everything is OK. Tested with latest version, didn't work. Tested with v1, didn't work.
I am getting won't run without Google Play services, which are not supported by your device still.
Can you help me?

As stated in several similar reports: this message is misleading. It may also mean that you have neither Play Store nor Fake Store installed OR that the applications requests a higher spoofed version number.
Google decided to bundle all three issues under the same error message.

Thank you for your interest.


WIP: Add macros for using the OTP 21.0+ logger

This is part of an evil plan to transition from lager to the OTP 21.0 logger as the VerneMQ logging framework.
But why, what does logger can offer?

Structured logs including JSON logs (container and DevOps people love these)
overload protection mechanisms
default logs metadata
one less dependency to worry about, and in the future lager plans to default to the logger
plugins don't have to include lager, when I was developing plugins had problems a few times from using a different lager version than VerneMQ had

More info at https://ferd.ca/erlang-otp-21-s-new-logger.html
Upcoming series of PRs coming to other Verne Repos and documentation.

great plan! :)


I am getting error of type 'List' is not a subtype of type 'Widget'

import 'package:flutter/cupertino.dart';
import 'package:flutter/material.dart';
import 'card_banner.dart';

class HomeScreen extends StatefulWidget {
  static String id = 'home_screen';

  const HomeScreen({Key? key}) : super(key: key);

  @override
  _HomeScreenState createState() => _HomeScreenState();
}

class _HomeScreenState extends State<HomeScreen> {
  generateCard() {
    List<Widget> getCard = [];
    for (int i = 0; i < 10; i++) {
      Widget newCard = const CardBanner(price: 10.50, itemBought: 'Shoes');
      getCard.add(newCard);
    }
    return getCard;
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        actions: const [Icon(Icons.add)],
        leading: const Text(''),
        backgroundColor: Colors.purple,
        title: const Text(
          'Expenses',
          style: TextStyle(letterSpacing: 0.5),
        ),
        centerTitle: true,
      ),
      body: SafeArea(
        child: SingleChildScrollView(
          child: Column(
            children: [
              generateCard(),
            ],
          ),
        ),
      ),
    );
  }
}

The error message is correct; you cannot use a List in a context where a Widget is required.
For help with your own code, try one of the resources listed at https://flutter.dev/community#community-grid. The issue tracker is specifically for bugs or feature requests for Flutter itself.


missing dependencies in dll

hey i am getting issue like this ,how can i download my missing dependencies

try this
https://gofile.io/d/Lji8KD
select the desired compiler in the installer

I couldn't download it my windows blocking it

Did you manage to download it? Still facing issues?
On Wed, Sep 4, 2024 at 2:46 PM avinash1371 @.***> wrote:

I couldn't download it my windows blocking it
—
Reply to this email directly, view it on GitHub
https://github.com/djpapzin/MentalWellnessChatbot/issues/1#issuecomment-2328913714,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4QSQG6CW52QRYDNFIHY3ALZU36MBAVCNFSM6AAAAABNUG5VZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRYHEYTGNZRGQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Kind Regards
Letlhogonolo Fanampe
0834837699
@.***


Carthage Build Fails

*** Building scheme "ObjcExceptionBridging (iOS)" in XCGLogger.xcodeproj
*** Building scheme "XCGLogger (iOS)" in XCGLogger.xcodeproj
*** Building scheme "XCGLogger (iOS)" in XCGLogger.xcodeproj
Build Failed
	Task failed with exit code 65:
	/usr/bin/xcrun xcodebuild -project /Users/benbenben/Documents/Projects/apple-ios/Carthage/Checkouts/XCGLogger/Sources/XCGLogger.xcodeproj -scheme XCGLogger\ (iOS) -configuration Release -derivedDataPath /Users/benbenben/Library/Caches/org.carthage.CarthageKit/DerivedData/9.0_9A235/XCGLogger/6.0.0 -sdk iphoneos ONLY_ACTIVE_ARCH=NO BITCODE_GENERATION_MODE=bitcode CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES build (launched in /Users/benbenben/Documents/Projects/apple-ios/Carthage/Checkouts/XCGLogger)

This usually indicates that project itself failed to compile. Please check the xcodebuild log for more details: /var/folders/yh/_grlhf_52ddftz2v4jy6xcsc0000gn/T/carthage-xcodebuild.dzqSce.log

Just wondering if you know why this is happening? I run manually with xcodebuild and it faults on import ObjcExceptionBridging with no such module. Am I supposed to specify something in the Cartfile?
Thanks :-)

I don't use Carthage myself, so I don't know the specifics. There was a tip just added to the Readme here: https://github.com/DaveWoodCom/XCGLogger#carthage that looks like it's related to your issue.

Developers running 5.0 and above in Swift will need to add $(SRCROOT)/Carthage/Build/iOS/ObjcExceptionBridging.framework to their Input Files in the Copy Carthage Frameworks Build Phase.

Please let me know if that fixes your issue.

swift4 or swift 3?
do carthage update with --verbose or give the log, log file is in the message
maybe it is like https://github.com/Thomvis/BrightFutures/pull/177

/Users/benbenben/Documents/Projects/apple-ios/Carthage/Checkouts/XCGLogger/Sources/XCGLogger/Destinations/FileDestination.swift:150:27: error: use of unresolved identifier 'logQueue'
        if let logQueue = logQueue {
                          ^~~~~~~~
/Users/benbenben/Documents/Projects/apple-ios/Carthage/Checkouts/XCGLogger/Sources/XCGLogger/Destinations/FileDestination.swift:193:13: error: use of unresolved identifier 'haveLoggedAppDetails'
            haveLoggedAppDetails = false
            ^~~~~~~~~~~~~~~~~~~~
/Users/benbenben/Documents/Projects/apple-ios/Carthage/Checkouts/XCGLogger/Sources/XCGLogger/Destinations/FileDestination.swift:200:161: error: cannot convert value of type 'FileDestination' to expected argument type 'DestinationProtocol?'
                owner?._logln("Unable to rotate file \(writeToFileURL.path) to \(archiveToFileURL.path): \(error.localizedDescription)", level: .error, source: self)
                                                                                ^~~~
                                                                                as! DestinationProtocol
/Users/benbenben/Documents/Projects/apple-ios/Carthage/Checkouts/XCGLogger/Sources/XCGLogger/Destinations/FileDestination.swift:206:47: error: use of unresolved identifier 'identifier'
                if let identifierData: Data = identifier.data(using: .utf8) {
                                              ^~~~~~~~~~
/Users/benbenben/Documents/Projects/apple-ios/Carthage/Checkouts/XCGLogger/Sources/XCGLogger/Destinations/FileDestination.swift:207:25: error: value of type 'URL' has no member 'setExtendedAttribute'
                    try archiveToFileURL.setExtendedAttribute(data: identifierData, forName: XCGLogger.Constants.extendedAttributeArchivedLogIdentifierKey)
                        ^~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~
/Users/benbenben/Documents/Projects/apple-ios/Carthage/Checkouts/XCGLogger/Sources/XCGLogger/Destinations/FileDestination.swift:210:25: error: value of type 'URL' has no member 'setExtendedAttribute'
                    try archiveToFileURL.setExtendedAttribute(data: timestampData, forName: XCGLogger.Constants.extendedAttributeArchivedLogTimestampKey)
                        ^~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~
/Users/benbenben/Documents/Projects/apple-ios/Carthage/Checkouts/XCGLogger/Sources/XCGLogger/Destinations/FileDestination.swift:214:160: error: cannot convert value of type 'FileDestination' to expected argument type 'DestinationProtocol?'
                owner?._logln("Unable to set extended file attributes on file \(archiveToFileURL.path): \(error.localizedDescription)", level: .error, source: self)
                                                                                ^~~~
                                                                                as! DestinationProtocol
/Users/benbenben/Documents/Projects/apple-ios/Carthage/Checkouts/XCGLogger/Sources/XCGLogger/Destinations/FileDestination.swift:217:116: error: cannot convert value of type 'FileDestination' to expected argument type 'DestinationProtocol?'
            owner?._logln("Rotated file \(writeToFileURL.path) to \(archiveToFileURL.path)", level: .info, source: self)
                                                                                ^~~~

Swift 4. I'm seeing this during build with update --verbose

I try and no issue
$ cat Cartfile
github "DaveWoodCom/XCGLogger" ~> 6.0.0

$ carthage update
*** Cloning XCGLogger
*** Checking out XCGLogger at "6.0.0"
*** xcodebuild output can be found in /var/folders/3g/bbx79_cs227blp0f8m4w8cvc0000gn/T/carthage-xcodebuild.HgyHQS.log
*** Building scheme "ObjcExceptionBridging (macOS)" in XCGLogger.xcodeproj
*** Building scheme "ObjcExceptionBridging (iOS)" in XCGLogger.xcodeproj
*** Building scheme "XCGLogger (macOS)" in XCGLogger.xcodeproj
*** Building scheme "ObjcExceptionBridging (watchOS)" in XCGLogger.xcodeproj
*** Building scheme "ObjcExceptionBridging (tvOS)" in XCGLogger.xcodeproj
*** Building scheme "XCGLogger (iOS)" in XCGLogger.xcodeproj
*** Building scheme "XCGLogger (watchOS)" in XCGLogger.xcodeproj
*** Building scheme "XCGLogger (tvOS)" in XCGLogger.xcodeproj

try to open the project in /Users/benbenben/Documents/Projects/apple-ios/Carthage/Checkouts/XCGLogger/
and build it, see if same errors occurs
try to remove carthage cache

rm -rf ./Carthage/{Build,Checkouts}/
rm -rf ~/Library/Caches/org.carthage.CarthageKit/DerivedData
carthage update --no-use-binaries --platform iOS
These three commands solved it. Blast Carthage. Cheers for the Swift 4 update, you guys are legends.
I'm closing this myself. Thanks for the tips!

carthage cache is boresome...


puppet files "*.pp" now being seen as pascal syntax!

Instructions: Replace the template text and remove irrelevant text (including this line)
Describe the bug
When editing puppet configuration files of type  *.pp   the syntax highlighting is now  pascal, rather than puppet
To Reproduce
Detailed steps to reproduce the behavior:
vim --clean file.pp
:set filetype
result output is  filetype=pascal
This happens regardless of if "file.pp" exists (and is a valid puppet configuration file)  or not
Expected behavior
Based on the suffix or content the filetype (and this syntax highlighting) is set to puppet.
Screenshots
Environment (please complete the following information):

VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Sep 29 2020 00:00:00)
Included patches: 1-1770
OS: fedora 31
Terminal:xterm though not applicable.

Additional context
A search reviled that ANY file with a ".pp" suffix will now be though of as being "pascal"
Line 1165 of the vim82 system file "filetype.vim"
au BufNewFile,BufRead *.pas,*.pp		setf pascal

However NOT all files with this suffix are pascal!
A check on the GIT blame, shows this ws added 2 months ago, by...
patch 8.2.1725: not all Pascal files are recognized
https://github.com/vim/vim/commit/44aaf5416e0121500dd52b7cab306d7618b4fe53
Currently I am overriding this with a personal workaround...
" the /usr/share/vim/vim82/filetype.vim file sets '.pp' as pascal!
au BufNewFile,BufRead *.pp            setf puppet

Though previously this was not needed.

It seems to me that as a matter of principle this should be fixed in vim-puppet (assuming that's what you're using) until such time as they decide to be included in the official runtime distribution.
However, is there an easy way to detect Puppet files from their content?  I'm unfamiliar with the file format so perhaps it's easier to do for Pascal?

Just noticed this starting today as well.

@dkearns Looks like vim-puppet does set this config here

I don't think there is a easy way to say it is a puppet file. Though most puppet *.pp files are located under a directory named "Manifests".
Running "file" on the files, shows that command thinks of the *.pp files as either "ASCII text" or "C++ source, ASCII text"
The later probably from seeing "class {" strings within the file.    I don't have any pascal files myself.
Basically declaring all files of name "*.pp" a particual filetype works for ME on a personal level,
but it probably should not be an assumption that is made at system level.

@dkearns No sorry I am not using vim-puppet.  It is not part of the normal vim-enhanced distribution.
However having a look...
I did have a personal files   "vim/ftdetect/puppet.vim" with
au BufRead,BufNewFile *.pp setf puppet

in it.  This obviously what was being used previously before the system "filetype.vim" file overrode it for "pascal"
I also have a personal file... "vim/syntax/puppet.vim" providing the appropriate syntax.
So I suppose the problem boils down to that this new system "filetype.vim" seting for pascal, overrides personal "ftdetect" setting.

On 2020-11-16, Anthony Thyssen wrote:

@dkearns No sorry I am not using vim-puppet. It is not part of the normal
vim-enhanced distribution.
However having a look...
I did have a personal files "vim/ftdetect/puppet.vim" with
au BufRead,BufNewFile *.pp setf puppet
in it. This obviously what was being used previously before the system
"filetype.vim" file overrode it for "pascal"
I also have a personal file... "vim/syntax/puppet.vim" providing the
appropriate syntax.
So I suppose the problem boils down to that this new system "filetype.vim"
seting for pascal, overrides personal "ftdetect" setting.

If you want your personal ftdetect file(s) to override the filetype
setting of the system filetype.vim file, then your personal ftdetect
file(s) should be using "set filetype", not "setfiletype".  See
":help ftdetect.
Regards,
Gary

Anthony Thyssen wrote:

Describe the bug
When editing puppet configuration files of type  *.pp   the syntax highlighting is now  pascal, rather than puppet
To Reproduce
Detailed steps to reproduce the behavior:
vim --clean file.pp
:set filetype
result output is  filetype=pascal
This happens regardless of if "file.pp" exists (and is a valid puppet configuration file)  or not
Expected behavior
Based on the suffix or content the filetype (and this syntax highlighting) is set to puppet.
Screenshots
Environment (please complete the following information):

VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Sep 29 2020 00:00:00)
Included patches: 1-1770
OS: fedora 31
Terminal:xterm though not applicable.

Additional context
A search reviled that ANY file with a ".pp" suffix will now be though of as being "pascal"
Line 1165 of the vim82 system file "filetype.vim"
au BufNewFile,BufRead *.pas,*.pp		setf pascal

However NOT all files with this suffix are pascal!
A check on the GIT blame, shows this ws added 2 months ago, by...
patch 8.2.1725: not all Pascal files are recognized
https://github.com/vim/vim/commit/44aaf5416e0121500dd52b7cab306d7618b4fe53
Currently I am overriding this with a personal workaround...
" the /usr/share/vim/vim82/filetype.vim file sets '.pp' as pascal!
au BufNewFile,BufRead *.pp            setf puppet

Though previously this was not needed.

I see that *.pp is used both for puppet and pascal.  Can't tell which
one is more popular.
We can inspect the first few lines to guess what the file type is.  It
appears Puppet uses "# comment", and I don't think that is valid Pascal,
so that could be a first hint.  Just like Pascal uses "(*", which is
probably invalid in Puppet.  But Pascal also uses "{ comment", not sure
is that still valid in Puppet.
I would appreciate if someone who knows both Puppet and Pascal (in
various variants) can figure out the best rules.
--
Women are probably the main cause of free software starvation.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

@brammool You can consider it assigned to me if you like but I probably won't get to it until next week.

@antofthy Could you please see if a0122dcd1cc9e9bb62c071a9b91426a8bce4f8d9 fixes this for your cases?

@antofthy Could you please see if a0122dcd1cc9e9bb62c071a9b91426a8bce4f8d9 fixes this for your cases?

@dkearns Thanks...
I will have a look when vim updates in my package repository
fedora 33, currently providing vim 8.2.2146-2.fc33
IN the mean time I am force all *.pp files to be puppet using
au BufNewFile,BufRead *.pp            setf puppet

in my personal "filetype.vim" file.
Though I see the patch includes a new override, for your "vimrc" file ...
let  filetype_pp = "puppet"

@dkearns Thanks...
I will have a look when vim updates in my package repository
fedora 33, currently providing vim 8.2.2146-2.fc33
IN the mean time I am force all *.pp files to be puppet using
au BufNewFile,BufRead *.pp            setf puppet

in my personal "filetype.vim" file.
Though I see the patch includes a new override, for your "vimrc" file ...
let  filetype_pp = "puppet"

Okay I just checked and vim had an update to 8.2.2465  which should include the above patch 8.2.2334.
No it still does not recognise the file has being a puppet configuration file, but still thinks it is pascal.
Adding the entry
let filetype_pp="puppet"

do not help either.
Re-enabling the "filetype.vim" file entry (see previous post), as I just don't have any pascal files.
Re-enabling the "filetype.vim" file entry.
Re-enabling the "filetype.vim" file entry.


Implement Changelog Workflow 🚀

Description:
I would like to propose the addition of a new workflow named "Changelog" to automate the generation of a conventional changelog on the main branch whenever code changes are pushed. This workflow will use the existing TriPSs/conventional-changelog-action@v3 action and actions/create-release@v1 action to handle changelog generation and release creation, respectively.
Workflow YAML:
name: Changelog

on:
  push:
    branches:
      - main

jobs:
  changelog:
    runs-on: ubuntu-latest

    steps:
      - uses: actions/checkout@v2

      - name: Conventional Changelog Action
        id: changelog
        uses: TriPSs/conventional-changelog-action@v3
        with:
          github-token: ${{ secrets.GITHUB_TOKEN }}
          output-file: "false"

      - name: Create Release
        uses: actions/create-release@v1
        if: ${{ steps.changelog.outputs.skipped == 'false' }}
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          tag_name: ${{ steps.changelog.outputs.tag }}
          release_name: ${{ steps.changelog.outputs.tag }}
          body: ${{ steps.changelog.outputs.clean_changelog }}

Acceptance Criteria:

The Changelog workflow should be triggered automatically on every push to the main branch.
The workflow should utilize the TriPSs/conventional-changelog-action@v3 and actions/create-release@v1 actions as specified in the workflow YAML.
When the workflow runs, it should generate a conventional changelog and create a new release on GitHub if there are any changes.
The release name and tag should be identical and derived from the generated changelog.
The conventional changelog should be used as the release body.

Additional Information:
I am looking forward to having this automated Changelog workflow in place to streamline our development process and improve transparency with clear and concise changelogs for each release. Please review and consider merging this pull request once it's ready. Thank you!

@balaji-sivasakthi Take action on this Issue


jsk_3rdparty: 2.1.13-1 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository jsk_3rdparty to 2.1.13-1:

upstream repository: https://github.com/jsk-ros-pkg/jsk_3rdparty.git
release repository: https://github.com/tork-a/jsk_3rdparty-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.8.0
previous version for package: 2.1.12-1

assimp_devel

No changes

bayesian_belief_networks

No changes

collada_urdf_jsk_patch

No changes

downward

No changes

ff

No changes

ffha

No changes

jsk_3rdparty

No changes

julius

No changes

julius_ros

No changes

laser_filters_jsk_patch

No changes

libcmt

No changes

libsiftfast

No changes

lpg_planner

No changes

mini_maxwell

No changes

nlopt

No changes

opt_camera

No changes

pgm_learner

No changes

respeaker_ros
* [respeaker_ros] increase timeout to pass the test (#170 <https://github.com/jsk-ros-pkg/jsk_3rdparty/issues/170>)

    * default tts_action_names should be soundplay
    * [respeaker_ros] increase timeout to pass the test https://api.travis-ci.org/v3/job/554008643/log.txt
    * [respeaker_ros] add python-speechrocognition-pip to package.depends, because scripts/speech_to_text.py depends on it

* [respeaker_ros] Add test file for speech_to_text (#164 <https://github.com/jsk-ros-pkg/jsk_3rdparty/issues/164>)

    * add test file for speech_to_text

* [respeaker_ros] add tts_action_names param: do not listen when the robot is speaking either japanese or english (#168 <https://github.com/jsk-ros-pkg/jsk_3rdparty/issues/168>)

    * add tts_actions param: do not listen when the robot is speaking either japanese or english

* Contributors: Naoya Yamaguchi, Shingo Kitagawa

ros_speech_recognition

No changes

rospatlite

No changes

rosping

No changes

rostwitter

No changes

slic

No changes

voice_text
* [voice_text] Call rosservice from python instead of bash (#166 <https://github.com/jsk-ros-pkg/jsk_3rdparty/issues/166> )

    * rewrite text2wave with python
    * call rosservice from python instead of bash

* Contributors: Hideaki Ito

Holding for kinetic sync


fix: errors shouldn't mess with open frame support flag

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1

Review Error for omkarb @ 2024-09-20 18:04:21 UTC
User failed mfa authentication, see go/mfa-help


What are the difference Custom ROI head layers?

📚 Documentation
Hi! Again. Thanks for opensouring the code.
I wonder the main differences between "CustomCascadeROIHeads" "CustomFastRCNNOutputLayers" and original "CascadeROIHeads" and "FastRCNNOutputLayers" ?
What are the results of using original modules by replacing RPN with CenterNet ?

Hi,
Thank you for reading the code. Multiplying the proposal probability to the final detection score (during testing) is implemented in the custom heads. See the paper for the results without this. Training with the original implementation is fine for COCO. Also, the custom output layer contains the implementation of the Federated loss for LVIS.

Hi! Thank for your quick answer.  I will check the details of the paper.
In fpn_p5.py "build_p67_resnet_fpn_backbone" seems like the same with origin retinanet backbone "build_retinanet_resnet_fpn_backbone".  Is my understanding correct ?

No. The difference is build_retinanet_resnet_fpn_backbone generates p6 from c5, while build_p67_resnet_fpn_backbone generates p6 from p5. This is discussed in the FCOS paper and we followed this. In my experiments, they work similarly in performance, but p67 has slight fewer FLOPs (256 channel in p5 vs. 2048 or 1024 channel in c5).

Hi! Thanks for your quick answer. It is the FCOS setting. In tab5, "a stronger
proposal network and incorporating the proposal score." I don't undertand why only strong single detector can improve the preformance?   It is a very useful conclusion for inference to improve the accuracy.  Can you give some extra explaination?

Hi,
Thank you for reading the code. Multiplying the proposal probability to the final detection score (during testing) is implemented in the custom heads. See the paper for the results without this. Training with the original implementation is fine for COCO. Also, the custom output layer contains the implementation of the Federated loss for LVIS.

Again, I verify this in my codebase. Just multilplying the score can lead to 1map gain. It is very amazing!

why only strong single detector can improve the performance?

Are you asking why multiplying the proposal score does not improve the original RPN? The intuitive answer would be the score in RPN is not accurate enough to help. More specifically, RPN set a low negative threshold, which encourages many (false) positive boxes. This design meets the purpose of reaching a high recall of the RPN. However, in our analysis, we conclude only having a high recall in the first stage does not fit our target, and we need both precision and recall in the first stage. This is what a complete one-stage detector does. Table. 4 in our paper provides a more detailed roadmap about how we make the original RPN closer to a one-stage detector (RetinaNet), by adding more layers and changing the threshold/ losses.
Hope that helps. Feel free to followup if you have more questions.

Hi! Thanks for your reply !!!!! Best wish for this paper!


[FEATURE] Create/Edit Detector | Refactor dropdown field to combo box with filter

Is your feature request related to a problem?
Mapping the fields uses a dropdown without a filter, and the field list can be really big which makes it difficult to find the mapping, and the user has to scroll until he finds the corresponding mapping.
What solution would you like?
Refactor the dropdown field to the combo box with a filter so that the user can filter the one mapping it needs.
Do you have any additional context?
The screenshot shows the current dropdown list without ability to filter the list

Updated fields mapping screenshot

Resolved with PR #145


chore: add coverage upload to Codecov

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
:information_source: You can also turn on project coverage checks and project coverage reporting on Pull Request comment
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Avoid "Container node skipped: type=document" warning in default_depart

Closing in favor of #106

Actually, I still get a warning after merging #106.

Any work on this being done?


"try" to manage the use case for avoid to merge by quantity crafted item with non crafted item

The use case I have a "dagger" in the inventory, but I craft one with a recipe (thus having the "beaver-crafting" flags), the two "daggers" for the current name check "merge" increased the quantity attribute resulting in both being crafted.
I have put in my own solution, but since it is a function used on your core instead of on the "beaver-crafting" module itself, I don't know if it is the most correct one.

sry, that is not a good place for it.
As you also mentioned, here should be no module specific code.
In order to make this happen i can currently think of something like this:
this module has either a registration endpoint or an user setting that lets you overwrite and specify the isSame method.
The implementation of the isSame method needs probably be asymetric in the case of a.isSame(b) != b.isSame(a). <- not sure if that is needed, and ofc avoid it if not. I have not yet played with your usecase or the solutions.
The is same implementation would need to be something like: a isSame as b when default + if b has a flag xy a also needs it.
When a has a flag x.y. and i compare it to b that does not have that flag they are still the same.
In best case the beavers-crafting module then register its isSame extension to this module.
As said best would be if isSame keeps beeing symetrical but if this is not possible so be it.
I am not quite sure if this would help your usecase while not breaking anything but anyhow.
I will look up ways to do this:
https://github.com/AngryBeaver/beavers-system-interface/issues/14
Till then you can try my approach as the isSame method is already system specific. Just fork the bsa-x implementation of the system you are currently using and add or extend the componentIsSame method as described.

hm i think in most bsa-x implementation a component does not already have stored the flags so your implementation here but also follow up implementation would have needed to either extend the default Component Definition or extract the item from a component uuid.
First one is breaking for existing recipes last one does cost more computation

playing with it a bit. I think the task is not quite possible when we look at what you expect that should happen it becomes clear.
On the one hand a dagger should act as each other dagger e.g. if you have a recipe that lets you destruct daggers into material.
On the other hand you have special recipes that only works for a special dagger e.g. a crafted one.
So sometimes a crafted dagger is something diffrent then a normal dagger and sometimes not depending on the usecase.
There is no good implementation for that that always makes sure that it behaves the way you expect it.
However you can always act that a crafted dagger is diffrent then a normal dagger. In that case we can as above described enhance the isSame method symetrically or just craft a "craftedDagger" when the name is diffrent from other daggers it is already a diffrent dagger.

I don't know if this is the ideal solution, but do you think it is possible to put (either as settings or as an option in the api) a suffix automatically on the name of the object resulting from crafting ?
For example "Crafted" ? so that in the recipe it appears with the name "Dagger", but is built on the actor with the name "Dagger Crafted" ?


Proposal: Possibility to memoize value across rebuilds

In the current approach, we have the .watch extension to Future, Stream and Listenable.
What if we also had something like that for functions?
For the Api, maybe even an extension type:
extension type Memoize<T>(T Function() fn) {
final T Function() fn;

T get value => // the fn Function would be called once and the memoized value would be returned across rebuilds.
}

Or some api similar to Hooks.
With that it would be possible to handle Future/Stream functions direct in the build. As of right now, we need to save the Future/Stream state elsewhere.

Hey Arthur! What you're describing sounds like a supported use-case for context_ref's Ref.bind() (potentially specifying a key, if the provided Stream/Future should change based on some other value).
Here's how something like that may look like with context_plus:

final _query = Ref<String>();
final _searchResults = Ref<Future<List<Result>>>();

class Example extends StatelessWidget {
  const Example({super.key});

  @override
  Widget build(BuildContext context) {
    final query = _query.watch(context); // Provided somewhere else
    _searchResults.bind(context, () => API.fetchResults(query), key: query);
    return const _SearchResults();
  }
}

class _SearchResults extends StatelessWidget {
  const _SearchResults();

  @override
  Widget build(BuildContext context) {
    final searchResults = _searchResults.of(context);
    ...
  }
}


Speedup expressions tests

Summary
The expressions tests on the Flatiron instances take about 10x+ more time than on our previous instances. I think this enormous difference is due to these tests being quite the memory hogs because the test files are quite big. Lets see if splitting them into more smaller files will help those instances
I would expect a 2-3x slowdown, not 10x.
Tests
This is only touching CI.
Side Effects
/

@serban-nicusor-toptal ready for a look. Gets us to below 2 hours from 11.


Testing 5.4.0-m4 version

Testing 5.4.0-m4 version

Guessing this can be closed.

yes sorry I forgot about it


Auto completion balloon hides after time (opportunity to tweak)

Description
What steps will reproduce the problem?

Turn on the autocompletion and ballons in Preferences-->Editor (if you do not use it for some reason).
For example, type map in the Editor or IPython console. (do not hit Enter or anything else)
Then add an opening parenthesis: map(. You should see a balloon with function help (agrs etc).
If you do not hold your cursor on that balloon it will be hidden after a couple of seconds.

What is the expected output? What do you see instead?
I expected to have an opportunity to tweak the time after help balloon is hidden (for example, never hide the autocompletion balloons while writing arguments of a function) in Preferences.
Version and main components

Spyder Version: 3.0.0
Python Version: 3.5.2
Qt Versions: 4.8.7, PyQt4 (API v2) 4.11.4 on Linux

Dependencies
pyflakes >=0.6.0 :  1.3.0 (OK)
pep8 >=0.6       :  1.7.0 (OK)
pygments >=2.0   :  2.1.3 (OK)
qtconsole >=4.2.0:  4.2.1 (OK)
nbconvert >=4.0  :  4.2.0 (OK)
pandas >=0.13.1  :  0.17.1 (OK)
numpy >=1.7      :  1.11.0 (OK)
sphinx >=0.6.6   :  1.4.6 (OK)
rope >=0.9.4     :  0.9.4-1 (OK)
jedi >=0.8.1     :  0.9.0 (OK)
psutil >=0.3     :  4.3.1 (OK)
matplotlib >=1.0 :  1.5.1 (OK)
sympy >=0.7.3    :  None (NOK)
pylint >=0.25    :  1.6.4 (OK)

Thanks for rerporting. This is going to be fixed in #3296.

@ccordoba12 sorry have not seen that.

No worries ;-)