Change console-breadcrumbs.js - support  lower case and other dev env…

Without this change, we get console-breadcrumbs.js in the source (when I in DEVELOPMENT or 'test' environment)
Goal

Support lower case (for example 'DEVELOPMENT')
Support other dev environments (for example - 'stage', 'test'...)

Changeset
Check isDev with not production environment
Testing
manual with react native debugger
@imjoehaines @bengourley

Hi @idanlevi1
If you want to disable log breadcrumbs for console messages on other release stages this can be done by excluding log from enabledBreadcrumbTypes in your Bugsnag configuration, which gives you full control over the console breadcrumbs without this PR:
https://docs.bugsnag.com/platforms/javascript/configuration-options/#enabledbreadcrumbtypes
The reason for us disabling these by default in development environments is that wrapping console methods to leave breadcrumbs has the side effect of messing with line numbers in log messages which can make debugging trickier. In general console breadcrumbs are useful in other non-production environments so we wouldn't want to disable them for other release stage names e.g. staging, testflight etc.

Hi @idanlevi1
If you want to disable log breadcrumbs for console messages on other release stages this can be done by excluding log from enabledBreadcrumbTypes in your Bugsnag configuration, which gives you full control over the console breadcrumbs without this PR:
https://docs.bugsnag.com/platforms/javascript/configuration-options/#enabledbreadcrumbtypes
The reason for us disabling these by default in development environments is that wrapping console methods to leave breadcrumbs has the side effect of messing with line numbers in log messages which can make debugging trickier. In general console breadcrumbs are useful in other non-production environments so we wouldn't want to disable them for other release stage names e.g. staging, testflight etc.

I don't want to disabled console logs, I want to see the source of logs in the debugger, without my change (in other stages/environment except for development - 'testing' for example) i see like that:

@idanlevi1
Excluding log from enabledBreadcrumbTypes in your Bugsnag configuration doesn't disable console logs, it disables capturing those logs as breadcrumbs shown on errors in the Bugsnag dashboard.
In order to capture those breadcrumbs Bugsnag needs to wrap console methods which can interfere with the console log output.
Can you try setting enabledBreadcrumbTypes to exclude logs in your Bugsnag configuration for your test environment and confirm whether that solves the issue e.g.
Bugsnag.start({
  enabledBreadcrumbTypes: ['error', 'navigation', 'request', 'user']
})

Closing this as we have not had a response, but if the previous advice does not resolve the issue let us know and we can take another look.


Fix a bug where NPE is raised when retrying a gRPC request

Motivation:
When creating a derived context, we check whether the RpcRequest is null or not
if ctx.rpcRequest() is not null in the consturctor of DefaultClientRequestContext.
private DefaultClientRequestContext(...) {
    if (ctx.rpcRequest() != null) {
        assert rpcRequest != null;
    }
    ...
}

However, the assertion can be false.
The rpcRequest of the derived context is set later after the derived context is created so we don't know the timing.
Also, we call:
ctx.logBuilder().defer(RequestLogProperty.REQUEST_CONTENT,
                       RequestLogProperty.RESPONSE_CONTENT);

that guarantees the rpcRequest of the derived context is set later when the request content of the parent context is set.
So we can completely remove the assertion.
Modification:

Remove the assertion in DefaultClientRequestContext.

Result:

Close #3248
You will no longer see NPE when retrying a gRPC request.

Does it make sense to change ctx.rpcRequest by other threads while creating a new derived context?

rpcRequest can be set by other threads. 😄
https://github.com/line/armeria/blob/master/grpc/src/main/java/com/linecorp/armeria/internal/client/grpc/ArmeriaClientCall.java#L168

Does it make sense to change ctx.rpcRequest by other threads while creating a new derived context?

rpcRequest can be set by other threads. 😄
https://github.com/line/armeria/blob/master/grpc/src/main/java/com/linecorp/armeria/internal/client/grpc/ArmeriaClientCall.java#L168

I got it. 👍 newDerivedContext could be executed by a user thread for the first time. I missed that point.


Convert blob objects

hi guys i develop a new article app and use C# with firebase as a backend for database
i user th following code to convert the rtichtext.text to byte array
 byte[] result;
        using (MemoryStream ms = new MemoryStream())
        {
            txt_article.SaveDocument(ms, DevExpress.XtraRichEdit.DocumentFormat.Rtf);
            result = ms.ToArray();
        }

and saved successfully to fire base as blob now in flutter i want to retrieve the blob convert it to formatted text and then assign to any widget to show the text
note:- the text contain pictures , formatted texts like any news app
thanks

Questions like these are better suited for Q&A sites like StackOverflow or on one of the flutter community sites at https://flutter.dev/community


Cache kusto identity tokens for 1h

Pull Request Description
Cache kusto identity tokens for 1h

Future Release Comment
Fixes:

Ingestion does not call the cluster for identity token for each file/reader

@AsafMah , I manually tested this with a 10s expiration period to see that we go through > not cached => cached => expired => cached


Preserve string delimiter in type printing.

Related to #60540
This PR shows what the impact of preserving string delimiters in type printing would be.
cc: @jakebailey @weswigham

We looked at this in the design meeting; the general consensus is that this is good for declaration files, but the fact that error messages are changing quote styles seems to be wrong; we should try and make diagnostic type printing normalize to " quotes because that's what our messages assume happen.


Create useful aliases, add colorization and initialize most tools.

Try to maximize the power and potential of pwnbox.

Also this has been done in PwnBox v3.


KCP-CLI:  shoot-ID filter for reconciliations is ignored

Description
The kcp. reconciliations filter are not using a whitelisting approach when filtering for reconciliations. E.g. the shoot-name xyz123 does not exist:
 kcp reconciliations -c xyz123 | wc -l
 31941

Expected result
When setting a filter for reconciliations, only the reconciliations matchings the filter should be listed.
Actual result
Filter seems to be ignored and all reconciliations are returned. But a shoot-ID which doesn't exist should lead to an empty result.
Steps to reproduce
Run the command above and verify the output.
Troubleshooting

Fixed on main
➜  kcp rc -c foo
SCHEDULING ID   RUNTIME ID   CREATED AT   UPDATED   STATUES   LOCK

Fixed in latest KCP version - functionality verified today.


video: improve error logging in IGPUCommandBuffer

Description

Testing

TODO list:

@alichraghi how many examples did you test this with, also both RWDI and Debug ?

don't remember how many but pretty sure only ran in Debug mode

don't remember how many but pretty sure only ran in Debug mode

try a few in RWdi and Release

done. all good


[4pt]  -Display Comments pop up with selected item's details - Student B

Create a comments popup only with the top section (displaying details of the selected item)

When the popup loads, the webapp retrieves data from the selected API and shows details about the selected item.
Add event to button prepared by your teammate that will open your popup. You need to communicate with your team member to make sure that you do not block each other (most likely the easiest solution is to merge the list of items feature to the dev branch before you try to add that event).

The link to the PR:
https://github.com/MAleemH/JavaScript-Capstone-Project-/pull/23


VERSION: Bump to 0.2.8

Signed-off-by: Fernando Fernandez Mancera<EMAIL_ADDRESS>

Coverage remained the same at ?% when pulling 3754adb38118edd577ccf91e63bd0f7b0b5cfce3 on ffmancera:bump.0.2.8 into 17bb22b417df2fe2b81b490ae76d3345ecb13399 on nmstate:nmstate-0.2.


will provide service daemon way to start gotunnel?

kind of need service way to start it but not start at foreground.
Thanks

usually i start it as below:
nohup ./gotunnel --args.... &

yes, me too.

if you can debian service support for gotunnel, I will be happy to merge. :-)

if you can add debian service support for gotunnel, I will be happy to merge. :-)

#20

@rmrf thanks, i'll move your PR to a special folder.


Dispatcher not killed on runner.stop()

Prerequisites

[X] I am using the latest version of Locust
[X] I am reporting a bug, not asking a question

Description
Hello there.
I am building a custom wrapper on top of a locust. Most of the upstream locust functionality is being preserved, some stuff is being monkey-patched. Mentioning it even though it shouldn't have an impact on the issue I am about to describe.
I am trying to implement custom failure rate algorithm/monitor that STOPS test run prematurely, before --run-time is being expended, in case the failure rate goes beyond this threshold.
Standalone runner - no issues.
Distributed run has no issues if all users are already spawned before we reach threshold.
However, real issue is when I set lets say --users=300 and my custom event stops the runner when only subset of all the users is spawned. worker is being stopped and immediately sends message that its ready again. What master does though, is it spawns start() method in a greenlet, which spawns additional greenlets in a separate gevent group that is not being stored anywhere in the runner, therefore I cant see/kill it. On top of that, MasterWorker is NOT actually killing the user dispatcher in its stop() method, it merely sets the dispatcher to None
self._users_dispatcher = None
which means the gevent group hooks back to the worker and keeps spawning users.
Whats strange is that it looks like it spawns exactly 60 users before runner.quit() is called and both master/worker runners quit...
What I would like to do is simply stop both master AND worker runners, reset the user dispatcher/user variables in both runners and be able to restart the test from webUI.
Being forced to straight up quit the worker is a workaround that I would like to not take into account.
All help would be appreciated.
Command line
mylocust --host <IP_ADDRESS> --root . -L DEBUG -f locustfile.py --autostart --autoquit 1 --users 200 --spawn-rate 1 -t 40 --master;      mylocust --host <IP_ADDRESS> --root . -L DEBUG -f locustfile.py --autostart --autoquit 1 --users 200 --spawn-rate 1 -t 40 --worker
Locustfile contents
import warnings

from mylocust.events.failure_rate_monitor_fema import *
from locust import HttpUser, constant_pacing, events, tag, task

warnings.filterwarnings("ignore")

@tag("labs")
@task
def get_labs(self):
    self.client.get("/api/v0/labs")

@tag("labs")
@task
def delete_lab(self):
    self.client.delete("/api/v0/labs/9e232a38-ad8b-48a0-9f2e-cba37d661453")

class MyUser(HttpUser):
    wait_time = constant_pacing(1)
    weight = 30
    tasks = [delete_lab, get_labs]

    def on_start(self):
        self.client.verify = False
        response = self.client.post(
            "/api/v0/authenticate", json={"username": "user1", "password": "password123"}
        )
        token = response.text.strip('"')
        self.client.headers = {"Authorization": f"Bearer {token}"}

# part of the code from custom locust "init" event
def init_failure_rate_monitor(
...
        # end test run once we reach high-enough failure rate
        if fema.ema >= max_failure_rate:
            logger.info(
                "Failure rate passed the selected threshold of "
                f"'{max_failure_rate * 100}%'."
            )
            gevent.spawn(
                environment.my_runner.stop_and_optionally_quit, force=True
            ).link_exception(environment.my_runner._greenlet_exception_handler)
            break
...

@events.init.add_listener
def event_init_failure_rate_monitor(environment, max_failure_rate: float = 0.05, **__):
    # Master/Standalone only
    if not isinstance(environment.runner, WorkerRunner):
        gevent.spawn(
            init_failure_rate_monitor,
            environment,
            max_failure_rate=max_failure_rate
        )

Python version
3.12
Locust version
2.31.8
Operating system
Ubuntu 22.04.5 LTS

Hi Patrik!
Right now "stopping" workers is a bit weird - workers send a message to master saying they have stopped and then send a "client_ready" message which is, in the master's eyes, pretty much the same as a worker connecting. I think maybe if we started by cleaning that up a little, it would be easier to make this work.
[2024-10-14 15:44:04,656] lars-mbp/INFO/locust.runners: lars-mbp.local_495d30b64433446dbcd700c1ff6c6af1 (index 0) reported that it has stopped
[2024-10-14 15:44:04,656] lars-mbp/INFO/locust.runners: lars-mbp.local_495d30b64433446dbcd700c1ff6c6af1 (index 0) reported as ready. 1 workers connected.

In the meantime, I have realized that the "STOPPED" worker might actually mean different things and I probably automatically assumed one of them, but after scrolling through the code over and over again, I am not sure whether there's an actual consensus on what the STOPPED should mean.
In the case of this "bug", it kinda acts as if it means "PAUSED" with the aforementioned feature of auto-unpausing added right after.
Biggest issue I have is that when I hit STOP, I assume (expect) that everything truly stops, including dispatcher, and all data, like http users from a current run are purged. If we want to persist the current state and just temporarily halt it maybe adding another PAUSED state would be an option.

maybe this solution will solve your problem click

Hi Patrik!
Right now "stopping" workers is a bit weird - workers send a message to master saying they have stopped and then send a "client_ready" message which is, in the master's eyes, pretty much the same as a worker connecting. I think maybe if we started by cleaning that up a little, it would be easier to make this work.
[2024-10-14 15:44:04,656] lars-mbp/INFO/locust.runners: lars-mbp.local_495d30b64433446dbcd700c1ff6c6af1 (index 0) reported that it has stopped
[2024-10-14 15:44:04,656] lars-mbp/INFO/locust.runners: lars-mbp.local_495d30b64433446dbcd700c1ff6c6af1 (index 0) reported as ready. 1 workers connected.

Are we planning for this optimisation, if so please assign the task to me i would like to contribute

Nice! Assigned it to you!

Want to check whether the thought process is aligned
Currently once the master sends a stop message, each worker does the following steps in sequence

stop() -  which kills the greenlets in that worker
worker sends a client_stopped message to master. Based on this master is removing those clients from the client list and from the dispatcher
Sleep for short interval
Worker sends the client_ready message to the master. Now based on this master again adds back the clients to client list and adds back the worker nodes in dispatcher
Set the worker state to ready

Change : We can remove steps 2,3 and 4, so that now once the master sends the stop message the worker will kill the greenlets and will set its state as ready. Master will still retain all the client list and the worker nodes list in the dispatcher

I dont think we can remove all of that, because the master still needs to know when the workers completed their stopping procedure (shutting down all Users for example).
This issue was originally about the dispatcher not being stopped, perhaps that could be fixed by ensuring it is properly stopped (somehow) before throwing away the instance (setting it to None), but what I was talking about is more about changing the communication to make the communication more clear to the master (sending something like "stopping_finished" instead of "client_ready", if you understand what I mean).
Maybe this isnt a huge priority...

understood, thanks


Data set profiling

This PR adds basic benchmarking scripts. For now, we only have added timing benchmarks. In the future, we can add memory benchmarks.

Closing this in favour of #1050.


add parent ID migrator for notion nodes

Description

Risk

Deploy Plan

LGTM modulo making sure that nodeId = parents[0] post transform

Yep 👍


[FEATURE] Import Seasons from Calendar/Weather

The Calendar/Weather import worked pretty well, but it didn't import my Season data which I had already set up in Calendar/Weather.

The importer should better account for seasons in the latest release.


You may not be subscribed to the OpenID UserInfo endpoint error

Okay. I completely broke it. I tried creating a new endpoint for our production server and now it won't work at all. I've replaced code, cleared my cache, tried on different browsers. Nada.
Reproduce:

Also, in making a key pair value, if I try <IP_ADDRESS> I get this error

Okay. I didn't realize that I hadn't subscribed to the API


Coverage fails intermittently on CircleCI with exit code 255

Unhandled exception:
Tests failed with exit code 255
#0      runTestsAndCollect (package:test_coverage/src/functions.dart:120:5)
<asynchronous suspension>
#1      main (file:///root/.pub-cache/hosted/pub.dartlang.org/test_coverage-0.4.0/bin/test_coverage.dart:51:9)
#2      _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:305:32)
#3      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:174:12)

We're encountering this exception semi-frequently on our CircleCI builds. Example: https://app.circleci.com/jobs/github/mobxjs/mobx.dart/1944
If you check out our pipelines, many of the failures are the same. Any insight?
Thanks!

Thanks for reporting! Hard to tell from this output. Would be nice to add a --debug option to test_coverage which prints all output from test runner instead of swallowing it.

Hey! I ended up doing essentially that in https://github.com/shyndman/test-coverage
We've since discovered a pretty ordinary-looking test failure seems to be responsible in our case.
I'm closing this off, since the problem is resolved in our case, but yes — more output is better. If there was a --debug flag, I'd leave it on all the time.

Thanks for reporting! Hard to tell from this output. Would be nice to add a --debug option to test_coverage which prints all output from test runner instead of swallowing it.

Is the flag being considered for an upcoming version?

Agree that it would be better to print out everything.
So atm using
dev_dependencies:
  test_coverage:
    git: https://github.com/shyndman/test-coverage.git


K8SSAND-1371 ⁃ Training - cert

┆Issue is synchronized with this Jira Task by Unito
┆friendlyId: K8SSAND-1371
┆priority: Medium

Zenhub usage fail...  Moving to correct location.


MAL 403/503 errors

Steps to reproduce

Try to update the status of an entry on the MAL tracker
Log out and back in in the app and try updating again
Try updating again

Expected behavior
Tracker should update
Actual behavior
After 1, Error 403. After 2, Logs in fine, trying to update gives Error 503, after 3, error 403 again
Crash logs
No response
Aniyomi version
<IP_ADDRESS>
Android version
Android 14
Device
Google Pixel 8 Pro
Other details
Several other users have been having this problem (see support)
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an official extension, I should be opening an issue in the extensions repository.
[X] If this is an issue with an official manga extension and this issue can be replicated in the Tachiyomi app, that I should be opening an issue in Tachiyomi's extensions repository.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

Yup I've gotten the same error with a Samsung S21 Ultra

The MAL tracker that aniyomi uses has been deleted. Please wait until the next update to continue using the MAL tracker.

you can migrate to kuukiyomi or anilist if you cant wait

https://en.wikipedia.org/wiki/HTTP_403

just migrate to kuukil/anilist if you cant wait

DO I  NEED TO GOOGLE IT FOR YOU?????

AND I KINDLY SAID "The MAL tracker that aniyomi uses has been deleted. Please wait until the next update to continue using the MAL tracker."

WAIT FOR THE UPDATE OR MIGRATE

oh sorry i forgot thet it was fixed
my bad

ok sorry your issue was real im just dumb

i was translating on the background so i usually forgor ab it

Same here I can't log in again on MAL.

Same here I can't log in again now after log out

Hello, same problem here. Yesterday, I could log in MAL but the manga read wouldn't update (error 503). Today, the login doesn't work anymore. I'm using a Pixel 4a.
Thanks in advance for the fix.

I'm getting the same issue with my S22 Ultra

This error is on MAL. Source: https://myanimelist.net/forum/?topicid=2143705

AND I KINDLY SAID "The MAL tracker that aniyomi uses has been deleted. Please wait until the next update to continue using the MAL tracker."

Dude, come on, it was fixed in a previous issue about Mal, and it worked for couple days, and people tried to tel you that and you became rude...

So, umm, I logged out to see what happens, here's how I tried to login:

press the button

I allow access (as I'm already logged in on my browser)

It just returns me to this page

If it retry those steps, it will ask me for permissions again, I'd give them, and nothing except returning to the app will happen, again.

it takes a second to auth on the app side, this is probably unrelated
On Sat, Feb 3, 2024 at 11:03 AM sTiKyt @.***> wrote:

So, umm, I logged out to see what happens, here's how I tried to login:

press the button
Screenshot_20240203-185909_Aniyomi.png (view on web)
https://github.com/aniyomiorg/aniyomi/assets/35602029/872fbe4d-05e0-4488-80cd-ff330b57e42c
2.
I allow access (as I'm already logged in on my browser)
Screenshot_20240203-185932_XBrowser.png (view on web)
https://github.com/aniyomiorg/aniyomi/assets/35602029/a5241fa0-9937-429f-853a-1e520813025f
3.
It just returns me to this page
Screenshot_20240203-190021_Aniyomi.png (view on web)
https://github.com/aniyomiorg/aniyomi/assets/35602029/621f8e76-6ab3-4929-8ee3-10028540c03f
If it retry those steps, it will ask me for permissions again, I'd give
them, and nothing except returning to the app will happen, again.
—
Reply to this email directly, view it on GitHub
https://github.com/aniyomiorg/aniyomi/issues/1381#issuecomment-1925395826,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABM2DA5JH4J2BF5UAIMXXJLYRZUUNAVCNFSM6AAAAABCTS3YY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRVGM4TKOBSGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

But it does go to the app and then shows me this thing:

Then, nothing... Tried about 20 times

My bad, I think it related. Only happens with MAL and is reproducible. MAL may have made API changes.

Yep, only MAL

On my end, I still can't sign in FYI.

Possibly related: https://myanimelist.net/forum/?topicid=2143705 It is also possible MAL is intentionally blocking.

This error is on MAL. Source: https://myanimelist.net/forum/?topicid=2143705

Does anybody know when will this fix ( estimated time)

We'll know when MAL fixes the issue and ZeroCrystal tells us about it : https://myanimelist.net/forum/?goto=post&topicid=2143705&id=70550058

Still can't log in... :(

It wasn't working for me up until a few minutes ago so I read on MAL forums to change the uaeragent string so I looked up one in the internet, tried logging in again and voilà I was in with the green tick. This is the user agent I tried if anyone is curious:
Mozilla/5.0 (Linux; Android 13; SM-S901U) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Mobile Safari/537.36

It wasn't working for me up until a few minutes ago so I read on MAL forums to change the useragent string so I looked up one in the internet, tried logging in again and voilà I was in with the green tick. This is the user agent I tried if anyone is curious: Mozilla/5.0 (Linux; Android 13; SM-S901U) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Mobile Safari/537.36

But how do I add a useragent string in the android browser, I can't seem to find anything about it in Chrome and Firefox on android. Or do I change it over pc on my phone somehow?

It wasn't working for me up until a few minutes ago so I read on MAL forums to change the useragent string so I looked up one in the internet, tried logging in again and voilà I was in with the green tick. This is the user agent I tried if anyone is curious: Mozilla/5.0 (Linux; Android 13; SM-S901U) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Mobile Safari/537.36

But how do I add a useragent string in the android browser, I can't seem to find anything about it in Chrome and Firefox on android. Or do I change it over pc on my phone somehow?

See in app's Settings > Advanced

Thanks for the tip! Working well now :).

It wasn't working for me up until a few minutes ago so I read on MAL forums to change the useragent string so I looked up one in the internet, tried logging in again and voilà I was in with the green tick. This is the user agent I tried if anyone is curious: Mozilla/5.0 (Linux; Android 13; SM-S901U) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Mobile Safari/537.36

But how do I add a useragent string in the android browser, I can't seem to find anything about it in Chrome and Firefox on android. Or do I change it over pc on my phone somehow?

See in app's Settings > Advanced

Dang, finally some solution

It wasn't working for me up until a few minutes ago so I read on MAL forums to change the useragent string so I looked up one in the internet, tried logging in again and voilà I was in with the green tick. This is the user agent I tried if anyone is curious: Mozilla/5.0 (Linux; Android 13; SM-S901U) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Mobile Safari/537.36

Loggedin with this useragent, ty so much

I measured the UA of my android chrome browser on this site and it works fine
https://www.whatismybrowser.com/detect/what-is-my-user-agent/
MAL doesn't seem to like aniyomi's default UA

It wasn't working for me up until a few minutes ago so I read on MAL forums to change the useragent string so I looked up one in the internet, tried logging in again and voilà I was in with the green tick. This is the user agent I tried if anyone is curious: Mozilla/5.0 (Linux; Android 13; SM-S901U) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Mobile Safari/537.36

Also worked for me. Thank you so much! 👍🏻

I have the problem again since the 14.02.


Add analysis test for sample applications

There is a list with public application list [0], that should be used for analysis test (focusing on lsp analyzer). Add such aplication to analysis test and ensure lsp analyzer out is the same as windup output.
[0] https://docs.google.com/document/d/1UlDbcRoXcBkAsHQMHDtev6loveosu4j4lYBEkKeUcbM/edit

Applications will be added one by one when get confirmation on adding it and confirmed expected analysis result. Closing this issue and continue with first next step which is https://github.com/konveyor/go-konveyor-tests/issues/39


Add negative flow manifests to test scenarios

User story
As a core developer I want to be confident my changes haven't broken any expected behaviours in IF.
Rationale
We currently only have the ability to test positive flows through IF. After implementing logging to file, we can create negative test scenarios too, to check that IF error out in the expected ways when it is supposed to.
Implementation details

[ ] enumerate the ways that IF is supposed to error out
[ ] design test cases for each intended failure mode and write up as manifests
[ ] add documentation for the test cases in human readable format so we can quickly assess coverage

Priority
3/5
Size
L
What does "done" look like?
Negative test cases exist, behave in expected way, and are documented
Does this require updates to documentation or other materials??
Yes, test cases require documentation
Deadline
tbc

Hi @jmcook1186 I believe this ticket is now redundant, covered by #615 and #592. I have nothing to add to the acceptance criteria that isn't already covered in the above two tickets, suggest closing.


there are 2 different stylesheets

[safari-downloader] the user<EMAIL_ADDRESS>was successfully authorized...
[safari-downloader] downloaded meta files...
[safari-downloader] downloaded table of content files...
[safari-downloader] downloaded chapter files...
[safari-downloader] an error occurred while fetching stylesheets. there are 3 different stylesheets. only supporting one. the layout may be different from the one online. sorry for that.
[safari-downloader] downloaded stylesheet files...
[safari-downloader] epub successfully saved. exiting...

yeah i manage to replicate this one also.

@nicohaenggi Any idea when this will be resolved? Thanks


[Event Request]Application “Tests-Misc”, Codeunit 134348 "UT Page Actions & Controls - 2"

[Event Request]Application “Tests-Misc”, Codeunit 134348 "UT Page Actions & Controls - 2"
Could you please insert the OnTestInitialize Event at the beginning of each Test procedure:

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Iiif 281 update open api spec

Update the OpenAPI spec to match patterns described in IIIF-270
Updated tests to match the new endpoint URLs

Travis seems to be having some troubles reaching the Maven central repo so that reminded me to add a local Maven cache for the Travis build too. Added in new commit pushed to this branch.


Improve code style

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

Project coverage is 100.00%. Comparing base (077b834) to head (b1d7fc4).
Report is 10 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #301   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           71        71
  Lines         1487      1487
  Branches        54        54
=========================================
  Hits          1487      1487

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


The IR checker must not check field existence on classes without instances

The following snippet reports a spurious IR checking error:
class Outer(f: Int) {
  class Inner {
    def get(): Int = f
  }
}

object HelloWorld extends js.JSApp {
  def main() {
    println(classOf[Outer])
    test(null)
  }

  def test(outer: Outer): Unit = {
    if (outer == null) {
      println("null")
    } else {
      val inner = new outer.Inner
      println(inner.get())
    }
  }
}

The error is:
[error] HelloWorld.scala(13:22:Select): Class Lhelloworld_Outer does not have a field helloworld$Outer$$f$f

In fact Outer does have such a field, so how come the IR checker got confused?
The reason is that Outer is needed at all (because of the classOf[Outer]) but does not have any instances. It is therefore trimmed down by the BaseLinker to an empty class definition, which does not have any field. The IR checker then complains about the access to that field from Inner, which does have instances (at least as far as our reachability analysis is concerned) and hence whose get() method is reachable.
The fix is easy: the IR checker must simply ignore checking field existence in classes that have no instances.

Fixed in d8fc6f02f6d5e3e1e3d0572c80690fe96998b3fd.


case sensitive file extensions not particularly useful

I can't think of any situations where having case sensitive extensions in the es_systems.cfg is particularly useful, and it would certainly simplify configurations if it wasn't. Would avoid things like
z64 .Z64 .n64 .N64 .v64 .V64 .ZIP .zip
etc

well maybe i want to use .ZIP for disabled games and .zip for enabled
the windows version should not be case sensitive

well maybe i want to use .ZIP for disabled games and .zip for enabled
the windows version should not be case sensitive

it would be easier to move the roms out of the way I would have though. At least it would be nice to have an option for this. It would make our configurations simpler on RetroPie if we could.

it would be easier to move the roms out of the way I would have though. At least it would be nice to have an option for this. It would make our configurations simpler on RetroPie if we could.

@Aloshi, can we do this?


Linux electron doesn't quit after closing the window

Running the latest release, the music doesn't stop after closing the window.

Disable closeButtonMinimize


fix: escape html tags in order to solve html reporter rendering problems

issue
Escaped some special characters like '&', '<', '>', '`', '"', ''', '/'.  then html reporter rendering will not be infected by html tags

This change is

Thank you, will add the commit in next release


update lehrfempp to 0.7.15

I've followed this guide
step by step carefully. Yes

I've tested this package remotely and have excluded all broken builds.
Here is the links to the Travis/AppVeyor with status "All passed":

https://ci.appveyor.com/project/craffael/hunter/builds/23151637
https://travis-ci.org/craffael/hunter/builds/508550584

Testing:

https://ci.appveyor.com/project/ingenue/hunter/builds/23205136
https://travis-ci.org/ingenue/hunter/builds/508631586?utm_source=github_status&utm_medium=notification

Uploading:

https://ci.appveyor.com/project/ingenue/hunter/builds/23206048
https://travis-ci.org/ingenue/hunter/builds/508649387?utm_source=github_status&utm_medium=notification

Released: https://github.com/ruslo/hunter/releases/tag/v0.23.138


[BUG]

Release version
APIM version v4.1.2
Describe the bug
Hi -
We are using APIops for APi Extractor and Publisher.  we got following error from Stoplight Spectral. Kindly help us to resolve this error. Thaks in Advance
Expected behavior
Hi -
we got following error from Stoplight Spectral. kindly help to resolve this issue ASAP.

Actual behavior
We tried use different case for path
Reproduction Steps
Got the error when we publish the tool

We don't support third party libraries. You will have to do your own investigation on which file this linting tool is not happy about.


Don't crop dropdown task run button

Fixes #454

Remove anchoring of the JBBox harboring the toolbar to BorderLayout.WEST as it causing the user to resize the window to reveal it fully.

Screenshot

Before
After

Thanks! Looks better! Ideally, I think it would be good to see weight 1 behavior for task names like :feature:verifyAnd... ♻ (the 'run task' button should be wrap_content and the task name should have weight 1). However, this seems difficult to implement.


Replace podAntiAffinity addon by a topologySpreadConstraints addon?

What is missing?
I stumbled upon this new recommendation reading the karpenter.sh documentation^karpenter-concepts:

Note
Don’t use podAffinity and podAntiAffinity to schedule pods on the same or different nodes as other pods. Kubernetes SIG scalability recommends against these features and Karpenter doesn’t support them. Instead, the Karpenter project recommends topologySpreadConstraints to reduce blast radius and nodeSelectors and taints to implement colocation.

More in the official documentation about the motivations: https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/#comparison-with-podaffinity-podantiaffinity
It may not be worth to pursue improvements to the podAntiAffinity addon like #1090.
Thoughts?
Why do we need it?
Follow ever evolving Kubernetes best practices
Environment

kube-prometheus version:
Insert Git SHA here

Anything else we need to know?:
anti-affinity addon: https://github.com/prometheus-operator/kube-prometheus/blob/6d013d4e4f980ba99cfdafa9432819d484e2f829/jsonnet/kube-prometheus/addons/anti-affinity.libsonnet

Can you share more about sig scalability requirements about this? I cannot find anything much info related to use of affinity vs topologySpreadConstraints. The only thing I found is KEP for introducing the feature and info that affinity and  topologySpreadConstraints can work together.
From what I see topologySpreadConstraints matter more when you want to have multiple constraints using multiple failure domains (something not easily possible with affinity). However, in our case, we are using only one failure domain (node) which begs to ask what is the benefit of switching to a different solution?
Don't get me wrong, I like the idea of using topologySpreadConstraints, but I just want to know more ;)

I am at the same point as you on all that. Reading the KEP further, PodAntiAffinity seem to cause them issues and they are even thinking about deprecating it in the linked issue:

Currently PodAntiAffinity supports arbitrary topology domain, but sadly this causes a slow down in scheduling (see Rethink pod affinity/anti-affinity). We're evaluating solutions such as limit topology domain to node, or internally implement a fast/slow path handling that. If this KEP gets implemented, we can simply achieve the semantics of "PodAntiAffinity in zones" via a combination of "Even pods spreading in zones" plus "PodAntiAffinity in nodes" which could be an extra benefit of this KEP.

From this, it seems to be more about how it works internally, rather than the potential gain in flexibility for the users. My guess is, when the Karpenter documentation refers to the "Kubernetes SIG scalability" recommendation, it is not about the scalability of your deployment, but the scalability of your Kubernetes Scheduler

they are even thinking about deprecating it in the linked issue

I'm not sure I see anything concrete in that issue which states that there will be any deprecation to affinity or anti-affinity.
In fact I see various related enhancements landing in 1.22 https://github.com/kubernetes/enhancements/issues/2249
To be clear, I am not saying we shouldn't consider this or it is a bad idea. I just want to be sure we are not being motivated by the wrong source.

I got the Karpenter documentation clarified aws/karpenter#948
So in short, pod anti-affinities are a strain for the Kubernetes Scheduler at the moment
They does not seem to be a clear decision on whatever they will be deprecated or improved, but topologySpreadConstraints are here as an alternative
I have finally found the literal recommendation

Note: Inter-pod affinity and anti-affinity require substantial amount of processing which can slow down scheduling in large clusters significantly. We do not recommend using them in clusters larger than several hundred nodes.

https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity
Now the questions for kube-prometheus:

Are we concerned about the Kubernetes Scheduler performance?
Do we want a topologySpreadConstraints addon?
Do we want to remove  the podAntiAffinity addon if doing 2.?

Are we concerned about the Kubernetes Scheduler performance?

I would say yes. If we can improve our users' environments by using a better performing feature, we should use it.

Do we want a topologySpreadConstraints addon?

I vote yes.

Do we want to remove the podAntiAffinity addon if doing 2.?

No, I think this would break too many workflows. We can however put a trace notice in the podAntiAffinity addon to advertise the usage of the new topologySpreadConstraints addon. Additionally, we would need to create better documentation about topology spread and usage of podAntiAffinity as well as topologySpreadConstraints with an explanation on why not to use podAntiAffinity.
By trace notice I mean something like this: https://github.com/prometheus-operator/kube-prometheus/compare/main...paulfantom:trace-notice?expand=1

cc @simonpasquier @PhilipGough you might be interested in this as AFAIR CMO is using anti-affinity heavily.

I have no issues with us adding support for the addon while retaining support for inter pod affinity.
Yes CMO is using podAntiAffinity for both AlertManager and the platform Prometheus. I know we have deployed on very large cluster but am not aware of any issues with scheduling performance.
I'd be curious to learn if the impact would be more substantial for high-churn workloads, as opposed to relatively static platform infra. Or if adding podAntiAffinity, podAffinity to a workload affects overall scheduling performance across the cluster in general or is just limited to those workloads.

@paulfantom sounds good, thank you for pointing to std.trace(), I had been wondering how to output things like deprecation warning in Jsonnet for some time.
I am going to experiment with topologySpreadConstraints in my clusters, and I will try to contribute an addon later

This seems already implemented. https://prometheus-operator.dev/docs/operator/api/
Should this issue be closed?

Karpenter implemented enough Pod Anti-Affinity support to satisfy the prometheus use case. It was released in v0.9.0

@migueleliasweb I think that this feature request is still valid because the ask is to implement a jsonnet addon that uses topologySpreadConstraints and this doesn't exist yet (though the prometheus-operator CRDs support it).


Access Issues with Files in Bloxstrap

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[ ] My answer given in the checkbox above is a lie.

What problem did you encounter?
Dear Bloxstrap Support Team,
I am encountering an issue with Bloxstrap version 2.7.0. Upon starting the application, I receive error messages related to file access permissions, as follows:
lua
Copy code
2024-07-22T09:27:54Z [JsonManager::Load] Failed to load!
2024-07-22T09:27:54Z [JsonManager::Load] Access to the path '%UserProfile%\AppData\Local\Bloxstrap\Settings.json' is denied.
2024-07-22T09:27:54Z [JsonManager::Load] Failed to load!
2024-07-22T09:27:54Z [JsonManager::Load] Access to the path '%UserProfile%\AppData\Local\Bloxstrap\State.json' is denied.
2024-07-22T09:27:54Z [JsonManager<Dictionary2>::Load] Failed to load! 2024-07-22T09:27:54Z [JsonManager<Dictionary2>::Load] Access to the path '%UserProfile%\AppData\Local\Bloxstrap\Modifications\ClientSettings\ClientAppSettings.json' is denied.
2024-07-22T09:27:54Z [Logger::Initialize] Failed to initialize because Bloxstrap cannot write to %UserProfile%\AppData\Local\Bloxstrap\Logs
2024-07-22T09:28:00Z [App::GlobalExceptionHandler] System.UnauthorizedAccessException: Access to the path '%UserProfile%\AppData\Local\Bloxstrap\Bloxstrap.exe' is denied.
Here are some details about the issue:
Error: Unable to load configuration files and unable to write logs due to access denied.
Related Folder: %UserProfile%\AppData\Local\Bloxstrap
Application Version: Bloxstrap v2.7.0
Date and Time of Error: 2024-07-22T09:27:54Z
I have attempted the following steps but the issue persists:
Checked and verified folder permissions.
Temporarily disabled antivirus software.
Ran the application as an administrator.
Please advise on the next steps to resolve this issue or if additional information is required from my end.
Thank you for your assistance!
Best regards,

Here are 3 wikis
https://github.com/pizzaboxer/bloxstrap/wiki/"Access-to-the-path-is-denied"-when-trying-to-remove-a-custom-font
https://github.com/pizzaboxer/bloxstrap/wiki/"Access-to-the-path-is-denied"-error-when-trying-to-reinstall-Bloxstrap
https://github.com/pizzaboxer/bloxstrap/wiki/"Access-to-the-path-is-denied"-or-"An-error-occurred-trying-to-start-process"-regarding-RobloxPlayerBeta.exe


feat: allow .svg files to be inlined

Base64 is unnecessary for SVG files: https://github.com/vitejs/vite/issues/1197#issuecomment-738780169
Also using Buffer.byteLength instead of character length when comparing with the assetsInlineLimit option.
Closes #1204

todo: avoid inlining svg fragments

todo: avoid inlining svg fragments

Hi @aleclarson, do you need a hand with this PR?
I'd be interested to see it landed.

@princed Sure, you can fork it and open another PR 👍

@aleclarson @nhardy @Shinigami92
My updated version https://github.com/vitejs/vite/pull/2909


Which Android Studio / Gradle / Java versions requried?

I would like to fork this repo and make some changes but I'm having issues while trying to use the local version with the Flutter package.
I was wondering if you could provide compatible versions of the above for me to try? I think I need to sync to project before using in the Flutter package but running into tons of errors and can't figure out what I need to do in order to get it to work...

@carman247 did you get the solution of it?


Feature/refresh tokens

PR Checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[x] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: #14
What is the new behavior?
There is now a route to refresh jwts and we are now sending back access tokens and refresh tokens when logging in and registering a user.
Does this PR introduce a breaking change?
[x] Yes
[ ] No

When logging in, a user will receive the following object
{
  "access_token": "...",
  "refresh_token": "...",
  "expires_in": "number",
  "token_type: "Bearer"
}

Other information

Coverage increased (+1.6%) to 83.176% when pulling cf08781ed21d15406f3c9661daddb082796fca9e on feature/refresh-tokens into 70153c9152e05885ff9148b9417113cb037d816c on master.

Coverage increased (+1.6%) to 83.176% when pulling 32865fa0fe98044b14c629ef884fcf44ea0fb4c2 on feature/refresh-tokens into 70153c9152e05885ff9148b9417113cb037d816c on master.

Coverage decreased (-15.8%) to 65.765% when pulling fd5110df50c39b60eb44f42508bc9231c4b2a3b3 on feature/refresh-tokens into 70153c9152e05885ff9148b9417113cb037d816c on master.

Approved


Search action - misleading succeeded value

I faced with the case where after performing search, succeeded returned true, but one shard failed. Don't you think that we should add additional checks for this situation?
Steps to reproduce:
1.Create index
POST: /test_index
{
    "mappings": {
        "test_type": {
            "properties": {
                "test_field": {
                    "index": "analyzed",
                    "type": "string"
                }
            }
        }
    }
}

2.Create document
POST: /test_index/test_type
{
    "test_field": "test"
}

3.Perform search
POST: /test_index/_search
{
    "highlight": {
        "fields": {
            "test_field": {}
        },
        "type": "fvh"
    },
    "query": {
        "match_all": {}
    }
}

Response:
{
    "took": 2,
    "timed_out": false,
    "_shards": {
        "total": 5,
        "successful": 4,
        "failed": 1,
        "failures": [
            {
                "index": "test_index",
                "shard": 3,
                "status": 400,
                "reason": "ElasticsearchIllegalArgumentException[the field [test_field] should be indexed with term vector with position offsets to be used with fast vector highlighter]"
            }
        ]
    },
    "hits": {
        "total": 1,
        "max_score": 1,
        "hits": []
    }
}

Status: 200, Succeeded: true - shouldn't it be false??

Status: 200

ES considers it success so why can't we? :)
This is a tough one because setting succeeded false means to have a success logic with assumptions, in your case that is "all shards must be ok for success". Maybe some users are ok with missing a few shards. Also what about timed_out, maybe some users consider that failure... This is why succeeded always just checked if return code is 2XX till recently (where we added some logic for Bulk). Going with this trend we'll need similar logic for all other actions too which means more assumptions and ultimately having a different success behaviour than ES.
Instead of that it might be nicer to have hasErrors and maybe getErrors kind of methods. Thus making sure the user is aware even if ES says an operation succeeded it can still have errors.

Having all those methods is a good option. Users who want to relay on es can use succeeded. If they need something more complex, they can create facade to JestClient that will change succeeded based on custom logic that can implemented in terms of  hasErrors and getErrors.


notify_slack should determine dag_id on its own

Description

Since common.slack.notify_slack is an Airflow TaskFlow API @task, it has access to the context variables: https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/taskflow.html#context
Thus, we should be able to have it determine the dag_id on its own (via the dag.dag_id property of the dag object available for templating).
This function will need to be changed to remove the dag_id required parameter from the outer function call, add dag: DAG | None = None at the end of the argument list, and then pass dag.dag_id into the send_message call:
https://github.com/WordPress/openverse/blob/7f5baa29f1c5f0e09266946bd2c1a2f321d6f07a/catalog/dags/common/slack.py#L421-L433

Hi, I'm new to contributing to public OpenSource projects and would like to take this up if available.

Hi @triii10 , thank you for your interest in contributing to Openverse! I've assigned this issue to you. If you have any questions, you may leave them here.
Please check out our welcome and general setup documentation pages for getting started with setting up your local environment.

I this issue still open. I'm interested to solve this issue

@rajatsingh23 a PR #5136 has already been opened to fix this issue. I would suggest picking one of the other open issues to work on. For example, you can look at the list of good first issues for an introduction to the code base or the list of help-wanted issues if you feel a bit more comfortable and would like something challenging.


Please rename v7 cli back to cf7.

cf7 should never have been renamed cf. they have incompatible interfaces, they should have two different command names.

Hey @ukabu - We're not going to change the v7 CLI back to cf7. It's a major release of the same product with the same goals and covered use cases plus enhancements. When released, cf6 broke the contract with the previous major release of the CLI cf5, and there are many other applications that release new versions including breaking changes to the interface and maintain a consistent naming convention.
That said, I'd be interested in hearing more specifically what problem you've experienced because we changed cf7 to cf.
Thanks,
Josh

I'm going to go ahead and close this issue out @ukabu, but I remain interested in learning more about his specific problems if you're willing to share them.
Thanks!
Josh

We have a large userbase that uses PCF. We also follow closely the platform releases, but have several environment that cannot be all updated at the same time.
We also have pipelines that have some tasks that uses the cf cli.
So we need two version of the cli to co-exist nicely. v7 does not work yet on our version (beta was ok). For pipeline we could have two version of our images, but then again, it would be nice to have the two cli version in the same image.
Our linux environment and images are debian based, today. we cannot have the cli v6 & v7 debian package coexist. It they were using alternatives, we could chose which one the cf command links too, but that is not the case.
And then there is the memory muscle thing. A different command name, even if it's just a 7 at the end, helps the brain adjust to the new subcommands more easily.
Having the same command for two completely different command line interface is akin, imo, to having a brand new API at the same endpoint as the previous one. We (you) don't do this for APIs, why would that be different for cli?
Doing it for historical reasons is not a very compelling argument ;-)

Hi,
@heyjcollins you say : We're not going to change the v7 CLI back to cf7
but how come I still see cf7.exe in both installers and binaries ???

Feedback provided in https://github.com/cloudfoundry/cli/issues/2001 is that the current switching mechanism does not easily allow users to work with an heterogeneous set of CF instances: some CF instance supporting the v3 API requirements, and some not, hence becoming unuseable with cf v7

I see the binaries for linux still include cf7 and a cf symlink.
Here is the workaround script I have to ease switching without requiring access to apt-get and redowloading the package

#switch cli version by simlinking /usr/bin/cf to /usr/bin/cf6 or /usr/bin/cf7
#$1 6 or 7
function switch-cli() {
  local cli_version=$1
  if [[ -L /usr/bin/cf ]];
  then
    sudo ln -nsf /usr/bin/cf${cli_version} /usr/bin/cf
    echo "which cf:"
    which cf | xargs ls -al
  else
    echo "cf is not a simlink, check your install"
    ls -al /usr/bin/cf
  fi
  cf -v
}

alias switch-cf6='switch-cli 6'
alias switch-cf7='switch-cli 7'

UX:
$ switch-cf6
which cf:
lrwxrwxrwx 1 root root 12 sept. 11 18:51 /usr/bin/cf -> /usr/bin/cf6
cf version 6.51.0+2acd15650.2020-04-07

$ switch-cf7
which cf:
lrwxrwxrwx 1 root root 12 sept. 11 18:51 /usr/bin/cf -> /usr/bin/cf7
cf version 7.1.0+4c3168f9a.2020-09-09

Hope this can help others.


KAFKA-12365; Disable transactional APIs on KIP-500 broker

Since we do not yet support producerId generation with the KIP-500 broker, this patch disables support of the transactional APIs. By removing the "broker" listener from the schema definitions, these APIs will not be advertised in ApiVersions and any requests will be rejected by the SocketServer.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Note I'm doing a pass over the other APIs that should be disabled for now. For example, the reassignment APIs are not yet supported. I will probably just generalize this patch to cover all of them.

The approach LGTM to me.  Can you also disable the relevant system test(s) in this PR?
Agree that we need to disable a few more things -- reassignment is one


Keda Admission Webhook rejects ScaledObject requests that use Range Limit

Report
Keda Admission Webhook fails ScaledObject requests with memory/CPU triggers that don't have memory/CPU request defined although Range Limit is defined in the namespace.
This bug report is similar to #4802 , but if Range Limit is defined with defaults limit and requests for CPU and memory, then Admission Webhook should not reject workload that define only limit, or only requests, or a combination of both.
Expected Behavior
Based on Kubernetes documentation for default memory and CPU, ScaledObject with memory and/or CPU triggers of a deployment with no requests or limits on the relevant scaler, should not be rejected by Keda Admission Webhook if a Range Limit is define with default limit and requests (of the relevant memory/CPU metric)
Actual Behavior
Keda Admission Webhook rejects ScaledObject request with:
admission webhook ... denied the request: the scaledobject has a memory trigger but the container ... doesn't have the memory request defined
Steps to Reproduce the Problem

Create a Range Limit with default limit and request of memory and CPU.
Create a Deployment with no resource requests or limit (e.g CPU)
Create a ScaledObject with CPU scaler that points to the Deployment.
Get an error message on apply.

Logs from KEDA operator
No response
KEDA Version
2.12.1
Kubernetes Version
1.26
Platform
Amazon Web Services
Scaler Details
Memory, CPU
Anything else?
No response

Yeah, makes sense totally. The admission webhook should check if there is any default value set by Range Limit.
Are you willing to include the validation?

Unfortunately I don't have experience in Go :sweat_smile:

@JorTurFer i would like to work on this issue

Nice!
Let me assign it to you :heart:

@Bhargav-InfraCloud I think you can proceed with this, we plan to do a new release later this week, we can include this if you are able to tackle it soon :)

Sure @zroubalik. Thanks! Working on it.

Hi team,
Please review the following PRs. Thanks!

https://github.com/kedacore/keda/pull/5377
https://github.com/kedacore/charts/pull/588


Check data type before running morphological operation

To output a clearer message to the user.
See: http://forum.spinalcordmri.org/t/problem-with-latest-version-installation/311/25?u=jcohenadad

I've just realized that we are actually using grey_erosion, which does accept non-binary data.

@jcohenadad, I see you've corrected the "typeError" in convert_list_str(). I've only added a correction to the help instruction (greyscale or binary image). Should I do a pull request for such a little modification.

@jcohenadad, I see you've corrected the "typeError" in convert_list_str().

it would be helpful if you could add a bit of context: when did i correct it? pls add a hyperlink to the modification you are referring to
I've only added a correction to the help instruction (greyscale or binary image). Should I do a pull request for such a little modification.
every modification to master requires a PR. That being said, there is currently a PR dealing with sct_maths #2616 so you might want to simply push on the working branch


 Set param:
    args.show = False
    args.device = "cuda:4"
    args.det_config = 'path/to/object_detector_config'
    args.det_checkpoint = 'path/to/object_detector_checkpoint'
    args.pose_config = 'mmpose/configs/wholebody_2d_keypoint/rtmpose/ubody/rtmpose-l_8xb32-270e_coco-ubody-wholebody-384x288.py'
    args.pose_checkpoint = 'path/to/model/dw-ll_ucoco_384.pth'

    args.input = 'video.mp4'
    args.output_root = 'result'

Run the script, result video was build in args.output_root


V9 support

Hi Callum,
Will you be releasing a V9 version of this package ? Or is it not possible with the underlying dependencies like Bobo browse?
Dave

I will get to you on helping out. Will probably need similar functionality too.

I was looking at this as well.
A few things I noticed is that LuceneSearchResultsBase has been removed from Examine, so I have this instead.
public abstract class FacetSearchResults : LuceneSearchResults, IFacetResults
{
    public FacetSearchResults(ISearchContext searchContext)
        :base(Array.Empty<ISearchResult>(), 0)
    {
        Facets = new Dictionary<string, IFacetResult>();

        if (searchContext.GetSearcher() is not IndexSearcher indexSearcher)
        {
            throw new Exception("Searcher is invalid");
        }

        Searcher = indexSearcher;
    }

    ///<inheritdoc/>
    public IDictionary<string, IFacetResult> Facets { get; }

    /// <summary>
    /// Exposes the internal <see cref="IndexSearcher"/>
    /// </summary>
    public IndexSearcher Searcher { get; }
}

however when requesting results.GetFacets() in the following code, I got this:

if (!_examineManager.TryGetIndex(Umbraco.Cms.Core.Constants.UmbracoIndexes.ExternalIndexName, out IIndex index))
{
    throw new InvalidOperationException($"No index found by name {Umbraco.Cms.Core.Constants.UmbracoIndexes.ExternalIndexName}");
}

if (index is not LuceneIndex luceneIndex)
{
    throw new InvalidOperationException($"Index {Umbraco.Cms.Core.Constants.UmbracoIndexes.ExternalIndexName} is not a LuceneIndex");
}

var writer = luceneIndex.IndexWriter.IndexWriter;

var manager = new SearcherManager(writer, true, new SearcherFactory());

var multiSearcher = new MultiFacetSearcher(
    "FacetSearcher",
    manager,
    luceneIndex.DefaultAnalyzer,
    luceneIndex.FieldValueTypeCollection
);

var query = multiSearcher.CreateQuery()
    .NodeTypeAlias(Course.ModelTypeAlias);

query.And()
    .Facet("Duration")
    .MinHits(10)
    .MaxCount(100);

var results = query.Execute(new QueryOptions(0, 100));

var data = new
{
    Facets = results.GetFacets(),
    Results = results
};

Furthermore signature of Execute method has changed to:
ISearchResults Execute(QueryOptions options = null)

I was looking at this as well. A few things I noticed is that LuceneSearchResultsBase has been removed from Examine, so I have this instead.
public abstract class FacetSearchResults : LuceneSearchResults, IFacetResults
{
    public FacetSearchResults(ISearchContext searchContext)
        :base(Array.Empty<ISearchResult>(), 0)
    {
        Facets = new Dictionary<string, IFacetResult>();

        if (searchContext.GetSearcher() is not IndexSearcher indexSearcher)
        {
            throw new Exception("Searcher is invalid");
        }

        Searcher = indexSearcher;
    }

    ///<inheritdoc/>
    public IDictionary<string, IFacetResult> Facets { get; }

    /// <summary>
    /// Exposes the internal <see cref="IndexSearcher"/>
    /// </summary>
    public IndexSearcher Searcher { get; }
}

however when requesting results.GetFacets() in the following code, I got this:

if (!_examineManager.TryGetIndex(Umbraco.Cms.Core.Constants.UmbracoIndexes.ExternalIndexName, out IIndex index))
{
    throw new InvalidOperationException($"No index found by name {Umbraco.Cms.Core.Constants.UmbracoIndexes.ExternalIndexName}");
}

if (index is not LuceneIndex luceneIndex)
{
    throw new InvalidOperationException($"Index {Umbraco.Cms.Core.Constants.UmbracoIndexes.ExternalIndexName} is not a LuceneIndex");
}

var writer = luceneIndex.IndexWriter.IndexWriter;

var manager = new SearcherManager(writer, true, new SearcherFactory());

var multiSearcher = new MultiFacetSearcher(
    "FacetSearcher",
    manager,
    luceneIndex.DefaultAnalyzer,
    luceneIndex.FieldValueTypeCollection
);

var query = multiSearcher.CreateQuery()
    .NodeTypeAlias(Course.ModelTypeAlias);

query.And()
    .Facet("Duration")
    .MinHits(10)
    .MaxCount(100);

var results = query.Execute(new QueryOptions(0, 100));

var data = new
{
    Facets = results.GetFacets(),
    Results = results
};

Furthermore signature of Execute method has changed to:
ISearchResults Execute(QueryOptions options = null)

Did you have a working example? Im also looking into this

@JohanReitsma83 no, unfortunately not. I was looking into it, but found too much of the underlying API had changed in Examine v3.
However there a Examine v4 in beta, so I will recommend to try it out, which includes support for facets:
https://github.com/Shazwazza/Examine/releases/tag/v4.0.0-beta.1
I have submitted a draft PR for Umbraco Commerce demostore to try out facets on ExternalIndex.
https://github.com/umbraco/Umbraco.Commerce.DemoStore/pull/3

Hey everyone!
I am going to archiving the Examine Facets project now.
The native implementation in Examine v4+ is fantastic, and the team have done great work in documenting it all here: https://shazwazza.github.io/Examine/ This is my recommended solution going forward!
Thanks for all of your contributions!
Callum


scylladb test add withOption for ALLOW FILTER true

@rajthilakmca  Do we need this pull-request ?  Why is this pullrequest still open ?
If not please close it ?


How long it takes to train GCNN-13 (Dataset: Google Billion Word) on single Tesla M40 GPU?

The paper "Language Modeling with Gated Convolutional Networks" says the majority of models are trained on single GPU, I wonder how long it takes to train GCNN-13 (Dataset: Google Billion Word) on single Tesla M40 GPU?

For the largest GCNN on GBW, we trained on 8 Tesla M40 GPU. For all of the other models, we trained on one. On 8 Tesla M40 GPU, it took a couple weeks to train fully. The PyTorch code we've open sourced here is faster and more efficient though.


support count in word movement commands

word_forward, word_backward, word_end_forward
In other words, now you can do 3w, 5b, and 4e in vi mode, for example.

Thanks for this!
I'm not sure what the plan is right now. There's a refactor branch that seems to touch a lot of editing related code, so I think @dzhou121 would want to hold off merging this PR until work on that branch completes?

I didn't know that. I don't mind waiting.

@dzhou121, @bugadani, is this PR still being considered?

Is there a way to add tests to this? Something like this one? (where did my cute test framework go? 😢 ) https://github.com/lapce/lapce/blob/f0f3dab62ceb4eaf4eca19ac2976227d46f9395a/lapce-core/src/buffer.rs#L1099

Thanks for the changes! I like the general direction (and I especially like how you placed the character offsets under the strings, that's very helpful!), but I still have a few readability concerns.

All good points. Fixed as much as I can.


Travis tests are not running

Check with Travis and ensure following:

Smoketests should run
UI tests should run
Lint checks if any should run

... and that the build MUST fail if any of the above fail.
For example, right now smoketests aren't running - https://app.travis-ci.com/github/apache/cloudstack/builds/247736668
Pl check and fix this for both 4.16 and 4.17/main as applicable.
ISSUE TYPE

Bug Report

COMPONENT NAME

CI/CD

Hi @rohityadavcloud I see tests running now, a lot of them are still queued

No @nvazquez cc @weizhouapache @Pearl1594 @davidjumani pl look at individual jobs, for example - https://app.travis-ci.com/github/apache/cloudstack/builds/247795805
They're all running in under 20mins but they are not really running Marvin smoketests, from one of those "passing" jobs we see:
nosetests: error: no such option: --with-marvin
real	0m0.173s
user	0m0.126s
sys	0m0.020s

Closing it since its been fixed on #6113


Create Worksheet

I see that it is possible to create a sheet/book but I am hoping that it doesn't mean that I need to use the many conversions needed with c: and r: but instead use something like an opposite of the xls.utils.sheet_to_json.
Could someone please help me with the easist way there is to create a book (no formatting required)?

hi @fonzy2013  do you already have a solution for this?

The inverse of the XLSX.utils.sheet_to_json function where header:1 is set (so we are dealing with arrays-of-arrays) is in the test suite:
https://github.com/SheetJS/js-xlsx/blob/master/test.js#L1044-L1069
https://github.com/SheetJS/js-xlsx/blob/master/tests/write.js#L46-L70
We will be adding a function like this, named XLSX.utils.aoa_to_sheet,  for the 0.9.5 release


TTL on map entries.

AsyncMap comes with contract to have ttl on entry - this has to be addressed.

the issue is addressed in https://github.com/romalev/vertx-consul-cluster-manager/pull/26


Documentation not clear

Description of the problem
I am trying to use it for client's ecommerce but if I try to use only hover , then i always get "failed to execute removeChild" error.  Always get this error just because I don't want to use other options but only hover? Why havenot you provided documentation for single option usage among hover, click, cursor, etc ??? Send me screenshot or stackblitz link where you have created only zoom on hover.

I want to make sure my customers don't have to click buttons everytime they try to zoom image using hover. Make it simple like react-image-zoom package or tell me how i can achieve zoom on hover by default using this package and need not to show other options on my page.

Dear @ChetSocio,
I am so sorry for the inconvenience. I never intended to force library users to click a button before activating the feature. You probably used the version of Reacrt 18 or so which caused the useEffect hook to run twice during development mode. I just included the fix in #205. It should fix the issue now, please update your dependency to the latest. Here is the demo on Stackblitz - https://stackblitz.com/edit/willnguyen1312-zoom-image-vxbn53?file=package.json
Please let me know how it goes on your end and whether you need extra support from me
Thanks so much :)
Best,
Nam

Hello Sir , thanks for your reply but i am using nextjs 13.5.1 with app router and even after copying your code exactly i am getting :
Unhandled Runtime Error
NotFoundError: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.

Here'ss my screenshot of code:

I think it's the problem with the package manager caching mechanism. You can try to clear it and install the latest one from npm. Thanks 🙂


Building a Spreadsheet - step 17: setting hyphenated attribute values as properties

Describe the Issue
I haven't looked at much of the new curriculum but I assume the fact that you need to convert the hyphenated aria attribute value to camel case for the property has been explained at some point?
Should using setAttribute not also be a valid way of setting attributes?
Do we teach setAttribute anywhere?
Affected Page
https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures-v8/learn-functional-programming-by-building-a-spreadsheet/step-17
Your code

Expected behavior

Explain how to set the aria attribute as a property if it has not been explained.
Allow the use of  setAttribute for setting attributes.
Teach the setAttribute method somewhere if it has not been taught.

Screenshots
No response
System

Device: [e.g. iPhone 6, Laptop]
OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04]
Browser: [e.g. Chrome, Safari]
Version: [e.g. 22]

Additional context
No response

Should using setAttribute not also be a valid way of setting attributes?
Do we teach setAttribute anywhere?

setAttribute and removeAttribute were first introduced in the music player project
https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures-v8/learn-basic-string-and-array-methods-by-building-a-music-player/step-50
We also have campers use el.ariaLabel in the Todo app
But we are currently removing most of the aria labels based on this conversation here
https://github.com/freeCodeCamp/freeCodeCamp/issues/52981
So it looks like this step will need to update the tests to accept both valid forms of setting the attribute
 input.ariaLabel = letter + number;

input.setAttribute('aria-label', letter + number);

I would prefer if the explanation was more explicit about all hyphenated attribute values being camel case as properties. You might be able it infer it but I would prefer if it was stated explicitly.

All hyphenated HTML attribute values, like aria-label are camel case as properties ariaLabel.

Or something like that. It might be worded better.
music player step 75
https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures-v8/learn-basic-string-and-array-methods-by-building-a-music-player/step-75

It might be easier to create a new step 18 to properly teach the el.attribute syntax to let them know there is another way to update an attribute since campers will only be familiar with setAttribute at this point.
We could do something like this
--description--
In earlier projects you learned about the setAttribute method. Another way to update an attribute in JavaScript is to use the following syntax:
el.attribute = value;

The property names for hyphenated HTML attribute values, such as aria-label, follow camel case, becoming ariaLabel.
el.ariaLabel = "Aria Label Value";

Set the aria-label attribute for the input element to the same value as the id attribute.

I've observed that using template literals to assign values is not allowed. While it may not be essential in this specific case, I believe there should be flexibility to use template literals when setting attribute values.
What are your thoughts on this?

Hi @aaqib605 !
Based on what I have see on the forum so far, I would imagine most people probably wouldn't use template literals here but we could just update the tests to allow for that option.

I am going to go ahead and open this back up for contribution
Note to contributors
This has been opened for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors.
If you would like to contribute and have not read the contributors docs, please do so here: https://contribute.freecodecamp.org/#/
If you have any issues with contributing, be sure to join us on the contributors channel, or on the contributors sub-forum
What should be changed
We are going to move forward with the changes discussed here
https://github.com/freeCodeCamp/freeCodeCamp/issues/52987#issuecomment-1879926549
This means adding a new step 18 to properly teach this syntax.
Please read through the docs here on how to insert a new step
https://github.com/freeCodeCamp/freeCodeCamp/issues/52987#issuecomment-1879926549

We are going to move forward with the changes discussed here

Sounds great.


X and Y props passed to labelComponent are off when using LineChart

Bugs and Questions
Checklist

[ ] This is a victory-native specific issue. (Issues that also appear in victory should be opened here)

[x] I have read through the FAQ and Guides before asking a question

[x] I am using the latest version of victory-native

[x] I have checked to make sure that my versions of react-native and react-native-svg are compatible with this version of victory-native. Read about version requirements

[x] I've searched open issues to make sure I'm not opening a duplicate issue

The Problem
What I'm trying to achieve is render a 'fancy' custom label that points to the last point of a line chart, like this:

The problem is, with smaller data sets, the x and y are not actually the x and y of the last point, and the label is quite off. Is there a way to get the x and y of the actual last drawn point of the lineGraph?
This is when I draw a circle using the passed x and y prop:

I quickly checked the source code of the tooltip component (as this is kinda what I want to achieve), but I don't see any crazy calculations happening with the x and the y..
Reproduction
Hard one to reproduce, this is more question to check if what I'm doing is correct.

Update, tried using the standard VictoryTooltip, to no avail..

@svenlombaert check out this issue on the main victory repo: https://github.com/FormidableLabs/victory/issues/702
I'm going to close this issue as not specific to victory-native


Support for contentFiles in nuspec packages

Does nuproj support contentFiles?
If so, awesome!  If not, could this be added?  Ideally we would be able to add a "special folder" called "Content Files", and then under that add a cs/vb/any folder, and then under that add a targetFramework folder and then finally add new/existing files to it. Then on each element set a few key properties like BuildAction, Copy To Output, and Flatten (although the last one only makes sense if we can add wildcard specs for the file name)

Sounds cool.

I've started working on this some time ago for #191 here: https://github.com/kovalikp/nuproj/tree/feat/contentv2. I should probably finish it some day.

Resolved by #254


Towards #56 - Update end-to-end-gentle.md

Towards #56 .
Changes proposed in this PR:

Gentle introduction example is homogenized with main2
Added the file that will be submitted to the judges
Added "setup" and "what the judges will do"

Fixes #56 .

Please change PR description and title to have "Towards #56"
More comments to follow...

My feedback for PR#59 also applies to this PR.
I'll summarize:

Key thing: test data needs to be from 24h, 23h, .., 12h in the past. And your model can only learn from data older than that. The README needs to get fixed accordingly.
it should be obvious to readers to see how this README expands upon the steps in main2.md. Therefore, this README's section numbers should correspond to section numbers in main2.md.

I took care of your comments, in particular:

test data needs to be from 24h -- done
readme sections correspond with main2 -- done
rewrote section 3.2 and now computes nmse with the 12 next subsequent values as per main2 -> 3.3
removed ancillary information from the example, such as select data per specific hour
rewrote text significantly (mostly at the end) to accomodate these changes

thanks,

Hi Trent, I rewrote the example as instructed. Let me know .Thanks


Scene background and ambient light values are ignored by Ogre2

Environment

OS Version: Ubuntu 18.04
Source or binary build? source, sdf9 branch

Description

Expected behavior: The background and ambient light values in <scene> should be used by Ogre2 to light the scene
Actual behavior: The values in <scene> are ignored. Instead, Ogre2 uses <background_color> and <ambient_light> values inside <plugin filename="GzScene3D" >. On the contrary, Ogre seems to only use the values in <scene>

Steps to reproduce

test_scene.sdf.txt

Run the attached SDFormat file
Change <engine> to either ogre or ogre2
Update values in <background> and <ambient> in <scene> if engine is Ogre2 and notice no changes

Update values in <background_color> and <ambient_light> in <plugin filename="GzScene3D" > if engine is Ogre and notice no changes.

Output
Ogre2:

Ogre:

I know at least for background color, we are using the param in GzScene3D to set the background color for the GUI and the one in <scene> for sensors so that they can have different background colors.

We need to document this better, but as @iche033 mentioned, the goal is that the parameters within the plugin override the <scene> tag.
However, the current code is setting first the color from the plugin and then overriding that with the one from <scene> here:
https://github.com/ignitionrobotics/ign-gazebo/blob/d7741f6c3ec307e465275033434ceea286546aa7/src/rendering/RenderUtil.cc#L644
The difference in behaviour we're seeing between ogre and ogre2 is that the former is actually doing the right thing, while the latter isn't. It looks like Ogre2Camera's background isn't updated when it's set through the API. I think this piece of code isn't doing what it should:
https://github.com/ignitionrobotics/ign-rendering/blob/44a19485aa32f48fd116ad6b5e938996eb5fbd90/ogre2/src/Ogre2RenderTarget.cc#L570-L583

Issue of the sim using <plugin filename="GzScene3D">'s <background_color> and <ambient_light> (as opposed to <scene>'s <background> and <ambient>) to light the scene cannot be reproduced, so no longer a concern. The GzScene3D GUI plugin was deprecated for MinimalScene during transition from Gazebo 5 to 6. Regardless of Ogre version and whether or not SDF file has GzScene3D, sim’s background and ambient colors use values from <scene>’s <background> and <ambient>. If use MinimalScene plugin (default uses Ogre2, but even if original Ogre), sim’s background and ambient colors still use values from <scene>’s <background> and <ambient>.
Original test_scene.sdf file (that uses GzScene3D), shown with Ogre vs. Ogre2.

Same SDF file with <plugin filename="GzScene3D"> removed, which defaults sim to use GUI plugins from gui.config, including MinimalScene with Ogre2.

As mentioned in https://github.com/gazebosim/gz-sim/issues/910#issuecomment-877422638, can we make it so that the <background_color> field in gui MinimalPlugin overrides the <scene> tag for the GUI? The goal is to be able to use a different background color in GUI compared to camera sensors.
One example world that you can use for testing is: sensors_demo.sdf

The original issue was about the <scene> tag not having an effect on the GUI. As @athenaz2 confirmed, the issue is now different. Instead, the <scene> tag currently takes precedence and there is no way to assign different backgrounds for the GUI and sensors. I'll close this issue and @athenaz2 will create a separate issue for that.


not supported sprite json format

What should I do if I want to custom from another json format not like easejs json format.
here example sprite json format from another generator.
player.txt

You will have to write a convertor. What software exports this format? Perhaps you could suggest to the software creator that they should support EaselJS as an export target.

Looks like Spriter?  In any case, it looks look skeletal animation rather than a spritesheet.  So other than finding somebody else who has implemented an easeljs adapter for it, or writing your own, you could also have also have Spriter export it as PNGs and then use TexterPacker (or whatever) to create a single spritesheet along with EaselJS json (assuming Spriter won't pack the spritesheet for you itself, I haven't used it)

@MannyC right i use spriter, is will be little difficult if I must create converter to do it.
is there any another similar spriter that was supported to generate sprite for easejs ?

You'll find some work on adapters for Spine.  Probably because it has an official javascript runtime ( not sure if Spriter does).  Otherwise, as I said, exporting the animated spritesheets rather than the bone instructions might be what you want.

Closing for now, since the solution is not applicable to EaselJS.

Closing for now, since the solution is not applicable to EaselJS.


treatable forms of intellectual disability review

http://www.sciencedirect.com/science/article/pii/S1096719211006081
include this knowledge in MAO

http://www.treatable-id.org/resources/literature-review.pdf
@laurenechan This paper (cited in the above paper), is a good resource.

Below are the terms suggested for PMID: 22212131
Many of these can be easily added via patterns.

Term
In MAXO
Notes:

fasting avoidance
yes

isoleucine restricted diet
no
pattern

dietary precursor restriction diet
no
?

cPMP (Cyclic Pyranopterin Monophosphate/Precursor Z) treatment
no
?

Betaine supplements,
no
pattern

folate supplementation
no
pattern

carnitine supplementation
no
pattern

methionine supplementation
no
pattern

Miglustat therapy
no

dietary protein restricion
yes
*

liver transplantation
yes
pattern

sodium benzoate/sodium phnylacetate   treatment
no

sodium phnylbutyrate
no

Iron chelation
no

stem cell transplantion
no
pattern

gene therapy
yes

creatine supplementation
pattern

Haematopoietic stem cell transplantation
no
pattern

arginine supplementation
no
pattern

sodium benzoate
no

biotin supplementation
no
pattern

folinic acid supplementation
no
pattern

chenodesoxycholic acid supplementation
no
pattern

HMG reductase inhibitor
no

CoQ supplementation
no
pattern

Hydroxycobalamin
no
?

cyanocobalamin
no
?

methylcobalamin
no
?

glycine supplementation
no
pattern

BH4 diet
no
?

amine replacement
no
? Possibly a pattern

N-acetylcysteine
no
?

oral metronidazol
no
?

arginine restriction (or avoidance?)
no
? Possibly a pattern

ornithine supplementation
no
pattern

ketogenic diet
yes

lysine restriction
no
pattern

riboflavin supplementation
no
pattern

beta-hydroxybutyrate supplementation
no
pattern

methione restriction
no
? Possibly a pattern

pyridoxine supplementation
no
? Pattern

diazoxide
no
?

glycine restriction
no
? Possibly a pattern

NMDA receptor antagonist therapy
yes

neuromodulating agents
yes*
need synonym for CNS agent therapy

Dietary restriction branched amino-acids
no
pattern

copper histidine supplementation
no
?

L-dopa substitution
no
?

tyrosine restriction
no
pattern

zinc supplementation
no
pattern

sick day mangement
no
? "; sick day management   ensuring sufficient calorie intake during illnesses" "The diabetes   care team should provide clear guidance to patients and families on how tom   manage diabetes during intercurrent illnesses to avoid complications of   ketoacidosis, dehydration, uncontrolled or symptomatic hyperglycemia,   hypoglycemia." PMID: 18036069 "     Everyone with a child who has a metabolic disorder needs to be prepared for   those days when the child experiences the flu or a cold and changes need to   be made in nutrient intake. With the increased fluid and caloric requirement   associated with fever, children with metabolic disorders are at risk of   having their disorder become uncontrolled. The best way to prevent this is to   increase calories and fluids and reduce the amount of natural protein that is   usually taken.  MSUD-support.org


Customer Feedback Mentor

Specializes in customer feedback and sentiment analysis, offering insights and recommendations.
https://chat.openai.com/g/g-HnmhpcynX-feedback-mentor

GPT is inaccessible, make it public

Done, thanks
On Mon, Nov 13, 2023, 2:07 PM Anil Chandra Naidu Matcha <
@.***> wrote:

GPT is inaccessible, make it public
—
Reply to this email directly, view it on GitHub
https://github.com/Anil-matcha/Awesome-GPT-Store/issues/108#issuecomment-1808842137,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6PBRNLZKLJZA5OPDKEKY5TYEJVY5AVCNFSM6AAAAAA7JTAZUGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBYHA2DEMJTG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Please raise a pull request for the same


Document how to handle external axes / groups

Hello Gijs :)
It would be nice to document how to to handle extra axis or groups on Fanuc robots with this driver.
At the moment I'm only interested in getting ROSSTATE working on a M710iC with a 2 axis turntable in group 2.
I've not yet dug the Karel code but maybe you already have examples with this kind of thing?

From what I understand in the code a linear track will be automatically supported.
Is this the same about axis in external groups?
https://github.com/gavanderhoorn/fanuc_driver_exp/blob/master/src/librosfanuc.kl#L183-L214

Unfortunately this driver, similar to the regular fanuc_driver pkg, does not support multi-group motion at the moment. See ros-industrial/fanuc#9 for an overview issue.
The code you linked to earlier would be involved in multi-group support, but at the moment that is all there is.
Adding this is on the TODO list, but no work has been done in that direction (well, that's not entirely true: there has been some work done, but it's not in the public repositories). A complicating factor is that it would be nice to do make such support dynamic (ie: not hard-coded for a specific setup). That is non-trivial, especially when dealing with both synchronous and asynchronous motion across multiple groups.
An additional complication is that industrial_robot_client currently has no support for multi-group setups. Some of the code from motoman_driver would have to be ported, or fanuc_driver_exp would have to be migrated to industrial_robot_client v2 (the code that is not public already uses this).
Summarising:

no, no support for multi-group setups
can be done, but would need work
there is non-public code that does support it, but that cannot be released as-is and would also need some work

I'm not entirely sure it would be possible with your setup, but one way around this limitation is to change your robot's configuration and move the two additional axes to the first group.
This would most likely mean that all motion of the robot and turntable would become coordinated. Perhaps not something that you'd want.

Just realised that you're mostly asking about ros_state. Adding multi-group state reporting is actually not that involved. I can see whether I can add that some time this week.

Thank you for the detailed responses. If you have some time to craft something it would really be helpful.
I'll think about how I can simplify my application, it's 3D scanning with a Keyence mounted on a Fanuc robot. The positioner turns a part while the robot is fixed at that time, then the robot moves to another pose and the cycle goes on.
There are probably simplifications that would allow to do this without re-writing a lot of code!

There is actually one relatively 'easy' way to get multi-group state reporting working: by using multiple fanuc_driver clients and two instances of ros_state on the controller.
That is how we've done it on ABB robots (such as YuMi fi) with the old driver (EGM will be different).
I'll see if I can quickly hack something together for you.

See the grp2_hack branch (diff).
I've basically just duplicated ROS_STATE, updated the MTION_GRP constant and made sure it ROS_STATE2 uses Server Tag 5 and TCP port 12002.
I'll attach an archive with the binaries once you tell me which version of system software you're running (V7.70 or V8.30).

See positioner_axes_as_78 (diff) for the second approach.
I think I like this better.
You'd only need to replace ROS_STATE, no duplication and the ROS side is also much simpler to configure (no second node, etc).
If you can let me know for which system software version you'd need a binary, I can attach it here to this thread.

Seeing as it's only a single file:

ros_state_r3bg2-2_770.zip
ros_state_r3bg2-2_830.zip

Be sure to rename the files to ros_state.pc before copying to your controller.
I'm pretty sure this will work out-of-the-box.
Let me know.

Hey, I like the second option too! The drivers abstracts groups, which feels good because there is no such thing in ROS from what I know.
I'll begin testing this today and I'll report my progress.
I will also provide you the information you asked !

Hey, I like the second option too! The drivers abstracts groups, which feels good because there is no such thing in ROS from what I know.
I'll begin testing this today and I'll report my progress.
I will also provide you the information you asked !

The drivers abstracts groups, which feels good because there is no such thing in ROS from what I know.

well .. motion groups do nicely map to ROS namespaces. Or at least, they can be made to map like that.
That makes it possible for drivers to relatively easily support asynchronous, but concurrent, execution of trajectories for different motion groups on the same controller.
So strictly speaking: no, there is no 'motion group' concept in ROS, but completely abstracting it away might also not be always desirable.

(just deleted your duplicated comment)

As this is not really an 'officical' solution, let's keep this issue as a stand-in for documentation right now.
Future users looking for multi-group support will find it.

Thanks again for testing.
Glad I was able to help.


Fix bug in logging in UpsertCompaction task

label:
bugfix
At present, the log message comes like:
Unable to get validDocIdsMetadata from all servers. Expected: 0, Actual: 1

This is wrong due to following reasons:

In the loop, we are iterating over the responses of all server-requests, and incrementing segmentCount by 1. Should be serverCount.
We are using the above wrong segmentCount value with expected segmentNames passed value.

Adding both logs for unequal segment count and unequal server count to improve debuggability.
Also renaming all logs to have "validDocIds" for easier debugging. At present, some logs had "valid doc ids" and some had "validDocIds".
cc @snleee

Codecov Report
Attention: 16 lines in your changes are missing coverage. Please review.

Comparison is base (e1e22bd) 61.74% compared to head (7ef221f) 61.77%.
Report is 4 commits behind head on master.

Files
Patch %
Lines

...t/controller/util/ServerSegmentMetadataReader.java
0.00%
10 Missing :warning:

...l/indexsegment/immutable/ImmutableSegmentImpl.java
28.57%
5 Missing :warning:

...oller/api/resources/PinotTableRestletResource.java
0.00%
1 Missing :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master   #12419      +/-   ##
============================================
+ Coverage     61.74%   61.77%   +0.03%
- Complexity      207     1155     +948
============================================
  Files          2436     2436
  Lines        133089   133103      +14
  Branches      20615    20618       +3
============================================
+ Hits          82172    82226      +54
+ Misses        44878    44844      -34
+ Partials       6039     6033       -6

Flag
Coverage Δ

custom-integration1
?

integration
<0.01% <0.00%> (ø)

integration1
<0.01% <0.00%> (ø)

integration2
0.00% <0.00%> (ø)

java-11
61.70% <11.11%> (+0.01%)
:arrow_up:

java-21
61.64% <11.11%> (+0.02%)
:arrow_up:

skip-bytebuffers-false
61.76% <11.11%> (+0.03%)
:arrow_up:

skip-bytebuffers-true
61.59% <11.11%> (+0.01%)
:arrow_up:

temurin
61.77% <11.11%> (+0.03%)
:arrow_up:

unittests
61.77% <11.11%> (+0.03%)
:arrow_up:

unittests1
46.90% <0.00%> (+0.01%)
:arrow_up:

unittests2
27.75% <11.11%> (+0.02%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


chore: upgrade dependencies

Includes autofixes for these lints:
packages/generator-liferay-theme/generators/app/__tests__/index.test.js
  7:1  error  imports must be sorted by module name (expected: "chai" << "chai-fs")  liferay/sort-imports

packages/generator-liferay-theme/generators/layout/__tests__/index.test.js
  7:1  error  imports must be sorted by module name (expected: "chai" << "chai-fs")  liferay/sort-imports

packages/generator-liferay-theme/generators/themelet/__tests__/index.test.js
  7:1  error  imports must be sorted by module name (expected: "chai" << "chai-fs")  liferay/sort-imports

packages/generator-liferay-theme/gulpfile.js
  9:1  error  imports must be sorted by module name (expected: "gulp" << "gulp-coveralls")  liferay/sort-imports

packages/liferay-theme-tasks/plugin/test/index.js
  9:1  error  imports must be sorted by module name (expected: "chai" << "chai-fs")  liferay/sort-imports

packages/liferay-theme-tasks/plugin/test/lib/register_hooks.js
  9:1  error  imports must be sorted by module name (expected: "gulp" << "gulp-util")  liferay/sort-imports

packages/liferay-theme-tasks/plugin/test/tasks/deploy.js
  9:1  error  imports must be sorted by module name (expected: "chai" << "chai-fs")  liferay/sort-imports

packages/liferay-theme-tasks/plugin/test/tasks/version.js
  9:1  error  imports must be sorted by module name (expected: "chai" << "chai-fs")  liferay/sort-imports

packages/liferay-theme-tasks/plugin/test/tasks/war.js
  9:1  error  imports must be sorted by module name (expected: "chai" << "chai-fs")  liferay/sort-imports

packages/liferay-theme-tasks/tasks/watch.js
  9:1  error  imports must be sorted by module name (expected: "http" << "http-proxy" << "http-proxy/lib/http-proxy/passes/web-outgoing")  liferay/sort-imports

✖ 10 problems (10 errors, 0 warnings)
  10 errors and 0 warnings potentially fixable with the `--fix` option.

Seems pretty low-risk so going to merge this.


Add jsonp query string with a "&" instead of "?" if url already contains parameters

Sorry, I didn't see this until now, merging.


Where can I find the system requirements for running OpenFAST and TurbSim?

Is your feature request related to a problem? Please describe.
I'm running OpenFAST and TurbSim in containers and need to set the memory and number of CPUs available to them. I can't find the recommended system requirements/specs in the docs so I'm currently guessing based on real-time usage stats.
Describe the solution you'd like
A link to where the recommended system requirements/specs are if they're already documented, or for this to be added to the docs if not.

Hi @cortadocodes!
We haven't really given much guidance on this since it really depends on the size of the model being used.  A simple land turbine may only need 100 MB, but a large offshore model could require 10 GB or more depending on discretization.
For the number of CPU's, it will depend if OpenMP was enabled or not.  If it isn't enabled, more than one CPU wouldn't gain much.
I do agree we need some form of system requirements given.
@deslaughter or @mayankchetan, do you have any thoughts?

Thanks @andrew-platt! In the docs it says OpenMP is disabled by default - is that still the case? I'm sure I saw the official docker image using OpenMP (2 cores, 4 threads?)
Just had another thought - it would be useful to have some kind of guide on the likely size of the output files (perhaps as a function of number of turbines?)

In v3.5.3 (and a few earlier versions) OpenMP is enabled anytime that FAST.Farm is compiled.  We changed this with PR #2229 to only be active when requested.  This change will be included in 3.5.4 and later.

Ok that makes sense. So anyone using the official docker image will be using multiprocessing by default. Is there a way to enable/disable multiprocessing on the command line? It would be useful to enable it at runtime instead of build time

At the moment we don't have a way to disable at the CLI.  That would be a nice feature.


[Marketplace]: Author of custom app not able to add published app to My applications

EPAM AI DIAL chat version
0.18.0
How to reproduce
Preconditions:
user created custom app
user published version 0.0.1 of custom app
Steps:

by user open DIAL Marketplace / Home page
find published custom app and click on it
select published version and click 'Use model' button
open My applications and check published custom app

Actual result

for author of application published version was NOT added to My applications

Expected result
author of custom app should be able to add published version of the app to My applications
Confidential information

[X] I confirm that do not share any confidential information

verified on staging succesfully