Cookie/crumb issues after about 10-20 minutes

Originally posted by @samducker in https://github.com/gadicc/node-yahoo-finance2/issues/736#issuecomment-1959844563

Hi its working on restart of my server, but then seems to stop working within 10-20mins.
My server is based in US EAST. How can I force the cookie to renew on each request?
Is there a way to force cookie refresh if I get an error like this?
I am running a honojs server on railway with no serverless (its constantly running). Naturally storing the cookie in a volume, doesn't seem to make any sense if I'm needing to refresh the cookie.

with followup:

No worries thank you for this library and your amazing work @gadicc I felt bad to tag :D, but I have a client on my back.
In the meantime I introduced a caching solution on my end which has limited the impact of my problem. So no worries, enjoy the weekend.
Happy to follow up with my sentry logs if helpful.
p.s. I am happy to submit a PR, if you can point me in the right direction also <3!

Thanks @samducker for your reply.  Glad you were able to mitigate the impact somewhat, but yes, let's try solve this properly.
Yes, the full logs would be great... maybe it will give me an indication of where things are getting stuck.  In the meantime, going to share a bit about the insides in case you want to take a look too.
The relevant code is in src/lib/getCrumb.ts, and actually on L36-40 we have:
  if (crumb && !noCache) {
    // If we still have a valid (non-expired) cookie, return the existing crumb.
    const existingCookies = await cookieJar.getCookies(url, { expire: true });
    if (existingCookies.length) return crumb;
  }

Unfortunately noCache option is not exposed in the API and is only used for testing, so no easy workaround there.  The issue is, it really should be noticing that the cookie is expired here, and fetch a new one automatically.  So we'll have to check that too.  I'd like to understand if it's trying to re-use an expired cookie or if something else is going wrong.  I also need to look at the code more carefully and double check what happens to the existing crumb when the cookie is refreshed.
I guess I really need to set up a long running process to track this properly, and will do that when I get the chance.  However, I'd love to give you more options in the meantime.  You could also try manually clearing the cookieJar, someting like:
const yf2 = require('yahoo-finance2').default;

setInterval(() => {
    yf2._opts.cookieJar.removeAllCookiesSync();
}, 60_000 * 10);

and see how that goes, too.  Let's keep in touch.

Not sure if below error is related to the above. Requesting summary data on a fresh started server results in an invalid crumb. I did not yet try the suggestion to empty the cookieJar.
const res = await yahooFinance.quoteSummary(symbol, {
	modules: ['summaryProfile', 'quoteType', 'financialData'],
});

Results in below error.
Fetching crumb and cookies from https://finance.yahoo.com/quote/AAPL...
fetch https://guce.yahoo.com/consent?brandType=nonEu&gcrumb=HaNZK6c&done=https%3A%2F%2Ffinance.yahoo.com%2Fquote%2FAAPL
fetch https://consent.yahoo.com/v2/collectConsent?sessionId=3_cc-session_9b772abd-9720-4015-8db3-f287cffe7253
fetch https://consent.yahoo.com/v2/collectConsent?sessionId=3_cc-session_9b772abd-9720-4015-8db3-f287cffe7253
fetch https://guce.yahoo.com/copyConsent?sessionId=3_cc-session_9b772abd-9720-4015-8db3-f287cffe7253&lang=sv-SE
Fetching crumb and cookies from https://finance.yahoo.com/quote/AAPL?guccounter=1...
Success. Cookie expires on Infinity
New crumb: yRG6Yj2wkbt
Error: Invalid Crumb

Not sure if below error is related to the above. Requesting summary data on a fresh started server results in an invalid crumb. I did not yet try the suggestion to empty the cookieJar.
const res = await yahooFinance.quoteSummary(symbol, {
	modules: ['summaryProfile', 'quoteType', 'financialData'],
});

Results in below error.
Fetching crumb and cookies from https://finance.yahoo.com/quote/AAPL...
fetch https://guce.yahoo.com/consent?brandType=nonEu&gcrumb=HaNZK6c&done=https%3A%2F%2Ffinance.yahoo.com%2Fquote%2FAAPL
fetch https://consent.yahoo.com/v2/collectConsent?sessionId=3_cc-session_9b772abd-9720-4015-8db3-f287cffe7253
fetch https://consent.yahoo.com/v2/collectConsent?sessionId=3_cc-session_9b772abd-9720-4015-8db3-f287cffe7253
fetch https://guce.yahoo.com/copyConsent?sessionId=3_cc-session_9b772abd-9720-4015-8db3-f287cffe7253&lang=sv-SE
Fetching crumb and cookies from https://finance.yahoo.com/quote/AAPL?guccounter=1...
Success. Cookie expires on Infinity
New crumb: yRG6Yj2wkbt
Error: Invalid Crumb

Yeah for me too this issue has been live today

I mitigated the issue by moving to serverless. Meaning essentially a new server / cookie would spawn and also adding a cache infront of my api meaning I made less requests and if a request failed I would still be able to return the previous fetched result.

Hi, all.  Bad news, I'm afraid.  Please see https://github.com/gadicc/node-yahoo-finance2/issues/764 for more info and for our official stance.

@gadicc I believe this issue can be closed now given this fix got released. No?
https://github.com/gadicc/node-yahoo-finance2/issues/764#issuecomment-2061075355

Thanks, @watadarkstar!  As much as I'd love to close this, there are two different issues here.  The original issue is an issue with cookies on long running processes.  The OP moved over to serverless so there hasn't been much further movement on this... I'd love to leave the issue open in case anyone notices this and can provide more input (or if I eventually ever have time to do long running debug sessions :sweat_smile:).
Then there was the more recent crumb issue of last week which through the usual magic of open source collaboration, we managed to solve :)  But that issue is newer than the original issue here, even though it was related.
Nevertheless, thanks for chiming in.  I admit the multitude of issues are a bit overwhelming for me so I do appreciate any help in getting some closed! :pray: :grin:

@gadicc i get this issue after several requests ( sometimes just 1 or 2 ) and with several delay intervals in between if anyone can help ?   Error: No set-cookie header on collectConsentSubmitResponse, please report.
at _getCrumb (webpack-internal:///(rsc)/./node_modules/.pnpm/yahoo-finance2@2.11.2/node_modules/yahoo-finance2/dist/esm/src/lib/getCrumb.js:106:27)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Object.yahooFinanceFetch [as _fetch] (webpack-internal:///(rsc)/./node_modules/.pnpm/yahoo-finance2@2.11.2/node_modules/yahoo-finance2/dist/esm/src/lib/yahooFinanceFetch.js:62:23)
at async Object.moduleExec [as _moduleExec] (webpack-internal:///(rsc)/./node_modules/.pnpm/yahoo-finance2@2.11.2/node_modules/yahoo-finance2/dist/esm/src/lib/moduleExec.js:58:18)
at async Object.quote (webpack-internal:///(rsc)/./node_modules/.pnpm/yahoo-finance2@2.11.2/node_modules/yahoo-finance2/dist/esm/src/modules/quote.js:9:21)


[0.26] KafkaChannel to init offsets before dispatcher

Manual cherry pick of the same fix in 0.24: https://github.com/knative-sandbox/eventing-kafka/pull/886

Release Note

- 🐛  Fixed a bug that was causing Kafka Channel dispatcher to miss some events in case the offset for the consumer group was not initialized

Docs

/test pull-knative-sandbox-eventing-kafka-integration-test-channel-consolidated
/test pull-knative-sandbox-eventing-kafka-integration-test-channel-consolidated-tls

/hold
let's use :cherries:-pick of the "merge sha" ...

/close
Closing in favor of https://github.com/knative-sandbox/eventing-kafka/pull/915


feat(Gruvify): add Gruvify theme

Adds an opinionated Gruvbox theme.
Repository can be found here.
A related spicetify/docs PR is also made here

Sorry for the late response, been real busy lately, but I would recommend not adding the theme here but instead just adding your theme to the marketplace using the repo you've already created. You can find the steps to do so on the docs, and it will make it much easier for you to keep pushing out changes.
Thanks!


[Summer of code] Reuse dledger remotingServer in controller mode.

Make sure set the target branch to develop
What is the purpose of the change
tracking issue: https://github.com/apache/rocketmq/issues/4330
Brief changelog
1.Reuse dledger's remotingServer in controller mode.
2.Fix some bugs when controller deployed standAlone.
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Codecov Report

Merging #4409 (72f28ca) into 5.0.0-beta-dledger-controller (12d9207) will decrease coverage by 0.02%.
The diff coverage is 50.84%.

@@                         Coverage Diff                         @@
##             5.0.0-beta-dledger-controller    #4409      +/-   ##
===================================================================
- Coverage                            43.30%   43.27%   -0.03%
- Complexity                            6338     6345       +7
===================================================================
  Files                                  839      840       +1
  Lines                                59637    59688      +51
  Branches                              8130     8134       +4
===================================================================
+ Hits                                 25824    25831       +7
- Misses                               30469    30517      +48
+ Partials                              3344     3340       -4

Impacted Files
Coverage Δ

...org/apache/rocketmq/namesrv/NamesrvController.java
48.25% <0.00%> (-1.39%)
:arrow_down:

.../namesrv/processor/ControllerRequestProcessor.java
0.00% <0.00%> (ø)

...ketmq/store/ha/autoswitch/AutoSwitchHAService.java
55.94% <ø> (-0.06%)
:arrow_down:

...q/controller/impl/manager/ReplicasInfoManager.java
63.41% <16.66%> (+1.60%)
:arrow_up:

...he/rocketmq/controller/impl/DLedgerController.java
70.32% <64.28%> (-2.35%)
:arrow_down:

.../apache/rocketmq/controller/ControllerManager.java
83.01% <75.00%> (-3.26%)
:arrow_down:

...controller/impl/DefaultBrokerHeartbeatManager.java
86.41% <77.77%> (+1.48%)
:arrow_up:

...org/apache/rocketmq/common/stats/StatsItemSet.java
47.76% <0.00%> (-2.99%)
:arrow_down:

...va/org/apache/rocketmq/logging/inner/Appender.java
30.33% <0.00%> (-2.25%)
:arrow_down:

...che/rocketmq/container/BrokerContainerStartup.java
55.08% <0.00%> (-2.12%)
:arrow_down:

... and 17 more

Continue to review full report at Codecov.

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

Coverage increased (+0.1%) to 47.458% when pulling 72f28ca7e0903b0d156ea98d381f9d05a21b91b1 on hzh0425:feature/use-dledger-remotingServer into 05841188e2c22c04c99ede878ea541be9b28c6f2 on apache:5.0.0-beta-dledger-controller.

/run-all-tests

/rebuild

@RongtongJin PTAL


Add excoveralls - coverage reporting

I wanted to check coverage in this library before using it in prod — thought I'd push the changes upstream.
This lets you view coverage reporting from the cli:
$ mix coveralls
# ...
Finished in 0.2 seconds (0.2s async, 0.00s sync)
14 tests, 0 failures

Randomized with seed 821896
----------------
COV    FILE                                        LINES RELEVANT   MISSED
  0.0% lib/ecto_network.ex                             5        0        0
 66.7% lib/ecto_network/cidr.ex                       27        6        2
 88.2% lib/ecto_network/inet.ex                      131       34        4
 87.5% lib/ecto_network/macaddr.ex                    67       16        2
[TOTAL]  85.7%
----------------

Or output a coverage report in html format:
$ mix coveralls.html && open cover/excoveralls.html

Thanks!


Extension - Fix min stake for TAO(Bittensor)

Describe the task
Fix min stake for TAO(Bittensor)
Suggest: Min amount to stake = Min stake + ED*1.5

@tunghp2002 please disable action View on explorer on History detail for Bittensor

Version test: http://<IP_ADDRESS>:8900/s/3FTYxs6oNn86CL3

[ ] Can't navigate to bittensor's explorer
Actual:

Expect: Only disable on the history details screen

Version test: http://<IP_ADDRESS>:8900/s/HRngeHEPkX9QW5W
Validation passed

Update min amount stake:

Check info validator, position for TAO

Re-check all action earning

Disable action View on explorer on History detail for Bittensor


[libVLC] any chance to add libVLC into the repository?

the request to add cross-platform video playback package - VideoLAN (aka VLC)
http://git.videolan.org/git/vlc.git
the repository includes the player itself, but only SDK in the request, libVLC.
which mostly consists from lib, include and plugins folders (and some files from src)
note: in case of positive decision to add the library, pay your attention that for successful usage this lib, it needs to be included - the plugins from full distribution.
currently this uses autotools for the build, as far as I see it can be built by  vc as well as mingw

@amigo421 https://github.com/sunqueen/vlc-<IP_ADDRESS>-2015
-G"Visual Studio 14 2015" -T"v120", как то так

VLC for Windows 10 Desktop
https://github.com/videolan/vlc-winrt
https://github.com/videolan/vlc-winrt/blob/master/build/VLC.sln

We can’t reopen this issue until a PR is opened, unfortunately, consider making a pull request!

I also need this.  But I'm confused about the closed status.  Does this mean this isn't going to be added?

@stephanecharette Nope, we hope that anyone can create a new PR to add it.

@stephanecharette Nope, we hope that anyone can create a new PR to add it.

If I knew how to build it, I wouldn't be using vcpkg.  I think this text on the main vcpkg page is misleading:

If a library you need is not present in the vcpkg catalog, you can open an issue on the GitHub repo

If issues asking for new ports are simply closed with people saying "figure it out and submit a PR", then why bother opening an issue?

@stephanecharette This issue has been closed due to our policy, you can open a new issue to request this port.
Thanks.

@stephanecharette This issue has been closed due to our policy, you can open a new issue to request this port.

What policy?

@stephanecharette We prioritize bugs and features.

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now.


Go to definition stopped working

I use to have alt+click to go to definition. But it stopped working.

VSCode Version: 1.39.0
OS Version: Ubuntu 18.04

Steps to Reproduce:

"editor.multiCursorModifier": "ctrlCmd",

I tried "editor.multiCursorModifier": "alt", and it makes multi-cursor not to work. So it seems that there is problems with alt. The rest of the shorcuts work weel with alt, though.
(& my alt button isn't broken :laughing:)

Does this issue occur when all extensions are disabled?: Yes

@vscodebot, mine isn't overriden by the system. It was working 2 days ago

@pirix-gh I could never use Alt+click on Ubuntu (the windows would always move when doing so), so I wonder how come this ever worked for you?

Hi @alexandrudima. I had disabled the window drag with dconf https://askubuntu.com/questions/521423/how-can-i-disable-altclick-window-dragging (that I replaced with the  button). Like I said, it was working a few days ago until the update came.

@alexandrudima Nevermind, I'll use shift+alt+click.

And just for info, I also disabled mnemonics (hotkeys alt+menukey) system-wide and in vscode via the window setting but it still had the same behavior.

btw, what is your alternative (setting) to handle this?

@pirix-gh I have just tried in Ubuntu 19.10. I have configured "editor.multiCursorModifier": "ctrlCmd" and I can use alt+click to jump to definition fine:

I tested, and it's the same. It seems like something else is capturing the mouse when I use alt... So this is probably not an issue, even though I'm on ubuntu 18.04.
Does the alt work out of the box on ubuntu 19.10? Or did you also have to disable the window dragging?

I was pleasantly surprised to see that alt works out-of-the-box on Ubuntu 19.10 ...


Bulk Import Contacts to Office365 - hopeless!

I thought office365 was supposed to be advanced? However, when it comes to importing contacts for the organisations to share (which is hidden under the "Users" tab - why?) I find I can only add them laboriously one at a time! To do a bulk import requires installing and running Powershell (whatever the hell that is). Surely Office365 can't be this backwards in 2018? I want to import a few contacts via CSV from another system and I am faced with this nonsense. Amazing. Microsoft is so user unfriendly, still! get a grip.

@swedishpotato - thank you for submitting feedback. PowerShell is a command line utility for working with items in bulk. I am sorry you are experiencing so much frustration with Office 365.
I think the best way forward is if you can open a service ticket in your tenant so this can get resolved ASAP. The support engineers will be able to guide you on the best way to import a few contacts and if it is possible to use a CSV file. Based on outcome let me know if it is something that can be called out in the docs.
Here is a quick video on opening a ticket: https://www.youtube.com/watch?v=puuOy0sEg1Y
If you don't mind please keep us posted here on the resolution and I really want to get this information you are discovering back into the docs.


How to show big label on Heatmap

Codepen
https://codepen.io/anon/pen/jgYXMa
Explanation

How can i show the entire label when it is bigger than a simple word or number?

For example: in the Pen all the "Title - Artist" labels on the left of the chart are cutted.
Thanks for help

You can set the minimum width of the yaxis labels by
yaxis: {
  labels: {
    minWidth: 200
  }
}


Implement ToTokens without reliance on {:?}

#296 (unblocks https://github.com/rust-lang/rust/pull/123940)

Published in 1.0.59.


DATRAS Litter: Two new codes for C-TS-REV

WGML requests two new codes:
A15 medical masks
A16 other fishing related plastics

Inform WGDG about these new codes.

@Osanna123 to create the two codes in PARAM. To inform @odontaster, so this task can be fully implemented.

LT300 and LT301 are added to PARAM with respective relations.
A15 and A16 might be missing some relations

implemented, also missing links.


Close cursors in AttachmentManager

Updated to match the rest of cursor closing code

Thanks for this. Unfortunately we're a bit behind on accepting contributions since becoming part of IBM; we're fixing this and I'll update with a comment when we have the process in place. Sorry for the delay.

Okay, I finally sorted all the things out. We need you to sign a CLA before I can accept these changes. This is hopefully a quick process, you can email a signed version. See the details here:
https://github.com/cloudant/sync-android/blob/master/CONTRIBUTING.md#contributor-license-agreement
Once I have this, I can accept your PRs. I really appreciate your patience as I've worked this process out.

Confirming signed CLA on file.
@rhyshort Could you check this over, you are more familiar with the code than me?
We have a holiday in the UK until Tuesday, so hopefully we can get this merged first thing next week.
Have a great weekend.

Looks good to me, merging
Thanks @Matulis


feat(#36): sender.login parse

closes #36

PR-Codex overview
This PR focuses on adding functionality to fetch the GitHub login of the approver of a pull request.
Detailed summary

Added code to fetch the GitHub login of the pull request approver.
Logged the approver's login and the received event.
Used the fetched GitHub token for further processing.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor release, tag is 0.0.11

@rultor release, tag is 0.0.11

@h1alexbel OK, I will release it now. Please check the progress here

@rultor release, tag is 0.0.11

@h1alexbel Done! FYI, the full log is here (took me 3min)


Share session link has the escience center link hardcoded

Would be nice if this was in a config file, now I need to edit the source code to update the url to idarksurvey.com

fixed in dev


FSM blueprint needs to be updated with client name that does not contain spaces

It is no longer legal to have a client name contain spaces. The Service Desk client violates this restriction and should be updated to have a name like Service-Desk instead.
@pburma do you want to make this change? I can make it if you do not have time, but is there anything else that needs to be adjusted besides the name? Are there references to the client by name elsewhere in the blueprint?

FYI... it's still an issue... :-) I just tried to upload it, and I had to manualy fix the "Service Desk" page set file name and the "name" property inside the file.

I've updated "Service Desk" client to "ServiceDesk" and submitted a pull request into master, now I wonder who is going to review and approve this one to get the updated fileset out to the public

well, I've tried to commit into Vantiq Blueprints Git on master but need "At least 1 approving review is required by reviewers with write access.".....so question is : Who is an authorized reviewer with write access there ?
Enumerating objects: 21, done.
Counting objects: 100% (21/21), done.
Delta compression using up to 8 threads
Compressing objects: 100% (15/15), done.
Writing objects: 100% (15/15), 548.34 KiB | 7.31 MiB/s, done.
Total 15 (delta 9), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (9/9), completed with 5 local objects.
remote: error: GH006: Protected branch update failed for refs/heads/master.
remote: error: At least 1 approving review is required by reviewers with write access.
To https://github.com/Vantiq/Blueprints.git
! [remote rejected] master -> master (protected branch hook declined)
error: failed to push some refs to 'https://github.com/Vantiq/Blueprints.git'

I don't see any pull request for this change.
How did you create your PR?
To create a PR we can see in github, "git push" your branch and then use the github web UI to create a PR from that branch to Vantiq/Blueprints:master.  From either the Code page or the Pull Requests page.

you are right, I ~thought~ having created a pull request but only tried to commit to master which got refused
Enumerating objects: 21, done.
Counting objects: 100% (21/21), done.
Delta compression using up to 8 threads
Compressing objects: 100% (15/15), done.
Writing objects: 100% (15/15), 548.34 KiB | 18.28 MiB/s, done.
Total 15 (delta 9), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (9/9), completed with 5 local objects.
remote: error: GH006: Protected branch update failed for refs/heads/master.
remote: error: At least 1 approving review is required by reviewers with write access.
To https://github.com/Vantiq/Blueprints.git
! [remote rejected] master -> master (protected branch hook declined)
error: failed to push some refs to 'https://github.com/Vantiq/Blueprints.git'

https://github.com/Vantiq/Blueprints/pull/21 created for review and merge


Configure Rollup

closes #61

Pull Request Test Coverage Report for Build 148720563

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.685%

Totals

Change from base Build 148611823:
0.0%

Covered Lines:
142

Relevant Lines:
144

💛  - Coveralls

Pull Request Test Coverage Report for Build 148722784
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.685%

Totals

Change from base Build 148611823:
0.0%

Covered Lines:
142

Relevant Lines:
144

💛  - Coveralls


Design the Manifest mechanism of services for the SMA.

The SMA will need to be provided a configuration (aka manifest) that specifies the list of the services it manages. The manifest will enumerate the services which the SMA is managing, along with details such as are needed to manage any given service. This mechanism is warranted by the need to onboard additional (device) services.
Essentially, the SMA needs to be made aware of (in the discoverability sense) of services that come online after the EdgeX (core) services have been launched: This, in turn, means some sort of  manifest mechanism that provides yet a third way to the SMA to be made aware of (in the discoverability sense) of services, in addition to the existing Registry and configuration.toml-based workflows.
Thus, from the perspective of the SMA—and in particular the discoverability aspects—we have in place a check to determine whether the SMA is aware of a given service (via its associated ServiceKey) via a lookup to identify if the ServiceKey is one for which the SMA has a ready-made "client" (referring here to a client that is responsible for mediating between a given service and the SMA). In particular, the SMA simply uses one of the ready-made list of clients that was created at bootstrap, thus using the config that's driven by statically-defined keys (one each for the core services)
But if a service is unknown to the SMA, the Registry is queried to determine whether it (i.e. the service) is available. And given that the service is unknown to the SMA, the Registry is asked for a ServiceEndpoint associated with that service.
And this is where the manifest mechanism comes in: The SMA will, at this juncture, lean on the provided configuration (aka manifest) to proceed with servicing the request. (Dynamic generation of the needed config information comes to mind as a possibility, though this may not be feasible for the first pass of a possible implementation.)
The alternate flow is that, for a service that is known to the SMA, there is no need to ask the Registry for a ServiceEndpoint associated with that service: The SMA simply uses one of the ready-made list of clients that was created at bootstrap, thus using the config that's driven by statically-defined keys (one each for the core services).

This really is an overall exercise in Service Discovery, and within that is situated the design of a manifest mechanism of services for the SMA.
To this end, the following potential use cases have been captured following design discussions:
SMA File-based Service Discovery.pdf
SMA Registry-based Service Discovery.pdf
SMA Manifest-based Service Discovery.pdf

@akramtexas Is this an ongoing concern? Should it be a Geneva work item?

I think this is an obsolete issue.  Closing.

I think this is an obsolete issue. Closing.

@michaelestrin That is correct, thanks for closing this issue.
@brandonforster Thanks for spotting this.


feat(logout): allow users to logout

This PR adds the ability for users to logout from the user menu.

It also improves the way we pull in patternfly styles. Previously we had our base styles loaded after the component styles in the DOM, hadn't been able to figure out why before but in working with some others we found that this import import { UnrecoverableError } from '@syndesis/ui'; coming before we pull in App.css causes the styles to be imported in the wrong order in the DOM. Now with this coming after App.tsx is pulled in, styles are automatically pulled in via the respective react components and we no longer need to import individual patternfly stylesheets as we were doing previously.
I also ditched the approach of using individual base patternfly stylesheets, now that we've made our styling adjustments to the elements that were impacted by introducing PF4 in general, we should be able to safely use the full base stylesheet as provided by react-core.

PR Storybook available here

Interesting, I'm getting a 200 response for logout locally, but in the PR build I get a 404. In either case, I'm not redirected to a logout page, and if I refresh the page it doesn't look like I actually logged out anyway. Getting close though. Maybe @zregvart has an idea of what the missing piece may be?

PR Storybook available here

PR Storybook available here

PR Storybook available here

Interesting, I'm getting a 200 response for logout locally, but in the PR build I get a 404. In either case, I'm not redirected to a logout page, and if I refresh the page it doesn't look like I actually logged out anyway. Getting close though. Maybe @zregvart has an idea of what the missing piece may be?

I'm guessing that locally you run against staging and on the PR build against stubs?
Thing to watch out for is the _oauth_proxy cookie, when you hit logout (if SYNDESIS-XSRF-TOKEN: awesome HTTP header is present) it should get cleared when /logout endpoint is invoked. If it doesn't get cleared (at that point) then we have a bug. Anyhows see the suggestion on the PR.
Other thing that we need to be aware of: because we have single sign on using OAuth, and we're not doing single logout on the staging cluster against GitHub it can appear as if you didn't logout, but what actually is happening is that you get logged out can get logged in right away (happens really fast since you already approved oauth-proxy's OAuth use).

Thx for the feedback everyone. So in the response headers I see
set-cookie: _oauth_proxy=deleted; Expires=Thu, 01-Jan-1970 00:00:01 GMT; Domain=.syndesis-staging.b6ff.rh-idev.openshiftapps.com; HttpOnly; Secure - which I think looks fine.
But in the request headers I see only Cookie: io=qfXo2D4soeosanqsAAAD which looks like it's missing some things (comparing against staging w/ angular app) I think that's my hang up.
Is the proxy definition ok? I used the same format as the /api/v1 endpoint and swapped the path to /logout. Should I be doing something different with the cookie here?

Is the proxy definition ok? I used the same format as the /api/v1 endpoint and swapped the path to /logout. Should I be doing something different with the cookie here?

I think it's fine, and no the proxy should only just be proxying.

PR Storybook available here


Wardley Map: add evolve support

We want to support code like:
evolve Node B -> something b 0.73 label [-5, 21]

We want the evolve to be a property of an actual note, instead of another model node with type.


Use without filesystem?

Just curious - is there any way this can be used on servers where there is no write access to a filesystem? I'm thinking of some of the cloud based servers out there.
Would love to add openid to some of my omniauth using apps but have always been stopped by not having a file system to write to.

Suddenly got the reference to the stores. Testing memcache now ;)


temporarily remove security audit

Motivation

Solution

PR Checklist

[ ] Added Tests
[ ] Added Documentation
[ ] Updated the changelog

Codecov Report

Merging #172 (f7fe8df) into main (4b82b07) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #172   +/-   ##
=======================================
  Coverage   46.57%   46.57%
=======================================
  Files          15       15
  Lines        5316     5316
=======================================
  Hits         2476     2476
  Misses       2840     2840

Flag
Coverage Δ

test
46.57% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


Doc updates for LowVirtOperatorCount & LowReadyVirtOperatorsCount

Thank you for the review @apinnick , hopefully the content is ship-shape now.
@sradco , when you have a bit of time, please look into the changes and let me know if something looks off, and if not, feel free to merge :-)

LGTM

@sradco This is ready for review/merge.

@sradco LGTM


[a11y]: set rel="external" on ShareListItem

As ShareListItem use external links only, so one should set rel="external" on share links

Moved here: https://github.com/gravity-ui/page-constructor/issues/485


Drag api

Reference api is based on reason like createRef

Internals are quite messy yet. Gonna fix in following PRs.

Example
import GridLayout, { createDragApiRef } from 'react-grid-layout';

class App extends React.Component {
  dragApi = createDragApiRef();

  onDrag = event => {
    if (this.dragApi.value) {
      const { x, y } = getPosition(event);
      if (inViewport(x, y)) {
        this.dragApi.value.dragIn({ i: 'id', w: 2, h: 2, node: event.target, position: { x, y }, event });
      } else {
        this.dragApi.value.dragOut({ position: { x, y }, event });
      }
    }
  };

  this.dragStop = event => {
    if (this.dragApi.value) {
      this.dragApi.value.stop({ position: getPosition(event), event });
    }
  };

  render() {
    return (
      <GridLayout dragApiRef={this.dragApi}>
        {...}
      </GridLayout>
    );
  }
}

Thanks - can you explain more about the motivation behind this (versus just passing those values on callback)?

Maintaining the same props (passed to grid) separatly is hard. Changes in lib may break UX implicitly for developer. Also right now it's not posible to maintain placeholder.

Modeling events with swapping states is also shot in the foot.

Will begging and groveling get this merged any quicker ;-)  Could really use it right now

We're looking for this as well, any chance it will be merged?

@TrySound @foodforarabbit We're trying to use this drag-api and wondering if there's any plan to merge it into this master branch anytime soon. Could you provide us with an update on any reasons why this is on hold? It'll be super helpful, thanks!

@samiyaakhtar Sorry, I am neither the repo maintainer nor the PR owner.. I simply forked the repo and added changes myself to support my exact needs, which may not necessarily support generic use cases. The simplest reason is probably that there are just more important features / fixes that need to be addressed first either in this repo, or another project.

This is essential to create a custom placeholder that recalculates its proper place while dragging external objects to react-grid-layout. This is a must-have.

I apologize for letting this sit so long. If someone is willing to resolve the conflicts & write some docs/tests for it, I'll merge it.

Hi @STRML, please take a look #935 😄

FYI @TrySound - I think there's a bug in ReactGridLayout.onResizeStop - whenever an item is resized the onLayoutChange prop is never called. This is because "same" layout is being passed to this.onLayoutMaybeChanged. I suspect it's a mutation issue
I'm just now digging into it so I'll let you know what I find.
BTW - thank you very much for this PR, I've been using it with great success.

Any results to expect here?

@STRML any update about this feature?

No - conflicts still need to be resolved and tests written.

Ok I have an updated version of the PR here: https://github.com/STRML/react-grid-layout/pull/1247
I'll look into tests. I'm thinking to copy example 15 and to copy the "droppability" test.

Hi,
I would like this feature to be added as it suits my usage with the library.
Exposing the drag API can give customizability to the developers using the library.
I would use this to callback the original drag API but throttle it to increase performance.


Upgrade OTel proto version.

Is your feature request related to a problem? Please describe.
Pixie OTel export uses an older version of the Span proto. See, e.g., the following:

Example Pixie source code using older library_spans.

Diff in OTel repository showing deprecation of the same.

IIUC Pixie currently uses OTel proto v0.10.0. The latest OTel proto release is now v1.1.0.
OTel proto v0.19.0 introduced a change where library_spans were completely rm'd, see:
https://github.com/open-telemetry/opentelemetry-proto/compare/v0.18.0...v0.19.0
Describe the solution you'd like
Upgrade Pixie OTel proto to v1.1.0 or to either of v0.18.0 or v0.19.0. Switch to using (e.g.) scope_spans.
Describe alternatives you've considered
As an alternative, we could keep using the older OTel proto version (i.e. do nothing).

This was completed in #1974.


[move-prover] data invariant assume and assertion for &mut params

For functions with &mut params s: S, the data invariant for S will be assumed at function entry (via Wellformedness - this is already done) and re-checked on any write-back to this reference --- this is newly added in this commit.
This PR is the opposite of PR #783 which does the opposite, i.e., drop the assumption at the function entry. PR #783 is proposed following the following guideline:

Data invariants are only checked when the &mut borrow ends. During
the lifetime of the &mut reference, the invariant can be temporarily
violated and hence, assuming data invariants there can lead to
inconsistency issues.

In theory, both PR's fix are better than the current practice (which is essentially assuming without assertion).
However, as the test result in PR #783 shows, the Options.move in stdlib heavily relies on the entrypoint assumption that a &mut Option has either 0 or 1 entry in its vector. Therefore, in this commit, we tighten the conditions where we assert data invariant.
In summary, after this PR, data invariants will be checked:

on write-backs to local root, arised from let r = &mut s where s is a local variable
on write-backs to global root, arised from let r = borrow_global_mut<S>(addr)
on write-backs to &mut parameter.

struct S {
    f: u8
}
spec S {
    invariant f != 0;
}

fun foo(s: &mut S) {
    // spec: assume s.f != 0;

    let r = &mut s.f;
    r = 0;

    // spec: write-back[s.f](r);
    // spec: assert s.f != 0;
}

Motivation
Fixes both #780 and #781
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan

CI
Two new test cases adapted from the issues are added

Rule 1 and  2 already exist and are correctly enforced.
Rule 3 is introduced in this PR

Rule 3 is the rule that causes push_1 and push_2 fail in the newly introduced test case.

Rule 3 is the rule that causes push_1 and push_2 fail in the newly introduced test case.

In push_1, does the write-back to the &mut parameter happen right after exiting the function call for push_back?
struct S {
    f: u8
}
spec S {
    invariant f != 0;
}

fun foo(s: &mut S) {
  s.f = 0;
}

In the example above, the write-back will happen after the line s.f = 0 because it uses an implicit mutable reference?

struct S {
    f: u8
}
spec S {
    invariant f != 0;
}

fun foo(s: &mut S) {
  s.f = 0;
  // no write-back as `s` is still alive
  s.f = 1;
  // no write-back as `s` is still alive
  s.f = 2;
  // write-back here as `s` is destroyed
  // data invariant asserted here, immediately after the write-back
}

I see. Just to make sure, the data invariant is not asserted in foo because s is not destroyed?
struct S {
    f: u8
}
spec S {
    invariant f != 0;
}

fun foo(s: &mut S): &mut S {
  s.f = 0;
  s.f = 1;
  s.f = 2;
  s
}

I think the data invariant should be instrumented as the return value is assigned to a new variable and hence, s is still considered as destroyed. But this can be confirmed by adding a test case and see the results, I'll add one to confirm.

That would be nice. Thanks!
By the way, I am curious if the write-back happening when a mutable reference is destroyed was already there before this PR? Or, is this newly added to this PR for the sake of enforcing data invariants?

It's already happening before this PR. This can been seen in the diff as well.

Added two test cases @junkil-park suggested in the comments, which also helps with the illustration on when write-backs happens.


Single Use Link Expired page

When using a Single Use Link a second time we need to display an error message to the user indicating that the link has expired or was not found. Currently we just show a blank page.
Below is the error message that we should in production and that is missing in QA/development.

Test case: https://scm.dlt.psu.edu/issues/3727

Duplicate with https://github.com/psu-stewardship/scholarsphere/issues/105


Bump api to relay v1

https://github.com/encryptedcoins/encoins-relay/releases/tag/v1

Resolved in #53


默认用户无法登录

crane部署完后，使用默认的用户名和密码无法登录，提示服务忙，请稍候重试

https://github.com/Dataman-Cloud/crane#option-1-stable-version-in-one-line   updated please agine

@upccup 就是按照option1安装的，rolex_rolex_db_1容器里面的rolex库一张表都没有，是否正常？

@jeremywu0127  今天 options 1 更新了， 今天上午更新的。原来有个bug。就是 rolex_rolex_1 这个程序无法 start

@vitan 那最新的可用包什么时候放出来？我是今天下午2点多测试的，rolex_rolex_db_1的log显示MySQL init process done. Ready for start up.

@jeremywu0127 可以拉下最新的代码，看这个https://github.com/Dataman-Cloud/crane/pull/419，已经merge了

@jeremywu0127  这个问题的话，应该是 mysql 容器没有成功启动，什么操作系统？

Issue in English is better, friendly to the Non-Chinese developers.

@vitan ubuntu 14.04 docker 1.12.1

@ckanner this is option 2 way to install ? cause I run option 1 again and it doesn't work

@jeremywu0127  need more info, please paste
docker ps, docker logs rolex_rolex_db_1 and docker  logs rolex_rolex_1

@vitan here is part of logs
ubuntu@test-munin:~$ docker ps
CONTAINER ID        IMAGE                   COMMAND                  CREATED             STATUS              PORTS                         NAMES
c1c73953395c        blackmamba:24abb08      "nginx -g 'daemon off"   3 days ago          Up 3 days               <IP_ADDRESS>:80->80/tcp, 443/tcp   crane_blackmamba_1
58b08024241a        crane:24abb08           "/bin/sh -c ./crane"     3 days ago          Up 3 seconds        <IP_ADDRESS>:5013->5013/tcp        crane_crane_1
8ca9a5eb83a1        registry:crane24abb08   "/entrypoint.sh /etc/"   3 days ago          Up 3 days           5000/tcp                      crane_crane_registry_1
0cdcaedd3535        mysql:crane24abb08      "docker-entrypoint.sh"   3 days ago          Up 3 days            3306/tcp                      crane_crane_db_1

ubuntu@test-munin:~$docker logs crane_crane_db_1
2016-09-18T10:56:20.551916Z 10838 [Note] Aborted connection 10838 to db: 'crane' user: 'root' host: '<IP_ADDRESS>' (Got an error reading communication packets)
2016-09-18T10:56:50.804950Z 10839 [Note] Aborted connection 10839 to db: 'crane' user: 'root' host: '<IP_ADDRESS>' (Got an error reading communication packets)
2016-09-18T10:57:21.072828Z 10840 [Note] Aborted connection 10840 to db: 'crane' user: 'root' host: '<IP_ADDRESS>' (Got an error reading communication packets)

ubuntu@test-munin:~$docker logs crane_crane_1
time="2016-09-18T10:56:51Z" level=error msg="Parse info CRANE_SWARM_MANAGER_IP got error: missing delimiter '='"
time="2016-09-18T10:56:51Z" level=info msg="begin to init and enable plugin: registryauth"

The container crane_crane_1 is always restarting, which is caused by the mysql wrong init, I guess.
@upccup  can you help to debug it? Need reproduce it on a Ubuntu server.

@upccup @vitan the code version which  I used is
commit 24abb084cbff70ca94bbf3433d63dcdbd376bebb
Merge: c3fc206 960b84d
Author: Zhou Weitao<EMAIL_ADDRESS>Date:   Wed Sep 14 18:05:25 2016 +0800
Merge pull request #437 from Dataman-Cloud/issue
Issue
and I use the option 1 to install the crane, server is ubuntu 14.04.2 docker version is 1.12.1  on aws ec2

@jeremywu0127  sorry to too late reply. is you mysql service is running good?

option 1
need more info
docker ps, docker logs, rolex_rolex_db_1 and docker logs rolex_rolex_1.
option 2
CRANE_IP=<IP_ADDRESS> ./bin/build-and-start.sh

Do you set CRANE_IP?

@f0x11 @upccup I have already set the CRANE_IP , and mysql log is like,
2016-09-20T02:13:27.041001Z 15512 [Note] Aborted connection 15512 to db: 'crane' user: 'root' host: '<IP_ADDRESS>' (Got an error reading communication packets)
2016-09-20T02:13:57.311483Z 15513 [Note] Aborted connection 15513 to db: 'crane' user: 'root' host: '<IP_ADDRESS>' (Got an error reading communication packets)

docker logs crane_crane_1 shows like:
time="2016-09-20T02:21:31Z" level=fatal msg="Get http://myip:2375/v1.24/version: dial tcp myip:2375: i/o timeout"
time="2016-09-20T02:21:31Z" level=error msg="Parse info CRANE_SWARM_MANAGER_IP got error: missing delimiter '='"
time="2016-09-20T02:21:31Z" level=info msg="begin to init and enable plugin: registryauth"
time="2016-09-20T02:21:31Z" level=info msg="connecting mysql uri: root:111111@tcp(crane_db:3306)/crane?charset=utf8&parseTime=true&loc=Local"
time="2016-09-20T02:21:31Z" level=info msg="init and enable plugin: registryauth success"
time="2016-09-20T02:22:01Z" level=error msg="Unable to ping docker daemon. Ensure docker is running endpoint http://myip:2375err: Get http://myip:2375/v1.24/version: dial tcp myip:2375: i/o timeout"
time="2016-09-20T02:22:01Z" level=fatal msg="Get http://myip:2375/v1.24/version: dial tcp myip:2375: i/o timeout"
time="2016-09-20T02:22:01Z" level=error msg="Parse info CRANE_SWARM_MANAGER_IP got error: missing delimiter '='"
time="2016-09-20T02:22:01Z" level=info msg="begin to init and enable plugin: registryauth"
time="2016-09-20T02:22:01Z" level=info msg="connecting mysql uri: root:111111@tcp(crane_db:3306)/crane?charset=utf8&parseTime=true&loc=Local"
time="2016-09-20T02:22:01Z" level=info msg="init and enable plugin: registryauth success

does crane connect to the 2375 port  by using the CRANE_IP?  the CRANE_IP which I set is the public ip and the 2375 port doesn't expose to all address in aws security group

the reason is the aws sg,it works now! but I get anther error like
time="2016-09-20T02:39:05Z" level=warning msg="get node list error: This node is not a swarm manager. Use \"docker swarm init\" or \"docker swarm join\" to connect this node to swarm and try again."
time="2016-09-20T02:39:05Z" level=warning msg="get stack list error: This node is not a swarm manager. Use \"docker swarm init\" or \"docker swarm join\" to connect this node to swarm and try again."
time="2016-09-20T02:40:05Z" level=warning msg="get node list error: This node is not a swarm manager. Use \"docker swarm init\" or \"docker swarm join\" to connect this node to swarm and try again."
time="2016-09-20T02:40:05Z" level=warning msg="get stack list error: This node is not a swarm manager. Use \"docker swarm init\" or \"docker swarm join\" to connect this node to swarm and try again."

I solved it, crane doesn't init docker swarm mode during the install progress ?

@jeremywu0127  the CRANE_IP is swarm manager ip, and crane use CRANE_IP:2375 to visit docker deamon. you can find this in https://github.com/Dataman-Cloud/crane/blob/master/bin/build-and-start.sh#L14  and https://github.com/Dataman-Cloud/crane/blob/master/bin/build-and-start.sh#L14 and https://github.com/Dataman-Cloud/crane/blob/master/src/utils/config/config.go#L18

@jeremywu0127  yes you should create a docker swarm cluster before run crane

thx to all guys,  crane is great ! 👍


Regression: Attaching Location to ChatMessage does not work

Describe the bug
The owner-webapp allows you to attach a location to the message you're composing. When you do that, no location data ends up in the message.
To Reproduce

Create a conversation in the owner-webapp
When sending a message, hit '+' and add the location

Expected behavior
In the message RDF, there should be some triples representing the location
Desktop (please complete the following information):

OS: Windows 10
Browser firefox current

Nothing conspicuous in the JS console

probably a hickup due to the new graph uris,not sure if thats the case but i will look into it tomorrow and dispatch accordingly

seems to work fine with me, i guess it works now


refactor(cache): replace hasmap's .iter().find() with .get()

Instead of finding a HashMap value by key through an iterator, HashMap::get should be preferred.
That is, unless it was chosen consciously to maybe improve performance on empty maps by avoiding a u64 hash, in which case this PR can be closed.

this is a holdover from when resolved was a vec, nice find. thanks

Thanks


[Feature Request]: Want to make Testimonial Dynamic instead of static data

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
I want to make that the user actually post the data in Testimonial via its profile but I am not sure about the approach @VaibhavArora314 can you guide me to make this feature.
In Testimonial the user name, avatar along with its review etc will be shown, Just tell me how to implement I will implement it ASAP.
Use Case
UI/UX
Benefits
User Testimonial engagement
Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

So instead of dummy profile photo and username, you want to show details of actual users and reviews from them?

So instead of dummy profile photo and username, you want to show details of actual users and reviews from them?

Ya like actual data from users what they taught about style share and all like most of the websites have !

So instead of dummy profile photo and username, you want to show details of actual users and reviews from them?

Ya like actual data from users what they taught about style share and all like most of the websites have !

Ok so basically you can break this into two sub issues: one for allowing users to provide feedback and other for integrating that feedback to testimonials.

@VaibhavArora314 I will start working on this ASAP because only 4 days is remaining !

Also allow users to provide stars out of 5 with their feedback

Also allow users to provide stars out of 5 with their feedback

Ya, like their will be a form in which there is a stars and write your feedback likd that


Hash mismatch downloading opencv when running make

I get the following error:
-- Using src='https://github.com/hunter-packages/opencv/archive/3.0.0-p6.tar.gz'
...
-- [download 100% complete]
-- verifying file...
file='/Users/josh/.hunter/_Base/Download/OpenCV/3.0.0-p6/228124c/3.0.0-p6.tar.gz'
-- SHA1 hash of
/Users/josh/.hunter/_Base/Download/OpenCV/3.0.0-p6/228124c/3.0.0-p6.tar.gz
does not match expected value
expected: '228124cf6076d9da62f1a9a357e350f3e43f81d0'
actual: 'bf51cf6fff52da81d7756c15cc878096813b256c'

sorry posted this to the wrong project


bump prometheus/client_golang for double counting bug

https://github.com/prometheus/client_golang/releases/tag/v1.13.1
https://github.com/prometheus/client_golang/pull/1118
Signed-off-by: Kenny Leung<EMAIL_ADDRESS>

ok, the knative jobs are now using go1.19
will update the rules here and open a PR to bump to go 1.19 the parts in our side


Pod::To::Xxxx options processing support

I'm wanting to support options processing in some Pod rendering modules, such as:
raku --doc=PDF my.pod --/index  --save-as=my.pdf

As far as I can work out the options are available in @*ARGS.
But I can't see any Rakuish way of processing the arguments.
-- @*ARGS-TO-CAPTURE has limited scope and isn't available here
-- I can't see anything on the ecosystem (GetOpt::Long seems Perlish, wont handle  '--/index')
Could Raku's built-in option parsing somehow be better made available to Pod renders?

Here's a short example, that demonstrates current behavior:
unit class Pod::To::Raku;

method render($pod, Int :$foo=42, Bool :$bar = True) {
    warn %( :$foo, :$bar, args => @*ARGS ).raku;
    warn $pod.raku.substr(0, 10) ~ '...';
}

when run with:  raku --doc=Raku lib/Pod/To/PDF/Lite.rakumod --foo=12 --/bar, outputs:
 {:args($["--foo=12", "--/bar"]), :bar(Bool::True), :foo(42)}
  in method render at /tmp/lib/Pod/To/Raku.rakumod (Pod::To::Raku) line 4
$[Pod::Blo...
  in method render at /tmp/lib/Pod/To/Raku.rakumod (Pod::To::Raku) line 5

Hi, David. I personally don't think that's the way to go. For arg handling, I think
it's better to write one's own driver program and handle args with either the sub MAIN way or one's own arg handler (which I prefer).

First thing.
The $pod variable is receiving an array of POD6 trees that are associated with the program processed by raku. This is all that is needed. The renderer then transforms the pod trees into some output form.
Rakudo assumes that when you call raku --doc=XXX  there is a distribution that provides a class Pod::To::XXXX and that class has a method render.
Second: Beware !! There is a bug in Rakudo, so that the render method is called twice. The workaround is to have some sort of state variable to track when render is called first, returning the rendered content, and then on the second time just return the rendered content.
Third, I have written a general renderer  which uses templates. It also allows for custom headers and custom FormattingCodes. For example, I have included a block =graphviz that generates a png from the dot description of a graph.
So, rather then working out how to deal with every Pod Block that might occur and generating pdf, you could write the templates for pdf output.
This might be easier because things like =item for lists and =defn take some thinking about.

Thanks all.
I'm using custom parsing, as suggested by Tom:
 for @*ARGS {
            when /^'--page-numbers'$/  { $page-numbers = True }
            when /^'--width='(\d+)$/   { $width  = $0.Int }
            when /^'--height='(\d+)$/  { $height = $0.Int }
            when /^'--save-as='(.+)$/  { $pdf-file = $0.Str }
            default { note "ignoring $_ argument" }
        }


Frost Spell Alerts are sideways

Reported by Nemo296 over CurseForge https://legacy.curseforge.com/wow/addons/spellactivationoverlay/#c354

Hi, when playing frost mage, the textures are sideways. Example, if the Fingers of Frost procs are suppose to be like this ( ) they're like ⌢ ⌢ and brainfreeze is ( when it's suppose to be ⌢ .
This is not the location, they are in the correct locations, but the textures are rotated.

This is probably due to the texture embedded in Cataclysm game files that has a different rotation than Modern WoW. Rotating the texture CW or CCW should fix it, but it should be done only for Cataclysm.

Hi! Most texture orientations have been fixed by the recent update, but not the freeze one (on top when an enemy is frozen): it still shows up in the wrong orientation. What's weird is that in the visual tests (hovering over the spell alert in settings), the texture is oriented properly, but not when triggered by the "enemy frozen" state.
Additionally, I noticed that the frozen texture does not show up when enemies are frozen by Improved Cone of Cold, if you happen to have a quick fix in hand. I can file a separate issue otherwise if you prefer.

Hi @serenity4 and thank you for your feedback. Mages will get some love in the next release. Both issues you mentioned will be fixed (among others).
I re-opened this issue because the Freeze debuff texture has wrong orientation, which is exactly the kind of problems pointed out in the original text.


Listener if the user click the browser BACK button

Hello
I checked the API serching for a 'browser BACK listener' but i didn't find it.
Is there a listener to run if the user click the browser back button ?
Because i want to reset the some params in the body to the initial state.
Sample case:
1. Index load -> background white
2. user hover a link and i change the background to blue ( because that page linked has background blue)
3. page with the blue background loaded using barba.
Now if the user click the browser back button he is going to see the index with the background blue. And should be white like when he load the page via url
So in case there is no listener for that, can i at least change the document stored by barba for the back link ?

Something like this should help...
let linkClicked = false

Dispatcher.on('linkClicked', () => {
  linkClicked = true
})

Dispatcher.on('initStateChange', ( => {
  if (!linkClicked) {
    console.log('state changed without a link being clicked... back button?')
  }
})

Dispatcher.on('transitionCompleted', () => {
  linkClicked = false
})

was looking for a solution to this myself, saw a comment on https://www.bountysource.com/issues/35867798-barba-js-v2-open-discussion by @bramcordie that did the trick for me (had to switch some lines though).
Leaving this here so it may help someone else.
var popping = false;

window.addEventListener('popstate', function () {
  popping = true;
});

Barba.Pjax.start();

Barba.Pjax.getTransition = function() {
  return popping ? HideShowTransition : FadeTransition;
};

Barba.Dispatcher.on('initStateChange', function() {
  popping = false;
});

or set popping false on click
var lastElementClicked;
Barba.Dispatcher.on("linkClicked", function(el) {
  lastElementClicked = el;
  popping = false;
});


Show each parameter of procedure/function on a new line

Is your feature request related to a problem? Please describe.
I'm always frustrated when I read procedure name with multiple parameters in one line
Describe the solution you'd like
Automatically show each parameter on a new line with one level of indentation.
It makes code much easier to read and it is important for developers.
I want it automatically for all procedures/functions (maybe some new option in Preferences?).
But it seems to be it will be beneficial for all users.
Additional context
Here are screenshots: "as is" and "to be":

Use this code to debug:
CREATE OR REPLACE PROCEDURE public.proc2(IN parameter1 integer, IN parameter2 integer, IN parameter3 integer, IN parameter4 integer, IN parameter5 integer)
 LANGUAGE plpgsql
AS $procedure$
begin
   raise notice '1';
end;

$procedure$
;

Thank you for request


Fix data anonymizer failures by updating legacy parser.

Signed-off-by: Yury Fridlyand<EMAIL_ADDRESS>Description

Don't print query if error occurred:
https://github.com/Bit-Quill/opensearch-project-sql/blob/d9d25ad01837427f83e27cdecaf1477582d31bef/legacy/src/main/java/org/opensearch/sql/legacy/utils/QueryDataAnonymizer.java#L40-L44
Don't validate tokens' type in [], fixes processing functions with multiple fields:
https://github.com/Bit-Quill/opensearch-project-sql/blob/d9d25ad01837427f83e27cdecaf1477582d31bef/legacy/src/main/java/org/opensearch/sql/legacy/parser/ElasticSqlExprParser.java#L149-L155
Don't process MATCH ... AGAINST clause, because it is overlayed by MATCH function. Fixes failure on MATCH function:
https://github.com/Bit-Quill/opensearch-project-sql/blob/d9d25ad01837427f83e27cdecaf1477582d31bef/legacy/src/main/java/org/opensearch/sql/legacy/parser/ElasticSqlExprParser.java#L501-L550

Issues Resolved
[WARN ][o.o.s.l.u.QueryDataAnonymizer] [...] Caught an exception when anonymizing sensitive data

TODO

[ ] Discuss
[ ] Confirm that we can remove support of MATCH ... AGAINST (Is it even supported BTW?)
[ ] Test it - WIP

Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

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.

Don't process MATCH ... AGAINST clause...

This fix damages support of this clause, but it was working ever. I failed to run it on OpenSearch 1.1 with plugin pre-match support (commit 012cc0321).
According to the article MATCH ... AGAINST provides full-text search for MySQL. Meanwhile, OpenSearch provides a set of full text search (relevance based search) functions which are much more flexible, see https://github.com/opensearch-project/sql/issues/182.
I don't think that we need to keep support for MATCH ... AGAINST especially in the legacy parser.

We need an anonymizer that works with the new engine. At some point the legacy engine goes will go away.
Until that happens, I think it's best if QueryDataAnonymizer.anonymizeData works similarly to how queries are processed -- try new engine first, if it fails -- try legacy engine, if it fails -- error out.
This way we we gain an anonymizer for the new SQL engine, avoid changing the legacy parser, and avoid regressions in anonymizer when legacy engine is removed.
Anonymizer for the new SQL engine would have a lot in common with PPL anonymizer. Probably will make sense to have a common subclass.
What do you think?


[GUI] Fix GUI cloning

Related forum issue: https://forum.babylonjs.com/t/cloning-meshes-with-gui/40430

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/13806/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13806/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13806/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/13806/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/13806/merge
https://gui.babylonjs.com/?snapshot=refs/pull/13806/merge
https://nme.babylonjs.com/?snapshot=refs/pull/13806/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/13806/merge#BCU1XR#0


Add support for Actions Semi ATB1103 MCU and EVB

Hello,
This PR adds support for Actions Semi ATB1103 MCU and its evaluation board. ATB1103 is part of the  Low power Bluetooth MCUs family (ATB110X) from Actions Semi. The target applications for this MCU are BLE Voice Remote, Smart wearable devices, Smart Home sensors, and BT Mesh device applications. The EVB (Golden board) is designed and manufactured by Actions Semi for their internal use but there are few commercial target boards available for this MCU as well.
This PR is based on the initial code support for the MCU and board developed by Actions Semi and hence the copyrights are shared based on the contributions.
Thanks,
Mani

@galak Any update on this PR?

@Mani-Sadhasivam there seems to be a conflict with upstream (with include/arch/arm/cortex_m/scripts/linker.ld so could you please rebase? You might also want to take look at whether fixing the warnings from checkpatch makes sense (there are no errors though).
There are also essentially no reviews from codeowners, so could the assigned reviewers please take a look?

Can you shrink the boards/arm/atb1103_golden/doc/img/atb1103_golden.jpg, 4M is kinda big.

Done

The compats for DTS, do you think the names cover other actions semi MCUs? Just wondering if there is some family name or something to use?

atb110x is the family name, hence added that to board compatible.

@galak Addressed the comments

@galak ping! This seems to be stuck for months now

Need to update to new dts macros

@galak There is no DT gpio used in this PR hence not sure what I should convert. Can you please point to it?

Need to update to new dts macros

@galak There is no DT gpio used in this PR hence not sure what I should convert. Can you please point to it?

@galak There is no DT gpio used in this PR hence not sure what I should convert. Can you please point to it?

All the DT_INST_{0..9} macros are deprecated and replaced with macros from include/devicetree.h.  Just look most any driver at this point and you'll see something like DT_INST_PROP(0, foobar) or the like.

 Thought you were asking to cleanup DT gpio (it's too late here :P)

-:101: WARNING:SPDX_LICENSE_TAG: Missing or malformed SPDX-License-Identifier tag in line 1
#101: FILE: boards/arm/atb1103_golden/atb1103_golden.dts:1:

Please ignore these warnings (see #24921)

@carlescufi @galak Ping!

Hi @carlescufi @galak, Any update on this one as well?

@ioannisg @galak could you take a look?

@Mani-Sadhasivam could you please send an email to the devel@ mailing list asking for reviewers for this PR?


[mingw] build failure

Operating system
Windows 10
Compiler
No response
Steps to reproduce the behavior
I was following instructions on building openetelemetry-cpp via cmake, here's the github page link - build-instructions-using-cmake. I encounter this error when running step # 2, command cmake ... The issue happens when it attempts to download the mingw package from https://mirror.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst and encounters a 404 error. When I try to open this link on the browser, I see the same error message. I'm not using any http proxy either. Can someone please help resolve this issue? Thanks!
Failure logs
cmake ..
-- Selecting Windows SDK version 10.0.22621.0 to target Windows 10.0.19045.
-- Building for architecture ARCH=x64
-- OPENTELEMETRY_ABI_VERSION_NO=1
-- OPENTELEMETRY_VERSION=1.12.0
-- nlohmann::json dependency satisfied by: git submodule
-- Using the multi-header code from C:/OpenTelemetry/opentelemetry-cpp/third_party/nlohmann-json/include/
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Installing build tools and dependencies...

C:\OpenTelemetry\opentelemetry-cpp\build>REM Copyright The OpenTelemetry Authors

C:\OpenTelemetry\opentelemetry-cpp\build>REM SPDX-License-Identifier: Apache-2.0
Running with Administrative privilege...
'choco' is not recognized as an internal or external command,
operable program or batch file.
Visual Studio installations detected:
'vswhere' is not recognized as an internal or external command,
operable program or batch file.
Building with vs2022 Professional...

** Visual Studio 2022 Developer Command Prompt v17.7.1
** Copyright (c) 2022 Microsoft Corporation

[vcvarsall.bat] Environment initialized for: 'x64'
Using existing vcpkg installation...
Computing installation plan...
error: while looking for gtest:x64-windows:
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\vcpkg\ports\gtest: error: gtest does not exist
Computing installation plan...
The following packages will be built and installed:
benchmark:x64-windows -> 1.5.3 -- C:\OpenTelemetry\opentelemetry-cpp\tools\ports\benchmark
Detecting compiler hash for triplet x64-windows...
Restored 0 package(s) from C:\Users\shivtyagi\AppData\Local\vcpkg\archives in 266 us. Use --debug to see more details.
Installing 1/1 benchmark:x64-windows...
Building benchmark:x64-windows...
-- Installing port from location: C:\OpenTelemetry\opentelemetry-cpp\tools\ports\benchmark
CMake Warning at scripts/cmake/vcpkg_fail_port_install.cmake:2 (message):
vcpkg_fail_port_install has been removed and all values should be moved by
adding supports field to manifest file or directly adding
benchmark:=fail to scripts/ci.baseline.txt.

Please remove vcpkg_fail_port_install(...).

Call Stack (most recent call first):
C:/OpenTelemetry/opentelemetry-cpp/tools/ports/benchmark/portfile.cmake:13 (vcpkg_fail_port_install)
scripts/ports.cmake:147 (include)

-- Note: benchmark only supports static library linkage. Building static library.
-- Using cached google-benchmark-c05843a9f622db08ad59804c190f98879b76beba.tar.gz.
-- Cleaning sources at C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/vcpkg/buildtrees/benchmark/src/879b76beba-25008a53f3.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/vcpkg/downloads/google-benchmark-c05843a9f622db08ad59804c190f98879b76beba.tar.gz
-- Applying patch version.patch
-- Using source at C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/vcpkg/buildtrees/benchmark/src/879b76beba-25008a53f3.clean
-- Found external ninja('1.11.0').
-- Configuring x64-windows
CMake Warning at scripts/cmake/vcpkg_configure_cmake.cmake:384 (message):
The following variables are not used in CMakeLists.txt:

  CMAKE_DEBUG_POSTFIX
Please recheck them and remove the unnecessary options from the
vcpkg_configure_cmake call.

If these options should still be passed for whatever reason, please use the
MAYBE_UNUSED_VARIABLES argument.
Call Stack (most recent call first):
C:/OpenTelemetry/opentelemetry-cpp/tools/ports/benchmark/portfile.cmake:26 (vcpkg_configure_cmake)
scripts/ports.cmake:147 (include)

-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Fixing pkgconfig file: C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/vcpkg/packages/benchmark_x64-windows/lib/pkgconfig/benchmark.pc
-- Using cached mingw-w64-i686-pkg-config-0.29.2-3-any.pkg.tar.zst.
-- Downloading https://mirror.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst;https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst;https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst;https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst;https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst;https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst -> mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst...
[DEBUG] To include the environment variables in debug output, pass --debug-env
[DEBUG] Trying to load bundleconfig from C:\Github\vcpkg\vcpkg-bundle.json
[DEBUG] Failed to open: C:\Github\vcpkg\vcpkg-bundle.json
[DEBUG] Bundle config: readonly=false, usegitregistry=false, embeddedsha=nullopt, deployment=Git, vsversion=nullopt
[DEBUG] Metrics enabled.
[DEBUG] Feature flag 'binarycaching' unset
[DEBUG] Feature flag 'compilertracking' unset
[DEBUG] Feature flag 'registries' unset
[DEBUG] Feature flag 'versions' unset
[DEBUG] Feature flag 'dependencygraph' unset
Downloading https://mirror.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst
Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst
Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst
Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst
Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst
Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst
error: Failed to download from mirror set
error: https://mirror.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst: failed: status code 404
error: https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst: failed: status code 404
error: https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst: failed: status code 404
error: https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst: failed: status code 404
error: https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst: failed: status code 404
error: https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst: failed: status code 404
[DEBUG] D:\a_work\1\s\src\vcpkg\base\downloads.cpp(1048):
[DEBUG] Time in subprocesses: 0us
[DEBUG] Time in parsing JSON: 13us
[DEBUG] Time in JSON reader: 0us
[DEBUG] Time in filesystem: 4547us
[DEBUG] Time in loading ports: 0us
[DEBUG] Exiting after 3.9 s (3842907us)

CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:32 (message):

  Failed to download file with error: 1
  If you are using a proxy, please check your proxy setting. Possible causes are:

  1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable
     to `https://address:port`. This is not correct, because `https://` prefix
     claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr
     , etc..) is an HTTP proxy. Try setting `http://address:port` to both
     HTTP_PROXY and HTTPS_PROXY instead.

  2. If you are using Windows, vcpkg will automatically use your Windows IE Proxy Settings
     set by your proxy software. See https://github.com/microsoft/vcpkg-tool/pull/77
     The value set by your proxy might be wrong, or have same `https://` prefix issue.

  3. Your proxy's remote server is out of service.

  If you've tried directly download the link, and believe this is not a temporary
  download server failure, please submit an issue at https://github.com/Microsoft/vcpkg/issues
  to report this upstream download server failure.
Call Stack (most recent call first):
scripts/cmake/vcpkg_download_distfile.cmake:270 (z_vcpkg_download_distfile_show_proxy_and_fail)
scripts/cmake/vcpkg_acquire_msys.cmake:25 (vcpkg_download_distfile)
scripts/cmake/vcpkg_acquire_msys.cmake:124 (z_vcpkg_acquire_msys_download_package)
scripts/cmake/vcpkg_acquire_msys.cmake:209 (z_vcpkg_acquire_msys_download_packages)
scripts/cmake/vcpkg_find_acquire_program(PKGCONFIG).cmake:22 (vcpkg_acquire_msys)
scripts/cmake/vcpkg_find_acquire_program.cmake:118 (include)
scripts/cmake/vcpkg_fixup_pkgconfig.cmake:203 (vcpkg_find_acquire_program)
C:/OpenTelemetry/opentelemetry-cpp/tools/ports/benchmark/portfile.cmake:40 (vcpkg_fixup_pkgconfig)
scripts/ports.cmake:147 (include)

error: building benchmark:x64-windows failed with: BUILD_FAILED
Elapsed time to handle benchmark:x64-windows: 14 s
Please ensure you're using the latest port files with git pull and vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+benchmark
You can submit a new issue at:
[https://github.com/microsoft/vcpkg/issues/new?title=[benchmark]+Build+error+on+x64-windows&body=Copy+issue+body+from+C%3A%2FProgram%20Files%2FMicrosoft%20Visual%20Studio%2F2022%2FProfessional%2FVC%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md](https://github.com/microsoft/vcpkg/issues/new?title=%5Bbenchmark%5D+Build+error+on+x64-windows&body=Copy+issue+body+from+C%3A%2FProgram%20Files%2FMicrosoft%20Visual%20Studio%2F2022%2FProfessional%2FVC%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md)

Computing installation plan...
The following packages will be built and installed:
protobuf:x64-windows -> 3.15.8#2 -- C:\OpenTelemetry\opentelemetry-cpp\tools\ports\protobuf
Detecting compiler hash for triplet x64-windows...
Restored 0 package(s) from C:\Users\shivtyagi\AppData\Local\vcpkg\archives in 251 us. Use --debug to see more details.
Installing 1/1 protobuf:x64-windows...
Building protobuf:x64-windows...
-- Installing port from location: C:\OpenTelemetry\opentelemetry-cpp\tools\ports\protobuf
-- Using cached protocolbuffers-protobuf-436bd7880e458532901c58f4d9d1ea23fa7edd52.tar.gz.
-- Cleaning sources at C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/vcpkg/buildtrees/protobuf/src/23fa7edd52-47d9944e09.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/vcpkg/downloads/protocolbuffers-protobuf-436bd7880e458532901c58f4d9d1ea23fa7edd52.tar.gz
-- Applying patch fix-static-build.patch
-- Applying patch fix-default-proto-file-path.patch
-- Applying patch port_def.patch
-- Using source at C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/vcpkg/buildtrees/protobuf/src/23fa7edd52-47d9944e09.clean
-- Found external ninja('1.11.0').
-- Configuring x64-windows
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Fixing pkgconfig file: C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/vcpkg/packages/protobuf_x64-windows/lib/pkgconfig/protobuf-lite.pc
-- Fixing pkgconfig file: C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/vcpkg/packages/protobuf_x64-windows/lib/pkgconfig/protobuf.pc
-- Using cached mingw-w64-i686-pkg-config-0.29.2-3-any.pkg.tar.zst.
-- Downloading https://mirror.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst;https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst;https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst;https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst;https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst;https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst -> mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst...
[DEBUG] To include the environment variables in debug output, pass --debug-env
[DEBUG] Trying to load bundleconfig from C:\Github\vcpkg\vcpkg-bundle.json
[DEBUG] Failed to open: C:\Github\vcpkg\vcpkg-bundle.json
[DEBUG] Bundle config: readonly=false, usegitregistry=false, embeddedsha=nullopt, deployment=Git, vsversion=nullopt
[DEBUG] Metrics enabled.
[DEBUG] Feature flag 'binarycaching' unset
[DEBUG] Feature flag 'compilertracking' unset
[DEBUG] Feature flag 'registries' unset
[DEBUG] Feature flag 'versions' unset
[DEBUG] Feature flag 'dependencygraph' unset
Downloading https://mirror.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst
Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst
Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst
Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst
Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst
Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst
error: Failed to download from mirror set
error: https://mirror.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst: failed: status code 404
error: https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst: failed: status code 404
error: https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst: failed: status code 404
error: https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst: failed: status code 404
error: https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst: failed: status code 404
error: https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst: failed: status code 404
[DEBUG] D:\a_work\1\s\src\vcpkg\base\downloads.cpp(1048):
[DEBUG] Time in subprocesses: 0us
[DEBUG] Time in parsing JSON: 11us
[DEBUG] Time in JSON reader: 0us
[DEBUG] Time in filesystem: 4731us
[DEBUG] Time in loading ports: 0us
[DEBUG] Exiting after 3.8 s (3736297us)

CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:32 (message):

  Failed to download file with error: 1
  If you are using a proxy, please check your proxy setting. Possible causes are:

  1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable
     to `https://address:port`. This is not correct, because `https://` prefix
     claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr
     , etc..) is an HTTP proxy. Try setting `http://address:port` to both
     HTTP_PROXY and HTTPS_PROXY instead.

  2. If you are using Windows, vcpkg will automatically use your Windows IE Proxy Settings
     set by your proxy software. See https://github.com/microsoft/vcpkg-tool/pull/77
     The value set by your proxy might be wrong, or have same `https://` prefix issue.

  3. Your proxy's remote server is out of service.

  If you've tried directly download the link, and believe this is not a temporary
  download server failure, please submit an issue at https://github.com/Microsoft/vcpkg/issues
  to report this upstream download server failure.
Call Stack (most recent call first):
scripts/cmake/vcpkg_download_distfile.cmake:270 (z_vcpkg_download_distfile_show_proxy_and_fail)
scripts/cmake/vcpkg_acquire_msys.cmake:25 (vcpkg_download_distfile)
scripts/cmake/vcpkg_acquire_msys.cmake:124 (z_vcpkg_acquire_msys_download_package)
scripts/cmake/vcpkg_acquire_msys.cmake:209 (z_vcpkg_acquire_msys_download_packages)
scripts/cmake/vcpkg_find_acquire_program(PKGCONFIG).cmake:22 (vcpkg_acquire_msys)
scripts/cmake/vcpkg_find_acquire_program.cmake:118 (include)
scripts/cmake/vcpkg_fixup_pkgconfig.cmake:203 (vcpkg_find_acquire_program)
C:/OpenTelemetry/opentelemetry-cpp/tools/ports/protobuf/portfile.cmake:120 (vcpkg_fixup_pkgconfig)
scripts/ports.cmake:147 (include)

error: building protobuf:x64-windows failed with: BUILD_FAILED
Elapsed time to handle protobuf:x64-windows: 41 s
Please ensure you're using the latest port files with git pull and vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+protobuf
You can submit a new issue at:
[https://github.com/microsoft/vcpkg/issues/new?title=[protobuf]+Build+error+on+x64-windows&body=Copy+issue+body+from+C%3A%2FProgram%20Files%2FMicrosoft%20Visual%20Studio%2F2022%2FProfessional%2FVC%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md](https://github.com/microsoft/vcpkg/issues/new?title=%5Bprotobuf%5D+Build+error+on+x64-windows&body=Copy+issue+body+from+C%3A%2FProgram%20Files%2FMicrosoft%20Visual%20Studio%2F2022%2FProfessional%2FVC%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md)

Computing installation plan...
error: while looking for ms-gsl:x64-windows:
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\vcpkg\ports\ms-gsl: error: ms-gsl does not exist
Computing installation plan...
error: while looking for nlohmann-json:x64-windows:
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\vcpkg\ports\nlohmann-json: error: nlohmann-json does not exist
Computing installation plan...
error: while looking for abseil:x64-windows:
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\vcpkg\ports\abseil: error: abseil does not exist
Computing installation plan...
error: while looking for grpc:x64-windows:
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\vcpkg\ports\grpc: error: grpc does not exist
Computing installation plan...
error: while looking for prometheus-cpp:x64-windows:
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\vcpkg\ports\prometheus-cpp: error: prometheus-cpp does not exist
Computing installation plan...
error: while looking for curl:x64-windows:
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\vcpkg\ports\curl: error: curl does not exist
Computing installation plan...
error: while looking for thrift:x64-windows:
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\vcpkg\ports\thrift: error: thrift does not exist
Make sure that vcpkg.cmake is set as the CMAKE_TOOLCHAIN_FILE at the START of the cmake build process!
Can be command-line arg (cmake -DCMAKE_TOOLCHAIN_FILE=...) or set in your editor of choice.
CMake Error at C:/Program Files/CMake/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR
GTEST_MAIN_LIBRARY)
Call Stack (most recent call first):
C:/Program Files/CMake/share/cmake-3.15/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE)
C:/Program Files/CMake/share/cmake-3.15/Modules/FindGTest.cmake:197 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
C:/Github/vcpkg/scripts/buildsystems/vcpkg.cmake:859 (_find_package)
CMakeLists.txt:606 (find_package)

-- Configuring incomplete, errors occurred!
See also "C:/OpenTelemetry/opentelemetry-cpp/build/CMakeFiles/CMakeOutput.log".
See also "C:/OpenTelemetry/opentelemetry-cpp/build/CMakeFiles/CMakeError.log".

Additional context
No response

I would suggest opening an issue with the maintainers at https://github.com/open-telemetry/opentelemetry-cpp as the embedded vcpkg link points to a commit that pulls older versions of msys2/mingw libraries no longer available for download.

I would suggest opening an issue with the maintainers at https://github.com/open-telemetry/opentelemetry-cpp as the embedded vcpkg link points to a commit that pulls older versions of msys2/mingw libraries and tools no longer available for download.

I suspect it is a problem with one of the dependencies, and not opentelemetry-cpp itself. I am trying to build my own code, I don't use opentelemetry, and a different dependency (zlib:x64-windows in my case) results in the exactly same error.

Note that you can also turn the setup around: Don't let opentelemetry-cpp install vcpkg to handle it is dependencies, but use vcpkg directly to install opentelemetry-cpp.

@tashivani I would like to suggest editing the title to: "opentelemetry-cpp uses outdated vcpkg". It is not really related to mingw.
In the end this also makes it clear that this issue belongs to them, not to vcpkg...

Thanks @jimwang118 for editing the title! Should I close this issue now since I already have another issue open on opentelemetry-cpp repo?

Thanks @jimwang118 for editing the title! Should I close this issue now since I already have another issue open on opentelemetry-cpp repo?

If your issue is resolved, you can close this issue.


[SPARK-6458][SQL] Better error messages for invalid data sources

Avoid unclear match errors and use AnalysisException.

Test build #29061 has started for   PR 5158 at commit 90c6ba4.

This patch merges cleanly.

Test build #29061 has finished for   PR 5158 at commit 90c6ba4.

This patch passes all tests.

This patch merges cleanly.

This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/29061/
Test PASSed.

LGMT (just a minor comment)

Test build #29099 has started for   PR 5158 at commit af9f82a.

This patch merges cleanly.

Test build #29099 has finished for   PR 5158 at commit af9f82a.

This patch passes all tests.

This patch merges cleanly.

This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/29099/
Test PASSed.


[FEATURE]: Create the LinkModalTrigger component for the Storybook

Is your feature request related to a problem?
This component is part of a reusable design system for Fonoster’s dashboard. It helps achieve consistency and reduces repetitive implementation work.

Describe the solution you'd like
The LinkBackTrigger should follow the design in the Figma file and be implemented as a standalone React component with the following props: onClick, disabled.

It should use MUI styles for styling
The component must have basic tests using

Describe alternatives you've considered
NA
Additional context
Before working on this item, please check the CONTRIBUTING document. Details about the LinkBackTrigger component can be found here.
Acceptance Criteria:

[ ] Matches Figma design
[ ] Storybook story with documentation
[ ] Works in light/dark themes
[ ] Includes basic unit tests

@psanders I can work on this issue

@Nageswari-droid, it is all yours 🙌

We are all set here. Thanks again @Nageswari-droid 🙏
(In relation to issue #679)


Visual unlocked for staking bug

After updating the NavPi it shows: "the wallet is unlocked for staking"
This is not the case, it is locked after update script. Unlocking the wallet for staking again will unlock it.

Same thing if you reboot the device. Not sure what to do here. I do want to resolve this though.

I haven't noticed this issue only on reboot, but I believe the problem is NavCoinlockstate.php has been checked into the main repo with Unlocked For Staking as the contents. So any update may overwrite the local change.
This file should really be removed from the repo, added a .gitignore, and appropriate checks done to set default state.

yes, we will remove it from the repo and add to git ignore. thanks!


Separate JSON-LD from MetaTags component

fix: #7

This will be a disruptive change, and we will improve it to make it compatible for at least a month or so.