Disable hwloc CLI tools and tests on Windows

Fixes https://github.com/HadrienG2/hwlocality/issues/87 by not compiling CLI tools and tests that are not needed for hwlocality's use case anyway.

I did a quick search before submitting a PR and wasn't able to find it. I'm not familiar with autotools though, so I might have missed something fairly obvious.

Branch is out of date. Should I update it or will you merge as is?

You will want to generate the configure script (see hwloc docs) and then run ./configure --help. This will tell you which configuration options are available.

Have not seen anything relevant in help message on Linux:

`configure' configures hwloc 2.8.1rc1-git to adapt to many kinds of systems.

Usage: ./configure [OPTION]... [VAR=VALUE]...

To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE.  See below for descriptions of some of the useful variables.

Defaults for the options are specified in brackets.

Configuration:
  -h, --help              display this help and exit
      --help=short        display options specific to this package
      --help=recursive    display the short help of all the included packages
  -V, --version           display version information and exit
  -q, --quiet, --silent   do not print `checking ...' messages
      --cache-file=FILE   cache test results in FILE [disabled]
  -C, --config-cache      alias for `--cache-file=config.cache'
  -n, --no-create         do not create output files
      --srcdir=DIR        find the sources in DIR [configure dir or `..']

Installation directories:
  --prefix=PREFIX         install architecture-independent files in PREFIX
                          [/usr/local]
  --exec-prefix=EPREFIX   install architecture-dependent files in EPREFIX
                          [PREFIX]

By default, `make install' will install all the files in
`/usr/local/bin', `/usr/local/lib' etc.  You can specify
an installation prefix other than `/usr/local' using `--prefix',
for instance `--prefix=$HOME'.

For better control, use the options below.

Fine tuning of the installation directories:
  --bindir=DIR            user executables [EPREFIX/bin]
  --sbindir=DIR           system admin executables [EPREFIX/sbin]
  --libexecdir=DIR        program executables [EPREFIX/libexec]
  --sysconfdir=DIR        read-only single-machine data [PREFIX/etc]
  --sharedstatedir=DIR    modifiable architecture-independent data [PREFIX/com]
  --localstatedir=DIR     modifiable single-machine data [PREFIX/var]
  --runstatedir=DIR       modifiable per-process data [LOCALSTATEDIR/run]
  --libdir=DIR            object code libraries [EPREFIX/lib]
  --includedir=DIR        C header files [PREFIX/include]
  --oldincludedir=DIR     C header files for non-gcc [/usr/include]
  --datarootdir=DIR       read-only arch.-independent data root [PREFIX/share]
  --datadir=DIR           read-only architecture-independent data [DATAROOTDIR]
  --infodir=DIR           info documentation [DATAROOTDIR/info]
  --localedir=DIR         locale-dependent data [DATAROOTDIR/locale]
  --mandir=DIR            man documentation [DATAROOTDIR/man]
  --docdir=DIR            documentation root [DATAROOTDIR/doc/hwloc]
  --htmldir=DIR           html documentation [DOCDIR]
  --dvidir=DIR            dvi documentation [DOCDIR]
  --pdfdir=DIR            pdf documentation [DOCDIR]
  --psdir=DIR             ps documentation [DOCDIR]

Program names:
  --program-prefix=PREFIX            prepend PREFIX to installed program names
  --program-suffix=SUFFIX            append SUFFIX to installed program names
  --program-transform-name=PROGRAM   run sed PROGRAM on installed program names

X features:
  --x-includes=DIR    X include files are in DIR
  --x-libraries=DIR   X library files are in DIR

System types:
  --build=BUILD     configure for building on BUILD [guessed]
  --host=HOST       cross-compile to build programs to run on HOST [BUILD]
  --target=TARGET   configure for building compilers for TARGET [HOST]

Optional Features:
  --disable-option-checking  ignore unrecognized --enable/--with options
  --disable-FEATURE       do not include FEATURE (same as --enable-FEATURE=no)
  --enable-FEATURE[=ARG]  include FEATURE [ARG=yes]
  --enable-silent-rules   less verbose build output (undo: "make V=1")
  --disable-silent-rules  verbose build output (undo: "make V=0")
  --enable-dependency-tracking
                          do not reject slow dependency extractors
  --disable-dependency-tracking
                          speeds up one-time build
  --enable-shared[=PKGS]  build shared libraries [default=yes]
  --enable-static[=PKGS]  build static libraries [default=no]
  --enable-fast-install[=PKGS]
                          optimize for fast installation [default=yes]
  --disable-libtool-lock  avoid locking (might break parallel builds)
  --enable-embedded-mode  Using --enable-embedded-mode puts the HWLOC into
                          "embedded" mode. The default is
                          --disable-embedded-mode, meaning that the HWLOC is
                          in "standalone" mode.
  --enable-debug          Using --enable-debug enables various hwloc
                          maintainer-level debugging controls. This option is
                          not recomended for end users.
  --enable-doxygen        enable support for building Doxygen documentation
                          (note that this option is ONLY relevant in developer
                          builds; Doxygen documentation is pre-built for
                          tarball builds and this option is therefore ignored)
  --disable-readme        disable the updating of the top-level README file
                          from the HTML documentation index
  --disable-picky         When in developer checkouts of hwloc and compiling
                          with gcc, the default is to enable maximum compiler
                          pickyness. Using --disable-picky or --enable-picky
                          overrides any default setting
  --disable-cairo         Disable the Cairo back-end of hwloc's lstopo command
  --disable-cpuid         Disable the cpuid-based architecture specific
                          support (x86 component)
  --disable-libxml2       Do not use libxml2 for XML support, use a custom
                          minimalistic support
  --disable-io            Disable I/O discovery build entirely (PCI, LinuxIO,
                          CUDA, OpenCL, NVML, RSMI, LevelZero, GL) instead of
                          only disabling it at runtime by default
  --disable-pci           Disable the PCI device discovery build (instead of
                          only disabling PCI at runtime by default)
  --enable-32bits-pci-domain
                          Enable 32 bits PCI domains (domains > 16bits are
                          ignored by default). WARNING: This breaks the
                          library ABI, don't enable unless really needed.
  --disable-opencl        Disable the OpenCL device discovery build (instead
                          of only disabling OpenCL at runtime by default)
  --disable-cuda          Disable the CUDA device discovery build using
                          libcudart (instead of only disabling CUDA at runtime
                          by default)
  --disable-nvml          Disable the NVML device discovery build (instead of
                          only disabling NVML at runtime by default)
  --disable-rsmi          Disable the ROCm SMI device discovery
  --disable-levelzero     Disable the oneAPI Level Zero device discovery
  --disable-gl            Disable the GL display device discovery (instead of
                          only disabling GL at runtime by default)
  --disable-libudev       Disable the Linux libudev
  --enable-plugins=name,...
                          Build the given components as dynamically-loaded
                          plugins
  --disable-plugin-dlopen Do not use dlopen for loading plugins.
  --disable-plugin-ltdl   Do not use ltdl for loading plugins.
  --enable-visibility     enable visibility feature of certain
                          compilers/linkers (default: enabled on platforms
                          that support it)
  --enable-netloc         The Netloc functionality is disabled by default.
                          Using --enable-netloc will cause configure to abort
                          if Netloc cannot be build (e.g., not supported on
                          your platform).

Optional Packages:
  --with-PACKAGE[=ARG]    use PACKAGE [ARG=yes]
  --without-PACKAGE       do not use PACKAGE (same as --with-PACKAGE=no)
  --with-pic[=PKGS]       try to use only PIC/non-PIC objects [default=use
                          both]
  --with-aix-soname=aix|svr4|both
                          shared library versioning (aka "SONAME") variant to
                          provide on AIX, [default=aix].
  --with-gnu-ld           assume the C compiler uses GNU ld [default=no]
  --with-sysroot[=DIR]    Search for dependent libraries within DIR (or the
                          compiler's sysroot if not specified).
  --with-hwloc-symbol-prefix=STRING
                          STRING can be any valid C symbol name. It will be
                          prefixed to all public HWLOC symbols. Default: ""
                          (no prefix)
  --with-cuda-version=<version>
                          Specify the CUDA version (e.g. 11.2) for selecting
                          the appropriate pkg-config file
  --with-cuda=<dir>       Specify the CUDA installation directory, used for
                          NVIDIA NVML and OpenCL too. If a non-existent
                          directory is given, all dependencies installed by
                          CUDA are disabled (CUDA, NVML and NVIDIA OpenCL).
  --with-rocm-version=<version>
                          Specify the ROCm version (e.g. 4.2.0) for selecting
                          the default ROCm installation path (e.g.
                          /opt/rocm-4.2.0)
  --with-rocm=<dir>       Specify the ROCm installation directory
  --with-hwloc-plugins-path=dir:...
                          Colon-separated list of plugin directories. Default:
                          "$prefix/lib/hwloc". Plugins will be installed in
                          the first directory. They will be loaded from all of
                          them, in order.
  --with-x                use the X Window System

Some influential environment variables:
  CC          C compiler command
  CFLAGS      C compiler flags
  LDFLAGS     linker flags, e.g. -L<lib dir> if you have libraries in a
              nonstandard directory <lib dir>
  LIBS        libraries to pass to the linker, e.g. -l<library>
  CPPFLAGS    (Objective) C/C++ preprocessor flags, e.g. -I<include dir> if
              you have headers in a nonstandard directory <include dir>
  LT_SYS_LIBRARY_PATH
              User-defined run-time library search path.
  CXX         C++ compiler command
  CXXFLAGS    C++ compiler flags
  CXXCPP      C++ preprocessor
  HWLOC_MS_LIB
              Path to Microsoft's Visual Studio `lib' tool
  CUDA_VERSION
              The CUDA version (e.g. 11.2) for selecting the appropriate
              pkg-config file
  ROCM_VERSION
              The ROCm version (e.g. 4.2.0) for selecting the default ROCm
              installation path (e.g. /opt/rocm-4.2.0)
  PKG_CONFIG  path to pkg-config utility
  HWLOC_PCIACCESS_CFLAGS
              C compiler flags for PCIACCESS, overriding pkg-config
  HWLOC_PCIACCESS_LIBS
              linker flags for PCIACCESS, overriding pkg-config
  HWLOC_CUDA_CFLAGS
              C compiler flags for CUDA, overriding pkg-config
  HWLOC_CUDA_LIBS
              linker flags for CUDA, overriding pkg-config
  HWLOC_CUDART_CFLAGS
              C compiler flags for CUDART, overriding pkg-config
  HWLOC_CUDART_LIBS
              linker flags for CUDART, overriding pkg-config
  HWLOC_LEVELZERO_CFLAGS
              C compiler flags for LEVELZERO, overriding pkg-config
  HWLOC_LEVELZERO_LIBS
              linker flags for LEVELZERO, overriding pkg-config
  XMKMF       Path to xmkmf, Makefile generator for X Window System
  CPP         C preprocessor
  HWLOC_LIBXML2_CFLAGS
              C compiler flags for LIBXML2, overriding pkg-config
  HWLOC_LIBXML2_LIBS
              linker flags for LIBXML2, overriding pkg-config
  DOXYGEN     Location of the doxygen program (required for building the hwloc
              doxygen documentation)
  PDFLATEX    Location of the pdflatex program (required for building the
              hwloc doxygen documentation)
  MAKEINDEX   Location of the makeindex program (required for building the
              hwloc doxygen documentation)
  FIG2DEV     Location of the fig2dev program (required for building the hwloc
              doxygen documentation)
  GS          Location of the gs program (required for building the hwloc
              doxygen documentation)
  EPSTOPDF    Location of the epstopdf program (required for building the
              hwloc doxygen documentation)
  W3M         Location of the w3m program (required to building the top-level
              hwloc README file)
  LYNX        Location of the lynx program (required to building the top-level
              hwloc README file)
  HWLOC_CAIRO_CFLAGS
              C compiler flags for CAIRO, overriding pkg-config
  HWLOC_CAIRO_LIBS
              linker flags for CAIRO, overriding pkg-config
  DIFF        diff tool
  ARCHIVEMOUNT
              Location of the archivemount program (for loading archive
              topology in tools)
  HWLOC_NUMA_CFLAGS
              C compiler flags for NUMA, overriding pkg-config
  HWLOC_NUMA_LIBS
              linker flags for NUMA, overriding pkg-config

Use these variables to override the choices made by `configure' or to help
it to find libraries and programs with nonstandard names/locations.

Report bugs to <https://github.com/open-mpi/hwloc/issues>.

There is embedded mode, but it builds libhwloc_embedded.la file and a bunch of object files instead of static library :confused:

Thanks for the investigation! :+1:


fix(Key): update iconW and iconH to iconWidth and iconHeight

Description

BLOCKED BY #356 (console warnings will not work correctly until that PR goes in)
Updates all instances of iconW and iconH in Key to iconWidth and iconHeight via the aliasing to ensure the previous property names still work but throw a deprecation warning if used.
References

Testing

In the Key story's template, try setting the style of iconW and iconWidth, as well as iconH and iconHeight, and observe in the console that there are deprecation warnings for the old property names, but that all 4 still appropriately apply the new style. For example:
          style: {
            iconW: 100,
            iconH: 100
          }

vs
          style: {
            iconWidth: 200,
            iconHeight: 200
          }

and the warning:
The style property "iconW" is deprecated and will be removed in a future release. Please use "iconWidth" instead.

Automation

Checklist

[ ] all commented code has been removed
[ ] any new console issues have been resolved
[ ] code linter and formatter has been run
[ ] test coverage meets repo requirements
[ ] PR name matches the expected semantic-commit syntax

Test Execution Failed.

:tada: This PR is included in version @lightningjs/ui-components-v2.12.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Provide a function to create a group directly into an administrative unit

We'd like to provide an additional function on the AdministrativeUnitsClient which allows us to create group objects directly into an administrative unit, as documented on MS Docs.
This would enable managing group in an administrative unit without write permission on a whole tenant. As it states here, the permissions could be scoped only to the respective AU.
It would also enable to solve this issue on the terraform provider for azuread, as the provider uses this package as dependency.

Hey @manicminer, we couldn't reproduce the test failure, do you think the tests fail because of this addition?

Hey @manicminer, we couldn't reproduce the test failure, do you think the tests fail because of this addition?

I think it was just some missing roles/permissions on our end, I think I have fixed it now


UI Catalog: Character Map - Some glyphs in right column are clipped

See 0xFb6f for example.  Note this is with Casckadia Nerd Font and other Nerd fonts (https://www.nerdfonts.com/font-downloads).
Probably related to : https://github.com/migueldeicaza/gui.cs/issues/1766

Repros on WSL (Windows Terminal/Ubuntu) as well:

If you install the gnome-terminal on the WSL and using the Monospace Regular font I don't have that issue. Perhaps related font issue?

I'm not having the clipped glyphs issue. Your font is bigger why?

I don't know why those glyphs look bigger on my machine. Odd.

Either fixed by #1743 or something else because I can't repo it anymore.


[serverless-1.34] patch bash image

PTAL @jrangelramos @dsimansk

Should we extra it into a variable? Fine to merge as it's now.
/lgtm

Hence one more question, is there any generic pipeline bash step?

/test 415-e2e-oncluster-test

/test 415-e2e-oncluster-test


add deluge

What this PR does / why we need it:
Adds deluge bit torrent web client. It's my favorite torrent client and variety is nice.
Which issue (if any) this PR fixes:
formatted in the new roles/{{ application }} format and fixes some of the things mentioned in a previous pull request #56
Fixes #
#56
Any other useful info:
All usefull info for operating should be in the added doc file.

Looks like a nice addition! Few tweaks required then we should be good to merge.

Looks like a nice addition! Few tweaks required then we should be good to merge.

Hey @PurpleNinja225 - I was ready to merge, why'd you close this?

Hey @PurpleNinja225 - I was ready to merge, why'd you close this?

Hey @PurpleNinja225 - I was ready to merge, why'd you close this?

I realized I was messing up the pull request with every commit on my fork because I didn't create a new branch on the fork :sweat_smile: still learning the whole github pull request and forking thing down the new pull request

Hey @PurpleNinja225 - I was ready to merge, why'd you close this?

I realized I was messing up the pull request with every commit on my fork because I didn't create a new branch on the fork :sweat_smile: still learning the whole github pull request and forking thing down the new pull request


workload detail vue should show a proper UI for workload.info field

Right now we just print the content as a weird dump:

Added three filters on workload data:

KeysIgnored : to ignore keys in workload tab view
KeysWithTypeList : to view keys with type list in v-chip tag
KeysWithTypeDict : to view keys with type dict in v-chip tag with pattern key : value


Coveralls badge not resolving

For ELLIOTTCABLE/Paws.js, I'm unable to generate a Coveralls badge, despite there being a project for it:
https://img.shields.io/coveralls/ELLIOTTCABLE/Paws.js.svg →

I can reproduce your issue. Coveralls are sending us inaccurate information. In fact, the copy-and-paste badge links they provide on their own website are inaccurate (see https://coveralls.io/repos/ELLIOTTCABLE/Paws.js/badge.svg → ). I'd love you to inform them of this issue; fixing it on their side will fix it on ours.

On second look, it seems you use the branch Master, instead of master, which may trouble their system. Using this should work: https://img.shields.io/coveralls/ELLIOTTCABLE/Paws.js/Master.svg →

Interesting; I'd think they'd use the HEAD branch. Thanks for the tip!


Add possibility to use test permutation in RNG tests for mobile theme

Following up on https://github.com/joreilly/Confetti/pull/528#issuecomment-1500398908 . Currently the BaseScreenshotTest does not support to make multiple tests for each permutation of the mobile theme. This was supported in the old test classes. We should be able to support that somehow.

I think so. But I'm not sure it's needs to be "library" code. As long as a test can be parameterised and control those aspects in its setup, we don't need an API

Yeah I was thinking to add it in each module so it  is not part of the test library module at least :)


tests: Bluetooth: ascs: Add Source ASE state transition tests

This adds source ASE state transition tests and improves the callback call validation.

rebased

Rebased


Serialize to storage points and synapse layers

If we have list of 100k point that won't fit in the url.
Is it reasonable to save that to gcs or s3  similarly an image layer?

Might be a good case for indexDB + an export function. Otherwise the server
has to support user sessions.
On Thu, Jun 8, 2017 at 4:20 PM, Ignacio Tartavull<EMAIL_ADDRESS>wrote:

If we have list of 100k point that won't fit in the url.
Is it reasonable to save that to disk?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/seung-lab/neuroglancer/issues/123, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACZoSSLDX-xLHrpLnAiwja3dWlnbgWitks5sCFd9gaJpZM4N0krd
.

Maybe we can do something similar to skeletons or mesh serialization in precomputed

Neuroglancer supports remotely stored annotations, I believe. Local annotations are stored in the JSON state, bypassing the URL limitation. And there is also the AnnotationFramework which is supposed to store annotations in a persistent way?


Dependencies

See here

Have a look here and there (or the original one)

inquirer and chalk implemented in place of promptly and consola

Won't use commander for now until they won't support 100% custom help (auto generated help isn't desired here)

Not useful anymore, closing for now.


Map crashes on Android 4.3

I know that Android 4.3 is already pretty old, but i am required to support it. This is the error i get when using it on a Android 4.3 device:

Map is the parent component of the google-map-react component in my setup. However, my setup is no that relevant, given that this is also reproducible when opening the clustering example on an Android 4.3 (i used the Android studio emulator, so no real device needed).
One thing to note, older versions work, just the newer versions of google-map-react don't. From my tests:
0.7.5 does work
0.14.5 doesn’t work
0.20 doesn’t work

Since the error is related to the way modules are imported/exported, the issue must come from a change in the way it is built/packaged. Any ideas what changed, where can i begin searching for the issue?
I can't revert to an older version because i also need this for mobile support: https://github.com/istarkov/google-map-react/pull/233 (and that's a recent addition)

Other errors at console?

Unfortunately, no other errors. Since the chrome debugger doesn't work with Android <4.4 i used this for getting that warning. Yeah, it's difficult to debug on old androids, that's why i am asking for some guidance.

I really have no idea what it is. May be the problem with polyfills I removed from this library.
for example promises "0.12.1" - "0.13.0"

Thanks for the hint, that was it. It needs the es6 promise polyfill in order to work. I don't know if i should close this. Do you want to put the polyfill back in, or you want to leave it on a need-to-use basis?
At the very least, a readme note would be required as a heads up for others encountering this.

@catalinfeier Thanks for the contribution, as we're way behind Android 4.3, I don't think anything would be needed here. Closing the issue.


Allow to set up dynamic clusters safely in a shared environment

Right now we do not enable the dynamic clusters feature except in a non-shared environment (desktop) but we'd like to do so since some may deploy Headlamp as a web service but would like users to be able to set up clusters individually, through a plugin for example.
The problem with allowing this feature is a shared environment is that, since we do not have an authentication system coupled with headlamp (auth is handled by the API server), any added clusters would be visible to all users; it'd also allow for denial of service abuse since one could just keep pushing new clusters.
So we should investigate if there's a way to do this safely while avoiding having to have a user authentication coupled with headlamp itself.
Some suggestions for this include:

Keeping the cluster info local (client-side/browser) and always passing the cluster info on every request. Caveats: too much data on every request, and/or insuficient data dependending on how the cluster is to be configured.
Using an associated session ID so users only see the clusters set up for their session. Caveats: would not prevent DOS attacks.

Looking more into this

I looked more into this, sharing my findings.
Regarding 1st approach.

Instead of passing all cluster info on every request, we should consider passing a unique cluster identifier or a minimal set of necessary information for each request. This way, we can reduce the data size while still allowing Headlamp to fetch specific cluster details as needed.
We already have caching in headlamp, we can leverage that and use client-side caching to reduce the number of requests for cluster information. Store the cluster details locally on the client-side so that repeated requests for the same cluster can be served from the cache, reducing the amount of data transmitted over the network.

Regarding second approach.

To prevent DoS attacks, we can combine the associated session ID with rate-limiting mechanisms. This way, even if a user's session allows them to set up multiple clusters, they are still subject to rate limits to prevent excessive cluster creation in a short period.
We can Implement a session expiration mechanism to ensure that unused or inactive sessions are cleared after a certain period of inactivity, freeing up resources and preventing abandoned sessions from cluttering the system.

More suggestions
Namespace Isolation(To be done by user):
In Kubernetes, we can utilize namespaces to provide isolation for each user's clusters. When a user creates a new cluster, it should be created within their designated namespace. This way, each user's clusters remain isolated from one another, and they can only see and manage their own clusters. Then user can create service account will required RBAC on who can access that namespace resources.
Dynamic Cluster Provisioning(Headlamp does this):
Implement a Kubernetes custom controller or operator within Headlamp to handle dynamic cluster provisioning. When a user requests a new cluster, the controller creates a new namespace for the user and provisions the cluster within that namespace. This controller can also ensure that the controller enforces cluster quotas per user to prevent any single user from creating an excessive number of clusters.
Rate Limiting and Resource Quotas(Headlamp does this):
We can leverage Kubernetes built-in rate limiting and resource quota mechanisms. Set appropriate limits on cluster creation and resource usage to prevent DoS attacks and resource abuse in the shared environment. The Kubernetes API server can enforce these limits for each user and namespace, ensuring that users can only create clusters according to their allocated resources and rate limits.


Emmet multi-cursor expansion incorrect

VSCode Version: Code - Insiders 1.16.0-insider (dc3a6df693da5ad6e9219cb0269439cc6a8c401a, 2017-08-11T06:58:01.143Z)
OS Version: Darwin x64 16.7.0

Foo-Test[bar=baz]*4
Bar-Test[bar=baz]*4

@jens1o You want to take this one up?
What is happening is that expanded value of the first abbreviation is overlapping with the second abbreviation.
We go through each of the cursors, extract abrbeviation and run expand on it here: https://github.com/Microsoft/vscode/blob/release/1.15/extensions/emmet/src/abbreviationActions.ts#L144
Instead of going through editor.selections in the order that they appear in that array, we need to sort it in descending order of their position and then go through the sorted list.

I'm sorry, but my Insiders version is close to being unusable at all(#32530). And the todays release doesn't fix my problem, and the functionality is very limited. :/

@ramya-rao-a Thanks for the fix!

@jmdowns2 deserves the credit, he provided the fix :)


Support dataset-only smart tag analysis

Resolve #433
Description:
The overall diff is pretty messy, so I recommend looking at the different commits individually.
I made a couple of decisions what we can debate:

Color the dataset-only bars (with no outcomes) dark blue (palette.secondary.dark) like other data visualizations.
Hide the pipeline-specific columns, including accuracy and some smart tag families.
Disable the Prediction and Outcome options from the menu (since hiding the options would result in a weird one-option menu).
On the Dashboard, move the Smart Tag Analysis card before Pipeline Metrics by Data Subpopulation, so all cards that support dataset-only are at the top. Is that a good idea?

Here is an example:

For reference, here is how it looks with a pipeline:

Checklist:
You should check all boxes before the PR is ready. If a box does not apply, check it to acknowledge it.

[x] ISSUE NUMBER. You linked the issue number (Ex: Resolve #XXX).
[x] PRE-COMMIT. You ran pre-commit on all commits, or else, you
ran pre-commit run --all-files at the end.
[x] USER CHANGES. The changes are added to CHANGELOG.md and the documentation, if they impact
our users.
[x] DEV CHANGES.

Update the documentation if this PR changes how to develop/launch on the app.
Update the README files and our wiki for any big design decisions, if relevant.
Add unit tests, docstrings, typing and comments for complex sections.

Awesome!!! A few comments on your questions:

I'm ok with the blue, but I think the color should be the same one as in the control panel when there is no pipeline. So either both are blue, or we pick the same dark grey (black?) for this viz too. Side note - is the same dark blue as in the dataset warnings for example?
I'm not sure about moving the tile before the pipeline quality. I absolutely get the reasoning, but I do feel when you have a pipeline selected, you would care/want to see the overall quality first. Curious what others think.
The rest is great.


Improve description fields with progressive disclosure

prefer toggle/progressive disclosure (view some/view all)

Orphans guidance: https://www.hedden-information.com/orphan-terms-in-a-taxonomy/


return float64s from JSHandle

Without this, true floating point values are never returned and are always truncated to integers. There is very likely a more optimized way to do this. Is there a reason the value can't just be returned without casting (if it's a "number")? Duh: because it might be an integer and not a floating point.

A test for that would be great, thanks for your contribution!

Not very DRY, but it'll do.

Thank you so much!


Consensus: Invoke fails after pausing one of the peers on the network.

Description
After an initial deployment of Chaincode Exampl02 on 5 peer network , paused one of the peers. It was observed that Invoke doesn't get executed on any of the peers.
Describe How to Reproduce

Setup a 5 node docker peer network with security

Deploy chaincode Example02 with 1000, 2000 as initial values and check Invoke and Query

'docker ps' command indicates that all 5 peers have chaincode containers deployed inside docker
Invoke and Query are successful

Issue 'docker pause PEER1' to paused Peer1

Invoke chaincode Example02 with args ["a","b","1"]
CONTAINER ID        IMAGE                       COMMAND     CREATED             STATUS                   PORTS                                                NAMES
f0c9e23e7cd9        rameshthoomu/peer:e108db6  "peer peer"  27 minutes ago      Up 27 minutes (Paused)   <IP_ADDRESS>:5001->5000/tcp, <IP_ADDRESS>:30003->30303/tcp     PEER1

Invoke is not getting executed waited for about 27 mins.
docker_peer_logs.zip
Commit Level: ae580613523bbedeeb8eb4a1ab609bf53c75750f

I suspect this is because of blocking Broadcast in the peer.  For PBFT, we should not block for sends, or at least not for more than 2f+1 sends.
I think we should move peer connection/disconnection events into the consensus plugin, and only expose a peer Writer interface.
@jeffgarratt

@tuand27613 , We paused the peer after a Deploy,  Invoke / Query twice
Here are the test steps :

Start 5 peer network
Deploy chaincode and wait for 90 seconds
Trigger Invokes and Queries twice and check if the block chain height is 4
Pause one of the peer
Invoke and Query for 100 Iterations

Observations based on two iterations:
Iteration1: After 88 Iterations Invoke/Queries does not go through on other peers
Iteration2: After 50 Iterations Invoke/Queries does not go through on other peers
Logs attached for the same
Iteration_1_2_logs.zip

Duplicate of #1076


Is there an event that listens to know if a call is coming?

I am trying to find out the information of the person being called and then process the call to accept it, but no event is found.
can you help me, thank you in advance

Hi, what event did you try? did you check CallKeep events as well?


How to genereate spritesheet and auto replace css?

Hello, In Polymer project build release, there is a task that generate the images into spritesheets and then auto replace the css. And now I can deal with one component file. It is my demo: https://github.com/YingshanDeng/polymer-generate-spritesheet. Any guid, thank you!
@ebidel

This seems specific to your app and unrelated to an issue in Polymer.


cannot copy to clipboard on localhost

When using this H5P content on a localhost machine, when trying to copy to clipboard, getting error message "Your text could not be copied to the clipboard"
Browser console shows "Uncaught TypeError: navigator.clipboard is undefined"

What browser are you using?
What's its permission state for accessing the clipboard?

Problem happens on Firefox, Chrome and Edge. But only locally, things are OK if I put my structure strip content online.
Don't know how to check "permission state for accessing the clipboard".

Sorry, I cannot reproduce this at all. Browser support for navigator.clipboard is fine (https://caniuse.com/?search=navigator.clipboard). I'd not know why running on localhost would make a difference - in fact running on localhost should lead browsers to allow clipboard access (if it's triggered by a user action, and it is).
You may want to check permissions using
navigator.permissions.query({name: 'clipboard-write'}).then((result) => { console.log(result.state) }); inside the H5P iframe context. Might give you denied.
You can also check what permission (or rejection) your local server sets (via some Content-Security-Policy) that might interfere or what the H5P integration sets onto iframes within the allow attribute. You could check whether your situation changes if that list contains clipboard-write.
This is not an issue with the content type code. In fact, it has a guard to detect that navigator.clipboard is not available and the text can therefore not be copied to the clipboard.

Thanks for looking into this, @otacke I have just tested the Structure strip h5p content on my local computer in Lumi, and it's working as expected. This means that---as you suggest---some kind of Content-Security-Policy is enforced in the parameters of my local server (Wampserver). I will continue my investigations and report.
Happy New Year 2024!

Happy New Year 2024 to you as well! Please let me know if you find out something. It's really an edge case, but I could try to query for more information when navigator.clipboard is not available and add a more specific error message.


terminate called after throwing an instance of 'BinaryNinjaCore::DatabaseException'

Even with the latest build, I still get an error reminisent of #1496
terminate called after throwing an instance of 'BinaryNinjaCore::DatabaseException'
  what():  Data too large
Aborted (core dumped)

to reproduce:

turn off tailcall options
analyze executable
save bndb

I am using linux
The file is too big to post here, Peter has a copy from the Slack chat (ch34.zip). Or let me know where to post it.

Fixed in 2.0.2225-dev


Core MapReduceChain token counting before combine step - Performance

System Info
This impacts both JS and Python versions
Who can help?
@hwchase17
@nfcampos
Information

[X] The official example notebooks/scripts
[X] My own modified scripts

Related Components

[X] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[ ] Vector Stores / Retrievers
[ ] Memory
[ ] Agents / Agent Executors
[ ] Tools / Toolkits
[X] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction
Discussed this with @nfcampos over slack, but pasting it here for documentation/community discussion to validate this change/issue.
I have switched from JS -> Python version but this issue is valid for both.
When using JS version, I noticed the mapreduce chains combine step decides when it should combine based on the token count sum of the map steps entire prompt, instead of just the outputs. This presented a few issues:

The point of the map step, as I understood it, is to condense the chunk to eventually be able to fit in the combine prompt, and so gauging when to combine based on summing all map steps’ (input+output) token counts didn’t make sense. This leads to several unnecessary iterations, and much longer run time than if it’s just the map steps’ output tokens being summed, which is what is eventually used in the combine step anyway.
If the map prompt has large instructions, then it is possible that the sum will never reduce past the threshold (token_max default is 3000). Example:

You have ten chunks having the map step being run.
Each chunk has 400 token instructions in map Prompt. 400*10= 4000 tokens.
The map steps would never condense enough to drop below the 3000 token limit, even though the output from each map step might be 100 tokens. Worse still, it would run up $$$ by running map steps until max_iterations.

I can share my monkey patch of the langchain JS code if it helps, and had even proposed a PR for this in the langchianjs discord. Now that we moved to python, and since I haven’t contributed to any python projects, I thought I’d check here before proposing this change or even attempting a PR.
My questions before proceeding are - does this sound right to you? Is there any reason why a generic mapreduce chain would use the entire map prompt from the map step, and not just the outputs when deciding to combine?
Expected behavior
The map_prompt output tokens should only be summed up when deciding if we can combine or not.
In the JS version, my monkey patched langchain MapReduce chain's implementation looked like:
async _call(values) {
    if (!(this.inputKey in values)) {
      throw new Error(`Document key ${this.inputKey} not found.`);
    }
    const { [this.inputKey]: docs, ...rest } = values;
    let currentDocs = docs;
    let totalIterations = 0;
    for (let i = 0; i < this.maxIterations; i += 1) {
      const inputs = currentDocs.map((d) => ({
        [this.documentVariableName]: d.pageContent,
        ...rest,
      }));
      const promises = inputs.map(async (input) => {
        const prompt = await this.llmChain.prompt.format(input);
        return this.llmChain.llm.getNumTokens(prompt);
      });
      const length = await Promise.all(promises).then((results) =>
        results.reduce((a, b) => a + b, 0)
      );
      const joinedInputs = {
        [this.documentVariableName]: inputs
          .map((_) => _[this.documentVariableName])
          .join('\n\n'),
        ...rest,
      };
      // Speed up converging - Patched Token Counting
      const joinedInputTextsPrompt = await this.llmChain.prompt.format(
        joinedInputs
      );
      const joinedInputTextsLength =
        (await this.llmChain.llm.getNumTokens(joinedInputTextsPrompt)) +
        (await this.llmChain.llm.getNumTokens(
          this.combineDocumentChain.llmChain.prompt.template
        ));
      console.log({
        length,
        joinedInputTextsLength,
      });
      const canSkipMapStep = i !== 0 || !this.ensureMapStep;
      // const withinTokenLimit = length < this.maxTokens; // Original implementation
      const withinTokenLimit = joinedInputTextsLength < this.maxTokens;
      if (canSkipMapStep && withinTokenLimit) {
        break;
      }
      console.time('MapReduceChain:mapStep');
      const results = await this.llmChain.apply(inputs);
      console.timeEnd('MapReduceChain:mapStep');
      totalIterations += 1;
      const { outputKey } = this.llmChain;
      currentDocs = results.map((r) => ({
        pageContent: r[outputKey],
      }));
    }
    const newInputs = { input_documents: currentDocs, ...rest };
    console.time('MapReduceChain:combineStep');
    const result = await this.combineDocumentChain.call(newInputs);
    console.timeEnd('MapReduceChain:combineStep');
    console.log('Iterations: ', totalIterations);
    return result;
  }

Relevant change:
const joinedInputTextsLength =
        (await this.llmChain.llm.getNumTokens(joinedInputTextsPrompt)) +
        (await this.llmChain.llm.getNumTokens(
          this.combineDocumentChain.llmChain.prompt.template
        ));
// const withinTokenLimit = length < this.maxTokens; // Original implementation
const withinTokenLimit = joinedInputTextsLength < this.maxTokens;

Edit: This only impacts JS version.

JS Issue is here. This doesn't seem to impact Python implementation of MapReduceChain.


Revamp the rabbitmq.com home page

The initial pull request (#1813) was merged into main too early as this work is still in its early stage of development. I reverted the merge and resubmitted the branch in this new pull request. The message below is the original description from @pstack2021.
— @dumbbell

Updates to the RabbitMQ homepage, these changes were agreed on in a meeting this morning (27.02.2024) with product management @HowardTwine and @DigitalBlasco and with development @dumbbell and @mkuratczyk
Doc tracking these changes: https://docs.google.com/document/d/1j7P4aM1IJFnl0E3InMVYk83g9ggOqwWDdT1DJKQHqxI/edit#heading=h.x02o23co6ze2
Points to note:

I haven't done anything with the banners, we can just leave the ones that are there for now. As agreed this morning, the plan is to create a 3.13 blog and when published, use this as a banner on the home page.

@dumbbell @mkuratczyk - Is there anyone that can write this blog for us? I can review it. I need to concentrate on writing the Introductory and other topics for the new OSS RMQ site (so we can publish the TOC I have built soon) and then get back to the commercial RabbitMQ 1.6 docs as these releases will be coming soon, thanks.

I can write the blog post if there are no other volunteers

@mkuratczyk: Feel free to write it :-) Otherwise I will do it once I'm done with the homepage.

Thanks @mkuratczyk. If you could write the blog post that would be great. Can we make this blog for all users please. Currently RabbitMQ release notes are aimed at more of a developer type audience rather than for other personas such as administrators. If we can keep descriptions simplistic yet with enough detail that all users "just get it". I do understand that the release notes are more "change log" type material hence written in this way
As an example of what I mean, please take a look at the items under "Core Broker" in the 3.12.12 release notes: https://github.com/rabbitmq/rabbitmq-server/releases/tag/v3.12.12, then compare these descriptions to those in the commercial release notes: https://docs.vmware.com/en/VMware-RabbitMQ-for-Kubernetes/1/rmq/release-notes.html (see under Core Server: Bug Fixes), I can review the blog PR when it is ready.
Many thanks
Paula

Another example for you to reference @mkuratczyk, please see the MQTT plugin bug fix description in the 3.12.12 release notes  and then compare it with my description (search for: Allow MQTT QoS 0 subscribers to reconnect) in the VMware RabbitMQ for K8s release notes.

Hi @dumbbell,
Firstly, let me commend you on the brilliant job you have done with the RabbitMQ homepage, I think it looks great and it will be liked for users of all types: new and old. I love the tabs for the use cases, so easy to see each one at a glance and move between them.
I am providing feedback here rather than sequencing through all the commits, I hope this is ok:

Remove full stop at the end of the one liner at the top of the page i.e. change it to: One broker to queue them all I know the https://www.rust-lang.org/ site uses it but if you search open source software sites in general most of them don't have, I think it looks better without it.
How about adding this to the introductory sentence to give it additional power/immediately tell users how many are using it already, can we change: RabbitMQ is a reliable and mature messaging and streaming broker, which is easy to deploy on cloud environments, on-premises, and on your local machine. to RabbitMQ is a reliable, mature messaging and streaming broker, which is easy to deploy on cloud environments, on-premises, and on your local machine. It is currently used by millions worldwide.
Under the Interoperable heading, possibly change: There is certainly a client library available for the programming language you love. No vendor lock-in! to  There are multiple client library available, which can be used with your programming language of choice, just pick one. No vendor lock-in!
Under Flexible, heading, I would change the word "etc: to "and so on", I wouldn't use word abbreviation in a home page or anywhere in documentation really.
Under Reliable heading, in this sentence change "be sure" to "ensure"
Under Examples of common use cases, suggested minor rewrite for this text: Here is a selection of common use cases we hear about from the community or the customers. You may find yourself in one of these cases and RabbitMQ can definitely help! Of course RabbitMQ is useful in many more situations. can we change this to: Here is a few common use cases we hear about from the community and our customers. If you find yourself in one of these cases, RabbitMQ is definitely the message and streaming broker that can help! We cannot provide all our use cases here, RabbitMQ can be used in many more situations, For help, contact the RabbitMQ team using the various contact methods at the end of this page.
RPC use case example: Possibly change: The website or kiosk expects to get an answer for the order in no time. to The website or kiosk expect to get an answer for the order in minimal time.
Minor grammatical update, highlighted in bold:  The caller that pushed the order then subscribes to another queue and wait for an answer with that same correlation ID. to The caller that pushed the order then subscribes to another queue and waits for an answer with that same correlation ID.
RPC use case example: Minor rewrite, possibly change: _A classic queue is a good fit here to achieve lower latency, at the expense of less safety — the caller can still retry. If however the order cannot be lost, you should prefer the combination of acknowledgments and quorum queues to ensure a message is safe once confirmed. to: To achieve lower latency, a classic queue is a good fit here but it is at the  the expense of less safety — the caller can still retry. However, if the order cannot be lost, you might prefer to use a combination of acknowledgments and quorum queues to ensure a message is safe once confirmed.

the caller can still retry does this text fit right at its location above?

RPC use case example: To improve readability, minor rewrite: This topology allows to serialize the processing of orders to serve them in a first come first served order. This avoids the need for transactions. to: This topology allows the processing of orders to be serialized to serve them in a first come first served order. This avoids the need for transactions.

Streaming use case example: suggested rewrite in the 1st paragraph - change: You run a video platform. When a user upload a new video, you have a ton of things to do once the video was safely stored: run some post-upload analysis, transcode lower quality copies of the video, notify other users subscribed to the author's creations, … to You run a video platform. When a user uploads a new video, you have multiple tasks to complete when the video is safely stored: run some post-upload analysis, transcode lower quality copies of the video, notify other users subscribed to the author's creations, and so on.

IoT use case example:

To be continued @dumbbell, I need to log off now for a while

Thank you @pstack2021 for the extensive review!
I applied all your suggestions, except the following ones:

Here is a few common use cases we hear about from the community and our customers. If you find yourself using one of these cases, RabbitMQ is definitely the message and streaming broker that can help! We cannot provide all our use cases here, RabbitMQ can be used in many situations. For more information, contact the RabbitMQ team using the various contact methods at the end of this page.

I agree the paragraph I wrote must be improved (I didn't have inspiration). However, we can't tell people to specifically ask us: this is a FOSS and they should ask the community (which we are part of). For a dedicated channel with the RabbitMQ team, this is commercial support territory.

the caller can still retry does this text fit right at its location above?

Can you clarify?

What about the License section: what exactly does "Behind the scene, RabbitMQ backed by Broadcom who offer professional services." mean?? "what professional services?

I didn't change the paragraph yet. We mostly need to paragraph to introduce the two sections below (FOSS and commercial offerings) and act as a horizontal visual delimiter. Like the one above, I didn't have inspiration. Most of the actual content should go in the sections below.

Also in addition to this paragraph, I would include information about how customers can contribute how about adding an additional paragraph similar to the following:

I didn't put this entire paragraph because this is not the place to explain how to contribute, I believe. I just put "Take a look at our Contributors page." with the link. What do you think?

In addition, a commercial edition of RabbitMQ is available which comes with exclusive warm standby replication and intra-cluster data compression advanced features

In this suggestion, I re-introduced the "such as" part because we may add other features in the future and we shouldn't have to list them all here.

Also for the list under this heading are they listed in the order that we want users to contact us i.e. do we want to direct people to slack first??

Good idea, I put GitHub first. However, no, Slack should stay last. The mailing-list and Discord are the preferred channels, because it's too cumbersome to invite people to Slack.
I added Twitter but I don't consider it a communication platform. This is probably the worst way to contact us. As the platform name tells it, it's mostly noise.


Unicode identifiers

Currently, the specification does not allow identifiers with non-ASCII characters. I think this should be changed.
It is already implemented in dart2js, and is pretty easy.

I agree. I really hate not being able to use ñ, á, é. í, ó, ú in my variables, labeling something "contrasena" instead of "contraseña" is just insulting.

Another usecase of a unicode identifier would be localization classes, where an identifier is needed for every localizable string and it needs to be in English as for now. Thinking of a meaningful and readable English identifier for every localizable strings is a heavy (but UNNECESSARY) mental overload for those developers who don't speak English much.
This mental overload discourages developers to write localized strings instead of hard coded local literals, fooling themselves that they would come back and turn those strings into localized ones once they get the translation.
My team once suffered from it, but the situation becomes much better when I decided to allow them to use local strings as the translation key. The developers in the team are happy and willing to write localizable strings at the dev phase.
I still can benefit our team from using local strings as translation key by adding a overloaded [] operator to the localization class and retrieving a localized string like FooLocalization.of(context)['some local string']. But it would be error-prone as there is no type system guarding the index lookup.


Come up with the framework for integration tests

So correctness can be tested end to end.

For our filebeat+logstash configs, we:

start new logstash instance with a bit to ship to a test elasticsearch index
start filebeat and point it at known payloads
wait some seconds for filebeat to finish processing
compare the test elasticsearch documents to expected results

I mainly wanted to chime in here to have logagent-js support a flag to tell it to quit once all EOF(s) reached.  That would remove a kludgy bit from my approach: assuming the shipper processes all logs in N seconds.

Just for reference, this is what Logstash may add: https://github.com/elastic/logstash/pull/5917


Kerberos with hive

Affected module
Hi,
I'm going to capture a hive data source with kerberos authentication enabled, But the connectionArguments in serviceConnection get an error when written this way.
connectionArguments={ "auth": "KERBEROS", "kerberos_service_name": "hive", }
What is the premise of writing this way? Or how do I transfer krb5.conf and keytab files.
can i config kerberos with hive
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Screenshots or steps to reproduce
Expected behavior
A clear and concise description of what you expected to happen.
Version:

OS: K8S
Python version:
OpenMetadata version: [1.4.1]
OpenMetadata Ingestion package version: Helm Install

Additional context
Add any other context about the problem here.

Hey @luhea, can you please open a thread on https://slack.open-metadata.org/ support channel, we may need more info here and we maybe able to assist you to configure your hive.
closing this ticket for now, if any improvement or fix required then we can reopen this.


Readme improvements

Hi everyone.
I had two problems using yours awesome editor:

The first one was by not knowing how to programmatically set value. So at first I was trying to do it using the codemirror instance until I saw that .value() actually does that.
The last one was more critical. I was trying to customize the toolbar and somehow it was not working properly. The toolbar was larger and a blank space was appearing instead of one of the icons. So, again I took a look in the source code and realized that the icon name for ordered lists in the readme doesn't match the actual implementation.

Because of those issues I took the time to improve the readme to avoid future users from having the same problem. Hope you agree with the changes.

Great catch, thanks for contributing!


add db file module and schemas

added db config and Pool exports all queries, and schemas

We have the database info added already


ci: base and head ref fix

Description
When VRT is skipped, Chromatic is returning "undefined" as the value of storybook-url. This needs to be an empty string in order to trigger the local CI build.
This also corrects the SHAs being used - NX was not providing the correct base and head SHAs so this moves those to using the ones provided in the pull_request event.
How and where has this been tested?
Please tag yourself on the tests you've marked complete to confirm the tests have been run by someone other than the author.
Validation steps

[x] Expect this branch to trigger a CI build of storybook for the published preview site link to CI run

To-do list

[x] I have read the contribution guidelines.
[x] ✨ This pull request is ready to merge. ✨

Successful storybook build: https://pr-2634--spectrum-css.netlify.app/preview/?path=/docs/guides-contributing--docs


WP folders are not ignored when dist is not ignored

When dist folder is not addded to .gitignore, WordPress ignored folders are also not being added, see: https://github.com/xhtmlized/generator-xh/blob/master/app/templates/gitignore#L36
Is there any reason for that?

Is this because of syntax error instead:
bower_components<% if (ignoreDist) { %>
dist<% if (isWP) { %>
wp/wp-content/themes/**/img
wp/wp-content/themes/**/fonts
wp/wp-content/themes/**/js
wp/wp-content/themes/**/css
wp/wp-content/themes/**/media
wp/wp-content/uploads<% } %><% } %>

should be:
bower_components<% if (ignoreDist) { %>
dist<% } %><% if (isWP) { %>
wp/wp-content/themes/**/img
wp/wp-content/themes/**/fonts
wp/wp-content/themes/**/js
wp/wp-content/themes/**/css
wp/wp-content/themes/**/media
wp/wp-content/uploads<% } %>


Add support for gnome 43

The tested extension works fine

I'm not sure if this extension is needed anymore in gnome 43. There's a VPN section now in the new quick settings menu that serves the same purpose this extension does

@Zackptg5 I'm probably missing something, but my VPN settings in GNOME does not support Wireguard

@fabrixxm I had to import them with nmcli in terminal and then they show up in quick settings

Ah! I thought the extension had moved somehow. I noticed the new vpn section the other day. It looks like it's not required for me anymore,
Thanks to the dev for developing and maintaining this! It got me by for a while now.


DOC-3546 retry count expression

https://harness.atlassian.net/browse/DOC-3546
Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[x ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

https://harness.atlassian.net/browse/DOC-3546

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Errors don't show under PROBLEMS

I compile a local SQLRPGLE program that has an errors. The errors don't show up under PROBLEMS, but they are inserted into the code.
Code_for_ibm_I.txt

⚠ REMOVE THIS LINE AND ANY SENSITIVE INFORMATION BELOW! ⚠

Context
Version

Code for IBM i version
2.7.0

Visual Studio Code version
1.86.2

Operating System
win32_x64

Active extensions
CL (vscode-clle): 1.1.4
Code for IBM i Walkthroughs (vscode-ibmi-walkthroughs): 0.4.0
Db2 for IBM i (vscode-db2i): 0.7.0
Emmet (emmet): 1.0.0
Error Lens (errorlens): 3.16.0
Extension Authoring (extension-editing): 1.0.0
Git (git): 1.0.0
Git Base (git-base): 1.0.0
GitHub (github): 0.0.1
GitHub Authentication (github-authentication): 0.0.2
IBM i Notebooks (vscode-ibmi-notebooks): 0.0.6
JSON Language Features (json-language-features): 1.0.0
Merge Conflict (merge-conflict): 1.0.0
NPM support for VS Code (npm): 1.0.1
Node Debug Auto-attach (debug-auto-launch): 1.0.0
Overtype (overtype): 0.5.0
RPGLE (vscode-rpgle): 0.26.1
TypeScript and JavaScript Language Features (typescript-language-features): 1.0.0

Remote system

Setting
Value

IBM i OS
V7R5M0

Tech Refresh
n/a

CCSID
37

Default CCSID
37

SQL
Enabled

Source dates
Disabled

Enabled features

/QOpenSys/pkgs/bin
/usr/bin
/QSYS.lib/LENNONS2.lib
/QSYS.LIB
/QIBM/ProdData/IBMiDebugService/bin

bash
attr
GENCMDXML.PGM
QZDFMDB2.PGM
startDebugService.sh

chsh
iconv
GETNEWLIBL.PGM

git
setccsid

grep

ls

md5sum

sort

stat

tar

tn5250

Shell env
BUILDLIB=LENNONS1
CURLIB=LENNONS1
HOME=/home/LENNONS
HOST=pub400.com
IFS_LIB=LENNONSB
IFS_SRCPF=VSCODE
LIB1=LENNONSB
LIBLS=LENNONSB LENNONS1 QGPL QTEMP QIWS
LOGIN=lennons
LOGNAME=lennons
MAIL=/var/spool/mail/lennons
OLDPWD=/home/LENNONS
PASE_USRGRP_LIMITED=N
PATH=/QOpenSys/pkgs/bin:/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:.:/usr/bin
PWD=/home/LENNONS
SHELL=/QOpenSys/pkgs/bin/bash
SHLVL=1
SSH_CLIENT=<IP_ADDRESS> 53431 2222
SSH_CONNECTION=<IP_ADDRESS> 53431 <IP_ADDRESS> 2222
TZ=<UTC>0
USER=lennons
USERNAME=lennons
WORKDIR=/home/LENNONS
_=/QOpenSys/pkgs/bin/env

Variants
{
  "american": "#@$",
  "local": "#§$"
}

Errors
[
  {
    "command": "/QOpenSys/usr/bin/qsh",
    "code": 1,
    "stderr": "CPC7301:  File QSQLPRE created in library QTEMP.\nCPC7305:  Member GETOBJUR added to file QSQLPRE in QTEMP.\nCPC3201:  Member GETOBJUR file QSQLPRE in QTEMP changed.\nRNS9307:  Diagnostic check of source is complete. Highest severity is 00.\nCPC0904:  Data area RETURNCODE created in library QTEMP.\nCPC7301:  File QSQLTEMP1 created in library QTEMP.\nCPC7305:  Member GETOBJUR added to file QSQLTEMP1 in QTEMP.\nRNS9308:  Compilation stopped. Severity 30 errors found in program.\nRNS9310:  Compilation failed. Program GETOBJUR not created in library LENNONS1.",
    "cwd": "/home/lennons/IBMi_IFS_Dev"
  },
  {
    "command": "/QOpenSys/pkgs/bin/md5sum $(find . -type f)",
    "code": 1,
    "stderr": "/QOpenSys/pkgs/bin/md5sum: ./APIs_SQL/LCKOBJC: No such file or directory\n/QOpenSys/pkgs/bin/md5sum: copy.CLLE: No such file or directory",
    "cwd": "/home/lennons/IBMi_IFS_Dev"
  },
  {
    "command": "/QOpenSys/usr/bin/qsh",
    "code": 1,
    "stderr": "CPC7301:  File QSQLPRE created in library QTEMP.\nCPC7305:  Member GETOBJUR added to file QSQLPRE in QTEMP.\nCPC3201:  Member GETOBJUR file QSQLPRE in QTEMP changed.\nRNS9307:  Diagnostic check of source is complete. Highest severity is 00.\nCPC0904:  Data area RETURNCODE created in library QTEMP.\nCPC7301:  File QSQLTEMP1 created in library QTEMP.\nCPC7305:  Member GETOBJUR added to file QSQLTEMP1 in QTEMP.\nRNS9308:  Compilation stopped. Severity 30 errors found in program.\nRNS9310:  Compilation failed. Program GETOBJUR not created in library LENNONS1.",
    "cwd": "/home/lennons/IBMi_IFS_Dev"
  }
]

@worksofliam
Well duh!  That fixed it. Didn't notice the filter--probably got there when I thought I was typing on the green screen but has failed to change the focus.  We live and learn.  Sorry...


Resend API url Exposed as a configuration item

@BenjaminX I will merge this, but I will only release a new version in the next couple of days together with some new functionality that is coming in, would you mind using the main branch for a little while ?

sure, follow you planning. Thx


Freezing header

Hi, is there a possibility to "freeze" the first row, so when scrolling down the table it will still be visible? Thank you.

see https://cxn03651.github.io/write_xlsx/worksheet.html#freeze_panes

That's awesome. Thank you very much.


Need more explicit field name config options for RegridDataPlane and PcpCombine to allow python embedding support

Currently [FCST/OBS]_VAR_NAME is used to determine many things: output field name for PcpCombine, input and output field name for RegridDataPlane, and input field name for the comparison wrappers (grid_stat, point_stat, ensemble_stat, mode, and mtd). However, also use this variable to supply a python script to pass data into the MET tools. Using python embedding for input into RegridDataPlane will fail because it tries to use the full python script as the output field name. Also, you may want to use RegridDataPlane and change the output field name. What needs to happen:

Add configuration variables for:
[FCST/OBS]_PCP_COMBINE_OUTPUT_FIELD_NAME
[FCST/OBS]REGRID_DATA_PLANE[INPUT/OUTPUT]_FIELD_NAME
so the user can explicitly set the names for these items.

Ensure backwards compatibility by checking if these new variables are set, and if not, just use [FCST/OBS]_VAR_NAME

Add additional error checking. If the RDP input is a python script and the explicit output field name is not set, report error and exit. Others?

The input and output names must correspond to the appropriate VAR variable, so they will have to be named [FCST/OBS]_<APP_NAME>_VAR[_INPUT/_OUTPUT/]_FIELD_NAME. The var_info dictionaries contain and 'index' item that corresponds to

These changes are in the 3.0-beta1 release. The documentation still needs to be updated before the 3.0 release.

Documentation was added to branch feature_297_sphinx_transition


cmd/link: misc/cgo/testshared failure on boringcrypto branches

I released the 1.17.4 and 1.16.11 to the boring crypto versions of Go, and I noticed a link failure in the trybots:
https://storage.googleapis.com/go-build-log/f967062a/linux-amd64_0dc21008.log
@heschi noticed that it appeared first in https://go.dev/cl/362654 but it looked unrelated so it was ignored. We suspect this is a real failure of a ~flaky~ (EDIT: I was wrong, it's deterministic) test that was recently exposed. Low priority because it doesn't actually block boring crypto releases, but it does add noise to the process.
CC @cherrymui @randall77

Do you mean that failure is nondeterministic? That would be weird as it seems from the C linker.

Yeah, I don't think it's flaky, just that it was hidden by the clobber test before.

Is it failing now? I don't see a failure in the dashboard or @mknyszek 's recent CLs.

See https://build.golang.org/?repo=&branch=dev.boringcrypto (the dev.boringcrypto branch). The most recent row has the failure for me.

Thanks. I was looking at boringcrypto.go.1.17 branch...

The boringcrypto syso references pthread functions, so we need to pass -pthread to the C linker.
I spent a while looking into why this is not failing before. It turns out that on 1.17 the tests there simply don't depend on any crypto packages, so the syso is not linked in. On tip, it does depend on crypto, possibly though fuzzing as a test dependent. I can reproduce the error with 1.17 branch with a test explicitly using crypto, e.g. go test -linkshared crypto/sha1. Will send a CL soon.

I understand this is resolved via https://go.dev/cl/369161, it just didn't get closed because the "Fixes" syntax doesn't close issues on dev.* branches. Notably, https://build.golang.org/?branch=dev.boringcrypto (as well as 1.17 and 1.16 ones) is green.


⚠ SolarOscp has degraded performance

In c9afc00, SolarOscp ($SOLAROSCP_URL) experienced degraded performance:

HTTP code: 200
Response time: 363 ms

Resolved: SolarOscp performance has improved in ffaa83e after 10 minutes.


No Color Bar

When I fit a Gaussian Process Regression model by calling 'GPy.models.GPRegression'. then I want to plot the model so I call 'm.plot(property='3d'). I know the highlight  area usually have a larger value, but  how can I show the related color bar for the colours. any help? thanks so much.

When you plot you get back the full dictionary of all matplotlib plots. Use the plot for the image and add a colorbar to the figure yourself.
fig.colorbar(cm, ax=ax)

Where cm is the image you want the colorbar for, ax is the axis you want the colorbar to be added and fig is the figure which contains cm.

The returned plot is fig = m.plot(). The problem is from the fig object, I did not find the image, and also what do I pass for the second parameter ax?

fig.figure.images is empty

Addendum: This doesn't work if you've set the plot_data parameter to False.


Granular notifiers in protocol spec

Added connect/disconnect notifiers per: https://github.com/ethersphere/bee/issues/653
Removed topology.Notifier to remove p2p and toplogy dependency
Reduced to single notifier as there is only one notifier needed for now, this is easy to expand to array if needed
Some code in libp2p  uses closePeer() instead of disconnect, as this is part of connection process and there is no need to signal disconnect in this case as the peer for not yet even added to peer registry.

Todo: more unit tests

Looks good @pradovic. I'm not sure why the signature change in the notifiers is needed to p2p.Peer, where p2p.Peer in fact stores only overlay address. swarm.Address usage maintains clarity that only overlay is conveyed, whereas p2p.Peer might infer that other information that should maybe not be leaked to higher level components, such as underlay or other p2p info.

I saw that @janos proposal uses Peer, so I wanted to make it uniform. No other reason, but I guess it could be useful if we expand Peer with more info. On the other hand, the major change in Notifier interfaces was just reducing it to one + decouple it from topology.

@janos I talked with @metacertain and he wanted to work on unit tests to get more familiar with this. So, I will wait for him to implement the tests and hlep him in the process, and we will add them as well.

@janos Tests are done. I used a bit different approach than what was proposed in the task, just because of the simplicity and I think this is good enouth. LMNWYT :)

@pradovic yes, this is just enough for testing the functionality. 👍 Thanks.


Poor performance

Hello !
I just installed the "qor_example with sqlite3" and testing it with "httpress" tool the qor server saturating 4 cores on a "atom 4 cores 100% cpu load" can not server more than 30 requests per minute.
httpress -t 2 -c 4 -n 1000  http://<IP_ADDRESS>:7000/
250 requests launched (7.319698 sec)
500 requests launched (8.065591 sec)
750 requests launched (8.522204 sec)
1000 requests launched (8.724288 sec)
thread 1: 498 connect, 498 requests, 498 success, 0 fail, 0 fail avg, 2881254 bytes, 136950 overhead
thread 2: 502 connect, 502 requests, 502 success, 0 fail, 0 fail avg, 2949567 bytes, 138050 overhead

TOTALS:  1000 connect, 1000 requests, 1000 success, 0 fail, 0 fail avg, 4 (4) real concurrency
TRAFFIC: 5830 avg bytes, 275 avg overhead, 5830821 bytes, 275000 overhead
TIMING:  32.738 seconds, 30 rps, 182 kbps, 131.0 ms avg req time

Here is the output of qor server:
[GIN] 2017/03/21 - 19:30:11 | 200 |   97.949061ms | <IP_ADDRESS> |   GET     /
[GIN] 2017/03/21 - 19:30:11 | 200 |  190.193125ms | <IP_ADDRESS> |   GET     /
[GIN] 2017/03/21 - 19:30:11 | 200 |  125.324602ms | <IP_ADDRESS> |   GET     /
[GIN] 2017/03/21 - 19:30:11 | 200 |  120.402457ms | <IP_ADDRESS> |   GET     /
[GIN] 2017/03/21 - 19:30:11 | 200 |  135.450495ms | <IP_ADDRESS> |   GET     /
[GIN] 2017/03/21 - 19:30:11 | 200 |  144.064528ms | <IP_ADDRESS> |   GET     /
[GIN] 2017/03/21 - 19:30:12 | 200 |    94.38226ms | <IP_ADDRESS> |   GET     /
[GIN] 2017/03/21 - 19:30:12 | 200 |  184.736622ms | <IP_ADDRESS> |   GET     /
[GIN] 2017/03/21 - 19:30:12 | 200 |  132.498017ms | <IP_ADDRESS> |   GET     /
[GIN] 2017/03/21 - 19:30:12 | 200 |  173.834234ms | <IP_ADDRESS> |   GET     /
[GIN] 2017/03/21 - 19:30:12 | 200 |   151.44642ms | <IP_ADDRESS> |   GET     /
[GIN] 2017/03/21 - 19:30:12 | 200 |  160.445979ms | <IP_ADDRESS> |   GET     /
[GIN] 2017/03/21 - 19:30:12 | 200 |   99.796298ms | <IP_ADDRESS> |   GET     /
[GIN] 2017/03/21 - 19:30:12 | 200 |    95.11343ms | <IP_ADDRESS> |   GET     /

Here is another test with a scripting language httpserver that only saturate 2 cores (50% cpu load):
httpress -t 2 -c 4 -n 1000  http://<IP_ADDRESS>:8082/show-sqlar-files-for/2010
250 requests launched (1.620703 sec)
500 requests launched (1.671610 sec)
750 requests launched (1.612594 sec)
1000 requests launched (1.574440 sec)
thread 1: 502 connect, 502 requests, 502 success, 0 fail, 0 fail avg, 2379480 bytes, 58232 overhead
thread 2: 498 connect, 498 requests, 498 success, 0 fail, 0 fail avg, 2360520 bytes, 57768 overhead

TOTALS:  1000 connect, 1000 requests, 1000 success, 0 fail, 0 fail avg, 4 (4) real concurrency
TRAFFIC: 4740 avg bytes, 116 avg overhead, 4740000 bytes, 116000 overhead
TIMING:  6.512 seconds, 153 rps, 728 kbps, 26.0 ms avg req time

And here is the test of the simple qor tutorial (100% cpu load 4 cores):
httpress -t 2 -c 4 -n 1000  http://<IP_ADDRESS>:9000/admin
250 requests launched (1.589055 sec)
500 requests launched (1.550498 sec)
750 requests launched (1.560108 sec)
1000 requests launched (1.670414 sec)
thread 2: 499 connect, 499 requests, 499 success, 0 fail, 0 fail avg, 1292909 bytes, 92814 overhead
thread 1: 501 connect, 501 requests, 501 success, 0 fail, 0 fail avg, 1298091 bytes, 93186 overhead

TOTALS:  1000 connect, 1000 requests, 1000 success, 0 fail, 0 fail avg, 4 (4) real concurrency
TRAFFIC: 2591 avg bytes, 186 avg overhead, 2591000 bytes, 186000 overhead
TIMING:  6.392 seconds, 156 rps, 424 kbps, 25.6 ms avg req time

One thing that could surly remove a lot of unnecessary cycles is the render package.
It re-reads and parses the templates on each request. I opened an issue about this some time ago here and would be willing to contribute an improved version like my own but since there was no feedback yet it didn't feel like this was welcomed.

Hello @cryptix
Sorry for that, I have noticed that before.
It is welcomed of course! it would be really really helpful if you can contribute to that.

That is good to hear!
I haven't fully thought this through but my current thinking is to require the RegisterPath calls to happen before any rendering happens (during init()/before ListenAndServe) and glob all template files in these locations and parse them then.
I haven't fully studied QORs internal use of render but I think this is a solution that should work with qor/admin and other parts like qor/widget.
Does this make sense to you @jinzhu? Or are there parts that I haven't seen that depend on loading template files on-demand/user supplied?
I'm not talking about reloading templates in development. That should and will still be possible. I just want to finalize the file locations to some point so that it doesn't have to poke around the filesystem as much anymore.

Timeframe wise I don't see this happening before end of february but it is encouraging to hear this from you @jinzhu!

hi team , any progress on this  ?


Documentation for the @rotate attribute

Add basic documentation to the facsimile documentation mentioning the @rotate attribute, which follows from the TEI attribute of the same name. This corresponds to the changes in the schema PR music-encoding/music-encoding#674.

Please let me know if anything from music-encoding/music-encoding#620 should be a part of this!

I think this can be safely merged, so should be done tomorrow at ODD Friday.


bacon: init at 1.1.5

Motivation for this change
bacon was missing from nixpkgs
Things done

[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)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 121268 run on x86_64-linux 1

1 package built:

bacon

I can confirm that this builds and works on a Debian system with nix installed, i.e. the "other Linux distributions" tickybox.


Initial commit for docker image

What:
Blueflood as a container

This all seemed to work beautifully, except for the fact that I couldn't actually use ports 19000 or 20000.
I'm running a CoreOS Virtualbox box.  That might have something to do with it.  But curl'ing Blueflood to test it, I get:
curl: (7) Failed to connect to localhost port 20000: Connection refused

Which brings up another point here: this PR seems very close to working, but should we have some tests to verify that it works?  It seems like a few basic tests wouldn't be hard, but the testing infrastructure to support it is tougher.  It might also increase the time for our functional tests significantly to have a build slave download docker stuff during each run.

@stackedsax The above formula worked :smiley: Let me make a new PR, release and change the Dockerfile.

@stackedsax The above formula worked :smiley: Let me make a new PR, release and change the Dockerfile.

Testing out the updates now -- those changes will fix it, for sure.
One thing: I notice that it takes a long time for this docker up to finish.  Seems like there's a ton of apt-updating after the initial docker images are downloading (and even that takes a while...).  Shouldn't all of this updating take place beforehand and you just publish a docker image which is ready to go?
But let me check that this works in the first place and we can iterate from there.

Testing out the updates now -- those changes will fix it, for sure.
One thing: I notice that it takes a long time for this docker up to finish.  Seems like there's a ton of apt-updating after the initial docker images are downloading (and even that takes a while...).  Shouldn't all of this updating take place beforehand and you just publish a docker image which is ready to go?
But let me check that this works in the first place and we can iterate from there.

Looks almost there.  I did a new docker-compose up and could access ports 19000 and 20000 no problemo.
However, I think something with elasticsearch doesn't work.  I posted some data successfully:
curl -i -X POST 'http://localhost:19000/v2.0/100/ingest' -d   '[
>       {
>         "collectionTime":<PHONE_NUMBER>000,
>         "ttlInSeconds": 172800,
>         "metricValue": 1337,
>         "metricName": "example.metric.one"
>       },
>       {
>         "collectionTime":<PHONE_NUMBER>000,
>         "ttlInSeconds": 172800,
>         "metricValue": 1338,
>         "metricName": "example.metric.one"
>       },
>       {
>         "collectionTime":<PHONE_NUMBER>000,
>         "ttlInSeconds": 172800,
>         "metricValue": 9001,
>         "metricName": "example.metric.two"
>       }
>
>     ]'
HTTP/1.1 200 OK
Content-Length: 0

And I see ES do something with the data:
elasticsearch_1 | [2016-01-03 00:56:04,839][INFO ][cluster.metadata         ] [Atlas] [metric_metadata_write] creating index, cause [auto(bulk api)], templates [], shards [5]/[1], mappings [metrics]
elasticsearch_1 | [2016-01-03 00:56:05,811][INFO ][cluster.metadata         ] [Atlas] [metric_metadata_write] update_mapping [metrics] (dynamic)

But when I go to list those metrics like this:
curl -X GET http://localhost:20000/v2.0/100/metrics/search?query=*

Returns this:
blueflood_1     | 2016-01-03 00:56:14 ERROR pMetricsIndexHandler:56  - Exception occurred while trying to get metrics index for 100
blueflood_1     | org.elasticsearch.indices.IndexMissingException: [metric_metadata_read] missing
blueflood_1     | 	at org.elasticsearch.cluster.metadata.MetaData.convertFromWildcards(MetaData.java:884)
blueflood_1     | 	at org.elasticsearch.cluster.metadata.MetaData.concreteIndices(MetaData.java:692)
blueflood_1     | 	at org.elasticsearch.action.search.type.TransportSearchTypeAction$BaseAsyncAction.<init>(TransportSearchTypeAction.java:118)
blueflood_1     | 	at org.elasticsearch.action.search.type.TransportSearchQueryThenFetchAction$AsyncAction.<init>(TransportSearchQueryThenFetchAction.java:71)
blueflood_1     | 	at org.elasticsearch.action.search.type.TransportSearchQueryThenFetchAction$AsyncAction.<init>(TransportSearchQueryThenFetchAction.java:65)
blueflood_1     | 	at org.elasticsearch.action.search.type.TransportSearchQueryThenFetchAction.doExecute(TransportSearchQueryThenFetchAction.java:62)
blueflood_1     | 	at org.elasticsearch.action.search.type.TransportSearchQueryThenFetchAction.doExecute(TransportSearchQueryThenFetchAction.java:52)
blueflood_1     | 	at org.elasticsearch.action.support.TransportAction.execute(TransportAction.java:75)
blueflood_1     | 	at org.elasticsearch.action.search.TransportSearchAction.doExecute(TransportSearchAction.java:100)
blueflood_1     | 	at org.elasticsearch.action.search.TransportSearchAction.doExecute(TransportSearchAction.java:43)
blueflood_1     | 	at org.elasticsearch.action.support.TransportAction.execute(TransportAction.java:75)
blueflood_1     | 	at org.elasticsearch.action.support.HandledTransportAction$TransportHandler.messageReceived(HandledTransportAction.java:63)
blueflood_1     | 	at org.elasticsearch.action.support.HandledTransportAction$TransportHandler.messageReceived(HandledTransportAction.java:51)
blueflood_1     | 	at org.elasticsearch.transport.netty.MessageChannelHandler.handleRequest(MessageChannelHandler.java:222)
blueflood_1     | 	at org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:114)
blueflood_1     | 	at org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
blueflood_1     | 	at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
blueflood_1     | 	at org.elasticsearch.common.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
blueflood_1     | 	at org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:296)
blueflood_1     | 	at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462)
blueflood_1     | 	at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443)
blueflood_1     | 	at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303)
blueflood_1     | 	at org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
blueflood_1     | 	at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
blueflood_1     | 	at org.elasticsearch.common.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)
blueflood_1     | 	at org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChannelsHandler.java:74)
blueflood_1     | 	at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
blueflood_1     | 	at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)
blueflood_1     | 	at org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:268)
blueflood_1     | 	at org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:255)
blueflood_1     | 	at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)
blueflood_1     | 	at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108)
blueflood_1     | 	at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
blueflood_1     | 	at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)
blueflood_1     | 	at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
blueflood_1     | 	at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
blueflood_1     | 	at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
blueflood_1     | 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
blueflood_1     | 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
blueflood_1     | 	at java.lang.Thread.run(Thread.java:745)
Error getting metrics index

So something isn't quite right.  I'll take another look at what exactly is in ES at this point, but just wanted to let you know.
Cheers,
-Alex

I guess we have to manually create the indices beforehand, both for events and metrics. I tested the ES part by adding event first
curl -XPOST 'http://localhost:19000/v2.0/836986/events' -d '{
"what": "Test Event",
"when":<PHONE_NUMBER>1,
"tags": "Restart",
"data": "Test Data"
}'

Then querying the event:
curl -XGET 'http://localhost:20000/v2.0/836986/events/getEvents?from=14407428181&to14407428291'

it worked, but let me take a look at this case and make the necessary modifications.

Querying for the metric values themselves worked for me, just not listing the metric names.
This new release might have changed things up, though.  I heard something about needing to create ES indices first, but the older release definitely didn't need this.  I'll check it out on the vagrant image I've been working on.

although it may not be strictly necessary, to get the proper ES index aliases and mappings, I created this script:  https://github.com/rackerlabs/blueflood/blob/enums-feature/blueflood-elasticsearch/src/main/resources/init-es.sh
(It's still in the enums-feature branch.)

+1

Thanks @GeorgeJahad.
@stackedsax This issue will be fixed, once https://github.com/rackerlabs/blueflood/pull/623 is merged.


Add link to new swap input plugin readme

We have added a README for the swap input plugin that should be added to the input plugin list.
URL for relevant page?
https://docs.influxdata.com/telegraf/v1.7/plugins/inputs/
What products and version are you using?
Telegraf 1.7
Where did you look before opening the issue?
https://github.com/influxdata/telegraf/issues/4290

It looks like all system inputs are grouped under the System heading.
Would it be preferable to update the System section body to be more descriptive of what "sub" inputs it includes, or bring swap and others (cpu, disk, memory, etc.) out?
Although they technically reside under system, It seems more intuitive to find them on this list individually, rather than grouped under a more generic heading.

I would like to ungroup these plugins, to reduce confusion between system plugins and the system plugin and in the code to have a more unified style.


Map Module Scaffolding

Component infos
Description
The map module is getting ready for active development. Whilst still waiting for final specs, there's another to getting going with. Previously some map components were used in the events page which need tidying before reuse, and then a base structure put in place to make it easier for devs to work with. Specifically:

[x] Add map page container
[x] Add map store
[x] Define map pin data structures
[ ] Set bindings to read/write map pins to DB
[x] Add mock data
[ ] Add backend function to pull DH site data
[ ] (?) Add backend function to write DH site data

Added the main page container, a separate Map View container and inside direct hookup to leaflet.
Pulled the legacy map pins and just hardcoded them for now, and added a small script to convert the data format to match what we expect the final db will look like (pending whatever people decide)
Haven't got round to adding the binding for adding more pins to the DB yet, but guessing this should hopefully be enough to start with styling, clustering, filtering etc.

Now implemented with #517
Separate issue created for db related question #518
Closing.


Azure Function App with Application Insights results in duplicate trace records.

I'm trying to use ILogger.BeginScope() to add custom metadata to all of the trace records in my function for a given request but I am seeing duplicate records being created in App Insights.  One record without my metadata added and one with it added as a custom dimension.  My expectation is that a single set of log messages (no duplicates) with the expected metadata is created in App Insights. Is this an issue with Serilog or with the way I've configured my app?
Startup.cs:
[assembly: FunctionsStartup(typeof(FunctionApp_Serilog.DependencyInjection.Startup))]
namespace FunctionApp_Serilog.DependencyInjection
{
    public class Startup : FunctionsStartup
    {
        public override void Configure(IFunctionsHostBuilder builder)
        {
            builder.Services.AddLogging(builder =>
                                                   builder
                                                       .AddSerilog(
                                                           new LoggerConfiguration()
                                                               .MinimumLevel.Verbose()
                                                               .WriteTo.Console()
                                                               .WriteTo.ApplicationInsights(TelemetryConfiguration.CreateDefault(), TelemetryConverter.Traces)
                                                               .CreateLogger(),
                                                           true)
                                                       );

        }
    }

HttpTriggered Function code:

namespace FunctionApp_Serilog
{
    public class Function1
    {
        private readonly ILogger _logger;

        public Function1(ILoggerFactory loggerFactory)
        {
            _logger = loggerFactory.CreateLogger<Function1>();
        }

        [FunctionName("Function_Serilog")]
        public async Task<IActionResult> Run([HttpTrigger(AuthorizationLevel.Function, "get", Route = null)] HttpRequest req)
        {
            using (_logger.BeginScope(new Dictionary<string, Guid> { ["RequestId"] = Guid.NewGuid() }))
            {
                _logger.LogInformation("*************Log Information********************");

                _logger.LogDebug("*************Log Debug**************************");

                _logger.LogWarning("*************Log Warning**********************");

                _logger.LogCritical("*************Log Critical**********************");

                _logger.LogError("*************Log Error**********************");

                _logger.LogMetric("*************Log Metric**********************", 1.0);

                _logger.LogTrace("*************Log Trace**********************");

                var structuredExampleObj = new { Prop1 = "prop 1 value", Prop2 = "prop 2 value" };
                _logger.LogTrace($"*************Log Trace Structured:{ @structuredExampleObj }**********************");

                _logger.LogDebug("SERILOG FUNCTION FINISHED EXECUTING");
            }
            return (ActionResult)new OkObjectResult($"Serilog Function1 Finished Executing - {DateTime.Now}");
        }
    }
}

What version of Serilog.Sinks.ApplicationInsights Nuget package were you using?

What version of Serilog.Sinks.ApplicationInsights Nuget package were you using?

3.1.0

I had a similar issue and fixed it by removing the Serilog App Insights log sink. You could try that and see if it fixes it. Microsoft's built-in sink should pick up your messages automatically. You just need to set the App Insights instrumentation key in app settings.

The problem is that you effectively have two sinks picking up the same messages.

cool

This issue seems to have resolved itself.


Docs task unclear

I would like to create a Dash docset for Atom, but I can't seem to build the docs. I tried running grunt docs inside the build directory, but it can't find markdown:guides task. Running only grunt build-docs does generate something, docs/output/api.json, but I don't know where to go from here.

I tried running grunt docs inside the build directory, but it can't find markdown:guides task.

I think markdown:guides should have been deleted as a part of https://github.com/atom/atom/commit/db13a40f0a5004b1dcec1734ee907ea6d25a70ce /cc @kevinsawicki.

Running only grunt build-docs does generate something, docs/output/api.json, but I don't know where to go from here.

The api.json file is what you get (it contains descriptions of classes and methods in Atom) -- we use that on atom.io to render the API docs pages. That file is also a part of Atom's releases. Just to make sure I understand -- can you clarify what exactly you expected to see instead?

Just to make sure I understand -- can you clarify what exactly you expected to see instead?

I was hoping to be able to run the step which converts the JSON file into the API docs website (HTML/CSS/JS), so I can use it for Dash. Is that step open sourced too?

I was hoping to be able to run the step which converts the JSON file into the API docs website (HTML/CSS/JS), so I can use it for Dash. Is that step open sourced too?

As far as I know, there is no such step currently -- we don't generate the API docs as a static site. /cc @thedaniel

Oh, you generate it on the fly with JavaScript or something? Anyway, I'm closing this then.

@silvenon we import it into a db and index it in elasticsearch and render the markdown "on the fly" (well, once, then it's heavily cached) - makes it easier to have good search / more sophisticated indexing / doc versioning. It would be nice to generate a basic static HTML set with grunt though.

Cool, thanks for the explanation :smiley:


[viostor] fix incorrect IO boundary handling in RhelScsiVerify

Signed-off-by: Zhang JianMing<EMAIL_ADDRESS>for the problem description
please visit #1095

@zjmletang,  @vrozenfe can you please take a look at CI failures in Win2025?

DF - SimpleIO stress test with IO process termination (Reliability)
DF - Reboot restart with IO before and after (Reliability)

Looks like MS changed the requirements for the test: Device not configured properly for basic testing: The Disk has no volume attached to it.


kriswallsmith/buzz 0.17 not compatible with 8.0

We get the error:
Error: Uncaught exception 'Error' with message 'Call to undefined method Buzz\Client\Curl::setTimeout()' in /www/vendors/vendor/m4tthumphrey/php-gitlab-api/lib/Gitlab/Client.php:79

We solved it by adding 0.16.1 explicitly to our composer.json:
        "m4tthumphrey/php-gitlab-api":"~8",
        "kriswallsmith/buzz":"0.16.1",

Ran into this issue as well. According to semver, the 0.* releases can contain BC breaks, which sadly broke my application. I think the kriswallsmith/buzz dependency should be tighter.


Return current MICM formatted mechanisms

Handlers of requests from the MICM preprocessor should return configuration files in the current MICM format

Closing as this does not apply to the new version of chemistry cafe.