Refactor codebase

Note this it implements the resolution algorithm correctly. That is known to cause issues (#90)
I also included a demo of some additional detail in wit status. I can remove this from the branch if necessary.
Last thing: the resolve() function depends on being able to clone in workspace_root/.wit when we tell it not to touch the root workspace.

I split up GitRepo into 3 separate classes:

GitRepo: simply manage a package on disk (very little code changed)
Package: what's found in wit-lock.json
Dependency: what's found in wit-workspace.json

I think the best way to visualize this is by looking at a verbose graph of block-pio-sifive: (click to see it up close)

In the above visualization, the boxes are Packages, and the circles are the Dependencies.
The wit-workspace.json along with each wit-manifest.json request a Dependency. As the package resolution algorithm is run, similar Dependencies are group together to point to the same Package. That Package is the version that "won" (i.e. the latest version).
After running the resolution algorithm, we get a list of Packages. We save this list in wit-lock.json. Then, we optionally tell each Package to make its GitRepo checked out to the correct version.
The separation between the 3 classes allows us to do a few things:

Resolve without touching the workspace root (fix #33)
Rename Packages without confusing already-cloned Dependencies expecting the old name (fix #78 #75)
Compare resolved Packages to the GitRepo on disk, telling us exactly what running wit update would do (for wit status)

Since this is a major rewrite and includes the changes made to master since refactor-packages branched off, I don't recommend using the GitHub GUI to merge. Rather, once we reach agreement, I recommend:
git checkout refactor-packages
git merge -s ours master

https://github.com/sifive/wit/pull/96/commits/50dc4a76ad0160f2c6dbda2abb6b2d48ead07b4d
I added a "Damaged Packages" field to wit status to avoid an error that previously occurred (folder not found).

tl;dr there's a bug that needs a small commit to fix, but it's a little complex to explain.
I'll need more time to work on it tomorrow.

Sounds good, thanks for the update!

Sadly, the fix commit (https://github.com/sifive/wit/pull/96/commits/3f86a2ff3b68f090387c34723f226c609b15746d) is much larger than I would have liked, but I think it is necessary.
Previously, I was using Package as a dummy object between a Dependency and a GitRepo. Packages were not meant for this, but I was using them like this anyway.
Packages are now much more explicit about whether they are "resolved" as the winner, allowing us to link same-named Dependencies together without implying that one of those Dependencies is the "winner."
This is explained in the Package docstring:

Packages are the "winner" of several dependencies of the same name.
These "winner" Packages are determined by WorkSpace.resolve and stored in the wit-lock.json
Before we know which dependency "won," we need a Package object to
link these same-named Dependencies together.
This transitive state is indicated by Package.revision == None
We need repo_paths here because we will use it to transform sources we need both for
downloading repos while in the transitive state and for downloading the "winning" git repo

The fixed bug was not previously noticed because it only affected broken workspace afaik

wit inspect crashes if you delete a repo, while wit status does correctly mark it missing.
One minor quibble about the wit status output:
Clean packages:
    freedom-devicetree-tools
    sifive-blocks
    environment-sanmateo-sifive
    api-firrtl-sifive
    api-generator-sifive
    berkeley-hardfloat
    wit
    api-chisel3-sifive
    chisel3
    api-scala-sifive
    block-pio-sifive
    soc-testsocket-sifive
    firrtl
    freedom-metal
    rocket-chip
Dirty packages:
Damaged packages:
    rocket-chip-wake
rocket-chip-wake (missing)

Could it just mention rocket-chip-wake once (indented under "Damaged packages") and put the (missing) there?

wit inspect crashes if you delete a repo, while wit status does correctly mark it missing.

Turns out wit inspect was always crashing, not just when missing a repo.
Fixed by https://github.com/sifive/wit/pull/96/commits/e281c6cb7609da4c840ce317ed82deb60fc52bd1


[CARBONDATA-1742] Fix NullPointerException in SegmentStatusManager

when loadFolderDetailsArray is null ,there is NullPointerException. We should fix it.

@xubo245 this change is already being handled in #1507

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1190/

@akashrn5 ok


Chips init function throws TypeError when there is a label

When initializing a div with the chips class, if there is a label in that div, the init function raises a TypeError. As far as I can tell, this has a quick fix, and I plan to submit a pull request shortly.
Expected Behavior

If there is already a label element present in the chips div, the initialization function should set its for attribute equal to the id of the input element.
Current Behavior

The function _setupLabel() (in the init function) throws a TypeError: this.$label.setAttribute is not a function.

Possible Solution

Chips.$label is created from Chips.$el.find("label"), which returns an array. setAttribute() expects a single element. Since there should only be one label element, it should be safe to set Chips.$label to Chips.$el.find("label")[0].
Steps to Reproduce (for bugs)

See this Codepen
Context

I am hoping to use this for adding tags in an Electron app I'm working on.
Your Environment

Version used: 1.0.0-rc.2 from npm
Browser Name and version: Electron v2.0.8
Operating System and version (desktop or mobile): Manjaro
Link to your project (if appropriate): https://github.com/cranndarach/lifetracker/tree/tags

Merged


I need only text content

Can I download only the text of the channel in html format without any other files?

It's able to scrape and see all the texts of the chat/channel thanks to Telethon, And I think this feature can be implemented.


Implement CocoaPods podspec

CocoaPods podspec implementation would allow to put together iOS & macOS SDK.

Initial implementation done with a6d275e.


Configure HTTP server root

Currently, chomp -s serves files from the project root. However, I would like to be able to specify ./lib as the HTTP server root so that "https://localhost:8080/" maps to "[PROJECT_ROOT]/lib/".

Added in https://github.com/guybedford/chomp/commit/5b9ec643bec09adb198a3d15f0d695b8c0289fa9, with a new:
[server]
  port = 8080
  root = "lib"

configuration as well as a --server-root=lib command-line flag.


Fixes from integration on an embedded target

These are some changes I did when integrating this library on an embedded target - they were needed because of compilation errors after I turned off a few options to reduce the code size.

Thanks
I will also merge these changes to upcomming version v6 (branch v6_WorkInProgress)
#if OPTION_ problems should are already fixed in this branch

Hello,
you are right. I will fix it.
Regards
Rainer
From: qichenxu @.>
Sent: Thursday, October 6, 2022 5:40 PM
To: vectorgrp/XCPlite @.>
Cc: Zaiser, Rainer @.>; State change @.>
Subject: Re: [vectorgrp/XCPlite] Fixes from integration on an embedded target (PR #29)
Hello I got LNK2019 unresolved external symbol loadFile referenced in function ApplXcpGetId and LNK11201 unresolved externals C_Demo error when building either C_Demo or CPP_Demo code using VS2019. It seems adding #include "xcp_cfg.h" to util.c would fix this problem.
The build was OK with previous commits. Would you take a look? Not sure if it's my compiler settings?
—
Reply to this email directly, view it on GitHubhttps://github.com/vectorgrp/XCPlite/pull/29#issuecomment-1270290556, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABAJOU43GUHYPP7MIVUIBG3WB3XGTANCNFSM6AAAAAAQVV34NQ.
You are receiving this because you modified the open/close state.Message ID<EMAIL_ADDRESS>


Does CodeCombat have an opinion on the future of Coffeescript?

Hi guys,
A quick heads up that there's a pretty active discussion going on over at coffeescript6/discuss about possible next steps for Coffeescript.
Thought you might want to comment, given CodeCombat is a heavy Coffeescript user. Discussed issues are here.
There's also a survey that's relevant to you: Survey for devs/teams with maintained Coffescript codebases: happy with CS, or considering migrating?

Cool! I commented on the survey issue; hope this helps. Will leave this open in case others want to chime in or get informed.

@nwinter thanks! Do you know of any other teams with big maintained Coffeescript codebases? I'd like to make them aware of the survey. CodeCombat was the first big team/project I thought of.

Nah, I haven't really been following any.


Bump to version 0.7.0

This change includes some heavy refactoring. Language dependency is scrapped, rather than that now the more reliable hrDeviceStatus value is used. The display information (statusX) is concatenated and returned on demand via device_status_details

Hello @nielstron! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file pysyncthru/__init__.py:

Line 67:80: E501 line too long (83 > 79 characters)
Line 79:80: E501 line too long (105 > 79 characters)
Line 117:80: E501 line too long (84 > 79 characters)
Line 124:80: E501 line too long (87 > 79 characters)
Line 125:80: E501 line too long (83 > 79 characters)


feat(CX-3273): Remove Phone validation in SWA form

This PR resolves CX-3273
Description

Removes the phone number validation in the SWA form

PR Checklist

[x] I tested my changes on iOS / Android.
[x] I added screenshots or videos to illustrate my changes.
[x] I added Tests and Stories for my changes.
[ ] I added an app state migration.
[ ] I hid my changes behind a feature flag.
[ ] I have prefixed changes that need to be tested during a release QA with [NEEDS EXTERNAL QA] on the changelog.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

Remove Phone validation in SWA form - kizito

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

wait, does this screenshot say "kizito"? 😝😝

but on a serious note, so we have a ticket to fix this in the right way? or are we disabling this forever?

wait, does this screenshot say "kizito"? 😝😝

😂😂😂😂

but on a serious note, so we have a ticket to fix this in the right way? or are we disabling this forever?

@pvinis Yeah, the Consignment team has indicated that it is not useful for them at this time or until the fix is ready.

right. what im asking is if there is a ticket to wait on. good that we disable it, but lets have a ticket to fix this, and it can be prioritized for whenever/never.


We need command line parameter!!!

steameand
What about some developer friendly tools, like command-line arguments, debugging tools?

Great idea! Stuff for helping with the development of custom sprites? Debugging tools, also is a great idea.

I'm working on a debug menu within the program, so I don't plan on adding command line arguments to the program. If I ever see the need for them though I'll be sure to reopen this issue!

Why did I ever reopen this? I still plan on having a embedded debug menu


OAuthSessionDataCache Entries are Not Cleared

Entries stored in the IDN_AUTH_TEMP_SESSION_STORE with the SESSION_TYPE of OAuthSessionDataCache are not getting cleared as expected. We ran a long-running test with IS 5.8.0 beta3 pack and after 15 hours, the following number of records were left on IDN_AUTH_TEMP_SESSION_STORE table.
+----------------------------+----------+
| SESSION_TYPE               | count(*) |
+----------------------------+----------+
| AuthenticationContextCache |       20 |
| AuthenticationResultCache  |        6 |
| OAuthSessionDataCache      |    29909 |
| SAMLSSOSessionDataCache    |       12 |
+----------------------------+----------+

OAuthSessionDataCache entries are created during authorization code and implicit flows. Ideally with our improved cleanup logic if they were deleted at the end of the request they would not remain in the IDN_AUTH_TEMP_SESSION_STORE.
So it is most probable that the code does not clear these cache entries at the end of the request.

@JKAUSHALYA @madurangasiriwardena
Any plans to improve the logic , i faced similar issue from table IDN_AUTH_TEMP_SESSION_STORE which i mentioned in this issue ,https://github.com/wso2/product-is/issues/7392,

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Case insensitive login with Postgre not working ?

Hi,
I setup fos_user + jwt on my symfony project and evertyhing is working fine except for a weird case.
On my dev env, if I try to login with different variation (with all lowercase, all upercase, one upercase, etc.) of one user email address, it works fine.
But on my integration/prod envs, it's giving me 'Bad credentials' if I do not provide the email address with the exact case.
The only difference between the envs is the database. I'm running mysql on local, and postgre on integration/prod.
Could it be the problem ?
Thanks in advance for your help,
Julien

Hey, the issue indeed comes from the different RDBMS used across your environments.
https://wiki.postgresql.org/wiki/Things_to_find_out_about_when_moving_from_MySQL_to_PostgreSQL says:

PostgreSQL is case-sensitive for string comparisons. The field "Smith" is not the same as the field "smith". This is a big change for many users from MySQL [...]

This difference between your environments does not seem sane, I'd suggest to choose one that you can use in all environments.


Backend full HTTPS

All endpoints of cool-maze.appspot.com should refuse HTTP

See the "secure: always" lines in app.yaml.


Tilde paths are not interpreted (e.g. ~/.yarn/bin) by uv_spawn

Version: 1.42.0 (or whatever version is in NeoVim 0.6.1)
Platform: Linux thinkpad-t490s 5.15.11 #1-NixOS SMP Wed Dec 22 08:32:52 UTC 2021 x86_64 GNU/Linux

I'm using the LSP server in NeoVim, and couldn't get it to work. It turns out that the language server binary path in my PATH variable was using tilde paths (e.g. ~/.yarn/bin) and according to NeoVim IRC at Libera, they mentioned that uv_spawn doesn't support tilde paths.

Tilde expansion is a feature of the shell, not of execve(). The latter is the primitive underlying uv_spawn().
Instead of calling (pseudo syntax):
uv_spawn("~/.yarn/bin/lsp", ["script.js"]);

Call:
uv_spawn("/bin/sh", ["~/.yarn/bin/lsp", "script.js"]);


remove dead coins

I used 2 things as criteria to remove:

Coin existed on CoinmarketCap
Coin had data on Coinmarketcap
Ranked higher than 500 on CoinmarketCap

LGTM


Possibility to add some fixers / preset tags directly through the bridge

To avoid array_merge usage like this: https://github.com/Soullivaneuh/php-cs-fixer-styleci-bridge/blob/f7d86d817843ada57948723e9a4cb14c32a3a490/README.md#psr-0-special-case

psr0 IS supported by StyleCI?

It's just not included in the presets anymore.

psr0 IS supported by StyleCI

Oh, I misunderstood that. I was thinking you completely removed it.
So if I do this:
preset: none

enabled:
  - psr0

This will works?

Yes.

Or, just disabling psr4 on any of the other presets and enabling psr0.

Like:
preset: recommended

disabled:
  - psr4

enabled:
  - psr0

Notice if you look on our fixer docs, we still list it as a fixer. :)

And it's still in the VALID constant.

Ok I see, thanks for the precision. :+1:
I'll update the documentation ASAP.

@GrahamCampbell Last question:
preset: symfony

disabled:
  - psr0

Will this work? Because PHP-CS-Fixer' Symfony preset enable psr0 AFAIK.

ping @GrahamCampbell


(PUP-5569) acceptance: use Set for mk_tmp_environment instead of SortedSet

This change uses Set instead of SortedSet which requires external gems
and could be actually slower in many cases than searching a Set which is
a valueless hash in ruby.
[skip ci]

small change reviewed by @hlindberg.  self-merging


stack-buffer-overflow during do_read_client_key_exchange

Description:
I have an asan stack for a crash we get fairly often with envoy v1.8.0.  We have active health checking enabled for the cluster, I've seen the crash with http2 and grpc. It looks like the buffer has a length of 0 at the point it's written to, but unfortunately I haven't managed to narrow it down very much.
=================================================================
 ==6==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7f544cddc9e0 at pc 0x7f545a435904 bp 0x7f544cddc200 sp 0x7f544cddb9a8
 WRITE of size 32 at 0x7f544cddc9e0 thread T11
     #0 0x7f545a435903 in __asan_memcpy (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x8c903)
     #1 0x27ab330 in OPENSSL_memcpy external/boringssl/src/crypto/fipsmodule/../internal.h:705
     #2 0x2835686 in ecp_nistz256_windowed_mul external/boringssl/src/crypto/fipsmodule/ec/p256-x86_64.c:216
     #3 0x2836556 in ecp_nistz256_points_mul external/boringssl/src/crypto/fipsmodule/ec/p256-x86_64.c:354
     #4 0x281d271 in ec_point_mul_scalar external/boringssl/src/crypto/fipsmodule/ec/ec.c:909
     #5 0x281cd29 in EC_POINT_mul external/boringssl/src/crypto/fipsmodule/ec/ec.c:866
     #6 0x26d20ee in Finish external/boringssl/src/ssl/ssl_key_share.cc:109
     #7 0x2707d2b in do_read_client_key_exchange external/boringssl/src/ssl/handshake_server.cc:1154
     #8 0x270b791 in bssl::ssl_server_handshake(bssl::SSL_HANDSHAKE*) external/boringssl/src/ssl/handshake_server.cc:1528
     #9 0x2721d4f in bssl::ssl_run_handshake(bssl::SSL_HANDSHAKE*, bool*) external/boringssl/src/ssl/handshake.cc:631
     #10 0x264c04a in SSL_do_handshake external/boringssl/src/ssl/ssl_lib.cc:902
     #11 0x17cdb9f in Envoy::Ssl::SslSocket::doHandshake() source/common/ssl/ssl_socket.cc:118
     #12 0x17cf4a0 in Envoy::Ssl::SslSocket::doWrite(Envoy::Buffer::Instance&, bool) source/common/ssl/ssl_socket.cc:169
     #13 0x17a76ff in Envoy::Network::ConnectionImpl::onWriteReady() source/common/network/connection_impl.cc:529
     #14 0x17a59a8 in Envoy::Network::ConnectionImpl::onFileEvent(unsigned int) source/common/network/connection_impl.cc:464
     #15 0x1798a63 in operator() source/common/network/connection_impl.cc:64
     #16 0x17ada85 in _M_invoke /usr/include/c++/5/functional:1871
     #17 0x177a96d in std::function<void (unsigned int)>::operator()(unsigned int) const /usr/include/c++/5/functional:2267
     #18 0x177856d in Envoy::Event::FileEventImpl::assignEvents(unsigned int)::{lambda(int, short, void*)#1}::operator()(int, short, void*) const (/usr/local/bin/envoy+0x177856d)
     #19 0x1778663 in Envoy::Event::FileEventImpl::assignEvents(unsigned int)::{lambda(int, short, void*)#1}::_FUN(int, short, void*) (/usr/local/bin/envoy+0x1778663)
     #20 0x2b8c214 in event_persist_closure ../event.c:1580
     #21 0x2b8c214 in event_process_active_single_queue ../event.c:1639
     #22 0x2b8c95e in event_process_active ../event.c:1738
     #23 0x2b8f6e7 in event_base_loop ../event.c:1961
     #24 0x1767b4d in Envoy::Event::DispatcherImpl::run(Envoy::Event::Dispatcher::RunType) source/common/event/dispatcher_impl.cc:161
     #25 0x172ebf9 in Envoy::Server::WorkerImpl::threadRoutine(Envoy::Server::GuardDog&) source/server/worker_impl.cc:94
     #26 0x172d4ca in Envoy::Server::WorkerImpl::start(Envoy::Server::GuardDog&)::{lambda()#1}::operator()() const (/usr/local/bin/envoy+0x172d4ca)
     #27 0x1730387 in _M_invoke /usr/include/c++/5/functional:1871
     #28 0x6f875b in std::function<void ()>::operator()() const /usr/include/c++/5/functional:2267
     #29 0x2b9e9e2 in operator() source/common/common/thread.cc:21
     #30 0x2b9ea0c in _FUN source/common/common/thread.cc:23
     #31 0x7f5459d876b9 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x76b9)
     #32 0x7f5458aa741c in clone (/lib/x86_64-linux-gnu/libc.so.6+0x10741c)

 Address 0x7f544cddc9e0 is located in stack of thread T11 at offset 1824 in frame
     #0 0x2835484 in ecp_nistz256_windowed_mul external/boringssl/src/crypto/fipsmodule/ec/p256-x86_64.c:203

   This frame has 4 object(s):
     [1856, 1857) 'p_str' <== Memory access at offset 1824 underflows this variable
     [256, 1792) 'table'
     [128, 224) 'h'
     [64, 96) 'tmp'
 HINT: this may be a false positive if your program uses some custom stack unwind mechanism or swapcontext
       (longjmp and C++ exceptions *are* supported)

 Thread T11 created by T0 here:
     #0 0x7f545a3df253 in pthread_create (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x36253)
     #1 0x2b9ed3c in Envoy::Thread::Thread::Thread(std::function<void ()>) source/common/common/thread.cc:24
     #2 0x172d805 in Envoy::Server::WorkerImpl::start(Envoy::Server::GuardDog&) source/server/worker_impl.cc:67
     #3 0x15f6045 in Envoy::Server::ListenerManagerImpl::startWorkers(Envoy::Server::GuardDog&) source/server/listener_manager_impl.cc:916
     #4 0x15984d6 in Envoy::Server::InstanceImpl::startWorkers() source/server/server.cc:343
     #5 0x159c4a7 in Envoy::Server::InstanceImpl::run()::{lambda()#1}::operator()() const (/usr/local/bin/envoy+0x159c4a7)
     #6 0x15a4125 in _M_invoke /usr/include/c++/5/functional:1871
     #7 0x6f875b in std::function<void ()>::operator()() const /usr/include/c++/5/functional:2267
     #8 0x159aace in Envoy::Server::RunHelper::RunHelper(Envoy::Event::Dispatcher&, Envoy::Upstream::ClusterManager&, Envoy::Server::HotRestart&, Envoy::AccessLog::AccessLogManager&, Envoy::Server::InitManagerImpl&, Envoy::Server::OverloadManager&, std::function<void ()>)::{lambda()#4}::operator()() const::{lambda()#1}::operator()() const (/usr/local/bin/envoy+0x159aace)
     #9 0x15a147e in _M_invoke /usr/include/c++/5/functional:1871
     #10 0x6f875b in std::function<void ()>::operator()() const /usr/include/c++/5/functional:2267
     #11 0x20e673f in Envoy::Server::InitManagerImpl::initialize(std::function<void ()>) source/server/init_manager_impl.cc:13
     #12 0x159b069 in operator() source/server/server.cc:428
     #13 0x15a17e1 in _M_invoke /usr/include/c++/5/functional:1871
     #14 0x6f875b in std::function<void ()>::operator()() const /usr/include/c++/5/functional:2267
     #15 0x19223f0 in Envoy::Upstream::ClusterManagerInitHelper::maybeFinishInitialize() source/common/upstream/cluster_manager_impl.cc:138
     #16 0x1921199 in Envoy::Upstream::ClusterManagerInitHelper::removeCluster(Envoy::Upstream::Cluster&) source/common/upstream/cluster_manager_impl.cc:91
     #17 0x192085d in Envoy::Upstream::ClusterManagerInitHelper::onClusterInit(Envoy::Upstream::Cluster&) source/common/upstream/cluster_manager_impl.cc:68
     #18 0x191f60a in Envoy::Upstream::ClusterManagerInitHelper::addCluster(Envoy::Upstream::Cluster&)::{lambda()#1}::operator()() const (/usr/local/bin/envoy+0x191f60a)
     #19 0x1949ca9 in _M_invoke /usr/include/c++/5/functional:1871
     #20 0x6f875b in std::function<void ()>::operator()() const /usr/include/c++/5/functional:2267
     #21 0x1f06160 in Envoy::Upstream::ClusterImplBase::finishInitialization() source/common/upstream/upstream_impl.cc:617
     #22 0x1f05365 in Envoy::Upstream::ClusterImplBase::onInitDone()::{lambda(std::shared_ptr<Envoy::Upstream::Host>, Envoy::Upstream::HealthTransition)#1}::operator()(std::shared_ptr<Envoy::Upstream::Host>, Envoy::Upstream::HealthTransition) const (/usr/local/bin/envoy+0x1f05365)
     #23 0x1f1b432 in _M_invoke /usr/include/c++/5/functional:1871
     #24 0x209b4bb in std::function<void (std::shared_ptr<Envoy::Upstream::Host>, Envoy::Upstream::HealthTransition)>::operator()(std::shared_ptr<Envoy::Upstream::Host>, Envoy::Upstream::HealthTransition) const /usr/include/c++/5/functional:2267
     #25 0x208e225 in Envoy::Upstream::HealthCheckerImplBase::runCallbacks(std::shared_ptr<Envoy::Upstream::Host>, Envoy::Upstream::HealthTransition) source/common/upstream/health_checker_base_impl.cc:141
     #26 0x2090b9e in Envoy::Upstream::HealthCheckerImplBase::ActiveHealthCheckSession::handleSuccess() source/common/upstream/health_checker_base_impl.cc:223
     #27 0x204ca8f in Envoy::Upstream::HttpHealthCheckerImpl::HttpActiveHealthCheckSession::onResponseComplete() source/common/upstream/health_checker_impl.cc:201
     #28 0x2060881 in Envoy::Upstream::HttpHealthCheckerImpl::HttpActiveHealthCheckSession::decodeData(Envoy::Buffer::Instance&, bool) (/usr/local/bin/envoy+0x2060881)
     #29 0x1e91d23 in Envoy::Http::StreamDecoderWrapper::decodeData(Envoy::Buffer::Instance&, bool) bazel-out/k8-dbg/bin/source/common/http/_virtual_includes/codec_wrappers_lib/common/http/codec_wrappers.h:35
     #30 0x230402f in Envoy::Http::Http2::ConnectionImpl::onFrameReceived(nghttp2_frame const*) source/common/http/http2/codec_impl.cc:436
     #31 0x2309c4b in operator() source/common/http/http2/codec_impl.cc:705
     #32 0x2309c80 in _FUN source/common/http/http2/codec_impl.cc:706
     #33 0x232c836 in session_call_on_frame_received ../lib/nghttp2_session.c:3295
     #34 0x232c836 in nghttp2_session_on_data_received ../lib/nghttp2_session.c:4941
     #35 0x2330a01 in session_process_data_frame ../lib/nghttp2_session.c:4961
     #36 0x2330a01 in nghttp2_session_mem_recv ../lib/nghttp2_session.c:6581
     #37 0x2300ce6 in Envoy::Http::Http2::ConnectionImpl::dispatch(Envoy::Buffer::Instance&) source/common/http/http2/codec_impl.cc:296
     #38 0x20a779c in Envoy::Http::CodecClient::onData(Envoy::Buffer::Instance&) source/common/http/codec_client.cc:115
     #39 0x20ac0d5 in Envoy::Http::CodecClient::CodecReadFilter::onData(Envoy::Buffer::Instance&, bool) bazel-out/k8-dbg/bin/source/common/http/_virtual_includes/codec_client_lib/common/http/codec_client.h:162
     #40 0x17c3f6e in Envoy::Network::FilterManagerImpl::onContinueReading(Envoy::Network::FilterManagerImpl::ActiveReadFilter*) source/common/network/filter_manager_impl.cc:56
     #41 0x17c42d5 in Envoy::Network::FilterManagerImpl::onRead() source/common/network/filter_manager_impl.cc:66
     #42 0x17a0bcb in Envoy::Network::ConnectionImpl::onRead(unsigned long) source/common/network/connection_impl.cc:261
     #43 0x17a6506 in Envoy::Network::ConnectionImpl::onReadReady() source/common/network/connection_impl.cc:494
     #44 0x17a5ae2 in Envoy::Network::ConnectionImpl::onFileEvent(unsigned int) source/common/network/connection_impl.cc:470
     #45 0x1798a63 in operator() source/common/network/connection_impl.cc:64
     #46 0x17ada85 in _M_invoke /usr/include/c++/5/functional:1871
     #47 0x177a96d in std::function<void (unsigned int)>::operator()(unsigned int) const /usr/include/c++/5/functional:2267
     #48 0x177856d in Envoy::Event::FileEventImpl::assignEvents(unsigned int)::{lambda(int, short, void*)#1}::operator()(int, short, void*) const (/usr/local/bin/envoy+0x177856d)
     #49 0x1778663 in Envoy::Event::FileEventImpl::assignEvents(unsigned int)::{lambda(int, short, void*)#1}::_FUN(int, short, void*) (/usr/local/bin/envoy+0x1778663)
     #50 0x2b8c214 in event_persist_closure ../event.c:1580
     #51 0x2b8c214 in event_process_active_single_queue ../event.c:1639
     #52 0x2b8c95e in event_process_active ../event.c:1738
     #53 0x2b8f6e7 in event_base_loop ../event.c:1961
     #54 0x1767b4d in Envoy::Event::DispatcherImpl::run(Envoy::Event::Dispatcher::RunType) source/common/event/dispatcher_impl.cc:161
     #55 0x159cd05 in Envoy::Server::InstanceImpl::run() source/server/server.cc:455
     #56 0x48070d in Envoy::MainCommonBase::run() source/exe/main_common.cc:99
     #57 0x42e94b in Envoy::MainCommon::run() (/usr/local/bin/envoy+0x42e94b)
     #58 0x41b6d6 in main source/exe/main.cc:37
     #59 0x7f54589c082f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2082f)

 SUMMARY: AddressSanitizer: stack-buffer-overflow ??:0 __asan_memcpy
 Shadow bytes around the buggy address:
   0x0feb099b38e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
   0x0feb099b38f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
   0x0feb099b3900: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
   0x0feb099b3910: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
   0x0feb099b3920: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 =>0x0feb099b3930: 00 00 00 00 00 00 00 00 f2 f2 f2 f2[f2]f2 f2 f2
   0x0feb099b3940: 01 f4 f4 f4 f3 f3 f3 f3 00 00 00 00 00 00 00 00
   0x0feb099b3950: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
   0x0feb099b3960: 00 00 00 00 f1 f1 f1 f1 00 00 00 00 00 00 00 00
   0x0feb099b3970: 00 00 00 00 f2 f2 f2 f2 00 00 00 00 00 00 00 00
   0x0feb099b3980: 00 00 00 00 f2 f2 f2 f2 00 00 00 00 01 f4 f4 f4
 Shadow byte legend (one shadow byte represents 8 application bytes):
   Addressable:           00
   Partially addressable: 01 02 03 04 05 06 07
   Heap left redzone:       fa
   Heap right redzone:      fb
   Freed heap region:       fd
   Stack left redzone:      f1
   Stack mid redzone:       f2
   Stack right redzone:     f3
   Stack partial redzone:   f4
   Stack after return:      f5
   Stack use after scope:   f8
   Global redzone:          f9
   Global init order:       f6
   Poisoned by user:        f7
   Container overflow:      fc
   Array cookie:            ac
   Intra object redzone:    bb
   ASan internal:           fe
==6==ABORTING

@PiotrSikora any thoughts on this?

This may be a separate issue and the version I'm currently running is v1.7.1.
The active health checks are h2 (or gRPC), I've noticed that there are multiple connections to the upstream (cx_active) and in that scenario we can get quite a few 5xx back.
If the upstream is h2, shouldn't there be only one cx_active (per host, per cluster)?  Most of our other services behave and all have 1.  Is it possible that a disconnection/reconnection during a health check causes this scenario? Are buffers moved in this scenario?
Could it be related to this: https://github.com/envoyproxy/envoy/issues/3877#issuecomment-413532713 ? I would note that I have currently have a local hack to check the client for nil before attempting to close it, which may be causing the multiple connections. I was never happy with that hack, and didn't have a repro or test, so I never attempted to upstream it.

I just test envoy v1.8.0 and also see multiple cx_active per h2 cluster node.

@mattklein123 sorry, no idea :(
@davidben does this look familiar at all (see first post)? v1.8.0 shipped with https://github.com/google/boringssl/commit/c7db3232c397aa3feb1d474d63a1c4dd674b6349 (i.e. chromium-69.0.3497.81).

That looks like a compiler bug. Here is the code in question:
https://github.com/google/boringssl/blob/c7db3232c397aa3feb1d474d63a1c4dd674b6349/crypto/fipsmodule/ec/p256-x86_64.c#L215-L216
p_str is pretty solidly a 33-byte buffer and the memcpy within bounds. The error says:
   This frame has 4 object(s):
     [1856, 1857) 'p_str' <== Memory access at offset 1824 underflows this variable
     [256, 1792) 'table'
     [128, 224) 'h'
     [64, 96) 'tmp'

1857 - 1856 is 1, not 33. It seems your compiler's ASan implementation is getting the size of that object wrong. Indeed I'll note that 1857 - 1824 = 33, the correct size of the buffer. So the correct bounds of p_str is [1824, 1856).
What compiler and version are you using? I vaguely recall seeing an ASan bug around here that was fixed in GCC, but I can't find it off-hand.

Interesting. I used envoyproxy/envoy-build:2029afbb36cd1e81340d85e665c68f26fca8355c as build and run container. When I made the release, latest was failing the link step that used ld to write the build version.


Fixes some mypy/pylint issues

Finally I can drop the grep -v "Unused type ignore comment" when running mypy locally ;)

Yes, me too.

currently, it looks like it's just running/reporting results as if executed locally.

However, there is still a issue with ReviewDog that it shows the findings X times instead of once. Which seems to be a bug with review dog as far as I can tell because the underlying tool pylint only reports the error/warning once. :rofl:


If reader remains connected, payment cannot be processed due to expired connection token

Describe the bug
After leaving the app for a while, without disconnecting a reader, calling processPayment results in an error:
Error: Could not process payment (code: SessionExpired): Expired API Key provided: pss_test_YW*********************************************************************_******NCBG. Platform access may have been revoked.

To Reproduce
Steps to reproduce the behavior:

Initialise the terminal SDK, discover a reader and connect to it
Wait for a while (not exactly sure how long - 60 mins or so? But could be shorter)
Call retrievePaymentIntent to fetch a payment intent
Call collectPayment, scan a card on the device
Call processPayment

Expected behavior
The connection token should be automatically refreshed as it has expired. Instead, an error is returned after calling processPayment.
Stripe Terminal React Native SDK version

0.0.1-beta.13

Smartphone (please complete the following information):

Device: iPad 10th generation
OS: iOS 16.4

Additional context
Since we supply a fetchTokenHandler to the StripeTerminalProvider, I was anticipating that the SDK would handle the lifecycle of the connection token. Perhaps I am doing something wrong. Under what circumstances will the SDK fetch a new token?

Hi @ts-candide -- thanks for the report here. We have fixed this issue in the underlying native iOS SDK, and we are working to update the ReactNative SDK to depend on the latest iOS SDK version.
The next RN SDK release should fix this issue, and we'll let you know when it's ready.

Thank you for the reply @billfinn-stripe
I notice that the current version released to npm (0.0.1-beta.13) is targeting v2.23.1 of the underlying iOS SDK. This issue is a bit of a dealbreaker for us adopting the Stripe terminal. Do you have any idea when a new version based on v3 of the iOS SDK will be available?
In the meantime, would you advocate for us pointing to the main branch as this appears to target the newer SDK?

In the meantime, would you advocate for us pointing to the main branch as this appears to target the newer SDK?

That would be great to confirm that the main branch picking up the latest iOS SDK does, in fact, fix your issue. I'm fairly sure it will, but in case it does not, can you provide your reader serial number, reproduce the problem, and a timestamp in UTC for when you encountered the most recent instance of the problem?

Hi, I haven't tested with the main branch yet, I will wait now until the new version has dropped.

Unfortunately the project I was working on has been shelved in the short term, so it's unlikely I will be able to perform any more testing on this issue.

@ts-candide sorry to hear that 😕 I am going to close the issue as resolved with the new release, feel free to reopen if someone runs into it still


Add a dbt package and a meltano transform for tap-salesforce

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/362
Originally created by @iroussos on 2019-02-07 15:45:19

Relevant discussion on undefined##undefined
Follows the conclusion of undefined##undefined

[x]  Create a new project meltano/dbt-tap-salesforce as the core dbt package used in Meltano for tap-salesforce and add the models we'll agree in undefined##undefined.
[x]  Add tap-salesforce transform to Meltano

View 9 previous comments from the original issue on GitLab


Docker tag strict pattern disallows semver.

Description
Docker tag is enforcing a strict pattern on the tag names:

A tag name may contain lowercase and uppercase characters, digits, underscores, periods and dashes. A tag name may not start with a period or a dash and may contain a maximum of 128 characters.

This prevents users to tag with the de-facto standard: semver, as semver 2.0 can potentially use a '+' character to include metadata.
Steps to reproduce the issue:
1.
docker tag 1fa4b226ec62 1.0.0-alpha+001
Describe the results you received:
Error parsing reference: "1.0.0-alpha+001" is not a valid repository/tag
Describe the results you expected:
Return code 0.
Additional information you deem important (e.g. issue happens only occasionally):
Happens every time.
Output of docker version:
Client:
 Version:      1.12.2-rc1
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   45bed2c
 Built:        Tue Sep 27 23:38:15 2016
 OS/Arch:      darwin/amd64
 Experimental: true

Server:
 Version:      1.12.2-rc1
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   45bed2c
 Built:        Tue Sep 27 23:38:15 2016
 OS/Arch:      linux/amd64
 Experimental: true

Output of docker info:
Containers: 5
 Running: 0
 Paused: 0
 Stopped: 5
Images: 81
Server Version: 1.12.2-rc1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 79
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.4.22-moby
Operating System: Alpine Linux v3.4
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 1.952 GiB
Name: moby
ID: GMUV:VFBH:VPNG:VPSB:HIZE:CV37:XVXC:QU22:VHLC:UEZF:AMSH:MUAA
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 15
 Goroutines: 27
 System Time: 2016-10-10T23:57:23.513758787Z
 EventsListeners: 1
No Proxy: *.local, 169.254/16
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
 <IP_ADDRESS>/8

Additional environment details (AWS, VirtualBox, physical, etc.):
MacOSX

Thanks for reporting, looks like this is a duplicate of https://github.com/docker/docker/issues/18168, which is being discussed in https://github.com/docker/distribution/issues/1201, and https://github.com/docker/distribution/pull/1202. I'll close this issue to keep the discussion central, but feel free to comment after I closed

Apologies, I searched extensively but somehow I didn't find the previous issue although it has almost the exact same title :S

@vromero no need to apologize, GitHub search is notoriously bad


Update contributing guide for project based on community landing page

Issue description / feature objectives
The README.md for the compliance-trestle leg of oscal-compass should be commensurate with the community landing page at https://github.com/oscal-compass/community
Caveats / Assumptions
The community page comprises contributions guidelines and such. Link from compliance-trestle to community page as appropriate.
Completion Criteria
Any duplicated/conflicting info is eliminated from compliance trestle repo.

This issue is pending updates to the organization level community page

This is still needed


feat(desktop): adding tray util for wallet sync

moves desktop ui out and just adds basic sync tool

this is going to be so easy i think. biggest unknown for me is what to do with the selected target folder for photo syncing, but i'm sure you guys know a way there.


Feature/update nextjs to 12.2

Nextjs 12.2 upgrade/migration for the sample app template and the nextjs package.
Description / Motivation
12.2 release has some updates for middleware as well as improved react 18 compatibility. This PR follows the migration steps and also switches the sample app from babel to swc.
Testing Details
Just manual testing so far.
Types of changes

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

fwiw, we updated our app at the beginning of the week and noticed that ISR has a minor issue:
https://github.com/vercel/next.js/issues/38130 which luckily has been fixed by a canary release later on https://github.com/vercel/next.js/pull/38136.
However, they did fix the beforeInteractive behaviour when using a custom _document (as in, the script actually gets inserted :) )


Design a consistent way to display address on the send  flow

@mica000 is this ready for integration?

https://www.figma.com/file/OSQocEEJnfcMkniEl8u3U8/%231483---Initial-Bitcoin-support?node-id=1101-56854&t=aN1XBe9LZW9tw8mp-4


How to use without a GPU?

I'm running wolf in docker on a Debian host with no GPU (neither dedicated card nor onboard graphics). I'm running the  compose file from the docs and getting the following error when running anything other than the Test ball app (which runs fine):
wolf  | 19:53:22.294313227 DEBUG | Host app state folder: /etc/wolf/1143853187824259421/RetroArch, creating paths
wolf  | 19:53:22.294370926 DEBUG | [STREAM_SESSION] Create wayland compositor
wolf  | 19:53:22.294385935 DEBUG | [WAYLAND] Creating wayland display
wolf  | 2024-11-25T19:53:22.296720Z ERROR libgstwaylanddisplay: Failed to create wayland display. err=Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })

Should this be working for my setup, is there extra config I need in my compose file or host?

Thank you for the speedy reply, much appreciated. Worked a treat 👍


validators can burn their funds

Codecov Report

Merging #329 (248bae7) into master (d9f159f) will increase coverage by 0.17%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #329      +/-   ##
==========================================
+ Coverage   66.90%   67.07%   +0.17%
==========================================
  Files          55       55
  Lines       16633    16694      +61
==========================================
+ Hits        11128    11198      +70
+ Misses       5505     5496       -9

Impacted Files
Coverage Δ

pallets/staking/src/lib.rs
68.75% <100.00%> (+0.64%)
:arrow_up:

pallets/staking/src/tests.rs
99.89% <100.00%> (+<0.01%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Added a ValidatorBurned event, added more tests. ready to review.


💡 [REQUEST] - <Adding separated section in the the resources for blog,docs,website and videos>

[x] I am from GSSoC23.
[x] I would like to be assigned this task.

Section
Description

Separation
I want to create separate section for blog/docs/website/youtube videos for every resources

Additional Text
Just like how in the screen-shot I have provided, I want to make 3 sections here and add the docs,blogs,websites in their respective sections and want to add youtube videos also for web-dev resources

Screenshots

Code of Conduct
By submitting this issue, you agree to follow our Code of Conduct.

[x] I follow the Contributing Guidelines of this project.
[x] I have checked the current issues for duplicate problems.
[x] I have read the readme of this repository.

I would like to work on this, Please assign it to me

@Soumyajit2825 can you please provide a reference for the UI which you wanted to create?