[xh]Replace openai function call with AI client function

Description
In wizard class, there is openai function call to classify "block_type", "pipeline_type" based on code description.
In this PR, I replaces this openai function with dedicated "find_block_params" in AI client funciton.
So each AI client can implement it. So wizard class becomes fully AI client isolated.
How Has This Been Tested?
Tested with 10 different code description to compare open ai classification response with hugging face classification response: https://docs.google.com/spreadsheets/d/1-fongvJv0lrtNp06wbnDqxmPNp66lCBJ-8TVKuftDds/edit?usp=sharing
Tested with Mage UI
Generate block with code description:

Generate pipeline with description:

Checklist

[X] The PR is tagged with proper labels (bug, enhancement, feature, documentation)
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas

cc:
@wangxiaoyou1993

You can rebase master branch to fix the CI failure

👍👍Fixed the CI! Thank you @wangxiaoyou1993

@wangxiaoyou1993 Updated the PR following comments and also tested with Mage UI.
The hugging face client functionally works by generating blocks and pipeline. But I look into the actual code it generated, the accuracy is something we can improve in the next step.


Crashes when indexing LLVM

There are a few different failure modes:

An assertion is being hit inside Clang itself. Need to double-check if this also hits with ToT Clang.
Sometimes, the callback for getting the index details is not being called. It's unclear how this is possible 🤔
There are timeouts. We should increase the timeout limit for sanitizers builds, and implement #45.

Assertion failed: (!VD->mightBeUsableInConstantExpressions(Info.Ctx)), function evaluateVarDeclInit, file ExprConstant.cpp, line 3327.
Assertion failed: (!VD->mightBeUsableInConstantExpressions(Info.Ctx)), function evaluateVarDeclInit, file ExprConstant.cpp, line 3327.
[09:49:01 info] driver    : killing worker 6, pid 48512
[09:49:01 warning] driver    : skipping job 1165.0 due to worker timeout
[09:49:01 info] driver    : the worker was running semantic analysis for '/Users/varun/Code/llvm-under-test/llvm/lib/ObjCopy/MachO/MachOWriter.cpp'
[09:49:02 info] driver    : killing worker 8, pid 48549
[09:49:02 warning] driver    : skipping job 1166.0 due to worker timeout
[09:49:02 info] driver    : the worker was running semantic analysis for '/Users/varun/Code/llvm-under-test/llvm/lib/ObjCopy/MachO/MachOLayoutBuilder.cpp'
[09:56:00 error] worker 4  : Exception::raise(): indexer/Worker.cc:1062 enforced condition callbackInvoked == 1 has failed: callbackInvoked = 0 for TU with main file '/Users/varun/Code/llvm-under-test/build/tools/clang/tools/extra/clangd/CompletionModel.cpp'

[09:56:01 error] worker 4  : Backtrace:
clang::ASTNodeTraverser<clang::JSONDumper, clang::JSONNodeDumper>::Visit(clang::CXXCtorInitializer const*) (in scip-clang) + 116
void clang::NodeStreamer::AddChild<void clang::JSONDumper::writeTemplateDeclSpecialization<clang::ClassTemplateSpecializationDecl>(clang::ClassTemplateSpecializationDecl const*, bool, bool)::'lambda'()>(llvm::StringRef, clang::ClassTemplateSpecializationDecl) (in scip-clang) + 420
void clang::NodeStreamer::AddChild<void clang::JSONDumper::writeTemplateDeclSpecialization<clang::ClassTemplateSpecializationDecl>(clang::ClassTemplateSpecializationDecl const*, bool, bool)::'lambda'()>(llvm::StringRef, clang::ClassTemplateSpecializationDecl) (in scip-clang) + 1464
clang::edit::EditedSource::commitInsert(clang::SourceLocation, clang::edit::FileOffset, llvm::StringRef, bool) (in scip-clang) + 752
start (in dyld) + 2544

[09:56:50 error] worker 6  : Exception::raise(): indexer/Worker.cc:1062 enforced condition callbackInvoked == 1 has failed: callbackInvoked = 0 for TU with main file '/Users/varun/Code/llvm-under-test/build/tools/clang/tools/extra/clangd/unittests/DecisionForestRuntimeTest.cpp'

[09:56:50 error] worker 6  : Backtrace:
scip_clang::Worker::processTranslationUnitAndRespond(scip_clang::IndexJobRequest&&) (in scip-clang) + 2428
scip_clang::Worker::run() (in scip-clang) + 712
scip_clang::workerMain(scip_clang::CliOptions&&) (in scip-clang) + 392
main (in scip-clang) (main.cc:0)
start (in dyld) + 2544

[09:58:00 info] driver    : killing worker 4, pid 48473
[09:58:00 warning] driver    : skipping job 3098.0 due to worker timeout
[09:58:00 info] driver    : the worker was running semantic analysis for '/Users/varun/Code/llvm-under-test/build/tools/clang/tools/extra/clangd/CompletionModel.cpp'
[09:58:50 info] driver    : killing worker 6, pid 74126
[09:58:50 warning] driver    : skipping job 3237.0 due to worker timeout
[09:58:50 info] driver    : the worker was running semantic analysis for '/Users/varun/Code/llvm-under-test/build/tools/clang/tools/extra/clangd/unittests/DecisionForestRuntimeTest.cpp'

Closing this since some of these are already fixed. Will open more narrow issues if we still run into this.


Do not merge - Add new action: WindowConfirm

[ ] Consider making it a more generic – window.prompt, window.alert, window.confirm ?

@mmiszy @witoszekdev do we still have a use case or it was worked around?


Missing schemes

I try to do a 1D integral along a line and a 2D integral over a rectangular surface. Using the examples provided on the main page I get:
import quadpy

scheme = quadpy.c1.gauss_patterson(5)
scheme.show()

results in: AttributeError: module 'quadpy' has no attribute 'c1'
and similar for the rectangular integration:
import quadpy

scheme = quadpy.c2.stroud_c2_7_2()
scheme.show()

results in: AttributeError: module 'quadpy' has no attribute 'c2'
Is this the same issue as https://github.com/nschloe/quadpy/issues/204 ? If this is the case, could you please release these schemes also? Or am I doing something wrong?

Probably an outdated version of quadpy.
On Sat, Jun 27, 2020, 10:14 AM drtrigon<EMAIL_ADDRESS>wrote:

I try to do a 1D integral along a line and a 2D integral over a
rectangular surface. Using the examples provided on the main page
https://github.com/nschloe/quadpy I get:
import quadpy
scheme = quadpy.c1.gauss_patterson(5)
scheme.show()
results in: AttributeError: module 'quadpy' has no attribute 'c1'
and similar for the rectangular integration:
import quadpy
scheme = quadpy.c2.stroud_c2_7_2()
scheme.show()
results in: AttributeError: module 'quadpy' has no attribute 'c2'
Is this the same issue as #204
https://github.com/nschloe/quadpy/issues/204 ? If this is the case,
could you please release these schemes also? Or am I doing something wrong?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nschloe/quadpy/issues/317, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABMK7BFX3TQWMWFJ7723JDRYWS5FANCNFSM4OJ5RG4A
.

Installed using pip may be 1 or 2 weeks ago...?
How to check the version? How to install the most recent one?

import quadpy
print(quadpy.__version__)

@drtrigon I got the same issue when using the PyPi version, but it goes away when I try to install the GitHub version by pip install git+https://github.com/nschloe/quadpy.git and the version is also 0.14.11.
>>> import quadpy
>>> quadpy.__version__
'0.14.11'
>>> dir(quadpy)
['__about__', '__all__', '__builtins__', '__cached__', '__doc__', '__file__', '__loader__', '__name__', '__package__', '__path__', '__spec__', '__version__', '_scipy_compat', 'c1', 'c2', 'c3', 'cn', 'e1r', 'e1r2', 'e2r', 'e2r2', 'e3r', 'e3r2', 'enr', 'enr2', 'helpers', 'p3', 'quad', 's2', 's3', 'sn', 't2', 't3', 'tn', 'tools', 'u2', 'u3', 'un', 'w3']

Thanks a lot to @zhucaoxiang - that was the problem!
As I had quadpy installed from PyPi already I had first to uninstall (otherwise it download, builds but does not install):
$ pip3 uninstall quadpy
$ pip3 install git+https://github.com/nschloe/quadpy.git

So the deployment to PyPi is the problem. For me this solution is good enough thus I'll close the issue. Feel free to re-open if you want to solve the deployment/PyPi problem also.

I have to re-open this issue - now the spherical coordinates are gone:
scheme = quadpy.sphere.lebedev_019()
scheme.show()

results now in: AttributeError: module 'quadpy' has no attribute 'sphere'
@zhucaoxiang: could you check this also, please?

Just use ipython and  your way through quadpy. You'll find u3.

I find u3 but for spherical coordinates I need sphere, right? (as noted by you in the 2nd example in https://github.com/nschloe/quadpy#sphere-u3)
Furthermore the example given by you for the rectangular (or quadrilateral) scheme does NOT work also: https://github.com/nschloe/quadpy#quadrilateral-c2 It results in: AttributeError: 'list' object has no attribute 'shape'
So I do get the impression the examples are heavily outdated. If you don't care fine - I can find another solution...

I'll do it when I find the time.

Most README snippets are now part of the integration testing, so such hiccups should no longer occur.

Seems to work now - thanks!

Hi, I have the same problem as the OP, I have 0.16.5 and cannot use lebedev scheme. And the link for the installation with git (pip install git+https://github.com/nschloe/quadpy.git) does not work
ERROR: Command errored out with exit status 128: git clone -q https://github.com/nschloe/quadpy.git /private/var/folders/1c/qqdm58sj5mjfk3xjz79fxzph0000gn/T/pip-req-build-gzx1rkmc Check the logs for full command output.
How can I solve it?

Hi, I have the same problem as the OP, I have 0.16.5 and cannot use lebedev scheme. And the link for the installation with git (pip install git+https://github.com/nschloe/quadpy.git) does not work
ERROR: Command errored out with exit status 128: git clone -q https://github.com/nschloe/quadpy.git /private/var/folders/1c/qqdm58sj5mjfk3xjz79fxzph0000gn/T/pip-req-build-gzx1rkmc Check the logs for full command output.
How can I solve it?


'problems' command rework

potentially in an embed + list
shows difficulty for each problem (breakdown?)
link to each submission (hyperlinked)

Overall vision, something like:
<-Start of embed block->
Problems Completed
Two Sum
Add Two Numbers
Maybe highlight each problem name with different colors based on difficulty with same colors used as on LeetCode website (light green -> Easy, yellow -> Medium, red -> Hard)


Performance Issues:

Version
v0.0.0
(installing 0.6.7 to test)
Bug
Opening an issues separate from the wedging issue documented elsewhere.
Running HASS on RPi 4B 4GB ram and booting from SSD. 4 addons (really basic stuff), processor sits at about 5% usually and ram usually at around 25%.
Turning on Bermuda leads to immediate slow down of the whole system. Bluetooth Proxies are running just fine, all added to areas, and seem to have very minimal impact on the system when Bermuda isn't running.
Logs have been sent via email.
Originally posted by @agittins in https://github.com/agittins/bermuda/issues/199#issuecomment-2220097804

I'll just leave the link here - logs
I've resent the email and made sure I had the address right so hopefully you get it there too, but it should be fine I think.

Great, got it, thanks!
OK, so for some reason Bermuda is seeing/creating tens of thousands of bluetooth devices, and I think that's causing it to bog down.
The following is partly me just working through the problem and taking notes as I go, if it's all a bit much to take in, just skip down to the "Next Steps" heading :-)
Of the bluetooth scanners that show up in the logs, this is how many updates we get from each one:
      2 0C:8B:95:A8:2D:B4
     12 DC:A6:32:A4:81:91
     30 4C:75:25:C4:51:C0
      5 4C:75:25:C6:80:9C
      5 4C:75:25:C6:80:BC
   6601 8e53deb259378073498fd5d4439ff7c4
  22710 21821ec872bdd98bf04545f692c4d0b8
  35416 158392aa5806da6fef042630ed5e3a0d

The ones that are MAC addresses look normal, and shows a fairly "typical" amount of traffic. Those last three are... something else! They are sending thousands on thousands of BluetoothChange.ADVERT events. This is almost certainly what's causing the bog down, and causing the log to be so big.
On top of the log volumes, it also means that there are a lot (like, a LOT a lot!) of devices stored in the backend's bluetooth advert logs. This will be taking up a bit of memory, but it seems it's perhaps not causing any issues except when Bermuda is trying to process the data.
These log entries:
2024-07-01 18:58:56.712 INFO (MainThread) [custom_components.bermuda] Having to prune 63830 extra devices to make quota.
2024-07-01 19:04:07.028 INFO (MainThread) [custom_components.bermuda] Having to prune 63837 extra devices to make quota.
2024-07-01 19:09:19.985 INFO (MainThread) [custom_components.bermuda] Having to prune 63834 extra devices to make quota.
2024-07-02 00:31:37.332 INFO (MainThread) [custom_components.bermuda] Having to prune 63858 extra devices to make quota.
2024-07-02 00:45:07.392 INFO (MainThread) [custom_components.bermuda] Having to prune 63890 extra devices to make quota.
2024-07-02 01:11:53.932 INFO (MainThread) [custom_components.bermuda] Having to prune 63864 extra devices to make quota.
2024-07-02 01:32:13.454 INFO (MainThread) [custom_components.bermuda] Having to prune 63897 extra devices to make quota.
2024-07-02 03:01:29.908 INFO (MainThread) [custom_components.bermuda] Having to prune 63888 extra devices to make quota.

Indicate that Bermuda is trimming the number of adverts, and even after discarding the old ones (with old timestamps on them) it still has another 63 thousand it has to purge to keep within the limits (we keep a thousand).
The error happens repeatedly because those integrations keep reporting new devices (or at least, new timestamps on them).
Looking at all the IRK devices it "finds" it seems that there are 11 thousand unique addresses there. I think something might be reporting its historical cache of addresses as new adverts, perhaps. Or something.
At any rate, what Bermuda is receiving is way outside of what it expected, which is why your system is bogging down.
Next Steps
There are two things that would be helpful...
I need to work out which integration(s) are providing those bluetooth scanner services, which HA is identifying as
8e53deb259378073498fd5d4439ff7c4, 21821ec872bdd98bf04545f692c4d0b8, and 158392aa5806da6fef042630ed5e3a0d.
In HA, if you can go to "Developer Tools", "Template" and paste this in:
8e53: {{ config_entry_attr('8e53deb259378073498fd5d4439ff7c4', 'domain') }}: {{ config_entry_attr('8e53deb259378073498fd5d4439ff7c4', 'title') }}

2182: {{ config_entry_attr('21821ec872bdd98bf04545f692c4d0b8', 'domain') }}: {{ config_entry_attr('21821ec872bdd98bf04545f692c4d0b8', 'title') }}

1583: {{ config_entry_attr('158392aa5806da6fef042630ed5e3a0d', 'domain') }}: {{ config_entry_attr('158392aa5806da6fef042630ed5e3a0d', 'title') }}

It should give you a listing on the right with the integration name and config title of each of them. Copy/paste that to here and I can work from there.
That's the most important thing I need right now, as it will tell me which integration is freaking Bermuda out, and I can hopefully try and replicate the issue here.
As a secondary objective 😄, if you have the Bluetooth integration visible, can you download diagnostics from that for me? In "Settings", "Devices and Services", "Bluetooth", click the meatball next to CONFIGURE and choose Download Diagnostics. It will look a bit like:

(note this is in the Bluetooth integration, not Bermuda).
I received your last email, so you can again upload it and send me the link via email, if that works for you.
Thanks for your time with this!

Hi @agittins ! It's grumpy guy from https://github.com/agittins/bermuda/issues/199
I decided to give another shot to Bermuda.
So here's info you're asking for:

config_entry-bermuda-01J4A5YEKP8F7F5JHBS9G5FBXM.json
Right now installed to 2 ESP devices and also HA has its own bluetooth adapter.
6 beacons added.
Didn't notice performance drop so far, except strange 20-sec hiccup for the time that diagnostics was gathered. I already thought it's freezing again, but it came back.

I will hold it on 2 scanner nodes for couple days, will see how it works.

Sorry it's been such a long time since I've responded, @agittins... Initially went to try and find the source of those BLE readings in setup and was just getting nulls when I both the template you provided and when I tried searching through other areas. I think I narrowed it down to either the Passive BLE HACS component or the BTHome Integration as I was using some of the xiaomi ble temp/humiditiy sensors. Scrapped those for now and swapped back to some sonoff zigbee ones and removed both of those integrations (plus the tractive ble pet tracker integration, but I'd be surprised if that was part of the problem) and I'm not getting the ridiculous logs that I was seeing before. Seeing something much more reasonable now, though still having issues with performance drop. Most notably when it comes to firing events or calling services from the front end. The best example of this is when using a Roku Remote card in lovelace it's pretty instantaneous when Bermuda isn't enabled - very much akin to just using a regular remote or the Roku app. Turning Bermuda on immediately adds a 1-3 second delay to all remote actions I call.
Not sure if any of that is helpful, and happy to provide more info for troubleshooting if you like, but just thought I'd come back with what I found finally.
Regardless, it works really really well to accomplish it's goal. Easiest room tracker I've used to date by far! With the added bonus of BLE proxies everywhere!

Cheers Jack, all good. Life gets in the way :-)
That's interesting that the template didn't work, maybe the id isn't a valid config entry, or maybe I got something wrong in the template.
Glad you have your system up and running, but sorry that your still having some performance/lag issues. I'd like to get to the bottom of it as it's probably something that others will continue to run into, and might point to something silly I'm doing that can be fixed :-) . I'm happy to work on this with you as long as you are, and no worries about delays etc.
I think to get a fresh start on looking  into this, what would really help is:

a download diagnostics from your current system. Note that this can take a bit of time to generate, as it scrubs the results to anonymise the mac addresses etc. The longer your system has been "up" the longer this will probably take, as it will have a lot more MAC addresses cached - so doing it after a fresh boot might work quicker.
30 seconds of debug logs. This is mainly so I can see how long each processing loop takes for Bermuda to complete, and if it's maybe doing something silly like reloading the device registry or something too often.

Feel free to email the log if you'd rather not post publically (oh and feel free to remove your old log from proton), the diagnostic download should be fairly safe to share, depending on your personal privacy boundaries.
Some things I am thinking that could be going on are:

lots of devices enabled, or a short update_interval, causing lots of state machine changes (directly impacts the frontend) and/or database writes
an unexpectedly large number of source devices being reported, slowing things down
Bermuda doing something unexpected.

Anyway if you are able to shoot me a diags and a debug log I can take a look from there, and the above might give you some ideas if you decide to do some more digging on top of that.

Regardless, it works really really well to accomplish it's goal. Easiest room tracker I've used to date by far! With the added bonus of BLE proxies everywhere!

Awesome, that's great to hear! 😀

@agittins I have Performance issue w/ Bermuda as well, not sure if I narrowed down the cause, but I tried to track iBeacon provided by HA Companion and added hass_Bluetooth_Proxy w/ its Companion on a stationary Android Tablet. Will try to dig deeper and find out what exactly bogs my system down in the coming days.
Should I post separate issue, or hijacking this one would be ok?

@myroslav sorry for the delay in my reply, I've been away and without solid internet for a while.
Sticking with this issue might be good for now, since I suspect there might be a common thread. The other integration you mention is very interesting, it could certainly be having an affect if it creates bluetooth entries in the HA backend that might be in a format Bermuda is not expecting.
If you're able to submit the output from a "download diagnostics" that might be really helpful, and I'll have a look at the hass_bluetooth_proxy integration when I can, too.
@jack3308 how have things been going with Bermuda for you? If you're still seeing slow-downs then a diagnostics might be helpful. Another thing is to check how many sensors you have enabled - Bermuda creates a lot of diagnostics sensors in a "disabled" state (like "distance to [proxy]" and "unfiltered distance to [proxy]"). If you have many of those enabled that will create a lot of memory use for the browser, making the front-end a bit heavy and slow, and will also result in a lot of database writes, making the backend slow.

Yea, I'd enabled the distance and one other sensor (can't quite remember which). But compared to the other things I'd had enabled it should have been negligible - even with the frequency of updates.
For what it's worth I did attempt the debugging your asked for and when I used the templates, but I crashed my browser or the pi each time I attempted so something was definitely off. THAT BEING SAID, I think my instance shouldn't be something to focus on because its been running since I started my ha journey and I've installed, uninstalled, and reinstalled nearly everything I could very my hands on at some point along the journey so my instance is murky as hell anyways. I'm in the process of migrating to a fresh install.
I've swapped my production instance to docker on my server and have re-imaged the Pi's ssd and had Bermuda running constantly without issue for the past 2 weeks now that its cleaned up. Haven't moved everything over to it yet, so I'll keep you updated if I experience the same sort of issue as I migrate back to the pi (once the semester finishes up this week).

@agittins I have Performance issue w/ Bermuda as well, not sure if I narrowed down the cause, but I tried to track iBeacon provided by HA Companion and added hass_Bluetooth_Proxy w/ its Companion on a stationary Android Tablet. Will try to dig deeper and find out what exactly bogs my system down in the coming days.

I'd set this up as well but has uninstalled it and still had the issue's? Maybe it leaves some artifacts that interact with Bermuda nastily? Either way, Bermuda does away with the need for the BT_Proxy_Companion for me so it won't be getting installed again now that I can use my m5 atoms for both tracking and proxy

Ahh, now that's very interesting! Yes, I wonder if that integration is leaving a lot of records in the bluetooth backend that are confusing/bogging down Bermuda. I might try installing it myself for a bit and see if I can see what it's doing - if nothing else I can probably alter Bermuda to ignore the extra records.

hello all, I posted this issue here without knowing about this issue. There are some callgrinds that @bdraco created after looking for perfomance bottlenecks on my HAOS system running on a NUC12 bare-metal.
thanks


IMU InverseKinematics GUI throws exception if weights are not visited

Steps to reproduce
Follow opensense demo and try to run IK without visiting/clicking the weights button.
Expected result
IK runs
Actual result
Exception with no message dialog pops up, reported by Nev.Pires from Vicon

(include screen grabs where appropriate)
Environment and GUI version

@aymanhab which demo / files were you using? using the Rajagopal_OpenSense setup files does not reproduce this issue for me

@carmichaelong I also got this error while testing this tutorial. To reproduce it:

Load the model "Rajagopal2015_opensense.osim".
Go to "Tools -> IMU Inverse Kinematics..."
Select "walking_orientations.sto" as Sensor Orientation File.
Click Run.

I am using the following build: OpenSim 4.4-2022-05-17-cc0a2cf

Thanks @AlbertoCasasOrtiz, that was helpful! Just for documenting if we ever look back at this issue: the model needs to have IMUs on it (e.g., a model from after running IMU Placer), and this workflow likely is different than testing before since this does not simply load the given setup file.

@carmichaelong Yes the difference is here we run the tool live from scratch without checking the weights (which is probably what we all did when testing) instead of loading  a file.


clim

started in https://github.com/holoviz/hvplot/pull/492/files, here just rebased
closes #491

Coverage decreased (-0.02%) to 72.066% when pulling 02c5d4472a7cf3fcbc201f01ffbbe25fb46eba2a on aaronspring:patch-1 into 736379ee37f09ee162ac733b4b908ac3b49bae4c on holoviz:master.


Add Contribution.md

Right now i have no way to know, how to contribute to this repo, can it be expanded so i know how to get started? thank you :) CC @PaliwalSparsh

We presently have no CONTRIBUTING.md file in chrome-extensions project.
INSTRUCTIONS -

Make a CONTRIBUTING.md (keep capitals) in the main folder.
Copy all the contents here in it.
Replace "UIP" in there in the first line with "chrome-search-extension"
Send in a PR.

Also please read the CONTRIBUTING.md that you just made and write a good commit message as mentioned in there.

Fixed by #22.


[SPARK-7572][MLLIB] do not import Param/Params under pyspark.ml

Remove Param and Params from pyspark.ml and add a section in the doc. @brkyvz

Merged build triggered.

Merged build started.

Test build #32529 has started for   PR 6094 at commit 022abd6.

LGTM

Test build #32529 has finished for   PR 6094 at commit 022abd6.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
    decisionTreeCode = '''class DecisionTreeParams(Params):
class DecisionTreeParams(Params):
class LinearRegression(JavaEstimator, HasFeaturesCol, HasLabelCol, HasPredictionCol, HasMaxIter,
class LinearRegressionModel(JavaModel):
class TreeRegressorParams(object):
class RandomForestParams(object):
class GBTParams(object):
class DecisionTreeRegressor(JavaEstimator, HasFeaturesCol, HasLabelCol, HasPredictionCol,
class DecisionTreeRegressionModel(JavaModel):
class RandomForestRegressor(JavaEstimator, HasFeaturesCol, HasLabelCol, HasPredictionCol, HasSeed,
class RandomForestRegressionModel(JavaModel):
class GBTRegressor(JavaEstimator, HasFeaturesCol, HasLabelCol, HasPredictionCol, HasMaxIter,
class GBTRegressionModel(JavaModel):
        s"FileOutputCommitter or its subclass is expected, but got a $
trait FSBasedRelationProvider
abstract class OutputWriter

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32529/
Test FAILed.

test this please

Merged build triggered.

Merged build started.

Test build #32539 has started for   PR 6094 at commit 022abd6.

Test build #32539 has finished for   PR 6094 at commit 022abd6.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
    decisionTreeCode = '''class DecisionTreeParams(Params):
class DecisionTreeParams(Params):
class LinearRegression(JavaEstimator, HasFeaturesCol, HasLabelCol, HasPredictionCol, HasMaxIter,
class LinearRegressionModel(JavaModel):
class TreeRegressorParams(object):
class RandomForestParams(object):
class GBTParams(object):
class DecisionTreeRegressor(JavaEstimator, HasFeaturesCol, HasLabelCol, HasPredictionCol,
class DecisionTreeRegressionModel(JavaModel):
class RandomForestRegressor(JavaEstimator, HasFeaturesCol, HasLabelCol, HasPredictionCol, HasSeed,
class RandomForestRegressionModel(JavaModel):
class GBTRegressor(JavaEstimator, HasFeaturesCol, HasLabelCol, HasPredictionCol, HasMaxIter,
class GBTRegressionModel(JavaModel):
        s"FileOutputCommitter or its subclass is expected, but got a $
trait FSBasedRelationProvider
abstract class OutputWriter

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32539/
Test FAILed.

The failed test was known to be flaky (SPARK-7497).

Merged into master and branch-1.4.


devmapper: Fix a bug and fix a comment and add one reliability check

Fixes #16682

CC @LK4D4 @calavera @vbatts @rhatdan

Code LGTM
waiting for CI

I saw that janky passed :D

@LK4D4
So can I generate a PR without having created an issue?
Also I don't understand why janky and experimental have failed. Can't see anything obvious which points to my patches.

@rhvgoyal Yup, you can.
It's jenkins problems, seems like it's restarting now.

do we really need three commits to fix two things? :pensive:

@calavera Does this new title of PR sounds better?

LGTM

Janky is failing with an unrelated error. Merging.


I can only see the web console

that can only see the web console the admins from userRoles.json is possible?

@PsycoYT Why? there is a global login system.


Update reference to CORS configuration for public buckets

Which Cloudflare product does this pertain to?
R2
Existing documentation URL(s)

https://developers.cloudflare.com/r2/buckets/public-buckets/

Section that requires update
https://github.com/cloudflare/cloudflare-docs/blob/e2e12d866732bdb7ad69b87ff65968c0c45b8c16/content/r2/buckets/public-buckets.md?plain=1#L187-L189
What needs to change?
Currently the page states that CORS configuration is only possible via the S3 API, but configuration via the Dashboard is possible like described here.
How should it change?
Add a reference to the CORS page or remove this paragraph as it may be redundant.
Additional information
No response

Thanks for the catch @kev-ac! I removed the older reference because it's already listed in the Buckets section of the docs.


asterisks are escaped in text

in the paragraph "Disabling and enabling network adapters by using Windows PowerShell" within the bold PowerShell commands the asterisks are escaped with a backslash.
s/"*"/"*"

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ae2ae1b9-c4a8-c6ab-5d91-5fdee507de09
Version Independent ID: f5224802-e2fa-2552-d379-db871f3a8eb7
Content: Troubleshooting NIC Teaming
Content Source: WindowsServerDocs/networking/technologies/nic-teaming/Troubleshooting-NIC-Teaming.md
Product: windows-server-threshold
Technology: networking-nict
GitHub Login: @shortpatti
Microsoft Alias: pashort

Thanks for your dedication to our documentation. If we have been unable to review your issue in a timely manner, we sincerely apologize for the delayed response. We have captured the informtion you have provided for review. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close


Azure explorer does not sign in and times out

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.19.0
Regression From
No response
Architecture
i86
Storage Explorer Build Number
No response
Platform
Windows
OS Version
Windows 10
Bug Description
I recently updated Azure storage (28.06.2024) and since then my accounts have disappeared from the app and when I try to log in it does not open the explorer. I have tried signing in in app as per the troubleshooting guide but it just says "waiting for authentication..." and then times out.
Steps to Reproduce

launch explorer
open account management tab
sign in with azure
nothing happens.

Actual Experience
Sign in times out without requesting credentials. troubleshooting guide does not solve the issue.
Expected Experience

Additional Context

@CovaB Can you share the app and authentication logs (you may also need to turn on verbose authentication logging in the Settings).

managed to resolve it manually installing .Net 8 and reinstalling azure storage.


Fix doc strings for the instance config file.

Codecov Report

Merging #389 into development will not change coverage.
The diff coverage is 100%.

@@             Coverage Diff              @@
##           development     #389   +/-   ##
============================================
  Coverage        98.36%   98.36%
============================================
  Files               38       38
  Lines             3005     3005
  Branches           143      143
============================================
  Hits              2956     2956
  Misses              43       43
  Partials             6        6

Impacted Files
Coverage Δ

...e_compute_engine/instance_setup/instance_config.py
100% <100%> (ø)
:arrow_up:

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 64e17bf...11ff6ba. Read the comment docs.


Shouldn't need .NET Core 3.1 SDK  for ML.NET CLI installation.

System Information (please complete the following information):

Windows OS: Windows 11 Enterprise 21H2
MLNET: 16.8.3

Describe the bug

On which step of the process did you run into an issue: https://docs.microsoft.com/en-us/dotnet/machine-learning/how-to-guides/install-ml-net-cli
Clear description of the problem: need to update the doc that  .NET Core 3.1 SDK shouldn't be the pre-requisites.

Repro steps:

Installed .Net 6.0 SDK;
Can installed mlnet, no need to install .Net Core 3.1 SDK.

Screenshots

@luisquintanilla
Could you update prerequisite from net core 3.1 to .net 6 before next cli release, thanks!


Add patch for fastchat

Needed by https://github.com/intel-analytics/Langchain-Chatchat/pull/27

Closed because this problem is caused by model itself. Use latest model to fix this issue.


Roll Engine from 8107b36c7b13 to d16ba48e1d79 (1 revision)

https://github.com/flutter/engine/compare/8107b36c7b13...d16ba48e1d79
2020-08-24<EMAIL_ADDRESS>Enable hybrid composition by default on Android (flutter/engine#20722)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

firebase_test_lab_tests-1-linux fails on rerun, cc @blasten

Commit queue failed; closing this roll.


Refactor Orbit.Transaction into OC.Transaction.

Instead of a Transaction simply observing a source, Transaction becomes a
source itself. Transaction is a form of MemorySource that isolates changes
from a base source.
A transaction has its own internal cache. By default, this cache will
retrieve data from the base source if it's not defined. Alternatively, a
transaction can be completely isolated from the base source by setting the
isolated option to true. An isolated transaction's cache must be
manually managed.
Transactions are "begun" immediately by default. This means that they
immediately begin tracking transforms applied to them. When commit is
invoked, the transforms applied to the transaction will be coalesced and
applied to the base source.
In addition to this change, other preparatory work has been done to
Cache and Source to allow for easier overriding of the retrieve
method, and to allow sparse caches to work with sparse link data.

One thing that I'm a little scared about here is that retrieving values from the Transaction.baseSource happens "on demand" and means that you could get one value, change the base source somehow, and then retrieve another value that is now out of "sync" with the base source... I don't know that this is that big of a problem, but I'm a little worried about the "state" of the Transaction.
I think it's worth trying to make an editing context in the Ember Orbit layer to test this implementation out.
Perhaps Model#editContext that returns a model subclass connected to a transaction with a .save

One thing that I'm a little scared about here is that retrieving values from the Transaction.baseSource happens "on demand" and means that you could get one value, change the base source somehow, and then retrieve another value that is now out of "sync" with the base source

This is a solid point, and the reason why I introduced the isolated flag. You could flip this flag after initial (synchronous) setup of a transaction, and then retrieve will no longer fall back to the base source.

Also seeing the schema,options pattern fail us - I wonder if we should rewrite the base Source constructor to prefer
new Source({ schema: .... })

@gnarf that's a good idea. In that way, we could require a schema for most sources, and a baseSource for transactions (which will then grab schema from baseSource.schema).

@gnarf thanks for the thorough review - I've incorporated all your suggestions. Please merge if it looks good to you.


ModuleNotFoundError: No module named 'api'

how to solve

@angyee on colab?

Did you clone this repository?
'api' is a folder created by OP and all the Python files are called inside program from this folder. 'api' is not a Python package which can be installed by pip.


Stdlib typings for typed arrays (and specific errors) need brand fields to improve type safety

All typed arrays are assignable in our present dts.
let arr = new Uint8Array(20);
let arr2 = new Int16Array(20);
arr = arr2; // Valid.

The same is true of specific errors:
let err = new SyntaxError();
let err2 = new RangeError();
err = err2; // Also valid

We should fix this, as both of these sets of types are sets whose members are meant to be distinguished by type rather than by structure. This is really important in the case of typed arrays, as the following happens:
let arr = new Uint8Array(20);
let arr2 = new Int16Array(20);
arr = arr2; // Valid.
let sliced = arr.slice(0, 10); // Typed as a Uint8Array (really an Int16Array at runtime)

I have an idea for this. Each typed array has a [@@toStringTag] property, which we can use string literal types on.

While this was partially fixed by #6361, there are still issues in ES5.


[Authorization] Fix ResourceType error

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


[Static PODs] test upload image

이미지 업로드 진행중입니다...

cat /etc/systemd/system/kubelet.service/@@.yaml

cat /etc/systemd/system/kubelet.service/@@.yaml

lgtm


[FEATURE REQUEST] Implement monitoring for Istio

Is your feature request related to a problem? Please describe.
We would like to monitor parameters of Istio (control plane and envoy proxy) on unmanaged clusters deployed with Epicli.
In compare to managed cluster (AKS/EKS) Istio pods are working in internal cluster network which is not accessible by external prometheus server win epiphany.
Describe the solution you'd like
We would like to scrape metrics from Istio Control Plane and Envoy Proxy in our external Prometheus service (monitoring machine). In order to make it, we should implement schema with Prometheus Federation.
I would like to have Prometheus locally in cluster which scrape metrics from Istio components and external Prometheus should be able to get metrics using Ingress Gateway as endpoint and the mentioned local Prometheus .
Describe alternatives you've considered
Deploy node port service without local prometheus and federations.
Additional context
How to monitor Istio using external Prometheus: link

After short research it looks that in order to send metrics from istio mesh to our external monitoring instances we need to:

Deploy prometheus inside of our istio mesh cluster in order to scrape metrics from sidecar proxies
Expose the prometheus service outside of the cluster using virtual service, gateway and destination rules:

$ cat <<EOF | kubectl apply -f -
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: prometheus-gateway
  namespace: istio-system
spec:
  selector:
    istio: ingressgateway
  servers:
  - port:
      number: 80
      name: http-prom
      protocol: HTTP
    hosts:
    - "prometheus.${INGRESS_DOMAIN}"
---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: prometheus-vs
  namespace: istio-system
spec:
  hosts:
  - "prometheus.${INGRESS_DOMAIN}"
  gateways:
  - prometheus-gateway
  http:
  - route:
    - destination:
        host: prometheus
        port:
          number: 9090
---
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: prometheus
  namespace: istio-system
spec:
  host: prometheus
  trafficPolicy:
    tls:
      mode: DISABLE
---
EOF

More here: link and here: link

We should first ensure Istio usage and future.

Closing because of deprecation of Istio component.


feat(parser): add optional display-name to layer

My keymap was failing with sub-expression Layer+ must match at least once. Turns out it was because I have a label assigned to each layer in my keymap which is used in ZMK to show the current layer on displays via widget.
My keymap layers start like this
default_layer {
    label = "Base";
    bindings = <

This change adds support for an optional label property in layers which can match zero or once. Potentially the label could be used to print on the images in the top left corner rather than the layer identifier of the keymap.
See https://github.com/zmkfirmware/zmk/pull/551 which is the merged change in ZMK to support using the label to show in display widgets. There is also https://github.com/zmkfirmware/zmk/issues/578 which is to document this optional layer.

It was announced on the ZMK discord that label will change to display-name. Updated the branch to refer to display-name instead of label.
Discord message announcing the change

Thank you!


fix: ControlValueAccessor become more touchy

The form surrounding the control implementing CVA was not properly showing value updates performed with this.form.setValue (which translates to the write-function of CVA).
CVA (now?) requires the form controls to handle the touch event stuff.

Nice! Thank you!


[SPARK-33212][FOLLOW-UP][test-maven][test-hadoop2.7] Bring back duplicate dependency check and add more strict Hadoop version check

What changes were proposed in this pull request?

Add back Maven enforcer for duplicate dependencies check
Strict check on Hadoop versions which support shaded client in IsolatedClientLoader
Cleanup unnecessary code

Why are the changes needed?

The Maven enforcer was removed as part of #30556. This proposes to add it back.
Also, Hadoop shaded client doesn't work in certain cases (see these comments for details). This strictly checks that the current Hadoop version (i.e., 3.2.2 at the moment) has good support of shaded client or otherwise fallback to old unshaded ones.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Existing tests.

Test build #134130 has started for PR 31203 at commit 062b7bc.

Test build #134130 has started for PR 31203 at commit 062b7bc.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38713/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38713/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38713/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38713/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38713/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38713/

Test build #134130 has finished for PR 31203 at commit 062b7bc.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #134130 has finished for PR 31203 at commit 062b7bc.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/134130/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/134130/

Test build #134146 has started for PR 31203 at commit b5d82b7.

Test build #134146 has started for PR 31203 at commit b5d82b7.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38729/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38729/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38729/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38729/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38729/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38729/

Test build #134146 has finished for PR 31203 at commit b5d82b7.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #134146 has finished for PR 31203 at commit b5d82b7.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/134146/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/134146/

Test build #134382 has started for PR 31203 at commit 6657c87.

Test build #134382 has started for PR 31203 at commit 6657c87.

I wonder if this should go into VersionUtils? That does claim to be specifically for working with Spark version strings, but it seems relevant...

Oops I wasn't even aware of VersionUtils. Yes I agree it seems a better place to put this code. Let me update the PR later.

I wonder if this should go into VersionUtils? That does claim to be specifically for working with Spark version strings, but it seems relevant...

Oops I wasn't even aware of VersionUtils. Yes I agree it seems a better place to put this code. Let me update the PR later.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/134381/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/134381/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38968/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38968/

Test build #134382 has finished for PR 31203 at commit 6657c87.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #134382 has finished for PR 31203 at commit 6657c87.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/134382/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/134382/

Test build #134405 has started for PR 31203 at commit 9b8a911.

Test build #134405 has started for PR 31203 at commit 9b8a911.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38991/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38991/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38991/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38991/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38991/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38991/

Test build #134405 has finished for PR 31203 at commit 9b8a911.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #134405 has finished for PR 31203 at commit 9b8a911.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/134405/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/134405/

Test build #134499 has started for PR 31203 at commit 396130b.

Test build #134499 has started for PR 31203 at commit 396130b.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39085/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39085/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39085/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39085/

Test build #134499 has finished for PR 31203 at commit 396130b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #134499 has finished for PR 31203 at commit 396130b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/39085/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/134499/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/134499/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/39085/

Changes LGTM thanks @sunchao !

Changes LGTM thanks @sunchao !

Thanks @xkrogen for the thorough review! @dongjoon-hyun @viirya could you take a look?

Thanks @xkrogen for the thorough review! @dongjoon-hyun @viirya could you take a look?

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/134524/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/134524/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/39109/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/39109/

Since the last question is addressed, I'll merge this. Thanks!

Since the last question is addressed, I'll merge this. Thanks!


'file' access is not allowed due to restriction set by the accessExternalDTD property

Using version 0.10, I get an error when parsing a XJB file:
[ERROR] External Entity: Failed to read external document ***, because 'file' access is not allowed due to restriction set by the accessExternalDTD property.

I have tried solutions from https://stackoverflow.com/questions/23011547/webservice-client-generation-error-with-jdk8, but the error still shows up.
I have also tried adding
xjcJvmOpts += "-Djavax.xml.accessExternalDTD = all"
xjcJvmOpts += "-Djavax.xml.accessExternalSchema=all"

to build.sbt

Not sure which step helped, but this was the solution:
val `collection-setter-injector` = "net.java.dev.vcc.thirdparty" % "collection-setter-injector" % "0.5.0-1"

val `jaxb2-basics` = "org.jvnet.jaxb2_commons" % "jaxb2-basics" % "0.9.4"

val `jaxb2-basics-annotate` = "org.jvnet.jaxb2_commons" % "jaxb2-basics-annotate" % "1.0.1"

val `jaxb2-default-value` = "org.jvnet.jaxb2_commons" % "jaxb2-default-value" % "1.1"

val `jaxb2-namespace-prefix` = "org.jvnet.jaxb2_commons" % "jaxb2-namespace-prefix" % "1.1"

val `jaxb2-commons-lang` = "org.jvnet.jaxb2_commons" % "jaxb2-commons-lang" % "2.3"

val `jaxb-xjc` = "org.glassfish.jaxb" % "jaxb-xjc" % "2.2.10"

val `jaxb-impl` = "com.sun.xml.bind" % "jaxb-impl" % "2.2.10"

xjcPlugins := Seq(
  `collection-setter-injector`,
  `jaxb2-basics`,
  `jaxb2-basics-annotate`,
  `jaxb2-default-value`,
  `jaxb2-namespace-prefix`,
  `jaxb2-commons-lang`
)

xjcLibs := Seq(
  `jaxb-xjc`,
  `jaxb-impl`
)

xjcJvmOpts := Seq(
  "-Djavax.xml.accessExternalSchema=all",
  "-Djavax.xml.accessExternalDTD=all"
)

xjcCommandLine := Seq(
  "-Xcollection-setter-injector",
  "-Xinheritance",
  "-Xinject-code",
  "-Xnamespace-prefix",
  "-Xdefault-value",
  "-Xannotate",
  "-extension",
  "-encoding", "utf-8",
  "-verbose"
)


[vm/ffi] fromFunction and asFunction drop type argument and return dynamic

Can you please clarify the title/description of the task?
I'm not sure if you're identifying a bug or feature.

If I remember correctly, we created this task during a discussion about the API. I think the goal was to remove locations in the source code which are invariant/covariant/contravariant. By removing the type argument from asFunction() it becomes invariant by construction (but dynamically typed).
For fromFunction I don't remember what we discussed.
If there is a bug in variance checking for fromFunction and asFunction then this should be classified as bug. Though a bug could also be fixed without changing the API.

Ah yes, #37853 is the bug and this is the API cleanup.

This is a trade-off between verbosity and static checking. Removing the type argument to asFunction and lookupFunction makes it less verbose. However, it also makes it so that type errors are only caught when assigning the returned closure to a variable with some function signature.
/cc @mkustermann what do you think?

We agreed offline to leave it as is.


DirectRestService does not support @Path with a regexp

When using DirectServiceService a path annotation with a regexp causes a compile error:
Invalid escape sequence (valid ones are  \b  \t  \n  \f  \r  \"  \'  \\ )

It looks like this is supported in the RestServiceClassCreator, just not for the direct case.

Looking at the REST service creator, I believe the fix here is to strip out any regular expressions from the @Path annotation path template, maybe in AnnotationCopyUtil.


could you give the link of your cpm-v2 paper?

Hi,
Thanks for your great work!
I can not find the V2 paper both in arxiv and google.

Our paper will be in Arxiv soon. Before that, you can download it here https://github.com/TsinghuaAI/tsinghuaai.github.io/blob/main/CPM-2.pdf.


One token per form by default?

There are so many instances where multiple forms are output to the same response that I think it would be beneficial to have the PER_FORM flag as default.
However, this is still up for the decision of the implementor, in which case WebEngine can make this choice.
Leaving this issue here while I ponder, or if anyone else wants to share their thoughts.

PER_PAGE actually makes more sense.
By default, the page is rendered 100% on the server side. That means that even with 100 forms on a page, it's impossible to submit one before another token is generated.
It is only when the page is updated on the client-side that we need to update the forms, as they could all be submitted simultaneously.


legacy some vs proposes any

all/some vs all/any has the advantage that some is fairly standard in logic  and less likely to be confused with all than any.
Another option might be exists, or forAll, forSome but might be worth checking if there were any guidelines...

JavaScript uses some / every while Python uses all / any. We could keep the original names, but there would be some value in consistency with one of these languages.


21-hour old conflict resolution not happened yet

From @Floppy on June 1, 2017 10:35
Just found a dependabot notification comment from 21 hours ago which hasn't yet resolved the conflict.
Not sure if it's because I linked it to another issue (#1 here), so perhaps dependabot thinks I've changed it and has stopped updating it?
https://github.com/theodi/static/pull/237
Copied from original issue: dependabot/feedback#7

Ack, that one's almost certainly because of the downtime GitHub had yesterday - we saw a lot of 500s from them. Need to implement a backoff strategy there - I'll get on it.

From @Floppy on June 1, 2017 10:37
Ah, yes, of course, forgot about that!

OK, I've moved as many of our interactions with GitHub into async processes, which means we can retry them automatically and this shouldn't happen again. I've also cleaned up all of the bad data from GitHub's outage yesterday, so theodi/static#237 is fixed up, along with a few other PRs that had got into that state.
Thanks for the bug report!


types-registry seems to be missing packages in the latest version

I noticed @types/semver in particular, but there are others too.
 Very odd. Maybe if we just rerun the CI job, this will go away?

Here's running inside Docker to really eliminate any environmental issues:
docker run --rm node:buster sh -c \
	"apt-get -qq update && apt-get -qq -y install jq && cd /tmp && npm -s i<EMAIL_ADDRESS>&& cat node_modules/types-registry/index.json | jq -r '.entries' | grep semver"

  "git-semver-tags": {
  "is-semver": {
  "semver-compare": {
  "semver-compare-multi": {
  "semver-sort": {
  "semver-stable": {
  "semver-utils": {

Sorry, I think we weren't clear; we are actually running the tool that produces the package in dry-run and looking at its output; the published package is definitely missing things.

Could there be a race condition, perhaps, that only triggers in low-resource environments, such as CI?

I just reran it and no change, but in rereading everything it turns out there is some caching locally and removing it got me to a reproduction:
rm -rf packages/definitions-parser/data
rm -rf packages/publisher/output
GITHUB_ACTIONS=1 pnpm run --filter @definitelytyped/publisher parse
GITHUB_ACTIONS=1 pnpm run --filter @definitelytyped/publisher publish-registry --dry
# check packages/publisher/output

With that in mind, #771 fixes the problem, so this feels like some weird package loading bug.

Last time I looked the code in this repo, I saw that some of the work was done in the worker processes, so perhaps it is something related to that?

It's most likely the fact that this job doesn't actually pnpm install the DT repo now that it's a real monorepo. That screws with the loading process because we too eagerly check for errors, which I'm guessing aren't propagated up somewhere accidentally and so we're publishing incomplete data. #771 fixes this by not doing those error checks up front, with #769 removing the need to do analysis entirely.

#771 indeed fixes this. 0.1.668 has the correct packages as far as I can tell from diffing against 0.1.665


Cleanup

Prolly a good time to mention these.
Is there a reason why the ppy license header is used instead of one for yourself?
Perhaps you could also set certain code styles or convention to trigger warnings/errors on build. (related

I don't really notice the license header with my IDE, i'll remove them in the next PR.


Add acronym exercise

This patch adds the acronym exercise with stub, tests and an example solution, as per the guidelines. The tests were based on the x-common test data.

So, what's the next step here?

Sorry for the noise, I deleted the branch from my repo and didn't realize it would affect the PR.

After a quick glance on my phone, this looks good to me. /ping @arguello

Merging. We can always update it later. Thanks, @tautologico!


CI_COMMIT_REF_NAME not populated correctly when branch name has a slash

If I have a branch named something like task/my_awesome_branch the CI_COMMIT_REF_NAME predefined variable just says task.

Roger that 👍 Will get that fixed right up...

@tOmoness here you go https://github.com/firecow/gitlab-ci-local/commit/7b8d262e54520310cbb8f76d5a0956d4f2fd6f7e


Jesse: Watch developerqna.com

Jesse requests the watch of the watch_keyword developerqna\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

developerqna\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


ARROW-1744: [Plasma] Provide TensorFlow operator to transfer Tensors between Plasma and TensorFlow

This is based off of #2046 from @pcmoritz and @concretevitamin, who wrote the original TensorFlow Op with help from @ericl.
In addition to the previous PR, this supports serialization of arbitrary type tensors.
To get it working, arrow has to be compiled in the following way:
cmake -DARROW_PLASMA=on -DARROW_TENSORFLOW=on -DARROW_PYTHON=on ..
make -j8
sudo make install

And pyarrow like that:
PYARROW_WITH_PLASMA=1 PYARROW_WITH_TENSORFLOW=1 python setup.py develop

The PR also includes utilities that should be generally useful in converting between TensorFlow and Arrow. It is currently supposed to be used to transfer weights in and out of TensorFlow but hopefully in the future there will also be support for data Tensors.

Codecov Report

Merging #2104 into master will decrease coverage by 0.14%.
The diff coverage is 15.85%.

@@            Coverage Diff             @@
##           master    #2104      +/-   ##
==========================================
- Coverage   86.42%   86.27%   -0.15%
==========================================
  Files         242      245       +3
  Lines       41536    41613      +77
==========================================
+ Hits        35896    35903       +7
- Misses       5640     5710      +70

Impacted Files
Coverage Δ

cpp/src/arrow/python/python_to_arrow.h
0% <ø> (ø)

cpp/src/arrow/python/python_to_arrow.cc
86.53% <0%> (-1.77%)
:arrow_down:

cpp/src/arrow/python/arrow_to_python.cc
86.59% <0%> (-5.13%)
:arrow_down:

cpp/src/arrow/ipc/writer.cc
93.19% <100%> (ø)
:arrow_up:

python/pyarrow/tests/test_plasma_tf_op.py
21.05% <21.05%> (ø)

python/pyarrow/plasma.py
78.43% <33.33%> (-9.67%)
:arrow_down:

cpp/src/arrow/python/tensor_util.cc
6.25% <6.25%> (ø)

cpp/src/arrow/util/memory.h
100% <0%> (ø)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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

This is ready for review

Thanks for reviewing and the comments so far, I'll respond to the remaining ones and incorporate the changes tomorrow!
The most important question to figure out is the more high level question of how/when to build the op and I'm curious about more thoughts here. Building it at runtime seems inevitable to me and I would really like to avoid having to introduce a C API if possible (to avoid the ABI conflicts), but let me know what you think. Most likely there will be a need for more TensorFlow/arrow code in the future (i.e. for passing arrow datasets/RecordBatches into TensorFlow) so having a solid foundation will be valueable.

Great work, this looks good to me! I'd hold off on introducing a C API and focus on keeping the code clean/simple for now. If we run into substantial build or binary issues, then that may be the right thing to do.

Yeah, sounds good to me, this is ready to merge now. Let's see what our experience is deploying it with Ray and then we can iterate on it.

Regardless of the review comments, I want to ask a higher-level question: does this have to be part of the Arrow codebase? We seem to be piling up adapters for third-party libraries without regard for maintenance concerns. I think even the fact that Plasma is part of the Arrow codebase should be questioned. It clearly is a separate piece of code (to the point that it has distinct build files) with its own quality standards.

I think it's a good idea to have all the code in the same place precisely to ease maintenance but also to have consistent governance standards Though there are Apache projects with multiple repos, I would really like to avoid that. Even having the Parquet adapter code in a separate codebase has been more trouble than it's worth IMHO.
The burden of maintenance should clearly be shared. I find it unfortunate that the Ray developers are not participating much in the packaging and release maintenance for Arrow, and instead ship this code on their own inside Ray.

In Parquet's case I understand, because there's a weird bidirectional dependency between the Parquet and Arrow repositories that makes everything complicated. In Plasma's case, the dependency would only be in a single direction (from Plasma to Arrow). Also, Plasma is more of an application than a library that would sit at the same level as Arrow.

Also, Plasma is more of an application than a library that would sit at the same level as Arrow.

This is true for now. We haven't built anything inside Arrow that depends on Plasma yet, but I think it's entirely possible in the future (spill-to-disk joins, etc.). In the context of a database system, Plasma serves as a "subsystem for managing shared memory pages and out-of-core data", so it fits with the objective of building a deconstructed database.

I fully agree with @wesm on Plasma. Let me know @pitrou if you have things in mind we can improve. The codebases originally started out as separate with different styles etc., but things are converging more and more and we are happy to put in work to make it even more so in the future.
Regarding TensorFlow, my perspective on this is that machine learning is a super important part of modern data processing (increasingly so) and TensorFlow is the de facto standard for ML and therefore we need to spend the time to make arrow and TensorFlow work together very well. Even if that's going to be painful (TensorFlow has its quirks). This is going to be far easier if the work happens in the arrow repo.
@wesm Thanks for the feedback and please let us know how we can improve the cooperation on the packaging and release maintenance.

Here is a thread from March 23 about problems with Arrow's packaging and release management:
<EMAIL_ADDRESS>No one who develops both Ray and Arrow replied on the thread, presumably (?) because you are vendoring Arrow and dealing with packaging on your own, so the woes that the Arrow release managers have experienced haven't impacted you very much. There's nothing inherently wrong or immoral with vendoring an upstream open source project.
In principle, you could base Ray releases on released versions of Arrow (Ray has released about as many times as Arrow has). To make this practical, Arrow would need to release more often. BUT, Arrow has not released more often because the release management and packaging process has been so historically onerous (I have borderline PTSD from having been the release manager too many times, only half joking).
Meanwhile, our 0.10.0 release is blocked as we've decided not to release again unless we can include the binary packages in the release vote, to prevent the kind of packaging disaster that befell the 0.9.0 release. So this is where we stand right now.
Since we are all ultimately volunteers, there's nothing forcing you to help with packaging and releases for Arrow, but the community would be stronger and healthier if you did.

BTW, Ray's vendored pyarrow conflicts with the non-vendored one if they are both installed:
>>> import ray
>>> import pyarrow
>>> pyarrow
<module 'pyarrow' from '/home/wesm/miniconda/envs/ray-test/lib/python3.6/site-packages/ray/pyarrow_files/pyarrow/__init__.py'>

I took a look at the PyPI download stats on BigQuery -- pyarrow is being installed ~10-15x as often as Ray, so this could spell trouble for users.

We do want to switch over to including pyarrow via pip into ray; we can try looking into that. The requirement from the development side is to have arrow nightlies or per-commit packages that we can use for the development of Ray (since there is a lot of development on both sides that needs to be in sync). For releases we would need to synchronize with arrow releases in some way.
The advantage to vendor arrow with Ray like we do now is that there is just one version we need to support and from the user's perspective "it just works".

Thanks all! If any of you have a moment, maybe you can jot down some ideas for where to go with TF integration from here? https://cwiki.apache.org/confluence/display/ARROW#ApacheArrowHome-MachineLearningFrameworkIntegrations


feat(connector): [Dlocal] Use connector_response_response_id as reference to merchant

Type of Change

[x ] Bugfix
[ ] New feature
[ ] Enhancement
[ ] Refactoring
[ ] Dependency updates
[ ] Documentation
[ ] CI/CD

Description

Additional Changes

[ ] This PR modifies the API contract
[ ] This PR modifies the database schema
[ ] This PR modifies application configuration/environment variables

Motivation and Context

How did you test it?

Checklist

[ ] I formatted the code cargo +nightly fmt --all
[ ] I addressed lints thrown by cargo clippy
[ ] I reviewed the submitted code
[ ] I added unit tests for my changes where possible
[ ] I added a CHANGELOG entry if applicable

Hi @nikita812 ,
This issue is already been assigned to someone else , If you are interested you can request for similar issues . Closing this pr in favor of https://github.com/juspay/hyperswitch/pull/2446


fix child fork with debug port in-use

Coverage increased (+0.01%) to 97.619% when pulling eeda38638095bea8ba5f3e76ff5ecffd270cd133 on release/2.0.2 into a2009f0581bb62a9977d374e443be556e8cd6e24 on master.

Coverage increased (+0.01%) to 97.619% when pulling eeda38638095bea8ba5f3e76ff5ecffd270cd133 on release/2.0.2 into a2009f0581bb62a9977d374e443be556e8cd6e24 on master.

Coverage decreased (-1.3%) to 96.33% when pulling 9d9757d152eec8e15b3b2b6e7f52eed906dc64b0 on release/2.0.2 into a2009f0581bb62a9977d374e443be556e8cd6e24 on master.


Add a warning when transforming a tower

Transform is a mechanic in random game modes where player can build a tower on top of another tower.
Add a popup dialog which has "yes/no" buttons to make sure that player wants to perform the action.

I don't think we need such a precaution. This popup dialog will add more annoyance than a user-friendliness. Towers are replaced very often in Upgrade and Random modes and on higher difficulties it has to be fast.

Ok, this was requested by someone in discord.
Could skip the confirmation by default and add a setting to toggle confirming off and on.
Though it's better to have as little settings as possible.

Closing for now. Will reopen if more people request and it's judged that this feature is needed.


Support for SNS SSE (Server-side Encryption)

I need support for server-side encryption in SNS, so I'd like to add it.
I've been working on it, and should have a PR  to submit soon.

Is this similar to #363?

#363 Added support for server-side encryption in the SQS queues, I need it in the SNS topic as well.
I'm using a similar approach to #363 to add this when creating a topic.

PR #553 submitted

Resolved by #575.


new course added in devops hi list

What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
Add resource
For resources
Description
Why is this valuable (or not)?
yes it is useful for devops learning person
How do we know it's really free?
yes free on youtube
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[ x] Include author(s) and platform where appropriate.
[ x] Put lists in alphabetical order, correct spacing.
[ x] Add needed indications (PDF, access notes, under construction).
[ x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Kindly review


ml1 notebooks improvements

I'm not sure how to contribute to the course notebook improvements.
Here are a few corrections/improvements:

courses/ml1/lesson1-rf.ipynb

replace:
*todo* define r^2
with:
In statistics, the coefficient of determination, denoted R2 or r2 and pronounced "R squared", is the proportion of the variance in the dependent variable that is predictable from the independent variable(s). https://en.wikipedia.org/wiki/Coefficient_of_determination

before:

df_raw.UsageBand = df_raw.UsageBand.cat.codes
add explanation:
"Normally pandas will continue displaying the text categories, while treating them as numerical data internally. Optionally we can replace the text categories with numbers, which will  make this variable non-categorical, like so:"

courses/ml1/lesson2-rf_interpretation.ipynb

In "One-hot section encoding" there is no explanation of what it does. Here is my attempt to explain:
"Using proc_df's *max_n_cat* argument we can turn some categorical variables into new columns,
where MyCol with categories (small, medium, large) will turn into 3 new one-hot encoded columns
MyCol_small, MyCol_medium, MyCol_large (removing the original one).

It will only happen to columns whose number of categories is no more than max_n_cat.

Now we may have columns with more important features than they were earlier where all categories were in one column."

courses/ml1/lesson3-rf_foundations.ipynb

a small fix here:
http://forums.fast.ai/t/another-treat-early-access-to-intro-to-machine-learning-videos/6826/615
Thanks.
If there is a better way to do it please let me know how (link?)
I'm currently trying to figure out the use of nbdime for notebook diff patches. I'll post more once the nbdime's developer has all the issues resolved.

moved to https://github.com/fastai/fastai/issues/566


All tests running all the time

My setup:
@TestGroup("common")
public class BillingDayServiceImplTest extends JooqTest {
    @ClassRule
    public static TestGroupRule rule = new TestGroupRule();
    public BillingDayServiceImpl target;

Maven intellij config: clean install -Dtestgroup=authorisation
But BillingDayServiceImplTest still runs and shouldn't as far as I can tell!

I'll have a look

thank you, if you need more information please let me know.

@marclazell I can not reproduce your problem. I created this Test based on your example:
import org.junit.ClassRule;
import org.junit.Test;
import com.github.ferstl.junit.testgroups.TestGroup;
import com.github.ferstl.junit.testgroups.TestGroupRule;

@TestGroup("common")
public class BillingDayServiceImplTest {

  @ClassRule
  public static TestGroupRule rule = new TestGroupRule();

  @Test
  public void test() {}
}

When I run mvn clean install -Dtestgroup=authorisation the test is skipped:
-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running BillingDayServiceImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.052 sec

Results :

Tests run: 1, Failures: 0, Errors: 0, Skipped: 1

What is in your base class JooqTest? Are you using a test runner that is not part of JUnit?

@RunWith(SpringJUnit4ClassRunner.class)
@TestExecutionListeners({DependencyInjectionTestExecutionListener.class})
@ContextConfiguration(locations = "classpath:testjooq.xml")
public abstract class JooqTest {

And a few Mocks and things.
Does your framework work for SpringForJunit?

@marclazell There is indeed an issue with SpringJUnit4ClassRunner. With an inactive test group your test will not be executed. However, the test runner will setup everything else. For example, it will create an Application context, inject dependencies, etc. before it finds out that there is nothing to do.
The reason for this behaviour is that all these steps happen before any JUnit class rules (such as TestGroupRule) are triggered.
Since Spring version 4.2, there is a solution to this problem. This version introduced class and method rules as replacement for the SpringJUnit4ClassRunner.
So if you are already using Spring 4.2, you can use a RuleChain which runs the TestGroupRule as the first rule:
@ClassRule
public RuleChain rules = RuleChain
    .outerRule(new TestGroupRule())
    .around(new SpringClassRule());

Instead of SpringJUnit4ClassRunner, you can just use JUnits BlockJUnit4ClassRunner which is the default if you don't use the @RunWith annotation.

@ferstl Thank you for this answer. Is there any solution to this issue where I can use SpringJUnit4ClassRunner with your TestGroup framework? The tests were written by a third party and I am unsure of the impact of changing the runner on thousands of tests.
Thanks!

@marclazell Unfortunately, there is nothing I can do. The SpringJUnit4ClassRunner creates the application context before any of the JUnit test rules are evaluated.
What I saw is, that the test runner just creates the application context but does not instantiate any beans (at least in my example). So probably, there is not much overhead for tests that do not run because of the TestGroupRule. If this doesn't work for you, you may try Spring's {{@IfProfileValue}} annotation instead of {{@TestGroup}}. I don't have much experience with this spring feature, but you could probably use {{@TestGroup}} for non-Spring tests and {{@IfProfileValue}} for Spring tests together.

Okay thanks very much for the advice! I will consult one of our architects about this dilemma as we really want to group tests, and your framework is quite easy and lightweight!
thanks again! Closing issue!


can support zip  jsbundle?

Not yet. That is the next thing to be done. Currently, because of this, we cannot update assets dynamically.


Timezone toggle

Need a way to let the user change the timezone, see thread https://github.com/GoogleChrome/devsummit/issues/145#issuecomment-528787558

thoughts on a stateful switch we place in a decently global spot on the schedule page?

the effect of it is global, but the moment you need to change it is quite contextual.
if we put it in the footer it may go unnoticed
if we put it in the header, it takes a hero role
if we put it in the settings, well we might not have settings if we dont do auth (yeah?)
it's almost like the best place is right in the context of the time, but then we lost all the fun way to "present" the data separate from it's underlying UTC. bah.
thoughts? jake, did you think of any better spots for it, i'm open to ideas here?
maybe where it's at now is fine, but needs some explainer text and a little bit of separation from the card text?
regardless, i'm still noodling on this and plan on producing some alt ideas.


Produce multi-module project in the archetype [ECR-4288]

Overview
Make the archetype produce a multi-module project,
with a module for messages; and the service itself.
Also, add exonum-messages to BOM.

See: https://jira.bf.local/browse/ECR-4288
Definition of Done

[ ] There are no TODOs left in the code
[ ] Change is covered by automated tests
[ ] The coding guidelines are followed
[ ] Public API has Javadoc
[ ] Method preconditions are checked and documented in the Javadoc of the method
[ ] Changelog is updated if needed (in case of notable or breaking changes)
[ ] The continuous integration build passes

You may want to run mvn install -pl service-archetype -am and see the generated during ITs project in the target (service-archetype/target/test-classes/projects/project/integration-test).


Suffix file not bundled with Hex package?

Created a new project (mix new foo), added the necessary things to mix.exs:
...
def application do
  [applications: [:logger, :public_suffix]]
end

defp deps do
  [{:public_suffix, "~> 0.2.0"}]
end
...

Then:
$ mix deps.get
Running dependency resolution
Dependency resolution completed
  idna: 2.0.0
  public_suffix: 0.2.0
* Getting public_suffix (Hex package)
Checking package (https://hexpmrepo.global.ssl.fastly.net/tarballs/public_suffix-0.2.0.tar)
Using locally cached package
* Getting idna (Hex package)
Checking package (https://hexpmrepo.global.ssl.fastly.net/tarballs/idna-2.0.0.tar)
Fetched package
$ mix compile
==> idna (compile)
Compiled src/idna_ucs.erl
Compiled src/idna_unicode.erl
Compiled src/punycode.erl
Compiled src/idna.erl
Compiled src/idna_unicode_data.erl
==> public_suffix
Compiled lib/public_suffix/remote_file_fetcher.ex
Compiled lib/public_suffix/rules_parser.ex

== Compilation error on file lib/public_suffix.ex ==
** (File.Error) could not read file /home/user/elixir/foo/deps/public_suffix/data/public_suffix_list.dat: no such file or directory
    (elixir) lib/file.ex:244: File.read!/1
    lib/public_suffix.ex:122: (module)
    (stdlib) erl_eval.erl:670: :erl_eval.do_apply/6

could not compile dependency :public_suffix, "mix compile" failed. You can recompile this dependency with "mix deps.compile public_suffix", update it with "mix deps.update public_suffix" or clean it with "mix deps.clean public_suffix"

Works fine with download_data_on_compile: true, though.
(Elixir 1.2.5, Hex 0.12.0)

Sorry for the trouble and thanks for reporting it!  I just released 0.2.1 with this fixed.


Client page

Hi, meet again. This time I would like to ask a question from the client. Our project does not have its own web client, does it?

Postal has a web interface for managing it but all the messages sent through Postal should be handled via a separate system that knows to pass emails to Postal for sending. Is that what you mean?

Yes, it would be nice to have pages to accept send management and so on

Unfortunately there is no interface beyond the ability to send messages and administration. If you want to add extra controls then these would be better located in your own application or a separate system.

🆗


genconfig generates new certificates each time

When building the cluster initially and then running talhelper genconfig it all works fine.
If you delete the talosconfig generated and run talhelper genconfig again you get a different ca, crt and key from the same configuration.
 The crt and key are expected to be different everytime u generated a new one because it's using the time you run the command but not the ca. And you will still get to access to Talos API as long as the ca is correct.

I can't reproduce it on my test though:
 diff clusterconfig/talosconfig clusterconfig-old/talosconfig
6,7c6,7
<         crt: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUJLVENCM0tBREFnRUNBaEVBalhOTSt5Q05sZ0tlVjZick9EUUxsREFGQmdNclpYQXdFREVPTUF3R0ExVUUKQ2hNRmRHRnNiM013SGhjTk1qTXhNVE13TVRVeE56UXhXaGNOTWpReE1USTVNVFV4TnpReFdqQVRNUkV3RHdZRApWUVFLRXdodmN6cGhaRzFwYmpBcU1BVUdBeXRs
Y0FNaEFGb2RmelU0YUdJQ1B2VElSMlNGemRNTGpNMWZXQXYzCmhGTU5BczZVdFFwSm8wZ3dSakFPQmdOVkhROEJBZjhFQkFNQ0I0QXdFd1lEVlIwbEJBd3dDZ1lJS3dZQkJRVUgKQXdJd0h3WURWUjBqQkJnd0ZvQVVHbkh2YVpOL0RtTzEweDdmZi9kMFU4N21wZFF3QlFZREsyVndBMEVBUisvRgpiNjNlMkRhcEgwMG1HSDVjWmY1bDJtQ3RjNDA2YXV
zcm5xQnRScytQWnhqQ0twQ2NNRDdyZE93Y2J3SUxjNGNRCmlKTWg2OEFzWEI1L0pFcE1Ddz09Ci0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K
<         key: LS0tLS1CRUdJTiBFRDI1NTE5IFBSSVZBVEUgS0VZLS0tLS0KTUM0Q0FRQXdCUVlESzJWd0JDSUVJRXNzNkprOG9kcGJjeWw4aGFWWWsxMGpVWWI4eG1ScjMzSm0zcjZPbnFYMAotLS0tLUVORCBFRDI1NTE5IFBSSVZBVEUgS0VZLS0tLS0K
---
>         crt: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUJLVENCM0tBREFnRUNBaEVBeWVzclljbDZWSlhETW81eU1ITHJYakFGQmdNclpYQXdFREVPTUF3R0ExVUUKQ2hNRmRHRnNiM013SGhjTk1qTXhNVE13TVRVeE56STFXaGNOTWpReE1USTVNVFV4TnpJMVdqQVRNUkV3RHdZRApWUVFLRXdodmN6cGhaRzFwYmpBcU1BVUdBeXRs
Y0FNaEFHUWpFTTBTdDlLVEpzZXFFWDZHYTJGM3lkL05KMGFQCnExRzRaZEVpODVTcm8wZ3dSakFPQmdOVkhROEJBZjhFQkFNQ0I0QXdFd1lEVlIwbEJBd3dDZ1lJS3dZQkJRVUgKQXdJd0h3WURWUjBqQkJnd0ZvQVVHbkh2YVpOL0RtTzEweDdmZi9kMFU4N21wZFF3QlFZREsyVndBMEVBbXVwOQpXelYza3IwS0syQ2ZJa25RaVlaNXNCbGkwUDBYQ0F
ERFNlMFJMM3VGU0xuRkhyZ0JiS3VDOThFNm1OTmZYU2dUCngzclprSERjRmt2RUEyQWZEUT09Ci0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K
>         key: LS0tLS1CRUdJTiBFRDI1NTE5IFBSSVZBVEUgS0VZLS0tLS0KTUM0Q0FRQXdCUVlESzJWd0JDSUVJSTVtd2hLYktGU2sxNXRYQlFBZkpDQitPQWdyaW16a1NGWnZpRDdZdVlRYQotLS0tLUVORCBFRDI1NTE5IFBSSVZBVEUgS0VZLS0tLS0K

Odd, I've just reproduced it again and put in a git repo https://github.com/lewis-green/talhelper-diff-issue.

The repo above also shows only the crt and key are different and it's expected to be different.
Are u sure your problem is related to talosconfig can't be used to do talosctl command? And I see that you're using the example talconfig.yaml without changing anything. The example is just for example and most things inside are not reasonable/doesn't make any sense and just for example of keys you can use with it.

@lewis-green I encountered a similar problem due to having the wrong name on the secrets file, and so it was actually regenerating the CA each time it ran. If you run the genconfig command with -d it should output if it's generating new secrets, similar to the snippets I posted on this issue.

@bluevulpine Seems like the issue is not the same because the linked repo above shows that it was using talsecret.yaml. But thanks for the information!

It was fixed today.

I'm going to close this issue because of inactivity. Feel free to re open if you still encounter this problem in the latest release. Thank you.


Avoid duplicate error messages due to cross-product

Before opening, please confirm:

[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

Bug Category
Schemas and Validation
Describe the bug
The validator can produce the same error message multiple times, one for each product configuration.
Expected behavior
It should remove the duplicates. Alternatively, make the error more specific in each case, so they are not duplicates.
Reproduction steps
cedar validate -s example.cedarschema.json -p example.cedar
Code Snippet
Example policy,
permit (
  principal,
  action in [Action::"SomeAction"],
  resource
)
when { principal in resource.someattribute };

Example schema,
{
  "My::Name::Space": {
    "entityTypes": {
      "Entity1": {
      },
      "Entity2": {
        "memberOfTypes": ["Entity3"],
        "shape": {
          "type": "Record",
          "attributes": {
            "attr4": {
              "type": "Entity",
              "name": "Entity4"
            }
          }
        }
      },
      "Entity3": {
      },
      "Entity4": {
        "memberOfTypes": [],
        "shape": {
          "type": "Record",
          "attributes": {
            "attr1": {
              "type": "Entity",
              "name": "Entity1"
            }
          }
        }
      }
    },
    "actions": {
      "action2": {
        "appliesTo": {
          "principalTypes": ["Entity1"],
          "resourceTypes": ["Entity2"]
        }
      },
      "action4": {
        "appliesTo": {
          "principalTypes": ["Entity1"],
          "resourceTypes": ["Entity4"]
        }
      },
      "action3": {
        "appliesTo": {
          "principalTypes": ["Entity1"],
          "resourceTypes": ["Entity3"]
        }
      }
    }
  }
}

Log output
Validation Results:
Validation error on policy policy0: Unrecognized action id Action::"SomeAction", did you mean My::Name::Space::Action::"action2"?
Validation error on policy policy0: Unable to find an applicable action given the policy head constraints
Validation error on policy policy0 at offset 112-134: Attribute not found in record or entity: someattribute
Validation error on policy policy0 at offset 112-134: Attribute not found in record or entity: someattribute
Validation error on policy policy0 at offset 112-134: Attribute not found in record or entity: someattribute

Additional configuration
No response
Operating  System
No response
Additional information and screenshots
No response

Personally I think we should include the cross product with every error (https://github.com/cedar-policy/cedar/issues/135). In that case, I don't think it's that bad to have the duplicates.

This is a bug in how we forward the error messages. The validator collects errors messages in a hash map, so exact duplicates are already avoided. The three errors returned by the validator are actually not the same even though the text is identical. The validator returns a "suggested fix" with each that is not being printed. The resource entity types all have different attributes, so the suggestion is different.

Fix the immediate issue in #252. It will still display three very similar errors messages. As future work, we could do something clever to gather error messages which have the same root cause but different details into a single message which would explain the error once and then elaborate on the individual details.

Closing as fixed by #252.


[ENH] Quickly validate if lock file needs to be updated

As a conda-project user, I would like to quickly check whether conda project update would require a re-lock.
I would like to ensure that my lock file is only forced to be re-generated if my environment specification file(s) have changed. As a result, I can have a pre-commit hook that runs to ensure that my environment.yml and conda-project.yml are never out-of-sync in git, if I choose to use that hook.

https://conda-incubator.github.io/conda-lock/flags/#-check-input-hash

Had a feeling it would be in conda-lock, but want to make sure it was captured here.

I have a question about this. Would you like to have a separate cli command or flags that just check that status of the lock file (and/or the prepared env)?
PR #22 now has two properties per environment. .is_prepared and .is_locked.
Would you want something like conda project lock --check-only that can report the status but not actually do anything? What might it return or print? Or would --dry-run be useful?
https://github.com/conda-incubator/conda-project/blob/751f452d21573f5313c6a18d2fb578e4af224d3a/conda_project/project.py#L95-L142

The specific use case I was thinking of was to have something like conda lock --check which would return a non-zero error code if the files are out of sync. This is inspired by poetry lock --check.
In particular, there is a pre-commit hook I have used in the past that would run this for poetry and fail the commit if the lock file was not in sync with the conda-project.yml file.
I can dig up the link to that if it'd be helpful. I can also contribute a pre-commit hook if we are able to support this functionality.

I will add conda-project lock --check-only and conda-project prepare --check-only as you suggest. Thanks!

Correction, in #22 I've done like poetry and implemented conda project check, which only checks the lockfile against the source for consistency. For multiple envs the command will return 1 if any of them are out-of-date.


Support create table like statement for iceberg and hudi table

What type of PR is this：

[x] bug
[x] feature
[ ] enhancement
[ ] others

Which issues of this PR fixes ：
Closes #4602
Problem Summary(Required) ：
Support create table like statement for iceberg and hudi table

[FE PR Coverage check]
:disappointed: fail : 1 / 19 (05.26%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/catalog/Catalog.java
1
19
05.26%


Generalize project hero component. #455.

Ticket
Closes #455.
Reviewers
@MillenniumFalconMechanic.
Changes

Refactored project Hero component to BackPageHero component.

Definition of Done (from ticket)

Project hero component renamed and moved, and re-used for both entity detail pages and export-related pages.

@frano-m, can you resolve the conflicts in this one, please? Thanks!
D


Binary classification using Pytorch

Hi,
While generating counterfactuals for a binary PyTorch classifier, I observed that the predict function only returns a single output (list with 1 element), as it is trimmed based on a number of output nodes:
dice_pytorch.py

Now, in explainer_base.py, we again see a check based on output nodes (in my case = 2), and so it throws an out of index error (line highlighted) as it is trying to access index = 1, whereas out model_score list is only having one element trimmed in dice_pytorch.py

Any information on this will be appreciated

This is fixed in PR #261  and #312. You can try checkout the branch amshar/support-private-data-for-sklearn-models---that should work for your problem.
It will be soon pushed for a release.
If it does not work, let me know


[Bug]: Can't restart document parsing

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Branch name
0.10.0
Commit ID
e18f407
Other environment information
docker

Actual behavior
上传文件点击启动，解析过程中发生点击取消，再重新进行解析无法成功，解析进度没有进展，报错"{} empty task!".format(msg["id"])   显示没有这个task，这里断言没有过的话，导致后续所有文档都无法进行解析

Expected behavior
希望大佬能够解答为什么，以及怎么处理，使得文档解析成功
Steps to reproduce
一个文档失败了，后续新加的文档也无法进行解析，进度条没有进展

Additional information
No response

后面无法进行的文档，我看到document表中一直都是 Task dispatched...    ，task表中一直为0，一直没有出现 task received...的msg，

Would you please upgrade RAGFlow to the latest version?
By the way, we intend to create an international community, so we encourage using English for communication.

Would you please upgrade RAGFlow to the latest version?
By the way, we intend to create an international community, so we encourage using English for communication.

does the latest version  can solve this problem ?  and When can the team version be released?  hope your reply ~~~

@adogwangwang v0.14.0+ has much better log and task monitoring and failure handling.


What are you think about vue-formly as form generator?

I use your admin panel, but I found that vue-formly is very functional like form generator, becouse I can on the config object set all configurations of form and it is very easy. All of the form elements from the admin panel I have set up as a custom elements for that package and now the creation of the form is very simple.
(for validation I use vee-validate, I don't use validation from that package)
https://github.com/formly-js/vue-formly

@codegor thank you for the suggestion but we think that formly lib is still quite fresh to be added as a dependency :)
We're thinking of wrapping inputs in something like  elements by the way

will be very cool if you will create a system for creating form from one config file, like at that pakedge. I think it is cool idea create form from 1 config object. Thank you for reply.


Instantiate contract process ordering

Problem State
As you can see in https://github.com/terra-project/core/issues/399
If you store the instantiated contract after dispatching all messages, it will block the messages to use instantiated contract.
https://github.com/CosmWasm/wasmd/blob/ff37dc68f2a4ea86abf7b7f124c166c793d63e67/x/wasm/internal/keeper/keeper.go#L242-L250
Proposed solution
So recommend to store the instantiated contract data and dispatch response messages later.

Good point. So the messages sent out can refer back to the newly instantiated contract. Will add to next release


[manuf] Propose to store DICE certificates in the flash_info with the "Cert Header"

Test point name
NA
Host side component
None
OpenTitanTool infrastructure implemented
None
Silicon Validation (SiVal)
Yes
Emulation Targets

[ ] None
[ ] CW310
[x] Hyperdebug + CW310

Contact person
No response
Checklist
Please fill out this checklist as items are completed. Link to PRs and issues as appropriate.

[x] Device-side (C) component developed

Currently, during ft_perso, the host write the RAW endorsed DICE certificate to flash_info pages.
When it needs to access them later on, the certificate length is calculated by parsing the header (1 or 2 bytes). This design works for X509 but not CWT-CBOR since there's no such information in some CBOR types (map, array specifically).
Ref:

https://cs.opensource.google/opentitan/opentitan/+/master:sw/device/silicon_creator/manuf/base/ft_personalize.c;l=627
https://cs.opensource.google/opentitan/opentitan/+/master:sw/device/silicon_creator/manuf/base/ft_personalize.c;l=316

I'm proposing to change the certificat storing format as below. The certificate is prepended by a 16 bits header followed by the ASCII  characters of the certificate name, followed by the certificate body.
This format is used already when transfering tbs & certificates from host vs. device.
The original X509 parsing logic can be reused for cross checking the result from the Cert Header.
   *  d15                                         d0
   * +-------------+--------------------------------+
   * | 4 bit       |            12 bits             |
   * +-------------+--------------------------------+
   * | name length |12 bits total cert payload size | <-- Cert Header
   * +-------------+--------------------------------+
   * |             cert name string                 |
   * +----------------------------------------------+
   * |                   cert                       |
   * +----------------------------------------------+

@timothytrippel for viz

I have a patch for that already. Can file a PR soon.

This sound reasonable to me. It looks like #24951 is the associated fix?

This sound reasonable to me. It looks like #24951 is the associated fix?

Yes, that's it.

Update the new storing format based on the conclusion.
   *  d15                                         d0
   * +-------------+--------------------------------+
   * | 4 bit type  |   12 bits total object size    | <-- Object Header
   * +-------------+--------------------------------+
   * | name length |12 bits total cert payload size | <-- Cert Header
   * +-------------+--------------------------------+
   * |             cert name string                 |
   * +----------------------------------------------+
   * |                   cert                       |
   * +----------------------------------------------+