[WIP] Keep archived out of VimPerformanceState

depend:

[ ] https://github.com/ManageIQ/manageiq/pull/22589 (first 4 commits)

Overview
Collecting VimPerformanceState.capture takes timestamp into account.
For Infra, only the current state is available in the tables. This introduced some assumptions around only being able to collect the state for now, and not pruning out the soft deleted records.
For containers, we can collect in the past and we need to make sure we are only collecting records that are not soft deleted at the time.
Before
We were having way too many archived containers in the VimPerformanceState records.
This was filling up the database, causing us to process too many records, slowing down metrics capture, and slowing down metrics rollups.
After

We are no longer putting the ids for archived records in the performance state
Even records that have archived record ids in the performance state records, we are not returning them.

Outstanding

similar treatment of other soft deleted records
migration/script to prune out existing VimPerformanceStates that contain archived ids

update:

this is now build upon #22589
dropped future and other sophisticated logic. only capturing for now.

update:

fixed failing test ( s/&klass/klass/)
updated performance numbers in git comment.

update:

rubocop in spec: Time.now.utc.beginning_of_hour

update:

updated specs to better show where the change happened around capture and now fails when you comment out the changed code.

update:

rebased

UN-WIP: this has reduced quite a bit in complexity

Backported to petrosian in commit 10f15a3f1414f1210269dd00dcccd464e6cb64d8.
commit 10f15a3f1414f1210269dd00dcccd464e6cb64d8
Author: Jason Frey<EMAIL_ADDRESS>Date:   Fri Aug 11 15:07:24 2023 -0400

    Merge pull request #22585 from kbrock/capture_vim_performance

    Keep archived out of VimPerformanceState

    (cherry picked from commit 900fb1bc6d235dc41668dc11cc79f0621429cc4f)


Missing video?

Where can I find the video used for this demo? My Deepstream 5.0 install doesn't have it and the video pointed to in the same config points to the video with cars driving by and folks walking on a sidewalk.

Hi, same issue on the 5.1 install, did you manage to find it?


Nft History component wrong currency

tested on /bsx/gallery/945672150-19
Amount should be KSM instead of BSX

Note

we should calculate royalty amount

👋


Labels in ACSets with TypedTables DictTable

In the latest version (v1.4) of TypedTables, there is support for noninteger primary keys https://typedtables.juliadata.org/dev/man/dicttable/. This seems helpful for better label support in ACSets.

That's a nice feature, although I'm not sure it will directly help us since struct acsets (#376) is moving away from having underlying typed tables. Our unique_index feature achieves a similar effect though.


Multiple Fluidity Tree Items causes dashboard to not show content

I have two tree items set as per the instructions:
treeConfig.AddCollection<Competition>(...);
and
treeConfig.AddCollection<Entry>(...);
When I load the section in the back office there is no content in the summary tab?

Steps to reproduce:

Create multiple tree items under a single section:

  public class FluidityBootstrap : FluidityConfigModule
  {
    public override void Configure(FluidityConfig config)
    {
      config.AddSection("Competitions", "icon-trophy", sectionConfig =>
      {
        sectionConfig.SetTree("Competitions", treeConfig =>
        {
          treeConfig.AddCollection<Competition>(c => c.Id, "Competition", "Competitions", "A listing of competitions held", "icon-medal", "icon-medal", collectionConfig =>
            {
              ...
            });
          treeConfig.AddCollection<Entry>(e => e.Id, "Entry", "Entries", "A list of entries to the competitions", "icon-poker-chip", "icon-poker-chip", collectionConfig =>
            {
              ...
            });
        });
      });
    }

  }

Open the section in the back office.

Hi Jon,
This is expected behaviour as the summary dashboard only shows collections for which ShowOnDashboard has been set to true so out of the box it will be empty.

So I need to add collectionConfig.ShowOnDashboard(); to the collections I want to show there!

That is correct yes
On Mon, 25 Jun 2018, 5:47 pm Jon R. Humphrey<EMAIL_ADDRESS>wrote:

So I need to add collectionConfig.ShowOnDashboard(); to the collections I
want to show there!
[image: 2018-06-25_17-46-29]
https://user-images.githubusercontent.com/39102/41863787-c45fbe16-789f-11e8-8f20-51b750f5f49e.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/umco/umbraco-fluidity/issues/59#issuecomment-400019116,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgLyZ3FhJ2VIHOwwy8zjJNTsAEZGdqcks5uARQOgaJpZM4U2aw5
.


MAINT Fix typos and wording across the mooc

As per RL feedback from @tuscland, in this PR:

corrects a typo "metioned" -> "mentioned";
changes idiomatic expression "to linger on" -> "to focus on";
adds a comment on overfitting when random forest are not correctly tuned;
adds link towards wikipedia to explain the concept of "expected value" as a generalization of the weighted average.

Thank you Arturo for taking in account my feedback, and congrats to the MOOC team for this excellent training!


Upload: Add image previewer

So that an image-viewer was added to the el-image element in #16605 and thought it would be a cool addition to the upload-list.
I've extracted the image-viewer to the packages folder now that it is used by multiple components. Not sure if it should be exported in src/index.js aswell and get its own docs page?
I've added it to the docs but cannot translate to the other languages.
I didn't find any test in the upload component which checked the HTML so not sure if any should be added?
Please make sure these boxes are checked before submitting your PR, thank you!

[x] Make sure you follow Element's contributing guide (中文 | English | Español | Français).
[x] Make sure you are merging your commits to dev branch.
[x] Add some descriptions and refer relative issues for you PR.

Test failure is unrelated to my change, can you rerun the tests?

@nicoeg Upload has file slot. It's duplicated. https://element.eleme.cn/#/en-US/component/upload#user-avatar-upload


JSX element type 'Textarea' does not have any construct or call signatures

Description
The issue "JSX element type 'Textarea' does not have any construct or call signatures" is likely due to missing parentheses after the  component.
CodeSandbox/Snack link
https://codesandbox.io/
Steps to reproduce

Go to '...'
Click on '...'
Scroll down to '...'
See error

gluestack-ui Version
1.1.30
Platform

[ ] Expo
[x] React Native CLI
[ ] Next
[ ] Web
[x] Android
[ ] iOS

Other Platform
No response
Additional Information

I am experiencing the same issue.
The error occurs starting from version "1.1.30" of @gluestack-ui/themed. The error does not occur in version "1.1.29".

I am also having the same issue.
"@gluestack-style/react": "^1.0.56",
"@gluestack-ui/config": "^1.1.18",
"@gluestack-ui/themed": "^1.1.30",

I am experiencing the same issue.
The error occurs starting from version "1.1.30" of @gluestack-ui/themed. The error does not occur in version "1.1.29".

its working, thank you 😁

FlatList  also have the same problem.

Latest version of gluestack-ui/themed 1.1.31 fixes this issue.

Latest version of gluestack-ui/themed 1.1.31 fixes this issue.

thanks, its work

Hey All, Sorry for delayed response this issue has been fixed in latest version of @gluestack-ui/themed.


Deployment 2017-10-18

Deployment 2017-10-18
Status: Planned
Planned production date: 2017-10-18
Focus: AzSecPack
Services to Deploy:

[ ] Gallery (with shims changes)
[ ] Search Service
[x] Catalog2Registration
[x] Catalog2Dnx
[x] Stats.ImportAzureCdnStatistics
[x] Gallery.Maintenance
[x] Validation.Runner
[x] HandlePackageEdits
[x] V3 Monitoring Jobs

Repo
Service
INT
PROD (primary)
PROD (secondary)

NuGetGallery
Gallery
[x]
[ ]
[ ]

NuGet.Services.Metadata
Search Service
[x]
[x]
[ ]

NuGet.Services.Metadata
V3 Monitoring Jobs (endpointmonitoring)
[x]
[x]
N/A

NuGet.Services.Metadata
Catalog2Registration
[x]
[x]
N/A

NuGet.Services.Metadata
Catalog2DNX
[x]
[x]
N/A

NuGet.Jobs
Stats.ImportAzureCdnStatistics
[x]
[x]
N/A

NuGet.Jobs
Gallery.Maintenance
[x]
[x]
N/A

NuGet.Jobs
Validation.Runner
N/A
[x]
N/A

NuGet.Jobs
HandlePackageEdits
[x]
[x]
N/A

Related blog posts/docs:

N/A

Deployed commit:  TBA
Gallery
Functional:

Admin delete packages page should include whether the package is soft-deleted or not (https://github.com/NuGet/NuGetGallery/issues/4683)
Delete Packages search UI does not show any message for empty search results (https://github.com/NuGet/NuGetGallery/issues/4230)
Delete package UI should de-dupe package ID (https://github.com/NuGet/NuGetGallery/issues/3856)
[api] [nuget.org] api/v2/FindPackagesById()/$count endpoint is broken (https://github.com/NuGet/NuGetGallery/issues/4760)
/stats/reports/packages/{id} returns 200 when Package doesn't exist (https://github.com/NuGet/NuGetGallery/issues/4701)
Latest version on Manage Packages view does not show SemVer 2.0.0 packages (#4782)
Edit Package experience is broken for SemVer 2.0.0 packages with build metadata (#4756)
Add recommendation in warning banner to Edit Package and Verify Package views (#4829)

Technical:

Auditing improvements (https://github.com/NuGet/Engineering/issues/724). requires shims merge

Stats.ImportAzureCdnStatistics
Technical:

CDN Log processor counts 300, 400 and 500 level HTTP responses as downloads (https://github.com/NuGet/NuGetGallery/issues/4803)
Trailing space (%20) on package ID in CDN logs causes log file to be rejected (https://github.com/NuGet/NuGetGallery/issues/4802)

Gallery.Maintenance
Technical:

Fix Gallery.Maintenance Crashes (https://github.com/NuGet/Engineering/issues/811)

Validation.Runner
Technical:

VCS request result has empty (or null) request ID, job ID, and region code (https://github.com/NuGet/Engineering/issues/844)
Eliminate unzip validator (https://github.com/NuGet/Engineering/issues/762)

** E2E tests **

E2E and functional tests should use protocol version header (https://github.com/NuGet/Engineering/issues/805)

HandlePackageEdits
Technical:

Filter out non-Available package status packages in Edit job (https://github.com/NuGet/NuGetGallery/issues/4654)

V3 Monitoring Jobs
Technical:

Updates to the framework to support the new queue based infrastructure (https://github.com/NuGet/NuGet.Services.Metadata/pull/243)
Add new queue-based jobs (https://github.com/NuGet/NuGet.Services.Metadata/pull/244)
If an exception cannot be deserialized, return a default exception instead (https://github.com/NuGet/NuGet.Services.Metadata/pull/242)

Discovered during INT validation: package edit page shows both warning messages for edit metadata as well as verify upload (form reuse). Fixed in this PR: https://github.com/NuGet/NuGetGallery/pull/4877

All deployments except Gallery are done for the sprint. We will be doing Gallery deployment next week.


Documentation for train_on_responses_only?

Can you write up some documentation how properly to use the new train_on_responses_only functionality? It doesn't seem to work out of the box with either chat templates or any of the manual formatting (e.g. Alpaca) examples.

Oh yep great idea!
https://github.com/unslothai/unsloth/wiki#train-on-completions--responses-only-do-not-train-on-inputs shows approx how to call it, but in the Ollama notebook https://colab.research.google.com/drive/1WZDi7APtQ9VsvOrQSSC5DDtxq159j8iZ?usp=sharing, you first need to use apply_chat_template which will make it work ie
chat_template = """Below are some instructions that describe some tasks. Write responses that appropriately complete each request.

### Instruction:
{INPUT}

### Response:
{OUTPUT}"""

from unsloth import apply_chat_template
dataset = apply_chat_template(
    dataset,
    tokenizer = tokenizer,
    chat_template = chat_template,
    # default_system_message = "You are a helpful assistant", << [OPTIONAL]
)

Then use
from trl import SFTTrainer
from transformers import TrainingArguments, DataCollatorForSeq2Seq
trainer = SFTTrainer(
    model = model,
    tokenizer = tokenizer,
    train_dataset = dataset,
    data_collator = DataCollatorForSeq2Seq(tokenizer = tokenizer),
    ...
    args = TrainingArguments(
        ...
    ),
)
from unsloth.chat_templates import train_on_responses_only
trainer = train_on_responses_only(trainer)

But in general, the function accepts an instruction and a response text field:
def train_on_responses_only(
    trainer,
    instruction_part = None, <<< eg "Instruction:\n"
    response_part    = None, <<< eg "Response:\n"
):

How does
instruction_part = "<|start_header_id|>user<|end_header_id|>\n\n",
response_part = "<|start_header_id|>assistant<|end_header_id|>\n\n",

work when potentially multiple instruction headers could be presented, eg a response to a function call "from: ipython"?
Would something like this be necessary?
instruction_part = "<|start_header_id|>user|ipython<|end_header_id|>\n\n",


TLS and rpc error between vault pods

@bonifaido Please find the TLS and rpc error between vault pods. I remember you fixed this issue through  #110.
Vault-0 Pod
==> Vault server configuration:
         Api Address: https://vault.default:8200
                 Cgo: disabled
     Cluster Address: https://vault.default:8201
          Listener 1: tcp (addr: "<IP_ADDRESS>:8200", cluster address: "<IP_ADDRESS>:8201", tls: "enabled")
           Log Level: debug

2018-08-22T12:34:10.259Z [DEBUG] storage.cache: creating LRU cache: size=0
2018-08-22T12:34:10.458Z [DEBUG] cluster listener addresses synthesized: cluster_addresses=[<IP_ADDRESS>:8201]
Mlock: supported: true, enabled: true
Storage: etcd (HA available)
Version: Vault v0.10.3
Version Sha: c69ae68faf2bf7fc1d78e3ec62655696a07454c7
==> Vault server started! Log data will stream in below:
2018-08-22T12:34:11.397Z [INFO ] core: security barrier not initialized
2018-08-22T12:34:13.025Z [INFO ] core: security barrier not initialized
2018-08-22T12:34:17.425Z [INFO ] core: security barrier not initialized
2018-08-22T12:34:19.725Z [INFO ] core: security barrier not initialized
2018-08-22T12:34:23.001Z [INFO ] core: security barrier not initialized
2018-08-22T12:34:29.876Z [INFO ] core: security barrier not initialized
2018-08-22T12:34:33.012Z [INFO ] core: security barrier not initialized
2018-08-22T12:34:39.837Z [INFO ] core: security barrier not initialized
2018-08-22T12:34:39.897Z [INFO ] core: security barrier not initialized
2018-08-22T12:34:41.097Z [INFO ] core: security barrier not initialized
2018-08-22T12:34:41.218Z [INFO ] core: security barrier initialized: shares=5 threshold=3
2018-08-22T12:34:41.346Z [DEBUG] core: cluster name not found/set, generating new
2018-08-22T12:34:41.346Z [DEBUG] core: cluster name set: name=vault-cluster-c7d5c7d3
2018-08-22T12:34:41.346Z [DEBUG] core: cluster ID not found, generating new
2018-08-22T12:34:41.346Z [DEBUG] core: cluster ID set: id=faa23069-95dc-3de4-f5ff-51cb2671c1ac
2018-08-22T12:34:41.533Z [DEBUG] core: generating local cluster certificate
2018-08-22T12:34:41.674Z [INFO ] core: post-unseal setup starting
2018-08-22T12:34:41.674Z [DEBUG] core: clearing forwarding clients
2018-08-22T12:34:41.674Z [DEBUG] core: done clearing forwarding clients
2018-08-22T12:34:41.839Z [INFO ] core: loaded wrapping token key
2018-08-22T12:34:41.839Z [INFO ] core: successfully setup plugin catalog: plugin-directory=
2018-08-22T12:34:41.959Z [INFO ] core: no mounts; adding default mount table
2018-08-22T12:34:42.120Z [INFO ] core: successfully mounted backend: type=kv path=secret/
2018-08-22T12:34:42.120Z [INFO ] core: successfully mounted backend: type=cubbyhole path=cubbyhole/
2018-08-22T12:34:42.120Z [INFO ] core: successfully mounted backend: type=system path=sys/
2018-08-22T12:34:42.120Z [INFO ] core: successfully mounted backend: type=identity path=identity/
2018-08-22T12:34:42.321Z [INFO ] core: restoring leases
2018-08-22T12:34:42.321Z [INFO ] rollback: starting rollback manager
2018-08-22T12:34:42.321Z [DEBUG] expiration: collecting leases
2018-08-22T12:34:42.324Z [DEBUG] expiration: leases collected: num_existing=0
2018-08-22T12:34:42.324Z [INFO ] expiration: lease restore complete
2018-08-22T12:34:42.547Z [DEBUG] identity: loading entities
2018-08-22T12:34:42.594Z [DEBUG] identity: entities collected: num_existing=0
2018-08-22T12:34:42.596Z [INFO ] identity: entities restored
2018-08-22T12:34:42.596Z [DEBUG] identity: identity loading groups
2018-08-22T12:34:42.598Z [DEBUG] identity: groups collected: num_existing=0
2018-08-22T12:34:42.598Z [INFO ] identity: groups restored
2018-08-22T12:34:42.599Z [DEBUG] core: starting cluster listeners
2018-08-22T12:34:42.599Z [DEBUG] core: cluster listener setup function
2018-08-22T12:34:42.599Z [DEBUG] core: clearing forwarding clients
2018-08-22T12:34:42.599Z [DEBUG] core: done clearing forwarding clients
2018-08-22T12:34:42.600Z [DEBUG] core: leaving cluster listener setup function
2018-08-22T12:34:42.600Z [INFO ] core: post-unseal setup complete
2018-08-22T12:34:42.600Z [INFO ] core: core/startClusterListener: starting listener: listener_address=<IP_ADDRESS>:8201
2018-08-22T12:34:42.600Z [INFO ] core: core/startClusterListener: serving cluster requests: cluster_listen_address=[::]:8201
2018-08-22T12:34:42.682Z [INFO ] core: root token generated
2018-08-22T12:34:42.699Z [INFO ] core: pre-seal teardown starting
2018-08-22T12:34:42.699Z [INFO ] core: stopping cluster listeners
2018-08-22T12:34:42.699Z [DEBUG] core: waiting for success notification while stopping cluster listeners
2018-08-22T12:34:42.699Z [INFO ] core: shutting down forwarding rpc listeners
2018-08-22T12:34:42.699Z [INFO ] core: forwarding rpc listeners stopped
2018-08-22T12:34:43.108Z [INFO ] core: rpc listeners successfully shut down
2018-08-22T12:34:43.108Z [INFO ] core: cluster listeners successfully shut down
2018-08-22T12:34:43.108Z [DEBUG] expiration: stop triggered
2018-08-22T12:34:43.108Z [DEBUG] expiration: finished stopping
2018-08-22T12:34:43.108Z [INFO ] rollback: stopping rollback manager
2018-08-22T12:34:43.108Z [INFO ] core: pre-seal teardown complete
2018-08-22T12:34:44.528Z [DEBUG] core: cannot unseal, not enough keys: keys=1 threshold=3 nonce=69f2f4a4-1080-d4ca-9fb7-22cb1978a9c6
2018-08-22T12:34:44.585Z [DEBUG] core: cannot unseal, not enough keys: keys=2 threshold=3 nonce=69f2f4a4-1080-d4ca-9fb7-22cb1978a9c6
2018-08-22T12:34:44.849Z [INFO ] core: vault is unsealed
2018-08-22T12:34:44.850Z [INFO ] core: entering standby mode
2018-08-22T12:34:45.015Z [INFO ] core: acquired lock, enabling active operation
2018-08-22T12:34:45.466Z [DEBUG] core: generating local cluster certificate
2018-08-22T12:34:45.666Z [INFO ] core: post-unseal setup starting
2018-08-22T12:34:45.666Z [DEBUG] core: clearing forwarding clients
2018-08-22T12:34:45.666Z [DEBUG] core: done clearing forwarding clients
2018-08-22T12:34:45.727Z [INFO ] core: loaded wrapping token key
2018-08-22T12:34:45.728Z [INFO ] core: successfully setup plugin catalog: plugin-directory=
2018-08-22T12:34:45.743Z [INFO ] core: successfully mounted backend: type=kv path=secret/
2018-08-22T12:34:45.743Z [INFO ] core: successfully mounted backend: type=system path=sys/
2018-08-22T12:34:45.743Z [INFO ] core: successfully mounted backend: type=identity path=identity/
2018-08-22T12:34:45.743Z [INFO ] core: successfully mounted backend: type=cubbyhole path=cubbyhole/
2018-08-22T12:34:45.886Z [INFO ] core: restoring leases
2018-08-22T12:34:45.887Z [INFO ] rollback: starting rollback manager
2018-08-22T12:34:45.887Z [DEBUG] expiration: collecting leases
2018-08-22T12:34:46.048Z [DEBUG] expiration: leases collected: num_existing=0
2018-08-22T12:34:46.048Z [INFO ] expiration: lease restore complete
2018-08-22T12:34:46.093Z [DEBUG] identity: loading entities
2018-08-22T12:34:46.132Z [DEBUG] identity: entities collected: num_existing=0
2018-08-22T12:34:46.132Z [INFO ] identity: entities restored
2018-08-22T12:34:46.132Z [DEBUG] identity: identity loading groups
2018-08-22T12:34:46.175Z [DEBUG] identity: groups collected: num_existing=0
2018-08-22T12:34:46.175Z [INFO ] identity: groups restored
2018-08-22T12:34:46.193Z [DEBUG] core: starting cluster listeners
2018-08-22T12:34:46.193Z [DEBUG] core: cluster listener setup function
2018-08-22T12:34:46.193Z [DEBUG] core: clearing forwarding clients
2018-08-22T12:34:46.193Z [DEBUG] core: done clearing forwarding clients
2018-08-22T12:34:46.194Z [DEBUG] core: leaving cluster listener setup function
2018-08-22T12:34:46.194Z [INFO ] core: post-unseal setup complete
2018-08-22T12:34:46.194Z [INFO ] core: core/startClusterListener: starting listener: listener_address=<IP_ADDRESS>:8201
2018-08-22T12:34:46.194Z [INFO ] core: core/startClusterListener: serving cluster requests: cluster_listen_address=[::]:8201
2018-08-22 12:34:55.899963 I | http: TLS handshake error from <IP_ADDRESS>:59162: EOF
2018-08-22 12:35:05.886677 I | http: TLS handshake error from <IP_ADDRESS>:59178: EOF
2018-08-22 12:35:05.950921 I | http: TLS handshake error from <IP_ADDRESS>:59182: EOF
2018-08-22 12:35:05.957330 I | http: TLS handshake error from <IP_ADDRESS>:59180: EOF
2018-08-22 12:35:12.920283 I | http: TLS handshake error from <IP_ADDRESS>:59188: EOF
Vault-1 pod
==> Vault server configuration:
         Api Address: https://vault.default:8200
                 Cgo: disabled
     Cluster Address: https://vault.default:8201
          Listener 1: tcp (addr: "<IP_ADDRESS>:8200", cluster address: "<IP_ADDRESS>:8201", tls: "enabled")
           Log Level: debug
               Mlock: supported: true, enabled: true
             Storage: etcd (HA available)
             Version: Vault v0.10.3
         Version Sha: c69ae68faf2bf7fc1d78e3ec62655696a07454c7

==> Vault server started! Log data will stream in below:
2018-08-22T12:34:54.724Z [DEBUG] storage.cache: creating LRU cache: size=0
2018-08-22T12:34:54.754Z [DEBUG] cluster listener addresses synthesized: cluster_addresses=[<IP_ADDRESS>:8201]
2018-08-22T12:34:56.061Z [DEBUG] core: cannot unseal, not enough keys: keys=1 threshold=3 nonce=f466e0ad-52e4-c943-8ca5-a270c7b5f261
2018-08-22T12:34:56.101Z [DEBUG] core: cannot unseal, not enough keys: keys=2 threshold=3 nonce=f466e0ad-52e4-c943-8ca5-a270c7b5f261
2018-08-22T12:34:56.203Z [INFO ] core: vault is unsealed
2018-08-22T12:34:56.203Z [INFO ] core: entering standby mode
2018-08-22T12:34:58.736Z [DEBUG] core: parsing information for new active node: active_cluster_addr=https://vault.default:8201 active_redirect_addr=https://vault.default:8200
2018-08-22T12:34:58.736Z [DEBUG] core: refreshing forwarding connection
2018-08-22T12:34:58.736Z [DEBUG] core: clearing forwarding clients
2018-08-22T12:34:58.736Z [DEBUG] core: done clearing forwarding clients
2018-08-22T12:34:58.736Z [DEBUG] core: done refreshing forwarding connection
2018-08-22T12:34:58.736Z [DEBUG] core: creating rpc dialer: host=fw-173b1df9-cd0f-54bf-1ecc-8b2904e9f9f6
2018-08-22T12:34:58.777Z [DEBUG] core: forwarding: error sending echo request to active node: error="rpc error: code = Unavailable desc = all SubConns are in TransientFailure"
2018-08-22T12:34:59.736Z [DEBUG] core: creating rpc dialer: host=fw-173b1df9-cd0f-54bf-1ecc-8b2904e9f9f6
2018-08-22T12:35:01.206Z [DEBUG] core: creating rpc dialer: host=fw-173b1df9-cd0f-54bf-1ecc-8b2904e9f9f6
2018-08-22T12:35:03.736Z [DEBUG] core: forwarding: error sending echo request to active node: error="rpc error: code = Unavailable desc = all SubConns are in TransientFailure"
2018-08-22T12:35:04.036Z [DEBUG] core: creating rpc dialer: host=fw-173b1df9-cd0f-54bf-1ecc-8b2904e9f9f6
2018-08-22T12:35:07.553Z [DEBUG] core: creating rpc dialer: host=fw-173b1df9-cd0f-54bf-1ecc-8b2904e9f9f6
2018-08-22T12:35:08.736Z [DEBUG] core: forwarding: error sending echo request to active node: error="rpc error: code = Unavailable desc = all SubConns are in TransientFailure"
2018-08-22T12:35:13.736Z [DEBUG] core: forwarding: error sending echo request to active node: error="rpc error: code = Unavailable desc = all SubConns are in TransientFailure"
2018-08-22T12:35:15.249Z [DEBUG] core: creating rpc dialer: host=fw-173b1df9-cd0f-54bf-1ecc-8b2904e9f9f6
2018-08-22T12:35:18.736Z [DEBUG] core: forwarding: error sending echo request to active node: error="rpc error: code = Unavailable desc = all SubConns are in TransientFailure"
2018-08-22T12:35:23.736Z [DEBUG] core: forwarding: error sending echo request to active node: error="rpc error: code = Unavailable desc = all SubConns are in TransientFailure"
2018-08-22T12:35:23.786Z [DEBUG] core: creating rpc dialer: host=fw-173b1df9-cd0f-54bf-1ecc-8b2904e9f9f6
2018-08-22T12:35:28.736Z [DEBUG] core: forwarding: error sending echo request to active node: error="rpc error: code = Unavailable desc = all SubConns are in TransientFailure"
2018-08-22T12:35:33.736Z [DEBUG] core: forwarding: error sending echo request to active node: error="rpc error: code = Unavailable desc = all SubConns are in TransientFailure"
2018-08-22T12:35:38.736Z [DEBUG] core: forwarding: error sending echo request to active node: error="rpc error: code = Unavailable desc = all SubConns are in TransientFailure"
2018-08-22T12:35:43.736Z [DEBUG] core: forwarding: error sending echo request to active node: error="rpc error: code = Unavailable desc = all SubConns are in TransientFailure"

Could you please paste the definition of the Vault StatelfulSet in YAML format?

apiVersion: apps/v1
kind: StatefulSet
metadata:
  creationTimestamp: 2018-08-22T13:47:47Z
  generation: 1
  name: vault
  namespace: secrets
  ownerReferences:
  - apiVersion: vault.banzaicloud.com/v1alpha1
    controller: true
    kind: Vault
    name: vault
    uid: f29a5963-a611-11e8-89cd-0a27cf95a454
  resourceVersion: "6258782"
  selfLink: /apis/apps/v1/namespaces/secrets/statefulsets/vault
  uid: f425c05d-a611-11e8-8625-0ebf78f1340e
spec:
  podManagementPolicy: OrderedReady
  replicas: 3
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      app: vault
      vault_cr: vault
  serviceName: ""
  template:
    metadata:
      creationTimestamp: null
      labels:
        app: vault
        vault_cr: vault
    spec:
      containers:
      - args:
        - server
        - -log-level=debug
        env:
        - name: VAULT_LOCAL_CONFIG
          value: '{"api_addr":"https://vault.default:8200","listener":{"tcp":{"address":"<IP_ADDRESS>:8200","tls_cert_file":"/vault/tls/server.crt","tls_key_file":"/vault/tls/server.key"}},"storage":{"etcd":{"address":"https://etcd-cluster:2379","ha_enabled":"true","tls_ca_file":"/etcd/tls/etcd-client-ca.crt","tls_cert_file":"/etcd/tls/etcd-client.crt","tls_key_file":"/etcd/tls/etcd-client.key"}},"ui":true}'
        - name: VAULT_CACERT
          value: /vault/tls/ca.crt
        - name: AWS_SHARED_CREDENTIALS_FILE
          value: /etc/aws/credentials
        image: vault:0.10.3
        imagePullPolicy: IfNotPresent
        livenessProbe:
          failureThreshold: 3
          httpGet:
            path: /v1/sys/init
            port: api-port
            scheme: HTTPS
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 1
        name: vault
        ports:
        - containerPort: 8200
          name: api-port
          protocol: TCP
        - containerPort: 8201
          name: cluster-port
          protocol: TCP
        readinessProbe:
          failureThreshold: 3
          httpGet:
            path: /v1/sys/health
            port: api-port
            scheme: HTTPS
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 1
        resources: {}
        securityContext:
          capabilities:
            add:
            - IPC_LOCK
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /vault/config
          name: vault-config
        - mountPath: /vault/file
          name: vault-file
        - mountPath: /vault/tls
          name: vault-tls
        - mountPath: /etc/aws/credentials
          name: aws-cred
          subPath: credentials
        - mountPath: /etcd/tls
          name: etcd-tls
      - args:
        - --mode
        - aws-kms-s3
        - --aws-kms-key-id
        - f2fa72dd-80d1-4a8a-ab42-b648af9392da
        - --aws-kms-region
        - us-east-1
        - --aws-s3-bucket
        - vault-key-bucket-dev
        - --aws-s3-prefix
        - ""
        - --aws-s3-region
        - us-east-1
        command:
        - bank-vaults
        - unseal
        - --init
        env:
        - name: K8S_OWNER_REFERENCE
          value: '{"apiVersion":"vault.banzaicloud.com/v1alpha1","kind":"Vault","name":"vault","uid":"f29a5963-a611-11e8-89cd-0a27cf95a454","controller":true}'
        - name: VAULT_CACERT
          value: /vault/tls/ca.crt
        - name: AWS_SHARED_CREDENTIALS_FILE
          value: /etc/aws/credentials
        image: banzaicloud/bank-vaults:master
        imagePullPolicy: IfNotPresent
        name: bank-vaults
        resources: {}
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /vault/tls
          name: vault-tls
        - mountPath: /etc/aws/credentials
          name: aws-cred
          subPath: credentials
      dnsPolicy: ClusterFirst
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext: {}
      terminationGracePeriodSeconds: 30
      volumes:
      - emptyDir: {}
        name: vault-config
      - emptyDir: {}
        name: vault-file
      - name: vault-tls
        secret:
          defaultMode: 420
          secretName: vault-tls
      - name: aws-cred
        secret:
          defaultMode: 420
          secretName: aws-cred
      - name: etcd-tls
        secret:
          defaultMode: 420
          secretName: etcd-cluster-tls
  updateStrategy:
    rollingUpdate:
      partition: 0
    type: RollingUpdate
status:
  collisionCount: 0
  currentReplicas: 2
  currentRevision: vault-7c6687958f
  observedGeneration: 1
  readyReplicas: 1
  replicas: 2
  updateRevision: vault-7c6687958f

Looks correct what the operator has generated. Is the <IP_ADDRESS> IP the address of the other Vault instance?

Ah yeah, you are in the secrets namespace but the configuration uses the default namespace:
https://vault.default:8200

@bonifaido Ah, let me try changing the api address and deploy. Will let you know.

@bonifaido Apologizes, for the late response.
We are still seeing the TLS and rpc error with the namespace change
Vault-Standby Pod
2018-08-26T16:28:50.588Z [DEBUG] storage.cache: creating LRU cache: size=0
2018-08-26T16:28:50.607Z [DEBUG] cluster listener addresses synthesized: cluster_addresses=[<IP_ADDRESS>:8201]
2018-08-26T16:28:50.948Z [DEBUG] core: cannot unseal, not enough keys: keys=1 threshold=3 nonce=71b8b28f-9a39-0529-c193-3aca705ca4cd
2018-08-26T16:28:50.973Z [DEBUG] core: cannot unseal, not enough keys: keys=2 threshold=3 nonce=71b8b28f-9a39-0529-c193-3aca705ca4cd
2018-08-26T16:28:51.001Z [INFO ] core: vault is unsealed
2018-08-26T16:28:51.001Z [INFO ] core: entering standby mode
2018-08-26T16:28:53.515Z [DEBUG] core: parsing information for new active node: active_cluster_addr=https://vault.secrets:8201 active_redirect_addr=https://vault.secrets:8200
2018-08-26T16:28:53.515Z [DEBUG] core: refreshing forwarding connection
2018-08-26T16:28:53.515Z [DEBUG] core: clearing forwarding clients
2018-08-26T16:28:53.515Z [DEBUG] core: done clearing forwarding clients
2018-08-26T16:28:53.515Z [DEBUG] core: done refreshing forwarding connection
2018-08-26T16:28:53.515Z [DEBUG] core: creating rpc dialer: host=fw-1216dc66-630d-2c5f-60e9-9adf79a371d0
2018-08-27T20:13:20.516Z [DEBUG] core: forwarding: error sending echo request to active node: error="rpc error: code = DeadlineExceeded desc = context deadline exceeded"
2018-08-27T20:13:30.516Z [DEBUG] core: forwarding: error sending echo request to active node: error="rpc error: code = DeadlineExceeded desc = context deadline exceeded"
2018-08-27T20:13:36.960Z [ERROR] core: barrier init check failed: error="failed to check for initialization: context deadline exceeded"
Vault-Active Pod
2018-08-27 11:21:53.929551 I | http: TLS handshake error from <IP_ADDRESS>:60088: EOF
2018-08-27 11:22:03.925257 I | http: TLS handshake error from <IP_ADDRESS>:60102: EOF
2018-08-27 11:22:14.188470 I | http: TLS handshake error from <IP_ADDRESS>:60108: EOF
2018-08-27 11:22:23.939882 I | http: TLS handshake error from <IP_ADDRESS>:60116: EOF
2018-08-27 11:22:33.940579 I | http: TLS handshake error from <IP_ADDRESS>:60124: EOF
2018-08-27 11:22:43.925792 I | http: TLS handshake error from <IP_ADDRESS>:60138: EOF
2018-08-27T11:22:44.951Z [DEBUG] rollback: attempting rollback: path=auth/aws/
2018-08-27T11:22:44.951Z [DEBUG] rollback: attempting rollback: path=secret/
2018-08-27T11:22:44.951Z [DEBUG] rollback: attempting rollback: path=sys/
2018-08-27T11:22:44.951Z [DEBUG] rollback: attempting rollback: path=identity/
2018-08-27T11:22:44.951Z [DEBUG] rollback: attempting rollback: path=cubbyhole/
2018-08-27T11:22:44.952Z [DEBUG] rollback: attempting rollback: path=aws/
2018-08-27T11:22:44.952Z [DEBUG] rollback: attempting rollback: path=auth/token/

Looks like the EOF errors are repeating every 10 seconds, we need to find out what is causing that. I'm trying to reproduce this on AWS.
There is a similar issue opened up for Vault: https://github.com/hashicorp/vault/issues/3847

I have created the same setup here in our AWS account, I try to reproduce the issue, it took almost one day - seeing from your logs - to get this error, so I will come back with some details tomorrow:
2018-08-27T20:13:20.516Z [DEBUG] core: forwarding: error sending echo request to active node: error="rpc error: code = DeadlineExceeded desc = context deadline exceeded"```

@bonifaido Yes, I found the issue and it is still open without any active threads. Also, we started seeing this issue exactly after a day Vault cluster is stood up. Once again, thanks for looking into this.
However, We will try analyzing from our end as well.

@gowthamsubbu in my two node AWS setup that was created on Monday I couldn't reproduce the issue. Could you please:

list vault pods with their node IPs kubectl get pods -o wide -l app=vault
make sure that communication between the nodes is opened in AWS sec groups on port 8200 and 8201 (the Vault service ports)
Send all the logs of both Vault instances

@bonifaido I already made sure the ports are open between both pods. Can you specify the exact log. Vault pod logs or from EC2 instance ?

Vault pod logs please, both instances.

@bonifaido As per the following line, we are generating CA, server and client TLS certificate which will be expire after 8760h = 365 days.
Is there a plan in place to renew the expired certificate ? Currently, deploying Vault will generate a new certificate and kubernetes secrets (vault-tls), which is mounted as a volume to be used as tls-server and tls-server-key.
It looks like re-deploying Vault is the only way to achieve this without any manual intervention. Please confirm.
https://github.com/banzaicloud/bank-vaults/blob/master/operator/pkg/stub/handler.go#L246

@bonifaido Thank you !

Hi @gowthamsubbu, implementation for this has been started in #159, please follow up that issue for more details. It still needs more work but we are on track.


possibile to use on a esp8266?

is there a specific reason for the esp32? or can it also work on the esp8266?
thanks !

the ESP32 hat three hardware serial ports while the 8266 only has one.


Upgrading to bootstrap5 #4602

Fixes Issue #4602
Describe the changes you have made in this PR:

Migrated the project from Bootstrap 4 to Bootstrap 5.
Updated Classes and Attributes: Replaced deprecated Bootstrap 4 classes (e.g., .jumbotron, .media, .ml-auto, .float-right) with their Bootstrap 5 equivalents or updated utility classes.
Data Attribute Renaming: Updated data attributes such as data-toggle and data-target to the new Bootstrap 5 format.
Bootstrap CDN Links: Replaced any Bootstrap v4 CDN links with the latest Bootstrap v5 versions.
Utility Class Adjustments: Improved layout and spacing with Bootstrap 5’s updated utility classes.
Fixed all major layout bugs visible.

( PLEASE FIND ATTACHED VIDEO OF THE WEBSITE AFTER MIGRATION )
This is my second iteration of the PR, addressing all the issues that surfaced during the Bootstrap 4 to 5 migration. I’m grateful for the guidance so far and eager to hear your thoughts on these fixes.
Thank you for the continued support and feedback,
Aditya Singh
cc: @tachyons @tanmoysrt
https://github.com/user-attachments/assets/15d2f354-a486-444d-8ef9-8049bf4f36a6

Summary by CodeRabbit
Release Notes

New Features

Updated UI components to align with Bootstrap 5 standards, enhancing overall styling and responsiveness.
Introduced a new zoom slider section in the CSS for improved functionality.

Bug Fixes

Corrected class names and attributes across various components to ensure proper functionality and styling.

Documentation

Updated HTML structure and class names in multiple views to reflect the latest framework conventions.

Chores

Updated dependencies in package.json to the latest versions of Bootstrap and Popper.js.
Refined CSS structure for better maintainability and responsiveness.

@salmoneatenbybear It seems that you accidentally added changes to git sub module on this PR and it causing CI to fail. Also could you check the issues raised by the coder rabbit ? Great job so far

@tachyons absolutely will look into it, thankyou

@tachyons I have reset the submodule changes, and updated the PR.

@tachyons I have looked into the changes suggested by coder rabbit and made those changes aswell, please review if you get time.

@tachyons I have tried to go to an earlier hash and hard reset from there in order to reinstate the sub modules, i haven't changed much in there just updated the QuickButtonMobile.vue and QuickButton.vue so that the ui remains stable across all devices, I am not sure why the CI keeps failing.

CI is failing because of this
Try https://how.wtf/reverting-changes-to-git-submodules.html

 CI is failing because of this
Try https://how.wtf/reverting-changes-to-git-submodules.html

Have tried to resolve by reverting the changes

@salmoneatenbybear specs are failing for groups, could you check that as well ? Like adding and removing members to the group ?

@salmoneatenbybear specs are failing for groups, could you check that as well ? Like adding and removing members to the group ?

Sure absolutely, will do that asap

@tachyons so i figured out why one of the CI checks was failing ( rest which were failing before due to the submodule changes are resolved ), its failing because :

The "delete" button (groups-assignment-delete-button) is missing from the assignment views.
There are parameter issues like an empty or missing group param, causing the tests to fail.

i havent made any changes related to this in this pr so i am not sure why this is occuring, i can try to fix this but for that i will need to add the missing "delete" button in the show.html.erb file under the mentor access section and link it to the destroy action.

It could be related to bootstrap JavaScript. Try if the feature works on
your branch like in the master branch
On Mon, 21 Oct, 2024, 3:35 pm Aditya Singh, @.***>
wrote:

@tachyons https://github.com/tachyons so i figured out why one of the
CI checks was failing ( rest which were failing before due to the submodule
changes are resolved ), its failing because :

The "delete" button (groups-assignment-delete-button) is missing
from the assignment views.
There are parameter issues like an empty or missing group param,
causing the tests to fail.

i havent made any changes related to this in this pr so i am not sure why
this is occuring, i can try to fix this but for that i will need to add the
missing "delete" button in the show.html.erb file under the mentor access
section and link it to the destroy action.
—
Reply to this email directly, view it on GitHub
https://github.com/CircuitVerse/CircuitVerse/pull/5117#issuecomment-2426218350,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXYAEB7YXKEHTR2J2UTPUTZ4TGYJAVCNFSM6AAAAABQIM4CJ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRWGIYTQMZVGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

It could be related to bootstrap JavaScript. Try if the feature works on
your branch like in the master branch
On Mon, 21 Oct, 2024, 3:35 pm Aditya Singh, @.***>
wrote:

@tachyons https://github.com/tachyons so i figured out why one of the
CI checks was failing ( rest which were failing before due to the submodule
changes are resolved ), its failing because :

The "delete" button (groups-assignment-delete-button) is missing
from the assignment views.
There are parameter issues like an empty or missing group param,
causing the tests to fail.

i havent made any changes related to this in this pr so i am not sure why
this is occuring, i can try to fix this but for that i will need to add the
missing "delete" button in the show.html.erb file under the mentor access
section and link it to the destroy action.
—
Reply to this email directly, view it on GitHub
https://github.com/CircuitVerse/CircuitVerse/pull/5117#issuecomment-2426218350,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXYAEB7YXKEHTR2J2UTPUTZ4TGYJAVCNFSM6AAAAABQIM4CJ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRWGIYTQMZVGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Alright I will try it and keep you updated.

@tachyons CI is failing due to Capybara not finding elements on the page and missing parameters, trying to fix them...

@tachyons the CI was failing beacause capybara is trying to find the bootstrap 4 id which has been changed when migrating to bootstrap 5, so the tests need to be changed with the appropriate bootstrap 5 id which i replaced the bootstrap 4 ids with, should i make the changed to the tests ?

Yes please

@tachyons pls review if you find time. Thankyou!

I have reset the apidoc file,
removed the whitespace
and also removed the package.json.save from the changes.
if anything else needs changes, updates/modifications, etc; pls do let me know, would be happy to make them.
Thankyou for your guidance @tachyons

Could you address the open issues raised by the @coderabbit ?

Could you address the open issues raised by the @coderabbit ?

Sure absolutely, will do that

@tachyons
The ruby on rails test CI failure seems to be caused by GitHub's permission restrictions on workflows triggered from forked repositories.
Specifically, the reviewdog tool in the CI pipeline requires write permissions to post review comments on pull requests. However, when a PR comes from a fork (like mine), GitHub limits the GITHUB_TOKEN permissions for security reasons, leading to a 403 Resource not accessible by integration error.
I believe this is why the CI check failed, not due to issues with the code itself. Could you please advise on how we should proceed? I'm happy to make any necessary adjustments.
Thank you for your time and guidance.

@tachyons I have closed this PR due to the submodule issue which was causing the CI to fail, i will be creating a new PR with the same changes so that the CI passes.

superseded by #5135


Add localization for group leave dialog

When trying to leave a group on the index page, one is asked "Are you sure?". This should also be localized for our deutschen friends

now tracked in #341


Creating unit test for fine-tuning

The unit test should check for

Correct architectural modifications between pretrained and fine-tuning model
Correct (un)freezing in the fine-tuning training

Check following:

Gradients enabled/disabled for (un)frozen layers
Continuous training curve when stopping & restarting training
Context switcheng between IPU/GPU


Align project general settings with settings combo switcher

From this:

To:

+1

6.4.x: b71513f56e0b5998d632696de171d1012e842e66


CAMEL-21269: camel-langchain4j-tokenizer fixes for the YAML DSL

This is a more more comprehensive fix for the tokenizer support for the YAML DSL.  There were quite a few problems in the model files that prevented it from being used with YAML (thus affecting any sub-project or project relying on this).
Although it's relatively big due to the regen of a few files, all the changes are backwards compatible and anyone using it with the Java DSL should not have to change any code.

You should also ping @mgubaidullin as it can affect Camel Karavan

You should also ping @mgubaidullin as it can affect Camel Karavan

Absolutely. I couldn't reproduce w/ the existing version of Karavan, but even if it got everything correctly, the generated YAML would still be wrong.
It's on my TODO list for next week to figure out if/how Karavan is affected so I can pinpoint exactly where/how we need to fix any code relying on the incorrect model.

I've just confirmed that the YAML itself is functional. Now I'll work with the users / tooling creators to make sure they can leverage the new EIP.
Let's merge this to make it easily available for others.


[Snyk] Security upgrade php from 8.2-cli-alpine to 8.0-cli-alpine

This PR was automatically created by Snyk using the credentials of a real user.Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Changes included in this PR

alpine-3.17/php/cli/Dockerfile

We recommend upgrading to php:8.0-cli-alpine, as this image has only 0 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Requested change will downgrade PHP to 8.0, rejecting.


Support for out of the box $custom-colors variable being merged with $theme-colors map

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I have read the contributing guidelines

Proposal
Following the Customize Sass documentation regarding Importing and Add to map to add a custom theme color one should do:
// 1. Include functions first (so you can manipulate colors, SVGs, calc, etc)
@import "bootstrap/scss/functions";

// 2. Include any default variable overrides here

$violet:  #7F00FF;

// 3. Include remainder of required Bootstrap stylesheets (including any separate color mode stylesheets)
@import "bootstrap/scss/variables";
@import "bootstrap/scss/variables-dark";

// 4. Include any default map overrides here

$custom-colors: (
  "violet": $violet
);

$theme-colors: map-merge($theme-colors, $custom-colors);

It would be nice if BS internally would define an empty $custom-colors map and merge that already with $theme-colors.
As it would be empty it causes no difference with current behaviour.
Except it would be much easier for users to add custom theme colors, as it would effectively reduce above code to:
// 1. Include functions first (so you can manipulate colors, SVGs, calc, etc)
@import "bootstrap/scss/functions";

// 2. Include any default variable overrides here

$violet:  #7F00FF;

$custom-colors: (
  "violet": $violet
);

// 3. Include remainder of required Bootstrap stylesheets (including any separate color mode stylesheets)
@import "bootstrap/scss/variables";
@import "bootstrap/scss/variables-dark";

// 4. Include any default map overrides here

// Nothing needed here as BS will automatically merge the $custom-colors into the @theme-colors.

Motivation and context
Making it easier for users customizing the Sass to add custom theme colors.

Thanks for creating this feature request @marceloverdijk
This is an interesting idea that we could study more in-depth for v5.4 (as it could be implemented without breaking anything in v5). I've added to the v5.4 project to analyze after our v5.3.x patches.

Yeah this is a solid idea, thanks for suggesting it!


Go 1.16.5 and 1.15.13 has been released

https://golang.org/doc/devel/release.html#go1.16.minor
go1.16.5 (released 2021-06-03) includes security fixes to the archive/zip, math/big, net, and net/http/httputil packages, as well as bug fixes to the linker, the go command, and the net/http package. See the Go 1.16.5 milestone on our issue tracker for details.
https://golang.org/doc/devel/release.html#go1.15.minor
go1.15.13 (released 2021-06-03) includes security fixes to the archive/zip, math/big, net, and net/http/httputil packages, as well as bug fixes to the linker, the go command, and the math/big and net/http packages. See the Go 1.15.13 milestone on our issue tracker for details.

Fixed upstream, thanks 🤝

Sure! 😀


Adding documentation example using the new SuperClusterViewportAlgorithm

Adds documentation for #640

Thank you for following up by adding this example, @mwaddell.


CyberTiger (U) - hangs at boot

CyberTiger (U) - 14E0635CCC2A80C77FD0A888A2E7977C55C6E129
This game hangs at the boot.
Tested on the latest version of Gadolinium on Windows 10.

Update: same as CyberTiger (E)


bdd-spring-1557161934 to 0.0.1

Promote bdd-spring-1557161934 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


the problem of netty dropping?

1: network environment： 4G mobile card
2: gateway environment： Linux
3: problem:
The gateway has 7000 long links of industrial control. If 2000 industrial control units are added to the gateway, more than 2000 industrial control units will be offline and then continue to be online.（网关有7000台工控长链接，在加入2000台工控，会导致大于2000台工控下线，然后在持续上线。）

sorry but without any more details it is impossible to give you any help.


Define types, tasks, variants and states

TODO

[ ] Define types, tasks, variants and states using the pattern inventory

Outcomes

Have clearly defined types, tasks, variants and states based current component implementation

Deliverables

Type, task, variant, and state options for the skip to content component filled out in the model and style requirements document

Estimated Effort

[ ] XS: 1 to 2 hours
[ ] S: half a day
[ ] M: 1-2 day
[ ] L: 1 week
[ ] XL: Move to an epic

Not relevant to this component


Add Transport class to do http request

A few code style things but a couple of important functional issues as well.

Thinking about process shutdown is really import
I think we need to look at the queuing design taking into account that the server might be logging on behalf of multiple client devices.

I got the 1st one. What's the concern for the 2nd one? Could you explain more?

The second point is related to this comment: https://github.com/amplitude/Amplitude-Node/pull/8#discussion_r437096071
When we send events to the API it's important that we send them in order for each device id. On client SDKs that's simple because all the events belong to that device id. For a server SDK we will probably be sending events for lots of different device ids. Some of those device ids might get throttled so we'll need to queue up events for them. While this is happening we shouldn't hold up events that are being logged on different device ids.

Some of those device ids might get throttled so we'll need to queue up events for them. While this is happening we shouldn't hold up events that are being logged on different device ids.

Our backend throttle the event payload based on deviceId?
Let's say my payload contains events from different deviceIds. One deviceId gets throttled, and the whole payload won't be submitted?

I don't know. Perhaps?


Autoscroll not working at all with Iron Router

I cannot get any command, any package, or this package, to allow me to scroll to the top. Even through the console. Any ideas?

Same here. Doesn't work.

I just tried it, seems to work with Meteor 1.2.1 and the latest iron:router. Are there any errors? What versions are you using?

@chriskgregory @zulhfreelancer I just tested again with a couple simple apps, it seems to work just fine. I'm closing this issue for now.
If you could please include a sample app reproduction, feel free to reopen this issue, and I'll be glad to help solve it!


div

Challenge http://freecodecamp.com/challenges/waypoint-give-a-background-color-to-a-div-element has an issue. Please describe how to reproduce it, and include links to screenshots if possible.
.background-color{
background-color:gray;
}

Closing. Please feel free to re-open with steps to reproduce the issue.
Happy Coding!

@mwandama you first need to give your div the class of gray-background
<div class="gray-background"
then you need to work with css
.gray-background{
    background-color:gray;
  }

I tried what you have shown me defining the <div class as you have shown me it didn't work

@mwandama you have to check your css class too, in the description above, you gave the wrong class name

I am trying to give a background color to a  element. What i did worked and it changed the background color to "silver" as it was supposed to. yet it tells me it is wrong. my code is below: help please?

CatPhotoApp
Click here for cat photos.

Things cats love:

cat nip
laser pointers
lasagna

Top 3 things cats hate:

flea treatment
thunder
other cats

 Indoor
 Outdoor
 Loving
 Lazy
 Energetic

Submit

The issue tracker is for reporting bugs only. If this is an issue for help with a challenge, please use the help chat room or try looking through the forum for help with a specific challenge.
Happy Coding.


matTextareaAutosize gets focus on initialization

Bug, feature request, or proposal:
Textarea with matTextareaAutozize directive gets the focus on initialization.
What is the expected behavior?
It should not get focus if it is not explicitly focused.
What is the current behavior?
It is now focused during initialization. This for example breaks the ng-touched/ng-untouched classes and therefore validation behavior.
What are the steps to reproduce?
https://stackblitz.com/edit/angular-r4nqhk?file=app/input-overview-example.html
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 6.0.2
Angular Material 6.1.0
Is there anything else we should know?
Only reproducible on Safari (both desktop/mobile), Edge, IE11

Probably a duplicate of https://github.com/angular/material2/issues/11308
However the affected user base seems to be bigger as initially described, if this is not only iOS.


Atomic select

Here's some select markup that goes with https://github.com/cfpb/capital-framework/pull/372

Question for the cf code, should the disabled version have the pacific outline when hovering? Disabled inputs get no hover state at all.
Other than that, this looks good to me 👍

@jimmynotjim there's no note about this in the design manual doc i have, but agree it probably shouldn't have it. i'll make a new PR for that in CF.


Added 28100 port to fix CSM UI for OVA 1.0.4

Describe your changes in brief
Added 28100 port to fix CSM UI for OVA 1.0.4

@mukul-seagate11 Seems this file is a generic one. Should we explicitly mention to use 28100 port for OVA 1.0.4

addressed via Note


Label tag with htmlFor prop dont't work together with Checkbox component

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Use a label tag to check a Checkbox using a htmlFor prop.
Current Behavior

Id isn't rendered in Checkbox, so when I click in a label the checkbox don't get marked.
Steps to Reproduce (for bugs)

https://codesandbox.io/s/v1m6jxwmo7
Your Environment

Tech
Version

Material-UI
1.0.0-beta.29

React
16

browser
Chrome 16

/claim

/claim I would like to be assigned this issue thank you

@nharrisanalyst Feel free to submit a pull-request :).

@oliviertassinari thanks for the feedback, I would like to solve this. My main ideia is to apply id in input only when is a checkbox/radio/switch.


Use a namespace for the classes

Currently there is no namespace, that's a little annoying. I will change that once I have time.
Any suggestion for the namespace's name is welcome.

Fixed by commit f4bf0688a7e7a7fdb50b0ac48a70ba413349a69a


Bug: 'apollo-server-plugin-base' module is not used in Apollo server v4, but required by newrelic

The requirement of the apollo-server-plugin-base module ends with a typescript error during compilation.
Description
apollo-server-plugin-base module is not used in Apollo Server v4 (see https://www.apollographql.com/docs/apollo-server/migration/#packages-merged-into-apolloserver ), but https://github.com/newrelic/newrelic-node-apollo-server-plugin/blob/v2.1.0/index.d.ts#L1 still tries to import it. And it ends with a typescript error during compilation.

Expected Behavior
Do not use the deprecated apollo-server-plugin-base module.
Env
@newrelic/apollo-server-plugin version 2.1.0
@apollo/server version 4.3.0

Hi @dhlavaty take a look at the release notes for 2.1.0.  For apollo 4 typescript users you have to use the plugin in a different way

I use @newrelic/apollo-server-plugin exactly as in the release notes.
Typescript's Module Resolution picks the index.d.ts file automatically. That is Typescript's default behavior. And because index.d.ts (as you can see) imports apollo-server-plugin-base, which is not a dependency nor peerDependency, it reports it as an error (absolutely correctly in my humble opinion).
So I have several options how to deal with it:

modify typescript's compilerOptions in tsconfig.json
use typescripts path mapping
use another creative workaround
install deprecated apollo-server-plugin-base as my project's dependency, even though it is not used/needed by Apollo v4

....but still, all mentioned above are just workarounds to an existing problem.
Actually, number 4 is the workaround I have chosen to use for now.

@dhlavaty this example app shows not needing to install apollo-server-plugin-base.  I'm interested if this works for you. there's not workarounds that you mentioned as far as i can tell.  We had this report a few months ago and we thought we had addressed.

Hi @bizob2828 , any progress on this one? our team also blocked by this issue


Can't get any prompt from System Preferences

I just installed yabai with homebrew but when i'm trying to start it with the command yabai --start-service nothing happen. I can't get any pop up from System Preferences.
I have also partially disable SIP
I'm on Mac OS Sonoma 14.2.1, Macbook Pro 16 M1 Max

sudo yabai --load-sa

unfortunately it didn't work, I ran the command and the desktop went momentarily black, I then ran the command to start yabai but it got stuck again with no pop-up. I tried running your command again and now I have this error yabai: missing required nvram boot-arg '-arm64e_preview_abi'!

Thank you but SIP is already disabled (as you can see in the video).When I try to start yabaii, it doesn't ask me for permission in accessibility, and gets stuck. Is there any way to manually add the path?
I also tried the command yabaii --load-sa but it gives me the error from beforeyabai: missing required nvram boot-arg '-arm64e_preview_abi'!

nvram: Error getting variable - 'boot-args': (iokit/common) data was not found
I'm on Sonoma 14.2.1, M1 Max

Yes i'm sorry i was missing the sudo nvram boot-args=-arm64e_preview_abi but didn't fix
I also configured the scripting addon https://github.com/koekeishiya/yabai/wiki/Installing-yabai-(latest-release)#configure-scripting-addition but still the same, when i run yabai --start-service nothing happen.
There's a way to manually add the path to accessibility?

Thank you so much! It worked!
I think the key was
sudo yabai --uninstall-sa
yabai --uninstall-service


Resolved docker version 23.0 issue

Previous Line 90 of buildContainerImage.sh will work for all docker versions before 23.0. Min version of docker as per code is 17.09, which is converted to 1709 by the code before comparison. For versions before 23.0, taking 5 letters works. But from docker version 23.0 onwards, 23.0.0, 23.0.1, etc. are converted to 23.0. (when 1st 5 letters are taken) and it becomes 230 after removing the decimal point as per code logic. So, the comparison of 230 > 1709 fails. Removing printf "%.5s" will resolve this.

Looks like the lint check here is a false negative

Great, thanks a lot @yunus-qureshi and @aditya059.
@yunus-qureshi, do you have the list of issues that have been fixed with this PR or do we need to skim through them?

Thanks @gvenzl. We'll skim and close the issues and redunant PRs.

@yunus-qureshi, great, thank you!


Moves collecting telemetry to a separate process

Moves collecting telemetry to a separate process to improve CLI's performance and make collecting telemetry events non-blocking for the execution of CLI commands.

Seems like there's a tiny merge conflict here @waldekmastykarz. Could you have a look at it?

Will do 👍

Ready @milanholemans 💪

Merged manually, thanks for contributing, you rock! 😊🌶


Warning if the runsettings contains non supported element like datacollectors and logger inside the VSTestBridge

We should send a warning if in the runsettings there're section no more supported with a "we will ignore it" and the link to the website with the diff, same warning will end also in VS.

@MarcoRossignoli @nohwnd Do you think it's safe to also report on the RunConfiguration entries?

I would not, only notify that the sections will be ignored.


Private Encryption Error

Describe The Bug
Once a week, at least one device would be showing up with this error message and I can't seem to fix it as I suspect it being server-ended.
Expected behavior
Connect as usual without errors
Logs
[26/02/2024, 16:09:22] [TPLink Tapo Platform] Error sending command: deviceInfo TypeError: RSA_PKCS1_PADDING is no longer supported for private decryption, this can be reverted with --security-revert=CVE-2023-46809
at Object.privateDecrypt (node:internal/crypto/cipher:79:12)
at LegacyAPI.decodeHandshakeKey (/var/lib/homebridge/node_modules/homebridge-tp-link-tapo/src/api/LegacyAPI.ts:183:30)
at LegacyAPI.handshake (/var/lib/homebridge/node_modules/homebridge-tp-link-tapo/src/api/LegacyAPI.ts:173:30)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at LegacyAPI.sendSecureRequest (/var/lib/homebridge/node_modules/homebridge-tp-link-tapo/src/api/LegacyAPI.ts:83:7)
at LegacyAPI.login (/var/lib/homebridge/node_modules/homebridge-tp-link-tapo/src/api/LegacyAPI.ts:20:22)
at TPLink.sendCommandWithNoLock (/var/lib/homebridge/node_modules/homebridge-tp-link-tapo/src/api/TPLink.ts:208:9) {
code: 'ERR_INVALID_ARG_VALUE'
}
[26/02/2024, 16:09:22] [TPLink Tapo Platform] Failed to get info about: <IP_ADDRESS>
Plugin Config
{
"bridge": {
"name": "Homebridge 547C",
"username": "0E:1A:5E:16:54:7C",
"port": 51618,
"pin": "354-64-223",
"advertiser": "bonjour-hap"
},
"accessories": [],
"platforms": [
{
"name": "Config",
"port": 8581,
"auth": "form",
"theme": "deep-purple",
"tempUnits": "c",
"lang": "auto",
"platform": "config"
},
{
"name": "TplinkSmarthome",
"addCustomCharacteristics": true,
"deviceTypes": [
"plug",
"bulb"
],
"platform": "TplinkSmarthome"
},
{
"addresses": [
"<IP_ADDRESS>",
"<IP_ADDRESS>",
"<IP_ADDRESS>"
],
"name": "TPLink Tapo Platform",
"platform": "HomebridgeTPLinkTapo"
},
{
"devices": [
{
"name": "Mi Air Purifier 2H",
"ip": "<IP_ADDRESS>",
"token": "5ecdb9d87ec3055d7db203cc5b2591ae",
"deviceId": "313063079",
"model": "zhimi.airpurifier.mc2",
"pollingInterval": 10,
"deepDebugLog": false,
"buzzerControl": true,
"ledControl": true,
"childLockControl": true,
"modeControl": true
},
{
"name": "Mi Wi-Fi Range Extender Pro",
"ip": "<IP_ADDRESS>",
"token": "9623e9045c5d6516ba0a8ef12d7618f7",
"deviceId": "352334985",
"model": "xiaomi.repeater.v3",
"pollingInterval": 10,
"deepDebugLog": false,
"buzzerControl": true,
"ledControl": true,
"childLockControl": true,
"modeControl": true
}
],
"platform": "miot"
},
{
"name": "TuyaWebPlatform",
"options": {
"username": "",
"password": "",
"countryCode": "61",
"platform": "smart_life"
},
"defaults": [
{
"device_type": "form"
}
],
"scenes": false,
"platform": "TuyaWebPlatform"
},
{
"cameras": [
{
"name": "Camera",
"ipAddress": "<IP_ADDRESS>",
"streamUser": "elias321",
"streamPassword": ""
}
],
"platform": "tapo-camera"
},
{
"platform": "BroadlinkRM",
"name": "Broadlink RM",
"hideScanFrequencyButton": false,
"hideLearnButton": false,
"hideWelcomeMessage": false,
"hosts": [
{
"address": "<IP_ADDRESS>",
"mac": "E8:16:56:1C:B4:63",
"isRFSupported": true,
"isRM4": true
}
],
"accessories": [
{
"name": "Bedroom TV",
"type": "tv",
"data": {
"on": "",
"off": "",
"volume": {
"up": "",
"down": ""
},
"inputs": [
{
"name": "HDMI 1",
"type": "hdmi",
"data": ""
},
{
"name": "HDMI 2",
"type": "hdmi",
"data": ""
}
],
"remote": {
"select": "",
"arrowUp": "",
"arrowDown": "",
"arrowLeft": "",
"arrowRight": "",
"playPause": "",
"info": "",
"back": "",
"options": "",
"digitalAnalog": "",
"programUp": "",
"programDown": "",
"nextTrack": "",
"previousTrack": ""
}
}
},
{
"name": "Moon Lamp",
"type": "light",
"defaultBrightness": 100,
"useLastKnownBrightness": false,
"data": {
"on": "",
"off": "",
"brightness100": "",
"brightness90": "",
"brightness80": "",
"brightness70": "",
"brightness60": "",
"brightness50": "",
"brightness40": "",
"brightness30": "",
"brightness20": "",
"brightness10": "",
"hue22.5": "",
"hue45": "",
"hue67.5": "",
"hue90": "",
"hue112.5": "",
"hue135": "",
"hue157.5": "",
"hue180": "",
"hue202.5": "",
"hue225": "",
"hue247.5": "",
"hue270": "",
"hue292.5": "",
"hue315": "",
"hue337.5": "",
"hue360": "***************"
},
"onDelay": 1,
"enableAutoOff": false,
"onDuration": 5,
"enableAutoOn": false,
"offDuration": 5
},
{
"name": "RM4 Thermometer",
"type": "temperatureSensor"
},
{
"name": "RM4 Humidity Sensor",
"type": "humiditySensor"
}
]
}
],
"disabledPlugins": [
"homebridge-camera-ui"
]
}
Plugin Version
v4.1.0
Homebridge Version
v1.7.0
Node.js Version
20.11.1
NPM Version
Not sure
Operating System
Not sure

Hello, I had this problem when uploading a version of a web application that uses Docker, it seems that on 02/14/2024 a fix was released on the node that does not allow RSA encryption with pkcs1 padding to be used, the simplest way to solve it is to run in the terminal a node --security-revert=CVE-2023-46809 that will remove this security rule...
https://nodejs.org/en/blog/vulnerability/february-2024-security-releases

Ahh I see. So it’s not possible to fix this on the actual Homebridge Tapo Plugin? Do you know the exact reason as to why they removed RSA encryption support?  I'll give it a spin and let you know how it goes. Thanks for the info.

It can't as Tapo is using old encryption

It’s strange because this issue only occurs with my H100 hub not with my other devices 🤷♀

Hello, I had this problem when uploading a version of a web application that uses Docker, it seems that on 02/14/2024 a fix was released on the node that does not allow RSA encryption with pkcs1 padding to be used, the simplest way to solve it is to run in the terminal a node --security-revert=CVE-2023-46809 that will remove this security rule...
Remembering that this is an ideal palliative solution and no longer use RSA encryption with pkcs1 padding
https://nodejs.org/en/blog/vulnerability/february-2024-security-releases

Hi - sorry, dumb question - do you know how I can apply the revert in Homebridge? I've tried in the HB console but it seems to take me to the REPL. I've tried this in settings > node_options but that didn't work. Yes, I've I've done a lot of searching but none of this has really helped... or should I just downgrade node? I'm sure it's really simple / obvious but it's eluding me! Thanks in advance.


No network connection after following all steps

Hi,
just found your work on boilerplate for sonoff.
Got a sonoff basic R2 and followed all the instructions, compiling and televersing went fine, achieved to connect on wifimanager then.
(Sonoff with fast green led blinking)
Then with all the infos needed ( SSID, password, Blynk token) and save done, the sonoff was slowly blynking and nothing more. impossible to make it connect to my wifi network. (and i'm sure about SSID and password, no mistake about it.)
If you have any idea of what I am missing.
Thnaks by advance and for all this suff :)

It seems I owned sonoff basic r2 with « sonoff rf r2 v1 0 » labelled on it with big black wires instead of soldered paths beneath. Dunno if it makes a difference

sorry i can't help, been out of this game for a while :|

I get:

ISR not in IRAM!
User exception ...

most likely on attaching interrupt.  Any clues how to solve it?


Client config builder methods

Closes #1122
Possible future tasks:

[ ] PolywrapClient probably shouldn't know about ClientConfigBuilder and shouldn't know about defaults. Add issue?

Should remove the noDefaults option within the constructor
PolywrapClient should just apply the config it's provided, not modify/add to it upon construction
Good separation of concerns, simpler client code.

Initial set of the ClientConfigBuilder methods.
Methods implemented:
Plugin methods
addPlugin(uri: string, plugin: PluginPackage)

Adds specified plugin registered under the uri. If a plugin already exists, overwrites it.
removePlugin(uri: string)

Removes the plugin registered under the uri.
Env methods
addEnv(uri: string, env: Record<string, unknown>)

Adds specified env registered under the uri. If an env is already registered under the uri, it performs a merge (currently using naive implementation - spread operator).
setEnv(uri: string, env: Record<string, unknown>)

Adds specified env registered under the uri if none exists. Otherwise, overwrites the env that is already registered under the uri.
removeEnv(uri: string)

Removes the env registered under the uri if one exists. Otherwise, does nothing.
InterfaceImplementation methods
addInterfaceImplementation(interfaceUri: Uri | string, implementationUri: Uri | string)

Adds the interfaceImplementationUri to the implementations collection for the specified interfaceUri. Creates the InterfaceImplementation if none exists for interfaceUri.
addInterfaceImplementations(interfaceUri: Uri | string, implementationUris: Array<Uri | string>)

Appends all interfaceImplementationUris to the the implementations collection for the specified interfaceUri. Creates the InterfaceImplementation if none exists for interfaceUri.
removeInterfaceImplementation(interfaceUri: Uri | string, implementationUri: Uri | string)

Removes the interfaceImplementationUri from the implementations collection for the specified interfaceUri. Removes the InterfaceImplementation if the implementations collection would remain empty.
UriRedirect methods
addUriRedirect(from: Uri | string, to: Uri | string)

Adds the specified UriRedirect. If an existing UriRedirect has the same from, overwrites it.
removeUriRedirect(from: Uri | string)

Removes the specified UriRedirect.
UriResolver methods
addUriResolver(resolver: UriResolver)

Adds the specified UriResolver to the end of the uriResolvers collection.
setUriResolvers(resolvers: UriResolver[])

Sets the uriResolvers collection to resolvers.

I'm onboard with all "future improvements" mentioned above!


Fix the IMAGE_TAG should be snapshot

Merging to fix the snapshot tag

Well, that was not great. Working on a revert + fix.


feat: support Firebase Remote Config

Is your feature request related to a problem? Please describe:

Firebase Remote Config is not currently supported.
Describe the solution you'd like:

Add a Firebase Remote Config plugin.
Describe alternatives you've considered:

Additional context:

+1

+1

it would be great to have this plugin

Anyone want to test the new plugin? I would like to get some feedback.
npm i<EMAIL_ADDRESS>
Docs: https://github.com/capawesome-team/capacitor-firebase/blob/feat/issue-9/packages/remote-config/README.md


add a compiletest for #18

@kpp am I missing something? This test shouldn't pass if #18 is a real error?

Thank you! Now it looks like you have handled all possible ui issues

Thank you @kpp for keeping your eyes open.


Fix bazel configuration

Set watchfs in the rc file to avoid server restart
(note than with 0.4.5 it can be set as non-startup option,
but keep it as startup option to stay compatible with
earlier version).
Add --nomaster_bazelrc to avoid having a RC file from
the host system compromise options.
Remove --package_path for long time unused.

looks good, merged, updated results. Thanks


Remove mandatory email requirement in Auto Email Report

Fixes https://github.com/DigiThinkIT/bloomstack/issues/292.

If this is not going back to Frappe then don't change this in Frappe. Hook it in.

But, but I asked you in chat, and you said it's fine.
Also, how do I hook this specific function? It's inside a class.

But, but I asked you in chat, and you said it's fine.
Also, how do I hook this specific function? It's inside a class.

er. I might have missed that. Add the validation in JS and hook that in?

There's multiple entry points for sending out the report, including daily and monthly hooks. I can override the button maybe, but it'll still fail when it gets no recipients from the hook.

Ya know what? Can you send this as a PR to Upstream and mention the use case? Tell that that we plan to do it properly soon as well. I'll merge this here for now.


fluxctl 1.21.2

Updating package fluxctl to release 1.21.2.
Release info
This patch release surfaces a notice from https://docs.fluxcd.io/en/latest/ declaring that "Flux v1 is in maintenance mode" into the Flux v1 stable docs, as well as pointing users from as many places as possible to the new Flux v2.
Fixes

Update AWS SDK and SOPS fluxcd/flux#3401
Set Rollout strategy type: Recreate (Fixes for chart 1.6.2) fluxcd/flux#3325

Maintenance and documentation

Point to Flux v2 from docs fluxcd/flux#3419, fluxcd/flux#3423
Point to new community resources at fluxcd.io, fluxcd/flux#3403
Update issue/PR templates to mention Flux v2 fluxcd/flux#3415, fluxcd/flux#3414
Add NetHunt to list of production users fluxcd/flux#3399

Thanks
Thanks to @nairb774, @ViBiOh, @SvitlanaTsupryk-jul18, @dholbach, @drewfreyling, @stefanprodan, @hiddeco, @kingdonb and @squaremo for their contributions to this release.

Can you please escape all the @<github-id> mentions? I get a notification every time.


Support for large requests (more_body=True)

This library seemed to hit the spot for drop-in support for msgpack with FastAPI. I am using the following to enable the msgpack interface:
app.add_middleware(MessagePackMiddleware)
Unfortunately, large client requests are failing. Running uvicorn with --log-level trace I see that the request is being chunked:
TRACE:    <IP_ADDRESS>:42088 - Connection made
TRACE:    <IP_ADDRESS>:0 - ASGI [4] Started scope={'type': 'http', 'asgi': {'version': '3.0', 'spec_version': '2.1'}, 'http_version': '1.0', 'server': ('<IP_ADDRESS>', 8901), 'client': ('<IP_ADDRESS>', 0), 'scheme': 'https', 'method': 'POST', 'root_path': '/app/<redacted>', 'path': '<redacted> 'raw_path': b'/<redacted>', 'query_string': b'', 'headers': '<...>'}
TRACE:    <IP_ADDRESS>:0 - ASGI [4] Receive {'type': 'http.request', 'body': '<65150 bytes>', 'more_body': True}
TRACE:    <IP_ADDRESS>:0 - ASGI [4] Receive {'type': 'http.request', 'body': '<65482 bytes>', 'more_body': True}
TRACE:    <IP_ADDRESS>:0 - ASGI [4] Send {'type': 'http.response.start', 'status': 400, 'headers': '<...>'}
INFO:     <IP_ADDRESS>:0 - "POST<redacted> HTTP/1.0" 400 Bad Request
TRACE:    <IP_ADDRESS>:0 - ASGI [4] Send {'type': 'http.response.body', 'body': '<45 bytes>'}
TRACE:    <IP_ADDRESS>:0 - ASGI [4] Completed
TRACE:    <IP_ADDRESS>:42088 - Connection lost

Requests under 64k work fine. JSON requests of any size are also fine.
The request is being sent from the client as a regular POST.
I assume this is related the comments about more_body not being implemented in the source code.
I am still getting up to speed with ASGI. Is this something that should be fixed with this middleware, or should I look at figuring out how to increase the buffer size elsewhere?

Hi!
Interesting... Could you share a minimal ASGI app (FastAPI or otherwise) along with a sample request that allow to reproduce this issue? We'd need to make sure this doesn't come from interaction with eg some FastAPI feature, or external limitations such as body limits on a reverse proxy. Eg I'm not sure where the 400 comes from...

About the 400: we raise a NotImplementedError in our code so I would be expecting the traceback from that plus a 500 error response, not a 400 bad request response. See: https://github.com/florimondmanca/msgpack-asgi/blob/master/src/msgpack_asgi/_middleware.py#L61

Thanks for the quick response! I'm quite new to FastAPI+ASGI, and finding any intuition I had with Flask only goes so far. ;-)
Here's a minimal app to show this:
server.py:
from fastapi import FastAPI
from msgpack_asgi import MessagePackMiddleware
from pydantic import BaseModel
from typing import List

app = FastAPI()

app.add_middleware(MessagePackMiddleware)

class StrList(BaseModel):
    hello: List[str]

@app.post("/")
def hello(data: StrList):
    return data

client.py:
import msgpack
import requests

# This works
url = "http://<IP_ADDRESS>:8000/"
data = { 'hello' : ['world'] }
headers = {'content-type': 'application/x-msgpack',
            'accept' : 'application/x-msgpack'}
resp = requests.post(url, data=msgpack.packb(data), headers=headers)
print(resp.status_code)

# This doesn't
data = { 'hello' : ['world'] * 50000 }
headers = {'content-type': 'application/x-msgpack',
            'accept' : 'application/x-msgpack'}
resp = requests.post(url, data=msgpack.packb(data), headers=headers)
print(resp.status_code)
print(msgpack.unpackb(resp.content))

Running the app with uvicorn --reload msgpackbug:app
Client Output:
200
400
{'detail': 'There was an error parsing the body'}

Thanks!
I guess the next step would be to determine which component in the stack (among FastAPI, Uvicorn, msgpack-asgi) does the checking that leads to this "failed to parse the body" error...?

If anyone's interested, I implemented this middleware, which I put infront of the msgpack middleware.
It does the buffering in memory.
Seems to work in my case
class FullBodyMiddleware(BaseHTTPMiddleware):
    async def __call__(self, scope: Scope, receive: Receive, send: Send) -> None:
        if scope["type"] != "http":
            await super().__call__(scope, receive, send)
            return

        async def full_receive():
            message = await receive()

            full_body = message["body"]
            more = message.get("more_body", False)

            while more:
                next_message = await receive()
                full_body += next_message["body"]
                more = next_message.get("more_body", False)

            message["body"] = full_body
            message["more_body"] = False
            return message

        await super().__call__(scope, full_receive, send)

    async def dispatch(
        self, request: Request, call_next: RequestResponseEndpoint
    ) -> Response:
        return await call_next(request)


Document options

For example, what values can these take:
https://github.com/cvanaret/Uno/blob/1f373ce25049e593088bee66b37a9057039ac19a/uno.options#L94-L102

To answer my own question, currently they are the only options:
https://github.com/cvanaret/Uno/blob/1f373ce25049e593088bee66b37a9057039ac19a/uno/solvers/QPSolverFactory.hpp#L21-L28
https://github.com/cvanaret/Uno/blob/1f373ce25049e593088bee66b37a9057039ac19a/uno/solvers/LPSolverFactory.hpp#L20-L26
although linear_solver can be MUMPS
https://github.com/cvanaret/Uno/blob/1f373ce25049e593088bee66b37a9057039ac19a/uno/solvers/SymmetricIndefiniteLinearSolverFactory.hpp#L23-L34

As a partial answer, the following command is available:
charlie@africa /media/data/Uno/build $ ./uno_ampl --strategies
Available strategies:
Constraint relaxation strategies: feasibility_restoration, l1_relaxation
Globalization mechanisms: TR, LS
Globalization strategies: l1_merit, fletcher_filter_method, waechter_filter_method, funnel_method
Subproblems: QP, LP, primal_dual_interior_point

I will add the available subproblem solvers.

With commit 73fa292, the command ./uno_ampl --strategies produces (when all subproblem solvers are installed):
Available strategies:
- Constraint relaxation strategies: feasibility_restoration, l1_relaxation
- Globalization mechanisms: TR, LS
- Globalization strategies: l1_merit, fletcher_filter_method, waechter_filter_method, funnel_method
- Subproblems: QP, LP, primal_dual_interior_point
- QP solvers: BQPD
- LP solvers: BQPD
- Linear solvers: MA57, MUMPS


First steps in replacing KClass with custom information type

Very first steps in replacing KClass as query result with a custom information class ReflectClass.
Sorry for lots of unrelated refactorings. I can extract them to another PR if needed.
Resolves #112

Also I think to extract refactorings into another PR is a great idea


Use tls-zeroed-aligned-memory

as part of eval of mimalloc (#1250 )
Problem
Perf result
all cases are measured with --block-verification-method=blockstore-processor
jemalloc
ledger processed in 24 seconds, 848 ms
ledger processed in 24 seconds, 842 ms
ledger processed in 24 seconds, 801 ms

mimalloc
ledger processed in 25 seconds, 666 ms
ledger processed in 25 seconds, 174 ms
ledger processed in 25 seconds, 77 ms

glibc
ledger processed in 24 seconds, 908 ms
ledger processed in 24 seconds, 827 ms
ledger processed in 24 seconds, 974 ms

rpmalloc
ledger processed in 24 seconds, 783 ms
ledger processed in 24 seconds, 977 ms
ledger processed in 25 seconds, 256 ms

Summary of Changes
xref: https://github.com/solana-labs/rbpf/pull/565
Fixes https://github.com/solana-labs/solana/issues/27275

I ended up doing exactly the same thing (a buffer pool), after my 0-filled tmpfs remap didn't work in the validator, from last week's standup:

integrated my alternative vm stack allocation impl in the validator and... it failed spectacularly. The trick I was using was to remap a 0-page in a new mapping (create a 0 filled tmpfs file, remap it over and over to allocate zeroed memory). That works great if you allocate from a relatively low number of threads. I discovered it breaks horribly if you allocate from a bazillion threads (like the validator does), because linux uses a rwlock on current->vm (the tree used to track vmas), and if you mmap from multiple threads that lock becomes write contended. So I begrudgingly scrapped that and implemented a thread-local buffer pool instead (not Recycler because that uses a lock), which seems to work, but needs some more love.

😅

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 82.8%. Comparing base (f54c120) to head (20e012f).
Report is 3 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1364   +/-   ##
=======================================
  Coverage    82.8%    82.8%
=======================================
  Files         872      872
  Lines      369252   369291   +39
=======================================
+ Hits       305797   305867   +70
+ Misses      63455    63424   -31


Fix compiler deprecation and feature warnings

Blocks #1064
scalac currently reports 7 deprecation and 14 feature warnings across our codebase. These become fatal when passing -Xfatal-warnings (https://github.com/informalsystems/apalache/issues/1473#issuecomment-1065161610) in #1064.
We should

[ ] enable -feature and -deprecation
[ ] fix all deprecation warnings
[ ] fix all feature warnings

Presumably related to #1064, which is why I'm assigned/

@shonfeder Sorry, I meant to assign myself 😅
I don't know if the current warnings á la
[warn] four deprecations (since 2.11.0); re-run with -deprecation for details

would fail with -Xfatal-warnings, so either this is blocked by #1064 or blocking it.

no worries! I'm happy to take the issue if you decide to change gears :)


Conflict due to Firebase UI 2.2.0 Dependency

Firebase/Play Services SDK version: 11.4.0
FirebaseUI version: 2.2.0
While trying to upgrade to Firebase UI 2.2.0, the build is failing because Firebase UI is using an old dependency (com.android.support:customtabs:25.4.0 (*)) which is in conflict with google support cardview (    compile 'com.android.support:cardview-v7:26.0.0').
The dependency tree for Firebase UI:
+--- com.firebaseui:firebase-ui-auth:2.2.0
|    |    +--- com.android.support:design:25.4.0 -> 26.0.0 ()
**|    |    +--- com.android.support:customtabs:25.4.0 ()**
|    |    +--- com.android.support.constraint:constraint-layout:1.1.0-beta1
The snippet of the error is also attached.
Could you please assist the resolution?
Thanks Firebase Team

@kumarkeviv Yeah, check out the README.

@SUPERCILEX ok then look like will have to wait till the dependency gets updated at Firebase UI.
Thanks

@kumarkeviv No, here's a quote from the README:

If you would like to use a newer version of one of FirebaseUI's transitive dependencies, you need to add explicit compile declarations in your build.gradle for all of FirebaseUI's dependencies at the version you want to use.

So just add compile com.android.support:customtabs:26.0.0 and you should be good to go.

Thanks @SUPERCILEX this resolves the issue.
I missed that point.


images: Error if the specified imagename does not exist

The images option allows the image name to be specified. If the specified image does not exist, an error should be output.
Before modification:
➜  buildah git:(images-wron-name) sudo buildah images --format {{.ID}} 456

After modification:
➜  buildah git:(images-wron-name) sudo ./buildah images --format {{.ID}} 456
No such image 456

Signed-off-by: Zhou Hao<EMAIL_ADDRESS>

Thanks @q384566678
You need to gofmt your code.

Thanks @q384566678
You need to gofmt your code.

bot, retest this please


Copy object using drag & drop with Ctrl pressed

I suggest to add feature to copy connection using drag & drop with Ctrl pressed.
It is slightly quicker and easier for a user than using context menu.
If Ctrl key is pressed on a keyboard and user drags the connection, when it drops it, the connection is pasted (a copy is created).
If you accept this principle, I suggest to make use of it for all the objects in the application, that can be copied/drag&dropped:

connection
database
schema
table
etc..

https://github.com/user-attachments/assets/8b3360b5-b13d-48cd-ae00-76f589f002db

Thank you for feature request!


Support for Laravel Dusk?

Is this great project already supporting Laravel Dusk tests?
If not it would be great if you can add Laravel Dusk. Thanks!

Hi @FabioWidmer
I would say yes.
Looking in Dusk composer dependencies I see that relies on facebook/webdriver, which depends on curl and zip extensions, both included in the images.

@edbizarro Thank you for your reply. I will try Laravel Dusk in the future and if there is a problem I will let you know.


Support for Python3.6

Does the library support Python 3.6?
We are going to relay on this library in the B2STAGE HTTP-API which is based on py 3.6
Thanks!

Hi,
It is tested against python 3.5: https://jenkins.argo.grnet.gr/job/B2HANDLE_devel/
The documentation also states python 3.5

Let me try to reformulate the question: do you have plan for supporting python 3.6?
Many thanks

The solution proposed in (#115) does not resolve the random dictionary order issue in python 3.6..

Does the issue affects only the tests? If that is the case we could start using the library anyway (maybe forking and editing the setup.py)

I just performed some operations like creating and retrieving handles (python 3.6.0) and it works.
The issue concerns only the testcase "test_create_revlookup_query_normal_checksum_and_url".

Ok. I have forked the repo here.
Just for the record: I couldn't install with pip3 install b2handle-1.1.1-py3.6.egg receiving the error:
Collecting b2handle-1.1.1-py3.6.egg
  Could not find a version that satisfies the requirement b2handle-1.1.1-py3.6.egg (from versions: )
No matching distribution found for b2handle-1.1.1-py3.6.egg

It worked with easy_install b2handle-1.1.1-py3.6.egg
I leave you the choice whether to close the issue. Thanks!

Just talked again with Sofiane and we think that the dictionary ordering issue is a Python issue that has already been discussed in the community for quite a while now. But this does not affect the functionality of b2handle; so our solution is to deactivate the test.
This could then go together with configured support for Py3.6 and further testing into one of the next releases. Currently, the splitting of the library / pyhandle development takes priority.

I admit I'm missing context here but if the core of the problem is that comparing dicts may yield failures because the order is undefined why not use cmp instead of ==. Or use an OrderedDict (from collections) to begin with.
Just my 2 cents,
Raphael - a lurker

I wonder if there is any progress on this?
Does the fork of @muccix  solve this issue?
Would it make sense to merge it back to the main project?

@stefan-wolfsheimer we will release a new version of the B2HANDLE library that supports Python 3.6. / 3.7

Meanwhile, the October 2019 https://github.com/EUDAT-B2SAFE/B2HANDLE/commit/256b5a96b759d35e142e5d359dfb4a9b99f2bd58 says:

The library currently supports Python 2.6, 2.7, 3.5, 3.6 and 3.7, and requires at least a Handle System server 8.1.

It seems this was also merged into the October 2019 pre-release 1.1.2.


Mongoose and Discriminators

I have a schema that uses mongoose discriminators for a few objects.  One example is -
let baseFollowSchema = mongoose.Schema({
followuuid: { type: String, default: uuidv4() },
createdDate: { type: Date, default: Date.now },
effectiveStartDate: { type: Date, default: Date.now },
effectiveEndDate: { type: Date, default: new Date(+new Date() + 30 * 24 * 60 * 60 * 1000) }, // 30 days
metadata: [metaDataItemSchema],
reviewData: [reviewDataItemSchema],
isActive: { type: Boolean, default: true },
isDeleted: { type: Boolean, default: false }
}, { discriminatorKey: 'followType' })
let Follow = mongoose.model('baseFollowSchema', baseFollowSchema, 'follow');
let KnowledgeGraphFollow = Follow.discriminator('followKGEntity',
new mongoose.Schema({
name: { type: String },
followedKGIDs: [{
kgid: { type: String },
entityType: { type: String },
name: { type: String },
metadata: [metaDataItemSchema]
}]
})
);
[.... Other models excluded for simplicity]
Is there a good example/test that can point me to how to implement the use of discriminators?
Thanks-
MJD

+1

@nodkz What if its in a sub-document, as an array?
eg.const sessionSchema = new mongoose.Schema({ 'generated': { 'events': [eventSchema]  } })

hello, I have gone through the comments, but really i wanted more flexibility, so i have gone ahead to create a small library that uses graphql-compose-mongoose under the hud. It creates a typeComposer, and an interface for the baseModel, then the baseTypeComposer exposes a discriminator function that returns a typeComposer that implements the baseType Interface.
It exposes a single function, composeWithMongooseDiscriminator that returns a custom DiscriminatorTypeComposer that has the discriminator method to create ChildDiscriminatorTypeComposer. The child is a normal TypeComposer with the baseInterface set as interface.
you can check out here, created a playground so you can test the library.
Graphql Playground With Functioning Schema and DB

There is a demo schema and a working database, you have all the compose-mongoose resolvers to play with.
@nodkz is it possible you integrate this with graphql-compose-mongoose or should i create a graphql-compose-mongoose-discriminators repo? Really love to hear from you with regards to this, haven't published yet.

@mernxl did amazing work.
With<EMAIL_ADDRESS>work with discriminators became work much easier
https://github.com/graphql-compose/graphql-compose-mongoose/releases/tag/v4.4.0


ADD support for stopper Wait propagation.

ADD unit tests for Wait and Stop for stopper children.

@tiger5226 can you show me where you use this in chainquery?

can close this as the changes to chainquery are not happening right now.


DTD Download Failure

Unable to download the DTD
http://cobertura.sourceforge.net/xml/coverage-04.dtd
Similar ticket here which was closed in the past.
https://github.com/a7ex/xcresultparser/issues/19
Current Error:
An error has been encountered in accessing this page.

Server: cobertura.sourceforge.net
URL path: /xml/coverage-04.dtd
Error notes: NONE
Error type: 404
Request method: GET
Request query string: NONE
Time: 2024-06-21 16:40:50 UTC<PHONE_NUMBER>)

Reporting this problem: The problem you have encountered is with a project web site hosted by SourceForge.net. This issue should be reported to the SourceForge.net-hosted project (not to SourceForge.net).
If this is a severe or recurring/persistent problem, please do one of the following, and provide the error text (numbered 1 through 7, above):
Contact the project via their designated support resources.
Contact the project administrators of this project via email (see the upper right-hand corner of the Project Summary page for their usernames) at<EMAIL_ADDRESS>If you are a maintainer of this web content, please refer to the Site Documentation regarding web services for further assistance.
NOTE: As of 2008-10-23 directory index display has been disabled by default. This option may be re-enabled by the project by placing a file with the name ".htaccess" with this line:
Options +Indexes

My bad. Needed to update to a newer version as the location of the DTD has moved.


Support StabilityAi Image Edit Api

Hello, this PR implements StabilityAi Image Edit - Remove Background API's client.

PR contents:

Add background removal via StabilityAI’s V2 Beta API.
Configured image handling as raw or Base64.
Add ImageEditHeaders for request headers.
Add Test.
Add docs.

Related Issue:

#708 (help wanted labelled)

I’m pleased to submit this PR to Spring AI.
Please let me know if any revisions are needed, and I will address them promptly.
I would be happy to assist with future maintenance as well.

I have resubmitted it as PR #1328.


The number of repos that we have starred is wrong

The number of repos that the user has starred shows up as 100, if the number is more than 100 because of the per_page=100in the GET request URL

I can get to work on this. I believe the user details contains total stars?


Fix 6 strictly greater

A couple fixes for the exercise 6_Strictly_greater_num.c
Each fix is split into different commits, so should be easy to spot.

Hey,
Here I checked Your Commit No. 2, and 3  are good but It was not fixes the ISSUE as I want solution for the given output , not the restriction to be put on Input
Otherwise Thanks for your Contribution
you can check if you will correct it then go forward but,


ionicHistory.backView() almost everytime is null

Short description of the problem:
When I try access to to ionicHistory.backView() is most cases it shows null
I use tabs
What behavior are you expecting?
ionicHistory.backView() should work when I navigate
Version 1.3.0, on previous worked fine

Upgraded to 1.3.1 No problems anymore


SSL Labs integration broken?

[E] SSL Labs Error: undefined method `each' for nil:NilClass

I'm working on something to address this - seems to be happening intermittently. Once I work something out, I'll get a new release out.
(Sorry for the delay in responding - missed the notification for this.)


tweak chef-solo run_lock timing test

fix the 'last' statements (my perl brain occassionally crops up
in ruby code) and replace with a raise.  of course this just swaps
one exception for another, but this time its really intended to
work this way.

swap the order of the expecations so that if we fails to see the
waiting on the other process statement, but we blow up in both
threads in the exception that was just added, we know we actually
have a legit run_lock race condition that this code just found.

does not fix this bug, just gets us a bit more information if it
reoccurs.
Signed-off-by: Lamont Granquist<EMAIL_ADDRESS>

@chef/client-core completely trivial tweaking to a spec

turns out i can also replicate the race condition and it looks like Process.spawn may be buggy, so real fix might be coming shortly...

https://bugs.ruby-lang.org/issues/10583 is likely the bug in Process.spawn.


Support Bazel version 0.11.0 [phab:D2198]

Created by schroederc at 2018-02-23 21:46:02:

shahms accepted this revision at 2018-02-23 21:47:31

schroederc closed via commit 237e8ca8d44369de611aa8dcc508405087c6574c at 2018-02-23 21:52:31


Simulator Load File error

Dear Manav:
I get a load file error when I  run: python drive.py model.h5
(BTW, There is some confusion in the community if the h5 file or the json file should be loaded.)
I run : python drive.py model.h5
I get  on my windows 10 machine:
Using TensorFlow backend.
Traceback (most recent call last):
File "drive.py", line 83, in
model = load_model(args.model)
File "d:\kits\Anaconda3\envs\carnd-term1\lib\site-packages\keras\models.py", line 140, in load_model
raise ValueError('No model found in config file.')
ValueError: No model found in config file.
Here is my save code:
..........
model.summary()
model.compile(optimizer='adam', loss='mse', metrics=['accuracy'])
history = model.fit(X_train, y_train, nb_epoch=10, batch_size=2000, verbose=1,
validation_data=(X_validation, y_validation))
score = model.evaluate(X_validation, y_validation)
print('Test score:', score[0])
print('Test accuracy:', score[1])
print("\nSaving model weights and configuration file.")
with open('model.json', 'w') as f:
f.write(model.to_json())
model.save_weights('model.h5')
f.close()
print("Saved model to disk")
from keras import backend as K
K.clear_session()
Thanks for any guidance you can provide me.

Try model.save('model.h5') instead of model.save_weights('model.h5').

You are Genius! Thanks it works.  If you dont mind, can you explain to me why the model save would works and not the weights?
Thank you so much I have been stuck on this for days!

save also saves the configuration of the network, i.e. how it's structured while save_weights only saves the weights. load_model needs to reconstruct the model it can't do this with with only knowledge of the weight values.

That clears things up. Thanks again!