Enhance Gas Fee Optimization in Transaction Processing

Objective: Improve gas fee efficiency in transaction processing to enhance user experience and reduce costs.
Details:

Current Status: Transactions on our blockchain incur varying gas fees based on network congestion.
Proposed Change: Develop and implement a gas fee optimization algorithm that dynamically adjusts transaction fees based on real-time network conditions.
Technical Requirements:

Research existing gas fee models and propose an optimized solution.
Implement the new gas fee algorithm in the transaction processing module.
Conduct thorough testing to validate performance and reliability under different network loads.

Expected Impact: Users will experience more predictable and cost-effective transactions, encouraging broader adoption of our blockchain platform.
Skills Required: Proficiency in blockchain development, understanding of gas fee dynamics, and experience with transaction optimization strategies.
Additional Information: Please refer to our project's contribution guidelines before proceeding. Feel free to discuss any implementation details or alternative approaches in the comments.
Acceptance Criteria:

The new gas fee algorithm should be integrated into the existing transaction processing system.
Performance tests should demonstrate improved efficiency without compromising transaction speed or security.

Related Issues: None

Thank you for creation an issue. The issue is very broad and doesn't have concrete suggestions or problem descriptions.
I'm closing this issue for now until future details.


move TestData.csv

I'm not sure what this file is for:
https://github.com/hytest-org/hytest/blob/main/essential_reading/DataSources/TestData.csv
I think it was maybe being used in a workflow somewhere, but can't remember where. I'm wondering if we can move this data to the OSN pod?

https://github.com/hytest-org/hytest/blob/main/dataset_preprocessing/ReChunkingData.ipynb

I don't have a strong opinion on where it is stored.
But if you move it, that rechunking notebook should be updated to reflect its location.

I see that notebook references TestData.zarr which is stored in that same folder - but I don't see TestData.csv in that notebook.

Ah yes... I absolutely missed that.
This csv is a vestige of model_evaluation\tutorials\nwm_streamflow\NWM_Benchmark_SampleData.csv
The TestData.csv can be deleted, as it has been replaced with NWM_Benchmark_SampleData.csv.
But this brings up another point... do you want TestData.zarr to be moved to other storage or remain in this repo.


Texture on ellipsoid entity does not work when using SampledPositionProperty as entity position

The texture on a ellipsoid entity is not rendered when the position of the entity is initialized using SampledPositionProperty (e.g. for animating the object over time).
Sandcastle example
As a side note, using CallbackProperty for setting the position causes the same misbehavior. It seem the texture is only applied when the entity position is initialized with a Cartesian3 object
Browser:
Chrome, Firefox
Operating System:
Windows 10

Thanks for the report @calogeromauceri. This looks like a duplicate with https://github.com/CesiumGS/cesium/issues/9674 (CZML data sources use entities under the hood). I'll close this to keep discussion in one place.


make empty array falsy as well (including upping version number)

fixes the array half of issue #16


Initial Project created from Atlas App Services Results in Disconnected Socket

What happened?
When I follow the instructions and setup the project and run it, I always get this error:
Error:

error handling "bind" message: error getting sync status from metadata store: error getting initial sync status: mongo: no documents in result

Logs:

[
  "Connection was active for: 1s"
]
Function Call Location:

SG

Remote IP Address:

<IP_ADDRESS>

SDK:

Dart v1.6.1

Framework:

Flutter v3.2.3 (stable) (Tue Dec 5 17:58:33 2023 +0000) on "ios_arm64"

Platform:

iOS vVersion 17.2.1 (Build 21C66)

On my Client Side Logs, it shows this on Flutter's Device:
Launching lib/main.dart on iPhone 15 Pro Max in debug mode...
Xcode build done.                                           10.7s
[ERROR:flutter/shell/platform/darwin/graphics/FlutterDarwinContextMetalImpeller.mm(42)] Using the Impeller rendering backend.
Connecting to VM Service at ws://<IP_ADDRESS>:64261/js8xCaiL568=/ws
flutter: To see your data in Atlas, follow this link:https://cloud.mongodb.com/links/65a4a4d0e591c818117a2c6b/explorer/AtlasCluster/database/collection/find
flutter: 2024-01-15T03:17:01.227284: [ERROR] Realm: App: log_in_with_credentials failed: 401 message: invalid username/password
flutter: To see your data in Atlas, follow this link: https://cloud.mongodb.com/links/65a4a4d0e591c818117a2c6b/explorer/AtlasCluster/database/collection/find
flutter: 2024-01-15T03:17:05.106130: [INFO] Realm: Realm sync client ([realm-core-13.24.0])
flutter: 2024-01-15T03:17:05.106291: [INFO] Realm: Platform: iOS Darwin 23.2.0 Darwin Kernel Version 23.2.0: Wed Nov 15 21:55:06 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6020 arm64
flutter: 2024-01-15T03:17:05.107431: [INFO] Realm: Connection[1]: Session[1]: Binding '/Users/ngoc/Library/Developer/CoreSimulator/Devices/F8FBCB59-4144-4D6E-80D8-23F6338B7FF5/data/Containers/Data/Application/368D5A44-0684-4FB9-9854-B9BACB2FDBB4/Documents/mongodb-realm/application-0-hkiwf/65a4a8839ab1876fdba3bdea/default.realm' to ''
flutter: 2024-01-15T03:17:05.107543: [INFO] Realm: Connection[1]: Session[1]: client_reset_config = false, Realm exists = true
flutter: 2024-01-15T03:17:05.107659: [INFO] Realm: Connection[1]: Connecting to 'wss://ws.ap-southeast-1.aws.realm.mongodb.com:443/api/client/v2.0/app/application-0-hkiwf/realm-sync'
flutter: 2024-01-15T03:17:05.214003: [INFO] Realm: Connected to endpoint '<IP_ADDRESS>:443' (from '<IP_ADDRESS>:64287')
flutter: 2024-01-15T03:17:05.604978: [INFO] Realm: Connection[1]: Connected to app services with request id: "65a5143136f40152d3b2713b"
flutter: 2024-01-15T03:17:05.758134: [INFO] Realm: Connection[1]: Closing the websocket with error code=WebSocket: OK, message='', was_clean=true
flutter: 2024-01-15T03:17:09.934501: [ERROR] Realm: Reading failed: End of input
flutter: 2024-01-15T03:17:09.935224: [INFO] Realm: Connection[1]: Closing the websocket with error code=WebSocket: Read Error, message='End of input', was_clean=false
flutter: 2024-01-15T03:17:09.935701: [INFO] Realm: Connection[1]: Connection closed due to transient error: ConnectionClosed: End of input
flutter: 2024-01-15T03:17:10.906101: [INFO] Realm: Connection[1]: Connecting to 'wss://ws.ap-southeast-1.aws.realm.mongodb.com:443/api/client/v2.0/app/application-0-hkiwf/realm-sync'

I really want to try and use Realm for my Project, but I can't seem to even get the sample project running. I'd love for some advice!
Repro steps
Just start the app-services project and the realm guide for flutter.
Version
1.6.1
What Atlas Services are you using?
Both Atlas Device Sync and Atlas App Services
What type of application is this?
Flutter Application
Client OS and version
iOS Version 17.2.1
Code snippets
No response
Stacktrace of the exception/crash you're getting
Launching lib/main.dart on iPhone 15 Pro Max in debug mode...
Xcode build done.                                           10.7s
[ERROR:flutter/shell/platform/darwin/graphics/FlutterDarwinContextMetalImpeller.mm(42)] Using the Impeller rendering backend.
Connecting to VM Service at ws://<IP_ADDRESS>:64261/js8xCaiL568=/ws
flutter: To see your data in Atlas, follow this link:https://cloud.mongodb.com/links/65a4a4d0e591c818117a2c6b/explorer/AtlasCluster/database/collection/find
flutter: 2024-01-15T03:17:01.227284: [ERROR] Realm: App: log_in_with_credentials failed: 401 message: invalid username/password
flutter: To see your data in Atlas, follow this link: https://cloud.mongodb.com/links/65a4a4d0e591c818117a2c6b/explorer/AtlasCluster/database/collection/find
flutter: 2024-01-15T03:17:05.106130: [INFO] Realm: Realm sync client ([realm-core-13.24.0])
flutter: 2024-01-15T03:17:05.106291: [INFO] Realm: Platform: iOS Darwin 23.2.0 Darwin Kernel Version 23.2.0: Wed Nov 15 21:55:06 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6020 arm64
flutter: 2024-01-15T03:17:05.107431: [INFO] Realm: Connection[1]: Session[1]: Binding '/Users/ngoc/Library/Developer/CoreSimulator/Devices/F8FBCB59-4144-4D6E-80D8-23F6338B7FF5/data/Containers/Data/Application/368D5A44-0684-4FB9-9854-B9BACB2FDBB4/Documents/mongodb-realm/application-0-hkiwf/65a4a8839ab1876fdba3bdea/default.realm' to ''
flutter: 2024-01-15T03:17:05.107543: [INFO] Realm: Connection[1]: Session[1]: client_reset_config = false, Realm exists = true
flutter: 2024-01-15T03:17:05.107659: [INFO] Realm: Connection[1]: Connecting to 'wss://ws.ap-southeast-1.aws.realm.mongodb.com:443/api/client/v2.0/app/application-0-hkiwf/realm-sync'
flutter: 2024-01-15T03:17:05.214003: [INFO] Realm: Connected to endpoint '<IP_ADDRESS>:443' (from '<IP_ADDRESS>:64287')
flutter: 2024-01-15T03:17:05.604978: [INFO] Realm: Connection[1]: Connected to app services with request id: "65a5143136f40152d3b2713b"
flutter: 2024-01-15T03:17:05.758134: [INFO] Realm: Connection[1]: Closing the websocket with error code=WebSocket: OK, message='', was_clean=true
flutter: 2024-01-15T03:17:09.934501: [ERROR] Realm: Reading failed: End of input
flutter: 2024-01-15T03:17:09.935224: [INFO] Realm: Connection[1]: Closing the websocket with error code=WebSocket: Read Error, message='End of input', was_clean=false
flutter: 2024-01-15T03:17:09.935701: [INFO] Realm: Connection[1]: Connection closed due to transient error: ConnectionClosed: End of input
flutter: 2024-01-15T03:17:10.906101: [INFO] Realm: Connection[1]: Connecting to 'wss://ws.ap-southeast-1.aws.realm.mongodb.com:443/api/client/v2.0/app/application-0-hkiwf/realm-sync'

Relevant log output
No response

@ngoctranfire Thank you for trying out Realm.
I see that it complains about the authentication:
flutter: 2024-01-15T03:17:01.227284: [ERROR] Realm: App: log_in_with_credentials failed: 401 message: invalid username/password

Does that ring a bell? Also, did you look into the error log?
https://cloud.mongodb.com/links/65a4a4d0e591c818117a2c6b/explorer/AtlasCluster/database/collection/find

@nielsenko The first time I actually tried it yes, it did result in incorrect credentials. Please ignore that. The second time, I got the correct credentials and got into the app, but the same thing still happened.

Hey, we got a response from the server team - looks like something went wrong initializing sync for your app. They'll investigate it, but in the meantime, you can try to terminate and reenable sync, which should resolve it.

@nirinchev I actually tried that too but it still never recovered. I still have the same issue.

Hi, can you terminate sync, then deploy, then enable sync and deploy. I suspect looking at your deployment history that you terminated sync, then enabled sync, then clicked deploy (which was a no-op).


Provide avx512f implementation of FMA and variant

Fix #884

cc @JohanMabille this one was clean & simple, I wonder how we could have missed that :-/

Thank you so much!!! 🎉 🎉

cc @JohanMabille this one was clean & simple, I wonder how we could have missed that :-/

Indeed :s


Composer

Thanks. I can't seem to run composer on this repo with the guide you have given.
composer update janasva / google-trends
I updated composer.json file as adviced.

{
    "require": {
        "jonasva/google-trends": "dev-master"
    }
}

I'm hoping that you would add supoort for Google Topcharts country based :)

Hi @youngbobby,
What is the error you are getting?
Make sure that you first update your composer.json file, and then execute the composer update command. Also, there is a typo in the composer update statement you posted. It has to be:
composer update jonasva/google-trends

Give it a try and let me know how it goes.

Hi @jonasva
This is the error I am getting:
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - The requested package jonasva/google-trends No version set (parsed as 1.0.0) could not be found.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see  for more details.

Read  for further common problems.

Here's my composer.json file:
{
    "name": "jonasva/google-trends",
    "description": "Unofficial Google Trends PHP API",
    "homepage": "http://github.com/jonasva/google-trends",
    "keywords": ["google", "trends", "api"],
    "license": "MIT",
    "authors": [
        {
            "name": "Jonas Van Assche",
            "email"<EMAIL_ADDRESS>        }
    ],
    "require": {
        "php": ">=5.4.0",
        "guzzlehttp/guzzle": "5.0.*@dev",
        "jonasva/google-trends": "dev-master"
    },
    "autoload": {
        "psr-0": {
            "Jonasva\\GoogleTrends": "src/"
        }
    }
}

hmm, that might related to the minimum-stability setting in your own composer.json. Try adding these 2 lines at the bottom of your project's composer.json:
"prefer-stable": true,
"minimum-stability": "dev"

i even have same issue, can you please guide me what to do.
my composer.json file:
{
"name": "jonasva/google-trends",
"description": "Unofficial Google Trends PHP API",
"homepage": "http://github.com/jonasva/google-trends",
"keywords": ["google", "trends", "api"],
"license": "MIT",
"authors": [
    {
        "name": "Jonas Van Assche",
        "email"<EMAIL_ADDRESS>    }
],
"require": {
    "php": ">=5.4.0",
    "guzzlehttp/guzzle": "5.0.*@dev",
    "jonasva/google-trends": "dev-master"
},
"autoload": {
    "psr-0": {
        "Jonasva\\GoogleTrends": "src/"
    }
},
"prefer-stable": true,
"minimum-stability": "dev"

}
and error i am receiving following error:
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- The requested package jonasva/google-trends No version set (parsed as 1.0.0) could not be found.
Potential causes:

A typo in the package name
The package is not available in a stable-enough version according to your minimum-stability setting
see https://groups.google.com/d/topic/composer-dev/_g3ASeIFlrc/discussion for more details.

Read https://getcomposer.org/doc/articles/troubleshooting.md for further common problems.

Hi @salmanyaqoob,
Actually in your project's composer.json file, you should just include jonasva/google-trends.
Give it a try with a composer.json file like this in your project, and let me know if it works:
{
	"require": {
		"jonasva/google-trends": "dev-master"
	},
  	"prefer-stable": true,
  	"minimum-stability": "dev"
}


Allow multiple types in wsprov_fetch_linked_objects

I lost the ability to filter by multiple types at some point. I didn't mean to lose this.

I'm okay to leave the versions as-is, i'll deal with it in the frontend


add private ip address for openstack driver

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "master" git@github.com:xinxian0458/machine.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.


Toggle not work inside a repeatable field

setting a toggle type field inside a repeatable always save it as true but not show the toggle as selected

Thanks @gcasaroseisnet - didn't know that. I've just added a sister-issue in https://github.com/Laravel-Backpack/CRUD/issues/3924 so that we take care of it right away, in Backpack 4.1.
Cheers!

Hey guys!
Thanks for raising the issue @gcasaroseisnet !
Unfortunatelly there is not much we can do to make the field work inside repeatable in version 4.1. But I have good news, 4.2 is really close to be lunched and this is fixed by: https://github.com/Laravel-Backpack/CRUD/pull/3905
I've just tested and everything works as expected using that branch.
I am going to close this since we already have the fix for it!
Thanks again,
Pedro

Thanks for the info @pxpm . Until then @gcasaroseisnet please use the checkbox field - that definitely works inside repeatable.


Add tests

Mostly opening this as an FYI
Will be much easier very soon – https://github.com/dart-lang/test/pull/663 😄

Nice, thanks! And yes, tests are in progress. I wanted to see if I can write an integration test against Firebase itself (for more confidence) and realized I'll need firebase_admin_interop for https://github.com/firebase/firebase-admin-node to verify database triggers. So building a PoC for it now.

I've started testing your package. Work very well for me so far. The good news about firebase_admin package. Can you say approximately when we will be able to test it?

@kevmoo Thanks again for the hint! I upgraded node_interop to use --platform node and it works great! There are a couple things I'm struggling with though, like expecting for console.log() to print something...
@marcinsydor Thanks for the feedback! I've just published a very-very barebones version here: https://pub.dartlang.org/packages/firebase_admin_interop
Also using updated test package to run integration tests. Looking forward for your feedback!
Next in line for tests is this package.

Great, seems to work fine for me. I'm trying now to return some values from the database but DataSnapshot doesn't have forEach function yet. If you not going to add it soon I guess I could add it myself?

I'm slowly getting back to work on this and other Dart related projects.
I've added a few tests since then and there is basic infrastructure for integration testing, however I'm not exactly sure how to solve an issue with Travis removing env vars for PR builds which breaks integration tests. Will do some research on that.
The new --platform=node makes things a lot easier though, very happy with it!

Great to hear!

Closing this one as there are some tests now. Can still do better on testing side, but let's track updates/improvements in separate issues.


Added support for output as an array of objects for newer versions of datatables.js

Regarding suggestion on issue: https://github.com/mcintyre321/mvc.jquery.datatables/issues/117
I removed the embedded resources from the project file because it wasn't compiling. It's referenced but not under version control.

I think you need to do a recursive submodule update to get the embedded resource files into your source folder. Could you do that and re-add the embedded resources please?

Sorry. Properly fixed. ;)


Spaces page

Is your feature request related to a problem? Please describe.
Make a spaces page showing images of various office spaces and in a very smooth and clean manner.
Describe the solution you'd like
Remember to have a very good UI
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

i would like to complete this task
@Mayank77maruti  assign me this task  hacktoberfest2024

@Swadeeppatil Welcome to 603WorkVed , don't forget to star the repo.
Happy contributing.

Hey @Swadeeppatil i am unassigning you from this task because of no response i think you are busy with some other work ,its perfectly fine.
Thank you for time.
Donot forget to star the repo.

@Mayank77maruti i did one task, im free you can assign me if it needs work on
already completed the blogs section

is this issue still open ?

Can this issue be assigned to me if no one is currently working on it ?

I have already assigned you.

This issue is currently open and no one is assigned. Anyone can attempt this.


Support dynamic language change

🚀 Feature Request
✍ Description
type YaConfigLang =  'ru_RU' | 'en_US' | 'en_RU' | 'ru_UA' | 'uk_UA' | 'tr_TR';

interface YaConfig {
  lang?: YaConfigLang | Observable<YaConfigLang>;
}

well, it's pretty complicated to implement. and if no one needs this, I'll close it for now.
notes:

We need a namespace for each language, e.g. ymaps_en, ymaps_ru etc. So I guess we need to create an injection token with this string instead of a hardcoded window.ymaps. It requires a lot of changes
YaApiLoaderService should work with different languages. I mean a script variable is not enough. We need a map (Map<string, HTMLElementScript)
We need to destroy a map. Somehow components should know about config changes.


Cache output for  profile collection API shows redundant data (profile-collection twice) - ouput differs from live

Cache output for  profile collection API shows redundant data  - ouput differs from live
http://xx:xxx/core-model-1-4:network-control-domain=cache/control-construct=513559991B/profile-collection
Cache o/p:

http://xx:xxx/core-model-1-4:network-control-domain=cache/control-construct=513559991B/profile-collection
[live_profile_collection.txt](https://github.com/openBackhaul/MicroWaveDeviceInventory/files/14616933/live_profile_collection.txt)
[cache_profile_collection.txt](https://github.com/openBackhaul/MicroWaveDeviceInventory/files/14616934/cache_profile_collection.txt)

  "core-model-1-4:profile-collection": {
    "profile": [
      {
        "uuid": "WRED-433.2.5",
        "lifecycle-state": "core-model-1-4:LIFECYCLE_STATE_INSTALLED",
        "wred-profile-1-0:wred-profile-pac": {
          "wred-profile-configuration": {
            "gentle-wred-is-on": false,
            "threshold-low": -1,
            "sensitivity": 0,
            "threshold-high": -1,
            "threshold-gentle": -1,
            "external-label": "test TC 5",
            "drop-probability-at-threshold-high": 10,
            "drop-probability-at-threshold-low": -1,
            "coloring-is-on": false
          },

 "profile-collection": {
      "profile": [
        {
          "uuid": "WRED-433.2.5",

Tested with MWDI latest version test_v1.1.5.
Issue is no longer observed.  Profile collection is listed only once in cache  and its in sync with live.
898.txt
http://xx:xxx/core-model-1-4:network-control-domain=cache/control-construct=513559991B/profile-collection

902_test_v1.1.5.

Tested with MWDI latest version test_v1.1.5.
Issue is no longer observed. Profile collection is listed only once in cache and its in sync with live.
898.txt
http://xx:xxx/core-model-1-4:network-control-domain=cache/control-construct=513559991B/profile-collection


fix(chartutil): port over enhancements to helm create from Helm 2

Signed-off-by: Matthew Fisher<EMAIL_ADDRESS>

Thank you for catching all those, @hickeyma. All comments addressed!


Unable to upgrade without any running into one issue or the other!

[x] I have reviewed the documentation
[x] I have searched existing issues
[x] I am using the latest React Native version

Environment
Environment:
OS: Windows 10
Node: 9.2.0
Yarn: 1.3.2
npm: 5.8.0
Watchman: Not Found
Xcode: N/A
Android Studio: Version  <IP_ADDRESS> AI-171.4443003
Packages: (wanted => installed)
react: ^16.2.0 => 16.3.1
react-native: ^0.52.2 => 0.55.2
Steps to Reproduce
react-native-git-upgrade
Actual Behavior
Cant get the upgrade done smoothly!!
First Issue

Second Issue

as a temporary solution, I has to do the following manually:

Update various dependencies manually via npm update

Update the version of react and react-native in package.json as the node_module did updata, but the package.json didnt


fix typo.

Signed-off-by: He Simei<EMAIL_ADDRESS>

@dalanlan thanks for the contribution. A few fixes please and it should be good-to-go.  (I love your icon. That was a cute cartoon.)

Updated @moxiegirl
Glad that you love Baymax:)

@dalanlan Good job.

LGTM from me. Need one more from @docker/docs-owners

thanks @dalanlan! LGTM
(and a nice avatar/movie indeed!)


HQ Button Integrate

Show HQ button if low quality image was loaded, and load the real HQ image if tapped

Done


Bump boto3/botocore versions

Description
In support of #2188, this PR bumps the versions of boto3/botocore, so that we have access to the new Docker image functionality.
GitHub Issues
Related #2188
Testing
I created a new virtual env with the new dependencies and ran several Zappa workflows: deploy, update, status, and undeploy.

Any other tests you'd recommend running?

Coverage decreased (-68.9%) to 4.114% when pulling 4d92c6565d9a66224c0c3d891307a32d2c5184ce on ian-whitestone:bump-reqmts into 542c8c60291ebc5ece03b8dd4abe9e0172715086 on Miserlou:master.

Coverage decreased (-16.6%) to 56.371% when pulling 6655776 on ian-whitestone:bump-reqmts into 542c8c6 on Miserlou:master.

No idea why coverage dropped, it shouldn't given that i just bumped dependencies. Can we merge even though this is failing (assuming we're ok with everything else?)

Coverage decreased (-16.6%) to 56.371% when pulling 6655776 on ian-whitestone:bump-reqmts into 542c8c6 on Miserlou:master.

No idea why coverage dropped, it shouldn't given that i just bumped dependencies. Can we merge even though this is failing (assuming we're ok with everything else?)

nvm, looks like it is passing now...

@jneves would you be able to 👍  or 👎 when you get a chance?

@jneves would you be able to 👍  or 👎 when you get a chance?

@mcrowson any chance you'd be able to 👍 or 👎 ?

I like the change, but can you make it to the zappa/zappa project? I'm not sure how @jneves pulled in the issues or if outstanding MRs got merged too, but make the changes to the other project and tag me.


Create Milestone button no longer working

Just noticed when using the tool that the Create Milestone button not working in the new way that you're importing function in the milestone manager. I could be doing something wrong. Not sure. Worth a look.
the function is not defined:

Tagging
@jens-markussen

Will check now @Causb1A

Problem confirmed and fixed. Thank for reporting.

Cheers thanks @jens-markussen


Roll Flutter Engine from b7dddee939f2 to 9d957437fb1e (1 revision)

https://github.com/flutter/engine/compare/b7dddee939f2...9d957437fb1e
2024-03-27<EMAIL_ADDRESS>[Impeller] Transform geometry to safe depth ranges instead of forcing discrete depth values. (flutter/engine#51673)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jacksongardner@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Add skip console highlighting.

Regarding the long open issue about skipping tests, maybe this might be an approach to break up the changes in easily reviewable pieces.
This work contains highlighting on the console for skipped tests only.

@pekkaklarck do you think this change is a good idea? Or do you prefer the work in one big chunk?

Does this change have any effect?

I definitely don't want to add unused code to the master.

Okay, let me re-phrase. At the moment, this code is unused. In future, this will be used when the SKIP status is added.

I added some more changes that include adding the SKIP status.

I don't want to add code to master that's not used regardless would be used in the future or not. Especially not when it's unclear if/when it is actually used and how would it be used. Such code could be added to a feature branch, but absolutely not to master.

Okay, I understand.


clickhouse keeper: questions about --force-recovery

clickhouse-keeper version: v22.3 & v23.4.1
deploy yaml: https://github.com/Altinity/clickhouse-operator/blob/master/deploy/clickhouse-keeper/clickhouse-keeper-3-nodes.yaml
if [[ "1" == "$MY_ID" ]]; then
  clickhouse-keeper --config-file=/etc/clickhouse-keeper/keeper_config.xml --force-recovery
else
  clickhouse-keeper --config-file=/etc/clickhouse-keeper/keeper_config.xml
fi

What I'm curious about is why this first node starts with --force-recovery.  What does it means ? If I removed it and modified it to have only one line like  clickhouse-keeper --config-file=/etc/clickhouse-keeper/keeper_config.xml

I found that all three keeper nodes can be started, but when I had  a DDL sql (like create database db on cluster 'xxx') by clickhouse-client, it blocked until timeout. The following is what I found when I checked the znode.

So what's wrong with this, why it's blocked..

The third problem I met was that I don't modify anything just used the same yaml https://github.com/Altinity/clickhouse-operator/blob/master/deploy/clickhouse-keeper/clickhouse-keeper-3-nodes.yaml.  When the fisrt keeper node restart, it looked like split-brain (while the first node was restarting, one of the left two nodes would be leader, and after the first node finished restarting, it also became a leader), I wonder know why, is it related to force-recovery ?  And how to resovle it...

Provided manifests still experimental and test_keeper.py still failed
We'll update keeper manifests and try to replace --force-recovery to reconfig support look details https://github.com/ClickHouse/ClickHouse/pull/49450, but no have ETA for it


PHP unable to load phpiredis.so

I cannot load the phpiredis module, as it fails to find libhiredis.so.0.10:
PHP Warning:  PHP Startup: Unable to load dynamic library '/usr/lib/php5/20090626/phpiredis.so' - libhiredis.so.0.10: cannot open shared object file: No such file or directory in Unknown on line 0

However, libhiredis.so.0.10 is built and located here:
/usr/local/lib/libhiredis.so.0.10
I built phpiredis with the hiredis location specified here:
./configure --enable-phpiredis --with-hiredis-dir=/usr/local/lib
Is this phpiredis failing, or hiredis?

If anyone have this problem, this is how i fixed in my ubuntu installation. (php-fpm)
Just follow the step from readme
git clone https://github.com/nrk/phpiredis.git
cd phpiredis
phpize && ./configure --enable-phpiredis
make && make install

Then in /etc/php5/mods-available create a file called phpiredis.ini. Add the content below to that .ini
; configuration for phpiredis  module
extension=phpiredis.so

Then
sudo php5enmod phpiredis

Restart your php and websever, should be fine

Thanks in advanced @blacklizard , you saved my day.


improve fallback behavior for queryHistory

when no message history is present the library will log to console that no history is present but i cant catch this in anyway

when no message history is present the library will log to console that no history is present but i cant catch this in anyway

What behaviour would you like to see? queryHistory will return an empty array which should give you a hint that no message was returned.
No message returned is a functionally valid scenario so I am not sure it would make sense to throw an error.

can you demonstrate in what syntax an empty array is returned? from what i see it relies on a callback and if there are no messages it just never calls back and just logs to console no messages present

can you demonstrate in what syntax an empty array is returned? from what i see it relies on a callback and if there are no messages it just never calls back and just logs to console no messages present

https://github.com/status-im/js-waku/blob/2011c76b30da203816da1780a7359c7b812af306/src/lib/waku_store/index.node.spec.ts#L55
But let's say you only want to use the callback: what kind of behaviour or API would you expect?

thanks, i swear i tried that and couldn't get the call to return anything to a var.. ill try again at some point to verify that part
for your second q, i personally would find it handy if when reaching the end of range it returned a false or empty array for the final callback

thanks, i swear i tried that and couldn't get the call to return anything to a var.. ill try again at some point to verify that part
for your second q, i personally would find it handy if when reaching the end of range it returned a false or empty array for the final callback

A false seems hack-ish. An empty array would be ok-ish. I think the most idiomatic way would be an async iterable because it would communicate whether or not it's the last value. WDYT?

agreed, i tried to get an async await response from the call but couldn't seem to do so. ive worked with other libraries that return an empty (sub)array on a callback as well, which is also helpful in some scenarios. both would be most superb, imho

Proposed change:

Create new generator function/API that does the store queries (async iterator)
Use (1) to provide new function that takes a callback parameter, callback is called with empy array after last page (or only on empty array if there no results.
Use (1) to provide function that returns all results in one promise
deprecate current queryHistory.


NVIDIA GPU support

Hello, author of nvidia-docker here.
As many of you may know, we recently released our NVIDIA Docker project  in our effort to enable GPUs in containerized applications (mostly Deep Learning). This project is currently comprised of two parts:

A Docker volume plugin to mount NVIDIA driver files inside containers at runtime.
A small wrapper around Docker to ease the deployment of our images.

More information on this here
While it has been working great so far, now that Docker 1.12 is coming out with configurable runtime and complete OCI support, we would like to move away from this approach (which is admittedly hacky) and work on something which is better integrated with Docker.
The way I see it would be to provide a prestart OCI hook which would effectively trigger our implementation and configure the cgroups/namespaces correctly.
However, there are several things we need to solve first, specifically:

How to detect if a given image needs GPU support
Currently, we are using a special label com.nvidia.volumes.needed, but it is not exported as an OCI annotation (see https://github.com/docker/docker/issues/21324)
How to pass down to the hook which GPU should be isolated
Currently, we are using an environment variable NV_GPU
How to check whether the image is compatible with the current driver or not.
Currently, we are using a special label XXX_VERSION

All of the above could be solved using environment variables but I'm not particularly fond of this idea (e.g. docker run -e NVIDIA_GPU=0,1 nvidia/cuda)
So is there a way to pass runtime/hook parameters from the docker command line and if not would it be worth it? (e.g. --runtime-opt)

+@cpuguy83 we briefly discussed that with you during DockerCon 16.

ping @mlaventure @crosbymichael wdyt?

Worth noting that https://github.com/opencontainers/runtime-spec/pull/483 might affect this

@3XX0 I guess another option would be to have a patched version of runc that has different options and knows about GPUs?
The image detection is a similar issue we have for multiarch in general, and there are flags on hub, but not well exposed yet. This might also work for driver version, let me find the spec.

Yes I thought about it too but I would rather not have to track upstream runc and we would still hit the same problems since the runtime config in Docker is daemon-wide and static.
Thanks, It would be greatly appreciated.

blockquote, div.yahoo_quoted { margin-left: 0 !important; border-left:1px #715FFA solid !important; padding-left:1ex !important; background-color:white !important; } Let me know what you need
Sent from Yahoo Mail for iPhone
On Monday, July 11, 2016, 11:24 AM, Jonathan Calmels<EMAIL_ADDRESS>wrote:
Yes I thought about it too but I would rather not have to track upstream runc and we would still hit the same problems since the runtime config in Docker is daemon-wide and static.
Thanks, It would be greatly appreciated.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I just saw that #24750 was closed and redirected here.
I believe we could already have basic GPU support with Docker Swarm if we were able to add devices when using docker service create. Is it on the roadmap?
Related: https://github.com/NVIDIA/nvidia-docker/issues/141

@3XX0 @flx42 I am the original author of #24750 . I am not sure this question is appropriate to post, if not, please forgive me. If I just want to implement Docker Swarm to orchestrate Swarm cluster supporting GPU, not caring about whether to use native Docker or nvidia-docker, could you give some comments here? Thanks in advance!

--mount type=bind,source=/host/path,target=/container/path

@cpuguy83 thanks!

@justincormack @cpuguy83 Yes, in https://github.com/NVIDIA/nvidia-docker/issues/141 I figured out I can mount the driver the user-level driver files like this:
$ docker service create --mount type=volume,source=nvidia_driver_367.35,target=/usr/local/nvidia,volume-driver=nvidia-docker [...]

But, unless I'm missing something, you can't bind mount a device, it seems to be like a mknod but without the proper device cgroup whitelisting.
$ docker service create --mount type=bind,source=/dev/nvidiactl,target=/dev/nvidiactl ubuntu:14.04 sh -c 'echo foo > /dev/nvidiactl'
$ docker logs stupefied_kilby.1.2445ld28x6ooo0rjns26ezsfg
sh: 1: cannot create /dev/nvidiactl: Operation not permitted

It's probably similar to doing something like this:
docker run -ti ubuntu:14.04
root@76d4bb08b07c:/# mknod -m 666 /dev/nvidiactl c 195 255
root@76d4bb08b07c:/# echo 'foo' > /dev/nvidiactl
bash: /dev/nvidiactl: Operation not permitted

Whereas the following works (well, invalid arg is normal):
$ docker run -ti --device /dev/nvidiactl ubuntu:14.04
root@ea53a1b96226:/# echo foo > /dev/nvidiactl
bash: echo: write error: Invalid argument

@NanXiao regarding your question, please look at https://github.com/NVIDIA/nvidia-docker/issues/141

@flx42 ah yes, that would be an issue. Can you create a separate issue that you can't have a device in a service to track that specific problem?

@justincormack created #24865, thank you!

😈😈
Hello world

On Jul 20, 2016, at 2:58 PM, Felix Abecassis<EMAIL_ADDRESS>wrote:
@justincormack created #24865, thank you!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Few comments

How to detect if a given image needs GPU support
The way we handled this for multi-arch is by explicitly introducing the "arch" filed into the image. I would suggest that we introduce an "accelerator" field to address not only GPUs but in the future for FPGA and other accelerator.

On the compatibility check, I would implement it such that it is optional. A lot of applications can run with or without GPUs, if GPUs are there, they will take advantage of them but if they are not there, they will just run CPU  only mode. If we make the driver check optional, it will make it easy to accommodate this requirement.

Any update here? really look forward to a standard way to use accelerators in container :)

See also https://github.com/kubernetes/kubernetes/issues/19049 . k8s is going to release new version with GPU support.
Swarm is very good for our system (k8s has something we don't need). However, GPU is defintely a key feature and if Swarm doesn't have any clearn plan for it we have to go with k8s :D

Hey guys, would really love to use a GPU supported swarm. This issue is still open, so I guess its not clear if this will be on the roadmap or not?! Any news on this topic?

We would love support. It is unfortunately a very complex issue. I know
someone was looking at a simpler way, will see if it was viable.
Contributions are welcome, it really needs a detailed design proposal of
how to resolve the issues.
On 11 Jan 2017 10:30 a.m., "Martin"<EMAIL_ADDRESS>wrote:

Hey guys, would really love to use a GPU supported swarm. This issue is
still open, so I guess its not clear if this will be on the roadmap or
not?! Any news on this topic?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/issues/23917#issuecomment-271833729,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAdcPB74d8IJOdocE_ygAImAeSxmQ1E8ks5rRK81gaJpZM4I9U2S
.

thx for the update @justincormack

@3XX0 @flx42
What are the low level steps to give a container access to the GPUs?  I was looking though your codebase and seen there are devices that must be added and volumes but I was not sure what the volumes were being used for?  Is that for the libs?
Other than placing the devices inside, are there any other settings that need to be applied?

It's actually tricky, we explain most of it here but there are a lot of corner-cases to think about.
We've been working on a library to abstract all these things, the idea is to integrate it as a RunC prestart hook. We have most of it working now and will publish it soon. The only issue with this approach is that we have to fork RunC and rely on Docker --runtime option.
In the long term, we should probably think about a native GPU integration leveraging something like --exec-opt.

@3XX0 if you want, we can work together on the runc changes.  I think it makes sense to have some support for GPU at that level and will make implementations much cleaner at the higher levels.

It should be pretty straightforward, the only things that need to be done are:

Fix this https://github.com/opencontainers/runc/issues/1044
Append some hooks in the spec

Once 1) is fixed and we have an option to add custom hooks from within Docker (e.g. exec-opt), we won't need the fork anymore (except for backward compatibility)

@3XX0 why use hooks at all?  Can you not populate everything in the spec itself to add the devices, add bind mounts, and give the correct permissions on the device level?

@3XX0 if we have a docker run --gpus what would the input data look like?

Our solution is runtime agnostic and hooks are perfect for that.
We also need to do more than what's exposed by the spec (e.g. update the library cache).

Right now we use an environment variable with a list of comma-separated IDs and/or UUIDs (similar to nvidia-docker NV_GPU). It allows us to be backward compatible with all the Docker versions, encode the GPUs required by a given image (i.e. ENV NVIDIA_GPU=any or ENV NVIDIA_GPU=all) and we can override them on the command line:
docker run --runtime=nvidia -e NVIDIA_GPU=0,1 nvidia/cuda

@crosbymichael We also hit some limitations with Docker, for example a lot of GPU images need large shmsize and memlock limits (our drivers need those). Not sure how to address that at the image level (Docker is not even relying on the spec for /dev/shm).
The workaround is to configure everything at the daemon level once we have https://github.com/docker/docker/issues/29492 fixed but it's far from being ideal.

You can open separate issues for shm limits etc, and we can resolve those
individually.
On 12 Jan 2017 10:19 p.m., "Jonathan Calmels"<EMAIL_ADDRESS>wrote:

@crosbymichael https://github.com/crosbymichael We also hit some
limitations with Docker, for example a lot of GPU images need large shmsize
and memlock limits (our drivers need those). Not sure how to address that
at the image level (Docker is not even relying on the spec for /dev/shm).
The workaround is to configure everything at the daemon level once we have
#29492 https://github.com/docker/docker/issues/29492 fixed but it's far
from being ideal.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/issues/23917#issuecomment-272302172,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAdcPMeUb1F7lBh9XVyRQfL1Xj_bd45eks5rRqb-gaJpZM4I9U2S
.

@justincormack @crosbymichael Do you have a timeline on the containerd 1.0 release and integration in Docker?
Right now the only option we have is to integrate at the runc level given that the containerd "runtime" is hardcoded. I would rather  do it with containerd 1.0 if Docker were to support it.

@3XXO containerd 1.0 is now integrated into Docker.

@3XX0  thanks for your excellent works!
I got some questions about nvidia-docker.
for example, assuming a PC got tow nvidia gpu for GPU A and GPU B. And index of GPU A  is 0, index of GPU B is 1.when I execute command as follows:

NV_GPU='0' nvidia-docker run -d nignx
Can this container use GPU B? By your comments above , it should not.
Since my pc got only one nvidia GPU ,so I can't make a try to confirm this.
However, I have tried this, run following commands respectively.

NV_GPU='0' nvidia-docker run -d nginx

docker run -d nginx
And I did not notice anything different between those two containers.
On both containers I can get the information of my GPU.
Did I miss something or it just goes like this.Looking forward your reply,thanks

@WanLinghao Inside the docker run -d nginx container, you should not see the GPUs, unless you have a special configuration. Can you double-check?

@flx42  I have tried three kinds of command
1. docker run -d nginx
2. docker run --privileged=true -d nginx
3. NV_GPU='0' nvidia-docker run -d nginx
And then I dig into their bashes respectively, execute
find / -name *nvidia*
I got results as follows：
first container and third container:
/sys/bus/pci/drivers/nvidia
/sys/kernel/slab/nvidia_pte_cache
/sys/kernel/slab/nvidia_p2p_page_cache
/sys/kernel/slab/nvidia_stack_cache
/sys/module/drm/holders/nvidia_drm
/sys/module/drm_kms_helper/holders/nvidia_drm
/sys/module/nvidia_modeset
/sys/module/nvidia_modeset/holders/nvidia_drm
/sys/module/nvidia
/sys/module/nvidia/drivers/pci:nvidia
/sys/module/nvidia/holders/nvidia_modeset
/sys/module/nvidia/holders/nvidia_uvm
/sys/module/nvidia_drm
/sys/module/nvidia_uvm
/proc/irq/33/nvidia
/proc/driver/nvidia
/proc/driver/nvidia-uvm

second container:
/dev/nvidiactl
/dev/nvidia0
/dev/nvidia-uvm-tools
/dev/nvidia-uvm
/dev/nvidia-modeset
/sys/bus/pci/drivers/nvidia
/sys/kernel/slab/nvidia_pte_cache
/sys/kernel/slab/nvidia_p2p_page_cache
/sys/kernel/slab/nvidia_stack_cache
/sys/module/drm/holders/nvidia_drm
/sys/module/drm_kms_helper/holders/nvidia_drm
/sys/module/nvidia_modeset
/sys/module/nvidia_modeset/holders/nvidia_drm
/sys/module/nvidia
/sys/module/nvidia/drivers/pci:nvidia
/sys/module/nvidia/holders/nvidia_modeset
/sys/module/nvidia/holders/nvidia_uvm
/sys/module/nvidia_drm
/sys/module/nvidia_uvm
/proc/irq/33/nvidia
/proc/driver/nvidia
/proc/driver/nvidia-uvm

As you can see, command 1 and command 3 makes no difference.
Can you give more information about this.
Looking forward your reply, THANKS!

Ah yes, nvidia-docker (version 1.0) will be passthrough to docker for this nginx image. We enable GPU support only when used with images that are based on our nvidia/cuda images from Docker Hub. We detect if the image has a special label for this purpose.
Note that version 2.0 of nvidia-docker behaves differently (documented on our README).

Any news on this? Would ❤ a LinuxKit distro with nvidia-docker onboard 🙌✨
//cc @3XX0 @justincormack

Trying to revive the interest for supporting OCI hooks here: https://github.com/moby/moby/issues/36987
If there is interested, we can close this issue once it's implemented.


fix: TestCreateCollectorProxy unit test failing on go-tip

Which problem is this PR solving?

Resolves #6198

Description of the changes

After the addition of t.Parallel in cmd/agent/app/builder_test.go in TestCreateCollectorProxy, its test started to fail during random ittterations. This was because in /cmd/agent/app/reporter/connect_metrics.go under NewConnectMetrics function  we are doing expvar.NewString("gRPCTarget") which isnt thread-safe and it should not be changed on initialized
Now we use sync.Once to tackle the above bug/problem

How was this change tested?

running go test -v

Checklist

[x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
[x] I have signed all commits
[ ] I have added unit tests for the new functionality
[x] I have run lint and test steps successfully

for jaeger: make lint test
for jaeger-ui: yarn lint and yarn test

Thanks!


handling fusion of two rightmost columns in hit summary lines

addressing issue #33

Changes Unknown when pulling ff6eaf1547aaeda2b1c1263aa34af4a289f31af1 on sjanssen2:fusefields into ** on biocore:split_search**.


impl(bigquery): introduce JobClient with GetJob API

This change is

I can add the connection test after this PR. Can you give me some example links for reference?

(Same link as before)
https://github.com/googleapis/google-cloud-cpp/blob/main/generator/integration_tests/tests/golden_thing_admin_connection_test.cc
Ahhhh... Sorry, I think I see what is confusing. Despite the fact that */integration_tests/* is contained in the filepath, the above is actually a unit test.
For background, it is an integration test of our generator to generate the files found here: https://github.com/googleapis/google-cloud-cpp/tree/main/generator/integration_tests/golden
But then to verify that the generated code works, we unit test it. Those tests are contained here: https://github.com/googleapis/google-cloud-cpp/tree/main/generator/integration_tests/tests

I'll definitely be doing the integration tests just a bit later or I may work in parallel but would be sending other apis for review as well and may focus on that initially.

Ack. This is fine with me.

I am assuming its okay to add my job_connection_test.cc file in v2/minimal/internal folder along with all the other files I have?

Yeah. That is ideal.


[imgui] Update to 1.88

Update imgui from 1.87 to 1.88.
Changelog : https://github.com/ocornut/imgui/releases/tag/v1.88

@RT222 ,Thanks for your pr, looks ci tested failed on port 'imgui-sfml',
This is error log, please take a look:
install-x64-osx-dbg-out.log

Found the issue, this change was the culprit :

Misc: Added constexpr to ImVec2/ImVec4 inline constructors. (https://github.com/ocornut/imgui/pull/4995)

Imgui 1.88 started to introduce C++11 features, and imgui-sfml was built for C++03 on OSX by default.


Feature Request: finer user control

Feature Requested
Specific functions I'd like to see are:

User can create presets that specify on/off/unchanged plugins;
User can create a function to mass toggle user-specified plugins;

Mass toggle has options always toggle, toggle if on, toggle if off.

Something similar has been suggested in #2 and not implemented, but the issue was closed, so I'm bringing it up again (hope you don't mind it!).
Relevant Screenshot
No response
Checklist

[X] The feature would be useful to more users than just me.

As an extra to this, it'd also be very nice for users if, when a user installs a new plugin, D&Q presented a prompt asking whether the user would like to add this new plugin to any existing presets or create a new one. Not sure how feasible this is, but it'd be very nice QoL-wise.


RPC Timeout kills docker container

When running an empty planaria write project from block 1 I keep getting RPC timeouts after about every ~1k blocks that kills the entire docker container. The bitcoind is running on the same machine and runs with the flags rpcworkqueue=512 and rpcthreads=64.
RPC BEGIN 2298 Tue Mar 12 2019 23:20:11 GMT+0000 (Coordinated Universal Time)
Err =  Error: Bitcoin JSON-RPC: Request Error: connect ETIMEDOUT <IP_ADDRESS>:8332
    at ClientRequest.<anonymous> (/planaria/node_modules/bitcoind-rpc/lib/index.js:113:15)
    at ClientRequest.emit (events.js:182:13)
    at Socket.socketErrorListener (_http_client.js:391:9)
    at Socket.emit (events.js:182:13)
    at emitErrorNT (internal/streams/destroy.js:82:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)
/planaria/bit.js:54
          throw new Error(err)
          ^

Error: Error: Bitcoin JSON-RPC: Request Error: connect ETIMEDOUT <IP_ADDRESS>:8332
    at /planaria/bit.js:54:17
    at ClientRequest.<anonymous> (/planaria/node_modules/bitcoind-rpc/lib/index.js:116:7)
    at ClientRequest.emit (events.js:182:13)
    at Socket.socketErrorListener (_http_client.js:391:9)
    at Socket.emit (events.js:182:13)
    at emitErrorNT (internal/streams/destroy.js:82:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)
2019-03-12T23:22:22.510+0000 I NETWORK  [conn2] end connection <IP_ADDRESS>:56822 (0 connections now open)
Exited 0

+1
Meet the same issue when I try to crawl the remote nodes.
Not sure what is the best practice of rpc retry in nodejs.


Online XP tracker doesnt show progress

This means that it permananetly states either one of two things

Show 0 XP gained in all skills (frequent)
Show my total xp gained in one day (infrequent)

That is because the API is returning nothing.


Change how results are unmarshaled from rego

We were assuming the results came from rego as []string, but they were begin returned as []interface{}. The logic was detecting those as invalid and erroring as a consequence.
Signed-off-by: Jose Fuentes<EMAIL_ADDRESS>

Ahh, very nice spot. :clap:
/lgtm
/approve


fatal errors thrown in scalacheck mode lose stacks

see this discussion:
https://gitter.im/scalameta/munit?at=5eb9dc2310d5ec031aff33d9
you can repro it with a simple property:
  property("hide my stacks") {
    Prop.forAll { i: Int =>
      if (i > 0) throw new StackOverflowError()
      else Prop(true)
    }
  }

Thank you for reporting! There's a pending fix in #129

Fix released as 0.7.7

Thank you so much! I appreciate your work on this. It is improving my enjoyment of using scala.

I’m glad to hear that! I didn’t anticipate so many people would be interested in MUnit, I started the project originally as an experiment to implement an sbt testing framework that reproduces the semantics of the Pants JUnit runner 😅

I think many folks think scalatest is over complex. "Tests as values" also has a lot of customers. Lastly, your API is just very enjoyable, and the UX touches are really great in reporting.


make lambda deployable to any environment

This is a temporary solution that requires the terraform user to have the lambda package on their local filesystem. In a separate PR we will change this so it can be done from the nixops machine and will also be part of the continuous delivery server.

I have no idea what any of this means, sadly.
I'm a bit confused, though: shouldn't the lambda package be coming from nix somehow?

So we can create lambda packages with nix build -f default.nix marlowe-symbolic-lambda however getting that package into the lambda requires getting terraform to upload it. We could put it in an s3 bucket and save the terraform user the trouble but then you need to create a bucket per region and the user will have to find the version and lots of other mess. For now there are only 2 or 3 people using terraform anyway and I intend to move this across to the deployment server asap so the issue should go away. This is a stop-gap solution to make sure that all environments work and the CD server works.


Setting the logging config in Tutorial 1

At the end of Tutorial 1, Section 1, it says "The output looks like this:". However, following only this tutorial up to this point, one would not get any output at all as python's default logging level is logging.WARNING, and one is never instructed to set the logging level or call propulate.utils.set_logger_config().

Thanks for your comment! I think this is only the case for the linked ReadTheDocs page which is not yet updated (this will hopefully happen very soon). The actual script in the Github repo (which should also be linked on the RTD page at the very top) uses the logger. I will change the title of this issue to "Updating static ReadTheDocs pages to current master stage" and assign myself to it. There will be a complete rework of RTD once other things (parallel checkpointing with hdf5, new solvers, more comprehensive tests, etc.) will be merged and we have a new PyPI release.


Clarify CHANGELOG instructions in "Committing code" docs

This changes the "Committing code" documentation to clarify whose role it is to update the CHANGELOG and release notes. It’s quite common for contributors to Wagtail to update the CHANGELOG / release notes in their PRs, which is a source of merging conflicts.
New version:

[…]

Thank you @gasman! Fastest PR review turn-around time in history 😄


Check failed: error == cudaSuccess (30 vs. 0)  unknown error

Hello,
I have a problem with using GeForce GTX 1080Ti for machine learning (CAFFA framework)
My platform:
ubuntu 16.04, Cuda V8.0.61, CuDNN8.0
I suggest my version is too new and I have to downgrade.
Could you advise the best way for solve my problem?
Find in following more details:
nvcc is warning about deprecation. But it not error and as I know it is about future.
nvcc warning : The 'compute_20', 'sm_20', and 'sm_21' architectures are deprecated, and may be removed in a future release

CAFFE  & py-faster-rcnn install with no error, but on training with py-faster-rcnn I recieve next massage:
I0601 15:30:44.833746 28338 layer_factory.hpp:77] Creating layer input-data
I0601 15:30:44.834151 28338 net.cpp:106] Creating Layer input-data
I0601 15:30:44.834161 28338 net.cpp:411] input-data -> data
I0601 15:30:44.834169 28338 net.cpp:411] input-data -> im_info
I0601 15:30:44.834178 28338 net.cpp:411] input-data -> gt_boxes
F0601 15:30:44.852488 28338 syncedmem.hpp:18] Check failed: error == cudaSuccess (30 vs. 0)  unknown error
*** Check failure stack trace: ***

More outputs:
~/caffe#nvcc -V gives

nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2016 NVIDIA Corporation
Built on Tue_Jan_10_13:22:03_CST_2017
Cuda compilation tools, release 8.0, V8.0.61

~/caffe# nvidia-smi
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 378.13                 Driver Version: 378.13                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  Graphics Device     Off  | 0000:01:00.0      On |                  N/A |
| 23%   39C    P8    17W / 250W |    578MiB / 11171MiB |     15%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|    0      1155    G   /usr/lib/xorg/Xorg                              20MiB |
|    0      1341    G   /usr/lib/xorg/Xorg                             262MiB |
|    0      1794    G   compiz                                          82MiB |
|    0      1939    G   fcitx-qimpanel                                   9MiB |
|    0      2015    G   ...el-token=3645A468136299F390B7B0886FE96671   173MiB |
+-----------------------------------------------------------------------------+

Sounds like a Caffe problem. What version of Caffe are you using? You might want to ask over at NVIDIA/caffe instead of here.
You can ignore the warnings about sm20, etc.

I have solved this problem with
sudo ldconfig /usr/local/cuda/lib64
And just in case someone encounters the same problem this link may be helpful: https://askubuntu.com/questions/889015/cant-install-cuda-8-but-have-correct-nvidia-driver-ubuntu-16
Thank you for your reply anyway!

CUDA runtime error (30) might show if your program is unable to create or open the /dev/nvidia-uvm device file. This is usually fixed by installing package nvidia-modprobe:
sudo apt-get install nvidia-modprobe
thanks to @gheinrich

Hi, I met the same problem yesterday, Google search gave me a lot of related posts but none of them solved my case. Actually, this CudaSuccess (30 vs 0) error may not related to a specific problem, but usually indicates that the GPU driver or CUDA tool kits is not functioning well.
In my case (Ubuntu14.04), the GPU driver version (384) is somehow incompatible with my CUDA toolkit 8.0. At that time, I installed GPU dirver and CUDA toolkits seperately without knowing they can not work with each other. I followed the CUDA installation guide provided by Nvidia to remove my previous GPU driver and CUDA toolkit.  After that, I downloaded CUDA toolkit from Nvidia again. This time, I install GPU driver along with CUDA tookits and the problem was gone.
Hope my experience will be useful.

Indeed, the problem was the version of Nvidia driver and CUDA.
As @laibruce said, to easily check this :
cd /usr/local/cuda/samples/1_Utilities/deviceQuery sudo make ./deviceQuery
With Nvidia 384 drivers and CUDA 8.0. I had : CUDA Driver Version / Runtime Version          9.0 / 8.0

sudo ldconfig /usr/local/cuda/lib64

use$ sudo ldconfig /usr/local/cuda/lib64
but outputs:
/sbin/ldconfig.real: /usr/local/cuda/lib64/libcudnn.so.7 is not a symbolic link


Download links are broken

I tried to follow the guide and add dependency to my build.gradle but the link is dead.

Can confirm, I've released my mod a few days ago with version 1.19.4:4.1.1 and it compiled just fine. Opened the project now and gave it a gradle reload, Indeed it no longer finds the jar. Althought it seems is only for the fabric jar, I've done the same thing in Forge and I got no issue

Can you confirm if this still occurs?
We had a brief period where the Maven repo was down, but this should be rectified now


MachineLearning: description should not contain HTML tag

https://github.com/Azure/azure-rest-api-specs/blob/master/arm-machinelearning/2016-05-01-preview/swagger/webservices.json#L5
"description": "These APIs allow end users to operate on Azure Machine Learning Web Services resources. They support the following operations:

Create or update a web service

Get a web service

Patch a web service

Delete a web service

Get All Web Services in a Resource Group

Get All Web Services in a Subscription

Get Web Services Keys

",

@amarzavery I'm not sure based on the history of the file to who I should assign this. If you could take a look :)

@ericwill-msft and @tudorid - can you take a look at this issue?

@lmazuel : Could you clarify the issue with HTML in description?

@kirthik not all language use the same kind of generator to build their technical documentation. Or we can use documentation generator that are not HTML at all.
In case of Python, HTML tags are not expected and produce bad documentation. So, I see two solutions:

We consider description fields are HTML, and we have to remove them in Python in our pre-process treatment
We consider description fields are basic text, and not HTML tags are allowed.

No HTML is more open to scenarios. But if it's part of the docs.microsoft.com process to produce doc, I can understand :)

Note that Swagger spec says:
description - string - A short description of the target documentation. GFM syntax can be used for rich text representation.

I'd like to upvote this issue. I saw HTML elements in monitor's SDK as well. It's a bad practice. HTML is a presentation level language, it shouldn't be used to describe rich text in lower level spec definitions. The higher level conversion of the spec, for example, Python SDK pulls the HTML tags directly into their doc string (example) will introduce unwanted noise into CLI.


Parsing error when linting .astro files

When I add Sheriff to my Astro project, I get various parsing errors like the following:
/[...]/capricious-chroma/src/components/Welcome.astro
  1:2  error  Parsing error: Expression expected

/[...]/capricious-chroma/src/layouts/Layout.astro
  1:10  error  Parsing error: '>' expected

/[...]/capricious-chroma/src/pages/index.astro
  1:2  error  Parsing error: Expression expected

✖ 3 problems (3 errors, 0 warnings)

To reproduce:

Create a new Astro project by running npm create astro@latest and selecting the default settings:

❯ npm create astro@latest

> npx
> create-astro

 astro   Launch sequence initiated.

   dir   Where should we create your new project?
         ./capricious-chroma

  tmpl   How would you like to start your new project?
         A basic, minimal starter

  deps   Install dependencies?
         Yes

   git   Initialize a new git repository?
         Yes

      ✔  Project initialized!
         ■ Template copied
         ■ Dependencies installed
         ■ Git initialized

  next   Liftoff confirmed. Explore your project!

         Enter your project directory using cd ./capricious-chroma
         Run npm run dev to start the dev server. CTRL+C to stop.
         Add frameworks like react or tailwind using astro add.

         Stuck? Join us at https://astro.build/chat

╭─────╮  Houston:
│ ◠ ◡ ◠  Good luck out there, astronaut! 🚀
╰─────╯

Set up Sheriff by running npm init @sherifforg/config and selecting No for both the experimental eslint.config.ts file and support for Prettier:

❯ npm init @sherifforg/config

><EMAIL_ADDRESS>npx
> create-config

Welcome to Sheriff! 👋
This wizard will guide you through the setup of Sheriff in your project.
Let's get started!

✔ Do you prefer the config as a Typescript file? The generated config will be a eslint.config.ts file (Experimental)
No
◐ No ESLint config files were found. Generating and configuring eslint.config.js file...

 WARN  If you have other ESLint configs in your project, remove them

◐ 'Astro' package found in the project. Setting up support for it...
ℹ Setting Sheriff with options:

 ╭──────────────────────────────────────────────╮
 │                                              │
 │  {                                           │
 │    "react": false,                           │
 │    "lodash": false,                          │
 │    "remeda": false,                          │
 │    "next": false,                            │
 │    "astro": true,                            │
 │    "playwright": false,                      │
 │    "jest": false,                            │
 │    "vitest": false                           │
 │  }                                           │
 │                                              │
 ╰──────────────────────────────────────────────╯

✔ Successfully generated eslint.config.js file

✔ Do you want to add Prettier support in the workspace?
Tip: if you want to use Prettier from the root of the monorepo, choose 'No'.
No
◐ Installing eslint, eslint-define-config, eslint-config-sheriff...
ℹ Detected package manager: npm
◐ Installing dependendencies...
npm warn ERESOLVE overriding peer dependency
npm warn ERESOLVE overriding peer dependency
npm warn ERESOLVE overriding peer dependency
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported

added 389 packages, and audited 688 packages in 17s

295 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
✔ eslint and eslint-define-config and eslint-config-sheriff were installed successfully
ℹ You're all set! Happy coding 🎉

Run ESLint:

❯ npx eslint .

[see above]

Please note that this issue may be related to https://github.com/ota-meshi/eslint-plugin-astro/issues/447.

I'll look into it. Clearly a parsing issue.


Record an updated video / screencast on how to install Docker on Windows

While there is a video already on the installation page, it is silent and a bit out of date. The installation documentation could really benefit from a video which walked the user through how to install the latest Docker on Windows and had narration explaining what to do.
The installation instructions for Windows are available at https://docs.docker.com/installation/windows/
While I don't have personal experience with it, I understand that ezvid is free software that works well to capture, narrate and upload screen casts. http://www.ezvid.com/
When complete please upload to Youtube under a Creative Commons license and submit a pull request to add the video to the installation documentation page.

This can easily go out of date when we release Docker 1.6 with docker.exe (client) and provide Chocolatey distribution as well. @spf13 please feel free to assign me, I'll happily do once I finish those stuff.

#dibs

@nebulae1 please do not #dibs this, with the 1.6 release the instructions will significantly change and we will have more than one distribution methods. (also you can see I dibs'ed above :smile:) @jessfraz to remove the party-related labels.

Ok... thought it would be a good one since I just completed the install...

@nebulae1 we will be slightly changing the boot2docker installation process by installing docker.exe on windows and it will no longer put users ssh-ed into boot2docker VM.
it will be also usable through cmd.exe/powershell, therefore instructions are changing a lot. I will be updating documentation as well as shooting new videos for this as you can see referenced above. https://github.com/boot2docker/windows-installer/issues/80
Thanks.

We would still absolutely love if anyone decided to fix this issue. I think we can all agree it is not technically an issue with Docker itself or a bug with how the docker engine works.
Please still feel free to complete this task. But we are going to close the issue in an effort to clean house so we can focus on bug hunting.

@spf13 ^ ?


plugin.apply is not a function

Vue.js version:     "vue": "2.0.1",
Vuex version: "vuex": "2.1.2"
Vue-pagination version: "0.2.6",
consumed using: webpack laravel mix
FULL error message (including stack trace):

Uncaught TypeError: plugin.apply is not a function
    at Function.Vue.use (app.js:8942)
    at Object.defineProperty.value (app.js:42692)
    at __webpack_require__ (app.js:660)
    at fn (app.js:84)
    at Object.<anonymous> (app.js:39724)
    at __webpack_require__ (app.js:660)
    at fn (app.js:84)
    at Object.<anonymous> (app.js:88586)
    at __webpack_require__ (app.js:660)
    at app.js:709

relevant code:

import VuePagination from 'vue-pagination-2';
let useVuex = true
Vue.use(VuePagination, [useVuex])

Duplicate of #8


tweepy.error.TweepError

tweepy.error.TweepError: Failed to send request: HTTPSConnectionPool(host='api.twitter.com', port=443):
Max retries exceeded with url: /1.1/users/show.json?id=twitter
(Caused by NewConnectionError
('<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x00000000031A8400>:
Failed to establish a new connection: [Errno 10060] ',))
the code is
import tweepy
consumer_key=""
consumer_secret=""
access_token=""
access_token_secret=""
auth = tweepy.OAuthHandler(consumer_key, consumer_secret)
auth.set_access_token(access_token, access_token_secret)
api = tweepy.API(auth)
user = api.get_user('twitter')
print user.screen_name
print user.followers_count
for friend in user.friends():
print friend.screen_name

Your code is running fine on my machine.
Can you see if you still have a problem? If so, what version of tweepy are you using? What version of python are you using?

You somehow can't connect to "api.twitter.com", that's not a problem with this library

Please don't necrobump old closed issues.
This is an issue with your SSL certificate when connecting to Twitter's API, which is unrelated to this issue and not an issue with Tweepy.
For code block usage, see https://docs.github.com/en/github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.


Implement .await completion for futures

Closes #1263 with completion for .await syntax for types that are implementing std::future::Future trait.
r? @flodiebold

@flodiebold thank you for feedback and assistance, should be good to go now.
@bjorn3 since no_std support is not considered (yet), I ditched lang_item (implemented in commit ab7774545cb5e45064c907429417bdee8d89f4d4) in favor of std::future::Future path resolution proposed by @flodiebold.

@matklad I changed the order of imports and used early returns as you recommended.

Looks good to me now.
bors r+


foundation-apps doesnt work and manual method produces hung process

Installed myApp using manual method described in gitIssue, when npm start used (after uninstalling bundler and reinstalling) process just hangs indefinitely,
[tom@server ~]$ cd myApp
[tom@server myApp]$ npm start

<EMAIL_ADDRESS>start /home/tom/myApp
gulp

[10:41:34] Using gulpfile ~/myApp/gulpfile.js
[10:41:34] Starting 'build'...
[10:41:34] Starting 'clean'...
[10:41:34] Finished 'clean' after 13 ms
[10:41:34] Starting 'copy'...
[10:41:34] Starting 'copy:foundation'...
[10:41:34] Finished 'copy:foundation' after 211 ms
[10:41:34] Starting 'sass'...
[10:41:35] Starting 'uglify:foundation'...
[10:41:35] Starting 'uglify:app'...
[10:41:35] Finished 'copy' after 940 ms
[10:41:35] Finished 'uglify:app' after 237 ms
[10:41:35] Finished 'uglify:foundation' after 632 ms
[10:41:35] Starting 'uglify'...
[10:41:35] Finished 'uglify' after 19 μs
[10:41:36] Finished 'sass' after 1.47 s
[10:41:36] Starting 'copy:templates'...
[10:41:36] Finished 'copy:templates' after 17 ms
[10:41:36] Finished 'build' after 1.73 s
[10:41:36] Starting 'server'...
[10:41:36] Webserver started at http://localhost:8079
[10:41:36] Finished 'server' after 406 ms
[10:41:36] Starting 'default'...
[10:41:36] Finished 'default' after 31 ms
hangs indefinitely.............

What do you see when you visit http://localhost:8079 in your browser?

it will not load that page at all in any browser, a port issue? running apache server on centos with webmin/virtualmin interface

when searching version, using foundation version, foundation -v or foundation --version or foundation-cli version or any of these variants get
[tom@server myApp]$ foundation version
module.js:340
throw err;
^
Error: Cannot find module 'config-chain'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/home/tom/.nodemodglobal/lib/node_modules/foundation-cli/node_modules/npm/lib/config/core.js:2:10)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
[tom@server myApp]$

I give up

The browser tries to load then times out and says could not load this
page...
On 24 Nov 2015 16:45, "Gerd Jungbluth"<EMAIL_ADDRESS>wrote:

What do you see when you visit http://localhost:8079 in your browser?
—
Reply to this email directly or view it on GitHub
https://github.com/zurb/foundation-apps/issues/721#issuecomment-159309042
.

latest attempt to run, checked iptables, port 8079 open, and server listening at this port on localhost but no joy...

<EMAIL_ADDRESS>start /home/tom/myApp
gulp

[14:42:45] Using gulpfile ~/myApp/gulpfile.js
[14:42:45] Starting 'build'...
[14:42:45] Starting 'clean'...
[14:42:45] Finished 'clean' after 22 ms
[14:42:45] Starting 'copy'...
[14:42:45] Starting 'copy:foundation'...
[14:42:46] Finished 'copy:foundation' after 398 ms
[14:42:46] Starting 'sass'...
[14:42:46] Starting 'uglify:foundation'...
[14:42:46] Starting 'uglify:app'...
[14:42:47] Finished 'copy' after 1.44 s
[14:42:47] Finished 'uglify:app' after 205 ms
[14:42:47] Finished 'uglify:foundation' after 628 ms
[14:42:47] Starting 'uglify'...
[14:42:47] Finished 'uglify' after 12 μs
[14:42:47] Finished 'sass' after 1.74 s
[14:42:47] Starting 'copy:templates'...
[14:42:47] Finished 'copy:templates' after 16 ms
[14:42:47] Finished 'build' after 2.2 s
[14:42:47] Starting 'server'...
[14:42:49] Webserver started at http://localhost:8079
[14:42:49] Finished 'server' after 1.23 s
[14:42:49] Starting 'default'...
[14:42:49] Finished 'default' after 22 ms
events.js:72
throw er; // Unhandled 'error' event
^
Error: listen EADDRINUSE
at errnoException (net.js:905:11)
at Server._listen2 (net.js:1043:14)
at listen (net.js:1065:10)
at net.js:1147:9
at asyncCallback (dns.js:68:16)
at Object.onanswer [as oncomplete] (dns.js:121:9)
npm ERR! Linux 2.6.32-042stab108.2
npm ERR! argv "node" "/home/tom/.nodemodglobal/bin/npm" "start"
npm ERR! node v0.10.40
npm ERR! npm  v3.5.0
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: gulp
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'gulp'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the foundation-apps-template package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     gulp
npm ERR! You can get their info via:
npm ERR!     npm owner ls foundation-apps-template
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/tom/myApp/npm-debug.log
[tom@server myApp]$
npm-debug.txt

https://github.com/zurb/foundation-apps/issues/147
See issue from almost exactly one year ago no resolution then either at least not one that helps... Carried out All these steps and no use,  running as su do is not a solution...

Get started building amazing websites with Foundation. We want to get you up and running as quickly as possible so you can build great things!
What a joke....

@dredgerman you are so right!!!
second day with correction of their npm dependencies - as quickly as possible


Options to hide shapes columns in large datasets in FeatureTableFX

Automatically applies when a new feautre list is loaded.


routing: Add Readyset.route

Adds a Readyset.route method, which takes a block and routes to
ReadySet all the queries that occur within that block.
NOTE: This PR is stacked on top of #46 and must be merged after that is merged

Sorry, I didn't notice the dependency on PR #41. Reverted for now.

@helpotters Fixed the prevent_writes docs and replied to your questions!

Merging after #46


Universal Wrapper Device may fail to recognize device type

Referencing channel 3 of HM-LC-Sw4-DR does not recognize channel type. While it does work for the other 3 channels:
CUX9001004:	CCU(SWITCH,'KEQ084XXXX:2.STATE') trigger(2:1.000)
CUX9001005:	CCU(SWITCH,'KEQ084XXXX:1.STATE') trigger(2:1.000)
CUX9001007:	CCU(SWITCH,'KEQ084XXXX:4.STATE') trigger(2:1.000)
CUX9001008:	CCU((null),'KEQ084XXXX:3.STATE') trigger(2:1.000)

Affects Version 1.10b1 on RaspberryMatic <IP_ADDRESS>70731.

This rather looks like a ReGaHss problem with your device.
Try the following HM-script to verify that.
string c; foreach (c,root.Channels().EnumUsedIDs()){   var c1 = dom.GetObject(c);   if (c1.Address().Find('KEQ084XXXX') != -1) {     var c2 = dom.GetObject(c1.Interface());     WriteLine(c2.Name() # '|' # c1.Address() # '|' # c1.HssType());   } }

Thanks for looking, result is:
BidCos-RF|KEQ084XXXX:1|SWITCH
BidCos-RF|KEQ084XXXX:2|SWITCH
BidCos-RF|KEQ084XXXX:3|SWITCH
BidCos-RF|KEQ084XXXX:4|SWITCH

I noticed I have attached additional custom datapoints to this channel. Here is an extract of XMLAPI statelist.cgi.

Dropping and recreating the custom data points after CUxD has made its checks seems a working workaround (until next reboot). Hence suggesting to reopen this issue to improve the datapoint matching algorithm in CUxD.

I don't see a problem with datapoint matching here.
What are the CUxD Syslog messages after you reboot your CCU?
There should be lines like this in the log:

... setup CUX9001004: ...
...
...

Maybe the channels are not fully available directly after the CCU reboot?
The wrapper device should work anyway, or doesn't it?

Thanks for pointing into direction, the error in Syslog reads:
Aug 15 20:24:53 homematic-raspi local0.err ReGaHss: Error: IseESP::ScriptRuntimeError: string c; string ret; foreach (c,root.Channels().EnumUsedIDs()){ var c1 = dom.GetObject(c); if (c1.Address().Find('KEQ084XXXX:3') != -1) { var c2 = dom.GetObject(c1.Interface()); ret = c2.Name() # '|' # c1.Address() # '|' # c1.HssType() # '|'; string dp; foreach (dp,c1.DPs()) { ret = ret # dom.GetObject(dp).HssType() # '|'; } Write(ret); quit; } }  [iseESPexec.cpp:12344]

Indeed dom.GetObject(dp).HssType() returns nothing for custom datapoint (that is variable assigned to a channel), hence the concatenation fails. A bit unsure what part is generating that script...

I can confirm, this affects only the logs and user interface (the 2 read only fields used for device configuration feedback).

CUxD generates this script, so maybe it has to check dom.GetObject(dp).HssType() for existence first?
Since I don't have custom datapoints, can you please check if that would work?
Or maybe use another method to return the datapoints?
The HM-script is defined in cuxd.inc, section ##15
Please let me know the results.

Thanks for pointer.
We can check that the DP object has the TypeName "HSSDP" (btw custom DP have the type VARDP), see branch fix-VARDP. For the moment, I am still not clear of the actual meaning of '|' char in section ##28 start of lines 503, 504 and 507, hence waiting until the fix is complete before creating the pull request...

The '|' lines are comment lines. They are ignored.
section ##28 is used for a similar (older) function with a different return value in CUxD device (05) FS20 Relais.

Thanks, was thinking it was a complex way of doing conditional statement's injections ;-)
Issue shall now be fixed by pull request #7 .
Regards

@mulder999 Thanks for this nice fix for recent CCU firmwares (2.29.18+)
@uwe111 please take over this file into your own build environment for the CCU1+CCU2 builds of future CUxD versions.


suggest date window on users tab search

🚀 Deployed on https://64aedf4ca1c5bb00a9ea607a--cozy-fox-0defec.netlify.app


CLICK TO SEE PORTFOLIO-->https://amporfolio.surge.sh/index

https://amporfolio.surge.sh/index
Portfolio Author

Portfolio Link?

GitHub Link:

Tech Stack

Hello, @aditimahabole thanks for contributing to this project, but as @piyush-multiplexer said, portfolio should be added to the Readme file inside the table.
Here's an open issue you can check out #104.
I'll be closing this pull request for now.
Thanks for your PR.


Fix property assignment where value is zero

When an attribute value is 0 (or false) the conditional in the prop method returns false and skips the assignment to the p object. Using hasOwnProperty avoids this issue.

the test we actually want is probably a[k] === undefined

Ooh, good catch. This does appear to be a safer catch. I've updated the PR. Thanks.

I'm grooming my backlog and closing stale PRs.


Allow log file creation to be disabled

Hey @pg9182 , can you  fill in the feature request details here? Perhaps a why? Thanks!

Working on an implementation of this now. Will be a launch argument when it is fully implemented. As of right now however more work is needed. Expect it to be working in a few days though

I think I add what you wanted #44

Implemented in https://github.com/R2Northstar/NorthstarLauncher/commit/c9d66513a85d5325d3d002ca16c82d8302ec0ea2

Thanks!


Prisma Client is returning undefined for all but one model.

Bug description
I have setup a ReST API project from typescript-express-starter with Prisma as ORM. It has a basic 'user' model and authentication setup. It works well but when I followed the given 'user' model and created two more models. These are generated in database and types too, but when I call the model methods from Prisma Client it returning undefined. I have also asked it in stackoverflow but no working answers. Here is the Github Repo. It is containerized.
How to reproduce

Expected behavior
The request to the localhost:3000/offers and localhost:3000/users should be similar.
Prisma information
generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "mysql"
  url      = env("DATABASE_URL")
}

model User {
  id       Int    @id @default(autoincrement())
  email    String @unique
  password String
}

model Product {
  id              Int     @id @default(autoincrement())
  name            String  @unique
  veg             Boolean
  price           Int
  image           String
  discountedPrice Int
  description     String
}

model Offer {
  id    Int    @id @default(autoincrement())
  name  String
  image String
}

Environment & setup
I am running it in docker container with the help of docker-compose.
If you're trying to run prisma commands in docker container, make sure to change the hostname from 'mysql' to 'localhost' in the .env file.
Prisma Version
prisma               : 2.23.0
@prisma/client       : 2.24.1
Current platform     : debian-openssl-1.1.x
Query Engine         : query-engine adf5e8cba3daf12d456d911d72b6e9418681b28b (at<EMAIL_ADDRESS>Migration Engine     : migration-engine-cli adf5e8cba3daf12d456d911d72b6e9418681b28b (at<EMAIL_ADDRESS>Introspection Engine : introspection-core adf5e8cba3daf12d456d911d72b6e9418681b28b (at<EMAIL_ADDRESS>Format Binary        : prisma-fmt adf5e8cba3daf12d456d911d72b6e9418681b28b (at<EMAIL_ADDRESS>Default Engines Hash : adf5e8cba3daf12d456d911d72b6e9418681b28b
Studio               : 0.393.0

@krishnapaul242
Sorry for late reply here. Can you please fill out the how to reproduce section? Simply tell us which route to look at otherwise your codebase looks decently sized.
Also, try this again with the latest version.

6 months later no further information, so I think we can consider this solved.
If this ever happens again, please comment here or even better - create a new issue. Thanks.


Blender 4 support

I realized that the connector only support Blender 3.X. There is a mention that there is an experimental support for the version 4 but I can't find any instructions. Also, what is the longer-term perspective for the version 4 support?

Simply install via Speckle Manager or through our manual installers . We currently will install to Blender 3.0 - 4.1.
For more instructions, see our docs and tutorial video.
We have been describing Blender 4.X as experimental only in-so-far as we test our connector more rigorously with the latest LTS version of blender (Currently Blender 3.6).
However we've done a fair bit of testing on Blender 4.0 as well, and everything appears to be working.
Any problems or bugs, please don't hesitate to file a bug report.

Closing this issue for now, since Blender 4 is fully supported. We'll update the messaging to removed the "experimental" word after our next release.


setup similar language use one language

Hi
i have two folders(zh and en) to store language data, and i18next-browser-languageDetector detect language may be 'zh', 'zh-CN', 'zh-TW', 'en', 'en-US' etc
i want the chinese('zh','zh-CN' etc) use data in folder 'zh' and english('en', 'en-US' etc) use data in folder 'en'.
but i don't know how to set i18next to satisfy my demand, could you tell me how to do this.
thanks.

try init with options { load: 'languageOnly' }

option { load: 'languageOnly' } is ok, thank you. : )


Regression: unable to handle request: Unsupported proxy type: "https" when using system proxy on Windows

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting a bug unrelated to a specific site
[X] I've verified that I'm running yt-dlp version 2023.07.06 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
On Windows, when system proxy is on, yt-dlp cannot do any network activity. This is a regression after the recent networking architecture rewrite.
Based on Nightly build, I found the following regression window: https://github.com/yt-dlp/yt-dlp/compare/1ba6fe9db5f660d5538588315c23ad6cf0371c5f...131d132da5c98c6c78bd7eed4b37f4458561b3d9
My proxy setting (just typical stuff):

Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
>yt-dlp -vU --ignore-config
[debug] Command-line config: ['-vU', '--ignore-config']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[131d132da] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: ffmpeg 6.0-full_build-www.gyan.dev (setts), ffprobe 6.0-full_build-www.gyan.dev, phantomjs 2.1.1, rtmpdump 2.3
[debug] Optional libraries: Cryptodome-3.18.0, brotli-1.0.9, certifi-2023.05.07, mutagen-1.46.0, sqlite3-2.6.0, websockets-11.0.3
[debug] Proxy map: {'http': 'http://<IP_ADDRESS>:7890', 'https': 'https://<IP_ADDRESS>:7890', 'ftp': 'ftp://<IP_ADDRESS>:7890'}
[debug] Loaded 1855 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-nightly-builds/releases/latest
Traceback (most recent call last):
  File "yt_dlp\__init__.py", line 971, in _real_main
  File "yt_dlp\update.py", line 287, in update
  File "yt_dlp\update.py", line 268, in check_update
  File "yt_dlp\update.py", line 221, in latest_version
  File "yt_dlp\update.py", line 211, in _get_actual_tag
  File "yt_dlp\utils\_utils.py", line 5009, in wrapper
  File "yt_dlp\update.py", line 192, in _get_version_info
  File "yt_dlp\YoutubeDL.py", line 4037, in urlopen
  File "yt_dlp\networking\common.py", line 102, in send
yt_dlp.networking.exceptions.NoSupportingHandlers: Unable to handle request: Unsupported proxy type: "https" (urllib)

This should have been avoided with https://github.com/yt-dlp/yt-dlp/commit/3f66b6fe50f8d5b545712f8b19d5ae62f5373980 🤔

This is also still happening in 2023.10.07

@Josiassejod1 can you share a verbose log please?

@bashonly
023-10-09T15:48:20.448Z pid=8 tid=gt8 WARN: Terrapin::ExitStatusError: Command '/app/vendor/gems/youtube-dl.rb-2023.10.07/vendor/bin/youtube-dl --no-color --no-progress --output '/data/downloads/e314f1e8-a309-4123-882c-093165efe1d8' --proxy 'https://groups-shader/:gdCXi72K4o4Ti6Semd34jRKAY@proxy.apify.com:8000' --format 'bestvideo[ext=mp4]+bestaudio[ext=m4a]/bestvideo+bestaudio' "https://www.youtube.com/watch?v=b-IY9ww3Xk0"' returned 1. Expected 0
Here is the command output: STDOUT:
[youtube] Extracting URL: https://www.youtube.com/watch?v=b-IY9ww3Xk0
[youtube] b-IY9ww3Xk0: Downloading webpage
STDERR:
ERROR: Unable to handle request: Unsupported proxy type: "https" (urllib)
2023-10-09T15:48:20.448Z pid=8 tid=gt8 WARN: /usr/local/bundle/gems/terrapin-0.6.0/lib/terrapin/command_line.rb:91:in run' /app/vendor/gems/youtube-dl.rb-2023.10.07/lib/youtube-dl/runner.rb:62:in run'
/app/vendor/gems/youtube-dl.rb-2023.10.07/lib/youtube-dl/video.rb:39:in download' /app/vendor/gems/youtube-dl.rb-2023.10.07/lib/youtube-dl/video.rb:15:in download'
/app/vendor/gems/youtube-dl.rb-2023.10.07/lib/youtube-dl.rb:25:in download' /app/app/models/file_kit/attachments/downloaders/youtube.rb:43:in rescue in download_youtube_file'
/app/app/models/file_kit/attachments/downloaders/youtube.rb:36:in download_youtube_file' /app/app/models/file_kit/attachments/downloaders/youtube.rb:25:in download_file'
/app/app/models/file_kit/attachments/downloaders/youtube.rb:17:in download!' /app/app/models/file_kit/attachments/downloaders/youtube.rb:9:in download!'
/app/app/models/file_kit/attachments/downloadable_sources.rb:21:in download_source!' /app/app/workers/file_kit/download_worker.rb:7:in perform'
So for context, I recently switched the binary of a rails gem using youtube-dp to ypt-dl so this is really low level abstraction

@Josiassejod1 This issue is about yt-dlp erroneously parsing proxies from the Windows registry. That is not at all what you are experiencing.
https proxies are not supported by yt-dlp and never have been. See #1890, https://github.com/ytdl-org/youtube-dl/issues/32549
Support for https proxies will be added when #3668 is merged

🫡  thanks for the heads up


Mark headers as SYSTEM includes in CMake

The include paths are set using:
    target_include_directories(pico_stdlib_headers INTERFACE include)

(e.g. in src/common/pico_stdlib/CMakeLists.txt)
As they're not marked as SYSTEM,  enabling warnings  (e.g. -Wall) will erroneously be tagged in the system headers.
pico-sdk/src/rp2040/hardware_regs/include/hardware/regs/addressmap.h:56:20: error: type qualifiers ignored on cast result type [-Werror=ignored-qualifiers]
   56 | #define TIMER_BASE 0x40054000

for example. If the headers are tagged SYSTEM then CMake uses -Isystem or equivalent which tells the compiler to suppress warnings coming from those includes.
A potential fix is:
$ git grep -l target_include_directories | xargs perl -pi -e 's/target_include_directories(.*)INTERFACE/target_include_directories$1SYSTEM INTERFACE/'

Modifying a simple example with target_compile_options(test PRIVATE -Wall -Wextra -Werror) shows up the improvement; though the numerous built-on-demand files (e.g. /home/mgodbolt/dev/personal/pico/pico-sdk/src/rp2_common/hardware_sync/sync.c:25) get built with these flags too and fail to compile. My cmake-fu is a bit weak at this point, as I can't see how test's PRIVATE flags are affecting things over in hardware_sync/sync.c but maybe someone stronger in this area can help.

If you look at test/kitchen_sink in the SDK, that builds everything with higher warning levels (and werror) than we do by default. That is the level of cleanliness we currently strive for.
This will get built if you build from pico-sdk directly, or you pass -DPICO_SDK_TESTS_ENABLED=1 to your build elsewhere.
Have to have a think about making these system.

Got it: thanks. I don't think I quite realised the SDK builds as part of a regular build (which is both ace but also means some compiler settings get picked up by it). Great job though; It Just Works™ :)

possibly worth seeing the state of things now (from a warnings perspective) and see if that helps any.

close in favor of #954


Plans For Normalization Support? Specifically URDNA2015 Normalization

JSON-LD libraries like https://github.com/piprate/json-gold support normalizing JSON-LD documents based on specs like URDNA2015, which is a requirement as part of for instance creating data integrity proofs.
Are there any plans to add normalization support to this library? SpruceID implement it into their identity core library here - https://github.com/spruceid/ssi/blob/main/src/urdna2015.rs

Hi, yes this is definitely something that I plan to have eventually. I don't have a timeline yet though, there are a lot of other things I want to finish first.

Yes I guess it is out of the scope of this crate.


feat: implement sequencer api with mysql

What this PR does:
add sequencer api component by mysql
Which issue(s) this PR fixes:
#489

Thanks!
To fix the CI error, you can make format and them git commit the changes

@GimmeCyy I answered you  below https://github.com/mosn/layotto/pull/509

@GimmeCyy 本地的锁似乎是没用的，layotto可能是多机部署。可以先交流下再写代码~

@GimmeCyy Thanks for your help!


Move the API to django-ninja

We started the implementation of https://qlued.alqor.io/api/v1/docs. However, it would be good to finish the transition and depreciate the old way.
This will require to implement and test:

[x] "str:backend_name/get_config/"
[x] "str:backend_name/post_job/"
[x] "str:backend_name/get_job_status/"
[x] "str:backend_name/get_job_result/"
[x] "str:backend_name/get_next_job_in_queue/"
[ ] "str:backend_name/get_user_jobs/"
[x] "/backends/"

We will not move get_next_job_in_queue. This one is outdated and we will leave it inside for legacy reasons.
However, this is really no point in adding it again as sqooler was changed to pull the information directly from the storage.

Decided to move  #34 to the next milestone. So we can remove it here.


Added project url output

Add a proper output to project init:
import layer
layer.init("sandbox")

# Your Layer project is here: https://app.layer.ai/layer/sandbox

I think you need to rebase or merge master


Text Alignment

All body texts/paragraphs should be left aligned and not centered.  Also applies for most headings/subheadings. Only bio pages (ones with names an portraits should be centered below the portrait)
Margins of all text and photos should have the same distance.
How to fix?

[x] Left align paragraphs (applies for all texts except name headings)
[x] Move bio name headings so that they are below the portrait rather than on top
[x] Align even margins

Before and During sections are done, all that's left is the After section which is after Alan is done with his audio issues. Marking as done cause it will be over soon.


fix: Type Registry required when printing Json

Type registry required to recognize "well-known types" and properly work with protobuf.Any type.

Codecov Report

Merging #108 (3a1c2a4) into master (52a2817) will decrease coverage by 13.30%.
The diff coverage is 56.25%.

@@              Coverage Diff              @@
##             master     #108       +/-   ##
=============================================
- Coverage     96.77%   83.47%   -13.31%
- Complexity      180      187        +7
=============================================
  Files            17       18        +1
  Lines           683      823      +140
  Branches         41       55       +14
=============================================
+ Hits            661      687       +26
- Misses           16      123      +107
- Partials          6       13        +7

Impacted Files
Coverage Δ

...vn/zalopay/benchmark/util/JMeterVariableUtils.java
22.72% <22.72%> (ø)

...main/java/vn/zalopay/benchmark/GRPCSamplerGui.java
72.81% <49.13%> (-27.19%)
:arrow_down:

...zalopay/benchmark/core/protobuf/ProtocInvoker.java
68.42% <54.90%> (-28.21%)
:arrow_down:

...ain/java/vn/zalopay/benchmark/core/ClientList.java
76.92% <68.75%> (-15.94%)
:arrow_down:

...n/java/vn/zalopay/benchmark/core/ClientCaller.java
94.78% <93.75%> (+0.33%)
:arrow_up:

...rc/main/java/vn/zalopay/benchmark/GRPCSampler.java
100.00% <100.00%> (ø)

...vn/zalopay/benchmark/core/grpc/ChannelFactory.java
100.00% <100.00%> (ø)

...lopay/benchmark/core/protobuf/ServiceResolver.java
89.09% <100.00%> (-0.20%)
:arrow_down:

... and 1 more

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 5306623...3a1c2a4. Read the comment docs.

@huynhminhtan PTAL. It's lgtm.