wifi.findAndConnect how do i listen to the response?

Hey
so if i try to connect to a wifi network using wifi.findAndConnect ... the responso only tells me if it is in range not if i got connected ... how do i know if the connection succeeded?

Hey wowzaaa
Android doesn’t provide a callback when you try to connect to a wifi. You have to listen for connectivity changes to know if connection succeeded. You can use NetInfo from React Native Components.


Update relaxed simd instructions

Changes wasm-tools to implement current https://github.com/WebAssembly/relaxed-simd/blob/main/proposals/relaxed-simd/Overview.md

Update instructions names and codes
Add new instructions i16x8.relaxed_q15mulr_s, i16x8.dot_i8x16_i7x16_s, i32x4.dot_i8x16_i7x16_add_s, and f32x4.relaxed_dot_bf16x8_add_f32x4

Oh also, would you like a publish?

If so, do you find it onerous/difficult/annoying to update all the other crates in the workspace?
Recently I'm wondering if we should try to deduplicate all the instruction encodings/names into one place to avoid having to name them in so many places.

It is not a big deal to update in multiple place, as long as testing will check typos and discrepancies in implementations.

Oh also, would you like a publish?

Yes, at your earliest convenience. I anticipate a reasonable delay up to 2 weeks between version release.

@yurydelendik I'm not following the the relaxed-simd spec much so you may know the answer to this. With https://github.com/WebAssembly/testsuite/pull/62 I was testing out updating the wasm-tools submodule to the testsuite to include relaxed-simd to ensure that all tests pass. Currently the only error is:
failed test: tests/testsuite/proposals/relaxed-simd/relaxed_fma_fms.wast

Caused by:
    unknown operator or unexpected token
         --> tests/testsuite/proposals/relaxed-simd/relaxed_fma_fms.wast:5:78
          |
        5 |     (func (export "f32x4.relaxed_fms") (param v128 v128 v128) (result v128) (f32x4.relaxed_fms (local.get 0) (local.get 1) (local.get 2)))
          |                                                                              ^

It looks like fms operations were reimplemented as fnma but there aren't any spec tests for fnma, so I'm wondering if you know what the current state of this is and how to reconcile this.

Also I'm happy to publish whenever, I'm just waiting for a day with no fuzz-bugs to publish. (should be today, checking on oss-fuzz now)

It looks like fms operations were reimplemented as fnma but there aren't any spec tests for fnma

The difference between f32x4.relaxed_fms and f32x4.relaxed_fnma is operands order. The existing test will be changed to use third operand as an accumulator (in fms and fma it was the first one). The old f32x4.relaxed_fma test will be failing as well. This change was made to keep signature similar to dot instructions.

Also I'm happy to publish whenever, I'm just waiting for a day with no fuzz-bugs to publish.

No problem. It is sort of a breaking change, and probably has not good tests. Disabling tests for fma/fms can be an option.

Ok sounds good, I'll handle that accordingly and publish these changes today.


New producers don't confirm anything until their second round

Something is too conservative in the producer_plugin watermarks.  New producers, who were "live" when they see the schedule promotion should confirm as they can know that they are not recovering from a state loss (which is the reason we usually lag a round for conservative confirmations).

BFT confirmations are not needed for 1.0


severe lagging/stuttering/freezing/skipping

Type
Crash or hang
Operating System
Windows
OS Version
Windows 10
Bug description
Seems to be after toa release this bug started. awful freezing but its clientwide, cant click or type when it happens. nothing to do with latency. seems like runelite just skips really hard. have uninstalled and reinstalled, redownloaded and installed, adjusted and disabled plugins, disabled hardware acceleration, uninstalled and disabled programs like msi and rivatuner. tried various settings in nvidia control panel, disabled any OCs, etc. bug seems to come and go without any clear reason. sometimes relaunching the client gives me an hour of no bug time, sometimes there is nothing i can do.
not that it matters but 3080 and i7 8700 16gb ddr4 on a m.2 so thats not an issue. nothing changed on my pc end.
Screenshots or videos
https://user-images.githubusercontent.com/95214548/187763696-082ddd96-4b58-42fd-a6a2-4f67cc0e8029.mp4
https://user-images.githubusercontent.com/95214548/187763737-7925a6cc-c07d-4485-b314-135d9e8c3cb9.mp4
https://user-images.githubusercontent.com/95214548/187763768-1484a0da-9d8b-4820-a3af-cd3a519d23c9.mp4
RuneLite version
runelite <IP_ADDRESS>
launcher 2.4.5
Logs
client_2022-08-09.0.log
client_2022-08-10.0.log
client_2022-08-11.0.log
client_2022-08-12.0.log
client_2022-08-13.0.log
client_2022-08-14.0.log
client_2022-08-15.0.log
client_2022-08-16.0.log
client_2022-08-17.0.log
client_2022-08-18.0.log
client_2022-08-19.0.log
client_2022-08-20.0.log
client_2022-08-21.0.log
client_2022-08-22.0.log
client_2022-08-23.0.log
client_2022-08-24.0.log
client_2022-08-25.0.log
client_2022-08-26.0.log
client_2022-08-27.0.log
client_2022-08-28.0.log
client_2022-08-29.0.log
client_2022-08-30.0.log
launcher.log
launcher_2022-08-01.0.log
launcher_2022-08-03.0.log
launcher_2022-08-04.0.log
launcher_2022-08-05.0.log
launcher_2022-08-06.0.log
launcher_2022-08-07.0.log
launcher_2022-08-08.0.log
launcher_2022-08-09.0.log
launcher_2022-08-10.0.log
launcher_2022-08-11.0.log
launcher_2022-08-12.0.log
launcher_2022-08-13.0.log
launcher_2022-08-14.0.log
launcher_2022-08-15.0.log
launcher_2022-08-16.0.log
launcher_2022-08-17.0.log
launcher_2022-08-18.0.log
launcher_2022-08-19.0.log
launcher_2022-08-20.0.log
launcher_2022-08-21.0.log
launcher_2022-08-22.0.log
launcher_2022-08-23.0.log
launcher_2022-08-24.0.log
launcher_2022-08-25.0.log
launcher_2022-08-26.0.log
launcher_2022-08-27.0.log
launcher_2022-08-28.0.log
launcher_2022-08-29.0.log
launcher_2022-08-30.0.log
client.log
client_2022-08-01.0.log
client_2022-08-03.0.log
client_2022-08-04.0.log
client_2022-08-05.0.log
client_2022-08-06.0.log
client_2022-08-07.0.log
client_2022-08-08.0.log

If you disable 117hd, reboot your client, and then don't use 117hd, does that fix it?

unfortunately not, still happening with 117hd turned off after restarting computer

If you can get a heap dump using the debug helper plugin from the pluginhub when it is freezing, that would be useful

github doesnt support that filetype

If you can get a heap dump using the debug helper plugin from the pluginhub when it is freezing, that would be useful

how can i share that with you? not hip on the norms on github

Join #support on https://runelite.net/discord and ping me there

Since this issue was opened, we've made a number of changes which should reduce the amount of memory the client in general uses, which should address this issue. Let us know if it is still a problem for you.
For some more information, you can read the blog post we published on it here: https://runelite.net/blog/show/2022-09-04-recent-performance-regressions-and-tombs-of-amascut


Bloom Filter Dump restore failing

trying to restore the dump having bloom filters from dump.rdb. Which is not working.

Bloom Module Installation:
https://github.com/RedisBloom/RedisBloom/archive/refs/tags/v2.2.18}.tar.gz
loading bloom in this way  `loadmodule /tmp/redisbloom.so >> redis.conf`

Version:
REDIS VERSION 7.0.4
REDIS DUMP VERSION 5.0.9

Command
rdb -c protocol dump.rdb | redis-cli -h <IP> -p <PORT> --pipe

Response
All data transferred. Waiting for the last reply...
Last reply received from server.
errors: 0, replies: 1

这是来自QQ邮箱的假期自动回复邮件。您好，我最近正在休假中，无法亲自回复您的邮件。我将在假期结束后，尽快给您回复。


Update seed data to bay area counties

Pull Request Template
Since we removed the ability for Partners to utilize a county that is covered by other Bloom instances (SF, San Mateo, Alameda, and City of San Jose), then we need to update the seed data to counties outside of those areas so that when they are viewed in the partners portal the county drop down will show data.
I tried to find addresses that were similar to the prior ones, in case it's easier to reference in the future. Not sure it really matters.
Issue Overview
This PR addresses #issue

[x] This change addresses the issue in full
[ ] This change addresses only certain aspects of the issue
[ ] This change is a dependency for another issue
[ ] This change has a dependency from another issue

How Can This Be Tested/Reviewed?
View main or any other branch with prior seed data & take a screenshot to compare with the new data. (You might need to add all counties to the filters to see all the data.)

Install & build all 3 services. Reseed (yarn db:reseed from backend/core) data and then yarn dev all 3 services.
Public site should have the following listings with [doorway] in the title:

1 in Sausalito
1 in Fairfield
1 in Sonoma (Sesame St - broken previously & need to be fixed in subsequent PR)
1 in Santa Clara (Sesame St - broken previously & need to be fixed in subsequent PR)
13 in San Ramon

*you may need to adjust the filter to include all counties
then double check as many listings as you have time for on the Partners & Public site to ensure that the address data & maps still look valid and don't have any issues. The things that will change are the map pin location & the county label at the top of each listing
Here's the locations updated in this PR:

Checklist:

[x] My code follows the style guidelines of this project
[x] I have added QA notes to the issue with applicable URLs
[x] I have performed a self-review of my own code
[x] I have reviewed the changes in a desktop view
[ ] I have reviewed the changes in a mobile view
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[x] I have assigned reviewers
[ ] I have run yarn generate:client and/or created a migration if I made backend changes that require them
[ ] My commit message(s) is/are polished, and any breaking changes are indicated in the message and are well-described
[ ] Commits made across packages purposefully have the same commit message/version change, else are separated into different commits

Reviewer Notes:
Steps to review a PR:

Read and understand the issue, and ensure the author has added QA notes
Review the code itself from a style point of view
Pull the changes down locally and test that the acceptance criteria is met
Also review the acceptance criteria on the Netlify deploy preview (noting that these do not yet include any backend changes made in the PR)
Either explicitly ask a clarifying question, request changes, or approve the PR if there are small remaining changes but the PR is otherwise good to go

On Merge:
If you have one commit and message, squash. If you need each message to be applied, rebase and merge.

to test this -- could you post a test plan -- reseed, then comment with a screenshot/video of the /listings page? we should see the county names change and the map pins change if this was successful.

@lisunshiny & @ifranch updated test plan included with some screenshots. I also made a couple more changes to include the Sesame Street listings in 2 other counties. Can you re-review/resolve as you see fit? Thanks!


Best way to handle sec and ms level of granularity

I see in the anomaly_detect_ts the period is not set when the granularity is either 'sec' or 'ms':
elif timediff.seconds > 0:
    granularity = 'sec'
    # Aggregate data to minutely if secondly
    data = data.resample('60s', label='right').sum()
else:
    granularity = 'ms'

This causes the error reported in #11 Questions: should data at the sec and ms level (1) be resampled to 'min' level of granularity and set the period=1440 (2) be unsupported with ValueError being thrown to interrupt processing, (3) provide both as a configurable option
I personally vote for (3). @Marcnuth @triciascully what do you think?

I vote or (3), and thanks for debugging this!
On a separate but related note, I've been manually running the code and setting the period to period = 96 because the data I'm working with is at a 15min interval - can you build in an option for configuration of the period as well, since people might be working with data that's every 10min, 15min, 30min, 2hrs, etc.?

Yep, I can do that! Please put in a issue so it can be tracked.
Thanks
—John
Sent from my iPhone

On Sep 20, 2018, at 4:55 PM, triciascully<EMAIL_ADDRESS>wrote:
I vote or (3), and thanks for debugging this!
On a separate but related note, I've been manually running the code and setting the period to period = 96 because the data I'm working with is at a 15min interval - can you build in an option for configuration of the period as well, since people might be working with data that's every 10min, 15min, 30min, 2hrs, etc.?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Adding in code to do the following:

enable resampling of both sec and ms to minute
render resampling of both sec and ms to be configurable so that either the resampling to a minute granularity occurs or a ValueError is thrown

Ah thank you, John! Sorry for the delay, I've been traveling - do you still need this in an issue?

No worries! Yes, please do that so it can be tracked. I am currently testing the fix that resamples data with ms and sec granularity. It's taking awhile because I need to generate it from metricbeat.

@triciascully this is implemented and tested in the master branch of my fork

merged, thanks @Marcnuth


The behavior of the FileLoggingSession is different than described.

Issue Observed:

Despite the documentation indicating that "The FileLoggingSession class sends logged messages to disk files as they
are logged," I cannot see any logs added to the file once the app is running, but the logs appear to be saved only after the application exits. This observation raises questions:

Questions:

Is the behavior observed (logs saved only upon application exit) an inconsistency with the documentation,
or is it the expected behavior and the documentation might be misleading or misinterpreted?

Is there a way to send the log to the file once it is logged?

Here is a minimal working demo code to illustrate the problem:
#include "pch.h"
#include <iostream>
#include <winrt/Windows.Foundation.h>
#include <winrt/Windows.Foundation.Diagnostics.h>
#include <chrono>
#include <thread>
#include <conio.h>

using namespace winrt;
using namespace Windows::Foundation;
using namespace Windows::Foundation::Diagnostics;

/*
This application creates a FileLoggingSession and a LoggingChannel to log messages
to an ETL file. The Windows.Foundation.Diagnostics documentation states that the
FileLoggingSession class automatically saves logged messages to disk files as they
are logged.

The log files are supposed to be stored in the application's local folder, which is
typically located at:
\AppData\Local\Packages\[PackageFamilyName]\LocalState\Logs

What the application does:
1. Initializes a WinRT apartment.
2. Creates a FileLoggingSession named "MySession".
3. Creates a LoggingChannel named "MyChannel" and adds it to the session.
4. Enters a loop that logs messages every second, appending a counter to indicate the message number.
5. If a key is pressed, the loop exits, stops logging, and triggers the saving of the log file.
6. According to the documentation, the log file should be saved immediately as per the FileLoggingSession's behavior.
*/

int main()
{
    init_apartment();

    // Create a new FileLoggingSession instance.
    FileLoggingSession session(L"MySession");

    // Add a logging channel to the session.
    LoggingChannel channel(L"MyChannel");
    session.AddLoggingChannel(channel);

    // Counter for log messages.
    int counter = 0;

    std::cout << "Logging started. Press any key to stop..." << std::endl;

    // Start a loop to generate logs.
    while (true)
    {
        if (_kbhit()) // Check if a key has been pressed.
        {
            _getch(); // Consume the key press.
            break;    // Exit the loop.
        }

        // Log a message with a counter.
        channel.LogMessage(L"Log message " + std::to_wstring(counter++));

        // Wait for 1 second.
        std::this_thread::sleep_for(std::chrono::seconds(1));
    }

    std::cout << "Stopping logging session. Please wait..." << std::endl;

    // Handle the async operation to save the log file.
    auto saveOperation = session.CloseAndSaveToFileAsync();
    saveOperation.get(); // Wait for the async operation to complete.

    std::cout << "Logging session closed and file saved." << std::endl;

    return 0;
}

Kind regards,
Krzysztof

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

ID: 0f5e03ad-d932-d83c-58e6-359dfe5ec5f4
Version Independent ID: cb6b60a2-2b3c-89bb-fd69-72c755e719c3
Content: FileLoggingSession Class (Windows.Foundation.Diagnostics) - Windows UWP applications
Content Source: winrt-api-build/xml/Windows.Foundation.Diagnostics/FileLoggingSession.xml
Product: uwp
Technology: winrt-reference
GitHub Login: @alvinashcraft
Microsoft Alias: aashcraft

Hi @krzysztofFC. Thanks for reaching out about this API. I'll try to find someone on the product team who can explain the observed behavior? Have you tried asking about this on the Q&A forums? The folks there can sometimes provide answers more quickly: Microsoft Q&A
If you do create a thread over at Microsoft Q&A, we would appreciate if you could share that link here so we can track the progress and incorporate any technical details into our documentation.

I got some info from the product team, @krzysztofFC. They said:
Events go to disk when a buffer is filled or when the user calls FileLoggingSession.CloseAndSaveToFileAsync.
I've updated the docs with this clarification. The changes should appear on the live site soon. Thanks for helping to improve the docs!


Update edit page layout to use a 2/3-1/3 layout

Update the edit page layout to use a 2/3-1/3 layout.
As part of Trello card

@tijmenb updated to apply the 2/3 layout only on the document editing page.


changed github.com/pingcap/ticdc to github.com/pingcap/tiflow

changed github.com/pingcap/ticdc to github.com/pingcap/tiflow

First-time contributors' checklist

[ ] I've signed Contributor License Agreement that's required for repo owners to accept my contribution.

What is changed, added, or deleted? (Required)
changed github.com/pingcap/ticdc to github.com/pingcap/tiflow
Which DM version(s) do your changes apply to? (Required)

[x] master (the latest development version)
[ ] v5.3 (TiDB DM 5.3 versions)
[ ] v2.0 (TiDB DM 2.0 versions)
[ ] v1.0 (TiDB DM 1.0 versions)

What is the related PR or file link(s)?

This PR is translated from:
Other reference link(s):

Do your changes match any of the following descriptions?

[ ] Delete files
[ ] Change aliases
[ ] Need modification after applied to another branch
[ ] Might cause conflicts after applied to another branch

/merge
/remove-status LGT1
/status LGT2

/merge


Table statement about external users group chat

The table "Things people outside your organization can do" states that "Be added to a group chat" action for "External access users" as not available, however, according to the "Chat and collaboration Group chat with external users" blog post, it is - https://techcommunity.microsoft.com/t5/microsoft-teams-blog/what-s-new-in-microsoft-teams-may-2021/ba-p/2391927

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

ID: 5f080a5c-4268-1db4-566f-f1edc27920b5
Version Independent ID: ac556a92-58af-3e05-f53b-0fc00afc96c0
Content: Use guest access and external access to collaborate with people outside your organization - Microsoft Teams
Content Source: Teams/communicate-with-users-from-other-organizations.md
Service: msteams
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

Thanks for reporting @marcoszanre


Context file choice should not be shown if --append-snippets not used

There is no point in showing a list of files when steps are not matched if the user has not specified  --append-snippets, because without this switch the snippets are simply printed to stdout.
IMO the correct behaviour is: the choice of context files should only be given when --append-snippets is used.

Agreed. The user is referring to the list of contexts. So this output:
 >> default suite has undefined steps. Please choose the context to generate snippets:

  [0] None
  [1] FeatureContext
 > 1

--- FeatureContext has missing steps. Define them with these snippets:

    /**
     * @Given I am not logged in
     */
    public function iAmNotLoggedIn()
    {
        throw new PendingException();
    }

Seems like a reasonable cleanup. I spent some time puzzling over why it wasn't writing to FeatureContext when I had selected it. If you know about the file, and my choice, why aren't you writing to it? Oh yeah, --append-snippets

The only thing selecting a context does is make sure the method names don’t collide with existing methods


[Bug Fix] Redirect logged users when visiting "join community" page

/claim #89
Fixes #89
@dm161

Logged In users are redirected to /Golang-Developers when they visit /Join-Golang-Community or /Hire-From-Golang-Community pages
Added Conditional Redirect in the handlers

@dm161 fixed the PR comments and pushed

sorry @Vasanth-Korada i missed this is it possible to open a PR with {{ if not .LoggedUser }}display button{{ end }} so that we dont show the button also for logged users?

Ok @dm161 will raise a PR


[Bug report] The API for creating an Iceberg catalog has a deprecated parameter "warehouse" that is required in the HTTP payload

Version
main branch
Describe what's wrong
The property key warehouse was removed with rest assigned as a catalog-backend on Web UI, but REST API call for creating a catalog still requires warehouse in the request body and missing warehouse in the HTTP request body will cause the exception below.
No option warehouse provided with restcatalog-backend on Web UI

POST http://localhost:8090/api/metalakes/test/catalogs
{
  "name": "1",
  "type": "relational",
  "provider": "lakehouse-iceberg",
  "comment": "",
  "properties": {
    "uri": "1",
    // "warehouse": "",   // Why is this a required property ?
    "catalog-backend": "rest",
    "authType": "simple"
  }
}

API call without “warehouse” causes the exception below:
{
    "code": 1001,
    "type": "IllegalArgumentException",
    "message": "Failed to operate catalog(s) [100] operation [CREATE] under metalake [test], reason [Properties are required and must be set: [warehouse]]",
    "stack": [
        ...
     ]
}

Error message and/or stacktrace
{
    "code": 1001,
    "type": "IllegalArgumentException",
    "message": "Failed to operate catalog(s) [100] operation [CREATE] under metalake [test], reason [Properties are required and must be set: [warehouse]]",
    "stack": [
        ...
     ]
}

How to reproduce
Create a test metalake and then create a catalog by sending the request without warehouse to the REST API as follows :
POST http://localhost:8090/api/metalakes/test/catalogs
{
  "name": "1",
  "type": "relational",
  "provider": "lakehouse-iceberg",
  "comment": "",
  "properties": {
    "uri": "1",
    "catalog-backend": "rest",
    "authType": "simple"
  }
}

Additional context
No response

Sure, I'd be happy to handle it.

@fsalhi2 would you please leave an comment here, so I can assign the issue to you, thanks.

Hi @jerryshao , here am i :)


E0001 Error transforming template: sequence item 1: expected str instance, int found template.yaml:1:1

E0001 Error transforming template: sequence item 1 : expected str instance, int found template.yaml:1:1
Description of issue.
I created a normal template like this:
AWSTemplateFormatVersion: '2010-09-09'
Transform: AWS::Serverless-2016-10-31
Description: >
AWS
SAM CloudFormation Template for Publication Assembly Service
Parameters:
AssetId:
Type: String
Default: 207958
......
LIKE this ..and I am not getting error anywhere else in the template but getting this error in the first line.
How do I resolve this
Cfn-lint uses the CloudFormation Resource Specifications as the base to do validation. These files are included as part of the application version. Please update to the latest version of cfn-lint or update the spec files manually (cfn-lint -u)

Looks like the formatting in your issue got lost.  If I am looking at your template correctly and when I run it I get
E0001 Error transforming template: Structure of the SAM template is invalid. 'Resources' section is required
template.yaml:1:1

That issue is a generic decoding issue it may not come with line numbers.  Is there more to the template giving you the error?


duplicated channel id

Hi,
I have some sources with some duplicated "channel ids" (I know this is not right, but thats the best i've managed to get).
Is there any chance to grab just the first found "channel id"? Right now tv_grab_xml is grabbing every channel id no matter if it is duplicated.
Hoping your doing well

Hi @jorges4lu2 ,
channel ids should be a unique identifier, it was strange that you have duplicates in your EPG xml file.
Could you provide the XML resource you are using, and some duplicate ids within it?
In truth, this project is very old and I don't remember much about it...be patient, I need time to figure out, how and if we can fix it.
Ciao!
p.s. please consider to making a donation e/o stars the project


Nodes scale down and consolidation is not works after decrease size of pods

Description
Observed Behavior:
Nothing happens, log is empty:
last INFO event related with "controller.machine.lifecycle	launched machine" During increasing pods size
Expected Behavior:
Instances scale down, consolidation and start smaller instances and pods re-scheduling into smaller node
Reproduction Steps (Please include YAML):
I use default pods for test Cluster scale up/down
After deploy big PODS:
Karpenter scale UP my cluster with set of instances:
Log output:
INFO	controller.machine.lifecycle	launched machine	{"commit": "34d50bf-dirty", "machine", "provisioner": "default", "provider-id": "aws:///us-east-1b/i-0c574d8ae******", "instance-type": "c5d.2xlarge"
apiVersion: apps/v1
kind: Deployment
metadata:
  name: ubuntu-test
  namespace: test
  labels:
    app: test
spec:
  replicas: 5
  selector:
    matchLabels:
      app: test
  template:
    metadata:
      labels:
        app: test
    spec:
      containers:
        - name: ubuntu-test
          image: ubuntu:latest
          tty: true
          resources:
            requests:
              cpu: "4000m"
              memory: "4Gi"
            limits:
              cpu: "5000m"
              memory: "5Gi"

After I tried to decrease size of PODS
to
          resources:
            requests:
              cpu: "250m"
              memory: "128Mi"
            limits:
              cpu: "500m"
              memory: "256Mi"

After my pods is restarting with new resource settings but cluster does't scale down
PODS active in same nodes and no new log events related with scaling or another errors.
If scale UP to bigger values 6000m and so one cluster is scaling UP.
No errors during this tests, I have another errors related with webhooks, but looks like this issues is not related. For example:
ERROR	webhook.DefaultingWebhook	Reconcile error	{"commit": "34d50bf-dirty", "knative.dev/traceid": "54f1bded-7e41-4918-a102-8ce80a6e1e62", "knative.dev/key": "karpenter/karpenter-cert",
My config.
resource "kubectl_manifest" "karpenter_provisioner" {
  yaml_body = <<-YAML
    apiVersion: karpenter.sh/v1alpha5
    kind: Provisioner
    metadata:
      name: default
    spec:
      requirements:
        - key: karpenter.sh/capacity-type
          operator: In
          values: ["spot"]
      limits:
        resources:
          cpu: 10000
      providerRef:
        name: default
      ttlSecondsAfterEmpty: 30
  YAML

  depends_on = [
    helm_release.karpenter
  ]
}

resource "kubectl_manifest" "karpenter_node_template" {
  yaml_body = <<-YAML
    apiVersion: karpenter.k8s.aws/v1alpha1
    kind: AWSNodeTemplate
    metadata:
      name: default
    spec:
      subnetSelector:
        karpenter.sh/discovery/${module.eks.cluster_name}: ${module.eks.cluster_name}
      securityGroupSelector:
        karpenter.sh/discovery/${module.eks.cluster_name}: ${module.eks.cluster_name}
      tags:
        karpenter.sh/discovery/${module.eks.cluster_name}: ${module.eks.cluster_name}
  YAML

  depends_on = [
    helm_release.karpenter
  ]
}

If delete this PODS Karpenter removes nodes.
Versions:
Karpenter 0.29.2

Kubernetes Version (kubectl version):
EKS 1.27, self-managed-nodes

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

We don't currently do spot to spot node replacement.  We will only consolidate spot nodes if we can entirely delete them.  The reasoning is that we haven't built a good way to do spot -> spot replacement without also hurting availability by effectively implementing a lowest price spot launch strategy.
Closing as a duplicate of https://github.com/aws/karpenter/issues/2741 , feel free to re-open if you disagree.


After reconnecting, the hub will not send data to the server

steps to reproduce:

client connects to the signalr enpoint

client successfully sends data and receives data from signalr

kill the server

the hub throws an error: Error: WebSocket closed.

state changed: 2

bring up the server

hub goes in reconnecting mode

state changed: 1 (yes we got a connection again!!!)

so far so good.
but when I try to run step 2, the call is made to the hub but not passed to the server.
Fiddler even doesn't show anyting there.

Can you provide a sample project with this behavior? I have tested this before without issue. You can check out the simple chat demo which reconnects and is able to send/receive after a reconnect...

I've set up a new project and I think it was related to an old signalR jQuery script. Issue gone.


Replacing compass mixing translate(X,Y) for translate3d.

Some adjustment for a better performance.

@antoniojunyor  you forgot the file _helper-classes.sass, line 133

tsk @deividmarques, pls see again :metal:


Failed to parse source map from "data" URL

WARNING in<EMAIL_ADDRESS>Module Warning (from ./node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from "data" URL:
What is causing this error? Is it because my version is wrong?

I am also encountring similar warning in terminal. While running my reactjs application.

I am using 8.19.4


[DON'T MERGE] Category style for ReviewApp

For https://github.com/bm-sms/daimon-news/pull/582

Thanks Review Apps ❤
This feature is landed on master 🚀


hangs on Height Loading after account creation

Used the appimage package 0.9. After adding my account credentials the app just does nothing. The only message is "Height Loading" in the lower left corner. But nothing changes for a long time now.
Restarting it or deleting the config and adding the account again doesn't change anything. Here is the output of the dev console:
action ACCOUNT_DATA_UPDATE_PENDING @ 22:06:25.812 core.js:104
action ACCOUNT_DATA_UPDATE_PENDING @ 22:06:35.811 core.js:104
...

Using Arch Linux. Keep up the great work! Thx.

I think this is because the default node went offline earlier today.
If you goto settings and change the node to https://api.steemit.com for the time being, it should resume working.

thanks for the answer. rpc.buildteam.io works. the api.steemit.com seems to talk a different protocol and doesn't.


Google Cloud: Invalid character in header content ["Authorization"]

Issue Summary
I'm getting the following error: Invalid character in header content ["Authorization"] on google cloud, on my personal device it's not showing that error.

Hello @DakshMiglani,
How did you solve your issue?
With Best Regards,
Elmer

Yea, so I was running my emailing service on kubernetes which was also supplying it the sendgrid key via secrets, But I didn't realise that it was also adding a '\n' character to it.
That's why later, when I checked the sendgrid api key, it looked like:
"SG_SOME-KEY-HERE\n".
So I stripped that newline character and boom it started working.

Thanks @DakshMiglani! Hopefully your solution will help others experiencing the same issue.
Would you mind adding a PR to our TROUBLESHOOTING.md?

@thinkingserious sure.

Thank you @DakshMiglani!

That saved my day... have been searching the error for hours! thanks!

@Existenziell glad this was helpful! such a pain to deal with such tiny issues!

That saved my day... have been searching the error for hours! thanks!
For me: In Vercel Environment Variables - hit Enter - add a \n to SENDGRID_API_KEY... lol

I think this is the issue I am having but not able to understand what do you mean by hit enter. and add a \n.
Could you please give an example of the value which is supposed to be passed in vercel.
Currently, my value for SENDGRID_API_KEY  is something like in this pattern SG.part1.part2-part3
I am passing the value in vercel as this which is giving the error "SG.part1.part2-part3".
Could you please help how should I pass the value
The shown way to pass environment variable below in the pic is giving error.


I economized 132 MB from my aplication

Please, accept this simple modification for better world.
Thanks for your module, it's beautiful, and i love him.
❤ ❤

For exemple, see size of .exe in:
version v1.1.0 ~> 66 MB
version v1.1.1 ~> 31,2 MB
https://github.com/dotenorio/clipboard-manager-electron/releases

@dotenorio Thank you for the update. I didn't focus much on this project. Good to know this has been used in another project. I am merging the pull request.

Tks man..

Can u update on npm?

It is done as well. But for some reason npm portal is still showing me 1.1.0 as the latest. May be a cache problem. But npm install installs version 1.1.1


Uncaught ReferenceError: process is not defined     at getFingerprint2

I installed this package in My React App and also set my SECURE_LOCAL_STORAGE_HASH_KEY in my .env file but once I call the "import" line, I get the error below. Please any solution to this. I even downgraded to version 1.0.18 still the error persisted. I used Vite to create the React App.
Uncaught ReferenceError: process is not defined
at getFingerprint2 (fingerprint.js:23:8)
at new EncryptionService2 (encryption.js:33:39)
at getAllLocalStorageItems2 (localStorageHelpers.js:32:19)
at new SecureLocalStorage2 (index.js:57:56)
at node_modules/react-secure-storage/dist/index.js (index.js:117:26)
at __require2 (chunk-BHN6OJC3.js?v=c31a19ab:15:50)
at index.js:119:19

Hi @tboy44wiz Can you please provide the Node, NPM and react version which you are using and the command you have run to create the app,

npm version =  8.15.0
node version = 16.17.0

Hi @tboy44wiz Can you please provide the Node, NPM and react version which you are using and the command you have run to create the app,

npm version = 8.15.0
node version = 16.17.0

Do you mind if I contribute to the fixing?

@tboy44wiz You can contribute, and I got engaged with few other work, it might take same time for me to take a look
Please make sure to create a new branch called dev/*** and create a PR, also before creating the PR just run yarn build:lib or npm run build:lib to build the files

@tboy44wiz Can you please provide your react-scripts version and if you are using webpack, then webpack version too?
To solve the "Uncaught ReferenceError: process is not defined" in React, open your terminal in your project's root directory and update the version of your react-scripts package by running npm install react-scripts@latest and re-install your dependencies if necessary.
https://bobbyhadz.com/blog/react-referenceerror-process-not-defined


Fix release go version

Coverage remained the same at 50.0% when pulling dc639cb4b64fa7e735234e0803040abc3537cd4c on fix-release into b7314e786cedc17f0ba128b12c2ebc724cb8bcd2 on main.


Load editor renderer by default

I have overwritten the checkbox provided to load a custom toggler using the Editor renderer.
But the issue is that since "mode" is either "click" or "dbClick" , user will have to click the column twice..on first click the editor renderer will be loaded and second click,editor renderer will toggle the checkbox.
How can I load the editor renderer by default?..i.e without the first click to activate the cell editing.
I have checked all the examples,even the advanced one.Everywhere the user has to first click to initiate the editing since the "mode" is set to "click".Is there a way to trigger the mode?

hello @anuragb26, sorry for lately reply, this requirement was asked before but so far I don't have plan to implement it. I will consider to implement this feature after I get free time.  sorry about I'm too busy recently lol

But another question will be how user perform the saving action?  press enter or I need to render a submit button beside the editor? or any idea?

Apologies for the delay in responding.
Save button cab still be set to  blurToSave: true from the cellEditFactory or the Press Enter which is the default.
I badly need this feature since I have to show a toggle switch in the columns.This will also be needed for anyone needing a radio button or basically any toggle/untoggle like functionality.

i think for my plan so far will be render a submit button if blurToSave is false.

since I have to show a toggle switch in the columns.This will also be needed for anyone needing a radio button or basically any toggle/untoggle like functionality

sorry, I can't get you

A toggle switch like above

@anuragb26 it's clear now.

Any updates on when this functionality would be added? I'd like to be able to render all editable columns in edit mode by default, to spare the users having to click a cell to be able to edit. It also makes it immediately clear which columns can be edited and which are readonly.
Thanks in advance.


do not install package in interactive mode

Specified packages are installed after entering the 'phase: Interactive' by default.
Some packages, e. g. tex, are big and take time to install. To avoid this overhead it would be helpful to to be able to control this behavior.
This minimalistic patch uses the environment variable "POUDRIERE_INTERACTIVE_NO_INSTALL" to specify that the specified packages should not be installed when entering the interactive phase.

This still installs dependencies, just not the main package.  Is that what you wanted?

Yes it is. It would be great to have it.

This makes me wonder, couldn't poudriere save up on build time by not installing the RUN_DEPENDS ?
I mean, RUN_DEPENDS are not needed to build the package (which is the goal of poudriere) they are only needed to run the packages after being installed.  The only thing that is needed is to register the dependency.

Having the runtime dependencies to check the build and the compiled binaries would be useful to me, but the installation is simply not necessary.
phase deinstall: only removes the packages specified to build, but keeps the runtime dependencies installed.
phase interactive: installs the specified packages again (not necessary)

What is the point of installing dependencies but not the main package?

Installing dependencies but not the main package gives you the ability to manually test with executables/libraries/outputs that were built in WRKDIR and therefore saves the time to extract the package to /usr/local. I think that can become one purpose of the interactive mode.

The dependencies are necessary to run tests that are part of the build process.
Another use case is: modify the package sources -> compile changes -> run tests
If the package is already installed you wouldn't know which shared objects, or include files, the tests will use without looking into the details (build directories vs. system directories).

@bdrewery: As I'm involved in the discussion offline as well: The idea is a workflow in which the port is built using poudriere in advanced interactive mode and keep the long running jail open for further port development server side. So the developer pokes into jailname-n and modifies the port skeleton and/or ports sources and builds the port again within the jail, runs various test etc. until development is finished and the build jail is stopped.
This is done using multiple package sets, so that builders can run independently to work on different ports in parallel over time (so e.g. you would have 103amd64-latex-latex, 103amd64-chrome-chrome running in parallel while working on ports trees and ports in parallel). As having the package already installed might have side-effects (like @capjo described), it's preferred to have all the dependencies in there, but not the package in question. Also running pkg delete every time an initial build is done can be forgotten easily and for big ports it's adding a time consuming add/delete cycle for no reason.
It might make sense to make this feature more fine grained though, so one could also skip installation of RUN_DEPENDS like you suggested, I could see some use in that (even though it wouldn't help the particular use case I'm talking about).

Thanks, I'll take it when I find some time to focus on Poudriere again in the next few weeks.

Ok I see the use for this now. I'm not fond of more options though. Not sure how else this would be addressed though.
Is this all actually interactive? We could have a confirmation prompt ask when entering the interactive jail whether dependencies and the package should be installed.

Is this all actually interactive? We could have a confirmation prompt ask when entering the interactive jail whether dependencies and the package should be installed.

In our use case it's not interactive, so there should be some option (env var, command line arg, ...) to control the behavior. Essentially, we run a full poudriere build once, tell it to leave the build jail running (poudriere testport -I) and then use the build jail via scripts (e.g. build with changed source code). This follows existing behavior of INTERACTIVE_MODE == 2 in that it does not ask any questions or enter an interactive prompt.

Can one of the admins verify this patch?

Can one of the admins verify this patch?


chore(ui): upgrade Clockface dependency to 0.0.27

[x] Well-formatted commit messages
[x] Rebased/mergeable
[ ] Tests pass
[ ] http/swagger.yml updated (if modified Go structs or API)
[ ] Documentation updated or issue created (provide link to issue/pr)
[ ] Signed CLA (if not already signed)

Failure seems to be staticcheck running out of resources.  I ran staticcheck locally and it was fine.  Let's go ahead and merge


大佬方便分享下MiniCPM的模型文件吗

在云盘路径里只看到了一个通义的。。

当然可以，请稍等。

Hello,
The MiniCPM-1B-sft model is now available, please git the latest MiniCPM_ONNX-1B Android project to use it. This model has been quantized to the uint8 format to better suit common mobile devices, though this process has resulted in some loss of accuracy despite our best efforts during quantization on the ONNX Runtime framework.


@vue/eslint-config-typescript is implicitly dependent on eslint-plugin-vue

Version
3.0.0-rc.3
Reproduction link
https://github.com/st-sloth/vue-cli-typescript-eslint-parser
Steps to reproduce
npm i
npm run lint-parserOptions-parser

What is expected?
Probably, no errors should be reported.
What is actually happening?
  1:7  error  Parsing error: Unexpected token :

The issue is that eslint-config-typescript puts parser inside of parserOptions instead of the root. Most likely because it is silently expected that eslint-plugin-vue is also used and it defines parser as vue-eslint-parser that in turn uses parserOptions.parser, defined in eslint-config-typescript (with this configuration, there is no error - npm run lint-vue-plugin in repro).
In our team we use sharable eslint configs that extend great vue configs and are split by feature - our TypeScript partial config extends eslint-config-typescript. And in the project using TypeScript without using Vue we now faced the problem that typescript-eslint-parser does not get used as the parser.
Of course, all this is probably by design, and we must explicitly add typescript-eslint-parser in our config (as npm run lint-parser in repro), but I've only come to this realization after hours of debugging, searching through the docs and code of different related repos and such.
Perhaps, at least the reason why in eslint-config-typescript parser is defined inside parserOptions should be explained in the config and/or docs and readers should be warned that in order to use this config without eslint-pliugin-vue they must specify parser themselves?

You are right that this is by design. The config is meant to be used with vue-cli, which means that eslint-plugin-vue will be present and with it, eslint-parser-vue.
Would you be up to send a PR mentioning this in the README?

Yep, I'll do that.


Upgrade python and action versions

coverage: 99.389%. remained the same
when pulling d97e23f795e97f8569917661eeeea4b05600d360 on main
into 7fc66f73b5700f7b9215dbdf4f729686d123ff97 on develop.


ESLint cannot find next/babel when using pnpm

What version of Turborepo are you using?
1.4.0
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Mac
Describe the Bug
After checking out the repository and opening the with-pnpm example and running pnpm install I noticed that ESLint is having issues in the editor. It claims that there is no module next/babel and this error is displayed both in WebStorm and VSCode. My gut feeling is that next/babel is usually referenced as a transitive peer dependency which doesn't work well with the strict nature of pnpm.

The error appears only when opening the root .eslintrc.js and the index.js in the eslint-config-custom package. Linting generally works and running pnpm lint works as well, it is just really annoying seeing errors when editing either of the files. Opening the basic example or a repository scaffolded with create-turbo and using npm instead of pnpm does not have this particular issue.
Expected Behavior
No ESLint errors in any configuration file.
To Reproduce
Open the with-pnpm example in WebStorm or VSCode with enabled ESLint plugins and install dependencies using pnpm. I could reproduce this with v6.32.25 and v7.7.0 of pnpm both installed with corepack.

you can try configuring your eslint plugin to detect your workspaces under vscode settings.
eslint.workingDirectories: [{ "pattern": "apps/*/" }]

i'm still trying to find out why this happens with pnpm in the first place or why this resolves it.

Even though this proposal can also be applied to WebStorm there is an inherent incompatiblity with pnpm that's not fixed by this. For the time being I applied the pattern I used in the nx-version of my repo with declaring ignorePatterns: ['**/*'] in the eslint-config-custom and then reverting this in the .eslintrc.js within my apps and packages as follows:
module.exports = {
  root: true,
  ignorePatterns: ['!**/*'],
  extends: ['custom'],
};

Maybe this patch from Rush, could also improve things:
https://www.npmjs.com/package/@rushstack/eslint-patch

Sadly I won't be able to test the suggested patch since I completely gave up on pnpm again.
Every few months when I try it out there is still issues with packages not adhering to decent standards and thus being incompatible with pnpm. This time around it was prisma... but that is offtopic and another story.

I get a similar error though I am using yarn :(

In root .eslintrc.js adding package manager as "pnpm" should solve this issue.

Try using degit to clone down the directory instead of cloning this whole repo. I've added readme instructions in #1884 and I was able to run npm run lint successfully that way and also don't see any issues in VSCode (which is admittedly not WebStorm, but since we've had multiple issues reported about this, I think it is probably a similar config issue)

I still look to be having this issue 😬

This may be the same root cause as #1911 in that next dependency isn't available, rather than an issue related to pnpm 🤔 . Not sure when I'll have time to dig into it, but our examples/ setup needs a bit of love.

Any update on this issue? When I generate the default project using pnpm create turbo@latest (with Next 13), I keep getting the error "cannot find module next/babel".

found out a hacky way to fix this
create a settings file .vscode/settings.json or add it to your global settings.json
  "eslint.workingDirectories": [
    { "pattern": "apps/*/" },
    { "pattern": "packages/*/" }
  ]

@Hamziss Didn't work for me 😞

@Hamziss Installing next in root package.json solves this but it's hacky solution to me and I don't like it. I used it though.

Merged, going to close for now, but please reopen if this issue comes up again!


Sprite doesn't get loaded

Do you want to request a feature, report a bug or ask a question?
Question
What is the current behavior?
Svg is doesn't get  imported when extract: true
What is the expected behavior?
Svg gets imported.
The best way is to create repo with minimal setup to demonstrate a problem (package.json, webpack config and your code).
https://gist.github.com/srosca/80932a82e55e90c8409c6a6dc09f7e51
Please tell us about your environment:

Node.js version: 8.9.4
webpack version: 3.5.4
svg-sprite-loader version: 3.1.6
OS type & version: MacOX Sierra

@srosca I need a whole package.json and build script to reproduce a problem

@kisenka Repo: https://github.com/CPatchane/test-webpack4-svg
Ref: https://github.com/webpack-contrib/mini-css-extract-plugin/issues/103

the same error with me
TypeError: Cannot read property 'options' of undefined
    at getLoaderOptions (/Users/.../node_modules/svg-sprite-loader/lib/utils/get-loader-options.js:26:80)

Could someone make a PR?

Also stumbled upon this, we replaced extract-text-webpack-plugin with mini-css-extract-plugin and now the svg urls in our css files don't get replaced by the sprite :(

I'm seeing the same error as @rguanghui while attempting to upgrade our build process from Webpack 3 to 4, during which I've also switched to mini-css-extract-plugin (just like @martinkadlec0).
When the error is thrown (from get-loader-options.js:26), the following values are assigned to the variables:
{
  loaderPath:
   '/home/wanecek/work/<redacted>/website/node_modules/svg-sprite-loader/lib/loader.js',
  rule: {
    resource: [Function: bound test],
    use: [ { options: undefined, loader: 'file-loader' } ]
  },
  multiRule: [ { options: undefined, loader: 'file-loader' } ],
  multiRuleProp: 'use'
}

rules.map(normalizeRule) evalutes to [{ loader: 'file-loader', options: null }], which makes the chained find method return undefined, causing an error to be thrown when the undefined.options is accessed.
Is it the getMatchedRule which extracts the wrong rule? Not too familiar with the plugin, will try to dig some more...
if the repo given by @evilebottnawi is insufficient, I can try creating a reproducible demo too... Let me know @kisenka :)

Not that I know of. @kisenka, have you had time to address this? Is there anything we can do to help?


Add Grid Layout

https://github.com/simoneas02/awesome-grid-layout
A curated list of CSS Grid Layout Module or only Css Grid. Inspired by awesome-flexbox
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title.For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should:

Include a short description about the project/theme of the list. It should not describe the list itself.Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
Be added at the bottom of the appropriate category.

The list I'm submitting complies with these requirements:

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
It's the result of hard work and the best I could possibly produce.
Non-generated Markdown file in a GitHub repo.
Includes a succinct description of the project/theme at the top of the readme. (Example)
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate.
Only has awesome items. Awesome lists are curations of the best, not everything.
Includes a project logo/illustration whenever possible.

Placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Has the Awesome badge on the right side of the list heading,
Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.

Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
If you use a license badge, it should be SVG, not PNG.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

Each link description starts with an uppercase character and ends with a period.Example: - [AVA](…) - JavaScript test runner.
Drop all the A / An prefixes in the descriptions.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.

Go to the top and read it again.

This anchor doesnt work: https://github.com/simoneas02/awesome-grid-layout#polyfills

Hi Jogai,
The anchor was fixed: https://github.com/simoneas02/awesome-grid-layout/commit/6c856cdb83a63388632167f52a69e2984a9e373a

Not followed:

Entries have a description
Doesn't include a Travis badge.
Has an appropriate license. - That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Has the Awesome badge on the right side of the list heading,

fixed: https://github.com/simoneas02/awesome-grid-layout/commit/9d97a2309063f23b01d54c1ecd5ba904e81fbe9a

Not followed:

Drop all the A / An prefixes in the descriptions.

Suggestions:

LEARN ABOUT THE NEW WAYS TO DO LAYOUT IN CSS. -> Learn about the new ways to do layout in css.
Describe why we should follow the people

@legodude17 fixed: https://github.com/simoneas02/awesome-grid-layout/commit/4e2fb39fb0836bc094c464719604e265b1d2f339

Nice work! This looks like a useful resource.

A curated list of CSS Grid Layout Module or only Css Grid.

It's not clear what "or only Css Grid" means. I think it can be dropped.

The CSS Grid Layout text in A curated list of CSS Grid Layout Module or only Css Grid. should link to somewhere people can read more about CSS Grid Layout.

The header image should be high-DPI. Set it to maximum half the width of the original image.

Has a Table of Contents section. Should be named Contents, not Table of Contents.

Specification and Working Group - => Specification and Working Group

css => CSS

Drop all the A / An prefixes in the descriptions.

The entries in the Who to Follow section needs a description/bio.
Chris Coyier@chriscoyier => Chris Coyier @chriscoyier (Same with some of the other entries)

ping @simoneas02

ping


V.1.4

…ew the image background of the desktop). And some other minor CSS improvements.
Important to note: i changed the way to assign a width and a height to each tile.

when loading the homescreen-app i take the width of the screen and then i calculate the width/height for the "normal" and the "small" tiles saving these values in the document using a dynamic insertion of CSS styles to the classes "tile" and "small".

at the begining of the CSS file i setted the "box-sizing" to "border-box", which is more convenient for better calculate widths of elements without be affected by paddings ;)

Indeed, Leandro, in the third commit i had to make another important change, because due the changes that i introduced in the HTML rendering of the icons the click over those icons were  generating NOTHING !?
So:

now an icon is a DIV of the class "tile" which has inside 2 other DIVs. Above is one with the class "tile_ic" (it get the click when user tap the screen with her finger), and below there is the "tile_bg", which serves for render a semi-transparent background or a solid-color background.

i had to modify the iconMap.set(tile_ic, icon); command for associate each icon with the DIV "tile_ic" because they are getting the "clicks" ;)

in the definition of the window.addEventListener('click') i use the attribute "rel" of the DIV who receive the event, instead the class you put like "icon_"+wordname[0]. Why? because in this way the code it's more simple and we have separated the classes name (for style purposes) and the "name" of the icon.

I hope you like these changes.

incorporados cambios de Sergio


Target monad instances

Instances of cats.Id, scalaz.Task, etc should be isolated in different modules in order to be imported by users on demand.

#18 closes this issue


⚠ Bofrost.fr has degraded performance

In 65327ca, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1208 ms

Resolved: Bofrost.fr performance has improved in 508a7aa after 6 minutes.


fetches manifests from subdirectory

for parity with https://github.com/user-interviews/rails-server/pull/18160/commits/f7b80ec783893857f9b74590448149609a417a1f

Can clean these up later for us


add chalk and yargs

This PR adds the following dependencies:

chalk for formatting (v4 due to v5 requiring ESM support)
yargs for argument parsing

It also adds a .nvmrc file for standardising on a version of nvm, adds a script for specifically running the cli without a global ts-node.
I've set the commands to be backwards compatible but also to make create-plugin its own command.
Here's a dodgy screenshot of how the chalk formatted output looks

This looks amazing, thanks @arranf!
A couple of small things:

I just added a .prettierrc to the develop branch, can you update and use that? that way we can get rid of the formatting changes in the PR
Can you open a separate PR for the .nvmrc file and another one for the script change? That way we can keep this PR focused on just the chalk/yargs stuff

This looks amazing, thanks @arranf!
A couple of small things:
1. I just added a `.prettierrc` to the develop branch, can you update and use that? that way we can get rid of the formatting changes in the PR

2. Can you open a separate PR for the `.nvmrc` file and another one for the script change? That way we can keep this PR focused on just the chalk/yargs stuff

Done!
I've deleted the .nvmrc changes and I'll open up a new PR for that, I'd like to keep the addition of the the new `cli" script part of this PR though - as I'd consider it part of the scope of the PR which is improving the CLI

@arranf should we also add a version command?
.version(function() { return require('../package').version; })

@arranf should we also add a version command?
.version(function() { return require('../package').version; })

Added.


BirthdayPicker component readme :: doc requirements

The following info is required for the readme doc:

[ ] Brief component description
[ ] Elements: image, short description
[ ] API - Component props
[ ] API - Accepted children: data-slot roles
[ ] API - React Code Examples
[ ] Style API - subcomponents
[ ] Style API - custom CSS states (pseudo-classes)
[ ] Style API - code examples

Issues referenced:
< none >

This component was removed, no readme, the spec will be used in the future so we're leaving it for now.


Certain custom themes can load in Safe Mode

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
If certain custom themes are selected before entering safe mode, they are loaded and activated during safe mode instead of being forced to One Dark temporarily.
Steps to Reproduce

Set a custom theme<EMAIL_ADDRESS>Close Atom
Launch Atom in safe mode using atom --safe
Note that the custom theme is still active and shows as an option in the list.
Select a built in theme (one-dark-ui)
Close Safe Mode and launch Atom in Safe Mode again
Note that only the built in themes show as options in the theme selection list.
Close Atom, launch in normal mode
Select a different UI theme<EMAIL_ADDRESS>Restart Atom in safe mode
Note that One Dark is selected as the theme as it should be.

Expected behavior:
Custom themes are not loaded or available in Safe Mode.
Actual behavior:
Certain custom themes can continue showing in Safe Mode if they was selected before entering Safe Mode:

Atom Material UI is the only one found so far that does this.
Reproduces how often:
100% of the time.
Versions
Not a beta bug 😆.
OS: Windows 10 x64 Enterprise
Atom    : 1.24.0
Electron: 1.6.16
Chrome  : 56.0.2924.87
Node    : 7.4.0
apm  1.18.12
npm  3.10.10
node 6.9.5 x64
atom 1.24.0
python 2.7.14
git 2.16.1.windows.4
visual studio 2015

Additional Information
I've tested this back to Atom v1.17.2, all Atom versions behave the same. I also tested with<EMAIL_ADDRESS>and found the same behavior.

I would like to assist with this issues, is there anyone who can point me in the direction of where there is a check for safeMode and determines themes.

I would probably start in config.js as that is where the configuration is being loaded, however I don't know for sure where this bug actually is.


[BUG] FutureWarning when using to_schema with a Pandas-like (but not Pandas) obejct

Minimal Code To Reproduce
Strictly speaking not a bug, just a warning, but this warning is spamming standard output; and could become a bug in the future.
Lets' use Dask data frame as an example of a Pandas-like (but not Pandas) object:
import pandas as pd
from fugue_dask._utils import DASK_UTILS

import dask.dataframe as dd

df = pd.DataFrame({"a": [1, 2, 3], "b": [4, 5, 6]}, index=[1,2,3])
ddf = dd.from_pandas(df, npartitions=2)
DASK_UTILS.to_schema(ddf)

throws warnings:
[REDACTED]/.venv/lib/python3.10/site-packages/triad/utils/pandas_like.py:116: FutureWarning: Series.__getitem__ treating keys as positions is deprecated. In a future version, integer keys will always be treated as labels (consistent with DataFrame behavior). To access a value by position, use `ser.iloc[pos]`
  tp = df.dtypes[i]
[REDACTED]/.venv/lib/python3.10/site-packages/triad/utils/pandas_like.py:116: FutureWarning: Series.__getitem__ treating keys as positions is deprecated. In a future version, integer keys will always be treated as labels (consistent with DataFrame behavior). To access a value by position, use `ser.iloc[pos]`
  tp = df.dtypes[i]

I believe it's just a matter of changing
tp = df.dtypes[i]

to
tp = df.dtypes.iloc[i]

Describe the bug
When a Pandas-like object is passed to to_schema, a FutureWarning is thrown. This does not happen with Pandas data frames, because they do not reach this part of the code.
Expected behavior
No warning.
Environment (please complete the following information):

Backend: pandas/dask
Backend version: dask==2024.1.0, pandas==2.1.4
Python version: Python 3.10.13
OS: macOS.

Thank you for reporting, will look into this


Change default TypeScript behavior to strict: true (fix #41)

This PR enables strict: true diagnostic errors from TypeScript (only when the "Display Errors" checkbox is checked), as requested in #41.  Example:

But I'm having some trouble with this turned on and the variable actually gets used (so it doesn't get tree shaken away).  It seems that TypeScript is somehow processing the same file twice, which leads to new errors:

It seems that src/components/editor/monacoTabs.tsx's MonacoTabs creates two models: the model at the top of the function and the model for each tab in tabs.  I'm seeing the same source code in both the root model and a tab, which is presumably the source of the problem.  Why this isn't a problem without strict mode, I'm not sure.  @amoutonbrady Could you explain what's going on here?  Could we remove one of the duplicates (presumably the top-level model?)?

This is an issue with files that don't have imports or exports and are then treated as a global script file. One trick might be to add a tsconfig flag to ignore output_dont_import.tsx?

@modderme123 Thanks for the tips! I didn't realize it was the lack of import/export that was causing the problem, and that it's an existing issue with the playground. I'll move this to a separate issue (#104).
This PR is now ready for review.

Here's yet another example of confusion that this PR will fix: https://github.com/solidjs/solid/issues/972

Thanks!

Looks like this has one side effect, the default example shows an error :/

Looks like this has one side effect, the default example shows an error :/

Ha, whoops; sorry I didn't notice that. It's a useful error message though: document.getElementById can be null which would cause a crash.
One natural way to write this line in TypeScript is this:
render(() => <Counter />, document.getElementById("app")!);

But maybe we want to avoid TypeScript-specific notation in our opening example -- that seems like a nice property to maintain.  So then I'd suggest:
const app = document.getElementById("app");
if (app) render(() => <Counter />, app);

It's a little wordier, but is definitely safer.  What do you think?

Oops, I pushed a commit before I saw this opting for the first one. I'll deploy in a minute

No worries! ! is a good choice too.


Current upload does not support inclusion of mime-type

Our current upload/update methods do not include the mime-type. As such, when we upload photos to storage and download them again they don't render properly.
The current fix was proposed by John on the discord channel. We should integrate it in so that Users can download/use photos.
    multipart_data = MultipartEncoder(
        fields={
            "file": (
                "party-parrot.gif",
                open("./out/party-parrot.gif", 'rb'),
                "image/gif"
            )
        })

    formHeaders = {
        "Content-Type": multipart_data.content_type,
    }

    headers = dict(supabase._get_auth_headers(), **formHeaders)
    response = requests.post(
        url=request_url,
        headers=headers,
        data=multipart_data,
    )

Hi there.
I am looking for some projects to contribute during this year's Hacktoberfest and I stumbled upon this one.
Supabase is a very cool initiative and I'm willing to help. :)
I would like to know if this issue is still available/open to assignment. The description above mentioned someone, John, is he already working on it?

Nope, not to my knowledge. Feel free to file a PR

This issue should be closed right?

It should indeed. But I believe that only the author or someone with admin privileges are able to close it.
Maybe @J0 can.

Yup @julianolf,
We are closing for now but feel free to let us know if you still face any further issues.
Thanks!


Changed properties to camelCase

Merge at your leisure....

Examples are not updated to work with these changes. Not merging until they are...


Node Optimist being Deprecated

So, i noticed that Optimist is being deprecated and won't be supported in the future.
It might be a good idea to use some other plugin:
https://github.com/substack/node-optimist

On Optimist’s page, it recommends yargs. Just swap the module, no code change required. :)

minimist


feat: add scarb rm

Implementing issue #93
Adds remove command with rm as alias. Currently, all it does is just removing the specified dependencies from the dependency table of a manifest file. It doesn't do any workspace clean up like cargo rm as there's no support for proper workspace yet as well as other types of dependency (e.g., dev, build).
I tried to refer as much as possible to cargo, so if there's anything lacking please let me know.

Also FYI: I will probably squash this PR, we used to combine related tests with commits that introduce tested logic :)


Various cleanups around pkg/datapath

Best reviewed by commit.

/test

/test-1.23-net-next

/test-runtime

Kind conformance test was failing due to #20034 which was fixed by #20039 in the meantime. Reviews are in and all other required tests passed. Marking as ready to merge.


chore(anchorlinks): Switch AnchorLinkHeader to .tsx

This adds an interface with two any values. We should eventually be
more explicit about the type, but the helper this function relies on
must be any.

Is Metadata really the only place using anchor link header stuff that's been migrated to TS?

Metadata is the only .tsx place using anchor links that I know of.


fix: webhook certificate issue

Pull request description
Fix issues with admission webhooks rejecting CRUD operations because of missing caBundle in the admission webhook configuration
Checklist (choose whats happened)

[ ] breaking change! (describe)
[x] tested locally
[x] tested on cluster
[x] added new dependencies
[ ] updated the docs
[ ] added a test

Breaking changes

Changes

Use kube-webhook-certgen for certificate create and admission patch

Fixes

Issue with webhook server rejecting requests due to invalid certificate

@kubeshop/testkube
NOTE: we will need to delete the existing webhook-server-cert secret as it is not compatible with our current implementation.
Just by deleting the testkube Helm chart will not delete the secrets created subsequently or by parent resources.

Can we provide any migrations for this?

@vsukhin
We could add an initContainer which deletes the secret if it already exists in the webhook-cert-create job, and then the main container will create the self-signed cert and the secret

That sounds like a good plan, we will need to make transation to changed version as smooth as possible

@nicufk this tool generates a long-lived self-signed cert (100y), and I guess that is fine, because this certificate is used only internally and for a very specific use case, no room for malicious intent even if it gets leaked somehow


EV11

Changes for EV11

[ ] Fix schematic errors
[ ] Fix schematic warnings
[x] Fix PCB errors
[ ] Fix PCB warnings
[ ] C33 does not have LCSC part number but other caps of same value do
[ ]  snap EDA stuff seems to have leaked in on BQ21040DBVR
[x] Match JLCPCB USB-C Footprint and Symbol
[x] Swap PB5 and PC12
[x] Swap PB4 and PC11
[ ] Test points on ALL signal traces, including clocks, and mics (using a normal 90 degree header)
[ ] SDO and JTAG connectors
[ ] Move battery connector to not be in the way of the keyboard connector.
[ ] The EEPROM should have an identifier like U? not CR1
[x] U4 has the wrong footprint
[x] ESP32s3 might have the wrong foot print
[ ] Attach SPKGND and AGND for wm8960
[ ] Mounting holes for screen
[ ] Move boot and reset buttons to be easier to press.
[ ] ADC for measuring battery voltage (Needs a voltage divider to protect ADC).
- This should come after the power switch to not burn energy through the divider
[ ] Plug in detect (Also voltage divider but on the 5v rail)

Can be on the USB power in?

@fluffy I've moved a lot of the requested changes from the PR #89 to here.

https://github.com/Quicr/hactar/commit/1fbbdc0f04e59ff6a59bf5608b80b71c2ae7d91c


Error: #3005 (activateOnceError): You need to be activate Adapty once

Hello,
We just upgraded to version 2.2.1. We migrated to every function and new stuff.

import { adapty } from "react-native-adapty";

useEffect(() => {
  (async () => {
    await adapty.activate(ADAPTY_SDK_PUBLIC_KEY);
  })();
}, []);

Here is my activation code on App.tsx.
Each time it gives me the Error: #3005 (activateOnceError): You need to be activate Adapty once and we do not call adapty.activate else where for sure.
Even sometimes it gives #2002 (notActivated): The Adapty is not activated but probably it is because of the development environment and stuff.
What should I do to fix this warning? It was all working great on the 1.3.13 version. I’m thinking to downgrade the version.

Hey!
I do not see any way to get notActivated after activateOnceError. I'm going to need a reproducible snippet for that, if you are able to make one.
About activateOnceError. This is not an incorrect behavior as is. You activate adapty once you cold boot your application. Hot reload/Fast Refresh technology re-executes useEffect and most other hooks on every refresh, whereas activation status persists.
Now, I'm to blame for not giving enough thought about this being a problem. I persisted only one call with useRef<boolean> or just wrapped activate() into a try {} catch {} block to ignore the error.
I'll try to make something smart for the following release, that would not incorporate any complex logic. In the meantime, can you try any of my proposed solutions?

Thank you for this awesome comment and suggestions :)
I will try to ignore it and also try to reproducible example for you

Hey again @divanc
https://github.com/WrathChaos/adapty-v2-error-example
Here is the reproducible example. All you need to do is replace the api-key and run the ios.
The try-catch console.log will appear each time.
I put my useIAP custom hook just in-case you want to check it out if something wrong on my code. But it always happens even without my custom hook either.
Can you please take a look at it?
Maybe is it because of my react-native version? (0.68.5)

Since I found you, let me ask an off-topic about adapty :)
I wonder what is the best practice for checking and setting the user's premium data. Do I need to check and save the user's premium profile each time on my backend side? Or should I even need to save this data for each month? Like saving the receipt and stuff?

Thank you so much! @divanc :)

Since I found you, let me ask an off-topic about adapty :)
I wonder what is the best practice for checking and setting the user's premium data. Do I need to check and save the user's premium profile each time on my backend side? Or should I even need to save this data for each month? Like saving the receipt and stuff?

I've asked my colleagues to provide you a better answer, than what I can give you 😅
Here is what I think:
If you have fully integrated Adapty in your paid content chain, then there is no need to duplicate anything to your side for validating purposes. At least, I haven't developed an app at such a scale. Adapty works directly with native StoreKits, so if a StoreKit and Adapty API are available, then the chances that you would get an incorrect status is minimal. If Adapty API is unavailable (I cannot remember such an occur in the last 2 years), then SDK would provide you a cached result.
This is another nice point. Adapty SDK does caching and a number of other things under the hood. If you would wait for your API to approve subscription status, then what about the case when user does not have internet? Adapty handles such cases to the best of my knowledge.
The only question is why really. If you can answer that, then there might be a reason. You just need to know that it would take quite some time to implement a nice validation solution and then debug it.
I may have misunderstood your question: please, correct me if I have given you an unrelated reply.

Testing your reproducible...

I did the following:

yarn install
cd ios && pod install
added my token
xed -b ios (launches Xcode)
Added my Bundle ID
Added my team for signing cert
Removed previous watchman logs
yarn start
Run on device in Xcode

I get the following:

It is rather strange, that it somehow without Swift bridging header...

'Server error' is about not finding paywall, I guess?

Localization is not good in that manner
I totally agree that activate is throwing an error more often, than preferable. Going to do something with it

While I was unable to get notActivated after activateOnceError, you can try an experimental feature in v2.2.1 — lockMethodsUntilReady. It makes all your calls wait until activate is resolved, so there wouldn't be any race condition.
adapty.activate('KEY', {
  lockMethodsUntilReady: true,
});

@divanc
I do not get Server error, actually I am able to fetch my paywall, products and even the profile has a premium or not.
I tried to use the lockMethodsUntilReady one but it just throws much more error than activateOnceError. So it is not a solution for me. I could not even call the paywall with this prop.

Testing with my paywall IDs...

Do you think anything else which I can provide? @divanc

Hey, sorry for being absent! Pleases check what I've found with your app:
Let's say, there are two purchase blocks in your app:

activating Adapty (my version)

useEffect(() => {
    async function fetch() {
      try {
        console.log('Registering adapty');
        await adapty.activate('TOKEN');
        console.log('Register: SUCCESS');
      } catch (error) {
        if (error instance AdaptyError) {
          console.log('Error activating', error.message);
        }
      }
    }
    fetch();
  }, []);

fetching a paywall, initiating your sub-SDK

const {isPremiumActive} = useIAP();

And I had somewhat consistent behavior: if I have declared activation promise before paywalls promise, then error is not raised. So in your App.tsx I have 1 → 2, Doing 2 → 1 seemed to result in this error you face.
Now I certainly understand that this is an insecure way of activating an sdk, but this somehow works until I can make something better! Also in your app lockMethodsUntilReady works just nicely for me. Can you provide some logs on that?
2 → 1 logs
JS Registered
Running "adapty" with {"rootTag":1,"initialProps":{}}
Fetching Paywalls...
Registering adapty
Paywall error:  Error: #2002 (notActivated): The Adapty is not activated
Register: SUCCESS

1 → 2 logs
JS Registered
Running "adapty" with {"rootTag":1,"initialProps":{}}
Registering adapty
Fetching Paywalls...
Register: SUCCESS
Paywalls: SUCCESS
Fetching products...
Products: SUCCESS

I plan to move activation outside of components to be hooked by JS interpreter before components mount, like on picture below:

But, I still need

To read a lot to understand how it works deeper, so background caching, event emitter and stuff wouldn't break
Probably to introduce another activation design in that case, as I consider this of another design pattern

Hello @divanc
Thank you so much for the detailed answer!
I tried both ways to activate the the adapty but I still got the errors something like this:

I simply copy-pasted this into my App.tsx
useEffect(() => {
async function fetch() {
try {
console.log('Registering adapty');
await adapty.activate('TOKEN');
console.log('Register: SUCCESS');
} catch (error) {
if (error instance AdaptyError) {
console.log('Error activating', error.message);
}
}
}
fetch();
}, []);

and then I have a straightforward react-navigation that just navigates my HomeScreen and I am simply calling my `useIAP` custom hook.

const { isPremiumActive } = useIAP();

In this hook is almost identical with the given repo example.

I got it, it is something wrong with my implementation, but I don't know how to wait for the activation because it simply does not wait for the activation and just tried to do something with the adapty.

I also tried to move it outside of the components to be hooked by the JS interpreter before the components mount on App.tsx but simply it gives the same error.

But this way, it looks like there is no way to wait for the adapty activation to re-use the adapty inside the other components, screens?

Let's reiterate — we're facing two problems:

3005 (already activated) throws more often than it should (in your example should not throw at all)
2002 (not activated) is being thrown in your example in paywalls section, although it should not. lockUntilReady thing does not help

Are there two all we discuss so far?

Hello @divanc Thank you so much for the detailed answer!
I tried both ways to activate the the adapty but I still got the errors something like this:
I simply copy-pasted this into my App.tsx
useEffect(() => {
    async function fetch() {
      try {
        console.log('Registering adapty');
        await adapty.activate('TOKEN');
        console.log('Register: SUCCESS');
      } catch (error) {
        if (error instance AdaptyError) {
          console.log('Error activating', error.message);
        }
      }
    }
    fetch();
  }, []);

and then I have a straightforward react-navigation that just navigates my HomeScreen and I am simply calling my useIAP custom hook.
  const { isPremiumActive } = useIAP();

This hook is almost identical with the given repo example.
However, when I call the adapty activation into component's useEffect like a componentDidMount, I just get this error:

Outside the component is making lots of unhandled promises :)
I got it, it is something wrong with my implementation, but I don't know how to wait for the activation because it simply does not wait for the activation and just tried to do something with the adapty.
I also tried to move it outside of the components to be hooked by the JS interpreter before the components mount on App.tsx but simply it gives the same error.
But this way, it looks like there is no way to wait for the adapty activation to re-use the adapty inside the other components, screens?
I can use it with try-catch to ignore the error but I think it should not be like this right? :)

In your attached screenshot I can see an interesting thing: you have an unhandled promise rejection about activating more than once. Also you said, that you've taken my fetch function to your flow. But my fetch function should not be able to throw an unhandled error, since it wrap all the body in a try-catch block.
Can you check, there is no other place, where you try to activate?

@WrathChaos please, check out v2.3.0!
With this release I was able to solve both of your errors on my end.
To prevent paywall fetching before activation mutex, I moved it outside of component as you can see in example App.tsx.
You can call this activation in any JS file, just make sure to import it to your core.

Wow! Thank you so much @divanc
I will try it out today!

More information:
When I use lockMethodsUntilReady more unhandled promise rejection are appears.

If I do not use lockMethodsUntilReady, try-catch can handle the error and I am still able to fetch profile, paywall etc

Sorry, had to jump on another task. Diving in...

@divanc Is there any news? :)

Sorry for not responding sooner, had to be offline for several days 😓
Your example made my log go crazy for a bit too. Although I tweaked your code a little and the problem was solved for me:

Instead of 'TOKEN' string I placed my test token, same for paywallID, Apple Team ID and bundle ID (duh)
I removed second activation of adapty in useEffect, that seemed to cause that hustle in logs. Here is my diff:

In your repo, this is /App.tsx:46

Can you confirm that this works for you?

@WrathChaos ping for the info 🏓

Hey @divanc
I will check it out this week :) sorry for the late response, some health issues

Hang in there! 💊

v2.3.5 MUST solve your issue! I'm going to write some more here today

I will try it out today and let you know

@divanc
It works! Thank you so much for helping sir!
🥇

@divanc Thank you for the detailed explanation but also a great catch :) At least you were able to solve it. Big kudos to you sir!


Error in accumulators

I am running 1.4.3 and I was getting errors running the accumulators
I put in a local hotfix at
https://github.com/joequant/OpenCEX-backend/commit/5a248aeba2035c0c18ccd4af314815202c2a6833
which seems to fix the problem.

fixed


Dynamically updating RBAC network filter

Title: Dynamically updating RBAC network filter without connection draining
Description:

I plan to use Envoy's RBAC Network filter for authorization, and I want to understand the behavior around updating the RBAC's rules and connection draining. Am I understanding correctly that the RBAC filter will drain connections upon any change? If so, is there any way to avoid connection draining when only updating the RBAC filter's rules? In particular I am planning to update the list of principals for the filter, and need to avoid draining connections.

[optional Relevant Links:]

https://www.envoyproxy.io/docs/envoy/latest/configuration/listeners/network_filters/rbac_filter

That's not supported unfortunately. Any change in RBAC triggers a drain even if the new RBAC allows existing connections.

I see, thanks @kyessenov. I have a usecase to filter connections on proxy protocol header values, and we want to update the allowlists without draining connections (ideally). Is something like external auth our only option at this time?

You could try wrapping RBAC into ECDS and updating RBAC config dynamically this way. But that would not retro-actively apply new config to the old connections.

Right, I think we would need it to apply the config to old connections as well.

This would be a new feature. We were thinking about supporting it in ECDS, but it requires an effort to retrofit the filters to apply to the existing streams.

Listener filter chain matching work incrementally. If you add/remove chains, only the connections in those chains are affected, regardless of the initial matching logic.


Fix Network dependency for some RPs to unblock Network release

This is part of https://github.com/Azure/azure-sdk-for-net/issues/35786, and to unblock the coming Network release https://github.com/Azure/azure-sdk-for-net/pull/34959

API change check
API changes are not detected in this pull request.


Add taxon and area params to plot_frequencies_time_series()

Re: issue #182

Do we want to add tests for these new param? Note: existing tests only run fig = api.plot_frequencies_time_series(ds, show=False).
Do we want to support lists of taxa or areas? We could upgrade this functionality to accept lists of strings (of taxa or areas) as well as single strings.

Do we want to add tests for these new param? Note: existing tests only run fig = api.plot_frequencies_time_series(ds, show=False). [Examples of usage were added to the existing notebook, which might suffice.]

Having the notebook examples is nice. We might also need to add some unit tests to maintain coverage.


Should include "YouCompleteMe" for coding

I am learning coding in Vim, I think it should be included "YouCompleteMe" plugin, it would be great for coding

It's a great plugin, but it has a lot of dependencies. You can easily install it by following this guide:
https://github.com/amix/vimrc#how-to-include-your-own-stuff


add CommonName to generated certificates

Adding a CN to the subject makes generated certificates usable in DSM (Synology).
I created a certificate, uploaded it to my DSM and are able to use it for example as "System default" certificate. Also DSM now shows a "Issued to:" value:

Without this patch, "Issued to:" was empty and the certificate was not selectable for any usages.
Fixes FiloSottile/mkcert#469

Hey @FiloSottile , just wondering if you've had a chance to take a look at this pull request? I think it's good to go, but let me know if there's anything else that needs to be done. Thanks!

@elexx I actually went ahead and built from source on Windows to add this pull request. I also have a Synology Disk Station and although it handled the cert imports fine on mine, I just liked having the CN label to easily differentiate between my different certs. Thanks for this!

I've built from source as well after applying the changes in the PR, but the certs still appear "blank" in Synology DS for me, as described in the initial comment buy @elexx. Unlike @LibbyJax I can't work with them in the UI either, they are unselectable for example in Security > Certificates > Settings where you would set a cert as the System default. Don't suppose either of you have any ideas?
Any idea why this PR hasn't been merged in?

add CN to generated certificates · elexx/mkcert@49fec4a
https://github.com/elexx/mkcert/commit/49fec4a21908ddf9cb3600fed28ea9c6de8bca93

For me this problem still exists. Any idea on how to fix this?


https://forest-97q.begin.app/ Down

https://forest-97q.begin.app/ Not reachable

See https://dimsum-0gd.begin.app instead


[WIP] Update use-nfs-volumes.md

Adding instructions for using NFS volumes with Swarm. (Work in progress)

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Deploy preview for modest-edison-79d82e ready!
Built with commit 845fcc85f7ffa80799c861c3285309e15abc350c
https://deploy-preview-7215--modest-edison-79d82e.netlify.com

@kavikat Please let us know if this is a WIP or ready for editorial review. Thanks!

@kavikat is this information still relevant? The original page appears to have been deleted so it may be simplest to create another PR adding a new page.

Closing the PR as it relates to UCP


[DOCFIX] Update scalability doc

What changes are proposed in this pull request?
Added a few improvements to the scalability doc

alluxio-bot, merge this please

@Xenorith could you help cherry picking this? Thx

alluxio-bot, cherry-pick this to branch-2.8 please


should add docs how to check and fix hosts file with $ vagrant hostmanager

check the VM's IP address
ping the associated domain to make sure it should ping the VM's IP address
if not:

$ vagrant hostmanager
and check the hosts file manually (how to open, edit, modify on Linux? Mac? Windows?)

extension task, so close.


Support Gemini LLM and Embeddings on VertexAI https://github.com/llm-tools/embedJs/issues/46

Added support for Gemini model and embeddings on VertexAI.
This PR also provides example and documentation on how to use, including updates to the main README.
Implemented with:

Langchain integration for LLMS on VertexAI: https://js.langchain.com/docs/integrations/llms/google_vertex_ai
Langchain's community integration (Experimental) for textembedding-gecko on VertexAI: https://js.langchain.com/docs/modules/data_connection/experimental/multimodal_embeddings/google_vertex_ai

Related Issue:
https://github.com/llm-tools/embedJs/issues/46

Thanks for sending in the PR; it's quite well written. There is one actionabale change that I think should be done pre-merge -

Rename the embedding model to reflect the actual model

Apart from that, there is an update I would like to do on the dependency front. I will do this and publish a new version post merge. What do you think about the change above?

Thanks for sending in the PR; it's quite well written. There is one actionabale change that I think should be done pre-merge -

Rename the embedding model to reflect the actual model

Apart from that, there is an update I would like to do on the dependency front. I will do this and publish a new version post merge. What do you think about the change above?

Thanks for the review.

Makes sense. Will need 1-2days to get back on this.
The mentioned dependency  comes from the documentation for the Embeddings' module on Langchain. Let me double check if it is really needed and how the module is using it and will update you on this matter.

@adhityan Just to summarize the changes:

Renamed the model to GeckoEmbedings and updated the corresponding example and READMEs
Bit tricky. I tried to follow the dependencies of the related LangChain modules and it differs for the Model and for the Embeddings as follows:

The Model already adds it as peer dependency: @langchain/google-vertexai -> @langchain/google-gauth -> google-auth-library
The Embedding does not install it - it relies on experimental module, part of @langchain/community. However it needs it.

tl;dr I suppose that we can safely skip it for now. We already have installed @langchain/google-vertexai (and its peer dependencies).
Please, take a look at the changes, it should be ready for merge.

Thank you. LGTM. I will merge it now. Changes will be published to the next library version by end of week.


Fix: Type of Notification.ID was int64. Change to ID

Now mstdn.exe timeline works fine, but
$ mstdn notification
json: cannot unmarshal string into Go struct field Notification.id of type int64
exit status 1

Notification.ID remains int64. Replacing int64 to ID, mstdn notification works fine.
If there are no problems, would you merge ?

Coverage remained the same at 85.755% when pulling 74f003d4a4cdb85187571c071955201deccd6fa0 on zetamatta:notification-id into 730317321abbdea25c96311c94eee46ca253dfc9 on mattn:master.

Coverage remained the same at 85.755% when pulling fe913e01e56f7a0d1105126450f9ffe9a30e774b on zetamatta:notification-id into 730317321abbdea25c96311c94eee46ca253dfc9 on mattn:master.

Thank you


Release Request: Qnap qpkg

Hello,
I would love to run this service on my NAS, which is always turned on anyway.
Thank you!

I was able to run it on my QNAP NAS in Container Station


Fix the behavior that was broken

by the merge of the ssa refactoring into function-return PR, the previous behavior is restored but it should be refactored again when we will support multiple return values.

What behavior was broken that this fixes?

So the code that I modified in this PR was in the #221 PR before I merged the refactoring. It enable support for functions that are used without assigning them, for instance constrain f(x) == 3.
The point is I did all the tests with this code , which is valid for functions that return only one value, so this is both working and required.
Obviously this is not good for multiple return values and this will be fixed. I have the multiple values PR ready, I just need these fix PRs to be merged first.
Long story short; this is a quick fix that will be cleaned with the multiple return PR.


Render module tree per package in the content page

When rendering content page for multiple packages it is useful to split the
module tree per package.
Fixes #1493

@coot This looks good, thank you very much!! I'll merge once CI passes. :)


PublishTestResults does not publish test attachments for NUnit tests.

Environment

Server - TFS on-premises, version 16.131.27701.1

Agent - Private:

Capability name
Capability value

Agent.OS
Windows_NT

Agent.OSVersion
10.0.14393

Agent.Version
2.131.0

Issue Description
The published NUnit test results do not contain any test attachments, even if the respective test results XML does list them.
I looked at the source code of Microsoft.TeamFoundation.TestClient.PublishTestResults,  Version=<IP_ADDRESS> and the attachments are only published for TRX logs.

We have fixed this issue sometime back. can you please try it and confirm. We haved it in Agent version >= 2.136

I need to check if we can upgrade the agent.

HI,
Did you able to validate it ? It will be great if you can confirm,

We have an on-premises TFS 2018. It does not seem to come with the agent of the version you mention. Do I just download a newer agent from somewhere or must the TFS server be upgraded too?

You dont need to upgrade server but you can download newer agent from github releases and configure, agents are compatible with older TFS server. Let me know if you face any issue.

A quick update - we upgraded the agent. I will monitor to see if there is any change.

@MarkKharitonov Any Update on the issue, can i mark it as fixed ?

I did not have the time to test it yet. Please, keep the issue open. I will try to find the time during this week.

I tested and it works with the new agent.
Thank you.

Closing the issue based on @MarkKharitonov response above.


Migrate to neo4j/graphql library in Hub

Description
As https://github.com/neo4j-graphql/neo4j-graphql-js is now deprecated (see explanation), we need to migrate to https://github.com/neo4j/graphql.
Unfortunately, at the time of writing this description, @additionalLabels directives are not supported - and we use them for zero-downtime content update in Hub.
Reason

The neo4j-graphql-js library is now deprecated and no longer maintained. The neo4j/graphql solution is official library from Neo4j, which we should pick as our solution for Hub GraphQL API.
After bumping security vulnerabilities, we broke GraphQL API contract: https://github.com/capactio/capact/pull/378

Links

https://neo4j.com/developer-blog/announcing-stable-release-official-neo4j-graphql-library-1-0-0/
https://neo4j.com/docs/graphql-manual/current/guides/migration-guide/

This issue is no longer blocked, as the @additionalLabels are now supported. However, IMHO we should put this task on hold until we know what's our target database solution is.

For now, we will stick with Neo4j, and due to an increasing number of conflicts due to out-date libraries we need to address that in the near future.


Access and extract the fulltext of pubmed books

It should be possible to access and extract the fulltext of the pubmed books (e.g. GeneReviews) via the PubMedArticle class.

Is there a way to do it anyway? I am not able to retrieve the fulltext


README.md: Describe local development

Mentions how to run/skip integration tests. At the moment, Fahrschein integration tests do not work with PostgreSQL14.

👍

:+1:

:+1:

:+1:

:+1: