Adding the ability to create a non-distributed table (can be used for postgres extensions)

Change logs
Add: create table table_name DISTRIBUTED BY LOCAL
Creates a table that is queried only on the coordinator
Why are the changes needed?
Some postgres extensions (sr_plan or yezzey) needs to create local table. Before we do this by C-functions. Now we can do using SQL syntax
Does this PR introduce any user-facing change?
No
How was this patch tested?
It has regress test
Contributor's Checklist
Here are some reminders and checklists before/when submitting your pull request, please check them:

[ ] Make sure your Pull Request has a clear title and commit message. You can take git-commit template as a reference.
[ ] Sign the Contributor License Agreement as prompted for your first-time contribution(One-time setup).
[ ] Learn the coding contribution guide, including our code conventions, workflow and more.
[ ] List your communication in the GitHub Issues or Discussions (if has or needed).
[ ] Document changes.
[ ] Add tests for the change
[ ] Pass make installcheck
[ ] Pass make -C src/test installcheck-cbdb-parallel
[ ] Feel free to request cloudberrydb/dev team for review and approval when your PR is ready🥳

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Should add test for join with other distribution table.

Should add test for join with other distribution table.

Maybe, but main reason for having LOCAL relation is that they act exactly like pg_catalog relations (so, used only on coordinator node).

Should add test for join with other distribution table.

Maybe, but main reason for having LOCAL relation is that they act exactly like pg_catalog relations (so, used only on coordinator node).

for example, save-restore plan (sr_plan) extension uses relation to store query plans. Designed originally for postgres, this ext does work well in Greenplum (or its forks), because it tries to perform distributed query each time we access sr_plans table.
https://github.com/yezzey-gp/ygp/blob/YGP_6.27_STABLE/gpcontrib/sr_plan/sr_plan--1.1--1.2.sql#L5-L15

Squash commit message?

Hi, @visill , thank you for your interesting about cloudberry. Could you give more details about why we should change the current data model? Coordinator in cloudberry inherits from greenplum. It doesn't process data scan, and tries to move the workload to the segments, so the database  has the ability to scale to a large data processing system. Local table seems violates our design, we need more discussion about why it's necessary.
Cloudberry has many extensions that were backported from PostgreSQL. Generally, our principle is to adapt the extensions to our distributed database, not the other way around.

Cloudberry has many extensions that were backported from PostgreSQL. Generally, our principle is to adapt the extensions to our distributed database, not the other way around.

Absolutely right.
This is wrong way, you need to make your extensions compatible with CBDB kernel codes.
Greenplum/Cloudberry store catalog on master, other tables should be on segments in MPP mode.
Could you explain more why need create table on master?
Why your extensions need to store data on master, if it must be , it's a catalog.
If it needs to  work only on master, you need to change your extensions with Gp_role to do that.
A lot of extensions are modified to be compatible in MPP like that.

Could you explain more why need create table on master?

Because we need to store and access data on master, during planning phase. It is about sr_plan extension.

Why your extensions need to store data on master, if it must be , it's a catalog. If it needs to work only on master, you need to change your extensions with Gp_role to do that. A lot of extensions are modified to be compatible in MPP like that.

While this is generally true, it is very unhandy to do that. Today I bumped into problems with another extension - pg_hint_plan. This extension also uses table to store its planner 'hints'. This table should persist on master exclusively.
So, the ability to force Greenplum to create relation without any distribution policy would help with at least two extensions now.
And yes, we can play with Gp_role inside extension installation script and all functions/sql/other that access this relation. Whilst it is achievable with sr_plan,  it is too much work in other cases, especially for https://github.com/ossc-db/pg_hint_plan
We also can execute heap_create_with_catalog from extension install script, to create all needed relation as we want (with NULL gp_policy).
But specifying one proper option in CREATE TABLE sql is just much more simple.

If one dislikes SQL approach, we can do it another way: using GUC to control transformDistributedBy behaviour when no distrib clause specified

We also can execute heap_create_with_catalog from extension install script, to create all needed relation as we want (with NULL gp_policy

That is forbidden in GPDB, all tables should have a distribution policy , you are passing an invalid param with that function.

It is impossible to forbid something for extension. extension install script is executed under superuser

I'm not talking about the permissions.
Superuser doesn't mean volatile our MPP design is right.
It's terrible that tables are created without a distribution policy entry in MPP by manual to avoid necessary checks like distribution policy, but not through SQL.


Conflict with RTOS

Hi,
The library is very good but I saw it conflicts with the STM32 FreeRTOS. Please make a test. if I use the LCD functions inside an RTOS task, then the RTOS stops working.

Probably because the library uses HAL_Delay() which may interfere with the scheduler. Have you tried using osDelay() or vTaskDelay() instead?

Maybe, I have not tested it though, but I think it should be. I'll try

I replaced with HAL_Delay() with osDelay() in the header file, FreeRTOS still ended up in Hard Fault IRQ. Turns out I called  Lcd_string() before osKernelInitialize() and so osDelay() wasn't available to the lib for calling yet. So replacing HAL_Delay() with osDelay() works just fine as long as you call the LCD write method after kernel init.
Just putting it out here, so it might help someone.


feature enable memtable on sink node by default

Proposed changes
Set session variable enable_memtable_on_sink_node to true by default.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


wss secure websocket connection support

Does this lib support wss? I didnt find any mention of it...

As you already might have found out it's supported through netty. For detailled configuration you need to pass a Netty  SslContext object to the client/server. If you don't use one a default instance (which basically ignores certificates and trusts anyone) will be used.

Yeah, thanks, I just tried a bunch of junk libs before this, and got lazy to try figure out myself, so just wrote hoping to get fast response :)
anyway this lib works like charm, thanks for your work.
i wonder how people keep creating such crappy interfaces for those libs, its just enough to look at javascript implementations...

So, does this lib support wss? how to implement it?

@Matthias247 can you please mention how do it set SslContext wss ?
@ixsans have you found it ?


Add License Information

Found the actual license info in package.json and added LICENSE file and a note to README.md.
Please let me know if you feel like the license is inaccurate and I can include the proper license. A good resource is https://opensource.org/licenses.

This is a good thing!
First time I hear about the ISC license though 😸

Good idea, thanks for the contribution !


GameConfig-level zoom property has no effect in 3.12.0 (tilesets?)

Version

Phaser Version: v3.12.0

Operating system: Windows 10

Browser: N/A. (Verified in Chrome 69 and Firefox 62.0)

Description

When initializing a game like this:
var game = new Phaser.Game({
  // ...
  zoom: 3,
  // ...
});

I expect the game to be zoomed by a factor of 3x, when in reality it doesn't get zoomed at all. The examples below use tilesets.
Example Test Code

Working, v3.10.1: https://codepen.io/mikewesthad/pen/VdOLge (from this tutorial)
Not working, v3.12.0: https://codepen.io/nanodeath/pen/PdLqLp

Additional Information

I've verified it was also working in v3.11.0.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Same issue, while starting from the webpack template.
Only modification is the add of this zoom attribute and it don't have any effect.
The corresponding code in the CreateRenderer (line 79 & 80) is called, but the change is not applied to the canvas tag "style" attribute.

Here's a fix. Modify the boot function to look like this:
`     * @method Phaser.Game#boot
* @protected
* @fires Phaser.Game#boot
* @since 3.0.0
*/
boot: function ()
{
if (!PluginCache.hasCore('EventEmitter'))
{
console.warn('Core Phaser Plugins missing. Cannot start.');
return;
}
    this.isBooted = true;

    this.config.preBoot(this);

    CreateRenderer(this);

    if (false)
    {}

    DebugHeader(this);

    this.canvas.style.width = (this.config.width * this.config.zoom).toString() + 'px';
    this.canvas.style.height = (this.config.height * this.config.zoom).toString() + 'px';

    AddToDOM(this.canvas, this.config.parent);

    this.events.emit('boot');

    //  The Texture Manager has to wait on a couple of non-blocking events before it's fully ready.
    //  So it will emit this internal event when done:
    this.events.once('texturesready', this.texturesReady, this);
},`

Basically I'm forcing the width and height value of the canvas before it's added to the DOM by doing:
    this.canvas.style.width = (this.config.width * this.config.zoom).toString() + 'px';
    this.canvas.style.height = (this.config.height * this.config.zoom).toString() + 'px';

This property was not being used correctly (or at all in several cases) and was left over from a previous version. It has been removed in 3.16 as the Scale Manager will now handle this.

Since this is a backwards breaking change, shouldn't that be punted until 4.x? Alternatively, can you test to see if this now-legacy property is set and emit a warning?

No, this will be handled by the Scale Manager now, it shouldn't be applied directly in the renderer or the the canvas element any more.

As a user...this isn't really a great response. You're willing to break backwards compat, break tutorials and examples, and it's not even clear why (though from an API perspective, I don't especially care why). How many other flags are going to randomly break within minor version upgrades? Was this change added to a changelog or upgrade guide anywhere, at least?

Why would it have been added to a change log in advance of the change being made? It's not a breaking change in the slightest. It's just handled by an entirely different system now, that's all. Which will be fully documented when it's released, just like all changes are.

The zoom property was deactivated since 3.12 without notice.
For me, it is a breaking change. I have a game that in splits into multiple scenes, each one being a minigame like WarioWare. With the zoom property, I was able to scale the entire game in one property. Would I be able to do the same with the Scale Manager? I don't want to scale individually each object in each scene.

It wasn’t deactivated, please don’t be overly dramatic. It wasn’t actually touched at all. All zooming will be handled by the scale manager from 3.16 onwards, just like it was always meant to be.

I'm still confused about why this was closed and dismissed. A configuration option that was working in 3.12 doesn't function in 3.14. Is that not a bug? I'm not referring to mainline or 3.16.

@Kyberklemming to say something was "deactivated without notice" is a dramatic statement, because it implies it was done on purpose without mentioning it anywhere, neither of which actually happened.
I'm quite surprised it even worked. It was an un-documented setting, with no examples, that hadn't been tested since the beta versions.
You can restore its functionality in 3.12+ by dropping this anywhere in your code:
this.game.canvas.style.width = (this.game.config.width * this.game.config.zoom).toString() + 'px';
this.game.canvas.style.height = (this.game.config.height * this.game.config.zoom).toString() + 'px';

That way you don't need to edit the build.
Or, wait for 3.16, which will handle it properly via the Scale Manager.


Support for Home Mode in Synology Surveillance Station

This requires bumping py-synology, which the author has yet to do.

py-synology 0.3.0 has now been released.  Updated PR.

This PR seems to have gone stale. Closing it.


[ros2] ‘placeholders’ is not a namespace-name - missing include

ros2 branch, using gcc-7.1.1 (ArchLinux):
.../class_loader/include/class_loader/class_loader.h:128:26: error: ‘placeholders’ is not a namespace-name
     using namespace std::placeholders;

in include/class_loader/class_loader.h there's a missing include, adding it fixed the compilation error:
#include <functional>

It's possible that in previous versions of gcc functional was included in other libraries used here, but now it's not the case.

fixed in #51 thanks @mjbogusz for reporting it


Real image editing

This is great! Do you plant to implement support for real image editing?

Thanks for the suggestion! It should be straightforward to implement via methods like Null-Text-Inversion+ Prompt-to-Prompt, especially as I already have an implementation for P2P in my research codebase. Let me see if I can implement something quickly.

I implemented this based on ReNoise with SDXL Turbo as the backend to make things snappy. You can find a notebook here: https://github.com/CompVis/attribute-control/tree/main/notebooks/real_image_editing

This is great, thanks for taking the time to implement so quickly!


[material-ui][docs] Inform about deprecated TablePagination SelectProps usage

Closes https://github.com/mui/material-ui/issues/41062
Description
Replace deprecated SelectProps property on CustomPaginationActions with slotProps
Refs
Loom Video

@DiegoAndai This PR is ready for review


jenkins JobRunTable added

I have added one more table in Jenkins plugin capable of showing all the builds triggers, for a particular job.

@Abhay-soni-developer i think we are good to merge this now.

@benjdlambert @NishkarshRaj @jhaals @awanlin  i think we are ready to merge this branch, all the requested changes have been done too

any updates on this please drop your feedback if you want anything more to be done or please can we get this merge quickly
@benjdlambert @NishkarshRaj @jhaals @awanlin

https://github.com/backstage/backstage/actions/runs/6194714819/job/16818170902?pr=19881
One last bit needed: the API Report must be updated.

@benjdlambert @NishkarshRaj @jhaals @awanlin
The API docs test which was failing, now runs successfully.
The merge is all set to be merged.
Thanks @NishkarshRaj  for your consistent support.

Thank you for your feedback. After careful consideration, I have made some changes to the low-level design of the component, which now meets both our requirements and your suggestions. I am confident that this solution will be easy to maintain and will fit smoothly into the plugin's future roadmap.
@Rugvip  @NishkarshRaj  @jhaals  @awanlin please review

Any updates over this pull request .

where are we with this pull request?
@freben  @Rugvip

OK, will now resume work on the feedbacks
and will contribute to this

@benjdlambert @Rugvip
made changes according to the feedbacks , please check this and get this merge if its all good from your side too.

@benjdlambert @jhaals @awanlin @tudi2d @Rugvip
please pay some attention to this PR, because I think we are very close to closing this PR

After merging the other PR, this has conflicts.

@benjdlambert @jhaals @awanlin @tudi2d @Rugvip
I have worked on the last feedback too. are we good to move forward with this?

@Rugvip are ready to merge this now

you really just need to wait for the review like everyone else.


ability to change dns domain name

With custom domain name (not cluster.local), i`ve got errors and operator cannot connect to pods.
connection.go:54] FAILED Ping(http://***:***@chi-clickhouse-dev-replicas-only-0-0.dev.svc.cluster.local:8123/) dial tcp: lookup chi-clickhouse-dev-replicas-only-0-0.dev.svc.cluster.local on <IP_ADDRESS>:53: no such host

and more errors like that.
As far as i see, it`s part of const template at
https://github.com/Altinity/clickhouse-operator/blob/master/pkg/model/namer.go#L125
I guess, it`s possible to move dns domain into template as well. Or probably, some workaround exists?

ahh, found issue with same problem.

@f41gh7, could you please provide link to this similar issue?
Our clickhouse operator pod cannot scrape metrics from ch pods, because of name resolution, we use custom domain (instead of cluster.local). We cannot find issues about that, and cannot find any ability configure this behaviour :(
As you mentioned, we also found, that .cluster.local part is hardcoded...


Implement an API to fetch details on a particular report

User Story
As a report stream receiver/org, I would like to see the details of report that was sent to me
Description/Use Case
This new API will be used to render the header in this mockup
Risks/Impacts/Considerations

Will need to consult with designer as the fields are slightly hidden by the stickies

Dev Notes

The existing report API can likely be leveraged so that there is limited work here
See getDeliveryFacilities on the codebase

Acceptance Criteria

[ ] A new endpoint exists at /api/v1/organizations/{organization}/deliveries/{report_id} the details for a particular report

[ ] Report ID
[ ] Earliest item
[ ] Latest item
[ ] Expiration
[ ] Delivery method
[ ] Folder location
[ ] Download URL

Hey team! Please add your planning poker estimate with Zenhub @arnejduranovic @jack-h-wang @JessicaWNava @jimmyfagan @luis-pabon-tf @mkalish @victor-chaparro


Error after plugin add "OBJC_CLASS$_GADAdMobExtras"

When I install the plugin I got the following error building on iOS
Undefined symbols for architecture i386:
"OBJC_CLASS$_GADAdMobExtras", referenced from:
objc-class-ref in CDVAdMobPlugin.o
ld: symbol(s) not found for architecture i386
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Could you help me??
Regards

+1

Upgrade your xcode to newest version may resolve this error.
BTW, use the plugin pro version is recommended.
See: https://github.com/floatinghotpot/cordova-admob-pro

I figured out my issue was due to a problem with Milennial media admob extension plugin. It looks like it needs to be updated, but removing it fixed my build process.


Implement 'Set cells to empty string' command and add to Common Transformations menu

From #820
A "Set cells to empty string" function would replace the content of the cells in all current rows to an empty string "". This would work in a similar way to the "Blank out cells" command in the Common Transformations menu but would set the value of the cells to an empty string, rather than null

May require #1491 to be done first, as simply using the TextTransform operation here (as with the current 'Blank cells' function) results in the inconsistent behaviour described in #1491 (null is left as null rather than replaced with an empty string)


docs: add recipes, contribution guide and TOCs

docs: add recipes, contribution guide and TOCs
chore(package.json): mark package as no side effects
docs(CONTRIBUTING.md): update size of release diagram
docs(readme.md): add types summary to TOC
docs(readme.md): add treeshake support badge

Codecov Report

Merging #37 (a48c68b) into next (13c162b) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head a48c68b differs from pull request most recent head 3ef2b24. Consider uploading reports for the commit 3ef2b24 to get more accurate results

@@            Coverage Diff            @@
##              next       #37   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           23        23
  Lines          249       249
  Branches        13        13
=========================================
  Hits           249       249

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 a69b922...3ef2b24. Read the comment docs.

:tada: This PR is included in version 1.1.0-next.2 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Bump SeiDB version

Describe your changes and provide context

Bump seidb version to latest

Testing performed to validate your change

Launched local chain, verified fix

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

Project coverage is 61.60%. Comparing base (954bd21) to head (161a6fe).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1613      +/-   ##
==========================================
+ Coverage   61.46%   61.60%   +0.13%
==========================================
  Files         365      365
  Lines       26107    26107
==========================================
+ Hits        16047    16083      +36
+ Misses       8994     8954      -40
- Partials     1066     1070       +4

see 2 files with indirect coverage changes


Notifiers documentation is wrong

In the documentation for using a notifier looks like this:
notify_by DataDog do |datadog|
  datadog.on_success           = true
  datadog.on_warning           = true
  datadog.on_failure           = true

   datadog.api_key              = 'api_key'
end

however this results in an error like this:
[2014/10/24 22:32:46][error] NameError: uninitialized constant Backup::Config::DSL::DataDog

Instead you need to define your notifiers like this:
notify_by Notifier::DataDog do |datadog|
  datadog.on_success           = true
  datadog.on_warning           = true
  datadog.on_failure           = true

   datadog.api_key              = 'api_key'
end

This appears to be the case for all the extended notifiers documented here: http://meskyanichi.github.io/backup/v4/notifiers
We either need to update the docs to reflect the namespace requirement of update the notify_by to include the namespace.

Closed by #642


docs: use of the snapshotters config option and using soci with finch

Description of changes:
Adding documentation for using snapshotters with Finch

[x] I've reviewed the guidance in CONTRIBUTING.md

License Acceptance
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@CodeChanning Mdlint failed. Would you like to fix it?

@CodeChanning Mdlint failed. Would you like to fix it?

Yes, I can work on fixing it. @ningziwen

@CodeChanning Mdlint failed. Would you like to fix it?

Yes, I can work on fixing it. @ningziwen

@CodeChanning Thanks. There is one mdlint error left.


Barometer for android

Air pressure sensor support for Android.
Would be awesome if someone port IOS

Wow, this is really cool, lot's of new API surface like the magnetometer @NoaneDan added 👍
I am super excited to ship it, but this would be the first feature we would only have on one platform, that's why I wouldn't feel super sure about if we should add it or not 🤔 I have no iPhone to test it, so I wouldn't feel too sure about how to add it. Maybe I can borrow one the next days, let's see

I think I could implement the barometer for IOS sometime this week.
I'll look into it as soon as possible.

On IOS the CMAltimeter class has access to pressure data, but it works a bit different from the CMMotionManager used in the other sensors in the way that you cannot set the update interval for the data.
I can implement the Barometer though, but it will work different from the other sensors.

@NoaneDan Can you explain a bit more how it will work different? Do you mean the JS API or the implementation on the iOS side?

@DanielMSchmidt For the IOS barometer you won't be able to set the update interval (it's 1 second by default), so both the native and the JS code will be slightly different.

I think this is a fine trade-off for having a new sensor

Would be cool if we could get the iOS side here and document the missing update interval somewhere in our docs

Hey @josephbuchma @NoaneDan @ZachW628,
we have now a version (5.1.x) with support for this feature on both platforms.
iOS is heavily undertested, I would love to hear your feedback 👍
Thank you for your time!


Feat/wash down

Fixes #322
This PR

Adds the command wash down which cleans up running wasmCloud hosts and NATS servers launched by wash up
Adds an additional output file for NATS which includes the PID of the nats-server process
Adds another option to wash drain which lets users easily clean up their wash downloads directory
Bumps the host version to 0.58.2
Creates an alias for detached called detach because I kept typing it wrong and it made me angry
Simplifies some of the up code now that we don't need to output a complicated stop command

Waiting on #329 to merge only because that modifies the up test to not infinite hang


Issue with Kafka Pod Communication Across Clusters in Bitnami

Description:
I am facing an issue with the deployment of a Kafka pod in Cluster A and its communication with microservices in Cluster B using a LoadBalancer (LB) defined for different brokers. Here are the details of the problem:
Cluster Configuration:
Cluster A: Contains the Kafka pod.
Cluster B: Contains various microservices that need to communicate with the Kafka pod in Cluster A.
Issue Description:
In Cluster B, we have defined the same Kafka LB for different brokers, and it works perfectly fine when microservices within Cluster A communicate with the Kafka pod.
Problematic Behavior:
The issue arises when microservices in Cluster B try to communicate with the Kafka pod in Cluster A.
We observe the following warning message in the Kafka logs:
2023-10-03 05:24:42.916 WARN 9 --- [| adminclient-1] org.apache.kafka.clients.NetworkClient : [AdminClient clientId=adminclient-1] Error connecting to node kafka-2.kafka-headless.kafka-pod.svc.cluster.local:9092 (id: 2 rack: null)

java.io.IOException: Can't resolve address: kafka-2.kafka-headless.kafka-pod.svc.cluster.local:9092
        at org.apache.kafka.common.network.Selector.doConnect(Selector.java:235) ~[classes!/:0.0.1-SNAPSHOT]
        at org.apache.kafka.common.network.Selector.connect(Selector.java:214) ~[classes!/:0.0.1-SNAPSHOT]
        at org.apache.kafka.clients.NetworkClient.initiateConnect(NetworkClient.java:864) [classes!/:0.0.1-SNAPSHOT]
        at org.apache.kafka.clients.NetworkClient.ready(NetworkClient.java:265) [classes!/:0.0.1-SNAPSHOT]
        at org.apache.kafka.clients.admin.KafkaAdminClient$AdminClientRunnable.sendEligibleCalls(KafkaAdminClient.java:889) [classes!/:0.0.1-SNAPSHOT]
        at org.apache.kafka.clients.admin.KafkaAdminClient$AdminClientRunnable.run(KafkaAdminClient.java:1104) [classes!/:0.0.1-SNAPSHOT]
        at java.lang.Thread.run(Thread.java:748) [na:1.8.0_191]
Caused by: java.nio.channels.UnresolvedAddressException: null
        at sun.nio.ch.Net.checkAddress(Net.java:101) ~[na:1.8.0_191]
        at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:622) ~[na:1.8.0_191]
        at org.apache.kafka.common.network.Selector.doConnect(Selector.java:233) ~[classes!/:0.0.1-SNAPSHOT]
        ... 6 common frames omitted

Problem Details:
The error message indicates that the Kafka pod in Cluster A is unable to resolve the address kafka-2.kafka-headless.kafka-pod.svc.cluster.local:9092 when attempting to connect from Cluster B.
This issue is causing communication problems between the microservices in Cluster B and the Kafka pod in Cluster A.
Expected Outcome:
We expect the Kafka pod in Cluster A to successfully resolve the address and establish communication with microservices in Cluster B via the defined LoadBalancer.

Hello @migruiz4 could you please assist me on it

I apologize for my mistake, @OneCricketeer. It appears that I posted the previous message on the wrong chat or thread.

Feel free to close this issue


adding evse-2 to model repo

Thank you for contributing to the Azure IoT Plug and Play Models repository
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact<EMAIL_ADDRESS>with any additional questions or comments.
The repository pipeline will ensure minimum validation of incoming DTDL models.

PR validation steps are described in the tools Wiki.
The same validation can be run locally via the dmr-client CLI.

Requested info template for model(s) submission
When submitting models to the repository we ask that you provide as much of the following meta information around your models and related devices as possible. This info will be used to improve Plug and Play.
:star2: Please replace the markdown comment examples with your own values.
Company Info

IoT Plug and Play Device Info

Model Submission Goals

Code Owners & Reserved Names

Hi Ricardo,
Thx for feedback. I am not too sure what you are requesting but... the display name field that the IoT Central App is listing is defined in the json file,  ie see line 204:
[cid:6e0e05ca-eac9-4129-9490-a705acc35887]
Does that answer your question?
Many thx
Mark

From: Ricardo Minguez (Rido) @.>
Sent: 30 July 2021 17:52
To: Azure/iot-plugandplay-models @.>
Cc: Mark Swinburn @.>; Mention @.>
Subject: Re: [Azure/iot-plugandplay-models] adding evse-2 to model repo (#341)
@rido-min commented on this pull request.
@Swinny619https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSwinny619&data=04|01||1213af1475ba4fc9a63908d9537a6754|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637632607445998824|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=wWK0YoSfp2fgmDjVkCi1RGSWez4SVx%2FpjWGePcHT6o8%3D&reserved=0 The interfaces LGTM although they are missing the displayName field. Is this intentional? This field will be used by IoT Solutions like IoT Central to display the name. Please consider adding it (not mandatory)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fiot-plugandplay-models%2Fpull%2F341%23pullrequestreview-719292790&data=04|01||1213af1475ba4fc9a63908d9537a6754|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637632607446008769|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=weCy%2FYkgZubliO7qItmVURZb0AxII8fEfSAlTJqCrG4%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAUVUDB2TQU5NXQYVF4MXYZ3T2LKENANCNFSM5BIOXQIA&data=04|01||1213af1475ba4fc9a63908d9537a6754|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637632607446008769|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=OrX%2FZd9tfcabx5XiyGVbdVwsVvFof%2B0C41IMz7Ye2ZA%3D&reserved=0.


doc(README): minor corrections

@rultor good to merge.

@rultor good to merge.

@rafamizes OK, I'll try to merge now. You can check the progress of the merge here

@rultor good to merge.

@rafamizes Done! FYI, the full log is here (took me 3min)

Merged by Rultor.


BUG: java.util.logging.Logger

Summary:
java.lang.ClassNotFoundException is thrown for java.util.logging.Logger if Logger is used in packaged application. This behavior does not occur with gradle run without packaging
Environment:
OS: Windows 10 Pro 1901 18363.900
Steps to Reproduce:

IntelliJ -> create new projekt -> Kotlin -> Java Compose for Desktop
Add TargetFormat.AppImage in build.gradle.kt
Add Remote JVM Debug running configuration to IntelliJ
Enable remote debugging in the compose app with

compose.desktop {
    application {
        mainClass = "MainKt"
        nativeDistributions {
            targetFormats(TargetFormat.Dmg, TargetFormat.Msi, TargetFormat.Deb, TargetFormat.AppImage)

            jvmArgs += "-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005"

gradle packageAppImage
run packaged app and set breakpoint in the button's onClick callback
start debugging the Remote JVM Debugging configuration
press the button
evaluate java.util.logging.Logger("foo") in IntelliJ's debugging panel
see the thrown ClassNotFoundException

Expected Results:
I would expect to receive a Logger object, as it would happen before packaging (with only gradle run)
Actual Results:
ClassNotFoundException is thrown, which crashes the app outside of this debugging evaluation call
Notes:
I found this bug when I tried to use squareup's okio library in a compose project (https://square.github.io/okio/)

Can you please provide a minimal repro so we can debug locally?

I created a sample project on my private profile: https://github.com/mitch3ls/jb-compose-issue-377-demo
All the necessary steps are described in main.kt

I tried the solution from #381 with both modules("java.util.logging") and modules("java.util"), but I get jlink failed with: Error: Module java.util.logging not found for both cases during gradle packageAppImage

https://docs.oracle.com/javase/9/docs/api/module-overview-frame.html module name is java.logging.

Thank you so much, that worked! It would be great if that could be incorporated into the documentation somehow 👍

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Adding an import causes type inference to fail

Note: I will soon be submitting code to work around this bug, so to reproduce it check out c890c487fe92fb96a2f56b20d7d00c58f571406d.
In IntelliJ, edit the file pkg/front_end/lib/src/fasta/kernel/frontend_accessors.dart and add the following import at the top:
import 'package:front_end/src/fasta/kernel/fasta_accessors.dart' show BuilderHelper;

This produces a large number of "Invalid override" errors.  It's not obvious why the presence of this import would have any effect--my best guess is that it's changing the behavior of the summary linker by putting frontend_accessors.dart and fasta_accessors.dart in the same library cycle.

@scheglov would you mind having a look at this?  I don't want to distract myself from collaborating with folks in Aarhus.

Absolutely.
Most probably I will able to fix this tomorrow.

I can reproduce it now in a test case.
a.dart
import 'b.dart';
class A1 {
  int _foo() => 1;
}
class A2 extends A1 {
  _foo() => 2;
}

b.dart
import 'a.dart';
class B extends A2 {}

When we link b.dart, we perform instance type inference for B, which causes us to perform type inference for A2. But the instance of InstanceMemberInferrer uses the instance of InheritanceManager that is configured with the b.dart library. So, we cannot inference the return type of A2._foo, but we still mark the A2 element as hasBeenInferred.
It seems to me that we should not lock InstanceMemberInferrer to use a single InheritanceManager instance. We probably should get these instances from ClassElement instances, from their LibraryElement, so from LibraryElementInBuildUnit which know their InheritanceManager instances.

Aha, that explains it!  Thanks for tracking it down.
I like your proposed approach for solving it--let me know if there's anything I can do to help.

The InheritanceManager holds on to a lot of memory. It isn't clear to me that we want to the element model to hold on to them, despite the fact that the element model is more ephemeral than it used to be.

The CL is out for review.
Not so brave as I hoped, just using a provider instead of an instance.
Not the 'inheritanceManager' accessor on LibraryElement.

FWIW, preliminary measurements show that during analysis of my workspace (analyzer, analysis_server, front_end, dart2js, kernel) we create about 7300 instances of InheritanceManager with total size of about 33 MiB (this excludes size of Element instances). This is about 5 KiB per instance in average.

https://github.com/dart-lang/sdk/commit/ddf683c73290e32fc846aa28c3c0b211540a3624

https://github.com/dart-lang/sdk/commit/ddf683c73290e32fc846aa28c3c0b211540a3624


 Does it have to be activated somehow?

Hi
You might not be the idiot, it might very well be me. I've actually never used a theme with Highcharts, either via highcharts-rails or just plain Highcharts.
From what I can see, you should just need to include the theme you want in your javascript file, for example //= require highcharts/themes/dark-green and it should automatically apply the dark-green theme to all your charts.


Github Enterprise Option

Addressing #100
Setting github: {apiRoot:''} will allow you to use Github Enterprise. Not setting it will default to github.com.

Thanks for the work. Need to test this somehow but I don't have GH
Enterprise available here. So it might be a bit tricky.
Could you please add some unit tests for the default GH URL? That would be
fantastic.
On Mon, Feb 2, 2015, 6:48 PM Scott<EMAIL_ADDRESS>wrote:

Addressing #100 https://github.com/geddski/grunt-release/issues/100
Setting github: {apiRoot:''} will allow you to use Github Enterprise. Not
setting it will default to github.com.
You can view, comment on, or merge this pull request online at:
https://github.com/geddski/grunt-release/pull/103
Commit Summary

Github Enterprise Option

File Changes

M README.md
https://github.com/geddski/grunt-release/pull/103/files#diff-0 (1)
M tasks/grunt-release.js
https://github.com/geddski/grunt-release/pull/103/files#diff-1 (6)

Patch Links:

https://github.com/geddski/grunt-release/pull/103.patch
https://github.com/geddski/grunt-release/pull/103.diff

—
Reply to this email directly or view it on GitHub
https://github.com/geddski/grunt-release/pull/103.

I looked at the unit tests, but wanted to get the code out before I got too distracted. I will circle back around to those when I sit back down to code for awhile.

Let's wait a couple of more days before merging. Maybe you will find the time :)
Thanks for your work so far!

is this really needed, i am currently using this on repos that exist in github enterprise

We're also running this on GH Enterprise without any problems

It wouldn't work if you had the github option set as it tries to post using the public github API, if you don't use that option then it would work.

@agubler Can you explain a little bit more? All this PR should do is to allow you to override the default, if you do not specify an apiRoot then the expectation is that it will use public github as it currently does (did?) Unless something changed that I am unaware of.
I have been stuck on the unit tests for a bit - I would need to inspect the post and verify that the urls are as expected but I am not really that familiar with the assertions yet.

Thank you for the work. I am pretty sure you need to change the URL for your GH Enterprise server. The option is now present. Can you please test this again? I don't have access to a GH Enterprise installation.