Automatic error report

this is annoyong
search for a term...
in the find in files tab.. on the upper right corner sub window..
click on one of the results and this window pops up\
File "C:\Users\IBM_ADMIN\Anaconda3\envs\ignite\lib\site-packages\spyder\plugins\projects.py", line 156, in
lambda v: self.editor.setup_open_files())
File "C:\Users\IBM_ADMIN\Anaconda3\envs\ignite\lib\site-packages\spyder\plugins\editor.py", line 2693, in setup_open_files
self.load(filenames)
File "C:\Users\IBM_ADMIN\Anaconda3\envs\ignite\lib\site-packages\spyder\plugins\editor.py", line 1940, in load
finfo = self.editorstacks[0].load(filename, set_current=False)
File "C:\Users\IBM_ADMIN\Anaconda3\envs\ignite\lib\site-packages\spyder\widgets\editor.py", line 2249, in load
finfo = self.create_new_editor(filename, enc, text, set_current)
File "C:\Users\IBM_ADMIN\Anaconda3\envs\ignite\lib\site-packages\spyder\widgets\editor.py", line 2167, in create_new_editor
filename=fname)
File "C:\Users\IBM_ADMIN\Anaconda3\envs\ignite\lib\site-packages\spyder\widgets\sourcecode\codeeditor.py", line 732, in setup_editor
self.set_language(language, filename)
File "C:\Users\IBM_ADMIN\Anaconda3\envs\ignite\lib\site-packages\spyder\widgets\sourcecode\codeeditor.py", line 837, in set_language
sh_class = sh.guess_pygments_highlighter(filename)
File "C:\Users\IBM_ADMIN\Anaconda3\envs\ignite\lib\site-packages\spyder\utils\syntaxhighlighters.py", line 1187, in guess_pygments_highlighter
lexer = get_lexer_for_filename(filename)
File "C:\Users\IBM_ADMIN\Anaconda3\envs\ignite\lib\site-packages\pygments\lexers_init_.py", line 203, in get_lexer_for_filename
res = find_lexer_class_for_filename(fn, code)
File "C:\Users\IBM_ADMIN\Anaconda3\envs\ignite\lib\site-packages\pygments\lexers_init.py", line 168, in find_lexer_class_for_filename
for cls in find_plugin_lexers():
File "C:\Users\IBM_ADMIN\Anaconda3\envs\ignite\lib\site-packages\pygments\plugin.py", line 53, in find_plugin_lexers
yield entrypoint.load()
File "C:\Users\IBM_ADMIN\Anaconda3\envs\ignite\lib\site-packages\pkg_resources_init_.py", line 2319, in load
self.require(*args, **kwargs)
File "C:\Users\IBM_ADMIN\Anaconda3\envs\ignite\lib\site-packages\pkg_resources_init_.py", line 2336, in require
items = working_set.resolve(reqs, env, installer)
File "C:\Users\IBM_ADMIN\Anaconda3\envs\ignite\lib\site-packages\pkg_resources_init_.py", line 813, in resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.VersionConflict: (setuptools 14.3.1 (c:\users\ibm_admin\anaconda3\envs\ignite\lib\site-packages), Requirement.parse('setuptools>=18.5'))

Thanks for reporting. This message means that you need to upgrade setuptools to at least version 18.5 in the conda environment that you are running spyder in, which is apparently ignite. You can do this with the command
conda upgrade -n ignite setuptools

from the Anaconda prompt.


INSTALL problem

Describe the bug
When doing an install with pip install quickumls I get the following error
In file included from unqlite.c:22:
In file included from /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/include/python3.8/Python.h:11:
In file included from /Library/Developer/CommandLineTools/usr/lib/clang/12.0.0/include/limits.h:21:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/limits.h:63:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:807:2: error: Unsupported architecture
#error Unsupported architecture
 ^
In file included from unqlite.c:22:
In file included from /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/include/python3.8/Python.h:11:
In file included from /Library/Developer/CommandLineTools/usr/lib/clang/12.0.0/include/limits.h:21:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/limits.h:64:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/machine/limits.h:8:2: error: architecture not supported
#error architecture not supported
 ^
In file included from unqlite.c:22:
In file included from /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/include/python3.8/Python.h:25:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/stdio.h:64:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/_stdio.h:71:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/_types.h:27:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:33:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/machine/_types.h:34:2: error: architecture not supported
#error architecture not supported
 ^
In file included from unqlite.c:22:
In file included from /Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.8/include/python3.8/Python.h:25:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/stdio.h:64:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/_stdio.h:71:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/_types.h:27:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:55:9: error: unknown type name '__int64_t'
typedef __int64_t       __darwin_blkcnt_t;      /* total blocks */
        ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:56:9: error: unknown type name '__int32_t'; did you mean '__int128_t'?
typedef __int32_t       __darwin_blksize_t;     /* preferred block size */
        ^
note: '__int128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:57:9: error: unknown type name '__int32_t'; did you mean '__int128_t'?
typedef __int32_t       __darwin_dev_t;         /* dev_t */
        ^
note: '__int128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:60:9: error: unknown type name '__uint32_t'; did you mean '__uint128_t'?
typedef __uint32_t      __darwin_gid_t;         /* [???] process and group IDs */
        ^
note: '__uint128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:61:9: error: unknown type name '__uint32_t'; did you mean '__uint128_t'?
typedef __uint32_t      __darwin_id_t;          /* [XSI] pid_t, uid_t, or gid_t*/
        ^
note: '__uint128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:62:9: error: unknown type name '__uint64_t'
typedef __uint64_t      __darwin_ino64_t;       /* [???] Used for 64 bit inodes */
        ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:68:9: error: unknown type name '__darwin_natural_t'
typedef __darwin_natural_t __darwin_mach_port_name_t; /* Used by mach */
        ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:70:9: error: unknown type name '__uint16_t'; did you mean '__uint128_t'?
typedef __uint16_t      __darwin_mode_t;        /* [???] Some file attributes */
        ^
note: '__uint128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:71:9: error: unknown type name '__int64_t'
typedef __int64_t       __darwin_off_t;         /* [???] Used for file sizes */
        ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:72:9: error: unknown type name '__int32_t'; did you mean '__int128_t'?
typedef __int32_t       __darwin_pid_t;         /* [???] process and group IDs */
        ^
note: '__int128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:73:9: error: unknown type name '__uint32_t'; did you mean '__uint128_t'?
typedef __uint32_t      __darwin_sigset_t;      /* [???] signal set */
        ^
note: '__uint128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:74:9: error: unknown type name '__int32_t'; did you mean '__int128_t'?
typedef __int32_t       __darwin_suseconds_t;   /* [???] microseconds */
        ^
note: '__int128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:75:9: error: unknown type name '__uint32_t'; did you mean '__uint128_t'?
typedef __uint32_t      __darwin_uid_t;         /* [???] user IDs */
        ^
note: '__uint128_t' declared here
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/_types.h:76:9: error: unknown type name '__uint32_t'; did you mean '__uint128_t'?
typedef __uint32_t      __darwin_useconds_t;    /* [???] microseconds */
        ^
note: '__uint128_t' declared here
In file included from unqlite.c:22:

To Reproduce
I just did a pip install like the instructions said
**Environment **
mac
Additional context
Add any other context about the problem here.

Hi David! Which OS/Python/C compiler version are you using? I seems that you might be trying to install QuickUMLS on a Mac, is it perhaps a M1-equipped Mac?

Hey, thanks for responding.  I have a 2018 macbook pro (intel i7) running 10.15.7 (catalina) and python3.8.  Maybe I misunderstood and you don't support mac??

on macOS, I would recommend installing inside an anaconda environment rather than using the built in python. After you install anaconda, install the following packages separately before pip installing QuickUMLS.
conda install -c conda-forge python-leveldb.

Installing QuickUMLS using the system python installation has proven tricky, so I don't support that at the moment.

So, that helped a lot.  I now have an environment where I can make calls to the matcher running against example text and seeing cuis, etc. coming back.  Thanks-looks good.  One additional question, have you done anything around standing this up as a service in the cloud or dockerizing/helm charting the process so it's not just running locally on my laptop?


Failed to setup device: Bedroom AC (5 is not a valid AirSwingLR)

I got this issue on hassio Log:
Logger: custom_components.panasonic_cc
Source: custom_components/panasonic_cc/init.py:73
Integration: Panasonic Comfort Cloud (documentation)
First occurred: 12:40:37 AM (1 occurrences)
Last logged: 12:40:37 AM
Failed to setup device: Bedroom AC (5 is not a valid AirSwingLR)

Hi,
It's the same issue as https://github.com/sockless-coding/panasonic_cc/issues/5 if you change left/right swing mode from the second left position it will work.
I've issued a pull request with a fix to the panasonic lib.

@sockless-coding thank you. My AC don't have function for L/R swing so I can't put it to that position. Will wait it fix in panasonic lib


clarity-angular version bump from 0.10.7 to 0.10.9 results in angular-cli build module resolution error

[x ] bug
[ ] feature request
[ ] enhancement

Expected behavior
ng build/serve should compile without errors
Actual behavior
Angular CLI based project fails with, what seems to be, a webpack error (field 'browser' doesn't contain a valid alias configuration). Complete error output follows.
ERROR in ./src/app/private/layout/header/header.component.ts
Module not found: Error: Can't resolve 'clarity-angular/layout/nav/clrResponsiveNavigationService' in 'D:\code\testapp\src\app\private\layout\header'
resolve 'clarity-angular/layout/nav/clrResponsiveNavigationService' in 'D:\code\testapp\src\app\private\layout\header'
  Parsed request is a module
  using description file: D:\code\testapp\package.json (relative path: ./src/app/private/layout/header)
    Field 'browser' doesn't contain a valid alias configuration
  after using description file: D:\code\testapp\package.json (relative path: ./src/app/private/layout/header)
    resolve as module
      D:\code\testapp\src\app\private\layout\header\node_modules doesn't exist or is not a directory
      D:\code\testapp\src\app\private\layout\node_modules doesn't exist or is not a directory
      D:\code\testapp\src\app\private\node_modules doesn't exist or is not a directory
      D:\code\testapp\src\app\node_modules doesn't exist or is not a directory
      D:\code\testapp\src\node_modules doesn't exist or is not a directory
      D:\code\node_modules doesn't exist or is not a directory
      D:\node_modules doesn't exist or is not a directory
      looking for modules in D:\code\testapp\node_modules
        using description file: D:\code\testapp\package.json (relative path: ./node_modules)
          Field 'browser' doesn't contain a valid alias configuration
        after using description file: D:\code\testapp\package.json (relative path: ./node_modules)
          using description file: D:\code\testapp\node_modules\clarity-angular\package.json (relative path: ./layout/nav/clrResponsiveNavigationService)
            no extension
              Field 'browser' doesn't contain a valid alias configuration
              D:\code\testapp\node_modules\clarity-angular\layout\nav\clrResponsiveNavigationService doesn't exist
            .ts
              Field 'browser' doesn't contain a valid alias configuration
              D:\code\testapp\node_modules\clarity-angular\layout\nav\clrResponsiveNavigationService.ts doesn't exist
            .js
              Field 'browser' doesn't contain a valid alias configuration
              D:\code\testapp\node_modules\clarity-angular\layout\nav\clrResponsiveNavigationService.js doesn't exist
            as directory
              D:\code\testapp\node_modules\clarity-angular\layout\nav\clrResponsiveNavigationService doesn't exist
      looking for modules in D:\code\testapp\node_modules
        using description file: D:\code\testapp\package.json (relative path: ./node_modules)
          Field 'browser' doesn't contain a valid alias configuration
        after using description file: D:\code\testapp\package.json (relative path: ./node_modules)
          using description file: D:\code\testapp\node_modules\clarity-angular\package.json (relative path: ./layout/nav/clrResponsiveNavigationService)
            no extension
              Field 'browser' doesn't contain a valid alias configuration
              D:\code\testapp\node_modules\clarity-angular\layout\nav\clrResponsiveNavigationService doesn't exist
            .ts
              Field 'browser' doesn't contain a valid alias configuration
              D:\code\testapp\node_modules\clarity-angular\layout\nav\clrResponsiveNavigationService.ts doesn't exist
            .js
              Field 'browser' doesn't contain a valid alias configuration
              D:\code\testapp\node_modules\clarity-angular\layout\nav\clrResponsiveNavigationService.js doesn't exist
            as directory
              D:\code\testapp\node_modules\clarity-angular\layout\nav\clrResponsiveNavigationService doesn't exist
      looking for modules in D:\code\testapp\src
        using description file: D:\code\testapp\package.json (relative path: ./src)
          Field 'browser' doesn't contain a valid alias configuration
        after using description file: D:\code\testapp\package.json (relative path: ./src)
          using description file: D:\code\testapp\package.json (relative path: ./src/clarity-angular/layout/nav/clrResponsiveNavigationService)
            no extension
              Field 'browser' doesn't contain a valid alias configuration
              D:\code\testapp\src\clarity-angular\layout\nav\clrResponsiveNavigationService doesn't exist
            .ts
              Field 'browser' doesn't contain a valid alias configuration
              D:\code\testapp\src\clarity-angular\layout\nav\clrResponsiveNavigationService.ts doesn't exist
            .js
              Field 'browser' doesn't contain a valid alias configuration
              D:\code\testapp\src\clarity-angular\layout\nav\clrResponsiveNavigationService.js doesn't exist
            as directory
              D:\code\testapp\src\clarity-angular\layout\nav\clrResponsiveNavigationService doesn't exist
      looking for modules in D:\code\testapp\src
        using description file: D:\code\testapp\package.json (relative path: ./src)
          Field 'browser' doesn't contain a valid alias configuration
        after using description file: D:\code\testapp\package.json (relative path: ./src)
          using description file: D:\code\testapp\package.json (relative path: ./src/clarity-angular/layout/nav/clrResponsiveNavigationService)
            no extension
              Field 'browser' doesn't contain a valid alias configuration
              D:\code\testapp\src\clarity-angular\layout\nav\clrResponsiveNavigationService doesn't exist
            .ts
              Field 'browser' doesn't contain a valid alias configuration
              D:\code\testapp\src\clarity-angular\layout\nav\clrResponsiveNavigationService.ts doesn't exist
            .js
              Field 'browser' doesn't contain a valid alias configuration
              D:\code\testapp\src\clarity-angular\layout\nav\clrResponsiveNavigationService.js doesn't exist
            as directory
              D:\code\testapp\src\clarity-angular\layout\nav\clrResponsiveNavigationService doesn't exist
[D:\code\testapp\src\app\private\layout\header\node_modules]
[D:\code\testapp\src\app\private\layout\node_modules]
[D:\code\testapp\src\app\private\node_modules]
[D:\code\testapp\src\app\node_modules]
[D:\code\testapp\src\node_modules]
[D:\code\node_modules]
[D:\node_modules]
[D:\code\testapp\node_modules\clarity-angular\layout\nav\clrResponsiveNavigationService]
[D:\code\testapp\node_modules\clarity-angular\layout\nav\clrResponsiveNavigationService.ts]
[D:\code\testapp\node_modules\clarity-angular\layout\nav\clrResponsiveNavigationService.js]
[D:\code\testapp\node_modules\clarity-angular\layout\nav\clrResponsiveNavigationService]
[D:\code\testapp\node_modules\clarity-angular\layout\nav\clrResponsiveNavigationService]
[D:\code\testapp\node_modules\clarity-angular\layout\nav\clrResponsiveNavigationService.ts]
[D:\code\testapp\node_modules\clarity-angular\layout\nav\clrResponsiveNavigationService.js]
[D:\code\testapp\node_modules\clarity-angular\layout\nav\clrResponsiveNavigationService]
[D:\code\testapp\src\clarity-angular\layout\nav\clrResponsiveNavigationService]
[D:\code\testapp\src\clarity-angular\layout\nav\clrResponsiveNavigationService.ts]
[D:\code\testapp\src\clarity-angular\layout\nav\clrResponsiveNavigationService.js]
[D:\code\testapp\src\clarity-angular\layout\nav\clrResponsiveNavigationService]
[D:\code\testapp\src\clarity-angular\layout\nav\clrResponsiveNavigationService]
[D:\code\testapp\src\clarity-angular\layout\nav\clrResponsiveNavigationService.ts]
[D:\code\testapp\src\clarity-angular\layout\nav\clrResponsiveNavigationService.js]
[D:\code\testapp\src\clarity-angular\layout\nav\clrResponsiveNavigationService]
 @ ./src/app/private/layout/header/header.component.ts 20:0-107
 @ ./src/app/private/private.module.ts
 @ ./src/app/app.module.ts
 @ ./src/main.ts
 @ multi webpack-dev-server/client?http://localhost:4200 ./src/main.ts

Reproduction of behavior
package.json content is as below, changing the clarity-angular version from 0.10.7 to 0.10.9 as mentioned results in the failure above.
{
  "name": "testapp",
  "version": "0.0.0",
  "license": "MIT",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "build.test": "ng build --target=production --environment=test",
    "build.prod": "ng build --target=production --environment=prod",
    "test": "ng test",
    "lint": "ng lint",
    "e2e": "ng e2e"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "^4.4.1",
    "@angular/common": "^4.4.5",
    "@angular/compiler": "^4.4.5",
    "@angular/core": "^4.4.5",
    "@angular/forms": "^4.4.5",
    "@angular/http": "^4.4.5",
    "@angular/platform-browser": "^4.4.5",
    "@angular/platform-browser-dynamic": "^4.4.5",
    "@angular/router": "^4.4.5",
    "@angular/upgrade": "^4.4.5",
    "@webcomponents/custom-elements": "1.0.4",
    "bootstrap": "4.0.0-beta",
    "chart.js": "^2.7.0",
    "clarity-angular": "0.10.7",
    "clarity-icons": "^0.10.9",
    "clarity-ui": "^0.10.9",
    "core-js": "^2.5.1",
    "d3": "^4.11.0",
    "font-awesome": "^4.7.0",
    "jquery": "^3.2.1",
    "moment": "2.19.1",
    "ng2-charts": "1.6.0",
    "ng2-toasty": "^4.0.3",
    "popper.js": "^1.12.5",
    "rxjs": "^5.4.2",
    "ts-helpers": "1.1.2",
    "zone.js": "^0.8.18"
  },
  "devDependencies": {
    "@angular/cli": "^1.4.7",
    "@angular/compiler-cli": "^4.4.5",
    "@types/d3": "^4.11.0",
    "@types/jasmine": "^2.6.0",
    "@types/node": "^8.0.34",
    "codelyzer": "^3.2.1",
    "jasmine-core": "^2.8.0",
    "jasmine-spec-reporter": "^4.2.0",
    "karma": "^1.7.1",
    "karma-chrome-launcher": "^2.2.0",
    "karma-cli": "1.0.1",
    "karma-coverage-istanbul-reporter": "^1.3.0",
    "karma-jasmine": "1.1.0",
    "karma-jasmine-html-reporter": "0.2.2",
    "node-sass": "^4.5.3",
    "protractor": "5.1.2",
    "raw-loader": "^0.5.1",
    "sass-loader": "^6.0.6",
    "ts-node": "^3.3.0",
    "tslint": "^5.7.0",
    "typescript": ">=2.1.0 <2.4.0"
  }
}

Environment details

Angular version: 4.x.x
See above.

Clarity version:
See above.

Windows 10, but using Git bash

@hippee-lee and @jeeyun : Could one of you check this out?

Also experiencing this issue.

@williamhallatt @rokobasilisk: Clarity website is built on top of Angular CLI too and we didn't face this issue. Could you give us more information to reproduce this? Can this be replicated on a Plnkr? https://embed.plnkr.co/AuJuo5/ If not then can you share a git repo which reproduces this?

@adityarb88 Here we go mate: clarity-break-minimal
If you grab that repo 'as-is', it will build ("clarity-angular": "0.10.7"), as soon as you (nuke your node_modules), update the package.json to 0.10.9, 'yarn install' (I doubt it matters how you pull your packages, npm or otherwise, but included this bit for the sake of completeness) and 'ng build', you'll get the failure described above.
I savagely ripped apart an existing product to produce this franken-app, so I hope this is enough to work with :)

@adityarb88 it turns out we were referencing a clarity object 'Page' in a unit test which was causing the error as Clarity seems to have started using Declaration files in the node_modules. We fixed our unit tests by changing an import from import { Page } from 'clarity-angular/data/datagrid/providers/page'; to import { ɵz as Page } from 'clarity-angular'; .
Then we also had to pass in a StateDebouncer to the Page object but that was unrelated.

@williamhallatt, @rokobasilisk: It looks to me that this issue is happening when you try to access the internal API. @williamhallatt In the repo your linked above I see this:
import { ClrResponsiveNavCodes } from 'clarity-angular/layout/nav/clrResponsiveNavCodes';
import { ClrResponsiveNavigationService } from 'clarity-angular/layout/nav/clrResponsiveNavigationService';

Could you please tell me why you need access to the nav service and the nav codes. We do not export these and accessing them is going to cause breakages.
Same applies for Page @rokobasilisk
cc: @hippee-lee

@adityarb88 we needed a greater level of customisation, and also as I previously mentioned for more thorough unit testing.
We understand the risks involved but thought our solution might help someone down the line and was worth posting!

We also face the same issue in our customized checkbox tree view that meets our product need after upgrading to 0.10.9. It seems we cannot customize clarity-angular widgets anymore.

@rokobasilisk: I am failing to understand why you need Page for testing components on your side. Could you please post an example and elaborate more on that?
@showlong: We need more details to understand the issue.

It seems we cannot customize clarity-angular widgets anymore.

I don't believe this is true. What exactly are you trying to customize? What were you trying to access before that you cannot access now? If you provide us with more details and the use case for doing that, we can consider providing what you need or recommend an alternative solution.
I would recommend that you file a separate issue for your customized tree view use case so that we can review and provide feedback.
Thanks!

I simply just want to +1 to report this issue.
In my case it seems the following 3 internal API are not exposed from your webpack build now but are available from previous angular cli build. It is simple question that if your webpack build block the internal APIs.
import {Expand} from 'clarity-angular/utils/expand/providers/expand';
import {TreeSelectionService} from 'clarity-angular/data/tree-view/providers/tree-selection.service';
import {clrTreeSelectionProviderFactory} from 'clarity-angular/data/tree-view/providers/tree-selection.provider';

I believe our bundles are now correctly isolating private APIs, and I don't believe we want to be supporting internal APIs that aren't meant for external consumption.
I'm not entirely sure what the use cases are for them here. If you are accessing internal APIs of Clarity, then you are likely unit testing Clarity and not your components, and the recommendation is to test using the public APIs.

@adityarb88
"Could you please tell me why you need access to the nav service and the nav codes. We do not export these and accessing them is going to cause breakages."
That explains a lot, I did not actually implement those bits, will find out and confirm whether or not there was a logical use-case or if it is learning curve related.
Thanks for the investigation and feedback!

@adityarb88 In relation to your question to @williamhallatt  above - we're using the ResponsiveNavService because the responsive menu's hamburger toggle actions dont seem to fire automatically - at least in our implementation.
I've forked the example @williamhallatt created to demonstrate the issue - to see this behaviour, pull down and serve this app: https://github.com/steveland83/clarity-break-minimal
In this fork I've commented out the calls to ResponsiveNavService. Clicking the menu hamburger trigger no longer toggles the responsive menu. If you revert the commit I made, you'll see that the menu triggers.
**Note that the Burger will only be visible when the browser is resized to a mobile screen size.
I adapted this code from here:
https://github.com/vmware/clarity/blob/6d3e670d8b386df45e9dd201e3b026e67be03a34/src/clarity-angular/layout/nav/header.ts
I'm assuming that we must have an issue in our implementation which is the root cause - but I'm unable to find it based on the examples available.
The documentation for sidenav (https://vmware.github.io/clarity/documentation/sidenav) doesnt mention of this functionality or provide an applicable example, so any pointers you can offer would be most appreciated :)

Update to the above - I've just found https://vmware.github.io/clarity/documentation/navigation
This section does describe the usage for responsive nav - we just didnt think to look under patterns before.
I've tested with this - and it certainly does work if used as described (<clr-header> tag directly within <clr-main-container>). In our case we insert this code based on the route (we have public & private menus) - its also in a child component a few levels down - and this seems to break it.

@steveland83: Could you replicate your issue on a Plnkr https://embed.plnkr.co/AuJuo5/ and file a new issue. Once you do that we can figure out whats going on.

I am going to close this issue. For more details please read @youdz's response here: https://github.com/vmware/clarity/issues/1649#issuecomment-339968863
I would recommend that you submit a separate issue for each of your use cases which break after upgrading from 0.10.7 to the latest version. Please provide details on why you need to access the internal API and we can give more feedback on how your issue can be resolved. If you are trying to do something that has a valid use case and is not present currently, we wouldn't mind providing that feature to you through our public API. But to do that we need to know more details about what you are trying to do and the use case for doing that. Thanks again! Please feel free to reach out to use if you have any more questions.

Thanks @adityarb88 - we do not need access to the internal API.
Our problems with Responsive Nav were the result of incorrect classes on the nav element - which were resolved after comparing to the example at https://vmware.github.io/clarity/documentation/navigation


document with godoc properly

Properly document using godoc with examples as seen here:
https://github.com/fluhus/godoc-tricks/blob/master/doc.go
https://pkg.go.dev/github.com/fluhus/godoc-tricks

see https://pkg.go.dev/github.com/bjartek/overflow/overflow


Consider integrating BIP-324

Hi, neat tool. This can be especially useful for someone in a pinch and without resources to use a full node. While I think many privacy-focused folks will use Tor, BIP-324 also provides increased privacy and censorship resistance, particularly at the ISP level. I co-authored the library for this in rust-bitcoin, so I would be happy to give a crack at integrating BIP-324 handshakes. You may also give it a shot if you'd like, we have some example code in the form of the proxy within the library. There is absolutely no rush though, as although v2 transport is the default in the most recent bitcoin patch, the adoption rate is relatively low from my experience. Cheers.

Thanks for the suggestion. I love the idea but I have some concerns with regard to the library itself:

The crate depends on rust-bitcoin instead of being an optional dependency of rust-bitcoin. Why does this matter? I am averse to bringing in dependencies that transitively include different versions of rust-bitcoin, at least until the secp256k1 dependency can be switched off. I explained the rationale here. I hit this problem a few times in different projects and fixing the dependency tree can be a sizable effort.

The crate should enable different rng implementations, either through a trait or feature gating. I generally use fastrand in my projects due to its tiny footprint and speed and I want to avoid bringing in crates that duplicate its functionality. The goal of pushtx is to be very small (I want to slim it down to under a megabyte) in order to make it a common lightweight tool that ships with different distros and doesn't download dozens of megabytes.

As for rust-bitcoin, it doesn't seem that it has stabilization as a goal any time soon -- every minor release comes with a sizable API breakage. That makes it good only as a high level dependency that appears once in the whole tree and that the rest of the app is as agnostic of as much as possible. It's a sad state of affairs because it's an indispensable tool but it really doesn't lend itself to maintainability -- the burden of future debt it places on the developer is very high.
The networking library I'm using for this project is protocol-agnostic and doesn't know about rust-bitcoin: https://github.com/alfred-hodler/peerlink. I prefer to stick to that approach as much as possible. I was able to invert the dependency tree there so something similar might be possible with your library as well.
Otherwise, I'd love for this tool to implement BIP-324.


Add custom icon/name for leak canary

When you have a bunch of apps on your device that all use Leak Canary, it's helpful if they use custom icons/names so you can tell them apart.

Ahh, this is great! I didn't realize this was supported. Thanks!


C/C++ extension 1.12.4: Mac OS arm64 binaries are not executable

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.72.0
OS Version: Darwin arm64 21.6.0

Steps to Reproduce:

Install C/C++ extension 1.12.4 from the Marketplace UI or from VSIX
Find that the native binaries included in the extension do not run. Logs below.

qiweiw@DK27P026WM bin % ./cpptools-srv
zsh: exec format error: ./cpptools-srv
qiweiw@DK27P026WM bin %
qiweiw@DK27P026WM bin % file cpptools-srv
cpptools-srv: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-musl-aarch64.so.1, with debug_info, not stripped

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.72.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

@VSCodeTriageBot
corrected version

Problem goes away when the app is moved out of the "Downloads" directory. Sorry for the spam.


Version 0.33 requires ruby 2.4 and above

Firstly thanks a lot for the contributions of this awesome gem.
Recently I was trying to upgrade this gem to version 0.33 but got this error while running bundle update. My ruby version is 2.3.3.
Bundler could not find compatible versions for gem "ruby":
  In Gemfile:
    ruby

    grape-swagger (= 0.33) was resolved to 0.33.0, which depends on
      ruby (>= 2.4)

As I understand, from version 0.33, grape-swagger will not support ruby below 2.4. Since this is not mentioned in the CHANGELOG, I would like to know whether you actually drop support for ruby below 2.4 or not.
Thank you very much.

This doesn't seem to be correct. It seems this was changed in a prepare to release commit, rather than on a PR:
https://github.com/ruby-grape/grape-swagger/commit/7237ef3525f907b82b1b4be8d81269d3602af7d0
@LeFnord  did you do so in purpose? If so - can we ammend the changelog? Else - can we rever this?

yeap, offcial support for ruby < 2.4 is dropped as it is common for most gems to only support last three versions … a look into travis ci shows the supported versions
@myxoh … yeap I dropped it … if you want, add something to the changelog, but please don't revert it, there was a bit more on changes as you mentioned
@sondnm … maybe it is a good point to update your used ruby version, the actual one is 2.6 and 2.7 is in the pipeline

Thanks a lot for the confirmation.
I am having trouble updating the ruby version although I know it's no longer supported 😆
I created a PR to update the changelog https://github.com/ruby-grape/grape-swagger/pull/763 though.


style: remove empty comments for license

What type of PR is this?

style
Check the PR title.

[ ] This PR title match the format: <type>(optional scope): <description>
[ ] The description of this PR title is user-oriented and clear enough for others to understand.

(Optional) Translate the PR title into Chinese.
去掉 license 顶层的空注释
(Optional) More detail description for this PR(en: English/zh: Chinese).

en: remove empty comments for license
zh(optional): 去掉 license 顶层的空注释
Which issue(s) this PR fixes:

thanks @FGYFFFF


Feature request: Open the map view for a record when clicking on the globe in the occurrence overlay

It would be nice if clicking on the globe icon in the occurrence overlay opened up a map view for that entity. This could be a simple call to the api to reload the same page but appending &view=MAP to the end of the url and replacing a search query with a unique ID. I have it working with the Occurence ID, but something similar would also likely be possible with any unique identifier (GBIF ID etc), as some occurrence records may not have a GUID like field.
Clicking on:

Would load the map view via a call that looks like this /specimen/search?occurrenceId=F9210E4D-35FF-FB40-9799-E35E27F3C6E0&view=MAP (/specimen may be /occurrence for other instances)

I'd rather extend the occurrence view with richer content. As it is now it is largely a stub without important features such as a map, video and audio, iiif links.
Especially since we will need occurrences pages on a url of their own.
Does that make sense please?


Unresolved reference: MaterialDialog

I can't use your library because AS can't find the path to MaterialDialog. Pointed the way manually, did not help.
Android Studio 3.4, Gradle 3.4.0, Kotlin, Androidx

I got the above error when I used "implementation 'com.afollestad.material-dialogs:input:3.0.0-alpha1'" WITHOUT having "implementation 'com.afollestad.material-dialogs:core:3.0.0-alpha1". I am not sure if they are supposed to work independent of each other, but making sure that the core library was installed took away the issue for me.
However, this issue wasn't actually happening to me until I did my latest upgrades to Android to 3.4, Kotlin to 1.3.21, etc. I then the experienced "Unresolved reference: MaterialDialog" error.
I hope this is of help to you and anyone else who may be experiencing this.

The core module is the fundamental module that you need in order to use this library. The others are extensions to core.

You definitely need the core dependency. This is clearly documented in README.md.

Closing, assuming that's the problem here


libseccomp: move gpref from buildInputs to nativeBuildInputs

Fixes a cross-compilation issue due to gperf not being available on the host system

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build libseccomp
@GrahamcOfBorg  build pkgsCross.aarch64-multiplatform.libseccomp

makeWrapper should be removed as it is unused (otherwise it would have had to be moved as well)

Done


Member function calls are slow

Member function calls on usertypes are slow. There should be a way to call the function directly without going through the index metamethod to get the right function, but doing that may require explicitly setting the functions on each and every userdata when the :new() function is run. This may be problematic...

Unfortunately, to support our feature set, they will need to remain slower than they could be. This is an unfortunate side-effect of lua.

Fixed:

https://github.com/ThePhD/sol2/commit/019c7b037b90db798faaeee4385699a72aaacc85


ISSUE-120: Add documentation for migration

Initial work for addending migration documentation.

@satishd it was my first encounter with rst, i assumed it was like markdown, so used my ide's markdown editor. Is there any recommended IntelliJ plugin for RST editing, or even stand alone tool that you suggest?

@michaelandrepearce same here :) Intellij identifies rST but it does not show any view mode. I was using http://rst.ninjs.org/ tool

@satishd thanks, that tool was useful, updated and pushed.
Will need updating later with links to maybe further docs about schema import once sorted.
But for now i think its good.

Closes #120


Invalid character constant

Error:F:,,,,\logger\LoggerPrinter.java:54.47: Invalid character constant

Can you post your log input please?


Remove "plain" from code_challenge_methods_supported in Discovery

How can we define which values are displayed for code_challenge_methods_supported in the Discovery endpoint?
By default it lists plain and S256, but I don't want to support plain and want to remove it from the Discovery endpoint, but can't find any options to do this.

This might no be easily possible right now without replacing the whole response generator.

Also, isn't it actually a per-client setting to allow plain?

Yes, it is a per-client setting, but I don't want to publish that I support plain when I personally won't allow any clients to use it.

You could maybe achieve the same thing by adjusting the discovery document response generator?


Fix vlc media controller offset on android

On Android, we had a media controller offset problem, this PR fixes that

Not good, closing...


SendMessageActionConfig should be persisted to a sqlite database

SendMessageActionConfig is currently being serialized and stored within each Action's actionInfo. This should be moved to a sqlite database, or something similar, to make extending functionality easier

SQLite may prove difficult here, as the configuration needs to be associated with specific event instances. What we should likely do instead is find a less fickle way of serializing the data to the existing byte[] -- maybe encoding to JSON before transforming?


Extract Method/Extract Variable in the Context Menu are not mapped to Pylance refactorings

Environment data

Language Server version: 2021.5.4
OS and version: Windows
Python version (& distribution if applicable, e.g. Anaconda): 3.8.10

Expected behaviour
When I open the context menu after highlighting a block of code, the Extract Method/Extract Variable items should be mapped to the Pylance refactorings.
Actual behaviour
They are not. Upon selection, I see this prompt...which is for Jedi.

Logs
Not really applicable
Code Snippet / Additional information

"Refactor..." seems to work as intended (with Pylance refactorings).

This has been resolved.., Thanks SO :)


mDNS binds to all interfaces

I run librespot on a Raspian which also runs a series of docker containers, which implies a shitload of networking interfaces, not all of them routable on the local network. BUT, the mdns responder in librespot includes all of these in the published record. This results in inconsistent connectivity/detection for Spotify clients.
# sudo tcpdump -n host <IP_ADDRESS> and port 5353
08:59:03.662690 IP <IP_ADDRESS>.5353 > <IP_ADDRESS>.5353: 0*- [0q] 11/0/0 PTR Stue HiFi._spotify-connect._tcp.local., SRV stue.local.:33099 0 0, TXT "VERSION=1.0" "CPath=/", A <IP_ADDRESS>, A <IP_ADDRESS>, A <IP_ADDRESS>, A <IP_ADDRESS>, A <IP_ADDRESS>, A <IP_ADDRESS>, A <IP_ADDRESS>, A <IP_ADDRESS> (434)

Just to verify I built a macvlan setup with a separate network namespace including the macvlan interface only which resulted in the expected:
# sudo tcpdump -n host <IP_ADDRESS> and port 5353
09:09:38.525806 IP <IP_ADDRESS>.5353 > <IP_ADDRESS>.5353: 0*- [0q] 4/0/0 PTR Stue HiFi._spotify-connect._tcp.local., SRV stue.local.:39285 0 0, TXT "VERSION=1.0" "CPath=/", A <IP_ADDRESS> (252)

Now, I assume this is an oversight but we should have a config/commandline option to specify which network interface to bind to. As discovery is a core function in the librespot library we probably need to include it here and not push it to "future daemon".
For now I get around this with a network namespace limiting the visibility of interfaces for the daemon but this is not quite a well-known nor documented configuration nor should we expect every implementor such as spotifyd/raspotify/vollibrespot to known and implement.
Best regards
Frafall
Example of local interfaces when running on a host also running docker containers:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether b8:27:eb:4c:c5:e5 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DORMANT group default qlen 1000
    link/ether b8:27:eb:19:90:b0 brd ff:ff:ff:ff:ff:ff
4: br-22f744702de6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
    link/ether 02:42:1c:cb:94:d6 brd ff:ff:ff:ff:ff:ff
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
    link/ether 02:42:db:f1:96:3e brd ff:ff:ff:ff:ff:ff
6: proxy_bridge: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
    link/ether 02:42:f0:10:4f:43 brd ff:ff:ff:ff:ff:ff
8: vetha1ef36c@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master proxy_bridge state UP mode DEFAULT group default
    link/ether 4e:b2:e8:f0:d5:e6 brd ff:ff:ff:ff:ff:ff link-netnsid 0
10: veth6dd6abd@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master proxy_bridge state UP mode DEFAULT group default
    link/ether c2:a8:84:73:d8:b5 brd ff:ff:ff:ff:ff:ff link-netnsid 1
12: veth2e8b881@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master proxy_bridge state UP mode DEFAULT group default
    link/ether 9e:36:87:7d:ad:9c brd ff:ff:ff:ff:ff:ff link-netnsid 2

Macvlan config:
# Configure a macvlan interface in a separate namespace
ip link add mac1 link eth0 type macvlan mode bridge
ip netns add net1
ip link set mac1 netns net1
ip netns exec net1 ip link set lo up
ip netns exec net1 ip addr add <IP_ADDRESS>/24 dev mac1
ip netns exec net1 ip link set mac1 up
ip netns exec net1 route add default gw <IP_ADDRESS>

# macvlan 'hack' for host visibility, ip by dhcpcd
ip link add mac0 link eth0 type macvlan  mode bridge
ip link set mac0 up
ip route add <IP_ADDRESS>/32 dev mac0

# Run librespot in network namespace
ip netns exec net1 /usr/bin/librespot --name "Stue HiFi" --backend alsa --bitrate 320 --disable-audio-cache --enable-volume-normalisation --linear-volume --initial-volume=100 --verbose

Currently libmdns doesn't let us select an interface to listen on, and binds to all non loopback ones.
There is an issue upstream to enhance this, but needs work..

Well, got Vollibrespot running in a network namespace with macvlan, publishes only what I want and get reliable discovery, only needed to make sure ipv6 and lo interface was properly set up.
But, I'd guess more ppl than me get unreliable discovery due to docker messing up network interfaces.
Nice work on the Vollibrespot btw, using it due to metadata and control functions :)

Well, got Vollibrespot running in a network namespace with macvlan, publishes only what I want and get reliable discovery, only needed to make sure ipv6 and lo interface was properly set up.
But, I'd guess more ppl than me get unreliable discovery due to docker messing up network interfaces.

Interesting workaround, like you said probably helpful in other situations as well!

Nice work on the Vollibrespot btw, using it due to metadata and control functions :)

I should really clean it up, it started of as a quick PoC for Volumo, but nice to see that it's useful to others as well! :-)

@Johannesd3 I thought about assigning this to you, as you have new mDNS in the works.

I have the same problem and reported upstream.

https://github.com/librespot-org/libmdns/pull/35 released as 0.7

Hi, since librespot now uses libmdns 0.7 which added support for binding to interface(s), would it be possible to implement this option?
I would try a PR myself, but unfortunately have no coding experience so stepping asside here

Hi, since librespot now uses libmdns 0.7 which added support for binding to interface(s), would it be possible to implement this option?
I would try a PR myself, but unfortunately have no coding experience so stepping asside here

Sure if @roderickvd thinks it's a good idea I think I can do that pretty easily.

It would probably be something like discovery-interfaces would be a comma separated list or a single interface, (I'll have to look at libmdns to see what our options are?) that defaults to "any".

Sure why not? The "why not" of course is not to have too many command line options, but in this case I think it's in fair demand and a new option is warranted.

I have a proposal for implementing an option to specify to which interfaces the mDNS responder shall bind. I am a new to Rust so my code will be for sure not optimal. I am unsure how to implement parsing IPv4 and IPv6 addresses. I used the libmdns exmaple from here as a reference.
Please give feedback :).
diff --git a/Cargo.lock b/Cargo.lock
index fe16c16..c97cdbb 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -1365,6 +1365,7 @@ dependencies = [
  "librespot-playback",
  "librespot-protocol",
  "log",
+ "regex",
  "rpassword",
  "sha1",
  "thiserror",
diff --git a/Cargo.toml b/Cargo.toml
index 7a423d7..23f41cc 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -60,6 +60,7 @@ sha1 = "0.10"
 thiserror = "1.0"
 tokio = { version = "1", features = ["rt", "macros", "signal", "sync", "parking_lot", "process"] }
 url = "2.2"
+regex = "1.5"

 [features]
 alsa-backend = ["librespot-playback/alsa-backend"]
diff --git a/discovery/src/lib.rs b/discovery/src/lib.rs
index 3c01003..4732230 100644
--- a/discovery/src/lib.rs
+++ b/discovery/src/lib.rs
@@ -47,6 +47,7 @@ pub struct Discovery {
 pub struct Builder {
     server_config: server::Config,
     port: u16,
+    bind_ips: Vec<std::net::IpAddr>,
 }

 /// Errors that can occur while setting up a [`Discovery`] instance.
@@ -87,6 +88,7 @@ impl Builder {
                 client_id: client_id.into(),
             },
             port: 0,
+            bind_ips: vec![],
         }
     }

@@ -102,6 +104,12 @@ impl Builder {
         self
     }

+    /// Set the ip addresses on which the mdns service should bind
+    pub fn bind_ips(mut self, bind_ips: Vec<std::net::IpAddr>) -> Self {
+        self.bind_ips = bind_ips;
+        self
+    }
+
     /// Sets the port on which it should listen to incoming connections.
     /// The default value `0` means any port.
     pub fn port(mut self, port: u16) -> Self {
@@ -117,6 +125,7 @@ impl Builder {
         let mut port = self.port;
         let name = self.server_config.name.clone().into_owned();
         let server = DiscoveryServer::new(self.server_config, &mut port)??;
+        let bind_ips = self.bind_ips;

         #[cfg(feature = "with-dns-sd")]
         let svc = dns_sd::DNSService::register(
@@ -127,14 +136,23 @@ impl Builder {
             port,
             &["VERSION=1.0", "CPath=/"],
         )?;
-
+
         #[cfg(not(feature = "with-dns-sd"))]
-        let svc = libmdns::Responder::spawn(&tokio::runtime::Handle::current())?.register(
+        let svc = if !bind_ips.is_empty() {
+            libmdns::Responder::spawn_with_ip_list(&tokio::runtime::Handle::current(), bind_ips)?.register(
             "_spotify-connect._tcp".to_owned(),
             name,
             port,
             &["VERSION=1.0", "CPath=/"],
-        );
+            )
+        } else {
+            libmdns::Responder::spawn(&tokio::runtime::Handle::current())?.register(
+                "_spotify-connect._tcp".to_owned(),
+                name,
+                port,
+                &["VERSION=1.0", "CPath=/"],
+            )
+        };

         Ok(Discovery { server, _svc: svc })
     }
diff --git a/src/main.rs b/src/main.rs
index d5c5392..e28f05d 100644
--- a/src/main.rs
+++ b/src/main.rs
@@ -14,6 +14,7 @@ use log::{error, info, trace, warn};
 use sha1::{Digest, Sha1};
 use thiserror::Error;
 use url::Url;
+use regex::Regex;

 use librespot::{
     connect::{config::ConnectConfig, spirc::Spirc},
@@ -185,6 +186,7 @@ struct Setup {
     zeroconf_port: u16,
     player_event_program: Option<String>,
     emit_sink_events: bool,
+    bind_ips:  Vec<std::net::IpAddr>,
 }

 fn get_setup() -> Setup {
@@ -240,6 +242,7 @@ fn get_setup() -> Setup {
     const VOLUME_CTRL: &str = "volume-ctrl";
     const VOLUME_RANGE: &str = "volume-range";
     const ZEROCONF_PORT: &str = "zeroconf-port";
+    const BIND_IP: &str = "bind-ip";

     // Mostly arbitrary.
     const AP_PORT_SHORT: &str = "a";
@@ -258,6 +261,7 @@ fn get_setup() -> Setup {
     const DISABLE_GAPLESS_SHORT: &str = "g";
     const DISABLE_CREDENTIAL_CACHE_SHORT: &str = "H";
     const HELP_SHORT: &str = "h";
+    const BIND_IP_SHORT: &str = "i";
     const CACHE_SIZE_LIMIT_SHORT: &str = "M";
     const MIXER_TYPE_SHORT: &str = "m";
     const ENABLE_VOLUME_NORMALISATION_SHORT: &str = "N";
@@ -570,6 +574,12 @@ fn get_setup() -> Setup {
         AUTOPLAY,
         "Explicitly set autoplay {on|off}. Defaults to following the client setting.",
         "OVERRIDE",
+    )
+    .optopt(
+        BIND_IP_SHORT,
+        BIND_IP,
+        "Interface IP address wo which mDNS will bind. Defaults to any interface",
+        "IP"
     );

     #[cfg(feature = "passthrough-decoder")]
@@ -1168,6 +1178,47 @@ fn get_setup() -> Setup {
         None => SessionConfig::default().autoplay,
     };

+    let bind_ips: Vec<std::net::IpAddr> = if opt_present(BIND_IP) {
+        if  let Some(bind_ip) = opt_str(BIND_IP) {
+            let mut ip_addresses: Vec<std::net::IpAddr> =  vec![];
+            let re_ipv4 = Regex::new(r"(\d+\.\d+\.\d+\.\d+)").unwrap();
+            for ip_addresse in bind_ip.split(",") {
+                if re_ipv4.is_match(ip_addresse){
+                    ip_addresses.push(ip_addresse.parse::<std::net::Ipv4Addr>().unwrap().into());
+                } else {
+                    let ip_v6: Vec<&str> = ip_addresse.split(":").collect();
+                    if 8 == ip_v6.len(){
+                        let new_ip_v6: Vec<u16> = ip_v6.iter().map(|&ip_part|
+                            if ip_part.is_empty() {
+                                0
+                            } else {
+                                u16::from_str_radix(ip_part, 16).unwrap()
+                            }).collect();
+                        ip_addresses.push( std::net::Ipv6Addr::new(
+                            new_ip_v6[0],
+                            new_ip_v6[1],
+                            new_ip_v6[2],
+                            new_ip_v6[3],
+                            new_ip_v6[4],
+                            new_ip_v6[5],
+                            new_ip_v6[6],
+                            new_ip_v6[7]
+                        ).into());
+                    } else {
+                        println!("Unable to match string {} to an IPv4 or IPv6 pattern", ip_addresse);
+                    }
+                }
+            }
+            ip_addresses
+        } else {
+            println!("Unable to bind-ip option, default to all interfaces.");
+            vec![]
+        }
+    } else {
+        vec![]
+    };
+
+
     let connect_config = {
         let connect_default_config = ConnectConfig::default();

@@ -1608,6 +1659,7 @@ fn get_setup() -> Setup {
         zeroconf_port,
         player_event_program,
         emit_sink_events,
+        bind_ips,
     }
 }

@@ -1640,6 +1692,7 @@ async fn main() {
             .name(setup.connect_config.name.clone())
             .device_type(setup.connect_config.device_type)
             .port(setup.zeroconf_port)
+            .bind_ips(setup.bind_ips)
             .launch()
         {
             Ok(d) => discovery = Some(d),

Thanks for the hint. Avoid a regex seems like a good idea. The main issue I had with the propose approach is that I am unable to recover if the string cannot be parsed, e.g. 192.168.0.a. This ends in a panic. I think it would be better to print a corresponding message and then bind to all IP addresses, so it doesn't fail.
I tried to resolve this but I was not able to. There is no pattern like try & catch in Rust, which I probably would have used in python or so.  I tried to look for something to replace it but I was unable to get  assert() or parse(), expect() and unwrap() working. Does anybody has a good idea here?
Anyhow removing the regex yields much cleaner code:
@@ -1168,6 +1177,21 @@ fn get_setup() -> Setup {
         None => SessionConfig::default().autoplay,
     };

+    let bind_ips: Vec<std::net::IpAddr> = if opt_present(BIND_IP) {
+        if  let Some(bind_ip) = opt_str(BIND_IP) {
+            let string_ips:  Vec<&str> = bind_ip.split(",").collect();
+            string_ips.iter()
+                .map(|s| s.parse::<std::net::IpAddr>().unwrap())
+                .collect()
+        } else {
+            println!("Unable to bind-ip option, default to all interfaces.");
+            vec![]
+        }
+    } else {
+        vec![]
+    };
+
+
     let connect_config = {
         let connect_default_config = ConnectConfig::default();

You should look into IpAddr::from_str. The Rust idiom for success or failure is returning and doing something with a Result. Welcome to Rust 👍

And and filter_map and map_err are your friends when playing with lists :-)

Alright thanks for the hints. I will read up and try again ;)

I was able to write something up with filter_map and map_err as well as unwrap_or_else(). Looking at the rest of the code unwrap_or_else() seems the way to go and then exiting the program. Hence I would propose:
    let bind_ips: Vec<std::net::IpAddr> = if opt_present(BIND_IP) {
        if  let Some(bind_ip) = opt_str(BIND_IP) {
            let string_ips:  Vec<&str> = bind_ip.split(",").collect();
            string_ips.iter()
                .map(|s| s.trim().parse::<std::net::IpAddr>().unwrap_or_else(|_| {
                    invalid_error_msg(
                        BIND_IP,
                        BIND_IP_SHORT,
                        s,
                        "IPv4 and IPv6 addresses",
                        ""
                    );
                    exit(1);
                }))
                .collect()
        } else {
            println!("Unable to bind-ip option, default to all interfaces.");
            vec![]
        }
    } else {
        vec![]
    };

Continuing in case of an error:
    let bind_ips: Vec<std::net::IpAddr> = if opt_present(BIND_IP) {
        if  let Some(bind_ip) = opt_str(BIND_IP) {
            let string_ips:  Vec<&str> = bind_ip.split(",").collect();
            let mut errors = vec![];
            let ip_addresses = string_ips.into_iter()
                .map(|s| s.trim().parse::<std::net::IpAddr>())
                .filter_map(|r|
                    r.map_err(|e| errors.push(e.to_string())).ok())
                .collect();
            if !errors.is_empty(){
                println!("issue parsing the address errors {:?}, mapped IP addresses {:?} successfull", errors, ip_addresses);
            }
            ip_addresses
        } else {
            println!("Unable to bind-ip option, default to all interfaces.");
            vec![]
        }
    } else {
        vec![]
    };

Looks goo, please feel free to open a PR! :-)
There are some minor things you could tweak, e.g Split is an iterator already, so you don't need to collect() -> into_iter() it.. You could bind_ip.split(",").map(....) but the rest looks good
I hope your enjoying Rust :-)

I have created a PR.
Thanks for the help and advice. So far I like Rust.

Implemented with #1071, @setime  please update the wiki and we can close this! :-)

I updated the wiki :).


Add toggle for map.fitBounds() - closes issue #55

Allow users to easily fit all markers within view on page load
Without bounds
@app.route('/map-unbounded/')
def map_unbounded():
"""Create map with markers out of bounds."""
    locations = []    # long list of coordinates
    map = Map(
        lat=locations[0].latitude,
        lng=locations[0].longitude,
        markers=[(loc.latitude, loc.longitude) for loc in locations]
    )
    return render_template('map.html', map=map)

With bounds
@app.route('/map-bounded/')
def map_bounded():
"""Create map with all markers within bounds."""
    locations = []    # long list of coordinates
    map = Map(
        lat=locations[0].latitude,
        lng=locations[0].longitude,
        markers=[(loc.latitude, loc.longitude) for loc in locations],
        fit_markers_to_bounds = True
    )
    return render_template('map.html', map=map)

Lets include those images and how to on readme.md?

This is so cool! My first PR. 😄

nice! @mattdavis1121 can you do the https://github.com/rochacbruno/Flask-GoogleMaps/issues/57 ? it is easy just include the info from here in README.md file

See #58. Added to the README, but I won't have time to do the example app. Hope that's okay.
Will this trigger a new release? I'm using this package at work, and I'd like to have the new code available in my requirements file.
Thanks!

@mattdavis1121 I'll finish reviewing the PRs and then release by the weekend.

Great! Thanks, Bruno.

@rochacbruno Any update on the release?

@mattdavis1121 released https://pypi.org/project/Flask-GoogleMaps/

@rochacbruno Great! Just installed and everything's working well. Thanks, man.
Any idea why the package doesn't show up in the results of pip freeze? Can't figure it out. I just wrote a SO question about it. https://stackoverflow.com/questions/46105730/why-doesnt-pip-installed-package-show-up-in-pip-freeze


Internet Explorer JS Error 0.9.5

We are having difficulties getting our cappuccino project to run on IE browsers.  We get the following error message, which is incredibly cryptic at best.
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Timestamp: Fri, 18 Nov 2011 19:40:04 UTC
Message: 'object.0' is null or not an object
Line: 3592
Char: 1
Code: 0
URI: http://unity-rc:10088/cps/assets/newcpseditor/Frameworks/Objective-J/Objective-J.js
Steve

Most of the time this is caused by an error in your own code, not in Cappuccino. Unfortunately because of the way ObjJ works sometimes the reported error message is not incredibly useful. Have you tried using the built in debugger in Internet Explorer to break on exceptions and to try and debug the issue? That is where you should start.
On Nov 18, 2011, at 11:47 AM, steverhoades wrote:

We are having difficulties getting our cappuccino project to run on IE browsers.  We get the following error message, which is incredibly cryptic at best.
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Timestamp: Fri, 18 Nov 2011 19:40:04 UTC
Message: 'object.0' is null or not an object
Line: 3592
Char: 1
Code: 0
URI: http://unity-rc:10088/cps/assets/newcpseditor/Frameworks/Objective-J/Objective-J.js
Steve

Reply to this email directly or view it on GitHub:
https://github.com/cappuccino/issues/issues/66

Is it the are that swapping out an earlier Cappuccino (0.9.1?) works but 0.9.5 doesn't?

Thanks for the quick response - i just double checked and it appears that it doesn't work in 0.9.1 or 0.9.5 for IE, It is extremely likely the issue is within our codebase - When I determine the cause I will confirm here.


Revert "[jvm-packages] Add XGBOOST_RABIT_TRACKER_IP_FOR_TEST to set rabit tracker IP."

Reverts dmlc/xgboost#6869

thanks!


doc for rchash is wrong

Context
1.18
Summary
rchash requires the random string to be repeated. This doesn't match the documentation.
Expected behavior
See https://docs.ethswarm.org/docs/bee/working-with-bee/staking/#check-node-performance
Actual behavior
curl http://glow.lan:1635/rchash/10/123456/123456

Possible solution
Fix bee or fix documentation

Also, bee returns "duration":<PHONE_NUMBER>526 in unknown units (nanoseconds?) instead of "Time": "2m54.087909745s" as documented.

Also, bee returns "duration":<PHONE_NUMBER>526 in unknown units (nanoseconds?) instead of "Time": "2m54.087909745s" as documented.

related - https://github.com/ethersphere/bee-docs/issues/530

new docs and api changes with 1.23 will address this


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_272r3rywqy/clone/recipe/meta.yaml:16: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_272r3rywqy/clone/recipe/meta.yaml:21: missing_wheel: For pypi packages, wheel should be present in the host section
WARNING: /tmp/abs_272r3rywqy/clone/recipe/meta.yaml:39: missing_description: The recipe is missing a description
ERROR: /tmp/abs_272r3rywqy/clone/recipe/meta.yaml:39: missing_license_family: The recipe is missing the about/license_family key.
ERROR: /tmp/abs_272r3rywqy/clone/recipe/meta.yaml:39: missing_dev_url: The recipe is missing a dev_url
ERROR: /tmp/abs_272r3rywqy/clone/recipe/meta.yaml:39: missing_documentation: The recipe is missing a doc_url or doc_source_url
Errors were found


Move VIM_SELECTOR_SPEC out of the base EmsRefresh

The VIM_SELECTOR_SPEC is used to filter properties that we care about from the VMware provider to reduce memory usage. It is a very VMware specific construct but was in EmsRefresh::VcUpdates in the main manageiq repository.
This moves the selection spec out of EmsRefresh under ManageIQ::Providers::Vmware::InfraManager::VimSelectorSpec
Depends on: https://github.com/ManageIQ/manageiq-providers-vmware/pull/20

Thanks @durandom
@blomquisg this moves the vim selector spec to the manageiq-providers-vmware repo

:+1:
However, this raises the question:  When can the three files changed in this PR be moved entirely to the vmware repo?

When can the three files changed in this PR be moved entirely to the vmware repo?

Working on it!  Hoping to kill EmsRefresh::VcUpdates completely and replace it with just queueing refreshes for updates and refresh_new_target for creates.


Correct typo in web-app-routing.md

Command: az keyvault certificate show --vault-name <KeyVaultName> -n <KeyVaultCertificateName> ---query "id" --output tsv is wrong with an extra hyphen. Will cause error: unrecognized arguments: ---query id .

Learn Build status updates of commit 89defd4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/aks/web-app-routing.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@jahabibi
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Hi,
This is just a simple typo fix. Can someone review and merge it?
Thanks!

It looks like the author is OOF.
@MGoedtel
Can you review the proposed changes? When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.

@Court72 - Sure, reviewing now.


2557 create market failure transaction

The title is actually a bit of misnomer in that I actually handle the onFailed callback by invalidating the form + messaging since the transaction doesn’t actually get stored on chain (AFAIK).


Trigger a fresh build?

[x] I read the conda-forge documentation and could not find the solution for my problem there.

Issue:
SWMM package is no longer found via conda/mambda (install or search)

Environment (conda list):

Base
$ conda list
# packages in environment at /Users/paul/mambaforge:
#
# Name                    Version                   Build  Channel
brotlipy                  0.7.0           py39h5161555_1003    conda-forge
bzip2                     1.0.8                h3422bc3_4    conda-forge
c-ares                    1.18.1               h3422bc3_0    conda-forge
ca-certificates           2021.10.8            h4653dfc_0    conda-forge
certifi                   2021.10.8        py39h2804cbe_1    conda-forge
cffi                      1.15.0           py39h52b1de0_0    conda-forge
charset-normalizer        2.0.12             pyhd8ed1ab_0    conda-forge
colorama                  0.4.4              pyh9f0ad1d_0    conda-forge
conda                     4.11.0           py39h2804cbe_0    conda-forge
conda-package-handling    1.7.3            py39h5161555_1    conda-forge
cryptography              36.0.1           py39hfb8cd70_0    conda-forge
icu                       69.1                 hbdafb3b_0    conda-forge
idna                      3.3                pyhd8ed1ab_0    conda-forge
krb5                      1.19.2               hd92b7a7_3    conda-forge
libarchive                3.5.2                hc24d6eb_1    conda-forge
libcurl                   7.81.0               h8fe1914_0    conda-forge
libcxx                    12.0.1               h168391b_1    conda-forge
libedit                   3.1.20191231         hc8eb9b7_2    conda-forge
libev                     4.33                 h642e427_1    conda-forge
libffi                    3.4.2                h3422bc3_5    conda-forge
libiconv                  1.16                 h642e427_0    conda-forge
libmamba                  0.21.2               h4676060_0    conda-forge
libmambapy                0.21.2           py39h1b2844e_0    conda-forge
libnghttp2                1.46.0               he4cd7f6_0    conda-forge
libsolv                   0.7.19               hccf11d3_5    conda-forge
libssh2                   1.10.0               hb80f160_2    conda-forge
libxml2                   2.9.12               hedbfbf4_1    conda-forge
libzlib                   1.2.11            hee7b306_1013    conda-forge
lz4-c                     1.9.3                hbdafb3b_1    conda-forge
lzo                       2.10              h642e427_1000    conda-forge
mamba                     0.21.2           py39hde45b87_0    conda-forge
ncurses                   6.3                  hc470f4d_0    conda-forge
openssl                   1.1.1l               h3422bc3_0    conda-forge
pip                       22.0.3             pyhd8ed1ab_0    conda-forge
pybind11-abi              4                    hd8ed1ab_3    conda-forge
pycosat                   0.6.3           py39h5161555_1009    conda-forge
pycparser                 2.21               pyhd8ed1ab_0    conda-forge
pyopenssl                 22.0.0             pyhd8ed1ab_0    conda-forge
pysocks                   1.7.1            py39h2804cbe_4    conda-forge
python                    3.9.10          hd16f9c5_2_cpython    conda-forge
python_abi                3.9                      2_cp39    conda-forge
readline                  8.1                  hedafd6a_0    conda-forge
reproc                    14.2.3               h3422bc3_0    conda-forge
reproc-cpp                14.2.3               hbdafb3b_0    conda-forge
requests                  2.27.1             pyhd8ed1ab_0    conda-forge
ruamel_yaml               0.15.80         py39h5161555_1006    conda-forge
setuptools                60.9.2           py39h2804cbe_0    conda-forge
six                       1.16.0             pyh6c4a22f_0    conda-forge
sqlite                    3.37.0               h72a2b83_0    conda-forge
tk                        8.6.12               he1e0b03_0    conda-forge
tqdm                      4.62.3             pyhd8ed1ab_0    conda-forge
tzdata                    2021e                he74cb21_0    conda-forge
urllib3                   1.26.8             pyhd8ed1ab_1    conda-forge
wheel                     0.37.1             pyhd8ed1ab_0    conda-forge
xz                        5.2.5                h642e427_1    conda-forge
yaml                      0.2.5                h3422bc3_2    conda-forge
yaml-cpp                  0.6.3                hc88da5d_4    conda-forge
zlib                      1.2.11            hee7b306_1013    conda-forge
zstd                      1.5.2                h861e0a7_0    conda-forge

Details about  conda and system ( conda info ):
Running an up-to-date OS X on M1 silicon (which I suspect is the issue)

$ conda info
     active environment : base
    active env location : /Users/paul/mambaforge
            shell level : 1
       user config file : /Users/paul/.condarc
 populated config files : /Users/paul/mambaforge/.condarc
                          /Users/paul/.condarc
          conda version : 4.11.0
    conda-build version : not installed
         python version : 3.9.10.final.0
       virtual packages : __osx=12.2.1=0
                          __unix=0=0
                          __archspec=1=arm64
       base environment : /Users/paul/mambaforge  (writable)
      conda av data dir : /Users/paul/mambaforge/etc/conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/conda-forge/osx-arm64
                          https://conda.anaconda.org/conda-forge/noarch
          package cache : /Users/paul/mambaforge/pkgs
                          /Users/paul/.conda/pkgs
       envs directories : /Users/paul/mambaforge/envs
                          /Users/paul/.conda/envs
               platform : osx-arm64
             user-agent : conda/4.11.0 requests/2.27.1 CPython/3.9.10 Darwin/21.3.0 OSX/12.2.1
                UID:GID : 501:20
             netrc file : None
           offline mode : False

It seems that the 5.2.1 version is no longer available upstream, only older versions (https://github.com/OpenWaterAnalytics/Stormwater-Management-Model/releases).
If I update the recipe to the last stable version (5.1.13), it will be a regression, and I don't know how conda will handle it.

Interesting. Thanks for taking a look.

@ocefpaf Looks like the upstream repo has walked back some version numbers and the tag that this recipe was building is gone (5.2.1).
See https://github.com/OpenWaterAnalytics/Stormwater-Management-Model/tags
Any advice on triggering a new build?
Best I can tell, we could trigger a fresh 5.1.13 build to get an Mac/ARM64 build. Then other architectures would still install 5.2.1 (built from the now non-existent release) by default.
In my mind, that's acceptable while upstream works on their new release and folks on new Macs get at least something.

@ocefpaf to be clear, by "older" you mean a lower semantic version and not necessarily an earlier release date, right?

Yes. Sorry for the confusion. You see why I had the screaming emoji there. Only folks that are looking into the code repo will know that. Everybody else won't even be able to install the newer package when updating b/c conda will pick up the older one due to the higher version,

Looks like there is now semantically more current release:
https://github.com/pyswmm/Stormwater-Management-Model/releases/tag/v5.2.3
I'll read back through the conda-forge docs to see about triggering a fresh build based on that.


Set same value

Color objects are able to mutate even thought the values given are not different than existing ones, as in the following example:
var color = Color('#abc');
color.hexString(); // -> '#AABCC'
color.hue(color.hue()).hexString() // -> '#A9BACB'

I've added a new test, and a patch on Color.prototype.setChannel() that gets the test to pass.

Hum weird. Thanks for the fix. I will try to cut a new release soon with immutable colors, cause mutation produce a lot of unexpected behavior (ref #56)


[1.18.2 Feature] Option to Disable New Chest Tiers

Would love to have a option available in config to disable the new update's feature on randomizing tiers on gear found in chests. This way I can make it how it existed prior to this update, basing it only on gear crafted/created.

Added with https://github.com/Globox1997/tiered/commit/e15666aab478ba3681302b5eed358b78064b369f


[fix] limit scope

The ReduceToOneCharacter function was a global function, but there was only one place where it was called, so we restricted its scope.

@nickspoons
reviewdog has failed, but this warning may false alarm.
accessModifierLen is defined.

@nickspoons
Thanks.
I fixed.


Add Verbal Validation Field and Text Field to Helper App (ARIG 12.12.19)

Add a Verbal Validation Field and Text Box in Helper App so that research assistants may provide qualitative notes and a validation on hard to match cases.
Text Box: "Validation Notes"
Verbal Validation Field:  Drop Down or Radio Button
Options = 1, Validated
0, Not validated
If we could potentially see a screenshot of this before it goes live?
Thanks!

Hi Mike, we added this feature to REDCap. 🙂  It's no longer needed in Helper App!


cmd/cgo: -godefs doesn't work with structures fields inside another structure.

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version devel +c814ac4 Thu Jul 19 21:30:27 2018 +0000 linux/amd64
-> go1.11beta2
Does this issue reproduce with the latest release?
No, it wasn't the case in go1.11beta1
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/chigotc/.cache/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/chigotc/go"
GOPROXY=""
GORACE=""
GOROOT="/home/chigotc/go/golangMaster"
GOTMPDIR=""
GOTOOLDIR="/home/chigotc/go/golangMaster/pkg/tool/linux_amd64"
GCCGO="/usr/bin/gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build447974166=/tmp/go-build -gno-record-gcc-switches"
What did you do?
I uses go tool cgo -godefs godefs.go  with godefs.go :
package godefs
/*
typedef struct st_timespec {
int tv_sec;
int tv_nsec;
} st_timespec_t;
struct stat {
int var1;
st_timespec_t atim;
int var2;
};
*/
import "C"
type Stat_t C.struct_stat
type StTimespec_t C.st_timespec_t
What did you expect to see?
// Code generated by cmd/cgo -godefs; DO NOT EDIT.
// cgo -godefs godefs.go
package godefs
type Stat_t struct {
Var1	int32
Atim	StTimespec_t
Var2	int32
}
type StTimespec_t struct {
Sec	int32
Nsec	int32
}
What did you see instead?
// Code generated by cmd/cgo -godefs; DO NOT EDIT.
// cgo -godefs godefs.go
package godefs
type Stat_t struct {
Var1	int32
Atim	_Ctype_struct_st_timespec
Var2	int32
}
type StTimespec_t struct {
Sec	int32
Nsec	int32
}
If the new feature "recordTypedefs" is removed, everything is alright:
Commenting this line: https://github.com/golang/go/blob/master/src/cmd/cgo/gcc.go#L567, is enough to bypass this bug.

Pretty sure https://golang.org/cl/125995 fixes this.


Lavaplayer Version: 2.1.2YouTube Source Version: youtube:v2:1.3.0 IP rotation set up

I am trying to set up IP rotation for YoutubeAudioSourceManager but I'm encountering an issue where I cannot import AbstractRoutePlanner or any classes from the extensions folder.
Dependencies in build.gradle:
dependencies {
implementation 'dev.arbjerg:lavaplayer:2.1.2'
implementation 'com.github.walkyst:lavaplayer-youtube-v2:1.3.0'
implementation("net.dv8tion:JDA:5.0.0-beta.24")
implementation("ch.qos.logback:logback-classic:1.5.6")

}
repositories {
mavenCentral()
maven {
url 'https://m2.dv8tion.net/releases'
}
maven {
url 'https://jitpack.io'
}
maven { url = "https://maven.lavalink.dev/releases" }
}

com.github.walkyst:lavaplayer-youtube-v2:1.3.0
what is this...

com.github.walkyst:lavaplayer-youtube-v2:1.3.0 what is this...

aorr i made a mistake when copying the dependencies
it should be :
implementation("dev.lavalink.youtube:v2:1.3.0") "it is the new youtube sorce
BTW
when i use
implementation 'com.github.devoxin:lavaplayer:1.9.1'
I can import AbstractRoutePlanner whithout any isseus

With dev.arbjerg.lavaplayer you might need to import the lavaplayer-ext-youtube-rotator module.
https://maven.lavalink.dev/#/releases/dev/arbjerg/lavaplayer-ext-youtube-rotator

With dev.arbjerg.lavaplayer you might need to import the lavaplayer-ext-youtube-rotator module separately. https://maven.lavalink.dev/#/releases/dev/arbjerg/lavaplayer-ext-youtube-rotator

fixed the issue Thanks!


Improve search results

Improve general search results and also no matching search results.

Preview:

Link examples:
https://www.twitch.tv/search?term=world of warcraft
https://www.twitch.tv/search?term=forsen


tcp input instead of serial

Hello,
Is it possible to use pyubx2 with a tcp input instead of serial?
My applications already use the serial port as input str2str -in serial://ttyACM0:115200:8:n:1#ubx -out tcpsvr://:5015 and I would like to connect pyubx2 on the localhost:5015
thanks!

Hi @jancelin Sorry, it's not currently possible and there are no plans to add this functionality in the foreseeable future.
If you're using a Posix platform, you should be able to use the standard ser2net and/or socat utilities to map a TCP socket to a serial stream or vice versa. Others have done this successfully.
As it happens, there is a similar issue on the backlog to add this functionality to the GUI application PyGPSClient (https://github.com/semuconsulting/PyGPSClient/issues/18), but I have no timeframe on this at present.

Ok
thanks for the explanation

Hi @jancelin
If you don't mind I'd actually like to keep this open for now, as it's a reasonable feature request. Just not sure when I'll have the time to implement.
It would probably be very simple in the first instance (i.e. no encryption or authentication) but I may look to offer enhanced functionalty at a later date.


Rectangular 3d surface

Hi, i'm using your library to create a surface with axes. I simply mixed up your examples of the scatterplot  and 3d surface, and everything works fine. I then tried to create a "rectangular" surface/grid with some rows and points per row (N of points per row != N of rows), but failed. I was just wondering if it was possible to create a rectangular grid.
EDIT: i noticed that when you create and render a plane with Nrows > N points per row, the code just breaks, while the vice-versa creates a distoted plane. You can try it by modifying your  3d surface plot parameters.
Your example

Hey, this is a bug. I will fix this in the next release. Thanks for the hint !


🛑 ENOENT: no such file or directory, stat '.../schema.graphql'

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
16.18.1
Amplify CLI Version
16.18.1
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Describe the bug
For my schema, I organised all of them in different files, so I have users.graphql, courses.graphql, etc... I don't have a "schema.graphql".
I have just recently updated the amplify version, and I started getting the following message When I finish pushing my changes:
🛑 ENOENT: no such file or directory, open '/Users/..../myproject/amplify/backend/api/GraphQLAPI/schema.graphql'
Resolution: Please report this issue at https://github.com/aws-amplify/amplify-cli/issues and include the project identifier from: 'amplify diagnose --send-report'
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
🛑 ENOENT: no such file or directory, stat '/Users/..../myproject/amplify/backend/api/GraphQLAPI/schema.graphql'
Expected behavior
I shouldn't get this message. The schema is there, just separately in different files.
Reproduction steps

Create schema for your models without the default "schema.graphl"

Project Identifier
No response
Log output

# Put your logs below this line

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hi @rafaelfaria and @johnf, The engineering team is actively investigating the specific #1074 issue as we have been able to reproduce it in the latest CLI version.

@josefaidt what does it mean "as not planned"? As in, not going to fix this?


analyzer 0.40.x support in floor_generator

Unfortunately I cannot use analyzer 0.40.x:
Because floor_generator 0.14.0 depends on analyzer ^0.39.4 and
no versions of floor_generator match >0.14.0 <0.15.0, floor_generator ^0.14.0 requires analyzer ^0.39.4.

The next release will contain updated dependencies ✔


Document clock SELECTED registers in headers and SVD

See https://github.com/raspberrypi/pico-sdk/issues/51

This also includes the SVD vtorPresent field for #22


Enhanced Styling of BoxApiInfo Components,  fixes #65

Description
Issue #65: Enhanced Styling of BoxApiInfo Component
The styling of the BoxApiInfo component are improved to enhance its visual appeal and user experience.
Reviewed and updated the Material-UI styles applied to the component.
Adjusted margins, and padding, or added styling enhancement.
Related Issues
List any related issues or pull requests that are being addressed.
Checklist

[x] I have tested my changes locally.
[x] I have added necessary documentation or updated existing documentation.
[x] My code follows the project's coding conventions and style guidelines.
[x] All tests pass successfully.
[x] I have added/updated relevant unit tests.

Additional Notes
Include any additional notes or context about your pull request.

Good morning! Yes, I would be happy to do that!
On Sun, 14 Jan 2024 at 22:35, Curtis Thomas @.***> wrote:

@Curtis-Thomas requested changes on this pull request.
Hi, good job with the changes.
Please reduce the margin bottom, it is too big and pushes the endpoints off the screen in some cases:
image.png (view on web)
If this change is accepted the endpoint boxes will also need an adjustment to match the style. Do you think this is something you would like to do?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

I look forward into it
On Wed, 17 Jan 2024 at 22:58, Curtis Thomas @.***>
wrote:

@.**** commented on this pull request.
I still think the bottom padding is too much:
—
Reply to this email directly, view it on GitHub
https://github.com/Curtis-Thomas/free-api-list-with-react/pull/112#pullrequestreview-1827818766,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4ZNXYGTIK5PM6CZMSUY363YPAC4FAVCNFSM6AAAAABBQNFRASVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTQMRXHAYTQNZWGY
.
You are receiving this because you authored the thread.Message ID:
@.***
com>

Awesome, thanks!
On Thu, 18 Jan 2024 at 14:56, Curtis Thomas @.***>
wrote:

Merged #112
https://github.com/Curtis-Thomas/free-api-list-with-react/pull/112 into
main.
—
Reply to this email directly, view it on GitHub
https://github.com/Curtis-Thomas/free-api-list-with-react/pull/112#event-11522618116,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4ZNXYEWGRLGCVROR2J6QIDYPDTGDAVCNFSM6AAAAABBQNFRASVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGUZDENRRHAYTCNQ
.
You are receiving this because you authored the thread.Message ID:
<Curtis-Thomas/free-api-list-with-react/pull/112/issue_event/11522618116@
github.com>


detroy player with plugin

please see code for the problem
var destroyPlayer = Clappr.ContainerPlugin.extend({
  bindEvents: function() {
    this.listenTo(this.container, Clappr.Events.CONTAINER_ERROR, this.onerror);
  },
  onerror: function(e) {
    // this.destroy(); # player not destroyed
    // this.container.destroy() # only some part destroyed
    // right code ?
  }
});

@ewwink if you wants to destroy player instance, simply call the player destroy() method. It cleanup the player instance and remove itself from the DOM. For more details, refers to player api documentation.
BTW, in your code example, this is not the player instance, it is your container plugin instance.

you mean like this?
var player = new Clappr.Player({source: "http://your.video/here.mp4", parentId: "#player"});
player.destroy()

but I want do it with plugin.

Using a player plugin to destroy the player instance seems to be a bad design (in my opinion).
Anyway, if you take a loot at player destroy method, you can see it first unbind player events calling player instance stopListening() method, then it call core instance destroy() method.
You can access easyly access core instance from your plugin instance, but for player instance you may needs to pass the reference to your plugin (maybe defining an external interface plugin method to inject player instance when created). There is maybe another way, but i missed it.

it seem the easiest way is using zepto
onerror: function(e) {
      $('#'+this.options.parentElement.id).html('<video src=...')
}

one more question, is there way to fallback from clappr to native <video> tag on android? I have .m3u8 file which CORS is not allowed but it work with <video> tag and clappr not, I tried adding recycleVideo and playInline but still not work.

nevermind I will use Clappr.Browser.isMobile instead and @kslimani thanks for your support.


Migrate to java.time lib instead of joda-time

Joda-time has been used till moving to Java 8. For now, these two time libraries are used together. It will make sense finally to move everywhere to only one lib - java.time - as a standard Java time library (see mail list discussion: https://lists.apache.org/thread.html/b10f6f9daed44f5fa65e315a44b68b2f57c3e80225f5d549b84918af@%3Cdev.beam.apache.org%3E).

Since this migration will introduce breaking API changes, then we should address it to 3.0 release.
Imported from Jira BEAM-5530. Original Jira may contain additional context.
Reported by: aromanenko.

Would a transitional support of both in 2.x be envisionable?

If someone puts together a plan that can do it without breaking changes - or at least very few - and sends the design to the dev@ list, I'm sure it would create a useful discussion.


Unsupported devices causing crashes/hangs

Devices with issues: Avermedia GC573 and NDI Virtual Cam.
the GC573 causes a crash and the NDI source causes a freeze. Is it possible to catch an unsupported device before it causes an issue? Or maybe hide these devices entirely?
We are using VideoKit as a runtime tool where the end user can selected devices. So crashes and freezes aren't ideal.
To Reproduce

Download NDI Tools
Select a device labeled "NDI WebCam Video"
Or try a different unsupported device like mentioned above.

Alpha 18
Windows 11
Unity 2022.3.9

@nickhudson4 can you share the Editor logs from the crash and hang?

EditorFreeze.log
It allows me to switch to the device. The freeze happens when stopping it. Specifically at this plugin call public static extern Status StopRunning (this IntPtr device);
EditorCrash.log

@olokobayusuf  the latest update (0.0.22) should no longer result in a crash.

@olokobayusuf This did fix the crashes with the virtual cams. However, still receiving crashes with the Avermedia GC573. Here is the crash log
Player.log


Add new C++ mangle syntax.

See https://github.com/dlang/dmd/pull/8667

Not sure if the CI builds the docs to look at? I couldn't build it on my system. The win32.mak just doesn't work and the posix.mak requires some specific folder layout from the looks of it. Was looking for a folder outside it's own ../dmd/*.

!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on .generated/dlangspec.log.
posix.mak:544: recipe for target '/dev/shm/dtest/work/repo/dlang.org/web/dlangspec.pdf' failed
make: *** [/dev/shm/dtest/work/repo/dlang.org/web/dlangspec.pdf] Error 1
fatal: 'refs/ae-sys-d-cache/website-5648c9a45e689256e58981f3b450079e30eb50fd-f2baf3c634d68ccbd27bae18dea84bbd' - not a valid ref

The error messages are pretty horrible...

Please squash commits when done

Yah I don't know why this isn't building, the error message is useless and the CI takes forever to complete.

@look-at-me that's due to a bad version of dub being used to build stuff by the CI, please rebase and it should go away.

Rebased

Could use a squash. Do you know why it fails ?

Close because obsolete. More or less the same has been added by another PR


Generate documentation

Polars often lacks documentation around the various enums/structs/functions that exist; since ocamldoc is a thing, we probably want to write things down and ensure things are properly documented.
I also wonder if it's possible to have doctest-style expect tests on the OCaml side.

I also wonder if it's possible to have doctest-style expect tests on the OCaml side.

Apparently MDX supports this, sweet!

I've started working on this in https://github.com/mt-caret/polars-ocaml/pull/37, but one thing I'm sad about is that ocamlformat doesn't apply to code blocks in MDX, which means that it's very difficult to maintain a consistent coding style within these tests: https://github.com/ocaml-ppx/ocamlformat/issues/1351


Update flyway-core to 9.19.1

About this PR
📦 Updates org.flywaydb:flyway-core from 7.15.0 to 9.19.1 ⚠
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.flywaydb", artifactId = "flyway-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.flywaydb", artifactId = "flyway-core" }
}]

labels: library-update, early-semver-major, semver-spec-major, commit-count:1

Superseded by #707.


Created test setup environment and fixed test(s)

I added a Gradle build as well.

Won't AGPL conflict with jetcd's apache license?

I think all of the dependencies use the Apache License.  What uses AGPL?

@at88mph thanks very much, I will do a deep review this weekend.

@at88mph what is the purpose of gradle in addition to maven here? Anything not possible with maven?
I think we should use only one build system.

I agree.  I was trying to get a handle on why the tests seemed to run in parallel, and I was testing to see if Maven was the issue since they failed every three or four runs.
I will remove the Gradle files.
Dustin N. Jenkins
Tel/Tél:<PHONE_NUMBER> | facsimile/télécopieur:<PHONE_NUMBER> |<EMAIL_ADDRESS><EMAIL_ADDRESS>National Research Council Canada | 5071 West Saanich Rd, Victoria BC. V9E 2E7
Conseil national de recherches Canada | 5071, ch. West Saanich, Victoria (C.-B) V9E 2E7
Government of Canada | Gouvernement du Canada

On Nov 11, 2016, at 06:26, Luca Burgazzoli<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
@at88mph https://github.com/at88mph what is the purpose of gradle in addition to maven here? Anything not possible with maven?
I think we should use only one build system.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/coreos/jetcd/pull/58#issuecomment-259967981, or mute the thread https://github.com/notifications/unsubscribe-auth/ABmC5NVOkjecKeJ7N3qwGwlgS41qLOy3ks5q9HsQgaJpZM4KtNq0.

closing the testing framework is added.


Wayland

Any wayland support soon?

I don't use Wayland, so it's unlikely to be something I work on in the medium term.
I know there is some X11/Wayland compatiblity shims... it might be possible to have the bar render using XCB, but running on top of Wayland? I imagine Wayland is not going to be using EHWM, so you'd probably need to create your own widgets to interface with your window manager. I am not sure if there's an equivalent to the EHWM standard on Wayland.

I hope you don't mind, but I'm going to close this as I don't plan on supporting Wayland in the future.


Remove warnings for vars not modified

This particular test was using vars but then not mutating them, which
was causing Xcode to issue warnings.

We left the var here because there are solutions that mutate by using an indirect enum. I don't want to disallow solution using value types.

Cool, what would you think about ignoring the file for warnings then, something like:
http://stackoverflow.com/questions/6921884/in-xcode-how-to-suppress-all-warnings-in-specific-source-files

that sounds good. I don't think it works with swift? haven't tried it.

Darn, guess it was an Obj-C file I did this for. :\
http://stackoverflow.com/questions/31540446/how-to-silence-a-warning-in-swift-2-0/32861678#32861678

I guess we could implement that particular problem using enums to get rid of the warning in our Xcode project.