CMakeList.txt pollutes upper project

What version of gRPC and what language are you using?
gRPC v1.28.0-pre3 c++ with cmake.
What operating system (Linux, Windows,...) and version?
Linux Ubuntu 18
What runtime / compiler are you using (e.g. python version or version of gcc)
cmake 3.13.4 gcc-8 (or clang-9)
What did you do?
add gRPC as a sub cmake of my cmake project.
add_subdirectory(ThirdParty/grpc)

What did you expect to see?
I did expect no observable change with respect to my project that is still not using anything from grpc.
What did you see instead?
Those two flags  (and only those)
-I../foo/ThirdParty/grpc/third_party/zlib
-Ifoo/ThirdParty/grpc/third_party/zlib

are injected on all the compiler invocations.
Now, if I do this
add_subdirectory(ThirdParty/grpc)
target_link_libraries(foo PRIVATE grpc++)

then, those are the flags injected:
-I../foo/ThirdParty/grpc/third_party/zlib
-Ifoo/ThirdParty/grpc/third_party/zlib
-I../foo/nqrpc/include
-I../foo/nqrpc/source
-I../foo/ThirdParty/grpc/include
-I../foo/ThirdParty/grpc/third_party/protobuf/src
-Ifoo/ThirdParty/grpc/third_party/cares/cares
-I../foo/ThirdParty/grpc/third_party/cares/cares
-I../foo/ThirdParty/grpc/third_party/abseil-cpp

This is mostly correct.  It is questionable whether business code needs cares or abseil (or even zlib).  If those library are not referenced by grpc's include files, then maybe those -I should not leak into the business project.
madler/zlib looks dead.  Their cmake is broken (you already have a workaround in your own cmake).  You might consider switching to https://github.com/zlib-ng/zlib-ng

This bug is very annoying.  This is especially bad it happens with zlib.  With another library, it would have been unnoticed. We want to use grpc as part of a much bigger project with many CMakeList, where zlib is also used by several others sub components, most of them shipping their own copy of zlib (with symbols properly mangled to avoid link issues).  You can imagine that this header search path contamination  breaks everything.
Absolutely all the  targets of the root CMakeList get contaminated.
I don't even know how zlib's cmake can achieve that.  Cmake's scoping rules are designed to prevent contamination  from a lower CMakeList to its parent.  Any setting you do in a CMakeList is only visible to children by default.

Unfortunately this is an inherent problem when including cmake projects with add_subdirectory (which is generally simpler, but has a risk of polluting your cmake environment by third_party CMakeLists.txt).
Solution 1:
The canonical way of depending on gRPC is to first pre-install gRPC and all its dependencies under a prefix and then importing gRPC using find_package() That way, your CMakeLists.txt will stay completely clean and you will also be able to de-duplicate dependencies such as zlib (in case more of your dependencies need zlib)
https://github.com/grpc/grpc/tree/master/src/cpp#find_package
Solution 2:
Btw, if you have zlib already installed on your system (e.g. you're on linux and it look like you are), you can just set cmake -DGRPC_ZLIB_PROVIDER=package when configuring gRPC and zlib's CMakeLists.txt won't get imported into your project at all.
https://github.com/grpc/grpc/blob/f7591a3426becbed20dbd1a80beb9c1e2ca1a738/cmake/zlib.cmake#L45
That said, we acknowledge that madler/zlib has its problems and we might look into using zlib-ng in the future, but we have no imminent plans to look into that (other priorities). The solutions I mentioned about should be enough to solve your problems.


add: birme to optimization category

https://www.birme.net/

A bulk image resizer which also allows you to save images in webp format, crop images, add a watermark, add a border and rename images :)

Woo let's go! Thanks 🦾


Setting projects tsconfig target, causes vue-jest to emit bad code

I was trying to track down an issue where running the unit tests produced this output:
{myPath}/src/pages/Home.vue:26
    const vue_1 = require("vue");
          ^

    SyntaxError: Identifier 'vue_1' has already been declared

      1 | //import { shallowMount } from '@vue/test-utils';
    > 2 | import Home from '../../src/pages/Home.vue';
        | ^
      3 |

      at Runtime.createScriptFromCode (node_modules/jest/node_modules/jest-runtime/build/index.js:1258:14)
      at Object.<anonymous> (tests/unit/example.spec.ts:2:1)

And stepping through the code I could see that both the template and the script section of my single-file-component were getting transpiled to have the line:
const vue_1 = require("vue")
I can get past that issue by removing the target line of my tsconfig.json, but then the rest of my application is compiling to a different target.
You can reproduce this by cloning the vtu-next-demo repo (current master at time of writing), adding a test to it that imports its App.vue, and adding "target": "es6", to the compilerOptions of the tsconfig.json.

Thanks for flagging this. I will investigate in the next day or so!

I was unable to repro this. Here is what I did:

get master of the repo you flagged (NOTE: since you made this issue, I updated that repo to the latest VTU and Vue 3 beta)
I added some tests (see the repo)
add the tsconfig.json you said
run yarn test

It passed. For some reason the first test run took 18 seconds which was VERY weird but then it got fast (< 40ms).
Any other tips to repro this? Maybe the combo of the latest VTU and Vue 3 beta fixed it 🤔 ?

Hmm, I'll check it out again in the next week and let you know.
Hopefully the updates fixed the issue.

Thanks, lmk.

I thought it was working, but then after poking around for a while it starting breaking again.
It looks like it might have been jest caching the success, then not clearing the cache when the tsconfig changed.
I can now consistently make the issue appear and disappear on the current master: 0e152893cf  by running:
yarn test --no-cache

when adding/removing the target attribute of the tsconfig.
Broken config:
{
  "compilerOptions": {
    "target": "es6",
    "esModuleInterop": true
  }
}

Working config:
{
  "compilerOptions": {
    "esModuleInterop": true
  }
}

Ok yep, I reproduced it. I will investigate. Any ideas? 🤔

Ok so setting "target": "es6" uses constinstead ofvar- sure - and each file doesconst vue_1 = require('vue'). So of course all the const` declarations conflict.
I can't seem to repro this in the vue-jest repo. I wonder what's going on. And what the correct way to handle this would be.

Ok in the vue-jest repo, target does not change the generated code to es6.

I released vue-jest 5.0.0-alpha.1 to deal with this for now. It's dirty; I just force es5 for the target. https://github.com/vuejs/vue-jest/commit/4eb19bcef252c16f5fd64d72877c7b688929ef4a. You could try installing that; it's working for me. I am not sure if this is a deal breaker for you - will it be a problem to compile to a different target for tests only?
I have really no idea how to fix this, there is very little info in terms of how to write a complex Jest transformer. The previous versions of vue-jest just ignored your tsconfig and compiled to es5 regardless, so it was using var which is why this was never a problem (I guess no-one noticed, lol).
For now this is the best thing I can do; I reached out a maintainer of author ts-jest for some ideas. Either way, this is a vue-jest issue, so I will close this for now with this workaround.

Thanks for your work.
Your work-around that forces es5 is good enough me to use for now.
Good luck finding a proper fix in vue-jest!


Bug Report

http://scratch.mit.edu/projects/1678269
http://phosphorus.github.io/#1678269
Error: XHR Error
    at XMLHttpRequest.xhr.onerror (http://phosphorus.github.io/phosphorus.js:225:21)

🤔 well... Phosphorus has to be able to run every 2.0 project :P and I don't know how it is possible to be able to run any project there is. So maybe the phosphorus server skipped a URL.

Phosphorus doesn't support 1.4 projects (#311). If you want to run this project in phosphorus, you can remix it in Scratch, which will update it to the 2.0 file format.
You can actually see in the network log that the Scratch player requests the 2.0 version of the project, and, failing to find that, falls back to loading the pre-2.0 .sb.

@bleush38p
(:


Update plan-onedrive-enterprise.md

Correct example provided for Manage OneDrive settings by using Intune

@nenonix @JohanFreelancer9 Copy editing is needed for this PR. Thanks.


iOS Issues - RUM Events Not Population

Describe what happened
Our Flutter app uses Datadog on both platforms. Android is correctly reporting RUM Navigation events, while iOS is not.

The above image shows Android successfully reporting navigation events, while iOS with the same config is not.

Steps to reproduce the issue:
// Dart imports:
import 'dart:developer';

// Flutter imports:
import 'package:flutter/foundation.dart';
import 'package:flutter/material.dart';

// Package imports:
import 'package:datadog_flutter_plugin/datadog_flutter_plugin.dart';
import 'package:universal_platform/universal_platform.dart';

// Project imports:
import 'storage.dart';

String getRumApplicationId() {
  var rumApplicationId = '';
  if (UniversalPlatform.isAndroid) {
    rumApplicationId = 'secret';
  } else if (UniversalPlatform.isIOS) {
    rumApplicationId = 'secret';
  } else if (UniversalPlatform.isWeb) {
    rumApplicationId = 'secret';
  }
  return rumApplicationId;
}

// Rewrite log messages to remove sensitive information
LogEvent? _logEventMapper(LogEvent event) {
  print('_logEventMapper');
  if (event.message == 'overwrite me') {
    event.message = 'overwritten';
  } else if (event.message == 'stop me') {
    // Return null if you don't want a message to be sent
    return null;
  }

  return event;
}

RumViewEvent _viewEventMapper(RumViewEvent event) {
  // print('_viewEventMapper');
  if (event.view.name == 'overwrite me') {
    event.view.name = 'overwritten';
  }

  return event;
}

RumActionEvent? _actionEventMapper(RumActionEvent event) {
  print('_actionEventMapper');
  if (event.view.name == 'overwrite me') {
    event.view.name = 'overwritten';
  }

  if (event.action.target?.name == 'discard') {
    return null;
  } else if (event.action.target?.name == 'censor me!') {
    event.action.target?.name = 'xxxxxxx me';
  }

  return event;
}

RumResourceEvent? _resourceEventMapper(RumResourceEvent event) {
  print('_resourceEventMapper');
  event.resource.url = event.resource.url.replaceAll(RegExp(r'email=[^&]+'), 'email=REDACTED');

  if (event.resource.url.contains('discard')) {
    return null;
  }

  return event;
}

RumErrorEvent? _errorEventMapper(RumErrorEvent event) {
  print('_errorEventMapper');
  if (event.error.message == 'discard') {
    return null;
  }

  if (event.error.resource != null) {
    event.error.resource!.url = event.error.resource!.url.replaceAll(RegExp(r'email=[^&]+'), 'email=REDACTED');
  }

  return event;
}

RumLongTaskEvent? _longTaskEventMapper(RumLongTaskEvent event) {
  if (event.view.name == 'discard') {
    return null;
  }

  return event;
}

/// A custom [ViewInfoExtractor] that can determine the name of a route so that
/// the view can be isolated in Datadog.
///
/// The default [ViewInfoExtractor] implementation only considers [PageRoute]s.
RumViewInfo? viewInfoExtractor(Route<dynamic> route) {
  final routeName = route.settings.name;
  if (routeName != null) {
    return RumViewInfo(name: routeName);
  }

  return null;
}

final rumConfiguration = RumConfiguration(
  applicationId: getRumApplicationId(),
  detectLongTasks: true,
  reportFlutterPerformance: true,
  rumViewEventMapper: _viewEventMapper,
  rumActionEventMapper: _actionEventMapper,
  rumResourceEventMapper: _resourceEventMapper,
  rumErrorEventMapper: _errorEventMapper,
  rumLongTaskEventMapper: _longTaskEventMapper,
);

final ddSdkConfiguration = DdSdkConfiguration(
  telemetrySampleRate: 100,
  clientToken: 'secret',
  env: box.get('environment') ?? 'production',
  site: DatadogSite.us1,
  trackingConsent: TrackingConsent.granted,
  nativeCrashReportEnabled: true,
  serviceName: 'secret',
  uploadFrequency: UploadFrequency.average,
  rumConfiguration: kReleaseMode ? rumConfiguration : null,
  loggingConfiguration: LoggingConfiguration(
    sendNetworkInfo: true,
    printLogsToConsole: true,
  ),
);

Future<void> initializeDatadog() async {
  inspect(ddSdkConfiguration);
  await DatadogSdk.instance.initialize(ddSdkConfiguration);
  if (kReleaseMode) {
    await DatadogSdk.instance.rum?.initialize();
  }
}

final ddRum = DatadogSdk.instance.rum;

 Future<void> newRunApp(DdSdkConfiguration configuration, AppRunner runner) async {
    final originalOnError = FlutterError.onError;
    FlutterError.onError = (details) {
      FlutterError.presentError(details);

      DatadogSdk.instance.rum?.handleFlutterError(details);
      logger.log.e(details.exception.toString(), details.exception, details.stack);

      originalOnError?.call(details);
    };
    PlatformDispatcher.instance.onError = (error, stack) {
      DatadogSdk.instance.rum?.addErrorInfo(
        error.toString(),
        RumErrorSource.source,
        stackTrace: stack,
      );
      return false;
    };
    await DatadogSdk.instance.initialize(configuration);
    runner();
  }

  newRunApp(ddSdkConfiguration, () {
    if (UniversalPlatform.isWeb) {
        runApp(const App());
    } else {
      runApp(const App());
    }
  });

We use go_router, the latest version, and the only observer that is passed in is the DatadogNavigationObserver
observers: [DatadogNavigationObserver(datadogSdk: DatadogSdk.instance)],
In addition to this, we are receiving this message in the Flutter Debug Console
[VERBOSE-2:shell.cc(1004)] The 'datadog_sdk_flutter.rum' channel sent a message from native to Flutter on a non-platform thread. Platform channel messages must be sent on the platform thread. Failure to do so may result in data loss or crashes, and must be fixed in the plugin or application code creating that channel.
See https://docs.flutter.dev/platform-integration/platform-channels#channels-and-platform-threading for more information.

Describe what you expected:
Additional context

Dart/Flutter version: Flutter 3.13.5, Dart 3.1.3
Android/iOS OS version: iOS 17, Mac OS Sonoma, latest XCode
Device Model: any iOS simulator/actual model
Datadog SDK version: latest version on pub.dev
Versions of any other relevant dependencies:

Is there something that I'm missing in the setup here? If I had to guess, I would say that there is something being triggered incorrectly on the iOS side with the await DatadogSdk.instance.rum?.initialize(); function.

Hi @mikhael28,
If you remove the event mappers, does iOS report properly?

I just ran my integration test for the mappers and they still pass, so unfortunately that's probably not your issue (something I still intend to fix, just not what's causing this). I would remove the mappers for now anyway, unless you need them for something.
You also shouldn't need to call DdRum.initialize manually. It's called automatically by DatadogSdk.initialize if a rumConfiguration is present. Since this actually sets up the mapper method channel, there's a possibility that's partially causing the issue. Can you try removing it and see if that helps?
I'll add some protections to make sure double calling that issues a warning and mark the method as internal.

Hey @fuzzybinary good news - the issue was only showing up in the local dev test. When deploying to prod, it reports the RUM events as expected. Well, good news / bad news I guess. All in all, things are working which is good, but the situation seems brittle.

@mikhael28 That's great to hear. This may be a significant enough issue I'm going to back port it to 1.x, but I won't put it at p0 for the time being.


[$500] Android-Thread-User B never received thread messages from User A& deleting parent not reflected

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:
User B - mweb, User A- Android in 2 devices

Go to http://staging.new.expensify.com/
Tap Fab
Tap assign task
Tap enter title
Tap next
Tap share somewhere and share it to user A (you will need to already messaged them one in order to see them for assignment)
Tap confirm task
Open User A Android account
Tap on bold task share by user B above
Tap side arrow next to task name
Tap assignee
Assign task to yourself, note it is reflected in User B task page
Complete the task by checking tick, note it is reflected in User B task page
Re-open the task by unchecking tick, note it is reflected in User B task page
Complete the task by checking tick, note it is reflected in User B task page
Send a message, note it is reflected in User B task page
Long press the sent message, and select reply in thread
In thread page, send 2 messages and note it is not reflected in User B task page
Tap on header to navigate task page
Tap 2 replies
Long press the parent message and select delete and confirm delete it.
Tap on header
Like in thread page, [deleted message]plus 2 replies shown
Verify user B task page whether displays the same

Expected Result:
In user B task page, thread messages must be shown/delivered. When user A deleted parent message, complete conversation [deleted message]plus 2 replies must be shown in User B task page.
Actual Result:
In user B task page, thread messages are not shown/delivered. When user A deleted parent message, complete conversation disappeared in User B task page.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[x] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.70-2
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/115492554/c9b3ed2c-701a-45f2-921d-13cc8834b360
https://github.com/Expensify/App/assets/115492554/703d0ada-530e-4c05-8f4f-eb99ad5aa049
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal Team
Slack conversation: @
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01033f439f718010d9
Upwork Job ID:<PHONE_NUMBER>621684736
Last Price Increase: 2023-09-15

I don't have a method to test this with two users on Android - @situchan would you be able to test this to see if it's still happening?
Sorry to ask, I'm just not sure how else to test through Browserstack with two devices (incognito mode isn't working).

Okay, I found another Android to test on.
I can reproduce these steps but I have no idea what is the issue. I think the issue is that when the parent message is deleted, it should delete the thread as well?

bumping https://expensify.slack.com/archives/C9YU7BX5M/p1695072837008099

Hello @Christinadobrzyn !
I can reproduce this issue on one device - SG M 52/Android 13/Chrome
Build v1.3.72-5
For me messages will appear if you return to the main chat with the user and then return to this task.
https://github.com/Expensify/App/assets/115492554/62bbfbc4-7f25-42b6-9aad-929518b1bc9e

Thanks @izarutskaya - to confirm have the steps in the original post been updated with the steps to reproduce this?

I can reproduce what we see but the issue is that the threaded messages are going to a chat thread and not the IOU. So I think making this change would be a feature request and not a bug. Going to close this for now and we can reopen it if needed.


Feat/ga/unit testing setup 110

https://github.com/SAP/guided-answers-extension/issues/110
Setup and configure jest and enzyme libraries in webapp so that we start adding unit tests for React components

Thanks @Klaus-Keller


bed file

Hi,
In this part, it writes
bedtools intersect -wa -wb -b /workspace/inputs/references/transcriptome/gene_annotation.bed -a WGS_Tumor_merged_sorted_mrkdup_bqsr.2.cns > WGS_Tumor_merged_sorted_mrkdup_bqsr.2.annotated.cns

I know that bed file is 0-based but cns file is  also 0-based(mimused by 1).  But it seems that we should plus 1 to  the start of every recode in the result cns file? Because the CNS format is 1-based.
Thanks for your reply.

Hi,

we the run bedtools intersect on the 0-based bed file and the 0-based segment file.

This step, I agree with you, and the result file 2.annotated.cns is still 0-based. So if we want to use the result file to go on other analysis, is it better to convert  it to 1-based?
And I have one more suggestion, rename  ".2.annotated.cns" to ".annotated.bed", this will be more clearly to know the coordination system of the file for newers.
Thank you.


logback problems

I've been trying to get logback to behave using the workaround guides. I couldn't get the custom configurator to be found at all, so I tried the option to supply the xml file from outside of the image when you launch it.
However, when I tried to do that I get a stack trace that complains about the file I'm supplying from outside:
./server/target/server -Dlogging.config=logback-spring.xml

Caused by: ch.qos.logback.core.LogbackException: Logback XML configuration is not supported yet, see https://github.com/spring-projects-experimental/spring-native/issues/625 (detected file: file:/Users/aclement/gits/project/logback-spring.xml)
	at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:46)
	at org.springframework.boot.logging.logback.LogbackLoggingSystem.configureByResourceUrl(LogbackLoggingSystem.java:191)
	at org.springframework.boot.logging.logback.LogbackLoggingSystem.loadConfiguration(LogbackLoggingSystem.java:165)
	... 22 more

(Note here I added to the message text in the substitution so it would tell me which XML file it was having trouble with).
I wonder if the substitution could be looking at that property to determine whether it should fail. (if the URL doesn't end with the value of System.getProperty("logging.config") or something) because just 'turning it off' perhaps fails too extreme.
(We could perhaps do with a sample that shows how to really use the external configurator solution)

I've removed the substitution that is producing this message. Maybe it needs re-adding but it needs some work and it preventing my app from getting anywhere. Without the substitution my app will accept external logback configuration via -Dlogging.config=logback-spring.xml OR logback configuration is working fine if the logback-spring.xml is inside the project. Perhaps it is the simplicity of the config in my situation, but it does just work (obviously with the setting in the build file that ensures we don't remove XML support). This is the logback config:
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <include resource="org/springframework/boot/logging/logback/defaults.xml" />
    <include resource="org/springframework/boot/logging/logback/file-appender.xml" />
    <root level="DEBUG">
        <appender-ref ref="FILE" />
    </root>
</configuration>%

Embedded logback-spring.xml looks like an interesting option, I will experiment and refine that.


[Quilt] Crash on startup with Vanity Splash Text

MC 1.19.2
QSL 4.0.0-beta13
FatChicken 2.0.1
VanitySplashText 1.1.0
The game crashes on startup with both mods installed. I believe it happens because your mod's version is internally marked as ${version}. Blacklisting your mod from vanity splashes lets the game start normally, but of course, I'd like to let it show your mod as well.
Logs: https://gist.github.com/Footage2-Amply-Pounce/3dd7cd8bcbe173252148a8115628dde5

fixed in 7372280e5166df55648efeccc30cba4f3e838c21


Add a stringutil helper and incidentally fix some string-related bugs

I've added a StringUtil helper with what I hope is a very clear scope - only string-related methods, and only methods which don't require any domain-specific knowledge. I've also changed some of the previous code I've written (and adjacent) to use these helpers. This actually incidentally resulted in a few fixed bugs (see second commit).
The first commit is mostly just IntelliJ refactors, moving existing methods into StringUtil. The second commit adds some new helpers and modifies some of the behavior of the existing helpers to make them more widely applicable. I know this is a bit far reaching, so for the second commit I've done an extra testing step of diffing the before/after changes (see that commit message for details), and aside from the fixed bugs there aren't any output changes.
Sorry if I went a bit overboard with the Collector 😅. I just really like streams.

I think it's interesting that you're using records. I haven't had time to fuss with those much. I couldn't decide if pulling them in here was worth it or not, so I didn't. ;)

I think it's interesting that you're using records. I haven't had time to fuss with those much. I couldn't decide if pulling them in here was worth it or not, so I didn't. ;)

Mostly I see them as a useful way to reduce boilerplate. The benefits are reduced here because generally instance variables have public access, but I see it as still worth it to avoid having to essentially repeat your instance variables three times (once for the declaration, once for the constructor arg, and once to assign it). Even though the IDE can automate away the writing of it, it's still clutter, although it does mean giving up mutable variables.
I'm a big Kotlin fan, which probably shows through. It's hard to go without all of the Kotlin niceties once you get used to them (extension methods, my beloved...)

I'm a big Kotlin fan, which probably shows through. It's hard to go without all of the Kotlin niceties once you get used to them (extension methods, my beloved...)

Yea.. a good friend of mine is all about Kotlin. I can't get there from here either (yet). I learned Rust instead.. :-P

I think it's interesting that you're using records. I haven't had time to fuss with those much. I couldn't decide if pulling them in here was worth it or not, so I didn't. ;)

Mostly I see them as a useful way to reduce boilerplate. The benefits are reduced here because generally instance variables have public access, but I see it as still worth it to avoid having to essentially repeat your instance variables three times (once for the declaration, once for the constructor arg, and once to assign it). Even though the IDE can automate away the writing of it, it's still clutter, although it does mean giving up mutable variables.

You aren't wrong here, especially as I'm essentially using them as records. I just wasn't sure how Qute and Jackson and all the other things would work with them, and didn't want to spend that time figuring out. I was wrestling enough trolls dealing with the data. ;)

Sorry if I went a bit overboard with the Collector 😅. I just really like streams.

I do avoid streams in some cases... i.e. there are methods to iterate over Jackson JsonObject fields or JsonArray elements.  Outside of that, I don't have an issue with streams. ;)

I think we hit an issue on the 5e side:
 java.lang.NumberFormatException: For input string: "30 tons"
	at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:67)
	at java.base/java.lang.Integer.parseInt(Integer.java:668)
	at java.base/java.lang.Integer.parseInt(Integer.java:786)
	at dev.ebullient.convert.StringUtil.pluralize(StringUtil.java:218)
	at dev.ebullient.convert.tools.dnd5e.qute.QuteVehicle$ShipCrewCargoPace.toString(QuteVehicle.java:179)

Fixed, I think. I've since realized that while I was running the DnD 5e tests, I'd neglected to actually add any source data - so the tests weren't actually doing anything 🤦


CircleMenu and CircleMenuItem doesn't export children as props

Hello, I was trying to use your menu for a project, it looks good, simple and well documented.
I'm facing an issue while using your package because CircleMenu and CircleMenuItem doesn't export children in their props, and then I cannot add elements inside of them as it is shown in the documentation.
I'm using React v17.0.2 with typescript v4.5.5 and the minimal code reproduction is:
<CircleMenu
    startAngle={45}
    rotationAngle={135}
    rotationAngleInclusive={true}
    itemSize={2}
    radius={100}
    menuToggleElement={

Whatever

    }
>
    <CircleMenuItem
        tooltip='Hello'
        tooltipPlacement={TooltipPlacement.Right}
        onClick={() => {}}
    >

Hello

    </CircleMenuItem>
</CircleMenu>

It is not allowing me to do this because CircleMenu and CircleMenuItem doesn't expect to have a children as seen in the props:
import { FC, ReactElement } from "react";
interface Props {
    startAngle: number;
    rotationAngle: number;
    rotationAngleInclusive?: boolean;
    radius?: number;
    itemSize?: number;
    className?: string;
    menuToggleElement?: ReactElement;
    menuToggleClassName?: string;
    onMenuToggle?: (toggleState: boolean) => void;
}
export declare const CircleMenu: FC<Props>;
export {};

Hi,
Thanks for using the package.
This seems weird, the children prop should come from the FC (FunctionComponent) type.
Does the error occur at build or in the IDE? Could you share what exactly is the error?


Service 'Set Program' not working for Dishwasher

The problem
The service Set Program won't work for my dishwasher. It does work via the Swagger and all other sensors are functioning in HA.
Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/connection.py:141
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 3 april 2022 20:45:05 (4 occurrences)
Last logged: 20:55:55

[547503625840] Error handling message: Service set_program: 400 Bad Request
[547503625840] Error handling message: template value does not contain a dynamic template @ data['sequence'][0]['target']['device_id'][0]. Got None
[547696402544] Error handling message: Service set_program: 400 Bad Request

Logger: homeassistant.helpers.script.websocket_api_script
Source: helpers/script.py:1365
First occurred: 3 april 2022 20:45:05 (3 occurrences)
Last logged: 20:55:55

websocket_api script: Error executing script. Error for call_service at pos 1: Service set_program: 400 Bad Request

I use this the Set program service, select Dishwasher and use the following parameters (I am using version 0.19)
service: miele.set_program
data:
  programId: 6
target:
  device_id: 6488f286878bf7a43284991ad57369ff

Let me know if you need/want more information
Version of miele integration having the issue?
0.19
Version of Home Assistant Core having the issue?
2022.3.8
Anything in the logs that might be useful for us?
No response
Additional information
config_entry-miele-2293fa67e57cb3d920e2a9f5911a7ffa.json.txt

It would be helpful if you could show the generated curl command from Swagger from a successful call. I don't need the line with Authorization token.

My apologies, I figured out the problems.

The first thing that needs to be done, is that the device needs to be turned on before a program can be selected and started
Secondly, apparently for my dishwasher programId number 6 doesn't work, which I used for testing within HA (and used a different number in swagger...)

So when I turn on the device via HA and then select program (not number 6!) via HA, it works perfectly! I will close this issue.

OK, unfortunately the error messages from the API are unspecific to say the least. "Bad request" is not very informative.


Convert to using Webpack and TypeScript

For realsies this time ...
Since brunch has fallen out of favor with the greater JavaScript community, the various components are becoming less maintained it seems. Switching to Webpack to resolve that problem. And since I'm redoing that whole thing, might as well convert to TypeScript at the same time ... especially since there isn't much JavaScript in the application yet.

Coverage increased (+0.07%) to 81.56% when pulling 5e7e00c5234900520becec3c6064f2a2c8805493 on webpack into a9ee40b58e8a03184c9a9457fbbc0212fb5e379d on master.


Feature Request: Add Support For Setting Default Schema Via Config

Feature discussion / request

Explain what is your use case
The project I'm working on is using a non-standard schema as the default, and so far developers have been specifying the schema manually on each query. This is kind of annoying, but manageable. When it really becomes a pain, is that depending on the environment the schema is different. e.g. development -> someSchema, production -> someOtherSchema.
Its a big government project, so I can't just tell everyone to use the default dbo schema and move on. Also there are a lot of contractors on the project, and not everyone specifies the schema in a flexible way. And even if they did, that's a lot of places that mistakes could be made.

Explain what kind of feature would support this.
I want to able able to set a default schema for my MSSQL database via a config parameter. I realize that MSSQL doesn't have native support for this, but it could be implemented at the knex query level.

Give some API proposal, how the feature should work.
I've implemented this feature in a slightly hacky
# src/db/db-client
import knex, { Knex } from "knex"

import { DB_CONFIG } from "@/config"

const db = knex(DB_CONFIG)

const dbWithSchema: Knex = new Proxy(db, {
  apply: (target, thisArg, argumentsList) => {
    return target(...argumentsList).withSchema(DB_CONFIG.defaultSchema)
  },
  get: (target, prop: keyof Knex) => {
    if (typeof target[prop] === "function") {
      if (prop === "withSchema") {
        return (schema: string) => target[prop](schema) // format taken from src/api/node_modules/knex/types/index.d.ts
      } else {
        return (...args: any[]) => target[prop](...args).withSchema(DB_CONFIG.defaultSchema)
      }
    }
    return target[prop]
  },
})

export default dbWithSchema

This lets me do the following and have the schema magically injected.
 import db from '@/db/db-client'
 db.select('id').from('user').then(console.log)

 db('user').limit(10).toString()
 db.from('user').limit(10).toString()
 db('user').withSchema('dbo').limit(10).toString()
 db.withSchema('dbo').from('user').limit(10).toString()

I'd love if this was something that came as a primary feature as there are a lot of edge cases that the way I'm currently doing it doesn't handle. One of these edge cases is db.migrate.latest() which generates a new Migrator instance, but clones the knex instance in such a way that it drops my schema wrapper.

I think this is to fix this issue.


multisearchable and weighting

Mulitsearch with weights don't seem to be working.
multisearchable :against => {:title => 'A', :description => 'B'}

Or is it not possible with pg_search?

For what it's worth, I did something similar to what @mirek and @nertzy suggest:
Create a migration like:
    change_table :pg_search_documents do |t|
      t.rename :content, :content_a
      t.text :content_b
      t.text :content_c
      t.text :content_d
    end

After your class calls ::multisearchable, include the following module to override #pg_search_document_attrs.
    module OverrideInstanceMethods
      # based on PgSearch::Multisearchable#searchable_text, for overriden
      # pg_search_document_attrs below.
      def weighted_searchable_text weight
        Array(pg_search_multisearchable_options[:against])
          .select{ |symbol, w| weight.to_s.capitalize == w.to_s.capitalize || (w.nil? && weight == :a) }
          .map{ |symbol, w| send(symbol) }
          .join(' ')
      end

      def pg_search_document_attrs
        [:a,:b,:c,:d].reduce({}) do |attrs, weight|
          attrs.tap do
            attrs["content_#{weight}".to_sym] = weighted_searchable_text(weight)
          end
        end.tap do |h|
          if (attrs = pg_search_multisearchable_options[:additional_attributes])
            h.merge! attrs.to_proc.call(self)
          end
        end
      end
    end

Elsewhere, monkey patch PgSearch::Document to use the new columns in its search scope:
module PgSearch
  class Document
    # override stock Multisearchable scope
    pg_search_scope :search, lambda { |*args|
      options = if PgSearch.multisearch_options.respond_to?(:call)
                  PgSearch.multisearch_options.call(*args)
                else
                  {:query => args.first}.merge(PgSearch.multisearch_options)
                end

      {
        against: {
          content_a: 'A',
          content_b: 'B',
          content_c: 'C',
          content_d: 'D'
        }
      }.merge(options)
    }
  end
end

Rolling this up into a PR would be a bit more work that I can do right now, but hopefully it can provide a basis for others.

One thing to keep in mind with the above code (which is great btw), is that you will also need to implement a custom rebuild method as done here https://github.com/Casecommons/pg_search#rebuilding-search-documents-for-a-given-class (the "More sophisticated approach" example). This is because the default rebuild method assumes a single "content" column which it is rebuilding for.

+1 for adding a weighting to multi column search
Id be open to requesting a pull to tackle and work through it if anyone else wanted to form a co-op to check / balance

@ericboehs Any way your custom SearchDocument and other bits you changed could be shared with a gist?

I assume you'd need to change this somehow?
https://github.com/Casecommons/pg_search/blob/bc24017fd39771237094d6fd99e93a7bf9806b8d/lib/pg_search/multisearchable.rb#L11

Hi @ericboehs are you able to elaborate on what you did and perhaps share some working code if possible? We're also having the same issue and is having trouble getting weighting working for multisearches. Thanks

Hi @ericboehs are you able to elaborate on what you did and perhaps share some working code if possible? We're also having the same issue and is having trouble getting weighting working for multisearches. Thanks

+1 for multisearch weighting 👍

entering @ericboehs code elaboration waiting room


Does not work with windows-gnu abi.

It works just fine for me. Maybe close the issue?

And I don't remember the reason even. Ok.


Cant lock Physicalbone3d in place because there is no option to make it static(bug)

The problem with this is I can only made rigidbody3d static there no option to make Physicalbone3d stay in place(static) as you can see here in this video:
https://github.com/godot-jolt/godot-jolt/assets/140886383/031942ec-c374-4e47-954c-acb0eb5e7a9f
So there is an option to make rigidbody freeze(static) but there is no option to make physicalbone3d freeze(static so it is impossible to make physicalbone3d stay in place  when I use godotphysics I still can lock the object on all axes.
I found the cause of this issue there is an update for godotjolt which caused this.

I dont know c++ so I cant modify the source code to fix this.

Ahh I found a solution for this just change this line of code at https://github.com/godot-jolt/godot-jolt/blob/master/src/objects/jolt_body_impl_3d.cpp line 1282 from None to All

Yes, this is an unfortunate reality right now, due to the way that axis-locking works in Jolt, which differs from how it's implemented in Godot Physics. I've been meaning to make a PR for Godot to add "freezing" to PhysicalBone3D, same as what RigidBody3D has, but I haven't gotten around to it.
In the meantime you can do the "freezing" yourself instead, by simply doing this:
PhysicsServer3D.body_set_mode(your_physical_bone, PhysicsServer3D.BODY_MODE_STATIC)

or if you plan to move the bone around while it's "frozen", you'll want to make it kinematic instead:
PhysicsServer3D.body_set_mode(your_physical_bone, PhysicsServer3D.BODY_MODE_KINEMATIC)

With this extension now having been merged into Godot in the form of an engine module (see README), it will be considered to be in maintenance mode going forward, where only bug fixes will be considered for merging. As such, I'll go ahead and close this.
This will instead be addressed for the new engine module by adding freezing support to PhysicalBone3D, as mentioned in my previous comment.


Switch Triton dialect to use MLIR properties

This does not change the compiler behavior, it is purely an internal change: it'll store inherent attributes (the one defined in ODS) within the operations themselves instead of in a DictionaryAttr in the MLIRContext.
The use of generic accessors like getAttribute("axis") should be avoided and direct access to the properties is prefered, like
reduceOp.getProperties().axis
Also getAttrs() or getAttrDictionary() are gonna be deprecated and users should move to getDiscardableAttrDictionary() instead.

I get these failures when running integration tests locally (both with and without my changes):
FAILED language/test_core.py::test_abs_f8[in_dtype0] - RuntimeError: value cannot be converted to type int8 without overflow
FAILED language/test_core.py::test_f8_xf16_roundtrip[out_dtype0-in_dtype0] - RuntimeError: value cannot be converted to type int8 without overflow
FAILED language/test_core.py::test_f8_xf16_roundtrip[out_dtype1-in_dtype0] - RuntimeError: value cannot be converted to type int8 without overflow
FAILED language/test_core.py::test_f8_xf16_roundtrip[out_dtype2-in_dtype0] - RuntimeError: value cannot be converted to type int8 without overflow
FAILED language/test_core.py::test_f16_to_f8_rounding[out_dtype0-in_dtype0] - RuntimeError: value cannot be converted to type int8 without overflow
FAILED language/test_core.py::test_f16_to_f8_rounding[out_dtype1-in_dtype0] - RuntimeError: value cannot be converted to type int8 without overflow
FAILED language/test_core.py::test_globaltimer - AssertionError: assert tensor(0, device='cuda:0') > 0

I'm not sure if there are known issues here? I pip install torch (2.0.1) and then run DEBUG=1 pip install   -vvve '.[tests]' ; ( cd test/unit && python3 -m pytest )  (the issue reproduces with DEBUG=0 as well).

Thank you Mehdi! Interestingly these issues are not known failures. I'll investigate today

I'm using a GeForce RTX 4090, in case it matters.


Exclude sensitive data from responses

Removed sensitive data from return of api endpoint
@PostMapping("/register")
public ResponseEntity<?> registerUser(@Valid @RequestBody User user) {
    User registeredUser = userService.registerNewUser(user);
    // Avoided returning the full user object here to not expose sensitive info
    return ResponseEntity.ok("User registered successfully with ID: " + registeredUser.getUserId());
}


unable to instantiate LXD container ver 5.8.1

Description
I have followed the official documentation step by step to install the front end and compute node for LXD.  I am not able to instantiate the LXD container.
To Reproduce
Front end:
ubuntu 18.04
opennebula 5.8.1
host file system: btrfs
Compute node:
ubuntu 18.04
opennebula 5.8.1
LXD 3.0 apt pakage
host file system: btrfs
storage backend:
NFS
datastores :
file datastore type: shared mode
image datastore type: qcow2
system datastore type: qcow2
each datastore under '/var/lib/one//datastores/' is symbolically linked to a directories created under '/mnt/NFS/'.  The ownership of each directory is set to oneadmin
In the sunstone, the capacities of the datastores are correctly displayed.
LXD image:
'ubuntu_bionic - LXD' downloaded from 'linux containers'
Tried to instantiate the container from 'ubuntu_bionic - LXD' image with all default values without an NIC.
I am not sure if it is a bug or incorrect configuration of the directory permissions.
Expected behavior
A successful instantiation of LXD container
Details

Affected Component: LXD node & storage
Hypervisor: LXD
Version: 5.8.1

Additional context
Add any other context about the problem here.
deployment log:
Sun Apr 28 21:54:04 2019 [Z0][VM][I]: New state is ACTIVE
Sun Apr 28 21:54:04 2019 [Z0][VM][I]: New LCM state is PROLOG
Sun Apr 28 21:54:07 2019 [Z0][VM][I]: New LCM state is BOOT
Sun Apr 28 21:54:07 2019 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/19/deployment.0
Sun Apr 28 21:54:09 2019 [Z0][VMM][I]: Successfully execute transfer manager driver operation: tm_context.
Sun Apr 28 21:54:09 2019 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Sun Apr 28 21:54:13 2019 [Z0][VMM][I]: Command execution fail: cat << EOT | /var/tmp/one/vmm/lxd/deploy '/var/lib/one//datastores/108/19/deployment.0' 'compute2' 19 compute2
Sun Apr 28 21:54:13 2019 [Z0][VMM][I]: deploy: Using qcow2 mapper for /var/lib/one/datastores/108/19/disk.0
Sun Apr 28 21:54:13 2019 [Z0][VMM][I]: deploy: Mapping disk at /var/lib/lxd/storage-pools/default/containers/one-19/rootfs using device /dev/nbd0
Sun Apr 28 21:54:13 2019 [Z0][VMM][I]: deploy: Mounting /dev/nbd0 at /var/lib/lxd/storage-pools/default/containers/one-19/rootfs
Sun Apr 28 21:54:13 2019 [Z0][VMM][I]: deploy: Mapping disk at /mnt/NFS/108/19/mapper/disk.1 using device /dev/loop3
Sun Apr 28 21:54:13 2019 [Z0][VMM][I]: deploy: Mounting /dev/loop3 at /mnt/NFS/108/19/mapper/disk.1
Sun Apr 28 21:54:13 2019 [Z0][VMM][I]: deploy: Using qcow2 mapper for /var/lib/one/datastores/108/19/disk.0
Sun Apr 28 21:54:13 2019 [Z0][VMM][I]: deploy: Unmapping disk at /var/lib/lxd/storage-pools/default/containers/one-19/rootfs
Sun Apr 28 21:54:13 2019 [Z0][VMM][I]: /var/tmp/one/vmm/lxd/mapper.rb:203:in realpath': Permission denied @ realpath_rec - /var/lib/lxd/storage-pools/default/containers/one-19/rootfs (Errno::EACCES) Sun Apr 28 21:54:13 2019 [Z0][VMM][I]: from /var/tmp/one/vmm/lxd/mapper.rb:203:in unmap'
Sun Apr 28 21:54:13 2019 [Z0][VMM][I]: from /var/tmp/one/vmm/lxd/container.rb:359:in public_send' Sun Apr 28 21:54:13 2019 [Z0][VMM][I]: from /var/tmp/one/vmm/lxd/container.rb:359:in setup_disk'
Sun Apr 28 21:54:13 2019 [Z0][VMM][I]: from /var/tmp/one/vmm/lxd/container.rb:241:in block in setup_storage' Sun Apr 28 21:54:13 2019 [Z0][VMM][I]: from /var/tmp/one/vmm/lxd/container.rb:234:in each'
Sun Apr 28 21:54:13 2019 [Z0][VMM][I]: from /var/tmp/one/vmm/lxd/container.rb:234:in setup_storage' Sun Apr 28 21:54:13 2019 [Z0][VMM][I]: from /var/tmp/one/vmm/lxd/deploy:78:in rescue in '
Sun Apr 28 21:54:13 2019 [Z0][VMM][I]: from /var/tmp/one/vmm/lxd/deploy:74:in `'
Sun Apr 28 21:54:13 2019 [Z0][VMM][I]: ExitCode: 1
Sun Apr 28 21:54:13 2019 [Z0][VMM][I]: Failed to execute virtualization driver operation: deploy.
Sun Apr 28 21:54:13 2019 [Z0][VMM][E]: Error deploying virtual machine
Sun Apr 28 21:54:13 2019 [Z0][VM][I]: New LCM state is BOOT_FAILURE
lxc.log:
lxc one-19<PHONE_NUMBER>5412.755 WARN     conf - conf.c:lxc_setup_devpts:1616 - Invalid argument - F                                                                                ailed to unmount old devpts instance
lxc one-19<PHONE_NUMBER>5412.784 ERROR    start - start.c:start:2028 - No such file or directory - F                                                                                ailed to exec "/sbin/init"
lxc one-19<PHONE_NUMBER>5412.784 ERROR    sync - sync.c:__sync_wait:62 - An error occurred in anothe                                                                                r process (expected sequence number 7)
lxc one-19<PHONE_NUMBER>5412.784 ERROR    lxccontainer - lxccontainer.c:wait_on_daemonized_start:842                                                                                - Received container state "ABORTING" instead of "RUNNING"
lxc one-19<PHONE_NUMBER>5412.785 ERROR    start - start.c:__lxc_start:1939 - Failed to spawn contain                                                                                er "one-19"
lxc<PHONE_NUMBER>5412.786 WARN     commands - commands.c:lxc_cmd_rsp_recv:132 - Connection reset by                                                                                peer - Failed to receive response for command "get_state"

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

Hello, we fixed a bug related to your specific setup, which is what happens here, however, it happens after the container fails to start. The log says LXD complains about missing the /sbin/init of the container image, which is another issue you are experiencing.

I'm closing this since the fix is already submitted, if you still experience the issue with the code of https://github.com/OpenNebula/one/tree/one-5.8 we could reopen it

Hi thank you for the fix. I have found the problem with '/sbin/init'.  It is because the image from 'linuxcontainers.org' is in raw format, and I downloaded into qcow2 datastore which messed up the internal of the file.  I switched it back to shared mode and set the LXD_SECURITY_PRIVILEGED to "false".  For some reason, I am still experiencing problem deploy the container.  Do you think there might be some problem with my LXD configuration ?
Template:
CONTEXT = [
NETWORK = "YES",
SET_HOSTNAME = "$NAME",
SSH_PUBLIC_KEY = "$USER[SSH_PUBLIC_KEY]" ]
CPU = "1"
DISK = [
IMAGE_ID = "20" ]
GRAPHICS = [
LISTEN = "<IP_ADDRESS>",
TYPE = "vnc" ]
HYPERVISOR = "lxd"
LXD_SECURITY_PRIVILEGED = "false"
MEMORY = "1024"
Sunstone log:
Mon Apr 29 16:53:13 2019 [Z0][VM][I]: New state is ACTIVE
Mon Apr 29 16:53:13 2019 [Z0][VM][I]: New LCM state is PROLOG
Mon Apr 29 16:53:19 2019 [Z0][VM][I]: New LCM state is BOOT
Mon Apr 29 16:53:19 2019 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/23/deployment.0
Mon Apr 29 16:53:20 2019 [Z0][VMM][I]: Successfully execute transfer manager driver operation: tm_context.
Mon Apr 29 16:53:20 2019 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Mon Apr 29 16:53:23 2019 [Z0][VMM][I]: Command execution fail: cat << EOT | /var/tmp/one/vmm/lxd/deploy '/var/lib/one//datastores/102/23/deployment.0' 'compute2' 23 compute2
Mon Apr 29 16:53:23 2019 [Z0][VMM][I]: deploy: Using raw filesystem mapper for /var/lib/one/datastores/102/23/disk.0
Mon Apr 29 16:53:23 2019 [Z0][VMM][I]: deploy: Mapping disk at /var/lib/lxd/storage-pools/default/containers/one-23/rootfs using device /dev/loop3
Mon Apr 29 16:53:23 2019 [Z0][VMM][I]: deploy: Resizing filesystem ext4 on /dev/loop3
Mon Apr 29 16:53:23 2019 [Z0][VMM][I]: deploy: Mounting /dev/loop3 at /var/lib/lxd/storage-pools/default/containers/one-23/rootfs
Mon Apr 29 16:53:23 2019 [Z0][VMM][I]: deploy: Mapping disk at /mnt/NFS/102/23/mapper/disk.1 using device /dev/loop4
Mon Apr 29 16:53:23 2019 [Z0][VMM][I]: deploy: Mounting /dev/loop4 at /mnt/NFS/102/23/mapper/disk.1
Mon Apr 29 16:53:23 2019 [Z0][VMM][I]: deploy: Using raw filesystem mapper for /var/lib/one/datastores/102/23/disk.0
Mon Apr 29 16:53:23 2019 [Z0][VMM][I]: deploy: Unmapping disk at /var/lib/lxd/storage-pools/default/containers/one-23/rootfs
Mon Apr 29 16:53:23 2019 [Z0][VMM][I]: deploy: Umounting disk mapped at /dev/loop3
Mon Apr 29 16:53:23 2019 [Z0][VMM][I]: deploy: Unmapping disk at /mnt/NFS/102/23/mapper/disk.1
Mon Apr 29 16:53:23 2019 [Z0][VMM][E]: deploy: Failed to detect block device from /mnt/NFS/102/23/mapper/disk.1
Mon Apr 29 16:53:23 2019 [Z0][VMM][E]: deploy: failed to dismantle container storage
Mon Apr 29 16:53:23 2019 [Z0][VMM][I]: /var/tmp/one/vmm/lxd/client.rb:145:in initialize': undefined method []' for #LXDError:0x0000563a7cdd6ed8 (NoMethodError)
Mon Apr 29 16:53:23 2019 [Z0][VMM][I]: from /var/tmp/one/vmm/lxd/deploy:86:in exception' Mon Apr 29 16:53:23 2019 [Z0][VMM][I]: from /var/tmp/one/vmm/lxd/deploy:86:in raise'
Mon Apr 29 16:53:23 2019 [Z0][VMM][I]: from /var/tmp/one/vmm/lxd/deploy:86:in rescue in <main>' Mon Apr 29 16:53:23 2019 [Z0][VMM][I]: from /var/tmp/one/vmm/lxd/deploy:74:in '
Mon Apr 29 16:53:23 2019 [Z0][VMM][I]: ExitCode: 1
Mon Apr 29 16:53:23 2019 [Z0][VMM][I]: Failed to execute virtualization driver operation: deploy.
Mon Apr 29 16:53:23 2019 [Z0][VMM][E]: Error deploying virtual machine
Mon Apr 29 16:53:23 2019 [Z0][VM][I]: New LCM state is BOOT_FAILURE
lxc log
lxc one-23<PHONE_NUMBER>5323.891 ERROR    conf - conf.c:mount_autodev:1131 - Permission denied - Failed to create "/dev" directory
lxc one-23<PHONE_NUMBER>5323.891 ERROR    conf - conf.c:lxc_setup:3529 - Failed to mount "/dev"
lxc one-23<PHONE_NUMBER>5323.891 ERROR    start - start.c:do_start:1263 - Failed to setup container "one-23"
lxc one-23<PHONE_NUMBER>5323.897 ERROR    sync - sync.c:__sync_wait:62 - An error occurred in another process (expected sequence number 5)
lxc one-23<PHONE_NUMBER>5323.909 ERROR    start - start.c:__lxc_start:1939 - Failed to spawn container "one-23"
lxc one-23<PHONE_NUMBER>5323.954 ERROR    lxccontainer - lxccontainer.c:wait_on_daemonized_start:842 - Received container state "ABORTING" instead of "RUNNING"
lxc<PHONE_NUMBER>5323.105 WARN     commands - commands.c:lxc_cmd_rsp_recv:132 - Connection reset by peer - Failed to receive response for command "get_state"

Well, the marketplace images are meant to be run SECURITY_PRIVILEGED = true

hmm  could you please advice what should I do if I need to run unprivileged container ?

well, right now, the only choice would be to create your own image, since we are facing this issue

Thank you very much. Looking forward to the next release :)


Use new numpy.random.Generator interface

Original report by Joseph Fowler (Bitbucket: joe_fowler, ).

As of numpy 1.17 (see docs) in mid-2019, there’s a new interface for random numbers, numpy.random.Generator. We should use it. It is faster and has better randomness properties.

Original comment by Joseph Fowler (Bitbucket: joe_fowler, ).

Finish switch to new numpy RPG API
Fixes #244


Coord can update their progress page

Needs #535

To define which fields need to be updated. Eventual mock-up after input from coords.


refactor prevented plant

Refactor prevented plant to be simpler by using more pandas functions instead of hand-rolled functions and move some things into an external helper dependency. Allows soy + corn model to be separate as well.

Closing this PR as stale.


🧩 refactor 🧩

This refactors to use Poetry as a dependency and build manager and adds a skeleton release pipeline. @jordan-pieces how are you publishing to pypi at the moment? I've included an imaginary secret in the pipeline, if we can get the pypi credentials in the secrets it should be gtg.

we should meet about this today and I can get you setup with the proper keys, we can pair on this today/tomorrow but itsll all deployed with a few commands but nothing crazy


Renewal failed

Issue description
I'm having an IDN domain for which the certificate was renewed successfully 6 times in the past.
Since 2019-10-19 it fails to renew.
When manually trying to renew I'm getting this output:
[WARN] Found 4 files older than 120 days in the CertificatePath
[EROR] Common name not contained in SAN list.
[EROR] (Exception): Target plugin generated an invalid target
[EROR] Renewal for [Manual] www.xn--erdbr-jra.net failed, will retry on next run

Steps to reproduce

Start "wacs.exe"
Press S to renew specific
Selecting the certificate from the list by entering the number

Client version:  <IP_ADDRESS>4 (RELEASE)
Windows version: Windows Server 2016 Datacenter (English, 64 bit)
Relevant part of log file:
[VERB] Loading ACME account signer...
[DBUG] Loading signer from C:\ProgramData\win-acme\acme-v02.api.letsencrypt.org\Signer_v2
[VERB] Constructing ACME protocol client...
[DBUG] Send GET request to https://acme-v02.api.letsencrypt.org/directory
[VERB] Request completed with status OK
[DBUG] Send HEAD request to https://acme-v02.api.letsencrypt.org/acme/new-nonce
[VERB] Request completed with status OK
[DBUG] Loading account information from C:\ProgramData\win-acme\acme-v02.api.letsencrypt.org\Registration_v2
[WARN] Found 4 files older than 120 days in the CertificatePath
[EROR] Common name not contained in SAN list.
[EROR] (Exception): Target plugin generated an invalid target
[DBUG] Exception details: Exception {Message="Target plugin generated an invalid target", Data=[], InnerException=null, TargetSite=PKISharp.WACS.DomainObjects.RenewResult Renew(PKISharp.WACS.DomainObjects.Renewal, PKISharp.WACS.RunLevel), StackTrace="   at PKISharp.WACS.Wacs.Renew(Renewal renewal, RunLevel runLevel)\r\n   at PKISharp.WACS.Wacs.ProcessRenewal(Renewal renewal, RunLevel runLevel)", HelpLink=null, Source="wacs", HResult=-2146233088}
[EROR] Renewal for [Manual] www.xn--erdbr-jra.net failed, will retry on next run

I've freshly-generated the certificate with this commandline:
"C:\Program Files\letsencrypt\wacs.exe" --target manual --host www.xn--erdbr-jra.net --validation filesystem --webroot "C:\Websites\misc\xn--erdbr-jra.net" --store pemfiles --pemfilespath "C:\Websites\ApacheConfigs\Certificates"

To my surprise, this succeeded:
[INFO] A simple Windows ACMEv2 client (WACS)
[INFO] Software version <IP_ADDRESS>4 (RELEASE)
[INFO] IIS version 10.0
[INFO] Scheduled task looks healthy
[INFO] Please report issues at https://github.com/PKISharp/win-acme
[INFO] Running in mode: Unattended
[INFO] Target generated using plugin Manual: www.erdbär.net
[INFO] Authorize identifier: www.xn--erdbr-jra.net
[INFO] Authorizing www.xn--erdbr-jra.net using http-01 validation (FileSystem)
[INFO] Answer should now be browsable at http://www.xn--erdbr-jra.net/.well-known/acme-challenge/seuFsLNX-s-_hYRcbUw5PQOuGOXndO44-uABpT-SUEM
[INFO] Preliminary validation looks good, but ACME will be more thorough...
[INFO] Authorization result: valid
[WARN] Found 4 files older than 120 days in the CertificatePath
[INFO] Requesting certificate [Manual] www.erdbär.net
[INFO] Store with PemFiles...
[INFO] Exporting .pem files to C:\Websites\ApacheConfigs\Certificates
[INFO] Installing with None...
[INFO] Scheduled task looks healthy
[INFO] Adding renewal for [Manual] www.erdbär.net
[INFO] Next renewal scheduled at 2019.12.28 11:27:08

I then did try a specific renewal again, with the steps to reproduce in my initial posting above.
This again lead to an error:
[VERB] Loading ACME account signer...
[DBUG] Loading signer from C:\ProgramData\win-acme\acme-v02.api.letsencrypt.org\Signer_v2
[VERB] Constructing ACME protocol client...
[DBUG] Send GET request to https://acme-v02.api.letsencrypt.org/directory
[VERB] Request completed with status OK
[DBUG] Send HEAD request to https://acme-v02.api.letsencrypt.org/acme/new-nonce
[VERB] Request completed with status OK
[DBUG] Loading account information from C:\ProgramData\win-acme\acme-v02.api.letsencrypt.org\Registration_v2
[WARN] Found 4 files older than 120 days in the CertificatePath
[EROR] Common name not contained in SAN list.
[EROR] (Exception): Target plugin generated an invalid target
[DBUG] Exception details: Exception {Message="Target plugin generated an invalid target", Data=[], InnerException=null, TargetSite=PKISharp.WACS.DomainObjects.RenewResult Renew(PKISharp.WACS.DomainObjects.Renewal, PKISharp.WACS.RunLevel), StackTrace="   at PKISharp.WACS.Wacs.Renew(Renewal renewal, RunLevel runLevel)\r\n   at PKISharp.WACS.Wacs.ProcessRenewal(Renewal renewal, RunLevel runLevel)", HelpLink=null, Source="wacs", HResult=-2146233088}
[EROR] Renewal for [Manual] www.xn--erdbr-jra.net failed, will retry on next run

So I can say the initial certificate request does work whereas the renewal fails for IDN domains.

Interesting bug. In the renewal.json file on disk the expected format for host names is unicode. I'm able to reproduce the effect that you are seeing by manually setting the punycode-notation there (e.g. xn--erdbr-jra instead of erdbär). But I'm not able to reproduce how this notation is getting stored there.
Can you check your file and report back what you are seeing there?

Currently searching my whole HDD for renewal.json. Any hint on where it should be stored?

In the configuration path, typically %programdata%\win-acme\{url}

Thank you, that helped! I've found Vnk5oDVB6U6DF-6IwdBPXQ.renewal.json in C:\ProgramData\win-acme\acme-v02.api.letsencrypt.org with this content:
{
  "Id": "Vnk5oDVB6U6DF-6IwdBPXQ",
  "LastFriendlyName": "[Manual] www.erdbär.net",
  "PfxPasswordProtected": "enc-AQAAANCMnd8BFdERjHoAwE/Cl+sBAAAAMWB/EEkIs0qsb0vn3uCVWgQAAAACAAAAAAAQZgAAAAEAACAAAAAWb09Uif+9UzzpRTfFdHHVwjMwnYJ2e95DQ1W/6MjO1gAAAAAOgAAAAAIAACAAAAB9SriXqMyDd63DLUOuYTvKhyBGsRLnVAc00Ihxk6FLyDAAAACLLTEGkQyS5gvM0sBrqTgglYXNbWmCIjKStDzI25CDtNd6auHI5mPB7eB+jr6lIBBAAAAAWMCApJ38cOJ1IY6ALc+uAfblzJW3j7o7YwYPNFzyddmYXvFHYKhQBn3Ag7eX/gtUuagL6sGYnh6bZrqSmWcNAw==",
  "TargetPluginOptions": {
    "CommonName": "www.erdbär.net",
    "AlternativeNames": [
      "www.erdbär.net"
    ],
    "Plugin": "e239db3b-b42f-48aa-b64f-46d4f3e9941b"
  },
  "ValidationPluginOptions": {
    "Path": "C:\\Websites\\misc\\xn--erdbr-jra.net",
    "CopyWebConfig": false,
    "Plugin": "1c77b3a4-5310-4c46-92c6-00d866e84d6b"
  },
  "CsrPluginOptions": {
    "Plugin": "b9060d4b-c2d3-49ac-b37f-962e7c3cbe9d"
  },
  "StorePluginOptions": [
    {
      "Path": "C:\\Websites\\ApacheConfigs\\Certificates",
      "KeepExisting": false,
      "Plugin": "e57c70e4-cd60-4ba6-80f6-a41703e21031"
    }
  ],
  "InstallationPluginOptions": [
    {
      "Plugin": "aecc502c-5f75-43d2-b578-f95d50c79ea1"
    }
  ],
  "History": [
    {
      "Date": "2019-11-03T10:27:08.7004986Z",
      "Success": true,
      "Thumbprint": "DDB60BD8BE66CD404B6FF6B920AB2448F07B5117"
    }
  ]
}

Strangly I'm not able to reproduce this, even when I use the exact renewal file that you have kindly shared. My theory that there would be punycode there also turned out to be false.
I do however notice a small inconsistency in the friendly name of the certificate as well. In some of your logs it says [Manual] www.erdbär.net (which is also consistent with the renewal.json file that you posted), but in your failing logs it's talking about [Manual] www.xn--erdbr-jra.net). This might be another manifestion of the same underlying issue, but it's also a bit suspicious that the failure is not logged in the history of this renewal. Can you double check that there are not in fact two seperate renewals set up for the same site?
Another thing I'd like to you try is the 2.1.0 beta version to see if that is also impacted.

OMG, you are right, there are indeed two entries:
1: [Manual] www.xn--erdbr-jra.net - renewed 6 times, due now
...
77: [Manual] www.erdbär.net - renewed 1 time, due after 2019.12.28 11:27:08

I've removed the "1" scheduled renewal and I'm now able to successfully renew the "77" (now "76").
Thanks for helping me on that!
I've also updated to the latest beta <IP_ADDRESS>5, just in case.


[18.09 backport] Use original process spec for execs

Backport of https://github.com/moby/moby/pull/38871 for 18.09
fixes https://github.com/moby/moby/issues/38865 for 18.09

ping @crosbymichael @tonistiigi PTAL


Selected Min Value is not setting by calling setSelectedMinValue()

I am using your lib into my app. For first time when view initializes setSelectedMinValue() method works perfectly. But when I make server API call to get values for those seekbar; setSelectedMinValue() is stuck at default setSelectedMaxValue(). Whereas setSelectedMaxValue() is working perfectly.
For example; I have take age range from 18-100 and default selection is like this:
ageSeekBar = new RangeSeekBars<>(getApplicationContext()); // Set the range ageSeekBar.setRangeValues(18, 100); ageSeekBar.setSelectedMinValue(18); ageSeekBar.setSelectedMaxValue(28);
After this I make some server call and from there I am updating it as
ageSeekBar.setSelectedMinValue(74); ageSeekBar.setSelectedMaxValue(98);
But as a result I see that Min-selection is at 28 whereas max selection is at 98.
So can you please help me out for fixing this issue.

I'd have to debug a bit, but I think the issue is that when you call setSelectedMinValue(74), your maxValue is at 28. So you would be moving the minimum beyond the max, which is of course not possible. So min gets stopped at 28. Then max moves on to 98 as normal.
This is a very valid usecase which is not well supported at the moment. Perhaps a good solution would to offer a method that would allow setting both min and max at the same time, similar to setRangeValues.
In the meantime, maybe a workaround that could work is to reset the select min and max to default (by calling resetSelectedValues(), then setting the desired selected values?

Ok Thank you for guiding, calling resetSelectedValues() resolved this issue.

Glad that worked @himanshuagarwal77225. I'm actually going to keep this issue open, as I would like to come up with a better solution for it.


Add shortcut for window focus next

Describe the feature
gi.app.go:183 -- used to have a keyboard shortcut in v1.  important for full keyboard-based navigation in Code.
Relevant code
No response

Just do it!!

just did!


Add early example of drawing a molecule to Getting Started with the RDKit in Python

Using Draw.MolToImage(), draws the first molecule in the tutorial, Cc1ccccc1.

Reference Issue

What does this implement/fix? Explain your changes.
This gives an example of drawing a molecule early in the tutorial. That is a key function that learners will likely want to use to confirm that their RDKit commands produce the expected result.
Any other comments?
I was unsure how to run doctests locally, so I have not done so. Guidance on how to do that would be appreciated.

Thanks for the contribution @bertiewooster and sorry for the slow first review of this... it's been a busy week.

I was unsure how to run doctests locally, so I have not done so. Guidance on how to do that would be appreciated.

You can run the doctests by doing make doctest in the Docs/Book directory. That will run the tests and report success/failure.

I implemented @greglandrum's suggestion, and that indeed makes the doctest pass for the modification in this pull request, so thanks.
The doctest finds an existing error (it's raised in the master branch as well) in the Ring Information section. If this existing error needs to be resolved, request guidance on how to do so.
Document: GettingStartedInPython
--------------------------------
[16:34:57] Explicit valence for atom # 6 N, 4, is greater than permitted
[16:34:57] Explicit valence for atom # 1 O, 3, is greater than permitted
[16:34:57] Can't kekulize mol.  Unkekulized atoms: 0 1 2
**********************************************************************
File "GettingStartedInPython.rst", line 512, in default
Failed example:
    len(Chem.GetSSSR(m))
Exception raised:
    Traceback (most recent call last):
      File "/Users/jemonat/opt/anaconda3/envs/my-rdkit-env/lib/python3.10/doctest.py", line 1346, in __run
        exec(compile(example.source, filename, "single",
      File "<doctest default[0]>", line 1, in <module>
        len(Chem.GetSSSR(m))
    TypeError: object of type 'int' has no len()
[16:35:01] Can't kekulize mol.  Unkekulized atoms: 1 2 3 4 5
**********************************************************************
1 items had failures:
   1 of 683 in default
683 tests in 1 items.
682 passed and 1 failed.
***Test Failed*** 1 failures.

Hi, I previously addressed the requested change, I just couldn't mark it as such due to the sequence of commits.
Request guidance on whether/how to address preexisting error (it's raised in the master branch as well) in the Ring Information section.

@bertiewooster sorry this took so long... Thanks for the contribution though!


Feature Request: pull delayed scheduler from configuration

Would it be possible for dask collections and delayed to initialize a distributed scheduler from some sort of configuration?
My understanding is that currently if a distributed client is instantiated then dask collections and delayed will use that client as the scheduler. However there is no way to put the client loading information into a configuration so that dask collections and delayed instantiate that client themselves if it doesn't exist, forcing you to use whatever client they initialize.
This would be good to have because libraries currently using dask collections and delayed have no way to bind to a particular client unless that client is externally initialized, which may not be possible in some circumstances, for instance running a standalone app.

CC @danielballan

Would it be possible for dask collections and delayed to initialize a distributed scheduler from some sort of configuration?

When constructing a dask collection type you can specify a default scheduler to use.
See https://docs.dask.org/en/latest/custom-collections.html
Maybe you'll be able to screw around with that to get what you want?

Awesome! Thank you very much! Is there something similar for delayed?

CC @martindurant

Delayed is a dask collection.  Everything I said holds true for it as well.

I think @mrocklin resolved this issue.  If I'm mistaken please reopen


Missing Prefabs Due to Absence of .meta Files in Unity Project

Hello,
First of all, thanks for your excellent work. I encountered some problems when trying to run this project in Unity. Specifically, there are errors of missing prefabs in the project. I suspect this may be due to the absence of some .meta files in the project.
If possible, could you check and re-upload these .meta files?
Thank you again for your contribution to this project, and I look forward to your help!

Could you provide more details about the errors? It should be an easy fix.

The detailed error information is shown in the following figure:

Actually, I am not familiar with Unity, so I also try running the Flightmare_unity project in Unity. Fortunately, it works very well. Therefore, I compared the project files of the two to find the reason.
The file comparison is as follows:

After searching, I learned that meta files in Unity are used to manage resources.  If meta files are missing, Unity will not recognize the corresponding assets. Even if the asset files exist, Unity will treat them as new assets, leading to prefabs, scenes, etc., failing to load resources correctly.
I suspect that when the Flymation project is run in Unity for the first time, some meta files are automatically generated. However, the resource index information contained in these files is incorrect, which causes the issue of missing prefabs.
Maybe modifying the .gitignore and then re-uploading could fix this issue.


Getting ready for opendistro-1.4 release

No major code changes. Changes are made due to changes in ES.

Changes are already in for opendistro-1.4
Closing this PR


Normal surface implementations

Only a single vol surface implementation exists for Normal vols: NormalSwaptionExpiryTenorVolatilitiesTest
It would be useful to have similar implementations for the following use cases:

Expiry/Strike (as quoted on Bloomberg)
Expiry/Moneyness (as quoted on Bloomberg)
Constant surfaces with no metadata (i.e. a NormalSwaptionVolatilities implementation containing just a simple double zValue, instead of requiring a full ConstantNodalSurfaceto be defined. Calls tosurfaceCurrencyParameterSensitivity()would probably throwUnsupportedOperationException`.

This one should probably be tackled in tandem with #847 since the addition of a constant surface (as described above) will mean that the pricing model can no longer be inferred from the Volatilities type.


Fix wrong api method call

#235 Introduces some REST API, but client calls one of it's API in wrong way.
Ready to merge.

Looks good, let's merge

LGTM (I was wondering why it's not working!)


Add raw data support

Thank you so much for the library! It was (almost) exactly what we needed. Let us know if we can help further.
This commit adds the ability to return the raw topic and message buffer,
allowing easier handling of binary data from mqtt inside the graphql endpoint
itself.
Enable by setting the rawData option. If it is not set, it behaves
identically to the existing JSON/String path.
It also upgrades Mocha to 7.0.1, to resolve multiple security
vulnerabilities with Mocha.

It looks like node 6 fails on modern versions of Mocha, but I suspect it is reasonable to no longer have support for it. Happy to do whatever makes sense for you.
It also appears like we are the first people to check in the package-lock - happy to remove it if you would rather not.


Custom Date and Range picker

Looking for date range picker like below( angular material design) in JavaFx. Are you guy's going to implement it? or Is there any other solution for that? Please let me know.

Hello,
it might be implemented in the future, however it's not planned yet. in the meantime, feel free to add your own contribution to JFoenix.
Regards,


Fixes the installation of consul-backinator

fixes #798
/assign @simonswine
Fix consul-backinator installation

/test puppet-tarmak-acceptance-ubuntu v1.11
/unassign
/assign @simonswine

/test puppet-tarmak-acceptance-ubuntu v1.11

/test puppet-tarmak-acceptance-ubuntu v1.11

Have you been successful at backing up:
systemctl start consul-backup.service
May 01 16:02:41 centos-72-x64 systemd[1]: Starting Backup consul KV store...
May 01 16:02:41 centos-72-x64 consul-backup.sh[5067]: 2019/05/01 16:02:41 [Error] Failed to backup key data: No keys found
May 01 16:02:41 centos-72-x64 systemd[1]: consul-backup.service: main process exited, code=exited, status=1/FAILURE
May 01 16:02:41 centos-72-x64 systemd[1]: Failed to start Backup consul KV store.

I made sure there is something stored in the KV store

/assign @JoshVanL
/unassign

@simonswine Seems fine for me
May 01 14:57:03 ip-10-99-32-10.eu-west-1.compute.internal systemd[1]: Starting Backup consul KV store...
May 01 14:57:03 ip-10-99-32-10.eu-west-1.compute.internal consul-backup.sh[18830]: 2019/05/01 14:57:03 [Success] Backed up 234 keys from / to /tmp/consul-backup
May 01 14:57:03 ip-10-99-32-10.eu-west-1.compute.internal consul-backup.sh[18830]: 2019/05/01 14:57:03 [Success] Backed up 2 ACL tokens from  to /tmp/consul-backup-acls
May 01 14:57:03 ip-10-99-32-10.eu-west-1.compute.internal consul-backup.sh[18830]: Keep your backup and signature files in a safe place.
May 01 14:57:03 ip-10-99-32-10.eu-west-1.compute.internal consul-backup.sh[18830]: You will need both to restore your data.
May 01 14:57:04 ip-10-99-32-10.eu-west-1.compute.internal consul-backup.sh[18830]: [217B blob data]
May 01 14:57:04 ip-10-99-32-10.eu-west-1.compute.internal consul-backup.sh[18830]: [225B blob data]
May 01 14:57:05 ip-10-99-32-10.eu-west-1.compute.internal consul-backup.sh[18830]: [227B blob data]
May 01 14:57:05 ip-10-99-32-10.eu-west-1.compute.internal consul-backup.sh[18830]: [235B blob data]
May 01 14:57:05 ip-10-99-32-10.eu-west-1.compute.internal systemd[1]: Started Backup consul KV store.
May 01 16:27:07 ip-10-99-32-10.eu-west-1.compute.internal systemd[1]: Starting Backup consul KV store..

/unassign
/assign @simonswine

/assign @MattiasGees

I tested this and it worked properly for me:
-- Logs begin at Tue 2019-05-07 11:31:42 UTC, end at Tue 2019-05-07 12:48:25 UTC. --
May 07 12:44:06 ip-10-99-32-10.eu-west-1.compute.internal systemd[1]: Starting Backup consul KV store...
May 07 12:44:06 ip-10-99-32-10.eu-west-1.compute.internal consul-backup.sh[17257]: 2019/05/07 12:44:06 [Success] Backed up 146 keys from /
May 07 12:44:06 ip-10-99-32-10.eu-west-1.compute.internal consul-backup.sh[17257]: 2019/05/07 12:44:06 [Success] Backed up 2 ACL tokens fr
May 07 12:44:06 ip-10-99-32-10.eu-west-1.compute.internal consul-backup.sh[17257]: Keep your backup and signature files in a safe place.
May 07 12:44:06 ip-10-99-32-10.eu-west-1.compute.internal consul-backup.sh[17257]: You will need both to restore your data.
May 07 12:44:07 ip-10-99-32-10.eu-west-1.compute.internal consul-backup.sh[17257]: [231B blob data]
May 07 12:44:07 ip-10-99-32-10.eu-west-1.compute.internal consul-backup.sh[17257]: [237B blob data]
May 07 12:44:08 ip-10-99-32-10.eu-west-1.compute.internal consul-backup.sh[17257]: [239B blob data]
May 07 12:44:08 ip-10-99-32-10.eu-west-1.compute.internal consul-backup.sh[17257]: [247B blob data]
May 07 12:44:08 ip-10-99-32-10.eu-west-1.compute.internal systemd[1]: Started Backup consul KV store.

/approve
/lgtm
/unassign
/assign @JoshVanL


World model

I just did a merge and squash for your branch into my dqn branch, so i could get your  world_models.py.
ill going to squash my own past unimportant commit later to keep thinks concise and meaningful
you are welcome to dev in my branch, our stuff doesn't conflict.
btw, note from Anthony
Terminal 1: Launch turtlebot.launch
Terminal 2: run python tf_node.py in old_scripts
Terminal 3: Launch navigation.launch
Terminal 4: run this file
source workspace in each terminal
ie: cd .../far_ws && source devel/setup.bash


Update vertx-s2i-all.json

This will avoid conflict if another ImageStream called centos is deployed

Thanks !


NumPy compatible serialization API

Description
Adopt NumPy and SciPy serialization formats for npx save functions.
See https://docs.scipy.org/doc/numpy-1.10.4/neps/npy-format.html for details.
Fixes https://github.com/apache/incubator-mxnet/issues/18667 if users use the npx.save / npx.savez functions.
Loading legacy parameter formats is still supported. Saving legacy parameter formats is still supported via nd.save.
Note that npx functions do not support to save / load npz format from cloud storage (S3, Azure, ...) but contributions adding the feature are welcome.
Compared to the prior implementation of npx save / load functions, legacy NDArrays (including sparse arrays) can now also be saved to the npy / npz formats by calling the npx functions with a legacy NDArray argument.

@yajiedesign @zhreshold any idea why this fails on Windows-CPU with
[2020-11-13T01:24:44.124Z] >       check_call(_LIB.MXNDArraySave(c_str(file), mx_uint(len(handles)), handles, keys))
[2020-11-13T01:24:44.124Z] E       OSError: exception: access violation writing 0xFFFFFFFFAAA338B0

when opening / saving a zip file via libzip?
Also any idea why on the Windows GPU builds the include directories get lost and we obtain compile error like
[2020-11-12T02:47:08.659Z] ..\src\c_api\c_api.cc(63): fatal error C1083: Cannot open include file: 'zip.h': No such file or directory

even though there is no issue finding the include files on Windows CPU build?

The build-time failure on gpu windows builds is resolved. Only the "access violation writing" on windows remains.

Access violation was due to MXNet building with WIN32_LEAN_AND_MEAN option on Windows.

@mxnet-bot run ci [unix-cpu]

@mxnet-bot run ci [centos-gpu]

@mxnet-bot run ci [centos-gpu, windows-gpu]


Update dotnet.yml

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.642%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1525

Relevant Lines:
1545

💛  - Coveralls


Backlog Badge

As per https://github.com/waffleio/waffle.io/issues/1294 we're not able to count backlog items (because they do not have a label). The readme currently has an incorrect backlog badge. I would like to somehow fix the issue as opposed to removing the badge. I wondered if it was possible to use shields.io in a similar manner to the waffle.io badges (specify relative repo details and the badge will perform the respective count on the fly) but I don't believe that's how the shield.io badges work. :unamused:
This should be completed as part of the README work in  #104.

Never mind, I'm a total pleb and didn't see the correct usage of the shields.io stuff:
https://img.shields.io/github/issues/compose-net/compose.svg?style=flat for example. (It.s confusing because it defaults to the shields/badges repo which looks like a normal part of the url!).
I've updated the current readme given the repo relocation, but I'll leave the issue open as a reminder for #104.


[DOCS] Fix formatting in README

Description
The title of the features are not bolded. We can bold them to make them clearly visible and separate them from their descriptions.
Screenshots

Additional information
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I have checked the existing issues
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

Description
The title of the features are not bolded. We can bold them to make them clearly visible and separate them from their descriptions.
Screenshots

Additional information
No response
Record

[x]  I agree to follow this project's Code of Conduct
[x]  I have checked the existing issues
[x]  I'm a GSSoC'23 contributor
[x]  I want to work on this issue

you can work on this!


Caching original dataone sources

I wrote the base code to get the original sources for dataone into a dictionary for 120 seconds.
I was hoping to get a review on the caching of the dictionary. Thanks!

I would work on pulling the original sources from gleaner and write tests for both of them.

i added tests for the dataone original sources.
I also fixed the authors showing as an array to showing each author in the list.
I tried adding it to the other pull request but it was closed before I could add it so I added it here.
I am not sure i know how to query the original source for the repos in gleaner

The gleaner original sources would come from the prov stuff that I sent you (on slack I think) - but that's ok, those can happen as a follow- on.


local api Spotify mute/unmute can't be used if NAudio is already instancied

Hi
just to let you know that any methods using naudio can't be used if the project using this api is already using it and has an instance of it running, so maybe add a message to the throw error to let the dev know to use its own naudio instance and find the process by himself, or provide a method that returns the spotify process id or session audio end point device id in the list

This API is not hooking into any NAudio stuff, it's just relying on the windows API, which can be seen here:
https://github.com/JohnnyCrazy/SpotifyAPI-NET/blob/35b531ec2bda6863118c2b61b8a9f572c062459e/SpotifyAPI/Local/VolumeMixerControl.cs

ex.Message = "Unable to cast object of type 'NAudio.CoreAudioApi.Interfaces.MMDeviceEnumeratorComObject' to type 'MMDeviceEnumerator'."
looks like NAudio is the source of the issue

by the way, thanks a lot the this api, it's a time saver

Are you 100% sure this is related to this API? I would need some steps to reproduce this, but I doubt I can help here, NAudio is not of my internal stuff.
Thanks for your kind words :) 👍

no i'm not 100% sure, but i always stay connected to the volume mixer using naudio, so that's why i guess no more than one library can use the volume mixer at the same time (windows api is probably used by naudio as well). you can close this issue if you want

also, i changed my mind about muting spotify while it plays an ad, because i experimented the same as #160 , it did not trigger the OnTrackChanged event after the ad. I did not have a chance to try the test build you uploaded in #241, cause ads show randomly. The next build might solve that first issue

Report back if there is anything which is not working like expected :thumsup:


Allow the omission of head in setSelections

This PR sets the default head to anchor in setSelections(), similar to setSelection().
I think it should have been this way to ensure the API is consistent.
I'm more concerned about someone reading the latest docs but using an older version of CM that doesn't support this. Not sure how this is dealt with generally.

Good idea. The docs simply describe the latest version, that's not been a big problem so far.


desktop duplication with dxgi + ffmpeg to create video

I am trying to record video using dxgi.. though using Desktopcapturing example i can get up to 10-15 fps. :/ am i using wrong way to achieve screen capturing.. can someone help me or point me on what to study and practice to achieve faster capturing?
i am also using ffmpeg with image2pipe and memorystream to send the bitmap :/

Take a look at Captura.
https://github.com/MathewSachin/Captura


[formal/conn] Move from top_earlgrey to chip_earlgrey_asic

This PR moves formal connectivity test top-level: from top_earlgrey to
chip_earlgrey_asic. This will help check the connectivity of blocks
like AST and Pinumx.
Signed-off-by: Cindy Chen<EMAIL_ADDRESS>

Hi all, the latest force push fixes a false comb loop issue.


Add workaround for conda version in Github Actions runner image

Recent actions using the latest environment have been failing - see recent example of the scheduled run.
The CI job actions aren't currently failing on metoppv, but this is because they're using existing caches. These CI jobs will also start to fail if the caches become stale and get regenerated. As an example, this happened on my personal fork.
This failure seems to be due to the conda version packaged in the current version of the runner VM images from Github Actions not working with mamba. See actions/runner-images#6910 for details.
Testing:

[x] Ran tests and they passed OK

Another way around this problem could be to change over to conda-libmamba-solver rather than installing and using the mamba CLI.

I'm happy to switch to libmamba solver now - looks like it's the preferred solution.

I went to bump the cache number and force caches to be regenerated after the changeover to libmamba-solver, but there is now a web interface to do this rather than needing to commit a change in the repository. See https://github.com/metoppv/improver/actions/caches and click on the bin icons.
This change fixes #1334.

...there is now a web interface to do this rather than needing to commit a change in the repository...

Oooh finally!
Good spotting :)

Given that CI is broken right now without this and we have PRs from the science team and two approvals here, I'm going to go ahead and merge.
Hope that's OK.
Thanks again @tjtg


Google image V14 ,Kubernetes /KOPS Cluster on AWS is very slow

we were able to use above example KOPS cluster and able to bring up the cluster( 6 ec2 nodes), we tried with both EBS & EC2 Instance storage but writing data to root  and  they both work . but when we we do a stress test on this performance seems  very low.
using both instance storage & EBS storage,
few stats : queue length is very low "0.06"
and OPS Stats
Results:
Op rate                   :      966 op/s  [WRITE: 966 op/s]
Partition rate            :      966 pk/s  [WRITE: 966 pk/s]
Row rate                  :      966 row/s [WRITE: 966 row/s]
Latency mean              :   51.2 ms [WRITE: 51.2 ms]
Latency median            :    7.8 ms [WRITE: 7.8 ms]
Latency 95th percentile   :  103.2 ms [WRITE: 103.2 ms]
Latency 99th percentile   :  198.3 ms [WRITE: 198.3 ms]
Latency 99.9th percentile :  298.3 ms [WRITE: 298.3 ms]
Latency max               :  601.4 ms [WRITE: 601.4 ms]
Total partitions          :    100,000 [WRITE: 100,000]
Total errors              :          0 [WRITE: 0]
Total GC count            : 0
Total GC memory           : 0.000 KiB
Total GC time             :    0.0 seconds
Avg GC time               :    NaN ms
StdDev GC time            :    0.0 ms
Total operation time      : 00:01:43
we tried to compare the performance kubernetes 1.4.8 & Cassandra 3.9 which is our current working cluster which give 20,000 OP/sec
our KOPS statefulset cluster capacity is same as Above Kuberentes 1.4.8 with  same cassandra.yaml settings
but cassandra performance on kubernetes 1.4.8 Perf seems much better than 1.9 KOPS
anybody faced similar issue ?
also is there a way to benchmark network performance of KOPS cluster vs kubernetes 1.4.8

/remove-lifecycle rotten

CI job also taking long time to build and returning time out, for 1 or two times


musikcubed doesn't recognize screen-256color terminal string?

When using screen-256color musikcube launches successfully but falls back to a default color scheme (instead of my custom true color scheme) but works fine with TERM=xterm-256color musikcube.
When I pass in, say, TERM=foobar musikcube, it fails to set up a terminal with:
warning: Could not set up terminal.
warning: TERM environment variable set to 'foobar'.
warning: Check that this terminal type is supported on this system.
warning: Using fallback terminal type 'ansi'.
warning: Could not set up terminal.
warning: TERM environment variable set to 'foobar'.
warning: Check that this terminal type is supported on this system.
warning: Using fallback terminal type 'ansi'.
fish: Job 1, 'TERM=foobar musikcube' terminated by signal SIGABRT (Abort)

The above error seems to be similar to the output of tput, but tput outputs 256 for both xterm-256color and screen-256color.
I dug around in the code a little trying to understand where musikcube was getting its info but other than Colors.cpp I wasn't sure.

xterm-256color definitely works for me in both macOS (with iTerm and Terminal.app) and Linux using the various terminal emulators I have installed.

Can you tell me a bit more about which operating system and terminal you're using?

Oops, sorry, I misread the original post. Hmm, I'm not sure why it wouldn't support screen-256color -- I'll have to play around a bit with it... but like I mentioned in the previous post, the app relies on ncurses for color mode capabilities detection.

Yeah it's weird, it's the only app I've used with this problem. It could be that my other terminal apps are forced to true color, or don't check? I'm not sure. If you can think of something that would give me similar results, or something I can run to extract what ncurses is telling musikcube I'll do that to help figure it out.
I'm on Solus Linux, fully updated. It ships with Gnome Terminal:
Linux monolith 5.14.21-210.current #1 SMP PREEMPT Sun Dec 5 21:23:09 UTC 2021 x86_64 GNU/Linux

Version 3.42.1 for GNOME 41
A terminal emulator for the GNOME desktop
Using VTE version 0.64.2 +BIDI +GNUTLS +ICU +SYSTEMD

Hey, thanks for the great program!
Just to say that on my home server - where I do not run X there is no possibility to change the colour scheme. I mean the terminal is the real terminal. Is it supposed to be like that or am I missing something?
Thanks
R


Add pin command

Codecov Report

Merging #105 (b0aa7a3) into master (ea84335) will decrease coverage by 2.40%.
The diff coverage is 6.32%.

@@             Coverage Diff              @@
##             master     #105      +/-   ##
============================================
- Coverage     70.29%   67.88%   -2.41%
- Complexity      466      473       +7
============================================
  Files            79       84       +5
  Lines          1451     1529      +78
  Branches        157      164       +7
============================================
+ Hits           1020     1038      +18
- Misses          389      447      +58
- Partials         42       44       +2

Impacted Files
Coverage Δ

...seedu/trackascholar/logic/commands/PinCommand.java
0.00% <0.00%> (ø)

...u/trackascholar/logic/parser/PinCommandParser.java
0.00% <0.00%> (ø)

...rackascholar/logic/parser/TrackAScholarParser.java
80.95% <0.00%> (-4.05%)
:arrow_down:

src/main/java/seedu/trackascholar/model/Model.java
100.00% <ø> (ø)

...n/java/seedu/trackascholar/model/ModelManager.java
96.15% <ø> (ø)

.../java/seedu/trackascholar/model/TrackAScholar.java
86.20% <ø> (ø)

...kascholar/model/applicant/UniqueApplicantList.java
83.67% <ø> (ø)

...c/main/java/seedu/trackascholar/ui/MainWindow.java
0.00% <0.00%> (ø)

src/main/java/seedu/trackascholar/ui/PinCard.java
0.00% <0.00%> (ø)

src/main/java/seedu/trackascholar/ui/PinList.java
0.00% <0.00%> (ø)

... and 3 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

LGTM!