feat(create-prs-to-update-vcs-repositories): add a workflow

Description
This PR adds a new feature as follows:

Check the version of all repositories in the autoware.repos
Check if the version of the repository is the latest
If the version is not the latest, create a PR to update the repository to the latest version

This PR will be created for each repository that is not the latest version

Related links
Semantic Versioning Discussion
Tests performed (Referenced from the URL in "Related links")
Premise

Target repositories must have tags matching the pattern: semantic_version_pattern = r'\b(v?\d+\.\d+(?:\.\d+)?(?:-\w+)?(?:\+\w+(\.\d+)?)?)\b'

This pattern can handle following example tags

    "0.0.1",
    "v0.0.1",
    "ros2-v0.0.4",
    "xxx-1.0.0-yyy",
    "2.3.4",
    "v1.2.3-beta",
    "v1.0",
    "v2",
    "1.0.0-alpha+001",
    "v1.0.0-rc1+build.1",
    "2.0.0+build.1848",
    "2.0.1-alpha.1227",
    "1.0.0-alpha.beta",
    "ros_humble-v0.10.2"

If updates occur in multiple repositories, create a separate PR for each repository

Test Cases
The following tests passed:

Duplicate PR Prevention

Executing the same Github Action multiple times should not create duplicate PRs with identical content

Multiple Repository Updates

When updates occur simultaneously in two or more repositories, PRs should be created for each affected repository

Idempotent Behavior

The operation should behave as expected and be idempotent, even if the target branch already exists locally or remotely

Examples:

a. No branches or PRs should be created for anything other than version updates of sub-repositories where tag updates have occurred
b. The Github Action should not produce errors like "branch already exists"
c. Github Action log output should remain consistent across runs, differing only in timestamps (excluding the initial PR creation)

Post-Merge Behavior

After a PR is merged, no unexpected behavior should occur

Examples:

a. PRs unrelated to the update should not be created
b. If a branch is deleted after the merge process, the deleted branch should not be pushed again

Notes for reviewers
Currently I'm thinking to trigger this workflow per day. Any proposal and comments are welcome.
Also, if you find the missing tests, please let me know. I'm happy to perform the tests.
Interface changes
No interface changes.
ROS Topic Changes
No ROS topic changes.
ROS Parameter Changes
No ROS parameter changes.
Effects on system behavior
A new PR will be created as the vcs repository has update with semantic versioning.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[x] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

(The reason of the force push is, the --signoff was not applied for the fixes by proposal)

@youtalk Thank you very much for your insightful review! Now all the checks have passed. Let me merge this branch :+1:

I've merge it! Let's move on!


error: pathspec '62ecb60' did not match any file(s) known to git.

when i run:
git clone --recursive https://github.com/dmlc/mxnet.git
git checkout 62ecb60
there is a error:
error: pathspec '62ecb60' did not match any file(s) known to git.

Just tried. I cannot reproduce this error.

It works for me, just checked.

move into the mxnet directory
git clone --recursive https://github.com/dmlc/mxnet.git
cd mxnet
git checkout 62ecb60

@gregchu  thanks a lot, with your suggestion , i can solve it


Fix migration from blocklayered

Questions
Answers

Description?
Because of wrong SQL queries, installing this module over the old blocklayered one in the BO fails. Also, when deleting it, the table ps_layered_friendly_url is still in the DB.

Type?
bug fix

BC breaks?
no

Deprecations?
no

Fixed ticket?
Partially PrestaShop/Prestashop#22668

How to test?
1. On PS 1.7.x.x, uninstall any existing ps_facetedsearch or blocklayered module.2. Check that your DB doesn't have any table starting with ps_layered_*.3. Install this modified version of blocklayered (only the compatibility range has been changed so we can install it manually on a 1.7.x.x shop).4. Install ps_facetedsearch with this PR, the install should not cause any problem.5. Check that blocklayered is uninstalled and that the table ps_layered_friendly_url is not present in the DB.

This change is

Hi @atomiix,
It is ok :heavy_check_mark:
https://drive.google.com/file/d/1huot96pFKhSXizbPrAP4Ut9WkVqUDlgS/view?usp=sharing
I checked with:

PS1769
PS1771
Develop branch

Thank you!


v2.0.9753

Problem

Description of why you made this PR

Solution

And how do you fix that problem

PR Status

[ ] Code finished and ready to be reviewed/tested
[ ] The fix/enhancement were manually tested (if applicable)

Automatic tests
Automatic tests can be triggered on https://ci-apps-dev.yunohost.org/ after creating the PR, by commenting "!testme", "!gogogadgetoci" or "By the power of systemd, I invoke The Great App CI to test this Pull Request!". (N.B. : for this to work you need to be a member of the Yunohost-Apps organization)

!testme

Tested on my live install https://call.trom.tf/ - everything works well. Log here - https://paste.trom.tf/koveveceha.sql - you can merge into master please.


Rarefaction as optional strategy for alpha diversity

Ref: Pat Schloss' recent analyses on rarefaction in alpha & beta diversity. This addressess well some of the long debates and controversies surrounding rarefaction in microbial ecology.
Based on this I tend to think that rarefaction should be provided as an option for alpha diversity calculations.
Here rarefaction refers to averaging alpha diversity estimates across many random rarifications (100x and 1000x are used in the preprint). This makes most difference in less diverse and low abundance environments but may influence also more rich ecosystems (see the preprint).
Options:

write an apply/do loop around estimateDiversity and just provide that as an example in mia vignette / OMA
provide rarefaction as an option in estimateDiversity directly (including user defined arguments for the number of rarification rounds, and for the read count threshold with some automated default such as the smallest read count among samples)

I am in favour of the second option.
Note:

we have estimateDiversity, estimateRichness, estimateDominance etc.; these all should be updated
or we can consider combining them into a single estimateAlpha function to simplify procedures and maintenance (perhaps a separate issue to deal with first to minimze extra work)

I agree with the second option and then still show an example at vignette and/or OMA for example.
Would for instance estimateAlphaWithRarefaction be a better naming? upon which the function would take as argument the functions:  estimateDiversity, estimateRichness, estimateDominance?

Lets do: "estimateAlpha" at least for now


[Feature Request] Enhance class inheritance

Issue type

[ ] bug report
[x] feature request

Issue description
While attempting to augment functionality, or modify some components' behavior, one is unable to simply extend core Component classes because, most of the time, properties and methods are private. This reduces the ability to add new functionality or tweaks on a "per project" basis.
It'd be nice to be able to add new methods or alter existing methods for custom functionality. It should be as simple as replacing private with the protected modifier.

What do you need to extend?
I don’t want to do this because:

Extending class components is not a good practice in React, it’s always better to achieve this result result with props
Sometime we will rewrite it with functional components 🤞

Thanks for your reply!
Specifically, I was trying to make a TopNavigation component render any ReactElement in the title prop, and not just strings. The edit to the code to achieve this was quite simple, really... but it would be cool to be able to update ui-kitten and have this derived component get most of the new functionality or bug fixes with minimal code.
I read in another issue (that I couldn’t find again) that such is a little against the philosophy of the framework, so I just decided to hack it for my needs. Current composition API doesn’t allow for this particular case.
Currently I just copied the code to a new file in my project as a new component.

@lesmo please open a new issue with a detailed description of the feature you need so we have a complete picture of how it could be resolved. Extending class components is not a good solution for this


chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
0bb608c -> 983b59d

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
minor
v1.27.2 -> v1.29.0

terraform-ibm-modules/common-pipeline-assets
action
minor
v1.20.0 -> v1.21.6

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.29.0
Compare Source
Features

Add function to get stable icd versions (#762) (738756f)

v1.28.5
Compare Source
Bug Fixes

deps: update gomod (#761) (e57b7c5)

v1.28.4
Compare Source
Bug Fixes

deps: update module golang.org/x/crypto to v0.19.0 (#757) (72d3f03)

v1.28.3
Compare Source
Bug Fixes

update to not hard fail on destroy (9c6e21c)

v1.28.2
Compare Source
Bug Fixes

deps: update gomod (#754) (2872471)

v1.28.1
Compare Source
Bug Fixes

Add Helper function and refactor tests (#752) (c3e0c1c)

v1.28.0
Compare Source
Features

add resource group print on failure (#746) (17daf42)

terraform-ibm-modules/common-pipeline-assets (terraform-ibm-modules/common-pipeline-assets)
v1.21.6
Compare Source
Bug Fixes

Updates release workflow to run outside CI container to address hanging bug (#659) (ddc3bb7)

v1.21.5
Compare Source
Bug Fixes

disable tag sign (#658) (6027821)

v1.21.4
Compare Source
Bug Fixes

disable commit signing (#657) (14ad6c9)

v1.21.3
Compare Source
Bug Fixes

update command (#656) (8281f64)

v1.21.2
Compare Source
Bug Fixes

add debug logging (#654) (7ea2e73)

v1.21.1
Compare Source
Bug Fixes

format readme (#653) (c44c48a)

v1.21.0
Compare Source
Features

Release pipeline now creates GIT issue and slack alert on failure (#636) (3a51e77)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline


feat(volumes): Show Volume Created column

Show Volume Created date column in Volume list
Show Volume Created date field in Volume details

Thanks @linquize :+1:


'.' is no longer in @INC

#3

Codecov Report

Merging #4 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master     #4   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines          12     12
  Branches        1      1
=====================================
  Hits           12     12

Continue to review full report at Codecov.

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


Refactoring setStreamType method

https://github.com/hayanmind/react-native-sound/commit/a28156923c966449e6cd88ecee85a9023a4e577c#r27780259

I might assign myself when I'll take care of it. In the meantime, if anyone wants to take it, feel free to do it :)


Reserve region-shaped allocations

This PR extends and changes with_capacity and reserve behavior:

Names are cleaned up to be: reserve extends an existing &mut Self and with_capacity creates a new instance.
Variants have been added that take Iterator<Item = &Self> arguments, to pre-size a region from existing regions.

Thanks!


Empty spritemap file

After updating to v3.0.0, my spritemap file only contains an empty svg tag.
<svg xmlns="http://www.w3.org/2000/svg"/>
I assume this is somehow related to the svgo changes.

Weird because I didn't have any issue with my test demo folder. Even by fetching the package from npm. Can you provide a reproduction ?

@haleyngonadi Can you share a reproduction ? Or any clue (type of project...) to help me to reproduce the issue ?

Had the same/similar issue.
Resolved it by using path.resolve
import path from "path";
VitePluginSvgSpritemap(path.resolve(__dirname, "./public/assets/*.svg"), {...}

Project is an almost clean install of react 19.0.0 using typescript.
Adding package.json, tsconfig and package.json for reference
tsconfig.json
package.json
vite.config.json - renamed to json, because github was unhappy with .ts :)

I tried with a vanilla react template from ViteJS, no problem for me.
@nakashu What is your OS? Windows, MacOS or Linux ?

@Applelo
Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 24.04.1 LTS
Release:        24.04
Codename:       noble

node - v22.12.0
pnpm - 9.6.0
For me it's not really a problem. I tried the path solution it worked and I moved on.
I just seen the issue and tough,  maybe it will help, to pinpoint the problem if it is real in react or something.
Will be working with it next days, so will try with different 'paths/. ./ /` ... etc etc.

I tried with path.resolve on windows but I am still having the issue.

I figured this out. For me, I had to pass the glob as an array; so
VitePluginSvgSpritemap(['resources/icons/*.svg']) instead of VitePluginSvgSpritemap('resources/icons/*.svg')

I tried this and it did work, wrapping the path string around an array fixed the issue.

@Santana1053
If you are not using WSL (you definitely should), try changing the forward slashes / to backwards \ ones
Colleague of mine had problem with paths like this before he switched to WSL.
Windows does it differently  :D


Add Composition to Portuguese(Brazil)

Related to #89

@pragmaticivan you are a machine!  Thank you so much for your contributions.
I'm going to give @tiagobarreto an opportunity to look at these before I merge.

Thanks :D :+1:

@tiagoamaro comment in the PR instead of my branch.

@pragmaticivan sorry! :+1:


Performance: unnecessary TYPE commands when downloading multiple files

FTP OS: Other
FTP Server: Other
Computer OS: Windows 10
I found it strange that the time it took my application to download a list of files more than doubled when switching from the standard FtpWebRequest classes/methods to using FluentFTP, so I went to the logs to investigate.
It turns out that each call to DownloadFile() ends up issuing a TYPE I command, even if the transfer type is already binary.
My workaround was to change the SetDataType() method in FtpClient_LowLevel.cs to only call SetDataTypeInternal if the CurrentDataType is not equal to the requsted type.
protected void SetDataType(FtpDataType type) {
#if !CORE14
			lock (m_lock) {
#endif
				if (CurrentDataType != type)
					this.SetDataTypeInternal(type);
#if !CORE14
			}
#endif

			CurrentDataType = type;

		}

I'm not sure if this is acceptable in every case, but it seems to improve performance by ~27% in my application.
It may be worth mentioning that I also commented out the section that calls GetFileSize() in DownloadFileInternal() despite having a binary transfer. That's why you don't see the SIZE commands in the logs below. This improved performance by about 21% for me. Perhaps this is better discussed in another issue, but I am curious as to why binary transfers should get the file size before transfer at all. With a download set of mostly small files, the SIZE command itself ends up being a significant portion of the total download time.
Logs :
# DownloadFile("C:\tmp\file.txt", "/file.txt", True, None)

# OpenRead("/file.txt", Binary, 0)
Command:  TYPE I
Response: 200 Type set to  I

# OpenPassiveDataStream(PASV, "RETR file.txt", 0)
Command:  PASV
Response: 227 Entering Passive Mode (127,0,0,101,210,225)
Status:   Connecting to <IP_ADDRESS>:53985
Command:  RETR /file.txt
Response: 150 Binary data connection.
Status:   Disposing FtpSocketStream...
Response: 226 Binary Transfer complete.

# DownloadFile("C:\tmp\file2.txt", "/file2.txt", True, None)

# OpenRead("/file2.txt", Binary, 0)
Command:  TYPE I
Response: 200 Type set to  I

# OpenPassiveDataStream(PASV, "RETR /file2.txt", 0)
Command:  PASV
Response: 227 Entering Passive Mode (127,0,0,101,210,227)
Status:   Connecting to <IP_ADDRESS>:53987
Command:  RETR /file2.txt
Response: 150 Binary data connection.
Status:   Disposing FtpSocketStream...
Response: 226 Binary Transfer complete.

Despite the performance improvements, there are various reasons we do what we do:

The call to GetFileSize is the fastest way to check if a file exists, and if it does, we then behave according to the FtpExists setting chosen.
If you wish to skip the check you may pass FtpExists.None to improve performance. Please see if that has identical behavior to your changes, if not, we will investigate further.
I don't exactly understand why TYPE I is being changed for no reason. This is a good improvement imo.

I have implemented point 3 in https://www.nuget.org/packages/FluentFTP/19.2.0.

Thanks for the reply. RE: item 2, isn't the FtpExists option only for Upload* method? For downloading, it appears that the SIZE command is always issued if in binary transfer mode: https://github.com/robinrodricks/FluentFTP/blob/ac6ef5c5dc4a4de81910f686056af5e1337ba97c/FluentFTP/Client/FtpClient_HighLevel.cs#L1776
Downloading to EOF while in binary transfer mode works just fine for me. Is there a reason why the size is typically needed beforehand?
Thank you for implementing point 3. I created a pull request to add fix to the Async method as well.

Oh I see, my bad about FtpExists. And regarding the SIZE command sorry to say I don't really understand fully if its needed or not as I'm not the original developer of the lib. However, there have been many fixes and performance improvements so I have developed the opinion that the lib was not highly efficient to begin with. If it appears that something is not needed, it probably is not needed. Perhaps his biggest mistake was total lack of comments in the source code, making it very hard to understand WHY something is done instead of just WHAT is going on.

Oh and about the size command being needed beforehand, I added that. Its basically so that we know how many bytes the file is and we stop reading when those many bytes have passed. If you're suggesting EOF I think there were problems with that in binary mode (not sure) so I chose the file size method since I thought it would be more reliable. Is it unusual for an FTP Client to download in this way?

In my limited experience, I think it is typical to download to EOF.
e.g. in this Golang FTP library[1], we use ioutil.ReadAll which reads to EOF[2].
Also if you use the built-in Windows ftp client in verbose mode, you won't see any SIZE commands issued when downloading, so I would guess it reads to EOF as well.
1: https://github.com/jum/tinyftp/blob/master/tinyftp.go#L244
2: https://golang.org/pkg/io/ioutil/#ReadAll

I think at this point the only advantage is having progress reports. Maybe we can only check SIZE if the progress reports are enabled and omit the check otherwise? Seems like a good idea to me...

Makes sense to me!

I like this discussion so far. Not had an interested contributor in a long time. Most people only come to bemoan their problems without offering any solutions. Thanks!

Combined changes into this finally https://www.nuget.org/packages/FluentFTP/19.2.2

Maybe you can try it and see if all looks good on your end?

Great, thanks. I'll give it a shot later today and let you know.

19.2.2 performance seems to be on par with my local hacked version 👍

Good to know! Thanks again for the well documented fixes and research!

Your welcome.


Remove old IE event listeners in domReady

https://github.com/cujojs/curl/blob/master/src/curl/domReady.js#L104-L105
The first parameter to both attachEvent and detachEvent should match.  Currently, the attached listeners are not being detached for old IEs.
Also, perhaps attachEvent should be inspected before assuming it can be used in that "else" block.
Possible fix:
else if ('attachEvent' in global) {
	addEvent = function (node, event) {
		event = 'on' + event;
		node.attachEvent(event, checkDOMReady);
		return function () { node.detachEvent(event, checkDOMReady); };
	};
}

But then should there be a final "else", or should addEvent be defined as a no-op by default?

Thanks @ravager!  Silly DOM events are so silent.

else if ('attachEvent' in global)

Yah, this is a probably a good idea.  However, early on, we decided to use the assume-MS-if-not-W3C pattern, instead.  I just fixed the event name (similar to what you proposed) so it is consistent the the rest of the code.


Allow this as return type from static methods

TypeScript allows to return this from instance methods, which is to say the least, is great. It would be even better if it allowed doing the same with static methods. The rationale is consistency and feature.
Line public static construct():this below will report error TS2526: A 'this' type is available only in a non-static member of a class or interface., the line below uses this inside static method to create a new instance of the class, the line below that also uses this to return static property. The error message is misleading, this can be and should be used inside static methods whenever appropriate.
class Foo {
    public static x:any;
	protected y:any;
    public static construct():this {
        return new this();
    }
    public static getX():any {
        return this.x;
    }
	public getY():any{
		return this.y;
	}
	public setY(value:any):this{
		this.y = value;
		return this;
	}
}

I'd like to inherit Foo and use construct on child classes, the only way I can do this by specifying Foo as return type, however, this will require to cast the result to Bar and Baz whenever called from those classes – inconvenient and inconsistent with instance method behaviour.
This seems to be common sense, since this already done for instance methods, shouldn't be much pain doing this for static methods either? What are your thoughts?

Duplicate of https://github.com/Microsoft/TypeScript/issues/5863


View object

PR for view object. ( talked about at #4979 )
Creating a view
CREATE VIEW <view-name> AS <query>

Dropping a view
DROP VIEW <view-name>

Alter a view
ALTER VIEW <view-name> [NAME <new-name>] [QUERY <new-query>]

Listing all views (console command)
list views

Example result:
VIEWS
-----------------+----------------------------------------------------------------------------------+
 NAME            | QUERY
-----------------+----------------------------------------------------------------------------------+
 userDisplay     | SELECT name, color.append(" ").append(name) as display_name FROM User            |
-----------------+----------------------------------------------------------------------------------+
 TOTAL = 1                                                                                |
-----------------+----------------------------------------------------------------------------------+

Example usage:
CREATE CLASS User
INSERT INTO User SET name="Mat", color="Blue"
INSERT INTO User SET name="Jason", color="Green"
INSERT INTO User SET name="Samantha", color="Red"

CREATE VIEW userDisplay AS SELECT name, color.append(" ").append(name) as display_name FROM User

SELECT FROM userDisplay WHERE name in ["Mat", "Samantha"]

result:
----+------+--------+------------
#   |@CLASS|name    |display_name
----+------+--------+------------
0   |null  |Mat     |Blue Mat
1   |null  |Samantha|Red Samantha
----+------+--------+------------

What's left

Some tests for the view; Would be nice if someone else can implement them!
Currently there is no check for the query value. That is, you can enter any value you would like in the query, and it will be saved. The error will only show up when actually querying the view. To be honest though I didn't really look at it, due to some time constraints. I'll try to look at it in the next few days.

Cool:)

But is it persistent view or dynamic?
Is there support for views usage in queries?

If answers are 1) not persistent and 2) no : it looks like just registry for queries, but not true views.

I'm not entirely sure what are you referring to; What is persistent/dynamic view? what is your definition for complex query?
Anyway, I think what you're asking if this is a view or a materialized view; If so, this is a simple view, not even insert-able.
"My" definition for view/materialized view, just to be clear:
https://en.wikipedia.org/wiki/View_(SQL)
https://en.wikipedia.org/wiki/Materialized_view


alpha_dash validation rule does not allow underscores

The documentation here clearly states that the alpha_dash validation rule should allow underscores, but in practice validation fails if an underscore is present in the value.
Couldn't find an existing issue, so I'm happy to submit a pull request if this issue hasn't already been discovered/fixed.

Ignore me, there is no bug.


Cannot get the Square crank to work right away.

Version
3.1.3 (cbe02d7)
Seed
R730-PKJ0-XXNE57KZ9PN10QQR9W4TWZ1ZZZZZZZZZZZZZZZZZZZZZ
Scenario
RE 3 (Jill)
Player Character
Wesker CV (I dont think it matters)
What happened?
Unless I pass a certain "stage", I cant use the 'square crank' on the metal gate to get items.

This is unfortunately a limitation of the game. No logic exists for the crank on the daytime version of that room.


Literal props that will be lookup props

UW RDA profile currently has PTs with type literal that will change to type lookup pending future QA work.
These PTs include values for useValuesFrom and defaultURI etc. that will be needed for future lookups but will cause errors if output for literal-type PTs now.

dvdVideo transform does not include these changes. Do they need to be added?

Hmm, looks like it but I'm not 100% sure. Talk about it Wednesday?

Most recent mono transform 7d2a4cd3fe709a1654f9bfbcadef5410631b90d9 eliminates errors for unacceptable props in PTs with type literal.


serverUrl, full url support with path

Is it possible to enable full URL support with a complete path for the serverUrl configuration variable, similar to how it is implemented in the APM (Application Performance Monitoring) JavaScript RUM (Real User Monitoring) agent?
And also config for java.io.IOException Cleartext HTTP traffic.

Offen is backend functionality (in this case apm/open telemetry endpoints) exposed outside over some proxy.
In my opinion this is an issue!

Hi @gjelenc - You should be able to set a full url with a path with no issues both in the gradle script as well as using the agent's runtime apis as there are no validations in place that prevent doing so. Please let us know if you find any issues!

And also config for java.io.IOException Cleartext HTTP traffic.

I'm not sure I'm following up regarding this part, however, I do know that Android's latest apis disable cleartext traffic by default, so in case your endpoint needs cleartext traffic to work (for debugging purposes) you could enable it in your app's AndroindManifest.xml file. There are a couple of ways this could be done that are explained in here.

Ok my gradle config is:
elasticApm {
    serverUrl = "https://api.example.si/es/some_path/"
    apiKey = "****"
}

And here are log from logcat:
2023-09-19 14:19:20.989 17360-17360 InputMethodManager      si.example.myapmapp             I  startInputInner - mService.startInputOrWindowGainedFocus
2023-09-19 14:19:21.498 17360-17583 ELASTIC_AGENT           si.example.myapmapp             D  Creating OkHttp event listener
2023-09-19 14:19:21.499 17360-17583 ELASTIC_AGENT           si.example.myapmapp             I  Intercepting OkHttp request
2023-09-19 14:19:21.499 17360-17583 ELASTIC_AGENT           si.example.myapmapp             D  Intercepting OkHttp request: https://api.example.si/opentelemetry.proto.collector.logs.v1.LogsService/Export
2023-09-19 14:19:21.499 17360-17583 ELASTIC_AGENT           si.example.myapmapp             I  Ignoring OTel exporting related http request
2023-09-19 14:19:21.836 17360-17654 OkHttpGrpcExporter      si.example.myapmapp             W  Failed to export logs. Server responded with HTTP status code 404. Error message: Not Found
2023-09-19 14:19:26.914 17360-17582 ELASTIC_AGENT           si.example.myapmapp             D  Returning true time
2023-09-19 14:19:26.929 17360-17582 ELASTIC_AGENT           si.example.myapmapp             D  Creating OkHttp event listener
2023-09-19 14:19:26.930 17360-17582 ELASTIC_AGENT           si.example.myapmapp             I  Intercepting OkHttp request
2023-09-19 14:19:26.931 17360-17582 ELASTIC_AGENT           si.example.myapmapp             D  Intercepting OkHttp request: https://api.example.si/opentelemetry.proto.collector.metrics.v1.MetricsService/Export
2023-09-19 14:19:26.931 17360-17582 ELASTIC_AGENT           si.example.myapmapp             I  Ignoring OTel exporting related http request
2023-09-19 14:19:27.021 17360-17650 OkHttpGrpcExporter      si.example.myapmapp             W  Failed to export metrics. Server responded with HTTP status code 404. Error message: Not Found
2023-09-19 14:19:32.553 17360-17591 ELASTIC_AGENT           si.example.myapmapp             D  Central config url: https://api.example.si/config/v1/agents?service.name=MyAPMApp&service.environment=android-dev
2023-09-19 14:19:32.554 17360-17591 ELASTIC_AGENT           si.example.myapmapp             D  Retrieving central config ETag null
2023-09-19 14:19:32.573 17360-17591 TrafficStats            si.example.myapmapp             D  tagSocket(116) with statsTag=0xffffffff, statsUid=-1
2023-09-19 14:19:32.953 17360-17591 ELASTIC_AGENT           si.example.myapmapp             D  Storing central config ETag null
2023-09-19 14:19:32.954 17360-17591 ELASTIC_AGENT           si.example.myapmapp             D  Central config cache control header not found
2023-09-19 14:19:32.954 17360-17591 ELASTIC_AGENT           si.example.myapmapp             D  This APM Server does not support central configuration. Update to APM Server 7.3+
2023-09-19 14:19:32.955 17360-17591 ELASTIC_AGENT           si.example.myapmapp             I  Central config returned max age is null
2023-09-19 14:19:32.955 17360-17591 ELASTIC_AGENT           si.example.myapmapp             I  Scheduling next central config poll
2023-09-19 14:19:32.956 17360-17591 ELASTIC_AGENT           si.example.myapmapp             D  Next central config poll in 60 seconds

You can see warnings: Failed to export metrics. Server responded with HTTP status code 404. Error message: Not Found
And URL: https://api.example.si/config/v1/agents?service.name=MyAPMApp&service.environment=android-dev
which is wrong,
it has to be: https://api.example.si/es/some_path/config/v1/agents?service.name=MyAPMApp&service.environment=android-dev

Thank you for the detailed information. I'll have a look at it.

I realized that the initial path was indeed being removed in 2 places:

The Elastic's central config setup, which should be fixed in https://github.com/elastic/apm-agent-android/pull/189
OTel's gRPC exporter.

For OTel's gRPC exporter, I created this PR that should fix it, however, I'm not sure if replacing the initial path is actually an expected behavior in OTel, so I'm going to wait for some feedback on their side before proceeding to merge this other PR.
Thank you for your feedback.

They mentioned in this PR that, when using gRPC, this is an expected behavior. I'm still planning to merge this other PR since it's related to Elastic's central config and doesn't work with gRPC. It seems like you might be able to have a server with an initial path as long as you use HTTP instead of gRPC by setting an HTTP exporter such as OtlpHttpSpanExporter for example, you could do so by setting a custom SignalConfiguration in the ElasticApmConfiguration object where you'd provide all 3 http exporters like so:
ElasticApmConfiguration config = ElasticApmConfiguration.builder()
        .setSignalConfiguration(SignalConfiguration.custom(httpSpanExporter, httpLogExporter, httpMetricExporter))
        .build();
ElasticApmAgent.initialize(context, config);

Just be aware that the Elastic APM server's OTLP over HTTP support was added on version 8.3.0.

The non-OTel part of this issue is fixed by https://github.com/elastic/apm-agent-android/pull/189 which is already merged, so I'm closing this issue.


update 64 bit perforce

per #269

Please rebase this branch on top of master.

Closed via https://github.com/Homebrew/homebrew-binary/commit/e0ce8dc363942179345b192b1603310de42ee7f4.


Markdown Highlighting Broken

Markdown support seems to be broken. No syntax highlighting at all. Syntax highlighting for Javascript works fine though so this seems to be a markdown-specific issue.
Platform: Windows (portable version)
Version: 0.1.2

Looks like main branch of https://github.com/MDeiml/tree-sitter-markdown no longer be actively maintained. It is switching to split_parser branch. here is example in neovim treesitter by author https://github.com/nvim-treesitter/nvim-treesitter/pull/3048.

Fixed in #957


drivers: uart: native_posix: convert to DT_INST defines

Convert driver to fully use DT_INST_ defines.
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

@galak we are in freeze.. ;)

@aescolar Looks like it is merged into a topic branch or did I miss something ;)

true story, sorry for the noise :)

:), since the DT_INST changes touch a lot of drivers decided a topic branch that we hopefully will merge right after the release is made.


Duk_harray fixes and cleanups

Issues from merge review:

[ ] Debugger changes and testing (especially inspecting array .length)
[ ] Debugger migration notes
[x] Change duk_pack() and duk_unpack() visibility to internal
[ ] Add overflow check to duk_pack() count * sizeof(duk_tval)
[ ] Add helper for value stack range wipe for duk_pack() (may reduce footprint)
[ ] Error message "array .length not writable" maybe too verbose, just "not writable"?
[ ] "property is virtual" error message inconsistent with other error messages ("not writable" etc)
[ ] Add DUK_HTHREAD_GET_TOP() macro to replace top = (duk_idx_t) (thr->valstack_top - thr->valstack_bottom)
[ ] a->length = count after creating array with predefined size unnecessary in duk_pack()
[ ] putprop comment "may realloc and compact properties and hence change e_idx" inaccurate
[ ] "Write to 'length' of an array is a very complex case..." comment formatting consistency
[ ] "new length is higher than old length, just update length, no deletions" log comment incorrect, "higher or same" would be correct
[ ] Error traceback C filename handling now reads DUK_TVAL_GET_STRING() etc; just copy value using DUK_TVAL_SET_TVAL()?
[ ] Mark-and-sweep and refcount DUK_HOBJECT_IS_ARRAY() check is unnecessary as there's nothing to mark/refzero process; just comment and remove check?
[ ] Array length write XXX note; calling convention for handling array length change (via value stack)
[ ] "Creating an Array with a huge count creates a dense array but with no preallocated array part" comment in test case incorrect
[ ] Check DUK_DPRINT() calls in duk_hobject_props.c; should be very few in success paths
[ ] JX/JC handling of gappy arrays, now seems to use "null" for gaps but "undefined" might be more appropriate?
[ ] Uint8Array etc typed array and Object.defineProperty() handling
[ ] Lowmemory configuration: disable non-BMP sources and coroutines?

Regarding the error message, "not writable" might not be verbose enough.  If one were to, say:
arr.length = foobar.count = 0;

...and threw an error, which property does "not writable" apply to?

Right, but the same applies to:
foo.something = bar.somethingElse = 123;

Actually I thought this error was already changed a while back to "property 'foo' of [string representation] not writable"?

Those verbose error messages only apply to some common situations like the base value being invalid and such. In this particular case:
((o) Duktape [linenoise] 1.99.99 (v1.5.0-323-g164fe31)
duk> a = { foo: 123 }
= [object Object]
duk> Object.defineProperty(a, 'foo', { writable: false })
= [object Object]
duk> function foo() { 'use strict'; a.foo = 123; }
= undefined
duk> foo()
TypeError: not writable
    at [anon] (duk_hobject_props.c:4086) internal
    at foo (input:1) strict
    at global (input:1) preventsyield

While this is something to improve on, I don't think Array .length should have an error message of its own but should just use the same error message as other properties (verbose or not).

Yes, definitely agree it shouldn't be special-cased (outwardly at least :).

#703 introduced a (most likely harmless) warning:
duk_error_augment.c(190): warning C4267: '=': conversion from 'size_t' to 'duk_int_t', possible loss of data (compiling source file ..\src\shared\duktape.c)

Thanks, fixed :)

I'll make a note of improving more of the property error messages when I next touch the property code (there's some pressure to rework it for better performance). BTW, there are >300 throw sites in Duktape internals and not every call site produces an awesome error message (yet) :-)


Please support "launchd:" address family type

DBus 1.10 supports launchd addresses directly, according to the spec.
They take the form launchd:env=SOME_ENV_VAR. The examples I've found on line result in
launchd:env=DBUS_LAUNCHD_SESSION_BUS_SOCKET

I'm currently connecting to that bus with
dbus.sessionBus({ busAddress : "unix:path=" + process.env.DBUS_LAUNCHD_SESSION_BUS_SOCKET.toString() });

in addition to encoding values and passing vie busAddress you can use host, port and socket directly:
dbus.sessionBus({ soket: process.env.DBUS_LAUNCHD_SESSION_BUS_SOCKET } )

but I'm keen to support all transports in busAddress string

Oh yeah, that's tidy, too. Admittedly, the launchd: support is a bit minor. More important is that I can't get it to connect using socket or busAddress (see #96)


CFP: Add cluster filter for cilium dashboards

Cilium Feature Proposal
Is your feature request related to a problem?
We have several clusters with Cilium installations. We have a central Grafana and would like to use the dashboards to switch between the clusters.
Describe the feature you'd like
See above
(Optional) Describe your proposed solution
There is a variable feature in Grafana which could be used to switch between datasources and clusters.

Thanks for this @pixiono.
What would you like the Cilium Grafana dashboards to do differently? I agree it seems like the variable feature will probably be useful to do something like switch between clusters, but could you give some more detail on what you need?

Hi @pixiono, this doesn't feel like a topic that needs extensive discussion or planning. If you'd like to add this to the official Cilium Grafana dashboards, feel free to open a PR! This is a really minor change. Closing this out for now.


SharePoint permissions documentation

Hi,
Is there a place where permissions of files and folders in SharePoint sites are documented? When I try to query https://{tenant}.sharepoint.com/{siteName}/_api/v2.0/drive/items/{itemId}/permissions, I am getting that looks like the following
<EMAIL_ADDRESS>"https://{site-name}.sharepoint.com//_api/v2.0/$metadata#permissions",
"value": [
{
<EMAIL_ADDRESS>"#oneDrive.permission",
<EMAIL_ADDRESS>"https://{site-name}.sharepoint.com//_api/v2.0/oneDrive.permission{uid}",
<EMAIL_ADDRESS>"oneDrive.permission{uid}",
"id": "",
"roles": [
"read"
],
"link": {
"scope": "organization",
"type": "view",
"webUrl": Permission Url
}
},
{
<EMAIL_ADDRESS>"#oneDrive.permission",
<EMAIL_ADDRESS>"https://{site-name}.sharepoint.com//_api/v2.0/oneDrive.permission{uid}",
<EMAIL_ADDRESS>"oneDrive.permission{uid}",
"id": {uid},
"roles": [
"write"
],
"link": {
"scope": "organization",
"type": "edit",
"webUrl": Permission Url
}
},
{
<EMAIL_ADDRESS>"#oneDrive.permission",
<EMAIL_ADDRESS>"https://{site-name}.sharepoint.com//_api/v2.0/oneDrive.permission{uid}",
<EMAIL_ADDRESS>"oneDrive.permission{uid}",
"grantedTo": {
"user": {
"displayName": "Company Administrator"
}
},
"id": {uid}
"roles": [
"write"
]
}
]
What I didn't understand here is scope values (organization in above output) of link attribute. Also, when I share a file with some user or a group, I don't see the permission granted to the user or group in the rest call output.
Can anyone please help me with the issue?

Hi team,
Any update on this?

That isn't covered by our docs yet. Links with "scope": "organization" is a new feature of SharePoint and OneDrive for Business that allows the links to be used by anyone within the company, but not external users / anonymous access. They are currently automatically created for every file in OneDrive for Business, but can be deleted/removed by the user through the sharing dialog.
We'll update the docs soon to include this additional parameter.


HTTPS broke some links

After uploading images, it redirects to http even on the https version.

This commit will allow your to set HTTP or HTTPS in the config.yml file.
Most links appear to work without this fix, however url_for function fails to accept the forwarded scheme (at least while we are using Apache to direct traffic to the PixPlot Docker container currently using gunicorn). I tested a number of configurations. I believe it may be possible to do with Nginx in the middle or wsgi, but I'm hard pressed to come up with a solution using either that is not overly complex for this limited app!

This issue may be related as well. It does not seem like this would have any effect.


Replicated subscriptions - Markers protobuf

Motivation
2nd part of the PIP-36. This PR adds the Protobuf definitions and ser/de for the internal markers used for snapshot building and subscription updates.

run java8 tests


Don't build on darwin with Cicero for now

Description
Recently, aarch64-darwin machines were added. We do not want to build on those on CI at least for now, see #4461.
Checklist

Branch

[x] Commit sequence broadly makes sense
[x] Commits have useful messages
[ ] The documentation has been properly updated
[ ] New tests are added if needed and existing tests are updated
[ ] Any changes affecting Consensus packages must have an entry in the appropriate changelog.d directory created using scriv. If in doubt, see the Consensus release process.
[ ] Any changes in the Consensus API (every exposed function, type or module) that has changed its name, has been deleted, has been moved, or altered in some other significant way must leave behind a DEPRECATED warning that notifies downstream consumers. If deprecating a whole module, remember to add it to ./scripts/ci/check-stylish.sh as otherwise stylish-haskell would un-deprecate it.
[ ] If this branch changes Network and has any consequences for downstream repositories or end users, said changes must be documented in interface-CHANGELOG.md
[ ] If serialization changes, user-facing consequences (e.g. replay from genesis) are confirmed to be intentional.

Pull Request

[ ] Self-reviewed the diff
[ ] Useful pull request description at least containing the following information:

What does this PR change?
Why these changes were needed?
How does this affect downstream repositories and/or end-users?
Which ticket does this PR close (if any)? If it does, is it linked?

[ ] Reviewer requested

Could it be that the aarch64-darwin jobs are mostly empty due to this?
https://github.com/input-output-hk/ouroboros-network/blob/e4a222f8e0f5d55591cc14b062332a8a61e85724/release.nix#L64-L66

Hmm good point, then I wonder how the zw3rk Hydra manages to build for aarch64-{linux,darwin} (see e.g. the checks for e4a222f8e0f5d55591cc14b062332a8a61e85724; we let the master commits be built by zw3rk, but don't use it for PRs as it was under pressure some time ago).
In that case, the aarch64-darwin check basically only checks Nix evaluation on aarch64-darwin, which seems neat and is not blocking anything, so I will close this PR for now.


add Dell template files

Merging this PR for initial testing but want to call out the following:

Parameter file should be complete to ensure consistency with the template file.
Parameter file does not specify intent & adapter to lock them in
Metadata file does not contain URL for EULA


Run multiple-model in parallel

Overview
This PR fixes #13
Changes:

Multiple outputs are zipped for the WPS output.

@julemai This PR fails on Mac and it's hard for me to debug just from the Travis output. I've changed the way raven is called to support multiple parallel processes and I guess that's where the error comes from.
You'll see in base.py that run returns a list of processes, and __call__ waits for them. My guess is that on Mac the process either doesn't start, or python doesn't wait for it to complete.
Do you have some time to look at this ?

@julemai This PR fails on Mac and it's hard for me to debug just from the Travis output. I've changed the way raven is called to support multiple parallel processes and I guess that's where the error comes from.
You'll see in base.py that run returns a list of processes, and __call__ waits for them. My guess is that on Mac the process either doesn't start, or python doesn't wait for it to complete.
Do you have some time to look at this ?

On it now.

@huard Seems like the problem is that the output folder that is used in cmd in base.py line 371 (option -o) is not existing. It expects <path>/model/p00/output but output is not created. Wondering why this would work on other platforms though.

Thanks !

All passing now on my Mac. :)

Yé ! @richardarsenault, you'll need to approve the PR for me to merge it.


Move Slack icon next to GitHub icon

Move the Slack icon (currently in the footer) to the right of the GitHub icon, as indicated below:

@knjk04 I have been looking for a solution in official documentation for this but looks like such links can be added only in footer section. I went through the list of clients to see if any of them have done any such customization but couldn't find any. I think as of now, material-mkdocs is not supporting adding additional options in header.

@kpnigalye Thanks for looking into this


Error and DynError and Box and env::var() and env::set_var()

Part of #324

Still need to test the box methods that this PR includes.


chore: add Vaadin usage statistic

Closes #213

@tarekoraby can you take a look at this PR if you have time?

LGTM, as far as the UsageStatistics.markAsUsed() is being used. When you use it locally after this change is merged, let me know and I'll check if the stats are being collected as expected.

I merge the change. @Dudeplayz we can review the README section later on


[DOC] Invalid  call back URL example in the OAuth2-OpenID Connect Single-Sign-On configuration document

Invalid sample call back url for the sample web app playground.
Expected callback url: https://myapp.com/callback|https://testapp:8000/callback
Actual callback url: https://myapp.com/callback|https://testapp:8000/callback**)**
Document: https://docs.wso2.com/display/IS570/Configuring+OAuth2-OpenID+Connect+Single-Sign-On
Affected : Version 5.2.0 +
Severity: Minor
Priority : Normal
Component : SAML SSO
Type: Document/product scenario

Closing this because the bracket is required there. It's inside a code block where we are asking the user to set the regex pattern as follows:
regexp=(https://myapp.com/callback|https://testapp:8000/callback)


Tobin gh1030 refinement

Replaces #1159
Fixes #1030
I found that those initial changes were causing new errors on smoketest. Upon further investigation, smoketest binds memory to a buffer without ever calling vkGetBufferMemoryRequirements().
There's an implication in the spec that this is invalid, although I don't see that it's explicitly stated anywhere.
To deal with this issue initially, I've added warnings in the case where memory is bound to a buffer/image without first checking the requirements and then validation will make the requirements call itself to fill its state.
There is still more work to be done to refactor BindImage/BufferMemory functions to Pre/Post and add proper checks for all of the VUs along with tests. Also need to fix smoketest. I'll open separate issues for these, but this PR is focused on getting the fix in for 1030.

cherry-picked and pushed to master


Fix 0.11.0-rc.1

What type of PR is this?
Add one of the following kinds:

bug

What this PR does / why we need it:
Fixes trailing whitespace issue
Removes example from networkAccessIdentifier
Which issue(s) this PR fixes:
Fixes the trailing whitespace and inapplicable example resulting from the PR #23 [commit]
(https://github.com/camaraproject/SimpleEdgeDiscovery/pull/23/commits/6bea72271ee009f5e3db760b1e915767ba6ceb9e)
Further commits cannot be made to update PRs on a protected branches, hence this PR is needed to update PR #23
Special notes for reviewers:
Changelog input
 release-note

Additional documentation
This section can be blank.
docs

@javierlozallu hope it's ok to assign you - this review is simply to fix the errors spotted in the 0.11.1-rc.1 commit , so that all the reviewers have a 'clean' copy of 0.11.0-rc.1 to review.


set correct arg for validate_date

Pull Request Test Coverage Report for Build 91

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.026%

Totals

Change from base Build 89:
0.0%

Covered Lines:
1957

Relevant Lines:
2038

💛  - Coveralls


TOTP support

I am attempting to set up a user pool with Multi-Factor Authentication and allow users to select a Time-based One-time Password using Google Authenticator. How do you respond to a challenge of type SOFTWARE_TOKEN_MFA using AWS .Net SDK?
ASP.Net Core 3 with Identity
Amazon.Extensions.CognitoAuthentication Version=1.0.4

Hi @jeff-heienickle,
After looking through this support library, it appears that unfortunately at the moment there is no wrapper for responding to a SOFTWARE_TOKEN_MFA challenge, as you can see here.
If you would like to see how to respond to the challenge without the cognito extensions, please look at the Cognito Identity Provider library in the main .NET SDK.
However, implementing said wrapper seems fairly simple, so I can push a fix, then get back to you. Alternatively, if you feel like contributing, feel free to put in a PR with the changes, and I can review it.
After added this, implementing would be as simple as following the MFA instructions from the README.
Please let me know if this helps answer your question, and if you would like to implement this yourself, or see it implemented, and I will close the issue.
😸 😷


refactor UOps Pattern Matcher

[x]  add UPat + refactor _match() and PatternMatcher
[x]  refactor constant_folder and assembly.py
[x]  regression tests

CI is broken. I would suggest making this a draft pr if it is not ready yet.
Also, it seems to be a lot of changes related to formatting, I would recommend reverting those and leaving only the ones required for refactoring UOps

CI is broken. I would suggest making this a draft pr if it is not ready yet.

Yeah I messed up upstream merge conflicts. I think its fixed now. But some tests (ptx, nv) are failing:
File "/home/runner/work/tinygrad/tinygrad/tinygrad/renderer/assembly.py", line 383, in <module>
    UPat(
TypeError: UPat.__init__() got an unexpected keyword argument '__allow_len__'

Should I change UPat ?

Is this a functional change or a whitespace change? If no functional changes are expected, how have you verified that.

Still contains whitespace changes. Closed in favor of #4791


some models are working, other don't

Hi there.
models i've tested that work :
Phi-3.1-mini-4k-instruct-Q5_K_M.gguf
Meta-Llama-3.1-8B-Instruct-Q5_K_M.gguf
Mistral-Small-Instruct-2409-Q4_K_M.gguf
models that don't :
Mistral-Nemo-Instruct-2407.Q4_K_M.gguf
mixtral-8x7b-instruct-v0.1.Q4_K_M.gguf
related settings :
# LLM settings
LLM_CONFIG = {
    "model_path": MODEL_PATH,
    "n_ctx": 16384,  # context size default 20000
    "n_gpu_layers": -1,  # number of layers to offload to GPU (-1 for all, 0 for none)
    "n_threads": 8,  # number of threads to use
    "temp": 0.7,  # temperature for sampling
    "top_p": 0.9,  # top p for sampling
    "top_k": 40,  # top k for sampling
    "repeat_penalty": 1.1,  # repeat penalty
    "max_tokens": 8192,  # max tokens to generate
    "stop": ["User:", "\n\n"]  # stop sequences
}

Logs :
2024-09-19 18:59:27,591 - ERROR - Error initializing LLM: Failed to load model from file: /whatever/mixtral-8x7b-instruct-v0.1.Q4_K_M.gguf
Traceback (most recent call last):
  File "/whatever/Web-LLM-Assistant-Llama-cpp/Web-LLM.py", line 105, in initialize_llm
    llm = Llama(**llm_config)
  File "/whatever/Web-LLM-Assistant-Llama-cpp/venv/lib/python3.10/site-packages/llama_cpp/llama.py", line 338, in __init__
    self._model = _LlamaModel(
  File "/whatever/Web-LLM-Assistant-Llama-cpp/venv/lib/python3.10/site-packages/llama_cpp/_internals.py", line 57, in __init__
    raise ValueError(f"Failed to load model from file: {path_model}")
ValueError: Failed to load model from file: /whatever/mixtral-8x7b-instruct-v0.1.Q4_K_M.gguf

Hi there.
models i've tested that work : Phi-3.1-mini-4k-instruct-Q5_K_M.gguf Meta-Llama-3.1-8B-Instruct-Q5_K_M.gguf Mistral-Small-Instruct-2409-Q4_K_M.gguf
models that don't : Mistral-Nemo-Instruct-2407.Q4_K_M.gguf mixtral-8x7b-instruct-v0.1.Q4_K_M.gguf
related settings :
# LLM settings
LLM_CONFIG = {
    "model_path": MODEL_PATH,
    "n_ctx": 16384,  # context size default 20000
    "n_gpu_layers": -1,  # number of layers to offload to GPU (-1 for all, 0 for none)
    "n_threads": 8,  # number of threads to use
    "temp": 0.7,  # temperature for sampling
    "top_p": 0.9,  # top p for sampling
    "top_k": 40,  # top k for sampling
    "repeat_penalty": 1.1,  # repeat penalty
    "max_tokens": 8192,  # max tokens to generate
    "stop": ["User:", "\n\n"]  # stop sequences
}

Logs :
2024-09-19 18:59:27,591 - ERROR - Error initializing LLM: Failed to load model from file: /whatever/mixtral-8x7b-instruct-v0.1.Q4_K_M.gguf
Traceback (most recent call last):
  File "/whatever/Web-LLM-Assistant-Llama-cpp/Web-LLM.py", line 105, in initialize_llm
    llm = Llama(**llm_config)
  File "/whatever/Web-LLM-Assistant-Llama-cpp/venv/lib/python3.10/site-packages/llama_cpp/llama.py", line 338, in __init__
    self._model = _LlamaModel(
  File "/whatever/Web-LLM-Assistant-Llama-cpp/venv/lib/python3.10/site-packages/llama_cpp/_internals.py", line 57, in __init__
    raise ValueError(f"Failed to load model from file: {path_model}")
ValueError: Failed to load model from file: /whatever/mixtral-8x7b-instruct-v0.1.Q4_K_M.gguf

Hey thanks for letting me know, so can I ask do the models that failed to work run under your Llama.cpp fine without using this program? if so can you please share the CLI input you use to run them successfully with just llama.cpp and tell me if the same settings in the llm_config script don't work even though your llama.cpp does?
If you let me know I can try and figure this issue out the best I can!

$ llama-cli -v
main: build = 3758 (3c7989fd)
main: built with cc (Debian 12.2.0-14) 12.2.0 for x86_64-linux-gnu

This works :
/whatever/llama.cpp/llama-server -m /whatever/Mistral-Nemo-Instruct-2407.Q4_K_M.gguf --ctx-size 16384 --threads 8 --temp 0.7 --top-p 0.9 --top-k 40 --repeat-penalty 1.1 --n-gpu-layers -1
This works once then fills my RAM 100% :
/whatever/llama.cpp/llama-server -m /whatever/mixtral-8x7b-instruct-v0.1.Q4_K_M.gguf --ctx-size 16384 --threads 8 --temp 0.7 --top-p 0.9 --top-k 40 --repeat-penalty 1.1 --n-gpu-layers -1
So Mistral-Nemo-Instruct-2407.Q4_K_M.gguf should work, for mixtral-8x7b-instruct-v0.1.Q4_K_M.gguf i might be doing something wrong or my system is not capable enough even with lower --ctx-size (NVIDIA 3090 24 Go VRAM)

Hey, so I've just done some testing on both Mistral-Nemo-Instruct-2407.Q4_K_M.gguf and mixtral-8x7b-instruct-v0.1.Q4_K_M.gguf
both work fine on my system (NVIDIA 3070) like no issues at all within the program, can you please double check the file paths, and perhaps re-download and reinstall dependencies for the program and see if that fixes it?
Also you could try setting a specific amount of GPU layers, rather then using all of them if your GPU is struggling, but I am quite confused because your graphics card should be better then mine and mine is working fine! so double check file paths re-download and then let me know how you go because from what I tested there isn't an issue for me!

Many thanks for testing.
it was a PEBKAC as i guess i was using an outdated python wheel for llama-cpp-python (v0.2.76-cu124 instead of v0.2.90-cu124)
Solved with :
pip install --no-cache-dir https://github.com/abetlen/llama-cpp-python/releases/download/v0.2.90-cu124/llama_cpp_python-0.2.90-cp310-cp310-linux_x86_64.whl
Both models work now.

Cool I'm glad you fixed it! please let me know if there are any other problems that you notice!


[#854][FOLLOWUP] feat(tez): add RssTezFetcher to fetch data from worker.

What changes were proposed in this pull request?
add RssTezFetcher to fetch data from worker.
Why are the changes needed?
Fix: https://github.com/apache/incubator-uniffle/issues/854
Does this PR introduce any user-facing change?
No.
How was this patch tested?
unit test

we will add unit test later.

we will add unit test later.

Will you add ut in this pr?

we will add unit test later.

Will you add ut in this pr?

in this pr

ok, we added unit test case, Dalao look look if there any problems .

Codecov Report

Merging #920 (db6c509) into master (6471c5e) will increase coverage by 1.12%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #920      +/-   ##
============================================
+ Coverage     55.53%   56.66%   +1.12%
+ Complexity     2246     2047     -199
============================================
  Files           341      293      -48
  Lines         16626    12934    -3692
  Branches       1327     1202     -125
============================================
- Hits           9234     7329    -1905
+ Misses         6863     5204    -1659
+ Partials        529      401     -128

see 54 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Provide a --machine flag for flutter analyze

Just like --version --machine we need to process the output of flutter analyzer in a mache-friendly way.
Thankfully, we already do this with the regular dart analyzer with the --format machine flag. https://github.com/dart-lang/pana/blob/2e30307bd6babc07a8b133b3dd927d7f65ebc3e9/lib/src/sdk_env.dart#L44
We just need flutter analyzer to

Add a --machine flag
Pass it on as --format machine to dartanalyzer
Either don't print other output, or make it trivial to exclude from reliably by a line-by-line parser. (Put in a big *FLUTTER*: prefix, encode the values in single-line JSON, open for discussion)

This is blocking https://github.com/dart-lang/pana/issues/32
Which is blocking https://github.com/dart-lang/pub-dartlang-dart/issues/170

CC @mit-mit

@danrubel is this something you can help with? We need this to get proper analysis of flutter packages & plugins on pub, which is needed to properly calculate package health.

QQ after looking at the source, it seems this not anything special beyond
setting the packet directory. Right?
No special lint or anything. Am I missing something?
From mobile. Sorry for brevity and/or spelling.
On Jun 15, 2017 11:44 AM, "Michael Thomsen"<EMAIL_ADDRESS>wrote:

@danrubel https://github.com/danrubel is this something you can help
with? We need this to get proper analysis of flutter packages & plugins on
pub, which is needed to properly calculate package health.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/10704#issuecomment-308683301,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABCikOtxrfdpheGDLtxZVm-8nGjDE9oks5sEP0WgaJpZM4N6YWZ
.

I'm updating flutter analyze to use the analysis server in the same way and using the same code as flutter analyze --watch. While I'm there I need to make sure that all the current flutter analyze options are supported. I can add this to the list.

QQ after looking at the source, it seems this not anything special beyond
setting the packet directory. Right?
No special lint or anything. Am I missing something?

@mit-mit @danrubel – thoughts here?

Not sure I understand your QQ, but ....
flutter analyze will be using analysis server rather than dartanalyzer to perform analysis, so unfortunately supporting a machine format will not be as easy as just adding a flutter analyze flag and forwarding that to the analysis engine.

Not sure I understand your QQ, but ....

Does (or will) flutter analyze do anything "special" beyond just running dartanalyzer? Special lints/flags/options/etc?

will be using analysis server...

That will make things more difficult.
I'm guessing it will dump a nice, complete list of errors/warnings/hints/lints to stdout, right?
Could we have an option to format them exactly like dartanalyzer --machine ?

I'm guessing it will dump a nice, complete list of errors/warnings/hints/lints to stdout, right?

Correct.

Could we have an option to format them exactly like dartanalyzer --machine ?

Definitely. That's the goal.

@danrubel what about

Does (or will) flutter analyze do anything "special" beyond just running dartanalyzer? Special lints/flags/options/etc?

It won't be running dartanalyzer. It will be running analysis server instead. Whatever lints/analysis/options are provided by analysis server will be available in flutter analyze as well.

https://github.com/dart-lang/pana/issues/32 was closed as not needed, so since this was filed because of that bug, I will close this one also. Please reopen the bug if it's still needed after all.


Fix deployment environment names

Codecov Report

Merging #484 (cc620cf) into main (540c5f8) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #484   +/-   ##
=======================================
  Coverage   98.52%   98.52%
=======================================
  Files          30       30
  Lines         542      542
  Branches       73       73
=======================================
  Hits          534      534
  Misses          8        8

Continue to review full report at Codecov.

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


robot-name: test runner fails on bonus test

I see from this solution that the test runner is apparently having trouble running the bonus tests (protected by a build tag):
We received the following error when we ran your code:
FAIL	robotname [build failed]
'/usr/local/go/bin/go test --json .' returned exit code 2: exit status 2

So the tests show as failed even though the student is not trying to pass the bonus test. We need to figure out what to do here, don't we? Perhaps the simplest thing is just to drop the 'bonus' idea and make it part of the standard tests.
For those not familiar with the exercise, the bonus test checks that the solution does not hang when there are no more possible names to generate, but instead returns an error. I think it's quite reasonable to include this as a non-bonus part of the exercise, but what does everybody else think?

If keeping the simplicity of not having the bonus is important, the bonus test could be extracted as its own new problem.
So the easy version  just focuses on teaching random generation.
Then a harder version like "robot name reloaded" can have the "bonus".
Has such pattern (exercise building on each other) been used before / is desired ?

One problem with the simple version (that is, the one that doesn't detect running out of names) is that the benchmark hangs, and students usually don't understand why this is. (It's because the benchmarker is quite liable to run the function more than 676,000 times, thus exhausting the robot namespace.)
A common way to solve this is by generating all possible names in advance and permuting them, which is desperately slow and wasteful, and complicated.
On the other hand, if you need to pass the bonus test (which is specifically that your function returns an error when there are no more names available), then you can write the simple solution (generate names randomly on request) with no problems. So my vote would be to make the bonus test part of the normal tests, and drop the build tag mechanism (which we don't use for any other exercise, as far as I know).

How about we give the student control by putting a constant in robot_name.go that defaults to false then the bonus instructions could say set the constant to true to enable the bonus test. Then we put everything in one test file as bitfield suggests and use the constant value in robot_name.go to noop the test unless they have enabled it. Allows students to opt into the extra testing without forcing everyone to do the bonus test unless they want to. Seems like a balance of alternative viewpoints and fixes the main problem bitfield identified.
Also, this exercise in general seems to be pretty weak on instructions given that we give them a completely empty stub file and the tests are not trivially instructive about what the boolean inputs mean (eg. this test).

Just to be clear, I'm suggesting that the 'doesn't hang forever when out of names' test is a really good way of steering students towards a better solution without mentor input (or perhaps more accurately, steering them away from a variety of bad solutions). This seems more in the spirit of Exercism V3, doesn't it?

Just to be clear, I'm suggesting that the 'doesn't hang forever when out of names' test is a really good way of steering students towards a better solution without mentor input (or perhaps more accurately, steering them away from a variety of bad solutions). This seems more in the spirit of Exercism V3, doesn't it?

I like that. I am sufficiently sold on this idea. So current proposal here:

Make the bonus test part of the standard test suite.
Update the instructions to be more explicit about this requirement.
Remove the Benchmark test since it is pretty redundant once you add the bonus test (and students using the UI will not be able to see the benchmark anyways).

@ekingery - do you agree with that plan?
NOTE: we already skip benchmark tests in the test runner (somewhat manually).

@ekingery - do you agree with that plan?

Yes, I agree. Thanks for checking. The build tags should definitely be a separate concept (if that), and not included as an optional sidebar. I'm pretty sure that is not a pattern we want to encourage.
Overall, it's a tough call because the bonus makes it a much more involved problem. But that's probably fine as it's just a practice exercise and doesn't have stated concepts or goals, etc. I'm guessing the lack of clear instructions and context around why the unique aspect is important or interesting is causing additional confusion / poor solutions.


Add ability to specify working directory of hooks

Follow up to https://github.com/gruntwork-io/terragrunt/pull/1584

Thanks for review! Going to merge + release now.


Allow for CPU-specific kernel to be set from zone_options_t

At some point, NSD will use a more efficient database. The prototype checks what "kernel" to use repeatedly, for parsing zone files, that will also be the case (i.e. once per invocation of zone_parse). An application should select the "kernel" to use at startup for consistency.

Also include the option to set a preferred kernel (e.g. westmere, fallback), so we can include an option in NSD to "forcefully" set a specific kernel. Useful for situations where a hypervisor returns bad data for the CPUID instruction (not the case in #222, but would be useful to work around the bug from a user perspective). Also be sure to allow for convenient fetching of the associated kernel name so we can print in the NSD logs which kernel has been selected (see NLnetLabs/nsd#354).


Not usuable in typescript projects

You are missing declaration types

After adding this to your Project, then you can use the module!

Sorry for that, I will try to fix that asap because this was a JS focused NPM Package


Debug toolbar draggable in the 4 edges of the VS Code screen.

Feature Request
The debug toolbar that appear when the a process is running, often (in my opinion) is in the wrong place and cover tabs/refresh buttons/console buttons.
I'd like to drag this toolbar in a custom edge of the editor like in the bottom.

This looks like a duplicate of #9093
Let me know if that is not the case

@mjbvz it is. Thanks very much


corrected the error with a group work and coding - nasir ali - group coding with appolin

Naming Rules
Name your PR like this: ISSUENUMBER-TITLE-YOURNAME
Description
Write a summary of your change. Explain why you have made it.
Related to
Make sure you include the issue number with a hash sign # so Github can link this PR to the right issue, like this:
Fixes #1
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have carefully reviewed my own code
[ ] I have commented my code
[ ] I have updated any documentation

Please fix up the PR description, it should contain:

Which issue is this adressing
What is this change actualy doing


fix bug of nifcloud_loadbalancer resource for use ssl_policy_name

Description

fix bug of nifcloud_loadbalancer resource for use ssl_policy_name

How Has This Been Tested?

[x]   Buld with make install command.

make install

[x]   Apply this example.

terraform {
  required_providers {
    nifcloud = {
      source = "nifcloud/nifcloud"
    }
  }
}

provider "nifcloud" {
  region = "jp-east-1"
}

resource "nifcloud_load_balancer" "basic" {
  load_balancer_name = "l4lb"
  instance_port      = 80
  load_balancer_port = 443
  accounting_type    = "1"
  ssl_certificate_id = nifcloud_ssl_certificate.basic.id
  ssl_policy_name    = "Standard Ciphers D ver1"
}

resource "tls_private_key" "basic" {
  algorithm = "RSA"
}

resource "tls_self_signed_cert" "basic" {
  private_key_pem       = tls_private_key.basic.private_key_pem
  validity_period_hours = 3
  dns_names             = ["example.com"]
  allowed_uses          = ["client_auth"]

  subject {
    common_name  = "example.com"
    organization = "ACME Examples, Inc"
  }
}

resource "nifcloud_ssl_certificate" "basic" {
  certificate = tls_self_signed_cert.basic.cert_pem
  key         = tls_private_key.basic.private_key_pem
}

[x] Run acceptance tests.

TF_ACC=1 go test ./nifcloud/acc/... -v -count 1 -parallel 1 -timeout 360m -run TestAcc_LoadBalancer

[x] Enjoy!!😸

Types of Changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Refactoring (improves code quality but has no user-facing effect)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation

Acceptance test passed.
$ TF_ACC=1 go test ./nifcloud/acc/... -v -count 1 -parallel 1 -timeout 360m -run TestAcc_LoadBalancer
?       github.com/nifcloud/terraform-provider-nifcloud/nifcloud/acc/helper     [no test files]
=== RUN   TestAcc_LoadBalancerListener
=== PAUSE TestAcc_LoadBalancerListener
=== RUN   TestAcc_LoadBalancer
=== PAUSE TestAcc_LoadBalancer
=== CONT  TestAcc_LoadBalancerListener
--- PASS: TestAcc_LoadBalancerListener (458.02s)
=== CONT  TestAcc_LoadBalancer
--- PASS: TestAcc_LoadBalancer (489.02s)
PASS
ok      github.com/nifcloud/terraform-provider-nifcloud/nifcloud/acc    947.047s

LGTM 🐱


add date to Hr letter model

add a date field to Hr letter, set the default date to the applying date
modify the serializer and requests API to handle this update

implemeneted!


search-guard installation fails in ES 2.4.1

I have downloaded the version <IP_ADDRESS> of searchguard .
sudo bin/plugin install -b com.floragunn/search-guard-2/<IP_ADDRESS>
and it fails to install saying

-> Installing from file:/app/v<IP_ADDRESS>.zip...
Trying file:/app/v<IP_ADDRESS>.zip ...
Downloading ..DONE
Verifying file:/app/v<IP_ADDRESS>.zip checksums if available ...
NOTE: Unable to verify checksum for downloaded plugin (unable to find .sha1 or .md5 file to verify)
ERROR: Could not find plugin descriptor 'plugin-descriptor.properties' in plugin zip

No need to download, you install Search Guard directly from Maven Central. From this:
-> Installing from file:/app/v<IP_ADDRESS>.zip...
Trying file:/app/v<IP_ADDRESS>.zip ...
I'm seeing that you try to install a zip file from a local directory. This is also possible, but you need the release zip file from Maven, not the sources from GitHub.
Anyways, this command:
sudo bin/plugin install -b com.floragunn/search-guard-2/<IP_ADDRESS>
fetches SG directly from Maven, and you should see an output like this:
sudo bin/plugin install -b com.floragunn/search-guard-2/<IP_ADDRESS>
Password:
-> Installing com.floragunn/search-guard-2/<IP_ADDRESS>...
Trying https://download.elastic.co/com.floragunn/search-guard-2/search-guard-2-<IP_ADDRESS>.zip ...
Trying https://search.maven.org/remotecontent?filepath=com/floragunn/search-guard-2/<IP_ADDRESS>/search-guard-2-<IP_ADDRESS>.zip ...
Downloading ..........DONE
Verifying https://search.maven.org/remotecontent?filepath=com/floragunn/search-guard-2/<IP_ADDRESS>/search-guard-2-<IP_ADDRESS>.zip checksums if available ...
Downloading .DONE
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@     WARNING: plugin requires additional permissions     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

java.lang.RuntimePermission getClassLoader
java.lang.RuntimePermission setContextClassLoader
java.lang.RuntimePermission shutdownHooks
javax.security.auth.AuthPermission doAs
javax.security.auth.AuthPermission modifyPrivateCredentials
javax.security.auth.kerberos.ServicePermission * accept
See http://docs.oracle.com/javase/8/docs/technotes/guides/security/permissions.html
for descriptions of what these permissions allow and the associated risks.
Installed search-guard-2 into /Users/jkressin/Development/elasticsearch-2.4.1/plugins/search-guard-2

See also the installation instructions in the documentation:
https://github.com/floragunncom/search-guard-docs/blob/master/installation.md


Dates @usercomments are NULL on IPAD

There is a bug with the display of comments by the pictures.
On computer the dates are OK , on IPAD the dates @comments are 1 january 1970 or all null null null null null null null nul:null

Thanks man, I'll check on Safari

On Yosemiti it works well in Safari except the date format is long date time which does not look so nice :(. I will try to add a date format support.
For the iPad issue, I'll have to check on the device it self

Code change for DateTime parsing check in. Please report if issue still exeists


feat: add Hero image

What is done:

HeroImage. It takes a free space in the viewport. I implement it using variables, so the user could change it in Codux.
Header styles fixed a little bit.

https://github.com/user-attachments/assets/0b4da061-095f-4033-bd21-1d0c8d3cab8f

Not ready yet.


GadgetBridge: Notification never stops?

I've just configured my Android with GadgetBridge and the Bangle-Smartwatch.
As soon as I get an notification on my android - i.E. WhatsApp - I get the same on my Bangle. Great. But: the Bangle vibrates and never stops. I do have to push a button; best case: Button 3 for round about 3 secs.
I guess this could not be the requested feature?
I'm using the current GadgetBridge on Android from F-Droid and the newest available GadgetBridge-App for Bangle.

Did you try tapping the screen to dismiss the notification?

Yes. Then the "Messagebox" disappears, but the watch keeps vibrating.
I'm specially thinking of this: what if during the night, when I'm sleeping I'm getting a notification? Does the watch will vibrate that strong that I will wake up?
From my point of view, the whats never stops vibrating until I press a button (Button2 and Button3 works).
Currently I have waited up to 30 Seconds.

Looks like this issue only occurs when using the centerclock-Watchface.
With Mixed Clock, for example, it works perfect: one short vibrate, not more.

Thanks - that's really helpful for narrowing it down!

Does this happen all the time? Just tried it here, and it only happens on the first notification after GadgetBridge connects. Subsequent notifications are fine.
I've narrowed it down to Gadgetbridge sending a setTime command when it connects. When the new Gadgetbridge release comes out you'll just be able to turn off 'Time Sync' and it'll work fine.
I'm still unsure why Centerclock in particular has this problem though!

Does this still happen? It might be fixed now?


Fix Xcode 14 build

Prior to this change cmake -G Xcode .. was failing with
CMake Error in interfaces/CMakeLists.txt:
  The custom command generating

    /Users/andrew/silkworm/interfaces/types/types.pb.cc

  is attached to multiple targets:

    generate_sentry_grpc
    generate_kv_grpc
    generate_ethbackend_grpc

  but none of these is a common dependency of the other(s).  This is not
  allowed by the Xcode "new build system".

When that was fixed, Xcode 14 complained about some conversions.

👍 What do you use to reformat the code?

My VS Code calls clang-format on file save.


contact views

Create a view inside the view.py file
Create a url in the urls.py
Link the 'contact.html' file to view.py


Compiler is unable to type-check seemingly simple expression in reasonable time and refuses to build

Description
The compiler refuses to build this "seemingly" simple ForEach expression:

The User struct is a simple struct consisting of a name as String and an id as UUID:
struct User: Identifiable {
    let id = UUID()
    var name: String
}

struct SomeView: View {
    var users = [
        User(name: "User one"),
        User(name: "User two"),
        User(name: "User three")
    ]

    var body: some View {
        HStack {
            ForEach(users.indices, id: \.self) { index in
                Text(users[index].name)
                    .offset(x: CGFloat((users.count - index - 1) * 30))
            }
        }
    }
}

Steps To Reproduce

create the User and a View containing ForEach with offset depending on indices
"The compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions"
...

Expected behavior
The compiler working and being able to build. The desired outcome would be something like this, where some users info are stacked with offset upon each other:

Environment (please fill out the following information)

OS: Ventura 13.0
Xcode Version/Tag/Branch: Version 14.1 (14B47b)

After restarting my mac it works now.


preload chunks: read range for 0: allocate chunk bytes: pool exhausted : query :store:

Thanos, Prometheus and Golang version used:
Thanos .18.0
Go go1.15.7
Prometheus  2.24.0
Object Storage Provider: GCS
What happened:
Installing the kube-prometheus stack with the default alerts and recording rules and setting those to be managed by the thanos ruler. I expect them all to recording the new metrics within thanos correctly but i keep getting these error messages
Logs

2021-03-29 12:33:44.508 BSTlevel=error ts=2021-03-29T11:33:44.508793543Z caller=proxy.go:307 component=proxy request="min_time:1614425620852 max_time:1617017620852 matchers:<name:"job" value:"apiserver" > matchers:<name:"le" value:"5" > matchers:<name:"scope" value:"cluster" > matchers:<type:RE name:"verb" value:"LIST|GET" > matchers:<name:"name" value:"apiserver_request_duration_seconds_bucket" > aggregates:COUNTER partial_response_disabled:true " err="Addr: <IP_ADDRESS>:10901 LabelSets: {prometheus="observability/kps-prometheus", prometheus_replica="prometheus-kps-prometheus-0"},{prometheus="observability/kps-prometheus"},{thanos_ruler_replica="thanos-ruler-thanos-rule-0"},{thanos_ruler_replica="thanos-ruler-thanos-ruler-slo-alerts-0"} Mint:<PHONE_NUMBER>022 Maxt:<PHONE_NUMBER>000: receive series from Addr: <IP_ADDRESS>:10901 LabelSets: {prometheus="observability/kps-prometheus", prometheus_replica="prometheus-kps-prometheus-0"},{prometheus="observability/kps-prometheus"},{thanos_ruler_replica="thanos-ruler-thanos-rule-0"},{thanos_ruler_replica="thanos-ruler-thanos-ruler-slo-alerts-0"} Mint:<PHONE_NUMBER>022 Maxt:<PHONE_NUMBER>000: rpc error: code = Aborted desc = fetch series for block 01F1CJK4N2XYMMKFYMCP9MWAKH: preload chunks: read range for 0: allocate chunk bytes: pool exhausted"

I have tried setting the store to
- --index-cache-size=500MB
- --chunk-pool-size=2GB
Makes no difference , I also increased the replica set of the query to 4 but still get these errors

can anyone provide any pointers

@GiedriusS Thank you for your reply i fixed this changing the --chunk-pool-size 2gb and not seeing the errors now
however the new problem is the thanos store is really high in cpu usage

I have one thanos store do i need to run multiple to bring down the cpu use and use min and max time setting on the different stateful sets


make command.DoNothing log?

Maybe make it print something so I know when it's being used?

I could just make it log.Fatalf


Update node version

Node 16 is deprecated
https://github.com/julia-actions/cache/blob/b1b004ffca7da8ece08fe42c9ee0ec4fc2cc5ca5/action.yml#L118
https://github.com/julia-actions/cache/blob/b1b004ffca7da8ece08fe42c9ee0ec4fc2cc5ca5/action.yml#L139
https://github.com/julia-actions/cache/blob/b1b004ffca7da8ece08fe42c9ee0ec4fc2cc5ca5/action.yml#L150
https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/

#107 probably addresses the issue for actions/cache, but pyTooling/Actions/with-post-step seems to be stuck to node16 upstream.

Here's the issue I opened upstream for a new release of pyTooling/Actions that includes the node20 bump: https://github.com/pyTooling/Actions/issues/77

This issue will be fixed by the combination of https://github.com/julia-actions/cache/pull/123 and https://github.com/julia-actions/cache/pull/125.

#123 and #127 have been merged.

This issue has been fixed by the combination of https://github.com/julia-actions/cache/pull/123, https://github.com/julia-actions/cache/pull/127, and https://github.com/julia-actions/cache/releases/tag/v2.0.0.
I've already created the v2.0.0 tag. I'll create the v2 tag shortly.

I've created the v2 tag.


Synchronize/utils angle

This PR is related to Design/angle #73 on the Roboteam_utils branch. It should be merged first before Design/angle #73 is merged.

Looks good but can you please branch from development next time because it is not clear what commits are actually relevant for this PR

I will do it next time...

Wait with merging this PR, somethings don't compile anymore so I will fix them first

Everything should be fixed by now


fix: unit testing suite should test by using the panther_analysis_tool.immutable types

Background
isinstance(thing, list) can be problematic due to panther_analysis_tool.immutable.ImmutableList returning falsey for that isinstance check and local unit tests returning truthy.
This PR updates the global helper unit test cases to use panther_analysis_tool.immutable.ImmutableCaseInsensitiveDict  as a wrapping type for test events.
This PR also updates the underlying global helper functions to typecheck against collections.abc.Sequence or collections.abc.Mapping as necessary.
Note: no detections should need to be updated as a result of this.
This update is expected to be fully backwards compatible, should a dict or list make it into any of the updated python functions.
Truth Table for isinstance(object, type)

object
type
truthy

str
collections.abc.Sequence
true

list
collections.abc.Sequence
true

dict
collections.abc.Sequence
false

ImmutableList
collections.abc.Sequence
true

ImmutableList
collections.abc.Mapping
false

ImmutableList
list
false

ImmutableDict
collections.abc.Sequence
false

ImmutableDict
collections.abc.Mapping
true

ImmutableDict
dict
false

Testing
make test

cc/ @egibs , I updated deep_walk to consider collections.abc.Sequence instead of list in one spot


NPM packaging

Claim an NPM package name. ✅
Create a build to publish to NPM. ✅
Ensure releases work correctly. Decide on tagging and when to release a new version to NPM.
Update installation instructions in README.
Eventually... release a 1.0.0

Currently a release requires a manual bump in package.json, then running npm publish locally.
I feel there should be a better way to do this automatically.

I think the bump should be manual though, so we can decide on the correct semver increase, but yeah the publish should be really easy with github actions.


Error on startup

Hi My Name is Ganesh Kandu
I an Trying to installed RainLoop in my PC
But Getting error
An Error occurred,please refresh the page and try again.
having php 5.5 and data directory is writable recursively

Try the following:

force refresh the browser Ctrl+F5
close and restart the browser
try another bwoser
empty Rainloop's cache folder ./data/_data_7d6917231519a4cf64ff358ceb666d55/_default_/cache

Exact same issue here... Tried all the above steps with no differing results.  Apache logs show nothing amiss.

Hi, did you install RainLoop from GitHub zip archive?

Negative...git cloned :)

It's almost the same thing.
Github version requires additional compilation, so it cannot work by itself.
Work package should be taken here:
http://www.rainloop.net/downloads/

Ah...ok I will give that a go thank you.

Ya that totally worked...thanks so much...continuing on my journey :)

Hi am Getting same error in firefox with v<IP_ADDRESS>5
An Error occurred,
please refresh the page and try again.
but working in chrome without error

Hello guys,
I had the same problem, and the problem was due to a plugin I had installed, the fix was the removal of this plugin, hope it helps


DPS RP API version for AZn+0

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[X] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[X] I commit to follow the Breaking Change Policy of "no breaking changes"
[X] I have reviewed the documentation for the workflow.
[X] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[X] Check this box if any of the following apply to the PR so that label “WaitForARMFeedback” will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[X] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

[X] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

can you expand the lint diff sub title in https://github.com/Azure/azure-rest-api-specs/pull/16538#issuecomment-951411183 and follow the https://github.com/Azure/azure-rest-api-specs/blob/master/documentation/openapi-authoring-automated-guidelines.md#R4009 to fix the new failure introduced by this PR?

can you expand the lint diff sub title in #16538 (comment) and follow the https://github.com/Azure/azure-rest-api-specs/blob/master/documentation/openapi-authoring-automated-guidelines.md#R4009 to fix the new failure introduced by this PR?

These are fixed, but now getting new errors with "tags" and "location" not being allowed, yet they are defined in the properties by using:
"allOf": [
{
"$ref": "#/definitions/Resource"
}
Please advise how to fix.

can you expand the lint diff sub title in #16538 (comment) and follow the https://github.com/Azure/azure-rest-api-specs/blob/master/documentation/openapi-authoring-automated-guidelines.md#R4009 to fix the new failure introduced by this PR?

These are fixed, but now getting new errors with "tags" and "location" not being allowed, yet they are defined in the properties by using: "allOf": [ { "$ref": "#/definitions/Resource" }
Please advise how to fix.

This failure is caused by current limitation of model validation, and new version will fix the issue, suppress the failure.


Skip cleaning docker cache prior to build

This seems to be more trouble than its worth, and much of
the remaining build time (except the push itself). We can
cache the cross-build/golang images between builds - it's
not going to kill us, and it'll save the occasional weird
flake of not finding an image when it tries to rm one of
these.

LGTM barring the one minor nit about a comment.  Can be merged.

Added a comment.


CFF autumn patches - update no 2 - rwfnestimate

A revised version of  rwfnestimate by @cffischer which introduces a new estimation option for correlation orbitals:
 Read subshell radial wavefunctions. Choose one below
     1 -- GRASP92 File
     2 -- Thomas-Fermi
     3 -- Screened Hydrogenic
     4 -- Screened Hydrogenic Core-Correlation

through which one can explicitly increase Z and thus contract correlation orbitals. In many cases (e.g. He 1s2 below) if you go to high n, and don't contract the correlation orbitals, GRASP has all kinds of problems because the overlap of 1s with ns is too small, problems that disappear if you get better initial estimates.
Short explanation by @cffischer (slightly edited from two separate emails):
Typically, when adding a new layer, you read the existing orbitals as initial estimates and then need to deal with the new correlation orbitals. If the new layer has high principal quantum numbers, the estimates need to be contracted.  The option for specifying the screening constant deals with one orbital at a time.  Option 4, increases Z by the specified amount for each orbital.
I have made extensive benchmark tests, one is for He 1s2 1S expansion in the normal form. I remember Jacek working on this decades ago - the code would only go to n = 5. I think Jacek solved the problem be extending the range.  Well, the problem actually was with initial estimated which need to be in the same region as 1s, ie. contracted. Initial estimates can be contracted by reducing the screening, but rather than have negative screening, it seemed better if Z was increased for correlation orbitals. So, option 4 allows the user to increase Z for a group of orbitals (not just one). I have succeeded in going to n = 9 when the generalized occupation number is like 4x10-8.

The option was intended for correlation orbitals but the code does no checking.  So, technically, this option allows the user to change the nuclear charge when generating hydrogenic orbitals for  the group of orbitals generated by option 4.


Shortcut to WindowsClient using correct container ClientUserSettings.config

The created desktop shortcut does not contain the correct path to container-specific ClientUserSettings.config. This may cause problems when a local installation of NAV exists with a different ClientServiceCredentialType settings.
The simple solution is to add a commandline parameter to use the ClientUserSettings.config of the container:
Currently created Desktop Shortcut
"C:\ProgramData\NavContainerHelper\Extensions\nav2016cu3\Program Files\90\RoleTailored Client\Microsoft.Dynamics.Nav.Client.exe"
Solution
"C:\ProgramData\NavContainerHelper\Extensions_{container}\Program Files_{navversion}\RoleTailored Client\Microsoft.Dynamics.Nav.Client.exe" -settings:"C:\ProgramData\NavContainerHelper\Extensions_{container}\Program Files_{navversion}\RoleTailored Client\ClientUserSettings.config"
A problem could be that the whole command line is too large for a desktop shortcut. So the ClientUserSettings.config must be copied to another location. For  e.g. "C:\ProgramData\NavContainerHelper\Extensions_{container}_\config"

This is fixed in the latest version of the containerhelper <IP_ADDRESS>.