Learn what happened from wechaty-puppet-padpro

Related to: https://github.com/botorange/wechaty-puppet-padpro/pull/191

Should fixed by #69


Unable to parse Apple Silicon M1

Failed to parse string since the modelline is Apple processor
........./node_modules/systeminformation/lib/cpu.js:418
          result.speed = modelline.split('@')[1].trim();
                                                ^

TypeError: Cannot read property 'trim' of undefined
    at / ......... /node_modules/systeminformation/lib/cpu.js:418:49
    at ChildProcess.exithandler (node:child_process:300:7)
    at ChildProcess.emit (node:events:376:20)
    at maybeClose (node:internal/child_process:1055:16)
    at Socket.<anonymous> (node:internal/child_process:441:11)
    at Socket.emit (node:events:376:20)
    at Pipe.<anonymous> (node:net:661:12)

@kenny-y I still wait for my M1 silicon hardware to arrive here ;-) ... will then extensively work on making System Information fully compatible with Apple ARM processors! Thank you for reporting. As you already done ... if you discover more issues please add "Apple Silicon M1" to the title. Thank you in advance.

I manually append '@0GHz` to the string as a quick hack and all the rest works (at least no exceptions thrown). I'll report more if I hit any issues.

BTW. I'm using ARM64 Node.js v15 compiled by this link: https://www.reddit.com/r/apple/comments/jyfg4m/nodejs_running_native_on_apple_silicon_m1_mac_mini/

@kenny-y good to know! This is what I am also aiming for!
Concerning this issue, I now added some code to catch this correctly (not yet published) but of course there is much more to do then as soon as I have the hardware here. Thank you for your support!

@kenny-y: This part of the code Is now released. Version 4.03.11 just published. Leaving this open while waiting for Apple silicon hardware.

@kenny-y - I just opened a new pinned issue to track complete Apple silicon compatibility: #453
As I will get the new hardware the next few days I there will report all findings.

Apple M1 compatibility mostly down. Version 4.33.0 just published.


Testing protocol

Primary: Chinweoke | Backup: Lori
Draft testing protocol based on template provided by Tianyi (BCO).

I received the protocol from Chinweoke, and will circulate it internally to obtain any final feedback/edits.

Hi @ChinweokeO can you implement the changes we discussed today on the testing protocol?

Update instructions & example text given new checkbox feature
Update content to include all interactions (use the Figma mockups to cross-reference from the features spreadsheet)
Add statements in Column C for each item.
Add Toolbar & Footer testing content to each new page of the application
Add MG - Upload section

Don't hesitate to reach out if you have any other comments/questions. If you don't think you'll get to this by the end of the month, please let me know. Thanks!


Fission is a Keda user now

Signed-off-by: Vishal Biyani<EMAIL_ADDRESS>Fission is using Keda as a way to integrate & scale various event sources for executing Fission functions, more details here:  https://blog.fission.io/posts/event-driven-scaling-fission-function-using-keda
CC @therahulbhati

Thanks for using KEDA, happy to have you on board!


Update Colcon-Tutorial.rst

clarification

Personally, I'm a fan of using a comma in this case, although the "then" is just extra. I would vote in favour of this change, but I understand that this is kind of opening the door to a ton of tiny, sometime subjective (depending on grammatical preferences, and sometimes native languages) changes like this one.

I can remove the "then" if it sounds heavy. The reason of my pull request is that reading the documentation I found difficult to understand the period, I had to read it many times. I am not a motherlanguage, but I am pretty sure that condition and consequence should be separated by a comma to be more readable. Sincerely, I added the "then" because it was embarrassing for me to open a pull request only for a comma.
Anyway, I didn't want to open a controversy about a comma. Feel free to do whatever you want with this doc, I only provided my opinion.

Ok, thank you for your suggestion.


Bullet point with fix for front door 503 error could be clearer

The bullet point
'If going through Azure Front Door results in a 503 error response code, configure the sendReceiveTimeout field for Azure Front Door. You can extend the default timeout up to 4 minutes (240 seconds). The setting is under backendPoolSettings and is called sendRecvTimeoutSeconds.'
Could be clearer, the setting is under the general settings tab on the Front Door Designer page, as apposed to under the settings for a given backend. Possible change of wording to make this a clearer guidance to resolve the issue?

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

ID: 42cb8651-4d1d-4031-ad64-93fc7a2c0c6c
Version Independent ID: d2f0f0f6-378b-d3e9-b5de-59ab8ac71c72
Content: Troubleshoot Azure Front Door configuration problems
Content Source: articles/frontdoor/front-door-troubleshoot-routing.md
Service: frontdoor
GitHub Login: @duongau
Microsoft Alias: duau

Hello @MThomas564
Thank you for your feedback! We will review and update as appropriate.

@MThomas564 I have made updates to the doc to reflect the correct steps to access that field. Screenshots are also include for reference.
Thank you!
#please-close


always return answer without context file

i have upload a file.txt.
i wish i can get answer from the file content.
in chat mode:
but it always generate answer random.
if i say 'response me based on the context',it will generate answer based on my file.txt.
in query mode:
it always tell me no relevent content found and it tell me right answer base on file.txt if i ask it "response me based on the context".
llm model: gpt-3.5-turbo.
embed model: buildin model.
vector db: built-in database.

@shatfield4

if i pin the file,all things work well.


[WIP] Feature/The Amicable Node-Preprint Divorce [PLAT-555][PLAT-480][PLAT-559]

❗ Dependent on Erin's Upload-to-Anything
❗❗ This is big, but not as big as it looks. A lot of the changes are just a model name change and referencing fields on the preprint instead of the node. And tests. Lots of tests.
Purpose
Removes the dependency of Preprints on Nodes.  Nodes can house supplemental files for a preprint, but beyond that, Preprints are their own thing.
TODO List

[ ] Test copying file from node to preprint w/ WB request. Not yet working locally - region errors?
[ ] API v2 move/copy hooks need to be adapted for preprints
[ ] Docs for new API version once all the fields we're deprecating are set.
[ ] Elastic search - migrating preprints: need a delete function, and may need to rewrite migrate_preprints in SQL
[ ] Elastic search - add tests that preprints indices were migrated correctly
[ ] Elastic search - file index migration should not migrate files attached to the preprint that are not the primary file? (unlikely case, but possible)
[ ] Elastic search - what do we do about nodes that are currently indexed as preprints?
[ ] Data migration - reverse migration needs testing
[ ] Data migration - OPTIMIZE, test on large data dump
[ ] SHARE - are Preprints updates working, sending preprint fields instead of node fields?
[ ] Legacy front-end changes [ON HOLD] - need feedback from product
[ ] Node model - remove obsolete fields (will be last step, after legacy front-end changes)
[ ] Schema migration to move obsolete fields off of node
[ ] Verify no issues with Preprint model ContentType now that name has been changed.
[ ] Obsolete email links related to nodes on preprints?
[ ] Document changes to API requests for creating a preprint.

Changes
Too many to list, here are some of them.
Admin App

Preprints are their own thing in the admin app, not relying on node fields
You can modify contributors directly, flag preprints as spam, and reindex preprints in elastic search
Several node templates/views made more generic to work with nearly-identical preprints

API

Preprint endpoints are looking at preprint fields, not node fields.
PreprintProviderList endpoint and PreprintFiles list endpoint added (to expose OSFStorage Waterbutler endpoints for uploading primary file
New process for creating a preprint 1) POST to v2/preprints/ (title, provider are required fields) 2) Use WB links to upload or move file to created preprint 3) PATCH to v2/preprints/<preprint_id>/ to finish up process.
New preprints scopes added now that preprints/nodes are separate

Elastic Search

Nodes are no longer indexed in Elastic Search as preprints, the preprint itself is indexed
Changes to reindexing

Modeling

New PreprintLog and PreprintContributor models
New ContributorMixin to share contributor-related methods between Nodes and Preprints
New SpamOverrideMixin to share spam-methods between Nodes and Preprints
Preprints uses Django-guardian for contributor permissions
Write contributors have been upgraded to have more permissions - can edit most things on a submitted preprint except publishing, withdrawing, etc.
Preprints do not have addons, so a few OSFStorage methods have been moved to the preprint.
UploadMixin added to Preprint that creates a root folder for storage

Preprint File

Stored on preprint instead of node
Some OSFStorage methods modified to handle permission checking on preprint in addition to node
Preprints have regions (by default, same region as UserSettings, in migration, pulls region off of node).

Legacy UI
TODO - need language verification from Product.
QA Notes

Side Effects

Ticket

Replaced by https://github.com/CenterForOpenScience/osf.io/pull/8422


review the current s3 config

The current way leads to problems such as this

Outside of the issue you list, I've never seen any problems with Cookiecutter Django's setup. None of the many other image packages cause any problems to the best of my knowledge. The conclusion I draw is that the issue is with sorl-thumbnail and not Cookiecutter Django's configuration. We play according to standard rules, apparently sorl-thumbnail does not.
I suggest you open an issue with sorl-thumbnail.

Thanks @pydanny. I guess this was already seen by sorl-thumbnail's crew. Should I insist there then? :)


Getting data before deserialization

Hello - would like to ask what you think about the following:
When registering a callback to receive messages, the library code will by default call utils.DeserializeDataFromString on the message and pass a map[string]interface{} to the callback.
If the client code wants to unmarshall the message directly to a struct it has serialize then deserialize again or do an awful lot of copying and casting. Do you think it makes sense to pass back bytes instead?

Yeah, it will probably look into it. But, i am sure you will need some mechanism to convert bytes to struct.. or a proper json struct model.


in packages without exports, look for proxy directories instead

Right now, we're stuck without an exports field in @apollo/client v3 - we are aiming to add one with v4, but there is no immediate update around the corner.
I'd love to use attw for all our entry points though - so this would look for all package.json files within a project and use those as entry points.

Hey, thanks for the contribution! I think I’m ok with this if we add a check that the proxy directory package.json files contain a "main" field. I’m thinking about cases where someone drops a {} or { "type": "module" } package.json in a directory to change the module format of a particular directory. Those would turn up as a false positive here, although that pattern feels unlikely to occur without root level exports.
Have you seen #40? I was planning just to let people pass in a list. Maybe this is a good start though, especially for the web client.

@andrewbranch that sounds like a very good sanity check - I've added it.
I've just seen #40 a few minutes ago - it seems like a good additional way to take, but we want to add this in CI, so something like this that automatically detects new entry points would be much preferred - I'm afraid that at some point we forget to add a new entry point to a manually managed list, and miss errors introduced that way.

I think this is good to go. Would you mind adding a changeset with a minor bump for the core package?

Sure, I just added one :)

Thanks! This will deploy to the web immediately. I’m hoping to get a couple other random fixes for stuff in today/tomorrow and do an npm release then.

Sounds great :) Thank you for looking at this so fast!


Enchantment: Don't close the injector after injecting

I love the fork, works flawlessly and is so nice to have again the skin changer working, but a very small change compared to the original is that the injector closes after injecting, forcing to reopen it every match.
Is just removing 2 lines, not big deal.
https://github.com/R3nzTheCodeGOD/R3nzSkin/blob/a349e3390ba02bce266b1e5ffcea0fb93212548e/R3nzSkin_Injector/R3nzSkin_Injector.cpp#L144-L146

i guess he added the closing idea bc like if u r streaming or sharing ur screen in discord noone will know that u r using the prog

I love the fork, works flawlessly and is so nice to have again the skin changer working, but a very small change compared to the original is that the injector closes after injecting, forcing to reopen it every match.
Is just removing 2 lines, not big deal.
https://github.com/R3nzTheCodeGOD/R3nzSkin/blob/a349e3390ba02bce266b1e5ffcea0fb93212548e/R3nzSkin_Injector/R3nzSkin_Injector.cpp#L144-L146


add hpc filter option

This PR will have the hpc filter option.
Dependecy
To add it to the GUI, first we need to release the change done in https://github.com/BSC-ES/autosubmit-api/pull/134 to support search by HPC and wildcard usage.
Tasks

[x] Update code
[ ] Update the changelog to include the minimal version of the API that supports this new feature

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 54.65%. Comparing base (41e5ef7) to head (b179d05).

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #159      +/-   ##
==========================================
+ Coverage   54.59%   54.65%   +0.05%
==========================================
  Files          52       52
  Lines        1696     1698       +2
  Branches      228      228
==========================================
+ Hits          926      928       +2
  Misses        605      605
  Partials      165      165

Flag
Coverage Δ

fast-tests
54.65% <100.00%> (+0.05%)
:arrow_up:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests
JS Bundle Analysis - Avoid shipping oversized bundles


[e2e]: nodejs release main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/7580076893
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.release.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.release.main.default.slsa3.yml
Trigger: schedule
Branch: main
Date: Fri Jan 19 06:02:05 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v40.0.177
Run: https://github.com/slsa-framework/example-package/actions/runs/7599358962
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.release.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.release.main.default.slsa3.yml
Trigger: release
Branch: v40.0.177
Date: Sun Jan 21 06:07:31 UTC 2024
Tests are passing now. Closing this issue.


fix android build: dex jumbo

@keybase/react-hackers the android build was failing. i think cause our binary was having too many methods (like we had on ios).
> com.android.build.api.transform.TransformException: com.android.ide.common.process.ProcessException: java.util.concurrent.ExecutionException: com.android.dex.DexIndexOverflowException: Cannot merge new index 65545 into a non-jumbo instruction!```

this pr adds the jumbo flag which lets us get over this limit.


fix(Interaction): backup / restore of materials

Materials are now cloned when backing them up so there is no way the ChangeToHighlightColor function can overwrite these settings.
Fixes https://github.com/thestonefox/VRTK/issues/844

There were the following issues with your Pull Request

Commit: 0260bc2eadbcf2ae3a74664d353f5f861b754829
Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/thestonefox/SteamVR_Unity_Toolkit

This message was auto-generated by https://gitcop.com

I'd split these into separate pull requests.
The fix(Controls) one should be separate (and can be merged pretty much straight away)

This PR refers to issue https://github.com/thestonefox/VRTK/issues/844 and supersedes https://github.com/thestonefox/VRTK/pull/704. All credits for the Implementation of the MaterialPropertyBlock Highlighter go to fight4dream

@thestonefox you're so fast ;) just fixed it while trying the example to reproduce you posted at https://github.com/thestonefox/VRTK/issues/844

removed fix for the PanelMenuController and issued another PR at https://github.com/thestonefox/VRTK/pull/861 instead.

This PR now contains the merge of the other PR and implements the changes to the MaterialSwapHighlighter that breaks the draw call batching.
Is your intention to just submit a PR that has the MPB version of the highlighter, but all fixed up?
If so, i'd start a new PR and just have that as a single commit, don't bother merging the other PR from fight4dream just give him a mention in the commit description.
Then your commit will be one nice simple commit adding a new highlighter.

wups, sorry didn't notice the draw call batching breaker is still in there. Thought I'd removed that commit when rebasing. Anyways, I don't really like the idea of taking the work of others and remove their fingerprint. That's why I left the initial commit in there. However, it's your repo, so if that's how you like it, I'll rebase to one commit only.

Yeah I know what you mean, but in this case is probably better to have a commit that works rather than a commit that's broken with a further commit making it work.

There were the following issues with your Pull Request

Commit: a0995fa98c42352bc46e15c3deb9a1513e50f0b9
Your commit message body contains a line that is longer than 72 characters

Guidelines are available at https://github.com/thestonefox/SteamVR_Unity_Toolkit

This message was auto-generated by https://gitcop.com

alright then, condensed this PR to one commit which simply adds the MaterialPropertyBlock Highlighter as a new and viable options for cases where material instances are involved.

One last thing! then it's ready for merge :)
Just change the git commit message (with git commit --amend) from Interaction to Highlighters
so:
feat(Highlighters): add highlighter that uses MPB for material swap
(this is a bit more descriptive imho)
other than that it's good to go! ❤ 💚 💙 💛

There were the following issues with your Pull Request

Commit: db827a95788af2d38fc2b47c4d79491d80dae52b
Your commit message body contains a line that is longer than 72 characters

Guidelines are available at https://github.com/thestonefox/SteamVR_Unity_Toolkit

This message was auto-generated by https://gitcop.com

There were the following issues with your Pull Request

Commit: 7e9fc87579a3b73e0752f7630a6bfe13e72a88d6
Your commit message body contains a line that is longer than 72 characters

Guidelines are available at https://github.com/thestonefox/SteamVR_Unity_Toolkit

This message was auto-generated by https://gitcop.com


Log Admin activity

Resolves: #717
Description
Adds user activity logging in the security layer of the dashboard.
How Has This Been Tested?
User activity is logged into the adminActivity.log file in the logs folder in the src/ directory of the pod
Merge criteria:

[ ] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work

Assigning to @LaVLaS and @cfchase to make sure we work to a solution that will log appropriately. @maroroman please work with them to arrive at a solution that works for what SRE needs.

Closing this since in favor of #914


Import path shortened in form-field

Hii @crisbeto, @devversion please review the PR.

Hi can you please fix the lint job by using a commit message following the format: refactor: use improved relative import path in form-field

Hii @devversion , updated the commit as suggested. Please have a look!
Thank you!


Stock_predicter.ipynb: definition of y in 212

Thanks for your project.
In line 212 in Stock_predicter.ipynb you split the data: X_train, X_test, y_train, y_test = train_test_split(X, y, test_size=0.3)
How have you defined y in this statement?
Thank you

y is y_df_mod.Values. y_df_mod is declared in lines 204 205.
I think it was somehow replaced during uploads by mistake.
Thank you for pointing out.


Rework blob printing, add blob functions and add correct handling of blobs to parquet reader/writer

Python-style blob handling
This PR reworks blobs to be more similar to the way they are in Python 3. Blobs will no longer be printed as purely hexadecimal. Instead, any valid ASCII characters in the blob will be printed as ASCII, and other bytes will be printed with a hexadecimal escape code (\x..). For example, the (totally random string) mühleisen will now be printed as m\xC3\xBChleisen when stored in a blob. This matches the behavior of Python3, e.g. in Python3 'mühleisen'.encode('utf8') -> b'm\xc3\xbchleisen'.
To further match Python in blob handling, we add two functions: encode and decode. Encode can be used on string values to convert them into (UTF8) blobs. Decode can be used on blob values to convert them into UTF8 strings (provided they are valid UTF8). We start off supporting only UTF8 for decode, but more types could of course be added in the future.
Examples:
D select encode('mühleisen');
┌───────────────────┐
│ encode(mühleisen) │
├───────────────────┤
│ m\xC3\xBChleisen  │
└───────────────────┘
D select decode('m\xc3\xbchleisen'::blob);
┌──────────────────────────┐
│ decode(m\xC3\xBChleisen) │
├──────────────────────────┤
│ mühleisen                │
└──────────────────────────┘
D select decode('\xFF\xFF\xFF'::BLOB);
Error: Conversion Error: Failure in decode: could not convert blob to UTF8 string, the blob contained invalid UTF8 characters

Base64
In addition, we add the functions to_base64 and from_base64 for blobs. These are named to match the functions present in MySQL of the same function. to_base64 takes a blob and outputs a varchar, from_base64 takes a (base64 encoded) varchar and outputs a blob.
Parquet blob handling
In addition to these changes, this PR also adds correct handling of blobs to the parquet reader by checking the converted type of byte_arrays. If the ConvertedType is set to UTF8, the result is converted into a string. Otherwise, the result is converted into a BLOB. In case a file has not set the UTF8 flag correctly for strings, it is now also easily possible to convert from BLOB -> VARCHAR through the decode function.
The Parquet writer is also updated to support writing of blobs, and to correctly set the ConvertedType on string columns.

Mühleisens of Amsterdam approve


Cannot find Client ID and Client Secret fields in Preferences > Extensions > Spotify :(

Extension – Title

Author: @jakubsvec001

Description
I cannot find the Spotify Extension
Steps To Reproduce

"Command" + "," > Spotify
Add Client ID and Client Secret

The current behavior
I am expecting to add my Copy Client ID and Client Secret into the extension preferences
The expected behavior
The Client ID and Client Secret fields are not available under "command" + "," > Spotify :(
I am able to find such fields for other extensions under their respective app names in "Extensions"
Raycast version
Version: 1.40.3

This isn't a super helpful comment, but I just want to mention that I am also having this issue!

I can't seem to find the preferences either.

@jakubsvec001 @ncastle @ramirez
Currently, Client ID and Client Secret cannot be added to preferences.The relevant content is hard encoded in the source code.
As a matter of fact, it is useless to add it.


Ordering within a section.

There doesn't seem to be a way to order pages within a section.  For example in the Billing and Pricing part of the example site, I do not see a way to force an ordering of the pages in the left hand bar.

hey @the-maldridge ,
you can easily order pages in left hand bar by using weight in page front matter.


Added key to viewport

I wanted to override default viewport information, but I could not.

Also siteDescription do not work for me, does it have something to do with
description: config.siteDescription not present in this file ?
I encourage siteDescription to be mandatory to have a higher SEO score

oops seems like #70  is yet to be merged

What does key: 'viewport' do? Also, I think you missed a comma :)

@tomtev well actually I wanted to change the viewport meta to content: 'width=device-width, initial-scale=1, shrink-to-fit' but I could not override this because there was no 'key' set

Ah, nice. Maybe we should add a key to charset also?
We should probably also make a 'head' option for gridsome.config.js so we could add for example:
head: {
  { key:'viewport', name: 'viewport', content: 'width=device-width' },
}

@tomtev @hjvedvik eagerly waiting for #70 and this to be merged in the core :)

Yes, its easy when you know how to do it :) Was just thinking its simpler for users to read config docs and see that there is are options for adding stuff to head. But we have a good documentation here https://gridsome.org/docs/head so I agree it's probably not needed.


remove redundant condition

Remove redundant condition in loopFix function.
The condition make a gap when click prev button.
There is swiper option:
swiperOption: {         slidesPerView: 'auto',         centeredSlides: true,         loop: true,         loopedSlides: 3,         navigation: {           nextEl: '.swiper-button-next',           prevEl: '.swiper-button-prev'         }       }

There is a online example.
When you click the prev button three times, you will see the gap.

Thanks, merged!


socket emit

Hello there,
I want to put socket emit on this line, but I could not put it anyway. I still can't get used to the code architecture.
users in the same room

Do you want to send messages and files over websockets instead of a peer connection? Do I understand correctly what you're trying to do?

I want to transfer data from 2nd picture to 1st picture to work in the backend.

Why don't you just use SocketActions and send the data via websockets? You can then broadcast to other peers in room on the server side

ReferenceError: document is not defined
Do you have any idea how to run this in the backend?

You can't access the document on the backend. Just send a plain object with the necessary information.

thank you.


:+1:

Hello!
Just wanted to say thank you.
It just works, it's easy to use, and it GREATLY improves performance. :heart: :heart: :heart: :heart:
Just had the same issue as #12 : NFS volume was not mounted due to host network latency. A reboot of my macbook has fixed it.

Hello @tut-tuuut ,
Glad it was useful and thanks for the kind words.
Cheers


Built-in traffic obfuscation

While this might be considered out of the scope of this project, it might be cool to include an option to obfuscate traffic using udptunnel or udp2raw as mentioned in https://www.wireguard.com/known-limitations/ (TCP Mode).

I don't have too much experience with docker so I can't really comment, though it seems like a pretty good idea. Wouldn't this make it much harder to install on bare metal though? And also to control the obfuscation from the panel?

Just have to ask. Why would you ever want this? Isn't the traffic encrypted, to begin with?

Of course. That's part of the reason to using a VPN. However, some firewalls are not too keen on allowing people to use VPNs so they block any VPN traffic using DPI. Some also block UDP altogether or throttle and limit it with QOS. Traffic obfuscation can make the VPN connection work on more networks (though it will make it a bit slower hence it shouldn't be on by default probably) and possibly even make VPNs usable in places like China.

This would be a reaaally great feature. Where i live, if you use the vpn on a 4G network, it will be throttled hard and basically be unusable. Only obfuscation works. So far I couldn’t make wireguard with obfuscation. So Im extremely interested if you can do it and hopefully it is still on your radar.
Also, do you think it would be possible for a client on iOS or just android phones ?

Aight, I'll look into the obfuscation part. However, it is out of scope to create a client for iOS for this project :)

Aight, I'll look into the obfuscation part. However, it is out of scope to create a client for iOS for this project :)

Awesome man. You'll be the first to implement this in a usable way. and of course I understand regarding the iOS client. I'll keep an eye and again thanks for your effort.

Aight,
So from what i gather, shadowsocks seems to be good for this pupose, and as mentioned, a additional client is required on client side. The plan is to incorporate client and server mode anyways for site-2site configurations so to have a env flag for starting shadowsocks on top of wg should be fine. @HappyShr00m , @TR-SLimey , would shadowsocks be sufficient, or do you have better suggestions?

@perara shadowsocks seems to use SOCKS5 which is good, but easily blocked with DPI. So that still leaves one problem unsolved.
Alternatively, udp2raw could work but requires root access on the clients which is a big downside.
Another alternative is udptunnel (another link) which claims to be able to convert UDP traffic into TCP, bi-directionally and does not seem to require root access, though it doesn't obfuscate traffic.
Then there's the udp_obfs project which specifically obfuscates UDP traffic but doesn't convert it to TCP which then leaves the UDP blocking problem unsolved but should stop DPI.
Lastly, there's the good ol' obfsproxy by TOR which is probably the best solution if it plays nicely with WireGuard.

@TR-SLimey Sorry for taking in this slow.
Just to verify, Since you mention obfsproxy I then assume that sending the traffic through the tor network would accomplish this?
That should at least be a non-issue, but of course, it would be a severe performance hit.

@perara obfsproxy doesn't necessarily require using the TOR network. It's a separate software developed for use mainly with TOR I believe. It doesn't require root and can imitate a number of other protocols iirc, and also works on Android because it's built into the TOR browser app, again iirc. That's why I think it's the best option if indeed it does work here.
As for udp2raw-tunnel, yeah, it sounds great, but there's always that one issue. Giving it as an option would certainly be good but I think that's too much of a flaw to use it as the main obfuscation method, especially if there's any intention of using this on iOS or Android.

@TR-SLimey
I've done some initial work for implementing obfs4 tor bridge. This works OK.
From my understanding, a tor bridge is essentially a "private" entry point to the tor network, where the purpose is to circumvent block lists of known entry points. So this solves the "obfuscation part"
Just to verify, I'm imagining something like this:
Application -> wireguard -> obfs client -> tor network (or something else) -> obfs decode -> wireguard
I think this will work for Linux, but I am not finding any good solution on how to route the WG traffic into a secondary VPN on android. Specifically, I've looked at Orbot, which seems to work fine with the obfs4 bridge.
Also, it would be awesome if it is possible to specifically define the exit node to use in the tor network so that the obfuscation goes only does 1-hop and ends at the server, where the wireguard server is also located.
This would have been quite trivial to do if WG supported pluggable transports. But this is not the case.
Another solution I've seen mentioned is shadowsocks with v2Ray, but I've yet to find any documentation if this method still works against GFW

@perara I think there's still a little bit of confusion. Obfsproxy is completely separate from TOR and doesn't actually require sending anything through the TOR network. The route you provided is more accurate like so:
[Application -> WireGuard -> Obfs4Proxy Client Side -> Obfs4Proxy Server Side -> WireGuard -> ...]
Here's a blog post about using OpenVPN with Obfs4Proxy which seems quite detailed and useful: https://www.comparitech.com/blog/vpn-privacy/hide-openvpn-traffic-obfsproxy-on-windows-and-linux-ec2/ . It seems to also talk about use on Windows so desktop cross-platform compatibility looks okay.
As for use on Android, I've started to look into modifying the WireGuard app (and making my own derivative) to allow the use of Obfs4Proxy. The sources for this app are here: https://git.zx2c4.com/wireguard-android/tree/ . I intend to basically glue those with the sources of Orbot which are here: https://gitweb.torproject.org/orbot.git/tree/ . Unfortunately I have very limited time to work on this so feel free to experiment yourself too.
As for shadowsocks and v2Ray, I have never heard of it so can't help much here.

@TR-SLimey Thanks for the clarification. The provided guide looks good and the proposed arch is more like what I was hoping for (this opens up for any type of obfs in that layer)
I'll do further investigation

I'm highly interested in this project/implementation of wg obfuscsrion. Is this still being worked on or was it abandoned/put on hold? I notice the last comment/commit was 1 year ago.


Vue3 setup how to define channels?

Hi, guys
I use vue 3.2.25 and rails 7.0.
I had successed subscribe channel， but it can't console.log when it's connected. I used vue3 setup.

[ ] vue code

// app.vue

<script setup>
import { getCurrentInstance, computed, watch, defineComponent} from "vue";
let { proxy } = getCurrentInstance();
import { useStore } from "vuex";
const store = useStore();

let connection = (token) => {
  return proxy.$cable.connection.connect(
    `${import.meta.env.VITE_APP_BASE_WS_URL}/?token=${token}`
  );
};

 defineComponent({
  channels: {
    NoticesChannel: {
      connected () {
        console.log('connected')
      },
      received (data) {
        console.log("data", data);
      },
      rejected() {
      console.log("rejected");
    },
    received(data) {
      console.log("data", data);
    },
    disconnected() {
      console.log("disconnected");
    },
    }
  }
 })

let notice_channel = (slug) => {
  proxy.$cable.subscribe({
    channel: "NoticesChannel",
    room: `notices:notices_count_${slug}`,
    public_room: "public_notices",
  }
  );
};

watch(
  () => store.state.user.current_user,
  (newVal, oldVal) => {
    if (newVal) {
      connection(store.state.user.token);
      notice_channel(newVal.slug);
    } else {
      proxy.$cable.unsubscribe({
        channel: "NoticesChannel",
      });
    }
  },
  { immediate: true }
);
</script>

[x] rails log display subscription is success

app/controllers/application_controller.rb:21:in `current_user'
NoticesChannel is streaming from notices:notices_count_sylor2
NoticesChannel is transmitting the subscription confirmation
NoticesChannel is streaming from public_notices

In browser console, I can not get console.log('connected') and also can not console received() log. I think maybe I used setup in vue, so channels can not use  defineComponent?
If it is , how to define channels in vue setup? Thanks so much~

same questions

This is not an ideal solution, but I hope this may works.
It looks like actioncable-vue doesn't register channels in composition API, so you have to do it manually.
// app.vue

<script>
import { defineComponent, getCurrentInstance } from 'vue';

export default defineComponent({
  setup() {
    const instance = getCurrentInstance();
    const cable = instance.proxy.$cable;

    const channelHandlers = {
      connected: () => console.log('channel connected'),
      rejected: () => console.log('channel rejected')
      received: (data) => console.log('channel received', data),
      disconnected: () => console.log('channel disconnected'),
    };

    const subscribeChannel = (name, handlers) => {
      cable.subscribe(name);
      cable._addChannel(name, handlers, {
        _uid: instance.uid,
        _value: instance.proxy,
      });
    };
  }
})
</script>

@Davidzhu001 @Winters0727 @Sylor-huang This is fixed in v3. Please look at the update README documentation.


Fixed #25078 -- Added support for disabled form fields

In XHTML, attribute minimization is forbidden, and the disabled attribute must be defined as <input disabled="disabled"

So maybe it better to use it like this instead of single disabled attribute

I'm not sure we're still guaranteeing XHTML compliancy (see also e61d99d96da).

Thanks for the useful reviews.


SDK container

This is the start of work aiming to create an SDK container and to make it usable as Flatcar's default SDK.
(also for CI builds etc.)
Usage

./build_sdk_container_image -v 2969.0.0 - builds an SDK container image of SDK version 2969.0.0
./run_sdk_container  -v 2969.0.0  - creates an SDK container from image 2969.0.0. The container will stop when the user exits and can subsequently be restarted using the same command.

Goals

Generate SDK container straight from an SDK tarball w/o intermediate steps
Allow off-container work on flatcar-scripts, coreos-overlay, and portage-stable

Design choices:

The SDK version is bound to the flatcar-scripts repo

sdk_container/.repo/manifests/version.txt contains the current SDK version
coreos-overlay and portage-stable repos are git modules of flatcar-scripts
aims to ease versioning as a simple check-out of flatcar-scripts will ensure the version string matches the ebuild repos used to build that version

local __build__directory which is bind-mounted into container, will contain OS images and bootstrapped SDK tarballs

__build__ is in .gitignore

Current features:

SDK import dockerfile will build SDK container from tarball with board support for amd64 and arm64

wrapper script can download SDK tarball or work with local tarball

docker image imitates "cork enter", user is placed in ~/trunk/src/scripts/
SDK container can build packages, OS images, and bootstrap SDKs (i.e. create new tarballs)

Limitations:

The container needs to be started via enter_sdk.shin order for bind-mounts and repo versions to work correctly

Notable divergence from current SDK (chroot):

toolchains are not built when initialising the SDK container. Instead, SDK toolchains are used.
The container does not use the repo tool. All cros-managed repos pull from github instead of local repos.

The following is missing:

push SDK image to registry

Remaining issues:

update_chroot says
Permission denied: '/var/lib/portage/preserved_libs_registry'
even though the file is writable by the 'portage' group
and the 'sdk' user is in the 'portage' group

I've addressed the comments by @pothos and @tormath1 , and added 2 features:

upload containers to ghcr.io (assumes docker is authenticated with github)
add a script to initialise a self-contained SDK container, i.e. without flatcar-scripts repo. The script clones the correct versions of scripts and ebuild repos directly into the container. While this is not the preferred use it arguably adds some freedom.

NOTE because of the recent change of using submodules for version pinning you might run into issues when trying to test this branch.
As a workaround you need to trick the container scripts into thinking this branch's tip is the alpha-2969.0.0 release:
$ git checkout t-lo/sdk-container
$ git tag --force alpha-2969.0.0

Please make sure to not push your tags to origin after that ;-)

I've updated the download section of build_sdk_container_image to download to sdk_container/.cache/sdks so the container can re-use the tarball (e.g. when bootstrapping a new SDK).
The download is skipped if the file exists.
Also, checksum and signature are downloaded now, too, and the tarball is verified.

Rebased to Alpha-2983.0.0.

I found an issue with switching to the sdk user via the USER command in Dockerfile.lean-arch: USER only allows to specify a single group, but sdk needs to be in group sdk (mirroring the host user's group, for bind-mounting) and in group portage.
I've added an ENTRYPOINT trampoline script to take care of switching to the sdk user correctly.

For reference, the ApplyPatch function is in https://github.com/kinvolk/mantle/blob/flatcar-master/sdk/repo.go#L173

I've updated the sdk container logic to address most of @pothos ' comments:

Simplified container locking to eliminate races
reworked version handling so:

for SDK container builds, the git tag is authoritative for SDK version and OS version
for container runs, the git tag is authoritative for the OS version; SDK version is taken from the version file after checkout

added code to pass environment variables to container runs via sdk_container/.env, added  COREOS_OFFICIAL passing to SDK build Dockerfile, and added /etc/sudoers.d/90_env_keep file to container

Wrt. the last item, I feel it's worth checking /iterating on what else from the remaining items cork passes to the chroot  we actually need.

We need a way to forward a list of environment variables, both here and in /etc/sudoers.d/90_env_keep (see https://github.com/kinvolk/mantle/blob/flatcar-master/sdk/create.go#L72)
There is also some mounting for ssh agent and gpg done: https://github.com/kinvolk/mantle/blob/flatcar-master/sdk/enter.go#L190

Finally found some time to get back to this - I've added respective features to run_sdk_container.

CopyGoogleCreds is probably also relevant to upload binary packages
This is still up to do since I need to figure out what this actually does.

Addressed @pothos ' final comment:

CopyGoogleCreds is probably also relevant to upload binary packages

Added a respective feature to run_sdk_container.

I'm in the process of uploading a new SDK container based on 3005.0.0 (ghcr.io/flatcar-linux/flatcar-sdk-all:3005.0.0) to our repo at https://github.com/orgs/flatcar-linux/packages/container/package/flatcar-sdk-all ; should be available in a few hours (uploading 7GiB takes a while) so you can test the PR.

build_sdk_container_image sometimes fails with the following error, when update-chroot tries to rebuild dev-lang/go:1.17.2 inside the Docker container.
Building Go cmd/dist using /usr/lib/go-bootstrap. (go1.5.3 linux/amd64)
 * /var/tmp/portage/sys-apps/sandbox-2.12/work/sandbox-2.12/libsandbox/trace.c:do_peekstr():125: failure (Operation not permitted):
 * ISE:do_peekstr:process_vm_readv(105779, 0x00007ffc7464c5b0{0x00007f2d7be07010, 0x580}, 1, 0x00007ffc7464c5c0{0x000000c820012a80, 0x580}, 1, 0) failed: Operation not permitted

It looks like the same issue as https://github.com/gentoo/gentoo-docker-images/issues/98.
A recommented way to resolve this issue is to run docker buildx build --allow security.insecure.

So, do folks think we can get this merged? I realise there are open TODOs but having it in main it would be helpful to set up a nightly main build. Changes in this branch should not affect the "traditional" build, things would co-exist nicely.

Rebased on latest main.

I've built an SDK container for 2905.2.6 and pushed it to ghcr.io just in case someone wants to test this with stable. I've built the container from a 2905.2.6 SDK tarball but using this PR branch for scripts (which is effectively main with my changes on top). We can consider cherry-picking my changes to flatcar-2905 or branch off a new sdk-2905 from main (after PR merge), shouldn't matter much.

When merging, this PR should be cherry-picked to

flatcar-2905
flatcar-2983
flatcar-3033
Respective adjustments need to be made to the git submodules in these branches to pull in the correct version, and to sdk_container/.repo/manifests/version.txt to reflect the correct Flatcar and SDK versions.

This will enable us to support containerised builds for all current release branches. Respective SDK container image versions have already been made available on https://github.com/orgs/flatcar-linux/packages.

@krnowak Thank you for the feedback! I've addressed the comments and committed your suggestions.

Rebased on the latest main (scripts, coreos-overlay, portage-stable).

The PR gets unwieldy to review (it's just a lot of code to pore over). Found one nit. I see some issues are not yet resolved (podman?), but the PR looks good from my side.

We can merge it as is and add Podman support later (I can do it since I would use Podman anyway on Fedora)

+1 for merging as well. I love that we can run it side by side as we transition and have something to fall back on.

🤩 Will merge & create separate, squashed PRs for the release branches flatcar-(2983,3033,3066).


What do you want to be different from minbrowser?

According to a presentation I watched one of the main goals of the project is to make the browser easier to use with many tabs.
This is already largely accomplished by the base of this repo (https://github.com/minbrowser/min) which I've been using quite a lot recently.
How does your project differ from minbrowser? What do you dislike about minbrowser, how do you want to extend it? I.e. why did you start a new project based on min?

Greets. Basically the goal of the project is to solve information overload dilemma. From what I saw observing regular people, they tend to open many tabs and afraid to close them. So list of tabs for them is like task list. And people tend to procrastinate, thus users with 50+ opened tabs. And regular users usually don't use bookmarks too.
1). First of all I see problem with tab mess when having many tabs opened, and I solve it with adding "collection tabs" for organization sake.
Collection tabs is also solution to upgrade bookmarks mechanism we have since mosaic browser (1993). Also I upgrade history mechanism.
2). Tab bar. I apply Miller's law (7 plus/minus 2) and typographic grid to make things polished and easy on the eye.
Tab bar adapts on whatever number of tabs you want there (actually up to 60 tabs per collection on fullHD display), we have a slider to control amount of tabs you watn to be visible per collection.
tab bar: chrome vs miniature
3). Fast preview on tab hover. So each tab you have opened saves a screenshot webpage. This way you can use it andpreview the tabs you have very quickly and without waiting tab to load if you just started the browser. So imagine hundreds of tabs avail. on the first browser start and even if you are offline you can preview pages, after all you have every URL page you visited screenshoted (and updated from time to time).
4). Overview panel. Where you have overview of all your collections and tabs opened. With fast preview too, so hovering over list of tabs gives you quick preview (screenshots).
5). Predefined collections to choose from. Too hint people with great stuff, best pages on the collection subject. Also I would like to make this collections community editable.
Excuse for my english.
Regards.

All this seems quite appealing and is something that will definitely be useful if done right. I have some problems in building it though; I'm going to open another issue about that.
ps.


Outdated cask: psychopy

Outdated cask: psychopy.
Info:

version: 1.83.04.
appcast url: https://github.com/psychopy/psychopy/releases.atom.

Please do not run find_outdated_appcasts unless you are a maintainer.


Bump Gateway API to 0.8.0

Problem Statement
The Gateway API v0.8.0 is going to be released. At the time of writing, 0.8.0-rc2 has been created.
Once 0.8.0 is released, we need to bump our dependency and verify that all the conformance tests work.
Acceptance Criteria

[ ] the Gateway API is bumped to 0.8.0
[ ] All the core conformance tests pass
[ ] The previously passing extended tests pass

Some related work has been already started in

https://github.com/Kong/kubernetes-ingress-controller/pull/4551
https://github.com/Kong/kubernetes-ingress-controller/pull/4509


Display multiple chart with same height and width

Hello
I am displaying multiple doughnut chart is same page. Issue is they both showing different height and width due to different size of there labels.
So is there any way to display both chart same size?
I have attached screenshot of chart and bellow is the JS code and also here is the codepen
var Chart1 = '';
     function myfunctionChart(positions, chartId, chartdata1) {
          var ChartDataTitle = [];
          var ChartDataColor = [];
          var ChartDataValue = [];
          $('.' + chartdata1 + ' span').each(function() {
            ChartDataTitle.push($(this).data('title'));
            ChartDataColor.push($(this).data('color'));
            ChartDataValue.push($(this).data('value'));
           });
           var config = {
            type: 'doughnut',
              data: {
                 datasets: [{
                        data: ChartDataValue,
                        backgroundColor: ChartDataColor,
                        label: 'Dataset 1'
                 }],
                 labels: ChartDataTitle
               },
               options: {
                 responsive: false,
                 maintainAspectRatio: true,
                        legend: {
                               position: positions,
                        },
                        title: {
                               display: false,
                               text: 'Chart.js Doughnut Chart'
                        },
                        animation: {
                               animateScale: true,
                               animateRotate: true
                        },
                 },
              };
                 var elem1 = document.getElementById("mychart1");
                 if (typeof elem1 !== 'undefined' && elem1 !== null) {
                 var ctx = document.getElementById(chartId).getContext("2d");
                 //    window.myDoughnut = new Chart(ctx, config);
                 Chart1 = new Chart(ctx, config);
                 return Chart1;
                 }
           }
 myfunctionChart('right', 'mychart1', 'chartdata1');
 myfunctionChart('right', 'mychart2', 'chartdata2');

if ($(window).width() < 1024) {
	Chart1.destroy();
	myfunctionChart('bottom', 'mychart1', 'chartdata1');
	myfunctionChart('bottom', 'mychart2', 'chartdata2');
}

@chiraggmodi This is related to #3458. One solution is to not use the on canvas legend and instead use an HTML legend.

I'm having the exact same issue but with bar graphs. The different labels result in charts of different widths. I've been trying to resolve the issue for over 8 hours now.

@ariellevitsky do you have a fiddle that reproduces that issue?

Just made one now!
https://jsfiddle.net/163s63e6/

@etimberg The problem is caused by calculating a left and right padding for the x-axis core.scale.js#L463-L464, which in the case of a category axis might better be treated differently, since the labels are centered under the bars.

@chiraggmodi For the original problem you could hack the afterFit function to set the minSize.width and the width of the legend to a fixed value.
codepen example
N.B. I changed the div-classes to div-IDs, as they were used as unique identifiers.

var charts = [];

/**
 * set fixed width/height option for the legend
 */
function afterFit() {
    if (typeof this.options.width === 'number') {
        this.minSize.width = this.options.width;
        this.width = this.options.width;
    }
    if (typeof this.options.height === 'number') {
        this.minSize.height = this.options.height;
        this.height = this.options.height;
    }
}

/**
 * Equalize legend width/height for all charts
 * uses maximum width/height
 */
function equalizeLegendWidth() {
    var maxLegendSize = 0;
    charts.forEach(function(chart) {
        var legend = chart.legend;
        var size = legend.isHorizontal()
            ? legend.height
            : legend.width;
        if (size > maxLegendSize) {
            maxLegendSize = size;
        }
    });
    if (maxLegendSize > 0) {
        charts.forEach(function(chart) {
           var legend = chart.legend;

           if (legend.isHorizontal()) {
                chart.legend.options.height = maxLegendSize;
            } else {
                chart.legend.options.width = maxLegendSize;
            }
            chart.update();
        });
    }
}

/**
 * build charts
 */
function buildCharts() {
    var containerId = 'chartdata';
    var numcharts = $('[id^=' + containerId + ']').length;
    var legendPosition = ($(window).width() < 1024)
        ? 'bottom'
        : 'right';

    // reset charts
    while(charts.length) {
        charts.pop().destroy();
    }
    // rebuild charts
    for (var i = 1; i <= numcharts; i += 1) {
        var chartId = 'mychart' + i;
        var chartDataId = 'chartdata' + i;
        charts.push(constructChart(legendPosition, chartId, chartDataId));
    }
    equalizeLegendWidth();
}

function constructChart(legendPosition, chartId, chartDataId) {
    var backgroundColor = [];
    var labels = [];
    var data = [];
    var ctx = document.getElementById(chartId).getContext("2d");

    $('#' + chartDataId + ' span').each(function(ignore, el) {
        var elData = el.dataset;
        labels.push(elData.title);
        backgroundColor.push(elData.color);
        data.push(elData.value);
    });

    var config = {
        type: 'doughnut',
        data: {
            datasets: [{
                data: data,
                backgroundColor: backgroundColor,
            }],
            labels: labels
        },
        options: {
            responsive: false,
            maintainAspectRatio: true,
            legend: {
                position: legendPosition,
            },
            title: {
                display: false,
                text: 'Chart.js Doughnut Chart'
            },
            animation: {
                animateScale: true,
                animateRotate: true
            },
        },
    };
    newChart = new Chart(ctx, config);
    newChart.legend.afterFit = afterFit;
    return newChart;
}

$(function() {
    buildCharts();
    $(window).on('resize', buildCharts);
});

Good find @jcopperfield on the padding. That should be removed once we know that the label will be drawn from a different point later on.

@jcopperfield thanks man, it working great!! there is some issue in mobile view but will correct that.

@chiraggmodi What is the issue with mobile view?

Is there a similar solution for the bar chart?

@jcopperfield in responsive due to large legend's, it showing scroll bar. I have attached a screenshot

@ariellevitsky Yes the solution for the bar chart is much simpler. Just add the following code to your scales configuration.
xAxes: [{
    type: 'category',
    afterFit: function(me) {
        me.paddingLeft = 0;
        me.paddingRight = 0;
    }
}],

Your code works to Chart.js Version 4. Thank you @oliver-j-holmes!

1

2

3

Hi! Excuse mi english please (I´m from Agrentina). To resolve two things to “Display multiple chart with same height and width” I add two attributes (one to doughnut, one to legend) on *.component.ts constructor
this.options = { layout: { padding: { left: 0, right: 0, top: 0, bottom: 0 } }, legend: { fullWidth: false, position: 'bottom', display: true, positionDoughnutLabelExtended: 'bottomLeft', (this align the legend at the left) labels: { fontSize:10, usePointStyle: true, } }, cutoutPercentage:80, positionPDExtended:'absolute', (this put all the doughnuts on the same place) };
I can put this attributes to modify the position. On the capture 1 are two attributes, on capture two only de legend attribute (positionDoughnutLabelExtended), on capture 3 without attributes (original set from doughnut and legend). To do this I modify chart.js Someone can resolve this better? Thanks!


"This device can make payments but has no supported cards" but Stripe test cards have been added

Hi,
Trying to test this with a stripe payment gateway but getting "This device can make payments but has no supported cards" message when checking availability yet a few test cards have been added and are visible in the wallet. Sample cards have been selected from this page https://developer.apple.com/support/apple-pay-sandbox/ in accordance with the setup instructions from here: https://stripe.com/docs/apple-pay/web.
Device is iPhone 6 running iOS 10.2

Thanks for stopping by @Graham-C.
On the readme this error is described.

If in your catch you get the message This device can make payments but has no supported cards - you can decide if you want to handle this by showing the 'Setup Apple Pay' buttons instead of the normal 'Pay with Apple Bay' buttons as per the Apple Guidelines.

It means that Apple Pay doesn't find a supported card as described in their docs:

If canMakePayments returns YES but canMakePaymentsUsingNetworks: returns NO, the device supports Apple Pay, but the user has not added a card for any of the requested networks. You can, optionally, display a payment setup button, prompting the user to set up his or her card. As soon as the user taps this button, initiate the process of setting up a new card (for example, by calling the openPaymentSetup method).

The supported payment methods can be defined in code: see https://github.com/samkelleher/cordova-plugin-applepay/blob/master/src/ios/CDVApplePay.m#L14
I would try make the sandbox accounts again, can you see them for example in another Apple Pay apps?

Hi @samkelleher, thanks for your quick reply.
When navigating to https://stripe.com/docs/apple-pay/web on the device the Apple Pay button near the top of the page becomes enabled and tapping this brings up the payment sheet with the 2 test cards I have in my wallet available.

Does the plugin work for yourself when you have only test cards in the wallet?

Fixed this now by registering a merchant ID via apple developer and stripe and then including this ID in Apple pay capabilities for my app via Xcode (https://stripe.com/docs/apple-pay/apps). Don't think this is mentioned in the readme which might be worth updating. Thanks

Hi Graham,
Okay so I followed the stripe guide now I am stuck as I am developing in cordova for this which is HTML and CSS etc so how do I use that in xcode?
James


apkeditor{,-bin}: init at 1.4.1

APKEditor: Powerful android apk resources editor.
This package installs a command APKEditor.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

This is starting to look pretty good.
One thing that sticks out a bit is that the file is quite long. Would it be possible to factor out the vendored deps into separate files perhaps?

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 349470

x86_64-linux

:white_check_mark: 2 packages built:

apkeditor
apkeditor-bin

Could you split the package inits into separate commits? Then we can merge.

Yeah let's skip the binary package for now.

gradle_6 was dropped yesterday: https://github.com/NixOS/nixpkgs/pull/352490. You'll have to make it work with gradle_7 or newer.


Bug: If processor detection block is used it will cause markdown rule to not work.

Environment
ESLint version: 9.9.1
@eslint/markdown version: 6.0.0
Node version: 22.1.0
npm version: 10.7.0
Operating System: Windows
Which language are you using?
commonmark
What did you do?

Configuration
import markdown from '@eslint/markdown';

export default [
  {
    files: ['**/*.js'],
    rules: {
      'no-console': 2,
    },
  },
  {
    files: ['**/*.md'],
    plugins: {
      markdown,
    },
    language: 'markdown/commonmark',
    processor: 'markdown/markdown',
    rules: {
      'markdown/fenced-code-language': 2,
      'markdown/heading-increment': 2,
      'markdown/no-empty-links': 2,
      'markdown/no-invalid-label-refs': 2,
      'markdown/no-missing-label-refs': 2,
    },
  },
  {
    files: ['**/*.md/**/*.js'],
    rules: {
      'no-console': 2,
    },
  },
];

# H1

#### Expected to be wrong, but passed

```js
const message = 'Hello, world!'
console.log(message)

What did you expect to happen?
markdown/heading-increment should throw an error, but it passes if a processor is provided.
What actually happened?

Link to Minimal Reproducible Example
https://stackblitz.com/edit/stackblitz-starters-hu6gry?file=package.json
Participation

[ ] I am willing to submit a pull request for this issue.

Additional comments
No response

This is a limitation of ESLint -- you can't use processor together with rules right now.


ERROR! 'platforms' is not a valid attribute for a RoleMetadata

Hello,
update_linux.yaml
- name: Apply Linux updates
  hosts: servers
  become: no

  roles:
    - linux_update

hosts
[servers]
ans02
ans03
ans04
ans05

ansible-playbook -i ~/ansible/hosts update_linux.yaml --syntax-check
ERROR! 'platforms' is not a valid attribute for a RoleMetadata

The error appears to be in '/root/ansible/playbooks/roles/linux_update/meta/main.yaml': line 2, column 1, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

---
galaxy_info:
^ here

What did I wrong ?
Using Almalinux 9.3 + ansible [core 2.14.14]
did Install by:  ansible-galaxy role install simeononsecurity.linux_update
mkdir ansible
cd ansible
mkdir playbooks
cd playbooks
cp -r ~/.ansible/roles/ .
cd roles
ln -s simeononsecurity.linux_update linux_update
cd ~/ansible/playbooks

ansible-playbook -i hosts update_linux.yaml

I've not run this on 2.14.x yet. Possibly just a meta information syntax change. I'll check

According to https://docs.ansible.com/ansible/latest/galaxy/user_guide.html#using-meta-main-yml it is correct
However according to https://docs.ansible.com/ansible/latest/dev_guide/collections_galaxy_meta.html it isn't
I found that it was depreciated in https://github.com/ansible/ansible/issues/82453

I submitted an mr to update the documentation I based my meta on. https://github.com/ansible/ansible-documentation/pull/1458

@n00bsi please pull latest and try again.


(cmd | node/rpc): Make RPC port configurable and ensure port 0 used for swamp

Make RPC port configurable and ensure that TestSwamp uses port 0 option to prevent trying to use same port for every node.

Codecov Report

Merging #617 (343e0b0) into main (16dba97) will decrease coverage by 0.06%.
The diff coverage is 64.70%.

@@            Coverage Diff             @@
##             main     #617      +/-   ##
==========================================
- Coverage   61.70%   61.64%   -0.07%
==========================================
  Files          93       95       +2
  Lines        4969     5008      +39
==========================================
+ Hits         3066     3087      +21
- Misses       1581     1597      +16
- Partials      322      324       +2

Impacted Files
Coverage Δ

node/config_opts.go
31.03% <0.00%> (-4.97%)
:arrow_down:

cmd/celestia/full.go
41.93% <33.33%> (-0.93%)
:arrow_down:

cmd/celestia/light.go
41.93% <33.33%> (-0.93%)
:arrow_down:

cmd/celestia/bridge.go
56.89% <50.00%> (-0.80%)
:arrow_down:

cmd/flags_rpc.go
81.25% <81.25%> (ø)

node/components.go
94.11% <100.00%> (-0.69%)
:arrow_down:

node/rpc/component.go
100.00% <100.00%> (ø)

node/rpc/config.go
100.00% <100.00%> (ø)

node/rpc/server.go
74.28% <100.00%> (+0.75%)
:arrow_up:

service/header/p2p_server.go
53.26% <0.00%> (-3.27%)
:arrow_down:

... and 2 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 bb958cb...343e0b0. Read the comment docs.


The web admin cannot read host address from environmental variables

Even after run
export RAFIKI_ADDR=ncrs.d2.comp.nus.edu.sg
The web admin is use the default host localhost as the base of API endpoint in production environment.
should take a look into the docker image and figure out why.

Currently, I can only successfully access web admin on NCRS host by hardcoding:
        window.ADMIN_HOST = 'ncrs.d2.comp.nus.edu.sg'         window.ADMIN_PORT = 3000
instead of updating .env.sh.


Doesn't work with yarn and npm scripts

Running yarn build with the following npm script does absolutely nothing, with or without the escaped double quotes.
"scripts": {
    "build": "rm -rf dist && NODE_ENV=production webpack -p --config webpack.config.js && cpx \"/dist/*.js\" \"/static/\"",
}

Node 12.13.0
cpx 1.5.0
yarn 1.19.1
latest MacOS

Are you sure you want /dist and /static ... those paths would point to the root of your file system, right?
Try this: ...  && cpx \"dist/*.js\" \"static/\"",


Overriding bootnode config param using default format in .env file leads to parsing error

⚠ Requests for support in an issue-format will be closed immediately. For support questions, we welcome you to our Discord.
Summary
This relates to docker-compose setup and specifically addresses the config in the .env file. The default bootnode address for testnet is not correct (identified earlier in #2437 and solved in master). If, however, in release 1.1.0 you want to override the currently incorrect bootnode address for testnet by using/adapting the default shown in the comment in the .env file ('default [/dnsaddr/boot.node.ethswarm.org]') it leads to a parsing error when starting the bee node.
Steps to reproduce
Start a fresh new node. Open .env file for a docker-compose setup, uncomment the BEE_BOOTNODE config line and enter the corrected default boot node address in the way suggested in the comments of the file: BEE_NODE=[/dnsadr/testnode.ethswarm.org]. Make sure log file is at least 'debug' and start the bee node
Expected behavior
Expected the bee to discover the bootnodes and start connecting to peers
Actual behavior
The bee continued to log that it had no peers and was trying the bootnodes. Before that, the log file indicated a parsing error: level=debug msg="multiaddress fail [/dnsaddr/testnet.ethswarm.org]: failed to parse multiaddr "[/dnsaddr/testnet.ethswarm.org]": must begin with /". Tried to also enter is as BEE_BOOTNODE="[/dnsaddr/testnet.ethswarm.org]", but that did not work either. Eventually it worked by not making it multiaddr, but just simply BEE_BOOTNODE=/dnsaddr/testnet.ethswarm.org. Maybe special characters are not correctly parsed/escaped?

I suspect you need quotes inside and outside the [].  Not sure the proper syntax, but something like:
BEE_BOOTNODE="['/dnsaddr/testnet.ethswarm.org']"
BEE_BOOTNODE="[""/dnsaddr/testnet.ethswarm.org""]"
BEE_BOOTNODE="["/dnsaddr/testnet.ethswarm.org"]"


Specify pnpm version in release action

The Miniflare testing was broken and complaining about this. Not sure how to test without merging it in first, but CI is already broken on main so 🤷

@petebacondarwin @CarmenPopoviciu #2256 was supposed to provide a durable fix here but didn't work. Based on https://github.com/pnpm/action-setup?tab=readme-ov-file#version the version field should being optional here, but it looks like the packageManager field would have to be set in Wrangler, not sure if that has any side effects.


Upgrade to 18.3.1: Fatal error initializing plugin com.google.gct.core

After I upgrade Google Cloud Tools plugin on my Ultimate 2017.2 to the latest version 18.3.1, I cannot open my project anymore. The message show as below:
Cannot load project:
com.intellij.ide.plugins.PluginManager$StartupAbortedException:
Fatal error initializing plugin com.google.gct.core

What can I do to fix this?
Thanks,

hi @maohieng is there any more info from this error that you can find? Perhaps a stacktrace that was shown in the error dialog? If not, you could try:
Help -> Show Log in Files, and open the IDE log
and paste in some of the log statements here around when you get this error.

@maohieng we found the issue:
https://github.com/GoogleCloudPlatform/google-cloud-intellij/pull/1974
We will merge in this fix and release a new version of the plugin (18.3.2) ASAP (within an hour or two). I'll update here once its been released.
Sorry, and thanks for reporting this!

@maohieng release 18.3.2 is now out. If you update the plugin to this version, this error should go away. Thanks again.

The error is gone now. Thank you.


integral.eo:30-32: Fix integral tests. Since new...

The puzzle 105-4cf141c2 from #105 has to be resolved:
https://github.com/objectionary/eo-math/blob/e4098ee4f3f60d7a0d3fba0cda5d30b52ee4e58d/src/main/eo/org/eolang/math/integral.eo#L30-L32
The puzzle was created by rultor on 19-Feb-23.
Estimate: 30 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@maxonfjvipon please pay attention to this new issue.


Add inline link to CONTRIBUTING to improve accessibility in README.

Fixes https://github.com/JayShukla8/Quotes/issues/185.
The link to CONTRIBUTING.md in  README file currently is just a plain text.
https://github.com/JayShukla8/Quotes/blob/cf7da08769d1160cfbb57ec8074e2c42f3c7b738/README.md?plain=1#L7

[x] Added an inline link for the same will improve accessibility.

Contributing as a registered participant of Hacktoberfest. Do let me know for any changes or improvements.

Thanks but i think the way it is is just fine.


[RFC] persistent filesystem id

fsspec currently uses fs._fs_token that is based on (among a few other things) thread id and args/kwargs passed to the filesystem constructor. This token is used to compare filesystems for caching.
In dvc, we have persistent storage for metadata associated with a particular file on a particular filesystem (e.g. we are saving that path/to/file has an md5 that is 123456 and use fs.checksum() for verification when loading next time).  Currently we only store this for local files, but we need to support that for remote files as well, so in our experimentation, we've introduced fs_id, which is a hash of a config dictionary that was used for creating a specific fs instance, which is very similar to _fs_token, except that it doesn't include tid, so it is persistent across sessions.
In the simplest case (and probably by default), fs_id(open for discussion on the naming) could just default to the hash of the whole config, but it is clear that many filesystems could do better than that. For example:

for local, it might be something like a hash of b"local".
for s3, fs_id should really depend on things like endpoint/region/bucket/etc, and not on user creds.
for ssh, fs_id should depend on base url, but not on user creds.

fs_id for a particular filesystem could change its algorithm in the future (e.g. if developers forgot to include some important parameter), so users should be ready for this and have some mechanism to recover from this. E.g. for dvc it will simply mean that old cached metadata will be effectively dropped, which is just a temporary inconvenience to recompute md5s for requested files.
I think this functionality could be handy for fsspec users in scenarios where they want to be able to identify filesystems across sessions and maybe have persistent storage of metadata. We've used to use hash of url (e.g. s3://bucket/path) in some cases, but url is not able to account for all important parameters, so a standalone fs_id would be much better. If there is interest in adopting it, we'll be happy to contribute PRs for it. Would really appreciate any comments/suggestions.

I agree a session-independent hash of a filesystem seems like a reasonable thing to want. Indeed, it is complicated by the fact that specifics (credentials, defaults) may depend on the environment, but even so. Having a method that can be overidden per filesystem would allow, as you say, for the constraining of which information is to be considered part of the filesystem's identity.
Question: shoudl this be used as the hash for the existing instance cache? Are other state-dependent factors actually useful?

is there a particular reason why _fs_token is thread-specific

The implementations are probably not thread-safe, due to, for example, mutation of the dircache. It would take some determined work to prove they are safe or fix any problems.

@martindurant Makes sense! So looks like it might make sense to have _fs_token as hash of fs.session_id(current _fs_token without tid) + tid, as the session_id part could be useful on its own and tid is just compensating for the lack of thread-safety. But this is just me trying to think ahead, unlike fs_id, we don't have any need for session_id right now and I don't yet see how we could use it in the near future.
Btw, regarding the naming of fs_id, how about just fs.id? Or maybe there is something more fitting? Would love to try to come up with some nice terminology/naming here. 🙂

id is reserved, no?
But yes, I think your understanding is correct.

id is reserved, no?

Unless I'm missing something, I don't see id property/method/etc anywhere in the code. But maybe it is a bit ambiguous. I guess we could start with a PR and maybe there will be better ideas when reviewing. Thanks for the feedback! 🙏


Twitter page clone

Creation of Twitter clone. Login or registration clone.

@omkar787 I can try this

Hello @sunidhisachan. I have assigned it to you

@pushpanjali-10 Yeah, you can create a sub folder in the twitter folder and work there.

Done


Shallow cloning on travis

According to https://docs.travis-ci.com/user/customizing-the-build#git-clone-depth, Travis CI provide a way to shallow clone a repository. This has the obvious benefit of speed, since you only need to download a small number of commits.

Coverage remained the same at 93.858% when pulling aa0e34c49f4b07f3906ea7214787219bfc532e17 on YunLemon:TRAVIS_SHALLOW_CLONE_1 into 1da38c8836e81560a3edfa177920b781f75d7300 on Netflix:master.


add: django admin add and edit pages.

Added the Django Admin Users listing, create and edit pages.

Passed all tests on the first try. Congrats!


markupsafe 2.1.1 cannot import soft_unicode

Hello, great script.
When running the following task:
- block:
    - name: Run database migrations for NetBox
      django_manage:
        command: migrate
        app_path: "{{ netbox_current_path }}/netbox"
        virtualenv: "{{ netbox_virtualenv_path }}"
      retries: 2
      register: _netbox_db_migration
      until: _netbox_db_migration is success

I ran into the traceback below:
fatal: [<IP_ADDRESS>]: FAILED! =>

{"changed": false, "cmd":

["./manage.py", "migrate", "--noinput"],

"msg": "\n:stderr: Traceback (most recent call last):\n
File \"./manage.py\", line 10, in <module>\n    execute_from_command_line(sys.argv)\n

File \"/srv/netbox/current/venv-py3/lib/python3.8/site-packages/django/core/management/__init__.py\", line 401, in execute_from_command_line\n    utility.execute()\n

File \"/srv/netbox/current/venv-py3/lib/python3.8/site-packages/django/core/management/__init__.py\", line 377, in execute\n    django.setup()\n

File \"/srv/netbox/current/venv-py3/lib/python3.8/site-packages/django/__init__.py\", line 24, in setup\n    apps.populate(settings.INSTALLED_APPS)\n

File \"/srv/netbox/current/venv-py3/lib/python3.8/site-packages/django/apps/registry.py\", line 114, in populate\n    app_config.import_models()\n

File \"/srv/netbox/current/venv-py3/lib/python3.8/site-packages/django/apps/config.py\", line 211, in import_models\n    self.models_module = import_module(models_module_name)\n

File \"/usr/lib/python3.8/importlib/__init__.py\", line 127, in import_module\n    return _bootstrap._gcd_import(name[level:], package, level)\n

File \"<frozen importlib._bootstrap>\", line 1014, in _gcd_import\n

File \"<frozen importlib._bootstrap>\", line 991, in _find_and_load\n

File \"<frozen importlib._bootstrap>\", line 975, in _find_and_load_unlocked\n

File \"<frozen importlib._bootstrap>\", line 671, in _load_unlocked\n  File \"<frozen importlib._bootstrap_external>\", line 848, in exec_module\n  File \"<frozen importlib._bootstrap>\", line 219, in _call_with_frames_removed\n  File \"/srv/netbox/releases/netbox-2.9.9/netbox/circuits/models.py\", line 8, in <module>\n    from dcim.models import CableTermination\n  File \"/srv/netbox/releases/netbox-2.9.9/netbox/dcim/models/__init__.py\", line 1, in <module>\n    from .device_component_templates import *\n  File \"/srv/netbox/releases/netbox-2.9.9/netbox/dcim/models/device_component_templates.py\", line 7, in <module>\n    from extras.models import ObjectChange\n  File \"/srv/netbox/releases/netbox-2.9.9/netbox/extras/models/__init__.py\", line 1, in <module>\n    from .change_logging import ChangeLoggedModel, ObjectChange\n

File \"/srv/netbox/releases/netbox-2.9.9/netbox/extras/models/change_logging.py\", line 8, in <module>\n    from utilities.utils import serialize_object\n

File \"/srv/netbox/releases/netbox-2.9.9/netbox/utilities/utils.py\", line 7, in <module>\n    from jinja2 import Environment\n  File \"/srv/netbox/current/venv-py3/lib/python3.8/site-packages/jinja2/__init__.py\", line 12, in <module>\n    from .environment import Environment\n

File \"/srv/netbox/current/venv-py3/lib/python3.8/site-packages/jinja2/environment.py\", line 25, in <module>\n    from .defaults import BLOCK_END_STRING\n

File \"/srv/netbox/current/venv-py3/lib/python3.8/site-packages/jinja2/defaults.py\", line 3, in <module>\n    from .filters import FILTERS as DEFAULT_FILTERS  # noqa: F401\n

File \"/srv/netbox/current/venv-py3/lib/python3.8/site-packages/jinja2/filters.py\", line 13, in <module>\n    from markupsafe import soft_unicode\nImportError: cannot import name 'soft_unicode' from 'markupsafe' (/srv/netbox/current/venv-py3/lib/python3.8/site-packages/markupsafe/__init__.py)\n", "path": "/srv/netbox/current/venv-py3/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin", "syspath": ["/tmp/ansible_django_manage_payload_dmp4hxo_/ansible_django_manage_payload.zip", "/usr/lib/python38.zip", "/usr/lib/python3.8", "/usr/lib/python3.8/lib-dynload", "/usr/local/lib/python3.8/dist-packages", "/usr/lib/python3/dist-packages"]}

This was a result of markupsafe 2.1.1 no longer being able to import soft_unicode. I fixed this error by replacing the package in /srv/netbox/current/venv-py3/lib/python3.8/site-packages/markupsafe with markupsafe 2.0.1.
pip install markupsafe==2.0.1
sudo rm -rf /srv/netbox/current/venv-py3/lib/python3.8/site-packages/markupsafe
sudo cp -r /home/myusername/.local/lib/python3.8/site-packages/markupsafe /srv/netbox/current/venv-py3/lib/python3.8/site-packages/
#Then rerunning the playbook

Please use the netbox_pip_constraints role variable for this. See the defaults file for the suggested version constraint:
https://github.com/lae/ansible-role-netbox/blob/5d0e0f7737dfea101acc604f4a4a0bd42f387502/defaults/main.yml#L96


Title: Adding smooth transitioning effect while changing the theme from dark to light

Which pre-existing JavaScript project will you be working on?
I will work on the website, which is hosting all these javascript projects. That is, the main website
Describe your enhancement/improvement
Current Condition:
The current website gives the option to toggle from light theme to dark theme, which can be of great help for the users in the night time or while using the website in the low light enviornments. But the Transition effect is'nt present.
My Modification:
I would like to Improve the transition effect in the project.
Anything you need to say to the Reviewers
Please assign me with this issue, I have already been came up with the solution for this issue.
Add any other context or relevant screenshots about the enhancement here.
No response

I too found this issue please resolve this as soon as possible


Upgrade asio

Add the latest Asio release
Switch to "ASIO_SEPARATE_COMPILATION" (https://github.com/mvukov/rules_ros2/pull/343)

Needs the skip-url-stability label

Hello @ltekieli, @tisonkun, modules you maintain (asio) have been updated in this PR. Please review the changes.


Better SEO Descriptions on all pages.

Is your feature request related to a problem? Please describe.
When embedding or discovering pages on google search, the descriptions are not very descriptive.
Describe the solution you'd like
Update the descriptions for all pages, potentially making a standard format for SEO descriptions.
Describe alternatives you've considered
N/A
Additional context
See #169 for more information

Hi @XavierChanth , I'd love to have a go at this. Could I be assigned this issue?

Sure @Shubhambawner @utkershrajvenshi , multiple PRs can be contributed since this is a lot of work. Please use this issue to collaborate. I suggest explicitly stating each page you are working on to avoid duplicate work.

I would like to work on thia

I would like to work on this

Sure @Shubhambawner @utkershrajvenshi , multiple PRs can be contributed since this is a lot of work. Please use this issue to collaborate. I suggest explicitly stating each page you are working on to avoid duplicate work.

It would be great if you could asign the pages, as it would be little time taking to do this by discussion

i would like to work on this as well

Hey @XavierChanth i would like to work on this issue

@JeremyTubongbanua I made a PR regarding the issue, please review and suggest changes, if any


Vickel: Watch aparth3id

Vickel requests the watch of the watch_keyword aparth3id. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

aparth3id has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by VLAZ in Charcoal HQ


after searching and selecting a song the bot doesnt changes the message that he added it to the queue but the song got added to queue

It takes time to update


Not  considering Curves in openssl.cnf

Hi All,
I am new and exploring openssl.
I was testing 'openssl s_server' and 'openssl s_client' in the openssl version 1.0.2z
I have added the Curves into openssl.cnf
openssl.cnf:
Curves = P-521:P-384:P-256
The above openssl option example  checked in demo code.
But when i was connection client and server, i suppose to get
Supported Elliptic Curves: P-521:P-384:P-256
Shared Elliptic curves: P-521:P-384:P-256
But i am seeing
Supported Elliptic Curves: P-256:P-521:brainpoolP512r1:brainpoolP384r1:P-384:brainpoolP256r1:secp256k1:B-571:K-571:K-409:B-409:K-283:B-283
Shared Elliptic curves: P-256:P-521:brainpoolP512r1:brainpoolP384r1:P-384:brainpoolP256r1:secp256k1:B-571:K-571:K-409:B-409:K-283:B-283
It means, not honouring the openssl.cnf values, but verified with strace its loading proper openssl.cnf file path varified.
Can we know is that expected behavior? or do we have any patch or fix to read from the the openssl.cnf Curve values.

the openssl version 1.0.2z

Are you sure? There is no such version as 1.0.2z. The last publicly available version of OpenSSL 1.0.2 is 1.0.2u. Later versions are available to premium support customers only. The next version after 1.0.2y was 1.0.2za. Perhaps this is what you mean? If you are a premium support customer then please raise a support query for this via our support system. Otherwise 1.0.2 is end of life and no longer supported.

Please note that 1.0.2 does not apply the default settings from the config file to the SSL_CTX. This was added later.


Unable to use bot on StackExchange.com domain

It seems like the login forms does not look the same on StackOverflow.com and StackExchange.com, making it currently not possible to use this bot on a chat.stackexchange.com

Hmm, this seems related to the Stack Exchange Chat authentication process. We are using HTMLUnit, which acts as a browser unit on its own. While Sam (poke: @ArcticEcho) has told me about a special authentication process being used in the Stack Exchange Chat (non-meta and non-SO), I doubt this is relevant. Maybe it will be an easy fix.

I also hope the login form interfaces doesn't change in later builds, otherwise automatic searching for the button may be preferable.

... I was wondering when you guys would finally run into this problem. Well, to login into chat.SE it's quite simple really; just POST the user's authToken + nonce to http://chat.stackexchange.com/users/login/global .
nonce can be fetched from http://chat.stackexchange.com/users/login/global/request, which returns JSON in the format of: {"token":"xxxxxxxxxxxxxxxxxx","nonce":"xxxxxxxxxxxxxxxxxx"} (the token here is somehow used (I'm still looking into this part) to finally get the user's authToken - all my attempts so far have proven unsuccessful).

Right, I've finally be able to get the chat.SE auth sorted out...

Login to SE.

GET http://stackexchange.com/users/chat-login.

Get the value from the value attribute of the input elements named authToken and nonce.

POST the above data (authToken=blah-blah-blah&nonce=blah-blah-blah) to http://chat.stackexchange.com/users/login/global with the request's referrer and origin both set to http://chat.stackexchange.com.

And that's it, you're in. Btw, the above POST request will return some JSON if the login was successful, example:
{"Message":"Welcome \u003ca href=\"/users/117611/sam\" title=\"Sam\"\u003eSam\u003c/a\u003e, you\u0027ve been logged in."}

Ignore that one... that was meant for #34 ...


onValueChange triggers an extra time after onSlidingCompleted on Android

Environment

react-native info output:

// react-native info

are you using the new architecture?
I'm guessing no.

which version of react & react-native are you using?
"expo": "~49.0.15",
"react": "18.2.0",
"react-native": "0.72.6",
"@react-native-community/slider": "4.4.2"

Description

onValueChange triggers an extra time after onSlidingCompleted on Android.
Inside of onSlidingCompleted I'm setting the slider value to a specific value when the thumb button is pressed if the current value and saved previous value is the same. This works but since onValueChange is triggered an additional time after onSlidingCompleted the slider jumps back to the initial pressed position.
This can be a bit hard to see in this project because it is so small/fast but you should be able to see it flash to the value 5. I think this works correctly on iOS.

Drag the slider to the right.
Press the thumb button a bunch of times.

Expected: after one press of the thumb button the slider should jump to the value 5.
Result: the slider jumps to 5 and back to the original position.
Expected order:
onSlidingStart
onValueChange (if there is a value change at all)
onSlidingComplete
Actual order:
onSlidingStart
onValueChange (if there is a value change at all)
onSlidingComplete
onValueChange
Reproducible Demo
Repro: https://github.com/henrikvilhelmberglund/react-native-slider-issue-android
Code:
import { StatusBar } from "expo-status-bar";
import { StyleSheet, Text, View } from "react-native";
import Slider from "@react-native-community/slider";
import { useState } from "react";

export default function App() {
  const [sliderValue, setSliderValue] = useState(5);
  const [sliderValueStart, setSliderValueStart] = useState();
  const handleSlidingStart = (initialSliderValue) => {
    console.log("handleSlidingStart", handleSlidingStart);
    setSliderValueStart(initialSliderValue);
  };

  const handleSlidingChange = (sliderValue) => {
    console.log("handleSliderChange", handleSlidingChange);
    setSliderValue(sliderValue);
    console.log("after set slider value in change", sliderValue);
  };

  const handleSlidingComplete = (sliderValue) => {
    console.log("handleSlidingComplete", handleSlidingComplete);
    if (sliderValue !== sliderValueStart) {
      setSliderValue(sliderValue);
    } else {
      console.log("sliderValue and sliderValueStart are the same");
      // set slider value to 5
      setSliderValue(5);
      console.log("after set slider value in complete", sliderValue);
    }
  };

  return (
    <View style={styles.container}>
      <Slider
        style={{ width: 400, height: 40 }}
        minimumValue={0}
        maximumValue={23}
        step={1}
        thumbTintColor="#000000"
        minimumTrackTintColor="#222222"
        value={sliderValue}
        onSlidingStart={handleSlidingStart}
        onSlidingComplete={handleSlidingComplete}
        onValueChange={handleSlidingChange}
        tapToSeek={true}
        // maximumTrackTintColor="#000000"
      />
      <StatusBar style="auto" />
    </View>
  );
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
    backgroundColor: "#fff",
    alignItems: "center",
    justifyContent: "center",
  },
});

@henrikvilhelmberglund is this fixed? i'm having the same issue, onValueChange triggered an extra time after onSlidingComplete!

Reproducing this still: snack (though snacks on android & iOS are broken as mentioned in #587)


chore(blockifier): change deserialization of versioned_constants

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2818  👈 (View in Graphite)
#2514
#2359 : 1 other dependent PR (#2501 )
#2327
#2247
#2188
#2067
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


Release 4.15.0

Questions
Answers

Description?
release PR for autoupgrade 4.15

How to test?
this is release PR

Does the upgrade work without mbo module ?

It seems the upgrade went well, is the BO working well ?
The error is normal, it says to the merchant to log again if you click on another link in the back office you will be redirected to the login.

Here we need to check if you are well redirected to the login page, if so we need to test the same scenarios with mbo and the feature disable the module on.

This error with notifications is not really an error. Ideally, we should block notifications from being retrieved during the upgrade. It's normal that this feature doesn't work if the module is moving files, etc., etc.

Hello there,
We indeed spotted a bug on our 4.1.1 version.
We fixed it on the 4.2.0 version, which is not released yet.
As it has a big impact here, we are releasing a 4.1.2 hotfix version today.
Sorry for the inconvenience 😬

Hello,
Can I change the label to Waiting for QA ?

👍

There is the result of our test :
By Hana :
-Check the upgrade from 1778 to 8.0.0 with php 7.3 (BO and FO): OK :heavy_check_mark:
-Check the rollback from 8.0.0 to 1778 with php 7.3  : OK :heavy_check_mark:
-Check the upgrade from 1778 to 8.0.1 (release of 8.0.x) with php 7.3 (BO and FO): OK :heavy_check_mark:
-Check the rollback from 8.0.1 (release of 8.0.x) to 1778 with php 7.3: OK :heavy_check_mark:
Issue still there :
https://github.com/PrestaShop/PrestaShop/issues/29700
and
https://github.com/PrestaShop/PrestaShop/issues/29699
By Aurelien :
PR tested and validated :
https://github.com/PrestaShop/autoupgrade/pull/508 https://github.com/PrestaShop/autoupgrade/pull/510 https://github.com/PrestaShop/autoupgrade/pull/514 https://github.com/PrestaShop/autoupgrade/pull/511 https://github.com/PrestaShop/autoupgrade/pull/495 https://github.com/PrestaShop/autoupgrade/pull/497 https://github.com/PrestaShop/autoupgrade/pull/457 https://github.com/PrestaShop/autoupgrade/pull/505 https://github.com/PrestaShop/autoupgrade/pull/466 https://github.com/PrestaShop/autoupgrade/pull/441
https://github.com/PrestaShop/autoupgrade/pull/489 https://github.com/PrestaShop/autoupgrade/pull/487 https://github.com/PrestaShop/autoupgrade/pull/491
https://github.com/PrestaShop/autoupgrade/pull/458
https://github.com/PrestaShop/autoupgrade/pull/450
https://github.com/PrestaShop/autoupgrade/pull/469
https://github.com/PrestaShop/autoupgrade/pull/440
https://github.com/PrestaShop/autoupgrade/pull/421
https://github.com/PrestaShop/autoupgrade/pull/464
https://github.com/PrestaShop/autoupgrade/pull/422
PR not tested because it's an autoupgrade on develop and we want to prioritize the upgrade on 8.0.0 :
https://github.com/PrestaShop/autoupgrade/pull/526
https://github.com/PrestaShop/autoupgrade/pull/527
https://github.com/PrestaShop/autoupgrade/pull/507
PR where it does not seem to be fully installed :
https://github.com/PrestaShop/autoupgrade/pull/484
-> If we uninstall the module before an update, after it the files is created but not installed in prestashop ( We think in the expected behavior it should be installed ) ( for me, it not block the PR, because it's partially installed )
What we have after the update :

@MatShir is it the expected behavior or not ?
After that day, I tested again to update with the MBO module and it works, as we can see here :

To Conclude :
We have only a minor issue, we didn't blocked this release for this, I will create an issue if it's important for you,
It's QA :heavy_check_mark:

Thank you everyone involved in building and testing this module release


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_484kbvavz8/clone/recipe/meta.yaml:15: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_484kbvavz8/clone/recipe/meta.yaml:21: missing_wheel: For pypi packages, wheel should be present in the host section
WARNING: /tmp/abs_484kbvavz8/clone/recipe/meta.yaml:40: missing_description: The recipe is missing a description
ERROR: /tmp/abs_484kbvavz8/clone/recipe/meta.yaml:40: missing_dev_url: The recipe is missing a dev_url
ERROR: /tmp/abs_484kbvavz8/clone/recipe/meta.yaml:40: missing_documentation: The recipe is missing a doc_url or doc_source_url
ERROR: /tmp/abs_484kbvavz8/clone/recipe/meta.yaml:40: missing_license_family: The recipe is missing the about/license_family key.
Errors were found


Outer md-button-toggle within md-button-toggle-group do not have round corners when selected or disabled

Bug, feature request, or proposal:
Bug
What is the expected behavior?
Proper styling of md-button-toggle within md-button-toggle-group
What is the current behavior?
Outer buttons do not have round corners when selected or disabled

What are the steps to reproduce?
https://material.angular.io/components/button-toggle/examples
What is the use-case or motivation for changing an existing behavior?
Comply with Material Design specs
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Material 2.0.0-beta.8
Google Chrome Version 60.0.3112.113 (Offizieller Build) (64-Bit)
Firefox 55.0.3 (64-Bit)
Is there anything else we should know?
This fixes the styling:
.mat-button-toggle:first-child.mat-button-toggle-checked, .mat-button-toggle:first-child.mat-button-toggle-disabled {
    border-top-left-radius: inherit;
    border-bottom-left-radius: inherit;
}
.mat-button-toggle:last-child.mat-button-toggle-checked, .mat-button-toggle:last-child.mat-button-toggle-disabled {
    border-top-right-radius: inherit;
    border-bottom-right-radius: inherit;
}

Where is that picture from? When looking at the Material Design specs the button-toggle is described differently.

@MA-Maddin Nothing, you're right. Your initial screenshot just looked like a screenshot from the specs to me.


if the whole docker cluster is large enough, will the linux route table become a bottleneck?

I notice that when launched a new container each host in the cluster will add a route rule, so if the cluster has 100 hosts, each host has 100 containers, the route table on each host will be more than 10000? will it become a bottleneck?

We don't believe so. We've done ad-hoc tests of the Linux kernel FIB at much larger scale than 10k and it has performed admirably.
In the event it does become problematic, it's not too difficult to perform aggregation on the routes if the IP address management system allows us to. That would involve essentially pre-allocating IP blocks to each host and then ensuring that containers launched on that host advertise only their aggregated route (e.g. one /24 instead of 256 /32s).
For the moment, however, we aren't concerned. =)


Update markdown filenames to have .md extension

These are markdown files that gets used to generate new GitHub issues when bootstrapping a new track. The extension makes the file more easily viewable on GitHub.
Resolves #25  (FYI: @Insti)

Thanks @kytrinyx :heart:


DELETE /contacts/{id}/mails/{mail-id}

Path: /contacts/{id}/mails/{mail-id}
Method: DELETE
Description: Delete specific mail from a specific Contact
Auth: member
Parameters:

id={String}
mail-id={Number} corresponds to the index of the mails array in this Contact

Response:
{
  phones: [{
    phone: String,
    valid: Boolean
  }],
  socials: {
    facebook: String,
    skype: String,
    github: String,
    twitter: String,
    linkedin: String
  },
  mails: [{
      mail: String,
      personal: Boolean
      valid: Boolean
  }],
}

Notes:
id is an _id field of mongodb.
Status codes:

Code
Rule

404
Contact not found or invalid mail-id

200
Always

Tests:

No match

Invalid mail-id, number is greater than or equal to mails array size
Invalid mail-id, number is less than 0

404 status code

All good

Returns modified contact.

Same thing as the phone. Not a mail ID, and fix the tests.

Contacts have an ID (check response object).