bug(docs): example for Location.move() implies it alters state when it does not

The example given for Location.move() in the main labware documentation https://docs.opentrons.com/v2/new_labware.html is:
from opentrons import types

metadata = {'apiLevel': '2.2'}

def run(protocol):
     plate = protocol.load_labware(
        'corning_24_wellplate_3.4ml_flat', slot='1')
     plate['A1'].center().move(
        types.Point(x=1, y=1, z=1)) # 1mm up, to the right, and towards the
                                    # back of the robot

This implies that this operation will "move" the robot's idea of where plate A1 is by this offset.
In fact the function docs say that it does not alter state and so the example above would do nothing. A better example would at least involve assignment e.g.:
a_bit_off_center = plate['A1'].center().move(
        types.Point(x=1, y=1, z=1)) # 1mm up, to the right, and towards the
                                    # back of the robot

(the text of that page should also say that it creates a new point, rather than moving existing point)

Thanks for reporting this. We'll fix the example, probably by doing either:
pipette.move_to(plate['A1'].center().move(types.Point(x=1, y=1, z=1)))

or
pipette.aspirate(100, plate['A1'].center().move(types.Point(x=1, y=1, z=1)))

As an aside, my personal opinion is that move is an inherently misleading name for this method. a.move(b) should instead be one of:

a.moved_by(b)
a.plus(b)
a + b

See #4763.


Crash when opening imgur link

https://www.reddit.com/r/testslideforreddit/comments/hpw9g1/imgur_link_in_comment_causes_crash/

Can't reproduce this one


Use subscribe/unsubscribe instead of register/unregister

It would be nice to keep naming consistent with other JS APIs like Observable

Closing in favor of #3


Update README.md

Murali Mandayam added his mid-term capstone project details.

Added details on MM's mid-term capstone project.

Hi Murali, getting close! Can you cut the summary in half and change the kaggle link to be a link on the work 'Kaggle' so the entire url does not show? I'm hoping for folks to be able to scan the list. Thank you, happy to help if this is becoming tedious.

Completed on ux305 via commandine merge.

Done on commandlne


Redirecting Traffic Through MacBook Proxy to Bypass DPI on Smart TV

Description:
I am trying to bypass DPI blocking on YouTube by using the spoof-dpi utility on my MacBook. It works fine on the MacBook itself, but I also want to route traffic from my Samsung Smart TV through this proxy to watch YouTube in 4K without issues. However, the traffic from the TV does not seem to reach the spoof-dpi utility running on the MacBook.
Home Network Setup:

Router: MikroTik hAP ac² (IP: <IP_ADDRESS>)

RouterOS v6.49.15 (stable)
DNS-over-HTTPS setup using AdGuard DNS.

MacBook: Running spoof-dpi (IP: <IP_ADDRESS>)

macOS 14.5 (23F79)

Smart TV: Samsung (IP: <IP_ADDRESS>)

spoof-dpi Settings:
spoof-dpi -addr <IP_ADDRESS> -port 8080 -dns-addr <IP_ADDRESS> -debug

Version:
spoof-dpi v0.10.6

Current Status:
When I start spoof-dpi on my MacBook, it listens on port 8080, and debug logs show that it handles requests from the MacBook itself correctly. However, the traffic from the Smart TV does not reach the utility. I tried adding a NAT rule on my MikroTik router to redirect the TV's traffic to the MacBook, but it did not work.
MikroTik NAT Rule:
/ip firewall nat add chain=dstnat protocol=tcp dst-port=80,443 src-address=<IP_ADDRESS> action=dst-nat to-addresses=<IP_ADDRESS> to-ports=8080

Despite trying different configurations and even disabling all firewall rules, the traffic from the TV does not seem to be redirected correctly.
Question:
How can I configure my network so that the Samsung Smart TV routes its traffic through the spoof-dpi proxy on my MacBook? Any guidance on setting this up or troubleshooting steps would be greatly appreciated.
Thank you!

+1

+1

This os HTTP/HTTPS proxy(only handles layer 7 packets not all the tcp packets) so that you should somehow be able to set the HTTP/HTTPS proxy setting on your preferred device, otherwise you will have to hack the device.


Investigate solutions for issues with changing the format, renaming and adding fields

If an existing field is renamed or the format is changed the user will not be able to modify that field in past forms. If the change breaks validation for past forms this will prevent the user from making any edits.
Currently if a new field is added to existing forms the user would not be able to edit past forms and add info for the new field.

The fix for new fields would likely involve changing the diff algorithm in getModifiedProperties. This still would not fix the issues with changing the format of existing fields or renaming fields.

I think this warrants further investigation and analysis before picking up.


add optional comment on fields

fixes #17
Proposed Changes

add +optional comment on fields that have omitempty

Nice one, thanks @pivotal-nader-ziada ! Now that I'm looking at the api conventions a little more closely, it looks like these optional values should also have a pointer type :thinking: no worries if you'd rather we do that in a separate issue tho (i totally missed it the first time around)
Before we merge this would you be able to add a bit more detail to the commit message around why we're making this change?
/lgtm
/approve
/hold
/meow space

/lgtm
Thanks for the follow up!


Validator ranked by staked amount

Now validators are ranked by stakedAmount

Making it easier to test and validate the staking flow, but also more user friendly
(Note for later: maybe displaying the stakedAmount somewhere could be relevant)

(Also there seems to be some build issue, according to Vercel)


Update sbt-scoverage

Codecov Report

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

@@           Coverage Diff           @@
##           master      #23   +/-   ##
=======================================
  Coverage   64.33%   64.33%
=======================================
  Files           5        5
  Lines         143      143
  Branches        9        4    -5
=======================================
  Hits           92       92
  Misses         51       51

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 e58be7c...57ba8e0. Read the comment docs.


Update README to add demo and stats

Added

Demo video
Stars
npm version
Monthly downloads

So seems like adding the demo to Github assets is not working. I think we should upload the video to the repo.

Fixed


Fix CLUSTER variable name

Modify CLUSTER variable name to ARO_CLUSTER_NAME to reflect the parameter passed to the deployment

Learn Build status updates of commit ac7f99a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/openshift/quickstart-openshift-arm-bicep-template.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@johnmarco,
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


IPsec cleanup

For IPsec some option are listed that are not valid in current setup.
Remove: AES-GCM until tested and functional
Change: IKE, charon supports setting to ike or ikev2 IKE supports both IKEv2 and IKEv1 according to documentation. Option needs to be auto or ikev2 not ikev1.

@jschellevis how relevant is this ticket in 2016?

Lots have changed.. i'd say close. Ad has done a lot of cleanups and enhacements.

ok


How can i pass object instead of array? Is there any option available?

Config
import React, { Component } from 'react';
import MUIDataTable from "mui-datatables";

const columns = ["Name", "Company", "City", "State"];

const data = [
{ name: 'Some Text', company: 'Github', city: 'Some Text', state: 'Some Text' },
{ name: 'Some Text', company: 'Github', city: 'Some Text', state: 'Some Text' },
];

const options = {
    rowsPerPage: 5,
    styles: {
        table: {
            toolbar: {
                root: {
                    borderBottom: '1px solid #e4e4e4'
                },
                search: {
                    searchText: {
                        color: 'red'
                    }
                }
            }
        }
    }
};
class MUITable extends Component {
    render() {
        return (

                <MUIDataTable
                    title={"Employee List"}
                    data={data}
                    columns={columns}
                    options={options}
                />

        );
    }
}

export default MUITable;

Issue
I would like to populate a table via an object, but it doesn't work. I got the following error.

Your Environment

Tech
Version

mui-datatables
1.0.7

node
9.5.0

OS
Windows 7 SP 1

@syedabuthahirm It is expecting an array. Just match it up to your columns so your config should look like this:
import React, { Component } from 'react';
import MUIDataTable from "mui-datatables";

const columns = ["Name", "Company", "City", "State"];

const data = [
['some text', 'Github', 'Some Text', 'Some Text'],
['some text', 'Github', 'Some Text', 'Some Text']
];

const options = {
    rowsPerPage: 5,
    styles: {
        table: {
            toolbar: {
                root: {
                    borderBottom: '1px solid #e4e4e4'
                },
                search: {
                    searchText: {
                        color: 'red'
                    }
                }
            }
        }
    }
};
class MUITable extends Component {
    render() {
        return (

                <MUIDataTable
                    title={"Employee List"}
                    data={data}
                    columns={columns}
                    options={options}
                />

        );
    }
}

export default MUITable;

Thanks, @gregnb.
I think we need to provide an option for the object as well.

No problem @syedabuthahirm. As far as the objects for data It is not something I am looking to support at this time


fix setting states

Description
Changes proposed in this pull request:

fix os usage setStates which causes broken create form for log pipelines.

Related issue(s)

/retest


WebApps staging slots can be linked from the preview environment

Is your feature request related to a problem? Please describe.
If I link to the backend production WebApps and then create a swa preview environment, I cannot link the prev env to the WebApps slots created from the production WebApps.
Describe the solution you'd like
Even if WebApps already linked from swa exist, it is possible to link to WebApps in a different slot.
Describe alternatives you've considered
Nothing
Additional context
Nothing

Hi @takashiuesaka, this is not possible as of now, a web app can only be linked to one SWA at a time, you can find this in the official documentation. Please let us know if you need more information. Thanks.

HI @rupareddy5-21, I am proposing a feature request. I am already aware of that limitation, but I am very disappointed that I cannot use the slot feature of WebApps because of that limitation.

Hi @takashiuesaka
I need to correct: We do indeed allow slots to be linked to staging environments.
It might be confusing in the Portal UI right now since it will show a validation error after selecting the Web App - but you can go ahead select the staging slot and hit link. This is solely because the validation currently does not get retriggered after the slot selection. We can work on improving this experience.

To be able to have a consistent link from your staging environment to your backend slot make sure to use either Branch environments or Named environments

Hi @annikel ,
Thank you for your reply.
My feature request is to be able to link from production and other pre-production environments in one SWA to production and slot in one WebApps. I don't think this is possible.

@takashiuesaka
I went ahead and tested the use case of SWA prod env -> Web App prod slot & SWA dev env -> Web App dev slot. It worked for me, as you can see here:

So, to your point @takashiuesaka, this use case is supported, but I did run into a bug which may have deterred you from doing this.
There was indeed a UI bug when attempting to link the Web App dev slot to the SWA dev slot after having previously linked the Web App prod slot to the SWA prod slot. The Portal indicates that it cannot link to the web app (due to it already being linked) but this should not occur when it is already linked to the current SWA.

Can you validate this @annikel? I think we should classify this as a Portal bug

Hi @thomasgauvin, thank you for verifying this.
Yes, I could not link to the WebApps slot because of the error in Portal you showed above.
I understand that it is a bug in Portal, but then how did you link to the slot from pre-production environment?
Could you please tell me how to do it?

@takashiuesaka While the error does pop up in the UI, you can still choose the App Service slot you wish to link your app environment to. Hope this helps! I have logged this bug with the Portal team and will keep you updated when it is fixed.

Man, I just ran into this bug last week and it's been two years :(.

The issues with the UI for this feature are terrible, when i try to link a function app slot to the web app staging environment I just get An error has occurred. ....

Same issue as @hawkzey here

It also does allow you to do it with some weird UI flows but it then breaks and doesn't let you remove it, is there a better way of doing this via cli?


NHibernateConfigurationFileCache for Sharp Lite

In Sharp Arch 1.9.6 we depended on the NHibernateConfigurationFileCache feature which dramatically reduced our application start up time.
I noticed this feature missing from Sharp Lite and was wondering if there was a reason for it? Is this something that can be added and used alongside the new 3.2 method of Nhibernate configuration.

This has been fixed.


Auto-manage /usr/local/var/alternatives/ symlinks for versioned @ formulae

Provide a detailed description of the proposed feature
If the user installs, for example, llvm@13, create the /usr/local/var/alternatives/llvm symlink to the llvm version unless a version of the llvm formula is already installed.
The base formula would have the highest priority, followed by the highest version of a versioned formula installed, and the symlink would be updated on formula install/uninstall.
It may be worthwhile to have some kind utility to manage this symlink like update-alternatives in Debian, but this kind of automatic management should be sufficient for most people.
What is the motivation for the feature?
Making versioned formulae easier to use by both the user and brew itself.
One example is #13780.
How will the feature be relevant to at least 90% of Homebrew users?
It wouldn't be, versioned formulae are not often used.
What alternatives to the feature have been considered?
I don't have any.

If the user installs, for example, llvm@13, create the /usr/local/opt/llvm symlink to the llvm version unless a version of the llvm formula is already installed.

This would break backwards compatibility so: we're not going to do this.
We may be open to something like /usr/local/var/somethingnew/llvm being handled in this way, though.
Would that work for you?

This would break backwards compatibility so: we're not going to do this.
We may be open to something like /usr/local/var/somethingnew/llvm being handled in this way, though.
Would that work for you?

Yes I think so, would you like me to submit a PR for this?

@rkitover Just to be clear: this won't change anything about how Homebrew itself works or uses e.g. LLVM but it'll perhaps make it easier to handle your PATH. Do you still want this given that?
I also wonder if the best fit for this may be a opt/llvm@any symlink or similar. Thoughts on that?

At the risk of speaking for @rkitover (please correct me if I'm mistaken!), I think they are primarily interesting in this in order to be able to use a versioned llvm@* formula inside the llvm_clang shim.
Even if we do what's proposed here, I don't think we'll be changing the llvm_clang shim to allow for any installed llvm, so the interest in this change may be moot.

Yes that was what I was thinking, but we should be able to do what we're discussing in #13780 without this, however that turns out.
This would slightly simplify my PATH handling, and I could see some small benefit for others, e.g. people use versioned postgres formulae.
I like the idea of opt/formula@any as well.

Actually now that I think about it more, /usr/local/opt/<formula>@any would make the /usr/local/opt directory listing very spammy and ugly, so perhaps /usr/local/var/alternatives/formula would be better after all, or another directory of your choice.
Another question that is unrelated, how hard would it be for a third party like me to host bottles for an OS for which you do not provide bottles. If I were to, for example, set up a build server and web directory for bottles on my server, would that be possible? And if not, is that something you would consider supporting?
According to this High Sierra is not a completely dead OS, with 4.3% market-share. So I would consider doing something that like that if it were possible. High Sierra also has some interesting properties, like being the last macOS to allow using some powerful NVIDIA GPUs.
I would of course not expect any association, endorsement or even reference from your project if I were to do this. It would be a completely separate thing, I am just asking if you would consider allowing hooks for this, and I will do the necessary work.

That's possible. See:
https://docs.brew.sh/Taps
https://docs.brew.sh/Interesting-Taps-and-Forks
https://github.com/gromgit/homebrew-core-mojave
https://github.com/shivammathur/homebrew-php

Actually now that I think about it more, /usr/local/opt/<formula>@any would make the /usr/local/opt directory listing very spammy and ugly

My suggestion would be we only do this for formula with at least one versioned formula which should make it less so.

My suggestion would be we only do this for formula with at least one versioned formula which should make it less so.

Yeah, that sounds good, thanks.

@carlocab I just noticed that nix has llvm and clang 14 for 10.13, I will look at how to adapt their patches to the formula.

MacPorts does as well. I think they're able to build LLVM for up to 10.10, but that relies on MacPorts-specific patches (they ship a special libSystem wrapper).
We can backport patches for the versioned LLVM formulae, but we should try to upstream fixes because we don't want to carry them indefinitely against the latest LLVM.

We can backport patches for the versioned LLVM formulae, but we should try to upstream fixes because we don't want to carry them indefinitely against the latest LLVM.

I agree 100%.
I think for me to make any headway on this I need to start looking at how the existing patches were done, and in the process patch llvm@14, and then try to come up with a more general patch I can submit to the LLVM project using whatever workflow they are using.
Then we'd need to do the same for llvm@15, which is probably happening soon given the rcs.
By the way, no response or any comments on https://github.com/llvm/llvm-project/issues/57553 so far.


Support for composite indexes

This pull-request adds support for composite indexes. It uses document.Array to wrap the multiple values into one for the index stores. The changes are not that large as the line changes count suggests, this is mainly due to having added a lot of table tests on the indexes.
I have also rewritten the tests for the index iteration methods, which are now quite exhaustive.
The Benchmarks are here and are quite good (0% change on simple indexes).

Codecov Report

Merging #376 (d65c079) into main (7853532) will increase coverage by 0.20%.
The diff coverage is 78.34%.

@@            Coverage Diff             @@
##             main     #376      +/-   ##
==========================================
+ Coverage   67.97%   68.18%   +0.20%
==========================================
  Files          73       73
  Lines        7332     7499     +167
==========================================
+ Hits         4984     5113     +129
- Misses       1679     1700      +21
- Partials      669      686      +17

Impacted Files
Coverage Δ

document/document.go
65.67% <0.00%> (-0.75%)
:arrow_down:

query/create.go
60.00% <50.00%> (ø)

database/index.go
71.05% <75.60%> (+3.11%)
:arrow_up:

stream/iterator.go
64.76% <81.33%> (+3.28%)
:arrow_up:

database/config.go
67.66% <83.33%> (+0.73%)
:arrow_up:

database/table.go
50.50% <83.33%> (+0.50%)
:arrow_up:

database/catalog.go
81.90% <100.00%> (+0.05%)
:arrow_up:

planner/optimizer.go
77.02% <100.00%> (ø)

sql/parser/create.go
72.03% <100.00%> (-0.47%)
:arrow_down:

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 7853532...d65c079. Read the comment docs.

Codecov Report

Merging #376 (378a3ba) into main (e19ca7a) will decrease coverage by 0.50%.
 Consider uploading reports for the commit 1c21c42 to get more accurate results

@@            Coverage Diff             @@
##             main     #376      +/-   ##
==========================================
- Coverage   68.53%   68.03%   -0.51%
==========================================
  Files          74       75       +1
  Lines        7479     7805     +326
==========================================
+ Hits         5126     5310     +184
- Misses       1678     1795     +117
- Partials      675      700      +25

Impacted Files
Coverage Δ

document/array.go
60.86% <0.00%> (-6.72%)
:arrow_down:

document/document.go
65.18% <0.00%> (-0.74%)
:arrow_down:

document/value.go
73.23% <0.00%> (ø)

expr/comparison.go
70.32% <0.00%> (-3.24%)
:arrow_down:

stream/range.go
34.04% <34.04%> (ø)

database/table.go
51.72% <55.00%> (+0.46%)
:arrow_up:

database/index.go
65.21% <65.11%> (-4.87%)
:arrow_down:

planner/optimizer.go
77.77% <82.82%> (+0.80%)
:arrow_up:

database/config.go
66.95% <83.33%> (+1.38%)
:arrow_up:

database/catalog.go
81.38% <86.66%> (+0.29%)
:arrow_up:

... and 9 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 e19ca7a...1c21c42. Read the comment docs.


[SUGGESTION] Config to allow other modded birds to perch on shoulders

Why stop at parrots? Quite a few mods add their own birds.

I'd have to take a look at how those specific mods implement their birds. Can you send examples?

 Better Animals Plus


how to add cancan authorize_resource to monologue?

http://localhost:3000/blog
This action failed the check_authorization because it does not authorize_resource. Add skip_authorization_check to bypass this check.
Started GET "/blog" for <IP_ADDRESS> at 2014-09-28 16:00:23 +0530
Started GET "/blog" for <IP_ADDRESS> at 2014-09-28 16:00:23 +0530
Processing by Monologue::PostsController#index as HTML
Processing by Monologue::PostsController#index as HTML
  User Load (1.0ms)  SELECT  "users".* FROM "users"  WHERE "users"."id" = 1  ORDER BY "users"."id" ASC LIMIT 1
  User Load (1.0ms)  SELECT  "users".* FROM "users"  WHERE "users"."id" = 1  ORDER BY "users"."id" ASC LIMIT 1
  Monologue::Tag Load (1.1ms)  SELECT "monologue_tags".* FROM "monologue_tags"   ORDER BY name
  Monologue::Tag Load (1.1ms)  SELECT "monologue_tags".*  FROM "monologue_posts"  WHERE "monologue_posts"."published" = 't' AND (published_at <= '2014-09-28 10:30:23.388196')  ORDER BY published_at DESC, monologue_posts.created_at DESC, monologue_posts.updated_at DESC LIMIT 100
  Monologue::Post Load (1.7ms)  SELECT  "monologue_posts".* FROM "monologue_posts"  WHERE "monologue_posts"."published" = 't' AND (published_at <= '2014-09-28 10:30:23.388196')  ORDER BY published_at DESC, monologue_posts.created_at DESC, monologue_posts.updated_at DESC LIMIT 100
  Monologue::Tagging Load (1.1ms)  SELECT "monologue_taggings".* FROM "monologue_taggings"  WHERE "monologue_taggings"."post_id" IN (1)
  Monologue::Tagging Load (1.1ms)  SELECT "monologue_taggings".* FROM "monologue_taggings"  WHERE "monologue_taggings"."post_id" IN (1)
  Monologue::Tag Load (0.8ms)  SELECT "monologue_tags".* FROM "monologue_tags"  WHERE "monologue_tags"."id" IN (1, 2)  ORDER BY id ASC
  Monologue::Tag Load (0.8ms)  SELECT "monologue_tags".*  FROM "monologue_posts"  WHERE "monologue_posts"."published" = 't' AND (published_at <= '2014-09-28 10:30:23.408231')  ORDER BY published_at DESC, monologue_posts.created_at DESC, monologue_posts.updated_at DESC LIMIT 10 OFFSET 0
  Monologue::Post Load (1.4ms)  SELECT  "monologue_posts".* FROM "monologue_posts"  WHERE "monologue_posts"."published" = 't' AND (published_at <= '2014-09-28 10:30:23.408231')  ORDER BY published_at DESC, monologue_posts.created_at DESC, monologue_posts.updated_at DESC LIMIT 10 OFFSET 0
  CACHE (0.1ms)  SELECT "monologue_taggings".* FROM "monologue_taggings"  WHERE "monologue_taggings"."post_id" IN (1)
  CACHE (0.1ms)  SELECT "monologue_taggings".* FROM "monologue_taggings"  WHERE "monologue_taggings"."post_id" IN (1)
  CACHE (0.0ms)  SELECT "monologue_tags".* FROM "monologue_tags"  WHERE "monologue_tags"."id" IN (1, 2)  ORDER BY id ASC
  CACHE (0.0ms)  SELECT "monologue_tags".* FROM "monologue_tags"  WHERE "monologue_tags"."id" IN (1, 2)  ORDER BY id ASC
  Monologue::User Load (1.0ms)  SELECT  "monologue_users".* FROM "monologue_users"  WHERE "monologue_users"."id" = $1 LIMIT 1  [["id", 1]]
  Monologue::User Load (1.0ms)  SELECT  "monologue_users".*  FROM "monologue_posts"  WHERE "monologue_posts"."published" = 't' AND (published_at <= '2014-09-28 10:30:23.339328')  ORDER BY published_at DESC, monologue_posts.created_at DESC, monologue_posts.updated_at DESC LIMIT 3
  Monologue::Post Load (0.7ms)  SELECT  "monologue_posts".* FROM "monologue_posts"  WHERE "monologue_posts"."published" = 't' AND (published_at <= '2014-09-28 10:30:23.339328')  ORDER BY published_at DESC, monologue_posts.created_at DESC, monologue_posts.updated_at DESC LIMIT 3
  CACHE (0.1ms)  SELECT "monologue_taggings".* FROM "monologue_taggings"  WHERE "monologue_taggings"."post_id" IN (1)
  CACHE (0.1ms)  SELECT "monologue_taggings".* FROM "monologue_taggings"  WHERE "monologue_taggings"."post_id" IN (1)
  CACHE (0.3ms)  SELECT "monologue_tags".* FROM "monologue_tags"  WHERE "monologue_tags"."id" IN (1, 2)  ORDER BY id ASC
  CACHE (0.3ms)  SELECT "monologue_tags".* FROM "monologue_tags"  WHERE "monologue_tags"."id" IN (1, 2)  ORDER BY id ASC
  Rendered<EMAIL_ADDRESS>(8.8ms)
  Rendered<EMAIL_ADDRESS>(8.8ms)
  Rendered<EMAIL_ADDRESS>(0.7ms)
  Rendered<EMAIL_ADDRESS>(0.7ms)
   (0.4ms)  SELECT COUNT(*) FROM "monologue_posts" INNER JOIN "monologue_taggings" ON "monologue_posts"."id" = "monologue_taggings"."post_id" WHERE "monologue_taggings"."tag_id" = $1 AND "monologue_posts"."published" = 't' AND (published_at <= '2014-09-28 10:30:23.657335')  [["tag_id", 2]]
   (0.4ms)  SELECT COUNT(*) FROM "monologue_posts" INNER JOIN "monologue_taggings" ON "monologue_posts"."id" = "monologue_taggings"."post_id" WHERE "monologue_taggings"."tag_id" = $1 AND "monologue_posts"."published" = 't' AND (published_at <= '2014-09-28 10:30:23.657335')  [["tag_id", 2]]
   (0.3ms)  SELECT COUNT(*) FROM "monologue_posts" INNER JOIN "monologue_taggings" ON "monologue_posts"."id" = "monologue_taggings"."post_id" WHERE "monologue_taggings"."tag_id" = $1 AND "monologue_posts"."published" = 't' AND (published_at <= '2014-09-28 10:30:23.660854')  [["tag_id", 1]]
   (0.3ms)  SELECT COUNT(*) FROM "monologue_posts" INNER JOIN "monologue_taggings" ON "monologue_posts"."id" = "monologue_taggings"."post_id" WHERE "monologue_taggings"."tag_id" = $1 AND "monologue_posts"."published" = 't' AND (published_at <= '2014-09-28 10:30:23.660854')  [["tag_id", 1]]
  Rendered<EMAIL_ADDRESS>(7.6ms)
  Rendered<EMAIL_ADDRESS>(7.6ms)
  Rendered<EMAIL_ADDRESS>(20.9ms)
  Rendered<EMAIL_ADDRESS>(20.9ms)
  Rendered<EMAIL_ADDRESS>(0.3ms)
  Rendered<EMAIL_ADDRESS>(0.3ms)
  Rendered<EMAIL_ADDRESS>(0.2ms)
  Rendered<EMAIL_ADDRESS>(0.2ms)
Redirected to http://localhost:3000/home
Redirected to http://localhost:3000/home
Completed 302 Found in 336ms (Views: 254.1ms | ActiveRecord: 15.2ms)
Completed 302 Found in 336ms (Views: 254.1ms | ActiveRecord: 15.2ms)

Okay, this issue was opened and closed a year ago. Still, my workaround might be useful.
In application_controller.rb:
check_authorization :unless => :authorization_not_needed?

  def authorization_not_needed?
  	monologue_controller? || devise_controller?
  end

  def monologue_controller?
	request[:controller].start_with?("monologue")
  end

It's not very elegant, but it works.


Precious-Pelicans

Submission for 2020 summer code jam

This PR removes the .gitignore in the root of the repository; this needs to be reverted before we can merge this PR. There also seems to be a secondary PR for this team which probably should have been merged into the fork instead (see #87).
No flake8 linting errors.


Incompatibility 'com.android.support:appcompat-v7:28.0.0' and 'com.google.firebase:firebase-core:17.0.1'

Hi there,
I have a problem within my app/build.gradle, when insering the lines recommended by Firebase:
implement 'com.google.firebase:firebase-core:17.0.1'
after implementing I synced the gradles files, it then states, that line
implementation 'com.android.support:appcompat-v7:28.0.0' (in app/build.gradle, under dependencies) is wrong and following error message appears:
--> Dependencies using groupId com.android.support and androidx.* can not be combined but found IdeMavenCoordinates{myGroupId='com.android.support', myArtifactId='loader', myVersion='28.0.0', myPacking='aar', myClassifier='null'} and IdeMavenCoordinates{myGroupId='androidx.legacy', myArtifactId='legacy-support-core-utils', myVersion='1.0.0', myPacking='aar', myClassifier='null'} incompatible dependencies less... (Strg+F1)
Inspection info:There are some combinations of libraries, or tools and libraries, that are incompatible, or can lead to bugs. One such incompatibility is compiling with a version of the Android support libraries that is not the latest version (or in particular, a version lower than your targetSdkVersion).  Issue id: GradleCompatible
Does anybody have a clue what I'm doing wrong?
compileSDKVersion and targetSDKVersion both 28

@Itseme1234 Hey,
Sorry, but this does not look like it's AsyncStorage related.
But this error is likely due to mixing support libs and androidx


Test: delay JMS server shutdown in JMS_TESTS.jmx

See Race condition in JMS_TESTS.xml discussion

Merged in https://github.com/apache/jmeter/commit/a7ba7d40c0681c0c657e4e15a37967dab06b6ba8


Unit tests for backend functions

Unit tests are too hard to maintain in a research setting... I prefer status pages and integration tests.


[Bug]: Warning raised when query to Persistent Client

What happened?
I just use collection.query at my PersistentClient collection, and the a lot of logger warnings raised.
The ingested id all shows up as warnings.
It happens at chromadb/segment/impl/vector/local_persistent_hnsw.py
logger.warning(f"Add of existing embedding ID: {id}")

I can't figure out why all ids already existed access. And I don't know why it occur warning log, yet it is not add code.
It works perfectly, but logging is so verbose and confused that it try to add whole ids at collection all again. Even I didn't put any corpus to collection, just load and query it.
Versions
chroma-hnswlib==0.7.3
chromadb==0.4.22
It happens linux(ubuntu) and mac both. Python 3.10
Relevant log output
No response

Hi @vkehfdl1 - could you provide more context? It seems like you are attempting to .add entries with the same id again, could you please share the code where you're ingesting data?

My code looks like this.
def vectordb_pure(query: str, top_k: int, collection: chromadb.Collection,
                        embedding_model: BaseEmbedding):
    embedded_queries = list(map(embedding_model.get_query_embedding, queries))
    id_result = []
    for embedded_query in embedded_queries:
        result = collection.query(query_embeddings=embedded_query, n_results=top_k)
        id_result.extend(result[‘ids’])
    return id_result

def main():
    db = chromadb.PersistentClient(path=db_path)
    collection = db.get_collection(name=collection_name)
    embedding_model = OpenAIEmbedding() # LlamaIndex Embedding
    top_k = 5
    tasks = [vectordb_pure(input_queries, top_k, collection, embedding_model) for input_queries in queries]
    loop = asyncio.get_event_loop()
    results = loop.run_until_complete(process_batch(tasks, batch_size=batch))

If I execute this kind of code, it occurs a lot warning that I add a existing id, like I mentioned.
I didn’t even try to add id to ChromaDB, just try to query...

What does process_batch do? It looks like it might add embeddings - since you are using a persistent client, the collection will have been loaded when you do get_collection - is it possible this collection already contains records with ids you loaded before?

Here is process_batch It's just run the given task in for loop. So, it did not add any embeddings.
def process_batch(tasks, batch_size: int = 64) -> List[Any]:
    results = []
    for i in range(0, len(tasks), batch_size):
        batch = tasks[i:i + batch_size]
        batch_results = await asyncio.gather(*batch)
        results.extend(batch_results)

    return results

Of course collection contain ids, but I don't add any embeddings at any code.
When I delete the warning line, it works fine. (Its feature is nothing wrong, just raise warning)
Maybe @tazarov fix this issue at #1763.
Hope to merge it quickly.
Thx:)

Same problem upon searching

@vkehfdl1, @joaomdmoura, we've found the root cause for this and working on a fix


Create developer guide

We want to make it easier for people to contribute new models to the codebase
For this, we can explain how to change the data loading, the model, the posterior etc.. This must be done after posterior refactoring

Basically done, will be done after @galenxing finishes his.


Crashed upon trying to build big reactor

pastebin http://pastebin.com/UvcXv4yN
version: latest
it said i needed more then one controllers for the big reactor then I right clicked and it crashed. could you please fix this. it says no class found powercrystals api

Remove the red net reactor port, you do not have the necessary mod to use it.


http3: Close client at errors

What problem does this solve?

Under load, we encountered an error that the client cannot allocate a new UDP port: listen udp <IP_ADDRESS>:0: bind: address already in use
# sudo lsof -p 512346 | grep UDP | wc -l
57142

Host always the same.
Not fully sure that this is the real place where the problem happen, but this maybe one of the reasons.

I don't think that's related. The HTTP/3 client doesn't keep the UDP connection open.
That being said, I think we can optimize things here. In principle, you only need a single UDP socket for all of your QUIC connections. That's because QUIC can demultiplex based on the QUIC Connection ID.
In quic-go, this is achieved by not using quic.DialAddr (which will create and manage a net.UDPConn for you), but using quic.Dial, which takes a net.UDPConn as an argument. In the HTTP/3 package, we could create a single UDPConn per RoundTripper, and use that for all outgoing requests.


Pass over "context information" to Tasks

To be able to add some context-related information (e.g. Workload Name, Version, App Name, ...) in the Functions executed in Keptn, they should get passed over when a function is executed.
As a proposal, this could be done as a JSON object (following the cloud event specification) in an environment variable.

Closed with https://github.com/keptn/lifecycle-controller/pull/170


[FEATURE] Implement users

Describe the solution you'd like
It would be nice to include users in the site.

There is a logout button dash core component. This should be used when users are implemented.

Adding user login/signup functionality to the app:
Description: The users would be able to:
- log in or sign up for our app.
Their login credential will be securely stored in the backend database.
Only the authenticated users would be allowed to enter the site,
- upload the csv data and
- visualize it.
Later, we can extend this functionality by letting the users save their plots and csv data.
- no sign-in is required. (they can't save the data on the server.)


[improvement](build index)Optimize failed task check on same tablet

Proposed changes

Remove logic for replica majority failure checking
Introduce TRY_LOCK_FAILED status code both in status.h and Status.thrift
Add MIN_FAILED_NUM = 3 for non try_lock_failed failure task. The task will try 3 times before canceling the job.
Add MAX_FAILED_NUM = 10 for try_lock_failed failure task.


Create circuits textures of the new (latest) tier

Missing textures 4 circuits added on the new tier
97
98
99
120

97 bbe6d9f5b192a5df1e844c7fe58823989bce7197


Pub Sub Data Source Unit Tests

Unit tests for the PubSubDataSource.
This PR also has a base class that does most of the difficult work of mocking an apiary service.

Codecov Report

Merging #684 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master    #684      +/-   ##
=========================================
- Coverage    2.96%   2.96%   -0.01%
=========================================
  Files         370     370
  Lines       13849   13850       +1
=========================================
  Hits          411     411
- Misses      13438   13439       +1

Impacted Files
Coverage Δ

...ogleCloudExtension.DataSources/PubSubDataSource.cs
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

PTAL


The 'sqlglot<24,>=23.0.2' distribution was not found and is required by apache-superset

Bug description
This error occurred while upgrading the superset image from version 3.0.1 to version 4.0.2 how to fix this
Screenshots/recordings

Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
This error occurred while upgrading the superset image from version 3.0.1 to version 4.0.2 how to fix this
Checklist

[X] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

I couldn't find a specific solution for the 'sqlglot' dependency issue in the context of upgrading from Superset version 3.0.1 to 4.0.2. However, I can suggest a general approach to resolve this kind of dependency issue:

Check Dependency Versions: Ensure that the version of 'sqlglot' specified in your environment matches the requirements for Superset 4.0.2. According to the dependencies for version 4.0.2, 'sqlglot' should be >=25.24.0,<26 [1].
Update Dependencies: You can manually update the 'sqlglot' package to the required version using pip:pip install 'sqlglot>=25.24.0,<26'

Rebuild Docker Image: If you are using Docker, make sure to rebuild your Docker image after updating the dependencies:docker compose down
docker compose up --build

Verify Installation: After updating, verify that the correct version of 'sqlglot' is installed by checking the installed packages:pip show sqlglot

These steps should help resolve the dependency issue you're encountering. If the problem persists, double-check the pyproject.toml or requirements files for any conflicting version specifications.
To continue talking to Dosu, mention @dosu.

RUN apt-get update
&& apt-get install -y --no-install-recommends
libnss3
libdbus-glib-1-2
libgtk-3-0
libx11-xcb1
libasound2
libxtst6
wget tar
libldap2-dev
pkg-config
build-essential
curl
default-libmysqlclient-dev
libsasl2-dev
libsasl2-modules-gssapi-mit
libpq-dev
libecpg-dev
libldap2-dev
&& pip install --upgrade "sqlglot>=23.0.2,<24"
&& touch superset/static/version_info.json
&& chown -R superset:superset ./*
&& rm -rf /var/lib/apt/lists/*
I added it as below and it didn't work

@michael-s-molina


Error thrown when trying to add entity with Boolean or Int32 property

Which service (blob, file, queue, table) does this issue concern?
Table
Which version of the Azurite was used?
3.14.3
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
npm
What's the Node.js version?
16.13.1
What problem was encountered?
Azurite returns an error when attempting to add an entity with a Boolean or Int32 property.
Steps to reproduce the issue?

Form the following entity object in a Node application:{
   partitionKey: "",
   rowKey: "",
   prop: { value: "false", type: "Boolean" }
}

Use @azure/data-tables to connect to the emulator and insert the entity.

Here are the relevant lines from the debug log:
2022-01-04T00:49:30.226Z 2a92d550-f0d2-48aa-b819-f2c8a8d99a47 verbose: DeserializerMiddleware: Start deserializing...
2022-01-04T00:49:30.227Z 2a92d550-f0d2-48aa-b819-f2c8a8d99a47 debug: deserialize(): Raw request body string is (removed all empty characters) {"PartitionKey":"1","RowKey":"2","bin":"false","bin@odata.type":"Edm.Boolean"}
2022-01-04T00:49:30.227Z 2a92d550-f0d2-48aa-b819-f2c8a8d99a47 info: HandlerMiddleware: DeserializedParameters={"options":{"queryOptions":{},"requestId":"73776de8-b219-4a28-870a-151d5a8a1072","dataServiceVersion":"3.0","responsePreference":"return-no-content","tableEntityProperties":{"PartitionKey":"1","RowKey":"2","prop":"false","bin@odata.type":"Edm.Boolean"}},"version":"2019-02-02","body":"ReadableStream"}
2022-01-04T00:49:30.227Z 2a92d550-f0d2-48aa-b819-f2c8a8d99a47 error: TableHandler:insertEntity() TypeError "TypeError: Not a valid EdmBoolean string.\n    at Function.validate (C:\\Users\\cralvord\\AppData\\Roaming\\npm\\node_modules\\azurite\\dist\\src\\table\\entity\\EdmBoolean.js:11:19)\n    at new EdmBoolean (C:\\Users\\cralvord\\AppData\\Roaming\\npm\\node_modules\\azurite\\dist\\src\\table\\entity\\EdmBoolean.js:7:38)\n    at Object.parseEntityProperty (C:\\Users\\cralvord\\AppData\\Roaming\\npm\\node_modules\\azurite\\dist\\src\\table\\entity\\EntityProperty.js:92:56)\n    at new NormalizedEntity (C:\\Users\\cralvord\\AppData\\Roaming\\npm\\node_modules\\azurite\\dist\\src\\table\\entity\\NormalizedEntity.js:41:55)\n    at TableHandler.insertEntity (C:\\Users\\cralvord\\AppData\\Roaming\\npm\\node_modules\\azurite\\dist\\src\\table\\handlers\\TableHandler.js:116:32)\n    at C:\\Users\\cralvord\\AppData\\Roaming\\npm\\node_modules\\azurite\\dist\\src\\table\\generated\\middleware\\HandlerMiddlewareFactory.js:58:18\n    at C:\\Users\\cralvord\\AppData\\Roaming\\npm\\node_modules\\azurite\\dist\\src\\table\\generated\\ExpressMiddlewareFactory.js:77:63\n    at Layer.handle [as handle_request] (C:\\Users\\cralvord\\AppData\\Roaming\\npm\\node_modules\\azurite\\node_modules\\express\\lib\\router\\layer.js:95:5)\n    at trim_prefix (C:\\Users\\cralvord\\AppData\\Roaming\\npm\\node_modules\\azurite\\node_modules\\express\\lib\\router\\index.js:317:13)\n    at C:\\Users\\cralvord\\AppData\\Roaming\\npm\\node_modules\\azurite\\node_modules\\express\\lib\\router\\index.js:284:7"

Have you found a mitigation/solution?
No. It should be noted that the same step taken against Azure are successful.

@edwin-huber @blueww Haven't heard back from anyone about this. Is this getting looked into? Several Storage Explorer users have been reporting on this problem. We use string values with data types to avoid type ambiguity and precision loss for certain types.

Hi @craxal thanks for the heads up.
I shall take a look.
We have a few issues pending the large PR #1157, as this has the potential to generate a lot of conflicts.
I'm trying to roll up as many smaller fixes as I can into that, as it is one of the major pieces of work before we consider that we are truly GA on Table.

Issue is fixed in pending PR #1259

@edwin-huber I think you linked back to this issue, not the PR...

Changes merged, pending next release.

any news about this issue? Is there a workaround that can be applied?


issue#111 Create PlantItemViewModel for using it as binding on every plant list item instead of plant and its click listener

The changes of this branch are about creating a view model for wrapping a plant and its click listener and use it as binding instead of having both the plant item and the click listener as bindings. Moreover, this changes let us to take out the logic of click action from adapter and use it only for delegating the user actions to collaborators (in this case the view model)

Softagram Impact Report for pull/2 (head commit: 4bc032adfa17)
:star: Change Overview

(Open in Softagram Desktop for full details)

:page_facing_up: Full report

Permalink: Full report for pull/2

Impact Report explained. Give feedback on this report to<EMAIL_ADDRESS>


Changelog for 1.21 missing CI approval notice

Description
When upgrading from 1.20.5 to 1.21.2 the CI pipeline status checks were ignored in PRs.
I checked the release notes before updating the instance here, however nothing mentioned this change.
After investigating the database i found out, that when a repo had status checks enabled but no custom pattern was supplied it skipped the check.
When i updated the field status_check_contexts to [*] status checks worked again.
Query used to find "broken" branch status check entries:
select
    protected_branch.status_check_contexts,
    repository.id
from repository
     join protected_branch
       on protected_branch.repo_id = repository.id
where protected_branch.enable_status_check
      and ( protected_branch.status_check_contexts is null
            or protected_branch.status_check_contexts = 'null' )

Gitea Version
1.21.2
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
2.20.1
Operating System
Debian
How are you running Gitea?
Docker Compose
Image: gitea/gitea:1.21
Database
PostgreSQL

Behaviour has changed as a result of this PR: Support for status check pattern (#24633)

The feature introduced in #24633 should be compatible with status_check_contexts. However, if one or more of status_check_contexts is not a legal glob expressions, glob.Compile will fail and the contexts cannot match.
https://github.com/go-gitea/gitea/blob/21229ed2c8ed00f57100adf9ebc5f4a08da9a66e/routers/web/repo/pull.go#L653-L663
I'll try to make a PR to fix it


node server crash caused by unprotected console.log in app.js

In src/app.js multiple console.log are logging variables which might not be available.
This causes node to crash.
e.g:
 socket.on('getProducers', () => {
        console.log(---get producers--- name:${roomList.get(socket.room_id).getPeers().get(socket.id).name})
        // send all the current producer to newly joined member
        if (!roomList.has(socket.room_id)) return
        let producerList = roomList.get(socket.room_id).getProducerListForPeer(socket.id)
        socket.emit('newProducers', producerList)
    })

 if (!roomList.has(socket.room_id)) getPeers fails and the server crashes.
By putting all the console.log into a  try/catch section or after the check avoids that.
socket.on('getProducers', () => {
         // send all the current producer to newly joined member
        if (!roomList.has(socket.room_id)) return ;
        console.log(---get producers--- name:${roomList.get(socket.room_id).getPeers().get(socket.id).name});
        let producerList = roomList.get(socket.room_id).getProducerListForPeer(socket.id);
        socket.emit('newProducers', producerList);
    })

I had the problem with node crashing because of one of the console.log
don't know why exactly it occurred.
Just fixed the console.logs and problem didnt appear again.

Fixed in commit  578999e2859c20063fa59c6dbc50292beb0abdf6


Zip push-to-deploy feature

Addition of zip push-to-deploy.

This PR has quite a bit of noise in it, primarily due to the namespaces of a few classes changing. I will send a more focused CodeFlow with notes.

Why use CodeFlow over GitHub PR system?

Better diff and commenting experience, ability to prune unimportant changes out of the review. Is there a way to better tailor a PR on GitHub? Maybe I don't know about it. Feel free to comment within the PR as well, I'll read those too.

Ok, will try to look on CodeFlow.

@nickwalkmsft can you share the basic API doc? i.e. how do I test this?

POST a zip file (curl, Postman etc.) to /push-deploy (this will soon be /api/zipdeploy as per Suwat's comment, but I don't have that in yet).
Add ?isAsync=true to do it in the background; the Location header of result will point to the deployment status.
Behavior and results should be what you'd find with any other deployment.

@nickwalkmsft Instead of piling everything here, I'll open individual issues for anything I find. Starting with #2571.

New changes and Codeflow sent.
FYI, I found out in CodeFlow that you can diff between two revisions by Ctrl-clicking their tabs.

So I'm playing tester on this one and letting @suwatch do the CR :)


No more release notes ?

Have you stopped producing release notes?
The last notes describes 8.0.0

The pull requests have all the commits for that release, I haven't produced release notes in 8.0.0, that's correct.


[WIP] Add CLI option to select custom targets path

Fixes issue #275
Proposed Changes

Add CLI flag to add custom targets path
Expand the path and save it as a reclass object

There is only one problem that I am facing:
kapitan/lib/kapitan.libjsonnet has this
  inventory(target=std.extVar("target"), inv_path="inventory/"):: std.native("inventory")(target, inv_path),

hardcoded. So is there a way to override this when dealing with custom target paths?
@uberspot

@googlebot I signed it!

Besides my comment, the only other thing missing is a small test to check that this flag is actually used. Could you add one under kapitan/tests/test_compile.py ? :)

Yeah sure! I'll add it ASAP. Apologies for the delay.


[MX-127] Hide tool bar when in search nav stack

https://artsyproduct.atlassian.net/browse/MX-127
Now that search is it's own page we had a problem in deciding where tapping a search result takes you in our nav system.
This PR implements the decision to copy the twitter app by keeping all search-related activity in the search page. It accomplishes this by hiding the bottom toolbar nav when viewing search results.
Here's how that looks.

Where I've put this logic feels like the wrong place conceptually but also the simplest place practically. I'm curious if you're concerned about that @ashfurrow or maybe you have a suggestion for where else this could go?

That said, other apps do this, so there's probably a good reason that I'm not seeing. Could you fill me in on the advantages that this interaction gives us/the user?

I think the main advantage over other options is that it leaves it up to the user to be in control of their rabbit hole. Otherwise we have to either clear it on their behalf when they leave the search page, which is not easy to get right, or let it get in their way when they come back.

Okay, that makes sense. Let's try this – I think it'll feel right once I use it on-device. My only other recommendation is to put the logic behind the lab option, similar to here:
https://github.com/artsy/eigen/blob/7716765ee8f0ea5e362cfd29ab8fbaa636f7cc96/Artsy/View_Controllers/App_Navigation/ARTopMenuNavigationDataSource.m#L152

Good suggestions, thanks! 🍏

turns out that twitter only does this on android, not iOS, which leaves me wondering whether it is indeed the best thing or whether it even matters much. 🤷♂

Let's try it out and see! We can highlight this with Sam+the rest of the team to get feedback.


add rel="noopener" to anchor elements for security and performance

Please see:

https://mathiasbynens.github.io/rel-noopener/
https://jakearchibald.com/2016/performance-benefits-of-rel-noopener/

Any interest?
Thanks for jssocials!

Thank for the suggestion.
Could you do a PR?


Argo-cd - Upgrading Helm Chart Loops

We're using argo-cd with the helm chart to deploy the operator. The problem is upgrading from 0.21.2 - > 0.22.2 argo-cd is looping over the CRD resources. It will show synced, but then not synced. Below is the screenshot of a sample of what it sees as out of sync. It's like it will change it, but then something else changes it back? At first I thought it was labels but the fields involved are not labels in the CRD

You should install CRD separatelly, 0.22.2
helm actually have strange policy about CRD resources

Understood, but we have many other operators with custom CRDs we deploy with argo without issue.

Understood, but we have many other operators with custom CRDs we deploy with argo without issue.

if you use olm with argocd you are fine, if you use argocd with helm for operators you will for sure run into issues with crd's at sometime

We are using kustomize helm charts. Which technically doesn't deploy a chart but just outputs the manifests - and it still has issues
---
kind: Kustomization
apiVersion: kustomize.config.k8s.io/v1beta1

helmCharts:
  - name: altinity-clickhouse-operator
    releaseName: clickhouse-operator
    namespace: clark-developer-featbit
    repo: https://docs.altinity.com/clickhouse-operator/
    includeCRDs: true

@tman5 is this not clear what actually do helmCharts with includeCRDs:true in kustomize
looks like nothing useful and you just have non updated CRDs, because this is a HELM architecture problem

So if we were to switch to move away from helm charts and just install the straight manifests, I have a question about our existing clickhouse clusters: if the operator pod goes away while we re-provision, will it also delete the clickhouse clusters with it?

it depends how exactly your kind: ClickHouseInstallation was deployed
if you are use values.yaml which contains additionalResources
then it deleted with on the helm side during uninstall release
in other case it should delete operator deployment wihtout deleting CRDs and ClickHouseInstallations (chi)
better will check it on staging before apply


unable to build

Hi,
I'm unable to build, on a debian 7.5 with Go 1.4.1
go build whisper-to-influxdb.go
# command-line-arguments
./whisper-to-influxdb.go:48: undefined: client.Series
./whisper-to-influxdb.go:121: undefined: client.Series
./whisper-to-influxdb.go:127: undefined: client.Series
./whisper-to-influxdb.go:129: influxClient.WriteSeriesWithTimePrecision undefined (type *client.    Client has no field or method WriteSeriesWithTimePrecision)
./whisper-to-influxdb.go:129: undefined: client.Second
./whisper-to-influxdb.go:304: undefined: client.ClientConfig

Am I missing anything ?

influxdb pushed a bunch of breaking changes to master. you could work around this by going into $GOPATH/src/github.com/influxdb/influxdb and running git checkout 0.8 and retrying the build

somebody should patch this project to use Godep against the best influxdb client version

Hello,
On RedHat 6.6 with go 1.3.3, same problem even after checking out influxdb version 0.8 as indicated. Tried other influxdb versions as well. Unfortunately, I don't know golang. Sad panda is sad...

try 0.8.8

Checked out v0.8.8 of github.com/influxdb/influxdb/client
and have same issue:
go run whisper-to-influxdb.go -all
command-line-arguments
./whisper-to-influxdb.go:48: undefined: client.Series
./whisper-to-influxdb.go:121: undefined: client.Series
./whisper-to-influxdb.go:127: undefined: client.Series
./whisper-to-influxdb.go:129: influxClient.WriteSeriesWithTimePrecision undefined (type *client.Client has no field or method WriteSeriesWithTimePrecision)
./whisper-to-influxdb.go:129: undefined: client.Second
./whisper-to-influxdb.go:308: undefined: client.ClientConfig

Same issue here, tried various branches, no success.
What about fixing the program to work with recent sources ?

I think you'd have to submit a PR - I don't know if @Dieterbe still has access to this repo.

yeah someone should file a PR, then we can fix it.

Is this fixed please?


Cards display browser tooltip on hover with card name

When you hover over a card you see a browser tooltip with the name of the card.

Looks like this is due to "title" being used as a property of px-card... we should maybe rename it to a non-browser-reserved word.
addCard: function (cardName, cardId, title, attributes) {
            if (!cardName || !cardId) {
                throw 'Add card must be called with a card name and card id';
            }
            var newCard = document.createElement(cardName);
            newCard.setAttribute('id', 'card-'+cardId);
            newCard.setAttribute('title', title);
            newCard.setAttribute('context', '{{context}}');

@carlosfhernandez Can you please create a rally story for this?

@lrbridge Great suggestion, we will get this into the next version of px-card

The API for px-card indicates that the property was changed from title to header-text at some point.


Node Voice Region Choosing Different Node then Choosed Node

🚥 Status
Open - If you have any better ideas for this do tell me here or mention and tell me on discord, do tell me if you're interested in resolving it
Issue description
Explanation: After creating a player with createConnection along with the region option/parameter set, Creates an Player on the Node matching that "region", If you try searching with resolve method it will search on other Node and plays on the other Node(previously selected Region Node) That's The main Issue here. It's caused By leastUsedNodes sorting method in Riffy.
My Solution: To add a node parameter riffy resolve method that way the user can parse the player's node while searching.
Another Solution is to modify the leastUsedNodes But it's not that much reliable compared to 1st solution.
Better Solution I have is to have resolve method in the Player Class itself & Have node parameter in Riffy resolve method too.
Steps to Reproduce:

Create a Player with createConnection
Provide the region parameter
Search something with riffy Resolve method
You'll see in the logs it searches on one Node and plays on other Node(It's supposed to search this Node only, As that's the Node filtered by Region and created on it)
Make sure to have regions defined in the NodeOptions.

Code sample
No response
Versions

riffy riffy-team/riffy#fix/user-bugs-feats

Issue priority
Medium (should be fixed soon)

Fixed in release 1.0.5


use the latest log4net

Current coverage is 44.72%

Merging #189 into master will not affect coverage as of d489350

@@            master    #189   diff @@
======================================
  Files           41      41
  Stmts         3931    3931
  Branches       365     365
  Methods          0       0
======================================
  Hit           1758    1758
  Partial        113     113
  Missed        2060    2060

Review entire Coverage Diff as of d489350

Powered by Codecov. Updated on successful CI builds.

LGTM


Removing extra WITHs in rewriters

This PR

Removes ProjectFreshSortExpressions.
Changes normalizeWithClauses such that it does not introduce new WITHs any more.
Removes PragmaWithout.
Fixes a bug in SemanticAnalysis that relied on the rewriting behavior which was removed.

In CfoG we currently rely on projectFreshSortExpressions. If this is merged, we would need to rework projection translation (currently there's a regression of 36 tests in RETURN and WITH acceptance  when running on this branch).

Ok, so I've managed to fix most of the regression when rebased on this branch, except the whole of TriadicSelection. That feature runs queries like this one:
MATCH (n:N)
OPTIONAL MATCH (n)-[r:R]->(m:M)
WITH n WHERE r IS NULL
RETURN n

And it fails in FE with SyntaxException: Variable `r` not defined (with default parsing/lateAstRewriting).

Thanks for the feedback @disolovyov
The failure you see in TriadicSelection is a bug we also see when depending on this branch. I will fix it and then ask you again to run the tests on your side.

@disolovyov I think I should have fixed that bug. If you could rerun your test suite that would be great.

@sherfert Yep, everything works now, thanks!


Center buttons in preference section

Fixes #101
Description
I have centered the buttons in image sections.
Screenshots (if appropriate):

Types of changes

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

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING document.

SWOC Participation

Name: Sanya Saeed
Discord Username: sanya29#3771
[X] I have included the issue number in my PR

What is the issue . please guide...

please check this now, I have removed media queries .

so should I close this pull request ??

Yup you can close this one and make a new request with the html and css files. Also make sure to resolve the merge conflict.


Scrollable Dialog

Feature request
With the current Dialog API the only achievable scrolling behaviour when you have a dialog with longer content is to scroll inside the actual dialog, scrolling on the whole container is not possible.
Overview
Make the Dialog API configurable in some way to allow outer scroll.
Examples in other libraries

Chakra UI has a config for the Dialog if you want the scroll to be inside or outside
Bootstrap

Who does this impact? Who is this for?
I think scrolling in dialogs is quite common so I think it impacts a lot of users of this library.
Additional context
I've tried to implement this outer scroll behaviour with the current API, but the issue is that clicking on the overlay doesn't work because of how the elements are layered, even with pointer-events: none on the content wrapper https://codesandbox.io/s/late-forest-oefp7?file=/App.js

It seems that if we resolved the Portal control issue  then you would be able to achieve what you want with a composition similar to the following:
<Dialog.Root>
  <Dialog.Trigger>Open</Dialog.Trigger>
  <Dialog.Portal>
    <Dialog.Overlay style={{ overflow: 'auto' }}>
      <Dialog.Content />
    </Dialog.Overlay>
  </Dialog.Portal>
</Dialog.Root>

Would this work for you?

Yes, that would be great 🙌

@jjenzz I just tested this out with the release candidate, it almost works but Dialog.Content is wrapped with a scroll remover. Maybe the solution would be to add an enableScroll prop to Dialog.Content?

@jjenzz I just tested this out with the release candidate, it almost works but Dialog.Content is wrapped with a scroll remover. Maybe the solution would be to add an enableScroll prop to Dialog.Content?

I think we should be able to exclude the Overlay part from the remove scroll behaviour.

@clemf we've released a new rc (0.1.2-rc.3) which should fix your issue. Let me know if that works for you.


[Errno 111] Connection refused

I get connection refused when it tries to create a new rich presence object
[nekkles@NekklesOS steam-presence]$ python3 main.py
----------------------------------------------------------
[Jul 17 2024 - 14:28:38] progam's current folder structure version is up to date...
----------------------------------------------------------
[Jul 17 2024 - 14:28:38] loading config file
[Jul 17 2024 - 14:28:38] intializing the SteamGrid database...
[Jul 17 2024 - 14:28:38] everything is ready!
----------------------------------------------------------
[Jul 17 2024 - 14:28:38] found game THE FINALS played by Nekkles
[Jul 17 2024 - 14:28:40] steam app ID 2073850 found for THE FINALS
[Jul 17 2024 - 14:28:41] game changed, updating to 'THE FINALS'
[Jul 17 2024 - 14:28:41] fetching the Discord game ID for THE FINALS
[Jul 17 2024 - 14:28:42] found the discord game ID for the finals
[Jul 17 2024 - 14:28:42] fetching icon for THE FINALS
[Jul 17 2024 - 14:28:42] found icon for THE FINALS in cache
[Jul 17 2024 - 14:28:42] creating new rich presence object for THE FINALS
Traceback (most recent call last):
  File "/home/nekkles/steam-presence/main.py", line 1201, in <module>
    main()
  File "/home/nekkles/steam-presence/main.py", line 1182, in main
    RPC.connect()
  File "/home/nekkles/.local/lib/python3.12/site-packages/pypresence/presence.py", line 43, in connect
    self.loop.run_until_complete(self.handshake())
  File "/usr/lib/python3.12/asyncio/base_events.py", line 687, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/home/nekkles/.local/lib/python3.12/site-packages/pypresence/baseclient.py", line 112, in handshake
    self.sock_reader, self.sock_writer = await asyncio.wait_for(asyncio.open_unix_connection(ipc_path), self.connection_timeout)
                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/asyncio/tasks.py", line 520, in wait_for
    return await fut
           ^^^^^^^^^
  File "/usr/lib/python3.12/asyncio/streams.py", line 97, in open_unix_connection
    transport, _ = await loop.create_unix_connection(
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/asyncio/unix_events.py", line 261, in create_unix_connection
    await self.sock_connect(sock, path)
  File "/usr/lib/python3.12/asyncio/selector_events.py", line 651, in sock_connect
    return await fut
           ^^^^^^^^^
  File "/usr/lib/python3.12/asyncio/selector_events.py", line 659, in _sock_connect
    sock.connect(address)
ConnectionRefusedError: [Errno 111] Connection refused

Same here. Maybe a Python change caused this? Worked for me for several weeks until about a week ago, and I have had Arch distribute a few Python upgrades in that time, I think.
Jul 25 15:27:00 baine python[1887016]:     await self.sock_connect(sock, path)
Jul 25 15:27:00 baine python[1887016]:   File "/usr/lib/python3.12/asyncio/selector_events.py", line 651, in sock_connect
Jul 25 15:27:00 baine python[1887016]:     return await fut
Jul 25 15:27:00 baine python[1887016]:            ^^^^^^^^^
Jul 25 15:27:00 baine python[1887016]:   File "/usr/lib/python3.12/asyncio/selector_events.py", line 659, in _sock_connect
Jul 25 15:27:00 baine python[1887016]:     sock.connect(address)

i believe that your virtual environment breaks when your OS's python version got updated, you should be able to fix it by just deleting it and remaking it
rm -rf venv/
python3 -m venv venv/
./venv/bin/python -m pip install -r requirements.txt

i believe that your virtual environment breaks when your OS's python version got updated, you should be able to fix it by just deleting it and remaking it
rm -rf venv/ python3 -m venv venv/ ./venv/bin/python -m pip install -r requirements.txt

Thanks for the reply! TBH, this didn't work for me initially but I've since restarted my computer and it just... kinda... works now? Not sure. I had also tried to reinstall before your suggestion which I think includes the step you suggested. Not sure what actually changed but I will take it :)

seems fixed


Overriding ops/whitelist prevents the server from starting due to authentication failure

This is probably not a direct issue with this Docker image, but e.g. specifying ops/whitelist by passing variables to the container, seems to cause authentication failures once the server tries to convert the .txt list of players into a .json:
minecraft_1  | [21:47:01 ERROR]: Conversion failed, please try again later
minecraft_1  | net.minecraft.server.v1_16_R3.NameReferencingFileConverter$FileConversionException: Could not request user ... from backend systems
minecraft_1  | 	at net.minecraft.server.v1_16_R3.NameReferencingFileConverter$3.onProfileLookupFailed(NameReferencingFileConverter.java:253) ~[patched_1.16.5.jar:git-Paper-643]
minecraft_1  | 	at com.destroystokyo.paper.profile.PaperGameProfileRepository$PreProfileLookupCallback.onProfileLookupFailed(PaperGameProfileRepository.java:64) ~[patched_1.16.5.jar:git-Paper-643]
minecraft_1  | 	at com.mojang.authlib.yggdrasil.YggdrasilGameProfileRepository.findProfilesByNames(YggdrasilGameProfileRepository.java:89) ~[patched_1.16.5.jar:git-Paper-643]
minecraft_1  | 	at com.destroystokyo.paper.profile.PaperGameProfileRepository.findProfilesByNames(PaperGameProfileRepository.java:44) ~[patched_1.16.5.jar:git-Paper-643]
minecraft_1  | 	at net.minecraft.server.v1_16_R3.NameReferencingFileConverter.a(NameReferencingFileConverter.java:71) ~[patched_1.16.5.jar:git-Paper-643]
minecraft_1  | 	at net.minecraft.server.v1_16_R3.NameReferencingFileConverter.d(NameReferencingFileConverter.java:258) ~[patched_1.16.5.jar:git-Paper-643]
minecraft_1  | 	at net.minecraft.server.v1_16_R3.DedicatedServer.convertNames(DedicatedServer.java:634) ~[patched_1.16.5.jar:git-Paper-643]
minecraft_1  | 	at net.minecraft.server.v1_16_R3.DedicatedServer.init(DedicatedServer.java:202) ~[patched_1.16.5.jar:git-Paper-643]
minecraft_1  | 	at net.minecraft.server.v1_16_R3.MinecraftServer.w(MinecraftServer.java:1065) ~[patched_1.16.5.jar:git-Paper-643]
minecraft_1  | 	at net.minecraft.server.v1_16_R3.MinecraftServer.lambda$a$0(MinecraftServer.java:289) ~[patched_1.16.5.jar:git-Paper-643]
minecraft_1  | 	at java.lang.Thread.run(Unknown Source) [?:?]
minecraft_1  | Caused by: com.mojang.authlib.exceptions.AuthenticationException
minecraft_1  | 	at com.mojang.authlib.yggdrasil.YggdrasilAuthenticationService.makeRequest(YggdrasilAuthenticationService.java:119) ~[patched_1.16.5.jar:git-Paper-643]
minecraft_1  | 	at com.mojang.authlib.yggdrasil.YggdrasilAuthenticationService.makeRequest(YggdrasilAuthenticationService.java:99) ~[patched_1.16.5.jar:git-Paper-643]
minecraft_1  | 	at com.mojang.authlib.yggdrasil.YggdrasilGameProfileRepository.findProfilesByNames(YggdrasilGameProfileRepository.java:56) ~[patched_1.16.5.jar:git-Paper-643]
minecraft_1  | 	... 8 more
minecraft_1  | [21:47:01 WARN]: Encountered a problem while converting the whitelist, retrying in a few seconds

Specifying the .json file directly works as intended, also opping players via the game works, suggesting that the usual authentication servers seem to be available. Perhaps the converter for ops.txt/white-list.txt uses a legacy API that is being phased out?

It's not the container doing that conversion, it's the Minecraft server jar doing it. Please report this issue to Mojang.

Someone reported the bug
https://bugs.mojang.com/projects/WEB/issues/WEB-4457?filter=allopenissues

I have the same issue: any workarounds?

Can I use an older version of the paper-1.16.5.jar file to change this?

@NotErikUden It'a an API issue so we have to wait for Mojang to fix it. For now the only workaround is probably to write an ops.json/white-list.json manually or run the server in offline mode.

It's an issue with their authentication/user lookup endpoint. So, no known workaround unless you have a whitelist.json already populated from before their system broke.

Yes! I didn't have a whitelist to begin with, however, I removed the - OP=Username from my stack and redeployed the server. Everything works now! Thank you very much.

Fixed upstream.


Add installation guides

Feature
Installation Guide
Motivation
Definitely, these kinds of libraries were written by brown-field of RN, so it would be better to add some guides like pod install and manual linking for projects with legacy versions.
Details

Auto-linking
iOS: manual linking
Android: manual linking

@alpha0010, I meant to add pod install, you haven't added this, it's so simple but definitely we should have it in README.md file

Whoops, yes.  That makes sense.  Somehow I missed that when reading your suggestion.


Events table infinite scrolling.

Uses ag-grid's 'infinite' row model type.
Added a switch to display event index (very useful for testing).
Tested on Chrome Version 84.0.4147.135 (Official Build) (64-bit) using sample traces ls-ust and yum.
Signed-off by: Akshay Sharma<EMAIL_ADDRESS>

Screwed up history. New PR time.


add sitemap plugin

I find there is jekyll-seo-tag plugin in Gemfile, maybe jekyll-sitemap is also useful!

Hi, @invisprints 👋  Can you also add this plugin to _config.yml
https://github.com/fastai/fastpages/blob/master/_config.yml#L78
plugins:
  ...
  - jekyll-sitemap

Ok, but I think it maybe an option plugin

Thanks!


ImportError: No module named views

I'm unable to use the application, because of import error:
File ".../virtualenv/local/lib/python2.7/site-packages/wagtailpolls/urls.py", line 4, in <module>
    from .views import chooser, editor, results, vote
ImportError: No module named views

The views module is not in the distribution at all, despite of it inclusion in the urls...

This was fixed earlier, but the newest release didn't include the fix! I've now released 0.1.4 which includes the fix. :)


Question about setting color in other views

Hello, thanks for the amazing project :)
However I've found that some of the views aren't quite fit into the FlatLaf's dark theme.
For example the function view:

Defined string view:

Script manager:

kind of hard to read the words in those views.  Anyway we could fix this ?
Also I would like to know if there's a way to change the font color in python interpreter / console ?  For now the font color is black and I would like to change that:

PCode is hard to read as well

Thanks for the interest in the project! I have also noticed various places where the colors could be a bit better. Unfortunately, these colors are not available as configuration options and with at least the variables I checked in the source code, they are private, hard-coded values. Because of this, not even a plugin would be enough to fix them. I'm fairly certain that the only option here is to recompile Ghidra and take out/replace the hard coded values.
If it is of interest, I could possibly look into this and even provide a patched release if I can get it looking right. It would definitely be a little bit a time/work/research before I could get to that though.

Thanks for the interest in the project! I have also noticed various places where the colors could be a bit better. Unfortunately, these colors are not available as configuration options and with at least the variables I checked in the source code, they are private, hard-coded values. Because of this, not even a plugin would be enough to fix them. I'm fairly certain that the only option here is to recompile Ghidra and take out/replace the hard coded values.

I figured.

If it is of interest, I could possibly look into this and even provide a patched release if I can get it looking right. It would definitely be a little bit a time/work/research before I could get to that though.

No need! We should report these bugs to upstream.

Here are some relevant upstream issues:

https://github.com/NationalSecurityAgency/ghidra/issues/1785
https://github.com/NationalSecurityAgency/ghidra/issues/632#issuecomment-496629318

It looks like an official dark theme is on the road map, but not sure how long it would take.
Here is the hardcoded PCode field coloring:

https://github.com/NationalSecurityAgency/ghidra/blob/27fb507b1877b13504baa75bc90da5f1db5f6ede/Ghidra/Features/Base/src/main/java/ghidra/app/util/pcode/PcodeFormatter.java#L102-L113

Here is a patch that fixes some of the panel's fg/bg coloring: https://github.com/pabx06/buildghidra/blob/8c75127ec14aaf9dadc963d9dfa8cc99ae24fff1/patch/InfoPanel.patch#L27

An alternative approach (when it's available) is to use a pixel shader to invert the colors (optionally preserving hue).
There is some documentation on how to do it here:
https://github.com/vn971/linux-color-inversion
This avoids the issue with bright colors in other views, as well as issues with the FlatLaf skin (such as that scrolling while dragging doesn't work). It also allows color-keyed transparency.
How it looks for me right now (usable, though much room for improvement):


Add odometer value to charging sessions

Is your feature request related to a problem? Please describe.
Unfortunately the value of the odometer in the charging session overview is missing.

For some people this is necessary to create receipts, when charging at home for the company.
Describe the solution you'd like
It would be great to to add the current value of the odometer, when a charging session has beend started or completed (should be the same value).
Describe alternatives you've considered
At the moment it is necessary to take a picture or write down the value of the odometer. As alternative you could use a script, which greps the information from the respective API.
Additional context
As the value is already been provided by the API (sudo evcc -l debug vehicle), e.g. Audi, it should be a low hanging fruit to add this to each charging session.

Odometer value is listed with in csv-file and it is listed in the session details.


Updating retention time as per CELA guidelines

@chrisda or @MSFTTracyP could you please approve this for me?

Learn Build status updates of commit da3c22e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/security/office-365-security/report-junk-email-messages-to-microsoft.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit dfa7f95:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/security/office-365-security/report-junk-email-messages-to-microsoft.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit babff98:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/security/office-365-security/report-junk-email-messages-to-microsoft.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


fix: suspected posts

unhide suspected posts for moderation in the posts page

Resolves #2159
What does this pull request aim to achieve? 💯
Please be concise and link any related issue(s):

[x] I have checked that no one else is working on similar changes.
[x] I have read the latest README and understand the development workflow.
[x] The name of this branch is: feature/<branch_name>, or hotfix/<branch_name> if this is a hotfix, where <branch_name> briefly describes the issue(s) resolved and is prefixed with the issue number(s) (e.g. 1127-1130-update-git-branching-model). The branch is created in a cloned version of this repo, not a forked repo.
[x] This branch is rebased/merged with the latest staging (or the latest production if it is a hotfix).
[x] There are no merge conflicts.
[x] There are no console warnings and errors.
[x] On the right hand side of this PR, I have linked the appropriate issue(s) under "Issues" and added a project progress under "Projects".
[x] The title describes the issue(s) being addressed using format: <issue_numbers> - <brief_issue_description> (e.g. #1127/#1130 - Update Git Branching Model)

@rabbi08  Can you test this build?

@rabbi08  Can you test this build?


Setting an organization owner doesn't update map sqls at first

1.- Create a new user and a map with a table.
2.- Assign him as an organization owner.
3.- Login again and open the map. The map looks empty (without data), but opening the sql query and just clicking “apply query” fixes it. In my case, it changed the sql from SELECT * FROM guess_country to SELECT * FROM "juanignaciosl-ded-02-admin".guess_country
cc @iriberri @ernesmb @yasharora73 @micagm

cc @rochoa

Summary of a talk with @rochoa and @zenitraM :

This is probably caused by...

PGBouncer alive connections not refreshing search path. This can be checked by manually killing connections at the middle of step 3.
Tiler keeping alive maps objects (because cartocss + sql hash doesn't change).

Query should not be rewritten.

This error is not common in production because of the previous causes, but it can happen depending on user interaction.

@rochoa it looks like it's not because PGBouncer connections but because tiler "alive maps objects". Killing connections won't fix the issue, but changing the CartoCSS does. It can be reproducible in local: if you change a layer CartoCSS manually, the map will show the data.
This is the request which fails and causes map to be empty:
http://deleteme-org-admin.localhost.lan:8181/api/v1/map?map_key=f83424546e1ce91b24e918a61a5394607cffd279

Error response (404):
{"errors":["Error: could not fetch affected tables or last updated time: relation \"public.guess_country\" does not exist"]}

Then I changed the layer CartoCSS with the console (changing CSS comment at m.layers[1].options['tile_style'] and saving with m.layers[1].save) and refreshed.

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


Creating light mode version

Hi Michael, I have interest in working with light/dark mode and toggle.

you can go ahead


WASM compression

Amplify seems to be compressing my js assets with gzip by default. I also have wasm assets in my application, and Amplify does not seem to compress wasm, which is a bummer, as wasm blobs can be quite large. I have searched the Amplify console, docs and elsewhere and I am unable to find anything about how I would be able to get Amplify to compress wasm. Thank you!

@ckampfe do you have an example link on Amplify you can share with the WASM blob?

@swaminator https://www.rasterize.live/ is my app, hosted on amplify. If you monitor the network tab, the wasm blob is called rat.wasm.

Also, you can see the full source of the app here: https://github.com/ckampfe/rat
Not sure if that is useful.

Amplify do not compress files greather than 10Mb... are your wasm files larger than that?


Use a distinct kid value for individual keys / certificates

https://github.com/Fraunhofer-AISEC/omejdn-server/blob/7136c52c78bb0d7d6a5c61bd0c4fd180d79034df/lib/oauth_helper.rb#L87
While our approach is technically compliant, it would be easier for the user if the kid is distinct. We could use a similar model as auth0, where kid is equal to x5t. See https://auth0.com/docs/security/tokens/json-web-tokens/json-web-key-set-properties

Before thinking about the JWKS, the component first needs to support key rotations in the first place. Not even multiple keys as supported atm.

#26 redoes the entire JWKS, adding support for key rollover and initial support for certificate chains to be distributed this way. If anyone would like to, it is ready to be reviewed.

old certificate/-chains and public/secret keys can be specified in omejdn.yml and the corresponding JWKs are advertised.
Where possible, x5t and x5c are specified in the JWKs


add global: reset

I just ran into this -- I used reset() in a cart and that confused shrinko8 (see help reset; it reloads 0x5f00..0x5f7f)
also, I filled out builtins_copied_to_locals (copied from pico8 0.2.5g for linux)

the tests initially failed, because this line was no longer showing up in the linter output:

test_input/bad.p8:15:12: Built-in global 'band' assigned outside _init - did you mean to use 'local function'?

this seems like it probably should still show up, even though band is now correctly marked as a member of builtins_copied_to_locals -- what do you think?

Thanks!
Looks like I missed pico8's second 'local ' line and so took only the first line as builtin locals.
I took the base change and fixed lint - as well as the reordering logic - to deal with builtin locals.


Fatal error: Unexpectedly found nil while unwrapping an Optional value

Describe the bug
Date Picker is not showing up.
Getting Fatal error when I call atePicker.present() with valid options on Xcode.
My code:
DatePicker.present({
        mode: 'date',
        date: new Date().toISOString(),
        max: this.getMaxDate(from),
        theme: 'light',
      })
      .then((dateData) => {
         console.log(dateData);
      })

Error in Xcode:
CapacitorCommunityDatePicker/Parse.swift:20: Fatal error: Unexpectedly found nil while unwrapping an Optional value

I'm getting this same issue, did you manage to find a solution @smhemel ? :)

No, I didn't get any solution regarding this. That's why I have used another package instead of this. @DanielDarrenJones

We've faced the same error in our project recently. In our case we were passing the following data to the DatePicker:
let { value: newValue } = await DatePicker.present({
  mode, // "time"
  date: value || dateSuggestion || undefined, // 24-hour formatted time string
  timezone,
  format: dateFormat, // "HH:mm"
  is24h: true,
  ios: {
    timezone,
    format: dateFormat,
    style: 'wheels',
    mode,
  },
  android: {
    timezone,
    format: dateFormat,
    mode,
  },
});

Despite the fact we explicitly passed the is24h and format params the plugin used the device's platform built-in Date formatter (DateFormatter from the Foundation code) - so devices with the 12 hour locale tried to parse the 24-hour formatted time, which returned nil. The things became worse because there's a "must-have-a-value" operator used:
//<EMAIL_ADDRESS>return formatter.date(from: date)!;
//                               ^--- here

Same error

I'm getting this same issue, did you manage to find a solution @smhemel ? :)

No, I didn't find any solution. I have implemented a custom date-picker using  component.

Same error. @smhemel any idea ?

I didn't find any solution. Also, I did R&D to find an alternative date-picker plugin for the capacitor, but I didn't.
After that, I have implemented a custom date-picker component using  component. Below, I have provided a screenshot. You can try the component.

I had the same problem setting the format and the max properties as well to ISO resolve my issue
Here's an updated version of the DatePickerOptions I am using
export const defaultPickerOptions: DatePickerOptions  = {
  locale: 'fr',
  max: new Date().toISOString(),
  mode: 'date',
  theme: 'dark',
  format: "yyyy-MM-dd'T'HH:mm:ss.sssZ"
}


stiemap.xml shows localhost:4000 everytime I build. Should we change manually to our repo.github.io domain evertime we push to the remote gh-pages branch?

[x] This is a question about using the theme.
[ ] This is a feature request.
[x] I have updated all gems with bundle update.
[x] I have tested locally with bundle exec jekyll build.
[ ] I believe this to be a bug with the theme --- not Jekyll, GitHub Pages or one of the bundled plugins.

Environment informations
Version:
-Minimal mistakes - latest

Operating System - windows

Expected behavior
bundle exec jekyll serve

Builds successfully and generates "sitemap.xml".
But sitemap.xml has all localhost:4000

Should the sitemap.xml still contain localhost:4000 even while we push to the gh-pages Github branch?
Or if we need to change to our domain, such as repo.github.io instead of "localhost:4000" manually?
Because, sitemap.xml is rebuilt everytime locally and all links change back to localhost:4000.

Sitemap generation is done by the Jekyll Sitemap plugin. So any questions or unexpected results when using it should be filed on that repo.
That said I think this is an easy fix on your part. There are some small differences in the jekyll serve and jekyll build commands. The big one obviously is serve fires up a server.
It also overrides url: in your _config.yml to localhost:4000, which is why you're seeing it in the sitemap.xml file it generates.
If you run bundle exec jekyll build instead that will build your site and use whatever domain is currently assigned to url in your _config.yml. If you're hosting on GitHub Pages I'm pretty it sets it for you automatically in the case you omitted it.

Oops. Just understood. That serving caused to render it in localhost. Excuse the beginner question.
Thanks anway! :)
And Man! Thanks for such a nice theme.

Hey Michael,
I have actually exactly this problem. I want to "fire up" my server on my hosting-server and the url is overwritten by localhost.
So I just got it working with this workaround:

Build site
Fire up the server with "--skip-initial-build"

If I want to update the page in the future I just need to build it again.
It works, but seems a bit odd to me. Well I'm not a web-dev, but shouldn't it work with just firing up the server?

@bastoGrande That's is a question for core Jekyll and has nothing to do with the theme.
As stated above they built in some logic to override site.url to localhost:4000 when starting a development server, since that's what you likely want locally when testing. When you run jekyll build it doesn't do that and will uses whatever values you've assigned for url in your _config.yml.
If you want to disable that behavior when running a local jekyll serve you need to use environment variables. See the official docs, but essentially you run JEKYLL_ENV=prod jekyll serve to force production instead of the default development.

Sitemap generation is done by the Jekyll Sitemap plugin. So any questions or unexpected results when using it should be filed on that repo.
That said I think this is an easy fix on your part. There are some small differences in the jekyll serve and jekyll build commands. The big one obviously is serve fires up a server.
It also overrides url: in your _config.yml to localhost:4000, which is why you're seeing it in the sitemap.xml file it generates.
If you run bundle exec jekyll build instead that will build your site and use whatever domain is currently assigned to url in your _config.yml. If you're hosting on GitHub Pages I'm pretty it sets it for you automatically in the case you omitted it.

I have similar problem. I created a new blog by creating a sub domain from the domain name I use. The url I will enter in config.yml should be this subdomain, right? I mean;
_config.yml
minimal_mistakes_skin    : "default" # "air", "aqua", "contrast", "dark", "dirt", "neon", "mint", "plum", "sunrise"
# Site Settings
locale                   : "en-US"
title                    : "sub.example.com"
......


Support "browser" field

https://gist.github.com/defunctzombie/4339901

It seems this browser field needs the full path to a file instead of allowing for a path to a directory and defaulting to index.js. I'd like to propose adding this functionality to allow usage similar to node and browserify.

Since the answer isn't posted here, it appears browser is a default field now. Documentation here

Any idea how you would use this to stop a node module trying to load fs?
For libsodium, adding   "browser": { "fs": false }, to packages.json seems to work, but this approach doesn't work for webtorrent, so its not clear if the libsodium project did something different than webtorrent.

That does not seem to work with objects defined as browser field, eg.
"browser": { "index.js": "browser.js", "sync.js": "browser.sync.js" }

I think this should be re-opened, since webpack does not currently respect objects set in the browser field.

@Bkucera which version are you on? The following is working for me with v4.19.0
  "browser": {
    "module": false
  }


AccumulateNode right-retract with previous right-activate may fail

The following throws an exception
(let [checked-all (assoc (acc/all)
                           ;; Add an explicit :convert-return-fn to be sure that this
                           ;; is only called with a valid reduced value.
                           :convert-return-fn
                           (fn [x]
                             (if (coll? x)
                               x
                               (is false
                                   (str "An invalid value was given to the :convert-return-fn: " x)))))
        q (dsl/parse-query [] [[Cold]
                               [?hs <- checked-all :from [Hot]]])

        hot (->Hot 50)]

    (is (empty? (-> (mk-session [q] :cache false)
                    (insert hot)
                    (retract hot)
                    fire-rules
                    (query q)
                    set))))

It should pass.
This was introduced in https://github.com/rbrush/clara-rules/commit/127a28314f067860e7a3748130b6318aca283d73 .
I made an optimization here that if an AccumulateNode had right-activates, but no left-activate that the reduced value would not be calculated until later when/if a left-activate ever occurred.  In this way, it made the accumulating behavior of the AccumulateNode lazier in when it was evaluated.
When the node had not calculated a reduced value yet, a placeholder of :clara.rules.engine/not-reduced was placed into memory to be specially mark the node's reduced value as "lazy"/"unrealized".
This value is not a valid value to pass to the :convert-return-fn of the accumulator, but the check for it was missed.
The changes here include a test for this case, along with a fix.

Looks good to me. Merging...


Calculate expression using math, support ^ operator

Are you requesting a feature, reporting a bug or asking a question?
requesting a feature
What is the expected behavior?
make complex math expressions like the one  used to calculate Body Surface Area
The plunker example does contains a possible expression (obviously not working)  that could be implemented.
https://plnkr.co/edit/IwGA43xYOjc39LaYGISL?p=preview
Is it feasible?
Thanks
Cinzia

You can write, register and use your own functions as described in this article - https://surveyjs.io/Documentation/Library/

@cinziasala We support "*" and "/", we do not support "^".
I will add it into our TODO list.
Thank you,
Andrew

@andrewtelnov
Thank you so much!


use cli file in start dev reload

(Trying all contributors)
@all-contributors please add @rluvaton  for content


Create release-notes-changelog.md

Kapacitor Release Notes/Change log -- official doc page!

@timhallinflux - looks good! I did some little edits to the Hugo-related stuff to get the page to load, and I removed one sentence but I think this is good to go!


Feature Request: Single Hyphen Longs (such as -type)

In clap.rs I suggest having multi character shorts/single hyphen longs.
Issues:
It would collide w/ stacking Options
Fix (Opt-In in order to disable arg stacking):
1: Use a .stackable() in order to disable stacking
example: https://hastebin.com/adidocexov.js
2: Have a dependency option in Cargo.toml
example: https://hastebin.com/jotegipixu.ini

Thanks for the suggestion! From the gitter conversation we'd probably end up supporting this with an opt-in AppSettings variant.
I'd be happy to mentor someone to adding this, or I can add it after v3 is out.
Prior to adding this feature I'd want someone to draw up a spec for how they see it working, as there are still some unresolved design questions.
Off the top of my head we'd need to decide:

Should we support -type args and longs --type in the same application?

Or should -type args disable longs?
Also, if we disable longs, should --help still be special cased?

Should we support -type args and stacking with values (-oval being -o val, or -typef is -type f as in the unix find command)?
Should we allow still stacking of single shorts?

If yes, should we allow stacking with multi-char args too? -typebzf being -type -b -z -f)?

I'm inclined to say no to just about all of the above, as it's all stuff we could add in later once the initial design and implementation is done. The primary thing we'd need to decide is allowing of longs/special casing of --help.

Also, there are two distinct ways to go about implementing this (granted which one we pick is slightly based off the answers to the questions above).

Disable longs, and treat -type args just like longs
Disable stacking and treat all -type style args as a single argument and not potentially multiple.

The terminology suggested feels confusing to me.
AFAIK, the distinction between short and long options is characteristic to POSIX / Unix / Linux command line style and implies that the "short" options are single-character and stackable (and optionally accept tackling value to the character).
The most well-known example of multi-character single-hyphen options is the find command. However, even find has a separate flavour of short options (-P, -L, -H, -D debug_options and -O0..-O3). Furthermore, are we really going to call -executable, -iwholename and -noignore_readdir_race "short" options?
Thus I'd suggest not reusing the "short" name and changing the interpretation of the "long" ones instead.
@NoorMkdad Could you please also write down your motivation for these? Is it something along the lines of "I want to use -cha because --cha looks weird"?

Thus I'd suggest not reusing the "short" name and changing the interpretation of the "long" ones instead.

I'm good with this. Let's refer to this as "Single Hyphen Longs"
As far as motivation, I've had enough people ask about this particular feature, that there is enough reason to add it as an opt in feature. The most common motivation I've found is people porting applications from another language, and want to be able to have a drop in replacement for some other application which uses single hyphen longs.

@tanriol Pretty much, I don't want to use a double dash for something 3 characters long and is intended as a shorter version of a longer option + It'll look weird

@NoorMkdad we may end up implementing this as disabling the long version. Because by convention the short version of a long arg is a single hyphen followed by a single character.
However, there are programs out there (especially on Windows) which use a single hyphen followed by a word as the long version.