pug Shorthand attribute not working.

in pug template this works:
Table(data='{$data}' currentPage='{currentPage}' selectedClass='secondary')
this not work:
Table({$data} {currentPage} selectedClass='secondary')
I can't write Shorthand, for when name and value match.
Thank you.

another issue:
I have:
<script>
    import {CRUD} from './_form.js'
    const c = new CRUD();
    const er = c.er;
</script>

This not working on pug templte:
ShowError(er='{c.$er}')
but this works:
ShowError(er='{$er}')

Same thing as #91, can you share a small reproducible project?

That's actually because the $ store syntax is only supported for top-level variables, not for object properties. If you want to access your store in that way, you should access it by c.er, without the dollar sign and you'd have to do some other stuff to get its value.


Extract assertion output into module and test

I've extracted the two assertion output functions into a separate module in order to reduce the amount of responsibilities that the session module has. As a result, both modules are now much more testable.
I've written unit tests for the output module. I think branch coverage is close to 100% but we'll need to hook up some sort of coverage tool to prove that.
I've also pointed the test:run script at the output spec file.

This is great @SiAdcock. Merged! Thanks :smile:


Incorrect statistics extracted from parquet data pages when all values are null

Originally posted by @efredine in https://github.com/apache/datafusion/issues/10922#issuecomment-2209376864
We always flatten the date page stats iterator - following the pattern from the initial PR: https://github.com/apache/datafusion/pull/10852/files#diff-7110f4709c105a18ef74a212396444d62052179a735d148fb62470a8b157fb40R582
But I'm wondering if flatten is the right thing to do here?
The min or max values for each page will be None if all the values on the page happen to be null: https://github.com/apache/arrow-rs/blob/master/parquet/src/file/page_index/index.rs#L37-L44
Using flatten in this case will mean that the length of result for that page will be shorter than the number of data pages? So, is it possible that rather than flatten we instead want to do something like a flat map where the Some values are flattened and None values are mapped to a null value?
Potential user impact:
The code appended nulls for missing values. However, I think in most cases, missing values are simply omitted because all the None values are removed by flattening. So, in general, users of the data page statistics will need to check whether or not the length of the array matches the number of actual data pages? This is different from how the row group statistics are handled - they will instead have a null value for any missing statistics.
Is this difference in behaviour expected or just a side effect of the implementation.
A: I think it is a side effect of implementation and not a good one

Ideally what I think we should do is to write up a test case (using your suggestion of a column / page that is entirely null) and verify there is a problem / fix it.

Take

Ok - quick update - I had some misunderstanding of what was going on. I think there may still be a problem, but its different from what I originally thought.
My misunderstanding: the top level flatten is because we have an iterator of iterators. The inner iterator is iterating over the page indexes within a ColumnIndex. That inner iterator returns an Option.
And the original PR added an explicit test case for the scenario of a data page with all null values:
https://github.com/apache/datafusion/blob/main/datafusion/core/tests/parquet/arrow_statistics.rs#L475-L504
However, the tests for all the other data types don't cover this scenario and there are a bunch of places where we are doing a filter_map in the inner loop which should probably just be a map. But I need to write tests to prove this first and then expand the coverage if it turns out to be the case.


Fix Writeback Index Prefix in Example Config

Change writeback index prefix in config.yaml.example from elastalert_status to elastalert since we already attach appropriate suffixes in create_index.py

Can you resolve conflicts please :)

Can you resolve conflicts please :)


chore: bump versions for next release(s)

This change also removes uv.lock. From the documentation

Unlike the pyproject.toml, which is used to specify the broad requirements of your project, the lockfile contains the exact resolved versions that are installed in the project environment. This file should be checked into version control, allowing for consistent and reproducible installations across machines.
A lockfile ensures that developers working on the project are using a consistent set of package versions. Additionally, it ensures when deploying the project as an application that the exact set of used package versions is known.

The problem with the presence of this uv.lock for purposes of development of a library like deltalake is that pip installations of the released package will not have the contents of that uv.lock file.
Therefore I want it to be removed so that our local installations, and CI, are always using pyproject.toml to resolve their dependencies in a manner which is consistent with the users of the installed package.

I am fine with removing it, but we should remove the checkout of the lockfile in the CI now, so that it can pass


Support dynamic retry delays

Server's that use rate limiting often use 429 Too Many Requests that includes a Retry-After header. It would be nice if Failsafe would support to dynamically set a delay for one particular exception.

I was going to argue that you could roll your own version of this, but it turned out to be a lot harder than I thought. Implementing it within Failsafe is more feasible, so I created PR #111 as a proposal that I believe would address your request.

Using the RetryPolicy.withDelayFunction from #111, your example could be written something like this:
CompletableFuture<Response> makeRequest(Request request)
        throws TooManyRequestsException {
    return ...;
}

CompletableFuture<Response> makeFailsafeRequest(Request request) {
    RetryPolicy retryPolicy = new RetryPolicy()
	.retryOn(TooManyRequestsException.class)
	.withDelayFunction((response, exception) -> {
	    if (exception instanceof TooManyRequestsException) {
		TooManyRequestsException tmre =
                    (TooManyRequestsException) exception;
		long retryAfterSeconds = tmre.getRetryAfterSeconds();
		if (retryAfterSeconds >= 0) {
		    return new Duration(
                        retryAfterSeconds, TimeUnit.SECONDS);
		}
	    }
	    return null;
	});

    return Failsafe.with(retryPolicy)
	.with(schedExecSvc)
	.future(() -> makeRequest(request));
}

Even if the exception is not thrown directly but if the future ends
exceptionally?
On Oct 1, 2017 20:28, "Tim Peierls"<EMAIL_ADDRESS>wrote:

Using the RetryPolicy.withDelayFunction from #111
https://github.com/jhalterman/failsafe/pull/111, your example could be
written something like this:
CompletableFuture makeRequest(Request request)
throws TooManyRequestsException {
return ...;
}
CompletableFuture makeFailsafeRequest(Request request) {
RetryPolicy retryPolicy = new RetryPolicy()
.retryOn(TooManyRequestsException.class)
.withDelayFunction((response, exception) -> {
if (exception instanceof TooManyRequestsException) {
TooManyRequestsException tmre =
(TooManyRequestsException) exception;
long retryAfterSeconds = tmre.getRetryAfterSeconds();
if (retryAfterSeconds >= 0) {
return new Duration(
retryAfterSeconds, TimeUnit.SECONDS);
}
}
return null;
});
return Failsafe.with(retryPolicy)

.with(schedExecSvc)
.future(() -> makeRequest(request));
}
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jhalterman/failsafe/issues/110#issuecomment-333396384,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAaPnUI34ZMMQZxqwDn_g1glId3gV_Hmks5sn9nmgaJpZM4PpjVh
.

Right, in fact, I probably shouldn't have put throws TooManyRequestsException in the signature of makeRequest and just said that the resulting CompletableFuture could complete exceptionally with that exception.
You could write a little test to confirm that that would work (without using the proposed new method).

Good use case. Thanks for filing this.

This is released in 1.1.0.


Request logging

Added some request logging features. This will log any incoming requests to the API to the console. Note that we're not logging outgoing content, this could be implemented fairly easily as an expansion to this.

Thanks for the quick review Ting! Some really insightful comments. I've implemented all suggested changes :) Also. I agree completely with the useful screenshot, so here it is!


Add AWS > PCI > Autoscaling, CodeBuild & Config docs.

Is your feature request related to a problem? Please describe.
N/A
Describe the solution you'd like
N/A
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Closed in https://github.com/turbot/steampipe-mod-aws-compliance/commit/9ecf1afc58bcc54ff2313adaae781340524361e1


Add api for getting child types in object tree view.

Make object name unique. Support get state by name, type, path or both.

Codecov Report

Merging #134 (54449ca) into stable/v8.x (5d6510d) will decrease coverage by 0.24%.
The diff coverage is 63.79%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@               Coverage Diff               @@
##           stable/v8.x     #134      +/-   ##
===============================================
- Coverage        50.68%   50.45%   -0.24%
===============================================
  Files               78       78
  Lines             6744     6753       +9
  Branches           799      800       +1
===============================================
- Hits              3418     3407      -11
- Misses            3051     3071      +20
  Partials           275      275

Components
Coverage Δ

AuthManager
94.40% <ø> (ø)

Cache
28.06% <ø> (-1.13%)
:arrow_down:

FDS
68.12% <ø> (ø)

FileWatcher
55.90% <ø> (ø)

Flip
37.48% <ø> (ø)

gRPC
77.12% <ø> (ø)

Logging
13.88% <ø> (ø)

Metrics
80.20% <ø> (ø)

Options
100.00% <ø> (ø)

Setting
56.68% <ø> (ø)

StatusObject
73.83% <63.79%> (-11.89%)
:arrow_down:

Utility
83.44% <ø> (ø)

Version
95.83% <ø> (ø)


Add helper utils to SDK for signing EIP712 typed data of attestation

historically a lot of the attestations helper functions were in the base or utils packages of the sdk, but might make sense ot just include this in the identity sdk directly

also small nit: make unblindedSignature a non-optional param https://github.com/celo-org/celo-monorepo/blob/06975ed0bc16e6664519f1a5b3b96181a6dcf2b7/packages/sdk/identity/src/odis/identifier.ts#L55


add mathjax url setting

useful for cross compatibility with notebook

This will also allow other extensions to reliably

Figure out if mathjax is available
Figure out where mathjax assets are


docs: align package.json serve script (fix #4609)

Modified the template package.json files for preact, react, svelte, vanilla, and vue javascript and typescript projects.

Description
Modified the template package.json files for preact, react, svelte, vanilla, and vue javascript and typescript projects. Based on the documentation for deploying a static site. The npm/yarn commands show preview to run vite preview when the template files have serve for vite preview. Added the command preview to the scripts section in the various package.json template files.
I wasn't sure if the lit-element templates needed a preview command as they were the two templates with out a vite preview command. I am unfamiliar with the framework to know if its needed or not.
Additional context

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[x] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[X] Read the Contributing Guidelines.
[X] Read the Pull Request Guidelines and follow the Commit Convention.
[X] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[X] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

Okay, I've updated the docs for the Deploy a Static Site page to now have the correct command: npm run serve instead of preview. Per the npm docs regarding pre and post scripts, it wouldn't be wise to use preview as a command.

I can add a note about why not pre-view. It's a nice to know, and will add it to the PR.


BaseMatrixOps is empty when installing header files only

When trying to install with header files only, the directory BaseMatrixOps is empty. The following shell command demonstrates the issue, since the last ls statement shows that the directory is empty.
git clone https://github.com/kthohr/optim.git && cd optim && \
./configure --header-only-version && ls header_only_version/BaseMatrixOps

This further causes the following error when trying to compile with #include "optim.hpp"

fatal error: 'BaseMatrixOps/include/BaseMatrixOps.hpp' file not found
#include "BaseMatrixOps/include/BaseMatrixOps.hpp"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Presumably the error message occurs because of this line, i.e., optim.hpp requires the BaseMatrixOps directory to not be empty.
https://github.com/kthohr/optim/blob/d480ec82f97d8fcee9194afbce6b4e9a3cdeccb2/include/optim.hpp#L28

The directory is empty because you did not run:
git submodule update --init


Several typos and inconsistencies in the messages after installing the Keptn CLI

Environment

Client OS (e.g., Linux, macOS, Windows): Linux, Ubuntu 21.04
Keptn Version (keptn version): Installing keptn 0.9.0
Kubernetes Cloud Provider (e.g., GKE, AKS): GKE
Kubernetes version (kubectl version):

Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.2", GitCommit:"092fbfbf53427de67cac1e9fa54aaa09a28371d7", GitTreeState:"clean", BuildDate:"2021-06-16T12:59:11Z", GoVersion:"go1.16.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"20+", GitVersion:"v1.20.8-gke.2100", GitCommit:"4cd085fda961821985d176d25b67445c1efb6ba1", GitTreeState:"clean", BuildDate:"2021-07-16T09:22:57Z", GoVersion:"go1.15.13b5", Compiler:"gc", Platform:"linux/amd64"}

Affected Component

[ ] Docs
[x] CLI
[ ] Kubernetes Integration
[ ] Openshift Integration
[ ] Helm
[ ] Istio
[ ] Bridge
[ ] Approval
[ ] Datastore
[ ] REST API
[ ] eventbroker / distributor
[ ] jmeter

Describe the bug
Several typos and inconsistencies in the messages after installing the CLI. Current text:

Keptn CLI installation completed successfully!
You can check Keptn installation by running:
keptn --help
To install Keptn in your cluser, please follow the documentation https://keptn.sh/docs/ or execute
keptn install
Learn more on how to use Keptn in our tutorials https://tutorials.keptn.sh/
Welcome aboard!

Proposed changes:

Keptn CLI installation completed successfully!
You can check the Keptn CLI installation by running:
keptn --help
To install Keptn in your cluster, please follow the documentation at https://keptn.sh/docs/ or execute:
keptn install
Learn more on how to use Keptn in our tutorials at https://tutorials.keptn.sh/
Welcome aboard!

To Reproduce

Steps to reproduce the behavior:

Run the Keptn CLI installer command: curl -sL https://get.keptn.sh | KEPTN_VERSION=0.9.0 bash

Hi @arthurpitman et. al.,
I've gone ahead and submitted PR 47 for this issue.

@bcdady Thank you for this


Makes hal.tensor.import/export carry tensor encodings and assert better.

This lets us expose an ABI-facing encoding that differs from the actual
SSA value type representing the storage of the tensor internally. It
effectively acts as a silent bitcast where the encoding type never needs
to change throughout the lowering pipeline even if the storage type does
(such as signed/unsigned to signless or complex to 2xf32, etc).
This also required moving the hal.buffer_view.assert op up one layer in
the pipeline from stream->hal to hal->stream and making it more
flexible.
To enable type punning the OPAQUE encoding and element types are
now allowed to bypass the assertion such that an application can say 🤷
and pass in bytes when required.
Integer types are also allowed to cast their signedness so that
interop across environments with different opinions doesn't get in the
way: a tensor<1xui32> is now compatible with tensor<1xi32> and
won't trigger an assertion. Useful for example if the model itself was
defined with a signless type but the frontend (say, numpy) only has
signed/unsigned and can't otherwise pass data in.
Revert "Revert "Adding bf16 and i4 support plumbing in a few places. (#7680)" (#7724)"
This rolls forward commit 7c7ce89.

(Rob says it looks good - may still be some things to work out as what he's doing develops but they'll be built on this)


No highlight for tsx file

Firstly thank you for making the treesitter version context plugin, I am using it for daily development. It really helps.
Today I used it in tsx file, however the treesitter_context window was not highlighted. I confirm I have tsx parser installed and it works normally except in the treesitter_context window. See the picture below

I have no idea whether it's the problem of this plugin or https://github.com/tree-sitter/tree-sitter-typescript, please help

This also happens with bash lsp. But done right with python lsps.

I can reproduce the issue, will look into it soon.

Any news on this? It makes it really hard to read

Please provide a complete testcase and I may be able to look into this. A screenshot isn't sufficient.

close then.


Does not open in the project directory

Windows 10. Tried Cygwin and Windows cmd, both took me to the default directory and not the project folder. Atom v. 1.14.3

+1

Try adding this line in Args --useThisOptionWhenLaunchingTerminal

I fixed this by hacking this package in Atom, by clicking 'View Code' in this package's settings.
Edit the \lib\atom-terminal.coffee file ...
I added the following before the line 'cmdline = ""#{app}" #{args}"':
replace  placeholder in args, if found
args = args.replace('', dirpath);
Then I changed the settings to:
Mac Win Run Directly: true (this may not be needed)
Set Working Directory: false
Suppress Directory Argument: true
App: C:\cygwin64\bin\mintty.exe
Args: --dir  -e /bin/bash
It then works on my Windows 10 PC.
A bit of a hack, but then it is fro Atom. :-)

Looking in the Tips for minty.exe led me to this possible solution:
C:\cygwin64\bin\mintty.exe --dir "%1" /bin/env CHERE_INVOKING=1 /bin/bash -l
But that requires the directory path to be in the middle of the args.
So I hacked this package (click 'View Code' in the package's settings) by editing the /lib/atom-terminal.coffee file. I just added this line after the line starting 'runDirectory =':
args = args.replace('%1', dirpath);
Restarted Atom, adjusted the settings to match the above solution and it works.
HTH


Fix:db-random-test

What problem does this PR solve?
https://github.com/pingcap/tispark/issues/2189
What is changed and how it works?
Change the code because i think is a small bug for the extra space. Besides,it's why the test 'DataGeneratorSuite' fail.
The bug is introduced with https://github.com/pingcap/tispark/pull/2060 in IndexColumn.scala: https://github.com/pingcap/tispark/pull/2060/files#diff-22c8b596e739ebc64046c1c8314c0785d5487b1525834e0c76a37c14de45e43bR116
change the test because the code changes without the test changes.

move clusteredIndex to primary key in Schema.scala: https://github.com/pingcap/tispark/pull/2060/files#diff-ad25d5a6aa3dabb5f06c0ba44a3b17787213469281c9a474349935f11593eec2R98
change some sqls in SchemaAndData.scala: https://github.com/pingcap/tispark/pull/2045/files#diff-262c5d9036ebd92a6208a9233324b90d57608dbe2c72fe1bf0ebf6af55bb770eR29

Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)

Code changes

Has persistent data change

/run-all-test

/run-all-tests

/cc @sunxiaoguang @zhangyangyu @birdstorm

I have added a test to verify the situation without cluster index

/run-all-tests

@birdstorm PTAL


Scale secondary first to higher tier if upscale primary

Regarding section:
Upgrading or downgrading a primary database
You can upgrade or downgrade a primary database to a different compute size (within the same service tier, not between General Purpose and Business Critical) without disconnecting any secondary databases. When upgrading, we recommend that you upgrade the secondary database first, and then upgrade the primary. When downgrading, reverse the order: downgrade the primary first, and then downgrade the secondary. When you upgrade or downgrade the database to a different service tier, this recommendation is enforced.

[!NOTE]
If you created secondary database as part of the failover group configuration it is not recommended to downgrade the secondary database. This is to ensure your data tier has sufficient capacity to process your regular workload after failover is activated.

Suggested edit/review:

Important to reference here:
Primary database in failover group cannot scale to higher tier unless secondary database is scaled to higher tier first. If you try to scale primary database to a higher tier before scaling secondary, it fails with this message:

Error code: .
Error message: The source database 'Primaryserver.DBName cannot have higher edition than the target database 'Secondaryserver.DBName’. Upgrade the edition on the target before upgrading source.

@sqlazure : Thanks for your contribution! The author, @anosov1960, has been notified to review your proposed change.

@MashaMSFT for visibility and awareness

Hi @sqlazure , thank you so much for your suggestion! This is definitely a great note to add. However, your suggestion does not follow proper markdown syntax. Would you mind editing your PR request to be:

[!IMPORTANT]
The primary database in a failover group cannot scale to a higher tier unless the secondary database has been scaled to the higher tier first. Trying to scale the primary database before the secondary database has been scaled may result in the following error:
Error message: The source database 'Primaryserver.DBName' cannot have higher edition than the target database 'Secondaryserver.DBName'. Upgrade the edition on the target before upgrading the source.

Thanks!

@GitHubber17 : Thanks for your contribution! The author, @anosov1960, has been notified to review your proposed change.

@MashaMSFT - I adjusted the content per your feedback. Is the PR ready for merge? Thanks

@GitHubber17 , awesome thanks! Yes, please, #sign-off

@MashaMSFT: I'm sorry - only the author of this article, @anosov1960, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


empty client_secret leads to "Missing credentials" error while request POST oauth/token

SECURITY NOTICE: If you have found a security problem in the UAA, please do not file a public github issue. Instead, please send an email to<EMAIL_ADDRESS>Thanks for taking the time to file an issue. You'll minimize back and forth and help us help you more effectively by answering all of the following questions as specifically and completely as you can.
What version of UAA are you running?
76.31.0
How are you deploying the UAA?
I am deploying the UAA

locally only using gradlew
using a bosh release I downloaded from bosh.io
using cf-release
using cf-deployment
as part of a commercial Cloud Foundry distribution

What did you do?
I am trying to upgrade UAA 76.11.0 to 76.31.0.
During login, the POST oauth/token request with empty secret client_secret: leads the below error.
Request: POST http://access.localhost:8080/uaa/oauth/token
Payload:
grant_type: authorization_code
code: xxxxxxxxxxxxxx
redirect_uri: http://localhost:8084/accessapp/index.html
code_verifier: xxxxxxxxxxxxxxxxxxxxxxxx
client_id: access-blueprint
client_secret:
Response Code: 401 Unauthorized {"error":"invalid_client","error_description":"Missing credentials"}
What did you expect to see? What goal are you trying to achieve with the UAA?
The POST http://access.localhost:8080/uaa/oauth/token request should be return token
What did you see instead?
The POST http://access.localhost:8080/uaa/oauth/token responded with 401 Unauthorized {"error":"invalid_client","error_description":"Missing credentials"}
Is UAA 76.31.0 not support empty secret? is it mandatory to having some secrets?  UAA 76.11.0 secret is not mandatory for clients, Is there any guidelines or policy to not allowing empty secret?

@strehle Thank you for the details.
In my case setting the client_secret: "" in my seed file working for the new clients.
But, lot of existing identity zones clients not working since they are created already with empty client_secret.
How can I migrate the existing clients? or How can I resolve this issue for existing/already created clients?

@strehle Thank you for the details. In my case setting the client_secret: "" in my seed file working for the new clients. But, lot of existing identity zones clients not working since they are created already with empty client_secret. How can I migrate the existing clients? or How can I resolve this issue for existing/already created clients?

I have not verified it, but I am sure that existing clients should have "" as secret.

In my application code now I set the client secret ="", so the newly created client(yellow marked one) has encoded text in the DB for client_secret column, and it authenticated as expected. But the existing clients that have null client_secret are not authenticated.
Shall I update this randomly generated encoded text to the other clients that have null values? or is there any other way to update the null-valued clients?
see the attachment here.

The secret value is a bcryt so please dont know share other values than "" , however the fact that you have many clients with same client_id means they are in different zones ?
Via uaa.yaml you cannot provision this.
Recommendation is: please define a good secret or omit it (null, like your case). Because if you dont want care for secrets, then you can use public flow.
But if you want simply restore what you had, then you need to set "", yes.

I assume this can be closed now ?


Gpiod rpi5

@tomer-w please edit the PR title to give it a nice name and you can merge it to main

@tomer-w  for next time, please make sure the PR has a good title as explained on the discussion, this automatically creates the release notes!


 Resolving deltas: 100% (1142/1142), done. __xsh_git_force_update: INFO: Updating repo to 0.3.3. HEAD is now at 5d64f2d Create __init__.sh [cloudshell-user@ip-10-0-160-20 ~]$ xsh load xsh-lib/aws Cloning into '/home/cloudshell-user/.xsh/repo/xsh-lib/aws'... remote: Enumerating objects: 993, done. remote: Counting objects: 100% (335/335), done. remote: Compressing objects: 100% (182/182), done. remote: Total 993 (delta 194), reused 253 (delta 131), pack-reused 658 Receiving objects: 100% (993/993), 163.59 KiB | 11.68 MiB/s, done. Resolving deltas: 100% (454/454), done. __xsh_git_force_update: INFO: Updating repo to latest. HEAD is now at 7cfe29a fix defect: .xsh/lib/aws/functions/cfn/__init__.sh: line 91: !XSH_AWS_CFN__STACK_STATUS[@]: parameter null or not set

HEAD is now at 7cfe29a fix defect: .xsh/lib/aws/functions/cfn/init.sh: line 91: !XSH_AWS_CFN__STACK_STATUS[@]: parameter null or not set

This line is a normal info message, the "error" is a part of the commit message.
There's nothing wrong here.


fix: Altair 5.5 compat

📝 Summary

Currently, tests/_plugins/ui/_impl/test_altair_chart.py is failing for DuckDB input, because:

previously _data has already been converted to PyArrow Table
now, _data is still a DuckDB PyRelation, which for now only has "interchange" level support in Narwhals. So, in that case, we convert to PyArrow. We plan to greatly improve DuckDB support next year: https://github.com/narwhals-dev/narwhals/discussions/1370

🔍 Description of Changes

📋 Checklist

[ ] I have read the contributor guidelines.
[ ] For large changes, or changes that affect the public API: this change was discussed or approved through an issue, on Discord, or the community discussions (Please provide a link if applicable).
[ ] I have added tests for the changes made.
[ ] I have run the code and verified that it works as expected.

📜 Reviewers

@akshayka OR @mscolnick

I have read the CLA Document and I hereby sign the CLA


Gradle doesn't detect all changes

If a change is only make at a subdocument, for example the glossar, gradle thought that the output is newer than the input and do nothing.

I guess this could be the solution: https://blog.gradle.org/introducing-incremental-build-support


CREATE TABLE Doc Update

Re: CREATE TABLE
Issue Description
The first example creates a table with no primary key, but this is never desirable in CRDB.
Suggested Resolution
Swap the order of the with/without primary key examples. Add a warning to the "no primary key" example indicating that this is supported for compatibility with other databases, but that it's always better to specify a primary key.

Resolving this as a part of this PR: #5075
Will reference this issue in that PR.


Unfreeze the Pipelines version to latest in e2e tests.

e2e tests were frozen to v0.47.2. They should be moved back to the latest.

/assign @khrm
/kind misc


Revert "[Decode] Reasonably assign the first frame slice"

Reverts Intel-Media-SDK/MediaSDK#2893

Because of some platform regression, need to revert it.


Syntax error in the PostgreSQL data transfer replace insert method.

DBeaver 21.3.2
This issue occurred in the case of data import in the PostgreSQL table and enabled setting "Replace method" - "On conflict do update set."
Steps to reproduce:

Create to tables:

CREATE TABLE Employee (
	"Rid" int4 NOT NULL,
	last_name varchar(40) NOT NULL,
	CONSTRAINT employee_pk PRIMARY KEY ("Rid")
);

CREATE TABLE Employee2 (
	"Rid" int4 NOT NULL,
	last_name varchar(40) NOT NULL,
	CONSTRAINT employee2_pk PRIMARY KEY ("Rid")
);

Insert some data in the Employee2 table.
Use right-click on the table Employee2 in the navigator tree and choose "Export data."
Choose "Database" export, select Employee table as a target.
On the Import setting page, choose "Replace method" - "On conflict do update set."
Click on "Proceed"

Expected behavior: Successful export.
Actual: An error appears

Verified


[BEAM-731] Replace DirectRunner with InProcessRunner

Renames InprocessPipelineRunner to DirectPipelineRunner and removes the
existing DirectPipelineRunner. Renamed the folder to direct to keep all
related files in the same folder. Removed inprocess prefix from
file names/class names/comments.
DiskCachedPipelineRunner - not used, and it was a temporary solution
to reduce the memory usage of DirectPipelineRunner. New
DirectPipelineRunner does not have the same amount of memory usage.
EagerPipelineRunner moved to direct folder and changed it to use new
DirectPipelineRunner.

R: @robertwb

@robertwb PTAL

LGTM, thanks!

Thank you


Upload success size parameter not correct for scaled images

Type of issue

[X] Bug report
[ ] Feature request
[ ] Support request

Uploader type

[ ] Traditional
[X] S3
[ ] Azure

Bug Report
Fine Uploader version
5.15.0
Browsers where the bug is reproducible
Chrome (though haven't tested any other browsers)
Operating systems where the bug is reproducible
IOS 10.12.6
Exact steps required to reproduce the issue
For example:

Select 3 files
Pause the 2nd file before it completes, but after it has started.
Attempt to resume the paused file.

All relevant Fine Uploader-related code that you have written
Your Fine Uploader template markup (if using Fine Uploader UI and the issue is UI-related)
{simply copy and paste your template markup}
Detailed explanation of the problem
I have scaling turned on in the S3 uploader.
scaling: {
          sendOriginal: true,

          sizes: [
            {name: 'test', maxSize: 1024}
          ]
}

I also have an uploadSuccess endpoint configured. The problem I am having is that the 'size' parameter of the scaled image is still the original files size, not the scaled images size.
Below are the params sent to the uploadSuccess endpoint for an uploaded file.
key:877ae779-28ae-4da0-9a20-612d7bf4c9c6.jpeg
uuid:877ae779-28ae-4da0-9a20-612d7bf4c9c6
name:Santa-2014 (test).jpeg
bucket:divvito-documents-dev
Content-Disposition:inline; filename=Santa-2014 (test).jpeg
size:2001403
type:image/jpeg
qqparentuuid:78ea76bb-b195-4a62-8fb6-fa5510cd0928
qqparentsize:2001403
qquuid:877ae779-28ae-4da0-9a20-612d7bf4c9c6

key:78ea76bb-b195-4a62-8fb6-fa5510cd0928.jpeg
uuid:78ea76bb-b195-4a62-8fb6-fa5510cd0928
name:Santa-2014.jpeg
bucket:divvito-documents-dev
Content-Disposition:inline; filename=Santa-2014.jpeg
size:2001403
type:image/jpeg
qquuid:78ea76bb-b195-4a62-8fb6-fa5510cd0928

Also to be checked that in the _formatSize method, the size in bytes is being devided by 1000 (1e3), but I guess it should actually be divided by 1024.

1000 is correct, 1024 is not

@rnicholus : If it's in bytes, for me, 1000 would be incorrect. If you convert from bytes to kb's you divide by 1024 and then to mb by 1024 again.

Well, there is no measurement for “kb” or “mb”. If you’re speaking of kB or MB, then powers of ten (SI) is correct. But if you instead want KiB or MiB, then you should use powers of 2. Fine Uploader has been following the SI method for a very long time, and that will not change.

ok. Thanks for the info @rnicholus


[FLINK-23550]  [FLINK-CORE] Support brotli compression algorithm

Brotli is a high performance, high compression ratio compression algorithm. Flink can consider supporting brotli compression algorithm.see https://github.com/google/brotli, thanks

@flinkbot run azure

@flinkbot run azure


pipeline_rnasediffexpression - improve regression tests

I think the new RNAseq pipeline will supersede all of these issues/milestones referring to pipeline_rnaseqdiffexpression


Error processing argument at index 2, conversion failure from #

Version
I am running that latest appimage under Linux mint
BotFramework-Emulator-4.2.0-linux-x86_64.AppImage
I also reproduced the issue with:
BotFramework-Emulator-4.1.0-linux-x86_64.AppImage
Describe the bug
When I start the Bot Framework Emulator, I see the following message:
Error occurred while client was loading: Error processing argument at index 2, conversion failure from #<Object>
When I try to add a bot, I see a very similar error:
Error while setting active bot: Error processing argument at index 2, conversion failure from #<Object>
It may also be relevant that, after adding the bot, I can't communicate with it until after a change is made in the settings. It doesn't matter what is changed there only that I change something. (Checking auth boxes, changing localhost override... they all do the trick). This issue appeared at the same time as the argument processing error so I believe they have the same root cause.
To Reproduce
Open AppImage
Check notifications
I cannot reproduce this issue on other systems. It appears something is broken in my local environment.
Expected behavior
No error
No need to go to settings and make an arbitrary change before bot can be accessed.
Additional context
When I run 4.1.0 from the CLI is get the following more detailed output:
TypeError: Error processing argument at index 2, conversion failure from #<Object>     at Object.normal (/tmp/.mount_BotFrabt0Yn0/app/resources/electron.asar/browser/api/menu.js:260:24)     at Menu.insertItemByType (/tmp/.mount_BotFrabt0Yn0/app/resources/electron.asar/browser/api/menu.js:287:19)     at Menu.insert (/tmp/.mount_BotFrabt0Yn0/app/resources/electron.asar/browser/api/menu.js:111:20)     at Menu.append (/tmp/.mount_BotFrabt0Yn0/app/resources/electron.asar/browser/api/menu.js:102:15)     at positioned.forEach (/tmp/.mount_BotFrabt0Yn0/app/resources/electron.asar/browser/api/menu.js:178:10)     at Array.forEach (<anonymous>)     at Function.Menu.buildFromTemplate (/tmp/.mount_BotFrabt0Yn0/app/resources/electron.asar/browser/api/menu.js:174:14)     at new MenuItem (/tmp/.mount_BotFrabt0Yn0/app/resources/electron.asar/browser/api/menu-item.js:19:25)     at positioned.forEach (/tmp/.mount_BotFrabt0Yn0/app/resources/electron.asar/browser/api/menu.js:178:17)     at Array.forEach (<anonymous>)     at Function.Menu.buildFromTemplate (/tmp/.mount_BotFrabt0Yn0/app/resources/electron.asar/browser/api/menu.js:174:14)     at new MenuItem (/tmp/.mount_BotFrabt0Yn0/app/resources/electron.asar/browser/api/menu-item.js:19:25)     at positioned.forEach (/tmp/.mount_BotFrabt0Yn0/app/resources/electron.asar/browser/api/menu.js:178:17)     at Array.forEach (<anonymous>)     at Function.Menu.buildFromTemplate (/tmp/.mount_BotFrabt0Yn0/app/resources/electron.asar/browser/api/menu.js:174:14)     at AppMenuBuilderImpl.buildFromTemplate [as refreshAppUpdateMenu] (/tmp/.mount_BotFrabt0Yn0/app/resources/app.asar/src/appMenuBuilder.ts:435:52) From previous event:     at AppImageUpdater._checkForUpdates (/tmp/.mount_BotFrabt0Yn0/app/resources/app.asar/node_modules/electron-updater/src/AppUpdater.ts:282:33)     at AppImageUpdater.checkForUpdates (/tmp/.mount_BotFrabt0Yn0/app/resources/app.asar/node_modules/electron-updater/src/AppUpdater.ts:221:35)     at Object.checkForUpdates (/tmp/.mount_BotFrabt0Yn0/app/resources/app.asar/src/appUpdater.ts:137:25)     at BrowserWindow.checkForUpdates (/tmp/.mount_BotFrabt0Yn0/app/resources/app.asar/src/main.ts:363:18)     at Object.onceWrapper (events.js:315:30)     at emitOne (events.js:116:13)     at BrowserWindow.emit (events.js:211:7)

I was able to recover by deleting the electron app config settings.
Remove the following:
~/.config/@bfemulator/
If I figure out how to repro the problem I'll open a separate issue, but things are running smoothly for me again so I'm happy.
I also ran git diff --no-index @bfemulator @bfemulator_original, and didn't see any obviously bad differences with the non-binary files.


Convert HTML to Markdown in place if code snippets are selected

If the HTML code is selected the conversion to Markdown is now performed in place, without opening a new tab.
Use case: adding (HTML) content to existing markdown documents.
The explicit type Promise<void> was causing the error Illegal value for 'line' documented here

Thanks David, this is a good enhancement.
I don't see any place says explicit type  Promise<void> causes error Illegal value for 'line', after the code translated into js, the type annotation is gone, how can it impact the program in runtime?


Add Image Zoom plugin

Add Image Zoom to list of Community Plugins

Motivation
(Write your motivation here.)
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work. Bonus points for screenshots and videos!)
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

Cool, I put a shout out to the Medium Zoom plugin at the top.


Add Rubocop to Jenkins

This branch adds Rubocop to our Jenkins test suite.
Rubocop is supplied by the govuk-lint Gem along with a set of rules that correspond to the GOV.UK styleguides.
Rubocop only checks for violations in the diff introduced in the current branch. This should help us avoid introducing new violations of the styleguide without first having to fix all existing violations.

I'm not a fan of breaking a build due to style violations, because in my experience automated tools are not perfect at detecting them. However, if I'm right gov-uk-lint will only execute in the build that runs in the background and builds regression tests, so it's a nice solution. Perhaps it's worth clarifying that in the README?
Looks good to me :+1:

However, if I'm right gov-uk-lint will only execute in the build that runs in the background and builds regression tests, so it's a nice solution.

Nope :-) This configuration actually runs gov-uk-lint before running rake test on Jenkins, not before running the regression tests.
My preference would still be to add this to Jenkins and to monitor it. If it starts getting painful then we should re-evaluate.


Use variable to represent CLI executable path

CLI location is changing and this will affect the catalog repository.  Updating the catalog script to allow the CLI path to be passed in as a variable.

pg2#163


Incorrect issue count

The issue count is not updating for a repo under "Repos you are currently helping".  The screenshot below is an example of the issue count for the Spree repo that show 315 issues

but when you go to the repo, there's only 225 issues

Expected Behavior
The issues count should update to reflect the actual number of issues on the GitHub repository.
Current Behavior
The issue count is not updating to reflect the actual number of issues on the GitHub repository.
Possible Solution
Update the issue count to match the number of issues on a GitHub repository.
Steps to Reproduce (for bugs)

Log onto Code Triage
View repo count under "Repos you are currently helping"

Cause of the issue
The number of issues is the number of issues and pull requests open in the request (225 issues + 90 pull requests = 315).
GitHub considers pull requests as issues in their api. I have gotten all their issues using the GitHub cli
# Getting all issues
$ gh api --paginate repos/spree/spree/issues | jq '.[].html_url'
"https://github.com/spree/spree/issues/11934"
"https://github.com/spree/spree/pull/11932"
[...]
# Counting all issues
$ gh api --paginate repos/spree/spree/issues | jq '.[].html_url' | wc -l
315

An example issue (spree/spree#11934)
{
  "url": "https://api.github.com/repos/spree/spree/issues/11934",
  "repository_url": "https://api.github.com/repos/spree/spree",
  "labels_url": "https://api.github.com/repos/spree/spree/issues/11934/labels{/name}",
  "comments_url": "https://api.github.com/repos/spree/spree/issues/11934/comments",
  "events_url": "https://api.github.com/repos/spree/spree/issues/11934/events",
  "html_url": "https://github.com/spree/spree/issues/11934",
  "id":<PHONE_NUMBER>,
  "node_id": "I_kwDNDPLOcceiNA",
  "number": 11934,
  "title": "Support Rails 7.1",
  "user": {},
  "labels": [],
  "state": "open",
  "locked": false,
  "assignee": null,
  "assignees": [],
  "milestone": null,
  "comments": 0,
  "created_at": "2023-09-22T13:25:55Z",
  "updated_at": "2023-09-22T13:25:55Z",
  "closed_at": null,
  "author_association": "MEMBER",
  "active_lock_reason": null,
  "body": null,
  "reactions": {},
  "timeline_url": "https://api.github.com/repos/spree/spree/issues/11934/timeline",
  "performed_via_github_app": null,
  "state_reason": null
}

An example pull request (spree/spree#11932)
{
  "url": "https://api.github.com/repos/spree/spree/issues/11932",
  "repository_url": "https://api.github.com/repos/spree/spree",
  "labels_url": "https://api.github.com/repos/spree/spree/issues/11932/labels{/name}",
  "comments_url": "https://api.github.com/repos/spree/spree/issues/11932/comments",
  "events_url": "https://api.github.com/repos/spree/spree/issues/11932/events",
  "html_url": "https://github.com/spree/spree/pull/11932",
  "id":<PHONE_NUMBER>,
  "node_id": "PR_kwDNDPLOWm58cg",
  "number": 11932,
  "title": "Improve line item packaging",
  "user": {},
  "labels": [],
  "state": "open",
  "locked": false,
  "assignee": null,
  "assignees": [],
  "milestone": null,
  "comments": 4,
  "created_at": "2023-09-15T11:40:56Z",
  "updated_at": "2023-10-02T09:59:02Z",
  "closed_at": null,
  "author_association": "NONE",
  "active_lock_reason": null,
  "draft": false,
  "pull_request": {
    "url": "https://api.github.com/repos/spree/spree/pulls/11932",
    "html_url": "https://github.com/spree/spree/pull/11932",
    "diff_url": "https://github.com/spree/spree/pull/11932.diff",
    "patch_url": "https://github.com/spree/spree/pull/11932.patch",
    "merged_at": null
  },
  "body": "Fixes #8621 \r\nMore context is provided in the original issue and in each commit body.",
  "reactions": {},
  "timeline_url": "https://api.github.com/repos/spree/spree/issues/11932/timeline",
  "performed_via_github_app": null,
  "state_reason": null
}

Possible solutions

[!IMPORTANT]
I do not know how to program in Ruby and have not tested these solutions, so take them with a grain of salt.

Maybe we could filter the list of issues by checking that the "pull_request" field does not exist while counting.
https://github.com/codetriage/CodeTriage/blob/a86e568030ff0639a798f0f52735182ad961ad58/app/models/repo.rb#L146-L151
We could also filter while fetching the API (See https://stackoverflow.com/a/66348538/1336930)
If this is a desired behavior, maybe we should change the card and replace "Issue" by "Issue & PR"
https://github.com/codetriage/CodeTriage/blob/a86e568030ff0639a798f0f52735182ad961ad58/app/views/repos/_repo.html.slim#L1-L8

@Mattherix I thought that maybe there was a mistake in the issue count, but from the above code I can see how its being calculated.

Github used to classify PRs as issues with code attached. It's how I still think about them. We have the info to separate out PRs. I think that's how most newer developers would think about them
Changing the UI is always tricky. We don't have any long term maintainers that are "visual/frontend" folks. That would be my biggest hesitation to adding this info to the UI: Need to iterate on visuals.


Add Index to ReadMe

Microsoft sql-docs ReadMe.md lacked an index. Hence added one.

@cursed4ever : Thanks for your contribution! The author, @, has been notified to review your proposed change.

@craigg-msft - Would you review the proposed changes? Thanks

Thank you @cursed4ever for the help.  merging.


Remove version check workaround

The additional check here can be removed, because now all 'specific-version' record list items will always have a record guid.

@Andy-Grigg  I just had a look at this. I don't think we can remove the check. For a draft v2, superseding a released v1, list item defined with record_version=2:

The item has a record_guid for the admin user
The item does not have a record_guid for a list user. Which means the resolvability check still queries the full history and if we then don't check for the specific version, we'll get false positives.

Is that what you would expect? I think it sort of makes sense: read users can't see draft records, therefore can't get their record guids.

Well, there's three scenarios within the scenario you describe:

If the list item doesn't have a version specified, I'd expect RL to return just the history guid, which we can resolve
If the list item has v1 specified, RL should return the v1 record guid which we can resolve
If the list item has v2 specified and RL returns no guid (makes sense because as you say, the user can't see the record), and so we should then return a negative result, i.e. don't include the record in the resulting list

Does the check for the final scenario become: "If the record list item contains a record version but no record guid, discard"?

After discussion, we're going to leave the code as is. The check described above

Does the check for the final scenario become: "If the record list item contains a record version but no record guid, discard"?

Would work, and would reduce the number of calls required to the database, but only in the specific scenario described above. The trade off is that it feels like a more fragile scenario: if the record guid is missing for any other reason, we'll end up with a false negative, and we can't be certain that this is the only reason the record guid would be missing.


Add missing -verbosity option to apps/cmp.c and add log output also in crypto/cmp

Extend log output, which is important for debugging CMP applications
in particular with non-trivial failures of certificate validation and cert chain building.

Add -verbosity option to apps/cmp.c, which had been missing so far such that debug outpug was invisible.
Add log output in setup_ssl_ctx() of the cmp app, ossl_cmp_msg_add_extraCerts(),
OSSL_CMP_validate_msg(), and OSSL_CMP_MSG_http_perform().
Correct suppression of log output with insufficient severity.
Add logging/severity level OSSL_CMP_LOG_TRACE = OSSL_CMP_LOG_MAX.

Checklist

[x] documentation is added or updated
[ ] tests are added or updated

This extension is important for the usability of the CMP application.
Therefore I'd appreciate a swift review such that this PR can be merged before feature freeze on the beta1 release.

Thanks a log for the immediate response!

Except the build failure is relevant.

I think I found and fixed the reason - a strict compiler warning that my gcc did not give.

Still strict warning related failures

Still strict warning related failures

Ah yes - second try...

Meanwhile found a simpler and cleaner solution, and also those gcc versions are happy with it :)
The delta is in the fixup commit.

This pull request is ready to merge

Merged - thanks @t8m


(UNTESTED / W.I.P) Improve cat.js so that it doesn't need an API

Just needs to be tested, which I will do later. But if you test it and it works, then feel free to merge this pull request.

I fixed it and looks good


Azure ML deployment: setting low memory request not taking effect

Describe the bug
Even if I set smaller than 500 MB memory request for the Azure ML deployment, at least 500 MB is always requested (as I understand, because of the storageinitializer init container).
Related command
az ml online-deployment create
Errors
(There is no error, but it does not work as expected.)
Issue script & Debug output
In Azure Machine Learning, there is an inference cluster named "reco-inference" which is a Azure Kubernetes cluster.
There is a custom instance type named "smallmemoryinstancetype" with 100Mi memory request, created like this:
kubectl apply -f smallmemory_instancetype.yaml

where the smallmemory_instancetype.yaml file contains:
apiVersion: amlarc.azureml.com/v1alpha1
kind: InstanceType
metadata:
    name: smallmemoryinstancetype
spec:
    resources:
    limits:
        cpu: "1"
        memory: "2Gi"
    requests:
        cpu: "10m"
        memory: "100Mi"

There is an azure ML environment: "machine-learning-recommendation-environment:12" (Linux, python version: 3.8).
There is a previously registered model: name: "modelname", version: 1. (Model artifact binary size: 78 mb.)
There is an endpoint named "endpointname" created like this:
az ml online-endpoint create --name endpointname --set compute=azureml:reco-inference

We deploy like this:
$azuremlModelId = "azureml:modelname:1"
az ml online-deployment create --name deploymentname -f deploymentConfigTest.yaml --set endpoint_name=endpointname --set model=$azuremlModelId --set environment=azureml:machine-learning-recommendation-environment:12

where deploymentConfigTest.yaml is:
type: kubernetes

app_insights_enabled: true

code_configuration:

  code: .

  scoring_script: score.py

request_settings:

  request_timeout_ms: 3000

  max_queue_wait_ms: 3000

instance_type: smallmemoryinstancetype

instance_count: 1

scale_settings:

  type: default

The deployment is successful. It appears in kubectl describe node as a pod. I can verify that the instance type is successfully set for the deployment (at the endpoint in Azure Machine Learning Studio).

When inspected with kubectl describe node, I can see the Memory Requests for the pod of my deployment.
It is exactly 500Mi.
Non-terminated Pods:          (13 in total)
  Namespace                   Name                                         CPU Requests  CPU Limits    Memory Requests  Memory Limits  Age
  ---------                   ----                                         ------------  ----------    ---------------  -------------  ---
  default                     deploymentname-endpointname-54d8bf5d5w9dz    110m (5%)     1100m (57%)   500Mi (10%)      2098Mi (45%)   18h
  ...

(I also verified that if I use an instance type with more than 500Mi memory request then more than 500Mi will be used, so the instance type setting itself is taking an effect on memory requests.)
As I understand, this is because of the storageinitializer init container (that is in the same pod as my inference server), where memory request is a fixed 500Mi amount.
For example, in the pod settings inspected in Lens, I see these settings for the init container:
initContainers:
- name: storageinitializer-modeldata
  ...
  resources:
    limits:
      cpu: 100m
      memory: 500Mi
    requests:
      cpu: 100m
      memory: 500Mi
  ...

Expected behavior
I would expect the Memory Requests for the pod of my deployment to be set to a smaller amount than 500Mi.
Environment Summary
OS: Azure DevOps windows-latest agent (Windows Server 2022 with Visual Studio 2022)
azure-cli                         2.53.1
core                              2.53.1
telemetry                          1.1.0
Extensions:
azure-devops                      0.26.0
connectedk8s                       1.5.2
k8s-extension                      1.5.1
ml                                2.21.1
Dependencies:
msal                            1.24.0b2
azure-mgmt-resource             23.1.0b2
Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\PannaKristof.azure\cliextensions'
Python (Windows) 3.10.10 (tags/v3.10.10:aad5f6a, Feb  7 2023, 17:05:00) [MSC v.1929 32 bit (Intel)]
Additional context
My question is: why is the memory request I set on my deployment not taking an effect on the init container also?
Is there any other (maybe completely different) solution to achieve smaller memory request for the init container? (For example, it would be ideal if I could set the request size for the init container also dynamically when running the online-deployment create command.)
The reason for my question: we would like to deploy several small deployments, but it is very wasteful to use 500 MB memory for each of them (when eg. 65Mi would be sufficient).
(Or is it possible that the init container actually needs this much space to work and I should not try to set the memory request?)
Thank you in advance for your help!

Thank you for opening this issue, we will look into it.


XML#parse not working for response.body_io

The XML#parse(io : IO) method seems not working correctly on response.body_io.
require "http/client"
require "xml"

url = "https://eutils.ncbi.nlm.nih.gov/entrez/eutils/esummary.fcgi"
form = {
  "db" => "gene",
  "id" => "1956"
}

HTTP::Client.post_form(url, form) do |response|
  if response.status_code == 200
    # xml = XML.parse(response.body_io.gets_to_end) # this is ok
    xml = XML.parse(response.body_io) # not working
    p xml.to_xml
  end
end

Btw, the same example on play gave the following error:

Program received and didn't handle signal SYS (31)

@need47 When you say "seems not working correctly", what do you mean? I ran the snippet and it worked fine (outside of the playground)

@asterite the snippet compiled and ran fine, while the output is not right. Basically I'm getting an empty xml now. But I'm expecting this: https://eutils.ncbi.nlm.nih.gov/entrez/eutils/esummary.fcgi?db=gene&id=1956

Hmm... for some reason xml doesn't like to be fed small chunks of bytes. This happens because the current ssl socket is not buffered. If I change it to buffer it starts working well. I guess that's a solution though I don't know why libxml works wrong otherwise.

@asterite thanks for the quick fix.


Use separate keys to address sink partitions

This is for @rajkiranrbala to review and see if that'll address the concurrent issue we discussed today (I asked @rajkiranrbala to create a Github issue for this too).

Coverage decreased (-0.9%) to 85.917% when pulling 9d33a7d41ada55a72a39721b7969af1ed46762e1 on jsdelfino:sinkpart into a7e2af449997cf3109178ac89010175d479049af on cloudfoundry-incubator:master.

Merged in #363.


ValueError: Expected object or value

@zchee Every time I open a blank new file and write pa in insert mode (in order to write package main) I have the following error in the vim bar:
[deoplete] Traceback (most recent call last):
[deoplete]   File "/Users/tibor/.vim/plugged/deoplete.nvim/rplugin/python3/deoplete/deoplete.py", lin
e 124, in gather_results
[deoplete]     ctx['candidates'] = source.gather_candidates(ctx)
[deoplete]   File "/Users/tibor/.vim/plugged/deoplete-go/rplugin/python3/deoplete/sources/deoplete_go
.py", line 110, in gather_candidates
[deoplete]     context, getlines(self.vim), bufname)
[deoplete]   File "/Users/tibor/.vim/plugged/deoplete-go/rplugin/python3/deoplete/sources/deoplete_go
.py", line 260, in get_complete_result
[deoplete]     return loads(stdout_data.decode())
[deoplete] ValueError: Expected object or value
[deoplete] Could not get completions from: go.  Use :messages for error details.

@tiborvass Thanks issue.
Sorry, now I'm in the hospital, so difficult to fix and debug, but I will check it.

@zchee oh! I wish you the best! Health first, projects second ;) Good luck

@tiborvass I'm very happy about your words :)
Thanks!!

@tiborvass Sorry for the late reply.
I'm back. I'll debug and fix this problem. Thanks for using deoplete-go.

@tiborvass BTW, it seems to you using vim-plug plugin manager.
FYI, I use Shougo/dein.vim and set lazy load. actually, add deoplete-go to &runtime is go filetype only. If that situation, not reproduced(maybe, on daily coding).
Are you use vim-plug lazyload feature?

I have the same problem. I tried to disable lazy-load and still can reproduce.

@LK4D4 Thanks for reports. Hmm... I'll try to debug.
Just in case, @tiborvass said the situation is below?
$ ls test.go
ls: cannot access 'test.go': No such file or directory
$ nvim test.go
# in Neovim...

pa|

@zchee yes I still have that issue in that situation

@tiborvass Thanks. and OK, not reproduced with use the dein.vim.
I'll try to debug and fix it for users who uses other plugin managers such as vim-plug.

Hope you're better!

:D

@tiborvass @LK4D4 I added Dockerfile for the clean test environment for now.
See dockerfiles/Dockerfile@011c2cc and run:
docker build --rm -t zchee/deoplete-go -f dockerfiles/Dockerfile .
# test for exist file
docker run --rm -ti zchee/deoplete-go nvim test.go
# test for **not** exist file
docker run --rm -ti zchee/deoplete-go nvim test2.go

But not reproduced :(
Do you have any idea for reproducing?

I have the same issue. MacOS X 10, nvim NVIM v0.2.0-779-g58b5e14, latest vim-go and deoplete.
Anytime I press ^X^O to autocomplete I get this error.

This is not really a deoplete-go issue, but a gocode issue.
If anything, deoplete-go could be more helpful in showing the error message from the output (both stdout and stderr) of the gocode tool, which in this case should have shown a nil dereference panic stacktrace.


Let clowns and mimes rename themselves on spawn

About the PR
Will let clowns and mimes give themselves a funny name when they arrive on station
Screenshots

Changelog

:cl:

add: Clowns and Mimes can now give themselves funny names when they arrive on the station!

are you still working on this? I'm considering doing it

are you still working on this? I'm considering doing it

Probably not any time soon, feel free to do it


add support for "use latest"

This closes #440

I've merged this PR, but I'm going to modify the keywork from "latest" to "newest"... i.e. nvm use newest will use the newest version of Node installed on the system. This will prevent a conflict with nvm use latest, which is another PR that was merged, which will identify the latest Node release (i.e. on nodejs.org).


Suggestion: Create Installer for Angular CLI

Versions
Angular CLI: 1.7.4
Node: 8.11.1
OS: win32 x64
Angular:
...

Repro steps
I'm trying to setup a private NPM server, in an offline environment (without connection to the world-wide-internet). This server need to serve Angular tools (and CLI primarily) in such way the clients could create new project - without having to manually include node_modules dependencies folder in every project (so using --skip-install flag is not an option).
The steps I did:

Running Verdaccio (private npm cache) in an ONLINE environment.
Installing all Angular's related packages (including CLI, compiler, etc) through Verdaccio in order to cache them.
Moving the cached packages into the the private NPM server (OFFLINE ENVIRONMENT), also with Verdaccio (acting as private npm server)
Setup the npm server to serve NODE-SASS package with the desired version (because Angular's CLI requires to download it at the installation's end).
Setting the offline-clients to use the private npm server & setting their npmrc file with "sass_binary_site" variable
After all the steps above - offline clients can install Angular CLI successfully, but when trying to create Angular CLI project, using "ng new" -> the process fails because of missing dependencies - although all the dependencies are exist in the private npm server!

Desired behavior
I think it's about time that such great tool like Angular CLI would have an OS installer (exe/deb and so on).
Trying to setup Angular offline development environment normally (without having to use weird/ugly tricks such as sharing node_modules folder or caching local packages as suggested here) seems to be impossible mission. really.
Yarn have their own installer as alternative option, so I really think that Angular should have such too.
The installer just needs to pack the base packages of Angular in order to enable creation & deployment of basic Angular project - without internet connection. Nothing more than that.
If you can tell me what I did wrong in the steps above, I would like to hear. But I really can't figure it out myself.

I feel like there's an issue with angular-cli that many people discuss, but nobody on the angular team seems to take seriously AT ALL: an offline non-binary install package.
It should be VERY easy to download a package from git, transfer it to a non-internet enclave, and install it with even a FEW commands, but it ought to be as simple as:
npm install angular-cli-.tgz --offline
And then have ALL dependencies included in the TGZ's internal package.json.
Otherwise, what the angular team is REALLY saying is, we don't want you using our product unless you have ONE GLARING DEPENDENCY:
an internet connection.
There are plenty of development environments where the requirement is an enclave WITH NO INTERNET CONNECTIVITY.  Seriously... has nobody at angular heard of OWASP? or STIGs? One of the LARGEST user communities for web applications is defense; yet, it appears nobody has seriously considered creating a fairly easy-to-use, COMPLETE offline installer package, that does NOT require an EXE or MSI to use.
And FWIW, before someone trolls me on this, yes, I am working on the problem.
Someone over there, start taking this seriously. Or it'll start being obvious that developers should stop taking Angular seriously.
< /rant >

@pjblecha thanks for your feedback. We totally agree that the dependency on fetching more packages at runtime hurts the usability of the CLI, and we're discussing ways to fix that.

@pjblecha thanks for your feedback. We totally agree that the dependency on fetching more packages at runtime hurts the usability of the CLI, and we're discussing ways to fix that.

That's great. I will actually appreciate it when I can actually reap the benefits of that effort.

Any news on this?


Add gulp task for revisioning main.js and main.css with a content hash

Added a gulp task to revision the main.js and main.css assets.  Basically, this gulp task will append a content hash to the main.css and main.js files (e.g. main.css -> main-a1f3e211.css) and replace the file paths in the index.html file.

Yes, would be nice to have a way to clear the cache.

So, any luck with making this a standard part of the boilerplate?

This is what I'm getting here:
`"C:\Program Files (x86)\JetBrains\WebStorm 2016.1\bin\runnerw.exe" "C:\Program Files\nodejs\node.exe" C:\www\genolab\genolab-frontend\client.js\src\main\webapp\node_modules\gulp\bin\gulp.js --color --gulpfile c:\www\genolab\genolab-frontend\client.js\src\main\webapp\gulpfile.babel.js prod
[14:52:18] Requiring external module babel-register
[14:52:25] Using gulpfile c:\www\genolab\genolab-frontend\client.js\src\main\webapp\gulpfile.babel.js
[14:52:26] Starting 'clean'...
[14:52:26] Starting 'views'...
[14:52:26] Finished 'views' after 130 ms
[14:52:26] Finished 'clean' after 178 ms
[14:52:26] Starting 'prod'...
[14:52:26] Starting 'views'...
[14:52:26] Starting 'styles'...
[14:52:26] Starting 'images'...
[14:52:26] Starting 'fonts'...
[14:52:26] Starting 'libraries'...
[14:52:26] Finished 'libraries' after 10 ms
[14:52:26] Starting 'browserify'...
[14:52:26] Rebundling...
[14:52:26] Finished 'fonts' after 44 ms
[14:52:27] Finished 'images' after 1.26 s
[14:52:45] Finished 'browserify' after 19 s
[14:52:45] Finished 'views' after 19 s
[14:52:45] Finished 'styles' after 19 s
[14:52:45] Starting 'revisionAssets'...
[14:52:45] DELETED: "c:\www\genolab\genolab-frontend\client.js\src\main\webapp\build\css\main.css"
[14:52:45] DELETED: "c:\www\genolab\genolab-frontend\client.js\src\main\webapp\build\js\main.js"
[14:52:45] Finished 'revisionAssets' after 91 ms
[14:52:45] Starting 'gzip'...
events.js:141
throw er; // Unhandled 'error' event
^
Error: EPERM: operation not permitted, lstat 'c:\www\genolab\genolab-frontend\client.js\src\main\webapp\build\js\main.js'
at Error (native)
Process finished with exit code 1
`

Hey all,
I'm going to close this.  I haven't had much time recently to dig into this on windows or verify that this works across npm versions.  Feel free to clone the branch from my repo or PM me for more details.


[Feature Request] Wait for branches to be ready rather than exiting when connecting

Hey everyone! It would be absolutely superb if the CLI would wait for branches to be ready rather than exiting completely in the following scenario:

Adding my +1 to this issue — I'm finding myself losing focus and flow because the state of a branch being created is unpredictable, which requires randomly retrying the connect command over and over. Some kind of waiting state on the branch create call would make it a lot more clear what PlanetScale is doing and inform when it's ready for me to develop against. Thanks!


Is it possible to cast "PyObject*" to "object" without incrementing refcount?

Let's suppose I have a C function that returns a NEW reference to PyObject. And then I want to call it and return it's result from a function that returns object. Currently if I simply do something like this:
def pyfunc():
    return <object>PyDict_New()

There will be refcount increment in the generated pyfunc() code for the returned dict which is undesirable.
My question is - is there a canonical solution to this problem?

You should really use return {} instead.
Apart from that, the whole point of object is to be refcounted. That is the difference to PyObject*, which is a pointer.
My guess is that you declared PyDict_New() as returning a PyObject*. That is incorrect. It returns an owned reference, i.e. object.

Please ask this kind of question on the cython-users mailing list in the future. The bug and issue tracker is only for tracking bugs and issues.

@scoder

Apart from that, the whole point of object is to be refcounted. That is the difference to PyObject*, which is a pointer.

Makes sense.

My guess is that you declared PyDict_New() as returning a PyObject*. That is incorrect. It returns an owned reference, i.e. object.

I ended up implementing this solution.

Sorry for insisting, but I was quite serious about this bit, actually:

You should really use return {} instead.

In this case, it happens to translate into the same C code as calling PyDict_New(), but using normal Python syntax and idioms in Cython code helps avoiding human mistakes (like the one that lead to this ticket), keeps the code easier to read and more maintainable, and allows Cython to generate more efficient code in many cases. It's really a win-win-win approach.
Only hand-tune your code if you really know and can prove in actual numbers that it's worth the added complexity. That applies to Cython in the same way as Python.
And, if you ever find a situation where you can write better C code than what Cython generates, consider improving Cython, so that all Cython users can benefit from it.

@scoder

You should really use return {} instead.

I used PyDict_New() as an example of a function that returns a new reference, in reality I call another function from some user-made extension.
What would you say about functions like PyTuple_GET_ITEM()? Is it normal to use them? I've found out that writing them by hand in Cython files gives slight speed advantage.

What would you say about functions like PyTuple_GET_ITEM()? Is it normal to use them? I've found out that writing them by hand in Cython files gives slight speed advantage.

Have you tried @boundscheck(False)? That's more likely to make a difference here than the reference counting.


[wip] : Sensor Services

This PR aims to take use of ros services to communicate and send instructions/commands to the sensors. The umrr sensors come with different operation modes and features which could be accessed through the services.

We are able to configure the IP address of the sensor providing a separate service for it. In order to successfully configure the IP address , after executing the service the sensor and the node must be restarted with the new sensor_ip value in the radar_param file.
Could be done with the following call:
ros2 service call /smartmicro_radar_node/configure_ip_address umrr_ros2_msgs/srv/SetIp "{value_ip:<PHONE_NUMBER>, sensor_id: x}"
The value of the IP address must be a DEC which is converted from HEX for e.g<PHONE_NUMBER> -> C0A8 0B99 -> <IP_ADDRESS>.

Thought I would run through a review while I was responding to another issue.

@JWhitleyWork Thanks for your review, I will look into it in n detail and make the required changes.


Bugfix/issue 1152 ccdf sigs

Summary:
Intended Effect:

Raise warning from Stan parser when attempting to use CDF or known non-distribution with _log suffix with sampling notation.

Soften the "Jacobian-required" message to a warning conditioned on checking non-linearity (same file, so I couldn't pass it up).

Fix bug in warnings tests in parser test utiliy leading to false negatives on warnings test (still no idea why the old way didn't work --- maybe a macro resolution syntax issue?).

How to Verify:

New models tickling new warnings in parser unit test for statement grammar.

Unit test for warning in statement grammar.

Revised test for Jacobian messages in statement grammar unit test will fail as before (but not as the test was written before), but the revised test will pass.

Side Effects:
None (models wouldn't compile before and will fail with warning message now)
Documentation:
None --- this brings behavior in line with doc.
Reviewer Suggestions:
Anyone.

Looks good.


reactivity does not accept default or initial as names

Describe the bug

When trying to initialize state from props named default or initiall, an error is shown.
To Reproduce

import { createSignal, type FlowProps } from 'solid-js';

export type FailProps = Props<{ default: number, initial: string }>;

export default function Failure(p: FailProps) {
  createSignal(props.default)
  createSignal(props.initial)
}

Expected behavior

No Error is shown.
Environment (please complete the following information):

OS: Ubuntu Server 22
Node version: v20.11.0
eslint-plugin-solid version: 0.14.2
eslint version: 8.57.0

Additional context

I think this might be intentional, but I couldn't find anything to prove that.

[X] I would be willing to contribute a PR to fix this issue

https://github.com/solidjs-community/eslint-plugin-solid/blob/main/packages/eslint-plugin-solid/src/rules/reactivity.ts#L578
I wouldn't mind if you changed the regex there to accept initial or default, that's fine! I don't think we should static on its own though, as it really does need to be a prefix to make sense.

yeah, it would be useful if @once would work on types:
export interface MyProps {
  /** @once */
  staticThing: string;
}


Change wildcard qualifier type from String to TableReference

Which issue does this PR close?

Closes #11072.
Rationale for this change

This PR changes the wildcard qualifier type to TableReference. This avoids an implicit SQL parsing during logical planning, and makes the API more consistent.
What changes are included in this PR?

The PR changes the wildcard qualifier type for Expr::Wildcard and updates the .proto file.
Are these changes tested?

The changes are covered by existing tests.
Are there any user-facing changes?

Yes, this PR contains breaking changes to the public API.

Thank you @alamb ! I've updated the protobuf code as suggested.


MSE Loss Function and corresponding test

I have implemented the MSE Loss function as discussed in the #654 and the corresponding test.

looks like there are some linting issues @burhanusman -- running make lint should allow you to reproduce locally

Hey @mortendahl,
I have fixed the lint errors, but am getting some other errors which I'm not sure how to go about exactly. Can you please take a look?
tensorflow.python.framework.errors_impl.InvalidArgumentError: Cannot assign a device for operation

private-input/encode/mul: node private-input/encode/mul (defined at

/home/circleci/repo/tf_encrypted/protocol/pond/pond.py:718) was explicitly assigned to

/job:localhost/replica:0/task:0/device:CPU:5 but available devices are [

/job:localhost/replica:0/task:0/device:CPU:0, /job:localhost/replica:0/task:0/device:XL

A_CPU:0 ]. Make sure the device specification refers to a valid device.

Thanks.

Sure, let me take a look tomorrow. Do you want me to push any fixes I might have directly to your branch?

Thanks a lot @mortendahl. Please feel free to push any changes to this branch.

I haven't been able to reproduce the error @burhanusman; happy to merge this up as is. @yanndupis would you mind leaving a review on the ML logic for good measures?
I believe what happened in your case is a mix-up between graphs, perhaps due to a race condition in the way we are currently testing the code. Improving testing in general is on the road map.

Hey @mortendahl @burhanusman , I will review this tomorrow first in the morning. thanks!

@burhanusman @mortendahl , the logic looks good 💪! Just need to fix linting. There is space missing around the function test_mean_squared_error. But even we that, I am a bit surprise that circle.ci is complaining.

Thanks @mortendahl!

My pleasure. Thank you for submitted the PR!


Multiline headlines overwrite themselves with background color.

I use Literata font for headlines. When a headline is long and takes more than one line, the next line overwrites bottom of the previous one, damaging letters like [gjpqy]. Can be "fixed" by increasing line spacing (1.1 does the job), however I guess text rendering should only place foreground pixels.

Workaround slated for v1.8.1.


Feature Request: TypeSchema validation plugin

I'd be happy to contribute this plugin for what it's worth, I'm just looking to see if something like this would be desired to begin with.
TypeSchema is a universal TypeScript schema validation adapter library. Essentially the plugin could expose a single schema parameter that could take a zod schema (like the existing zod validation plugin), or something faster like valibot, ArkType, ajv, etc, or whatever else comes in the future.

That definitely sounds interesting! I've been wanting to add a more generic//library agnostic validation plugin.
I haven't had a chance to look into this deeply,.what is the overhead of this library? One of the things Pothos tries.to avoid is having additional dependencies, so I would want to make sure this doesn't have dependencies on all the libraries it supports

Both the @typeschema/main library and the @typeschema/core library (included by main) are pretty small.
@typeschema/main also defines optional peer dependencies on @typeschema/{arktype,class-validator,deepkit,effect,fastest-validator,function,io-ts,joi,json,ow,runtypes,superstruct,suretype,typebox,valibot,valita,vine,yup,zod}, and all of those seem pretty small as well.
I think this should be a fairly lightweight way to be able to get validation and type inference from any widely-used schema library.

The optional peer dependencies declarations can be seen here: https://github.com/decs/typeschema/blob/a5c728db9f4f1355a1df04d73091531862084a5e/packages/main/package.json#L128-L206


Focus issue after drag in chromium based browsers

Regression?
Yes
System Info and Version
 System/Version info
yprland, built from branch  at commit 9a09eac79b85c846e3a865a9078a3f8ff65a9259  (props: bump version to 0.42.0).
Date: Wed Aug 7 19:17:10 2024
Tag: v0.42.0, commits: 5069

flags: (if any)

System Information:
System name: Linux
Node name: vnva-zenbook
Release: 6.10.6-artix1-1
Version: #1 SMP PREEMPT_DYNAMIC Tue, 20 Aug 2024 02:43:37 +0000

GPU information:
04:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [1002:1638] (rev c5) (prog-if 00 [VGA controller])

os-release: NAME="Artix Linux"
PRETTY_NAME="Artix Linux"
ID=artix
BUILD_ID=rolling
ANSI_COLOR="0;36"
HOME_URL="https://www.artixlinux.org/"
DOCUMENTATION_URL="https://wiki.artixlinux.org/"
SUPPORT_URL="https://forum.artixlinux.org/"
BUG_REPORT_URL="https://bugs.artixlinux.org/"
PRIVACY_POLICY_URL="https://terms.artixlinux.org/docs/privacy-policy/"
LOGO=artixlinux-logo

plugins:

======Config-Start======

Config File: /home/vnva/.config/hypr/hyprland.conf: Read Succeeded
#monitor=eDP-1,preferred,0x0,1.5,bitdepth,8
#monitor=HDMI-A-1,preferred,-560x-1440,1,bitdepth,8
#monitor=HDMI-A-1,preferred,1920x300,1,bitdepth,8

source = ~/.config/hypr/monitors.conf

exec-once=dbus-update-activation-environment WAYLAND_DISPLAY XDG_CURRENT_DESKTOP
exec-once = ~/.dotfiles/bin/hyprland-fix-portals
exec-once = swww-daemon
exec-once = dinit
exec-once = /usr/bin/ags

#exec-once=[workspace 1 silent] telegram-desktop
#exec-once=[workspace 2 silent] google-chrome-beta
#exec-once=[workspace 3 silent] alacritty
exec-once=[workspace special:magic silent] alacritty

windowrulev2=noanim,title:(Media viewer)
windowrulev2=fullscreen,title:(Media viewer)
windowrulev2=float,class:(io.crow_translate.CrowTranslate)
windowrulev2=float,title:(Save File)

windowrulev2 = suppressevent maximize, class:.*
windowrulev2 = animation popin, class:wofi
#windowrulev2 = noanim, class:wofi
windowrulev2 = pin, class:wofi
windowrulev2 = float, title:(Picture in picture)
windowrulev2 = pin, title:(Picture in picture)
windowrulev2 = stayfocused, class:wofi

layerrule = noanim, status-bar
layerrule = animation slide top, ags-control-bar
layerrule = animation slide top, ags-app-launcher

# Set programs that you use
$terminal = alacritty
$fileManager = dolphin
$control-bar = ags --toggle-window ags-control-bar
$app-launcher = ags --toggle-window ags-app-launcher

# Some default env vars.
#env = XCURSOR_SIZE,24
env = HYPRCURSOR_THEME,rose-pine-hyprcursor
env = HYPRCURSOR_SIZE,24
env = QT_QPA_PLATFORMTHEME,qt5ct
env = QT_QPA_PLATFORM,wayland
env = GDK_BACKEND,wayland,x11

xwayland {
  force_zero_scaling = true
}

input {
    kb_layout = us,ru
    kb_options = grp:alt_shift_toggle
    kb_variant =
    kb_model =
    kb_rules =

    follow_mouse = 1

    touchpad {
        natural_scroll = false
    }

   sensitivity = 0 # -1.0 to 1.0, 0 means no modification.

   repeat_delay = 200
   repeat_rate = 50
}

general {
    gaps_in = 5
    gaps_out = 5
    border_size = 0
    layout = dwindle
    allow_tearing = false
}

decoration {
    rounding = 5
    blur {
        enabled = true
        size = 3
        passes = 1
    }

    drop_shadow = false
    shadow_range = 4
    shadow_render_power = 3
    col.shadow = rgba(1a1a1aee)
}

animations {
    enabled = true

    animation = border, 0
    animation = borderangle, 0

    animation = windows, 1, 2, default, slide
    animation = fade, 1, 2, default
    animation = workspaces, 1, 2, default
    animation = specialWorkspace, 1, 2, default, fade
}

dwindle {
    pseudotile = yes
    preserve_split = yes
    default_split_ratio = 1.05
    smart_split = true
}

gestures {
    workspace_swipe = on
}

misc {
    force_default_wallpaper = 0
    disable_hyprland_logo = true
}

device {
    name = epic-mouse-v1
    sensitivity = -0.5
}

$mainMod = SUPER

bind = $mainMod, Q, exec, $terminal
bind = $mainMod SHIFT, Q, exec, $control-bar
bind = $mainMod, C, killactive,
bind = $mainMod SHIFT, M, exit,
bind = $mainMod, E, exec, $fileManager
bind = $mainMod, V, togglefloating,
bind = $mainMod, R, exec, $app-launcher
bind = $mainMod, P, pseudo,
bind = $mainMod, J, togglesplit,
bind = $mainMod, F, fullscreen

bind = $mainMod, left, movefocus, l
bind = $mainMod, right, movefocus, r
bind = $mainMod, up, movefocus, u
bind = $mainMod, down, movefocus, d

bind = $mainMod, 1, workspace, 1
bind = $mainMod, 2, workspace, 2
bind = $mainMod, 3, workspace, 3
bind = $mainMod, 4, workspace, 4
bind = $mainMod, 5, workspace, 5
bind = $mainMod, 6, workspace, 6
bind = $mainMod, 7, workspace, 7
bind = $mainMod, 8, workspace, 8
bind = $mainMod, 9, workspace, 9
bind = $mainMod, 0, workspace, 10

bind = $mainMod ALT, 1, movecurrentworkspacetomonitor, 0
bind = $mainMod ALT, 2, movecurrentworkspacetomonitor, 1

bind = $mainMod SHIFT, 1, movetoworkspace, 1
bind = $mainMod SHIFT, 2, movetoworkspace, 2
bind = $mainMod SHIFT, 3, movetoworkspace, 3
bind = $mainMod SHIFT, 4, movetoworkspace, 4
bind = $mainMod SHIFT, 5, movetoworkspace, 5
bind = $mainMod SHIFT, 6, movetoworkspace, 6
bind = $mainMod SHIFT, 7, movetoworkspace, 7
bind = $mainMod SHIFT, 8, movetoworkspace, 8
bind = $mainMod SHIFT, 9, movetoworkspace, 9
bind = $mainMod SHIFT, 0, movetoworkspace, 10

bind = $mainMod, S, togglespecialworkspace, magic
bind = $mainMod SHIFT, S, movetoworkspace, special:magic

bind = $mainMod, mouse_down, workspace, -1
bind = $mainMod, mouse_up, workspace, +1
bind = $mainMod, code:59, workspace, -1
bind = $mainMod, code:60, workspace, +1

bindm = $mainMod, mouse:272, movewindow
bindm = $mainMod, mouse:273, resizewindow

# Print - capture region and copy
bind = , Print, exec, grim -g "$(slurp)" - | wl-copy
# Shift Print - capture region and edit
bind = SHIFT, Print, exec, grim -g "$(slurp)" - | swappy -f -
# Mod Print - capture current monitor and copy
bind = $mainMod, Print, exec, grim -o "$(hyprctl activeworkspace -j | jq -r '.monitor')" - | wl-copy
# Mod Shift Print - capture all monitors and copy
bind = $mainMod SHIFT, Print, exec, grim - | wl-copy

# Lockscreen
bind = $mainMod, L, exec, hyprlock

bind = ALT,F1,pass,^(com\.obsproject\.Studio)$

Config File: /home/vnva/.config/hypr/monitors.conf: Read Succeeded
# Generated by nwg-displays on 2024-08-18 at 16:31:36. Do not edit manually.

monitor=eDP-1,2880x1800@90.0,960x468,1.5
monitor=DP-1,3440x1440@99.98,2880x341,1.0

======Config-End========

Description
After selecting text and trying to transfer it (often I do this by accident), the focus breaks in chromium based browsers. Also reproduced when trying to drag an image
How to reproduce
Select the text and try dragging it
Crash reports, logs, images, videos
https://github.com/user-attachments/assets/cc99ae15-c3a7-4571-bc32-b316eaf179dc

Duplicate of https://github.com/hyprwm/Hyprland/issues/7496

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."


Latest release deployment is broken after OCP changes

I don't know for sure if @ctron 's recent configuration changes to our OCP cluster are the cause of the error, but the deploy job in the latest-release workflow hasn't succeeded ever since. It fails with the following error:
+ operator-sdk run bundle ghcr.io/trustification/trustify-operator-bundle:latest --namespace trustify-latest --timeout 15m
time="2024-10-17T10:31:35Z" level=info msg="Creating a File-Based Catalog of the bundle \"ghcr.io/trustification/trustify-operator-bundle:latest\""
time="2024-10-17T10:31:35Z" level=info msg="Generated a valid File-Based Catalog"
time="2024-10-17T10:31:39Z" level=info msg="Created registry pod: ghcr-io-trustification-trustify-operator-bundle-latest"
time="2024-10-17T10:31:39Z" level=info msg="Created CatalogSource: trustify-operator-catalog"
time="2024-10-17T10:31:39Z" level=info msg="OperatorGroup \"operator-sdk-og\" created"
time="2024-10-17T10:31:39Z" level=info msg="Created Subscription: trustify-operator-v1-0-0-snapshot-sub"
time="2024-10-17T10:46:27Z" level=fatal msg="Failed to run bundle: install plan is not available for the subscription trustify-operator-v1-0-0-snapshot-sub: Get \"[https://api.cluster.trustification.rocks:6443/apis/operators.coreos.com/v1alpha1/namespaces/trustify-latest/subscriptions/trustify-operator-v1-0-0-snapshot-sub\](https://api.cluster.trustification.rocks:6443/apis/operators.coreos.com/v1alpha1/namespaces/trustify-latest/subscriptions/trustify-operator-v1-0-0-snapshot-sub/)": context deadline exceeded\n"

I tried updating to the latest operator-sdk release, but it didn't help.
I'm hoping @carlosthe19916 might offer some guidance on how to diagnose the problem.

@jcrossley3 I'll investigate tomorrow. Thanks for sharing the log. I'll see what changed recently for it to fail now

The cluster was converted into a multi-arch cluster. I am not sure what that means internally. Some nodes are now arm64 nodes. There's some information about multi-arch clusters here: https://docs.openshift.com/container-platform/4.16/post_installation_configuration/configuring-multi-arch-compute-machines/multi-architecture-compute-managing.html
For trustification (v1) I had to amend the Helm charts in a way that they only deploy pods on amd64, as we don't build and publish multi-arch images for v1.

Is it easy enough to revert the multi-arch conversion? If the deploy job then works, at least we could confirm the correlation.

IIRC it was impossible.

Yea, not possible:

Migration from a multi-architecture payload to a single-architecture payload is not supported. Once a cluster has transitioned to using a multi-architecture payload, it can no longer accept a single-architecture update payload.

I'd love to know how you figured that out, but I'm afraid I may lack the expertise required to understand it.

I'd love to know how you figured that out, but I'm afraid I may lack the expertise required to understand it.

I think it was just being lucky. As soon as I started reading this issue today, @ctron already mentioned the "multi-arch" change in the OCP cluster (which to me would be almost impossible to track as I know almost nothing about that OCP instance).

I think you're being humble, but as they say in the casino, luck counts!


enhanceProvide a method to determine whether incremental updates of multiple tables are allowed

Currently, only range partitioning is supported, and it must be a dynamic partition or auto partition.
Think about the list partition carefully before making any decisions

run buildall

run buildall

run performance


Add a more complete example that demonstrates the use of cooldowns

Follow-up to #253.

Closing this because it does not belong here, and is now part of leafwing_abilities. @alice-i-cecile can you remove it from the 0.6 milestones? (I don't think it matters, because 0.6 has already been released but...just in order to keep things clean)


Support for multi-targeted libraries?

I thought this scenario was now supported, but I may have misread. I have a .NET Standard class library in VS2017 targeting netstandard1.4 and net462. When I install GitVersioning, I do not get a project.json file (have to add it manually), and when I build I get errors:
1>obj\Debug\net462\Foo.AssemblyInfo.cs(17,12,17,58): error CS0579: Duplicate 'System.Reflection.AssemblyFileVersionAttribute' attribute
1>obj\Debug\net462\Foo.AssemblyInfo.cs(18,12,18,67): error CS0579: Duplicate 'System.Reflection.AssemblyInformationalVersionAttribute' attribute
1>obj\Debug\net462\Foo.AssemblyInfo.cs(21,12,21,54): error CS0579: Duplicate 'System.Reflection.AssemblyVersionAttribute' attribute

Am I doing something wrong, or is this not supported yet?

Yes, it's supported.
You should delete your project.json file. (new) VS2017 projects don't use it. Instead, when you install a package it adds a PackageReference item to your project file.
Your compile errors are due to https://github.com/dotnet/sdk/issues/1142. You can workaround it by deleting that temporary file manually. A "Rebuild" might do it.

Sorry, I meant that I don't get a version.json file -- I know that project.json shouldn't be there.
And yes, Rebuild does clear things up.

In the new project type, installing packages never runs the package's install.ps1 script. So you have to create the version.json file yourself.

I hardly hit this any more. I think they fixed it.


Enhancementfix unclear exception msg when tag.location invaild.

Proposed changes
Issue Number: close #xxx
Problem summary
CREATE TABLE test (
id BIGINT COMMENT '',
) ENGINE = OLAP
DUPLICATE KEY(dmp_share_cd_time_idatat)
COMMENT 'OLAP'
DISTRIBUTED BY HASH(dmp_share_cd_time_idatat) BUCKETS AUTO
PROPERTIES (
"replication_allocation" = "tag.location: 1",
"in_memory" = "false",
"storage_format" = "V2",
"compression" = "ZSTD",
"estimate_partition_size" = "115G",
"disable_auto_compaction" = "false"
);
exception msg: String index out of range: -1 is weird, now it will be 'Invalid replication allocation location tag property: tag: location: 1'
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[x] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

please fix this on master too


Scrape post comments without being logged in?

Until about a month ago, I could pull comments from public profile posts without being logged in, but now I immediately receive a 429 error. (I've tested this is a controlled setting with a residential IP address, no other calls to Instagram from the same IP, using a rate controller, etc.) I can, however, pull dozens of images without any issue, which leads me to believe that it's not actually rate-limit related, but that Instagram has blocked all comment-level data to non-logged in users.
In addition, I have no problem pulling comments when I'm logged in.
This used to work, but now returns 429:
instaloader --comments -- -CViXWNxpzF4
This works:
instaloader --comments --login XXXXXXXXXXX -- -CViXWNxpzF4
Has anyone observed similar behavior? Am I correct in understanding that Instagram has blocked comment-level data for non-logged-in users?
Any input is appreciated, thank you!

Yeah, I believe for Instagram scraping comments is quite a sensitive thing.

I have an alternate tool that works:
PS C:\> instagram -i CViXWNxpzF4
{Display_URL:https://scontent-hou1-1.cdninstagram.com/v/t51.2885-15/e35/s1080x1080/248826697_118016843992855_6873736538889054481_n.jpg?_nc_ht=scontent-hou1-1.cdninstagram.com&_nc_cat=1&_nc_ohc=oqUcXjDc_WsAX9YNVRx&edm=AABBvjUBAAAA&ccb=7-4&oh=b8d3a6aa625aba8e163ebad3ce78c216&oe=619F702B&_nc_sid=83d603&ig_cache_key=MjY5MzgxODIwODgxMDkwNTk3Ng%3D%3D.2-ccb7-4
Edge_Media_Preview_Like:{Count:4413397}
Edge_Media_To_Parent_Comment:{Edges:[{Node:{Text:Killer}} {Node:{Text:😍}}
{Node:{Text:😍}} {Node:{Text:😍}} {Node:{Text:Show off}} {Node:{Text:QUIT
SHOWING OFF WHEN THERES ALOT OF KIDS DYING FOR FOOD!!!}} {Node:{Text:😂}}
{Node:{Text:❤}} {Node:{Text:😂}} {Node:{Text:sart}} {Node:{Text:❤}}
{Node:{Text:See Dr ty Hi u}} {Node:{Text:❤}} {Node:{Text:See Dr ty Hi u}}
{Node:{Text:Hyd}} {Node:{Text:What up}} {Node:{Text:😍}} {Node:{Text:First}}
{Node:{Text:O 🔥🔥🔥}} {Node:{Text:Pathetic}} {Node:{Text:Lblblb}}
{Node:{Text:I want 1 heel from there}} {Node:{Text:�😍😍}}}]}
Edge_Sidecar_To_Children:<nil> Video_URL:}


an incomplete/unnecessary sentence in "IS as a Key Manager" section

Description:
The highlighted section in the below screen is not complete or unnecessary as consider the whole part of description on WSO2AM_DB

This was fixed in the following pages as follows:
This DB stores the identity data and API-related data and it includes OAuth tokens and keys. When serving key-validation requests, the Key Manager accesses the WSO2AM_DB, validates whether there are subscriptions made by the particular key.
[1] https://docs.wso2.com/display/AM210/Configuring+WSO2+Identity+Server+as+a+Key+Manager
[2] https://docs.wso2.com/display/AM2xx/Configuring+WSO2+Identity+Server+as+a+Key+Manager
[3] https://docs.wso2.com/display/AM220/Configuring+WSO2+Identity+Server+as+a+Key+Manager


Doesn't work with tmux 1.9

Hi!
I'm using Debian Jessie and Tmux 1.9 and after commit 8bc5ff3247e0816313e0e65112562f44b2ec6472 plugin stops to work. I'm running the same config with Arch Linux and Tmux 2.2 and plugin works fine.
What can I do to debug and get this plugin working on Tmux 1.9?

Hi @fbertux
Thanks for reporting it.
You can try to execute the plugin manually, inside a tmux session:

Open tmux
Go to your plugins folder, usually at ~/.tmux/plugins
Run ./tmux-prefix-highlight/prefix_highlight.tmux

That should output an error, if any.

Hi @erickpintor
Thanks for answer.
No errors printed.
If I run set -x prefix_highlight.tmux I get this output , I don't know if helps.

Yes, that does help.
There seems to be an issue with the interpolation of the new "Copy" highlight:
+ tmux set-option -gq status-right '#[fg=colour234,bg=colour234,nobold,nounderscore,noitalics]\
#[fg=colour85,bg=colour234] #{?client_prefix,#{@_prefix_highlight_attr_prefix} ^A ,\
#{?pane_in_mode,#{@_prefix_highlight_attr_copy}Copy,}}#[default] \
#[fg=colour238,bg=colour234,nobold,nounderscore,noitalics]⮂#[fg=colour255,bg=colour238]\
 %b %d %R #[fg=colour190,bg=colour238,nobold,nounderscore,noitalics]\
#[fg=colour17,bg=colour190] #H '

Specifically here: #{@_prefix_highlight_attr_copy}Copy,}}. Seems like the placeholder was not replaced properly.
Unfortunately, it does not happen in my Mac with Tmux 2.1. I'll have to setup a VM.
Meanwhile, feel free to revert the latest commit from your local. That should fix the problem for now.

Hi @fbertux
Would you mind testing again?
After https://github.com/tmux-plugins/tmux-prefix-highlight/commit/b64828f8585c4189a26dbf87d2e9ec1362251e0e, I believe the issue is fixed.
At least, it didn't happened when I tested on a docker image.

Hi @erickpintor
It's working now.
Thanks!

Cool! I'm closing this issue then.
Até mais.


Fix match by custom attributes

Changes

add method to correctly format the predicate for custom attributes
adapt tests accordingly

cc/ @hajoeichler @emmenko

:+1:

Coverage increased (+0.05%) to 17.651% when pulling 88bd787d98e2d83090c14e821bd6c56059936ef7 on bugfix/match-by-custom-attributes into e987504b91cbff8bf09a53cc6c4c27babd7542c6 on master.


about covalent docking

is it possible to perform covalent docking with vina 1.2.3 and covalent docking based virtual screening (batch file mode)?
can I install this tool (vina 1.2.3) in windows  ?

Unfortunately no, because the batch mode works only for the ligands, and covalent docking passes the ligand as a flexible sidechain.
Soon, it will be possible to do covalent docking in AutoDock-GPU, in batch mode, after this pull request is completed: https://github.com/ccsb-scripps/AutoDock-GPU/pull/171/

Thanks for the information.
The covalent docking with autodock 4.2 contain some scripts written in python 2. Recent linux OS possess p[ython 3. Therefore these scripts depicts issue. I changed the print statement syntex as per python 3 (only add () and use import pybel as ob ) and found most of the scripts started working.  But unable to solve one issue associated with class OBMolCopy(ob.OBMol).
the actual error is
"lass OBMolCopy(ob.OBMol):
AttributeError: module 'pybel' has no attribute 'OBMol"
Autodock 4.2 is one of the most reliable open source docking tool. There for in my covalent docking project I want to use it. But encountered by above issue. Can you assist me to resolve it. I am attaching the changed scripts as .txt documents. Thanks Sir
CopyMol.txt
py-3-prepareCovalent.txt
ResidueProfiler.txt


Incorrect URL in documentation

I hope this is the right place to report this. There's a small misprint under the "Choose a SDK" section in the interactive reference
The Github link goes to "https://github.com/mixer/interactive-sdk-cpp"
when it should go to "https://github.com/mixer/interactive-cpp/"

Thank you for reporting the issue! I checked and it looks like one of our engineers has fixed the link. Thank you again for reporting it!


minor improvements/bugfixes

improved Makefile
included header ctype.h for isprint()
added comments
removed unneccesary redirection of stdout/stderr
renamed variabled mp to mountingpoint
moved creation and assignment out of if statement
customized assassination of mountingpoint
added rmdir call for mounting directory after unmounting a device

thanks for your interest!