Is it possible to use this client with rancher v2.6.0?

I trying to add a cluster repo, but I found it at the v1 endpoint and I cannot figure out how to use the client to add the repo

Cluster Repos are a CRD in the "downstream" cluster You should use the regular Kubernetes API or a client for it to interact with resources in downstream clusters.

@vincent99 Does that mean that this library is going to be deprecated in the near future? Because if I have to use native tools, I don't understand what good is this client for then? I have spent 2 years creating an application stack using this library as the base for deploying and interacting with downstream clusters and I would hate to replace all of that hard work
PS: I apologize if I sound rude.

This library hasn't really changed in years, because it does everything by reading schemas from the endpoint and knows absolutely nothing about Rancher or Kubernetes.  It contains no code specific to them, and exists basically unchanged since before Rancher or Kubernetes existed (we open-sourced the implementations at a previous company).  So that part isn't going anywhere.
Nor is what exists in /v3 today for the foreseeable future.  That is still the right place to manage Rancher-specific global-level resources and things that "live" in the management/"local" resources.
But we are no longer creating new public APIs for downstream clusters that present k8s resources in the format this client uses (exposed in /v3).
For downstream has always been primarily for the UI to consume, supported only a small subset of the hundreds of types you might have in the cluster (the ones the UI shows), required using projects and only namespaces in one, etc.
The newer explorer UI does not use that for showing you the resources in the selected cluster.  It supports all resource types, any  namespace regardless of whether it's in a project, etc.  So we're not adding newer features to the older API.
The K8s API is not really _that _ different and there are lots of clients, so you'll probably find it wouldn't be that much work to start using for new types.
Or if you REALLY want there is actually a new API (at /k8s/clusters/(id)/v1) that the new UI uses and that does still use the spec this client implements, and you could find clusterrepos in there.  It is a mostly mechanical translation of k8s to that format, with a few features that makes building the UI easier/faster/possible.  But we consider this an internal implementation detail and it is explicitly not documented and could have breaking changes in any release.

@vincent99 Well, thanks for the info. I have made all the changes I needed already with this library to make it all work with v2.6.0. The test case deploying monitoring v2 at https://github.com/rancher/rancher/blob/f7516246e8f75178c8e2a4827eb0cd25a600dcd8/tests/validation/tests/v1_api/test_monitoring_v2.py#L21 helped me to understand how it works.
We will migrate our codebase away from this library in the future for the downstream clusters.


Data Science with Python : Cheatsheet on Open CV Library

Description 📜
This issue deals with the documentation for cheat-sheet for matplotlib library of Python.
The readme.md will contain the codes and a .ipynb file will contains all the demonstration of all the codes.
Fixes #7063

Type of change 📝

Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

Datascience with Python

Checklist ✅

I follow Contributing Guidelines & Code of conduct of this project.
I have performed a self-review of my own code or work.
I have commented my code, particularly in hard-to-understand areas.
My changes generates no new warnings.
I'm GWOC'21 contributor

@prathimacode-hub
Please review my PR

@prathimacode-hub Please review my PR again
Thanks


rf_ files viewing problem

Hi, I was trying to view the rf_ files using the phpnow-1.5.6, but failed and got this message.
"Fatal error: Class 'mysqli' not found in E:\PHPnow\htdocs\rf_list.php on line 34"
"Fatal error: Class 'mysqli' not found in E:\PHPnow\htdocs\rf_graph.php on line 21"
"Fatal error: Class 'mysqli' not found in E:\PHPnow\htdocs\rf_status.php on line 27"
seems Class 'mysqli' is missing? How can I fix it? Thank you

Make sure you have mysqli installed with your PHP installation. That should solve the issue, what operating system are you using?

It turns out to be the php configuration problem.  and I changed the "extension=php_mysqli.dll" expression.
However, here comes another error,
"
Warning: mysqli::mysqli() [mysqli.mysqli]: (HY000/2005): Unknown MySQL server host 'xxxx' (11001) in D:\PHPnow\htdocs\rf_graph.php on line 21
Connection Failed: Unknown MySQL server host 'xxxx' (11001)
"
In the original rf_graph file, line 15 to line 21 are:
`	<?php
$servername = "xxxx";
$username = "xxxx";
$password = "xxxx";
$dbname = "xxxx";
$conn = new mysqli($servername, $username, $password, $dbname);

`
Should I replace "xxxx" with specific contents?

And I using in a Win10 system.

You'll need to set up a MySQL server on your machine and use the database schema from the REFIT-MYSQL.sql file to create the empty database structure.
All of the variables with "xxxx" will be specific to the MySQL server you set up.

Thanks a lot. It is my first time using PHP and SQL.
I have created the database 'refit' and sourced the REFIT-MYSQL.sql to 'D:/PHPnow/Mysql/data/refit';
changed 'xxxx’ to the following setting
$servername = "localhost";
 $username = "root";
 $password = "123456";
 $dbname = "refit";

However, when I open rf_ files using "http://<IP_ADDRESS>/rf_graph.php", I got this information:
** for rf_graph
Notice: Undefined index: houseID in D:\PHPnow\htdocs\rf_graph.php on line 53
Notice: Undefined variable: data_Set in D:\PHPnow\htdocs\rf_graph.php on line 36
Notice: Undefined variable: data_Set_Label in D:\PHPnow\htdocs\rf_graph.php on line 50
Check Sensors Check Scripts
Power
Notice: Undefined index: houseID in D:\PHPnow\htdocs\rf_graph.php on line 105
Nothing Selected	, Aggregate
** for rf_list
0 results (It's all gone wrong)
** for rf_status
0 results (It's all gone wrong)

You haven't populated the database with values hence the nothing selected issue, this repository is to give an idea of how the REFIT dataset was created. It's not the way to access the data, the data is available at https://pureportal.strath.ac.uk/en/datasets/refit-electrical-load-measurements-cleaned


#166 Schedule task every X hours from a date in the past

Also fix the tests that didn't pass near year time change day (Mar 25, for example)

@naduda hey, this repo is no longer maintained (per the note in the readme) - we have a maintained fork over at https://github.com/go-co-op/gocron and recently added support for this exact use! https://github.com/go-co-op/gocron/issues/106


[OFFICIAL/TV] @ AEW WrestleDream 2024 LiVe StreamS Free On TV Channel 13 OCT 2024

)HERE'S! WAY TO WATCH AEW WrestleDream 2024 LIVE STREAMS ON TV CHANNEL
AEW WrestleDream 2024 live stream: How to watch wrestling PPV – start time, card, preview. It's time to watch AEW WrestleDream 2024 as this latest All Elite Wrestling PPV follows in the footsteps of last month's stellar All Out. Having retained the AEW World Championship, Bryan Danielson once again headlines a stacked card, this time as he defends his gold against former Blackpool Combat Club cohort Jon Moxley.
🔴🌍📺📱👉GO LIVE==►► CLICK HERE TO STREAMING
🔴🌍📺📱👉STREAMING==►► CLICK HERE TO WATCH LIVE
🔴🌍📺📱👉GO LIVE==►► CLICK HERE TO STREAMING
🔴🌍📺📱👉STREAMING==►► CLICK HERE TO WATCH LIVE
While Danielson vs. Moxley is the clear headline attraction of AEW WrestleDream 2024, there are plenty of other great match-ups dotted across the card, which takes place on Saturday live from Washington's Tacoma Dome.
Given the history of AEW delivering big when it comes to Pay-Per-View, and in the aftermatch of the excellent duo of All In and All Out, anticipation is high for another great show with WrestleDream.
AEW WrestleDream 2024 start time
Date: Saturday, October 12
Time: The main broadcast starts at 8 p.m. ET / 5 p.m. PT and Oct 13 at 1 a.m. BST / 11 a.m. AEDT.
Watch in the U.S.: PPV / YouTube / Triller TV
Elsewhere: DAZN / PPV
Watch anywhere
Given the history of AEW delivering big when it comes to Pay-Per-View, and in the aftermatch of the excellent duo of All In and All Out, anticipation is high for another great show with WrestleDream.
AEW WrestleDream 2024 start time
Date: Saturday, October 12
Time: The main broadcast starts at 8 p.m. ET / 5 p.m. PT and Oct 13 at 1 a.m. BST / 11 a.m. AEDT.
Watch in the U.S.: PPV / YouTube / Triller TV
Elsewhere: DAZN / PPV
Watch anywhere
Given the history of AEW delivering big when it comes to Pay-Per-View, and in the aftermatch of the excellent duo of All In and All Out, anticipation is high for another great show with WrestleDream.
AEW WrestleDream 2024 start time
Date: Saturday, October 12
Time: The main broadcast starts at 8 p.m. ET / 5 p.m. PT and Oct 13 at 1 a.m. BST / 11 a.m. AEDT.
Watch in the U.S.: PPV / YouTube / Triller TV
Elsewhere: DAZN / PPV
Watch anywhere
Given the history of AEW delivering big when it comes to Pay-Per-View, and in the aftermatch of the excellent duo of All In and All Out, anticipation is high for another great show with WrestleDream.
AEW WrestleDream 2024 start time
Date: Saturday, October 12
Time: The main broadcast starts at 8 p.m. ET / 5 p.m. PT and Oct 13 at 1 a.m. BST / 11 a.m. AEDT.
Watch in the U.S.: PPV / YouTube / Triller TV
Elsewhere: DAZN / PPV
Watch anywhere

Closed due to irrelevant content.


How to implement annotation at runtime via reflection in Java

Proposed title of article
HOW TO IMPLIMENT ANNOTATION AT RUNTIME VIA REFLECTION IN JAVA
Proposed article introduction
The Reflection API is part of the standard Java API Library which enable us to explore both the intrinsic nature of the class and intensities without using any explicit new operator at runtime.
This tutorial guides on how to get stated with field's annotation at runtime. we will us reflection API to define class and method information about annotation that are attached to class and methods. We will discus some step by step on how to implement annotation at runtime via reflection.
Key takeaways
By the end of this tutorial the learner will be able to:

Defines reflection on annotation
Check fields that are annotated at a specific time through some codes.
Modify application using reflection.

References
N/A

How does this topic differ from existing documentation such as http://tutorials.jenkov.com/java-reflection/annotations.html?

The article has just tackle some types of annotation and there use. In this tutorial, I will show how to obtain annotations of class and methods using reflection via reflection API. Besides we will also discuss how to get an information and read information about annotation that are attached to the class used and methods.

Any updates @WanjaMIKE ???

Good afternoon and thank you for submitting your topic to the EngEd program.
After some careful consideration it struck us that this topic may be a bit over saturated throughout other blog sites and official documentations. We're more interested in original, practitioner-focused content that takes a deeper dive into programming-centric concepts. Please feel free to suggest an alternate topic to explore. 🚀
We typically refrain from publishing content that is covered widely on the net or other blogs. We're more interested in original, practitioner-focused content that takes a deeper dive into programming-centric concepts.
But in order to approve the topic it has to serve value to the larger developer community at large. Please feel free to suggest an alternate topic to explore. 🚀


Deactivating code completion leads to loss of menu option and outline explorer

Issue Report Checklist

[x] Searched the issues page for similar reports
[x] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[x] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[x] Could not reproduce inside jupyter qtconsole (if console-related)
[x] Tried basic troubleshooting (if a bug/error)

[x] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[x] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
After a fresh os/anaconda/spyder reinstall I started spyder and deactivated code completion (central option in the menu, forgot how it's called and I can). then, upon reloading spyder, this box was still unchecked, but ALL other code completing and linting options were checked and active. checking and unchecking the central code completion option again inactivated all code completion options. another spyder restart later, the menu section "code completion" is gone, and so is the outline pane - no option/checkbox to bring it back
potentiall related to this? https://github.com/spyder-ide/spyder/issues/15631
What steps reproduce the problem?
as described above
What is the expected output? What do you see instead?
as described above
Paste Traceback/Error Below (if applicable)

    > spyder
    Pruned plugin: outline_explorer
    Missing requirement: completions
    Restart plugins pruning by REQUIRES check

Versions

Spyder version:  spyder                    5.0.5            py37haa95532_2
Python version: python                    3.7.10               h6244533_0
Qt version:  qt                        5.9.7            vc14h73c81de_0
PyQt version: pyqt                      5.9.2            py37h6538335_2
Operating System name/version: win 10

Dependencies

PASTE DEPENDENCIES HERE

Hi @mluerig,
This is a known bug and we are working towards fixing it for our next version, Spyder 5.1.0. If the configuration page is not present in preferences, then code completion should be off. In the case you want to bring it back, you'll need to reset spyder doing spyder --reset, it is the only way for now.
Thanks for reporting!


Added documentation about using asynchronous APIs in a C# native module

The current documentation about authoring native modules in C# covers only creating methods which leverage synchronous APIs. However, most of the APIs in the Universal Windows Platform are implemented using the asynchronous pattern. However, due to the way React Native for Windows works, you can't create such methods using the standard approach, but you must use a few helpers provided by the platform. I've updated the documentation to include these information.

@stmoy can you review? I believe Native Modules are still your area of expertise :)

@jonthysell as well. Overall this looks good and reasonable to me!

@kikisaints and @stmoy I probably have made a mistake 😐 I submitted a Pull Request to upgrade the TodosFeed sample to React Native 0.62 but, since this PR was still open, my work got added to this one instead creating a new PR. Sorry for this!

@kikisaints and @stmoy I probably have made a mistake 😐 I submitted a Pull Request to upgrade the TodosFeed sample to React Native 0.62 but, since this PR was still open, my work got added to this one instead creating a new PR. Sorry for this!

@qmatteoq  - what are the next steps on this PR?

Hello @harinikmsft I have some work to do because the PR has been stale for too long and, since the master always needs to reflect the most recent bits, it has been exceeded by #208 since 0.63 has brought direct support for Task.
I'm on vacation this week, but next week I will review the latest changes and include only the update for the TodosFeed demo.

@qmatteoq do you need anything/are you blocked on anything to move this forward?

@qmatteoq do you need anything/are you blocked on anything to move this forward?

Only by time :-) I'm swamped with Ignite this week, this item is in my "To-Do" list for next week. Thanks for your patience!

Looks like samples/rssreader/msbuild.binlog  snuck through, can you remove it? :)

I apologize @asklar, I did some changes to upgrade rssreader to 0.62 but I forgot that this PR was still open.
I'm going to close it and submit a new one, since this PR contains too many moving parts.
Thanks!


check something!

@ruinmessi
hey!
Can you give me your 2015test-dev result (a .json file )  which you submitted to server，I just  want to check my results. thanks ，my<EMAIL_ADDRESS>thanks!

Which model would you want? I have to run it again by my own.

thanks，i have solved it！


Fixes #94 : Look for php in C:\ rather than in the current directory.

Modified cheat.bat to look for PHP in the C:\ Drive and use the one in there as well.
Fixes #94

@xPaw

No. The batch is specifically to download it into a local sub folder.
And you haven't modified the PS script, so this won't work.

@xPaw. But no one installs PHP in a local sub folder. It should first check if it is installed in C:\

You don't need to install anything yourself, it does it automatically for you.


Move off of Longhorn

Many people probably saw this coming. I will be trying New Solution next.

[ ] Backup Media Namespace
[ ] Disable all helm charts that require Longhorn
[ ] Verify all deployments which require Longhorn are un-deployed
[ ] Wipe the Longhorn drives on the storage nodes
[ ] Deploy New Solution with using the storage node labels
[ ] Verify New Solution deployment
[ ] Re-enable disabled deployments

Another instance today of two containers as not mounting as part of a multiple chart upgrade. Killing the failed containers and allowing them to rebuild seems to have fixed the issue for now.

I ended up re-building a single node to resolve a no-mount scenario in the past week. No issues since then, but still another worrying issue. Still not 100% on moving yet due to the time investment in performing the move and setup of new infrastructure.

Another instance of mount failed: exit status 32 when upgrading a helm chart, pod refuses to mount the pvc. Restarting node helped for the initial pod causing issues, then caused issues for other pods trying to mount storage.

Completely on rook-ceph now, longhorn is no longer in the cluster.


Various migration cleanups

These are various places where we are accessing models incorrectly,
which makes having the specs run against a dummy app impossible.
@bdunne Please review.
cc @chrisarcand @carbonin

Some notes:

I am preferring ArRegion.anonymous_class_with_ar_region over ApplicationRecord.  I'd rather allow hitting the ArRegion directly than the thing that is including ArRegion as it removes a level of indirection, and thus coupling.
I can completely avoid FactoryGirl in cases where they were listed by just faking out ids.

@bdunne @chrisarcand Updated.  The stub_const also solves the test failures, so that's another + for that approach.


Use JSON.MGET for repo.fetch multiple ids

Currently repo.fetch(ids) translates to awaiting multiple JSON.GET. Performance might be improved by replacing JSON.GET with JSON.MGET.
https://github.com/redis/redis-om-node/blob/6f08d0292844e41831c8e6b6e61a940432f7db1e/lib/repository/repository.ts#L355-L363

That's a good callout. I'm working on Redis OM 0.5.0 right now and will add this to my backlog.


feat: redis dedup backend

hi ! im attempting to implement #2004
im not done yet (i need to add the configuration switch case and look at other things), but i thought i would push up some progress, and maybe if this is an awful idea or i am doing something very bad code wise i should know.
it passes tests using an embedded redis, so that is good
What does this PR do / Why do we need it:
adds a redis backend for the dedup cache
Testing done on this change:
i've copied the test from bolt and ran it with embedded redis.
Automation added to e2e:
not any. should i add a test that spins up redis docker image?
Will this break upgrades or downgrades?
it will break downgrades if the user downgrades to a version that no longer supports redis and they are using redis
Does this PR introduce any user-facing change?:

adds redis as backend for dedup cache

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

I would love to see Redis support added. Are you still working on this?

I would love to see Redis support added. Are you still working on this?

hi yes, I plan to see this pr to completion

@elee1766
There is a user requirement for this feature.
https://github.com/project-zot/zot/discussions/2365
We can take over this PR.

Is this still being worked on?


Update charging_station preset with socket information

Currently the charging station preset misses the most important part. There is no information on the socket type (socket:<type>) and the charging output (socket:<type>:output). The full documentation can be found here: https://wiki.openstreetmap.org/wiki/Tag:amenity%3Dcharging_station
I looked into adding it myself with a pull request, but the conditional tags make it harder. Is there currently a way to add a more advanced preset for this? The socket type could be a drop-down and the capacity would be conditional on the socket type.

@danielsjf So this came up before in #6879 and was closed as essentially too complex. These tags use some nonstandard patterns that are different from almost everything else in OSM, meaning iD can't support them out-of-the-box. People can invent whatever tags they want in OSM, but that doesn't mean editors can always support them…

@quincylvania, thanks for reopening. Just socket:type2 (one of the popular ones) has already 14k tags and this will only increase. Even though I agree that the choice of the tagging scheme was poor, I don't see it changing anytime soon.
Replying in this thread since the other one is closed:

I agree with @bhousel in https://github.com/openstreetmap/iD/pull/6879#issuecomment-547607403 that current isn't very useful, but the output certainly is. I would even dare to say that apart from the socket type this is one of the most important values. The comparison with gasoline pumps doesn't hold since there the difference might be 2 or 4 minutes while for EVs this means a couple of hours vs a full night.
Apart from this, I think this way of tagging has grown from many different charging options that existed. One charging station can support multiple socket types. Each socket type can have its own max output and the overall charging station can have a separate max output that is more constraining than each individually (https://upload.wikimedia.org/wikipedia/commons/f/f6/Charging_station_socks.jpg). A new standard will therefore always be more complex than just an enumeration of the socket types.

If there is anything that I can do to help facilitate this issue, just let me know.


Use this package together with Flask

I have developed OCPP client and server with this awesome library. I wanted to add GUI to the client and server. I intend to use React as frontend and Flask as backend for the application.
How to integrate OCPP python client with Flask framework. As the OCPP has its event loop running continuously blocking the flask code. Please help.

Thanks for your compliment.
Unfortunately Flask and this package don't mix very well because Flask is sync and this package is async.
But I experimented a bit with using this package together with Quart. Quart is a async web framework with a very similar API to Flask.
There is some very ugly code over on my personal profile.
Note that it probably doesn't work anymore with the current release of the ocpp package, but I think you can learn from the approach.

Hey @id4github thanks for your interest. As Auke said, flask doesnt blend so well, but maybe aiohttp can be an option. They have also an api that can mimic flask operations... maybe you can check it out: https://docs.aiohttp.org/en/stable/faq.html

Thanks for the quick reply. I will try these options(Quart , aiohttp).

Great! I will close this issue for now. Feel free to reopen this one or create a new issue if you have questions.

For people landing on this question. I've created a small example of an CSMS integrated with an HTTP API using aiohttp. The code can be found in this comment,

The aiohttp version is shared in the comment I linked in my previous post.


Feature request: resize query window

Recently I've been using the query window a lot, and there are two things that would improve my experience;

resizable query window on mouse drag - drag down to expand
it's difficult now to click on the last row as the scroll bar pops up

Query window is already resizable, so not sure what the problem is - you just need to hover over the horizontal divider line.
Regarding your second point - i'm not sure what you mean, perhaps a screenshot is in order?

Oh you're right. I've been trying to resize from the bottom of the code box instead of the line below the buttons.
As for the second point; if I try to select the code in line 101 and hover over the line I get the scroll bar. I suppose this could be fixed by adding a little margin

I recommend dropping a few extra blank lines in the query textfield :)
On a serious note, i'll see what could be done, maybe adding an extra margin is all that needed.


BUG Image_Cached objects (resampled images) don't inherit all properties

When Image_Cached objects are created in Image::getFormattedImage() only the Title and ParentID properties are copied from the source Image object. All other properties, including any assigned by extensions, are ignored. This means you can't access any custom Image properties (such as a Caption or a set of focus point coordinates :wink:) on resampled image instances in templates. This is bad for chainabiilty and template flexibility.
I figure this is a bug, and hopefully not very hard to fix but I'm not sure the best way to go about it. I would think though that rather than specify the properties you do want to copy to the new Image_cached object, it would be better to specify the exclusions (ID and Filename?) and copy everything else.

Could you set the failover to the original object?

I bet I could! But I don't know what that means :D

Check out ViewableData::$failover
Make sure you set it in the Image_Cached constructor, and you'll probably never see this problem again.  ;)

Cool thanks! I'll check it out

Should this inevitable PR target 3.1 as a bugfix, or 3.3 as a new feature?

I'd put it into 3 branch. :)

The failover approach didn't work for me - maybe it doesn't kick in because the Image_Cached object already has Title etc. properties, they're just null/false/default values? I've tried a different approach which seems to work: https://github.com/silverstripe/silverstripe-framework/pull/4578


Spring crop refuses to go away

I had some strawberries planted as the season rolled over from Spring to Summer. The next day, seeing the unharvestable crops, I removed them (with a sickle) and replaced them with Corn. Later, when I slept, and returned to the farm, the strawberries had returned, replacing the corn that was there the day before. I removed and replaced them again, but they came back again the next day. I tried removing the tilled ground beneath them, and replacing them with dirt, but they still came back.
This was printed whenever I slept (a number of times, I think one for each crop): http://paste.feed-the-beast.com/view/afbe0fd2
Exiting minecraft and re-entering the world fixed the problem, I've since cheated myself some Corn seeds to make up for the loss.

I saw this once, but it never seemed very consistent. And I haven't had it since. Can I see the full log? I'll try and recreate it in the mean time..

Sorry, it looks like it's split into two. The one has the forge stuff and the other has the error and stuff.
fml-client-3.log: http://paste.feed-the-beast.com/view/532994f0
2016-10-01-7.log: http://paste.feed-the-beast.com/view/53688ee4

As I was unable to recreate this based on the same things you did, All I can think of is somehow, the data wasn't remove the daily ticking. I'll explicitly remove them when I kill crops. Instead of relying on the destruction of the tile to do that.

As I was unable to recreate the issue. I tried somethings. Don't know if they'll work or not... But if you can try out this build and let me know, that would be very helpful. Part of the issue may have been that I messed up and had withered crops as growing still, as well as not removing them from the daily ticking when they did. But relying on the tile changes for that.
http://joshiejack.uk:8080/job/Harvest-Festival/job/1.10.2/87/

I was able to do it again when my Corn transitioned from Summer to Fall, but it didn't print anything to the log that time.
I don't know if this build fixed anything, as it produced a new crash when I loaded into a world: http://paste.feed-the-beast.com/view/a9e7b606
I was able to create a new world just fine, but planting any seeds caused the crash to occur again.

Ehhhhh annoying. What did I break. Worked in dev (but also tried out of dev, was broken for me too).

Okay I am going to bed now. Give this one a go when it's done building: http://joshiejack.uk:8080/job/Harvest-Festival/job/1.10.2/88/

This looks like it fixed it!


Implemented the additional properties resolver

RabbitMQ 3.5 has a method to send a message with different priority's. But currently we can't send additional properties to the consumer. This implements my pull request https://github.com/SimpleBus/Asynchronous/pull/2.
Our use case is that we have a CommandHandler which is generating video's from images. We have a cronjob that gets new images from different api's and from that it generates images. But sometimes a customer needs de latest video fast and with the priority option it can skip the line and proces faster.
This pull request depends on https://github.com/SimpleBus/Asynchronous/pull/2

Travis-CI fails becues it depends on my other pull request I don't know how to fix that

Nice! As mentioned in your other PR, it would be great to have multiple
resolvers. You should be able to register them with a tag and a priority.
Would you agree with that?
Op 18 apr. 2015 14:25 schreef "Cliff Odijk"<EMAIL_ADDRESS>
RabbitMQ 3.5 has a method to send a message with different priority's. But
currently we cant send additional properties to the consumer. I implemented
the base classes here but did not give an implementation like the routing
key resolver.
Our use case is that we have a CommandHandler which is generating video's
from images. We have a cronjob that gets new images from different api's
and from that it generates images. But sometimes a customer needs de latest
video fast and with the priority option it can skip the line and proces
faster.
This pull request depends on SimpleBus/Asynchronous#2
https://github.com/SimpleBus/Asynchronous/pull/2
You can view, comment on, or merge this pull request online at:
https://github.com/SimpleBus/RabbitMQBundleBridge/pull/9
Commit Summary

Implemented the additional properties resolver

File Changes

M src/DependencyInjection/Configuration.php
https://github.com/SimpleBus/RabbitMQBundleBridge/pull/9/files#diff-0
(4)
M
src/DependencyInjection/SimpleBusRabbitMQBundleBridgeExtension.php
https://github.com/SimpleBus/RabbitMQBundleBridge/pull/9/files#diff-1
(14)
M src/RabbitMQPublisher.php
https://github.com/SimpleBus/RabbitMQBundleBridge/pull/9/files#diff-2
(13)
M src/Resources/config/commands.yml
https://github.com/SimpleBus/RabbitMQBundleBridge/pull/9/files#diff-3
(1)
M src/Resources/config/events.yml
https://github.com/SimpleBus/RabbitMQBundleBridge/pull/9/files#diff-4
(1)
A src/Resources/config/properties.yml
https://github.com/SimpleBus/RabbitMQBundleBridge/pull/9/files#diff-5
(4)
M tests/RabbitMQPublisherTest.php
https://github.com/SimpleBus/RabbitMQBundleBridge/pull/9/files#diff-6
(16)

Patch Links:

https://github.com/SimpleBus/RabbitMQBundleBridge/pull/9.patch
https://github.com/SimpleBus/RabbitMQBundleBridge/pull/9.diff

—
Reply to this email directly or view it on GitHub
https://github.com/SimpleBus/RabbitMQBundleBridge/pull/9.

Done!

Looks good!
Some comments:

Could you add a property resolver as a service for the functional test and verify that the right properties are being added?
Maybe we should already release a new version simplebus/asynchronous so we can make the tests on Travis pass ;)

Could you add a property resolver as a service for the functional test and verify that the right properties are being added?

I'm not sure what you mean but i will try to add a new test inside the functional test class.

Maybe we should already release a new version simplebus/asynchronous so we can make the tests on Travis pass ;)

I was thinking about this i really like the idea of separating packages because with that you don't have the optional dependencies like in your blog. But doing pull requests like these you need to create multiple pull requests which have dependencies on each other how could we solve these problems without releasing things and still be able to create pull request that won't fail?

Could you add a property resolver as a service for the functional test and verify that the right properties are being added?

I'm trying to test this and currently i have added the service inside the functional test config.yml but the service is private how could i test if the resolver is registering the right properties?

I was thinking about this i really like the idea of separating packages because with that you don't have the optional dependencies like in your blog. But doing pull requests like these you need to create multiple pull requests which have dependencies on each other how could we solve these problems without releasing things and still be able to create pull request that won't fail?

Right, this is where I regret that I didn't create one big repository and letting them be split into several smaller ones by some automatic tool. That would have made life so much easier...
In the past I did some tricks with having branch aliases in Composer, lowering minimum stability, etc. but I'm not sure it'll work in this case.

Also, about the test: the unit test for the RabbitMqPublisher is just fine. If you can think of a way in which to functionally test this, i.e. verify something on the consuming side, etc. that would be a nice to have. Otherwise, if you see this working properly, then we could also just leave it at that.

In the past I did some tricks with having branch aliases in Composer, lowering minimum stability, etc. but I'm not sure it'll work in this case.

I'm doing this locally to run the test suit but i don't think i should push to my pull request right?

Also, about the test: the unit test for the RabbitMqPublisher is just fine. If you can think of a way in which to functionally test this, i.e. verify something on the consuming side, etc. that would be a nice to have. Otherwise, if you see this working properly, then we could also just leave it at that.

I just added a test using an alias of the delegate resolver service to make it public and then test if properties are being handled.

I just added a test using an alias of the delegate resolver service to make it public and then test if properties are being handled.
I see, you're testing that the specialized property resolver is actually used. It would also be great to verify the behavior of the publisher in some way, but this may not be easy. For now I'd say we're fine.

I just tagged v1.1.0 of simple-bus/asynchronous by the way. So now you can change the required version in the composer.json to ^1.1.0 to make sure that when people install this library, those classes exist.

I see, you're testing that the specialized property resolver is actually used. It would also be great to verify the behavior of the publisher in some way, but this may not be easy. For now I'd say we're fine.

What do you think of this new test i just implemented. During runtime i'm changing the producer to a mocked version to capture the date being send to the producer.

I just tagged v1.1.0 of simple-bus/asynchronous by the way. So now you can change the required version in the composer.json to ^1.1.0 to make sure that when people install this library, those classes exist.

I have updated my pull request to "simple-bus/asynchronous": "~1.1"

Coverage increased (+4.99%) to 30.6% when pulling 01286a694991e22cb0c6c61571b0d9f5adbdc738 on cmodijk:patch-1 into 788f3391636f93439da33b34e944f74777f1de61 on SimpleBus:master.

Coverage increased (+4.99%) to 30.6% when pulling 01286a694991e22cb0c6c61571b0d9f5adbdc738 on cmodijk:patch-1 into 788f3391636f93439da33b34e944f74777f1de61 on SimpleBus:master.

Maybe you saw it but I released a new major version of this package. I removed the Message interface and all type-hints for it so maybe we can release your feature is 2.1.0?

Yes I saw this, is there any documentation why you did this change?

Coverage decreased (-1.27%) to 24.34% when pulling 455631c501f349e63d7da54d0c464747b77f3a5f on cmodijk:patch-1 into 69b5ec2709be92e8eb72996adb7e0e27d4382995 on SimpleBus:master.

I have just updated my pull request to match the upstream

Coverage increased (+4.99%) to 30.6% when pulling 6619a499ab9c33e6558264fe3dceda4912fbeda9 on cmodijk:patch-1 into 69b5ec2709be92e8eb72996adb7e0e27d4382995 on SimpleBus:master.

Thanks again!
I added some documentation as well: http://simplebus.github.io/RabbitMQBundleBridge/doc/additional_properties.html and http://simplebus.github.io/Asynchronous/doc/additional_properties.html

Cool! Tnx for writing the docs that's not my strong point.

No problem!
Op 6 mei 2015 12:27 schreef "Cliff Odijk"<EMAIL_ADDRESS>
Cool! Tnx for writing the docs that's not my strong point.
—
Reply to this email directly or view it on GitHub
https://github.com/SimpleBus/RabbitMQBundleBridge/pull/9#issuecomment-99410519
.


Performance

Hi and thank you for your work.
Have you tested your implementation on the benchmarks/datasets mentioned in the paper?

Here are some performance tests:

ModelNet40: OA 91.3%
S3DIS

Ahh I see, thank you for your quick response.
Closing this issue.


Re-enable network access for AVDs

The video_player driver test asset videos live stream duration != 0 is failing (see failure: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android android_platform_tests_shard_6 master/1962/overview) because https://flutter-review.googlesource.com/c/recipes/+/61440 removed the flag that enables network access. In the long run, this should be re-enabled on a per-test basis (see https://github.com/flutter/flutter/issues/160691), but https://flutter-review.googlesource.com/c/recipes/+/61660 should be landed for now to un-skip the asset videos live stream duration != 0 test.

Note that the following test was also failing:

network videos reports buffering status

And got skipped as well (both have TODOs in the code linking to this issue)


Update skills round css

Rearranged labels, change colour of background and text.

#93

Tested on my local machine and the font sizing looks a bit different. Running Windows 10. I'll give it another look later.
Otherwise, the code looks okay. LMK if this is intended.

Yeap the font size is as intended, skills smaller than round of job application, could you ss again, i changed the font thickness, i think it only renders in windows.

Codecov Report

Merging #92 (8955d62) into master (b0251f6) will increase coverage by 0.15%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master      #92      +/-   ##
============================================
+ Coverage     73.00%   73.16%   +0.15%
- Complexity      429      445      +16
============================================
  Files            74       76       +2
  Lines          1293     1323      +30
  Branches        135      140       +5
============================================
+ Hits            944      968      +24
- Misses          316      321       +5
- Partials         33       34       +1

Impacted Files
Coverage Δ

...du/linkedout/logic/parser/SearchCommandParser.java
94.73% <0.00%> (-5.27%)
:arrow_down:

src/main/java/seedu/linkedout/MainApp.java
0.00% <0.00%> (ø)

.../seedu/linkedout/logic/commands/SearchCommand.java
100.00% <0.00%> (ø)

...model/applicant/NameContainsKeywordsPredicate.java
100.00% <0.00%> (ø)

...el/applicant/NameContainsAllKeywordsPredicate.java
100.00% <0.00%> (ø)

.../model/applicant/JobContainsKeywordsPredicate.java
100.00% <0.00%> (ø)

...u/linkedout/model/applicant/KeywordsPredicate.java
42.85% <0.00%> (ø)

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 b0251f6...8955d62. Read the comment docs.

@RyanCheungJF Yeap the font size is as intended, skills smaller than round of job application, could you ss again, i changed the font thickness, i think it only renders in windows.
Upon second inspection, I think I will make it the same font size to match our mock UI

I've pulled the latest changes from your branch. This is the latest result.


Extend absolute path file

I had a problem  with extend an absolute path file in node.js
This may correct it :
extend bug details

This is an issue for me as well.

Closing due to lack of simple example to reproduce.
If this is still an issue, please reopen and provide a TwigFiddle example of it working in TwigPHP and the same example in twig.js using this template.


The resource type could not be found in the namespace 'Microsoft.Compute' for api version '2016-04-30-preview'

Environment summary
Install Method: How did you install the CLI? (e.g. pip, interactive script, apt-get, Docker, MSI, nightly)
Answer here:
followed instrucstions on
https://docs.microsoft.com/en-us/cli/azure/install-azure-cli
CLI Version: What version of the CLI and modules are installed? (Available with az --version)
Answer here:
azure-cli (2.0.2)
acr (2.0.0)
acs (2.0.2)
appservice (0.1.2)
batch (2.0.0)
cloud (2.0.0)
component (2.0.0)
configure (2.0.2)
container (0.1.2)
core (2.0.2)
documentdb (0.1.2)
feedback (2.0.0)
find (0.0.1b1)
iot (0.1.2)
keyvault (2.0.0)
lab (0.0.1)
monitor (0.0.1)
network (2.0.2)
nspkg (2.0.0)
profile (2.0.2)
redis (0.1.1b3)
resource (2.0.2)
role (2.0.1)
sql (2.0.0)
storage (2.0.2)
vm (2.0.2)
Python (Linux) 2.7.12 (default, Nov 19 2016, 06:48:10)
[GCC 5.4.0 20160609]
OS Version: What OS and version are you using?
Answer here:
ubuntu linux 16.04
Shell Type: What shell are you using? (e.g. bash, cmd.exe, PowerShell)
Answer here:
bash
Description
Hi,
when I execute:
az disk create ..
( based on the description
https://docs.microsoft.com/en-us/azure/virtual-machines/linux/upload-vhd )
I get an error:
"
The resource type could not be found in the namespace 'Microsoft.Compute' for api version '2016-04-30-preview'.
"
I am currently running this command in: AzureGermanCloud
( that is the output of: az cloud show )
Please fix this issue. Thanks in advance.

Let us use #2190 to trace sovereign clouds.
@bleissem, you need to wait, and hope it won't be long


make classes final

Pull Request Test Coverage Report for Build 1430

508 of 508 (100.0%)  changed or added relevant lines in 39 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.4%) to 100.0%

Totals

Change from base Build 1390:
0.4%

Covered Lines:
932

Relevant Lines:
932

💛  - Coveralls


Hi, sorry if I'm misunderstanding, or maybe it's because Server Components are still alpha, but I was under the impression that this demo would load zero javascript.
If I look in the browser devtools network tab on https://next-news-rsc.vercel.sh/csr for example I'm seeing it loads a bunch of js files like https://next-news-rsc.vercel.sh/_next/static/chunks/313-ac2dffa02b6a4c2a.js.
Is this because the functionality is not out of alpha, or am I understanding wrong? Would love to use this.

Sorry for the confusion, that page /csr doesn't use Server Components (as you can see here: https://github.com/vercel/next-rsc-demo/tree/main/pages). We will improve the wording there to "Without React Server Components and Streaming", thanks for the feedback!
To answer your question, when using Server Components all server module imports will not be bundled and shipped to the client. Here is a detailed example and explanation: https://twitter.com/benschwarz/status/1466213985334693889.
But there will still be JavaScript shipped to the client just to make sure client transition and React hydration are working, as Dan Abramov explained in the same thread:

ReactDOM is literally “React” so yes, it is expected to be included on all pages. Server Components don’t remove the need for React itself — otherwise you wouldn’t be able to add interactive bits on the client. (However, SSR lets you show content as HTML before JS loads.)
From https://twitter.com/dan_abramov/status/1466554954944958466

Thanks a lot for the explanation! I'm actually quite surprised to learn that server-side libs were sent to the client until now. Seems like good steps are being taken to make Next/React the best of both worlds between SSR and interactive on the client, but it's not there yet.

@shuding does it mean that if I will have a page as a server component (index.server.tsx) no JS would be bundled into that page's file (static/chunks/pages/index-[fingerprint].js)? So I wouldn't have JS for example of my UI components and styled-components?


Don't warn/immediately timeout when terminate-after=1?

I am using nextest non-interactively, so I don't really want to be warned that a test has been running for a while, I just want it to be killed. So I am using a config that looks like this:
[profile.default-miri]
slow-timeout = { period = "60s", terminate-after = 1 }

And I get output that looks like this:
        SLOW [> 60.000s]           regex::backtrack crazy::nest_limit_makes_it_parse
     TIMEOUT [  60.052s]           regex::backtrack crazy::nest_limit_makes_it_parse

I'm not sure it makes a whole lot of sense to print the slow notification first here. Could nextest just emit:
     TIMEOUT [  60.000s]           regex::backtrack crazy::nest_limit_makes_it_parse

So I actually thought about this! My big concern was that the TIMEOUT message is printed after the process terminates, which can take up to 10 seconds longer if the process somehow blocks SIGINT.
I think we should replace that last SLOW message with TERMINATING or something.

I agree with what you're saying for the general case, but of course my follow-up question is...
Can I tell nextest that I don't care about graceful shutdown, so that I just see the TIMEOUT instead of the TERMINATING? I'm even interested in nextest using SIGKILL instead, so that it doesn't even have to consider a delay between timeout and the test actually shutting down. (of course I have no idea how this would/could work on other platforms)

Nextest's kill procedure is currently hardcoded:

send SIGTERM
wait 10 seconds for the process to die
if it doesn't die within those 10 seconds, send SIGKILL

We could make this timeout configurable and set it to 0 for an immediate SIGKILL, I guess. Would you like to work on this?
(On Windows we always do a SIGKILL equivalent immediately)

Yup, I'm going to look into this. I'll let you know if I get stuck.

This is going to be out as part of cargo-nextest 0.9.39, releasing shortly. Thanks for working on this!


Add the ability to tessellate based on the field to the Tessellate operator.

Description
I added the ability to tessellate based on the field variation within a high order cell to the Tessellate operator. Previously it only considered the curvature of the element in deciding how to tessellate the high order element.
I added a "Field criterion" setting to the Tessellate operator that controls the tessellation based on the field values.
I added a vtk test file with a biquadratic quad that contained a spherical field within the element. I also updated the documentation and added tests using the new test data. I didn't update the release notes since the Tessellate operator is new for this release and there was already information about it being added.
Type of change
New feature.
How Has This Been Tested?
I added tests to the test suite. I also generated the html from the updated documentation and proofread it and verified that it didn't generate any new warning or error messages.
Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] I have added debugging support to my changes
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[X] I have added any new baselines to the repo
[X] I have assigned reviewers

Thanks for the heads-up. I didn’t know that!


Recreate SparkContext if job is cancelled unexpectedly

We hit an out of memory issue due to unstable streaming which resulted in Spark cancelling the job. The driver kept running with a stopped context. We need to recreate the context in the event that it's stopped unexpectedly.

Resolving as we're now tracking this elsewhere.


Added Typescript version of usePrevious hook

I provided Typescript version of usePrevious hooks. I tried to be as generic is possible, if there is some mistakes let me know.

Also added useWindowsSize hook Typescript version

Thank you!


.gitattributes: make sure *.h *.c are detected as C

Currently a large portion of your code is detected as Objective C, which is incorrect. Use .gitattributes to mark it as C.

this looks like github' fault more than anything being wrong with repo itself but this was annoying enough for me so might as well fix it this way

https://github.com/github/linguist/issues/1626


Undo of replacing all DNAs in sequence in view mode on preser (C) from the library causes undeletable monomer on the canvas (all of them)

Steps to Reproduce

Go to Macromolecules mode - Sequence mode
Load from file: Replacing all DNAs in sequence in view mode from the library causes undeletable monomer on the canvas (all of them).zip

Select all monomers (in view mode)

Go to Library - RNA tab - Presets
Click on C preset

Press Undo button

Actual behavior
@ symbol remains one the canvas

If you switch to flex mode - you found corrupted canvas

Expected behavior
Canvas returned back to initial state

Versions

Ketcher Version 2.24.0-rc.1 Build at 2024-08-06; 19:17:47
Indigo Toolkit Version 1.23.0-rc.1.0-g85f89b8f5-wasm32-wasm-clang-19.0.0
Windows 10 Pro
Chrome Version 127.0.6533.100 (Official Build) (64-bit)

Related issue - https://github.com/epam/ketcher/issues/4878

Fixed.

Ketcher Version 2.24.0-rc.2 Build at 2024-08-14; 19:00:14
Indigo Toolkit Version 1.23.0-rc.2.0-g6a2a7526a-wasm32-wasm-clang-19.0.0
Chrome Version 127.0.6533.100 (Official Build) (64-bit)
Win10


Unable to run test suite on newly created database (after v0.1.4)

Hi!
I am having issues running the test suite for v0.1.4 on a fresh database.
I am getting this error:
ActiveRecord::StatementInvalid:
PG::UndefinedTable: ERROR:  relation "events" does not exist
LINE 8:  WHERE a.attrelid = '"events"'::regclass

Steps to reproduce:

Drop the database
Create the database
Install timescaledb extension (btw, it would be useful to add this step to the README).
Run test suite

If I do the same process on v0.1.3, there are no issues. Also, if I run the tests on v0.1.3 and then run the tests on v0.1.4 (without recreating the DB), no issues, this is probably why this was not caught before?

Apologies, I forgot to run bundle exec rake test:setup... All good.


Use argument --tcplisten

How do I pass arguments to wasmtime through the shim? I want to use --tcplisten to listen for TCP connections.
I'm trying this command.
ubuntu@wasi:~$ sudo ctr run --rm --runtime=io.containerd.wasmtime.v1 docker.io/martinlinkhorst/wasi:latest wasi10
info: Microsoft.Hosting.Lifetime
      Now listening on: http://localhost:5000
Fatal: TCP accept failed with errno 8. This may mean the host isn't listening for connections. Be sure to pass the --tcplisten parameter.

We currently don't have a way to pass arguments to embedding wasmtime in the shim. What you can do, however, is to write a new shim using runwasi as a library and enable tcplisten in wasmtime.
Check this out: https://github.com/Mossaka/containerd-wasm-shims/blob/main/containerd-shim-aspdotnet-v1/src/main.rs#L89-L90

Thanks a lot!

Going to go ahead and close this as this should indeed be done in a new shim.
The shims in this repository are (currently) strictly for wasi.
The wasmtime shim is also not using the wasmtime binary which is what implements this functionality.
It is using wasmtime as a library.


#626 implement /api/dashboard endpoint

This implements the /api/dashboard endpoint as described in the api doc, and in discussion on slack.
However, I was not able to get a closed_time for a Proposal. AFAIKT there is no record of the end time of a proposal. I have instead serialized the is_vote_closed property on Proposal. Please let me know if I've missed something there.
Example response body
{
  "roles": [
    {
      "id": 1,
      "name": "Base User",
      "description": "",
      "number_of_members": 2
    },
    {
      "id": 2,
      "name": "Integration Admin",
      "description": "",
      "number_of_members": 2
    }
  ],
  "community_doc": "This is a test document.",
  "platform_policies": [
    {
      "id": 3,
      "name": "Test Policy",
      "description": ""
    },
    {
      "id": 1,
      "name": "All Platform Actions Pass",
      "description": "All platform actions pass automatically"
    }
  ],
  "constitution_policies": [
    {
      "id": 2,
      "name": "All Constitution Actions Pass",
      "description": "All constitution actions pass automatically"
    }
  ],
  "proposals": [
    {
      "id": 1,
      "status": "passed",
      "proposal_time": "2024-03-09T03:25:08.653763Z",
      "is_vote_closed": true,
      "action": {
        "id": 1,
        "action_type": "policykitadduserrole"
      },
      "initiator": {
        "id": 1,
        "readable_name": "d.douglas.carr"
      },
      "policy": {
        "id": 2,
        "name": "All Constitution Actions Pass",
        "description": "All constitution actions pass automatically"
      }
    },
    {
      "id": 2,
      "status": "passed",
      "proposal_time": "2024-03-09T03:25:45.363079Z",
      "is_vote_closed": true,
      "action": {
        "id": 2,
        "action_type": "policykitaddcommunitydoc"
      },
      "initiator": {
        "id": 1,
        "readable_name": "d.douglas.carr"
      },
      "policy": {
        "id": 2,
        "name": "All Constitution Actions Pass",
        "description": "All constitution actions pass automatically"
      }
    },
    {
      "id": 3,
      "status": "passed",
      "proposal_time": "2024-03-09T05:20:48.448574Z",
      "is_vote_closed": true,
      "action": {
        "id": 3,
        "action_type": "policykitaddplatformpolicy"
      },
      "initiator": {
        "id": 1,
        "readable_name": "d.douglas.carr"
      },
      "policy": {
        "id": 2,
        "name": "All Constitution Actions Pass",
        "description": "All constitution actions pass automatically"
      }
    }
  ]
}

I think it looks good to me, except I am not sure whether we should only display one community document or not (see discussion in the slack)

Thanks for reviewing @leijie-wang. I've updated the PR to use the community_docs property, as discussed with @antiantivirus on Slack.

Thanks @ddouglascarr!


csvcubed-devtools has no tests

There are no tests in csvcubed-devtools, which resulted in errors in upstream packages, to avoid this tests need to be built to ensure that the tools are doing what they say they are.

It does now https://github.com/GSS-Cogs/csvcubed-devtools/actions/runs/3313137144


Cannot retrieve Info from Probe when using ctypes python wrapper.

I am using a python wrapper to include the solum library in my python application. When passing something to the Library I mostly get the error that the information could not be retrieved. An example is receiving the StatusInfo to get the probe Battery and Temperature.
CusStatusInfo is defined:
class CusStatusInfo(Structure):
_fields_ = [
    ("battery", c_int),
    ("temperature", c_int),
    ("frameRate", c_double),
    ("teeTimeRemaining", c_double),
    ("fan", c_int),  # Use the enum directly if ctypes integration is needed
    ("guide", c_int),  # Use the enum directly if ctypes integration is needed
    ("charger", c_int),  # Use the enum directly if ctypes integration is needed
]

The Info is then retrieved by:
probe_status = CusStatusInfo()
self.lib.solumStatusInfo.argtypes = [POINTER(CusStatusInfo)]
self.lib.solumStatusInfo.restype = c_int
result = self.lib.solumStatusInfo(byref(probe_status))
print(result)
print(probe_status.temperature)

result always results in -1 and the temperature is returned as 0
The issue happens on most functions I call to send something to the library.
When setting CusParam.IMUStreaming to on (1) I also get the return value -1. However. After a few seconds after the call IMUStreaming seem to work as the callback function is called properly.  It seems that the return value I get is -1, even if it was succesfull. Is there a timing issue (The function is called, but the Library does not wait until the probe returns the value)?
I am using the Solum API v11.3 on the L15HD Probe.
Is the behaviour known? Is there any known way for these calls to work?
Thank you and kind regards,
Christian

I cannot say for homemade python wrappers, we made one specifically for the Cast API, and given the asynchronous nature of our APIs, it may be necessary to do the same for Solum in order to function properly.

I tried to replicate this issue in my C++-Code and I got the same issue.
I call my function
int res;
if(isImuStreamingOn){
res = solumSetParam(ImuStreaming, 1.0);
}
std::cout << "IMU Streaming Res: " << res << std::endl;
Which results in a print "IMU Streaming Res: -1

you are using version 12 now?


Add ready blocks to processing

When calling done on the BlockScheduler, add the next set of blocks (the immediate successor blocks), if any, to the processing list.
This corrects an issue where the blocks are scheduled again due to not being marked as in-process via the above mechanism.

Also, a backport PR is required for this patch on 1-2

Will add after it is merged


refactor(sfu): optimize AudioObserver

Description
Even in large session, list of active speakers is always short. Change to sort/clone smaller list, use map for streams, and reuse slice.

besides reusing the string slice, which I agree why moving to map is more performant? Can we add a benchmark so we can be sure?

@OrlandoCo For large session, current codepath need to sort all streams even quiet ones. But active speakers are usually very short 0-3 in practice.

Even large sessions are small enough for a slice to get better performance than a map, we can make that the slice just get active speakers and on calc just clear it with [:0] until the next loop. We can benchmark both if required.

@OrlandoCo Yap, in general, audio stream count is relatively small, not likely to have a few hundred audio publishers in practice. Do you know how often observe() is called? Is AudioLevelExtension included in every RTP audio packet? Currently, DataChannel in PeerLocal use map not slice, but DC count is also small per session. Lol, I feel embarassed for doing premature optimization while removing another one.

@OrlandoCo I just implemented to use slice as you suggested, the problem of using slice  is that sort.Slice can't work on short streamIDs list (doesn't have a map to look up), so it is back to sorting full stream.
https://github.com/pion/ion-sfu/blob/d663b423c96b186e12458e61ba53e010d5ce092b/pkg/sfu/audioobserver.go#L82
To reuse previous slice, its type need to change from []string too. Do you wan to see the alternative version?

@OrlandoCo Here is the alternative version using slice. IMHO, map version is simpler.
https://github.com/Screenleap/ion-sfu/commit/85d6678b9f1ec4b646406a2f0ffc213c15ee23ac

@OrlandoCo Here is the alternative version using slice
https://github.com/Screenleap/ion-sfu/commit/154f24e8aeb1f0ea8c386b32b21bcafcd77861ae


feat: support block gzip for streams

Which issue does this PR close?
Closes #9156
Rationale for this change
Updates the stream gzip decoding to check for multiple members within a file.
What changes are included in this PR?
Doesn't update the Read decoder because it already supports multiple members in a file.
Are these changes tested?
The gzip decoding still seems to work, and I checked a manually bgzipped file, but I'm not sure if this code path is tested already.
Are there any user-facing changes?
No

Thanks @alamb -- certainly down to add a test. Before I go the route you mentioned, I wanted to ask if you knew that would follow the stream decoding path? Looking at https://github.com/apache/arrow-datafusion/blob/ae882356171513c9d6c22b3bd966898fb4e8cac0/datafusion/core/src/datasource/physical_plan/csv.rs#L393-L441 in the CsvOpener, I think local files would result in .convert_read being called and not .convert_stream which is what is modified in this PR? Is that right?
If not I'll code that up, otherwise perhaps adding a specific unittest that calls .convert_stream or maybe there's a way to force .convert_stream to be called from the slt-based tests? Thanks!

If not I'll code that up, otherwise perhaps adding a specific unittest that calls .convert_stream or maybe there's a way to force .convert_stream to be called from the slt-based tests? Thanks!

I think a specific unit test for convert stream would be great and easiest (and you can probably just generate some data directly)

I think this is ready for review @alamb.
Happy to take another approach testing, but in 4e009e1 I added the test which creates a byte stream from a hardcoded vector.

Thanks!


Use processed filter list for native dialogs.

Fixes https://github.com/godotengine/godot/issues/99250
Ensures native dialog filters are translated, have autogenerated filters included and use the same text on all platforms.

Thanks!


Sonnet support for images

Issue
Will sonnet support images? Also it would be great to be able through some mechanism to quickly add images. My idea is my Flameshot automatically ads screen to /add image command. Is there any interface how to do that in python?
Version and model info
No response

Also make sure it works with OpenRouter too

Thanks for trying aider and filing this issue.
This looks like a duplicate of #556, so I'm going to close it so discussion can happen there. Please let me know if you think it's actually a distinct issue.

#556  is related, but I think it's a separate issue.
openrouter/openai/gpt-4 is not listed in models.py, so comprehensive configurations need to be written or a special process for openrouter should be added.
I created Sonnet support itself as a Pull Request, so please check it!

I merged it. Thanks!


The volume and music time sliders not appearing properly

For some reason, when I installed this theme the sliders had a duplicated circle (or slider dot). It is not especially annoying but looks really unappealing when using the slider to move around the music.
Things to note:

Running the latest version of Spotify/spicetify (spicetify 2.14.3)
Installed this theme yesterday

Can't reproduce the issue. Works all fine OOB on my end.

@HubCode07 it usually happens when you moved from fluent spicetify to bloom spicetify
Send us a screenshot of your xpui.js file
We will let you know how to fix it by yourself
(Note: this happens when you haven't properly uninstalled previous versions of bloom or spicetify-fluent or else when you apply the theme wrong)

I had this issue. Very easy to fix. I had previous installed Fluent and the Fluent.js was still in the config even after uninstalling. Just remove that as well as deleting the fluent folder from your Themes folder. Make sure you have
[Patch]
xpui.js_find_8008 = ,(\w+=)32,
xpui.js_repl_8008 = ,${1}56,
This fixed everything for me.

@ryanmoz Thanks it is the solution
We will wait for @HubCode07 to conform its fixed
Anyways thanks for your solution @ryanmoz
And also a special thanks to @windowz414  for quick response for this issue
You make bloom better!

[AdditionalOptions]
home_config           = 1
experimental_features = 1
extensions            = fluent.js|bloom.js
custom_apps           = marketplace
sidebar_config        = 1
[Patch]
xpui.js_find_8008 = ,(\w+=)32,
xpui.js_repl_8008 = ,${1}56,
[Setting]
inject_css              = 1
replace_colors          = 1
overwrite_assets        = 1
check_spicetify_upgrade = 0
spotify_path            = C:\Users\nachi\AppData\Roaming\Spotify
current_theme           = bloom
color_scheme            = dark
spotify_launch_flags    =
prefs_path              = C:\Users\nachi\AppData\Roaming\Spotify\prefs
[Preprocesses]
disable_upgrade_check = 1
disable_sentry        = 1
disable_ui_logging    = 1
remove_rtl_rule       = 1
expose_apis           = 1
; DO NOT CHANGE!
[Backup]
version = <IP_ADDRESS>8.g1e4ccc6e
with    = 2.14.3

[AdditionalOptions]
home_config           = 1
experimental_features = 1
extensions            = fluent.js|bloom.js
custom_apps           = marketplace
sidebar_config        = 1
[Patch]
xpui.js_find_8008 = ,(\w+=)32,
xpui.js_repl_8008 = ,${1}56,
[Setting]
inject_css              = 1
replace_colors          = 1
overwrite_assets        = 1
check_spicetify_upgrade = 0
spotify_path            = C:\Users\nachi\AppData\Roaming\Spotify
current_theme           = bloom
color_scheme            = dark
spotify_launch_flags    =
prefs_path              = C:\Users\nachi\AppData\Roaming\Spotify\prefs
[Preprocesses]
disable_upgrade_check = 1
disable_sentry        = 1
disable_ui_logging    = 1
remove_rtl_rule       = 1
expose_apis           = 1
; DO NOT CHANGE!
[Backup]
version = <IP_ADDRESS>8.g1e4ccc6e
with    = 2.14.3
Also I have deleted fluent on my computer

And also a special thanks to @windowz414 for quick response for this issue
You make bloom better!

Any time, @nimsandu! You're the one who made Bloom and so managed to establish this strongly bonded community. I should thank you for that. <3

I did all of the instructions said above but it did not work for me (it did not fix the problem) here is the screenshot of the file

Sorry for the wait, here is the text file if you need it (converted file, since GitHub, does not support js files)
xpui.txt

issue fixed reinstalled Spotify and worked


[thci] print traceback and re-raise exceptions

THCI used to catch Exceptions and print errors using ModuleHelper.WriteIntoDebugLogger. However, in most of time it just help hide the actual issue and make it harder to debug.
Re-raising the exceptions should be a better approach:

@API decorator will print the full exception Traceback via ModuleHelper.WriteIntoDebugLogger and then re-raise.

Good cleanup, thanks!
Maybe for another PR, I'd be in favor of unifying what we are printing, i.e., remove print(cmd) everywhere and just keep it in __executeCommand().

Can't agree more. print(cmd) or print('call methodName') are mostly redundant because we are already printing in __executeCommand and @watched or @API.
We may clean it up in another PR.


Feat: Borderless inputs and textAlign prop on button

What kind of change does this PR introduce?
Adds borderless inputs and textAlign prop to button

@i-pip applying a couple of edits, hope that's ok 👍  😄

fixed Text Area as well, let me know if that's ok 😄

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix amount field description in swagger

[x] fix amount field description in swagger

Comments

Issue Number

bors r+

bors r+

bors r+


Add profile panel in Ui

pushing to check code coverage
edited multiple files, also added fxml files which cannot be tested, will find a way
likely to fail some tests

@ziyang27 is this still an open issue or can this be closed?

@tanyunchao still need, dun have enough code coverage to merge yet

Some changes from my initial PR:

added tests
integrated with the rest of the features

Note: The test coverage will tank a little. I implemented quite a few UI components that were not tested.

@tanyunchao @Colex2000 ready to merge already, can help me a take a look when you free?


Doc build fixes

Includes:

Update UWP versions in doc build templates

Leaving this open until we confirm that the full doc build works.

I tested this PR for the UWP samples builds (100.8) . It worked for UWP and Xamarin.Forms.UWP. Can you please merge your fix? That way the Jenkins build machine will get it. Many thanks. -don


Minor tidy-up

Move go.mod and go.sum to the e2e folder (all Golang stuff should be in the e2e folder imo)
Delete node_modules and yarn.lock in the root directory (someone probably ran yarn install here by mistake)
Run formatter for Makefile

I'd also like to do another PR to update versioning and dependency management using this approach after this one.


Async support

Hi there!
First of all: Thanks for this little gem! It's been tirelessly sending around messages for me for years now without any complaints :)
In noticed that pretty much all my message listeners are actually containing async code and return Promises, which will cause them to run in parallel and potentially also cause unhandled promise exceptions in case anything goes wrong. Since I wanted neither of those, I simply created an overload to mitt's emit:
emitAndAwait simply awaits every handler that returns a Promise, and then continues with the next one, thus ensuring sequential execution. Also, if a Promise failed (which it really shouldn't for a pub/sub subscriber), this would propagate properly to the caller.
        async emitAndAwait<T = any>(type: EventType, evt: T) : Promise<void> {
            const handlers = ((all.get(type) || []) as EventHandlerList).slice();
            const wildCardHandlers = ((all.get('*') || []) as WildCardEventHandlerList).slice()

            for (const handler of handlers) {
                // don't do Promise.all, but handle events one by one
                // if it's not actually a promise, await will just immediately continue
                await handler(evt);
            }

            for (const handler of wildCardHandlers) {
                await handler(type, evt);
            }
        }

Since this is returns a Promise too, it can be simply awaited by the caller:
await this.emitter.emitAndAwait("foo", fooMessage);

This has become my go-to replacement for all my mitt calls. Would that maybe make sense in the library itself?

Hey! I found this code searching in the repository. How do you integrate it with mitt?

Hi there
I would love to see this as part of the library  (FYI @developit), but for now, I just copied to source code of mitt into my project, and added the method above.

Asynchrony is expensive when unused, so this couldn't feasibly be landed in Mitt itself. However you can implement it as an addon:
import mitt from 'mitt';

export function mittAsync(all) {
  const inst = mitt(all);
  inst.emitAsync = emitAsync;
  return inst;
}

async function emitAsync(type, e) {
  let handlers = this.all.get(type);
  if (handlers) for (const f of handlers) await f(e);
  let handlers = this.all.get('*');
  if (handlers) for (const f of handlers) await f(type, e);
}

// usage:
const events = mittWithAsync();
events.on('get', async url => fetch(url).then(r=>r.json()));
await events.emit('get', '/foo.json');

I come from https://github.com/EventEmitter2/EventEmitter2 and I was looking for this feature, I would like to see this built-in but I understand the inconvenients. Thanks for the workaround @developit and this gold project 🥇

Does anyone have a workin codesandbox/jsfiddle example with the provided workaround? I cannot seem to make it work.

@dekadentno I have tested it. It works, but you have to modify a little bit.
Credit to @developit
<script src="https://unpkg.com/mitt/dist/mitt.umd.js"></script>

const sleep = (ms) => {
  return new Promise(resolve => setTimeout(resolve, ms));
}

const mittAsync = (all) => {
  const inst = mitt(all);

  inst.emitAsync = async function (type, e){
    let handlers = this.all.get(type);
    if (handlers) for (const f of handlers) await f(e);

    let handlers2 = this.all.get('*');
    if (handlers2) for (const f of handlers2) await f(type, e);
  };

  return inst;
}

const evt = mittAsync();

evt.on('foo', async (e) => {
	await sleep(2000);
	console.log('foo', e);
});

const test = async () => {
	await evt.emitAsync('foo', { a: 'b' });
  await console.log('test');
}

test();

You can test it here https://jsfiddle.net/tr2myfwk/

Moved to #157.


Cleanup / harmonize the client user-agents in the Syncer code

We should cleanup / harmonize the names of client-go user-agents used in the Syncer code.
It seems that they were defined at various times in the code history, and we miss a common pattern and naming consistency.
Main constraint: have one common prefix named after the binary for easy filtering in e.g. audit

cc @sttts

/transfer-issue contrib-tmc


Remove tools:ignore for allowsBackup

@joeatwork sorry to trouble you again. can you please let us know why we added AllowBackup?

@yinfeiru I believe lint was complaining. I'd rather have lint throw a warning (there are many lint warnings currently) than affect existing customers. We probably want to be able to merge manifests in the future.

merge it!


Do not apply ObjectMetadata#contentLength for UploadPartRequest. …

…(#1248)
:loudspeaker: Type of change

[x] Bugfix
[ ] New feature
[ ] Enhancement
[ ] Refactoring

:scroll: Description
Fixes #1248

:bulb: Motivation and Context

:green_heart: How did you test it?
Created new integration and unit test.
:pencil: Checklist

[x] I reviewed submitted code
[x] I added tests to verify changes
[ ] I updated reference documentation to reflect the change
[ ] All tests passing
[x] No breaking changes

:crystal_ball: Next steps

Thank you @Mobe91!


Release fixture renaming

It would be great to modify the naming of the fixtures to include the version number. E.g. fixtures-0.2.4.tar.gz

I think this would make it impossible to always fetch the latest version of the fixtures.
In the CI you can access a specific version like so: https://github.com/ethereum/execution-spec-tests/releases/download/v/fixtures.tar.gz

We can get the latest release using the GitHub API without knowing the name from assets['browser_download_url']  within the json (or get the name of the downloads etc) here:
https://api.github.com/repos/ethereum/execution-spec-tests/releases/latest


Document Enterprise FIPS build

Issue description
We will be releasing a new build of Enterprise that have compatibility with FIPS standards. Specifically, the Enterprise FIPS build is uses FIPS 140-2 compliant cryptography libraries. Note that Enterprise itself is not "certified" as FIPS compliant, but can help companies who need to be FIPS compliant reach that designation.

Good reference docs: https://docs.oracle.com/database/121/DBSEG/asoappe.htm#DBSEG1041
Another example to possibly borrow ideas from: https://www.mongodb.com/docs/manual/tutorial/configure-fips/

Additional links
Github epic: https://github.com/orgs/influxdata/projects/68/views/1?filterQuery=epic%3AFIPS
What product(s) and version(s) does this apply to?
InfluxDB Enterprise 1.11 FIPS build
Link(s) to documentation that needs to be changed
https://docs.influxdata.com/enterprise_influxdb/v1.11/
What needs to be added or updated?
For FIPS documentation, we would like to have a section very similar to Hashicorp's FIPS documentation.

Additional info from @gwossum below.
FIPS build limitations:

Direct upgrade path from non-FIPS to FIPS is not currently supported (related to password hashing)
Flux does not support mssql / sqlserver or snowflake databases in from() and to()
TLS uses a restricted set of functionality (mandated by FIPS):

TLS 1.2 only
TLS only supports the following cipher suites:

ECDHE_RSA_WITH_AES_128_GCM_SHA256
ECDHE_RSA_WITH_AES_256_GCM_SHA384,
ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
RSA_WITH_AES_128_GCM_SHA256
RSA_WITH_AES_256_GCM_SHA384

Restrictions on digital signatures supported (mandated by FIPS). This impacts TLS certificates. The following signatures are supported:

PSSWithSHA256
PSSWithSHA384
PSSWithSHA512
PKCS1WithSHA256
ECDSAWithP256AndSHA256
PKCS1WithSHA384
ECDSAWithP384AndSHA384
PKCS1WithSHA512
ECDSAWithP521AndSHA512

Restrictions on RSA key size (manded by FIPS). This impacts TLS certificates. The following RSA key sizes are supported:

2048
3072

Restrictions on EC curves supported (mandated by FIPS). This impacts TLS certificates. The following EC curves are supported:

P-256
P-384
P-521

If you start with a fresh install without a config file that sets the password hash, it will default to a FIPS-compliant password hash that conforms to NIST SP 800 and OWASP guidelines. In fact, it will not let you configure a non-FIPS password hash. It will crash out on startup if you specify something like bcrypt.


Add  element

Spec: https://html.spec.whatwg.org/multipage/text-level-semantics.html#the-data-element
https://www.chromestatus.com/feature/5701891585474560: Chrome 62+, Opera 49+
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/data

If this is a duplicate or even exists already, <data> or at least data element should find this I believe :)

Exists now via MDN https://caniuse.com/#feat=mdn-html_elements_data but is still not that easy findable.

Seems to be easily findable now:
https://caniuse.com/?search=data
https://caniuse.com/?search=<data>
https://caniuse.com/?search=data element
(MDN data via mdn/browser-compat-data#358)

Closing as per above.


fix(knative): Integration in error state when knative SinkBinding mode=inclusion

https://github.com/apache/camel-k/issues/4119
Release Note
knative trait sets `bindings.knative.dev/include=true` label to the namespace when there is a SinkBinding.

I remember that we have already fixed something regarding namespace labelling for Knative sink binding injection in the past. Do you know why this came back as a regression?

It was fixed only on 1.8 downstream at the time.

Can we merge it ?


Negative margins is a bit buggy

Awesome little tool.
The only issue I found with it is that sometimes it doesn't seem to handle negative margins well.
When I drag one of the margin handles in the negative direction and let go of the cursor, there are times when the margin won't be draggable anymore. And sometimes when it is draggable, if you drag it even just a little bit, it jumps back to zero.
https://user-images.githubusercontent.com/34774629/125170960-e86f4780-e1b1-11eb-813b-36192feb6c70.mov

@csabaxyz thanks for pointing out the issue.
Let me fix this and will update you for sure.
Thanks again.

Hey @csabaxyz
This bug has been fixed. Thank you for reporting.


Dedicated Information about significant weather

At the moment, information about significant weather, e.g. hot/cold, stormy, rainy days, are only recognizable by the corresponding key words within the forecast, e.g. {frosty, cold, normal, summer, hot} as a description for temperature related significant weather.
A new parameter should be available that adds the concrete significant weather attributes to the forecast by showing them as a new text block within the forecast. For example: the forecast can finish with the information:

Significant weather: cold (temperature below 0°C during the day), stormy (max. wind speed greater than 28 m/s), heavy rains (more than 25 mm within one hour).

Done with #13.
Added new parameter that leads to an additional sections with the warnings for the current forecast.


Using service accounts?

when I tried to use the builder, I realized that the script used rclone to authenticate google account, and the script contains some things like client id, client secret, refresh token, etc.
Is it possible to use SA? Just wondering if it is possible to kind of break the gdrive limit when downloading/uploading from the index.

I don't kniw


Report: Local TDO Attendance Summary

Show breakdown of TDO attendance by T1/T2/Total

Pull request #124


Update .repoman.yml

Add config setting for regex that parses the page URL from the new docs issue template
Remove old breaking changes rule; the other one defined in the config handles it now
Add rule for new action that detects the product/tech metadata and adds the labels

@adegeo Are you going to update the dotnet/aspnetcore.docs  .repoman.yml file too?


Crash on unsubscribe from topic after ERROR is received

When socket error is reported and we try to unsubscribe from the topic, IllegalStateException will be thrown as shown below:
    @NonNull
    @Override
    public Completable send(String stompMessage) {
        return Completable.fromCallable(() -> {
            if (getSocket() == null) {
                throw new IllegalStateException("Not connected yet");
            } else {
                Log.d(TAG, "Send STOMP message: " + stompMessage);
                rawSend(stompMessage);
                return null;
            }
        });
    }

Could we maybe just check when unsubscribing if actual event should be sent based on sockets state?

I'll look into this more later today. Thanks for the report :)

Would you mind if I just create a quick fix to check if a connection is still live before trying to send unsubscribe event? Other possible quick solution would be to just log an attempt to send a message when the connection is closed instead of crashing the app.

Hi! Sorry, I just got back from a vacation in Mexico :) sorry to keep you waiting!
I'll resume work on this today or tomorrow, but yeah, if you make a working fix then I'll totally look into that.

Glad to hear that you are back! Regarding the issue, I don't see a decent fix without exposing provider details. Would you mind if we just don't throw runtime exception on sending unsubscribe event?


ground items plugin: add loot beams

picture for a blog: https://i.imgur.com/Yb9VyJY.png
gif for a blog: https://i.imgur.com/8QqQVO8.gif
Requires !92
new gif with colors
https://i.imgur.com/GIhE9IZ.gif

Code LGTM otherwise.

Has this been forgotten? Would love to see this!

Has this been forgotten? Would love to see this!

updated to use a new RuneliteObject api which is also included in this PR
it also uses DBs suggestion and has colors now
new gif https://i.imgur.com/GIhE9IZ.gif


Per-Server Send Limit

Hello,
Most experienced guys, your assistance please.
Mailserver -> Settings -> Send Limit -> unlimited e-mails every 60 minutes*
This is the default setting.
When on earth is the configuration page for adjusting this limit?
Do i need to edit this via ssh? or directly on a db table?

Hello, @willpower232
I have also faced the issue with sending limit but I need monthly limit this hourly limit.
So how can I apply monthly limit?
Thank You

Please see #361


RHBPMS-4365 - Scripts get reformatted after editing process causing c…

…ompile error

Tested and looks good.
+1


BUG:src/hir_typeck/common.cpp:751: Impl parameters were not expected (got T/I:0/)

Code
#![crate_type = "lib"]
struct Assert<const COND: bool>;
trait IsTrue {}
impl IsTrue for Assert<true> {}
trait IsNotZst {}
impl<T> IsNotZst for T
where
    Assert<{ std::mem::size_of::<T>() > 0 }>: IsTrue,
{}
fn assert_not_zero_sized<T: IsNotZst>(_: T) {}
fn main() {
    assert_not_zero_sized(vec![]);
}

Output
The error message I received is: ":0:0 BUG: src/hir_typeck/common.cpp:751: Impl parameters were not expected (got T/I:0/)".
I found that when I remove the first line, the compiler could output the correct error message🤣
Setup: V V V
(0.00 s) Setup: DONE
Target Load: V V V
(0.00 s) Target Load: DONE
Parse: V V V
(0.00 s) Parse: DONE
LoadCrates: V V V
(0.39 s) LoadCrates: DONE
Expand: V V V
(0.00 s) Expand: DONE
- main: params.outfile = lib3.rlib
Implicit Crates: V V V
(0.00 s) Implicit Crates: DONE
Resolve Use: V V V
(0.00 s) Resolve Use: DONE
Resolve Index: V V V
(0.00 s) Resolve Index: DONE
Resolve Absolute: V V V
(0.00 s) Resolve Absolute: DONE
HIR Lower: V V V
(0.00 s) HIR Lower: DONE
Lifetime Elision: V V V
(0.00 s) Lifetime Elision: DONE
Resolve Type Aliases: V V V
(0.00 s) Resolve Type Aliases: DONE
Resolve Bind: V V V
(0.10 s) Resolve Bind: DONE
Resolve UFCS Outer: V V V
(0.00 s) Resolve UFCS Outer: DONE
Resolve HIR Self Type: V V V
(0.00 s) Resolve HIR Self Type: DONE
Resolve HIR Markings: V V V
(0.00 s) Resolve HIR Markings: DONE
Sort Impls: V V V
(0.01 s) Sort Impls: DONE
Resolve UFCS paths: V V V
(0.00 s) Resolve UFCS paths: DONE
Constant Evaluate: V V V
:0:0 BUG:src/hir_typeck/common.cpp:751: Impl parameters were not expected (got T/*I:0*/)
Aborted (core dumped)

If remove the first line of the code:
Implicit Crates: V V V
:0:0 warn:0:Multiple panic_runtime crates loaded - panic_abort-0_0_0 and panic_unwind-0_0_0
:0:0 error:0:Unable to locate crate 'alloc_system' in search directories
Aborted (core dumped)

The std::mem::size_of::<T>() > 0 is the cause of the issue, constant evaluation isn't correctly propagating the generic parameter through to the expansion/evaluation of that expression.

It's an ICE because the generic type was copied to a scope with no generics.
I'll address the issue when I get time.

Not valid with rustc (1.81.0). I'll fix the ICE, but won't work on making it compile.
tpg@gaige$ rustc samples/test/mrustc-322.rs
error: generic parameters may not be used in const operations
 --> samples/test/mrustc-322.rs:8:34
  |
8 |     Assert<{ std::mem::size_of::<T>() > 0 }>: IsTrue,
  |                                  ^ cannot perform const operation using `T`
  |
  = note: type parameters may not be used in const expressions

error: aborting due to 1 previous error


Temporarily disable the format linter

Disable it temporarily (but keep other linter checks) until https://github.com/golang/go/issues/28200 is fixed.
This is to avoid non-format errors for piling up while the lint test is not required.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: mandarjog
If they are not already assigned, you can assign the PR to them by writing /assign @mandarjog in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

bin/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/assign @sdake

cc @hklai

@ymesika: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
b80b1d1ee88d3fae2d75058ee15dfea9a01a39c1
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Since there is no accurate time when https://github.com/golang/go/issues/28200 can be fixed. And during these time, should not introduce other failure.
After this should make lint required.
/lgtm

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: hzxuzhonghu
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: sdake
If they are not already assigned, you can assign the PR to them by writing /assign @sdake in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

bin/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/test istio-unit-tests

Looks like there are some license related errors. Could you help resolve them in the same PR?

@hklai The errors were already fixed in #9423

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: hzxuzhonghu
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers: costinm, nmittler, wattli
If they are not already assigned, you can assign the PR to them by writing /assign @costinm @nmittler @wattli in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

bin/OWNERS
galley/OWNERS
istioctl/OWNERS
pilot/OWNERS [hzxuzhonghu]
pkg/OWNERS
security/OWNERS
tests/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: hzxuzhonghu
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: rshriram
If they are not already assigned, you can assign the PR to them by writing /assign @rshriram in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ymesika: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
58c1e3898620051f0d7778ac3833626c67197b02
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-unit-tests

@quanjielin Yes, you had dead code referencing that vendor code.
If you put it back can you please make sure the lint test pass?

I added placeholder in security/pkg/nodeagent/plugin/providers/google/iamclient.go refers to that pkg, which you comment it out...
is there any lint test fail ? https://github.com/istio/istio/pull/9420 presubmit pass for me.

Yes, I preferred to comment it out because if you uncomment the CircleCI lint test will fail gomeatlinter complaining about deadcode.
You can uncomment my comments, add the vendor and see if the lint test pass.

by running lint test you mean make lint  ?

Yep. Or just run bin/linters.sh. Same.


setup the is error

Issue
Expected Behavior
hexo 3.9
next 7
Actual Behavior
Steps to Reproduce the Problem

_ install the result error.

Specifications

(The version of the project, operating system, hardware etc.)

Can you show the tags part in your blog?
Seems that your tags part is not an array.
Hexo can parse the header like below, but this plugin only supports array.
---
title: Test.md
date: 2019-11-03 13:57:49
tags: FFF
---

Change to:
---
title: Test.md
date: 2019-11-03 13:57:49
tags:
    - FFF
---

Can you show the tags part in your blog?
Seems that your tags part is not an array.
Hexo can parse the header like below, but this plugin only supports array so far.
---
title: Test.md
date: 2019-11-03 13:57:49
tags: FFF
---

Change to:
---
title: Test.md
date: 2019-11-03 13:57:49
tags:
    - FFF
---

Will fix in next version.

@MikeCoder  This is what I set up before installing this plug-in,And I'm having a problem installing this plug-in, not deploying and publishing it

Weird, I can't reproduce this on my computer,  it shouldn't run the plugin when installing.
Also, you can install the plugin manually.

go to node_modules folder, and run git clone https://github.com/MikeCoder/hexo-blog-encrypt.git
add  "hexo-blog-encrypt": "^3.0.3", to package.json

Then, add console.log to node_modules/hexo-blog-encrypt/index.js line 39, like:
  if (data.tags) {
    // add log here to find out which blog is wrong.
    console.log(data);
    console.log(data.tags);
    data.tags.forEach((cTag, index) => {
      if(tagEncryptName.includes(cTag.name)){
        password = password || tagEncryptPass[index];
      }
    });
  }

It may help.

Weird, I can't reproduce this on my computer, it shouldn't run the plugin when installing.
Also, you can install the plugin manually.

go to node_modules folder, and run git clone https://github.com/MikeCoder/hexo-blog-encrypt.git
add  "hexo-blog-encrypt": "^3.0.3", to package.json

Then, add console.log to node_modules/hexo-blog-encrypt/index.js line 39, like:
  if (data.tags) {
    // add log here to find out which blog is wrong.
    console.log(data);
    console.log(data.tags);
    data.tags.forEach((cTag, index) => {
      if(tagEncryptName.includes(cTag.name)){
        password = password || tagEncryptPass[index];
      }
    });
  }

It may help.

I think you should test this problem,ths @MikeCoder

For bugs that occur in a specific scenario, debug requires corresponding scenario information. As a developer, you should also be clear that if I can't reproduce it then I can't solve it.
BTW, this is not commercial software.


First implementation KL loss

Codecov Report

Merging #3 (2d381d2) into master (5c081dc) will not change coverage.
The diff coverage is 0.00%.


Lab 4.2 Task 4 Remove Rating and Source Column

Module: 04
Lab: 4.2
Task: 4
Step: 00
Description of issue
I experienced error if I fill the Rating and Source Column in the Feedback Form.
Is it not better to remove the Rating and Source Column in the Feedback Form?

MOC Labs Review has resolved this issue with pull request #65


[Feature Request] return "number of inserted rows" metric on spark df.write operation

Feature request
Overview
When inserting rows via spark df.write operation into a Delta Lake table it would be helpful if number of inserted rows (Long) would be returned.
Motivation
We are currently building a data lakehouse facilitating Delta Lake as storage format. Ingested raw data are processed and curated through multiple layers (bronze/silver/gold).
In order to maintain some kind of data lineage and processing audit as well as ensuring data quality / completeness, it is important to log how many rows were inserted/deleted/updated when new data is processed from on layer to another.
Delta Lake API DELETE operations already returns metrics, and metrics for operations UPDATE and MERGE are in development (see https://github.com/delta-io/delta/issues/1321 and https://github.com/delta-io/delta/issues/1322). Basically metrics for plain INSERTS/writes/appends is the last missing puzzle piece.
Currently df.write doesn't return any metrics. Our workaround is to analyze the commit info from the Delta Logs in a separate post-processing step and extract the metric from it.
Further details
Delta Log version looks like this; we are interested in attribute commitInfo.operationMetrics.numOutputRows
{
  "commitInfo": {
    "timestamp":<PHONE_NUMBER>417,
    "operation": "WRITE",
    "operationParameters": {
      "mode": "Append",
      "partitionBy": "[]"
    },
    "readVersion": 317,
    "isBlindAppend": true,
    "operationMetrics": {
      "numFiles": "1",
      "numOutputBytes": "2147041",
      "numOutputRows": "2986"
    }
  }
}

Our workaround for retrieving the number of written rows looks like this:
written_rows_count = int(deltaTable.history(1).select(F.col('operationMetrics')).collect()[0]['operationMetrics']['numOutputRows'])

Disclaimer
I'm not sure if my request is technically in scope of Delta Lake OSS since it is closely related to Apache Spark.
If it is not, I'd like to open the discussion if it would make sense to add an INSERT operation to Delta Lake API that can be used instead of df.write and the provides the desired metric.
Willingness to contribute
The Delta Lake Community encourages new feature contributions. Would you or another member of your organization be willing to contribute an implementation of this feature?

[ ] Yes. I can contribute this feature independently.
[ ] Yes. I would be willing to contribute this feature with guidance from the Delta Lake community.
[x] No. I cannot contribute this feature at this time.

I certainly like the idea to also have an insert statement being available in delta lake. This would make my pipelines much more convenient as it would reduce boilerplate code

@TarekSalha Delta Lake does support INSERT INTO using Spark SQL as documented here.
@keen85 thanks for posting this issue. A change to the return value of df.write API would have to happen in Spark, not Delta, so we'll close this issue.

Hi @nkarpov,
What about adding an DeltaTable.insert(df) operation to the Delta Lake API?

That's a good point. Re-opening this in case someone wants to work on this.


write scaladoc for json module

Currently, there is a fairly good README for the json module, but scaladoc is lacking. The document should point out some key design decisions like:

[x] the use of io.circe.generic.extras instead of io.circe.generic
[x] why it essentially creates a "soup" of circe instead of keeping its modular strucutre
[x] important references, and ways future problems could be tackled.

closed with 0.2.0-RC1


add load test pipeline to nightly job

Reason for Change:

Updates the current CI pipeline to use templates
Adds lint as part of CI

Requirements

[x] squashed commits
[ ] included documentation
[x] added unit tests and e2e tests (if applicable).

Issue Fixed:

Please answer the following questions with yes/no:

Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution?