error: weight's shape is different,  _IncompatibleKeys

getting these error with locons trained with https://github.com/KohakuBlueleaf/a1111-sd-webui-locon/commit/9abae9e121d1b5ec4b4b5a8760faa70bfbe0fbd0
did I do something wrong?
weight's shape is different: lora_unet_input_blocks_3_0_op.lora_down.weight expected torch.Size([64, 320, 3, 3]) found torch.Size([64, 320]). SD version may be different
weight's shape is different: lora_unet_input_blocks_1_0_in_layers_2.lora_down.weight expected torch.Size([64, 320, 3, 3]) found torch.Size([64, 320]). SD version may be different
weight's shape is different: lora_unet_input_blocks_1_0_out_layers_3.lora_down.weight expected torch.Size([64, 320, 3, 3]) found torch.Size([64, 320]). SD version may be different
weight's shape is different: lora_unet_input_blocks_2_0_in_layers_2.lora_down.weight expected torch.Size([64, 320, 3, 3]) found torch.Size([64, 320]). SD version may be different
weight's shape is different: lora_unet_input_blocks_2_0_out_layers_3.lora_down.weight expected torch.Size([64, 320, 3, 3]) found torch.Size([64, 320]). SD version may be different
weight's shape is different: lora_unet_input_blocks_6_0_op.lora_down.weight expected torch.Size([64, 640, 3, 3]) found torch.Size([64, 640]). SD version may be different
weight's shape is different: lora_unet_input_blocks_4_0_in_layers_2.lora_down.weight expected torch.Size([64, 320, 3, 3]) found torch.Size([64, 320]). SD version may be different
weight's shape is different: lora_unet_input_blocks_4_0_out_layers_3.lora_down.weight expected torch.Size([64, 640, 3, 3]) found torch.Size([64, 640]). SD version may be different
weight's shape is different: lora_unet_input_blocks_5_0_in_layers_2.lora_down.weight expected torch.Size([64, 640, 3, 3]) found torch.Size([64, 640]). SD version may be different
weight's shape is different: lora_unet_input_blocks_5_0_out_layers_3.lora_down.weight expected torch.Size([64, 640, 3, 3]) found torch.Size([64, 640]). SD version may be different
weight's shape is different: lora_unet_input_blocks_9_0_op.lora_down.weight expected torch.Size([64, 1280, 3, 3]) found torch.Size([64, 1280]). SD version may be different
weight's shape is different: lora_unet_input_blocks_7_0_in_layers_2.lora_down.weight expected torch.Size([64, 640, 3, 3]) found torch.Size([64, 640]). SD version may be different
weight's shape is different: lora_unet_input_blocks_7_0_out_layers_3.lora_down.weight expected torch.Size([64, 1280, 3, 3]) found torch.Size([64, 1280]). SD version may be different
weight's shape is different: lora_unet_input_blocks_8_0_in_layers_2.lora_down.weight expected torch.Size([64, 1280, 3, 3]) found torch.Size([64, 1280]). SD version may be different
weight's shape is different: lora_unet_input_blocks_8_0_out_layers_3.lora_down.weight expected torch.Size([64, 1280, 3, 3]) found torch.Size([64, 1280]). SD version may be different
weight's shape is different: lora_unet_input_blocks_10_0_in_layers_2.lora_down.weight expected torch.Size([64, 1280, 3, 3]) found torch.Size([64, 1280]). SD version may be different
weight's shape is different: lora_unet_input_blocks_10_0_out_layers_3.lora_down.weight expected torch.Size([64, 1280, 3, 3]) found torch.Size([64, 1280]). SD version may be different
weight's shape is different: lora_unet_input_blocks_11_0_in_layers_2.lora_down.weight expected torch.Size([64, 1280, 3, 3]) found torch.Size([64, 1280]). SD version may be different
weight's shape is different: lora_unet_input_blocks_11_0_out_layers_3.lora_down.weight expected torch.Size([64, 1280, 3, 3]) found torch.Size([64, 1280]). SD version may be different
weight's shape is different: lora_unet_middle_block_0_in_layers_2.lora_down.weight expected torch.Size([64, 1280, 3, 3]) found torch.Size([64, 1280]). SD version may be different
weight's shape is different: lora_unet_middle_block_0_out_layers_3.lora_down.weight expected torch.Size([64, 1280, 3, 3]) found torch.Size([64, 1280]). SD version may be different
weight's shape is different: lora_unet_middle_block_2_in_layers_2.lora_down.weight expected torch.Size([64, 1280, 3, 3]) found torch.Size([64, 1280]). SD version may be different
weight's shape is different: lora_unet_middle_block_2_out_layers_3.lora_down.weight expected torch.Size([64, 1280, 3, 3]) found torch.Size([64, 1280]). SD version may be different
weight's shape is different: lora_unet_output_blocks_0_0_in_layers_2.lora_down.weight expected torch.Size([64, 2560, 3, 3]) found torch.Size([64, 2560]). SD version may be different
weight's shape is different: lora_unet_output_blocks_0_0_out_layers_3.lora_down.weight expected torch.Size([64, 1280, 3, 3]) found torch.Size([64, 1280]). SD version may be different
weight's shape is different: lora_unet_output_blocks_1_0_in_layers_2.lora_down.weight expected torch.Size([64, 2560, 3, 3]) found torch.Size([64, 2560]). SD version may be different
weight's shape is different: lora_unet_output_blocks_1_0_out_layers_3.lora_down.weight expected torch.Size([64, 1280, 3, 3]) found torch.Size([64, 1280]). SD version may be different
weight's shape is different: lora_unet_output_blocks_2_0_in_layers_2.lora_down.weight expected torch.Size([64, 2560, 3, 3]) found torch.Size([64, 2560]). SD version may be different
weight's shape is different: lora_unet_output_blocks_2_0_out_layers_3.lora_down.weight expected torch.Size([64, 1280, 3, 3]) found torch.Size([64, 1280]). SD version may be different
weight's shape is different: lora_unet_output_blocks_2_1_conv.lora_down.weight expected torch.Size([64, 1280, 3, 3]) found torch.Size([64, 1280]). SD version may be different
weight's shape is different: lora_unet_output_blocks_3_0_in_layers_2.lora_down.weight expected torch.Size([64, 2560, 3, 3]) found torch.Size([64, 2560]). SD version may be different
weight's shape is different: lora_unet_output_blocks_3_0_out_layers_3.lora_down.weight expected torch.Size([64, 1280, 3, 3]) found torch.Size([64, 1280]). SD version may be different
weight's shape is different: lora_unet_output_blocks_4_0_in_layers_2.lora_down.weight expected torch.Size([64, 2560, 3, 3]) found torch.Size([64, 2560]). SD version may be different
weight's shape is different: lora_unet_output_blocks_4_0_out_layers_3.lora_down.weight expected torch.Size([64, 1280, 3, 3]) found torch.Size([64, 1280]). SD version may be different
weight's shape is different: lora_unet_output_blocks_5_0_in_layers_2.lora_down.weight expected torch.Size([64, 1920, 3, 3]) found torch.Size([64, 1920]). SD version may be different
weight's shape is different: lora_unet_output_blocks_5_0_out_layers_3.lora_down.weight expected torch.Size([64, 1280, 3, 3]) found torch.Size([64, 1280]). SD version may be different
weight's shape is different: lora_unet_output_blocks_5_2_conv.lora_down.weight expected torch.Size([64, 1280, 3, 3]) found torch.Size([64, 1280]). SD version may be different
weight's shape is different: lora_unet_output_blocks_6_0_in_layers_2.lora_down.weight expected torch.Size([64, 1920, 3, 3]) found torch.Size([64, 1920]). SD version may be different
weight's shape is different: lora_unet_output_blocks_6_0_out_layers_3.lora_down.weight expected torch.Size([64, 640, 3, 3]) found torch.Size([64, 640]). SD version may be different
weight's shape is different: lora_unet_output_blocks_7_0_in_layers_2.lora_down.weight expected torch.Size([64, 1280, 3, 3]) found torch.Size([64, 1280]). SD version may be different
weight's shape is different: lora_unet_output_blocks_7_0_out_layers_3.lora_down.weight expected torch.Size([64, 640, 3, 3]) found torch.Size([64, 640]). SD version may be different
weight's shape is different: lora_unet_output_blocks_8_0_in_layers_2.lora_down.weight expected torch.Size([64, 960, 3, 3]) found torch.Size([64, 960]). SD version may be different
weight's shape is different: lora_unet_output_blocks_8_0_out_layers_3.lora_down.weight expected torch.Size([64, 640, 3, 3]) found torch.Size([64, 640]). SD version may be different
weight's shape is different: lora_unet_output_blocks_8_2_conv.lora_down.weight expected torch.Size([64, 640, 3, 3]) found torch.Size([64, 640]). SD version may be different
weight's shape is different: lora_unet_output_blocks_9_0_in_layers_2.lora_down.weight expected torch.Size([64, 960, 3, 3]) found torch.Size([64, 960]). SD version may be different
weight's shape is different: lora_unet_output_blocks_9_0_out_layers_3.lora_down.weight expected torch.Size([64, 320, 3, 3]) found torch.Size([64, 320]). SD version may be different
weight's shape is different: lora_unet_output_blocks_10_0_in_layers_2.lora_down.weight expected torch.Size([64, 640, 3, 3]) found torch.Size([64, 640]). SD version may be different
weight's shape is different: lora_unet_output_blocks_10_0_out_layers_3.lora_down.weight expected torch.Size([64, 320, 3, 3]) found torch.Size([64, 320]). SD version may be different
weight's shape is different: lora_unet_output_blocks_11_0_in_layers_2.lora_down.weight expected torch.Size([64, 640, 3, 3]) found torch.Size([64, 640]). SD version may be different
weight's shape is different: lora_unet_output_blocks_11_0_out_layers_3.lora_down.weight expected torch.Size([64, 320, 3, 3]) found torch.Size([64, 320]). SD version may be different

_IncompatibleKeys(missing_keys=['lora_unet_input_blocks_1_0_in_layers_2.lora_down.weight', 'lora_unet_input_blocks_1_0_out_layers_3.lora_down.weight', 'lora_unet_input_blocks_2_0_in_layers_2.lora_down.weight', 'lora_unet_input_blocks_2_0_out_layers_3.lora_down.weight', 'lora_unet_input_blocks_3_0_op.lora_down.weight', 'lora_unet_input_blocks_4_0_in_layers_2.lora_down.weight', 'lora_unet_input_blocks_4_0_out_layers_3.lora_down.weight', 'lora_unet_input_blocks_5_0_in_layers_2.lora_down.weight', 'lora_unet_input_blocks_5_0_out_layers_3.lora_down.weight', 'lora_unet_input_blocks_6_0_op.lora_down.weight', 'lora_unet_input_blocks_7_0_in_layers_2.lora_down.weight', 'lora_unet_input_blocks_7_0_out_layers_3.lora_down.weight', 'lora_unet_input_blocks_8_0_in_layers_2.lora_down.weight', 'lora_unet_input_blocks_8_0_out_layers_3.lora_down.weight', 'lora_unet_input_blocks_9_0_op.lora_down.weight', 'lora_unet_input_blocks_10_0_in_layers_2.lora_down.weight', 'lora_unet_input_blocks_10_0_out_layers_3.lora_down.weight', 'lora_unet_input_blocks_11_0_in_layers_2.lora_down.weight', 'lora_unet_input_blocks_11_0_out_layers_3.lora_down.weight', 'lora_unet_middle_block_0_in_layers_2.lora_down.weight', 'lora_unet_middle_block_0_out_layers_3.lora_down.weight', 'lora_unet_middle_block_2_in_layers_2.lora_down.weight', 'lora_unet_middle_block_2_out_layers_3.lora_down.weight', 'lora_unet_output_blocks_0_0_in_layers_2.lora_down.weight', 'lora_unet_output_blocks_0_0_out_layers_3.lora_down.weight', 'lora_unet_output_blocks_1_0_in_layers_2.lora_down.weight', 'lora_unet_output_blocks_1_0_out_layers_3.lora_down.weight', 'lora_unet_output_blocks_2_0_in_layers_2.lora_down.weight', 'lora_unet_output_blocks_2_0_out_layers_3.lora_down.weight', 'lora_unet_output_blocks_2_1_conv.lora_down.weight', 'lora_unet_output_blocks_3_0_in_layers_2.lora_down.weight', 'lora_unet_output_blocks_3_0_out_layers_3.lora_down.weight', 'lora_unet_output_blocks_4_0_in_layers_2.lora_down.weight', 'lora_unet_output_blocks_4_0_out_layers_3.lora_down.weight', 'lora_unet_output_blocks_5_0_in_layers_2.lora_down.weight', 'lora_unet_output_blocks_5_0_out_layers_3.lora_down.weight', 'lora_unet_output_blocks_5_2_conv.lora_down.weight', 'lora_unet_output_blocks_6_0_in_layers_2.lora_down.weight', 'lora_unet_output_blocks_6_0_out_layers_3.lora_down.weight', 'lora_unet_output_blocks_7_0_in_layers_2.lora_down.weight', 'lora_unet_output_blocks_7_0_out_layers_3.lora_down.weight', 'lora_unet_output_blocks_8_0_in_layers_2.lora_down.weight', 'lora_unet_output_blocks_8_0_out_layers_3.lora_down.weight', 'lora_unet_output_blocks_8_2_conv.lora_down.weight', 'lora_unet_output_blocks_9_0_in_layers_2.lora_down.weight', 'lora_unet_output_blocks_9_0_out_layers_3.lora_down.weight', 'lora_unet_output_blocks_10_0_in_layers_2.lora_down.weight', 'lora_unet_output_blocks_10_0_out_layers_3.lora_down.weight', 'lora_unet_output_blocks_11_0_in_layers_2.lora_down.weight', 'lora_unet_output_blocks_11_0_out_layers_3.lora_down.weight'], unexpected_keys=['lora_unet_input_blocks_1_0_in_layers_2.lora_mid.weight', 'lora_unet_input_blocks_1_0_out_layers_3.lora_mid.weight', 'lora_unet_input_blocks_2_0_in_layers_2.lora_mid.weight', 'lora_unet_input_blocks_2_0_out_layers_3.lora_mid.weight', 'lora_unet_input_blocks_3_0_op.lora_mid.weight', 'lora_unet_input_blocks_4_0_in_layers_2.lora_mid.weight', 'lora_unet_input_blocks_4_0_out_layers_3.lora_mid.weight', 'lora_unet_input_blocks_5_0_in_layers_2.lora_mid.weight', 'lora_unet_input_blocks_5_0_out_layers_3.lora_mid.weight', 'lora_unet_input_blocks_6_0_op.lora_mid.weight', 'lora_unet_input_blocks_7_0_in_layers_2.lora_mid.weight', 'lora_unet_input_blocks_7_0_out_layers_3.lora_mid.weight', 'lora_unet_input_blocks_8_0_in_layers_2.lora_mid.weight', 'lora_unet_input_blocks_8_0_out_layers_3.lora_mid.weight', 'lora_unet_input_blocks_9_0_op.lora_mid.weight', 'lora_unet_input_blocks_10_0_in_layers_2.lora_mid.weight', 'lora_unet_input_blocks_10_0_out_layers_3.lora_mid.weight', 'lora_unet_input_blocks_11_0_in_layers_2.lora_mid.weight', 'lora_unet_input_blocks_11_0_out_layers_3.lora_mid.weight', 'lora_unet_middle_block_0_in_layers_2.lora_mid.weight', 'lora_unet_middle_block_0_out_layers_3.lora_mid.weight', 'lora_unet_middle_block_2_in_layers_2.lora_mid.weight', 'lora_unet_middle_block_2_out_layers_3.lora_mid.weight', 'lora_unet_output_blocks_0_0_in_layers_2.lora_mid.weight', 'lora_unet_output_blocks_0_0_out_layers_3.lora_mid.weight', 'lora_unet_output_blocks_1_0_in_layers_2.lora_mid.weight', 'lora_unet_output_blocks_1_0_out_layers_3.lora_mid.weight', 'lora_unet_output_blocks_2_0_in_layers_2.lora_mid.weight', 'lora_unet_output_blocks_2_0_out_layers_3.lora_mid.weight', 'lora_unet_output_blocks_2_1_conv.lora_mid.weight', 'lora_unet_output_blocks_3_0_in_layers_2.lora_mid.weight', 'lora_unet_output_blocks_3_0_out_layers_3.lora_mid.weight', 'lora_unet_output_blocks_4_0_in_layers_2.lora_mid.weight', 'lora_unet_output_blocks_4_0_out_layers_3.lora_mid.weight', 'lora_unet_output_blocks_5_0_in_layers_2.lora_mid.weight', 'lora_unet_output_blocks_5_0_out_layers_3.lora_mid.weight', 'lora_unet_output_blocks_5_2_conv.lora_mid.weight', 'lora_unet_output_blocks_6_0_in_layers_2.lora_mid.weight', 'lora_unet_output_blocks_6_0_out_layers_3.lora_mid.weight', 'lora_unet_output_blocks_7_0_in_layers_2.lora_mid.weight', 'lora_unet_output_blocks_7_0_out_layers_3.lora_mid.weight', 'lora_unet_output_blocks_8_0_in_layers_2.lora_mid.weight', 'lora_unet_output_blocks_8_0_out_layers_3.lora_mid.weight', 'lora_unet_output_blocks_8_2_conv.lora_mid.weight', 'lora_unet_output_blocks_9_0_in_layers_2.lora_mid.weight', 'lora_unet_output_blocks_9_0_out_layers_3.lora_mid.weight', 'lora_unet_output_blocks_10_0_in_layers_2.lora_mid.weight', 'lora_unet_output_blocks_10_0_out_layers_3.lora_mid.weight', 'lora_unet_output_blocks_11_0_in_layers_2.lora_mid.weight', 'lora_unet_output_blocks_11_0_out_layers_3.lora_mid.weight'])

You should update the extension

Are you using some other extension for lora?

LoHa and LoCon with cp decomposition doesn't support addnet now

your training is broken
maybe due to the change of weight init value
try to tune the training parameter

@azumukupoe You should use more small dim (
if you resolution is different from the resolution that base model trained on
conv will learn more about "how to denoise"
and sometime it will make your training process broken


Flutter gestures  conflict in UIScrollview

If you embed FlutterViewController.view in UIScrollView
the flutter gestures will conflict with the UIScrollView
for example : the Textfiled selection handlers  (longpress the Textfiled, will show 2 handlers),

var scrollView:UIScrollView!
    var flutterViewController:UIViewController!
    var contentView:UIView!
    override func viewDidLoad() {
        super.viewDidLoad()
        view.backgroundColor = #colorLiteral(red: 0.9333327413, green: 0.9333335757, blue: 0.9490187764, alpha: 1)

        let flutterEngine = (UIApplication.shared.delegate as! AppDelegate).flutterEngine
        flutterViewController = FlutterViewController(engine: flutterEngine, nibName: nil, bundle: nil)
        self.addChild(flutterViewController)

        scrollView = UIScrollView()
        view.addSubview(scrollView)
        scrollView.backgroundColor = .yellow
        scrollView.translatesAutoresizingMaskIntoConstraints = false

        contentView = UIView(frame: CGRect(x: 0, y: 0, width: 1000, height: 1000))
        contentView.backgroundColor = .green
        scrollView.addSubview(contentView)

        contentView.addSubview(flutterViewController.view)
        flutterViewController.view.translatesAutoresizingMaskIntoConstraints = false
        NSLayoutConstraint.activate([
            scrollView.leftAnchor.constraint(equalTo: view.leftAnchor),
            scrollView.rightAnchor.constraint(equalTo: view.rightAnchor),
            scrollView.topAnchor.constraint(equalTo: view.safeAreaLayoutGuide.topAnchor),
            scrollView.bottomAnchor.constraint(equalTo: view.bottomAnchor),

            flutterViewController.view.leftAnchor.constraint(equalTo: contentView.leftAnchor),
            flutterViewController.view.rightAnchor.constraint(equalTo: contentView.rightAnchor),
            flutterViewController.view.topAnchor.constraint(equalTo: contentView.topAnchor),
            flutterViewController.view.bottomAnchor.constraint(equalTo: contentView.bottomAnchor),
        ])
        scrollView.contentSize = CGSize(width: 1000, height: 1000)
    }

Hi @FlashTang
In order to address the issue properly, please provide a completed and minimal reproducible code sample so that we may verify this.
Also, please provide the output of flutter doctor -v and be more specific on Steps to reproduce, Actual result, and Expected result.
Thank you!

Thanks for providing the sample code, but I'm not sure what the issue is here. What does it mean "can not select charactors"? Please be more specific on Steps to reproduce, Actual result, Expected result.

Demo (iOS)

@huycozy
Thank you for response, I guess you are running 'my_flutter' project directly ?, my_flutter is a module
please open and run the Xcode project EmbedInScrollView.xcworkspace locate in EmbedInScrollView folder, otherwise there will be no wrapped UIScrollView
As you can see , there are two blue dots in Textfield

normally you can drag & move the blue dot to change the range (select characters you want, )
but in this case you can't, it will scroll the native UIScrollView instead (conflict)

No, I ran the native project (I knew it's add-to-app project). I see the issue now, there are the conflict gestures between UIScrollView and Flutter TextField handlers.
Can you try implementing this solution to see if it works for your case?

No, I ran the native project (I knew it's add-to-app project). I see the issue now, there are the conflict gestures between UIScrollView and Flutter TextField handlers.
Can you try implementing this solution to see if it works for your case?

Hi, I just converted the Obj-C solution (by @HaoXianSen) to swift version  and applied to the project
here is the project which applied the solution above you mentioned
https://github.com/FlashTang/flutter_scrollview_issue_try_fix
but, unfortunately, the native UIScrollView will stop working completely as long as the touches are inside the 'FlutterView' I think.
The textfield selecting issue is just an example, in fact all touch events are conflicting in such cases
I think this issue is more complicated, maybe flutter should provide function(s) to stop bubbling events to native ?
like webview -  event.stopPropagation() and event.preventDefault()  does.
Thank you.

Hi, I re-clone your updated sample code and see the handler can be dragged.

Demo with updated sample code
https://user-images.githubusercontent.com/104349824/229413955-424ec64b-c116-4c53-b1a9-17c142650441.MP4

I think this issue is more complicated, maybe flutter should provide function(s) to stop bubbling events to native ?

For another issue, you should control it manually by your own implementation. The idea behind this is that you can detect when to block/allow UIScrollView's gesture (maybe when focusing on TextField for example)
Please see https://flutter.dev/community for resources and ask questions like this. You may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp.
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it. Thank you!

Hi, I re-clone your updated sample code and see the handler can be dragged.
Demo with updated sample code

I think this issue is more complicated, maybe flutter should provide function(s) to stop bubbling events to native ?

For another issue, you should control it manually by your own implementation. The idea behind this is that you can detect when to block/allow UIScrollView's gesture (maybe when focusing on TextField for example)
Please see https://flutter.dev/community for resources and ask questions like this. You may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp.
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it. Thank you!

@huycozy
Hi , the handler can be dragged because the UIScrollView gesture is disabled (since the view is FlutterView)
Thanks for your help, the idea sounds good , maybe I should pass event to UIScrollView delegate from Flutter gesturedetector


Feature request - HA Postgres cluster

From @tamalsaha on November 19, 2017 5:5
From @rimusz on October 4, 2017 12:21
HA Postgres cluster support please :)
Copied from original issue: k8sdb/cli#120
Copied from original issue: kubedb/operator#131

KubeDB Postgres supports HA cluster with asynchronous replication.


Application v2 Basic Auth Header

Changed create application request auth to use basic auth based on changes announced by the Product API team

As part of releasing an internal security update for the Applications Service, we noticed that v2 of the public-facing Application API was accepting API key/secret as request params for authentication. This has been treated as a bug.
Request parameter auth was never intended to be supported and was not documented publicly or internally for v2 of the API. We recommend customers use header auth (basic auth) for this API instead. https://developer.nexmo.com/concepts/guides/authentication#header-based-api-key-and-secret-authentication

Contribution Checklist

[x] Unit tests!
[x] Updated CHANGELOG.md
[x] My name is in CONTRIBUTORS.md

Closing. Wrong repo


4.x: antlr-runtime dependency convergence

Environment Details

Helidon Version: 4.0.1

Problem Description
[ERROR] Rule 0: org.apache.maven.enforcer.rules.dependency.DependencyConvergence failed with message:
[ERROR] Failed while enforcing releasability.
[ERROR]
[ERROR] Dependency convergence error for org.antlr:antlr4-runtime:jar:4.9.3 paths to dependency are:
[ERROR] +-io.helidon:helidon-all:pom:4.0.0-SNAPSHOT
[ERROR]   +-io.helidon.graphql:helidon-graphql-server:jar:4.0.0-SNAPSHOT:compile
[ERROR]     +-com.graphql-java:graphql-java:jar:18.6:compile
[ERROR]       +-org.antlr:antlr4-runtime:jar:4.9.3:runtime
[ERROR] and
[ERROR] +-io.helidon:helidon-all:pom:4.0.0-SNAPSHOT
[ERROR]   +-io.helidon.integrations.cdi:helidon-integrations-cdi-hibernate:jar:4.0.0-SNAPSHOT:compile
[ERROR]     +-org.hibernate.orm:hibernate-core:jar:6.3.1.Final:compile
[ERROR]       +-org.antlr:antlr4-runtime:jar:4.10.1:runtime

Steps to reproduce
Comment-out workaround in all/pom.xml (dependencyManagement at the bottom).
mvn validate -f all/pom.xml

The fix to this issue should remove the work-arounds in the following files (see #8171):

all/pom.xml
dependencies/pom.xml

I have tried fixing this by upgrading graphql-java to 22.1, but then we have a problem with failing tests:
[ERROR] Failures:
[ERROR]   DateTimeIT.testDateAndTime:152
Expected: is "02/17/1968"
     but: was <1968-02-17>
[ERROR]   DateTimeIT.testDateInputsAsPojo:283->validateResult:325
Expected: is "02/17/1968"
     but: was <1968-02-17>
[ERROR]   MapIT.testMap:55->AbstractGraphQLTest.getAndAssertResult:218 Errors: Server Error

[ERROR]   NumberFormatIT.testNumberFormats:72
Expected: is "1 id"
     but: was "1"
[ERROR] Errors:
[ERROR]   DateTimeIT.testDatesAndMutations:243 ClassCast class java.time.LocalDate cannot be cast to class java.lang.String (java.time.LocalDate and java.lang.String are in module java.base of loader 'bootstrap')
[ERROR]   DateTimeIT.testDifferentSetterGetter:72 ClassCast class java.time.LocalDate cannot be cast to class java.lang.String (java.time.LocalDate and java.lang.String are in module java.base of loader 'bootstrap')
[ERROR]   DateTimeScalarIT.testDateAndTime:66 ClassCast class java.time.LocalDate cannot be cast to class java.lang.String (java.time.LocalDate and java.lang.String are in module java.base of loader 'bootstrap')

So there seem to be backward incompatible changes, which may be a problem to introduce in 4.1.


Example Code in README fails.

There is an assertion error in the example code in the README.
The text that  is input to the model
"[CLS] Who was Jim Henson ? [SEP] Jim Henson was a puppeteer [SEP]"
is expected to be tokenized and masked like so
['[CLS]', 'who', 'was', 'jim', 'henson', '?', '[SEP]', 'jim', '[MASK]', 'was', 'a', 'puppet', '##eer', '[SEP]'].
However the [CLS] and [SEP] tokens are split up and in the class of [CLS] it is broken into word pieces. The actual tokenized results looks like this
['[', 'cl', '##s', ']', 'who', 'was', 'jim', 'henson', '[MASK]', '[', 'sep', ']', 'jim', 'henson', 'was', 'a', 'puppet', '##eer', '[', 'sep', ']']

This could be related to #266 - are you using the latest version of pytorch-pretrained-BERT?
``

No, I was on 0.4, I upgraded to 0.6.1 and it worked.


Safari "not supported" banner styling issues

Banner on safari browser isn't readable.

This is a sign to support safari :)


Fix instance list fetch

Making URL the single source of truth is making the instance list view very slow to load, May be we can tackle this later, for now the above fix works fine.


[PE-D][Tester A] Hyperlink in Argument Constraints Summary section of the UG does not work

Your browser does not support the video tag.video:https://raw.githubusercontent.com/Dinoman44/ped/main/files/299e871c-f5c5-4496-af9b-e2cf23a9bc41.mov
This hyperlink (if there is any) does not seem to work. Other hyperlinks in the table work.
(Found in the Argument Constraints Summary section of the UG)

Labels: severity.VeryLow type.DocumentationBug
original: Dinoman44/ped#9

duplicate with #194


fix(operation): fix golint

Codecov Report

Merging #41 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #41   +/-   ##
=======================================
  Coverage   93.62%   93.62%
=======================================
  Files           4        4
  Lines         392      392
=======================================
  Hits          367      367
  Misses         18       18
  Partials        7        7

Impacted Files
Coverage Δ

operation.go
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Design brushup proposal

I drafted a quick proposal how to make the UI clearer and easier to use. Feel free to use it or not ;-)

Colors:

White:
Section title font
Active layer font
Button font + stroke 1px
Active input field
666666
All other fonts
Scrollbars
262626
Active layer background
Hover layer background
Section header background
1a1a1a
Header background
First sidebar background
212121
Second sidebar background
353535
Input field + dropdown background
505050
Input field + dropdown stroke 1px

Font sizes:

14px: Section Titles
11px: Form controls + buttons
12px: Layer list, form labels

Left margins:

10px: Layer list, Section titles
20px: Form labels

Very nice I like it. Thanks a lot, appreciate it.
Will track progress on it on this ticket.

You may want to increase the contrast slightly for accessibility reasons. For example #262626 on a #666666 background fails Web Content Accessibility Guidelines contrast ratio see http://leaverou.github.io/contrast-ratio/#%23666666-on-%23262626

You are right @orangemug.
I updated the mockup, also with some color changes and checkboxes added.

Colors:

White:
Section title font
Active layer font
Button font + stroke 1px
Input field font
Selected checkbox button font
Active input field background
666666
All other fonts
Scrollbars
353535
Active layer background
Hover layer background
Section header background
Input field + dropdown background
1a1a1a
Header background
First sidebar background
Mouse over checkbox button background
212121
Second sidebar background
505050
Selected checkbox button background
Input field + dropdown stroke 1px

Font sizes:

14px: Section Titles
11px: Form controls + buttons
12px: Layer list, form labels

Left margins:

10px: Layer list, Section titles
20px: Form labels

Alternative "Add filter" styling:

Migrated all inline-styles to CSS (larger effort than i thought - but also helped to clean up).
I already implemented some of the suggestions.
Styles can now be directly tweaked at https://github.com/maputnik/editor/tree/master/src/styles

The colors all depend on the variables in https://github.com/maputnik/editor/blob/master/src/styles/index.scss.
So there is one place to tweak colors.

One more thing: With a section header "Layers" in the first sidebar the "Add Layer" button can be moved from the page header to the sidebar. (I find the original position a little bit odd.)

One more thing: With a section header "Layers" in the first sidebar the "Add Layer" button can be moved from the page header to the sidebar. (I find the original position a little bit odd.)

Yes sidebar is more suitable!!
Feedback on modals and the menu is welcome as well.
Sources icon is not ideal  but the name "Sources" indicates the right thing I think.
Download will probably in the future change to "Export" to open a modal.

I thought about the menu and the modals and found only two more (minor) issues:

The "Inspect" Button is actually an on/off button, so it should visibly change state. Either by conveying on/off (colors?) or by switching the wording (Inspect mode / Map mode or X-Ray view / Map view).
In the "Sources" modal I find "Choose public sources" more important than "Add new source". Would move it up.

[ ] Try out how Lucida Sans looks

Lucida Sans Regular: Everything else

@muesliq After some Google searches I don't think that's a free font..

Lucida Sans Unicode is a "web safe font", so you don't need to embed it or worry about licensing, you just reference it. Like, you know, in the old days ;-)

Most of the points have been implemented, I'm closing this now.


Copy-DbaSsisCatalog fails when only one SSIS service is running on destination server

Bug Report

General Troubleshooting steps

[x] Verified running latest release of dbatools?  (Downloaded and installed on 9/20/2017 via
Invoke-Expression (Invoke-WebRequest -UseBasicParsing https://dbatools.io/in)

[x] Verified errors are not related to permissions?

[x] Can duplicate in new/fresh PowerShell.exe session?

Version Information

Operating System (Windows Server 2012 R2):
PowerShell Version:

PS C:\Windows\system32> $PSVersionTable.PSVersion

Major  Minor  Build  Revision
-----  -----  -----  --------
4      0      -1     -1

SQL Server (SQL 2016|13.0.4451):

Steps to Reproduce

I only have one SSIS instance running, it appears that the Copy-DbaSsisCatalog function calls the Get-RemoteIntegrationService function... and Get-RemoteIntegrationService calls Get-DbaSqlService -ComputerName $Computer | Where-Object Servicename -like "MsDts*" ... and it is erroring out when $result.Count -gt 0 fails (line 113 on https://github.com/sqlcollaborative/dbatools/blob/master/functions/Copy-DbaSsisCatalog.ps1)
I think line 113 fails because only one object is returned, and thus it isn't a collection? (And thus the .Count property is empty?)
Changing line 113 solved it for me:
#Old Line 113
if ($result.Count -gt 0) {
#New Line 113:
if ($result) {

[x] Attach any screenshots (if possible/allowed)
Screenshot of error:

Screenshot of related lines from Copy-DbaSsisCatalog:

Problem to solve
I think the $result = Get-DbaSqlService -ComputerName $Computer | Where-Object Servicename -like "MsDts*" call might need to be changed to Get-DbaSqlService -Type SSIS (however, my testing shows the same issue).
In the end, it appears that $result = Get-DbaSqlService -ComputerName $Computer | Where-Object Servicename -like "MsDts*" has a value, the the .count property is empty when $result is only one object.

Fixed.


Wallet Restore

Created Wallet
Transferred 0.999999 (1 CASH - fee) to Wallet.
Balance shows correctly once synced.
Renamed wallet.db to wallet.dbOriginal
Restored Wallet from seed.
Balance shows 0 CASH ...
Therefore Transferred 0.99999900 (1 CASH - fee) to the restored wallet.
Balance shows correctly once synced.
Tried Restoring Wallet again from seed.  Shows 0 CASH.
Tried restore a 3rd time.  Same result.  I now have 3 wallets with 0.999999 CASH!!!!!
Is there an issue with seed restore?
beam v2.5.96 ubuntu report.zip

If I understand correctly, you are restoring to the same pc right? If you close the wallet, copy the original wallet.db file back to where it was, and then re-open the wallet, does it show the right balance now?

Same PC.  Original Wallet only shows the one transaction of 0.999999 - Blockchain Height is showing as 1789892

That looks correct. Are you set up to use a remote node or local node?

Remote Node: explorer.lite-cash.com:10000

Ok try changing it to localnode and make sure to have a peer in the list.
You can use the same explore address you are using for remote node. You can also add ca1.lite-cash.com:10000. It's good to have more than one.

Any luck?

Perfect.  Balance now 2.999997.
Just to confirm. Running on local nodes explorer.lite-cash.com:10000 and ca1.lite-cash.com:10000

yep that should work just fine :)


IPv6 now working when using 6rd with a /64 prefix

Describe the bug
All what follows is on OPNsense 20.1.4 (i386/OpenSSL).
My ISP supports IPv6 using 6rd but sadly only assigns a single /64. However this should be enough to have radvd/SLAAC on the LAN interface, and indeed it works fine with the router provided by the ISP. But let's proceed by steps.
I can properly set up 6rd on the WAN interface. I need to manually add wan_stf as the IPv6 default route to workaround https://github.com/opnsense/core/issues/3903, but then the tunnel works fine:

root@net6501:~ # ifconfig wan_stf
wan_stf: flags=4041 metric 0 mtu 1280
	inet6 2001:b07:5d2e:58c7:: prefixlen 64
	nd6 options=1
	v4net <IP_ADDRESS>/0 -> tv4br <IP_ADDRESS>
	groups: stf

root@net6501:~ # route -6 get default
   route to: default
destination: default
       mask: default
        fib: 0
  interface: wan_stf
      flags:
 recvpipe  sendpipe  ssthresh  rtt,msec    mtu        weight    expire
       0         0         0         0      1280         1         0

root@net6501:~ # ping6 -c1 ipv6.google.com
PING6(56=40+8+8 bytes) 2001:b07:5d2e:58c7:: --> 2a00:1450:4002:805::200e
16 bytes from 2a00:1450:4002:805::200e, icmp_seq=0 hlim=57 time=7.416 ms

The LAN interface is configured to track the WAN interface, with IPv6 prefix ID 0x0 (IIUC as I have a single /64 this is the only choice). The interface configuration looks correct: the LAN interface get assigned the :1 address of the 6rd /64:

bridge0: flags=8843 metric 0 mtu 1500
	ether 02:9d:ee:f2:88:00
	inet <IP_ADDRESS> netmask 0xffffff00 broadcast <IP_ADDRESS>
	inet6 2001:b07:5d2e:58c7::1 prefixlen 64
	inet6 fe80::29d:eeff:fef2:8800%bridge0 prefixlen 64 scopeid 0xa
	nd6 options=1
	groups: bridge
	id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
	maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
	root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
	member: ath0_wlan1 flags=143
	        ifmaxaddr 0 port 9 priority 128 path cost 33333
	member: em1 flags=143
	        ifmaxaddr 0 port 2 priority 128 path cost 55

and the router advertisement also works, as my laptop on the LAN gets assigned addresses on the right /64:

3: wlp61s0:  mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 48:f1:7f:b4:3e:9e brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global dynamic noprefixroute wlp61s0
       valid_lft 4929sec preferred_lft 4929sec
    inet6 2001:b07:5d2e:58c7::2000/128 scope global dynamic noprefixroute
       valid_lft 4932sec preferred_lft 2232sec
    inet6 2001:b07:5d2e:58c7:84b2:3297:aa4c:135a/64 scope global temporary dynamic
       valid_lft 86267sec preferred_lft 14267sec
    inet6 2001:b07:5d2e:58c7:f1c5:2ef7:e567:afd2/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 86267sec preferred_lft 14267sec
    inet6 fe80::4470:3f96:5d7c:54d0/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

However I can't ping the router (2001:b07:5d2e:58c7::1) from the laptop: there is no reply to ping. This is pretty strange as there are two interfaces with IP addresses on the same network and they communicate.
I am specifically blaming the fact that the 6rd assigned network is a /64 because if I misconfigure it as a /63 then router and laptop can communicate with the addresses assigned by radvd, but of course the 6rd tunnel does not work.
This is somehow similar to https://github.com/opnsense/core/issues/2663, but a lot of things changed since OPNsense 18.7. I don't know if this ever worked with OPNsense, but it is reported working with pfSense.

If I remove the inet6 address from the wan_stf interface like this:
ifconfig wan_stf inet6 2001:b07:5d2e:58c7:: -alias

the router <-> laptop communication starts working immediately, so I think the wan_stf interface is interfering with the traffic what should go to the LAN interface.
Needless to say that that the 6rd tunnel stops working when I do this, but at least we're sure that on the LAN side everything is configured correctly.

I created a script in /usr/local/etc/rc.syshook.d/start/ which automates this after a reboot, it also gives the wan_stf a ULA which you can use to ping the router from other devices, however the router cannot access the internet unless you explicitly use the LAN interface/address
script 55-fix-6rd (must be executable):
#!/bin/sh

echo "+------------------------------+"
echo "|                              |"
echo "| Fixing 6rd.................. |"
echo "|                              |"
echo "+------------------------------+"

BAD_IP="$(/sbin/ifconfig wan_stf | /usr/bin/sed -n '/.inet6 /{s///;s/ .*//;p;}')"
RANDOM_ULA="$(echo fd`openssl rand -hex 7`: | /usr/bin/sed 's/.\{4\}/&:/g')"
/sbin/route add -inet6 default -interface wan_stf
/sbin/ifconfig wan_stf inet6 $BAD_IP -alias
/sbin/ifconfig wan_stf inet6 $RANDOM_ULA/64 alias

echo "+------------------------------+"
echo "|                              |"
echo "| Done fixing 6rd............. |"
echo "|                              |"
echo "+------------------------------+"

Hope this helps and maybe Fastweb will give us more than just a single /64 some day. :wink:

Thanks, that's an interesting workaround. Way better than nothing, however there has to be a better way, as it works flawlessly with pfSense 2.3.5 (the latest version supporting i386 hardware). I couldn't test with newer releases but it's not reported as broken AFAIK.

it works flawlessly with pfSense 2.3.5 (the latest version supporting i386 hardware). I couldn't test with newer releases but it's not reported as broken AFAIK.

Can confirm that it's plug and play on 2.4.5 as well, no issues.

I will close this issue if off-topic discussions continue to take place. Discuss OPNsense solutions or troubleshooting or use whatever works for you.

@fichtner thanks for chiming in. Please allow me to disagree: I think we have a bug here, and not a support request, and I think mentioning other solutions using the same underlying operating system but behaving differently is OPNsense troubleshooting. "Looking at differences" is probably the single most powerful debugging technique have, and is the basis of more advanced ones as bisecting, A/B testing and so on.
If we are here is because we have reasons to prefer OPNsense to other solutions, and are willing to allocate some time to try to make it better.
This said: yes, let's stay on topic. :)

I do not disagree that it may be a bug. I spent a lot of work to make this happen remotely two years ago. The issues that I see:

No way for a dev to test such a setup natively so we did everything remotely with brave testers.
No patches for this in FreeBSD after all these years (not just the last two), which in my opinion is done deliberately.

I'm happy to look into it, but we run with a lot of restrictions and need help to point us to the line of code that needs to be changed.
I do not believe tracking a /64 prefix through a router is going to work and prone to breakage as far as IPv6 connectivity on the router itself goes.
Cheers,
Franco

PS: I checked the code and I can see nothing obvious except that we're flying blind here with not a single log message attached, e.g.
https://github.com/opnsense/core/blob/master/src/etc/inc/interfaces.inc#L2688
That would be an easy thing to compare...

Question: if you stop tracking LAN and just add a static ULA in the configuration, then LAN should receive advertisements and if you're in luck you can reach WAN?

@fichtner I can't take down my connection at the moment, I can try over the weekend. However in my understanding ULA addressed (fd00::/8) are not meant to the routed or routable to the IPv6 Internet:

[...] Its purpose in IPv6 is analogous to IPv4 private network addressing. Unique local addresses may be used freely, without centralized registration, inside a single site or organization or spanning a limited number of sites or organizations. They are routable only within the scope of such private networks, but not in the global IPv6 Internet.

It looks like you are right. It works for routing and internal communication but not to reach the Internet from the client.
Looking at the workaround presented it forces the IPv6 traffic out the WAN interface, which means it "solves" the issue of the routing table dilemma if it should send to WAN or LAN, but it would probably also break reaching your LAN devices from the firewall itself.
If that is the approach employed by the other firewall (I am only guessing) it's not so much desirable. You can try to comment out the following, but it might need further manipulation of the system still:
https://github.com/opnsense/core/blob/50f0b15198c87fb1ac1ec4dedaa9518912db91d4/src/etc/inc/system.inc#L458
The thing is this isn't portable and related to /64 usage indeed and has other implications such as not being able to delegate more than one subnet internally or may conflict with Multi-WAN setups.

Changig the prefix length on the wan_stf interface to /128 might allow the router as well as hosts in the LAN to access the Internet. But I can't easily test this.
ifconfig wan_stf inet6 $BAD_IP -alias
ifconfig wan_stf inet6 $BAD_IP/128

This issue has been automatically timed-out (after 180 days of inactivity).
For more information about the policies for this repository,
please read https://github.com/opnsense/core/blob/master/CONTRIBUTING.md for further details.
If someone wants to step up and work on this issue,
just let us know, so we can reopen the issue and assign an owner to it.


Basic REST API

Hi,
this PR adds django-rest-framework and two REST views (for exporting badges and instructors).
When you start the development server, go to: http://<IP_ADDRESS>:8000/api/v1/ and follow links to other resources.
These websites are generated with django-rest-framework entirely for viewing purposes (it will help other developers with implementation of that API).
To-do:

throttling
YAML format output
rebuilding 'site' with API calls (PR in different repository)

Once YAML output is implemented, this PR will solve (sometimes partially):

#432 (API for badges, airports)
#454 (API for badges, YAML for exporting badges from /workshops/export/badges)
#455 (API for airports, YAML for exporting instructors from /workshops/export/instructors)

This PR leaves missing:

API for workshops (#432)
YAML on the export badges page (#454)
YAML on the export instructors page (#455)

UPDATE: this PR solves #454. It also solves #455.

@rgaiacs can you please review?  I'm still network-challenged.

can you please review?

@gvwilson Yes, I'm doing it right now. Feel free to re-assignee this pull request to me.

@pbanaszkiewicz When I follow

When you start the development server, go to: http://<IP_ADDRESS>:8000/api/v1/ and follow links to other resources.

I get
NoReverseMatch at /api/v1/

Reverse for 'export-badges' with arguments '()' and keyword arguments '{}' not found. 0 pattern(s) tried: []

Request Method: 	GET
Request URL: 	http://<IP_ADDRESS>:8000/api/v1/
Django Version: 	1.8.3
Exception Type: 	NoReverseMatch
Exception Value:

Reverse for 'export-badges' with arguments '()' and keyword arguments '{}' not found. 0 pattern(s) tried: []

Exception Location: 	/usr/local/lib/python3.4/dist-packages/django/core/urlresolvers.py in _reverse_with_prefix, line 496
Python Executable: 	/usr/bin/python3
Python Version: 	3.4.3
Python Path:

['/home/raniere/software-carpentry/amy',
 '/usr/local/lib/python3.4/dist-packages/Tinkerer-1.4.2-py3.4.egg',
 '/usr/local/lib/python3.4/dist-packages/pyquery-1.2.9-py3.4.egg',
 '/usr/local/lib/python3.4/dist-packages/Babel-1.3-py3.4.egg',
 '/usr/local/lib/python3.4/dist-packages/Sphinx-1.3.1-py3.4.egg',
 '/usr/local/lib/python3.4/dist-packages/Jinja2-2.7.3-py3.4.egg',
 '/usr/local/lib/python3.4/dist-packages/cssselect-0.9.1-py3.4.egg',
 '/usr/local/lib/python3.4/dist-packages/sphinx_rtd_theme-0.1.8-py3.4.egg',
 '/usr/local/lib/python3.4/dist-packages/alabaster-0.7.4-py3.4.egg',
 '/usr/local/lib/python3.4/dist-packages/snowballstemmer-1.2.0-py3.4.egg',
 '/usr/local/lib/python3.4/dist-packages/docutils-0.12-py3.4.egg',
 '/usr/local/lib/python3.4/dist-packages/Pygments-2.0.2-py3.4.egg',
 '/usr/lib/python3/dist-packages',
 '/home/raniere/src/perprof-py',
 '/usr/lib/python3.4',
 '/usr/lib/python3.4/plat-x86_64-linux-gnu',
 '/usr/lib/python3.4/lib-dynload',
 '/usr/local/lib/python3.4/dist-packages']

Environment:

Request Method: GET
Request URL: http://<IP_ADDRESS>:8000/api/v1/

Django Version: 1.8.3
Python Version: 3.4.3
Installed Applications:
('django.contrib.auth',
 'django.contrib.contenttypes',
 'django.contrib.sessions',
 'django.contrib.messages',
 'django.contrib.staticfiles',
 'workshops',
 'crispy_forms',
 'selectable',
 'django_countries',
 'django_filters',
 'reversion',
 'rest_framework',
 'api')
Installed Middleware:
('reversion.middleware.RevisionMiddleware',
 'django.contrib.sessions.middleware.SessionMiddleware',
 'django.middleware.common.CommonMiddleware',
 'django.middleware.csrf.CsrfViewMiddleware',
 'django.contrib.auth.middleware.AuthenticationMiddleware',
 'django.contrib.auth.middleware.SessionAuthenticationMiddleware',
 'django.contrib.messages.middleware.MessageMiddleware',
 'django.middleware.clickjacking.XFrameOptionsMiddleware')

Traceback:
File "/usr/local/lib/python3.4/dist-packages/django/core/handlers/base.py" in get_response
  132.                     response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/usr/local/lib/python3.4/dist-packages/django/views/decorators/csrf.py" in wrapped_view
  58.         return view_func(*args, **kwargs)
File "/usr/local/lib/python3.4/dist-packages/django/views/generic/base.py" in view
  71.             return self.dispatch(request, *args, **kwargs)
File "/usr/local/lib/python3.4/dist-packages/rest_framework/views.py" in dispatch
  464.             response = self.handle_exception(exc)
File "/usr/local/lib/python3.4/dist-packages/rest_framework/views.py" in dispatch
  461.             response = handler(request, *args, **kwargs)
File "/home/raniere/software-carpentry/amy/api/views.py" in get
  18.                                      format=format),
File "/usr/local/lib/python3.4/dist-packages/rest_framework/reverse.py" in reverse
  51.         url = _reverse(viewname, args, kwargs, request, format, **extra)
File "/usr/local/lib/python3.4/dist-packages/rest_framework/reverse.py" in _reverse
  64.     url = django_reverse(viewname, args=args, kwargs=kwargs, **extra)
File "/usr/local/lib/python3.4/dist-packages/django/core/urlresolvers.py" in reverse
  579.     return force_text(iri_to_uri(resolver._reverse_with_prefix(view, prefix, *args, **kwargs)))
File "/usr/local/lib/python3.4/dist-packages/django/core/urlresolvers.py" in _reverse_with_prefix
  496.                              (lookup_view_s, args, kwargs, len(patterns), patterns))

Exception Type: NoReverseMatch at /api/v1/
Exception Value: Reverse for 'export-badges' with arguments '()' and keyword arguments '{}' not found. 0 pattern(s) tried: []

@rgaiacs fixed.

@pbanaszkiewicz This looks good to me. :+1: to merge.

Thanks, @rgaiacs. I'll add some tests to the mix and then merge.


Decrease save/load payload sizes

From the forum: A user had a problem with loading larger project files when antivirus was scanning the project during upload. Upon further investigation with the network utilities, the user noted that the blocks files were including whitespace and that they were not being compressed in any way during transit. I will note that we also are not stripping extraneous whitespace on the server either. For long chains of blocks, this whitespace creates unnecessary costs in terms of storage and transit.
We should investigate removing the whitespace and/or enabling GZIP compression with GWT RPCs to reduce the amount of traffic used by App Inventor.

I think this can be done in three parts:

[ ] Use the XML serializer that doesn't pretty-print the XML. This reduces the amount of whitespace characters sent between server and client
[ ] New servlet to handle HTTP PUT semantics for sending project resources
[ ] New servlet (possibly the same as above) to allow HTTP GET of project resources that can take advantage of native gzip compression in the browser.

@ewpatton How do we differentiate Dev mode vs prod mode on UI when saving a project right now or it needs to be added?

The first thing to check is whether goog.DEBUG is defined/true in RAW mode versus SIMPLE mode. That would be the easiest to key off of since the XML generation is all done in Blockly/blocklyeditor, and that's compiled by Google Closure Compiler.

Goog.DEBUG is not defined by the mode. It is false when in both RAW/SIMPLE mode.

Downloaded latest plovr.jar.
put the following code in plovrConfig.js"define": {
"goog.DEBUG": true
},
set mode to "SIMPLE" in plovrConfig.js.
Got a compilation error complaining about illegal initialization of @define of goog.define('goog.DISALLOW_TEST_ONLY_CODE', COMPILED && !goog.DEBUG) (this hsould have already been fixed in latest clousre library) in base.js. Commented out that line. I was able to redefine goog.DEBUG and use it to generate dev mode and prod mode code.  So in short, we need to upgrade plovr and closure library in order to redefine goog.DEBUG in compile time and take advantage of it to generate code for different modes.


Islandora link headers grow unbounded

Every time we add an entity reference to a node, we get another link header (Subjects, Resource Type, Genre, Contributor -- anything referencing a taxonomy term).  This overall makes sense, but means the link headers can grow unbounded and potentially run into external limits.  Once we had our metadata application profile in place and started testing nodes, we ran into header buffer size limits in NGINX and started getting HTTP 502 Bad Gateway errors.  The limits are easily upped, but the headers can still grow.
Link: <http://purl.org/coar/resource_type/c_c513>; rel="tag"; title="Image"
Link: <http://future.islandora.ca/taxonomy/term/5>; rel="tag"; title="Image"
Link: <http://future.islandora.ca/taxonomy/term/27>; rel="tag"; title="Cats"
Link: <http://future.islandora.ca/taxonomy/term/28>; rel="tag"; title="Dogs"
Link: <http://future.islandora.ca/taxonomy/term/28>; rel="tag"; title="Dogs"
Link: <http://future.islandora.ca/taxonomy/term/27>; rel="tag"; title="Cats"

Islandora itself doesn't concern itself with how it's deployed, really, so this ticket is about should we have all these link headers? Do they add value?  Can we de-dup them?  How much control over them do we have in the first place?
The system functions overall, but nodes with enough entity reference that hit this limit return 502's. It is a nasty little bug to run into when you suddenly start getting 502's for one node and not another.  I'm not sure if there is an easy fix here, so this is more of a conversation starter and to make folks aware about these headers.

Hey @bseeger,
I think @kayakr has stumbled into this before as well.
So we do that to try and be as "RESTful" as possible while still conforming to web standards, but I dunno how many people (er... client softwares) are making use of it.  We use some link headers in the backend to get things into Fedora, but certainly not all.  The ones generated by your standard entity references (member or, media of, tags, etc...) don't come into play at all as far as Islandora is concerned.
I'm happy to either

Eliminate them entirely (you know how much I love :fire:)
Keep them, but push them into the message body using json:api and https://www.drupal.org/project/jsonapi_hypermedia

I'm open to other suggestions, too.  In the very least, or maybe just as a stop-gap measure, we can document the issue and suggest workarounds for nginx/apache.

Right now, it's unclear to me:

what information these links are intending to convey, and/or what is the use case for including them?
who (which module) is generating these links
where these links are configurable, if at all.

Right now, it seems the information these link headers convey is limited.  i.e. they're all tag relation (unrelated to, say, what the RDF predicate would be when relating the object to the entity).  The nature of the linked resource is not apparent to the consumer (i.e. they could be any other entity or taxonomy term.  Name, subject, copyright, type, etc).  title can be confusing, particularly (as is the case of Image in Bethany's example) when the same title is used for different resources.
It would seem ideal if they were configurable somehow.  Maybe we want to simply un-check a checkbox to turn them off entirely.  Maybe others might want to specify which taxonomies they wanted to include, or use a different rel (related, maybe), I'm not sure.

@bseeger I'm curious as to how they're getting duplicated.  Are you tagging twice or do we just have a bug there.
@birkland It's provided by the main islandora module as an attempt to provide links to relevant items in message headers.  The idea is that you'd be able to navigate the repository using just HEAD requests until you find what you want.  I don't know who's actually using it, though.  And our own backend, which I'd consider the main client / user of this feature, doesn't really use it much at all.
I think in terms of concrete steps forward, we can definitely

Investigate the duplicates and de-dupe them.  It's pretty wasteful / silly to keep them.
Figure out how to limit / restrict them

With little effort, we can only emit the headers to REST api requests and not when a user views the page in the browser
With a bit more effort, we can toggle the feature with config

But if no one really is using this at all and it's more of a nuisance than anything else, we can totally deprecate and remove it.  If we make it toggleable, and no one uses that toggle and everyone just sets it to off walks away.... then we don't actually need to maintain that code at all.

I can see why link headers are potentially useful, but it was a tricky issue to diagnose when we encountered it for the first time, and nginx has quite a low allowance by default (64 I think). See previously #1519 Islandora generates Link headers for non-repository content

@dannylamb  - I totally double tagged things.  Here's the record: http://future.islandora.ca/node/40

@dannylamb  - I totally double tagged things.  Here's the record: http://future.islandora.ca/node/40

@dannylamb points out that

The idea is that you'd be able to navigate the repository using just HEAD requests until you find what you want.

If that's the case, couldn't a REST client use the JSON-LD for a node to do the same thing? If so, would we need all those link headers at all?

@bseeger Good to know it's not a bug, just a use case that was never considered.  Didn't plan on folks tagging twice.
@mjordan Good point.  Everything we're exposing is in the jsonld already. The advantage would be that you don't have to pull down the whole record and can get by with just HEAD requests, which would be faster.  But considering this has inconvenienced more people than those who have taken advantage of the feature, frankly I don't think it's even worth it at this point.

I completely agree. I'd gladly sacrifice the link headers for more reliability, especially when we have similar functionality that doesn't have nasty side effects. Would be happy to hear alternative points of view though.

I have also recently come up against this nginx header limit being overcome by Link headers added by an entity_reference field.
I think in the short term I'm going to ask for the http_max_hdr limit to be increased on the server. Long term I suggest removing Link headers for non-Islandora objects or allowing site administrator to configure which entity types/fields are used to generate Link headers.

Workaround implemented in Islandora Workbench is to set Requests' max headers to 10,000 (from default of 100 headers).


Report 1304 "Standard Sales - Quote" FormatDocumentFields

Please add a new publisher event in the report 1304 "Standard Sales - Quote":
local procedure FormatDocumentFields(SalesHeader: Record "Sales eader")
begin
        with SalesHeader do begin
            FormatDocument.SetTotalLabels(GetCurrencySymbol, TotalText, TotalInclVATText, TotalExclVATText);
            FormatDocument.SetSalesPerson(SalespersonPurchaser, "Salesperson Code", SalesPersonText);
            FormatDocument.SetPaymentTerms(PaymentTerms, "Payment Terms Code", "Language Code");
            FormatDocument.SetPaymentMethod(PaymentMethod, "Payment Method Code", "Language Code");
            FormatDocument.SetShipmentMethod(ShipmentMethod, "Shipment Method Code", "Language Code");
        **_OnAfterFormatDocumentFields(SalesHeader);_**
    end;
end;

Definition:
[IntegrationEvent(false, false)]
local procedure OnAfterFormatDocumentFields(var SalesHeader: Record "Sales eader")
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 46955.


Default Components folder will be created at init time (#340)

Description

Dapr init will create a components folder under homedir/.dapr
Dapr run will use this unless specified by --components-path
Dapr uninstall will delete the default components folder

Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #340
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[ *] Code compiles correctly
[ *] Created/updated tests
[ *] Extended the documentation

We need to issue a docs update in the docs and samples repos that explain this new behavior.

We need to issue a docs update in the docs and samples repos that explain this new behavior.

I have these PRs open:
https://github.com/dapr/samples/pull/228
https://github.com/dapr/docs/pull/621


[CS] NFC: Store ContextualTypeInfo in SyntacticElementTarget

Move the contextual type locator onto ContextualTypeInfo, and consolidate the separate fields in SyntacticElementTarget into storing a ContextualTypeInfo. This then lets us plumb down the locator for the branch contextual type of an if/switch expression from the initial constraint generation, rather than introducing it later. This should be NFC.

@swift-ci please test


Translation: "GetMyIP" or "Get My IP"

Report a problem with a translation
@Timthreetwelve
In Translation strings you use "Get My IP" when the app name is "GetMyIP".
What's the raeson to use "Get My IP" in translation strings?
Contribute a translation
I believe that in translation strings "Get My IP" should be "GetMyIP" (when it's related to the app).

If this is a contribution, enter the language name and code
Italian (it-IT)
If you wish to have your contribution acknowledged
bovirus

@bovirus, in my mind the application is named Get My IP. I have been diligent in referring to the application as Get My IP in the documentation, and in any part on the UI that displays the name.
The exceptions are the GitHub repo name and the namespaces, which do not allow spaces, and the executable file names.
Upon review, I see that GetMyIP was used as the application name in the Languages\Strings.xx-XX.xaml files, which I will be happy to update.
Thanks for bringing this to my attention.
Tim

All of the language files now use Get My IP for the application name.
I also found one instance in the Readme.txt file.
Thanks again,
Tim


Multiple definition of %i in parseArgs

We use %i inside a for-loop which is inside a for-loop that uses %i:
https://github.com/Areloch/Torque3D/blob/BaseGameTemplate/Templates/BaseGame/game/core/parseArgs.cs#L231

Ah, my bad this was intentional.. And horrible..


Create IR structs, and merge functions for IRs.

What type of PR is this?
/kind feature
What this PR does / why we need it:
Add structures needed to support translation of extension features.
Which issue(s) this PR fixes:

Fixes #125
Does this PR introduce a user-facing change?:

None

/assign @LiorLieberman

Thanks for all the work on this @sawsa307 and also to @LiorLieberman for the great reviews!
/lgtm
/approve
(For future readers, most of my review for this work was actually on #185.)


ARROW-9266: [Python][Packaging] Enable S3 support in macOS wheels

Depends on #8304

@github-actions crossbow submit wheel-osx-mavericks-cp36m wheel-osx-high-sierra-cp36m

@github-actions crossbow submit wheel-osx-*

@github-actions crossbow submit wheel-osx-*

@kszucs please rebase

@github-actions crossbow submit wheel-osx-*

@github-actions crossbow submit wheel-osx-*

@github-actions crossbow submit wheel-osx-*

The successful builds take between ~42-45 minutes but occasionally it exceeds the 50m build time limit. Sadly we can't utilize travis' build cache since crossbow always creates new branches and the fallback default branch won't have any cache entries.

@github-actions crossbow submit wheel-osx-mavericks-cp38

The successful builds take between ~42-45 minutes but occasionally it exceeds the 50m build time limit. Sadly we can't utilize travis' build cache since crossbow always creates new branches and the fallback default branch won't have any cache entries.

Does this explain why some of the nightly builds seem to be intermittently missing certain macOS wheels?  E.g., sometimes for example there's no cp38 wheel, only for that wheel to come back with the next nightly publish.

Sadly we can't utilize travis' build cache since crossbow always creates new branches and the fallback default branch won't have any cache entries.

We could run something on master on the crossbow repo to warm the cache.

I think @nealrichardson is right: my understanding is that travis caching will try to pull from default branch if no cache is available for current branch, so the warming strategy could work.

Sadly we can't utilize travis' build cache since crossbow always creates new branches and the fallback default branch won't have any cache entries.

We could run something on master on the crossbow repo to warm the cache.

We would need to merge the latests tasks (multiple .travis.yml files) generated by crossbow to master automatically which would be rather complicated. Crossbow also creates diverged branches from master at the moment.

Does this explain why some of the nightly builds seem to be intermittently missing certain macOS wheels? E.g., sometimes for example there's no cp38 wheel, only for that wheel to come back with the next nightly publish.

Could you send me build links? I don't entirely see your question.


Is it possible to use further filters?

Is it possible to use further filters? It would be brilliant to be able to filter by date or by string matches of the text column (e.g. all comments that contain the word pushshift).
If not, is there an efficient way to work around this? Ideally, I would like to work with the full dumps -- the whole time range and all subreddits --, but having little experience with 'big data', I find processing the sheer amount of data very hard.
Thanks a lot for this tool btw. I just tried it for the first time, but it seems very promising :)

I've added some filters for score and date, it's been on my TODO list for a while. What issues are you running in to, are they disk space or speed? Maybe what you want can be achieved with flags rather than additional filters?
I'm also open to pull requests that add regex filters on title and text bodies.

I've added some filters for score and date, it's been on my TODO list for a while.

Cool, that's great, thanks!

What issues are you running in to, are they disk space or speed?

Good question. I'm still a bit lost, and both aspects are a challenge to me. Ideally, I need to parse the complete dumps and extract/process all comments that contain specific words. Preferably across all subreddits or at least across a subset of maybe 100 mid-size subreddits.
I previously used the Pushshift API via praw to download the data, but given the vast volume it's pretty slow. This is why I thought processing the dumps would be better.
Turns out that this is challenging too, though. I have an M1 Macbook and I could put everything on a large external disk, but from what I have seen so far (converted 2021-06 as a pilot), putting everything in an SQL database using your tool would create a huge database plus processing would take ages.
I guess another option is to do all of this on a VM (e.g. Google Cloud) to use lots of CPUs, but then I need a giant disk and upload everything. Do you happen to have advice?

Maybe what you want can be achieved with flags rather than additional filters?

What do you mean by flags?

I'm also open to pull requests that add regex filters on title and text bodies.

I know zero Rust, unfortunately, so can't help there :/

--unsafe-mode will greatly speed up database creation by disabling a lot of the data integrity features of sqlite. The drawback is that interrupting the import will almost certainly result in a corrupt database file. This usually isn't an issue if you are starting from scratch anyways. You just start over.
--disable-fts skips the FTS table creation and population during import. This also speeds up the import process. You can create your own FTS tables by hand after the import completes.
Combining both flags, I have been able to create a sqlite database in < 36 hours. The final size of the database is between 3.5-4 TB.

Thanks for this information!

--unsafe-mode will greatly speed up database creation by disabling a lot of the data integrity features of sqlite. The drawback is that interrupting the import will almost certainly result in a corrupt database file. This usually isn't an issue if you are starting from scratch anyways. You just start over.

Cool, I'll try.
Plus this suggests that in the 'safe mode' one can just re-run the DB creation command if interrupted and it will pick up from where it ended?

--disable-fts skips the FTS table creation and population during import. This also speeds up the import process and results in a smaller file. The drawback here is that without FTS you can't run queries like SELECT * FROM comment_fts WHERE body MATCH 'snoo' quickly. Searches will for submissions or comments with a given word require a full table scan every time. With that said, you can create your own FTS tables by hand after the import completes.

So this means that without FTS queries would be much slower, right?
The thing is that the columns that are part of the FTS table don't contain all the information I need (e.g. created_utc). Is there a way of quickly joining the info from the non-FTS columns with the results? If not, the current FTS table wouldn't be very useful for me anyway.

Combining both flags, I have been able to create a sqlite database in < 36 hours. The final size of the database is between 3.5-4 TB.

An SQLite database of the complete dumps? Wow, that's impressive. That would certainly be feasible both in terms of processing time and disk usage. Were you using a "normal" laptop/desktop or was this using 100 CPUs and 1 TB RAM on the cloud? 😉

Plus this suggests that in the 'safe mode', one can just re-run the DB creation command if interrupted, and it would more or less pick up from where it ended?

The importer will try to ingest all of the files in the input directory, but if the contents are already the DB, no changes will be made.

So this means that without FTS, queries would be much slower, right? Still quick enough to be manageable?

Much slower. I couldn't say how long a text search would take, I haven't tried it yet. If you limit by some field such as author or subreddit you can probably make significant performance improvements by adding an index on that field. For example I created an index on subreddit in my DB (which took some time) and ran this query:
sqlite> .timer on
sqlite> SELECT COUNT(*) FROM comment WHERE subreddit = 'pushshift' AND body LIKE '%cool%';
75
Run Time: real 110.155 user 0.126618 sys 0.588360

So, a text search with an index and without FTS took about 2 minutes on a small subreddit. This would probably be much faster on a SSD, but I don't have one large enough.

The thing is that the columns that are part of the FTS table don't contain all the information I need (e.g. created_utc). Is there a way to quickly join the non-FTS columns' info with the results? If not, the current FTS table wouldn't be very useful for me anyway.

As you suggest, you can use a join. eg for comments:
SELECT comment.created_utc
FROM comment_fts
JOIN comment ON comment_fts.rowid = comment.id
WHERE comment_fts.body MATCH 'foo';

An SQLite database of the complete dumps? Wow, that's impressive. That would certainly be feasible both in terms of processing time and disk usage. Were you using a "normal" laptop/desktop or was this using 100 CPUs and 1 TB RAM on the cloud? So would you recommend I do this on my local machine using a big external hard disk rather than on a cloud VM?

This was done on a desktop computer with an AMD Ryzen 7 2700X CPU with 64 GB of memory on a spinning disk drive. An import should be possible on an M1 given enough disk space. A VM in the cloud could work as well, though you might want to be mindful of egress costs if you want to export that DB.

Finally, you don't plan on sharing the resulting DB, do you? There has been some interest in this on the Pushshift subreddit. It's not only me, I think :)

I'll consider it. I'm not sure if my ISP would appreciate that kind of upload usage.

Thanks a lot, that's very helpful!

So this means that without FTS, queries would be much slower, right? Still quick enough to be manageable?

Much slower. I couldn't say how long a text search would take, I haven't tried it yet. If you limit by some field such as author or subreddit you can probably make significant performance improvements by adding an index on that field. For example I created an index on subreddit in my DB (which took some time) and ran this query:
sqlite> .timer on
sqlite> SELECT COUNT(*) FROM comment WHERE subreddit = 'pushshift' AND body LIKE '%cool%';
75
Run Time: real 110.155 user 0.126618 sys 0.588360

So, a text search with an index and without FTS took about 2 minutes on a small subreddit. This would probably be much faster on a SSD, but I don't have one large enough.

Good to know, thanks!

The thing is that the columns that are part of the FTS table don't contain all the information I need (e.g. created_utc). Is there a way to quickly join the non-FTS columns' info with the results? If not, the current FTS table wouldn't be very useful for me anyway.

As you suggest, you can use a join. eg for comments:
SELECT comment.created_utc
FROM comment_fts
JOIN comment ON comment_fts.rowid = comment.id
WHERE comment_fts.body MATCH 'foo';

An SQLite database of the complete dumps? Wow, that's impressive. That would certainly be feasible both in terms of processing time and disk usage. Were you using a "normal" laptop/desktop or was this using 100 CPUs and 1 TB RAM on the cloud? So would you recommend I do this on my local machine using a big external hard disk rather than on a cloud VM?

This was done on a desktop computer with an AMD Ryzen 7 2700X CPU with 64 GB of memory on a spinning disk drive. An import should be possible on an M1 given enough disk space. A VM in the cloud could work as well, though you might want to be mindful of egress costs if you want to export that DB.

Finally, you don't plan on sharing the resulting DB, do you? There has been some interest in this on the Pushshift subreddit. It's not only me, I think :)

I'll consider it. I'm not sure if my ISP would appreciate that kind of upload usage.

I have just written code to execute this complete pipeline on Google Colab ( download dumps, extract them to a database and filter by keyword, and then download the result as csv files ), see here: reddit_keywords .
I had to treat Pushshift-Importer as a black box in my code, but it would be really nice to have regex filters as built-in features.
By the way, queries with a MATCH operator like SELECT * FROM comment_fts WHERE body MATCH 'snoo' did not work for me. I had to write my queries with LIKE.

By the way, queries with a MATCH operator like SELECT * FROM comment_fts WHERE body MATCH 'snoo' did not work for me. I had to write my queries with LIKE.

I had to disable building FTS by default. Without filters it can take a very long time to build the database. FTS can be enable with --enable-fts

I had to treat Pushshift-Importer as a black box in my code, but it would be really nice to have regex filters as built-in features.

It might be some time before I can implement this. I'm happy to review PRs.


Host build pipeline prototype for use in the authorized nodes

Until we roll out a more robust build pipeline, we need the build pipeline prototype to be setup so every authorized node we run can use it. This has to be setup in the easiest fashion possible, since it will have to be replaced in one of the follow-up 0.x releases.
This tutorial contains the instructions for the prototype: https://github.com/pyrsia/pyrsia/blob/main/docs/tutorials/build_from_source.md#run-build-pipeline-prototype with these changes:

the script to pull docker images needs to be tweaked so it uses an authenticated call to Docker Hub to prevent API limits
the Java part can be skipped in this issue. A follow-up issue for milestone 0.3 will be created.

Our authorized nodes need to be configured to use this build pipeline prototype using --pipeline-service-endpoint - see https://github.com/pyrsia/pyrsia/blob/main/docs/tutorials/build_from_source.md#run-build-pipeline-prototype for more information.

@sbtaylor15 I assigned this to you, since I think you have already started (or even finished?) this.

I think we can close this now?


⚠ Bofrost.es has degraded performance

In 112636d, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1676 ms

Resolved: Bofrost.es performance has improved in 934278c after 20 minutes.


Can fine-tuned model be fine-tuned again?

In order to fine tune on a new additional dataset , could the trained model be fine-tuned without unlearning on the previous data?
Can this fine tuned model be further fined tuned on a new set of data ?

I think there is no problem to fine tune it, the data used to train this model is simple 16KHz wav.  By the way, is there any problem to train from the start?


How to update the command line of the apiserver to enable PodPreset ?

What kind of request is this (question/bug/enhancement/feature request):
Question
In order to use PodPreset, the apiserver commandline needs to be updated to include settings.k8s.io/v1alpha1=true in the --runtime-config option.
How to do that ?
Environment information

Rancher version : 2.1.7
Installation option : single install

Cluster information

Cluster type : Custom
Machine type : VM
Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.5", GitCommit:"32ac1c9073b132b8ba18aa830f46b77dcceb0723", GitTreeState:"clean", BuildDate:"2018-06-21T11:46:00Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.4", GitCommit:"c27b913fddd1a6c480c229191a087698aa92f0b1", GitTreeState:"clean", BuildDate:"2019-02-28T13:30:26Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.5", GitCommit:"32ac1c9073b132b8ba18aa830f46b77dcceb0723", GitTreeState:"clean", BuildDate:"2018-06-21T11:46:00Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.4", GitCommit:"c27b913fddd1a6c480c229191a087698aa92f0b1", GitTreeState:"clean", BuildDate:"2019-02-28T13:30:26Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

found the solution here:  https://github.com/rancher/rancher/issues/11587


Continue to adapt color temperature down to the sleep temperature after sunset

Continue to adapt color temperature down to the sleep temperature after sunset. Results in a gradually warming light during the night time rather than a fixed color temperature throughout the night time.

this looks good! Have you been testing this at home yourself for sometime?

This looks good! Have you been testing this at home yourself for sometime?

Yeap I’ve got it setup in my house across 4 zones and works like a charm. Try it out, I’ve set a 4500k max temp, 3000k minimum colour temp and a 2000 sleep temp.
See below graph. The blips are due to me switching on and off the adaptive light switch.

Have been using your integration for a few months now, this looks like a very useful addition. @basnijholt do you think you will merge this into next release?

Unfortunately, I haven't had the time to test it myself yet.
I know many people will blindly smash the update button in HACS so I am a bit careful with changing the core logic.

I understand, your point is very valid. Just want to say thanks again, been running your integration for the last few months and it is already amazing in its current form. Looking forward where you will take it in the future.

Thought to comment back- been using it and has been flawlessly since the beginning of Feb.

I really like this idea, a lot. Adaptive Lighting makes everything so smooth you never notice the lighting changes - it's just always perfect. Except when transitioning to sleep mode, which if it's a big change, can be jarring.
Some food for thought:
I use the sleep mode a bit differently than others, I think.
For most of my lights, I have a 2500K-6536K color temp range, with 25%-100% brightness range for the normal Adaptive Lighting operation.
For sleep mode, I have it set to 4500K, 1% brightness. It creates a pleasant moonlight effect, great for walking around at night after you've been sleeping, since it's barely any light - but it's a cool-ish white (like the moon). For some of my fixtures that have bulbs without diffusers, you can even get crisp shadows that look just like moonlight shadows. I love it.
My point is - the functionality in the PR seems like it kind of assumes the sleep color temp is lower (on the kelvin scale) than the min color temp, and that's not how all users use the sleep settings.

Some food for thought: I use the sleep mode a bit differently than others, I think. For most of my lights, I have a 2500K-6536K color temp range, with 25%-100% brightness range for the normal Adaptive Lighting operation. For sleep mode, I have it set to 4500K, 1% brightness. It creates a pleasant moonlight effect, great for walking around at night after you've been sleeping, since it's barely any light - but it's a cool-ish white (like the moon). For some of my fixtures that have bulbs without diffusers, you can even get crisp shadows that look just like moonlight shadows. I love it.
My point is - the functionality in the PR seems like it kind of assumes the sleep color temp is lower (on the kelvin scale) than the min color temp, and that's not how all users use the sleep settings.

Good idea! I stumbled on this effect when about a year ago I replaced my bulbs in the bathrooms with 6500K bulbs. I reset the (non-smart) dimmers to go very low. I noticed at night when I turned on the light in the bathroom to the minimum, it gave a very pleasant moonlight effect.
I am now embarking on changing as many lights as I can with DIY continuously variable CCT. At first I thought ramp down to low temps at night, but then I remembered the moonlight effect.
Not sure what the right approach would be. With the current functionality, you don't get the ramp down  (or up) to the sleep mode temp, but sleep mode itself seems to be sufficient if we're not trying to ramp to it's temp. That's sort of how I would prefer it for the moonlight effect when getting up in the middle of the night.

Any update on when this might be merged and released? Thanks!

I've added the config option adapt_until_sleep which defaults to False, as I think a major problem with this PR was changing the core logic.

We would also need some documentation on this new config option.

We would also need some documentation on this new config option.

I'm not familiar enough with this PR to provide those.

We would also need some documentation on this new config option.

I've added a general description to the README but I'm afraid I'm not familiar enough with this PR to explain it more thoroughly.

@basnijholt Hey this PR automerged. It was supposed to wait for all reviewers to approve it and the tests to pass. I'm so sorry.
It's absolutely done though, the config option is the only thing that activates it and it defaults to false.

I already wondered how this suddenly got in. Thanks for explaining and thanks for getting this over the finish line!

@all-contributors, please add @igiannakas for code

https://github.com/all-contributors please add @igiannakas for code

@all-contributors please add @igiannakas for code

Thank you for the mention 😀


pageup/pagedown doesn't work in the compose box

Easily reproduced by entering a few lines of text, going to the bottom, and hitting pageup.
This is likely a bug in our static/js/hotkey.js code.

@timabbott I would like to get further information regarding the issue. I tried reproducing it but it seemed to work fine. Hitting page up and page down works fine in the compose box on my system.

Interesting!  I'm experiencing this problem in Chrome 52 on Linux; what browser did you try?

@zulipbot claim


APEXMALHAR-2289 #resolve #comment Add resource monitor

@davidyan74 Could you review. This PR add resource monitor to monitor the system resource such as garbage collection and CPU usage to identify the benchmark issue.

@davidyan74 Applied comments, please review

Can you check all protected usages?

Also, RuntimeException has not been changed to Thowables.propagate

@davidyan74 I changed all class fields into private. But still keep some constructors and methods as protected

@brightchen  I would say make all of them private for now unless there is a subclass that needs them.

@davidyan74 changed all protected to private as your commented.


Sort eslin rules

This PR does nothing else but sorts eslint rules. So that when I start moving them into dcos/javascript it's easier to trace changes.

Confirmed with deep-equal 👍  😎


Update workflows

comment now point to knobots instead .github
use spdx identifier (we can do this now: https://github.com/knative/community/issues/970#issuecomment-1077944819)

/lgtm


Integrate clippy into github workflow

Problem
Currently there is no linter for Rust code in the project.
Details
Integrating clippy into github workflow would force developers to write clean code.
Acceptance criteria
cargo clippy should be included into build_and_test.yml.

could be related https://github.com/zkmopro/mopro/pull/245#discussion_r1820534257


[RFC] Consul Support in Dynaconf

Is your feature request related to a problem? Please describe.
We use Hashicorp consul for config management. We also have some startup configs stored in a file. Dynaconf works very well in managing local config but we have to implement another handler for consul config management
Describe the solution you'd like
A cohesive solution, an integration with consul too for fetching configs on the fly and watching for changes. Considering the popularity of consul, it will be quite useful for other folks too :)
Describe alternatives you've considered
We have a consul handler implementation but that requires managing multiple config managers in one project

In case anyone needs it, we added a custom loader to load configs from Consul. A Simple ConsulReader was made using python-consul package. Keys were fetched and loaded in obj
# Consul loader for Dynaconf
from .consul_handler import ConsulClient

def load(obj, env=None, silent=True, key=None, filename=None):
    """
    Reads and loads in to "obj" a single key or all keys from source
    :param obj: the settings instance
    :param env: settings current env (upper case) default='DEVELOPMENT'
    :param silent: if errors should raise
    :param key: if defined load a single key, else load all from `env`
    :param filename: Custom filename to load (useful for tests)
    :return: None
    """
    # Load data from your custom data source (file, database, memory etc)
    # use `obj.set(key, value)` or `obj.update(dict)` to load data
    # use `obj.logger.debug` to log your loader activities
    # use `obj.find_file('filename.ext')` to find the file in search tree
    # Return nothing

    consul_client = ConsulClient(
        host=obj.CONSUL.HOST,
        token=obj.CONSUL.TOKEN,
        root_path=obj.CONSUL.ROOT_PATH
    )
    fetch_keys = obj.CONSUL.pathlist
    data = consul_client.get_finalized_value(keys=fetch_keys, format="yaml")
    obj.update(data, loader_identifier='consulremote')

I will personally not implement or support an  embedded consul loader, I think this is better to be added as a new example/ and documentation explaining how to create new loaders and then is up to the user to add it.
It can also be offered as  a plugin.


Retirement dates are conflicted

Retirement dates are conflicted.
https://github.com/MicrosoftDocs/azure-docs/blob/49264a89513c09e30dfc39cad35d0a4305fcc866/articles/ai-services/openai/concepts/models.md?plain=1#L173
https://github.com/MicrosoftDocs/azure-docs/blob/49264a89513c09e30dfc39cad35d0a4305fcc866/articles/ai-services/openai/concepts/model-retirements.md?plain=1#L63-L64
gpt-35-turbo (0301) is retired at July 5, 2024 or June 13, 2024.
gpt-35-turbo (0613) is retired at June 13, 2024 or July 13, 2024.
Which is correct?

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

ID: 52384bbf-8e4d-a27c-cae6-2013c0097aac
Version Independent ID: 3f2d39cf-ce78-b4e3-4a91-a76217ca5c73
Content: Azure OpenAI Service model retirements - Azure OpenAI
Content Source: articles/ai-services/openai/concepts/model-retirements.md
Service: azure-ai-openai
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@ichimura
Thanks for your feedback! We will investigate and update as appropriate.

@ichimura thank you for your question. We have updated the docs internally to reflect the correct dates:

Model
Version
Retirement date

gpt-35-turbo
0301
No earlier than June 13, 2024

gpt-35-turbogpt-35-turbo-16k
0613
No earlier than July 13, 2024

This change will go-live in the en-us version of the docs later today, and will then be reflected in the localized versions of the docs over the next 1-4 weeks.

@mrbullwinkle really? Azure OpenAI Studio says 0613 retires at June 13, 2024.

@ichimura, yes unfortunately the dates in the Studio are currently still incorrect. Updating the values in Studio takes a bit longer from a perspective than updating the docs which we are able to update the same day a change is made. The Studio also still incorrectly lists 0613 as being slated for retirement prior to 0301 which came out earlier and will retire before 0613. The most up-to-date info regarding model retirement is here:
https://learn.microsoft.com/en-us/azure/ai-services/openai/concepts/model-retirements

@ichimura
Thank you for reaching out. Our PG team will promptly update the document. This thread will be closed for now. Should you have any additional questions about the documentation, please don't hesitate to tag me in your response, and we'll be more than happy to assist further.
#Please-close


Wrong intellisense popup travels with cursor

TypeScript Version: 2.9.2 and 3.0.0-dev.20180626

Search Terms:
jsx props intellisense moves with cursor
Code
import Table from 'antd/lib/table'
//...
render() {
  return (
    <Table.Column render={(){/*<- cursor between braces*/}}/>
  )
}

Expected behavior:
Expected is that intellisense popup disappears.
Actual behavior:

last screen is ctrl+space invoked on render so that two(three) popups are now visible
Playground Link:
https://github.com/ackvf/typescript-repro/tree/render-prop
Related Issues:
https://github.com/Microsoft/TypeScript/issues/25265

this looks like a duplicate of #25265 or at least the same underlying cause.

Ok, I was not sure that the ghost popup is really tied to the same cause, so I created two issues.


Terminal remains blank when # visible lines > terminal.integrated.scrollback

VSCode Version: Code - Insiders 1.15.0-insider (211ffdf184329179ddca9c1fe993f5f11f3c4dda, 2017-08-02T05:07:49.324Z)
OS Version: Darwin x64 16.6.0
Extensions: none

Verifying #19193
Steps to Reproduce:

terminal.integrated.scrollback: 10
Open new terminal with more than 10 visible lines
Remains blank
Reload
Opens fine
Make it show <= 10 lines in viewport
Close terminal and reopen
Opens fine

@chrmarti
@Tyriar
FYI
Just reproduce the same behavior on Windows 7/cmd.exe

This was meant to be fixed via https://github.com/sourcelair/xterm.js/pull/750

This should be fixed in latest. Also I'm preventing negative values in https://github.com/sourcelair/xterm.js/issues/911


Table size in Reading mode

I’m not sure this is a bug, but I can not get the table I’ve created to appear in Minimal in the same proportion as the normal Obsidian Theme. I’ve tried making changes to the settings UI for tables.

This is the default styling for tables in Minimal, they always appear full width
i can look into adding a CSS class to override

One more Toggle 😉

Hi. I'm not sure if this is exactly the same question, but it's related to the "Table size in Reading mode". I've a doubt about width  on "standard" tables (compared to dataview tables). On edit mode (with live preview), both use the entire "text space", as You see below (first table is dataview, second is default table).

But when You switch to preview mode, default tables not use this space:

I checked the tables options, but changing the default width only apply to edit mode, and the width is too large ("overflow" the text)

Is there any option to force that default tables works as dataview tables and full the entire "text space"?
Thanks a lot for your works and congratulations for the theme!
Best regards.

This was fixed in 6.0 you can use Style Settings > Table > Maximize table width


Сompatible TreeChop

Is it possible that Chainsaw enchantment is compatible with the TreeChop mod?
Apotheosis-1.20.1-7.0.5
TreeChop-1.20.1-forge-0.18.3
or is the compatibility problem on the side of the developers of the TreeChop mod?

The chainsaw enchantment is fundamentally incompatible with how that mod works. Chainsaw attempts to walk the tree and break the entire log structure on block break, but that mod prevents the block from actually being broken.
If TreeChop wanted to add compat they could potentially make it so having a chainsaw-enchanted axe would immediately break the tree, but this is not functionality I can add.


Added support for capturing customized settings for Synthesis and Implementation and a small bugfix

This pull request adds support for capturing synthesis and implementation settings that differ from Vivado defaults and fixed support for Block Designs with IPs that create their own BD such as Xilinx's MIPI CSI-2 Rx Subsystem.

I cherry picked defaults-fix instead of using the merge commit, and fast forwarded v2020.1, in order to preserve some semblance of linear history.


fix: added onClose on cancel event

Indeed, the @cancel event is on the address-form component of the App (not in ShopInvader)


also three finger dragging doesn't select text, only drags windows

The three fingers drag should work whatever you drag over text or a windows title bar. Maybe the text you are trying to select is into a UWP application (#2), that is not supported yet.
You should be able to select text into the path field in explorer, or text in firefox or chrome.


Stake Pool meta-data fields (ticker/name, and list of IPs)

Hello! Just have a couple of questions about specifics of the pool meta-data entries from the delegation design spec:
https://github.com/input-output-hk/fm-ledger-rules/blob/master/docs/delegation_design_spec/delegation_design_spec.tex#L2256-L2274

Is that right that "ticker" and "name" are not validated in any way and there's no rule implied that would enforce uniqueness for this? So it's possible to create multiple pools with the same name and ticker, right? I understand all the reasons why it would work like this, just want to explicitly clarify this fact )

What is the purpose for the list of IP addresses and\or domain names? Is it supposed to be used for discovery/validation in any way? Because I would expect it to be a valid case when a block signed by a valid pool can be broadcasted from any node in the network, and IP wouldn't matter.

Thank you!

I just see the section about the relay IPs removed from the spec. Is the idea still the same?

From discussions it seems that ticker and name will be validated according to the char-length specified next to them: 3-5 chars for a ticker and up to 50 chars name. I guess that for all other fields it is combined size limit of 512 bytes minus ticker and name. So e.g. the shorter is your URL - the more tags you can add, etc.

It seems that list of IPs still serves the same point with the same idea. No auto-validation, but people can check it manually.


What would it take to support tiled routing graphs?

Hey! I'm the maintainer of Headway, a self-hostable maps stack. I'm thinking about taking the project in a direction that would allow instances to link together in a federated network that could grow to cover the planet. Doing so presents a number of challenges though. From the routing side of things, an end-user can't simply send a routing query including route endpoints to an untrusted server, because of the privacy implications. Nor can it download a routing graph for the entire planet. Valhalla handles this by dividing up the routing graph into tiles. Do you know if an approach like that could work with fast_paths? If so, what would need to change?
Compiling Valhalla to webassembly seems extremely difficult, and I'd like to evaluate building turn-by-turn on top of fast_paths instead. I'm not sure which would end up being more difficult since both of these ideas sound ridiculously complex, but this option involves less CMake at least and I want to explore it a bit.

After reading through some of the valhalla source code I've convinced myself I don't want to try and build this from scratch. Still puzzled as to how best to do offline routing for web clients.

I actually had a breakthrough with Valhalla and I think I will be able to get it to build, so closing this for now. I think it's probably best that I don't try to build any of these pieces from scratch, because whatever I can throw together by myself will be way worse than what's already out there. :)

:+1: For a tiled approach I think Valhalla should be a good choice.