feat: add support for intergration build

when build in intergrating, repo and tag need to be as cumstom args from same repo pull request
Log: add support for intergration build

/merge


add storybook skeleton sample

add storybook skeleton sample
The purpose is to select the closest one, copy and paste it when needed, and then make minimal modifications to achieve the target style.

Uploading CleanShot 2024-10-07 at 16.05.41.mp4…

TableCard skeleton example
Link: https://bootstrap-vue.org/docs/components/skeleton


Create ethical_statement.md

First draft.  It is a light rip from LPI, although I do feel enough has changed that we are good.  Additionally, as we add and take away, it will move further away from the source document.

One thing to note here, I was just browsing and didn't realize that Github has a community section: https://github.com/opendatacam/opendatacam/community where a Code of Conduct based on an open license can be proposed.  Thoughts about just using that?

Ok, I put an alternative up.


🐛 Refresh external managed token secret if service account is deleted

cherrypick https://github.com/open-cluster-management-io/ocm/pull/504

Summary
Related issue(s)
Fixes #https://issues.redhat.com/browse/ACM-12018

/test integration

/assign @elgnay @qiujian16

/approve
/lgtm

/cherrypick backplane-2.5


Update documentation

This PR updates documentation for most of the modules in this library.

Looks good, haven't reviewed everything thoroughly yet, but will just merge it in first.


Support integer and boolean types

#4
something like this

Codecov Report

Merging #5 into master will decrease coverage by 4.63%.
The diff coverage is 79.16%.

@@             Coverage Diff              @@
##             master       #5      +/-   ##
============================================
- Coverage      92.3%   87.67%   -4.64%
- Complexity       21       32      +11
============================================
  Files             4        7       +3
  Lines            52       73      +21
============================================
+ Hits             48       64      +16
- Misses            4        9       +5

Impacted Files
Coverage Δ
Complexity Δ

src/ParamConverterManager.php
100% <100%> (ø)
13 <0> (+1)
:arrow_up:

src/BooleanParamConverter.php
62.5% <62.5%> (ø)
4 <4> (?)

src/IntegerParamConverter.php
83.33% <83.33%> (ø)
3 <3> (?)

src/FloatParamConverter.php
83.33% <83.33%> (ø)
3 <3> (?)

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 67d91a3...0023900. Read the comment docs.

have you got further imminent plans? could you tag the release?


Support installing projects from requirements.txt-like file

pip supports installing projects from a requirements.txt file (see https://pip.pypa.io/en/stable/reference/requirements-file-format/). To quickly install multiple repos, it could make sense to support something similar in cmakip, for example support:
cmakip install -r cmake_repos_to_install.txt

where cmake_repos_to_install.txt is:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

We do not have any reason to support the specific format of requirements.txt, so we can also support other formats such as the .yaml  format used by https://github.com/dirk-thomas/vcstool that we already used in the robotology-superbuild's releases, i.e. something like:
cmakip install -r cmake_repos_to_install.yaml

where cmake_repos_to_install.yaml is:
repositories:
  fmt:
    type: git
    url: https://github.com/fmtlib/fmt.git
    version: 8.1.1
  spdlog:
    type: git
    url: https://github.com/gabime/spdlog.git
    version: v1.10.0
  eigen:
    type: git
    url: https://gitlab.com/libeigen/eigen.git
    version: 3.4.0

However, the main advantage of the requirements.txt-like format is that we can include if necessary any additional option (see https://github.com/ami-iit/cmakip/issues/3).


COMP: Modernize searching in list

CMake failure in sanity test is resolved by using
modern list searching paradim.
Use 'if( ${var} IN_LIST MYLIST)'
CMake Error at Wrapping/TypedefMacros.cmake:326 (message):
itk_wrap_class: Invalid option 'EXPLICIT_SPECIALIZATION'.  Possible values
are POINTER, POINTER_WITH_CONST_POINTER, POINTER_WITH_SUPERCLASS,
POINTER_WITH_2_SUPERCLASSES, EXPLICIT_SPECIALIZATION,
POINTER_WITH_EXPLICIT_SPECIALIZATION, ENUM and AUTOPOINTER
Call Stack (most recent call first):
Wrapping/TypedefMacros.cmake:272 (itk_wrap_named_class)
Modules/Core/Common/wrapping/vnl_c_vector.wrap:7 (itk_wrap_class)
Wrapping/TypedefMacros.cmake:196 (include)
Wrapping/TypedefMacros.cmake:150 (itk_load_submodule)
Modules/Core/Common/wrapping/CMakeLists.txt:60 (itk_auto_load_submodules)
PR Checklist

[X] No API changes were made (or the changes have been approved)
[X] No major design changes were made (or the changes have been approved)

vnl_test_hungarian_algorithm (Failed) is a fluke. Merging.


PRR: Add Terraform modules for metrics and alarms

We should set up terraform modules that set up metrics and alarming on all required metrics. This could be done as an extesnion to the existing monitoring module, which contains a dashboard.

Ensure the following:

Alerts include links to a playbook
Metric names and formats follow a standard schema

We have some dashboard before: https://github.com/abcxyz/lumberjack/tree/main/terraform/modules/monitoring


Create a timeline

Add a list of all your activities, achievements, work experience. Add as much info as you can remember. In case you don’t have working experience tell about your pet-projects or student projects. Don’t be shy :)

Added experience block

Merged changes into develop

Merged changes into main


Shutdown buddyworks

@cconstab all repositories are moved to github actions, request you to check buddy.works if we have traffic then please confirm.
TY..


Fix broken links on README

Describe changes
Update broken links on the readme page.
Pre-requisites
Please ensure you have done the following:

[x] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] If I have added an integration, I have updated the integrations table.
[ ] I have added tests to cover my changes.

Types of changes

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

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: schustmi:x: dnthYou have signed the CLA already but the status is still pending? Let us recheck it.

Thank you! Good catch(es)!


ag matches blank lines with pattern '\s*'

at matched the blank line even though the literal q was part of the pattern
This happened on cygwin ( not  significant as it happens on Linux also appended below)
cloned and compiled from source
Minor patch to get it to compile on cygwin ( see below )
This was reduced from a more realistic pattern, but ag should not match and print the blank line, just the line with the q
Tried with a '.*' prefix, ' *' ( zero or more spaces ) and no prefix - those all work
I had started by anchoring to the beginning of the line - ( e.g. '^\s+q' but it's broken in that case also )
$  ( echo "" ; echo q  ) > q && ./ag  '\s*q' q
1:
2:q

$ ./ag --version
ag version 2.2.0

Features:
  +jit +lzma +zlib

expected just one line to print

$ perl -nle 'print if /^\s*q/' q
q

$ grep -P '^\s*q' q
q

$  ( echo "" ; echo q  ) > q && ack  '\s*q' q
q

$ ag --version
ag version 2.1.0

Features:
  +jit +lzma +zlib

$ ack --version
ack 2.22
Running under Perl 5.30.3 at /usr/bin/perl.exe

Copyright 2005-2017 Andy Lester.

This program is free software.  You may modify or distribute it
under the terms of the Artistic License v2.0.

diff --git a/src/main.c b/src/main.c
index e116f70..763cb51 100644
--- a/src/main.c
+++ b/src/main.c
@@ -154,7 +154,7 @@ int main(int argc, char **argv) {
             }
 #if defined(HAVE_PTHREAD_SETAFFINITY_NP) && (defined(USE_CPU_SET) || defined(HAVE_SYS_CPUSET_H))
             if (opts.use_thread_affinity) {
-#if defined(__linux__) || defined(__midipix__)
+#if defined(__CYGWIN__) || defined(__linux__) || defined(__midipix__)
                 cpu_set_t cpu_set;
 #elif __FreeBSD__
                 cpuset_t cpu_set;

dcd@jetson:~$ ag --version
ag version 2.1.0

Features:
  +jit +lzma +zlib
dcd@jetson:~$ ( echo "" ; echo q  ) > q && ag -i '\s*q' q
1:
2:q
dcd@jetson:~$ uname -a
Linux jetson 4.9.140-tegra #1 SMP PREEMPT Wed Mar 13 00:32:22 PDT 2019 aarch64 aarch64 aarch64 GNU/Linux

I face similar problems. A solution to your issue may be to apply a look-ahead before your pattern:
(?=\S+)

I face similar problems. A solution to your issue may be to apply a look-ahead before your pattern:
(?=\S+)


BOT_CALLBACKS_DISABLED

I'm trying to test inline callback data in a group chat however I keep getting this error
Unhandled rejection Error: 400 {"ok":false,"error_code":400,"description":"BOT_CALLBACKS_DISABLED"}
I'm not sure if anyone solved this. But in a normal chat (1 to 1) there isn't this error.

Ok, so I read the official telegram's documentation and it mentioned the explicitly that inline keyboard is only available for one-on-one chats currently.

Warning: Inline keyboards are currently being tested and are only available in one-on-one chats (i.e., user-bot or user-user in the case of inline bots).


Tweets ending in exclamation points are rejected

Entering the command t update "I'm tweeting from the command line!" elicits the response:
-bash: !": event not found
Escaping the exclamation point (i.e. tweeting "I'm tweeting from the command line\!) allows the update to post. However, I think this is an unnecessary burden to place on the user.

This is actually a bash error. Exclamation points are part of bash syntax.
You can fix it by quoting your string with single quotes (which are not interpolated) instead of double quotes, like this:
t update 'I''m tweeting from the command line!'

Note: Since you're using single quotes, you need to escape the apostrophe in I'm by using two single-quotes.


HIGH DATALOSS RISK: Multi Edit overrides field data with its "defaultValue"

Describe the Bug
this is quite a severe issue causing collection fields to reset to a defined "defaultValue" if you use the mass edit function from the UI
I discovered the bug when i selected 20 posts and changed the Status field in the UI. I noticed that the Date field data changed on all documents to the "defaultValue"
{
    name: 'publishDate',
    label: 'Publish Date',
    type: 'date',
    required: true,
    defaultValue: () => new Date().toISOString(),
},

In this case the Mass Edit will override the existing field date value to a fresh new Date set in "defaultValue"
Link to the code that reproduces this issue
https://github.com/yonnic/payload-override-bug
Reproduction Steps

Create a test collection with a field defining a defaultValue besides some other dummy fields.
Generate a few dummy items in the Collection but make sure to not use the value set in "defaultValue"
Mass Edit using the UI on some documents and apply changes to one of the dummy fields.
Watch how the field having "defaultValue" gets reset.

https://github.com/user-attachments/assets/5e1721f1-db12-4916-97ba-f6d49ff54172
Which area(s) are affected? (Select all that apply)
Not sure
Environment Info
Binaries:
  Node: 20.15.1
  npm: 10.7.0
  Yarn: 1.22.22
  pnpm: 9.14.2
Relevant Packages:
  payload: 3.2.1
  next: 15.0.3
  @payloadcms/db-mongodb: 3.2.1
  @payloadcms/email-nodemailer: 3.2.1
  @payloadcms/email-resend: 3.2.1
  @payloadcms/graphql: 3.2.1
  @payloadcms/next/utilities: 3.2.1
  @payloadcms/payload-cloud: 3.2.1
  @payloadcms/plugin-cloud-storage: 3.2.1
  @payloadcms/richtext-lexical: 3.2.1
  @payloadcms/storage-s3: 3.2.1
  @payloadcms/translations: 3.2.1
  @payloadcms/ui/shared: 3.2.1
  react: 19.0.0-rc-02c0e824-20241028
  react-dom: 19.0.0-rc-02c0e824-20241028
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.2.0: Fri Oct 25 20:27:42 PDT 2024; root:xnu-11215.60.400.0.1~11/RELEASE_ARM64_T6000
  Available memory (MB): 65536
  Available CPU cores: 10

Hey @yonnic - thank you for catching this!
I just opened a PR to fix the issue - we'll get a release out for this asap!


WIP: Make Schema Data Displayed in Pattern Lab Dynamic(ish)

Jira
TBD
Summary
POC showing PHP + build tools updates to make sure schema data in PL updates when schema files change.
Details
See todo comments -- at a minimum, we should probably move the new schema watch task out of the PL watch task and into it's own standalone watch task for handling data.
How to test
TBD

This is super promising!
One thing I don't understand is how just adding this in docs.twig updates the data everywhere:
{% set data = getBoltData() %}
{% set schema =<EMAIL_ADDRESS>%}

For example, in button.twig, we have the following.  How does that not just use the initial bolt variable from the twig environment?  (FWIW, I tested and it does work-- I'm just scratching my head as to how it works).
{% set schema =<EMAIL_ADDRESS>%}

PR was released with v2.8.4-canary.bde01a443.0

PR was released with v2.9.0


Working on features section c,d (issue-04)

Creating the features section. Working on features c and d from the google doc.
c: Create Custom Music Rating Album
Make your custom playlist and let your friends rate your music taste!
d: Find Your Music Soulmate
Answer our quiz to see how compatible your music taste is to your friends.

Note: Ill have to change the paths for the images to a git path once they are merged in with the main branch.


Updated winevt.yaml data file

Context: https://github.com/google/timesketch/pull/2910

Added a documentation to the top of the file to explain how it is supposed to be used.
Added the provider_identifier which is optional per our schema.
Changed event_identifier to messag_identifier per our schema.
Added missing references
Updated formatting and fixed some errors

Closed by https://github.com/google/timesketch/pull/2910#discussion_r1366796033


Question: why is the Visitor trait limited to statements, relations & expressions?

What is the reason for that particular design decision versus providing a more general Visitor implementation?
Two options for a generalised Visitor trait come to mind:

expose pre + post trait method variants for every AST node type, or
expose only two trait methods (pre_visit + post_visit) with signatures like fn pre_visit(&mut self, node: &AstNode) -> ControlFlow<Self::Break> - where AstNode is an enum with a wrapper variant for every AST node type found in src/ast/mod.rs and can be matched against.

Would the maintainers be interested in a PR that implements one of the above two approaches?
My preference would be for option 2 because it would not break the trait when node types are added/removed.
Suggested approach:

Define a new RawVisitor trait (and RawVisitorMut trait) like this:

pub trait RawVisitor {
  type Break;
  fn pre_visit(&mut self, node: &AstNode) -> ControlFlow<Self::Break>;
  fn post_visit(&mut self, node: &AstNode) -> ControlFlow<Self::Break>;
}

Define an adapter type (RawVisitorAdapter ?) that accepts a V: Visitor generic argument and implements RawVisitor & RawVisitorMut, which calls the appropriate method on V (or none at all)

struct RawVisitorAdapter<V: Visitor>(v);

impl<V: Visitor> RawVisitor for RawVisitorAdapter<V> {
  type Break = V::Break;

  fn pre_visit(&mut self, node: &AstNode) -> ControlFlow<Self::Break> {
     match node {
        AstNode(Statement) => self.0.pre_visit_statement(...),
        // etc
     }
  }

  fn post_visit(&mut self, node: &AstNode) -> ControlFlow<Self::Break>;
}

Change the Visit derivation macros to generate code in terms of RawVisitor & RawVisitorMut instead of Visitor, like this:

pub trait Visit {
    fn visit_raw<V: RawVisitor>(&self, visitor: &mut V) -> ControlFlow<V::Break>;

    // This has an identical signature to the existing trait, but has a default implementation
    fn visit<V: Visitor>(&self, visitor: &mut V) -> ControlFlow<V::Break> {
       self.visit_raw(RawVisitorAdapter::new(visitor))
    }
}

What is the reason for that particular design decision versus providing a more general Visitor implementation?

The core reasons are  to keep this crate easy to extend with new sql syntax by casual contributors and limited maintenance bandwidth.
The current visitor pattern / macros require a single new #[derive] call
In terms of your proposed implementation, it seems reasonable. I would be interested in knowing how it would work when a contributor added a new node, like https://github.com/sqlparser-rs/sqlparser-rs/pull/897
How would we ensure that these new nodes were added to the AstNode enum? What would happen if we forgot to do so?
perhaps @lovasoa  and @tustvold  have some other perspectives
Basically I think a general purpose rewriter / visitor would be a great addition, as long as we don't make it too hard to add new code to this repo

sqlparser-rs is at the very core of SQLPage, so I can reiterate my proposition: I wouldn't mind being added as a maintainer here :)

Indeed -- I am looking for help maintaining it for sure. I think you can do all the time consuming parts of maintenance (PR reviews, answering questions / tickets, etc) without having write access to the repository.
I am waiting for someone to actually show the initiative to do this work (there are plenty of people willing to write code).
I had a promising candidate in @AugustoFKL  (see https://github.com/sqlparser-rs/sqlparser-rs/issues/808) but sadly there were some circumstances that required them to stop working here
I will write up a discussion explaining the current state of affairs

In terms of your proposed implementation, it seems reasonable. I would be interested in knowing how it would work when a contributor added a new node, like https://github.com/sqlparser-rs/sqlparser-rs/pull/897
How would we ensure that these new nodes were added to the AstNode enum? What would happen if we forgot to do so?

That's a great question. Assuming the parent node of the new node has a derived Visitor instance then compilation would fail  due to the derived code not being able to find a matching AstNode variant, which is not ideal.
Ideally, the AstNode enum would be generated automatically by walking the types starting with sqlparser::ast::Statement but that would require some deep macro voodoo.

You don't need to create a huge enum. You can use the built in Any trait. Have a look at my PR ;)

@lovasoa depends on if you want to match on it. I'll take a look at you PR though.

FWIW https://github.com/sqlparser-rs/sqlparser-rs/pull/951 added visiting TableFactor as well

Update: I've been experimenting with various implementation strategies to generalise the AST visitor. Nothing to ready to show yet, but this is business critical for my company so it's a high priority to figure out something that works well.
I'll update this issue with a link to a draft PR hopefully in a matter of days.

Progress update - I have a working generalised visitor implementation. I'll put up a PR later this week when I've done some more testing.

Is this still happening? Generalised visitor implementation would be appreciated.

@osaton @alamb yes this is still happening. Apologies for the lack of comms.
TL;DR I ended up taking quite a different approach to what I originally planned, due to our (the company I work for) evolving needs.
The comprehensive Visitor implementation will be initially released as its own crate.
Summary of features so far:

A Visitor implementation is notified of every type in the sqlparser AST (200+ types when you take into account the Vec, Box and Option combinations, plus primitives).
The Visitor trait itself is generic over the AST node type of interest (there aren't 200+ trait methods - in fact there are just two: enter and exit).
The AST traversal is performed in an optimal order for semantic analysis workloads (instead of the order of AST fields in the source). Specifically, AST nodes that can refer to other AST nodes are visited after the AST node that introduces the referent - e.g. a FROM clause is visited before the a projection that refers to columns in the tables introduced by the FROM clause. This cuts down on the number of passes required for semantic analysis workloads.

In order to pull that off, I needed to write a build.rs script to analyse sqlparser's sources because hand writing AST traversal for all of the AST types would have been a lot of work.
I need to write up some docs but I would love some feedback on the code before I publicly publish the repo.
Would you both be keen on taking a look later this week?

Three features that I really wanted from sqlparser while writing the enhanced Visitor code:

Optional feature to have a unique ID baked into all AST nodes

It's possible for multiple AST nodes at different places in the tree that have the same type to have the same hash and compare as equal. This seems counter intuitive, but two syntactically identical nodes can be different semantically.
Not having robust (and cheap) means of uniquely identifying a node makes building HashMaps of derived metadata keyed by node particularly tricky.

Optional feature to have span information baked into all AST nodes

This would be super useful for debugging and reporting errors nicely (like miette does).

Type per enum variant (no fields) everywhere

It would be nice to not have to match an enum in order to pluck out a variant. Instead I'd like be able to implement Visit<InsertStatement>.
1 & 2 could be solved by wrapping every struct field or enum variant field in a Node<T> type that Derefs to T but also contains a unique ID and span info. Because of the Deref it might be possible to do this without breaking backwards compatibility but I haven't actually tried it.

@freshtonic Your visitor crate sounds perfect for my use case. I would love to try it but I'm not sure if I'm able to give any constructive criticism about the code as I'm fairly new to Rust and systems programming languages in general.

Optional feature to have a unique ID baked into all AST nodes

It's possible for multiple AST nodes at different places in the tree that have the same type to have the same hash and compare as equal. This seems counter intuitive, but two syntactically identical nodes can be different semantically.
Not having robust (and cheap) means of uniquely identifying a node makes building HashMaps of derived metadata keyed by node particularly tricky.

Optional feature to have span information baked into all AST nodes

This would be super useful for debugging and reporting errors nicely (like miette does).

Type per enum variant (for Statement and Expr at least, maybe some additional other types)

I don't know if this can be done without breaking changes, but having both 1 and 2 would be amazing.


Azure function app caching issue with key vault reference

My Application settings of Azure function app, has keyvault reference like @Microsoft.KeyVault(SecretUri=https://myvalut.vault.azure.net/secrets/mySecret/), whenever new version of "mySecret" introduced in keyvault, Azure function still renders the old/stale value not the latest value/version of "mySecret".
If I open up app setting using KUDU (https://myhttpfunc.scm.azurewebsites.net/api/settings) I can see "mySecret":"onemoretry" where "onemoretry" is the old value. Only Azure func app restart updates "mySecret" with new value.
How to make Azure function which uses keyvault reference to fetch latest value/version of the targeted keyvault secret as & when it get updated, without Azure function restart?
Can you please clarify whether the value returned would be cached on the Azure function app or if it would incur a request to KeyVault every time that App Setting was queried by the code?
If function app needs to be restarted everytime after keyvault secret vault update then what is the purpose of the below keyvault reference support without version number?
@Microsoft.KeyVault(SecretUri=https://myvalut.vault.azure.net/secrets/mySecret/),

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

ID: 7feaa3d0-7233-a3cb-cb9b-a9a55b1f0d7a
Version Independent ID: f41f9d51-52f8-1f45-1043-1344a3b74458
Content: Use Key Vault references - Azure App Service
Content Source: articles/app-service/app-service-key-vault-references.md
Service: app-service
GitHub Login: @mattchenderson
Microsoft Alias: mahender

Some quick update would be appreciated.

The scope for these doc issues is to help identify gaps and issues with the documentation. Is there something in any specific Azure doc you are looking to have updated or are having issues with?
If yes, please provide us with the link to the documentation you are referring to so we can better assist.
Else, if you are looking for help with debugging issues I would suggest reaching out to the MSDN and Stack Overflow communities. Our team will help you there.

It is not about the document it more about the functionality of app services as I have mentioned in my original post. Can you move this concern or tag right team to answer/clarify the query?

@TestUser0811 I believe this is the current intended behavior. The secret is fetched when the function first warms up and if the function were to scale down to zero, it will pick the latest secret at the time of warming up again.
@mattchenderson Could you please confirm and share more insights here?
We are assigning this issue to the content author for further review and to update the docs accordingly.

@PramodValavala-MSFT "The secret is fetched when the function first warms up and if the function were to scale down to zero" this statement of yours is not true. Only function app restart is fetching the latest secret & it is painful to restart function app every time you update the keyvault secret version & it is definite caveat Microsoft has to patch out.
Even tried out updating the function app's application settings with the newly version of keyvault secret by using the REST API & the application settings value get updated as expected but still function is rendering the previous value of the keyvault secret not the latest value. Function App considering the latest version of the secret only after its restart.
Help me with the possible solution where function can able to pick up the latest value of key vault secret version with out Function App restart.
Format of Keyvault reference configured Function App's application setting, @Microsoft.KeyVault(SecretUri=https://myvalut.vault.azure.net/secrets/mySecret/),

some update would be appreciated.

Does restarting the function app pick up the latest value? It didn't seem to work for me. What I had to do is to make a minor update to the url. Actually removed the "/" at the end and saved it. Then it picked up the latest.

We are facing this as well. Tried restarting the function app, removed the "/" from key vault url, but the function app picks up the old secret value.

This really needs to be fixed - a restart should clear any cache being used!

Use the "SecretVersion" in your configuration reference.
@Microsoft.KeyVault(VaultName=myvault;SecretName=mysecret;SecretVersion=ec96f02080254f109c51a1f14cdb1931)
Use Key Vault reference

Use the "SecretVersion" in your configuration reference.
@Microsoft.KeyVault(VaultName=myvault;SecretName=mysecret;SecretVersion=ec96f02080254f109c51a1f14cdb1931)
Use Key Vault reference

That would mean updating configuration when keyvault value has a new version added, which is not viable or acceptable in most cases.

Is there any update on this obvious problem? It really needs to be resolved - restarting and stopping and then starting the function app has no effect on the function app seeing the new KV value.

Restarting my FA didn't pick up the latest KV value :(

I am also facing the same issue. Was there any resolution around this?

I see an issue where the function app is caching the original application setting value from the KV despite the following scenarios:

The KV value was updated with a new version, and the new version was explicitly referenced in the application settings value.
The application settings value was updated directly without using the KV.
The application setting was removed (the function app still somehow picked up the original value).
A new application setting with the same name was added with a new value not using KV.

Same issue. Refreshing the app-service doesn't fetch newest value.
I need to make a change in the config of the app service and save that. It will ask for a refresh and that will trigger it.

@PramodValavala-MSFT @Karishma-Tiwari-MSFT @mattchenderson Also having the same issue with AppServices, restarting isn't enough to get the most recent secret value. I can even disable all older versions in my keyvault and it still uses the old version. Because of this I'm fairly certain that this is a caching issue.
After a certain time and restarting it just works. I guess this happens when the cache TTL is finally reached.

Any update on this issue? Function restart is not picking the latest version of the KeyVault secrets, only configuration change refreshes the latest version of the KeyVault secrets. Its high maintenance to continue with workaround if secret is referenced in multiple functions/app services.

My solution for now is to specify ;SecretVersion=... in the config, but this is a mayor pain point as you need to update this everytime you update your secret

I have the same issue. This "cache" persists even through multiple app restarts and code redeployments.
Using a SecretVersion is not a solution but a workaround and it means I have to write even more automation to handle this.

same here.
in our case, the cache can live up to 5 hours and even we restart the function app and it still cannot flush the cache.

This madness caused us a 6-hour P1 recently.

This is burning me too and I say that this is nothing more than pure poop! MSFT, can you please fix this?

I am also suffering on this. Function (v4 isolated) is still seeing the old value even though the function is restarted. Pls fix this!

Same here with Function App v4 (P1V3). Looking forward on getting this fixed to save hours of troubleshooting in the future 😅

+1 for this issue to be fixed - should pick up latest version by default

+1

We would also appreciate a fix for this. A restart should not use the cached value

Same problem here. Please fix it.

Adding on to the pile, here. At minimum, a function app restart or code redeployment should cause a cache refresh. With a properly set up CI/CD, it's a mere button click to restart/redeploy to pick up new value, and I don't mind that.

So I dug around the Googles more, and I found documentation about using key vault references and it says that key vault references are refreshed every 24 hours. https://learn.microsoft.com/en-us/azure/app-service/app-service-key-vault-references?tabs=azure-cli#rotation. Or the alternative approach as mentioned here, is to do a force config update.
IMO, that still doesn't cut it. You can plan your key/secret rotations to avoid your key/secret from expiring and causing production downtime, but where you have emergency rotations such as compromised keys/secrets, you still require a forced update. Can't simply be down for a day until the secret/key refreshes itself.

Just having a button to trigger a refresh makes a lot of sense to me, especially since the cache updates every 24 hours anyway. There shouldn't be a need for downtime to force an update.
It would make key rotation so much smoother - currently my catch-all approach is to just redeploy the relevant apps.

Any updates on this one? Not the slickest of password rotation methods currently!

Any updates? This completely ruins the use of password rotation

Same issue here. Please put this on your roadmap.

+1

As referenced by @bcline760, it seems the secrets get rotated every 24 hours by default unless an appsetting change is made and saved. As part of my pipelines I've started using az webapp config appsettings set ... --settings DummyTimestamp=$([datetime]::UtcNow.ToString("s")) to trigger a key vault update

The 24-hour cache and a force-update-through-restart behavior has since been added to the article already. There is a lot of feedback related to the feature itself that should be best submitted with https://feedback.azure.com/.
For any content feedback, please feel to continue to use this GitHub channel. Thank you. #please-close

We really need a solution for this - we are rotating a system credential which is stored in key vault (by an ops team). This credential is then read by an app service using a key vault reference. We need the app service to read the updated credential otherwise our api will stop working. This causes us P1 issues - Please fix!


[Feature-request] Can generate custom poller/polling methods

Got this feedback while writing custom poller and polling methods in DocumentIntelligence SDK: https://github.com/Azure/azure-sdk-for-python/pull/37197#discussion_r1744627534
Expected:
The generator can generate customer poller/polling methods.

Thanks for feedback.
Standard LRO polling only has several patterns which is integrated into azure-core, while custom LRO polling may have unlimited possibilities, so it is a little hard to generate for custom poller/polling. We will collect more feedbacks and see if codegen could do something for better usage experience about customization.

@kristapratico I think it falls into your current investigation on patching


Request: Demo of an EditorPlugin

I have been trying to figure out how to create an editorplugin with UI.  It would be great if someone could provide a very barebones example, perhaps similar to the "Custom Dock" demo that is part of the "Godot Demo Projects" repository, but implemented in GDNative (preferrably with C++.)  If an example exists anywhere for this, I haven't been able to find it.

Hello, if nobody is doing this, may I do It?

Hello, if nobody is doing this, may I do It?

Sure, go ahead :slightly_smiling_face:


SpellSoundPlay EndSpellCast crash

My PC had Bane on him, so when I wen to next map and tried to rest crash went off.
See last log message in the pic.

I think I fixed this issue recently.
It was due to the Jammed Spell garbage collection, which had an issue with invalid caster handle when the caster wasn't in the party. It called SpellEnd, triggers the EndSpellCast event and tries to play the end spell sound on the caster, which is no longer valid.
Can you confirm it's closed?
Also, just to verify, you were running a dev build, right?

Thanks!
Cannot confirm as I lost the save. But looked at the code fix, should be covered.


Simple Fix for 4.8

In SQLite.h you need to add #include "sqlite3.h" or the project won't build.
// Fill out your copyright notice in the Description page of Project Settings.
#pragma once

#include "Engine.h"
#include "sqlite3.h"

It has been fixed in my repo https://github.com/KhArtNJava/SQLite3UE4 with commit https://github.com/KhArtNJava/SQLite3UE4/commit/7bf8703eeafd036aaf3ea6dcfd542a6d705443bc ...

Hello.
New fixes in my fork https://github.com/KhArtNJava/SQLite3UE4 :

Fixed crash in packaged project (Found and fixed bug - Yep, I did it!!!).
A lot of new BPs.


2D Visco benchmark fix

Fix a typo in the 2d viscoelastic benchmark equations. Update the preset models and viscoelastic_example.py accordingly.

Codecov Report

Merging #918 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master     #918   +/-   ##
=======================================
  Coverage   90.06%   90.06%
=======================================
  Files         148      148
  Lines       19737    19737
  Branches     3060     3060
=======================================
  Hits        17777    17777
  Misses       1596     1596
  Partials      364      364

Impacted Files
Coverage Δ

examples/seismic/model.py
41.91% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

merged.


Web: Removing WiFi-APs ruins whole config

Hi, when you use the Web-Interface to remove all WiFi-APs and write the config, the configuration file gets corrupted and the Web-Interface is no longer usable (Error: "Failed to load configuration").
I think the error could be here (when the number is zero):
https://github.com/richonguzman/LoRa_APRS_iGate/blob/main/src/web_utils.cpp#L62

Hello. When you get "Failed to load configuration" can you go to http://YOUR_LORA_IP/configuration.json and send the config? Of course please remove your passwords first! You can send it here in the issue or to my e-mail<EMAIL_ADDRESS>

Ok, this problem will be fixed in next update. If you want, you can go to this repo and test it now, release is available: https://github.com/SQ2CPA/LoRa_APRS_iGate

Fixed in https://github.com/richonguzman/LoRa_APRS_iGate/pull/56

I´m a little late, but i have tested it now.
The fix works. Thank you very much!


Display current python version when in a conda environment

Is your feature request related to a problem? Please describe.
Currently, the conda section of the prompt displays the name of the currently selected conda environment, which is great, but doesn't display the python version of that conda environment.
Describe the solution you'd like
I would suggest that conda/pyenv/virtualenv/venv etc be merged to just display the current python version in the prompt.
Describe alternatives you've considered
A python version field in the conda section — which specifically asks conda info for the current python version — could also work, but would be a lot of duplication of effort.
Documentation, adoption
There could be a flag to disable this behavior.

Thanks @avarun42,  This is merged to v4 branch with #431. Hope we could get back to work on that release asap.


Composer view is static and has no backend link capabilities

The composer window has no capability to authenticate users first and shows up as a blank window with no real function.
Eventually it should show a login screen until a member of the club enters their username/password. If they succeed at this, it should give them write access to their blog.

Fixed by 5dbdae7dc80d11cd9841f0edf9decd266305262f


"READONLY You can't write against a read only replica" after restart redis docker containers with ansible playbook

Hello. I use spring data redis starter and I have a problem with RedisSentinelConfiguration after failover due execute ansible playbook.
My microservice doesn't see master change after failover.
I have 3 replicas and 3 sentinels for each on the same hosts. In other words host1 with two ports, one for redis, another for sentinel and etc. (example, host1:6379,host1:26379; host2:6379,host2:26379; host3:6379,host3:26379)
When I execute the command "DEBUG SEGFAULT" or "DEBUG SLEEP 80" (for switch master testing), master change it role on slave and master switches, microservice track changes and take new master.
But when I run ansible playbook which contains follow tasks: stop redis container, stop sentinel container, some actions for configuration of redis and then start redis container, start redis sentinel container
Then problem is occur: io.lettuce.core.RedisReadOnlyException: READONLY You can't write against a read only replica
The main problem is MasterReplicaConnectionProvider.getConnectionAsync(WRITE) take old master for write operation. How to enforce MasterReplicaConnectionProvider update their knowNodes after full connectivity outage?
After restart of microservice the problem withdraws itself.
My config in redis starter below (Spring, Kotlin):
@Bean
fun lettuceClientOptionsBuilderCustomizer(): LettuceClientConfigurationBuilderCustomizer {
    return LettuceClientConfigurationBuilderCustomizer { builder ->
    	builder.readFrom(ReadFrom.REPLICA_PREFERRED) //enables SentinelConnector for MasterReplica API
            .clientOptions(ClientOptions.builder()
                .protocolVersion(ProtocolVersion.RESP3)
                .publishOnScheduler(true)
                .build())
            .useSsl()
            .disablePeerVerification()
    }
}

@Bean
fun redisSentinelConfiguration(properties: RedisProperties): RedisSentinelConfiguration {
    return RedisSentinelConfiguration(
        properties.sentinel!!.master ?: properties.defaults.sentinelMaster, //mymaster
        properties.sentinel.nodes //sentinelHost1:26379,sentinelHost2:26379,sentinelHost3:26379
    )
}

I tried to change configuration, but nothing help.

autoReconnect(true) for ClientOptions
validateConnection() for LettuceConnectionFactory

Help please. Any suggests will in help.

UPDATE: I disabled autoReconnect and enabled validateConnection, RedisReadOnlyException doesn't appears, but connection is lost. When I send request to microservice, it's trying to get connection with redis and hangs for a long time until it breaks on timeout.
Last message in my logs is: io.lettuce.core.masterreplica.MasterReplicaConnectionProvider.getConnectionAsync(READ)


Running the script just does nothing

I'm on mac, and maybe I just installed the chrome thing wrong? I put it in the file and ran command -v chrome and nothing happened, and then I ran the script and nothing happened.

Hi @MagnusStrom, so you tried try this?
4. If you are on MacOS, please add Chrome alias in ~/.bashrc or ~/.zshrc or other shell rc file:

alias chrome="/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome"

Restart terminal app and then run command -v chrome?

Running the second command worked, but the first one did not.

@KevCui And yes, I have tried that. I did:
nano ~./bashrc
and got this https://i.imgur.com/kaTprf3.png

Hi @MagnusStrom, you edited ~/.bashrc, not ~./bashrc, right? I think it's a typo in your previous comment.
Since Apple changed default shell to Zsh. By any chance, you are not using Bash? You can check you current shell with this command echo $SHELL. If it's Zsh, you have to add alias into ~/.zshrc.

Hello @KevCui, yes turns out i needed to edit zshrc. And running command -v chrome now gives me:
https://i.imgur.com/3r01CTh.png
But still running ./soap2day-dl.sh -n 'game of'
gives me nothing!

Hi @MagnusStrom, one step closer :) Could you run bash -x ./soap2day-dl.sh -n 'game of' and share the log? Thanks.

Wait, I think I did install jq incorrectly, i have to install it through homebrew

Update: Now it returns this.

Hi @MagnusStrom, it's weird the chrome path is not recognized during script execution. I hard-coded it in the latest commit. It should work for you now.

it worked!! thank you!!


Add ability to report issue (provide feedback) on general pages

It would be good to be able to provide generic feedback on the home / about and search results pages.
See search results - no 'Was this page helpful ' is shown.

Currently, the logic for storing feedback is implemented in the serve() method of the ContentPage by listening for POST requests. To enable this feature for every page type, I would prefer to move the feedback logic to a separate endpoint.
When saving feedback, a foreign key to a wagtail page is required. This will not be possible on the search result page as this is not implemented as a wagtail page. @laymonage do you have any preference on how this should be approached? I would address this by changing the feedback model to allow null values for this foreign key and additionally store the requested URL in a URLField.

I’ve added a feedback link within the footer which will hopefully be enough.


crush in CRYPTO_THREAD_write_lick

Describe the bug
*** Aborted at<PHONE_NUMBER> (unix time) try "date -d @1693468522" if you are using GNU date ***
PC: @                0x0 (unknown)
*** SIGSEGV (@0x18) received by PID 30278 (TID 0x7f9e0a261080) from PID 24; stack trace: ***
    @     0x7f9e0bd8b425 google::(anonymous namespace)::FailureSignalHandler()
    @     0x7f9e0e92d3bf (unknown)
    @     0x7f9e0e926d46 __GI___pthread_rwlock_wrlock
    @     0x7f9e0b04da2c CRYPTO_THREAD_write_lock
    @     0x7f9e0afbf35e ENGINE_add
    @     0x7f9e0f7ef251 s2n_rand_init
    @     0x7f9e0f7ebc25 s2n_init
    @     0x7f9e0f78748a aws_tls_init_static_state
    @     0x7f9e0f77a476 aws_io_library_init
    @     0x7f9e0f6f8644 aws_mqtt_library_init
    @     0x7f9e0f6d2d63 Aws::Crt::ApiHandle::ApiHandle()
    @     0x7f9e0f66ead4 Aws::New<>()
    @     0x7f9e0f66e703 Aws::InitializeCrt()
    @     0x7f9e0f66a7eb Aws::InitAPI()
    @     0x7f9e1295c5fe shiva::tabletserver::TabletServer::Start()
    @     0x562f8d557651 shiva::minicluster::MockTabletServer::StartNode()
    @     0x562f8d53fde3 main
    @     0x7f9e0b1fa0b2 __libc_start_main
    @     0x562f8d51d15d _start

Expected Behavior
when i call initApi, my process crash. i need help how can i resolve it .I'm not sure if it's related to what's mentioned below.
/usr/bin/ld: warning: libkrb5.so.26, needed by /lib/x86_64-linux-gnu/libgssapi.so.3, may conflict with libkrb5.so.3
Current Behavior
crash
Reproduction Steps
call initApi
Possible Solution
No response
Additional Information/Context
No response
AWS CPP SDK version used
develop
Compiler and Version used
gcc (Ubuntu 8.4.0-3ubuntu2) 8.4.0
Operating System and version
20.04.1-Ubuntu

How are you compiling and using this sdk? The basic use of this sdk should look something like this and shouldn't crash when you call initApi
#include <aws/core/Aws.h>
int main(int argc, char** argv)
{
   Aws::SDKOptions options;
   Aws::InitAPI(options);
   {
      // make your SDK calls here.
   }
   Aws::ShutdownAPI(options);
   return 0;
}


Add default value to options

Would be nice to have the default value for each option, except of course rulesor globals

No.


Add V3 keystone support, expose configuration options for domain and project

This was based on @imduffy15 s work and rebased against the 2.8 version of the plugin.

I will have to look at this in more detail. It is necessary to ensure this works with both versions of keystone and users will understand how to configure that correctly in both cases.
I do not like how the method signatures are bloating so I consider introducing a wrapper object for login details.

I agree 100% we should make sure this works on both versions. A wrapper object seems like a way to go. Is there a way for us to automatically test the wrapper?

I am running ATH that exercises Keystone v2. One way would be to ask someone like you, who have an access to keystone v3 instance, to run it against their instance and report problems.
An alternative would be to resurrect #85 and create integration tests that interact with openstack in docker container which would hopefully give as the flexibility to choose component versions.

I have access to an Openstack instance running v2 and v3 endpoints, and I've had a go at running the plugin with the V3 changes from this pull request merged in.
The good news is that it will authenticate and then allows VM provisions to take place, but using the client = OSFactory.builderV3()... code doesn't allow for fallback to V2 authentication when a v2 API endpoint is used.
I don't know the best way to choose between the two builder methods - but falling back by catching the exception does at least functionally work as per the change in PR #83 (although I think maybe the exception message could be a little confusing if they both fail). Perhaps we could switch on the URL if we could guarantee that the strings v2 and v3 will occur in the API endpoint URL?

Thanks for your input @fraz3alpha
We already had a URL deployed as far as I know without "v3" in the URL.
I think we should go with a simple dropdown letting you choose whether it's a v3 or v2 the plugin should run against? This way its explicit and should only be very little prone to errors and implicit behaviour. I think I could manage plugging this in. The builder code from #83 for v2 works as is for you? I think I could manage to plug the dropdown and both builders based on it together if we can all agree this is the way to go.

Is there a way for us to automatically test the wrapper?

I am working on a credentials wrapper and its AJAX passing to Descriptor method without so much magic. I will have something to build on hopefully soon.

What is the relation between auth field for v2 (endPointUrl, identity, credential, zone?) vs. v3(???)? Is v3 a superset of v2? IIUC project and domain are new, region is just renamed zone, right?

@LarsFronius : There was a couple of different variables used in your version vs. the other pull request, so they don't match up 1:1, but for reference I have been using this in my testing:
+        // Try version 2
+        try {
+            LOGGER.fine("Attempting to use V2 API endpoint");
+            return  OSFactory.builder().endpoint(endPointUrl)
+                    .credentials(identity, credential.getPlainText())
+                    .tenantName(project)
+                    .authenticate()
+                    .useRegion(region);
+        } catch (ClientResponseException e) {
+            // Failing that, try version 3
+            LOGGER.fine("Attempting to use V3 API endpoint");
+            return OSFactory.builderV3().endpoint(endPointUrl)
+                    .credentials(identity, credential.getPlainText(), Identifier.byName(domain))
+                    .scopeToProject(Identifier.byName(project), Identifier.byName(domain))
+                    .authenticate()
+                    .useRegion(region);
+        }

It also includes an extra domain parameter to credentials in the V3 version over what you had originally - I need to go back and check and see if that's actually required if you include the domain in the scopeToProject() call
Regarding how to differentiate between V2 and V3, I like your idea for a switchable set of parameters to make it explicit. Also, I see from v3.0.0 of openstack4j that they appear to have made some breaking changes that mean we may have to split out the V2 and V3 clients differently anyway if/when this plugin moves up to that version: http://www.openstack4j.com/learn/getting-started/#authenticate

Hi! I've tested this on our v3 instance, works well. I had to add a region parameter to the plugin configuration, but this might be caused by the fact that I was using VERY old version previously, which didn't require region. Could you please let me know, what is required to merge this? Explicit distinction of v2 and v3 via drop-down option?

The problem is this breaks v2 support. Or at least was last time I checked.

Implemented in #133.


DEPS.xwalk: Roll blink-crosswalk (2a0323e -> 6e19c2e).

6e19c2e Merge pull request #52 from rakuco/revert-faulty-revert
d00a85f Revert "Revert "Merge 192508 "Focus a page only if the page is different from cu..."""

This roll is to revert a reverted upstream commit that was not supposed
to be pushed to blink-crosswalk (it was reverted temporarily while we
were debugging XWALK-3863).

@darktears @kenchris


Chart 0.8.2 - YAML parse error on crowdsec/templates/lapi-deployment.yaml

When upgrading my chart to 0.8.2, I get the following error:
helm upgrade failed: YAML parse error on crowdsec/templates/lapi-deployment.yaml:
error converting YAML to JSON:
yaml: line 59: mapping values are not allowed in this context

the relevant lapi section of my values.yaml:
    repository: crowdsecurity/crowdsec
    tag: "latest"

  lapi:
    env:
      - name: DISABLE_AGENT
        value: "true"
      - name: ENROLL_KEY
        valueFrom:
          secretKeyRef:
            name: crowdsec-secret
            key: ENROLL_KEY
      - name: ENROLL_INSTANCE_NAME
        value: "k8s_cluster"

    dashboard:
      enabled: false
      ingress:
        enabled: false

    resources:
      requests:
        cpu: 150m
        memory: 100M
      limits:
        memory: 100M

    # -- Enable persistent volumes
    persistentVolume:
      # -- Persistent volume for data folder. Stores e.g. registered bouncer api keys
      data:
        enabled: true
        accessModes:
          - ReadWriteOnce
        storageClassName: "ceph-fs"
        size: 1Gi
      # -- Persistent volume for config folder. Stores e.g. online api credentials
      config:
        enabled: true
        accessModes:
          - ReadWriteOnce
        storageClassName: "ceph-fs"
        size: 100Mi

Hi @ahgraber,
Could you please paste all the values content so we can try to reproduce the error.

# -- for raw logs format: json or cri (docker|containerd)
container_runtime: containerd

image:
  # -- docker image repository name
  repository: crowdsecurity/crowdsec
  # -- pullPolicy
  pullPolicy: IfNotPresent
  # -- docker image tag
  tag: "latest"

# # If you want to specify secrets that will be used for all your crowdsec-agents
# # secrets can be provided be env variables
# secrets:
#   # -- agent username (default is generated randomly)
#   username: ""
#   # -- agent password (default is generated randomly)
#   password: ""

# lapi (local api) will deploy pod with crowdsec lapi and dashboard as deployment
lapi:
  env:
    # by default disable the agent for local API pods
    - name: DISABLE_AGENT
      value: "true"
    - name: ENROLL_KEY
      valueFrom:
        secretKeyRef:
          name: crowdsec-secret
          key: ENROLL_KEY
    - name: ENROLL_INSTANCE_NAME
      value: "k8s_cluster"
    # - name: ENROLL_TAGS
    #   value: "k8s linux test"
    # # If it's a test, we don't want to share signals with CrowdSec so disable the Online API.
    # - name: DISABLE_ONLINE_API
    #   value: "true"
  dashboard:
    # -- Enable Metabase Dashboard (by default disabled)
    enabled: false
    ingress:
      enabled: false

  resources:
    requests:
      cpu: 150m
      memory: 100M
    limits:
      memory: 100M

  # -- Enable persistent volumes
  persistentVolume:
    # -- Persistent volume for data folder. Stores e.g. registered bouncer api keys
    data:
      enabled: true
      accessModes:
        - ReadWriteOnce
      storageClassName: "ceph-fs"
      size: 1Gi
    # -- Persistent volume for config folder. Stores e.g. online api credentials
    config:
      enabled: true
      accessModes:
        - ReadWriteOnce
      storageClassName: "ceph-fs"
      size: 100Mi

  nodeSelector:
    node-role.kubernetes.io/master: "true"
  tolerations:
    - key: "node-role.kubernetes.io/master"
      operator: "Exists"

  # -- Enable service monitoring (exposes "metrics" port "6060" for Prometheus)
  metrics:
    enabled: true
    serviceMonitor:
      enabled: true

# agent will deploy pod on every node as daemonSet to read wanted pods logs
agent:
  acquisition:
    # -- Specify each pod you want to process it logs (namespace, podName and program)
    - namespace: networking
      podName: traefik-*
      program: traefik
    # - namespace: security
    #   podName: keycloak-postgresql-*
    #   program: pgsql
  resources:
    limits:
      memory: 100Mi
    requests:
      cpu: 150m
      memory: 100Mi
  # -- Enable persistent volumes
  persistentVolume:
    # -- Persistent volume for config folder. Stores local config (parsers, scenarios etc.)
    config:
      enabled: true
      accessModes:
        - ReadWriteMany
      storageClassName: "ceph-fs"
      size: 100Mi
  # -- environment variables from crowdsecurity/crowdsec docker image
  env:
    # As we are running Traefik, we want to install the Traefik collection
    - name: COLLECTIONS
      value: "crowdsecurity/linux"
    - name: COLLECTIONS
      value: "crowdsecurity/traefik"
    - name: COLLECTIONS
      value: "crowdsecurity/base-http-scenarios"
    - name: COLLECTIONS
      value: "crowdsecurity/http-cve"
    - name: COLLECTIONS
      value: "crowdsecurity/mariadb"
    - name: COLLECTIONS
      value: "crowdsecurity/pgsql"
    - name: COLLECTIONS
      value: "crowdsecurity/sshd"

    - name: PARSERS
      value: "crowdsecurity/cri-logs"

    - name: TZ
      value: "${TIMEZONE}"
    - name: DISABLE_ONLINE_API
      value: "false"
    # - name: LEVEL_TRACE
    #   value: "false"
    # - name: LEVEL_DEBUG
    #   value: "false"
    # - name: LEVEL_INFO
    #   value: "false"

  # -- tolerations for agent
  tolerations:
    - key: "node-role.kubernetes.io/master"
      operator: "Exists"

  # -- Enable service monitoring (exposes "metrics" port "6060" for Prometheus)
  metrics:
    enabled: true
    serviceMonitor:
      enabled: true

the deployment uses fluxcd for gitops and the repo is public, you can see everything attached to the deployment here

Hi @ahgraber,
Thanks for the reply. It's fixed in this PR: https://github.com/crowdsecurity/helm-charts/pull/77
It will be available on the next release.

Is there an eta for the release @he2ss ? Any other items going into the release that are left undone? Inquiring minds are interested in the fix. Thanks!

Hi,
Yep, there was also https://github.com/crowdsecurity/helm-charts/pull/78/files
The release 0.8.3 is done


Download speed drop by 1/3 after 1.4.25

Prior to this update I get around ~150MiB but only get ~50MiB now. I've tried to download the same file multiple times. I think it has to do with the removal of bg bots (https://github.com/tgdrive/teldrive/commit/a1440b1d7a06b2f2d8e135b14ffe3bc75ed18b52).

@vavtnen Enable multi threaded streams  add
``[tg.stream]
multi-threads=8
stream-buffers=16```  in config file and use stream endpoint (replace downlaod with stream in download link) to download files at higher speeds.

Here is what I have for config.toml
[tg.stream]
multi-threads = 16
buffers = 30
bots-limit = 48
stream-buffers=32
rclone config is using stream
This is the download speed from the latest version using aria2c -x 16 -s 16
09/19 08:04:56 [NOTICE] Downloading 1 item(s)
[#622a6f 1.9GiB/23GiB(8%) CN:16 DL:53MiB ETA:6m57s]
This is the download speed from version 1.4.20 using aria2c -x 16 -s 16
09/19 08:11:56 [NOTICE] Downloading 1 item(s)
[#3dd258 2.1GiB/23GiB(8%) CN:16 DL:163MiB ETA:2m16s]
Both version use the same configs, but download speed is much slower with the latest version.

@vavtnen From 1.4.22 rate limit is added in downloads you can disable it in config in earlier version you were downloading without rate limit , its recommeded to not disable those to prevents bans.

@divyam234 the speed is still around ~50MB/s with your rate limit setting. It went up to ~200+MB/s if I disable the rate limit.
runCmd.Flags().BoolVar(&config.TG.RateLimit, "tg-rate-limit", true, "Enable rate limiting for telegram client")
runCmd.Flags().IntVar(&config.TG.RateBurst, "tg-rate-burst", 5, "Limiting burst for telegram client")
runCmd.Flags().IntVar(&config.TG.Rate, "tg-rate", 100, "Limiting rate for telegram client")
This block of code has been the same through out all version. Did you just implemented the rate limit feature in 1.4.22?
I will play around with the rate limit setting to see what I am able to push without disrespecting the rate limit.
Thanks.


Add pixelated Image tutorial youtube link

Hi, Skia is amazing library! I really love it.
I made pixelated image with React Native Skia tutorial video today and this is the PR to add this video link in the tutorial list :)
Thanks :)

yes so nice :)
On Tue, Sep 5, 2023 at 7:21 PM Daehyeon Mun @.***>
wrote:

Hi, Skia is amazing library! I really love it.
I made pixelated image with React Native Skia tutorial video today and
this is the PR to add this video link in the tutorial list :)
Thanks :)
You can view, comment on, or merge this pull request online at:
https://github.com/Shopify/react-native-skia/pull/1821
Commit Summary

6818617
https://github.com/Shopify/react-native-skia/pull/1821/commits/681861764a08974999dc32464881ff9b4a7f46f7
Add pixelated Image tutorial youtube link

File Changes
(1 file https://github.com/Shopify/react-native-skia/pull/1821/files)

M docs/docs/tutorials.md
https://github.com/Shopify/react-native-skia/pull/1821/files#diff-fdb0af4a6a030329a92576d91754976ee02e7878084c574234108318dfc22bd8
(1)

Patch Links:

https://github.com/Shopify/react-native-skia/pull/1821.patch
https://github.com/Shopify/react-native-skia/pull/1821.diff

—
Reply to this email directly, view it on GitHub
https://github.com/Shopify/react-native-skia/pull/1821, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACKXVXIINULVILBKXTPWZDXY5NP7ANCNFSM6AAAAAA4MDKRDQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I have signed the CLA


cps_ir: Sink single-use expressions to avoid temporaries

We over-hoist some expressions.
We should re-sink them when the optimization does not enable other optimizations and there is a single use with the same or lesser execution count.
Sometimes the single use is in a branch, which would help performance as well as code size.
SSA:
    _addEventListeners_onCancelWrapper: {
      "^": "Closure:0;_box_0,onCancel",
      call$1: function(e) {
        this._box_0.removeListeners.call$0();
        return this.onCancel.call$1(e);
      }
    },
CPS:
    _addEventListeners_onCancelWrapper: {
      "^": "Closure:0;_box_0,onCancel",
      call$1: function(e) {
        var v0 = this.onCancel;
        this._box_0.removeListeners.call$0();
        return v0.call$1(e);
      }
    },

Obsolete


Seeing some odd issues after updating to 5.0.0 from 4.1.2

I know auto-bind was removed but did this change how stores behave? I wrote my own auto-bind once I saw that it was going to be removed but my stores appear to have some issues after the update. Read the release notes and it didn't mention any particular changes to stores but I see that the 'store.js' file is now gone and is now just exporting a plain observable. I think this may be a breaking change.

I think the issue was that i didn't realize all components using the view HOC were getting autoBound and when I switched to my autoBind it stopped working -__- gotta go and ensure everything explicitly uses my autoBinder.

Yeah, the only breaking change was the removal of auto-bind. The store.js file only added the auto-bind to the observables (so I could completely remove it).


Fix circleci config

The test suite requires a running kong server.
Currently, the circleci script does not work properly.

Done, it was not that super easy.
CircleCI dind does not allow you to setup the environment that we needed (it is not possible to connect to kong that is connected to other container - postgres).


Iterate stats section

Trello: https://trello.com/c/EM3HJ1RV
What's changed?
We want to update the statistics section of /coronavirus to represent the new design captured in https://trello.com/c/5PdpKCiC/639-landing-page-re-jig-updating-the-statistics-section
Why?
When revealed the wider public will have a much better picture of Coronavirus content.
Expected changes
Before

After

⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠

@andysellick If the statistics partial  is no longer being used, it should be removed as well.

@JonathanHallam Thanks for your review. I've made the changes you suggested (missing guard clauses, misleading variable names) and updated the commit messages. I believe @andysellick has also made the changes to the arrow logic, so this PR is ready for re-review.


[Device Team] Implement option wheel

Back Button Switches current position in wheel, front button selects it.
Here are the options:

Short Description
Long Description
Volume

Long Hold of both buttons should turn on a debug mode?

Seems like I am getting an interesting error when playing audio files from the SD. It is able to play the audio for "audio" easily, but when playing "short description" it sometimes cuts out early (sometimes the audio doesn't even begin) and it returns the following error message,:
assert failed: heap_caps_free heap_caps.c:381 (heap != NULL && "free() target pointer is outside heap areas")
Other times it throws an abort() immediately without playing audio.
Playing file: Short Description.wav
abort() was called at PC 0x420d7072 on core 1
Backtrace: 0x40378196:0x3fcebd10 0x4037e2b1:0x3fcebd30 0x40384f45:0x3fcebd50 0x420d7072:0x3fcebdd0 0x42003241:0x3fcebe70 0x4200328d:0x3fcebeb0 0x4200c36a:0x3fcebed0 0x42046f99:0x3fcebf40

Seems like I am getting an interesting error when playing audio files from the SD. It is able to play the audio for "audio" easily, but when playing "short description" it sometimes cuts out early (sometimes the audio doesn't even begin) and it returns the following error message,:
assert failed: heap_caps_free heap_caps.c:381 (heap != NULL && "free() target pointer is outside heap areas")

Other times it throws an abort() immediately without playing audio.
Playing file: Short Description.wav

abort() was called at PC 0x420d7072 on core 1

Backtrace: 0x40378196:0x3fcebd10 0x4037e2b1:0x3fcebd30 0x40384f45:0x3fcebd50 0x420d7072:0x3fcebdd0 0x42003241:0x3fcebe70 0x4200328d:0x3fcebeb0 0x4200c36a:0x3fcebed0 0x42046f99:0x3fcebf40

Issue seemed to be that we defined a global Audio object while re-defining another Audio object deeper in the code that used similar I2S hardware resources. This was fixed by redefining the Audio object everywhere it is called. In the future I will define an audio manager with a single Audio object that accesses the I2S hardware resources without having to continuously re-initialize the object.

Created a single Audio object in the Esp32.cpp class that is accessible by any script that has access to the Esp32 device object declared in mainController.ino
Seems that while testing on the breadboard we have introduced some more audio playing issues and we are receiving post errors once again. Need to debug

Menu Wheel is implemented and fully working now!


Add requiresMainQueueSetup to fix warning in RN 0.49+

Please see this for reference.

What does that exactly do? Expect removing the warning?

@stoneman1 The warning stems from here.

I can see that it now gives a proper warning, but how will the underlying issue get fixed, in other words, what do we have to do to achieve "main queue setup" and avoid this breaking "in a future release of React Native?

@ayercm So from my understanding, by returning true for requiresMainQueueSetup, we signify that this module interacts with UI directly. If we return false it will run on the background thread. Either way, I think we should define requiresMainQueueSetup here to suppress the warning, but we can discuss what the returning boolean should be.


Fix/support pubkey encodings

This PR adds support for multiple public key encodings in the DID document.
Fixes https://github.com/decentralized-identity/did-jwt/issues/127
Also removes the @stablelib/utf8 dependency.

Added two tests, and caught a bug 👍


Union type inference doesn't distinguish types with constant values if any of them has a non-constant value

TypeScript Version:  3.4.4-dev.201xxxxx, 3.5.0-dev.20190420
Search Terms: Type inference, type union, constant values, variable values, property does not exist on type
Code
type _0 = {foo: string}

type _01 = _0 & {foo: "1"}
type _02 = _0 & {foo: "2", bar: string}
type _03 = _0 & {foe: "3", bar: string}

type _04 = _01 | _02 | _03
function ex(ample: _04) {
    if(ample.foo == "2") {
        console.log(ample.bar)
    }
}

Expected behavior:
Compiles successfully
Actual behavior:
Compilation fails:
ast.ts:10:27 - error TS2339: Property 'bar' does not exist on type '_04'.
  Property 'bar' does not exist on type '_01'.

10         console.log(ample.bar)
                             ~~~

Found 1 error.

Playground Link: https://www.typescriptlang.org/play/#src=type _0 %3D {foo%3A string}

type _01 %3D _0 %26 {foo%3A "1"}
type _02 %3D _0 %26 {foo%3A "2"%2C bar%3A string}
type _03 %3D _0 %26 {foe%3A "3"%2C bar%3A string}

type _04 %3D _01 | _02 | _03
function ex(ample%3A _04) {
    if(ample.foo %3D%3D "2") {
        console.log(ample.bar)
    }
}

Related Issues: None found
If a union of types is distinguished by values on a property foo and one of the types has a variable value for that property, none of them are distinguished in an if statement and as a result the body of that statement hasn't inferred any specific type. Please note that the example here is phrased to highlight a likely trigger: a subtle mistake in code where there's a "parent" type defining a variable value for the property and a "child" type incorrectly overriding it.
At a lower level, for the console.log(...) line the compiler is inferring _01 | _02 | _03 (or more strictly not inferring from _04) but should be inferring _02 | _03. In the case where this situation is due to a mistake in the code it may still produce an error message but at least it'd be an error message referring to the errant type.
If nothing else, it would be nice to have a compiler warning that the value that the expression is testing isn't constant for all members of the union.

foe —> foo


Inspect just last commit

When PUSH WebHook is sent to the WebHook URL then a batch of commits are queued. When we rebase a branch, all commits are queued and inspected again, one by one.
This is a waste of time and server resources, and PHPCI should analyse just the last commit (due it contains all updates included in that branch).

One of those commits could break a build. If PHPCI skipped to the last commit it would report a broken build and you would think the last commit was the culprit when it is not. That could be misleading.

Hi @JoolsMcFly
Then maybe a Plan B could be skip a commit that was already analysed? Imagine a Pull Request has about 100 small commits, and then we rebase that Pull Request. When we push --force that rebased branch then we will queue 100 commits again, when we already inspected them and - more important - when we rebased from another branch that is already inspected too.
What do you think?

I hear you. I've actually tweaked PHPCI for our needs and added a branch whitelist so it only builds master and our SprintN branches. Saves resources and build time when devs are working in their own branches.
May I ask why you have to use rebase? I have never used rebase myself, I always merge.

Given this case, how can I add this branch whitelist? Is there a way via phpci.yml configuration file to set-up a set of branches that I want to inspect and then ignore other branches?
Some times is easier for us to use rebase, specially when some of us are working with some code that changes every few minutes due all new updates (so we pull the parent branch and then rebase from there) - Probably you already know about this, just in case https://www.atlassian.com/git/tutorials/merging-vs-rebasing

I just made a Q&D tweak to PHPCI/Controller/WebhookController.php's bitbucketWebhook method:
        foreach ($payload['push']['changes'] as $commit) {
            try {
                $email = $commit['new']['target']['author']['raw'];
                $email = substr($email, 0, strpos($email, '>'));
                $email = substr($email, strpos($email, '<') + 1);

                // I added this IF statement:
                if (preg_match('#^(?:Sprint_[0-9]*_Release|master)$#', $commit['new']['name'])) {
                    $results[$commit['new']['target']['hash']] = $this->createBuild(
                        $project,
                        $commit['new']['target']['hash'],
                        $commit['new']['name'],
                        $email,
                        $commit['new']['target']['message']
                    );
                }
                // patch ends here
                $status = 'ok';
            } catch (Exception $ex) {
                $results[$commit['new']['target']['hash']] = array('status' => 'failed', 'error' => $ex->getMessage());
            }

As you can see it's very straightforward, I just run a regexp on the branch name and voilà.
Thanks for your link. I actually checked this article after I pasted my message! I might start rebasing more often now. Thanks.

Another nice read, indeed.
👍 I will try to implement a similar update on my Webhook Controller, thanks!


GetCommentsCount always returns 0 so comments never work

It would appear this field doesn't get populated correctly so don't use it for now.

@mmitche Either there is a bug in the github api, or github.

In the newer versions I think it works properly (using it now)

@mmitche are you just using webhooks though?  If that is the case it would never check here for comments.

@DavidTanner In this case yeah.  If we hit a restart, it will do an initial check for comments


toki pona Support

I would like to request support for toki pona to be added to this project.
The in-game code is tok
It's a constructed language, but I'd hardly consider it fictional.
There are many people who would love to help in translation :)

https://crowdin.com/project/sodium-fabric/discussions/1


Add syntax example to Python API reference

Inline code snippets from the syntax examples to explain how to use the Python APIs.

okay , maybe I can help

@kinfey - are you still looking into this? If so could you please add target dates for completion?

@kinfey - are you still looking into this? If so could you please add target dates for completion?

I will merge it on Next Monday

@kinfey - where you able to merge this?

yes ,give me  more 2 days

Closing so we can create new issues for docs later


No Verification That Passwords Match

Hello,
Taking a look at this and I see that the policy has two password inputs for new password and to re-enter password. Not sure why this is there because there is nothing verifying that the passwords match.
I suggest either removing the reEnterPassword claim or put in a method that verifies the passwords match before writing it.
[Enter feedback here]

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

ID: 420a3332-60e0-40f6-ad8e-9179977d3194
Version Independent ID: fa315134-a545-40d1-7a1a-845ce5a61021
Content: Set up password change by using custom policies - Azure AD B2C
Content Source: articles/active-directory-b2c/add-password-change-policy.md
Service: active-directory
Sub-service: b2c
GitHub Login: @kengaderdus
Microsoft Alias: kengaderdus

@Norrch2
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

@Norrch2
Thank you for your feedback and patience. In the article, the pre-requisites show that you need to use the provided starter packs, and the two claim types have been declared there.
Regarding a check whether they match, the claim types are considered special. The UI validates that the user correctly re-entered their password during account creation based on them (claim types).
I hope this helps.

Please allow me a few to deploy these to test prior to closing this ticket.

@kengaderdus I have determined what the problem was. The problem was caused because the special treatment of these claims is only applicable for outputClaims and not display claims. If DisplayClaims is the direction we should be going should this also support displayClaims too?

@Norrch2
The special treatment is applied to both OutputClaims and DisplayClaims as long as you retain the Ids of the claimsTypes as reenterPassword and newPassword.

@Norrch2
We'll now close this issue. #please-close


fixing dtype bug vectorstore

🚀 🚀 Pull Request
Title: Fix Data Type Mismatch in VectorStore
Description:
###Summary
This pull request addresses a bug  where creating a tensor using VectorStore and adding it to the tensor embeddings leads to  an error due to a data type mismatch. The issue arises when the default data type is set to float32 while when we add embedding it has dtype float64. VectorStore consistently uses float32 as the default data type and fixing it gives that to change it in the back of VectorStore.
Fix
Resolves the error encountered when creating a tensor with VectorStore and adding it to the tensor embedding due to a data type mismatch.
How to Test

Create a tensor using VectorStore.
Add embedding to the tensor.
Verify that the error no longer occurs.
Ensure that other functionalities remain unaffected

Checklist
Code has been tested locally and passes all relevant tests.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Alibi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@DocAlibi really appreciate for the contribution, team will review and follow up! 🙏

Hey @DocAlibi! Thank you for the PR. An issue here is that there is a loss of data when converting from float64 to 32 and we should probably not do such implicit conversions. So it is safer to let the users make the decision here. However, can you think of any other way we could make the user experience better (perhaps a better error message)?

@Fayaz thank you for your review.
I believe we already are doing typecasting in VectorStore code, so I
believe it should be fine to do it here too.
Here is the example, where my program is erroring out, however i believe it
is quite common use case. On top of that, our embedding htype by default is
float32, won't it be better to upcast/downcast to it by default? I believe
there shouldn't be happening unrecoverable information loss
ср, 24 янв. 2024 г., 10:05 Fayaz Rahman @.***>:

Hey @DocAlibi https://github.com/DocAlibi! Thank you for the PR. An
issue here is that there is a loss of data when converting from float64 to
32 and we should probably not do such implicit conversions. So it is safer
to let the users make the decision here. However, can you think of any
other way we could make the user experience better (perhaps a better error
message)?
—
Reply to this email directly, view it on GitHub
https://github.com/activeloopai/deeplake/pull/2748#issuecomment-1907337262,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATCCJ3UHO37TW7TBI3L7JBTYQCCATAVCNFSM6AAAAABCGY6MECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBXGMZTOMRWGI
.
You are receiving this because you were mentioned.Message ID:
@.***>

This would especially be a problem if a user wants float64 embeddings for some reason and we automatically converted it to another dtype. I can't see your example btw.
I think a better solution would be to dynamically change the dtype of the tensor according to the first sample being added, instead of changing the input data. Would you be interested in doing that @DocAlibi?

Error in the attachment.
if we use float64 in embeddings , won't this be inefficient in terms of
memory?
P.S. Error that occurs  connected with dtype is not fully understandable in
my case.
[image: photo_5300892978421814942_w (1).jpg][image:
photo_5300892978421814945_w (1).jpg]
On Thu, Jan 25, 2024 at 6:20 PM Fayaz Rahman @.***>
wrote:

This would especially be a problem if a user wants float64 embeddings for
some reason and we automatically converted it to another dtype. I can't see
your example btw.
I think a better solution would be to dynamically change the dtype of the
tensor according to the first sample being added, instead of changing the
input data. Would you be interested in doing that @DocAlibi
https://github.com/DocAlibi?
—
Reply to this email directly, view it on GitHub
https://github.com/activeloopai/deeplake/pull/2748#issuecomment-1910093018,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATCCJ3WC6SGUM7TY5YZ6RYLYQJEYJAVCNFSM6AAAAABCGY6MECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJQGA4TGMBRHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

It would consume more storage but better to do that and print some kind of warning (that float32 is default) rather than changing input data.

Hi @DocAlibi We decided to close this PR, but if you want to cast the embeddings you may do so prior to the input to the VectorStore.add() function, and if you'd like to use float64 embeddings, you can define the tensors using the approach below:
vector_store = VectorStore('mem://dummy', tensor_params=[{'name': 'embedding', 'dtype': 'float64'},
                                                         {'name': 'text', 'htype': 'text'},
                                                         {'name': 'metadata', 'htype': 'json'}])


feat: Integrate Codecov with Bitrise

Description
Integrate Codecov with Bitrise to show the code coverage.
Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist

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

Bitrise
View test reports
View more details on Bitrise

Build Artifacts

grype_output_vm_build.csv

grype_output_vm_build.json


Update Add Event Form to match updated event model

Please provide a summary of the feature
With the updates to the events model the event form can no longer submit objects in the feature/recurringEvents branch.
PR into feature/recurringEvents
Are there any potential issues you foresee with this feature
If you are accessing a database with older event objects your calendar may white screen and you should delete your event objects.
Is this feature related to any current or past issues? Please provide the #
#148
If you're interested in working on this feature, please comment so you can be assigned
Assigned to @InstincDev

Thank for posting the issue.  It's all good 👍🏾. I wasn't planning on working on this till Saturday evening. I will check for updated details then.

Completed


Look up whether "date" is included in the result_dict, not string result

Summary
When decoding a circuit job result, the date contained in the result json can either be an object which is decoded by the RuntimeDecoder or a string. In case it's a string, it needs to be handled correctly and parsed as an object in json_decoder.py:decode_result.
Details and comments
At the moment, the decode_result code is looking at result which is the result as a string, but it should look at the json result instead.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2942

Relevant Lines:
5875

💛  - Coveralls


Fix -Wstrict-prototypes warnings

Pull Request Template
Description
Closes #948
Checklist Before Requesting Review

[ ] PR Title follows correct guidelines.
[ ] Description of changes and all other relevant information.
[ ] (Optional) Link any related GitHub issues using a keyword
[ ] (Optional) Provide info on any relevant functional testing/validation.  For API changes or significant features, this is not optional.

/clang-format-run


Discover devices doesn't work on Docker

➜ arnau elgato-keylight (async-discovery) ✗ docker run -it --entrypoint /usr/local/bin/elgato-keylight-discover elgato-keylight:latest
Error: avahi-browse error: No such file or directory (os error 2)
➜ arnau elgato-keylight (async-discovery) ✗ docker run --rm -it --entrypoint /bin/bash elgato-keylight
root@0b3793dbbc39:/app# avahi-daemon
Found user 'avahi' (UID 101) and group 'avahi' (GID 102).
Successfully dropped root privileges.
avahi-daemon 0.8 starting up.
dbus_bus_get_private(): Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
WARNING: Failed to contact D-Bus daemon.
avahi-daemon 0.8 exiting.
root@0b3793dbbc39:/app# avahi-browse
bash: avahi-browse: command not found

Mount dbus socket on container https://github.com/mviereck/x11docker/wiki/How-to-connect-container-to-DBus-from-host


Does the Encoder treat itype=14 and 15 the same as itype=10 and 11?

itype=10: Uninferable jump
itype=11: Inferrable jump
itype=14: Other uninferable jump
itype=15: Other inferable jump

Yes


Persistent Chat History in VSCode

Feature Request: Persistent Chat History in VSCode
Description
I would like to request a feature where CodeGPT can save chat history between sessions in Visual Studio Code. This functionality would be similar to what Gemini and OpenAI provide, where the chat history is tied to the user and can be accessed even after restarting VSCode.
Use Case
This feature would be extremely useful for developers who need to refer back to previous conversations with CodeGPT for context or to continue a prior discussion without losing any information.
Proposed Solution

Implement a mechanism to save chat history locally or in the cloud.
Ensure the chat history is tied to the user and can be retrieved upon restarting VSCode.
Provide an option to clear the chat history if needed.

Thank you for considering this feature request. It would greatly enhance the usability and continuity of using CodeGPT within VSCode.

Hello @tJolloHMH, thank you for your inquiry. Currently, you can review your conversation history in the Playground, but this only applies to your own agents and not to public agents. We appreciate your suggestion and will consider it for future updates. At CodeGPT, we value your participation in our development. Is there any other question or suggestion you would like to share with us today?

+1 for this.
What should I do to "review your conversation history in the Playground" with Claude?
I also want to know.


Language fix

Didn't know if I should go with username or mention, so I went with username for now


BomContentTest assertReachable should not wait for release pull request

In BomContentTest, assertReachable should not wait for a pull request for release.
Currently it waits until a "release pull request" (e.g., https://github.com/googleapis/java-cloud-bom/pull/4301) is made https://github.com/googleapis/java-cloud-bom/blob/main/.github/workflows/full-convergence-check.yaml#L10.
In normal pull requests, the check is skipped:

When someone tries to add nonexistent artifacts to a BOM (google-cloud-bom/pom.xml or libraries-bom/pom.xml), then the pull request is invalidated. (not waiting for the release pull request).

@lqiu96 This is an example bad pull request https://github.com/googleapis/java-cloud-bom/pull/4456 The artifact ID has typo but the checks succeed. We already have logic to check such typo via assertReachable (https://github.com/googleapis/java-cloud-bom/blob/main/tests/src/test/java/com/google/cloud/BomContentTest.java#L65). However, it's not called when normal pull requests come.


[EXECUTOR] Enable multiple device in one graph, beta of model parallel

The user can annotate a ctx_group property on each of the operator
During bind, a group2ctx map can be provided to specify mapping from group to device.
Copy node is automatically inserted.

Tested on CPU, hope someone can take over to test on GPU and do model parallel tests on cases such as LSTM.

cc @antinucleon @pluskid
The API is backward compatible, with a new API ExecutorBindX, that allows additional mapping, we can open an issue discussing model parallel interface.

@mli can you help review this?


Some more typecasts to satisfy the latest version of the clang++ compiler

Adding these typecasts prevents the more recent versions of the clang++ compiler from complaining.

Also see related discussion here https://github.com/dvidelabs/flatcc/pull/59

Thanks. We could use a test for running samples/monster or similar in a C++ compiler as part of the test suite to catch these early.


Make Version() return full result in golang client

We now return the full version result in the client.

Codecov Report

Merging #363 (a5c7822) into main (b77965b) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##            main    #363   +/-   ##
=====================================
  Coverage   6.89%   6.89%
=====================================
  Files          2       2
  Lines         29      29
  Branches      17      17
=====================================
  Hits           2       2
  Misses        27      27


[WIP] Add "profile" gadget

Based on BCC's tool profile:
https://github.com/iovisor/bcc/blob/master/tools/profile_example.txt

TODO:

[ ] https://github.com/iovisor/bcc/pull/2824

How is it supposed to work?
I see nothing in the output
mvb@asus ~/.../inspektor-gadget $ ./inspektor-gadget profile
Node numbers: 0 = ip-10-0-13-205 1 = ip-10-0-25-233

You should select pods with --label or similar. Also, if the selected pods don't take much CPU, it is possible that the samples don't pick anything. Might work better if the processes are actively using the CPU. This is a WIP so I have not tested it properly.

I tested it and I'm able to see the output in folded mode, is there a specific reason to use that format?
I added some more documentation in https://github.com/kinvolk/inspektor-gadget/pull/47.
I think it'd be good to remove the deployment options and other non related things from this PR so we can merge it until we make a decision on the other changes.

I tested it and I'm able to see the output in folded mode, is there a specific reason to use that format?

I liked the short form but maybe it needs to be optional like in the bcc tool upstream...

I think it'd be good to remove the deployment options and other non related things from this PR so we can merge it until we make a decision on the other changes.

It makes sense. It can be rebased on master now.


[test] not clear what combinations of input/output formats are valid

I send turtle to e-Link and request the results in HTML. I'm not sure if this combination is considered but if not, then this should be clearly stated in the documentation.
The request is:
curl -X POST --header "Content-Type: text/turtle" --header "Accept: text/html" -d @test-e-link.txt "http://api-dev.freme-project.eu/current/e-link/documents?templateid=1" -v

The turtle is: test-e-link.txt
The results is:

Whitelabel Error Page

This application has no explicit mapping for /error, so you are seeing this as a fallback.

Fri Oct 23 13:20:36 CEST 2015

There was an unexpected error (type=Internal Server Error, status=500).

Can only convert to outformat "text/html" when informat is also "text/html"

its not clear if this combination of input/output format is supported.

the error should be formated same as the errors of the other services (created separated issue for this https://github.com/freme-project/e-Internationalization/issues/13)

@borriellom please add a line to the e-internationlization documentation that states that roundtripping only works when the input format is equal to the output format.

Documentation changed. Please, check if it's ok.

roundtripping only works when the input format is equal to the output format.

Why not allowing input: HTML, output: NIF?... yes this is not round-tripping but, I can then use the NIF, do smth with it, and convert it back to HTML. For such scenarios, input and output format should not be the same.
It can be good to highlight (put in bold) the part saying: "This is a general rule when performing the round-tripping: input and output formats must be the same". Otherwise, the documentation looks much better.

Also, I dont think the statement "roundtripping only works when the input format is equal to the output format" is true. To me it worked HTML to Turtle. See the example in https://github.com/freme-project/e-Internationalization/issues/18

Yes, it works from HTML to Turtle, but it's not round-tripping.
In this scenario you are simply invoking a FREME e-Service over a HTML file. The result is turtle as usual. Its explained in the first part of documentation, where I talk about the conversion to NIF.
The actual round-tripping is performed only if input and output formats are the same. That doesn't mean that e-Internationalization returns an error if you specify HTML as input format and Turtle as output format. It simply means that if you want perform the round-tripping you have to provide same input and output formats.

ok ,thanks for clarification


#203 Update color theme & logo

✅ DoD

[x] Resolves #203
[x] Release notes updated
[x] HelpScout documentation updates proposed  na

(use n/a when API docs (Release notes, etc) do not need to be updated)
📝 Summary
the build version 1.5.6

📸 Examples

🛑 Problems

Write any discovered & unresolved problems (link to created Jira issues)

💡 More ideas
Write any more ideas you have

Should we also try to build the windows version?


account 'id'

While testing my OS Java ACME server impl I came across the topic of expected 'id' element in the account response. As far as I can see there is nothing like this included in the spec.
My proposal would be to the URL from the location header. This avoids any assumptions regarding the implementation ...
Nevertheless:
You did a great Job!
Greetings,
Andreas

I'm not entirely sure what you mean... Dehydrated behaves (at least mostly) RFC8555-conform, so if you want to write a new server-software you should implement it following RFC8555, there are no assumptions in implementation on client- or server-side.

Hi  Lukas,

I'm not entirely sure what you mean... Dehydrated behaves (at least mostly) RFC8555-conform, so if you want to write a new server-software you should implement it following RFC8555, there are no assumptions in implementation on client- or server-side.

if I understand your software correctly it takes advantage of an element
'id' in the account data structure
line 404:
ACCOUNT_ID="$(cat "${ACCOUNT_KEY_JSON}" | get_json_int_value id)"
But as far as I can see there is NO element 'id' defined in the spec
(Snippet from RFC8555):
{
"status": "valid",
"contact": [
<EMAIL_ADDRESS><EMAIL_ADDRESS>],
"termsOfServiceAgreed": true,
"orders": "https://example.com/acme/orders/rzGoeA"
}
Moreover I would consider it at least dangerous to make assumption about
the server's URL structure:
line 408:
ACCOUNT_URL="${CA_ACCOUNT}/${ACCOUNT_ID}"
This will be a valid in many implementations but it is NOT backed by the
spec!
BTW::
I'm testing my stuff with your client because colleagues recommended it
as 'great stuff' and want to be sure everything's woks out fine, not to
spot some minor spec deviations ;-)
Greetings,
Andreas
--
Andreas Kühne
Chair of OASIS DSS-X
phone: +49 177 293 24 97
mailto<EMAIL_ADDRESS>Trustable Ltd. Niederlassung Deutschland Gartenheimstr. 39C - 30659 Hannover Amtsgericht Hannover HRB 212612
Director Andreas Kühne
Company UK Company No: 5218868 Registered in England and Wales

I think you are correct, this seems to be something dehydrated doesn't do correctly. I'll fix this in the next few days.

Thanks for opening this issue @kuehne-trustable-de.
I realized Pebble carried over this "Boulder-ism". I have a PR up to remove it: https://github.com/letsencrypt/pebble/pull/225 @lukas2511 Perhaps it will help you test your fix.
I'd like to remove the ID field from Boulder's "ACME v2" Account resource responses but it will be a little trickier to implement and will need to follow a full API announcement with enough fore-warning for developers/users. I'm tracking that in https://github.com/letsencrypt/boulder/issues/4136 but it will probably be some time before it can be prioritized.

This has been fixed by now. Thanks for reporting.


RFC Adding Derived Key Feature

Added Derived Key Feature set. We can now create a derived key and display it in hex format.

@AdithyaKrishnan Can you rebase and squash the commits?


inbox: Focus on entire row instead of stream name on show.

discussion: https://chat.zulip.org/#narrow/stream/101-design/topic/inbox.20view.20.2322408/near/1647407

Posted a few comments, otherwise lgtm.

Merged, thanks @amanagr!


Fix for #71: Added check if instances of ClassTree are null

Fix for #71
Instances of ClassTree were set to null when there was no class declaration to initialize them with (e.g. in case of a package-info.java).
Now there is an if-condition catching those null trees.

I just realized that these null checks are already included in PR #64... Should not be a problem though, I think the additional tests in this PR are still good to have.
I will remove the null checks from PR #64 so that we don't have any merge conflicts.

As discussed we will do the suggested cleanup but the fix itself is fine to be merged and go into the release.
@lmarniazman please file an issue for the remaining cleanups and later when you have time create additional PRs after the release for that.

@hohwille
Moved this to #81, thanks for the feedback!


Add filter implementation to DG

#70

Codecov Report

Merging #73 (f465317) into master (2abff9a) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #73   +/-   ##
=========================================
  Coverage     69.99%   69.99%
  Complexity      415      415
=========================================
  Files            78       78
  Lines          1383     1383
  Branches        139      139
=========================================
  Hits            968      968
  Misses          360      360
  Partials         55       55

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

LGTM


test(cpu-usage): test CPU load under various framerates

I.e., throttle request_animation_frame and build a table with FPS and CPU load columns.

Here is a chart (i did the tests in a random order, throttling animate() using:
// Always run (ran twice) [CPU 52%  , 54%]
if( Date.now() % 2 == 0) return; // [CPU 28.5%]
if( Date.now() % 4 == 0) return; // [CPU 16%]
if( Date.now() % 8== 0) return; // (ran twice) [CPU 12%, 13% ]