Inconsistent version numbering on Github releases and image tags

Describe the bug
On github, the latest release is v0.3.3, released today.
On Docker Hub, the latest tag is 0.3.4, pushed about a day ago, and 0.3.3 was pushed about a month back.
Additionally, the latest tag with an image for all three architectures is 0.3.2, the 0.3.3 and 0.3.4 tags only have amd64 images.
To Reproduce
Steps to reproduce the behavior:

Check releases on https://github.com/plunder-app/kube-vip/releases
Check image tags on https://hub.docker.com/r/plndr/kube-vip/tags?page=1&ordering=last_updated

Expected behavior
Consistency between release versions and image tags on Docker Hub.
Release v0.3.3 should have a 0.3.3 image tag, with properly pushed images for amd64, arm64, and arm/v7

This is now completely automated through GitHub Actions! 🔥


joinEager is seem not optimized

Assume I have 2 tables in Postgresql, User & Company. User is belong to 1 Company.
Then I want to filter User by Company, so I made query like this:
const users = await User.query()
    .joinEager('company')
    .where('company.id', 'C0000003');

The result return as I expected, but I want to know how the sql query is built, so I follow this comment to print out the sql. Here what I got:
select "user"."id" as "id", "user"."companyId" as "companyId", "company"."id" as "company:id", "company"."name" as "company:name"
from "user" left join (select "company".* from "company") as "company" on "company"."id" = "user"."companyId"
where "company"."id" = ?'

I notice the the query join user with  (select "company".* from "company") as "company". So Postgres have to make the query select "company".* from "company" before joining. You think it's a bit redundant?
Meanwhile this can be optimized to just from "user" left join "company". What do you think about this?
BTW I love your work on this, keep it up guys!

In that query, the select is redundant and shouldn't be there. I'll take a look. Postgres query planner does get rid of that select though. You can try running both versions with explain analyze and you'll see that the same plan gets generated. Other databases may end up running tgat query though

By the way, you can just chain .debug() to any query to see what gets executed

I'm pretty sure that execution time difference is random fluctuation. Did you try running both of those something like 1000 times and taking an average?

It can also be a constant addition, so every query will be 0.1ms slower, which shouldn't be an issue. You should try to analyze the queries with a larger real-life dataset.

I've just tried a few times, also my dataset is quite small, so I think I'll try later on a larger data-set.
So if it really is a constant of 0.1ms slower, it shouldn't be an issue.
Thanks


Modified test suite to use Tor, to improve reliability

Modified test suite to use Tor as proxies for the requests against scholar.

Closing this. Tried to address the issues raised at https://github.com/OrganicIrradiation/scholarly/pull/88


Authorizing Windows user instead of linking account.

Heyo
This project appears to be exactly what I need, however I have no forms authentication in my application in contrast to your examples.
What I'm doing
I have a website that uses windows authentication, mobile clients that use webapi token-based oauth security, and an integration api that uses a simliar api-key token-based security.  The windows users accounts exist in a database which I need to query to check that the authenticated windows user has access to the application.  This is preferred over using AD groups in Authorize attributes.
I'm considering splitting some of these back-end concerns up, but for now they're all serviced by one web server
Where I'm at
If request isn't successfully authenticated through the Owin pipeline, I get redirected to the virtual endpoint /Windows/Login, which seems to be where the WindowsLoginHandler comes into play.  The flow works, triggering a 401 challenge.  On successful authentication, I'm sent back through the WindowsLoginHandler.  I have an authenticated LoginUserIdentity, but my session doesn't have a userId yet so I'm sent through WinLoginAsync which appears to be attempting to redirect to my Account/WindowsLogin endpoint.
Your flow here redirects them to a login form.  I need to auto log them in if their account exists in my db.  I'm attempting to just do this work in AccountController.Windows' WindowsLogin endpoint, but I never get there.
What I'm asking
I guess I'm wondering if this could be done in a simpler fashion since I don't need to redirect my users to login forms.  Or, do you have any thoughts why ExecuteController may not be hitting my endpoint?
Thanks!

Hi,
The redirect to login form occurs only if LogonUserIdentity is not authenticated, But you say:

On successful authentication, I'm sent back through the WindowsLoginHandler. I have an authenticated LoginUserIdentity, but my session doesn't have a userId yet so I'm sent through WinLoginAsync

So you are hitting this line, which will execute WindowsLogin action, correct ?
But again you say:

Your flow here redirects them to a login form. I need to auto log them in if their account exists in my db.

So how is it that you are redirected to login form, as you should hit this line. which passed the point of redirecting to the login form ?

I may not have described correctly what is happening.  The good news is, I resolved my issue.  Since I'm redirecting to a login endpoint and not posting to one from a login form, I shouldn't have a ValidateAntiForgeryToken attribute on my endpoint.  It's working great now!
Thanks!

Thanks for the feedback!


feat: add environment variables config to beanstalk deployments

Issue #, if available:
DOTNET-4809
Description of changes:
add environment variables config to beanstalk deployments
Introduce new KeyValue type that supports a Dictionary.
Updated UX to ask user for key value pairs with ability to Add, Update and Delete
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Can you add a new config to https://github.com/aws/aws-dotnet-deploy/tree/main/test/AWS.Deploy.CLI.Common.UnitTests/ConfigFileDeployment/TestFiles/UnitTestFiles and add a unit test with a config file that has a key-value pair.
Make sure you add a new config file and not edit an existing one, since the existing files are also used in integ tests


⚠ Bofrost.at has degraded performance

In 35d28bb, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1701 ms

Resolved: Bofrost.at performance has improved in d40787c.


[GHSA-6h86-9r5g-f2h5] Cross-site scripting (XSS) vulnerability in includes...

Updates

Affected products
Source code location
Summary

Comments
Add Composer package

Same as https://github.com/github/advisory-database/pull/4969

Here are the missing version ranges:
  "affected": [
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "mediawiki/core"
      },
      "ranges": [
        {
          "type": "ECOSYSTEM",
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.21.9"
            }
          ]
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "mediawiki/core"
      },
      "ranges": [
        {
          "type": "ECOSYSTEM",
          "events": [
            {
              "introduced": "1.22.0"
            },
            {
              "fixed": "1.22.6"
            }
          ]
        }
      ]
    }
  ],


Invisible buttons and misalignments everywhere

Description
After updating to version 133, minimize and maximize buttons are invisible. The tablet mode for some reason is enabled, and the searchbox is misaligned when is focused
Include screenshot / video recording if possible.
Configuration

Firefox Version: 133
OS: Windows 11
Tweaks enabled:

Could you try to update to the latest commit of the theme. The tab height should be fixed now, though I cannot replicate the other issues.

Alternatively, adding back the Mica option (removed with 708e4e8) and enable widget.windows.mica and browser.theme.native-theme in about:config, the window control will now appear everytime the browser window is active.

That is beautiful. It’s good to see it back in 133.
@bmFtZQ  A little off-topic for this issue, but would you be able to restore the mica tweak again?

Could you try to update to the latest commit of the theme. The tab height should be fixed now, though I cannot replicate the other issues.

yeah, it's now fixed. updating fixed the other stuff too...
and yes, I agree, restore the mica tweak please!


hotfix (tester) - Easter Island & Haiti Windows time zone

The windows tester systematically fails because a new windows time zone entry was added for the Easter Island.
https://blogs.technet.microsoft.com/dst2007/2016/03/23/time-zone-update-for-chile-and-haiti/
This PR fixes the two functions involved.  (tzDatabaseNameToWindowsTZName and windowsTZNameToTZDatabaseName). They're gonna be deprecated in next rlz but they still need to be maintained.
reference for the names:

"Pacific/Easter": https://en.wikipedia.org/wiki/Pacific/Easter.
"Easter Island Standard Time": value from windows itself.

Haiti is also concerned (a bug can hide another bug) "Haiti Standard Time". But Idon't know the identifier in the Time zone database ?

win_32_64 passed, we need auto-merge toogled on ASAP thx.

linux_64_64 failure is unrelated, the demand is still valid.

Auto-merge toggled on

@MartinNowak don't forget to cherry pick in stable ;)

I opened #4321 to cherry-pick the change into stable branch.

Nice. It' important for me to fix the hot stuffs before I leave. My daughter gets a bit angry otherwise...


Change input format from all DateTimeFields.

Some fields were not covered yet.
Issue #26

Thanks so much for this. The patch has just been outdated by more recent changes (I now have PayPalDateTimeField which encapsulates this and other logic). Any chance you could update your patch?

Sure. I will update it

I merged the new commits into my branch.

Thanks so much, this is merged now, and in release 0.2.5


Set DataDecodedParameter value as unknown

The parameter value can be of any type
Sets type as a required field in the JSON schema

Coverage remained the same at 87.592% when pulling 0a173e0c7b1f525fc4e0d06cab32b63d18da4abf on fix_data_decoded_parameter_schema into f46ee2afffe1b0a8f1414c7e8e0318c204cc0fc7 on main.

Coverage remained the same at 87.592% when pulling 0a173e0c7b1f525fc4e0d06cab32b63d18da4abf on fix_data_decoded_parameter_schema into f46ee2afffe1b0a8f1414c7e8e0318c204cc0fc7 on main.


fv3ift.emulation: add TensorFactory abstraction

This refactor prepares for temperature scaled transformations. Since these tranforms will depend on data, I need to separate the config layer from the actual transform object. The config objects satisfy the TransformFactory interface and the transforms implement TensorTranform.
The diff is somewhat large because the transform object was coupled to the models, losses, and top-level config object...I tried to remove this coupling where it was easy.

I was kind of confused by the PR description that said "I need to separate the config layer from the actual transform object.". Is the intent that the config is still needed at least to use config.build_transform at the start but from then on the config is no longer needed to do stuff using the transform?

The basic struggle is that the Transform can no longer be represented in yaml config since it will need to depends on data. The TransformFactory is the yaml-able object.


[CORE][SPARK-10527]: Minor enhancement to evalutate debugstring only when log level is debug in DAGScheduler

Merged build triggered.

Merged build started.

Test build #42233 has started for   PR 8678 at commit e4c4c10.

Test build #42233 has finished for   PR 8678 at commit e4c4c10.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class SparkHadoopWriter(jobConf: JobConf)
class BlockRDD[T: ClassTag](sc: SparkContext, @transient val blockIds: Array[BlockId])
class ZippedWithIndexRDD[T: ClassTag](prev: RDD[T]) extends RDD[(T, Long)](prev)
class Checkpoint(ssc: StreamingContext, val checkpointTime: Time)
abstract class InputDStream[T: ClassTag] (ssc_ : StreamingContext)
abstract class ReceiverInputDStream[T: ClassTag](ssc_ : StreamingContext)

Merged build finished. Test PASSed.

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

@srowen thanks for the detailed explanation, passed the value directly

Merged build triggered.

Merged build started.

Test build #42271 has started for   PR 8678 at commit 42bf3ef.

I don't think this is worth doing. It makes the code harder to read, and the string computation is not at all expensive. This isn't even a hot code path, so the reduce in scheduling delay here is extremely negligible. I would prefer to close this issue.

@andrewor14  for the "harder to read part" initially i had changed the val to a def ; the rest was the same , I am sure it was not affecting the readability if thats your concern here, but @srowen  suggested to pass the value directly (don;t know why)
I can revert it to my original change if you prefer that way.
"The reduce in delay is extremely negligible"
agreed! ,  but still it is there !

Test build #42271 has finished for   PR 8678 at commit 42bf3ef.

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

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

Merged build finished. Test PASSed.

No, it's never OK to sacrifice readability for a performance improvement that doesn't actually matter. Even changing it to a def adds complexity because now you have nested methods. Thanks for your work, but please close this PR.

@andrewor14 I agree with your comment on the first revision, but just inlining the string argument as the latest commit does seems to simplify the code a tiny bit, and maybe gain a negligible bit of speed. Are you looking at the result after the second commit? i'm also fine closing this as it's pretty trivial, but I don't mind the change in its second form.

I just think having a match evaluated in a method parameter makes the code look more complicated. Elsewhere in Spark we try to simplify the existing code in the opposite direction, so I see this as some sort of regression.
If it's actually a significant source of performance improvement then I would be OK with sacrificing readability, but that's not the case here.

OK I support closing it too. It's negligible.

@andrewor14 , @srowen thanks for the feedback. I was actually working on a very low latency spark job (300 - 500 ms) , and thought it better to improve obvious things. It might not be applicable for wider audience, as suggested,  closing this PR


run demo.py for video output error

python demo.py --video-input /workspace/xdy/CenterNet2-master/output/video/2021111616185900.mp4
[12/09 01:25:50 detectron2]: Arguments: Namespace(config_file='/workspace/xdy/CenterNet2-master/projects/CenterNet2/configs/CenterNet2_DLA-BiFPN-P5_640_16x_ST.yaml', webcam=False, video_input='/workspace/xdy/CenterNet2-master/output/video/2021111616185900.mp4', input=None, output='/workspace/xdy/CenterNet2-master/output/val/', confidence_threshold=0.3, opts=[])
WARNING [12/09 01:25:50 d2.config.compat]: Config '/workspace/xdy/CenterNet2-master/projects/CenterNet2/configs/CenterNet2_DLA-BiFPN-P5_640_16x_ST.yaml' has no VERSION. Assuming it to be compatible with latest v2.
Loading pretrained DLA!
0%|                                                                                | 0/7501 [00:01<?, ?it/s]
Traceback (most recent call last):
File "/workspace/xdy/CenterNet2-master/projects/CenterNet2/demo.py", line 185, in
for vis_frame in tqdm.tqdm(demo.run_on_video(video), total=num_frames):
File "/root/miniconda3/envs/detectron2/lib/python3.9/site-packages/tqdm/std.py", line 1180, in iter
for obj in iterable:
File "/workspace/xdy/CenterNet2-master/projects/CenterNet2/predictor.py", line 152, in run_on_video
yield process_predictions(frame, self.predictor(frame))
File "/workspace/xdy/CenterNet2-master/projects/CenterNet2/predictor.py", line 115, in process_predictions
vis_frame = video_visualizer.draw_instance_predictions(frame, predictions)
File "/workspace/xdy/detectron2/detectron2/utils/video_visualizer.py", line 109, in draw_instance_predictions
else [y[0] for y in filter(lambda x: x[1], zip(labels, visibilities))]
TypeError: 'NoneType' object is not iterable
I run demo.py for video output,but something wrong here.But when I run demo.py with Base-CenterNet2.yaml,it work.how can i fix it?

There always wrong  when I used the argument "--opts MODEL.WEIGHTS"

Hi @Dannyxu1031 have you figured the issue out?
I find that the NoneType problem comes from the visibilities--labels--duration and finally turns out to be the predictions dict not including the  ID_duration key:
durations = predictions.ID_duration if predictions.has("ID_duration") else None
the prediction of model CenterNet2_R50_1x is:
<class 'detectron2.structures.instances.Instances'> Instances(num_instances=39, image_height=542, image_width=807, fields= [pred_boxes: Boxes(tensor([[241.1353, 139.6680, 375.6159, 197.3571],         [604.5829, 141.3495, 656.8168, 165.8259],         [276.3841, 225.3874, 573.3428, 483.9016],         [372.2970, 148.4080, 477.9282, 191.1354],         [501.4162, 141.7366, 545.5916, 169.5368],         [763.7508, 139.8452, 797.9053, 175.4382],         [542.8406, 134.1765, 607.2749, 168.4592],         [  2.0638, 142.5656,  79.9496, 184.2120],         [337.7661, 134.5329, 411.2755, 162.6599],         [111.1094, 115.5351, 126.5559, 124.9969],         [125.5042, 115.0389, 151.5087, 129.8213],         [739.4490, 141.0512, 779.1739, 161.4336],         [ 79.7839, 117.6921, 110.8978, 136.0438],         [716.1653, 140.6606, 744.0775, 161.7662],         [212.7217, 139.5664, 271.5062, 177.7411],         [696.8834, 140.5839, 742.4159, 162.4066],         [174.0790, 120.8204, 210.0613, 135.5340],         [214.9684, 124.3780, 231.7171, 134.9491],         [542.7147, 137.1107, 575.5455, 167.6913],         [469.0678, 170.3258, 543.6485, 238.9222],         [180.7123, 123.1844, 211.9622, 135.1333],         [105.5332, 115.1088, 125.4691, 125.6428],         [472.3793, 141.9874, 545.4722, 170.2103],         [473.3885, 147.4614, 513.0460, 170.4382],         [  2.4199, 142.6647,  36.9965, 184.3582],         [336.5692, 136.4574, 377.8730, 160.0500],         [280.0128, 124.7579, 317.7306, 138.9644],         [171.5089, 116.8886, 201.7563, 134.1216],         [696.7322, 141.3676, 729.3130, 162.5914],         [469.0678, 170.3258, 543.6485, 238.9222],         [771.5851, 130.7168, 795.5539, 144.2596],         [ 81.7277, 115.2408, 108.9647, 131.9405],         [695.9254, 129.7966, 704.5533, 141.3309],         [113.4691, 114.2615, 143.1823, 127.2237],         [472.9387, 153.7226, 480.4456, 168.7634],         [469.2350, 196.9153, 544.2471, 237.9603],         [118.9201, 115.1781, 143.0161, 128.7013],         [188.2796, 124.4722, 214.7957, 135.0403],         [ 60.7254, 150.7339,  81.0295, 181.7287]])),  scores: tensor([0.9408, 0.9379, 0.9376, 0.9237, 0.8962, 0.8423, 0.8215, 0.8173, 0.7885,         0.7645, 0.7584, 0.7530, 0.7295, 0.7114, 0.7082, 0.6648, 0.6562, 0.6121,         0.5982, 0.5779, 0.5294, 0.5046, 0.4942, 0.4880, 0.4769, 0.4741, 0.4723,         0.4706, 0.4571, 0.4199, 0.4031, 0.4021, 0.3771, 0.3743, 0.3703, 0.3409,         0.3377, 0.3323, 0.3114]),  pred_classes: tensor([ 2,  2, 13,  2,  2,  2,  2,  2,  2,  2,  2,  2,  2,  2,  2,  2,  2,  2,          2, 13,  2,  2,  2,  2,  2,  2,  2,  2,  2, 56,  2,  2,  2,  2,  2, 13,          2,  2,  2])])

use --video-input instead of --input

use --video-input instead of --input

Hi, @surefyyq , you can change line 76 in detectron2/utils/video_visualizer.py from durations = predictions.ID_duration if predictions.has("ID_duration") else None to durations = predictions.ID_duration if predictions.has("ID_duration") else [1]*num_instances. And then reinstall detectron2 by python -m pip install -e CenterNet2. That works for me.

Thanks for your reply! I will try it.
------------------ 原始邮件 ------------------
发件人: "Liren @.>;
发送时间: 2022年4月24日(星期天) 下午5:44
收件人: @.>;
抄送: @.>; @.>;
主题: Re: [xingyizhou/CenterNet2] run demo.py for video output error (Issue #74)
Hi, @surefyyq , you can change line 76 in detectron2/utils/video_visualizer.py from durations = predictions.ID_duration if predictions.has("ID_duration") else None to durations = predictions.ID_duration if predictions.has("ID_duration") else [1]*num_instances. And then reinstall detectron2 by python -m pip install -e CenterNet2. That works for me.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Please how can I modify it so that it only detects people, I have not found the code to modify the label


Cannot read property 'browser' of undefined (latest version)

Platform
MacOS

NPM

Describe the bug
Cannot read property 'browser' of undefined
To Reproduce
Steps to reproduce the behaviour:

I only copied the code for the parallel scans from here:  https://www.npmjs.com/package/wappalyzer

I saved it to a file and only run the 'nodejs wpp.js'

See error

(node:71334) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'browser' of undefined     at new Wappalyzer (/private/tmp/node_modules/wappalyzer/index.js:5:39)     at /private/tmp/file.js:6:28     at Object.<anonymous> (/private/tmp/file.js:24:3)     at Module._compile (internal/modules/cjs/loader.js:956:30)     at Object.Module._extensions..js (internal/modules/cjs/loader.js:973:10)     at Module.load (internal/modules/cjs/loader.js:812:32)     at Function.Module._load (internal/modules/cjs/loader.js:724:14)     at Function.Module.runMain (internal/modules/cjs/loader.js:1025:10)     at internal/main/run_main_module.js:17:11 (node:71334) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) (node:71334) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Expected behaviour
JSON response containing the technology for each website.

Fixed in v6.0.4.

This should no longer be an issue in v6.0.6.

I am on 6.0.12 (the latest on npm) and still have this problem.

@zcaceres Can you show me to full trace?

Will try to repro, almost same trace I'd say as the one listed above.


[RESTEASY-2300] Blank Host Name still throws exception

Issue: https://issues.redhat.com/browse/RESTEASY-2300
Upstream PR: https://github.com/resteasy/Resteasy/pull/2436 https://github.com/resteasy/Resteasy/pull/2435

I'm closing this as there's no plan for releasing a new 3.12.x version, next one on the 3.x series will be 3.13.0.Final.


Save sequencer sample selection

Save the selected sample or samples for the sequencer. So if you select a sample in a sequencer section and then close and reopen a sequencer section, you don't have to select that sample again.
Love the project by the way.

Thanks @khaki32!
I've definitely thought about this as a workflow improvement, too. I'm a little hesitant to implement it as the default behavior, though - I could see people wanting the Sequencer to open up as a "clean slate" too, so maybe it would be nice to have a user setting to toggle this on/off.
As far as how it would work, would you want it to save the selected sample(s) at the Track level or on a Track Section basis?

I'm a little hesitant to implement it as the default behavior, though - I could see people wanting the Sequencer to open up as a "clean slate" too, so maybe it would be nice to have a user setting to toggle this on/off.

I agree, this would be good as customizable behavior. As far as the default setting goes, there could be an "X" button next to the sample dropdown to quickly clear the selected samples. As a nice comprise.

As far as how it would work, would you want it to save the selected sample(s) at the Track level or on a Track Section basis?

For me definitely at the track level, but that's just personal preference.

Going to start hacking on this - I can probably get out a version that stores the selected samples in local storage as a hold-over (will remember sample selections for a track while in the same browser until local storage/app data has been cleared), but longer term I'd love to build out some of the infrastructure for a generic user settings table and wire this up to it! (#40)

This should be out now - let me know if you run into any issues!

Cool! Works and looks great.

Just wanna comment that it's really nice that you did this with local storage! Saves it even after a few days.

Just wanna comment that it's really nice that you did this with local storage! Saves it even after a few days.

Glad to hear! I was thinking local storage should be pretty solid for something like this - the other implementation I was tossing around in my head is persisting records in a linking table in the database, but it seemed like too much work for very little payoff vs. something so simple to wire up with local storage!


Electricity price is set at VoLL unexpectedly

In this scenario some very strange price-setting behaviour occurs. It is a scenario that uses quite a lot of our more advanced features, like DSR in industry, external coupling and availability curves for interconnectors.
The strange behaviour is that in unexpected hours the electricity price is set at the VoLL of 3000 euros/MWh, which suggests that the total supply in those hours is insufficient to cover the total demand. However, when I look at those hours, this does not seem to be the case.
Example for hour 15
The prices on the interconnectors are the following:

The interconnector to Norway is importing, all the others are exporting. The only flexible power plants are the waste CHPs (with and without CCS) and the hydrogen power plants (turbine and CCGT). The hydrogen turbine is not running at full capacity and has a lower price than the other interconnectors (DE, BE, DK and UK), which are priced at 150 euros/MWh. I would therefore expect the hydrogen turbine to set the price at 135.13 euro/MWh.
Would you be able to have a look at this please @antw? Perhaps it has something to do with the effect of availability curves on the calculation of the intersection of total demand and supply?

I think this is due to a mistake when calculating the price curve. We check if the most expensive dispatchable is fully-loaded, and when it is treat that as a deficit.
# (simplified)
deficit = dispatchable.load == dispatchable.max_load

However, that failed to account for the possibility that the most expensive dispatchable may not have any availability in the hour; its maximum permitted load was zero. In that case, both the load and max_load are zero, and as they're both zero, they're equal to each other.
I changed the approach in Merit to find the most expensive dispatchable with non-zero max_load, and instead use that to figure out if there is a deficit:
https://user-images.githubusercontent.com/4383/200919040-958cb059-1321-499e-9c1c-636269abc92d.mp4
https://user-images.githubusercontent.com/4383/200919052-0ac918b1-ae96-4aab-9283-a928e2ff63fa.mp4
@mabijkerk Does this look better to you?

It does not look like it solves all entire issue: I would expect to see fewer hours in which the price is set by the VoLL. Now it looks like there are more hours which are considered a deficit.
Another remark: the "before" looks different for me on pro now.

What about the edge case where the most expensive dispatchable is exactly used to its maximum capacity, but no additional demand has to be served?
Would in that case for the most expensive dispatchable with non-zero max_load apply that load and max_load are equal to each other and the price be set at VoLL? Because in that case I would rather expect the price to be set by the most expensive dispatchable.

Finally, I would only expect a VoLL price to occur when inflexible demand cannot be served. So if the most expensive power plant (say marginal costs are 120 euros/MWh) is running at full capacity to serve a flexible demand, such as an export for 150 euros/MWh willingness to pay, then I would not expect to see a VoLL. In this case the export interconnector should set the price at 150 euros/MWh.

What about the edge case where the most expensive dispatchable is exactly used to its maximum capacity, but no additional demand has to be served?
Finally, I would only expect a VoLL price to occur when inflexible demand cannot be served.

Thanks, I'll look into this and agree with your comments. Checking if the most expensive dispatchable load == max_load was quite sensible before we had flexible consumers, but perhaps isn't the best approach these days. This may indeed be why we still have more hours at the fallback price than there are blackout hours.


Add 'extras' virtual package to fix kernel upgrade fallback from aufs to devicemapper

Signed-off-by: Matt Bentley<EMAIL_ADDRESS>

PR for discussion of https://github.com/docker/docker/issues/10859

hmmm ping @tianon idk what the virtual extras do

https://packages.debian.org/sid/linux-image-extra-virtual is a 404 -- where does this package virtual come from?  Is it Ubuntu-specific?

@tianon - yes, it is Ubuntu specific but so are all of the linux-image-extra-* packages as far as I know.

Oh right, the || true makes sure that works regardless.
However, this is potentially more dangerous than the other one is -- this package will install linux-image-generic (http://packages.ubuntu.com/vivid/linux-image-generic), which could then install a different kernel from what the user is currently using/intended to use.  I guess we could argue that if they care about the way their system is configured, they shouldn't be running a random "install" script off the internet (which is what I'd rather encourage anyhow -- IMO this script needs to go away completely at some point).

@unclejack what do you think?

@tianon Perhaps we should prompt for the installation of the generic-extra kernel when detecting the virtual kernel without aufs on Ubuntu?

That sounds reasonable to me! :+1:

Can you please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "curl-install-fix" git@github.com:mbentley/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~2
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

This will update the existing PR, so you do not need to open a new one.

I added some logic to check and see if the following were true:

The current kernel was a -generic kernel
That a linux-image-*-generic package was installed

This should verify that the packages linux-image-extra-$(uname -r) and linux-image-extra-virtual won't install a different kernel than what is currently running and ensure that the package is really installed and that someone just don't have -generic in the name of their custom compiled kernel.
If the kernel doesn't match, it will just give a warning and suggest installing linux-image-virtual (which will install the linux-image-generic package) and linux-image-extra-virtual for proper AUFS support.

:+1: for the new logic! :smile:

LGTM
cc @jfrazelle @unclejack

@mbentley I think this needs a rebase; project/install.sh was moved to hack/install.sh

thanks @thaJeztah.  Rebased.

LGTM

Same issue but the docker OS is centos7. How to fix it there?

Are you certain that you started with aufs support on CentOS 7?  I wouldn't think so unless you compiled your own kernel as CentOS 7 and RHEL 7 are not shipping with aufs support to the best of my knowledge.


[#217] Initial Beta Sign up

Extracted conversation from main chat
Added Sample conversation flow
Added state machine for supplying email/question
TODO: Send question + Email to BE for storage

[Feedback Requested]
[#217]

So after I talked to @lancelafontaine we came up with an idea how to have all the codes in our repo with minimum duplication.

instead of making a new directory for duplicated front-end infrastructure, we change the config in the existing infrastructure with an environment variable, let's say CJL_RELEASE. We build the page within the infra. When the variable is set to beta, the CI/CD is gonna pick up the code and build based on the config (i.e. build the beta landing page ONLY, and ignore all other pages and routing)
create beta_backend_service with independent database
our CD is gonna have two configs: 1) it builds everything on the front-end except the beta page, and builds every service except beta_backend_service, and associate to capstone.cjl.com; 2) it builds only the beta page on FE and only the beta_backend_service, and associate to procezeus.ca

@arekmano

Clarification for 3: we would still only have on CI/CD pipeline. Builds would run tests for all services (beta, non-beta) and deploy both to our server.

That seems like significant effort for a change that we will essentially "dispose" of.
I think it makes sense to have both the beta page up as well as our application. Beta would be for public, application page would be for demos, internal testing, etc.
Configuration + pipeline changes do not add user value IMO and we should stick to what works already.

For these reasons I think it makes sense to decouple them "nearly" entirely, and have the beta be a seperate entity. Something like nginx routing should discriminate what we show users. (e.g. procezeus.ca -> beta page, capstone.cjl -> application)


feat: add SnapPicture functionality

Get a snapshot from the camera.
The data returned by the camera is validated with MIME sniffing [1], and returned in a byte slice.

https://mimesniff.spec.whatwg.org/

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 0% with 17 lines in your changes missing coverage. Please review.

Project coverage is 76.41%. Comparing base (6aebe08) to head (13bfe2e).

Files with missing lines
Patch %
Lines

fi9800p.go
0.00%
15 Missing :warning:

fi8919w.go
0.00%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##             main       #5       +/-   ##
===========================================
- Coverage   91.01%   76.41%   -14.60%
===========================================
  Files           5        5
  Lines          89      106       +17
===========================================
  Hits           81       81
- Misses          8       25       +17

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


x11: Fix disconnects if WITH_XCURSOR is set to OFF

Fix disconnects if WITH_XCURSOR is set to OFF. In that case xf_Pointer_New currently returns FALSE causing a disconnect.

From my perspective, what is written in the description here should actually be in the body of the commit message, as otherwise it gets lost (when backporting, or viewing commits locally (not on github)).

@pnowack updated the description 👍

Change itself looks good to me.

@pnowack updated the description +1

I think you forgot to force push your changes.


Remove API Endpoint - Linearity Injection Data

Scope includes Unit Testing and testing of the DELETE endpoint:
https://api-easey-dev.app.cloud.gov/qa-certification-mgmt/swagger/#/Linearity Injection/LinearityInjectionWorkspaceController_deleteLinearityInjection

Test Case: TC848

Test Passed


Microsoft.Azure.Cosmos	3.9.1

Type: Incorrect
Summary:
Microsoft.Azure.Cosmos	3.9.1
Details:
Declared license was listed at Other, but project site indicates license is MIT
Resolution:
History of license on project site indicates initial license was MIT and has not changed
Affected definitions:

Microsoft.Azure.Cosmos 3.9.1

Just for reference, the license link used to point to a EULA, but recently stopped working. I had opened an issue to get it fixed and they changed it to MIT. I opened an issue with ClearlyDefined service to get it to stop auto declaring OTHER for this link since they changed what license it points to.
https://github.com/clearlydefined/service/issues/746


json: Playground simplifications

For #3580

Background

Change List

Address comments in original PR
I think the playground is starting to look quite clean.

Coverage increased (+3.1%) to 82.555% when pulling 97147036f958045f340068b9e119fffa665a02e3 on ib/playground-simplifications into f20a4a37200428917605b5d52aadff9b433d13b1 on master.


Add helper constants for nonmutating method names

For context https://github.com/rubocop-hq/rubocop-performance/pull/140/files#r439732580
Bullet number 4

and those ENUMERABLE_METHOD_NAMES, NONMUTATING_ARRAY_METHODS and NONMUTATING_HASH_METHODS into rubocop-asts AST::CollectionNode module?

But it is not really belongs to rubocop-ast, I was wrong. So opened pr here.

it is not really belongs to rubocop-ast, I was wrong.

Why? IMO all criteria that are independent of a particular cop, that can be factually said to be accurate outside of a context, should be in rubocop-ast, these included.

Ok. So is this file a good place for those constants https://github.com/rubocop-hq/rubocop-ast/blob/master/lib/rubocop/ast/node/mixin/method_identifier_predicates.rb ?
And if so, should I also add pedicate methods like nonmutable_array_method?, etc there?

I think so

Opened on rubocop-ast https://github.com/rubocop-hq/rubocop-ast/pull/38


Loading checkpoints for inference

Which checkpoints in drive link you provided will load correctly in default MDefDETR model without any errors? Im getting missing/unexpected keys errors.

Hi @KaleemW,
Please try loading MDef_DETR_r101_epoch20.pth checkpoints. If you will still get an error then please post the full error message along with the process you are following for loading the weights here. I hope it will be helpful. Thank you

Thanks a lot. It worked. Just wanted to know one last thing that is there a cpu implementation available for this project. I ran successfully with cuda but without cuda it doesnt compile MSDA...

Thanks a lot. It worked. Just wanted to know one last thing that is there a cpu implementation available for this project. I ran successfully with cuda but without cuda it doesnt compile MSDA...

Thanks a lot. It worked. Just wanted to know one last thing that is there a cpu implementation available for this project. I ran successfully with cuda but without cuda it doesnt compile MSDA...

Hi @KaleemW,
Unfortunately, only GPU implementation is available at the moment.

Ok Sir! Thank You for your help.

@mmaaz60 hi could you tell me what is the inference speed of your model? and how to do batch inference to improve the efficiency? Thanks.

Hi @Edwardmark,
Thank you for your interest in our work. Please refer to the Table 10 of our paper for inference speed. Further, the batch inference implementation is available at modulated_detection.py.
I hope it will help. Thank You.


[Bug]: Installed on Ubuntu 23.10 GUI doesn't show readable letters

What happened?
After GIMP installation on Ubuntu with snap, the GU of the started program doesn't show any readable letters in menu and toolboxes.

What should have happened?
Fix this bug or explain how to fix this problem.
Output of snap info $snap_name
no output

Output of snap connections $snap_name
Schnittstelle             Plug                                             Slot                              Notizen
appstream-metadata        snap-store:appstream-metadata                    :appstream-metadata               -
audio-playback            firefox:audio-playback                           :audio-playback                   -
audio-record              firefox:audio-record                             :audio-record                     -
avahi-observe             firefox:avahi-observe                            :avahi-observe                    -
browser-support           firefox:browser-sandbox                          :browser-support                  -
browser-support           gimp:browser-support                             :browser-support                  -
camera                    firefox:camera                                   :camera                           -
content[gnome-42-2204]    firefox:gnome-42-2204                            gnome-42-2204:gnome-42-2204       -
content[gtk-3-themes]     firefox:gtk-3-themes                             gtk-common-themes:gtk-3-themes    -
content[icon-themes]      firefox:icon-themes                              gtk-common-themes:icon-themes     -
content[sound-themes]     firefox:sound-themes                             gtk-common-themes:sound-themes    -
content[gnome-42-2204]    firmware-updater:gnome-42-2204                   gnome-42-2204:gnome-42-2204       -
content[gtk-3-themes]     firmware-updater:gtk-3-themes                    gtk-common-themes:gtk-3-themes    -
content[icon-themes]      firmware-updater:icon-themes                     gtk-common-themes:icon-themes     -
content[sound-themes]     firmware-updater:sound-themes                    gtk-common-themes:sound-themes    -
content[gnome-3-38-2004]  gimp:gnome-3-38-2004                             gnome-3-38-2004:gnome-3-38-2004   -
content[gtk-2-engines]    gimp:gtk-2-engines                               gtk2-common-themes:gtk-2-engines  -
content[gtk-3-themes]     gimp:gtk-3-themes                                gtk-common-themes:gtk-3-themes    -
content[icon-themes]      gimp:icon-themes                                 gtk-common-themes:icon-themes     -
content[sound-themes]     gimp:sound-themes                                gtk-common-themes:sound-themes    -
content[gnome-42-2204]    snap-store:gnome-42-2204                         gnome-42-2204:gnome-42-2204       -
content[gtk-3-themes]     snap-store:gtk-3-themes                          gtk-common-themes:gtk-3-themes    -
content[icon-themes]      snap-store:icon-themes                           gtk-common-themes:icon-themes     -
content[sound-themes]     snap-store:sound-themes                          gtk-common-themes:sound-themes    -
content[gnome-42-2204]    snapd-desktop-integration:gnome-42-2204          gnome-42-2204:gnome-42-2204       -
content[gtk-3-themes]     snapd-desktop-integration:gtk-3-themes           gtk-common-themes:gtk-3-themes    -
content[icon-themes]      snapd-desktop-integration:icon-themes            gtk-common-themes:icon-themes     -
content[sound-themes]     snapd-desktop-integration:sound-themes           gtk-common-themes:sound-themes    -
cups-control              firefox:cups-control                             :cups-control                     -
desktop                   firefox:desktop                                  :desktop                          -
desktop                   firmware-updater:desktop                         :desktop                          -
desktop                   gimp:desktop                                     :desktop                          -
desktop                   snap-store:desktop                               :desktop                          -
desktop                   snapd-desktop-integration:desktop                :desktop                          -
desktop-launch            snap-store:desktop-launch                        :desktop-launch                   -
desktop-legacy            firefox:desktop-legacy                           :desktop-legacy                   -
desktop-legacy            firmware-updater:desktop-legacy                  :desktop-legacy                   -
desktop-legacy            gimp:desktop-legacy                              :desktop-legacy                   -
desktop-legacy            snap-store:desktop-legacy                        :desktop-legacy                   -
desktop-legacy            snapd-desktop-integration:desktop-legacy         :desktop-legacy                   -
fwupd                     firmware-updater:fwupd                           :fwupd                            -
gsettings                 firefox:gsettings                                :gsettings                        -
gsettings                 firmware-updater:gsettings                       :gsettings                        -
gsettings                 gimp:gsettings                                   :gsettings                        -
gsettings                 snap-store:gsettings                             :gsettings                        -
gsettings                 snapd-desktop-integration:gsettings              :gsettings                        -
hardware-observe          firefox:hardware-observe                         :hardware-observe                 -
home                      firefox:home                                     :home                             -
home                      gimp:home                                        :home                             -
joystick                  firefox:joystick                                 :joystick                         -
login-session-observe     snapd-desktop-integration:login-session-observe  :login-session-observe            -
mount-control             firefox:host-hunspell                            :mount-control                    -
network                   firefox:network                                  :network                          -
network                   gimp:network                                     :network                          -
network                   snap-store:network                               :network                          -
network-bind              firefox:network-bind                             :network-bind                     -
opengl                    firefox:opengl                                   :opengl                           -
opengl                    firmware-updater:opengl                          :opengl                           -
opengl                    gimp:opengl                                      :opengl                           -
opengl                    snap-store:opengl                                :opengl                           -
opengl                    snapd-desktop-integration:opengl                 :opengl                           -
packagekit-control        snap-store:packagekit-control                    :packagekit-control               -
personal-files            firefox:dot-mozilla-firefox                      :personal-files                   -
removable-media           firefox:removable-media                          :removable-media                  -
screen-inhibit-control    firefox:screen-inhibit-control                   :screen-inhibit-control           -
shutdown                  firmware-updater:shutdown                        :shutdown                         -
snap-themes-control       snapd-desktop-integration:snap-themes-control    :snap-themes-control              -
snapd-control             snap-store:snapd-control                         :snapd-control                    -
system-files              firefox:etc-firefox                              :system-files                     -
system-files              snapd-desktop-integration:snap                   :system-files                     -
system-packages-doc       firefox:system-packages-doc                      :system-packages-doc              -
u2f-devices               firefox:u2f-devices                              :u2f-devices                      -
unity7                    firefox:unity7                                   :unity7                           -
unity7                    gimp:unity7                                      :unity7                           -
upower-observe            firefox:upower-observe                           :upower-observe                   -
upower-observe            firmware-updater:upower-observe                  :upower-observe                   -
wayland                   firefox:wayland                                  :wayland                          -
wayland                   firmware-updater:wayland                         :wayland                          -
wayland                   gimp:wayland                                     :wayland                          -
wayland                   snap-store:wayland                               :wayland                          -
wayland                   snapd-desktop-integration:wayland                :wayland                          -
x11                       firefox:x11                                      :x11                              -
x11                       firmware-updater:x11                             :x11                              -
x11                       gimp:x11                                         :x11                              -
x11                       snap-store:x11                                   :x11                              -
x11                       snapd-desktop-integration:x11                    :x11                              -

Output of snap version
snap    2.62
snapd   2.62
series  16
ubuntu  23.10
kernel  6.5.0-28-generic

Relevant log output
no

Teminal output of app
no

@joefichi Are you using a GPU accelerated VM machine? (I get this exact bug when running some GTK based apps on VirtualBox with GPU acceleration enabled)


serve gets stuck every now and then

Note: for support questions, please use one of these channels:
https://forum.ionicframework.com/
http://ionicworldwide.herokuapp.com/
Short description of the problem:
It seems like ionic serve gteyx stuck for me when using it with webstorm.
I'd assume that is due to some file changes in a short ammount of time and scrupts not handling them very well.
What behavior are you expecting?
Either killing the current update and starting over or just finishing all of them.
Steps to reproduce:

have project
wildly save and edit files
see serve stopping

I waited 2 mins before taking this screenshot
http://i.imgur.com/qXsWVAy.png
EDIT: this is what happens when more file changes occur ten minutes later http://i.imgur.com/GN7KYIU.png
EDIT2: sometimes it seems like webpack just gets stuck without many file changes
Which @ionic/app-scripts version are you using?
$ ionic info

Your system information:

Cordova CLI: 6.2.0
Ionic Framework Version: 2.0.0
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.0.0
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 10
Node Version: v7.4.0
Xcode version: Not installed

Other information: (e.g. stacktraces, related issues, suggestions how to fix, stackoverflow links, forum links, etc)
Link to my project https://gitlab.com/pikandpeople/mobile-next

+1

I observe this issue to with my html files. When I updating html files I need to restart ionic serve to get updates
Cordova CLI: 6.5.0
Ionic Framework Version: 2.0.1
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.0.0
ios-deploy version: 1.9.0
ios-sim version: 5.0.13
OS: macOS Sierra
Node Version: v6.9.4

(same thing with Ionic App Scripts Version: 1.0.1)

I was getting the same errors as megobyte. I just downgraded to 1.0.0 for active development when using ionic serve.
Cordova CLI: 6.4.0
Ionic Framework Version: 2.0.0
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.0.0
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 10
Node Version: v6.9.2
Xcode version: Not installed

same thing as here Webpack frequently freezes when started?
what solved it for me: downgrade node to 6.9.5 (LTS)
my info:
Cordova CLI: 6.5.0
Ionic Framework Version: 2.0.1
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.0.1
ios-deploy version: 1.9.1
ios-sim version: 5.0.13
OS: OS X El Capitan
Node Version: v6.9.5
Xcode version: Xcode 8.2.1 Build version 8C1002

Can still confirm. Hangs when doing changes while another change is still ongoing (being compiled).
Your system information:

 ordova CLI: 6.5.0
Ionic Framework Version: 2.0.1
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.1.0
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 10
Node Version: v7.5.0
Xcode version: Not installed

Due to inactivity and inability to recreate, we're closing this issue.
Thanks,
Dan


Font mismatch when inserting diagrams into Google Docs by Google Workspace add-on

Preflight Checklist

[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe the bug
When I insert a diagram into Google Docs using the Workspace add-on, the image is displayed in a different font than drawio. If you use "Copy as Image" on app.diagrams.net and paste the diagram into Google Doc, the font will be the same as drawio.
Also, it occurs both in drawio's shape with text and in the PlantUML diagram embedded in drawio.
To Reproduce
Steps to reproduce the behavior:

Create a diagram with shapes containing text ("新" in Japanese) on app.diagrams.net.

Insert the PlantUML diagram into the drawio diagram using the following steps. "Arrange > Insert > Advanced > PlantUML..." The source code of PlantUML is as follows.

@startuml
listfonts 新
@enduml

Save the diagram to Google Drive
Create a Google Docs deck, with the Diagrams.net add-on installed.
Choose "Insert Diagram..." for the add-on, and insert saved diagram.

Expected behavior
The image shown in the Google Doc should match the font shown in app.diagrams.net

Screenshots
The image in Docs is using a different font. I'm unsure if this is a Theme font for the Doc, or a default font.

draw.io version (In the Help->About menu of the draw.io editor):

draw.io version v24.0.6

Desktop:

OS: Mac/Windows
Browser Chrome
Browser Version 122.0.6261.129 (Official Build) (x86_64)

I tested the problem in incognito/private mode with all browser extensions switched off, write "yes" below:

no; need to be logged into Google.

What format is the PlantUML output in?

The output format is .drawio or .drawio.svg.

What is the font family name of the correctly rendered text please?

The font that can correctly render the text of shapes on drawio is "Sawarabi Gothic" from Google Fonts. However, the drawio font does not seem to have any effect on the embedded PlantUML diagram.

This is expected. We host PlantUML on AWS lambda which provides limited scope for custom fonts.


Update Sheffield job advert.

Should close - https://github.com/hpc-social/jobs/issues/21
N.b. if the automation is going to process my new form entry this PR can probably be discarded.

The easiest thing to try is to delete the job from our sheet, and then you can add a new entry. Let me know if you'd like me to proceed.

As I've already submit the new listing to the form, deleting this seems wise.
I'll amend this PR now.

Just so you know, there is a Google form that backs this entire thing, so we can delete here for an immediate fix, but the larger fix is deleting from that Google Sheet (which I've done just now). Hopefully that will remove the job entirely.

Many thanks!


build errors on missing "//base"

When running ./configure on OS X with bazel 0.3.1-homebrew, these errors occur:
ERROR: /Users/jmhodges/src/github.com/tensorflow/tensorflow/tensorflow/core/BUILD:692:1: no such package 'base': BUILD file not found on package path and referenced by '//tensorflow/core:ios_tensorflow_test_lib'.
ERROR: /Users/jmhodges/src/github.com/tensorflow/tensorflow/tensorflow/core/kernels/BUILD:2211:1: no such package 'base': BUILD file not found on package path and referenced by '//tensorflow/core/kernels:android_tensorflow_kernels_no_rtti_lite_runtime'.
ERROR: /Users/jmhodges/src/github.com/tensorflow/tensorflow/tensorflow/core/kernels/BUILD:2211:1: no such target '//tensorflow/core:android_tensorflow_lib_lite_no_rtti_lite_runtime': target 'android_tensorflow_lib_lite_no_rtti_lite_runtime' not declared in package 'tensorflow/core' defined by /Users/jmhodges/src/github.com/tensorflow/tensorflow/tensorflow/core/BUILD and referenced by '//tensorflow/core/kernels:android_tensorflow_kernels_no_rtti_lite_runtime'.
ERROR: /Users/jmhodges/src/github.com/tensorflow/tensorflow/tensorflow/core/kernels/BUILD:2211:1: no such target '//tensorflow/core:android_proto_lib_no_rtti_lite_runtime': target 'android_proto_lib_no_rtti_lite_runtime' not declared in package 'tensorflow/core' defined by /Users/jmhodges/src/github.com/tensorflow/tensorflow/tensorflow/core/BUILD and referenced by '//tensorflow/core/kernels:android_tensorflow_kernels_no_rtti_lite_runtime'.
ERROR: Evaluation of query "deps((//... union @bazel_tools//tools/jdk:toolchain))" failed: errors were encountered while computing transitive closure.

This seems to be because of targets like "ios_tensorflow_test_lib" and, so on, depending on a "//base" that does not exist.
Off hand, I'm not able to figure out what this was trying to refer to. Perhaps it used to exist?

(Added bazel version to ticket: 0.3.1-homebrew)

This seems to have been introduced in ed87884e50e1a50f7dc7b36dc7a7ff225442bee0. Perhaps, it's a Google internal thing that just slipped in?

Same deal with //tensorflow/core:android_tensorflow_lib_lite_no_rtti_lite_runtime. It just doesn't exist.

Looks like this only happens when you try to build with CUDA.

@jmhodges Yes, those are some references that weren't meant to be interpreted by the external version of TF.
This is a duplicate of #4312, where you can find workarounds for the errors you're seeing -- essentially just revert/comment out the new functions.

Ah, it's been 10 days since that ticket. Is there no fix I could send up to handle this?

(I'm trying to confirm #4145 now that configure has some nice new CUDA smarts, and it's a little bit harder to confirm with these changes not in master. I'm sure I'm not the only external contributor trying to help and having to rediscover this!)


need redis protocol example like below

need redis protocol example like below
https://github.com/IceFireDB/redhub
possible to replace redhub internal networking stuff with gain?
i can sponsor a few coffees for this.
p.s. : i can sponsor more coffees if u can do pub/sub features on it.
i was looking at your project for a long time and it's really amazing for u to have done so far. thank you

Here you go, an example of using the Gain framework as a backend for the RedHub library:
https://github.com/pawelgaczynski/redhub
Not a perfect implementation, but it should be enough to understand how to use Gain.

cool! will test it out soon and revert with feedback.

redgain is a bit slower. why?
redis-benchmark -p 6380 -t get,set -n 100000 -q
redhub:
SET: 54288.82 requests per second, p50=0.431 msec
GET: 56022.41 requests per second, p50=0.423 msec
redgain:
SET: 50505.05 requests per second, p50=0.455 msec
GET: 53475.94 requests per second, p50=0.431 msec

@pawelgaczynski the version of server in example folder is eating around 10% of cpu core doing nothing. why?

@kolinfluence please provide the specifications of the host on which you tested it (CPU, Linux, kernel).

@pawelgaczynski

i5-4300U
Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz

cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"

Please provide the kernel versions of both machines. You can check it with uname -r command. Did you test redgain by always running the client and server on the same machine?

@pawelgaczynski sorry for the missed reply
i5-4300U
Linux  5.15.0-73-generic #80-Ubuntu SMP Mon May 15 15:18:26 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
i5-2400
Linux  5.15.0-69-generic #76-Ubuntu SMP Fri Mar 17 17:19:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

@pawelgaczynski can u pls clean up your version of redhub repo so i can try again? thx
# go mod tidy
go: finding module for package github.com/pawelgaczynski/gain
go: finding module for package github.com/rs/zerolog
go: finding module for package github.com/pawelgaczynski/redhub
go: finding module for package github.com/pawelgaczynski/redhub/pkg/resp
go: found github.com/pawelgaczynski/gain in github.com/pawelgaczynski/gain v0.3.1-alpha
go: found github.com/pawelgaczynski/redhub in github.com/pawelgaczynski/redhub v0.0.0-20230525152746-f48c208a8ab1
go: found github.com/pawelgaczynski/redhub/pkg/resp in github.com/pawelgaczynski/redhub v0.0.0-20230525152746-f48c208a8ab1
go: found github.com/rs/zerolog in github.com/rs/zerolog v1.29.1
go: redgain imports
	github.com/pawelgaczynski/redhub<EMAIL_ADDRESS>parsing go.mod:
	module declares its path as: github.com/IceFireDB/redhub
	        but was required as: github.com/pawelgaczynski/redhub
root@ubuntu-22:/home/ubuntu/Documents/Programs/redgain/example# grep -rnH 'IceFireDB' .
root@ubuntu-22:/home/ubuntu/Documents/Programs/redgain/example#

can you please modify this also?
https://github.com/tidwall/redcon
as it has more features

possible to advise what kernel version to use?

As io_uring is in active development it is worth using or at least testing performance on the latest possible kernel version. If my spare time permits, I intend to compare gain performance on all official kernel versions from 5.15 upwards.

isnt it more accurate to use a separate client / server to test?

Yes, it is. Client and server on one machine is hardly a common use case for web applications. If you test on separate machines then please indicate which one was the server.

@pawelgaczynski can u pls clean up your version of redhub repo so i can try again? thx

Done.

can you please modify this also?

I'll have a look at it and let you know. I can't promise if and when I'll be able to do it for you, but I'll try.

@pawelgaczynski
Intel(R) Core(TM) i3-8145U CPU @ 2.10GHz
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.2 LTS"
Linux ubuntu-22 5.19.0-43-generic #44~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon May 22 13:39:36 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
GOMAXPROCS=1 ./server
redhub:
SET: 149499.17 requests per second
GET: 150353.33 requests per second
redgain:
SET: 138869.59 requests per second
GET: 138159.72 requests per second
using single core performance test. redhub is faster. running redisbenchmark and server on same laptop.

@pawelgaczynski you dont have to benchmark against all kernel version it has been done here, which obviously says the higher kernel version, the faster io_uring performs
https://github.com/uNetworking/uWebSockets/issues/1603


Updated debug check for batch operation

Pull Request Template
Description
Cross partition batch operation can also contain partition key range id which causes the debug validation to fail. Updated validation to match backend.
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Please add a simple UT to cover it.


string enum member used as "computed enum member" types as number.

TypeScript Version:  all the ones in playground, latest is v4.1.0-dev20201001

Search Terms:
enum, incorrect type, computed enum, number, string
Code
enum Constants {
    hello = "Hello"
}
enum Potato {
    // THIS IS CONSIDERED A NUMERIC ENUM!!!!!
    h = Constants.hello
}
// Error: Type 'Potato' is not assignable to type 'string'.(2322)
const value: string = Potato.h;

// intellisense shows Potato.h = "Hello", but tsc compiles as though it's a number
console.log(Potato.h.toExponential());

Expected behavior:
Using a string enum member as the computed key in another enum should either be considered a string enum or be not allowed.
Actual behavior:
Potato.h is typed as number despite being assigned to a string. Potato.h.toExponential() passes type checking and throws runtime error.
Playground Link
Related Issues:
https://stackoverflow.com/questions/64145849/how-can-i-pass-an-enum-with-keys-of-another-string-enum-into-a-function-that-a

This behavior is 🤪
Found my way here after researching a different SO question.

Fixed by #50528.


SnackBar with Button

Can you add a button to your snackbar like in Android?

Should include 0-1 actions, not dismiss or cancel. One problem might be that it might block any potential FABs, so as such we should send an event to let users be able to shift their fabs when a snackbar is shown.
https://material.io/guidelines/components/snackbars-toasts.html#snackbars-toasts-specs

tskulbru,
Thats what I need. At least 1 action like https://github.com/zekunyan/TTGSnackbar.


fixed DS-2751 by checking for null

Fixed https://jira.duraspace.org/browse/DS-2751

+1 by inspection, haven't tested it.

+1 by inspection as well

As discussed in our DevMtg today, one of the questions is why/how null values get into this getISSNs() list to begin with. It looks like one of the classes that implements ISSNItemExtractor must be adding null values to the list. Here's the two possible culprits:

https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/java/org/dspace/app/sherpa/submit/MetadataAuthorityISSNExtractor.java
https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/java/org/dspace/app/sherpa/submit/MetadataValueISSNExtractor.java

I think the culprit is the MethadataAuthorityISSNExtractor. It expects every metadata value to have an authority value. We probably need a null check here: https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/java/org/dspace/app/sherpa/submit/MetadataAuthorityISSNExtractor.java#L40

Updated the null check to check at MethadataAuthorityISSNExtractor like @pnbecker suggested.

@tmguimaraes thanks, that is great! Have you tested it?
Your PR is now a little bit messy, containing two merge commits and a commit that is mostly reverting a previous one. Can you please file a clean PR containing only one commit that adds the null check?
To do so, I would create locally a new branch from DSpace/master, add the null check and push it using -f to the branch on github you used to create this PR. Changing the branch used to create this PR automatically updates the PR.

Only tested this change in my dspace 5.2 VM.
I'm currently installing DSpace 6 to test this.

@tmguimaraes thanks a lot for cleaning this PR!
+1 by inspection, looks obvious and good to me.

Tested on vagrant-dspace.

+1, obvious fix, thanks @tmguimaraes :-)

I'll merge this as it is such an obvious fix.


Use different OpenCV tracker

How can I use different a different OpenCV tracker other than TrackerMIL?
It seems that there are a number of other available trackers:

BOOSTING
MIL
KCF
TLD
MEDIANFLOW
GOTURN
MOSSE
CSRT

I tried just replacing every 'TrackerMIL' with 'TrackerMOSSE' but I think more will be needed to switch to a different tracker

Hi @realtimshady1
Other trackers from OpenCV are not supported.

can this be an enhancement then?

I'm not quite sure, there's no longer a need for it but I do understand the code better since last year. So perhaps it can be looked into


Slight tiling shift for subsequent rounds

Hello, great work on ashlar. I noticed a minor tiling shift for subsequent rounds, even if I used the same stack of images. Here is a gif of what I mean. The first image is the DAPI channel of the first round and is stitched pretty well, but the second image is the DAPI channel of the 'second' round (but still equal in values to the first).

I took a look through the code and I noticed that if I took out the call to this method, and I ran the code again, the results were as expected, with no shift (this is a gif!).

Here is how I am generating the stitched images:
from pathlib import Path
from typing import List

from ashlar.scripts.ashlar import process_single

def register_cycles(paths: List[Path], dst_template: Path, verbose=True):
    aligner_args = dict(verbose=verbose, filter_sigma=2.0)
    mosaic_args = dict(verbose=verbose)

    process_single(
        [str(p) for p in paths],
        output_path_format=str(dst_template),
        flip_x=False,
        flip_y=False,
        ffp_paths=None,
        dfp_paths=None,
        aligner_args=aligner_args,
        mosaic_args=mosaic_args,
        pyramid=False,
        quiet=not verbose,
    )

def run():
    paths = [
        Path("images/test-stack.ome.tiff"),
        Path("images/test-stack1.ome.tiff"),
    ]
    # dst = Path("stitched") / "original-cycle-{cycle}-channel-{channel}.tif"
    dst = Path("stitched") / "modified-cycle-{cycle}-channel-{channel}.tif"
    dst.parent.mkdir(exist_ok=True, parents=True)
    register_cycles(paths, dst_template=dst)

if __name__ == "__main__":
    run()

I am using the master branch of ashlar, and changing filter_sigma to the default value did not change the result.

Great test case! I can reproduce this locally and will investigate what's going on.

When we align tiles across cycles, we find that pure-background tiles with no cells will align based on the camera dark current noise (phase correlation is that sensitive), which is not useful and throws off the statistics we use for replacing bad alignments with interpolated positions. Ashlar has logic to detect this and discard these dark current alignments, but I just realized this logic is also triggered when you try to align the same set of images to itself!
I've added an extra check that only triggers it when the corresponding tile in the first cycle is likely to be background. This fixes your same-images use case but we need to do more testing on images that actually required the original fix to make sure they're still handled OK.

Oh I see. This edge case only came up because we wanted to check what the stitching results were before committing to a second round of cycif.
Are you referring to hot/warm pixels? We've found that many of the brightest pixels are correlated, and so for our pipeline we take a few as-dark-as-possible images before a scan, take the median, find pixels above a certain percentile, and replace them with the median of their neighborhoods, although I just realized we didn't do this for the above test case. Do you think this would help?

I think it's totally reasonable to try and register the same round of images to itself as a test, so I want to make sure that does give the expected results.
The issue is not just a few hot pixels but rather "fixed-pattern noise" (FPN) that produces low-level signal fluctuations at every pixel. Our FPN rejection logic should ignore hot pixels too since their positions are also fixed in the image, so you shouldn't need to filter them out before running Ashlar.
More on FPN:
https://en.wikipedia.org/wiki/Fixed-pattern_noise
http://isl.stanford.edu/~abbas/ee392b/lect07.pdf
Example image from https://www.researchgate.net/publication/341682797_CMOS_Fixed_Pattern_Noise_Removal_Based_on_Low_Rank_Sparse_Variational_Method :

Good to know! I can see why that would be a problem for registration. Although, we still remove hot pixels anyway because we have long exposure times and they are very noticeable otherwise.
Please let me know when there is a branch to play with so I can check using our images. Thank you!

This PR has the fix if you want to test it:
https://github.com/labsyspharm/ashlar/pull/140

Thank you, this was a problem for me as well!


Add support for multiple configuration contexts

Hi @gunnarmorling,
here comes the PR! I hope I've got the the requirements right 😄.
One thing I would like to challenge is supporting the old, properties-like config format. Because we are still pre 1.0.0, I guess it would be acceptable to not support the current (properties-like) configuration format anymore. Wdyt?
The current, context-aware format is very flexible, except for the context-name and cluster URL, every other property is
optional.
So both
{
    "currentContext": "local",
    "local": {
        "cluster": "http://localhost:8083"
    }
}

and
{
    "currentContext": "local",
    "local": {
        "cluster": "http://localhost:8083",
        "boostrapServers": "localhost:9092",
        "offsetTopic": "connect-offsets"
    }
}

are valid.
Fixes #24.

One thing I would like to challenge is supporting the old, properties-like config format. Because we are still pre 1.0.0, I guess it would be acceptable to not support the current (properties-like) configuration format anymore. Wdyt?

Yes, that's ok. We only should log a meaningful error in that case.
Other than that, could you

Rebase this PR so to address the current conflicts
Squash the commits into one and prefix the message with a suitable emoj :)
Add a section to the README describing the notion of contexts; two or three sentences will surely suffice, just to explain the overall approach

Thanks again!

Now adding a few lines to the README.md.

Hi @gunnarmorling, that push should resolve most, if not all of your comments 😄.

@helpermethod, could you also re-generate the completion script (see instructions in the README) for the new options?

Thanks a lot, @helpermethod! So I've played around a bit, it looks great overall. I wonder though if we can make the experience a bit smoother by default, i.e. if the user has not configured any context yet. How about the following if no context has been configured:

When invoking any command other than config and its sub-commands, use http://localhost:8083 (as before), and display a warning such as "No configuration context has been defined, using http://localhost:8083 by default. Run ... to create a context."
When invoking config get-context, print a message like "No configuration context has been defined, http://localhost:8083  will be used by default. Run ... to configure a create."

WDYT?

Great suggestions, I'll incorporate them over the weekend!

@helpermethod, if you'd like me to wrap up this one, just let me know. Would love to have it in, so we can get to the offset reset stuff :)

Hi @gunnarmorling,
I'm on it, I'm currently stuffed with work so it's not easy to find some uninterrupted time 😄.
I don't quite get the difference between

When invoking any command other than config and its sub-commands, use http://localhost:8083 (as before), and display a warning such as "No configuration context has been defined, using http://localhost:8083 by default. Run ... to create a context."
When invoking config get-context, print a message like "No configuration context has been defined, http://localhost:8083 will be used by default. Run ... to configure a create."

So in any case basically a warning is printed and a default is returned?

So in any case basically a warning is printed and a default is returned?

Yes, that'd be the idea. Only the wording of the messages might be slightly different ("Using..." for actual commands vs. "Will use..." for get-context), but perhaps I'm overthinking it and we can have one which fits for both :)

@helpermethod, there's a few odd changes part of this now, like version downgrades in the POM and removal of the Dependabot config.

Messed up the latest commit, fixing it right now.

I hope that should do it 😅!

Yepp, LGTM. Applied. Thanks a lot!


fix(pkg/driverbuilder): wait the pull to download

Co-authored-by: Lorenzo Fontana<EMAIL_ADDRESS>Signed-off-by: Leonardo Di Donato<EMAIL_ADDRESS>What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area pkg
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
fix(builder/docker): image pull wait for completion

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign fntlnz
You can assign the PR to them by writing /assign @fntlnz in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leodido]

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

LGTM label has been added.  Git tree hash: 92f2a18c1ea1e96382a8c8b69237b174f1d03e21


Optimize util functions!

In retrospect I should have realized I should have done this lol, thanks!


Unnecessary if statement in search tutorial

An unnecessary if statement exists in the following page.
https://www.elastic.co/search-labs/tutorials/search-tutorial/full-text-search/filters

Thanks for the report. You are correct, that if statement was a left over from a previous version of this tutorial that should have been removed in the last update. I have updated that code example now. Thanks!


Error on master channel

Please check above issue.
I am using flutter master channel .
Thank you.

+1 -> works on stable, package needs to be updated to conform to latest flutter master channel updates

Fixed in v1.9.3


Spelling check fails to run when non-standard characters are included in the dictionary

I am working on a repo which includes a list of colleges participating in a project. Three of these colleges have letters that are not standard English letters. If they are not included in the dictionary, the spell check fails. If they are included in the dictionary, the spell check fails to completely run and throws an error.
Error can be seen in the PR:
https://github.com/fhdsl/AnVIL_BioDIGS_Book/pull/6
The characters in question are ā, é, and ñ

I added some error catching here: https://github.com/jhudsl/ottr-reports/pull/27 that could potentially resolve this for now. At least folks will know what's causing the issue.


[2factor]the warning message doesn't update properly

Steps

log in to osf
go to your user settings page
enable two factor addon and don't authorize it yet
then you will see
on top:

cilck on the active your device link will redirect you to

authorize the two factor addon
you will see the two factor filed becomes

but the warning message on top is still

and click on the link doesn't take you anywhere.
Expected
The warning message on top should be changed to "Your two factor addon has been successfully authorized".

@chennan47 @GaryKriebel Was not able to recreate.

The problem is that, if you don't click to dismiss the message. It persist even you active the addon.

@GaryKriebel I'll grab this one real quick


urlencode query string params

urlencode query string params

Yes, the test suite passes locally as well for me for all versions of Python.

Works for me too. 🚢


Grindable/Juiceable needs to be reworked

Description

So as bike-shedded on Discord we talked about how confusing Grinding/Juicing are and blah blah. Anyway we need to make clearer the distinction between juicing and grinding something. There's also the matter of #4179 which technically is already fixed by using JuiceableComponent.
Do we want to remove dual functionality from the Juicer/Grinder?
Do we want to just merge Grindable/Juiceable? Juiceable seems to mostly be for food related objects like apples and oranges in SS13 so maybe do mirrorcult's idea about having a dedicated food processor?
I think having a dedicated food processor is a good idea because juicing your apples into a beaker is kinda weird anyway. I also think merging Juiceable/Grindable into one thing is good as then we can just automatically use a SolutionContainer if no result: is specified.

Closed by #4407

Closed by #4407

This won't link the issue you need to put "Closes #IssueNumber" in your PR itself for the automation to work properly.


Form Validation

Description
Form Validation
Domain
Frontend Dev HTML/CSS/JS
Type of Contribution
Audio
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign


Automation tests for pytorch model RHOAIENG-9071 for triton

Added Automation Test for RHOAIENG-11561

Verified with Jenkins Build 243

Verified with Jenkins Build 263


A question about downloading dataset

Hello, I cannot download the datasets for testing at the website you gave. Is there any other way to download the datasets?Thank you for your help.
Wish you good luck

Hi. What's the error that you are getting from the download?


Improvement: improve code structure to make it easier to change between models we are using

Right now we only have the linear regression model integrated. We would like to have an architecture that facilitate us to changing between this method to other implementations made by the future contributors.

@KarinePistili I would like to work on this issue. Can you assign it to me?

hello @sitamgithub-MSIT , assigned!

About your question:
Yes, exactly. We want an easy way to developers to change between the models. It would be important as well, to document how to make the change so it is easy for the users that would like to switch the models for their tests.
We are open to your suggestions on how too implement this, so share with us when you have an idea for this.

About your question:
Yes, exactly. We want an easy way to developers to change between the models. It would be important as well, to document how to make the change so it is easy for the users that would like to switch the models for their tests.
We are open to your suggestions on how to implement this, so share with us when you have an idea.

At first sight, I was thinking about maintaining a model configuration file just by changing the model file. If we can actually run our gaze_tracker.py file, then that will be good.
The config should consist of models and their hyperparameters, along with a training flag, which is basically a boolean field. If that is true, then training will happen, unless not.

This is the initial idea that I had. Although I will try to find another way to figure it out.

I looked into the backend codebase a little bit. I started by looking at the main.py file, which contains a reference to session.py from the app routes. Furthermore, we can see that the gaze_tracker.py file is actually being used if we go back and use the session.py file. Ultimately, the pre-processing steps and models we use are contained in this gaze_tracker.py file.
As of right now, the gaze_tracker.py file appears to be the only functional file for this issue. And as I mentioned earlier, we can control the models used in the gaze_tracker.py file by using an .yaml file. Correct me if I am wrong, but this is my basic understanding.
cc: @KarinePistili @hvini

One more thing I would like you to clarify for me is that, although the gaze_tracker.py file contains a number of methods, we are only using the predict method. Please let me know if it is untrue.
As seen below, there are two more comparable situations in the predict method where we initialize our models:
model = make_pipeline(PolynomialFeatures(2), linear_model.LinearRegression())
model.fit(X_train_x, y_train_x)
y_pred_x = model.predict(X_test_x)
===================================================
model = make_pipeline(PolynomialFeatures(2), linear_model.LinearRegression())
model.fit(X_train_y, y_train_y)
y_pred_y = model.predict(X_test_y)

What I am interested in knowing right now is whether there is a slim possibility that we will use two distinct models for the x and y coordinates. If not, repetitive code can be removed.

I think it could work. @hvini what do you think about this?

This is possibly how the .yaml file looks. Though subject to change during implementation based on project requirements and workability.
model_type: linear_regression
hyperparameters:
  degree: 2
  alpha: 0.1

And our model code part can look like this:
# Select model based on model_type
if model_type == 'linear_regression':
        model = make_pipeline(StandardScaler(), PolynomialFeatures(config['hyperparameters']['degree']),
                              linear_model.Ridge(alpha=config['hyperparameters']['alpha']))
else:
        raise ValueError("Invalid model type")

Nevertheless, I have not tested it yet. To me, the frontend codebase and configuration remain unexplored. It could take some time to set up and configure Firebase. However, in my opinion, we can test it eventually without actually setting anything up. For the purpose of testing whether it works or not, even an YAML file, the gaze_tracker file, and an artificially generated dataset similar to actual data will do!


Slightly odd that CI is split across CircleCI and Semaphore

We should just consolidate on Semaphore

This is now done


Add annotations reserved by the KRM Functions Specification

Documents the annotations from Kustomize / the KRM Functions specification. These are many years old but do not appear on the website. Current documentation is on the Kustomize repo here:

https://github.com/kubernetes-sigs/kustomize/blob/ce3e394a414387ce09679523902e981414b09a1a/cmd/config/docs/api-conventions/functions-spec.md#internal-annotations
https://github.com/kubernetes-sigs/kustomize/blob/ce3e394a414387ce09679523902e981414b09a1a/cmd/config/docs/api-conventions/manifest-annotations.md

/cc @justinsb @sftim

I think this is ready for tech review (by someone who knows kustomize / the thinking behind these annotations). @KnVerey I imagine you'd know who can review this?

/lgtm


Fix compiling issue with ros2 galactic.

It is a simple fix for compiling with galactic ros2 version.
Thanks.

give it more tests and recreate this pr.


Restructured docker-compose folder

PR Checklist
PR Structure

[ ] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[ ] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[ ] This PR's title starts with name of package that is most changed in the PR, ex.
paymentservice.stellar, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[ ] This PR adds tests for the most critical parts of the new functionality or fixes.

What
Restructured docker-compose folder
Why
Simplify the folder structure.
Known limitations
N/A

Reference Server Preview is available here:https://anchor-ref-pr767.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr767.previews.kube001.services.stellar-ops.com/

Something went wrong with PR preview build please check

Reference Server Preview is available here:https://anchor-ref-pr767.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr767.previews.kube001.services.stellar-ops.com/


Allows ubuntu/debian configuration for containerd

With this change it will allow correct configuration for both Ubuntu and Debian.
This does not promotes Debian as supported, but allows to start working on it.
Which issue(s) this PR fixes:
Fixes #2719
What type of PR is this?
Add one of the following kinds:
/kind bug
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:
NONE
Introduces initial support for Debian. Changes containerd repository configuration to allow Ubuntu or Debian.

Documentation:
NONE

PS: tr is part of coreutils package, so literally it is impossible to not be on any Debian based distribution and not have it.


Switch AddDbContext to use .Add instead of .TryAdd when adding DbContextOptions

Fix https://github.com/aspnet/EntityFramework/issues/5156
This brings https://github.com/aspnet/EntityFramework/pull/5017 into release branch
cc @divega @ajcvickers

Fixes https://github.com/aspnet/EntityFramework/issues/4994 too

@natemcmaster Can you explain why it requests bringing #5017 in? As I understand it, all this change will do in the normal case is change which of the two generic DbContextOptions is returned when the non-generic one is resolved. It doesn't make #5017 any worse or better.
We could decide we really need this fix in RC2 anyway, but I don't think that it is related to this change.

FWIW we talked in triage today and decided to bring #5017 in. I agree the two changes are somewhat orthogonal, but #5017 makes the whole experience less confusing and the code in this PR a bit cleaner.

@natemcmaster @rowanmiller @divega I think a better process here would be to make this change as a single PR that we take through ask mode, and then reference the existing PRs for the other changes and bring those through separately. This change conflates several things into one PR, some of which have already been done in other PRs in dev. This doesn't seem to be the right way to go about this.

@divega Not sure how it makes the code in this PR cleaner. It should be a one-line change--TryAdd to Add. A couple of tests might break because of the last wins/first wins implication, but it shouldn't require any other product changes.

@ajcvickers I was thinking because of ContextType which you added. Not sure it makes it cleaner in any other way.

@divega How is ContextType involved in the change from TryAdd to Add?

It helps removing a couple of reflection calls that Migrations was using to detect the DbContext types. That is all. They are still orthogonal.
BTW, I agree with you that from the process perspective we can take the two PRs separately.

@divega Exactly. There are several things being conflated here, only one of which is described in the description of the PR.
It feels wrong to me when in ask mode to manually merge bits and pieces from several existing commits into one PR, then add some new stuff, and give it a title that doesn't reflect what is really happening at all. Seems like sloppy process. But I will step back now and let it happen this way if that's how you guys have discussed it should happen.

But I will step back now and let it happen this way if that's how you guys have discussed it should happen.

We didn't discuss this explicitly. I think this is very good feedback, so I have asked @natemcmaster to send new PRs.

Updated. This PR to isolate the change. The other PR is https://github.com/aspnet/EntityFramework/pull/5186

:shipit:


(#21) [New]: Cookie law

Description
Show cookie law banner.
fixes #21
Code formating
The code has to be well formatted following the formatting rules. For example in Python the code has to follow the PEP8.
Before create your PR, please make sure your code is well formatted and styled doing:
$ >> pre-commit run --all

As a first step it's fine but this library says that is not GDPR complaint

Oops, you are right, but we use it in all apsl projects.
Anyway, it's only affect to  United Kingdom, right?
That's not our market and I think is not a problem.


Quiet noisy output from Makefile.common

This patch suppresses the noisy output of Makefile.common (mostly the echoing of the long commands used to invoke 'litani add-job' used to create the ninja build graph) unless the Makefile variable VERBOSE is defined (eg, with make VERBOSE=1 report).
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I've modified the Makefile as Kareem recommended (adding the -s flag to MAKEFLAGS).  I have retained the progress information printed by long-running targets: On slow machines, it is comforting to see progress information printed during the four or five seconds before ninja starts printing its own progress information.


doc: add Maintainability Badge. will revisit after v1.3 release

Codecov Report

Merging #28 (4d864e2) into main (cb8017a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #28   +/-   ##
=======================================
  Coverage   30.41%   30.41%
=======================================
  Files           9        9
  Lines        1006     1006
=======================================
  Hits          306      306
  Misses        700      700

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 cb8017a...4d864e2. Read the comment docs.


Track all feature flag calls

If an analytics processor exists we previouly only tracked feature flag names that were present either from the environment or from the API. However, this gave us no information about calls to flags that either were wrong, or were handled by the default handler.
With this change we now track all calls for more extensive coverage.

Hey @JonasAlfredsson, this is interesting. I can definitely understand the use case, however, I'm not sure how useful it would be right now since there is no functionality for surfacing this data, right? What was your intention here?

My intention is to make tracking more accurate by also recording every time we call for a feature flag that is subsequently handled by the default handler instead of only when we get them via the API/Environment.
If there is no way of seeing the calls to "invalid" feature names, then perhaps that is another feature request that should be placed on the server issue tracker (if there is such a one)?.

Yep, for sure. We track all of our server feature requests / issues here: https://github.com/Flagsmith/flagsmith/issues

Added a feature request there, where it could be discussed at a higher level if desired.


Brain and source space are not aligned in the left_cerebellum_volume_source example

Description of the problem
In the left_cerebellum_volume_source example, the final display using the following freeview command:
nii_fname = 'mne_sample_lh-cerebellum-cortex.nii'
src.export_volume(nii_fname, mri_resolution=True)

from mne.utils import run_subprocess
mri_fname = subjects_dir + '/sample/mri/brain.mgz'
run_subprocess(['freeview', '-v', mri_fname, '-v',
                    '%s:colormap=lut:opacity=0.5' % aseg_fname, '-v',
                    '%s:colormap=jet:colorscale=0,2' % nii_fname,
                    '-slice', '157 75 105'])

shows non aligned brain/source space:

When checking the sources coord_frame:
[s['coord_frame'] for s in src]
[5 (FIFFV_COORD_MRI), 5 (FIFFV_COORD_MRI), 5 (FIFFV_COORD_MRI)]

From what is understand from the mne.SourceSpaces.export_volume documentation, , everything should be well aligned, as a trans Must be provided if source spaces are in head coordinates and include_surfaces and mri_resolution are True.
I have the same issue with my own dataset. Everything works fine (well aligned) with the following script:
fig = mne.viz.plot_alignment(
    subject=subject,
    subjects_dir=subjects_dir,
    surfaces="white",
    coord_frame="mri",
    src=src,
)

If the issue doesn't come from a misunderstanding from my part, I assume the error to be found in the  export_volume  method or in my freeview settings.
Steps to reproduce
Download and run the left_cerebellum_volume_source notebook

Link to data
No response
Expected results
The source space should be aligned with the brain (T1,brain,aseg)
Actual results
The source space are not aligned with the brain (T1,brain,aseg)
head↔MRI
Additional information
Platform             Windows-10-10.0.19045-SP0
Python               3.11.7 | packaged by Anaconda, Inc. | (main, Dec 15 2023, 18:05:47) [MSC v.1916 64 bit (AMD64)]
Executable           c:\Users\victor.ferat\AppData\Local\miniconda3\envs\meg\python.exe
CPU                  Intel64 Family 6 Model 165 Stepping 2, GenuineIntel (12 cores)
Memory               15.6 GB
Core
├☑ mne               1.6.1 (latest release)
├☑ numpy             1.26.3 (unknown linalg bindings (threadpoolctl module not found: No module named 'threadpoolctl'))
├☑ scipy             1.12.0
├☑ matplotlib        3.8.2 (backend=module://matplotlib_inline.backend_inline)
├☑ pooch             1.8.0
└☑ jinja2            3.1.3
Numerical (optional)
├☑ nibabel           5.2.0
└☐ unavailable       sklearn, numba, nilearn, dipy, openmeeg, cupy, pandas
Visualization (optional)
├☑ pyvista           0.43.2 (OpenGL 4.5.0 - Build <IP_ADDRESS>8 via Intel(R) UHD Graphics)
├☑ pyvistaqt         0.11.0
├☑ vtk               9.3.0
├☑ qtpy              2.4.1 (PyQt6=6.6.1)
├☑ pyqtgraph         0.13.3
├☑ mne-qt-browser    0.6.1
├☑ ipywidgets        8.1.1
└☐ unavailable       ipympl, trame_client, trame_server, trame_vtk, trame_vuetify
Ecosystem (optional)
└☐ unavailable       mne-bids, mne-nirs, mne-features, mne-connectivity, mne-icalabel, mne-bids-pipeline
I'm running freeview from a docker container as  I'm using a windows platform.

Can confirm with MWE:
from mne import setup_volume_source_space
from mne.datasets import sample
from mne.utils import run_subprocess
from mne.viz import plot_alignment

subjects_dir = sample.data_path() / "subjects"
subject = "sample"
aseg_fname = subjects_dir / subject / "mri" / "aseg.mgz"

# setup a volume source space of the left cerebellum cortex
lh_cereb = setup_volume_source_space(
    subject,
    mri=aseg_fname,
    sphere=(0, 0, 0, 0.12),
    volume_label="Left-Cerebellum-Cortex",
    subjects_dir=subjects_dir,
    sphere_units="m",
)

plot_alignment(
    subject=subject,
    subjects_dir=subjects_dir,
    surfaces="white",
    coord_frame="mri",
    src=lh_cereb,
)

nii_fname = "mne_sample_lh-cerebellum-cortex.nii"
lh_cereb.export_volume(nii_fname, mri_resolution=True, overwrite=True)

mri_fname = subjects_dir / "sample" / "mri" / "brain.mgz"
run_subprocess(
    [
        "freeview",
        "-v",
        str(mri_fname),
        "-v",
        "%s:colormap=lut:opacity=0.5" % str(aseg_fname),
        "-v",
        "%s:colormap=jet:colorscale=0,2" % nii_fname,
        "--slice",
        "157",
        "75",
        "105",
    ]
)

And that commented run_subprocess command is outdated in the tutorial anyway..