typo: flowss -> flows

Docs Build status updates of commit b89d47a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/data-guide/relational-data/etl.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


fix: server-create allow create server with empty disk

这个 PR 实现什么功能/修复什么问题:
修正：允许创建kvm主机时，没有系统盘镜像，也没有cdrom
是否需要 backport 到之前的 release 分支:

release/2.10.0
release/2.11
release/2.12

/area region

/cc @wanyaoqi

Codecov Report

Merging #3106 into master will increase coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #3106      +/-   ##
=========================================
+ Coverage    7.17%   7.17%   +<.01%
=========================================
  Files         478     478
  Lines       76847   76848       +1
=========================================
+ Hits         5512    5514       +2
  Misses      70872   70872
+ Partials      463     462       -1

Flag
Coverage Δ

#aFlag
7.17% <0%> (ø)
:arrow_up:

Impacted Files
Coverage Δ

pkg/compute/models/guests.go
0.66% <0%> (ø)
:arrow_up:

pkg/mcclient/options/servers.go
0% <0%> (ø)
:arrow_up:

pkg/util/seclib2/seclib.go
95.74% <0%> (+4.25%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4356de5...619117d. Read the comment docs.

/approve
/lgtm


DRILL-5816: Hash function produces skewed results on String values wi…

…th same leading prefix
        Note: Changing hash32 computation to use Murmur3.hash32 instead of int casted version of Murmur3.hash64

@amansinha100 - Please help to review.

The change looks benign. I wonder; do we have a test case that exercises the hash functions so we can be certain that the fix actually solves the original problem?

@paul-rogers - I have added few tests and findings using hash32 and hash64 to compute the 32 bit hash codes in JIRA.

lgtm.  +1.  @sohami could you pls check with @chunhui-shi if unit tests were added previously for  DRILL-4237 (another skew issue)?  If not, could you create a new JIRA to add such tests, which should include the data set for DRILL-4237, DRILL-4119, DRILL-5816 among others.

I have created DRILL-5287 for adding tests.


Added missing grayscale flag in image provider

Contains the same change as #928, but includes README change as well
Closes #928

Duplicate of #928.


Linear Regression for Color.

Hi guys,
Can anyone please help me what is the correct way to use this library for Color Linear Regression.
I have two different rgb colors.
One is light grey:-
Expected RGB Values: [243, 243, 243]
Actual RGB Values: [233, 223, 231]
One is dark grey:-
Expected RGB Values: [85, 85, 85]
Actual RGB Values: [79, 77, 78]
I was using openCV in native iOS to get it working but now i moved to React Native and looking for this solution.
Here is the native code i used before to make it working:-
NSArray *patchColors = @[@[@233, @223, @231], @[@79, @77, @78]];
NSArray *greyColors = @[@[@243, @243, @243], @[@85, @85, @85]];

// Expected Log:-
a=3.948074, b=1.025974
a=1.671219, b=1.082192
a=4.450974, b=1.032680

// Get the Formula: y = slope*x + intercept

NSMutableArray * linearRegression(NSArray *patchColors, NSArray *greyColors) {

    NSUInteger count = [patchColors count]; // number of grey standards
    CvPoint * points=(CvPoint*)malloc( count * sizeof(points[0]));
    CvMat point_mat;

    NSMutableArray * result = [[NSMutableArray alloc] init];

    for(int channel=0; channel<3; channel++) { // 3 color channels
        for(int i=0; i<count; i++) {
            points[i].x = [ [ [patchColors objectAtIndex:i] objectAtIndex:channel] intValue];
            points[i].y = [ [ [greyColors objectAtIndex:i] objectAtIndex:channel] intValue];
        }
        float line[4];// to store the results
        point_mat = cvMat( 1, 2, CV_32SC2, points );
        cvFitLine(&point_mat,CV_DIST_L2 ,0,0.01,0.01, line);
        float slope = line[1]/line[0];
        float intercept = line[3] - slope*line[2];
        LinearPolynomial *formula = [[LinearPolynomial alloc] init];
        [formula setIntercept:intercept];
        [formula setSlope:slope];
        [result addObject:formula];
        printf("a=%f, b=%f \n", intercept, slope);
    }
    return result;

}

Thanks

This library is written in javascript, not objective-c. You will need to re-write the linear model.


[Tests] XFAIL IRGen/typed_throws_abi.swift on arm64e

rdar://139555118
This test fails on arm64e, because of expected differences in code gen, because of ptrauth.

@swift-ci smoke test


Possible to write to gist from a pwa?

The example heavily relies on
https://github.com/jonschlinkert/gists/blob/master/test/support/auth.js#L20
in order to work. Taking it out leads to 401 auth error from gist.
The problem is that this does not work on progressive web apps. It requires access to the user's file system as it relies on the fs module :(
My question is - any ways around this? What if I have a pwa that runs from the web browser?

The examples are using the test/support/auth.js file to create the options object to use when creating the instance of the Gists class and providing it with the GitHub authentication credentials.
The gists package itself does not directly use fs so you should be able to use this package in a web browser if you bundle it up with your other code. You'll have to authenticate with GitHub in some other way to get an access token or something, then you can use that to create the new instance of Gists:
// Using a `Bearer` token from GitHub
// This should be retrieved using a GitHub OAuth application webflow process as described in the GitHub API documentation
const gists = new Gists({ bearer: token });

You can also read public gists without using authentication credentials. See the Gists API documentation for more information around authentication.

the documentation is confusing. Is there an example out there with some pseudocode?
Does it only need the bearer key?

Can this be done in a simpler way by giving it an access token?

nevermind, it was simple:just do this instead
const gists = new Gists({ token: token });


[FEAT]

Is your feature request related to a problem? Please describe.
Would like more choices for offline system than VELOS and rSeries.
Describe the solution you'd like
Currently I only see VELOS and rSeries devices as offline destinations. Would it be possible to add addtional options like VE and iSeries Hardware and then select a TMOS version?
Describe alternatives you've considered
Looks like it will sort of work if I don't choose an Offline Destination BIG-IP it will read the destination it seems. I haven't done any testing if it just thinks every destination is F5OS based or not.
Additional context

Filed internal Jira SOLUTIONS-5766 (also same request as https://github.com/f5devcentral/f5-journeys/issues/47)

I will close this request as a duplicate of #47


flow-remove-types produces invalid JS after non-latin characters in comments

Flow version: 0.100.0
Expected behavior
Given the following input:
// @flow
// п
function foo(bar: number) {}

flow-remove-types should produce:
//
// п
function foo(bar        ) {}

Actual behavior
It produces invalid JS:
//
// п
function foo(bar:         {}

The non-latin character is the trigger. Without it, it works correctly. This seems like quite a serious bug considering how common it is to use non-latin characters in comments (e.g. comment in other languages, draw arrows etc.).
cc @mroch @samwgoldman

This seems to be a bug in flow-parser which produces incorrect range values in AST for non-latin characters. E.g. parsing // п and // n produces [0, 5] and [0, 4] ranges respectively, although both should be the same.

same root cause as #5793, I believe. the lexer reports its position in unicode codepoints, of which these are 1, but they are multibyte.

@mroch I believe it's a recent regression, because https://astexplorer.net/ (which uses Flow v0.94.0) shows identical AST for both cases ([0, 4]).

this is 0.94, when hovering over the FunctionDeclaration in the AST. so it's been there a while, but flow-remove-types regressed because it moved to flow-parser.

this appears to only be an issue with the range. the loc matches babylon.
it's a bit easier to see if you do it all on one line: https://flow.org/try/#0PQKk-CAsBmD2MNxA (see the AST tab). since it's all on line 1, the range should match the columns in loc.

@mroch ah, yeah, you're right. The link I commented earlier triggers the bug if you add a new line after the comment.

hrm i think we intentionally made range work like this. it's the byte offset in the file, which is what you'd want if you wanted to seek to read that part of the file from disk. but it's not what you'd pass to substring in JS, which is what tools like flow-remove-types do.

cc @nmote I think we should change range to match esprima and babylon, and potentially add (an option for) another field like byte_range or something. will need to figure out which tools need to be updated to use that.

https://github.com/facebook/flow/blob/a05cbb202197d57e5e909e11dcbb859f11c48641/src/parser/offset_utils.mli#L8-L30
... yup

Thanks for looking into this @mroch! Agreed about bringing Flow AST more in line with other parsers.
In the meantime, to fix the breaking bug with flow-remove-types sooner, should we just rewrite the logic so that it only depends on line/column, not range? I could take a stab at a PR.

alternatively, if it could work with UTF8 bytes instead of JS strings, that would make the existing ranges correct.
for example, perhaps changing flow-remove-types to use Buffers? I think the offsets of a Buffer are in bytes, not codepoints. modifying a buffer in place instead of lots of string concatenation could be a perf win too.
https://github.com/facebook/flow/blob/a05cbb202197d57e5e909e11dcbb859f11c48641/packages/flow-remove-types/index.js#L107

@mroch yep, will do!

We are running into the same problem, in our case with a ™ in a comment.
// @flow
import React from 'react';

/*
  This should Just Work™
*/
export const SomeComponent = (props: Object) => (
  <div {...props}>
    This breaks
  </div>
);

becomes
import React from 'react';

/*
  This should Just Work™
*/
export const SomeComponent = (props:=> (
  <div {...props}>
    This breaks
  </div>
);

Looks like it's been a few months now -- any updates on a fix?


Better, more persistent handling of logs

As discussed on #687, there is good reason to treat logfiles as akin to data generated by an analysis pipeline. Unfortunately, right now, the only options are to steal the logfiles from the clutches of the temporary job folders on the toil workers, or to grab truncated files that are stashed away in the jobstore. We should solve this scourge and help those betrayed by the log files that have dashed off into the sunset.

Just wanted to add a point to this. Being able to disable workdir cleaning is great, but oftentimes, I really want the logs, but I don't want the workdir, because the logs are orders of magnitude smaller than the workdirs, and my workdirs don't give me any additional ability to debug beyond my raw pipeline inputs.

Once we have export functionality which @JakeNarkizian is working on, we could use it to implement --exportLogsTo=s3://some-bucket/logs/

@fnothaft @hannes-ucsc what about an option to propagate the worker logs onto master in their own per job files? There is already a (broken) option to control the truncation of the worker log files, which would be easy for me to fix. Those options, potentially combined with log level debug to insure all worker output reaches master, seem like they would solve this issue. This wouldn't be as persistent as exporting the logs to a separate s3 bucket, however.

Great idea.

This wouldn't be as persistent as exporting the logs to a separate s3 bucket, however.

… but much more user friendly. If we do this, there must be some housekeeping, like a global limit on the overall size of all worker logs, LRU eviction etc. Gzipping the logs before they are sent to the leader will dramatically improve throughput and log storage capacity.


Allow disabling upgrade diff

Is your feature request related to a problem? Please describe.
I tried to use common module but the upgrade diff does some weird stuff and the activation fails. I don't need that diffing, it would be cool if there is a option to disable it

Do you mind pasting the error message? If we can fix the error we can keep the module system simple.

[ERROR]   stderr) error: experimental Nix feature 'nix-command' is disabled; use '--extra-experimental-features nix-command' to override
[ERROR]   stdout) Activation script snippet 'diff' failed (1)
[ERROR]   stdout) setting up /etc...

On second apply it works. I assume on first apply the old generation has not nix-command enabled

thanks, that helped me build the fix


clear() for LoSo_Doctrine_ORM_Tools_Repository_GenericRepository

Following the recipe on
http://www.doctrine-project.org/blog/doctrine2-batch-processing
for batch-inserting etc. it woud be nice to have a method clear in the GenericRepository
public function clear()
{
$this->_em->clear();
}

Function added, thanks for the suggestion.


add keep_policies config to prevent Zappa from removing resource policy

Description
This is a small change to ignore certain policies from the pruning that happens in Zappa._clear_policy
The context is that my function is attached to a VPC/VPN/private ALB through a secondary configuration. It requires a policy that allows load-balancing, but the policy keeps getting cleared out by Zappa.
This change allows for a simple keep_policies configuration that can be set to a list or string for SID matching within the function policy, and is null/disabled by default.

Can you raise an issue describing the problem addressed here?

Description
This is a small change to ignore certain policies from the pruning that happens in Zappa._clear_policy
The context is that my function is attached to a VPC/VPN/private ALB through a secondary configuration. It requires a policy that allows load-balancing, but the policy keeps getting cleared out by Zappa.
This change allows for a simple keep_policies configuration that can be set to a list or string for SID matching within the function policy, and is null/disabled by default.

I am fairly confident that there are probably existing Zappa settings that can do some, if not basically all, of what you are trying to accomplish with this PR.  It's not 100% clear to me what exact behavior you need to have (or to avoid?) from Zappa, but if you read through the README, especially once it starts talking about Zappa's Advanced Settings and various specific use cases for them (with many of those use cases also linking to some useful tutorials some of our users have made), I think there's a good chance you'll find what you need somewhere in the documentation.
In particular, there are several examples under the Using Custom AWS IAM Roles and Policies that stand out in my mind as possibly being able to help with what it seems like you might be trying to do with this PR:

Custom AWS IAM Roles and Policies for Deployment: If you are encountering issues with the default Zappa IAM role not being able to deploy your application successfully, take a look at this example and consider using the profile_name setting.  A profile can be tied to an IAM user/role that can be granted whatever specific policies/permissions you need so Zappa is able to deploy your application successfully in your specific environment.
Custom AWS IAM Roles and Policies for Execution: If the problem is that, once deployed, Zappa seems to be unable to run your application, then perhaps take a look at this example.  By setting "manage_roles": False and then setting either role_name or role_arn to a custom role name/arn you've set up without the help of Zappa that you can grant whatever specific policies/permissions that the role needs to be able to successfully run your application in your environment.

I'll note that it sounds like using the existing settings {"manage_roles": False, "role_name": "MyIAMPolicyRole"} would do something very similar to what you are trying to accomplish with the new setting you suggest adding in this PR (e.g., {"keep_policies": "MyIAMPolicyRole"}).

Furthermore, you can see just below the previous example that you can also use the extra_permissions setting to essentially explicitly add a list of additional JSON IAM policies containing whatever permissions you'd like for the Zappa IAM role to have.  This can be used as an alternative to provisioning and managing a custom IAM role, as this will have Zappa still manage the IAM role, but just with whatever extra policies/permissions you give it in your Zappa settings file.
Also, as a kind of compromise between the relative extremes of telling Zappa to stop managing IAM at all and having to maintain the Zappa execution role yourself, or having to put all of the custom IAM policies/permissions you need the Zappa IAM role to have in one giant extra_permissions block in your settings file, I believe a third option is that you could also choose to use the assume_policy and/or attach_policy settings, which you'd do by defining them as strings containing the filename (and qualified path, if necessary) of a valid JSON IAM Policy file (ex. "assume_policy": "my_very_long_policy_file.json"), which can then allow the policies/permissions needed by the Zappa IAM role to live in its own JSON IAM Policy file, which you can then have the Zappa IAM role assume or attach, respectively, to gain the permissions it needs when executing your application in your environment.

And, if it helps, Zappa can also be configured to run within a VPC using some other settings you may want to take a look at.  For starters, check out the vpc_config dictionary setting near the very bottom of the list of Advanced Settings, and then you can read a bit more about running Zappa within a VPC here: Running Tasks in a VPC.  That section should also contain links to external tutorials that go into more depth on the subject.
Speaking of tutorials, that reminds me: don't forget to check out our Zappa Guides section of the README - several cover topics around deploying and running Zappa within a VPC and other topics you might find helpful for your specific situation.
You may also want to check out our section on how to configure API Gateway to make your Zappa application only be accessible from within your private VPC, if that's a use case relevant to you.  See: Endpoint Configuration
Lastly, I'll also just mention that Zappa has some ALB support out-of-the-box as well, including supporting ALBs running within VPCs.  Similar to the vpc_config I mentioned earlier, take a look at the alb_vpc_config dictionary setting near the very top of the list of Advanced Settings (and don't forget about the alb_enabled setting either!), and then you can read a bit more about running Zappa behind an ALB: Application Load Balancer Event Source.  I think that's yet another section that contains some links that go into more depth on the subject.
With sufficient targeted Zappa research under your belt, I would bet that you will be able to accomplish what you are trying to without needing to open a PR to add any additional settings to Zappa. But, then again, perhaps I have just not fully understood what you are trying to accomplish... 😕
That's why, if you do the research and still feel like you are no closer to solving your problem on your own, then I strongly agree with and bump @monkut's wise suggestion to please create a new Issue, which will provide you with a dedicated, more visible space designed for discussion to happen among the Zappa community.  You'll be able to share more on the specifics of the problems you are facing, and that will help us all to get on the same page 🙌
And, who knows, you might even get lucky and have another member of the Zappa community who has dealt with the same issue before might show up and tell you how he figured out how to solve it.  That's certainly something I've seen happen a few times.
Anyway, I really hope something in the documentation or a tutorial will help the solution to your problem click for you, but, if not, I look forward to reading the Issue you open about it and learning in more detail about why the current Zappa implementation seems to be incompatible with achieving your goals under your specific set of circumstances, and collaborating on what would be the ideal way to solve whatever the root of that problem ends up being 🤔
Good luck!


Transpiler-helper module

A module to use the Qiskit transpilation on qoqo Circuits and QuantumPrograms

Formatting isn't correct, write me and I'll explain you how to set it up properly.
Also everything about versioning is missing, but for the moment it's fine, we can think about that later on. In the meantime you could modify the CHANGELOG adding something like
### Unreleased

* Added `transpiler_helper` submodule.


Background colour not fixed when hue is 0

When the initial hue is 0 (e.g. colour is black or red), the background colour of the saturation bar changes as the saturation is changed. When the hue is not 0 (e.g. colour is blue or #ff0001), the background colour is fixed.
The fixed background colour seems to be the correct behaviour, as this means that the user can see what the colour will be before they click on it. The background colour should probably only ever change as the hue bar changes and default to red.
Manually dragging to the top of the hue bar also fixes the background colour.
This fiddle demonstrates the issue:
https://jsfiddle.net/34v1kjkc/

The bug seems to be in Color.toRGB, where !h returns true for both undefined and 0.
A possible fix is to change
if (!h) { ... }
to
if (typeof h === "undefined") { ... }
However, I don't know what other implications doing this has.


feat(k8s): Switch from CoreV1 Endpoints to DiscoveryV1 EndpointSlice

EndpointSlice API is available as V1 since K8s 1.21. Let's do not rely on old Endpoint API in KTF.
It's been spotted during work on https://github.com/Kong/kubernetes-ingress-controller/issues/3916. In KIC TestCreateManager depends on this package. In that test K8s objects have to be mocked, relying on obsolete CoreV1 Endpoints by kubernetes-telemetry requires to use them in those mocks instead of DiscoveryV1 API.

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

@programmer04 Oh oh, I just missed that this is not a PR to KIC 😅 Nevermind! :)


Space-X Landing Page Clone

🛠 Fixed Issue :
Closed : SpaceX Clone #287

👨💻 Changes proposed

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

Imp Note :
I have hosted this clone on Netlify , By clicking here you can see the Output.
📷 Screenshots

hey @Rayman-Sodhi ,Checkout this PR and if all things are good to go , Then Kindly merge it ............

You can see the output here :
https://ayushsleeping-spacexclone.netlify.app/

Also this clone is fully Mobile Responsive .

This one is also copied from here https://github.com/ashutoshlohani/spaceX-clone-landing-page
@Rayman-Sodhi

This one is also copied from here https://github.com/ashutoshlohani/spaceX-clone-landing-page
@Rayman-Sodhi

Hey @gurjeetsinghvirdee , I didn't copy from anywhere ................... and few things I learn from a Youtube and then implmented it .


Introduce project settings

Introducing projectsettings makes a lot of sense, but I think we should keep them separate from the ProjectMeta.

How exactly would you do that?

@jaapio I am not sure how to proceed here, please clarify

ProjectSettings is for me a collection of settings defined by the user when running the application. That means that input-format and output-format are part of the settings in my opinion so is the theme. I compare this to the settings phpdoc and PHPUnit define in XML. Those settings allow users to define their configuration in code and commit it to their project.
ProjectMeta is another layer of configuration, defined in the RST format. And we need to merge those at some point. ProjectMeta is a result of the parser, together with the parsed documents? So if we put the ProjectMeta in the context of the parser, we could merge those in an eventlistener (yes events need to be adjusted for this).
So steps would be:

start application
read ProjectSettings from file
configure the runtime (input, output, theme, title)
pre parser get the ProjectMeta from the ParserContext and overwrite the title & version with ProjectSettings
run the parser
run compiler
push the ProjectMeta in the renderContext
start rendering

During the rendering, we have the renderContext to carry the ProjectMeta. That allows us to do the title rendering etc.

I'm not sure if I'm now overcomplicating stuff, and if this makes it more clear for you. Please let me know, otherwise, we can schedule a call to talk about this.

I believe you are thinking about a different kind of settings here, like about the ones that wouter introduced. These settings should replace the settings.cfg of Sphinx. This is information that is needed for rendering, parsing or in the passes. In Sprinx it is done like this: https://github.com/TYPO3-Documentation/TYPO3CMS-Reference-CoreApi/blob/main/Documentation/Settings.cfg It contains information about project (output in rendering) edit on github button (rendering) intersphinx mapping (already needed in the passes) and can in some cases be used to define additional textroles (we might not want to support that, but it would be needed during parsing). The settings are part of the data of the project / document tree. different versions of the project might have different settings. However I would not include technical information like which Extensions are loaded or what are the paths in here. As this information is not part of the project itself

I'm getting confused by the number of different settings in this situation. That means that we will have 4 levels of settings?

guides.xml
cli arguments & options
ProjectSettings
ProjectMeta

The first 2 are application settings? where the last 2 are project settings? Maybe we should name them as such, remove the ProjectMeta and directly configure the ProjectSettings when reading fieldset lists?
I'm trying to avoid too many layers that people won't understand.

I am starting starting to wonder if ProjectMeta should be a Node. We would have a ProjectNode, it knows its DocumentNodes and stores Project wide information

Interesting... that would also remove the need of metas? As we can store them in the projectNode?

Should we give it a try? However without a Node being mutable that will be a real hassle, as we would have to change the ProjectNode whenever we find a new link or some such

Maybe we should make an exception, however... the immutable behavior is not a hard requirement for me it think. So if it becomes a real issue, we might need to consider removing it.
Let's first give it a try with immutable, and if it becomes a problem let's see how we can change this.

The ProjectNode should be known from any DocumentNode. That means for each and every change we would have to inform all documents?

I didn't follow the whole discussion, but I'm not very convinced about the need for a settings.php next to guides.xml. I think we can combine them (which I'm also used to do with Sphinx's conf.py file).

We can allow extension configuration (the thing we now exclusively use with prependExtensionConfig()) to be included in the XML config:<guides>
  <extension class="phpDocumentor\Guides\Guides"
    title="Project title"
  />
</guides>

(we can do it so that the GuidesExtension can be configured through the root <guides> node)
In the GuidesExtension, we would preconfigure ProjectSettings in the DI container based on the config we receive.
Then, for some options we can allow CLI options to e.g. call $projectSettings->setName($input->getOption('project-name')) to override the default config values.

If we, in the future, add container caching we can check freshes based on guides.xml: As long as it is not updated, the container is still fresh. If it's updated, we have to rebuild the container.

From a phpDocumentor point of view, refreshing might become an issue, as we are already using the container cache. What you see in general is that people install phpDocumentor globally and then start parsing their projects. Having a shared cache with multiple projects might become an issue when using the configuration options of Symfony?

In TYPO3 we also work with a settings.cfg which is part of the data, not part of the Application. We use the same Application for a great number of input. Each input has to have its own settings

@jaapio I gave it another try, attached the project Node to the ParserContext/RenderContext and introduced a CompilerContext to also have it available there

@jaapio thanks for the suggestions, done!

Do we still need the SettingsManager? If an extension wants to change the project settings, this can be done via a compiler pass or pre-rendering.

The settings do not come from an extension but from the project data. So yes we still need them and more settings then just the project name will come once I get this finally merged. I wanted to keep this PR short and simple and it is starting to turn into a monster :(

@jaapio done

Merged! Thanks for all the improvements


Register/load module files only for admin not for user.

@nWidart is it possible to register/load module files only for admin but not for user ?
For example How can I replace this function in module.php file?

I use a database to register all modules and with spatie/permission verify have access to BREAD to build user menu and into controllers use Policy

I use a database to register all modules and with spatie/permission verify have access to BREAD to build user menu and into controllers use Policy

@yashiroiori Could you give me a short explanation on how to achieve this?


Handle lack of usernames better

New accounts don’t have a way to set a username, but the design seems to assume each user has one. When it falls back to email, it looks like a bug. Maybe we should always use email and just remove the first at symbol?

Fixed on #15
simply always shows email


Prompts Picker

closes: https://linear.app/sourcegraph/issue/SRCH-1264/surface-prompts-in-cmd-k-in-vscode-sorted-by-last-used
Adds quick pick for prompts with alt+p shortcut.
https://www.loom.com/share/18c0c54259e34704834d47544e02b2a3?sid=b112f153-48f2-4d4c-9a1c-0e248252ccf0
Test plan

alt + p
search and select any prompt
it should be executed the same way it does from the prompt library.

Changelog
Adds quick pick for prompts with alt+p shortcut.

@thenamankumar Added a few comments. I'd like us to try and get them in as they vastly improve UX for little cost.

@thenamankumar Added a few comments. I'd like us to try and get them in as they vastly improve UX for little cost.

I updated the short cut to Shift+Opt+P.
I also moved the description to below the title.
Lets add the additional links like "New Prompt" later separately. I don't have more time this week.

@thenamankumar Added a few comments. I'd like us to try and get them in as they vastly improve UX for little cost.

I updated the short cut to Shift+Opt+P.
I also moved the description to below the title.
Lets add the additional links like "New Prompt" later separately. I don't have more time this week.

Aweesome! No worries.

Thanks all! I'm going to merge this as its a required feature we need to ship on Nov 25


Feat/LIVE-4533 LIVE-4532 - Improve decimal handling to show more digits

📝 Description
live-common:
Add dynamicSignificantDigits parameter to formatCurrencyUnit to show more digits of value when needed. Also increased this default parameter value from 4 to 6, so more digits will be displayed throught LLM and LLD.
live-mobile and live-desktop:
use new parameter from formatCurrencyUnit, dynamicSignificantDigits, in all related display value components/utils. Increased this value (to 8) for the display of the account crypto value in Account page so more digits are shown.
❓ Context

Impacted projects: `` live-common, live-desktop, live-mobile
Linked resource(s): `` https://ledgerhq.atlassian.net/browse/LIVE-4533 https://ledgerhq.atlassian.net/browse/LIVE-4532

✅ Checklist

[ ] Test coverage
[ ] Atomic delivery
[ ] No breaking changes

📸 Demo
Before:

After:

🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

Should resolve https://github.com/LedgerHQ/ledger-live/issues/553


dts/stm32: Populate clocks for i2c nodes and use CONFIG_ #defines for instances configuration

"clocks" property is missing in stm32 i2c nodes, which prevents using #define CONFIG_xxx for clock related code configuration in i2c instances:
static const struct i2c_stm32_config i2c_stm32_cfg_1 = {
	.i2c = (I2C_TypeDef *)CONFIG_I2C_1_BASE_ADDRESS,
	.pclken = {
		.enr = LL_APB1_GRP1_PERIPH_I2C1,
		.bus = STM32_CLOCK_BUS_APB1,
	},

Rather than using the hardcoded #defines LL_APB1_GRP1_P_XXX and STM32_CLOCK_BUS_XXX,
instance configuration code, should rather use the equivalent coming from dts #define generation.
Cf example in drivers/can/stm32_can.c:
static const struct can_stm32_config can_stm32_cfg_1 = {
        [... ]
	.pclken = {
		.enr = CONFIG_CAN_1_CLOCK_BITS,
		.bus = CONFIG_CAN_1_CLOCK_BUS,
	},
	.config_irq = config_can_1_irq
};

This should be done in 3 steps:
-Populate "clocks" property in all i2c nodes in stm32 dtsi files
-Populate the CONFIG_ <> generated defined in stm32 fixup files
-Update stm32 i2c instanceiation code to use CONFIG_ symbols

I have done it for I2S in stm32f4 (#9034 ) and it can be taken as reference once that it is approved
by @erwango.


Recommendations for Standalone Deployment w/ UI?

Morning team,
For an ideal simple deployment to support the upcoming TLA PlugFest, I'd like to avoid having weird ports exposed and preferably run on a single machine (some datasim.tla.adlnet.gov).
We typically just stick everything into containers and route traffic through an nginx container, but that typically requires the containers having unique root paths for their requests etc.  With the API not allowing for a root path config option like /api and the containerized version having given us issues in the past, I'm curious what the best / recommended practice would be to get everything stood up without too much fuss etc.
Thanks!
-Trey

Hey Trey,
Just to make sure, is it your intention to use the UI/API itself in the demo or do you just need to generate & send data?
If it's the former, we've got a PR+Branch with support for server env configuration (including a root path) here: https://github.com/yetanalytics/datasim/pull/72 . I'm currently looking at the UI to see if I need to add some config for the root path there too.
If it's just the latter you can run it "headless" a la the CLI, (the default entrypoint in the Dockerfile).
I also note we haven't yet published public docker builds of this, which I can remedy.

For the UI, currently you will have to build it yourself if you want a different hostname/path to the server in the client, see here.
Basically the steps would be:

Edit the datasim-ui.env/api variable here to your desired host/port/path: https://github.com/yetanalytics/datasim-ui/blob/master/prod.cljs.edn#L1
Run make clean gh-pages
Serve the contents of the gh-pages directory that step 2 creates.

We plan on doing some kind of integrated CD for datasim-ui in the future, but it is currently manual.

OK, #72 and #73 are merged, to set the root path you could do something like:
$ docker run -it \
> -e API_ROOT_PATH=/foo \
> -p 9090:9090 \
> --entrypoint bin/server.sh \
> yetanalytics/datasim:latest
[main] INFO com.yetanalytics.datasim.server - {:msg "Starting DATASIM API...", :root-path "/foo", :host "<IP_ADDRESS>", :port 9090, :allowed-origins ["https://yetanalytics.github.io" "http://localhost:9091"], :line 276}
[main] INFO org.eclipse.jetty.util.log - Logging initialized @6627ms to org.eclipse.jetty.util.log.Slf4jLog
[main] INFO org.eclipse.jetty.server.Server - jetty-9.4.44.v20210927; built: 2021-09-27T23:02:44.612Z; git: 8da83308eeca865e495e53ef315a249d63ba9332; jvm 11.0.15+10-alpine-r1
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@320d98f5{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.AbstractConnector - Started<EMAIL_ADDRESS>(http/1.1, h2c)}{<IP_ADDRESS>:9090}
[main] INFO org.eclipse.jetty.server.Server - Started @7051ms

And find that:
$ curl <IP_ADDRESS>:9090/foo/health
OK%

Hope this helps!


Vite produces error on import - marker-clusterer-plus does not provide an export named 'default'

Describe the bug
When using vite, the vite throws below error
The requested module '/node_modules/marker-clusterer-plus/src/markerclusterer.js?v=9cd0e59f' does not provide an export named 'default'

To Reproduce
Steps to reproduce the behavior:

Instantiate Vue project using vite
Import library in main.js
import VueGoogleMaps from '@fawmi/vue-google-maps'

Expected behavior
No error
Screenshots

Desktop (please complete the following information):

OS: Windows
Browser: Chrome
Version: 92

Additional context
Should we move to using https://github.com/googlemaps/js-markerclustererplus instead of no longer maintained https://github.com/mikesaidani/marker-clusterer-plus

Found a workaround this, in case anyone comes looking here
  // in vite.config.js
  optimizeDeps: {
    include: [
      'marker-clusterer-plus'
    ]
  }

Moving to https://github.com/googlemaps/js-markerclustererplus instead of no longer maintained https://github.com/mikesaidani/marker-clusterer-plus will also solve this error, as @googlemaps/js-markerclustererplus exports are not erroneous.

I also had to add vue-google-maps to optimizeDeps because I was getting:
Uncaught SyntaxError: The requested module<EMAIL_ADDRESS>does not provide an export named 'default'    main.js:1

optimizeDeps: {
    include: [
      '@fawmi/vue-google-maps',
      'marker-clusterer-plus',
    ],
  },

@adarshmadrecha
This should be fixed in the recent version, can you please check whether this exists in version 0.9.3?

@fawmi ❤ ,   Thanks for the fix. I tested on v0.9.4 There is no longer need to add vite config.

Using the latest Vue, Vite and this library, I faced today this with the same issue with fast-deep-equal. I added it to the optimizeDeps and it worked fine:
  optimizeDeps: {
    include: [
      'fast-deep-equal',
    ],
  },


Email not working

Captcha failing which prevents email from sending.

fixed in the new version; www.jsonschema.net


Direct links to stories broken

http://homelessness.civicpdx.org/migration is the url  that shows when you navigate to the migration card, but it can't be accessed directly/leads to 404.

This is another issue related to the civic platform not working yet. I can look into an interim solution.

Assigning to @meganmckissack to push to the Platform team


CI: Basic build for major operating systems

Just does a basic install and test of AKMC for now.

Merging for now, need to move towards the refactor anyway.


Feat: Create OS_LEADERS.md to list OS Leaders and their roles

Is your feature request related to a problem? Please describe.
It would be helpful for contributors to know the OS Leaders and their roles on the projects. This way they know who to ping on project specific issue.
 So, perhaps this issue can only be claimed by an OS Leader.

@isabelcosta or @annabauza , can you please confirm whether or not this issue is valid? Thanks

@mtreacy002 I just saw this now, but will totally come back to this, in a couple weeks.

Cam I work on this issue?

Can I work on this? @isabelcosta @mtreacy002

This issue is a bit old. At the moment, we don't have an ongoing ambassadors program, so we don't have official OS leaders to fill in this information.
I will close this issue cc @anitab-org/admins
cc @Jayita10 @Esther-Wavinya


Use self-assigned over  assigned to

This matches the GitHub UI

Interested in making a PR @disrupted ?


1337 attachment content type

Thanks @ImEagle - will review this over the weekend. Am closing the PR so it's not in the inbox.


Font size in code blocks is huge

Source:

Rendering with the default theme + Prism syntax highlighting:

Haven't found a way to influence this yet, will report back if I do.

I would think that something like this in the theme would do it:
export default {
  styles: {
    pre: {
      fontSize: [3],
    },
  },
};

but it has no effect. Only when I target the Slide, it works:
export default {
  styles: {
    Slide: {
      fontSize: [3],
    },
  },
};

Of course that changes all font sizes everywhere which I don't want.
(I also don't quite understand where the value "3" comes, was able to find this which suggests that by default, the font sizes are [3, 4, 5, 6] but where that comes from, I don't know.)

The theme.fontSizes array is where the typographic scale is defined, and it uses a default scale if it's not set. The way you have theme.styles.pre.fontSize set looks correct, however, so I'm unsure what might be causing the issue you're seeing

Thanks for the info. Do you know where the theme.fontSizes array comes from? I found this file but don't see it there – it's probably not the right file.
I wasn't able to work out how to fix the font size on the theme level so this is a workaround I'm currently using:
# My slides

---

<div style={{ fontSize: '0.5em' }}>

```jsx
export const query = graphql`
  query {
    fileName: file(relativePath: { eq: "images/myimage.jpg" }) {
      childImageSharp {
        fluid(maxWidth: 400, maxHeight: 250) {
          ...GatsbyImageSharpFluid
        }
      }
    }
  }
`;
```

</div>

I think you should set the font sizes to code instead of pre in your case.

@pengx17 I believe I tried both and neither worked, but I can't try right now.

@borekb hmm .. not sure how did you config your app, but I think this works in this demo: https://codesandbox.io/s/mdx-deckprism-example-fbnxe


[Bug]: Description meta is lost when expanding composite tokens

What happened?
Description property meta is lost when expanding composite tokens, meaning you don't get a comment in the output CSS.
There are probably two ways to go about it:

Copy over the meta into the separate expanded tokens, so they all share a copy of the same meta. This seems like the better solution for "any" generic metadata
Put it on the first property only, which might be nicer for something like description, because you wouldn't really wanna see the same comment 4+ times?

Reproduction
Configurator Link
:root {
   /* Some cool description */
  --sdFontMainFontFamily: Arial;
  --sdFontMainFontWeight: 600;
  --sdFontMainLineHeight: 20;
  --sdFontMainFontSize: 14px;
}

Expected output
:root {
   /* Some cool description */
  --sdFontMainFontFamily: Arial;
  --sdFontMainFontWeight: 600;
  --sdFontMainLineHeight: 20;
  --sdFontMainFontSize: 14px;
}

Which at the moment cannot really be accomplished without https://github.com/amzn/style-dictionary/pull/953, and you'd have to put a newline in the description somewhere to manipulate it into placing it above the token. So perhaps it would be cool if that was a commentStyle option as well (short-above, long-above, in addition to short/long, where above is just forced for comments with newlines)
For now,
:root {
  --sdFontMainFontFamily: Arial; /* Some cool description */
  --sdFontMainFontWeight: 600;
  --sdFontMainLineHeight: 20;
  --sdFontMainFontSize: 14px;
}

would already be better, so just moving the description of the group to the first property of the expanded parts is a good intermediate solution
Or alternatively, no special case for description, copying the meta to all props:
:root {
  --sdFontMainFontFamily: Arial; /* Some cool description */
  --sdFontMainFontWeight: 600; /* Some cool description */
  --sdFontMainLineHeight: 20; /* Some cool description */
  --sdFontMainFontSize: 14px; /* Some cool description */
}

Version
0.8.1

@six7 would love your feedback on this.

Let's do version A: Copy over the meta into the separate expanded tokens, so they all share a copy of the same meta. This seems like the better solution for "any" generic metadata
I feel that way you can look at a token, no matter which part of a composite token it is, and understand the added context.

Just to add to this:
:root {
  --sdFontMainFontFamily: Arial; /* Some cool description */
  --sdFontMainFontWeight: 600; /* Some cool description */
  --sdFontMainLineHeight: 20; /* Some cool description */
  --sdFontMainFontSize: 14px; /* Some cool description */
}

this seems (currently) a better solution since style-dictionary output isn't always deterministic in it's output ordering. These tokens may not always be grouped together.

Fixed in v0.14.1


Max reactor height >48 is ignored in the config file.

I set it to 200. Still getting "Machine is too large, it may be at most 48 blocks in the Y dimension" when trying to assemble it.
Would be happy to fix it myself, if someone would help me out getting the mod to compile in my local environment :)
Thanx

Nevermind, apparently this setting has to be set on BOTH the server and the client.
I've only set it server side...


Formatter: wrap comments

Playing with the beta formatter, I was curious why it did not wrap long comments.
See the following long.py file:
def test():
    # This is a very very very very very very very very very very very very very very very very very long comment.
    pass

Running the latest ruff version, the file is left unchanged, while I expected the long comment line to be wrapped:
$ ruff --version
ruff 0.0.289

$ ruff format ./long.py
warning: `ruff format` is a work-in-progress, subject to change at any time, and intended only for experimentation.
1 file left unchanged

I then realized that Black itself doesn't format comments.

Wrapping comments would be a nice quality of life improvement to auto-fix a number of E501 rule violations.

Possibly related issues:

https://github.com/astral-sh/ruff/issues/7361
https://github.com/astral-sh/ruff/issues/5630
https://github.com/astral-sh/ruff/issues/3894
https://github.com/astral-sh/ruff/issues/1904#issuecomment-1671613520

Hey @kdeldycke — I think there are some fair concerns raised in the Black issue but thanks for starting the discussion!
Out of curiosity, would docstring formatting resolve most of your needs here?

In the mean time, autopep8 is supporting comment wrapping. You can perform this task and this only with the following one-liner:
$ autopep8 --in-place --max-line-length 88 --select E501 --aggressive ./long.py

$ cat ./long.py

def test():
    # This is a very very very very very very very very very very very very
    # very very very very very long comment.
    pass

$ autopep8 --version
autopep8 2.0.4 (pycodestyle: 2.11.0)

Hey @kdeldycke — I think there are some fair concerns raised in the Black issue but thanks for starting the discussion!

Oh yes. I'm just starting to understand the complexity of the issue. It's hard to generalize comment autoformat. Especially because of the line-dependency of # pragma kind of comments. I haven't looked into ruff code so I have no idea how hard and how feasible is it to handle these two situations.

Out of curiosity, would docstring formatting resolve most of your needs here?

Oh you mean moving this long comment into a docstring? On paper yes. And yes, I guess when comment became that long, it is time to consider moving them into you function's docstring.
I still have the case in which I need long comments: to not have them appears in the auto-generated Sphinx documentation. I have some places in my code where I need long explanation of implementation details, but don't want to distract the user of my library with these implementation details in the top-level documentation.

I've just come across this again and wanted to throw in something for consideration if this gets implemented...
Some directives in Sphinx, e.g. autodata, have a special comment notation to indicate that the comment should be used for documentation, e.g.
#: A generic type variable.
T = TypeVar("T")

It would be nice to preserve the correct comment marker when wrapping, i.e. the following:
#: This is a very very very very very very very very very very very very very very very very very long comment.
MAGIC_NUMBER = 123

...after formatting would produce:
#: This is a very very very very very very very very very very very very very very very
#: very very long comment.
MAGIC_NUMBER = 123

...and not this:
#: This is a very very very very very very very very very very very very very very very
# very very long comment.
MAGIC_NUMBER = 123

Another thing for consideration might be what happens with comment tags, as defined in lint.task-tags. How should these wrap?
Like this?
# TODO: This is a very very very very very very very very very very very very very very
# very very very long comment.

Or like this? (Which I personally like...)
# TODO: This is a very very very very very very very very very very very very very very
#       very very very long comment.


import header file picker causes the dialog to hide behind the main window

When using the "browse" button to pick a file from the "import header" dialog, the main "import header" dialog will be lowered behind Binary Ninja after selecting a file.

fixed in latest dev


some improvements for jsg/README.md

WIP, still reading/working my way through the file, but wanted to open PR already anyway :)
Thanks for open-sourcing this, amazing to finally be able to check it out! And great work on the product itself, of course! :)

Thanks! Assigning this to @jasnell (who is currently out for a couple days) as he wrote this file.

Done with the file! Added a 2nd commit that contains some "review comments" that I'd be happy to turn into concrete changesets, if desired!

Thank you @seeekr ! I'll be able to take a look tomorrow and will post some feedback then

@jasnell Did you get around to taking a look yet? :-) I can also offer to split off the stuff/comments that might necessitate some more thinking & potentially discussion into another PR or so, so it's more straightforward to just accept the uncontroversial changes?
LMK!

Not yet! Been pretty tied up the last two weeks.

Ping @seeekr


Nix environment is broken on macos

I wanted to test locally my changes for a future pull request and the nix environment seems broken on MacOS. Here's the output of running nix-shell:
building '/nix/store/d3k1zgccyykrxnsxzwzzkhn871808cah-breathe-5074aecb5ad37bb70f50216eaa01d03a375801ec-src.drv'...
dyld: Library not loaded: /usr/lib/system/libsystem_network.dylib
  Referenced from: /nix/store/zdh6jqgv3ayqgl0ifj1z3f9n4s31d8s4-Libsystem-osx-10.11.6/lib/libSystem.B.dylib
  Reason: image not found
error: builder for '/nix/store/d3k1zgccyykrxnsxzwzzkhn871808cah-breathe-5074aecb5ad37bb70f50216eaa01d03a375801ec-src.drv' failed due to signal 6 (Abort trap: 6);
       last 3 log lines:
       > dyld: Library not loaded: /usr/lib/system/libsystem_network.dylib
       >   Referenced from: /nix/store/zdh6jqgv3ayqgl0ifj1z3f9n4s31d8s4-Libsystem-osx-10.11.6/lib/libSystem.B.dylib
       >   Reason: image not found
       For full logs, run 'nix log /nix/store/d3k1zgccyykrxnsxzwzzkhn871808cah-breathe-5074aecb5ad37bb70f50216eaa01d03a375801ec-src.drv'.
error: 1 dependencies of derivation '/nix/store/sqf2k7cnwvqx4xq560bzlqq60z5csc7i-python2.7-breathe-git-arximboldi-5074aecb5ad37bb70f50216eaa01d03a375801ec.drv' failed to build
building '/nix/store/vp7b1p14phwkmjr047p4cr5m9vllkqz2-builder.pl.drv'...
error: 1 dependencies of derivation '/nix/store/rqkgr243m22d1jwr63q0j3x3d1gwr2zl-python-2.7.13-env.drv' failed to build
error: build of '/nix/store/575h7cmv25ijxmgip8sib2rgj27566l1-python3-3.8.5-env.drv', '/nix/store/71jgz7sv8vf3aa610pqq84b3xzbcq00f-sass-3.7.4.drv', '/nix/store/724fjxn5fgf7idlr15qdn11xqwrswr0h-immer-git-ffbc180da6463f8f06af0e96336f161256422b1f.drv', '/nix/store/dbcwi7vsnrvhbi0zph1wqhjg9qhchvz1-imgui-git-6ffee0e75e8f677c5fd8280dfe544c3fcb325f45.drv', '/nix/store/g4c95hwxzjyn58prg82a3vqwcxnf8iih-emscripten-2.0.1.drv', '/nix/store/hnhv3xk7m2rmi4g7q6959a38hrpsw5dh-cereal-git-arximboldi-f158a44a3277ec2e1807618e63bcb8e1bd559649.drv', '/nix/store/nqw5amnsd1py1w56q904rm8qi0srsb3r-libhttpserver-git-f4caf637090b5ff39bfc146b0ecd633f670c3697.drv', '/nix/store/rqkgr243m22d1jwr63q0j3x3d1gwr2zl-python-2.7.13-env.drv', '/nix/store/wyscvqk5z25v2di15jzvvcvj7qh2gnfh-zug-git-be20cae36e7e5876bf5bfb08b2a0562e1db3b546.drv' failed

It seems that the breathe library build is broken.

Wrong repo


Is not work about 'dict' input?

Hello, I'm trying to use pytorch-summary
But, my model's input is "dict" type.
What can I do for using this library about dict input?
Thank you for sharing awesome library :)

I have the same problem. Have you solved it？

@kdheejb7 @styanddty
Hi, I met the same problem, too. Have you solved it？

Same problem.  Have you solved it?


Commits to source/fork repos inconsistently counted

In most cases, if I contribute to a source repo, commits to my fork of that repo are not also counted. This is sensible/expected behaviour. However in some cases commits to both are counted. For example, on https://sourcerer.io/chris48s the number one repo on my list is https://github.com/DemocracyClub/UK-Polling-Stations (which is a source repo) and then the number two repo is https://github.com/chris48s/UK-Polling-Stations (which is a fork of https://github.com/DemocracyClub/UK-Polling-Stations ).
If there's any extra info I can provide to help debug this, let me know.
Thanks

Hi @chris48s !
Really good finding, thank you! We will fix it in near future.


Fine grained controls on FSS for advanced users

Follow-up from: https://github.com/nci/scores/issues/188#issuecomment-2097490317
The FSS implementation in #266 provides the user with flexibility to calculate skill scores from single 2-D fields. However, accumulating these scores temporally or spatially across other dimensions is not a trivial problem, and may have implications on skill interpretation. See: 1
The current implementation (#266) aggregates the decomposed scores. Which is one approach shown in the reference. While this achieves consistency in some situations may have trade-offs compared to simply averaging the scores in other situations. Furthermore, 0 value cases were discussed here: https://github.com/nci/scores/pull/266#discussion_r1595199353 similar questions/points are also considered in the reference.
The implementation in #266 already offers a single field variant, and in specialised methods the ability to return decomposed scores. Hence, the user can already choose to address any follow up research using those features. However, for convenience it may be useful to provide the choice between aggregation (current implementation) and averaging over other dimensions when accumulating fields.
Further, to address cases where F = O = 0 there are a couple of propositions given in the referenced paper.

Reference

https://journals.ametsoc.org/view/journals/mwre/149/10/MWR-D-18-0106.1.xml

FSS "curve"
Often times in papers the FSS is computed as a curve, where
x axis = scale (i.e. window size)
y axis = FSS value

Curves of exponentially increasing thresholds, e.g. 0.5 1 2 4 8 16 32 are commonly used (at least in rainfall). Are overlayed on one another. Additionally, one may wish to overlay lead_times. Currently creating complex datasets with multiple windows/threshold are shown in FSS.ipynb tutorial notebook but if this is a common enough use-case it should be considered to be in the public API.

Note: This is where #269 and #270 can provide benefits due to speed up of computations as well as limiting memory usage, when compared to pure python/numpy calls. This would allow more data-points to be used in the curve without much computational overhead.

Extra usability comments from Pete

An extra comment:
It is common to use FSS on percentages as well as/instead of thresholds. Is it too late to ask for this to be added (or should it be a new request?)
Reason I ask is that FSS with percentages can better reflect user interpretations  - especially where forecasters really look at patterns and generally do a bit of bias correction for peak amounts. This is especially true for rainfall, which is the main use of FSS.
Another common part of FSS is to impose a lower threshold on frequency - i.e. to get a result both obs & model domain-wide frequencies need to have greater than a certain percentage (0.5%, or 1% or some user specified value). When comparing occurrences at just a few points across a domain the FSS doesn't really make much sense.


How to determine the correct CRS when adding multiple geojson?

Given that a GeoJSON layer in leaflet is an extension of the layer group and it is actually multiple individual layers each of which could have its own CRS, and given that it is possible to load multiple geojson files in to the same geojson layer, it seems premature to have all of the sub-layer's CRS set upon the initial layer creation and first geoJSON which is loaded.  Instead shouldn't we assign each sublayer's CRS when the geojson file is actually loaded into the layer so that if we are loading multiple geojson's with different CRS into the same geojson layer, each sublayer is assigned the correct crs?
I think this change would be minor, Instead of having Proj4 change the 'initialization' to add the CRS upon initialization, it would assign the CRS in the 'addData' function so that it add the CRS to the sub layers whenever new data is added to the layer?

Hi!
This sounds reasonable, but looking at the code, the CRS is already picked up in the addData method: https://github.com/kartena/Proj4Leaflet/blob/master/src/proj4leaflet.js#L291-302
What I think is the problem, is that Leaflet has a single coordsToLatLng option, which means that you really can't have more than one CRS in a single GeoJSON layer.
The solution is either to use one layer per CRS, or reproject the GeoJSON to the same CRS (preferably WGS84), something you could do before handing the GeoJSON to Leaflet with for example reproject.

I'm sorry, I was actually looking at the refactored version for Leaflet 1.0.0-beta2 which no longer includes the addData method, and which only uses the initialization function:
https://github.com/kartena/Proj4Leaflet/blob/leaflet-proj-refactor/src/proj4leaflet.js#L156-168
Right now the leaflet addData() function makes all of the sub-layers automatically inherit their parent layers options.  The only way I can get multiple sub-layers with different CRS's in the same layer is by starting with separate GeoJSON layers and then looping through one layer calling addLayer() to move the sub-layers from one layer into the other layer without inheriting/changing their options or the parents options.

@MuellerMatthew ah, right. I realized that you were referring to leaflet-proj-refactor when I saw your PR. You were completely right that the implementation had problems since it didn't have the addData method; I've ported over the relevant commit to the 1.0 branch as well.


npm run start not finding ssl-nss.so

Commit: 054526dacd2dfcea47a07dda1971b7fbb45e00ed
# npm run start -- -p 9555

><EMAIL_ADDRESS>start /root/matrix-appservice-purple
> node build/src/Program.js -c config.yaml "-p" "9555"

Unable to load crypto module: crypto will be disabled: Error: global.Olm is not defined
Dec-29 15:00:20.533 INFO cli Loading config file %s /root/matrix-appservice-purple/config.yaml
Dec-29 15:00:20.550 INFO Program Starting purple bridge on port  9555
Dec-29 15:00:20.551 INFO Program Selecting node-purple as a backend
(node:16960) ExperimentalWarning: The fs.promises API is experimental
(node:16960) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 unpipe listeners added. Use emitter.setMaxListeners() to increase limit
(node:16960) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:16960) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 drain listeners added. Use emitter.setMaxListeners() to increase limit
(node:16960) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added. Use emitter.setMaxListeners() to increase limit
(node:16960) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 finish listeners added. Use emitter.setMaxListeners() to increase limit
(node:16960) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 unpipe listeners added. Use emitter.setMaxListeners() to increase limit
(node:16960) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:16960) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 drain listeners added. Use emitter.setMaxListeners() to increase limit
(node:16960) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added. Use emitter.setMaxListeners() to increase limit
(node:16960) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 finish listeners added. Use emitter.setMaxListeners() to increase limit
Dec-29 15:00:20.733 INFO RoomAliasSet Loaded 2 regexes
Dec-29 15:00:20.734 INFO Program Bridge has started.
Dec-29 15:00:20.734 INFO RoomSync Beginning sync
Dec-29 15:00:20.737 INFO RoomSync Got 0 group rooms
Dec-29 15:00:20.737 INFO RoomSync Finished sync
Dec-29 15:00:20.737 INFO PurpleInstance Starting purple instance
Dec-29 15:00:20.738 INFO PurpleInstance Plugin search path is set to  /root/matrix-appservice-purple/node_modules/node-purple/deps/libpurple

(process:16960): GLib-CRITICAL **: 15:00:20.738: g_hash_table_insert_internal: assertion 'hash_table != NULL' failed

(process:16960): GLib-CRITICAL **: 15:00:20.738: g_hash_table_insert_internal: assertion 'hash_table != NULL' failed

(process:16960): GLib-CRITICAL **: 15:00:20.738: g_hash_table_insert_internal: assertion 'hash_table != NULL' failed

** (process:16960): CRITICAL **: 15:00:20.738: purple_dbus_register_pointer: assertion 'map_node_id' failed
node: symbol lookup error: /root/matrix-appservice-purple/node_modules/node-purple/deps/libpurple/ssl-nss.so: undefined symbol: purple_plugin_register
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR<EMAIL_ADDRESS>start: `node build/src/Program.js -c config.yaml "-p" "9555"`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2018-12-29T15_00_20_760Z-debug.log

Yeah, this is because it always fails to find the correct symbols. I tend to suggest the start.sh script as a workaround.

Yep! start.sh works.


[Realsense Viewer] [Multicam] Unable to select cameras (index >0)

Required Info

Camera Model
D415

Firmware Version
5.12.3 (Doesn't matter)

Operating System & Version
Windows 10

Platform
PC

SDK Version
Tested & Symptoms Confirmed 2.29.0 ~ 2.34.1

Issue Description
Able to select a single camera on top of the list ↓↓↓

Unable to select the ones after that ↓↓↓

Same symptoms with much less cameras

@dorodnic   I would think that it might be an IMGUI related issue if IMGUI is responsible for the user interface elements?

@MojamojaK    Do you still experience this UI issue in the newest SDK version 2.35.2 please?

Just tested on the 2.35.2 viewer
Probelm persists

It looks like a user-interface bug.  As there are not many other RealSense users who may be adding 20+ cameras into the RealSense Viewer, it is a difficult problem to recreate to prove that it is a bug.  I will seek advice from Intel about it.

This also happens with 2 cameras connected btw.

Thanks, I will update my internal report.

As we have not had any other reports from RealSense users of this particular user-interface effect occurring and have not been able to replicate it, the case will now be closed.  Thank you very much for your report @MojamojaK


Programs can be applied for despite disabled status

If an applicant applies for a program and leaves the in progress application open in their browser, they can still submit their application despite the program being disabled.
This bug affected our Production instance (v2.4.2). A program we disabled on July 15, 2024 had three applications come through days after July 15, 2024. Two of the applicants are registered users and one is a guest user.
We replicated the issue in our Test instance (v2.4.2):

Person 1 begins applying for a program and leaves the tab open in their browser
Person 2 (as admin) publishes the program with the Disabled visibility state
Person 1 submits application

OS: Ubuntu (24.04)
Browser: Firefox
Version: 128.0.2

Please let me know if you need me to clarify anything.

This PR may be discussing a similar thing, not sure:  #5043

Once an application is started, it will continue to be on the program version that it was on when the application was started. However, there's a feature flag that was just released in 2.4.3 (FASTFORWARD_ENABLED) that will fast forward an in progress application to the latest program version. Let me know if that fixes the issue you're seeing.

I upgraded our test instance to 2.4.3 and enabled the FASTFORWARD_ENABLED flag. The applicant gets an error message when they try to navigate different screens.
Overall this is good--but is it possible to change the error message?
Instead of directing folks to contact technical support, the message could let the applicant know that this program is disabled or no longer available.

This should be fixed in the latest version of CiviForm https://github.com/civiform/civiform/releases/tag/v2.8.0


[Incremental] Add sdk arguments to incremental tests

The latest Swift makes tests fail because it cannot load libraries. Point the frontend to the sdk for the incremental tests. Add an affordance to do so. More tests will probably need to use this affordance in the future.

@swift-ci please test

(Barring the Linux failure, which just needs an extra check for xcrun's existence)

@swift-ci please test

(Barring the Linux failure, which just needs an extra check for xcrun's existence)

Thanks!

@swift-ci please test


Add function to find latest version available.

ref : https://github.com/loomnetwork/loomchain/pull/1362

Oh, I accidentally push to the wrong place.


Common changes for DotNetCore Alias

Base pr for #1533, will contain any changes that are cross-cutting between branches.
Changes:

Added new verbosity enum inline with new tooling (common for most commands)
Added support for diagnostic output

@JonCubed,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

The new verbosity options look good... any reason why the Verbose setting is left remaining though?
dotnet.exe no longer accepts --verbose so this should be removed I'm thinking?

Im running 1.0.1 of the tooling but it also looks to me like dotnet doesnt take a --diagnostics argument and instead you just set verbosity to diagnostic?
Also I see in this PR (and the dotnet restore one #1534 ) the restore verbosity options are still using the DotNetCoreRestoreVerbosity enum and not the new consolidated DotNetCoreVerbosity that you've added here.
Perhaps this is a difference between tooling v1.0 and v1.0.1?  IMO may as well shoot for 1.0.1 though since everything is more nicely standardised (eg no separate diagnostic option, and all the dotnet subcommands seem to take the same verbosity levels etc)

@JonCubed I've started to review the .NET Core PRs and it seems like this is the one we should start with and get merged first.
I've changed the target branch to cake-build:feature/dotnetV10tooling.

@ryangribble commented 10 hours ago
dotnet.exe no longer accepts --verbose so this should be removed I'm thinking?

I agree, it should be removed.

ryangribble commented 10 hours ago
IMO may as well shoot for 1.0.1 though since everything is more nicely standardise

I agree, we should target 1.0.1.

@devlead correct all other PRs are based on this branch.
@ryangribble @devlead this branch was meant to introduce changes that were required for all branches, so I've limited changes to specific commands to the relevant PRs where they will be in the context.
@ryangribble The DotNetCoreExecutor Alias was the only one using Verbose so I felt to keep things clean and changes to a minimal that Verbose should be removed in that PR #1551.

Im running 1.0.1 of the tooling but it also looks to me like dotnet doesnt take a --diagnostics argument and instead you just set verbosity to diagnostic?

I upgraded to 1.0.1 and it still takes --diagostics. its a host option that is passed before the command. if you run dotnet --help you'll see it.

Also I see in this PR (and the dotnet restore one #1534 ) the restore verbosity options are still using the DotNetCoreRestoreVerbosity enum and not the new consolidated DotNetCoreVerbosity that you've added here.

In this PR DotNetCoreVerbosity is still using DotNetCoreRestoreVerbosity but in #1534 it is using DotNetCoreVerbosity, it can't use  DotNetCoreRestoreVerbosity as it has been deleted.

IMO may as well shoot for 1.0.1 though since everything is more nicely standardise

I agree, we should target 1.0.1.

That's fine by me, if they are following semantic versioning I don't believe there will be any structural difference in the commands

@devlead all the PRs have been rebased, just waiting on CI to complete

@JonCubed excellent, doing a release right now, but will take a as soon as possible after CI finished.

no worries

Nice work! Sorry I didn't spot that some of the changes I highlighted were covered in other specific PR's 😀

@ryangribble no worries, I should have probably made it a bit clearer

@devlead I guess we need to rebase everything again before merging?

@JonCubed said....
I guess we need to rebase everything again before merging?

Don't think so, currently looks good.

@JonCubed this is in sync with so no rebase try, just rebase 1 PR at a time as they get merged, I'll keep this branch in sync with develop later.
Been busy but I'll look at merging this one first and then we'll go to the next one.
Any particular order for the rest PRs?

@devlead no order for others, all are self-contained


Undefined array key "finalAmount"

First and foremost, thank you for the excellent implementation, but during testing, I encountered an error "Undefined array key "finalAmount"" when retrieving the invoice status
Steps for reproduction:
`
$config = new Config("YOUR X-TOKEN HERE");
$monobank = new MonobankAcquiring($config);
$request = new CreateRequest(
553 * 100,
null,
null,
new MerchantPaymInfo('22', 'test')
);
$invoiveResponse = $monobank->call($request);
$monobank->call(new StatusRequest($invoiveResponse->getInvoiceId()))
`
Thanks

@maksa988 Can you help me?


src/looprestoration.rs: Avoid extra shim calls in fn ptrs

This uses the bitdepth-specific fns directly rather than creating bitdepth-dispatching shim fns.  This eliminates the extra call, which is bad for performance (not measured here, but similar shim calls were bad for perf since the cross-language asm call is not inlined into the shim.
See https://github.com/memorysafety/rav1d/pull/367#discussion_r1289774310 and other comments on that PR.
This also removes the now-unused paste! dependency.  Though if we want to avoid repeating all the match BD::BPC { ... }s, which will come up in other init fns as well, we can add a wrapper macro that uses paste!, similar to the decl_looprestoration_bd_fn! macro removed here, but without any shim generation.

@thedataking, I'm not sure why this is failing on macOS.  I don't think I changed anything that would cause it to succeed on x86_64-unknown-linux-gnu but fail on x86_64-apple-darwin.  Also, if we could get test failures recorded (per test) instead of having meson eat them somewhere, that would be great (for something like this, and in general, too).

The macOS failure should hopefully be fixed now after @thedataking's patch; I made a dumb typo.


python, maven and swagger additions

adding in python virtualenv, maven and swagger components to VM for local dev efforts

@anhou reset from the branch that I previous destroyed...

Thanks for the addition of instructions for the python bits^^ :+1:

:+1:


Object spread operator not working when using into SFC templates

Version
3.0.4
Node and OS info
Node 9.3.0 / yarn 1.9.4 / Windows 10
Steps to reproduce
Use object spread operator inside a SFC template (eg. costructing event payload inline).
<button @click="$emit('event-name', {...localVariable, optionToMerge: true})"></span>

What is expected?
Object spread operator working both in template bindings and script
What is actually happening?
It works fine in script tag, firing off Object spread operator requires specified objectAssign option with 'Object.assign' or polyfill helper error when used into templates.

The problems seems to lay on "buble" transpiler in which object spread operator is not enabled by default as considered "risky" (but can be enabled).
I guess that template bindings and script tags of an SFC are transpiled/compiled by different webpack loaders and the template one causes the problem.

Same here. There used to be a workaround on it (as seen here) but i'm not quite sure on how to properly configure it with the new cli.


Fixed decals when importing a map

Description
When a map is imported, some decals are created over the road to add dirty. Those decals are configured through a .json file and also use the .xodr of the map. But in the import process those files were find in all the content of the project and not only on the content of the package created. That means that if other .json file or .xodr was found, that was used instead of the correct one.
Where has this been tested?

Platform(s): Windows
Python version(s): 3.7
Unreal Engine version(s): 4.26

Possible Drawbacks

This change is

Loos good to me. Tests with the new map shows the decals correctly placed at the driving lanes


CI builds

I'm trying to get CI builds running, but I'm stuck on one thing. NuProj.ProjectSystem.14 fails to build, both with and without referencing Microsoft.Collections.Immutable assembly.
With Microsoft.Collections.Immutable reference:
https://ci.appveyor.com/project/kovalikp/nuproj/build/1.0.6#L76
Without Microsoft.Collections.Immutable reference:
https://ci.appveyor.com/project/kovalikp/nuproj/build/1.0.8#L73
It appears that NuProj.ProjectSystem.14 is using lib\Xaml2Cs.exe instead of lib14\Xaml2Cs.exe for whatever reason to generate .cs files. Any idea what could be wrong? The build is working locally just fine :confused:
The CI build is set to use Visual Studio 2015 RC environment.

NuProj.ProjectSystem.14 should be using lib14\Xaml2cs.exe. And it should be referencing the System.Collections.Immutable NuGet package instead of Microsoft.Collections.Immutable

Yes, that's what it appears to be  doing, at least according to logs.
[00:02:14] Target "GenerateRuleSourceFromXaml" in file "C:\projects\nuproj\src\NuProj.ProjectSystem.12\ProjectSystem.targets" from project "C:\projects\nuproj\src\NuProj.ProjectSystem.12\NuProj.ProjectSystem.12.csproj" (target "PrepareResourceNames" depends on it):
[00:02:14] Using "XamlRuleToCode" task from assembly "C:\projects\nuproj\src\NuProj.ProjectSystem.12\..\..\lib\Xaml2Cs.exe".
[00:02:14] Task "XamlRuleToCode"
[00:02:14]   Generating code for 'Rules\general.xaml'.
[00:02:14]   Generating code for 'Rules\general.browseobject.xaml'.
[00:02:14]   Generating code for 'Rules\folder.xaml'.
[00:02:14]   Generating code for 'Rules\content.xaml'.
[00:02:14]   Generating code for 'Rules\none.xaml'.
[00:02:15]   Generating code for 'Rules\scc.xaml'.
[00:02:15]   Generating code for 'Rules\ProjectReference.xaml'.
[00:02:15]   Generating code for 'Rules\ResolvedProjectReference.xaml'.
[00:02:15] Done executing task "XamlRuleToCode".
[00:02:15] Done building target "GenerateRuleSourceFromXaml" in project "NuProj.ProjectSystem.12.csproj".

[00:03:01] Target "GenerateRuleSourceFromXaml" in file "C:\projects\nuproj\src\NuProj.ProjectSystem.14\ProjectSystem.targets" from project "C:\projects\nuproj\src\NuProj.ProjectSystem.14\NuProj.ProjectSystem.14.csproj" (target "PrepareResourceNames" depends on it):
[00:03:01] Using "XamlRuleToCode" task from assembly "C:\projects\nuproj\src\NuProj.ProjectSystem.14\..\..\lib14\Xaml2Cs.exe".
[00:03:01] Task "XamlRuleToCode"
[00:03:01]   Generating code for '..\NuProj.ProjectSystem.12\Rules\content.xaml'.
[00:03:03]   Generating code for '..\NuProj.ProjectSystem.12\Rules\folder.xaml'.
[00:03:03]   Generating code for '..\NuProj.ProjectSystem.12\Rules\general.browseobject.xaml'.
[00:03:03]   Generating code for '..\NuProj.ProjectSystem.12\Rules\general.xaml'.
[00:03:03]   Generating code for '..\NuProj.ProjectSystem.12\Rules\none.xaml'.
[00:03:03]   Generating code for '..\NuProj.ProjectSystem.12\Rules\ProjectReference.xaml'.
[00:03:03]   Generating code for '..\NuProj.ProjectSystem.12\Rules\ResolvedProjectReference.xaml'.
[00:03:03]   Generating code for '..\NuProj.ProjectSystem.12\Rules\scc.xaml'.
[00:03:03] Done executing task "XamlRuleToCode".
[00:03:03] Done building target "GenerateRuleSourceFromXaml" in project "NuProj.ProjectSystem.14.csproj".

And yet it seems to generate Microsoft.Collections.Immutable for NuProj.ProjectSystem.14:
[00:03:16] obj\Release\content.cs(78,104): error CS0234: The type or namespace name 'Collections' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?) [C:\projects\nuproj\src\NuProj.ProjectSystem.14\NuProj.ProjectSystem.14.csproj]

:unamused:

Then my guess is it's a problem with the .targets files. The GeneralRuleSourceFromXaml task accepts parameters that specify the type names to use for several functions. Immutable collections might be one of them.

@terrajobst Can you please update appveyor settings to use VS 2015 RTM environment and use MSBuild 14.0? CI builds should be working now.

Resolved with #136


cuda implementations of torch/image functionality

Hi everyone
Over the last few months I have been developing lua functions similar to torch/image with cuda support, whenever I needed it. However, I have not seen a single cuda-accelerated function in here. So I was wondering whether others are interested in this functionality and how it is best shared with the community: seperate repo? build flags for this library? automatic replacement of functions when called with a torch.CudaTensor or just extending the function name with _cu or similar?
What are your thoughts on this?
Lukas

it would def be interesting to add.
A separate package called cuimage would be best.
There are a few CUDA accelerated functions here: https://github.com/qassemoquab/texfuncs by Maxime Oquab.

Hey @lukasc-ch are you still working on this? :+1: to having CUDA-accelerated image functions not just for speed but also to prevent overhead from shuffling tensors CPU <-> GPU.

prevent overhead from shuffling tensors CPU <-> GPU

FYI we have started a branch that extends image.load and image.scale with an optional reusable buffer like most torch7 math functions, e.g.:
local dst = torch.FloatTensor()
image.load(dst, "test.jpg") -- `dst` is resized and filled with the loaded image

In particular it is also possible to provide a float tensor created with cutorch.createCudaHostTensor() (a.k.a. pinned memory) that can be used to speed up CPU -> GPU data transfers (provided other conditions are fulfilled).
This branch works and is backward compatible, but not 100% polished. I tend to think that it would be better to 1/ re-think args parsing / checking e.g. with torch/argcheck (most if not all image API-s could benefit from this) to improve readability / maintainability and 2/ apply such modifications.
Would be interesting to hear what others think about this and also how much orthogonal / relevant it is vs. a cuimage project.

@Kaixhin It's good to see that there is some interest to have this functionality publicly available. So far I could not find time to work on this. Reducing the data copying is certainly an interesting aspect. My motivation was coming more from the Tegra K1 and X1 platform, where anything running on the CPU is painfully slow. Hopefully, I will find some time in January to get this done.

Hi all, is there any news for cuimage, or something alternative?


Content cut off when printing

I have a table which contains only one colum. I draw speech bubbles in it, similar to Whatsapp.
Now I have
responsive: 'scroll'
and
overrides: {     MUIDataTable: {       responsiveScroll: {         maxHeight: '100%'       }     }   }
set.
Unfortunately, when I press on Print, a part is cut off.
If I print the page with CTRL + P, it works, but the rest of the UI is on the paper.
Here is a photo (with button):
Here is a photo (CTRL + P):
I suspect, when printing with the button, the virtual page is not as big as the content. How can I change that?

Tech
Version

Material-UI
3.9.2

MUI-datatables
2.0.0-beta.56

React
16.8.3

browser
Safari / Chrome

Also seeing this issue. When I had the table option of Responsive: 'stacked' it printed all rows. Now that I have it as 'scroll' (because it's a better view on mobile), only the first 20 rows are printing and the rest cut off where the container has not expanded vertically.

+1

Also seeing this issue. When I had the table option of Responsive: 'stacked' it printed all rows. Now that I have it as 'scroll' (because it's a better view on mobile), only the first 20 rows are printing and the rest cut off where the container has not expanded vertically.

I am also facing same problem.

No :/

I'm not sure this is a bug. Does this issue occur using the default options only, or only when overriding styles? If you are seeing this when overriding styles, then you are outside of supported print functionality, since print is dependent on styles.
For example, if you've overridden the max-height, you also need to set the overflows to "visible". But that's on you to provide, since the library cannot anticipate how people will modify and override the styles.

I am also noticing this issue.
I have not overridden any styles.
with these options
						options={{
							filter: true,
							sort: false,
							filterType: 'dropdown',
							responsive: 'scrollMaxHeight',
							selectableRows: 'none',
							pagination: false
						}}

all the records are returned on a .csv download (15) but only 8 are generated the pdf.
when I remove the responsive option all the records are on the .csv and pdf.
many thanks.

@s33dco Would you mind opening a new issue with your steps to reproduce? This one is out of date, as the API has changed, so I'm going to be closing it.

I am also seeing this issue and have been trying to get around it for some days now. When I use some of the example on codepen it works until I set the dependencies to more recent versions. I also see that the new window before print doesn't come up. Can it be related to react-to-print which is used?

I have to close this. Printing is dictated by styling. Default styles seem to work correctly. If there's a bug, I need an issue with specific instructions and a minimal codesandbox example.


Bug in Indexing Function Causes Inconsistent Document Deletion

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
Here is an example that demonstrates the problem:
If I change the batch_size in api.py to a value that is larger than the number of elements in my list, everything works fine. By default, the batch_size is set to 100, and only the first 100 elements are handled correctly.
from langchain_community.document_loaders import TextLoader
from langchain.text_splitter import CharacterTextSplitter
from langchain_openai import OpenAIEmbeddings
from langchain_community.vectorstores import Chroma
from langchain_core.documents import Document
from langchain.indexes import SQLRecordManager, index

embeddings = OpenAIEmbeddings()

documents = []

for i in range(1, 201):
    page_content = f"data {i}"
    metadata = {"source": f"test.txt"}
    document = Document(page_content=page_content, metadata=metadata)
    documents.append(document)

collection_name = "test_index"

embedding = OpenAIEmbeddings()

vectorstore = Chroma(
    persist_directory="emb",
    embedding_function=embeddings
)
namespace = f"choma/{collection_name}"
record_manager = SQLRecordManager(
    namespace, db_url="sqlite:///record_manager_cache.sql"
)

record_manager.create_schema()

idx = index(
    documents,
    record_manager,
    vectorstore,
    cleanup="incremental",
    source_id_key="source",
)
# for the first run
# should be : {'num_added': 200, 'num_updated': 0, 'num_skipped': 0, 'num_deleted': 0}
# and that's what we get.
print(idx)
idx = index(
    documents,
    record_manager,
    vectorstore,
    cleanup="incremental",
    source_id_key="source",
)
# for the second run
# should be : {'num_added': 0, 'num_updated': 0, 'num_skipped': 200, 'num_deleted': 0}
# but we get : {'num_added': 100, 'num_updated': 0, 'num_skipped': 100, 'num_deleted': 100}
print(idx)

Error Message and Stack Trace (if applicable)
No response
Description
I've encountered a bug in the index function of Langchain when processing documents. The function behaves inconsistently during multiple runs, leading to unexpected deletions of documents. Specifically, when running the function twice in a row without any changes to the data, the first run indexes all documents as expected. However, on the second run, only the first batch of documents (batch_size=100) is correctly identified as already indexed and skipped, while the remaining documents are mistakenly deleted and re-indexed.
System Info
langchain==0.1.20
langchain-community==0.0.38
langchain-core==0.1.52
langchain-openai==0.1.7
langchain-postgres==0.0.4
langchain-text-splitters==0.0.2
langgraph==0.0.32
langsmith==0.1.59
Python 3.11.7
Platform : Windows 11

Hello, I am also hitting this problem.
if I do not increase batc_size in indexer to be > than document size, I have deletes and adds although I did not change anything in the directory I am loading.
If batch size is > number of loaded documents, then the skip happens and everything is fine.
So, something seems not to be right here.

I created my own indexing system to solve the problem. It is a bit more sophisticated because it is meant to be used with a multi-vector retriever.
You can find the code on my github
And watch the video on Youtube

Hi! i also ran into this problem and worked on a solution for this issue in this PR.
@eyurtsev i hope this can be helpful.

Is there any reason for the PR from @federico-pisanu  to be reverted? This problem still occurs and as far as I understand his solution was according to standards and fixed the underlying problem


EL-691: UAT environment

What
Link to story

Merge the latest CFE-P changes (including the removal of git-crypt in UAT environments)
Attempt to deploy to a UAT branch on PR creation and to a main UAT environment on merge to main.

Checklist
Before you ask people to review this PR:

Tests and rubocop should be passing: bundle exec rake
Github should not be reporting conflicts; you should have recently run git rebase main.
There should be no unnecessary whitespace changes. These make diffs harder to read and conflicts more likely.
The PR description should say what you changed and why, with a link to the JIRA story.
You should have looked at the diff against main and ensured that nothing unexpected is included in your changes.
You should have checked that the commit messages say why the change was made.

Merge the latest CFE-P changes (including the removal of git-crypt in UAT environments)

Big imports like this are great, but probably better as a separate PR, since it is hard to see this ticket's changes separately.
I'd argue that the CFE-P changes are already reviewed there, and you are not the author. So importing them into this repo only requires your review before merging. But the team should really agree this.
btw there are conflicts on this branch now

Ok, amending this PR to be getting the codebases in sync, will then create a new one to add the new stuff

@davidread I've fixed the conflicts and turned this into a "re-sync" PR. But Github is also set up so I can't approve PRs I've opened myself, regardless of authorship of commits (although it doesn't help that I authored the commits I'm trying to sync anyway).


Libraries link not working

Hello,
I'm trying to download the libraries but the link is dead. Please update or send me the correct link. Thanks!
/download/tinylab_libraries.zip

Hello,
You can use this link for all documentations. Regards.
https://github.com/Robotistan/Tinylab-Board

Hello @auswag,
You can temporarily access all library and project code files from the link below. Our development is ongoing and we are sorry for this. We want to solve your problems. Please contact us.
https://github.com/keremizgol/tinylab-kitap/tree/master


Prevent entry row from scrolling

I moved the entry row to an ToolbarView, so it will now always stay at the top:
Screencast from 2023-12-03 12-01-11.webm
I set the libadwaita crate to use the feature v1_4 for this to work.
I had to move some input messages from content to app, because the entry row is now there.
It needed to be at the same level of the header bar, so they could be on the same ToolbarView.

It's currently looking a lot like a search bar, but this will be solved in #21.


inconsistency between the performance of github

Hi , when I test the config of flashocc-r50-4d-stereo, the result is  38.07 :
===> per class IoU of 6019 samples:
===> others - IoU = 9.37
===> barrier - IoU = 46.72
===> bicycle - IoU = 19.43
===> bus - IoU = 41.69
===> car - IoU = 51.07
===> construction_vehicle - IoU = 24.99
===> motorcycle - IoU = 21.24
===> pedestrian - IoU = 23.6
===> traffic_cone - IoU = 24.22
===> trailer - IoU = 31.21
===> truck - IoU = 38.18
===> driveable_surface - IoU = 81.12
===> other_flat - IoU = 40.13
===> sidewalk - IoU = 51.93
===> terrain - IoU = 55.31
===> manmade - IoU = 47.01
===> vegetation - IoU = 39.89
===> mIoU of 6019 samples: 38.07
{'mIoU': array([0.094, 0.467, 0.194, 0.417, 0.511, 0.25 , 0.212, 0.236, 0.242,
       0.312, 0.382, 0.811, 0.401, 0.519, 0.553, 0.47 , 0.399, 0.903])}

which is a little higher than the result you provide:
 with_pretrain:
 ===> per class IoU of 6019 samples:
 ===> others - IoU = 9.08
 ===> barrier - IoU = 46.32
 ===> bicycle - IoU = 17.71
 ===> bus - IoU = 42.7
 ===> car - IoU = 50.64
 ===> construction_vehicle - IoU = 23.72
 ===> motorcycle - IoU = 20.13
 ===> pedestrian - IoU = 22.34
 ===> traffic_cone - IoU = 24.09
 ===> trailer - IoU = 30.26
 ===> truck - IoU = 37.39
 ===> driveable_surface - IoU = 81.68
 ===> other_flat - IoU = 40.13
 ===> sidewalk - IoU = 52.34
 ===> terrain - IoU = 56.46
 ===> manmade - IoU = 47.69
 ===> vegetation - IoU = 40.6
 ===> mIoU of 6019 samples: 37.84 with_pretrain:
 ===> per class IoU of 6019 samples:

BTW, I use 4090 for testing. Could the gap caused by this?

I use this model in readme for testing, and find the mIoU gap above :
https://github.com/Yzichen/FlashOCC/blob/master/projects/configs/flashocc/flashocc-r50-4d-stereo.py


The custom properties shim alters the cascade order incorrectly

For example, I have the following CSS in my <flex-line> element definition:
:host {
  --flex-line-gutter: 1em;
}
:host ::content > * {
  margin: var(--flex-line-gutter) 0 0 var(--flex-line-gutter);
}
:host ::content > flex-line {
  margin: 0;
}

It get translated into this:
<style scope="flex-line">
  flex-line > flex-line {
    margin: 0;
  }
</style>
<style scope="flex-line-0">
  flex-line.flex-line-0 > * {
    margin: 1em 0 0 1em;
  }
</style>

As you can see, the order of the rules has been reversed and the specificity of the first content rule has increased, completely changing the cascade order.
If you're going to change the specificity of a rule (which I understand you have to in some cases) you should normalize it so all rules are increased by the same relative specificity.

This issues was fixed in #2642 but not closed.

Thanks Tim.
Phil holler if you see anything contrary.


One of the bug blog bugs has a really long title causing an issue with description column – convert to LONGTEXT

E   _mysql_exceptions.Warning: (1265, "Data truncated for column 'description' at row 1")

ALTER TABLE card_bugs MODIFY description TEXT

and update the source code.


rbx_dom_lua should be a Wally package

Right now it's only possible for consumers to use rbx_dom_lua by manually copying it out of the repository. It would be a lot easier and more useful if it were a Wally package!

This should at least be simple to resolve, since we can just start publishing it to wally. However, it should also come with more complete documentation and proper CI for it.


Updated Enums.TimeZone from PnP.Site.Core to PnP.Framework

Type

[x] Bug Fix
[ ] New Feature
[ ] Sample

Related Issues?
What is in this Pull Request ?
The hyperlink in the description of the parameter -TimeZone redirects to the archived PnP-Sites-Core project. The parameter syntax already states the correct class [-TimeZone <PnP.Framework.Enums.TimeZone>]. Therefore, I updated the hyperlink to the corresponding web page https://pnp.github.io/pnpframework/api/PnP.Framework.Enums.TimeZone.html.

Thanks @m-hanisch , have merged it !
It will be available from tomorrow onwards.
So glad to have you contribute here, much appreciated 🙏😊


Strict name matching for Repository.GetTagID()

Fixes #7985
I'm assuming "\n" is OK for all platforms? Anyone running Mac?

Once again I had to use:
make clean generate swagger-check swagger-validate vendor

Then commit, push. Let's see what happens with CI now.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@d9545f9). Click here to learn what that means.
The diff coverage is 83.33%.

@@            Coverage Diff            @@
##             master    #8074   +/-   ##
=========================================
  Coverage          ?   41.77%
=========================================
  Files             ?      481
  Lines             ?    64425
  Branches          ?        0
=========================================
  Hits              ?    26915
  Misses            ?    34041
  Partials          ?     3469

Impacted Files
Coverage Δ

modules/git/repo_tag.go
60.1% <83.33%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d9545f9...78f5cf0. Read the comment docs.

So, I don't know why I had to update vendor/, as it is unrelated to this PR. Good news is that it works.

Could you add some tests for that? And is the depends libraries update is necessary?

Could you add some tests for that? And is the depends libraries update is necessary?

@lunny I'll add a test, but the CI is failing again if I don't update vendor.

@lunny see #8075 about the CI failing (it's a dummy PR with no real changes from master).

Please send backport to 1.9

@guillep2k add label:backport/done ?


Fix slug unique validation with locale

Hi, this validation rule was not working for me, the generated query would fail like this:
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'NULL' in 'where clause' (SQL: select count(*) as aggregate from `menus` where `slug` = /head and `NULL` <>  and `locale` = en)

This patch fixes that problem and now it works for me.

Hey!
Thanks for brining up the issue. I published a fix with commit https://github.com/optimistdigital/nova-menu-builder/commit/c2a527cc6a58a1247b044768d0c248a89211675b and created version 1.0.3.
Your validation rule allowed the creation of new menus (which is a pretty bad bug I somehow published), but it still kept one issue where you couldn't update an existing menu anymore (ie change its name and keep the slug the same), due to the unique validation failing. The menu ID that is currently being edited had to be added to the exemption list.
The updated rule looks like so:
...
->rules('required', 'max:255', 'unique:menus,slug,{{resourceId}},id,locale,' . $request->locale)

Thanks.

@Tarpsvo Thanks for the quick response!