text:
correct token been added but the plugin keep saying its invalid

Visual Studio Code Version : version 1.19.0
Code Settings Sync Version : 2.8.6
Operating System : Mac OS X
Occurs On: [Upload & Download & Help Configuring ]
Proxy Enabled: [ No ]
GIst Id: [ https://gist.github.com/adamchenwei/bd846fbef0ece06ae73ca99a1619cfeb ]
I pasted the exact id of bd846fbef0ece06ae73ca99a1619cfeb  into the field popped up. But it keep saying its invalid with these two errors
Sync : Error Logged In Console (Help menu > Toggle Developer Tools).
Sync : Invalid / Expired GitHub Token. Please generate new token with scopes mentioned in readme. Exception Logged in Console.
*and there is NO errors records in the console. Also it directs me to my gist page.

bd846fbef0ece06ae73ca99a1619cfeb is your GIST ID
it is not token.
Read the readme once again thoroughly

I have the same issue. AND I HAVE BEEN FOLLOWING THE TUTORIAL.

The token menu doesn't even come up, tried reinstalling.

@Modelmat whats your gist id
and may i know where you have placed the token

The thing I generated on github is: 48d1a7ac399af303ae3922e415bd79812f670dde. I can't enter it anywhere. Placing it in the "sync.gist" didn't work/.

you need to place the token here.
https://github.com/shanalikhan/code-settings-sync#customized-sync

I don't have a syncLocalSettings.json in my C:\Users\Me.vscode\ folder anywhere

The same issue for me. And I can't syncLocalSettings.json in my system

@shanalikhan I figured it out. I had to delete the syncLocalSettings.json from %appdata%\Code\User\.
Maybe make a FAQ, it is pretty hidden.

I just simply started using another plugin, works a lot better.

Adam and modelmat,
Feel free to send me pull request in order to improve the document to help other users understanding much better i will release new version for it

Yep. When I have some time, I can make some Wiki pages for you

we can link them in readme page
But i think user wont go wiki pages that much they will read the readme most of the time.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Modelmat notifications@github.com
Sent: Saturday, December 9, 2017 9:01:15 AM
To: shanalikhan/code-settings-sync
Cc: Shan Khan; Mention
Subject: Re: [shanalikhan/code-settings-sync] correct token been added but the plugin keep saying its invalid (#452)
Yep. When I have some time, I can make some Wiki pages for you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/shanalikhan/code-settings-sync/issues/452#issuecomment-350422005, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIXjnMKUt9HYe2bpphhsin8Iej5VWU5lks5s-gYLgaJpZM4QiWgM.

Yeah. The README is a bit overcrowded too. Should we make a new issue?

Lets go with the Wiki pages, we can reference them in readme.

See issue #468

For the people who are getting the same error as OP.
Go to this url:
https://github.com/shanalikhan/code-settings-sync#customized-sync
Pick one of the below paths for your OS:
Windows, this is %APPDATA%\Code\User\syncLocalSettings.json.
Mac, $HOME/Library/Application Support/Code/User/syncLocalSettings.json.
Linux, ~/.config/Code/User/syncLocalSettings.json.
cd into your User folder below.
Remove the JSON file

authors: Lindar90 Modelmat ZuleikaRose adamchenwei shanalikhan

repo: shanalikhan/code-settings-sync


text:
Project Manager projects list is not synchronized

🐛 Describe the bug
I use the Project Manager extension. When synchronizing the projects list is not synchronized.
This file is located in the $HOME/Library/Application Support/Code/User/ directory.
I have a large list on my Macbook which I want to use on my iMac as well.
Basically I need to have a identical setup of my VSCODE environment on both machines.
🌴 **Visual Studio Code Version : 1.27.2
🌴 **Code Settings Sync Version : 3.1.2
🌴 **Operating System : Mac High Sierra
🌴 **Occurs On: Download
🌴 **Proxy Enabled: No

See https://github.com/shanalikhan/code-settings-sync#global-settings
ignoreUploadFiles , ignoreUploadFolders keys.
you need to setup properly.

Well, I expected and honestly think that synchronising an extension must also synchronise the data (files/folders/settings) of that extension.
The synchronised counterpart would not be exactly the same as the original if it doesn't.
Otherwise it makes no sense at all to sync because one cannot rely on it. I have strong doubts whether I can rely on my iMac system!
The user should not need to care about which files/folders/settings belong to an extension and which ones should be synced or shouldn't be synced.
(Often there is even no documentation about what files belong to an extension as well.)

Hi @shanalikhan, good point, that makes sense! 👍

Maybe you can add an explanation in the documentation in the Global Settings ignoreUploadFiles part which files are for what extension?

What does the 'workspaceStorage' do?

Found another issue;
On one computer I have settings set to true: Auto Download and Auto Upload.
I upload the settings.
On the second computer I download the settings.
The settings Auto Download and Auto Upload are NOT synchronized!

Maybe you can add an explanation in the documentation in the Global Settings ignoreUploadFiles part which files are for what extension?

Public WIKI Edit is enabled, If you want feel free to create new page with these details.

The settings Auto Download and Auto Upload are NOT synchronized!
Auto upload and download is facing problem at the moment. Check other issues

OK hope issues are solved soon.
Question: is there an overview about which folders and files are synchronised?

source: gharchive/issue

authors: focussing shanalikhan

license: MIT

license_type: permissive

license_source: github-api


text:
Create website index file

This adds an index file

THis looks great !

source: gharchive/pull-request


text:
Partials in subdirectories are not found

Please see:
https://github.com/shannonmoeller/gulp-hb/issues/43
I already got this problem with gulp-compile-handlebars. I debugged that module and saw that the partials in the subdirectories are being registered. Unfortionally they are not found anyway.
Maybe this is a problem of handlebars itself?

Reopening #43.

authors: MickL shannonmoeller

repo: shannonmoeller/gulp-hb


text:
Shap for LSTM - features as timestep

Hi there,
I would like guidance as to how can I go about using Shap to explain my model when I am inputting the features(29 of them) as timesteps. So my LSTM training set has shape (observations, 29, 1).
Really appreciate your input.

I have the same issue but I couldn't find a solution for that. When I try to feed my data in the shape of (num_data, num_f1, num_f2), the kernelExplainer raises an error.

I have the same issue but I couldn't find a solution for that. When I try to feed my data in the shape of (num_data, num_f1, num_f2), the kernelExplainer raises an error.

Same problem. Can SHAP deal with 3d input data?

Assuming you know the number of timesteps you're interested in using and it is constant, you might consider feeding the data into the model as 2d and then reshaping it within the model before the RNN.

Still struggling... I will try to shape my input to 2d and then reshape it.

repo: shap/shap


text:
BUG: check_additivity fails when running torch on gpu

Issue Description
Unfortunately https://github.com/shap/shap/pull/3265 just got merged the moment I found a bug.
When running DeepExplainer with torch on gpu, the model outputs need to be transferred to cpu prior running _checkaddivity.
This bug was introduced to the master due to merge of https://github.com/shap/shap/pull/3265 and is NOT released yet (0.42.1 does not contain this bug).
test_deep.py is not testing torch with gpu device currently, so this bug slipped through unfortunately. I also made an issue regarding tests on cuda: https://github.com/shap/shap/issues/3279
Minimal Reproducible Example
-

Traceback
91 def shap_values(self, X, ranked_outputs=None, output_rank_order='max', check_additivity=True):
     92     """ Return approximate SHAP values for the model applied to the data given by X.
     93
     94     Parameters
   (...)
    123         were chosen as "top".
    124     """
--> 125     return self.explainer.shap_values(X, ranked_outputs, output_rank_order, check_additivity=check_additivity)

File ~/mambaforge/envs/mlvapto/lib/python3.10/site-packages/shap/explainers/_deep/deep_pytorch.py:218, in PyTorchDeep.shap_values(self, X, ranked_outputs, output_rank_order, check_additivity)
    215         with torch.no_grad():
    216             model_output_values = self.model(*X)
--> 218     _check_additivity(self, model_output_values, output_phis)
    220 if not self.multi_output:
    221     return output_phis[0]

File ~/mambaforge/envs/mlvapto/lib/python3.10/site-packages/shap/explainers/_deep/deep_utils.py:11, in _check_additivity(explainer, model_output_values, output_phis)
      9 for l in range(len(explainer.expected_value)):
     10     if not explainer.multi_input:
---> 11         diffs = model_output_values[:, l] - explainer.expected_value[l] - output_phis[l].sum(axis=tuple(range(1, output_phis[l].ndim)))
     12     else:
     13         diffs = model_output_values[:, l] - explainer.expected_value[l]

File ~/mambaforge/envs/mlvapto/lib/python3.10/site-packages/torch/_tensor.py:970, in Tensor.__array__(self, dtype)
    968     return handle_torch_function(Tensor.__array__, (self,), self, dtype=dtype)
    969 if dtype is None:
--> 970     return self.numpy()
    971 else:
    972     return self.numpy().astype(dtype, copy=False)

TypeError: can't convert cuda:0 device type tensor to numpy. Use Tensor.cpu() to copy the tensor to host memory first.

Expected Behavior
No response
Bug report checklist

[X] I have checked that this issue has not already been reported.
[X] I have confirmed this bug exists on the latest release of shap.
[X] I have confirmed this bug exists on the master branch of shap.
[X] I'd be interested in making a PR to fix this bug

Installed Versions
master - 6e807f8f567ac5745103924311433256b2ec69bf

Bug should be fixed with https://github.com/shap/shap/pull/3281


text:
ThorSwap "View Transaction" should link to viewblock

Overview
Currently, our logic for the "View Transaction" link is to route to the inbound Tx explorer i.e the explorer of the sell asset, or to CowSwap/Osmosis explorer if the swap is from one of these sources
We should also handle ThorSwap Txs to consistently link to viewblock - currently, we only route to it in case of RUNE as a sell asset, since viewblock is defined as a RUNE explorer
References and additional details
https://github.com/shapeshift/web/blob/b5e649395c8a4fa057f9d57c48981d99aa64cfc9/src/components/Trade/TradeConfirm/TradeConfirm.tsx#L147-L156
In the case of Thor swaps, thorchain is the source so we can simply add a case for it:

Acceptance Criteria

All ThorSwaps "View Transaction" links in trade confirm link to viewblock.io

Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response

We should make TradeSourceName an enum whilst we're here.

repo: shapeshift/web


text:
[Spike] Document load times for large wallet

background
several users with large wallets have complained about slow app experiences and initial load times. Some of them are on mobile devices, but the experience isn't unique to mobile only.
we should determine was an acceptable load time to target for a large wallet (how to define this?) and then work towards what we can fit into that time budget.
To start, we can get a document of the current time spent on each group of actions we take on load (wallet balances, tx history, defi positions, etc) and then work with product to reason about what can be deferred or removed.
AC

determine a wallet we can use as a performance benchmark
document loads time with profiler using this wallet
consider optimizations that could be made
once complete schedule time with product / eng to discuss options to improve performance

Document with findings here
https://www.notion.so/shapeshift/Perf-2024-02-27-9c145074b2e9423486b4876f913704ce?pvs=4


text:
fix: accounts balances by chain buckets

Description
This sorts accounts balances by chain buckets in the accounts page.

tested on an account with a mixed balance of BTC (on Segwit, Segwit Native and Legacy) and ATOM on CosmosHub.
also tested on an account with ETH and ERC20 tokens exclusively, in isolation (without other assets)
not tested with both of these two cases at the same time (an account with a mix of BTC (Segwit, Segwit Native and Legacy), Atom on CosmosHub and ETH + ERC20 tokens

Notice

[x] Have you followed the guidelines in our Contributing guide?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[x] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)
closes #1289
Risk

Is using asset.chain as a discriminator the right way to go? Is there any case in the future where this could break sorting, and do we have a better way to achieve this using account specifiers?
This could potentially break the sorting in the case of a mix of assets and account tokens e.g ERC20s

Testing

Go to accounts page
Accounts should be grouped by asset type
Sorting by fiat balance should still be working

Screenshots (if applicable)

tested and working in preview @gomesalexandre


text:
feat: relive react error boundary

Description

Notice

[ ] Have you followed the guidelines in our Contributing guide?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[x] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #2638
Risk

Testing

Engineering

Operations

Screenshots (if applicable)

@developerfred this PR fails lint and has no filled-out template.
I'm going to close this for now. Please reopen when the contributor guidelines have been followed.


text:
feat: disable chatwoot errywhere

Description
Chatwoot isn't quote ready for primetime - issues were found on mobile.
This PR just undoes what https://github.com/shapeshift/web/pull/4739 did.
Pull Request Type

[x] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)
N/A
Risk
Almost literally 0.
Testing
N/A
Engineering
N/A
Operations
N/A
Screenshots (if applicable)
N/A

Current dependencies on/for this PR:

develop

PR #4746   👈

This comment was auto-generated by Graphite.


text:
Convert all css code to scss

Closes: #55
Convert all css code to scss
@sharmaaditya570191

Please share screenshot so that we can check if it does not break anything in the UI.


text:
web-collection

书籍地图
网站https://anvaka.github.io/greview/
完成的地图
1 Hands-on Machine Learning 机器学习
https://anvaka.github.io/greview/hands-on-ml/1/
2 Designing Data-Intensive Applications数据集群运用 https://anvaka.github.io/greview/ddia/1/
3 100 Things Every Designer Needs to Know About People
所有的设计师需要知道关于人的100件事情（IT类）
https://anvaka.github.io/greview/100-things-designer/1/
4 Cracking the Coding Interview Questions
破解编码面试问题
https://anvaka.github.io/greview/cracking-code-interview/1/
主要参照网站https://www.yasiv.com亚马逊网站数据地图

https://www.artic.edu/collection?is_public_domain=1 高清艺术品 3000PX（不需要需注册，暂时没有其他限制）
https://pxhere.com 高清摄影作品无版权 3000~6000PX
（需注册，暂时没有其他限制）

ML书单
│  李航.统计学习方法.pdf
│  机器学习及其应用.pdf
│  All of Statistics - A Concise Course in Statistical Inference - Larry Wasserman - Springer.pdf
│  Machine Learning - Tom Mitchell.pdf
│  PRML.pdf
│  PRML读书会合集打印版.pdf
│  Programming Collective Intelligence.pdf
│  [奥莱理] Machine Learning for Hackers.pdf
│  [机器学习]Tom.Mitchell.pdf
│  《大数据：互联网大规模数据挖掘与分布式处理》迷你书.pdf
│  推荐系统实践.pdf
│  数据挖掘-实用机器学习技术（中文第二版）.pdf
│  数据挖掘_概念与技术.pdf
│  机器学习-Mitchell-中文-清晰版.pdf
│  机器学习导论.pdf
│  模式分类第二版中文版Duda.pdf（全）.pdf
│  深入搜索引擎--海量信息的压缩、索引和查询.pdf
│  矩阵分析.美国 Roger.A.Horn.扫描版.pdf
│  统计学习基础 数据挖掘、推理与预测.pdf
│
├─机器学习实战
│      machinelearninginaction.zip
│      机器学习实战 单页.pdf
│      机器学习实战.pdf
│
└─论文文集
└─LDA
LDA-wangyi.pdf
LDA数学八卦.pdf
text-est.pdf

http://www.yinwang.org/blog-cn/2018/11/23/grammar
王垠老师的《解密计算机科学》还没写完，又开始写第二本书《解密英语语法》。发布第一章以后，第二天他又把这个计划取消了，“我曾经想过把这写成一本完整的语法书，可是后来发现似乎一篇文章足矣。

2、亚马逊的机器学习课程
https://aws.amazon.com/training/learning-paths/machine-learning/
亚马逊公司推出了官方的机器学习课程，学完以后，还能参加付费考试，通过者可以获得 AWS 机器学习认证。

1 https://nomoregoogle.com/
该网站收集各种谷歌服务的替代品，让你可以不使用谷歌。
2 https://inakanoseikatsu.com/大分県国東市・賃貸一戸建・5000円/
日本乡村房屋信息
大分県国東市・賃貸一戸建・6万円／年
3 https://github.com/jabcode/jabcode  彩色二维码 可以加入更多信息 仅支持网页版扫描不支持微信扫描
4 狮子王3D版本预告片
https://m.weibo.cn/s/video/show?object_id=1034%3A4309454896982524&fromWap=1&ep=H3XXTpQWk,1400854834,H3XXTpQWk,1400854834

知乎排名前100的问题和答案 https://zhuanlan.zhihu.com/p/26779637

看见统计 https://seeing-theory.brown.edu/cn.html#firstPage

https://github.com/snowkylin/tensorflow-handbook
简单粗暴TensorFlow 2.0 | A Concise Handbook of TensorFlow 2.0 z中文版
https://mp.weixin.qq.com/s/Ok9ediwb35LzQiT9YVKfWA
CVPR 2019 | APDrawingGAN：人脸秒变艺术肖像画
https://github.com/Dikea/ML-Weekly-Learning
ML 自学者周刊
本刊物在公众号「 进击的龙 」每周连载，欢迎关注


text:
XAudio 2.7 support

I just noticed the alpha no long has XAudio2.7 support. I am unable to make much use of the new 3.0.0.0 alpha versions unless XAudio2.7 support is brought back. XAudio2.8 does not work on Win7 and that OS still has over 50% of the market share. I'm sure many others feel the same.
Thanks,
Xanather

the latest version on git is now including support for both 2.7 and 2.8 from the same binaries (still an alpha). I will release an update alpha02 in the coming days.

authors: xanather xoofx

repo: sharpdx/SharpDX

license: mit

license_source: bigquery


text:
Moved tests into 'RegexTests' folder as required by Swift PM

Fixes issue #46

In the latest build failure, it looks like the test files have been added to the Regex module instead of RegexTests.

So they have, sorry about that!

When are you planing to merge this fix?

Thanks @andrew804!

No problem!

repo: sharplet/Regex


text:
Future: King of Fighters 97 Global Match - Steam

It looks like Steam's "King of Fighters 97 Global Match" is pretty close to KOF97 Mame rom. Comparing the files from these versions, here is what I was able to find ([Steam game directory]\Data\rom vs kof97.zip):

Steam
Mame
CRC
Match

c1.bin
?
E9CB47E7
❌

m1.bin
232-m1.m1
45348747
✅

p1.bin (First 1.048.576 bytes)
232-p1.p1
7DB81AD9
✅

p1.bin (Other 4.194.304.bytes)
232-p2.sp2
158B23F6
✅

s1.bin  s2.bin
232-s1.s1
8514ECF5
✅

sp_4j.bin JP Bios
N/A
DFF6D41F

sp_4s.bin (US Bios?)
N/A
142E97CC

v1.bin split in 3 (1/3)
232-v1.v1
22A2B5B5
✅

v1.bin split in 3 (2/3)
232-v1.v2
2304E744
✅

v1.bin split in 3 (3/3)
232-v1.v3
759EB954
✅

c1.bin seems to contain the sprite rom data, "equivalent" to .c1 to .c6 on kof97.zip, since they all add up to exactly 40MB, but they are not equal and the CRCs don't match 😞
By splitting c1.bin in 6 parts (4x 8MB + 2x 4MB) and zipping all files from the Steam version together - and properly renamed - I managed to boot the rom in RetroArch's Mame. The problem is, most of the sprites are displayed incorrectly:

Screenshots

Again, it seems like the only missing piece is figuring out how to fix the sprite rom data in c1.bin.

Interestingly enough, by running the built (from Steam files) kof97.zip against the tool NeoBuilder Homebrew GUI v1.06 I was able to create a .neo file that worked on my Mister FPGA, which was my ultimate goal 🎉

Hmm... that implies that the ROM data is there in full, and just requires
transformations. When I get a chance, I'll take a look.
On Thu, Nov 23, 2023, 1:45 PM fliperdeboteco @.***>
wrote:

Interestingly enough, by running the built (from Steam files) kof97.zip
against the tool NeoBuilder Homebrew GUI v1.06
https://bidouillouzzz.blogspot.com/2022/02/neobuilder-homebrew-gui.html
I was able to create a .neo file that worked on my Mister FPGA, which was
my ultimate goal 🎉
—
Reply to this email directly, view it on GitHub
https://github.com/shawngmc/game-extraction-toolbox/issues/69#issuecomment-1824817095,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABYAQQZILPR55456COXTMCTYF6KVTAVCNFSM6AAAAAA7X6T5UWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRUHAYTOMBZGU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

There's a bash script to extract a working ROM of KOF'97 from the Amazon version of Global Match: https://github.com/RedundantCich/goNCommand/blob/main/GoKOF97
Maybe this could be of use for the Steam version as well?

There's a bash script to extract a working ROM of KOF'97 from the Amazon version of Global Match: https://github.com/RedundantCich/goNCommand/blob/main/GoKOF97
Maybe this could be of use for the Steam version as well?

Yep it worked! I will create a PR for this repo to include a command for this game.
Thank you!!!

Credit goes to lioneltrs and RedundantCich, of course. Still glad I was able to be of service!

Maybe the same can also be done with the other Neo Geo ports developed by Code Mystics?

Garou: Mark of the Wolves
Samurai Shodown V Special
The Last Blade 2 (there's already a bash script for it)

The King of Fighters '98: Ultimate Match also contains a playable AES version of the Neo Geo original, but the file structure is different compared to other Code Mystics ports. So it might not be a full ROM or something else.

@RealRelativeEase
Perhaps. I don't own Garou: Mark of the Wolves, Samurai Shodown V Special nor The Last Blade 2 on Steam, besides the first two are already already extractable from the Humble Bundle version.
I took a look at King of Fighters '98: Ultimate Match and it doesn't look like it is emulated at all. Did you find any reasons to think otherwise?

It was just a wild guess that the AES version of KOF'98 inside of Ultimate Match is ROM-based, since I couldn't spot any differences compared to a regular ROM of the game run in AES mode. Aside from the option to return to Ultimate Match in the main menu, which could've been added in there via a patch or a custom hack.
I don't think there were too many full-on ports of Neo Geo games past the PS1/Dreamcast, since most of the collections and re-releases seem to contain ROMs wrapped in an emulator.

As far as I can tell, The KOF '98 UM FE is a port, not a ROM-based release.
I can confirm however that, The KOF '97 GM as well as The Last Blade 2 are indeed ROM-based releases and both can be turned into usable ROMs.
By following the commits fliperdeboteco created as well as lioneltrs' original bash script, I was able to recreate a stand-alone python script that converts the ROM files into the KOF97.zip and test that it indeed works correctly.
I cannot comment on the"Samurai Shodown V Special" because I instead purchased the Samurai Shodown NeoGeo Collectionhttps://github.com/shawngmc/game-extraction-toolbox/issues/63 released two years later and from those, ValadAmoleo had managed to extract games 1-4 and then in the following guide, Author alhumbra (Richard Roe) explained how to also extract SS 5S FE. The following tool uses said instructions to extract the SS 5V FE ROM.
Finally, I cannot comment on Garou: Mark of the Wolves because I too bought the Humble Bundle NeoGeo Classic Collection which includes this game among others and in that collection, all ROMs can be easily found in the installer files.

authors: Feilakas RealRelativeEase fliperdeboteco shawngmc

repo: shawngmc/game-extraction-toolbox


text:
We do not require square brackets for httplib.

Resolves #707.
I need to come up with a test for this that doesn't suck, but it should be considered illuminating that no tests break with this change.

@t-8ch You added this in 208ba74c796116bafc95d46dfcf4325449643ab6, any idea why? Is it safe to remove now?

The original issue was https://github.com/shazow/urllib3/pull/199

BTW, I legitimately have no good idea how to test this. I guess I could manually replace the socket to force httplib to do its validation but not actually use the socket, but...that doesn't feel good.

According to https://github.com/shazow/urllib3/pull/199#issuecomment-19837893, it sounds like it happens on a specific Py3 version when port is not given? :/

What's our supported set of Py3 versions? The oldest I have installed right now is Python 3.3.6, which does not reproduce the bug in #199.

Pip supports 3.2 still
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Ugh, ok, I'll try to reproduce on 3.2.

Python 3.2.6 also does not reproduce the bug from #199. Looks like this must have been fixed in a version of 3.2 prior to 3.2.6.
@dstufft What's the scope of your supported 3.2 versions? Put another way, how much effort should I be going to to track down a release that actually exhibits this bug?

What versions of X does pip support is always a sort of hard question. In this case I think that the only reason someone would be using Python 3.2 is either if they are using PyPy3 (which I'm not sure if pip even works on....) or if they are getting Python 3.2 from their OS. Typically our support for anything other than the latest version in a particular X.Y series is best effort based on how big of a deal the bug seems to be, and how hard the fix is.
Looking at the bug, it appears this only affects cases where someone is passing a raw IPv6 into urllib3? So for pip that would probably map to someone is using a raw ipv6 address as an --index-url, --find-links, or are using it in a link from a private index. I suspect that very few people are going to be switching to IPv6 and still be using Ubuntu Precise. There's a good chance the next major version of pip drops support for 3.2 anyways.
tl;dr I wouldn't spend much effort into it unless someone comes out of the wood work to explicitly complain.

Thanks @dstufft. From my perspective that makes me want to merge this, but then again I proposed it so I'm naturally in favour. ;)

I don't have an opinion on the change itself, but I wouldn't let a nebulous concern about a <3.2.6 Python 3.2 prevent you.

If you're interested - https://groups.google.com/forum/#!topic/pypa-dev/Ef0PF2ZGAv0

I've no feelings about this, @Lukasa totally your call, feel free to hit whichever buttons speaks to you.

Yeah, 3.2 is broken in many ways with httplib. I'd say we just stop trying to support 3.2 in this case. :+1:

Screw it, let's do it.

authors: Lukasa dstufft shazow sigmavirus24


text:
strict parameter is obsolete in python version > 3.4

The strict parameter causes twill to break:
In [1]: from twill.commands import *

In [2]: go("http://www.python.org/")
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-2-8620e344db1d> in <module>()
----> 1 go("http://www.python.org/")

/home/moritz/projects/twill/venv/lib/python3.4/site-packages/twill-1.8.0-py3.4.egg/twill/commands.py in go(url)
    108     Visit the URL given.
    109     """
--> 110     browser.go(url)
    111     return browser.get_url()
    112

/home/moritz/projects/twill/venv/lib/python3.4/site-packages/twill-1.8.0-py3.4.egg/twill/browser.py in go(self, url)
     79         for u in try_urls:
     80             try:
---> 81                 self._journey('open', u)
     82                 success = True
     83                 break

/home/moritz/projects/twill/venv/lib/python3.4/site-packages/twill-1.8.0-py3.4.egg/twill/browser.py in _journey(self, func_name, *args, **kwargs)
    510             auth = None
    511
--> 512         r = self._session.get(url, auth = auth)
    513
    514         if _follow_equiv_refresh():

/home/moritz/projects/twill/venv/lib/python3.4/site-packages/requests/sessions.py in get(self, url, **kwargs)
    485
    486         kwargs.setdefault('allow_redirects', True)
--> 487         return self.request('GET', url, **kwargs)
    488
    489     def options(self, url, **kwargs):

/home/moritz/projects/twill/venv/lib/python3.4/site-packages/requests/sessions.py in request(self, method, url, params, data, headers, cookies, files, auth, timeout, allow_redirects, proxies, hooks, stream, verify, cert, json)
    473         }
    474         send_kwargs.update(settings)
--> 475         resp = self.send(prep, **send_kwargs)
    476
    477         return resp

/home/moritz/projects/twill/venv/lib/python3.4/site-packages/requests/sessions.py in send(self, request, **kwargs)
    583
    584         # Send the request
--> 585         r = adapter.send(request, **kwargs)
    586
    587         # Total elapsed time of the request (approximately)

/home/moritz/projects/twill/venv/lib/python3.4/site-packages/requests/adapters.py in send(self, request, stream, timeout, verify, cert, proxies)
    401                     decode_content=False,
    402                     retries=self.max_retries,
--> 403                     timeout=timeout
    404                 )
    405

/home/moritz/projects/twill/venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py in urlopen(self, method, url, body, headers, retries, redirect, assert_same_host, timeout, pool_timeout, release_conn, chunked, **response_kw)
    564             # Request a connection from the queue.
    565             timeout_obj = self._get_timeout(timeout)
--> 566             conn = self._get_conn(timeout=pool_timeout)
    567
    568             conn.timeout = timeout_obj.connect_timeout

/home/moritz/projects/twill/venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py in _get_conn(self, timeout)
    254                 conn = None
    255
--> 256         return conn or self._new_conn()
    257
    258     def _put_conn(self, conn):

/home/moritz/projects/twill/venv/lib/python3.4/site-packages/requests/packages/urllib3/connectionpool.py in _new_conn(self)
    215         conn = self.ConnectionCls(host=self.host, port=self.port,
    216                                   timeout=self.timeout.connect_timeout,
--> 217                                   strict=self.strict, **self.conn_kw)
    218         return conn
    219

What version of requests are you using? I cannot reproduce this.

What's the actual exception? It's not included in your output paste.
Our test suite runs on Python 3.4 and 3.5, it should be catching this if it's indeed the case.

I used it on debian 8 packaged python 3.4. The Exception I missed copying is:
TypeError: __init__() got an unexpected keyword argument 'strict'

That is absolute correct as strict was marked as obsolete and finally removed in 3.4:
https://docs.python.org/3.3/library/http.client.html#http.client.HTTPConnection
https://docs.python.org/3.4/library/http.client.html#http.client.HTTPConnection

@nm-mrt It looks like you must have installed a very old version of requests.
urllib3 strips the strict kwarg out before passing to the constructor on Python 3, as you can see here. This has been true since 181cf0945379c171ff0a7649bedcc4d1dee9a569, first released in urllib3 version 1.8 in March 2014 and equivalently in requests 2.3.0 in May 2014. This bug has not been around for a very long time.

pip freeze tells me it's 2.10.0. But you are right It should not happen like that. It looks like it uses http.client.HttpConnection instead of urllib3.connection.HttpConnection. I'll investigate there.

OK. Twill replaces HTTPSConnection.ConnectionCls explicitly:
        from requests.packages.urllib3 import connectionpool as cpl
        cpl.HTTPConnectionPool.old_http = cpl.HTTPConnectionPool.ConnectionCls
        cpl.HTTPConnectionPool.ConnectionCls = wsgi_intercept.WSGI_HTTPConnection

Well ... works as designed.

So...why are they doing that? =P

authors: Lukasa nm-mrt shazow sigmavirus24


text:
Is this project still maintained?

Hi,
Is this project still maintained? If not, would you be open to a new maintainer?
Thanks!

I'd be open to help maintaining this project. I think the original maintainer intended to open it up to more maintainers.
I'm currently maintaining my own fork that has some of the not-yet-merged features. If you'd like to get some of the more recent features, feel free to use my fork (and/or submit upstream PRs there as well).
The idea is that hopefully the features that get added to that (and are therefore observed to be stable) will be more quickly merged upstream.

@nfischer: I've been kind of talking with @arturadib on Twitter. I'm hoping that he'll give someone (you, if you want, I also volunteer) push rights. He seems to be inactive.

Thanks for getting in contact with him. I'm not a twitter user, so I couldn't reach out to him. I'd personally really like to see this project be more actively maintained.
I'd definitely be interested in co-maintaining the project. I don't think I have enough experience with this particular project to know what features are most desired by the current users. I do however have decent experience in shell scripting (and can see areas where ShellJS lacks compared to Bash), and can review any POSIX-related pull requests (adding new commands, making ShellJS functions match POSIX behavior, etc.). I'd also be able to help go through old issues, verify bugs, and help provide simple solutions to problems users report. Having at least the permission to close issues would be very helpful there.
I think the best way to go forward would be to have @arturadib add one or two people to the ShellJS organization, and perhaps set up a channel for discussing major PRs and design decisions for the project. What do you think, @ariporad?

@nfischer: well, I don't really have any experience, but I belive in this project, and would be happy to help our (if you'd like). I purposed you since you seemed active, but there might be others too.
Besides that, I think your plan sounds great! I think that whoever gets added to the org should just create a gitter, and we can chat there.

I think a gitter is a great idea. Slack would be another alternative. I actually only recently found out about this project, but immediately found features/bug fixes, so I've been working on some PRs. When I saw that there were over 100 open issues, I went through and answered the ones I could, to help filter through stuff so the maintainer(s) would have an easier time later on.
I anticipate having a decent amount of spare time to devote to this, so I'd at the very least be able to respond to issues and bug fixes, if not also write my own feature additions as PRs.

Added both of you as collaborators. Use it wisely :)
Main thing I ask is to (a) try to remain as close as possible to *nix
commands, (b) avoid feature bloat, and (c) only accept new
features/behaviors with tests that pass on CI.
Thanks guys!
@nfischer https://github.com/nfischer- if you create a Twitter account
I'll give a shout out to both of you on Twitter :)
-@r2r http://twitter.com/r2r
On Fri, Jan 8, 2016 at 12:50 AM, Nate Fischer notifications@github.com
wrote:

I think a gitter is a great idea. Slack would be another alternative. I
actually only recently found out about this project, but immediately found
features/bug fixes, so I've been working on some PRs. When I saw that there
were over 100 open issues, I went through and answered the ones I could, to
help filter through stuff so the maintainer(s) would have an easier time
later on.
I anticipate having a decent amount of spare time to devote to this, so
I'd at the very least be able to respond to issues and bug fixes, if not
also write my own feature additions as PRs.
—
Reply to this email directly or view it on GitHub
https://github.com/shelljs/shelljs/issues/272#issuecomment-169903164.

@arturadib Thanks! Yeah, my thinking was to keep behavior close to *nix, and change things if current behavior doesn't match *nix. Also, do you know why the CI doesn't seem to be working right now? I created issue #266 for it. I imagine it has to do with renaming from arturadib/shelljs -> shelljs/shelljs, but I'm not completely sure.
@ariporad Would you be able to set up a gitter for the three of us to discuss the best way to go moving forward? I was thinking we should prioritize merging bug fix pull requests from other users, and then once those are merged, pull in bug fixes from each other, and then move on to feature additions afterward.

CI should be fixed now, thanks for the heads up!
https://travis-ci.org/shelljs/shelljs
-@r2r http://twitter.com/r2r
On Fri, Jan 8, 2016 at 1:53 PM, Nate Fischer notifications@github.com
wrote:

@arturadib https://github.com/arturadib Thanks! Yeah, my thinking was
to keep behavior close to *nix, and change things if current behavior
doesn't match *nix. Also, do you know why the CI doesn't seem to be working
right now? I created issue #266
https://github.com/shelljs/shelljs/issues/266 for it. I imagine it has
to do with renaming from arturadib/shelljs -> shelljs/shelljs, but I'm
not completely sure.
@ariporad https://github.com/ariporad Would you be able to set up a
gitter for the three of us to discuss the best way to go moving forward? I
was thinking we should prioritize merging bug fix pull requests from other
users, and then once those are merged, pull in bug fixes from each other,
and then move on to feature additions afterward.
—
Reply to this email directly or view it on GitHub
https://github.com/shelljs/shelljs/issues/272#issuecomment-170090090.

@arturadib: It looks like I need to be a member of the org (shelljs) to create the gitter. Any chance that would be possible?
Thanks!

@arturadib, @nfischer: But while we're talking here, I have a few ideas:

I'm going to setup some better labels, is that OK?
I think we should make heavy use of those labels and of the assignment feature.
What are your thoughts about semantic-release? I personally really like it.
Any objections to setting up AppVeyor (like travis for Windows)
Thoughts on lgtm.co (I've never used it)?
I think it might be wise to switch to a traditional test runner, or at least add code coverage.
Contributing guidelines?

However, it seems like you'll be much more active a maintainer than I (based off the last 24h), so I'll defer to you to make decisions.

Labels are great. Feel free to go ahead and label any old issues as well.
Again, using labels and assignments are fine.
I don't have any experience with that package (although I'm familiar with the concept of semver). My thoughts are that ShellJS isn't ready yet for v1.0, so most changes are up for grabs (without too much regard to the version number). Would that be useful even before we hit v1.0?
I've never used AppVeyor, but I'm not completely opposed. I think more of a priority is getting old PRs merged into the project, and later on adding in the extra CI. What do you think?
I like the idea of peer review. How difficult would it be to set up lgtm.co? I've never used that, but I've used a similar work flow before and liked it. I think passing the review of at least one maintainer should be good enough for approval (since we have quite a few PRs to work through).
The current unit tests are simple enough to write, and seem to do the job. Do you think there's a benefit to switching frameworks?
I think we should write up some contributing guidelines. We should probably have an in-depth discussion about what we want to be in the guidelines though. I personally like Vundle's policy of squashing commits (See here)

If you'd like, we can set up a slack team for the time being, and can set up a gitter later on.

@arturadib: Sorry to keep bothering you, but it looks like we need admin perms for this repo to set stuff up, such as gitter and lgtm.io. (Actually, could we maybe get the ability to create repos in the org too, if possible?) Also, how should we contact you if we need to do a release (As of right now, we don't have npm perms, which is totally fine, but I'm not sure spamming your twitter is the best way).
@nfischer:
Semantic Release would be helpful because it handles the releasing and the change log generation for us. It also ensures that anything on master is production ready (because it will be released to npm).
I think AppVeyor would be worthwhile because it allows us to reduce bugs on Windows before merging.
LGTM takes 5 minutes, as soon as I have the right perms, I'll set it up.
I think out current setup is fine, but I'm going to try to setup nyc, to get code coverage.
I'd rather not setup slack if possible, I already have a daunting number of slack logins (since there's no way to link accounts, grr...), but if needed, I'll set on up.

@nfischer: Another thought, do you want to have us work on branches in this repo, or in our forks? (I don't think we should work on master).

Also, Labels have been setup. They currently use the semantic-release/angular commit types, but that can be changed (they were created by a script).

The new labels look great!
I think working on our own forks might be cleanest. That seems to work well for Vimium at least.
You make good points about semantic release and appveyor. As long as setting those up doesn't impede us too much, it sounds good to me. I'm ok with moving forward without lgtm.co for a while, as long as we're careful. For the time being, let's not merge until each of us gives an LGTM on the PR.

@nfischer: Ok, sounds great. Once we have perms, I'll set those up.

@nfischer: Idea: Add a label for each command (ex. shjs, ls, cd, touch, grep).

Also, are we going to do semantic-release? If so, we need to be really strict about making sure commits conform to the guidelines. We can also setup GitCop, which can enforce that for us.

I think the command labels could be useful. Although it could be tedious to maintain that. I'm not opposed to the extra labels though (if they're too tedious, we can always just stop using them).
If semantic release is strict about commit messages, then this would be a pain to use for old PRs--it would basically mean we can't merge any of them unless the authors rewrite their commit messages and force-push to their forks. If that's the case, it's probably easier to wait on semantic-release and add it in later once we get some of these issues resolved. I don't think we're ready yet for another release, so it should be OK to wait on that. What do you think?

@nfischer: It is, but the way it works is that all commits between the last release and the current release must match. But as far a PRs go, that's easy: https://git.io/vuFF1

:+1: for the link.
Just might be tedious if we have to edit everyone's pull requests to get them to merge. Either way, it seems like we'll have to wait for perms to set up gitcop, semantic-release, etc. So until we get perms, I think we should stick with the current method of merging good PRs as-is. Since the previous commits don't follow semantic-release, this probably isn't making things much harder for when we switch.

Sounds great. But shall we say use the commit guidelines going forward?

Sounds good to me. I'll try to conform to conform to that in any commits I make.

@nfischer: Thanks, no pressure.
ProTip: You're going to want to change the merge commit text when you merge commit messages. (I personally recommend chore(git): do whatever).

What colors should the labels be for the various commands?

Any color is fine with me. Doesn't matter to me very much.

@nfischer: I'm sorry I haven't had much time to devote to this recently. I've been really busy. I should be more available over the next few days.
P.S. Do you ever sleep? Or do you just work on this project 24/7?

Hey guys– Wow, awesome energy all around! :)
I've created a Gitter room at https://gitter.im/shelljs/shelljs. I've also added both of you as members of the shelljs org, so you should be members there too I think.
As to integrations, our highest priority is CI testing on Windows since we don't have any coverage there, so feel free to set that up!
As for other tools (code style/conventions, semver, etc) why don't you spend some time doing things the old/manual way to get a feel for the problem in this setting and then if that proves to be too inefficient maybe we can think about other integrations?
Lastly, please let me know your npm usernames so I can add you as contributors there too :)
Many thanks for your contributions!!

@nfischer btw you should totally create a Twitter account so I can give you proper credit there! :)

@arturadib: Thanks so much!!!! You rock!!!
I like to be creative with usernames, so I'm @ariporad on npm :smile:.
How involved do you want to be going forward? Do you want to be involved in all decisions, or nothing?

@nfischer: do you want to keep the commit message guidelines?
And does anyone have any objections to me setting up the following:

LGTM.io
Gitcop (if we keep the guidelines)
AppVeyor
???

Thanks again @arturadib!

@ariporad not a big fan of imposing commit message styles to be honest
AppVeyor sounds great if it lets us do CI on Windows, which we need badly

@ariporad added you on npmjs.com

@arturadib: Thanks so much! We'll hold of on the commit messages for now, they could be very useful in the future.

@arturadib: Sorry, but it looks like you need to change a setting for the github org for us to be able to setup AppVeyor/LGTM/etc. Would you mind doing that? Thanks!

@arturadib
My Twitter: ntfschr
My npm: nfischer
Thanks!

I think CI should be our first priority. Let's add OS X support (I'll update my PR tonight).
After that we can focus on Windows support.
Also, I think it would be good to find a time when we can all get on the gitter and lay down concrete goals and set up roles for the project to get things rolling

@nfischer: Agreed. Although it's kind of bad timing, as I'm going on vacation this on Saturday, and I'm not sure if I'll have internet access. We could maybe do one night this week, otherwise in two weeks when I'm back.

@nfisher, @arturadib: Im on vacation, so I don't have great internet, but I'd like to make a time to get together the three of us in gitter and discuss the future. (Any day in the next week or so works for me).
Im really sorry about being pretty inactive recently, this was really poor timing on my part. (And Ive been trying to at least check in from my phone when I can, so that usually means reviewing PRs, not contributing code, which makes me feel just a little like a taskmaster, but i promise it will change soon).

Sounds good to me. I pinged the gitter the other day to see when your availability would be. I can be free sometime tomorrow and have a fairly light schedule during the week. Would tomorrow work for you?

@nfisher: I'm not sure when "tomorrow" is (based off your comment), but I pinged the gitter. Let's move this there.

I'm also going to lock this.

authors: ariporad arturadib nfischer

repo: shelljs/shelljs


text:
Request ipv6 ping and traceroute support

Thank you very much for making this library
Request ipv6 ping and traceroute support

Thank you

repo: shellrow/tracert


text:
v-model returns null for options array of object data

The documentation for this link is not work: https://vue-multiselect.js.org/#sub-single-select-object
I have followed the exact code but the result is not the same as what showed in the documentation. The v-model value always returns null data and all options are checked.
Expected behaviour
v-model returns the selected option object data and only the selected option is checked
Actual behaviour
v-model returns null data and all options are checked
Dependencies:
Vue 3.2
Multiselect 2.6.2

Hello, @aqordeon. U should use the npm install vue-multiselect@next with vue v3.
see the Readme https://github.com/shentao/vue-multiselect/tree/next.

authors: aqordeon smirnov-d

repo: shentao/vue-multiselect


text:
Bring to the front

Bring to the front
How do I leave the component above all other layers?
Observe the illustration below. The vue-multiselect should, in this case, stand on top of all other screen elements. In fact, it should always stay on top of the other screen elements. I think this should be a standard match.
How do you solve this?
Thanks a lot for the help.

Well, this isn’t a problem related to staying above other elements. It happens because your container styles have the overflow property set to auto. You could probably change it to visible and it should work then :) Without showing the scrollbar.

Okay, but I want multiselect to be over the footer of the modal component of Bulma css.

Then do the change that I suggested. Otherwise, it won’t be possible.
It’s a problem of the container – you can’t get outside of it with anything you have inside. Not just multiselect.

<template lang="html">
  <transition name="fade">

          <form>

                Cidade

                <dm-form-select @event="getValueField" field-name="city"></dm-form-select>

        </form>

  </transition>
</template>

I would say try changing this class modal-card-body.

i tried:

  .modal-card {
    overflow: auto !important;
  }

  .modal-card {
    overflow: auto !important;
    z-index: 1 !important;
  }

  .modal-card-body {
    overflow: auto !important;
  }

  .modal-card-foot {
    overflow: auto !important;
  }

But I was not successful.

You have to change it to visible instead of auto.

Yeah! It's work!
  .custom {
    width: 80% !important;
    overflow: visible !important;
  }
  .modal-card-body {
    overflow: visible !important;
  }

Thanks a lot for the help.

Happy to help! :)

Looks great! 👍

Returning...
The problem using "overflow: visible;" In a Bulma modal is that I can no longer scroll when the form is larger than the screen layout.
What I effectively need is that scrolling within the modal works and that "vue-multiselect" is over all elements.
Look at the illustrations below:

IMHO this is not a Bulma Modal scrolling problem. This will happen with all scrollable containers. Wouldn't it be preferable to position the dropdown list absolute, given this would mimics the behaviour of a native select? codepen.

The element is positioned absolutely within the multiselect container. What you probably mean is positioning it absolutely within the whole document, which is a bit harder to accomplish.

Hi there,
I ran into the same issue, and it's definitely a problem of the absolute positioned list, rather than the overflow of a parent container. As the multiselect wants to "imitate" and extend a html select element, which is overlapping any overflow (it even reaches out over the Browser), there needs to be a fix.
A solution I was working on is to set the list to position: fixed; z-index: n; with a calculated position to an element that acts as – as I call it – anchor. I build a little helper:
const calculatePosition = function calculatePosition(anchor, element) {
    const anchorBounding = anchor.getBoundingClientRect();
    const height = window.innerHeight;
    const general = ` width: ${anchorBounding.width}px; left: ${anchorBounding.left}px;`;
    let pos = `top: ${anchorBounding.bottom}px;` + general;
    if (height - anchorBounding.bottom < 200 && height - anchorBounding.top > height - anchorBounding.bottom) {
        pos = `top: inherit; bottom: ${height - anchorBounding.top}px;` + general;
    }

    element.setAttribute('style', pos);
};

with a method:
recalulateList() {
    calculatePosition(this.$el.querySelector('input'), this.$el.querySelector('ul'));
}

Triggering on start and, on scroll, to recalculate the position, keeping the element attached.
Hope this helps finding a solution.
Regards,
Manuel

I found very interesting example with Popper.js, but it's uses old version of vue-multiselect.
https://codesandbox.io/s/0x608nxo10

Why is this closed? I have the same issue in conjunction with a fixed header.

The v3, once it finally releases... allows for the user to provide their own implementation of the list (or the built-in but wrapped in whatever you want). You could then use popper or any other solution for that. As for 2.x, I sadly don’t have the time to work on this and I don’t want to introduce any dependencies.
If you want to help, feel free to dig into the v3 branch, look for regressions compared the current version / see if what’s there solves this problem.

I am facing this in tailwind Dialog. How would i fix this?

Same problem in bootstrap modal, any solution ?

authors: ArthurShlain benoitkopp bibermann daenuprobst shentao swapnilnandgave08 tornography xereda


text:
[Fix]: Corrected the api-secret key-name for Jibit driver in payment config file.

Description
Corrected the api-secret key-name for Jibit driver in payment config file.
Motivation and context
Why is this change required? What problem does it solve?
#232
How has this been tested?
It is tested by Jibit payment gateway.
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

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

Checklist:
Go over all the following points, and put an x in all the boxes that apply.
Please, please, please, don't send your pull request until all of the boxes are ticked. Once your pull request is created, it will trigger a build on our continuous integration server to make sure your tests and code style pass.

[x] I have read the CONTRIBUTING document.
[x] My pull request addresses exactly one patch/feature.
[x] I have created a branch for this patch/feature.
[x] Each individual commit in the pull request is meaningful.
[x] I have added tests to cover my changes.
[x] If my change requires a change to the documentation, I have updated it accordingly.

If you're unsure about any of these, don't hesitate to ask. We're here to help!

thanks for providing the fix.

authors: Ar-Monta khanzadimahdi

repo: shetabit/multipay


text:
fixtureで初期データを投入する

投入したい初期データ

ユーザーデータ
放送データ

確認したいこと

スーパーユーザーの登録
環境変数の適用

参考
モデルに対する初期データを投入する
https://docs.djangoproject.com/ja/3.2/howto/initial-data/
Djangoでfixtureを使ってユーザーモデルと紐づくサンプルデータを投入する方法
https://qiita.com/yongjugithub/items/64f36038421c18eefd43

パスワードをハッシュ化

まずは各種データを作成

ユーザー情報（テスト用）
放送局情報（ガチ）
番組情報（一部） #44
放送情報（一部） #45
何卒情報（一部） #45

ユーザーと放送局はプルリク作るの忘れ。
全部ここに配置してある。
https://github.com/shg25/rnsite/tree/develop/airs/fixtures

現行サイトからの移行も検討しつつ、fixtureをどこまで作るべきかは相談したいところ

現状の方針のまま

引き続きスプレッドシートで編集して適宜追加
現行サイトから移行も別途検討

ここはクローズして引き続き別のIssueで対応

追記：

確認したいこと

スーパーユーザーの登録
環境変数の適用

ユーザー情報はFixtureからは使わない方針にする
settings.pyのSECRET_KEYはユーザー情報に関係なくHerokuの環境変数で対応


text:
Failed to activate the copy-paste-context package

[Enter steps to reproduce below:]

... upgrade to Atom 0.187.0
... launch Atom
... see error message (below)

Atom Version: 0.187.0
System: Mac OS X 10.10.2
Thrown From: copy-paste-context package, v2.1.0
Stack Trace
Failed to activate the copy-paste-context package
At Cannot read property 'apply' of undefined

TypeError: Cannot read property 'apply' of undefined
    at Function.<anonymous> (/Applications/Atom.app/Contents/Resources/app/node_modules/space-pen/lib/space-pen.js:122:30)
    at Function.View.buildHtml (/Applications/Atom.app/Contents/Resources/app/node_modules/space-pen/lib/space-pen.js:96:10)
    at CopyPasteContextView.View (/Applications/Atom.app/Contents/Resources/app/node_modules/space-pen/lib/space-pen.js:121:33)
    at new CopyPasteContextView (/Users/phillip/.atom/packages/copy-paste-context/lib/copy-paste-context-view.coffee:12:57)
    at Object.module.exports.activate (/Users/phillip/.atom/packages/copy-paste-context/lib/copy-paste-context.coffee:8:42)
    at Package.module.exports.Package.activateNow (/Applications/Atom.app/Contents/Resources/app/src/package.js:240:19)
    at /Applications/Atom.app/Contents/Resources/app/src/package.js:221:30
    at Package.module.exports.Package.measure (/Applications/Atom.app/Contents/Resources/app/src/package.js:167:15)
    at Package.module.exports.Package.activate (/Applications/Atom.app/Contents/Resources/app/src/package.js:214:14)
    at PackageManager.module.exports.PackageManager.activatePackage (/Applications/Atom.app/Contents/Resources/app/src/package-manager.js:465:21)

Commands

Config
{
  "core": {
    "disabledPackages": [
      "metrics",
      "welcome",
      "feedback",
      "exception-reporting",
      "autocomplete",
      "recent-projects",
      "open-last-project"
    ],
    "themes": [
      "atom-dark-ui",
      "atom-pitchblack-syntax"
    ]
  }
}

Installed Packages
# User
Sublime-Style-Column-Selection, v1.2.3
atom-cli-diff, v0.11.0
atom-pitchblack-syntax, v0.0.0
auto-update-packages, v0.2.2
copy-paste-context, v2.1.0
highlight-line, v0.10.1
highlight-selected, v0.9.1
minimap, v4.6.0
project-colorize, v0.1.0
remember-session, v0.5.1

# Dev
No dev packages

Having the same issue

Same issue.

authors: PhillipHolmes brpaz czechbox

repo: shieldal/copy-paste-context


text:
Rationales

Each thing in the list deserves a file on the rationale behind it, even if those are largely URLs.

I agree that seeing the rationale would be great, but please don't do this within the checklist, as you probably don't want to read it every time you read the checklist.

A very good idea . May be we can  start to make a seperate files as a reference to every check point.

Without a rational for each recommendation, the checklist is not very useful (to me at least).
Security is never perfect or absolute, so whether and how to secure something depends on how sensitive the data is and who you are protecting it from. And while some practices are widely accepted, there are disagreements about others. Take for example the discussions on Basic Auth and JWT in the issues on this repo. A rational for why the author(s) of this checklist recommend to use JWT Bearer Auth over Basic Auth would be good. (IMO, neither is perfect, but both can be good enough for some APIs)

I agree that this list does not come across as useful to me. A security checklist asking its users to follow its advice without question paradoxically undermines the security-conscious process and mindset the checklist appears to support.

Anyone want to try having a go at this, make some PRs, etc?

authors: Maikuolan alexchamberlain darioseidl erlkonig montchr netcode

repo: shieldfy/API-Security-Checklist


text:
fix: make sure langId is set for twoslash renderer

Closes #23

Structurally good, but these test fails are legit ^
I think we'll also need to change the default recommended CSS ( https://github.com/shikijs/twoslash/blob/main/packages/shiki-twoslash/style.css - to hide these elements )

Oops sorry about that. Forgot to run the tests before pushing. I'll update the tests so that they're good with new ts code blocks containing new language ids.

Tricky, yeah, this makes sense (the Shiki Twoslash site doesn't seem to exhibit this problem, so we can probably drop that property)

authors: frencojobs orta

repo: shikijs/twoslash


text:
关于播放的时候一些问题和建议

问题：
1.如果一篇文章里面有2段短代码，在单个页面中播放的时候会重叠，Hermit插件没有这个现象，
2.当播放完某一首歌自动跳转到下一曲之时，这时候点击下一曲，效果是重新播放，而不是暂停
建议：
1.在手机端播放的时候，歌曲列表显得有点窄，我把高度改成了0.6em，感觉比较合适，播放的按钮还有静音和列表按钮也很小，个人感觉可以独立出来，加一个框，方便移动设备点击，播放进度条不用那么长
2.正在播放的音乐只有一个颜色深浅的变化，我觉得可以考虑点击之后文字右移，然后有个动态图标表示它正在播放，点击播放按钮和播放音乐之前，通常有个加载的时间，可以考虑在播放按钮和暂停按钮之间添加一个正在缓冲的动态图片
先说这么多。。还有一些之后再说

建议增加音量的调整~

现在unexpected character at line 1 column 1 of the JSON data，应该是API失效了吧0.0

authors: 3298021 Ereebay jzwalk

repo: shingchi/Remix


text:
Shiny is saving and loading random properties in IOS Preferences

IF YOU DON'T ANSWER THIS TEMPLATE - THE BOT WILL AUTOMATICALLY CLOSE YOUR ISSUE!  PLEASE DON'T ASK FOR WORKAROUNDS OR TIMELINES - THIS IS FREE SOURCE CODE
Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)

[X] iOS
[ ] Android
[ ] UWP

PLATFORMS THAT YOU CANNOT FILE ISSUES ON RIGHT NOW: Tizen, watchOS, tvOS, macOS
Feature Library
beta components are not fully done - issues MUST include full reproducible sample and stacktrace or they will be closed without explanation!!!

[X ] Core
[ ] Locations
[ ] HTTP Transfers
[ ] Notifications
[ ] Push
[ ] Push - Azure Notification Hub
[ ] Push - Firebase (beta)
[ ] Sensors
[ ] AppCenter Logging Integration
[ ] Location Sync (beta)
[ ] Photo Sync (alpha)
[ ] BluetoothLE (beta)
[ ] Beacons (beta)
[ ] SQLite Integration

Version of Library
Lastest on nuget
Version of OS(s) listed above with issue
All Version
Steps to Reproduce

Expected Behavior
Do nothing

Actual Behavior
Shiny is saving random properties in IOS Preferences and loading them on app restart.

Objects that are registered with shiny (through startup) that implement INotifyPropertyChanged are automatically saved to preferences.

thanks, any way to disable this feature on certain objects

authors: aritchie obader

repo: shinyorg/shiny


text:
Can't add Engine via docker.sock

FATA[0000] error adding engine: Get unix:///docker.sock/_ping: unsupported protocol scheme "unix"

Same for me :)

@mauimauer Would you mind sharing how you accomplished this with socat?

You can see an example here https://github.com/ehazlett/dockerfiles/tree/master/docker-proxy

authors: EmileVauge benhosmer ehazlett mauimauer

repo: shipyard/shipyard


text:
[modified] 未記入保存時、タイプ毎にエラーの表記を修正

課題
設定＞組織変更でフォルダを作り「統合を追加する」のボタンを押し、未記入で保存を押すとエラー表示が「移動先」、「移動元」になる。
やったこと
model内でtype毎にエラーの表示を変えるようにした。

Coverage decreased (-9.7%) to 70.649% when pulling c0ebbfbfea894234eda930ce0cb6078b778ed5cc on ash0411-maker:fix/organization_setting into 2d940bd9e43a73380c6db21c7ee990d8a907fae8 on shirasagi:master.

repo: shirasagi/shirasagi


text:
Update grpc@8.2

Build grpc@8.2

:beers: @BrewTestBot has triggered a merge.

repo: shivammathur/homebrew-extensions


text:
Update php@8.4

Build php@8.4

:beers: @BrewTestBot has triggered a merge.

repo: shivammathur/homebrew-php


text:
icu4c 74.2 php@7.2-zts

Update php@7.2-zts

:beers: @BrewTestBot has triggered a merge.


text:
実行環境の見直し

EC2 AmazonLinux2への依存が強いため、オンプレや他のVPSなどで実行するのが面倒
今後の方向性として、MinecraftのバージョンごとにDocker Imageを配布したい

いくつかの点で Docker イメージの配布は難しいように思います。
TL;DR
Dockerfile / docker-compose.yml を配布しましょう。
課題
EULA
EULA に以下の記載があります。

お客様は、当社ゲームを購入している場合、当社ゲームを自由に扱い、修正データ、ツール、またはプラグイン (以下総称して「Mod」といいます) を追加して変更することができます。「Mod」とは、お客様またはその他のユーザーが作成したオリジナルのものであって、著作権で保護される当社のコードまたはコンテンツの相当部分を含まないものを意味します。
お客様が Mod を Minecraft ソフトウェアと組み合わせた場合、その組み合わせを当社ゲームの「Mod バージョン」といいます。
……
お客様は、当社ゲームまたは当社のソフトウェアの Mod バージョンを頒布することはできません。

我々が提供する Docker イメージは、その内部に Spigot サーバーの jar を持つことになるとは思いますが、
その jar には Mojang 所有のコンテンツも含まれていますので、 EULA に抵触してしまいます。
Dockerfile だったら、我々の著作物だけを配布することになるので、
特に何にも抵触しないと思います。
Spigot のリリースモデル
実は、Minecraft と Spigot のバージョンは1対多で対応しています。
例えば、 MC 1.18.x に対応する Spigot は 3290-3368 の 78 バージョンあります。

https://hub.spigotmc.org/versions/

我々は↑にあるJSONの更新を何らかの方法で常に追い続ける必要があります。
これ自体は日次バッチとかで回すことになろうと思いますが、それよりも楽な方法があります。
ユーザーが使うタイミングで毎回 docker build してもらうことです。

次に、ベースイメージの選定ですが、これはDocker 公式の openjdk でよいと思います。
理由
Spigot が要求する Java のバージョン
Spigot はビルドするサーバーのバージョンに応じて、
特定のバージョンの Java を要求してきます。

https://hub.spigotmc.org/stash/projects/SPIGOT/repos/buildtools/browse/src/main/java/org/spigotmc/builder/Builder.java?until=e350a4449c276dba76221b40c2befa8b8ffb3c7a&untilPath=src%2Fmain%2Fjava%2Forg%2Fspigotmc%2Fbuilder%2FBuilder.java#319-364
https://hub.spigotmc.org/versions/

ここで要求されるのは主に以下のバージョンです。

Java 8
Java 16 (～1.17.x)
Java 17 (～1.18.x)

この中には LTS ではないものも含みます。
これの何が問題なのかというと、distroless (Java 11 か 17 しかない)のようなセキュアで軽量な Docker イメージではサポートされていない Java が要求されるケースがあることです。
https://github.com/GoogleContainerTools/distroless
若干 attack surface / サイズが大きくなりますが、Docker 公式の OpenJDK イメージは数多くの Java をサポートしつつ、 alpine や slim といった比較的軽量なものが用意されているので、これを使うのが最適解かと思います。
https://github.com/docker-library/docs/blob/master/openjdk/README.md#supported-tags-and-respective-dockerfile-links
aarch64 への対応
EC2 に加え、ECS Fargate でも Graviton2 が使えるようになりました。
https://aws.amazon.com/jp/blogs/news/announcing-aws-graviton2-support-for-aws-fargate-get-up-to-40-better-price-performance-for-your-serverless-containers/
これは従来の x86_64 のプロセッサに比べて性能・価格が優れています。
そうした点で、AWSユーザーを想定すると aarch64 に対応したいところです。
また、 Raspberry Pi 上で動作させるユーザーも意識したいです。
これらの点で、 aarch64 向けのイメージが欲しいと考えています。
openjdk には aarch64( arm64v8 と書かれている) 向けのイメージが存在しています。

e289d2ff023393fe81be2c4ea70f2b6a806d7d6e
Minecraft v1.18用のを作ってみました。
OpenJDKのAlpineがaarch64に対応していなかったため、Debian slimを利用しました。
作ってみたのにも関わらず今更の相談ですが、ユーザにDockerfileを選ばせるのではなく、Minecraftのバージョンから自動的にOpenJDKを選ぶようにするのはどうでしょうか？
以下の理由から、Alpineをベースイメージとして、Minecraftのバージョンによって適切なOpenJDKをインストールする形にしてもよいのではないかと考えています

複数のDockerfileなどを管理し続けるのは、Dockerfileを自動生成するような環境を作らない限り大変だと考えていること
Dockerfileを分けても次ような処理を書かなくてはならないこと

https://github.com/shokkunrf/gretel/blob/feat/in-container/1.18/Dockerfile#L7

AlpineのパッケージマネージャーにはJava 16の提供があったが、Debianにはなかったこと

https://pkgs.alpinelinux.org/packages?name=*openjdk*&branch=v3.15&arch=aarch64
https://packages.debian.org/search?keywords=openjdk

確かに。
複数の Dockerfile を扱うようなスクリプトを管理するよりも、
OpenJDK をバージョンに合わせてインストールするスクリプトを定義する方が楽なので、
そちらにしましょうか。
debian のパッケージに Java 11 と 17 しかなかったのは盲点でした。
debian のパッケージ管理はかなり厳格で安定志向なので、LTS以外はなくなってしまっているのでしょう。
見たところ alpine は古い Java のパッケージもかなり長くメンテナンスされているようですし、よさそうですね。
alpine:latest を使いましょうか。

確認感謝:pray:
alpine:latestについて、半年に1回バージョンアップするのは面倒ですが、動作保証的な感覚でバージョン固定したほうがよいと考えています
Alpineがバージョンアップ時に破壊的変更をしないならlatestでもよいのですが、どうなんですかね？

そうなんですよね。肝心のopenjdkがcommunityレポジトリにあるので……
Alpine が破壊的変更をしないかというとそういうことはないです。
gretel に影響がありそうなのは、パッケージのバージョンが上がって発生するケースでしょうか。
gretel が依存するパッケージは少ないですが、保守的に倒しますか。
とはいえ、開発者体験を損なうのもつらいところです。
保守的に倒す場合は、向こう半年目処でこの辺りを整備しておきたいなと思っています。

開発用Slackでリリースノートの更新を追えるようにする
簡単なE2Eテストを書く
半年に一度などで depandabot のようにPRを飛ばす仕組みを作る

authors: shokkunrf usagiga

repo: shokkunrf/gretel


text:
Set default layout for categories doesn't change existing assingments

Actual behaviour: When setting a new layout for categories as default, it doesn’t overwrite the already existing assignments where the previous default layout has been assigned to.
Expected behaviour: Setting a new default layout for categories should lead to this layout being assigned to all categories where the previous default layout has been assigned to.
For product layouts this works as intended tho.
Steps to reproduce:
Create custom layout for categories
Mark Layout as new default
Result: New default is not being assigned to existing categories that were already assigned to a default layout.

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-38792
[created from NEXT-38792, comment 501815]

repo: shopware/shopware


text:
TypeError: Cannot read properties of undefined (reading 'reduce')]

Issue Description:
Problem
Encountering a TypeError during the execution of the shopware integration. The error message specifically states: "Cannot read properties of undefined (reading 'reduce')".
running dockware on docker-compose
using admin-api
any idea what's causing this?

i have no idea what's this
[useListing][search] Did not found any category with collection name: Summer-BBQ/Hidden-Carousel-Category

> dev
> next dev

   ▲ Next.js 14.0.0
   - Local:        http://localhost:3000
   - Environments: .env

 ✓ Ready in 2.8s
 ○ Compiling /page ...
 ✓ Compiled /page in 8.7s (1032 modules)
==> [TypeError: Cannot read properties of undefined (reading 'reduce')]
[useListing][search] Did not found any category with collection name: Summer-BBQ/Hidden-Carousel-Category
==> [TypeError: Cannot read properties of undefined (reading 'reduce')]
[useListing][search] Did not found any category with collection name: Summer-BBQ/Hidden-Category
==> [TypeError: Cannot read properties of undefined (reading 'reduce')]
==> [TypeError: Cannot read properties of undefined (reading 'reduce')]
==> [TypeError: Cannot read properties of undefined (reading 'reduce')]
 ✓ Compiled /favicon.ico/route in 495ms (37 modules)

when i try to build i get
    ~/pr/shop/frontend    main !4 ?1  npm run build                                                1 ✘

> build
> next build

   ▲ Next.js 14.0.0
   - Environments: .env

Failed to compile.

./components/product/variant-selector.tsx
Error:
  × Expected a semicolon
    ╭─[/home/zack/projects/astrogas/frontend/components/product/variant-selector.tsx:29:1]
 29 │   }
 30 │
 31 │   const combinations: Combination[] = variants.map((variant) => ({
 32 │     console.log(variant);
    ·            ─
 33 │     id: variant.id,
 34 │     availableForSale: variant.availableForSale,
 35 │     // Adds key / value pairs for each variant (ie. "color": "Black" and "size": 'M").
    ╰────

  × Expected ',', got '.'
    ╭─[/home/zack/projects/astrogas/frontend/components/product/variant-selector.tsx:29:1]
 29 │   }
 30 │
 31 │   const combinations: Combination[] = variants.map((variant) => ({
 32 │     console.log(variant);
    ·            ─
 33 │     id: variant.id,
 34 │     availableForSale: variant.availableForSale,
 35 │     // Adds key / value pairs for each variant (ie. "color": "Black" and "size": 'M").
    ╰────

Caused by:
    Syntax Error

Import trace for requested module:
./components/product/variant-selector.tsx
./components/product/product-description.tsx
./app/product/[...handle]/page.tsx
./node_modules/next/dist/build/webpack/loaders/next-app-loader.js?name=app%2Fproduct%2F%5B...handle%5D%2Fpage&page=%2Fproduct%2F%5B...handle%5D%2Fpage&pagePath=private-next-app-dir%2Fproduct%2F%5B...handle%5D%2Fpage.tsx&appDir=%2Fhome%2Fzack%2Fprojects%2Fastrogas%2Ffrontend%2Fapp&appPaths=%2Fproduct%2F%5B...handle%5D%2Fpage&pageExtensions=tsx&pageExtensions=ts&pageExtensions=jsx&pageExtensions=js&basePath=&assetPrefix=&nextConfigOutput=&preferredRegion=&middlewareConfig=e30%3D!./app/product/[...handle]/page.tsx?__next_edge_ssr_entry__

> Build failed because of webpack errors
   Creating an optimized production build  .%                                                                           ~/pr/ast/frontend    main !4 ?1                                                            1 ✘  23s 

when i try to build i get
    ~/pr/shop/frontend    main !4 ?1  npm run build                                                1 ✘

> build
> next build

   ▲ Next.js 14.0.0
   - Environments: .env

Failed to compile.

./components/product/variant-selector.tsx
Error:
  × Expected a semicolon
    ╭─[/home/x/projects/shop/frontend/components/product/variant-selector.tsx:29:1]
 29 │   }
 30 │
 31 │   const combinations: Combination[] = variants.map((variant) => ({
 32 │     console.log(variant);
    ·            ─
 33 │     id: variant.id,
 34 │     availableForSale: variant.availableForSale,
 35 │     // Adds key / value pairs for each variant (ie. "color": "Black" and "size": 'M").
    ╰────

  × Expected ',', got '.'
    ╭─[/home/x/projects/shop/frontend/components/product/variant-selector.tsx:29:1]
 29 │   }
 30 │
 31 │   const combinations: Combination[] = variants.map((variant) => ({
 32 │     console.log(variant);
    ·            ─
 33 │     id: variant.id,
 34 │     availableForSale: variant.availableForSale,
 35 │     // Adds key / value pairs for each variant (ie. "color": "Black" and "size": 'M").
    ╰────

Caused by:
    Syntax Error

Import trace for requested module:
./components/product/variant-selector.tsx
./components/product/product-description.tsx
./app/product/[...handle]/page.tsx
./node_modules/next/dist/build/webpack/loaders/next-app-loader.js?name=app%2Fproduct%2F%5B...handle%5D%2Fpage&page=%2Fproduct%2F%5B...handle%5D%2Fpage&pagePath=private-next-app-dir%2Fproduct%2F%5B...handle%5D%2Fpage.tsx&appDir=%2Fhome%2Fx%2Fprojects%2Fshop%2Ffrontend%2Fapp&appPaths=%2Fproduct%2F%5B...handle%5D%2Fpage&pageExtensions=tsx&pageExtensions=ts&pageExtensions=jsx&pageExtensions=js&basePath=&assetPrefix=&nextConfigOutput=&preferredRegion=&middlewareConfig=e30%3D!./app/product/[...handle]/page.tsx?__next_edge_ssr_entry__

> Build failed because of webpack errors
   Creating an optimized production build  .%                                                                           ~/pr/ast/frontend    main !4 ?1                                                            1 ✘  23s 

i gave up on deploying the frontend on my machine
and used varcel and i get this error in the log
 ApiClientError: Failed request
 - [Precondition Failed] No matching sales channel found.
    at (node_modules/.pnpm/@shopware+api-client@0.0.0-canary-20231024141318/node_modules/@shopware/api-client/dist/index.mjs:57:8)
    at (node_modules/.pnpm/@shopware+api-client@0.0.0-canary-20231024141318/node_modules/@shopware/api-client/dist/index.mjs:114:6)
    at (node_modules/.pnpm/ofetch@1.3.3/node_modules/ofetch/dist/shared/ofetch.00501375.mjs:254:30)
    at (node_modules/.pnpm/ofetch@1.3.3/node_modules/ofetch/dist/shared/ofetch.00501375.mjs:261:14)
    at (lib/shopware/api.ts:114:11)
    at (lib/shopware/index.ts:199:15)
    at (components/grid/three-items.tsx:46:38) {
  ok: false,
  status: 412,
  statusText: 'Precondition Failed',
  url: 'https://shop.idk.ma/store-api/product-listing/4ab73c06d90d4a5cb312209a64480d87',
  details: {
  errors: [
  {
  status: '412',
  code: 'FRAMEWORK__ROUTING_SALES_CHANNEL_NOT_FOUND',
  title: 'Precondition Failed',
  detail: 'No matching sales channel found.',
  meta: { parameters: [] },
  trace: [
  {
  file: '/var/www/html/vendor/shopware/core/Framework/Api/EventListener/Authentication/SalesChannelAuthenticationListener.php',
  line: 117,
  function: 'salesChannelNotFound',
  class: 'Shopware\\Core\\Framework\\Api\\ApiException',
  type: '::'
},
  {
  file: '/var/www/html/vendor/shopware/core/Framework/Api/EventListener/Authentication/SalesChannelAuthenticationListener.php',
  line: 84,
  function: 'getSalesChannelData',
  class: 'Shopware\\Core\\Framework\\Api\\EventListener\\Authentication\\SalesChannelAuthenticationListener',
  type: '->'
},
  {
  file: '/var/www/html/vendor/symfony/event-dispatcher/Debug/WrappedListener.php',
  line: 116,
  function: 'validateRequest',
  class: 'Shopware\\Core\\Framework\\Api\\EventListener\\Authentication\\SalesChannelAuthenticationListener',
  type: '->'
},
  {
  file: '/var/www/html/vendor/symfony/event-dispatcher/EventDispatcher.php',
  line: 206,
  function: '__invoke',
  class: 'Symfony\\Component\\EventDispatcher\\Debug\\WrappedListener',
  type: '->'
},
  {
  file: '/var/www/html/vendor/symfony/event-dispatcher/EventDispatcher.php',
  line: 56,
  function: 'callListeners',
  class: 'Symfony\\Component\\EventDispatcher\\EventDispatcher',
  type: '->'
},
  {
  file: '/var/www/html/vendor/shopware/core/Content/Flow/Dispatching/FlowDispatcher.php',
  line: 47,
  function: 'dispatch',
  class: 'Symfony\\Component\\EventDispatcher\\EventDispatcher',
  type: '->'
},
  {
  file: '/var/www/html/vendor/shopware/core/Framework/Webhook/WebhookDispatcher.php',
  line: 70,
  function: 'dispatch',
  class: 'Shopware\\Core\\Content\\Flow\\Dispatching\\FlowDispatcher',
  type: '->'
},
  {
  file: '/var/www/html/vendor/shopware/core/Framework/Event/NestedEventDispatcher.php',
  line: 31,
  function: 'dispatch',
  class: 'Shopware\\Core\\Framework\\Webhook\\WebhookDispatcher',
  type: '->'
},
  {
  file: '/var/www/html/vendor/symfony/event-dispatcher/Debug/TraceableEventDispatcher.php',
  line: 127,
  function: 'dispatch',
  class: 'Shopware\\Core\\Framework\\Event\\NestedEventDispatcher',
  type: '->'
},
  {
  file: '/var/www/html/vendor/symfony/http-kernel/HttpKernel.php',
  line: 166,
  function: 'dispatch',
  class: 'Symfony\\Component\\EventDispatcher\\Debug\\TraceableEventDispatcher',
  type: '->'
},
  {
  file: '/var/www/html/vendor/symfony/http-kernel/HttpKernel.php',
  line: 76,
  function: 'handleRaw',
  class: 'Symfony\\Component\\HttpKernel\\HttpKernel',
  type: '->'
},
  {
  file: '/var/www/html/vendor/shopware/core/Framework/Adapter/Kernel/HttpKernel.php',
  line: 56,
  function: 'handle',
  class: 'Symfony\\Component\\HttpKernel\\HttpKernel',
  type: '->'
},
  {
  file: '/var/www/html/vendor/symfony/http-kernel/HttpCache/SubRequestHandler.php',
  line: 86,
  function: 'handle',
  class: 'Shopware\\Core\\Framework\\Adapter\\Kernel\\HttpKernel',
  type: '->'
},
  {
  file: '/var/www/html/vendor/symfony/http-kernel/HttpCache/HttpCache.php',
  line: 460,
  function: 'handle',
  class: 'Symfony\\Component\\HttpKernel\\HttpCache\\SubRequestHandler',
  type: '::'
},
  {
  file: '/var/www/html/vendor/symfony/http-kernel/HttpCache/HttpCache.php',
  line: 262,
  function: 'forward',
  class: 'Symfony\\Component\\HttpKernel\\HttpCache\\HttpCache',
  type: '->'
},
  {
  file: '/var/www/html/vendor/symfony/http-kernel/HttpCache/HttpCache.php',
  line: 276,
  function: 'pass',
  class: '

Details: {
  errors: [
  {
  status: '412',
  code: 'FRAMEWORK__ROUTING_SALES_CHANNEL_NOT_FOUND',
  title: 'Precondition Failed',
  detail: 'No matching sales channel found.',
  meta: { parameters: [] },
  trace: [
  {
  file: '/var/www/html/vendor/shopware/core/Framework/Api/EventListener/Authentication/SalesChannelAuthenticationListener.php',
  line: 117,
  function: 'salesChannelNotFound',
  class: 'Shopware\\Core\\Framework\\Api\\ApiException',
  type: '::'
},
  {
  file: '/var/www/html/vendor/shopware/core/Framework/Api/EventListener/Authentication/SalesChannelAuthenticationListener.php',
  line: 84,
  function: 'getSalesChannelData',
  class: 'Shopware\\Core\\Framework\\Api\\EventListener\\Authentication\\SalesChannelAuthenticationListener',
  type: '->'
},
  {
  file: '/var/www/html/vendor/symfony/event-dispatcher/Debug/WrappedListener.php',
  line: 116,
  function: 'validateRequest',
  class: 'Shopware\\Core\\Framework\\Api\\EventListener\\Authentication\\SalesChannelAuthenticationListener',
  type: '->'
},
  {
  file: '/var/www/html/vendor/symfony/event-dispatcher/EventDispatcher.php',
  line: 206,
  function: '__invoke',
  class: 'Symfony\\Component\\EventDispatcher\\Debug\\WrappedListener',
  type: '->'
},
  {
  file: '/var/www/html/vendor/symfony/event-dispatcher/EventDispatcher.php',
  line: 56,
  function: 'callListeners',
  class: 'Symfony\\Component\\EventDispatcher\\EventDispatcher',
  type: '->'
},
  {
  file: '/var/www/html/vendor/shopware/core/Content/Flow/Dispatching/FlowDispatcher.php',
  line: 47,
  function: 'dispatch',
  class: 'Symfony\\Component\\EventDispatcher\\EventDispatcher',
  type: '->'
},
  {
  file: '/var/www/html/vendor/shopware/core/Framework/Webhook/WebhookDispatcher.php',
  line: 70,
  function: 'dispatch',
  class: 'Shopware\\Core\\Content\\Flow\\Dispatching\\FlowDispatcher',
  type: '->'
},
  {
  file: '/var/www/html/vendor/shopware/core/Framework/Event/NestedEventDispatcher.php',
  line: 31,
  function: 'dispatch',
  class: 'Shopware\\Core\\Framework\\Webhook\\WebhookDispatcher',
  type: '->'
},
  {
  file: '/var/www/html/vendor/symfony/event-dispatcher/Debug/TraceableEventDispatcher.php',
  line: 127,
  function: 'dispatch',
  class: 'Shopware\\Core\\Framework\\Event\\NestedEventDispatcher',
  type: '->'
},
  {
  file: '/var/www/html/vendor/symfony/http-kernel/HttpKernel.php',
  line: 166,
  function: 'dispatch',
  class: 'Symfony\\Component\\EventDispatcher\\Debug\\TraceableEventDispatcher',
  type: '->'
},
  {
  file: '/var/www/html/vendor/symfony/http-kernel/HttpKernel.php',
  line: 76,
  function: 'handleRaw',
  class: 'Symfony\\Component\\HttpKernel\\HttpKernel',
  type: '->'
},
  {
  file: '/var/www/html/vendor/shopware/core/Framework/Adapter/Kernel/HttpKernel.php',
  line: 56,
  function: 'handle',
  class: 'Symfony\\Component\\HttpKernel\\HttpKernel',
  type: '->'
},
  {
  file: '/var/www/html/vendor/symfony/http-kernel/HttpCache/SubRequestHandler.php',
  line: 86,
  function: 'handle',
  class: 'Shopware\\Core\\Framework\\Adapter\\Kernel\\HttpKernel',
  type: '->'
},
  {
  file: '/var/www/html/vendor/symfony/http-kernel/HttpCache/HttpCache.php',
  line: 460,
  function: 'handle',
  class: 'Symfony\\Component\\HttpKernel\\HttpCache\\SubRequestHandler',
  type: '::'
},
  {
  file: '/var/www/html/vendor/symfony/http-kernel/HttpCache/HttpCache.php',
  line: 262,
  function: 'forward',
  class: 'Symfony\\Component\\HttpKernel\\HttpCache\\HttpCache',
  type: '->'
},
  {
  file: '/var/www/html/vendor/symfony/http-kernel/HttpCache/HttpCache.php',
  line: 276,
  function: 'pass',
  class: 'Symfony\\Component\\HttpKernel\\HttpCache\\HttpCache',
  type: '->'
},
  {
  file: '/var/www/html/vendor/symfony/http-kernel/HttpCache/HttpCache.php',
  line: 204,
  function: 'invalidate',
  class: 'Symfony\\Component\\HttpKernel\\HttpCache\\HttpCache',
  type: '->'
},
  {
  file: '/var/www/html/vendor/shopware/core/Framework/Adapter/Kernel/HttpCacheKernel.php',
  line: 65,
  function: 'handle',
  class: 'Symfony\\Component\\HttpKernel\\HttpCache\\HttpCache',
  type: '->'
},
  {
  file: '/va

i gave up on deploying on my local machine and used vercel now i get this error
is this frontend actually ready for people to use or just some facade i really need to know if i'm able to use shopware with next commerce
  errors: [
  {
  status: '404',
  code: 'PRODUCT__CATEGORY_NOT_FOUND',
  title: 'Not Found',
  detail: 'Could not find category with id "ff7bf3c59f1342a685844fbf8fdf9dc8"',
  meta: {
  parameters: {
  entity: 'category',
  field: 'id',
  value: 'ff7bf3c59f1342a685844fbf8fdf9dc8'
}

Solution Edit:
components/carousel.tsx
components/grid/three-items.tsx

Change the hard-coded ID with your own (you can obtain it from the URL in the admin panel).
Had more issues with Shopware that I decided to switch completely. I advise anyone reading this to look for alternatives, since support for Shopware is almost nonexistent.

repo: shopwareLabs/nextjs-shopware-starter


text:
Refactor events.

Change file system & module names.
Before merge we need republish plugins (shower-navigator and shower-timer).

Unit tests are failing (with updated timer and navigation plugins)
  31 passing (112ms)
  5 failing

  1) shower.Plugins Should add and init new plugin:
     Uncaught Error: Module "shower-test-plugin": can't resolve dependence "event.Emitter" (file:///Users/pepelsbey/Projects/Shower/core/shower.min.js:7)

  2) shower.Plugins Should remove the plugin:
     Uncaught Error: Module "shower-test-plugin": can't resolve dependence "event.Emitter" (file:///Users/pepelsbey/Projects/Shower/core/shower.min.js:7)

  3) shower.Plugins Should get the plugin:
     Uncaught Error: Module "shower-test-plugin": can't resolve dependence "event.Emitter" (file:///Users/pepelsbey/Projects/Shower/core/shower.min.js:7)

  4) shower.Plugins Should instance the plugin with options from the Shower:
     Uncaught Error: Module "shower-test-plugin": can't resolve dependence "event.Emitter" (file:///Users/pepelsbey/Projects/Shower/core/shower.min.js:7)

  5) shower.Plugins Should instance the plugin with options from method:
     Uncaught Error: Module "shower-test-plugin": can't resolve dependence "event.Emitter" (file:///Users/pepelsbey/Projects/Shower/core/shower.min.js:7)

I also see auto-generated tests/unit/tests.js file, should I also commit it?

No, I will remove this file.

authors: pepelsbey zloylos

repo: shower/core


text:
XP Bar - Forge Timer

Is your feature request related to a problem? Please describe.
I think this item is similar to the money instead of hunger bar feature. It can be annoying to have to press tab to check on forge progress, especially on long forge times.
Describe the solution you'd like
I think it could be interesting to have a red XP bar during forging that drains as it completes, and a green full one when the forge is complete, and an empty green one when it is ready.
Describe alternatives you've considered
You can literally just press tab.
Additional context
This is definitely a QOL improvement, and does not have any particular merit. Additionally, I am aware that the way that I described could be quite difficult, and I apologize for such.

Dupe


text:
Fix prefix argument so that it applies consistently even on windows

After updating from the old unmaintained jteeuwen version I had issues using the prefix argument:

Having any prefix argument changes the behaviour significantly (in my case it was using full paths instead of relative paths with any prefix present). It also won't do the fix that is marked for issue #110 in this case.
The prefix is a regexp now. This is different from the old version and not documented.
On windows, the prefix regexp is applied to the path with backslashes in. This makes it harder to write code that's consistent across platforms.

Also slightly unrelated but very close in the code: on Windows, a leading slash won't be removed.
Here's a pull request that fixes these problems.
P.S. Thanks for maintaining this fork. I was having problems with the old version due to it not listing "DO NOT EDIT" in the correct place, so golint was confused.

This PR break the symlink test on convert_test.go.

Sorry, this test was failing for me before as well (on Windows). I may be able to have a look on Linux and see if I can correct it.

Closing due to no response. Sorry.

authors: m-r-hunt shuLhan

repo: shuLhan/go-bindata


text:
feat(nextra/docs/blog): allow import .md/.mdx as well

fixes https://github.com/shuding/nextra/issues/83
depend on https://github.com/shuding/nextra/pull/546 since I already touched plugin.ts
review only last commit

nice this will be wonderful!

repo: shuding/nextra


text:
Extension issue

Issue Type: Bug
Extension Name: vscode-blade-formatter
Extension Version: 0.16.1
OS Version: Windows_NT x64 10.0.19044
VS Code version: 1.68.1

:warning: We have written the needed data into your clipboard. Please paste! :warning:

Requesting to close this issue. 0 information given. @shufo

Closed by #372

repo: shufo/vscode-blade-formatter


text:
单机单进程和组级别任务有什么区别？

我的测试如下：结果一样，不明白这两种选择的区别在哪。
任务级别：
	1. 组级别任务：
		定义：在所有选择的节点上选一个节点运行
		测试：
			1. 停止某一node节点，任务在其他机器照常运行，任务没有在这台机器运行
				启动该node节点，任务能被调度到这台机器执行
			2. 停止某一节点的etcd，任务在其他机器照常运行，任务没有在这台机器运行
				启动该节点etcd，任务能被调度到这台机器执行
			3. 停止web节点
				任务正常执行

	2. 单机单进程：
		测试：
			1. 停止某一node节点，任务在其他机器照常运行，任务没有在这台机器运行
				启动该node节点，任务能被调度到这台机器执行
			2. 停止某一节点的etcd，任务在其他机器照常运行，任务没有在这台机器运行
				启动该节点etcd，任务能被调度到这台机器执行
			3. 停止web节点
				任务正常执行

请看这里的说明：任务类型 。
在

去除了同时有且只有一个任务进程在跑的限制，只要任务调度时间到，就会在某个节点上面开始另一个任务进程。
也就是说组级别任务可能会同时运行两次这个任务？

当出现以下情况的时候：

任务设定为每隔10秒会执行一次；
任务脚本的运行时间为15秒（就是脚本的运行时间大于任务的间隔时间）；

当发生以上情况时，这两种任务类型才会有区别

repo: shunfei/cronsun


text:
fix how it deal with QPS

time.Duration is an alias of int64. 1.0/createConfig.qps can go below 1 and time.Duration(1.0/createConfig.qps) * time.Second will become 0.

Lgtm, thanks for fixing this!

authors: mengqiy shyamjvs

repo: shyamjvs/kube-stress


text:
Extract linter to library dependency

I've been looking for a Kotlin linter for two reasons, one of which is accomplished with this library. The other reason I want a Kotlin linter is to create a companion linter for FP libraries. This linter would do things like:

Enforce use of val.
Require functions to be pure.
Use Maybe instead of nullables when the type exists.

For this reason, it would be useful to decouple the rules from the base linter/parser. Implementing libraries could then supply their own rules. Thoughts?

@pardom Sure. I can make KtLint.lint/format public. That will allow to specify custom rules & handle any violations any way you like.
Let me know if I'm missing something. Thanks!
P.S.
ktlint is available through Maven Central
<dependency>
    <groupId>com.github.shyiko</groupId>
    <artifactId>ktlint</artifactId>
    <version>0.1.2</version>
</dependency>

P.P.S.
I'm also considering adding "presets" (additional (more restrictive) set of rules) to ktlint. FP could potentially be one them (in fact I'm pretty sure I would use it myself). I'm always open to collaboration and so if you're interested - I can definitely see FP rules included into ktlint (ktlint --fp).

I was thinking of something a bit more abstract. For example:
├── ktlint-core
│   └── src
│       └── rule
├── ktlint-standard
│   └── rule
└── ktlint-functional
    └── rule

ktlint-core is the base project, and other projects like ktlint-standard and ktlint-functional add ktlint-core as a dependency, and provide only the rules. Or the can compose one another, e.g. ktlint-functional could depend on ktlint-standard.

Where does CLI (Main.kt) go? some kind of 'ktlint-cli' module which wires all together?

Perhaps. I'm not exactly sure what the mechanism would be to wire it all up, off hand. Making the parser open for extension is the goal, though.

@pardom jsyk: this thing is in progress. It might take several days before it's ready (due to the insane the schedule this week) but it's coming.

Cool, no hurry. I'd be happy to contribute, too.

@pardom 0.2.0 is finally out :tada:. readme.md & chanelog.md updated. ktlint was broken into multiple modules but more importantly it now supports for 3rd party rulesets. Please check the readme.md ("Usage" and "Creating a ruleset" sections) and let me know if something isn't clear or simply doesn't make sense. Thank you!

authors: pardom shyiko

repo: shyiko/ktlint


text:
Draggable gaps ?

Hi,
I am wondering if the layout can / could support draggable gaps where one gap (a separation between 2 content panes) is draggable to adjust the size / ratio of those 2 panes.
Something like this:

At the same time, maybe this whole thing and a state manager to save the updated layout should be build on top of this project rather than integrated with it...

+1 on the feature request.
I actually got an idea how this could be accomplished:

create a Splitter/DraggableSeparator widget or sth like that
use GestureDetector to catch drag events
bind a callback to a handler that changes the values in columnSizes/rowSizes

This has the drawback of eliminating the need for a rowGap/columnGap, as the splitter replaces the gap. (OTOH you could also use the gap to make only part of the gap draggable using the splitter)
I just discovered this lib and think its awesome. This feature would be a great improvement nonetheless. Maybe I can play around with the idea. Are there better approaches?

authors: ricardoboss tlvenn


text:
Share your stylesheet

Not an issue per say, but could you share information about the setup you used for the screenshots ? I love it !
It seems to be Atom Material, but with some tweeks, would you mind sharing your stylesheet ?

Sure! Packages List of my Atom available on Packages

authors: qpre siamak

repo: siamak/atom-panda-syntax


text:
[Bug]: takeUntil import

What happened?
Hi, im geting this error, when serving an angular project with ngx-editor v13
./node_modules/ngx-editor/fesm2015/ngx-editor.mjs:1160:34-43 - Error: export 'takeUntil' (imported as 'takeUntil') was not found in 'rxjs'
Version
v13.0
Angular Version
v13.3.11
What browsers are you seeing the problem on?
No response
Link to reproduce
No response
Relevant log output
No response
Willing to submit a PR?
No response

Try updating to rxjs 7.5 or later

Thanks for reply,
From rxjs manual import should be
import { takeUntil } from 'rxjs/operators' , they changed that while ago, I'm not sure they bring that back in 7.5

Not sure. For now, I hope you can upgrade. will fix this sooner.

Fixed in v14.2.0

authors: hzorr sibiraj-s

repo: sibiraj-s/ngx-editor


text:
Guess v1.2.1 rating

Here is the ZIPped .pgn of 33 games 5m+3s against other engines, mostly played with White, all from starting position : woodpusher-v1.2.1-33-games-5m+3s.zip

I guess v1.2.1 has about rating 1600.
Today i may let the newer v1.3.0 play against those same engines again, to see how Woodpusher improved. I will post the results here.

Very interesting! I'll take a look as soon as I find some time.
I've only used Stockfish as a sparring partner. When I clamp the ELO to 2000 they play about equal, but that's on my machine. The major improvement I've made is with respect to move ordering. That greatly improved how deep it is able to go within the allotted time. Previously it has never been able to finish the "mate in 10" test, but now it succeeds in about 15 secs.
I'm also using CuteChess as a GUI, but on Windows. The illegal move issue turned out to be bad timing on my part, but since I made a couple of fixes I've never seen it again. Maybe it behaves differently on Linux, but there was a bug in the code that needed fixing regarding of OS.
Thank you so much for the interest you invest in my little project.

Right now I'm generating a more interesting opening book, with more options for each game state. As it is now, with the current version, two instances of WP will always play the same game. Additionally, WP will always open with E4.
I'll introduce a bit of randomness.

In fact a good opening book is a nice idea, but overall i decided not to use an opening book while playing engine-vs-engine games. An idea might be to create an UCI option to set the max ply of the opening book to reach positions for the engine to start its own evaluations. Such UCI option can be an extended version of the current 'OwnBook' option : 0 is no-book, 5 means 5 ply etc.
The randomness can also be an UCI option : 0 is none.
I have nothing against Woodpusher always playing a same variation (randomness 0), as a chess player it can help me to find better moves to "solve a puzzle" - being that position. I didn't yet find the time to play a game against v1.3.0, testing your "negative time adjustment" .. i will now and post it here later.

..and post it here later

[ replay game by LiChess link ]
[Event "engine-vs-engine"]
[Site "Holland @ https://lichess.org/DJcWNDxK "]
[Date "2024.12.01"]
[Round "?"]
[White "Woodpusher v1.3.0"]
[Black "Roelof Berkepeis"]
[Result "1-0"]
[ECO "A04"]
[GameDuration "00:22:43"]
[Opening "Reti Opening"]
[PlyCount "65"]
[TimeControl "1200+3"]

1. Nf3 {+0.28/8 31s} b6 {11s} 2. e3 {+0.62/8 31s} Bb7 {5.3s}
3. d4 {+0.68/7 5.9s} e6 {4.9s} 4. Bd3 {+0.62/7 19s} Nf6 {2.0s}
5. O-O {+0.49/7 19s} Be7 {5.3s} 6. c4 {+0.31/7 30s} Na6 {8.1s}
7. a3 {+0.55/7 8.6s} c5 {3.7s} 8. Nc3 {+0.69/8 34s} Nc7 {13s}
9. e4 {+0.71/8 34s} Ng4 {57s} 10. dxc5 {+1.24/7 8.6s} d6 {63s}
11. Qa4+ {+1.81/8 35s} Qd7 {13s} 12. Qxd7+ {+1.68/8 35s} Kxd7 {3.4s}
13. cxd6 {+1.74/8 35s} Bxd6 {2.5s} 14. h3 {+1.66/7 12s} Ne5 {2.6s}
15. Nxe5+ {+1.44/8 36s} Bxe5 {1.8s} 16. Be3 {+1.39/7 16s} Bxc3 {20s}
17. bxc3 {+1.64/7 10s} Na6 {5.0s} 18. a4 {+1.53/7 13s} Rac8 {5.6s}
19. a5 {+1.52/8 18s} Nc5 {4.1s} 20. Bxc5 {+1.48/9 32s} bxc5 {16s}
21. a6 {+1.79/9 21s} Ba8 {21s} 22. e5 {+1.72/8 33s} h5 {11s}
23. Ra5 {+1.76/7 7.0s} h4 {26s} 24. Rb1 {+1.72/8 20s} Rh5 {20s}
25. f4 {+1.92/10 49s} f6 {2.4s} 26. exf6 {+2.13/10 49s} gxf6 {3.2s}
27. Bg6 {+2.02/9 49s} Rh6 {5.8s} 28. f5 {+2.02/10 48s} e5 {14s}
29. Bf7 {+2.03/9 21s} Ke7 {19s} 30. Be6 {+2.19/10 17s} Rc7 {29s}
31. Rab5 {+2.24/10 48s} Rh8 {35s} 32. Rb8 {+2.23/10 34s} Rd8 {12s}
33. Rxd8 {+5.07/12 53s, Black resigns} 1-0

authors: sictransit tissatussa

repo: sictransit/woodpusher


text:
Update build flags for lua (Fix #217)

With theses flags, we can now compile with older and newer version of Ubuntu. I tested with Ubuntu 14.04.3 and CoreOS. :-)
If anybody can test with Mac OSX and others OS ;-)

Cool @Aurlin
I will check it later.

Hi @Aurlin
I test in my mac and find it works. I will merge it.
we will re-discuss this if anyone meets compile error later :-)
Thank you.

authors: Aurlin siddontang

repo: siddontang/ledisdb


text:
Some additions to the README

Based on our discussions, just edited in the README a bit. Feel free to use...

Awesome! Looks good :) Thank you!

authors: jholthusen sieren

repo: sieren/Homepoint


text:
Export function to verify individual signature

Summary
Calling the existing VerifyImageSignatures function multiple times for the same image with different verifiers will download the OCI manifest multiple times. This is inefficient and slow.
Exporting a function that verifies a single signature allows the decoupling of the fetch and verification stages.
Release Note

I don't think the test failure is related to the changes in the PR:
--- FAIL: TestReadWrite (0.07s)
    write_test.go:36: appending signatures: error writing layer: rename C:\Users\RUNNER~1\AppData\Local\Temp\TestReadWrite2597293721\001\blobs\sha256\e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b8551856907808 C:\Users\RUNNER~1\AppData\Local\Temp\TestReadWrite2597293721\001\blobs\sha256\e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855: Access is denied.
FAIL
FAIL	github.com/sigstore/cosign/pkg/oci/layout	0.111s

Seems reasonable to me!
Any objections to the new public API anyone?

OK then, merging!

authors: dlorenc ribbybibby

repo: sigstore/cosign


text:
ghcr.io/gythialy/golang-cross:v1.17.2 -> v1.17.2-1

Fixes the release maybe?
Release is getting the error:
...
Step #5:       • signing                   artifact=sget-darwin-arm64 cmd=./dist/cosign-linux-amd64
Step #5:    • docker images
Step #5:       • building docker image     image=gcr.io/projectsigstore/cosigned:1.3.0-arm64v8
Step #5:       • building docker image     image=gcr.io/projectsigstore/sget:1.3.0-arm64v8
Step #5:       • building docker image     image=gcr.io/projectsigstore/cosign:1.3.0-arm64v8
Step #5:       • building docker image     image=gcr.io/projectsigstore/sget:1.3.0-amd64
Step #5:       • building docker image     image=gcr.io/projectsigstore/cosigned:1.3.0-amd64
Step #5:       • building docker image     image=gcr.io/projectsigstore/cosign:1.3.0-amd64
Step #5:    ⨯ release failed after 460.13s error=failed to build gcr.io/projectsigstore/cosigned:1.3.0-arm64v8: exit status 125: unknown flag: --load
Step #5: See 'docker --help'.
Step #5:
Step #5: Usage:  docker [OPTIONS] COMMAND
Step #5:
Step #5: A self-sufficient runtime for containers
Step #5:
Step #5: Options:
Step #5:       --config string      Location of client config files (default
...

See https://github.com/sigstore/cosign/issues/988

Gonna leave this one for @cpanato who may have insight into whether this is the right change.

let me run in my fork

authors: cpanato dekkagaijin mattmoor


text:
Change scorecard to use reusable workflow

Summary

The motivation for this PR is to change rekor-monitor to use Scorecard reusable workflow from sigstore/community reusable workflow.
Good to know:

I have removed the permissions needed to run Scorecard on private repositories. They are contents: read and actions: read.
I have "removed" the old repo_token, in the reusable workflow called scorecard_token, cause it was not being used as seen in Actions logs https://github.com/sigstore/rekor-monitor/actions/runs/3916334289/jobs/6695353686#step:4:12.

Let me know if these permissions are needed for another reason in this repo or if scorecard_token should be used.
Release Note

Config changes: Change Scorecard to use reusable workflow from sigstore/community
Documentation

None.

I have a person that I have an account there could be the hackers was looking through my texts in my account and he close it without consent I will keep keep continues open I will report this to to get hopped down hike in the app then I prevent me to send you information over and over this people are my neighbor hope you guys seeing this he will not stop it how do you so severely that he's people are in a bed next to me there are in this location I tried to send information out there

repo: sigstore/rekor-monitor