Broken ingress host path DNS validation in 2.0 UI

Rancher versions:
rancher/server: 2.0.0.preview-23
Infrastructure Stack versions:
kubernetes: 1.8.9
Docker version: (docker version,docker info preferred)
17.3.2
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
Ubuntu 16.04.1 LTS
Type/provider of hosts:
AWS EC2
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single control plane host, single compute plane host
Steps to Reproduce:
Add a host to an Ingress with a - in the DNS name from the GUI
Results:
Validation failed in API: Ingress.extensions "kubernetes-dashboard-kdsyu" is invalid: spec.backend.serviceName: Invalid value: "kube-system/kubernetes-dashboard-kdsyu": a DNS-1035 label must consist of lower case alphanumeric characters or '-', start with an alphabetic character, and end with an alphanumeric character (e.g. 'my-name', or 'abc-123', regex used for validation is '[a-z]([-a-z0-9]*[a-z0-9])?')
Looks like the regex pattern needs an escape character to interpret the - inside the square brackets as a literal - instead of it's special meaning as a range

The hyphen doesn't need to be escaped when it's at the beginning or end of range.  That error is straight from k8s, and because the value is kube-system/kubernetes-dashboard-kdsyu and slash is not allowed.  That field is for the default service to send requests that match no other rule too.
But I'm not sure how you got that value in the first place, that looks like something setting an old-style reference to [stack name]/[service name].

This issue should be fixed as UI now filters out workload/services from the different namespace (k8s doesn't support cross namespace linking for ingress services). With services/workload only from the same namespace, the issue should be gone.
@sangeethah @soumyalj can we re-test on the very latest.

Tested with latest build from master.
This issue is still reproducible.
Any update done to an ingress that has "Target Backend" set to "Service" fails with this error
Validation failed in API: Ingress.extensions "test1" is invalid: spec.rules[0].http.backend.serviceName: Invalid value: "default/newwork": a DNS-1035 label must consist of lower case alphanumeric characters or '-', start with an alphabetic character, and end with an alphanumeric character (e.g. 'my-name', or 'abc-123', regex used for validation is '[a-z]([-a-z0-9]*[a-z0-9])?')

Same as issue tracked in https://github.com/rancher/rancher/issues/12644

Ok, here are the most simple steps to repro:

create ingress with service
Click edit. Do not change any params, just hit save.

I've tried by modifying the path for service based ingress; there issue doesn't happen. NO issue is present for workload based ingress either.

Tested with latest build from mater.
Able to update ingress that has "Target Backend" set to "Service" successfully.


[Camera][iOs] high memory usage (400+ mb at launch)

Found an issue dealing with Flutter core functionality: when the camera opens on iOS, then we face high memory usage. Please check the attached screenshot of the Xcode Instruments and a link to the application, as well as logs. Does anyone face the same issue?

example app
iPhone 7, iOs 14.0

Logs
flutter run --verbose
[  +84 ms] executing: sysctl hw.optional.arm64
[  +14 ms] Exit code 1 from: sysctl hw.optional.arm64
[        ] sysctl: unknown oid 'hw.optional.arm64'
[   +5 ms] executing: [/Users/nikitakhilobok/Documents/flutter/] git -c
log.showSignature=false log -n 1 --pretty=format:%H
[  +27 ms] Exit code 0 from: git -c log.showSignature=false log -n 1
--pretty=format:%H
[        ] b22742018b3edf16c6cadd7b76d9db5e7f9064b5
[        ] executing: [/Users/nikitakhilobok/Documents/flutter/] git tag
--points-at b22742018b3edf16c6cadd7b76d9db5e7f9064b5
[  +65 ms] Exit code 0 from: git tag --points-at
b22742018b3edf16c6cadd7b76d9db5e7f9064b5
[        ] 2.2.0
[   +5 ms] executing: [/Users/nikitakhilobok/Documents/flutter/] git rev-parse
--abbrev-ref --symbolic @{u}
[  +12 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [/Users/nikitakhilobok/Documents/flutter/] git ls-remote
--get-url origin
[  +11 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +90 ms] executing: [/Users/nikitakhilobok/Documents/flutter/] git rev-parse
--abbrev-ref HEAD
[  +14 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[   +6 ms] executing: sw_vers -productName
[  +12 ms] Exit code 0 from: sw_vers -productName
[        ] macOS
[        ] executing: sw_vers -productVersion
[  +13 ms] Exit code 0 from: sw_vers -productVersion
[        ] 11.2.3
[        ] executing: sw_vers -buildVersion
[  +13 ms] Exit code 0 from: sw_vers -buildVersion
[        ] 20D91
[  +63 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping
update.
[   +3 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required,
skipping update.
[  +42 ms] executing:
/Users/nikitakhilobok/Library/Android/sdk/platform-tools/adb devices -l
[  +10 ms] executing: sysctl hw.optional.arm64
[   +3 ms] Exit code 1 from: sysctl hw.optional.arm64
[        ] sysctl: unknown oid 'hw.optional.arm64'
[        ] executing: xcrun xcodebuild -version
[ +763 ms] Exit code 0 from: xcrun xcodebuild -version
[   +1 ms] Xcode 12.5.1
           Build version 12E507
[   +2 ms] executing: xcrun xcdevice list --timeout 2
[   +3 ms] xcrun simctl list --json devices
[        ] executing: xcrun simctl list --json devices
[  +43 ms] List of devices attached
           <IP_ADDRESS>:41686     device product:walleye model:Pixel_2
           device:walleye transport_id:1
[ +106 ms] {
                      "devices" : {
                        "com.apple.CoreSimulator.SimRuntime.iOS-12-0" : [
                          {
                            "dataPath" :
                            "\/Users\/nikitakhilobok\/Library\/Developer\/CoreSi
                            mulator\/Devices\/0E34A0D0-2F60-4CC3-BACA-ACC9A3008C
                            5F\/data",
                            "logPath" :
                            "\/Users\/nikitakhilobok\/Library\/Logs\/CoreSimulat
                            or\/0E34A0D0-2F60-4CC3-BACA-ACC9A3008C5F",
                            "udid" : "0E34A0D0-2F60-4CC3-BACA-ACC9A3008C5F",
                            "isAvailable" : true,
                            "deviceTypeIdentifier" :
                            "com.apple.CoreSimulator.SimDeviceType.iPhone-5s",
                            "state" : "Shutdown",
                            "name" : "iPhone 5s"
                          },
                          {
                            "dataPath" :
                            "\/Users\/nikitakhilobok\/Library\/Developer\/CoreSi
                            mulator\/Devices\/5CD425EA-F9DA-4B31-9E17-DFA7273635
                            DE\/data",
                            "logPath" :
                            "\/Users\/nikitakhilobok\/Library\/Logs\/CoreSimulat
                            or\/5CD425EA-F9DA-4B31-9E17-DFA7273635DE",
                            "udid" : "5CD425EA-F9DA-4B31-9E17-DFA7273635DE",
                            "isAvailable" : true,
                            "deviceTypeIdentifier" :
                            "com.apple.CoreSimulator.SimDeviceType.iPhone-6-Plus
                            ",
                            "state" : "Shutdown",
                            "name" : "iPhone 6 Plus"
                          },
                          {
                            "dataPath" :
                            "\/Users\/nikitakhilobok\/Library\/Developer\/CoreSi
                            mulator\/Devices\/3F558823-11B6-4DA0-AA60-F07C0A109A
                            3D\/data",
                            "logPath" :
                            "\/Users\/nikitakhilobok\/Library\/Logs\/CoreSimulat
                            or\/3F558823-11B6-4DA0-AA60-F07C0A109A3D",
                            "udid" : "3F558823-11B6-4DA0-AA60-F07C0A109A3D",
                            "isAvailable" : true,
                            "deviceTypeIdentifier" :
                            "com.apple.CoreSimulator.SimDeviceType.iPhone-6",
                            "state" : "Shutdown",
                            "name" : "iPhone 6"
                          },
                          {
                            "dataPath" :
                            "\/Users\/nikitakhilobok\/Library\/Developer\/CoreSi
                            mulator\/Devices\/E46BE8E6-0A80-4878-9D86-F6AC6E3BD2
                            C8\/data",
                            "logPath" :
                            "\/Users\/nikitakhilobok\/Library\/Logs\/CoreSimulat
                            or\/E46BE8E6-0A80-4878-9D86-F6AC6E3BD2C8",
                            "udid" : "E46BE8E6-0A80-4878-9D86-F6AC6E3BD2C8",
                            "isAvailable" : true,
                            "deviceTypeIdentifier" :
                            "com.apple.CoreSimulator.SimDeviceType.iPhone-6s",
                            "state" : "Shutdown",
                            "name" : "iPhone 6s"
                          },
                          {
                            "dataPath" :
                            "\/Users\/nikitakhilobok\/Library\/Developer\/CoreSi
                            mulator\/Devices\/2D35228E-996D-4520-A8C5-BFBF7F9E13
                            BE\/data",
                            "logPath" :
                            "\/Users\/nikitakhilobok\/Library\/Logs\/CoreSimulat
                            or\/2D35228E-996D-4520-A8C5-BFBF7F9E13BE",
                            "udid" : "2D35228E-996D-4520-A8C5-BFBF7F9E13BE",
                            "isAvailable" : true,
                            "deviceTypeIdentifier" :
                            "com.apple.CoreSimulator.SimDeviceType.iPhone-6s-Plu
                            s",
                            "state" : "Shutdown",
                            "name" : "iPhone 6s Plus"
                          },
                          {
                            "dataPath" :
                            "\/Users\/nikitakhilobok\/Library\/Developer\/CoreSi
                            mulator\/Devices\/9B381EE8-7C69-452C-AA72-EDC890E222
                            C3\/data",
                            "logPath" :
                            "\/Users\/nikitakhilobok\/Library\/Logs\/CoreSimulat
                            or\/9B381EE8-7C69-452C-AA72-EDC890E222C3",
                            "udid" : "9B381EE8-7C69-452C-AA72-EDC890E222C3",
                            "isAvailable" : true,
                            "deviceTypeIdentifier" :
                            "com.apple.CoreSimulator.SimDeviceType.iPhone-SE",
                            "state" : "Shutdown",
                            "name" : "iPhone SE (1st generation)"
                          },
                          {
                            "dataPath" :
                            "\/Users\/nikitakhilobok\/Library\/Developer\/CoreSi
                            mulator\/Devices\/D8E4306B-6976-4FF4-BC69-EDE447E04D
                            6C\/data",
                            "logPath" :
                            "\/Users\/nikitakhilobok\/Library\/Logs\/CoreSimulat
                            or\/D8E4306B-6976-4FF4-BC69-EDE447E04D6C",
                            "udid" : "D8E4306B-6976-4FF4-BC69-EDE447E04D6C",
                            "isAvailable" : true,
                            "deviceTypeIdentifier" :
                            "com.apple.CoreSimulator.SimDeviceType.iPhone-7",
                            "state" : "Shutdown",
                            "name" : "iPhone 7"
                          },
                          {
                            "dataPath" :
                            "\/Users\/nikitakhilobok\/Library\/Developer\/CoreSi
                            mulator\/Devices\/34E47678-CE63-4DE6-A09E-40312C9E4A
                            CE\/data",
                            "logPath" :
                            "\/Users\/nikitakhilobok\/Library\/Logs\/CoreSimulat
                            or\/34E47678-CE63-4DE6-A09E-40312C9E4ACE",
                            "udid" : "34E47678-CE63-4DE6-A09E-40312C9E4ACE",
                            "isAvailable" : true,
                            "deviceTypeIdentifier" :
                            "com.apple.CoreSimulator.SimDeviceType.iPhone-7-Plus
                            ",
                            "state" : "Shutdown",
                            "name" : "iPhone 7 Plus"
                          },
                          {
                            "dataPath" :
                            "\/Users\/nikitakhilobok\/Library\/Developer\/CoreSi
                            mulator\/Devices\/909E3FC4-F681-4C83-A96A-40EBC29B93
                            B5\/data",
                            "logPath" :
                            "\/Users\/nikitakhilobok\/Library\/Logs\/CoreSimulat
                            or\/909E3FC4-F681-4C83-A96A-40EBC29B93B5",
                            "udid" : "909E3FC4-F681-4C83-A96A-40EBC29B93B5",
                            "isAvailable" : true,
                            "deviceTypeIdentifier" :
                            "com.apple.CoreSimulator.SimDeviceType.iPhone-8",
                            "state" : "Shutdown",
                            "name" : "iPhone 8"
                          },
                          {
                            "dataPath" :
                            "\/Users\/nikitakhilobok\/Library\/Developer\/CoreSi
                            mulator\/Devices\/03C16D03-176F-42B7-885C-3967774EB8
                            41\/data",
                            "logPath" :
   ...

% flutter analyze
Analyzing ios_camera_memory_issue...
No issues found! (ran in 1.7s)

flutter doctor -v

[✓] Flutter (Channel stable, 2.2.0, on macOS 11.2.3 20D91 darwin-x64, locale en-GB)
    • Flutter version 2.2.0 at /Users/nikitakhilobok/Documents/flutter
    • Framework revision b22742018b (3 months ago), 2021-05-14 19:12:57 -0700
    • Engine revision a9d88a4d18
    • Dart version 2.13.0
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/nikitakhilobok/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Users/nikitakhilobok/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.5.1, Build version 12E507
    • CocoaPods version 1.10.1
[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
[✓] VS Code (version 1.58.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.25.0
[✓] Connected device (4 available)
    • Pixel 2 (mobile)       • <IP_ADDRESS>:41686                       • android-arm64  • Android 11 (API 30)
    • iPhone (Test) (mobile) • 2bf90be17a0f6983501e24b4830ea2ebb86e869d • ios            • iOS 14.0
    • macOS (desktop)        • macos                                    • darwin-x64     • macOS 11.2.3 20D91 darwin-x64
    • Chrome (web)           • chrome                                   • web-javascript • Google Chrome 92.0.4515.159
• No issues found!

Your screenshot shows allocations, not leaks. The leaks row appears to be empty. Can you please attach the data supporting the claim that there's a leak here?

Your screenshot shows allocations, not leaks. The leaks row appears to be empty. Can you please attach the data supporting the claim that there's a leak here?

Sorry, there was an incorrect description of the problem.

uploaded new screenshots

Hi everyone
I can reproduce the high memory usage when using camera, compared to native iOS camera example using AVFoundation  (camera embedded instead of picker just like the example provided above)
Used the following minimal code sample

complete minimal runnable code sample
import 'package:flutter/material.dart';
import 'dart:async';
import 'package:camera/camera.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData.dark(),
      home: HomeScreen(),
    );
  }
}

class HomeScreen extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: MaterialButton(
          onPressed: () {
            Navigator.push(
                context,
                MaterialPageRoute<void>(
                    builder: (BuildContext context) => CameraScreen()));
          },
          color: Colors.blueAccent,
          child: Text('Open Camera'),
        ),
      ),
    );
  }
}

class CameraScreen extends StatefulWidget {
  @override
  _CameraScreenState createState() => _CameraScreenState();
}

class _CameraScreenState extends State<CameraScreen> {
  CameraController? controller;
  Completer<bool> completer = Completer<bool>();

  @override
  void initState() {
    initCamera();
    super.initState();
  }

  @override
  void dispose() {
    controller?.dispose();
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      floatingActionButton: FloatingActionButton(
        onPressed: () => Navigator.pop(context),
        child: Icon(Icons.arrow_back),
      ),
      body: FutureBuilder<bool>(
        future: completer.future,
        builder: (context, snapshot) {
          if (snapshot.hasData) {
            return Center(child: CameraPreview(controller!));
          } else
            return Center(child: CircularProgressIndicator());
        },
      ),
    );
  }

  Future initCamera() async {
    final List<CameraDescription> cameras = await availableCameras();
    controller = CameraController(cameras[0], ResolutionPreset.max);
    await controller!.initialize();
    completer.complete(true);
  }
}

camera
Native

Logs

stable
master

❗
❗

Check flutter doctor -v outputs for each channel below

flutter doctor -v

✅: No Issue ❗: Issue reproduced
Thanks for filing the issue

Hi all!
During investigation of the camera plugin code, I was able to find the reason (one of) why the consumption is so high. When passing the resolutionPreset parameter to the setCaptureSessionPreset function, the preset for the camera in iOS is set. Apple describes the presets on its website, and I noticed an inaccuracy.
In the function, ONLY presets for video recording are assigned to the _capturedSession.sessionPreset parameter. If we use these preset modes for photography, we will get a lower resolution of photos and increased RAM consumption (since buffering is used).
To avoid this situation, you need to use AVCaptureSessionPresetPhoto (in native). This preset is used for photos and in this case it fits best, but there is no possibility to choose this preset from Flutter.
I attach screenshots before and after changing the library.


Fix boost compile & linker flags

The current boost-modular-build-helper have some shortcomings when it comes to handling flags provided with VCPKG_CXX_FLAGS, VCPKG_C_FLAGS and VCPKG_LINKER_FLAGS variants. I first noticed it when trying to build for Unix with -fPIC but later ended up having linker errors due to code that was not position depended.
This patch honours the flags provided by a triplet and instruments b2 correctly.
Further it patches an issue within the CXXFLAGS in the boost-modular-build.cmake file. The script was assuming that all CXXFLAGS start with a whitespace and replaced all whitespaces with <compileflags>. In the end the user-config.jam was malformed when omitting the whitespace.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: mschmieder sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Thanks again!


OCM-3854 | fix: Update expected output substring for podPidLimit id:68828,68835

OCM-8017 [CI] Debug and fix: Update expected output substring for podPidLimit
Ouput log :- https://privatebin.corp.redhat.com/?7b8b514467f2e015#BWmitNRiVPZ19f3BiBLAGunLuD7TagezUhvEmvpkrUdH

@AkashKanni  Please write the commit title in the format <card id> | test: automated cases id:123456,123457

/test e2e-presubmits-pr-rosa-hcp

/test e2e-presubmits-pr-rosa-hcp

/test coverage

/test e2e-presubmits-pr-rosa-hcp

/test e2e-presubmits-pr-rosa-hcp

@AkashKanni as https://github.com/openshift/rosa/pull/2056 is merged, could you rebase and check if problems still occurs ?

/test e2e-presubmits-pr-rosa-hcp

The fix is already covered in another PR https://github.com/openshift/rosa/pull/2056, closing this PR.


Update press.md

Add to press.md Minify Hugo Generated HTML

 You should sign our Contributor License Agreement in order to get your pull request merged.

Hello @ratson,
thank you for contributing your article about Hugo. I've merged you additions as 3749dc76f7c174f740427cd8f706de1d26c80690 (master) and b086f4b850b76ff711c606e746f9c7c9d40ab012 (v0.15.docs).
Best regards,
Digitalcraftsman


Increase code coverage

.. and hold stable at least 80%

Having excluded the forked parts of the code (they have already been tested), we found out the real percentage of test coverage - 74%. Just a little bit left! :)

It seems that there are enough integration tests for the client, but there are none for the factory. We need to think about how to implement them.
Unit tests are also required for the following classes:
NClient

[ ] RestNClientBuilder
[ ] RestNClientFactoryBuilder

NClient.Standalone

[ ] ClientInterceptor

NClient.Common

[ ] Converters
[ ] ContentExtensions

NClient.Providers.Api.Rest

[ ] RestRequestBuilder

NClient.AspNetCore

[ ] NClientControllerFinder
[ ] VirtualControllerInterceptor
[ ] ControllerQualifier
[ ] VirtualControllerFeatureProvider
[ ] AddNClientControllersExtensions
[ ] ModelExtender

NClient.Providers.Mapping.LanguageExt

[ ] ResponseToEitherBuilder

Go get 'em tiger!

is anyone working on this?

@kolatcole hi!
No, you can do it :)


Info icon off centre on table size view

Technical spec
Templates are here https://github.com/CoderDojo/cp-zen-platform/blob/cf2e0c2eaecd208b91fc1bba1e2871e8f155059b/web/public/templates/dojos/start-dojo-wizard/step-one-register.dust and here https://github.com/CoderDojo/cp-zen-platform/blob/master/web/public/templates/dojos/start-dojo-wizard/step-one-register.dust
CSS is here https://github.com/CoderDojo/cp-zen-platform/blob/cf2e0c2eaecd208b91fc1bba1e2871e8f155059b/web/public/css/dashboard.less

I'm on this

Deployed now, thanks @michaelfbradley


Update documentation

Clarifies the language around prerequisites and installation
Adds .env.template to make it easier for prospective adopters to install
Adds explicit License stanza to the README

Codecov Report

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

@@           Coverage Diff           @@
##           master     #237   +/-   ##
=======================================
  Coverage   49.13%   49.13%
=======================================
  Files          14       14
  Lines         232      232
  Branches       41       41
=======================================
  Hits          114      114
  Misses         96       96
  Partials       22       22

Continue to review full report at Codecov.

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

Sure, I can work on clarifying that this evening.
I'm assuming the keys only really matter when there's a risk of the developer hitting rate limiting because BYS is calling out to GitHub frequently. Is this only really an issue when it's crawling large organizations or users with a lot of repos? Are there other scenarios where a developer might run up against the rate limit?

Updated the language around the API keys. Let me know if this sounds better.

@flickz can you review and merge if everything is good for you?


Let single line command be a single command

this will change existing behaviour, but I could not found a single pipeline where it was used ...
so just use a list of commands if you need them

Codecov Report

Merging #1009 (e4d6352) into master (8da0ee4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1009   +/-   ##
=======================================
  Coverage   51.19%   51.19%
=======================================
  Files          81       81
  Lines        6157     6157
=======================================
  Hits         3152     3152
  Misses       2822     2822
  Partials      183      183

Continue to review full report at Codecov.

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


World generator crashes at large world sizes!

This issue was originally submitted by @githubl0ver69 in SpongePowered/SpongeAPI#1809.

Referred to you from the Nucleus team @  #1136
My problem:

Short version: Can't generate large worlds because the server crashes.
Long version: I can only generate a world so large before the server inevitably crashes with an "java.lang.OutOfMemoryError" exception. I don't understand programming so I'm wondering if there's a possible resolution to this.
The following commands I'm attempting to type with Nucleus:
world border set "Survival" 0 0 102400
world border gen "Survival"

Nucleus's response:

Nucleus simply invokes the Sponge world pre generator, so it's down to that, it's not Nucleus. It tries to manage the memory but sometimes it just can't....
...Ultimately, not a Nucleus problem.

@githubl0ver69 please add versions and logs
though in the end I doubt there can be done much on the Sponge side, pregeneration due to its nature will always take a lot of memory and for huge areas, regular restarts during the process to free up memory are simply needed

There is no reason at all to keep the whole pregenerated area in memory, so restarts shouldn't be required. If sponge doesn't correctly unload the chunks, this is sponge issue. I know vanilla has a limit on how fast it can unload chunks, but it's unlikely any computer can generate chunks fast enough to exceed that, and it's likely sponge removes that limit.

@Barteks2x you can achieve the same thing in vanilla, theres command block scripts to pregenerate worlds.. even those will OOM eventually. why do you think stuff like this  exists? try the build in forge command to pregen and look at the memory consumption after like 30min..
this has nothing to do with what sponge does, if anything pregen is faster with sponge than without thanks to sponge's async lighting. if you seriously think restarts arent required for big maps during pregen, I'm sorry then you are just simply wrong.

Then why I can fly around as a player for thousands and thousands of blocks, generating more and more terrain, without ever running out of memory? And there really isn't much difference in how Minecraft generates terrain for players. I don't know why it runs out of memory but this definitely isn't something that should happen, unless all of the chunks are generated in a single tick (which is a very very bad idea).

I actually investigated it and it turns out the reason (at least for forge generate command) is that AnvilChunkLoader can't write the chunks to disk fast enough. Maybe blocking the server thread if chunksToRemove has too much stuff would be a good idea? This would have the effect of lagging the server if too many chunks are getting unloaded, but it would prevent such out of memory errors. And simply generating chunks less frequently than once per tick would fix it too.

I think I know what your problem is. Sponge adds an optimization to keep chunks in memory for a short period of time after they become unused. Usually, this is intended to improve performance when players keep moving into and out of a few chunks. However, when used with large-scale pregeneration, it can easily become problematic.
To work around this, you can change the chunk-gc-load-threshold in the Sponge configuration to a value like 1000 and restart the server - this will force all extra chunks to be unloaded whenever 1000 chunks are loaded simultaneously. If the server still crashes, decrease that value. Once you're done, change it back to 0.


Cannot add new stacked inlines

So I was giving the master branch a shot and noticed that we're now using Django's own Javascript to dynamically insert/remove inlines (yay!). It seems to be working fine, except that instances of StackedDynamicInlineAdmin don't get the "Add another" link.
I'm using Django 1.9.4 and Mezzanine master (with grappelli-safe master too).
I actually encountered this after developing a fix for a weird issue where stacked inlines were not being ordered by drag-n-drop. I hope to contribute that once we can sort this out.

I have the same problem after fixing ordering stacked inlines too

Hey @jerivas or @Cajoline are you able to make a repo with a sample project demonstrating the issue? StackedDynamicInlineAdmin isn't used directly in Mezzanine anywhere.
Also, there are remnants of Mezzanine's dynamic inline system that we should tidy up as part of fixing this. For example, BaseDynamicInlineAdmin and dynamic_inline.js don't do anything related to dynamic inlines – they're purely related to ordering now.

Alright, just created this demo repo.
Some additional issues I see (might be worth tracking them separately):

Ordering of stacked inlines is broken. Most likely just a missing selector in JS #62 (see comment on April 1, 2016)
The order "handle" is showing in the inline body as well as in the title (it appears as a field after the "bio" field in the demo)

Thanks Ed. I'm taking a look now.

Couple of first steps: https://github.com/stephenmcd/grappelli-safe/compare/dynamic_stacked
Those changes get the "add another" link and expanding/collapsing working. Haven't taken a look at any other issues yet.

@AlexHill
Thank you,
I try this fix but for me not work, in the newest object created it's not possible to edit it i have an validation error (empty field)

@Cajoline Most likely an error in the sample FamilyMember model. Just added a migration to support empty date_of_birth. Try pulling and running migrate.

@AlexHill Adding/removing inlines seems to be working fine. I have fixes for the two issues I described previously, and I have created a fork of my own to compare.
The only outstanding thing left is that new stacked inlines added via "Add another" show a "Remove" text instead of the little "X" on the corner. I'm not sure how Django is copying the DOM to create new inlines, but it's producing different markup at least in the <h3> region of each inline.
Finally, I added another migration to the sample app so that stacked inlines use a RichTextField (at least for me that's a common case). That produces a TinyMCE error in the submit handler defined in dynamic_inline.js. For now I'm just catching the exception and logging it to the console, and it seems to be working fine. Previously the exception prevented the new _order values from being computed.

Hmmm, looks like there's another problem with stacked inlines + rich text. I can not interact with the TinyMCE instances created via "Add another". This looks like a different issue, though, I'll see what I can find and follow up in another issue.

@jerivas I have the same problem it's impossible to interacting with the new rich text, when i click "add another"

Just tested with Mezzanine 4.2.0 / Grappelli 0.4.4 and the fixes by @AlexHill still hold, with the only drawback being that the "Remove" link appears as text instead of the "X" icon on added stacked inlines.
I've contributed my changes as PR #1655.

fac64af09c901225e4921ce58ff0a88636b1abcb


Missing livenessProbe for Cloud Run in Go package

Issue details
There is no livenessProbe available to set. Looks like parameters are the same to startup probe, just different name.
https://cloud.google.com/run/docs/configuring/healthchecks#liveness-probes
Affected area/feature
Go package github.com/pulumi/pulumi-gcp/sdk/v6 v6.41.0

Hi @Mistic92 - we will support this as soon as this change is pulled into an upstream release - soon hopefully! 🤞

The upstream PR was merged and livenessProbe is now available: https://www.pulumi.com/registry/packages/gcp/api-docs/cloudrun/service/#livenessprobe_nodejs


Can not remove Map Image URL

Hi, when I remove this URL the editor keeps adding it back.

Hmm, yeah, as a temp solution you can remove it from the ServerGrid.json manually after you generate it. I'll push a PR shortly that fixes it.

Should be fixed on latest now! :)


upgrade(): angular2 beta.5

ok, it turns out that beta.5 is broken and that's why this PR makes the CLI to generate a project that is broken at runtime. There is a fix on the way: https://github.com/angular/angular/pull/7002
I think we might need to wait for that to land and delay the release further. :-( I hope that we can cut beta.6 tomorrow.

Upgraded to beta.6. Tested locally. This will fail because beta.6 doesn't exist, but I'll rerun travis when it does.

@IgorMinar tests pass. PTAL.

@IgorMinar PTAL

lgtm, go ahead and merge


implement main page (issue #12)

Awesome Job! Love the UI. (Taylor Swift is not that good... but I'll let it pass this one time.)

Yikes unexpected approval! But Taylor is still the BEST!


service have field image is readonly

Bug description
Before 1.23 can edit image field (replace hash or tag) and update service by press update

Now is present only switch "latest" in update windows
Expected behavior
Editable field image in service

Wrong - in service present option "Change container image"


Chrome error on export as PNG...

When I go to file and Export to PNG I am seeing this error in the console and a blank window opens with no artwork...
This is from Chrome console...
Uncaught TypeError: Cannot read property 'location' of null
at Object.renderCallback (method-draw.js:491)
at draw (eval at globalEval (jquery.js:328), :2505:106)
at Object.svg.loadXmlDoc (eval at globalEval (jquery.js:328), :2512:5)
at Object.svg.loadXml (eval at globalEval (jquery.js:328), :2431:8)
at canvg (eval at globalEval (jquery.js:328), :84:8)
at Object.exportHandler [as exported] (method-draw.js:489)
at c.call (svgcanvas.js:927)
at $.SvgCanvas.rasterExport (svgcanvas.js:5621)
at Object.success (method-draw.js:2345)
at fire (jquery.js:3099)
This is from FF comnsole...
TypeError: exportWindow is null - method-draw.js line 491
Any idea on how to fix this?

@clipartinc just fixed this


How to deal with classes with type contexts in the required context?

For instance, the search :: String -> [Char] gives fromString :: !{#Char} -> a with the required context instance fromString [Char]. This instance is defined in StdList for [a] with the type context fromChar a (so, here a is Char). Ideally, we would also mention that fromChar restriction. However, I don't think it should be in the same list as the fromString instance: there may be another instance for fromString [Char] that does not have the fromChar restriction, hence it may not be needed.
I currently don't see a good way to show this information UX-wise, or represent it nicely in the required_context field of libcloogle. But this issue is here to make sure it's known and allow others to think of good representations.

Since these requirements can be nested arbitrarily deep, including the information will only cause confusion. Better to not give it; people will realise this as soon as they use the instance.


property of property in nspredicate

Say you have a message object which has a conversation object as a property.
I'm trying to do a predicate like the following
"conversation.currentUser != sender" but it can't seem to find "conversation.currentUser" on Message (note, there is a message.sender property).

If you have your conversation objects, you should be able to just run the predicate "currentUser != sender" on those objects

Actually, what you tried to achieve can't be really mapped to our current coverage of NSPredicate support. I added "multi-level object equality link queries" to https://github.com/realm/realm-cocoa/issues/1490, where we track that.
For now, you would need to enumerate and filter all messages manually:
let messages = realm.objects(Message).filter { (let message) in
    message.conversation.currentUser != message.sender
}


refactor(nix): use flake-parts and nixfmt

elixir-utils needed an update to add support for elixir 1.17/otp27
as elixir-utils is now using flake-parts, we do so as well to  shrink the size of the lock file. the behavior should be exactly the same.
use nixfmt as a formatter as it is now the official nix formatter.

Pull Request Test Coverage Report for Build e57e54ad272c0fb430cc205affce481abbfbd909-PR-605
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+80.6%) to 80.565%

Totals

Change from base Build<PHONE_NUMBER>0:
80.6%

Covered Lines:
1227

Relevant Lines:
1523

💛  - Coveralls

Ah yes clearly
nods head

Pull Request Test Coverage Report for Build 2d59f4e9287948ce04d1a837bb83a7b0719677d7-PR-605
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+80.6%) to 80.565%

Totals

Change from base Build<PHONE_NUMBER>0:
80.6%

Covered Lines:
1227

Relevant Lines:
1523

💛  - Coveralls


Add back buffer support to graphics device for D3D11

Closing for now. Will reopen when it's in a better state.


double-beep: Watch prodctrow

double-beep requests the watch of the watch_keyword prodctrow. See the MS search here and the Stack Exchange search here.

prodctrow has been seen in 2 true positives, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


Codecov

Codecov Report

Merging #4 into master will decrease coverage by 50.00%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##            master       #4       +/-   ##
============================================
- Coverage   100.00%   50.00%   -50.00%
============================================
  Files            2        2
  Lines            8        8
============================================
- Hits             8        4        -4
- Misses           0        4        +4

Impacted Files
Coverage Δ

CodeCovExample/Classes/CDCVHoge.m
0.00% <0.00%> (-100.00%)
:arrow_down:

Continue to review full report at Codecov.

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


[Feature]: Ensure Consistent Shortcut Behaviors (e.g. Return, Tab, etc.), ideally using Native Accessibility Interactions

What would you like to see added to the NWB GUIDE?
Using Return to advance through a form was previously implemented. However, this behavior notably diverges from the native Tab accessibility feature in several ways, including:

Advancing past a select element
Will not focus FilesystemSelector element
Inconsistent behavior with a boolean selector (i.e. pressing Enter will select the currently focused button instead of advancing)
Stuck on list inputs because Enter submits values to the list
No ability to jump between accordions, even when open

Instead of maintaining an ad-hoc shortcut system on top of native accessibility features, it may be prudent to require users to leverage the native behaviors _except when adding instead of mirroring an interaction`.
For instance, the keywords input supports pressing Enter instead of the submit button to register a written keyword to the list. In the current implementation, this blocks the ad-hoc Enter advancement mechanism but is itself a useful behavior. This would be a good justification to keep this behavior while removing the mirrored Enter / Tab behavior.
Do you have any interest in helping implement the feature?
Yes.
Code of Conduct
Yes
Did you confirm this feature was not already reported?
Yes

Not sure where it comes from, but there's also a weird issue where you can tab backwards, but not forwards, through editable list items like the keywords list.

Summarized and moved to https://github.com/NeurodataWithoutBorders/nwb-guide/issues/846
Re-open again whenever this starts active development


There are some Chinese in Engish Docs

There are some Chinese in Engish Docs

@yankay Thanks for your suggestions.
It's really a mistake, we will fix it.


cleanup

Killing unused file (per  https://github.com/RackHD/on-http/pull/112#discussion_r52050293), and doing some other cleanup since I had a PR already set up. Sorry for the run-around with this @jlmcknight ...

+1

*** BUILD #844 ***
Test Name: test_node_workflows_del_active
Error Details: (500)
Reason: Internal Server Error
HTTP response headers: HTTPHeaderDict({'Content-Length': '55', 'X-Powered-By': 'Express', 'Connection': 'keep-alive', 'ETag': 'W/"37-8t9AZ2rAvzY65nyPPx7Nfg"', 'Date': 'Fri, 08 Apr 2016 15:41:23 GMT', 'Access-Control-Allow-Origin': '*', 'Content-Type': 'application/json; charset=utf-8'})
HTTP response body: {"message":"Failed to cancel 5707d11f5e9aa37f28b0cf9f"}

-------------------- >> begin captured logging << --------------------
urllib3.connectionpool: WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None)) after connection broken by 'ProtocolError('Connection aborted.', BadStatusLine("''",))': /api/1.1/nodes
urllib3.connectionpool: INFO: Starting new HTTP connection (11): localhost
--------------------- >> end captured logging << ---------------------
Stack Trace:   File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-http/RackHD/test/tests/api/v1_1/nodes_tests.py", line 376, in test_node_workflows_del_active
    raise e
'(500)\nReason: Internal Server Error\nHTTP response headers: HTTPHeaderDict({\'Content-Length\': \'55\', \'X-Powered-By\': \'Express\', \'Connection\': \'keep-alive\', \'ETag\': \'W/"37-8t9AZ2rAvzY65nyPPx7Nfg"\', \'Date\': \'Fri, 08 Apr 2016 15:41:23 GMT\', \'Access-Control-Allow-Origin\': \'*\', \'Content-Type\': \'application/json; charset=utf-8\'})\nHTTP response body: {"message":"Failed to cancel 5707d11f5e9aa37f28b0cf9f"}\n\n-------------------- >> begin captured logging << --------------------\nurllib3.connectionpool: WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None)) after connection broken by \'ProtocolError(\'Connection aborted.\', BadStatusLine("\'\'",))\': /api/1.1/nodes\nurllib3.connectionpool: INFO: Starting new HTTP connection (11): localhost\n--------------------- >> end captured logging << ---------------------'

Test Name: pollers_data_get
Error Details: Condition was True.
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/on-http/RackHD/test/tests/api/v2_0/pollers_tests.py", line 157, in pollers_data_get
    assert_false(poller.get('lastFinished', False))
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 67, in assert_false
    raise ASSERTION_ERROR(message)
AssertionError: Condition was True.

@heckj this file has no references anywhere. Perhaps we should just remove it?

@benbp if it's no longer in use, then yeah - let's kill it away. I thought it was when I put up this PR. No workflows or responses leveraging the retry.ipxe thing any longer?

test this please

:+1:

:+1:

Test this please

*** BUILD #933 ***

test this please

*** BUILD #945 ***

test this please


Parsing invalid dates not working as expected

I expect Date.create('02-35-2014') (and any other invalid combinations) to return isValid() = false.
It returns a date of Friday March 7th, 2014 00:00:00.000
it can be reproduced here:  http://sugarjs.com/dates as well

Sorry for the delay here. No, Sugar intentionally allows overshooting of dates as it internally uses the setDate, etc methods which allow overshooting as well. This actually allows for a lot of flexibility when incrementing.
I suppose some kind of "strict mode" might be possible, however this would get hairy very fast as there's a wide range of cases to account for... for example what about February 29th? What about 11:39pm on a day that has a DST shift?

Going to close this one out for now. Feel free to reopen as needed.


Views Drop

Is there an existing issue for this?

[X] I have searched the existing issues

I'm submitting a ...

[X] bug report
[ ] feature request
[X] support request --> Contact me over mail for support https://github.com/MShawon

Description
I Have Send Some Views To My Youtube Video But VIews Were Dropping
IP Royal : Residental Proxies
Environment
- OS : Windows
- Python : Latest
- Script version : Latest

config.json
{
    "http_api": {
        "enabled": true,
        "host": "<IP_ADDRESS>",
        "port": 5000
    },
    "database": true,
    "views": 200,
    "minimum": 50,
    "maximum": 70,
    "proxy": {
        "category": "p",
        "proxy_type": "http",
        "filename": "NewProxy.txt",
        "authentication": true,
        "proxy_api": false,
        "refresh": 4.0
    },
    "background": false,
    "bandwidth": false,
    "playback_speed": 1,
    "max_threads": 5,
    "min_threads": 4
}

well there could be many reasons

did you follow the best practices?
did you use multiple video?
maybe your proxy setup isn't right..did you set TTL?

if you don't know what's the reason..just mail me with enough details and proxy configuration.. I will look into it

can this script cause the YouTube channel to get banned from the YouTube team...?

Hi,
even in my case the views are dropped using sticky sessions
WOuld you be able to help?

well there could be many reasons

did you follow the best practices?
did you use multiple video?
maybe your proxy setup isn't right..did you set TTL?

if you don't know what's the reason..just mail me with enough details and proxy configuration.. I will look into it

Hello @MShawon
i think this bot very perfections if you add login email...
after major update youtube need login. can you add this request for new update YouTube-Viewer
thanks for your attention


AuthenticatorTokenProvider throws on null key

In AuthenticatorTokenProvider.ValidateAsync if the key returned from the UserManager is null, then it throws in the call to Base32.FromBase32:
https://github.com/aspnet/AspNetCore/blob/bfec2c14be1e65f7dd361a43950d4c848ad0cd35/src/Identity/Extensions.Core/src/AuthenticatorTokenProvider.cs#L49
Perhaps it should bail out early if key is null.

Fixed via https://github.com/aspnet/AspNetCore/pull/14037


nixos/gnupg: drop references to gtk2; pinentry-*: build dependent variant with an override instead of choosing the output

Description of changes
This PR basically cleans up all #270266
see https://github.com/NixOS/nixpkgs/pull/270266#issuecomment-1871700542
Closes #276143
Closes #133156
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Just wanted to mention again, that all the other pinentry flavors don't handle both tty and graphical prompts as well as gtk2. It's either or with them, so I don't think it should be dropped as a pinentry flavor.

all the other pinentry flavors don't handle both tty and graphical prompts as well as gtk2.

I am not sure how gtk2 is realted to tty/curses.

It's either or with them, so I don't think it should be dropped as a pinentry flavor.

It is only dropped as a default entry. You can still configure it to use it.

@SuperSandro2000

I am not sure how gtk2 is realted to tty/curses.

The gtk2 pinentry flavor is the only one that will correctly prompt in the terminal if necessary, or graphically if available. e.g. If I SSH into my machine, I can still use gpg with the gtk2 pinentry flavor, because it will put the prompt in the terminal. Meanwhile, it will still give a graphical prompt if I'm using it from the desktop environment. Other graphical pinentry flavors will always put up the graphical prompt on the desktop, even if you're logged in remotely with SSH.

I cannot test all the changes myself - I think they they are correct but I would appreciate it, if other people could help to verify that.

Do not merge for now since only setting one enabledFlavor probably does not provide a proper fallback.

I vaguely recall that curses was supposed to be a fallback, if gui could not be started. But now the only reference I found is #71095 (comment), which is not very informative.

Based on this I am not sure that is even working.

Based on this I am not sure that is even working.

I'm using this functionality daily and others have also noted they are using this in other PRs regarding the breakage of pinenentry-gtk2.

I'm using this functionality daily and others have also noted they are using this in other PRs regarding the breakage of pinentry-gtk2.

yeah, gtk2 but we don't really know that for the other flavors and I kinda remember that jan some time said, that this might not work.


⚠ lukeschweickart.com has degraded performance

In c3f32d9, lukeschweickart.com (https://lukeschweickart.com) experienced degraded performance:

HTTP code: 520
Response time: 425 ms

Resolved: lukeschweickart.com performance has improved in c109319 after 18 minutes.


WIP - Apply changes

need ready for the merge yet but open if anyone wants to review.
WIP tag will be removed when it is ready.

Closing as I am going to switch this around and do some refactoring first.


return with "Got 0 tweets (0 new)"

I tried to run twitterscraper with any certain keywords, but it always return results as "INFO:twitterscraper:Got 0 tweets (0 new)."

same thing after running an example command. Any update?


User story: Auto refresh on active logs

User story: Auto refresh on active logs
As a User I want to have an auto refresh feature to view new incoming logdata on active logs
Sketches
Time based logs

Depth based logs

Acceptance criteria

[ ] [describe criteria]
[ ] [describe criteria]

Also, here are a few points that need to be addressed:

[ ] [describe Constraint]
[ ] [describe Constraint ]

Resources

Lead resource: AkerBP
Contributors: [list names/company]

Will be covered by the more recently groomed #1899 (see comments).

Implemented in #2050.


Only PNG Images are being compared. No results are being produced if the images are in JPG format.

face_recognition version:
Python version:
Operating System:

Description
Describe what you were trying to get done.
Tell us what happened, what went wrong, and what you expected to happen.
What I Did
Paste the command(s) you ran and the output.
If there was a crash, please include the traceback here.

You need to attach some sample files to reproduce this or a log of the error messages you are getting. I can't help just from a title alone.

Ok Sure.


Specification implementation examples

Perhaps as EXAMPLES.md and EXAMPLES.rst.

Wow.  The pandoc conversion from Markdown to rst for a six wide table:
+--------+--------+--------+--------+--------+--------+--------+
| `|Kent | `|Divj | `|Ben  | `|Jame | `|Jero | `|Chri |
| C.     | ot     | Briggs | s      | en     | s      |
| Dodds| | Singh| | |\ Ben | Monger | Engels | Simpki |
| \ Kent | \ Divj | Briggs | |\ Jam | |\ Jer | ns|\ C |
| C.     | ot     |  <http | es     | oen    | hris   |
| Dodds  | Singh  | ://ben | Monger | Engels | Simpki |
| <http: | <http: | eb.inf |  <http |  <http | ns <ht |
| //kent | //boga | o>`__  | ://git | s://gi | tp://g |
| cdodds | s04.gi | `📖 <ht | hub.co | thub.c | ithub. |
| .com>` | thub.i | tps:// | m/Jame | om/jfm | com/ch |
| __     | o>`__  | github | skmong | engels | rissim |
| `📖 <ht | `📖 <ht | .com/k | er>`__ | >`__   | pkins> |
| tps:// | tps:// | entcdo | `📖 <ht | `📖 <ht | `__    |
| github | github | dds/al | tps:// | tps:// | `📖 <ht |
| .com/k | .com/k | l-cont | github | github | tps:// |
| entcdo | entcdo | ributo | .com/k | .com/k | github |
| dds/al | dds/al | rs/com | entcdo | entcdo | .com/k |
| l-cont | l-cont | mits?a | dds/al | dds/al | entcdo |
| ributo | ributo | uthor= | l-cont | l-cont | dds/al |
| rs/com | rs/com | ben-eb | ributo | ributo | l-cont |
| mits?a | mits?a | >`__   | rs/com | rs/com | ributo |
| uthor= | uthor= |        | mits?a | mits?a | rs/com |
| kentcd | bogas0 |        | uthor= | uthor= | mits?a |
| odds>` | 4>`__  |        | Jamesk | jfmeng | uthor= |
| __     |        |        | monger | els>`_ | chriss |
| 👀 ❓    |        |        | >`__   | _      | impkin |
|        |        |        |        |        | s>`__  |
+========+========+========+========+========+========+========+
| `|Kent | `|Divj | `|Ben  | `|Jame | `|Jero | `|Chri |
| C.     | ot     | Briggs | s      | en     | s      |
| Dodds| | Singh| | |\ Ben | Monger | Engels | Simpki |
| \ Kent | \ Divj | Briggs | |\ Jam | |\ Jer | ns|\ C |
| C.     | ot     |  <http | es     | oen    | hris   |
| Dodds  | Singh  | ://ben | Monger | Engels | Simpki |
| <http: | <http: | eb.inf |  <http |  <http | ns <ht |
| //kent | //boga | o>`__  | ://git | s://gi | tp://g |
| cdodds | s04.gi | `📖 <ht | hub.co | thub.c | ithub. |
| .com>` | thub.i | tps:// | m/Jame | om/jfm | com/ch |
| __     | o>`__  | github | skmong | engels | rissim |
| `📖 <ht | `📖 <ht | .com/k | er>`__ | >`__   | pkins> |
| tps:// | tps:// | entcdo | `📖 <ht | `📖 <ht | `__    |
| github | github | dds/al | tps:// | tps:// | `📖 <ht |
| .com/k | .com/k | l-cont | github | github | tps:// |
| entcdo | entcdo | ributo | .com/k | .com/k | github |
| dds/al | dds/al | rs/com | entcdo | entcdo | .com/k |
| l-cont | l-cont | mits?a | dds/al | dds/al | entcdo |
| ributo | ributo | uthor= | l-cont | l-cont | dds/al |
| rs/com | rs/com | ben-eb | ributo | ributo | l-cont |
| mits?a | mits?a | >`__   | rs/com | rs/com | ributo |
| uthor= | uthor= |        | mits?a | mits?a | rs/com |
| kentcd | bogas0 |        | uthor= | uthor= | mits?a |
| odds>` | 4>`__  |        | Jamesk | jfmeng | uthor= |
| __     |        |        | monger | els>`_ | chriss |
| 👀 ❓    |        |        | >`__   | _      | impkin |
|        |        |        |        |        | s>`__  |
+--------+--------+--------+--------+--------+--------+--------+

I'm thinking that we encourage use of Markdown with automated conversion to rst rather than providing rst templates...

Lol, that's hilarious. I agree :-)

That is definitely not for human use... :)

#20

Pulling the discussion about PR #20 over to this thread based upon an attempt to manually mock the current spec for an example Markdown gallery.
@kentcdodds We are starting to delve into implementation issues here and, while not part of the spec, they will be important to how/whether projects use this spec.  The change in the git commit based definition of "contributor" appears to be the issue of most significance in this project.  Perhaps we bag these examples/recommendations and mandatory contribution category indicators altogether in favor of a much more permissive implementation approach that places this in the hands of the project where it likely belongs.  As I understand the goal of this project, it is that all contributors who meet community defined criteria of this term (which is in flux and being worked out at present in this early draft version), are acknowledged for their contribution.  Period.  Whether projects provide an indicator of the type of contribution, an image that represents the contributor, and the way that they implement these indicators should perhaps exist outside of the spec itself or at the very least should be optional components of the specification and decisions for the project teams.
Thoughts?

I think I understand the concern you're expressing. However I worry that if we don't give at least an example and some specific guidelines, projects will be less likely to adopt the idea. Without the guidelines, the spec is no longer a spec, but more of a blogpost about a good idea people should implement in some way.

I completely agree.  I think that guidelines are useful to help with implementation.  I am specifically wondering about the use of these as mandatory parts of the specification:

Indication of the Contribution Category in text or icon image format using the defined Contribution Categories and/or Contribution Categories emoji images (see below).
A link to the Contribution Category in text or emoji format using the defined Contribution Categories and/or Contribution Categories emoji.

As I worked with the Markdown example, it became clear that these items may pigeonhole the entire spec a bit and act as disincentives to use in some projects.  Should display of the types of contributions in a list of contributors be mandatory or should it simply be the inclusion of individuals in the list who meet the community defined criteria as "contributor"?    If we choose the former, projects that do not fit the mold of a small number of easily displayed contribution categories per contributor will not bother with implementation of this and will therefore not be in compliance with the specification.  If we choose the latter, there is much greater flexibility for a project to determine the hows of acknowledgment and this, in my view, opens the spec to a greater variety of project types and project maintainers.  It really hinges on whether, and at what level of granularity, acknowledgment is going to be defined.  Is there a lower minimum "level" of acknowledgment implementation that we can specify if this is felt to be an issue?

Just to be clear, you're basically suggesting that we move those two bullet points to the optional section and that we allow people to comply to the spec even if they don't specifically call out the types of contributions people have made?
I think I'm ok with that. Thoughts from others welcome :thought_balloon:

@fhemberger
@ben-eb
@Jameskmonger
@jfmengels
@bogas04
@frigginglorious
Thoughts about the issues in https://github.com/kentcdodds/all-contributors/issues/15#issuecomment-191324682?
I don't think that this means that we should not provide a set of guidelines and maybe even examples (where this originated) of the contributor list, nor that tools to support the specification and optional guidelines for contributor lists should be developed.  I do think that if we pull ourselves out of mandatory hows of acknowledgment implementation this becomes an acceptable specification for a much larger group of individuals & projects.  I would favor specifying the who.

Seems like being more permissive makes sense to me. For example, there might well be people who want to use GitHub style emoticons for contributors instead of Unicode, etc.

all contributors who meet community defined criteria of this term (which is in flux and being worked out at present in this early draft version), are acknowledged for their contribution. Period.

:+1: The aim of the spec is IMO simply to indicate what should be done, in regards of recognizing contributors and "displaying" them, not how:

Indicating what should be considered a contribution (code, docs, talks, translation, bug reports, ...)
broad guidelines on how to make the contributors stand out (list them in the README, add a contributors section, ...)

That said, the rest of the work IMO is to set up easy guidelines/workflows so that respecting the spec does not become too much of a burden for maintainers:

Give contributor list examples
Give ideas of how to display contributors (emoji is one way, but just one potential way)
Explore and document/provide friction-less workflows. We have already seen problems with conflicts in merges, and we should find ways to avoid that as best as possible. And neither maintainers nor contributors should also have to add themselves to a Markdown table, figuring out how Markdown works, why the display breaks when adding the 8th contributor or 4th contribution emoji.

Provide tools (well, that's why I started the CLI at least), GH bots, ...
Indicate how maintainers can communicate with the contributors in order to know how the user would like to get represented.

Not sure if you agree, but IMO all (or almost all) the work should be handled automatically or semi-automatically, I think it will otherwise be really too painful for maintainers.
In short: more permissive also makes sense to me (Sorry if I totally missed the point ^^')

we allow people to comply to the spec even if they don't specifically call out the types of contributions people have made

Seems like being more permissive makes sense to me.

The aim of the spec is IMO simply to indicate what should be done, in regards of recognizing contributors and "displaying" them, not how

I think that we are all saying similar things and it seems that there is some level of agreement about the laxity in the implementation / layout of the acknowledgments associated with the specification.  If this is the case, should we create new issue reports for the mandatory parts of the spec in its current iteration so that we can discuss these in more detail to nail down the wording?  It seems that there may need to be a bit of shuffle between what are currently considered mandatory and optional items.  Perhaps we call those that deal with how one formats their contributor tables / lists "guidelines for implementation" and they exist outside of the spec altogether?
This would turn the spec into something that:

defines a contributor based upon community defined categories that represent contributions to open source work (as currently defined in the Emoji table & open to vetting + modification by the community)
specifies that all contributors should receive project acknowledgment as a contributor in some "prominent" way if they meet the definition of a contributor based upon #1 above

The details of how the acknowledgment happens are then largely left to the projects that implement the spec, though we provide guidelines that might work for projects of various sizes/contributor numbers and suggest associated tools to ease the work associated with implementation of the spec (which is going to be a damn hard transition for many projects even if they are very motivated to support this!).

I +1 the apparent general consensus :-)

@kentcdodds We are starting to delve into implementation issues here and, while not part of the spec, they will be important to how/whether projects use this spec. The change in the git commit based definition of "contributor" appears to be the issue of most significance in this project. Perhaps we bag these examples/recommendations and mandatory contribution category indicators altogether in favor of a much more permissive implementation approach that places this in the hands of the project where it likely belongs. As I understand the goal of this project, it is that all contributors who meet community defined criteria of this term (which is in flux and being worked out at present in this early draft version), are acknowledged for their contribution. Period. Whether projects provide an indicator of the type of contribution, an image that represents the contributor, and the way that they implement these indicators should perhaps exist outside of the spec itself or at the very least should be optional components of the specification and decisions for the project teams.

I'm fine with that. Honestly I've focused more of my efforts around the all-contributors-cli project. The spec was originally created before that CLI existed. I'm looking forward to more automation to be written (like a GitHub bot that automatically updates the .all-contributorsrc and the README.md for us).
I'm less concerned about how folks implement this spec. I'm more interested in people get attribution for their work.

@chrissimpkins Have you had a chance to prepare a PR for that?

@Berkmann18 Unfortunately I have not. Apparently three years was not sufficient time. :) My apologies.
Is this still something of interest? I have been following very peripherally and will need to catch up with where things are to submit this.

@chrissimpkins It's still something of interest, have you looked at the website, the CLI and the bot?

have you looked at the website, the CLI and the bot?

Just checked out all of the links.  Lots of work going on here.  Looks great!  👏  to all of the contributors  :)

It's still something of interest

I would be willing to PR in a set of mocked up README docs that follow the spec if your request is to address the OP comment that I made.  Does the CLI tool support *.rst as well as *.md files?  If not, do you want *.rst too?

I would be willing to PR in a set of mocked up example README docs that follow the spec if your request is to address the OP comment that I made.

Awesome.

Does the CLI tool support *.rst as well as *.md files? If not, do you want *.rst too?

It supports both (and possibly more but I only tested on both extensions).
I think having the *.rst one might be good for those who use those files like how *.md files are used on GH.

@chrissimpkins Have you manage to get something working?

hi colleagues @Berkmann18 @chrissimpkins i was digging around trying to find whether there is an .rst implementation (or markdown) rather than HTML for this bot. i use readthedocs which doesn't love html tables embedded within rst files. I may have missed this in the docs but is there a way to implement the bot so it writes the contributor table using rst or md? this issue suggests it may be possible?
thank you so much for any guidance. this is a super cool tool.

@lwasser There's no option (afaik) for now that enables you to tell the bot which format to use but I reckon it would be a great feature to add.
Would mind opening a PR for that?

Friendly ping @lwasser .

hey @Berkmann18 a PR for this is beyond my current tech skillset at the moment!!  This is a great project however!

Hey


Added blog with changes according to contribution guidelines

Checklist

Please note that in case of below checklist not updated accordingly, the maintainers have the right to immediately close your pull request.

[x] You created a branch from dev branch.
[x] You PR is raised on dev branch and not onmaster.
[x] Blog follows Blog Guidelines.
[x] You have read the Contribution Guidlines before creating this PR.
[x] Checked for any duplicate blog entry.
[x] Checked for all grammatical errors in the blog.
[x] You have not published the blog content anywhere else on the internet on platforms like medium, dev.to etc.
[x] The content is not copy-pasted from anywhere else on the Internet.

Description of change
Added the blog and made the request on the dev branch

Author Details for Blog Post Entry

id: arshita129
github: https://github.com/arshita129
linkedin: https://www.linkedin.com/in/arshita-2370221b4/
#233

@puneetsingh24  Why is this labelled off-topic?


CAMEL-17478 camel-aws2-s3 Aws credentials parameters are mandatory for downloadLibnk for autowired client

Issue https://issues.apache.org/jira/browse/CAMEL-17478
My previous PR (https://github.com/apache/camel/pull/6736) was too strict with doc change. The real behavior is not so strict.
I'm fixing doc to describe current behavior correctly + I'm adding a junit test to cover the negative case with downloadLink action with S3 client from the registry.

Error is not caused by style violation from my change. It is caused by
Error:  Failed to execute goal on project camel-knative-api: Could not resolve dependencies for project org.apache.camel:camel-knative-api:jar:3.15.0-SNAPSHOT: Could not find artifact org.apache.camel:camel-cloudevents:jar:3.15.0-SNAPSHOT in apache.snapshots (https://repository.apache.org/snapshots/) -> [Help 1]


Transition to only support Python 3.5

Mostly for typing and being more organized. I think we need to eventually transition to only support python 3.5.

Disagree; Python 2.7 is still common enough that I think it's worth supporting even at the cost of some readability.
(I use Python 2.7 myself primarily, so I'm not without bias, but if there is enough support for 3.5 only then I'm not against it.)

Project is new, so I think it's much better to switch the standard development to 3.5 and support 2.7 only through six.

There's a lot of work to be done since original code base is that bad. This should wait until after refactor.

Disagree, most of the module's i use for plugin(s) are python 2.7

For the foreseeable future, we will continue to support both.


reverseYears prop should only reverse the order in years overlay and months overlay should be unaffected

Describe the bug
When reverseYears prop is set to true, the rows in months overlay is also reversed.
Mar    Feb    Jan
Jun    May    Apr
Sep    Aug    Jul
Dec    Nov    Oct
To Reproduce
Steps to reproduce the behavior:

Go to https://vue3datepicker.com/api/props/#reverseyears
Click on the date picker, then click on the month.
See months overlay.

Expected behavior
The month overlay should remain in it's original order and the reverseYears prop should have no effect on it.
Screenshots
Not able to attach.
I have fixed this and will commit the codes after submitting this bug report.

Yes, I did saw. Great work and I look forward to it.


Get basic react example tree running

Fixes a couple of bugs, and allows directory navigation and viewing files

Added syntax highlighting

Updated styles to match master banch, and added commits and commit paths

I'm happy to merge to master, and work on the styles to have them match ipfs css

By the way it looks like the server is down, so the demo doesn't work at the moment (unless you have it cached locally): https://igis.devtty.eu


Type check for setVariable and getVariable funcs

Type check is required for below functions :
template<typename T, unsigned int N> __device__ T FLAMEGPU_API::getVariable(const char(&variable_name)[N]);
and
template<typename T, unsigned int N> __device__ void FLAMEGPU_API::setVariable(const char(&variable_name)[N], T value)

RTTI functions are not supported in device code (https://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html#rtti)
We probably can't do this.


FocusTraversal issues with multiple ListViews and GridView

Problem
I encountered some FocusTraversal issues with ListView combined with another ListView or GridView when navigating on Desktop with arrow-keys or on an Android TV with the d-pad. The navigation does not behave as expected when reaching the end or the beginning of a ListView or GridView. I've sumarized some scenarios, their actual behavior and my expected behavior.
Reproducing examples
Scenario 1.
Start fresh and right arrow (or right d-pad) and navigate to the end of the green list. Keep pressing the right button and notice how the Focus jumps from "Green 19" to "Blue 11" continuing to navigate through the blue ListView.
Expected behavior: Navigating with right arrow-key should stop at the last element of the green ListView.
Scenario 2.
Start fresh and navigate one down to the blue ListView and navigate right (or right d-pad) to the end of the blue list. Keep pressing the right button and notice how the Focus jumps from "Blue 19" to "Green11" continuing to navigate through the green ListView.
Expected behavior: Navigating with right arrow-key should stop at the last element. of the blue ListView.
Scenario 3.
Start fresh and navigate down to the Grid. Navigate to the end of any row, Notice how the focus jumps from "Grid 8" or "Grid 17", etc.. to "Blue 11" continuing to navigate through the blue ListView.
Expected behavior: Navigating with right arrow-key should stop at the last element of a grids row.
Scenario 4.
Navigate to the end of the green ListView, and then navigate to the end of the blue ListView. Now, still in the blue ListView, navigate back (left arrow or left d-pad) to the beginning of the blue ListView. Keep navigating back with the left arrow and notice how the focus jumps from "Blue 0" to "Green 8".
Expected behavior: Navigating with left arrow-key should stop at the first element of the ListView.
Scenario 5.
Navigate to the end of the blue ListView. Navigate down to the Grid. Navigate back in the GridView from "Grid 8" to "Grid 0", or "Grid 17" to "Grid 9", etc.... Keep navigating back with the left arrow and notice how the focus jumps from "Grid 0" (or Grid 9, etc...) to "Blue 8".
Expected behavior: Navigating with left arrow-key should stop at the first element of the grids row.

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: Column(
          children: [
            Container(
              color: Colors.green,
              height: 100,
              child: ListView.builder(
                scrollDirection: Axis.horizontal,
                itemCount: 20,
                itemBuilder: (ctx, index) => RawMaterialButton(
                  onPressed: () {},
                  child: Text('Green $index'),
                ),
              ),
            ),
            Container(
              color: Colors.blue,
              height: 100,
              child: ListView.builder(
                scrollDirection: Axis.horizontal,
                itemCount: 20,
                itemBuilder: (ctx, index) => RawMaterialButton(
                  onPressed: () {},
                  child: Text('Blue $index'),
                ),
              ),
            ),
            Expanded(
              child: GridView.builder(
                itemCount: 200,
                gridDelegate: SliverGridDelegateWithFixedCrossAxisCount(
                    crossAxisCount: 9,
                    childAspectRatio: 1,
                    crossAxisSpacing: 0,
                    mainAxisSpacing: 0),
                itemBuilder: (ctx, index) => RawMaterialButton(
                  onPressed: () {},
                  child: Text('Grid $index'),
                ),
              ),
            )
          ],
        ),
      ),
    );
  }
}

flutter doctor -v
[✓] Flutter (Channel master, 1.24.0-8.0.pre.194, on Microsoft Windows [Version 10.0.20251.1], locale en-AT)
    • Flutter version 1.24.0-8.0.pre.194 at D:\Projects\Development\Flutter\flutter-sdk-win
    • Framework revision 018467cdb1 (10 hours ago), 2020-11-11 02:04:03 -0500
    • Engine revision 81f219c59c
    • Dart version 2.12.0 (build 2.12.0-31.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at C:\Users\adonis\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[✓] Visual Studio - develop for Windows (Visual Studio Community 2019 16.8.0)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
    • Visual Studio Community 2019 version 16.8.30709.132
    • Windows 10 SDK version 10.0.18362.0

[✓] Android Studio (version 4.1.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[✓] VS Code (version 1.51.0)
    • VS Code at C:\Users\adonis\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.16.0

[✓] Connected device (1 available)
    • Windows (desktop) • windows • windows-x64 • Microsoft Windows [Version 10.0.20251.1]

• No issues found!

@ad-on-is Again this seems to be similar to 67814. I'd suggest you to follow-up there since it has been reopened.
Closing this as duplicate. If you disagree, write in comments and I'll reopen.
Thanks.

No, this is a totally different issue. The other describes the behavior in the GridView itself, this, on the other hand, describes the issue related between multiple ListViews and GridViews.

@darshankawar Could you please reopen this one?


OAIRepository: marcxml output format

FIX Switched names in config. (closes #2962)

FIX Dummy variable not needed causing and error.

Signed-off-by: Jaime García<EMAIL_ADDRESS>

@jgarcial thanks! Can you please amend commit message:
oairepository: fix marcxml output format

* FIX Switches keys in CFG_OAI_METADATA_FORMATS configuration mapping.
  (closes #2962)

* FIX Amends bfe_oai_marcxml element since get_preformatted_record
  does not return a tuple anymore.

Signed-off-by: Jaime García<EMAIL_ADDRESS>Reviewed-by: Jiri Kuncar<EMAIL_ADDRESS>...

ping @jgarcial

@jirikuncar
I just rebased and pushed the amended commit.

@jgarcial thanks!


restic prune ends with Fatal: index is not complete

Output of restic version
restic 0.16.4 compiled with go1.21.6 on linux/amd64
What backend/service did you use to store the repository?
rclone
Problem description / Steps to reproduce
1m41s ➜ restic prune
enter password for repository:
repository f7f0ba29 opened (version 2, compression level auto)
loading indexes...
[0:02] 100.00%  42 / 42 index files loaded
loading all snapshots...
finding data that is still in use for 37 snapshots
[0:26] 100.00%  37 / 37 snapshots
searching used packs...
{<data/46f16cfd> <data/64e597b3> <data/dcfe4bbf> <data/8e9cef5e> <data/314589c3> <data/2d9e4048> <data/c3319088> <data/07cb59af> <data/8ef04398> <data/6fb50d53> (4034 more)} not found in the index
Integrity check failed: Data seems to be missing.
Will not start prune to prevent (additional) data loss!
Please report this error (along with the output of the 'prune' run) at
https://github.com/restic/restic/issues/new/choose
Fatal: index is not complete

Did you notice any errors reported in prior restic runs or did something unexpected happen? Maybe an interrupted network connection or did the host go into standby while restic was running?
Is this the first failing prune run? Do you have logs of the backup and prune run before the failing one?
Did restic report any errors there?
How often do you run backup, check and/or prune?
Is the repository used by multiple hosts or just a single host? Do you use the unlock command or is it called automatically from your backup scripts?
Please run restic check to analyze the damage to the repository. If downloading all data from the repository isn't a problem, then please run restic check --read-data instead to perform a full integrity check.
It would be helpful to know which snapshots are missing blobs: Please run restic find --blob 46f16cfd 64e597b3 dcfe4bbf 8e9cef5e 314589c3 2d9e4048 c3319088 07cb59af 8ef04398 6fb50d53 (those are the ids of the blobs reported as missing) to find the affected snapshots (well, at least some of them).

Hi,
I started from scratch and did this:

init a local reposirtory (on a ext4 removable media)

restic -r /media/myuser/mydisk/backup init

backup to local repository

restic -r /media/user/disk/backup backup /home/user/

init a distant repository using a rclone backup

restic -r rclone:pcloud:restic-backup init

copy local repository to distant repositroy

restic --repo rclone:pcloud:restic-backup copy --from-repo /media/myuser/mydisk/backup/

check local repository

restic -r /media/myuser/mydisk/backup/ check
--> 319 additional files were found in the repo, which likely contain duplicate data.

check distant repository : FATAL ERROR

restic --repo rclone:pcloud:restic-backup check
588 additional files were found in the repo, which likely contain duplicate data.
This is non-critical, you can run restic prune to correct this.
check snapshots, trees and blobs
[0:24] 100.00%  2 / 2 snapshots
Fatal: repository contains errors

prune distant repository : FATAL ERROR

restic --repo rclone:pcloud:restic-backup prune
enter password for repository:
repository ca0bb18f opened (version 2, compression level auto)
loading indexes...
[0:02] 100.00%  183 / 183 index files loaded
loading all snapshots...
finding data that is still in use for 2 snapshots
[0:08] 100.00%  2 / 2 snapshots
searching used packs...
collecting packs for deletion and repacking
pack 1302d93e: calculated size 17252774 does not match real size 2834432
Run 'restic repair index'.
[0:03] 7.39%  2836 / 38393 packs processed
Fatal: pack size does not match calculated size from index
I'm leaving the repo as is for now, to try to troubleshoot this...
Regards
Franck

pack 1302d93e: calculated size 17252774 does not match real size 2834432

Sorry for the late reply. If I remember correctly, then pCloud can store multiple versions of a file. Can you check whether the file in data/13/1302d93e[...] has multiple versions? Please download it and run shasum -a256 on that file. The resulting hash should match its filename.
The pack file in question was likely damaged during the upload, then real size of 28MB is larger than what restic would create using the default settings. This is unfortunately not the first time we've seen such problems in conjunction with pCloud.
Did rclone report any warnings while uploading the repository copy to pCloud? Fixing the repository should be rather straightforward. Delete the broken file, then run restic repair index and afterwards copy the snapshots again.

Thanks @MichaelEischer
Indeed, hash of data/13/1302d93e[...] does not match with file name. So I deleted the file, repaired the index and copied snapshots again.
Then check, prune, check worked:
5m33s ➜ restic --repo rclone:pcloud:restic-backup check using temporary cache in /tmp/restic-check-cache-1671829285 enter password for repository:  repository ca0bb18f opened (version 2, compression level auto) created new cache in /tmp/restic-check-cache-1671829285 create exclusive lock for repository load indexes [0:06] 100.00%  14 / 14 index files loaded check all packs check snapshots, trees and blobs [0:26] 100.00%  9 / 9 snapshots no errors were found
And yes, rclone did display some errors, that were supposedly solved after retries. Unfortunately I didn't keep the logs...
Thanks again
Franck


There is no any filter in the video section

Can you show me the screenshot?

Here is a preview, maybe it can solve your problem.


Support managed Opensearch

Current odd elasticsearch does not work with AWS managed Opensearch.

Implemented in odd-collector


Add OTP and Linked Connections to API section

:bus:
Holy crap, Linked Connections looks really cool. Does it work well in practice?

Don't have personal experience with it, unfortunately.


Form validations (DO NOT MERGE)

For #1752
Started work on the new form validations logic. Please review the approach before I start going through and updating all the views/controllers accordingly:

Removed the ariatiseForm.js and validations.js files and all references
Removed validation error messages for JS from the views/layouts/application.html.erb
Added a generic requiredField.js which continues to add the asterisk to fields marked aria-required="true". This was originally part of the 2 JS files above.
Consolidated the 3 error message helpers in ApplicationController to one failure_message method
Added a views/layouts/_error.html.erb
Added a named yield section to views/layouts/application.html.erb notification section. Individual views can render content_for that named section
Simplified the Notifications and Theme controllers/views in SuperAdmin namespace and updated their save logic so that the user isn't driven back out to index when they create/update a record
Added some CSS to take advantage of Rails field_with_errors class that it adds to form elements that have errors so that the boxes have a red border.
I also added a generic ActiveRecord:RecordNotFound handler to the ApplicationController that will redirect to a branded 404 page in production (related to #899)

Let me know what you think of the approach. Happy to adjust if there's a better/more conventional way to handle things.

+1 for the interactive rebase, but I like the approach taken here.

Closing as this one is no longer relevant


Implement file versioning

We need a way to detect file versions to allow for updating the format in the future.

The best feature is one that doesn't need any code to support.
I've decided that we already have enough versioning support: we have a lot of values in the u8 space of PageHeader that can be used for breaking changes to root formats if needed.


vmware esxi 5.5 - ova hardware version

Hi,
We'd like to use k-a on esxi 5.5 which only supports hardware version 10.
Is there any reason you build your OVA template using vmware hardware version 11?
Do you build the OVA with packer or similar? If so please could you share the source?

@dayglo We can provide you steps to convert OVA file to support hardware version 10 using vCenter Converter.
VMware Issue: https://github.com/vmware/kubernetes/issues/128

@dayglo Please use this image vmx-10 image on esx5.5 - https://storage.googleapis.com/kubernetes-anywhere-for-vsphere-cna-storage/KubernetesAnywhereTemplatePhotonOSESX5.5.ova

@dayglo just following up regarding new image I shared above.
Can you please close this issue, if you are able to deploy cluster using this image.

Thanks for sharing that link

@dayglo provided links works fine for @psyolent on ESX 5.5
Can you close this issue?


Update version: LizardByte.Sunshine version 0.20.0

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/112895&drop=dogfoodAlpha

[Policy] Needs-CLA

[Policy] Needs-Author-Feedback

Do NOT merge!


Move defaultLogPolicy to after Sign phase

This change pushes logging to the end of the pipeline, allowing for retried requests to be logged.
Fixes #20910

API change check
API changes are not detected in this pull request.

Good job on this clean change!
There is a test failure in the Browser test, the reason seems to be that we don't add all the policies when running in the browser

you may want to modify your expected policies based on isNode.

I forgot to put that in the commit message, but that's done. Hoping for some more comments before merging this one.


[FAQ] Add list of available built-in functions

Enhancement
Add an introduction and list of:

built-in functions available for arrays
built-in functions available for strings

what builtin functions are we talking here @Peefy ?


Added initial null-safety conversion.

Addresses #84. @kevmoo or @grouma, is there any chance that you can please review these changes? This is primarily based on the Dart Null-Safety migration tool. However, I had to make slight minor changes to the way VirtualDirectory locates a resource from paths using an Iterator.
Long-story short, since VirtualDirectory._locateResource was null-checking on whether the current item existed, and since Iterator.current is not nullable, I had to write a simple re-implementation of Iterator that allows for a nullable current item.
Nevertheless, after using that custom Iterator class, all 126 tests passed.
Feel free to comment as needed, and I'll address them at my earliest convenience. Thanks in advance.

@googlebot I fixed it.

@googlebot I fixed it.

Looks like the legacy SDK isn't set up for null-safety. Dunno if that can be waived.

Looks like the legacy SDK isn't set up for null-safety. Dunno if that can be waived.

We just need to update the SDK it runs on to 2.12.0 (which is the new min sdk for the package).

Looks like the legacy SDK isn't set up for null-safety. Dunno if that can be waived.

We just need to update the SDK it runs on to 2.12.0 (which is the new min sdk for the package).

Feel free to update the quick actions script as needed on this branch. Otherwise, please let me know what changes to make and where, and I'll try to hammer them out tonight.

@jakemac53 a gentle reminder regarding the recent changes that I made as per your feedback. Thank you in advance.

This looks good to me (see one small additional nit) - I also pushed up a commit to bump the version and add a changelog entry.

Definitely will address them tonight. Also, I did leave comments regarding making _unhandledController in virtual_host.dart late. Please let me know how you want me to approach it.

Rolling this internally just to double-check and then we can publish


Added FP32 to FP16 conversion transformation

@diyessi can you suggest what is wrong in CI ? Just can't find any error message.


The RelayInformationDocument class inside the Relay class is using member names that do not match the JSON.

Describe the bug
The RelayInformationDocument class inside the Relay class is using member names that do not match the JSON.
To Reproduce
Steps to reproduce the behavior:

Run NostrExamples.
The console displays "UnrecognizedPropertyException: Unrecognized field "supported_nips" (class nostr.base.Relay$RelayInformationDocument), not marked as ignorable (11 known properties: "contact", "pubkey", "software", "version", "limitation", "name", "description", "fees", "paymentsUrl", "supportedNipExtensions", "supportedNips")".

Additional context
In the JSON, the correct names to be used are "supported_nips", "supported_nip_extensions", and "payments_url" instead of "supportedNips", "supportedNipExtensions", and "paymentsUrl".

Correct. This is fixed in the feature/feature_bug_fixes branch. Will merge soon

Also, please note:
In the new branch, I introduce the ApplicationConfiguration class to configure the other properties file names - Identity (profile.properties), Client (relays.properties), etc.
You will need an app.properties in the same folder as the jar file, or in your classpath.
Please look in the code to check how I am using it.

The JSONJsonProperty annotation on line 82 of Relay.java in the bugfix branch is "supported_nipd", but it should be "supported_nips", right?

Yes. Typo.
Sent with Tutanota, enjoy secure & ad-free emails.
1 Jun 2023, 09:35 by @.***:

The JSONJsonProperty annotation on line 82 of Relay.java in the bugfix branch is "supported_nipd", but it should be "supported_nips", right?
—
Reply to this email directly, > view it on GitHub https://github.com/tcheeric/nostr-java/issues/36#issuecomment-1571513936> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/ABQMG7AKUU5E6GMQFMR7UI3XJBA5BANCNFSM6AAAAAAYS5LTGA> .
You are receiving this because you were assigned.> Message ID: > <tcheeric/nostr-java/issues/36/1571513936> @> github> .> com>

Fixed


Remove text loading in basic walk through demo.

@RAMitchell For the Python package, I want to move away from the text parser in dmlc, or at least it should not be the first option users think of (as in the basic walkthrough). If we want to advertise its performance benefit, we should first fix related issues like: https://github.com/dmlc/xgboost/issues/4356 , and probably move the maintenance from dmlc-core to XGBoost.


Changed API url

This URL doesn't work [404 not found]
https://raw.githubusercontent.com/CSSEGISandData/COVID-19/master/csse_covid_19_data/csse_covid_19_time_series/time_series_19-covid-Confirmed.csv
Please let me know if you change the address

@mauricioduqueorozco
They've changed it to use underline.
here


Add it to npm?

This is a great module m8. I went through the code too. Well written imo. Why isn't it in the npm registry though?
Pick a nice name(by feeding the entire github username registry into this chain and generating a nice name) and push it to the npm registry!

Thanks. I should clean it up and write some examples first though :)

@fwg any updates on this?