text:
[BUG] Crash on iOS 13.x

Describe the bug
I used this library because we're supporting iOS 13, and I wanted a scrollview paging. but I got a crash when I run this on iOS 13.
To Reproduce

I just have this code in my View

Pager(page: $page,
                      data: viewModel.items,
                      id: \.id,
                      content: { item in
                        OnboardingView(info: item)
                            .frame(width: UIScreen.main.width, height: .infinity, alignment: .center)
                      })
                    .preferredItemSize(CGSize(width: UIScreen.main.width, height: .infinity))

CRASH Details:
Terminating app due to uncaught exception 'CALayerInvalidGeometry', reason: 'CALayer position contains NaN: [nan nan]. Layer: <SwiftUI.ImageLayer:0x600001f5aa00; position = CGPoint (0 0); bounds = CGRect (0 0; 0 0); delegate = <UIView: 0x7ff31de8ce30; frame = (0 0; 0 0); anchorPoint = (0, 0); autoresizesSubviews = NO; layer = <SwiftUI.ImageLayer: 0x600001f5aa00>>; contents = <CGImage 0x7ff31de75db0> (IP)
	<<CGColorSpace 0x600000e4c480> (kCGColorSpaceICCBased; kCGColorSpaceModelRGB; sRGB IEC61966-2.1)>
		width = 977, height = 770, bpc = 8, bpp = 32, row bytes = 3908
		kCGImageAlphaPremultipliedLast | 0 (default byte order)  | kCGImagePixelFormatPacked
		is mask? No, has masking color? No, has soft mask? No, has matte? No, should interpolate? Yes; allowsGroupOpacity = YES; contentsMultiplyColor = (null); contentsScale = 3; anchorPoint = CGPoint (0 0)>'
*** First throw call stack:
(
	0   CoreFoundation                      0x00007fff23e3dcce __exceptionPreprocess + 350
	1   libobjc.A.dylib                     0x00007fff50b3b9b2 objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff23e3db0c +[NSException raise:format:] + 188
	3   QuartzCore                          0x00007fff2b4cb30f _ZN2CA5Layer12set_positionERKNS_4Vec2IdEEb + 173
	4   QuartzCore                          0x00007fff2b4b99c0 -[CALayer setPosition:] + 35
	5   SwiftUI                             0x00007fff2c6a102e $s7SwiftUI11DisplayListV11ViewUpdaterC8PlatformO14updateGeometry2of8position0K7Changed6origin0mL04size0nL0yAE0E4InfoVz_So7CGPointVSbASSbSo6CGSizeVSbtFZ + 142
	6   SwiftUI                             0x00007fff2c8aad81 $s7SwiftUI11DisplayListV11ViewUpdaterC8PlatformO14updateGeometry33_FC53F098534E3B876A0A95CFFF8C8D27LL_4item4size5state15clipRectChangedSbAE0E4InfoVz_AC4ItemVSo6CGSizeVSPyAE5ModelO5StateVGSbtFZ + 1857
	7   SwiftUI                             0x00007fff2c8a8a9d $s7SwiftUI11DisplayListV11ViewUpdaterC8PlatformO11updateState33_FC53F098534E3B876A0A95CFFF8C8D27LL_4item4size5stateyAE0E4InfoVz_AC4ItemVSo6CGSizeVSPyAE5ModelO0I0VGtFZ + 685
	8   SwiftUI                             0x00007fff2c8a832c $s7SwiftUI11DisplayListV11ViewUpdaterC8PlatformO010updateItemE0_4item5stateyAE0E4InfoVz_AC0I0VSPyAE5ModelO5StateVGtFZ + 6604
	9   SwiftUI                             0x00007fff2c8a68ee $s7SwiftUI11DisplayListV11ViewUpdaterC8PlatformO08makeItemE04item5stateAE0E4InfoVAC0I0V_SPyAE5ModelO5StateVGtFZ + 238
	10  SwiftUI                             0x00007fff2c6ddc29 $s7SwiftUI11DisplayListV11ViewUpdaterC8PlatformO08makeItemE04item5stateAE0E4InfoVAC0I0V_SPyAE5ModelO5StateVGtFZTA + 9
	11  SwiftUI                             0x00007fff2c4ec140 $s7SwiftUI11DisplayListV11ViewUpdaterC0E5CacheV6update4item5state3tag2in04makeE00hE0AG6ResultVAC4ItemV_SPyAE5ModelO5StateVGAG3TagOAE0E4InfoV2IDVA_AR_AWtXEyA_z_ArWtXEtF + 608
	12  SwiftUI                             0x00007fff2c6dcd57 $s7SwiftUI11DisplayListV11ViewUpdaterC010updateItemE033_C85E9C9D8E8767197A33852BB19DA7BELL9container4from10localStateyAE9ContainerAGLLVz_AC0H0VAE5ModelO0U0VztF + 167
	13  SwiftUI                             0x00007fff2c6dcb41 $s7SwiftUI11DisplayListV11ViewUpdaterC015updateInheritedE033_C85E9C9D8E8767197A33852BB19DA7BELL9container4from11parentStateyAE9ContainerAGLLVz_AC4ItemVSPyAE5ModelO0U0VGtF + 785
	14  SwiftUI                             0x00007fff2c6dc2f3 $s7SwiftUI11DisplayListV11ViewUpdaterC6update33_C85E9C9D8E8767197A33852BB19DA7BELL9container4from11parentStateyAE9ContainerAGLLVz_ACSPyAE5ModelO0T0VGtF + 147
	15  SwiftUI                             0x00007fff2c6dcb8d $s7SwiftUI11DisplayListV11ViewUpdaterC015updateInheritedE033_C85E9C9D8E8767197A33852BB19DA7BELL9container4from11parentStateyAE9ContainerAGLLVz_AC4ItemVSPyAE5ModelO0U0VGtF + 861
	16  SwiftUI                             0x00007fff2c6dc2f3 $s7SwiftUI11DisplayListV11ViewUpdaterC6update33_C85E9C9D8E8767197A33852BB19DA7BELL9container4from11parentStateyAE9ContainerAGLLVz_ACSPyAE5ModelO0T0VGtF + 147
	17  SwiftUI                             0x00007fff2c6dcb8d $s7SwiftUI11DisplayListV11ViewUpdaterC015updateInheritedE033_C85E9C9D8E8767197A33852BB19DA7BELL9container4from11parentStateyAE9ContainerAGLLVz_AC4ItemVSPyAE5ModelO0U0VGtF + 861
	18  SwiftUI                             0x00007fff2c6dc2f3 $s7SwiftUI11DisplayListV11ViewUpdaterC6update33_C85E9C9D8E8767197A33852BB19DA7BELL9container4from11parentStateyAE9ContainerAGLLVz_ACSPyAE5ModelO0T0VGtF + 147
	19  SwiftUI                             0x00007fff2c6dcb8d $s7SwiftUI11DisplayListV11ViewUpdaterC015updateInheritedE033_C85E9C9D8E8767197A33852BB19DA7BELL9container4from11parentStateyAE9ContainerAGLLVz_AC4ItemVSPyAE5ModelO0U0VGtF + 861
	20  SwiftUI                             0x00007fff2c6dc2f3 $s7SwiftUI11DisplayListV11ViewUpdaterC6update33_C85E9C9D8E8767197A33852BB19DA7BELL9container4from11parentStateyAE9ContainerAGLLVz_ACSPyAE5ModelO0T0VGtF + 147
	21  SwiftUI                             0x00007fff2c6dcb8d $s7SwiftUI11DisplayListV11ViewUpdaterC015updateInheritedE033_C85E9C9D8E8767197A33852BB19DA7BELL9container4from11parentStateyAE9ContainerAGLLVz_AC4ItemVSPyAE5ModelO0U0VGtF + 861
	22  SwiftUI                             0x00007fff2c6dc2f3 $s7SwiftUI11DisplayListV11ViewUpdaterC6update33_C85E9C9D8E8767197A33852BB19DA7BELL9container4from11parentStateyAE9ContainerAGLLVz_ACSPyAE5ModelO0T0VGtF + 147
	23  SwiftUI                             0x00007fff2c6dcb8d $s7SwiftUI11DisplayListV11ViewUpdaterC015updateInheritedE033_C85E9C9D8E8767197A33852BB19DA7BELL9container4from11parentStateyAE9ContainerAGLLVz_AC4ItemVSPyAE5ModelO0U0VGtF + 861
	24  SwiftUI                             0x00007fff2c6dc2f3 $s7SwiftUI11DisplayListV11ViewUpdaterC6update33_C85E9C9D8E8767197A33852BB19DA7BELL9container4from11parentStateyAE9ContainerAGLLVz_ACSPyAE5ModelO0T0VGtF + 147
	25  SwiftUI                             0x00007fff2c6dcb8d $s7SwiftUI11DisplayListV11ViewUpdaterC015updateInheritedE033_C85E9C9D8E8767197A33852BB19DA7BELL9container4from11parentStateyAE9ContainerAGLLVz_AC4ItemVSPyAE5ModelO0U0VGtF + 861
	26  SwiftUI                             0x00007fff2c6dc2f3 $s7SwiftUI11DisplayListV11ViewUpdaterC6update33_C85E9C9D8E8767197A33852BB19DA7BELL9container4from11parentStateyAE9ContainerAGLLVz_ACSPyAE5ModelO0T0VGtF + 147
	27  SwiftUI                             0x00007fff2c6dcb8d $s7SwiftUI11DisplayListV11ViewUpdaterC015updateInheritedE033_C85E9C9D8E8767197A33852BB19DA7BELL9container4from11parentStateyAE9ContainerAGLLVz_AC4ItemVSPyAE5ModelO0U0VGtF + 861
	28  SwiftUI                             0x00007fff2c6dc2f3 $s7SwiftUI11DisplayListV11ViewUpdaterC6update33_C85E9C9D8E8767197A33852BB19DA7BELL9container4from11parentStateyAE9ContainerAGLLVz_ACSPyAE5ModelO0T0VGtF + 147
	29  SwiftUI                             0x00007fff2c6dc10e $s7SwiftUI11DisplayListV11ViewUpdaterC6update04rootE04from7versionySo6UIViewC_A2C7VersionVtF + 782
	30  SwiftUI                             0x00007fff2c44ec44 $s7SwiftUI14_UIHostingViewC17renderDisplayList_7versionSbAA0fG0V_AG7VersionVtF + 52
	31  SwiftUI                             0x00007fff2c8149ac $s7SwiftUI16ViewRendererHostPAAE6render8interval17updateDisplayListySd_SbtFyyXEfU_ + 844
	32  SwiftUI                             0x00007fff2c80a3d5 $s7SwiftUI16ViewRendererHostPAAE6render8interval17updateDisplayListySd_SbtF + 373
	33  SwiftUI                             0x00007fff2c96a0c2 $s7SwiftUI14_UIHostingViewC14layoutSubviewsyyF + 226
	34  SwiftUI                             0x00007fff2c96a0e5 $s7SwiftUI14_UIHostingViewC14layoutSubviewsyyFTo + 21
	35  UIKitCore                           0x00007fff4911aae8 -[UIView(CALayerDelegate) layoutSublayersOfLayer:] + 2478
	36  QuartzCore                          0x00007fff2b4c0180 -[CALayer layoutSublayers] + 255
	37  QuartzCore                          0x00007fff2b4c630b _ZN2CA5Layer16layout_if_neededEPNS_11TransactionE + 523
	38  QuartzCore                          0x00007fff2b4d19a2 _ZN2CA5Layer28layout_and_display_if_neededEPNS_11TransactionE + 80
	39  QuartzCore                          0x00007fff2b41aa14 _ZN2CA7Context18commit_transactionEPNS_11TransactionEd + 324
	40  QuartzCore                          0x00007fff2b44e3ef _ZN2CA11Transaction6commitEv + 649
	41  UIKitCore                           0x00007fff48c127fc _UIApplicationFlushRunLoopCATransactionIfTooLate + 104
	42  UIKitCore                           0x00007fff48cbf89c __handleEventQueueInternal + 7487
	43  UIKitCore                           0x00007fff48cb606b __handleHIDEventFetcherDrain + 88
	44  CoreFoundation                      0x00007fff23da1c71 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
	45  CoreFoundation                      0x00007fff23da1b9c __CFRunLoopDoSource0 + 76
	46  CoreFoundation                      0x00007fff23da1374 __CFRunLoopDoSources0 + 180
	47  CoreFoundation                      0x00007fff23d9bf6e __CFRunLoopRun + 974
	48  CoreFoundation                      0x00007fff23d9b884 CFRunLoopRunSpecific + 404
	49  GraphicsServices                    0x00007fff38b5ac1a GSEventRunModal + 139
	50  UIKitCore                           0x00007fff48c19220 UIApplicationMain + 1605
	51  BitcoinComCard                      0x0000000103921b5b main + 75
	52  libdyld.dylib                       0x00007fff519b910d start + 1
	53  ???                                 0x0000000000000001 0x0 + 1
)
libc++abi.dylib: terminating with uncaught exception of type NSException
*** Terminating app due to uncaught exception 'CALayerInvalidGeometry', reason: 'CALayer position contains NaN: [nan nan]. Layer: <SwiftUI.ImageLayer:0x600001f5aa00; position = CGPoint (0 0); bounds = CGRect (0 0; 0 0); delegate = <UIView: 0x7ff31de8ce30; frame = (0 0; 0 0); anchorPoint = (0, 0); autoresizesSubviews = NO; layer = <SwiftUI.ImageLayer: 0x600001f5aa00>>; contents = <CGImage 0x7ff31de75db0> (IP)
	<<CGColorSpace 0x600000e4c480> (kCGColorSpaceICCBased; kCGColorSpaceModelRGB; sRGB IEC61966-2.1)>
		width = 977, height = 770, bpc = 8, bpp = 32, row bytes = 3908
		kCGImageAlphaPremultipliedLast | 0 (default byte order)  | kCGImagePixelFormatPacked
		is mask? No, has masking color? No, has soft mask? No, has matte? No, should interpolate? Yes; allowsGroupOpacity = YES; contentsMultiplyColor = (null); contentsScale = 3; anchorPoint = CGPoint (0 0)>'
terminating with uncaught exception of type NSException
CoreSimulator 732.17 - Device: iPhone 11 Pro Max (E3DAF89C-34D6-4FBB-9B7B-34A19459E3D6) - Runtime: iOS 13.4 (17E255) - DeviceType: iPhone 11 Pro Max

Expected behavior
it will not crash on iOS 13 --- it works fine on iOS 14 though :)
When I removed the whole Pager code, and replaced with horizontal scrollview (without paging), it runs on my ios13 device. Which is how I figured it's the SwiftUIPager library.
Environment:
(Real Device)

OSX: iOS 13.6

Device: iPhoneXS
(Simulator)

OSX: iOS 13.4

Device: iPhone 11 Pro Max

SwiftUIPager version
SwiftUIPager (1.13.0) // from Podfile.lock

Hi @jenbitcoin , when I use your code in iOS 14 I get a warning that says [SwiftUI] Invalid frame dimension (negative or non-finite).

What are you trying to achieve exactly? If you look at the error, it mentions CALayer, SwiftUI and a NaN. This must be because you're using .infinity. I bet you've seen that in some tutorials, but the use it with frame(maxWidth:maxHeight:). Apple also recommends using a GeometryReader rather than UIScreen.
If what you want is your page to take up all the available space, you don't need preferredItemSize. This simple Pager
contains items that will extend to take up the available space in the container

Actually, this code fails too:
struct ContentView: View {
    var body: some View {
        Text("Test on iPhone 11 Pro Max, iOS 13.3")
            .frame(width: UIScreen.main.bounds.width, height: .infinity, alignment: .center)
    }
}

The issue here is the use of .infinity, which is a NaN

Closing as it's not related to this framework

thanks @fermoya i'm very new to swiftUI, just learned it last week. thanks for pointing me to the right issue. have a great day

authors: fermoya jenbitcoin

repo: fermoya/SwiftUIPager


text:
Fixed error in Spin Python - Redis Outbound code sample

Content must go through a pre-merge checklist.
Pre-Merge Content Checklist
This documentation has been checked to ensure that:

[ ] The title, template, and date` are all set
[ ] Does this PR have a new menu item (anywhere in templates/*.hbs files) that points to a document .md that is set to publish in the future? If so please only publish the .md and .hbs changes in real-time (otherwise there will be a menu item pointing to a .md file that does not exist)
[ ] File does not use CRLF, but uses plain LF (hint: use cat -ve <filename> | grep '^M' | wc -l and expect 0 as a result)
[ ] Has passed bart check
[ ] Has been manually tested by running in Spin/Bartholomew (hint: use PREVIEW_MODE=1 and run npm run styles to update styling)
[ ] Headings are using Title Case
[ ] Code blocks have the programming language set to properly highlight syntax and the proper copy directive
[ ] Have tested with npm run test and resolved all errors
[ ] Relates to an existing (potentially outdated) blog article? If so please add URL in blog to point to this content.

@tpmccallum  - Do you think we should link this page under the Redis Outbound example? Or mention 'The Spin SDK surfaces the Spin Redis interface to your language'

source: gharchive/pull-request

repo: fermyon/developer

license_type: permissive

license_source: github-api


text:
feat(cli): use code view instead of preview in "edit this page" links

Description
In "Edit this page" links in the docs, link to "code" version of the page instead of the "preview" version, which imo is a better ux for mdx.

Great add!

authors: chdeskur zachkirsch

repo: fern-api/fern


text:
🛑 PDF Association Solution Agent is down

In ece4d91, PDF Association Solution Agent (https://www.pdfa.org/solution-agent/) was down:

HTTP code: 521
Response time: 139 ms

Resolved: PDF Association Solution Agent is back up in 6a16c54 after 26 minutes.

source: gharchive/issue

license: MIT


text:
首页的 时长过滤 没有生效

非前端开发者，不太会看 F12 的日志，自己排查不出来问题。

是否启用了白名单免过滤板块的功能？

日志里有这些日志，不知道是否相关。

没有启用任何白名单功能。

B站相关的脚本逐个关闭测试了，依旧不生效。

请提供一下浏览器版本，可以测试一下如下功能：

首页的关键词过滤是否生效
播放页、搜索页的时长过滤是否生效
看一下使用的首页网址是 https://www.bilibili.com/ 还是 https://www.bilibili.com/index.html ，后者不会生效

Chrome 126.0.6478.127
播放页、搜索页都可以生效，只有首页不生效
首页是 https://www.bilibili.com/

关键词过滤也可以生效，唯独 时长过滤 没有生效

关键词过滤 也只生效了一次，然后首页再也不生效了。正常尝试回忆复现之前的操作。

我在相同版本 Chrome 没能复现
试一下首页的 UP主过滤和 BV 号过滤，右键单击 UP 主 / 右键单击标题 点击屏蔽以后视频是否立即消失？

首页

用 https://www.bilibili.com/ 重新打开一个新标签，有一定概率生效，不生效的次数更多；
不管有没有生效，Ctrl+R 刷新后，一定不生效；
关键词过滤 和 时长过滤会一起生效或一起不生效

搜索页和播放页
不管什么情况，时长和关键词都能生效

我在相同版本 Chrome 没能复现
试一下首页的 UP主过滤和 BV 号过滤，右键单击 UP 主 / 右键单击标题 点击屏蔽以后视频是否立即消失？

只有在生效的时候，才会立刻消失。
不生效的时候，右键屏蔽没有任何反应，但是黑名单里会增加名称。

排查出来了，是这个插件： https://chromewebstore.google.com/detail/相关法律法规/cgcndfhnodpingjaaofffpkblamjfojp
关闭就一切正常了

排查出来了，是这个插件： https://chromewebstore.google.com/detail/相关法律法规/cgcndfhnodpingjaaofffpkblamjfojp 关闭就一切正常了

这也太玄学了XD

当概率生效的时候，我就怀疑是不是和加载顺序有关，然后把会更改页面的插件全部排查了一遍。
可惜这个插件已经两年多没更新了。
所以这边能不能试试看兼容一下，不然就只能顶着各种恶心的缩写和和谐词了 🤣  。

当概率生效的时候，我就怀疑是不是和加载顺序有关，然后把会更改页面的插件全部排查了一遍。
可惜这个插件已经两年多没更新了。
所以这边能不能试试看兼容一下，不然就只能顶着各种恶心的缩写和和谐词了 🤣 。

看了一眼，那个插件会暴力的检测所有元素文本，所以我没法兼容它只能让它别太暴力.... 目前两个插件在首页只能有一个生效
如果有能力，可以 fork 那个插件的项目，在入口文件轻微修改一下让它不在 B 站首页运行，build 一个自己的版本

啊，非前端开发者劝退了。
行吧，只能二选一了。


text:
Digest is based on a partially ordered model schema blocking reproducibility

Prerequisites

[X] I checked the documentation and found no answer to my problem
[X] I checked the existing issues and made sure there are no similar bug reports

Category
Bug (unexpected behavior)
Expected Behavior
Digests should be based on completely sorted json. Completely sorted means recursively sorting all keys, arrays, and nested objects. It seems that nested objects are sorted by key but, arrays are not.
Observed Behavior
Digest is based on a json representation of the open api model schema. However, the json is only ordered by keys.
For example given a model
class SuperImportantCheck(Model):
    """Plus random docstring"""
    check: bool
    message: str
    counter: int

when Model.build_schema_digest() is called it runs schema = model.schema_json(indent=None, sort_keys=True)
for the given SuperImportantCheck Model, schema will equal
{"description": "Plus random docstring", "properties": {"check": {"title": "Check", "type": "boolean"}, "counter": {"title": "Counter", "type": "integer"}, "message": {"title": "Message", "type": "string"}}, "required": ["check", "message", "counter"], "title": "SuperImportantCheck", "type": "object"}

Notably, schema.required maps to an array with the unordered parameters ["check", "message", "counter"].
The unordered nature of the schema json means other agents hoping to interact with an agent must implement a Model with the same ordering such that the digests match.
To Reproduce
Modify uAgents/python/src/model.py to contain
 @staticmethod
    def build_schema_digest(model: Union["Model", Type["Model"]]) -> str:
        schema = model.schema_json(indent=None, sort_keys=True)
        print(schema)
        digest = hashlib.sha256(schema.encode("utf8")).digest().hex()

        return f"model:{digest}"

Then run python python/tests/test_model.py
Version
v0.17.0
Environment Details (Optional)
No response
Failure Logs (Optional)
No response
Additional Information (Optional)
No response

Thank you for opening this issue.
As you may have seen in the branches section or PR #374 just to name an example, we are very much aware of the topic.
Unfortunately we've been holding off of changing the way the digest is created for now because of backwards compatibility. Introducing a new way of calculating the digest will ultimately break compatibility for many existing agents so we need to be careful when rolling out such a change.
To minimise the amount of breaking changes we're working hard in-house to come up with a better solution for manifests in general which in turn will have an impact on how the digest will be created.
Coming back to your observation and what you've written under "expected behaviour":

Digests should be based on completely sorted json.

That is an assumption caused probably by the nature of our documentation. I'm convinced that there is no point in the docs where we state that Models used for agent to agent communication can differ in structure/order. It was always meant to be this way to allow for some flexibility but at the same time you'll never see examples or integrations where two agents that want to communicate don't share the exact same model definition (including order).
So for me that is an implicit definition and I want to apologise for being unclear in that regard.
We'll do our best to come up with a new way of treating the manifest in the near future and hope this will not block your progress or project in any way.

Leaving this issue open as a reminder

I had the same concerns regarding backward compatibility. I ran into this issue while implementing digest in an NPM package. To ensure that our agents are compatible with existing agents, we're implementing a digest that should be identical to the Python digest. I would like your opinion on our implementation of digest. We can continue the discussion at https://github.com/fetchai/uAgents/discussions/539. Current progress on our digest implementation can be found at https://github.com/Luceium/uAgents-NPM/blob/digest/src/model.ts#L74.

authors: Archento Luceium

repo: fetchai/uAgents


text:
html内容会出现错位问题

遇到一个问题：
我通过编辑器编辑一段内容，然后通过getContent获取html内容。会出现一个问题，具体如下。
假如我设置的内容是 aaaaaabbbbbbbbbbbcccccc  , 然后获取的内容会变成

于是我想在编辑的时候把内容填充到编辑器里的时候，会报js错误。因为内容换行了。

官方没有人解决吗？ 这个问题我想不止我遇到吧。

repo: fex-team/ueditor

license: mit

license_source: bigquery


text:
Adds FFaker::Bank.routing_number and accounting_number

This adds FFaker::Bank.routing_number and accounting_number
For our use case, we're looking for realistic looking US Bank account numbers and routing numbers.
Accounting numbers can very between 9 and 17 digits (Reference) Routing numbers have a checksum calculation on the last digit.

But, we probably should think about US suffix somewhere (in the module name?), if it's specific to a country.

Done.

@marocchino thank you for the approval. This PR has been in a green state for a little over 7 days with no new comments. I would love to see it merged this week.

You've waited too long. I think this will be okay.

authors: marocchino professor

repo: ffaker/ffaker


text:
The computer should be doing step 6

Move the contents of the new [projectname] folder out into the root

This is because we run wagtail start [name] instead of wagtail start [name] .. This complains about the requirements.txt already existing.
We should script this or something

Like the look of this, but having a lot of ball ache with the "Move the contents of the new [projectname] folder out into the root".
+1 for having the computer do this element.
What should the final requirements.txt look like, and where should it be?

Hi @mjdavies
The final requirements.txt should look like the one in this repo, with anything else you want added. I suppose you could use the one generated by wagtail start [name] . but I don't remember right now what's in it and what's missing.
The requirements.txt file should be at the root of your project alongside manage.py

Cheers Dan
The requirements.txt that wagtail start creates has these values
Django>=1.9,<1.10
wagtail==1.3.1
wagtail1.3.1 has these dependencies by the looks
beautifulsoup4 (4.4.1)
django-appconf (1.0.1)
django-compressor (2.0)
django-modelcluster (1.1)
django-taggit (0.18.0)
django-treebeard (3.0)
djangorestframework (3.3.2)
html5lib (0.9999999)
Pillow (3.1.1)
pytz (2015.7)
rcssmin (1.0.6)
rjsmin (1.0.12)
six (1.10.0)
Unidecode (0.4.19)
Willow (0.2.2)
I've always struggled a bit working out what needs to be in a production level requirements.txt.  We end up copying them from other projects alot, but I've got a sneaky feeling we're including some modules that aren't needed sometimes.
Be nice if torchbox would release a production level requirements.txt and keep that up to date for us.  I suppose that's not very practical though as there's so many things you can add onto it, as it's a django app at heart.
Thanks again

authors: danreeves mjdavies


text:
zsh: command not found: ffuf

Hi, I'm getting command not found error. I tried every way to configure the path as below:
export GOPATH=$HOME/go
export PATH=$PATH:$GOPATH/bin
export PATH=/usr/local/bin:$PATH
export $PATH=$PATH:/Users/Arpit/Desktop/ffuf
export GOPATH=/Users/Arpit/Desktop/Desktop/DevSecOps/BB/go
export GOPATH=/Users/Arpit/Desktop/ffuf

Hi @Th3R0oT, here you have a mess with Golang, not with Ffuf, if you look your exports, you can see you set FFUF in $GOPATH, which is wrong.
https://github.com/golang/go/wiki/SettingGOPATH

Still not working. I've changed the oath as per your given instruction as below:
export GOPATH=$HOME/go

Hi @Th3R0oT, you having a issue with GO, i recommend you do a clean install of GO and check some manuals how to do it and make your environment ready for any GO tools.

The installation dir for binaries that were built and installed by go get ... should be found in $HOME/go/bin .

authors: Th3R0oT bsysop joohoi

repo: ffuf/ffuf


text:
JPEG化したもののみ not valid

$ fgosccnt IMG_4620_R.JPG
filename,ドロ数
IMG_4620_R.JPG: not valid,

$ fgosccnt IMG_4620.PNG
filename,ドロ数,チョーク(x3),チョーク(x7),紙片(x3),紙片(x7),ヒポぐるみ(x3)
合計,,2,2,1,1,9
missing,,,,,,
IMG_4620.PNG,15,2,2,1,1,9

$ fgosccnt  IMG_4620_R.JPG
Traceback (most recent call last):
  File "c:/Users/nono_000/Documents/git/dev8/fgosccnt/fgosccnt.py", line 1711, in <module>
    csvfieldnames, outputcsv = get_output(inputs, args.debug)
  File "c:/Users/nono_000/Documents/git/dev8/fgosccnt/fgosccnt.py", line 1611, in get_output
    sc = ScreenShot(img_rgb, svm, svm_chest, svm_card, fileextention, debug)
  File "c:/Users/nono_000/Documents/git/dev8/fgosccnt/fgosccnt.py", line 421, in __init__
    self.items.append(Item(item_img_rgb, item_img_gray, svm, svm_card, fileextention, mode, debug))
  File "c:/Users/nono_000/Documents/git/dev8/fgosccnt/fgosccnt.py", line 778, in __init__
    self.ocr_digit(mode, debug)
  File "c:/Users/nono_000/Documents/git/dev8/fgosccnt/fgosccnt.py", line 1308, in ocr_digit
    self.dropnum =  self.detect_white_char(base_line, margin_right, font_size, debug=debug) + self.dropnum
  File "c:/Users/nono_000/Documents/git/dev8/fgosccnt/fgosccnt.py", line 1132, in detect_white_char
    line = self.get_number(base_line, margin_right, font_size)
  File "c:/Users/nono_000/Documents/git/dev8/fgosccnt/fgosccnt.py", line 1066, in get_number
    result = self.read_char(pt)
  File "c:/Users/nono_000/Documents/git/dev8/fgosccnt/fgosccnt.py", line 1250, in read_char
    tmpimg = cv2.resize(tmpimg, (win_size))
cv2.error: OpenCV(4.2.0) C:\projects\opencv-python\opencv\modules\imgproc\src\resize.cpp:4045: error: (-215:Assertion failed) !ssize.empty() in function 'cv::resize'

read_char の読み込み座標がマイナスになっている
JPEG版
[133, 152, 153, 180]
[113, 152, 133, 180]
[93, 152, 113, 180]
[64, 152, 84, 180]
[44, 152, 64, 180]
[24, 152, 44, 180]
[-5, 152, 15, 180]

PNG版
[133, 152, 153, 180]
[153, 152, 173, 180]
[133, 152, 153, 180]

アイテムの切り出し位置が一段ずれている

img2str() のleftcell_ptsの値

PNG [[15, 614, 203, 816], [15, 387, 203, 589]]
JPG[ [15, 614, 203, 816]]

PNGは二行目・三行目、JPGは三行目のみ認識

一つしか認識しなくても大丈夫な仕様なのでバグ

repo: fgophi/fgosccnt


text:
DB migration conflicts

Hi guys,
have question.
For example, I need to add migration for custom field in existing table.
I've made some coding in schema/*.php and added function version_102.
But time passed and new kanboard version released with new migrations.
Thus I have got confilct between my version_102 and "native" version_102.
Do you have any ideas about resolving this issue?

You should use a plugin that run custom migrations: https://kanboard.net/documentation/plugin-schema-migrations

@fguillot thanx

repo: fguillot/kanboard


text:
🛑 FedericoMazzei is down

In 98e23d6, FedericoMazzei (https://www.federicomazzei.com.ar) was down:

HTTP code: 502
Response time: 471 ms

Resolved: FedericoMazzei is back up in cab3be9.

repo: fideo/statusSites


text:
SPA mode with mobile sub navigation

Swap out window.location =

waiting this feature

authors: danharrin kahfieidn

repo: filamentphp/filament


text:
Tab with 2 or more custom components thows livewire error on click of actions

Package
filament/filament
Package Version
3.2.72
Laravel Version
11.6.0
Livewire Version
3.4.12
PHP Version
8.3.6
Problem description
When creating multiple tabs on a form and adding more than 1 custom component tab ( eg a custom tab that shows a table ),
if you save form or perform any action that requires re-rendering, the tab content is now gone and livewire throws an error Uncaught Snapshot missing on Livewire component with id: 6TUO5eLzk5BAWJjoChfx or  Uncaught Component not found: 6TUO5eLzk5BAWJjoChfx
Have tried with adding keys to the custom component but still does not rectify the issue, the ids it is not finding seem to be in a parent div.

Expected behavior
System to work with save buttons and all components remaining rendered
Steps to reproduce
Create a form with tabs, use multiple custom components
(I use 3 normal form tabs and 2 custom component tabs)
Save the form or perform an action that requires re-rendering.
Reproduction repository
https://github.com/d3vnz/filament-issue
Relevant log output
No response

Please give each component a key like
Tab::make('Tab3')
    ->schema([

       Livewire::make(CustomTabComponent1::class)->key('custom-one')
    ]),
Tab::make('Tab4')
    ->schema([

        Livewire::make(CustomTabComponent2::class)->key('custom-two')
    ]),
Tab::make('Tab5')
    ->schema([

        Livewire::make(CustomTabComponent3::class)->key('custom-three')
    ]),

Which is the equivalent of doing @livewire(CustomTabComponent3::class, [], key('custom-three')) etc

Have added the keys and still have same issue. Replicated on the repository attached to this issue as well.

So it shows the correct key but after rerender or save button, the entire component is empty

Then

Great that has fixed a big part of it.  Not sure if I should open up another bug for this one but if you look at repository now, notice I added a table to one of the custom components. This stops the save button on main form component from working. (Thought it was related issue to the key but maybe not)

Unfortunately we don't fully support tables embedded within forms at this time. There is a workaround though - use the ->lazy() method on the Livewire component with the table
Livewire::make(CustomTabComponent2::class)->key('custom-2')->lazy(),

I have the same issue, after adding ->key() the error disappeared, but when adding more than 5 livewire components into my InfoList, the page loads and is blank:
<?php

namespace App\Http\Livewire\Dashboards;

use App\Enums\PermissionsEnum;
use App\Http\Livewire\Dashboards\Company\ByDayDashboard;
use App\Http\Livewire\Dashboards\Company\ByOfferDashboard;
use App\Http\Livewire\Dashboards\Company\ByTrafficSourcesDashboard;
use App\Http\Livewire\Dashboards\Company\ByVerticalDashboard;
use App\Http\Livewire\Dashboards\Company\ByPartnerDashboard;
use App\Http\Livewire\ListComponent;
use Filament\Infolists\Components\Livewire;
use Filament\Infolists\Components\Tabs;
use Filament\Infolists\Infolist;
use Filament\Support\Enums\IconPosition;
use Illuminate\Contracts\View\View;
use Illuminate\Support\Facades\Auth;

class CompanyDashboard extends ListComponent
{
    public function mount()
    {
        Auth::user()->can(PermissionsEnum::SeeCompanyDashboard->value);
    }

    public function render(): View
    {
        return view('livewire.dashboards.company.company-dashboard');
    }

    public function infolist(Infolist $infolist): Infolist
    {
        return $infolist
            ->schema([
                Tabs::make('Tabs')
                    ->persistTab()
                    ->persistTabInQueryString()
                    ->id('company-dashboard')
                    ->tabs([
                        Tabs\Tab::make('By Day Dashboard')
                            ->icon('heroicon-m-calendar-days')
                            ->iconPosition(IconPosition::After)
                            ->schema([
                                Livewire::make(ByDayDashboard::class)
                                    ->key('leif-days'),
                            ]),
                        Tabs\Tab::make('By Traffic Source Dashboard')
                            ->icon('heroicon-m-circle-stack')
                            ->iconPosition(IconPosition::After)
                            ->schema([
                                Livewire::make(ByTrafficSourcesDashboard::class)
                                    ->key('leif-sources')
                                    ->lazy(),
                            ]),
                        Tabs\Tab::make('By Partner Dashboard')
                            ->icon('heroicon-m-user-group')
                            ->iconPosition(IconPosition::After)
                            ->schema([
                                Livewire::make(ByPartnerDashboard::class)
                                    ->key('leif-partners')
                                    ->lazy(),
                            ]),
                        Tabs\Tab::make('By Vertical Dashboard')
                            ->icon('heroicon-m-tag')
                            ->iconPosition(IconPosition::After)
                            ->schema([
                                Livewire::make(ByVerticalDashboard::class)
                                    ->key('leif-verticals')
                                    ->lazy(),
                            ]),
                        Tabs\Tab::make('By Offer Dashboard')
                            ->icon('heroicon-m-banknotes')
                            ->iconPosition(IconPosition::After)
                            ->schema([
                                Livewire::make(ByOfferDashboard::class)
                                    ->key('leif-offers')
                                    ->lazy(),
                            ]),
                    ]),
            ]);
    }

}

If I remove one of the Tabs with a component inside, or comment out the component inside the tab, everything shows as expected.

Ok, this seems to be Safari related:
SecurityError: Attempt to use history.replaceState() more than 100 times per 10 seconds
seems to prevent promises from being resolved, when I use Chrome I can see all my dashboard components.

authors: aotearoait danharrin madsem


text:
Fix $persist breaking Alpine when Tabs are used in modals

Description
We can persist the currently active Tab to localStorage:
Tabs::make('Example Tabs')
                ->persistTab(true)
                ->id('example-tabs')
                ->tabs([...])

I can see the value being updated and written in devtools when the tab is changed. However, when tabs are used in a modal which is being dismissed, the value of tab is incorrectly set to undefined during a Livewire commit hook.
When opening the modal again, the UI breaks and nothing is rendered. This error appears in the console:

The fix seems to be to fall back to the current tab, instead of trying to persist a potentially undefined array offset.
Visual changes
N/A
Functional changes

[ ] Code style has been fixed by running the composer cs command.
[x] Changes have been tested to not break existing functionality.
[ ] Documentation is up-to-date.

Related Alpine PR: https://github.com/alpinejs/alpine/pull/4128

Hello, I have a similar issue

Not sure if they are related but I just have a modal action in my header, and when I press confirm, the action is "loading" and I get this error in the console

authors: JackWH thethunderturner


text:
Feature/custom xlsx writer

Description
Since OpenSpout XLSX writer is a little bit limited (eg. doesn't format currency cells) I've tried to use different writer. The problem was that whenever I've tried to launch my custom job with different writer it always failed because there was another XLSX job in the queue. So here is my proposition to implement customWriter() method so it will skip the original job and proceed with the rest of the queued tasks.
Visual changes

Functional changes

[X] Code style has been fixed by running the composer cs command.
[X] Changes have been tested to not break existing functionality.
[X] Documentation is up-to-date.

I recognize the issue for not (easily) being able to format cells. Wouldn't it be a better solution to include a write in Filament and add native support for formatting of cells and perhaps some simple styling (bold, italic).

The problem is that there is no perfect package. I've actually added styling to Filament exports and been working on conditional styling but dropped it since OpenSpout doesn't suit all my needs. The package I use now is SimpleXLSXGen but it does not support chunking. PHP_XLSXWriter looks promising but I think it's no longer maintained. That's why I came with solution above.

Personally, I don't think this is the right solution. The method doesn't really allow you override anything "custom", just disable the existing job. IMO, you just need to bind a new CreateXlsxFile class to the container to replace the existing one, no? Then you can implement any processing you want.
Please let me know if I am misunderstanding

authors: danharrin ralphjsmit shepard153


text:
Fix: SpatieMediaLibraryFileUpload compatible visibility method

[x] Changes have been thoroughly tested to not break existing functionality.
[x] New functionality has been documented or existing documentation has been updated to reflect changes.
[x] Visual changes are explained in the PR description using a screenshot/recording of before and after.

Really not sure about this... it overwrites the user's defined custom properties. And why doesn't Spatie document this as a secure way to implement private visibility? 🤔

Yes, this may conflict with other settings of some users, I intend to close this PR.

authors: danharrin killjin


text:
使用时 报错

Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/urllib3/connectionpool.py", line 445, in _make_request
six.raise_from(e, None)
File "", line 3, in raise_from
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/urllib3/connectionpool.py", line 440, in _make_request
httplib_response = conn.getresponse()
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/http/client.py", line 1349, in getresponse
response.begin()
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/http/client.py", line 316, in begin
version, status, reason = self._read_status()
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/http/client.py", line 277, in _read_status
line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/socket.py", line 704, in readinto
return self._sock.recv_into(b)
socket.timeout: timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/requests/adapters.py", line 440, in send
resp = conn.urlopen(
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/urllib3/connectionpool.py", line 755, in urlopen
retries = retries.increment(
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/urllib3/util/retry.py", line 532, in increment
raise six.reraise(type(error), error, _stacktrace)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/urllib3/packages/six.py", line 770, in reraise
raise value
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/urllib3/connectionpool.py", line 699, in urlopen
httplib_response = self._make_request(
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/urllib3/connectionpool.py", line 447, in _make_request
self._raise_timeout(err=e, url=url, timeout_value=read_timeout)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/urllib3/connectionpool.py", line 336, in _raise_timeout
raise ReadTimeoutError(
urllib3.exceptions.ReadTimeoutError: HTTPConnectionPool(host='127.0.0.1', port=7890): Read timed out. (read timeout=35)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/yingliming/Desktop/xlhy/python_apollo_demo/demo.py", line 4, in
client.start()
File "/Users/yingliming/Desktop/xlhy/python_apollo_demo/apolloclient.py", line 63, in start
self._long_poll()
File "/Users/yingliming/Desktop/xlhy/python_apollo_demo/apolloclient.py", line 121, in _long_poll
r = requests.get(url=url, params={
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/requests/api.py", line 75, in get
return request('get', url, params=params, **kwargs)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/requests/api.py", line 61, in request
return session.request(method=method, url=url, **kwargs)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/requests/sessions.py", line 529, in request
resp = self.send(prep, **send_kwargs)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/requests/sessions.py", line 645, in send
r = adapter.send(request, **kwargs)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/requests/adapters.py", line 532, in send
raise ReadTimeout(e, request=request)
requests.exceptions.ReadTimeout: HTTPConnectionPool(host='127.0.0.1', port=7890): Read timed out. (read timeout=35)

30秒的超时不够，服务端默认是60秒，所以需要将30改成大于60的数字

https://github.com/chunlaiqingke/apyllo
这里做了维护，可以交流一下

repo: filamoon/pyapollo


text:
Bug: Dvd drive is missing tooltip on the sidebar

Description
Simple and low priority:
In the navigation, there's a DVD drive. It seems to have an empty tooltip. (including eject button)

Steps To Reproduce
In the left nav pane, hover the drive.
Requirements
Tooltip with text. Either for the drive or the Eject button.
Files Version
2.5.29
Windows Version
10.0.22621.2361
Log File
debug.log

Thanks for the report, I've added this to the project board.

@Jay-o-Way Is this still an issue in the preview version? https://files.community/download/preview

I fixed the issue where the Eject button's tooltip was not displayed ccorrectly in v2.5.32

Dvd drive is missing tooltip
Can you share a screenshot that shows info instead of you hovering on Eject button?

repo: files-community/Files


text:
Please add an interface for displaying and managing all the fonts in the folder C:\Windows\Fonts

What feature or improvement do you think would benefit Files?
Explorer have already provides a user-friendly interface for the C:\Windows\Fonts folder. I hope Files can also have a similar interface to manage fonts.
Requirements
null
Files Version
3.0.15.0
Windows Version
10.0.22631.2715
Comments
No response

Thanks for the feedback, Windows File Explorer doesn't use a different interface compared to Files. You can set it to grid view with the tool bar options.


text:
Open in new tab

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here. Ex: What device type/UI layout and app version?
I replaced the standard File Explorer with Files.
When I open Files through another program like Firefox, it always starts in a new instance.
It would be great if there were a setting, to toggle if it should open in a new instance or a new tab when opening it from another program by clicking on "show location".

Thanks for this suggestion. This is currently being implemented as part of #3382


text:
Newtonsoft.Json.Serialization crash when entering folder

Explain the bug
Unhandled hard crash when entering new directories. Did not happen consistently, but occurred three times within ten minutes. The folders in question were 'large' -- either containing several hundred image files or nested subfolders. My layout mode is on 'Grid View (Large)'.
To reproduce
Open a large folder soon after app start with layout mode set to Grid View (Large).
Log
debug.log
I have redacted folder names from the log file for the sake of privacy.
Expected behavior
No crashes or a more graceful crash.
System Information
Edition	Windows 10 Home
Version	21H1
Installed on	13/02/2021
OS build	19043.1052
Experience	Windows Feature Experience Pack 120.2212.2020.0
Version 1.5.0.0
Additional comment
Problem did not reoccur when restarting app. Maybe because the directories were cached?

Hello, this issue should be fixed in latest version which is currently in beta.
You can try 2 workarounds that were found for similar issues.
Workaround 1:

Turn Off "Enable individual preferences for individual directories" in Settings > Files and Folders
Set Tiles or GridView layout mode

Workaround 2:

Disable these two settings (turn off caching) under Experimental

Thanks very much for the advice, I'll try it out.


text:
win+e for new windows

before while Im uisng the windows files I usually use win+e to add a new windows of files but I cant do it here it will just open a new tab and u can open new tab with ctrl+t so u can adda a setting saying win+e to open new windows,my english is poor some of it im using google translate Please excuse me
What's the Problem?
I try to use win+e to open a new windows
Solution/Idea
add a setting writting win+e to open new windows
Alternatives
idk
Priorities

Capability
Priority

This proposal will allow developers to accomplish W
Must

This proposal will allow end users to accomplish X
Should

This proposal will allow developers to accomplish Y
Could

This proposal will allow end users to accomplish Z
Won't

Files Version
2.1.5.0
Windows Version
Windows Home Inside Preview Build 22543.rs_prerelease.220122-2315(Im using DEV)
Comments
No response

plzzzz help, this matter lot to me

@littleblack111 It's not exactly labeled the way you might expect but you can get the behavior you're looking for by turning on the option to open a new instance when opening an item from the jumplist.

wdym

where is it

Settings dialog > preferences > startup settings

sorry Im using chinease


text:
feat: 🎸 add typescript type definitions

Adds support for Typescript by adding type definitions allowing users of
this component to get autocomplete and type-safe usage of this component
Closes #76

any chance to get this merged?

This package is pretty important for most of the people who uses Filestack with React, I don't see many activity by the Filestack team maintaining it, if more effort was put on this would be very appreciated by your customers.

Please approve

authors: gabrielsch jayp lstanden

repo: filestack/filestack-react


text:
Order of transformer tests

Figure out why the order of transformer tests in BFS and DFS is not as expected

https://www.icloud.com/keynote/0d0ntSXt6IGcf5dlIz-axOp6A#Scheduling


text:
Update sbt to 1.5.5

Updates org.scala-sbt:sbt from 1.3.13 to 1.5.5.
Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

labels: library-update, semver-minor

Superseded by #1426.

repo: finagle/finch


text:
Can't find .gitmessage file

Looks like this bug still exists :(

#28

Fixed in 807509556f59fed267ca8e28f65deb6b1e64c5ac

authors: Sarabadu dideler rkotze

repo: findmypast-oss/git-mob


text:
Tenant rules

Is this code something we still need?

I think this is old stuff is it not?

repo: findonflow/find


text:
IllegalStateException: Not on FX application thread

As per a comment on a commit, I am also getting this error trying to run the Racer class directly from a fresh clone. This also happens on a custom class.
Machine specifications:
Windows 10
java version "1.8.0"
Java(TM) SE Runtime Environment (build 1.8.0-b132)
Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode)
javac 1.8.0
Full error:
Exception in thread "main" java.lang.IllegalStateException: Not on FX application thread; currentThread = main
at com.sun.javafx.tk.Toolkit.checkFxUserThread(Unknown Source)
at com.sun.javafx.tk.quantum.QuantumToolkit.checkFxUserThread(Unknown Source)
at javafx.scene.Scene.(Unknown Source)
at javafx.scene.Scene.(Unknown Source)
at GameArena.(GameArena.java:125)
at Racer.(Racer.java:55)
at Racer.main(Racer.java:215)
Using Platform.runLater on the offending line seems to fix some things but breaks others.

interesting... most builds seem happy with this, although it does sound like an this issue marvin raised on a recent pull request: https://github.com/finneyj/Racer/pull/1
Does this happen on a clean build of this repo, or only after you've made changes?

This happens on a clean build

very curious, as this is find on most builds...

Update: I have updated to the latest version of Java (and this seems to have fixed it.
java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)

ahh, cool. :-)
Just a bug in the JavaFX  code then. most likely just some validation that was a bit too strict. please close this issue off if you're happy.

authors: cbartzis finneyj

repo: finneyj/Racer


text:
Add Maturity Matrix Excel sheet

Ensure we maintain a copy of the maturity matrix that was posted to the GitHub
Discussions in source control before we transform it into a table.
In a subsequent PR we'll turn this into an HTML table.

/easycla

Hi @amaltson - Can you check with @claredillon the Excel sheet contributed into the repo is the latest release version as the following Discussion does have the correct versions uploaded as PDFs.
https://github.com/finos/InnerSource/discussions/12#discussioncomment-1022570

Hi @amaltson - Can you check with @claredillon the Excel sheet contributed by this PR is the latest release version as the following Discussion does have the correct versions uploaded as PDFs.
#12 (comment)

I grabbed the Excel file from @claredillon comment. I skipped the PDFs as they can't be changed and I figured we want to keep something that's more source controllable and changeable.
Looking into the automatic conversion, we'll actually need to export each Spreadsheet into a CSV and then run pandoc on that. I'll try to give that a whirl soon.

Also, we need to capture the feedback provided by @aaronsearle in the discussion below. Maybe this should now be raised as an Issue once this PR has been accepted and merged?
#12 (reply in thread)

Agreed, let's do that as a separate commit to show our work 😄

authors: amaltson mcleo-d

repo: finos/InnerSource


text:
Relation: Add support for pivot

relies on https://github.com/finos/legend-pure/pull/807

# Summary

We are bringing the magic of SecView `DataCube` in `Alloy`!

Unlike the existing query builder tools in Alloy like Databrowser and Alloy Query, where the focus is the form editor which is used to incrementally build the query, `DataCube` focus on allowing users incrementally build up the grid view of their data.

[screenshot]

One can think of `DataCube` as a data report builder tool, the report built by `DataCube` contains 2 parts: the data-fetching layer, i.e. the data query, and the layout customization. These are also the 2 main pieces of work: improving data query capabilities in Alloy and bringing in the `DataCube`'s rich set of layout features.

# Layout Features

# Query Capabilities

Alloy has supported most query functions that `DataCube` support, with exceptions for a few, such as `pivot` (also known as `h-pivot`), `group by rollup`.
https://docs.snowflake.com/en/sql-reference/constructs/pivot
https://docs.snowflake.com/en/sql-reference/constructs/group-by-rollup

- [ ] TDS source:
  - [x] project()
  - [x] Import CSV
  - [ ] Service
  - [ ] DataSpace
- [x] extend()
- [x] distinct()
- [x] drop()
- [x] filter()
- [x] groupBy(): aka v-pivot
- [ ] groupByRollUp()/groupByCube()
- [ ] limit
- [ ] pivot(): aka h-pivot
- [ ] pivotWithTotal()
- [x] rename()
- [ ] slice
- [ ] sort
- [x] select(): for show/hide columns

The general form of the query being built/supported by this UI is

TDS
->groupBy() // v-pivot (form the tree map on the left)
->pivot() // h-pivot
->extend() // allow creating new columns
->filter()
->select()
->rename()
->sort()
->limit()
(->slice()) // an optimization we can do to lessen memory usage

> We must confirm the form of the query as the more things coming after `pivot()` the more complicated/brittle the query is potentially

# Application Architecture

- [ ] Support different query edition workflows (this potentially allow us to merge back into `Alloy Query`)
- [ ] Support saving the query with layout configuration (consider saving this to local disk for now or MongoDB store)
- [ ] Do not auto-apply changes like `Alloy Query` so we can better support undo/redo

Future

FUTURE Split View (2 queries or more and you can use the row as the input for the bottom one)

FUTURE Local caching

FUTURE Support Paremters

FUTURE Plotting/Graphing?

FUTURE Streaming data!

FUTURE When specifying the filter, we can search for value: think about this, this can be turned on/off as it potentially stresses the DB

FUTURE Support undo/redo

FUTURE Show result set summary (time it takes, number of rows, etc.)

Horizontal Pivot (aka pivot):

The total columns (--> this will require group by rollup)
Arrangement of the total columns (last or first)
Default aggregation per data type: do not aggregate on strings
Columns can be excluded from h-pivot

Vertical Pivot (aka group-by):

Root aggregation (basically we need group-by rollup)
Tree representation: that supports drilldown (drilling down will fire sub-query)

Extended Column (aka Derivation)

Create derivation by right-clicking the grid
Concern: what is the order of operation: can we filter on extended columns, can we pivot, etc.?

LAYOUT Column pinning: you can drag and drop the vertical rule next the v-pivot to freeze the column when scrolling horizontally

Column Rename

Column Selection

Column Rearrange

In-grid Interaction:

FUTURE Filter out/in like in query grid
Column Auto-Sizing: double click to

Filter

Add new filter condition for selected value(s)

Sort

In grid sorting
Absolute sorting

Layout:

LAYOUT Grid

Hide/Show root aggregation
Row limit: affects all level (even for the drilldown -> show a warning about the row limit to user at the bottom of the screen)
Show selection stats: the stats of the selected columns
Show lines: Tree, Horizontal, Vertical
Scale Number: basis point (0.01%), percentage (%), million (m), billion (b), thousands (k), auto (b/m/k)
Display warning when truncated (show as ######), or display elipsis when truncated
Font: select font, size, italic, bold
Color: fore/background: normal, negative, zero, error
Alternatate color every ? row, choose color

LAYOUT Column

Blur: make secret/redact?
Font: see above
For numeric only: decimal points (how many digits after comma), display comma, negative value in parenthesis, scale (see above)

result.csv
Northwind data for testing

result (2).csv
Northwind data

repo: finos/legend-engine


text:
February 7th 2023 - Regulation Innovation SIG Meeting Minutes

Regulation Innovation SIG
Date
February 7 2023 - 12pm EST / 5pm GMT
WebEx info

Meeting link: https://finos.webex.com/finos/j.php?MTID=m6be3cd5cdc56622e15e74fbd30e7253c
Meeting number:  127 759 5114
Password: d9kKJPdX5C9
More ways to join:

Join by video system: Dial 1279881411@finos.webex.com. You can also dial 173.243.2.68 and enter your meeting number.
Join by phone: +1-415-655-0003 US Toll | +44-20319-88141 UK Toll | Access code: 127 759 5114

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact legal@finos.org with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[ ] Convene & roll call (5mins)
[ ] Display FINOS Antitrust Policy summary slide
[ ] Review Meeting Notices (see above)
[ ] Approve past meeting minutes
[ ] Compliant Financial Infrastructure - Introduction and call for requirements - @abdullahgarcia, @AdrianHammond - JPMC and Red Hat
[ ] Confirmation of Payee (CoP) - UK Payments Initiative - Tim Norman - Synechron Payments
[ ] Making the case for a FINOS Payments Special Interest Group - Andrew Duckett and Andy Smith - Discover

Confirmation of Payee
The Payment Systems Regulator (PSR) has confirmed its plans that will see around 400 more financial firms provide the name checking service, Confirmation of Payee (CoP). CoP is a service that checks account and reference details when CHAPS, Faster Payment or standing order is setup. This helps to make sure payment aren’t sent to the wrong account by mistake and will reduce fraud. CoP needs to be developed to provide Customers of the UK payments industry with a way to check the name on the Account Details of the person/entity they wish to pay.
BACKGROUND
CoP is an overlay service that checks that the Account Name provided by a Payer corresponds, to an acceptable level, with the Account Name identified by the CoP Responder with the Account Details the Payer has supplied. CoP aims to give the Customer more control and more certain outcomes when they make a Payment by providing them with assurance regarding the name on the account, they wish to make a Payment to. In particular, it aims to provide consumers with a tool which can be used to avoid making misdirected payments.
OBJECTIVE
One of the key objectives of CoP is to reduce the incidences of misdirected payments; in particular, “Authorized Push Payment” fraud which is of significant detriment and a concern to Customers in the UK payments market. Amongst other things, CoP will seek to substantially reduce the volume of payments that are fraudulently diverted.
Link to PSR ……………… https://www.psr.org.uk/news-and-updates/latest-news/news/psr-directs-400-firms-to-introduce-the-payment-protection-measure-confirmation-of-payee/

[ ] https://github.com/finos/open-regtech-sig/issues/50 by @jgavronsky
[ ] Appetite for increasing SIG meeting cadence to 2x meetings per month
[ ] AOB, Q&A & Adjourn (5mins)

Decisions Made

[ ] ...

Action Items

[ ] ...

WebEx info

Meeting link: https://finos.webex.com/finos/j.php?MTID=m6be3cd5cdc56622e15e74fbd30e7253c
Meeting number:  127 759 5114
Password: d9kKJPdX5C9
More ways to join:

Join by video system: Dial 1279881411@finos.webex.com. You can also dial 173.243.2.68 and enter your meeting number.
Join by phone: +1-415-655-0003 US Toll | +44-20319-88141 UK Toll | Access code: 127 759 5114

Hi All 😄

Hello 👋🏻

:wave: :shipit:

Andy Smith @ Discover

Hello!

Ashley Nelle-Davis @ Data Foundation

Hi 👋🏻 Jonathan Haggarty @ NatWest

¡Hola!

Julia / FINOS

authors: AdrianHammond Julia-Ritter abdullahgarcia andybs anelledavis eddie-knight haggyj mcleo-d yulleyi

repo: finos/open-regtech-sig


text:
closing websockets

I've added support for websocket close messages in line with the new keep-alive thing.

done. toby, we've had a patch for ping and keep alives on ff for websockets yesterday. have you rebased before that ? thanks

oh, forget about it, I misread that you did it over the keep alive. thanks.

yup, i kept his stuff in there :)

Please add yourself in the credits section of README.rst !

hehe ok :)

authors: fiorix gleicon tobypadilla

repo: fiorix/cyclone


text:
set label when repeating the record

Add the possibility to set the label when repeating the record:
$ smt repeat --label=
Imported from Bitbucket issue 180,  created by samarkanov on 05-20-2013 at 18:15, last modified: 06-01-2013 at 12:13

Implemented in r753
Trac comment by apdavison on 06-01-2013 at 12:13

repo: fipymigrate/sumatra


text:
Using Scrollable List TabView inside Nested ScrollView.

Hello There,
I am using this library inside a nestedListView. I am creating a FlexibleSpaceBar() to show image. Also I am using SliverOverlapAbsorber() and SliverOverlapInjector  so that the body of my nested scroll view doesnt hide behind the appbar.
NestedScrollView() body takes a column (Container & ScrollableListTabview()). If i scroll the from container, the flexible appbar collapses but it doesnt collapse when i scroll from the ScrollableListTabview(). I hope you understand the scenario I ll attach the code and image of what i am trying to achieve.
`class ShopScreen extends StatefulWidget {
final Shop shop;
const ShopScreen({
Key key,
@required this.shop,
})  : assert(shop != null),
super(key: key);
@override
_ShopScreenState createState() => _ShopScreenState();
}
class _ShopScreenState extends State {
var top = 0.0;
ScrollController _scrollController;
Color _theme;
Shop _shop;
String _selectedCategory;
@override
void initState() {
super.initState();
_selectedCategory = _shop.categories[0].id;
_theme = Colors.white;
_scrollController = ScrollController()
..addListener(
() => !_isAppBarCollapsed()
? _theme != Colors.white
? setState(
() {
_theme = Colors.white;
print('setState is called');
},
)
: {}
: _theme != Colors.black
? setState(() {
print('setState is called');
_theme = Colors.black;
})
: {},
);
}
bool _isAppBarCollapsed() {
if (_scrollController.hasClients) if (_scrollController.offset >
(170 - kToolbarHeight)) return true;
return false;
}
@override
Widget build(BuildContext context) {
return Scaffold(
body: NestedScrollView(
key: PageStorageKey("NestedScrollView"),
controller: _scrollController,
headerSliverBuilder: (BuildContext context, bool innerBoxIsScrolled) {
return [
SliverOverlapAbsorber(
handle: NestedScrollView.sliverOverlapAbsorberHandleFor(context),
sliver: SliverAppBar(
leading: Center(
child: Container(
padding: EdgeInsets.symmetric(horizontal: 5, vertical: 3),
decoration: BoxDecoration(
color: scaffoldColor,
borderRadius: BorderRadius.circular(5),
),
child: GestureDetector(
onTap: () {
AppRouter.pop(context);
},
child: Icon(
Icons.arrow_back,
color: Colors.black,
),
),
),
),
expandedHeight: 200,
floating: false,
pinned: true,
forceElevated: innerBoxIsScrolled,
actions: [
IconButton(
icon: Icon(Icons.favorite_border_rounded, color: _theme),
onPressed: () {},
)
],
flexibleSpace: FlexibleSpaceBar(
title: Text(
_shop.name,
style: TextStyle(fontSize: 12.0, color: theme),
),
background: Hero(
tag: "shop ${shop.id} image ",
child: Image.network(
imageURL + shop.image,
fit: BoxFit.cover,
color: primaryColor.withOpacity(0.5),
colorBlendMode: BlendMode.darken,
errorBuilder: (ctx, obj, trace) {
return Placeholder();
},
),
)),
),
),
];
},
body: Builder(builder: (ctx) {
return CustomScrollView(
key: PageStorageKey("CustomeScrollView"),
primary: false,
physics: NeverScrollableScrollPhysics(),
slivers: [
SliverOverlapInjector(
handle: NestedScrollView.sliverOverlapAbsorberHandleFor(ctx),
),
SliverToBoxAdapter(
child: Column(
crossAxisAlignment: CrossAxisAlignment.start,
children: [
Padding(
padding: const EdgeInsets.symmetric(
vertical: 8, horizontal: 16),
child: Column(
crossAxisAlignment: CrossAxisAlignment.start,
children: [
Row(
mainAxisAlignment: MainAxisAlignment.spaceBetween,
children: [
Text(shop.address1,
style: TextStyle(fontSize: 16)),
Pill(
text:
"${num.parse(shop.distance).toStringAsFixed(1)} km",
color: primaryColor,
)
],
),
vSpace(5),
Text("Open Now daily time 9:30 am to 11:00 pm"),
],
),
),
Divider(
height: 20,
thickness: 2,
color: lightGreyColor,
),
Container(
height: MediaQuery.of(context).size.height * 0.84,
child: ScrollableListTabView(
tabHeight: 48,
bodyAnimationDuration:
const Duration(milliseconds: 300),
tabAnimationCurve: Curves.easeOut,
tabAnimationDuration: const Duration(milliseconds: 200),
tabs: [
ScrollableListTab(
tab: ListTab(
label: Text('Vegetables'),
activeBackgroundColor: primaryColor),
body: ListView.builder(
shrinkWrap: true,
physics: NeverScrollableScrollPhysics(),
itemCount: 10,
itemBuilder: (, index) => ListTile(
leading: Container(
height: 40,
width: 40,
decoration: BoxDecoration(
shape: BoxShape.circle,
color: Colors.grey),
alignment: Alignment.center,
child: Text(index.toString()),
),
title: Text('Vegetables element $index'),
),
)),
ScrollableListTab(
tab: ListTab(label: Text('Fruits')),
body: ListView.builder(
shrinkWrap: true,
physics: NeverScrollableScrollPhysics(),
itemCount: 10,
itemBuilder: (, index) => ListTile(
leading: Container(
height: 40,
width: 40,
decoration: BoxDecoration(
shape: BoxShape.circle,
color: Colors.grey),
alignment: Alignment.center,
child: Text(index.toString()),
),
title: Text('Fruits element $index'),
),
)),
ScrollableListTab(
tab: ListTab(label: Text('Meat')),
body: ListView.builder(
shrinkWrap: true,
physics: NeverScrollableScrollPhysics(),
itemCount: 10,
itemBuilder: (, index) => ListTile(
leading: Container(
height: 40,
width: 40,
decoration: BoxDecoration(
shape: BoxShape.circle,
color: Colors.grey),
alignment: Alignment.center,
child: Text(index.toString()),
),
title: Text('Meat element $index'),
),
)),
ScrollableListTab(
tab: ListTab(label: Text('Herbs&Spices')),
body: GridView.builder(
shrinkWrap: true,
gridDelegate:
SliverGridDelegateWithFixedCrossAxisCount(
crossAxisCount: 2),
physics: NeverScrollableScrollPhysics(),
itemCount: 10,
itemBuilder: (, index) => Card(
child: Center(
child:
Text('Herbs&Spices element $index')),
),
)),
ScrollableListTab(
tab: ListTab(label: Text('Egg')),
body: GridView.builder(
shrinkWrap: true,
gridDelegate:
SliverGridDelegateWithFixedCrossAxisCount(
crossAxisCount: 2),
physics: NeverScrollableScrollPhysics(),
itemCount: 10,
itemBuilder: (, index) => Card(
child:
Center(child: Text('Egg element $index')),
),
)),
],
),
),
],
),
),
],
);
}),
),
);
}
}
`
and here is what i am trying to make

I apologize for the code formatting. Just copy poste that into your VS Code. I need help ASAP.

Is there any progress on this?
I am trying to accomplish the same thing


text:
Trip data

How can i save trip data?
could you explain ?

I have same problem.
I turn off key, directly shutdown without saving data

Thank you

authors: asilbey sinanhalici


text:
Access to DocumentSnapshots in FirestoreRecyclerAdapter

Hey guys, loving the new Firestore stuff.  Quick question.  I am converting from RTD to this and one thing I did in my previous schema was to not explicitly store the key inside the "object" because I could explicitly use getRef(position) to grab the key to attach to my local POJO.  It seems that this automatic reference is not there to grab the id of the DocumentSnapshot.
I am able to manage it myself by overriding onChildChanged()...
@Override
    public void onChildChanged(ChangeEventType type, DocumentSnapshot snapshot, int newIndex, int oldIndex) {
        super.onChildChanged(type, snapshot, newIndex, oldIndex);
        //....use a local variable to store metadata, document id, etc from the DocumentSnapshot by the newIndex
    }

But I wanted to see if this was the best way to access the document id, metadata, etc, or if there was something else.
Thanks!!!!

Try this: FirestoreRecyclerAdapter.getSnapshots()#getSnapshot(index).

@SUPERCILEX that gives me the Object I passed into the FirestoreRecyclerAdapter, which is built off the document information.  Unless there is a way, in that POJO to tell the class to pull key or metadata and store in the object, it doesn't seem it would work??

I'm not sure I understand, that method gives you a DocumentSnapshot. Is that not what you want?

It appears the way I am using FirestoreRecyclerAdapter it gives me back the Object I instantiate
the adapter with:
inventoryViewAdapter = new FirestoreRecyclerAdapter<Item, InventoryViewAdapter.ViewHolder>(options) {
......

provides the following when I try to get a DocumentSnapshot from getSnapshots:

@SUPERCILEX nevermind, I read your response closer and got it
DocumentSnapshot r = getSnapshots().getSnapshot(position);

works!

Awesome!

@bagintz Looks like we can close this. Thanks @SUPERCILEX

I had been searching the docs for a way to get the document id, I'm glad I finally the answer but this info should be in the docs! Unless I completely missed it, which in that case I apologize.

I agree with @kr05. In my case I wanted to get the snapshot to recognize if it had pending writes before processing:
val r = snapshots.getSnapshot(position)
                if (r.metadata.hasPendingWrites()) {
                    return
                }

Thankfully I stumbled upon this thread after a bit of searching.

authors: SUPERCILEX bagintz brendanosborne kr05 samtstern

repo: firebase/FirebaseUI-Android


text:
FR: Code Examples

Unfortunately the majority of the documentation linked to in the README does not have Golang examples. Trying to do something as simple as read data from a reference isn't very clear, especially for people new to Go.
It would be fantastic and super helpful if you could include some basic examples in this repo.
Thanks!

@timendez we maintain our documentation at https://firebase.google.com/docs, which has plenty of samples. For instance the database documentation can be found at https://firebase.google.com/docs/database/admin/start.
The links in the README file are just for the convenience of the developers working on the SDK. If you want quick access to some samples you can also check under https://github.com/firebase/firebase-admin-go/tree/master/snippets. These are the same examples that appear in our website.

repo: firebase/firebase-admin-go


text:
Cannot find module 'firebase-admin/app' (only on deploy)

[REQUIRED] Step 2: Describe your environment

Operating System version: _____
Firebase SDK version: 8.10.0
Firebase Product: admin
Node.js version: 16
NPM version: 8.1.0

[REQUIRED] Step 3: Describe the problem
Can't deploy Firebase Functions anymore. It all works perfectly on localhost, also deployed same firebase-admin before and out of nowhere got this error.
Steps to reproduce:
Tried to deploy Functions and can't deploy any of them all of a sudden.
Relevant Code:
const { initializeApp, cert } = require('firebase-admin/app')
package.json
{
  "name": "functions",
  "description": "Cloud Functions for Firebase",
  "engines": {
    "node": "16"
  },
  "scripts": {
    "serve": "firebase serve --only functions",
    "shell": "firebase functions:shell",
    "start": "npm run shell",
    "deploy": "firebase deploy --only functions",
    "logs": "firebase functions:log"
  },
  "dependencies": {
    "axios": "^0.27.2",
    "busboy": "^1.6.0",
    "cookie-parser": "^1.4.4",
    "cors": "^2.8.5",
    "dayjs": "^1.11.5",
    "firebase-admin": "8.10.0",
    "firebase-functions": "3.22.0",
    "form-data": "^4.0.0",
    "gotenberg-js-client": "^0.7.3",
    "install": "0.13.0",
    "morgan": "^1.10.0",
    "nodemailer": "^6.4.6",
    "npm": "8.19.2",
    "pdf-lib": "^1.17.1",
    "pdf.js-extract": "^0.1.4",
    "pdfkit": "^0.13.0",
    "webdav": "^3.2.0"
  },
  "private": true
}

i  deploying functions
⚠  functions: package.json indicates an outdated version of firebase-functions.
Please upgrade using npm install --save firebase-functions@latest in your functions directory.
⚠  functions: Please note that there will be breaking changes when you upgrade.
i  functions: ensuring required API cloudfunctions.googleapis.com is enabled...
i  functions: ensuring required API cloudbuild.googleapis.com is enabled...
✔  functions: required API cloudbuild.googleapis.com is enabled
✔  functions: required API cloudfunctions.googleapis.com is enabled
i  functions: preparing functions directory for uploading...
i  functions: packaged functions (93.56 KB) for uploading
i  functions: ensuring required API pubsub.googleapis.com is enabled...
i  functions: ensuring required API cloudscheduler.googleapis.com is enabled...
✔  functions: required API cloudscheduler.googleapis.com is enabled
✔  functions: required API pubsub.googleapis.com is enabled
✔  functions: functions folder uploaded successfully
i  functions: updating Node.js 16 function api(europe-central2)...
i  functions: updating Node.js 16 function sendExpiringCasesToHQ(us-central1)...
i  functions: updating Node.js 16 function sendReportedCasesToHQ(us-central1)...

Functions deploy had errors with the following functions:
        api(europe-central2)
        sendExpiringCasesToHQ(us-central1)
        sendReportedCasesToHQ(us-central1)

Because there were errors creating or updating functions, the following functions were not deleted
To delete these, use firebase functions:delete
i  functions: cleaning up build files...
Error: There was an error deploying functions:
- Error Failed to update function api in region europe-central2
- Error Failed to update function sendExpiringCasesToHQ in region us-central1
- Error Failed to update function sendReportedCasesToHQ in region us-central1

2022-11-02T09:51:33.196805Z ? sendReportedCasesToHQ: Provided module can't be loaded.
2022-11-02T09:51:33.196846Z ? sendReportedCasesToHQ: Did you list all required modules in the package.json dependencies?
2022-11-02T09:51:33.196856Z ? sendReportedCasesToHQ: Detailed stack trace: Error: Cannot find module 'firebase-admin/app'
2022-11-02T09:51:33.196863Z ? sendReportedCasesToHQ: Require stack:
2022-11-02T09:51:33.196908Z ? sendReportedCasesToHQ: - /workspace/initFirebaseAdmin.js
2022-11-02T09:51:33.196915Z ? sendReportedCasesToHQ: - /workspace/index.js
2022-11-02T09:51:33.196923Z ? sendReportedCasesToHQ: - /layers/google.nodejs.functions-framework/functions-framework/node_modules/@google-cloud/functions-framework/build/src/loader.js
2022-11-02T09:51:33.196931Z ? sendReportedCasesToHQ: - /layers/google.nodejs.functions-framework/functions-framework/node_modules/@google-cloud/functions-framework/build/src/main.js
2022-11-02T09:51:33.196941Z ? sendReportedCasesToHQ:     at Function.Module._resolveFilename (node:internal/modules/cjs/loader:956:15)
2022-11-02T09:51:33.196950Z ? sendReportedCasesToHQ:     at Function.Module._load (node:internal/modules/cjs/loader:804:27)
2022-11-02T09:51:33.196958Z ? sendReportedCasesToHQ:     at Module.require (node:internal/modules/cjs/loader:1028:19)
2022-11-02T09:51:33.196966Z ? sendReportedCasesToHQ:     at require (node:internal/modules/cjs/helpers:102:18)
2022-11-02T09:51:33.196979Z ? sendReportedCasesToHQ:     at Object.<anonymous> (/workspace/initFirebaseAdmin.js:1:33)
2022-11-02T09:51:33.196986Z ? sendReportedCasesToHQ:     at Module._compile (node:internal/modules/cjs/loader:1126:14)
2022-11-02T09:51:33.196994Z ? sendReportedCasesToHQ:     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1180:10)
2022-11-02T09:51:33.197Z ? sendReportedCasesToHQ:     at Module.load (node:internal/modules/cjs/loader:1004:32)
2022-11-02T09:51:33.197008Z ? sendReportedCasesToHQ:     at Function.Module._load (node:internal/modules/cjs/loader:839:12)
2022-11-02T09:51:33.197015Z ? sendReportedCasesToHQ:     at Module.require (node:internal/modules/cjs/loader:1028:19)
2022-11-02T09:51:33.197467Z ? sendReportedCasesToHQ: Could not load the function, shutting down.
2022-11-02T09:51:33.355972094Z E sendReportedCasesToHQ: Function cannot be initialized. Error: function terminated. Recommended action: inspect logs for termination reason. Additional troubleshooting documentation can be found at https://cloud.google.com/functions/docs/troubleshooting#logging

Hi @janswist, You are using the modular syntax with a legacy version of firebase-admin. The modular SDK was introduced in v10.0.0. Upgrade your firebase-admin dependency to the latest version should fix this issue. See https://firebase.google.com/docs/admin/migrate-node-v10 for more details.

It's really outrageous that we get such a breaking change, TS is not throwing errors on this and it affects almost every area in the code.
Was this mentioned in any release notes? anywhere? maybe It's just me who can see anything about this?

authors: ariel-dao janswist lahirumaramba

repo: firebase/firebase-admin-node


text:
Realm crashed app in external_commit_helper.cpp @ realm::_impl::ExternalCommitHelper::listen() + 220

Description
I am using Realm using SPM to cache data in my application and recently I saw a crash reported in Crashlytics regarding Realm for a user.
Realm framework version: RealmSwift, 10.42.0
Crash happened on,
Realm notification listener
0  libsystem_kernel.dylib         0x25bc kevent + 8
1  MyApp Prod               0x8f5a68 realm::_impl::ExternalCommitHelper::listen() + 220 (external_commit_helper.cpp:220)
2  MyApp Prod               0x8f5c48 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct>>, realm::_impl::ExternalCommitHelper::ExternalCommitHelper(realm::_impl::RealmCoordinator&, realm::RealmConfig const&)::$_0>>(void*) + 191 (tuple:191)
3  libsystem_pthread.dylib        0x16b8 _pthread_start + 148
4  libsystem_pthread.dylib        0xb88 thread_start + 8

Reproducing the issue
This is very random issue and unable to reproduce on DEV build. It happens randomly on Prod build only.
Firebase SDK Version
10.7.0
Xcode Version
14.2
Installation Method
Swift Package Manager
Firebase Product(s)
Analytics, Authentication, Crashlytics, Remote Config
Targeted Platforms
iOS
Relevant Log Output
# Crashlytics - Stack trace
# Application: com.me.myapp
# Platform: apple
# Version: 1.7.0 (47)
# Issue: 254d5c40b592e7ff4ad783d1ff25b010
# Session: ea254220f1094c409bff8f539a1b5e7e_DNE_0_v2
# Date: Tue Aug 08 2023 17:07:55 GMT+0530 (India Standard Time)

com.apple.uikit.eventfetch-thread
0  libsystem_kernel.dylib         0xc84 mach_msg2_trap + 8
1  libsystem_kernel.dylib         0x13b54 mach_msg2_internal + 80
2  libsystem_kernel.dylib         0x13e2c mach_msg_overwrite + 540
3  libsystem_kernel.dylib         0x11c8 mach_msg + 24
4  CoreFoundation                 0x79024 __CFRunLoopServiceMachPort + 160
5  CoreFoundation                 0x7a250 __CFRunLoopRun + 1208
6  CoreFoundation                 0x7f3ec CFRunLoopRunSpecific + 612
7  Foundation                     0x41fd4 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 212
8  Foundation                     0x41ebc -[NSRunLoop(NSRunLoop) runUntilDate:] + 64
9  UIKitCore                      0x4d03fc -[UIEventFetcher threadMain] + 416
10 Foundation                     0x5b544 __NSThread__start__ + 716
11 libsystem_pthread.dylib        0x16b8 _pthread_start + 148
12 libsystem_pthread.dylib        0xb88 thread_start + 8

com.google.firebase.crashlytics.MachExceptionServer
0  MyApp Prod               0xc0f838 FIRCLSProcessRecordAllThreads + 393 (FIRCLSProcess.c:393)
1  MyApp Prod               0xc0fc18 FIRCLSProcessRecordAllThreads + 424 (FIRCLSProcess.c:424)
2  MyApp Prod               0xc1d6d0 FIRCLSHandler + 34 (FIRCLSHandler.m:34)
3  MyApp Prod               0xc1decc FIRCLSMachExceptionServer + 521 (FIRCLSMachException.c:521)
4  libsystem_pthread.dylib        0x16b8 _pthread_start + 148
5  libsystem_pthread.dylib        0xb88 thread_start + 8

com.apple.CoreMotion.MotionThread
0  libsystem_kernel.dylib         0xc84 mach_msg2_trap + 8
1  libsystem_kernel.dylib         0x13b54 mach_msg2_internal + 80
2  libsystem_kernel.dylib         0x13e2c mach_msg_overwrite + 540
3  libsystem_kernel.dylib         0x11c8 mach_msg + 24
4  CoreFoundation                 0x79024 __CFRunLoopServiceMachPort + 160
5  CoreFoundation                 0x7a250 __CFRunLoopRun + 1208
6  CoreFoundation                 0x7f3ec CFRunLoopRunSpecific + 612
7  CoreFoundation                 0xc1ea4 CFRunLoopRun + 64
8  CoreMotion                     0x13248 CLMotionActivity::isTypeInVehicle(CLMotionActivity::Type) + 23160
9  libsystem_pthread.dylib        0x16b8 _pthread_start + 148
10 libsystem_pthread.dylib        0xb88 thread_start + 8

Thread
0  libsystem_kernel.dylib         0x1558 __psynch_cvwait + 8
1  libsystem_pthread.dylib        0x8078 _pthread_cond_wait + 1232
2  MyApp Prod               0xcc0398 -[SENTExecutor threadLoop] + 2219728
3  Foundation                     0x5b544 __NSThread__start__ + 716
4  libsystem_pthread.dylib        0x16b8 _pthread_start + 148
5  libsystem_pthread.dylib        0xb88 thread_start + 8

com.apple.NSURLConnectionLoader
0  libsystem_kernel.dylib         0xc84 mach_msg2_trap + 8
1  libsystem_kernel.dylib         0x13b54 mach_msg2_internal + 80
2  libsystem_kernel.dylib         0x13e2c mach_msg_overwrite + 540
3  libsystem_kernel.dylib         0x11c8 mach_msg + 24
4  CoreFoundation                 0x79024 __CFRunLoopServiceMachPort + 160
5  CoreFoundation                 0x7a250 __CFRunLoopRun + 1208
6  CoreFoundation                 0x7f3ec CFRunLoopRunSpecific + 612
7  CFNetwork                      0x259580 _CFURLStorageSessionDisableCache + 60900
8  Foundation                     0x5b544 __NSThread__start__ + 716
9  libsystem_pthread.dylib        0x16b8 _pthread_start + 148
10 libsystem_pthread.dylib        0xb88 thread_start + 8

Thread
0  libsystem_kernel.dylib         0x118c __workq_kernreturn + 8
1  libsystem_pthread.dylib        0xe28 _pthread_wqthread + 364
2  libsystem_pthread.dylib        0xb7c start_wqthread + 8

Thread
0  libsystem_kernel.dylib         0x118c __workq_kernreturn + 8
1  libsystem_pthread.dylib        0xe28 _pthread_wqthread + 364
2  libsystem_pthread.dylib        0xb7c start_wqthread + 8

Thread
0  libsystem_kernel.dylib         0x118c __workq_kernreturn + 8
1  libsystem_pthread.dylib        0xe28 _pthread_wqthread + 364
2  libsystem_pthread.dylib        0xb7c start_wqthread + 8

Thread
0  libsystem_kernel.dylib         0x118c __workq_kernreturn + 8
1  libsystem_pthread.dylib        0xe28 _pthread_wqthread + 364
2  libsystem_pthread.dylib        0xb7c start_wqthread + 8

Thread
0  libsystem_kernel.dylib         0x118c __workq_kernreturn + 8
1  libsystem_pthread.dylib        0xe28 _pthread_wqthread + 364
2  libsystem_pthread.dylib        0xb7c start_wqthread + 8

Thread
0  libsystem_kernel.dylib         0x118c __workq_kernreturn + 8
1  libsystem_pthread.dylib        0xe28 _pthread_wqthread + 364
2  libsystem_pthread.dylib        0xb7c start_wqthread + 8

Thread
0  libsystem_kernel.dylib         0x118c __workq_kernreturn + 8
1  libsystem_pthread.dylib        0xe28 _pthread_wqthread + 364
2  libsystem_pthread.dylib        0xb7c start_wqthread + 8

Thread
0  libsystem_kernel.dylib         0x118c __workq_kernreturn + 8
1  libsystem_pthread.dylib        0xe28 _pthread_wqthread + 364
2  libsystem_pthread.dylib        0xb7c start_wqthread + 8

Thread
0  libsystem_kernel.dylib         0x118c __workq_kernreturn + 8
1  libsystem_pthread.dylib        0xe28 _pthread_wqthread + 364
2  libsystem_pthread.dylib        0xb7c start_wqthread + 8

Thread
0  libsystem_kernel.dylib         0x118c __workq_kernreturn + 8
1  libsystem_pthread.dylib        0xe28 _pthread_wqthread + 364
2  libsystem_pthread.dylib        0xb7c start_wqthread + 8

Thread
0  libsystem_kernel.dylib         0x118c __workq_kernreturn + 8
1  libsystem_pthread.dylib        0xe28 _pthread_wqthread + 364
2  libsystem_pthread.dylib        0xb7c start_wqthread + 8

Thread
0  libsystem_pthread.dylib        0xb74 start_wqthread + 254

Realm notification listener
0  libsystem_kernel.dylib         0x25bc kevent + 8
1  MyApp Prod               0x8f5a68 realm::_impl::ExternalCommitHelper::listen() + 220 (external_commit_helper.cpp:220)
2  MyApp Prod               0x8f5c48 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct>>, realm::_impl::ExternalCommitHelper::ExternalCommitHelper(realm::_impl::RealmCoordinator&, realm::RealmConfig const&)::$_0>>(void*) + 191 (tuple:191)
3  libsystem_pthread.dylib        0x16b8 _pthread_start + 148
4  libsystem_pthread.dylib        0xb88 thread_start + 8

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

{
      "identity" : "realm-core",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/realm/realm-core",
      "state" : {
        "revision" : "3c4b86da569368c4ee5ccca2a112d511cc6fa936",
        "version" : "12.11.0"
      }
    },
    {
      "identity" : "realm-swift",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/realm/realm-swift.git",
      "state" : {
        "revision" : "dc1672b3011eb992ce95db4feec83cd897626a16",
        "version" : "10.32.1"
      }
    }

Hi @paresh-thakor, per checking your stack trace, it looks like there's no issue related to Firebase SDK. With this, you may try to file a ticket through Realm repo to investigate the issue. Thanks.

authors: paresh-thakor rizafran

repo: firebase/firebase-ios-sdk


text:
let response = try await model.generateContent(prompt) no error and no response

Description
let response = try await model.generateContent(prompt)
no error and no response
infinetly
Reproducing the issue
Code from the sample
let response = try await model.generateContent(prompt)
if let text = response.text {
print(text)
}
Firebase SDK Version
11.0.0
Xcode Version
15.3
Installation Method
Swift Package Manager
Firebase Product(s)
VertexAI
Targeted Platforms
iOS
Relevant Log Output
No logs

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

Just need to enable appCheck


text:
Bug in App Check debug provider

Step 1: Describe your environment

Xcode version: 13.0 (13A233)
Firebase SDK version: 8.8.1
Installation method: Swift Package Manager
Firebase Component: Auth

Steps to reproduce:

Enable App Check for Storage in the Firebase console by going to Project Settings -> App Check -> Storage and clicking on Enforce.
Wait 15 minutes or so for your changes to take effect.
Somewhere in your project, set up the Debug Provider Factory.
Generate a CI Debug token by going to Project Settings -> App Check -> Manage debug tokens. (Don't use a local token generated by Simulator, create a new one in the Firebase Console.)
Put the token in your app environment by editing the scheme and adding a value for the APP_CHECK_DEBUG_TOKEN key.
Run the app, and try to access a file from Firebase Storage in your project.

What happened? How can we make the problem occur?
Access to storage is denied (files don't load), and an error is logged in the console:
ResponseBody={
  "error": {
    "code": 401,
    "message": "Firebase App Check token is invalid."
  }
}

Relevant Code:
App Check provider setup:
#if targetEnvironment(simulator)
let providerFactoryDebug = AppCheckDebugProviderFactory()
AppCheck.setAppCheckProviderFactory(providerFactoryDebug)
#else
if ProcessInfo.processInfo.environment["ui_test"] == "true" {
    let providerFactoryDebug = AppCheckDebugProviderFactory()
    AppCheck.setAppCheckProviderFactory(providerFactoryDebug)
} else {
    let providerFactory = MyAppCheckProviderFactory()
    AppCheck.setAppCheckProviderFactory(providerFactory)
}
#endif

@maksymmalyhin changing the name of the environment variable fixed the issue. Thanks so much for your help!
I think the docs are clear, I just wasn't reading over them carefully. I think it was the fifth step in the instructions (passing in APP_CHECK_DEBUG_TOKEN=$(APP_CHECK_DEBUG_TOKEN_FROM_CI) to a CI build) that made me think that the Firebase framework was looking for APP_CHECK_DEBUG_TOKEN instead of FIRAAppCheckDebugToken.


text:
kFirebaseInstallationsErrorDomain missing NS_SWIFT_NAME

https://github.com/firebase/firebase-ios-sdk/blob/bdac2b87f6d6e604deae914a970a75136b3a62b5/FirebaseInstallations/Source/Library/Public/FirebaseInstallations/FIRInstallationsErrors.h#L19
This is missing the NS_SWIFT_NAME, unfortunately fixing it is a breaking change. It should be named InstallationsErrorDomain.

Merged #9395 into v9


text:
Create an API review and Changelog for FirebaseFunctions breaking changes

Removed global symbols
Removed FirebaseFunctions.h
Dropped CocoaPods library support (Firebase-wide)
Dropped support from import Firebase and import Firebase.h

Deprecation merged for 8.15.0.
Still need removal for 9.0.0


text:
[Infra] Add workflow for detecting unlinked Firestore symbols

Context

Creates a workflow job to test for regressions within the FirebaseFirestore.xcframework where an unreferenced symbol is introduced.
Tried writing in Swift but running xcodebuild via Process became a flaky headache.
Unblocks #10896

Testing Plan

As long as #10896 isn't merged, Firestore contains unlinked symbols. This workflow should pick them up and cause a failure. Once this PR is merged, I will rebase #10896 on top of master and re-run CI. #10896 should fix the failures.
There are some additional edge cases that I will introduce in a separate PR for the purpose of testing against this workflow.

#no-changelog

Thank you @andrewheard! I gave that style guide a scan– great doc that I didn't know existed! I pushed a commit to pipe the xcodebuild logs to xcpretty. CI shows that the script is expectedly failing, but the xcodebuild logs add too much noise. See the bottom of this successfully failing run: https://pipelines.actions.githubusercontent.com/serviceHosts/a4b318a7-37c3-4d67-809f-340c6f31caac/_apis/pipelines/1/runs/115852/signedlogcontent/38?urlExpires=2023-03-07T23%3A24%3A31.9554175Z&urlSigningMethod=HMACV1&urlSignature=Gg7NOvOC0jmijbMKcr1bENCjyl8Bcc7ISlfnFELrfBk%3D

When unlinked symbols are detected, you'll see output like this that lists the unlinked symbols:
Failure: Unlinked Objective-C symbols have been detected:
177a178,179
> +[FSTFirestoreComponent componentsToRegister]
> +[FSTFirestoreComponent load]
765a768,776
> -[FSTFirestoreComponent .cxx_destruct]
> -[FSTFirestoreComponent appWillBeDeleted:]
> -[FSTFirestoreComponent app]
> -[FSTFirestoreComponent firestoreForDatabase:]
> -[FSTFirestoreComponent initWithApp:]
> -[FSTFirestoreComponent instances]
> -[FSTFirestoreComponent keyForDatabase:]
> -[FSTFirestoreComponent removeInstanceWithDatabase:]
> -[FSTFirestoreComponent setInstances:]
1115a1127
> +[FSTFirestoreComponent componentsToRegister]

When no unlinked symbols are detected, the script will output:
Success: No unlinked Objective-C symbols have been detected.


text:
[Infra] Quick fix for NOTICES generation

#no-changelog

Do you understand the CI failure?

Yep, thanks @paulb777. Hmm, I'll have to special case the beta pods.