services: resolve community slugs for record search

Closes #1188.

:heart: Thank you for your contribution!
Description
Please describe briefly your pull request.
Checklist
Ticks in all boxes and 🟢 on all GitHub actions status checks are required to merge:

[x] I'm aware of the code of conduct.
[x] I've created logical separate commits and followed the commit message format.
[x] I've added relevant test cases.
[x] I've added relevant documentation.
[ ] I've marked translation strings (for relevant code).
[ ] I've followed the CSS/JS and React guidelines (for relevant code).
[ ] I've followed the web accessibility guidelines (for relevant code).
[ ] I've followed the user interface guidelines (for relevant code).
[ ] I've identified the copyright holder(s) and updated copyright headers for touched files (>15 lines contributions).
[ ] I've NOT included third-party code (copy/pasted source code or new dependencies).

Third-party code
If you've added third-party code (copy/pasted or new dependencies), please reach out to an architect.
Reminder
By using GitHub, you have already agreed to the GitHub’s Terms of Service including that:

You license your contribution under the same terms as the current repository’s license.
You agree that you have the right to license your contribution under the current repository’s license.

We need to consider if this needs to be backported to 9.1

@fenekku the issue was opened by you, how important is this for your use cases in LTS 9.1?
@ppanero be aware that we cannot cherry-pick the commit, we have refactored resources/services. We will need to copy/paste the fix.

This fix was desired by one of our librarians who is performing automated checks of the communities we imported. We only know the community identifiers in advance.
Thanks for the fix. At this point, we've moved on to v11 because features we need are there. So, for us, as long as it goes in a patch for v11 we are good.


Mediaflux like it best (faster) when http connections are kept open over multiple API calls

Currently we code our http connection every time we make a request to Mediaflux.
It would be good it we could keep the http connection to mediaflux open for the duration of the controller, or longer.
Open Call: https://github.com/pulibrary/tiger-data-app/blob/main/app/models/mediaflux/http/request.rb#L59
Close call: https://github.com/pulibrary/tiger-data-app/blob/main/app/models/mediaflux/http/request.rb#L71
In theory we could pass in an http object to the request and note that it is not ours so the we would not shut it down
At the moment we assume the http object is ours and shut it down every time.

This should be revisited after we sort out authentication.

Carolyn also found that the Docker container was dying when excessive connections were being created and destroyed for aterm. Perhaps there is a database connection pool pattern which must be implemented?

This Python client indicates that users need to implement their own connection pool for concurrent tasks.

This is not completely resolved, as the finalizer implemented in https://github.com/pulibrary/tiger-data-app/pull/517 is not called as consistently as I was hoping that it might be. I also do not completely have a clear understanding of the acceptance criteria for this, and would like to please request assistance and review with understanding what remains to be addressed for this.

As discussed during the check-in meeting on 02/26/24, the finalizer at the Object-level is actually introducing a performance decrease. This must be removed, and then this issue can be closed.


Configurable sketch accuracy in merge rollup task

Merge rollup task feature enhancement 2
Adds the capability to configure sketch precision / accuracy for different rollup buckets.  This can result in a space saving for use cases where historical data does not require high accuracy
See: https://github.com/apache/pinot/issues/14310
release-notes:

New configuration options

NOTE: This PR is a work in progress and has been created to demonstrate the concept

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

Project coverage is 0.00%. Comparing base (59551e4) to head (8d6697f).
Report is 1278 commits behind head on master.

:exclamation:  There is a different number of reports uploaded between BASE (59551e4) and HEAD (8d6697f). Click for more details.
HEAD has 53 uploads less than BASE

Flag
BASE (59551e4)
HEAD (8d6697f)

integration
7
1

integration2
3
1

temurin
12
1

java-21
7
1

skip-bytebuffers-true
3
0

skip-bytebuffers-false
7
1

unittests
5
0

unittests1
2
0

java-11
5
0

unittests2
3
0

integration1
2
0

custom-integration1
2
0

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #14373       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436        3     -2433
  Lines        133233        6   -133227
  Branches      20636        0    -20636
=============================================
- Hits          82274        0    -82274
+ Misses        44911        6    -44905
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <ø> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <ø> (ø)

java-11
?

java-21
0.00% <ø> (-61.63%)
:arrow_down:

skip-bytebuffers-false
0.00% <ø> (-61.75%)
:arrow_down:

skip-bytebuffers-true
?

temurin
0.00% <ø> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

NOTE: This PR is a work in progress and has been created to demonstrate the concept

This is ready for review ?

NOTE: This PR is a work in progress and has been created to demonstrate the concept

This is ready for review ?

This is ready for review but it stops short of introducing the parameters for every single aggregator function.  Since initial feedback seems positive, I will include the additional sketches in this PR shortly.

NOTE: This PR is a work in progress and has been created to demonstrate the concept

This is ready for review ?

This is ready for review but it stops short of introducing the parameters for every single aggregator function. Since initial feedback seems positive, I will include the additional sketches in this PR shortly.

Im assuming these will additional sketch params building on top of what you have now right? If it makes sense, you can break this into 2 PRs as well.

@swaminathanmanish let's break it into multiple PRs as that would make the review process easier.  You are correct - I only intend to build upon what I have here.
I do have the additional documentation that is required in mind as well.


[Request] Firefox port

Hi,
first of all thank you for this extension! But I got a request, would you port this extension to firefox?
I've got 0 Javascript and browser extension developing experience, so I think I'll not be able to do this by myself.
I only read that this (in general) shouldn't be to complicated: https://extensionworkshop.com/documentation/develop/porting-a-google-chrome-extension/
Is this also the case for your extension? If true would you be Interested to port this extension to firefox?

Hi @mietzen, thank you for the feedback!
I've been thinking about porting this extension to Firefox for quite some time now. Unfortunately, it's not as simple as publishing the same package to Firefox. There are some minor browser API incompatibilities that I need to address first. I'm planning to find some time in the next couple of weeks and get this done.

Firefox compatibility (which essentially means Manifest Version 2 compatibility) has been merged to main. I have submitted the extension to the add-on marketplace of Firefox and is awaiting a review. Will update this thread, once the extension is reviewed and available for install.

@mietzen The extension has been approved: https://addons.mozilla.org/en-US/firefox/addon/icloud-hide-my-email/


Increase Bunny timeout

By default Bunny has a Timeout of 15 seconds which to me seemed like a very long time but one of the suggestions in this issue was to increase to 30 seconds, which does seem to help a bit but not get rid of them.
I did also try going to the crazy amount of 300 seconds which cleared up nearly all of them, so it could be that we need to find a sweet spot - but those timeout amounts seem so high that it would be a bit weird.

Can you describe the problem this is trying to solve please?

@boffbowsh Sure, we're seeing a lot of Timeout::Error's in Errbit from Bunny since it is now running in Sidekiq (and many many times more often): https://errbit.integration.publishing.service.gov.uk/apps/552637940da1157bfa000399/problems/57b5721a6578634ed04c0000

I don't think this will actually help at this point since I'm seeing the failures occur much earlier than this timeout value
{"@timestamp":"2016-08-18T09:59:51Z","@fields":{"pid":18686,"tid":"TID-ou06mtbp8","context":" DownstreamLiveWorker JID-f5be20638969a3235fb2f8e5","program_name":null,"worker":"DownstreamLiveWorker"},"@type":"sidekiq","@status":"fail","@severity":"INFO","@run_time":0.11,"@message":"fail: 0.11 sec"}
{"@timestamp":"2016-08-18T09:59:52Z","@fields":{"pid":18686,"tid":"TID-ou09v9dfo","context":" DownstreamLiveWorker JID-95da4812e2d5d16e9cae2c43","program_name":null,"worker":"DownstreamLiveWorker"},"@type":"sidekiq","@status":"fail","@severity":"INFO","@run_time":0.088,"@message":"fail: 0.088 sec"}
{"@timestamp":"2016-08-18T10:00:10Z","@fields":{"pid":18686,"tid":"TID-ou067t9bo","context":" DownstreamLiveWorker JID-5de9dbc60a8eedf8698f7572","program_name":null,"worker":"DownstreamLiveWorker"},"@type":"sidekiq","@status":"fail","@severity":"INFO","@run_time":0.23,"@message":"fail: 0.23 sec"}
{"@timestamp":"2016-08-18T10:00:27Z","@fields":{"pid":18686,"tid":"TID-ou09uk8rw","context":" DownstreamLiveWorker JID-fd2df8f98b764aa9cf31d835","program_name":null,"worker":"DownstreamLiveWorker"},"@type":"sidekiq","@status":"fail","@severity":"INFO","@run_time":0.093,"@message":"fail: 0.093 sec"}
{"@timestamp":"2016-08-18T10:00:48Z","@fields":{"pid":18686,"tid":"TID-ou03k7pbk","context":" DownstreamLiveWorker JID-237448a58e25bbeafcb927dc","program_name":null,"worker":"DownstreamLiveWorker"},"@type":"sidekiq","@status":"fail","@severity":"INFO","@run_time":0.079,"@message":"fail: 0.079 sec"}
{"@timestamp":"2016-08-18T10:14:33Z","@fields":{"pid":18686,"tid":"TID-ou0656nb0","context":" DownstreamLiveWorker JID-e3cf611cb0b21db2efc1af76","program_name":null,"worker":"DownstreamLiveWorker"},"@type":"sidekiq","@status":"fail","@severity":"INFO","@run_time":0.063,"@message":"fail: 0.063 sec"}

So I'm going to close this for now.


[google_maps_flutter] Marker is flickering when marker update and rebuild.

Steps to reproduce
When update the marker List and rebuild, the target marker will flicker. Not every times but easy to reproduce.
Only happened on Android. iOS is good.
Device: Android 14 API 34(whatever simulator or real device)
try this with the minimal code sample.

tap the marker  =>  change target marker to yellow
tap the map  =>  change yellow marker back to red

it works good before I upgrade SDK version
Before:

flutter 3.7.12
google_maps_flutter  2.2.6

After:

flutter 3.19.6
google_maps_flutter  2.6.1

Anything helpful? Thanks to everyone.
Minimal Code sample
main.dart
import 'dart:async';

import 'package:flutter/material.dart';
import 'package:flutter_riverpod/flutter_riverpod.dart';
import 'package:google_maps_flutter/google_maps_flutter.dart';

void main() {
  runApp(const ProviderScope(
    child: MyApp(),
  ));
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'GOOGLE MAP FLASH',
      theme: ThemeData(
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
        useMaterial3: true,
      ),
      home: const MyHomePage(title: 'Google Map Flash'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key, required this.title});

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        backgroundColor: Theme.of(context).colorScheme.inversePrimary,
        title: Text(widget.title),
      ),
      body: const Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[Expanded(child: MapWidget())],
        ),
      ),
    );
  }
}

class MapWidget extends ConsumerStatefulWidget {
  const MapWidget({super.key});

  @override
  ConsumerState<ConsumerStatefulWidget> createState() => _MapWidgetState();
}

class _MapWidgetState extends ConsumerState<MapWidget> {
  final Completer<GoogleMapController> _mapController = Completer<GoogleMapController>();
  late final GoogleMapController controller;
  static const defaultZoom = 16.0;
  late List<Marker> markersList = ref.read(markersProvider);
  late int lastRebuildTime;

  @override
  void initState() {
    super.initState();
    WidgetsBinding.instance.addPostFrameCallback((_) async {
      // refresh icon after get markersList from backend
      ref.read(markersProvider.notifier).setState(getMarker());
      controller = await _mapController.future;
    });
  }

  /// a mock of api which returns a list of position
  List<LatLng> getlocation = [
    const LatLng(35.5594, 139.7210),
    const LatLng(35.5604, 139.7210),
    const LatLng(35.5614, 139.7210),
    const LatLng(35.5624, 139.7210),
    const LatLng(35.5634, 139.7210),
    const LatLng(35.5644, 139.7210),
    const LatLng(35.5654, 139.7210),
    const LatLng(35.5664, 139.7210),
    const LatLng(35.5674, 139.7210),
  ];

  getMarker() {
    List<Marker> markerList = [];
    for (var i = 0; i < getlocation.length; i++) {
      var marker = Marker(
        markerId: MarkerId('$i'),
        position: LatLng(getlocation[i].latitude, getlocation[i].longitude),
        icon: BitmapDescriptor.defaultMarker,
        consumeTapEvents: true,
        onTap: () {
          ref.read(nowIndexProvider.notifier).state = i;
        },
        zIndex: 0,
      );
      markerList.add(marker);
    }
    return markerList;
  }

  @override
  Widget build(BuildContext context) {
    lastRebuildTime = DateTime.now().millisecondsSinceEpoch;

    ref.listen(markersProvider, (oldMarker, newMarker) async {
      int rebuildTimeDiff = DateTime.now().millisecondsSinceEpoch - lastRebuildTime;
      if (rebuildTimeDiff < 200) {
        await Future.delayed(Duration(milliseconds: 200 - rebuildTimeDiff));
      }
      setState(() {
        // refresh marker when markersList update
        markersList = newMarker;
      });
    });

    ref.listen(nowIndexProvider, (oldIndex, nowIndex) async {
      if (nowIndex != -1) {
        CameraPosition cameraPos = CameraPosition(target: getlocation[nowIndex], zoom: defaultZoom);
        controller.animateCamera(CameraUpdate.newCameraPosition(cameraPos));
      }

      if (nowIndex == -1) {
        // set all marker to default color
        ref.read(markersProvider.notifier).changeMarker(oldIndex!, BitmapDescriptor.defaultMarker, 0);
      } else if (oldIndex != -1 && oldIndex! < getlocation.length) {
        // change the target marker to special color
        ref.read(markersProvider.notifier).changeMarker(oldIndex, BitmapDescriptor.defaultMarker, 0);
        ref.read(markersProvider.notifier).changeMarker(nowIndex, BitmapDescriptor.defaultMarkerWithHue(60), 1.0);
      } else {
        // change the target marker to special color
        ref.read(markersProvider.notifier).changeMarker(nowIndex, BitmapDescriptor.defaultMarkerWithHue(60), 1.0);
      }
    });

    return GoogleMap(
      mapType: MapType.normal,
      initialCameraPosition: const CameraPosition(target: LatLng(35.5594, 139.7210), zoom: defaultZoom),
      markers: Set.of(markersList),
      onMapCreated: (GoogleMapController controller) {
        if (!_mapController.isCompleted) {
          _mapController.complete(controller);
        }
      },
      mapToolbarEnabled: false,
      zoomControlsEnabled: false,
      myLocationButtonEnabled: false,
      onTap: (argument) async {
        ref.read(nowIndexProvider.notifier).state = -1;
      },
    );
  }
}

class MarkerList extends StateNotifier<List<Marker>> {
  MarkerList() : super([]);

  List<Marker> changeMarker(int index, BitmapDescriptor bitmap, double zIndex) {
    var item = state[index];
    var marker = Marker(
      markerId: item.markerId,
      position: item.position,
      consumeTapEvents: item.consumeTapEvents,
      icon: bitmap,
      onTap: item.onTap,
      zIndex: zIndex,
    );
    state[index] = marker;
    state = [...state];
    return state;
  }

  void setState(List<Marker> newState) {
    state = newState;
  }
}

final markersProvider = StateNotifierProvider<MarkerList, List<Marker>>((ref) {
  return MarkerList();
});

final nowIndexProvider = StateProvider<int>((ref) {
  return -1;
});

pubspec.yaml
name: google_map_flash
description: "A new Flutter project."
version: 1.0.0+1

environment:
  sdk: '>=3.3.1 <4.0.0'
dependencies:
  flutter:
    sdk: flutter
  google_maps_flutter: ^2.6.1
  flutter_riverpod: ^2.5.1

  cupertino_icons: ^1.0.6

dev_dependencies:
  flutter_test:
    sdk: flutter
  flutter_lints: ^3.0.0
flutter:
  uses-material-design: true

Video
https://github.com/flutter/flutter/assets/32993902/8f94e360-b5ca-4d5e-9f56-090de04fad9e
Logs
D/MIUIInput( 7333): [MotionEvent] ViewRootImpl windowName 'com.example.google_map_flash/com.example.google_map_flash.MainActivity', { action=ACTION_DOWN, id[0]=0, pointerCount=1, eventTime=599817703, downTime=599817703, phoneEventTime=17:30:48.953 } moveCount:0
D/MIUIInput( 7333): [MotionEvent] ViewRootImpl windowName 'com.example.google_map_flash/com.example.google_map_flash.MainActivity', { action=ACTION_UP, id[0]=0, pointerCount=1, eventTime=599817745, downTime=599817703, phoneEventTime=17:30:48.995 } moveCount:0
W/ProxyAndroidLoggerBackend( 7333): Too many Flogger logs received before configuration. Dropping old logs.
6
E/FrameEvents( 7333): updateAcquireFence: Did not find frame.
D/MIUIInput( 7333): [MotionEvent] ViewRootImpl windowName 'com.example.google_map_flash/com.example.google_map_flash.MainActivity', { action=ACTION_DOWN, id[0]=0, pointerCount=1, eventTime=599818469, downTime=599818469, phoneEventTime=17:30:49.720 } moveCount:0
D/MIUIInput( 7333): [MotionEvent] ViewRootImpl windowName 'com.example.google_map_flash/com.example.google_map_flash.MainActivity', { action=ACTION_UP, id[0]=0, pointerCount=1, eventTime=599818553, downTime=599818469, phoneEventTime=17:30:49.803 } moveCount:0
W/ProxyAndroidLoggerBackend( 7333): Too many Flogger logs received before configuration. Dropping old logs.
4
E/FrameEvents( 7333): updateAcquireFence: Did not find frame.
D/MIUIInput( 7333): [MotionEvent] ViewRootImpl windowName 'com.example.google_map_flash/com.example.google_map_flash.MainActivity', { action=ACTION_DOWN, id[0]=0, pointerCount=1, eventTime=599819106, downTime=599819106, phoneEventTime=17:30:50.356 } moveCount:0
D/MIUIInput( 7333): [MotionEvent] ViewRootImpl windowName 'com.example.google_map_flash/com.example.google_map_flash.MainActivity', { action=ACTION_UP, id[0]=0, pointerCount=1, eventTime=599819156, downTime=599819106, phoneEventTime=17:30:50.406 } moveCount:0
W/ProxyAndroidLoggerBackend( 7333): Too many Flogger logs received before configuration. Dropping old logs.
42
E/FrameEvents( 7333): updateAcquireFence: Did not find frame.
D/MIUIInput( 7333): [MotionEvent] ViewRootImpl windowName 'com.example.google_map_flash/com.example.google_map_flash.MainActivity', { action=ACTION_DOWN, id[0]=0, pointerCount=1, eventTime=599819817, downTime=599819817, phoneEventTime=17:30:51.067 } moveCount:0
D/MIUIInput( 7333): [MotionEvent] ViewRootImpl windowName 'com.example.google_map_flash/com.example.google_map_flash.MainActivity', { action=ACTION_UP, id[0]=0, pointerCount=1, eventTime=599819885, downTime=599819817, phoneEventTime=17:30:51.135 } moveCount:0
W/ProxyAndroidLoggerBackend( 7333): Too many Flogger logs received before configuration. Dropping old logs.
4
E/FrameEvents( 7333): updateAcquireFence: Did not find frame.

Flutter Doctor output
[✓] Flutter (Channel stable, 3.19.6, on macOS 14.3.1 23D60 darwin-arm64, locale zh-Hans-CN)
    • Flutter version 3.19.6 on channel stable at /Users/a005103/fvm/versions/3.19.6
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 54e66469a9 (5 days ago), 2024-04-17 13:08:03 -0700
    • Engine revision c4cd48e186
    • Dart version 3.3.4
    • DevTools version 2.31.1

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/a005103/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)
    • All Android licenses accepted.

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

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

[✓] Android Studio (version 2023.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 17.0.7+0-17.0.7b1000.6-10550314)

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

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

[✓] Connected device (5 available)
    • 23127PN0CC (mobile)         • e727544e                             • android-arm64  • Android 14 (API 34)
    • sdk gphone64 arm64 (mobile) • emulator-5554                        • android-arm64  • Android 14 (API 34) (emulator)
    • iPhone 15 (mobile)          • B91C6079-B635-427F-90B6-1E36C2B025CC • ios            • com.apple.CoreSimulator.SimRuntime.iOS-17-4 (simulator)
    • macOS (desktop)             • macos                                • darwin-arm64   • macOS 14.3.1 23D60 darwin-arm64
    • Chrome (web)                • chrome                               • web-javascript • Google Chrome 124.0.6367.61

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

@L4rue
Can you check this issue and see if it resembles your case or not ?
If not, in your case, does it replicate without flutter_riverpod implementation ? If so, please provide us updated code sample without that package code.

Thanks for the update. I tried replicating on Pixel XL api 33 emulator, but wasn't able to see the reported behavior.
Also tried to use your code sample in plugin example (marker_icon.dart) but still didn't get the behavior.
Can you try the same and check at your end ?

Thanks for your trying.
At first, I tried replicating on Pixel XL API 33 emulator same as you and all markers are good like before.
But I found the path or roads of map are black. That was strange. So, I search some about that. At this comment, he mentioned Google’s latest renderer dependency on Google Play and Pixel XL API 33 emulator has no Google Play. I suspect the reported issue is related to this.
Based on the above guess, I tried replicating on Pixel 7 Pro API 33 emulator which has Google Play. In this time, the black roads are gone. But the reported behavior happened again. It's really hard but still could reproduce on emulator.
Look this video.
Video
https://github.com/flutter/flutter/assets/32993902/740f43a2-9995-4427-aaa4-b595d02e295b

On real device, almost evetimes could reproduce the behavior.
Just a guess, maybe the difficulty of reproducing is related to the performance of device？Because of low performance and low frame on emulator. After all, it might only last one or two frame.
Here some information of device what I used.
Emulator
Device: Pixel 7 Pro API 33 / Pixel 7 Pro API 34
Google Play Server version: 24.13.19(190400-626168189)
Google Play Store version: 40.6.31-31 [0] [PR] 626489609

Real Device
Device: Xiaomi 14
OS: Xiaomi Hyper OS <IP_ADDRESS>.UNCCNXM (Base on Android 14)
Google Play Server version: 24.13.19(190408-626168189)
Google Play Store version: 38.4.22-21 [0] [PR] 582466152

Device: Pixel 8
OS: Android 14
Google Play Server version: 24.13.18(190400-623909296)
Google Play Store version: 40.4.32-31 [0] [PR] 621277340

Thanks for the update. I tried on Samsung S10 device and also on PIxel XL emulator running Android 13, but was unable to see the flickering. Does the flickering occur while trying to drag the marker or while zooming in and out ?
https://github.com/flutter/flutter/assets/67046386/d50c0fe8-326b-4659-a67e-40618a79a840

Thanks for the update. I tried on Samsung S10 device and also on PIxel XL emulator running Android 13, but was unable to see the flickering. Does the flickering occur while trying to drag the marker or while zooming in and out ?
Screen_Recording_20240424_111624.mp4

Thanks for your trying. By your video, I think I caused a misunderstanding by not describing my operations in detail.
try this.

Not double click, but single tap the marker (not drag the map or zoom in/out)
=> This will trigger the callback function nowIndexProvider.changeIndex(i);, it will change the taped marker to yellow by notifyListener as my video (camera will move to marker's position by the callback function. It's not a drag event)
Not double click, but single tap the map (not drag the map or zoom in/out)
=> This will trigger the callback function nowIndexProvider.changeIndex(-1);, it will change the taped marker back to red by notifyListener  as my video

Maybe useful

Thanks for the update and patience while we try to figure this out.
I followed the steps you mentioned and clicking on the marker does change the color but I didn't observe the flicker, as shown in below video:
https://github.com/flutter/flutter/assets/67046386/4b87620f-b8f6-4cdf-a7f8-34210cdb3273
I ran on latest stable version and on Pixel XL emulator running Android 13.

Could you click between marker and map, not between marker and marker? In addition, it is easier to reproduce the problem on a real device. My colleagues all reproduced this problem on their mobile phones.
Anyway, thanks for your work.

Thanks for the update. I was able to replicate this by running on S10 device with latest versions.
https://github.com/flutter/flutter/assets/67046386/9709649c-8355-4258-8051-b17a6f410510

 stable, master flutter doctor -v
[!] Flutter (Channel stable, 3.19.6, on macOS 12.2.1 21D62 darwin-x64, locale
    en-GB)
    • Flutter version 3.19.6 on channel stable at
      /Users/dhs/documents/fluttersdk/flutter
    ! Warning: `flutter` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/flutter, which is not inside
      your current Flutter SDK checkout at
      /Users/dhs/documents/fluttersdk/flutter. Consider adding
      /Users/dhs/documents/fluttersdk/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/dhs/documents/fluttersdk/flutter.
      Consider adding /Users/dhs/documents/fluttersdk/flutter/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 54e66469a9 (6 days ago), 2024-04-17 13:08:03 -0700
    • Engine revision c4cd48e186
    • Dart version 3.3.4
    • DevTools version 2.31.1
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

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

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

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

[!] Flutter (Channel master, 3.22.0-14.0.pre.67, on macOS 12.2.1 21D62
    darwin-x64, locale en-GB)
    • Flutter version 3.22.0-14.0.pre.67 on channel master at
      /Users/dhs/documents/fluttersdk/flutter
    ! Warning: `flutter` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/flutter, which is not inside
      your current Flutter SDK checkout at
      /Users/dhs/documents/fluttersdk/flutter. Consider adding
      /Users/dhs/documents/fluttersdk/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/dhs/documents/fluttersdk/flutter.
      Consider adding /Users/dhs/documents/fluttersdk/flutter/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 1a905d508d (20 hours ago), 2024-04-21 06:44:23 -0400
    • Engine revision 75ca2195c9
    • Dart version 3.5.0 (build 3.5.0-83.0.dev)
    • DevTools version 2.35.0-dev.8
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/dhs/Library/Android/sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for
      more details.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13C100
    • CocoaPods version 1.11.2

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

[✓] IntelliJ IDEA Ultimate Edition (version 2021.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 65.1.4
    • Dart plugin version 213.7228

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

[✓] Connected device (3 available)
    • Darshan's iphone (mobile) • 21150b119064aecc249dfcfe05e259197461ce23 • ios
      • iOS 15.3.1 19D52
    • macOS (desktop)           • macos                                    •
      darwin-x64     • macOS 12.2.1 21D62 darwin-x64
    • Chrome (web)              • chrome                                   •
      web-javascript • Google Chrome 109.0.5414.119

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

! Doctor found issues in 1 category.

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

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

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

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

From triage: There are major changes planned for markers. We will re-investigate after https://github.com/flutter/packages/pull/4055 lands.

@jokerttu is currently working on marker improvements. I am not sure if this issue will be addressed as part of that work.

@reidbaker, the PR for custom marker resizing improvements has already been merged. However, I don’t believe it will have any effect on this issue.

Any news on this? It still happens with the latest version, which supposedly includes the marker improvements.
google_maps_flutter: ^2.9.0

It happens on Android only, on iOS everything works as expected. But it is quite noticeable. A release build mitigates very little, but it's still reproducible visibly.
In my case, I'm updating the location of the marker very frequently to simulate smooth movement (live location movement).
P.S: if needed, I can also create a sample to reproduce the issue.


Azure pipeline tags

While running in Azure pipeline nx run-many --all --target=version --parallel=1, outputs the following:
🟢 Nothing changed since last release.

Example in project.json:
"version": {
      "executor": "@jscutlery/semver:version",
      "options": {
        "preset": "conventional",
        "baseBranch": "main",
        "syncVersions": true
      }
    }

Any reason why the latest git tag is not found?

Decided to use changsets as an alternative.


Wrong input when starting

When starting an activity (from off) via home(this plugin) it always starting the false activity/input. It seems like there is a default activity/input which always starts when activating it. When i start a scene with input x it doesnt work.
Thanks :)

Hi, did you configure main activity ?
Also, please note that from home app there is no way to start on an input, it will always start on the default one. You can however do this via shortcut

Hey how do i configure a main activity? :)
So that means there isnt a chance to start in a special input?
Thanks :)

Am 03.06.2020 um 17:17 schrieb Nicolas Dujardin<EMAIL_ADDRESS>
Hi, did you configure main activity ?
Also, please note that from home app there is no way to start on an input, it will always start on the default one. You can however do this via shortcut
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Check readme, option is documented ;)
And like I said, you can through shortcut but not directly through home app (it is a missing feature there that was possible ont in first beta of ios12) .

Ahh okay yes i tried with shortcut on iphone but anyway after a few seconds it changes back to „main input“ 🤷🏾♂. That is the Problem.

Am 03.06.2020 um 17:22 schrieb Nicolas Dujardin<EMAIL_ADDRESS>
Check readme, option is documented ;)
And like I said, you can through shortcut but not directly through home app (it is a missing feature there that was possible ont in first beta of ios12) .
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Can you share config and log in debug mode please ?

Thats the config

Am 03.06.2020 um 17:26 schrieb Nicolas Dujardin<EMAIL_ADDRESS>
Can you share config and log in debug mode please ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

You Missed a copy paste or file attachement

Ohh sorry now ?!

Am 03.06.2020 um 17:34 schrieb Nicolas Dujardin<EMAIL_ADDRESS>
You Missed a copy paste or file attachement
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Now

Hi, I need your logs to investigate on this .


Plans for an openpose model including hand pose data?

Are you guys planning on eventually training an openpose model, including handpose data?
https://github.com/Hzzone/pytorch-openpose#hand-pose-estimation
I feel like if we had the openpose model usable with hand data then stable diffusion will finally be able to consistently reproduce hands/fingers.
I'm assuming the biggest hurdle will be obtaining enough annotated data to produce such a model in the first place though.

No need to train a new pose model, they already exist, such as with mediapipe

Is it possible to use one of those models with controlnet so it can know how to handle detected hands?

I would absolutely love to have a ControlNet trained on Mediapipe's Holistic model, for hands but also for face and expression:
https://google.github.io/mediapipe/solutions/holistic.html

i call dibs on face control :)

hi~我是周曦文~您的邮件我已经收到。

all issues about "Release the openpifpaf model". this is not a duplicate.
https://github.com/lllyasviel/ControlNet/issues/109
https://github.com/lllyasviel/ControlNet/issues/201
https://github.com/lllyasviel/ControlNet/issues/331
https://github.com/lllyasviel/ControlNet/issues/467

hi~我是周曦文~您的邮件我已经收到。

also see #445


cleanup flow of common-adapters

[x] add flow to common-adapters

[x] cleanup of React.Component/React$Component variants in flow files

[x] use Component<void, Props,void> instead of defining props oureselves

[x] sort imports

[x] exports on bottom

👍


feat: update to eye v10.26.2

feat: update to eye v10.26.2

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

npm package (@latest dist-tag)
GitHub release
v16.30.0

Your semantic-release bot :package::rocket:


Minor panel fixes

i think the panel is all done now  😎

thanks mate i appreciate that, be good to see what crazy stuff people can add to this page its been fun doing this i think, gonna try and think of some things to add down the line, its hard to come up with ideas aint it.


Validate transaction fee payer earlier

Problem
Fee payer validation and fee deduction should be done as early as possible in transaction execution to avoid doing unnecessary work for transactions that don't pay fees. (related to SIMD-0082)
Summary of Changes
New tx processor methods:

TransactionBatchProcessor::validate_fees which validates the fee payers for a batch of transactions by calling validate_transaction_fee_payer
TransactionBatchProcessor::validate_transaction_fee_payer which loads the fee payer account, validates it, and deducts fees

validate_fees is now called first inside the load_and_execute_sanitized_transactions function before updating the programs cache
Fixes #

Haven't reviewed yet, but as a high level we check fee payer in both new and old scheduler impls early on

Haven't reviewed yet, but as a high level we check fee payer in both new and old scheduler impls early on

Yup, great point. I reworked the description to mention that and describe that the scheduler helps in this regard but is not a complete solution. Another big motivation for this refactoring is to do fee payer validation separately so that it's clear in the code that even if a transaction fails for another reason before execution, we can still definitely charge fees.

rebased to fix conflicts


You need to create a swarm-scoped network before the stack is deployed

After building and running deploy, I'm getting this error.
Error:
network "traefik-public" is declared as external, but could not be found. You need to create a swarm-scoped network before the stack is deployed

docker network ls
2e1b7e59a2e3        fast-api-test-proj_default          bridge              local
ce37fdaa9fcd        fast-api-test-proj_traefik-public   bridge              local

I assume this network name should be traefik-public and not prefixed with the project name, that was created automatically during some step?
Do I have to manually create the network?
docker network create --driver=overlay traefik-public

What are the proper steps to get a deploy?

I managed to create the stack, created that network, but I'm unable to connect on local machine. It works with docker-compose up but not with the swarm stack.
Running on Windows WSL2, docker for windows with swarm enabled v2.3.2.
DOMAIN=fast-api-test-proj.com TRAEFIK_TAG=fast-api-test-proj.com STACK_NAME=fast-api-test-proj-com TAG=prod bash ./scripts/deploy.sh

I tried
DOMAIN=localhost TRAEFIK_TAG=fast-api-test-proj.com STACK_NAME=fast-api-test-proj-com TAG=prod bash ./scripts/deploy.sh

http://localhost:8090/

I had the same error and it was because there was not network named traefik-public running yet. Take a look at this and the first half of the explanation to Traefik here: https://dockerswarm.rocks/ It should get you up to speed.

run the following command
network create -d overlay traefik-public

Please use the right comand:
docker network create -d overlay your-network-name


Bad output

from transformers import AutoTokenizer, AutoModelForCausalLM
Load the model without moving it to 'cuda' initially
quantized_model = AutoModelForCausalLM.from_pretrained(
"ISTA-DASLab/Meta-Llama-3-70B-AQLM-PV-1Bit-1x16",
torch_dtype="auto",
device_map="auto",
low_cpu_mem_usage=True,
)
tokenizer = AutoTokenizer.from_pretrained("ISTA-DASLab/Meta-Llama-3-70B-AQLM-PV-1Bit-1x16")
import time
start = time.perf_counter()
Ensure input_ids are on the correct device when passed to generate
input_ids = tokenizer("I'm AQLM, ", return_tensors="pt")["input_ids"].to(quantized_model.device) #changed
output = quantized_model.generate(input_ids, min_new_tokens=128, max_new_tokens=128)
end = time.perf_counter()
print(f"Generating at {128 / (end - start):.1f} tok/s")
print(tokenizer.decode(output[0]))
Loading checkpoint shards: 100%
 3/3 [01:05<00:00, 21.21s/it]
The attention mask and the pad token id were not set. As a consequence, you may observe unexpected behavior. Please pass your input's attention_mask to obtain reliable results.
Setting pad_token_id to eos_token_id:128001 for open-end generation.
Generating at 3.4 tok/s
I'm AQLM,  meta sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping sourceMapping cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad cad ca

https://huggingface.co/sdyy/bb/tree/main

What is the solution?

from transformers import AutoTokenizer, AutoModelForCausalLM
quantized_model = AutoModelForCausalLM.from_pretrained(
"ISTA-DASLab/Llama-2-70b-AQLM-2Bit-2x8-hf",
torch_dtype="auto", device_map="auto", low_cpu_mem_usage=True,
)
tokenizer = AutoTokenizer.from_pretrained("ISTA-DASLab/Llama-2-70b-AQLM-2Bit-2x8-hf")
import time
start = time.perf_counter()
output = quantized_model.generate(tokenizer("Hey how are you doing today?", return_tensors="pt")["input_ids"].cuda(), min_new_tokens=30, max_new_tokens=30)
end = time.perf_counter()
print(f"Generating at {128 / (end - start):.1f} tok/s")
print(tokenizer.decode(output[0]))
The attention mask and the pad token id were not set. As a consequence, you may observe unexpected behavior. Please pass your input's attention_mask to obtain reliable results.
Setting pad_token_id to eos_token_id:2 for open-end generation.
The attention mask is not set and cannot be inferred from input because pad token is same as eos token. As a consequence, you may observe unexpected behavior. Please pass your input's attention_mask to obtain reliable results.
/usr/local/lib/python3.10/dist-packages/torch/utils/cpp_extension.py:1965: UserWarning: TORCH_CUDA_ARCH_LIST is not set, all archs for visible cards are included for compilation.
If this is not desired, please set os.environ['TORCH_CUDA_ARCH_LIST'].
warnings.warn(
/usr/local/lib/python3.10/dist-packages/aqlm/inference_kernels/cuda_kernel.py:20: FutureWarning: torch.library.impl_abstract was renamed to torch.library.register_fake. Please use that instead; we will remove torch.library.impl_abstract in a future version of PyTorch.
@torch.library.impl_abstract("aqlm::code1x16_matmat")
/usr/local/lib/python3.10/dist-packages/aqlm/inference_kernels/cuda_kernel.py:33: FutureWarning: torch.library.impl_abstract was renamed to torch.library.register_fake. Please use that instead; we will remove torch.library.impl_abstract in a future version of PyTorch.
@torch.library.impl_abstract("aqlm::code1x16_matmat_dequant")
/usr/local/lib/python3.10/dist-packages/aqlm/inference_kernels/cuda_kernel.py:48: FutureWarning: torch.library.impl_abstract was renamed to torch.library.register_fake. Please use that instead; we will remove torch.library.impl_abstract in a future version of PyTorch.
@torch.library.impl_abstract("aqlm::code1x16_matmat_dequant_transposed")
/usr/local/lib/python3.10/dist-packages/aqlm/inference_kernels/cuda_kernel.py:62: FutureWarning: torch.library.impl_abstract was renamed to torch.library.register_fake. Please use that instead; we will remove torch.library.impl_abstract in a future version of PyTorch.
@torch.library.impl_abstract("aqlm::code2x8_matmat")
/usr/local/lib/python3.10/dist-packages/aqlm/inference_kernels/cuda_kernel.py:75: FutureWarning: torch.library.impl_abstract was renamed to torch.library.register_fake. Please use that instead; we will remove torch.library.impl_abstract in a future version of PyTorch.
@torch.library.impl_abstract("aqlm::code2x8_matmat_dequant")
/usr/local/lib/python3.10/dist-packages/aqlm/inference_kernels/cuda_kernel.py:88: FutureWarning: torch.library.impl_abstract was renamed to torch.library.register_fake. Please use that instead; we will remove torch.library.impl_abstract in a future version of PyTorch.
@torch.library.impl_abstract("aqlm::code2x8_matmat_dequant_transposed")
RuntimeError                              Traceback (most recent call last)
 in <cell line: 2>()
1 start = time.perf_counter()
----> 2 output = quantized_model.generate(tokenizer("Hey how are you doing today?", return_tensors="pt")["input_ids"].cuda(), min_new_tokens=30, max_new_tokens=30)
3 end = time.perf_counter()
24 frames
/usr/local/lib/python3.10/dist-packages/torch/_ops.py in call(self_, *args, **kwargs)
1059         if self_._has_torchbind_op_overload and must_dispatch_in_python(args, kwargs):
1060             return call_overload_packet_from_python(self, args, kwargs)
-> 1061         return self._op(*args, **(kwargs or {}))
1062
1063     # TODO: use this to make a dir
RuntimeError: CUDA error: invalid argument
CUDA kernel errors might be asynchronously reported at some other API call, so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1
Compile with TORCH_USE_CUDA_DSA to enable device-side assertions.


⚠ Fetchers has degraded performance

In 570e47e, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 473 ms

Resolved: Fetchers performance has improved in 3301c15.


WP Permalinks

Install worked a treat, wordpress runs superbly in folder www/nginxshopp/
Running on Win 10
That is the wordpress folder is named nginxshopp and runs as it should with default permalinks
I switch to Pretty Permalinks (Post Name in this case) and 404's result.
I have tried adding
location /nginxshopp/ {
try_files $uri $uri/ /nginxshopp/index.php?$args;
}
and
location /nginxshopp {
index index.php;
if (!-e $request_filename) { rewrite ^(.+)$ nginxshopp/index.php?q=$1 last;
}
to the nginx.conf file, all to no avail.
With the former I get an index of the pages
Rather than attempt a full reinstall as per your answer here https://github.com/WPN-XM/WPN-XM/issues/393
Is there a solution that does not involve nginxshopp.dev?

Hey!

Is there a solution that does not involve nginxshopp.dev?

Yes, there is. I think, you are already on the right track.
You would add an additional location section to the main server block in nginx.conf.
That's the one, which serves localhost.
Your first location block looks ok to me! It should enable short URLs for Wordpress, like http://localhost/wordpress/2016/02/hello-world/:
location /wordpress {
    try_files $uri $uri/ /wordpress/index.php?$args;
}

With the former I get an index of the pages

Ah..wait..... you get the listing only, when there is no index.php.
Wordpress has an index.php.
I assume, that you installed "shopp" into the folder /www/nginxshopp, right?
When the application is not a standalone application, but a plugin for Wordpress,
you would need to drop it into the wordpress plugin folder.
C:\server\www\wordpress\wp-content\plugins\shopp.
Please move the files there, then check in the WP backend, if it's possible to activate the plugin.
That also means that plugin doesn't have it's own rewrite rule configuration,
because the one from Wordpress applies.
You can rename the "wordpress" folder to "wp-shopp" and adjust the location accordingly,
to get another URL, e.g. http://localhost/wp-shopp.
Is this ok?
Best, Jens

Hmm, when i activate the plugin i get an installation error...
Fatal error: Uncaught Error: Call to undefined function mysql_error() in C:\server\www\wordpress\wp-content\plugins\shopp\core\flow\Install.php on line 219
( ! ) Error: Call to undefined function mysql_error() in C:\server\www\wordpress\wp-content\plugins\shopp\core\flow\Install.php on line 219

That's because mysql_error is deprecated since PHP5.5.0 and i'm running PHP7.
The requirements for Shopp are not correct: ""5.2 or higher", it's "5.2 to 5.4".
Need to install a 5.4 and will test the installation tomorrow...

Hi Jens,
Thanks for taking a look, I will try these suggestions out in the morning....
In the meantime, I did follow your absolutely perfect instructions for setting up a site using the wordpress.dev solution and have that running on localhost now with pretty permalinks working with no issue
I had no issues installing Shopp on that and it is running now
Incidentally, I also have Shopp running on a site using PHP version 7.0 and I have several sites running Shopp on 5.6
Please do not spend any more of your valuable time on this issue. I will be able to take it from here. Thank you
I did originally try the wpn-xm php 7.0 version but found that I had issues with adminer (and noted it my uninstall reply) and so went down to the 5.6 which is a real treat to work with.
Congratulations on a very fine piece of development

Please do not spend any more of your valuable time on this issue. I will be able to take it from here. Thank you

You are welcome.

I did originally try the wpn-xm php 7.0 version but found that I had issues with adminer (and noted it my uninstall reply) and so went down to the 5.6 which is a real treat to work with.

Yes, i got a few reports about incompatibility. At the time of packaging Adminer had a few issues with 7. It's latest version should run fine.

Congratulations on a very fine piece of development

Glad you like it (, despite the fact that it's still a vZero product with a lot of issues.)


set full date not work.

the code from the documentation returns an error:
code:
_const setFullDateBtn = document.querySelector('#setFullDateBtn');
const datepicker = MCDatepicker.create({
el: '#example'
});
setFullDateBtn.onclick = () => {
datepicker.setFullDate(new Date(2021, 1, 1));
};_
return error:
Uncaught TypeError: Cannot read properties of undefined (reading 'setFullDate')
at setFullDateBtn.onclick

Hi there!
Make sure you have imported the resources correctly.
It says the module is undefined which means it wasn't imported properly.


Cannot use underscore (_) in database name

Im using AlaSQL v0.3.2. Consider:
alasql("CREATE localStorage DATABASE IF NOT EXISTS "+dbName);
alasql("ATTACH localStorage DATABASE "+dbName);

If dbName contains an underscore (_), the second statement fails with this message in console:
TypeError: LS.get(...) is null
db.tables = LS.get(lsdbid).tables;

The error is in function LS.attachDatabase, in line 16714.

Thank you for a very well described bug!

Seems the problem is not related to underscore, but it occurs when the lines in webappstore.sqlite containing my database is removed. But the real problem seems to be that LS.get(lsdbid) returns null, and so LS.get(lsdbid).tables fails. A check for null (or a try/catch) should fixc the probem, I guess?

Hmm. So you remove the file while its attatched?

Not exactly. Im creating a backup/restore function for my program. I removed the lines representing my database from the webappstore2 table (using the SQLiteManager plugin for Firefox) in order to see how my program would react if no database was found. That's when I get the error message I reported.
This might be an obscure bug, and I can easily get around it by using a try/catch. Anyway, the offending line 16714 should be fixed, I think.

Trying to understand here: LS.get(lsdbid) retuning null beacuse you removed details from the .sqlite file?
To use SQLite files you need to use ATTACH SQLITE DATABASE - but your example is having ATTACH localStorage DATABASE
Have a look at https://github.com/agershun/alasql/wiki/SQLite and let me know if this helps you.

retuning null beacuse you removed details from the .sqlite file?
So it would seem.

To use SQLite files you need to use ATTACH SQLITE DATABASE - but your example is having ATTACH localStorage DATABASE
With my code (ATTACH localStorage DATABASE), the data actually goes into the webappstore2 table in Firefox's webappstore.sqlite file...

With my code (ATTACH localStorage DATABASE), the data actually goes into the webappstore2 table in Firefox's webappstore.sqlite file...

Ahhhh, I get what you are saying

I changed the name of the issue to reflect the real problem.
BTW, thanks for a great plugin! :)  :+1:


add support for setting all reviewers as assignees

This PR adds support for setting multiple assignees. It sets all reviewers to be assignees using the assignees parameter GitHub API docs.
closes #139
@vjeux I could not find any existing tests for setting the first reviewer as an assignee. Should I also add a test for this?
(I signed the CLA a couple of minutes ago before submitting the PR. Maybe It takes another minute to be registered)

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at<EMAIL_ADDRESS>Thanks!

Nice, so easy!
Feel free to add a test if you want, but I'd be happy to take it in as is.
Could you sign the CLA and I'll pull it in, thanks!

Yup, I can see you have signed the CLA, thanks!


Added Dutch translations

Dutch translation for the explorer.
I haven't looked into adding a way to switch languages yet. Will that be the done the same way as on ark.io (so with the flag > showing a list of available languages on hover)?

We haven't added any translation selection to the explorer yet as it wasn't a major point on the to do for release.

I understand, but I was wondering whether you guys already had something in mind on how it should be added (for example in the same style as on ark.io)?

I will be adding that soon.


UART Communications on OrangePi Zero Pins

Hello,
I am having trouble connecting a UART device to the OrangePi Zero from the onboard pins. When physically connected, the /dev/ttyS1 does not present itself to the kernel and it does not show that a device is connected. It appears that these ports are not enabled. Any help on this would be great!
Thank you

@Andrew-Wallace thank you for letting us know, we'll look into this with high priority and get back to you as soon as possible

Hi @Andrew-Wallace ,
Currently I don't have an Orange Pi Zero to test on, as the Orange PI Zero is currently community supported.
However, I have an Orange Pi Lite v1 that I used for the purpose of this test. Please see below how I enabled uarts 1 and 2 on it. The procedure should be the pretty much the same on the Zero.
I've also released BalenaOS 2.45.1+rev1 for the Orange Pi Zero in the staging dashboard. Please try with this latest release, since the old one doesn't have support for overlayfs, nor does it contain the dtbos for enabling additional uarts.
Load the overlays:
root@010706e:~# mkdir -p /sys/kernel/config/device-tree/overlays/ttys1
root@010706e:~# cat /mnt/boot/dtb/overlay/sun8i-h3-uart1.dtbo > /sys/kernel/config/device-tree/overlays/ttys1/dtbo
root@010706e:~# mkdir -p /sys/kernel/config/device-tree/overlays/ttys2
root@010706e:~# cat /mnt/boot/dtb/overlay/sun8i-h3-uart2.dtbo > /sys/kernel/config/device-tree/overlays/ttys2/dtbo

Check dmesg to see the devices:
root@010706e:~# dmesg | grep tty
[   70.203647] 1c28400.serial: ttyS1 at MMIO 0x1c28400 (irq = 145, base_baud = 1500000) is a U6_16550A
[   81.883428] 1c28800.serial: ttyS2 at MMIO 0x1c28800 (irq = 146, base_baud = 1500000) is a U6_16550A

Switch baudrate to test with PC:
root@010706e:~# stty -F /dev/ttyS1 115200
root@010706e:~# stty -F /dev/ttyS2 115200

Connect uart cable from PC to pins to 11 & 13 for uart2
and to 38 & 40 for uart1 and test with minicom:
root@010706e:~# cat /dev/ttyS1
this is a test on uart1

root@010706e:/# cat /dev/ttyS2
this is another test

As I said, the procedure for loading the overlays on the Orange PI Zero should be pretty much the same, only the actual pins
on the header will probably differ, for when you connect your cables.

Hello @acostach,
After trying your solution to my OrangePi zero using the new BalenaOS 2.45.1+rev1, ttyS1 and ttyS2 are now working. Thank you very much for your help!

After working with the serial ports, I noticed that this must be done each time the device is power cycled. Is there a way to automate this so it runs these commands on boot? I tried to run these in a node-red container I have on my device and /sys/kernel/config/device-tree is not presented to the container. What could I do to fix this issue?
Thank you

Hi, are you using a multicontainer app or a single container? If single container, is the container running in privileged mode?

Hello, it is a multicontainer environment, but they are independent of each other. The container using the UART is a node-red container that is running in privileged mode.

Hi @Andrew-Wallace ,
In the hostOS, the path you mention is mounted as a configfs by the sys-kernel-config automount.
Therefore, for the container can you please try mounting it like this:

mount -t configfs none /sys/kernel/config

before loading the dtbo files as usual?

Hello @acostach,
After running the mount command this is as far as I got:
root@173d061f4c1c:/usr/src/node-red# mount -t configfs none /sys/kernel/config root@173d061f4c1c:/usr/src/node-red# mkdir -p /sys/kernel/config/device-tree/overlays/ttys1 root@173d061f4c1c:/usr/src/node-red# cat /mnt/boot/dtb/overlay/sun8i-h3-uart1.dtbo > /sys/kernel/config/device-tree/overlays/ttys1/dtbo cat: /mnt/boot/dtb/overlay/sun8i-h3-uart1.dtbo: No such file or directory
Thank you

Hi @Andrew-Wallace ,
/mnt/boot is a path accessible only from the rootfs, not from container.
Please store the dtbos either in a volume of your application, or add them to your application container directory using COPY in your Dockerfile:
https://github.com/balena-io-projects/multicontainer-getting-started/blob/89ae9a1f756843db93cf0fa02ce7f2c4eb4db6ea/data/Dockerfile.template#L13
https://www.balena.io/docs/learn/develop/multicontainer/#named-volumes


OSSM-6163: Fix v2.5 SMCP Prometheus route errors

This PR fixes the v2.5 SMCP Prometheus access.
I will create another PR about the Grafana query client auth issue later.


Show latest reading events by event date, not event creation date.

Adjusts the selection for homepage reading events to pull the most recent occurrences, not latest created, reading events.

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

v0.54.0
GitHub release

Your semantic-release bot :package::rocket:


Emacs shell incorrectly doesn't get the fancy output

Thanks for creating miette! :)
Steps to Reproduce
Add the example program from the README to src/main.rs:
src/main.rs
/*
You can derive a Diagnostic from any `std::error::Error` type.

`thiserror` is a great way to define them, and plays nicely with `miette`!
*/
use miette::{Diagnostic, SourceSpan};
use thiserror::Error;

#[derive(Error, Debug, Diagnostic)]
#[error("oops!")]
#[diagnostic(
    code(oops::my::bad),
    url(docsrs),
    help("try doing it better next time?"),
)]
struct MyBad {
    // The Source that we're gonna be printing snippets out of.
    // This can be a String if you don't have or care about file names.
    #[source_code]
    src: NamedSource,
    // Snippets and highlights can be included in the diagnostic!
    #[label("This bit here")]
    bad_bit: SourceSpan,
}

/*
Now let's define a function!

Use this Result type (or its expanded version) as the return type
throughout your app (but NOT your libraries! Those should always return concrete
types!).
*/
use miette::{Result, NamedSource};
fn this_fails() -> Result<()> {
    // You can use plain strings as a `Source`, or anything that implements
    // the one-method `Source` trait.
    let src = "source\n  text\n    here".to_string();

    Err(MyBad {
        src: NamedSource::new("bad_file.rs", src),
        bad_bit: (9, 4).into(),
    })?;

    Ok(())
}

/*
Now to get everything printed nicely, just return a Result<()>
and you're all set!

Note: You can swap out the default reporter for a custom one using `miette::set_hook()`
*/
fn main() -> Result<()> {
    // kaboom~
    this_fails()?;

    Ok(())
}

And this Cargo.toml:
Cargo.toml
[package]
name = "miette-test-case"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
miette = { version = "3.2.0", features = ["fancy"] }
thiserror = "1.0.30"

Now open Emacs, and then open the Emacs shell via M-x shell.
Finally, run the command cargo run within the Emacs shell.
Expected Results
The fancy output is enabled, and we see the expected source snippets and unicode box drawing characters underlining the source spans and all that.
Basically the same output that you get running cargo run in a regular terminal:

Actual Results
We do not get the fancy output, and seem to get a screen reader compatible output that is hard to read instead:

For what it's worth, this can be added to the top of main as a temporary work around:
        let _ = miette::set_hook(Box::new(|_| {
            Box::new(
                miette::MietteHandlerOpts::new()
                    .force_graphical(true)
                    .build(),
            )
        }));

The code controlling this is over here:
https://github.com/zkat/miette/blob/main/src/handler.rs#L186-L196
and by extension,
https://github.com/zkat/supports-color/blob/main/src/lib.rs
There could also probably be some logic around "well, it doesn't support color, but it does support some level of graphical output", but I made a design decision at some point that "no color" in miette means "screen reader friendly" so you could just use NO_COLOR to make it narratable. That may have been a mistake? I'm happy to change that as long as there's an easy out for screen reader users.

For what its worth, the Emacs shell also supports (at least most?) ansi colors. But it sets TERM=dumb by default, because it doesn't support many of the more advanced control codes for moving the cursor around and clearing output and things like that.

Should I stop punning off NO_COLOR for accessible output?

I'm not sure, unfortunately. I don't have a lot of experience with terminal feature detection.

Emacs will also automatically set the INSIDE_EMACS env var. Perhaps worth special casing that in the handler or in supports-color?


DOC: Unclear command line format in README

Issue:
The Quick Start section for Windows in the README has a command format for installing x64 libraries, which goes like this in the README:
> .\vcpkg\vcpkg install package:x64-windows

The part package:x64-windows might seem a little unclear to people using the tool for the first time as it is not explicit/clear that in this, package is to be substituted with the appropriate package name. The command formats before this one denote this by using square brackets to make the substitution clear:
> .\vcpkg\vcpkg install [packages to install]

Fix:
Adding square brackets around the word package (for uniformity) to clarify the substitution could make things clearer to the reader, for example:
> .\vcpkg\vcpkg install [package name]:x64-windows

Just got this exact issue moments ago.
Tho I have some experience with C and C++ on other platforms I'm pretty new to vcpkg.
I initially though one had to install a package named package:x64-windows to add x64 compilation support for Windows.
This issue saved me quite a bit of time 👍


New command: m365 spe container permission add

Usage
m365 spe container permission add [options]
Description
Adds permission to Container
Options

Option
Description

-i, --containerId <containerId>
Container id

-r, --roles <roles>
Comma separated list of permissions. Possible values are reader, writer, manager, owner.

--upn <upn>
The upn/email of user to assign role to

Examples
Adds a reader role for the specified user to the container
m365 spe container permission add --containerId "b!ISJs1WRro0y0EWgkUYcktDa0mE8zSlFEqFzqRn70Zwp1CEtDEBZgQICPkRbil_5Z"  --roles "reader" --upn<EMAIL_ADDRESS>
Default properties
No response
Additional Info
we may use the following API for that:
https://learn.microsoft.com/en-us/graph/api/filestoragecontainer-post-permissions?view=graph-rest-1.0&tabs=http

One improvement could be adding another example, maybe one with multiple roles. We could also add userId, so they can set permissions using the user Entra ID.

I think upn should also be renamed to userName to be consistent with other commands.

I think upn should also be renamed to userName to be consistent with other commands.

updated ✅

One improvement could be adding another example, maybe one with multiple roles. We could also add userId, so they can set permissions using the user Entra ID.

Added additional example ✅
Improved a bit description ✅
and the description of the container ID ✅
Good call with the userId. added ✅

@pnp/cli-for-microsoft-365-maintainers any other feed or should we open it up?

Made a few small remaining changes. LGTM!


.Net 4.5 projects added for Managed-OSVR

This is in support of non-Unity managed OSVR usage (OSVR-MonoGame et. al.) with .net 4.5 support. Adds an additional ClientKit project with linked files from the .net 2.0 project.
CC issues:
https://github.com/OSVR/OSVR-Unity/issues/3
https://github.com/OSVR/OSVR-Unity/issues/6
I have signed the Apache ICLA 2.0:
http://www.apache.org/licenses/icla.txt

Looks good to me, thanks!


Is it possible to add missing Serbian alphabet?

The Serbian language uses two alphabets and if I want to translate from SR(Cyrillic)->EN I don't have issues.
But in the case of SR(Latin)->EN, Google Translate will automatically change my input from Latin to Cyrillic and then do the translation, which is not the case with this Alfred workflow.
I've found this support google thread where it says they have sr-Latn as language code. Can we add it to the list of languages?

Hi, @Aracki sorry for lated reply, I'm just watching the main repository(alfred-google-translate) and not watching this.
I'm not good at the Serbian language, and cannot check if the sr-Latn works, could you raise a PR for that?

Before the update of alfred-google-translate plugin:
sr-Latn could be set, but it doesn't work.
After the upgrade it works, but it is recognizing my Serbian Latin input as Bosnian or Croatian which is fine because it's basically the same language.

Closes #2


Add unitary tests and CI to the project

Should be good to add unitary tests and set a good coverage as a goal, and configure some continuous integration to this project (TravisCI ?)

Closed by #4


Update 2024_lhc.md

short little shifty wifty

Thank you @wvangoet
Is there an entry for some B2 results? Maybe we should link to the one a bit above the B1 VDM_V4 you linked to? It seems to be around midnight, is it valid as a final B2 result?

Those are indeed the last B2 results, they were done a bit quicker.
I saw Tobias also put a shift summary on a later log.

@fsoubelet You mean: 3983844  ?
Also: will be merged in #130

Also: will be merged in #130


[Llama2] Fix tensor serialization in CI

@tapspatel we need to re-serialize the tensors in CI. Could you rm /opt/cache/llama2_70b_cache/llama-data-cache/weights-cache-2/* ?

#7177 resolved

removed


Release-process Wiki entry, step 8, buckets not betas

Step 8 should refer to "bucketN" milestones, not "betaN": https://github.com/flutter/flutter/wiki/Release-process#rolling-the-beta-channel

I haven't found any mention of bucketN or betaN.
Perhaps this was replaced by
Move all the open bugs in the current milestone to the Overdue milestone.

I assume this issue is stale.


Automatic error report

<!---   *** BEFORE SUBMITTING: PASTE CLIPBOARD HERE TO COMPLETE YOUR REPORT ***   ---!>
![image](https://user-images.githubusercontent.com/28038669/54569172-cff12700-4a14-11e9-9ea9-251ff16dcb51.png)

Please update Spyder to its latest version (3.3.3) and try again. I think we fixed this problem already.

Closing due to lack of response.

Please update Spyder to its latest version (3.3.3) and try again. I think we fixed this problem already.

3.3.3 works well! Thanks for your effort! 牛逼


LXC - Error: a number is required

Heya,
Experiencing an issue with LXCs on v2.9.7:
Error: a number is required
│
│   with module.proxmox_lxc["****"].proxmox_lxc.proxmox_lxc,
│   on .terraform\modules\proxmox_lxc\modules\proxmox\proxmox_lxc\main.tf line 34, in resource "proxmox_lxc" "proxmox_lxc":
│   34:       mtu    = 1500
│
Same error with/without the MTU attribute specified
Thanks!

Yeah also seeing this.

│ Error: a number is required
│
│   with proxmox_lxc.work-docker,
│   on work-docker.tf line 22, in resource "proxmox_lxc" "work-docker":
│   22:   network {

Duplicate of https://github.com/Telmate/terraform-provider-proxmox/issues/502 I don't get it are we meant to specify an MTU value?

you have inconsistent state file from older version where mtu was a string, either edit the state file or start from scratch with latest version and a clean state file


Update CONTRIBUTING.md file

What is the feature request? What problem does it solve?
Research if the contributing.md file can be improved. As we have the first contributors, it could be good to revise if there can be made any further improvements to the file to explain the process better.
Suggested solution

Revise the file
Propose the changes if necessary (can be a branch and a PR)
Agree with the team and merge the changes.

Triaged. Closed as being already resolved(as part of: https://github.com/vmware/versatile-data-kit/pull/1741 ).


Add configuration and functional option to scroll a stack without skipping images

I wanted a way to consume scroll events and prevent the stack state from progressing to the next index until the currently request index had been drawn. I think this covers that.

Coverage decreased (-0.03%) to 3.98% when pulling 735e0ca66add84fee81b286bc1246b7880ab8354 on jdnarvaez:jdnarvaez/scrollWithoutSkipping into 29182180ed3f850ba41c609b98b96464affca5f0 on cornerstonejs:master.

Thanks for the contribution! I'll try to get to this ASAP, but it will likely be after the holidays.

Trying to make sure I understand. In your new implementation, you bypass the scrollToIndex and instead:

Record the "pending" image change
Call scrollWithoutSkipping

Where we:

Verify the "pending" final scroll image is not already being displayed
Register a cornerstonenewimage event listener that

When the next image rendered matches the next "pending image"

We pop of the pending image event (it's no longer pending :P)
Remove the listener
Call scrollWithoutSkipping if we have more pending items

^ Now that something is listening, we call scrollToIndex

I think this would force stackScroll requests to process in order, So if the stack scroll calls are:

display image 1
display image 2
display image 3
etc.

Then they should all display in order without skipping.
Note: I've also added some comments to your code with additional questions.
Follow-up question for @swederik, does scrollToIndex uhh.. Scroll? It looks like it queues up and loads whatever newImageId you give it?

Correct. As far as I can tell scrollToIndex just queues the image call, which may or may not execute in order depending on how long the loadImage request takes.


Fix typo syncronization -> synchronization

Fix typo

Summary

Changelog
[General][Fixed] - Fixed typo syncronization -> synchronization

Test Plan

Hi @pruthvip! Could you please log in into app.circleci.com?
I can see that the CircleCI pipeline is not running on this PR due to a missing OAuth token between CircleCI and GitHub


Import/Export tools

I have a database of products that I will need to import and re-import on a regular basis.
If a product is out of stock or no longer sold by our supplier I need to "sync" with our database.
I have been planning to write a script that would take care of that.
So my question is: Are there any tools or simplified API to do these tasks?
I have been unable to find any info in the docs.
Disclaimer: I know very little of Django and its database models.

We're going to add some features to support data import/export in Saleor (see the roadmap). Specific issues will be added in the future, once we start working on those features.

Did this move ahead at all since the issue being closed? I'd also like to import a bunch of products and would like to avoid learning a new language to do it...

We have an issue for CSV import/export (#5174) and an open PR for CSV export of products. Once the export feature is done, we want to start working on import as a separate PR, but it's hard to give some dates when it'll be ready. Anyway this is one of our priorities for the next release of Saleor.


Possibly unbounded recursion in QueueHandler could lead to stack overflow

In https://github.com/vapor/core/blob/92cef8935fbeb16516b3c687ca3039fa5ce60860/Sources/Async/QueueHandler.swift#L73, writeOutputIfEnqueued calls itself. Unless the compiler can optimize this away as a tail recursion, it could lead to stack overflows if there are very many elements in outputQueue. (Still unlikely, but not sure if it's worth taking any risks with that.)

@MrMage any recommends for how to fix?

I think it should be easy to replicate the same behavior with a while loop.


add 5-byte large disk builds for arm and arm64

I have Odroid HC2s with 12TB drives in them, so running the 5-byte build of SeaweedFS seemed correct.

Do you also want to add it to the release?


unittest case for rayfile with flux_type==1

flux_type_1.zip
Still working on how to add it to Unittest


#46 : Allow for the option to not listen on all interfaces

Fixes #46

Thanks for bringing up this issue. I've added support for registering, browsing and resolving services at specific network interfaces by allow a comma-separated list of network interface in the -Interface option.
The following example registers the service hello world._http._tcp._local at port 8080 on the network interfaces eth0 and wlan0.
dnssd register -Name "hello world" -Type _http._tcp -Port 8080 -Interface=eth0,wlan0


Change case statements to match updated phoenix generators

duplicate of stale PR https://github.com/ueberauth/guardian/pull/615
@Hanspagh could you please review this again so I can close this and my old PR?

@Hanspagh / @panbenson in the future if we have a PR blocked because of another team member's stale review we can dismiss it :+1: @Hanspagh you should have permissions to do so or you can ping me to take a peek.
Sorry about the last PR getting caught up in limbo @panbenson, we appreciate your interest in getting involved with the project :grin:


HBASE-26814 Addendum: Fix spotbugs warning and clarify intent

See discussion in https://issues.apache.org/jira/browse/HBASE-26814

I can't seem to get spotbugs to run locally in a useful way to verify this fix. I've tried various different permutations of mvn spotbugs:spotbugs, spotbugs:check, etc. We'll see what precommit check shows, but it didn't catch the original. If someone has a one-liner I can run I'd be happy to give it a shot

You can look in the BlueOcean output of the General Checks to find it. The incantation looks like
[](https://ci-hbase.apache.org/blue/organizations/jenkins/HBase-PreCommit-GitHub-PR/detail/PR-4196/1/#step-87-log-1105)[](https://ci-hbase.apache.org/blue/organizations/jenkins/HBase-PreCommit-GitHub-PR/detail/PR-4196/1/#step-87-log-1106)[](https://ci-hbase.apache.org/blue/organizations/jenkins/HBase-PreCommit-GitHub-PR/detail/PR-4196/1/#step-87-log-1107)[](https://ci-hbase.apache.org/blue/organizations/jenkins/HBase-PreCommit-GitHub-PR/detail/PR-4196/1/#step-87-log-1108)[](https://ci-hbase.apache.org/blue/organizations/jenkins/HBase-PreCommit-GitHub-PR/detail/PR-4196/1/#step-87-log-1109)[](https://ci-hbase.apache.org/blue/organizations/jenkins/HBase-PreCommit-GitHub-PR/detail/PR-4196/1/#step-87-log-1110)[](https://ci-hbase.apache.org/blue/organizations/jenkins/HBase-PreCommit-GitHub-PR/detail/PR-4196/1/#step-87-log-1111)[](https://ci-hbase.apache.org/blue/organizations/jenkins/HBase-PreCommit-GitHub-PR/detail/PR-4196/1/#step-87-log-1112)[](https://ci-hbase.apache.org/blue/organizations/jenkins/HBase-PreCommit-GitHub-PR/detail/PR-4196/1/#step-87-log-1113)[2022-03-10T13:54:26.637Z] ============================================================================
[2022-03-10T13:54:26.637Z] ============================================================================
[2022-03-10T13:54:26.637Z]                       spotbugs detection: branch-2.5
[2022-03-10T13:54:26.637Z] ============================================================================
[2022-03-10T13:54:26.637Z] ============================================================================
[2022-03-10T13:54:26.637Z]
[2022-03-10T13:54:26.637Z]
[2022-03-10T13:54:26.637Z] [Thu Mar 10 13:54:19 UTC 2022 INFO]: Personality: branch spotbugs
[2022-03-10T13:54:26.637Z] cd /home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-4196/yetus-general-check/src/hbase-server
[2022-03-10T13:54:26.637Z] /opt/maven/bin/mvn --batch-mode -Dmaven.repo.local=/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-4196/yetus-m2/hbase-branch-2.5-patch-1 --threads=2 -DHBasePatchProcess test-compile spotbugs:spotbugs -DskipTests=true > /home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-4196/yetus-general-check/output/branch-spotbugs-hbase-server.txt 2>&1

When we cherry pick obviously spotbugs doesn't run. I do run unit tests locally, but this will vary by individual. It is interesting that the settings might be different per branch.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

-1 :x:
patch
0m  4s
https://github.com/apache/hbase/pull/4201 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/4201

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4201/1/console

versions
git=2.25.1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  7s
Docker mode activated.

-1 :x:
patch
0m  3s
https://github.com/apache/hbase/pull/4201 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4201/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4201

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4201/1/console

versions
git=2.17.1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

-1 :x:
patch
0m  3s
https://github.com/apache/hbase/pull/4201 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/4201

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4201/1/console

versions
git=2.25.1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Templatizer: repeated templatize() doesn't forward root properties when _forwardParentProp is set.

Description
When calling templatize() on the same template again, and _forwardParentProp is present, parent properties aren't forwarded.
Live Demo
http://codepen.io/hanger/pen/KrmrJA?editors=1010
Observed Results
In the live demo code:
Polymer({
  is: 'x-el',
  behaviors: [Polymer.Templatizer],
  _forwardParentProp() {},
  ready() {
    const tplA = this.querySelector('template.a');
    for(let i = 0 ; i < 3 ; i++) {
      this.templatize(tplA);
      this.appendChild(this.stamp({nameA: i}).root);
    }
  },
});

shows the wrong output

0 a: fromRoot
1 a:
2 a:

But
Polymer({
  is: 'x-el',
  behaviors: [Polymer.Templatizer],
  _forwardParentProp() {},
  ready() {
    const tplA = this.querySelector('template.a');
    this.templatize(tplA); // outside loop
    for(let i = 0 ; i < 3 ; i++) {
      this.appendChild(this.stamp({nameA: i}).root);
    }
  },
});

and
Polymer({
  is: 'x-el',
  behaviors: [Polymer.Templatizer],
  // no _forwardParentProp
  ready() {
    const tplA = this.querySelector('template.a');
    for(let i = 0 ; i < 3 ; i++) {
      this.templatize(tplA);
      this.appendChild(this.stamp({nameA: i}).root);
    }
  },
});

show the correct output

0 a: fromRoot
1 a: fromRoot
2 a: fromRoot

Expected Results
In all three cases, the parent binding should be forwarded, not only when calling templatize() for the first time. The method specifically deals with the case where it's called repeatedly, so it seems this is supported.
We call templatize() multiple times because we want to use multiple templates. Unfortunately stamp() doesn't accept the template to use as an argument.
What does work is calling templatize() once for each template and setting the private variables stamp() reads to switch instead:
this.templatize(tplA);
this.templatize(tplB);

for(let i = 0 ; i < 3 ; i++) {
  this._templatized = tplA;
  this.ctor = tplA._content._ctor;
  this.appendChild(this.stamp({nameA: i}).root);

  this._templatized = tplB;
  this.ctor = tplB._content._ctor;
  this.appendChild(this.stamp({nameB: i}).root);
}

I think two things should be done about this:

Fix the bug in templatize() causing the breakage.
Add a template override parameter to stamp():

    /** ...
     * @param {HTMLTemplateElement=} template The template to use (must have been
     *   processed with templatize before), if not given, use the last templatized one.
     */
  stamp: function(model, template) {
      model = model || {};
      var ctor = template ? template._content._ctor : this.ctor;
      if (this._parentProps) {
        var templatized = template ? template : this._templatized;
        for (var prop in this._parentProps) {
          if (model[prop] === undefined) {
            model[prop] = templatized[this._parentPropPrefix + prop];
          }
        }
      }
      return new ctor(model, this);
    },

This is not only triggered when trying to use multiple templates, but also in web component tests using a fixture containing an element that uses the templatizer. The fixture is supposedly torn down at the end, but because the templatizer adds _content._ctor to the original element, this persists between test cases, breaking their isolation: every test case in my suite passes on its own, but the suite fails with the errors described in the bug.
A workaround I found is to manually remove the _content._ctor from all templates:
  teardown(function() {
    for (let template of document.querySelectorAll('template')) {
      if (template._content) {
        template._content._ctor = undefined;
        template._content = undefined;
      }
    }
  });

I'm having the same (or similar) issues, by making multiple calls to this.templatize(template) and this.stamp() on the same templates. Works the first time on a given template, but any subsequent calls to this.stamp() do not apply bound values on creation.
I noticed that making changes to bound values after creation do seem to propagate correctly to the stamped elements, indicating that the bindings are there. So I tried the solutions proposed above and many other attempts including _prepParentProperties but none worked for me.
I ended up by initialising the bound values manually at creation time. This seems to work for now... it's a bit of a hack, but in case it helps anyone:
  // this overrides the default from Polymer.Templatizer
  stamp: function(model) {
    model = model || {};

    if (this._parentProps) {
      var templatized = this._templatized;
      for (var prop in this._parentProps) {
        if (model[prop] === undefined) {
          model[prop] = templatized[this._parentPropPrefix + prop];

          // this is a fix for missing initial bindings on subsequent stamps
          // https://github.com/Polymer/polymer/issues/3755
          if (model[prop] === undefined) {
            model[prop] = this._getBinding(prop, this.dataHost);
          }
        }
      }
    }

    return new this.ctor(model, this);
  },

  _getBinding: function(prop, dataHost) {
    var data = dataHost && dataHost.__data__;

    if (!data) {
      return undefined;
    }

    if (prop in data) {
      return data[prop];
    }

    return this._getBinding(prop, dataHost.dataHost);
  }

Ran into this same issue. @liabru workaround seems to do the trick 👍

With the new model of Polymer.Templatize.templatize (https://github.com/Polymer/polymer/blob/72a59f77cd5375d3bb691b0396c1f4b30ac722d8/lib/utils/templatize.html) this issue has been resolved. You can now stamp multiple unique templates. An example which uses 2 templates and correctly implements forwardHostProp is http://jsbin.com/zoludihiqo/edit?html,console,output


Fix signing not working using Ledger on Testnet

Mainnet networkId was being used instead of dynamic(in this case testnet), which made created signatures invalid on testnet.

Thanks for your controbute, it's not only networkId field problem.
We are trying to solve this problem: https://discord.com/channels/484437221055922177/733755408161833040/988987213956149268

@wjdfx What else is there? I didn't see anything else on discord.
Note that I tried this fix and ledger signing works on testnet now.

@wjdfx What else is there? I didn't see anything else on discord.
Note that I tried this fix and ledger signing works on testnet now.

Oh, If you have been tried and worked, let me try again, before we use same change but it doesn't worked.

@binier are you sure it's will successfully after this code? You didn't got [Invalid_signature]  error?

https://devnet.minaexplorer.com/wallet/B62qqXi8mm3UsY45DJFpEc6KK4k69hcVmWf6xm4FRYcuUKXUGW2BGit
@wjdfx The second transaction was done using Ledger + locally built Auro wallet.
Can you try clean/rebuilding the extension and adding to chrome? Maybe it's a cache thing..

@binier can you add my discord: niuniu | Bit Cat#9001
Or telegram @sanxiacat
Thank you.


faster integerization in integer walker fciqmc

Pull Request Test Coverage Report for Build 762992095

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 72.829%

Totals

Change from base Build 761510223:
-0.02%

Covered Lines:
2088

Relevant Lines:
2867

💛  - Coveralls

This change is incorporated in #59.


[9.x] Added missing method to CursorPaginator interface

Autocompletion in IDEs doesn't recognize the withQueryString method because paginate, simplePaginate and cursorPaginate returns the CursorPaginator interface that doesn't contain the method withQueryString.
The interface method can be safely added because the class that implements CursorPaginator, has a base class with the withQueryString implemented.

Indeed this is a major breaking change, and cannot be added to 9.x.

Sounds reasonable, tomorrow I will propose the changes to the master branche.


Tweak log and logging levels

Tweaked our logging so:

verboseLog() — like debug, but not want to show it by default (since we configure our loggers to .debug) because it's too verbose/noisy. This includes logging in deinit{} and things that happen too frequently, yet not useful (eg. skipping TokenScript signature verification)
debugLog() — like info, but more for debugging purposes. This is our default logging level for console, so must not be so excessive that the console is unreadable
infoLog() — should be the most common. Refreshes, etc. This is our default logging level for log files (currently unused, but we'll let user attach them to support emails in the future)
warnLog() - unexpected errors that are unhandled, mostly. So we can look out for these and fix/handle them
errorLog() — not used

cc @eviltofu

Force-pushed after tweaking commit message


fix: action-a/Dockerfile to reduce vulnerabilities

The following vulnerabilities are fixed with an upgrade:

https://snyk.io/vuln/SNYK-DEBIAN9-APT-407402
https://snyk.io/vuln/SNYK-DEBIAN9-GLIBC-356506
https://snyk.io/vuln/SNYK-DEBIAN9-GLIBC-356506
https://snyk.io/vuln/SNYK-DEBIAN9-GLIBC-356851
https://snyk.io/vuln/SNYK-DEBIAN9-GLIBC-356851

df


Add a title to the homepage link

Added a title to the homepage link.
References
Related to https://github.com/github/accessibility-audits/issues/2739

I assessed a couple of other options as well:

Adding <title> to the svg doesn't feel correct as the issue says we need to add title to the link and not to the image.
Adding alt attribute is inappropriate as it is intended for using on img

We already have a link to npmjs.com on the right side. I think it is fine to have the logo redirect to docs homepage and have the title npm docs.

+1 to the comments to just make it as npm Docs, also do check once that the tool passes with updating the title else we might have to update aria-label instead.

@anurbol @prabum3 @20shivangi  It seems we have 2 a pointing to the docs homepage one for logo another for text npm Docs. I would suggest that we only have one a and move the logo inside the a and then the text would act as title and the logo would be aria-hidden.

@anurbol @prabum3 @20shivangi It seems we have 2 a pointing to the docs homepage one for logo another for text npm Docs. I would suggest that we only have one a and move the logo inside the a and then the text would act as title and the logo would be aria-hidden.

Yes @amit-avit , that's what I was saying that there will be duplication :D
We can go with this approach

@amit-avit @prabum3 @20shivangi
I've merge the two links into one (there is now single a instead of two). Because previously there were two independent elements - logo and title, they were positioned on an arbitrary height relative to each other, and now they are strictly vertically aligned in their common link element (which lead to the logo now being positioned a bit lower). Which I believe is a good thing. But if I am mistaken please let me know.
https://user-images.githubusercontent.com/3603448/196427424-9af4d6a0-769c-4394-a944-996cf2bbf7df.mp4


Add Serial Programmer for Jekyll, Hugo & Gatsby

Opening PR again because Something happened in the last one, Gatsby theme didn't showed up.

It's still now showing up the Gatsby theme, any idea?

Damn, It was still a private repo, Fixed it now.

@jmau111 is there anything wrong with this PR ?
Your's got merged right ?


Different return types depending on status code alone

What are the steps to reproduce this issue?

Have a operation that returns multiple return codes for success, e.g.

  /accept/{invite_key}:
    parameters:
      - in: path
        name: invite_key
        required: true
        schema:
          type: string
    post:
      operationId: AcceptInvitation
      responses:
        '201':
          description: Invitation accepted
          content:
            application/json:
              schema:
                type: object
        '204':
          description: Invitation already accepted before
          content:
            application/json:
              schema:
                type: object

What happens?
The generated code cannot distinguish between the two types as it doesn't consider the status code anywhere.
What were you expecting to happen?
Some way for the code to either return the status code (in addition to the body), or the generated code to handle the difference.
Any logs, error output, etc?
n/a
Any other comments?
I don't know whether "I am holding it wrong" or this is a gap - looking for guidance.
What versions are you using?
Operating System: MacOS
Package Version: 6.12.1
Browser Version: n/a

@02strich
Well, OpeaAPI supports the case where there are multiple 20X. Also, in orval
Supports multiple types of successful responses. However, the method of accessing the returned status code differs depending on the client you are using, so please refer to the respective client package you are using.


Disable Code Splitting in Nuxt Config

Just wondering if we can get an option to disable code-splitting when generating routes ?
I tried to use the below but could get it to work:
plugins: [
      new webpack.optimize.LimitChunkCountPlugin({
        maxChunks: 1
      })
    ]

It should be build.plugins, doc: https://nuxtjs.org/api/configuration-build#plugins.
Or you can use build.extend to customize any webpack config you want doc: https://nuxtjs.org/api/configuration-build#extend.


⚠ Bofrost.lu has degraded performance

In f22eeba, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1154 ms

Resolved: Bofrost.lu performance has improved in 0df0edc after 25 minutes.


Fix OpenID Connect code flow by always returning id_token

Token Endpoint must always return id_token; client not required to send response_types with "id_token" in Token Request, expecting this violates the specification and ruins code flow (for apache module mod_auth_openidc at least).
See http://openid.net/specs/openid-connect-core-1_0.html#TokenRequest

Is Hybrid flow what you need? https://github.com/cloudfoundry/uaa/blob/develop/uaa/src/test/java/org/cloudfoundry/identity/uaa/integration/feature/OpenIdTokenGrantsIT.java#L239-239
We do not want an open id token returned unless specifically requested. We're an OAuth server first, OpenID Connect compatibility is something we are working towards, but shouldn't override or mess up our OAuth behavior.

Hmm, last time I've tried UAA + mod_auth_openidc hybrid flow was not working, shall re-check.
The current behaviour breaks RFC6749 (OAuth 2.0), as I see it. :-1:
"response_type" parameter expected to be send to authorization endpoint and nowhere else. Token endpoint doesn't expect it, uses "code" parameter instead.
I'm not going to argue about the policies you guys've decided upon. :wink:
I just see (correct me if wrong, please) UAA doesn't follow OpenID Connect spec in the case of Code flow (expecting something not defined by the spec), if that's by design I'm fine with that, we have that thing working for us in our fork. :stuck_out_tongue_winking_eye:

We're still going through the motions of this PR. and will be coming back to it shortly

Fixed via https://github.com/cloudfoundry/uaa/commit/5f8286d2e9aa383611c39370d04b33e981ec23a8

Thank you, Filip!

@ysoldak Take note, it's according to spec. Slightly different than you had it. You have to explicitly define the scope=...openid... parameter in the /oauth/authorize request.


read.cv link support

Would be great to have support for read.cv in the links.
Example site: https://read.cv/vmstan

All set! Thanks for the suggestion. 👍

Awesome. Looks good.
(Also thanks for the blue checkbox)