color not working on Windows PowerShell

Note: this issue was imported from https://github.com/wercker/stern/issues/69, but it was originally created by tw0517tw...
It looks

Note: this comment was imported, but it was originally made by teddyber...
any idea when this can be fixed? i'm stuck on a windows box these days and i miss those colors :'(

Note: this comment was imported, but it was originally made by tw0517tw...
@teddyber I've changed my console to the newer and open sourced PowerShell https://github.com/PowerShell/PowerShell and found it supports the color codes used in stern. maybe you can give it a try?

Note: this comment was imported, but it was originally made by teddyber...
thanks for the tip but unfortunately, it didn't work. in the meantime i installed a linux distro through WSL and i have a colored stern :-)

Note: this comment was imported, but it was originally made by tw0517tw...
https://github.com/microsoft/terminal
maybe my color is from using new Windows Terminal

Note: this comment was imported, but it was originally made by derekrprice...
@tw0517tw I chose to enable ANSI color for PowerShell in my registry, per this SO answer, which fixed this problem for me.  Per the same answer, it might be possible to fix it in the Stern code too, if the GO implementation supports the Windows API call.


Template to search multiple fields

I am attempting to search on multiple fields, (SKU -OR- description), but it seem to only ever search on the itemTextField
It properly shows the template when searching, but just doesn't allow you to search on the SKU
  <ion-item>
    <ion-label>SKU</ion-label>
    <select-searchable item-content [items]="supplierItems" itemValueField="ItemId" itemTextField="Description" [canSearch]="true">
      <ng-template selectSearchableTitleTemplate>
        SKU
      </ng-template>
      <ng-template selectSearchableItemTemplate let-item="item">
        ({{item.SKU}}) {{item.Description}}
      </ng-template>
    </select-searchable>
  </ion-item>

Is there a way to make ionic-select-searchable search on multiple fields?
Thanks in advance (great plugin)

Hello @TrevorLinkgreen. The component doesn't know anything about your search logic and the templates simply renders your items.
However, you can implement any search functionality in your onSearch event.
Here's how:
https://stackblitz.com/edit/ionic-select-searchable-on-search?file=pages%2Fhome%2Fhome.html

Perfect, thanks


Issue with TSImageUploadControl - Default image not found error

I've deployed the TSImageUploadControl code from github. The upload is working fine. However the default image is not being set. I'm getting the error "Image not found" in this line
this._context.resources.getResource(DefaultImageFileName, this.setImage.bind(this, false, "png"), this.showError.bind(this));
After the call to getResource, the error function showError is called which displays the image not found message. I can see the default.png in the "img" folder. I'm unable to find the actual exception that is thrown by getResource. Are you able to help?

Thanks for the feedback. Please raise the issue in the community forum. Our developers will help you resolve the issue. Closing the issue.

Thanks @Nkrb . I've posted the issue here - https://powerusers.microsoft.com/t5/Power-Apps-Pro-Dev-ISV/Issue-with-PCF-TSImageUploadControl-Default-image-not-found/td-p/641777
Hope someone from dev team can pick this. Looks like a bug

I've reopened the issue as I  haven't got any help from the community. Hope you can look into this


CloudWatch logs can not be enabled with Amazon MQ for RabbitMQ

CloudWatch logs can't be enabled with Amazon MQ for RabbitMQ. It will throw an error even when you don't specify the audit logging which is only supported with ActiveMQ. This is a Terraform bug which should be fixed in Terraform 3.38.0: https://github.com/hashicorp/terraform-provider-aws/issues/18067
Expected behavior
CloudWatch logs gets enabled by defining:
logs=aws.mq.BrokerLogsArgs(
    audit=None,
    general=True,
),

I have also tried to not define the audit at all. Documentation states that False is the default: https://www.pulumi.com/docs/reference/pkg/aws/mq/broker/#brokerlogs
I have also tried to define it as False but the same error rises.
Current behavior
Throws an error:
aws:mq:Broker (rabbitmq):
    error: 1 error occurred:
    	* updating urn:pulumi:dev::********::aws:mq/broker:Broker::rabbitmq: 1 error occurred:
    	* error updating MQ Broker (b-1493e1ab-919a-4743-b83d-de0ddf8f214a) configuration: BadRequestException: Audit logs are not supported for RabbitMQ brokers.
    {
      RespMetadata: {
        StatusCode: 400,
        RequestID: "f50eeafd-fdc9-419e-a9ae-d872b2ea74d4"
      },
      ErrorAttribute: "logs.audit",
      Message_: "Audit logs are not supported for RabbitMQ brokers."
    }

Steps to reproduce

Define aws.mq.Broker with engine_type="RabbitMQ" with engine_version="3.8.11"
Use apply_immediately=True
Pulumi up

Context (Environment)
AWS Console has only a toggle disabled/enabled. It works fine there.

This is a Terraform bug which should be fixed in Terraform 3.38.0: hashicorp/terraform-provider-aws#18067

Version 4.2.0 of the Pulumi AWS provider includes version 3.38.0 of the upstream Terraform AWS provider.  So this should be available now in the latest package releases.
If you are still seeing this with the latest package, please do repopen and reconfirm whether this is the same issue as hashicorp/terraform-provider-aws#18067.


Update to latest cppwinrt version results in winrt headers not generated in Generated Files

Hi cppwinrt team,
While trying to update cppwinrt nuget package to latest version (2.0.220418.1) for project and it's dependencies, project build started failing with:
Error	C1083	Cannot open include file: 'winrt/base.h': No such file or directory

If I check obj/Generated Files dir, I can see that winrt dir with headers is missing there, i.e. Generated Files dir is empty. You can find the code here:
https://github.com/microsoft/PowerToys/tree/stefan/vcm_cppwinrt_update
Check the latest commit for changes. Without latest commit, building VideoConferenceModule project (src\modules\videoconference\VideoConferenceModule\Video Conference.vcxproj) is passing and winrt headers are preseng in Generated Files/winrt.

Apparently, this fixes the issue:

Feel free to close it :)


Sync on complete always returns TRUE cached flag.

On the first run of the app I am running
var sync = ContentSync.sync({id: 'app', type: 'local'});
sync.on('complete', function(data) {...
just to check if the app has cached data, and it properly responds with error
on the second and next runs however I am always getting data.cached=true, even though no data has been cached, which ends up with fatal error ERR_FILE_NOT_FOUND.

Hi @kleeb
What version of the plugin are you using and on which platform?

I am checking the latest version on Android 6.
And this looks weird for Android:
result.put(PROP_CACHED, type.equals(TYPE_LOCAL))
isn't it always true when we choose local sync?
Shouldn't it be more something like:
result.put(PROP_CACHED, new File(outputDirectory + "/www/").exists()) ?


fix the scroll behavior of pivot table in dashboard and edit view

".widget.pivot_table" selector doesn't exist anymore.
".chart-container .pivot_table" exists both in dashboard and explore/edit view.
".widget .pivot_table" exits in dashboard.

this seems to break vertical scrolling in the edit/explore view.

closing in favor of https://github.com/airbnb/superset/pull/2674


Can't use o1-preview model

I get the following error for o1-preview.
copilot Error: The requested model is not supported.

I updated the model selection settings as follows and tried it.
;;  OpenAI models: https://platform.openai.com/docs/models
(defcustom copilot-chat-model "gpt-4o"
  "The model to use for Copilot chat."
  :type '(choice (const :tag "GPT-4o" "gpt-4o")
                 (const :tag "Claude 3.5 Sonnet" "claude-3.5-sonnet")
                 (const :tag "o1 (Preview)" "o1")
                 (const :tag "o1-mini (Preview)" "o1-mini"))
  :group 'copilot-chat)

I get the following error for o1-preview.
copilot Error: The requested model is not supported.

I updated the model selection settings as follows and tried it.
The claude-3.5-sonnet responded as expected. I did not change the settings here in the first place.
The o1 returned the same error. I also tried o1-ga, but it was the same.
I waited for o1-mini for about 10 minutes and it did not return any response or error.
o1 must be enabled in my account.

If the problem is simply that it is not enabled, then o1-mini should return the same error as o1.
The situation is not clear to me.

Did you try with o1-preview instead of just o1 ? The vim plugin seems to use that
There also seems to be some extra handling for o1 such as not sending some parameters, so beware

Sorry, my explanation was a bit lacking.
The original choice was o1-preview, so I first tried using that to set up the model, but it didn't work, so I tried o1 and others.


minor: Remove dead assists-related function

Unless I'm missing something, assists_with_fixes seems to be always used and ends up in the same code path.

bors r+


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/58712

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/59261

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/61140

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/61143

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/62071

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/62087

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/62157

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/66898

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/74151

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/103892

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106305

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106308

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/107094

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/113691


Create component Grafana dashboards

Each application component in the architecture exports Prometheus metrics. Create a Grafana dashboard for each component that shows relevant metrics (for example: heap metrics in Java). These should be stored with each respective component as a JSON file.

Can you please assign this task to me.


Kotlin Native IncorrectDeferenceException when calling 3.x apollo on a background thread.

Summary
Kotlin Native IncorrectDeferenceException when calling 3.x apollo on a background thread.
Version
3.1.0
Description
In 3.x+ this code will crash with the error message Uncaught Kotlin exception: kotlin.Throwable: The process was terminated due to the unhandled exception thrown in the coroutine [StandaloneCoroutine{Cancelling}@83a05a48, MainDispatcher]: Non-main native call
val query = AnyQuery()
return flowOf(1)
    .map { myApolloClient.query(query).execute() }
    .flowOn(Dispatchers.Default)

This code will crash with the error message Uncaught Kotlin exception: kotlin.native.IncorrectDereferenceException: illegal attempt to access non-shared <object>@8239c448 from other thread
IncorrectDereferenceExceptions are incredibly difficult to track down in large projects, so maybe this could throw a Non-main native call exception like the previous code sample?
val query = AnyQuery()
return myApolloClient.query(query).toFlow()
    .flowOn(Dispatchers.Default)

Switching the flowOn dispatcher to Main in either case will make everything work as intended 👌  - example below
val query = AnyQuery()
return myApolloClient.query(query).toFlow()
    .flowOn(Dispatchers.Main)

Other info which may of may be useful?

No exceptions were thrown when triggering apollo calls on a background thread in versions pre-3.x
The clients created on the main thread
We're using native-mt coroutines
This maybe relates to #2916

I'm mostly opening this is a reference if anyone runs into similar issues, as the problem will probably go away as soon as the new memory model becomes stable in Kotlin Native.
If there is a simple fix to avoid IncorrectDeferenceExceptions that could potentially be quite handy though 👌

Indeed, there is a requirement that requests execute on the Main dispatcher on native. That doesn't mean that the request is going to block the main thread. Both cache and network delegate to a worker thread so it is fine to call execute() from the main thread.
The tldr; of why there is such a limitation is that for a while we didn't want to force the native-mt version of coroutines on users and that workers need a "known" thread to give control back to. You can read more about it there.
This will change with the new memory model but until it is there, you can call execute() from the main thread. Let us know if there are strong reasons not to do so but we haven't found any so far.
All that being said, we could make the error message better. I'll look into this.

This will change with the new memory model but until it is there, you can call execute() from the main thread. Let us know if there are strong reasons not to do so but we haven't found any so far.

No strong reasons, it just means we need to do a bit of thread switching in our api layer, so it's a tad bug prone as these errors only show at runtime on iOS.
Once the new memory model is stable, will apollo need an update before removing the main thread restriction on native?

Gotcha 👍 . For the record, on Android execute() is meant to be called from the main thread too. It will dispatch internally so you could in theory use the same kind of threading model for both iOS and Android and leave ApolloClient offload cache/network work to other threads.

Once the new memory model is stable, will apollo need an update before removing the main thread restriction on native?

Yes, most likely. Certainly not a huge update but removing the assert comes to mind. Maybe a few other small things.

Closing this one in favor of https://github.com/apollographql/apollo-kotlin/issues/4100


Add percona pxc operator repository

The Artifact Hub, a CNCF sandbox project, is another place you can list your repos. To do that, you login (or create an account), create an organization, and list your repository. You can link it to a user or organization.


[CI] Cancel previous build if a new commit is pushed to a PR

cc @jroesch @tmoreau89 @ZihengJiang

🎊


Need the Scan QR from Dapp Browser function back

Can put it here before we have a better design.

@farrahfazirah can think about a better design

Need to replace the switch camera button with Album(check a qr from photo in album)

@hboon @James-Sangalli same for Andriod @JamesSmartCell

Following up with #1097

@tomekalphawallet current design. Photos text not visible with white background


Windows 8.1

Change text and color in windows 8.1

Changing text now works on Windows 10, which is better :)


[BUG] rapids user is causing permissions issues

The rapids user is causing issues as outlined in the following thread: https://github.com/rapidsai/dask-cuda/issues/412.

rapids user has been removed in #186. closing issue


Linkis management console, administrator page ECM and micro service management how to open?

Search before asking

[X] I searched the issues and found no similar issues.

Linkis Component
linkis-commons
What happened + What you expected to happen
Linkis management console, administrator page ECM and micro service management how to open?
Linkis管理台，管理员页面ECM和微服务管理怎么开启？
Relevent platform
nothing
Reproduction script
nothing
Anything else
This question comes from the QA documentation of the Linkis community
QA Doc Link：https://docs.qq.com/doc/DSGZhdnpMV3lTUUxq
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

解决方案：需要在conf/linkis.properties文件里面设置管理员：wds.linkis.governance.station.admin=hadoop,peacewong
设置完成后，刷新即可。
solution：need to be in the conf/linkis. The properties files inside set administrator: WDS. Linkis. Governance. Station. Admin = hadoop, peacewong
After setting, refresh.


Markdown Parsing Error: Text that ends with a break line and a hyphen returns only a bullet point

Steps to reproduce
By using the latest version of the package flutter_markdown: 0.7.4+1
and using the class MarkdownBody and passing to the data parameter
a text that ends with a line break and a Hyphen, for example:
Best Regards,
Sally McMahon
-

The result deletes the text previous to the Hyphen, and only shows a bullet point, the result will be:
•

Expected results
Is expected to not delete the previous text to the hyphen,
Best Regards,
Sally McMahon
•

Actual results
it deletes the previous text to the hyphen
Code sample
`const MarkdownBody(
      data: '''
Best Regards,
Sally McMahon
-
''',
    );`

Screenshots or Video

With break line and hyphen the text is removed:

Without the break line the text is shown:

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.19.6, on macOS 14.7 23H124 darwin-arm64, locale en-ES)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[!] Xcode - develop for iOS and macOS (Xcode 15.4)
    ✗ Unable to get list of installed Simulator runtimes.
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.3)
[✓] IntelliJ IDEA Community Edition (version 2023.2.5)
[✓] VS Code (version 1.94.2)
[✓] Connected device (3 available)
[✓] Network resources

! Doctor found issues in 1 category.
luis.garcia@MAC-LGARCIA lodgify-flutter % flutter doctor -v
[✓] Flutter (Channel stable, 3.19.6, on macOS 14.7 23H124 darwin-arm64, locale en-ES)
    • Flutter version 3.19.6 on channel stable at /opt/homebrew/Caskroom/flutter/3.16.5/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 54e66469a9 (6 months ago), 2024-04-17 13:08:03 -0700
    • Engine revision c4cd48e186
    • Dart version 3.3.4
    • DevTools version 2.31.1

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

[!] Xcode - develop for iOS and macOS (Xcode 15.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15F31d
    ✗ Unable to get list of installed Simulator runtimes.
    • CocoaPods version 1.15.2

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

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

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

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

[✓] Connected device (3 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554 • android-arm64  • Android 14 (API 34) (emulator)
    • macOS (desktop)             • macos         • darwin-arm64   • macOS 14.7 23H124 darwin-arm64
    • Chrome (web)                • chrome        • web-javascript • Google Chrome 130.0.6723.70

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

! Doctor found issues in 1 category.

</details>

@luismalodgify
I tried the code sample using latest stable version on Android emulator in which it displays the text properly, as shown below:

 runnable code

import 'package:flutter/material.dart';
import 'package:flutter_markdown/flutter_markdown.dart';
import 'package:markdown/markdown.dart' as md;

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

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
        visualDensity: VisualDensity.adaptivePlatformDensity,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key? key, required this.title}) : super(key: key);
  final String title;
  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: Center(
          child: MarkdownBody(
              data: '''
              Best Regards,
              Sally McMahon
              -
''',
          )
      ),
    );
  }
}

Please upgrade to latest stable and use above to check and confirm.

Hello @darshankawar, thank you so much for the fast reply,
The error is not related to the Android Emulator, check the video please, if you remove the space previous to the text the issue is reproducible:
https://github.com/user-attachments/assets/fc98d76f-2882-4f4e-8f71-fa62e68d45c1
if the space is included, the issue is reproducible, also with the space it change the text format, it looks like console text
child: MarkdownBody(
              data: '''
              Best Regards,
              Sally McMahon
              -
''',
)

Thanks for the update. I do see the same behavior as reported with and without space. If there's no space after newline, then the text is not displayed, instead a dot is shown. Also, if there's three tabbed space between each newline, then only the text is displayed as-is.
Below works:
const String data = '''
    Best Regards,
    Sally McMahon
    -
''';

This doesn't:
const String data = '''
Best Regards,
Sally McMahon
-
''';

stable : 3.24.3
master : 3.27.0-1.0.pre.259


Can't minimize Riot app on macOS using standard keyboard shortcut

On macOS, ⌘+M is a reserved shortcut for minimizing any window. To many users, It's a very familiar shortcut. The riot app hijacks ⌘+M and uses it for enabling/disabling Markdown editing in the compose window. I suggest replacing the shortcut with something like ⇧+⌘+M.

This repo is for Riot on iOS, you are looking for https://github.com/vector-im/riot-web/ and https://github.com/vector-im/riot-web/issues/5165 has already been filed for this


example for array use

Hi, how do I use this library to put data in msgpack array?
for example i would like to create a nested array like this:
[ 1, [1,2,3]]
Thanks

hi,
i'm not longer support this library.
When I left it, it didn't supported nested array, due to bad documentation about how the protocol acts.
I keep the sources available for anyone who wishes to continue develop upon it.


ModelicaExternalC not compatible with hdf5 1.10

Reported by perost on 31 May 2016 14:05 UTC
ModelicaExternalC doesn't build with the latest release of the hdf5 library, since the arguments to the macro H5Rdereference has changed¹. When trying to build ModelicaExternalC (using autotools) I get the following errors with hdf5 1.10:
../../C-Sources/ModelicaMatIO.c:18392:69: error: too few arguments to function call, expected 4, have 3
                ref_id = H5Rdereference(dset_id,H5R_OBJECT,ref_ids+i);
                         ~~~~~~~~~~~~~~                             ^
/usr/include/H5Rpublic.h:63:8: note: 'H5Rdereference2' declared here
H5_DLL hid_t H5Rdereference2(hid_t obj_id, hid_t oapl_id, H5R_type_t ref_type, const void *ref);
       ^
<... several more errors saying the same thing ...>

¹ https://www.hdfgroup.org/HDF5/doc/RM/RM_H5R.html#Reference-Dereference

Migrated-From: https://trac.modelica.org/Modelica/ticket/2001

Comment by beutlich on 31 May 2016 14:29 UTC
This is a duplicate of https://github.com/tbeu/matio/issues/37. It will be fixed by the provided patch (upstream) once matio v1.5.7 is released such that I can merge it to the external C code.

Modified by beutlich on 31 May 2016 19:31 UTC

Comment by beutlich on 21 Jun 2016 19:58 UTC
Resolved by ab69b8c1c2de2b7406d2a79f9a850c98020aca90. Sorry for the delay.

Changelog modified by beutlich on 21 Jun 2016 19:58 UTC
Updated matio library to v1.5.7 (ModelicaMatIO.[ch])

Comment by beutlich on 3 Jul 2016 20:10 UTC
Updated ModelicaMatIO.[ch] to v1.5.8 by 4ae6fed3f1420af0d77c463231d22e23c099da74.

Changelog modified by beutlich on 3 Jul 2016 20:10 UTC
Updated matio library to v1.5.8 (ModelicaMatIO.[ch])

I got this error today.

I got this error today.

Already fixed.


Feat: Add Finnish translation

Summary
Creating the Finnish translation
Closing Issues
Fixes #160
Types of changes

[x] I have read the CONTRIBUTING document.
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Improvements to existing code, such as refactoring or optimizations (non-breaking)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

@Sadeedpv thank you for contributing. I just merged this. I'll create a release later this week that will include it.

@Sadeedpv I just released v1.21.0 that includes this translation (also available via major tag v1). 🚀 Thank you again for contributing.


We should create a database for all the msgf+ jobs

Description of feature
Originally reported by @jpfeuffer
Description of feature
E.g. for MSGF+ we can first create the index for the database and then pass it to every ID step. Might need some customization in the OpenMS adapters.
This will decrease a lot the time for msgf+ compute.

@daichengxin in the next PR, would be nice to include this feature. Every time msgf+ is used, it would be relevant to save space and time/cpu resources to have only one job before all the msgf+ that creates the database for all the msgf+ and it passed to all processes.


[BUG] 微调时多轮对话数据格式问题

是否已有关于该错误的issue或讨论？ | Is there an existing issue / discussion for this?

[X] 我已经搜索过已有的issues和讨论 | I have searched the existing issues / discussions

该问题是否在FAQ中有解答？ | Is there an existing answer for this in FAQ?

[X] 我已经搜索过FAQ | I have searched FAQ

当前行为 | Current Behavior
使用 lora单卡微调 对话采用多轮格式 对话数据约2000条 LR：3e-4  epoch：5和10
期望行为 | Expected Behavior
No response
复现方法 | Steps To Reproduce
No response
运行环境 | Environment
- OS:
- Python:
- Transformers:
- PyTorch:
- CUDA (`python -c 'import torch; print(torch.version.cuda)'`):

备注 | Anything else?
使用的多轮对话没有按照user assistant 一问一答，会有多个user对应一个assistant或多个user对应一个assistant，这样格式的数据会对微调效果有影响吗，微调出的模型合并后能够正常问答，但是对于提示词的指令遵从效果不好，有时候不会按照指令执行，而是直接输出微调中的某些数据。

微调后的模型也跑了测评集ceval之类的  评分只下降了一点点 1.8B 7B 14B都试过  都有不完全遵从提示词和直接输出微调中数据的问题，是否也有可能是因为多轮对话中某一段话出现频率太高的问题   因为是客服对话数据，客服会有一些固定回答

The finetune.py does indeed support the user/assistant dialogue structure where messages can appear in an arbitrary order, but the models have not been trained on data formatted in this way.
This might imply that the model could potentially overfit to your specific dataset, where data is arranged in a novel manner.
To mitigate this issue, we recommend one of two actions:

You could revise your data to conform to the user/assistant format in a fixed order, ensuring that the model adapts appropriately during fine-tuning.
Alternatively, consider diversifying your dataset by including various conversation structures to enhance the model's adaptability and reduce the risk of overfitting to a single conversation pattern.

Please note that these suggestions are based on general best practices in machine learning and may not be a final resolution to your problem.

The finetune.py does indeed support the user/assistant dialogue structure where messages can appear in an arbitrary order, but the models have not been trained on data formatted in this way.
This might imply that the model could potentially overfit to your specific dataset, where data is arranged in a novel manner.
To mitigate this issue, we recommend one of two actions:

You could revise your data to conform to the user/assistant format in a fixed order, ensuring that the model adapts appropriately during fine-tuning.
Alternatively, consider diversifying your dataset by including various conversation structures to enhance the model's adaptability and reduce the risk of overfitting to a single conversation pattern.

谢谢，想再请教一下，用少量（几千条对话）数据lora微调（参数用的脚本默认值），模型合并后不能很好遵从提示词是正常现象吗？比如微调前让模型把输出结果转化成json格式输出没有问题，但微调后再让模型把输出结果转化成json格式完全没有效果。微调的数据里不包含json相关的内容，是需要加上吗？

The phenomenon suggests catastrophic forgetting and it could be related to the hyper-parameter settings in finetuning. Balancing the data is normally a viable way but whether it works depends on your specific usecase.


Interoperating with existing F# async

We could allow binding to an existing F# Async, passing the cancellation token through.
Similar to this in the existing AsyncSeq: https://github.com/fsprojects/FSharp.Control.AsyncSeq/blob/main/src/FSharp.Control.AsyncSeq/AsyncSeq.fs#L425

See #110 for a first attempt at this.

This has now been implemented and will be part of the 0.4.0 release cycle.


Context.Wait v4 alternative

Hi,
Is there an alternative in v4 for the context.wait method from the older versions?
I have looked through the v4 reference and I cannot find a direct replacement for this call.
Thanks

What does context.wait do? I can't find a reference to it (most of my experience is with v4).
If my understanding of it is correct than the await call used everywhere in v4 code does the same thing and is an integral part of the bot working.

@Jhanbury Thank you for your question.  We like to keep the issues section of the repo for defects or product feature request.  How to questions are best served by our support team over on Stack Overflow
For product behavior, how-to, or general understanding questions, please use Stackoverflow.
https://stackoverflow.com/search?q=bot+framework

@Jhanbury Please take a look at this question here. That might help in understanding it better. If you need further assistance, please create a new question in StackOverflow as Scott mentioned.

@sgellock @dmvtech my apologies, thanks for the help


Malware in this program?

My Instagram account was hacked (for the first time ever) shortly after (unsuccessfully) trying this program for the first time. The password of the e-mail account associated with it (which I also enter in using the same browser) was unaffected, as were the other accounts and programs I use on my computer, leaving this program (in which I entered only my Instagram login info and nothing else) as the primary culprit. Is it possible that malware has slipped into the binaries of this program?

I downloaded it from that site and the binary came from Github's servers.

Same situation, downloaded from the website, got my insta hacked a few hours later.

Well thats bad to hear, i just installed it and use it for my business account, lets see if i get hacked too

@propolisor @Mozoloa how exactly do you mean your insta account was hacked? What happened to the account after you tried to login?

@ifedapoolarewaju The password was changed (with an e-mail sent notifying me of this) and my old password was invalid. I had to change it back via e-mail to regain control of the account.

the website now enforces https. https://igdm.me


Release 2.1.2

Questions
Answers

Description?
Release 2.1.2

Type?
improvement

BC breaks?
no

Deprecations?
no

Fixed ticket?
N/A

How to test?
Release Test

Hello @Progi1984,
I have tested this release and it's ok for me, I have found no regression :tada:
Thanks you !

Thanks @Progi1984 💪!
And happy birthday 🥳!


Added the sensor information to the CIMI resource schema

Added the sensor info in the CIMI schema (device)

@ssgUPC please also fix the conflicts

@ssgUPC please also fix the conflicts

sure

@cjdcordeiro fixed the conflicts

@sstanovnik I modified the schema as per your comments.

@cjdcordeiro CI is failing because of something unrelated to this PR, right?

yes it's unrelated.
I'll try to have a look at this later this week

I don't know, why always I'm facing such kind of conflicts issues ..... :(

@sstanovnik, I have already updated and changed the CIMI resource schema for device-dynamic, can you please check it.

@cjdcordeiro changed and updated


Added members list modal

Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your master!
Make sure you are making a pull request against the dev branch. Also you should start your branch off dev branch.
Check you have included issue number in your pr (e.g #23).
Check your code additions will fail neither code linting checks nor unit test.

Description
Added a members modal on project, team & office page. Issue #389

@SubodhDahal good work on that, but one thing I see here is, you're using eventbus to show the modal, but if you're importing the component why don't you pass a prop, or use a data variable on the parent component to hide and show the modal instead using eventbus. EventBus should be used sparsely, only when its absolutely necessary. On this case we can achieve our goal without using eventbus.

@Hasnayeen I've now removed the usage of the event bus and used the method you recommended. Please have a look.

Codecov Report

Merging #427 into dev will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                dev     #427   +/-   ##
=========================================
  Coverage     82.22%   82.22%
  Complexity      321      321
=========================================
  Files           106      106
  Lines          1018     1018
=========================================
  Hits            837      837
  Misses          181      181

Continue to review full report at Codecov.

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


Unable to access pdf of plan via https://dmptool.org/api/v1/plans_full for test visibility

Using the /plans_full API call, I'm able to GET the pdf of a plan  if the visibility of the plan is one of public, private, or institutional but not for test.   That is,
curl -H  "Authorization: Token token=TOKEN" https://dmptool.org/api/v1/plans_full/PLANID.pdf

returns a HTTP 401 Unauthorized error if plan with PLANID has a test visibility.
Is this intended behavior or a bug in the API.

@rdhyee The DMPTool is in maintenance mode now as all dev resources are trained on the new DMPRoadmap platform, which we tentatively aim to release later this summer. We implemented a quick-and-dirty test plan option to test things before designing something better in the new version. So we won't be fixing any issues you might find with the API unless they pose security or other serious problems. Please let me know if you're still working on the OSF integration so we can coordinate plans for the future.


adding other providers?

congrats on this great project!
I work at Radar and we have a cost effective alternative to Google Maps and Mapbox -- see here
would you be open to a PR that would add support for our maps? it would mostly consist of:

an additional input + some copy in the API Keys modal
an additional choice in the source select menu
obviously all required classes/changes

our map is based on the same standard pbf vector tiles, so the additional code in Map.tsx would be pretty minimal (i.e. it would use the same MapGL component as you're using now)
cheers!

@gregsadetsky Of course! More the merrier.


make image url match more strict

PT-187179232
This approach is still fragile. It would be better to only allow localAssets in specific cases. And then we could require the image urls have a protocol which will make the pattern even less likely to be falsely identified.
Also there are two different tests for image urls. One is in the image map. The other is in data-types.ts. The test in data-types.ts is much more strict, but it likely prevent cases where an image is dragged from another page into CLUE.

@bgoldowsky In this case I think we are OK. The only files in the domain of CLUE are public files. And even if the image is resolved against the curriculum repository those files are all public too. Some of them are teacher guides, but it is easy enough for a user to access those guides even without hacking the URL.
These patterns are for any image reference in CLUE. Users can enter in URLs as text in the datacards and tables. We don't advertise this, but if you put a URL in a table or datacard it will try to render it as an image. Another way is to drag a image from another webpage into CLUE which creates a image tile. I'm pretty sure whenever you drag an external image the browser will either try to paste the bytes or an absolute URL.

Since this doesn't change cypress tests I'm going to remove @johnTcrawford's review and merge.


[BUG] Dataset summary permissions error

Describe the bug
After the summary job is executed, the accessControlModel for each summary object should be set to public when create() is called.
Regular users have never been able to see the summary page, but it's never been reported.  I modified the database to fix for now, but the code needs to be changed

Summary feature was removed in the mongo track thing.


BITFINEX - Bitfinex_Api_Order_Book_Data_Source - Unexpected Error Occured

Describe the bug
I create Pure MM strategy with connector to Bitfinex. Then i starting the bot, the log panel showing error.
"Bitfinex_api_order_book_data_source - Unexpected error occured when listening to order book streams. Retrying in 5 seconds..."
But i check on Bifinex App, the order still created and canceled.
I create 2 bot there with hummingbot, ETC and ETH with custom config order_refresh_time : 60
ETH is working fine.
But for ETC pair seem also error in order_refresh_time, the order stuck more than 5 minutes (maybe because Bitfinex_api_order_book_data_source Error)
Steps To Reproduce

Connect to Bitfinex API
Create strategy Pure_MM
Start bot and observe log pane for error

Screenshots

Release version
Version 1.9.0
Attachments
I'm sorry don't know how to get log file.
New user in Linux OS.
Optional: your discord username:
febriyana#9115

I have the same issue, and it's not new, for the last few months.


Rename equivariant_model

It doesn't actually produce a model but a basis. So let's call it that.
equivariant_basis

But before we rush into it, let's think this through. This is the canonical construction of an equivariant ACE basis. There will be others ... so let's specify that too. So maybe the right choice is
equivariant_ace_basis

@CheukHinHoJerry @zhanglw0521  -- thoughts?

Jerry suggested equivariant_ace_descriptor which might make more sense?

But I'm ok with that too, but depends who we are talking to. I'm not convinced we should so readily give in to the ML language.
I'd be even open to just having equivariant_ace_descriptor to be the alias for equivariant_ace_basis (or vice-versa).
One more thought before you make the change: should the equivariant even be there? It's really implicit, isn't it? But I'm also ok to keep it for now ...


Added styles to handle fullscreen on near.social and properly display on near.org as well

resolves #190

https://github.com/NEARBuilders/gateway/assets/65053264/e90df080-bd83-4f9e-b0a9-8f21329216a1

@Jikugodwill if you have tested everything, can you please merge it?
It's already approved.


[Bug 🐞]:  timeout on brpop - Error while farmerbot is trying to power off a node

What happened?
One of my nodes didn't power off with the above mentioned error in the farmerbot logs.
The node started at 03:15 am and is still running 8 hours later.
Connection speed is fine, I have a VM on my always on node to check.
What did you expect?
A node that powers off after half an hour.
What browsers are you seeing the problem on?
No response
ZOS info
No response
Dashboard info
No response
weblets info
No response
Relevant log output
2024-01-15 11:09:25 [INFO ] [POWERMANAGER] Resource usage too low: 7. Turning off unused node 5643
2024-01-15 11:09:25 [DEBUG] Received job with guid 9cb5adfe-224a-4224-a20f-b469d0c8520d
2024-01-15 11:09:25 [DEBUG] Assigned job 9cb5adfe-224a-4224-a20f-b469d0c8520d to jobs.actors.farmerbot.powermanager:
2024-01-15 11:09:25 [DEBUG] jobs.ActionJob{
    guid: '9cb5adfe-224a-4224-a20f-b469d0c8520d'
    twinid: 0
    action: 'farmerbot.powermanager.poweroff'
    args: params.Params{
        params: [params.Param{
            key: 'nodeid'
            value: '5643'
        }]
        args: []
    }
    result: params.Params{
        params: []
        args: []
    }
    state: tostart
    start: 2024-01-15 11:09:25
    end: 1970-01-01 00:00:00
    grace_period: 0
    error: ''
    timeout: 0
    src_twinid: 0
    src_action: ''
    dependencies: []
}
2024-01-15 11:09:25 [INFO ] [POWERMANAGER] Executing job: POWEROFF 5643
2024-01-15 11:09:35 [ERROR] [POWERMANAGER] Job to power off node 5643 failed: timeout on brpop
2024-01-15 11:09:35 [INFO ] Elapsed time for update: 2.2195045666666666
2024-01-15 11:11:26 [DEBUG] Received error response for job with guid 9cb5adfe-224a-4224-a20f-b469d0c8520d
2024-01-15 11:11:26 [DEBUG] Returned job 9cb5adfe-224a-4224-a20f-b469d0c8520d

After restarting the farmerbot, the node shut down immediatelly.
All other were woken up.
2024-01-15 11:35:00 [INFO ] [POWERMANAGER] Resource usage too low: 7. Turning off unused node 5643
2024-01-15 11:35:00 [DEBUG] Received job with guid fe0d6b0a-285d-46bc-825e-d2ce145fcb55
2024-01-15 11:35:00 [DEBUG] Assigned job fe0d6b0a-285d-46bc-825e-d2ce145fcb55 to jobs.actors.farmerbot.powermanager:
2024-01-15 11:35:00 [INFO ] [POWERMANAGER] Executing job: POWEROFF 5643
2024-01-15 11:35:00 [DEBUG] jobs.ActionJob{
guid: 'fe0d6b0a-285d-46bc-825e-d2ce145fcb55'
twinid: 0
action: 'farmerbot.powermanager.poweroff'
args: params.Params{
params: [params.Param{
key: 'nodeid'
value: '5643'
}]
args: []
}
result: params.Params{
params: []
args: []
}
state: tostart
start: 2024-01-15 11:35:00
end: 1970-01-01 00:00:00
grace_period: 0
error: ''
timeout: 0
src_twinid: 0
src_action: ''
dependencies: []
}
2024-01-15 11:35:06 [DEBUG] Received result for job with guid fe0d6b0a-285d-46bc-825e-d2ce145fcb55
2024-01-15 11:35:06 [DEBUG] Returned job fe0d6b0a-285d-46bc-825e-d2ce145fcb55
2024-01-15 11:35:06 [INFO ] Elapsed time for update: 2.4280008
2024-01-15 11:39:46 [INFO ] [DATAMANAGER] Node 719 is ON.

Just received a similar report from a farmer running Farmerbot on Farm 45.
See errors:

At this stage; he has resorted to manually booting the nodes, and some nodes appear to be working fine after the reboot.

All this already changed in the new farmerbot


[New UI] Update the new UI of dev document

Updated website with new UI screenshots

@zhongjiajie PTAL

Thanks for your contribution, I will take a look tomorrow.


Disable input in alert

Ionic version:  (check one with "x")
(For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[x] 3.x
[ ] 4.x
I'm submitting a ...  (check one with "x")
[ ] bug report
[x] feature request
Please do not submit support requests or "How to" questions here. Instead, please use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
Disabled property in alert template is only set on checkbox and radio input.
Line 32 and 43 in alert-component.ts
Expected behavior:
Disabled property in alert template should also affect other inputs.
Steps to reproduce:
This is the default behaviour.
Related code:
To fix the problem, add [disabled]="i.disabled" on line 55 in alert-component.ts
[disabled]="i.disabled"

Other information:
Ionic info:

Hello! Thank you for the feature request. I'm going to move this issue over to our internal list of feature requests for evaluation. We are continually prioritizing all requests that we receive with outstanding issues. We are extremely grateful for your feedback, but it may not always be our next priority. I'll copy the issue back to this repository when we have begun implementation. Thanks!

This issue was moved to ionic-team/ionic-feature-requests#323


Flink 20114

This PR is co-authored with @becketqin.
What is the purpose of the change
This PR fixed a few bugs related to KafkaSource. See "Brief change log" for the list of bug fixes made in this PR.
Brief change log
Bug fixes:

KafkaSourceReader should not commit offsets for partitions whose offsets have not been initialized.
SourceCoordinatorContext should not log and fail job again if it receives InterruptedException after it is closed.
SourceOperatorStreamTask should be closed synchronously to avoid ClassNotFoundException.
PartitionOffsetsRetrieverImpl.committedOffsets() should handle the case without committed offsets.
SourceOperatorStreamTask should check the committed offset first before using OffsetResetStrategy.
Auto offset commit should be disabled by default.
SourceCoordinatorContext should fail job if it fails to send event to subtasks.

Usability improvements:

Reduce the offset commit logging verbosity from INFO to DEBUG.
SourceOperatorStreamTask should report numRecordsOutCount.
KafkaSourceEnumerator should close the admin client early if periodic partition discovery is disabled.
Remove the unused close.timeout.ms config.

Tests:

Added IT cases for KafkaSource by migrating IT cases from FlinkKafkaConsumer.

Verifying this change
The following bug-fix related commits are verified with new tests added in the same commit:

Every commit which fixes a bug comes with a new unit test to verify the bug fix
KafkaSourceReader should not commit offsets for partitions whose offsets have not been initialized
SourceCoordinatorContext should not log and fail job again if it receives InterruptedException after it is closed.
PartitionOffsetsRetrieverImpl.committedOffsets() should handle the case without committed offsets
SourceOperatorStreamTask should check the committed offset first before using OffsetResetStrategy
Auto offset commit should be disabled by default

The "Auto offset commit should be disabled by default" commit is trivial and no test needs to be added.
The following two bug-fix related commits are not additionally tested since I don't know how to test them with the existing Flink test framework. Will try to add tests for them if anyone has any suggestion.

SourceOperatorStreamTask should be closed synchronously to avoid ClassNotFoundException.
The "SourceCoordinatorContext should fail job if it fails to send event to subtasks"

In addition, this PR added tests in KafkaSourceITCase to provide better coverage for KafkaSource.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

Most code of this PR comes from https://github.com/apache/flink/pull/14239 by @becketqin. I have taken effort to rebase it onto HEAD, verify the related fixes, and made a few more improvements (e.g bug fixes) related to KafkaSource.

@StephanEwen @becketqin Could you help review this PR when you get time?

@flinkbot approve description

@flinkbot run azure

Thanks for looking into these issues. I'll try to take a look asap so we can get these improvements into 1.13.

@StephanEwen Thank you for the detailed review! The PR's code has been updated according to the discussion.

@StephanEwen @becketqin Thanks for the review! I think all issues are resolved. Could you take another look?

Merged to master.
8d2fa1bb81eff790bdc21a69d15a17aa074010ae


Backport: Implement dumping of lwAFTR conf file and binding table

This is a backport of #297 to lwaftr_starfruit. The feature was missing and didn't work correctly.

I run it in lwaftr_starfruit and the binding table is dumped correctly as well as lwAFTR's configuration file.

I run the tests manually. Everything OK.

lgtm then :)


Ft locate update

What does this PR do?
This PR refactors code for the locate microservice.
What JIRA task is related to this PR?
N/A
How do I test out this PR?
Git clone this repo cd AirQo-api/src/locate. Run py -m venv env to create a python virtual environment. Run env\scripts\activate to activate the environment and then run pip install -r requirements.txt to install necessary packages. Afterwards, run flask run to test out the end points using any REST client tool available to you.
Which end points should are ready for testing?
Base url: http:localhost:4001/api/v1
Partial urls:

/map/parishes
/map/savelocatemap
map/getlocatemap/<user_id>
map/updatelocatemap/<SPACE_NAME>
map/deletelocatemap/<SPACE_NAME>
More in the api documentation

Getting some error here. I think we might need to update the requirements.txt file


YARN-11469. [BackPort] Refactor FederationStateStoreFacade Cache Code. (#5570)

Description of PR
We expect to upgrade ehcache from 3.3.1 to 3.8.2 in branch-3.3, but before upgrading this jar package version, we need to backport 2 pr.

YARN-11469. Refactor FederationStateStoreFacade Cache Code. (#5570)
YARN-11470. FederationStateStoreFacade Cache Support Guava Cache. (#5609)

How was this patch tested?
Add Junit Test.
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
6m 46s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ branch-3.3 Compile Tests _

+1 :green_heart:
mvninstall
46m 23s

branch-3.3 passed

+1 :green_heart:
compile
0m 39s

branch-3.3 passed

+1 :green_heart:
checkstyle
0m 31s

branch-3.3 passed

+1 :green_heart:
mvnsite
0m 44s

branch-3.3 passed

+1 :green_heart:
javadoc
0m 39s

branch-3.3 passed

+1 :green_heart:
spotbugs
1m 26s

branch-3.3 passed

+1 :green_heart:
shadedclient
38m 12s

branch has no errors when building and testing our client artifacts.

-0 :warning:
patch
38m 33s

Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 35s

the patch passed

+1 :green_heart:
compile
0m 31s

the patch passed

+1 :green_heart:
javac
0m 31s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 17s

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common: The patch generated 0 new + 0 unchanged - 11 fixed = 0 total (was 11)

+1 :green_heart:
mvnsite
0m 33s

the patch passed

+1 :green_heart:
javadoc
0m 26s

hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common generated 0 new + 44 unchanged - 1 fixed = 44 total (was 45)

+1 :green_heart:
spotbugs
1m 21s

the patch passed

+1 :green_heart:
shadedclient
36m  9s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
2m 55s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common.txt
hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
asflicense
0m 35s

The patch does not generate ASF License warnings.

142m 21s

Reason
Tests

Failed junit tests
hadoop.yarn.server.federation.policies.amrmproxy.TestLocalityMulticastAMRMProxyPolicy

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6796/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6796

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 7c05cf879860 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / edccf15f717b75b7de005aad3f663216b6ace96d

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6796/1/testReport/

Max. process+thread count
557 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6796/1/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 29s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ branch-3.3 Compile Tests _

+1 :green_heart:
mvninstall
47m 49s

branch-3.3 passed

+1 :green_heart:
compile
0m 37s

branch-3.3 passed

+1 :green_heart:
checkstyle
0m 29s

branch-3.3 passed

+1 :green_heart:
mvnsite
0m 42s

branch-3.3 passed

+1 :green_heart:
javadoc
0m 38s

branch-3.3 passed

+1 :green_heart:
spotbugs
1m 22s

branch-3.3 passed

+1 :green_heart:
shadedclient
36m 32s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 35s

the patch passed

+1 :green_heart:
compile
0m 31s

the patch passed

+1 :green_heart:
javac
0m 31s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 18s

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common: The patch generated 0 new + 0 unchanged - 11 fixed = 0 total (was 11)

+1 :green_heart:
mvnsite
0m 34s

the patch passed

+1 :green_heart:
javadoc
0m 25s

hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common generated 0 new + 44 unchanged - 1 fixed = 44 total (was 45)

+1 :green_heart:
spotbugs
1m 21s

the patch passed

+1 :green_heart:
shadedclient
35m 20s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
2m 57s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common.txt
hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
asflicense
0m 38s

The patch does not generate ASF License warnings.

134m 58s

Reason
Tests

Failed junit tests
hadoop.yarn.server.federation.policies.amrmproxy.TestLocalityMulticastAMRMProxyPolicy

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6796/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6796

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 77569b6f3797 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / f41739716669971d640ab5f294b3a14ed84cc8a8

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6796/2/testReport/

Max. process+thread count
747 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6796/2/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
6m 17s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 2 new or modified test files.

_ branch-3.3 Compile Tests _

+1 :green_heart:
mvninstall
46m 52s

branch-3.3 passed

+1 :green_heart:
compile
0m 39s

branch-3.3 passed

+1 :green_heart:
checkstyle
0m 31s

branch-3.3 passed

+1 :green_heart:
mvnsite
0m 45s

branch-3.3 passed

+1 :green_heart:
javadoc
0m 40s

branch-3.3 passed

+1 :green_heart:
spotbugs
1m 26s

branch-3.3 passed

+1 :green_heart:
shadedclient
35m 38s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 36s

the patch passed

+1 :green_heart:
compile
0m 31s

the patch passed

+1 :green_heart:
javac
0m 31s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 18s

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common: The patch generated 0 new + 0 unchanged - 11 fixed = 0 total (was 11)

+1 :green_heart:
mvnsite
0m 34s

the patch passed

+1 :green_heart:
javadoc
0m 27s

hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common generated 0 new + 44 unchanged - 1 fixed = 44 total (was 45)

+1 :green_heart:
spotbugs
1m 22s

the patch passed

+1 :green_heart:
shadedclient
34m 59s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
3m  6s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common.txt
hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
asflicense
0m 37s

The patch does not generate ASF License warnings.

139m  0s

Reason
Tests

Failed junit tests
hadoop.yarn.server.federation.policies.amrmproxy.TestLocalityMulticastAMRMProxyPolicy

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6796/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6796

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 30922528e317 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 /<PHONE_NUMBER>c0553896852554e207af22f5c2d646

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6796/3/testReport/

Max. process+thread count
552 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6796/3/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
6m 25s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 2 new or modified test files.

_ branch-3.3 Compile Tests _

+1 :green_heart:
mvninstall
53m 43s

branch-3.3 passed

+1 :green_heart:
compile
0m 39s

branch-3.3 passed

+1 :green_heart:
checkstyle
0m 29s

branch-3.3 passed

+1 :green_heart:
mvnsite
0m 44s

branch-3.3 passed

+1 :green_heart:
javadoc
0m 40s

branch-3.3 passed

+1 :green_heart:
spotbugs
1m 25s

branch-3.3 passed

+1 :green_heart:
shadedclient
35m 24s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 35s

the patch passed

+1 :green_heart:
compile
0m 31s

the patch passed

+1 :green_heart:
javac
0m 31s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 18s

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common: The patch generated 0 new + 0 unchanged - 11 fixed = 0 total (was 11)

+1 :green_heart:
mvnsite
0m 34s

the patch passed

+1 :green_heart:
javadoc
0m 26s

hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common generated 0 new + 44 unchanged - 1 fixed = 44 total (was 45)

+1 :green_heart:
spotbugs
1m 22s

the patch passed

+1 :green_heart:
shadedclient
34m 49s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
3m 12s

hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
asflicense
0m 37s

The patch does not generate ASF License warnings.

145m 34s

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6796/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6796

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 945bbd036316 5.15.0-106-generic #116-Ubuntu SMP Wed Apr 17 09:17:56 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / e3cfb1a85a036ff50c99f13ac2927530f1eabc07

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6796/4/testReport/

Max. process+thread count
552 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6796/4/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

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

This message was automatically generated.

@steveloughran @goiri We are backporting YARN-11469 to branch-3.3 in order to upgrade ehcache from 3.3.1 to 3.8.2. However, there are significant differences between the code in branch-3.3 and branch-3.4. I had to redevelop YARN-11469 based on the code in branch-3.3, which has resulted in some variances between YARN-11469 in branch-3.3 and branch-3.4, but they are generally consistent.

I don't write/review yarn code, or hdfs. better for everyone. fewer regressions and I can stay out of support escalations. sorry

I don't write/review yarn code, or hdfs. better for everyone. fewer regressions and I can stay out of support escalations. sorry

Thank you for feedback! I understand and respect your principles.


SINGA -475 add Sign operator to singa

ready for merge

Thanks! Ready for merge

In my opinion:
For the function y=sign(x) , y = 1 when x > 0, y = -1 when x < 0. Therefore, the derivative is 0 except x = 0.
The function y=sign(x) is discontinuous at x=0 where the derivative is undefined in the mathematical logic. However, an defined derivative leads to a nan number, so we used a derivative of zero also at x=0.
As a result, dx is always 0 while the output shape (size of array) is the same as input shape.

This is what tensorflow use:
Status SignGrad(const Scope& scope, const Operation& op,
                const std::vector<Output>& grad_inputs,
                std::vector<Output>* grad_outputs) {
  auto shape = Shape(scope, op.input(0));
  auto zero = Cast(scope, Const(scope, 0.0), op.input(0).type());
  auto dx = Fill(scope, shape, zero);
  grad_outputs->push_back(dx);
  return scope.status();
}
REGISTER_GRADIENT_OP("Sign", SignGrad);

seems to fill the dx with all zero

there are conflicts and there are two solutions (same as what happened in log operator):

merge this branch with the latest master
checkout a new branch from the latest master. Then copy the added code into the autograd.py and test_operations.py; send a new PR.


pppos example missing (IDFGH-12531)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
The pppos_client example is no longer available. Its mentioned in esp modem and other places in documentation. The link is also mentioned in some older tickets, but the link is not longer working. Has it been moved to some other path/repo?
https://github.com/espressif/esp-idf/tree/master/examples/protocols/pppos_client
Example old ticket providing this url:
https://github.com/espressif/esp-lwip/issues/1

Found details of new link in esp modem component.
idf.py create-project-from-example "espressif/esp_modem^1.1.0:pppos_client"

@hazad Thanks to the ESP-IDF Component Manager, many components now no longer need to be maintained in ESP-IDF. esp-modem now maintained in https://github.com/espressif/esp-protocols/tree/master/components.


[ FIXES ISSUE #143 ] Remove unnecessary package-lock.json

Description

Fixes #143
[x] Remove unnecessary package-lock.json files

Hello @sil-samriddha!
Thank you for submitting this pull request Your pull request will be reviewed by maintainers shortly. Meanwhile make sure you have referenced the respected issue in this pr Your pr will not be merged if it does not refer respected pr and have read our Contributing Guidelines https://github.com/UBA-GCOEN/StichHub/blob/main/CONTRIBUTING.md And Code of Conduct https://github.com/UBA-GCOEN/StichHub/blob/main/CODE_OF_CONDUCT.md

Hello @sil-samriddha!
Thank you for submitting this pull request Your pull request will be reviewed by maintainers shortly. Meanwhile make sure you have referenced the respected issue in this pr Your pr will not be merged if it does not refer respected pr and have read our Contributing Guidelines https://github.com/UBA-GCOEN/StichHub/blob/main/CONTRIBUTING.md And Code of Conduct https://github.com/UBA-GCOEN/StichHub/blob/main/CODE_OF_CONDUCT.md


Transfer state on provider side remains STARTED although the transfer is completed

The status of a transfer keeps in state STARTED on the provider side, whereas the consumer shows it as COMPLETED and the transfer has been finished.

Tested version of MVD is commit 69124ce (head)


Create Yonatan119.json

Ofcourse!
I will add it right now
בתאריך יום ג׳, 9 בפבר׳ 2021 ב-12:29 מאת Michal Porag <
notifications@github.com>:

@MichalPorag requested changes on this pull request.
Hi Yonatan!
Thank you so much for open a PR and join the community, great job :)
We would be happy if you could also add your unprofessional profiles on
social networks. It will be easier to contact you, to us and to the group
members.
In people/Yonatan119.json
https://github.com/urish/pull-request-community/pull/34#discussion_r572764654
:

@@ -0,0 +1,6 @@

+{

"name": "יונתן בן עזרא",

"github": "yonatan119",

"linkedin": "https://www.linkedin.com/in/yonatan-benezra-554483174/",

"description": "אוהב לגרום לדמיון לעלות על המסך"

We would be happy if you could tell a little about yourself, things you
like to do, professional background including technological programming
languages, hobbies and most importantly things that excite you :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/urish/pull-request-community/pull/34#pullrequestreview-586391055,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQRQFZIRARFY6WEXELYH5HDS6EFBZANCNFSM4XKWXSIA
.


Send invoice - Chat shows skeleton briefly after the invoice is created

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

Version Number: 1.4.68-0
Reproducible in staging?: Yes
Reproducible in production?: No (New Feature)
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
Expensify/Expensify Issue URL:
Issue reported by: Applause Internal Team
Slack conversation:
Action Performed:

Go to staging.new.expensify.com
Go to FAB > Send invoice.
Enter amount and select participant.
Create the invoice.

Expected Result:
Workspace chat will not show skeleton after the invoice is created.
Actual Result:
Workspace chat shows skeleton briefly after the invoice is created.
Workaround:
Unknown
Platforms:

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

[ ] Android: Native
[X] Android: mWeb Chrome
[ ] iOS: Native
[X] iOS: mWeb Safari
[X] MacOS: Chrome / Safari
[X] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/38435837/9f36f112-4562-40c8-a451-ec3c761465b7

View all open jobs on GitHub

We think this bug might be related to #wave-collect - Release 1

@abekkala FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

Not a blocker, going to pass it to contributors.

#vip-billpay related. @danielrvidal could you please help prioritize?

Seems like good clean up, but I would not say CRITICAL to launching for earnings. Marking it as medium. But yea, this would be great to have someone look into and clean up.

Taking this one on me as a cleanup issue of my project. It should be fixed by my PR, which improves the Onyx updates sent after the SendInvoice command.

removed the external and help wanted labels and added Internal as @cristipaval is taking this one

@alitoshmatov could you please verify if this is still reproducible when you have a minute?

@alitoshmatov just bumping the comment from Cristi for you!

Not reproducible
https://github.com/Expensify/App/assets/59907218/a5e82b1d-6dba-4f64-9e56-3dbc35ea7e8e

Thanks a lot for retesting. I'll close it.


[FEATURE] Automate bumping versions after releases

Is your feature request related to a problem?
Coming from https://github.com/opensearch-project/opensearch-clients/issues/34. The version should be bumped each time a release is made so that builds happen for new changes with appropriate versioning.
What solution would you like?
Implement workflow similar to https://github.com/opensearch-project/OpenSearch/blob/main/.github/workflows/version.yml

Adopt workflow from OpenSearch or from elastic.net https://github.com/elastic/elasticsearch-net/blob/7.17/.github/workflows/make-bump.yml


touchRetentionOffset

What is the touchRetentionOffset property being set on TouchableOpacity ? I don't see that property in the React Native docs.

Perhaps it is EdgeInsetsPropType : https://github.com/facebook/react-native/commit/f331d2a8441fa024a43401953d8eae07f52c4919

It's a new prop -- code/documentation here https://github.com/facebook/react-native/commit/f331d2a8441fa024a43401953d8eae07f52c4919

I linked to that commit already. This issue should stay open as there are places that should be changed in ExNavigator: https://github.com/exponentjs/ex-navigator/blob/bf76fe8dd10ad5e0ca0ac1357f7016926ee77cb7/ExRouteRenderer.js#L109

Yeah. I'll update it when the next RN RC goes out.


Build hapi-fhir-structures-hl7org-dstu2 module

[Jenkins Automated Message - This is not a real comment from James] OK TO TEST?

FYI the HL7.org structures library isn't a part of the default HAPI build because we're still working on getting these structures integrated with the rest of the library. The goal is to have that work done in the next few weeks, but it won't be until after 0.9 is released which should be this week.
Will merge this as soon as we can though!

Then no need to keep this open. You will enable it when it's ready™.


Wrong lines when no source map

When in development, we don't generate sourcemaps and use babel-register to dynamically transpile the source code.
I noticed that if we load require('source-map-support').install(); in that context, the error stack shows wrong line numbers.
Is it by  design, implying that we should only install source-map-support when we know we're going to have sourcemap files available, or is it a bug in the module ?

I'm having the same problem. Any hits on how this can be solved?


Question 87

import MyComponent from './MyComponent'
It should be :
import MyComponent from './myComponent'

@enggsuraj Thank you. Can you create a PR?

sure


Carthage can’t build SwiftCheck-iOS scheme

It looks like the SwiftCheck-iOS scheme has the test target configured to build for the Analyze & Run actions. This causes build failures in carthage - “error: module 'SwiftCheck' was not compiled for testing”

Well that's annoying.  Can you flip the Enable Testability switch in the target in a pull request please?

This sould be the same as https://github.com/typelift/Swiftz/pull/289.

Opened PR #147

And we're live.
Thanks again!  :heart:


Cleanup EventSource externs

Mark withCredentials as @const to align with the spec [1]
Updated spec url
Corrected the return type of onopen, onmessage and onerror to be void
Collapsed '@type {X} @const' declarations to '@const {X}'

[1] https://html.spec.whatwg.org/multipage/server-sent-events.html#the-eventsource-interface

Created internal issue http://b/128987592

I'm not very familiar with EventHandlers, but it seems to me from https://html.spec.whatwg.org/multipage/webappapis.html#the-event-handler-processing-algorithm that there might be return values? Is there documentation elsewhere that says the return type of onopen, onmessage, and onerror is void?

I am away from my development machine atm so I can not confirm this but I am under the impression that it would effectively be a no-op to return a value as the event is not cancelable and there is no subsequent event handler and thus returnValue is also ignorable. It is mostly equivalent to invoking event.preventDefault() FWIU which is likewise a noop (again because there is no "default" action).
Note a similar change has been applied to WebSocket at https://github.com/google/closure-compiler/blob/master/externs/browser/html5.js#L3029-L3052
Cleaning this up has the advantage that downstream consumers of the externs such as google/elemental2 are forced to generate types with a return type if there is an any return type (which increases verbosity and code size) even though there is no real reason to allow this.

Ok, sounds good. Thanks for explaining. I've imported this for internal testing and review. It should be fine as long as no one else was depending on the previous behavior.

Thanks


Add API to get visible entries

Allow only fetching data that is shown at the moment.
Signed-off-by: Matthew Khouzam<EMAIL_ADDRESS>

Not yet ready, showing progress


Links which ends with ) doesn't work

Links which ends with closing round brackets will lead to an error.
e.g.:
https://en.wikipedia.org/wiki/Qt_(software)
will lead to:
Error: https://en.wikipedia.org/wiki/Qt_(software returned statuscode 404.

Felix, due to personal and professional circumstances I cannot deal with this problem in the forseable future, sorry.
You like to submit a PR for it?

Hey Gernot,
unfortunately, I don't have time for that at the moment either. But hopefully in a few days.

To me it looks like the problem has vanished. Could you please try to reproduce and give a little more context (which version of HSC) and perhaps even a test case, @FelixGeisler?


Fix half no_std compatibility

It seems that not all crates were fixed in https://github.com/samcrow/canadensis/commit/9004e2ef0ea701ab5a4c1e0216512f0ecb75cdac
Added default-features = false for the rest of half dependencies

Thanks for contributing. I released canadensis 0.3.1 and canadensis_macro 0.3.1 with the fixes.


Update version to 0.6.0.

@alexander-yevsyukov PTAL.

Current coverage is 80.42% (diff: 100%)

Merging #200 into master will increase coverage by 0.03%

@@             master       #200   diff @@
==========================================
  Files           147        147
  Lines          5406       5406
  Methods           0          0
  Messages          0          0
  Branches        595        595
==========================================
+ Hits           4346       4348     +2
+ Misses          950        949     -1
+ Partials        110        109     -1

Powered by Codecov. Last update 6db0e02...8e174fd


Region not to be formated

Is your feature request related to a problem? Please describe.
I'd like it is not to be formated in the PROC FORMAT or PROC SQL, or other special situations. For example, if I format the code below
proc format;
  value range
    40000-high='High'
    26000-< 40000='Medium'
    other ='Low';

  invalue evaluation
    'O'=4
    'S'=3
    'E'=2
    'C'=1
    'N'=0;
run;

It becomes
proc format;
  value range 40000-high='High' 26000-< 40000='Medium' other='Low';

  invalue evaluation 'O'=4 'S'=3 'E'=2 'C'=1 'N'=0;
run;

I'd like to keep the format of the first one.
For PROC SQL, it is similar. Usually I'll make a separate sql script file to format code and then paste it back, however, sas extension's format will make it flat again.
Describe the solution you'd like
I'd like to suggest add some thing like REGION. For example,
proc format;
  /* sas-format-disable */
  value range
    40000-high='High'
    26000-< 40000='Medium'
    other ='Low';

  invalue evaluation
    'O'=4
    'S'=3
    'E'=2
    'C'=1
    'N'=0;
  /* sas-format-enable */
run;

proc sql;
  * sas-format-disable;
  select
    momage,
    (weight * 0.01) as newweight
  from
    outdata
  where
    calculated newweight > 5;
  * sas-format-enable ;
run;

Environment
SAS version 9.4

This is an extended feature request of https://github.com/sassoftware/vscode-sas-extension/issues/989 .

I wonder if there are any protocol about formatting conventions in SAS, similar PEP8 in Python. @scnwwu

If that a protocol exist, we can write a standalone VSCode extension purely for formatting, just like the black, flake8 or autopep8 did.


Add option to enable worker graceful shutdown

In this PR I have automated the process of enabling the Worker Graceful Shutdown feature.
Enabling the option will:

Add a preStop lifecycle event to all worker Pods;
Set the shutdown.grace-period configuration property to gracePeriod;
Configure the workers' accessControl since the default system access control does not allow graceful shutdowns.

I also added a test to check if the graceful shutdown endpoint can be successfully called on the worker Pods.
Fixes #189

Hello @nineinchnick,
Thank you so much for finding the time to review this PR!
I will try to implement all the required changes, hopefully during this week and I will let you know then they are ready.

Thanks! No rush and we can always chat on the Trino slack if anything is not clear enough

Dear @nineinchnick,
I have addressed all your comments.
Regarding the test implementation, I considered using a long-running query; however, I was uncertain about its appropriateness as it seemed more like a Trino test than a Helm Chart test. Ultimately, my testing approach involves deleting a worker pod using kubectl and verifying that the logs of the affected pod contain the "Shutdown requested" string. This method effectively tests both the worker's authorization and the lifecycle configuration.
Looking forward for your feedback!

I rebased and addressed your last comment. Should be ready now!


Support targeting .NET 4.7.2

MSBuild needs to understand .NET 4.7.2 so developers can target it using new VS/MSBuild.

Thanks - I have been trying to do just this. And my knowledge of .NET is such that without finding this pull request via google I would have been completely stumped. Do you know when this will be introduced?

AFAIK this is done with #3286. We can reopen if there's more work discovered.


Short solution needed: "How to check Redis version" (redis)

Please help us write most modern and shortest code solution for this issue:
How to check Redis version (technology: redis)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

How to check Redis version


Update *.lfcla.com console landing pages

lfcla.com
The link at the bottom of the page to "request to add project." Should we link to new intake form https://docs.google.com/forms/d/e/1FAIpQLSdnTk_9xjk7YoiX_FcPEqsFytsLMcT8OzYUbK6TsYopR1XhdA/viewform ?
corporate.lfcla.com

The last line is struck through because it is out of order, the third box addresses this step.
project.lfcla.com

The HERE link could go to https://docs.google.com/forms/d/e/1FAIpQLSdnTk_9xjk7YoiX_FcPEqsFytsLMcT8OzYUbK6TsYopR1XhdA/viewform

The LFID should have been created during the application process or before by the user. So this whole bullet point could be rewritten to say "Log in to your Linux Foundation ID using the sign in link above. If you do not know your Linux Foundation ID, you can recover it by following the help links on that page."

@dealako the changes on dev look good!

This will be pushed to PROD on our next release.  Closing this issue as part of our product backlog meeting.


API key quota exceeded

Microsoft PowerToys version
0.82.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
Advanced Paste
Steps to reproduce
Open Advance paste, use AI when connecting add after it says API key quota exceeded.
Even tho I checked my quota and its okay. Also I have used only one API key. (using free chatgpt).
✔ Expected Behavior
Response from what I have requested.
❌ Actual Behavior
API key quota exceeded
Other Software
No response

Microsoft PowerToys version
0.82.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
Advanced Paste
Steps to reproduce
Open Advance paste, use AI when connecting add after it says API key quota exceeded. Even tho I checked my quota and its okay. Also I have used only one API key. (using free chatgpt).
✔ Expected Behavior
Response from what I have requested.
❌ Actual Behavior
API key quota exceeded
Other Software
No response

same issue here, used both legacy api keys and the api project keys but both seem to throw this error

Make sure you have credits in your Openai account, without credits it will throw this error.

@paaavann do you also have credits in the account? /needinfo


 This truly shows why abortion should be mandatory for some people.

Had used recaf to remove the auth in some jars like updated beta jars etc not just src. That's why src isn't fully updated

bro did not do anything lmao

bro got given all the source

I'm literally cumming in laughter seeing this so far into the future.


Docker sends SIGTERM to systemd-journald (and causes a soft-reboot)?

Something is happening when I try to stop containers on a 16.04 VM. I lose my ssh session, my tmux session and the machine "soft reboots".
docker version:
Client:
 Version:      1.10.3
 API version:  1.22
 Go version:   go1.6.1
 Git commit:   20f81dd
 Built:        Wed, 20 Apr 2016 14:19:16 -0700
 OS/Arch:      linux/amd64

Server:
 Version:      1.10.3
 API version:  1.22
 Go version:   go1.6.1
 Git commit:   20f81dd
 Built:        Wed, 20 Apr 2016 14:19:16 -0700
 OS/Arch:      linux/amd64

docker info:
Containers: 16
 Running: 0
 Paused: 0
 Stopped: 16
Images: 15
Server Version: 1.10.3
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 68
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: host bridge null
Kernel Version: 4.4.0-22-generic
Operating System: Ubuntu 16.04 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 3.359 GiB
Name: master
ID: KSVP:ECEP:LOQS:3YWO:WBWU:PSK4:5TGO:FSSS:2WYA:6RZM:OVJV:CCS6
WARNING: No swap limit support

This is on an Ubuntu 16.04 VM in Azure.
Steps to reproduce the issue:

Use kubelet with cbr0 mode
Start some containers
Kill those containers

Describe the results you received:
Docker seems to fail to stop the containers. Next in the logs is something indicating that docker sent SIGTERM to systemd-journald:
May 29 22:13:57 master systemd-journald[64414]: Journal stopped
May 29 22:13:57 master systemd-journald[2398]: Runtime journal (/run/log/journal/) is 34.4M, max 34.3M, 0B free.
May 29 22:13:57 master systemd-journald[64414]: Received SIGTERM from PID 943 (docker).

Additional information you deem important (e.g. issue happens only occasionally):

This is sudo journalctl -f | tee journal.log right before I deleted the containers. The output stops whenever things go south... so you can correlate with
The full log journal

The relevant section:
May 29 22:13:56 master kernel: eth0: renamed from vethd82d06e
May 29 22:13:56 master kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1386aab: link becomes ready
May 29 22:13:56 master kernel: cbr0: port 4(veth1386aab) entered forwarding state
May 29 22:13:56 master kernel: cbr0: port 4(veth1386aab) entered forwarding state
May 29 22:13:56 master docker[943]: time="2016-05-29T22:13:56.448536888Z" level=warning msg="Error getting v2 registry: Get https://registry-1.docker.io/v2/: dial tcp <IP_ADDRESS>:443: connect: network is unreachable"
May 29 22:13:56 master kernel: device veth842eb8f entered promiscuous mode
May 29 22:13:56 master kernel: IPv6: ADDRCONF(NETDEV_UP): veth842eb8f: link is not ready
May 29 22:13:56 master kernel: cbr0: port 8(veth842eb8f) entered forwarding state
May 29 22:13:56 master kernel: cbr0: port 8(veth842eb8f) entered forwarding state
May 29 22:13:56 master systemd-udevd[2199]: Could not generate persistent MAC address for veth842eb8f: No such file or directory
May 29 22:13:56 master systemd-udevd[2262]: Could not generate persistent MAC address for veth57870ea: No such file or directory
May 29 22:13:56 master kernel: device veth1335787 entered promiscuous mode
May 29 22:13:56 master systemd-udevd[2264]: Could not generate persistent MAC address for veth1335787: No such file or directory
May 29 22:13:56 master kernel: IPv6: ADDRCONF(NETDEV_UP): veth1335787: link is not ready
May 29 22:13:56 master kernel: cbr0: port 11(veth1335787) entered forwarding state
May 29 22:13:56 master kernel: cbr0: port 11(veth1335787) entered forwarding state
May 29 22:13:57 master kernel: cbr0: port 8(veth842eb8f) entered disabled state
May 29 22:13:57 master kernel: cbr0: port 11(veth1335787) entered disabled state
May 29 22:13:57 master kernel: eth0: renamed from vetheb5efdc
May 29 22:13:57 master kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth842eb8f: link becomes ready
May 29 22:13:57 master kernel: cbr0: port 8(veth842eb8f) entered forwarding state
May 29 22:13:57 master kernel: cbr0: port 8(veth842eb8f) entered forwarding state
May 29 22:13:57 master kernel: eth0: renamed from veth57870ea
May 29 22:13:57 master kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1335787: link becomes ready
May 29 22:13:57 master kernel: cbr0: port 11(veth1335787) entered forwarding state
May 29 22:13:57 master kernel: cbr0: port 11(veth1335787) entered forwarding state
May 29 22:13:57 master docker[943]: time="2016-05-29T22:13:57.650521456Z" level=info msg="Container 2d77443ef5362361e8102211b85e4663d6f91b5fd49d786dabd7bbabe3f96740 failed to exit within 2 seconds of SIGTERM - using the force"
May 29 22:13:57 master docker[943]: time="2016-05-29T22:13:57.651441861Z" level=info msg="Container f41bca579433fd4ba9d63690ba7fb10b468081f541efb569dfabd72daa70e261 failed to exit within 2 seconds of SIGTERM - using the force"
May 29 22:13:57 master docker[943]: time="2016-05-29T22:13:57.713825681Z" level=info msg="Container 0062afb8c56d78758e068985e59f7f69b1bc9b880573d20e9f51083ccab9487a failed to exit within 2 seconds of SIGTERM - using the force"
May 29 22:13:57 master docker[943]: time="2016-05-29T22:13:57.718193803Z" level=info msg="Container a120c3e472f8145db61c0f1f9d21301822781a2dcd914e02d2080335e8935c20 failed to exit within 2 seconds of SIGTERM - using the force"
May 29 22:13:57 master systemd-journald[64414]: Journal stopped
May 29 22:13:57 master systemd-journald[2398]: Runtime journal (/run/log/journal/) is 34.4M, max 34.3M, 0B free.
May 29 22:13:57 master systemd-journald[64414]: Received SIGTERM from PID 943 (docker).
May 29 22:13:57 master systemd[1]: Started Login Service.
May 29 22:13:57 master systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
May 29 22:13:57 master systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart.
May 29 22:13:57 master systemd[1]<EMAIL_ADDRESS>Service has no hold-off time, scheduling restart.
May 29 22:13:57 master systemd[1]: systemd-udevd.service: Service has no hold-off time, scheduling restart.
May 29 22:13:57 master systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart.
May 29 22:13:57 master kernel: cbr0: port 10(veth625bdc9) entered disabled state
May 29 22:13:57 master kernel: cbr0: port 9(vethda8ad51) entered disabled state
May 29 22:13:57 master kernel: device vethda8ad51 left promiscuous mode
May 29 22:13:57 master kernel: cbr0: port 9(vethda8ad51) entered disabled state
May 29 22:13:57 master kernel: cbr0: port 11(veth1335787) entered disabled state
May 29 22:13:57 master kernel: cbr0: port 8(veth842eb8f) entered disabled state
May 29 22:13:57 master kernel: cbr0: port 4(veth1386aab) entered disabled state
May 29 22:13:57 master kernel: cbr0: port 7(vethc9a4089) entered disabled state
May 29 22:13:57 master kernel: device veth1335787 left promiscuous mode
May 29 22:13:57 master kernel: cbr0: port 11(veth1335787) entered disabled state
May 29 22:13:57 master kernel: device veth842eb8f left promiscuous mode
May 29 22:13:57 master kernel: cbr0: port 8(veth842eb8f) entered disabled state
May 29 22:13:57 master kernel: device veth1386aab left promiscuous mode
May 29 22:13:57 master kernel: cbr0: port 4(veth1386aab) entered disabled state
May 29 22:13:57 master kernel: device vethc9a4089 left promiscuous mode
May 29 22:13:57 master kernel: cbr0: port 7(vethc9a4089) entered disabled state
May 29 22:13:57 master systemd[1]: unscd.service: Service hold-off time over, scheduling restart.
May 29 22:13:57 master systemd[1]: walinuxagent.service: Service hold-off time over, scheduling restart.
May 29 22:13:57 master systemd[1]: Stopped Azure Linux Agent.
May 29 22:13:57 master systemd[1]: Started Azure Linux Agent.
May 29 22:13:57 master systemd[1]: Stopped Name Service Cache Daemon.
May 29 22:13:57 master systemd[1]: Started Name Service Cache Daemon.
May 29 22:13:57 master systemd[1]: Stopped Flush Journal to Persistent Storage.
May 29 22:13:57 master systemd[1]: Stopping Flush Journal to Persistent Storage...
May 29 22:13:57 master systemd[1]: Stopped Journal Service.
May 29 22:13:57 master systemd[1]: Starting Journal Service...
May 29 22:13:57 master systemd[1]: Stopped udev Kernel Device Manager.
May 29 22:13:57 master systemd[1]: Starting udev Kernel Device Manager...
May 29 22:13:57 master systemd[1]: Stopped Getty on tty1.
May 29 22:13:57 master systemd[1]: Started Getty on tty1.
May 29 22:13:57 master systemd[1]: Stopped Login Service.
May 29 22:13:57 master systemd[1]: Starting Login Service...
May 29 22:13:57 master systemd[1]: Stopped Network Time Synchronization.
May 29 22:13:57 master systemd[1]: Starting Network Time Synchronization...
May 29 22:13:57 master systemd[1]: Starting OpenBSD Secure Shell server...
May 29 22:13:57 master systemd[1]<EMAIL_ADDRESS>Service hold-off time over, scheduling restart.
May 29 22:13:57 master systemd-journald[2398]: Journal started

These things jumped out as being suspicious:

May 29 22:13:56 master kernel: eth0: renamed from vethd82d06e

May 29 22:13:56 master docker[943]: time="2016-05-29T22:13:56.448536888Z" level=warning msg="Error getting v2 registry: Get https://registry-1.docker.io/v2/: dial tcp <IP_ADDRESS>:443: connect: network is unreachable"

When I add the docker apt repo and update (and move options from /etc/default/docker to the systemd unit file), I can no longer reproduce this problem. I've been able to successfully delete my replicaset which causes a delete and recreate of 9 containers (3 x (api-service + api-nginx + pause)) .
Working version:
docker version
Client:
 Version:      1.11.1
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   5604cbe
 Built:        Tue Apr 26 23:43:49 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.1
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   5604cbe
 Built:        Tue Apr 26 23:43:49 2016
 OS/Arch:      linux/amd64

docker info
Containers: 9
 Running: 9
 Paused: 0
 Stopped: 0
Images: 15
Server Version: 1.11.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 54
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: host bridge null
Kernel Version: 4.4.0-22-generic
Operating System: Ubuntu 16.04 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 3.359 GiB
Name: master
ID: KSVP:ECEP:LOQS:3YWO:WBWU:PSK4:5TGO:FSSS:2WYA:6RZM:OVJV:CCS6
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support

Note that /etc/default/docker is not used for systems running on systemd (see the comment at the top of that file: https://github.com/docker/docker/blob/master/contrib/init/sysvinit-debian/docker.default#L1-L8
For systemd, please don't make direct modifications to the docker.service file; use drop-in files instead (see https://docs.docker.com/engine/admin/systemd/#custom-docker-daemon-options).
Or, perhaps a better option, use a daemon.json configuration file; https://docs.docker.com/engine/reference/commandline/daemon/#daemon-configuration-file

Oh, I noticed you originally reported with docker 1.10.3 on Ubuntu 16.04
 Version:      1.10.3
 API version:  1.22
 Go version:   go1.6.1

It looks like that is not an official package (at least not one that's supported by us), because we never shipped Docker 1.10 for ubuntu 16.04. And have not released a version of Docker compiled with Go 1.6. Did you perhaps install a package that's maintained and supported by Ubuntu?

Yes, I was originally using the docker.io package from Ubuntu. (which uses /etc/default/docker as an EnvironmentFile against recommendations).
Thanks for the note on drop-ins, I was just hacking to check if it repro'd quickly.
Anyhow, I guess the hint is that I should file this on Ubuntu's bug tracker instead. Feel free to close this if that's the case and I'll follow up on the Ubuntu side of things.
Thanks for the fast reply!

Filed on Ubuntu: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1586856
Closing this out for now. Thanks again @thaJeztah.