altInput breaks defaultDate

as soon as altInput = true, the defaultDate doesn't get displayed anymore and the picker opens on the current date, not the defaultDate.

the data supplied to flatpickr is the date-stamp to the right (which corresponds to 2009-05-28).
the defaultDate is not displayed in the input field and the flatpickr opens with the current date
this is how the component is used in the code:

<Flatpickr v-model="Store.mainObj.datum"
	:options="{ defaultDate:Store.mainObj.stamp,
		altFormat:'d.m.Y',
		altInput: true,
		shorthandCurrentMonth:true }"/>

removing altInput: true fixes it, but leaves me with a wrong format.

flatpickr version used: 2.4.3
Browser name and version: any browser
vue: 2.2.1
OS and version: macos 10.10.5

Hello,
Could you please check if this issue is also present in the latest release?
https://jsfiddle.net/aj6k3f1v/
Thank you :+1:

Checked with npm v 2.4.8 and the problem still remains
Am 6. April 2017 um 22:17:36, Gregory (notifications<EMAIL_ADDRESS>schrieb:
Hello,
Could you please check if this issue is also present in the latest release?
https://jsfiddle.net/aj6k3f1v/
Thank you 👍
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/chmln/flatpickr/issues/737#issuecomment-292303631, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACMVEOWDQ7s_JuYZBIjYFYgJXoV73RWpks5rtUhbgaJpZM4M2G4U.

@didamaran you can't use altInput without setting up the dateFormat value. Try to set the dateFormat: Y-m-d and only then use altInput: true, altFormat: d.m.Y. This should help.
https://jsfiddle.net/LLppa1h0/

I'm sorry to say that this doesn't do the trick.
changed my code to
<Flatpickr v-model="Store.mainObj.mydate"
:options="{ defaultDate: Store.mainObj.mydate,
	dateFormat: 'Y-m-d',
	altInput: true,
	altFormat: 'd.m.Y' }"/>

feeding it with a date in Y-m-d format or as a date stamp, but the problem still persists.

Could not reproduce it on a fiddle
https://jsfiddle.net/chmln/6pyajLga/

@didamaran make sure your Store.mainObj.mydate is not null/undefined or has different format. Also, you may have difficulties with flatpickr because flatpickr is loading earlier, then the Store.mainObj.mydate value becomes accessible or whatever.

so @JamesJGoodwin is probably right and it's due to the component lifecycle


Fix required many widget parameters when extracted a widget

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

I'm using a parameter from a statefulwidget , here's my widget that i've extracted that led to that

                    GestureDetector(
                      onTap: () {
                        isSubCategoryClicked.value = false;
                      },
                      child: Flexible(
                        child: Visibility(
                            visible: isClicked.value &&
                                !isPicking &&
                                !isNearbyClicked.value,
                            child: widget.categoryName.isNotEmpty
                                ? Container(
                                    height: 110,
                                    width:
                                        MediaQuery.of(context).size.width * 0.5,
                                    child: ListView.separated(
                                        itemCount: widget
                                            .categoryName[category.value]
                                            .sub_categories
                                            .length,
                                        scrollDirection: Axis.horizontal,
                                        separatorBuilder: (context, index) =>
                                            SizedBox(
                                              width: 10,
                                            ),
                                        padding: EdgeInsets.only(left: 10),
                                        itemBuilder: (context, index) {
                                          final int subCatLength =
                                              subCatsCloned.value.length;
                                          return GestureDetector(
                                            onTap: () {
                                              subCatIndex.value = index;
                                              isSubCategoryClicked.value = true;

                                              if (isSubCategoryClicked.value) {
                                                subCatsCloned.value = [
                                                  ...widget
                                                      .categoryName[
                                                          category.value]
                                                      .sub_categories
                                                ];
                                                subCatsCloned.value.removeAt(
                                                    subCatIndex.value);
                                                subCatsCloned.value.add(widget
                                                        .categoryName[
                                                            category.value]
                                                        .sub_categories[
                                                    subCatIndex.value]);
                                              }
                                            },
                                            child: AnimatedAlign(
                                              duration:
                                                  Duration(milliseconds: 200),
                                              curve: Curves.easeIn,
                                              alignment: Alignment.centerLeft,
                                              widthFactor:
                                                  isSubCategoryClicked.value
                                                      ? 0.1
                                                      : 1,
                                              child: Column(
                                                children: [
                                                  Container(
                                                      decoration: BoxDecoration(
                                                        border: Border.all(
                                                          color: Colors.black,
                                                        ),
                                                        borderRadius:
                                                            BorderRadius
                                                                .circular(100),
                                                      ),
                                                      child: CircleAvatar(
                                                          radius: 40,
                                                          backgroundColor:
                                                              Colors.white,
                                                          child:
                                                              CachedNetworkImage(
                                                            imageUrl: isSubCategoryClicked
                                                                    .value
                                                                ? subCatsCloned
                                                                        .value[
                                                                            index]
                                                                        .image ??
                                                                    ""
                                                                : widget
                                                                        .categoryName[category
                                                                            .value]
                                                                        .sub_categories[
                                                                            index]
                                                                        .image ??
                                                                    "",
                                                            imageBuilder: (context,
                                                                    imageProvider) =>
                                                                Container(
                                                              decoration:
                                                                  BoxDecoration(
                                                                shape: BoxShape
                                                                    .circle,
                                                                image: DecorationImage(
                                                                    image:
                                                                        imageProvider,
                                                                    fit: BoxFit
                                                                        .cover),
                                                              ),
                                                            ),
                                                            placeholder: (context,
                                                                    url) =>
                                                                CircularProgressIndicator(),
                                                            errorWidget: (context,
                                                                    url,
                                                                    error) =>
                                                                Icon(Icons
                                                                    .broken_image),
                                                          ))),
                                                  Visibility(
                                                      visible: !isSubCategoryClicked
                                                              .value ||
                                                          (index ==
                                                                  subCatLength -
                                                                      1 &&
                                                              isSubCategoryClicked
                                                                  .value),
                                                      child: Text(
                                                        isSubCategoryClicked
                                                                .value
                                                            ? subCatsCloned
                                                                .value[index]
                                                                .name["en"]
                                                            : widget
                                                                .categoryName[
                                                                    category
                                                                        .value]
                                                                .sub_categories[
                                                                    index]
                                                                .name["en"],
                                                      )),
                                                ],
                                              ),
                                            ),
                                          );
                                        }),
                                  )
                                : Container()),
                      ),
                    ),

Expected results
SubCategoriesWidget(
isSubCategoryClicked: isSubCategoryClicked,
 isClicked: isClicked,
 isPicking: isPicking,
 isNearbyClicked: isNearbyClicked,
category: category,
widget:widget,
subCatsCloned: subCatsCloned,
subCatIndex: subCatIndex),

Actual results
SubCategoriesWidget(isSubCategoryClicked: isSubCategoryClicked,
 isClicked: isClicked,
 isPicking: isPicking,
 isNearbyClicked: isNearbyClicked,
 widget: widget, widget: widget,
 category: category,
 subCatsCloned: subCatsCloned,
 subCatIndex: subCatIndex,
 widget: widget,
 widget: widget,
 widget: widget,
 widget: widget),

Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[Paste your output here]

Hi @MezoPeeta. Thanks for filing this. Can you provide more information on this issue, not sure I fully get it. What are you trying to achieve? What issue are you facing? Can you also provide a minimal complete reproducible code sample that doesn’t include 3rd party plugins or complex production code ( a single main.dart file) that I can look into and reproduce the issue?
Thank you!

I'm trying to extract a lot of widgets into one
Issue is it gets too many widget parameters and it gives an error too
here's my main.dart

import 'package:flutter/material.dart';
import 'package:hooks_riverpod/hooks_riverpod.dart';
import 'package:waspha/src/utils/cache_helper.dart';

import 'src/app.dart';

void main() async {
  WidgetsFlutterBinding.ensureInitialized();

  runApp(const ProviderScope(child: MyApp()));
  await CacheHelper.init();
}

here are all packages im using
  cupertino_icons: ^1.0.2
  go_router: ^10.1.0
  flutter_hooks: ^0.20.0
  hooks_riverpod: ^2.3.8
  google_maps_flutter: ^2.4.0
  location: ^5.0.3
  freezed_annotation: ^2.4.1
  json_annotation: ^4.8.1
  dio: ^4.0.0
  flutter_svg: ^2.0.7
  otp_text_field: ^1.1.3
  cached_network_image: ^3.2.3
  bitmap: ^0.1.3
  google_fonts: ^5.1.0
  phone_form_field: ^8.1.0
  shared_preferences: ^2.2.0
  google_places_flutter: ^2.0.6
  dio_cookie_manager: ^2.0.0
  intl: ^0.18.1
  table_calendar: ^3.0.9

dev_dependencies:
  flutter_test:
    sdk: flutter

  flutter_lints: ^2.0.0
  build_runner: ^2.4.6
  freezed: ^2.4.2
  json_serializable: ^6.7.1
  riverpod_generator: ^2.2.6

Thanks for your response @MezoPeeta. For this issue to be workable we'd need you to kindly remove all 3rd party plugins or complex production code and help streamline the issue to a single main.dart file we can reproduce the issue with on our end.
Thank you!

You mean like this
import 'package:flutter/material.dart';

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

class MyApp extends StatelessWidget {
  const MyApp({super.key});
  static const String _title = 'Flutter Stateful Clicker Counter';
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: _title,
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key});
  // This widget is the home page of your application. It is stateful, meaning
  // that it has a State object (defined below) that contains fields that affect
  // how it looks.
  // This class is the configuration for the state.
  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {

  @override
  Widget build(BuildContext context) {
        return Scaffold(
        appBar: AppBar(
          title: const Text('Flutter Demo Click Counter'),
        ),
        body: GestureDetector(
          child: Flexible(
            child: Visibility(
                visible: true,
                child: widget.categoryName.isNotEmpty
                    ? Container(
                        height: 110,
                        width: MediaQuery.of(context).size.width * 0.5,
                        child: ListView.separated(
                            itemCount: widget.categoryName[category.value]
                                .sub_categories.length,
                            scrollDirection: Axis.horizontal,
                            separatorBuilder: (context, index) => SizedBox(
                                  width: 10,
                                ),
                            padding: EdgeInsets.only(left: 10),
                            itemBuilder: (context, index) {
                              return GestureDetector(
                                onTap: () {},
                                child: AnimatedAlign(
                                  duration: Duration(milliseconds: 200),
                                  curve: Curves.easeIn,
                                  alignment: Alignment.centerLeft,
                                  widthFactor: 0.1,
                                  child: Column(
                                    children: [
                                      Container(
                                          decoration: BoxDecoration(
                                            border: Border.all(
                                              color: Colors.black,
                                            ),
                                            borderRadius:
                                                BorderRadius.circular(100),
                                          ),
                                          child: CircleAvatar(
                                            radius: 40,
                                            backgroundColor: Colors.white,
                                            child: Image.asset(""),
                                          )),
                                      Visibility(
                                          visible: true, child: Text("")),
                                    ],
                                  ),
                                ),
                              );
                            }),
                      )
                    : Container()),
          ),
        ));
  }
}

@dam-ease

Thanks for your response @MezoPeeta. Yes, like this. Running this, the error is about The getter 'isNotEmpty' being called on null which seems to be expected.
Not sure I fully understand where many widget parameters need to be passed/extracted here.
For this issue to be workable, we'd need you to please help provide all the information needed for us to reproduce this on our end.
More specifically, please provide the information indicated below:

A completed and minimal reproducible code sample
The output of flutter doctor -v
Reproduction steps

Also note that if you need assistance on personal code, 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.
Thank you!


v4 - Accordion example uses v3 panel markup

http://v4-alpha.getbootstrap.com/components/collapse/#accordion-example

Just noticed this now in recent sources, 2 months later, so would be nice to see this PR merged, especially if alpha2 is imminent.
However, and without trying @kkirsche 's fix, why does the Accordion example work without any of these old or new classes?  They are only for the styling of appearance?

Hmm, apparently not just styling, some behavior too.  As it was, with no classes operative, the accordion was a single pane open at a time.  If you clicked on another group item, it expanded while closing the previously open item.  With kkirsche's fix, now you can open/close each group independently.  This is radio button vs. checkbox behavior.
There are actually two behaviors possible - does the documentation say which behavior is available, or how to get either behavior?

Duplicate of #18375.


Don't offer to upgrade tags of railway platforms with access=private

When a mapper selects a railway=platform with the public_transport=platform tag missing, the validator will suggest to add that tag ("Train Platform has incomplete tags", "Upgrade the tags"). Currently this also happens on railway platforms inaccessible to the public (e.g. with access=no, access=private, etc.). In this case adding the public_transport=* tag would be misleading—these usually represent platforms of significance to the railway system but not the public transportation network.
For example, this platform at Boland's Landing on the Long Island Rail Road in Queens, New York, is only accessible by railway employees. Official maps omit it and riders are often unaware that it even exists, unless an employee happens to be on board to request a stop there. It certainly fits the definition of an area where people board and exit trains, but the train doors will not open for ticketed passengers at Boland's Landing. So I have it tagged as railway=platform + access=private.
I like to add access tags to platforms to make it clear which ones are explicitly not for public transportation. If the validator ignores this, new users tempted to Fix All The Warnings will sometimes come across such platforms and upgrade the tags. Potentially I could add public_transport=no to these platforms to pre-empt any attempts at upgrading the tags, but I'd rather not have to add another tag into the mix and throw in noise for people consuming public_transport=* tagged data.

Hello and welcome, @claysmalley. This is a tricky issue since transit tagging is applied so unevenly in OSM, but I'm pretty sure what iD is doing is okay.
Despite the name, public_transport=platform defines only the place where passengers board or disembark a transit vehicle and doesn't imply "public" access. As you know, that's what the access tag is for. Plenty of mass transit infrastructure doesn't fit the literal meaning of "public transport"—theme park monorails, resort ski lifts, Google's employee shuttle buses—but it makes sense to use the same tags for everything that functions the same way.
That said, do you know if this is causing problems for any apps using OSM data? With iD we're much more concerned with practical data usage than theoretical tag definitions.

Fair enough. I can't think of any data consumers that currently depend on this distinction.

@claysmalley Great, thanks for understanding!


#186 - Add FunctionParameter model and reduce schema parsing

Closes #186
This switches the Function model to having its parameter definitions stored in a new model FunctionParameter, rather than through the pre-generated schema.  The reasons for doing this are:

It makes Function and Workflow consistent in their parameter handling
It makes interacting with the Function parameters (find parameters of type X) much easier, since wasn't any tooling for parsing and interacting with the pydantic generated schema.
It makes us must less tied to the pydantic library and its schema format, since we have the parameter data in a format that we can easily feed into any library of our choosing.

The main changes that are happening here:

A new FunctionParameter model now exists.  It and WorkflowParameter share a common base, so those two models and the base model now live in core/models/parameter.py.
The builder has been updated to create (and delete) FunctionParameter instances rather than generating a pydantic schema.
The TaskParameterForm now uses the info from the FunctionParameter instances to construct the form, rather than relying on the schema.
There is now a core/utils/parameter.py (not to be confused with the now deleted parameters.py) that is the home of all of the logic that deals with pydantic.  Generating the schema and validating parameters against that schema all happen here.  This file is also now the home of the single source of parameter type definitions.  The various places that had defined their own parameter types now just import it from here.

Other related changes:

The code that was in core/utils/serialization.py was no longer needed after these changes so that file is now gone.  A much simpler helper method that just finds the json parameters from the database is included in core/utils/parameter.py and used internally by t he validated_parameters function there.
Many of the unit tests needed to be update to replace the function schema in various fixtures with FunctionParameter instances.

Test Instructions

Some new unit tests were written to confirm that the validation on WorkflowRun and the FunctionParameter removal during the build process work as expected.
Make sure that package builds still work, functions are still taskable, and field validation in the UI still works.  The behavior should be the same as before in all cases.

I was testing and accidentally deleted part of a function and left the parameters section. The package.yaml ended up with two parameter sections:
      # (required) Parameters that the function takes
      parameters:
        - name: a
          type: integer
          default: 1
          required: true
        - name: b
          type: integer
          default: 1
          required: true

      # (required) Parameters that the function takes
      parameters: []

I don't know if this was a feature before the refactor, but if we can catch this misconfiguration that'd be good thing. I'd error on multiple parameter definitions.

The package.yaml ended up with two parameter sections...if we can catch this misconfiguration that'd be good thing

We unfortunately cannot detect this particular error, since the library we're using (pyyaml) merges duplicate keys rather than throwing an error.  This goes against the yaml spec, but it seems like they've never reached consensus on how to fix it.  See discussions here and here.


Quarkus 3 Migration: fix failing tests

fixing all test failing across all repos

@porcelli since the migration already happened, could we consider this as done?


Fixed configure script to accept "-h" and "--prefix".

Calling ./configure --prefix PATH ignored the option (and PATH).
Same with ./configure -h.
Missing PATH (or additional argument) called ./configure --help which showed the error:
# ./configure -p
./configure: 29: ./configure: ./configure.sh: not found

Fixed configure script to accept -h (in addition to --help) and --prefix PATH (in addition to -p PATH) as stated in usage/help of the script. Also put usage/help into a variable and echoed when arguments were incorrect, to avoid error listed above.

See also issue https://github.com/lloyd/yajl/issues/149.


Add responsiveness with Key Frames

Desktop style
@media (min-width: 992px) {
.element {
animation: desktop-animation 3s infinite;
}
}
Mobile style
@media (max-width: 991px) {
.element {
animation: mobile-animation 3s infinite;
}
}
Desktop animation
@keyframes desktop-animation {
0% { background-color: red; left: 0px; top: 0px;}
25% { background-color: yellow; left: 200px; top: 0px;}
50% { background-color: blue; left: 200px; top: 200px;}
75% { background-color: green; left: 0px; top: 200px;}
100% { background-color: red; left: 0px; top: 0px;}
}
Mobile animation
@keyframes mobile-animation {
0% { background-color: blue; left: 0px; top: 0px;}
25% { background-color: green; left: 100px; top: 0px;}
50% { background-color: red; left: 100px; top: 100px;}
75% { background-color: yellow; left: 0px; top: 100px;}
100% { background-color: blue; left: 0px; top: 0px;}
}
This is just a simple example. You can customize the animations and media breakpoints to suit your specific needs. Remember, the animation can be anything from color change, movement, transformation, etc. The key is to define different keyframes for different screen sizes.

Hello @RodrigoNet0,
I can work on this ticket. Could you assign me this task?

Hello @HarikaB11 ,
Is anyone working on this ticket?

@khamkarsuraj Yes, I am working on this.

I'm pretty sure the correct process is to raise a PR with the appropriate changes, not wait to be assigned.

I'm pretty sure the correct process is to raise a PR with the appropriate changes, not wait to be assigned.

you are right

/* Tablet style */
@media (min-width: 768px) and (max-width: 991px) {
.element {
animation: tablet-animation 3s infinite;
}
}
/* Tablet animation */
@keyframes tablet-animation {
0% { background-color: purple; left: 0px; top: 0px;}
25% { background-color: orange; left: 150px; top: 0px;}
50% { background-color: pink; left: 150px; top: 150px;}
75% { background-color: cyan; left: 0px; top: 150px;}
100% { background-color: purple; left: 0px; top: 0px;}
}
This is some CSS added by me ..


Adding the feature of Align numeric values on decimal

Fix https://github.com/dbeaver/dbeaver/issues/16152 by adding the feature of Align numeric values on decimal in n grid-view, as well as text-view.
This is implemented by padding white space for the data is user checked "Align with decimal" in perferences. The whitespace will be removed if user choose to unchecked it.
There may be better way to achieve this.
Attention to be paid: Current method may not work well with long numbers, and there are excessive whitespaces. This happens because I haven't figured out a way of getting all the data of a specific column then figure out length of a grid.
This can be fixed by adding UI in the preferences and let users tell us the estimted length of the numbers, though the best approach will be figuring out the needed white space automatically.
I am willing to keep working on those feaures. But that will be many, many changes I guess.
I am sorry that I accidentally git added files that shouldn't be commited. I haven't found good ways of removing them myself, is it possible that you only accept part of this branch?

Hello @Tazhio,
Can you please attach a screenshot showing how the introduced option affects the output?

Hi, @Tazhio! There is no way to accept only part of changes from pull request. You can revert files, which you don't want to change, to the revision where they are in initial state.

Sorry for the late reply. I think may work on the latest branch then make my changes again

Hello @Tazhio,
Can you please attach a screenshot showing how the introduced option affects the output?

Sorry for the late reply. Here are the screenshots for the output:

Hi, @Tazhio! Please, remove all unintended changes from this PR unless we can't accept it.

Hello @Tazhio,
This PR looks stale.
Please fix all conflicts and remove unnecessary changes. Otherwise, it will be closed.


NOTICE File

Hello,
NOTICE file has the details of changelog information rather than having copyright details. I checked the latest version too, same thing. Could you please correct the same and confirm us back. Our legal team is not approving to use this tech for the above said problem.
According to the Apache License 2.0 section 4(d) -- anyone distributing his code in a derivative work must include along with the license
Thanks,
Sesha

Hi, you can remove the NOTICE file in your distribution, but have to keep the License file.


[RIP-31] Support RocketMQ BrokerContainer

The issue tracker is ONLY used for bug report(feature request need to follow RIP process). Keep in mind, please check whether there is an existing same report before your raise a new one.
Alternately (especially if your communication is not a bug report), you can send mail to our mailing lists. We welcome any friendly suggestions, bug fixes, collaboration and other improvements.
Please ensure that your bug report is clear and that it is complete. Otherwise, we may be unable to understand it or to reproduce it, either of which would prevent us from fixing the bug. We strongly recommend the report(bug report or feature request) could include some hints as the following:
FEATURE REQUEST

Please describe the feature you are requesting.

Currently, a RocketMQ process has only one broker. However, the slave costs fewer resources than the master. So I want to provide a new BrokerContainer mode, in which multiple brokers can be added or removed to a BrokerContainer process and reuse some resources such as the transport layer. And it can improve the utilization of a single node. So I would like to start an RIP to support RocketMQ BrokerContainer.

Provide any additional detail on your proposed use case for this feature.

Refer to wiki

Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?

nice-to-have

If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:

sub-task1-issue-number: sub-task1 description here,
sub-task2-issue-number: sub-task2 description here,
...

@RongtongJin Hello, here are some examples based on testcontainer, do you want to introduce something similar to KafkaContainer for user brokers to run in containers to reduce losses?
https://github.com/apache/flink/commit/ce9cfced5df0b557625018d7267bae5fcd04f40c

@RongtongJin Hello, here are some examples based on testcontainer, do you want to introduce something similar to KafkaContainer for user brokers to run in containers to reduce losses?
apache/flink@ce9cfce

Nope, this RIP has nothing to do with container like docker. It is a RocketMQ native container that can add multiple brokers in one process.

Hi, I have added some code to support Container in DLedger mode. Can I submit a pr directly under this issue?:-D @RongtongJin

Hi, I have added some code to support Container in DLedger mode. Can I submit a pr directly under this issue?:-D @RongtongJin

Of course!


Scale should recycle index instead of incrementing "highestUsedIndex"

Is this a request for help?:
Yes
Is this an ISSUE or FEATURE REQUEST? (choose one):
ISSUE
What version of acs-engine?:
0.19.2

Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Kubernetes v1.11.3
What happened:
We are using cluster-autoscaler to automatically add/remove nodes. When adding new nodes, acs-engine determines the the node name's index by incrementing the “highestUsedIndex”. Since our cluster scales up/down pretty frequently, we are reaching the max index limit (100) pretty quickly even though the actual nodes count is much less than 100.
Failed to scale up: failed to increase node group size: resources.DeploymentsClient#CreateOrUpdate: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="InvalidTemplate" Message="Deployment template validation failed: 'The provided value '101' for the template parameter 'agentpool1Count' at line '1' and column '1383' is not valid. The parameter value is not part of the allowed value(s): '1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100'.'."
What you expected to happen:
acs-engine should determine the node name's index from the unused index.
How to reproduce it (as minimally and precisely as possible):
Scale-up and down multiple times, and notice the node name's index keeps increasing.
Anything else we need to know:
It prevents us to deploy cluster-autoscaler in prod.

Looks like this is the issue: https://github.com/Azure/acs-engine/blob/v0.19.2/parts/agentparams.t#L2
In v0.19.2 we used to have limits to what is allowed for agent pool count "{{.Name}}Count". In later versions, we removed this limit. https://github.com/Azure/acs-engine/blob/master/parts/agentparams.t#L1-L7


use vscode file watching in vscode

Vscode already does the heavy lifting of fileqatching, cross platform, all deployment scenarios. Use this instead of fs.watch

Support multiple files


Support for URI filenames, unicode filenames, and unicode paramters

Hi,
As requested by @pdbaines, I added support for:

URI filenames (Issue #8),
unicode filenames (Issue #7)

Damian

@deads -- looks like a permission error on setup.py:
Traceback (most recent call last):
  File "setup.py", line 42, in <module>
    init_py = open("paratext/__init__.py", "w")
IOError: [Errno 13] Permission denied: 'paratext/__init__.py'

and:
$ ls -alh paratext
total 32K
drwxrwxr-x 2 ubuntu ubuntu 4.0K Jun 13 23:53 .
drwxrwxr-x 4 ubuntu ubuntu 4.0K Jun 13 23:50 ..
-rw-rw-r-- 1 ubuntu ubuntu  15K Jun 13 23:53 core.py
-rw-rw-r-- 1 ubuntu ubuntu 2.4K Jun  8 06:34 helpers.py
-rw-r--r-- 1 root   root    150 Jun  8 07:08 __init__.py

Wait... that file wasn't even changed in this PR. Okay, ignore me... I have it up and running. I will dig in and let you know any issues that come up.

Okay, great @pdbaines . Standing by.

All good. I'll merge.


[Bug]:

Expected Behavior
I have 3 categories in the preferences modal (necessary, analytics and marketing). Under necessary there are two, under analytics one service and under marketing 3 services.
When I click on "accept all", all categories and services are saved correctly and set in the json.
When the page is reloaded and the preferences modal is opened again via a button, all categories and services are correctly set to "On". If "Save preferences" is now clicked, all categories and services have to be saved as before and should be under "acceptedCategories" AND "acceptedServices".``
Current Behavior
I have 3 categories in the preferences modal (necessary, analytics and marketing). Under necessary there are two, under analytics one service and under marketing 3 services.
When I click on "accept all", all categories and services are saved correctly and set in the json (screenshot 1).
When the page is reloaded and the preferences modal is opened again via a button, all categories and services are correctly set to "On". If "Save preferences" is now clicked (screenshot 2), all categories are correctly saved to "On", but the services are set to "Off".
all services, except for those under "necessary", will end up under "rejectedServices"!

Steps to reproduce

open Preferences Modal -> click on "accept all"
reload the page
open Preferences Modal again -> click on "Save preferences"
open Preferences Modal and check the services (were set incorrectly)

Proposed fix or additional info.
No response
Version
3.0.1
On which browser do you see the issue?
Firefox, Chrome

This sounds like the same bug I reported as #700. I've submitted a PR with a fix here: https://github.com/orestbida/cookieconsent/pull/701

Thank you @peaemaye!

Should be fixed by #701


cmd/cue/cmd: make import path specification more shell friendly

the restructuring with -l is not working on windows with the given examples
cue import -l '"\(name)"' test.yaml

with a test.yaml of
name: test
value: whatever

always results in
parser error in path "\\(name)": illegal character U+005C '\'

i think this should be working as the documentation states U+005C as the right character to start string-interpolation. tried on last release.

It looks like the double quotes are dropped by your shell as well (the double quotes in the error message are added by CUE). I don't know how escaping works in PowerShell so I don't know how to solve this. Could you try using a different shell?

Looking at the PowerShell docs, it uses back tick for escaping and the usual bash quoting indeed won't work for escaping. You will have to adjust the examples to work with PowerShell or use a different shell.
IIUC
cue import -l `"\(name)`" test.yaml

should work, but I have no means of testing this.

With the new syntax (using colons rather than spaces), the current specification of -l is a bit awkward. It makes sense to change the syntax at some point. I'll see if a syntax that doesn't need quoting as much makes sense. This could make examples work on both shells, at least, although incompatibilities will inevitably remain.

This issue has been migrated to https://github.com/cue-lang/cue/issues/176.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


v5.1.0 seems to have a breaking change

eslint-plugin-react was broken on master, and things that shouldn't require semicolons between them now do.
See https://github.com/yannickcr/eslint-plugin-react/commit/65b746edb07080ac3a8c66cd12c532f1a1adc5cb for my workaround. This appeared today, so I'm assuming it was v5.1.0 - not sure which change tho.

Minimal reproduction:
require('acorn-jsx/inject')(require('acorn')).parse('class Foo {}\n<div />', {plugins: {jsx: true}})

According to git bisect, the first bad commit was https://github.com/ternjs/acorn/commit/2062c6b85eb0547dcccbb6f4d9507281dfc3ccb5.

cc @marijnh

More of a bug than a breaking changed. Fixed in attached patch and released as 5.1.1

One dev's bug is another's breaking change ;-) Thanks for the fast fix!


PR: Enhance the warnings display

Description of Changes

[ ] Wrote at least one-line docstrings (for any new functions)
[ ] Added unit test(s) covering the changes (if testable)

[x] Included a screenshot or animation (if affecting the UI, see Licecap)

Issue(s) Resolved

Fixes #9247
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct:

Hello @goanpeca! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file spyder/plugins/editor/panels/linenumber.py:

Line 110:80: E501 line too long (82 > 79 characters)
Line 121:29: E117 over-indented

In the file spyder/plugins/editor/widgets/codeeditor.py:

Line 1457:31: W291 trailing whitespace

In the file spyder/widgets/mixins.py:

Line 207:1: W293 blank line contains whitespace

@ccordoba12 currently the line number area is not changing size when zooming in/out. I think it perhaps should?

@goanpeca I cannot properly test this due to #9425 , which I've repro'd on multiple branches consistently. However, some initial comments:

Could you capitalize the first letter in the Pyflakes message, so it matches the others and doesn't look out of place?
If Pyflakes doesn't have error codes, can you just make the parenthetical be (pyflakes) s (or (pyflakes error)/(pyflakes warning) if there are multiple types) since there's no reason to show the whole thing when there's no error code?
Code is redundant and appears in every message, taking up space; can you just remove it?

Also, how do you enable those pylint errors? They don't show up, even after running static code analysis.

Thanks for the review @CAM-Gerlach

Could you capitalize the first letter in the Pyflakes message, so it matches the others and doesn't look out of place?

Yep

If Pyflakes doesn't have error codes, can you just make the parenthetical be (pyflakes) s (or (pyflakes error)/(pyflakes warning) if there are multiple types) since there's no reason to show the whole thing when there's no error code?

Agreed

Code is redundant and appears in every message, taking up space; can you just remove it?

Not sure, @ccordoba12 wanted it to be obvious so I will defer to his judgement.

Also, how do you enable those pylint errors? They don't show up, even after running static code analysis.

You have to use the latest pyls (but spyder will complain you need a lower version)

I assume you're aware, but just in case, pyflakes messages still have the spurious E in your screenshot.

I assume you're aware, but just in case, pyflakes messages still have the spurious E in your screenshot.

They do have error codes http://flake8.pycqa.org/en/2.5.5/warnings.html

@goanpeca Okay, but I'm a little confused that's flake8, not vanilla pyflakes, which it explicitly says on that page does not provide error code (and none are provided in your screenshot).

@CAM-Gerlach you are right, my bad!

Thanks @goanpeca for this! Things look really nice!!
I have a couple of quick comments:

Instead of using the information sign for hints, please use mdi-lightbulb to follow VSCode lead regarding that symbol.
Please use a nice shade of green instead of blue for hints, because blue is already used by TODO's.

Code is redundant and appears in every message, taking up space; can you just remove it?

I disagree. In ten years of maintaining Spyder nobody has complained about it. Besides, it's much better to be explicit than a bit vague about those messages too. So in my role as BDFL of Spyder I say that stays.

Please use a nice shade of green instead of blue for hints, because blue is already used by TODO's.

Ok, I will post a screenshot to see how it looks

I disagree. In six years of maintaining Spyder nobody has complained about it. Besides, it's much better to be explicit than a bit vague about those messages too. So in my role as BDFL of Spyder I say that stays.

I was referring to the word code in messages I added (see first screenshot see the word code in parentheses), not about the title.

I was referring to the word code in messages I added

Ok, sorry. Perhaps they should stay? I mean it's hard to understand what those messages mean without the word code on them.

If you want to keep "code" repeated in every message for the sake of explicitness, its not a big deal, though I'd prefer it without it since the user can reasonably infer what it means (at worst, they have to google it their first time, which is exactly what they likely want to do anyway).
However, I do strongly disagree with the green color for information. Blue has long been the standard color for this across all the UIs I'm familiar with, while Green means "Good"/"Ok", which is not the case here. For example, the first four relevant results for errors warnings information colors state that the universal convention is red-error, orange/yellow-warning, blue-info, and green-ok/success/good. If you feel it conflicts unduly with the annotation color, then that color should be changed to something else, like grey.

I really like this change!

However, I do strongly disagree with the green color for information.

I would go back to the blue for the info.

Ok, sorry. Perhaps they should stay? I mean it's hard to understand what those messages mean without the word code on them.

I think pyflake: E0602 would look good and still googles well. I think the word "code" in there is a little distracting.
I also think that the error codes are in general a little distracting and not too important on first glance or for new users. Can we make the error stand out from the error code with a different brightness or maybe color. For example have the (pyflake: E0602) part a darker grey or make the other part lighter.

I would go back to the blue for the info.

We have a lot of things that are blue in the editor panels: the TODO's symbol (as I said before) and the debugger arrow. So if you want blue for info, we really need to change to green those other symbols. @goanpeca, please do that as part of this PR, but you also need to change those colors in ScrollFlagArea.

I think pyflake: E0602 would look good and still googles well. I think the word "code" in there is a little distracting

Ok, fair enough. I agree with this suggestion.

For example have the (pyflake: E0602) part a darker grey or make the other part lighter

This is a good suggestion too. I think the error code should be lighter to make it less relevant than the rest of the text.

We have a lot of things that are blue in the editor panels: the TODO's symbol (as I said before) and the debugger arrow.

TODOs/etc can be grey or (if not visible enough) purple. Debugger error can be green.

I think pyflake: E0602 would look good

Agreed as well (though to be really nitpicky, its pyflakes and its the one that doesn't have error codes :)

I think the error code should be lighter to make it less relevant than the rest of the text.

I agree with having it a different shade, but in our default dark theme, having it lighter would make it much more visible/prominent, not less. If we wanted something that would work across our themes, we could just use italic instead (though that might not look quite as clean)?

We will still need to go over all the colors in Spyder at some point before the official release of 4.0 so I suggest we do not take more time than it is needed to get this functionality going. We should be moving faster and leave all the color and style discussions for another issue/PR.

On another note, do we plan to add additional highlights to the code editor words to indicate the problems (errors, warning, info, hint) on the text itself, using curly underline and colors?

Thoughts @bcolsen @ccordoba12 ?

Beautiful!! I really like it! I was about to suggest using magenta for TODOs, so that's really cool.

We should be moving faster and leave all the color and style discussions for another issue/PR and focus on the actual tooltip (what this PR is about) and not on the icons and colors on the LineNumber/ScrollBar area.

Ok, agreed. Please open a new issue about it so we don't forget to address that, either in beta3 or beta4.
We should do two things about that: define a central place to import different colors and (in my opinion) change the debugger arrow to green.

On another note, do we plan to add additional highlights to the code editor words to indicate the problems (errors, warning, info, hint) on the text itself, using curly underline and colors?

Yes, I was also about to suggest that. Please open another issue about it.


fix: remove duplicate implementation of deepName

Codecov Report

Merging #110 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #110   +/-   ##
=========================================
  Coverage     86.22%   86.22%
  Complexity      146      146
=========================================
  Files            47       47
  Lines           501      501
  Branches        116      116
=========================================
  Hits            432      432
  Misses           20       20
  Partials         49       49

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 15688c9...7b2151b. Read the comment docs.


launcher.c: add support for Unicode sys.argv in cli/gui.exe Windows launchers

In Python 3 on Windows, sys.argv is created through the Windows Unicode API.
That means command line arguments are retrieved as wchar_t* through the Windows-specific wmain (for console programs) and wWinMain (for gui programs) entry points.
See https://bugs.python.org/issue2128
However, setuptools' "cli.exe" and "gui.exe" launchers, as defined in launcher.c, are still using the Windows ANSI API: i.e. the entry point is main, and argv type is char * instead of wchar_t*, which means it's dependant on the current console's codepage.
This prevents Windows Python 3 from accessing the Unicode command line arguments which are sent by Windows when running python scripts via the usual python.exe command. When run through launchers, the sys.argv contains instead replacement strings like "?????", which is not nice.
The fix proposed here is similar to the one which introduced support for Unicode sys.argv in Python 3: https://hg.python.org/cpython/rev/22a74eaf6b22/
Basically:

we use 'wmain' and 'wWinMain' as entry points, so we can use wchar_t *argv
we replace all char* with wchar_t*
we use the 'wide' Unicode version of all relevant functions (wcslen instead
of strlen, CreateProcessW instead of CreateProcessA, etc.)

Please let me know what you think.
Thank you.

I just added unit tests for the sys.argv as unicode strings. I expect them to fail, as the precompiled cli.exe and gui.exe are still the unpatched ones. The tests do pass with my patched version of launcher.c.
Of course, I need to skip these for python 2, becuse of this and that.

No, I haven't tried distlib yet. I'll give it a try and let you know.
Btw, I managed to compile launcher.c with the following commands in Visual Studio (I tried all 2008, 2010, 2013 and 2015):
cl /DGUI=0 /DUNICODE /D_UNICODE /O1 /Fecli.exe launcher.c /link /SUBSYSTEM:CONSOLE
cl /DGUI=1 /DUNICODE /D_UNICODE /O1 /Fegui.exe launcher.c /link /SUBSYSTEM:WINDOWS

I also compiled it successfully using GCC 5.3.0 from mingw-w64, using the following commands:
gcc -DGUI=0 -municode -O -s -o cli.exe launcher.c
gcc -DGUI=1 -mwindows -municode -O -s -o cli.exe launcher.c

So.. I just tried to plug the distlib-generated .exe launchers in setuptools' test suite, and tried running the unicode sys.argv unit tests above, and -- I'm happy and a little bit sad at the same time.
Happy because they seem to be working; a bit sad because I spent a few days trying to fix this in setuptools, without knowing @vsajip had already fixed the issue in distlib... ;)
Although the unicode argv works, two other tests in test_windows_launchers.py fail for some reason.
I guess I shall leave it to you to decide how to proceed.
I'd really like this issue to be solved, whether in setuptools or through distlib.
Thanks a lot.

@anthrotype Thanks so much for the extended work on this. My guess is there's more work to be done than just copying the executables from distlib. I was actually thinking that distlib could be vendored into setuptools (the way that six and packaging are) and then it could replace all of the script handling logic (not just the windows executables).
I'm happy to accept for a short-term solution to simply bundle the distlib executables or to accept this pull request above and implement the originally proposed solution, but of course it would be best to remove as much of this duplication as possible... I am worried about the failing test cases, as you mentioned. If we're to include the distlib executables, I'd like to know why those tests are failing.
So short answer is - whatever you have time for, I appreciate the help.

distlib could be vendored into setuptools (the way that six and packaging are) and then it could replace all of the script handling logic

That sounds good to me, better to avoid duplication.

I'm happy to accept for a short-term solution to simply bundle the distlib executables

the problem is that the pre-compiled executables in distlib are meant to work with distlib.scripts.ScriptMaker, and can't simply be dropped in setuptools as they currently are.
At least they need to be recompiled without #define APPENDED_ARCHIVE, which unfortunately is written in the source file, so can't be undefined from the comand line: ([launcher.c:36] (https://bitbucket.org/pypa/distlib/src/a258e3bdd6f8205f3815e173a55ffe857e743995/PC/launcher.c?at=default&fileviewer=file-view-default#launcher.c-36)).
This definition specifies the mode in which the launcher works:

the default is append the python script source in an archive inside the same exe (but this requires the distlib ScriptMaker);
the other option (with APPEND_ARCHIVE undefined) works the same as setuptools' launcher, i.e. the exe tries to find a "-script.py[w]" file to run in the same folder.

As I mentioned yesterday, even when I recompile the distlib launcher without APPEND_ARCHIVE to make it work like setuptools', then there is one test case that fails: test_windows_launcher::TestCLI.test_with_options.
After tinkering with pointers, I eventually found a solution to the issue (see patch below).
The problem was that, when the python executable in the #!shebang was not wrapped in quotes (as in above test case), the distlib launcher was also appending the argument in the executable line. So the latter was being included twice: once in the quoted executable string, and again on its own:
"C:\Python35\python.exe -Oi" -Oi

As I'm not familiar enough with mercurial to send a pull request myself, it'd be nice if someone could have a look and send the patch to the bitbucket repository? 😁
diff -r a258e3bdd6f8 PC/launcher.c
--- a/PC/launcher.c	Mon May 16 23:31:18 2016 +0100
+++ b/PC/launcher.c	Fri May 27 12:46:01 2016 +0100
@@ -33,7 +33,7 @@

 #pragma comment (lib, "Shlwapi.lib")

-#define APPENDED_ARCHIVE
+// #define APPENDED_ARCHIVE

 #define MSGSIZE 1024

@@ -406,6 +406,8 @@
     }
     /* p points just past the executable. It must either be a NUL or whitespace. */
     assert(*p != L'"', "Terminating quote without starting quote for executable in shebang line.");
+    /* if p is whitespace, make it NULL to truncate 'line', and advance */
+    if (*p && iswspace(*p)) *p++ = L'\0';
     /* Now we can skip the whitespace, having checked that it's there. */
     while(*p && iswspace(*p))
         ++p;

so after this patch I can replace the cli.exe and gui.exe in setuptools package with the patched distlib launchers and the test pass, including those for the unicode argv (PY3 only).

unlike setuptools, distlib does not have precompiled launchers for the ARM platform; only 32 and 64 bit, cli and gui. But I guess those should be easy to make.

not familiar enough with mercurial

It's quite possible that Vinay accepts pull requests in the github mirror.

they need to be recompiled without #define APPENDED_ARCHIVE

I don't think it will be acceptable to comment out that line - after all, pip uses the version with that variable defined. I'd like to setuptools to use the same. Can we adapt setuptools to append the script instead?

The problem was that, when the python executable in the #!shebang was not wrapped in quotes

Again, maybe it makes sense for setuptools to generate scripts that are compatible with the launchers as written. Is that possible?

But I guess those should be easy to make.

Yes, this issue should be filed with distlib. Would you like me to do that?

Can we adapt setuptools to append the script instead?

Sure we can do that. So to clarify, you want setuptools to make the exe launchers the same way that distlib ScriptMaker does (by appending the shebang and source code), but without requiring to import from distlib (at least, temporarily)?

it makes sense for setuptools to generate scripts that are compatible with the launchers as written

yeah, we could put quotes to work around that bug, but the bug still needs to be fixed upstream.

this issue should be filed with distlib

Yes please! Thanks.
I'll try to figure out how to send the patch above to mercurial, otherwise I'll just send it to the git mirror.

you want setuptools to make the exe launchers the same way that distlib ScriptMaker does

Yes.

yeah, we could put quotes to work around that bug, but the bug still needs to be fixed upstream.

Sounds good.

I requested ARM launchers here.

ok, now that ARM launchers are gone, it should be easier to integrate distlib launchers in setuptools.
I should be able to work on this over the weekend.
Do you want me to close this PR and open a separate one, or shall I keep working on this branch?
The simplest way to proceed is to modify the WindowsExecutableLauncherWriter._get_script_args method in easy_instal module so that it zips and append the wrapped script, along with the #!shebang, to the launcher executables.
Another option would be to "vendor" distlib, like pip currently does, and use distlib's ScriptMaker for that.
What do you prefer me to do?
Besides, I noticed another difference between the way setuptools and distlib make their launchers. The setuptools also adds an (external) manifest file for each .exe. The manifest is added only for 32 bit launchers, and according to the inline comment, it is meant

to prevent Windows from detecting it as an installer (which it will for launchers like easy_install.exe). Consider only adding a manifest for launchers detected as installers. See Distribute #143 for details.

distlib, on the other hand, (or at least the way pip currently uses it) doesn't seem to add a manifest by default to the executables.
So I'm not sure what I should do here. /cc @vsajip @jaraco

Well, if pip is using distlib and that doesn't add a manifest and nobody's complained, does that mean manifests aren't really needed? I would imagine manifests are only useful for things like elevated privilege levels - which shouldn't in general apply to scripts installed with Python packages, ISTM,

I seem to recall that only one of the 32-bit or 64-bit executables needed the manifest.

for the records, this is the distribute issue 143 that the comment I quoted above was referring to:
https://bitbucket.org/tarek/distribute/issues/143/easy_install-opens-new-console-cant-read

so it appears the issue of undesired UAC elevation only affects executables detected as installers:

Installer Detection only applies to:

32 bit executables
Applications without a requestedExecutionLevel
Interactive processes running as a Standard User with LUA enabled
Before a 32 bit process is created, the following attributes are checked to determine whether it is an installer:
Filename includes keywords like "install," "setup," "update," etc.

https://technet.microsoft.com/en-us/library/cc709628(WS.10).aspx
I haven't read the full MS article, but I believe we should include the manifest at least for scripts that happen to contain one of those keywords.
It's going to be an external xml file, because for embedding it inside the executable itself we need the mt.exe command, which we can't assume will be available on the users' machines.

OK, I run some tests and it appears that the distlib launchers do not need any external manifest file, even when the script name contains keywords like "install", or "setup".
I made a minimalist setup.py for a script named "launcher_install", containing just a print("hello world") in its main(), and I set that as a console script entry point.
I tested it on Python 2.7 and 3.5 32-bit with setuptools 23.0. When I install my test module from source distribution (pip install -v .), I get a launcher_install.exe which is the current setuptools launcher, accompanied by a separate .exe.manifest file and launcher_install-script.py.
If I then delete or rename the manifest file, and try to run this executable (containing the "install" word in the name) under Windows 7, I get "permission denied". So for setuptools launchers, the manifest is required, at least when thos keywords are present in the script name.
However, if I make a wheel first, and the I pip install from the wheel, I get a new-style, self-contained distlib launcher, with no external manifest file.
This time, even the executable has "install" in its name, It Just Works™ 😄
I presume it's the way the setuptools and the distlib launchers are compiled. For the first, the cl.exe command is used, as explained in the "msvc-build-launcher.c" batch script). For distlib launchers, Visual Studio is used via the included .sln solution file. So Visual Studio must be injecting a manifest directly in the distlib launchers.
So, all in all, I think we can safely get rid of the manifest thing if we switch to distlib launchers.
WDYT?

@anthrotype Thanks for the detailed analysis. That sounds good to me.

The distlib launchers do contain an embedded manifest:
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <requestedExecutionLevel level="asInvoker" uiAccess="false"></requestedExecutionLevel>
      </requestedPrivileges>
    </security>
  </trustInfo>
</assembly>

@vsajip thanks for the confirmation! It wasn't clear to me. :)

@jaraco I modified easy_install.py to use the distlib launchers, however now I'm not sure what to do with the current setuptools launcher executables (cli-32.exe, gui-32.exe, etc.) included as package_data in setuptools source.
Shall I simply replace them with the pre-compiled distlib binaries, found here?
And what names shall I use for these: the same distlib uses (t32.exe, t64.exe, w32.exe and w64.exe), or I should keep the current setuptools names (cli-32.exe, cli-64.exe, gui-32.exe, gui-64.exe)? I would prefer to use the distlib names to make it clearer they work differently from the old ones.
And what about those copies of the 32 bit launchers which don't not have a "-32" suffix?
The msvc-build-lancher.cmd says:
REM buildout (and possibly other implementations) currently depend on
REM the 32-bit launcher scripts without the -32 in the filename, so copy them
REM there for now.
copy setuptools/cli-32.exe setuptools/cli.exe
copy setuptools/gui-32.exe setuptools/gui.exe

Shall I get rid of the two launchers above?
I can't simply rename distlib's "t32.exe" to "cli.exe", etc., as the new launchers work differently from the old ones (i.e. don't expect to find the wrapped script in the same directory, but append it to themselves as zipped data).
The "msvc-build-launcher.cmd" itself should go, I think. It should probably be replaced by a copy of @vsajip simple_launcher source files.

ah, and what about the launcher manifest.xml file, shall we remove that as well as no longer needed by distlib launchers?

Please have a look at this branch on my setuptools fork:
https://github.com/anthrotype/setuptools/commits/distlib-launchers
I can force-push to this same PR branch, or open a new pull request if you like.
Thanks

by a copy of @vsajip simple_launcher source files
Note that these updated sources will be copied to the distlib source tree before the next release of distlib.

Overall, my suggestion is that we re-use as much of distlib as possible. If it's possible, for example, to call into distlib (perhaps passing the script text) and let distlib produce the executables, that would be best.

Shall I simply replace [the existing binaries] with the pre-compiled distlib binaries, found here?

Perhaps we should keep the old ones in place just in case other libraries are referencing them. We'll definitely mark them as deprecated and not use them internally.

And what names shall I use for these: the same distlib uses (t32.exe, t64.exe, w32.exe and w64.exe), or I should keep the current setuptools names (cli-32.exe, cli-64.exe, gui-32.exe, gui-64.exe)? I would prefer to use the distlib names to make it clearer they work differently from the old ones.

I'd like not to copy anything into setuptools, but instead reference it from distlib. If making calls into distlib isn't suitable, and we need to reference these resources directly, then we should reference them from the distlib package. There might be some challenges with doing this using a vendored package, but if you want to simply assume that distlib is a requirement of setuptools for now, that would be fine.

And what about those copies of the 32 bit launchers which don't not have a "-32" suffix? Shall I get rid of [them]?

Same as the other scripts - we'll leave them there for now for compatibility, and we'll remove all of them with one announced release.

The "msvc-build-launcher.cmd" itself should go, I think. It should probably be replaced by a copy of @vsajip simple_launcher source files.

Agreed.

ah, and what about the launcher manifest.xml file, shall we remove that as well as no longer needed by distlib launchers?

Let's consider that deprecated also, and remove it when removing the launcher executables.

I can force-push to this same PR branch, or open a new pull request if you like.

Go ahead and force-push that here. Thanks.

Thanks for the reply.
If we assume distlib is a dependency of setuptools, then it's easy for me to just call distlib's ScriptMaker. We don't need to reference the executable files directly as that is taken care of by distlib itself.
Ok, so I shall keep the old executables as well as the classes and function that references them in easy_install.py. I will simply no longer use them, but import and use ScriptMaker from distlib (just for the windows launcher, for now, I guess).

If you run into any problems invoking ScriptMaker to do what you need, do let me know!

I'm going to close this for now, but feel free to revive the effort at any time.

I'm sorry, I could not find the time to work on this as I was busy with other stuff...
Also I wasn't sure how I should go about vendoring distlib in setuptools.
For now I resorted to making a wheel and using pip to install so it uses the distlib launchers instead of setuptools'.

I'm having exactly same issue. Really pity this was abandoned because CLI executables without support for unicode arguments are almost unusable. E.g. you can't even pass the non-ASCII filename.

Googling to find out why console scripts installed by conda on Windows (through setuptools 61.2.0 I guess, not distlib) lost out-of-codepage characters in the command line, I landed here. How about reopening this issue and merge the OP's PR to solve it in setuptools itself, too?

Also I wasn't sure how I should go about vendoring distlib in setuptools.

Given #2825, would adding distlib as a dependency of setuptools be a more acceptable approach than vendoring? Though currently setuptools has no run-time dependencies ...

Agreed that #2825 would imply depending. Unfortunately, until #2825 is resolved, vendoring is the sole means of utilizing a dependency.


Remove ROS-specific descriptions

Proposed change(s)
Remove ROS-specific descriptions from GitHub Issue/Pull request template
Useful links (GitHub issues, forum threads, etc.)

https://github.com/mangdangroboticsclub/mini_pupper/pull/6

Types of change(s)

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Code refactor (non-breaking change which refactor the code)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update only
[x] Other (update GitHub config)

Checklist

[x] I have read the CONTRIBUTING guidelines.
[x] I have checked to ensure there aren't other open Pull Requests for the same change.

Other comments

fine with me


Eliminate a bunch more recursion; expand the TreeLike iterator trait a bit

This PR replaces the recursive derived implementations of PartialEq, PartialOrd, Hash, fmt::Debug and fmt::Display. Along the way it expands the iter::TreeLike trait to make it a bit more useful (adding a Ternary variant and making the existing Nary variant generic as long as you can get a length out of it and index into it).
The new fmt::Debug method works using a new DisplayNode wrapper around Terminal which allows iterating over a script in the same way as it's displayed, treating things like or_i(0, X) as l:X and implementing the c:pk_k aliases and so on. This seems generally useful but this PR does not expose it in the public API because I'd like to make some breaking changes to Terminal down the line and don't want to expand the API.
The new Ord impl orders things alphabetically (assuming it is bug-free at least) by using the same iterator as the display logic. This is both nonrecursive and a more useful ordering for anybody who cares about the exact ordering. On the other hand, if anybody is depending on the existing ordering this will break their code. I would assume not, since the existing ordering is a weird ad-hoc thing based on the order that derive(PartialOrd) happens to use.
Similarly, it adds a Terminal::fragment_name accessor which returns a &'static str representing the fragment name as displayed. This is also not put into the public API.
The block of type parameters used in the debug output of Miniscripts is moved into a fmt::Display impl on Type itself. This is part of the public API.
This PR does not replace the Clone impl, which is currently derived. This impl actually isn't recursive, since it just clones the Arcs in the first layer of the script. Maybe we want to implement this manually and do a "deep copy"? This would be useful for users who have keys with interior mutability or something. I have a followup which does this, but didn't include it because I felt it might be controversial and need its own discussion.
This PR also does not replace the implicit Drop impl, because that's hard to do and I haven't done it. But we're making progress.

Maybe we want to implement this manually and do a "deep copy"? This would be useful for users who have keys with interior mutability or something. I have a followup which does this, but didn't include it because I felt it might be controversial and need its own discussion.

I don't see any harm "deep copy". Or we can wait for someone to complain or explicitly request that feature. I can forsee users using keys with interior mutability when scanning funds from descriptors keys containing wildcards.

I don't see any harm in having a "deep copy". Or we can wait for someone to complain or explicitly request that feature. I can forsee users using keys with interior mutability when scanning funds from descriptors keys containing wildcards.

Nice. I'll PR it since I've already got the code written.


[Add2App] Cannot not compile on AOS (AndroidX enabled) with Flutter version > 1.12.0 -> Imports Error

Cannot compile with AOS once updated to Flutter version > v1.12.0, tried with latest version on channel master / dev / stable, the same issue:
Error: Unresolved reference: facade   on this line import   io.flutter.facade.Flutter
From my observation, the FlutterActivity is importing non-AndroidX references, so I guess it maybe the AndroidX issue.
My Android project has enabled AndroidX support, and also my Flutter module has specified ->  module:
    androidX: true
The project works great before upgrading to Flutter version 1.12.x. There's no problem for the imports and the FlutterActivity is using AndroidX references.
Once I have upgraded to Flutter version 1.12.x. flutter packages get give me the following warning:
The plugin `flutter_native_image` is built using an older version of the Android plugin API which assumes that it's running in a full-Flutter environment. It may have undefined behaviors when
Flutter is integrated into an existing app as a module.

Can this be the reason why the Flutter SDK is still referencing the non-AndroidX reference, when some of the Flutter plugins I am using gave me this error?
Please help. Thanks so much!
Flutter Doctor:
[✓] Flutter (Channel master, v1.13.7-pre.24, on Mac OS X 10.14.6 18G95, locale en-HK)

[!] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses
[✓] Xcode - develop for iOS and macOS (Xcode 10.3)
[✓] Android Studio (version 3.4)
[!] IntelliJ IDEA Ultimate Edition (version 2019.2.4)
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
[✓] Connected device (2 available)

! Doctor found issues in 2 categories.

Hi @michael-chiu
As I understand that your are referring to a 3rd party plugin flutter_native_image
You might want to search for solution on the plugin's github and consider opening an issue there
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

@VladyslavBondarenko , thank you for your help.
I agree it maybe an issue that can be fixed on the plugins side. However, I am getting the below error on a number of plugins, even on some from flutter.dev, like image_picker(the plugins themselves support AndroidX) :
The plugin `xxx` is built using an older version of the Android plugin API which assumes that it's running in a full-Flutter environment. It may have undefined behaviors when
Flutter is integrated into an existing app as a module.

This stop me from upgrading my Flutter version to above 1.12.x. So I would like to know in Add2App case, I need to wait all the plugins my project using to implement v2 Android Plugin APIs to fix this issue?
Is it possible for the latest Flutter version being compatible with the v1 Android Plugin APIs for Add2App case? Any temporary workaround for this issue would be nice.
Thank you.

@michael-chiu
I would upgrade plugins and check whether the new Flutter version is compatible with them.
And or would use for a while older Flutter version, or if the problem is in some third-party plugins, which don't update regularly, and there are exists analogs from Flutter team, and it's easy to replace them, I would consider this option too.
Unfortunately I don't possess more info and can not answer the second question

@michael-chiu
If you face with this problem with plugins from flutter/plugins repository, it would be better to create separate issue(s) for them.
Closing, if you disagree please write in the comments and I will reopen it.
Thank you


Requires Node versions < 8

Node 7 was the current version at the time package.json was last modified and users report in #639 that the app doesn't install with 8+.

@bhousel yes? no?

From reading here, it looks like we can just drop the contextify dependency:
https://github.com/brianmcd/contextify
(I see issues like this a lot with node-pre-gyp failing on newer node builds, and in almost all cases we can find a workaround or pure javascript replacement)

Thanks @bhousel. Someday, perhaps. In the meanwhile, I think this will make the current state of affairs more clear, yes?

Thanks @bhousel. Someday, perhaps. In the meanwhile, I think this will make the current state of affairs more clear, yes?

Looks good 👍


HBASE-27045 Disable TestClusterScopeQuotaThrottle

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 38s
Docker mode activated.


Add --no-name gzip flag to compression file output

We are get annoying file diff triggers when reprocessing the pipeline, even if nothing changes in the file. This is important to fix so that we are able to isolate actual changes that result from reprocessing output data.
As @shntnu notes in #48 the reason why the gzip files are triggering positive diffs, is because of an added timestamp.
The way to remove the timestamp from the file is to pass a --no-name (-n) flag to the gzip command. See http://linuxcommand.org/lc3_man_pages/gzip1.html
Fortunately, it looks like pandas-dev/pandas#33398 has added the ability to include args to pandas gzip compression. This improvement will be included in pandas version 1.1, which is scheduled for an Aug 1 release.
Three Options

pandas v1.1 option (assuming that it solves this problem!)
base python option (outlined https://github.com/broadinstitute/lincs-cell-painting/pull/48#issuecomment-636462269)
bash option (outlined https://github.com/broadinstitute/lincs-cell-painting/pull/48#issuecomment-636337076).

For the pandas or python option, the solution should ideally live in pycytominer. I've created a stub for this at cytomining/pycytominer#83

fixed in #63

Awesome!!!


Clean up apiservice

Add OwnerReferences to APIService so that when konk-service is deleted the APIService is unregistered from the Konk.
https://github.com/infobloxopen/konk/blob/7f1e36214ca33908a0dc25eeaad86019067d7dc2/helm-charts/konk-service/templates/apiservice-configmap.yaml#L50

Dupe of #207


ARM binary out of range syscall

Describe the bug
I need to run gem5 with the ARM O3 processor.
When I use the binary located at /tests/test-progs/hello/bin/arm/linux/hello everything works fine but when compile another code
#include <stdio.h>
int main() {
    printf("Hello, ARM!\n");
    return 0;
}

I get this error:
build/ARM/base/statistics.hh:277: warn: One of the stats is a legacy stat. Legacy stat is a stat that does not belong to any statistics::Group. Legacy stat is deprecated.
gem5 Simulator System.  http://gem5.org
gem5 is copyrighted software; use the --copyright option for details.

gem5 version <IP_ADDRESS>
gem5 compiled Sep 24 2024 17:30:34
gem5 started Sep 26 2024 16:53:01
gem5 executing on user01, pid 28484
command line: build/ARM/gem5.opt -d m5out-cortex-2 configs/common/cores/arm/cortex-a15.py

Global frequency set at<PHONE_NUMBER>000 ticks per second
warn: No dot file generated. Please install pydot to generate the dot file and pdf.
0: system.remote_gdb: listening for remote gdb on port 7000
Starting simulation with O3CPU (Out-of-Order) Cortex-A15 and L1/L2 cache configuration...
build/ARM/sim/simulate.cc:107: info: Entering event queue @ 0.  Starting simulation...
build/ARM/sim/syscall_emul.cc:73: warn: ignoring syscall set_robust_list(...)
build/ARM/sim/syscall_desc.hh:204: fatal: Syscall 398 out of range
Memory Usage: 8515608 KBytes

I compile the code using arm-linux-gnueabi-gcc -marm -static -g -o hello-arm hello.c and it's information mach with the binary in the test folder.
hello-arm: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, BuildID[sha1]=11741fdbc30cd57860546f706974c28508da1467, for GNU/Linux 3.2.0, with debug_info, not stripped
Affects version
<IP_ADDRESS>
gem5 Modifications
No
To Reproduce
Run gem5 with this command:
build/ARM/gem5.opt -d m5out-cortex-2 configs/common/cores/arm/cortex-a15.py
If writing code, or a terminal command, use code blocks. Either an inline code block, scons build/ALL/gem5.opt (enclosed in two '`') or a multi-line codeblock:
import m5
from m5.objects import *
from m5.util import *
from O3_ARM_v7a import *
# Define a system to simulate
system = System()

# Set clock frequency for the system
system.clk_domain = SrcClockDomain()
system.clk_domain.clock = '2.5GHz'  # Adjust according to your needs
system.clk_domain.voltage_domain = VoltageDomain()
system.clk_domain.voltage_domain.voltage = "1.1V"

# Define the memory configuration
system.mem_mode = 'timing'  # Use timing memory mode for accurate simulation
system.mem_ranges = [AddrRange('8GB')]  # Set memory size

# Create a simple memory bus
system.membus = SystemXBar()

# Define the CPU - Out-of-Order CPU (O3CPU model) simulating ARM Cortex-A15
system.cpu = O3_ARM_v7a_3()  # O3CPU simulates an out-of-order ARMv7 Cortex-A15-like CPU
system.cpu.numPhysFloatRegs = 32

# L1 Instruction Cache (I-Cache)
system.cpu.icache = O3_ARM_v7a_ICache(size='32kB', assoc=2)  # Set L1 I-cache size and associativity
system.cpu.icache.cpu_side = system.cpu.icache_port
# system.cpu.icache.mem_side = system.membus.cpu_side_ports

# L1 Data Cache (D-Cache)
system.cpu.dcache = O3_ARM_v7a_DCache(size='32kB', assoc=2)  # Set L1 D-cache size and associativity
system.cpu.dcache.cpu_side = system.cpu.dcache_port
# system.cpu.dcache.mem_side = system.membus.cpu_side_ports

system.l2bus = L2XBar()

system.cpu.dcache.mem_side = system.l2bus.cpu_side_ports
system.cpu.icache.mem_side = system.l2bus.cpu_side_ports

# L2 Cache (shared by both L1 I-cache and D-cache)
system.l2cache = O3_ARM_v7aL2(size='1MB', assoc=16)  # Set L2 cache size and associativity
system.l2cache.cpu_side = system.l2bus.mem_side_ports
system.l2cache.mem_side = system.membus.cpu_side_ports  # Connect L2 cache to memory bus
# system.l2cache.cpu_side = system.cpu.icache.mem_side
# system.l2cache.mem_side = system.membus.cpu_side_ports

# Connect L2 cache to the memory bus
# system.l2cache.mem_side = system.membus.cpu_side_ports

# Setup memory controller
system.cpu.createInterruptController()

system.mem_ctrl = MemCtrl()
system.mem_ctrl.dram = DDR3_1600_8x8()
system.mem_ctrl.dram.range = system.mem_ranges[0]
system.mem_ctrl.port = system.membus.mem_side_ports

system.system_port = system.membus.cpu_side_ports

# Create a process for running a binary
binary = '/home/user01/workspace/gem5/tests/test-progs/hello/bin/arm/linux/hello'
binary = '/home/user01/workspace/arm/hello-arm'
#binary = '/home/user01/workspace/paper/hello'
system.workload = SEWorkload.init_compatible(binary)

process = Process()
process.cmd = [binary]
system.cpu.workload = process
system.cpu.createThreads()

# Define the root object for the simulation
root = Root(full_system=False, system=system)

# Instantiate the simulation
m5.instantiate()

print("Starting simulation with O3CPU (Out-of-Order) Cortex-A15 and L1/L2 cache configuration...")
exit_event = m5.simulate()

print(f"Simulation finished with exit cause: {exit_event.getCause()}")

If possible, please include the Python configuration script used and state clearly any parameters passed.
Terminal Output
If applicable, add the terminal output here. If long, only include the relevant lines.
Please put the terminal output in code blocks. I.e.:
#Terminal output here#

Expected behavior
A clear and concise description of what you expected to happen.
Host Operating System
Ubuntu 22.04
Host ISA
X86
Compiler used
scons last version
Additional information
Add any other information which does not fit in the previous sections but may be of use in fixing this bug.

Hello, I was able to get this to work by using aarch64-linux-gnu-gcc as the compiler and by using gem5 version <IP_ADDRESS>, which is the latest version. Could you try it and see if that works for you?

Hi. Thanks for your response.
I get another error.
user01@user01:~/workspace/gem5$ build/ARM/gem5.opt -d m5out-cortex-2 configs/common/cores/arm/cortex-a15.py
build/ARM/base/statistics.hh:277: warn: One of the stats is a legacy stat. Legacy stat is a stat that does not belong to any statistics::Group. Legacy stat is deprecated.
gem5 Simulator System.  http://gem5.org
gem5 is copyrighted software; use the --copyright option for details.

gem5 version <IP_ADDRESS>
gem5 compiled Sep 24 2024 17:30:34
gem5 started Oct  4 2024 15:36:00
gem5 executing on user01, pid 1019844
command line: build/ARM/gem5.opt -d m5out-cortex-2 configs/common/cores/arm/cortex-a15.py

Global frequency set at<PHONE_NUMBER>000 ticks per second
warn: No dot file generated. Please install pydot to generate the dot file and pdf.
0: system.remote_gdb: listening for remote gdb on port 7000
Starting simulation with O3CPU (Out-of-Order) Cortex-A15 and L1/L2 cache configuration...
build/ARM/sim/simulate.cc:107: info: Entering event queue @ 0.  Starting simulation...
build/ARM/sim/syscall_emul.cc:73: warn: ignoring syscall set_robust_list(...)
build/ARM/sim/syscall_desc.hh:204: fatal: Syscall 293 out of range
Memory Usage: 8515668 KBytes

Is this relevant to the 64 bits?
I can not change the version because I have to convert gem5 outputs to McPAT inputs, and no project is available for the last version of gem5.

aarch64-none-linux-gnu-gcc -static hello.c -o hello-arm worked.


Modifications for docker compatibility

Hi,

added the nodaemon option as per the Supervisor spec.
added a test to ensure supervisorctl is actually running before trying to update it (this is because it does not run during docker builds, only at runtime)
added the ability to add an autostart service without starting it immediately

The last of those three is the only one I see as potentially changing the behaviour of this module, but only to what is the standard functionality for Puppet services, i.e. enable and ensure should be separate parameters.

LGTM


[NTRN-163] add dex stargate tests

task: https://hadronlabs.atlassian.net/browse/NTRN-163
the code is mostly a copy+paste from here: https://github.com/neutron-org/neutron-integration-tests/pull/240 with a few changes/adaptations

https://github.com/neutron-org/neutron-tests/actions/runs/7111070219

https://github.com/neutron-org/neutron-tests/actions/runs/7111070219

https://github.com/neutron-org/neutron-tests/actions/runs/7206923966

https://github.com/neutron-org/neutron-tests/actions/runs/7206923966


Appstudio update test-component-pac-cvqq

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-cvqq-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
28 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
17 seconds
deprecated-base-image-check

✅ Succeeded
16 seconds
inspect-image

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
47 seconds
clamav-scan

✅ Succeeded
19 seconds
sbom-json-check

✅ Succeeded
9 seconds
optional-label-check

✅ Succeeded
9 seconds
label-check

✅ Succeeded
5 seconds
show-sbom

✅ Succeeded
6 seconds
show-summary

Pipelines as Code CI/test-component-pac-cvqq-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
13 seconds
clone-repository

✅ Succeeded
44 seconds
build-container

✅ Succeeded
10 seconds
inspect-image

✅ Succeeded
9 seconds
deprecated-base-image-check

✅ Succeeded
39 seconds
clamav-scan

✅ Succeeded
8 seconds
clair-scan

✅ Succeeded
9 seconds
sbom-json-check

✅ Succeeded
13 seconds
optional-label-check

✅ Succeeded
13 seconds
label-check

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
10 seconds
show-summary


Saving as PBIT file results in an corrupt file

When opening a BIM-file and saving it as a PBIT file a corrupt PBIT file is created.
The exported PBIT file is not a zip-archive with the expected content(DataMashup, DataModelSchema, DiagramState etc. etc.), but is only a JSON file with the model-definition inside it.
I tried to copy this exported PBIT file into an empty PBIT I generated with PBI Desktop, by replacing the DataModelSchema file but this didn't result in an valid file as well. (FormatException: Input file or data stream does not conform to the expected file format specification.)

Removed the "*.pbit" option from the "Save As..."-dialog, as it is not currently possible to create a .PBIT file from scratch (opening an existing .PBIT file and using the regular "Save"-option will still work, however).

Well, if you open a PBIT file how do you save it with another name? It seems to me that now you are forced to rename the PBIT in advance. Would it be possible to remove the *pbit option only if you don't open an existing PBIT?

You’re right. “Save As...” should work for PBIT when such a file was opened in the first place. Will provide a fix shortly.


revert netlink

Revert "Enhance vxlan tests"
Revert "Add kubeproxy unit tests"
Revert "Add hook to mock cni.Discover"
Revert "Use iptables interface in kubeproxy"
Revert "Use netlink interface in kubeproxy"
Revert "Add netlink interface and fake"

Closed, it's still failing, so it was simply a herring


wrong cocoapod

your cocoapod spec on cocoapod.org is downloading RKNotificationHub that is a code that has nothing to do with notifications.

interesting, i'll look into it. i just double checked my podspec and it looks ok on my side

oh i found the issue. thanks for letting me know! i'm updating it now


Update: Tencent.QQ version <IP_ADDRESS>849

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

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

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

Microsoft Reviewers: Open in CodeFlow

/azp run


don't call the zookeeper host strings URLs

I spent a few minutes trying to guess what the scheme part might be. Documentation would be better if it doesn't say it is expecting a format it isn't expecting.

That "details" link for the failed test is a 404.


Add captcha?

Thoughts on adding captcha or some required field that would reduce spam?

Could do that. If it's not a proper captcha it'll just get added to the
spammers' bag of tricks someday...
On Thu, Oct 1, 2015 at 1:28 PM, Samantha Combs<EMAIL_ADDRESS>wrote:

Thoughts on adding captcha or some required field that would reduce spam?
—
Reply to this email directly or view it on GitHub
https://github.com/punkave/apostrophe-forms/issues/33.

--
*THOMAS BOUTELL, *DEV & OPS
P'UNK AVENUE |<PHONE_NUMBER>  |  punkave.com

We should definitely not wing it though. There's recaptcha, it's a service,
we could make it optional to use it.
On Thu, Oct 1, 2015 at 1:37 PM, Tom Boutell<EMAIL_ADDRESS>wrote:

Could do that. If it's not a proper captcha it'll just get added to the
spammers' bag of tricks someday...
On Thu, Oct 1, 2015 at 1:28 PM, Samantha Combs<EMAIL_ADDRESS>wrote:

Thoughts on adding captcha or some required field that would reduce spam?
—
Reply to this email directly or view it on GitHub
https://github.com/punkave/apostrophe-forms/issues/33.

--
*THOMAS BOUTELL, *DEV & OPS
P'UNK AVENUE |<PHONE_NUMBER>  |  punkave.com

--
*THOMAS BOUTELL, *DEV & OPS
P'UNK AVENUE |<PHONE_NUMBER>  |  punkave.com

Closing now that this is in the 2.x version.


EvalError: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive

I am trying to use alasql in an browser environment, when i try to load the script which has alasql bundled within it is giving
EvalError: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive
Based on content security policy we can't use those JS functions mentioned in this link
It seems alasql is using new Function() which triggers the CSP error. how can we resolve this?

AlaSQL is built around creating code. for new functions. If you are not allowed to create new functions then AlaSQL cant help you (until we made a version that preprocesses the functions as part of the build step - but we are not there yet)


Add map panel

What?
マップ表示パネルを追加
Why?
マップを表示したい
Screenshot or video
https://user-images.githubusercontent.com/13210107/146302614-3c983e0a-a97c-4b90-ae58-25110bc341f9.mov

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: yusukefs
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

現在位置の表示と合わせて動かす機能は別PRで追加します

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: WatanabeToshimitsu, yusukefs
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


[ClangImporter] Default optional "options" dictionary params to nil, not [:].

When a parameter has distinct "nil" and "empty" values, "nil" generally represents the default settings, while "empty" is explicitly cleared.
rdar://problem/27196867

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

A smoke test on macOS does the following:

Builds the compiler incrementally.
Builds the standard library only for macOS. Simulator standard libraries and
device standard libraries are not built.
lldb is not built.
The test and validation-test targets are run only for macOS. The optimized
version of these tests are not run.

A smoke test on Linux does the following:

Builds the compiler incrementally.
Builds the standard library incrementally.
lldb is built incrementally.
The swift test and validation-test targets are run. The optimized version of these
tests are not run.
lldb is tested.

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

@DougGregor Mind spot-checking this?
Not adding to swift-ci right now because the bots have more serious things going on.

@swift-ci Please test

Linux failure unrelated (also occurred on master).

Over to Ted to merge.

@swift-ci smoke test linux

@tkremenek Linux smoke test passed.


Support OS X

Mostly small changes to the C code, and trying to work with the few sysctls the folks over at Cupertino still let unprivileged mortals use. I want to call out the 64 bit dev/ino -> 32 bit in the VFS code (that struct is also accessed from Rust), the !O_TMPFILE fallback code path (now the main code path for temporary files on OS X), and the topmost datasync commit.
The OFD locks with "private" fcntl number are fun, but overall feel unlikely to break.

Patches look ok. Built and tested with 1.66.0 on a Monterey M1.


REFACTOR: Refactor full_axis argument

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. What kind of performance improvements would you like to see with this new API?
full_axis at the virtual partition level is used as a flag to tell the partition whether to block partition after or to materialize the result as a single partition - we should probably change it from full_axis to a more descriptive name that better reflects its usage.

I think we can also stop making it a property of the axis object, and instead control the full_axis behavior with arguments to apply. apply seems to be the only thing that uses the full_axis argument.


Build new RPM packages

Need to build all new RPM packages and also setup a place to push them to (repo). I will work to see if we can get an Artifactory Pro license for open-source from Jfrog.

We've used bintray in the past.

I setup a Bintray account for Mantl, but it would also be nice to have Artifactory for package and build management.

I just rebuilt almost all of the RPM packages. They are available here: https://bintray.com/mantl/rpm-packages
MISSING PACKAGES

vault-mantl
vault
old
mesos
marathon
kubernetes
journalbeat
distributive
consul-k8s-0.6.4-4.centos.x86_64.rpm
consul-k8s-0.6.4-3.centos.x86_64.rpm
calico

ADDITIONAL PACKAGES

traefik-config-scripts
consul-kubernetes

RPM Repo
[bintraybintray-mantl-rpm-packages]
name=bintray-mantl-rpm-packages
baseurl=https://dl.bintray.com/mantl/rpm-packages
gpgcheck=0
repo_gpgcheck=0
enabled=1

I just built a new version of Vault: https://bintray.com/mantl/rpm-packages/vault/0.7.0-0