RAS-930 Reduce collection exercise logging level to info

What and why?
Updating the logging level from debug to info
How to test?
deploy to you environment and run the acceptance tests, make sure that no debug level logs appear in the collection exercise logs
Jira
https://jira.ons.gov.uk/browse/RAS-930

There are a couple of log line in there that need upping
"Event is not actionable, setting to COMPLETED state", "Problem loading fixture {} reason {}"
A couple I am on the fence with i.e "Deleting collection exercise event id, event tag". I am not bothered about getting DTOs or hitting end points etc, but deleting things I am a bit more interested to see them in the logs, at a stretch an important creation as well.

I've updated some of the debug logs, mostly to info, but the ones which are around problems were elevated to warn (they're also in the test directory)


Feature request: Versioning of applications within app templates

I would like the ability to have users of the UI choose between multiple versions of the same application.  This would require something like the following in the templates:
versions: ["latest","may2017","dec2016"]
and in the UI one would select from among the three versions to start up.

I already have interest in something similar. But instead of using version here, I'm thinking that the image field should be updated to an array...
E.g. support something like image: ['nginx:latest', 'nginx:alpine']. UI would default to the first entry and when multiple images are found a dropdown would be displayed to be able to select it.
What do you think?

That would work for me.  I can see where this might be easier for you to
implement and gets us the same functionality.
On Fri, Jul 7, 2017, 11:37 PM Anthony Lapenna<EMAIL_ADDRESS>wrote:

I already have interest in something similar. But instead of using version
here, I'm thinking that the image field should be updated to an array...
E.g. support something like image: ['nginx:latest', 'nginx:alpine']. UI
would default to the first entry and when multiple images are found a
dropdown would be displayed to be able to select it.
What do you think?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/portainer/portainer/issues/999#issuecomment-313838183,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABNSm4OFWJJnrZl5k9_1NYzWhMsgNgO_ks5sLyOqgaJpZM4ORe5n
.

Well, I'd not say easier as any change in the template format requires backward compatibility.
But that's an interesting request, so we'll work on this.


HBASE-18901 [C++] Provide CMAKE infrastructure

Provided cmake files for packages in which a default module
did not exist.
Moved tests to a location where we could automatically build
the test suite.
Resolved minor issues with tests
Tested across OSX, RHEL7, and Ubuntu16

HBASE-18901 [C++] Cleanup CMAKE

Note that some of the cmake modules are derivative of previous work that I've done, which was likely derivative work of someone else's work years past. How would you like me to handle this?
Even if I didn't immediately reference or copy their cmake module I'd be happy to document somewhere that something may be a derivative work as a result of someone else's efforts that I've propagated via memory.

This PR is slated to be closed as a part of HBASE-20391 because the referenced JIRA has since closed.
If this is incorrect and you are still interested in working on the issue please comment there and/or reopen the PR.

I think @joshelser can confirm that this was merged via another PR. I will close as a result. Thanks

I guess I could confirm too, but I don't really know how to use git....what's the command?


Low Frame Rate Issue with Concurrent Lidar and Camera

Version: Apollo 9.0 Hardware: X86 and Orin
Issue Details: I am experiencing an issue where launching lidar and camera perception using the same launch file results in the lidar frame rate dropping from the original 10 frames to only 2 or 3 frames. However, if I use two separate launch files to start the lidar and camera simultaneously, the frame rate remains normal.
Does this indicate that running camera perception and lidar perception in the same process leads to GPU resource contention, whereas separate processes do not encounter this issue?
Currently, I want to perform multi-sensor fusion, such as with perception_all.launch, which starts lidar perception and camera perception within the same process. I wish to separate these two. But because the channels sent by the them are internal channels, they cannot be found in cyber_monitor. Therefore, to start multi_sensor_fusion, it seems I have to run it in the same launch file, but the frame rate is poor. What should I do? Is it possible to use msg_adapter to do something helpful? Are there any examples available?

What should I do?

Yes, the lidar, camera and fusion modules need to be started at the same process(one launch), the reason is just as you said "because the channels they send are internal channels"

Is it possible to use msg_adapter to do something helpful?

Yes, you can use some msg_adapter to publish messages, note that messages have serialization methods, and "msg_adapter" needs the same processing as lidar, camera and fusion modules

issue
lidar frame rate dropping from the original 10 frames to only 2 or 3 frames
I'm not sure what the problem is, simply you can add logs and check if the lidar module frequency is 10 hz, then we can narrow down the problem.
By the way, you can use the following method to collect the module time cost
PERF_BLOCK("filter_bank")

It will save all the logs in a file called "PERF.info.log", then you can use aperf tool to visualize the time cost line.
https://github.com/ApolloAuto/apollo/blob/master/modules/tools/aperf/README.md

@daohu527
Thanks. I failed to find the PERF.info.log. But I printed the time of entering and exiting for each component in
time_cost.txt
It is clear that the lidar_detection component is slower than any other front component, while the other front components seem to be fine. (It always takes more than 200 ms.)
The issue only occurs when I launch camera_detection_multi_stage_yolox3d.dag and lidar_detection.dag in the same launch file.
If I use two separate launch files to launch them individually, the time for lidar_detection is about 100 ms.
But if I want to use fusion, the issue seems to be unavoidable because I need to launch them in the same file.
Can you give me any suggestions? Thank you

What should I do?

Yes, the lidar, camera and fusion modules need to be started at the same process(one launch), the reason is just as you said "because the channels they send are internal channels"

Is it possible to use msg_adapter to do something helpful?

Yes, you can use some msg_adapter to publish messages, note that messages have serialization methods, and "msg_adapter" needs the same processing as lidar, camera and fusion modules

issue
lidar frame rate dropping from the original 10 frames to only 2 or 3 frames
I'm not sure what the problem is, simply you can add logs and check if the lidar module frequency is 10 hz, then we can narrow down the problem.
By the way, you can use the following method to collect the module time cost
PERF_BLOCK("filter_bank")

It will save all the logs in a file called "PERF.info.log", then you can use aperf tool to visualize the time cost line.
https://github.com/ApolloAuto/apollo/blob/master/modules/tools/aperf/README.md

which Apollo version do you use? I check the code default perf.log is on!
https://github.com/ApolloAuto/apollo/blob/ba32187d4f1879fb0a9b941ca501cd5717c680df/scripts/apollo_base.sh#L43
The reason why this is used is that it can record the time of each module, So I suggest you use aperf to analyze!

@HandsomeAIccx You can refer to modify and add ENABLE_PROFILER, or format your time consumption, your log module is not aligned


Control switch fix

Someone was tried hu?

Basically when playing in a song it would swap the binds instead of just in the menus.
Click here to see what I mean

Maintainers can edit it since ya know resolve conflict stuff plus I did this on my phone 🥲

Also changed death to select instead of click on left joystick

wait why was funkinlua removed

wait why was funkinlua removed

Idk it was there help

revert the commit that deleted funkinlua? it isnt that hard to revert

revert the commit that deleted funkinlua? it isnt that hard to revert

IDK HOW! 😭
Are you a maintainer? If so you might be able to do it.

im not but i can make a pr inside of a pr
but feeling lazy

Also in the thing it says I deleted FunkinLua.hx but
Click here for a video

revert the commit that deleted funkinlua? it isnt that hard to revert

IDK HOW! 😭
Are you a maintainer? If so you might be able to do it.

revert the commit that deleted funkinlua? it isnt that hard to revert

IDK HOW! 😭
Are you a maintainer? If so you might be able to do it.

https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/reverting-a-commit maybe try following this

revert the commit that deleted funkinlua? it isnt that hard to revert

IDK HOW! 😭
Are you a maintainer? If so you might be able to do it.

revert the commit that deleted funkinlua? it isnt that hard to revert

IDK HOW! 😭
Are you a maintainer? If so you might be able to do it.

https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/reverting-a-commit maybe try following this

It gives errors when trying to revert!

@ShadowMario, I think you should look at this.

It's okay, you tried.

It's okay, you tried.

@ShadowMario... ya know the face buttons for switch are messed up right?

🤦🏻

No?


FreeBSD Support

On my Linux machine, taking the changes I made for FreeBSD also compile and work on Linux.
Hope it works for you too.

Yup. It works for me.


Use m2w64 compilers

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Are there any other planned changes here or can we merge this?

LGTM to merge - this should go in before the migration

OK, @isuruf let us know if you spot any other changes you'd like made.


Add OpenWRT_guide.md

Initial revision.
Feel free to update)

Can you create docs folder and put it there? Also link in readme would be nice. Thanks!

Done!


Confusion on ARM support matrix

Title
There are several different docs about dotnet core around ARM support but they are conflict to each others.
General

The following link: https://docs.microsoft.com/en-us/dotnet/core/linux-prerequisites?tabs=netcore2x#supported-linux-versions shows NET Core 2.1 is supported on the following Linux 64-bit (x86_64 or amd64) distributions/versions, I guess the doc want to tells me dotnet core 2.1 support ARM64 on any linux?

The following link: https://github.com/dotnet/core/blob/master/release-notes/2.1/2.1-supported-os.md#linux shows ARM32 support starts with Debian 9 and Ubuntu 18.04. Earlier versions of those distros are not supported on ARM32, So why this doc doesn't tells me anything about ARM64?

The following link: https://github.com/dotnet/core/blob/master/release-notes/2.1/2.1-supported-os.md#windows shows dotnet core 2.1 only support Windows x86/x64, it doesn't support any Windows ARM.

The following link: https://docs.microsoft.com/en-us/dotnet/core/rid-catalog#using-rids shows there is not Linux ARM RID instead, there are ARM RID for Windows?

My goal is  to publish a self-contained dotnet core app that target ARM.
I want to know what kind of ARM i can target:
win-arm32 ?
win-arm64 ?
linux-arm32 ?
linux-arm64 ?

The currently supported ARM targets are detailed in the 2.1-supported-os document.  ARM32 on Debian and Ubuntu are the supported platforms at the moment.
We have begun building ARM64 runtime and SDK. These are in the experimental stages right now. The same is true for the Win ARM builds.
@richlander for additional info and to fact check me.

Should we update all docs to make them consist?

Where needed, yes.

https://docs.microsoft.com/en-us/dotnet/core/linux-prerequisites?tabs=netcore2x#supported-linux-versions says nothing about ARM so needs to have current info added. @JRAlexander
https://github.com/dotnet/core/blob/master/release-notes/2.1/2.1-supported-os.md#linux is current and correct?
https://github.com/dotnet/core/blob/master/release-notes/2.1/2.1-supported-os.md#linux should be thought as as API documentation and is not a statement of support.

I assume your are reference to  https://docs.microsoft.com/en-us/dotnet/core/rid-catalog#using-rids for should be thought as as API documentation and is not a statement of support.

Yes, sorry about that!

I know one day I will write a matrix code

Does this leave this where there is just the need to have the docs updated as mentioned above?
https://docs.microsoft.com/en-us/dotnet/core/linux-prerequisites?tabs=netcore2x#supported-linux-versions says nothing about ARM so needs to have current info added. @JRAlexander

https://docs.microsoft.com/en-us/dotnet/core/linux-prerequisites?tabs=netcore2x#supported-linux-versions already mentions ARM32 from PR https://github.com/dotnet/docs/pull/6901 on 8/8. Closing.


Tag Keys starting with aws: error with reserved word

When instances are created with CloudFormation or Service Catalog, the services will create their own tags on instances.  These tags all start with "aws:".  When trying to convert, the error comes up that these are reserved tags.....
The tag keys maybe just renamed to something like changing "aws:cloudformation" to "AWScloudformation".
botocore.exceptions.ClientError: An error occurred (InvalidParameterValue) when calling the RunInstances operation: Tag keys starting with 'aws:' are reserved for internal use

Hi,
Good catch! It is a side use-case as instances created with IaaC are less likely with the need to use EC2-spot-converter (It will create a configuration drift from a CloudFormation/TerraForm/Pulumi PoV) but it could useful in some case so will add the support. Thanks.

Thanks for looking at adding this feature!  Kudos on this tool.... worked very well in our (small) test environment!
You are correct, this is probably not an issue for most but when deploying EC2 instances with CloudFormation stacks and AWS Service Catalog this is creating these tags.  To your point these instances should be built as spot to begin with, but for us it is not always the case (ie. lift-shift).

v0.14.0 released. Enjoy!

Jusr detected a small regession. v0.14.1 coming soon...

v0.14.1 released. Should be ok this time...


Long emote names trigger the message height/length limits

This one for example: https://betterttv.com/emotes/5d41cce86b7300449a433b68
3 of them = 150 height, but doesn't look that way

This is probably caused by https://github.com/pajbot/pajbot2/issues/86


How to use Http.Swift

hi, i have installed your Framework, now I tried to C/P your readme `let server = Server()
server.get("/hello/{id}") { request in
print(request.queryParams["state"])
return .ok(request.routeParams["id"]!)
}
try server.run()`
but I have an error on server.run  : "Error thrown from here are not handled"

and a second question, how to use a certain port and can I use server.stop or similar to stop server?


Transformation caching does not work correctly

`public interface Transformation extends Key {
/**

Transforms the given resource and returns the transformed resource.

If the original resource object is not returned, the original resource will be

recycled and it's internal resources may be reused. This means it is not safe to rely on the
original resource or any internal state of the original resource in any new resource that is
created. Usually this shouldn't occur, but if absolutely necessary either the original resource
object can be returned with modified internal state, or the data in the original resource can
be copied into the transformed resource.

If a Transformation is updated, {@link #equals(Object)}, {@link #hashCode()}, and

{@link #updateDiskCacheKey(java.security.MessageDigest)} should all change. If you're using a
simple String key an easy way to do this is to append a version number to your key. Failing to
do so will mean users may see images loaded from cache that had the old version of the
Transformation applied. Changing the return values of those methods will ensure that the cache
key has changed and therefore that any cached resources will be re-generated using the updated
Transformation.

During development you may need to either using {@link

com.bumptech.glide.load.engine.DiskCacheStrategy#NONE} or make sure {@link
#updateDiskCacheKey(java.security.MessageDigest)} changes each time you make a change to the
Transformation. Otherwise the resource you request may be loaded from disk cache and your
Transformation may not be called.

@param context The Application context
@param resource  The resource to transform.
@param outWidth  The width of the view or target the resource will be displayed in, or {@link

             com.bumptech.glide.request.target.Target#SIZE_ORIGINAL} to indicate the

             original resource width.

@param outHeight The height of the view or target the resource will be displayed in, or {@link

             com.bumptech.glide.request.target.Target#SIZE_ORIGINAL} to indicate the

             original resource height.

@return The transformed resource.
*/
Resource transform(Context context, Resource resource, int outWidth, int outHeight);

/**

For caching to work correctly, implementations must implement this method and
{@link #hashCode()}.
*/
@Override
boolean equals(Object o);

/**

For caching to work correctly, implementations must implement this method and
{@link #equals(Object)}.
*/
@Override
int hashCode();
}`

For caching to work correctly, transformation must implement method equals(Object o) and hashCode(Object o);

thanks for #105 @CrabeMan


error in ctranslate

ctranslate2_translate_lines
translations = self.translator.translate_batch(
RuntimeError: No position encodings are defined for positions >= 210, but got position 210
i am getting this error when trying to do translation with  the ctranslate model.

Please refer https://github.com/OpenNMT/CTranslate2/issues/1157


[FEATURE] Add Node-based Entity System

Add a node based entity management system like in Godot/Unity/etc.
Like this:
Scene:

Entity 1

Rigidbody

Sketch

Entity 2

Sketch

This feature would be a good addition, however Qilin is not a whole game engine, but rather a framework to build game engines.
Also qilin is inspired by MonoGame which do not have a real entity node system.


Remove support for ATracker route + cos set up

Observability DA will handle this - but lets hold off until that is ready

Hi @MatthewLemmond - there is an issue in https://github.com/terraform-ibm-modules/terraform-ibm-account-infrastructure-base/issues/27 . kms and cos related variable should be set to null by default under https://github.com/terraform-ibm-modules/terraform-ibm-account-infrastructure-base/blob/f646074f7ff8c0b8761c8bc981c75a784b1bfde1/solutions/account-infrastructure-base/variables.tf#L28 (like in the root module)

created https://github.com/terraform-ibm-modules/terraform-ibm-account-infrastructure-base/pull/91 to fix that, was not caught by tests due to all of our tests provisioning atracker and COS

Added in https://github.com/terraform-ibm-modules/terraform-ibm-account-infrastructure-base/pull/87


ipad crash, viewer in iframe

Hi
On ipad 2 with any browser (safari, chrome, dolphin, opera), when the pdfjs viewer is displayed in a iframe ,the browser crashes and is suddenly closed. To reproduce it, try to display the viewer presented in the demo in a iframe.
On desktop, there is no problem.
Thx.

Finally, the crash occured just when a parent of the iframe has display:flex


Fixed a typo in durandal.d.ts

I changed CompositionTransation to CompositionTransaction. It now matches https://github.com/BlueSpire/Durandal/blob/master/src/durandal/js/composition.js

@EisenbergEffect reviewed, looks good. i can add this to definitelytyped as well if you'd like

Ok. I merged it. Feel free to submit it to definitely typed.


Sets default log levels for destinations.

Sets the default min and max log level in the Logger::Destination initializer.

Fixes issue 3.


implement APE14 compatibility in reproject

Solves #777
This is a fairly straightforward PR but needs tests.

Codecov Report

Merging #778 (dea4a27) into master (1f67a8f) will decrease coverage by 0.06%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #778      +/-   ##
==========================================
- Coverage   77.86%   77.80%   -0.07%
==========================================
  Files          24       24
  Lines        5811     5816       +5
==========================================
  Hits         4525     4525
- Misses       1286     1291       +5

Impacted Files
Coverage Δ

spectral_cube/spectral_cube.py
76.55% <0.00%> (-0.26%)
:arrow_down:

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 1f67a8f...dea4a27. Read the comment docs.

This is not even close to straightforward.  I don't think spectral-cube can or should support any non-serializable WCSes.


Add support for useCookie(cookieName)

returns the specified cookie
req.cookies.name (needs cookie parser)

Closing in favor of #41


update Bill's PPP

Codecov Report

Merging #205 (e7c101e) into master (d933b65) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #205   +/-   ##
=========================================
  Coverage     74.80%   74.80%
  Complexity      645      645
=========================================
  Files            88       88
  Lines          1889     1889
  Branches        221      221
=========================================
  Hits           1413     1413
  Misses          397      397
  Partials         79       79

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 d933b65...e7c101e. Read the comment docs.


Delete current allocator, replace with more efficient slab allocator

^

Also adding crate cloning scripts in this PR to help ease development on my end.


Promises

I have the following code:
    user.save()
        .then(function () {
            req.login(user, function (err) {
                if (err) {
                    next(err);
                } else {
                    auth.login(req, res);
                }
            });
        })
        .error(function (err) {
            winston.err(err);
        });

It would be nicer as:
    user.save()
        .then(function () {
            return req.login(user);
        })
        .then(function () {
            auth.login(req, res);
        })
        .error(function (err) {
            winston.err(err);
        });

If I added support for promises to passport, would you merge it?

Closing. See comment for rationale.

See issue #536 for adding promise support now that a lot of time has passed since this issue was created.


data_channel: made DataChannelReadyState public

Verified on Android

LGTM. I'll file an issue about exposing this in the JavaScript layer.


Version of Google OR-tools

Hey, we appreciate the great contribution of AM to this field. I was wondering what is the version of google or-tools? I am having trouble when running it for PCTSP.

We have solved this issue by modifying the example in Ducumentation.
We drop the capacity constraint and add
# add min prize constraint
def prize_callback(from_index):
    """Returns the demand of the node."""
    # Convert from routing variable Index to demands NodeIndex.
    from_node = manager.IndexToNode(from_index)
    return data['prizes'][from_node]
prize_callback_index = routing.RegisterUnaryTransitCallback(
    prize_callback)
dimension_name = 'Prize'
routing.AddDimension(
    prize_callback_index,
    0,
    100000000,
    True,
    dimension_name)
prize_dimension = routing.GetDimensionOrDie(dimension_name)
index = routing.End(0)
routing.solver().Add(
        prize_dimension.CumulVar(index) >= data['min_prize'])

# allow to drop nodes
for node in range(1, len(data['distance_matrix'])):
    routing.AddDisjunction([manager.NodeToIndex(node)], data['penalty'][node])

Thanks anyway!


YJDH-683 | feat(kesaseteli): update summer voucher price for year 2024 to 350e

Description :sparkles:
feat(kesaseteli): update summer voucher price for year 2024 to 350e
also support Excel exporting previous years' summer vouchers with the
old price of 325e, add test for this
refs YJDH-683
Issues :bug:
YJDH-683
Testing :alembic:
Screenshots :camera_flash:
Additional notes :spiral_notepad:

EMPLOYER branch is deployed to platta: https://kesaseteli-employer-pr2745.dev.hel.ninja :rocket::rocket::rocket:

HANDLER branch is deployed to platta: https://kesaseteli-handler-pr2745.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://kesaseteli-handler-pr2745.dev.hel.ninja :laughing::tada::tada::tada:

YOUTH branch is deployed to platta: https://kesaseteli-youth-pr2745.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://kesaseteli-youth-pr2745.dev.hel.ninja :laughing::tada::tada::tada:

TODO:

[ ] Fix tests

API branch is deployed to platta: https://kesaseteli-pr2745.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

EMPLOYER branch is deployed to platta: https://kesaseteli-employer-pr2745.dev.hel.ninja :rocket::rocket::rocket:

EMPLOYER branch is deployed to platta: https://kesaseteli-employer-pr2745.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://kesaseteli-employer-pr2745.dev.hel.ninja :laughing::tada::tada::tada:

HANDLER branch is deployed to platta: https://kesaseteli-handler-pr2745.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://kesaseteli-handler-pr2745.dev.hel.ninja :laughing::tada::tada::tada:

YOUTH branch is deployed to platta: https://kesaseteli-youth-pr2745.dev.hel.ninja :rocket::rocket::rocket:

This PR is now ready for code review, @melniiv, @nikomakela, @jakezu

After discussing with product owner updated the use of 325e (previous years' summer voucher price) for employer summer voucher applications until 2024-05-31 in order to support late coming employer summer voucher applications during 2024 before the 2024 summer job period starts on June 1st. Changed the logic in force push.

API branch is deployed to platta: https://kesaseteli-pr2745.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

EMPLOYER branch is deployed to platta: https://kesaseteli-employer-pr2745.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://kesaseteli-employer-pr2745.dev.hel.ninja :laughing::tada::tada::tada:

HANDLER branch is deployed to platta: https://kesaseteli-handler-pr2745.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://kesaseteli-handler-pr2745.dev.hel.ninja :laughing::tada::tada::tada:

YOUTH branch is deployed to platta: https://kesaseteli-youth-pr2745.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://kesaseteli-youth-pr2745.dev.hel.ninja :laughing::tada::tada::tada:

Clarified comment and removed useless assert from test (The test cases may be using a freeze_time already so testing whether a date is not in the past might not be using the real date). Force pushed.

API branch is deployed to platta: https://kesaseteli-pr2745.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

EMPLOYER branch is deployed to platta: https://kesaseteli-employer-pr2745.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://kesaseteli-employer-pr2745.dev.hel.ninja :laughing::tada::tada::tada:

HANDLER branch is deployed to platta: https://kesaseteli-handler-pr2745.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://kesaseteli-handler-pr2745.dev.hel.ninja :laughing::tada::tada::tada:

YOUTH branch is deployed to platta: https://kesaseteli-youth-pr2745.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://kesaseteli-youth-pr2745.dev.hel.ninja :laughing::tada::tada::tada:


Update README.md with link pointing to the correct location.

Closed the previous PR #52 and opened a new one.

Thanks, @krishna-mk!


Do not raise update events for products / recipes which were not changed

Is your feature request related to a problem? Please describe.
Currently, if you save a recipe within the product UI the the facade throws events for all recipes of the product and the type itself. There is no option to only save the modified recipe. The other way around, if a product gets saved, recipe updates for all recipes are raised.
Describe the solution you'd like

The product management / recipe management can identify changes and only for the changed entries the event will be raised

Describe alternatives you've considered

The UI can identify the changes and only call save for the changed entries

While the alternative might be easier, it doesn't scale with different usages of the web service and does not work for change calls from the facade.

Moved to https://github.com/PHOENIXCONTACT/MORYX-Framework/issues/232


Ensure long output does not exceed API limits

With some of our simple checks, long output cause an issue:
Traceback (most recent call last):
  File "/home/icinga/.local/share/virtualenvs/icinga-plugins--BT7bI7t/bin/hipsaint", line 11, in <module>
    load_entry_point('hipsaint', 'console_scripts', 'hipsaint')()
  File "/opt/icinga-plugins/hipsaint-test/hipsaint/bin/commands.py", line 85, in main
    msg.deliver_payload()
  File "/opt/icinga-plugins/hipsaint-test/hipsaint/messages.py", line 102, in deliver_payload_v2
    raw_response = urlopen(request)
  File "/usr/lib64/python2.7/urllib2.py", line 154, in urlopen
    return opener.open(url, data, timeout)
  File "/usr/lib64/python2.7/urllib2.py", line 437, in open
    response = meth(req, response)
  File "/usr/lib64/python2.7/urllib2.py", line 550, in http_response
    'http', request, response, code, msg, hdrs)
  File "/usr/lib64/python2.7/urllib2.py", line 475, in error
    return self._call_chain(*args)
  File "/usr/lib64/python2.7/urllib2.py", line 409, in _call_chain
    result = func(*args)
  File "/usr/lib64/python2.7/urllib2.py", line 558, in http_error_default
    raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 400: Bad Request

This is due to limitations set by the hipchat API. This proposed change detects and truncates long output for the card. It does not affect what is seen in an email or in Icingaweb2.

looks good to me!
Thanks for the contribution.


Update slides

This updates the slides for the "Open Source Experience",
Paris, France.
Signed-off-by: David A. Wheeler<EMAIL_ADDRESS>

I present tomorrow, only slides are affected, and unsurprisingly all tests pass.
I'm merging this now (immediately).


Korean translation modification

A local in Korea modified the translation (though it took a little time).
(translator translated "disabled" as "person with disabilities." xd)

🚀 Thank you for your assistance with the GitHub project! Your contribution has propelled the project forward. 👍 Your help is invaluable! 🙌

A local in Korea modified the translation (though it took a little time).
(translator translated "disabled" as "person with disabilities." xd)

Yes, it was exactly the same in German :D
(The one with disabled and person with disabilities)


Simpler with mocha's built-in promise support

Updated test docs following http://tobyho.com/2015/12/16/mocha-with-promises/

Thanks @hoegrammer, this is a lot nicer!


Some limits are not appearing

Describe the bug
I've deploy the solution into multiple accounts but can't find any trace of any Amazon SageMaker or Amazon CloudFront quota's in the DynamoDB. More could be missing, I haven't checked them all.
To Reproduce
Deploy the solution, then query the data that has been collected and look for any traces of Amazon SageMaker or Cloudfront quotas. For example "Cookies per cache policy".
Expected behavior
All quota's are collected in the dynamodb table QMTable.
Please complete the following information about the solution:

[x] Version: [e.g. v1.0.0]
v6.2.9

[x] Region: [e.g. us-east-1]
us-east-1

[x] Was the solution modified from the version published on this repository?
no

[x] Have you checked your service quotas for the services this solution uses?

[x] Were there any errors in the CloudWatch Logs? How to enable debug mode?
None that I could find

Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).
Results from
SELECT distinct(service)
FROM "default"."quota-monitor-hub-qmtable336670b0-1n3u9ljhx0m6l"

"service"
"DynamoDB"
"Bedrock"
"Connect"
"SSM"
"Route53"
"DiagnosticTools"
"Kinesis"
"SNS"
"Location"
"ECR"
"SES"
"AppSync"
"Fargate"
"IoT"
"CloudWatch"
"NeptuneGraph"
"Lightsail"
"KMS"
"RDS"
"RoboMaker"
"VPC"
"CloudTrail"
"EMR"
"EBS"
"Braket"
"Textract"
"ELB"
"NetworkMonitor"
"Firehose"
"EventBridge"
"IVS"
"AutoScaling"
"FIS"
"IAM"
"Athena"
"CloudFormation"
"IVSChat"
"AppIntegrations"
"RolesAnywhere"
"TrustedAdvisor"
"Logs"
"EC2"
"CloudHSM"

Additional context
Add any other context about the problem here.
All services have been enabled in SQServiceTable including sagemaker and cloudfront.

Thank you for reporting this issue and providing detailed information. We understand that you're unable to find any traces of Amazon SageMaker or Amazon CloudFront quotas in the DynamoDB table, despite having enabled these services in the SQServiceTable.
We will investigate this issue and work on identifying the root cause. In the meantime, we would appreciate if you could provide us with any additional information or logs(specifically QM-ListManager-Function logs) that might be helpful in troubleshooting this issue.

Sure. Here's some logs

When I run aws service-quotas list-service-quotas --service-code cloudfront , I see no quotas, so we do not monitor Cloudfront service. Even for the services supported by service quotas, we filter out metrics that do not have CloudWatch AWS/Usage. For the SageMaker and the Warnings in the logs, we are releasing a patch this week. Hope it helps!

yeah this could be a bug or a temporary issue with the Service Quotas API for CloudFront.

Created an issue here: https://github.com/aws/aws-cli/issues/8941

Just pointing it out again, Even if that cli works, we will not monitor cloudfront because its quotas have got no Utilization metrics

Aaah sorry I misunderstood. Is this because all utilisation metrics come from cloudwatch? And cloudfront metrics aren't there? (failing this check i assume) Would you have a list of which other metrics are missing and would you have any idea if they will ever be added?

Yes that is the right code check. I don't know the specifics but Service quota team is the right team to answer that question but based our team discussion with the them, they are onboarding lot of AWS services

This is issue is fixed in the latest version v6.2.11


Support iteration type argument in randomized SVD

The PR https://github.com/dask/dask/pull/6813 introduced a regression where the number of iterations for randomized SVD can be set but it no has no effect with the default iteration type "none".  This new iterator parameter should be exposed in TruncatedSVD like the number of iterations parameter (n_iter).
https://github.com/dask/dask-ml/blob/134c77a8fa1da5b421a2a6ef868a176b23540f38/dask_ml/decomposition/truncated_svd.py#L9-L18

Hi @eric-czech, just checking - is this still a necessary addition, given that https://github.com/dask/dask-ml/pull/767 has been merged already?

Nope!  Sorry for letting it hang.  This can be ignored now.

Thanks for confirming!


Added dark humor detection task

This is the initial commit.

Not a reviewer. @cyc025, thank you for submitting this task!
I've noticed that the prompts for non-jokes in task.json are almost always much shorter than the prompts for jokes. A naive language model could cheat on this task by exploiting the correlation.
I would kindly suggest to reformulate the prompts in such a way, as to remove the correlation.

Not a reviewer. @cyc025, thank you for submitting this task!
I've noticed that the prompts for non-jokes in dark_humor_detection/task.json are almost always much shorter than the prompts for jokes. A naive language model could cheat on this task by exploiting the correlation.
I would kindly suggest to reformulate the prompts in such a way, as to remove the correlation.

I appreciate that feedback (Vielen danke!) and I'm revising the texts now.

@googlebot I fixed it.

@googlebot I signed it!

@googlebot I fixed it.

@googlebot I consent.

@googlebot I fixed it.

@googlebot I fixed it.

@guygurari can you help @cyc025 with licensing issue?

@guygurari can you help @cyc025 with licensing issue?

Hi @chiafullo  thanks for bringing it up, I actually resolved it later on by creating this new pull request:
https://github.com/google/BIG-bench/pull/345
Sorry for the confusion!


don't unregister exception and signal handlers after any exception/si…

…gnal is caught. save previous signal handlers and call them
we weren't calling previous signal handlers before. i'm hoping this fixes the root problem for https://github.com/mixpanel/mixpanel-iphone/issues/704

oh wait this still isn't working with crashlytics for signals. closing until i resolve that


Create Posts “hola-a-todos”

Automatically generated by Netlify CMS

👷 Deploy Preview for suspicious-bhabha-9e08fd processing.
🔨 Explore the source changes: fd31b837b6abe8c98a4be10d372573de37091ddb
🔍 Inspect the deploy log: https://app.netlify.com/sites/suspicious-bhabha-9e08fd/deploys/614b6d5ea1a9100008b37fd0


Modify application build process with selectable unity-app-generator versions

Control over the version of unity-app-generator used needs to be moved to a location that allows for more rapid deployment. The current method of baking the software into the Gitlab runner does not allow easily updating. Instead unity-app-generator at a specific version number should be deployed as a step before building the application. This additionally helps document in build logs what version of the app package generator was used.
Steps to correct:

Remove installing unity-app-generator from the Gitlab runner deployment
Modify the lambda function to pass a unity-app-generator version string
Add a step to the gitlab-ci.yml to install unity-app-generator with the passed version string

Steps:

Modify instance environment to install certain versions, test
Move to YAML afterwards with a version tag
Add passing of parameter to Gitlab from Lambda
Modify Gitlab YAML to use passed parameter

Use a Python virtual environment to install unity-app-generator and app-pack-generator into temporary directory for each pipeline build.

Not an obvious how to pass parameters to the automatically triggered app pack pipeline. Only have the ability to pass parameters to mcp-clone pipeline.
Will modify the .gitlab-yaml copied by mcp_clone to inject the version when copying into the repo.

Requires implementing issue unity-app-generator #19 first.

Implemented selection of versions to the Lambda.
Remaining work:

Additions to end user API to override default


⚠ Bofrost.de has degraded performance

In 68593eb, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1615 ms

Resolved: Bofrost.de performance has improved in a4ae44a.


Calling OpenAI API with function setup fails with "400 Bad request"

Calling OpenAI API with functions setup (following example 04) fails with "400 Bad request"

the POST to openAI backend looks like this:
const url = 'https://api.openai.com/v1/chat/completions';
const requestCfg = {
  headers: {
    'Content-Type': 'application/json',
    'Content-Length': 5558,
    'User-Agent': 'AlphaWave',
    Authorization: 'Bearer <my-api-token>'
  }
};
const request = {
  messages: [
    {
      role: 'user',
      content: '<my_content>'
    }
  ],
  max_tokens: 1000,
  temperature: 0.11,
  functions: [
    {
      name: 'custom_schema',
      description: 'Use custom JSON schema for output.',
      parameters: {
        type: 'object',
        properties: {
          company: {
            type: 'string'
          },
          address: {
            type: 'string'
          },
        required: [
          'company',
          'address',
        ]
      }
    }
  ],
  model: 'gpt-3.5-turbo'
};

Per the OpenAI docs https://platform.openai.com/docs/guides/function-calling, the function calling should have these props in  the request (copied from example in the doc):
  const tools = [
    {
      type: "function",
      function: {
        name: "get_current_weather",
        description: "Get the current weather in a given location",
        parameters: {
          type: "object",
          properties: {
            location: {
              type: "string",
              description: "The city and state, e.g. San Francisco, CA",
            },
            unit: { type: "string", enum: ["celsius", "fahrenheit"] },
          },
          required: ["location"],
        },
      },
    },
  ];

  const response = await openai.chat.completions.create({
    model: "gpt-4o",
    messages: messages,
    tools: tools,
    tool_choice: "auto", // auto is default, but we'll be explicit
  });

Analyzing the difference, request.messages prop is ok, but .functions prop is wrong, should be nested under .tools prop in a slightly different layout. Also there is a .tool_choice prop that would be needed, as I'd like to set it to "required".
To summarize, I see a disconnect between AlphaWave request and OpenAI docs, that .functions prop should be transformed into a similar .tools  prop.

I was able to resolve the 400 bad request with OpenAI API. It still supports "function" field, however, it is allergic to JSON Schema of size larger than few fields, and is geared toward using a monkey schema.
I also confirmed that OpenAI "tools" field has the same problem with JSON Schema.
I the meantime I made a local mod of OpenAIModel that uses "tools" field and return result. LMK if there's an interest for a PR.
Since neither "function" nor "tools" gives any real benefit for JSON Schema, closing this.


Some data points from Column Plot yield errors

Cohort:  TCGA Esophageal Cancer (ESCA)
Dataset:  somatic mutation SNPs and small INDELs (ucsc automated vcf)
Gene:  TP53

Line 34 of js/Tooltip.js has the following array contents.  Notice the 2nd index within the array...

Fixed via 375cfb257fc8c2f898a07e6e883869325c41809e


Team maintainer aren't set

I noticed, that some teams don't have a team maintainer, though for every team a team maintainer has been defined.

See https://github.com/opentelekomcloud/ansible-collection-gitcontrol/issues/34


Update Logo.png

just updating the logo for the governance token

You will need to resolve conflict, can you merge or use the latest version of master for the base of your PR?

yes will use the latest version of master


Error if component uses IxSelect or IxDropdown in unit test

Prerequisites

[X] I have not leaked any internal company information.
[X] I have not posted internal links or code snippets.

What happened?
Similarly the already fixed #882, this error only occurs in unit test, and not breaking that, just a log message, and i only observed if the problematic component has multiple unit test. If you have at least 4, than it is observable easily. I observed this bug with both the IxSelect component and the IxDropdown as well. My reasoning why this is an issue is also the same as the previous fixed issue.
ERROR: TypeError: Cannot read properties of undefined (reading 'destroy')
TypeError: Cannot read properties of undefined (reading 'destroy')
    at Dropdown.proto.disconnectedCallback (https://ne22ajecdpar-nf1l--9876--26ebe8bf.local-credentialless.webcontainer.io/_karma_webpack_/node_modules_siemens_ix_dist_esm_ix-select_entry_js.js:509:35)
    at safeCall (https://ne22ajecdpar-nf1l--9876--26ebe8bf.local-credentialless.webcontainer.io/_karma_webpack_/vendor.js:2845:30)
    at disconnectedCallback (https://ne22ajecdpar-nf1l--9876--26ebe8bf.local-credentialless.webcontainer.io/_karma_webpack_/vendor.js:3151:7)
    at https://ne22ajecdpar-nf1l--9876--26ebe8bf.local-credentialless.webcontainer.io/_karma_webpack_/vendor.js:3358:25
    at Object.jmp (https://ne22ajecdpar-nf1l--9876--26ebe8bf.local-credentialless.webcontainer.io/_karma_webpack_/vendor.js:3674:13)
    at HostElement.disconnectedCallback (https://ne22ajecdpar-nf1l--9876--26ebe8bf.local-credentialless.webcontainer.io/_karma_webpack_/vendor.js:3358:15)
    at _ZoneDelegate.invoke (https://ne22ajecdpar-nf1l--9876--26ebe8bf.local-credentialless.webcontainer.io/_karma_webpack_/polyfills.js:348:158)
    at ProxyZoneSpec.onInvoke (https://ne22ajecdpar-nf1l--9876--26ebe8bf.local-credentialless.webcontainer.io/_karma_webpack_/vendor.js:7644:33)
    at _ZoneDelegate.invoke (https://ne22ajecdpar-nf1l--9876--26ebe8bf.local-credentialless.webcontainer.io/_karma_webpack_/polyfills.js:348:46)

ERROR: TypeError: Cannot read properties of undefined (reading 'destroy')
TypeError: Cannot read properties of undefined (reading 'destroy')
    at Select.proto.disconnectedCallback (https://ne22ajecdpar-nf1l--9876--26ebe8bf.local-credentialless.webcontainer.io/_karma_webpack_/node_modules_siemens_ix_dist_esm_ix-select_entry_js.js:509:35)
    at safeCall (https://ne22ajecdpar-nf1l--9876--26ebe8bf.local-credentialless.webcontainer.io/_karma_webpack_/vendor.js:2845:30)
    at disconnectedCallback (https://ne22ajecdpar-nf1l--9876--26ebe8bf.local-credentialless.webcontainer.io/_karma_webpack_/vendor.js:3151:7)
    at https://ne22ajecdpar-nf1l--9876--26ebe8bf.local-credentialless.webcontainer.io/_karma_webpack_/vendor.js:3358:25
    at Object.jmp (https://ne22ajecdpar-nf1l--9876--26ebe8bf.local-credentialless.webcontainer.io/_karma_webpack_/vendor.js:3674:13)
    at HostElement.disconnectedCallback (https://ne22ajecdpar-nf1l--9876--26ebe8bf.local-credentialless.webcontainer.io/_karma_webpack_/vendor.js:3358:15)
    at _ZoneDelegate.invoke (https://ne22ajecdpar-nf1l--9876--26ebe8bf.local-credentialless.webcontainer.io/_karma_webpack_/polyfills.js:348:158)
    at ProxyZoneSpec.onInvoke (https://ne22ajecdpar-nf1l--9876--26ebe8bf.local-credentialless.webcontainer.io/_karma_webpack_/vendor.js:7644:33)
    at _ZoneDelegate.invoke (https://ne22ajecdpar-nf1l--9876--26ebe8bf.local-credentialless.webcontainer.io/_karma_webpack_/polyfills.js:348:46)

What type of frontend frameware are you seeing the problem on?
Angular
Which version of iX do you use?
2.0.4
Code to produce this issue.
https://stackblitz.com/edit/ne22aj-ecdpar

Internal ref [IX-877]

Please upgrade to version 2.1.0 or later, as the issue has been resolved.

Thank you!


Split infrastructure into components

qhub deploy currently splits the infrastructure deployment into stages using Terraform resource targeting.
This is 'wrong' according to Terraform, and we should consider splitting it up into separate configurations instead and rolling them out in order.
If we had clear separate configs then this would also mean we can destroy in reverse order, and I think this might help with our timeout problems on tear down. (We could technically do this with target anyway, but only if all remaining targets are listed explicitly - our final deploy step just runs everything, including the initially-targeted items too.)
From HCL docs:

Once Terraform has selected one or more resource instances that you've directly targeted, it will also then extend the selection to include all other objects that those selections depend on either directly or indirectly.
This targeting capability is provided for exceptional circumstances, such as recovering from mistakes or working around Terraform limitations. It is not recommended to use -target for routine operations, since this can lead to undetected configuration drift and confusion about how the true state of resources relates to configuration.
Instead of using -target as a means to operate on isolated portions of very large configurations, prefer instead to break large configurations into several smaller configurations that can each be independently applied. Data sources can be used to access information about resources created in other configurations, allowing a complex system architecture to be broken down into more manageable parts that can be updated independently.

Note I have attempted to improve qhub destroy using terraform targets in the meantime: https://github.com/Quansight/qhub/pull/948

Going to close this issue since it is implemented in #1003. We should definitely look into using terragrunt. Since right now the outputs from each module are being captured in python and being explicitly passed in via a var-files.


Programming exercises: Add Gradle as a project type for Java exercises on Atlassian Setup

Checklist
This PR has quite a lot of line additions but this is mainly due to the newly added template files (like .gitignore, etc.).
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Server

[x] I followed the coding and design guidelines.
[x] I added multiple integration tests (Spring) related to the features (with a high test coverage).
[x] I implemented the changes with a good performance and prevented too many database calls.
[x] I documented the Java code using JavaDoc style.

Client

[x] I followed the coding and design guidelines.
[x] I added multiple screenshots/screencasts of my UI changes.

Changes affecting Programming Exercises

[ ] I tested all changes and their related features with all corresponding user types on Test Server 1 (Atlassian Suite).
[ ] I tested all changes and their related features with all corresponding user types on Test Server 2 (Jenkins and Gitlab).
-> The new project type is only available on the Atlassian Setup. However, these changes should not cause any problems on the Jenkins/Gitlab-Setup. In addition, these project types should not be selectable on this setup.

Motivation and Context
As part of the Bachelor Thesis from @Hialus and @ole-ve about the automatic generation of code hints for programming exercises (HESTIA) in Java, testwise coverage has to be recorded. We will use a plugin that is only available for Gradle projects, therefore we decided to add Gradle as a new project type.
In addition, Maven is getting less innovative and may be considered as not state-of-the-art anymore.
Description
This PR introduces two new project types:

Plain - Gradle: The template and solution repositories are plain Java code, the test repository is a Gradle project. The Maven equivalent in Artemis is 'Eclipse' for which the template and solution repositories are also plain Java code but the test repository is a Maven project.
Gradle - Gradle: The template, solution, and test repository are all Gradle projects. The Maven equivalent is 'Maven' where all three repositories are Maven projects.

The creation of the project files has been adapted as well as the creation of the build plans on the Bamboo server.
Related changes
In order to work, the following related changes have been made:

Changing the Ares testing framework to support Gradle: #191
The builds can be a little bit slow. This is due to the fact that the used artemis-maven-template Docker images which is used to cache most common dependencies are not updated to also include the Gradle wrapper. This will be changed independently of this PR.

Steps for Testing
Prerequisites:

Testserver with the Atlassian Setup (TS1, TS3)
1 Instructor
1 Student

Log in to Artemis
Navigate to Course Administration
Navigate to Exercises
Generate new Java programming exercises. Check for both projects type 'Plain - Gradle' and 'Gradle - Gradle' that the following things are working correctly:

creating the build plans and repositories
Template Score: 0%, Solution Score: 100%
importing as a Gradle project into the local IDE works fine
when activating the static code analysis, introducing some style issues, and pushing the changes, the build result contains feedback on these style issues
when applying and pushing changes to (one of the three) repositories, the test case results update accordingly and these results are as expected
when pushing some code that does not compile, the build result shows a build error
adding new dependencies to the build.gradle in the test repository and using classes from this dependency works fine
when activating sequential test runs, confirm that the behavioral tests are only executed after the structural tests have all passed. Otherwise, no test results are shown for these behavioral tests.
When opening all three repositories locally, everything should work as expected.

Only for project type 'Gradle - Gradle':

Check that also the solution and template repository are Gradle projects
Add a dependency to all three repositories and use classes from this dependency. When pushing the changes the result should be as expected.

Review Progress
Code Review

[ ] Review 1
[ ] Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Screenshots

I would also like to see some server tests for the new changes.

I am working on that. I am figuring out a neat way how to execute Gradle builds from within Java.

This seems to be interesting!
Do you also plan to create build plans for Jenkins (I would assume that this should be easily doable :) and would enhance the PR a lot) ?

This seems to be interesting! Do you also plan to create build plans for Jenkins (I would assume that this should be easily doable :) and would enhance the PR a lot) ?

This should be no big challenge and I will definitely implement it. But maybe not in this PR but as a soon (and very small) follow-up since this PR already adds a lot of functionality to be tested into a sensible area of Artemis.

I experimented a bit with the new project type:

The problem statement contains for example the test case testBubbleSort. This always shows up in grey in the problem statement as the result is reported for test case testBubbleSort(). The same applies to other behavioural test cases.
Code issues are not marked in the online editor as the path contains the prefix /opt/bambooagent/bamboo-agent-home/xml-data/build-dir/TESTINGSESSIONGRADLEBFEIN-SOLUTION-JOB1/ instead of e.g., only src/main/resources/bfein/Context.java.
The build errors are not marked in the code editor but only shown in the build output. The current parsing code expects the Maven format for errors.
Locally, running ./gradlew does not seem to work because the actual gradle/wrapper/gradle-wrapper.jar is missing.
I think it would be nice to have another entry in the sourceSets of build.gradletest {
    java {
        srcDir "localtest" // not necessarily final name
    }
}

so that students can easily add their own unit tests during local development if they want. That localtest directory would have to be created beforehand and contain some .keep/.gitkeep file so that the Alt+Insert->Test action works correctly in IntelliJ.

Okay, I only suggested it because we have got some exercises where we encourage writing own tests.
I looks like the default Maven template does not have a local tests directory set up either, so I assume it is not/rarely used at TUM. Therefore, not adding it to this template either and requiring the additional small setup step for instructors is perfectly fine by me.

The problem statement contains for example the test case testBubbleSort. This always shows up in grey in the problem statement as the result is reported for test case testBubbleSort(). The same applies to other behavioural test cases.

79b4abf: I changed the problem statement for the gradle template accordingly.

Code issues are not marked in the online editor as the path contains the prefix /opt/bambooagent/bamboo-agent-home/xml-data/build-dir/TESTINGSESSIONGRADLEBFEIN-SOLUTION-JOB1/ instead of e.g., only src/main/resources/bfein/Context.java.

2657b1f: Directories are included in the static code analysis that are not part of the copied submission (src/main/java and src/main/resource). I implicitly removed those directories from the main source set by setting the assignment folder (where the copied submission is located) as the only main source. There is no scenario where files in these directories would be used in the test repository.

The build errors are not marked in the code editor but only shown in the build output. The current parsing code expects the Maven format for errors.

487f920: I fixed this by introducing a new regex matching the build error for Gradle build output. I know that the taken solution is not the best, but this is mainly due to the messy code parsing the build log for errors. Refactoring is definitely required, but also out of scope for this PR. I will take a look at this in a separate PR.

Locally, running ./gradlew does not seem to work because the actual gradle/wrapper/gradle-wrapper.jar is missing.

b30be0f: I fixed this by including the corresponding gradle-wrapper.jar into the repository.

Could you please link a follow-up issue / pr here that deals with gradle for jenkins/gitlab as well :)
At my university, some people are looking forward to this. Therefore, I could link such an issue to them :)


timeSecond.every(x),  x modulo 60 is a restriction?

I try to use d3time.timeSecond.every(x) to create interval, which i use to generate ticks for time scale. The x is dynamic, meaning it depends on the time scale domain and range. Whenever x changes i create new interval for tick creation.
I am almost sure, that it is not a bug. But i would rather ask a question to be 100% sure, or may be to alter the behaviour of the timeSecond interval.
It seems, that x  in d3time.timeSecond.every(x) is rounded modulo 60.
When i create interval with say x=320, and pass it to timeScale.ticks i get ticks distributed evenly with 60s distance between one another.
How can i solve my task, given the x may be greater then 60?
I expected that d3time.timeSecond(320) creates an interval, which passed to timeScale.ticks() will produce ticks distributed evenly with 320s distance to one another.
May be i do not see the reason or the restriction which makes mentioned behaviour impossible
p.s.: huh, sounds messy, sorry for that, i did my best to describe my case.
p.s.2: i will try to provide a sample code for clarification soon

Assembled an example to demonstrate the case. fiddle
< Example code
console.clear();

const ticksView = d3.timeSecond.every(320);
const tscale = d3.scaleTime();

const left = new Date(2015, 0, 1);
const right = new Date(left);
right.setHours(right.getHours() + 2);

const expectedAvgDistance = 320;
const duration = (right - left) / 1000;
const expectedNumberOfTicks = Math.floor(duration / expectedAvgDistance);

tscale.range([0, 1000]);
tscale.domain([left, right]);
const ticks = tscale.ticks(ticksView);
const { length: butGotTicks } = ticks;
const butGotAvgDistance = duration / butGotTicks;
console.log({ duration, expectedAvgDistance, expectedNumberOfTicks, butGotTicks,  butGotAvgDistance });

< Example output
butGotAvgDistance: 59.50413223140496
butGotTicks: 121
duration: 7200
expectedAvgDistance: 320
expectedNumberOfTicks: 22

Yes, this is the behavior of interval.every. Per the API Reference, emphasis added:

Returns a filtered view of this interval representing every stepth date. The meaning of step is dependent on this interval’s parent interval as defined by the field function. For example, timeMinute.every(15) returns an interval representing every fifteen minutes, starting on the hour: :00, :15, :30, :45, etc. Note that for some intervals, the resulting dates may not be uniformly-spaced; timeDay’s parent interval is timeMonth, and thus the interval number resets at the start of each month. If step is not valid, returns null. If step is one, returns this interval.
This method can be used in conjunction with interval.range to ensure that two overlapping ranges are consistent. For example, this range contains odd days:

d3.timeDay.every(2).range(new Date(2015, 0, 1), new Date(2015, 0, 7));
// [Thu Jan 01 2015 00:00:00 GMT-0800 (PST),
//  Sat Jan 03 2015 00:00:00 GMT-0800 (PST),
//  Mon Jan 05 2015 00:00:00 GMT-0800 (PST)]
>
>As does this one:
>
>```js
d3.timeDay.every(2).range(new Date(2015, 0, 2), new Date(2015, 0, 8));
// [Sat Jan 03 2015 00:00:00 GMT-0800 (PST),
//  Mon Jan 05 2015 00:00:00 GMT-0800 (PST),
//  Wed Jan 07 2015 00:00:00 GMT-0800 (PST)]

See also interval.filter.

In the case of seconds, the field number is in [0, 60] (though 60 only occurs with leap seconds), so higher values don’t make sense.
You probably want to define a custom time interval instead of using interval.every, such as:
function fixedDuration(ms) {
  return d3.timeInterval(function(date) {
    date.setTime(Math.floor(date / ms) * ms);
  }, function(date, step) {
    date.setTime(+date + step * ms);
  }, function(start, end) {
    return (end - start) / ms;
  });
}

var interval = fixedDuration(320 * 1000); // Every 320s since UNIX epoch.

https://runkit.com/mbostock/5820c97c7757c900142a53e4

@mbostock Awesome! Thank you very much! That is exactly what i need! 👍


fix(Jenkinsfile): adjust timeout

Some of our jobs take rather long to complete which esp. in combination with retires leads to false negatives. This PR increase the timeout to reduce the number of false negatives due to timeouts. I thought about removing the timeout but decided that we should always investigate what happened if a pipeline runs for longer than 3 hours and thus kept the timeout. The timeout also saves us form rouge builds that run for ever, an issue other teams ran into.

We should look into why our tests are taking so long to finish.


Next Problem in Files behaving oddly

Hi,
When working with a file with many spelling errors the "Next Problem in Files" (F8) keypress began behaving oddly. This was noted with Visual Studio Code for Mac (v1.28.2).
The behaviour I would see was:

Press F8 repeatedly to navigate past the non-spelling issues (e.g. duplicate keys)
Find a spelling issue and correct it
Press F8 again to navigate to the next issue, and the position in the "problem list" would regress and you would start navigating past problems you'd already seen
Can you please make it so the final F8 keypress continues on from the current position in the problems list, rather than regressing to an problem we'd already skipped past?

I'd suggest using this file to test the issue:
https://github.com/api-lifecycle-workshop/locations/blob/dc7d8a70b178141872c786d9d19f81ba550bdbbe/_config.yml
With this file there were 70+ problems, and while I was working through them I'd frequently find myself bumped from problem ~20 back to problem ~13, and so frequently navigated past the duplicate key issues I didn't care about.
Thanks, Matt

I'll take a look


Subscripting crashes when cast to Int8/Int16/Int32/Int64

Currently Swift subscript is of type Any?. As such, we cannot return a different type based on context, so we always return the Objective-C types. Most of these types are implicitly bridged, but those that aren't might unexpectedly cause crashes.
foo["intCol"]  as! Int  // 😎
foo["int8Col"] as! Int8 // crash!

The workaround is to access the value as an NSNumber and then explicitly bridge.
(foo["int8Col"] as! NSNumber).int8Value // 😎

There are 2 potential ways to solve this. Both break some existing code:

Convert to Swift property type before returning value. We can look this type up by property name in the schema. Note that this will silently break existing code that assumes Int8/Int16/Int32/Int64 values are returned as NSNumber, which isn't implicitly bridged.
Supplement Any? function with overloads for every possible type so that Swift can infer correct version based on context. This code require a lot of boilerplate. Also, this breaks using subscript in Any contexts due to Swift's overload resolution rules.

An ideal solution requires a change in Swift. We could also wait for either:

Swift adds generic subscripts, allowing us to return T? and perform the bridging in the function based on the inferred type.
Swift adds implicit bridging between NSNumber and Int8/Int16/Int32/Int64. Note that while this solution may seem ideal (if fixed in Swift), the generic solution is probably preferable since it doesn't rely on any Objective-C compatibility features (and thus would be easier to mirror in a pure Swift API).

EDIT: This issue should also track KVC's lack of bridging which crashes due to the same issue. This is probably slightly less problematic because it's an NSObject API more than a Realm API.

This was implemented in Swift meanwhile.
https://github.com/realm/realm-cocoa/pull/7057 adds the tests to make sure it works.

This was implemented in Swift meanwhile.
https://github.com/realm/realm-cocoa/pull/7057 adds the tests to make sure it works.


New 0.0.22 release breaks sdkman on Ubuntu 20.04

It looks like it was compiled against Glibc >= 2.32 but Ubuntu 20.04 only has 2.31...
... is this intentional or is there any way to continue to support Glibc 2.31?
    packer-ubuntu.amazon-ebs.ubuntu_base: [env-versions] /home/runners/.sdkman/libexec/version: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /home/runners/.sdkman/libexec/version)
    packer-ubuntu.amazon-ebs.ubuntu_base: [env-versions] /home/runners/.sdkman/libexec/version: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /home/runners/.sdkman/libexec/version)
    packer-ubuntu.amazon-ebs.ubuntu_base: [env-versions] /home/runners/.sdkman/libexec/version: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /home/runners/.sdkman/libexec/version)

+1!
Semi related, it seems like there is (or was) some issue with how releases actually update get.sdkman.io.  We were last able to successfully invoke sdkman native version 0.0.15 on Jan 26 (installing sdkman via the recommended curl -s https://get.sdkman.io | bash approach)
For some reason after Jan 28, the get.sdkman.io endpoint, jumped to getting version 0.0.22, and at this point our Ubuntu 20.04 base stopped being able to invoke sdkman post-installation.

Thanks both, I'll see if I can set the build to explicitly use the earlier version of GLIBC.

Hi @shakefu and @jbury,
I replicated this and have now tied our builds to GH runners using Ubuntu 20.04. I released native extensions 0.0.23, and tested this on Ubuntu 20.04 and 22.04, which seems to work well.
Could both of you please confirm that the latest release has resolved the problem?


Changing the resources needed for buildings

Is it possible to change the costs of some buildings ?

Short answer: Yes!
(The patch already changes the price of the market (to zero)
Any more specific thoughts (like implementable for all patch users) or more for personal taste? For example, blacksmith costs were discussed in https://github.com/Sh0wdown/UnofficialCrusaderPatch/issues/469, and for example I recall somebody suggesting to make also the houses free, as the AI sometimes struggles when it has wood shortages. Or changing unit costs, or...
Anyway, except for the free market and the costs of Ladderman, no "finetuning" of ingame cost was done in the patcher and always leads to discussions.
P.S.: I suggest to change the title, as this is quite misleading: It suggests the question "Is it possible to change the resources a building produces?" (Yes, amount and resource should also be possible (If one wants a stone producing Fletcher).)

The thing is i want to create an alternative winning scenario for my offline LAN event.
For this I thought about changing the costs of the round tower to (1000 wood and 1000 Stone).
Sorry if my question was not that clear.
If this is possible how can I do it ?

I can maybe look sunday into the round tower to change it, maybe I can give you a script or the changed exe.

Yeah, maybe I should make my answer more clear: It is in general possible, however, the Patch as it is right now does not have this as an option.

I can look into it with cheatengine, and maybe I can change it

J-T-de that's true and I know it.
PodeCaraox did you find out something ? Or can you tell me more about the cheatengine, so I can give it a try ?

Okay, I found all building costs (and the corresponding buildings) in the .exe, I only have to figure out how to include it to the UCP. Single costs would easily work (as depicted here https://github.com/Sh0wdown/UnofficialCrusaderPatch/issues/270 ), but I would prefer an .aic - like config, where I have to figure out how to implement this.
Regarding Cheat-Engine: here are the basics one has to know https://github.com/Sh0wdown/UnofficialCrusaderPatch/issues/270#issuecomment-475943521 , but this alone is only the start...

damn, if @J-T-de is as quick as that, we might see a new realease of the UCP just by him soon. Maybe you ll take over his work and just contribute. I am sure, if he sees your skills he ll make you a contributer and then you can manage the project alongside him somehow?


panic: error generating pkgs

Hey, thanks for the great tool :) Unfortunately I have an issue creating the toml file for this repo. To reproduce:
git clone https://github.com/veertuinc/anklet.git
pushd anklet
nix shell github:nix-community/gomod2nix
gomod2nix generate

results in this output:
INFO[0000] Parsing go.mod                                modPath=go.mod
INFO[0000] Downloading dependencies
panic: error generating pkgs: exit status 1

goroutine 1 [running]:
github.com/nix-community/gomod2nix/internal/cmd.generateFunc(0xb23dc0?, {0xb5a2c8?, 0x0?, 0x0?})
        /build/source/internal/cmd/root.go:67 +0x416
github.com/spf13/cobra.(*Command).execute(0xb23dc0, {0xb5a2c8, 0x0, 0x0})
        /build/source/vendor/github.com/spf13/cobra/command.go:987 +0xaa7
github.com/spf13/cobra.(*Command).ExecuteC(0xb23ae0)
        /build/source/vendor/github.com/spf13/cobra/command.go:1115 +0x417
github.com/spf13/cobra.(*Command).Execute(...)
        /build/source/vendor/github.com/spf13/cobra/command.go:1039
github.com/nix-community/gomod2nix/internal/cmd.Execute()
        /build/source/internal/cmd/root.go:124 +0x25
main.main()
        /build/source/main.go:6 +0x17

do you have any idea what might be wrong here? Thanks!
EDIT: I have checked the other issues I could find for this error but the patch version is defined in the go.mod and everything else wasn't applicable

i already had 1.23.0
this fixed it for me:
    gomod2nix.inputs.nixpkgs.follows = "nixpkgs";


Markdown stripping parameters from URLs when the URL contains the word 'issues'

Gogs version (or commit ref): <IP_ADDRESS>9
Git version: 1.9.1
Operating system: Ubuntu 14.04.4 LTS
Database:

[x] PostgreSQL

Can you reproduce the bug at http://try.gogs.io:

[x] Yes https://try.gogs.io/ultralisk/ultratest/issues/2

Description
I pasted a link into an issue comment which happened to have a similar structure to a gogs URL, gogs treated the URL like a reference link as well as stripped the parameters that the linked contained.
...

The regex processing I could find in the code starts at ./modules/markdown.go at line 79.
Testing off of the Go code:
IssueFullPattern = regexp.MustCompile(`(\s|^)https?.\*`issues/[0-9]+(#+[0-9a-zA-Z-]\*`)?\`)

This essentially means any URL with the format http://...issues/[0-9] will format as a link to an issue, all ?s are optional expressions so it could be either http or https
Test Cases:

Input URL
Output Formatting

http://1111/2222/ssss-issues/3333?param=blah&blahh=333
#3333

http://test.com/issues/33333
#33333

http://test.com/issues/3
#3

http://issues/333
#333

https://issues/333
#333

http://tissues/0
#0

The outputs were links, you can check the actual output from my post at https://try.gogs.io/ultralisk/ultratest/issues/3

In addition to that, IssueFullPattern is used to process later in markdown.go at line 128.
m = IssueFullPattern.Find(link)
	if m != nil {
		m = bytes.TrimSpace(m)
		i := strings.Index(string(m), "issues/")
		j := strings.Index(string(m), "#")
		if j == -1 {
			j = len(m)
		}
		out.WriteString(fmt.Sprintf(` <a href="%s">#%s</a>`, m, base.ShortSha(string(m[i+7:j]))))
		return
	}

If it could be done with logic to detect the hostname or network address then this could process regex on only valid hosts. Not that it can be done to work 100% of the time, but it definitely is a starting concept.

@tcarrio injecting settings.AppSubUrl in the regex would fix this issue, and is IMO preferable :)

@bkcsoft I'm only concerned that won't consider instances that are run using localhost or a direct IP address where settings.AppSubUrl returns the hostname

well, I meant settings.AppUrl which is set in https://github.com/gogits/gogs/blob/master/modules/setting/setting.go#L309
and default being https://github.com/gogits/gogs/blob/master/conf/app.ini#L55

That would go a long way in fixing this issue

I'm going to try to work on it.  My work will be on this branch: https://github.com/cstroe/gogs/tree/issue-3006

I have a fix in this PR https://github.com/gogits/gogs/pull/3121
Please feel free to test and suggest any changes.

Close as fixed.


Use inner channel when current channel is not netty or direct

Fix: If transport channel is not netty or direct, check if getInnerChannel is implemented using reflection and use that channel.

Code change looks good. will wait for combine test result post CI changes.


"make test" fails, but then passes if run manually

Hi, I'm trying to compile & install openvdb, and "make test" fails both of the tests.
Looking at /path/to/openvdb/build/Testing/Temporary/LastTest.log, it appears that "vdb_unit_test" very nearly passes -- only 21 tests barely fail the double equality assertion test. And that result is replicated by manually running "/path/to/openvdb/build/openvdb/vdb_test".
Is this normal, and can I ignore the failed tests?
"pytest" is more interesting... When run as part of the "make test" command, it immediately fails with this error:
Traceback (most recent call last):   File "/path/to/openvdb/openvdb/python/test/TestOpenVDB.py", line 41, in <module>     import studioenv ImportError: No module named studioenv <end of output>
But when I run the test manually by copying and pasting the command from the failed test log: "/usr/bin/python" "/path/to/openvdb/openvdb/python/test/TestOpenVDB.py", it passes all 16 tests.
What's "studioenv"? I've been googling for a python module with that name for a while, and can't find anything. Second, why would the test suddenly start working when I ran it manually?
Thanks

The test fails for me too, but pasting the command still leads to the same error with me.

With the recent changes and ports to CMake, the test commands have been changed and I believe this is resolved. Closing, but feel free to re-open should this issue persist


Column: Switchable button (with state)

Hey,
is it possible to make column with buttons as "switches"? Meaning each row will have its own state and the button would render accordingly. It should not be coupled to the action buttons.
Example:

Column
Action
On click

Value 1
Published (green)
Unpublished (red)

Value 2
Unpublished (red)
Publishes (green)

It is something like this: http://grid.mesour.com/version2/column/status/
The reason:
Right now I do this using custom renderer and I do it quite often, it would be great to have some option to do this natively.

1, You know - it is project/client/developer specific, thought it's used very often.
2, It is not so hard to implement that in some base datagrid factory.
But i will think about it.

Thanks :)

It is in master for now. I have to put in in documentation before tagging.

So you decided to go for it? Great! Thanks.

It is tagged as v2.3 now. Is it suitable for your projects? Or do you need another behaviour?

I'll get back to you once I get time to check it out, busy right now. :/

Hey, I've quickly checked the docs and the status column looks great!


Pooya

I replaced links with the exact web address in my browser.

In other parts also the links are like: https://en.wikipedia.org/wiki/Encapsulation_(computer_programming) which aren't correct. Should I replace them with the form which can be copy pasted in the browser like https://en.wikipedia.org/wiki/Encapsulation_(computer_programming) ?


Import the suppressions per report

CodeChecker cmd suppress run_name -i <import_file>
will only import suppressions for the run indicated by run_name,
and not all reports.
Suppressions are imported as single report suppressions
instead of suppression rules.
This is the behaviour the user expects when run name is given
as a parameter to the command.
This patch also fixes the changeReviewStatus(report_id, status, message)
API function to change the review status of a single report only
instead of all reports with the same hash.

I fixed all your comments. Ready to be merged.


Fixed Molniya Plot Error

This PR will resolve issue #1117 .

Thank you @96RadhikaJadhav, merging this!


Allow the preloading script to create a preloaded COS image in different projects

By adding a command line arg for '_DEST_PROJECT', we can specify which project the preloaded image should be uploaded to. Previously, it would just use the default project in the gcloud config of whatever/whomever was invoking the dev_cloudbuild.yaml script.
Ideally, this will allow us to upload the preloaded image to the gcp-guest project, like the other preloaded images for other distros during the guest-package-build concourse pipeline.

/ok-to-test
Would you be able to squash all the commits?


Bumping miniconda version in RTD

Seeing it this fixes https://github.com/numba/numba/pull/8809

Mamba is necessary to get conda>=4.8

fix added to #8809


INTN_MAX macro constants are defined in <stdint.h>

Hence they are C99, not C89!
Again, I don't see how we can possibly support 64-bit integers in pure C89.

If json_int_t is known to be at least 64-bit, can we perhaps limit ourselves to the following?
#define JSON_INT_MAX<PHONE_NUMBER>854775807

But then I'm not even sure such a large integer is valid in C89...

I think the point of allowing the user to define jons_int_t is that it could be defined smaller than 64 bits (or larger) depending on the user's needs. Perhaps we should merge #102 first.

Actually, it's best to let end users define JSON_INT_MAX themselves in a non-portable way if needed, just like json_int_t.

That shouldn't be difficult to achieve. Though, with all this compile time customizability, I will want to add some way to detect mismatched compile settings as early as possible, worst case scenario being runtime asserts in debug builds.

See #115.


Rethink simtools.testing

The simtools.testing modules provide functionality used for integration tests. One of the motivation to have it there was to have it tested in a typical unit test setup.
This is not ideal, as this code is not need to run simtools and does not need to be delivered to the user. Rethink the approach and change if necessary.

The dependency on pytest is removed with PR #1286
Suggest to close this issue. We still have the testing modules as part of the user code, but we gain through in this approach that this code is tested on a similar level. The only other alternative I could imagine is to add a src/simtools-testing package. This seems to be a bit excessive for the few functions we have in the testing module.
Close this?

Agree, can close


doc: Update readme with the support matrix for OT collectors

Update readme with the support matrix for OT collectors

According to support poloicy we should backport security fix to all supported versions

@rnishtala-sumo what's the status of this PR? Seems to have fallen by the wayside.

@echlebek I believe the final decision was that we're not taking this approach to support multiple prior versions. We're going to stick to the current, which is only support the latest version.


No information about down time during ASE Scale up/down

[Enter feedback here]
Under "How Scaling Works section", There is no information related to Down time of the application during Scale UP/Down in ASE.
Please include Application down time/ availability related information during Scale up or down on ASE
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e754567e-9482-5693-5ef8-6cc811ea7f57
Version Independent ID: 7c87e9ce-cf7f-120d-e6a3-9b605e231ef3
Content: Use and manage an App Service Environment - Azure App Service Environment
Content Source: articles/app-service/environment/using-an-ase.md
Service: app-service
GitHub Login: @ccompy
Microsoft Alias: ccompy

@NagaSandeepZen3 Thanks for the feedback! We are taking a look into this and will get back to you soon.

@NagaSandeepZen3 Thanks for the feedback! We are taking a look into this and will get back to you soon.

Thanks for asking question! The time frame is not mentioned as it depends on a numbers of factors.
You may refer to this document Scaling apps in an App Service Environment v1 might be helpful.
As mentioned in the document that  the multitenant App Service, scaling is usually immediate because a pool of resources is readily available to support it. In an ASE, there is no such buffer, and resources are allocated upon need.
In ASEv2, when you scale an App Service plan, the needed infrastructure is automatically added and there is a time delay to scale operations while the infrastructure is added.
In ASEv1, the needed infrastructure must be added before you can create or scale out your App Service plan.
Also note that Moving an ASP from one worker pool will cause cold starts of the apps in that ASP. This can cause requests to run slowly as your app is cold started on the new compute resources. The cold start can be avoided by using the application warm up capability in Azure App Service. The Application Initialization module described in the article also works for cold starts because the initialization process is also invoked when apps are cold started on new compute resources.
Hope this helps.

Thanks for asking question! The time frame is not mentioned as it depends on a numbers of factors.
You may refer to this document Scaling apps in an App Service Environment v1 might be helpful.
As mentioned in the document that  the multitenant App Service, scaling is usually immediate because a pool of resources is readily available to support it. In an ASE, there is no such buffer, and resources are allocated upon need.
In ASEv2, when you scale an App Service plan, the needed infrastructure is automatically added and there is a time delay to scale operations while the infrastructure is added.
In ASEv1, the needed infrastructure must be added before you can create or scale out your App Service plan.
Also note that Moving an ASP from one worker pool will cause cold starts of the apps in that ASP. This can cause requests to run slowly as your app is cold started on the new compute resources. The cold start can be avoided by using the application warm up capability in Azure App Service. The Application Initialization module described in the article also works for cold starts because the initialization process is also invoked when apps are cold started on new compute resources.
Hope this helps.

@nagasandeepp We will now proceed to close this thread. If there are further questions regarding this matter, please let us know. We will gladly continue the discussion.

@nagasandeepp We will now proceed to close this thread. If there are further questions regarding this matter, please let us know. We will gladly continue the discussion.


Refactored Activity to add Lumberjack into it.

Added lumberjack into the Activity class in order to ease the logging of the endpoints.

LGTM

:+1:


Application Layout/Application Links Selected Issue

When using the Application Layout Control with Bootstrap theme the application links do not get an "active" class assigned if property of 'selected' or 'selection' have value of true.  Either issue in Bootstrap theme or in Application Layout control.

Found the source of this issue. It is due to the method makeSelectedActive in ApplicationLinksRenderer returning false.
This appears to be a remnant of the original Bootstrap4XPages project, as you can see the same method returns false here: https://github.com/OpenNTF/Bootstrap4XPages/blob/master/eclipse/plugins/org.openntf.xsp.bootstrap/src/org/openntf/xsp/bootstrap/renderkit/html_extended/extlib/layout/tree/BootstrapApplicationLinksRenderer.java
Simple fix is to remove the method in ApplicationLinksRenderer and revert to the handling in the superclass. Only concern is any unexpected side effects, but it seems like it should be pretty clean.

Closing as a duplicate of #79


mDNS should be configurable via KConfig (IDFGH-2027)

Environment

Development Kit:     ESP32-DevKitC
Kit version (for WroverKit/PicoKit/DevKitC): v3
Module or chip used:  ESP32-WROOM-32
IDF version (run git describe --tags to find it): v3.3 (all versions really)
Build System:         CMake
Compiler version (run xtensa-esp32-elf-gcc --version to find it): 5.2.0
Operating System:     Windows
Power Supply:         USB

Problem Description
mDNS task runs at a very low priority and pinned to core 0 (PRO_CPU). It would be good to make these options configurable via KConfig:

task priority
task pinned to core (0, 1, floating)
mdns_service_add timeout (used here)
expose MDNS_TIMER_PERIOD_US

Expected Behavior
Calling mdns_service_add should not timeout due to higher priority task running on the same core.
Actual Behavior
mdns_service_add returns ESP_FAIL on first call as seen in https://github.com/atanisoft/ESP32CommandStation/issues/26. When the API returns ESP_FAIL I've added a workaround to reschedule the call to mdns_service_add at a later time which returns ESP_OK.
Even with mdns_service_add() returning ESP_OK the service description is not seen from other devices (rPi as example):
pi@RPi-JMRI:~/openmrn $ avahi-browse -a -t -k
+  wlan0 IPv6 _openlcb-can._tcp                             _openlcb-can._tcp    local
+  wlan0 IPv4 _openlcb-can._tcp                             _openlcb-can._tcp    local
+  wlan0 IPv6 RPI-JMRI                                      _device-info._tcp    local
+  wlan0 IPv4 RPI-JMRI                                      _device-info._tcp    local
+  wlan0 IPv6 RPI-JMRI                                      _smb._tcp            local
+  wlan0 IPv4 RPI-JMRI                                      _smb._tcp            local

Steps to repropduce
in app_main() set the current task priority higher than 1 and not call vTaskDelay(), inside the code call mdns_service_add() and verify the return value.
Code to reproduce this issue
https://github.com/atanisoft/ESP32CommandStation/tree/development can be used to reproduce this by using PlatformIO to compile/flash it to the ESP32 using the default configuration settings.

+1 and also need to make task stack size configurable

make task stack size configurable

I'm not certain it can be shrunk much unfortunately. There doesn't seem to be much need to increase it.  But if you have a usecase for adjusting it then I'm all for the extra flexibility, I just haven't found one yet.

@atanisoft,
as for now it defined: #define MDNS_SERVICE_STACK_DEPTH    4096
in my case (4 registed services) I have never seen stack usage more than 50%:

@no1seman makes sense, it could likely be dropped some in your case.
Can you share the code for generating the table with usage percent? I haven't been able to get the percentage to make much sense in my tests.

@atanisoft ,
it's impossible for now, because there's to much dependencies in my project, but it's not so hrd to make, just look into tskTCB structure ($IDF_PATH/components/freertos/tasks.c)  and you'll be able to make your own.


raftstore: fix metrics for Apply wait duration (#9893)

Signed-off-by: Xu Qiaolun<EMAIL_ADDRESS>
What problem does this PR solve?
Issue Number: close #9893
Problem Summary: Apply wait duration measurement error.
Release note

No release note

/merge
Thank you!

/run-cherry-picker


Running LuckPerms title...

I know I asked this already but I was able to take out the prefix using lang.yml but the plugin / version is still not editable from the lang.yml
Can you help me hide this? The main reason is I am hiding all the plugins used on the server. As you can see I am simply using the default bukkit permission for all invalid actions.
Thanks

If players are even thinking about using the /lp command, then surely they already know LuckPerms is on your server?
What's the big deal with trying to hide things?

Just want to see if I can hide everything and I want to make the server appears as vanilla as possible

If players are even thinking about using the /lp command, then surely they already know LuckPerms is on your server?

Just get a command blocker plugin if you're really that bothered.

Thank you for your thoughts.


#4 Adding the hover effect animation to the feature card

https://github.com/user-attachments/assets/3aa22537-6e80-4065-8ce8-d324fc404ccd

@Biplab-313 pls review these changes

#4


add preloads to schemas

Add ability to define preloads in :schemas options to avoid preloading into build_object
defmodule People do
  use Algoliax.Indexer,
    index_name: :algoliax_people,
    object_id: :reference,
    schemas: [{__MODULE__, [:animals]}],
    algolia: [
      attributes_for_faceting: ["age"],
      searchable_attributes: ["full_name"],
      custom_ranking: ["desc(updated_at)"]
    ]
end

Todo:

[ ] preload on batch for reindex and reindex_atomic

close with #29


Provide explicit release to nd-configure if it fails to determine one, specify minimal version of datalad (>= 0.10.0) for conda

This should address the problems for using datalad-installer on github actions in ubuntu-latest

there was also a gotcha with stuck for weeks con/tinuous fetch for datalad/git-annex which prevented download/indexing of recent 0828 git-annex release, and then I had to fix up https://datasets.datalad.org/datalad/packages/update.sh since it was not copying .exe and that lead to appveyor windows test to fail here.

Woohoo, green!


feat(layers): transport layers

Motivation
Implementating a simple Transport retry layer for a RpcClient.

Solution
WIP.
Implement a custom Transport layer called RetryLayer which uses RetryPolicy to determine whether to retry a request or not.
A couple of TODOs, but I wanted to get a review before proceeding. The end goal is to implement a RetryLayer like the one in ethers

PR Checklist

[x] Added Documentation
[ ] Breaking changes

Is this something we want to include in alloy directly, basically the foundry retry implementation?

It would be ideal if this could be integrated into alloy directly in such a way that allows for a generic retry policy to be provided. I think a lot of consumers currently have to implement the full stack in their own codebase such as what I did here, which is undesirable.

Should we close this given we're doing the retry layer upstream?

Should we close this given we're doing the retry layer upstream?

I'd

Should we close this given we're doing the retry layer upstream?

I have removed the retry layer implementation, I'd still like to include the LoggingLayer, to show what needs to be done to implemented your own custom layer.


custom dataset training

hey guys,
I wanted to train the hand model to detect nails positions.
is there any way to custom train the model with my own dataset?
@bazarevsky

Hi @arianatri, Please refer https://github.com/google/mediapipe/issues/2123#issuecomment-974152958 for more understanding on your query. Thanks!


Wrong id selector

Hello,
in the capture constructor, you call the following:
this.settings.canvas = document.getElementById(`#${this.settings.canvas}`) || window.canvas;

getElementById does not allow to select with leading "#" - this is querySelector syntax. This means it always uses the window.canvas fallback.
 I will fix it asap!

Fix by 27da75cc176fc667b07490b8944691b61259c566


[Bug][Server] zookeeper多级目录情况下, 任务无法分配worker执行

Describe the bug
zookeeper多级目录场景下任务无法分配worker
To Reproduce
Steps to reproduce the behavior, for example:

修改配置文件zookeeper.properties
zookeeper.dolphinscheduler.root=/path/to/dolphinscheduler
正常启动master, worker
新建工作流定义, 新建shell节点, echo "hello world"

Expected behavior
1.控制台正常显示已注册的master, worker
2.启动任务后, master报错: "fail to execute : xxx due to no suitable worker, current task need to yyy worker group execute"
Which version of Dolphin Scheduler:
-[1.3.1.release]
Additional context
1.ExecutorDispatcher#dispatch //hostManager.select 根据已经注册的worker, 通过group找到允许执行的worker
2.ZookeeperNodeManager$WorkerGroupNodeListener#dataChanged 监听worker变化
3.错误代码部分

`

    if (event.getType() == TreeCacheEvent.Type.NODE_ADDED) {
      logger.info("worker group node : {} added.", path);
      String group = parseGroup(path); //格式化获取group出错, 导致无法刷新syncWorkerGroupNodes
      Set<String> workerNodes = workerGroupNodes.getOrDefault(group, new HashSet<>());
      Set<String> previousNodes = new HashSet<>(workerNodes);
      Set<String> currentNodes = registryCenter.getWorkerGroupNodesDirectly(group);
      logger.info("currentNodes : {}", currentNodes);
      syncWorkerGroupNodes(group, currentNodes);
   }

`

`

private String parseGroup(String path){
String[] parts = path.split("\\/");
if(parts.length != 6){
  throw new IllegalArgumentException(String.format("worker group path : %s is not valid, ignore", path));
}
String group = parts[4]; // /dolphinscheduler/nodes/worker/default, 这段代码符合的路径
return group;

}
`

临时修改
String group = parts[parts.length-2];// 临时修改

5.问题原因: workerGroupNodes保存worker信息, workerGroupNodes通过dataChange刷新, parseGroup错误导致变量一直无法更新, 最终ExecutorDispatcher#dispatch无法获取worker, 任务无法继续

@xingchun-chen please check

could you submit a PR to solve this issue?

I will take it.

I will take it.

This is a bug, 1.3.2 immediately to release the version, do you have time to submit the code as soon as possible? If there is no time, we will fix this problem in 1.3.2. Thx
这算是一个bug，1.3.2着急要发版，你有时间尽快提交代码么，如果没有时间，我们将会在1.3.2上修复这个问题 . 如果有时间可以直接在1.3.2上提，谢谢

looking into it

I will take it.

This is a bug, 1.3.2 immediately to release the version, do you have time to submit the code as soon as possible? If there is no time, we will fix this problem in 1.3.2. Thx
这算是一个bug，1.3.2着急要发版，你有时间尽快提交代码么，如果没有时间，我们将会在1.3.2上修复这个问题 . 如果有时间可以直接在1.3.2上提，谢谢

send a pr, but e2e Test fail. could you help take a look?


ensure KongClusterPlugin configured as global plugins have the ingress.class annotation

KongClusterPlugin can be configured as global plugins using the label global: "true".
KongPlugin can do the same, but that behavior is set to be removed with https://github.com/Kong/kubernetes-ingress-controller/issues/681.
Change the store abstraction to only return global plugins if they have a matching ingress.class annotation on them.
This is required to avoid multiple Kong Ingress Controllers from picking global plugins. Users wish to configure different set of global plugins for internal and external ingress controllers.
For more details on background, please see doc in #690.

Handled in #767.


Expermimental mypy plugin

I was playing around a bit with a mypy plugin and this was the best I could come up with.
Unfortunately the mypy docu about the plugins is not very detailed...
This plugin makes mypy recognize the user defined accessors.
There is a quite severe bug in there (due to my lack of understanding of mypy internals probably) which makes it work only on the first run but when you change a line in your code and run mypy again it will crash... (you can delete the cache to make it work one more time again :)
Any chance that a mypy expert can figure this out? haha

(FYI I had been the mypy person here — for my sins — but I think this is beyond my understanding — so putting an issue into mypy might be the best path forward on the cache issue...)

(FYI I had been the mypy person here — for my sins — but I think this is beyond my understanding — so putting an issue into mypy might be the best path forward on the cache issue...)

Didn't want to steal your job, haha.
Yes, I think a mypy issue might be the best way forward.
I still have to construct a minimal example for this issue though ...


helm/hubble-ui: fixed ingress configuration on EKS clusters

On EKS clusters, the interpolated value of .Capabilities.KubeVersion.Version is assimilated as a prerelease per its semver syntax, eg: v1.18.8-eks-7c9bda. With this change, we are fixing the compute of the ingress.apiVersion template parameter when deploying over EKS clusters.
Fixes: #14018

Nominate for backport 1.9


Fixes for ConstraintViolation with micronaut-serde

fixes #176
fixes #178

This draft PR has two tests that expose the reported issues. The test-suite-serde-java subproject uses JUnit5 so instead of using @PendingFeature that would be applicable for Spock tests I use @Disabled. Unfortunately, JUnit5 doesn't have a comparable feature that I'm aware of.

I have split the tests.
I added identical tests to test-suite to verify the issue is not present with Jackson.
Moreover, I have added spec.name to avoid bean pollution between tests.


tutorials command emits json

Describe the bug
Tutorials command emits json.
Steps to reproduce the behavior

type tutorials

Expected behavior
A list of tutorials or tutorial commands to try.
Screenshots
If applicable, add screenshots to help explain your problem.

thanks for the bug report! hmm, i don't see this with the latest master, in either webpack or electron clients?

After updating to latest master 9b5ba11296df8a4fc86b8213ae58cb157339f67f, i get the expected output. Sorry I should have made sure I was up to date first.


k-9 v5.112 from f-droid -> no more dark theme

Expected behavior
after upgrade theme should stay dark
Actual behavior
after upgrade suddenly theme is light. even when going to settings and switching to dark and light again. theme stays light
Environment
K-9 Mail version: k-9 v5.112 from f-droid
Android version: 6

Fixed in 5.113