[sql] Add support for "add column" schema changes

This PR implements SQL statements of the form
ALTER TABLE t ADD COLUMN <column>

under the restriction that <column> is either nullable or provides a default.
That restriction ensures that schema changes are backwards compatible and the orchestration layer can still communicate with clients on old schemas.
Views/joins/aggregates/etc. on the table will update as expected.
The schema migration happens in place and under a lock, and I haven't done any perf tests adding columns to large tables.  But, schema migration is a relatively infrequent operation and this has been designed to ensure that subsequent operations on the table pay no extra cost based on the table's schema history.

Sorry, just seen this PR. Writing docs is exhausting and I need a break! Will look at this very soon.

Marking as ready for review again now; fixed the issue I found while working on extract-column and improved the test coverage to cover it with (1) views over views over altered tables and (2) multiple alter-tables in sequence.
Merge looks trivial, so I'll hold off on that until after review/edits.

I'm curious about the eager approach to rebulding everything. Did you look much in to what it would take to do this incrementally? Could even be lazy about it and do a 'read repair' until a row is changed or purge kicks in and at this point write in the nulls.

I looked into it a bit, leaving the old data in place and setting up an incremental computation from it to a new directory.  I decided to go with this eager approach when thinking about adding multiple columns over time, and wanting to avoid paying maintenance cost or growing the incremental computation graph based on that history -- instead, the DB knows only about the current schema and other operations all work as before.
I'm thinking that extract-column schema migrations will need to maintain reactive views in order to serve clients on the pre-extraction schema, though.  Still working out the details there.

I guess this gets pretty tricky for downstream views that need their schema changed.

And this too :)


Ability to use in command line as well

In which part of the interface would this feature applies?

[x] 1. Load your data
[x] 2. Choose a chart
[x] 3. Mapping
[x] 4. Customize
[x] 5. Export
Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
Ability to use RAWgraphs from the command line as well to generate graphs, where each parameter can be passed in the command line.
Describe alternatives you've considered
Raw python scripts.
Additional context
None

+1 would love this as well, I frequently need to make a lot of the same chart with different data. If I could run a cli-based tool that takes all the necessary arguments and a CSV to produce a PNG or SVG that would be amazing!


c#: projects with <OutputType>Exe</OutputType> don't generate cabi_realloc when compiled

Also a further problem I found was that it becomes necessary to declare <IlcExportUnmanagedEntrypoints>true</IlcExportUnmanagedEntrypoints> if you have <OutputType>Exe</OutputType>, otherwise the compiler won't generate any export for cabi_realloc at all and therefore the component wouldn't satisfy the spec.
Originally posted by @SteveSandersonMS in https://github.com/bytecodealliance/wit-bindgen/issues/760#issuecomment-1835758603

Now we use a separate mechanism for cabi_realloc this should be fixed.


readme: refer to correct project.

Probably copy/pasta?

?

That was an accident.  I deleted the master branch and it must of closed the PR automatically.  I'll manually merge.  My bad!


getTradeOfferViaAPI provided. returns array for now

I just implemented it: https://github.com/waylaidwanderer/PHP-SteamCommunity/commit/a86f89c84158db35a8f133cb82432c49ee3b530b
Thanks though!


Top of page should display "mnemonic" instead of "seed"

See screenshot.

Chris, I guess the menu need to be updated to.

Will "Show mnemonic" work?

Yes, that works.

Will be pushed soon


Added Purge Command

Added a command to purge/delete desired number of messages from a channel.
-Need to have admin permissions.
-By default it will delete last 5 messages (including the command).

Hey there! Thank you for your contribution for the Discord.py bot of HackSquad!
I'd like to have a few comment about your command:

Purge should not have a default argument (Actually 5), otherwise, when using !purge, 5 message will be purged and this might not be good in case someone just wanted to see the help.
Your command should preferably have a doctoring explaining the command's purpose.
Your command should return a feedback, telling that the purge has been completed or not.

Hey there @imCHiGi, the project has been rewrite from A to Z.
Your changes are probably out of date, do you mind updating them?
It would be nice if you can make a moderation cog so that it can easily be worked on more safely!
Thanks for your understanding!

Closing as there was no update on this.


⚠ Bofrost.at has degraded performance

In 9d256a3, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1642 ms

Resolved: Bofrost.at performance has improved in 0389841.


Reconsider whether it's safe to rely on recent Uglify versions

I don't have all the context but just flagging to look at this before cutting 2.x.
https://mobile.twitter.com/AdamRackis/status/987346564527116288
https://github.com/facebook/react/issues/12555#issuecomment-379274977
https://github.com/facebook/react/issues/12434

Unfortunately, babel-minify is really slow: https://github.com/mozilla-neutrino/neutrino-dev/pull/809#issuecomment-383311318.

I’d be cautious with that too because we couldn’t get it to work reliably enough at FB about a year ago.

Other than build times, babel minify hasn't been too bad. I have been bit before by variable name mangling though, which was painful to debug. We are in a tough period right now with both Uglify and Babel minify not receiving the maintenance love they probably need.

We've switched to Terser.


Weight computed twice

Hi, I've looked at your repo and I'm not getting expected results wrt using weights.
The weight is applied with
weights = self._get_weights(target).to(x.device)
Yet it is done again in focal_loss/focal_loss.py#L88
Is there something I'm missing? When I remove weights from L88 I'm getting expected results that are equal to a torch-based WeightedCrossEntropyLoss

If you believe this is a bug I can submit a PR fixing it

self._get_weights(target) does not just retrieve the weights


fs: fuse: Avoid possible buffer overflow

Checks path's size before copying it to local variable.

@de-nordic would you mind taking a look again ?


Remote HIYASU ref YK1F

246/5000
Good afternoon.
I'm setting the climate for the home air, and I've got the codes for Mitsubishi, but for an air of the HYASU brand (remote ref YK1F) I can not find them.
Does anyone use it or know another compatible?
Thank you

Try Gree codes, 1180 or 1181

Ok 1180 Thank’s

@mac587 thank you so much for this information; it's very valuable knowledge for me! If you don't mind me asking, where did you learn this from?


[Feature Request] Add banner.svg as Branding configuration

Much like ui-logo and ui-logo-dark we would like for the banner.svg that is displayed in the Rancher Home screen to be configurable. This should have the same user experience as uploading a logo or favicon in the Global Settings -> Branding.

+1
is there any update/progress on this?


Create a Docker image with Python and pip for use in the strongbox-web-integration-tests

Task Description
We need to create a Docker image with Python and pip for use in the strongbox-web-integration-tests project.
Tasks
The following tasks will need to be carried out:

[ ] Add Python
[ ] Add pip

Task Relationships
This task is a dependcy of: #811 ,  #816.

@anki2189 , @steve-todorov : FYI.


Recent change breaks backwards compatibilty for register_page_listing_more_buttons hook

The following change added into Wagtail 2.10 caused the explorer to break on a site I deployed it on: https://github.com/wagtail/wagtail/commit/5f3c12682fe5f93de6a0f614ab4af89d8518e807
This site has the following register_page_listing_more_buttons hook:
@hooks.register("register_page_listing_more_buttons")
def page_listing_more_buttons(page, page_perms, is_parent=False):
    ...

After applying the Wagtail 2.10 update, the Explorer crashes with the following error:

TypeError: page_listing_more_buttons() takes from 2 to 3 positional arguments but 4 were given

Since this is a Wagtail admin error, this is likely to slip through someones unit tests. We should add an upgrade consideration pointing out that you need to add next_url=None to any register_page_listing_more_buttons hooks.

We can use the accepts_kwarg helper to provide a proper deprecation path here:

when calling the hook, see if the function expects a next_url kwarg
if not, output a deprecation warning telling the developer to add next_url=None, and call the hook without the extra argument
in Wagtail 2.12, remove that check

Fixed in #6218. (So this is why I was getting deja vu...)


add type-safe module to construct API links

Issue Number

#1232
Overview

1e1867cca9064f831e2eecb0f2cebf7c6a339ae4
add type-safe module to construct API links
This is mostsly relying on servant machinery ('safeLink') but, it
defines easy-to-use constructors that can play well in integration
tests. The reasons behind this change are plural:

In order to correctly re-design the way fixtures are created for the
various types of byron wallets (to tidy up the existing scenarios and
make them easier to use), I needed a more holistic way to deal with
wallet endpoints (shelley or byron) which was generic enough to avoid
too many duplication in the integration DSL. One of the main
empediment for this was the way we defined endpoints.

The current module interface we use for dealing with endpoints is
very much stringly typed and, although it is mostly sufficient at the
call-site, it can be quite error-prone and doesn't prevent bad
surprises when passing along wrong data.

We have the 'Cardano.Wallet.Api.Client' when a strongly-typed client
is needed, but, if we don't want a strongly typed client (like in the
integration tests), we have to fallback all the way down a fully
untyped client. This module now offers a middle-ground where we can
still statically check at least the URL and methods being used.

The way the current module interface works in the DSL duplicates all
the API path. This new module now fully uses 'Cardano.Wallet.Api' as
a source of truth, removing a lot of duplications in the paths.

Now, TODO: updates the integration tests to use this approach and clean
up the DSL module from the existing 'xxxEp' helpers.

a857586ed9667dccca7f035de1d23a9c72449600
replace DSL endpoints with new '.Link' module
TODO:

[x] Framework/DSL.hs

[x] Scenario/API/Addresses.hs

[x] Scenario/API/ByronTransactions.hs

[x] Scenario/API/ByronWallets.hs

[x] Scenario/API/Network.hs

[x] Scenario/API/Transactions.hs

[x] Scenario/API/Wallets.hs

[x] Jormungandr/Scenario/API/StakePools.hs

[x] Jormungandr/Scenario/API/Transactions.hs

Comments

bors try

bors r+


isRemoval prop

Here, instead of displaying both + and - for all the tracks, you could utilize the isRemoval prop passed to the Track component to determine which button to use.
For example, if this.props.isRemoval is false (ie. for the tracks in searchResults), then you'd want the + button to be able to add the track. And if this.props.isRemoval is true (ie. tracks in playlist), you'd want the - button.
One way you could implement this is by using the ternary operator.

thank you, this is what I did :
render() {
const button = this.props.isRemoval ? (
 -
) : (
 +
)
return (

{this.props.track.name}
{this.props.track.artist} | {this.props.track.album}

{button}

    );
};


Apply rules and aggregate weak labels in Python Client

As a Python user I want to:

Read the rules from a Token Classification dataset
Apply the rules to the dataset (i.e., generating a weak label matrix)
Aggregate/denoise the resulting weak labels

In principle we should follow the same data model that we use for Text Classification and decide if we want to have a external dependency for the Aggregation/denoising model (e.g., skweak)

@frascuchon was that the task asked for upcoming release ?

Hi Ufuk, the upcoming release tasks are listed here:
https://github.com/argilla-io/argilla/milestone/9
It's the one about adding/removing rules from the client

Ref #1749


[Chore]: Ensure metrics server is enabled on EKS-E2E cluster

install-dependencies.sh is installing a metrics server, as it doesn't find one.
It's probably better if we just create the cluster with one.
Find the option and change the creation script.

The AWS instructions say to install metrics server via
kubectl apply -f https://github.com/kubernetes-sigs/metrics-server/releases/latest/download/components.yaml

We vendir that file and the install-dependencies script applies it. So I think we're fine already. Closing without any change.


#41, graph clarity, add vertical line for future income

Added to both charts on the graphs page. There is no tooltip for the line. I could add one, but the code would be pretty hideous.

This is great! Thank you! It might be good if we could at least add a label to it, but I'm not familiar with that functionality. Note to self: we may end up using the 'current' income value.

@knod I could add a label if you want.  It is easy to do.  There was one before I just didn't like the look of it.
And if you want to play around with the implementation, ctx is a CanvasRenderingContext2D, which is part of the browser API, not Chart.js. It took me awhile to realize that...


OCPBUGS-28634: Update agentserviceconfig.md to remove PUBLIC_CONTAINER_REGISTRIES

Instructing customers to override PUBLIC_CONTAINER_REGISTRIES is not ideal since the value specified for that override will completely wipe the default list and they could run into issues getting their images pulled (see https://issues.redhat.com/browse/OCPBUGS-28634). Instead we should provide the option to just add their registry to the default list.

What this PR does / why we need it:
Modifies the document for setting up assisted service to add a customer's registry as a "public" registry (one that doesn't require authentication). Prevents customers from using PUBLIC_CONTAINER_REGISTRIES which will override the default list.
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes # https://issues.redhat.com/browse/OCPBUGS-28634
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.
[x] This change includes docs.
[ ] This change includes unit tests.

/cc @jparrill

/retitle OCPBUGS-28634: Update agentserviceconfig.md to remove PUBLIC_CONTAINER_REGISTRIES

/approve

/retest-required

/retest

/lgtm


Can't edit files

I tried running marathon edit createSession and it says.
💥  Failed to open script 'createSession' for editing
👉  Make sure that it exists and that its file is readable

I can verify that the file exists, and marathon edit createSession --no-xcode seems to work.

Hey @codeOfRobin 👋 Could you run marathon edit createSession --verbose and post the output here, so that we can start debugging the issue?

👋 Running with verbose gives me
🏃  $ cd "/Users/robinmalhotra/.marathon/Scripts/Cache/-Users-robinmalhotra-Developer-scripts-createSession/" && readlink OriginalFile
   /Users/robinmalhotra/Developer/scripts/createSession.swift
   $ cd "/Users/robinmalhotra/Developer/scripts/" && /usr/bin/env xcrun --sdk macosx swift --version
   Apple Swift version 4.0 (swiftlang-9<IP_ADDRESS> clang-900.0.36)
   Target: x86_64-apple-macosx10.9
   $ cd "/Users/robinmalhotra/.marathon/Scripts/Cache/-Users-robinmalhotra-Developer-scripts-createSession/" && /usr/bin/env xcrun --sdk macosx swift package generate-xcodeproj
   error: package has unsupported layout; found loose source files: /Users/robinmalhotra/.marathon/Scripts/Cache/-Users-robinmalhotra-Developer-scripts-createSession/.build/checkouts/Networking.git--5313523778849338262/Tests/DELETETests.swift, /Users/robinmalhotra/.marathon/Scripts/Cache/-Users-robinmalhotra-Developer-scripts-createSession/.build/checkouts/Networking.git--5313523778849338262/Tests/Dictionary+FormURLEncodedTests.swift, /Users/robinmalhotra/.marathon/Scripts/Cache/-Users-robinmalhotra-Developer-scripts-createSession/.build/checkouts/Networking.git--5313523778849338262/Tests/DownloadTests.swift, /Users/robinmalhotra/.marathon/Scripts/Cache/-Users-robinmalhotra-Developer-scripts-createSession/.build/checkouts/Networking.git--5313523778849338262/Tests/GETTests.swift, /Users/robinmalhotra/.marathon/Scripts/Cache/-Users-robinmalhotra-Developer-scripts-createSession/.build/checkouts/Networking.git--5313523778849338262/Tests/JSONTests.swift, /Users/robinmalhotra/.marathon/Scripts/Cache/-Users-robinmalhotra-Developer-scripts-createSession/.build/checkouts/Networking.git--5313523778849338262/Tests/NetworkingTests.swift, /Users/robinmalhotra/.marathon/Scripts/Cache/-Users-robinmalhotra-Developer-scripts-createSession/.build/checkouts/Networking.git--5313523778849338262/Tests/POSTTests.swift, /Users/robinmalhotra/.marathon/Scripts/Cache/-Users-robinmalhotra-Developer-scripts-createSession/.build/checkouts/Networking.git--5313523778849338262/Tests/PUTTests.swift, /Users/robinmalhotra/.marathon/Scripts/Cache/-Users-robinmalhotra-Developer-scripts-createSession/.build/checkouts/Networking.git--5313523778849338262/Tests/ResulTests.swift, /Users/robinmalhotra/.marathon/Scripts/Cache/-Users-robinmalhotra-Developer-scripts-createSession/.build/checkouts/Networking.git--5313523778849338262/Tests/SHA1.m, /Users/robinmalhotra/.marathon/Scripts/Cache/-Users-robinmalhotra-Developer-scripts-createSession/.build/checkouts/Networking.git--5313523778849338262/Tests/String+UTF8Tests.swift, /Users/robinmalhotra/.marathon/Scripts/Cache/-Users-robinmalhotra-Developer-scripts-createSession/.build/checkouts/Networking.git--5313523778849338262/Tests/TestHelpers.swift, /Users/robinmalhotra/.marathon/Scripts/Cache/-Users-robinmalhotra-Developer-scripts-createSession/.build/checkouts/Networking.git--5313523778849338262/Tests/UnauthorizedCallbackTests.swift

Looks like it's an issue around SPM not quite liking his tests. We should probably inform Elvis about this.

Looks like the framework you're trying to use does not have a Swift 4-compatible layout. As of Swift 4, all code needs to be contained in folders matching the various modules/targets of a Swift Package. So the framework needs to be updated to support Swift 4.
Marathon's error message could be better here of course.

Cool, thanks a lot! I'll speak to the project maintainer.


Highlight matching parenthesis

A small but very convenient feature is the one that highlights the matching parenthesis ((),[],{},<>) for the one currently on the cursor. This is especially useful for multi-line and multi-parenthesis expressions.

@aelij I'd like to tackle this. Do you have any specific PR requirements?

Thanks, @aholmes!

All the changes should be in the RoslynPad.Editor.Windows assembly
Store the highlight color in ClassificationHighlightColors
I suggest you take a look at SharpDevelop, they've probably implemented this for their AvalonEdit-based editor

@aelij Great! I have everything set up, so I'll get to this as soon as I can, life permitting.

Also implemented Ctrl+] for navigating between braces.

Awesome! 👌 I didn't realize so much code was involved - no wonder I had a hard time.

Most of it was copied from Roslyn :)


ayush name added

@hemant5454, could you please add your name to Contributors.md?

Closing this as this has been stalled for a while.


Brute Force kNN example

Fails due to absence of BF kNN implementation in 2020.2 version of DAAL which is used in CI. Merge after 2020.3 release.

@Alexsandruss you can add a versioning check - then it automatically turns on - as the release appears.
see examples:
https://github.com/IntelPython/daal4py/blob/master/examples/run_examples.py#L104

@Mergifyio rebase


Fix bug of sending empty log from docker container

What does this PR do?

Add condition of checking the docker header when form a log line in logs decoder.
Remove build tag docker from some files that doesn't require docker to run in order to be checked by linter
Rename DockerParser to Parser to pass linter check.

Motivation
Client complain
Additional Notes
Tested with client failing user case.

Good catch !
I think that's a bit of a hack because we match it on all incoming logs. Would it be hard to make it only on docker sources now that we have a decoder instance by tailer ?

hmm, decoder is general to all, we will need to do instanceof (if there is any) based on the parser passed in.

Finished to review the code, I did not look at the tests yet.
Overall looks good to me, I think you address the problem correctly considering our current design but I have on main concern which is to isolate completely the docker specific decoding logic from the decoder ; I left an idea on how to address this problem.


Define multiple keys for type conversion

Description
Allow defining multiple keys in the convert_entry_type processor.
Note: existing key still works. But only One Of (key or Keys) is required.
If all of them defined or Non of them defined, will throw exception.
eg:
processor:
    - convert_entry_type:
         keys: ["key1", "key2"]
         type: "integer"

converts
{"message":"value","key1":"123", "key2":"456"}
to
{"message":"value","key1":123, "key2":456}
Issues Resolved
Resolve #2823
Check List

[x] New functionality includes testing.
[x] New functionality has been documented.
[x] New functionality has javadoc added
[x] Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Changes looks good, just missing the documentation

Ok, updated README


feat(cert): support for auto reload certificate when updated

Moved from : https://github.com/gravitee-io/gravitee-gateway/pull/786
Issue
Closes gravitee-io/issues#5888
Description
Support file base and kubernetes configuration.

Gravitee.io Automatic Deployment
📚 View the storybook of this branch here

Gravitee.io Automatic Deployment
Congrats, all the CI steps were 🟢 . The Bot was able to deploy the build of this PR, so you can now try it directly here! 🚀
Notes: The deployed app is linked to the management API of the Element Zero team's environment.

IMHO - todo : rebase this PR https://github.com/gravitee-io/gravitee-node/pull/89 and change gravitee-node version in this PR one

Replaced by https://github.com/gravitee-io/gravitee-api-management/pull/879


Design Backlog: Operation Information Page

This is a design review follow-up ticket to #196
Here are the design review notes from Suha:

The blue information blurb links back to registration, with the last word 'registration' as a hyperlink that takes you to your registration dashboard. Could we implement this at this point of time?

BORO ID and BCGHG ID are greyed out and meant to be auto-populated with information we will have on the user. It can't be edited. Can we visually reflect this? In Figma, we have #F2F2F2 (bc-background-grey) fill such fields

The button placement , stylization and sizing at the end (for Save, Continue, Cancel) are different than in Figma

I wasn't able to test out whether Reporting Activities, Regulated Products, Operation representative were multi-select drop-downs where we can select more than one entry

The header of the form looks different than what we have in Figma. I do believe we have this styled component we can borrow from Moose

Needs updating. Many of these have been addressed already.

zoey to check which ones have been implemented already and then update this ticket

@patriciarussellCAS I believe we can close this ticket. Checkbox 2 and 4 are already implemented. Checkbox 1 is being implemented in a different ticket #432
RE: third checkbox: "The button placement , stylization and sizing at the end (for Save, Continue, Cancel) are different than in Figma" <- the only difference is that instead of "continue", in dev it says "save & continue" which is actually better than just continue, so I mark this checkbox as done.
RE: last checkbox: "The header of the form looks different than what we have in Figma. I do believe we have this styled component we can borrow from Moose", it looks the same currently.

Thanks Zoey. Works for me. I will close this.


Rename PaymentButton configuration

Previously, PaymentButton had a private configuration property which contained an SVGConfiguration. That property name is used in iOS 15, so we cannot use it for our own private one. We can rename it to something unused, instead. We have renamed it to svgConfiguration.
Resolves #173

Thanks for being quick. 😀 @huwr

Thanks for being quick. 😀 @huwr

I actually did it months ago but never made a PR in case things changed!


Add pyproject.toml for Custom Node Registry

We are working with dr.lt.data and comfyanon to build a global registry for custom nodes (similar to PyPI). Eventually, the registry will be used as a backend for the UI-manager. All nodes go through a verification process before being published to users.
The main benefits are that authors can

publish nodes by version and users can safely update nodes knowing ahead of time if their workflows will break or not
automate testing against new commits in the comfy repo and existing workflows through our CI/CD dashboard

Action Required:

[ ] Go to the registry. Login and create a publisher id (everything after the @ sign on your registry profile).
[ ] Add the publisher id into the pyproject.toml file.
[ ] Merge the separate Github Actions PR, then merge this PR.

If you want to publish the node manually, install the cli by running pip install comfy-cli, then run comfy node publish
Check out our docs if you want to know more about the registry. Otherwise, feel free to message me on discord at haohao_81202 or join our server if you have any questions!

hey @lks-ai, wanted to send a small nudge and ask if you had any questions!

@lks-ai, wondering if there's any way we can support you on this PR!


Working set size increase on startup when remote write enabled

Bug Report
What did you do?
I enabled remote write, restarted the prometheus pod and it OOMed because the working set size increased 3x.
What did you expect to see?
Here's what container_memory_working_set_bytes, process_resident_memory_bytes and go_memstats_alloc_bytes looked like before enabling remote write:

What did you see instead? Under which circumstances?
Here's after enabling remote write:

After ~4 hours, working set size goes back to expected level:

Environment

System information:

Linux 4.15.0-1037-azure x86_64

Prometheus version:

prometheus, version 2.10.0 (branch: HEAD, revision: d20e84d0fb64aff2f62a977adc8cfb656da4e286)
  build user:       root@a49185acd9b0
  build date:       20190525-12:28:13
  go version:       go1.12.5

Prometheus configuration file:

global:
  scrape_interval: 15s
  scrape_timeout: 10s
  evaluation_interval: 15s
  external_labels:
    datacenter: eastus2
    environment: dev
    prometheus: kubernetes
    prometheus_replica: "0"
alerting:

... alerting configs ...

rule_files:
- /etc/prometheus/rules/prometheus-prometheus-kube-prometheus-rulefiles-0/*.yaml
scrape_configs:

... lots of scrape configs ...

remote_write:
- url: http://REDACTED:7201/api/v1/prom/remote/write
  remote_timeout: 30s
  queue_config:
    capacity: 10
    max_shards: 1000
    min_shards: 1
    max_samples_per_send: 100
    batch_send_deadline: 5s
    max_retries: 3
    min_backoff: 30ms
    max_backoff: 100ms

Somewhat similar to #5666

IME enabling remote write after the rewrite usually has about 25-35% memory increase. We haven't seen memory usage 3x with remote write on, but without more info I can't offer any suggestions.
Are you able to show us logs from your Prometheus prior to it being OOM killed, or a pprof profile? How many active series do you have? I would assume not many based on the graphs you posted. You could also have a look at the metrics Tom mentions here: https://github.com/prometheus/prometheus/issues/5424#issuecomment-478550630

I'd like to add a little info here. We're seeing something very similar, and have been struggling all week to figure out why Prom is consistently using so much memory. Based on a bit of testing, we observe that on startup, Prometheus quickly reshards up to a large number of remote write shards (presumably to flush out the WAL into the remote write target). This uses up an immense amount of memory causing OOMs. Restricting the max number of shards seems to solve this problem for us.
Happy to provide metrics/pprofs that would help if this is unexpected behavior. We're running with about 1.2M timeseries, and with the default remote write settings we're getting OOMs at around 14GB of resident set. We've had to reduce our max shards to 50 and our max samples per send to 10000, and this gives us around 9GB rss.

@Niksko That sounds like expected behaviour to me. Remote Write isn't able to start sending metrics until after it's replayed the existing WAL, so it will want to upshard a lot initially.
As another data point for you, we have some Prometheus instances that have about 1.35mil active series. We use the default max and min shards, but bump the capacity from 10 to 100. Those instances are using ~ 17GB in RSS and ~12GB cache. These are running in pods, we let them request 25GB and limit them to 30GB.
If you're interested you can graph this query: https://github.com/prometheus/prometheus/blob/master/documentation/prometheus-mixin/dashboards.libsonnet#L107 to see if you're remote write is falling behind. Debug logging will also tell you how many shards remote write wants to use.

Also note that https://github.com/prometheus/prometheus/pull/5787 adds metrics for the configured and desired shards.
Overall, the observed behavior seems expected with the configured number of max shards. Since this is more a configuration problem than an actual bug, I'm closing this issue.

Also see #5267 wherein I try to reduce the default max shards and #5763 which is trying to improve the desired shards calculation.

I do not think that the observed behavior in this ticket is expected. I see at least two real issues that are being commented on:

The current shard calculation only takes how far behind the remote write component is into account, not the input rate of samples. #5763 fixes that.

This is likely the biggest issue causing the spikes of number of shards.

Potentially large amount of upsharding when a queue is started. Caused while we catch up on samples missed during WAL replay, and amplified by point 1. Technically all of that time is unnecessary (though nice from a separation of concerns) since the TSDB startup also reads the WAL on startup.

These are valid concerns with the current remote write behavior and it is incredibly frustrating to tune a remote writing Prometheus right now.

From my point of view, part of this is a documentation issue.
Documentation should indicate that memory usage of this scale is expected and intended, and you should provide rough estimates to help people determine legitimate usage from unexpected usage. There are many, many threads in various places that show that the high memory usage of Prometheus comes as a shock to people. Clearly it shouldn't be a shock.

Thanks for all your input. Since #5763 and #5267 are still being worked on, I'll re-open this. Mostly so that people running into memory issues and searching for open bugs will find this. To be closed once both PRs are merged.
Also note that I re-purposed #5803 to track better documentation of configuring remote-write queues.

Some documentation has been added: https://github.com/prometheus/docs/pull/1417/files
Not sure there's anything else actionable here, if there is we should add it to #6333

We are currently running a bug scrub with the team. Following @cstyan's line of argument, we close this now. Please follow up in #6333 if needed.


Disable timeout for minio proxy

With caddy version 0.9.5 timeouts are now enabled by default (https://github.com/mholt/caddy/releases/tag/v0.9.5). This breaks uploads and downloads with minio that take longer then 10s.

Thanks Jan! But actually this problem will go away literally tomorrow once people upgrade. :) So I'll close this, since it won't be needed at that point.


[CH-5425] Add temporary logging for apns request

Note: This change will NOT be merged.
We will simply have apns-push-service temporarily use this branch to log the request and test for a day.
The PR is just for people to check if these code will log things correctly.

Testing done. Closing this PR.


CORS: Error during options request

I'm trying to fetch data from a mocked response through a web app but I am getting the following message:
Access to XMLHttpRequest at 'http://localhost:3001/api/v1/alarme/nao-lido/2019-06-04' from origin 'http://localhost:8771' has been blocked by CORS policy: Request header field authorization is not allowed by Access-Control-Allow-Headers in preflight response.

So, I looked in the terminal and I found the following message:
Error: ENOENT: no such file or directory, open '/home/lssev/dev/bancos/spi/spi-mock/mock/rest/alarme/#nao-lido#{date}/OPTIONS/mock/response.txt'
    at Object.openSync (fs.js:440:3)
    at Object.writeFileSync (fs.js:1265:35)
    at MockController.writeFile (/home/lssev/dev/bancos/spi/spi-mock/node_modules/node-mock-server/lib/Utils.js:153:6)
    at MockController._handleMockRequest (/home/lssev/dev/bancos/spi/spi-mock/node_modules/node-mock-server/lib/controller/MockController.js:203:9)
    at Layer.handle [as handle_request] (/home/lssev/dev/bancos/spi/spi-mock/node_modules/express/lib/router/layer.js:95:5)
    at next (/home/lssev/dev/bancos/spi/spi-mock/node_modules/express/lib/router/route.js:137:13)
    at next (/home/lssev/dev/bancos/spi/spi-mock/node_modules/express/lib/router/route.js:131:14)
    at next (/home/lssev/dev/bancos/spi/spi-mock/node_modules/express/lib/router/route.js:131:14)
    at next (/home/lssev/dev/bancos/spi/spi-mock/node_modules/express/lib/router/route.js:131:14)
    at next (/home/lssev/dev/bancos/spi/spi-mock/node_modules/express/lib/router/route.js:131:14)

So, as I saw the "OPTIONS" in the terminal, I thought I should replicate the mocked response for the OPTIONS method. But even with the OPTIONS response mocked endpoint I  am getting the CORS problem. At least, I am not getting the message in the terminal again. Just my application that still not being able to fetch the data when requesting through the OPTIONS method.
When I make the same request through Postman, it works. Just through my web application that I am getting into this problem. Any advices that I should follow?
My options are:

var mockServer = require('node-mock-server');
var path = require('path');

mockServer({
	'restPath': path.join(__dirname, '/rest'),
	'uiPath': '/',
	'title': 'Api mock server',
	'version': 1,
	'urlBase': 'http://localhost:3001',
	'urlPath': '/api/v1',
	'port': 3001,
	'contentType': 'application/json',
	'accessControlExposeHeaders': 'X-Total-Count',
	'accessControlAllowOrigin': '*',
	'accessControlAllowMethods': 'GET, POST, PUT, OPTIONS, DELETE, PATCH, HEAD',
	'accessControlAllowHeaders': 'origin, x-requested-with, content-type',
	'accessControlAllowCredentials': 'true',
	'headers': {},
	'open': true,
	'dirName': __dirname
});

Well, I solve the problem by doing the following steps:

Adding the authorization header on the accessControlAllowHeaders option.
Creating an OPTIONS request and adding a response.txt file inside the mock folder.


Include local.sites.php

Added renaming on example. files so that our example.sites.php and example.local.sites.php from our projectify extra files repo also get renamed.
The Drush Make will not interfere afterwards as the files have been renamed and the Drush make example.sites.php will just remain the example.


Add testcases for Undo command where purge future versions is utilised.

Add a test case where the undo command is used followed by a commit to the datastore, which can consist of any command that mutates the datastore

Will do manual testing which has higher yield instead


Doc site at vers.js.org

A really simple start is to generate docs with jsdoc from your current (awesome!) doc strings and README.md and push it to the gh-pages branch.  Add a CNAME file with your subdomain of choice vers.js.org. Finally, open a PR on https://github.com/js-org/js.org that adds the domain to the active list.
If there is interest for this I can submit a PR, or, someone can do that ^^

Reference Tap Flux for an example.


Reference User correctly

Codecov Report

Merging #3555 (3069376) into development (e57c506) will decrease coverage by 7.73%.
The diff coverage is 20.53%.

@@                Coverage Diff                @@
##             development    #3555      +/-   ##
=================================================
- Coverage          30.37%   22.63%   -7.74%
+ Complexity         15516    15343     -173
=================================================
  Files                416      393      -23
  Lines              73757    68765    -4992
=================================================
- Hits               22403    15568    -6835
- Misses             51354    53197    +1843

Impacted Files
Coverage Δ

sources/DumpDatabase.php
0.00% <0.00%> (ø)

...s/ElkArte/AdminController/ManageCalendarModule.php
0.00% <0.00%> (ø)

sources/ElkArte/AdminController/ManagePaid.php
5.51% <0.00%> (ø)

sources/ElkArte/Agreement.php
0.00% <0.00%> (-53.09%)
:arrow_down:

sources/ElkArte/CalendarEvent.php
44.44% <0.00%> (ø)

sources/ElkArte/Controller/News.php
0.00% <0.00%> (ø)

sources/ElkArte/Controller/Post.php
22.23% <0.00%> (-18.99%)
:arrow_down:

sources/ElkArte/Controller/Register.php
0.00% <0.00%> (-37.21%)
:arrow_down:

sources/ElkArte/Controller/Stats.php
0.00% <0.00%> (ø)

sources/ElkArte/Modules/Calendar/Post.php
0.00% <0.00%> (ø)

... and 198 more

Continue to review full report at Codecov.

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

Instead, just place a use ElkArte\User; at the top of the file with the other use items ... its the new require once 😸

I did think that, then looked in other files and you’d referenced it that way. So went with Elkarte\User 😅
Is your preference an use?

LOL ... yes the preference is the use statement all around.  Some large changes  were done with cough copy/replace cough and that is likely why there are some inconsistencies. This time I'm 😇


Configuring auto-launched dev server (or better solution for running configureable server)

My situation: on client-side I have a VueJs and Nuxt-based app as frontend which I want to connect to my nexus app as API middleware.  As database backend I use the prisma plugin with nexus.
So the workflow is:    Nuxt and Apollo Client Module (Frontend) <-> Nexus Graphql API (Graphql/HTTP) <-> Database (Prisma)
I am so confused about how to solve specific things in nexus framework as there are so many different tutorials and examples are out there which all seem to rely on different versions of the framework, so that code often isn`t valid anymore. And also the docs are useless sometimes as there seems required code to be missing or it is invalid too.
I know the framework is under heavy development and some things are outdated atm but I really like it so much so I hope you can give me some help here please.
I also want to implement/use the following features of the framework in future for my API:

Graphql subscriptions
Authorization (maybe with tokens and Http-based cookies)
Eventually some HTTP endpoints when GQL is useless (downloading big files to frontend)
...

At the moment I got stuck when configuring CORS headers on nexus (GraphQl) server side. I dont know how to do it because when I run nexus in development mode (yarn -s dev) everytime the auto-launched development server instance is ran and I did not found any working example on how to change or configure the underlying server instance.
There are some examples out there running the Graphql server manually with custom code and express, but the it conflicts with the auto-launched dev server as both are starting then. What is the best way (code) of solving that ?
BTW i initially created the project with the installer command "npx nexus" so the necessary configs were created automatically. My current package.config:
    "@nexus/schema": "^0.15.0",
    "nexus": "^0.26.1",
    "nexus-plugin-prisma": "^0.18.1",

Nexus is EOL, let's give the devs some time to reorganize the documentation around schema, fix namespacing, etc.

Sorry I didn`t realize that there are two different projects and I was using EOL nexus framework. Just some days after posting I found the information about nexus framework EOL, where things got a bit clearer: https://github.com/prisma-labs/graphql-framework-experiment/issues/1432
I will fully switch over to nexus schema (with prisma layer) which may solve my issues. Thanks.


Layout not inflated on first start

Layout is inflated only after a requestLayout call is fired after onResume is called

Fixed in dea14a2


Cordova Plugin

I really like the lock for iOS look and feel. Do you have any plans to create a plugin for cordova apps? I made an attempt but it does get stuck when the view is dismissed.
`
@implementation lockPlugin
-(void)init:(CDVInvokedUrlCommand*)command {
A0Lock *lock = [A0Lock sharedLock];

A0LockViewController *controller = [lock newLockViewController];
controller.onAuthenticationBlock = ^(A0UserProfile *profile, A0Token *token) {

    CDVPluginResult* result = [CDVPluginResult resultWithStatus:CDVCommandStatus_OK
                                            messageAsDictionary:@{
                                                                  @"idToken":token.idToken,
                                                                  @"refreshToken":token.refreshToken,
                                                                  @"tokenType":token.tokenType,
                                                                  @"accessToken":token.accessToken,
                                                                  @"email":profile.email
                                                                  }];

    [self.commandDelegate sendPluginResult:result callbackId:command.callbackId];

    [self.viewController dismissViewControllerAnimated:YES completion:nil];

};
[lock presentLockController:controller fromController:self.viewController];

}
@end
`
After the plugin returns the result, I can no longer interact with the cordova app. No errors in console..

I am not a big expert on cordova plugins but it could be a threading issue and where the callback is executed.
We were considering if it's worth wrapping the native lock in a plugin but after the experience with react-native we are not so sure about it.
I'd advise to ask in either ask.auth0.com or StackOverflow, probably someone can shed light with your issue after the plugin returns.

@cevatkerim Did you ever make any progress with this? Cordova + lock + wkwebview + inapp-browser is killing me


Lookahead in regex is undocumented

Is lookahead for regexes currently supported? It's undocumented currently.

It's before. It's described in S05 as well - so it's "documented" just not in a user-friendly fashion.

Thanks @vendethiel. I tried to document it in https://github.com/perl6/doc/pull/106

Fixed in https://github.com/perl6/doc/pull/106


Download flow changed- replicated

Description

Related Issue

Types of changes

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

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I have run the pre-merge tests locally and they pass.
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[ ] If Gemfile.lock has changed, I have used --conservative to do it and included the full output in the Description above.
[x] All new and existing tests passed.
[x] All commits have been signed-off for the Developer Certificate of Origin.

DEMO : https://progresssoftware.sharepoint.com/:v:/s/ChefCoreC/Ed8z3Gw8VORIkamEun5WHAwBbL8CYIZ1JMZBu5g2PgwBMw?e=VAW2w3

Tests are missing in this PR


docs(p-toolbox-table): change two-way-binding hook

To Reviewers

[ ] Skipping review is not a problem (style, chore ONLY)
[ ] Not that difficult

Type of Change

[ ] New feature
[ ] Bug fixes
[ ] Feature improvement

[ ] These changes require a usage change

[x] Others (performance improvement, refactoring, CI/CD, etc.)

Checklist

[x] Updated Storybook documents
[x] Tested with console

Description

change makeOptionalProxy to useProxyValue
tested with all p-toolbox-table in console

Things to Talk About

:tada: This PR is included in version 1.1.0-beta.395 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[cmake] Fix building with CMake

Disable building tests on Darwin
Fix test registration on Linux when double-wide atomics aren't available
Unconditionally enable double-wide atomics

Checklist

[X] I've read the Contribution Guidelines
[X] My contributions are licensed under the Swift license.
[X] I've followed the coding style of the rest of the project.
[ ] I've added tests covering all new code paths my change adds to the project (if appropriate).
[X] I've verified that my change does not break any existing tests.
[ ] I've updated the documentation if necessary.

@swift-ci test

cc @compnerd This (with #38) is an attempt at making the CMake config work out of the box. (Beware, I have no idea what I'm doing. 🙈)

@swift-ci test

Rebased on current HEAD. Also added an arm64 fix from swift-collections.
@swift-ci test

I submitted https://github.com/apple/swift/pull/39404 to get the ball rolling on enabling cx16 by default in swiftc.
When/if that gets into a compiler release, we can bump the required toolchain version in a minor release, allowing us to get rid of the ENABLE_DOUBLEWIDE_ATOMICS/-mcx16 mess.

Merging to have a functional CMake config.


make svalinn t2

About the PR
title
no points change only tier
Why / Balance
its just outclassed by advanced laser which is an actual t3, if you want to make 10 batteries you can also just make 10 lasers
maybe it will be seen outside of warops now
Changelog
:cl:

tweak: Svalinn laser pistol is now a Tier 2 tech instead of Tier 3.

This may need it moved to the secfab instead of the protolathe since I agree this could make it much more common

This may need it moved to the secfab instead of the protolathe since I agree this could make it much more common

putting it in the secfab removes the only reason it exists, it being a shitty mass produceable laser pistol that non-sec can get

even as a T2 and on the protolathe i doubt we will ever see it used, its expensive, a bad gun and overall makes me wanna cry. its a shame cause its got the coolest sprite ever and a unique mechanic of being powered by power cells, if anything i think it should get a buff along with this.

it probably shouldnt be contraband tbh.

Also done in #31762


Get a refreshed access token if expired

Is your feature request related to a problem? Please describe.
To authenticate a user against my Rest API, I forward the Lens access token and send it to my server, then call the Lens API to verify that it's valid. This process is working fine as recommended by the lens docs.
To get the access token, I use the useAccessToken hook but that returns the current accessToken that might be expired, I need a way to get a refreshed access token.
Describe the solution you'd like
I guess smth like the following would solve my problem
const {getAccessToken} = useAccessToken()

const myFunc = async () => {
  // SDK would get a new access token if expired from the refresh token
  const validAccessToken = await getAccessToken()
  callMyAPI(validAccessToken)
}

@pradel while looking into this I've spotted an issue that, even implementing the pattern you mentioned, would prevent it from working properly. I am working on a fix, will let you know about an ETA as soon as I have an idea of problem.

Fix ready for next release: https://github.com/lens-protocol/lens-sdk/pull/840

@cesarenaldi will the token be refreshed if no calls are made to Lens for a long time?

Yes, the token from useAccessToken will automatically refresh seamlessly. As you would expect from a hook with that signature. Make sure any callback that depends on it are updated accordingly if leverage useCallback hook (or useMemo).

BTW, the approach you suggested is probably better IMO, just didn't want to introduce an API breaking change as I am aware several teams rely on the useAccessToken hook.

I assume this issue is solved then.

@krzysu tried with the latest version and the token is not refreshed, can you please reopen the issue?

@pradel sorry, I only got to this now. I managed to reproduce some issue at bootstrap time. Hook returns null and does not updates with the newly refreshed token. Is this the behaviour you are flagging?

The behavior I noticed is after 30 mins of inactivity (so when the access token expires)

@pradel a fix for this in the next release.

@b-bot this issue was specifically for the Lens React SDK. The LensClient operates under different assumptions. It's a lower level integration with the Lens API so many things that in the Lens React SDK are taken care of by the SDK, with the LensClient are on the integrator to detect and renew.
Said that, at a quick glance I don't see the method you would need to invoke to refresh credentials when you encounter NotAuthenticatedError.
Can I ask you about your integration? Are you using the LensClient on the client-side? Is your use of the Access Token to validate user's identity?

@b-bot ok, we have few things going on here. Let's start from the simple one.
The LensClient automatically refresh tokens only when a new instance is used for the first time and it was instantiated with a persistent storage.
In this regards it's similar to the Lens React SDK.
Contrary to the Lens React SDK it does not refresh tokens ahead of their expiry time (30 mins), nor when a request fails due to expired token. It instead propagates the CredentialsExpiredError error to the caller which is responsible to perform a manual refresh.
In my previous message I hinted at the fact I couldn't find the method you are supposed to call in this circumstances. So we might need to expose it and release a fixed version of the @lens-protocol/client SDK for you.
But before going into that I would like to understand more about your use case to make sure it's what you need.
Can I ask how do you authenticate the LensClient on the BE? Is this using an app Lens Profile of your choice?
And on the FE, is this authenticated as well? With what Profile? The user's Profile?

Not sure how accurate is the snippet, but if the lensClient instance is just available in scope of the authorize method, it seems to me you risk to re-use the same instance across multiple requests, possibly belonging to different users.
It appears to me your use of LensClient on the BE is on a user-by-user base, so you should use ephemeral instances of the  LensClient that you throwaway once done with a given request. The LensClient class is quite cheap to instantiate so no issue in instantiating one on a request base.
With ephemeral instances scoped to the request, you can keep the default storage which is an in-memory storage. You actually want to avoid using a shared storage cause you would risk to use an authentication state from a request that possibly belong to another user.
Now the question is: do you plan to mediate other Lens request through endpoints in your BE or is this just for issuing your authenticated session?
If your only purpose is to verify the user identity and issue an authenticated session token to your user, I recommend complete the auth handshake on the client (authentication.generateChallenge(...) and authentication.authenticate(...)) and then send to your server authentication request the Lens accessToken (you can get it via authentication.getAccessToken), on the server you can then verify its legitimacy via authentication.verify(accessToken) and on positive verification issue your auth session token.
You can also fetch info about the profile, the Lens accessToken JWT contains the Profile ID you can extract and use to call
lensClient.profile.fetch which does not require authentication. In this case the BE instance of the LensClient never needs to be authenticated so you could also consider sharing it across requests.
If, on the other hand, you actually need to mediate requests to the Lens API via other endpoints in your BE, the need of using ephemeral LensClient instances is paramount. As this is sligthly more involved, let me know if it's your case and I can guide you through it.

First question: is this ephemeral?
TL;DR; No
In my experience with NextJS the lensClient instance imported this way on the server-side risks to be leaked across requests that are likely made by different clients/users.
While the approach is fine on the client-side where the only main thread is for the user, on the server you might have a pool of threads (or processes) that is used to serve incoming requests.
Said that, there is a lot of magic going on with NextJS and Vercel so don't know if they are spawning and destroying an new JS execution context for each request. Gut feeling is that they might not, cause it would make start up time unpredictable depending of how much code run at module level of the overall import chain (and we are talking about dependencies of dependencies being imported and evaluated).
By ephemeral I meant an instance of the LensClient that is bound to the request. It gets created when request comes in and it gets destroyed once it finishes. Each request deals with a new instance of the LensClient. It could be created in the request handler itself or in any middleware.
Sending the access token to your server is useful for occasional usage. For example to verify the user identify before issuing app specific session token(s). However, because it last only for 30 minutes and then it needs to be refreshed, you need to make sure you pass a fresh one with every request. You can't simply put in in the shared session after successful login. In 30 minutes time it will not be usable by your BE request handlers.
An approach I know people are using is to define a cookie based storage: https://github.com/lens-protocol/lens-sdk/issues/842#issuecomment-1945521443
With such approach the client and the server will automatically share the same internal state (i.e. refresh token). The ephemeral instance of the LensClient created on the server will be authenticated from the get-go.

This NextJS doc page gives some insights when they talk about Serverless Node.js and raises the same concern about boot up time: https://nextjs.org/docs/app/building-your-application/rendering/edge-and-nodejs-runtimes
So I guess, it depends on the way you run it.
As instantiating a LensClient is not expensive your could encapsulate all the decision making around isDev into a factory function:
function createLensClient() {
  return new LensClient(...);
}

and use such function to create an ephemeral instance in the API route handler or a middleware for it.

Hey @b-bot can you please share some insights on

The client doesn't really suit serverless architecture IMO

would love to hear your take. If this is an issue with cold boot or specific to your auth setup.
Regarding:

My idea with storing the access token in the session was to also get the refresh token there and use it to persist the auth.
There is a callback I have that runs every time the session is accessed and I wanted to validate it in there (possibly refresh, was going to submit a PR to add that method to the client)

This is possible. You can instantiate an authenticated instance of the LensClient via client.authentication.authenticateWith({ refreshToken: '...' }).
There is not a clear way to 'extract' the refresh token from the React SDK but can provide you a workaround in the short term and add a bespoke hook for that.

I would have preferred to just use the React Hooks but no integration exists yet for my library (thirdweb)

This is where custom IBindings comes into play. We provided a wagmi binding just because of its popularity, but you don't need to wait for us to create one for your library, usually it involves few lines of code. See for example this template for PWA using Privy from a community dev: https://github.com/bartomolina/lens-pwa/blob/main/lib/lens-privy-bindings.ts
I would also recommend to use React SDK if your app is leveraging React. All the heavy lifting of dealing with Lens Protocol and API intricacies is done for you.
I will be happy to help on TG, are you in the Lens Dev Garden group?

authenticateWith was born for a very specific use case: a client that has its own API integration and needs to create a LensClient instance out of a Refresh Token. So that's why currently there is no React SDK counterpart. But it's easy to create an hook, we already have useAccessToken and useIdToken hooks. Adding a useRefreshToken is pretty quick.
In the meantime you could extract the refresh token by accessing the client storage use in the React SDK. Either you create it using whatever underlying mechanism you like for the client and you pass it around, or you rely on the default (i.e. leverages window.localStorage) and use the useStorage hook to get hold of it.
Once you have storage, you call:
const item = storage.getItem('lens.development.credentials');

const content = JSON.parse(item);
const refreshToken = content.data.refreshToken;

Notice the item label contains the environment name (development or production) so it differs depending on your LensConfig setup (this was done mostly to avoid annoying clashes/error during the development experience).
Regarding:

What's your opinion on using React Hooks AND the client, would this complicate authentication further?
We made is so it's possible to have them working in the client side-by-side, but this is meant either for token-gated support or for very remote cases where a feature is available on the LensClient but didn't make it to the React SDK (yet).

Just added you to the TG group. Feel free to DM me to discuss details further.

@b-bot the PR with the useRefreshToken hook that should smooth the DX described above is going to land soon on the next canary release.

A fix for this Issue thread was released as part of last 2.x alpha. Current stable 2.1 includes such fix.
@pradel can you please confirm this is solved in your integration?

@cesarenaldi did a quick test and it seems to be working, I guess we can close the issue and reopen it in case the issue appears again?

@pradel awesome news! Closing this for now.


Filter out 'eglot backend from doom-thing-at-point

Context : https://github.com/joaotavora/eglot/issues/503
Fixes a bug where having eglot enabled in a buffer will make SPC * search the whole project for literally LSP Identifier at point.

Thanks!


Reorganization of Hulls

This pull request adds the hull functions as a seperate module. The goals are:

Convert to V2 math
Standardize API; names, parameter passing, error checks, etc.
Full test coverage

hull

[X] code complete
[X] tests complete, 82.35% coverage (97.06% coverage for hull2DPoints)
[X] review complete

hullChain

[X] code complete
[X] tests complete, 93.75% coverage
[X] review complete

A couple of things need discussion about this pull request.
First. Is the module name correct? I think the module should be changed to 'hulls'.
Second. I see no need for an 'object' to hold a 'points' and 'indices' data. I think a single function to compute the indices and return the points would be better.
Third. The hull function does not support geom3 today. Should I add a stub for this now?
@kaosat-dev Thoughts?

@kaosat-dev please review

@kaosat-dev please do a final review. and see the question above...

BIG NEWS! I just added hull of path2 geometries, which returns the outline (path2) of the hulled points.

@kaosat-dev This should be read for merge now.
Unless... you want to add hull of geom3 geometries now.

Looks good to me @z3dev , thanks for the hard work ! Merging


Uncaught DOMException: Failed to execute 'importScripts' on 'WorkerGlobalScope': The script at 'https://unpkg.com/<EMAIL_ADDRESS>failed to load.

问题描述
Uncaught DOMException: Failed to execute 'importScripts' on 'WorkerGlobalScope': The script at 'https://unpkg.com/<EMAIL_ADDRESS>failed to load.

I have searched the closed issues and found one https://github.com/antvis/G6/issues/2919 , but it can't solve my problem, because the resource has been deleted.
But Why? And How to solve this problem ?
重现链接
https://unpkg.com/<EMAIL_ADDRESS>重现步骤
just run you code
预期行为
expect it to layout correctly, but nope.
平台

操作系统: [macOS]
网页浏览器: [Google Chrome]
G6 版本: [4.8.8]

屏幕截图或视频（可选）
No response
补充说明（可选）
No response

Has been resolved, please reinstall the dependencies.


Fixed UI, Gaps and Nav bar

Fixes Issue
Fixed gap after Nav bar .
Fixed products.
Fixed nav bar links.
Fixed nav bar CSS.
Fixed categories responsiveness.
And removed some bugs in CSS.
Closes #1113
Screenshots
https://github.com/codervivek5/VigyBag/assets/128584849/5be8ebc7-558b-43d6-b4c2-d93593203d0b

someone is already working on this issue so you need to wait till then

Perfect work

@codervivek5 Thank you
But not added tags


Incorrect ID for policies with paths

What happened?
After restarting the AWS provider, policy objects with a path become not Ready. I believe it is because the initial tfstate id and the composed tfstate id are different. The composed state after a restart does not contain the path in the ARN used in the id field. This results in an error:
apply failed: creating IAM Policy (crossplane-app-policy-pg-license-only-test):
      EntityAlreadyExists: A policy called crossplane-app-policy-pg-license-only-test
      already exists. Duplicate names are not allowed.\n\tstatus code: 409, request
      id: uuid-of-error-event

How can we reproduce it?
Create an IAM policy object with a path and restart the IAM provider.
What environment did it happen in?

Crossplane Version: v1.12.2
Provider Version: v0.36.0
Kubernetes Version: 1.26
Kubernetes Distribution: EKS

I can confirm that the id contains the path after creating a new policy, but the generated id does not contain the path.

We have encounter the same issue.
To note that the policies initially look good (if they are created by crossplane) but at some point they become unready and will not get back to normal due to a policy conflict (trying to recreate the same policy)
it also makes it impossible to “import” policies with a path

The issue is relevant for the latest master


RDK-35648: Override HDMI Color Depth

Reason for change:
Override HDMI Color Depth
Test Procedure: None
Risks: Low
Change-Id: Ia1ecef1eae8e1f8678039ed8432e9bce32238368
Signed-off-by:Anooj Cheriyan<EMAIL_ADDRESS>(cherry picked from commit e4cdf549b4946aabb85dd5939dd3202d92a2feec)

New one created: https://github.com/rdkcentral/rdkservices/pull/2583


Deprecate ForkOptions.javaHome

When configuring compile tasks such as JavaCompile setting the Java home on fork options is absoleted by the toolchain functionaliy.
For the corner-case when toolchain spec fidelity does not allow to select a desired JDK, forkOptions.executable can be used as a work-around.

For the corner-case when toolchain spec fidelity does not allow to select a desired JDK, forkOptions.executable can be used as a work-around.

Can be, or will be after this is solved?
Because currently I see no way to use a custom executable, for example to execute something with a Java runtime built by the current build as long as there is no was to programmatically create a toolchain.
As far as I have seen, with Gradle 8 now the toolchain is used unconditionally even if none was set explicitly and forkOptions.executable is simply always ignored, without it being deprecated or anything.


funct7 values of SRA,SUBW,SRAW appear to be incorrect in unpriv section 4.2.2 of version 20240411.

Hi,
I think that the funct7 values in unpriv section 4.2.2 of version 20240411 are incorrect.
In the V20191213, funct7 values are 7-bits (in section 5.2).
The values are 0000000 or 0100000.

However, in the version 20240411, funct7 values have only 6-bits; the least significant bits seem to be missing.
The values are 000000 or 010000.

Is this correct?
The relevant file is:
https://github.com/riscv/riscv-isa-manual/blob/353e88f8d5c629be5a42ada8618fcfa9acb5d287/src/images/wavedrom/rv64i_int-reg-reg.adoc?plain=1#L13

@wmat this is indeed a bug; these funct7 fields should all have another 0 appended on the right.

Thank you!


card_type: separator issues using Tap Action activate all the time more-info

For any feature request you can open a new discussion here:
https://github.com/Clooos/Bubble-Card/discussions/categories/feature-requests
For any question you can open a new discussion here:
https://github.com/Clooos/Bubble-Card/discussions/categories/q-a
Describe the bug
A clear and concise description of what the bug is.
Every action tap action I use in the separator show more info
To Reproduce
Steps to reproduce the behavior:

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

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
YAML
If applicable, add any relevant YAML code.

type: custom:bubble-card
card_type: separator
name: Luces
icon: phu:bulb-candle
tap_action:
action: call-service
service: automation.trigger
target:
entity_id: automation.ios_event_prueba
sub_button:

entity: light.luces
show_state: true
icon: mdi:light-recessed
show_icon: true
show_background: false
show_attribute: false

Your code here

type: custom:bubble-card
card_type: separator
name: Luces
icon: phu:bulb-candle
tap_action:
action: call-service
service: automation.trigger
target:
entity_id: automation.ios_event_prueba

Informations (please complete the following information):

OS: [e.g. iOS]
Browser/App: [e.g. chrome, safari]
Bubble Card version: [e.g. 2.0.4]
Home Assistant version: [e.g. 2024.6.4]

Additional context
Add any other context about the problem here.
Thank you! 🍻

Well I was not aware that it was even possible to add a tap action directly in YAML on the separator.
It seems that Bubble Card is living its own life now 👀

hahahaha ;) coool
Andres Roepke Del Solar.
Ingeniero Civil Industrial
Ingeniero Electronico
Mobile 88196932
On Mon, Jul 8, 2024 at 12:47 Cloos @.***> wrote:

Well I was not aware that it was even possible to add a tap action
directly in YAML on the separator.
It seems that Bubble Card is living its own life now 👀
—
Reply to this email directly, view it on GitHub
https://github.com/Clooos/Bubble-Card/issues/634#issuecomment-2214675941,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIOTKWRYQMD4Y2J5MGZRX2TZLK7BVAVCNFSM6AAAAABKP5VY2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJUGY3TKOJUGE
.
You are receiving this because you authored the thread.Message ID:
@.***>


While building charm with AVX512 flags facing error

I am trying to build charm 6.10.2 with AVX512 flag ./build charm++ multicore-linux-x86_64 iccstatic --with-production "-O3 -ip -xCORE-AVX512"
Facing below error

below attachement is config.log file
config.zip
kindly give us a solution.
Even though this fix  was done in 6.10.2 version it is still occurring.

It is misdetecting the Python version, which is why the build fails. It is the same issue as https://github.com/UIUC-PPL/charm/issues/3546.
Could you try building Charm++ 7.0.0 with the same options?

python - 3.9.7
bash - 5.0.17(1)-release
awk - GNU Awk 5.0.1, API: 2.0 (GNU MPFR 4.0.2, GNU MP 6.2.0)
Above is my version details.

But the same builds fine for  charm 6.10.2 with AVX512 flag ./build charm++ multicore-linux-x86_64 iccstatic --with-production "-O3 -ip " . is it expected ?

Yes 7.0.0 builds after running "make pgm" , pgm file is not present after building successfully Is it expected ?

icpc: warning #10237: -lcilkrts linked in dynamically, static library not available . i get this warning , do u know how to get rid of it.

(below question is not related but i am just asking incase if you know.)
5. I get below error if use charm-AVX512 for compiling namd. I followed this post

the point 5 is also thrown from charm lib only

One thing worth mentioning is that the parameters at the end of the build command should not be enclosed in quotes. For example, ./build charm++ multicore-linux-x86_64 iccstatic --with-production -O3 -ip -xCORE-AVX512.

Please reopen if this is still an issue.


Ignore offline updates

Is there a way to ignore updates sent when Bot was offline?

See description of the option "ignore_background_updates": https://core.telegram.org/tdlib/options. This is the only possible solution.

Thanks. That is what I was looking for

Are options beginning with 'x' or 'X' shared between two independent tdlib instances?

No, options can't be shared between different instances.

@levlam, what is the best moment for setting options? Is it ok to do it before call to setTdlibParameters?

@pylakey Yes, it is ok. Options can be set any time and some even must be set before setTdlibParameters.


The random generator now properly uses the seed to produce deterministic results.

I am not sure what the wanted behaviour is, but this looked like it might be unintentional. Since the seed wasn't used to seed the random generator, successive calls to random() of any kind (which occur at several points in the code) gave actual random results, even when a seed was given.
This patch makes the seed be the actual seed of the random generator. This got rid of some of the problems I was having when trying to modify the ocean_level variable so that it can actually modify the ocean level. That is not done yet, however.
It also got rid of the remaining lack of deterministicness I saw when regenerating a world with the same seed (there were some slight changes in colors...hopefully weren't my eyes).
If this proves useful, the seed-variable could probably be removed as a parameter from several function calls. In theory it should not be needed anywhere after having set off the RNG.

If somebody found the time to explain what "coverage" is and how it tends to criticise files that were not changed, I would very much appreciate that. :)

While I somewhat understand 'coverage' I would appreciate if someone could explain what tests are run and how we can add new coverage tests. That way I can check any code I write before submitting it to see if it will fail coverage test and if necessary add a test for my new code.

Due to the random nature of some of the tests... for example the smoke test, that it sometimes covers code paths in one run in not in others. As we write more tests, this variability will decline.
Coverage basically means "code coverage".  When a line of code isn't covered it means that it is never run. This can mean that it is dead-code or that we haven't written tests that cover that specific functionality.

Thanks for the clarification. :)
So more methods are needed in the test-module, I will keep it in mind.

random.seed() seeds the random number generator with the system's current time. This is actually is redundant code because when using random functions, it will automatically seed with the system's current time.
I recommend you remove the seed.random() from 394.
That you have random.seed(seed) afterwards is great, because it will make the system more deterministic when you define a seed.

In other languages I have used there was always need to initiate the random generation with a single call to seed(). I will double check if this is necessary and adjust the code if necessary.

https://docs.python.org/2/library/random.html#random.seed
Initialize the basic random number generator. Optional argument x can be any hashable object. If x is omitted or None, current system time is used; current system time is also used to initialize the generator when the module is first imported.

So, if nothing is given... it uses current system time.
This means if you run random.randint(0, 65535), it will auto initialize with random.seed().

No, it means if you run random.seed() it uses random.seed(systemtime()).
I am still reading, give me a couple of minutes.^^

Just tested it in the console (Python 3), you seem to be correct.

Well, not exactly redundant, it gets a new seed... system time. But for our use, is totally redundant as you only need a random number when you didn't give a 'seed'. Now that you have this new seed, you seed the random.seed(seed) which will be used throughout which gives us predictable determinism (thankfully). You also pass this seed on to platec.
So as I seed, drop the first random.seed() in your PR for being not necessary. The original (at the top) was also redundant.

Please re-read what I quoted:
"current system time is also used to initialize the generator when the module is first imported."
That is why you don't need to run random.seed() by itself, unless you want to use another time as a seed.

Sorry, I missed that last part. Thank you for the clarification. :)
Commit is up.

As a bonus: every commit gives a new shot at the coverage-test due to the involved randomness. Maybe the test works out this time.^^

;) It's great


Add custom failure messages with lazy stringification

Is it or will it possible to output custom messages only when REQUIRE or CHECK fails? In Catch, we can capture certain variables before doing the check, but that unnecessarily creates a string and then discards it when the test succeeds (which should be more common than failures).

this is planned - it is in the roadmap - INFO - but It will go into version 2.0 for which I cannot promise a release date. I will have to figure out the reporters API and such contextual information will have to fit the picture. I'm gearing up for a 1.1 release with fixes in the upcoming days.
Currently I don't see how to implement this without always constructing the strings - even when the assertions pass.

This is implemented in the dev branch - check out the documentation


Update to PHPUnit 9

Note: Removes support for running the PHPUnit tests with versions of PHP <= 7.2

Tested with PHP 7.3 (Debian Buster) and PHP 8.0 (Debian Bullseye + PHP from sury.org)


Linters. Selecting files if the status is not "removed".

Motivation and context
This patch will help avoid errors in the future when the utility tries to perform a static analysis of the code of a file that is removed from the repository as part of PR.
The check will include files that do not have the removed status.
How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[ ] I have updated the license header for each file (see an example below)

# Copyright (C) 2021 Intel Corporation
#
# SPDX-License-Identifier: MIT

Coverage remained the same at 71.613% when pulling b2a141302ba416036ec89f519ffb521029eea01e on dvkruchinin:dkru/update-linters-workflow-configs into 55b20e197d74bae12786a849dc315fb2f71a2cec on openvinotoolkit:develop.


Autoloader fails on '0' class

Hi, we are using PHPStan and we have lot of tests analysed by phpstan, with data providers, that looks like this:
yield [
    [
        'a' => '1',
        'b' => '0',
    ],
];

Since phpstan checks if class exists, it calls class_exists on strings and it throws exception Exception (Class name is empty) thrown while autoloading class 0.
While debugging i found out it is caused by the custom autoloader, here is minimal code to break things up:
<?php

require __DIR__ . '/vendor/duccio/apns-php/ApnsPHP/Autoload.php';

var_dump(class_exists('0'));

It would be nice to make this package use composer autoloader (classmaps) or PSR-4 as suggested in #135 ?
I can send PR migrating this repository to PSR-4 as i can do it automatically with rector - https://github.com/rectorphp/rector

Basically this library breaks this assumption and throws an exception instead: https://3v4l.org/RIFmv


Delay in sending logs to Logstash

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

It looks like in case of a lot of log events (about about 1 million per day), python-logstash-async doesn't process them in time and keeps them in the queue. This leads events being pushed to logstash with a long delay(several hours in our case).

Operating System and version (e.g. Linux, Windows, MacOS):
Code example or link to GitHub repo or gist to reproduce problem:
Other diagnostic information / logs:
Logs from `cvat` container

Next steps
You may join our Gitter channel for community support.

I can start working on this if someone can point me towards a direction. I am new contributor.

In general, each data may be delayed

I can start working on this if someone can point me towards a direction. I am new contributor.

Hi,did you fix this problem?

I can start working on this if someone can point me towards a direction. I am new contributor.
Hi,did you fix this problem? @abidahmadq

@abidahmadq did you fix this problem

Probably it is not relevant anymore. New logging system.


readme in the root is wrong

Especially the ability to push files.
using (SyncService service = new SyncService(new AdbSocket(), device)) //new AdbSocket() is wrong
using (Stream stream = File.OpenRead(@"C:\MyFile.txt"))
{
service.Push(stream, "/data/MyFile.txt", null, CancellationToken.None);     //params is wrong
}

@bestfc It took a while but I updated the readme file :). Hope it helps!


Message Box Position Issue and Reversed Background Text in Chat with Rider

Describe the bug
The message box is positioned too low on the screen, and the background text is displayed in reverse.
To Reproduce

Go to 'Place Order'.
Complete the process to place the order.
When the order is placed and assigned to a rider, click on 'Chat with Rider'.
See error

Expected behavior
The message box should be positioned slightly higher for better accessibility, and the background text should be displayed correctly, not in reverse.
Screenshots

Smartphone (please complete the following information):

Device:  IOS

fixed


Formal documentation on what a README should be

We need to have a more formal definition on what we expect from the executor's READMEs. This can be a work in progress evolving over time but we need a document where to check what is the current status on what is needed

A very first draft can be found here: https://docs.google.com/document/d/1UebHh5WDArscXZkT5TKENDdsce0n9KmvkHJkoucBT_w/edit#


code search with meilisearch

WIP

In case the file sort order is part of the search engine code, could stable sort(https://github.com/go-gitea/gitea/issues/24170) be implemented here? :)

@techknowlogick I tested this PR. While I can start Gitea without errors and set meilisearch as the code indexer, I always end up with No source code matching your search term found. for every search. Even just basic ones, e.g. searching for get or similar (fuzzy mode).
I can see that some indexing is happening in the connected meilisearch instance.
Let me know how I can dig deeper to provide some meaningful log insights or similar.

@techknowlogick I tested this PR. While I can start Gitea without errors and set meilisearch as the code indexer, I always end up with No source code matching your search term found. for every search. Even just basic ones, e.g. searching for get or similar (fuzzy mode).
I can see that some indexing is happening in the connected meilisearch instance.
Let me know how I can dig deeper to provide some meaningful log insights or similar.

This might also be a general problem in the Gitea repo search code. I have been trying to get the Elasticsearch support working with Zincsearch and what you describe is exactly the behaviour I see with Zincsearch as well.

@poVoq I replied to @pat-s elsewhere, but I'll repost here so that anyone else tracking can also see. The reason no search results are coming up is that the code for searching in meilisesrxh doesn't exist yet, only indexing. That's what the WIP part of this PR is.
Your issue with zincsearch may be something else, and you may wish to open a an issue about that to track.

Maybe it's a related issue https://github.com/zincsearch/zincsearch/issues/538

@techknowlogick I tested this PR. While I can start Gitea without errors and set meilisearch as the code indexer, I always end up with No source code matching your search term found. for every search. Even just basic ones, e.g. searching for get or similar (fuzzy mode).
I can see that some indexing is happening in the connected meilisearch instance.
Let me know how I can dig deeper to provide some meaningful log insights or similar.

This might also be a general problem in the Gitea repo search code. I have been trying to get the Elasticsearch support working with Zincsearch and what you describe is exactly the behaviour I see with Zincsearch as well.

Maybe here is a related issue https://github.com/zincsearch/zincsearch/issues/538

@techknowlogick no plans to finish this? Really a pity as otherwise only Elastic/Opensearch seem to work and those are really not great.

Because indexer will have a big refactor, so I think this PR will be affected. Maybe another PR could be created after the refactor finished. ref: #25174


Added some new methods for context window weight generation

There seems to be some interesting potential for experimentation in the weights for the context window, right now there is only flat and pyramid and they are identical for every step.
This pull request adds a few new shapes for the weights, but also introduces a new feature: by passing in the sigma it is possible to change the weights over time and for example have a stronger weight for the center conditionings at the beginning which then gradually smooths out towards the end. Or vice-versal.

Long-term it would be nice if those weights could somehow be exposed in the context options, so one could write a custom component to introduce additional ways to change them. Maybe there is a way and I did not see it, but given the way how the callback functions are currently integrated I had difficulties trying to patch them from the "outside" that's why I added the pull request.

Looks good, when I get a chance this evening, I will merge this into develop first so I can increment the version number the pyproject.toml file and test out each method before merging into main.
I didn't think anyone would be too interested in creating nodes for defining custom fuse methods, but I can definitely make that happen sometime in the next month. Currently doing a bunch technical debt related tasks in AnimateDiff-Evolved and Advanced-ControlNet and working on documentation/tutorials for all features before I start adding anything else that will require big code refactors/enhancements. I'll let you know when something like that is integrated, I plan on trying out some unconventional things with new contexts so that's likely when I can expose some of the context options guts to be extendable with custom nodes.

Cool thanks! And of course I agree that this is not a high priority item, and I can always do another pull request in case I find some interesting use case for the weights. How do you generally feel about proposed changes that add ui elements to existing nodes? I guess the hurdles for those might be higher? Not sure if there are some unwritten laws or "ui etiquette" I should know about.


Update README.md

bingleton url -> clooi url

needs doing on the noob guide too

Sure, done -- just did a straightforward search & replace in this case, haven't tried to independently test. All instances of it looked like they should be replaced though.


Email set up

We need to figure out which service we are going to use to email users and how we are going to implement this with Phoenix.

Closing as we decided to use Mailgun and Bamboo.


Convert simple alias functions to abbreviations

Add conf.d/breeze.fish script, which initialises all simple
abbreviations and removes them on uninstall.
Remove replaced alias functions.
Remove git completions file, which should no longer be needed.
Resolves #41

I checked out it.
Is it automatically show original command when I hit enter key?

Yes, exactly! 🙂
I only did it for the alias-like functions where the abbreviation maps directly to an expanded command, so the following ones that have more custom functionality don't expand:

ga
gb
gbl
gbu
gco
gd
gl
grm
gs

I was also thinking we could name space the remaining breeze functions and add abbreviations for them. So, for example, gd would expand to _breeze_git_diff.   I think this could help users understand/remember when they are running a custom breeze function, make them more findable in history, and better group them in the user's functions folder. Let me know what you think! 🙂

My latest commit includes name spacing of custom functions in case we want to include this.

@bingocaller

I tried. but, auto-complementary shows the function name.
Users may surprise about it. I guess the original git function should appear.
Do you know how to fix this?

Yes, that was my intention. I thought it might reduce confusion about which functions are being run, but it seems that is not the case. 😅
If we want the abbreviations to expand to git <command> while still doing the file shortcuts we would have to overload git somehow. We could potentially do that, but I think it's out of scope for this PR. I'd be up for doing a separate PR with a suggestion for how to do it, though! 😁
In the meantime, I'll remove 9fd197d so we can merge this, if you agree with the implementation.

@shinriyo I've removed 9fd197d, so this should be good to merge if you agree with converting the simple alias functions to abbreviations.


Added mention of .Data.Pages, removed duplicate .Site.Pages mention.

Great catch, @dimo414!  Thank you for your contribution!
Committed as caaf6370689ab135a9e348b6662502e73dc75ac8 (master) and 32ede3e68ff1a193cd3679df1efb23d260a2a452 (v0.14.docs).


golang buildin page broken

page link: https://golang.org/pkg/builtin/
expect to see the api index,
get "/src/builtin/builtin.go:88:11: expected type, found '=' (and 1 more errors)"

Dup of #21601.

Closing as duplicate.


Fix wildcard equality operator tests with x/z in LHS

For the wildcard equality operator only x and z bits of the right hand side value are considered as wildcard bits.
x and z bits on the left hand side are still compared and may result in the comparison itself returning x.
There are a few test entries for the wildcard equality operator test that do not consider this and expect the wrong value. Correct these tests to expect that the result is 1'bx.

I think it says "may result" since the result can also be 1'b0 or 1'b1 if it is clear from other bits that the values are/are not equal. E.g. 4'bx101 == 4'b000x will yield 1'b0.


3.0 - Added new sensors and fixed some stuff

Removed timeout from init because it caused issues with adding the integration (#85, #84)
Fixed bug with number attributes (#64)
Fixed bug with entity class (#61)
Bumped weconnect to 0.49.0
Added door states

Front & Rear
Bonnet & Trunk

Lockstate is not binary, unknown is also available and will give wrong info when used as binary (#73)
More sensors are not binary, moved them to sensor (This is breaking for some automations because the entity name and type will change)
Implemented SensorDeviceClass
Removed miles/kilometers celcius/fahrenheit entities because home assistant will convert them
Implemented async_forward_entry_setups (https://developers.home-assistant.io/blog/2022/07/08/config_entry_forwards/)

See #93


Use images from articles and not from thumbnails

This PR https://github.com/viniciuskneves/berlin_en_news/pull/13 introduced images to Tweets.
So far we're using thumbnails which are low resolution and can get blurry once you open Twitter on a computer.
We could use the images from the articles instead, which have a higher resolution and sometimes even more than one image.
Article with one image: https://www.berlin.de/en/news/coronavirus/6122241-6098215-coronavirus-restrictions-longer-stay-in-.en.html
Article with 2 images: https://www.berlin.de/en/news/coronavirus/6123872-6098215-retail-calls-on-supermarket-customers-to.en.html
@leonardopavanrocha FYI

@viniciuskneves  It makes sense to use the article image instead of the thumbnail. Since I am already familiar with this issue, I can implement this during the week.


react-addons-shallow-compare  -> React.PureComponent

Remove the legacy addon and replace with PureComponent as discussed here:
https://facebook.github.io/react/docs/shallow-compare.html

Hey, the PR looks good! It is conflicting with our other PR that I just merged. If you rebase I'll merge ASAP.

@borisyankov done

Thanks. 👍

Has the development of react-sparklines come to a halt? Since nobody seems to care about fixing the latest release that is broken.


Firebase Bug Reporting automation is failing

The bugs, using Firebase Extension, is not working.
Trigger GitHub issues from Crashlytics
<EMAIL_ADDRESS>

com.linardsl.libhacontimig.hm.betaPro_issue_ac637dbbc1ac137cb9bdcf74ea1fbc93_crash_session_65b9ae57001f00011e2577c0a84760f7_DNE_0_v2_stacktrace.txt


Make CSR error

Hi
I am running ubuntu 16.04 with kvm enabled and ran into this issue, I was following the readme for CSR and the make ran into this error:
devops@devops:~/myvirtual_labs/vrnetlab/csr$ make
Makefile:15: warning: overriding recipe for target 'docker-pre-build'
../makefile.include:18: warning: ignoring old recipe for target 'docker-pre-build'
for IMAGE in csr1000v-universalk<IP_ADDRESS>-serial.qcow2; do \
	echo "Making $IMAGE"; \
	make IMAGE=$IMAGE docker-build; \
done
Making csr1000v-universalk<IP_ADDRESS>-serial.qcow2
make[1]: Entering directory '/home/devops/myvirtual_labs/vrnetlab/csr'
Makefile:15: warning: overriding recipe for target 'docker-pre-build'
../makefile.include:18: warning: ignoring old recipe for target 'docker-pre-build'
rm -f docker/*.qcow2* docker/*.tgz* docker/*.vmdk* docker/*.iso
cat cidfile | xargs --no-run-if-empty docker rm -f
cat: cidfile: No such file or directory
rm cidfile
rm: cannot remove 'cidfile': No such file or directory
Makefile:15: recipe for target 'docker-pre-build' failed
make[1]: [docker-pre-build] Error 1 (ignored)
Building docker image using csr1000v-universalk<IP_ADDRESS>-serial.qcow2 as vr-csr:16.04.01
cp ../common/* docker/
make IMAGE=$IMAGE docker-build-image-copy
make[2]: Entering directory '/home/devops/myvirtual_labs/vrnetlab/csr'
Makefile:15: warning: overriding recipe for target 'docker-pre-build'
../makefile.include:18: warning: ignoring old recipe for target 'docker-pre-build'
cp csr1000v-universalk<IP_ADDRESS>-serial.qcow2* docker/
make[2]: Leaving directory '/home/devops/myvirtual_labs/vrnetlab/csr'
(cd docker; docker build --build-arg http_proxy= --build-arg https_proxy= --build-arg IMAGE=csr1000v-universalk<IP_ADDRESS>-serial.qcow2 -t vr-csr:16.04.01 .)
Cannot connect to the Docker daemon. Is the docker daemon running on this host?
../makefile.include:24: recipe for target 'docker-build-common' failed
make[1]: *** [docker-build-common] Error 1
make[1]: Leaving directory '/home/devops/myvirtual_labs/vrnetlab/csr'
../makefile.include:9: recipe for target 'docker-image' failed
make: *** [docker-image] Error 2
devops@devops:~/myvirtual_labs/vrnetlab/csr$ ls
csr1000v-universalk<IP_ADDRESS>-serial.qcow2  docker  Makefile  README.md
devops@devops:~/myvirtual_labs/vrnetlab/csr$ ls -la
total 1423512
drwxrwxr-x  3 devops devops       4096 Oct  5 10:35 .
drwxrwxr-x 19 devops devops       4096 Oct  5 10:35 ..
-rw-rw-r--  1 devops devops<PHONE_NUMBER> Oct  5 10:21 csr1000v-universalk<IP_ADDRESS>-serial.qcow2
drwxrwxr-x  2 devops devops       4096 Oct  5 11:55 docker
-rw-rw-r--  1 devops devops        694 Oct  5 10:32 Makefile
-rw-rw-r--  1 devops devops       3994 Oct  5 10:32 README.md
devops@devops:~/myvirtual_labs/vrnetlab/csr$

I already installed kvm
devops@devops:~/myvirtual_labs/vrnetlab/csr$ kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used

and have docker installed as well from apt-get.
Am I missing something? I am using the .qcow2 image from cisco.com downloads

was able to get it to make image by using sudo, and installed few other libraries.
cd vrnet
cd csr
sudo make docker-image
csr1000v-universalk<IP_ADDRESS>a.qcow2 from cisco.com
docker run -d --privileged --name my-csr-router vr-csr:16.03.01


Your feature request title here

What feature would you like to see?
I want Scroll Configruation use NOScrollGlow

You can already set this through the theming: https://github.com/woltapp/wolt_modal_sheet/blob/main/lib/src/theme/wolt_modal_sheet_theme_data.dart#L133
Here is an example how to set the theming: https://github.com/woltapp/wolt_modal_sheet/blob/main/example/lib/main.dart#L161

Still it's not working for me any help really it would be appreciated.
On Fri, 16 Feb 2024, 13:49 Cagatay Ulusoy, @.***> wrote:

You can already set this through the theming:
https://github.com/woltapp/wolt_modal_sheet/blob/main/lib/src/theme/wolt_modal_sheet_theme_data.dart#L133
Here is an example how to set the theming:
https://github.com/woltapp/wolt_modal_sheet/blob/main/example/lib/main.dart#L161
—
Reply to this email directly, view it on GitHub
https://github.com/woltapp/wolt_modal_sheet/issues/147#issuecomment-1947939684,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4LUA55QBFFKFJKC3XBTXVTYT4I7NAVCNFSM6AAAAABDLSYTYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBXHEZTSNRYGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

This is addressed in this PR and will be released in 0.9.0
https://github.com/woltapp/wolt_modal_sheet/pull/283