Configure the timeout in the dashboard

Which package/s are you suggesting this feature for?
Dashboard
Is your feature request related to a problem? Please describe
In case the dashboard fails to load deployments as the network is slow, there is no way to change the timeout
Describe the solution you'd like
The user should be able to configure the timeout he wants. This timeout should be stored in the user's metadata. and if it's not found fall back to the timeout configured in the config file.

Suggestion: introduce a new Setting page that contains a timeout field, change password, dark/light mode.

@ehab-hassan can we please have a design for the settings page?

@amiraabouhadid check this
https://www.figma.com/proto/7f7OANwfyTHQxtoP80D4rp/Untitled?node-id=1-16&t=eh8DWQe0dYbd8oMq-0&scaling=scale-down&content-scaling=fixed&page-id=0%3A1

updated

https://www.figma.com/proto/7f7OANwfyTHQxtoP80D4rp/Untitled?node-id=9-228&t=eh8DWQe0dYbd8oMq-0&scaling=min-zoom&content-scaling=fixed&page-id=0%3A1

added update theme card and settings page

blocked on #3341

verfied on devnet
Version fccc6af
settings page is now available

testsuite

The behaviour of the timeout should be verified

Tried with a throttled connection and increased time out and it works.
Do you recommend a specific test that could be more reliable?
@xmonader

Tried with a throttled connection and increased time out and it works.
Do you recommend a specific test that could be more reliable? @xmonader

I didn't see that in your verification steps

Tried with a throttled connection and increased time out and it works.
Do you recommend a specific test that could be more reliable? @xmonader

I didn't see that in your verification steps

okay will add steps and searching for a scenario doing the opposite to watch it fail due to time out

okay I tried to produce a Pessimistic Scenario but still did not work out
made the time out to 3 seconds and made the connection to 3g but still everything is working fine which is weird.

can we also write in the validation the max amount which is 180 and 1800 instead of the max limit exceeded
as we wrote the minimum is 3

@khaledyoussef24 will not be adding reset button at the moment, please open feature request
updated validation error messages to include the max timeout in seconds

verified on devnet
Version ffbb750
max time out validation is now added

after setting the time out ti 3 seconds and tried to verify deploying in this time worked fine and functional

after resetting it it deployed fine

testcase coveing validation
test1
test2
timeout function
test1
test2


Fix mocha commands

This vastly simplifies invocation of mocha. A dir with the name test/ is automatically picked up.
This fixes CI, as there is a .spec hidden deep in node_modules included currently (the CI failures in other PRs).
It also replaces Istanbul with Istanbul's new official binary, nyc.
https://github.com/istanbuljs/nyc

Closing in favor of #46. I checked out this PR and made the appropriate mocha change. One of our node_modules had checked in a .spec.js file that was being picked up by our mocha command.


197 add an on hover test step1

4 layers of condition made it little complex to read, check with Doug if we can simplify this complexity

I agree with Mizanur. We may want to separate out these conditions into helper methods.


dataset with multi objects

How to create .ply file with multi objects in the scene?

Duplicate of #7


Network Abstraction

Adding an abstract layer for Branch Remote interface. This will allows
developers to create their own network layer and handle the network
communication in their own way.
By default Branch provides Implementation for

HttpUrlConnection
or
OKHttp (If dependency is added to the project)

Also this has a lot of clean up and arch changes
@aaustin @EvangelosG

@sojanpr run makeJar with this PR and you will see the ~6 comment related issues in BranchRemoteInterface.java which breaks JAR generation.


ZAI-197 Review ZAIR-101 and make sure the subscribers endpoint works …

…in the namespacing code base

This change is

With such a large amount of functionality (and files) coming into the develop branch with this commit, it might be wise to be extremely picky with what else goes in until this is locked down @cBrenDev


Show the display-name of the claim instead of claim URI, in the self registration page and user consent gadget

Display Claim display name instead of claim URI, when self-registration and user portal consent gadget.

Added DisplayName support for PII Category with https://github.com/wso2/carbon-consent-management/pull/62/

Adding purposes/PII categories with displayName and description is supported with
https://github.com/wso2/carbon-consent-management/pull/63/

@thusithak,
Now we can change the signup page and dashboard with displayName instead of claim URI.

Fixed with https://github.com/wso2/carbon-identity-framework/pull/1381

Fixed with https://github.com/wso2/carbon-identity-framework/pull/1381


Add quick edit functionality for files

I have found the current edit procedure of first opening a file and clicking the edit(pencil icon) link to be little annoying. So, I have added a little code which replaces the current simple text file icon with an edit icon and links to the edit link of the file. Hope it helps.
Sidenote: I have applied the file filter but how do we detect whether a file is editable or not, e.g. images, binaries, etc.

@paulmolluzzo Done. 8ee45626321679e97dd3f0495d610c00f43c6e9e

Thanks for your suggestion, but this isn't something I'm interested in having.
I've created a wiki page if you want to add it there as a tip: https://github.com/sindresorhus/refined-github/wiki

@sindresorhus I can't edit the wiki. Can you please mention the tweak(in case someone else likes it) and link it to my fork?

If you squash it into one commit I'll link to the diff ;)

Here it is: Quick Edit functionality diff

The commit title and message isn't very useful. Fix that. I would also recommend the commit include a link to a screenshot of how it would look like.  If you don't want people to dismiss it right away, you need to sell it.

I have added a screenshot, and updated the message. I know about the commit messages , but they're squashed and hence, not much helpful. Anyway, here is it new diff link.
Thanks.

Ok, I think it need to be more explicit:
Title:
Add a quick edit button for every file in the repo file browser

Message
Let's you quickly edit files without first having to open them.

And don't include the following junk:
Screenshot added.
String concatenation -> Template Strings (ES6).
Single quotes. :\
Move constant declaration to top of the function.
Bugfix: icons were not replaced if coming from a non-tree area of the repo. + Build test fixes.
Edit shortcut: Replace file icon with edit icon.

Thank you for your effort. Does this seems ok?

Just to note I'd like to have this just for the readme file on the repo page. You see the readme, but you need to click through to see the edit button, really frustrating.
@devkhan I'd suggest to have these buttons hidden and to be shown just when you hover on the row of a specific file.

Just to note I'd like to have this just for the readme file on the repo page. You see the readme, but you need to click through to see the edit button, really frustrating.

@hkdobrev Haha, get out of my head 😝 I was going to open an issue about that tomorrow.

@devkhan Added :)

That seems a better implementation, I'd get to it in a few days. Anyway, thanks @sindresorhus.


🐛 Bug Report — allow_custom_ports is not working

According to allow-specifying-a-custom-port-when-making-a-subrequest-with-the-fetch-api
it says that setting the flag allow_custom_ports or a compatibility date greater than 2024-09-02, should allow fetch to work with custom ports for HTTPS, however settings this has no effect, you still get the warning and the api errors out
known issue with fetch() requests to custom HTTPS ports in published Workers: the custom port will be ignored when the Worker is published using the "wrangler deploy" command.

@danlapid

Is the problem you’re having just the error message or is the functionality not working as intended in a deployed worker?

@danlapid i haven't deployed it yet, i'm trying in dev using --remote, and the fetch request don't work, it gets stuck shows an error, looks like maybe the port is removed

Seems like we might’ve missed that then, it should work in local dev without the —remote flag and in a deployed worker

@danlapid it's actually working, i logged the request
the real issue is i'm getting 526 (invalid certificate), my app wasn't checking for this status code, that's why it was stuck
but i had set process.env.NODE_TLS_REJECT_UNAUTHORIZED = '0' to allow invalid certifications, looks like it's not working, how do you disable the invalid certificates in cloudflare fetch?

Seems like we might’ve missed that then, it should work in local dev without the —remote flag and in a deployed worker

Looks like without --remote i don't even get the 526, it fails entirely, but when i add the flag i get status 526

In wrangler dev you can teach it about local certificates using the --https-key-path and --https-cert-path command line args.

What happens in prod, do we need to provide the certs too? or prod can ignore 526's
Woulda been nice if fetch was passed an agent parameter like in node-fetch/undici or  just an option with rejectUnauthorized: false

OK so I did some digging and I think I have an understanding of all this now.
In production:
Since 2024-09-02 (compat date), the default for Workers is that custom outbound HTTPS ports are allowed. So you should just be able to do things like fetch("https://some-domain:5000") and it will work.
In wrangler dev:
Outbound fetches to HTTPS ports, where the server is using proper CA signed certificates should just work (even though you currently get a warning telling you it will fail in production). https://github.com/cloudflare/workers-sdk/pull/7038 should resove that unwanted warning.
Outbound fetches to HTTPS ports that are hosted on local servers using self-signed certificates will fail because workerd will fail to make the TLS connection giving errors about the certificates not being trusted. The solution to this is to tell workerd about your local Certificate Authority certificates, which you use to sign the certificates that the local HTTPS server is using. You do this by setting NODE_EXTRA_CA_CERTS environment variable to point to the file holding the local CA certificates. Wrangler will pick up these certificates and pass them through Miniflare to configure workerd to know about this CA and therefore trust your local server's certificates.

@petebacondarwin what about in production when you make outbound fetches to custom HTTPS ports that are hosted on remote servers using self-signed certificates?

I don't believe we have any way to support self-signed certificates in production.

It is quite easy, and free, to set up domains with Cloudflare to have fully trusted certificates, so I would recommend doing that even for test servers if they are exposed on the public Internet.


⚠ Site has degraded performance

In f6200cf, Site (https://fyle.uk) experienced degraded performance:

HTTP code: 200
Response time: 12081 ms

Resolved: Site performance has improved in b3d0721 after 13 minutes.


Do-Not-Merge: Test implementation of iterating streams with exceptions

Description
Just a quick POC for this discussion https://github.com/Aalto-LeTech/intellij-plugin/pull/126#discussion_r408089430
I don't actually feel this is necessary: for loops are much cleaner. What do you think?

This only works if the function throws at most one type of checked exception right?

This only works if the function throws at most one type of checked exception right?

Well, kinda. E must be a supertype for all the exceptions that are thrown by the consumer function. So if in the test interruptIfZero() could also throw an IOException then the third parameter to StreamUtil.forEach() should be just Exception.class


Ads not showing in release apk

while testing on emulator, ads were showing but after i made a signed release apk ads are not showing. Code is same as before..please help..
<AdMobBanner
adSize="smartBanner"
adUnitID="ca-app-pub-************/2424988888"
testDevices={[AdMobBanner.simulatorId]}
onAdFailedToLoad={error => console.error(error)}
/>

Having same issue, i'm using expo admob implementation. Admobrewarded works fine in dev mode, but when using release apk it stops working.

Having the same problem on ios.

Same problem.
Ad is show up on emulator (Genymotion) but not on real device (debug.apk) !

This is caused by not setting the AppID most likely, there is no way to set it currently on this lib

anyone solve this issue?

same problem!

Me too ?

same problem

troubleshoot below:
a) test ad id - test ad should load
b) wrong ad id - no ad should on load (nothing should show), wrong id can be '1111111'
c) real ad id - real ad should NOT load locally (nothing should show, since it not uploaded)
d) real ad id - real ad should load after uploading to google play (after 4 hours or so, after upload)

ads only work on emulator. Please give solution.

Same issue. Did you solve this problem?

Same problem.. ads were showing in debug apk but not in release apk..
NOTE : I have generated separate apk for different architectures... not a universal apk

Same problem here! Ads shows on Emulator but no in release apk. I'm using react-native-admob

Same problem here! Ads shows on Emulator but no in release apk. I'm using react-native-admob

Did you signed the app? I had same problem but now my ads are showing..

I think if apk release not upload to google play store, The Ads cannot displayed in Release Apk.

In my case i`m use Publisher Banner to Ad Manager. The test show normal but in production not show anything. someone can helpme?

In my case i`m use Publisher Banner to Ad Manager. The test show normal but in production not show anything. someone can helpme?
If your app is signed and you are having the issue in admob.. check this comment
https://github.com/sbugert/react-native-admob/issues/507#issuecomment-597298909

In my case the ads shows in release apk but when i uploaded it to playstore the ads wont show. I have no clue where to debug

In my case the ads shows in release apk but when i uploaded it to playstore the ads wont show. I have no clue where to debug

you found any solution ?

same issue no luck yet

Hey, Any update there, same issue here.

Some here😥please solve this


[cgroups2] Introduces the MemoryControllerProcess.

Introduces the MemoryControllerProcess, the cgroups v2 memory
isolator, which will be used by the Cgroups2IsolatorProcess.
Unlike the MemorySubsystemProcess, the cgroups v1 memory isolator, we:

Don't allow limits on swap memory to be set.
Don't report memory pressure levels (this facility is no longer part
of the cgroups memory controller's API)

Future work may include:

Adding support for swap memory, and
Reporting the (now available) memory pressure stall information

This patch updates the ROOT_MemUsage so it passes on a cgroups v2 machine using the new MemoryControllerProcess.

Going to land this via #581 instead since it needed a minor fix.


feat: add parseMarkdownTables to ktemplate

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


DASHBUILDE-32: Drop jOOQ dependency (fine tuning)

The required modifications to make the new SQL provider implementation work under kie-wb and the jbpm consoles.

I can confirm that the PR fixes the errors that the jbpm console ng was displaying yesterday,
but looking at the commit I'm not confident enough about if the changes will break something else.. so that's why I didn't merge it in master.
I notice that there are still some issues with the filters created in the tasks list, and for that reason I will investigate that path before re-enabling anything in 6.3.x branch.
I wasn't sure either if @porcelli will check something on the PR or not.. so guys please merge asap when you are confident with the changes.

merged in master


Updated progressive web apps topic

[x] I followed the contributing guidelines: https://github.com/github/explore/blob/master/CONTRIBUTING.md

I am:

[x] Suggesting edits to an existing Topic page
[ ] Curating a new Topic page

EDITING AN EXISTING TOPIC PAGE*
I'm suggesting these edits to an existing topic:

[ ] Image (and my file is *.png, square, dimensions 288x288)
[x] Content (and my changes are in index.md)

Please explain why these changes are necessary:
As someone who has been involved with the creation of progressive web apps since day one (I wrote the O'Reilly book Building Progressive Web Apps), I think the current topic needs two changes:

Remove the created_by field which only listed two people as the creators of progressive web apps. While Francis and Alex were immensely influential for the creation of progressive web apps and service workers in particular, and while I personally adore and have been floored by the depth of Alex's intelligence and vision in every single interaction I ever had with him (I never had a chance to meet Francis), I think it isn't fair to attribute to two people what is an industry-wide effort by dozens of people who have worked day and night to make this happen.

I would also suggest replacing the link to Google's web site (which seems to suggest it is the "official website" of progressive web apps) with a link maintained by many different browser vendors (such as MDN). Again, while I absolutely admire Google's efforts to help further the open Web, and believe they have been one of (if not the most) critical elements in making progressive web apps a success, this was an industry wide effort with a lot of resources put in by many companies. If anything, the appearance of progressive web apps being a Google thing has been detrimental to their adoption.

CURATING A NEW TOPIC PAGE

[ ] I've formatted my changes as a new folder directory, named for the topic as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME])
[ ] My folder contains a *.png image (if applicable) and index.md
[ ] All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs

Please explain why you think this Topic page should be curated:
Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

Seems reasonable.
Thanks so much for your contribution!  You rock, @TalAter!


chore(.vscode workspace configs)

Description
Improve dev experience for those who use VSCode by add pathing to view all three radius projects in VScode workspace in order to quickly switch between different projects.
An unfortunate assumption for this to work is that the developer would have cloned all 3 repos, in which case I will add the correct documentation to reflect that
Fixes # (issue)
#34
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

@usrrname why is it needed? I think locations can vary for all repos

Based off conversations with @DogaIster I realize there won't be a need for moving between projects that frequently so I'm going to decline this PR


cloneType vs. chiselCloneType

cloneType doesn't seem to preserve IO directionality, while chiselCloneType does. However, the names are highly unintuitive.
Related to #368, it might be a good idea to have a .clone (which preserves directionality) and .asType / .getType which doesn't. (and in my opinion, the behavior is clearer too)

I agree that .cloneType vs .chiselCloneType is confusing. I don't think that .clone is a good candidate because of it's Java meaning and all of the baggage that comes with that, but I do think that .asType or .getType are good names. Picking these names is pretty tough though, and it might be wise to drop .cloneType unless it does the exact same thing it does now or did in the past...

If we go with the stricter type system in #368 I can see there being a use for two types of clone, one that preserves directionality / "bindings" (I've found it useful to be able to clone another block's IO) and another that does not (for instance, to use a IO data type in a Reg).

Do avoid the name clone. That was the chisel1 name for cloneType and it was problematic for the reason @jackkoenig mentioned.

@sdtwigg used newType in the original #200 pr. My renaming that to chiselCloneType, although well-intentioned, was probably a mistake: I wanted to mark it for internal use only.
Do we need three type generators:

newUnboundType (corresponding to the current cloneType
newUnboundTypeWithWidth (corresponding to the cloneTypeWithWidth
newBoundType (corresponding to the current chiselCloneType

I'm hoping we don't need to expose all three to user code. cloneType exists only because we can't reproduce the client's type construction environment without help from the client. Since it's now part of the public API (and we don't intend to change its semantics), it should probably retain its current name. I'm quite happy changing the name of the other two, and possibly using newUboundType internally, passing the buck to cloneType to do the heavy lifting.

Is there ever a case where we want clone type while dropping widths? While widths aren't part of the types as far as the type system is concerned, I think that's just an implementation detail.
Also, do we want to expose Binding as something users should know about? If not, then it shouldn't be in names of API functions. I also think it makes sense to describe APIs in terms of how it affects the user. Something like .asType() / .getType() (current cloneTypeWidth) vs. like .cloneIo() (current chiselCloneType, or whatever the full scope of Bindings is).

Resolution as follows:

Deprecate chiselCloneType
Deprecate cloneType as a user callable function. Eventually this may be made protected. It will still remain as a function that users need to overload in some cases, like a Bundle with constructor arguments.
Introduce getType, which can only be called on a terminally-bound type (something that was wrapped with Wire(...) or IO(...)) and returns the non-terminally-bound version. It is an error to invoke this on a non-terminally-bound type (with the overall philosophy of stricter separation of model nodes and hardware graph nodes)
Introduce wipeDir, which an only be called on a non-terminally-bound type. It does exactly what you think it should do, it wipes the direction so you can instantiate a Reg or Mem of a bidirectional Bundle.

It is an error to invoke this on a terminally-bound type because you almost always want to use getType instead. If you want to do this, you have to go the extra step and use getType.wipeDir

Introduce requireIsHardware (or requireUnbound, if Bindings is more than an implementation detail?), requireDirectioned, requireUndirectioned APIs. Please suggest better names! This helps library writers enforce the strict separation of model vs. hardware graph types.
Ideally, all this would be done in the (Scala) type system, but that would be a massive structural, and most likely very backwards incompatible, change in Chisel. So impractical. But I'd love to be proven wrong here.

Additionally, cloneType's contract should be such that it must return a non-terminally bound type, so terminal bindings are always final (assign once, non mutable after).
wipeDir will mutably clear non-terminal direction bindings using a special API. Once #440 is implemented, bindings can be made write-once with the exception of wipeDir, which will have access to a private[chisel3] API. It's not possible to clone without bindings, since directionality may be bound in Bundle constructors.

Should address #445, #368. Implementation depends on #440.


Psych Engine replacing sprites with big black boxes, playing the intro off-time, and crashing a ton

Describe your bug here.
Pretty much what the title says.
Psych Engine often replaces sprites with big black boxes and usually crashes when I play a different mod week/song after playing another.
I even downloaded a fresh copy of Psych and put that in a separate folder, with JUST the mod the black-box sprite bug seems to most consistently show up in (if you're curious, it's Mutilation)
Also, Psych seems to go through the intro sequence SIGNIFICANTLY off-time. More specifically, the first 'ayy' is heard at 'not associated with' instead of the line right after. This one specifically seems to carry over into quite a couple mods for some reason. (It happened in Vs Aflack Remastered)
So yeah, a LOT of things going wrong. These problems are occurring in a completely official and unmodified build of Psych. I'm not quite sure what happened. It MUST be on my end, cause I don't see ANYONE else with ANY of these problems.
I tried deleting my Psych Engine saves too, but that changed absolutely nothing.
Also neglected to mention that sometimes Girlfriend, or more rarely Boyfriend, are victims of this. The damn vanilla BF and GF sprites are not safe.
Also, a crash SOMETIMES happens:
when i game over while there are black boxes in existence
or
when i retry from such a game over
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No.

All I could think of is uninstall and reinstall your build.
Other than that its a problem on your end.

Also the intro is supposed to be off time.


📚 Documentation: Add CONTRIBUTING.md to guide contributors

💬 Let us know how we can improve our documentation.
Please add CONTRIBUTING.md file so we can understand how to get started with initial setup and contribute to the actual issues.
Create a CONTRIBUTING.md file to provide contributors with instructions on how to get started with the project.
The file should include:

A brief overview of the project
Steps to set up the project locally
Guidelines for reporting issues and submitting pull requests
Information about coding standards and testing
Any additional resources or documentation relevant to contributors
This will improve the onboarding process for new contributors and help maintain project consistency.

hi @AkashJana18  can you assign this issue to me


Impossible: ill-typed application on inference

Getting an inference blowup with the following code:
module A

assume val m : Type -> Type
assume val return_m : #a:Type -> a -> m a
assume val bind_m : #a:Type -> #b:Type -> m a -> (a -> m b) -> m b
assume val push_m : #a:Type -> #b:(a -> Type) -> (x:a -> m (b x)) -> m (x:a -> b x)

val push_sum : #a:Type -> #b:(a -> Type) ->
                  dtuple2 a (fun (x:a) -> m (b x)) -> m (dtuple2 a b)
let push_sum (#a:Type) (#b:(a -> Type)) (p : (dtuple2 a (fun (x:a) -> m (b x)))) =
    match p with
    | Mkdtuple2 x y ->
        bind_m #(b x) (* #(dtuple2 a b) *) y (fun (y' : b x) ->
        return_m (* #(dtuple2 a b) *) (Mkdtuple2 x y'))

Running F* gives:
Unexpected error; please file a bug report, ideally with a minimized version of the source program that triggered the error.
Impossible: ill-typed application ?26724 : Type
	a:Type ->
b:(uu___151587:a -> Prims.Tot Type) -> p:x:a & A.m (b x) -> x:a -> y:A.m (b x) -> Prims.Tot Type

The example is a bit complex, but I couldn't really minimize it any more. Uncommenting any of the two #(dtuple2 a b) annotations makes the file succeed.
I think inference should succeed here, but even if not, this is a blowup and should be a proper error

This doesn't blow up anymore, but fails due to #1091 at encoding time (so --lax works OK). Closing this one and commenting there.


Remove Technical Preview doc from title

This is now unmaintained and will be deleted or archived. So should rather add a big warning at top linking to the docs.
I have slowly moved all the bits out of here to prepare for shifting it.


Proxied download restriction

Discussed in https://github.com/spencerwooo/onedrive-vercel-index/discussions/222

Originally posted by myl7 January  1, 2022
Currently in proxied download, url param has no limitation. Someone may access urls like https://drive.spencerwoo.com/api/proxy?url=https%3A%2F%2Fgoogle.github.io%2Fstyleguide%2Fcppguide.html to use the api as a proxy, which does not seem to be expected.
To ensure url is valid, maybe we can check if it is an index api raw=true redirection.
And for people who do not use it, as proxied download will consume Vercel bandwidth limitation, maybe an option to turn it off is required.

fixed in 312bcff515dde582ca27488953a58e8300fd17ae


DOC: Clear some warnings for daal4py doc builds

Description
This PR resolves many warnings that pop out when building the daal4py docs and which prevent the CI jobs from building those docs correctly.
Note that it doesn't solve all of the warnings - after this PR, one would still see many of these cases:
scikit-learn-intelex/doc/daal4py/docstring of daal4py._daal4py.classifier_prediction_result:1: WARNING: duplicate object description of daal4py.classifier_prediction_result, other instance in algorithms, use :noindex: for one of them

(I'm not sure what to do about those)

PR should start as a draft, then move to ready for review state after CI is passed and all applicable checkboxes are closed.
This approach ensures that reviewers don't spend extra time asking for regular requirements.
You can remove a checkbox as not applicable only if it doesn't relate to this PR in any way.
For example, PR with docs update doesn't require checkboxes for performance while PR with any change in actual code should have checkboxes and justify how this code change is expected to affect performance (or justification should be self-evident).
Checklist to comply with before moving PR from draft:
PR completeness and readability

[x] I have reviewed my changes thoroughly before submitting this pull request.
[x] Git commit message contains an appropriate signed-off-by string (see CONTRIBUTING.md for details).
[x] I have added a respective label(s) to PR if I have a permission for that.
[x] I have resolved any merge conflicts that might occur with the base branch.

Testing

[x] I have run it locally and tested the changes extensively.
[ ] All CI jobs are green or I have provided justification why they aren't.

Performance
Not applicable.

This worked for a local build, but it seems it was not enough for the CI job named "Docs":
https://dev.azure.com/daal/daal4py/_build/results?buildId=40827&view=logs&j=7e620c85-24a8-5ffa-8b1f-642bc9b1fc36&t=dadee17e-671e-5fd8-4599-c783ec4d74d0
It still fails to import daal4py during the doc build step. Wonder if the issue might be that it is not building it.


New to library text shows " at the end

Screenshot attached to demonstrate.

Fixed in v1.0.1, no ETA on release.


Include support for ESP32 boards

Added support for ESP32 boards.
Tested using a RejsaCAN ESP32 v2.3.  Only one line needs to be changed in RaceChronoDiyBleDevice which refers directly to the bluefruit library.
The only testing performed has been rudimentary, so this PR is mainly for comments while I prove it further.

Just a quick note on throughput.  I played with the updateRateDivider today and was able to get roughly 5x the message rate I was able to get with the ItsyBitsy nRF52840.  The best I could do with the ItsyBitsy was ~10Hz as reported by RaceChrono for 4 CAN ID's.  I was able to crank the ESP32 up to 50-70Hz for 5 CAN ID's.
I have an idea for a method to define aggregate messages in the vehicle-specific header files to get the most out of the available bandwidth, but that will come much later.

Awesome news, thanks!
I also was thinking about a way to define an "aggregate" message, let me know if you prefer me to just bite the bullet and do it, or you can't wait to take care of it yourself.

I don't have a burning desire to implement aggregate messages, but I'm willing to take a stab at it.  The next item on my list of "wants" is analog input support using an ADS1115 or similar.  The ESP32 ADCs are 3.2V only and non-linear.

Gotcha! I suggest you focus on the analog inputs, and I hope to get to tinker with aggregate messages in the next few weeks. The data from my GR86 has an ever so slightly lower refresh rate than I want, so this was something I wanted to do anyways.

Gotcha! I suggest you focus on the analog inputs, and I hope to get to tinker with aggregate messages in the next few weeks. The data from my GR86 has an ever so slightly lower refresh rate than I want, so this was something I wanted to do anyways.

You could always load this build up on one of those boards Magnus sent you ;)

During testing I encountered a bug where RaceChrono showed low rates and an incomplete channel list when starting a session with the car already running.
Disconnecting/reconnecting the CANbus (or turning the car off/on) without stopping the session remedied the issue and RaceChrono started showing all channels at expected rate.
Do you have any ideas what might be going on?  Serial output is below:
Connected.
Connecting to the CAN bus...
Success!
Command: DENY ALL PIDS.
Current state of the PID map:
  No PIDs are allowed.

Command: ALLOW PID 496 (0x1F0), requested update interval: 50 ms.
Current state of the PID map:
  496 (0x1F0), sending 1 out of 2 messages.

Command: ALLOW PID 339 (0x153), requested update interval: 50 ms.
Current state of the PID map:
  339 (0x153), sending 1 out of 2 messages.
  496 (0x1F0), sending 1 out of 2 messages.

Command: ALLOW PID 1555 (0x613), requested update interval: 50 ms.
Current state of the PID map:
  339 (0x153), sending 1 out of 2 messages.
  496 (0x1F0), sending 1 out of 2 messages.
  1555 (0x613), sending 1 out of 5 messages.

Command: ALLOW PID 501 (0x1F5), requested update interval: 50 ms.
Current state of the PID map:
  339 (0x153), sending 1 out of 2 messages.
  496 (0x1F0), sending 1 out of 2 messages.
  501 (0x1F5), sending 1 out of 2 messages.
  1555 (0x613), sending 1 out of 5 messages.

WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
Command: ALLOW PID 1557 (0x615), requested update interval: 50 ms.WARNING: Receive buffer overflow, dropping one message.

WARNING: Receive buffer overflow, dropping one message.
Current state of the PID map:
  339 (0x153), sending 1 out of 2 messages.
  496 (0x1F0), sending 1 out of 2 messages.
  501 (0x1F5), sending 1 out of 2 messages.
  1555 (0x613), sending 1 out of 5 messages.
  1557 (0x615), sending 1 out of 5 messages.

WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
Command: ALLOW PID 1349 (0x545), requested update interval: 50 ms.
Current state of the PID map:
  339 (0x153), sending 1 out of 2 messages.
  496 (0x1F0), sending 1 out of 2 messages.
  501 (0x1F5), sending 1 out of 2 messages.
  1349 (0x545), sending 1 out of 100 messages.
  1555 (0x613), sending 1 out of 5 messages.
  1557 (0x615), sending 1 out of 5 messages.

WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
Command: ALLOW PID 790 (0x316), requested update interval: 50 ms.
WARNING: Receive buffer overflow, dropping one message.

WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
Command: ALLOW PID 809 (0x329), requested update interval: 50 ms.
WARNING: Receive buffer overflow, dropping one message.

WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.
WARNING: Receive buffer overflow, dropping one message.

You could always load this build up on one of those boards Magnus sent you ;)

Totally, but I also want to squeeze every bit of performance from nRF if I can :)

RaceChrono showed low rates and an incomplete channel list when starting a session with the car already running.

Not off the top of my head. Might be a bug in how requested channels got initialized, or might even be a RaceChrono bug...

I'm pretty stumped with the refactor.  C++ is not my main language, so it's been fairly slow going.  I think I'm almost there, I'm just having an issue with the handler function.  I'm hesitant to check it in to this PR, so I've put it in a different branch here

I did a quick scan, looks promising!
If it makes your life easier, you can start by keeping the ESP32-related additions local, and start the PR with nRF52-only refactoring. You can start by:

Creating src/RaceChronoNRF52.h by copying (git cp) the old src/RaceChrono.h
Adding a bunch of virtual <...> = 0; to src/RaceChrono.h and removing the definitions of class fields
Renaming src/RaceChrono.cpp to src/RaceChronoNRF52.cpp

That should work?

Apologies for the delayed reviews, I was traveling last couple of weekends, and was swamped with tasks (at work and otherwise) when I came back.

Sorry I haven't been responsive here.  I've been poking at the refactor here and there but I keep getting frustrated with declaring the CAN handler.  I'll get there.  On the plus side, I have implemented OTA updates over wifi in the main app (for esp32).

I ended up doing some refactor myself in aedc9b41c73e99dbd4f05292e5dbf4154d9f0bf0, please take a look.
Hopefully it is a good example of how ESP32 support could work.
In fact, now that I've started, maybe I'll find some time to do add ESP32 support this weekend myself.

That looks great!  I can try to work from there if you like (assuming you didn't get it done over the weekend), or just let you take the reins.

Sorry, I had some issues with my ESP32 hardware on the weekend (turned out my two RejsaCAN boards were dead on arrival!), but I was still able to make some progress.
Check out d5f397a31e7364a99c4e2596e7702bb475f2ac66!
I've only done some basic tests, so it most likely has bugs.
I'm going to close this PR, but please please give this new version a try and send me new PRs with fixes for whatever bugs you'll find!

And again thanks a lot for your help figuring out how to add this support!

Ah sorry I've meant 7899d636d83533257843dbb6307e143217a8a7ac

I'll load this build this weekend and give it a try!


Get Metadata method isn't passing the necessary options

Can you squash these commits?

@twistor done


IPT with fontawesome integration

First steps in Fontawesome integration. This is going to make the styling a lot easier for the colors of the organisation can be set in the custom.css to match the 'corporate' identity.

Thanks Sijmen for this pull request addressing https://github.com/gbif/ipt/issues/1153 We'll review it shortly.

Thanks @SCozijnsen, and sorry this took so long to merge. It will be in the next release, later this month.


Verify your Play Console developer account now

@Expensify/mobile-deployers Google sent us the email below to verify our Google Play developer account before Feb 11, 2025.

@AndrewGable I assume that's something that only you might be able to do? Let me know if this is a chore any deployer can do and I'd be happy to work on it.

Thanks for making an issue! I can handle


Support exiting of parallel block on first completed task

The parallel element provides a completed-by property but this only works if the task that should determine the exit condition is known upfront.
The proposal is that that we add a new property e.g. complete-on-first-task-completed. This would cause a parallel block to exit as soon as one task exits.
This is useful when running queries in parallel for example. As soon as one task exits the load reduces overall, invalidating all subsequent executions by other tasks. This would ensure a clean exit.
Note the naming above is a proposal by @danielmitterdorfer only and we're open to suggested better ones.

Has a mixed-type completed-by been considered?  an int for number of tasks to end before marking completed or a string for a named task? Having a single parameter vs two that are mutually exclusive makes the natural default behavior (all tasks complete) a little easier to grok, I would think


libotr: upgrade v4, remove v3, for CVEs

Things done:

[ ] Tested using sandboxing (nix-build --option build-use-chroot true or nix.useChroot on NixOS)
[ ] Built on platform(s): NixOS / OSX / Linux
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

I'd very much like at also see:

[ ] libotr upgrade cherry-picked to 16.03
[ ] libotr upgrade cherry-picked to 15.09
[ ] libotr_3_2 removal cherry-picked to 16.03

It would also be nice to:

[ ] libotr_3_2 removal cherry-picked to 15.09

but I understand that is probably more contentious.

@grahamc you can create separate PR with that :)

I'm sorry, I don't understand. A separate PR with what?

https://github.com/NixOS/nixpkgs/pull/13795#issuecomment-194524373

so 2 more PRs: one against 15.09, one against 16.03?

Sorry, didn't notice your PRs and already pushed the 4.1.0 -> 4.1.1 upgrade to master, 15.09 and 16.03: https://github.com/NixOS/nixpkgs/commit/728cf25e168072212ba5aed51be386170e608bc4

Thanks for removing the version bump! :+1:


Use of CONAN_LOGIN_USERNAME for private conan repo

Description of Problem, Request, or Question
I run private Conan repository which I am able to upload packages from console. At the same time I cannot configure cpt to upload packages there.
I followed the instructions initially and got the message "Upload skipped, credentials for remote 'private_repo' not available", even though I specified CONAN_LOGIN_USERNAME.
The problem code was found through PDB as there's no docs for that as far as I aware: you need to set env variables CONAN_LOGIN_USERNAME_private_repo and CONAN_PASSWORD_private_repo.
So, question is, am I able to use the Conan installation and settings that are already in the system without specifying CONAN_PASSWORD in my build scripts?
Environment Details

Conan Package Tools Version: 0.29.1
Operating System: Windows
Operation System Version: Windows 10
Compiler+version: MS VC++ 15
Conan version: conan 1.18.0
Python version: python 3.7.3

Steps to reproduce (Include if Applicable)
Build logs (Include if Available)

OK, that's another case of skipping docs.
For those who find that later: there is Reference at the end of README.md
Solution:
CONAN_UPLOAD="https://private-repo.com/conan_path@True@my_private_repo"
CONAN_LOGIN_USERNAME_my_private_repo="my_username"
CONAN_PASSWORD_my_private_repo="my_password"
CONAN_USERNAME="repo_name"
This will upload "package/1.2.3@repo_name/stable" to Conan repository from CONAN_UPLOAD

The "documentation" is in README file, there is a specific topic about upload:
https://github.com/conan-io/conan-package-tools#upload-packages
Only CONAN_LOGIN_USERNAME, CONAN_PASSWORD and CONAN_UPLOAD should be enough for uploading your package.
If you need to specify the repo name as suffix, is because you are not running Conan Package Tools, or your environment variables are isolated and not been consumed by CPT.
If you need so set CONAN_UPLOAD or any env var as parameter in your script, you can pass directly to ConanMultiPackager constructor, as specified on parameters topic:
https://github.com/conan-io/conan-package-tools#conanmultipackager-parameters-reference

Thanks, for the answer!
Is there a way to use logged in Conan user instead of supplying your own login/password through environment or arguments?

No because it's a mandatory step. It could be logged in before starting CPT, but it will check if you filled username and password, otherwise it won't upload your package.


Update deprecation notice to state that CodeQL Action v1 is discontinued

For now, link the changelog post announcing the deprecation.  However, we expect to publish a new changelog note confirming that the CodeQL Action v1 is now discontinued.  Once that's out we should link it from the notice and changelog.
Merge / deployment checklist

[x] Confirm this change is backwards compatible with existing workflows.
[x] Confirm the readme has been updated if necessary.
[x] Confirm the changelog has been updated if necessary.

Changelog post now published.


make all classes in domTree.js PascalCase and make them named exports

The purpose of this refactor is make our more consistent as well as follow common naming conventions.

@ylemkimon I'm assigning this to you since it's ready for review again.


Comprehensive edit of topic

@sascala i have graphics to add, so please don't merge, yet.

I have some fiddly little changes, too. :-)

@sascala thanks for tweaking. the graphics are finalized and the topic is ready for merge.


Ability to invalidate and rotate node template keys

Today user enters the provide access key on the node template at the moment of creation, and there is no way to invalidate/rotate them. Have to add support for that, and the implementation might require key decoupling.
We should consider this issue while designing the feature as they seem to be entangled
https://github.com/rancher/rancher/issues/12186

with rancher:master build (02/19/2019), we have the ability to decouple the cloud credentials from other node template details. Issues found while testing this feature, have been logged separately.
https://github.com/rancher/rancher/issues/18201
https://github.com/rancher/rancher/issues/18194
https://github.com/rancher/rancher/issues/18040
https://github.com/rancher/rancher/issues/18039


How to generate access token?

The only option seems to be using pscale auth, UI only generates service tokens. We're integrating cloud APIs to collect asset data at Resmo we normally prefer OAuth or API keys and ask user to generate one for us. Planetscale also seems to have Oauth but it seems to be only for device, CLI m2m authentication?

Hi @mustafaakin, we now have Oauth Apps available in beta. https://planetscale.com/blog/introducing-planetscale-api-and-oauth-applications

I know, we are a launch partner :)


[+[!LIVESTREAMs!]+]* St. John Bosco vs Sierra Canyon LIVE FREE ON TV CHANNEL 7 September 2024

[+[!LIVESTREAMs!]+]* St. John Bosco vs Sierra Canyon LIVE FREE ON TV CHANNEL 7 September 2024
The upcoming Friday Night high school football een the Sierra Canyon Mustangs and the St. John Bosco Spartans is set to be an exciting encounter, featuring two teams eager to establish their dominance. Both squads bring unique strengths to the table, promising a competitive and engaging matchup.
🔴📺 GO LIVE==►► CLICK HERE TO WATCH LIVE

🔴📺 STREAMING==►► CLICK HERE TO WATCH LIVE

Sierra Canyon
The Sierra Canyon Mustangs are known for their disciplined and balanced approach, with a strong emphasis on both offense and defense.
Offense: Sierra Canyon’s offense is built around a reliable and versatile quarterback who excels in both the passing and running games. The quarterback’s ability to make accurate throws and extend plays with his legs adds a dynamic element to the Mustangs' attack. The running game is also a key strength, featuring a running back who is adept at finding holes and gaining yards after contact. The offensive line provides solid protection and creates running lanes, ensuring that both the passing and running games can operate effectively.
Defense: Defensively, Sierra Canyon is known for its physical and aggressive style of play. The defensive line is strong and capable of disrupting the opposing offense’s rhythm, while the linebackers are quick and effective in both run support and pass coverage. The secondary is experienced and skilled at reading the quarterback, making it difficult for opponents to execute deep passes or exploit mismatches.
St. John Bosco
The St. John Bosco Spartans are known for their athleticism and high-energy play, particularly on offense.
Offense: St. John Bosco’s offense is characterized by its speed and explosiveness. The quarterback is a playmaker who can change the game with both his arm and legs, often using a fast-paced and spread attack to keep defenses on their heels. The receiving corps is fast and capable of making big plays, stretching the field and creating mismatches. The running back is also a key asset, with the ability to break off long runs and complement the passing game. The offensive line is agile and quick, providing the necessary protection and creating opportunities for both the running and passing games.
Defense: Defensively, St. John Bosco relies on its speed and aggression to disrupt opponents. The defensive line is quick and disruptive, capable of putting pressure on the quarterback and stopping the run. The linebackers are versatile and energetic, making plays in both run support and pass coverage. The secondary is athletic and opportunistic, always looking to create turnovers and capitalize on mistakes.
Key Matchups to Watch
Sierra Canyon’s Balanced Attack vs. St. John Bosco’s Aggressive Defense: Sierra Canyon’s ability to balance the run and pass will be tested against St. John Bosco’s aggressive defensive style. The Mustangs will need to execute well to counter the Spartans’ defensive pressure.
St. John Bosco’s Speed vs. Sierra Canyon’s Physicality: St. John Bosco’s speed and explosiveness will challenge Sierra Canyon’s physical and disciplined defense. The Mustangs will need to contain the big plays and prevent St. John Bosco from exploiting their speed.
Turnovers and Field Position: As with many games, turnovers and field position will play a crucial role. The team that can manage the ball effectively and capitalize on opportunities will have a significant advantage.
Prediction
This game is expected to be a high-energy contest, with Sierra Canyon’s balanced approach going up against St. John Bosco’s explosive playmaking. If Sierra Canyon can maintain control and execute their game plan effectively, they could gain the upper hand. However, St. John Bosco’s ability to make big plays and disrupt the game with their speed could tilt the balance in their favor.


Resolve dev server 404 when refreshing

The webpack dev server will throw 404 not found when refreshing on non-root routes. Configure the fallback option to resolve it.

It may be a few days before i can update npm.


Serverless Next.js

Related to #1104, #1406, #1414.
Hi guys,
Sorry for opening another issue about this, but I see a problem that I have no idea how to solve.
A working example can be found at https://github.com/geovanisouza92/serverless-next, just npm install and npm start.
When opened on the browser, it triggers the "Lambda", that starts building the page as expected, and after responding with all files correctly, a request to /_next/on-demand-entries-ping?page=/ triggers the deletion of .next directory and starts another build again, looping forever. When I run on production mode, it throws ../.next/build-stats.json.
So, about the serverless approach, I understand that is absolutely not related with Next.js in any way. What I see as a problem (at least, that I cannot understand/explain) is this looping thing.
Thanks.

I think it's a baaad idea to build the app in serverless.
In this case, build the app locally and push it(with .next dir) to serverless env and only start the server.
Check this for more info: https://learnnextjs.com/basics/deploying-a-nextjs-app

@arunoda Serverless means there is no server administration, so, no running process involved. No one can simply "start the server".
About this being a good or bad idea, this is not the question. It's a trend. Will eventually happens, more and more often, even with decentralized approaches (p2p, scuttlebut, ask-your-neighbour's-computer-to-render-something...). It's a possibility that I'm trying to explore. :smiley:

As far as I can see, there is this checking about an entry of the last build state for each page, but considering that requests not necessarily (and often) don't get to the same function instance, this kind of state forces the reload on the client. In another context, I would say that this is good, but considering that I'm trying to emulate the function, this state is not kept between requests.
There is a way to disable this checking?

@geovanisouza92 you didn't get my point :D
I know what serverless is.
What you are doing is running your app in dev mode building it somehow in a should not be.
Serverless means you only need to do a minimum task for a request. So, you should not build the app on it.
Please follow this guide: https://learnnextjs.com/basics/deploying-a-nextjs-app
You'll understand what I said.

@arunoda Thanks for pointing the reference. It's clarifying :)
For production it works now, first running npm run build (next build underneath) and then my custom server works.
But,
Yeah, I'm running it in dev mode.
While I'm developing it still keeps removing the .next dir with generated files, and keeps refreshing (even when I run next build first [is this intended?]). So, I'm just guessing here, please, correct me if I missed something:
This build-stats.json thing it's used internally by Next to detect what it's invalid and should be rebuilt, but, while in dev mode, this stats are kept in memory. And due to the nature serverless works (mostly using one function instance per request), this stats are not share, so it's lost between requests.
Considering that I had understood this correctly, my question is: There is a way to keep this stats on file (just like production mode does) so it could be reused by function instances only for development, of course? I mean, some kind of configuration option.
See, I'm just exploring this possibility, and this looping refresh bothers the workflow. I can't just put env NODE_ENV=production everywhere... I need development, test and production modes. I know that you understand that.

I think we are talking different ways and this is the best I can help you. If you need more help, try to join our slack channel.

Use Next.js dev mode only when you are developing.
Use Next.js production mode (next build && next start) when running your app on production
For serverless, build the app locally with next build and push the app with .next directory. Then just use next start

I've tried to mingle aws-serverless-express with the app.prepare() workflow from custom-server-express and it doesn't seam to work...
https://github.com/zeit/next.js/blob/v3-beta/examples/custom-server-express/server.js
https://github.com/awslabs/aws-serverless-express/blob/master/example/app.js
{
  "errorMessage": "\"listener\" argument must be a function",
  "errorType": "TypeError",
  "stackTrace": [
    "Server.addListener (events.js:275:10)",
    "new Server (_http_server.js:234:10)",
    "Object.exports.createServer (http.js:44:10)",
    "Object.createServer (/var/task/node_modules/aws-serverless-express/index.js:144:25)",
    "Object.<anonymous> (/var/task/lambda.js:5:37)",
    "Module._compile (module.js:570:32)",
    "Object.Module._extensions..js (module.js:579:10)",
    "Module.load (module.js:487:32)",
    "tryModuleLoad (module.js:446:12)"
  ]
}

@metaheap I workaround using concurrently to launch next build and serverless offline --port 4000, and a next.config.js with a webpack DefinePlugin to put a API_ENDPOINT to use on every request for development.
For production mode, API_ENDPOINT is an empty string (due the fact that all functions will be behind the same API Gateway), and the web function works with the built .next folder.
The code is at: https://github.com/geovanisouza92/serverless-next
P.S. It's a WIP yet, please, feel free to open issues and provide help :smiley:

@metaheap i was able to hack out a solution to that problem, see my comment here


Configuration isn't working

It is not possible to use a json file to configure the generator because there problems loading Newtonsoft.Json when packaged as NuGet package.

Fixed in mentioned commit.


Typo Recognize Flowers with TensorFlow Lite on Android

URL(s) with the issue:
https://codelabs.developers.google.com/codelabs/recognize-flowers-with-tensorflow-on-android#4
Description of issue (what needs changing):
Copy the TensorFlow Lite model model.tflite and label.txt that you trained earlier to assets folder at lite/codelabs/flower_classification/start/app/src/main/assets/.
The path used above is incorrect and needs to be updated to lite/codelabs/flower_classification/android/start/app/src/main/assets/
Thanks,
George

@lintian06  could you take a look?

@lintian06  could you take a look?

Thank you for the suggestion! It is going to be fixed soon. :-)

Thank you for the suggestion! It is going to be fixed soon. :-)

I see the codelab has been revamped and the issue no longer persists. Please let us know if you have any difficulties. Thanks!


Red Android screen on first touch..(

Hi!
This is an excellent plugin, but I can not use it, for several days I can not find a solution.
I read the instructions, many times I tried to find a solution in a note about android, but unsuccessfully.
I tried to make the most simple -

but even here a failure.
Other plug-ins based on the carousel cause the same error. I do not rule out that my head is just stuck in a dead end, and the solution is simple, but I can not find it.
I see this screen in my dream....
When I first try to scroll:

In general, I need animation of the map and its markers like here

on idea I can use an "ViewPagerAndroid" instead of "ScrollView" or "Carousel" for Platform Android and I started to do it, but I had a new problem - I can not bind an animation to a region change in map
If I said wrong, sorry, I recently began to study programming and application development.
I will be grateful for any advice, in advance for your help !!!
P.S. Sorry for my English)
"react": "16.0.0",
"react-native": "0.50.3",
"react-native-snap-carousel": "^3.4.0"

Hi @messpublic,
First, be aware that you did not follow the contributing guidelines! This is a necessary step if you want us to be able to help you.
In the issue template, you'll find some input that might help you figure out what's wrong, particularly:

Have you tried to start with the provided example and to import your own logic in it step by step?
Have you been able to reproduce the bug on iOS?

Then, you need to provide me with an example that reproduces the issue. Create a new app using https://snack.expo.io/, copy your code and remove things until you’re left with the minimal reproducible demo.
Share your answers as well as a demo and I'll se what I can do about your issue.
As a side note, we've considered implementing ViewPagerAndroid. Unfortunately, the preview effect (which is the root of the plugin) can't be implemented with it at the moment.

This happens in my case sometimes, even if I just use ScrollView.
This issue might be helpful https://github.com/facebook/react-native/issues/16522

Closing as no further feedback was provided.


Add .circleci/config.yml

I have no clue why this was opened.

Unless there is a compelling response from the pull request author in 24 hours, I recommend we close it.

I agree


Bug fix for PropertyDDS summarizer

This PR introduce a bug fix for PropertyDDS summarizer, where users could end-up with inconsistent state in a very spefic scenario described in more details in the test .

@DLehenbauer Can you please take a look ?


🐛 lint/noBarrelFile reports files that are not barrel files

Environment information
Playground

What happened?
A file without re-export is reported.
Playground
Expected result
Files without re-exports should not be reported.
Code of Conduct

[X] I agree to follow Biome's Code of Conduct

By the way, we should certainly skip declaration files (.d.ts).

@togami2864 To understand what kind of file the analyzer is analysing, you can use this API:
let file_source = ctx.source_type::<JsFileSource>();

Thank you for reporting! This bug is misleading:(


BT RUL KIT (Remaining Useful Life) Release 23.12 Operations View Acceptance Criteria

Release 23.12 KIT Operations View

[ ] Quick Setup Guide and Deployment Scripts in Repository

Documentation for the operations view must be available in Eclipse Tractus-X as MD files.
A reference implementation must be deployable via versioned and released HelmCharts with ArgoCD and as local deployment. In addition, a quick setup guide must be provided.

Quick Setup Guides
Deployment Scripts (e.g. local, helm charts, terraform)

Best Practice:

eclipse tractusx-docs-artefacts
How-to-create-a-KIT-website

Artifact Repository:

eclipse-tractusx

Contacts:

Responsible: PO/BO (from relevant Domain)
Responsible for Process: PO / BO (from relevant Domain)
Consult: KIT-CONTACT1, KIT-CONTACT2 + System Team
Review by: PCA/BDA

@maximilianong @danielmiehle okay from your side?
@DennDir this KIT is not part of the release management process yet because the "Release Management Status" is not tracked!

BT RUL KIT shifted to R24.03 (in Consortia OpSync 30.Nov.2023)


Methods other than sendMessage do not accept chat_id

When I try to call bot.sendAudio or bot,sendPhoto I get a "Bad Request: chat_id is empty " despite using the same chatID as in sendMessage (which works perfectly fine)

+1

Thank you for reporting this issue (sorry about my late answer - i don't saw it -.-)
I think the telegram-developer have changed there API. However, i fixed that issue. Now you don't get this exception anymore. But if you send an audio file you will get a BotException ("Could not deserialize response!") - because the response body has been changed.
I will make a litte fix-release. But i think i should check all api-calls against the update telegram-bot-api :)

The problem still exists in forwardMessage. I am using same chat_id for both forwardMessage and sendMessage; however it gives me "Bad Request: chat_id is empty" in forwardMessage.


Just curious: Why are you monckey patching the class instead of the logger instance?

Inspired on you code, I implemented my own version of the multilogger:
def add_logger(name, logger)
  name = name.to_s
  raise "'#{name}' is reserved in #{Rails.logger.class} and can not be used as a log accessor name." if Rails.logger.respond_to?(name)

  Rails.logger.define_singleton_method(name.to_sym) do
    logger
  end
end

add_logger(:yodlee, Log4r::Logger['yodlee'])

And how I'm using it: Rails.logger.yodlee.debug("Querying index!!!")
Thanks in advance!

Hehe I am not even aware that define_singleton_method exists. What are the benefits of define_singleton_method over monkey patching?

The mayor benefit was that I don't need know the class of the logger.
But I'm not sure if that could have some collateral damage...

Actually I think you got a point. Would you like to do a PR?


Render Images stored in Google Drive

from https://github.com/RoamJS/google
Requested by Adam H via slack.

Pretty sure this gets knocked out with #6 correct?

Indeed!


Cut traceback only when a test function is run

perftester cuts traceback on default. It can be a problem when one needs to perform benchmarks and an error is thrown; the minimalistic traceback will not be of any help, hence one needs then to run the Config.full_traceback() method. But note that the minimalistic traceback is needed only during testing, and not even benchmarking. Hence this is what we can do: before running a memory or time test, cut traceback; when the test is done, use the .full_traceback method so that the regular traceback is shown.

Implemented, with the following description:
"Before, the default behavior of the package was to cut traceback and enable the user to change this behavior to show full traceback. This is no good since if one conducts some benchmarks, full traceback should be enabled.
Now the default behavior is to show full traceback, with one exception: during performance testing, traceback is cut, but in all other situations (outside of performance tests), full traceback is shown."


too many warnings and errors

When running dcgm-exporter as a service, it logs on each scrap (in my case every 2s) stuff like this:
2021-01-04 15:34:28.095 WARN  [12466:17166] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.095 WARN  [12466:17166] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.096 WARN  [12466:17166] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.130 ERROR [12466:17166] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/core/DcgmModuleCore.cpp:45] [DcgmModuleCore::ProcessMessage]
2021-01-04 15:34:28.130 ERROR [12466:14315] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/nvswitch/DcgmModuleNvSwitch.cpp:341] [DcgmNs::DcgmModuleNvSwitch::ProcessCoreMessage]
2021-01-04 15:34:28.131 ERROR [12466:14946] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/profiling/DcgmModuleProfiling.cpp:1694] [DcgmModuleProfiling::ProcessCoreMessage]
2021-01-04 15:34:28.142 WARN  [12466:17166] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.142 WARN  [12466:17166] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.142 WARN  [12466:17166] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.151 ERROR [12466:17166] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/core/DcgmModuleCore.cpp:45] [DcgmModuleCore::ProcessMessage]
2021-01-04 15:34:28.151 ERROR [12466:14315] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/nvswitch/DcgmModuleNvSwitch.cpp:341] [DcgmNs::DcgmModuleNvSwitch::ProcessCoreMessage]
2021-01-04 15:34:28.151 ERROR [12466:14946] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/profiling/DcgmModuleProfiling.cpp:1694] [DcgmModuleProfiling::ProcessCoreMessage]
2021-01-04 15:34:28.162 WARN  [12466:15949] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.162 WARN  [12466:15949] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.162 WARN  [12466:15949] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.170 ERROR [12466:15949] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/core/DcgmModuleCore.cpp:45] [DcgmModuleCore::ProcessMessage]
2021-01-04 15:34:28.170 ERROR [12466:14315] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/nvswitch/DcgmModuleNvSwitch.cpp:341] [DcgmNs::DcgmModuleNvSwitch::ProcessCoreMessage]
2021-01-04 15:34:28.170 ERROR [12466:14946] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/profiling/DcgmModuleProfiling.cpp:1694] [DcgmModuleProfiling::ProcessCoreMessage]
2021-01-04 15:34:28.177 WARN  [12466:15949] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.177 WARN  [12466:15949] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.177 WARN  [12466:15949] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.183 ERROR [12466:15949] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/core/DcgmModuleCore.cpp:45] [DcgmModuleCore::ProcessMessage]
2021-01-04 15:34:28.183 ERROR [12466:14315] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/nvswitch/DcgmModuleNvSwitch.cpp:341] [DcgmNs::DcgmModuleNvSwitch::ProcessCoreMessage]
2021-01-04 15:34:28.183 ERROR [12466:14946] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/profiling/DcgmModuleProfiling.cpp:1694] [DcgmModuleProfiling::ProcessCoreMessage]
2021-01-04 15:34:28.188 WARN  [12466:15949] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.188 WARN  [12466:15949] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.188 WARN  [12466:15949] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.193 ERROR [12466:15949] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/core/DcgmModuleCore.cpp:45] [DcgmModuleCore::ProcessMessage]
2021-01-04 15:34:28.193 ERROR [12466:14315] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/nvswitch/DcgmModuleNvSwitch.cpp:341] [DcgmNs::DcgmModuleNvSwitch::ProcessCoreMessage]
2021-01-04 15:34:28.193 ERROR [12466:14946] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/profiling/DcgmModuleProfiling.cpp:1694] [DcgmModuleProfiling::ProcessCoreMessage]
2021-01-04 15:34:28.197 WARN  [12466:15949] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.197 WARN  [12466:15949] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.197 WARN  [12466:15949] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.212 ERROR [12466:15949] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/core/DcgmModuleCore.cpp:45] [DcgmModuleCore::ProcessMessage]
2021-01-04 15:34:28.212 ERROR [12466:14315] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/nvswitch/DcgmModuleNvSwitch.cpp:341] [DcgmNs::DcgmModuleNvSwitch::ProcessCoreMessage]
2021-01-04 15:34:28.212 ERROR [12466:14946] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/profiling/DcgmModuleProfiling.cpp:1694] [DcgmModuleProfiling::ProcessCoreMessage]
2021-01-04 15:34:28.232 WARN  [12466:15949] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.232 WARN  [12466:15949] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.232 WARN  [12466:15949] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.272 ERROR [12466:15949] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/core/DcgmModuleCore.cpp:45] [DcgmModuleCore::ProcessMessage]
2021-01-04 15:34:28.272 ERROR [12466:14315] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/nvswitch/DcgmModuleNvSwitch.cpp:341] [DcgmNs::DcgmModuleNvSwitch::ProcessCoreMessage]
2021-01-04 15:34:28.272 ERROR [12466:14946] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/profiling/DcgmModuleProfiling.cpp:1694] [DcgmModuleProfiling::ProcessCoreMessage]
2021-01-04 15:34:28.284 WARN  [12466:15949] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.284 WARN  [12466:15949] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.284 WARN  [12466:15949] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4254] [DcgmCacheManager::GetLatestSample]
2021-01-04 15:34:28.303 ERROR [12466:15949] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/core/DcgmModuleCore.cpp:45] [DcgmModuleCore::ProcessMessage]
2021-01-04 15:34:28.303 ERROR [12466:14315] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/nvswitch/DcgmModuleNvSwitch.cpp:341] [DcgmNs::DcgmModuleNvSwitch::ProcessCoreMessage]
2021-01-04 15:34:28.304 ERROR [12466:14946] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/profiling/DcgmModuleProfiling.cpp:1694] [DcgmModuleProfiling::ProcessCoreMessage]

Are there any intentions to fix it? Or should dcgm-exporter rather be seen as an hot experimental piece of SW, which should not be used in production?

I too have run into this issue running datacenter-gpu-manager-2.0.13-1.x86_64 RPM and dcgm-exporter built from commit 6860bc83e609eb0c4eba6b5eca7af6c02d50d3b3

I too have run into this issue running datacenter-gpu-manager-2.0.13-1.x86_64 RPM and dcgm-exporter built from commit 6860bc83e609eb0c4eba6b5eca7af6c02d50d3b3

dcgm-exporter/nv-hostengine seems to be very poor software.

Hi @jelmd - thanks for reporting this issue. Can you please provide more information on what your system configuration is? Specifically:

what is the underlying NVIDIA driver version?
which tagged version of dcgm-exporter you're using
what GPUs you're running on
what host Linux distribution

This will help us investigate and respond better to your issue. Thanks

@dualvtable As I'm running into this same issue:

450.80.02
Tag is 2.1.1
In my case it's v100 and I think my p100 might have had same issue, two separate clusters but everything else is identical
RHEL 7.7

418.87.01
2.0.13 included in https://github.com/NVIDIA/gpu-monitoring-tools/archive/2.1.2.tar.gz
8 boxes with 8x GeForce RTX 2080 Ti, 1 box with 4x Tesla V100-SXM2-32GB
Ubuntu 18.04

Great thanks - and when do you guys see this issue? Is that at container startup or do we start emitting these messages after a while?
And one last question - did you observe this in prior releases? I'm trying to determine if this is a regression that we somehow introduced and missed in our test plan.
Thanks again.

Looking at our logs it looks like the messages happen every ~2 seconds, with many messages per iteration.  We had to deploy logrotate to aggressively rotate /var/log/nv-hostengine.log as we had systems with their local disks getting filled up from this one log file.  I do not recall this being an issue prior to the 2.x release but the exact version when this began with exporter is unclear to me.  Looking at yum RPM history for DCGM it looks like when we upgraded to 2.1.1 of the exporter we also upgraded to datacenter-gpu-manager RPM 2.0.13.  Prior to 2.0.13 it looks like we had 1.7.2 with the version of exporter is less clear because our initial deployment was a fork.  The commit I authored and was running locally was ed27d32dd12000dc10f78e4aea632367eae54c17, merged in merge request 25 on gitlab I believe.

Same thing here - produces trash all the time. Log size is ~ 4640 B/s, so ~ 383 MiB/d =8-(

Chiming in, while troubleshooting another issue, I see that my nv-hostengine.log is massive!
14.2 GiB  nv-hostengine.log
filled with:
2021-03-05 15:07:49.246 ERROR [1508:1552] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/core/DcgmModuleCore.cpp:45] [DcgmModuleCore::ProcessMessage]
2021-03-05 15:07:49.246 ERROR [1508:2145] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/nvswitch/DcgmModuleNvSwitch.cpp:341] [DcgmNs::DcgmModuleNvSwitch::ProcessCoreMessage]
2021-03-05 15:07:49.248 WARN  [1508:1552] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:3929] [DcgmCacheManager::GetLatestSample]
2021-03-05 15:07:49.248 WARN  [1508:1552] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:3929] [DcgmCacheManager::GetLatestSample]
2021-03-05 15:07:49.248 WARN  [1508:1552] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:3929] [DcgmCacheManager::GetLatestSample]
2021-03-05 15:07:49.249 ERROR [1508:1552] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/core/DcgmModuleCore.cpp:45] [DcgmModuleCore::ProcessMessage]
2021-03-05 15:07:49.249 ERROR [1508:2145] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/nvswitch/DcgmModuleNvSwitch.cpp:341] [DcgmNs::DcgmModuleNvSwitch::ProcessCoreMessage]
2021-03-05 15:07:49.251 WARN  [1508:1552] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:3929] [DcgmCacheManager::GetLatestSample]
2021-03-05 15:07:49.251 WARN  [1508:1552] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:3929] [DcgmCacheManager::GetLatestSample]
2021-03-05 15:07:49.251 WARN  [1508:1552] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:3929] [DcgmCacheManager::GetLatestSample]
2021-03-05 15:07:49.253 ERROR [1508:1552] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/core/DcgmModuleCore.cpp:45] [DcgmModuleCore::ProcessMessage]
2021-03-05 15:07:49.253 ERROR [1508:2145] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_0-postmerge/modules/nvswitch/DcgmModuleNvSwitch.cpp:341] [DcgmNs::DcgmModuleNvSwitch::ProcessCoreMessage]
2021-03-05 15:07:51.235 WARN  [1508:2461] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:3929] [DcgmCacheManager::GetLatestSample]
2021-03-05 15:07:51.236 WARN  [1508:2461] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:3929] [DcgmCacheManager::GetLatestSample]
2021-03-05 15:07:51.236 WARN  [1508:2461] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_0-postmerge/dcgmlib/src/DcgmCacheManager.cpp:3929] [DcgmCacheManager::GetLatestSample]

Hi, could you also provide the set of metrics you are collecting using the dcgm-exporter?

The files we use for the exporter were copied from this repo at the time when the exporter was deployed:
Cluster with V100s having this issue:
[root@pitzer-rw02 ~]# cat /etc/dcgm-exporter/dcp-metrics-included.csv
# Format,,
# If line starts with a '#' it is considered a comment,,
# DCGM FIELD, Prometheus metric type, help message

# Clocks,,
DCGM_FI_DEV_SM_CLOCK,  gauge, SM clock frequency (in MHz).
DCGM_FI_DEV_MEM_CLOCK, gauge, Memory clock frequency (in MHz).

# Temperature,,
DCGM_FI_DEV_MEMORY_TEMP, gauge, Memory temperature (in C).
DCGM_FI_DEV_GPU_TEMP,    gauge, GPU temperature (in C).

# Power,,
DCGM_FI_DEV_POWER_USAGE,              gauge, Power draw (in W).
DCGM_FI_DEV_TOTAL_ENERGY_CONSUMPTION, counter, Total energy consumption since boot (in mJ).

# PCIE,,
DCGM_FI_DEV_PCIE_TX_THROUGHPUT,  counter, Total number of bytes transmitted through PCIe TX (in KB) via NVML.
DCGM_FI_DEV_PCIE_RX_THROUGHPUT,  counter, Total number of bytes received through PCIe RX (in KB) via NVML.
DCGM_FI_DEV_PCIE_REPLAY_COUNTER, counter, Total number of PCIe retries.

# Utilization (the sample period varies depending on the product),,
DCGM_FI_DEV_GPU_UTIL,      gauge, GPU utilization (in %).
DCGM_FI_DEV_MEM_COPY_UTIL, gauge, Memory utilization (in %).
DCGM_FI_DEV_ENC_UTIL,      gauge, Encoder utilization (in %).
DCGM_FI_DEV_DEC_UTIL ,     gauge, Decoder utilization (in %).

# Errors and violations,,
DCGM_FI_DEV_XID_ERRORS,            gauge,   Value of the last XID error encountered.
DCGM_FI_DEV_POWER_VIOLATION,       counter, Throttling duration due to power constraints (in us).
DCGM_FI_DEV_THERMAL_VIOLATION,     counter, Throttling duration due to thermal constraints (in us).
DCGM_FI_DEV_SYNC_BOOST_VIOLATION,  counter, Throttling duration due to sync-boost constraints (in us).
DCGM_FI_DEV_BOARD_LIMIT_VIOLATION, counter, Throttling duration due to board limit constraints (in us).
DCGM_FI_DEV_LOW_UTIL_VIOLATION,    counter, Throttling duration due to low utilization (in us).
DCGM_FI_DEV_RELIABILITY_VIOLATION, counter, Throttling duration due to reliability constraints (in us).

# Memory usage,,
DCGM_FI_DEV_FB_FREE, gauge, Framebuffer memory free (in MiB).
DCGM_FI_DEV_FB_USED, gauge, Framebuffer memory used (in MiB).

# ECC,,
DCGM_FI_DEV_ECC_SBE_VOL_TOTAL, counter, Total number of single-bit volatile ECC errors.
DCGM_FI_DEV_ECC_DBE_VOL_TOTAL, counter, Total number of double-bit volatile ECC errors.
DCGM_FI_DEV_ECC_SBE_AGG_TOTAL, counter, Total number of single-bit persistent ECC errors.
DCGM_FI_DEV_ECC_DBE_AGG_TOTAL, counter, Total number of double-bit persistent ECC errors.

# Retired pages,,
DCGM_FI_DEV_RETIRED_SBE,     counter, Total number of retired pages due to single-bit errors.
DCGM_FI_DEV_RETIRED_DBE,     counter, Total number of retired pages due to double-bit errors.
DCGM_FI_DEV_RETIRED_PENDING, counter, Total number of pages pending retirement.

# NVLink,,
DCGM_FI_DEV_NVLINK_CRC_FLIT_ERROR_COUNT_TOTAL, counter, Total number of NVLink flow-control CRC errors.
DCGM_FI_DEV_NVLINK_CRC_DATA_ERROR_COUNT_TOTAL, counter, Total number of NVLink data CRC errors.
DCGM_FI_DEV_NVLINK_REPLAY_ERROR_COUNT_TOTAL,   counter, Total number of NVLink retries.
DCGM_FI_DEV_NVLINK_RECOVERY_ERROR_COUNT_TOTAL, counter, Total number of NVLink recovery errors.
DCGM_FI_DEV_NVLINK_BANDWIDTH_TOTAL,            counter, Total number of NVLink bandwidth counters for all lanes
DCGM_FI_DEV_NVLINK_BANDWIDTH_L0,               counter, The number of bytes of active NVLink rx or tx data including both header and payload.

# DCP metrics,,
DCGM_FI_PROF_GR_ENGINE_ACTIVE,   gauge, Ratio of time the graphics engine is active (in %).
DCGM_FI_PROF_SM_ACTIVE,          gauge, The ratio of cycles an SM has at least 1 warp assigned (in %).
DCGM_FI_PROF_SM_OCCUPANCY,       gauge, The ratio of number of warps resident on an SM (in %).
DCGM_FI_PROF_PIPE_TENSOR_ACTIVE, gauge, Ratio of cycles the tensor (HMMA) pipe is active (in %).
DCGM_FI_PROF_DRAM_ACTIVE,        gauge, Ratio of cycles the device memory interface is active sending or receiving data (in %).
DCGM_FI_PROF_PIPE_FP64_ACTIVE,   gauge, Ratio of cycles the fp64 pipes are active (in %).
DCGM_FI_PROF_PIPE_FP32_ACTIVE,   gauge, Ratio of cycles the fp32 pipes are active (in %).
DCGM_FI_PROF_PIPE_FP16_ACTIVE,   gauge, Ratio of cycles the fp16 pipes are active (in %).
DCGM_FI_PROF_PCIE_TX_BYTES,      counter, The number of bytes of active pcie tx data including both header and payload.
DCGM_FI_PROF_PCIE_RX_BYTES,      counter, The number of bytes of active pcie rx data including both header and payload.

Cluster with P100 having this issue:
[root@owens-rw01 ~]# cat /etc/dcgm-exporter/default-counters.csv
# Format,,
# If line starts with a '#' it is considered a comment,,
# DCGM FIELD, Prometheus metric type, help message

# Clocks,,
DCGM_FI_DEV_SM_CLOCK,  gauge, SM clock frequency (in MHz).
DCGM_FI_DEV_MEM_CLOCK, gauge, Memory clock frequency (in MHz).

# Temperature,,
DCGM_FI_DEV_MEMORY_TEMP, gauge, Memory temperature (in C).
DCGM_FI_DEV_GPU_TEMP,    gauge, GPU temperature (in C).

# Power,,
DCGM_FI_DEV_POWER_USAGE,              gauge, Power draw (in W).
DCGM_FI_DEV_TOTAL_ENERGY_CONSUMPTION, counter, Total energy consumption since boot (in mJ).

# PCIE,,
DCGM_FI_DEV_PCIE_TX_THROUGHPUT,  counter, Total number of bytes transmitted through PCIe TX (in KB) via NVML.
DCGM_FI_DEV_PCIE_RX_THROUGHPUT,  counter, Total number of bytes received through PCIe RX (in KB) via NVML.
DCGM_FI_DEV_PCIE_REPLAY_COUNTER, counter, Total number of PCIe retries.

# Utilization (the sample period varies depending on the product),,
DCGM_FI_DEV_GPU_UTIL,      gauge, GPU utilization (in %).
DCGM_FI_DEV_MEM_COPY_UTIL, gauge, Memory utilization (in %).
DCGM_FI_DEV_ENC_UTIL,      gauge, Encoder utilization (in %).
DCGM_FI_DEV_DEC_UTIL ,     gauge, Decoder utilization (in %).

# Errors and violations,,
DCGM_FI_DEV_XID_ERRORS,            gauge,   Value of the last XID error encountered.
DCGM_FI_DEV_POWER_VIOLATION,       counter, Throttling duration due to power constraints (in us).
DCGM_FI_DEV_THERMAL_VIOLATION,     counter, Throttling duration due to thermal constraints (in us).
DCGM_FI_DEV_SYNC_BOOST_VIOLATION,  counter, Throttling duration due to sync-boost constraints (in us).
DCGM_FI_DEV_BOARD_LIMIT_VIOLATION, counter, Throttling duration due to board limit constraints (in us).
DCGM_FI_DEV_LOW_UTIL_VIOLATION,    counter, Throttling duration due to low utilization (in us).
DCGM_FI_DEV_RELIABILITY_VIOLATION, counter, Throttling duration due to reliability constraints (in us).

# Memory usage,,
DCGM_FI_DEV_FB_FREE, gauge, Framebuffer memory free (in MiB).
DCGM_FI_DEV_FB_USED, gauge, Framebuffer memory used (in MiB).

# ECC,,
DCGM_FI_DEV_ECC_SBE_VOL_TOTAL, counter, Total number of single-bit volatile ECC errors.
DCGM_FI_DEV_ECC_DBE_VOL_TOTAL, counter, Total number of double-bit volatile ECC errors.
DCGM_FI_DEV_ECC_SBE_AGG_TOTAL, counter, Total number of single-bit persistent ECC errors.
DCGM_FI_DEV_ECC_DBE_AGG_TOTAL, counter, Total number of double-bit persistent ECC errors.

# Retired pages,,
DCGM_FI_DEV_RETIRED_SBE,     counter, Total number of retired pages due to single-bit errors.
DCGM_FI_DEV_RETIRED_DBE,     counter, Total number of retired pages due to double-bit errors.
DCGM_FI_DEV_RETIRED_PENDING, counter, Total number of pages pending retirement.

# NVLink,,
DCGM_FI_DEV_NVLINK_CRC_FLIT_ERROR_COUNT_TOTAL, counter, Total number of NVLink flow-control CRC errors.
DCGM_FI_DEV_NVLINK_CRC_DATA_ERROR_COUNT_TOTAL, counter, Total number of NVLink data CRC errors.
DCGM_FI_DEV_NVLINK_REPLAY_ERROR_COUNT_TOTAL,   counter, Total number of NVLink retries.
DCGM_FI_DEV_NVLINK_RECOVERY_ERROR_COUNT_TOTAL, counter, Total number of NVLink recovery errors.
DCGM_FI_DEV_NVLINK_BANDWIDTH_TOTAL,            counter, Total number of NVLink bandwidth counters for all lanes

FWIW: replaced dcgm-exporter incl. datacenter-gpu-manager on 10 boxes with nvmex and got rid off ~ 500 GB logfiles.
nvmex is a KISSed agent written in C and thus needs less resources, in my case ~ 6 vs. 24 MiB RSS, ~ 120 MB vs. 6 GB VSZ, CPU usage ~ 12+-5% vs. 45+-15%, on average ~ 25W less/box. We do not use MIG, so for now this part and less useful/static data NVML provides are ignored/not fetched.
Just in case you wanna try it out on Ubuntu: Download and install  nvmex-10 or nvmex-11 as well as libprom. They probably work on other linux distros as well if libmicrohttpd.so.12 is installed.

i have save issue, /var/log/nv-hostengine.log have much warnings and errors. it cause this log file size upper to 15GB!.
2021-07-15 08:17:23.624 ERROR [1:24] GetLatestSample returned No data is available for entityId 0 groupId 1 fieldId 230 [/workspaces/dcgm-rel_dcgm_2_1-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4395] [DcgmCacheManager::GetMultipleLatestSamples]
2021-07-15 08:17:23.625 ERROR [1:24] GetLatestSample returned Feature not supported for entityId 0 groupId 1 fieldId 449 [/workspaces/dcgm-rel_dcgm_2_1-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4395] [DcgmCacheManager::GetMultipleLatestSamples]
2021-07-15 08:17:53.623 WARN  [1:13] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_1-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4315] [DcgmCacheManager::GetLatestSample]
2021-07-15 08:17:53.623 ERROR [1:13] Error: unable to retrieve PCIe topology information: Feature not supported [/workspaces/dcgm-rel_dcgm_2_1-postmerge/dcgmlib/src/DcgmHostEngineHandler.cpp:1616] [DcgmHostEngineHandler::ProcessGetTopologyIO]
2021-07-15 08:17:53.624 ERROR [1:13] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_1-postmerge/modules/core/DcgmModuleCore.cpp:82] [DcgmModuleCore::ProcessMessage]
2021-07-15 08:17:53.624 ERROR [1:20] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_1-postmerge/modules/nvswitch/DcgmModuleNvSwitch.cpp:356] [DcgmNs::DcgmModuleNvSwitch::ProcessCoreMessage]
2021-07-15 08:17:53.624 ERROR [1:20] ReadNvSwitchStatusAllSwitches() returned No data is available [/workspaces/dcgm-rel_dcgm_2_1-postmerge/modules/nvswitch/DcgmModuleNvSwitch.cpp:387] [DcgmNs::DcgmModuleNvSwitch::RunOnce]
2021-07-15 08:17:53.624 ERROR [1:22] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_1-postmerge/dcgm_private/modules/profiling/DcgmModuleProfiling.cpp:1816] [DcgmModuleProfiling::ProcessCoreMessage]
2021-07-15 08:17:53.624 ERROR [1:13] GetLatestSample returned No data is available for entityId 0 groupId 1 fieldId 230 [/workspaces/dcgm-rel_dcgm_2_1-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4395] [DcgmCacheManager::GetMultipleLatestSamples]
2021-07-15 08:17:53.624 ERROR [1:13] GetLatestSample returned Feature not supported for entityId 0 groupId 1 fieldId 449 [/workspaces/dcgm-rel_dcgm_2_1-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4395] [DcgmCacheManager::GetMultipleLatestSamples]
2021-07-15 08:18:23.623 WARN  [1:96] Fixing entityGroupId for global field [/workspaces/dcgm-rel_dcgm_2_1-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4315] [DcgmCacheManager::GetLatestSample]
2021-07-15 08:18:23.624 ERROR [1:96] Error: unable to retrieve PCIe topology information: Feature not supported [/workspaces/dcgm-rel_dcgm_2_1-postmerge/dcgmlib/src/DcgmHostEngineHandler.cpp:1616] [DcgmHostEngineHandler::ProcessGetTopologyIO]
2021-07-15 08:18:23.624 ERROR [1:20] ReadNvSwitchStatusAllSwitches() returned No data is available [/workspaces/dcgm-rel_dcgm_2_1-postmerge/modules/nvswitch/DcgmModuleNvSwitch.cpp:387] [DcgmNs::DcgmModuleNvSwitch::RunOnce]
2021-07-15 08:18:23.624 ERROR [1:96] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_1-postmerge/modules/core/DcgmModuleCore.cpp:82] [DcgmModuleCore::ProcessMessage]
2021-07-15 08:18:23.624 ERROR [1:20] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_1-postmerge/modules/nvswitch/DcgmModuleNvSwitch.cpp:356] [DcgmNs::DcgmModuleNvSwitch::ProcessCoreMessage]
2021-07-15 08:18:23.625 ERROR [1:22] Unknown subcommand: 3 [/workspaces/dcgm-rel_dcgm_2_1-postmerge/dcgm_private/modules/profiling/DcgmModuleProfiling.cpp:1816] [DcgmModuleProfiling::ProcessCoreMessage]
2021-07-15 08:18:23.626 ERROR [1:96] GetLatestSample returned No data is available for entityId 0 groupId 1 fieldId 230 [/workspaces/dcgm-rel_dcgm_2_1-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4395] [DcgmCacheManager::GetMultipleLatestSamples]
2021-07-15 08:18:23.626 ERROR [1:96] GetLatestSample returned Feature not supported for entityId 0 groupId 1 fieldId 449 [/workspaces/dcgm-rel_dcgm_2_1-postmerge/dcgmlib/src/DcgmCacheManager.cpp:4395] [DcgmCacheManager::GetMultipleLatestSamples]

Based on feedback from NVIDIA I set the following environment variable to silence the extra logging:
__DCGM_DBG_LVL=NONE

Now the only logs I get in /var/log/nv-hostengine.log is 1 or 2 messages every 30 seconds.


add namespace and schema to settings.xml

@garrettjonesgoogle

How much does this matter?

The schema probably not much. The namespace, quite a bit though Maven is notorious for ignoring this. It's sort of like if a Java compiler decided it was going to ignore package names and only used the bare classnames for everything.


could it set don't route?

Could it set the popup notification do not route but will set the seen = true when click the notification? thanks.

Hi,
This is not supported by default, but you could implement it on your application like this I think:

instead of URL, return '#' for this notification
use jQuery to catch the click on that notification, prevent default and fire the ajax call yourself

Something like:
$('#notifications [data-route="#"]').click(function () {
  $.get('<?= Url::to(['/notifications/notifications/read']) ?>', {
    id: $(this).data('id'),
  });
  return false;
});

Thanks a lot.