[futter_tools] StateError: Bad state: Future already completed

Version: stable/3.13.8
Command: debug_adapter
StateError: Bad state: Future already completed
at _Completer.completeError(future_impl.dart:18)
at ThreadInfo.resolveUrisToPathsBatch.<anonymous closure>(isolate_manager.dart:1023)
at _LinkedHashMapMixin.forEach(compact_hash.dart:625)
at ThreadInfo.resolveUrisToPathsBatch(isolate_manager.dart:1023)
at <asynchronous gap>(async)
at ThreadInfo.resolveUrisToPackageLibPathsBatch(isolate_manager.dart:976)
at <asynchronous gap>(async)
at IsolateManager._sendLibraryDebuggables(isolate_manager.dart:812)
at <asynchronous gap>(async)
at Future.wait.<anonymous closure>(future.dart:525)
at <asynchronous gap>(async)
at IsolateManager._configureIsolate(isolate_manager.dart:392)
at <asynchronous gap>(async)
at IsolateManager.registerIsolate(isolate_manager.dart:221)
at <asynchronous gap>(async)
at DartDebugAdapter._configureExistingIsolates.<anonymous closure>(dart.dart:749)
at <asynchronous gap>(async)
at Future.wait.<anonymous closure>(future.dart:525)
at <asynchronous gap>(async)
at DartDebugAdapter._configureExistingIsolates(dart.dart:742)
at <asynchronous gap>(async)
at DartDebugAdapter._withErrorHandling(dart.dart:2424)
at <asynchronous gap>(async)
at DartDebugAdapter.connectDebugger(dart.dart:690)
at <asynchronous gap>(async)
at FlutterDebugAdapter._connectDebugger(flutter_adapter.dart:383)
at <asynchronous gap>(async)
at FlutterDebugAdapter._handleDebugPort(flutter_adapter.dart:464)
at <asynchronous gap>(async)

any solution, i riceve the error:
Error: Bad state: Future already completed

Hi @stoppiNeobiz, are you able to provide some reproducible steps for us to replicate, that would help us find a solution if it has not already been fixed

hi @eliasyishak  the complete errore is this, i work on web:
Error: Bad state: Future already completed
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 294:3  throw_
dart-sdk/lib/async/future_impl.dart 43:31                                    complete
packages/google_sign_in_web/google_sign_in_web.dart 170:5                    initWithParams
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 45:50           <fn>
dart-sdk/lib/async/zone.dart 1661:54                                         runUnary
dart-sdk/lib/async/future_impl.dart 162:18                                   handleValue
dart-sdk/lib/async/future_impl.dart 846:44                                   handleValueCallback
dart-sdk/lib/async/future_impl.dart 875:13                                   _propagateToListeners
dart-sdk/lib/async/future_impl.dart 647:5                                    [_completeWithValue]
dart-sdk/lib/async/future_impl.dart 721:7                                    callback
dart-sdk/lib/async/schedule_microtask.dart 40:11                             _microtaskLoop
dart-sdk/lib/async/schedule_microtask.dart 49:5                              _startMicrotaskLoop
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 181:7

this is the code:
final GoogleSignIn _googleSignIn = GoogleSignIn(
        clientId: "xxxxxxxxxx.apps.googleusercontent.com",
        scopes: scopes,
      );

this code cause the error .

hi @eliasyishak the problem compares when I use bloc, if I remove the bloc consumers then it doesn't give an error and everything works. This, however, is a problem

hi @eliasyishak , i confirm that is bloc, this is my very simple app:
main:
import 'package:firebase_auth/firebase_auth.dart';
import 'package:firebase_core/firebase_core.dart';
import 'package:flutter/material.dart';
import 'package:flutter_bloc/flutter_bloc.dart';
import 'bloc/login_cubit/login_cubit.dart';
import 'firebase_options.dart';
import 'home.dart';
import 'repositories/authentication_repository.dart';

Future<void> main() async {
  WidgetsFlutterBinding.ensureInitialized();

  await Firebase.initializeApp(options: DefaultFirebaseOptions.web);
  runApp(const MyApp());
}

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

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MultiRepositoryProvider(
      providers: [
        RepositoryProvider<AuthenticationRepository>(
          create: (context) => AuthenticationRepository(
            firebaseAuth: FirebaseAuth.instance,
          ),
        ),
      ],
      child: MultiBlocProvider(
        providers: [
          BlocProvider<LoginCubit>(
            create: (context) => LoginCubit(
              authenticationRepository: context.read<AuthenticationRepository>(),
            ),
          ),
        ],
        child: MaterialApp(
          title: 'amdigitallife',
          theme: ThemeData(
            useMaterial3: true,
          ),
          home: HomePage(),
        ),
      ),
    );
  }
}

this is the home:

import 'package:firebase_auth/firebase_auth.dart';
import 'package:flutter/foundation.dart';
import 'package:flutter/material.dart';
import 'package:flutter_bloc/flutter_bloc.dart';
import 'package:google_sign_in/google_sign_in.dart';
import 'package:google_sign_in_platform_interface/google_sign_in_platform_interface.dart';
import 'package:google_sign_in_web/google_sign_in_web.dart' as web1;
import 'bloc/login_cubit/login_cubit.dart';

class HomePage extends StatefulWidget {
  const HomePage({super.key});

  @override
  State<HomePage> createState() => _HomePageState();
}

class _HomePageState extends State<HomePage> {
  @override
  void initState() {
    super.initState();
    _init();
  }

  _init() {
    const List<String> scopes = <String>[
      'email',
    ];
    final GoogleSignIn googleSignIn = GoogleSignIn(
      clientId: "472109982413-ivqi0bulgrqlkoaktrq6e2rjjc9ainm2.apps.googleusercontent.com",
      scopes: scopes,
    );
    googleSignIn.onCurrentUserChanged.listen((GoogleSignInAccount? account) async {
      if (kIsWeb && account != null) {
        final authentication = await account.authentication;
        final idToken = authentication.idToken;
        final credential = GoogleAuthProvider.credential(
          accessToken: "",
          idToken: idToken,
        );
        await FirebaseAuth.instance.signInWithCredential(credential);
      }
      googleSignIn.signInSilently();
    });
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Column(
        children: [
          (GoogleSignInPlatform.instance as web1.GoogleSignInPlugin).renderButton(configuration: web1.GSIButtonConfiguration()),
          BlocConsumer<LoginCubit, LoginState>(
              listener: (context, state) {},
              builder: (context, state) {
                return Text("Test");
              })
        ],
      ),
    );
  }
}

The login cubit is simple cubit empty, if you try with blocConsumer in page, not work, if you delete the bloc works correctly.

hi @eliasyishak sorry if I write to you again but I have reduced the problem further, the problem is this line:
authenticationRepository: context.read() passed to the cubit. if i delete this line work correctly otherwise i riceve the error

Hey guys, I've solved it! This bug is from the latest versions of Flutter and Dart extensions for VS Code. Just downgrade their versions a few releases, and it should be fixed.

Hey guys, I've solved it! This bug is from the latest versions of Flutter and Dart extensions for VS Code. Just downgrade their versions a few releases, and it should be fixed.

^ FYI @DanTup. This is one of the top crashers on stable/3.16.4

Thanks, I'll take a look.

I'm assuming this downgrade opted them out of using DAP. This is one of the top crashers on stable/3.16.4

Yeah, if you go back a few versions you'll likely end up on the legacy DAPs. You could also force that by setting "dart.previewSdkDaps": false in settings instead of downgrading.
How often is this occurring? Are there specific actions that cause it? Before the last update ~50% of people were on the new debug adapters and in the latest release it became 100%, it's odd that it didn't come up before (although it's always possible the behaviour changed slightly in the latest Flutter release).

it's odd that it didn't come up before (although it's always possible the behaviour changed slightly in the latest Flutter release).

Well this was filed back in October for 3.13

Well this was filed back in October for 3.13

Ah sorry, missed that.
I think this issue could be the same as https://github.com/dart-lang/sdk/issues/52632, although I don't know if there are other ways to trigger it. If I create a Flutter app where a filename has a comma, then the debug session terminates and I get a flutter_01.log written that contains this:
StateError: Bad state: Future already completed

#0      _Completer.completeError (dart:async/future_impl.dart:19:31)
#1      ThreadInfo.resolveUrisToPathsBatch.<anonymous closure> (package:dds/src/dap/isolate_manager.dart:1136:58)
#2      _LinkedHashMapMixin.forEach (dart:collection-patch/compact_hash.dart:633:13)
#3      ThreadInfo.resolveUrisToPathsBatch (package:dds/src/dap/isolate_manager.dart:1136:20)
<asynchronous suspension>
#4      ThreadInfo.resolveUrisToPackageLibPathsBatch (package:dds/src/dap/isolate_manager.dart:1089:21)
<asynchronous suspension>
#5      IsolateManager._sendLibraryDebuggables (package:dds/src/dap/isolate_manager.dart:913:5)
<asynchronous suspension>
#6      Future.wait.<anonymous closure> (dart:async/future.dart:523:21)

I will fix the issue causing us to try to complete the completer twice (I have an idea what that is), however we might still be left with an error (although one with a better message) if the cause is that the VM is returning invalid responses to that request.

I've opened https://dart-review.googlesource.com/c/sdk/+/342800 which will improve the error message here to make it clearer what the issue is and adds a failing test for https://github.com/dart-lang/sdk/issues/52632.
However, I don't have a good way to work around the bug because when the response length doesn't match the request length, we can't tell which items are valid/invalid (and if we treat them all as invalid many things won't work correctly). We'll need the underlying issue to be resolved to properly address this.
For anyone hitting this bug - I would check whether any of your files may have commas in the filenames. If so, renaming the files to not include commas may avoid the issue until there's a fix for https://github.com/dart-lang/sdk/issues/52632. If you have a repro and believe you don't believe you do, please try:

Run the Dart: Capture Debugging Logs command from the command palette before starting your application
Start your application and trigger the issues
Click Cancel on the logging notification to stop logging and open the log file
Search for a line that contains "method":"lookupResolvedPackageUris" (probably near the end of the log just before the session terminated)
Format that line as JSON and it will include a list of paths - one of which may contain a comma or other character that's triggering https://github.com/dart-lang/sdk/issues/52632

It turns out, my change does actually improve things here. Without the fix, the exception is thrown synchronously because we tried to complete a completed future. However with my change, we're no longer throwing, we're just completing those futures with errors which is picked up by some other error handling.
It doesn't solve the whole problem (there are still errors), but in my testing with the fix on Flutter master, it's not terminating the debugging session.

It turns out, my change does actually improve things here. Without the fix, the exception is thrown synchronously because we tried to complete a completed future. However with my change, we're no longer throwing, we're just completing those futures with errors which is picked up by some other error handling.
It doesn't solve the whole problem (there are still errors), but in my testing with the fix on Flutter master, it's not terminating the debugging session.

ahh, ok, so we suspect that the underlying error being hit is https://github.com/dart-lang/sdk/issues/52632, which is currently being investigated. And then this DDS CL will prevent this error from crashing the tool but be handled by existing error handling code. Do I have that right?

ahh, ok, so we suspect that the underlying error being hit is https://github.com/dart-lang/sdk/issues/52632, which is currently being investigated. And then this DDS CL will prevent this error from crashing the tool but be handled by existing error handling code. Do I have that right?

Yes, that is correct - although this is based on the assumption that the trigger here is having commas in filenames (or something else that fails in the same way). Without repros from those hitting this I can't be certain there aren't other conditions (which may or may not behave differently).
I'm not certain there aren't other ways in which existing error handling wouldn't cover this, but in my testing (with the change) I could not produce any crashes and debugging worked. There remains a risk that some things won't work correctly until https://github.com/dart-lang/sdk/issues/52632 is resolved though.
Once that change lands, we should push an updated DDS and make sure it gets into Flutter (cc @bkonyi!)


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-30-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4334

Questions ?
Please refer to the Backport tool documentation


put tutorial content in correct place

Change Summary
Correction from #16
Checklist

[ ] Unit tests for the changes exist
[ ] Tests pass on CI
[ ] Documentation reflects the changes where applicable

It seems that the tutorials.md file wasn't built in the preview. 😦  I think I need to fix the actions.  This is a bit tricky.  The question is when should we update the data/ files (e.g., the GitHub statistics and the download statistics).  I'll create an issue and PR to resolve this.

I'm trying to fix this with #19.  If this works, then you should be able to pull in recent changes to this PR after #19 is merged.

@jukent:  Ok.  I think the workflow is fixed.  You should be able to update your branch and it should work.


Making Guess Game efficient

Any ideas for making Guess Game more faster and efficient? Also any interface changes are welcome.

What about using colorama to make a colorful interface?

What about using colorama to make a colorful interface?

Nice. Go for it.
Also try something to improve the game efficiency and adding more features.

should I make a hard, medium and easy  mode for the game.
Hard mode : regenerates the number after each try as it becomes easy to guess after 2 try.
medium mode : regenerates the number after 2 try.
easy mode :- same as game in current state.

should I make a hard, medium and easy mode for the game.
Hard mode : regenerates the number after each try as it becomes easy to guess after 2 try.
medium mode : regenerates the number after 2 try.
easy mode :- same as game in current state.

That seems interesting, go for a leveled game.

How about showing a number line of the range of numbers and every time the user guesses it will add a point to the number line?
For example:
|>----------------------------------------------------------------------------<|
10                                                                            20

How does this look like?

How does think look like?

How does this look like?

Creative!

How does this look like?

Creative!

Can you try doing this in Jupyter Notebook ?

How about showing a number line of the range of numbers and every time the user guesses it will add a point to the number line?
For example:
|>----------------------------------------------------------------------------<|
10                                                                            20

This won't add a valuable contribution. It's just formatting, we would like to increase the working efficiency first.

How about showing a number line of the range of numbers and every time the user guesses it will add a point to the number line?
For example:
|>----------------------------------------------------------------------------<|
10                                                                            20

This won't add a valuable contribution. It's just formatting, we would like to increase the working efficiency first.

Ok, I was just suggesting. Sorry for the inconvenience.

added easy and hard mode to guess_game.py

What about an option E which lets u choose your own range of numbers? (only in hard and medium mode)

What about an option E which lets u choose your own range of numbers? (only in hard and medium mode)

Not a bad idea. I will assign anyone willing to add "E" option.

More updates and enhancements are always welcome.


Cannot import v5.1.0 due to "non optimal" go.mod

I am using go1.14.
I tried to import v5.1.0 with this command:
go get -u<EMAIL_ADDRESS>
and it gave me this error:
go get<EMAIL_ADDRESS><EMAIL_ADDRESS>invalid version: module contains a go.mod file, so major version must be compatible: should be v0 or v1, not v5

As stated in go mod wiki page, any package with major version larger than v0 and v1 must include its major version in the module name.
So the statement here module github.com/gojektech/heimdall should be appended with /v5 so that it would become module github.com/gojektech/heimdall/v5.
I don't know whether this change would broke backward compatibility for imports.
Example: will import "github.com/gojektech/heimdall/httpclient" be changed to import "github.com/gojektech/heimdall/v5/httpclient" and all will be ok?
If all is OK I can make a PR to this.

I'm experiencing the same issue when I try to use v5.1.0

This issue is actual to me too. How i can upgrade library to 5.1.0 correctly using go get?

I'm also unable to import v5.1.0. https://github.com/gojek/heimdall/pull/80 seems to be a good fix.

#80 fixes this. closing this


US-2008 Users with the EOA wallet should see the gas fee in rBTC

https://github.com/rsksmart/rif-wallet/assets/47615361/52962696-134c-4476-891e-66223fbd7805

When I tested this ticket, I noticed two things:
1- The fee displayed on the confirmation screen differs from the fee displayed when the transaction is completed
20231211_160831.mp4
2- Could you please rebase the changes into this PR to ensure that the fee is deducted in rbtc when sending rdoc and usdrif?
Aside from that, I have a doubt: why do I go straight to the send screen after creating a wallet instead of deploying it?
20231211_163513.mp4

I checked the code but the thing is I don't manipulate exact values, I only change how it is represented, so I don't think that this change in fee is due to the things I made here, but maybe I am wrong @jessgusclark can you help us here?

@jormelCoin , for displaying the gas cost, this is an incorrect number but unrelated to this PR. I have created US-2071 to investigate this.


replace wmr config checker with asmdef version defines

This change removes the requirement for running the winmr config checker. It is replaced by DOTNETWINRT version defines in the appropriate asmdefs

/azp run

checking the code. the doc updates will be done before merging

actually, the documentation needs to be modified after the dotnetwinrt package is published for the feature tool. a separate issue will be filed

docs issue is #9320

/azp run


build error  : Post-processing 'desktop/ext/css/cui/bootstrap2.css' failed!

os:ubuntu 16.04
java: oracle java 1.8.0_65
exec make apps cmd to build hue and get the following error:
Post-processed 'desktop/ext/css/cui/bootstrap-responsive2.css' as 'desktop/ext/css/cui/bootstrap-responsive2.e47b2a557fdc.css'
Post-processing 'desktop/ext/css/cui/bootstrap2.css' failed!

Fixed, thanks!


Update the SSB site status metric number and states

This change was announced yesterday by Stephan.
I still need to test in testbed and create a branch PR.
@ticoann please review

test this please


Update index.js

trying to guard against fastboot (don't import bootstrap-datetimepicker, which requires jquery if we're on fastboot)

Thank you!
I never used fastboot, but looking at the code wouldn't it be better to use process.env.EMBER_CLI_FASTBOOT for addon's?
https://github.com/ember-fastboot/ember-cli-fastboot/issues/105

@claudiocro sorry, I think you're probably right! I'm a newb )-:

Closing as you want t

Closing as you want t


Rendered Plane Texture Issue in Visualizer

The rendered plane in the visualizer is no longer showing the chequered pattern. It appears that the XML is ignoring the textures. Is this an intended change? Could you provide any information on which version introduced this change?
Below is the relevant XML code from ant.xml:
<asset>
  <texture builtin="gradient" height="100" rgb1="1 1 1" rgb2="0 0 0" type="skybox" width="100"/>
  <texture builtin="flat" height="1278" mark="cross" markrgb="1 1 1" name="texgeom" random="0.01" rgb1="0.8 0.6 0.4" rgb2="0.8 0.6 0.4" type="cube" width="127"/>
  <texture builtin="checker" height="100" name="texplane" rgb1="0 0 0" rgb2="0.8 0.8 0.8" type="2d" width="100"/>
  <material name="MatPlane" reflectance="0.5" shininess="1" specular="1" texrepeat="60 60" texture="texplane"/>
  <material name="geom" texture="texgeom" texuniform="true"/>
</asset>
<worldbody>
  <light cutoff="100" diffuse="1 1 1" dir="-0 0 -1.3" directional="true" exponent="1" pos="0 0 1.3" specular=".1 .1 .1"/>
  <geom conaffinity="1" condim="3" material="MatPlane" name="floor" pos="0 0 0" size="40 40 40" type="plane" rgba="0.5 0.5 0.5 1.0"/>
  ...
</worldbody>

And below the new vs old render produced by the visualizer in this colab:

See https://github.com/google/brax/releases/tag/v0.11.0, let us know if there's still an issue!


Before upload data to the storage account

@adiazcan commented on Fri Oct 19 2018
You have to explain that we need to create a File System or Container on Data Lake, before upload the json radio data. If you run the azcopy command without create this container, the command will fail

Detalles del documento
⚠ No edite esta sección. Se requiere para docs.microsoft.com ➟ Vinculación de problema de GitHub.

ID: 036f4100-7c61-bc71-1d90-1afe39b5456f
Version Independent ID: 471e0ecd-27ab-56ab-48f3-d16f14d87e88
Content: Aprenda a realizar operaciones de extracción, carga y transferencia con Azure Databricks
Content Source: articles/storage/data-lake-storage/handle-data-using-databricks.md
Service: azure-databricks
GitHub Login: @jamesbak
Microsoft Alias: jamesbak

Hi team,
Please check this issue.
Thanks!

@LisandroSu Thanks for the feedback! We are currently investigating and will update you shortly.

Hi,
I believe that if you follow the steps in order you should be Okay at the end of  step 4 it mentions:
Now the file system is created for the storage account.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.
Regards,
Alberto Vega


Is where a way to integrate with Iron-router?

Is where a way to integrate upload-server with Iron-router , i always get access denied on '/upload' path, but upload folder does not exist on filesystem. Need example, please.

I am using with Iron router and have no problem. Try cheking folder permissions and configuration.

True, this package is router agnostic, where routes can be configured by both flow and iron router.


Set celery timezone for enikshay

@javierwilson @mkangia @proteusvacuum
I'm pulling this from the icds config https://github.com/dimagi/commcarehq-ansible/blob/master/ansible/vars/icds/icds_public.yml
I didn't notice anything going wrong, just thought this might be a better setting. I think without this the enikshay task [0] is running at midnight UTC (530 IST). this would cause it to run at midnight IST
buddy @sravfeyn
[0] https://github.com/dimagi/commcare-hq/blob/af4c010ee38dfeda5e6149a880be374c9dd16843/custom/enikshay/tasks.py#L62

Repeaters fire every 5 minutes with heartbeat, so this shouldn't affect that. This is a good change, I didn't realize this was running at 5:30AM.


Consider removing the coding introduction chapter

From an international perspective, that chapter is not contributing to the guide. The only content in it currently is teacher notes and stuff related to NCEA, which should instead be in the curriculum section.
@timbellnz do you mind if I just remove it altogether?

The idea that there are three kinds of coding is a generic concept (and appears in other books), but the teacher specific material could be removed. I think it's useful to tackle the ambiguity of "coding" somewhere. The alternative is to mention it in each chapter, but that would be repetitive.

That's a good idea. Currently that chapter isn't really doing that, and effectively needs a complete rewrite (although will be a short chapter). Are you able to do that, given that you are a guru at coding topics?
We could also bring up a couple of other ideas in curiosity boxes, such as entropy and information theory in general :-)

Closing this and making a new issue for rewriting the chapter.


Update maintainers

cc: @dotsdl @j-wags

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Works for me! Thanks @mattwthompson!

@jthorton can you merge this? Neither I nor @mattwthompson can.

Thanks!


Change included header for uint64_t in InstructionsExecuted.h

The Linux build on swiftpackageindex.com said it couldn’t find uint64_t in InstructiosnExecuted.h. I think we need to include stdint.h instead. Let’s try that.

@swift-ci Please test


Finish up the new website.

Flesh out and migrate content from the previous Electric website to the "next" site.

@KyleAMathews I'm curious whether you're amenable to (or whether you want to cut) the two stage CTA section at the bottom of https://deploy-preview-1570--electric-next.netlify.app
It's intended to get across that Electric is both simple to get started with "one fetch at a time" and something that intends to take you all the way to a fully local-first paradigm when you're ready.
I'm conscious that I'm under strict instructions not to overreach / document things that aren't true yet. In my defence, the code shown does work and I think showing it may fire the imagination and connect the docs for developers, especially those who have come into electric through pglite.

Yeah the pglite code snippet seems like a good idea. It's a genuinely remarkable thing so both impressive and will get lots of people talking.


[BUG]lastTransitionTime and lastUpdateTime are same across all resources for Global role status fields

Rancher Server Setup

Rancher version: v2.9-head 1c2b815c8dd

Information about the Cluster

Kubernetes version: v1.30.1+k3s1
Cluster Type (Local/Downstream): Local

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

If custom, define the set of permissions: Admin

Describe the bug
Global role status fields for namespaced rules and cluster role exists have the same last transition time and last updated time, even when the namespaced rules resource is updated.
To Reproduce

Create a global role with the following yaml:

apiVersion: management.cattle.io/v3
builtin: false
displayName: grole1
kind: GlobalRole
metadata:
  name: grole1
  finalizers:
    - foo
namespacedRules:
  - cattle-global-datae:
    - apiGroups:
        - management.cattle.io
      resources:
        - preferences
      verbs:
        - '*'

The status field shows error as the namespace does not exist but for ClusterRoleExists, status is completed.
Edit the yaml and update the namespace name to cattle-global-data
Notice the error is resolved
Notice the lastTransitionTime and lastUpdateTime for both namespaced rules and cluster role exists.

Result
lastTransitionTime and lastUpdateTime are same even and is updated for cluster roles as well when there is no change to the cluster role.
Expected Result
Expected lastTransitionTime and lastUpdateTime to be different for both of the resources as there was a change only to the namespace rules.
Screenshots

The current implementation of the status field resets the entire status every time the global role handler reconciles the object. It would be more valuable to reset only the changed conditions. Will look into it.


Logical Operators

Hi,
I am searching for a way to query my collections and using logical operators via Rest. Something like the Resource Query Language https://doc.apsstandard.org/2.1/spec/rql/#spec-rql-logical
Do you know if there is something similar already available for meteor and if not any hint on how to do that with restivus?
Thanks in advance.
BR

Unfortunately, I'm not sure of any support for this in Meteor as yet. Please let me know if you find anything. The good news is that this is something I certainly intend to support in Restivus. It won't make it into the next major release (0.7.0), but it should follow shortly thereafter. See #70 for more information on the planned support for filtered searching via query params. Once that's up and running, I'll look into adding the support for logical operators. The Resource Query Language looks pretty well-defined, so if I don't find anything more widely adopted, I'll use that spec. If you're unable to wait (could be 6+ weeks) and would like to add the support for this yourself, then maybe we could squeeze it into the next major update.


Fix: phase test with img_size

I am not sure if it is the right fix, but I did this changes to run the test phase

Thank you !


Wrong link linked

In the Check the location of the CSV files section there's a wrong link to copying the files into the Docker container. It should be https://memgraph.com/docs/getting-started/first-steps-with-docker#copy-files-from-and-to-a-docker-container
instead of https://memgraph.com/docs/getting-started/install-memgraph/docker#copy-files-from-and-to-a-docker-container

Fixed.


Fix immutable mapping of JSON arrays

Hi,
I recently updated my project to take advantage of the new immutable support (thank you for adding it by the way), but found that JSON arrays (ex. [[String: Any]]) weren't mapping correctly.
It appears this is because execution ends up in Mapper.map(JSON: [String: Any]) which only handles the StaticMappable or Mappable case - not ImmutableMappable.
My naive approach was to follow the example of StaticMappable and add support in that method for ImmutableMappable. However I saw that ImmutableMappable defines a number of extensions on Mapper, I suspect the correct approach would be to provide such an extension that supported arrays.

I intended to leave a comment on cd824806f47cd4181f27c47155d343ebcb956909 :(

Thank you for the quick turn around on this @tristanhimmelman!


Cmd + shift + z does not work on Dvorak keyboards (cmd + y does)

Steps:
Normal (US) keyboard:

set keyboard layout to US
start atom --safe
new file
type something
cmd + z undoes
cmd + shift + z redoes

Dvorak keyboard:

set keyboard layout to Dvorak
start atom --safe
new file
type something
cmd + z undoes
cmd + shift + z does not redo
cmd + y does redo

Notes:

Running 1.4.3 on El Capitan
I've had this problem since I started using Atom, two days ago
This is first and only keybinding issue I've ever encountered in using Dvorak for the last 6 years on Mac.

Anything I can do to provide more info?

@godspeedelbow Have you tried using Keyboard-Localization?

This is a duplicate of https://github.com/atom/atom-keymap/issues/37. Please subscribe there for updates.

Hi @lee-dohm, I saw that both this issue and atom/atom-keymap#37 were closed, but I also use the Dvorak keyboard and I'm having the same issue.
Should I open another issue? Should we re-open this?
@godspeedelbow, are you still having this issue as well?
Cheers,

@pirelenito Please open a new issue over at the https://github.com/atom/atom-keymap repository. Make sure you fill out the entire issue template when you open the issue.  Feel free to @mention me when you have opened it and I can take a look.

Nope @pirelenito, problem solved by switching back to Qwerty. I even wrote something about it :)
https://github.com/godspeedelbow/writing/blob/master/dvorak.md


Python3 compatability

I added python3 compatability.  Had to mostly update print lines, dictionary.keys() errors, where I had to coerce the keys to a list.
There were a few other bugs that I don't quiet understand - was able to provide fixes but I'm not sure they make intuitive sense.
The most important of these bugs occurs on line 438-440 in tablecpdfactorization.py.  This is the code I changed:
try:
      # modify result
                    current[node] = self.bn.Vdata[node]["vals"][rindex]
except UnboundLocalError:
                    current[node] = self.bn.Vdata[node]["vals"][x]
                    #I have no idea if this is the correct thing to do

I'm not sure why rindex is used, it's not guaranteed to exist, so it feels odd to force a result change and have that be the thing you return based on conditions you cannot guarantee will be met.  If I have time I'll go back in and refactor this and other things.  But it would be helpful to know why this was done in the first place.

There was still an issue with some print statements below the units module, which I fixed in https://github.com/Anaphory/libpgm/commit/bbcbb8d39c58e869e48f6e29b1aeae39b868e582. (I also moved utils to be a submodule of libpgm, because I don't want a global utils package that is specific to some other package.)


Backend function benchmark

The discussion behind this request is contained in issue #13 (link).

Great!


Format conversion doesn't seem to work`

Given this PNG input image:

and this code:
ImageVoodoo.with_image("test.png").bytes("JPG")

Results in this broken file:

Am I just doing something wrong here?
ImageVoodoo.with_bytes(ImageVoodoo.with_image("test.png").bytes("JPG")).format

returns JPG as expected

No obvious answer yet (although I recently switched to Linux and I am realizing OpenJDK does not have JAI bundled in it :| ):
http://stackoverflow.com/questions/3432388/imageio-not-able-to-write-a-jpeg-file
The colorspace comments makes me think there is some code I need to add when translation is from a png to a jpg (although I have done this tons of times so I don't get why it happens here).

Hmm here is another article pointing out in the answer it is a bug in Java which has never really been fixed:
http://stackoverflow.com/questions/13072312/jpeg-image-color-gets-drastically-changed-after-just-imageio-read-and-imageio
Wow if we need to do this to fix this then there may be issues since I will need to load some Java code.

FWIW here's java -version:
› java -version
java version "1.8.0_91"
Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.91-b14, mixed mode)

Looks like it maybe just needs to be converted to an RGB image first?
http://stackoverflow.com/a/2408779/813265

Well, actually it seems like bytes is writing RGB data to a CMYK jpeg file.

Looks like there's a possibly relevant PR: https://github.com/jruby/image_voodoo/pull/9


workspaces: bump to v0.1.0-alpha4

/lgtm

hmmm, looks like prow is having some issues.  This might not land until monday.

/retest

/retest


Is there support for locale?

Hi, I liked a lot this package, but I wasn't able to find a way to change locale.
is there any planning to support?
Thanks

Hello @fabiohxcx we have the same problem. Have you finally found a solution to change locale ?
Thanks

Hi Alice,
I needed to implement timeLineBuilder, eventTileBuilder, etc.
Like this:

 timeLineBuilder: (date) => Transform.translate(
        offset: Offset(0, -7.5),
        child: Padding(
          padding: const EdgeInsets.only(right: 7.0),
          child: Text(
            "${((date.hour - 1)) + 1} h",
            textAlign: TextAlign.right,
            style: TextStyle(fontSize: 15.0),
          ),
        ),
      ),

weekDayBuilder: (day) => Container(
        alignment: Alignment.center,
        margin: EdgeInsets.zero,
        padding: EdgeInsets.symmetric(vertical: 10.0),
        decoration: BoxDecoration(
          border: Border.all(
            color: Color(0xffdddddd),
            width: 0.5,
          ),
        ),
        child: Text(
          weekTitles[day],
          style: TextStyle(
            fontSize: 17,
            color: AppColors.black,
          ),
        ),
      ),

I used the default implementations as a base.
But if the owner allows us, I think we can create a Pull Request in order to implemente locale as a new feature.

Hello, We would love to have your contribution to this repository. so feel free to create a PR for any bug fix or an enhancement.
Thanks

Added PR #36

Added in 1.0.1 PR #107 #36


Publishing updates to SQLINTBLOGLP for release on 20220203

Publishing updates to SQLINTBLOGLP for release on 20220203

Docs Build status updates of commit 788587e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

documentation/blog/MS-SQLINTBLOGLP/0b5e3a73-15fc-44b5-b5e6-7385b693115c.md
:white_check_mark:Succeeded

documentation/blog/MS-SQLINTBLOGLP/f5f55ea5-bb77-4448-a9c6-c9ba363d59dc.md
:white_check_mark:Succeeded

documentation/blog/MS-SQLINTBLOGLP/toc.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Accidentally including commas in Lineout Query End point results in nothing

I cutnpasted a coordinate from a pick into the Lineout Query's End point text box. It included commas. But, hitting 'Query' button results in nothing happening and is confusing. I think it would be best if it would just accept either a space ' ' or a comma ',' as a field separator. In fact, that would be great if all of VisIt text box inputs behaved that way. We often present text to users (that they are inclined to cutnpaste, which our text boxes cannot accept and that is probably a bad practice to continue). I would regard this later observation of VisIt handling of text outputs and inputs as a 'major irritation' though the particular case of this ticket is a minor one.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 1849
Status: Pending
Project: VisIt
Tracker: Bug
Priority: Normal
Subject: Accidentally including commas in Lineout Query End point results in nothing
Assigned to: -
Category: -
Target version: -
Author: Mark Miller
Start: 05/22/2014
Due date:
% Done: 0%
Estimated time:
Created: 05/22/2014 02:20 pm
Updated: 05/27/2014 08:10 pm
Likelihood: 3 - Occasional
Severity: 2 - Minor Irritation
Found in version: 2.7.1
Impact:
Expected Use:
OS: All
Support Group: Any
Description:
I cutnpasted a coordinate from a pick into the Lineout Query's End point text box. It included commas. But, hitting 'Query' button results in nothing happening and is confusing. I think it would be best if it would just accept either a space ' ' or a comma ',' as a field separator. In fact, that would be great if all of VisIt text box inputs behaved that way. We often present text to users (that they are inclined to cutnpaste, which our text boxes cannot accept and that is probably a bad practice to continue). I would regard this later observation of VisIt handling of text outputs and inputs as a 'major irritation' though the particular case of this ticket is a minor one.
Comments:
I believe most of our windows that accept multiple values in a single text box, will output an error message if attempting to parse the text results in an error.QvisLineoutQueryWidget currently does not issue the message (and possibly other query widgets as well).IIRC, VisIt either parses the QLineEdit text string with sscanf (as with QvisLineoutQueryWidget), or splits the string on spaces (See GuiBase::QStringToDoubles).

For this particular ticket, Lineout query definitely should print out a warning.
For the problem in general (not allowing commas in qlineedits lists of values), I think we should
audit our lineedit parsing, and use a consistent interface (like GUIBase::QStringToDoubles when we expect doubles).  Then modify that interface to allow commas.  For double/floats locale should be taken into account as some countries use commas where we use decimal points.


Enforce test ordering

The tests are run in what looks like a random order.  Would it be possible to enforce eg alphabetic order?  In theory this should make a difference; in practice some of the tests leave stuff behind and running them in random order makes debugging harder.

@trasz you might also want to file an issue in https://github.com/freebsd/kyua/


Make folder generation at code level

For now, the folders are placed manually for sensitivity analysis. We can check if the directory exists and create one at run-time. (Also check others that need pre-defined folder names)

This is implemented as well.


Keys falsely detected as unused

I have a project that includes a flutter package in a subfolder. This package is also localized and has its own arb files aside from the main app. The keys listed in the package are all used but they are listed as unused by translations_cleaner. I would expect either to properly detect them as used (in the package) or to have an option to ignore those or only search for arb files that belong to the package where the command runs from.

In the current state, I had not considered the case of a flutter package in a subfolder, I will look into this.

Same issue here, this is my solution:
In project_files.dart,
change
final dartFile = Glob("$path/lib/**.dart");
to
final dartFile = Glob("$path/**.dart");


Added archiving methods and token_expire parameter

Added methods from https://docs.pcloud.com/methods/archiving/.
Additionally I included token_expire parameter in the PyCloud class initializer. It allows user to change token lifespan and corresponds to the authexpire parameter in https://docs.pcloud.com/methods/intro/global_parameters.html.
(also it's my first contribution to open source, sorry if I'm doing something wrong)

Thanks @olokelo! Very well done!

Thanks @olokelo! Very well done!


Using "grant_power" action to grant powers that do not exist crashes the game

If the "grant_power" action attempts to grant a power that either does not exist or has errored, it will cause the game to crash.

This should now be fixed by https://github.com/apace100/apoli/pull/157


NGL.Superposition class not working

When I try to superpose structures using directly NGL.Superposition class:
var c1 = stage.compList[0].structure;
var c2 = stage.compList[1].structure;
var sup = NGL.Superposition(c1, c2);

I get an error:
Uncaught TypeError: this.prepCoords is not a function
    at Object.Superposition (superposition.js:49)
    at <anonymous>:1:15

Maybe missing new in from of NGL.Superposition?

You are absolutely right @fredludlow .  Thanks!


Make MqttDecoder settings configurable

MqttServerInitializer instantiates the netty MqttDecoder using its default constructor; the default value is used for maxBytesInMessage field. It makes not possible to decode messages larger that 8092 bytes; io.netty.handler.codec.DecoderException is thrown, with the followin message "too large message".
See https://github.com/netty/netty/issues/9983
Background: I'm using OPC UA PubSub with MQTT transport protocol and the size of meta frames exceeds this limit.

MqttServerInitializer instantiates the netty MqttDecoder using its default constructor; the default value is used for maxBytesInMessage field. It makes not possible to decode messages larger that 8092 bytes; io.netty.handler.codec.DecoderException is thrown, with the followin message "too large message".
See netty/netty#9983
Background: I'm using OPC UA PubSub with MQTT transport protocol, and the size of meta frames exceeds this limit.

Hi @dgyuri, thanks a lot for bringing this up.
This project was initially a PoC, and such cases were not taken into consideration while I was implementing the bridge.
The point you just raised makes total sense to me, but I will let @ppatierno and @kyguy take a look and decide.

This could make sense by adding mqtt.max.bytes.message configuration parameter and handling it. @dgyuri are you willing to contribute to have it?

This could make sense by adding mqtt.max.bytes.message configuration parameter and handling it. @dgyuri are you willing to contribute to have it?

Hi @dgyuri, are you up to take this?

Closed by #74


nodejs_20: 20.14.0 -> 20.15.0

Description of changes
https://github.com/nodejs/node/releases/tag/v20.15.0

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Cherry-picked a commit to account for the failing tests, see https://github.com/NixOS/nixpkgs/pull/313982#issuecomment-2181235552

Can you squash all your commits into one single commit?

You ticked that it builds on aarch64-darwin?  Before this update it won't build (#322145, example hydra build) and this update doesn't seem to fix that (tried locally).

It's possible that something else in master..staging-next broke this, of course.  (and you e.g. built atop master)

Yes you're right, I tried locally on top of master, then remembered I have to target staging for this package, and did not re-try the build after the rebase.

Not a problem.  I think it's usually better, as building against staging head would typically have a bad ratio of work/benefit.  (staging-next sometimes, but depends on timing...)

Though of course, it will be great if someone fixes the issue, even if not introduced by this update.

I think that's what https://github.com/NixOS/nixpkgs/pull/262124 is up to :)


Import and Export with parameterized DateTime format.

This is helpful if using different datetime formats during importing / exporting excel spreadsheets.

Awesome idea, thanks for adding this!


Incompatibility between redisson versions

Recently I have upgraded redisson version to 3.20.1 in a service called X (saves the data). A service called Y tries to read the data from ElasticCache using 3.17.1 redisson version. Unfortunately the parsing is failing and throwing below error while reading.
Another important use case is:
New redisson client (3.20.1) was unable to parse or read previously saved cache data (saved using redisson 3.17.1). This is the major use case where reading cache data is failing with same error.
org.redisson.client.RedisException: Unexpected exception while processing command
at org.redisson.command.CommandAsyncService.convertException(CommandAsyncService.java:331) ~[redisson-3.17.1.jar!/:3.17.1]
at org.redisson.command.CommandAsyncService.get(CommandAsyncService.java:118) ~[redisson-3.17.1.jar!/:3.17.1]
at org.redisson.RedissonObject.get(RedissonObject.java:82) ~[redisson-3.17.1.jar!/:3.17.1]
at org.redisson.RedissonBucket.get(RedissonBucket.java:135) ~[redisson-3.17.1.jar!/:3.17.1]
Redisson client should not vary in data format between version unless we change ElasticCache server. Not sure how this happened with redisson newer versions ?

Please read changelog before update. https://github.com/redisson/redisson/blob/master/CHANGELOG.md Default codec has been changed since 3.19.0 version.

yes. You need to specify it explicitly if you don't want to convert data stored by previous codec.

yes. You need to specify it explicitly if you don't want to convert data stored by previous codec.


Necessary to add the ability to work with git

magit?

Yes, magit is cool package!

Commit #dcb8fde


Deploy etcd exporter

rah I'm not used to "commiting the comment transaction" of github. Sorry for  the delay


 Or perhaps move the packages to an organization?

I've added you an @ranjanan. Let me know if there are others I should add.

Thanks @dcjones.

Cc @tkelman

@ranjanan https://github.com/dcjones/Loess.jl/blob/9643b2b27bf2ae83881ce3902009a9018401d719/REQUIRE#L2
EVERY TIME

Thanks for adding me @dcjones :)


avoidVar does not respect equality

several tests fail, including symbolic algebra, if ensuring(_ == x) is added.

Surfaced after making Induc for symbolic Naturals InducFuncLike in 1e18678eec92dd

The mistake in 1e18678 was silly and unrelated.

Many cases have been fixed, and were due to #194 including for free groups.
Another problem was the use of scala lambdas in Product Types, which were not recognized as equal unless they were equal objects.


orchestra/remote: add a method to create temporary directory

[ ] Delete the copy of PR branch pushed on ceph/teuthology after the PR is merged.

Equivalent of commit 5a667b81 on PR #29421.

@kshtsk
Since I am pretty close, I can do the same thing for mktemp() -- use coreutils mktemp instead of Python's tempfile.mktemp(). Would that be nice?

@kshtsk
Since I am pretty close, I can do the same thing for mktemp() -- use coreutils mktemp instead of Python's tempfile.mktemp(). Would that be nice?

yep, this would be nice

looks good, what about testing this code?

Ok. How are patches tested on teuthology?

I believe you need to run any basic testing where this part of code is used in the lab with your branch. Like, running teuthology-suite -t your_branch_name.
However, this method work now only for branches within ceph/teuthology. To make it working from custom repo, we need to patch teuthology.

Also, there can be some functional/system tests can be written additionally, since it requires 'ssh' server running. Though, there is nothing running like that on the jenkins, you can run it manually on your system.
I had some ideas, like running ssh on some specific port via docker. Not sure all this is a 100% requirement for your PR. Maybe logs of teuthology tests with running this code is enough, at least it should not break others tests.

To make it working from custom repo, we need to patch teuthology.

By custom repo, do you mean a fork? And can you elaborate on "we need to patch teuthology" part?

Would it be OK to push the PR branch on origin? I can use -t in that case.

To make it working from custom repo, we need to patch teuthology.

By custom repo, do you mean a fork? And can you elaborate on "we need to patch teuthology" part?

I mean your fork, yes. teuthology-suite only support teuthology-branch option which can be used for testing your changes, but it does not support teuthology-repo at the moment.

Would it be OK to push the PR branch on origin? I can use -t in that case.
I think yes, do not forget to clean it up after merging this PR :-)

Following is the traceback from the teuthology job -
2019-08-09T05:51:10.129 INFO:tasks.cephfs_test_runner:======================================================================
2019-08-09T05:51:10.129 INFO:tasks.cephfs_test_runner:ERROR: test_acls (tasks.cephfs.test_acls.TestACLs)
2019-08-09T05:51:10.129 INFO:tasks.cephfs_test_runner:----------------------------------------------------------------------
2019-08-09T05:51:10.129 INFO:tasks.cephfs_test_runner:Traceback (most recent call last):
2019-08-09T05:51:10.129 INFO:tasks.cephfs_test_runner:  File "/home/teuthworker/src/git.ceph.com_ceph-c_wip-rishabh-add-test-for-acls/qa/tasks/cephfs/xfstests_dev.py", line 7, in setUp
2019-08-09T05:51:10.129 INFO:tasks.cephfs_test_runner:    self.prepare_xfstests_dev()
2019-08-09T05:51:10.130 INFO:tasks.cephfs_test_runner:  File "/home/teuthworker/src/git.ceph.com_ceph-c_wip-rishabh-add-test-for-acls/qa/tasks/cephfs/xfstests_dev.py", line 19, in prepare_xfstests_dev
2019-08-09T05:51:10.130 INFO:tasks.cephfs_test_runner:    self.write_local_config()
2019-08-09T05:51:10.130 INFO:tasks.cephfs_test_runner:  File "/home/teuthworker/src/git.ceph.com_ceph-c_wip-rishabh-add-test-for-acls/qa/tasks/cephfs/xfstests_dev.py", line 47, in write_local_config
2019-08-09T05:51:10.130 INFO:tasks.cephfs_test_runner:    self.get_test_and_scratch_dirs_ready()
2019-08-09T05:51:10.130 INFO:tasks.cephfs_test_runner:  File "/home/teuthworker/src/git.ceph.com_ceph-c_wip-rishabh-add-test-for-acls/qa/tasks/cephfs/xfstests_dev.py", line 79, in get_test_and_scratch_dirs_ready
2019-08-09T05:51:10.130 INFO:tasks.cephfs_test_runner:    mountpoint=self.test_dir)
2019-08-09T05:51:10.130 INFO:tasks.cephfs_test_runner:  File "/home/teuthworker/src/git.ceph.com_ceph-c_wip-rishabh-add-test-for-acls/qa/tasks/cephfs/fuse_mount.py", line 35, in mount
2019-08-09T05:51:10.130 INFO:tasks.cephfs_test_runner:    return self._mount(mount_path, mount_fs_name, mountpoint)
2019-08-09T05:51:10.131 INFO:tasks.cephfs_test_runner:  File "/home/teuthworker/src/git.ceph.com_ceph-c_wip-rishabh-add-test-for-acls/qa/tasks/cephfs/fuse_mount.py", line 61, in _mount
2019-08-09T05:51:10.131 INFO:tasks.cephfs_test_runner:    timeout=(15*60)
2019-08-09T05:51:10.131 INFO:tasks.cephfs_test_runner:  File "/home/teuthworker/src/git.ceph.com_git_teuthology_wip-rishabh-remote-add-mkdtemp/teuthology/orchestra/remote.py", line 205, in run
2019-08-09T05:51:10.131 INFO:tasks.cephfs_test_runner:    r = self._runner(client=self.ssh, name=self.shortname, **kwargs)
2019-08-09T05:51:10.131 INFO:tasks.cephfs_test_runner:  File "/home/teuthworker/src/git.ceph.com_git_teuthology_wip-rishabh-remote-add-mkdtemp/teuthology/orchestra/run.py", line 437, in run
2019-08-09T05:51:10.131 INFO:tasks.cephfs_test_runner:    r.wait()
2019-08-09T05:51:10.131 INFO:tasks.cephfs_test_runner:  File "/home/teuthworker/src/git.ceph.com_git_teuthology_wip-rishabh-remote-add-mkdtemp/teuthology/orchestra/run.py", line 162, in wait
2019-08-09T05:51:10.132 INFO:tasks.cephfs_test_runner:    self._raise_for_status()
2019-08-09T05:51:10.132 INFO:tasks.cephfs_test_runner:  File "/home/teuthworker/src/git.ceph.com_git_teuthology_wip-rishabh-remote-add-mkdtemp/teuthology/orchestra/run.py", line 184, in _raise_for_status
2019-08-09T05:51:10.132 INFO:tasks.cephfs_test_runner:    node=self.hostname, label=self.label
2019-08-09T05:51:10.132 INFO:tasks.cephfs_test_runner:CommandFailedError: Command failed on smithi102 with status 1: 'mkdir -- /tmp/tmp.ZmXKYe1MSstest'
2019-08-09T05:51:10.132 INFO:tasks.cephfs_test_runner:

The error occurred in call within this call[1] which implies that the call to mkdtemp() was successful[2] [3].
Link to the teuthology job - http://pulpito.front.sepia.ceph.com/rishabh-2019-08-09_05:25:14-fs-wip-rishabh-add-test-for-acls-distro-basic-smithi/4202978/

@batrick @kshtsk Cam you please merge the PR and/or reply to the previous comment? Thanks!

@kshtsk @batrick Thanks!


How about flatten the text path with usvg?

https://github.com/linebender/vello_svg/blob/cf6fe5502e1b6701a1dd4e8dc20f706a49d6a47c/src/lib.rs#L262-L264
Similarly as:
https://github.com/RazrFalcon/resvg/blob/ac7e7d0c40eb22dae19139f36ce28ad16e123db4/crates/resvg/src/render.rs#L45

This isn't implemented yet, but is on the TODO list. :)


nearcore: 1.28.0 -> 1.28.1

Description of changes
https://github.com/near/nearcore/releases/tag/1.28.1

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Neard just had an intermediate release, that we need to push before 1.29.0.


feat (src/index. js -> fs.writeFileSync) => remove white blanks with trim() function

This is our first contribution to the Open Source community !

The ci/cd problem does not seems link to this. I will merge it and look into it later on. Thanks for you contribution!


Subgraph shows wrong rewards data for epoches

Subgraph shows wrong rewards data for epochs.
Query:
{
  epoch(id: 14){
    id
    signalledTokens
    stakeDeposited
    queryFeeRebates
    totalRewards
    totalIndexerRewards
    totalDelegatorRewards
  }
}

Response
{
  "data": {
    "epoch": {
      "id": "14",
      "queryFeeRebates": "0",
      "signalledTokens": "0",
      "stakeDeposited": "226603162385070786571647",
      "totalDelegatorRewards": "532407296752233258035720",
      "totalIndexerRewards": "532407296752233258035720",
      "totalRewards": "531715261692226026250400"
    }
  }
}

thanks, I figured out what the issue is here, there is some extra addition. will tag the PR in here when it is fixed!

https://github.com/graphprotocol/graph-network-subgraph/pull/73/files fixed

https://github.com/graphprotocol/graph-network-subgraph/pull/73/files fixed


Vectris implementation in Rust + Tailwind CSS + Leptos.

Here's how it's looking, after some manual population of the matrix.
Nested reactivity isn't working at the level of the matrix, so I still have to figure that one out.
More to come.


Fix some doc generation warnings

This fixes the various warnings that come from the initial phase of reading the doc files. There are still some warnings during the writing the output phase.

10.0.x cherry-pick:
https://github.com/apache/trafficserver/pull/11420


MIgrate the Davies Project

See https://github.com/pulibrary/davies_project

I have tried another approach using CollectionBuilder; at Esmé's suggestion I have built it in a different GitHub repository.


[IMPAC-751] Fixed Multi-Company Ordering

@cesar-tonnoir
I was able to order the settings internally in the directives -- however, the widget-specific data was not uniform enough to do this at the directive level. Since lots of widgets reuse the same html file, I did not have to add that many orderBys.

@xaun Let me know what you think.
In translateCategories, I made an array of all translate promises, and then called Promises.all(translationPromises). So that only after each promise is fulfilled, sortData is called.

@xaun I moved initDates out from the if block. #initDates depends on w.metadata which is populated regardless of whether or not impac's requests were successful.

@iseessel looks good, can you rebase and fixup your "formatting" and "clean up" commits. It's best to only push commits to remote that provide useful chunks of history. For example when Im working I may make quick commits to save my progress, and try things out, but for a PR, I use rebase to clean up my commit history.
Not sure if you know, but during rebase, you can even re-order your commits, saving them in that order, or then squashing them up into previous commits. If you use vim as your rebase editor, to move a line it is :m2 (in visual mode), the number being the index of the line. This is useful as maybe I realised I need to make a cleanup for a commit I made previously, its more relevant to squash that cleanup into a commit 4 commits ago.

@xaun
Thanks for the help! Let me know how this looks. Tried to keep it across several commits as there were a lot of changes to different parts.

@iseessel you'll need to merge release/1.6.9 into your branch or rebase on-top of release/1.6.9, and resolve the conflicts

@xaun  We are merging these changes onto 1.6.9 now?


Support B3 headers in OTEL propagation

Problem
Tracing is instrumental in supported distributed systems such as Knative Eventing, Kafka, etc.   Many systems (including Istio), by default use B3 (multi) headers.   Kafka Broker appears to be configured for only W3C headers.   Traces involving Knative Eventing stop when it hits the broker or only start after messages hit other systems, you don't get an end-to-end trace when using B3
Persona:
Which persona is this feature for?

Producer
Consumer

Exit Criteria
Kafka Broker propagates B3 headers (in addition to W3C)
Time Estimate (optional):
How many developer-days do you think this may take to resolve?
Additional context (optional)
Add any other context about the feature request here.

FYI, I added
          value: b3

to the receiver and dispatcher deployments to no effect.

Thanks for reporting!
We should be able to easily support it by injecting a propagator in https://github.com/knative-sandbox/eventing-kafka-broker/blob/67b507aeee9f3f88864a98f2be2dc56194051e71/data-plane/core/src/main/java/dev/knative/eventing/kafka/broker/core/tracing/OpenTelemetryTracer.java#L48
and use it in place of:

https://github.com/knative-sandbox/eventing-kafka-broker/blob/67b507aeee9f3f88864a98f2be2dc56194051e71/data-plane/core/src/main/java/dev/knative/eventing/kafka/broker/core/tracing/OpenTelemetryTracer.java#L67
https://github.com/knative-sandbox/eventing-kafka-broker/blob/67b507aeee9f3f88864a98f2be2dc56194051e71/data-plane/core/src/main/java/dev/knative/eventing/kafka/broker/core/tracing/OpenTelemetryTracer.java#L166
https://github.com/knative-sandbox/eventing-kafka-broker/blob/67b507aeee9f3f88864a98f2be2dc56194051e71/data-plane/core/src/main/java/dev/knative/eventing/kafka/broker/core/tracing/OpenTelemetryTracer.java#L183

/good-first-issue

/assign

@arghya88 No need to fix it here, we're planning to use the new module directly from vertx https://github.com/eclipse-vertx/vertx-tracing/pull/22
We'll just need to configure the tracer when using the new module

Now that this is merged https://github.com/eclipse-vertx/vertx-tracing/pull/22, we're going to implement this as soon as we update to vert.x 4.1 https://github.com/knative-sandbox/eventing-kafka-broker/issues/784

Just an heads up here. Once we merge #784, we need to import the sdk extensions and add this trace propagator: https://github.com/open-telemetry/opentelemetry-java/blob/50408d499f85d5761d0a5ed9bf9d77d5ff01fff5/extensions/trace-propagators/src/main/java/io/opentelemetry/extension/trace/propagation/B3Propagator.java

What is the support plan for the OTEL stuff at the vertx side long term? We are heavily depend on vertx for most stuff.

What is the support plan for the OTEL stuff at the vertx side long term?

Vert.x is going to support the vertx-opentelemetry integration, that is the implementation of the Tracing SPI, the rest is on us :smile:

We heavily depend on vertx for most stuff, should not we use the otel java lib (directly)?

Why should we? The vertx-opentelemetry project is a contribution back to them started from this project, where we can help the greater vert.x community to use opentelemetry, and we can also profit back. There's no reason, nor any need, for us to do a custom implementation of the Tracing SPI. We use today vertx-opentelemetry, it works fine and fits our use case, so I don't see any need to change it.

Also should not we add this to the effort for migrating Eventing to OTEL?

For this specific eventing-kafka-broker project, there isn't anything left to do about this. Except perhaps this issue, which is not really related to otel but in general to support more tracing functionalities.

Vert.x is going to support the vertx-opentelemetry integration
There's no reason, nor any need, for us to do a custom implementation of the Tracing SPI.
I am referring to the first part.  We should minimize deps and from what I see across all Knative components there are different client libs, which makes integration life worse. From what I see we implemented the OTEL integration :)

Honestly, I don't get what are you referring to :smile: The opentelemetry library we use is the official one from the opentelemetry team.
What we do in this project, data plane wise, has nothing to do with the rest of knative, since we use Java, so we obviously have a different stack with different libs etc. In other words, if we would use opencensus here, nothing would change anyway because the java opencensus library is different from the golang opencensus library.

We should minimize deps (if possible)

I disagree, when talking about official vertx dependencies of the vertx stack. Those are well tested and fits together with vertx-core, so everything in there is good for us to use.

Links to https://github.com/open-telemetry/opentelemetry-java/issues/3364

@treyhyde your goal is to emit b3 headers, or you just want the broker to recognize them and then still emit tracecontext?

/assign

@treyhyde your goal is to emit b3 headers, or you just want the broker to recognize them and then still emit tracecontext?

The basic goal to propagate all tracing headers so we have basic insights into how the app is working.   B3 is the defacto standard ... still (ignoring ACTUAL standards) as it is the default in sooo many places due to its long tenure.  If I pass B3 I expect B3 on the other side.  If I pass W3C, I expect W3C on the other side.    In the same deployment I could easily see different apps using different header types and I would want all of them to work.  (though, in this case, we use b3 universally since that is the Istio default).     We switched to the kafka-channel with the standard broker because this worked out of the box.


Add I18N support for Ava tests

Please verify the following:

[x] Everything works on iOS/Android
[x] ignite-base ava tests pass
[x] fireDrill.sh passed

Describe your PR
Updates Setup for Ava tests to add support for I18n interpolated strings

Adds support for I18N in unit tests. Invaluable for when a test depends on interpolated i18n .t('foo', {someValue})


Write support for Swift 5

Support Swift 5 locally and work on test coverage as a separate issue.

Before closing this, please add something to the native release notes

Added mention in native release note and highlight in gradle/gradle release notes.


Connection refused connecting from another container

Description
I'm building a Testcontainers' solution to test my java Quarkus service.
Up until now, I have successfully created 4 running docker containers:

Generic Container running my service's image (let's call it Service A)
Generic container running Azurite's
Mock server container running a mock of an external API service
Generic container running Event Hub emulator's

All of these containers are running in the same network.
The issue, now, is that my service is not able to connect to the event hub emulator's container.
I have tried all different kind of options for the connection string:

Endpoint=sb://localhost;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;
Endpoint=sb://host.docker.internal;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;
"Endpoint=sb://" + eventHubIpAddress + ";SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;"
Endpoint=sb://eventhubs-emulator;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;

I even removed the emulator and azurite from being managed by Testcontainers and just ran docker compose -f docker/docker-compose.yaml up -d, re-adapted the configuration for the Testcontainers' containers. I even added them to the same network of the emulator, but nothing works. I always get connection refused.
Logs
[com.azu.cor.amq.imp.han.ConnectionHandler] (reactor-executor-3) {"az.sdk.message":"onTransportError","connectionId":"MF_3002fd_1723802485997","errorCondition":"proton:io","errorDescription":"Connection refused","hostName":"localhost"}
[com.azu.cor.amq.imp.ReactorConnection] (reactor-executor-3) {"az.sdk.message":"Error occurred while processing connection state.","exception":"Connection refused, errorContext[NAMESPACE: localhost. ERROR CONTEXT: N/A]","connectionId":"MF_3002fd_1723802485997"}

Desktop

OS: MacOS

Image Platform-Architecture Used

Linux-arm64

Docker Version

Docker version 24.0.7, build afdd53b

Arguments && Environment variables to start Emulator

ACCEPT_EULA: Y
CONFIG_PATH: ./config.json

Emulator Launch Method

Using Testcontainers' Generic Container

Event Hub Emulator
this.eventHubContainer = new GenericContainer<>("mcr.microsoft.com/azure-messaging/eventhubs-emulator:1.2.4-preview-arm64")
                .withCreateContainerCmdModifier(cmd -> cmd.withName("eventhubs-emulator"))
                .withNetworkAliases("eventhubs-emulator")
                .withExposedPorts(5672)
                .withNetwork(this.network)
                .withEnv("BLOB_SERVER", "azurite")
                .withEnv("METADATA_SERVER", "azurite")
                .withEnv("ACCEPT_EULA", "Y")
                .withCopyToContainer(MountableFile.forClasspathResource("config.json"), "/Eventhubs_Emulator/ConfigFiles/Config.json")  // Copy config.json
                .waitingFor(Wait.forListeningPort().withStartupTimeout(Duration.ofMinutes(2)));
this.eventHubContainer.start();

Service A
this.serviceA = new GenericContainer<>(FILTER_STREAM_IMAGE_NAME)
                .withCreateContainerCmdModifier(cmd -> cmd.withName("serviceA"))
                .withNetwork(this.network)
                .withExposedPorts(8080)
                .withExposedPorts(5005)
                .withEnv("quarkus.rest.client.filter.management-service.url".replace(".", "_").toUpperCase(), "http://external-api:1080")
                .withEnv("EVENT_HUB_CONNECTION_STRING", "Endpoint=sb://localhost;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;")
                .withEnv("BLOB_STORAGE_CONNECTION_STRING", String.format(BLOB_STORAGE_CONNECTION_STRING, "azurite", azuriteContainer.getMappedPort(10000)))
                .withStartupTimeout(Duration.ofMinutes(2))
                .withLogConsumer(new Slf4jLogConsumer(log))
                .withNetwork(this.network);
this.serviceA.start();

Expected Behaviour
Service A's container should successfully connect to Event Hub Emulator's container
Actual Behaviour
Service A's container isn't able to connect to Event Hub Emulator's container (connection refused)

@rjvq85 ; can you provide more details around :

Logs from EH Emulator container. (Console & File Logs)
SDK version used in Application A to interact with Event-Hub.

Hi @krishankumar95,
Thanks!
Sure, here it is:
1. Logs
info: a.a.aap[0]
      Emulator Service is Launching On Platform:CBL-Mariner/Linux,Arm64
info: a.a.aap[0]
      Instantiating service components
info: a.a.aap[0]
      Creating namespace, entities and consumer groups
info: a.a.aaw[0]
      Emulator is launching with config : {"LoggingConfig":{"Type":"File"},"NamespaceConfig":[{"Type":"EventHub","Name":"emulatorns1","Entities":[{"Name":"eh1","PartitionCount":2,"ConsumerGroups":[{"Name":"eh1-consumer"},{"Name":"eh1-consumer-intest"},{"Name":"$default"}]},{"Name":"eh2","PartitionCount":2,"ConsumerGroups":[{"Name":"eh2-consumer"},{"Name":"eh2-consumer-intest"},{"Name":"$default"}]},{"Name":"process-result","PartitionCount":2,"ConsumerGroups":[{"Name":"consumer-service"},{"Name":"consumer-dashboard"},{"Name":"$default"}]}]}]}
info: a.a.aap[0]
      Emulator Service is Successfully Up! ; Use connection string : "Endpoint=sb://localhost;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;"

/home/app/EmulatorLogs:
2024-08-16 13:55:44.227 +00:00 [WRN] <Trc Id="60006" Ch="Debug" Lvl="Warning" Kw="1000000000011110" UTC="2024-08-16T13:55:44.227Z" Msg="An exception was handled at TenantCacheComponent.OnEndRefresh. Exception message ExceptionId: e68e7d28-1229-48ab-bd2b-69a087770691-System.NullReferenceException: Object reference not set to an instance of an object.
   at a.a.aax.z(IAsyncResult)." />
2024-08-16 13:55:44.243 +00:00 [WRN] <Trc Id="60000" Ch="Operational" Lvl="Warning" Kw="4000000000011110" UTC="2024-08-16T13:55:44.243Z" Msg="Exception occurred while creating performance counters. Exception message &apos;System.PlatformNotSupportedException: Performance Counters are not supported on this platform.
   at System.Diagnostics.PerformanceData.CounterSet..ctor(Guid providerGuid, Guid counterSetGuid, CounterSetInstanceType instanceType)
   at h.hM.ad()
   at h.hM.ab()
   at h.hh.A(PerformanceCounterLevel)&apos;." />
2024-08-16 13:55:45.254 +00:00 [WRN] <Trc Id="60000" Ch="Operational" Lvl="Warning" Kw="4000000000011110" UTC="2024-08-16T13:55:45.254Z" Msg="Exception occurred while creating performance counters. Exception message &apos;System.PlatformNotSupportedException: Performance Counters are not supported on this platform.
   at System.Diagnostics.PerformanceData.CounterSet..ctor(Guid providerGuid, Guid counterSetGuid, CounterSetInstanceType instanceType)
   at h.hK.ab()
   at h.hh.A(PerformanceCounterLevel)&apos;." />
2024-08-16 13:55:45.269 +00:00 [WRN] <Trc Id="60000" Ch="Operational" Lvl="Warning" Kw="4000000000011110" UTC="2024-08-16T13:55:45.269Z" Msg="Exception occurred while creating performance counters. Exception message &apos;System.PlatformNotSupportedException: Performance Counters are not supported on this platform.
   at System.Diagnostics.PerformanceData.CounterSet..ctor(Guid providerGuid, Guid counterSetGuid, CounterSetInstanceType instanceType)
   at h.hK.ab()
   at h.hh.A(PerformanceCounterLevel)&apos;." />
2024-08-16 13:55:45.272 +00:00 [WRN] <Trc Id="60006" Ch="Debug" Lvl="Warning" Kw="1000000000011110" UTC="2024-08-16T13:55:45.271Z" Msg="An exception was handled at TenantCacheComponent.OnEndRefresh. Exception message ExceptionId: 9f204705-e8d3-419f-b95e-fd9452f700f1-System.NullReferenceException: Object reference not set to an instance of an object.
   at a.a.aax.z(IAsyncResult)." />
2024-08-16 13:55:45.343 +00:00 [WRN] <Trc Id="60000" Ch="Operational" Lvl="Warning" Kw="4000000000011110" UTC="2024-08-16T13:55:45.343Z" Msg="Exception occurred while creating performance counters. Exception message &apos;System.PlatformNotSupportedException: Performance Counters are not supported on this platform.
   at System.Diagnostics.PerformanceData.CounterSet..ctor(Guid providerGuid, Guid counterSetGuid, CounterSetInstanceType instanceType)
   at h.hp.ac()
   at h.hp.ab()
   at h.hh.A(PerformanceCounterLevel)&apos;." /

These were the only logs I found.
2. SDK

com.azure:azure-core-amqp:2.9.0
com.azure:azure-messaging-eventhubs:5.18.0
com.azure:azure-messaging-eventhubs-checkpointstore-blob:1.19.0
Quarkus 3.8.3
Java 17

@rjvq85 ; For interacting with EH Emulator please use the SDK version >=5.18.6. Any version prior will not work.
Reference : SDK Changelog

@krishankumar95 thank you. I'm no longer getting connection refused after updating to v.5.18.6.
However, when trying to connect to the emulator (and subsequently trying to send a message) I get this error:
[main] INFO  com.azure.messaging.eventhubs.EventHubClientBuilder - {"az.sdk.message":"Emitting a single connection.","connectionId":"MF_7f4bcd_1724053418140"}
[main] DEBUG com.azure.core.amqp.implementation.ReactorConnection - {"az.sdk.message":"getConnectionState","connectionId":"MF_7f4bcd_1724053418140","state":"UNINITIALIZED"}
[main] INFO  com.azure.messaging.eventhubs.implementation.EventHubConnectionProcessor - {"az.sdk.message":"Setting next AMQP channel.","entityPath":"eventhub1"}
[main] INFO  com.azure.core.amqp.implementation.ReactorConnection - {"az.sdk.message":"Creating and starting connection.","connectionId":"MF_7f4bcd_1724053418140","hostName":"eventhubs-emulator","port":5672}
[main] INFO  com.azure.core.amqp.implementation.ReactorExecutor - {"az.sdk.message":"Starting reactor.","connectionId":"MF_7f4bcd_1724053418140"}
[reactor-executor-1] INFO  com.azure.core.amqp.implementation.handler.ConnectionHandler - {"az.sdk.message":"onConnectionInit","connectionId":"MF_7f4bcd_1724053418140","hostName":"eventhubs-emulator","namespace":"eventhubs-emulator"}
[reactor-executor-1] INFO  com.azure.core.amqp.implementation.handler.ReactorHandler - {"az.sdk.message":"reactor.onReactorInit","connectionId":"MF_7f4bcd_1724053418140"}
[reactor-executor-1] INFO  com.azure.core.amqp.implementation.handler.ConnectionHandler - {"az.sdk.message":"onConnectionLocalOpen","connectionId":"MF_7f4bcd_1724053418140","hostName":"eventhubs-emulator"}
[reactor-executor-1] INFO  com.azure.core.amqp.implementation.handler.ConnectionHandler - {"az.sdk.message":"onConnectionBound","connectionId":"MF_7f4bcd_1724053418140","hostName":"eventhubs-emulator"}
[reactor-executor-1] WARN  com.azure.core.amqp.implementation.handler.ConnectionHandler - {"az.sdk.message":"onTransportError","connectionId":"MF_7f4bcd_1724053418140","errorCondition":"proton:io","hostName":"eventhubs-emulator"}
[reactor-executor-1] DEBUG com.azure.core.amqp.implementation.ReactorConnection - {"az.sdk.message":"Disposing of active sessions due to error.","connectionId":"MF_7f4bcd_1724053418140"}
[reactor-executor-1] INFO  com.azure.core.amqp.implementation.ReactorConnection - {"az.sdk.message":"Disposing of ReactorConnection.","connectionId":"MF_7f4bcd_1724053418140","isTransient":false,"isInitiatedByClient":false,"shutdownMessage":"errorContext[NAMESPACE: eventhubs-emulator. ERROR CONTEXT: N/A]"}
[reactor-executor-1] DEBUG com.azure.core.amqp.implementation.ReactorConnection - {"az.sdk.message":"Closed CBS node.","connectionId":"MF_7f4bcd_1724053418140","signalType":"onComplete"}
[reactor-executor-1] DEBUG com.azure.core.amqp.implementation.ReactorConnection - {"az.sdk.message":"Scheduling closeConnection work.","connectionId":"MF_7f4bcd_1724053418140"}
[reactor-executor-1] DEBUG com.azure.core.amqp.implementation.ReactorConnection - {"az.sdk.message":"Closed reactor dispatcher.","connectionId":"MF_7f4bcd_1724053418140","signalType":"onComplete"}
[reactor-executor-1] DEBUG com.azure.core.amqp.implementation.ReactorConnection - {"az.sdk.message":"Closed management nodes.","connectionId":"MF_7f4bcd_1724053418140","signalType":"onComplete"}
[reactor-executor-1] INFO  com.azure.core.amqp.implementation.handler.ConnectionHandler - {"az.sdk.message":"onTransportClosed","connectionId":"MF_7f4bcd_1724053418140","errorCondition":"proton:io","hostName":"eventhubs-emulator"}
[reactor-executor-1] INFO  com.azure.core.amqp.implementation.handler.GlobalIOHandler - {"az.sdk.message":"onTransportClosed","connectionId":"MF_7f4bcd_1724053418140","hostName":"eventhubs-emulator"}
[reactor-executor-1] INFO  com.azure.core.amqp.implementation.handler.ConnectionHandler - {"az.sdk.message":"onConnectionUnbound","connectionId":"MF_7f4bcd_1724053418140","hostName":"eventhubs-emulator","state":"ACTIVE","remoteState":"UNINITIALIZED"}
[reactor-executor-1] INFO  com.azure.core.amqp.implementation.ReactorConnection - {"az.sdk.message":"Closing executor.","connectionId":"MF_7f4bcd_1724053418140"}
[reactor-executor-1] INFO  com.azure.core.amqp.implementation.handler.ConnectionHandler - {"az.sdk.message":"onConnectionLocalClose","connectionId":"MF_7f4bcd_1724053418140","hostName":"eventhubs-emulator"}
[reactor-executor-1] INFO  com.azure.core.amqp.implementation.ReactorExecutor - {"az.sdk.message":"Processing all pending tasks and closing old reactor.","connectionId":"MF_7f4bcd_1724053418140"}
[reactor-executor-1] DEBUG com.azure.core.amqp.implementation.ReactorExecutor - {"az.sdk.message":"Had more tasks to process on reactor but it is shutting down.","connectionId":"MF_7f4bcd_1724053418140"}
[reactor-executor-1] INFO  com.azure.core.amqp.implementation.ReactorDispatcher - {"az.sdk.message":"Reactor selectable is being disposed.","connectionId":"MF_7f4bcd_1724053418140"}
[reactor-executor-1] INFO  com.azure.core.amqp.implementation.ReactorConnection - {"az.sdk.message":"onConnectionShutdown. Shutting down.","connectionId":"MF_7f4bcd_1724053418140","isTransient":false,"isInitiatedByClient":false,"shutdownMessage":"connectionId[MF_7f4bcd_1724053418140] Reactor selectable is disposed.","namespace":"eventhubs-emulator"}
[reactor-executor-1] DEBUG com.azure.core.amqp.implementation.ReactorExecutor - {"az.sdk.message":"Completing close and disposing scheduler. Finished processing pending tasks.","connectionId":"MF_7f4bcd_1724053418140"}
[reactor-executor-1] WARN  com.azure.core.amqp.implementation.ReactorConnection - {"az.sdk.message":"Error occurred while processing connection state.","exception":"errorContext[NAMESPACE: eventhubs-emulator. ERROR CONTEXT: N/A]","connectionId":"MF_7f4bcd_1724053418140"}
com.azure.core.amqp.exception.AmqpException: errorContext[NAMESPACE: eventhubs-emulator. ERROR CONTEXT: N/A]

The connection string is Endpoint=sb://eventhubs-emulator;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;. If I use host.docker.internal I get the same error and if I use localhost I get connection refused again.
This first warning:
[reactor-executor-1] WARN  com.azure.core.amqp.implementation.handler.ConnectionHandler - {"az.sdk.message":"onTransportError","connectionId":"MF_7f4bcd_1724053418140","errorCondition":"proton:io","hostName":"eventhubs-emulator"}

Doesn't really show much detail. I've also tried to find the issue by debugging the code that sends the message but there isn't any specific error message.

Update: this error occurs when I try to send a message from a client that I create in the host machine. Because of this I'd expect that I could connect to event hub with the standard connection string Endpoint=sb://localhost;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true; since I expose all the necessary ports in the docker-compose.
I don't see any explicit error that could point me into any direction.

Update:
I was looking at the python example and I tried to run the simple_sender and simple_receiver locally and it worked.
I have then tried to replicate the methods using Java's SDK with
private static void sendMsg() {
      final String connectionString = "Endpoint=sb://localhost;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;";
      final String eventHubName = "eh1";

      final EventHubProducerClient producerClient = new EventHubClientBuilder()
              .connectionString(connectionString, eventHubName)
              .buildProducerClient();
      final CreateBatchOptions createBatchOptions = new CreateBatchOptions();
      createBatchOptions.setPartitionId("1");
      EventDataBatch eventDataBatch = producerClient.createBatch(createBatchOptions);

      final Random random = new Random();
      final String eventMessageLeft = "{\"direction_data\":{\"direction\": \"left\"}}";
      final String eventMessageRight = "{\"direction_data\":{\"direction\": \"right\"}}";

      for (int i = 0; i < 10; i++) {
          final String message = (random.nextInt(100) % 2 == 0) ? eventMessageRight : eventMessageLeft;
          final EventData eventData = new EventData(message);
          if (eventDataBatch.tryAdd(eventData)) {
              producerClient.send(eventDataBatch);
              System.out.println("Sent message: " + message);

              eventDataBatch = producerClient.createBatch(createBatchOptions);
              if (!eventDataBatch.tryAdd(eventData)) {
                  throw new IllegalArgumentException("Event is too large for an empty batch. Max size: "
                                                     + eventDataBatch.getMaxSizeInBytes());
              }
              if (eventDataBatch.getCount() > 0) {
                  producerClient.send(eventDataBatch);
              }
          }
      }

      producerClient.close();
      System.out.println("All messages sent.");
  }

and
private static void receiveMsg() {
        final String connectionString = "Endpoint=sb://localhost;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;";
        final String eventHubName = "eh1";
        final String consumerGroup = "cg1";

        final EventHubConsumerClient cc = new EventHubClientBuilder()
                .connectionString(connectionString, eventHubName)
                .consumerGroup(consumerGroup).buildConsumerClient();

        cc.receiveFromPartition("1", 10, EventPosition.earliest())
                .forEach(event -> {
                    final EventData eventData = event.getData();
                    System.out.println("Received event: " + eventData.getBodyAsString());
                });

        cc.close();
    }

and it worked. The connection string is the same. I don't really understand what's changed, because I have gone back to the original config.json, but after successfully testing it I re-tested with my own config.json (multiple entities) and still works.
I will close the issue.
Thanks.


git-splits contains carriage-return characters

which leads to arcane errors like
fatal: 'splits' appears to be a git command, but we were not
able to execute it. Maybe git-splits is broken?

An alternative fix on unix/osx is to run dos2unix to remove the dos style line endings.
e.g. on osx (using homebrew to install dos2unix)
brew install dos2unix
dos2unix $(which git-splits)

yes, thanks . i think more than a few issues/PRs mentioned this :) . fixed in latest release


chore(localization): update strings in registration page (resolves #792)

See #792 for details.

@chosww what page did you update? Sorry the original figma link doesn't seem to work anymore!


(PDB-1179) Simplify start-puppetdb and webapp building

This commit cleans up the syntax of the starting of puppetdb and the
building of puppetdb webapplications with an authorizer. As new
webservers are added into the puppetdb project it is desirable to have
clean, standardized examples of build-app functions and configuration
manipulation. This commit also adds the authorizer, built from the
certificate-whitelist config, to the shared-globals of the
PuppetDBServer so that other apps need not build the authorizer from
scratch again.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/869/

Failure was just a trasient ^

just a minor note about some prexisting stuff. This looks good to me otherwise.

@wkalt comments addressed!

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/881/

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/888/

@pljenkinsro retest this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/890/

+1 will merge when the pipeline has be cleared


final update

removed the cgmanifest file per Don's request

[ ] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[ ] Title summarizes what is changing.
[ ] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).

Codecov Report

:exclamation: No coverage uploaded for pull request base (release-2021.06@bde5192). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head 8c3dfb7 differs from pull request most recent head 8d25c26. Consider uploading reports for the commit 8d25c26 to get more accurate results

@@                Coverage Diff                @@
##             release-2021.06   #6176   +/-   ##
=================================================
  Coverage                   ?     72%
=================================================
  Files                      ?     398
  Lines                      ?   26831
  Branches                   ?    3943
=================================================
  Hits                       ?   19376
  Misses                     ?    5808
  Partials                   ?    1647


CocoaPods support. Old SDK support

Added CocoaPods Podfile
Added GitHub Actions workflows for testing and deploying.
Switched it to the older Swift 5.7 and SDKs. I like the StaticBigInt constructor too, but it's supported only in the latest SDK versions :( More practical is String constructors for now.
Tested on Linux (and it works!)

I have one proposal.
I can split this lib into 3 pods. It will allow it to use the same import logic as SPM. Workflow scripts though will be crazy.
What do you think? Because right now you need #if !COCOAPODS everywhere

It sounds better. I prefer CocoaPods as far in the background as possible. In layman's terms, does that mean 3 pod files?

Yes. It will have 3 Podfiles which will be published on each release. I already added them in the branch: https://github.com/ypopovych/Numberick/tree/pods-swift57

Closed in favor of: https://github.com/oscbyspro/Numberick/pull/56


Adding implementation of isinstance.

I've only checked this for simple cases to get the discussion rolling.
We need to think of cases that we think might break it and even if it doesn't then that is the set of things we can test for.
Both individual and tuples of types are supported.

Thanks for the starter patch @DrTodd13, @guilhermeleobas is taking a look at how to extend this etc, thanks @guilhermeleobas!

@guilhermeleobas implemented this fully in https://github.com/numba/numba/pull/7244, closing as complete. Thanks again for the initial ideas @DrTodd13.


[Removal]:

Hotspot Name
Sneaky Cyan Swan
Hotspot b58 Address
11273Lqh4dL59TSKMqrvq5qXMPMDVHi67wnzhfaMUZpERjYPbJWi
Discord Handle
No response
Hotspot Manufacturer
Sensecap
Removal Reason
This is a true and legit sensecap Hotspot and there is no true reason to remove it from the map
Modifications
No
Extra forwarders
No
Extra antennas
No
Additional Information
Hello,
My revenue is below normal and the antennae is indoor so I don't understand why a stupid person would report me as illegal.
Actually he reported the whole block and area.
I appreciate to remove it as we own almost 4 devices in the region .

I also agree in this case that the HS should be removed.
Added PR and requested removal due to the local area's topology and multi HS cluster.

I also agree in this case that the HS should be removed. Added PR and requested removal due to the local area's topology and multi HS cluster.

Hello 6Corner,We own 4 hotspots in this region and all of it is legit and physical indoor anteana .Please look at the revenue it is very low as some devices even make 1.3 HNT .I appreciate to remove them from the deny list .If needed I can provide all proof and photos that show these devices.
We are completly legit and placing us on the deny list is not the good at all .


Bulk remove pages fails after 8 pages

In my app, there is a functionality that allows people to "split" a long PDF into two PDFs.
The way it currently works is as follows:

User scrolls through the PDF, and selects the split point. Everything from that point and before will be extracted into a new PDF
Load the PDF, and create an array of every page that needs removing from the source. (e.g. if we make the split point Page 5, the array will be [0 , 1, 2, 3, 4].

This is the code:
// Initiate PDFDocument object
      let pdf = await PDFDocument.create();

      // Now load into a PDFDocument object
      const file = await readFileAsync(filename);

      const source = await PDFDocument.load(file);

       // Make an array of all pages to extract
      let newPages = [];
      for (i = 0; i < splitPoint; i++) {
        newPages.push(i);
      }

      // Copy those pages to a new PDF
      const copiedPages = await pdf.copyPages(source, newPages);
      copiedPages.forEach(page => pdf.addPage(page));
      const newEntry = await pdf.save();

      // Now remove pages from the source document and save back
      newPages.forEach(page => {
        source.removePage(0);
      });
      const newSource = await source.save();

Whenever the newPages array is greater than 8, I always get this error - regardless of the PDF. By this point I have already error checked to see that the "split point" is actually within the document, i.e. that there are in fact at least 9 pages in the document. So this error is not being produced by trying to remove a page when the document doesn't have that page contained within it.
Error: Index out of bounds: 0/-1 (b)
[0]     at PDFPageTree.removeLeafNode (/Users/me/workspace/app/server/node_modules/pdf-lib/cjs/core/structures/PDFPageTree.js:105:19)
[0]     at PDFPageTree.removeLeafNode (/Users/me/workspace/app/server/node_modules/pdf-lib/cjs/core/structures/PDFPageTree.js:109:20)
[0]     at PDFCatalog.removeLeafNode (/Users/me/workspace/app/server/node_modules/pdf-lib/cjs/core/structures/PDFCatalog.js:27:22)
[0]     at PDFDocument.removePage (/Users/me/workspace/app/server/node_modules/pdf-lib/cjs/api/PDFDocument.js:338:22)
[0]     at /Users/me/workspace/app/server/routes/pdfRoutes.js:73:16
[0]     at Array.forEach (<anonymous>)
[0]     at /Users/me/workspace/app/server/routes/pdfRoutes.js:72:16

Any ideas? Is there a better way to do this?

Hello @jackwshepherd!
What version of pdf-lib are you using?

1.4.1.

Can you please share a document I can use to reproduce the issue?

Just emailed it to you - thanks a lot. Hopefully we can understand why, and post the response here. Just didn't want the doc to be public.

It seems to work fine with PDFs that are text - seems to arise only with PDFs that are comprised of images. Very odd.

@jackwshepherd I found and fixed the bug that was causing this issue in #441.

Version 1.5.1-rc2 is now published. It contains the fix for this issue.
You can install this new version with npm:
npm install<EMAIL_ADDRESS>
It's also available on unpkg:

<EMAIL_ADDRESS><EMAIL_ADDRESS>
As well as jsDelivr:

<EMAIL_ADDRESS><EMAIL_ADDRESS>

Version 1.6.0 is now published. It contains the fix for this issue. The full release notes are available here.
You can install this new version with npm:
npm install<EMAIL_ADDRESS>
It's also available on unpkg:

<EMAIL_ADDRESS><EMAIL_ADDRESS>
As well as jsDelivr:

<EMAIL_ADDRESS><EMAIL_ADDRESS>


ARTEMIS-3133 Just Encapsulating ObjectPool into a small utility

@franz1981 for your review

if we intend to use object pools.. perhaps we could expand on this idea.


fix: clone each SpannerParameter when cloning a parameter collection

Cloning a SpannerParameterCollection would not clone the individual SpannerParameter instances
in the collection. This would mean that if you cloned a SpannerCommand and then changed the
value of a parameter on the original command, the value would also be changed on the cloned
command.

@jskeet PTAL
I've added a test case that would fail before this change, and now succeeds.
In addition it might be worth noting that the CloneUpdateWithParameters() test failed after introducing this change, as it checked whether the parameters of a cloned command were equal to the original command. However, as SpannerCommand does not implement Equals(..) it in reality checked for reference equality of the underlying parameters of the original and cloned command.

Will review on Monday - I'm on vacation today.

Closed and reopened with "allow breaking changes" as the parameter reordering in an earlier PR is strictly-speaking breaking (but in a way we're okay with). This is probably a sign that we should do a minor release soon :)

This is probably a sign that we should do a minor release soon :)

+1 to that. This change and the one for GetBytes are needed for the NHibernate driver and dialect that we are currently working on.

Cool. We're in a release freeze right now, but we can do a release on December 1st if that would be useful.

Cool. We're in a release freeze right now, but we can do a release on December 1st if that would be useful.

Yes, that would certainly be useful. Thanks!


Prevent "endless" search requests

Apparently, when having lots of documents and searching for a very common word like the, you can cause Loupe to crash because it finds too many matching documents and tries to calculate way too much.
We should try to fix that for sure. I don't know what is the best way but probably just an internal absolute limit.

Just brainstorming some ideas:

Reject queries that only contain very common words (the, an, a, with) — maybe reuse stop words for that
Set a hard timeout for query execution time (e.g. 1.000ms)
Set a hard upper limit on number of processed results (e.g. 10.000)
Rate limiting (this one's better implemented on the consumer side)
Cache results for around 1 minute (might also be better to do on the consumer side)

See https://github.com/loupe-php/loupe/pull/137