[Burn-P3+ Prometheus Bug]: Incomplete Greenup, Curing, etc definitions by Season cause crashes

Contact Details
No response
What happened?
The fire growth options (such as green up, curing, etc) allow values to be set by season. Default values are used if these tables are empty, but if values are present but not all seasons are accounted for (either explicitly or implicitly with "All" / NA values) zero vector values are created that cause problems.
Solution: Better generalized error handling to make sure datasheets of this type account for all sampled (though not necessarily all defined) seasons, causes, etc.
What component are you seeing the problem on?
No response
Relevant log output
No response
Approvals Process

[ ] Testing For Issue
[ ] Merge

Actually, for if (for example) a user specifies the green up condition for Spring but doesn't specify any information about green up for Summer, should we insert the default value for Green up for Summer (with a warning), or should we just error out and report the problem? @BadgerOnABike @katieb1

Hmm, I think defaults are tougher to assume based on seasons as seasons don't necessarily mean a specific set of weeks. For example if there is an early spring and late spring defined but greenup and curing are only define for early spring, what assumption do we make for late spring?
From that perspective I'm a fan of error out and report.


Update multi-factor-authentication-nps-extension.md

alternate login id is now supported.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@benpahl : Thanks for your contribution to the Azure documentation! The author, @kgremban, has been notified to review your proposed change.

Hi @benpahl, thanks for making this fix. Please make one style update before I sign off on this pull request. Instead of listing the full article URL, please make a hyperlink with alt text like this:
name of article

Oops. Github took my markdown too literally :) let me try that again:
[name of article]
no line break
(nps-extension-advanced-configuration.md)

Kelly, I think i've updated the hyperlink properly. Thanks! BP

@kgremban - Please see the comment from @benpahl on August 18.
To resolve this pull request, please add an appropriate comment so that automation can take appropriate action.   Thanks

Thanks for making that edit, @benpahl
#sign-off


Supports New Operator

Released April 16, 2015
Added new operators.
https://cloud.google.com/bigquery/release-notes#04162015

Press release said
Added COALESCE.
Added GROUP_CONCAT_UNQUOTED.
Added support for RIGHT OUTER JOIN and FULL OUTER JOIN.
Added ROLLUP and GROUPING modifiers.

maybe more updated new operators.
BIT_AND, BIT_OR, BIT_XOR, EXACT_COUNT_DISTINCT, UNIQUE,
CAST, NVL, EXP, INSTR, LTRIM, RTRIM,

Added
GroupBy supports ROLLUP
BqFunc :
Coaslesce, GroupConcatUnquoted, Grouping, BitAnd, BitOr, BitXor, ExactCountDistinct, Unique, Cast, Nvl, Exp, InStr, TrimLeft, TrimRight

0.6.1


Improving PackageDescriptor for URL-specified packages

pub struct PackageDescriptor {
    pub name: String,
    pub version: String,
    #[serde(rename = "type")]
    pub package_type: PackageType,
}

The current PackageDescriptor struggles to describe dependencies that do not come from the repository specified by PackageType (e.g., dependencies specified by URL). The current solution for this seems to be to put the URL in the version field, but this seems like a bit of a stretch of the meaning of that field.
I'm opening this issue to start a discussion about how this could be improved in the future.

Javascript
npm allows specifying packages by URL in many different ways:
// URL directly to a tarball. No version specified
    "asd": "http://asdf.com/asdf.tar.gz",
// `git+ssh` URL with a commit-ish
    "cli": "git+ssh://git@github.com:npm/cli.git#v1.0.27",
// `git` protocol URL with a `semver` version range
    "example": "git://github.com:npm/example#semver:^5.0",

I would hope that the git URLs are locked to a specific commit hash before they are put into the package-lock.json, but I haven't yet tested this.


Cannot upload the same Tenant Customization to more than 1 production Tenant

Hi team,
Look, I have created Tenant customization, with

app id = guid1
app name = app name 1
publisher = publisher 1
version = <IP_ADDRESS>

Then i uploaded that to the Online Business Central Production Tenant A => Everything works fine.
Then i uploaded the same tenant customization (with the same id, publisher name, app name and a version) to the Online Business Central Production Tenant B => And I've got an error that the same version of this app is already exists!
So why is that? Is it a bug? Or this is by design?
Thanks.
P.S. Sorry if i created that in a wrong thread.

@dkatson how are you uploading the extension to the BC production tenant?

Hi, Extension Management => Upload Extension
Dmitry

On 19 Dec 2018, at 10:34, Alexandru Toader<EMAIL_ADDRESS>wrote:
@dkatson how are you uploading the extension to the BC production tenant?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

this is a really terrible management !!! if I have many customers who need the same app, it is necessary to have a different project for each customer. If we have other apps that depend on each other, to which  to make updates ... you become crazy !!! Also it is not sure that changing only the app id the publication is successful! Can anyone has found a way to manage apps in a centralized way, and branch out the deployment based on the necessary tenants?

Hi, read here
https://community.dynamics.com/nav/b/katsonsnavblog/archive/2019/01/23/top-tips-and-tricks-on-how-to-create-per-tenant-extensions
Dmitry Katson,
MVP
My Blog
My Twitter
My LinkedIn

On 12 Feb 2019, at 14:11, giann85<EMAIL_ADDRESS>wrote:
this is a really terrible management !!! if I have many customers who need the same app, it is necessary to have a different project for each customer. If we have other apps that depend on each other, to which to make updates ... you become crazy !!! Also it is not sure that changing only the app id the publication is successful! Can anyone has found a way to manage apps in a centralized way, and branch out the deployment based on the necessary tenants?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

We are aware of the issue but we don't have a good solution for it yet.
You are able to publish the extension for another tenant if you change the version number and I know it is just a workaround and not a solution to the problem.

This is a big issue for us and will be an issue for a lot of other developers. We really want to be able to write tools that we can deploy to multiple tenants, even if they aren't functionality the client themselves will use.
We have data import tools we use for implementation that we've converted to BC that help us mass apply templates. We've also created customisations that we've found multiple customers are interested in, but we aren't an ISV so we aren't putting these on the app store.
Being able to only publish these tools to a single tenant without having to bump the version numbers is frustrating to say the least!

Hi @charlespockert ,
We resolved these problems through changes in internal process. See here for details, it may help: https://funwithcside.wordpress.com/2019/05/03/versioning-per-tenant-extensions-using-github-releases/
Cheers
Jurica

@JuricaB so what the error is actually saying is that some differences between one package and another exist, and in fact you can deploy the same customisation across multiple tenants as long as you use the same build files from tenant to tenant.
I have no issue with this as we can just generate build artifacts or check in packaged versions (it's a shame that Azure DevOps doesn't have the same "releases" functionality as GitHub).
Going to give this a shot.

@JuricaB are you aware if the limitation on deployment extends to sandbox? e.g. if we deploy to sandbox, does this prevent us publishing a recompile of the same extension to a production tenant?

@JuricaB are you aware if the limitation on deployment extends to sandbox? e.g. if we deploy to sandbox, does this prevent us publishing a recompile of the same extension to a production tenant?

I have not run into any such issues - so far! Maybe I have just been lucky?

Vote here to make this possible

Closing this issue as it has been converted to an idea which was implemented a few releases ago. Thank you for the input.


DBZ-3528 Support for MongoDB Outbox Event Router SMT

https://issues.redhat.com/browse/DBZ-3528
Major changes

Added Kafka Connect SMT for MongoDB Outbox Event Router
Added unit tests and integration tests
Added documentation for MongoDB Outbox Event Router
Extracted a method to utilize as util method for validating configuration string of additional fields
Modified access modifiers of Outbox Event Router's configuration fields to use in mapping from MongoDB Outbox Event Router's configuration fields to existing ones

Hey @sgc109, so I did one more review pass, and this is looking really good to me know. There's one last question about whether the aggregate ID should be an OID.
Apart from that, and more as a follow-up, it would be great to have an example for using this SMT in our demos repo, similar to the one for the existing outbox router. Do you think you could provide that? The example wouldn't have to be as elaborate, e.g. we wouldn't necessarily need this actual services, writes to the outbox table could be done in a transaction using the MongoDB CLI. Of course I wouldn't mind having flavours of those example services using MongoDB either :)
In any case, that can be a follow-up task, just gauging your interest here.

In fact, I will move forward and merge this PR once CI has passed. If you think the aggregate id should be an OID (I tend to think that), you could send a follow-up PR. @Naros, could you rebase your "Outbox GA" PR once this one is in. Note this PR here surfaces some issues we have spoken about before, like the "debezium" option name space and the duplicated payload id (not quite sure where we stand with this discussion), unless you took care of those already also for this new SMT implementation.

I've logged https://issues.redhat.com/browse/DBZ-4302 for adding the example.

Rebased and applied. Great work, @sgc109, thank you so much.

Let's follow up on the issue re the aggregate id type.

@gunnarmorling Yes, I'll give it a try to provide the example of this SMT and modify aggregateid related things too.


chore: Change something missing… console log

Although very minor the console.log in the terminal has a line that reads as “Something missing or not working as expected...” this was interpreted by me as a statement to the fact something was wrong even though there was clearly no errors thrown. It would have been clearer to me if the text was changed to “If something is missing or not working as expected...”
Again this is a really minor issue but thought it would not hurt to create a PR
Thanks
Ryan

You're right, this can be confusing, thanks 👍


Occasion selector color and behavior

@lcoenen @buckwierd
From the occasion selector:

can we improve how it looks like when you are selecting the option? So it looks cleaner.

can we make the selection color, not that green? Can we make it our orange with white letters maybe?

Technically possible but I'm not sure if it's only CSS. I'll check it out.
Will do

Do you have any idea on the how to improve it or how it should look?

I'll try to come up with something. I'll get back to you on this.

I can't find a way to modify it via CSS with Inspect. I can't even find the element that is determining the background colour when choosing an option.
I won't be of much assistance with this one.
If you use it, you will see that the UX is not very pleasant since it looks out of sync with the overall form. The width does cover the entire field, as you can still see the arrow on your right.
So maybe small fixes to it, and updating the selection colour would be enough for now.
Thanks 👍

On my end the dropdown has a normal standard drop down behaviour:

Simple list
Blue bg for the hovered option

@RohrerHope the only thing I can do here at the moment is to optimise the padding at the top

@RohrerHope We could also change the color of the title liek Payment, Message, Occasion etc. to orange, to make them more visible. Agree or will we leave them grey?

@buckwierd
I'll play with the css regarding the title colours and get cable to you. Not today most probably.
Thanks.

This is how it looks now

This is how it would look like with titles in our orange

I like how the orange titles look like.
If we move forward with that option, then other titles in the platform are also greyed out, so we need to check for those and change them as well.
Thanks 👍

The other titles will be automatically updated after we changed the global grey color that’s connected to these type of titles.
The color grey is defined by 4-6 shades in the global color file, so we’ll have to change one, see which titles are affected and then decide if we send it to master or revert it.

Sounds good.
BTW, about the occasion selector. It now looks different than in the original screenshot I posted. It looks cleaner.
Did anyone change anything in it?


Scope-limited calls

Some calls require specific scopes or types of credentials to function.
For example:

Featured playlists can be retrieved with application credentials
Searching requires user credentials
Some fields of a user request are provided only with certain scopes
Playlist and follow modifications generally require scopes

Determine the credentials and scopes required for each call. Document them. Should access be restricted before a request or by catching an error from Spotify?

Functions are now documented

Restricting the requests in Spotify may be confusing and annoying to deal with. The Spotify devs probably change the scopes from time to time and unexpected errors would be thrown if noone is actively maintaining the repo. Also, outdated versions of spotipy would be obsolete. But I'm unsure about how often these changes actually happen.
Maybe if somehow a test could make sure that the spotipy requirements are the same as the official ones it'd be easier to maintain.

I agree. No idea if they change the specifications, I'd hope not. Perhaps between API versions, since this is v1. But that's a separate issue. Let's just make sure the errors carry enough meaning to the caller.


Let 352 2 fe project creation form

Project creation form - Form Pages 2, 3 and 4.
This PR adds the projects creation form pages 2, 3 and 4
Testing instructions
Acceptance criteria
There will be a way for a signed up user with role “project developer” to create a project
The user is able to enter the project’s mandatory and optional fields (see “project” fields in the “forms” sheet)
There will be a way to validate the information entered in the fields
Errors are displayed if the information is incorrect
There will be a way for the user to know that the content should be written in the language of the account
There will be a way confirm or dismiss the creation of the project
Note: Save/cancel
The layout must comply with the designs defined HeCo - Work in progress
Tracking
LET-352

@barbara-chaves If not part of this PR, could you create another one with these points:

There will be a way for the user to know that the content should be written in the language of the account
There will be a way confirm or dismiss the creation of the project


[BUG] onExitFullScreen and onEnterFullScreen is execute twice when trigger

Describe the bug
Function written in the onExitFullScreen and onEnterFullScreen is execute twice.
To Reproduce
Just use the existing example given and print any value during exit and enter full screen. You will notice the function is executed twice.
Expected behavior
It shouldn't execute twice.

For me they are even executed more than twice - and in completely random order. For example, when entering fullscreen, onExitFullscreen is called a few times and then onEnterFullscreen is called a few times. Same when exiting fullscreen. This makes it the methods completely pointless and unusable.

This error is still reproducible. Any update or solution?


The example of "Calling Java from JavaScript" doesn't work

Hi,
I tried to use TeaVM with an example from the official website. However, I couldn't get the expected result in the 'Calling Java from JavaScript' section. When I executed 'mvn clean package', I got an error message in the console.

I would appreciate it if you could help me find out what's wrong with my code. Thank you!

import org.teavm.jso.JSBody;
import org.teavm.jso.dom.html.HTMLDocument;
public class Client {
	@JSBody(params = { "message" }, script = "console.log(message)")
	public static native void log(String message);

	@JSBody(params = { "str", "count" }, script = ""
	        + "return javaMethods.get('java.lang.String.substring(II)Ljava/lang/String;')"
	                + ".invoke(str, 0, count);")
	public static native void left(String str, int count);

    public static void main(String[] args) {
    	log("fasfds");
    	left("barzoo", 2);
        var document = HTMLDocument.current();
        var div = document.createElement("div");
        div.appendChild(document.createTextNode("TeaVM generated element111"));
        document.getBody().appendChild(div);
    }
}

java 17.0.7 2023-04-18 LTS

Apache Maven 3.9.2 (c9616018c7a021c1c39be70fb2843d6f5f9b8a1c)

You can do it like this:
class Start {
  public static void main(String[] args) {
    exportFoo((a, b) -> foo(a, b));
  }

  private String foo(int a, String b) {
     // do something with a and b and produce result
  }

  @JSBody(params = "foo", script = "main.foo = foo;")
  private static native void exportFoo(ExportFunctionFoo foo);
}

@JSFunctor
interface ExportFunctionFoo extends JSObject {
  String call(int a, String b);
}

now from JS you should call main method first to install foo function, and then you can use foo from JS code, e.g.:
main();
console.log(main.foo(23, "qwe"));

Thank you very much! I will give it a try.


How to check the options details of Futures?

For example, I want to query the option chain of futures /ES. What symbol should I put to the API calls? If I simply provide "ES", it directs me to the stock ES, rather than the futures.

Someone else was wondering the same thing, this was the Schwab API team's response: "Hello, Thank you for reaching out to the Schwab Trader API Support Team. The GET /chains endpoint does not currently support data for options on futures. At this time, it will only return data for equity and index options."
Also, futures typically follow this format:
Key format: '/' + 'root symbol' + 'month code' + 'year code'
Month code is 1 character: (F: Jan, G: Feb, H: Mar, J: Apr, K: May, M: Jun, N: Jul, Q: Aug, U: Sep, V: Oct, X: Nov, Z: Dec)
Year code is 2 characters (i.e. 2024 = 24)
Key examples: "/ESF24", "/GCG24", "/ES"

I see. Thanks a lot @tylerebowers!


MTL-1288 Fix Race Condition and Debug Mode

Summary and Scope

Fixes MTL-1288

Issue Type

Bugfix Pull Request

Race Condition Fixes
This fixes two race conditions.

Fix the race condition with the pave function. Do not create anything until after the pave function has ran to completion.
Fix the race condition with dmsquash-live, add wait_for_dev to prevent pivoting to root before dmk8s finishes.

Metal Debug
This also fixes debug. metal.debug was not honoring metal.debug=1 in some cases. Also add metal.debug to every possible file except for module-setup.sh.
Consistent Behavior
This change removes the need to key off metal.no-wipe. Instead if the ephemeral disk is found this module quits, otherwise if luks is disabled and a deployment server is set this module must find a disk. metal.no-wipe is just a safeguard to ensure wipe functions are not invoked when it's enabled. This makes behavior consistent with dracut-metal-mdsquash.
Consider NVME-Only Systems
Leverage the new disks_exist method to wait for /dev/sd or /dev/nvme devices. This ensures that pure NVME systems can deploy, otherwise only SD systems and mixed (SD + NVME) are compatible.
Misc.

Add/update License

Prerequisites

[x] I have included documentation in my PR (or it is not required)
[x] I tested this on internal system (x) (if yes, please include results or a description of the test)
[x] I tested rebooting with metal.no-wipe=0
[x] I tested rebooting with metal.no-wipe=1
[x] I tested rebooting with the disk boot loader
[x] I tested the three scenarios above on k8s-masters and k8s-workers

Idempotency

Risks and Mitigations
What is less risky, or more risky now - or if your mod fails is there a new risk?
This mitigates the risk of loosing partitions from forgetting to manually wipe, ensuring that any boot from the PIT node will wipe the nodes.
This does pose some risk in-and-of itself being that this is significantly changes the codebase and that this codebase is hard to test.

Done testing. NCNs wipe themselves whenever they're booted with metal.no-wipe=0, otherwise partitions are mounted normally when diskbooted or netbooted with metal.no-wipe=1.


Using Forms in Grid does not stretch input controls to the maximum length of the grid column when validation tooltip is enabled to the input control

Select one ...  (check one with "x")
[x] bug
[ ] feature request
[ ] enhancement

Expected behavior

The input text control's length should be extended to the length of the grid column.
Actual behavior

When a validation tooltip is attached to the input control, it doesn't size properly according the length of the grid column.

Reproduction of behavior

Steps:

Create a form inside a grid (just like the sample in the "Forms in grid" section of the Forms (layout) documentation.
In a "form-group row" div, there should be two columns, one for the label and one for the input text.
Create two set of form-group row, the other has a validation tooltip and the other has none.
Issue: The one that has a validation tooltip does not resize properly. It does not stretch its length the length of the grid column. See screen shot above, the length of the Code field is shorter than the other fields without validation tooltips.

<form class="compact" [formGroup]="employeeForm" (ngSubmit)="onSubmit()" [hidden]="submitted">

                Code

                    <input class="form-control" type="text" id="txtCode" formControlName="code">
                    Code is required.

                First Name

                    <input class="form-control" type="text" id="txtFirstName" formControlName="firstName">

</form>

Include a link to the reproduction scenario you created by forking one of the Clarity Plunker Templates:

Environment details

Angular version: 4.0.X

Clarity version:

OS and version:

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Closing this for now. Just need to set the label width to 100% to stretch it all the way to the length of the column.

@whizkidwwe1217: .form-control class on the .tooltip should do the same.


Save Settled and Redeemed dates on Invoice

Currently there are only booleans. Settled date is useful for ordering a transaction list.

@elnosh any update on this? we'd like to get the cashu LNClient merged for NWC


Generate source-map reference into less-files

This change generates less source-maps correctly
so that they are actually used by Chrome.

Coverage remained the same at 94.118% when pulling 8f3a9e16752227e0b910874f548fc33987dbc798 on source-maps+ into 14787a15d5836a5b2506384b245221284f353e1a on master.

Coverage remained the same at 94.118% when pulling 80a1c877bbd34c523d6662d8f19246d6f07d009c on source-maps+ into 14787a15d5836a5b2506384b245221284f353e1a on master.


docs: add Guild#features type

Please describe the changes this PR makes and why it should be merged:
Guild#features was abstract/not very obvious so I added typings for it, which I feel is necessary because it can only be a specific subset of strings in an array.
Semantic versioning classification:

[ ] This PR changes the library's interface (methods or parameters added)

[ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)

[x] This PR only includes non-code changes, like changes to documentation, README, etc.

Why does this need an entire typedef? I'd be interested in minimizing extra documentation that has limited purpose; I think just putting it in the existing doc string is sufficient.

We have other typedefs for types used just once - so I thought this was alright, I'm not sure what'd be preferred, though.

Fair enough. I still disagree with the concept, but consistency is good. 👍

Misses MORE_EMOJI


Timeline pin unpin need document update

Team for pin and upin option to appear on timeline beside control actions configure security privileges mention are for msdyn_customcontrolextendedsettings  --> create/rea/write....but as per check done you have new table msdyn_timeline pin. Security role should have create/Read/delete permissions on this table.

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

ID: fa09a110-d91d-b551-3cc8-5c6885857e65
Version Independent ID: 3e787680-48f9-a3c6-73be-667be545e562
Content: Timeline Overview for Users - Power Apps
Content Source: powerapps-docs/user/add-activities.md
Service: powerapps
Sub-service: end-user
GitHub Login: @dsierman
Microsoft Alias: dsierman

Thanks for your comment, @ravulask. This issue has been assigned to the doc author for review.


Update express-graphql

This fixes a peer dep warning for graphql 15
Here's the changelog for express-graphql
Highlights of the breaking changes in 0.10.0

https://github.com/graphql/express-graphql/pull/608 Do not pass parameters if we can't parse them.
https://github.com/graphql/express-graphql/pull/622 Sync TS typings with Flow typings
https://github.com/graphql/express-graphql/pull/624 Flow cleanup typings
https://github.com/graphql/express-graphql/pull/626 Convert CommonJS module syntax to ES6
https://github.com/graphql/express-graphql/pull/638 Drop support for TS < 3.4

@Whoaa512 Thanks a lot for minimal PR 👍
Was a pleasure to merge 🙇


Identical molecule found for num_molecules > 1

It seems that always the same molecule is found when choosing num_molecules > 1.
Can easily be reproduced, taking the default config.

Ok, I resolved the issue. It seems to be a cross-issue with other packages installed in my virtual environment. Having a plain mindlessgen environment allows for generation of multiple molecules. 🎉
As a remark, maybe include some sanity check that not the same hash is used for multiple runs. E.g. check the molecule ID written to  mindless.molecules.

Great to hear! 🎉 Do you know the exact reason for np.random giving always the same result? So that we can include it to a Known Issues section?

Hard to say, especially because the numpy.random seed was different at each run. Guess it was an exotic cross-effect. Hopefully, this should not happen to too many users. As mentioned above, checking for identical output might be a good sanity check and worth raising a notification.

My solution is to add a random number seed associated with time like this,
It's not an elegant way, but works
in /src/mindlessgen/molecules/generate_molecule.py
357     def generate_random_coordinates(at: np.ndarray) -> tuple[np.ndarray, np.ndarray]:
358         """
359         Generate random coordinates for a molecule.
360         """
361         # import the time module
362         import time
363
364         # get the current time in seconds since the epoch
365         seconds = time.time()
366
367         atilist: list[int] = []
368         xyz = np.zeros((sum(at), 3))
369         numatoms = 0
370         np.random.seed(int(seconds)+1929)

My solution is to add a random number seed associated with time like this, It's not an elegant way, but works
in /src/mindlessgen/molecules/generate_molecule.py
357     def generate_random_coordinates(at: np.ndarray) -> tuple[np.ndarray, np.ndarray]:
358         """
359         Generate random coordinates for a molecule.
360         """
361         # import the time module
362         import time
363
364         # get the current time in seconds since the epoch
365         seconds = time.time()
366
367         atilist: list[int] = []
368         xyz = np.zeros((sum(at), 3))
369         numatoms = 0
370         np.random.seed(int(seconds)+1929)

Thanks for your feedback!
But shouldn't the np.random.seed be not fixed in standard applications and clean environments? Do you have an idea how to check for this issue before starting a calculation or how to get rid of it?

Thanks for your reply,
My guess is the 'random number generator' in the multiprocessing pool generates the same seeds for each subprocess.
Just like discussion in this question,
https://stackoverflow.com/questions/29854398/seeding-random-number-generators-in-parallel-programs


BPA: Display description

BPA rules contain a Description field explaining why the Best Practice exists. From the BPA screen, this description is not available without significant navigation (Manage rules > (find the rule) > Edit rule).
This could be a hover text on the rule, a button at the top, or on the right click menu. It would also be fantastic to have URL links to web articles that explain the rules in greater detail.

Check out these rules - many rules have links to articles/videos.
https://powerbi.microsoft.com/en-us/blog/best-practice-rules-to-improve-your-models-performance/


The name 'DataTransfer' does not exist in the current context

I'm getting an error compiling in the BlogDetailsView.cs with the latest code.  "The name 'DataTransfer' does not exist in the current context" on line 32.  Is DataTransfer in Xamarin Essentials?
My Xamarin Essentials is from Nuget version 1.0.1

It has been changed to "Share". I will update the repo today :)


Produce state changes to changelog topics

Overview
Built on top of feature/recovery/topic-changelog-manage
Produces state changes to a changelog topic, which is successfully expanded on/used by another recovery feature branch. This is here to keep the logic specific to just producing to the changelogs separate (since it can be).
Uses column families.

I will probably update the delete_cache logic after seeing and rebasing Haris's PR, which gave me in idea on how I can probably remove its necessity.

merging everything into 1 branch....


Add ability to exclude by tag

It would be really useful to be able to exclude resources and classes by 'tag'.  In my case, for some hosts, puppet.conf is always different between environments because we update the environment setting with the current environment.

Sure, that shouldn't be too hard to implement.


prune mode does not work

OS Linux
Daemon compile from source
Prune mode does not work
In sbtc.conf - prune=700

In logs
But blockchain not prunning

Indeed, same here, Very concerning as we need to carry the whole BTC history....
Very inefficient to not be pruning it

Can someone from dev address this please?
Thanks


learning pytorch

first import pytorch then go online and search some useful pytorch sites, The Incredible Pytorch

beginners should start here

this is the repo that i made when i was learning pytorch and followed an auto-generated timeline from chatgpt, [learning-pytorch]{https://github.com/jynlee7/learning-pytorch}


Support for multiple let in do notation

Currently, multiple let does not work in do notation.
meta example : tactic unit :=
do let x := tactic.skip, y := x in y --fails

meta example : tactic unit :=
do let x := tactic.skip in let y := x in y --succeeds

We recently added support for Haskell-like let-decls in do-notation.
We can now have let x := v, in a do-block.
That is,
do a_1,
     let x := v,
     a_2

is sugar for
do a_1,
     let x := v in do,
     a_2

The drawback is that after the ,, Lean is now expecting the rest of a do-block.

Note that, the following is accepted now:
meta example : tactic unit :=
do let x := tactic.skip,
   let y := x,
   y

Apparently, Haskell allows the following variant that may be useful for us too.
meta example : tactic unit :=
do let {x := tactic.skip,
        y := x},
   y

Here is a way to fallback into the regular let-expression
meta example : tactic unit :=
do (let x := tactic.skip,
        y := x in y)


Creating the translation for contribute-bugs.md

In the hope that will be helpful for https://github.com/rust-lang/rust-www/pull/501

👍


Accept-Datetime-Format bug

Accept-Datetime-Format is not respected in heartbeat messages:
This is what I get when Accept-Datetime-Format is set to UNIX
Pricing Heartbeat 2016-12-13T13:41:27.222512838Z
================================================

type = HEARTBEAT
time = 2016-12-13T13:41:27.222512838Z

Type = PRICE
instrument = EUR_NZD
time =<PHONE_NUMBER>.426472413
status = tradeable
bids = [1]
asks = [1]
closeoutBid = 1.47247
closeoutAsk = 1.47301

Type = PRICE
instrument = EUR_HKD
time =<PHONE_NUMBER>.296723637
status = tradeable
bids = [1]
asks = [1]
closeoutBid = 8.24445
closeoutAsk = 8.24594

Could you please also unify __str__() implementation for different entities? Currently it's not the same at least for PRICE and HEARTBEAT messages. I suppose Type in PRICE should be lowercase.

The heartbeat problem was a known bug that was fixed recently. I'll check why it hasn't been released yet. To my knowledge it should at least be on fxtrade practice by now.
The str inconsistencies are because those strings are generated using the property's "display names", however no display names were provided for those entities. I'll add them and push out a build. The truth is I'm not super happy with the the str representations provided, but they are what we have for now. Maybe just dumping YAML from str would look nice...

Let me know when it is released to fxTrade live.
As for dumping YAML, I think it's a good idea. As long as it makes output consistent.

The fix should be on fxtrade practice, but won't be promoted until the first maintenance of the new year (likely Jan 6)

Any updates on this issue?

Thanks for fixing this.

Ah, thanks for checking and verifying.


Purpose of this PR is to add some of the icons

Description
Change is adding new icons. 7 icons have been added

viewSOMExpression:  Purpose is to view SOM expression for a component.
groupInPanel: This is for grouping various components into a single panel
addChildPanel: This is to add child panel in a panel
addPanelToolbar: adds toolbar to panel in authoring
fragmentAdd: To add a fragment
tableCellsSplit: split table cell
commentAdd:  it's used in review and commenting. Once a form is in review, the reviewer can add field-specific comment

Related Issue

Motivation and Context
This change provides some icons that were part of Coral but are not part of Coral-Spectrum.
These are required for Adaptive form Authoring UI. Icons are required only for GreyScale.
How Has This Been Tested?
The same has been tested using Examples in code. Please find attached a snapshot to see how new icons show in UI.
Screenshots (if appropriate):

Types of changes

[] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ x] I have read the CONTRIBUTING document.

Hi,
Thanks for your submission, it looks good, there are a few small corrections:
Please inline styles, remove and tags in symbols.

@CezCz : Thanks for feedback. I have removed inline style.


Support platform

Fix #3415
There are no environment variable MOLECULE_PLATFORM_NAME set by default.
How to use

Test one image

Assume platform name is ubuntu-18.04
molecule test --platform=ubuntu-18.04

or
export MOLECULE_PLATFORM_NAME=ubuntu-18.04
molecule test

Test all images

unset MOLECULE_PLATFORM_NAME
molecule test

I am wondering if it would not be better to implement it the same way ansible does:
  -l SUBSET, --limit SUBSET
                        further limit selected hosts to an additional pattern

@ssbarnea
Thanks for your attention.
I prefer to use '--platform' as platform is self-explanatory and used extensively in molecule project.
But if you insist, I don't mind changing it to 'subset'.

Any chance to refresh this?

The PR is rebased on main.
Could you kindly review it?

@zhan9san Did you ever tried to run the tests locally because I never seen them passing on that change.

Hi @ssbarnea
Thanks for your time.

I never seen them passing on that change.

Actually, it did pass the checks once.
As the main branch is growing faster, and it is easy to get the expected PYTEST_REQPASS mismatched in PR.
I am wonder would it be possible to remove the PYTEST_REQPASS in Github action. Maybe it will avoid some unnecessary warnings.

I will mark it as draft to avoid being noisy and we should get it out of draft only when the CI is passing on it.

Here is a test PR in my forked repository, the pipeline failed at uploading coverage data because of the authentication issue.
I am leaving this PR status as draft. Could you please review it and trigger the pipeline?
Thanks for your amazing work maintaining this project.

If you change the number of tests you are expected to also update the PYTEST_REQPASS values. That variable is used only as a fail-safe mechanism for protecting us from making changes that might stop all/some tests from being run.

Hi @ssbarnea
Thank you for running the pipeline. The CI failed at sudo apt-get update.

If you change the number of tests you are expected to also update the PYTEST_REQPASS values.

Please allow me to describe the following scenario. One PR may resolve conflicts many times if it is not merged in time.
Time 0: PYTEST_REQPASS is 500 in main branch
Time 1: 3 tests are added in PR-1 and PYTEST_REQPASS is changed to 503, and CI for PR is successful. PR-1 is ready to merge.
Time 2: 4 tests are added in PR-2 and PYTEST_REQPASS is changed to 504, and CI for PR is successful. PR-2 is ready to merge.
Time 3: PR-1 is merged into main branch, which results in at least one conflict in PR-2 about PYTEST_REQPASS.
Time 4: Rebase PR-2 branch on main to resolve the conflict, and the PYTEST_REQPASS becomes 507 in PR-2 branch.
Due to some reasons, PR-2 is still not merged into master and PR-3 is created.
Time 5: PR-3 is created and 5 tests are added and merged into main. The PYTEST_REQPASS becomes 508, which will also introduce at least one conflict in PR-2.

Hi @ssbarnea
The code is rebased on main, and the conflict PYTEST_REQPASS is fixed as well.
Would you mind checking it again?

@zhan9san @ssbarnea
Shouldn't this option exist for other operations as well? Such as molecule converge, molecule lint, etc. From a users perspective I kind of expected the option to exist for all of the other commands that accept the -s flag.
It would be great to be able to quickly test a single platform during development with molecule converge -s scenaro -p platform and it would also be beneficial to be able to run the molecule lint/syntax check on a single platform in a CI since there is really no need to run the linting multiple times.
(Perhaps I should open a separate issue to discuss this)

@gardar
It would be great if you can submit a PR as well.


Update minimum_note_length default value to the value used on basicpitch.io

also correct comment regarding the unit used

Do I need to bump the version to 0.2.1 in setup.cfg?


feat: add static discovery

I think this is quite simple but I am having a hard time with a working example. I am confused with GOSSIP_PORT: 3322,CLUSTER_PORT: 3320, REMOTING_PORT: 50052.
Help is needed.
closes #335

@qazwsxedckll let me take a look at a working example and see what we can come up. Also thank you so much for this PR. I really appreciate the effort.

@qazwsxedckll for the cluster engine to work efficiently we need the following ports:

gossipPort: This is used by Hashicorp memberlist.
peersPort: This is the port Go-Akt nodes used to discover each other
remotingPort: This is required for remoting communication between actor systems on the various nodes on the cluster.

I hope this clarifies the various ports. I am open to any simplification if necessary.

Like it stated here https://github.com/Tochemey/goakt?tab=readme-ov-file#clustering, cluster mode requires remoting to be enabled.

@qazwsxedckll I added some validation to the configuration. Please accept the collaborator invite I sent you and then ci pipeline should run smoothly. Once again thanks for the contribution.

@qazwsxedckll The PR is ready now. I have added the example project for this discovery. Thanks

@qazwsxedckll I am going to merge your PR. I did run the ci locally and it seems great. Please do you have any objection or anything else to add?


Sort comments

Sort comments in TOC order, preamble before CFR.

Some small things, but overall very nice

Nice excited to see it


[ENH] Speed up notebooks

Describe the feature or idea you want to propose
Notebook testing now takes around 40-50 mins, which is excessive imo. Matt has added a breakdown to the time each takes. It would be good to try speed up the worst offenders.
Describe your proposed solution
speed up some of these

Start with those over 100 secs:

[ ] Clustering (585 secs): see #659
[ ] forecasting_proba (442)
[ ] forecasting (353)
[ ] deep_learning (319)
[ ] dictionary_based (141)
[x] signature_method (116) see #662
[ ] sklearn_distances (111)

can close this, things seem fine atm


request: switch to not interfere with ssh config

Hello, thanks so much for your work on rtinst, much appreciated.
Could you implement a switch/option for the installer to not modify the SSH config?
I understand your reasoning for why it's there, however I feel it'd be beneficial to leave that option to the user - rather than enforcing it by default. Less important would be a second switch to 'add' vsftpd or not, however I'd be happy with just the SSH change.
Looking forward to your feedback on this - take care!

I'll add it as a request. All PR's are welcome and appreciated towards increasing the quality of rtinst, so feel free to contribute 👍
To comment on this. Remember that rtinst is an installation script which installs rTorrent/ruTorrent and add some security aspects when having a web server. So, more advance user are probably either not using rtinst or integrating rtinst into their installation script. The latter is what I've been doing for years and it's quite easy. Here is a snippet which could be a start:
#!/usr/bin/env bash

export USER=USERNAME        # Input the user which run rTorrent

# Backup ssh config
cp /etc/ssh/sshd_config /etc/ssh/sshd_config_BAK

# Install rtinst
bash -c "$(wget --no-check-certificate -qO - https://raw.githubusercontent.com/arakasi72/rtinst/master/rtsetup)"

# Run rtinst
sudo -u $USER sudo -i -- rtinst -l # Enable logging

# backup rtinst ssh config and set old backup as ssh config
cp /etc/ssh/sshd_config /etc/ssh/sshd_config_RTINST_BAK
mv /etc/ssh/sshd_config_BAK /etc/ssh/sshd_config

...

I'll add it as a request. All PR's are welcome and appreciated towards increasing the quality of rtinst, so feel free to contribute 👍
To comment on this. Remember that rtinst is an installation script which installs rTorrent/ruTorrent and adds some security aspects when having a web server. So, more advance user are probably either not using rtinst or integrating rtinst into their installation script. The latter is what I've been doing for years and it's quite easy. Here is a snippet which could be a start:
#!/usr/bin/env bash

export USER=USERNAME        # Input the user which run rTorrent

# Backup ssh config
cp /etc/ssh/sshd_config /etc/ssh/sshd_config_BAK

# Install rtinst
bash -c "$(wget --no-check-certificate -qO - https://raw.githubusercontent.com/arakasi72/rtinst/master/rtsetup)"

# Run rtinst
sudo -u $USER sudo -i -- rtinst -l # Enable logging

# backup rtinst ssh config and set old backup as ssh config
cp /etc/ssh/sshd_config /etc/ssh/sshd_config_RTINST_BAK
mv /etc/ssh/sshd_config_BAK /etc/ssh/sshd_config

...


Publish 10.20, 11.15, 13.6 and 14.2 images [release]

Added an empty commit with release messaging to trigger push-images.sh in the configuration to address #44

@JalexChen  Instead of doing Adam, Mike, and myself individually, you can do @CircleCI-Public/images


AppNotificationContentBuilder API

This has now been replaced by: https://github.com/microsoft/WindowsAppSDK/pull/2648
closing...


Question about local repositories support

Hi,
with the Keil uVision pack manager the packs are by default installed in the packs directory.
In my setup, this is:
C:\Keil_v5\ARM\PACK
But the pack installer also works with "local repositories".
I mean that I can indicate a folder containing a pdsc file and the required artefacts and this supersedes a similar pack definition in the root directory.
Does cmsis-pack-manager support the same "local repositories" feature ?
Or is it only working with the root directory and ".pack" files ?
Thanks & Regards,
Fred

At the moment, CPM only supports its own pack repository containing .pdsc files and .packs under subdirectories for the vendor and pack name. Later today I'll document structure this in a wiki page and reference it here.
CPM may very well not support your use case right now… But the goal is for it to be a common command-line tool for managing CMSIS-Packs. That's why I added #157. I'd like to document your use case in that issue.

At the moment, CPM only supports its own pack repository containing .pdsc files and .packs under subdirectories for the vendor and pack name. Later today I'll document structure this in a wiki page and reference it here.
CPM may very well not support your use case right now… But the goal is for it to be a common command-line tool for managing CMSIS-Packs. That's why I added #157. I'd like to document your use case in that issue.

Thanks for the clarification and the #157 issue.

Thanks for the clarification and the #157 issue.


SPFx Webpart Lifecycle.

Hi Team,
Please provide information on the life cycle events.

SPFx webpart
SPFx webpart when react control is added

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

ID: 6c25a90e-829c-b436-d8ab-f9c010588ee1
Version Independent ID: 768fa9a1-2375-fb5a-be58-cb66320cc789
Content: Build your first SharePoint client-side web part (Hello World part 1)
Content Source: docs/spfx/web-parts/get-started/build-a-hello-world-web-part.md
Product: sharepoint
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

What exactly are you looking for? The page lifecycle doesn't really apply here.
Once SPFx is loaded, it starts to initialize all the web parts on the page, indicated by the OnInit() event. Then when it's time to paint the web part on the page, the render() method is called.
React web parts aren't special as they are added to the page from within the render() method by using React.render(htmlElement, reactComponet). From there, the React component life cycle applies.

I'm new to SPFx and want to create a webpart with webpart custom properties (PropertyPaneConfiguration). As on-premise webpart has life cycle event OnInit(), LoadViewState(), CreateChildControls(), OnLoad(), OnPreRender(), Render().
So similar to them I want to configure the webpart, read and perform operation on properties at the runtime. I want to relate the SPFx webpart implementation to the classic webpart stytle.
Please provide more details on this with code snippet.

Most of those are things that apply to the server-side ASP.NET page lifecycle & don't translate to the client-side. The only two that really apply to client-side are OnInit() (which does the same... it runs when your web part is being initialized) & Render() (which does the same thing).
The others, CreateChildControls(), OnLoad(), & OnPreRender() don't translate to client-side. You can always hook into the DOM page events... nothing special with SPFx.
But for what you're doing, it might be best if you run through this doc to see how custom properties & the property pane work. There are also some basic training materials here: http://aka.ms/spfx-training
Then ask questions if things aren't making sense.

@andrewconnell thanks for the help.

I am getting an error about the OnInit vs OnRender with the footer example web part in SPFX.
https://github.com/SharePoint/sp-dev-fx-extensions/blob/master/samples/react-application-regions-footer/src/extensions/yammerFooter/YammerFooterApplicationCustomizer.ts
 public async onInit(): Promise<void> {     Log.info(LOG_SOURCE,Initialized ${strings.Title}`);
// Added to handle possible changes on the existence of placeholders
// this.context.placeholderProvider.changedEvent.add(this, this._renderPlaceHolders);
// this.context.application._layoutChangedEvent.add(this, this._layoutChanged);

// Retrieve the menu items from taxonomy
Log.info(LOG_SOURCE, `Creating instance of SPTermStore.SPTermStoreService`);
Log.info(LOG_SOURCE, `spHttpClient: ${this.context.spHttpClient}`);
Log.info(LOG_SOURCE, `siteAbsoluteUrl: ${this.context.pageContext.web.absoluteUrl}`);
let termStoreService: SPTermStore.SPTermStoreService = new SPTermStore.SPTermStoreService({
  spHttpClient: this.context.spHttpClient,
  siteAbsoluteUrl: this.context.pageContext.web.absoluteUrl,
});

Log.info(LOG_SOURCE, `SourceTermSetName: ${this.properties.SourceTermSetName}`);
this._bottomMenuItems = await termStoreService.getTermsFromTermSetAsync(this.properties.SourceTermSetName);

// Call render method for generating the needed html elements
this._renderPlaceHolders();

return Promise.resolve<void>();

}`
This example only has OnInit, but calls render placeholder. I noticed when I navigate to subpages I get an error, most likely because the page is not redrawing correctly. Is the above code best practice, or should it be adjust with an onRender?


Add instructions for Debian based linux distributions

Thanks for the PR.
Question: What is wrong with the existing instructions in the README? Installing in $BASH_COMPLETION_USER_DIR (defaulting to ~/.local/share/bash-completion) is the defacto way to install local completions for all linux OSes. This is even specified in the bash-completion README.
Did this not work for you?

Cool and thanks for your time reviewing it.
I never managed to install correctly bash-completion on my machine. So the instructions are for installing without bash-completion.

How would this work without bash-completion installed?

On Fedora 31, according to the config file found in /etc/profile.d/bash_completion.sh, the user directory to target is ${XDG_CONFIG_HOME:-$HOME/.config}/bash_completion

@Nabellaleen See the third "Q" in this list: https://github.com/scop/bash-completion#faq

Indeed, it works well on .local/share/bash_completion but not in .config

I can confirm that the default instructions in the README did not work in Ubuntu 20.04 (threw an error: Failed writing body), whereas these instructions worked.
One extra step was required for me, though: I had to add source ~/.bash_completion to my ~/.bashrc.
(Thanks for writing this tool! :smile:)


Make Vector4/i properties show in 2x2 layout

Vector4 version of #45713
Before:

After:

With link:

This is going to be especially relevant for Vector4i properties after #79021
It also allows to unify Rect and Vector editor properties.

What about Plane?
I think the other one went through more easily because xy and hw are separate concepts, but here xyzw are just positions in identical dimensions

What about Plane?

Looks like another duplicate property 🙄
I can unify it together with Rect properties and it will get 2x2 layout for free.

I think the other one went through more easily because xy and hw are separate concepts, but here xyzw are just positions in identical dimensions

The original PR was about having more space, I never considered the concepts. Vector4 didn't exist then and I don't use Plane, so I didn't know it also has this problem.

A vector4 doesn't naturally have a 2x2 structure like a transform 2d has. Can you explain this change?

See https://github.com/godotengine/godot-proposals/issues/2237

I'm not totally sure about this. Especially when I work with shaders a lot with many vec3, vec4 and mat4 types I feel this  can make the UI a bit more confusing. Keeping all vector values in one row  (except for weirdo Vector2) makes eyeballing the UI easy and there is a visual difference between vectors and matrices. Making Vector4 take two rows makes it easy to mistake for a matrix.
And if Vector4 takes too much space horizontally, what should mat4 or Projection look like? It also takes four slots horizontally right now and it's hard to image how the new layout would look like without breaking the currently 1-to-1 visual to data mapping.

I think this should be tied to another editor setting like interface/inspector/horizontal_vector2_editing and interface/inspector/horizontal_vector_types_editing, although it's really pushing it. The latter is also a "lie" if this PR displays it this way regardless of the setting.

I think it would be confusing to add this for Vector4, but I'm not strongly attached to that position.


I cannot  implement RenderItem?

I create file RenderSprite.java and cannot implement RenderItem from file Box2DCamera.java

my best guess is that you have to implement Box2DCamera.RenderItem instead of just RenderItem
e.g.: public class Foo implements Box2DCamera.RenderItem {}

my best guess is that you have to implement Box2DCamera.RenderItem instead of just RenderItem
e.g.: public class Foo implements Box2DCamera.RenderItem {}

Okay.  Fix success. Thank you


codesandbox.io examples does not work

https://react-dnd.github.io/react-dnd/examples/dustbin/single-target
Not Found
We could not find the sandbox you're looking for.

Same for multiple targets, etc

Oh, i tried again and it works. Weird.

The examples can also be found on Github if needed under examples_decorators and examples_hooks.


chore(STONEINTG-758): deprecate old ver of deprecated-image-check

v1 and v2 of deprecated-image-check are deprecated (for real now) and after deprecation date EC will start failing build verifications.

Look for any open pull requests in the repository with the title "e2e-tests update" and
see if there are recent e2e-tests updates that will be applicable to your change.

/retest

/retest

/retest


CUDA and cUDNN version compatability for tensorflow 2.17.0?

Issue type
Build/Install
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
2.17.0
Custom code
Yes
OS platform and distribution
Windows 10
Mobile device
No response
Python version
3.9
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
I wanted to check what is the cuda and cUDNN version compatibility required for tensorflow 2.17.0?
Standalone code to reproduce the issue
I wanted to check what is the cuda and cUDNN version compatibility required for tensorflow 2.17.0?

Relevant log output
No response

Hi @prajsri99 ,
Thank you for raising your concern here. GPU support on native-Windows is only available for 2.10 or earlier versions, starting in TF 2.11, CUDA build is not supported for Windows. For using TensorFlow GPU on Windows, you will need to build/install TensorFlow in WSL2 or use tensorflow-cpu with TensorFlow-DirectML-Plugin. This is clearly mentioned in the documentation, so please review it for further details.
Thank you!


Documenter Completion Popup Should Close When Switching Tabs

Video: https://cdn.discordapp.com/attachments/737255889517543545/753658590266392706/popup_stays.mov

It does now.


[cudapoa] changing variables related to dimension of POA arrays from uint16_t to template type

many data structures defined in cudapoa_kernels.cuh associate with dimensions of score matrix, graph or reads sequence lengths. Dimension of cudapoa input was initially limited by uint16_t or int16_t types because of these data structures. Now those structures are templated and switch to 32-bit integer when needed.
Initial measurements indicated keeping data type to int32_t all the time has up to 20% degrading effect on the performance in cudapoa_benchmarks, therefore it has been changed to template type to switch to 32-bit only when needed.

This PR affects changes requested in #299

@tijyojwad do you know what are the CI errors about? I could not relate them to the recent changes.

@r-mafi looks like a conda package install issue in the job, unrelated to your changes. Rerunning tests now to see if that fixes the issue

rerun tests


Invitations REST API

[x] create invitation
[x] get invitation
[ ] modify role only
[ ] accept
[ ] decline
[ ] cancel

From what I understood in discussions, it is fair to target /api/communities/<pid_value>/invitations[/<invitation_id>] as the endpoint for all of those in the end (even actions/accept ...). If that's not the case then it may just be a question of moving functionality into invenio-requests.


Organize plug-ins install docs in manageable way

In each plug-in article, the install process is duplicated. As we add more plug-ins, it can be difficult to keep all installations in sync. Consider refining a single "Install Plug-ins" page and removing install procedures from each plug-in article. Some initial thoughts on how to address this (not a mandate, just ideas):

Remove installation section from each individual plug-in doc. Leave a heading that links to new "Install Plugins"
Create a single page with the procedure that covers installation  (Db2 is a special case that might warrant leaving its installation section in place)
- Add a table that supplies the tag usage
Each plug-in doc is more of an overview/usage guide at this point (overview, profiles, commands). consider naming the entire section accordingly.

Another thought - do we need the level of detail regarding profiles in each doc? It's currently just duplicating information that can be found in the CLI. Do we have real world examples of anyone finding this Profiles section in plug-in docs useful?

Absolutely good points. I agree with all of them, and we can propose this change in future. Let me think on a new structure of the plug-in docs, and I should get back to you.
Now as for your questions:

Profile details issue - this was in place, because of different rules as to the necessity of creation of profile. Maybe we can transpose this section to the general (unified) doc on how to install plug-ins, so that it doesn't appear in the overview/usage plug-in articles.
Maybe, but not that I know of. To figure this out, we can sync with POs/PMs

@IgorCATech
I think for now, we can keep profile sections in each plug-in article, and keep them very simple. I don't really think it's that useful to show the output from the command, or anything like that. IMO, the level of detail in the profile section here is appropriate and useful - https://zowe.github.io/docs-site/latest/user-guide/cli-cicsplugin.html#installing-from-a-local-package   more detailed info can be found in the help, as @JamesBauman mentions.


Diagnostics: Parsed headers are printed as a whole

In the parsing phase, all parsed header paths are printed at the end.
Is there a way to make it print each one by one so we can visualize the progress in the console?

Suppose parsing 2 files: test1.h, test2.h.
The output on the console is like:
Parsing libraries...
Parsing code...
Parsed 'Test1.h, Test2.h'

And Parsed 'Test1.h, Test2.h' is printed only after both files are parsed, my question: is there a way to print when each file is parsed?
Imagine parsing a module with multiple files which can take much time to complete, can we show when each file is parsed?

Need to investigate more, but maybe when I get the project built from source because for now I am having difficulty running build.sh. For now I am relying on the nuget package.
Thanks.


v0.14.0-alpha endgame

DRIs

DRI

Endgame
@ewgenius

QA
@y-f-u

Docs
@digadeesh

Comms
@karifabri

Milestone Release Timeline

Date
Description

Planning
Mon, June 3

Release
Mon, June 3

Announcement
Tue, June 4

Planning Checklist

[x] Review the specific GitHub Milestone

Release Checklist

[ ] All outstanding spiceai feature PRs are merged @ewgenius
[ ] Full test pass and update if necessary over README.md (please get screenshots!) @y-f-u
[ ] Full test pass and update if necessary over Docs (please get screenshots!) @digadeesh
[x] Full test pass and update if necessary over existing and new Samples (please get screenshots/videos!) @y-f-u
[ ] Full test pass and update if necessary over existing and new Quickstarts (please get screenshots/videos!) @y-f-u
[x] Merge Docs PRs @digadeesh
[ ] Merge Registry PRs @ewgenius
[ ] Merge Samples PRs @ewgenius
[ ] Merge Quickstarts PRs @ewgenius
[ ] Update release notes @ewgenius
[ ] Update acknowledgements by triggering Generate Acknowledgements workflow @ewgenius
[ ] Verify version.txt and version in Cargo.toml are correct using docs/RELEASE.md @ewgenius
[ ] Ensure E2E Test CI is green on trunk branch @ewgenius
[ ] QA DRI sign-off @y-f-u
[ ] Docs DRI sign-off @digadeesh
[ ] Create a new branch release-v[semver] and merge all relevant changes into it. E.g. release-v0.9.1-alpha@ewgenius
[ ] Release the new version by creating a pre-release GitHub Release with the tag from the release branch. E.g. v0.9.1-alpha@ewgenius
[ ] Release any docs updates by creating a v[semver] tag. @ewgenius
[ ] Trigger algolia search crawler workflow, to reindex updated docs. @ewgenius
[ ] Update the Helm chart version (image.tag version & chart version). Ensure docker build for the tag from the release branch completed (~2 hours) and trigger the Release Chart workflow. @ewgenius
[ ] Final test pass on released binaries @ewgenius
[ ] Run E2E Test Release Installation @ewgenius
[ ] Update version.txt and version in Cargo.toml to the next release version. @ewgenius
[ ] Update versions in brew taps @ewgenius
[ ] Remove the released version from the ROADMAP @ewgenius

Announcement Checklist

[ ] X: @spice_ai
[ ] Reddit: reddit.com/r/spiceai
[ ] Discord: #announcements
[ ] Telegram: spiceai
[ ] Blog: blog.spiceai.org

PR reference

PR 1.
PR 2.
etc.

Test:

[ ] MotherDuck @digadeesh
[ ] GraphQL @ewgenius
[ ] Caching changes @y-f-u


No autofocus with rpiCamera source and rpiCameraAfMode: auto

Which version are you using?
v1.0.3
Which operating system are you using?

[ ] Linux amd64 standard
[ ] Linux amd64 Docker
[ ] Linux arm64 standard
[ ] Linux arm64 Docker
[ ] Linux arm7 standard
[ ] Linux arm7 Docker
[x] Linux arm6 standard
[ ] Linux arm6 Docker
[ ] Windows amd64 standard
[ ] Windows amd64 Docker (WSL backend)
[ ] macOS amd64 standard
[ ] macOS amd64 Docker
[ ] Other (please describe)

Describe the issue
Autofocus mode auto with rpiCamera source doesn't seem to work i.e.: setting rpiCameraAfMode to auto doesn't achieve focus. I'm using a Raspberry Camera Module 3 connected to a RPi Zero W. Setting rpiCameraAfWindow to something like 0.25,0.25,0.5,0.5 didn't change anything. Using manual focus and setting the lens position works however and so does the continuous setting.
Server logs don't show anything suspicious.
Versions:
OS: Raspbian GNU/Linux 11 (bullseye)
libcamera: v0.0.5+83-bde9b04f
libfreetype6: 2.10.4+dfsg-1+deb11u1
Describe how to replicate the issue

Start server with the following configs:

logLevel: debug
logDestinations: [syslog]
rtsp: yes
protocols: [tcp]
rtspAddress: :554
rtmp: no
hls: no
webrtc: no
srt: no

paths:
  live:
    source: rpiCamera
    rpiCameraCamID: 0
    rpiCameraWidth: 1280
    rpiCameraHeight: 720
    rpiCameraHFlip: False
    rpiCameraVFlip: False
    rpiCameraBrightness: 0.0
    rpiCameraContrast: 1
    rpiCameraSaturation: 1
    rpiCameraSharpness: 0
    rpiCameraExposure: auto
    rpiCameraAWB: auto
    rpiCameraDenoise: "cdn_off"
    rpiCameraShutter: 0
    rpiCameraMetering: centre
    rpiCameraGain: 0
    rpiCameraEV: 0
    rpiCameraHDR: false
    rpiCameraFPS: 30
    rpiCameraIDRPeriod: 60
    rpiCameraBitrate: 2000000
    rpiCameraProfile: main
    rpiCameraLevel: '4.1'
    rpiCameraAfMode: auto
    rpiCameraAfRange: normal
    rpiCameraAfSpeed: normal
    rpiCameraLensPosition: 0

Connect with VLC to rtsp://<SERVER_IP>:554/live

Did you attach the server logs?

no
Did you attach a network dump?

no

one up for this, I have the same problem

Hello, in order to control the RPI camera, the server uses the same API behind libcamera-vid.
Try using libcamera-vid with --autofocus-mode and --autofocus-window and post the results here.
If autofocus works with libcamera-vid, then there's a bug inside the server that can be solved, otherwise it's an issue that should be reported to libcamera maintainers.

That's Fair enough, I will try as soon as I can

I made a mistake and wrote continous instead of continuous. Continuous auto focus does indeed work given the parameter is written correctly.
However, auto does not. It works fine with libcamera-vid (achieves focus on start and keeps it) whereas MediaMTX doesn't focus at all.

Agreed, same behavior observable here. Camera Module 3 + PI 4

Same here. Using  rpiCameraAfMode: manual and rpiCameraLensPosition: 0.0 does not prevent from auto focus. Camera Module 3 with RP 2w zero

i took another look at the sample libcamera apps and i found out that auto focus needs an initial scan, that was not triggered. Please try this nightly release and let me know if it fixes the issue.
@kanehekili your issue is off topic here, please open another issue and provide details on how to replicate.
mediamtx_v1.2.0-6-gefd9001_darwin_amd64.tar.gz
mediamtx_v1.2.0-6-gefd9001_darwin_arm64.tar.gz
mediamtx_v1.2.0-6-gefd9001_linux_amd64.tar.gz
mediamtx_v1.2.0-6-gefd9001_linux_arm64v8.tar.gz
mediamtx_v1.2.0-6-gefd9001_linux_armv6.tar.gz
mediamtx_v1.2.0-6-gefd9001_linux_armv7.tar.gz
mediamtx_v1.2.0-6-gefd9001_windows_amd64.zip

@aler9 Your nightly release does indeed fix this issue, thank you for working on it!

added in v1.2.1


How to choose order of JS imports?

Apologies if this is a n00b question.
Restangular depends on lodash. I tried adding Restangular to a fork of this project, but couldn't figure out how to get lodash to be ahead of Restangular in the final main.js, so keep getting an error.
Uncaught Error: [$injector:modulerr] Failed to instantiate module app due to:
Error: [$injector:modulerr] Failed to instantiate module restangular due to:
ReferenceError: _ is not defined

or if I try to import it and add it to requires:
Uncaught Error: [$injector:modulerr] Failed to instantiate module app due to:
Error: [$injector:modulerr] Failed to instantiate module lodash due to:
Error: [$injector:nomod] Module 'lodash' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.

Of course it works fine if I just just a CDN lodash and ignore the bower one. Any tips? Is this a debowerify issue? Where would I specify the ordering?

Can you provide an example of how you're importing lodash and restangular, and how you're injecting them (if at all) into the app?

I've had the same problem, which I've patched by manually loading it in the
order it requires on the page.
Would be nice to handle it as all other modules.
On Sat, Dec 19, 2015, 04:58 Jake Marsh<EMAIL_ADDRESS>wrote:

Can you provide an example of how you're importing lodash and restangular,
and how you're injecting them (if at all) into the app?
—
Reply to this email directly or view it on GitHub
https://github.com/jakemmarsh/angularjs-gulp-browserify-boilerplate/issues/130#issuecomment-165943633
.

@jakemmarsh I added lodash and restangular, in that order, with import statements and to requires in app/js/main.js. (have tried many variants on this with no luck, but maybe there is some trick I'm missing).

I just saw this comment in a related thread and wondered if it is relevant here:
http://stackoverflow.com/questions/14968297/use-underscore-inside-angular-controllers
"its necessary when you add 'use strict' to your file. Since underscore/lodash isn't defined it will throw ReferenceError: _ is not defined... you have to inject it, or use window._"

Did anyone manage to resolve this issue in their project other then using CDN?
I'm trying to do the same slick-carousel needs jquery to be injected before angular, but I can't get it to work using just imports...

Ok so this finally did the trick: https://github.com/StrikeForceZero/acgb-boilerplate-shim-example, which I found in this issue: https://github.com/jakemmarsh/angularjs-gulp-browserify-boilerplate/issues/148


Cannot install with Prisma 2.21.1

When trying to install casbin-prisma-adapter on a fresh project, I'm hit with the following error output from Prisma:
npm ERR! code 1
npm ERR! path /Users/jack_barry/repos/playground-prisma/node_modules/@prisma/cli
npm ERR! command failed
npm ERR! command sh -c node scripts/preinstall-entry.js
npm ERR! ┌─────────────────────────────────────────────────────────────────────────────┐
npm ERR! │                                                                             │
npm ERR! │     The package @prisma/cli has been renamed to prisma.                     │
npm ERR! │                                                                             │
npm ERR! │     Please uninstall @prisma/cli first.                                     │
npm ERR! │     Then install prisma to continue using Prisma CLI:                       │
npm ERR! │                                                                             │
npm ERR! │         # Uninstall old CLI                                                 │
npm ERR! │         npm uninstall @prisma/cli                                           │
npm ERR! │                                                                             │
npm ERR! │         # Install new CLI                                                   │
npm ERR! │         npm install prisma --save-dev                                       │
npm ERR! │                                                                             │
npm ERR! │         # Invoke via npx                                                    │
npm ERR! │         npx prisma --help                                                   │
npm ERR! │                                                                             │
npm ERR! │     Learn more here: https://github.com/prisma/prisma/releases/tag/2.16.0   │
npm ERR! │                                                                             │
npm ERR! └─────────────────────────────────────────────────────────────────────────────┘

I think that the dependency of @prisma/cli is causing this.
If I try to install @prisma/cli directly it gives similar errors. This happens because of the preinstall.js script that gets run as part of the preinstall script from the package.json of @prisma/cli
Have confirmed that if I build and pack casbin-prisma-adapter locally after removing the peerDependency of @prisma/cli, the issue is no longer present on install. Would removing that as a peerDependency be particularly harmful?

@Zxilly

Thanks!

@Jack-Barry @Zxilly can we just update the @prisma/cli pkg to latest version to fix this issue?

@hsluoyz It looks like the latest version of the @prisma/cli package includes the preinstall script that prevents it from being installed, to guide users to installing the prisma package instead. So if anything the version of @prisma/cli would probably have to be locked at an older version to continue using/installing it.
It looks like the fix proposed in #23 does what's needed (switches the dependency/peerDependency to prisma)

@Jack-Barry released: https://www.npmjs.com/package/casbin-prisma-adapter/v/1.0.2

@hsluoyz That worked a treat, thanks for the quick update and release


Standalone: Group inverted index operations in batch put

At the moment we're seeing long write times at larger index sizes for the inverted index. Long-term we should probably move to a segmented approach, similar to how it's done in Lucene.
As a short-term performance boost we could try to group all writes in a batch and then write them to disk in one go. This will potentially safe hundreds of read/write cycles on very frequent inverted index items, such as stopwords and very common words.
In theory this might make larger batch sizes more efficient than smaller sizes.

Not closing yet, as investigating this should be done before finally closing it, but moving it to the Performance milestone, as any change done in here would be non-breaking to a user.

Finally tried this out as part of the implementaiton for #1334. As predicted the benefit is not huge, but there was some meassurable benefit and we basically go this for free, since I had to build the implementation for #1334 anyway, where the difference was quite noticable.


Disable clock test on backdeploy concurrency lib

Clocks don't work with back deploy.
I'm not sure if we still need the unsupported backdeploy runtime, or if the unsupported back deploy concurrency is sufficient?

@swift-ci please smoke test


Replace print statements with proper logging

This PR:

Introduces the usage of the logging standard module
Adds a top-level convenience function typhon.set_loglevel() to control the logging level
Replaces (almost) all calls of the print() function with the appropriate logging function
Add information for developers on how to create log messages

In general, Typhon should not print any messages to stdout by default. To restore output, you can set the logging level by using the standard module
logging.basicConfig(logging.INFO)

or the Typhon convenience function
typhon.set_loglevel(logging.INFO)

Cheers,
Lukas

In addition:

remove an outdated backup file
fix a bug in the DopplerWind class (switch between 'red' and 'blue' shift did not work)

Good initiative! I will have a look into this next week!

Okay, thanks! I tried to minimise the changes to your code and mainly used your existing logging mechanisms. It's up to you, if you want to refactor it even more 😉


useNavigate not working correctly

Describe the bug
What is supposed to happen ? What is happening instead ?
When trying to invoke useNavigate in a story, the path is being appended to the original path instead of updating the path param.
For example, with the following meta, the story loads with a path of '/pokemon/1':
const meta = {
    component: PokemonPage,
    decorators: [withRouter],
    parameters: {
        reactRouter: reactRouterParameters({
            location: {
                pathParams: {id: '1'},
            },
            routing: {path: '/pokemon/:id'}
        }),
    },

} satisfies Meta<typeof PokemonPage>;

But when trying to update with use navigate like below:
 const {id} = useParams();
    const navigate = useNavigate();

    const [tabIndex, setTabIndex] = useState(0);

    const [{data, loading}, refetch] = useAxios<{ pokemon: Pokemon[] }>(
        '/api/v1/pokemon?pageSize=1500'
    )

    const handlePrev = () => {
        if (id && (parseInt(id) - 1) > 0) {
            navigate((parseInt(id) - 1).toString())
        }
    }

    const handleNext = () => {
        if (data?.pokemon && id && (parseInt(id) - 1) < data?.pokemon.length - 1) {
            navigate((parseInt(id) + 1).toString())
        }
    }

    const handlePokemonSelect = (index: number) => {
        navigate((index + 1).toString())
    }

it is just appending the updated id to the end of the path, like '/pokemon/1/2' which the router cannot find.
To Reproduce
Describe all the steps required to reproduce the issue.
See above code
To help us resolve your issue more quickly, please fork the [https://stackblitz.com/edit/storybook-addon-remix-react-router](stackblitz project) to reproduce your issue.
Additional context
Add any other context about the problem here.
Environment
Share the output of the following command :
npx sb info

Storybook Environment Info:

  System:
    OS: macOS 14.1
    CPU: (11) arm64 Apple M3 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.18.2 - ~/.nvm/versions/node/v18.18.2/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 9.8.1 - ~/.nvm/versions/node/v18.18.2/bin/npm <----- active
  Browsers:
    Chrome: 130.0.6723.91
    Safari: 17.1
  npmPackages:
    @storybook/addon-essentials: ^8.3.6 => 8.3.6
    @storybook/addon-interactions: ^8.3.6 => 8.3.6
    @storybook/addon-links: ^8.3.6 => 8.3.6
    @storybook/addon-onboarding: ^8.3.6 => 8.3.6
    @storybook/blocks: ^8.3.6 => 8.3.6
    @storybook/react: ^8.3.6 => 8.3.6
    @storybook/react-vite: ^8.3.6 => 8.3.6
    @storybook/test: ^8.3.6 => 8.3.6
    eslint-plugin-storybook: ^0.10.1 => 0.10.1
    msw-storybook-addon: ^2.0.3 => 2.0.3
    storybook: ^8.3.6 => 8.3.6
    storybook-addon-remix-react-router: ^3.0.1 => 3.0.1

@JacobPotter Can you please provide a stackblitz with both the app implementation and the storybook ? So we can witness the difference in behavior ?


setting active text editor with url parameter.

Is it possible to pass parameter like &fileToOpen=index.js to url to open this file in editor?

this concerns upstream, please tell @microsoft about your feature request, thanks!

@fanixus96 this is a good idea. Maybe it can be done via extension?

But right now Im able to close editor and after refresh this editor will be opened. I have found https://github.com/cdr/code-server/issues/801 but I cant find file saved on localStorage? Where are you saving this configuration? I can t find where it is triggered.

There should be a JSON file in ~/.local/share/code-server/state that
contains information about open editors and so on.


Cannot access railsContext in components

Congratulation for the great work on react_on_rails!  👍
I have just started trying it out. I am facing an issue where I cannot access the railsContext in the constructors of my components. It is always an empty Object {}.
Tracking down the stack brings me to node_package/src/createReactElement.js, because my component is a react component and not a generator function that returns one, it uses React.createElement(component, props) thus, discarding the railsContext.
export default class NavigationBar extends React.Component {

  constructor(props, _railsContext) {
    super(props)

    console.log(_railsContext) // Object {}
  }
  ...
}

import ReactOnRails from 'react-on-rails'
import NavigationBar from '../containers/navigation-bar'

ReactOnRails.register({
  NavigationBar
})

  <body>
    <%= react_component 'NavigationBar' %>
    ...
  </body>

What am I doing wrong ?

Hi @othierry, the docs specify your answer. You need to use a generator function.
https://github.com/shakacode/react_on_rails/blob/master/README.md#rails-context


ENFILE, file table overflow

Hey Guys,
This is really just a question, i can't seem to find help anywhere how to debug this.

I am on Yosemite. Guessing it has something to do with that, since it never happened the previous year on my mac.
I have ran everything in --verbose to verify i am not globbing node_modules or anything i wasn't expecting. What i am trying to figure out is how many files are currently being watched, to see if there is some leak that --verbose doesn't help me with.
Is there a terminal command or any way to see the number of open files? I used to get the "to many files opened" but i have upped that limit extremely high with ulimit. Now i don't get that, just this "ENFILE table overflow" guy.
All this issue really is is for any help in how i can debug whats going on, i have searched so many posts already i keep rounding back to already visited ones 3, 4 times lol.
Thanks for this library. It is night and day how useful this tool you guys have built is, thank you!

I am facing the same issue ,Do you have any solution on this?


Blockrain Activity : UI Issue

Hey @llaske
I have found the UI issue in the Blockrain activity when we hover on the rotate button it is not properly aligned as all other buttons are properly aligned.
For reference I have attached screenshots for the same, please look and review them and give me your thoughts.

Yes you're right it could be improve.


dist/renderer/styles/app.css not found in /opt/Ramme/resources/app.asar

Built and installed on arch linux.
There is only an SCSS file in the asar.
Uncaught Exception:
Error: ENOENT, dist/renderer/styles/app.css not found in /opt/Ramme/resources/app.asar
    at notFoundError (ELECTRON_ASAR.js:115:19)
    at Object.fs.readFileSync (ELECTRON_ASAR.js:513:9)
    at WebContents.page.on (/opt/Ramme/resources/app.asar/src/main/index.js:154:23)
    at emitOne (events.js:96:13)
    at WebContents.emit (events.js:191:7)

Same problem, with both the .tar.gz and the .pacman. Help?

After some basic research I think the issue might be of SASS files not getting compiled due a lack of libsass on arch, can anyone confirm you can do that?

@anatolinicolae What do I do, just try to build?

@anatolinicolae The PKGBUILD in the AUR package just downloads the .deb and extracts it. It doesn't compile anything.

@anatolinicolae There's no error anymore, whether I build the app with libsass installed or not. However, in both cases, the sidebar doesn't show up at all, and the only button at the bottom is the upload button. There's no way to access any other pages.

I tried building v3.2.3 - there's still no error either way, but the buttons are at the bottom, and there's space where the sidebar should be.

Sidebar Missing
Yeah, I removed the sidebar thing in the last release 'cause I didn't have enough time to fix it.
#275
Regarding the SASS assets, I decompressed myself the pacman package and found the same as reported before. Cannot actually tell where's the problem though. The build script builds assets once, then should package the same compiled assets into destination-specific packages, which doesn't seem to happen... 🤔

Can you guys try building the app with a little change? Try with dist/main instead of src/main in app/package.json and let me know if the final package works fine and loads correctly.

Just installed 3.2.5 via regular dmg and getting this error on launch (old Mac running Sierra). Everything seems to work fine after I dismiss it tho, so win.

Also getting this same message in ubuntu 14.04:

And after I quit out:

I'm getting the same issue on GalliumOS whether I install the deb using dpkg or build from source using yarn dist.

OS: Mint 18.3 sylvia
Kernel: x86_64 Linux 4.15.0-29-generic

Error at every startup on Ubuntu 18.04 after installing from amd64.deb:

Same with ubuntu 16.04 and Ramme_3.2.5_amd64.deb

same problem on windows 10 pro Ramme-Setup-3.2.5.exe  but the app run  normall after closing the dialog


Strange behvaviour, phantom button presses and scrolling on it's own

Thanks for taking the time for reporting an issue!
Describe what happened
Include any error message or stack trace if available.
We are having very strange behaviour since integrating Datadog into our app. Buttons are seemingly being pressed and views being navigated to with absolutely no human interaction.
We have only had this issues since integrating DataDog into our app
We upgraded from 1.0.0-rc5 after reading this issue: https://github.com/DataDog/dd-sdk-reactnative/issues/138
We are now on 1.0.0 as it sounded very similar to our issues. The buttons being pressed on their own are all either being passed to children or are callbacks to parent views. Some of the buttons fire navigation events.
"@datadog/mobile-react-native": "1.0.0",
"@datadog/mobile-react-navigation": "1.0.0",
I've completely disabled RUM from datadog, but we are still getting reports and commented out navigation tracking. We noticed that there are onPress handler overrides from the old 1.0.0-rc5 version in the mobile-react-navigation 1.0.0 code also. Unsure if this is related.
Steps to reproduce the issue:
We are unable to reproduce since 99% of the time the buttons and navigation work as expected, but have plenty of videos /reports of random buttons being pressed without interaction throughout the entire app. We are wondering if this is something you have seen or heard of? It is impacting our business heavily, and is not something I've seen prior to integration with Datadog.
Describe what you expected:

Hi @HannahCarney, thanks for reaching out!
We did not have any report of a similar issue so far.
It could be that the way you pass onPress to your components does not work well with our onPress interceptor (see its code at version 1.0.0 here: https://github.com/DataDog/dd-sdk-reactnative/blob/862d527a93e927774ecc2f3859848aa8422aa6dc/packages/core/src/rum/instrumentation/DdRumUserInteractionTracking.tsx).
Does the issue disappear if you disable User Interaction Tracking?
Could you share the code for one of the button that gets triggered unexpectedly to help us troubleshoot?
Thank you!

We have disabled interaction tracking completely but are still seeing the issue but we have noticed you have EventInterceptor code in both the mobile-react-native library and the mobile-react-navigation library? We have noticed the code is different between the two, and are not sure if by importing DdRumReactNavigationTracking we have still pulled in the event tracking there. We have noticed we are still getting RUM reports of ApplicationStart, and we get this twice for every session.
Here is the most heavily affected button because it's triggering random printouts (print button gets pressed randomly)
useEffect(() => {
return () => { setPrinting(false), clearTimeout(timer.current) };
}, []);
const printReceipt = () => {
if (printing === false) {
setPrinting(true);
Log.d([PRINT] PRINT_BUTTON_PRESSED ${orderId} )
orderActions.printOrder({
OrderId: orderId,
onFinish: () => {
if (isMounted) {
Log.d([PRINT] PRINT_BUTTON_STOP_CALLBACK ${orderId} )
//give it time to print
timer.current = setTimeout(() => {
setPrinting(false);
}, 1500);
}
}
})
}
}
return (

{!isFullyRefunded && (
<StyledButton
fdKey="refund-btn"
big
inverted
negative
onPress={() => {
navigation.navigate("RefundOrder", { OrderId: orderId });
}}
children="REFUND"
/>
)}

);
};
import React from "react";
import {
TouchableOpacity,
ActivityIndicator,
StyleSheet,
View
} from "react-native";
import StyledText from "./StyledText";
type Props = {
fdKey: string;
disabled?: boolean;
onPress: () => void;
children?: string;
inverted?: boolean;
loading?: boolean;
big?: boolean;
negative?: boolean;
};
StyledButton.tsx
const StyledButton: React.FC = (props: Props) => {
const {
children,
disabled,
onPress,
fdKey,
inverted,
loading,
big,
negative
} = props;
if (negative) {
return (
<TouchableOpacity
testID={fdKey}
accessibilityLabel={fdKey}
style={{
marginVertical: 8,
marginHorizontal: 16,
paddingLeft: 10,
paddingRight: 10,
backgroundColor: inverted ? "#ffffff" : "#ff426a",
flex: 1,
height: big ? 48 : 32,
borderRadius: 24,
justifyContent: "center",
alignItems: "center",
borderTopWidth: 0.25,
borderLeftWidth: 0.5,
borderRightWidth: 0.5,
borderBottomWidth: 2,
borderColor: "rgba(37, 65, 244, 0.1)",
opacity: disabled ? 0.2 : 1
}}
disabled={disabled}
onPress={onPress}
>
<StyledText
variant={big ? "title" : "subtitle"}
color={inverted ? "#ff426a" : "#ffffff"}
weight="medium"
numberOfLines={1}
text={children}
/>
{loading && (
<View style={[StyleSheet.absoluteFill, { justifyContent: "center" }]}>

)}

);
}
return (
<TouchableOpacity
testID={fdKey}
accessibilityLabel={fdKey}
style={{
marginVertical: 8,
marginHorizontal: 16,
backgroundColor: inverted ? "#ffffff" : "#203af2",
flex: 1,
height: big ? 48 : 32,
borderRadius: 24,
justifyContent: "center",
alignItems: "center",
opacity: disabled ? 0.2 : 1
}}
disabled={disabled}
onPress={onPress}
>
<StyledText
numberOfLines={1}
variant={big ? "title" : "subtitle"}
color={inverted ? "#203af2" : "#ffffff"}
weight="bold"
text={children}
/>
{loading && (
<View style={[StyleSheet.absoluteFill, { justifyContent: "center" }]}>

)}

);
};
StyledButton.defaultProps = {
disabled: false
};
export default StyledButton;

Hi @HannahCarney,
In the mobile-react-navigation we include the types for mobile-react-native as well as it depends on this package, so that's not something that could potentially create an issue as no code is actually there. Can you confirm this is the case for you as well?
Could you send the list of dependencies from your package.json to see if any one of them could interact with our SDK and create this issue?
Also I've seen reports of this bug happening when the Touchable component is inside a ScrollView, or other scrollable components from librairies:

https://github.com/satya164/react-native-tab-view/issues/1241
https://github.com/callstack/react-native-pager-view/issues/424

Could you specify if this is the case for this button?
Also if this is possible, can you share one video showing the issue?
If you don't want to share it here, you can also reach out to our support mentioning this issue and they will forward it to us.
Thanks a lot!

We just updated to 1.1.3 to try it out. Sadly we already found that bug and changed it to the gesture handler, but this didn't work, and it's not related because our button here is outside of scroll view. We get phantom presses on ones in scrollview and ones outside of it too.
"workspaces": {
"packages": [
"apps/",
"packages/"
]
},
"dependencies": {
"@datadog/mobile-react-native": "1.1.3",
"@date-fns": "",
"@logger": "",
"@formatjs/intl-datetimeformat": "^5.0.0",
"@formatjs/intl-getcanonicallocales": "^1.9.0",
"@formatjs/intl-locale": "^2.4.45",
"@formatjs/intl-numberformat": "^7.4.2",
"@formatjs/intl-pluralrules": "^4.3.2",
"@react-native-async-storage/async-storage": "~1.15.0",
"@react-native-community/datetimepicker": "4.0.0",
"@react-native-community/netinfo": "6.0.0",
"@react-native-community/slider": "4.1.12",
"@react-native-picker/picker": "2.2.1",
"@react-navigation/drawer": "6.4.1",
"@react-navigation/native": "6.0.10",
"@react-navigation/native-stack": "6.6.2",
"axios": "0.26.0",
"expo": "44.0.6",
"expo-application": "4.0.2",
"expo-av": "~10.2.0",
"expo-constants": "~13.0.1",
"expo-splash-screen": "~0.14.1",
"expo-status-bar": "~1.2.0",
"expo-updates": "~0.11.7",
"immer": "^9.0.12",
"moment": "^2.24.0",
"moment-timezone": "^0.5.27",
"react": "17.0.2",
"react-dom": "17.0.2",
"react-native": "0.64.3",
"react-native-android-open-settings": "^1.3.0",
"react-native-device-info": "~8.5.0",
"react-native-dotenv": "^3.3.1",
"react-native-elements": "3.4.2",
"react-native-gesture-handler": "~2.1.0",
"react-native-launch-arguments": "^2.0.1",
"react-native-modal": "13.0.1",
"react-native-notification-sounds": "0.5.4",
"react-native-reanimated": "~2.3.1",
"react-native-safe-area-context": "3.3.2",
"react-native-screens": "~3.10.1",
"react-native-signalr": "^1.0.6",
"react-redux": "8.0.1",
"redux": "4.2.0",
"redux-act": "1.8.0",
"redux-saga": "1.1.3",
"redux-thunk": "2.4.1",
"reselect": "4.1.5",
"rn-escpos": "",
"rn-sunmi": "",
"rn-runtime": "*"
},
"devDependencies": {
"@babel/core": "^7.12.9",
"@flipdishbytes/fe-toolbox": "file:flipdishbytes-fe-toolbox-v0.0.51.tgz",
"@testing-library/react-native": "^10.1.1",
"@types/jest": "27.5.1",
"@types/lodash": "4.14.182",
"@types/react": "17.0.21",
"@types/react-dom": "17.0.2",
"@types/react-native": "0.67.7",
"@types/react-redux": "7.1.24",
"@types/react-test-renderer": "18.0.0",
"@types/signalr": "2.2.37",
"babel-plugin-transform-remove-console": "6.9.4",
"jest": "^28.1.2",
"jest-expo": "^44.0.0",
"prettier": "2.5.1",
"react-native-flipper": "^0.137.0",
"react-test-renderer": "17.0.2",
"redux-devtools-extension": "^2.13.8",
"redux-flipper": "^2.0.1",
"redux-saga-test-plan": "4.0.5",
"typescript": "4.6.4"
},
"resolutions": {
"react": "17.0.2",
"typescript": "4.6.4"
}
}

Hi this happens for all components regardless of if we memo them or not, the app is currently only Android so I wouldn't know about that. Was unable to reproduce it with the android back button. All I can say that is similar between all the buttons where it happens is that they are all callbacks to a parent view. We have useCallback on some of them, and others have no useCallback, two of the buttons we see happening the most, have actions in them, but one just has a navigation route.

Hi @HannahCarney!
As there has been no activity on this issue for a while I'm going to close it.
Feel free to reopen it with more details if you still encounter the issue!


Update UI deps to latest and greatest

Added first smoke test
Ran prettier against codebase
Fix issue with welcome page

Signed-off-by: Tom Barlow<EMAIL_ADDRESS>

LGTM


Fix bug#1

#1

Coverage decreased (-0.4%) to 88.0% when pulling 08699f83511ca45e6eb099aab5c3e497ece80163 on arcondello:fix_bug#2 into 95ce25a4d82b44b02d5cd7590015a2918a33c819 on dwavesystems:master.

Coverage decreased (-0.4%) to 88.0% when pulling 08699f83511ca45e6eb099aab5c3e497ece80163 on arcondello:fix_bug#2 into 95ce25a4d82b44b02d5cd7590015a2918a33c819 on dwavesystems:master.

Coverage decreased (-0.4%) to 88.0% when pulling 08699f83511ca45e6eb099aab5c3e497ece80163 on arcondello:fix_bug#2 into 95ce25a4d82b44b02d5cd7590015a2918a33c819 on dwavesystems:master.


added profile, cv pdf and picture to this pr

I tried the build locally too but lmk if there any issues


CLI output should no longer say "preview endpoint" or "static"

Waiting (up to --wait-timeout=5m0s) for sandbox to be ready...
✓ Sandbox status: Ready: All desired workloads are available.

Dashboard page: https://app.signadot.com/sandbox/id/9df7wtlhn31h2

PREVIEW ENDPOINT    TYPE     URL
route-endpoint      fork     https://route-endpoint--sandbox-basic.preview.signadot.com
frontend-endpoint   static   https://frontend-endpoint--sandbox-basic.preview.signadot.com

The static value is coming from our API server. Should we hard-code the CLI to replace it with host, or is there still time to change the server-side response to say host for the V2 API?

We have time to change the API response. Should be fine to make such changes for a few more days IMO. Let's do it in the server would be my suggestion.


Display r2 and p-values of regression models

Done with 52e0aec
Decided not to include r2 since regressions are loess for which r2 doesn't make a lot of sense. p-values are now shown in plot subtitles


Add Desktop mode to valid MacOS Fullscreen modes

Description

Adds the current Desktop mode to the valid Fullscreen Modes (which makes sense, as being <= of the Desktop mode is the parameter for being a valid Fullscreen Mode).
MacOS fullscreen mode just takes the desktop mode and creates black borders around it to match the wanted resolution, in its current implementation. So this change is fully compatible.
The change also has the benefit of making it so there is always going to be a valid Fullscreen mode, unless a catastrofic error occurred.
I didn't add this line of code in the previous PR because I thought for sure the current Desktop mode would also be a Fullscreen mode. However, that doesn't seem to be guaranteed.
This PR is related to the issue #3330 .
Should be ported to master as well.
Tasks

[X] Tested on macOS

How to test this PR?
You probably need to set some intermediate HiDPI mode, like the user who reported the issue and tested the fix.
As for the code, look at issue #3330 .
I say probably because I couldn't experience this...

I did some more testing and can now clearly see that when you set your MacBook display to the highest resolution setting, the desktop resolution does not appear in the list of fullscreen modes. I'm not sure why this is, but this PR should address that.

SFMLBuildMaster: Build this please.


Added functionality to read armband info and subscribe to emg data

I needed the functionality to read armband info and EMG data. I found your npmjs module and wanted to keep it updated. There are tests still missing though.

@paintenzero I did some tests with your code and for some reason I can't explain, all four channels are logging the same data (see attached image) which makes no sense.

I took a look at the code and subscription to all four EMG characteristics is correctly implemented, therefore I don't know where the error might be.


docs: fix simple typo, interoperatibility -> interoperability

There is a small typo in windows/sodium/crypto_hash.h, windows/sodium/crypto_hash_sha256.h, windows/sodium/crypto_hash_sha512.h.
Should read interoperability rather than interoperatibility.

While this is true, the sodium library is a third party library. The master repo is here: https://github.com/jedisct1/libsodium


SavageWorlds-Tabbed - French translation and fix missing translation hooks.

Changes / Comments
French translation and bug fixes to enable translation where it was missing :

Updated French translation to 3.1 of SavageWorlds Tabbed sheet
Changed run button into a roll template to enable translation
Fixed a few broken i18n tags
Added i18n tags to places it was missing, and added translation entries in all the language files
(however I'm quite unsure about what to do with zu.js file)

Thank you Cassie for that merge !


chore: Prevent Asset Store Tools from being redistributed

#13
#12  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @AngelOnFira and the rest of your teammates on  Graphite


docs: Update metrics description

Fixes #N/A
Description
Updated metric description for karpenter_nodes_total_pod_requests and karpenter_nodes_total_pod_limits to include daemonSet pods.
How was this change tested?
NA
Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 79.224%

Totals

Change from base Build<PHONE_NUMBER>8:
0.0%

Covered Lines:
5960

Relevant Lines:
7523

💛  - Coveralls


Rename "PORT" definitions in the net tests and samples

This PR renames all local definitions with the name PORT in the net tests and samples, in order to prevent name conflict with certain HALs (notably, Atmel SAM E5x HAL).
An example of such a name conflict:
https://github.com/zephyrproject-rtos/hal_atmel/blob/1fe96f0a5e1a11d8101b258a3b84d35dc7178401/asf/sam0/include/same54/same54p20a.h#L949

I would also consider it a bug in the HAL if it uses too generic words which can easily lead to conflicts.

I agree, but I don't think Microchip would be willing to change this so easily -- we will see :) cc @nandojve

I would also consider it a bug in the HAL if it uses too generic words which can easily lead to conflicts.

I agree, but I don't think Microchip would be willing to change this so easily -- we will see :) cc @nandojve

It's far more easily re-write hal_atmel :D