Add static channel dropdown

@jarredwitt Mattermost PRs are merged with squash commits (instead of merge commits or fast forwards) so our individual commit messages don't leave as noticeable of a trail, but there are a few principles that we should keep in mind:

Always try to rebase your branch off of master (or any other branch) instead of merging.
 So in this case, commits e4e6659, 30cdac3, and e0864c4 would become a single commit when you're ready to push/open your PR.

The importance of naming/terminology in software can't really be overstated. Naming is especially important this early on in a project. "Header" is a reasonable term for the component at the top of the channel view. It is already referred to as such in both the code and by members of the team/community (i.e. "nav header", "channel header"). And that usage is quite common in frontend web development.
But "header" is one of the more overloaded terms in this project and in UIs in general. (Several competing instances could be listed here.) I think that topbar would be a more accurate and obvious term. Plus: this usage of "header" seems anachronistic in a mobile app.
@jarredwitt, @harrison, @elias What are your thoughts?

@enahum, @hmhealey, @jarredwitt
Soon we should set up CI to at least run eslint. I'd really like to configure it to display here on the PR any warnings that were issued, even if the build wasn't broken by a full-on error. If that's not possible, then we could use a service like Hound for this. It'll add inline comments for style violations.

I don't mind calling the components Topbar instead of Header as long as the text in the UI for things like Channel Header remain the same. I actually changed the name of the sidebars to drawers as it has more meaning in a mobile app.

As far as I know the CI is up and running, it does run eslint and the tests under the test folder, dunno if we can post here the styling errors with mattermod maybe @hmhealey can confirm that, I would prefer to have that functionality within mattermod and not adding another service, but in the event we are unable to do that, we can discuss a little bit further the use of Hound.

Marking this as work in progress since we've got the new designs for the ChannelInfo scene


Random fixes

#54 by @Fausto95 had two small issues:

The color for input needs to be of the exact format 6 lowercase hexadecimal (#ffffff) for it to work
Arrows didn't receive the stroke color

After that change, the top UI becomes pretty cluttered and hard to parse. I moved all the options into fieldsets and moved the non-essential ones below the fold. We'll need to have a proper structure there but at least it should get us going for a bit more time :)

Thanks for fixing them @vjeux.
Btw the UI looks amazing after these changes


Crash when Process produce the error

The crash happen in release mode or build with Xcode, this can temporary fix by ignoring the signal using signal(SIGPIPE, SIG_IGN) in applicationDidBecomeActive and applicationWillUnhide in AppDelegate, but won't fix when building a release app
import Cocoa
import FlutterMacOS

@NSApplicationMain
class AppDelegate: FlutterAppDelegate {
    override func applicationDidBecomeActive(_ notification: Notification) {
        signal(SIGPIPE, SIG_IGN);//Ignore signal
    }

    override func applicationShouldTerminateAfterLastWindowClosed(_ sender: NSApplication) -> Bool {
        return true
    }

    override func applicationWillUnhide(_ notification: Notification) {
        signal(SIGPIPE, SIG_IGN);
    }

    override func applicationWillBecomeActive(_ notification: Notification) {
        signal(SIGPIPE, SIG_IGN);
    }
}

Example code: Try to run some command that the Process will produce the error, for my case by executing npm -v
import 'package:flutter/material.dart';
import 'dart:io';

import 'package:pretty_json/pretty_json.dart';
void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key key, this.title}) : super(key: key);
  final String title;

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

class _MyHomePageState extends State<MyHomePage> {
  var text = '';

  void _incrementCounter() async {

    var result = await Process.run("npm",["-v"]);
    print(result.stdout);

    setState(() {
      text = result.stdout;
    });

    // var env = Platform.environment;
    // print(prettyJson(env));

    // setState(() {
    //   text = prettyJson(env);
    // });
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: Center(
        child: SingleChildScrollView(
          child: Column(
            mainAxisAlignment: MainAxisAlignment.center,
            children: <Widget>[
              SelectableText(text),
            ],
          ),
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: Icon(Icons.add),
      ),
    );
  }
}

Flutter doctor -v:
[✓] Flutter (Channel dev, 1.26.0-12.0.pre, on Mac OS X 10.15.7 19H2 darwin-x64,
    locale en-US)
    • Flutter version 1.26.0-12.0.pre at /Users/macbook/Developer/flutter
    • Framework revision a706cd2112 (7 weeks ago), 2021-01-14 18:20:26 -0500
    • Engine revision effb529ece
    • Dart version 2.12.0 (build 2.12.0-224.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/macbook/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /Users/macbook/Library/Android/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.0.1, Build version 12A7300
    • CocoaPods version 1.10.1

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.50.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (1 available)
    • macOS (desktop) • macos • darwin-x64 • Mac OS X 10.15.7 19H2 darwin-x64

• No issues found!

Hi @LeXuanKhanh
closing as a duplicate of https://github.com/flutter/flutter/issues/76989
Follow up from https://github.com/flutter/flutter/issues/75911#issuecomment-788216117
Thank you

Hi @TahaTesser, this is not related of that issue, @stuartmorgan comment only explain why the environment is different, but not give the solution or the explanation for this crash
You can make the crash not just execute some not found executable, but some random invalid command too like abc
I expected when this happen, the Process only throw an error and not crash my whole app

in release mode or build with Xcode

FYI, it would be helpful in future bug reports if you could be more precise about the way you are describing building and launching when it's relevant to the issue. "Release mode" and "with Xcode" are completely orthogonal things—you can build in release or debug modes with flutter build, flutter run, or the Xcode UI—so saying "release mode or with Xcode" doesn't really make sense.

There are steps relevant to the way which I build and run
Release mode: I run the flutter build macos then run the .app file in Build/macos/Build/Product/Release folder
Run with XCode: press the Build button in XCode
Run with Android Studio: run debug with Android Studio (press Run or Debug button)


Unregistering a Twilio instance does not end active calls on it.

Issue Summary

Steps to Reproduce

Make a call
Unregister from TwilioVoice.instance while the call is still ongoing

Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?
Since I no longer have a token, I should be expected to be disconnected from all calls.

I think it is expected behavior, unregister call back only unregister the current token and prevent getting further calls, you should call the hangup method before calling unregister

Hi @yacoublambaz
Yes, this is intended behaviour as @bazl-E suggests and would be rather odd and unintuitive to have the call dropped when unregistering. This should be handled by the developer on a case by case basis.


Include request attributes in key used for caching authorization

Two things I wonder about in this context:

Does memcached enforce any "restrictions" on the used keys? (length, allowed characters)
Should we "obfuscate" the token in some way? This might not matter too much when the in-memory cache used, but using a valid token as a key in a memcached seems wrong.

Refs https://issues.redhat.com/browse/LOG-4393
PTAL @periklis

Two things I wonder about in this context:
* Does memcached enforce any "restrictions" on the used keys? (length, allowed characters)

According to their source code the max key length is 250 Bytes: https://github.com/memcached/memcached/blob/1.6.21/memcached.h#L68
Additionally Redis keys are strings and the usual limit for the string data type is 512 MB: https://redis.io/docs/data-types/strings/#limits

* Should we "obfuscate" the token in some way? This might not matter too much when the in-memory cache used, but using a valid token as a key in a memcached seems wrong.

I would obfuscate by default regardless cache type.

Refs https://issues.redhat.com/browse/LOG-4393
PTAL @periklis

@periklis I opted to hash the userinfo, leaving just the "username" in the plain information (mostly for debugging purposes, I can also take that one out just leaving the hash). I hope this doesn't make the CPU usage increase too much. I can have a look on a test-cluster.


Install and Configure ESLint

Let's install and configure ESLint so we get some nice warnings and errors when we make syntax mistakes in our code. ESLint will also help us enforce coding conventions.
https://eslint.org/

So far I'm not certain with this issue.
The portfolio template provided an eslintrc.js file.
It includes 'extends: ['eslint:recommended', 'plugin:astro/recommended', 'plugin:astro/jsx-a11y-strict'],'


Fix no db prefix

If you use db prefix without this fix you will get empty columns list. Because of this intuiting a field type doesn't work.

Why is it still waiting? Only me is who use prefixes in mysql?

Hi @mgralikowski ,
Apparently not a lot of people use db prefixes in Laravel, yes :-) I totally agree with this change - merged, will be tagged later today with a few more non-breaking changes. It will be version 3.6.6.
Sorry for not giving attention to this sooner. The reason I didn't merge this at the time was that I know that Eloquent used to have an inconsistency / bug in using db prefixes. That's why I never use them myself - after using Laravel for years, I just got used to never using prefixes. I'm still not very happy with the implementation - I would expect $model->getTable() to return the real table name (with the prefix) but hey ho. It won't be a problem for those who use db prefixes in Laravel, I guess.
Anyway, merged. Thank you for the PR.
Cheers!

Prefixes - old habit in case using db for multiple system Laravel + WP for example ;) I agree, they cause some problem with 3rd party libraries (Eloquent is 100% ok) so i am not going to use them in next projects.


Rework policy signing-key flag check

Invoking gittuf's policy commands that require a signing key without the -k flag to specify said signing key does not raise an error.
Currently, this check is performed by setting an attribute on the flag via cobra. Unfortunately, it appears that disabling this requirement for subcommands that do not need a signing key (i.e. list-rules) also disables the flag for subcommands that do need it.
This PR recreates the required flag check in the CheckIfSigningViable function.
A minor note: As this is done in PreRunE, the signing key flag check will run before other flag checks. Run gittuf policy add-rule without any flags before and after this PR change to see what I mean. Unsure if we care about this.

Were you able to build off this branch and test?

trust, rsl, and policy worked for me, and gittuf policy add-key, requires a key, while list-rules passes without needing one

thanks for checking!


Proxy

how to use proxy？

not sure what you're asking here :/

I think he is asking how to use proxy to access youtube in pytube. (eg. how to use socks5 proxy in pytube)
Maybe this link will help http://stackoverflow.com/questions/31777692/python3-requests-with-sock5-proxy


Fix use after free of task in FuturesUnordered when dropped future panics

Fixes https://github.com/rust-lang/futures-rs/issues/2863

Hmm. I see AddressSanitizer also complains about the same leak.
Given that it would complicate CI, and how Vec and VecDeque behave, trying to avoid the risk of potential abort for bad future here may not actually be a worthwhile goal...

I could just ignore this test there? The main thing it tests for is caught by miri.
It feels kind of bad to change this due to testing issues....
TBH if there was a test for hitting the abort case that would probably have issues too since iirc there isn't a good way to test should_abort :(


Variables in fragments

The following GraphQL request does not seem to be supported:
query getChecks($appId: Int!, $owner: String!, $repo:String!, $base: GitObjectID!, $head: GitObjectID!) {
  repository(name: $repo,owner:$owner) {
    base: object(oid: $base) {
      ... checks
    }
    head: object(oid: $head) {
      ... checks
    }
  }
}

fragment checks on Commit {
  checkSuites(first: 1,filterBy:{appId: $appId}) {
    nodes {
      checkRuns(first: 100) {
        nodes {
          name
          status
          conclusion
        }
      }
    }
  }
}

I get two errors: Variable "$appId" is never used in operation "getChecks" (first $appId) and Invalid argument. Expected "Int" but received "Null". (second $appId).
I'm using graphql-ppx 1.0.1 in native OCaml, but I doubt this is relevant to this issue.

Sorry, I didn't realize that this use case was actually documented in https://beta.graphql-ppx.com/docs/fragment#variables-within-fragments.
Following the documentation, I've changed by request into:
fragment checks on Commit @argumentDefinitions(appId: {type: "Int!"}) {
  checkSuites(first: 1,filterBy:{appId: $appId}) {
    nodes {
      checkRuns(first: 100) {
        nodes {
          name
          status
          conclusion
        }
      }
    }
  }
}

query getChecks($appId: Int!, $owner: String!, $repo:String!, $base: GitObjectID!, $head: GitObjectID!) {
  repository(name: $repo,owner:$owner) {
    base: object(oid: $base) {
      ... checks @arguments(appId: $appId)
    }
    head: object(oid: $head) {
      ... checks
    }
  }
}

But I still get the second error (Invalid argument. Expected "Int" but received "Null".). I'm starting to think that this might actually be related to my use of the native version...

Yes the native version doesn't support variables in fragments yet. I'd love to upgrade the ReScript version of the PPX to make it work for both native and ReScript.

How much of the code base is shared and how much is duplicated between Bucklescript and native ReasonML? Is the evolution of Bucklescript + ReasonML toward ReScript going to make it even harder to share code or not?

There are now two ppx-es that share code. We can change the ReScript one to also work on native, we "just" need all Js.* invocations to be replaced with code that works on native (under a -native switch). That's probably a lot less work than updating the current native ppx code.

In my bucklescript code, I have same error: Invalid argument. Expected "Int" but received "Null"
It is normal ?

Hi all.
I am also facing the same issue.
How did you fix this?
I am using graphql ppx version 1.0.0

Hi all.
I am also facing the same issue.
How did you fix this?
I am using graphql ppx version 1.0.0


Comitting README, code, dataset, finalreport

Edited README, uploading code, data, and report

Accidently closed


Regression creating/comparing JSON encoded data

Description
Running my test suite, I realized a bunch of tests doing Data comparisons started failing with Xcode 15. I managed to find an example. It's possible that something simpler would also reproduce, but this is the simplest I was able to get it.
Steps to reproduce
import Foundation
import XCTest

struct Model {
    struct SubModel: Encodable {
        var data: [Int]

        init(count: Int) {
            self.data = []
            self.data.reserveCapacity(count)

            for _ in 0..<count {
                self.data.append(Int.random(in: 0..<99999999))
            }
        }
    }

    internal enum Enum: Int, Encodable {
        case notRequested = 0
        case verified = 1
        case failed = 2

    }

    let submodel: SubModel
    let count: Int
    let result: Enum = .verified

    init(count: Int) {
        self.submodel = .init(count: count)
        self.count = count
    }
}

extension Model: Encodable {
    private enum CodingKeys: String, CodingKey {
        case submodel
        case count
        case result
    }

    func encode(to encoder: Encoder) throws {
        var container = encoder.container(keyedBy: CodingKeys.self)

        try self.submodel.encode(to: encoder)
        try container.encode(self.count, forKey: .count)
        try container.encode(self.result, forKey: .result)
    }
}

let jsonEncoder = JSONEncoder()

extension Encodable {
    var asData: Data {
        get throws {
            return try jsonEncoder.encode(self)
        }
    }
}

private let model = Model(count: 1000000)

final class JSONRegressionTests: XCTestCase {

    func testComparison() throws {
        try XCTAssertEqual(model.asData, model.asData)
    }
}

Expected behavior
Test passes, like it does on Xcode 14.x / iOS 16.
Actual behavior

Environment

Swift compiler version info:

swift-driver version: 1.82.2 Apple Swift version 5.9 (swiftlang-<IP_ADDRESS>.6 clang-15<IP_ADDRESS>)
Target: arm64-apple-macosx13.0

Xcode version info:

Xcode 15.0
Build version 15A5160n

Deployment target: iOS 17.0

Additional context
Weirdly sometimes after a clean build, the test passes, but subsequent runs fail, maybe pointing to some sort of miscompilation?
I can't really tell what the problem is. As you can see on the error though, the actual Data has the same hash and length (this is the error when comparing the values using Nimble instead of XCTest which provides the hash as well):

expected to equal <Data<hash=17221091,length=1364>>, got <Data<hash=17221091,length=1364>>

JSON encoding does not guarantee that the bytes will be exactly equal.  It has never guaranteed this, but some recent performance optimizations in JSONEncoder have made the output more variable than it used to be.  For example, a struct with two Int fields a and b might be encoded as:
{"a":7,"b":15}

or as
{"b": 15, "a": 7,}

Both are perfectly valid and should be treated as equivalent.  But as Data, they are not the same.
If you want to verify JSON encodings, you should use a utility similar to JSONSerialization.jsonObject(with:options:) to break down each JSON document into a general structure and then compare the broken-down version incrementally.

That makes sense 👍🏻  I guess I needed this to ensure consistency:
encoder.outputFormatting = .sortedKeys


Hotkey is hardcoded

Due to B for backpack, I wanted to change the binding to something I wont accidentally hit every 5 seconds when building.
But when changing the key bindings they show as conflicting, and will work for the duration of that session, but after relogging they will no longer work. Changing them via the config file provides the same issue.
This really feels like the key bindings are hard coded to BBOR.
MC : 1.19.2
Forge : 43.2.4
BBOR : 2.5.1 (2.6 provided the same issue)

I'm running into the same issue.  If I change it, the hotkey shows and responds as the new key, but on game restart, while the hotkey still shows the new key, it goes back to using "b" as the actual hotkey.  It also seems to block propogation of that key, as the backpack doesn't still also open.

I'm no expert, but it appears as though you're re-registering the hotkey every time the mod gets loaded (ie, client restart), which is why it's ignoring remappings through client config.
https://github.com/irtimaled/BoundingBoxOutlineReloaded/blob/9b3d975c355cb4087f9f33ff510e9b7e0f808025/src/main/java/com/irtimaled/bbor/client/ClientProxy.java#L17

Can confirm bug. Very irritating.

Bumping issue because it's still a thing and seems to be across versions (i'm seeing it on 1.18.2)


Realtime-img2img

I installed it all. Running function ”demo | realtime-img2img“ with "python main.py --acceleration tensorrt" an error was thrown:
"The config attributes {'skip_prk_steps': True} were passed to LCMScheduler, but are not expected and will be ignored. Please verify your scheduler_config.json configuration file."

And a pop-up window prompts that python cannot find the entrance:

The camera unable to be called in web-UI and there returns the prompt "cannot read properties of undefined (reading 'enumerateDevices')" as I click the "START" buttom:

What did I do wrong? Everything else is normal
My environment:
python=3.10.9
CUDA=11.8
torch use:
pip3 install torch==2.1.0 torchvision==0.16.0 xformers --index-url https://download.pytorch.org/whl/cu118
tensorrt use:
pip install git+https://github.com/cumulo-autumn/StreamDiffusion.git@main#egg=streamdiffusion[tensorrt]
And make sure there is no problem with the "python -m streamdiffusion.tools.install-tensorrt" step.
win11x64
......
Please help me and thanx a lot~

The error message is still there, but I can make it work now:
Enter "edge://flags/#unsafely-treat-insecure-origin-as-secure" in the edge address bar (in chrome just replace "edge" with "chrome"), and search with keywords "Insecure origins treated as secure", then click the "enabled" button. Add addresses in the box below: "http://localhost:7860,http://<IP_ADDRESS>:7860" and restart edge.

The error message is still there, but I can make it work now: Enter "edge://flags/#unsafely-treat-insecure-origin-as-secure" in the edge address bar (in chrome just replace "edge" with "chrome"), and search with keywords "Insecure origins treated as secure", then click the "enabled" button. Add addresses in the box below: "http://localhost:7860,http://<IP_ADDRESS>:7860" and restart edge.

This worked for me on chrome so thank you!

You can also just use localhost:7860 and then you need not make any settings changes.


EC2 instance costs not calculated

If your issue relates to the Discovery Process, please first follow the steps described in the implementation guide Debugging the Discovery Component

Describe the bug
When i add EC2 instances to my diagram it shows costs as $0.
To Reproduce
Steps to reproduce the behavior:

Go to Perspective main screen.
Search for an EC2 instance
Select it in the dropdown
The diagram renders, but costs for the instance are $0

Expected behavior
To see the costs incurred for running these instances.
Screenshots
If applicable, add screenshots to help explain your problem.
Browser (please complete the following information):

Name [e.g. chrome, firefox]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

This is caused by Perspective expecting ARNs in the Cost and Usage Reports. EC2 are logged with resourceId inside CURs, so Perspective does not pick it up.
You can view EC2 related costs in the Cost query builder using the Query by Service and selecting "Elastic Compute Cloud" and seeing the costs associated with EC2 resources

This was fixed in v1.1.4.


[4.0-pre-alpha] Failed to export to Android

Godot version
v4.0.dev.20211004.official [2e8cba0bd]
System information
Windows 11, Vulkan Mobile
Issue description

My export settings, which will do in 3.x:

If I put the keystone path in the export preset, the export still fails.

Steps to reproduce
Try to export to Android.
Minimal reproduction project
No response

At least in 3.3.3 and 3.3.4 the export to android isnt working as well - the generated APKs are not signed, even if all settings correct set. I tried it with 3.2.3 and in this case it worked fine.

At least in 3.3.3 and 3.3.4 the export to android isnt working as well - the generated APKs are not signed, even if all settings correct set. I tried it with 3.2.3 and in this case it worked fine.
The errormessage said

This is unrelated to the issue reported here. This appears to be the same cause as https://github.com/godotengine/godot/issues/18222.

Are you using jdk11?

@autofool jdk8 I suppose.

You need to use jdk11 for Godot4. check here

Upgraded to jdk11, new error

APK can be generated but cannot be installed on mobile phones.

Have you recreated your store and store key with jdk11?

@autofool Yes, I've recreated the keystore file.

This issue could be specific to Windows 11. Have you tried in Windows 10? Unfortunately I don’t have Windows 11 device to probe more into the error.

@floppyhammer Can you check if it works for you with the official alpha templates?
Android export was fine last time I tried it.

@KoBeWi No for v4.0.alpha9.official [fc18891db].

It turns out that this is the 4.0 counterpart of https://github.com/godotengine/godot/issues/58192.

Closing as duplicate of #58192 if it's not version specific.


BUG-Scope issue when assigning to state using lambda

Description
Using the example in the docs for using a lambda expression to assign to state does not work in a subpage.
How to reproduce
# app.py
import taipy as tp
from fruit import fruit_md

pages = {
    "/": "<|navbar|>",
    "fruit": fruit_md,
}

def on_change(state, var_name, var_value):
    print(var_name, var_value)

tp.Gui(pages=pages).run()

# fruit.py
from taipy.gui import Markdown

fruit_list = ["apple", "banana", "cherry"]
selected_fruits = fruit_list[:]

fruit_md = Markdown(
"""
# Select fruit

<|{selected_fruits}|selector|lov={fruit_list}|multiple|>

# assign

<|Select All|button|on_action={lambda s: s.assign("selected_fruits", s.fruit_list)}|> - does not work

<|Clear All|button|on_action={lambda s: s.assign("selected_fruits", [])}|> - does not work

# setattr

<|Select All|button|on_action={lambda s: setattr(s, "selected_fruits", s.fruit_list)}|> - does not work

<|Clear All|button|on_action={lambda s: setattr(s, "selected_fruits", [])}|> - works

# fn

<|Select All|button|on_action=select_all|> - works

<|Clear All|button|on_action=clear_all|> - works
""")

def select_all(state):
    state.selected_fruits = state.fruit_list

def clear_all(state):
    state.selected_fruits = []

Expected behavior
All 6 buttons above should work
Screenshots
When available and relevant, screenshots better help show the problem.
Runtime environment
Please specify relevant indications.

taipy-gui dev branch

I and @FredLL-Avaiga has retested this issue on the current dev branch and it is working as expected. @arcanaxion please retest it and let us know if it is working for you too.

I and @FredLL-Avaiga has retested this issue on the current dev branch and it is working as expected. @arcanaxion please retest it and let us know if it is working for you too.

Yes it all works now, thanks!

Thanks @arcanaxion
I will close the issue then


Fix ordering of VC snapshot setup logic

According to Apple docs, you should call addChild before adding the child VC's view to the parent VC's view. Also, when looping over multiple strategies of varying sizes, there could be issues where the target view controllers view is not laid out again properly in time (we were only forcing layout on the container rootViewController vs the actual target viewController).
Reordering the methods and explicitly forcing layout on both the child and root vc fixed several issues we were having with nested collection views not laying out properly because the ordering of the tests (small to big vs big to small screen size).

Having a hard time coming up with a dummy example/test to reproduce what I'm seeing in my project. Will keep trying!

I take it back, was able to create a unit test that fails. The autoclosure for the matching param was throwing me off. Will update this PR!


bug: Missing content details on locations

Bug Definition
There are som locations which cannot show the details about the relief request.

-- Please add discord contact information
** discord username: @sercannerhan#0543 **

## Bug environment

Describe the environment produces the bug. For example:
afetharita.com

Describe how you are producing the bug step by step

Go to prod
Filter Verified
Search for the id:707477 by zooming in Gaziantep
Click on the location to open the drawer
Find the details.
Only the adresss information is visible and there is no  details about the request.
When you checked the API response, you can find the expected information in additional_notes (acil ısıtıcı kıyafet, battaniye ve eşofman altı lazım 14 have nar ACİL!!!)

Expected Behaviour
When a users clicks on the location to see the detail on relief requests, the detail abou the request should be visible with the address information (not only the address information).
Screen shots

If possible, add screenshots to describe your bug.

Desktop Information

Operating System: [for example iOS]
Browser [for example, safari]
Version [for example 22]

Mobile Phone Information

Devıce: [for example iPhone6]
Operating System (with the version): [for example iOS8.1]
Version [for example default browser, safari]
Browser Version [for example 22]

Additional Context
Add any other context about the bug here

Fixed


Create a workflow diagram

We need to create a workflow diagram for this project to make it easy for  us and new contributors to understand how everything works.

Would love to take this!

@nabuskey just to clarify - by a workflow diagram, do you mean. a flowchart for how the various commands work e.g create and the -p package-dir flag? or high level arch diagram of idpbuilder?

Thank you @bnjoroge1 for taking this on.
I believe @nabuskey 's intention is to develop something similar to what we have for the AWS reference implementation here.
The installation workflows should show how the core packages are configured, how keycloak is set up, and how the pulling of local and remote packages is taken care of. The flow should help the new contributors follow the execution path and gain better understanding of how the different pieces in the idpbuilder could work together.

Hey Nima - thanks for the comment and apologies for taking too long to get a PR up, but I just did. Would love a review/feedback on anything I should include in the diagram. Here's the PR: https://github.com/cnoe-io/idpbuilder/pull/347
cc @nabuskey @nimakaviani


Make BUILD_NAME globally configurable

Makes it easier to distinguish between official and custom builds by allowing developers to customize BUILD_NAME env var.
I can make it to default to custom_build over official if you like. Of course, nothing prevents someone to use official name, but this will decrease the likelihood of someone compiling the editor and export templates as official, otherwise the only way to distinguish such builds is by using checksums.
Also note that BUILD_NAME can be fetched at run-time via script with Engine.get_version_info().

Looks good! Yeah I think it would make sense to make it default to custom_build, I can set official in my own config.sh.

Changed to custom_build by default.

Thanks!


🚀 [Feature] : Better README.md

Is your feature request related to a problem? Please describe.
The current README.md lacks detailed information, making it difficult for new users to understand the project's purpose, how to set it up, and how to contribute. This can be frustrating and may hinder adoption and collaboration.
Describe the solution you'd like
I would like a comprehensive README.md that includes the following sections:

Project Overview: A brief description of the project and its goals.
Features: A list of key features and functionalities.
Installation: Step-by-step instructions on how to set up the project locally.
Usage: Examples and explanations of how to use the project.
Contributing: Guidelines for contributing to the project.
License: Information about the project's license.
Contact: How to get in touch with the project maintainers.

Describe alternatives you've considered
An alternative could be to create a separate documentation website for detailed guides and tutorials, but enhancing the README.md is a more immediate and accessible solution.
Additional context
Including badges for build status, dependencies, and other relevant information could also enhance the README.md. Screenshots or additional visual aids may be helpful to illustrate key points.
If you want to speed up the process of this issue, please send 🚀 as a reaction.

Please add README following sections and make it better readibility as well.
I took from langx/website repo https://github.com/langx/website/blob/main/README.md?plain=1
Can you please update this readme.md as well like the langx/website readme.md

## Table of Contents
- [Getting Started](#getting-started)
- [Contributing](#contributing)
- Stats ...
  - Stargazers
  - Contributors
- [License](#license)

## Getting started

To clone this project, simply run the following command:

# clone this repo
git clone  https://github.com/langx/website

## Contributing

We welcome contributions from the community! If you'd like to contribute to LangX, please fork our repository and submit a pull request. We'll review your changes and merge them if they meet our guidelines. Thank you for helping to make LangX even better!

We'll review your changes and merge them if they meet our guidelines. Thank you for helping to make LangX even better!

LangX is an open source project and we welcome contributions from the community. If you're interested in contributing, please check out our GitHub repository for more information.

## Versioning

LangX uses [Semantic Versioning](https://semver.org/) for versioning. For the versions available, see the [tags on this repository](https://github.com/langx/website/releases).

## Stats

### Stargazers

[![Stargazers over time](https://starchart.cc/langx/website.svg?variant=adaptive)](https://starchart.cc/langx/website)

### Contributors

[![GitHub Contributor Over Time](https://contributor-overtime-api.git-contributor.com/contributors-svg?chart=contributorOverTime&repo=langx/token-website)](https://git-contributor.com?chart=contributorOverTime&repo=langx/token-website)

[![GitHub Contributors Image](https://contrib.rocks/image?repo=langx/token-website)](https://github.com/langx/token-website/graphs/contributors)

## License

LangX is released under the [MIT License](./LICENSE). If you use this project, please include the license file in your distribution.

If you want speed up process of this issue, please send 🚀 as a reaction.

Will do!


⚠ Unifi Controller has degraded performance

In dceda7a, Unifi Controller ($UNI_ENDPOINT) experienced degraded performance:

HTTP code: 200
Response time: 380 ms

Resolved: Unifi Controller performance has improved in b8fa409.


[Docs] - Added status command files

Signed-off-by: databender<EMAIL_ADDRESS>Description
This PR fixes #2938
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Thanks for tackling this one, @umairnsr87

@umairnsr87 Could you force ammend a signoff here?
Check Here for Instructions, https://github.com/layer5io/meshery/pull/3086/checks?check_run_id=2716683583

@adithyaakrishna  @leecalcote  Can you please review this?

@adithyaakrishna I have made suggested changed. Thanks +1:

@umairnsr87 merge conflict - https://github.com/layer5io/meshery/pull/3086/conflicts


TF2.0beta distribute.MirroredStrategy hangs causing 100% GPU

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

I run the code provided in the tutorial https://www.tensorflow.org/beta/tutorials/distribute/keras

== check python ===================================================
python version: 3.6.7
python branch:
python build version: ('default', 'Feb 28 2019 09:07:38')
python compiler version: GCC 7.3.0
python implementation: CPython
== check os platform ===============================================
os: Linux
os kernel version: #1 SMP Thu Nov 29 14:49:43 UTC 2018
os release version: 3.10.0-957.1.3.el7.x86_64
os platform: Linux-3.10.0-957.1.3.el7.x86_64-x86_64-with-centos-7.6.1810-Core
linux distribution: ('CentOS Linux', '7.6.1810', 'Core')
linux os distribution: ('centos', '7.6.1810', 'Core')
mac version: ('', ('', '', ''), '')
uname: uname_result(system='Linux', node='monod33.mbb.ki.se', release='3.10.0-957.1.3.el7.x86_64', version='#1 SMP Thu Nov 29 14:49:43 UTC 2018', machine='x86_64', processor='x86_64')
architecture: ('64bit', '')
machine: x86_64
== are we in docker =============================================
No
== compiler =====================================================
c++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36)
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
== check pips ===================================================
numpy                    1.16.4
protobuf                 3.8.0
tensorflow-datasets      1.0.2
tensorflow-gpu           2.0.0b1
tensorflow-metadata      0.13.0
== check for virtualenv =========================================
False

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
No
TensorFlow installed from (source or binary):
binary (pip)
TensorFlow version (use command below):
Python version:
2.0.0b1
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
cuda 10.0/cuDNN 7
GPU model and memory:
4x Nvidia 1080Ti 11GB (MSI GeForce GTX)

Describe the current behavior

Training on one GPUs works fine
All GPUs are recognized
When I select multiple GPUs example: strategy = tf.distribute.MirroredStrategy(devices=["/device:GPU:0","/device:GPU:1"]) the processing hang and the GPUs are stuck at 100%

code output hangs at:
2019-06-19 09:03:44.971843: W tensorflow/compiler/jit/mark_for_compilation_pass.cc:1483] (One-time warning): Not using XLA:CPU for cluster because envvar TF_XLA_FLAGS=--tf_xla_cpu_global_jit was not set.  If you want XLA:CPU, either set that envvar, or use experimental_jit_scope to enable XLA:CPU.  To confirm that XLA is active, pass --vmodule=xla_compilation_cache=1 (as a proper command-line flag, not via TF_XLA_FLAGS) or set the envvar XLA_FLAGS=--xla_hlo_profile.
2019-06-19 09:03:44.992837: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcublas.so.10.0
2019-06-19 09:03:46.143152: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcudnn.so.7

nvidia-smi output
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 410.93       Driver Version: 410.93       CUDA Version: 10.0     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 108...  Off  | 00000000:1A:00.0 Off |                  N/A |
| 29%   38C    P2    73W / 250W |  10883MiB / 11178MiB |    100%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 108...  Off  | 00000000:1B:00.0 Off |                  N/A |
| 29%   35C    P2    73W / 250W |  10883MiB / 11178MiB |    100%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce GTX 108...  Off  | 00000000:88:00.0 Off |                  N/A |
| 29%   28C    P8     8W / 250W |    157MiB / 11178MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   3  GeForce GTX 108...  Off  | 00000000:89:00.0 Off |                  N/A |
| 29%   26C    P8     8W / 250W |    157MiB / 11178MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory ||  GPU       PID   Type   Process name                             Usage      |
|=============================================================================||    0    195955      C   ...processing/anaconda3/envs/tf/bin/python 10873MiB |
|    1    195955      C   ...processing/anaconda3/envs/tf/bin/python 10873MiB ||    2    195955      C   ...processing/anaconda3/envs/tf/bin/python   147MiB |
|    3    195955      C   ...processing/anaconda3/envs/tf/bin/python   147MiB |+-----------------------------------------------------------------------------+
Describe the expected behavior
Run the training in parallel
Code to reproduce the issue
Code provided in the tutorial: https://www.tensorflow.org/beta/tutorials/distribute/keras for TF2.0 Beta
Other info / logs
output when running the code
2019-06-19 09:03:37.964465: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1640] Found device 0 with properties:
name: GeForce GTX 1080 Ti major: 6 minor: 1 memoryClockRate(GHz): 1.62
pciBusID: 0000:1a:00.0
2019-06-19 09:03:37.967415: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1640] Found device 1 with properties:
name: GeForce GTX 1080 Ti major: 6 minor: 1 memoryClockRate(GHz): 1.62
pciBusID: 0000:1b:00.0
2019-06-19 09:03:37.970349: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1640] Found device 2 with properties:
name: GeForce GTX 1080 Ti major: 6 minor: 1 memoryClockRate(GHz): 1.62
pciBusID: 0000:88:00.0
2019-06-19 09:03:37.973263: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1640] Found device 3 with properties:
name: GeForce GTX 1080 Ti major: 6 minor: 1 memoryClockRate(GHz): 1.62
pciBusID: 0000:89:00.0
2019-06-19 09:03:37.973368: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcudart.so.10.0
2019-06-19 09:03:37.973414: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcublas.so.10.0
2019-06-19 09:03:37.973455: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcufft.so.10.0
2019-06-19 09:03:37.973538: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcurand.so.10.0
2019-06-19 09:03:37.973578: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcusolver.so.10.0
2019-06-19 09:03:37.973618: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcusparse.so.10.0
2019-06-19 09:03:37.973679: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcudnn.so.7
2019-06-19 09:03:37.995237: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1763] Adding visible gpu devices: 0, 1, 2, 3
2019-06-19 09:03:37.998940: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1640] Found device 0 with properties:
name: GeForce GTX 1080 Ti major: 6 minor: 1 memoryClockRate(GHz): 1.62
pciBusID: 0000:1a:00.0
2019-06-19 09:03:38.001616: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1640] Found device 1 with properties:
name: GeForce GTX 1080 Ti major: 6 minor: 1 memoryClockRate(GHz): 1.62
pciBusID: 0000:1b:00.0
2019-06-19 09:03:38.004343: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1640] Found device 2 with properties:
name: GeForce GTX 1080 Ti major: 6 minor: 1 memoryClockRate(GHz): 1.62
pciBusID: 0000:88:00.0
2019-06-19 09:03:38.007065: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1640] Found device 3 with properties:
name: GeForce GTX 1080 Ti major: 6 minor: 1 memoryClockRate(GHz): 1.62
pciBusID: 0000:89:00.0
2019-06-19 09:03:38.007148: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcudart.so.10.0
2019-06-19 09:03:38.007219: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcublas.so.10.0
2019-06-19 09:03:38.007257: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcufft.so.10.0
2019-06-19 09:03:38.007293: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcurand.so.10.0
2019-06-19 09:03:38.007356: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcusolver.so.10.0
2019-06-19 09:03:38.007393: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcusparse.so.10.0
2019-06-19 09:03:38.007448: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcudnn.so.7
2019-06-19 09:03:38.027019: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1763] Adding visible gpu devices: 0, 1, 2, 3
2019-06-19 09:03:38.027513: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1181] Device interconnect StreamExecutor with strength 1 edge matrix:
2019-06-19 09:03:38.027550: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1187]      0 1 2 3
2019-06-19 09:03:38.027578: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1200] 0:   N Y Y Y
2019-06-19 09:03:38.027603: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1200] 1:   Y N Y Y
2019-06-19 09:03:38.027627: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1200] 2:   Y Y N Y
2019-06-19 09:03:38.027651: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1200] 3:   Y Y Y N
2019-06-19 09:03:38.041771: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1326] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 10470 MB memory) -> physical GPU (device: 0, name: GeForce G$X 1080 Ti, pci bus id: 0000:1a:00.0, compute capability: 6.1)
2019-06-19 09:03:38.044220: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1326] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:1 with 10470 MB memory) -> physical GPU (device: 1, name: GeForce G$X 1080 Ti, pci bus id: 0000:1b:00.0, compute capability: 6.1)
2019-06-19 09:03:38.046649: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1326] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:2 with 10470 MB memory) -> physical GPU (device: 2, name: GeForce G$X 1080 Ti, pci bus id: 0000:88:00.0, compute capability: 6.1)
2019-06-19 09:03:38.049078: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1326] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:3 with 10470 MB memory) -> physical GPU (device: 3, name: GeForce G$X 1080 Ti, pci bus id: 0000:89:00.0, compute capability: 6.1)
2019-06-19 09:03:38.287085: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1640] Found device 0 with properties:
name: GeForce GTX 1080 Ti major: 6 minor: 1 memoryClockRate(GHz): 1.62
pciBusID: 0000:1a:00.0
2019-06-19 09:03:38.288567: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1640] Found device 1 with properties:
name: GeForce GTX 1080 Ti major: 6 minor: 1 memoryClockRate(GHz): 1.62
pciBusID: 0000:1b:00.0
2019-06-19 09:03:38.290048: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1640] Found device 2 with properties:
name: GeForce GTX 1080 Ti major: 6 minor: 1 memoryClockRate(GHz): 1.62
pciBusID: 0000:88:00.0
2019-06-19 09:03:38.291505: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1640] Found device 3 with properties:
name: GeForce GTX 1080 Ti major: 6 minor: 1 memoryClockRate(GHz): 1.62
pciBusID: 0000:89:00.0
2019-06-19 09:03:38.291560: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcudart.so.10.0
2019-06-19 09:03:38.291573: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcublas.so.10.0
2019-06-19 09:03:38.291586: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcufft.so.10.0
2019-06-19 09:03:38.291599: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcurand.so.10.0
2019-06-19 09:03:38.291611: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcusolver.so.10.0
2019-06-19 09:03:38.291623: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcusparse.so.10.0
2019-06-19 09:03:38.291635: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcudnn.so.7
2019-06-19 09:03:38.302880: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1763] Adding visible gpu devices: 0, 1, 2, 3
2019-06-19 09:03:38.303091: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1181] Device interconnect StreamExecutor with strength 1 edge matrix:
2019-06-19 09:03:38.303106: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1187]      0 1 2 3
2019-06-19 09:03:38.303116: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1200] 0:   N Y Y Y
2019-06-19 09:03:38.303126: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1200] 1:   Y N Y Y
2019-06-19 09:03:38.303134: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1200] 2:   Y Y N Y
2019-06-19 09:03:38.303143: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1200] 3:   Y Y Y N
2019-06-19 09:03:38.314925: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1326] Created TensorFlow device (/device:GPU:0 with 10470 MB memory) -> physical GPU (device: 0, name: GeForce GTX 1080 Ti, pci bus id: 0000:1a:
00.0, compute capability: 6.1)
2019-06-19 09:03:38.317831: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1326] Created TensorFlow device (/device:GPU:1 with 10470 MB memory) -> physical GPU (device: 1, name: GeForce GTX 1080 Ti, pci bus id: 0000:1b:
00.0, compute capability: 6.1)
2019-06-19 09:03:38.320690: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1326] Created TensorFlow device (/device:GPU:2 with 10470 MB memory) -> physical GPU (device: 2, name: GeForce GTX 1080 Ti, pci bus id: 0000:88:
00.0, compute capability: 6.1)
2019-06-19 09:03:38.323571: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1326] Created TensorFlow device (/device:GPU:3 with 10470 MB memory) -> physical GPU (device: 3, name: GeForce GTX 1080 Ti, pci bus id: 0000:89:
00.0, compute capability: 6.1)
Train on None steps
Epoch 1/12
2019-06-19 09:03:44.971843: W tensorflow/compiler/jit/mark_for_compilation_pass.cc:1483] (One-time warning): Not using XLA:CPU for cluster because envvar TF_XLA_FLAGS=--tf_xla_cpu_global_jit was not set.  If you want XLA:CP
U, either set that envvar, or use experimental_jit_scope to enable XLA:CPU.  To confirm that XLA is active, pass --vmodule=xla_compilation_cache=1 (as a proper command-line flag, not via TF_XLA_FLAGS) or set the envvar XLA_
FLAGS=--xla_hlo_profile.
2019-06-19 09:03:44.992837: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcublas.so.10.0
2019-06-19 09:03:46.143152: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcudnn.so.7

Thanks for the help!

Hi
I forgot to mention that the previous code was run using ipython. Today I run the same code with a jupyter notebook and as standalone script from shell and everything worked fine. I guess the issue has to do with ipython.
Thanks for the help!


Spline in 3D can not be differentiated due to an AttributeError

I stumbled into the same issue as described here: Stackoverflow.
At the moment I try to circumvent this error by using the workaround described there.
Reproducing code example:
import numpy as np
from scipy import interpolate

points = np.random.rand(10,2) * 10

(tck, u), fp, ier, msg = interpolate.splprep(points.T, s=0, k=3, full_output=True)

# Calculate derivative
spline_der = interpolate.splder(tck, n=1)

Error message:
Traceback (most recent call last):
  File "/snap/pycharm-community/132/helpers/pydev/pydevd.py", line 1758, in <module>
    main()
  File "/snap/pycharm-community/132/helpers/pydev/pydevd.py", line 1752, in main
    globals = debugger.run(setup['file'], None, None, is_module)
  File "/snap/pycharm-community/132/helpers/pydev/pydevd.py", line 1147, in run
    pydev_imports.execfile(file, globals, locals)  # execute the script
  File "/snap/pycharm-community/132/helpers/pydev/_pydev_imps/_pydev_execfile.py", line 18, in execfile
    exec(compile(contents+"\n", file, 'exec'), glob, loc)
  File "/home/clemens/VCS/gpstracksimulator/test.py", line 19, in <module>
    spline_der = interpolate.splder(tck, n=1)
  File "/home/clemens/VCS/PythonVenv/GPSTrackSimulator/lib/python3.7/site-packages/scipy/interpolate/fitpack.py", line 657, in splder
    return _impl.splder(tck, n)
  File "/home/clemens/VCS/PythonVenv/GPSTrackSimulator/lib/python3.7/site-packages/scipy/interpolate/_fitpack_impl.py", line 1206, in splder
    sh = (slice(None),) + ((None,)*len(c.shape[1:]))
AttributeError: 'list' object has no attribute 'shape'

Scipy/Numpy/Python version information:
Scipy: 1.3.0
Numpy: 1.16.4
Python: 3.7

Prefer using make_interp_spline / BSpline objects in new code, these should work fine with n-D coefficient arrays.

Thank you for the comment. I tried to use BSpline before (but in a probably wrong way by trying to generate it from the output of splprep), but there I also stumble into quite strange errors (or is the output of splprep not compatible to the BSpline class?
import numpy as np
from scipy import interpolate

points = np.concatenate((np.linspace(0.0, 5.0, 20, endpoint=True).reshape(20, 1), np.full((20, 1), 5.0) + np.random.rand(20, 1)), axis=1)

(tck, u), fp, ier, msg = interpolate.splprep(points.T, s=0, k=3, full_output=True)

t = np.array(tck[0])
c = np.array(tck[1])
k = tck[2]

bspline = interpolate.BSpline(t, c, k)

Error message:
Traceback (most recent call last):
  File "/snap/pycharm-community/132/helpers/pydev/pydevd.py", line 1758, in <module>
    main()
  File "/snap/pycharm-community/132/helpers/pydev/pydevd.py", line 1752, in main
    globals = debugger.run(setup['file'], None, None, is_module)
  File "/snap/pycharm-community/132/helpers/pydev/pydevd.py", line 1147, in run
    pydev_imports.execfile(file, globals, locals)  # execute the script
  File "/snap/pycharm-community/132/helpers/pydev/_pydev_imps/_pydev_execfile.py", line 18, in execfile
    exec(compile(contents+"\n", file, 'exec'), glob, loc)
  File "/home/clemens/VCS/gpstracksimulator/test.py", line 17, in <module>
    bspline = interpolate.BSpline(t, c, k)
  File "/home/clemens/VCS/PythonVenv/GPSTrackSimulator/lib/python3.7/site-packages/scipy/interpolate/_bsplines.py", line 223, in __init__
    raise ValueError("Knots, coefficients and degree are inconsistent.")
ValueError: Knots, coefficients and degree are inconsistent.

I will try using make_interp_spline.

The main issue here is that indeed, splprep returns the coefficients as a list of arrays, and this is inconsistent with splder. As noted at SO, splev can evaluate derivatives, and splev is consistent with both splrep and splprep. (please file a bug if you find a counterexample).
This is a known wart, and it's frozen by backwards compatibility.

An alternative is to avoid splprep(..., s=0) entirely and use make_interp_spline. Here's an example of replicating the splprep outputs. First let's make sense out of the splprep output:
# start with the OP example
import numpy as np
from scipy import interpolate

points = np.random.rand(10,2) * 10

(tck, u), fp, ier, msg = interpolate.splprep(points.T, s=0, k=3, full_output=True)

# check the meaning of the `u` array: evaluation of the spline at `u`
# gives back the original points (up to a list/transpose)

xy = interpolate.splev(u, tck)
xy = np.asarray(xy)
np.allclose(xy.T, points)

Next, let's replicate it without splprep.  First, build the u array: the curve is represented parametrically, and u is essentially an approximation for the arc length. Other parametrizations are possible, but here let's stick to what splprep does. Translating the pseudocode from the splprep doc page,
vv = np.sum((points[1:, :] - points[:-1, :])**2, axis=1)
vv = np.sqrt(vv).cumsum()
vv/= vv[-1]
vv = np.r_[0, vv]

# check:
np.allclose(u, vv)

Now, interpolate along the parametric curve: points vs vv:
spl = interpolate.make_interp_spline(vv, points)

# check spl.t vs knots from splPrep
spl.t - tck[0]

The result, spl, is a BSpline object which you can evaluate, differentiate etc in a usual way:
np.allclose(points, spl(vv))

# differentiate
spl_derivative = spl.derivative(vv)

Finally, since this is confusing and does show up every now and then, some explanation could in principle be added to e.g. scipy.interpolate tutorial (https://docs.scipy.org/doc/scipy/reference/tutorial/interpolate.html). Help is wanted and appreciated. Perspective of someone who is relatively new to it would be especially helpful.

Since this is an API wart which is not going to be fixed, I'm going to close the issue. Thanks for reporting it @q-wertz


Show Avatar and Consistent Terminology in Dispute Close modal

This is the current dispute close modal:

In the Discussion tab, the Vendor is called 'Vendor', but we then call them the 'Seller' when determining the split of funds. It's a possible stumbling block for users, so it should be changed to Vendor. To make it even easier, we should show the avatar of the Buyer and Vendor.

Yes avatars are extremely helpful here. Moderator is not going to easily remember who is who.


Compose version Unknown + Minor Typo

Current DSM version: 6.2.3
Current Docker version: 18.09.8
Current Docker Compose version: 1.24.0
Target Docker version: 19.03.11
Target Docker Compose version: Unknown
Step 1 from 6: Stopping Docker service
pkgctl-Docker stoped.

Should there be a Docker Compose version displayed, rather than "Unknown"?
Also, "stopped" is spelt incorrectly :p

Strange, the script should indeed detect the latest compose version automatically. Can you try running below command from your Synology command line? It should return '1.26.0'.
curl -s "https://github.com/docker/compose/tags" | egrep "a href=\"/docker/compose/releases/tag/[0-9]+.[0-9]+.[0-9]+\"" | head -1 | cut -c 45- | sed "s/\">//g"

The message pkgctl-Docker stoped. is generated by synoservicectl, so unfortunately not a message I can change myself.

Yep, it returned:
1.26.0
Haha, that makes the typo even funnier :D

My guess is that the web scraping call sometimes times out, perhaps GitHub has some kind of rate limiting in place. I encountered a similar issue in another repository. My suggestion is to include a default value for the Docker engine and Docker Compose binary to revert back to in case curl fails.


Updated product name for left nav

@synchrophoto Hi Kirk, That should do the trick — sorry for the confusion; we lose track of who-knows what about our idiosyncratic docs system.


Feature/arangosearch-maintenance-rework

Scope & Purpose
(Please describe the changes in this PR for reviewers - mandatory)

[x] :hankey: Bugfix (requires CHANGELOG entry)
[ ] :pizza: New feature (requires CHANGELOG entry, feature documentation and release notes)
[x] :fire: Performance improvement
[x] :hammer: Refactoring/simplification
[ ] :book: CHANGELOG entry made

Backports:

[ ] No backports required
[ ] Backports required for: (Please specify versions and link PRs)

Related Information
(Please reference tickets / specification / other PRs etc)

[ ] Docs PR:
[ ] Enterprise PR:
[ ] GitHub issue / Jira ticket number:
[ ] Design document:

Testing & Verification
(Please pick either of the following options)

[ ] This change is a trivial rework / code cleanup without any test coverage.
[ ] The behavior in this PR was manually tested
[ ] This change is already covered by existing tests, such as (please describe tests).
[ ] This PR adds tests that were used to verify all changes:

[ ] Added new C++ Unit tests
[ ] Added new integration tests (e.g. in shell_server / shell_server_aql)
[ ] Added new resilience tests (only if the feature is impacted by failovers)

[ ] There are tests in an external testing repository:
[ ] I ensured this code runs with ASan / TSan or other static verification tools

Link to Jenkins PR run:
Documentation

All new features should be accompanied by corresponding documentation.
Bugs and features should furthermore be documented in the CHANGELOG so that
support, end users, and other developers have a concise overview.

[ ] Added entry to Release Notes
[ ] Added a new section in the Manual
[ ] Added a new section in the HTTP API
[ ] Added Swagger examples for the HTTP API
[ ] Updated license information in LICENSES-OTHER-COMPONENTS.md for 3rd party libraries

External contributors / CLA Note
Please note that for legal reasons we require you to sign the Contributor Agreement
before we can accept your pull requests.

http://jenkins.arangodb.biz:8080/job/arangodb-matrix-pr-linux/14451/

http://jenkins.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/12941/

http://jenkins.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/12942/

mac build
http://jenkins01.arangodb.biz:8080/job/arangodb-matrix-pr-mac-onlycatch/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/12959/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/12961/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/12963/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/12966/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/12971/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/


[release-2.30.0][BEAM-12390] clickhouse test fails when test resource can't be read b…

…y others permission
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Java PreCommit

R: @chamikaramj

LGTM


remote error: tls: bad certificate

Description
Observed Behavior:
On a new EKS cluster (without anything previously installed), we're "tls: bad certificate" when trying to register a provisioner...which breaks our scale out. :(
Karpenter: v0.27.6
EKS: v1.25.12-eks-2d98532
ArgoCD: v2.8.3+77556d9
Sample logs:
$ kubectl logs karpenter-provisioners-5cd99796cf-lrnbs -f
{"level":"info","ts":1695796080.7865567,"logger":"fallback","caller":"injection/injection.go:63","msg":"Starting informers..."}
2023/09/27 06:28:03 Registering 2 clients
2023/09/27 06:28:03 Registering 2 informer factories
2023/09/27 06:28:03 Registering 3 informers
2023/09/27 06:28:03 Registering 5 controllers
{"level":"INFO","time":"2023-09-27T06:28:03.864Z","logger":"controller","message":"Starting server","commit":"5a2fe84-dirty","path":"/metrics","kind":"metrics","addr":"[::]:8080"}
{"level":"INFO","time":"2023-09-27T06:28:03.867Z","logger":"controller","message":"Starting server","commit":"5a2fe84-dirty","kind":"health probe","addr":"[::]:8081"}
I0927 06:28:03.970155       1 leaderelection.go:248] attempting to acquire leader lease infra/karpenter-leader-election...
{"level":"INFO","time":"2023-09-27T06:28:04.009Z","logger":"controller","message":"Starting informers...","commit":"5a2fe84-dirty"}
2023/09/27 06:28:05 http: TLS handshake error from <IP_ADDRESS>:50520: remote error: tls: bad certificate
...
I've x-posted this here, as possibly related/identical: https://github.com/knative/pkg/issues/2560#issuecomment-1736787511
Expected Behavior:
no errors :)
Reproduction Steps (Please include YAML):
mostly stock helm chart (v0.27.0), with the following overrides (some details redacted here):
logLevel: info
logEncoding: json

revisionHistoryLimit: 3

controller:
  image:
    repository: {{ include "ecrPrefix" . }}/mirror/public.ecr.aws/karpenter/controller
    tag: v0.27.6
    digest: sha256:21848a7d84ad33a02d930ad1c233fe7403920507c9e0681c9e7780dc9c34fca4

  resources:
    requests:
      cpu: 100m
      memory: 300Mi

  env:
    # needed to call AWS pricing api
    - name: HTTP_PROXY
      value: http://squid.infra:3128
    - name: HTTPS_PROXY
      value: http://squid.infra:3128
    - name: NO_PROXY
      value: sqs.{{ .Values.context.aws_region }}.amazonaws.com,eks.{{ .Values.context.aws_region }}.amazonaws.com,sts.{{ .Values.context.aws_region }}.amazonaws.com,ec2.{{ .Values.context.aws_region }}.amazonaws.com,<IP_ADDRESS>/8,<IP_ADDRESS>/12,<IP_ADDRESS>/16

settings:
  aws:
    clusterName: {{ .Values.context.eks_cluster_name }}
    defaultInstanceProfile: {{ .Values.context.eks_cluster_name }}-node-karpenter
    interruptionQueueName: karpenter-{{ .Values.context.eks_cluster_name }}-instance-interruption
  tags:
    Terraformed: false
    KarpenterManaged: true
  batchMaxDuration: "120s"
  batchIdleDuration: "30s"

extraVolumeMounts:
  - name: aws-iam-token
    mountPath: /var/run/secrets/eks.amazonaws.com/serviceaccount
    readOnly: true

extraVolumes:
  - name: aws-iam-token
    projected:
      defaultMode: 420
      sources:
      - serviceAccountToken:
          audience: sts.amazonaws.com
          expirationSeconds: 86400
          path: token

replicas: 2

serviceAccount:
  name: karpenter-{{ .Values.context.slice_name }}
  annotations:
    eks.amazonaws.com/role-arn: {{ include "awsRoleARNPrefix" . }}/karpenter-{{ .Values.context.slice_name }}

dnsPolicy: ClusterFirst

tolerations:
  - key: "bootstrapper"
    operator: "Exists"

podAnnotations:
  ad.datadoghq.com/controller.check_names: '["openmetrics"]'
  ad.datadoghq.com/controller.init_configs: '[{}]'
  # https://docs.datadoghq.com/agent/guide/template_variables/
  ad.datadoghq.com/controller.instances: '[{ "openmetrics_endpoint":"http://%%host%%:8080/metrics","namespace":"infra","metrics":["^karpenter.*"] }]'
  ad.datadoghq.com/webhook.check_names: '["openmetrics"]'
  ad.datadoghq.com/webhook.init_configs: '[{}]'
  # https://docs.datadoghq.com/agent/guide/template_variables/
  ad.datadoghq.com/webhook.instances: '[{ "openmetrics_endpoint":"http://%%host%%:8080/metrics","namespace":"infra","metrics":["^karpenter.*"] }]'

Versions:

Chart Version: v0.27.0
Karpenter Version: v0.27.6
Kubernetes Version (kubectl version): v1.25.12-eks-2d98532

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

We're using ArgoCD to install the karpenter helm chart....so our very ugly workaround is:

disable ArgoCD "auto-sync" for karpenter
delete all validating and mutating k8s webhooks
manually apply the desired Provisioner to the cluster (kubectl -f foo.yaml apply)
re-enable ArgoCD "auto-sync" for karpenter
observe karpenter restores the deleted k8s webhooks
rolling restart of the karpenter nodes (kubectl rollout restart deployment karpenter)

This allows us to get a Provisioner into the cluster (by skipping any validation), so the karpenter controller can build out nodes.
NOTE: any edits/updates of the Provisioner fail -- due the the same error: http: TLS handshake error from <IP_ADDRESS>:50520: remote error: tls: bad certificate

I'm going to close this as a duplicate of https://github.com/aws/karpenter/issues/2902, we're working on removing the webhooks entirely which should resolve this.


updated offset calculation, reduce factorial part. handle full scroll…

Hi please check the changes that I've made. I've found the issue with wrong offset calculation related to fraction part. And also layout behavior was extended with ability to scroll scrollview to top without hide floating panel.

I've found the issue with wrong offset calculation related to fraction part.

Sounds great! I will add some comments later.

And also layout behavior was extended with ability to scroll scrollview to top without hide floating panel.

Could you please tell me more detail?

hi sure. we want to have an ability to scroll scrollview to top and only after that hide floating panel. It's when we trying to resolve recognizer conflicts. I've added the new option that give ability scroll to top without issue until we reach top most position.

hi sure. we want to have an ability to scroll scrollview to top and only after that hide floating panel. It's when we trying to resolve recognizer conflicts. I've added the new option that give ability scroll to top without issue until we reach top most position.

I'm sorry I'm still not able to understand the API's effect and use case. I might need to know about  "full" scroll-to-top. I tried to use supportFullScrollToTop API as below, but I didn't know the change of a panel behavior with the API.
class FUllScrollToTopLayout: FloatingPanelLayout {
    var supportedPositions: Set<FloatingPanelPosition> {
        return [.full, .hidden]
    }
    var initialPosition: FloatingPanelPosition {
        return .full
    }

    func insetFor(position: FloatingPanelPosition) -> CGFloat? {
        return FloatingPanelDefaultLayout().insetFor(position: position)
    }

    func supportFullScrollToTop() -> Bool {
        return true
    }
}

hi ))
Ok, here I'm trying to prevent close panel until the scroll position will be on top. In our case we found some incorrect behavior with recognizers, when you have a long feed and scroll it to top. in 50% of cases user close the panel, instead of scrolling top. This key: supportFullScrollToTop prevent this behavior until we do not scroll to top. the default behavior in extension does not change the main behavior. You can only set it to true if you will face with this kind of issue.

In our case we found some incorrect behavior with recognizers, when you have a long feed and scroll it to top. in 50% of cases user close the panel, instead of scrolling top.

I got it. It should be resolved. I suppose that the expect behavior is close to scroll handling of Sheet modal on iOS 13. Is my understanding correct?
And now I'v recognized the lib's scroll handling isn't working well on the full-only layout, but unfotunatelly I haven't be able to feel the effect of supportFullScrollToTop.

Could you please split supportFullScrollToTop feature from the PR?
Because I would like to merge your fix of offset calculation at first and then discuss and apply the new feature on a new PR.

Could you please split supportFullScrollToTop feature from the PR?
Because I would like to merge your fix of offset calculation at first and then discuss and apply the new feature on a new PR.

probably would be better to not split the PR, I've send you an video how it works without those changes.

please check

@dmytrofrolov1
Thank you for your commits! I so appreciate your PR and our discussion. Unfortunately you added some additional 4 spaces line, but I will take care of them later.


There's no script download-able or inside the page

"The following script exports the necessary information of the default owner ("UntrustedGuardian") on a host that is configured using local mode."
There's no script download-able or inside the page

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

ID: 3e14cc0c-919d-f378-935e-c078d07e339b
Version Independent ID: b13b9af5-9703-75d4-23a0-128f88da8413
Content: Migrating local VM owner certificates for VMs with vTPM
Content Source: virtualization/community/team-blog/2017/20171214-migrating-local-vm-owner-certificates-for-vms-with-vtpm.md
Product: powershell
GitHub Login: @mattbriggs
Microsoft Alias: mabrigg

Please remove me from this email list I have tried several times to get off
this email. My Son set this account up and now he doesn't remember the
password. I'm so tired of getting upwards of 30 emails daily and I can't
take it anymore. Please remove me, I need my phone and email for my job.
Thank you
On Mon, Nov 21, 2022, 10:43 AM Virgilio Alexandre Fornazin <
@.***> wrote:

"The following script exports the necessary information of the default
owner ("UntrustedGuardian") on a host that is configured using local mode."
There's no script download-able or inside the page
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com
http://learn.microsoft.com ➟ GitHub issue linking.

ID: 3e14cc0c-919d-f378-935e-c078d07e339b
Version Independent ID: b13b9af5-9703-75d4-23a0-128f88da8413
Content: Migrating local VM owner certificates for VMs with vTPM
https://learn.microsoft.com/en-us/virtualization/community/team-blog/2017/20171214-migrating-local-vm-owner-certificates-for-vms-with-vtpm
Content Source:
virtualization/community/team-blog/2017/20171214-migrating-local-vm-owner-certificates-for-vms-with-vtpm.md
https://github.com/MicrosoftDocs/Virtualization-Documentation/blob/live/virtualization/community/team-blog/2017/20171214-migrating-local-vm-owner-certificates-for-vms-with-vtpm.md
Product: powershell
GitHub Login: @mattbriggs https://github.com/mattbriggs
Microsoft Alias: mabrigg

—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/Virtualization-Documentation/issues/1822,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUSVTTZ7TZ55XF3ACFNCMJTWJOKCVANCNFSM6AAAAAASGZAT6U
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


Improvement: Readme

First, it's a good project, i like it. Thanks!
Readme could be improved, for example to let newcomers know that you need to redirect /z/ to index.php?code=$1.
Also it'd be great to explain the obfuscated js, found at the end of the dashboard.php.

Thank you so much. I really appreciate your suggestion and correction. I replaced the obfuscated JS with a non-obfuscated one, and I will be fixing the ReadMe.md the way you recommend. 💖💗


DeprecationWarning: Tapable.plugin is deprecated. Use new API on .hooks instead

Following this post: https://github.com/webpack/webpack/issues/6568#issuecomment-377491754
I added process.traceDeprecation = true to the top of my webpack.common.js and ran the build again.
The output points to this plugin as causing the warning.
clean-webpack-plugin: /Volumes/Vault/Templates/2018-typescript-module/webpack/build has been removed.
  0% compiling(node:83535) DeprecationWarning: Tapable.plugin is deprecated. Use new API on `.hooks` instead
    at Object.apply (/Volumes/Vault/Templates/2018-typescript-module/node_modules/write-file-webpack-plugin/dist/index.js:140:14)
    at webpack (/Volumes/Vault/Templates/2018-typescript-module/node_modules/webpack/lib/webpack.js:37:12)
    at processOptions (/Volumes/Vault/Templates/2018-typescript-module/node_modules/webpack-cli/bin/webpack.js:436:16)
    at yargs.parse (/Volumes/Vault/Templates/2018-typescript-module/node_modules/webpack-cli/bin/webpack.js:512:3)
    at Object.parse (/Volumes/Vault/Templates/2018-typescript-module/node_modules/webpack-cli/node_modules/yargs/yargs.js:552:18)
    at /Volumes/Vault/Templates/2018-typescript-module/node_modules/webpack-cli/bin/webpack.js:217:8
    at Object.<anonymous> (/Volumes/Vault/Templates/2018-typescript-module/node_modules/webpack-cli/bin/webpack.js:514:3)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3)
    at Module.require (module.js:596:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/Volumes/Vault/Templates/2018-typescript-module/node_modules/webpack/bin/webpack.js:80:2)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3)
    at Function.Module.runMain (module.js:693:10)
    at findNodeScript.then.existing (/Users/<>/.nvm/versions/node/v8.10.0/lib/node_modules/npm/node_modules/libnpx/index.js:268:14)
    at <anonymous>

"clean-webpack-plugin": "0.1.19",

Woops, the package causing the issue is on the following line write-file-webpack-plugin . sorry.

in case anyone else finds themselves here, i was getting this error (caused by clean-webpack-plugin, not write-file-webpack-plugin) bc i was still on 0.1.17. upgraded to 0.1.19 and got rid of the deprecation warning


Some small observations

While testing and checking out the projects, I made some edits that may be useful.

I like most / almost all of this. Thanks a lot!!
As this branch is not in this repo, I think I will create a new branch and PR based upon this and make some small changes.

Closing in favor of #23.


DB::Exception: Too many simultaneous queries. Maximum: 1000. (TOO_MANY_SIMULTANEOUS_QUERIES)

Hello ,
We are seeing below exception is clickhouse server log
2024.07.22 06:20:07.987964 [ 15813 ] {aaa59f3c-cf58-4e91-809b-e9db05851a56}  DynamicQueryHandler: Code: 202. DB::Exception: Too many simultaneous queries. Maximum: 1000. (TOO_MANY_SIMULTANEOUS_QUERIES), Stack trace (when copying this message, always include the lines below):

DB::Exception::Exception(DB::Exception::MessageMasked&&, int, bool) @ 0x000000000cf5565b
DB::Exception::Exception<unsigned long&>(int, FormatStringHelperImpl<std::type_identity<unsigned long&>::type>, unsigned long&) @ 0x00000000079aae30
DB::ProcessList::insert(String const&, DB::IAST const*, std::shared_ptrDB::Context, unsigned long) @ 0x0000000011c52fa2
DB::executeQueryImpl(char const*, char const*, std::shared_ptrDB::Context, DB::QueryFlags, DB::QueryProcessingStage::Enum, DB::ReadBuffer*) @ 0x0000000011f64875
DB::executeQuery(DB::ReadBuffer&, DB::WriteBuffer&, bool, std::shared_ptrDB::Context, std::function<void (DB::QueryResultDetails const&)>, DB::QueryFlags, std::optionalDB::FormatSettings const&, std::function<void (DB::IOutputFormat&)>) @ 0x0000000011f6b9a9
DB::HTTPHandler::processQuery(DB::HTTPServerRequest&, DB::HTMLForm&, DB::HTTPServerResponse&, DB::HTTPHandler::Output&, std::optionalDB::CurrentThread::QueryScope&, StrongTypedef<unsigned long, ProfileEvents::EventTag> const&) @ 0x0000000012f5ca15
DB::HTTPHandler::handleRequest(DB::HTTPServerRequest&, DB::HTTPServerResponse&, StrongTypedef<unsigned long, ProfileEvents::EventTag> const&) @ 0x0000000012f61350
DB::HTTPServerConnection::run() @ 0x0000000012fdb73a
Poco::Net::TCPServerConnection::start() @ 0x00000000158af152
Poco::Net::TCPServerDispatcher::run() @ 0x00000000158aff51
Poco::PooledThread::run() @ 0x00000000159a85e7
Poco::ThreadImpl::runnableEntry(void*) @ 0x00000000159a6c1d
? @ 0x00007f0f8e3ae609
? @ 0x00007f0f8e2d3353
(version <IP_ADDRESS>8 (official build))

We are using clickhouse-default-profile for creating users in clickhouse https://github.com/Altinity/clickhouse-operator/blob/master/deploy/helm/clickhouse-operator/values.yaml#L612 and using the same user to ingest data in clickhouse on a large scale
Question:
If we set <max_concurrent_queries_for_all_users>0</max_concurrent_queries_for_all_users> in clickhouse-default-profile , will that resolve the issue?

issue is not related to clickhouse-operator itself, issue is related to clickhouse-server
are you sure you need to run 1000 simultaneous queries?
could you share
clickhouse-client -q "SELECT normalizedQuery(query), count() FROM system.processes GROUP BY ALL"
?

Output:-
CREATE DATABASE IF NOT EXISTS ?  ON CLUSTER x123 - 989 times
looks like this is root reason
why you try to create database so often
something wrong with your application
better run
SYSTEM SHUTDOWN
and restart replica
after that look to your application code

Yes. we have fixed this.
But we cannot push the fix to the stack for atleast 2 weeks
Hence need your expert help in answering below question
If we set <max_concurrent_queries_for_all_users>0</max_concurrent_queries_for_all_users> in clickhouse-default-profile , will that resolve the issue?

Hi @Slach
Would you be able to help here?

Look on max_concurrent_queries  as gate that protects your cluster from more problems that would be harder to debug and would cause much more problems. If you disable it you will cause more problems and mitigate none - it looks like your DDL is run in some kind of busy loop - if you let it loose it will exhaust some other resource in the system.

If we set <max_concurrent_queries_for_all_users>0</max_concurrent_queries_for_all_users> in clickhouse-default-profile , will that resolve the issue?

no, you will just overload clickhouse
and after 5000 qps you will get liveness probe failure
first of all fix your application

also read
https://altinity.com/blog/clickhouse-in-the-storm-part-1
https://altinity.com/blog/clickhouse-in-the-storm-part-2


Add a quick link for getting to the .deb packages

Going to the stated location of https://download.docker.com/linux/ubuntu/dists/trusty/stable/ does not give an easy link to the .deb files. This addition gives such a link.

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Sorry, this is incorrect. Docker CE is not distributed on dockerproject.org. All links for Linux distributions are found beneath https://download.docker.com/linux/.

@mstanleyjones Maybe I missed something big in the link you included. I have seen no binaries at the URL you posted, https://download.docker.com/linux. There are only listings of packages which in turn point to dockerproject.org APT packages. For example, going for  the trusty packages I navigated to https://download.docker.com/linux/ubuntu/dists/trusty/stable/binary-amd64/ and found

The partial contents of the Package file show as follows:
Package: docker-ce
Architecture: amd64
Version: 17.03.0~ce-0~ubuntu-trusty
Priority: optional
Section: admin
Maintainer: Docker<EMAIL_ADDRESS>Installed-Size: 86522
Depends: iptables, init-system-helpers (>= 1.13~), sysv-rc (>= 2.88dsf-24) | file-rc (>= 0.8.16), libapparmor1 (>= 2.6~devel), libc6 (>= 2.17), libdevmapper1.02.1 (>= 2:1.02.63), libltdl7 (>= 2.4.2), libsystemd-journal0 (>= 201)
Recommends: aufs-tools, ca-certificates, cgroupfs-mount | cgroup-lite, git, xz-utils, apparmor
Conflicts: docker (<< 1.5~), docker-ee, docker-engine, docker-engine-cs, docker.io, lxc-docker, lxc-docker-virtual-package
Replaces: docker-engine
Filename: dists/trusty/pool/stable/amd64/docker-ce_17.03.0~ce-0~ubuntu-trusty_amd64.deb
Size: 19123396
MD5sum: 000cd3ae4c4cfc4d5ca79a0886398d4b
SHA1: 62e177aa3a70ac4fcf741492894d1ba53b773aab
SHA256: 389d6ef8a6051de7c0e586cf07d042b60edccbbffeb7c9814001cd6213b7f6dc
SHA512: 28f7c4d5ac650f90ccb60f888052488f9ca18497c7c88d64d0a0152f77f372c995792e80e1630b0e7db9e8f81d08174353ca4c3e20531f0e430f1afbe9c7a7ee
Homepage: https://dockerproject.org
Description: Docker: the open-source application container engine
...[details omitted]

In Apt repositories, the files you need are in the pool directory. For instance: https://download.docker.com/linux/debian/dists/stretch/pool/stable/amd64/
There's no "quick link" because you have to choose the Debian version (stretch here) and the stability (stable / edge / test).

Thank you, I see it now. I think it could be more clear in the documentation that the pool directory is the location of the .deb files. If that is a standard name for a location of .deb files then I am not aware of the standard. I'll change the MR to reflect that if you are interested in such a clarification.

Sure, go for it and ping me when it's ready for review. The pool directory is very standard for Ubuntu and Debian.

With the latest commit I added this MR is good to go.

It looks like the existing file already covers this use case as per my last comment.


[FEAT] Make wash claims aware of wasmcloud.toml

Feature
Just like wash build infers information about a project from the wasmcloud.toml file, it should be a one step process to run wash claims sign to sign an existing wasm file without building.
Alternatives considered
Instead of adding this support, we could make the signing process a core piece of the build command. I don't see any reason why having flexibility here would be bad, running the sign command without worrying about the build process at all is valuable and this would essentially just reduce the number of parameters necessary to supply with wash claims sign.
Origin
          One thing about the `--sign-only` flag: Would it be better user experience for `wash sign` to be `wasmcloud.toml` aware? It feels like that would be more discoverable and ergonomic from my POV

Originally posted by @thomastaylor312 in https://github.com/wasmCloud/wasmCloud/issues/938#issuecomment-1808926592

Closing since this is obviated by https://github.com/wasmCloud/wasmCloud/issues/1219


Add cause to logged error messages

Summary
Add cause to logged error messages.
Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

Do we usually test log messages?
I think logs are mostly implementation details useful for error reporting and debugging, not part of the API contract, so no need to test.
But scenarios such as these where the log is something directed to our users maybe we should test it.

We usually don't test logging, as it is very susceptible to change. But perhaps we could add tests for end-user targeted logs. In this case, we have more tests to write, so I'd recommend merging this PR and later open a new one dedicated only to logging tests.


chore: coveo/actions has moved to coveo-platform/actions DT-6947

Note to reviewer: Merge this pull request when you approve it! Thanks!!
https://coveord.atlassian.net/browse/DT-6947
Summary of changes:

The coveo/actions repository is being moved to coveo-platform/actions

@jonapich do we have access to coveo-platform hosted actions from coveo without privileged tokens?


Crypto-square test incorrect

In clojure, haskell, et. al the expectation for "Madness, and then illumination." is "msemo aanin dnin ndla etlt shui", but in ruby it is 'msemo aanin dninn dlaet ltshu i'. This is due to the tests falsely expecting the result to not be a transposition of the input with spaces, but the flattened transposition separated into chunks the same size as the row length.

Also, the tests included the skips as skip("Skip") which the Makefile doesn't strip, so it seems that the example doesn't even pass the current broken tests - fixing now.

Thanks for catching this. There has been a bit of confusing back-and-forth in the crypto square example.


server: pick the retry local leader read

What is changed and how it works?

Issue Number: Ref #14553

What's Changed:
Pick https://github.com/tikv/tikv/pull/15726 to the tikv-6.5-with-read-timeout branch.

Related changes

[ ] PR to update pingcap/docs/pingcap/docs-cn:
[ ] Need to cherry-pick to the release branch

Check List
Tests

[x] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Release note

None

@crazycs520 PTAL

/test

@MyonKeminta PTAL again, thx

/test


added fontawesome to use common icons.

Summary: added fontawesome to use it's custom icons, this PR should be rebased after merging the bootstrap-sass one to use the new scss syntax.

:+1:


[SPARK-47901][BUILD] Upgrade common-text 1.12.0

What changes were proposed in this pull request?
This pr aims to upgrade Apache common-text from 1.11.0 to 1.12.0
Why are the changes needed?
The new version bring 2 bug fix:

TEXT-232:  WordUtils.containsAllWords?() may throw PatternSyntaxException
TEXT-175:  Fix regression for determining whitespace in WordUtils

The full release notes as follows:

https://github.com/apache/commons-text/blob/rel/commons-text-1.12.0/RELEASE-NOTES.txt

Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass GitHub Actions
Was this patch authored or co-authored using generative AI tooling?
No

Merged into master for Spark 4.0, thanks @yaooqinn ~


Fonts rework

Use system fonts only for text to avoid FOUT
Move font-awesome to npm/webpack
Move NotoColorEmoji to web_src
Remove presumably unneccesary 'PT Sans Narrow'
Simplify webpack import exclusions

Fixes: https://github.com/go-gitea/gitea/issues/11818
Fixes: https://github.com/go-gitea/gitea/pull/11814

LGTM  thanks! I'm also of the opinion that we don't really need to ship a emoji fallback webfont and the few people who run systems that don't install one by default and haven't already  installed one should expect to just not see them which must already be true for almost  every other site they visit.
Feels like an intentional decision for somebody not to have one of these fonts installed at this point and I can't imagine why they would prefer downloading a 9MB Web font instead of installing a real one system wide. I only agreed to it previously because I didn't want the emoji PR held back but think it is unnecessary for us to provide. Maybe for another PR though

Yeah I think I tend to agree to remove the emoji fallback but as it stands, it does not hurt us to have. Browsers should only attempt the download if they can't display a certain emoji. Then there's the issue that the font does not work in Firefox because of a bug there, so it's only targeting Chrome/Edge on Linux really.

would appreciate someone with Chinese locale testing it too however

I did not change anything about the locale-specific font overrides, so I guess those will be fine.

Looks good, would appreciate someone with Chinese locale testing it too however

I will test it after it deployed on try.gitea.io


Support HTTPS client certificate for better security

For better security and to avoid any brute force attempt for the login password, we can support https client certificate in code-sever.
That is an example of how easily it can be supported using node.js.

Instead of supporting many auth methods within code-server itself, we think it's better to make use of the large ecosystem of reverse proxies.
See https://github.com/cdr/code-server/blob/v3.4.1/doc/FAQ.md#how-should-i-expose-code-server-to-the-internet

If you want to use external authentication (i.e sign in with Google) you should handle this with a reverse proxy using something like oauth2_proxy or Cloudflare Access.

To be clear, I fully agree a http client certificate is more secure! We're just trying to avoid configuration complexity within code-server.

I understand. I just see it is very easy to add because it is natively supported in node.js, in fact it is just 1 parameter in server options (i.e. rejectUnauthorized: true). Any second thoughts?
var options = {
    key: fs.readFileSync('server-key.pem'),
    cert: fs.readFileSync('server-crt.pem'),
    ca: fs.readFileSync('ca-crt.pem'),
    crl: fs.readFileSync('ca-crl.pem'),
    requestCert: true,
    rejectUnauthorized: true
};
https.createServer(options, function (req, res) {
    console.log(new Date()+' '+
        req.connection.remoteAddress+' '+
        req.socket.getPeerCertificate().subject.CN+' '+
        req.method+' '+req.url);
    res.writeHead(200);
    res.end("hello world\n");
}).listen(4433);

Well, you'd still have to pass in the ca and crl as well right?
cc @code-asher for thoughts.

It seems simple enough that I'm not opposed to it although admittedly I would rather see authentication happen externally via a reverse proxy.

I think there would also be very few users who would use this as a direct feature in code-server as well so I'm going to close.


Edit murals

Thanks, I like to think it wouldn't have been possible without a class that taught me how to write Scheme inside of ML to make a new version of Impcore