change nuget package version number for pre release build

Current coverage is 76.22%

Merging #337 into master will increase coverage by +1.20% as of b81b01a

@@            master    #337   diff @@
======================================
  Files           41      41
  Stmts         4076    4076
  Branches       355     353     -2
  Methods
======================================
+ Hit           3058    3107    +49
+ Partial        149     148     -1
+ Missed         869     821    -48

Review entire Coverage Diff as of b81b01a

Powered by Codecov. Updated on successful CI builds.

LGTM.


Not performing auto-anything, no icon in the status bar

Hi there, thank you very much for the extension! It will save me from a lot of work if I can get it to work!
Unfortunately, though, I really don't know what to say other than that it doesn't work for me. I tried it with the default settings and non-default setting, trying to get it to auto-do stuff every 5s, commit on close etc. None worked. Then I noticed that the icon in the status bar is not visible, which I think might be telling of something wrong. I only saw it once, but it disappeared very quickly after I clicked on it, and I don't know what to do to see it again.
Update, as I'm writing this: It happened again, while I was tinkering with the settings! It did sync the folder with git, but then the icon disappeared again. I don't know what triggered the extension to work, though.
I know I'm not providing much info, but I really don'T know what to do. I'd be happy to provide more info if asked.
Lastly, I'm using this in a LaTeX directory, and I use the auto features to sync the folder with Overleaf via github. Maybe this is relevant somehow?

I'm experiencing this issue as well.
GitDoc v0.1.0 VsCode v1.83.1 on Windows 10

I hope you all figured it out... but for future viewers... make sure you follow the instructions to enable it.  Then you'll see the "mirror" icon at the bottom of VS Code.

I'm not able to repro this issue, and so I think there may have been a temporary regression in VS Code for a bit. That said, I'm going to close this for now, and please reopen it if you're still encountering a problem 🙏


[Q] What is gorilla?

Sorry, I'm new to wandb development. What are all of the env vars related to "GORILLA_*" for? I've never heard of gorilla, can't find what it is referencing.
Thanks.

Hi Stanley, you can ignore those environment variables. Those are internal use for our backend.

May I ask @stroypet where were you seeing these env vars?

Here's the list of user-facing environment variables: https://docs.wandb.ai/guides/track/advanced/environment-variables

Ah I see, okay. Thanks for the list. I was testing out the dockerized version for a potential use case, ended up poking around inside the docker image and got curious.


Pre-empted driver quitting with a .close

See https://github.com/mozilla/geckodriver/issues/1151. It looks like at least Firefox will annoyingly remain open if a page has certain kinds of modal dialogs.
Although it's a teeny bit messy, I don't think it can hurt to really close the browser.

I hope this also fixes an issue with Safari that I've observed a while ago. Let me check the changes locally, before merging this in.
Thanks for doing this!

Ping @alexeyraspopov - any update? 😊

Sorry for this huge delay. I didn't have enough time to continue this project. I'm really sorry.


feat(axisPointer): trigger axisPointer when data is null (with echarts.connect)

Brief Information
This pull request is in the type of:

[ ] bug fixing
[x] new feature
[ ] others

What does this PR do?
This PR adds a triggerOnNull option to the axisPointer that enables the triggering of the axisPointer on null values when using the echarts.connect or dispatchAction API.
Fixed issues
None.
Details
Before: What was the problem?
Prior to this PR, when connecting multiple charts using echarts.connect with trigger set to axis, the axisPointer would not get triggered if the value in the connected chart was null.
An example of this can be seen in the image below (https://codesandbox.io/s/echarts-without-toggleonnull-fy4g4d?file=/src/index.js):

After: How does it behave after the fixing?
After this PR, the user can set the option to trigger the axisPointer on null values using the triggerOnNull option, like below:
axisPointer: {
    triggerOnNull: true
}

This enables them to trigger the axisPointer on the connected charts even if those do not have a value, or their value is null or undefined.
Note: axisPointer's snap property takes precedence over this feature and should be set to false in the xAxis for this to work.

Document Info
One of the following should be checked.

[ ] This PR doesn't relate to document changes
[ ] The document should be updated later
[x] The document changes have been made in https://github.com/apache/echarts-doc/pull/349

Misc
ZRender Changes

[ ] This PR depends on ZRender changes (ecomfe/zrender#xxx).

Related test cases or examples to use the new APIs
N.A.
Others
Merging options

[x] Please squash the commits into a single one when merging.

Other information
The documentation has been updated in this PR: https://github.com/apache/echarts-doc/pull/349

Thanks for your feedback @Ovilia! I have added some test cases. Please let me know if anything else is required 🙂.


component prop not available in typescript definition

As mentioned in docs, the TableBody has a component prop. It's defined in TableBody.js but not in d.ts.
The same issue in others components related to table, like:

Table
TableRow
TableCell
TableHead
TableBody
TableFooter
TablePagination

Tech
Version

Material-UI
1.0.0-beta.21

React
16.1.1

Typescript
2.6.1

Thanks, @danilobjr! Seems like you know what needs to be added, care to make a PR? 😄


DDLS: ignore ACTFLAG and CHGFLAG

Changes to these components disrupt me for nothing.
I do not believe these components needs to be versioned.

issue https://github.com/larshp/abapGit/issues/1239
downport to 702, perhaps make a method for clearing a field

I do understand that there is an issue with indentation, though I have no idea what is the correct amount of whites paces /o.
But I have no idea what's wrong on the line 278 :(

OK.
Am I supposed to run abaplint locally to figure out how to fix the issues?
Are we supposed to keep master working on ancient, legacy ABAP?

abaplint helps finding the language elements which are not compatible with 702 when opening the PR, some errors are found by people installing abapGit on 702
Target version for abapGit is 702, as stated in the README

Yes, I am going through CONTRIBUTING.md. To be honest, quite hostile requirements :) - like the crazy thing called "Pretty printer" which produces unnecessary white space change commits that have no real use - why can't we just type everything lower case - so we do no need to hold shift nor we need to use Pretty "commit-uglifier" printer?

BTW, I code in vim on my workstation, hence I have no pretty printer handy :)

Hmm, I have no idea how to populate an internal table on 702 :) - my ABAP skills are so weak -  I started last year with ABAP 7.5 :D

APPEND 'AS4USER' TO lt_clr_comps.
I like to keep things consistent. Yeah, pretty printer is not perfect, I wish SAP would provide better tooling.
abapGit is kinda special, many customers still run 700, so limiting to 702 still leaves out some users. But 702 introduced a lot of nice language features 😉 Some day I hope to be able to code abapGit in 740 syntax and then have it automagically downported to 702, but tooling...

Amended and abaplint quite. Thank you for your guidance!

Perhaps, io_xml->add can have an optional list of ignored components.

I see only some activation and statistics uses. One could expect that the flag gets changed by pulling the sources and hence the activation should run.
Hmm, maybe, we should set the flag to some value different than '' in the method deserialize.

Seems to me that the field CHGFLAG is changed during activation (CL_DD_DDL_HANDLER~ACTIVATE -> CL_DD_DDL_VIEW~ACTIVATE -> CL_DD_DDL_VIEW~GET_RELEVANT_DELTA )

Hmm, I have the feeling that cleared CHFLAG has the effect of no-recording in transport task. I am all for setting CHFLAG  to some arbitrary value after pull. Will do some test before I jump into a conclusion.


Add TaintClusterSucceed and update TaintClusterFailed

This closes #438
Added TaintClusterSucceed event to Cluster object, and merged TaintClusterByConditionFailed and RemoveTargetClusterFailed to TaintClusterFailed.
Deployment preview: https://deploy-preview-440--karmada.netlify.app/docs/next/reference/instrumentation/event

/kind documentation


[image_picker][web] cancel cause picker to never return

Steps to Reproduce

clone this repository or use the code sample below
run flutter run -d chrome
tap the fab
when the picker window show up choose cancel

Expected results:

should return null

Actual results:

never returns

code sample
import 'package:flutter/material.dart';
import 'package:image_picker/image_picker.dart';

void main() {
  runApp(const PickerFilesProvider(child: MaterialApp(home: MyHomePage())));
}

Future<Iterable<XFile>> pickFiles() async {
  try {
    final maybeFiles = await ImagePicker().pickMultiImage();
    return [if (maybeFiles != null) ...maybeFiles];
  } on Exception catch (e, s) {
    debugPrint('$e, $s');
    return [];
  } on Error catch (e) {
    debugPrint('$e, ${e.stackTrace}');
    return [];
  }
}

extension XfilesNamesX on Iterable<XFile> {
  Iterable<String> get names sync* {
    for (final file in this) {
      yield file.name;
    }
  }
}

class PickerFilesProvider extends StatefulWidget {
  final Widget child;
  const PickerFilesProvider({
    required this.child,
  }) : super(key: const ValueKey('PickerFilesProvider'));

  @override
  State<PickerFilesProvider> createState() => _PickerFilesProviderState();
}

class _PickerFilesProviderState extends State<PickerFilesProvider> {
  late final ValueNotifier<Iterable<String>> _notifier;

  @override
  void initState() {
    super.initState();
    _notifier = ValueNotifier(<String>[]);
  }

  @override
  void dispose() {
    _notifier.dispose();
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return _PickedFiles(
      child: widget.child,
      notifier: _notifier,
    );
  }
}

class _PickedFiles extends InheritedWidget {
  final ValueNotifier<Iterable<String>> notifier;
  const _PickedFiles({
    required this.notifier,
    required Widget child,
  }) : super(key: const ValueKey('PickedFiles'), child: child);

  static _PickedFiles of(BuildContext context) {
    final _PickedFiles? result =
        context.dependOnInheritedWidgetOfExactType<_PickedFiles>();
    assert(result != null, 'No PickedFiles found in context');
    return result!;
  }

  @override
  // ignore: avoid_renaming_method_parameters
  bool updateShouldNotify(_) => false;
}

extension PickedFilesX on BuildContext {
  ValueNotifier<Iterable<String>> get pickerfiles =>
      _PickedFiles.of(this).notifier;
}

class PickerButton extends StatefulWidget {
  const PickerButton({
    final key = const ValueKey('PickerButton'),
  }) : super(key: key);

  @override
  State<PickerButton> createState() => _PickerWidgetState();
}

class _PickerWidgetState extends State<PickerButton> {
  late final ValueNotifier<bool> _busy;

  @override
  void initState() {
    super.initState();
    _busy = ValueNotifier(false);
  }

  @override
  void dispose() {
    _busy.dispose();
    super.dispose();
  }

  void _pickFiles() async {
    _busy.value = true;
    context.pickerfiles.value = (await pickFiles()).names;
    _busy.value = false;
  }

  @override
  Widget build(BuildContext context) {
    return FloatingActionButton(
      child: ValueListenableBuilder<bool>(
          valueListenable: _busy,
          builder: (context, busy, _) => busy
              ? const CircularProgressIndicator(color: Colors.black)
              : const Icon(Icons.upload)),
      onPressed: _pickFiles,
    );
  }
}

class MyHomePage extends StatelessWidget {
  const MyHomePage({
    final key = const ValueKey('MyHomePage'),
  }) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return const Scaffold(
      body: PickedFilesListView(),
      floatingActionButton: PickerButton(),
    );
  }
}

class PickedFilesListView extends StatelessWidget {
  const PickedFilesListView({
    final key = const ValueKey('PickedFilesListView'),
  }) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return ValueListenableBuilder<Iterable<String>>(
      valueListenable: context.pickerfiles,
      builder: (context, names, _) => ListView(children: [
        for (final name in names) Center(child: Text(name)),
      ]),
    );
  }
}

pubspec
environment:
  sdk: '>=2.14.3 <3.0.0'
  flutter: ^2.5.2

dependencies:
  flutter:
    sdk: flutter
  image_picker: ^0.8.4

dev_dependencies:
  flutter_lints: ^1.0.4

flutter:
  uses-material-design: true

doctor
[✓] Flutter (Channel stable, 2.5.3, on macOS 11.6 20G165 darwin-x64, locale en-EE)
    • Flutter version 2.5.3 at /Users/francesco/fvm/versions/stable
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18116933e7 (5 days ago), 2021-10-15 10:46:35 -0700
    • Engine revision d3ea636dc5
    • Dart version 2.14.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/francesco/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 13.0, Build version 13A233
    • CocoaPods version 1.11.0

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

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)

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

[✓] Connected device (3 available)
    • Pixel 3a (mobile) • 965AY0WP5C • android-arm64  • Android 11 (API 30)
    • macOS (desktop)   • macos      • darwin-x64     • macOS 11.6 20G165 darwin-x64
    • Chrome (web)      • chrome     • web-javascript • Google Chrome 94.0.4606.81

• No issues found!

I guess no progress? Just now faced this issue myself.

I also have the same problem that occurs only on the web. Were you able to find a workaround?

The "cancel" event seems to be coming to web standards. The moment it's available in all browsers, we can hook it up. Don't despair:
https://github.com/whatwg/html/pull/6735

Also interesting, there's a new showPicker API coming to trigger the file selector, rather than faking a "click" on the button!

This problem may be related to #90779.
Too long waiting time needing loading indicators instead,
but the cancellation event cannot be obtained on the Web

I'm almost sure that #90779 is caused by a sub-optimal way of initializing XFiles on the web, where there isn't a constructor that can directly accept the File/Blob from the browser (instead, it needs to copy bytes, and the larger the image, the SLOWER that process is).
We have an issue tracking that problem: https://github.com/flutter/flutter/issues/91869

There sure has to be a way, because file_picker library returns null after cancel.
Looking at the code, I think it is using window focus event.
Maybe it would be worth a try?

I keep experiencing this problem since a few months with file_selector and image_picker on the web

@lukas-h makes sense, both plugins use the same technique in the browser (an input type=file).

Unassigning myself, since I won't be able to work on this in the near future. Apologies!

Any update guys? I facing the same issues too.

The Chromium cancel event is being worked on here, it seems that all other browsers have already landed implementations of the cancel event for the file inputs.

I am able to reproduce this issue using the latest version of the image_picker package and on the latest stable and master channels.
Code Sample
  flutter doctor -v
[✓] Flutter (Channel master, 3.11.0-2.0.pre.55, on macOS 13.3 22E252 darwin-arm64, locale en-NG)
    • Flutter version 3.11.0-2.0.pre.55 on channel master at /Users/dammya/fvm/versions/master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 835b892d7f (10 days ago), 2023-05-07 01:30:22 +0530
    • Engine revision 23f730efbf
    • Dart version 3.1.0 (build 3.1.0-83.0.dev)
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
    • Android SDK at /Users/dammya/Library/Android/sdk
    • Platform android-33, build-tools 32.1.0-rc1
    • ANDROID_HOME = /Users/dammya/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.11.3

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

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Community Edition (version 2022.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

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

[✓] VS Code (version 1.78.0)
    • VS Code at /Users/dammya/.Trash/Visual Studio Code 20.07.05.app/Contents
    • Flutter extension version 3.50.0

[✓] Connected device (4 available)
    • Damilola’s iPhone (mobile) • 71c843fa5f3dec767999f36224653c0faa78660e • ios            • iOS 16.4 20E247
    • iPhone 14 Pro Max (mobile) • D7F3302D-D66F-4B89-B8CF-DBEE1CDB5449     • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-4 (simulator)
    • macOS (desktop)            • macos                                    • darwin-arm64   • macOS 13.3 22E252 darwin-arm64
    • Chrome (web)               • chrome                                   • web-javascript • Google Chrome 113.0.5672.92

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

• No issues found!

[✓] Flutter (Channel stable, 3.10.0, on macOS 13.3 22E252 darwin-arm64, locale
    en-NG)
    • Flutter version 3.10.0 on channel stable at /Users/dammya/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 84a1e904f4 (7 days ago), 2023-05-09 07:41:44 -0700
    • Engine revision d44b5a94c9
    • Dart version 3.0.0
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version
    32.1.0-rc1)
    • Android SDK at /Users/dammya/Library/Android/sdk
    • Platform android-33, build-tools 32.1.0-rc1
    • ANDROID_HOME = /Users/dammya/Library/Android/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.11.3

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

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Community Edition (version 2022.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

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

[✓] VS Code (version 1.78.0)
    • VS Code at /Users/dammya/.Trash/Visual Studio Code 20.07.05.app/Contents
    • Flutter extension version 3.50.0

[✓] Connected device (4 available)
    • Damilola’s iPhone (mobile) • 71c843fa5f3dec767999f36224653c0faa78660e •
      ios            • iOS 16.4 20E247
    • iPhone 14 Pro Max (mobile) • D7F3302D-D66F-4B89-B8CF-DBEE1CDB5449     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-4 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-arm64   • macOS 13.3 22E252 darwin-arm64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 113.0.5672.92

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

• No issues found!

could the same fix of https://github.com/flutter/flutter/issues/121328 be applied here?

@iapicca yes, the implementations are not shared now, but the same fix (or extremely similar) could, and should, be applied to both plugins, as Stuart mentioned in the issue you linked.

A fix for this is coming:

https://github.com/flutter/packages/pull/4453

(The same fix for file_selector has already landed here: https://github.com/flutter/packages/pull/3683)


Add methods about invitations in auth-server in Litmus

We need to add methods wrapped invitation APIs in auth-server.

sendInvitation
acceptInvitation
declineInvitation
removeInvitation
listInvitations
getUsersForInvitation

The auth-server documentation is here

i want take the issue !


V1.8.0 patchset

Carries patches from 1.8.0-rc.1. Dev tests are passing.
@s-urbaniak @aaronlevy

lgtm


When I press next without filling in any field, the screen goes to next one. When the required fields are not entered, the next button should not work

Similarly when a person presses prev button, the screen should show a prompt text that all the data entered will be lost


refactor: test check_approval

There were number of missing checks and the for loop was making it very hard to understand. Didn't want to spend too much time on it but I think this is better to follow.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 70.16%. Comparing base (4535a52) to head (e7d8ee1).

@@                    Coverage Diff                     @@
##           chungquantin/feat-nfts     #403      +/-   ##
==========================================================
+ Coverage                   69.97%   70.16%   +0.19%
==========================================================
  Files                          70       70
  Lines                       12975    13055      +80
  Branches                    12975    13055      +80
==========================================================
+ Hits                         9079     9160      +81
  Misses                       3617     3617
+ Partials                      279      278       -1

Files with missing lines
Coverage Δ

pallets/nfts/src/tests.rs
99.90% <100.00%> (+<0.01%)
:arrow_up:

... and 1 file with indirect coverage changes


Client config should support puppet

https://sensuapp.org/docs/latest/reference/clients.html#puppet-attributes

Released in v2.35.0


Log files should be opened read-only

Testing #39572
It is very weird that I can type in log files... Furthermore, typing in the renderer log file generates additional log messages which is even weirder.

Marking this as dup pf #39638


Add version numbers to duplicate template IDs

Specifically, there are 3 types of CosmosDB triggers for C# floating around. Staging templates have 2.x and 4.x and backup/latest have 3.x and 4.x.
It's a bit of a pain to handle, so I'm only showing 4.x templates in verified. Part of this decision was driven that we should probably only recommend the latest version, but it also made our testing suite hard to deal with when there were different choices across latest/staging/backup.

Does this address a specific issue? Can you link it if so?

I'm closing this for now. I'm not consistently seeing this reproduce anymore...


kube-apiserver restart after start  cirros vm

What happened:
I found after I run "virtctl start testvm"  , kube-apiserver restart.
What you expected to happen:
kube-apiserver always run fine.
How to reproduce it (as minimally and precisely as possible):

build k8s cluster via kubeadm
install kubevirt
start cirros vm

Anything else we need to know?:
kube-apiserver  exit after "virtctl start testvm"
[root@master0 ~]# docker ps -a |grep -i api
9678a6da9811        ce0df89806bb           "kube-apiserver --ad…"   5 minutes ago       Up 5 minutes                                     k8s_kube-apiserver_kube-apiserver-master0_kube-system_0402f49bc0fbf16ec28503db1b70c1c8_5
19b6bcd9feee        ce0df89806bb           "kube-apiserver --ad…"   8 minutes ago       Exited (0) 5 minutes ago                         k8s_kube-apiserver_kube-apiserver-master0_kube-system_0402f49bc0fbf16ec28503db1b70c1c8_4
b0e7653190ee        k8s.gcr.io/pause:3.2   "/pause"                 37 minutes ago      Up 37 minutes                                    k8s_POD_kube-apiserver-master0_kube-system_0402f49bc0fbf16ec28503db1b70c1c8_0

kube-apiserver log as following:
I0922 06:14:49.010159       1 controller.go:89] Shutting down OpenAPI AggregationController
I0922 06:14:49.010372       1 controller.go:181] Shutting down kubernetes service endpoint reconciler
I0922 06:14:49.011326       1 apiservice_controller.go:131] Shutting down APIServiceRegistrationController
I0922 06:14:49.011426       1 controller.go:123] Shutting down OpenAPI controller
I0922 06:14:49.016072       1 available_controller.go:416] Shutting down AvailableConditionController
I0922 06:14:49.016554       1 cluster_authentication_trust_controller.go:463] Shutting down cluster_authentication_trust_controller controller
I0922 06:14:49.016651       1 customresource_discovery_controller.go:245] Shutting down DiscoveryController
I0922 06:14:49.016736       1 apiapproval_controller.go:198] Shutting down KubernetesAPIApprovalPolicyConformantConditionController
I0922 06:14:49.016821       1 crd_finalizer.go:278] Shutting down CRDFinalizer
I0922 06:14:49.020326       1 dynamic_cafile_content.go:182] Shutting down request-header::/etc/kubernetes/pki/front-proxy-ca.crt
I0922 06:14:49.020414       1 dynamic_cafile_content.go:182] Shutting down client-ca-bundle::/etc/kubernetes/pki/ca.crt
I0922 06:14:49.020545       1 dynamic_serving_content.go:145] Shutting down aggregator-proxy-cert::/etc/kubernetes/pki/front-proxy-client.crt::/etc/kubernetes/pki/front-proxy-client.key
I0922 06:14:49.020649       1 dynamic_cafile_content.go:182] Shutting down request-header::/etc/kubernetes/pki/front-proxy-ca.crt
I0922 06:14:49.024460       1 nonstructuralschema_controller.go:198] Shutting down NonStructuralSchemaConditionController
I0922 06:14:49.024585       1 establishing_controller.go:87] Shutting down EstablishingController
I0922 06:14:49.024700       1 naming_controller.go:302] Shutting down NamingConditionController
I0922 06:14:49.024796       1 autoregister_controller.go:165] Shutting down autoregister controller
I0922 06:14:49.024913       1 crdregistration_controller.go:142] Shutting down crd-autoregister controller
I0922 06:14:49.026532       1 tlsconfig.go:255] Shutting down DynamicServingCertificateController
I0922 06:14:49.053499       1 dynamic_serving_content.go:145] Shutting down serving-cert::/etc/kubernetes/pki/apiserver.crt::/etc/kubernetes/pki/apiserver.key
I0922 06:14:49.053713       1 dynamic_cafile_content.go:182] Shutting down client-ca-bundle::/etc/kubernetes/pki/ca.crt
E0922 06:14:49.081577       1 status.go:71] apiserver received an error that is not an metav1.Status: &errors.errorString{s:"context canceled"}
E0922 06:14:49.101018       1 status.go:71] apiserver received an error that is not an metav1.Status: &errors.errorString{s:"context canceled"}
E0922 06:14:49.105319       1 status.go:71] apiserver received an error that is not an metav1.Status: &errors.errorString{s:"context canceled"}
E0922 06:14:49.159646       1 status.go:71] apiserver received an error that is not an metav1.Status: &errors.errorString{s:"context canceled"}
I0922 06:14:49.160313       1 trace.go:205] Trace[700552469]: "Get" url:/api/v1/namespaces/kubevirt/endpoints/virt-controller,user-agent:virt-controller/v0.0.0 (linux/amd64) kubernetes/$Format,client:<IP_ADDRESS> (22-Sep-2020 06:14:45.875) (total time: 3284ms):
Trace[700552469]: [3.28455998s] [3.28455998s] END
E0922 06:14:49.165036       1 status.go:71] apiserver received an error that is not an metav1.Status: &errors.errorString{s:"context canceled"}
I0922 06:14:49.188999       1 secure_serving.go:241] Stopped listening on [::]:6443
E0922 06:14:49.757585       1 controller.go:184] StorageError: key not found, Code: 1, Key: /registry/masterleases/<IP_ADDRESS>, ResourceVersion: 0, AdditionalErrorMsg:
~

Environment:

KubeVirt version (use virtctl version):

[root@pcentos ~]# virtctl version
Client Version: version.Info{GitVersion:"v0.32.0", GitCommit:"44d3011eb09b1488d181439dd0bf54f58ebb148b", GitTreeState:"clean", BuildDate:"2020-08-11T19:31:18Z", GoVersion:"go1.12.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{GitVersion:"{gitVersion}", GitCommit:"{gitCommit}", GitTreeState:"{gitTreeState}", BuildDate:"{buildDate}", GoVersion:"go1.12.8", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes version (use kubectl version):

[root@pcentos ~]# kubectl version
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.1", GitCommit:"206bcadf021e76c27513500ca24182692aabd17e", GitTreeState:"clean", BuildDate:"2020-09-09T11:26:42Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.1", GitCommit:"206bcadf021e76c27513500ca24182692aabd17e", GitTreeState:"clean", BuildDate:"2020-09-09T11:18:22Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"}

VM or VMI specifications:
kubevirt.github.io/labs/manifests/vm.yaml

Cloud provider or hardware configuration:

OS (e.g. from /etc/os-release):
[root@pcentos ~]# cat /etc/redhat-release
CentOS Linux release 7.8.2003 (Core)

Kernel (e.g. uname -a):
[root@pcentos ~]# uname -a
Linux pcentos 3.10.0-1127.el7.x86_64 #1 SMP Tue Mar 31 23:36:51 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
[root@pcentos ~]#

Install tools:

Others:

@todaygood could you check the kube-apiserver logs from the instance which crashed? Should be something like kubectl logs -p (-p for previous). The provided logs don't contain any hint of a crash.

I rebuild the envionment  and met this issue , but this time , I didn't found apiserver recoved, so I can't get the output of  "kubectl logs -p kube-apiserver"
[root@pcentos test-vm]# kubectl get pod -A
Unable to connect to the server: net/http: TLS handshake timeout
[root@pcentos test-vm]# kubectl get pod -A                                         # wait for several minutes, run again
The connection to the server master0:6443 was refused - did you specify the right host or port?
[root@pcentos test-vm]# kubectl get pod -A                                         # wait for several minutes, run again
Unable to connect to the server: net/http: TLS handshake timeout

and I find golang dumpstack  in kube-apiserver container's log  , please check file:
issue4228-kube-apiserver.zip

@todaygood I think that the apiserver may have an issue in your k8s build. It looks like it just crashes when virtctl tries to do the /start-REST call to our aggregated apiserver. This looks like an apiserver bug. I would suggest updating k8s from 1.19.0-rc0 to 1.19.2.

I faied to reproduce it, now I run 0.33  smoothly , so close it.


feat: Upgrade dependencies and allow Laravel v11

This upgrade allows almost all dependencies to be upgraded to their latest versions and allows Laravel v9, v10, and v11 to use the driver.
Closes #20

Looks like builds are failing on PHP 8.1. Support for it can be dropped and PHP 8.2 can be the minimum.

Hmm, looks like SurrealDB v2 will need a bit more effort. I remove it from here and will do a separate PR about that with the switch to the SDK itself.


SAKIII-4066 change lhnav to use one list for both public/private items

https://jira.sakaiproject.org/browse/SAKIII-4066

Merged via squash


Create Issue: #4.txt

Issue: #4

Hey @rndastech
Thanks for opening this PR 🚀. Mentor will review your pull request soon and till then, keep contributing and stay calm.
Thanks for contributing in OpenCode'24 ✨✨!

Hey @rndastech
Your PR has been merged 🥳🥳 and you have earned 10 points.
Thanks for contributing in OpenCode'24 ✨✨


Forbid aliases for certain imports

It would be nice if adding ( "List.Extra", "" ) to the config meant that List.Extra should never be aliased

Just noticed that this is similar to #35


feat(instrumentation-fetch)! Passthrough original request to applyCustomAttributes

[!NOTE]
This PR currently contains an extra commit from #5268. I will rebase once that is merged.

Which problem is this PR solving?
Currently, the browser fetch() instrumentation unconditionally clones the response object for every request, in order to preserve the ability for the applyCustomAttributes to consume the response body. This cloned response doesn't get consumed/released until the body has been streamed and read entirely, which forces the browser to buffer and retain the entire response body, creating unnecessary memory pressure on large or long-running response streams. In extreme cases, this is effectively a memory leak and can cause the browser tab to crash.
Fixes #4888
Short description of the changes
The offending code was added in #2497.  This is certainly a breaking change, and we can discuss the mitigations below.
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Unit tests

Checklist:

[x] Followed the style guidelines of this project
[x] Unit tests have been added
[ ] Documentation has been updated

Background – the browser fetch() API
When fetch() was added to the browser, they made some deliberate design choices/improvements:

Everything is async/promise-based (as opposed to event-based in XHR).
Breakdown the request/response lifecycle/phases more granularly (as opposed to a single onreadystatechange hook/event).
Work better/more efficiently with large/long-running response streams, reduce unnecessary buffering.

Concretely:

fetch() returns a promise that resolves with a Response object, which can happen as soon as the headers are fully received.
 In addition, those APIs are methods that returns the data, rather than exposing the body as a property on the response itself. This allows the browser to stream the response in the background, and have more liberty in how the implement/fulfill those APIs. For example, in await response.json(), a browser could choose to use a streaming JSON parser and discard/move the underlying bytes as they arrive, reducing the need for buffering/copying bytes unnecessarily.
To facilitate the above, no matter which ones of the APIs are used to consume the response body, it can only be consumed once per Response object. This is necessary to achieve the goals in the previous bullet point – if you are allowed to call await response.json() followed by await response.text() sometime later, the optimization in (2) is no longer possible, and the browser must buffer the response bytes for the lifetime of the response object, and each call to those APIs will have to copy the underlying data.
The Response.clone() API provides a way to opt-in to buffering/copying the response body in cases where there are multiple consumers. This must be called before the response body has been read.

Background – the original feature request #2497
As mentioned above, the current instrumentation code unconditionally call .clone() on every response:
https://github.com/open-telemetry/opentelemetry-js/blob/8ab52d547990692e2f7a4dc5242ec61a3e42971e/experimental/packages/opentelemetry-instrumentation-fetch/src/fetch.ts#L375
It then holds onto the cloned response object, until the response body has been fully streamed/read:
https://github.com/open-telemetry/opentelemetry-js/blob/8ab52d547990692e2f7a4dc5242ec61a3e42971e/experimental/packages/opentelemetry-instrumentation-fetch/src/fetch.ts#L383
This was introduced way back in #2497. Effectively, this code "reserves the right" to read the response body in applyCustomAttributesOnSpan(), which doesn't get called until the entire response is available, forcing the browser to buffer and hold onto the underlying bytes in the meantime.

[!NOTE]
There are actually two .clone()s here. resClone predates #2497, and was added in #2203 to ensure the span timing covers the whole lifecycle of the request/response, rather than just up to the point where the headers are sent. This .clone() is still problematic in that it forces the browser to copy the bytes as there are now more than one consumer, but since it uses the streaming-based API which discard the read bytes as soon as they are become available, it at least shouldn't contribute to the memory pressure problem which is the focus of this PR. We should probably still revisit that to see if there are better ways to accomplish this by hooking into resource timing API, but it's nontrivial and out-of-scope here. Removing the second clone alone should be sufficient to address the memory pressure problem reported in #4888.

This behavior/"feature" is fundamentally unsound, as it creates unnecessary memory pressure for all fetch() requests. This may be negligible in small responses, but when streaming a large response body this can be especially problematic. Worse, in case of long-running response streams, this is effectively a memory leak. At the extremes, as reported in #4888, this can cause the browser tab to run against its allowed memory limit and crash.
What now?
I don't see how we can reasonably support this feature without running into the fundamental problem described above. To that end, and considering that this is still an experimental package, I suggest that we drop it the feature and send it back to the drawing board.
The original feature request was too sparse on details. It was unclear what it was trying to accomplish – specifically why would it be useful to be able to read the response body in applyCustomAttributes(). I could speculate on the use cases, but I also think the design of the feature is itself flawed – applyCustomAttributes() is meant to be a synchronous hook, but by design, doing anything with the response body necessitates async operations. This means code like the test added in #2497 is also fundamentally broken, and probably only working due to this internal delay, which is certainly unintentional/unreliable. Future refactors (e.g. the fix for #5122) could very well remove the need for this delay and the code will subtly break.
So, I think the best course of action is to open an issue representing the breakage/feature request, and make a note in the CHANGELOG pointing to the issue, so we can evaluate what, if any, the replacement APIs should look like.

Tests are failing because this PR currently targets next, and #5277 hasn't landed in that branch yet.

Feature was originally contributed by @echoontheway. There isn't a description of the original use case in the PR https://github.com/open-telemetry/opentelemetry-js/pull/2497/files
It has been raised several times in the past that this feature causes memory thrash and leaks. In my opinion, the motivating use case would have to be very convincing in order to keep this feature when it has caused so many issues.

It has been raised several times in the past that this feature causes memory thrash and leaks. In my opinion, the motivating use case would have to be very convincing in order to keep this feature when it has caused so many issues.

the PR was raised then to log the response of fetch api to review the data for business maintainers.

i think it's ok to remove the feature for the moment considering memory pressure for long-running response streams.

Next steps (for me):

[ ] Wait for #5268 to be merged
[ ] Rebase
[ ] Open a new feature-request issue for the removed functionality
[ ] Link to the issue from the CHAGELOG entry


Add Periodic Re-checks to BalancedConsumer

I don't trust Zookeeper.  Very rarely, it fails to send events when topics/brokers/etc change.  We should add a periodic re-check to make sure what the consumer is consuming is what zookeeper thinks it's consuming.

The most important thing to check here is whether the zookeeper nodes created by this call correspond to the internally-held list of partitions. This can run on another background thread that only wakes up once every two or three autocommit cycles.

I think this works, let me know what you think. https://github.com/Parsely/pykafka/pull/171/files


Improved version of the Gradle script

I've added error handling for file reading operations in the checkFlutterSdkLocation task. Now, if there are any issues reading the local.properties file, the build process will fail with a detailed error message explaining the problem. Additionally, I've corrected the dependency resolution for the checkFlutterSdkLocation task to depend on preBuild properly. Issue #22

Hi team
can you please explain me why my merged is blocked. what I have done wrong.


Running out of memory on computing cluster

Hi, I'm trying to run SigProfilerExtractor via SigProfilerExtractorR, and I'm coming across issues running this on my university's shared computing cluster. Despite allocating sufficient memory during the jobs, the tool always exceeds the limit  after performing NMF for the minimum # of signatures, and cannot continue with the rest. SigProfilerExtractor via SigProfilerExtractorR produces no memory issues on my laptop, and I'm only encountering this problem on the cluster (so far it has exceed more than 500G). This issue may possibly be related to this post: https://github.com/AlexandrovLab/SigProfilerExtractor/pull/119
Any insights or suggestions are greatly appreciated. I've listed some environment settings below. Please reach out if you need more details for troubleshooting.

This occurs for both SigProfilerExtractor versions v1.1.4 and v1.1.5
Using a Conda environment with Python v3.7.
Related issue: https://github.com/AlexandrovLab/SigProfilerExtractor/pull/119
JOB_METADATA.txt  attached to post
codlin-nmf-2071206.txt is some command line output.

JOB_METADATA.txt
cmdline-nmf-3071206.txt

Dear @kgeyer,
Sorry for the late reply, and thanks for your interest! Not sure what may be causing this issue in your cluster. Indeed, the PR you mentioned has already been merged into the main branch and was incorporated in version v1.1.5. I would suggest updating to the most recent v1.1.6 and trying the python version of SigProfilerExtractor directly in your cluster (instead of the R wrapper). Please let us know if you are still having issues.

@marcos-diazg Thank you for your response. I'll try this soon, and will let you know how it goes.

Please reopen the ticket if the issue persists. Thank again for your interest!


(#86) compare operators

Implement Operators for (i32, i64):

>
>=
<
<=

Pull Request Test Coverage Report for Build 1637

15 of 51 (29.41%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-2.07%) to 76.644%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

ast/context.go
5
41
12.2%

Totals

Change from base Build 1634:
-2.07%

Covered Lines:
1142

Relevant Lines:
1490

💛  - Coveralls


refactor(userconfig): new generator for SDKv2

About this change—what it does

Add new user config generator for SDKv2
Use TypeSet for arrays with scalar elements

good point @ivan-savciuc

Rebased on master, regenerated docs (description strings are updated only).

Results of migration from v3 straight to  v4 (this version of user_config).

This one is not related to this PR in particular, since not related to user_config but I still would like to mention it here. Let's say we create a simple PG resource in v3 without user_config at all:

resource "aiven_pg" "pg1" {
  service_name = "xxx"
  project = "xxx"
  plan = "startup-4"
}

After  successful creation in v3 and migration to the latest version of user_config we constantly get diff in the plan/apply:
Terraform will perform the following actions:

  # aiven_pg.pg1 will be updated in-place
  ~ resource "aiven_pg" "pg1" {
      - cloud_name              = "google-europe-west1" -> null
        id                      = "aiven-ci-kubernetes-operator/ivans-pg1"
        # (19 unchanged attributes hidden)

        # (2 unchanged blocks hidden)
    }

Even after consecutive terraform apply this diff never goes away, which is a problem.

Now back to migration from v3 causes service recreation:

resource "aiven_pg" "pg2" {
  service_name = "xx"
  project = "xx"
  plan = "startup-4"

  pg_user_config {
    pg_read_replica = true
    pg_service_to_fork_from = aiven_pg.pg1.service_name
  }
}

After migration of the resource from above we get a massive diff and moreover it forces resource recreation, and this issues/diff never disappears even after recreation.
~ pg_user_config {
          - additional_backup_regions = [] -> null
          - backup_hour               = 9 -> null
          - backup_minute             = 42 -> null
          - enable_ipv6               = false -> null
          - ip_filter                 = [
              - "<IP_ADDRESS>/0",
            ] -> null
          - ip_filter_string          = [] -> null
          + pg_service_to_fork_from   = "ivans-pg1" # forces replacement
          - pg_stat_monitor_enable    = false -> null
          - pg_version                = "15" -> null
          - service_to_fork_from      = "ivans-pg1" -> null
          - shared_buffers_percentage = 0 -> null
          - static_ips                = false -> null
          - work_mem                  = 0 -> null
            # (1 unchanged attribute hidden)

          - pglookout {
              - max_failover_replication_time_lag = 60 -> null
            }
        }

There are some other issues but I can reproduce them even without need of migration from v3 to v4 and will highlight them in a separate thread.

A bug found related to boolean behaviour 🐞

I have added a test, and additional cases. All green. Please checkout the test case in files.

@muralibasani please fix the conflicts on this branch


[ISSUE #776] make mqadmin usage information more friendly to user

What is the purpose of the change
Fix issus #776
Brief changelog
make mqadmin usage information more friendly to user
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage increased (+0.01%) to 44.836% when pulling 0a55e4bfd7e08b505874f03247e9327d49af59eb on husterxsp:issue776-fix into 6a573a773a87edbcdcc138614b756019fc280988 on apache:develop.


UPS using '®'  in API responses, causing REXML::ParseException

I'm using ruby 1.9.3p545 and active_shipping 0.12.3.
UPS seems to have started including the '®' symbol in reporting activity of packages. It appears that this is causing an error when active_shipping tries to parse the API response.
Example shipment: 1ZW69Y250398445209
Screenshot:
Calling find_tracking_info for this tracking number results in the following stack trace:
REXML::ParseException: #<REXML::ParseException: #<ArgumentError: invalid byte sequence in UTF-8>
/usr/lib64/ruby/1.9.1/rexml/source.rb:210:in `match'
/usr/lib64/ruby/1.9.1/rexml/source.rb:210:in `match'
/usr/lib64/ruby/1.9.1/rexml/parsers/baseparser.rb:419:in `pull_event'
/usr/lib64/ruby/1.9.1/rexml/parsers/baseparser.rb:183:in `pull'
/usr/lib64/ruby/1.9.1/rexml/parsers/treeparser.rb:22:in `parse'
/usr/lib64/ruby/1.9.1/rexml/document.rb:245:in `build'
/usr/lib64/ruby/1.9.1/rexml/document.rb:43:in `initialize'
/data/food52/shared/bundled_gems/ruby/1.9.1/gems/active_shipping-0.12.3/lib/active_shipping/shipping/carriers/ups.rb:323:in `new'
/data/food52/shared/bundled_gems/ruby/1.9.1/gems/active_shipping-0.12.3/lib/active_shipping/shipping/carriers/ups.rb:323:in `parse_tracking_response'
/data/food52/shared/bundled_gems/ruby/1.9.1/gems/active_shipping-0.12.3/lib/active_shipping/shipping/carriers/ups.rb:121:in `find_tracking_info'
[...]

I propose that active_shipping should sanitize the response before creating the REXML::Document, unless REXML provides a way of gracefully handling cases like these.

I ported UPS to use Nokogiri to parse XML. Can you see if this is still an issue?


[Failing Test]:

What happened?
No response
Issue Failure
Failure: Test is flaky
Issue Priority
Priority: 1 (unhealthy code / failing or flaky postcommit so we cannot be sure the product is healthy)
Issue Components

[X] Component: Python SDK
[X] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam YAML
[ ] Component: Beam examples
[X] Component: Beam playground
[X] Component: Beam katas
[X] Component: Website
[X] Component: Infrastructure
[X] Component: Spark Runner
[X] Component: Flink Runner
[ ] Component: Samza Runner
[X] Component: Twister2 Runner
[X] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Hi @Lucky777178, could you share which tests are failing?

Closing since there is not enough info to investigate. Please share more info if this is still a problem


nvidia card not working inside container

When trying to run the simulation on a new Ubuntu 22.04 installation on a new laptop, the GL windows were not working, meaning that both rviz and gazebo showed the UI, but the 3d scene in both applications is just black.
Trying to run glmark2 inside the container also failed, and stated that the Mesa drivers are being used.

This is now working for me


RetryInterceptor.onError - exceptions handling

Hi @rodion-m
I have tried to use your library in my project. I have several tests of my communication layer including test for incorrect url.
Unfortunately test stops working after adding your interceptor.
Here is what I have discovered.
RetryInterceptor.onError do not handling errors that could arise in this method. For example in my case I have had incorrect url (http    ://github.com with spaces) that makes troubles when I am specifying logPrint function. Interceptor prepare output string for logPrint function and call err.requestOptions.uri which throws exception FormatException: Illegal scheme character (at character 5). This exception bubble out without corresponding handling.
The solution could be simple in my case, just use path instead of uri or something similar in that direction. But I propose you to think about general error handling to avoid issues for example when _retryEvaluator could throw an error.

Hi @solikhver ! Thanks a lot for contributing. I accept that we should change uri to path in logging.
Also, I think that the default retry evaluator should not retry this type of error at all. So, I plan to add something like this in a default retry evaluator:
...
      shouldRetry = error.type != DioErrorType.cancel
                  && error.error is! FormatException;
...

As for me you can wrap any exception that could happens during RetryInterceptor.onError call with your own and do not retry if this type of error is presented. But definitely it shouldn't be unhandled exceptions even if it occurs in evaluator.

The issue is fixed #2af5c2b.
Also, a new parameter  ignoreRetryEvaluatorExceptions is added by default it's false.
Thanks again for contributing!


ARM64

Could MyMonero be packaged for arm64 as either a .appimage or a flatpak? This may be especially useful with the recent introduction of the Pinephone/Librem5 as Linux phones

Will chat with the team and look at the options.

It would also be helpful for the new Apple silicon (m1).

It would also be helpful for the new Apple silicon (m1).

Any updates on getting Electron to at least version 11? (aka the minimum target to build for arm64-darwin)
I tried building the develop branch just now by manually forcing version 11 and the app compiles but is not functional upon launch:
An unexpected application error occurred.

Please let us know of the following error message as it could be a bug:

TypeError: Cannot read property 'app' of undefined
TypeError: Cannot read property 'app' of undefined
    at file:///Applications/MyMonero.app/Contents/Resources/app.asar/local_modules/MainWindow/Views/index.electron.renderer.js:37:38Mozilla/5.0 (Macintosh; Intel Mac OS X 12_0_1) AppleWebKit/537.36 (KHTML, like Gecko) MyMonero/1.2.2 Chrome/87.0.4280.141 Electron/11.5.0 Safari/537.36

So far, only the official monerod and other supporting binaries are arm64 compatible with no issues. There is no Monero wallet with a GUI that runs on arm64-darwin and building the open sourced ones including this ends in varying degrees of failure.


Installation with ROS noetic

Hello.
I am totaly newbie in ROS and I jsut trying to use my ROS camera, that I just receiced :).
https://orbbec3d.com/develop/ is down now, so I deciced to use ROS for my ROS camera.
I've installed ROS as described in http://wiki.ros.org/Installation/Ubuntu and followed instructions for Astra camera - this http://wiki.ros.org/astra_camera and this https://github.com/orbbec/ros_astra_camera .
First question is that command sudo apt install ros-$ROS_DISTRO-rgbd-launch ros-$ROS_DISTRO-libuvc ros-$ROS_DISTRO-libuvc-camera ros-$ROS_DISTRO-libuvc-ros unable to find libuvc packages for ROS:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package ros-noetic-libuvc
E: Unable to locate package ros-noetic-libuvc-camera
E: Unable to locate package ros-noetic-libuvc-ros

How to install them on ROS noetic?
The second one question:
When I am running
cd ~/catkin_ws
catkin_make --pkg astra_camera
I got build errors, I think, it's because apt unable to install libuvc packages:
devusr@devusr-virtual-machine:~/catkin_ws$ catkin_make --pkg astra_camera
Base path: /home/devusr/catkin_ws
Source space: /home/devusr/catkin_ws/src
Build space: /home/devusr/catkin_ws/build
Devel space: /home/devusr/catkin_ws/devel
Install space: /home/devusr/catkin_ws/install
####
#### Running command: "make cmake_check_build_system" in "/home/devusr/catkin_ws/build"
####
-- Using CATKIN_DEVEL_PREFIX: /home/devusr/catkin_ws/devel
-- Using CMAKE_PREFIX_PATH: /home/devusr/catkin_ws/devel;/opt/ros/noetic
-- This workspace overlays: /home/devusr/catkin_ws/devel;/opt/ros/noetic
-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.8.2", minimum required is "3")
-- Using PYTHON_EXECUTABLE: /usr/bin/python3
-- Using Debian Python package layout
-- Using empy: /usr/lib/python3/dist-packages/em.py
-- Using CATKIN_ENABLE_TESTING: ON
-- Call enable_testing()
-- Using CATKIN_TEST_RESULTS_DIR: /home/devusr/catkin_ws/build/test_results
-- Forcing gtest/gmock from source, though one was otherwise available.
-- Found gtest sources under '/usr/src/googletest': gtests will be built
-- Found gmock sources under '/usr/src/googletest': gmock will be built
-- Found PythonInterp: /usr/bin/python3 (found version "3.8.2")
-- Using Python nosetests: /usr/bin/nosetests3
-- catkin 0.8.8
-- BUILD_SHARED_LIBS is on
-- BUILD_SHARED_LIBS is on
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- ~~  traversing 1 packages in topological order:
-- ~~  - astra_camera
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- +++ processing catkin package: 'astra_camera'
-- ==> add_subdirectory(ros_astra_camera)
-- Using these message generators: gencpp;geneus;genlisp;gennodejs;genpy
CMake Error at ros_astra_camera/CMakeLists.txt:8 (find_package):
  By not providing "Findlibuvc.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "libuvc", but
  CMake did not find one.

  Could not find a package configuration file provided by "libuvc" with any
  of the following names:

    libuvcConfig.cmake
    libuvc-config.cmake

  Add the installation prefix of "libuvc" to CMAKE_PREFIX_PATH or set
  "libuvc_DIR" to a directory containing one of the above files.  If "libuvc"
  provides a separate development package or SDK, be sure it has been
  installed.

-- Configuring incomplete, errors occurred!
See also "/home/devusr/catkin_ws/build/CMakeFiles/CMakeOutput.log".
See also "/home/devusr/catkin_ws/build/CMakeFiles/CMakeError.log".
make: *** [Makefile:320: cmake_check_build_system] Error 1
Invoking "make cmake_check_build_system" failed

Tell me please how to solve this issue?

@KhArtNJava Try to install following packages
sudo apt install ros-noetic-rgbd-launch libuvc-dev
And try to build the astra ros wrapper package


Update bulk.js

Not Processed batch should be completed.
Resolve issue #765

Hey, sorry this didn't get reviewed in time, we aren't feature work on master so I'm going to close this in favor of https://github.com/jsforce/jsforce/pull/1481.


Change Travis CI to something else, it's slow and flaky

Android emulator runs really bad on Travis, pretty often we see that instrumentation tests are not starting because emulator is not responding.
Personally, I'd go with Circle CI for now.

CircleCI does indeed seem nice though I've never used it. We could also for a while go and have 2 CI's. I've seen that in other projects too. At the end we'll see who we'll cut loose.

Good idea, I'll connect Circle CI soon (I use it for personal projects, works fine, though I like Travis UI more)

Guess this can be closed @artem-zinnatullin ?

Ok, I'll remove Travis if I'll see failing builds.


raw A/V output on HDMI port

Hi Iizukanao,
Is it possible to get a raw a/v output of picam-streamer on raspberry pi's HDMI port
Thanks and Regards

If you use the -p (or --preview) option, the video will be output over HDMI, but the audio will not.

Thakyou for your prompt reply
🙏🙏🙏🙏🙏🙏
On Wed, Feb 9, 2022 at 9:01 PM Nao Iizuka @.***> wrote:

If you use the -p (or --preview) option, the video will be output over
HDMI, but the audio will not.
—
Reply to this email directly, view it on GitHub
https://github.com/iizukanao/picam-streamer/issues/51#issuecomment-1033886592,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJFDX6T65Q6TT5MJ2ALPHKLU2KCFNANCNFSM5N5NTOOQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>


Responsive Kafé

This PR attempts to make the basis for a responsive Kafé platform. Given the time constraints, it's not perfect, but it's a first step in the right direction.

@Necmttn Also, there is one merge conflict that needs to be resolved ;)


Add layout 12 for ALC262 for HP Compaq dc7700 SFF

ALC262 on HP Compaq dc7700 SFF.
Requires HDEF with a layout-id of 12 to be properly added beforehand.
Should work on the other dc7700 form factors, not tested.

Thanks


[포스터] 제작 (A급 | C급)

행사용 포스터에 관해서 진행하는 Issues
A급 그리고 C급에 대해서 이미지로 올라올 예정

Poster A ver. - Draft
1-1 Man on Cloud

1-2 Hoon on Cloud

2-1 Globe-1

2-2 Globe-2

2-3 Globe-3

3-1 Gear

Poster C ver. - Draft
Humorous poster sample
Let's seek to chic way to save the sick earth.

Hey, these are great! 🌏🌳⚡  Would be good to connect on this with folks in Tag Environmental Susteinability as well! https://github.com/cncf/tag-env-sustainability (cncf slack #tag-environmental-sustainability)

Ah I see you already did in Slcak 💯 🙌


ContentDisposition is always empty

Hi,
I'd like to save an attachment. Unfortunatelly is the return value of ContentDisposition always empty.
So its not possible to read the attached data.
I seems, that the key Content-Disposition is always missing in the header map

Hi @Franky-W. I wouldn't have the time to test this out right now. If you're able to figure this out and come up with a solution, please do share it here so that it can be added to the repo.


Remove "Maintenance Schedule" Buttons from SIV that have been created.

In Sales invoice that have been created: Please remove Maintenance Schedule using server script or client script.

approved close!


Avoid passing -fPIC compiler argument on Windows

Position-independent code is not used on Windows, and passing -fPIC results in a build error, since the argument is unknown

I think it would be better to factor out extraCCFlags instead of replicating the whole destination initialiser.

Fixed, now there's a single Destination initializer and no nested #ifs

@swift-ci please smoke test

@compnerd would you help drive this PR since you have some feedback on the impl

Seems that @neonichu had already approved the change, and there is only more discussion on the handling here.  I'm going to go ahead and merge this, and we can do further improvements in follow up changes.


Horizontal stacked chart

I want to create horizontal stacked chart. Is this possible? My attempt in vain http://codepen.io/anon/pen/LVwwOr?editors=001

Hi @ShobhitMaheshwari
Unfortunately, we are not supporting horizontal stacks at the moment.
Best,
Christoph


events of job1 trigger action of job 2

Hi,
I wrote a config file with two jobs for the same directory :
watcher.ini
[job_write]
watch=/some/dir
events=create,modify,move_to,write_close
recursive=true
autoadd=true
excluded=
command=/some/path/in_create.sh $filename $nflags $tflags

[job_delete]
watch=/some/dir
events=delete,move_from
recursive=true
autoadd=true
excluded=
command=/some/path/in_delete.sh $filename $nflags $tflags
The scripts called write logs and copy file to another server :
in_create.sh
#!/bin/bash
LOGFILE=/var/log/watcher.log
echo "$(date +%Y-%m-%d);$(date +%H:%M:%S);$1;$3;$2;in_create.sh" >> $LOGFILE
(...)
in_delete.sh
#!/bin/bash
LOGFILE=/var/log/watcher.log;
echo "$(date +%Y-%m-%d);$(date +%H:%M:%S);$1;$3;$2;in_delete.sh" >> $LOGFILE
(...)
I expect, when I create a directory or file, that only in_create.sh will be called, but the logs show that both scripts in_create and in_delete are called.
I found a workaround by joining the 2 jobs in one and making a script who checks the nature of events and redirects to the right script, but I guess this behaviour is not normal.
I see in my logs lines like this one :
$mkdir /some/dir/test

2016-03-11;13:16:18;/some/dir/test;IN_CREATE|IN_ISDIR;1073742080;in_create.sh
2016-03-11;13:16:18;/some/dir/test;IN_CREATE|IN_ISDIR;1073742080;in_delete.sh

The second line should not be there, should it ?

hey gedeef,
that's the same way i solved that issue. i redirected the according commands to functions in
one event-handler-script. it's easier to maintain. the script uses arguments (bash: $1 $2 ...)
to sort e.g. $tflags.
cheers.


Faulty solver response handling

Describe the bug
When attempting to reproduce a minimal variation of the backend-process basicUse-example where the answer gets printed to ghci,
the answer does not get printed and a part of the answer appears in next prompt.
Tested with defaultConfig for z3 and custom cvc5 config.
Produces below:

To Reproduce
Modify example to print solvers answer.
main :: IO ()
main = do
  -- 'Process.with' runs a computation using the 'Process' backend
  Process.with
    -- the default configuration uses Z3 as an external process and disables logging
    Process.defaultConfig
    $ \handle -> do
      -- first, we make the process handle into an actual backend
      let backend = Process.toBackend handle
      -- then, we create a solver out of the backend
      -- we enable queuing (it's faster !)
      solver <- initSolver Queuing backend
      -- we send a basic command to the solver and ignore the response
      -- we can write the command as a simple string because we have enabled the
      -- OverloadedStrings pragma
      answer <- command solver "(get-info :name)"
      -- note how there is no need to send an @(exit)@ command, this is already
      -- handled by the 'Process.with' function

      putStr answer

      return ()

Expected behavior
Expected answer to be printed and next prompt to be empty.
Environment

Windows 11
Version 0.3 of smtlib-backends and smtlib-backends-process

Additional context
Tried manually opening and closing Handle via new and close, same result.

putStrLn works.
Thanks for your fast answer!


"Unable to make progress running work" redux2

You closed https://github.com/gradle/gradle/issues/21125 and https://github.com/gradle/gradle/issues/21325, saying the problem is fixed in 7.6, but I just tried 7.6-rc-3 and got this error:
16:13:49  Unable to make progress running work. The following items are queued for execution but none of them can be started:
16:13:49    - Build ':':
16:13:49        - Waiting for nodes:
16:13:49            - :verifyAllSignatures (state=SHOULD_RUN, dependencies=NOT_COMPLETE, group=finalizer :verifyAllSignatures ordinal: task group 0, delegate: default group, no dependencies, finalizes=[:bootJar, :buildRelease] )
16:13:49            - :generatePermissions (state=SHOULD_RUN, dependencies=NOT_COMPLETE, group=finalizer :generatePermissions ordinal: task group 0, delegate: default group, dependencies=[:classes, :compileJava, :generateVersion], waiting-for=[:generateVersion, :compileJava, :classes], has-failed-dependency=false, finalizes=[:compileJava] )
16:13:49            - :buildRelease (state=SHOULD_RUN, dependencies=NOT_COMPLETE, group=task group 0, dependencies=[:clean (complete), :generateVersion], waiting-for=[:generateVersion], has-failed-dependency=false )
16:13:49            - :assemble (state=SHOULD_RUN, dependencies=NOT_COMPLETE, group=finalizer :assemble ordinal: task group 0, delegate: default group, dependencies=[:bootJar, :jar], waiting-for=[:bootJar, :jar], has-failed-dependency=false, finalizes=[:buildRelease] )
16:13:49        - Reachable nodes:
16:13:49            - :compileJava (state=SHOULD_RUN, dependencies=NOT_COMPLETE, group=composite group, entry point: false, ordinal: default group, groups: [finalizer :assemble ordinal: task group 0, delegate: default group, finalizer :generatePermissions ordinal: task group 0, delegate: default group], no dependencies )
16:13:49            - :processResources (state=SHOULD_RUN, dependencies=NOT_COMPLETE, group=composite group, entry point: false, ordinal: default group, groups: [finalizer :assemble ordinal: task group 0, delegate: default group, finalizer :generatePermissions ordinal: task group 0, delegate: default group], no dependencies )
16:13:49            - :classes (state=SHOULD_RUN, dependencies=NOT_COMPLETE, group=composite group, entry point: false, ordinal: default group, groups: [finalizer :assemble ordinal: task group 0, delegate: default group, finalizer :generatePermissions ordinal: task group 0, delegate: default group], dependencies=[:compileJava, :processResources], waiting-for=[:processResources, :compileJava], has-failed-dependency=false )
16:13:49            - :generateVersion (state=SHOULD_RUN, dependencies=NOT_COMPLETE, group=finalizer :generateVersion ordinal: task group 0, delegate: composite group, entry point: true, ordinal: task group 0, groups: [finalizer :assemble ordinal: task group 0, delegate: default group, finalizer :generatePermissions ordinal: task group 0, delegate: default group], no dependencies, finalizes=[:processResources] )
16:13:49            - :bootJar (state=SHOULD_RUN, dependencies=NOT_COMPLETE, group=finalizer :assemble ordinal: task group 0, delegate: default group, dependencies=[:classes, :compileJava, :generateVersion], waiting-for=[:generateVersion, :compileJava, :classes], has-failed-dependency=false )
16:13:49            - :jar (state=SHOULD_RUN, dependencies=NOT_COMPLETE, group=finalizer :assemble ordinal: task group 0, delegate: default group, dependencies=[:classes, :compileJava, :generateVersion], waiting-for=[:generateVersion, :compileJava, :classes], has-failed-dependency=false )
16:13:49        - Ordinal groups: group 0 entry nodes: [:buildRelease]
16:13:49    - Workers waiting for work: 16
16:13:49    - Stopped workers: 0
16:13:49
16:13:49  FAILURE: Build failed with an exception.
16:13:49
16:13:49  * What went wrong:
16:13:49  Unable to make progress running work. There are items queued for execution but none of them can be started

It works fine locally. Does that in Jenkins.

Thank you for your interest in Gradle!
This issue will be closed as a duplicate of #22734. Please add your 👍 to that issue.

However, if you can still reproduce after trying with the changes done for the issue above, we will need a reproducer to track down the issue.


Add compatibility with vue2js

@Justineo

Just release v2.0.0 and this issue is already resolved there so I'm closing this. Thanks!


Update Python agent-config

Removing usage of otlp_proto_grpc/http (as for deprecation)
General fixes

@open-telemetry/python-approvers , @open-telemetry/python-maintainers: PTAL

/easycla

@ronyis since you submitted this change, we've applied prettier-style formatting to the repo and added a check that's now failing. Would you mind running npm run pretter:write on this file? Might be easier to first rebase.

Sure, done @cartermp


fix: Added date time parsing for conditional formatting

Added datetime string parsing / validation.
fixes #1108

@vbabich  It was suggested by @niloc132 that instead of using convertDateTime, we could use autoEpochToNanos in the Java expression that gets run by the engine. This would require us to parse the datetime in the UI first and then use the nanos value in the expression. This "should" address the issue we still have with the engine only supporting a subset of timezones.
I'm hesitant to do that for this issue given the current solution is already implemented, but I can create a new issue if we think this is a better solution.

@bmingles Agreed, open another issue for this.


Implement a MixedOperator

What should we add?
We would like to add support for more complex models which couple various types of particles (e.g. fermions with bosons).
Among other things, this finds application in lattice gauge theory which is a planned addition to the lattice framework (see e.g. #556 which is the simplest LGT case).
A rough list of requirements which are needed for this to work are:

a MixedOperator class which can hold multiple kinds of operators (i.e. FermionicOp, SpinOp, etc.)

the above class should allow storage of interaction coefficients between different operator kinds (in addition to the operator-internal coefficients ofcourse)

an extension/addition of the QubitConverter to handle a MixedOperator

this requires multiple QubitMapper instances for all operator types contained in the mixed op
this should handle delegation of the various qubit registers: e.g. the fermionic operators get mapped to qubits q1 .. qN and the spin operators get mapped to qubits q(N+1) ... q(N+M)
purely fermionic operators need to be tensored with all-identity operators on the qubit-registers assigned to the spin-subsystem
purely spin operators are tensored with all-identity terms on the fermionic-subsystem (etc.)
mixed operators are mapped individually and then tensored together in the qubit-space taking into account the potential mixing coefficients stored in the MixedOperator

:warning: Disclaimer: this is mostly an assortment of some thoughts. A first step for tackling this issue would be to come with a design on how to achieve this, given the rough outline of requirements presented above. I am happy to answer questions with more details :+1:

I would like to participate implementing this MixedOp


One small grammar fix.  Deleted an empty cell.  Made script default t…

One small grammar fix.  Deleted an empty cell.  Made script default to cpu context.  Executed all paragraphs so users can see output.

Closed in favor of #453 which incorporates these changes and leaves all cells unexecuted.


Missing TranslationBehavior.

Hello. I have next error:

Class 'bl\multilang\behaviors\TranslationBehavior' not found

I think it because in composer json missing dependency for black-lamp/yii2-multi-lang

@Sensetivity Hey! This extension actually not supported. Please use https://github.com/yiimaker/yii2-email-templates instead.


style(RecsList & Single Cluster page): changed the Added column

changed the Added column to modified
updated the translations
screenshots are in the Jira

:tada: This PR is included in version 1.0.12 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


PyIceberg is not respecting token in the load table response

Apache Iceberg version
0.7.1 (latest release)
Please describe the bug 🐞
In the Iceberg REST API spec, the load table endpoint can include a config map with additional properties to configure for when accessing the given table. One of these a potential token property in the LoadTableResult in a section which states

The following configurations should be respected by clients

It doesn't appear that PyIceberg is respecting this property and continues to use the original token supplied in the catalog configuration request. This can lead to incorrect permissions being applied for table operations which in some cases could prevent operations from succeeding when they should.

Thanks for reporting this @creechy
Do you have an example to reproduce this issue?
For now, I found some more docs on token
https://github.com/apache/iceberg/blob/cd32ec76ecd2866c05185065e4ed7196121de49a/open-api/rest-catalog-open-api.yaml#L672-L675
And relevant code in the REST client implementation
https://github.com/apache/iceberg-python/blob/e4c1748fee220076f04e35ab2f182dd51ca20705/pyiceberg/catalog/rest.py#L506-L515

@kevinjqliu

Do you have an example to reproduce this issue?

I provided an example with a Tabular config to @Fokko, who confirmed that PyIceberg does not appear to be switching tokens. FWIW here's the script, probably not all that useful, but if you know how to look at the response of load_table, you should see a config object with a token in it, which PyIceberg is not using. In my case, the original token does not have the necessary privileges to update the table, and so this ends up with a 409 Conflict instead of succeeding.
catalog = load_catalog(
    "raw",
    **{
        "type": "rest",
        "uri": "https://api.tabular.io/ws/",
        "warehouse": "<warehouse>",
        "credential": "<credential>"
    },
)

table = catalog.load_table("default.buddy")

schema = table.schema().as_arrow()

df = pa.Table.from_pylist(
    [{"s": "Groningen"}], schema=schema
)

table.append(df)


Adding bindings for D2D1, DWrite, DXGI, and some of Windowscodecs

This pull request adds interface bindings for D2D1, DWrite, DXGI, and some of Windowscodecs (enough that interfaces the other libraries use are defined).

Is there anything else I should do for this?


Action.execute().subscribe() receiving ActionError.notEnabled even when enabled

I could be misunderstanding this, but my thinking is that subscription closures passed into Action.execute().subscribe() should receive values, errors, etc from that particular invocation of execute(). I noticed I was never getting called back in the onCompleted closure, and found that I always receive a ActionError.notEnabled. This happens even when I create my Action with an explicit enabledIf: Observable.just(true).

Can you give a go to the HEAD of the repo? we think we fixed this issue, a second confirmation would be great.

BTW errors are being passed to the observable returned for each execution. Do you have a case where this doesn't work?

I confirmed we've already fixed this issue in our HEAD.
This patch will get released today 🙇
Test code
import UIKit
import RxSwift
import Action

class ViewController: UIViewController {
    var action: CocoaAction!

    override func viewDidLoad() {
        super.viewDidLoad()

        action = CocoaAction {
            return Observable
                .just()
                .delay(1.0, scheduler: MainScheduler.instance)
        }

        action.execute().debug().subscribe()
    }
}

2.1.0 output
2017-01-09 15:43:13.820: TestViewController.swift:17 (viewDidLoad()) -> subscribed
2017-01-09 15:43:13.821: TestViewController.swift:17 (viewDidLoad()) -> Event error(notEnabled)
Received unhandled error: /Users/ishkawa/dev/src/github.com/RxSwiftCommunity/Action/Demo/TestViewController.swift:17:viewDidLoad() -> notEnabled
2017-01-09 15:43:13.821: TestViewController.swift:17 (viewDidLoad()) -> isDisposed

HEAD output
2017-01-09 15:44:36.798: TestViewController.swift:17 (viewDidLoad()) -> subscribed
2017-01-09 15:44:37.811: TestViewController.swift:17 (viewDidLoad()) -> Event next(())
2017-01-09 15:44:37.812: TestViewController.swift:17 (viewDidLoad()) -> Event completed
2017-01-09 15:44:37.812: TestViewController.swift:17 (viewDidLoad()) -> isDisposed

Ohhh you have a reproducible test? Fantastic, we'll be able to add it to the tests then! 👍

I just switched to HEAD and it works! Thank you all.

Great! Thanks a lot for testing this! Going to close the issue, this should be released as 2.2.0 shortly.


Avoid unnecessary instantiations in DispatchToVectorized

This avoids unnecessary template instantiations when vectorizing with 16-bit and larger data types, significantly reducing compile times for some kernels.
It should also help with the Windows compilation issue discussed here:
https://github.com/tensorflow/tensorflow/issues/54276#issuecomment-1032186006
No functional change.

cc @nluehr

@reedwm Can you please review this PR ? Thank you!

@benbarsdell  Can you please address Ubuntu Sanity errors? Thank you!

Rebased, which seems to have fixed the CI (I think it was broken due to https://github.com/tensorflow/tensorflow/issues/55494, but I guess the CI doesn't automatically pick up that fix?).


Build a standalone statically linked binary for easier distribution

The current method is a convoluted mess.

Some of the complexity arises because Skyscope is built with Nix (and so has an interpreter path in /nix/store) but needs to run on both Nix and non-Nix systems.
Also the distribution package bundles the entire shared library closure (including libc) to allow Skyscope to run on as many systems as possible.

If we could build a statically linked binary (using musl instead of glibc), it would make distribution much simpler.

Addressed by #94.


Support dynamic message name on Conduit.Test functions

Hi, my team is using this nice library and sometimes we want to test dynamic message names.
I don't know if there's a better way to support this (the code feels repetitive and couldn't keep the deprecated behaviour), so any suggestions are welcome :)

I'm not sure I understand the use case. Name there should always be an atom because it refers to publish :name, ....

Oh, I see. We can go to a v1.0.0 for this.


Users visibility permissions

Any user can see all the users in the "users" section. Can we somehow limit this already now? Users might use full names and might not be desirable to be seen by other users, especially if there are multiple collections, for each institution separately, but users from both collections can still see all the registered users on the platform. This should be limited to admin only, or to see users that are part of the collections that you are also in...

I would also like to disable all users being able to see the users section. I agree that this should be limited to admin only.

Internally, users are access controlled models, so this would be a matter of setting all users to public=False.  I don't think there is a web api to do this for users, so this would be running for user in User().find():  User().setPublic(user, False, save=True) in python and hooking to the user creation event to ensure new users are so flagged.
It wouldn't be a hard feature to add to a plugin.


Disable updated/created logs in console

Thanks for this awesome library! :)
When a signal gets created or updated, a message is printed in the console. How can this behavior be disabled?

Thanks!!
And this is the fix:
https://github.com/rodydavis/signals.dart/issues/230#issuecomment-2058114698


Indention broken when used with Treesitter

Hey :wave:,
I just started using https://github.com/nvim-treesitter/nvim-treesitter, a increasingly popular treesitter based highlighting plugin, and noted that the indention was broken on javascript files. I tracked this down to vim-polyglot and further down to vim-graphql.
If you run nvim-treesitter as your highlighter, with the following config:
" Treesitter.
lua <<EOF
require'nvim-treesitter.configs'.setup {
  highlight = { enable = true },
  indent = { enable = true },
}
EOF

and also have vim-graphql installed - the indention will be broken for javascript files.
Please let me know if I can provide any further information! :pray:

Vim Version

NVIM v0.5.0-808-gee3acef38
Build type: RelWithDebInfo
LuaJIT 2.0.5
Compilation: /usr/bin/cc -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/tmp/builds/neovim-git/src/build/config -I/tmp/builds/neovim-git/src/neovim-git/src -I/usr/include -I/tmp/builds/neovim-git/src/build/src/nvim/auto -I/tmp/builds/neovim-git/src/build/include
Compiled by sqve@jiji

Features: +acl +iconv +tui

That isn't a configuration I currently use, so it may take me a while to investigate the root cause of the issue.
If you're able to dig in and narrow down how that runtime environment differs from vim/non-treesitter, it will help me address this sooner.

If you're able to dig in and narrow down how that runtime environment differs from vim/non-treesitter, it will help me address this sooner.

Could you elaborate a bit here? I'm a bit unsure on what you would find helpful.

Well, same. 😉 I don't use neovim or tree-sitter, so I'm not sure how they handle indentation, etc. differently from a standard vim runtime.
It'll take me some time to learn about that. If you could get a sense why this plugin is breaking in that environment, it would speed up the fix.
In the meantime, I believe there's a way to disable just the vim-graphql plugin inside of vim-polyglot. It would be helpful to know that doing so solves the problem you're seeing.

Alright, so, as far as I know vim and neovim does not differ much in how they handle indention. But I'm far from an expert so just my $0.002 USD.
The plugin nvim-treesitter is essentially a highlighter that uses treesitter instead of regex to highlight code. I have enabled it to also handle indent but it made no difference in turning it off.

@sQVe I think #70 may fix the issue you're seeing. I don't think the problem was directly related to treesitter.

@jparise Yes, you are correct. I don't see any issues any longer! :+1: :tada:

What's the work-flow to get this pushed to vim-polyglot?

What's the work-flow to get this pushed to vim-polyglot?

I don't use vim-polyglot myself, but from the project's readme:

You can either wait for new patch release with updates or run make by yourself.

@sheerun FYI this is an important fix to pick up.

I'll update soon, I'm on mobile internet...
On Thu, Nov 12, 2020 at 6:18 PM Jon Parise<EMAIL_ADDRESS>wrote:

What's the work-flow to get this pushed to vim-polyglot?
I don't use vim-polyglot myself, but from the project's readme
https://github.com/sheerun/vim-polyglot#updating:
You can either wait for new patch release with updates or run make by
yourself.
@sheerun https://github.com/sheerun FYI this is an important fix to
pick up.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jparise/vim-graphql/issues/67#issuecomment-726216992,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACHMDJ7HT4BLQ2Y7CRKW3LSPQKFDANCNFSM4TQX3AYQ
.


1.4.1 build issue — Undefined symbols for architecture arm64

Description
Starting from version 1.4.0 and still happening in 1.4.1 i am getting the follow error at the end of building. It does not happen on 1.3.13.
❌  Undefined symbols for architecture arm64
┌─ Symbol: SkUnicodes::Libgrapheme::Make()
└─ Referenced from: skia::textlayout::ParagraphBuilder::make(skia::textlayout::ParagraphStyle const&, sk_sp<skia::textlayout::FontCollection>) in libskparagraph.a[arm64][6](libskparagraph.ParagraphBuilderImpl.o)

❌  ld: symbol(s) not found for architecture arm64

❌  clang: error: linker command failed with exit code 1 (use -v to see invocation)

› 3 error(s), and 2 warning(s)

CommandError: Failed to build iOS project. "xcodebuild" exited with error code 65.

I am running:

MacBook Pro M1 Pro 14.5 (23F79).
Expo SDK 51
React Native 0.75.3

Version
1.4.0 - 1.4.1
Steps to reproduce
start an iOS build with expo expo run:ios or npm run run:ios
Snack, code example, screenshot, or link to a repository
https://github.com/AndreasJJ/skia-repro-1.4.1

+1


Github actions broken due to expired 16.04 environment.

https://github.blog/changelog/2021-04-29-github-actions-ubuntu-16-04-lts-virtual-environment-will-be-removed-on-september-20-2021/
We should migrate to 18.04. This will raise the minimum supported platform for linux natives, but lwjgl3 has already done this change.

September 20 sounds pretty soon! I saw TEt link to https://github.com/LWJGL/lwjgl3/commit/307ebed6ef6ba420b2165ddb2ec21dd9a37479df on Discord a while back. Don't know what to make of it but it might be useful to reference.

No no, it is, JAmes. LWJGL3 probably took steps we can also take, maybe identical ones in some places. Also, September 20 is over for the planet as a whole in less than 8 hours.


Cr 1089 create modify endpoint in preparation for cuc tests

Motivation and Context

This change to the mock case service is required in order to mimic RM in the following scenario:
Given the case does not exist in the cache
And the case exists in RM
When the case address details are modified
And the case modified event is sent to RM and RM  action it
When the call is made to fetch the case again from GetCaseByUPRN
Then GetCaseByUPRN gets the modified case from RM
NB. The above scenario has yet to be written - this is a pre-requisite for it.
What has changed

A new POST endpoint has been added to the mock case service, which allows an existing case to be modified. It is works locally with the following URL:
http://localhost:8161/cases/data/cases/modify
It is very similar to the add endpoint; it also requires a request body, which is of type List, such as this:
[{
"caseRef": "123123002",
"arid": "2344266233",
"estabArid": "AABBCC",
"estabType": "ET",
"uprn": "1347459999",
"createdDateTime": "2019-04-14T13:45:26.564+01:00",
"addressLine1": "Happy House Three",
"addressLine2": "89 Harbour Street",
"addressLine3": "Somewhere",
"townName": "Portsmouth",
"postcode": "G1 2AA",
"organisationName": "ON",
"addressLevel": "E",
"abpCode": "AACC",
"latitude": "41.40338",
"longitude": "2.17403",
"oa": "EE22",
"lsoa": "x1",
"msoa": "x2",
"lad": "H1",
"caseEvents": [
{
"id": "101",
"eventType": "CASE_UPDATED",
"description": "Initial creation of case",
"createdDateTime": "2019-04-14T13:45:26.564+01:00"
},
{
"id": "102",
"eventType": null,
"description": "Create Household Visit",
"createdDateTime": "2019-04-14T13:45:26.564+01:00"
}
],
"id": "3305e937-6fb1-4ce1-9d4c-077f147789ac",
"caseType": "HH",
"addressType": "SPG",
"region": "E",
"collectionExerciseId": "49871667-117d-4a63-9101-f6a0660f73f6",
"surveyType": "CENSUS",
"handDelivery": false
}]

How to test?

Test the changes by firstly running one of the GET case endpoints in Postman e.g.
http://localhost:8161/cases/3305e937-6fb1-4ce1-9d4c-077f147789ac
Then run the modify endpoint in Postman, as described above, and then re-run the GET endpoint to check that the case has been modified.

This PR has now been replaced with the following new PR (after discussing the problem with Phil):
https://github.com/ONSdigital/census-mock-case-api-service/pull/28


Fix UG bug

What's change

Update all the screenshot to the latest UI #210
Include a note for remove and removepj command that empty keyword will not throw error even if the field is empty #220

Duplicate of #255


Make initial version of RTP pipeline

Update the folio batch script pipeline

Coverage remained the same at 96.832% when pulling ab642e1d4fa4d0e2ffd128b675b70e8c87011904 on bad_ants into ddd48be806b89391da8aa6692b1784dd36da9df5 on master.


Have ' ' chars get inserted correctly after a resize

Since the character spec didn't contain a character width it was being skipped
during refresh.
Fixes #159

@Tyriar can you provide us with some testing instructions on this? How can we verify that this PR works?

@parisk This was introduced by my wcwidth patch. I tried to fix all new cell creations with the character width as third array element. This one slipped through ;)
You can test it with a resize or resize+refresh test case - the sum of the third cell element of a line should always be equal to term.cols after resizing. Same for the length of a not styled line string containing only halfwidth characters in refresh.

👍  Thanks a lot!


Reland "Add the refresh rate fields to perf_test #99710"

Relands https://github.com/flutter/flutter/pull/99710 with conditionally add the new keys.
The original PR caused a failure, see: https://github.com/flutter/flutter/pull/99801
See https://github.com/flutter/flutter/pull/99710#issuecomment-1063201618 for discussion on the failure.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

cc @zanderso @bdero

@dnfield This has landed. Do you know where I can see the values from benchmark?

https://flutter-flutter-perf.skia.org/e/?queries=sub_result%3D90hz_frame_percentage%26sub_result%3D80hz_frame_percentage%26sub_result%3D60hz_frame_percentage%26sub_result%3D30hz_frame_percentage%26sub_result%3D120hz_frame_percentage


ci: add ci to test intree migration to ceph-csi

This commit adds CI to test intree migration to Ceph-csi
Signed-off-by: subhamkrai<EMAIL_ADDRESS>

this PR in in top of #39


Disabled timepicker not display value on safari

Hi, on chrome when disable it display gray color like this

But on safari, this color is white => can't see (maybe safari bug)
I need change style to this
.vue__time-picker input.display-time:disabled, .vue__time-picker input.display-time.disabled {
    color: gray !important;
}

Hi @godshades,
Thanks for the report. However, I cannot reproduce it with the Safari on my end -- Version 13.1 (156<IP_ADDRESS>.8).

Can you try opening this JSFiddle with your Safari and capture a screenshot? Along with your current Safari and macOS version will be even better.


filter(ticdc): Fix verify table rules

What problem does this PR solve?

Issue Number: ref #10457
What is changed and how it works?
Check List
Tests

No code

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

/retest

/retest

/retest

/retest


Add settings button to sidebar

Settings button on sidebar
Fixes #3027

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)

Hi! There seems to be some lint check error - you may want to run prettier (perhaps as a plugin that auto-formats on save).

New screenshot


Inquiy about the reconstruction signals

Hi authors, thanks for your excellent work.
After reading the paper, I find that loss calculation just needs RGB color, depth, and occupancy, which using Eq.2, Eq. 10, and Eq. 11. But in Eq. 8 and Eq. 9, the scale and rotation are also predicted. May I ask whether they are used? I am not sure whether some important things are ignored by me.
Additionally, may I ask if there are any plan to release the code.
Best

No problem at all for the delay in replying.
Actually, the variables rotation and scale are intermediate variables used in the reconstruction of the RGB and Depth values, which are then used for the final loss calculation, as shown in the code below. The full code will be released in the next few days, so please bear with us for a little while longer.

Got that. Looking forward to your full code.


Builder Library components don't show up as expected

Describe the bug
Some Library components aren't showing up, even on the page they were created from
To Reproduce
This error seems a little intermittent, so I can't guarantee that it will show up in every case
Steps to reproduce the behavior:

Open an Edit View
Click on an appropriate layer
Click the Library accordion and "Add"
Give the component a name and icon
The component will be added to the library, but in some cases, when the page is refreshed, the component is not visible, and when other views are Configured, the component is similarly not visible

Expected behavior
Library components should be visible on the type of Configurator that they were created with, at a minimum
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
This isn't a problem for every attempt to save components to a library and my testing has not yet revealed a common cause for ones which fail to appear on their appropriate pages.

Fixed in #2753. The code for determining whether a library component was suitable for a view was out of date as new widget types had been added to some view patterns


When actions='only' is empty it fails

If actions only df comes empty, script thinks it's erroneous and retries outputting the OHLC info

Fixed in 0.0.15

You rock :+1:


Any example of how to make a select field?

I can't see on the docs how do I make a select field. I want a select field that shows "bronze", "silver, "gold", but actual values are 1, 2, 3.

select widgets take a "choices" object, whose keys are the <option> values, and whose values are the <option> HTML content.

like this?
options.widget = widgets.select({choices: {'1':'bronze'. '2':'silver', '3':'gold'}});
fields.string(options);

I tested here and actually is not the widget that take the choices object, but the field. You passo the choices object with the field options.

Ah right thanks :-) clearly the documentation needs improvement, for which a PR is welcome!

I would like, but I've been very busy ATM, coding both web and Android.on a project for the company. My head gets confused sometimes, creating new objects in Java using {}.