Fix search suggestions 'View Channel' Bug

PR Checklist

Please check all that apply to this PR using "x":

[x] I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
[x] I have checked that this PR does not introduce a breaking change
[ ] This PR introduces breaking changes and I have provided a detailed explanation below

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting)
[ ] Refactoring (no functional changes)
[ ] Documentation changes
[ ] Other - Please describe:

Fixes
Issue Number: 4607
What is the current behavior?
Search suggestion drop-down box has the 'View Channel' label when the query string is in fact a URI for a file.
What is the new behavior?
Label shows 'View Channel' when URI is recognized as a channel URI, and 'View File' when it is recognized as a file URI.
Other information
Suggestion for future improvement - strip '#' from the end of query string, so that URIs will be correctly recognized (and navigated to) when they are being typed out but not fully completed.

Congrats on the first PRs with this and the redux one, thanks again! We'll get a review on this soon.
Once we do, can we show you some appreciation for the contributions?

Thanks for fixing this!


Converting catalog to markdown and back to json looses catalog title

Describe the bug
Taking a json catalog (such as the 800-53r4 reference catalog) and converting to markdown, and then back to json causes the catalog title to be replaced with 'REPLACE_ME':
To Reproduce
Steps to reproduce the behavior:

mkdir trestletest
cd trestletest/
. ../../compliance-trestle/venv.trestle-develop/bin/activate
trestle init
trestle import -f ../oscal-content/nist.gov/SP800-53/rev4/json/NIST_SP-800-53_rev4_catalog.json -o NIST_SP-800-53_rev4
trestle author catalog-generate --name NIST_SP-800-53_rev4 --output md_catalogs/NIST_800-53_rev4
trestle author catalog-assemble -v --set-parameters --markdown md_catalogs/NIST_800-53_rev4 --output NIST_SP-800-53_rev4
head catalogs/NIST_SP-800-53_rev4/catalog.json

head catalogs/NIST_SP-800-53_rev4/catalog.json
{
  "catalog": {
    "uuid": "fd2eac2a-1ec9-4f66-990e-9dcecab12055",
    "metadata": {
      "title": "REPLACE_ME",
      "last-modified": "2022-03-29T15:22:35.697670+01:00",
      "version": "REPLACE_ME",
      "oscal-version": "1.0.0"
    },
    "controls": [],

Expected behavior
head ../oscal-content/nist.gov/SP800-53/rev4/json/NIST_SP-800-53_rev4_catalog.json
{
  "catalog": {
    "uuid": "b954d3b7-d2c7-453b-8eb2-459e8d3b8462",
    "metadata": {
      "title": "NIST Special Publication 800-53 Revision 4: Security and Privacy Controls for Federal Information Systems and Organizations",
      "last-modified": "2021-06-08T13:57:28.91745-04:00",
      "version": "2015-01-22",
      "oscal-version": "1.0.0",
      "props": [
        {

This could probably be solved by trestle import should write catalog metadata that does not fit into the per control MD into the .trestle directory.
Probably we should not be round tripping for upstream catalogs, but this seems like a requirement that also applies to managing custom catalogs

This is as intended and the solution is always to provide the original "parent" catalog during assembly.  The assembly process always takes the parent catalog, and its metadata, and pulls in the new content from the markdown to make the new catalog - and then it should check if the result is new relative to the destination json catalog - and not write it out if there is nothing new.
This is the only way metadata and backmatter can be captured and retained.  The destination catalog may not be present yet, when first assembled - and after that the destination catalog is only checked for the purpose of detecting changes that need to be written out.  I will clarify this in the docs.
So assembly requires 1) the parent json catalog, 2) the source markdown catalog and 3) the destination json catalog.  So just provide the optional --name of the original json catalog:
usage: trestle author catalog-assemble [-h] [--name NAME] -m MARKDOWN -o OUTPUT [-sp] [--regenerate] [--version VERSION] [-v] [-tr TRESTLE_ROOT]

Assemble markdown files of controls into a Catalog json file.

optional arguments:
  -h, --help            show this help message and exit
  --name NAME, -n NAME  Optional name of the catalog model in the trestle workspace that is being modified. If not provided the output name is used.
  -m MARKDOWN, --markdown MARKDOWN
                        Name of the input markdown file directory
  -o OUTPUT, --output OUTPUT
                        Name of the output generated json Catalog
  -sp, --set-parameters
                        set profile parameters and values based on the yaml header in control markdown
  --regenerate, -r      Flag to force generation of new uuids in the model
  --version VERSION, -vn VERSION
                        New version for the assembled model

This is working as intended but I should probably change it.  During assemble  the --name refers to a parent catalog that is used as the source of metadata.  If you don't specify it then the new json file is created straight from the markdown and there is no metadata including title.  This allows a user to create the catalog either anew, from the markdown only, or to specify the parent explicitly.
But I could allow the default behavior, if no --name is specified, to load from the existing assembled json file if it already exists.  That is probably better - but it means if you want to create the catalog just from the markdown you will need to erase the previously assembled catalog, or direct the output to a new catalog name.
So I will change that default behavior.


WIP,FIX: focalpoint

This PR fixes https://github.com/mne-tools/mne-python/issues/9007 by changing the camera's default focal point.

Weird rendering problems:
https://25630-1301584-gh.circle-artifacts.com/0/dev/auto_tutorials/source-modeling/plot_background_freesurfer_mne.html#using-freesurfer-s-surface-reconstructions

Those are really scary. I think it got reported but I didn't take care of it yet. I agree it's probably resize event or something.
My next focus will be between this and multiplotter.

BTW, the results are available on:
https://26478-1301584-gh.circle-artifacts.com/0/dev/index.html

I still see issues:
https://26478-1301584-gh.circle-artifacts.com/0/dev/auto_tutorials/source-modeling/plot_eeg_mri_coords.html

Circle probably uses PyVista master since it breaks already. I'll open a PR to get ready for those changes.

@GuillaumeFavelier any chance to return to this? It's going to be a blocker for 0.23

TBH I was counting on https://github.com/mne-tools/mne-python/pull/8997 to fix it indirectly but considering the slow progress, it might not be enough for the next release. I'll give it max priority then :+1:

I think #8997 is a good one to merge right after release rather than right before it. It's a big change and we want some months of testing and use ourselves to make sure it's stable

I think it's worth a [circle full] after https://github.com/mne-tools/mne-python/pull/9318 is merged.

tutorials/forward/10_background_freesurfer.py: https://27738-1301584-gh.circle-artifacts.com/0/dev/auto_tutorials/forward/10_background_freesurfer.html?highlight=freesurfer

main
PR

tutorials/forward/50_background_freesurfer_mne.py: https://27738-1301584-gh.circle-artifacts.com/0/dev/auto_tutorials/forward/50_background_freesurfer_mne.html?highlight=freesurfer

main
PR

For reference:
examples/connectivity/sensor_connectivity.py: https://27738-1301584-gh.circle-artifacts.com/0/dev/auto_examples/connectivity/sensor_connectivity.html?highlight=sensor connectivity

And locally for tutorials/inverse/60_visualize_stc.py:

LGTM -- ready to go, then?

Ready on my end

Thanks @GuillaumeFavelier !


Currently Not working

Seems to not be working at the moment on cloudflare sites, doesn't seem to try and wait the 5 secs just does it instantly and shows the usual cloudflare jargon.
Sites I have noted not working are
https://www.animepace.si/
http://kimcartoon.me/

These websites are working for me. Can you please make sure you're using the latest version of cloudflare-scrape? To check, see if cfscrape.__version__ is 1.9.4.

I've done pip install cfscrape as have been using it a long time and it's
saying all dependancies satisfied.
On 12 Feb 2018 19:58, "Anorov"<EMAIL_ADDRESS>wrote:

These websites are working for me. Can you please make sure you're using
the latest version of cloudflare-scrape? To check, see if
cfscrape.version is 1.9.4.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Anorov/cloudflare-scrape/issues/140#issuecomment-365043281,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AY0MYP7T0BKurAZ75XwKtnfC3ht-1qR-ks5tUJfPgaJpZM4SB45c
.

@nemesis668 When you execute “pip show cfscrape” what’s the output for the version field?

On Feb 12, 2018, at 17:48, nemesis668<EMAIL_ADDRESS>wrote:
I've done pip install cfscrape as have been using it a long time and it's
saying all dependancies satisfied.
On 12 Feb 2018 19:58, "Anorov"<EMAIL_ADDRESS>wrote:

These websites are working for me. Can you please make sure you're using
the latest version of cloudflare-scrape? To check, see if
cfscrape.version is 1.9.4.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Anorov/cloudflare-scrape/issues/140#issuecomment-365043281,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AY0MYP7T0BKurAZ75XwKtnfC3ht-1qR-ks5tUJfPgaJpZM4SB45c
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Says 1.9.0

I un-installed and installed again and now it seems to be running the latest version and all working :)


Made PR template checklist check-able by ALL PRs

Which issue is fixed by this PR? If not related to an existing issue, what does this PR do?
The new PR template re-words the bottom checklist ('this pr includes documentation', 'updates Changelog.md' etc.) such that any PR that is ready for merging will have ALL boxes checked.
It also changes the "Which TC components are affected by this PR?" section to an unordered list, the new recommendation being that unaffected components be removed from said list.
All together, this results in a PR that's ready for review having a nice, happy "6/6" in the PR list.
Which TC components are affected by this PR?
This PR Template
What is the best way to verify this PR? Please include manual steps or automated tests.
Just look at the template - no tests because no functionality.
Check all that apply
See, none of these are true, so this PR will show up as "0/6", which implies it's missing required pieces.

[ ] This PR includes tests
[ ] This PR includes documentation updates
[ ] This PR includes an update to CHANGELOG.md
[ ] This PR includes all required license headers
[ ] This PR includes a database migration (ensure that migration sequence is correct)
[ ] This PR fixes a serious security flaw. Read more: www.apache.org/security

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3309/
Test PASSed.

"If this is a fix for an unreported security vulnerability, do not submit this PR and please report the issue to<EMAIL_ADDRESS>See: http://www.apache.org/security/"

I think this could/should be the first item in the PR template.

While we're kinda overhauling the PR template, I'd like to see a new list item along the lines of "if this is a bugfix, what version(s) are affected (e.g. the current TC release, master -- include commit hash)? Will this need backported to a current release candidate?"
As committers we should try to get better at evaluating whether or not a bugfix that comes in also affects the most recent TC release and/or a current release candidate, so that we can proactively backport bugfixes instead of being surprised when we find bugs in a release that have already been fixed in master but weren't backported. However, it would be nice if the PR submitter were encouraged to check the current release candidate and/or the current release for the bug as well, since they'd likely be asked to open a backport PR as well in those cases.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3334/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3335/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3355/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3366/
Test PASSed.


Sliding Window Implementation with Explanation

Implemented and Explained about Sliding window.
Checked it in my text editor and code is working perfectly fine.

Hey @Suryash-Jha  , make sure your Pull Request is descriptive and complete the checklist .
I would recommend you to go through this tutorial video of the project here ,thanks.

No Response From Contributor ...

Short Description or CheckLists

Make sure your Pull Request is descriptive and complete the checklist .
I would recommend you to go through this tutorial video of the project here ,thanks.
///------------------Descriptoin -----------------------///
For contribution and more guidelines i would recommend you to go through this
tutorial video of the project here, thanks.
///-----------------CheckList-------------------------///
Make sure your Pull Request is descriptive and complete the checklist .
I would recommend you to go through this tutorial video of the project here ,thanks.
///------------------Description -----------------------///
Let me show you how to check the check list , there should be no space inside brackets like [x]
[x]

[x] Checklist
[ ] Or you can just check them from outside without doing any of these
[x] ✨ I have added tests to cover my changes.
[x] 🚩 All new and existing tests passed.
[ ] 🌟 ed the repo

Starr the repo if you haven't !
Have you watched this video ?

///----------------------PR README --------------------///
You need to follow particular guidelines for your README , please follow
these guidelines click here
also you can see how your README should look like see here
for more please go through these here

No response from the contributor ??

@Lakhankumawat  I think we should close this pr !

Sorry sir... actually i was busy in some hackathons...so i forgot about
gssoc.
I will try to make my PR as directed as soon as possible.
Please, don't close this PR.
Thanks,
Suryash
On Wed, Mar 16, 2022, 6:24 PM Siddhi Bhanushali @.***>
wrote:

@Lakhankumawat https://github.com/Lakhankumawat I think we should close
this pr !
—
Reply to this email directly, view it on GitHub
https://github.com/Lakhankumawat/LearnCPP/pull/176#issuecomment-1069095870,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUID5NS5MCHSMN6XQTY7U6DVAHKYRANCNFSM5PU4RHNA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>


Add 93 Dub Watchface

Adds a clock based off of 91 Dub v2.0 by Orviwan (https://github.com/orviwan/91-Dub-v2.0)

Looks great - thanks!


0.24.0 test keeper upgrade [wip]

Adding test to check clickhouse-keeper upgrade.
This test fails due to the fact that local tables switch to a read-only mode.
Adding check to test_048, that pvc is supported for ClickHouseKeeperInstallation.

We're seeing this issue in the field. Is there a workaround for tables going R/O when Keeper is upgraded?


feat: Add event logo in AboutFragment

Fixes #2303
Changes: Added event logo in AboutFragment. In case the logo can't be fetched, the placeholder is the same as before.
Screenshots for the change:

@iamareebjamal Please review.

Please edit the issue to be about the logo. BAckground image is different


import {BLEmanger} from 'react-native-ble-plx'  is undefine

Prerequisites

[X] I checked the documentation and FAQ without finding a solution
[X] I checked to make sure that this issue has not already been filed

Expected Behavior
The BleManager should not be undefine when importing
import {BleManager, BleError} from 'react-native-ble-plx';
Current Behavior
The BleManager is undefine when importing
import {BleManager, BleError} from 'react-native-ble-plx';
Library version
3.1.2
Device
Pixel 7
Environment info
info Fetching system and libraries information...
(node:77921) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
(node:77921) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
System:
  OS: macOS 13.1
  CPU: (10) arm64 Apple M1 Pro
  Memory: 2.14 GB / 32.00 GB
  Shell:
    version: 3.2.57
    path: /bin/bash
Binaries:
  Node:
    version: 21.5.0
    path: /opt/homebrew/bin/node
  Yarn:
    version: 1.22.17
    path: /usr/local/bin/yarn
  npm:
    version: 10.2.4
    path: /opt/homebrew/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods: Not Found
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 22.2
      - iOS 16.2
      - macOS 13.1
      - tvOS 16.1
      - watchOS 9.1
  Android SDK:
    API Levels:
      - "28"
      - "30"
      - "31"
      - "33"
      - "34"
    Build Tools:
      - 30.0.2
      - 30.0.3
      - 31.0.0
      - 33.0.0
      - 33.0.1
      - 34.0.0
    System Images:
      - android-29 | Google APIs ARM 64 v8a
      - android-33 | Google APIs ARM 64 v8a
      - android-33 | Google APIs Intel x86_64 Atom
      - android-33 | Google Play ARM 64 v8a
    Android NDK: Not Found
IDEs:
  Android Studio: 2022.3 AI-223.8836.35.2231.10406996
  Xcode:
    version: 14.2/14C18
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.9
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.73.3
    wanted: 0.73.3
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: false

Steps to reproduce
import {BleManager, BleError} from 'react-native-ble-plx';

export let ble = new BleManager();

The BleManager is undefined here
Formatted code sample or link to a repository
Not Yet

Relevant log output
Not Yet

Additional information
React Native: 0.73.3
JDK: 17
Nodejs: 21.5.0
Android SDK: 34
AndroidManifest.xml
<manifest xmlns:android="http://schemas.android.com/apk/res/android">

    <uses-permission android:name="android.permission.INTERNET" />

       <!-- Android >= 12 -->
   <uses-permission android:name="android.permission.BLUETOOTH_SCAN" android:usesPermissionFlags="neverForLocation"/>
   <uses-permission android:name="android.permission.BLUETOOTH_CONNECT" />
   <!-- Android < 12 -->
   <uses-permission android:name="android.permission.BLUETOOTH" android:maxSdkVersion="30" />
   <uses-permission android:name="android.permission.BLUETOOTH_ADMIN" android:maxSdkVersion="30" />

   <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" android:maxSdkVersion="30" />

   <!-- Add this line if your application always requires BLE. More info can be found on:
       https://developer.android.com/guide/topics/connectivity/bluetooth-le.html#permissions
     -->
   <uses-feature android:name="android.hardware.bluetooth" android:required="true"/>
   <uses-feature android:name="android.hardware.bluetooth_le" android:required="true"/>

    <application
      android:name=".MainApplication"
      android:label="@string/app_name"
      android:icon="@mipmap/ic_launcher"
      android:roundIcon="@mipmap/ic_launcher_round"
      android:allowBackup="false"
      android:theme="@style/AppTheme">
      <activity
        android:name=".MainActivity"
        android:label="@string/app_name"
        android:configChanges="keyboard|keyboardHidden|orientation|screenLayout|screenSize|smallestScreenSize|uiMode"
        android:launchMode="singleTask"
        android:windowSoftInputMode="adjustResize"
        android:exported="true">
        <intent-filter>
            <action android:name="android.intent.action.MAIN" />
            <category android:name="android.intent.category.LAUNCHER" />
        </intent-filter>
      </activity>
    </application>
</manifest>

build.gradle
buildscript {
    ext {
        buildToolsVersion = "34.0.0"
        minSdkVersion = 24
        compileSdkVersion = 34
        targetSdkVersion = 34
        ndkVersion = "25.1.8937393"
        kotlinVersion = "1.8.0"
    }
    repositories {
        google()
        mavenCentral()
    }
    dependencies {
        classpath("com.android.tools.build:gradle")
        classpath("com.facebook.react:react-native-gradle-plugin")
        classpath("org.jetbrains.kotlin:kotlin-gradle-plugin")
    }
}

allprojects {
    repositories {
      maven { url 'https://www.jitpack.io' }
    }
}

apply plugin: "com.facebook.react.rootproject"

Hi @blood-romantic,
Thanks for reaching out. We'll check the issue and get back to you with a solution proposal soon.

@blood-romantic
Can you double-check what happens when you add some options?
const options: BleManagerOptions = {
  restoreStateIdentifier: "BleInTheBackground",
  restoreStateFunction: (restoredState) => {
    if (restoredState == null) {
      console.log("BleManager was constructed for the first time.");
    } else {
      console.log(
        "BleManager BleManager was restored.",
        restoredState.connectedPeripherals
      );
    }
  }
};

export let ble = new BleManager(options);

npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.73.3
    wanted: 0.73.3
  react-native-macos: Not Found

Seems you need to install the module first:
npm i react-native-ble-plex

@cixio the module has been install, i'm not sure why show Not Found

npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.73.3
    wanted: 0.73.3
  react-native-macos: Not Found

Seems you need to install the module first: npm i react-native-ble-plx

can you verify that the folder modules/react-native-ble-plx exists?

@blood-romantic
Could you create a new project and install only react-native-ble-plx and check if problems still exist or even better show this repository? Before I start investigating this problem, I would like to exclude any potential environmental issues.

Close this issue, after reinstall the dependency, it is ok


[ci] release

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
<EMAIL_ADDRESS>Patch Changes

#1420 275f87f Thanks @abdelhalimjean! - Fix rare font-family issue if users have a font installed with a name of ""

size-limit report 📦

Path
Size

/index.html
5.21 KB (-0.04% 🔽)

/_astro/*.js
21.44 KB (-0.04% 🔽)

/_astro/*.css
13.14 KB (0%)


[5.1] No need to export CONTRIBUTING.md

No need to export CONTRIBUTING.md
Targeting 5.1 on purpose.

To be closed if #12364 is merged.

Closing in favor of https://github.com/laravel/framework/pull/12364


Use "division-by-multiplication" scheme to fasten division

@mcroomp, unfortunately this is not working, not enough precision for all u16 range https://github.com/microsoft/lepton_jpeg_rust/blob/2f8c32420e3c67462afa459ece898b001794ce2e/src/structs/quantization_tables.rs#L88
Even 2^32 fails - first at 17215. A classical scheme from Warren should work, but it has variable shifts.

I wanted to make this, but you are faster :)


istio depends on envoy/admin/v2alpha unstable API

istioctl, pilot, and test framework use an experimental xDS API which may cause issues with stability and future compatibility.
/cc @mandarjog

@yangminzhu @howardjohn
Can we get rid of this dependency? We should not use any alpha-level xDS APIs since they put us at risk of sudden incompatible changes. An opaque blob containing alpha-level APIs should be the right way to enable experimentation, but please don't use the schematized versions, even if it is available in go-control-plane.

An opaque blob containing alpha-level APIs should be the right way to enable experimentation

I am not sure what you mean by this?

What I meant is to pass-through YAML straight to Envoy without trying to parse it in Istio.

Where are we sending yaml to envoy using alpha APIs? As far as I can tell this is just the admin api that we read for debugging, readiness check, etc?

@howardjohn We should not query alpha APIs in this case. If we depend on the schema of admin APIs for readiness check, then that locks us with particular builds of Envoy since these APIs are churning, and we cannot expect that a month from now or a month ago build of Envoy works with the sidecar agent.

Is there any alternative?

@kyessenov I think using alpha API doesn't make the things worse in some case. One recent example is here: https://github.com/istio/istio/blob/1a837b3fa74058ff1397bb0207cea20ae269c188/pilot/cmd/pilot-agent/status/util/listeners.go#L40 Previously the code is parsing the /listeners output manually using  regex. And it breaks in the test when updating to a newer Envoy because the text output changed.
I changed the code to use the admin API when updating the proxy sha, and I think this at least gives us 2 benefits: 1) it will fail in the build instead of test when something changed in Envoy; 2) it's much easier and also reliable to parse the API compared to using regex parsing the text output.

@yangminzhu I agree that using API is better than regex-parsing the JSONs. I don't understand how this will be caught during build without a runtime test that validates the envoy output?

Oh, I mean it will be caught when you updating the go-control-plane API. Also I think the error will be much obvious even if only updating the proxy sha. Previously I have to look deep into the test log to figure out it failed because the text output is changed.

I think there are at least 3 main use cases of alpha API:

istioctl uses the admin API to do some analysis on the Envoy config
pilot-agent uses the admin API to get the active listeners of the Envoy for health check purpose
pilot authn plugin uses v2alpha Envoy JWT filter API.
(I'm not sure how is this used in test code, feel free to add if there are other use cases)

For the authn v2alpha JWT filter case, it shouldn't be a big problem because the API is already quite stable and we just need to promote it to v2 in Envoy, like I did for the RBAC v2alpha -> v2 promotion in Envoy.
It's tricky for the first 2 use cases because I'm not sure what's would be the proper replacement without using the alpha API, @kyessenov @howardjohn thoughts?

I'm most concerned about #2. We should use some other stable mechanism to get that number (stats or some other self-monitoring way).

We also look at /server_info (https://github.com/istio/istio/pull/14928).
If there is a more stable way to get this information sgtm, but i am not sure if it is exposed anywhere else

I think stats have been more stable than the rest, but don’t know the api stability level.
Server_info, config-dump are also v2alpha.
That said, this is a good time to define a stable api inside envoy and then use it.
We can define it with the intention of graduating it to stable.

Yes, we need to push to graduate any APIs that we really need to stable in envoy. We need to be able to swap out envoy binaries on a regular basis once we start building native extensions, and we don't want to be locked into particular SHAs because some alpha-level API changed.


EOS-27315: hctl bootstrap is failing in latest hare main

hctl bootstrap hangs in main,
[root@ssc-vm-g2-rhev4-1947 ~]# hctl bootstrap --mkfs --xprt libfab ~/1n.yaml
2022-01-07 10:44:17: Generating cluster configuration... OK
2022-01-07 10:44:20: Starting Consul server on this node......... OK
2022-01-07 10:44:29: Importing configuration into the KV store... OK
2022-01-07 10:44:31: Starting Consul on other nodes...Consul ready on all nodes
2022-01-07 10:44:31: Updating Consul configuraton from the KV store... OK
2022-01-07 10:44:33: Waiting for the RC Leader to get elected.... OK
2022-01-07 10:44:36: Starting Motr (phase1, mkfs)...

Because config_path kv is missing is missing in Consul, config_path is added through hare mini provisioner, which is not invoked as part of hctl bootstrap.
Jan 07 10:49:18 ssc-vm-g2-rhev4-1947.colo.seagate.com hare-hax[6027]: 2022-01-07 10:49:18,919 [DEBUG] {MainThread} Got HAConsistencyException: config path not present in consul while invokingJan 07 10:49:23 ssc-vm-g2-rhev4-1947.colo.seagate.com hare-hax[6027]: 2022-01-07 10:49:23,924 [DEBUG] {MainThread} KVGET key=config_path, kwargs={}

This is a regression from commit 28869a4f.
Solution:
Move MessageBus.init to ha module, thus the relevant code will be
invoked only if deployed with cortx-ha component.
Signed-off-by: Mandar Sawant<EMAIL_ADDRESS>

[root@ssc-vm-1623:root] ./install.sh /home/520478/rpmbuild/RPMS/x86_64/cortx-hare-2.0.0-1_gite6f6abc.el7.x86_64.rpm

installing hare
Preparing...                          ################################# [100%]
Updating / installing...
   1:cortx-hare-2.0.0-1_gite6f6abc.el7################################# [100%]
[root@ssc-vm-1623:root] hctl bootstrap --mkfs ./singlenode.yaml
2022-01-07 12:36:10: Generating cluster configuration... OK
2022-01-07 12:36:11: Starting Consul server on this node........ OK
2022-01-07 12:36:17: Importing configuration into the KV store... OK
2022-01-07 12:36:17: Starting Consul on other nodes...Consul ready on all nodes
2022-01-07 12:36:17: Updating Consul configuraton from the KV store... OK
2022-01-07 12:36:18: Waiting for the RC Leader to get elected........ OK
2022-01-07 12:36:23: Starting Motr (phase1, mkfs)... OK
2022-01-07 12:36:30: Starting Motr (phase1, m0d)... OK
2022-01-07 12:36:32: Starting Motr (phase2, mkfs)... OK
2022-01-07 12:36:42: Starting Motr (phase2, m0d)... OK
2022-01-07 12:36:47: Checking health of services... OK
[root@ssc-vm-1623:root] hctl status
Data pool:
    # fid name
    0x6f00000000000001:0x3e 'sns-pool'
Profile:
    # fid name: pool(s)
    0x7000000000000001:0x54 'default': 'sns-pool' 'dix-pool' None
Services:
    ssc-vm-1623.colo.seagate.com  (RC)
    [started]  hax        0x7200000000000001:0x7   inet:tcp:<IP_ADDRESS>@2001
    [started]  confd      0x7200000000000001:0xa   inet:tcp:<IP_ADDRESS>@3001
    [started]  ioservice  0x7200000000000001:0xd   inet:tcp:<IP_ADDRESS>@3002
    [started]  ioservice  0x7200000000000001:0x1c  inet:tcp:<IP_ADDRESS>@3003
    [unknown]  m0_client  0x7200000000000001:0x2b  inet:tcp:<IP_ADDRESS>@5001
    [unknown]  m0_client  0x7200000000000001:0x2e  inet:tcp:<IP_ADDRESS>@5002
[root@ssc-vm-1623:root] hctl shutdown
Stopping m0d@0x7200000000000001:0xd (ios) at ssc-vm-1623.colo.seagate.com...
Stopping m0d@0x7200000000000001:0x1c (ios) at ssc-vm-1623.colo.seagate.com...
Stopped m0d@0x7200000000000001:0x1c (ios) at ssc-vm-1623.colo.seagate.com
Stopped m0d@0x7200000000000001:0xd (ios) at ssc-vm-1623.colo.seagate.com
Stopping m0d@0x7200000000000001:0xa (confd) at ssc-vm-1623.colo.seagate.com...
Stopped m0d@0x7200000000000001:0xa (confd) at ssc-vm-1623.colo.seagate.com
Stopping hare-hax at ssc-vm-1623.colo.seagate.com...
Stopped hare-hax at ssc-vm-1623.colo.seagate.com
Making sure that RC leader can be re-elected next time
Stopping hare-consul-agent at ssc-vm-1623.colo.seagate.com...
Stopped hare-consul-agent at ssc-vm-1623.colo.seagate.com
Shutting down RC Leader at ssc-vm-1623.colo.seagate.com...
[root@ssc-vm-1623:root]

Re-triggered single node deployment at http://eos-jenkins.colo.seagate.com/job/Cortx-PR-Build/job/Cortx-Deployment/job/Kubernetes/job/hare/77/, completed successfully.


Adds Pbde Molstar

Continuation of #19
A Panel Pane to wrap the PDBe implementation of the Mol* ('MolStar') viewer.
Check out

PDBe Mol*
Mol*
Mol* GitHub

Cite Mol*:
David Sehnal, Sebastian Bittrich, Mandar Deshpande, Radka Svobodová, Karel Berka,
Václav Bazgier, Sameer Velankar, Stephen K Burley, Jaroslav Koča, Alexander S Rose:
Mol* Viewer: modern web app for 3D visualization and analysis of large biomolecular structures,
Nucleic Acids Research, 2021; https://doi.org/10.1093/nar/gkab314.
Todo:

[] Test that dynamic updates work
[] Decide if light theme should be could default as is custom in Panel.
[] Decide if default theme should be dark or default/ light.
[] Add/ use utility functions
[] Add events.
[] Fix that the component get slower and slower on each rerender.
[] Reference Notebook
[] Add automated tests
[] Test, Test, Test
[] pypi package
[] conda package
[] Communication

Nice to have

Some Gallery notebook showing an example application.
Some way to update the css file across all PdbeMolstar instances when the theme changes.
Set default theme based on theme=default or them=dark url query args.

https://user-images.githubusercontent.com/42288570/147883741-25b67e5b-afa6-4fbd-9e65-4fb9c34cb0dc.mp4
I will leave it here @Jhsmit . Could you give it a spin and make a PR into this branch? Feel free to tell me if I should work on something to help.

FYI. I've added you as a member of this repo and to the gitter channel @Jhsmit

Thanks Marc, I'll have a look.
"make a PR into this branch?" , What do you mean by this? add commits to this PR or should I start from here and commit to my own fork and PR from there?

What I mean is that It would be nice for me to see and accept changes to this branch.
I would expect that has to be done via a separate pull request from your fork/ branch into this branch. But if there are other ways and you prefer them just use them.
If you know how to collaborate on a feature branch like this please let me know. Not so used to it :-)

Ok yep I think i managed it in #21.
Usually my workflow I just me in a lonely repo so I had to do some git-fu to figure it out.

Another PR has been approved

Not merged :-)

I will approve this one now @Jhsmit . I believe its in a good enough state to release, and then we can improve later.
I plan to publish package and market it on twitter later today. Hope its ok?

Thanks Marc!
Sounds good to me. Lets get it out and then we might solutions to the resizing / events later.
I'll put it in PyHDX and also tweet about it later

It will not be today. But ASAP. Something got in the way :-)

I've release v0.0.12 to pypi
I've requested v0.0.12 release on conda-forge https://github.com/conda-forge/panel-chemistry-feedstock/pull/1

I've tested. But for some reason the Panel jupyter-preview and Panel apps are not working on binder.

Preview: https://mybinder.org/v2/gh/marcskovmadsen/panel-chemistry/HEAD?urlpath=lab/tree/examples/reference/PDBe_MolStar.ipynb
App: https://mybinder.org/v2/gh/marcskovmadsen/panel-chemistry/HEAD?urlpath=panel/PDBe_MolStar

Both work fine for me:

I did have the issue where the resizing wasn't triggered correctly and only half of the viewer was showing. But re-executing the cell solved that.
On conda-forge, you should merge the PR yourself if all checks pass since you're the maintainer.

Hmm. I don't have a merge button.

I get this for the preview binding link you posted above:

All seems to work fine.

Regarding conda-forge, its strange you do not have write access
Are you in the conda-forge/panel-chemistry team?
You should be able to find that on your github.com homepage in the bar on the left
This is what it looks like for me:

Perhaps you could try this procedure here:
https://conda-forge.org/docs/maintainer/updating_pkgs.html#updating-the-maintainer-list


Submit challenge for 2021-08-31 meetup

Language
Javascript
Challenge
Zero Point
Closes #147

I think it would make sense to test an example that includes two or more "non-nested" zero sequences (like the example in the challenge description intro paragraph). The tests are all "one and done," and the function should be able to take care of more than one sequence.
It also might be good to include a zero in one of them (which I assume should be deleted).

@mrumiker , good catch. I added a test case for both suggestions as they seem reasonable. Thank you for the review!


Sidebar image size

Is it possible to alter the size of an image included in the sidebar? The sidebar css class forces image width of 100% but I have a logo I'd like to include that is smaller than that. I've put the following into sidebar.html:

Have you tried adding inline CSS to the img element to set the width and heights you want. That should override any of the sidebar CSS.

Perfect, thanks. :-)


Update piston_window dependency

This crate uses piston_window = "0.120.0" while piston_window = "0.128.0" is on creates.io

yeah I am facing the same issue


allegro5: <IP_ADDRESS> -> <IP_ADDRESS>

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/allegro/versions.
meta.description for allegro5 is: "A game programming library"
meta.homepage for allegro5 is: "https://liballeg.org/"
meta.changelog for allegro5 is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found <IP_ADDRESS> with grep in /nix/store/6c9q94ylz21gvn2vxybx0r06jgmk6zdj-allegro-<IP_ADDRESS>
found <IP_ADDRESS> in filename of file in /nix/store/6c9q94ylz21gvn2vxybx0r06jgmk6zdj-allegro-<IP_ADDRESS>

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
0 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
allegro5
dwarf-fortress-packages.dwarf-fortress-full
liberation-circuit

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/6c9q94ylz21gvn2vxybx0r06jgmk6zdj-allegro-<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A allegro5 https://github.com/r-ryantm/nixpkgs/archive/f9771ac5baec358aa6fa5c8fae7301c2970bd622.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/6c9q94ylz21gvn2vxybx0r06jgmk6zdj-allegro-<IP_ADDRESS>
ls -la /nix/store/6c9q94ylz21gvn2vxybx0r06jgmk6zdj-allegro-<IP_ADDRESS>/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

allegro5
dwarf-fortress-packages.dwarf-fortress-full
liberation-circuit

Maintainer pings
cc @7c6f434c for testing.

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

3 packages built:

allegro5
dwarf-fortress-packages.dwarf-fortress-full
liberation-circuit

Since this is a library, I needed to run something that depends on it. dwarf-fortress seems to be working fine.

@thiagokokada Hey, did you test on NixOS or non-NixOS? I had some problems running allegro on Ubuntu

For me, this example works with apt-installed libraries on Kubuntu 22.04, but it doesn't work with nix-installed libraries (display is NULL):
#include <allegro5/allegro5.h>
#include <allegro5/allegro_font.h>
#include <unistd.h>

int main (int argc, char **argv) {

  al_init();

  void *display = al_create_display(800, 600);

  sleep(2);

  al_destroy_display(display);

  return 0;
}


How to economize on RAM when starting a crawl with a large list of urls?

A very long list of starting URLs consumes a significant amount of RAM throughout the crawler's runtime. I tried converting the get_urls() function into a generator, but the crawler.run() method did not accept it. What is the recommended approach?
import asyncio
from crawlee.playwright_crawler import PlaywrightCrawler, PlaywrightCrawlingContext

def get_urls():
    urls = []
    ids = range(1, 100000)
    for id in ids:
        url = f"https://example.com/product/{pinside_id}"
        urls.append(url)
    return urls

async def crawl_example() -> None:
        # PlaywrightCrawler crawls the web using a headless browser controlled by the Playwright library.
        crawler = PlaywrightCrawler()

        # Define a request handler to process each crawled page and attach it to the crawler using a decorator.
        @crawler.router.default_handler
        async def request_handler(context: PlaywrightCrawlingContext) -> None:
            context.log.info(f'Processing {context.request.url} ...')
            # Extract relevant data from the page context.
            data = {
                'url': context.request.url,
                'title': await context.page.title(),
            }
            # Store the extracted data.
            await context.push_data(data)

            # Extract links from the current page and add them to the crawling queue.
            # await context.enqueue_links()

        # Add initial URLs to the queue and start the crawl.
        await crawler.run(get_urls())

asyncio.run(crawl_example())

corrected a variable name

In the example code, the variable pinside_id should just be id.

With #777 merged, it should be possible to make a RequestList that loads URLs from a generator (regular or async). Then you can pass that to your crawler like this:
crawler = PlaywrightCrawler(request_manager=await RequestList(your_generator()).to_tandem())

Feel free to test this with a beta release such as https://pypi.org/project/crawlee/0.5.0b25/


[Interactive] Add start_time field in ServiceStatus

Is your feature request related to a problem? Please describe.
It's useful to display the service uptime for user. So we could add a start_time field in GET /v1/service/status interface:
ServiceStatus:
     x-body-name: service_status
      type: object
      properties:
        status:
          type: string
        graph:
          $ref: '#/components/schemas/GetGraphResponse'
        bolt_port:
          type: integer
          format: int32
        hqps_port:
          type: integer
          format: int32
        gremlin_port:
          type: integer
          format: int32
        start_time:
          type: integer

Fixed via https://github.com/alibaba/GraphScope/pull/3838


Branch c_lib: Euler not working for n >= 3

c_lib and numpy Euler works the same for n = 2, but not for n = 3

Fixed. See bbc47be173f2a48fb4e9d122e0617afdc9bdaf32


lumen 10 support

Hi @stevebauman ,
have you plan to support lumen 10 ?
Thanks in advance for your answer.

Hi @evifere,
I've just released Lumen 10 support. Thanks for the reminder!

thanks


Performance improvements, pass 1

My "All The Mods 2" server was being very slow. A user made a 5x ore processing flow and used Thermal Dynamics pipes for all the energy/fluid/item transfers, since the Mekanism pipes are currently really broken (#4507 and another issue where you have to place each pipe piece twice). The server's TPS was having severe issues, I profiled to see what's going on. Methods like "receiveEnergy" and "fill" were taking the vast majority of the time. So I dug in.
The result of today's investigation is these commits. I drastically increased the performance of these methods. For example receiveEnergy was not accounting for if we were already full of energy. It was always checking if the side was valid and marking the chunk dirty. You can look at each commit for its improvements.
The observer thing is something I haven't followed through with yet. My general thinking is like this: getConfig seems to be a bit slow (according to the profiler), and for these purposes it stores which sides are set to input, output, etc. That's something that the user generally changes shortly after placing the machine, and then doesn't touch again. So most of the effort of going and getting the config is wasted; we should be able to pretty aggressively cache which side is which. I figured if we add an observable and then trigger it when a side data is changed, then we can cache/memoize some methods and just update the cached values when the observer triggers an event.

Great, appreciate the changes. Once we get the transmitter issues sorted out Mekanism is gonna be more stable than ever.


Request for dream laboratory

Add domain dreamlab.edu.vn

@vannguyen90 This domain does not belong to a university, nor to a college. I have to close the request without merging. Please ensure that you are familiar with this repository rules located at the bottom of this page before submitting a new request.


feat: bring back the custom DataSink overload

What this PR changes/adds
This PR brings back the overloaded method in the DataPlaneManager that takes a DataSink parameter.
If specified, the DataPlaneManager(Impl) will immediately delegate to the PipelineService.
This effectively restores the behaviour before #3486
Why it does that
For streaming, e.g. HTTP, we need to be able to supply just any random data sink
Further notes
List other areas of code that have changed but are not necessarily linked to the main feature. This could be method
signature changes, package declarations, bugs that were encountered and were fixed inline, etc.
Linked Issue(s)
Closes # <-- insert Issue number if one exists
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

Codecov Report
Attention: 8 lines in your changes are missing coverage. Please review.

Comparison is base (fa978df) 71.78% compared to head (5c5b922) 71.75%.

Files
Patch %
Lines

...aplane/framework/pipeline/PipelineServiceImpl.java
12.50%
7 Missing :warning:

...aplane/framework/manager/DataPlaneManagerImpl.java
90.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3627      +/-   ##
==========================================
- Coverage   71.78%   71.75%   -0.03%
==========================================
  Files         909      909
  Lines       18134    18144      +10
  Branches     1033     1033
==========================================
+ Hits        13018    13020       +2
- Misses       4672     4680       +8
  Partials      444      444

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


.watch() doesn't list all services

Watch method only lists some services while using Bonjour Browser by Tildesoft (you had mention this tool somewhere) I can see them all.
I published 4 services in my NodeJS app using both https://github.com/agnat/node_mdns and https://github.com/watson/bonjour and also joking with their params, but no luck at all.
This is what Bonjour Browser sees:

My services are BONJOUR test 1/2 and MDNS test 1/2.
zeroconf is used as this:
let zeroconf = cordova.plugins.zeroconf;
zeroconf.watch('_smb._tcp.', 'local.', function(result) {
	let action = result.action;
	let service = result.service;
	if (action == 'added') {
		console.log('1 service added', service);
	} else if (action == 'resolved') {
		console.log('1 service resolved', service);
	} else {
		console.log('1 service removed', service);
	}
}, function(err){
	console.log("ERROR", err);
});

and, running it in a real iPod Touch 5th gen, the Safari console prints out this:

As you can see zeroconf doesn't list my services.
I already tried to change ports, hostnames and service names in the Node JS app.
I already tried some combination of '_smb._tcp.', 'local.'.
No luck at all.
Bonus note: as you can see in Bonjour Browser, there're also 2 services registered as _teamviewer._tcp., but I can't see them using cordova.plugins.zeroconf.watch('_teamviewer._tcp.', 'local.', console.log); directly on console.
I'm feeling lost :-(
Can you help me please?
Thanks a lot.

ok.. that's annoying
could you install a zeroconf browser app on your ipod and check that you see all the services in it?
(Flame Services Browser for instance)

UPDATE: running the same code on the iOS simulator, I got these from the console:
2017-12-01 18:29:45.242087+0100 m-frame[16702:587662] THREAD WARNING: ['ZeroConf'] took '95.268066' ms. Plugin should use a background thread. 2017-12-01 18:29:45.397604+0100 m-frame[16702:587662] service added EPSON WP-4535 Series 2017-12-01 18:29:45.399945+0100 m-frame[16702:587662] service added Mac mini 2017-12-01 18:29:45.401882+0100 m-frame[16702:587662] service added BONJOUR test 1 2017-12-01 18:29:45.402090+0100 m-frame[16702:587662] service added MDNS test 2 2017-12-01 18:29:45.444354+0100 m-frame[16702:587662] service resolved EPSON WP-4535 Series 2017-12-01 18:29:45.445042+0100 m-frame[16702:587662] service resolved Mac mini 2017-12-01 18:29:45.446439+0100 m-frame[16702:587662] service resolved MDNS test 2 2017-12-01 18:29:51.066513+0100 m-frame[16702:587662] service added GranGuardia 2017-12-01 18:29:51.104781+0100 m-frame[16702:587662] service resolved GranGuardia
So it does find them! All! But why on real device it doesn't ?
Need to further investigate...

Ok, installed "Discovery - DNS-SD Browser" app by the previous mentioned Tildesoft.
My services are not found!
Also TeamViewer ones.
It lists only the same you see also with your plugin.
Any idea on why it happen and how to resolve?

Closing old issue. Feel free to reopen.


drivers: gpio: Fix typo on esp32

esp32 has 40 gpio ports but some ranges are wrote 32_63 instead of 32_39.
Signed-off-by: Vitor Massaru Iha<EMAIL_ADDRESS>

Patch itself LGTM, but please re-push without the merge commit.

Done, thanks for your review.


Bug: Enabling more than 2 style flags does not work

Description:
Creating a wxTextCtrl with style flags wxTE_READONLY|wxTE_MULTILINE|wxTE_RICH2 is not possible, because code generation yields invalid code.
The generated code is  wxTE_READONLY|wxTE_MULTILINE, wxTE_RICH2 (note the comma instead of pipe).
Example: flags.wxui.txt
Observations:

The broken string is already in the wxui file, so it doesn't seem to be a bug in a specific code generator.
It seems like only the first two flags are separated with a pipe. All additional flags get addd with commas as separators.
wxWindow->window_style also has this problem. There are possibly more places...

What version of wxUiEditor are you using? I ask because I tried this on version 1.1.2 (last release version) as well as the daily build and I could not reproduce the problem.

Yeah, it's not urgent for me (not that it would change anything :)).
I ended up using wxStyledTextCtrl and didn't run into that specific problem.
Anyway, thanks for this great tool. It saves me a lot of time and is pretty easy to use as well.


Add scroll bar to integrated terminal

On Mac I am not getting scrollbars when the content overflows.

Known issue but valid, not sure scrollbars are going to happen unless we fork term.js.

Forking term.js would also be necessary if we wanted to do any improvements to the UX inside the terminal. For example improving the selection experience (related to this), adding links or something to terminal for tighter integration with editor (#1037), making the cursor blink without breaking selection, etc.

I use the integrated terminal only for doing "ng build" and getting an error message about what failed to build. But I am never able to read the cause of the failed build because I can not scroll up. Not every error is in the error windows. Sometimes error appear only at build process.
Thus if you want to justify the existance of the integrated terminal it really needs scrollbars or I have to the CMD.

@bastienJS you should still be able to scroll using the mouse wheel and ctrl+shift+arrows/page up/page down.

This needs to be tackled upstream first at https://github.com/sourcelair/xterm.js/issues/77

OSX 0.11.6 / vscode 1.3.1

fn + up down arrow doesn't work in terminal it gives a ~ character instead.
scroll speed per line results into a much faster and choppy scroll then in a normal vscode editor window, try to make sure scroll speed of all different windows are the same in vscode if technically possible.

Plan B: Disable mouse scroll completely to prevent accidental scrolling and introduce a new button that opens a new editor tab with a copy of the console buffer outbut. As a bonus you can then keep that output and use it as a copy paste clip board.

@gertcuykens the WIP PR is out for the scroll bar https://github.com/sourcelair/xterm.js/pull/218, it supports mouse wheel events that scroll by pixel, line and page. It's very smooth based on my testing so far.

Scrollbar for the integrated terminal would be awesome.

I just updated Code to version 1.5 and the scrolling in integrated terminal doesn't work with my mouse wheel. The only way i can scroll is cmd+arrows

@emartinpi are you using oh-my-zsh? The scroll bar should be visible and working whenever application keypad mode is disabled.

@Tyriar yes, i'm using oh-my-zsh. Application keypad mode was enabled so I disabled it from terminal menu, reset VCode but nothing changed in integrated terminal, the same behavior keeps going

@emartinpi I suspect this is the root cause of the issue https://github.com/sourcelair/xterm.js/issues/151

@emartinpi this worked for me - https://github.com/Microsoft/vscode/issues/7817#issuecomment-229069151

Thanks @jcarter It worked for me as well, but I suppose this workaround may break some key bindings...
@Tyriar Will there be a fix for this issue?

@emartinpi I was hoping someone from the community would be able to chip in on https://github.com/sourcelair/xterm.js/issues/151, I don't use oh-my-zsh personally and won't have time to look at it any time soon.


date in flag made optional

Part of https://github.com/anthonyharrison/csaf/issues/4
In CSAF, date property in flag inside vulnerabilities should be optional and some URL may not contain this.
`In addition, any Flag item MAY provide the three optional properties Date (date), Group IDs (group_ids) and Product IDs (product_ids).

https://docs.oasis-open.org/csaf/csaf/v2.0/os/csaf-v2.0-os.html#3235-vulnerabilities-property---flags
Also, product id should be in array and not be single entity.
Product IDs (product_ids) are of value type Products (products_t) and contain a list of Products the current flag item applies to.

if "references" in vulnerability:
    for reference in vulnerability["references"]:
        vuln_info.set_value(reference["category"], [reference.get("summary",""), reference.get("url","")])

I guess above reference["category"] also needs to be changed to "category":
if "references" in vulnerability:
    for reference in vulnerability["references"]:
        vuln_info.set_value("category", [reference.get("summary",""), reference.get("url","")])


Adds about properties to DS dashboard

Screen Grab: http://phantomjinx.co.uk/stuff/ds-dashboard.png
Partners with https://github.com/Teiid-Designer/komodo/pull/455

about.*

Provides about widget detailing both the web client and repo about
properties fetched using http and rest respectively

Updates teiid widget to add runtime/server version to properties.

About box on the dashboard looks good to me, so it'll satisfy this issue.
I don't know if there is a standard patternfly or JBoss Web UI pattern to expose this information... like Eclipse applications via "Help" dropdown menu.  So we'll wait until anyone asks for more in another issue.. or  not.


[master] v2

support multiple XRC20 tokens
~token holders ranking and percentage~
analytics (DAU, MAU, Stickiness = (DAU/MAU)*100), Uptime)
Delegate List v2: supports enterprise edition of iotex-core
Contract IDE v2
Account System

Domain Service (alias registration)
admin vs non admin. settings based on database instead of config and env var
auth

@puncsky regarding Contract IDE v2 will use start with Remix IDE source or something else?


[Docker] Unable to login

Provide Your Network Information

Where is the location of your server? (i.e. City, or In/Out China) HONG KONG
Which cloud platform(AliYun/Qcloud/DigitalOcean/etc) are you using? DOCKER

run -ti --rm --volume="$(pwd)":/bot zixia/wechaty mybot.ts
It is expected to login after scanning QR code. But, nothing happened. On the android, wechat showed I already logged into webwechat but nothing showed on the console.
Thanks,

Need More Information
Sorry, you did not follow the ISSUE Template, and there's not enough information about your problem.
In order to help us to find the problem out, you should provide all the detail information about the issue. Please make sure you are following the ISSUE Template, answer all the question, and the more important: provide the steps to reproduce the problem.

Sorry here is the message. I just follow your example.
Your Example: docker run -ti --rm --volume="$(pwd)":/bot zixia/wechaty mybot.ts
admins-MacBook-Pro:wechaty admin$ docker run -ti --rm --volume="$(pwd)":/bot zixia/wechaty mybot.ts

\ \      / /__  | |   __ | | _   _
\ \ /\ / / _ / _| ' \ / ` | __| | | |
\ V  V /  / (| | | | (| | || || |
_/_/ _|_|| ||_,|_|_, |
|__/

        https://www.chatie.io

/ |  _ __  _ __   ___  | |() __   __ _
| |   / _ | '_ | '_ \ / _ / | | | ' \ / _` |
| || () | | | | | | |  / (| || | | | | (| |
__/|| ||| ||_|_|_||| ||_, |
|_/

/ | |   __ | || __ )  ___ | | ___
| |   | '_ \ / ` | __|  _ \ / _ | _/ |
| || | | | (| | || |) | () | |__
_|| ||_,|_|/ ___/ _|/
Starting Wechaty v0.10.9 with Node.js v7.10.1 ...
Working directory: /bot
Executing ts-node mybot.ts
05:31:30 INFO Wechaty v0.10.13 initializing...
05:31:30 ERR PuppetWebBridge init() exception: AssertionError: Chromium revision is not downloaded. Run "npm install"
05:31:30 ERR PuppetWeb initBridge() exception: Chromium revision is not downloaded. Run "npm install"
05:31:30 ERR PuppetWeb init() exception: AssertionError: Chromium revision is not downloaded. Run "npm install"
05:31:30 ERR Wechaty init() exception: Chromium revision is not downloaded. Run "npm install"
(node:32) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 4): AssertionError: Chromium revision is not downloaded. Run "npm install"
(node:32) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

\ \      / /__  | |   __ | | _   _
\ \ /\ / / _ / _| ' \ / ` | __| | | |
\ V  V /  / (| | | | (| | || || |
_/_/ _|_|| ||_,|_|_, |
|__/

        https://www.chatie.io

| | () |   / _ \
|  | \ / / | | | | | |
| | >  <| | |  | || |
|___//__|_|  _/

You need to run npm install first. (Before docker run)

the same problem

@liutian1937 What version did you use? Please try v0.12, it should work without any problem.
See: https://github.com/Chatie/wechaty/issues/937#issuecomment-340411445

I'll close this issue due to inactivity.
Please make sure you are using the latest stable version of Wechaty when you ran into issue.
Currently v0.12 should work without any problem.

the same problem with redhat4.8.5&docker1.12.6&wechaty0.13.12
$sudo docker run -ti --rm --volume="$(pwd)":/bot zixia/wechaty mybot.js

\ \      / /__  | |   __ | | _   _
\ \ /\ / / _ / _| ' \ / ` | __| | | |
\ V  V /  / (| | | | (| | || || |
_/_/ _|_|| ||_,|_|_, |
|__/

https://www.chatie.io

/ |  _ __  _ __   ___  | |() __   __ _
| |   / _ | '_ | '_ \ / _ / | | | ' \ / _` |
| || () | | | | | | |  / (| || | | | | (| |
__/|| ||| ||_|_|_||| ||_, |
|_/

/ | |   __ | || __ )  ___ | | ___
| |   | '_ \ / ` | __|  _ \ / _ | _/ |
| || | | | (| | || |) | () | |__
_|| ||_,|_|/ ___/ _|/
Starting Wechaty v0.13.12 with Node.js v8.9.0 ...
Working directory: /bot
Executing babel-node --presets env mybot.js
12:08:54 WARN Wechaty init() DEPRECATED and will be removed after Jun
2018. Use start() instead. 12:08:54 INFO Wechaty v0.13.12 starting...
12:08:54 ERR PuppetWebBridge init() exception: AssertionError
[ERR_ASSERTION]: Chromium revision is not downloaded. Run "npm install"
12:08:54 ERR PuppetWeb initBridge() exception: Chromium revision is not
downloaded. Run "npm install" 12:08:54 WARN PuppetWebBridge quit()
page.close() exception: TypeError: Cannot read property 'close' of
undefined 12:08:54 WARN PuppetWebBridge quit() browser.close()
exception: TypeError: Cannot read property 'close' of undefined
12:08:54 ERR PuppetWeb init() exception: AssertionError
[ERR_ASSERTION]: Chromium revision is not downloaded. Run "npm install"
12:08:54 ERR Wechaty start() exception: Chromium revision is not
downloaded. Run "npm install" (node:32)
UnhandledPromiseRejectionWarning: Unhandled promise rejection
(rejection id: 1): AssertionError [ERR_ASSERTION]: Chromium revision is
not downloaded. Run "npm install" (node:32) [DEP0018]
DeprecationWarning: Unhandled promise rejections are deprecated. In the
future, promise rejections that are not handled will terminate the
Node.js process with a non-zero exit code.

\ \      / /__  | |   __ | | _   _
\ \ /\ / / _ / _| ' \ / ` | __| | | |
\ V  V /  / (| | | | (| | || || |
_/_/ _|_|| ||_,|_|_, |
|__/

https://www.chatie.io

| | () |   / _ \
|  | \ / / | | | | | |
| | >  <| | |  | || |
|___//__|_|  _/

@zhuaoyuan Could you please run the following command and submit the output log?
docker run zixia/wechaty:0.12.0 doctor
docker run zixia/wechaty:0.12.0 test

@zixia
Have sent logs to<EMAIL_ADDRESS>

@zhuaoyuan Please post the logs by replying this issue, because we can easily track all the related information.
Thanks!

@zixia Here it is.
wechaty-log.txt


[FEATURE]: ATTACH support

Describe what you want
I know this is probably on your radar but wanted to put this in. With the ability to now ATTACH db's in Turso would love the feature to be implemented.
This is my suggestion and would require Turso to have createClient() return the id of the db.
import { db as db_one } from '../server/db/first/client'
import { db as db_two } from '../server/db/two/client'
import { users as users_one } from '../server/db/one/schema'
import { users as users_two } from '../server/db/two/schema'
import { alias } from 'drizzle-orm/sqlite-core'
import { eq } from 'drizzle-orm'

const attached = alias(db_two, 'attached')

// stupid query I know, lets just say ones normal users, the other is managers/admins
const res = await db_one.attach(attached).select().from(users_two).where(eq(users_two.id, users_one.id))

This way we keep the drizzle way of building, apis stay similiar. You also get the win of separate clients/schemas, and can implement attach for other databases that don't support the ATTACH keyword but drizzle can do some magic under the hood etc.

must have! waitin..

+1 on this, only feature missing for us to adopt Drizzle!

+1. Would be great!

For my use case, I only need to run ATTACH DATABASE once at app startup. I got this working with a custom SQL statement, but wanted drizzle's native schema support for working with tables in the attached DB.
I got that working with the sqliteTableBase function which is already included in drizzle source code but isn't exported (I copy and pasted into my codebase to test). That function includes a schema argument, which works if you point it at the alias of your attached database.


observability deployment_id self

I am following the documentation here: https://registry.terraform.io/providers/elastic/ec/latest/docs/resources/ec_deployment
It says that I can use:
observability {
  deployment_id = "self"
}

To store the observability data in the current deployment. However I get an error in terraform using that:
│ Error: observability ref_id auto discovery: deployment get: 1 error occurred:
│       * id "self" is invalid

Maybe I have this block in the wrong place?

No I actually gave up on using terraform for elastic. The resources that can be managed feel very limited so not any huge benefits from managing the cluster setup from TF rather than the UI. I had been hoping to manage dashboards, indexes etc but I don't think it supports all the resources.

Btw, the solution turned out to be to bump the provider version up to the latest version (v0.5.0)

@jonnymccullagh @andrea-berling fwiw the Elastic Stack provider supports managing Elasticsearch resources and we're working on supporting Kibana (specifically alerts and dashboards) now.

@andrea-berling @jonnymccullagh as mentioned - you need to update the provider for the functionality to be available :)
and as @tobio mentioned, the Elastic Stack provider supports Elastic stack object configuration.
Closing this issue for now.


EventEmitter NotFound

When packager cannot found this file, then an error occurred as https://github.com/facebook/react-native/issues/4968

Whoops!! my bad

@behzad888 what was the error?
I am facing the same error.

@mukeshkamboj  Please see #12 and https://github.com/magicismight/react-native-root-toast/issues/44.

Thanks for your help @behzad888
Now I understand the root cause of this error.

@mukeshkamboj will you merge it in the coming days?

@magicismight will you merge it in the coming days?


Cannot connect - Failed to access None

I've verified all settings, and can connect to REPL using picomon. ST3 w/ micropython tools will not connect and gives the error "Failed to access None. Please check connection or settings."
EDIT - I originally tested this on OSX Catalina. Switching to a linux laptop I am given the same error message and cannot connect.

Hi, it has been looooooooong times after this repository. I'm not able to remember everything. But its look like about serial comm. Can  you verify the rights of your user for the port?

Hi.
I have the same error, on windows 10, 64 bit.

I did have the same issue On my end the problem was with package not being able to fetch user settings from the file.
I have downloaded a folder with application code to Packages folder within Sublime Text installation, and changed line 228 of micropython.py to not feature spaces in folder name:
{"base_file": "${packages}/st3-micropython-tools/MicroPython.sublime-settings"}

Hi @sacp can you review and test the slotion which provided by @szromek . We can update the source after the reviews. I don't have any boards to run micropython anymore... :(
PRs are welcome if its working, btw ^^

Still an issue.
I am using sublime text on Linux, and I have proper perms for the device (I access it using screen)
If anyone managed to fix this please let me know.


Unable to use Oracle DB as the datasource

Hi,
I am trying to use Oracle DB as the data source for superset but the connection to the Data base fails with a very generic error message. I have the tried connecting to the Oracle DB using a 'SqlPlus' client from the same host using the same credentials and that connects without any issues.
This is the connection string that I am using to connect to Oracle DB:
oracle://<username>:<password>@<host-name>:<port>
Expected results
Successfully connect to Oracle DB
Actual results
I see the below error message in the logs
Unexpected error DatabaseError ERROR:superset.views.core:Unexpected error DatabaseError
How to reproduce the bug

Go to Add data sources in superset UI
Try connecting to ORacle DB

Environment

superset version: 0.37.2
python version: 3.6

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[ Y] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[ Y] I have reproduced the issue with at least the latest released version of superset.
[ Y] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

Issue was resolved after using ldconfig instead of env variables to set path to oracle instant client.


Cleanup BWA launch script

mesos launch script should not have --output_dir set by default, especially writing to /home/mesosbox/shared.

Keep in mind that Toil 3.2.0 will have a reasonable default for --workDir that will put it on ephemeral.
Consider adding a comment that signifies argument as a stop-gap and that it should be removed.

@hannes-ucsc , I mistyped --output_dir somehow.  Sorry, --workDir is set to /var/lib/toil already.


Failover does not add any LUN disks to RHVM

Initiating a failover does not trigger any action to add the LUN disk to RHVM. The mapping file contains the lun disks. The host logs into the lun. But the failover completes without adding the lun disk into rhvm. The result is, the VMs dont have any disks added and therefore fail to boot later in the playbook execution process.
Critical blocker - ovirt-ansible-disaster-recovery does not work.

Hi, Can you please submit a bug using bugzilla if it is still relevant?
https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine
This repository is now in read-only mode.

Hi, it is still relevant unless fixed. Can you confirm fixed? Else
please do the needful.
Regards,
Tony Pearce
On Wed, 28 Oct 2020 at 19:57, Eyal Shenitzky<EMAIL_ADDRESS>wrote:

Hi, Can you please submit a bug using bugzilla if it is still relevant?
https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine
This repository is now in read-only mode.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/oVirt/ovirt-ansible-disaster-recovery/issues/77#issuecomment-717885377,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGIUMGDNUJ52QGH47H7GLWTSNABLTANCNFSM4J3WI6MA
.

Development moved to https://github.com/ovirt/ovirt-ansible-collection If this is still relevant, please reopen there.


config(dm): adjust safe mode duration when start/resume

What problem does this PR solve?

Issue Number: close #6224
What is changed and how it works?
add configuration to adjust safe mode duration

set "0s", not step in safe mode
set "1s" or "1h", step in safe mode one second or one hour
do not set it, step in safe mode as same as internal default( now is 60s )

Check List
Tests

Unit test
Integration test
No code

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
add configuration to adjust safe mode duration

/cc @GMHDBJD @lance6716

Codecov Report

Merging #6225 (e9741ec) into master (ef587e6) will decrease coverage by 0.4222%.
The diff coverage is 64.5161%.

Flag
Coverage Δ

cdc
63.7709% <67.9577%> (-0.9138%)
:arrow_down:

dm
51.8933% <49.2857%> (+0.0041%)
:arrow_up:

engine
62.5961% <58.6885%> (+0.0621%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #6225        +/-   ##
================================================
- Coverage   58.4193%   57.9970%   -0.4223%
================================================
  Files           711        712         +1
  Lines         84205      83387       -818
================================================
- Hits          49192      48362       -830
- Misses        30540      30671       +131
+ Partials       4473       4354       -119

/hold
need understand safe mode more

we already have safe-mode-duration, can safe-mode-duration = 0 be used for this scenario? @okJiang

we already have safe-mode-duration, can safe-mode-duration = 0 be used for this scenario? @okJiang

Yes，we can use it. @lance6716

set 0, not step in safe mode when resume
set x, step in safe mode x second when resume
set -1(default), step in safe mode as same as internal ( now is 5s )

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

all test passed. ptal again~ @lance6716 @GMHDBJD

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test
/run-verify

the it is passed, ptal again. @lance6716 @GMHDBJD
It should be noted that if disable safe-mode derectly when beginLocation equal safeModeExitPoint, it cause lots of bugs. I can't do it this pr and revert it. https://github.com/pingcap/tiflow/pull/6225#discussion_r923607530.

/run-dm-integration-test

/run-dm-integration-test

Will this part https://github.com/pingcap/tiflow/blob/b4bbb862318b6a516e591678a2fe098cbba2b6d4/dm/syncer/syncer.go#L3147 affect user? Can we remove this logic?

Another requirement is to report an error when safemode-duration is too short, did you implement it?

/run-dm-integration-test

Will this part
https://github.com/pingcap/tiflow/blob/b4bbb862318b6a516e591678a2fe098cbba2b6d4/dm/syncer/syncer.go#L3147
affect user? Can we remove this logic?

I don't confirm. Have you any suggestion? @lance6716

Will this part
https://github.com/pingcap/tiflow/blob/b4bbb862318b6a516e591678a2fe098cbba2b6d4/dm/syncer/syncer.go#L3147
affect user? Can we remove this logic?

I don't confirm. Have you any suggestion? @lance6716

I also don't know why we need to open safe mode. Maybe it's because for the old versions when shard resync we didn't maintain checkpoint correctly, so we need safemode as walkaround. I think if CI can pass it's OK to remove it

Will this part
https://github.com/pingcap/tiflow/blob/b4bbb862318b6a516e591678a2fe098cbba2b6d4/dm/syncer/syncer.go#L3147
affect user? Can we remove this logic?

remove this will bring much workload. Don't move it now

/run-dm-integration-test

Another requirement is to report an error when safemode-duration is too short, did you implement it?

we can add some note in document.

it passed https://ci2.pingcap.net/blue/organizations/jenkins/dm_ghpr_integration_test/detail/dm_ghpr_integration_test/7890/pipeline

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

https://github.com/pingcap/tiflow/blob/8f3fd7a7f30fa6eefc9bc95879eee2653ab6c937/dm/dm/config/task.go#L1075 Copy the new config item for downgrade and omit it if it has default value

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/cc @GMHDBJD @lance6716

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

please check the log, don't blindly rerun CI. @okJiang

/run-dm-integration-test

shardddl2 failed
/run-dm-integration-test

ptal~ @lance6716 @GMHDBJD

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-all-test

/run-all-tests

/merge

/merge


Added support for IP compression when using --linux_perf_ipt_block

Add support for IP compression when using Intel PT for hardware-based coverage-feedback fuzzing
When using Intel PT for hardware-based coverage-feedback fuzzing (with the --linux_perf_ipt_block option), IP compression is ignored (see Intel® 64 and IA-32 Architectures Software Developer’s Manual Vol. 3C Section <IP_ADDRESS> "Target IP (TIP) Packet"). As a result, there will be many collisions in the coverage bitmap.
This issue is also mentioned in this README by the developers of libxdc:

Hongfuzz: Similarly to PTrix, honggfuzz avoids disassembling the stream and instead only considers the contend of the TIP packages. It should be noted that it seems like the authors ignored TIP compression and hence cause a significant amount of collisions in the bitmap.

To support IP compression, the latest IP emitted by TIP, TIP.PGE and TIP.PGD Intel PT packets is tracked using last_tip_ip.

Thank you!

Thank you!


Support of taxonomy element for big taxonomies loading data through ajax

Taxonomy fits perfectly with data where it is involved localization. For example:
Country -> State -> City
or
Country -> State -> City -> Shop
However, problem is current taxonomy element for dynamic forms loads the entire collection. That is too much data to send to the client without need on scenarios where localization is included in the taxonomy.
Solution could be to allow base different taxonomy elements on the same taxonomy. Each taxonomy will render only terms of one level of the taxonomy. First taxonomy element will show only root terms, second one though ajax will load terms of the next level based on the selected term on the first taxonomy element, and so on.

I've implemented this functionality. However, currently I cannot provide a PR because it is based on the branch implementing this feature https://github.com/OrchardCMS/Orchard/issues/6163 in my company repo. So, it would be needed you accept a PR for first feature in order I can submit a PR for this issue.
This are the changes added for implementing this issue:
https://github.com/xkproject/Orchard/compare/xkproject:%236163editDynForms...%236816_TaxonomyElementWithAjax


feat: add Hackmanit/Web-Cache-Vulnerability-Scanner

#1554 Hackmanit/Web-Cache-Vulnerability-Scanner

https://github.com/Hackmanit/Web-Cache-Vulnerability-Scanner
Web Cache Vulnerability Scanner is a Go-based CLI tool for testing for web cache poisoning. It is developed by Hackmanit GmbH

$ wcvs -u https://example.com
WCVS v1.0.0 started at 2021-12-28_14-03-24
wordlists/headers: open wordlists/headers: no such file or directory

I don't know aqua can support this tool.


Provide compiled provider for "main" architectures

Hello,
It would be great if a few binaries could be provided with the releases, at least for amd_64 arch. Compiling from the sources is nice when only one guy works with it, but here we're a bit more, and integrating this provider in our workflow is just not possible in the current situation.
If you (dev team :)) could provide a couple of pre-compiled binaries, it would just make life easier :).
Thank you in advance!
Cheers,
C.

@cjeanneret thx  i don't think is really complicated task to do it, and i can agree that it would help for people that are non-go familiar.
I will have a look

https://github.com/goreleaser/goreleaser

The main issue is that you would need distro specific builds because of the libvirt dependency.
I suggest we build in OBS using a _service file tracking the latest tag for SUSE, Fedora, CentOS, Ubuntu, and then unpack the single binary from published packages via CI and publish them on Github, or somewhere where users are most likely to find it (few people use Terraform itself from packages).
But that would guarantee a secure and correct build.

@dmacvicar thanks for feedback, i thinkit make sense.
I am also thinking about Dockerfiles (Ubuntu, Fedora, SUSE) and containers where we could build the pkgs inside and add also the pkg dependencies.
As an advantage i see that this could be directly hosted here like in release dir and could be more open.
Additionally we could add/interface concourse-ci or other CI systems.
I don't see to much drawbacks on the container solution, but i think maybe you see some of them. :thinking:
The OBS solution is see it more advanced and customizable, but as drawback we have the unpacking CI step and the pkg hosting somewhere or adding the PWD on obs.
I like both solution but i tend to consider the docker solution more open for contributors. ( i might don't see any drawbacks) :thinking:

I am not against building on Docker, but I don't want to publish binaries built on somebody's laptop.

@dmacvicar ok, in both way we need to setup CI for this project. ( even with obs we need to unpack it somewhere).
I have in mind 2 ideas:
-1) we can have a concourse.ci.opensuse (free on opensuse server) for building pkgs
-2) we can use jenkins-pipeline on a opensuse.ci.suse.de
I can volonteer for this and feel free to addme in geekops if this is needed for doing this tasks.

0.4 is released and now we provide builds (a simple tar with the binary) for different distributions:
https://github.com/dmacvicar/terraform-provider-libvirt/releases/tag/v0.4 is the first release to include them.

https://download.opensuse.org/repositories/home:/dmacvicar:/terraform-provider-libvirt:/stable has the builds for the latest stable tag.
https://download.opensuse.org/repositories/home:/dmacvicar:/terraform-provider-libvirt/ has the builds for master branch


Add Ubuntu Noble support notes

Summary
Add Ubuntu Noble support
NB: this can be merged only after the next release, either patch or minor, and we have verified that server and omnibus work fine on Ubuntu Noble.
Ticket Link
https://mattermost.atlassian.net/browse/CLD-7799

Friendly reminder @toninis @phoinixgrr that this docs PR will benefit from your reviews. Thanks!

@mvitale1989 - Is this being tested as part of v9.11 release readiness? Or should we target a different milestone to publish this docs PR update?

@cwarnermm All test servers are upgraded to Ubuntu Noble, and i have run the automated E2E Cypress tests on Ubuntu Noble as well, it is on track for v9.11 :+1:
cc @amyblais @saturninoabril FYI

Fantastic! Thanks, @mvitale1989!!

Thanks @mvitale1989, great work in adding support to Noble and ensuring it's fully tested!


Add Shortcuts Help

Add a Help shortcut like ? to display all the shortcut keys and their functions

Duplicate of #4279


AKS Learn feedback: typo (nodepool name mismatch)

Type of issue
Typo
Feedback
There is a mismatch in the content of "Add a manual scale profile to a node pool" section.
In the text, the node pool name is "myvmpool," but in the command, it is "myvmpool1."
It's a minor difference that can be noticed upon careful reading, but it caused confusion at first glance. I would appreciate it if you could make the correction.
Page URL
https://learn.microsoft.com/en-us/azure/aks/virtual-machines-node-pools
Content source URL
https://github.com/MicrosoftDocs/azure-aks-docs/blob/main/articles/aks/virtual-machines-node-pools.md
Author
@wdarko1
Document Id
5b8d05eb-273f-e369-a3f5-4c739008b3e3

#reassign:schaffererin

Hi, @torumakabe. Thank you for your feedback!
I've merged a PR that addresses this issue, and the changes will be live in the AKS documentation shortly.
I will now close out this issue. Thanks again :)
#please-close


Discussion paper for Issue#34 and PR#123

The discussion paper raises two separate topics:
Terminology
The paper proposes to replace the terms public and private used in PR #123 with observed and local. I make the following observations:

For the "normal" case when IPv4 CGNAT is in operation, the observed parameters will be the public parameters, and the local parameters will be the private parameters. The terms are essentially synonymous. For IPv4 scenarios, I would expect CGNAT to be in operation for the vast majority of commercial use cases for this API.
For the "exception" case when CGNAT is not in operation, the terms are not synonymous:

The parameters in use will be either private or public (almost certainly private), but cannot be both
The observed and local parameters will therefore be identical

As I only really care about the first case (when CGNAT is in operation), I really don't mind whether the terms private / public or local / observed are used. It's not at all clear to me which terminology a developer will find more intuitive. I would suggest a poll to decide this.

API Design and Constraints on API Caller Input Options
Good API design not only allows the API caller to specify the parameters required, but also places logical (i.e. machine enforceable) constraints on the values and combinations of parameters that can be specified.
Required Parameter Combinations
The discussion in Issue #34 showed that the following parameter combinations are required if the API caller wishes to identify the UE using its IPv4 address:

The API caller MUST specify the public IPv4 address as well as EITHER the private IPv4 address OR the public port
Using the proposed terminology, the API caller MUST specify the observed IPv4 address and EITHER the local IPv4 address OR the observed port

The proposal on Page 9 of the discussion document does not help to enforce these requirements

If the API caller specifies an IPv4 subnet as localIpAddr, there is no requirement for them to also specify an observedIpAddr IPv4 subnet
If the API caller specifies an observedIpAddr IPv4 subnet, there is no requirement for them also to specify either a localIpAddr IPv4 subnet or a uePorts->observedPorts value

Much of the discussion in Issue #34 and the associated PR #123 was about trying to enforce these requirements on the API caller, who may not understand why they need to additionally provide public_address if they want to identify the UE by private_address, but must understand that they have to do it.
Additional observations

The discussion paper proposal introduces a new requirement that, if the UE is identified by IP address(es), then either IPv4 or IPv6 addresses must be specified, but not both.

This excludes dual-stack scenarios, which are currently allowed by the API design. Mixed IPv4 / IPv6 scenarios deserve a whole issue to themselves, and should not be excluded without some additional discussion.

Separate local and observed fields for IPv6 addresses don't really make sense as they will always be the same value
The proposal allows for UEs to continue to be identified by arbitrarily large subnets, when the discussion in the issue concluded that UEs should be identified by single IP addresses
Knowing localPorts is useless for identifying the UE (because all UEs can use almost any source port value) but observedPorts is useless for flow descriptions. The two reasons for specifying ports (UE identification and flow descriptions) should be separated. Only a single observed (i.e. public) port should be specified.
More generally, it is not clear to me that localPorts is required for flow descriptions rather than just using wildcards. Maybe if the UE is acting as a router and sending multiple flows to the same application server IP:port combination, then different QoS levels will be required for the different flows, but how does the API caller learn the local port in that case? Anyway, use of UE ports in flow rules requires a separate discussion issue of its own.

I will shortly make an alternative proposal in the original Issue #34 which deals with using the API design to constrain allowed API caller input parameter options.

@emil-cheung
As discussed during the meeting, the discussion paper omits the scenario that Issue #34 was originally created for, which is where the device (i.e. UE) or, more specifically, an application running on the device directly requests the QoD service.
In this case, the device can easily find its private (local) IPv4 address if it does not know or have other parameters (external identifier, msisdn, etc.) but, as discussed in Issue #34, this is insufficient to identify the device uniquely. Hence the proposal is that the device obtain its public (observed) IPv4 address and then provide both parameters to the QoD service.
How does the device obtain its public IPv4 address? By using DNS, as follows:
dig @resolver1.opendns.com A myip.opendns.com +short -4

Try it - it really works. It works for any DNS client (e.g. nslookup) with suitable syntax changes, but you have to use the opendns resolver (or another resolver that supports this functionality). There are also HTTP APIs that can be used to obtain this information.
So a mobile app can obtain sufficient information to identify itself by IPv4 address to the QoD service without involving the application server, and the proposed API changes in Issue #34 were designed to address this scenario.


Cli(ticdc): add safepoint command

What problem does this PR solve?

Issue Number: close #11470
What is changed and how it works?
Add safepoint command which can query, set and delete servicesafepoint. It works by updating ttl with pd.client.UpdateServiceGCSafePoint and query pd's API to show all service gc safepoints.
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
need update user documentation
Release note
None.

/ok-to-test

Perhaps it makes more sense for set and delete operations to return only the modified fields? In such way, the user can clearly know the result of the operation, and can query again if the user needs to confirm all Safepoints.

Perhaps it makes more sense for set and delete operations to return only the modified fields? In such way, the user can clearly know the result of the operation, and can query again if the user needs to confirm all Safepoints.

delete will not return the modified fields


Rake tasks always skipped

su -s /bin/bash -c 'bundle exec /opt/elasticbeanstalk/support/scripts/check-for-bundle exec rake-task.rb assets:precompile' webapp
bundler: command not found: /opt/elasticbeanstalk/support/scripts/check-for-bundle
Install missing gem executables with bundle install
echo 'No assets:precompile task in Rakefile, skipping asset compilation.'
No assets:precompile task in Rakefile, skipping asset compilation.

su -s /bin/bash -c 'bundle exec /opt/elasticbeanstalk/support/scripts/check-for-bundle exec rake-task.rb db:migrate' webapp
bundler: command not found: /opt/elasticbeanstalk/support/scripts/check-for-bundle
Install missing gem executables with bundle install
echo 'No db:migrate task in Rakefile, skipping database migration.'
No db:migrate task in Rakefile, skipping database migration.

I solved it by adding this config:
container_commands:
  02_compile-assets:
    command: bundle exec rake assets:precompile
  03_migration:
    command: bundle exec rake db:migrate

But is there a way to fix this in your config?

Thanks for reporting this, Max!
Truthfully, I have no idea. I no longer use Elastic Beanstalk (moved to Kubernetes).
You're using the Passenger AMI, right?

@gkop Thank you for answering.
No, I'm using Puma.
Don't think that's related but you should change everywhere where you use

/opt/elasticbeanstalk/containerfiles/.post-provisioning-complete

to

/opt/elasticbeanstalk/support/.post-provisioning-complete

because of that, the first two commands always run instead of just on the first deploy

Ah, I'm not sure this repo ever worked very well with Puma. I recall the Puma AMI being quite different than the Passenger one.
I moved to Kubernetes because it's not proprietary to Amazon. I never really like Elastic Beanstalk, it felt too hacky.

In my case I forgot to include the Rakefile in the zip of the source code.
Before including Rakefile
2023/11/15 15:28:38.062190 [INFO] Running command /bin/su webapp -c bundle exec /opt/elasticbeanstalk/config/private/checkforraketask.rb db:migrate
2023/11/15 15:28:38.415446 [INFO] rake aborted!
No Rakefile found (looking for: rakefile, Rakefile, rakefile.rb, Rakefile.rb)
/opt/elasticbeanstalk/config/private/checkforraketask.rb:21:in `<top (required)>'
/bin/bundle:25:in `load'
/bin/bundle:25:in `<main>'
(See full trace by running task with --trace)

023/11/15 15:28:38.415465 [INFO] No db:migrate task in Rakefile, skipping db:migrate.

After including it:
2023/11/15 15:41:10.369753 [INFO] Running command /bin/su webapp -c bundle exec /opt/elasticbeanstalk/config/private/checkforraketask.rb db:migrate
2023/11/15 15:41:11.109087 [INFO] Found db:migrate task in Rakefile
2023/11/15 15:41:11.109132 [INFO] Running command /bin/su webapp -c bundle exec rake db:migrate
2023/11/15 15:41:12.932420 [INFO] ==<PHONE_NUMBER>4950 CreatePosts: migrating ======================================
-- create_table(:posts)
   -> 0.0099s
==<PHONE_NUMBER>4950 CreatePosts: migrated (0.0100s) =============================
...


[UX] Clicking the profile card should redirect to the user's profile page

Is your feature request related to a problem? Please describe.
As of now, clicking the sidebar's profile card opens up the 'Edit Profile' dialog.
The problem is, most users would expect to be redirected to their profile page when clicking on this element (just like other social media platforms do ; e.g. Twitter).
Describe the solution you'd like
Clicking the sidebar's profile card should redirect the user to their profile page instead of opening up the 'Edit Profile' dialog.
Additional context

This is temp while we don't have a proper settings page

@ajmnz But there is an 'Edit Profile' button on the profile page itself! The current design seems redundant, not standard and doesn't make sense regardless of whether or not a Settings page is available.

Many users were complaining that they didn’t see where to edit the profile. We now have this button in the profile page because it was implemented two days ago.
This behavior will eventually be replaced for a link to the profile page.


[core] Fix TS error in reportBrokenLinks script

Fixes the TS check in CI, it didn't pass when https://github.com/mui/base-ui/pull/903 was merged

[x] I have followed (at least) the PR section of the contributing guide.

Example of a failing build: https://app.circleci.com/pipelines/github/mui/base-ui/5513/workflows/31a96b61-2b6c-4d9d-a272-e4978f5f1eb4/jobs/42537


fix(RELEASE-1118): fix partial oci auth match in rpm task

cosign is flakey when there are partially matching auth entries in the docker config file. This commit modifies the push-rpm-manifests-to-pyxis task to create a new docker config file for each image processed so that the only entry in the docker config file will be one for the image about to have its sbom downloaded.

/test release-pipelines-e2e-suite

/test release-pipelines-e2e-suite

/test release-pipelines-e2e-suite

/test release-pipelines-e2e-suite

/test release-pipelines-e2e-suite

/test release-pipelines-e2e-suite

/test release-pipelines-e2e-suite

/test release-pipelines-e2e-suite

/test release-pipelines-e2e-suite

/test release-pipelines-e2e-suite

/test release-pipelines-e2e-suite

/test release-pipelines-e2e-suite

/test release-pipelines-e2e-suite

/test release-pipelines-e2e-suite


Get Print function working again; improvements started for OBS tQ and OBS tN

Some packages also updated.

Pull Request Test Coverage Report for Build 270

4 of 31 (12.9%)  changed or added relevant lines in 5 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.6%) to 59.641%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

client_converter_callback.py
0
5
0.0%

preprocessors/preprocessors.py
1
10
10.0%

door43_tools/project_deployer.py
1
14
7.14%

Files with Coverage Reduction
New Missed Lines
%

door43_tools/project_deployer.py
1
17.05%

Totals

Change from base Build 266:
-0.6%

Covered Lines:
2892

Relevant Lines:
4849

💛  - Coveralls


Modularized pycubed

Just added a bunch of my comments. Here are the notes from today's meeting:

[ ] Move everything into one pycubed.py file
[ ] Remove extra stuff (logging, radio stuff)
[ ] Move the pycubed.py file to drivers/pycubedmini