Cannot see org/group linked secrets on repo despite having write access

Component
web-ui
Describe the bug
Hi,
I am not able to see secrets assigned to an org or groups that I am a part of in a repository where I have write access.
I can see secrets if I'm set as a Woodpecker administrator, as a regular user, I can use those secrets but the list appears empty.
I should see secrets on the settings > secrets page of a repository which I am an admin of in the forge.
To note :
When I go to settings > secrets, there is an error popping up : ": user not authorized".
The repository is placed in an organization where I have write access permissions. When I try to go back to the org by clicking on its name, the ": user not authorized" pop-up again and the list is empty.
Steps to reproduce

Create a repository in an organization where you have write access
Enable it on woodpecker
Go to settings then secrets

Expected behavior
I should be able to see secrets linked to organizations and groups that I am a part of without being a Woodpecker admin on repositories that I'm a administrator of.
System Info
Woodpecker 2.8.0

Additional context
No response
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]

No, but I do have write access on this org.

If that's how it works right now, alright but shouldn't I (even as a reader) be able to see the secrets available on a repo ?

Cannot reproduce on next-21755bef4e.

I should see secrets on the settings > secrets page of a repository which I am an admin of in the forge.

I am an admin in the forge

of a repository

I can see secrets on the settings page


python312Packages.mitogen: 0.3.12 -> 0.3.13

Diff: https://github.com/mitogen-hq/mitogen/compare/refs/tags/v0.3.12...v0.3.13
Changelog: https://github.com/mitogen-hq/mitogen/blob/v0.3.13/docs/changelog.rst

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 347897 run on x86_64-linux 1

4 packages built:

python311Packages.mitogen
python311Packages.mitogen.dist
python312Packages.mitogen
python312Packages.mitogen.dist


Ref #36 -- Add time of day as additional instruction

@mostafa-anm is there a test yet for the system prompt? you might created/update it.

You can simply use sam.config.TIMEZONE. It'll have what you need.


EPIC: non-spatial Python-Rust Arrow library

I'm trying to move client APIs to be less tied to spatial-specific objects. E.g. geoarrow::table::Table is now just an Arrow table (schema and batches) with nothing spatial-specific (just geoarrow metadata on one or more columns). Similarly, I'm moving the JS APIs to use arrow-wasm::Table as the primary/only table export.
I think part of this progress in Python will involve a totally non-spatial Python-Rust Arrow library, which the GeoArrow Python bindings will depend on. I think it's better to start this as a standalone library earlier than later so that it stays non-spatial.
Ideally this generic arrow-rust-Python library will not enable multiple-pymethods so it can also be used in pyodide.

[ ] Decide on a name/repo location for this new library
[ ] Should it have namespacing? E.g. to distribute Parquet separately?
[ ] Minimal generic arrow-rs bindings

See also discussion here and here

pyo3-arrow version 0.1 is now published! https://docs.rs/pyo3-arrow

Now that pyo3-arrow exists and is published, I'll close this


ERROR: The certificate of ‘download.ncg.ingrid.pt’ has expired``

$ wget https://download.ncg.ingrid.pt/webdav/udocker/udocker-1.1.3.tar.gz
--2018-12-11 00:12:34--  https://download.ncg.ingrid.pt/webdav/udocker/udocker-1.1.3.tar.gz
Rezolvare download.ncg.ingrid.pt (download.ncg.ingrid.pt)... <IP_ADDRESS>
Connecting to download.ncg.ingrid.pt (download.ncg.ingrid.pt)|<IP_ADDRESS>|:443... conectat.
ERROR: The certificate of ‘download.ncg.ingrid.pt’ is not trusted.
ERROR: The certificate of ‘download.ncg.ingrid.pt’ has expired.
The certificate has expired

hi @mr-c
should be fixed, I have renew the certificate
confirm and if OK, close


Proposal for provider separation

Problem Statement
Maintaining SecretStores/ClustersecretStores as we add new providers is painful, as newly added providers tend to be more dynamic then older ones.
This is an issue to go to GA as the SecretStore API would eventually not follow v1 grading.
Related Issue
To Address #694 as a general strategy for versioning
Proposed Changes
See design

Hey @moolen  @knelasevero  I was able to come up with a code proposal for the provider separation that really pleases me. I'm updating this proposal with more diagrams on the technical level what are the implementation differences and steps that I think it should take, but bottom line is:

Allows provider separation per spec
Allows much cleaner referentAuthentication mechanism with SecretStores/ClusterSecretSTores (reason why I think we should not drop them)
Allows for smooth migration of providers (instead one big PR that changes all)
Relatively simple to implement changes (At least for small providers such as Gitlab (added as an example to see how different it would be))

Also relevant, @shuheiktgw  @Skarlso @sebagomez

Here is the branch with the new code. https://github.com/external-secrets/external-secrets/blob/feature/new-provider-structure/pkg/controllers/secretstore/client_manager.go

Also worth to mention, if this proposal is accepted, after implementing all provider separation, we can deprecate:

GetProvider() schema call (and all the Provider/store schema to be fair, and just change it to be Provider/Kind schema)
Convert() methods on the provider interface
NewClient(store) from provider interface (we can rename the NewClientFromObj to NewClient, and remove NewClient implementation).

Just went through the implementation with @gusfcarvalho in a call. I like how gradual we can take this one, and already apply this TODAY without needing to get breaking changes in. I think this will help us a lot in the future so I am a +1 for this

@knelasevero @moolen @shuheiktgw @Skarlso @sebagomez @IdanAdar  Please use this comment to vote if this design should be implemented or not. A lot of discussion here is still valid, this approach seems to be the one that got the most of the tradeoffs away. The only remaining bit of discussion is what we deprecate after this feature is added - SecretStore, SecretStore.spec.provider, or none. The scope of this design will NOT be around this deprecation.
👍 means you vote to implement this
👎 means you vote to not implement this
🚫 means you refrain yourself from voting
Please add one of those as a comment to this issue

this proposal was accepted with the majority of votes 👍

/approve

@moolen @knelasevero can you be the final approvers here? 😄  can't approve my own contribs


Update the output data from the MILP

*The time ran needs to be updated to 1200 (or whatever it is in general.yaml)


Server does not save players list

The server is running somewhat properly (can connect & play) but the /admin/players list is emptied at each restart, losing player names and roles.
@DevinLeamy on discord : "IIRC, local changes are just stored in-memory and are not persisted. Feel free to open an issue for this as well. This was the intended behaviour for the development build so that we didn't break things in production"

@SachaYatta Just to clarify, are you running with ./b data-snapshot run or doing a self-hosted k8s build?


chore: bdd-spring-1575566862 to 0.0.1

chore: Promote bdd-spring-1575566862 to version 0.0.1

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

Needs approval from an approver in each of these files:

OWNERS

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


inconsistencies when using flag '-o json'

kubernetes version
Client Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.4", GitCommit:"d6f433224538d4f9ca2f7ae19b252e6fcb66a3ae", GitTreeState:"clean", BuildDate:"2017-05-19T20:41:24Z", GoVersion:"go1.8.1", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.4+coreos.0", GitCommit:"8996efde382d88f0baef1f015ae801488fcad8c4", GitTreeState:"clean", BuildDate:"2017-05-19T21:11:20Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}

Environment:

aws
coreos
Linux ip-10-0-65-22 4.11.2-coreos #1 SMP Tue May 23 22:04:34 UTC 2017 x86_64 Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz GenuineIntel GNU/Linux
tectonic installer:

What happened:
I have a daemonset, running on 5 nodes. When I kill a pod of this daemonset and get it's status
with kubectl, I will notice inconsistencies with the json output ( -o json )
For example, when I kill the pod and run
kubectl get pod "$POD_NAME",
it's status will be Terminating
But, killing it and running
kubectl get pod "$POD_NAME" -o json | jq '.status.phase',
I will get Running
Also, as I said, this pod is from a daemonset.
When I do kubectl get daemonset "$DAEMONSET_NAME" -o json,
the output of status will sometime be inconsistent too.
for example, after killing a pod and waiting for it to be up again ( status Running ),
the status of the daemonset will look like that
    "status": {
        "currentNumberScheduled": 5,
        "desiredNumberScheduled": 5,
        "numberAvailable": 4,
        "numberMisscheduled": 0,
        "numberReady": 4,
        "numberUnavailable": 1,
        "observedGeneration": 3,
        "updatedNumberScheduled": 5
    }

What you expected to happen:
Both command should give me the same result, ie Terminating
How to reproduce it (as minimally and precisely as possible):

kill a pod
get it's status using kubectl get pod "$POD_NAME"
kill another pod
get it's status using kubectl get pod "$POD_NAME" -o json | jq '.status.phase'

Thanks for the issue.
For some resources get does some logic instead of just printing what is in the yaml so this is expected.


[Autocomplete][joy] Fix Autocomplete and Modal components to work together

Fixed In Joy UI Autocomplete and Modal do not work properly together.
It's a continuation of https://github.com/mui/material-ui/issues/37501

[x] I have followed (at least) the PR section of the contributing guide.

@siriwatknp can you please check this.

@saikathalderr Thanks for the fix. I think it is partially done because by adding zIndex might work with Modal but it introduces another bug when you use the Autocomplete outside of the Modal.
For example, you have a header with a sticky position (zIndex < the modal) if you scroll the page while Autocomplete's listbox is open, you will see that the listbox is above the header.
I think the solution is still using zIndex but with a CSS variable so that it can be controlled by the context (components).


Change tee-to-socket to split-to-socket

Make this script a wrapper which invokes the command with child_process rather than piping. When piping the exit code is lost, if instead it wraps and invokes with child_process then it can exit with the same code.

Fixed by 3f17b0a802ddba0171bd90b66fc13b5b3d8023fc.


SAML login working in Firefox but not Chrome

Hello,
I am running Amazon Connect using the SAML 2.0 authentication option with the CCP embedded in an iframe. The integration is working fine in Firefox, where when I login to my app, the CCP will get opened in a new browser tab and automatically close once it finishes loading. In Chrome, the new tab opens, the CCP loads successfully, but the tab does not auto close and I see the following errors in my browser console.

Here are the properties I'm setting when calling initCCP:
ccpUrl: https://<my-connect-instance>.awsapps.com/connect/ccp-v2
loginUrl: Here I'm using my ADFS IdPInitiatedSignOn url with a relay state using connect/federate/<my-connect-instance-id> and a destination of connect/ccp-v2 as described in https://docs.aws.amazon.com/connect/latest/adminguide/configure-saml.html.
loginPopup: true
loginPopupAutoClose: true
softphone: {     allowFramedSoftphone: true }
Update: I've also noticed this issue happen occasionally in Firefox. For example, we had 3 co-workers test it in Firefox, for 2 of them it worked while 1 of them saw the same errors shown above.

I've just tested again now with the latest version of Streams installed:
Streams: 1.6.6
Chrome: 89.0.4389.128
One important difference for me is that recently it has been working in a regular Chrome window, but the issue happens consistently when running in an incognito window. Could you see if you can reproduce the issue in incognito mode?

Chrome incognito mode doesn't work because the default Chrome behavior is "Block third-party cookies in Incognito", see your Chrome cookies settings at chrome://settings/cookies.

That was the issue, thanks!

Chrome incognito mode doesn't work because the default Chrome behavior is "Block third-party cookies in Incognito", see your Chrome cookies settings at chrome://settings/cookies.

This will soon be the default behavior for chrome in general. Does the Connect team have any comment on how this will be addressed?
https://www.pcmag.com/news/google-effort-to-kill-third-party-cookies-in-chrome-rolls-out-in-april


[Enhancement]: Unit test has issue if unique rule used in model

General unique rule syntax is unique:table, but it creates issue in update request to ignore current model.
Currently it works if unique rule is defined as unique:table,fieldName but it should also work as unique:table only.

Hii,
We have write sample unite tests, that are not using $rules, so it will run fine.
Still, let us know the exact steps, so we can produce it.
Thanks

I think we already have an open issue for unique handling. so this should be handled when that is fixed.


change: Add cargo.lock to project

Resolves #74

Thank you @Nukesor,
Super cool to create a git AUR package !
Can you change the commit type to "chore" or "ci" instead of "change" so the commit gets picked during next release changelog generation ? Sorry for nitpicking, I shall create a CONTRIBUTING.md file and update the conventional commit bot make this clear.

Done :)
Don't worry, I tend to forget documenting stuff like this all the time as well :D


Reversing next work day

Hey, using your library for some local council work. Need to find out the previous workday. Currently using the is_work_day method, but perhaps we could change up the get_next_work_day method to include a step param that we could set to -1 and iterate backwards? Something like this?
    def get_next_work_day(self, division=None, date=None, step=1):
        """
        Returns the next work day, skipping weekends and bank holidays
        NB: If no division is specified, only holidays common to *all* divisions are returned.
        :param division: see division constants; defaults to common holidays
        :param date: search starting from this date; defaults to today
        :param step: step, use -1 to reverse, default 1
        :return: datetime.date; NB: get_next_holiday returns a dict
        """
        date = date or datetime.date.today()
        one_day = datetime.timedelta(days=step)
        holidays = set(holiday['date'] for holiday in self.get_holidays(division=division))
        while True:
            date += one_day
            if date.weekday() not in self.weekend and date not in holidays:
                return date

Any thoughts?

good idea @Eugerome, going backwards in time sounds like a useful feature. i've added a get_prev_work_day method because i think it's more understandable than providing a negative step when asking for a next day.
https://pypi.org/project/govuk-bank-holidays/0.9/

Sounds fair. Thanks for adding it!


Can I use this in offline.

I am trying to display flags in offline mode.
Is is possible?

All the flags are bundled within the package, it should be usable offline.


Abrt readme and ccpp fix

This PR contains 2 changes.

First is README update, that contains documented use of ABRT by NPD, my leader asked me to do.
Second is abrt-adaptor ccpp pattern fix, I found it didn't catch all possible cpp problem messages produced by ABRT.

This change is

LGTM


Avoid overwriting seed==0

Before this change, if I create a Trainer with seed=0, the seed is overwritten with a random seed.

Good catch, @tbenthompson !


Support abandon should allow multiple claim ids / txids

The Issue
Support abandon should allow the passing of multiple claim ids so that users can unlock tips across numerous claims.  Should also allow the same with multiple txid/nouts so that we can allow users to select a bunch of tips and unlock them in one shot.
System Configuration

LBRY Daemon version:
LBRY App version:
LBRY Installation ID:
Operating system:

Anything Else

Screenshots

Internal Use
Acceptance Criteria

Definition of Done

[ ]  Tested against acceptance criteria
[ ] Tested against the assumptions of user story
[ ] The project builds without errors
[ ] Unit tests are written and passing
[ ] Tests on devices/browsers listed in the issue have passed
[ ] QA performed & issues resolved
[ ] Refactoring completed
[ ] Any configuration or build changes documented
[ ] Documentation updated
[ ] Peer Code Review performed

this is now possible with txo spend


Unable to use turbo from 1.2.6+

What version of Turborepo are you using?
1.2.6
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Mac
Describe the Bug
Executing a command like pnpm exec turbo run test --concurrency=1 for 1.2.6+ causes a high cpu usages and memory usages and a command that causes close to 100% cpu usages and a memory usages up 25gb+ (system has 16gb). After a while the turbo instance will cause the computer to slow down and a forced restart (power button)
Unable to use turbo to execute a task command defined
Expected Behavior
Able to execute the command in a similar manner as on 1.2.5 without high cpu and memory usage
To Reproduce
MacBook Pro 14" M1
Latest maCOS
PNPM 6.32.9
Small mono-repo with ~49 packages
run the command:
pnpm exec turbo run test --concurrency=1 --continue

Yikes. Can you verify that --dry works? What happens if you run w/o --continue?

Appears to have been resolved in most recent releases of turbo. Closing this ticket for now :)


Add doc-comment to test README examples

Allows to keep in check the README file examples.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #102   +/-   ##
=======================================
  Coverage   96.14%   96.14%
=======================================
  Files          12       12
  Lines        1479     1479
=======================================
  Hits         1422     1422
  Misses         57       57

Impacted Files
Coverage Δ

src/lib.rs
92.3% <ø> (ø)
: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 0aa2fa2...310d3c2. Read the comment docs.

Neat, thanks.


Bump knobots update-deps job at post release

As per title, the following patches are necessary to start pulling the main so it should be done after the release:

https://github.com/knative-sandbox/knobots/pull/230
https://github.com/knative-sandbox/knobots/pull/245

/cc @dprotaso @lionelvillard

/lgtm
/approve


GDScript: Fix stack overflow when using multiple await

This fixes a regression caused by #61003. I tested this PR with the example #57126 and could not reproduce the crash nor the leak, so I assume I didn't undo the fix.
Fixes #61130

Thanks!


Crashing failure in cernan 0.8.3 with elastic 0.20.6

The cernan project recently updated to elastic 0.20.6 in 0.8.3 and we're now getting reports of crashes in production. Example of the crash:
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Client(ClientError { inner: Error(Request, State { next_error: Some(Http(Error { kind: Io(Error { repr: Custom(Custom { kind: WouldBlock, error: StringError("timed out") }) }), url: Some("http://REDACTED.es.amazonaws.com/_bulk") })), backtrace: None }) })', /checkout/src/libcore/result.rs:906:4
note: Run with `RUST_BACKTRACE=1` for a backtrace.

It's unclear to me if the problem is internal to elastic or an issue with cernan's use of it. Our integration is here: https://github.com/postmates/cernan/blob/master/src/sink/elasticsearch.rs On further review I'm suspicious of the two unwraps present in this function: https://github.com/postmates/cernan/blob/master/src/sink/elasticsearch.rs#L176 but would appreciate any suggestions or other problematic uses of elastic.
Cernan tracking issue: https://github.com/postmates/cernan/issues/353

Hi @blt, I'd say the issue would be that second unwrap on the bulk call. The source appears to be this error variant in reqwest. We get this when reqwest  fails to receive a response in the given timeout. It looks like along with the upgrade to elastic 0.20 we also pulled in reqwest 0.8 which introduces a default timeout of 30 seconds. It's possible that since these are bulk requests that 30 seconds just isn't long enough in this case (although that is still a pretty long time) and the new default is being hit.
Right now the only way we'd expose that configuration would be through reqwest directly. You can build a reqwest client and pass it in to elastic with no timeout using its timeout method:
let http = reqwest::Client::builder()
    .timeout(None)
    .build()?;

let client = SyncClientBuilder::from_params(params)
    .http_client(http)
    .build()?;

But I think it would be good to add a convenient timeout method to elastic's builder, that is ignored if you pass in a http_client.

Although if you're not expecting requests to ever take >30 seconds then it's possible the timeout is just the effect of some other problem.
If the user bumps the RUST_LOG environment variable up to info then starting requests will be logged too.
If there's anything else I can do to help please let me know!

Hi @KodrAus, thank you for the quick response. I'll take care of that second unwrap and put cernan in a test environment, see how things go from there. I wouldn't expect requests to take > 30 seconds but anything can happen, I suppose.
An explicit timeout on elastic's builder would be welcome.

We've confirmed that postmates/cernan#356 resolves the problem. Thanks much!

No problem! Glad to hear it's working smoothly again. The timeout is potentially another error variant we could pull out to the top-level since it's another one you might reasonably want to respond to programmatically.


test.sh does not aborts when there are errors

See this https://travis-ci.com/vanhauser-thc/AFLplusplus/jobs/294050859
There is a Null Ptr Deref in the fuzzer reported by ASan and Travis says that all tests are fine.

ah damn. yes that was something I tried to workaround the arm64 travis issue.
now it reports correctly again. sorry


Differing definitions of int64_t on macos

On macos (no idea about "real" BSD), int64_t is defined as long long, while on linux it's defined as long. This causes issues with the printf formatting generating warnings (it won't actually affect the runtime since long is still also 8 bytes)
There's inttypes.h and PRId64 nonsense, but that might get ugly...

@zhiayang thanks for bringing this up! I hope we will come with a reasonable solution eventually.

@zhiayang oh btw, @kolumb tried to address that in #23. Do you still get the warnings on the latest commit?

@zhiayang oh btw, @kolumb tried to address that in #23. Do you still get the warnings on the latest commit?

yep, it's fixed already!
sadge syntax though

yep, it's fixed already!
sadge syntax though

yep, it's fixed already!
sadge syntax though

yep, it's fixed already!
sadge syntax though


Add Validate Operator Bundle check to CraneEngine

The Validate Operator Bundle does not change whether we are using Crane
or not. So, just re-enable in the operator policy.
Signed-off-by: Brad P. Crochet<EMAIL_ADDRESS>

I will validate that this does not require privilege before merging.
/hold

/hold cancel
This is passing without privilege now.


strconv/json: non-UTF8 bytes are being unescaped in strconv.Unquote/json.unquote

What version of Go are you using (go version)?

$ go version
go version go1.17.2 darwin/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
```
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/fffonion/Library/Caches/go-build"
GOENV="/Users/fffonion/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/fffonion/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/fffonion/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/Cellar/go/1.17.2/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.17.2/libexec/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.17.2"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/fffonion/bbb/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug
```

What did you do?

package main

import (
	"fmt"
	"strconv"
)

func main() {
	// `"\147\\u0001"`
	in := []byte{34, 147, 92, 117, 48, 48, 48, 49, 34}

	str0, _ := strconv.Unquote(string(in))
	fmt.Println([]byte(str0))

}

It seems neither does UnquoteChar (https://github.com/golang/go/blob/go1.17.6/src/strconv/quote.go#L267) nor does its caller Unquote (https://github.com/golang/go/blob/go1.17.6/src/strconv/quote.go#L267) handles the error from utf8.DecodeRuneInString(s), so any single byte non-UTF8 sequence are being escaped to utf8.RuneError and stored in output.
In Python for example, such cases are handled properly:
a=bytes([147,92,117,48,48,48,49])
a.decode('raw_unicode_escape')
# '\x93\x01'

What did you expect to see?
[147 1]
What did you see instead?
[239 191 189 1]

This is how strings and UTF-8 work in Go. Every byte of illegal UTF-8 is converted to U+FFF8.
it's actually not all that clearly documented. Although we went to great pains to do this consistently between all the library routines and the range statement, and therefore by inclusion strconv.Unquote, the best documentation for this behavior is here: https://pkg.go.dev/unicode/utf8#DecodeRune. It also appears in https://go.dev/ref/spec#For_statements in the section about range clauses.
It should probably be made more visible.
But as far as this behavior is concerned, it is working as intended. I'll leave the issue open to see if anyone has ideas about the best way to make this easier to discover.

@robpike Thanks for the reply!

@robpike I noticed the case above might pointed to json package instead (https://github.com/golang/go/blob/go1.17.6/src/encoding/json/decode.go#L1306) where a similar approach is done as strconv.Unquote. However, per JSON RFC, putting unescaped
characters like 0x93 unescaped, as shown in example, is allowed.
Does it make sense to make the json package specificly allow this use case? Technically it could just be:
		default:
			rr, size := utf8.DecodeRune(s[r:])
			if rr == utf8.RuneError {
				b[w] = s[r]
				r += 1
				w += 1
			} else {
				r += size
				w += utf8.EncodeRune(b[w:], rr)
			}

The the error condition would need to be
size == 1 && rr == utf.RuneError

and that is certainly possible but I am not in a position to say whether it's the right thing to do. It would likely break some tests, but maybe not too many. Non-compliance with the RFC is arguably a reason to make such a change but this behavior would be unique within the Go environment that it would require discussion.

When it comes to encoding/json, I'm afraid the current behavior is well documented:

When unmarshaling quoted strings, invalid UTF-8 or invalid UTF-16 surrogate pairs are not treated as an error. Instead, they are replaced by the Unicode replacement character U+FFFD.

Changing the default behavior would surely break programs out there in subtle ways. The general understanding with the Go standard library's compatibility guarantee is that we may be able to change undocumented behavior, as long as very few Go programs out there break because of the change. But changing documented behavior, especially if it could break programs, is almost always a breaking change we cannot do.
Note that the json encoder does allow disabling the replacement of invalid UTF-8 (see below), so one could imagine a proposal to also opt out of this feature in the decoder.

String values encode as JSON strings coerced to valid UTF-8, replacing invalid bytes with the Unicode replacement rune. So that the JSON will be safe to embed inside HTML

@mvdan Thanks for pointing out the docs. And I do understand chaning the behaviour is a concerning move. Is it worth
to however have a similar switch that disables this behaviour, as SetEscapeHTML does? As I do test with json libraries like
json-iterator/go and bytedance/sonic and they support such behaviour.

Is it worth to however have a similar switch that disables this behaviour, as SetEscapeHTML does?

That is what I'm saying could be proposed. I would start a new issue, though, because it's entirely separate from strconv.

@fffonion. There are at least three possible behaviors to do for json:

Silently convert invalid UTF-8 to the Unicode replacement character,
Silently preserve invalid UTF-8 as is, and
Reject invalid UTF-8.

The current behavior of json is behavior 1. Both behaviors 1 and 2 are non-compliant with RFC 8259, which states in section 8.1. that the text "MUST be encoded using UTF-8". If we add an option, it would be to opt-into behavior 3, but that doesn't seem to be what you want (based on the original issue).
I'm not sure we should be adding options to json that allows it to get farther from standard behavior. Rather, we should be doing the opposite (i.e., moving closer to compliance).

@dsnet Indeed, reading through the UTF8 spec, it says if a codepoint is larger than 0x7F (non-printable), it should be encoded in at least two bytes. So a single byte\x99 is not a valid "UTF-8 string". I guess for our case maybe the JSON encoder (lua-cjson) might be problematic; I do tested other implementations like PHP or Python and Go, they seem to correctly encode those non-printable ASCII bytes.


Create performance benchmarks

Currently, Incremental DOM does not have any good performance benchmarks to base changes on. Ideally they would be able to run as a part of the build process as well as standalone. In addition to testing for something like average time per pass, it should also check for the maximum time per pass to make sure GC is not kicking in.
This is fairly difficult as it is hard to model how the rest of an application generates garbage during updates. While the library itself may never generate enough garbage to cause more than an young gen GC, any allocation may end up ultimately causing old-gen GC which is hard to isolate and reproduce in a test, especially as heap sizes are likely to vary between environments. Since young gen GC can be very fast, it can be difficult to notice GC occurring with the amount of noise in a test.
Additionally, a spike does not necessarily indicate a GC occurred, but could happen due to the process being scheduled off which is likely to occur if running many iterations and hogging the CPU. This is not likely to occur in actual usage while updating web pages, but is something to watch out for when creating tests
Ultimately, any sort of environment we are likely to test on will have a huge amount of RAM compared to a smartphone in a developing country, which may have as little as 256MB and much of that taken by the OS.

An additional point is that testing performance on extremely hot code paths is not particularly valid as there is almost no use case where enough updates to one piece of the UI would occur for this to happen. Even if it did happen in some cases, it is not the predominant case. Since we are aiming for predictable performance, we really want to have the best non-optimized performance possible. Collecting enough samples to be statistically valid while making sure not to run into optimizations is something to look out for.

There may be some flags that can be used from https://code.google.com/p/v8/source/browse/branches/bleeding_edge/src/flag-definitions.h#522 to check for GCs perhaps by capturing and inspecting the trace output.
Some flags from https://code.google.com/p/v8/source/browse/branches/bleeding_edge/src/flag-definitions.h#255 may be useful in disabling optimizations to allow for better measuring of performance on non-hot code paths while still capturing enough data to draw conclusions.

Imo, something like a standard benchmark for template engines needs to exist at some point. dbmonster is meaningless to me.

It seems like when dbmonster hit repaint cycle, all the fast implementation seems to be same speed to me.
I find this Ember/Backbone benchmarks useful, since you can see speed and numbers in average.
https://twitter.com/tomdale/status/424247991780659200
already added Incremental DOM in my repo for above benchmark - http://rawgit.com/S-YOU/doTA/master/examples/animate-circles/index.html, but which includes my library too, you may remove it.

It seems like when dbmonster hit repaint cycle, all the fast implementation seems to be same speed to me.
I find this Ember/Backbone benchmarks useful, since you can see speed and numbers in average.
https://twitter.com/tomdale/status/424247991780659200
already added Incremental DOM in my repo for above benchmark - http://rawgit.com/S-YOU/doTA/master/examples/animate-circles/index.html, but which includes my library too, please ignore.

already added Incremental DOM in my repo for above benchmark - http://rawgit.com/S-YOU/doTA/master/examples/animate-circles/index.html, but which includes my library too, please ignore.

Sorry to break your demo, but I updated the github pages where you were pulling IncrementalDOM from to use the new element functions (elementOpen instead of ie_open, etc).

I have updated my demo too. rawgit have 5 min cache; thx for the ping.

Not sure I should open new thread or not, but I noticed that performance of incremental-dom on firefox is only half speed of chrome, while Ember+HTMLBars and Backbone is similar on both browser.
http://rawgit.com/S-YOU/doTA/master/examples/animate-circles/index.html

I noticed a similar difference on some of the benchmarks I am working for Firefox. It is definitely worth looking into.

I created a branch with a few initial tests. I'd like to add more as I go along as well as adding a comparison to a baseline version (e.g. 0.2.0).
I'm also working on some exploratory work around perf (especially the FIrefox issues brought up) in my own branch in this file. So far the performance is much more inline with Chrome and I'm exploring some ideas for #141. It isn't anywhere near complete, but it should be easy enough to create a bunch of experiments.

awesome, :thumbsup: going to test it now.

exploration indeed faster, on both firefox and chrome. :thumbsup:
myresults -
chrome - exploration/creation 3.340ms, incrementaldom/creation 8.281ms
firefox - exploration/creation 10.278ms, incrementaldom/creation 15.690ms

Turns out caching firstChild, nextSibling and parentNode has some pretty good performance benefits (seeing down from 250ms to 165ms per iteration on selection). It does cause some extra time on creation, so might want to find a way to mitigate the impact, It might be worth continuing down that path and inverting the relationship where we operate on an object tree in place that has references to the corresponding DOM nodes. The reason I didn't go this route to begin with because it was easier to just operate on the DOM but it seems like it might be worth it.


please find exception stacktrace - using arcface as model

return DeepFace.find(img_path=img_path, db_path=config.tdes_images_location, align=align,
  File "/home/akhil/PycharmProjects/TDES-analytics/venv/lib/python3.10/site-packages/deepface/DeepFace.py", line 488, in find
    img_objs = functions.extract_faces(
  File "/home/akhil/PycharmProjects/TDES-analytics/venv/lib/python3.10/site-packages/deepface/commons/functions.py", line 105, in extract_faces
    img_region = [0, 0, img.shape[1], img.shape[0]]
AttributeError: 'NoneType' object has no attribute 'shape'

message is clear. your input (most probably img_path or some item in db_path) cannot be load that is why its shape is none.

can I raise a MR for having clear message? @serengil

return DeepFace.find(img_path=img_path, db_path=config.tdes_images_location, align=align,
  File "/home/akhil/PycharmProjects/TDES-analytics/venv/lib/python3.10/site-packages/deepface/DeepFace.py", line 488, in find
    img_objs = functions.extract_faces(
  File "/home/akhil/PycharmProjects/TDES-analytics/venv/lib/python3.10/site-packages/deepface/commons/functions.py", line 105, in extract_faces
    img_region = [0, 0, img.shape[1], img.shape[0]]
AttributeError: 'NoneType' object has no attribute 'shape'

what was the decision of this problem? @surapuramakhil


refactor: Use npx jest as default jest_cmd

Slightly better start perf: No need to climb the directory tree
More flexible: Either runs the locally installed version or asks to install it temporarily*
Jest users (should) always have NPM installed, and as such, have npx available.

*A temporary install through npx still requires a config file present somewhere in the current working directory or above in the tree.
A default config file could fix that, but I think it should be the user's choice to set it up or not.
However, it would be nice to have an option to set the path to a global config file, and maybe recycle the old tree-climbing functions to find a local config, and then use the default if none is found... But then that wouldn't work with Jest configs from inside package.json. :confused:

Woops, it seems my formatter aggressively shifted all indentation there.


[DO NOT MERGE] Auto PR to update dependencies of istio

This PR will be merged automatically once checks are successful.
none

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
1bde358e58fb923d2565c6304e49796bcfeb355a
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
1bde358e58fb923d2565c6304e49796bcfeb355a
link
/test istio-unit-tests

prow/istio-presubmit.sh
1bde358e58fb923d2565c6304e49796bcfeb355a
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


HashMap - Word Frequency - Dart

Please assign this to me as I would love to work on it using HashMap
Thanks.

Please I would like to turn this into Dart rather than Java, thank you.

hello @fz3hra Are you still working on this?

@ismaelsadeeq it was already done

Okay, closing this.


WIP: Add 2019 Live stream

Add stream page.
Update link to stream page.

:+1: feel free to merge when you put the link in

Updated link, merging.
CC @RichiH Ready for twitternating.


Also publish on open-vsx

https://open-vsx.org - a repository of VSCode plugins for forks of VSCode that removes integration with Microsoft properties.

https://open-vsx.org/extension/alantech/alan-lang


load multiple files under single directory

how to load multi static files under directory !
module.exports = {
entry: './assets/js/.*js',
output: {
filename: 'bundle.js'
}
};
i am unable to find proper docmentation  with working sample code?

Note that entry accepts an array. You could glob the files you need and pass a resulting array to it. It still might not do what you expect, though.
How are you going to use the resulting bundle?

i will use final consolidated js file and replace all existing files from js directory in prod version

i want o achieve something like this
http://stackoverflow.com/questions/17008472/how-to-minify-multiple-javascript-files-in-a-folder-with-uglifyjs and then consolidated all file into one file

The following would output a build file per each entry. It assumes you are using glob but any other library would do.
...
entry: toObject(glob.sync(<pattern>)), // object of entries in format {name: path}
output: {
  filename: '[name].min.js' // note [name], that's where entry name goes
}
...

That toObject thinger will figure out the object keys. Those keys are then passed to [name]. You can try hardcoding something at first to see how it works and generalize from there as you like.

thanks , really good approach ! bebraw
could we use below
var path = require('path');
module.exports = {
entry: path.join(__dirname, 'assets'),
output: {
filename: 'bundle.js'
}
};
iam getting error "ERROR in Entry module not found: Error: Cannot resolve 'file' or 'directory'"

Nope. You need something like this:
var glob = require('glob');

module.exports = {
  entry: toObject(glob.sync('assets/**/*.js*')),
  output: {
    filename: '[name].js'
  },
  ...
};

function toObject(paths) {
  var ret = {};

  paths.forEach(function(path) {
    // you can define entry names mapped to [name] here
    ret[path.split('/').slice(-1)[0]] = path;
  });

  return ret;
}

Hi,
great the logic work awesome but stumbling unto below error
ERROR in Entry module not found: Error: Cannot resolve module 'assets/js/utility
.js'
the file exists  in path!

Make sure the paths you generate are absolute. That might resolve it.

Hi sorry my bad
just put " ./"
entry: toObject(glob.sync('assets/**/.js')),
and it start working great man

and how import from main?

i have tried the webpack.config.js given above and now it is giving me this error
Conflict: Multiple assets emit to the same filename [bundle].js.
I wanted to generate the output of all files in a single bundle.js file.Can anyone help me?

I created a npm package for entry-points based on these.
See README
https://github.com/sectsect/webpack-sweet-entry

To generate the proper folder structure with the file path you need something like below:-
You can use this as below:-

function toObject(paths) {
    var ret = {};

    paths.forEach(function(path) {
        // you can define entry names mapped to [name] here
        ret[path] = path;
    });

    console.log(ret);
    return ret;
}

module.exports = {
    entry :  toObject(glob.sync('./src/**/*.js*')),
    output: {
        path: path.resolve(__dirname, 'lib'),
        filename: '[name].js'
    },
}```

refined a little bit like entry object key and value both should be `path` so it will generate the same `lib` folder structure like `src` folder.

Thanks @bebraw


[Select] Do not render correctly when displayEmpty is set to true

Outlined or Filled selects do not render correctly when displayEmpty is set to true. The label overlaps the 'None' value.
https://codesandbox.io/s/material-demo-forked-kg8p2?file=/demo.tsx

It's by design, see the examples.

The description in the Component API reference for Select - displayEmpty property does not mention anything about outlined and filled variants. If it's by design why it is not mentioned in the documentation? And by the way a property that only works in a certain context looks like a bad design.

@mihaipanait This is fair, what do you think about this diff?
diff --git a/packages/material-ui/src/Select/Select.d.ts b/packages/material-ui/src/Select/Select.d.ts
index fc3a50279e..28514096b1 100644
--- a/packages/material-ui/src/Select/Select.d.ts
+++ b/packages/material-ui/src/Select/Select.d.ts
@@ -54,8 +54,11 @@ export interface SelectProps
   /**
    * If `true`, a value is displayed even if no items are selected.
    *
-   * In order to display a meaningful value, a function should be passed to the `renderValue` prop which returns the value to be displayed when no items are selected.
-   * You can only use it when the `native` prop is `false` (default).
+   * In order to display a meaningful value, a function can be passed to the `renderValue` prop which
+   * returns the value to be displayed when no items are selected.
+   *
+   * ⚠ When using this prop, make sure the label doesn't conflict with the empty displayed value.
+   * The label should either be hidden or forced to a shrunk state.
    * @default false
    */
   displayEmpty?: boolean;
@@ -129,12 +132,10 @@ export interface SelectProps
   onOpen?: (event: React.ChangeEvent<{}>) => void;
   /**
    * Control `select` open state.
-   * You can only use it when the `native` prop is `false` (default).
    */
   open?: boolean;
   /**
    * Render the selected value.
-   * You can only use it when the `native` prop is `false` (default).
    *
    * @param {any} value The `value` provided to the component.
    * @returns {ReactNode}

Do you want to work on a pull request to improve the documentation? :)

Seems to me shrink isn't enough, as it shows as the border go through the shrinked label.
We also need to "notch" the select I think


Dogecoin switch to PoS consensus

Just trying to discuss the idea before wasting any time on this, if the community is really interested in switching to PoS and updating the source code to the latest Bitcoin source to fix all vulnerabilities, there is a shortcut to all of this, Particl  is using a modified version of the PoS v3 which they call Particl Proof of Stake, it solves the main issues of the first of PoS by allowing for cold staking (thus not exposing keys) this also allows pool staking for smallholders (think of it as delegating staking powers to validators) and it also implements community governance by allowing voting, private transactions can be ported as well (CT and RingCT) but that can be ignored if the community decided to stick to fully transparent transactions.
If the community decides to go this path:

Changes can be ported and consensus changed with a fork at a defined block height (this will bring compatibility with Bitcoin 0.19 as well, which includes huge improvements including segwit)
Implement faster blocks (for example 1 min blocks)
I wouldn't increase the block limit, but if the community insists on doing it, I wouldn't push it beyond 2MB, since there will be already 10x the capacity of BTC, with native segwit it is possible to unlock more txps by porting the lightning network.

Edit: I need to mention that this version of PoS (or any PoS system I know of FWIW) is inferior to the security of PoW, but its carbon footprint is neutral

How hard is it to pivot to PoS at this point?

I think POS can solve the problem about Reduce power consumption，but more and more Whale will stake dogecoin and doge more and more concentrated，like Present BTC ，so if you want dogecoin  make everyone can tanfer to each others ，please think carefully abount it，and I think  make some ecology  dapp is the more important。

I think POS can solve the problem about Reduce power consumption，but more and more Whale will stake dogecoin and doge more and more concentrated，like Present BTC ，so if you want dogecoin make everyone can tanfer to each others ，please think carefully abount it，and I think make some ecology dapp is the more important。

Aren’t there better PoS consensus protocols already?

"If the community decides to go this path:
Changes can be ported and consensus changed with a fork at a defined block height (this will bring compatibility with Bitcoin 0.19 as well, which includes huge improvements including segwit)"

Incorporating Segwit into Doge isn't possible without serious fundamental changes to the code, from our teams experience you cannot add segwit to aux-pow algo.  this would require a fork away from auw-pow and have serious known and unknown consequences when syncing SPV wallets or electrum for example.

"Implement faster blocks (for example 1 min blocks)"

This would require another fork.  Probably unnecessary since zmq is functional and speeds are already sufficient.

"I wouldn't increase the block limit, but if the community insists on doing it, I wouldn't push it beyond 2MB, since there will be already 10x the capacity of BTC, with native segwit it is possible to unlock more txps by porting the lightning network."

regarding block size only, this may also have serious known and unknown consequences to SPV wallets or electrum

How hard is it to pivot to PoS at this point?

The code is difficult but the real question is community adoption.  Would the coin community make the change if POS client was introduced?  That's the question to ask.
If Musk wants POS, he should submit a bounty like everyone else.

"If the community decides to go this path:
Changes can be ported and consensus changed with a fork at a defined block height (this will bring compatibility with Bitcoin 0.19 as well, which includes huge improvements including segwit)"

Incorporating Segwit into Doge isn't possible without serious fundamental changes to the code, from our teams experience you cannot add segwit to aux-pow algo.  this would require a fork away from auw-pow and have serious known and unknown consequences when syncing SPV wallets or electrum for example.

"Implement faster blocks (for example 1 min blocks)"

This would require another fork.  Probably unnecessary since zmq is functional and speeds are already sufficient.

"I wouldn't increase the block limit, but if the community insists on doing it, I wouldn't push it beyond 2MB, since there will be already 10x the capacity of BTC, with native segwit it is possible to unlock more txps by porting the lightning network."

regarding block size only, this may also have serious known and unknown consequences to SPV wallets or electrum

those changes would come with the PoS consensus change, they are already implemented in Particl and have been working for at least 3 years now.
Also, since we are discussing consensus changes, this already implies forking (probably multiple hard forks)

I don't know if moving to PoS is really the solution to the primary concerns that seem to have spurned this concern. As far as I can see, the main source of this movement in the community appears to be derived from concern about the environmental impact of Dogecoin, not the protocol it uses. Perhaps it might be prudent if something as serious as a fork was on the cards to widen the scope and actually define the full set of issues that are of concern right now and come up with our own solution to say the top major problems present (e.g. network transaction capacity, environment, etc)?
The amount of interest Elon is generating for the coin right now might actually allow us to do something innovative in the space by bringing in new people to help.
If we aren't making significant changes though that we can easily justify as solving a major issue, it will hard to get many on board with something as significant hard fork in the network.

Cardano have a POS already working and staking pools. they have the concept of saturation to avoid whales to centralize the staking process, it works, but I think it is a more democratic and make it a better staking process if the protocol just do round-robin to select the next block signer pool, that way it does not matter how many stake you have as long as you have a minimum amount TBD, but how many pools are there.  There will never be too many pools on the long term because people won't run pooling nodes if there are not cost effective, too many pools will make them to loose money, so the pools counter will tent to be stable around the minimum profitable point.

I don't think PoS is a serious consideration.  There are numerous problems, the least of which our inflation rate is not enough to support it.  Do you think anyone would lock up their coins for 1 year to make 4% returns?  Your coins could go up or down 4% in a day.

I don't think PoS is a serious consideration. There are numerous problems, the least of which our inflation rate is not enough to support it. Do you think anyone would lock up their coins for 1 year to make 4% returns? Your coins could go up or down 4% in a day.

Solid PoS algorithms do not require freezing your funds. There are some out there that you can literally unstake at any given moment and sell if you need to or use for payment. Example being ADA.

Hey guys, you should come over to this thread so we don't have redundancy
https://github.com/dogecoin/dogecoin/issues/1924

I don't think PoS is a serious consideration. There are numerous problems, the least of which our inflation rate is not enough to support it. Do you think anyone would lock up their coins for 1 year to make 4% returns? Your coins could go up or down 4% in a day.

Solid PoS algorithms do not require freezing your funds. There are some out there that you can literally unstake at any given moment and sell if you need to or use for payment. Example being ADA.

Yes, I am talking about ADA here, Cardano. it is a solid POS system, not freezing needed

PoW only! Keep it stable, improve it. Keep it free!
 We eventually need to move away from it. The Ethereum guys are really smart to have made that decision years ago.
Bitcoin will show the worst case scenario, it's a no brainer you shouldn't need to waste a whole's country's energy intake to process 7 transactions per second.
Then there's also the economic issues of PoW as the block rewards dwindle (in the case of Bitcoin), things will get ugly when block fees can't pay the bill, the entire hashrate will be very irregular, there will be all sorts of attacks to fork blocks that yield bigger fees.
Some princeton guys wrote a whole paper of the clusterf** that will come to be
On the Instability of Bitcoin Without the Block Reward

Bitcoin provides two incentives for miners: block rewards
and transaction fees. The former accounts for the vast majority of miner revenues at the beginning of the system, but
it is expected to transition to the latter as the block rewards
dwindle. There has been an implicit belief that whether
miners are paid by block rewards or transaction fees does
not affect the security of the block chain.
We show that this is not the case. Our key insight is that
with only transaction fees, the variance of the block reward is
very high due to the exponentially distributed block arrival
time, and it becomes attractive to fork a “wealthy” block
to “steal” the rewards therein. We show that this results
in an equilibrium with undesirable properties for Bitcoin’s
security and performance, and even non-equilibria in some
circumstances. We also revisit selfish mining and show that
it can be made profitable for a miner with an arbitrarily low
hash power share, and who is arbitrarily poorly connected
within the network. Our results are derived from theoretical
analysis and confirmed by a new Bitcoin mining simulator
that may be of independent interest.
We discuss the troubling implications of our results for
Bitcoin’s future security and draw lessons for the design of
new cryptocurrencies.

I think POS can solve the problem about Reduce power consumption，but more and more Whale will stake dogecoin and doge more and more concentrated，like Present BTC ，so if you want dogecoin make everyone can tanfer to each others ，please think carefully abount it，and I think make some ecology dapp is the more important。

I agree! POS is not good for a currency "for the people", a currency for strength and liquidity, it does not need concentration in portfolios to carry out mining. POW is the best way not to let it accumulate in wallets and make the currency strong for use around the world; We see the strong exit of ETH for portfolios for its 2.0 update, is this a good thing? Only speculative for big whales, but to create a strong currency for everyday life, only a currency like Doge is able to supply the needs of the world market, from small to big business.

 We eventually need to move away from it. The Ethereum guys are really smart to have made that decision years ago.
Bitcoin will show the worst case scenario, it's a no brainer you shouldn't need to waste a whole's country's energy intake to process 7 transactions per second.
Then there's also the economic issues of PoW as the block rewards dwindle (in the case of Bitcoin), things will get ugly when block fees can't pay the bill, the entire hashrate will be very irregular, there will be all sorts of attacks to fork blocks that yield bigger fees.
Some princeton guys wrote a whole paper of the clusterf** that will come to be
On the Instability of Bitcoin Without the Block Reward

Bitcoin provides two incentives for miners: block rewards
and transaction fees. The former accounts for the vast majority of miner revenues at the beginning of the system, but
it is expected to transition to the latter as the block rewards
dwindle. There has been an implicit belief that whether
miners are paid by block rewards or transaction fees does
not affect the security of the block chain.
We show that this is not the case. Our key insight is that
with only transaction fees, the variance of the block reward is
very high due to the exponentially distributed block arrival
time, and it becomes attractive to fork a “wealthy” block
to “steal” the rewards therein. We show that this results
in an equilibrium with undesirable properties for Bitcoin’s
security and performance, and even non-equilibria in some
circumstances. We also revisit selfish mining and show that
it can be made profitable for a miner with an arbitrarily low
hash power share, and who is arbitrarily poorly connected
within the network. Our results are derived from theoretical
analysis and confirmed by a new Bitcoin mining simulator
that may be of independent interest.
We discuss the troubling implications of our results for
Bitcoin’s future security and draw lessons for the design of
new cryptocurrencies.

Also PoW is unsafe from a government as an adversary scenario, ask people in Venezuela how the government would easily find them, seize their miners and put them in prison, the power consumption easily gives you away, not to mention all the unnecessary costs that go to middle men to keep the network running (power companies, ASIC manufacturers, shippers) and add to that all the extra costs (if you've ever mined you'll know well what I'm talking about)
Then you have all the a-symmetries, not everybody can mine given their access to cheap energy, and the inevitable backslash from the public Bitcoin has started to face and which will only get worse as the years pass and we have more natural disasters due to greenhouse emissions. It's a hard sell telling people most of the mining comes from clean energy sources when we know most of the hashrate is coming from corner-cutting China.
I don't think there's a single next gen blockchain using PoW, it's just not going to fly in the future.

It is not a complete truth, but it is also not a lie! But we don't need POS for Doge at the moment, we need more speed on the network for transactions and lower costs for that only! Maybe in the future, when we have a more distributed use, with Doge production already above demand, then yes, we can upgrade to POS and that will make the currency gain value at that moment, now that would only make the value go up strongly but without I intend with the use of it by mankind on a daily basis.
Just what Doge needs now is to increase the number of transactions and lower fees, with greater performance on his network, he is able to supply any market need worldwide!

Bitcoin will show the worst case scenario, it's a no brainer you shouldn't need to waste a whole's country's energy intake to process 7 transactions per second.

This is the key.  Don't do the transactions on the ledger then.  7 tx/s isn't much, but it's definitely enough to serve the needs of a billion users by shifting activity off the chain.
And, since it goes without being said enough, I would like to point out:

energy usage in itself is morally neutral
carbon emissions are problematic
not all energy production releases carbon into the atmosphere
not all carbon emissions come from energy production (in the US, only about 25%)
eliminating fossil fuels from energy supply benefits everyone, not just people that use crypto

I would like to propose a slightly different look at this.

Doge helps people gives back - That's what makes it better. So how can Doge give back 'power'

Competition in Proof of Work is simply a waste of energy. It's means multiple people using their own resources, and the 'best' one wins. This is analogous to buying a $100 dinner, just eating 2 fries and throwing the rest out. This does not help nor does it 'give back'

The Proof of Stake needs to allow anyone to stake, and un-stake at will. It also needs to allow cold staking

As noted the switch in consensus from PoW to PoS needs to occur at a specific block height.

Presently to participate in mining, you need to be part of a mining pool and it's great that this can occur in combination with litecoin BUT mining pools are simply a different type of 'whale' then the 'whales' staking with Proof of Stake. It seems to me to be better to give back to those actually running full nodes and staking, then those using up energy for the 'hopes' of winning.  I believe this analogous to the idea, it is better to invest $1/day in an RRSP  then to pay $/day for a lottery ticket. The money spent is the same, but the former gaurteees a return (give's back) while the latter is only the 'hope' of a return.

I am closing this issue since I don't think most people on this thread understand the technical requirements for this.

<EMAIL_ADDRESS>no that easy to successfully attack


请问如果要使用pcn数据集重新训练模型要训练多长时间

I uesd 3days with 2 GPU
May I ask which piece of code did you use to directly predict using a trained model? I've been unable to find it


Update FLI viewer for multihop

More general question...is the current iteration of FLI contracts compatible with UniswapV3?


Adds seven new channels

Adds Apple, Bright Moments, Devconnect, farcastHER, Nature, and Rugby channels per Dan's new release today
Also adds the Network States channel which was created recently

@dylsteck apologies for the delay on reviewing this. I've merged in #8 which contained a few more channels in addition to the ones in this PR.

No problem, and sounds good!


[R-package] Add additional linters to CI

Linting for the R code in this project was introduced in #2437 . As of that PR, the following linters from the lintr project were not available from the distribution of lintr on CRAN.
github_only_linters <- list(
    "equals_na" = lintr::equals_na_linter
    , "function_left" = lintr::function_left_parentheses_linter
    , "implicit_integers" = lintr::implicit_integer_linter
    , "paren_brace_linter" = lintr::paren_brace_linter
    , "semiconlon" = lintr::semicolon_terminator_linter
    , "seq" = lintr::seq_linter
    , "todo_comments" = lintr::todo_comment_linter
    , "true_false" = lintr::T_and_F_symbol_linter
)

To close this issue, add those linters to .ci/lint_r_code.R once lintr does a new release (> 1.0.3) to CRAN.

Closing in favor of being in #2302 with other feature requests. If you'd like to submit a PR to address this, re-open the issue.

Since we use r-lintr distribution from conda (not CRAN), to complete this issue it may also be necessary to make a pull request to https://github.com/conda-forge/r-lintr-feedstock to get r-lintr feedstock updated.

it seems that lintr did a release on October 1, 2019! I am going to re-open this issue and pick it up tonight or tomorrow.

and they updated the conda feedstock for r-lintr 🙌
Seems that project has a bot that automatically opens a PR when a new version makes it to CRAN (or maybe when a new release is created on jimhester/lintr).
Either way, should be able to address this issue now!


Rad Pro: J614 conversion factor, detection speed

Hi, I have installed the new 2.0 version on my GC-01 equipped with a J614 GM tube and compared to my stock Bosean FS-5000 with a much better J321 tube (better design and construction of the counter overall). When testing against a small source of Americium-241 or background levels the GC-01 tends to overreport the radiation level in Sv by almost double, sometimes even saturating completely and skyrocketing resulting in a "reset" (the level becomes -.--). Also, if it is possible, I suggest to make the adaptive fast algorithm faster, since compared to the FS-5000 it's much slower to detect a source. Or maybe create an option called adaptive super fast idk. Just a thought, I really appreciate the developer work :)

Can you make a video showcasing the response time of the Bosean FS-5000 and Rad Pro?

Here are the videos, remember I have not installed radpro on the FS-5000, only on the GC-01. https://1drv.ms/f/s!AtXtrPDofI3fnF6hsrigzKZNjMyS
The conversion factor I'm using is the standard one for the J614 tube in the menu.

Regarding the slower response of the GC-01, this behavior is expected. The two devices you are comparing have tubes with significantly different conversion factors. Under identical conditions, the device with the lower conversion factor will receive fewer pulses per second than the other. As a result, it will take longer to average.
Regarding the selected conversion factor of the J613 tube, I insist that you continue this conversation in #89.


How to .verify that a Domain layer constructor initialized with expected SobjectList

Use case:
Class A needs to construct a Domain for Opportunity and then invoke a method on that domain object
Opportunities domain = Opportunities.newInstance(someOppoList);
domain.doWork();

If you are unit testing class A and want to use ApexMocks to see if your code under test is passing the right list of opportunities to the domain object, you try in your testmethod :
...
Opportunity] mockOppos = new List<Opportunity> { ...}
((Opportunities)mocks.verify(mockOppoDomain,mocks.times(1).description('domain sb constructed w/ all Oppo in scope')))
				.newInstance(mockOppos);

But this won't compile because Opportunities.newInstance() is a static method and there is no StubAPI support for statics.
Since the pattern says to use Opportunities domain = Opportunities.newInstance(someOppoList); that in turn resolves to:
public static IOpportunities newInstance(List<Opportunity> sObjectList){
    	return (IOpportunities) Application.Domain.newInstance(sObjectList);
  }

...I'm a bit puzzled how to use ApexMocks to see if my mockDomain object was constructed with the expected list of sobjects.
N.B. relevant Mockito Stackoverflow  seems to suggest this isn't going to be possible.
Is there an alternative besides moving the domain method to a Service layer?

I think that the best thing to do, it's to move the logic in the service layer. The Domain layer duties in my mind are strictly related to the trigger. That is tested through integration tests.
I'm used putting the logic that would change the object in the service layer, and then you can mock it.
I never had the need to mock the domain.

Ah yes, but what about the Example in the Force.com Enterprise Architecture book where the domain layer implemented an isCompliant method?  That wasn’t a trigger use casse.

Eric Kintzer

On Oct 6, 2017, at 04:49, Enzo Denti<EMAIL_ADDRESS>wrote:
I think that the best thing to do, it's to move the logic in the service layer. The Domain layer duties in my mind are strictly related to the trigger. That is tested through integration tests.
I'm used putting the logic that would change the object in the service layer, and then you can mock it.
I never had the need to mock the domain.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Ah constructor mocking/spying. Unfortunately, I don't think this is possible in ApexMocks.
I've been using sinon in nodeJS and had similar issues.
The best I can suggest is having a domain factory method, where the tests create a real Domain instance and verify the records. And then route all of the Domain creation throughout your app through this factory, mocking it out in unit tests.
Closing as wontfix, I think it's just a limitation we have to accept.

@cropredyHelix yes, if its behavior of the object it can be included in the domain class, it's not a hard and fast rule though, at least if it's in or below the service layer we have logic in a safe place! 👍


Feat: upload delete popup

Fixes #110
Changes

Add popup to delete candy machine
Move delete to popup
Functionality works

Checks

[X] Have you catchup your branch with the latest state in base?

[X] Have you reviewed your proposed changes and removed debris?
[X] Have you successfully ran due tests with your changes?

This is happening to me.
On low height screens this happens too...

Change button title "Delete candy machine" to "Delete"
Also, the disabled button when you click delete is bigger than the previous one, it looks a little weird

 This is happening to me. On low height screens this happens too...  Change button title "Delete candy machine" to "Delete" Also, the disabled button when you click delete is bigger than the previous one, it looks a little weird

Yes, this is solved in this pr because the behavior is similar

please @cpl121 lets fix the conflicts with the base branch before proceeding with a final review 🙏🏼


Install-WDK failing on Windows 2019 image

Describe the bug
In the last release from the old repo this script portion was disabled: https://github.com/microsoft/azure-pipelines-image-generation/blob/releases/vs2019/20191209/images/win/scripts/Installers/Vs2019/Install-WDK.ps1
Virtual environments affected

[ ] macOS 10.15
[ ] Ubuntu 16.04 LTS
[ ] Ubuntu 18.04 LTS
[ ] Windows Server 2016 R2
[x ] Windows Server 2019

Expected behavior
Running the VSIXnstaller from the VS2019 directory should probably take place after the VS2019 installation script is run.
Actual behavior
In current packer template the Install-WDK script is run prior to the Install-VS2019 script.
From our logs:
==> vhd: Start-Process : This command cannot be run due to the error: The system cannot find the file specified.
==> vhd: At C:\Windows\Temp\script-5e0206cb-ef62-b1b3-285f-0beff0e0b781.ps1:34 char:13
    vhd: Unsuccessful exit code returned by the installation process: .

Fixed in #157 and awaiting deployment.


Feature/zenko 303 management websocket proxy support

Makes the management websocket go through a proxy if environment variables are present.

Hello RachedBenMustapha,
My role is to assist you with the merge of this
pull request. Please type @bert-e help to get
information on this process.
Status report is not available.

Waiting for approval
The following approvals are needed before I can proceed with the merge:

2 peers

In the queue
The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.
The changeset will be merged in:

:heavy_check_mark: development/8.0

The following branches will NOT be impacted:

development/7.4

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of Release Engineering will
contact you to help resolve the matter.
IMPORTANT
Please do not attempt to modify this pull request.

Any commit you add on the source branch will trigger a new cycle after the
current queue is merged.
Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of Release Engineering now.

I have successfully merged the changeset of this pull request
into targetted development branches:

:heavy_check_mark: development/8.0

The following branches have NOT changed:

development/7.4

Please check the status of the associated issue ZENKO-303.
Goodbye RachedBenMustapha.

@RachedBenMustapha I think the dependencies introduced are not used in the code, bufferutil and utf-8-validate.

they are, ws has slow fallbacks if they are missing


pull request for e2e test at 12/16/2016 09:15:18

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


filters and facet built on stored value

Describe the bug
Not 100% a bug, but, in my opinion a nice-to-have improvement.
When a facet or a filter index is built on top of values submitted by selecting them from a closed list (i.e. dropdown), the facet / filter relies on the "stored" value, and not on the displayed value, which might differ in case of submissions performed in different languages.
To Reproduce
Let's suppose we want to configure a facet and/or a filter to lookup publication by language. Stored value in dc.language metadata is the iso code of the language, while user has selected the value depending on context language ("English", "Inglese", "Anglais", ...).
With current logic, a facet of this kind would appear with "en", "es", "fr",... values. If an user wants to perform a manual query based on this filter, in case he/she enters "English" the query would not return any result as filter, in this case, would work only if user uses "en" in his/her query.
Expected behavior
It would be a nice improvement allowing lookup on fields having values set starting from closed lists, allowing filtering and faceting working on the "display value" in addition to the "stored value" already used.

Agreed this would be a nice improvement, but flagging this as low priority for now as it's not immediately required.  That said, if anyone volunteers/donates this, I'd be supportive of the idea.


Fixes for base 58 encoding and decoding

This PR fixes a OOB read in the base58 decoding function and a OBB write in the encoding function.
The encoding function has been rewritten so that it uses much less stack. Finally, a small bug has been fixed in the decoding function: buffers with several leading 1s were not properly decoded.
The prototypes of the function have been modified to make tests easier. Return value must be checked by the caller as they do not throw exceptions anymore.

Merged manually


Tojimangas update domain

Source information
Tojimangas 1.4.1
Source language
Spanish
Source new URL
https://tojimangas.com/
Other details
No response
Acknowledgements

[X] I have updated all installed extensions.
[X] I have opened WebView and checked that the source URL has not changed yet.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I will fill out all of the requested information in this form.

Add a :+1: reaction to issues you find important.

The extension already uses that link. As the bot message has told you twice now. If there's an issue, make issue request.


Update ganache to v7

Related to #211

Coverage decreased (-0.5%) to 90.273% when pulling 678d8a5cb363324dd36cd3a58b96b6fa95fba0b2 on update-ganache-v7 into 4b2842746a98d8fb6bb3e7829573157096d20438 on master.


Notify devs about the regression on the PR

We are failing the perf tests when there is a possible perf regression and posting a link to the performance dashboard


Informing users about accessibility standards

When building math visualizations, it's common to have mouse-based interactions. It's worth warning people, especially ed-tech people, that they must accommodate keyboard users to comply with various parts of WCAG.

I've been surprised to see how easy it was to use the keyboard for point manipulation
What do you have in mind? A docs page about keyboard interaction?

Generally yeah. I think with SVG, especially when creating custom elements, it'll be easy for people to blunder things like keyboard operability and navigation.
I think screen reader support is unlikely (given the visual nature of the library) but it would be good to ensure folks know how to make accessible visualizations.
Even as it stands now, I don't like how users have to tab through movable points. It feels cumbersome if there's a lot on the screen, and since they can be repositioned arbitrarily, the tab order can feel unintuitive at times.


Getting empty object. Sometimes.

I'm using react-redux.
I'm getting an weird issue.  My component has applyContainerQuery being applied to it, but I have a redux container wrapping it. Looks like this:
<Connect(MyComponent)>
  <ContainerQuery(MyComponent)>
     <MyComponent>
  </ContainerQuery(MyContainer)>
</Connect(MyComponent)>

When I reload the page my component console logs out this.props.containerQuery and it results in an empty object.
Has anyone seen this with react-redux?
The only time that I can get it to not give me an empty object is when the HMR reloads the code.  If I manually reload the page I'll always get an empty object.  Really stumping me.
UPDATE: I figured it out.  One of my developers added in an at the top of the render() function:
if (!item.id) {
   return null;
}

@silasb Thanks for the update!


Added support for opensearch-py client connections urllib3httpconnection, requestshttpconnection

Description
Added support for opensearch-py client connections urllib3httpconnection, requestshttpconnection.
Issues Resolved
#437
Follow up Issues
Document how to use urllib3httpconnection, requestshttpconnection client connections.
Usage examples:

below connection_class in --client-options is case insensitive.
opensearch-benchmark execute-test --distribution-version=2.11.1 --workload=geonames --test-mode --kill-running-processes --client-options "connection_class:urllib3"

For urllib3httpconnection: both options (urllib3, urllib3httpconnection) will work. Case insensitive

For requestshttpconnection: both options (requests, requestshttpconnection) will work. Case insensitive

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

Closing this PR. I will resubmit it once opensearch-py has service time metrics.


(Kotlin) Retrieving value from map with class reference key

1. Which language seems to have the issue?

Kotlin

2. Describe the issue
[Code block in markdown file]

[Actual Preview]

[What I've expected]

3. Are you using highlight or highlightAuto?

I'm not sure but this issue occurs in Visual Studio Code markdown preview.

4. Sample Code to Reproduce
```kotlin
val validators = mutableMapOf<KClass<*>, FieldValidator<*>>()
validators[String::class] = DefaultStringValidator
validators[Int::class] = DefaultIntValidator
```

I can confirm your other two issues, but not this one.  This is sloppy and not the kind of mistake we'd typically make - perhaps the VS Code plugin is interfering with our generated HTML somehow.    If you believe this is truly an issue with our library please submit a stand-alone JSFiddle that reproduces this issue with only our code and I've be happy to have a closer look.
Also possible this has been fixed already but not yet released.


infinite the window has crashed dialogs

VS Code version: Code - Insiders 1.23.0-insider (fc389d2, 2018-04-05T05:10:30.542Z)
OS version: Darwin x64 17.4.0

Steps to Reproduce:

Unclear.  Let me know if I can upload a crash log.

Does this issue occur when all extensions are disabled?: No
I wonder if this is eslint?  Can you please use this bug to just avoid the infinite dialogs?  That would be a core vscode issue right?
This would be greatly appreciated -

Why do you suspect eslint?
Did this just start happening recently or did it always happen?

How do I check?  I think eslint crashed for what is it 5 times before you see a dialog?  Just started happening. I started code with disabled extensions and then started code with extensions enabled and it disappeared.

So you see a message that eslint crashed, then you see the window crash?

and then started code with extensions enabled and it disappeared.

So when you start with extensions disabled, it doesn't crash?

If you can just tell me how to get you a dump we can save back and forth time.  Within the hour previous, I saw the window that eslint crashed x times.  It does not crash now either way.

Directions here: https://github.com/Microsoft/vscode/wiki/Native-Crash-Issues#macos


Update image docker.io/ollama/ollama to v0.2.8

This PR contains the following updates:

Package
Update
Change

docker.io/ollama/ollama
patch
0.2.7 -> 0.2.8

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


[1.12.2] rftools dimlets very very very rare drop

After haivn a EIO spawner running spawning ender evo enderman, i noticed that after 24hrs of grinding/killing using draconic evo grinder ive amassed 8 Dimlet packages form rftools dim where as after running the same period using def MC enderman youd have over 100x as many dimlets.
Im not sure if this is a compatability issue from rftools dim side with ender evo

Seems this was an EnderIO spawning issue


Docker image gce-proxy:1.33.3-alpine is missing libraries

Bug Description
The Alpine version of the latest gce-proxy image is lacking some libraries, making it unable to run /cloud_sql_proxy:
Error loading shared library libresolv.so.2: No such file or directory (needed by /cloud_sql_proxy)
Error relocating /cloud_sql_proxy: __res_search: symbol not found

Example code (or command)
// paste your code or command here

Stacktrace
No response
Steps to reproduce?

Run: docker run -it --rm eu.gcr.io/cloudsql-docker/gce-proxy:1.33.3-alpine /cloud_sql_proxy
Expect:

2023/02/23 07:04:20 current FDs rlimit set to<PHONE_NUMBER>, wanted limit is 8500. Nothing to do here.
2023/02/23 07:04:20 gcloud is not in the path and -instances and -projects are empty

Actual result:
Error loading shared library libresolv.so.2: No such file or directory (needed by /cloud_sql_proxy)
Error relocating /cloud_sql_proxy: __res_search: symbol not found

Environment

OS type and version: GKE 1.25 and latest Manjaro
Cloud SQL Proxy version (./cloud-sql-proxy --version): 1.33.3
Proxy invocation command (for example, ./cloud-sql-proxy --enable_iam_login --dir /path/to/dir INSTANCE_CONNECTION_NAME): just plain /cloud_sql_proxy without any parameters

Additional Details
No response

Same issue seems to affect the 2.1.0 alpine image (eu.gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.1.0-alpine).
Distroless (default) 2.1.0 image does not suffer from the same issue.
Environment

OS type and version: GKE 1.23
Cloud SQL Proxy image: 2.1.0-alpine
Proxy kubernetes definition:

containers:
  - name: cloudsql-proxy
    image: eu.gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.1.0-alpine
    args:
      - "--structured-logs"
      - "--port=1433"
      - "--private-ip"
      - "<INSTANCE_URL>"
 .
 .
 .

GKE logs
Error loading shared library libresolv.so.2: No such file or directory (needed by /cloud-sql-proxy)
Error relocating /cloud-sql-proxy: __res_search: symbol not found

Hi @tun0 and @GroundedBeans! 😄
Thanks for raising this and providing details on the issue. I was able to reproduce this for the latest versions of both the v1 and v2 proxy.
I will investigate further and work on a fix as soon as I can.
In the meantime, you can both unblock yourselves by downgrading your version of alpine build. I tested 2.0.0-alpine and 1.33.2-alpine and both seem to work just fine.
Will add further updates here as I have them, thanks!

In the meantime, you can both unblock yourselves by downgrading your version of alpine build.

That's exactly what we did :wink:

@tun0 and @GroundedBeans I will be performing a release soon to push new working images.

Released new version of both the v1 and v2 proxy:

v2.1.1
v1.33.4

Awesome! Will test tomorrow (right now it's time for sleep 😴).

Morning!
Alpine image seems to work now.

Can confirm as well! Thanks!


use ByteBuffer instead of Array[Byte] for MemcacheCodec

use ByteBuffer instead of Array[Byte] for MemcacheCodec
bump to 3.0.0 since this is an API change

yay!


How to configure a secret in opensearch.yml config.

Is your feature request related to a problem? Please describe.
I am looking out for a way to configure opensearch.yml with a secret.
For eg:
plugins.query.datasources.masterkey: "secret"
Above master key can't be committed to github, so we need a way to integrate opensearch.yml with secrets in K8s.

@prudhvigodithi  Any idea on this?

Hey @vamsi-amazon, you can pre-create the secret and mount the secret using extraVolumes: and extraVolumeMounts
Example:
      volumeMounts:
        - name: opensearch-config
          mountPath: "/usr/share/opensearch/opensearch.yml"
          readOnly: true
  volumes:
    - name: opensearch-config
      secret:
        secretName: opensearch-config-secret
        optional: true

When you add as secret, make sure you comment this line https://github.com/opensearch-project/helm-charts/blob/main/charts/opensearch/values.yaml#L48 that asks for opensearch.yml: setting.

@prudhvigodithi  are you suggesting to create entire opensearch.yml as a secret volume and mount it?

Is there a way just for using k8's secrets inside of opensearch.yml, not whole file plugins.query.datasources.encryption.masterkey: {K8's secret}

Is this setting plugins.query.datasources.masterkey: "secret" supported as environment variable ?

@vamsi-amazon Is your setting supported as env variable?

@prudhvigodithi  @Flyingliuhub  I didn't know what that means?

@vamsi-amazon certain OpenSearch configs can be passed as environment values ex cluster.initial_master_nodes, network.publish_host etc, in the same manner can this plugins.query.datasources.masterkey: "secret" passed as environment  values?
More examples https://github.com/Opster/opensearch-k8s-operator/blob/main/opensearch-operator/pkg/builders/cluster.go#L379-L412
Adding @TheAlgo @bbarani @peterzhuamazon

Closing this issue, please feel free to re-open if required.
Thanks
Adding @bbarani @peterzhuamazon


Automatically change directory to mounted EBS volume

Resolves #10

it's been a while since I looked at this code, so I'm inclined to trust you, but isn't this done by getTmp() ?

It seems that getTmp() only does this when --volumes is specified.

Looking into this, it seems both --volumes and --ebs are using the $TMPDIR env var. I'm thinking it could be useful to separate these out, e.g., $TMPDIR_VOLUME and $TMPDIR_EBS.

i.e., something like:
https://github.com/tomazberisa/batchit/commit/47393468b9955becdeae02e543e8aa4c31e761f1

TMPDIR is used by the OS and things like python's tempfile or go's version to know where to make temp-files. So I'd prefer to keep it as that. I think it's fine to have one over-ride the other as the user can over-ride in their script.

I am fine with this PR as-is if it's ready.

Good point re: TMPDIR and agree overrides are ok.
Made a very minor tweak and PR is ready.
Thanks for looking into all this!

thanks!


Issue538

fixed #538
Contributing to Twilio

All third-party contributors acknowledge that any contributions they provide will be made under the same open-source license that the open-source project is provided under.

[ ] I acknowledge that all my contributions will be made under the project's license.

So I took over this PR. Summary of the changes I have done:

implementation should be generic, so it is deduplicated for each framework
it takes into account parameter name, type and default value
if a parameter was marked as redacted at least once, the merged parameter is treated as redacted as well
similarly we prefer to preserve x-empty-is-null: true
there is still one thing that is not done properly: https://github.com/twilio/guardrail/pull/539/files#diff-f0ed213f3160ee8faee416537f0c544eR470 I'm not really sure how to raise an error cleanly there

@hanny24 Would you please permit outside collaborators on this branch? I've got a fix for the throw that I would like to push, but it seems disallowed.

Just gonna open a separate PR actually.

Merged


Can't install the app

After clicking through all the warnings about installing an app from an untrusted source, I just end up with "App not installed".
I am running Android 8.0.0 on a Galaxy S7

me too.how can i install it?parse error when install it

@leebufan what's the android version are you using?

What error do you get when you try to install the app via adb using adb install app.apk?

probably because playstore protection


Json data not working while rss is working

hi,
there is an issue with json data , when i am using an endpoint to send rss its working fine, with json its not, find below my code for rss and json, i am fairly new to mautic. I'll appreciate any help or feedback.
one of the finding is that my json endpoint is not getting hit at all with my code below
working rss
 {% TWIG_BLOCK %}
          {% set items = 'http://<IP_ADDRESS>:3009/rss' | rss %}

          {% for item in items %}

               {{ item.title }}

{{ item.description|raw }}

          {% endfor %}

  {% END_TWIG_BLOCK %}

not working json
 {% TWIG_BLOCK %}
          {% set items = 'http://<IP_ADDRESS>:3009/json' | json_decode %}

          {% for item in items %}

               {{ item.title }}

{{ item.description|raw }}

          {% endfor %}

  {% END_TWIG_BLOCK %}

json payload
[
  {
    "title": "title-0",
    "description": "description-0",
    "feed_url": "http://example.com/rss.xml-0",
    "link": "http://example.com/rss.xml-0",
    "site_url": "http://example.com-0",
    "image_url": "http://example.com/icon.png-0"
  },
  {
    "title": "title-1",
    "description": "description-1",
    "feed_url": "http://example.com/rss.xml-1",
    "link": "http://example.com/rss.xml-1",
    "site_url": "http://example.com-1",
    "image_url": "http://example.com/icon.png-1"
  },
  {
    "title": "title-2",
    "description": "description-2",
    "feed_url": "http://example.com/rss.xml-2",
    "link": "http://example.com/rss.xml-2",
    "site_url": "http://example.com-2",
    "image_url": "http://example.com/icon.png-2"
  },
  {
    "title": "title-3",
    "description": "description-3",
    "feed_url": "http://example.com/rss.xml-3",
    "link": "http://example.com/rss.xml-3",
    "site_url": "http://example.com-3",
    "image_url": "http://example.com/icon.png-3"
  },
  {
    "title": "title-4",
    "description": "description-4",
    "feed_url": "http://example.com/rss.xml-4",
    "link": "http://example.com/rss.xml-4",
    "site_url": "http://example.com-4",
    "image_url": "http://example.com/icon.png-4"
  }
]

seems related to this https://github.com/Logicify/mautic-advanced-templates-bundle/issues/25

i think i am wrong to expect the json url will work as it load file with simplexml_load_file, i will find some other way


Useful to link to download instructions

[Enter feedback here]

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

ID: 4aa0101c-da3b-4681-8646-bfbbc6dba4e4
Version Independent ID: 4aa0101c-da3b-4681-8646-bfbbc6dba4e4
Content: PowerToys File Locksmith utility for Windows
Content Source: hub/powertoys/file-locksmith.md
Product: dev-environment
Technology: powertoys
GitHub Login: @alvinashcraft
Microsoft Alias: aashcraft

Thanks, @ikjordan. I added two "see also" links to the bottom of the page to link to the PowerToys overview and PowerToys install pages. The PR should be live shortly.


Support dotnet publish

My sqlproj looks like this
<Project Sdk="Microsoft.Build.Sql/0.1.15-preview">

    <PropertyGroup>
        <Name>MyDb</Name>
        <DSP>Microsoft.Data.Tools.Schema.Sql.Sql160DatabaseSchemaProvider</DSP>
        <ModelCollation>1033, CI</ModelCollation>
    </PropertyGroup>

</Project>

I'd like to publish the output dacpac to a folder (along with my other projects) for deployment. Using dotnet publish throws an error:
C:\Program Files\dotnet\sdk\8.0.205\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Publish.targets(164,5): error MSB4036:
 The "AllowEmptyTelemetry" task was not found. Check the following: 1.) The name of the task in the project file is the
 same as the name of the task class. 2.) The task class is "public" and implements the Microsoft.Build.Framework.ITask
interface. 3.) The task is correctly declared with <UsingTask> in the project file, or in the *.tasks files located in
the "C:\Program Files\dotnet\sdk\8.0.205" directory. [D:\test\MyDb\MyDb.sqlproj]

Our current proposal for dotnet publish functionality will diverge from the SSDT and original SQL projects msbuild publish capability and I believe aligns with the behavior you expected.  The original SQL projects initiate a DacFx publish operation of the build artifact to a database connection specified in a publish profile. With Microsoft.Build.Sql the plan to align with the default dotnet publish behavior.
https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-publish

dotnet publish compiles the application, reads through its dependencies specified in the project file, and publishes the resulting set of files to a directory.

The dacpac is the build artifact from a Microsoft.Build.Sql project that would be published/copied to the directory.
Applying this dacpac to a database would require the sqlpackage dotnet tool (or another implementation of DacFx publish APIs)

Great to hear - that's exactly what I was hoping you'd say! :)

Is there any information on when this behavior is expected to be implemented?  Glad to hear about the publish functionality to a directory.

@srbrills How is that very different from getting the build output?

It is not very different, true.  I currently just get the build output.  However, it keeps me from being able to use a simpler set of automation tasks in a pipeline.  It would be great if I could just run dotnet publish against each of the projects in a solution, making a build pipeline more simplified, but as it stands now I have to write an extra conditional step for these newer SQL projects.

I just came to look for the same behavior. I'd like to use dotnet publish to put the dacpac file into an output folder, along with any scripts, similar to how it works with out projects.