Fatal error: 'try!' expression unexpectedly raised an error: Error Domain=io.realm Code=9 "mmap() failed: Cannot allocate memory size: 55672832 offset: 335544320"

How frequently does the bug occur?
Sometimes
Description
We are on version 10.26.0 and in some devices we started to get an increasing number of this error. It seems to be a reoccurring issue in some Realm versions for quite some time now. The exact error is the following:
Fatal error: 'try!' expression unexpectedly raised an error: Error Domain=io.realm Code=9 "mmap() failed: Cannot allocate memory size: 55672832 offset: 335544320"
Any ideas why is it happening and how to solve it?
Stacktrace & log output
Fatal Exception: RLMException
0  CoreFoundation                 0x99d78 __exceptionPreprocess
1  libobjc.A.dylib                0x16734 objc_exception_throw
2  CarmaGo                        0x5fa9a4 -[RLMRealm refresh] + 918 (RLMRealm.mm:918)
3  CarmaGo                        0x696f3c Realm.refresh() + 903 (Realm.swift:903)
4  CarmaGo                        0x130068 closure #1 in MapViewModel.setupResultPublisher() + 272 (MapViewModel.swift:272)
5  Combine                        0xb4b0 Subscribers.Sink.receive(_:)
6  Combine                        0xada8 protocol witness for Subscriber.receive(_:) in conformance Subscribers.Sink<A, B>
7  Combine                        0x129fc closure #1 in Publishers.ReceiveOn.Inner.receive(_:)
8  libswiftDispatch.dylib         0x1c04 thunk for @escaping @callee_guaranteed () -> ()
9  libdispatch.dylib              0x1e68 _dispatch_call_block_and_release
10 libdispatch.dylib              0x3a2c _dispatch_client_callout
11 libdispatch.dylib              0xb124 _dispatch_lane_serial_drain
12 libdispatch.dylib              0xbc80 _dispatch_lane_invoke
13 libdispatch.dylib              0x16500 _dispatch_workloop_worker_thread
14 libsystem_pthread.dylib        0x10bc _pthread_wqthread
15 libsystem_pthread.dylib        0xe5c start_wqthread

Can you reproduce the bug?
Not yet
Reproduction Steps
No response
Version
10.26.0
What SDK flavour are you using?
Local Database only
Are you using encryption?
No, not using encryption
Platform OS and version(s)
iOS 15.0
Build environment
No response

Hi @theoks
could you please share more info?
Your approach on threading for Realm? The code could help.
Do you retain any references to the Realm or Realm Objects?
Could you check for me a memory consumption?

@pavel-ship-it
Thanks for responding.
I will share a detailed stack, a screenshot of the memory consumption (which as you can see doesn't increase) and a screenshot of the memory references of all Realms and Realm objects and results.
However I'd like to highlight that this specific issue started appearing after we started using version 10.26.0 and without making any changes in our codebase.
Before upgrading to 10.27.0 we moved almost all calls (except some that run during app launch) to the new writeAsync functionality.
Both in version 10.26.0 (without having implemented the writeAsync) and in 10.27.0 (where we implemented writeAsync) we started seeing this specific crash.
The way we retrieve a new Realm is through a computed variable like this:
public var realm: Realm {
	try! Realm(configuration: configuration())
}

This way we are able to get every time a new Realm, which is created in the current queue (99% of the time this is a serial background queue with priority set to userInitiated, the other 1% is done on the main queue).
We never store a Realm in a property, we usually use them in a transient manner within function bodies, or other short scopes (so they are deallocated as soon as they go out of scope). The only long-lived Realm objects are in some Combine pipelines which we create by using the collectionPublisher property, however these pipelines are properly deallocated either manually or by being stored in AnyCancellable sets (which are deallocated when their top-level objects get deallocated themselves).
Here is a detailed stack trace:
Thread 1#0	0x0000000199248708 in objc_exception_throw ()
#1	0x0000000101d327d8 in RLMSetErrorOrThrow(NSError*, NSError* __autoreleasing*) at /Users/theo/Library/Developer/Xcode/DerivedData/CarmaGo-fbmtnxdkyuhmabemakhnmnakbvbt/SourcePackages/checkouts/realm-swift/Realm/RLMUtil.mm:415
#2	0x0000000101cb132c in RLMRealmTranslateException(NSError* __autoreleasing*) at /Users/theo/Library/Developer/Xcode/DerivedData/CarmaGo-fbmtnxdkyuhmabemakhnmnakbvbt/SourcePackages/checkouts/realm-swift/Realm/RLMRealm.mm:389
#3	0x0000000101cb50e4 in -[RLMRealm commitAsyncWriteTransaction:allowGrouping:] at /Users/theo/Library/Developer/Xcode/DerivedData/CarmaGo-fbmtnxdkyuhmabemakhnmnakbvbt/SourcePackages/checkouts/realm-swift/Realm/RLMRealm.mm:799
#4	0x0000000101e04984 in Realm.commitAsyncWrite(allowGrouping:_:) at /Users/theo/Library/Developer/Xcode/DerivedData/CarmaGo-fbmtnxdkyuhmabemakhnmnakbvbt/SourcePackages/checkouts/realm-swift/RealmSwift/Realm.swift:449
#5	0x0000000101e0472c in closure #1 in Realm.writeAsync(_:onComplete:) at /Users/theo/Library/Developer/Xcode/DerivedData/CarmaGo-fbmtnxdkyuhmabemakhnmnakbvbt/SourcePackages/checkouts/realm-swift/RealmSwift/Realm.swift:395
#6	0x0000000101e04b28 in closure #1 in Realm.beginAsyncWrite(_:) at /Users/theo/Library/Developer/Xcode/DerivedData/CarmaGo-fbmtnxdkyuhmabemakhnmnakbvbt/SourcePackages/checkouts/realm-swift/RealmSwift/Realm.swift:422
#7	0x0000000101d3d828 in thunk for @escaping @callee_guaranteed () -> () ()
#8	0x0000000101cc3be4 in void realm::util::UniqueFunction<void ()>::call_regular_void<void () block_pointer __strong>(std::__1::integral_constant<bool, true>, void () block_pointer __strong&) at /Users/theo/Library/Developer/Xcode/DerivedData/CarmaGo-fbmtnxdkyuhmabemakhnmnakbvbt/SourcePackages/checkouts/realm-core/src/realm/util/functional.hpp:148
#9	0x0000000101cc3b48 in realm::util::UniqueFunction<void ()>::SpecificImpl<void () block_pointer __strong>::call() at /Users/theo/Library/Developer/Xcode/DerivedData/CarmaGo-fbmtnxdkyuhmabemakhnmnakbvbt/SourcePackages/checkouts/realm-core/src/realm/util/functional.hpp:168
#10	0x0000000101f2e774 in realm::util::UniqueFunction<void ()>::operator()() const at /Users/theo/Library/Developer/Xcode/DerivedData/CarmaGo-fbmtnxdkyuhmabemakhnmnakbvbt/SourcePackages/checkouts/realm-core/src/realm/util/functional.hpp:94
#11	0x00000001022593dc in realm::Realm::run_writes() at /Users/theo/Library/Developer/Xcode/DerivedData/CarmaGo-fbmtnxdkyuhmabemakhnmnakbvbt/SourcePackages/checkouts/realm-core/src/realm/object-store/shared_realm.cpp:759
#12	0x0000000102147660 in realm::Realm::Internal::run_writes(realm::Realm&) at /Users/theo/Library/Developer/Xcode/DerivedData/CarmaGo-fbmtnxdkyuhmabemakhnmnakbvbt/SourcePackages/checkouts/realm-core/src/realm/object-store/shared_realm.hpp:468
#13	0x000000010214763c in realm::_impl::RealmCoordinator::async_request_write_mutex(realm::Realm&)::$_6::operator()()::'lambda'()::operator()() const at /Users/theo/Library/Developer/Xcode/DerivedData/CarmaGo-fbmtnxdkyuhmabemakhnmnakbvbt/SourcePackages/checkouts/realm-core/src/realm/object-store/impl/realm_coordinator.cpp:1288
#14	0x0000000102147614 in void realm::util::UniqueFunction<void ()>::call_regular_void<realm::_impl::RealmCoordinator::async_request_write_mutex(realm::Realm&)::$_6::operator()()::'lambda'()>(std::__1::integral_constant<bool, true>, realm::_impl::RealmCoordinator::async_request_write_mutex(realm::Realm&)::$_6::operator()()::'lambda'()&) at /Users/theo/Library/Developer/Xcode/DerivedData/CarmaGo-fbmtnxdkyuhmabemakhnmnakbvbt/SourcePackages/checkouts/realm-core/src/realm/util/functional.hpp:148
#15	0x0000000102147574 in realm::util::UniqueFunction<void ()>::SpecificImpl<realm::_impl::RealmCoordinator::async_request_write_mutex(realm::Realm&)::$_6::operator()()::'lambda'()>::call() at /Users/theo/Library/Developer/Xcode/DerivedData/CarmaGo-fbmtnxdkyuhmabemakhnmnakbvbt/SourcePackages/checkouts/realm-core/src/realm/util/functional.hpp:168
#16	0x0000000101f2e774 in realm::util::UniqueFunction<void ()>::operator()() const at /Users/theo/Library/Developer/Xcode/DerivedData/CarmaGo-fbmtnxdkyuhmabemakhnmnakbvbt/SourcePackages/checkouts/realm-core/src/realm/util/functional.hpp:94
#17	0x0000000102377b40 in realm::util::InvocationQueue::invoke_all() at /Users/theo/Library/Developer/Xcode/DerivedData/CarmaGo-fbmtnxdkyuhmabemakhnmnakbvbt/SourcePackages/checkouts/realm-core/src/realm/object-store/util/scheduler.cpp:101
#18	0x0000000102378658 in realm::util::RunLoopScheduler::RunLoopScheduler(__CFRunLoop*)::$_0::operator()(void*) const at /Users/theo/Library/Developer/Xcode/DerivedData/CarmaGo-fbmtnxdkyuhmabemakhnmnakbvbt/SourcePackages/checkouts/realm-core/src/realm/object-store/util/apple/scheduler.hpp:65
#19	0x0000000102378630 in realm::util::RunLoopScheduler::RunLoopScheduler(__CFRunLoop*)::$_0::__invoke(void*) at /Users/theo/Library/Developer/Xcode/DerivedData/CarmaGo-fbmtnxdkyuhmabemakhnmnakbvbt/SourcePackages/checkouts/realm-core/src/realm/object-store/util/apple/scheduler.hpp:64
#20	0x0000000180570414 in __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ ()
#21	0x00000001805811a0 in __CFRunLoopDoSource0 ()
#22	0x00000001804ba694 in __CFRunLoopDoSources0 ()
#23	0x00000001804c005c in __CFRunLoopRun ()
#24	0x00000001804d3bc8 in CFRunLoopRunSpecific ()
#25	0x000000019c607374 in GSEventRunModal ()
#26	0x0000000182e43648 in -[UIApplication _run] ()
#27	0x0000000182bc4d90 in UIApplicationMain ()
#28	0x0000000188325f24 in closure #1 in KitRendererCommon(_:) ()
#29	0x0000000188253e08 in runApp<τ_0_0>(_:) ()
#30	0x00000001882350f4 in static App.main() ()
#31	0x0000000100c05450 in static GoApp.$main() at /Users/theo/Projects/carmaproject/CarmaGo/CarmaGo/App/GoApp.swift:10
#32	0x0000000100c056a4 in main ()
#33	0x000000010b331ce4 in start ()

Here is the memory consumption:

Here is the memory graph for all Realm objects:

Since this issue started after a specific update, and it impacts almost all our users, any assistance will be greatly appreciated. Please feel free to ask for further input if needed.

@pavel-ship-it
Is there a possibility that there is something else except memory? If you take a look at the screenshot I attach, the memory is not increasing, neither is it too much, however I still got the allocation crash.
I also ran a session in the Leaks instrument and there aren't any concerning leaks, except the random small ones coming from some native libraries which you normally get sometimes. If a Leaks instrument recording would be helpful to see by yourselves what's going on in memory, I'd probably be able to send over one.

@pavel-ship-it I am facing the same issue and I found out that this weakRealmNotifier reference is building up, leading to realm file getting bigger and bigger and eventually the app crashes

@pavel-ship-it @tgoyne @ericjordanmossman
We managed to limit the issue a lot. It was unrelated to writeAsync (@ericjordanmossman you mentioned our issue in #7817, but it wasn't the writeAsync after all). The main problem was that we were creating a Combine collectionPublisher and then we were adding a subscribe(on:) publisher to kick it off on a background thread. This ultimately led to an enormous count of WeakRealmNotifier.notify() instances to be created (check the screenshots above), which apparently (though we are not 100% sure) led to a mmap()exception.
However, we still get this kind of crash with the same stacktrace.
Our app stores and modifies objects really quickly (we get live updates from the sensors and we need to provide immediate feedback to the user and store the state at the same time), and after some thousand objects (which probably translate to tens of thousands transactions) we still get the same error. However the object count of WeakRealmNotifier.notify() and the app size stays within normal levels (no more than 2-3 MB, the most we've seen is 5MB). The open Realms are around 3 each time and we have around 10 stored instances of collections and objects that are accessed through the main thread.
It's been almost a month since we first mentioned this issue, and it still affects almost 100% of our users, although more sparingly than before. However, it is still a very bad UX to have the app crash two or three times within 6-7 hours of use because of this Realm bug.
Is it possible that you take a look and help us figure it out? It seems to be a common issue across many Realm versions.

@tgoyne @pavel-ship-it I just saw that the 12.4.0 version of realm core contains a possible fix for this case.
Do you know if it be included in the next release of the swift version?

facing exact same issue, tried on realm swift versions tags 10.39.1, 10.28.1,
no more resources load into realm database after ~2.7 GB loaded.
getting again and again, autorelasepool did not fix the issue, pls help
Fatal error: 'try!' expression unexpectedly raised an error: Error Domain=io.realm Code=9 "mmap() failed: Cannot allocate memory size: 55541760 offset:<PHONE_NUMBER>" UserInfo={NSLocalizedDescription=mmap() failed: Cannot allocate memory size: 55541760 offset:<PHONE_NUMBER>, Error Code=9}
Terminating app due to uncaught exception 'RLMException', reason: 'Attempted to insert null into non-nullable column
Exception backtrace:

I got the same issue after I update realm from 10.13 to 10.43.

facing exact same issue, tried on realm swift versions tags 10.39.1, 10.28.1,面对完全相同的问题，尝试过 Realm Swift 版本标签 10.39.1、10.28.1、
no more resources load into realm database after ~2.7 GB loaded.加载 ~2.7 GB 后，不再有资源加载到 Realm 数据库中。
getting again and again, autorelasepool did not fix the issue, pls help一次又一次，AutoRelasepool 没有解决问题，请帮忙
Fatal error: 'try!' expression unexpectedly raised an error: Error Domain=io.realm Code=9 "mmap() failed: Cannot allocate memory size: 55541760 offset:<PHONE_NUMBER>" UserInfo={NSLocalizedDescription=mmap() failed: Cannot allocate memory size: 55541760 offset:<PHONE_NUMBER>, Error Code=9}致命错误：“try！”表达式意外引发错误：错误 Domain=io.realm Code=9 “mmap（） 失败：无法分配内存大小：55541760偏移量：2617245696” UserInfo={NSLocalizedDescription=mmap（） 失败：无法分配内存大小：55541760偏移量：2617245696，错误代码=9}
Terminating app due to uncaught exception 'RLMException', reason: 'Attempted to insert null into non-nullable column由于未捕获的异常“RLMException”而终止应用，原因：“尝试将 null 插入不可为 null 的列 Exception backtrace: 异常回溯：

Did you fix the problem?


Update Dateline Fix LIS Testcase files

Updated the Issue #117, Crossing the International Dateline,
testcase in LIS to account for open water surface in addition
to Noah LSM land surface type.
Updated the ldt.config and lis.config files in LIS directory:
lis/testcases/domains/latlon_idlcross
New tarball input and output testcase files can be found here:
/discover/nobackup/projects/lis/Projects/LDT/LISF_Testcases/Cross_Dateline/Testcase
Input LDT testcase tarball:  LDT_Test/testcase_ldt_input.tar.gz
Input LIS testcase tarball:  LIS_Test/testcase_lis_input.tar.gz
Output LIS testcase tarball:  LIS_Test/testcase_lis_output.tar.gz

Ok, thanks. I updated the testcase tarball files for inputs to LIS.
Please try again. Thank you!

IGNORE PREVIOUS REMARK
I found the ctl files in /discover/nobackup/projects/lis/Projects/LDT/LISF_Testcases/Cross_Dateline/Testcase/LIS_Test.  I'll use them now.

Yes, the control files are found in the new committed LIS testcase:
https://github.com/karsenau/LISF/tree/fix/dateline/lis/testcases/domains/latlon_idlcross
as per Jim's LIS testcase instructions.

Results look good.
I will confer with Jim about how to handle adding the testcases to his suite.  I think he prefers this to happen before we commit the latest changes to master; but I understand this is a high priority capability to polish off.

Jim just put the test case tarfiles on his backlog, and gave his consent to merging this pull request now.  I will do so.


Too old content for Node Authorization should be removed or update

This is a Feature Request

What would you like to be added

2 sections below may include too old content, mentioning v1.6 ~ v1.8. They should be removed or updated.

Upgrades from previous versions using RBAC
RBAC Node Permissions

https://kubernetes.io/docs/reference/access-authn-authz/node/
Why is this needed
Too old content may not be needed or should not be included in the latest document.
Comments

/language en
/kind cleanup

/triage accepted
/sig auth
I think

/triage accepted
/sig auth
I think

/assign

/assign

Rather than remove those sections, let's update them to clarify why they remain valid.

/kind documentation

/remove-lifecycle rotten

/remove-kind feature
/kind bug
/priority backlog

/remove-lifecycle rotten

/lifecycle frozen
The update needed is to delete the page content from https://kubernetes.io/docs/reference/access-authn-authz/node/#upgrades-from-previous-versions-using-rbac onwards (including that heading)
/help


The version in generated appcast-*.rss does not match the defined app.version

Describe the bug
When running gradlew -q printConveyorConfig, the output is:
.....
app.version = 1.0.0
.....

However, the generated appcast-amd64.rss file
<rss xmlns:sparkle="http://www.andymatuschak.org/xml-namespaces/sparkle" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
    <channel>
        <title>Changelog</title>
        <link>http://localhost:3000/appcast-amd64.rss</link>
        <description>Most recent changes with links to updates.</description>
        <language>en</language>
        <item>
            <title>Version <IP_ADDRESS></title>
            <link>http://localhost:3000/</link>
            <sparkle:version><IP_ADDRESS></sparkle:version>
            <description>
                <![CDATA[ New release: version <IP_ADDRESS> ]]>
            </description>
            ........
        </item>
    </channel>
</rss>

The version in the appcast-amd64.rss is <IP_ADDRESS>, which does not match the defined app.version of 1.0.0.
Additional context

OS: MacOS 14.5 Intel
Version 14.3

That's intentional. The last number comes from the app.revision key, which is intended to be used if you change the packaging configuration but not the underlying code. The idea is that the revision number can be hidden in the app UI. same thing is done on Windows. It's useful when packaging other people's software for example, as the 4th digit normally isn't used.

However, Sparkle will use this combined version number and display it in the upgrade UI, which I am concerned might confuse users. Users generally do not care about the revision number.

The fix for this should go out in the next minor release, thanks for the suggestion!


Can't claim rewards (have .02 sol in wallet)

Describe the bug
I am unable to claim the rewards from my gateway.  Any time I hit the claim rewards button I get the following message:  "Reward Redemption failed.  Please try again later.  (request failed with status code 404).  I've tried many times over the past two weeks with the same result.  I hadn't claimed rewards in months, so I'm not sure when this might have started.
To Reproduce
Steps to reproduce the behavior:

Go to Collectibles
Click on Claim Rewards > Add all to account
Scroll down to ......  No need to scroll error pops up here
See error:   Reward Redemption failed.  Please try again later.  (request failed with status code 404)

Expected behavior
I expected the rewards to be moved into my wallet
Screenshots
For some reason, when I take a screenshot it shows up as all black (assuming security feature)
Smartphone (please complete the following information):

Device: Pixel 7 Pro
OS: [e.g. iOS8.1]
App Version:  2.6.4<PHONE_NUMBER>) -- I do see an update announcement within the app, but see no update option in play store
Additional context*
Add any other context about the problem here.

Going to settings , App, helium wallet then clear cache resolved my issue

This should be fixed in later releases. 2.7.0+


FutureWarning: You are using torch.load

C:\Users\Qatrol\Downloads\game\open-oasis\generate.py:17: FutureWarning: You are using torch.load with weights_only=False (the current default value), which uses the default pickle module implicitly. It is possible to construct malicious pickle data which will execute arbitrary code during unpickling (See https://github.com/pytorch/pytorch/blob/main/SECURITY.md#untrusted-models for more details). In a future release, the default value for weights_only will be flipped to True. This limits the functions that could be executed during unpickling. Arbitrary objects will no longer be allowed to be loaded via this mode unless they are explicitly allowlisted by the user via torch.serialization.add_safe_globals. We recommend you start setting weights_only=True for any use case where you don't have full control of the loaded file. Please open an issue on GitHub for any issues related to this experimental feature.
ckpt = torch.load("oasis500m.pt")
C:\Users\Qatrol\Downloads\game\open-oasis\generate.py:23: FutureWarning: You are using torch.load with weights_only=False (the current default value), which uses the default pickle module implicitly. It is possible to construct malicious pickle data which will execute arbitrary code during unpickling (See https://github.com/pytorch/pytorch/blob/main/SECURITY.md#untrusted-models for more details). In a future release, the default value for weights_only will be flipped to True. This limits the functions that could be executed during unpickling. Arbitrary objects will no longer be allowed to be loaded via this mode unless they are explicitly allowlisted by the user via torch.serialization.add_safe_globals. We recommend you start setting weights_only=True for any use case where you don't have full control of the loaded file. Please open an issue on GitHub for any issues related to this experimental feature.
vae_ckpt = torch.load("vit-l-20.pt")
C:\Users\Qatrol\Downloads\game\open-oasis\generate.py:42: FutureWarning: You are using torch.load with weights_only=False (the current default value), which uses the default pickle module implicitly. It is possible to construct malicious pickle data which will execute arbitrary code during unpickling (See https://github.com/pytorch/pytorch/blob/main/SECURITY.md#untrusted-models for more details). In a future release, the default value for weights_only will be flipped to True. This limits the functions that could be executed during unpickling. Arbitrary objects will no longer be allowed to be loaded via this mode unless they are explicitly allowlisted by the user via torch.serialization.add_safe_globals. We recommend you start setting weights_only=True for any use case where you don't have full control of the loaded file. Please open an issue on GitHub for any issues related to this experimental feature.
actions = one_hot_actions(torch.load(actions_path))
0%|                                                                                | 0/31 [00:00<?, ?it/s]

don't loading

What gpu are you using?

What gpu are you using?

1050ti

1050 can't run this, anything below a 3080 is pretty much a no go looking at the render times. the bare minimum for the script to work out of the pack is about 11 gigabytes of vram or so


API Groups page not showing groups properly in the DevPortal

Description
We have noticed some issues on the developer portal API Groups page on the latest U2 level (122) of APIM 4.1.0. Please refer to the below attached image.

Steps to Reproduce
Follow the [1] and create API groups.
[1] - https://apim.docs.wso2.com/en/3.0.0/learn/consume-api/customizations/customizing-the-developer-portal/customize-api-listing/categorizing-and-grouping-apis/
Affected Component
APIM
Version
4.1.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response

Fixed with https://github.com/wso2/apim-apps/pull/527


Better user controls

From PyWeek feedback
Coiuld not find a way to quit the game from the 'map'. Had to start a level and let me kill to find the quit button. Also I do not like that the game goes to full screen without warning.
Thanks for your time.

From PyWeek feedback
I had to remove all sound to be able to run it.
You can only access to the main menu if you are in a level, and go to map and main menu takes you to the map.
The game is fun, I didn't get the theme implementation.

95a1ac15d2895cc8fab3db05084ddab5ca3f5fed
Game starting in full screen will not be fixed as I do not consider it an issue
Sound bug cannot be investigated without further information. Suspect user did not have necessary codecs


Refactored require paths for plugin compatibility

As mentioned within https://github.com/guardian/scribe/issues/311 requiring immutable.js with:
'immutable/dist/immutable'
breaks the https://github.com/guardian/scribe-plugin-noting test suite. I've re-jigged the require paths so that this should no longer be a problem.  As I don't work with other plugins would be good to know that this doesn't break anything else @robinedman @theefer @rrees? Test suite run's fine on my local.

At the moment none of the plugins are depending on immutable except the core code so it should be fine.

Did you check that you can still run the release scripts after this change?

Also I'm confused why we can't use the paths config to point to the right place, which I thought was what you did in your fix.

Yeah, I changed the paths config in test/app/index.html within the noting plugin.  I added the fix here as I assumed that https://github.com/guardian/scribe/issues/311 would apply to other plugins.

Ah OK I understand. So it sounds like you've fixed the problem, which only existed in the noting plugin? @rrees said no other plugins depend on immutable, so there shouldn't be any other problem?
It would seem inconsistent to use a path dependency for immutable-js when the other Scribe dependencies (lodash-amd, and html-janitor here which I think is for a plugin) use a configured path. In the current state of things, using Scribe implies configuring the paths for any libraries it uses. Given the mess required to get things hooked up (dist vs source, installed vs link, etc), it may be best to stick to that for now.
That said, in the future I'd strongly suggest looking into a better way to manage dependencies. jspm is working amazingly well for both media-service and workflow :-)

Well, any plugin which depends on scribe#master will have this issue util we update thetest/app/index.html file within that repo.  From a brief look there's these two:

https://github.com/guardian/scribe-plugin-curly-quotes
https://github.com/guardian/scribe-plugin-smart-lists

but it also means that any plugin we want to update to use scribe's master branch will suffer the same problem and it's not immediately apparent what breaks the test suite from the debug output.
As far as I can see this causes no issues with scribe but will prevent further issues down the line which for me is a win, not sure how @robinedman @rrees and @hmgibson23 feel about this.
In terms of the future, it seems pretty trivial to ship the compiled source unless I'm missing something?

@theefer add an issue for looking at the conversion for JSPM, its where we want to go after all

Also we do ship compiled code. It's just depending on scribe#master that doesn't. My bad.

In terms of the future, it seems pretty trivial to ship the compiled source unless I'm missing something?

Bundling a package with its dependencies causes a lot of issues:

It's impossible to dedupe anything compiled in the bundle (e.g. immutable-js compiled in Scribe, and Composer also depending on Scribe and immutable-js -- how to avoid two copies?). That means it appears twice in the payload (performance penalty), conflicting versions may be required in the dependency graph (but we have no way to tell or get warned, because it's just a part of the bundle blob), and the AMD loader can get rather confused by it getting re-defined. Singleton behaviour may also be broken.
It's very hard to do any "tree shaking" to remove things that aren't needed
If the only way to get the package in is in its bundled form, that will likely make it hard to dev against, say using link or a source copy instead of the package. We've had this problem with Composer/Scribe, it's really hard to get Composer setup to run against a bower link version of Scribe.

So we could compile Scribe but exclude the dependencies (lodash, immutable), but then it's exactly the same problem of configuring where to load them from.
Really the way to avoid problems is to delay the bundling until as late as possible; ideally as part of the app bundling itself. In other words, we want the full dependency graph unfolded, from the app down to its dependencies and their dependencies (rather than any intermediate bundle). As a bonus, that means we're running everything from source (even better than source maps!), which helps development.
In practice, it's really, really hard to do this with Bower, because there is so much fiddly manual setup (exactly the things you're highlighting here, with so many paths having to be set everywhere).
NPM natively doesn't really help much either, because it's duplicating libraries at all levels, which is fine (ish) on the server-side, but we eventually need to flatten all versions (as Bower does) as we said we can't really have duplicates on the frontend. Also, NPM/browserify is very centered around CommonJS, and even though there are transforms and things you can inject to get AMD support (not sure about globals), it remains difficult to put in place deep down in your dependency graph.
That's where jspm comes in. It relies on NPM and Github as sources of structured packages, but then handles all the dependency configuration, format management/transformation, etc. Suddenly it's really easy to depend on new packages, regardless of where they come from or their format, and to use them without having to write a lot of config paths. And it also lets you bundle a dependency graph together, optionally with arithmetic to add/remove/isolate subtrees, and to run your app off the bundle instead of the sources, without having to change a single line of code manually (no changing of import scripts, etc).
Note that a lot of people have been debating this recently, including a long whiny and interest post on Medium, whose author unfortunately desperately wants to try and contrive Bower to do the job, for some reason. Still well worth a read, as what he describes is almost exactly what jspm provides.


Fix Quickstart -bootstrapTableDir command line option.

This is a fix for the -bootstrapTableDir which seems to have broken with #9246 enhancements. Verified that the existing functionality of loading a table by specifying -bootstrapTableDir is working:
-bootstrapTableDir /Users/alal/tables/windows -configFile /Users/alal/Quickstart/config.conf
Also verified that the new functionality that loads all the sample tables when no -bootstrapTableDir option is provided is also working.

@xiangfu0 Please review.

Codecov Report

Merging #9285 (73c9a0a) into master (d778df2) will decrease coverage by 54.58%.
The diff coverage is 0.00%.

:exclamation: Current head 73c9a0a differs from pull request most recent head 4586334. Consider uploading reports for the commit 4586334 to get more accurate results

@@              Coverage Diff              @@
##             master    #9285       +/-   ##
=============================================
- Coverage     69.90%   15.32%   -54.59%
+ Complexity     4685      168     -4517
=============================================
  Files          1862     1813       -49
  Lines         99335    97271     -2064
  Branches      15115    14883      -232
=============================================
- Hits          69444    14910    -54534
- Misses        24967    81231    +56264
+ Partials       4924     1130     -3794

Flag
Coverage Δ

integration1
?

integration2
?

unittests1
?

unittests2
15.32% <0.00%> (-0.01%)
:arrow_down:

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

 Learn more

Thanks for fixing this!


docs: adjust notebooks to new API

Summary of Changes
The notebooks are now being executed again and work with the new API.

:tada: This PR is included in version 0.25.0 :tada:
The release is available on:

v0.25.0
GitHub release

Your semantic-release bot :package::rocket:


Crash when removing a member

To reproduce:
Room 1 with 3 users: A (riot-ios user), B (riot-ios user), C (riot-web user)

A remove C

No crash

A remove B

Device A crashes

I was not able to reproduce the issue.

Me neither...


govuk_solr: attempt #2 to add "disable" mode, which actually just stops & disables the jetty service

Let's try that again, shall we?
https://trello.com/c/zLLNaKtv
A re-spin of #10485 which moves the definitions of $required_packages and $java_home out of the conditional block, with the hopes that it will now be visible to jetty.erb.

(I'm going to try applying this semi-manually to ci-integration first and watch its actions carefully)

This does indeed appear to have no effect on nodes that don't have $disable set.


except ? not recognized by this plugin

according to the documentation of Cython @ https://cython.readthedocs.io/en/latest/src/userguide/language_basics.html#error-return-values, the syntax of except? should be recognized as a way to specify the exception value, whereas the syntax is not recognized and the following code is regarded as a syntax error .
Please help fix.
from libc.limits cimport INT_MAX
cpdef int test_func(int input) except ?INT_MAX:
return 1
thanks
Xiquan Ren

the original explanation of the syntax is
Error return values
In Python (more specifically, in the CPython runtime), exceptions that occur inside of a function are signaled to the caller and propagated up the call stack through defined error return values. For functions that return a Python object (and thus, a pointer to such an object), the error return value is simply the NULL pointer, so any function returning a Python object has a well-defined error return value.
While this is always the case for Python functions, functions defined as C functions or cpdef/@ccall functions can return arbitrary C types, which do not have such a well-defined error return value. By default Cython uses a dedicated return value to signal that an exception has been raised from non-external cpdef/@ccall functions. However, how Cython handles exceptions from these functions can be changed if needed.
A cdef function may be declared with an exception return value for it as a contract with the caller. Here is an example:
cdef int spam() except -1:
...
With this declaration, whenever an exception occurs inside spam, it will immediately return with the value -1. From the caller’s side, whenever a call to spam returns -1, the caller will assume that an exception has occurred and can now process or propagate it. Calling spam() is roughly translated to the following C code

If all possible return values are legal and you can’t reserve one entirely for signalling errors, you can use an alternative form of exception value declaration
cdef int spam() except? -1:
...
The ? indicates that the value -1 may signal an error.
In this case, Cython generates a call to PyErr_Occurred() if the exception value is returned, to make sure it really received an exception and not just a normal result. Calling spam() is roughly translated to the following C code:
ret_val = spam();
if (ret_val == -1 && PyErr_Occurred()) goto error_handler;
There is also a third form of exception value declaration


Feature request: Popover

Hello,
Would you consider adding a popover component that could be triggered by click/hover events?

I'm actually working on a popover component :) I'll try to create a PR next week

Awesome, thanks for letting me know! :)

I'm not a fan of popovers but I can see their utility, gonna wait for @Tobbe PR :)

We're using it for login/logout in our current project.

Re #47 that would probably look something like this

    Element to hover to trigger preview

If you don't have the time to do so, let me know so I can start one.

I can put up a quick and dirty PR just so we have something to discuss :)

Making some progress on that PR...

Writing the documentation I realize there is a lot of work left to do to align it more with the rest of Buefy... This will take some time.

Oh before making the docs, let me see how it is? You can make a PR or a fork link :)

PR created. Will not have much more time to spend on this during the week I'm afraid. (Smal fixes/changes are no problem of course.)

Probably not gonna have time to test it before weekend as well. Thanks man.

Haven't forgotten about this. But vue's <transition> element is giving me some problems with unit testing...

Me neither! Just out of time, gonna take a look on weekend maybe.

Dropdown now works like Popver as well.

I think a proper popover that you can render HTML in (aka Bootstrap Popovers) is a useful feature. The current dropdowns don't really accommodate for that use-case (especially centered positioning & arrows like the tooltip has are missing). May i give it another go?

@jwahdatehagh Thanks but I don't think it's worth, dropdown the way it is covers most of cases

I arrived here hoping to find a solution specifically for creating a tooltip with rendered HTML content. Is there a way to take the styling from tooltip and apply it to dropdown? I can't easily figure it out. @jwahdatehagh is onto something for sure.

@grebebird i'm just using the excellent https://github.com/Akryum/v-tooltip with buefy/bulma styling now. If file size is an issue, you can remove Buefy's Tooltip import to make up for it 😉

Thanks @jwahdatehagh !
I feel like I'm on to something with using a dropdown with a "notification is-primary" inside (looks like a tooltip without the arrow), and I'm battling removing the top/bottom padding of the "dropdown-content" class, which for some reason isn't working (yet?). I feel like just adding "is-tooltip" to "b-dropdown" could encapsulate this more cleanly than I am hacking it (e.g. remove all padding, set background color like the is-primary notification).


Hazard type coastal flood also returns flood

When clicking on the facet filter coastal flood it returns datasets that are not coastal flood. I initially thought it was because it also returned flood hazard type but it looks like the issue is more generic to all hazard types.
https://jkan.riskdatalibrary.org/datasets/?hazard_type=coastal-flood

This is the expected behaviour enforced by last update.
The selection returns 1 coastal hazard dataset + all exposure datasets.
To see only the hazard layer, you need to first select Hazard as category.
I understand the intentions but I don't fully agree with this - it looks like a bug.


Prevents shadowing a variable in another scope block

Previous code has shadowed a variable in another scope, therefore it never returned a real HttpResponse body after a break loop statement. After this minor fix, I was able to receive working &HttpResponse on a gcm.SendHttp() callback.

Thanks!


thymol not found by search

The thymol project is no longer found as a search result, although the packages query looks fine:
curl http://bower.herokuapp.com/packages/thymol
{"name":"thymol","url":"git://github.com/thymol/thymol.js.git","hits":26}
Can you please provide any insight into this?

You do not have a bower.json file in your repo
https://github.com/thymol/thymol.js
Thus it will not show up. Add it to your project and you should be all set :+1:


Not all operations are supported by the Edge TPU

Hey there!
I´m using tensorflow gpu version 2.3.0 and my custom model (anchors and image size are the same, i only modified the number of classes and used relu layers instead of leaky).
First of all I needed to add this line converter.experimental_new_converter = False because my tensorflow version is higher than 2.2 (just in case this is interesting for you).
After that I was able to run edgetpu_compiler -s quant.tflite  but the output tells me that some operations will be run on the CPU
Edge TPU Compiler version 14.1.317412892

Model compiled successfully in 329 ms.

Input model: quant.tflite
Input size: 8.38MiB
Output model: quant_edgetpu.tflite
Output size: 8.40MiB
On-chip memory used for caching model parameters: 1.84MiB
On-chip memory remaining for caching model parameters: 256.75KiB
Off-chip memory used for streaming uncached model parameters: 5.64MiB
Number of Edge TPU subgraphs: 1
Total number of operations: 25
Operation log: quant_edgetpu.log

Model successfully compiled but not all operations are supported by the Edge TPU. A percentage of the model will instead run on the CPU, which is slower. If possible, consider updating your model to use only operations supported by the Edge TPU. For details, visit g.co/coral/model-reqs.
Number of operations that will run on Edge TPU: 19
Number of operations that will run on CPU: 6

Operator                       Count      Status

RESIZE_NEAREST_NEIGHBOR        1          Operation version not supported
MAX_POOL_2D                    6          Mapped to Edge TPU
CONCATENATION                  1          More than one subgraph is not supported
QUANTIZE                       1          More than one subgraph is not supported
QUANTIZE                       2          Mapped to Edge TPU
QUANTIZE                       1          Operation is otherwise supported, but not mapped due to some unspecified limitation
CONV_2D                        2          More than one subgraph is not supported
CONV_2D                        11         Mapped to Edge TPU

Do you have any idea how to fix this?

I have the exact same problem with the same number/type of unsupported ops. Also on tf 2.3.0 (gpu).

Update: Tensorflow 2.1.0 seems to work for me. Didn't have to change anything about the EdgeTPU compiler, just the TF version while running keras_to_tflite_quant.py

I have experienced the same issue, finally a was able to fully compile a yolov3-tiny custom model with the latest tensorflow version (v2.3). The main problem here is that the edge tpu compiler can't convert the RESIZE_NEAREST_NEIGHBOR operation (that comes from the Upsampling2D layer in the keras transformation) and it creates the rest of failed compiled operations due to subgraphs.
What the edge tpu compiler really can't convert is the half_pixel_centers = True  argument of the resize neighbor operation in https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/ops/image_ops_impl.py#L1627 so the solution is to set it to false, I guess the same problem appears when trying to compile the bilinear operation. The workaround that I did was to hardcode half_pixel_centers = False  in the python/site-packages/tensorflow/python/ops/gen_image_ops.py that the system generates when compiling tensorflow, but I have yet to do more research on the problem.

I have experienced the same issue, finally a was able to fully compile a yolov3-tiny custom model with the latest tensorflow version (v2.3). The main problem here is that the edge tpu compiler can't convert the RESIZE_NEAREST_NEIGHBOR operation (that comes from the Upsampling2D layer in the keras transformation) and it creates the rest of failed compiled operations due to subgraphs.
What the edge tpu compiler really can't convert is the half_pixel_centers = True argument of the resize neighbor operation in https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/ops/image_ops_impl.py#L1627 so the solution is to set it to false, I guess the same problem appears when trying to compile the bilinear operation. The workaround that I did was to hardcode half_pixel_centers = False in the python/site-packages/tensorflow/python/ops/gen_image_ops.py that the system generates when compiling tensorflow, but I have yet to do more research on the problem.

It solved the problem (Y)!

I have experienced the same issue, finally a was able to fully compile a yolov3-tiny custom model with the latest tensorflow version (v2.3). The main problem here is that the edge tpu compiler can't convert the RESIZE_NEAREST_NEIGHBOR operation (that comes from the Upsampling2D layer in the keras transformation) and it creates the rest of failed compiled operations due to subgraphs.
What the edge tpu compiler really can't convert is the half_pixel_centers = True argument of the resize neighbor operation in https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/ops/image_ops_impl.py#L1627 so the solution is to set it to false, I guess the same problem appears when trying to compile the bilinear operation. The workaround that I did was to hardcode half_pixel_centers = False in the python/site-packages/tensorflow/python/ops/gen_image_ops.py that the system generates when compiling tensorflow, but I have yet to do more research on the problem.

Operator                       Count      Status
MAX_POOL_2D                    6          Mapped to Edge TPU
RESIZE_NEAREST_NEIGHBOR        1          Mapped to Edge TPU
QUANTIZE                       4          Mapped to Edge TPU
CONCATENATION                  1          Mapped to Edge TPU
CONV_2D                        13         Mapped to Edge TPU
It solved the problem (Y)!  Thank You :)


Menus with options Observable keep old values

If I construct a Menu with an options Observable and update it to less values, some of the old values are still shown.
MWE
# Makie 0.6.2, GLMakie 0.17.2
fig = Figure()
opt = Observable(["A", "B", "C"])
Menu(fig[1,1], options=opt)
opt[] = ["D"]

Extra info: This seems to only occur when fig is shown prior to setting opt[] = ["D"]. If fig is (re)displayed after, it works as expected.

This is probably due to the additional scene nesting in Blocks since 0.17, which messed with the deletion behavior, because the menu logic hasn't changed.

Could that change also be related to the fact I'm now seeing truncate UInt8 errors with scene IDs now? (an issue I have yet to make an Issue about).

Yes that is also related. If you have a lot of Blocks there are too many scenes created for GLMakie to handle. It wasn't caught at the time because our tests don't seem to use 255+ Scenes.

Ah, that's interesting. Could the fact so many scenes are generated also be related to it being rather slow to interact with? It's a scatter + contour + 2x density plot graph on ~2000 2d data points with several Menus and an IntervalSlider controlling the data.

Menu could probably use a redesign that doesn't use Label and Box internally for the entries as those are probably too heavy. I'm not sure, @SimonDanisch said that Scenes should be very lightweight so that it shouldn't matter much that more are added

My impression is that interactivity is usually slow when it ends up triggering lots of things. For example in #1835 I made some improvements to Axis3 interactions. When rotating the axis the rough chain of observables for labels was:

mouse events trigger azimuth and elevation (probably mostly both)
azimuth (always) triggers mi1 and mi2, elevation (always) triggers mi3 (these hold information of the viewing angle, i.e. above or below, left or right, front or back) and both trigger an update to projectionview (amongst other matrices)
each of those trigger text position, alignment and rotation updates for aixs labels
And each of those triggers a full recalculation of text layouting

So starting from one mouse event you ended up triggering 1 -> 2 -> 5 -> 15 recalculation of the character layout for labels. Times 3 for x, y, z label and I also skipped ticks, grid lines and frame lines.
After the pr mi1, mi2, mi3 only trigger when they actually change (which is rare), text positions no longer trigger a recalculation of the character layout and text alignment and rotation have been merged into one trigger. So the common chain has been reduced to 1 -> 2 -> 2 (up to 5) -> 2 (5) recalculations of the character layout.

Yes you're completely right. I find it's not so easy to predict the best structure for an observable chain before I've written it once in its full form. For example, with Axis3, it was natural for me to think of azimuth and elevation separately, but of course in terms of observables it makes more sense to have one orientation value for the Axis and not split it..

I fell like a lot of times readability and usability are at odds with performance when using Observables.
For example, changing output = map(f, input) to
output = Observable(initital_value)
on(x -> output.val = x, input)

is often useful to avoid triggering downstream updates multiple times, but it takes more space and gives you no chance to follow the observable chain upwards.
Or patterns like
o1 = map(prep1, input)
o2 = map(prep2, input)
o3 = map(prep3, input)
output1 = map(f, o1, o2)
output2 = map(g, o1, o3)

which come up often and feel natural, but result in multiple triggers. Doing
output1 = map(x -> f(prep1(x), prep2(x)), input)
output2 = map(x -> g(prep1(x), prep3(x)), input)

would call prep1 multiple times, which might be more expensive. So you'd have to do
o1 = map(prep1, input)
o2 = map(prep2, input)
o3 = map(prep3, input)
output1 = map(_ -> f(o1[], o2[]), input)
output2 = map(_ -> g(o1[], o3[]), input)

which makes it difficult to understand how updates flow.

I still hope we can come up with a bundle-of-observables object that can help with this mess by grouping updates together and forwarding only to those places that need it.

The original issue raised here has now been solved in #2074.


blog: announce the removal of the translated docs

Motivation and Context

blog post containing announcement of removal.

@purplecabbage I finished with this PR too. Merge it in when ready.

This PR is closed by #1199


Taking screenshot while camera is active crashes app on android devices

Problem
Application restarts and crashes if user takes a screenshot while camera is active, snaps picture and presses "OK"
Command or Code

Version information

OS: Android 11
node -v : 14.21.1
cordova -v : 10.0.0<EMAIL_ADDRESS>"cordova-plugin-camera": "^6.0.0"
Logs

Potentially related to https://github.com/apache/cordova-plugin-camera/issues/679 with an open PR https://github.com/apache/cordova-plugin-camera/pull/781
If you could try testing that PR to see if it will solve your issue
cordova plugin remove cordova-plugin-camera
cordova plugin add https://github.com/dongourdet/cordova-plugin-camera.git#android-recoverable-security-exception

Fixed by https://github.com/apache/cordova-plugin-camera/pull/907


Perl 6 variables

For some reason, my variable rule is being skipped (or not catching) by linguist (Atom/Highlights has no problem with it though).
Here's the rule to save you from clicking a link.  It's in the variable entry of the repository and I'm sure it's not catching because the sigil ($, @, %, &) is left as bare text.
        {
          'match': '(?x)
            (\\$|@|%|&)
            (\\.|\\*|:|!|\\^|~|=|\\?)?
            (
              (?:\\p{Alpha})
              (?:
                [a-zA-Z0-9_\xc0-\xff\\$]|
                [\\-\'][a-zA-Z_\xc0-\xff\\$]
              )*
            )'
          'captures':
            '1':
              'name': 'variable.other.identifier.sigil.perl6fe'
            '2':
              'name': 'support.class.twigil.perl6fe'
            '3':
              'name': 'variable.other.identifier.perl6fe'
          'name': 'meta.variable.container.perl6fe'
        }

We've had the same kind of grammar interpretation differences in the past between Sublime Text and Linguist. What was happening is that GitHub and Sublime Text were using different regexp processors: GitHub uses a PCRE-based engine whereas Sublime Text uses Oniguruma. I don't know what Atom is using but it could be the same kind of discrepancies.
You should try to tweak your regular expressions. In particular, I'd try to replace \\p{Alpha} ;)

Thanks for your reply! Yes I do believe this is the issue.  Atom does indeed use Oniguruma and I have tried to take advantage of this fact.  I will see what I can do to fix this while still remaining compatible with both engines.

@pchaigno That property was definitely the blocker for this rule! I've updated my repo and tried with Lightshow and it works perfectly.
Should I submit a PR to update the submodule or could someone just bump it to the latest commit?

@pchaigno That property was definitely the blocker for this rule! I've updated my repo and tried with Lightshow and it works perfectly.

Glad I could help :smile:

Should I submit a PR to update the submodule or could someone just bump it to the latest commit?

No need, it'll be automatically updated with the next release of Linguist ;)


Fix wincrypt symbols conflict

With openssl variants such as boring ssl, the conflict symbols are not undefined such as openssl.
Explicit undefine those so it works for both normal openssl and  boring ssl

I've never used boringSSL or wincrypt (I don't have a windows machine), so can you provide a bit more context?
I'm not sure what downstream consequences undefining the symbols might have if we do it globally.  Maybe we could limit the lines to only execute if there is some kind of IS_BORINGSSL macro.
Similar issue:
https://bugs.chromium.org/p/boringssl/issues/detail?id=371

Looks like there is one
https://boringssl.googlesource.com/boringssl/+/HEAD/PORTING.md
So I updated the change with that
#ifdef OPENSSL_IS_BORINGSSL


search-sample OBJ format models don't load textures.

When loading an OBJ format object with textures, the texture loads fail as they attempt to load from server, rather than the resources actual remote directory specified by its url.
A workaround/hack is to insert the following code in the loading code in search-sample->createImage, where the MTLLoader is created:

var loader = new THREE.MTLLoader();

loader.setCrossOrigin(true);
for(var i=0;i<format.resources.length;i++){
	var resource = format.resources[i];
	if(resource.contentType.indexOf("image/")==0){
		var texPathEnd = resource.url.indexOf(resource.relativePath);
		if(texPathEnd!=-1){
			loader.setTexturePath(resource.url.slice(0,texPathEnd));
			break;
		}
	}
}

This hack finds the first image/* resource, subtracts the filename from the URL, then sets the MTLLoaders "texturePath" to that. MTLLoader uses this path in subsequent texture load attempts.
Note, this triggers cross origin request, which requires setting loader.setCrossOrigin(true);
-hth

Fixed. Thanks!

@ianmacgillivray this can be closed.


dm-worker hangs after running dm tasks with fast/full validators

What did you do?

Run dm tasks with fast and full validators
Run other DM cases, run dmctl query-status to get DM task status

What did you expect to see?
dm-worker should not hang, dmctl query-status should run success
What did you see instead?
dm-worker hangs, dmctl query-status return context deadline exceeded error
/ # /dm-master -V
Release Version: v6.3.0-alpha
Git Commit Hash: 2c12e2e60d786d61419fc19aa28691dbdf525b55
Git Branch: heads/refs/tags/v6.3.0-alpha
UTC Build Time: 2022-09-27 11:01:23
Go Version: go version go1.19.1 linux/amd64
Failpoint Build: false
/ # time /dmctl --master-addr=[<IP_ADDRESS>:8261](http://<IP_ADDRESS>:8261/) query-status
{
    "result": true,
    "msg": "",
    "sources": [
        {
            "result": true,
            "msg": "no sub task started",
            "sourceStatus": {
                "source": "source-0",
                "worker": "dm-dm-worker-2",
                "result": null,
                "relayStatus": null
            },
            "subTaskStatus": [
            ]
        },
        {
            "result": false,
            "msg": "[code=38008:class=dm-master:scope=internal:level=high], Message: grpc request error, RawCause: rpc error: code = DeadlineExceeded desc = context deadline exceeded",
            "sourceStatus": {
                "source": "source-1",
                "worker": "",
                "result": null,
                "relayStatus": null
            },
            "subTaskStatus": [
            ]
        }
    ]
}
real    0m 30.15s
user    0m 0.05s
sys     0m 0.02s
/ # grep WARN /var/lib/dm-master/log/dm-master.log | tail
[2022/09/27 17:48:12.060 +00:00] [WARN] [interceptor.go:197] ["request stats"] [component="embed etcd"] ["start time"=2022/09/27 17:47:41.958 +00:00] ["time spent"=30.101792535s] [remote=[<IP_ADDRESS>:40152](http://<IP_ADDRESS>:40152/)] ["response type"=/pb.Master/QueryStatus] ["request count"=-1] ["request size"=-1] ["response count"=-1] ["response size"=-1] ["request content"=]
[2022/09/27 17:49:28.632 +00:00] [WARN] [interceptor.go:197] ["request stats"] [component="embed etcd"] ["start time"=2022/09/27 17:44:18.790 +00:00] ["time spent"=5m9.842540218s] [remote=[<IP_ADDRESS>:38842](http://<IP_ADDRESS>:38842/)] ["response type"=/pb.Master/OperateTask] ["request count"=-1] ["request size"=-1] ["response count"=-1] ["response size"=-1] ["request content"=]
[2022/09/27 17:49:29.223 +00:00] [WARN] [interceptor.go:197] ["request stats"] [component="embed etcd"] ["start time"=2022/09/27 17:48:59.121 +00:00] ["time spent"=30.102463024s] [remote=[<IP_ADDRESS>:40665](http://<IP_ADDRESS>:40665/)] ["response type"=/pb.Master/QueryStatus] ["request count"=-1] ["request size"=-1] ["response count"=-1] ["response size"=-1] ["request content"=]
[2022/09/27 17:50:45.723 +00:00] [WARN] [interceptor.go:197] ["request stats"] [component="embed etcd"] ["start time"=2022/09/27 17:45:36.547 +00:00] ["time spent"=5m9.175809748s] [remote=[<IP_ADDRESS>:39335](http://<IP_ADDRESS>:39335/)] ["response type"=/pb.Master/OperateSource] ["request count"=-1] ["request size"=-1] ["response count"=-1] ["response size"=-1] ["request content"=]
[2022/09/27 17:52:05.587 +00:00] [WARN] [interceptor.go:197] ["request stats"] [component="embed etcd"] ["start time"=2022/09/27 17:46:56.189 +00:00] ["time spent"=5m9.397952776s] [remote=[<IP_ADDRESS>:39842](http://<IP_ADDRESS>:39842/)] ["response type"=/pb.Master/OperateSource] ["request count"=-1] ["request size"=-1] ["response count"=-1] ["response size"=-1] ["request content"=]
[2022/09/27 17:53:21.104 +00:00] [WARN] [interceptor.go:197] ["request stats"] [component="embed etcd"] ["start time"=2022/09/27 17:48:11.972 +00:00] ["time spent"=5m9.132926971s] [remote=[<IP_ADDRESS>:40346](http://<IP_ADDRESS>:40346/)] ["response type"=/pb.Master/OperateSource] ["request count"=-1] ["request size"=-1] ["response count"=-1] ["response size"=-1] ["request content"=]
[2022/09/27 17:54:38.529 +00:00] [WARN] [interceptor.go:197] ["request stats"] [component="embed etcd"] ["start time"=2022/09/27 17:49:29.125 +00:00] ["time spent"=5m9.404252609s] [remote=[<IP_ADDRESS>:40868](http://<IP_ADDRESS>:40868/)] ["response type"=/pb.Master/OperateSource] ["request count"=-1] ["request size"=-1] ["response count"=-1] ["response size"=-1] ["request content"=]
[2022/09/28 01:25:27.517 +00:00] [WARN] [interceptor.go:197] ["request stats"] [component="embed etcd"] ["start time"=2022/09/28 01:24:57.413 +00:00] ["time spent"=30.103021161s] [remote=[<IP_ADDRESS>:59562](http://<IP_ADDRESS>:59562/)] ["response type"=/pb.Master/QueryStatus] ["request count"=-1] ["request size"=-1] ["response count"=-1] ["response size"=-1] ["request content"=]
[2022/09/28 01:27:45.295 +00:00] [WARN] [interceptor.go:197] ["request stats"] [component="embed etcd"] ["start time"=2022/09/28 01:27:15.185 +00:00] ["time spent"=30.109207704s] [remote=[<IP_ADDRESS>:60382](http://<IP_ADDRESS>:60382/)] ["response type"=/pb.Master/QueryStatus] ["request count"=-1] ["request size"=-1] ["response count"=-1] ["response size"=-1] ["request content"=]
[2022/09/28 01:29:11.210 +00:00] [WARN] [interceptor.go:197] ["request stats"] [component="embed etcd"] ["start time"=2022/09/28 01:28:41.107 +00:00] ["time spent"=30.10232034s] [remote=[<IP_ADDRESS>:60906](http://<IP_ADDRESS>:60906/)] ["response type"=/pb.Master/QueryStatus] ["request count"=-1] ["request size"=-1] ["response count"=-1] ["response size"=-1] ["request content"=]

Versions of the cluster
master
current status of DM cluster (execute query-status <task-name> in dmctl)
/ # /dm-master -V
Release Version: v6.3.0-alpha
Git Commit Hash: 2c12e2e60d786d61419fc19aa28691dbdf525b55
Git Branch: heads/refs/tags/v6.3.0-alpha
UTC Build Time: 2022-09-27 11:01:23
Go Version: go version go1.19.1 linux/amd64
Failpoint Build: false

dm-worker logs
work1.dm-worker.log

When enter DataValidator.stopInner by user action (stop-task, validator stop, etc) or data validating error, stopInner will hold the lock and wait other validator goroutine exit. other validator goroutine may send error at https://github.com/pingcap/tiflow/blob/1961b63f2172ffcdc3609867996c0bf7f17e08f2/dm/syncer/validate_worker.go#L167-L171 or other place. But since the lock is hold by DataValidator.stopInner, reading from error channel is blocked at https://github.com/pingcap/tiflow/blob/1961b63f2172ffcdc3609867996c0bf7f17e08f2/dm/syncer/data_validator.go#L456-L459 When error channel is full (validate worker number > 10), it will enter deadlock.
And when this deadlock is caused by user action, it will further block DM-worker's so query-status can't be responsed.
worker1.goroutine.txt

And I remember uber's code guide channel size is 0 or 1. If we follow it this bug will be easier to be exposed

/found automation


Issues with TileMap collisions

Godot version
3.4 stable
System information
Windows 10
Issue description
The tile maps with physics don't work well. You can get stuck in them only with the rigid bodies. If you move a kinamatic body crazy fast it doesn't get stuck.
Rigid bodies dont get stuck in static bodies though.
Here is a video showing it. The deminstration starts about one min in. https://youtu.be/1R7j0QDXm_Q
Steps to reproduce
to reproduce you get tileset and then make sure it has phisics. After that you then set up a basically thickish peice of tile piecis that all have colition. You then create a rigid body and then atatch a script like this one. Move the rigid body down way low. Then run.
extends RigidBody2D

func _physics_process(delta):
	add_central_force(Vector2(0,-100))

Minimal reproduction project
In this project, I use this tileset. I think I need to mention them. https://opengameart.org/content/platformer-tilesets
GeomitryDash.zip

I think one way to fix it would be to make it so that the tile sets combiend to make one static body with perhaps a colition polygon around it

@mottom1  Please surround large blocks of text with triple backticks like this:
```
text here
```
This prevents them from taking too much space and also makes sure issue references aren't accidentally created. I edited your comment, but remember to do this next time :slightly_smiling_face:

I can confirm it, more than 1000 Y axis velocity makes it.
Reproducable project: 55336.zip


Issue with Cleanup Causes Pelican Tests to Fail on Subsequent Runs

When running all tests on the main branch in Pelican, the tests run successfully the first time, however, they fail in subsequent runs. The test that fails specifically is:
TestHandleCLIExecutableAlias/no-alias-mixedCase
It turns out this test copies the pelican executable to a different name PELICAN, but the PELICAN file already exists from the previous run, causing the cp command to fail.
The odd thing about this PELICAN file, which causes the problem, is that it is an empty file. Commands such as ls, find, and file do not detect it, and the rm command says that the file does not exist. However, when rm is run with the -f option, it successfully removes the file, and the test passes after that.
I see that in the test, we do os.Stat(arguments[0]) on line 232 in main_test.go to check if the file already exists. However, just like the bash commands mentioned before, os.Stat also fails to detect the file's presence.

Oddly, this happens only with the PELICAN test case. After removing this test case, the test works fine with the other cases.


⚠ Mobitopup has degraded performance

In d7b8626, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 8698 ms

Resolved: Mobitopup performance has improved in 05982e8.


main class

hi
Im using java netbeans and i want to run this project
where is the main class
can you help me please how i can run this project and see the result

Hi,
If you want to run the application as a console app, the Main class is https://github.com/loomchild/segment/blob/master/segment-ui/src/main/java/net/loomchild/segment/ui/console/Segment.java.
Jarek


Menu with items disappears

When hovering the mouse over the menu "with items" the submenu expands, but when trying to move the mouse over the submenu it suddenly disappears.
Problem discovered on Ubuntu 20.04, on Windows 10 everything works fine.

I just found out it is a bug in the Avalonia framework: https://github.com/AvaloniaUI/Avalonia/issues/4729

I just found out it is a bug in the Avalonia framework: https://github.com/AvaloniaUI/Avalonia/issues/4729


react-router v4

https://github.com/ReactTraining/react-router/blob/v4/README.md
This is still in alpha, but sounds like it should integrate much more closely with React/Redux.

Yea, I also think it will allow us to do some cool stuff with routes not having to be centralized anymore.


Better Concealing

First of all let me thank you for this awesome plugin. I have a few questions regarding the concealing of the latex code

I noticed that \overline{x} does not render to x̄. In fact, only very few overlined letters (i suspect the ones who have a single unicode letter corresponding to it) render in the concealed mode. It should be theoretically possible to render every possible overlined character as unicode is stackable (so even greek ones and fat ones and so on). Same goes for dotted / double dotted / hat and so on.
is it possible to have \frac{a}{b} simply render to a/b? If the fraction is larger it could render with brackets like {...}/{...}
A little thing: is it possible to have \, and \: and \; just render to [space]? I think it would make the concealed view even easier to read

only very few overlined letters (i suspect the ones who have a single unicode letter corresponding to it) render in the concealed mode. It should be theoretically possible to render every possible overlined character as unicode is stackable (so even greek ones and fat ones and so on).

Yes, that's correct! Only letters that have a corresponding unicode character with a bar get concealed. I'll look into stacking unicode characters; I wasn't aware that overlines etc were stackable. Thank you for the tip!

is it possible to have \frac{a}{b} simply render to a/b? If the fraction is larger it could render with brackets like (...)/(...)

Yep, I can try to add this in a future version. There's some discussion of this in #22.

A little thing: is it possible to have , and : and ; just render to [space]? I think it would make the concealed view even easier to read

Good idea, I'll add this in the next release.

Thank you so much for the fast reply! Sounds good, im looking forward to the next release :)

Fractions are now concealed in 1.4.5.

Fractions are now concealed in 1.4.5.

What theme are you using? The concealed code are quite wired in my case, and I thingk maybe this is caused by the theme.

What theme are you using? The concealed code are quite wired in my case, and I thingk maybe this is caused by the theme.

This is the default theme in Obsidian v0.15. Can you share a screenshot showing the problem and the LaTeX source code behind it?

Can you share a screenshot showing the problem and the LaTeX source code behind it?

The powers in the first line is written as ^{2} while in the second line ^2.

Moving to a new issue (#62).


(Feature Request) Add support for UMod Framework

Most Unity / Slime Rancher mods were made with umod framework. I would love to play them alongside UPM. Is this possible?

UPM is not being developed anymore, and is being superceded by https://github.com/GamePluginKit which is still under development (although I've been too busy with some IRL things lately to continue)
I believe that the uMod Framework already supports loading UPM mods though, so that's also an option.


@elevenlabs-alpha/react

yarn
yarn install v1.22.22
[1/4] Resolving packages...
error Error: https://registry.yarnpkg.com/@elevenlabs-alpha%2Freact: Not found
at params.callback [as _callback] (/home/taher/.nvm/versions/node/v20.18.0/lib/node_modules/yarn/lib/cli.js:66680:18)
at self.callback (/home/taher/.nvm/versions/node/v20.18.0/lib/node_modules/yarn/lib/cli.js:141410:22)
at Request.emit (node:events:519:28)
at Request. (/home/taher/.nvm/versions/node/v20.18.0/lib/node_modules/yarn/lib/cli.js:142382:10)
at Request.emit (node:events:519:28)
at IncomingMessage. (/home/taher/.nvm/versions/node/v20.18.0/lib/node_modules/yarn/lib/cli.js:142304:12)
at Object.onceWrapper (node:events:633:28)
at IncomingMessage.emit (node:events:531:35)
at endReadableNT (node:internal/streams/readable:1696:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Hi there - we don't have an @elevenlabs-alpha/react package?


add drawer background default/reset option

Add clear background option in drawer background.

I just have been hesitating about where the option should be placed so a little bit lazy. As a feasible alternative, you can set a usless picture for the drawer background and then delete the pic from Photos on your phone. Last to achieve that aim, restart the app. Ahahaha...

This option was add in commit  https://github.com/lzls/Videos/commit/b2106678fc74cdcae6f92b74ced748b5961f4c33, so issue closes.


Update ci.yml

Codecov Report

Merging #28 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #28   +/-   ##
=======================================
  Coverage   90.69%   90.69%
=======================================
  Files          10       10
  Lines         559      559
=======================================
  Hits          507      507
  Misses         52       52

Flag
Coverage Δ

#unittests
90.69% <ø> (ø)

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

Continue to review full report at Codecov.

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


HBase Range Filter to RDD with PySpark

@GenTang I was wondering if you have an example of how to subset an HBase table with a range filter or some other method. I am working with very large tables where the row key contains a timestamp and I would like to filter the HBase table to, for example, return just one day.
I can accomplish this with a filter on the RDD via Spark itself, but I feel like this is suboptimal and seems to take longer than a range filter scan via the HBase Shell.
Thanks!

I discovered this is possible with a conf such as:
    conf = {"hbase.zookeeper.quorum": zookeeperhost,
            "zookeeper.znode.parent": "/hbase",
            "hbase.mapreduce.inputtable": hbase_table,
            "hbase.zookeeper.property.clientPort": zookeeper_port,
            "hbase.zookeeper.leaderport": "3888",
            #"hbase.mapreduce.scan.row.start": startrow,
            #"hbase.mapreduce.scan.row.stop": stoprow
           }

this effectively conducts a range scan on the HBase table so you do not read the entire table into memory as an RDD.


Add documentation on demo datasets.

Write a small section on the available demo datasets VandeSchoot, Hall and Cohen.

@GerbrichFerdinands


Re-export necessary items in pathfinder-canvas

Export types need to use the canvas API from other pathfinder crates.
From pathfinder-color all types and convinience functions are exported.
From pathfinder-geometry only the 2D vector and rect types with
their convinience functions are exported.
Items from pathfinder-renderer are not re-exported as they also
belong to the back-end.
Pattern, while used in the canvas API, is not re-exported as
it is not needed for basic usage and depends on a lot of other types.
See #283

Not sure why continuous-integration/travis-ci/pr is still pending. If I click on details it shows a successful run.


How to combine with Droid-slam?

Hi, thanks for contributing such great work! I was wondering how you combined monocular depth with Droid-slam? Is the monocular depth used for Droid-slam initialization? Or is it just taking the pose provided by Droid-slam and fusing it with TSDF?

Hi, thanks for contributing such great work! I was wondering how you combined monocular depth with Droid-slam? Is the monocular depth used for Droid-slam initialization? Or is it just taking the pose provided by Droid-slam and fusing it with TSDF?

Thanks for your interest!  We use the predicted metric depth as a prior for the RGBD mode of droid SLAM. The depth serves as initial clues and regularization items. No fusing stage is needed.

嗨，感谢您贡献如此出色的工作！我想知道你是如何将单筒望远镜深度与 Droid-slam 结合起来的？单眼深度是否用于 Droid-slam 初始化？或者它只是采用 Droid-slam 提供的姿势并将其与 TSDF 融合？

感谢您的关注！我们使用预测的度量深度作为 droid SLAM 的 RGBD 模式的先验。深度用作初始线索和正则化项。不需要熔融阶段。

i wonder how to get the metric depth ?because i find out that output result is not like metric depth(near region big value，far region small value)


M1 Mac Problem: nothing provides requested libgfortran 5.0.0.dev0**

Required attestation

[ x] I have completely and exactly followed the virtual environment setup instructions from the book and have consulted the README for any updates.
Comment: I followed the README instructions for M1 Macs.

[ x] I have cloned either this repository or my fork of this repository so that I have all necessary files on my local machine.

[x ] I have checked that this issue has not already been reported or resolved here.

[x ] I am aware that there is a pre-built Binder environment that I can use, but I want to install locally on my machine instead.

Background information
1. Which OS are you using?
MacOS 12.6.3 M1 chip
2. Which Python version are you using?
3.9.7
3. Are you using conda or venv?
mamba

Commands run and their outputs
The commands (or concepts) that I ran were:
forked the repo
cloned repo using github desktop
cd into repo directory on local
Then,
conda install mamba -n base -c conda-forge
mamba env create --file m1_environment.yml
Screenshots
Output of the above commands yields:

From your screenshot, mamba is not looking for ARM-compatible packages, but rather for ones that would work with the old chip architecture (Intel chip). See where it says conda-forge/osx-64 in your screenshot? For Apple Silicon chips, this would be conda-forge/osx-arm64. It seems that you have an Intel chip rather than an M1 chip, in which case you would follow the instructions as laid out in the book (i.e., use the environment.yml file and not the m1_environment.yml file).
This package is still available on conda-forge, but only for osx-arm64 architectures (Apple Silicon chips). This package is only needed for Apple Silicon chips, and it is only available for ARM chips (not Intel). If you do have an Apple Silicon chip, then I'm not sure what is going wrong since I'm not able to reproduce this on my machine.

Thanks for your quick response! I definitely have an Apple M1, so I will investigate and post any results I find here.


[CERT-TEST-FAILURE] -[TC-IDM-10.1] Test-failure

Feature Area
Other
Test Case
TC-IDM-10.1
Reproduction steps
Command to run the Test-case script: python3 TC_DeviceBasicComposition.py --manual-code<PHONE_NUMBER>2  --storage-path admin_storage.json --tests test_IDM_10_1
Bug prevalence
Whenever i do
GitHub hash of the SDK that was being used
2d5fe2ce434f5d0f7714d55e67914e3e8ebf5827
Platform
raspi
Anything else?
As per the latest change in the test-plan https://github.com/CHIP-Specifications/chip-test-plans/pull/3383 The step 3 "For every cluster on every endpoint verify that the following global attributes do not contain duplicate values:" has been newly added. So the python script needs to be updated as per the test-plan.
Test-plan Reference: https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/interactiondatamodel.adoc#tc-idm-10-1-cluster-requirements-global-attributes-dut_server

This isssue is resolved in https://github.com/project-chip/connectedhomeip/pull/28892


Create function/script to assemble custom PO file based on queried items.

After refining the query established in #5144, need to use that query to output a custom file formatted as a PO file ready to be imported into POEditor.

Looks like we're not going the route of a custom script, etc... just going to use good ole MySQL and run a query to grab the handful of items and manually setup the POT file.
So closing this issue.

@angaither @mikefantini


Ignore npm@5 package-lock.json

Currently running npm test in DefinitelyTyped repo with npm version 5 results in generating package-lock.json for definitions having package.json, e.g. multer-s3. Because of that npm test fails with:

Error: Directory /../DefinitelyTyped/types/multer-s3 has unused file package-lock.json
at /.../DefinitelyTyped/node_modules/types-publisher/src/lib/definition-parser.ts:348:11
at Generator.next ()
at fulfilled (/.../DefinitelyTyped/node_modules/types-publisher/bin/lib/definition-parser.js:4:58)

I'm having the same issue. Any luck with resolutions?

@nik-john I submitted #351 which fixes this issue.


#35352 sub pages for settings

When running the project locally and clicking on a link I see the following error:


Critical vulnerability fixes + minimal adjustments for running on Mac with Apple silicon

This PR has the minimal changes required to:

Resolve some critical and high vulnerabilities.
Allow development on Mac computers with Apple silicon processors.

This includes the following changes:

Running npm audit fix to apply some non-breaking, automatically-fixable vulnerability fixes. This changed the package-lock.json file.
Ensuring the docker service runs in the linux/amd64 context.
Replacing the legacy node-sass package with the recommended replacement.

Before running npm audit fix:

After running npm audit fix:

I did some checks to make sure everything works properly.

Related issues:

https://github.com/filegator/filegator/issues/501
https://github.com/filegator/filegator/issues/414

Also resolves:

https://github.com/filegator/filegator/pull/361
https://github.com/filegator/filegator/pull/303

Thanks for this, I will fix more dependencies in a sepatare mr and combine all this to pass ci/cd

Closed with #508

Thank you 🙏


Performance analysis in chrome devTools: Taking 10-20 seconds(approx) to load

I'm submitting a ...
[ ] bug report
What is the current behavior?
The homepage is taking a lot of time to load, I did a performance analysis in chrome canary and it is taking
a) 17.29 seconds as first load time,
attaching the screenshots of the network and the timeline tabs.

b) 10.15 seconds for consecutive loads since the files come from cache,

In both the cases it is taking a lot of time which makes it difficult to use this for any production applications.
Not attaching the timeline data details since the data can be retrieved very easily in a web browser.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
The readings can be stimulated easily in any web browser devTools.
What is the expected behavior?
I think there is a lot of room for improvement in the performance.
What is the motivation / use case for changing the behavior?
Make the project useful to be used as a live application.
Please tell us about your environment:
OS X El capitan (10.11.6)
Chrome canary (56.0.2891.0)
Checked in the above environment but pretty sure it can be replicated in most of the systems.
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
I did a basic analysis of the call tree and flame chart of the same, the basic observations were:
a) If you check the call stack, bootstrap and jQuery are taking a lot of time and must be increasing a lot of time in the scripting phase. I guess approximately 50% of the loading time is coming from here.
b) zone.js invoke is taking a of time in the initial phase.
c) zone.js animation frame fired is taking quite much time after the completion of the scripts and network calls which is contributing to the idle time in the call tree summary.

I feel also slow than before!

Hi @hearsid, thanks for submitting this questions. Are you looking into the development build or a production one?

@nnixaa Just checked the production build (ran it on my localhost by the webpack configration provided), it is taking 11.7 seconds (approx) to load. I can create a PR to enable gzip compression in webpack.prod.js . gzip is supported by almost all browsers now and thus I think adding and enabling it be default for the production build will be a good idea since we have some huge files here. (screenshot attached)

I made change in my code to enable gzip compression in the webpack file and nginx and hosts file to see the difference the file sizes and here is the difference.
vendor..bundle.js   from 2.0MB -> 372KB
main..bundle.js       from 1.3MB -> 339KB
Screenshot attached.
Since I made the changes in the my host file the domain is http://ng2adminlocal.com/ in the address bar.

If you think the same will be a good idea, here is the link to the PR for the same.
https://github.com/akveo/ng2-admin/pull/370
Cheers.

@hearsid how did you configure your server to run gzip?

@elviro You can check the PR above ( https://github.com/akveo/ng2-admin/pull/370 ) to see the current nodejs setup to support gzip, nodejs server mostly goes with an nginx server as reverse proxy so if you are using an nginx server, it is pretty easy to configure nginx server to support gzip ( https://www.digitalocean.com/community/tutorials/how-to-add-the-gzip-module-to-nginx-on-centos-7 )
Apart from this, I also did some POC of angular 2 server side rendering by angular universal and the results for improving the first load time were really good.

im getting illegal characters on the browser when i change the index.html js files to the .gz files..

Please don't change index.html js file links in the

so if i want to test this locally with production build. where is this nginx config file? if it has to do with configuring the server that may be out of my hands as that is hacking it.

Closing due to inactivity.


release mode is broken

if you do release mode in ios, it doesnt work.
You need to search for Entitlements-Release.plist and add the following:
<key>com.apple.security.application-groups</key> 	<array> 		<string>group.com.mango.clickupdev.shareextension</string> 	</array>
might want to update docs

I just had the same error. This did work before.

@joshoconnor89
Which error are you experiencing exactly?
I am getting "Code Signing Error: ShareExt requires a provisioning profile with the App Groups and Push Notifications features."
Your fix does not seem to help ...


Composite model for particle mechanics

Description
Implementing the composite model for particle mechanics: The phase in the current particle mechanics implementation is set to 'primary' by default. This is being updated to support independent phases (e.g., primary/secondary such as Gr/Si). To accommodate these changes, the associated files in full_battery_models, interface, SEI, and particle modules have been updated, along with modifications to the Chen2020 parameter set.
This is part of the work by Bonkile et al.
Fixes # (issue)
Type of change
Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s. If necessary, also add to the list of breaking changes.

[x] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[ ] Bug fix (non-breaking change which fixes an issue)

Key checklist:

[ ] No style issues: $ pre-commit run (or $ nox -s pre-commit) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
[ ] All tests pass: $ python run-tests.py --all (or $ nox -s tests)
[x] The documentation builds: $ python run-tests.py --doctest (or $ nox -s doctests)

You can run integration tests, unit tests, and doctests together at once, using $ python run-tests.py --quick (or $ nox -s quick).
Further checks:

[ ] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works

@brosaplanella Unable to request specific reviewer in draft mode.

Hi Asher! The style tests are failing, this is because you have some defined variables/function that are not used. This is an issue it can't be automatically fixed by the pre-commit bot, so you will need to do it manually. You can find what's causing the issue if you check the failing test (https://github.com/pybamm-team/PyBaMM/actions/runs/11345431722/job/31553629641?pr=4516) and scroll down (you need to start reading at line 46).

Hi @brosaplanella,
I've addressed the style issues, and now the remaining problem is with the unit tests. Although multiple tests are failing, they all stem from two types of errors:

AttributeError: 'set' object has no attribute 'values'
AttributeError: 'ReactionDriven' object has no attribute 'phase_name'
Could you advise on how I should proceed with resolving these? Thank you!

Hi! The latter is because the ReactionDriven porosity model (reaction_driven_porosity.py) is not available for composite materials, that's why it breaks. I need to dig a bit more regarding the first issue.
BTW, it's better to not force push. I believe the issue you encountered is that the pre-commit bot made some style changes. In those cases you have to pull first and then push.

Hi! The latter is because the ReactionDriven porosity model (reaction_driven_porosity.py) is not available for composite materials, that's why it breaks.

I made a PR that fixes this, which Sunil is already using (he requested it). Go to this branch of my fork of PyBaMM and merge the changes into your branch.

Thank you @DrSOKane; merging reaction_driven_porosity from your branch and significant reduced the number of errors.
The errors now are:

AttributeError: 'set' object has no attribute 'values'
AttributeError: 'ReactionDriven' object has no attribute 'phase_name'
Can this be re-scoped to self.phase_name??
pybamm.expression_tree.exceptions.ModelError: Missing variable for submodel 'porosity': 'Negative total SEI thick...'
Failed: DID NOT RAISE <class 'pybamm.expression_tree.exceptions.OptionError'>


Install-ISHDotNetHosting - Prerequisite for 14.0.3

Install-ISHDotNetHosting - Prerequisite for 14.0.3
.NET Core 3.1 (Hosting Bundle) is also a requirement for 14.0.3

#134  - Revert "Install-ISHDotNetHosting for 14.0.3"
Reverted since .NET Core 3.1 (Hosting Bundle) is no longer a requirement for 14.0.3


Feat: Add prefers-reduced-motion API implementation

Introduced use_prefers_reduced_motion function to create a reactive interface for detecting the user's reduced motion preference.
Updated documentation for use_preferred_contrast, use_media_query, and use_preferred_dark functions to include See also references.
Resolves #149

Good work! Thanks.


datasets

I want to train with my own dataset, but I don't know how to make a dataset similar to that in this article. I'd like to know how to make res101.mat and att.splits.mat files in XLSA file?

Much appreciation for your interest. You can use the pre-trained ResNet101 to get the res101.mat. The att_split.mat is the annotation from the corresponding dataset.

same question.I wonder if there is any code for this. I use the bert model to convert the caption of other public data sets into semantic features, but the vector value of the semantic features varies from time to time

same question.I wonder if there is any code for this. I use the bert model to convert the caption of other public data sets into semantic features, but the vector value of the semantic features varies from time to time

Perhaps you could check the way of using Bert. Or you can try CLIP text encoder. Hope this can help you.


Add support for test suite duration in test summary

I've verified that this rev parses the output correctly in the streaming-build:29 image with Rust 1.54.0.


RDAP notices/remarks bugfix, asn_description added, generate examples fixes/adds

Coverage remained the same at 100.0% when pulling 9e1613cb5d404a260508e51dd364460309149608 on dev into 9f101964fb18d5b65c6b36de9d16ee6d353d450b on master.


Float.fromInt should not trap on large values

Float.fromInt is currently implemented by going through Int64 and traps on larger values. Although documented, this is very surprising and unhelpful and should rather be fixed.
See forum.

The necessary primitives were added in dfinity/motoko#2733. Patch for motoko-base imminent.


Remove per-analysis logic from Ensemble

This PR is to start discussion. I would like to remove as much of the per-analysis logic as possible from the Ensemble class. This represents one possible way to do this, but I'm not sure it is the best.
Create helper functions to provide the required columns (args) and meta for each analysis. Use ColumnMapper to link these back to the correct columns in the Ensemble. This requires that the user does a little more set up to run the analysis.

We talked about this a bit, but to summarize here; I think there's a lot of value in what's being proposed from a maintainability standpoint. I'm not keen on the extra functions (such as meta_sf2, etc.) that are required to be imported and supplied. I think that users would benefit a lot from the Ensemble continuing to handle these things under the hood. So maybe an alternative approach is good? I know you had a few ideas, the one I proposed was to have the meta and required columns live in the analysis function files (as presented here), but continue to map them within ensemble.batch. This would alleviate some of the concern with the Ensemble object becoming too complex, as at least in this instance we modify the mappings within the analysis function file. But I'm happy with other approaches that keep the user feel at a similar level to how things are now.

Reverting pull request since this isn't the approach we are going to go with. Thanks for taking a look and the discussion.


Weather In Celcius

Hi, so i live in the UK and we read our weather in celcius rather than Fahrenheit. ive never developed an android app before this is my first thing. Probably  not the best idea but ive wanted to do this for ages. anyway, i got the weather api working perfectly im using the free trial of darksky. however, it shows the temperature in fahrenheit and not celcius. how do i change this? i had a look in a few places but couldnt work it out. am i being stupid or is it not possible XD
thanks

oh i've done it! in case anyone else wants to do this within the weather part you just add this to the end of the url: ?units=si
so happy when i figured this out XD
so this:
return String.format(Locale.US, "https://api.darksky.net/forecast/%s/%f,%f",
Becomes this:
return String.format(Locale.US, "https://api.darksky.net/forecast/%s/%f,%f"+"?units=si",

and thats all there is too it!


Compilation fails using gfortran ubuntu 22.04

Bug description
<OpenFast compilations fails when using Ubuntu 22.04 and gfortran 11.3. This bug was reported as 743 and 744 (https://github.com/OpenFAST/openfast/issues/743) in OpenFAST 2.5.1 but it appears to still be present in 3.5.2 >
To Reproduce
<configured with:
cmake .. -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS=ON -DBLAS_LIBRARIES="/usr/lib/x86_64-linux-gnu/libblas.so" -DLAPACK_LIBRARIES="/usr/lib/x86_64-linux-gnu/liblapack.so">
Steps to reproduce the behavior:

Compile with 'make -j12'
Error message: OpenFAST/modules/openfast-library/src/FAST_Solver.f90:3016:39:

2297 |                      CALL CleanUp()
|                                   2
......
3016 |             do nb=1,size(y_BD_perturb)
|                                       1
Error: Index variable ‘nb’ redefined at (1) in procedure ‘cleanup’ called from within DO loop at (2)
OpenFAST Version
<Version 3.5.2 Master branch>
**************************************************************************************************
 OpenFAST

 Copyright (C)  National Renewable Energy Laboratory
 Copyright (C)  Envision Energy USA LTD

 This program is licensed under Apache License Version 2.0 and comes with ABSOLUTELY NO WARRANTY.
 See the "LICENSE" file distributed with this software for details.
 **************************************************************************************************

 OpenFAST-v3.5.2
 Compile Info:
  - Architecture: 64 bit
  - Precision: double
  - Date: Feb 12 2024
  - Time: 17:19:38
 Execution Info:

System Information (please complete the following information):

OS: <e.g. Ubuntu 22.04
Compiler: <e.g. GFortran 11.3>
Compiler settings: <cmake .. -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS=ON -DBLAS_LIBRARIES="/usr/lib/x86_64-linux-gnu/libblas.so" -DLAPACK_LIBRARIES="/usr/lib/x86_64-linux-gnu/liblapack.so">

Additional context

@jantheron69, could you share the compilation errors from 3.5.2?  The line numbers above don't correspond with the 3.5.2 source code for FAST_Solver.f90.

Hi Andrew, here is the result of my git branch query:
git branch -a

master
remotes/origin/HEAD -> origin/master
remotes/origin/dev
remotes/origin/dev-unstable-pointers
remotes/origin/main
remotes/origin/master
remotes/origin/rc-3.5.2

The line numbers are as I pasted in the bug report. Here again:
2297 |                      CALL CleanUp()
|                                   2
......
3016 |             do nb=1,size(y_BD_perturb)
|                                       1
Error: Index variable ‘nb’ redefined at (1) in procedure ‘cleanup’ called from within DO loop at (2)
make[2]: *** [modules/openfast-library/CMakeFiles/openfast_postlib.dir/build.make:114: modules/openfast-library/CMakeFiles/openfast_postlib.dir/src/FAST_Solver.f90.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:1490: modules/openfast-library/CMakeFiles/openfast_postlib.dir/all] Error 2
make: *** [Makefile:136: all] Error 2
Do I explicitly have to pull branch "rc-3.5.2"?

The master branch was removed a few years ago.  So what you have in your master branch is likely from the last release before we renamed master to `main.
For version 3.5.2, you need to use the main branch, or the v3.5.2 tag.
The branch rc-3.5.2 was removed after we posted the 3.5.2 release.

Thanks Andrew! That worked. Maybe put something like this in the compile instructions for Linux? Or maybe I missed it?

Excellent!  Good to hear that worked.
The issue is more of a git usage issue than OpenFAST.  I'll think about what to add to the  docs

[like]  Theron, Johannes Nicolaas reacted to your message:

From: Andy Platt @.>
Sent: Monday, February 12, 2024 7:56:40 PM
To: OpenFAST/openfast @.>
Cc: Theron, Johannes Nicolaas @.>; Mention @.>
Subject: Re: [OpenFAST/openfast] Compilation fails using gfortran ubuntu 22.04 (Issue #2030)
Excellent! Good to hear that worked.
The issue is more of a git usage issue than OpenFAST. I'll think about what to add to the docs
—
Reply to this email directly, view it on GitHubhttps://github.com/OpenFAST/openfast/issues/2030#issuecomment-1939457339, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AS7EVWR5VIOQWMKQRTFRE63YTJXXRAVCNFSM6AAAAABDEMD54WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZZGQ2TOMZTHE.
You are receiving this because you were mentioned.Message ID: @.***>

Have a good day; thanks for your super fast response


Crash on starting

https://gist.github.com/gollariel/4a0496d04bb8fcaa458263bdfc7ba4ce

fixed. will be pushed in new update


Can no longer open image files from the git viewlet

fixes #33739
The SCM viewlet is always using window.showTextDocument when clicking on a file in the list of outgoing changes, however this will fail with an error if the file is binary. Previously it was using the vscode.open command which handled this nicely. However, that was changed via https://github.com/Microsoft/vscode/commit/c0381f2b62b9bf1b3d81f9f88b82a9eb5bd873dc to support more options when opening actual text files.
This fix adds TextDocumentShowOptions to the vscode.open command so that binary files can also be opened.
I realize we had this request going on already via https://github.com/Microsoft/vscode/pull/30675 but at that time I did not see the issue with binary files.

We can't keep going back and forward on commands vs API. What's the right way to do this?

@joaomoreno @jrieken showTextDocument makes no sense for an extension that is capable of opening non text documents. Imho there is no good API right now other than vscode.open to handle binary files, unless we want to make the GIT extension check for binary file type.


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/OPS-E2E-PPE/docs-archive-test-source

Docs Build status updates of commit 2147302:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Release_Archive_master_2020-03-11-03-30-14 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Release_Archive_master_2020-03-11-03-30-14

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


trap FAT32 disk WriteAt errors

Fix for untrapped errors raised by FAT32 disk (mentioned in https://github.com/diskfs/go-diskfs/issues/130).

I prefer the idiomatic
			if _ , err := file.WriteAt(p[0:toWrite], int64(offset)+fs.start); err != nil {
 				return totalWritten, fmt.Errorf("Unable to write to file: %v", err)
 			}

But I wouldn't hold it up for that.

Me too! But I forced myself to use the existing style within the code ;). Feel free to change it as you please.


Capture Comments on a page

Options
zoomerang, email, database, github issuse

I'll move this to the website repo at some point

 A

Accidentally closed

Reopened

Moved to website