CLI exits  the process on invalid file input rather than outputing the error message

Describe the bug
When using the generate command for models , if an invalid specification file is provided then the cli exits with status code 1 but does not stdout any specific message about what error happened.
How to Reproduce
Steps to reproduce the issue. Attach all resources that can help us understand the issue:

Use command asyncapi generate models typescript asyncapi.yml

Screenshots

Link to GitHub repository with project that has issues
Files that can help reproduce the issue, like your AsyncAPI file, either paste inside the issue in a code block or in a sharable gist
File used

asyncapi: '2.5.0'
info:
  title: Streetlights API
  version: '1.0.0'
  license:
    name: Apache 2.0
    url: 'https://www.apache.org/licenses/LICENSE-2.0'
server:
  mosquitto:
    url: mqtt://test.mosquitto.org
    protocol: mqtt
channels:
  light/measured:
    publish:
      summary: Inform about environmental lighting conditions for a particular streetlight.
      operationId: onLightMeasured
      message:
        name: LightMeasured
        payload:
          type: object
          properties:
            id:
              type: integer
              minimum: 0
              description: Id of the streetlight.
            lumens:
              type: integer
              minimum: 0
              description: Light intensity measured in lumens.
            sentAt:
              type: string
              format: date-time
              description: Date and time when the message was sent.

Here the file is invalid because the server parameter is at wrong location
Expected behavior
A clear and concise description of what you expected to happen.

An error message be displayed something like : Generator Error: Input is not a corrent AsyncAPI document so it cannot be processed.
This will result in understanding what the error is about.

Additional Context

The issue is in this line
https://github.com/asyncapi/cli/blob/9c3bde73ba9e62a1b92dbda0d3c217aa94c92626/src/parser.ts#L83-L84
The issue is that instead of only returning the status of the document it is exiting the process. Rather the approach here https://github.com/asyncapi/cli/blob/9c3bde73ba9e62a1b92dbda0d3c217aa94c92626/src/commands/generate/models.ts#L146-L148 is that we handle the status and make an output of the reason.

I would like to solve this bug if this is approved

Here the file is invalid because the server parameter is at wrong location

@chinma-yyy you mean the server property does not exist ?

Here the file is invalid because the server parameter is at wrong location

@chinma-yyy you mean the server property does not exist ?

Actually this is the output when I run validate command on the specification file.

Gotcha. @chinma-yyy

IMHO,
It would be more useful if we could add more info around why things are failing instead of logging a generic message saying Generator Error: Input is not a correct AsyncAPI document so it cannot be processed.
Even if we are planning to add something of this sort (which is a good idea) I feel, we must give a more descriptive message saying why the file is invalid, Something like
Property "server" is not expected to be here
https://github.com/asyncapi/cli/blob/9c3bde73ba9e62a1b92dbda0d3c217aa94c92626/src/parser.ts#L66
FYI, If you want to construct such a message, i think the way to go is by parsing the diagonistics from here, which is an object of this type
{
  diagnostics: [
    {
      code: 'asyncapi-defaultContentType',
      message: 'AsyncAPI document should have "defaultContentType" field.',
      path: [],
      severity: 1,
      source: 'asyncapi.yaml',
      range: [Object]
    },
    {
      code: 'asyncapi-id',
      message: 'AsyncAPI document should have "id" field.',
      path: [],
      severity: 1,
      source: 'asyncapi.yaml',
      range: [Object]
    },
    {
      code: 'asyncapi-servers',
      message: 'AsyncAPI document should have non-empty "servers" object.',
      path: [],
      severity: 1,
      source: 'asyncapi.yaml',
      range: [Object]
    },
    {
      code: 'asyncapi2-tags',
      message: 'AsyncAPI object should have non-empty "tags" array.',
      path: [],
      severity: 1,
      source: 'asyncapi.yaml',
      range: [Object]
    },
    {
      code: 'asyncapi-latest-version',
      message: 'The latest version of AsyncAPi is not used. It is recommended update to the "2.6.0" version.',
      path: [Array],
      severity: 2,
      source: 'asyncapi.yaml',
      range: [Object]
    },
    {
      code: 'asyncapi-info-contact',
      message: 'Info object should have "contact" object.',
      path: [Array],
      severity: 1,
      source: 'asyncapi.yaml',
      range: [Object]
    },
    {
      code: 'asyncapi-info-description',
      message: 'Info "description" should be present and non-empty string.',
      path: [Array],
      severity: 1,
      source: 'asyncapi.yaml',
      range: [Object]
    },
    {
      code: 'asyncapi-document-resolved',
      message: 'Property "server" is not expected to be here',
      path: [Array],
      severity: 0,
      source: 'asyncapi.yaml',
      range: [Object]
    },
    {
      code: 'asyncapi2-message-messageId',
      message: 'Message should have a "messageId" field defined.',
      path: [Array],
      severity: 1,
      source: 'asyncapi.yaml',
      range: [Object]
    }
  ]
}

The default failSeverity is 0. So we can construct a message appending the messages with severity: 0

Please feel free to criticize :slightly_smiling_face:
@Souvikns What do you think ? Is it better to just give out a generic error message and let the user run the validate command or is it better to go one step ahead and show user what's making it fail ?

Yeah, I think it is better to log a meaningful error and show why it is failing, nice idea @kaushik-rishi we should use the diagnostics for a better error log. I think we should just use this https://github.com/asyncapi/cli/blob/master/src/parser.ts

Will go ahead and create one PR resolving the bug

@chinma-yyy

Will go ahead and create one PR resolving the bug

Yeah, it's more of an improvement than a bug if you want to call it that way.
Extract the logic of constructing the error message from the diagnostics into a separate function and let me know if you need any help 🙂


flagpack gradient and shadow?

how do we take advantage of the original flagpack options?
https://flagpack.xyz/docs/design/#styles
https://www.npmjs.com/package/react-flagpack
hoping for all props to become available

It is not planned to introduce these features as they might increase bundle size significantly or mess up with tree-shaking

why would it increase bundle size or mess up tree shaking? these are just css classes
see here https://github.com/Yummygum/react-flagpack/blob/main/src/Flag.scss#L100
and usage here https://github.com/Yummygum/react-flagpack/blob/main/src/Flag.tsx#L27

@rtivital any update?

I'm not planning to work on this any time soon. If you want this feature, you are welcome to submit a PR. Note that you will need to test that tree shacking works.


EITC parameters

reform = {2016:{"_EITC_rt":[[0.08415, 0.374, 0.44, 0.495]],
                "_EITC_prt": [[0.08415, 0.17578, 0.23166, 0.23166]]}}

It seems this reform has inconsistent results between taxcalc and TaxBrain. Using taxcalc, the difference between baseline and reform is within 2 billions, but on TaxBrain the difference is roughly between 70 - 80 billions, running separately or combined together.
@talumbau @MattHJensen @martinholmer

closed via #203


[Android] Attmpt to invoke method setAREventListener on null object reference

Problem
After calling cameraDeepArController.dispose on Android this platform exception is thrown.
[ERROR:flutter/lib/ui/ui_dart_state.cc(209)] Unhandled Exception: PlatformException(error, Attempt to invoke virtual method 'void ai.deepar.ar.DeepAR.setAREventListener(ai.deepar.ar.AREventListener)' on a null object reference, null, java.lang.NullPointerException: Attempt to invoke virtual method 'void ai.deepar.ar.DeepAR.setAREventListener(ai.deepar.ar.AREventListener)' on a null object reference

The app continues to work if you continue in the debugger, however when the DeepAR camera is loaded again the effects do not get applied, and when the controller gets disposed again, the same exception gets thrown, and not calling controller.dispose  makes everything to work properly with no issues.
Steps to reproduce

Create and Initialize an instance of CameraDeepArController
Call controller.dispose in the dispose method of the widget
Dispose of the widget

Possible Cause
After looking through the code a bit it seems that this line which sets in HandleCameraDeepAr.java could be the cause
https://github.com/mtellect/CameraDeepAR/blob/32ba7e9c8d08a4dbcb69a6e124e768b82b800162/android/src/main/java/com/camera_deep_ar/handlers/HandleDeepAr.java#L249

Thanks I'd take a look

Is there any updates with this issue?

Any change?

I don't think there has been any updates on this, however DeepAR has created their own Flutter plugin, I haven't had a chance to try it out yet, but it's their official plugin, so I'd imagine it's pretty stable. https://github.com/DeepARSDK/deepar-flutter-plugin


Update plan_patterns.py

Description

Motivation and Context

How Has This Been Tested?

Re-running the tests....

Can we either document this as an aspect ratio or as major/minor axes?
I suspect the generalization we want here is actually the full set of ellipse parameters (5 dof: x-center, y-center, major/minor axis, and a rotation angle).

So the ‘asymetry’ term that I use is the same as the 'aspect ratio’, if it is clearer to label it ‘aspect' this could easily be changed. But in my mind ‘aspect' is defined relative to the x and y axes whereas  ‘asymetry’ is defined relative to some arbitrary axis along which the symmetry is broken. This may just be due to my training in crystallography however !-).
In fact we have all 5 dof’s.
input values related to the ellipse are x_start, y_start, dr, asym and tilt.
These are related to the 5 dof’s specified as
x-center = x_start
y-xenter = y_start
major/minor axis = dr (depending if asym is < or > 1)
minor/major axis = dr* asym (depending if asym is < or > 1)
tilt = rotation angle
The benefit of using asymmetry instead of axis for me is that asymmetry is a more logical “optional” parameter than “major/minor axis” (personal preference). In addition there is no confusion regarding which axis needs to be major and which is minor, as that is defined within the asymmetry term.
Anyway as this is really a philosophical argument about naming conventions I leave the decision up to the DAMA group.
cheers
Andrew
Andrew Walter
Assc. Physicist
Brookhaven National Laboratory
Photon Sciences, NSLS 2
Building 741
Upton, New York
USA 11973
phone: office +1<PHONE_NUMBER>
beamline +1<PHONE_NUMBER>
email: awalter<EMAIL_ADDRESS>On Mar 5, 2017, at 9:28 PM, Thomas A Caswell <notifications<EMAIL_ADDRESS>wrote:
Can we either document this as an aspect ratio or as major/minor axes?
I suspect the generalization we want here is actually the full set of ellipse parameters (5 dof: x-center, y-center, major/minor axis, and a rotation angle).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/NSLS-II/bluesky/pull/656#issuecomment-284287892, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AYlCpULOpxa_d2_2ypPfn9Wgui9q8cy4ks5ri29XgaJpZM4MRcv2.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@0d3d0c0). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master     #656   +/-   ##
=========================================
  Coverage          ?   82.68%
=========================================
  Files             ?       20
  Lines             ?     4378
  Branches          ?        0
=========================================
  Hits              ?     3620
  Misses            ?      758
  Partials          ?        0

Impacted Files
Coverage Δ

bluesky/plan_patterns.py
97.26% <100%> (ø)

Continue to review full report at Codecov.

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

Superceded by #675


Update random number generator to use C++11 standard library

Currently, our random number generator uses boost random library, which has largely been supplanted by C++11.  This PR updates the random number tools to use the C++11 intrinsics.
This change is needed to allow us to transition to C++17.  In c++17, std::random_shuffle is removed in place of std::shuffle, which is no longer compatible with the boost random generators.  This requires us to change the base random generators to the c++11 versions, and thus swap out the distributions to the c++11.   After this PR, we no longer depend on boost random.
The c++11 versions allow us to simplify a couple of things:

C++11 provides a true-random generator, which can replace our complicated, platform-specific version.
C++11's mt19937_64 benchmarks as one of the fastest random number generators on modern hardware (e.g. https://gist.github.com/MikeLing/d258cf0c7e18d17639c577a695dbec41), so there is no point in having separate fast_ versions.  This PR consolidates these.  This change is in the second commit.

@hoytak - will this change impact our users? Is there functionality where the same data and the same seed will now produce different results? If so, what functionality is affected?


docs(CONTRIBUTING): update release checklist

Added missing points to the release notes, including updating the website after we modify the docs.
Not sure how much detail to go into about redeploying the website. I think we could look into how we create a GitHub Action that auto-deploys when the docs directory is updated

@mikehardy I'll address the website deployment in another p/r.


feat: update design system colors

Added back primary and secondary text color variables
Updated all colors to match the new Design System colors
Standardized borders to use border color, and set it to be gray-6, which is aligned with Radix's color science.
Fixes constant declared inside ViewMode, which is usually used in client components, being imported by server components.
Fixes Bridge Skeleton/Loading state not matching new size of elements
Fixes label contrast color in brand/green accent buttons, now set to #111111
Added prefetch to Transaction ViewMode links

transaction and block page not accessible, internal server error 500

Next.JS still executes some client-component code during SSR or SSG, even for client components, and router.prefetch called in ViewMode accesses window internally, which causes the error in prod.
I've fixed the code to only run client side.


Upgrade controller-runtime to v0.3.0

Upstream k8s libs are updated to kubernetes-1.15.4 release tag
Fixed many API breaking changes
Logic regarding checking version of CCM is removed

What this PR does / why we need it:
Takes advantage of newer and better controller-runtime APIs
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Upgrade controller-runtime to v0.3.0

/hold
hack with cache drop (resolved upstream) to be removed

/hold cancel


chore(ci): test against node 0.12 instead of 0.11

Travis seems to be under maintenance. Will retry tomorrow.

Merged with 32a4a0d3d0696c73704a36bcf06f81fd6fa023a4


Any Row as Header

Include the ability to make any row in the table act as a header row

Won't Do


Hey....I am stuck

Challenge Size your Images has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
 You haven't applied the smaller-image class to the img element yet.
Please visit the Help Room for help with issues like these, in future! This place is for reporting bugs with the website itself. Happy Coding!

thanks a lot
On 23 November 2016 at 21:36, Manish Giri<EMAIL_ADDRESS>wrote:

@emboruett https://github.com/emboruett Your code is incomplete. You
haven't applied the smaller-image class to the img element yet.
Please visit the Help Room https://gitter.im/FreeCodeCamp/Help for help
with issues like these, in future! This place is for reporting bugs with
the website itself. Happy Coding!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/11780#issuecomment-262596851,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWkFp7RzHHfnlDViocthxHJPZz4dqZwJks5rBIfFgaJpZM4K66qc
.


[FIX] Scaling XR Providers

Summary
Fixes a bug introduced around https://github.com/ultraleap/UnityPlugin/commit/2e48d9ba1e1d460161cfd45d294379bab7e553ee which breaks LeapXRPinchLocomotion.
Reviewer Tasks

[x] Code reviewed.
[ ] Checked and agree with release testing considerations added to MR for the next release.

Closes Issue
Fixes this bug reported by @Dwarph.

Have pulled this change - will do some testing on it.

@zalo so those changes fix the ability to use the Pinch Locomotion script without weird scaling stuff becoming unstable. What I did notice though is when you pinch with both hands to scale the scene, the capsule hands also scale. Was that intentional or has something else got lost/broken? Also what's the script ordering meant to fix?
https://user-images.githubusercontent.com/53301524/196404155-d48661d7-78ac-483b-b24d-231eb7aeb1e1.mp4

@MaxPalmer-UH On the contrary, the capsule hands are not scaling with the rest of the provider+rig.
Are your capsule hands in the same transform hierarchy as both your Service Provider and main camera rig?   My rig is: Rig Parent -> XR Provider -> Left/Right Capsule Hand.

OK, making the capsule hand a child of the rig stops the scaling. A rigged hand will still scale, I presume this is expected?


Unable to install GPU version of Pennylane-Qulacs

Hi, I am trying to install Pennylane-Qulacs GPU with python3.11 and Pennylane.
My Pennylane info is as follows:
Name: PennyLane
Version: 0.35.0
Summary: PennyLane is a cross-platform Python library for quantum computing, quantum machine learning, and quantum chemistry. Train a quantum computer the same way as a neural network.
Home-page: https://github.com/PennyLaneAI/pennylane
Author:
Author-email:
License: Apache License 2.0
Location: /usr/local/lib/python3.11/dist-packages
Requires: appdirs, autograd, autoray, cachetools, networkx, numpy, pennylane-lightning, requests, rustworkx, scipy, semantic-version, toml, typing-extensions
Required-by: pennylane-qulacs, PennyLane_Lightning, PennyLane_Lightning_GPU

Platform info:           Linux-6.5.0-25-generic-x86_64-with-glibc2.35
Python version:          3.11.0
Numpy version:           1.26.3
Scipy version:           1.12.0
Installed devices:
- lightning.qubit (PennyLane_Lightning-0.35.1)
- qulacs.simulator (pennylane-qulacs-0.32.0)
- default.clifford (PennyLane-0.35.0)
- default.gaussian (PennyLane-0.35.0)
- default.mixed (PennyLane-0.35.0)
- default.qubit (PennyLane-0.35.0)
- default.qubit.autograd (PennyLane-0.35.0)
- default.qubit.jax (PennyLane-0.35.0)
- default.qubit.legacy (PennyLane-0.35.0)
- default.qubit.tf (PennyLane-0.35.0)
- default.qubit.torch (PennyLane-0.35.0)
- default.qutrit (PennyLane-0.35.0)
- null.qubit (PennyLane-0.35.0)
- lightning.gpu (PennyLane_Lightning_GPU-0.35.1)

When I enter
sudo pip3.11 install --upgrade qulacs-gpu
I get the following error:
Collecting qulacs-gpu
  Using cached Qulacs-GPU-0.3.1.tar.gz (209 kB)
  Preparing metadata (setup.py) ... done
Building wheels for collected packages: qulacs-gpu
  Building wheel for qulacs-gpu (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> [173 lines of output]
      running bdist_wheel
      running build
      running build_ext
      /tmp/pip-install-8o8kjk9r/qulacs-gpu_dc39012c072548388f98f5526c10dac2/setup.py:48: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.
        cmake_version = LooseVersion(re.search(r'version\s*([\d.]+)', out.decode()).group(1))
      /tmp/pip-install-8o8kjk9r/qulacs-gpu_dc39012c072548388f98f5526c10dac2/setup.py:18: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.
        version = LooseVersion(out)
      /tmp/pip-install-8o8kjk9r/qulacs-gpu_dc39012c072548388f98f5526c10dac2/setup.py:19: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.
        return version >= LooseVersion('7.0.0')
      /tmp/pip-install-8o8kjk9r/qulacs-gpu_dc39012c072548388f98f5526c10dac2/setup.py:18: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.
        version = LooseVersion(out)
      /tmp/pip-install-8o8kjk9r/qulacs-gpu_dc39012c072548388f98f5526c10dac2/setup.py:19: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.
        return version >= LooseVersion('7.0.0')
      CMake Warning (dev) in CMakeLists.txt:
        No project() command is present.  The top-level CMakeLists.txt file must
        contain a literal, direct call to the project() command.  Add a line of
        code such as

          project(ProjectName)

        near the top of the file, but after cmake_minimum_required().

        CMake is pretending there is a "project(Project)" command on the first
        line.
      This warning is for project developers.  Use -Wno-dev to suppress it.

      -- The C compiler identification is GNU 11.4.0
      -- The CXX compiler identification is GNU 11.4.0
      -- Detecting C compiler ABI info
      -- Detecting C compiler ABI info - done
      -- Check for working C compiler: /usr/bin/gcc - skipped
      -- Detecting C compile features
      -- Detecting C compile features - done
      -- Detecting CXX compiler ABI info
      -- Detecting CXX compiler ABI info - done
      -- Check for working CXX compiler: /usr/bin/g++ - skipped
      -- Detecting CXX compile features
      -- Detecting CXX compile features - done
      CMake Deprecation Warning at CMakeLists.txt:2 (cmake_minimum_required):
        Compatibility with CMake < 2.8.12 will be removed from a future version of
        CMake.

        Update the VERSION argument <min> value or use a ...<max> suffix to tell
        CMake that the project does not need compatibility with older versions.

      -- SIMD SUPPORT: Yes
      -- CMAKE_HOST_SYSTEM_PROCESSOR = x86_64
      -- USE_SIMD = Yes
      -- USE_OMP = Yes
      -- USE_GPU = Yes
      -- USE_TEST = Yes
      -- USE_PYTHON = Yes
      -- OPT_FLAGS = -mtune=native -march=native -mfpmath=both
      -- Fetch googletest for C++ testing
      CMake Deprecation Warning at build/temp.linux-x86_64-cpython-311/_deps/googletest_fetch-src/CMakeLists.txt:1 (cmake_minimum_required):
        Compatibility with CMake < 2.8.12 will be removed from a future version of
        CMake.

        Update the VERSION argument <min> value or use a ...<max> suffix to tell
        CMake that the project does not need compatibility with older versions.

      CMake Deprecation Warning at build/temp.linux-x86_64-cpython-311/_deps/googletest_fetch-src/googlemock/CMakeLists.txt:42 (cmake_minimum_required):
        Compatibility with CMake < 2.8.12 will be removed from a future version of
        CMake.

        Update the VERSION argument <min> value or use a ...<max> suffix to tell
        CMake that the project does not need compatibility with older versions.

      CMake Deprecation Warning at build/temp.linux-x86_64-cpython-311/_deps/googletest_fetch-src/googletest/CMakeLists.txt:49 (cmake_minimum_required):
        Compatibility with CMake < 2.8.12 will be removed from a future version of
        CMake.

        Update the VERSION argument <min> value or use a ...<max> suffix to tell
        CMake that the project does not need compatibility with older versions.

      -- Found PythonInterp: /usr/bin/python3.11 (found version "3.11")
      -- Looking for pthread.h
      -- Looking for pthread.h - found
      -- Performing Test CMAKE_HAVE_LIBC_PTHREAD
      -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
      -- Found Threads: TRUE
      -- Fetch pybind11 for python-binding
      -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.11.so
      -- Performing Test HAS_CPP14_FLAG
      -- Performing Test HAS_CPP14_FLAG - Success
      -- pybind11 v2.5.0
      -- Install from pip
      -- OUTDIR = /tmp/pip-install-8o8kjk9r/qulacs-gpu_dc39012c072548388f98f5526c10dac2/build/lib.linux-x86_64-cpython-311
      -- CMAKE_SYSTEM_NAME = Linux
      -- CMAKE_C_COMPILER = /usr/bin/gcc
      -- CMAKE_CXX_COMPILER = /usr/bin/g++
      -- CMAKE_BUILD_TYPE = Release
      -- CMAKE_CXX_FLAGS = -DVERSION_INFO=\"0.3.1\" -std=gnu++14 -pthread -fext-numeric-literals -fopenmp -fPIC
      -- CMAKE_CXX_FLAGS_DEBUG = -g
      -- CMAKE_CXX_FLAGS_RELEASE = -O3 -DNDEBUG -mtune=native -march=native -mfpmath=both
      CMake Deprecation Warning at src/CMakeLists.txt:1 (cmake_minimum_required):
        Compatibility with CMake < 2.8.12 will be removed from a future version of
        CMake.

        Update the VERSION argument <min> value or use a ...<max> suffix to tell
        CMake that the project does not need compatibility with older versions.

      CMake Deprecation Warning at src/csim/CMakeLists.txt:1 (cmake_minimum_required):
        Compatibility with CMake < 2.8.12 will be removed from a future version of
        CMake.

        Update the VERSION argument <min> value or use a ...<max> suffix to tell
        CMake that the project does not need compatibility with older versions.

      CMake Deprecation Warning at src/gpusim/CMakeLists.txt:1 (cmake_minimum_required):
        Compatibility with CMake < 2.8.12 will be removed from a future version of
        CMake.

        Update the VERSION argument <min> value or use a ...<max> suffix to tell
        CMake that the project does not need compatibility with older versions.

      CMake Error at /usr/share/cmake-3.22/Modules/FindCUDA.cmake:859 (message):
        Specify CUDA_TOOLKIT_ROOT_DIR
      Call Stack (most recent call first):
        src/gpusim/CMakeLists.txt:3 (find_package)

      -- Configuring incomplete, errors occurred!
      See also "/tmp/pip-install-8o8kjk9r/qulacs-gpu_dc39012c072548388f98f5526c10dac2/build/temp.linux-x86_64-cpython-311/CMakeFiles/CMakeOutput.log".
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-install-8o8kjk9r/qulacs-gpu_dc39012c072548388f98f5526c10dac2/setup.py", line 111, in <module>
          setup(
        File "/usr/local/lib/python3.11/dist-packages/setuptools/__init__.py", line 103, in setup
          return distutils.core.setup(**attrs)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/usr/local/lib/python3.11/dist-packages/setuptools/_distutils/core.py", line 185, in setup
          return run_commands(dist)
                 ^^^^^^^^^^^^^^^^^^
        File "/usr/local/lib/python3.11/dist-packages/setuptools/_distutils/core.py", line 201, in run_commands
          dist.run_commands()
        File "/usr/local/lib/python3.11/dist-packages/setuptools/_distutils/dist.py", line 969, in run_commands
          self.run_command(cmd)
        File "/usr/local/lib/python3.11/dist-packages/setuptools/dist.py", line 963, in run_command
          super().run_command(command)
        File "/usr/local/lib/python3.11/dist-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/usr/local/lib/python3.11/dist-packages/wheel/bdist_wheel.py", line 368, in run
          self.run_command("build")
        File "/usr/local/lib/python3.11/dist-packages/setuptools/_distutils/cmd.py", line 318, in run_command
          self.distribution.run_command(command)
        File "/usr/local/lib/python3.11/dist-packages/setuptools/dist.py", line 963, in run_command
          super().run_command(command)
        File "/usr/local/lib/python3.11/dist-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/usr/local/lib/python3.11/dist-packages/setuptools/_distutils/command/build.py", line 131, in run
          self.run_command(cmd_name)
        File "/usr/local/lib/python3.11/dist-packages/setuptools/_distutils/cmd.py", line 318, in run_command
          self.distribution.run_command(command)
        File "/usr/local/lib/python3.11/dist-packages/setuptools/dist.py", line 963, in run_command
          super().run_command(command)
        File "/usr/local/lib/python3.11/dist-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/tmp/pip-install-8o8kjk9r/qulacs-gpu_dc39012c072548388f98f5526c10dac2/setup.py", line 50, in run
          self.build_extension(ext)
        File "/tmp/pip-install-8o8kjk9r/qulacs-gpu_dc39012c072548388f98f5526c10dac2/setup.py", line 108, in build_extension
          subprocess.check_call(['cmake', ext.sourcedir] + cmake_args, cwd=self.build_temp, env=env)
        File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
          raise CalledProcessError(retcode, cmd)
      subprocess.CalledProcessError: Command '['cmake', '/tmp/pip-install-8o8kjk9r/qulacs-gpu_dc39012c072548388f98f5526c10dac2', '-DCMAKE_LIBRARY_OUTPUT_DIRECTORY=/tmp/pip-install-8o8kjk9r/qulacs-gpu_dc39012c072548388f98f5526c10dac2/build/lib.linux-x86_64-cpython-311', '-DCMAKE_RUNTIME_OUTPUT_DIRECTORY=/tmp/pip-install-8o8kjk9r/qulacs-gpu_dc39012c072548388f98f5526c10dac2/build/lib.linux-x86_64-cpython-311', '-DPYTHON_EXECUTABLE=/usr/bin/python3.11', '-DPYTHON_SETUP_FLAG:STR=Yes', '-DCMAKE_C_COMPILER=gcc', '-DCMAKE_CXX_COMPILER=g++', '-DCMAKE_BUILD_TYPE=Release', '-DUSE_GPU:STR=Yes']' returned non-zero exit status 1.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for qulacs-gpu
  Running setup.py clean for qulacs-gpu
Failed to build qulacs-gpu
ERROR: Could not build wheels for qulacs-gpu, which is required to install pyproject.toml-based project

I am wondering what this means, and how I can fix it. Thank you very much for your help.

Hi @JustinS6626! This looks like an error compiling Qulacs for GPUs on your system; unfortunately, we'll likely be unable to help you out here, as this looks to be an issue with Qulacs. I suggest opening an issue in the Qulacs GitHub here: https://github.com/qulacs/qulacs

Thank you very much for getting back to me! I actually succeeded in overcoming the issue for Qulacs-GPU using the command
USE_GPU=Yes sudo pip3.11 install --no-build-isolation .

Could it work for pennylane-qulacs-gpu as well?


ng-swipe-up/down disables default swipe-up/down behavior of the browser

for instance, if i got a very long div, when use ng-swipe-up directive , i want to see the details on the end of div, it will not move the long div up.

occurs both in PC and Mobile device.

It seems that it blocks scrolling.
You should be able to see the issue in Chrome Dev tools (mobile device tools) by creating an instance of div  that has long, scrolling content


ARROW-7681: [Rust] Explicitly seeking kills BufRead performance.

BufRead will discard its internal buffer when seek() is called. This
kills much of the performance of a buffered reader, especially when many
tiny (1-byte) reads are performed.

edit: disregard, I don't think this works; it doesn't provide methods for getting at the underlying reader which are required by a few areas in the Parquet code.

Hey @maxburke, I'll wait for a second review from another Arrow commiter before merging this, because we introduce the 2 unstable flags.
CC @liurenjie1024 @paddyhoran @andygrove

Thanks @maxburke Left some comments. If this is a serious bug fix or impacting users heavily, I would suggest merging this when this feature got merged into stable rust.

I share the concerns about further reliance on nighly Rust. Let's revisit this for the release after 0.17.0

@maxburke can you please test master, an alternative solution has been provided by #6949. If it doesn't resolve the problem, we can reopen this PR.


fix Issue: jaroWinkler gives score > 1 for distinct strings

Bug: distinct strings with common prefixes get a weight > 1.0
jaroWinkler('commonlongprefixword', 'commonlongprefixworm')
The former code easily gives weights > 1.0 for distinct strings.

Hello @jfseb. Thanks for noticing this one. Reading my code again, I also found some other inconsistencies, notably normally for Jaro-Winkler, the size of the common prefix should not be exceeding 4. Let me some time to document myself again more thoroughly on the metric so I can fix it correctly.

@jfseb I'm gonna go ahead and merge your PR and fix the code even more.


Release to npm

We should release it so users can use our CLI and API easily

Oh, it's already published


buckle: init at 1.1.0

Description of changes
Buckle is a launcher for buck2, similar to bazelisk for Bazel.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@thoughtpolice can I interest you in a buck2-related review? :)

Thanks for the review @Aleksanaa, I have added your suggestions to the commit.


FarCor.MyFarAnti-Virus version 4.31.3102.572

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Which type of evidence we can provide for URLs validation.

You need to prove that the URL is from the Official Website since it does not match the Publisher.


Add drift method to Simulator

Add drift method to allow us to simulate drift. Initial thoughts

add functionality into the mass spec to allow us to calculate drift
add column / drift class which takes time and returns shifted time to query chemical
Make no changes to chemical class, just query it at a different time

Easiest option is that we insert something in this method...
https://github.com/sdrogers/vimms/blob/a13520ca79870751843ac72dbdc7df5147f43ae8/vimms/MassSpec.py#L600
to map the query_rt to adjusted_query_rt or something...

Should an rt mapping be deterministic in the sense that f(x) should always return the same for a given x?
Some probably should. But also could imagine a NoisyColumn that generates noise?

The reason for above question is that I think we'll end up calling it more often than once per RT

Yes, once generated f(x) should have no noise. This is important for both checking multiplce chemicals at the same RT (simons comment above) and also if we wanted to test multiple methods on the same f(x) for a comparison. You could however generate multiple f(x) using the same process which would have noise

Thinking more on this. Be useful to have input from @RonanDaly ...
If we add drift as proposed above, peak shapes will get warped. Is that what we want? The alternative is that we apply the warping to the peak RTs in the chemical list before we start the environment...

Might have to be a little careful doing that as long tails at the front of the chromatogram could make estimating the drift function near impossible. Suggest if we do what you suggest above, that we drift the top of the peaks maybe?

Doing which? Moving the chemical RT?
Not sure what difference it makes drifting the top or the start? They have a fixed length, so moving the start by 10s is the same as moving the top by 10s? But I suspect I misunderstood your comment.

For fixed length simulated peaks, yes it doesn't make a difference. If we used real data, converted into ROIs/chemicals and then added drift it would make a different, but I guess we wouldnt necessarily do this. For example, a chromatogram starting at rt=100 but the peak only appearing at rt=600 could get 1 sec drift (due to start rt=100). Similarly a chromatogram starting at rt=500 and the peak appearing at rt=600 could get 5 seconds drift (due to start rt=500). The peaks would be appearing at the same time, but because of when the noisy chromatogram started, they would have completely different drift

Talking to Stefan now, it seems like this is the correct option: 'The alternative is that we apply the warping to the peak RTs in the chemical list before we start the environment...'. He says that the main drift is a physical shift of the chemicals, rather than a warping of the chemicals. He also said that its quite important that two chemicals that are at the same RT won't necessarily drift the same amount. Suggest that when generating the drift for each chemical that we add noise (ie random sample from prior at a the RT) such that two chemicals with the same RT don't have the same RT after drift

That’s useful - so a column in our world is something that provides a new rt for each chemical that has some drift term (ie new rt is function of old rt) and a random term


Need Customize Lane component

I want to customize the Lane component in a way that it can have multiple sections.
For Example
If I have LightVehicles card I want to have sections for 2 wheeler, 3 wheeler, 4 wheeler.
Currently what I am doing is, I am adding a 'type' property for each card, and while displaying it with a different color based on the type. In my case 2, 3, and 4 wheeler.
The problem here is, when I am dragging 2 wheeler over to the other lane, say for example HeavyVehicles, then, I have to again sort the whole lane to differentiate between the 2,3, & 4 wheelers.
I want to have a Title for each section.
Or also we can have nested lanes, but having an option to customize the Lane Component will be much easier.

@abdulkhaliquem9 The library supports straight forward use-cases trying to keep the design closer in spirit to a trello board.
But, you are free to customize the lane look-and-feel by defining your own custom template:
Refer example here:
https://rcdexta.me/react-trello/?selectedKind=Custom Templates&selectedStory=Custom Lane Template&full=0&addons=0&stories=1&panelRight=0
Corresponding code here:
https://github.com/rcdexta/react-trello/blob/master/stories/CustomLaneStyling.story.js


Fix for issue #35 (brainfuck_insert_after() corrupts instruction lists)

Moved next initialization to before after->next gets set, so next will hold the original tail.

Great! Thank you!


[BUG] Running 'ninja -C out/host' requires zap-cli

Reproduction steps

cd to connectedhomeip
Run gn gen  out/host
Run ninja -C out/host

Note: Running on macOS
Bug prevalence
Always
GitHub hash of the SDK that was being used
89c6fb677e9f02a0ee51f25a9636a60c070e7f3b
Platform
darwin
Platform Version(s)
N/A
Anything else?
The issue started to occur in this PR.

This is expected behavior...  What's not expected is xcodebuild needing zap-cli.


do not truncate display for hover

close #4311

Can you add a test for this in case someone changes it in the future?

@kjeremy it's done :) thanks for the review

bors r+


Users can cancel auto-merge on their own PR's

The previous behavior was that auto-merge could not be canceled by a user to prevent PR's from piling up.
With the new behavior, users can cancel Auto-Merge on their own PR's with no way to re-enable it.

Ref https://github.com/microsoft/winget-pkgs/pull/96100

Related to https://github.com/microsoft/winget-pkgs/issues/95543

Related to:

https://github.com/microsoft/winget-pkgs/issues/95543

This is more likely a GitHub thing, but maybe fabric bot could do something here.

Looking into this more... this is definitely a change due to the fact that we've basically gone from running our own infrastructure and auto merge functionality to 'simply enabling' the native automerge under certain conditions.
I'm willing to bet we could fix it with a new repo-defined task if it's not considered desirable behavior; basically, capture the event in which a user cancels the PR and then simply re-enable it, although that might lead to excess activity.  Still, I think that should be something that's more or less doable now.  I'll have to check the new code base we're running on to see if we have a "cancelled automerge" event / how it comes in (nothing obvious springs to mind).
Other than writing up the template for how to do this in the new YML format when we get it out there, I'm not sure there's anything we can do code wise on our end.  I'll reference this in our backlog as a potential documentation / investigation to see how we can reach feature parity, so to speak.

Out of curiousity, how important is this feature for your workflow?

Out of curiousity, how important is this feature for your workflow?

I think it would be rare for users to cancel their own auto-merge, so this is probably an edge case; However, it is important that when a PR meets all the criteria, it gets merged. I think there may be workarounds with the new format such as having a "merge" action instead of using automerge, but if PR's aren't merged, updates to packages won't be available to end users.

https://github.com/microsoft/winget-pkgs/issues/96183
These two have the same root cause (how GH handles automerge).  It's technically a bug that we don't have the full support for automerge handled (I have some PRs out to 'fix' said bug by adding in what we need) but I still would like to see if there's a policy option that could be used, as fighting against GH with FabricBot actions is... not ideal in terms of traffic and etc.   So in terms of re-enabling automerge there might be a better solution.
Having said dealing with automerge related events are a thing that we receive in the app, so at the very least they can be utilized in the workflow graph.

I've started trying to reach out to the team at GH responsible for automerge just to get the ball rolling; in the meantime I've made some very tiny changes to the gitops base to make sure these events are forwarded on to FabricBot so that users can apply workarounds (as well as reacting to automerge events in other situations too!).
Let's keep in contact here re: how the automerge change in general is disrupting your workflow, as that might influence our backlog and how we prioritize pushing features out if things aren't able to worked with as is.!

OK, maybe it could be another rule to add a label for our team to know which ones we need to manually merge, and some message to the author regarding the disable automerge coming from GitHub.

I'm going to close this as with the new GitOps framework we can check to re-enable automerge on any Pull_Request event, which should trigger the rule even when a user tries to cancel the automerge on their own PR


release SAP BTP service operator

Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Does your operator have nested directory structure?
[ ] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[x] Are you familiar with our contribution guidelines?
[x] Have you packaged and deployed your Operator for Operator Framework?

[x] Is your submission signed?
[x] Is operator icon set?

Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Submit operators to both upstream-community-operators and community-operators at once
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

ready for merge

I see that this i your first version. You are using old manifest format and new bundle format exists. I would recommend you to use bundle format because manifest format will be soon deprecated. In short you will move csv and crds to manifest directory and port package file to metadata/annotations.yaml file. Here is an example https://github.com/operator-framework/community-operators/tree/master/upstream-community-operators/cockroachdb/2.0.9

Hi,
is there any tool that converts to new structure I am not sure how to create the annotations.yaml

I am now getting this error:
fatal: [localhost]: FAILED! => changed=false
msg: Operator 'sap-btp-operator/0.1.1' is running in 'semver' mode and contains 'replaces' key in '/tmp/community-operators-for-catalog/upstream-community-operators/sap-btp-operator/0.1.1/manifests/sap-btp-operator.v0.1.1.clusterserviceversion.yaml' !!!

@pavelmaliy It depends what you want. If you want to run in semver mode you have to remove replaces fields in csv. If you want to run replaces mode you have to create file ci.yaml like this


 This helps you complete a pull request. Please follow the instructions below. Reminder that you are bound to abide by the Code of Conduct
Description
Tell us about your pull request!
Please make sure your submission is in the correct directory. In most cases, this is in submissions/YOUR-USERNAME/filename.
For example, if @ipaye is completing Day 1:

I read the solved the Day 1 task.
I create 2 new documents inside _submissions/ipaye/Day1
I title these documents guessgame.js_

You can find complete details in the submission instructions for each module.
Labels - DELETE THIS SECTION AFTER COMPLETING
Apply the following labels:

Module number.
What is it? Application, bug, submission or feature request.

Labels - DELETE THIS SECTION AFTER COMPLETING
Apply the following labels:
Module number.
What is it? Application, bug, submission or feature request.
Module number should be Day............each folder should be for a day and not module. Eg instead of module 0, module 1, we should have Day 1, Day 2


ix-menu does not open when below the "sm" breakpoint if there are multiple instances of ix-basic-navigation

What happened?
If there is more than one instance of ix-basic-navigation created on the page, and while below the "sm" breakpoint of ix-basic-navigation, clicking on the menu button does not open the menu.
Multiple instances of ix-basic-navigation may get created if it gets removed from the DOM and then added again (using ngIf in Angular for example), or if you have a different ix-basic-navigation component on different pages.
When a new instance of ix-basic-navigation is created on the page, you can see a warning in the console saying: "Menu already defined".
What type of frontend frameware are you seeing the problem on?
Angular
Which version of iX do you use?
2.0.3
Code to produce this issue.
A simple method to reproduce, although it's not a real example, is:

Create 2 ix-basic-navigation components on the same page.
Resize the browser's window until you reach the "sm" breakpoint.
Click on the menu button of the first ix-basic-navigation, you should notice the menu opens normally.
Click on the menu button of the second ix-basic-navigation, you should notice the menu of the first component is the one that incorrectly opens, while the menu of the second component does not open.

Demo:
https://stackblitz.com/edit/stackblitz-starters-kshyhf?file=src%2Fapp%2Fapp.component.ts
Example code:
@Component({
  selector: 'my-app',
  standalone: true,
  imports: [CommonModule, IxModule],
  template: `

      Please resize the browser window until you reach the "sm" breakpoint

        <ix-basic-navigation>

          <ix-menu>
            <ix-menu-item homeTab icon="home">Page 1</ix-menu-item>
          </ix-menu>

Page 1

        </ix-basic-navigation>

        <ix-basic-navigation>

          <ix-menu>
            <ix-menu-item homeTab icon="home">Page 2</ix-menu-item>
          </ix-menu>

Page 2

        </ix-basic-navigation>

  `,
  styles: [
    `
      :host {
        display: flex;
        flex-direction: column;
        width: 100vw;
        height: 100vh;
      }

      .header {
        text-align: center;
        color: darkorange;
      }

      @media (max-width: 768px) {
        .header {
          display: none;
        }
      }

      .content {
        flex: 1;
        display: flex;
        justify-content: center;
      }

      .nav-container {
        padding: 1rem;
        flex: 1;
      }

      ix-basic-navigation {
        background-color: rgba(255, 255, 255, 0.3);
      }

      ix-basic-navigation div {
        flex: 1;
        padding: 1rem;
        text-align: center;
      }
    `,
  ],
})
export class AppComponent {}

Internal ref [IX-862]


Boost changes are not reflected in sending data

Steps to reproduce
In the game:update_state section, add a player and change the boost value from 33 to 100.
What is expected?
Boost changes are not reflected in sending data.
What is actually happening?
inputBoost() may not be called depending on the result of filterBoost().

Has been fixed in the recent commit, thanks for the issue 😄


BTM and Oracle XA database links

Hi
We got app based on Oracle+BTM+SpringFramerwotk+Hibernate
and I see resource leak if XA transaction contain operation on database links.
Resurces are released on application kill.
I know. this is common problem http://stackoverflow.com/questions/5088934/how-can-i-close-oracle-dblinks-in-jdbc-with-xa-datasources-and-transactions-to-a
but how to add additional action 'alter session close database link ' after transaction commit /rollback

You could register a synchronization (http://docs.oracle.com/javaee/5/api/javax/transaction/Synchronization.html) in the current transaction that would execute the alter session query.
Now the way to get the current transaction in which you can register the synchronization and a jdbc connection to run the query highly depends on your spring/hibernate stack.


"SQL Server Previous Versions Documentation" page contains dead links for most prior SQL Server versions

This page contains a link to online documentation for versions of SQL Server prior to SQL Server 2016: "SQL Server previous versions documentation", https://learn.microsoft.com/en-us/previous-versions/sql/.  That page contains dead links for SQL Server versions 2005 to 2012.  Only the link to SQL Server 2014 is still active.
If the only way to obtain documentation for SQL Server 2005 to 2012 is to download offline documentation please state that rather than give us false hope by directing us to a page which turns out to be dead links.

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

ID: 444e750b-2eb3-722c-bd43-16963e35248a
Version Independent ID: b4351b94-6403-4efa-9e8f-3738211ce849
Content: Previous versions of SQL Server documentation - SQL Server
Content Source: docs/sql-server/previous-versions-sql-server.md
Service: sql
Sub-service: install
GitHub Login: @markingmyname
Microsoft Alias: maghan

Duplicate of https://github.com/MicrosoftDocs/sql-docs/issues/9193.


How to disable jinjax for specific lines

Hello,
I'm very new to JinjaX and I have an issue while trying to integrate it with an existing Jinja2 application.
I have this line of code in my jinja template. It assign a very specific string value to a variable and it should not get expanded by JinjaX.
{% set dom_without_length_change = "<'d-sm-flex align-items-center'<'mb-1 flex-grow-1'i><'mb-1'f><B>><'row'<'col-sm-12'rt>><'row'<'mt-2'p>>" %}

When compiling template, I get this error.
jinja2.exceptions.TemplateSyntaxError: Unclosed component <B>

Is it possible to disable JinjaX rendering for this specific line. Or maybe there is another workaround ?
Thanks

Ho I think I figure it out looking at the code. I'm not sure it's this feature is document in the doc.
{% raw %}
{% set dom_without_length_change = "<'d-sm-flex align-items-center'<'mb-1 flex-grow-1'i><'mb-1'f><B>><'row'<'col-sm-12'rt>><'row'<'mt-2'p>>" %}
{% endraw %}

This works:
{% set dom_without_length_change = "<'d-sm-flex align-items-center'<'mb-1 flex-grow-1'i><'mb-1'f><" + "B>><'row'<'col-sm-12'rt>><'row'<'mt-2'p>>" %}

Sorry, it's a crappy solution, but it works until I use a real parser instead of regular expressions


Travis not able to publish

Description:
Not sure what happened here. Just merging this PR like normal when this happened. The PR didn't change any of the secure things tho.
Versions affected:
dev
Reproduction:
https://travis-ci.org/ractivejs/ractive/builds/209964279
Code:
publishing as unstable edge build to npm...
npm ERR! Linux 4.8.12-040812-generic
npm ERR! argv "/home/travis/.nvm/versions/node/v6.10.0/bin/node" "/home/travis/.nvm/versions/node/v6.10.0/bin/npm" "publish" "--tag" "v0.9-dev"
npm ERR! node v6.10.0
npm ERR! npm  v3.10.10
npm ERR! code ENEEDAUTH
npm ERR! need auth auth required for publishing
npm ERR! need auth You need to authorize this machine using `npm adduser`

Took a shot in the dark and added NPM_TOKEN to Travis, to no avail.
Found an older build that had encountered this error, and a follow-up build that made it work or at least got past the auth error. The fix appears to be adding an encrypted variable, but I don't know what it contains.
Thoughts @evs-chris ?

So it turns out that running npm with auth via an npm script was the issue. I'd guess that npm strips out the auth env variables to prevent accidental leakage when you use run-script. Seems to be ok now though.

🤦♂ A big "today I learned" moment for me. 😄


fix(c_sharp): modified queries to avoid inner objects to contain braces

Don't use C#, but these changes seem to be enough

Works as expected


enable RST longdesc

Looks pretty on Pypi. Also added some badges.

Thx! The check fails here (although README.rst has been generated):
$ make README.rst
pandoc README.md -o README.rst
python setup.py check -r -s || exit 1
running check
warning: check: Could not finish the parsing.

error: Please correct your package.
make: *** [README.rst] Error 1

Any idea why this happens?

No idea. Cannot reproduce either with
$ pandoc --version
pandoc <IP_ADDRESS>
Compiled with texmath <IP_ADDRESS>, highlighting-kate <IP_ADDRESS>.
Syntax highlighting is supported for the following languages:
    actionscript, ada, apache, asn1, asp, awk, bash, bibtex, boo, c, changelog,
    clojure, cmake, coffee, coldfusion, commonlisp, cpp, cs, css, curry, d,
    diff, djangotemplate, doxygen, doxygenlua, dtd, eiffel, email, erlang,
    fortran, fsharp, gcc, gnuassembler, go, haskell, haxe, html, ini, isocpp,
    java, javadoc, javascript, json, jsp, julia, latex, lex, literatecurry,
    literatehaskell, lua, makefile, mandoc, markdown, matlab, maxima, metafont,
    mips, modelines, modula2, modula3, monobasic, nasm, noweb, objectivec,
    objectivecpp, ocaml, octave, pascal, perl, php, pike, postscript, prolog,
    pure, python, r, relaxngcompact, restructuredtext, rhtml, roff, ruby, rust,
    scala, scheme, sci, sed, sgml, sql, sqlmysql, sqlpostgresql, tcl, texinfo,
    verilog, vhdl, xml, xorg, xslt, xul, yacc, yaml
Default user data directory: /home/nschloe/.pandoc
Copyright (C) 2006-2014 John MacFarlane
Web:  http://johnmacfarlane.net/pandoc
This is free software; see the source for copying conditions.  There is no
warranty, not even for merchantability or fitness for a particular purpose.

$ python --version
Python 2.7.9

OK, maybe it's my older pandoc or python version:
$ pandoc --version
pandoc <IP_ADDRESS>
Compiled with texmath <IP_ADDRESS>, highlighting-kate <IP_ADDRESS>.
Syntax highlighting is supported for the following languages:
    actionscript, ada, apache, asn1, asp, awk, bash, bibtex, boo, c, changelog,
    clojure, cmake, coffee, coldfusion, commonlisp, cpp, cs, css, curry, d,
    diff, djangotemplate, doxygen, doxygenlua, dtd, eiffel, email, erlang,
    fortran, fsharp, gnuassembler, go, haskell, haxe, html, ini, java, javadoc,
    javascript, json, jsp, julia, latex, lex, literatecurry, literatehaskell,
    lua, makefile, mandoc, markdown, matlab, maxima, metafont, mips, modelines,
    modula2, modula3, monobasic, nasm, noweb, objectivec, objectivecpp, ocaml,
    octave, pascal, perl, php, pike, postscript, prolog, python, r,
    relaxngcompact, rhtml, roff, ruby, rust, scala, scheme, sci, sed, sgml, sql,
    sqlmysql, sqlpostgresql, tcl, texinfo, verilog, vhdl, xml, xorg, xslt, xul,
    yacc, yaml
Default user data directory: /home/andre/.pandoc
Copyright (C) 2006-2013 John MacFarlane
Web:  http://johnmacfarlane.net/pandoc
This is free software; see the source for copying conditions.  There is no
warranty, not even for merchantability or fitness for a particular purpose.

$ python --version
Python 2.7.5+

I'll simply ignore the error, ha! :smile:


building from source doesn't work

Building framework from source doesn't work anymore, i followed successfully the procedure until it says to open the TesseractOCR.xcodeproj and build the "TesseractOCRAggregate" but in the project there is not target called in this way. Instead there is a TesseractOCR.framework and this is not an aggregate framework, in the project also miss a script that build aggregate framework. Maybe needs an update to documentation?

No need, since you are reffering a documention for the latest release, but use the developer branch.
Pls, refer README_howto_compile_libaries.md and Makefile from the sources.
I'm closing the issue.
Feel free to reopen it, if the proposed doesn't help you.

i followed also that procedure, i obtain all compiled libraries but not any framework, suggestions?

There is no need in "TesseractOCRAggregate" target anymore, since it did the same as Makefile does.
If you need a framework, pls, check all the available targets. There is a TesseractOCR. It will create a framework from those .a files you've made with Makefile, as I remember.
Also, "TesseractOCRAggregate" exists in 4.0.0 release as I remeber. If not, sorry.


Turn off syntax highlighting for shell or when no language is specified

Use no syntax highlighting if

```
```

or

```sh
```

This works now. SO closing it. Harsha added github-markup support and it works.


fix browser test env debug port

Description
Browser test env outter and inner ports don't match, so this fixes that
I had to do this to get IntelliJ debugger to communicate with the container

I just ran bin/run-browser-tests-ci locally and that passed.


Relationship table selection overwrites $table

The table select overwrites the $table which is used on line 55 in a belongsto relationship.
Instead of the selected table it will show the last table from the foreach loop

Thanks for this!


[refactor] restore consensus committed sub dags from last index + 1

Description
Following this work https://github.com/MystenLabs/sui/pull/13819 we can now safely restore the committed sub dags from the last index + 1 since the consumer is atomically processing all the transactions and we don't need to re-send the last index subdag.
Test Plan

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] protocol change
[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

I'm unfamiliar with consensus handler and I'm actually not sure about this change. last_executed_sub_dag_index() reads from the last_consensus_index table, which has an ExecutionIndices field that gets updated for every transaction processed in the consensus handler.
What if a consensus output has 10 transactions, and the node crashed after processing 7 transactions? Will the remaining 3 transactions be skipped after this change? We should run some restart tests with high consensus handler load, e.g. in private testnet. I'm open to be convinced if this is not an issue.

Ok, so updates to last_consensus_index are in a batch per consensus commit in process_consensus_transactions_and_commit_boundary(). This change should be fine as long as the Sui per-commit logic is indeed atomic.

I think this should work now that ConsensusHandler is atomic - it either will process all transactions in commit or none.
But lets add a big warning to the ConsensusHandler saying that code there should stay atomic, since we now rely on it in narwhal.
Let's also confirm we don't have a problem when we pass last_executed_sub_dag_index=0 to narwhal in the beginning of the epoch (e.g. we still replay from very beginning in that case)

@andll I can confirm that the recovery will work as expected with last_executed_sub_dag_index = 0 because we always publish the first committed sub dag with index = 1.
Regarding the ConsensusHandler being atomic there is already a comment , but as a best effort attempt I've also added a simtest test_consensus_handler_atomic to ensure this - so at least if someone accidentally breaks the atomicity assumption we do have something that might catch it (under assumptions) apart from the other sim tests. New test here https://github.com/MystenLabs/sui/pull/13901/commits/2ebaa10a33d8d66794fb198a9f41dfaebd221685
CC @mystenmark @mwtian


Publish gRPC Release Schedule

Release schedule (feature window closing and anticipated release dates) roadmap should be publicly posted on the grpc.io website

https://github.com/grpc/grpc/blob/master/doc/grpc_release_schedule.md


Lock sidebar menu hidden when refresh page

After reloading or refreshing the page, the sidebars appear and then disappear. How to prevent this behavior by default?

This sounds more like an issue with your code than the plugin, so this would be better asked on Stack Overflow. If this is actually an issue with the Plugin, please resubmit your issue using the template provided.


Removed Google Code mention

Removed mention of Google Code. As its closed. Added GitLab mention instead

:pizza: !


generate uf2 artifact for feather

I always forgot to update the ci yml :sweat_smile:

I always forgot to update the ci yml :sweat_smile:


I need /etc/pip.conf to point to my pypi proxy

Is your feature request related to a problem? Please describe.
We have our pypi proxy, but not a proxy. In air-gapped environments I would like to get at pypi libraries published by the organization.
Describe the solution you'd like
I'd like to use a template for /etc/pip.conf
Describe alternatives you've considered
File in each homedir is maintenance burden.
Additional context
# /etc/pip.conf
[global]
## Proxy config for Python libraries. Example:
## index-url = https://user:password@proxy:8443/artifactory/pypi/pypi-virtual/simple
{% if artifactory_hostname is defined%}
index-url = https://{{ artifactory_hostname }}:{{ artifactory_port  }}/{{ artifactory_repo_path }}
# cert = {{certificate_path }}
{% endif %}

Cool, I'll work on it.
Thanks @bbaassssiiee for your feedback.


Event loop is closed when testing with TestClient

I try to follow FastAPI docs on testing,
and I'm getting RuntimeError: Event loop is closed error when I have ratelimiter enabled.
In main.py:
async def _dummy_auth_function(scope: Scope) -> tuple[str, str]:
    return "dummy_uid", "default"

app.add_middleware(
    RateLimitMiddleware,
    authenticate=_dummy_auth_function,
    backend=RedisBackend(StrictRedis(
        ...
    )),
    config={
        r"^/v3/": [Rule(minute=1000, second=20)],  # <-- Works when this is deleted
    },
)

My test_ping.py file:
import pytest
from fastapi.testclient import TestClient

from .main import app

client = TestClient(app)

@pytest.mark.integration()
def test_ping():
    response = client.get("/v3/test/ping")
    response = client.get("/v3/test/ping")  # <-- this doesn't work
    assert response.status_code == 200

This code fails with Event loop is closed on second request,
unless the endpoint is not ratelimited.

Please use https://www.starlette.io/testclient/#asynchronous-tests

I did try it, but I'm still having the same error:
@pytest.mark.asyncio()
async def test_ping():
    async with AsyncClient(app=app, base_url="http://test") as client:
        response = await client.get("/v3/test/ping")
        response = await client.get("/v3/test/ping")  # <-- works

@pytest.mark.asyncio()
async def test_pong():
    async with AsyncClient(app=app, base_url="http://test") as client:
        response = await client.get("/v3/test/ping")  # <-- fails
        response = await client.get("/v3/test/ping")


训练技巧提问

尊敬的作者您好，我在尝试复现您的论文PNS-Net网络，在您提供的数据集上进行预训练和微调，测试结果在Dataset:CVC-ColonDB-300数据集上没有达到论文中给的精度，三个训练集的评价指标结果如下。
(Dataset:CVC-ClinicDB-612-Test) meanDic:0.774;meanIoU:0.696;wFm:0.765;Sm:0.864;meanEm:0.857;MAE:0.051;maxEm:0.884;maxDice:0.803;maxIoU:0.729;meanSen:0.757;maxSen:0.992;meanSpe:0.975;maxSpe:0.985.
(Dataset:CVC-ClinicDB-612-Valid) meanDic:0.843;meanIoU:0.756;wFm:0.824;Sm:0.922;meanEm:0.936;MAE:0.013;maxEm:0.966;maxDice:0.883;maxIoU:0.810;meanSen:0.862;maxSen:0.991;meanSpe:0.968;maxSpe:0.978.
(Dataset:CVC-ColonDB-300) meanDic:0.654;meanIoU:0.551;wFm:0.617;Sm:0.838;meanEm:0.797;MAE:0.025;maxEm:0.835;maxDice:0.693;maxIoU:0.590;meanSen:0.764;maxSen:1.000;meanSpe:0.978;maxSpe:0.990.
麻烦请教一下您，训练模型时有什么其他的技巧吗？另外，预训练和微调之后的网络模型测试评价指标差距不是很大，可以增加微调epoch或者有其他方法增强微调网络的性能吗？多有打扰。
Pretrain【epoch100】
(Dataset:CVC-ClinicDB-612-Test) meanDic:0.771;meanIoU:0.693;wFm:0.770;Sm:0.856;meanEm:0.852;MAE:0.050;maxEm:0.888;maxDice:0.811;maxIoU:0.736;meanSen:0.734;maxSen:0.992;meanSpe:0.974;maxSpe:0.983.
Finetune【epoch1】
(Dataset:CVC-ClinicDB-612-Test) meanDic:0.774;meanIoU:0.696;wFm:0.765;Sm:0.864;meanEm:0.857;MAE:0.051;maxEm:0.884;maxDice:0.803;maxIoU:0.729;meanSen:0.757;maxSen:0.992;meanSpe:0.975;maxSpe:0.985.

Hi, @Moqixis
Sorry for the late reply. Since we got a very, very limited video dataset for this task before submission, we adopted two-stage training to achieve promising performance. But, in general, the two-stage models indeed have some tricky training treatments, incurring them hard to train. Thus, please fine-tune your model before ensuring the best pre-training performance you can ever get, and then try to fine-tune your model on video datasets by using a small learning rate, fixing the static branch, or something else. You can feel free to discuss me with your experience for more inspiration.
I also note that there has a similar issue #13. Today, we retrain our model on the pre-trained weight and get a similar performance reported in our conference paper. Next is the comparison; please check it out.
Original Performance:

(Dataset:CVC-ClinicDB-612-Test) Sm:0.903;meanEm:0.903;MAE:0.038;maxEm:0.923;maxDice:0.860;maxIoU:0.795;maxSpe:0.992.
(Dataset:CVC-ClinicDB-612-Valid) Sm:0.923;meanEm:0.944;MAE:0.012;maxEm:0.962;maxDice:0.873;maxIoU:0.800;maxSpe:0.991.
(Dataset:CVC-ColonDB-300) Sm:0.909;meanEm:0.921;MAE:0.013;maxEm:0.942;maxDice:0.840;maxIoU:0.745;maxSpe:0.996.

New Performance (that we retrained again):

(Dataset:CVC-ClinicDB-612-Test) Sm:0.891;meanEm:0.876;MAE:0.043;maxEm:0.921;maxDice:0.854;maxIoU:0.785;maxSpe:0.995.
(Dataset:CVC-ClinicDB-612-Valid) Sm:0.917;meanEm:0.923;MAE:0.013;maxEm:0.952;maxDice:0.861;maxIoU:0.787;maxSpe:0.991.
(Dataset:CVC-ColonDB-300) Sm:0.897;meanEm:0.892;MAE:0.012;maxEm:0.936;maxDice:0.833;maxIoU:0.734;maxSpe:0.997.

These numerical results show some performance fluctuations due to different random seed or PyTorch versions or something. But I think it is acceptable for us. It does not show a 'huge' drop after the fine-tuning process.
Thank you all guys to pay attention to our work. Further problems and discussions are welcome here.
ONE MORE THING We also release a large-scale VPS dataset, named SUN-SEG to promote this field. By using this dataset, you can feel free to train your large model without no worries about over-fitting problems. You can also discard the two-stage training strategy using our enhanced method, PNS+, which only needs training once. We strongly suggest you use them.
Best,
Ge-Peng.

Hi, @Moqixis
Sorry for the late reply. Since we got a very, very limited video dataset for this task before submission, we adopted two-stage training to achieve promising performance. But, in general, the two-stage models indeed have some tricky training treatments, incurring them hard to train. Thus, please fine-tune your model after ensuring the best pre-training performance you can ever get, and then try to fine-tune your model on video datasets by using a small learning rate, fixing the static branch, increasing the fine-tuning epochs, or something else. You can feel free to discuss me with your experience for more inspiration.
I also note that there has a similar issue #13. Today, we retrain our model on the pre-trained weight and get a similar performance reported in our conference paper. Next is the comparison; please check it out.
Original Performance:

(Dataset:CVC-ClinicDB-612-Test) Sm:0.903;meanEm:0.903;MAE:0.038;maxEm:0.923;maxDice:0.860;maxIoU:0.795;maxSpe:0.992.
(Dataset:CVC-ClinicDB-612-Valid) Sm:0.923;meanEm:0.944;MAE:0.012;maxEm:0.962;maxDice:0.873;maxIoU:0.800;maxSpe:0.991.
(Dataset:CVC-ColonDB-300) Sm:0.909;meanEm:0.921;MAE:0.013;maxEm:0.942;maxDice:0.840;maxIoU:0.745;maxSpe:0.996.

New Performance (that we retrained again):

(Dataset:CVC-ClinicDB-612-Test) Sm:0.891;meanEm:0.876;MAE:0.043;maxEm:0.921;maxDice:0.854;maxIoU:0.785;maxSpe:0.995.
(Dataset:CVC-ClinicDB-612-Valid) Sm:0.917;meanEm:0.923;MAE:0.013;maxEm:0.952;maxDice:0.861;maxIoU:0.787;maxSpe:0.991.
(Dataset:CVC-ColonDB-300) Sm:0.897;meanEm:0.892;MAE:0.012;maxEm:0.936;maxDice:0.833;maxIoU:0.734;maxSpe:0.997.

These numerical results show some performance fluctuations due to different random seed or PyTorch versions or something. But I think it is acceptable for us. We don't take further action to improve the performance as we just fine-tune our model with one epoch. Overall It does not show a 'huge' drop after the fine-tuning process.
Thank you all guys to pay attention to our work. Further problems and discussions are welcome here.
ONE MORE THING We also release a large-scale VPS dataset, named SUN-SEG to promote this field. By using this dataset, you can feel free to train your large model without worries about over-fitting problems. You can also discard the two-stage training strategy using our enhanced method, PNS+, which only needs training once. We strongly suggest you use them.
Best, Ge-Peng.

谢谢您的回复，我再尝试尝试。


Black for Code formatting

Could we use Black for code formatting? That would be easier for contributors.
Black has the following features:

it is very predictable (unsurprising choices).
it is a very popular formatting standard
4 spaces = the standard for Python and even for Google Python Style Guide
it hosted by the Python Software Foundation
it minimizes git diffs
integrates well with other tools (so a contributor does not have to customize other tools for 2 spaces)

it can be controlled via pyproject.toml (example here)
pylint, flake8, etc are all happy with its results
it can format inside Jupyter notebooks

A typical counter argument is that Black increases the number of lines, but in practice, @michalk8 and I checked that a 980 lines file grows only by 60 lines, which is about 6%.
I think these are pretty strong arguments in its favor.

For 2 spaces indentation with yapf, the only positive point that I can think of is:

used in many jax libraries

My counter arguments are:

it does not play nice with pylint and other tools, because they 4 spaces
the 2 spaces convention currently enforced by yapf is inconsistent because function arguments are indented with 4 spaces.

What do you think?

@michalk8 has also noticed that there are some libraries in the Jax ecosystem that do use 4 spaces: https://github.com/patrick-kidger/equinox

i think that the argument for jax libraries is that google/ and dm/ jax libraries are 2 spaces. Outside of that people are free :)

If we can configure blue to have 2 spaces, I'd go for it (and keep the rest default), relly mist string normalization.

I don't think that'll be happening anytime soon. :)
https://github.com/psf/black/issues/378

;) true, but @michalk8 was referring to Blue

That's what I get for responding before my first ☕ !

I think the 2 vs. 4 debate never ends :)
For 80 character lines, I think 2 spaces is more reasonable. I kind of like 80 characters, it makes coding a bit easier...
Since this is the way the project runs now, and I don't see an obvious tipping point here, I'd stick to this choice. However, happy to switch to Blue! And I agree that yapf has a weird behavior w.r.t function arguments, with 4 spaces thrown in here and there.

Ok, I'll rename the issue accordingly ;)

If we can keep 2/80 i am all in favor and see no downside

I suggest we leave this issue open until the change is proposed in a PR.

If we can configure blue to have 2 spaces, I'd go for it (and keep the rest default), relly mist string normalization.

I looked at blue, it doesn't seem to have the option to use 2 spaces unfortunately.

Hi, should we close this issue? It seems to me that most of people in this thread are happy with 2 spaces and Yapf is the only well-known formatter which allows that.

Agree, closing this!


serializers: datacite serialization of publication year

The RDM datamodel contains a publication_date which is handled by a marshmallow_utils.EDTFDateString field. This can also handle ranges... Datacite serialziation requires a publicationYear.

[ ] How to obtain the year from the given string
[ ] Can the EDTFDateString be reused and some how made accessible the year?

publicationYear is not a well-loved field in DataCite, since the actual data fields are much more descriptive. It's used for citation purposes, but DataCite will prioritize the date field if they are present. I would keep things simple and just strip out the year, or the first year in a range.

So it will always favor the Issued date... Can actually "publication dates" have ranges?

It's a real uncommon edge case. The only scenario I can imagine is if you're putting a whole bunch of journal articles into a single record.
I've done some testing, and with the Rest API DataCite actually accepts a range for publicationYear but only saves the first year. I think we should follow this implementation and only send the first year. It could be as simple as just returning the first 4 numbers in the EDTFD date.

Agree with Tom, simply usage first possible year of publication


Release engineering: enable Go Releaser on tags in Travis CI

While the 0.9.1 is in RC, why not enabling Go Releaser to build binaries and put them in GitHub releases page ?
Based on the branch of this PR I released a fake version on my repository simply by creating and pushing the v0.9.99 tag. Before that a GITHUB_TOKEN environment variable with a GitHub token (with write:packages role) must be added in Travis CI.

So this just add binaries with the releases, right ?Are there any other reasons for having this?

Yes and it can also creates nice changelogs and release notes according to configuration.
It's very straightforward for releaser as it is only a tag to create and push.
For end users, it's easier to download a prebuilt binary sometimes. go get always pull the latest (unstable?) version and building a specific version from source implies to git clone, git checkout the right tag (after finding its name) and go install (pretty complicated for just the CLI).


Error: Deploying with winrm

Providing a value for the winrm_listeners like the below:
 winrm_listeners = [     {       protocol        = "Http"     }   ]
gives an error:

│ Error: Invalid function argument
│
│   on .terraform/modules/vm01/main.windows_vm.tf line 151, in resource "azurerm_windows_virtual_machine" "this":
│  151:     for_each = { for listener in var.winrm_listeners : sha256(listener) => listener }
│
│ Invalid value for "str" parameter: string required.

The line in main.windows_vm.tf is:
https://github.com/Azure/terraform-azurerm-avm-res-compute-virtualmachine/blob/27d9ec63b9344740e51bdd67dc0e3cf9bb15685c/main.windows_vm.tf#L151
Changing the line to :
for_each = { for listener in var.winrm_listeners : sha256(jsonencode(listener)) => listener } resolves it and the vm is deployed with winrm configured. Can you please check/advise? Thank you.

@ptsouk - Thank you for this, I will run the review and make the changes this afternoon and test.  Should be able to get an updated version out later today if everything goes ok.

@ptsouk - this has been corrected in release 0.7.0.  Can you please confirm that this resolves your issue?


rest api server running fail

Environment

OS: centos6.5
Erlang/OTP:
EMQ: 2.3

Description
the listener for the rest api not running, but when i use the command emqttd_ctl listeners start mqtt:api 8099, it showed Failed to restart mqtt:api listener on 8099, error:not_found  , 8099 is the port for the api server in the config file.
How should i start the server? Thx

The mqtt:api port defaults to 8080. You can't start the api port because someone else has already listened on it, right ?
You could change the configuration and restart the emq for now, I'll look at the emqttd_ctl listeners restart problem.
## Default: <IP_ADDRESS>:8080
listener.api.mgmt = <IP_ADDRESS>:8099

I don't know what you want. The listener for rest api would be started after emqttd starting unless the 8080 port has been occupied by other application. If you want to to change the rest api port, change it in  etc/emq.conf, then restart emqttd.
If you want to change listen port of rest api when emqttd is running, it is a new feature for us

@terry-xiaoyu  I don't think this is bug. It looks like @wormcc 's problem. Maybe he needs a new feature. But I assume that this is not a good idea which want to change rest api listener's port when emqttd has been started.

@Gilbert-Wong Thanks for the reply, i have changed the default port 8080 to 8099 in the emq.conf, then i restarted the broker, but the rest api server did not run, and the 8099 port  wasn't occupied by other application either.

Execute ./bin/emqttd_ctl listeners and tell me what's printed on terminal


Fix release image prefix

Fix #580

Not the right direction, good PR here : https://github.com/open-telemetry/opentelemetry-operator/pull/581


Add final where it's missing

We can always remove them later if someone really needs to extend one of the exception classes.
Maybe we should have an interface for Listener?

a) Aerys is extending Listener (it's extending it with a Stream interface for getting the whole msg at once) [thus, just no.]
b) LazyPromise is fine with final
c) If you already acknowledge if someone really needs to extend one of the exception classes the case, why do you even consider them as final? Please don't then.

c) If you already acknowledge if someone really needs to extend one of the exception classes the case, why do you even consider them as final? Please don't then.

I only said that, because I assumed it's the reason they're not final. I don't see a real reason to extend these.

Only one I have an issue with is Listener since that class is extended in a couple of Amp libs. I suppose we could make an interface and wrap it in those libs, but is that necessary?

@kelunik I don't see a real reason for forbidding extension of the interfaces…


Is there a way to get the entire catalog of GUNW of metadata?

Is your feature request related to a problem? Please describe.
I want to get all the metadata for the entire catalog of GUNWs and make a pretty picture. I always get a subset (~150k products when there is 400k+). Do I have split up the globe?
Describe the solution you'd like
results = asf.search(processingLevel=[asf.PRODUCT_TYPE.GUNW_STD], maxResults=1_000_000) gives me all GUNW metadata
Describe alternatives you've considered
Not much.
Additional context
Make pretty pictures.

I see similar truncated search results with asf_search 3.2.1 on python 3.10.4:
>>> import asf_search
>>> results = asf_search.search(processingLevel=[asf_search.PRODUCT_TYPE.GUNW_std])
>>> results = asf_search.search(processingLevel=[asf_search.PRODUCT_TYPE.GUNW_STD])
>>> len(results)
112831
>>> asf_search.__version__
'3.2.1'

I'd expect over 471,000 results as of this writing: https://cmr.earthdata.nasa.gov/search/granules?provider=ASF&collection_concept_id=C1595422627-ASF&page_size=0

Currently, asf_search relies on our SearchAPI as its backend, which has a ~15-minute time limit on how long it'll allow queries to run, it's possible you're running into that. We have some backlog to alleviate that, but in the mean time, a simple solution would be to break up the query by years (probably simpler than by geospatial).
Some quick checking indicates each year there are fewer than 100k products (about 90k in 2018 and 2019 each, significantly less in other years), which should complete well within the SearchAPI's time limit.

Thank you!


[Profiler] Fix autoclosure property wrapper crash

We need to query the top-level expression, not the sub-expression of a potential function conversion.
rdar://99449154
Resolves #60908

@swift-ci please test


Focus on obscureText TextField, a black screen appear

Focus on obscureText TextField, a black screen appears, and press the back button to return to the TextField screen;
My device is Huawei P30.
Simple code:
Scaffold(
	body: Container(

		child: TextField(
			obscureText: true,
		),
	),
)

[✓] Flutter (Channel master, v1.9.8-pre.38, on Mac OS X 10.14.6 18G87, locale zh-Hans-CN)
    • Flutter version 1.9.8-pre.38 at /usr/local/opt/flutter
    • Framework revision c4d54743b1 (3 days ago), 2019-08-31 16:35:41 -0400
    • Engine revision 4b22bc1bd9
    • Dart version 2.5.0 (build 2.5.0-dev.4.0 36985859e4)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/ppyupp/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • ANDROID_HOME = /Users/ppyupp/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 10.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.3, Build version 10G8
    • CocoaPods version 1.6.1

[✓] Android Studio (version 3.4)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 37.0.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[✓] VS Code (version 1.37.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.4.0

[✓] Connected device (1 available)
    • iPhone Xʀ • EC7C58BB-8F88-439C-AE37-7838D7EACDDA • ios • com.apple.CoreSimulator.SimRuntime.iOS-12-4 (simulator)

• No issues found!

I definitely don't see this problem in the simulator, but maybe it has to do with the device.  I'll try to find a similar Huawei device to try it on.

Yes, the Android emulator does not have this problem.
I only found this problem on Huawei p30 and Huawei Honor 20, Other Android devices(Xiaomi Mi 8, VIVO, OPPO) don't have this problem.

I tried this on the following devices, and I couldn't reproduce it on any of them:

Huawei Honor V8 running Android 8
Huawei Nova 4 (Android 9)
Huawei P20 Pro Android 8
Huawei EVA-TL00 Android 6

I just ran the app, tapped on the input, and typed some text.  Am I doing something wrong?  Here's my code:
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
        textSelectionHandleColor: Colors.greenAccent,
      ),
      home: Scaffold(
        body: Center(
          child: TextField(obscureText: true),
        ),
      ),
    );
  }
}

HI @ppyupp
This is not reproducible on Samsung device too  and based on this comment confirmation also not reproducing this issue, i feel safe to close this issue
if you're still experiencing this problem, please create a new issue and provide the information
required in the template.
Thank you


Refactor to avoid conflicts between Permission.excludes and Permission.needs

We can get into a weird state with conflicting logic by doing the following:
d = Denial(('a', 'c'))
p = Permission(('a', 'c'))

u = d.union(p)
#  now u has ('a', 'c') in BOTH needs and excludes

With this refactoring, a need can be needed or excluded, but not both. This change is not expected to break anything and just handle the edge case described above.

closes #78


Change examples to use the system fonts OSes are actually using

Guys, this is not optimal.
Please provide examples with the fonts the OSes are actually using. If they use the best font, and the assumption is yes, I would like to use it as well.
Why do you think I need to see an example with Lobster font?!
Thanks

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

ID: fe0572c4-91be-fc86-d130-242db2bf470b
Version Independent ID: 1238fdd7-c378-6d0d-654e-55656a70d386
Content: Fonts in Xamarin.Forms - Xamarin
Content Source: docs/xamarin-forms/user-interface/text/fonts.md
Product: xamarin
Technology: xamarin-forms
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Hi @lnaie
Unfortunately, the only reliable way to use the same font cross-platform is to use a custom font (e.g. Lobster), which is why the doc shows this approach.
This is because different platforms ship different fonts, and the presence of a font on a platform does not mean it's present in other versions of the platform, or even in other locales. In addition, there's no reliable way to enumerate the fonts available all platforms.


[Init] deck from wiki not working in visual studio build.

This may be a general javascript issue and not a Bridge specific issue. But the Init attribute is not working for me. I am a web development noob so I may be missing something obvious. My javascript file is identical to the javascript in the deck, but it is giving an error.
Steps To Reproduce

Create new Bridge class library named InitTest in VS 2017 (with Bridge nuget version 17.6.0)
Copy & Paste code from deck into App.cs
Build and open html in Chrome Version 71.0.3578.98 (latest version)

https://deck.net/f3d5ac5a0f2493f6c6b5a511688fd20f
Expected Result
On Bridge console:
Absolute Top
Before Class is defined
After Class is defined
Startup
Absolute Bottom

Actual Result
No bridge console output, chrome inspector console shows:
Absolute Top
bridge.console.js:314
Uncaught TypeError: Cannot read property 'appendChild' of null
    at ctor.init (bridge.console.js:314)
    at new ctor (bridge.console.js:215)
    at Function.get [as instance] (bridge.console.js:22)
    at Function.logBase (bridge.console.js:90)
    at Function.log (bridge.console.js:129)
    at Function.System.Console.WriteLine (bridge.console.js:47)
    at App.cs:28

bridge.console.js:314
Uncaught TypeError: Cannot read property 'appendChild' of null
    at ctor.init (bridge.console.js:314)
    at new ctor (bridge.console.js:215)
    at Function.get [as instance] (bridge.console.js:22)
    at Function.logBase (bridge.console.js:90)
    at Function.error (bridge.console.js:122)
    at bridge.console.js:83

in fact dect.net use that scripts in her body, not head

Deck.NET places the script tags in the <head> of the document.
I'm going to close this issue as I was unable to reproduce and the Deck.NET sample is working as expected, but please feel free to follow-up with new information if you can provide a reproducible sample and we will re-open the issue.


Fix Readme

Fix readme links

Codecov Report

Merging #280 (057947f) into master (0e10bd4) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #280   +/-   ##
=========================================
  Coverage     75.97%   75.97%
  Complexity      683      683
=========================================
  Files            94       94
  Lines          1998     1998
  Branches        223      223
=========================================
  Hits           1518     1518
  Misses          414      414
  Partials         66       66

Continue to review full report at Codecov.

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


Add --stats-only option

Allows you to print just the stats and nothing else. Good way to check things like total matches from a script, or manually without flooding the screen.

Thanks!


Event viewer update

Description of the new feature / enhancement
Event viewer is a super powerful tool and has a ton of bells and whistles
Imagine what a next generation event viewer could do and improve your workflows.  Be able to quickly create filters for instance
Scenario when this would be used?
Any time you're trying to see errors that have thrown
Supporting information
No response

Do you have a concept image? Sounds interesting.

It shoukd have a simple search

A concern to this I got some days ago was that this isn't really a toy like the other PowerToys. That's more like a standalone app, how do you want to integrate this?

Thanks for the ability to contribute ideas and requirements 👍

Performance.
opening eventvwr logs can take a lot of time

Ctrl+F search

"Quick filters"
Show all errors in the last x minutes from different sources (application, system, ...)

An online database like EventID.net hosted and maintained by Microsoft to make understanding and solutions easier. The database could include links to docs.microsoft.com like known issues, troubleshooting docs etc.

Option to exclude xml from copy details as text
Filter options in right click menu to include or exclude items matching the selection; like how process monitor has.
Enable right click copy of log message selection when using the lower pane; currently ctrl+c is needed to copy the selection
Add process name and process id; service name if applicable
Ability to make the center pane full screen ... to rephrase, ability to unpin the left and right panes like SQL Server Management Studio allows.
Ability to attach to processes as a first chance debugger, add any exceptions to the event viewer log
Ability to create a prebuilt filter to send to an end user to apply and have a way for them to send the results back easily

I think the main issue with EventViewer is how unapproachable it is with 'secret' buckets to know to look in or needing to be 'turned on' in order to diagnose an issue.
It'd be great to approach things with more intelligence with a scenario based focus to let folks jump into looking at the diagnostics for the problem they're trying to solve (login, application not starting, power issue, USB issue, device issue, security/access issue, etc...)


watchOS Compilation Compatibility

Currently, master cannot be compiled for watchOS because it attempts to deal with an UIApplication memory warning. The memory warning and the class UIApplication are both unavailable on watchOS.
This pull request ensures that a watchOS compilation does not try to compile this existing code.
Notes:

TARGET_OS_IPHONE is defined and true for both iOS and watchOS
TARGET_OS_IOS is a new flag in the iOS 9/watchOS 2 SDKs that is only true for iOS compilation
There is another new flag that is TARGET_OS_WATCH, but it would be odd to conditionally exclude something that is specifically for one platform

This PR could have been simplified by doing #if TARGET_OS_IOS and removing TARGET_OS_IPHONE altogether, but that would cause issues for previous SDKs. This approach works for current, past, and “future” SDK/Xcode versions.

Thank you!


Case sensitive FileExists function?

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
1.10.2
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
GOOS: windows
GOARCH: 386
What did you do?
From windows, I ask a Linux server if file exists?
There are two files inside a folder:
test.mov
I would like to verify if file test.MOV not exists (because case sensitivity is different).
Is it possible in golang?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
What did you expect to see?
What did you see instead?

The Go project doesn't use its issue tracker to answer questions. For questions about Go, see https://golang.org/wiki/Questions.

Related tickets worth reviewing: #5441, #18358.  It appears a decision hasn't been made yet on what the correct behaviour should be.


Display average of score field for all reviews

Adds scores and an average score to the review outcomes in submissions tables.

Open to suggestion on this one, when no review has been submitted. We can either remove Avg. score or add a placeholder for 0 average

Closes #3304

Thoughts on moving this here, @frjo @gmurtaza00

Thoughts on moving this here, @frjo @gmurtaza00

Does this seem alright?

That what's I was thinking, the red color was more of an indicator from my annotation tool. You can keep the font color same as the body font (black) and rest looks good to me.

Initially NA score was being display as 99 and average was calculated using this score. Rebasing resolved this issue. Now score is displayed correctly and average is also being calculated correctly.

Closing this since this view is being replaced.


HDDS-5383. Eliminate expensive string creation in debug log messages

What changes were proposed in this pull request?
Eliminate expensive string creation in debug log messages(For example: toString()).
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-5383
How was this patch tested?
No test.

Please @jojochuang  review this, thank you.

Thanks to @jojochuang ’s review, I neglected this small problem and corrected it immediately.

Can you also fix these two as well?
https://github.com/apache/ozone/blob/2254abfa4d8ee3fda24c3d7215b0ddca61632fec/hadoop-hdds/framework/src/main/java/org/apache/hadoop/hdds/scm/proxy/SCMSecurityProtocolFailoverProxyProvider.java#L213
https://github.com/apache/ozone/blob/2254abfa4d8ee3fda24c3d7215b0ddca61632fec/hadoop-hdds/framework/src/main/java/org/apache/hadoop/hdds/scm/proxy/SCMBlockLocationFailoverProxyProvider.java#L189
given the complexity of the debug message, I suggest to wrap them with LOG.isDebugEnabled() too.

Of course,I can fix these two.

Thanks again to @jojochuang ’s review, a bug about MockCRLStore.java has been posted to new jiraHDDS-5396


too fast stdout or stderr output kills beaker client

execute:
while(true) { System.out.println("FOOBAR"); }
in groovy or java

fixed for too many 'lines of output' - we must also make sure that works if you don't write \n in the stream

must fix also for 'returning' a value way too large as result evaluation.


fix: destructuring fields from formState not reactive

I was testing the form with the zod resolver. When destructuring formState properties isDirty, isValid, dirtyFields. Their value is not reactive. However, destructuring errors from formState is reactive.
Does not work:
const { formState: { isDirty, dirtyFields, isValid} = useForm(...)}
works:
const { formState } = useForm(...)

formState.isValid (reactive)

Need to play with this a bit more. Here is a minimal reproduction.
codesandbox

aha! let's think about what to do


Hide StringIndexType from TextAnalyticsRequestOptions

Not everyone needs this property, so to avoid confusion, let's hide it.
e should still document that this capability exists for people that want to use it.

We decided to make it internal for now to keep the discussion about moving the type to Azure Core