docs: type hinting and docstrings in molstruct

This was really bugging me while refactoring query, so did a separate extra PR for it.

I left minor comments, more for me to understrand than for suggesting changes. I removed the duplicated comments, but in case we decide to change something we need to remember that it may be in multiple files.

Sorry, I was actually meaning to leave references to some of these changes when I made the PR, but then forgot :)
I added them now in reply to your comments

3 additional changes:

I used from __future__ import annotations to avoid the quotation marks around some of the type hints
I improved docstrings and their formatting according to this convention: https://realpython.com/documenting-python-code/#class-docstrings.
I moved SingleResidueVariant into residue.py as they are closely related classes.

I even wonder if it would make sense to make it a child class of Residue instead of taking the Residue as an attribute (but that would require more coding than I am currently willing to do for this).

You should be able to go through the commits one by one to see each change in isolation, which might make reviewing easier.

3 additional changes:

I used from __future__ import annotations to avoid the quotation marks around some of the type hints

I improved docstrings and their formatting according to this convention: https://realpython.com/documenting-python-code/#class-docstrings.

I moved SingleResidueVariant into residue.py as they are closely related classes.

I even wonder if it would make sense to make it a child class of Residue instead of taking the Residue as an attribute (but that would require more coding than I am currently willing to do for this).

You should be able to go through the commits one by one to see each change in isolation, which might make reviewing easier.
Note that because I have "automatic import sorting upon save" turned on, some additional imports are switched around as well.

Regarding 3., JFYTK, we're using the Google Style convention for docstrings.

3 additional changes:

I used from __future__ import annotations to avoid the quotation marks around some of the type hints

I improved docstrings and their formatting according to this convention: https://realpython.com/documenting-python-code/#class-docstrings.

I moved SingleResidueVariant into residue.py as they are closely related classes.

I even wonder if it would make sense to make it a child class of Residue instead of taking the Residue as an attribute (but that would require more coding than I am currently willing to do for this).

You should be able to go through the commits one by one to see each change in isolation, which might make reviewing easier.
Note that because I have "automatic import sorting upon save" turned on, some additional imports are switched around as well.

Regarding 3., JFYTK, we're using the Google Style convention for docstrings. Nice that you moved SingleResidueVariant into residue.py, makes more sense. Regarding the possibility of making it a child of Residue, that also makes sense, not sure how much it's worth to spend time on doing it

Thanks for the ref to google convention. It does still follow that as well. I wasn't sure whether the class itself should get a docstring or only the init method. But in both style guides, they each get a docstring.


Post duplicated on app, not online

Shake to reload does not change this

Timestamps: tue nov 24 9:45a and 11:23a

When tapping share, both posts have same link
https://d1w3fhkxysfgcn.cloudfront.net/linda/2015-11-24T04:15:41.938Z

Could the post be created twice on app with retryFailedOperations?


Enable component async loading

What problem does this feature solve?
For now there is no full support for vue async components described here:
https://vuejs.org/v2/guide/components-dynamic-async.html#Handling-Loading-State
Solution presented in:
https://github.com/vuejs/vue-router/pull/2140
https://github.com/chrisvfritz/vue-enterprise-boilerplate/blob/master/src/router/routes.js
is solving problem only partially because of such construction beforeRouteEnter etc guards are not launched due to fact that component is resolved inside another component after route update
This problem is also mentioned here:
https://forum.vuejs.org/t/vue-router-async-component-loading-error-components-never-shown/40618/2
What does the proposed API look like?
Update doc with information that this syntax is not working with vue-router.

If as you said in https://github.com/vuejs/vue-router/pull/2140/files#r298066005 , the navigation guards do not work, provide a boiled down repro to show your point

https://codesandbox.io/s/vue-template-971d5
Go to the default path:

Loader component is mounted
beforeRouteEnter guard is not triggered
Target Component is mounted

Go to /component path:

Loader component is not mounted
beforeRouteEnter guard is triggered
Target Component is mounted

Due to docs syntax used in /component path should work fine but is not working properly.
Wrapping target Component into functional render component cause to vue-router ignore route guards.

Ah, I see now. Let me explain what happens: The loader only appears after navigation is confirmed, while the network request is waiting for the component. This is exactly what we want for guards, the whole point is to not use the component if the navigation is cancelled, which could eventually prevent a network request as well

So you can't handle component loading in vue-router the way described in documentation.

So how achieve displaying loading during request for component and don't lose navigation guards?

I found one solution:
https://stackoverflow.com/questions/44886812/how-to-display-a-loading-animation-while-a-lazy-loaded-route-component-is-bein
But I think we should be able to do such thing as handling loading without usage of vuex and modifing Root component.

There is an example about handling the waiting state in between navigations at https://github.com/chrisvfritz/vue-enterprise-boilerplate/blob/master/src/router/index.js
It's something that will improve in next version and we also need to provide a better documentation for that topic

Thank you. Good to hear that this will be improved in next version :)

https://codesandbox.io/s/vue-template-bys6q
I tried to handle loading by beforeEach and afterEach as you described but it's not working in proper way. Because vue-router is mounting Root element after resolving all hooks so after resolving child components.

Yeah, that's because in the root Vue, you are displaying the router-view component. Instead of having the loading logic inside of your view component Root.vue, it should be at the root component. Like the example in the cli or in docs where we mount an App.vue component. That component is always displayed so you can display the logic there

So I have to display whole page loader? If I have several components like Root.vue mounted for higher paths and want display loader only on updated part of website can I do that some way?


Dates are really, really broken.

The Issue
Steps to reproduce

Go to All content
Set filter to newest
Enjoy

Expected behaviour
Tell us what should happen
The dates should be recent
Actual behaviour
Tell us what happens instead
The dates are over 50,000 years in the future
System Configuration

Device: Google Pixel 2
Android version: 11

Anything Else

Screenshots
<!-- If a screenshot would help explain the bug, please include one or two here
Once it's not 2 am and i can use my computer without waking anyone up ill add them cause github mobile does not let you add images

## Internal Use

### Acceptance Criteria
1.
2.
3.

### Definition of Done
- [ ]  Tested against acceptance criteria
- [ ] Tested against the assumptions of the user story
- [ ] The project builds without errors
- [ ] Unit tests are written and passing
- [ ] Tests on devices/browsers listed in the issue have passed
- [ ] QA performed & issues resolved
- [ ] Refactoring completed
- [ ] Any configuration or build changes documented
- [ ] Documentation updated
- [ ] Peer Code Review performed

Which app version?

I put it in but it did not show

0.17

Also seeing this on 0.17, Android 10:

This could be caused by the SDK not rejecting a release_time of something that the app itself reports as "Invalid date" on the front end (but the video is able to be viewed). I tested this by passing  --release_time=99999999999999 to the lbrynet app on Linux.


CreateQueue fails when attributes aren't passed but are changed from default

https://github.com/adamw/elasticmq/blob/master/rest/rest-sqs/src/main/scala/org/elasticmq/rest/sqs/CreateQueueDirectives.scala#L47
CreateQueue doesn't take into consideration when attributes aren't passed in the request but have been changed from the defaults.  This differs from AWS SQS behavior.  If attributes aren't passed, they should not be considered in determining whether the queue name exists exception is thrown.

Ah :) maybe you could try writing a PR? thanks!


[Improvements] Camera

Add new features to camera as per :

Allow to set either by Interest(LookAt as now), Orientation (for pinhole simulations), Direction
Allow to switch between perspective and ortho (ortho is important for shadow maps).
Fov to be configurable (Also allow focal length instead, which is more widely used).
Aspect Ratio should be optional (enabled by default), some cases require to disable it.
Near / Far should be configurable (can drastically improve some post proc, needed to fit shadow maps too)
Lens shift (extremely useful for projector simulation).
Allow to set a custom view/projection matrix (can always derive back most parameters from it).
Allow to work in reverse depth mode
Add Coc factors (Depth of field)

Some excellent suggestions here.
I'm not sure how to break this up between different operators and context, yet.

I slightly edited and sorted the task.


Under Night In-Birth Exe:Late(st) [PCSE01144]

App summary

App name: Under Night In-Birth Exe:Late(st)
App serial: PCSE01144
App version: 1.00

Vita3K summary

Version: v0.1.8
Build number: 3158
Commit hash: https://github.com/vita3k/vita3k/commit/[60a68325]
CPU backend: Dynarmic
GPU backend: Vulkan

Test environment summary

Tested by: JackMonty
OS: Windows 10
CPU: AMD Ryzen 5 Pro 3500U
GPU: Nvidia Geforce GT1030
RAM: 32 GB

Issues
Game runs with good speed on Vulkan. Audio crackles when characters speak  in story segments. There is some slight graphical corruption \ flashes that occur on menus, story scenes and a little during fights - they disappear in split seconds though so don't affect game-play. No graphics glitches when running under OpenGL but the game runs too slowly.
Screenshots
Title

Story Mode

Story Mode - Graphics Glitch

Gameplay

Log
vita3k.log
Recommended labels

Playable
Graphics Bug
Audio Bug

i was eagerly waiting for this game to become playable. but it's not. the problem is the loading times. it takes almost 30 minutes to enter the game, choose a mode, choose a character and finally start a match. It's unbearable!!! Please fix this. When i webt to play i only made one match and i quit immmediatly. With these loadings it's impossible to play the game. i think you put playable to soon!!!

Hello @Megapedro,
It loads very quickly for me - like within a few seconds - what settings are you using and do you have a log file?

i iam playingbon mobile but i have a pocco with snapdragon and 6gb of ram. it's enough. the settings i am playing with vulkan, fix fxaa, and anisotropic x2, resolution x2

i am hearing that some people are having problems with the new version of the emulator in some games...problems that they havn't before. Version 5 that came 2 weeks ago. And they had to go to version 4 again for the games to workout again. There's a chance that might be it?

Hi @Megapedro,
Thanks for the extra details - this was tested using the PC version of Vita 3k so I think that will make a big difference! I did use one of the latest releases at the time - I think the key difference is in platform but I will let the Devs comment on that - it loads fast for me on a PC...

maybe that's the problem. it's not playeble in mobile! but all of the game that appears playable in here i playbthem on mobile without problems. only this is giving me headaches. Tanks for the answer.

any word if this is already playable on android?

Problems on Android: Half of the Stages are pure Glitch and Laggy. Loadings are faster but still slow ( 1 Minute ). Music is Glitchy in some parts. But the problem is the game crashing every 10 minutes. You can't play Arcade because of the stages and you can't play Chronicles, Tutorial, Mission, Training, Etc, because every 10 minutes you get kicked out of the app and have to start it again.
The only Playable thing in this game on Mobile is the versus mode and only if you don't choose some Stages. I can't explain but if the game is constantly loading, it doesn't crash so often and you can play for some hours before it happen.
Please Fix it, i love this game so much and this is the only place i'm capable of playing it.

RE-TESTED ON PC
App summary

App name: Under Night In-Birth Exe:Late(st)
App serial: PCSE01144
App version: 1.00

Vita3K summary

Version: v0.2.0
Build number: 3690
Commit hash: https://github.com/vita3k/vita3k/commit/[f0285143]
CPU backend: Dynarmic
GPU backend: Vulkan

Test environment summary

Tested by: JackMonty
OS: Windows 10
CPU: AMD Ryzen 5 Pro 3500U
GPU: Nvidia Geforce GT1030
RAM: 16 GB

Issues
Game runs pretty much perfect now under Vulkan. No more audio problems or graphical text glitches or flashes in fighting scenes. OpenGL still causes the game to lag a little bit so best played on Vulkan.
Screenshots
Working Text on Vulkan

Working Text on Vulkan

Recommended labels

Remove Graphics Bug
Remove Audio Bug


Breaks on Kotlin 1.1 beta

If I have Kotlin set to version 1.1.0-beta-38 I get the following error.

e: Some runtime JAR files in the classpath have an incompatible version. Remove them from the classpath or pass the correct '-language-version' explicitly. Alternatively, you can use '-Xskip-runtime-version-check' to suppress this error
.....gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-reflect/1.0.6/3d499d3b7768f88c4796e5a1e357933e11a8936d/kotlin-reflect-1.0.6.jar: Runtime JAR file has version 1.0 which is older than required for language version 1.1

Setting Kotlin back to 1.0.6 solves the problem. Would be nice to get a release of this updated for kotlin-reflect-1.1.

I'm waiting for the 1.1.0 release before releasing any Mockito-Kotlin versions that depend on non-final versions of Kotlin.
Instead, you can use the following to overcome the issue, in your root's build.gradle:
allprojects {
    configurations.all {
        resolutionStrategy {
            forcedModules = ["org.jetbrains.kotlin:kotlin-stdlib:1.1.0-beta-38", "org.jetbrains.kotlin:kotlin-reflect:1.1.0-beta-38"]
        }
    }
}

Ah good point. Thanks for the workaround tip!


feat (Twilio): add window functions to dedupe for each hashid

(still need to test this locally)

@jitoquinto @kanelouise @royconst wacky day I know, but would love to get some 👀 on this so we can hopefully merge in before tomorrow's run!


swift-2.0 branch generating many errors (Alamofire issues)

Tried to pull the latest swift-2.0 into Xcode 7 GM and getting lots of compiler errors, such as "#" having been removed from Swift.

That's odd. How are you installing it? You'll need to manually point to Alamofire's Swift 2 branch in your podfile. It's working for me with this one: https://github.com/artsy/eidolon/blob/master/Podfile

Tried a few different things, starting with the swift-2.0 branch README.md... obviously out of date.
After updating to:
pod 'Box', :head
pod 'Result', :head
pod 'Alamofire', :git => 'https://github.com/Alamofire/Alamofire.git', :branch => 'swift-2.0'
pod 'ReactiveCocoa', :git => 'https://github.com/ashfurrow/ReactiveCocoa.git', :branch => 'swift2'
pod 'Moya/ReactiveCocoa', :git => 'https://github.com/Moya/Moya.git', :branch => 'swift-2.0'

It is healthier – seems to be down to two compile errors (versus the dozens prior to the change):
CompileSwift normal x86_64 /Users/zbeckman/Projects/Glimpulse/iOS/project/Glimpulse/Pods/Moya/Moya/ReactiveCocoa/Moya+ReactiveCocoa.swift
    cd /Users/zbeckman/Projects/Glimpulse/iOS/project/Glimpulse/Pods
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift -frontend -c /Users/zbeckman/Projects/Glimpulse/iOS/project/Glimpulse/Pods/Moya/Moya/Endpoint.swift -primary-file /Users/zbeckman/Projects/Glimpulse/iOS/project/Glimpulse/Pods/Moya/Moya/ReactiveCocoa/Moya+ReactiveCocoa.swift /Users/zbeckman/Projects/Glimpulse/iOS/project/Glimpulse/Pods/Moya/Moya/Moya.swift /Users/zbeckman/Projects/Glimpulse/iOS/project/Glimpulse/Pods/Moya/Moya/ReactiveCore/MoyaResponse.swift /Users/zbeckman/Projects/Glimpulse/iOS/project/Glimpulse/Pods/Moya/Moya/ReactiveCocoa/RACSignal+Moya.swift -target x86_64-apple-ios8.2 -enable-objc-interop -sdk /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.0.sdk -I "/Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Products/QA 1-iphonesimulator" -F "/Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Products/QA 1-iphonesimulator" -g -import-underlying-module -module-cache-path /Users/zbeckman/Library/Developer/Xcode/DerivedData/ModuleCache -D COCOAPODS -serialize-debugging-options -Xcc "-I/Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Intermediates/Pods.build/QA 1-iphonesimulator/Moya.build/swift-overrides.hmap" -Xcc -iquote -Xcc "/Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Intermediates/Pods.build/QA 1-iphonesimulator/Moya.build/Moya-generated-files.hmap" -Xcc "-I/Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Intermediates/Pods.build/QA 1-iphonesimulator/Moya.build/Moya-own-target-headers.hmap" -Xcc "-I/Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Intermediates/Pods.build/QA 1-iphonesimulator/Moya.build/Moya-all-non-framework-target-headers.hmap" -Xcc -ivfsoverlay -Xcc /Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Intermediates/Pods.build/all-product-headers.yaml -Xcc -iquote -Xcc "/Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Intermediates/Pods.build/QA 1-iphonesimulator/Moya.build/Moya-project-headers.hmap" -Xcc "-I/Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Products/QA 1-iphonesimulator/include" -Xcc -I/Users/zbeckman/Projects/Glimpulse/iOS/project/Glimpulse/Pods/Headers/Private -Xcc -I/Users/zbeckman/Projects/Glimpulse/iOS/project/Glimpulse/Pods/Headers/Private/Moya -Xcc -I/Users/zbeckman/Projects/Glimpulse/iOS/project/Glimpulse/Pods/Headers/Public -Xcc "-I/Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Intermediates/Pods.build/QA 1-iphonesimulator/Moya.build/DerivedSources/x86_64" -Xcc "-I/Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Intermediates/Pods.build/QA 1-iphonesimulator/Moya.build/DerivedSources" -Xcc -DQA_1=1 -Xcc -DCOCOAPODS=1 -Xcc -ivfsoverlay -Xcc "/Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Intermediates/Pods.build/QA 1-iphonesimulator/Moya.build/unextended-module-overlay.yaml" -Xcc -working-directory/Users/zbeckman/Projects/Glimpulse/iOS/project/Glimpulse/Pods -emit-module-doc-path "/Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Intermediates/Pods.build/QA 1-iphonesimulator/Moya.build/Objects-normal/x86_64/Moya+ReactiveCocoa~partial.swiftdoc" -O -module-name Moya -emit-module-path "/Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Intermediates/Pods.build/QA 1-iphonesimulator/Moya.build/Objects-normal/x86_64/Moya+ReactiveCocoa~partial.swiftmodule" -serialize-diagnostics-path "/Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Intermediates/Pods.build/QA 1-iphonesimulator/Moya.build/Objects-normal/x86_64/Moya+ReactiveCocoa.dia" -emit-dependencies-path "/Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Intermediates/Pods.build/QA 1-iphonesimulator/Moya.build/Objects-normal/x86_64/Moya+ReactiveCocoa.d" -emit-reference-dependencies-path "/Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Intermediates/Pods.build/QA 1-iphonesimulator/Moya.build/Objects-normal/x86_64/Moya+ReactiveCocoa.swiftdeps" -o "/Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Intermediates/Pods.build/QA 1-iphonesimulator/Moya.build/Objects-normal/x86_64/Moya+ReactiveCocoa.o"

/Users/zbeckman/Projects/Glimpulse/iOS/project/Glimpulse/Pods/Moya/Moya/ReactiveCocoa/Moya+ReactiveCocoa.swift:37:66: error: value of type 'ErrorType' has no member 'domain'
                            subscriber.sendError(NSError(domain: error.domain, code: statusCode, userInfo: error.userInfo))
                                                                 ^~~~~ ~~~~~~
/Users/zbeckman/Projects/Glimpulse/iOS/project/Glimpulse/Pods/Moya/Moya/ReactiveCocoa/Moya+ReactiveCocoa.swift:39:50: error: cannot convert value of type 'ErrorType' to expected argument type 'NSError!'
                            subscriber.sendError(error)
                                                 ^~~~~

Ideas...?
By the way, what's the difference between your Alamofire branch and the Swift 2 master (Alamofire) branch? Can I safely point at the Alamofire URL or should I stick with your's for now...?
(Kind of looking for guidance on how to proceed now that Xcode 7 GM is out...)

Hmm. I'll have to look at that tomorrow. Might be a change with the GM.

Alamofire were very quick - they've already merged their Swift branch into master and deleted the Swift 2 branch. You just need to point at the master branch for Alamofire now.
I've submitted a PR for Moya which updates this.

Hmm. Still no good, I'm seeing the same error. Updated to use the latest AlamoFire. Here's the complete Podspec I'm using:
target 'Glimpulse', :exclusive => false do
        pod 'SwiftSpinner', :git => 'https://github.com/zbeckman/SwiftSpinner.git'
        pod 'XCGLogger', :git => 'https://github.com/DaveWoodCom/XCGLogger.git', :branch => 'swift_2.0'
        pod 'GRValidation', '~> 0.2'
        pod 'SwiftDate', :git => 'https://github.com/malcommac/SwiftDate.git', :branch => 'swift-2.0'
        pod 'DateTimeKit', :git => 'https://github.com/zbeckman/DateTimeKit.git'
        pod 'MagicalRecord'
        pod 'Box', :head
        pod 'Result', :head
        pod 'Alamofire', '~> 2.0'
        pod 'ReactiveCocoa', :git => 'https://github.com/ashfurrow/ReactiveCocoa.git', :branch => 'swift2'
        pod 'Moya/ReactiveCocoa', :git => 'https://github.com/Moya/Moya.git', :branch => 'swift-2.0'
end

(Realizing that, technically this looks like a Moya/ReactiveCocoa issue – I can create an issue over there if you would prefer).

I'm going to work on getting it all to work this afternoon with the Xcode 7 GM.

OK cool, so this is working for me (this PR).
@zbeckman Your podfile looks good to me. But you'll need to update things:
pod update Box Result Alamofire Moya/ReactiveCocoa

Let us know if that works :cake:

The code on this PR is working for me locally: https://github.com/artsy/eidolon/pull/504

I'm now pulling the following pods:
	pod 'Box', :head
	pod 'Result', :head
	pod 'ReactiveCocoa', :git => 'https://github.com/ashfurrow/ReactiveCocoa.git', :branch => 'swift2'
	pod 'Alamofire', '~> 2.0'
	pod 'Moya', :git => 'https://github.com/Moya/Moya.git', :branch => 'swift-2.0'

After adding Alamofire and Moya, I'm getting the following runtime error. This only seems to be happening after adding in Alamofire and Moya, but I'm still debugging.
If you see anything wrong with my config please let me know.
2015-09-11 01:48:07.648 XCTRunner[35507:240964] The bundle “GlimpulseUITests” couldn’t be loaded because it is damaged or missing necessary resources. Try reinstalling the bundle.
2015-09-11 01:48:07.648 XCTRunner[35507:240964] (dlopen_preflight(/Users/zbeckman/Library/Developer/CoreSimulator/Devices/FCFAAFBF-1AB4-4223-9BCC-CA91CBDE96DC/data/Containers/Bundle/Application/11F5D849-3061-4E91-A44C-F35AA544520A/GlimpulseUITests-Runner.app/PlugIns/GlimpulseUITests.xctest/GlimpulseUITests): Library not loaded: @rpath/libswiftCoreLocation.dylib
  Referenced from: /Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Intermediates/CodeCoverage/Glimpulse/Products/QA 1-iphonesimulator/ReactiveCocoa.framework/ReactiveCocoa
  Reason: image not found)

Oh no! I had a similar issue yesterday but I can't recall exactly what fixed it. You've tried the routine fixes like deleting derived data and resetting the simulator? Are there any compiler warnings that seem related?

Yes – all the routine fixes.
I'm very fuzzy on which pods I need to pull in... ReactiveCocoa, Alamofire, Moya, ReactiveMoya... And I'm pretty sure the README is quite out of date in this regard.
I'm able to get Moya to install – but, any attempt to bring in ReactiveCocoa fails.

Here is our working build of Moya + ReactiveCocoa - which generates this lockfile
pod 'Alamofire'
pod 'ReactiveCocoa', :git => 'https://github.com/ashfurrow/ReactiveCocoa.git', :branch => 'swift2'
pod 'Moya/ReactiveCocoa', :git => 'https://github.com/Moya/Moya.git', :branch => 'swift-2.0'

Should get you the right setup, if you have been using older references for these branches - you may need to pod install

I agree the README needs updating – I'll roll that into https://github.com/Moya/Moya/pull/214

Hm, OK – a little more info – the error I reported above:
2015-09-11 01:48:07.648 XCTRunner[35507:240964] The bundle “GlimpulseUITests” couldn’t be loaded because it is damaged or missing necessary resources. Try reinstalling the bundle.
2015-09-11 01:48:07.648 XCTRunner[35507:240964] (dlopen_preflight(/Users/zbeckman/Library/Developer/CoreSimulator/Devices/FCFAAFBF-1AB4-4223-9BCC-CA91CBDE96DC/data/Containers/Bundle/Application/11F5D849-3061-4E91-A44C-F35AA544520A/GlimpulseUITests-Runner.app/PlugIns/GlimpulseUITests.xctest/GlimpulseUITests): Library not loaded: @rpath/libswiftCoreLocation.dylib
  Referenced from: /Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Intermediates/CodeCoverage/Glimpulse/Products/QA 1-iphonesimulator/ReactiveCocoa.framework/ReactiveCocoa
  Reason: image not found)

Only seems to be a problem in the "iOS UI Testing Bundle" target type. (Unfortunately, this is where we do all our testing, so the outcome is that when we run tests, it immediately fails and nothing works – we just get the above error).

Also, if I only use:
pod 'Alamofire'
pod 'ReactiveCocoa', :git => 'https://github.com/ashfurrow/ReactiveCocoa.git', :branch => 'swift2'
pod 'Moya/ReactiveCocoa', :git => 'https://github.com/Moya/Moya.git', :branch => 'swift-2.0'

Then, I get compile errors as follows:
CompileSwift normal x86_64 /Users/zbeckman/Projects/Glimpulse/iOS/project/Glimpulse/Pods/Box/Box/Box.swift
    cd /Users/zbeckman/Projects/Glimpulse/iOS/project/Glimpulse/Pods

/Users/zbeckman/Projects/Glimpulse/iOS/project/Glimpulse/Pods/Box/Box/Box.swift:6:37: error: 'Printable' has been renamed to 'CustomStringConvertible'
public final class Box<T>: BoxType, Printable {
                                    ^~~~~~~~~
                                    CustomStringConvertible
/Users/zbeckman/Projects/Glimpulse/iOS/project/Glimpulse/Pods/Box/Box/Box.swift:31:10: error: 'toString' has been renamed to 'String'
                return toString(value)
                       ^~~~~~~~
                       String
Swift.toString:1:33: note: 'toString' has been explicitly marked unavailable here
@available(*, unavailable) func toString<T>(x: T) -> String
                                ^

CompileSwift normal x86_64 /Users/zbeckman/Projects/Glimpulse/iOS/project/Glimpulse/Pods/Box/Box/MutableBox.swift
    cd /Users/zbeckman/Projects/Glimpulse/iOS/project/Glimpulse/Pods
/Users/zbeckman/Projects/Glimpulse/iOS/project/Glimpulse/Pods/Box/Box/MutableBox.swift:8:51: error: 'Printable' has been renamed to 'CustomStringConvertible'
public final class MutableBox<T>: MutableBoxType, Printable {
                                                  ^~~~~~~~~
                                                  CustomStringConvertible
/Users/zbeckman/Projects/Glimpulse/iOS/project/Glimpulse/Pods/Box/Box/MutableBox.swift:25:10: error: 'toString' has been renamed to 'String'
                return toString(value)
                       ^~~~~~~~
                       String
Swift.toString:1:33: note: 'toString' has been explicitly marked unavailable here
@available(*, unavailable) func toString<T>(x: T) -> String
                                ^

(Hence, the addition of the pods for Box and Result from HEAD). However, once I add in those (fixing the compiler errors) – we end up back at the original problem where none of our tests work (the image not found error).

It would seem that if I build ReactiveCocoa using Carthage, and install it as directed (that is, drag the framework into my embedded binaries) – the problem changes. Now:
2015-09-11 21:15:50.796 XCTRunner[20612:2543548] (dlopen_preflight(/Users/zbeckman/Library/Developer/CoreSimulator/Devices/FCFAAFBF-1AB4-4223-9BCC-CA91CBDE96DC/data/Containers/Bundle/Application/7FD22288-32A0-419F-B0AF-54DE9143FDBB/GlimpulseUITests-Runner.app/PlugIns/GlimpulseUITests.xctest/GlimpulseUITests): Library not loaded: @rpath/libswiftCoreLocation.dylib
  Referenced from: /Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Intermediates/CodeCoverage/Glimpulse/Products/QA 1-iphonesimulator/Moya.framework/Moya
  Reason: image not found)

(Notice that now it's Moya that has library problems...)
I think this has something to do with the fact that I'm building &/or testing for iOS. And I found this, which I'm not sure what to make of: https://github.com/Carthage/Carthage#if-youre-building-for-ios.

I've been able to use CocoaPods to install Moya/ReactiveMoya without any problems on a fresh Xcode project (download it here). I did so using Xcode 7 GM and the following Podfile:
use_frameworks!

target 'Test' do

pod 'Result', :head
pod 'ReactiveCocoa', :git => 'https://github.com/ashfurrow/ReactiveCocoa.git', :branch => 'swift2'
pod 'Moya/ReactiveCocoa', :git => 'https://github.com/Moya/Moya.git'

end

@zbeckman If that isn't working for you on your existing project, could you try cleaning your build directory? Command-Shift-K should do it in Xcode. It could be that Xcode's forgotten its derived data cache is stale. Let us know if any of that helps.

Ok, so after a good bit of fiddling, I learned a few things.
I'm using Xcode 7 GM. I'm in the habit of clearing the project directory and derived data whenever anything odd happens (so, um... like hourly ;-).
First off, everything works just fine if I install ReactiveCocoa using Carthage (Swift 2 branch of course), and drag the framework into our project, in conjunction with the following pods (all required for a good build). In addition, I have SwiftCheck installed via Carthage:
# UX components
pod 'SwiftSpinner', :git => 'https://github.com/zbeckman/SwiftSpinner.git'

# Frameworks
pod 'MagicalRecord'
pod 'Alamofire'
pod 'Moya', :git => 'https://github.com/Moya/Moya.git', :branch => 'swift-2.0'

# Utility components
pod 'XCGLogger', :git => 'https://github.com/DaveWoodCom/XCGLogger.git', :branch => 'swift_2.0'
pod 'GRValidation', '~> 0.2'
pod 'DateTimeKit', :git => 'https://github.com/zbeckman/DateTimeKit.git'

I also learned that BrightFutures has an incompatible dependency (it requires Result 0.6.1 and ReactiveCocoa is now using 1.0.0 – which leads to a lot of problems... However, with RAC your probably don't need BrightFutures so hopefully this isn't an issue for anyone).
NOW. After getting all that figured out (and committed! It took forever so I don't want to lose this config), I gave our project a try with nothing except these pods (and, of course, I removed the Carthage install of RAC):
pod 'SwiftSpinner', :git => 'https://github.com/zbeckman/SwiftSpinner.git'
pod 'Result', :head
pod 'ReactiveCocoa', :git => 'https://github.com/ashfurrow/ReactiveCocoa.git', :branch => 'swift2'
pod 'Moya/ReactiveCocoa', :git => 'https://github.com/Moya/Moya.git'
pod 'XCGLogger', :git => 'https://github.com/DaveWoodCom/XCGLogger.git', :branch => 'swift_2.0'
pod 'GRValidation', '~> 0.2'

target 'GlimpulseTests', :exclusive => false do
	# Testing framework
	pod 'Nimble', :git => 'https://github.com/Quick/Nimble.git', :branch => 'swift-2.0'
	pod 'Quick', :git => 'https://github.com/Quick/Quick', :branch => 'swift-2.0'
end

Did the usual (clean project, delete derived data) – and it fails with the following output:
2015-09-12 20:20:32.726 XCTRunner[84436:3618319] (dlopen_preflight(/Users/zbeckman/Library/Developer/CoreSimulator/Devices/FCFAAFBF-1AB4-4223-9BCC-CA91CBDE96DC/data/Containers/Bundle/Application/EF1E312C-E955-45EE-B805-B86307D314A2/GlimpulseUITests-Runner.app/PlugIns/GlimpulseUITests.xctest/GlimpulseUITests): Library not loaded: @rpath/libswiftCoreLocation.dylib
  Referenced from: /Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Intermediates/CodeCoverage/Glimpulse/Products/QA 1-iphonesimulator/Moya.framework/Moya
  Reason: image not found)

Just for the heck of it (to make sure nothing is different) I tried:
pod 'Moya', :git => 'https://github.com/Moya/Moya.git'

But I think that initial name is just symbolic – anyhow, it didn't matter.
So bottom line – Still no good using the CocoaPod, but it's fine using Carthage from the original ReactiveCocoa repository.
I'm stumped...

I've never used Carthage and CocoaPods together before – not sure of how that'd work. What version of CocoaPods are you using? There's a similar issue in #216.

We've rearranged this repository since you initially had this problem. Could I ask you to try creating a new Xcode project, and pod install using the following pods? Please leave Carthage out so that we can narrow the problem down.
pod 'Result', :head
pod 'ReactiveCocoa', :git => 'https://github.com/ashfurrow/ReactiveCocoa.git', :branch => 'swift2'
pod 'Moya/ReactiveCocoa', :git => "https://github.com/Moya/Moya.git"

After pod installing, open the project in Xcode 7 GM and run the app. Hopefully it'll work (it's working for me).
If that doesn't work, please download this Xcode project which I've prepared. It works on my machine. If it doesn't on your machine, we'll have a better idea of where to look.
If that does work, we'll try the same approach on your library. If you could undo the changes made when you were troubleshooting using git, that would be helpful. If it still doesn't work, then it could be something specific about your project.
I'll continue looking for the solution on my end. Thanks for helping us figure out the problem! :cake:

I tried removing the Carthage install of ReactiveCocoa, and then updating with the pods you suggested:
pod 'Result', :head
pod 'ReactiveCocoa', :git => 'https://github.com/ashfurrow/ReactiveCocoa.git', :branch => 'swift2'
pod 'Moya/ReactiveCocoa', :git => "https://github.com/Moya/Moya.git"

I get the same problem, again, only on the UI testing target (regular test targets and the app itself seem to work fine):
2015-09-13 11:22:13.386 XCTRunner[29003:4857736] (dlopen_preflight(/Users/zbeckman/Library/Developer/CoreSimulator/Devices/FCFAAFBF-1AB4-4223-9BCC-CA91CBDE96DC/data/Containers/Bundle/Application/056B5BED-0B9F-41AB-A248-117BD6824748/GlimpulseUITests-Runner.app/PlugIns/GlimpulseUITests.xctest/GlimpulseUITests): Library not loaded: @rpath/libswiftCoreLocation.dylib
  Referenced from: /Users/zbeckman/Library/Developer/Xcode/DerivedData/Glimpulse-avhroqmcgyzbiecltqxshdpczkht/Build/Intermediates/CodeCoverage/Glimpulse/Products/QA 1-iphonesimulator/Moya.framework/Moya
  Reason: image not found)

I also took a look at your test project. There is an important different in regard to how we have our Podfiles set up, and possibly the resulting code:
My Podfile installs all of the common pods without including them in a target (that is, like this):
pod 'Moya'
pod 'OtherCommonStuff'

target 'UITests'
    pod 'Quick'
end

So, with that in mind, I started "upgrading" your Podfile, incrementally adding elements until I got a similar failure.
The first step was to adopt the above format. Then I added a few lines that were missing from yours, but present in my config (such as the iOS target). Finally, I added in my testing libraries.
This is what I ended up with:
platform :ios, '8.0'

source 'https://github.com/CocoaPods/Specs.git'

use_frameworks!

pod 'Result', :head
pod 'ReactiveCocoa', :git => 'https://github.com/ashfurrow/ReactiveCocoa.git', :branch => 'swift2'
pod 'Moya/ReactiveCocoa', :git => "https://github.com/Moya/Moya.git"

target 'TestTests' do
	pod 'Nimble', :git => 'https://github.com/Quick/Nimble.git', :branch => 'swift-2.0'
	pod 'Quick', :git => 'https://github.com/Quick/Quick', :branch => 'swift-2.0'
end

target 'TestUITests' do
	pod 'Nimble', :git => 'https://github.com/Quick/Nimble.git', :branch => 'swift-2.0'
	pod 'Quick', :git => 'https://github.com/Quick/Quick', :branch => 'swift-2.0'
end

And I get this result when the UI tests run:
2015-09-13 11:31:46.948 XCTRunner[32697:4885511] (dlopen_preflight(/Users/zbeckman/Library/Developer/CoreSimulator/Devices/A5E91AA9-62B2-43C9-9378-9FA9A3F5491D/data/Containers/Bundle/Application/B2691E9B-944A-49C7-8EF3-FE1CCB98D62B/TestUITests-Runner.app/PlugIns/TestUITests.xctest/TestUITests): Library not loaded: @rpath/libswiftCoreLocation.dylib
  Referenced from: /Users/zbeckman/Library/Developer/Xcode/DerivedData/Test-hbfuhujgtjfczffhoidfubqaazyo/Build/Products/Debug-iphonesimulator/Moya.framework/Moya
  Reason: image not found)

Great work! I'm having trouble with the Demo project in #216 too. After adding pods to the specific target in the Podfile, it's now working! This kind of stuff has always tripped me up – looping in @orta.

Same here! Ok, I updated our main project's Podfile as follows (specifically, I put the main target 'Glimpulse' back in, so now every pod is explicitly included in a target):
platform :ios, '8.0'
source 'https://github.com/CocoaPods/Specs.git'
use_frameworks!

target 'Glimpulse', :exclusive => false do
	# UX components
	pod 'SwiftSpinner', :git => 'https://github.com/zbeckman/SwiftSpinner.git'

	# Frameworks
	pod 'MagicalRecord'
	pod 'Result', :head
	pod 'ReactiveCocoa', :git => 'https://github.com/ashfurrow/ReactiveCocoa.git', :branch => 'swift2'
	pod 'Moya/ReactiveCocoa', :git => "https://github.com/Moya/Moya.git"

	# Utility components
	pod 'XCGLogger', :git => 'https://github.com/DaveWoodCom/XCGLogger.git', :branch => 'swift_2.0'
	pod 'GRValidation', '~> 0.2'
	pod 'DateTimeKit', :git => 'https://github.com/zbeckman/DateTimeKit.git'
end

target 'GlimpulseTests', :exclusive => false do
	# Testing framework
	pod 'Nimble', :git => 'https://github.com/Quick/Nimble.git', :branch => 'swift-2.0'
	pod 'Quick', :git => 'https://github.com/Quick/Quick', :branch => 'swift-2.0'
end

target 'GlimpulseIntegrationTests', :exclusive => false do
	# Testing framework
	pod 'Nimble', :git => 'https://github.com/Quick/Nimble.git', :branch => 'swift-2.0'
	pod 'Quick', :git => 'https://github.com/Quick/Quick', :branch => 'swift-2.0'
end

target 'GlimpulseUITests', :exclusive => false do
	# Testing framework
	pod 'Nimble', :git => 'https://github.com/Quick/Nimble.git', :branch => 'swift-2.0'
	pod 'Quick', :git => 'https://github.com/Quick/Quick', :branch => 'swift-2.0'
end

And it works!
Questions, though:
Notice that I am not including any of the following pods:
	#pod 'Box', :head
	#pod 'Result', :head
	#pod 'Alamofire'

So, are Result and Alamofire looped in through dependencies? Do we need to include these in our Podfile?
Thankfully this simplifies our Carthage setup too... just one project now (SwiftCheck) that doesn't do pods.

Great! I'm glad that's working.
Box is no longer required at all. Result seems to have been updated on Trunk, so we can remove it too. Same with Alamofire – used to need it specified for Swift 2 support, don't anymore.

BTW you can reduce test duplication by doing something like this.

Nice! Thanks for the tip.

Seems like this is resolved, I'm going to close the issue. Don't hesitate to reopen, or open a new issue, if you run into any further problems. Thanks again for your help! :100:


How to disable slidebox for a while?

I checked this document and found that disable-scroll doesn't work at all. Because I have many horizontal scrollable area on the screen and I want when I start to scroll on items I need to disable slidebox for a while to prevent windows and elements are scrolled at the time.

@ajoslin: Any specific reason for deprecating disableScroll instead of leaving the two options? Using the delegate for this seems to cause problems when having a slidebox inside a modal.


Error: Invariant failed - Cypress Build Fails -

Have you experienced this bug with the latest version of the template?
First time using this template
Steps to Reproduce

Forked repo.
Followed egghead.io tutorial.
Pushed to github.
Added SESSION_SECRET and DATABASE_URL  to Fly.io and Github.

Works locally but building fails in Cypress on invariant:
node_modules/tiny-invariant/dist/tiny-invariant.cjs.js:10
        throw new Error(prefix);
              ^
Error: Invariant failed
    at invariant (/home/runner/work/remixed/remixed/node_modules/tiny-invariant/dist/tiny-invariant.cjs.js:10:15)
    at getEnv (/home/runner/work/remixed/remixed/build/index.js:42:44)
   //...etc

Expected Behavior
That it builds and works
Actual Behavior
Fails on Cypress build in github.
> start:mocks
> binode --require ./mocks -- @remix-run/serve:remix-serve build binode ./mocks ./node_modules/dotenv/config @remix-run/serve:remix-serve build

🔶 Mock server running

/home/runner/work/remixed/remixed/node_modules/tiny-invariant/dist/tiny-invariant.cjs.js:10
        throw new Error(prefix);
              ^
Error: Invariant failed
    at invariant (/home/runner/work/remixed/remixed/node_modules/tiny-invariant/dist/tiny-invariant.cjs.js:10:15)
    at getEnv (/home/runner/work/remixed/remixed/build/index.js:42:44)
    at Object.<anonymous> (/home/runner/work/remixed/remixed/build/index.js:[49](https://github.com/Andrehatlo/remixed/actions/runs/3696328499/jobs/6259880586#step:9:50):14)
    at Module._compile (node:internal/modules/cjs/loader:11[55](https://github.com/Andrehatlo/remixed/actions/runs/3696328499/jobs/6259880586#step:9:56):14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1209:10)
    at Module.load (node:internal/modules/cjs/loader:1033:32)
    at Function.Module._load (node:internal/modules/cjs/loader:868:12)
    at Module.require (node:internal/modules/cjs/loader:10[57](https://github.com/Andrehatlo/remixed/actions/runs/3696328499/jobs/6259880586#step:9:58):19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at Object.<anonymous> (/home/runner/work/remixed/remixed/node_modules/@remix-run/serve/dist/cli.js:42:13)
http://localhost:8811 timed out on retry 91 of 3, elapsed 90307ms, limit 90000ms
Error: connect ECONNREFUSED <IP_ADDRESS>:8811

I have checked out the other closed issues regarding `` this issue and have edited the deploy.yml file with the following:
github/workflows/deploy.yml
- name: 🌳 Cypress run
        uses: cypress-io/github-action@v5
        with:
          start: npm run start:mocks binode --require ./mocks --require ./node_modules/dotenv/config -- @remix-run/serve:remix-serve build
          wait-on: "http://localhost:8811"
        env:
          PORT: "8811"

Hey @Andrehatlo, if you don't mind commenting back with how you fixed this issue, this will be very helpful for future travelers 🙏

Indeed, I'm having the same exact issue
Run cypress-io/github-action@v5
start server "npm run start:mocks command "npm run start:mocks"
current working directory "/home/runner/work/remix-project-lab/remix-project-lab"
waiting on "http://localhost:8811" with timeout of 60 seconds
/opt/hostedtoolcache/node/16.18.1/x64/bin/npm run start:mocks

> start:mocks
> binode --require ./mocks -- @remix-run/serve:remix-serve build

🔶 Mock server running

/home/runner/work/remix-project-lab/remix-project-lab/node_modules/tiny-invariant/dist/tiny-invariant.cjs.js:10
        throw new Error(prefix);
              ^
Error: Invariant failed
    at invariant (/home/runner/work/remix-project-lab/remix-project-lab/node_modules/tiny-invariant/dist/tiny-invariant.cjs.js:10:15)
    at Object.<anonymous> (/home/runner/work/remix-project-lab/remix-project-lab/build/index.js:155:35)
    at Module._compile (node:internal/modules/cjs/loader:1155:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1209:10)
    at Module.load (node:internal/modules/cjs/loader:1033:32)
    at Function.Module._load (node:internal/modules/cjs/loader:868:12)
    at Module.require (node:internal/modules/cjs/loader:1057:19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at Object.<anonymous> (/home/runner/work/remix-project-lab/remix-project-lab/node_modules/@remix-run/serve/dist/cli.js:42:13)
    at Module._compile (node:internal/modules/cjs/loader:1155:14)
http://localhost:8811 timed out on retry 91 of 3, elapsed 90236ms, limit 90000ms
Error: connect ECONNREFUSED <IP_ADDRESS>:8811

Locally npm run test:e2e:run and npm run test:e2e:dev run fine. Also npm run start:mocks and it changes port from 3000 to 8811 when setting the env variable locally.

Found other similar issues like https://github.com/alexreardon/tiny-invariant/issues/146 and https://github.com/remix-run/grunge-stack/issues/71, and the most likely culprit mentioned was missing environment variables. And indeed, that was my case as well.
In my case I was missing DATABASE_URL, SESSION_SECRET, and other project specific env variables.


[Quick Navigation] Quick Navigation modal doesn't resize on narrower viewports

Description
On narrower viewports (but still larger than mobile), the modal is clipped (see screenshot below).

Checklist
~- [ ] If possible, I've reproduced the issue using the main branch of this package.~ N/A, I reproduced this on a WIP demo https://sofiaromorales.github.io/swift-argument-parser/documentation/argumentparser

[X] This issue hasn't been addressed in an existing GitHub issue.

Expected Behavior
No response
Actual behavior
No response
Steps To Reproduce

Navigate to https://sofiaromorales.github.io/swift-argument-parser/documentation/argumentparser/
Invoke Quick Navigation
Reduce your viewport size to something narrow

Swift-DocC-Render Version Information
No response

\cc @sofiaromorales

addressed by  #396

addressed by #396

Can we add the issue's development to #396 and close this issue? @sofiaromorales

addressed by #396

Can we add the issue's development to #396 and close this issue? @sofiaromorales

This bug was resolved in #396, but only a project maintainer can close the issue \cc @mportiz08


Component/main button

main button design

MainButton (getting start) : 💯
MainPage : maybe resize "BLETCHER" ?? (would be more better if getting little bigger)
MainPage : if possible, appearing MainPage with animation (such as fade in animation?? with short time) would be looking awesome!  -exmaple

MainButton (getting start) : 💯
MainPage : maybe resize "BLETCHER" ?? (would be more better if getting little bigger)
MainPage : if possible, appearing MainPage with animation (such as fade in animation?? with short time) would be looking awesome!  -exmaple

I'll reflect your idea when working on the main page.


New ChromeRestClient can't use existing http seesion

In the previous version, it can use the http session to send request if user already login in another tab
Expected outcome
it should use existing http session to send request.
Actual outcome
Now it popup a window, and can't use http seesion to send request,
Versions
App: <IP_ADDRESS>-stable
Chrome: 49.0.2623.112
Platform: Windows (7)
Steps to reproduce

Duplicate of #487


scale spirals out of control when using the delta matrix

When using the scale gizmo it somehow moves the object along with scaling it. This causes it to thrash until it jumps off screen.

That's a serious issue! Can you please try to reproduce it with the sample app?

I can reproduce this issue on a recent build. All mt transforms are stored locally and every frame I calculate the absolute transform. Because of this, I used the delta matrix. Translation and rotation work properly but the scale in the delta matrix goes out of control

I'll take a look very soon! Thanks

I have a workaround for this one now.
ImGuizmo::Manipulate(
	&view.m[0][0],
	&proj.m[0][0],
	gizmoOperation,
	gizmoMode,
	&matrix.m[0][0],
	&deltaMatrix.m[0][0],
	currentSnap,
	&transform->getBoundsMutable().m_LowerBounds.x);

matrix *= transform->getParentAbsoluteTransform().Invert();

transform->setTransform(matrix);

The basic idea is that the matrix parameter is always having the absolute transform, which is indeed correct. So I convert matrix from world position to local coordinates by multiplying it by the inverse of the world transform of the object.

@CedricGuillemet Any update on this? Having the same issue on one of more recent builds (38825331d2c752365a5aa530665f2c62b3f28671).
Haven't really investigated the code, but what seems to be happening is that the delta matrix always contains a non-zero scale value, regardless of the scale gizmo being used or not. In my testing it returned a [1, 1, 1] scale despite me using the translation gizmo

In fact it seems like the entire delta scale is very broken. Firstly the delta matrix will always have a scale of [1, 1, 1] when doing translation and rotation.
Secondly when actually using the scale gizmo the delta matrix always contains a positive scale value, meaning the delta matrix can't be used for scaling down a transform, which seems strange to me, although it may be intended behaviour (if it is intended may I ask why?)

Alright so now that I've investigated the code it's pretty obvious why the delta matrix always has a scale of [1, 1, 1] when doing translation or rotation.
It's because e.g the deltaMatrixTranslation matrix is set to an identity matrix. This may require a separate issue, let me know and I can open a separate one!

@CedricGuillemet So I realized that I was handling the delta scale incorrectly. Apparently the correct way of doing the delta scale is to multiply my original scale with the delta scale.
Personally I think the delta scale should either be an actual delta, or it should be made very clear that the delta scale should be multiplied with the current scale.
It is slightly confusing considering that both translation and rotation is additive, not multiplicative. But this really should be a separate issue where we can discuss it so I'll stop spamming this issue 😅


User registration fails in group chat spec

The first two users always register fine, but the last user 'C' gets an error

Very weird, seems like C username fails, but userC works well


dump sdk?

When I click this button, the game freeze. Am I supposed to wait for a long time or? Btw, where would the sdk be dumped?

Yes. It will dump an il2cpp_dump.json you can parse or just read through. It's 1GB.


enable intel ipex cpu and xpu in python3.11

What does this PR do?

Fixes # (issue)
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[ ] Did you write any new necessary tests?

Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

@Narsil @ErikKaum please help review and merge.

https://github.com/huggingface/text-generation-inference/pull/2507 upgrade python3.10 to python3.11. so the cpu and xpu regression again
error like
"text-generation-router: error while loading shared libraries: libpython3.11.so.1.0: cannot open shared object file: No such file or directory"
This PR is to enable xpu cpu in python3.11

numa does not work with python3.10. so I replace with py-libnuma. also upgrade xpu to torch 2.3


Validate test/schema import format: Fixes #1685

Fixes Issue
Fixes #1685

Changes proposed

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.

@lampajr I just pushed another commit that produces a custom mapper, which is cached and reused as a CDI bean by default: https://github.com/Hyperfoil/Horreum/pull/1689/commits/7463f9409a65b6234d9f8cdc9474d99c42ae1215


[NO-TICKET] Update k256 to 0.11.0 in casper-types.

Created from the PR for tracking.

For consideration after 1.5 is released.


Blend mode add on iPad air 2

Expected Behavior
https://imgur.com/HCFUJz2
Current Behavior
On iPad air 2(A1566), it will be like below.
https://imgur.com/a/djIvp6A
Should not showing black rect.
Possible Solution
In my case, I can use blend setting below to solve it temporary.
[gl.ONE, gl.ONE, gl.ONE, gl.ONE_MINUS_SRC_ALPHA]
Steps to Reproduce
please try https://drive.google.com/open?id=1zjJ6shjbDylhPL9nWGIGwEHk49en_kJn
Environment

pixi.js version: v5.0.2
Browser & Version: Safari and Chrome
OS & Version: iPad air 2  OS version: 12.1.4

PC chrome(74.0.3729.131), android device and some iOS device do not have this issue.

Duplicate of #5673 and #5446 , both are because our ADD is the same as in Adobe Flash.
Workaround: yes, what you said.
I believe we have to add one more ADD blendMode, however i dont know whether to choose
[gl.ONE, gl.ONE, gl.ONE, gl.ONE_MINUS_SRC_ALPHA] or [gl.ONE, gl.ONE]. The biggest problem is the name. Any ideas?

Oh, wait, sorry, its different. Maybe continuation of #5563 . Something about artifacts on iPad.

@hsienwei Could you let us know if the latest verison of PixiJS fixes this for you? Thanks!

Test in iPad air 2 with pixi.js version v5.1.1.  Issue fixed.


nsight-systems-cli: add recipe

Add recipe for installing libraries and tools of Nvidia Nsight Systems CLI.
Signed-off-by: Ilies CHERGUI<EMAIL_ADDRESS>

Tests are done on Jetson Xavier AGX and Nano (eMMC verison)
Here is interesting logs when using the Nsight systems CLI

The nsight-systems-cli recipe provide 2 main packages: nsight-systems-cli and nsight-systems-cli-qdstrmimporter
If only nsight-systems-cli is installed within the image the result's files from the nsight systems CLI have an extension *.qdstrm
Example:

root@jetson-nano-devkit-emmc:~# /opt/nvidia/nsight-systems-cli/2020.5.3/bin/nsys profile --output /tmp/deviceQuery.log --show-output false /usr/bin/cuda-samples/deviceQuery
Collecting data...
Processing events...
Saving temporary "/tmp/nsys-report-1268-251d-5651-84ac.qdstrm" file to disk...

Creating final output files...
Report file moved to "/tmp/deviceQuery.log.qdstrm"

root@jetson-nano-devkit-emmc:~#

when installing the packagensight-systems-cli-qdstrmimporter the result's files  have an extension *.qdrep as illustrate the above examples.

To be clear, is the qdstrmimporter required to run the nsight gui and start/run/analyze profiling sessions from a host computer?

To be clear, is the qdstrmimporter required to run the nsight gui and start/run/analyze profiling sessions from a host computer?

No, the Nsight systems GUI have this tool integrated in the host package NsightSystems-linux-public-2<IP_ADDRESS>-0256620.deb.


Run in java container like marketplace does

Description
Change sonarqube to use Java 11 container
Fixes # THEEDGE-2473
Type of change
What is it?

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[X] Refactor

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I run make pre-commit to check fmt/vet/lint/test-no-fdo

For reference https://github.com/RedHatInsights/marketplace-processor/pull/106/files to compare with marketplace


feat: add cardBin to card change event

Description

Adds cardBin to CardChangeEvent

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

[x] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix can't migrate title with double quotes

This change escapes double quotes in the GitHub issue title argument.
This is a workaround for a quirk in PowerShell where CLI arguments expecting quotes are mangled. See https://github.com/cli/cli/issues/3425 and https://stackoverflow.com/questions/6714165/powershell-stripping-double-quotes-from-command-line-arguments.

Fantastic, and interesting use case I had not thought of! 🎉


Windows Support

See Win32::Console::ANSI on P5 for inspiration.

The module works as is under git bash, but not powershell/CMD. (on the latter two, the case of the builtins seems to require uppercase, and then it generates Invalid attribute name '←[1m'

https://metacpan.org/pod/Win32::Console::ANSI


[release/3.1] Update to 3.1.100 rtm sdk

#bugnumber

#bugnumber

Not sure.  It's directly related to the file timestamp issue with nuget pack.


ActiveRecord adapter unavailable from flipper/adapters/active_record

The example shown here uses the following to import the ActiveRecord adapter: require 'flipper/adapters/active_record'
However, using this in code results in an uninitialized constant Flipper::Adapters::ActiveRecord error. Additionally, executing Flipper::Adapters.constants in the Rails console results in the following:
=> [:Memoizable, :Memory]
Visiting this page in the docs directory instructs the user to install the flipper-active_record gem instead.
How come the ActiveRecord adapter is not accessible via flipper/adapters/active_record as shown in the example, when the class is clearly present in the source? Alternatively, why does a separate part of the documentation specify the need to install a separate gem? Where is the source for that specific gem?

@Orbyt that's a great question!  Thanks for the super descriptive issue.
How come the ActiveRecord adapter is not accessible via flipper/adapters/active_record as shown in the example, when the class is clearly present in the source?
All of the source code lives in this repository, but you'll notice in the root directory there are multiple
.gemspecs so that each adapter can be packaged separately.
e.g.

flipper-active_record.gemspec
flipper-redis.gemspec
flipper-mongo.gemspec

Flipper users explicitly install the adapters they need to use.  This way an ActiveRecord user that has no need for a mongo adapter doesn't download all of the mongo code.
If you're curious how this works you can take a look at the flipper.gemspec#L13 and notice that all other gemspecs are ignored when packaging the flipper gem.
executing Flipper::Adapters.constants in the Rails console results in the following:
=> [:Memoizable, :Memory]
The Memoizable, and Memory adapters are not packaged as separate gems and are included when you gem install flipper - they don't depend on third party dependencies like ActiveRecord, or Mongo.
Alternatively, why does a separate part of the documentation specify the need to install a separate gem?
Maybe together we can make this more clear that this assumes you have installed flipper-active_record.  Would love to hear your thoughts.

@AlexWheeler I appreciate the thorough response.
I went into my local gem installation directory of the Flipper gem and noticed the flipper/adapters/ directory was in fact a bit different than shown in this repository. I assume that this is caused by the following lines in the flipper.gemspec file you mentioned:
Dir['flipper-*.gemspec'].map do |gemspec|
  spec = eval(File.read(gemspec))
  plugin_files << spec.files
  plugin_test_files << spec.files
end

ignored_files = plugin_files

Is this correct?
Regarding the following:

Maybe together we can make this more clear that this assumes you have installed flipper-active_record. Would love to hear your thoughts.

I think the require 'flipper/adapters/active_record' statement found in active_record/basic.rb#L17 is slightly confusing.
Perhaps a small comment mentioning the separate gem needs to be installed above that line would be helpful. Including some of the information you've just mentioned here would be helpful on the ActiveRecord adapter documentation.
I'm happy to submit a PR if you think it would be a good addition.

@AlexWheeler thanks for the great explanation. You rock.
@Orbyt This repo works like a mono-repo where there are several projects in one. It makes it more confusing for situations like this, but way less work from a maintenance standpoint. I also like that all the code is together in one place (so you don't have to hunt around for multiple repos). Having gone the multiple repo route on other similar projects, I can say I like the mono-repo better.
The confusion hasn't come up yet, but I REALLY appreciate you reporting it. I'm sure others have as well but didn't have the time or energy, so thank you!

I'm happy to submit a PR if you think it would be a good addition.

I'd love to see what you come up with.

I added a very small PR including the comment I indicated would be useful above. Frankly, I think the majority of my confusion arose due to being a newcomer to the Ruby/Rails community. The clarification on how the project is packaged into separate gems makes things make a little more sense.
I'll continue to give the documentation some thought and will submit further PR's if necessary.


Key Concepts doc sample data is unformatted

This page: https://docs.influxdata.com/influxdb/v1.4/concepts/key_concepts/
The data "Sample data" section is unformatted/misaligned.

Duplicate of #1410 -- thanks for catching this.


Fixing previous pipeline mistakes

For some reason, it doesn't include the two most recent commits of this branch. Will recreate the pr


feat: replace retry sdk v1 with sdk v2

Description of changes:
Trying to replace usage of java-sdk-v1 with api from java-sdk-v2, there is a lot of work, but starting somewhere.
Some code is here for compatibility issues waiting for next PRs

@hhkkxxx133 Can you check ?

@hhkkxxx133 please review and approve this asap, we are also impacted by this issue


Only set SDKPriorityUpdateHandling if workflow update is being used

What was changed
Only set SDKPriorityUpdateHandling if workflow update is being used. Previously SDKPriorityUpdateHandling was set at the start of every workflow, this made it difficult to roll back the Go SDK to a previous version that did not understand SDKPriorityUpdateHandling without workflows getting stuck . Now rollback will only be blocked if a user was using workflow update.
Using workflow update in a workflow execution means:

Registered an update handler
Received any update requests

I also changed the type of an unknown SDK flag error to be treated as non deterministic to align with the behaviour of a missing workflow version call since SDK flags are basically internal SDK version calls.
Why was the flag originally set in all workflow executions

So all new workflow executions would always use the new correct update behaviour.
Because that is what we believed we needed to do when we added SDKFlagProtocolMessageCommand flag to handle the ordering of update messages and the workflow task completed event (where the SDK reads the flags) since this is another update related flag the same logic applies. On review I couldn't find a good reason why we needed to always have set the flag. I think the actual issue was how the SDK was reading the messages, which I have fixed.

Other options
We could not add a flag at all. This would be the simplest option, but would break all current users of update in the Go SDK. Since there are currently users activity using and paying for workflow update this option was not chosen.
Release Notes
We will need to call out this lack of roll back support if a user is using workflow update in the release notes

In the original PR to add SDK flags to the proto we said an unknown flags should error I believe.
Choosing to not error is also dangerous since if a user does roll back then rolls forward again you are in a very weird state where a flag was being used, but then stopped being used, but the SDK doesn't know it stopped being used. I agree we should standardize, i'll open a feature issue for this.

In the original PR to add SDK flags to the proto we said an unknown flags should error I believe.

Yeah I do pretty clearly say that right in the comment. Now I've got to go figure out what the reason was that I moved away from that in Core, because there definitely was a reason, and IIRC it had to do with the lazy usage getting out of control

Yeah if there is no code that explicitly takes another path when the flag is not set

Yeah there is no, no update code, that takes another path

I too would hope there is no behavior difference from a workflow started on a newer SDK and older SDK if it didn't do anything with updates.

There is one code path that is effected unfortunately. The consequence is that registering an update handler on a workflow started on a older SDK won't introduce non determinism, so almost a good thing in some ways.


Fungal Growth is sometimes called Fungal Grotto

The trait at locations named Fungal Growths consists of towering fungal growths, although they are named Fungal Grotto in the game. This is likely a mistake, as they are clearly growths and not grottos.

Details
FF462B3C
Game Version
<IP_ADDRESS>
Language
English (EN)
New Game
Yes
Reproduction Steps
Go to Zelazny III in the Zelazny system, land in the Volcanic biome, find a Fungal Growth location and observe how the growths are refered to as grottos.

I don't think this is a bug. The POI name tends to slightly differ from the trait name sometimes.

Sometimes, sure. And to change anything without more confirmation would be premature. It's just that the object in question is so obviously a growth, a grotto would be its exact opposite.


Use utf8mb4 by default

Fixes #60

Thanks for contribution.
But it looks like it requires Mysql >=5.5.3 and Mariadb >=5.5. Could you please look into server version field of an initial handshake packet and fall back to utf8 if it is too old?

Yep, done!

Please add this comment to #36 before i merge:

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

@blackbeam You should add the contribution section to your README, then there's no need to have future contributors add to that thread.


Login - Remove PK, Scatter, SQRL

Summary
As a DHO user I should only be able to login via Anchor.
AC

[x] Remove PK field
[x] Remove Scatter
[x] Remove SQRL
[ ] Update Copy (to be done)

@leonieherma1  just awaiting the copy, should move this to testing? or keep in progress?

@jmgayosso you can put it in blocked - i hope I have the copy by monday or tuesday....


Nginx/Apache

Shall we continue using Apache, or should we force Heroku to use nginx? This will allow us to drop the other.

Just force nginx. :P

We should do that on Cachet then :)

Turns out we're only using nginx by default! Let's remove all references to Apache from the buildpack ;)


Add NTRU classical security

Classical security estimations are added. Since the submission doesn't
state the classical security directly, the numbers are derived from the
NIST security levels.
NTRUHPS2058509 has no classical security bits since is has NIST level 0 with the non-local model of computation.
Closes #151

I think you got something mixed up in the paramset comments.

I think you got something mixed up in the paramset comments.

Tried to clarify the source of the classical security with bc4af37


upgrade go-nvml version

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes # https://github.com/Project-HAMi/HAMi/issues/370
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

thx
/lgtm
/approve


Unresolvable dependency resolving [Parameter #3 [  $mustunderstand ]] in class SoapHeader

Laravel 8.46.0
PHP 7.4.18
Package 1.3.0
Error 1:  Unresolvable dependency resolving [Parameter #3 [ <optional> $mustunderstand ]] in class SoapHeader {"exception":"[object] (Illuminate\\Contracts\\Container\\BindingResolutionException(code: 0): Unresolvable dependency resolving [Parameter #3 [ <optional> $mustunderstand ]] in class SoapHeader at /var/www/magnum/vendor/laravel/framework/src/Illuminate/Container/Container.php:1067)
Error 1 Quick Fix: \ricorocks-digital-agency\soap\src\Request\SoapClientRequest.php:100 replace mustUnderstand to mustunderstand...
Error 2: Soap header throw error when actor is null...
Error 2 Quick Fix: Add actor to header

@ArthurPatriot, could you please provide a sample of your code that you are seeing this fail on please?

@nedwors
And not working if not add actor...

@ArthurPatriot thank you for the snippet, very helpful. We are working on some fixes, would appreciate you testing the pr with your code when we publish, will ping you when ready.

@nedwors sure, I will wait impatiently))

@ArthurPatriot, have created a draft pr #28, would you be able to see how it performs in your code please?

@nedwors checking...

@nedwors checked. All Ok.

@nedwors checked. All Ok.

Brilliant, thank you.
Your second point about actor, were you meaning this package's header class was throwing an error or the php SoapHeader class?

Trouble in Laravel IoC, resolve helper function require actor field must be filled... when its nulllaravel throw exception... Current solution perfect excludeactor` field from array to resolve)))
Error 2: PHP Warning:  SoapHeader::SoapHeader(): Invalid actor in /var/www/***/vendor/laravel/framework/src/Illuminate/Container/Container.php

@nedwors  Recheck without actor... Still not working...
If not use actor() throw error: Illuminate/Contracts/Container/BindingResolutionException with message 'Unresolvable dependency resolving [Parameter #4 [ <optional> $actor ]] in class SoapHeader

@nedwors add fix in PR #29

@ArthurPatriot appreciate the pr, not really keen on enforcing the soap constant for a null actor of we don't need to. Have pushed an update using the service container on the existing PR, this should solve the optional dependency resolution failure.

@nedwors has other solution? actor field must be null (optional handling not working...) or soap const... Current solution with excluding actor from resolve array not working.

@nedwors ok, it's one of solutions... If it's working let's create release))

Can you recheck with the latest updates on pr #28 please for the actor issue @ArthurPatriot?

@nedwors PHP Warning:  SoapHeader::SoapHeader(): Invalid actor in /var/www/***/vendor/ricorocks-digital-agency/soap/src/Providers/SoapServiceProvider.php on line 35

May be solution in my PR is normal)))

@nedwors after looking into it a little further, isn't SOAP_ACTOR_NONE the equivalent of null anyway?
https://stackoverflow.com/questions/33543078/php-soap-client-invalid-actor/37185662#37185662

@lukeraymonddowning my solution don't break any user code...) Tested in live code...

Updated pr #28 @ArthurPatriot - be good to get your input. Thanks

Code merged into 1.3.1


Fix MVT related issues

Use io.BytesIO instead of StringIO when convenient. See #302, #291.
Fix EmptyResponse for PBF format.

I am inclined on merging this. OK with you @migurski ?

I agree — this is important for Py3 compatibility.

Ok! Done!

Please release a new version to PyPI. Latest version there is from September and this merge fixed mapbox vector tiles. PyPI version doesn't work (in neither Python2 nor Python3).


Output information about the progress of org-to-org migrations as repos are migrated

When waiting for an organization-to-organization migration with the wait-for-migration command, the only feedback that the CLI provides on the progress of the migration is its state.
Org-to-org migrations potentially stay in the REPO_MIGRATION state for a long time if there are many repos to be migrated, and this can be a worrying time - as a user, you are likely to wonder "is my migration actually moving forward"?.
The node query for OrganizationMigrations allows you to fetch the remainingRepositoriesCount and totalRepositoriesCount for the migration.
This commit starts grabbing that data and logging a progress indicator (1/10 repos migrated) to the console.
Note that the GraphQL API currently returns 0 for the two count fields if the number of repos has not yet been completed. There is an outstanding bug to fix this and return null instead. This code is future-proof, able to handle both values.
Fixes https://github.com/github/gh-gei/issues/699.
_I don't intend to make it a habit to make code changes, but I wanted to see this enhancement added before org-to-org ships, and I wanted to get familiar with the codebase 😊 _

[x] Did you write/update appropriate tests
[x] Release notes updated (if appropriate)
[x] Appropriate logging output
[x] Issue linked
[x] Docs updated (or issue created)

looks good, could we get a test for the null scenario?

The null scenario shouldn't be relevant now, as we're just relying on the statuses instead.


Fix +nightly test compilation

Previously an error
  Compiling git2 v0.8.0 (/home/travis/build/alexcrichton/git2-rs)
error: name `cfg` is reserved in macro namespace
   --> src/cred.rs:421:18
    |
421 |     macro_rules! cfg( ($($k:expr => $v:expr),*) => ({
    |                  ^^^
error: aborting due to previous error
error: Could not compile `git2`.
warning: build failed, waiting for other jobs to finish...
error: build failed

was produced.
I replaced cfg macro name, which appears to be reserved now, by test_cfg.

Thanks!


chore: fix flaky build steps

/azp run

Codecov Report

Merging #1298 (236e08a) into master (6a58691) will decrease coverage by 14.64%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master    #1298       +/-   ##
===========================================
- Coverage   83.31%   68.66%   -14.65%
===========================================
  Files         302      251       -51
  Lines       14023    12312     -1711
  Branches      681      681
===========================================
- Hits        11683     8454     -3229
- Misses       2340     3858     +1518

Impacted Files
Coverage Δ

...m/src/main/scala/com/microsoft/lightgbm/SWIG.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...la/org/apache/spark/ml/param/TypedArrayParam.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...soft/azure/synapse/ml/cognitive/AudioStreams.scala
0.00% <0.00%> (-87.88%)
:arrow_down:

...ft/azure/synapse/ml/cognitive/AzureSearchAPI.scala
2.59% <0.00%> (-87.02%)
:arrow_down:

...osoft/azure/synapse/ml/cognitive/AzureSearch.scala
7.19% <0.00%> (-80.58%)
:arrow_down:

...azure/synapse/ml/lightgbm/LightGBMClassifier.scala
11.11% <0.00%> (-80.00%)
:arrow_down:

...ynapse/ml/train/ComputePerInstanceStatistics.scala
11.11% <0.00%> (-77.78%)
:arrow_down:

...e/synapse/ml/cognitive/FormRecognizerSchemas.scala
7.69% <0.00%> (-76.93%)
:arrow_down:

...rosoft/azure/synapse/ml/train/TrainRegressor.scala
10.71% <0.00%> (-76.79%)
:arrow_down:

...rosoft/azure/synapse/ml/explainers/ImageSHAP.scala
16.66% <0.00%> (-76.67%)
:arrow_down:

... and 110 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 6a58691...236e08a.


Revive the libp2p Community Call

The libp2p Community Call has been happening since January. The next one is here: https://lu.ma/2024-04-02-libp2p-community
The notes are taken here: https://docs.google.com/document/d/12lxeh579GjEZUB5KmKhFb2OhObkKYF3cg5ClkfAEosE/edit?usp=sharing


Add quotes around package name in composer command

Without the quotes the command fails.

It works for me without quotes. What composer version/OS do you use?

Composer version 1.3.2, MacOS High Sierra 10.13.3. I get "no matches found: kordy/ticketit:0.*" when I run it without the quotes. With the quotes it runs fine.
Kind regards,
Svetoslav Spasov
On Wed, 28 Mar 2018 at 23:37 "Balázs Dura-Kovács" < ">"Balázs Dura-Kovács" > wrote:

It works for me without quotes. What composer version/OS do you use?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (
https://github.com/thekordy/ticketit/pull/443#issuecomment-377027724 ) , or
mute the thread (
https://github.com/notifications/unsubscribe-auth/ALmO2_hToK9jaNxRavVA_t5lMhRK6lgEks5ti_R8gaJpZM4S-k54
).

The newest version is v1.6.3, so you might want to upgrade. I'll merge this anyway, because it works with or without quotes for me, but this might cause problems for other people too.


add option to get the latest message using latest as request parameter

fixes: https://github.com/jhillyerd/inbucket/issues/50

Looks great, thank you

@jhillyerd there any other steps to do? or you will merge to master?

No more steps - is in master (rc2) now.


feat: chat UI to stub chat service via websocket plugin

progress toward design sketch:
C4Component
title Endo Trivial Chat: Echo

Person(chatA, "Alice", "a chat use on the Agoric side")
    Rel(chatA, webUI, "uses", "HTTP")
Container(webUI, "Agoric UI", "Web page")
    BiRel(webUI, wsPlugin, "tx/rx", "WebSocket")
Container(wsPlugin, "WebSocket Plugin", "Endo plug-in")
    Rel(echoChat, wsPlugin, "uses", "endo API")
Container(echoChat, "Trivial Chat App: Echo", "Endo app")

something is weird about the way this PR is tracking (or... not tracking) main


[fix][UI]Add render to projects-overview table

Purpose of the pull request

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

bug


Fix font-awesome missing. Use publishable folder instead old asset fo…

…lder, see PR #56

I personally think we should just let @afsardo update the paths in his PR and treat this as a duplicate.

This is done and working better than my PR ^^ you can pull this and close mine :)

Thanks guys, actually using a custom font library for voyager. You can see the response here: https://github.com/the-control-group/voyager/pull/56
I've made sure to remove the occurrences of FontAwesome and replace them with the custom Voyager font class 👍


terraform/auth: fix dropped error

This fixes a dropped err variable in terraform/auth.

Good catch! Thank you.


Skip by default the setting up of inputs in the deploy-many.sh script

Rational is that end-user would set those values through project ui, and then deploy the stack through the script.

@daniel-butler-irl - another one related to deploy-many script if you're looking at that area.


Asset gem WIP

Prototype packaging origin as a ruby gem. For rails apps such as the desktop app we can use rails engines to include the assets. I have still to include an example of implementing it in a rails app.
Examples of importing origin as an asset gem using Sprockets :
https://github.com/fac/website/pull/956
https://github.com/fac/freeagent/pull/8457
https://github.com/fac/campaigner/pull/75
https://github.com/fac/fieldagent/pull/694
Potentially fapd-portal and data-warehouse in the future.
TODOS

[x] Bring PR up to date.
[ ] Bring other PRs up to date.

[x] FreeAgent
[ ] Website
[ ] Campaigner
[ ] FieldAgent

[ ] How does building out the origin docs work with the asset gem?
[ ] Does bringing in origin as an asset gem match up with designers workflow? Probably some pairing required to understand.
[ ] Run the implementations past the engineering team at the engineering forum and ask for comments/concerns

Nice work!
I'm wondering whether we adopt the Gem as the defacto way of managing and implementing Origin, and ditch npm altogether. npm makes it really easy for designers to publish new versions, and has enough in the way of user/contributor permissions for us. How would switching to rubygems change any of that?
Where would the stylesheets installed by the gem actually live? What paths would we use to reference them from inside the local stylesheets (e.g. in app/assets/stylesheets)?
What would the process be for updating to a new version of the Gem?

I'm wondering whether we adopt the Gem as the defacto way of managing and implementing Origin, and ditch npm altogether. npm makes it really easy for designers to publish new versions, and has enough in the way of user/contributor permissions for us. How would switching to rubygems change any of that?

@robbiemanson There isn't anything to say we couldn't have npm and gem implementations. However, as you say if npm isn't really adding anything at the moment then we could look at adopting the Gem approach as the defacto way. There should be any real major changes to the publishing cycle compared to npm. There are two ways to publish a gem. Either you can publish to rubygems itself or you can pull the gem in from the github repo.
Ruby Gems publishing
For the former you would just bump https://github.com/fac/origin/blob/asset-gem/lib/origin/version.rb and then tag the release in github. Then you'd build and publish the gem. See here for details (http://guides.rubygems.org/publishing/). Then in your gem file for the project you want to install it would just be updating the version number and then doing bundle install
gem "origin", "0.3.16"

Pull from Git repo
For the latter approach you would just bump https://github.com/fac/origin/blob/asset-gem/lib/origin/version.rb and then tag the release in github. Then in your gem file for the project you want to install it would just be updating the version number and then doing bundle install:
gem "origin", "0.3.16",  :github => "git@github.com:fac/origin.git"

Where would the stylesheets installed by the gem actually live?

These would be internally added to the Sprockets path for the application. So they wouldn't be committed to the projects repo like the desktop app does at the moment. Simply you could have the path as what ever you really wanted really. For example to @import a stylesheet to use then it could be: @import "origin/global/fonts/_font-functions"; Nice, simple and clean IMO

What would the process be for updating to a new version of the Gem?

Sort of elaborated above how the publishing system works. See above.
I'll prototype a branch that switches over the desktop app to show you how it could look.

 Origin Gem

I've checked this branch against fieldagent and I don't see any issues :100:

@ball-hayden The updated docs/instructions look great. It's still missing anything about using the local version of the gem in the dev environment, but I don't really think that should hold up shipping the gem.


Add build subcommand

With this commit we introduce a new build subcommand,
allowing users to simply build Elasticsearch (and plugins) for
a given target operating system and architecture.
Relates https://github.com/elastic/rally/pull/1570, https://github.com/elastic/rally-teams/pull/75/
Closes https://github.com/elastic/rally/issues/1462

Weird, it first fails on:
esrally race --track="tsdb" --challenge="downsample" --track-repository="/var/lib/jenkins/workspace/elastic+rally+pull-request+rally-tracks-compat/.rally/benchmarks/tracks/rally-tracks-compat" --track-revision="master" --configuration-name="pytest" --enable-assertions --kill-running-processes --on-error="abort" --pipeline="benchmark-only" --target-hosts="<IP_ADDRESS>:19200" --test-mode

I can repro this locally on master:
$ esrally install --quiet --http-port=29200 --node=rally-node --master-nodes=rally-node --car=4gheap,trial-license --seed-hosts="<IP_ADDRESS>:29300" --revision=current
{
  "installation-id": "5afc6106-5f08-407a-9304-c21614713e85"
}

$ esrally start --installation-id 5afc6106-5f08-407a-9304-c21614713e85 --race-id 2000

$ esrally race --track="tsdb" --challenge="downsample" --track-revision="master" --configuration-name="pytest" --enable-assertions --kill-running-processes --on-error="abort" --pipeline="benchmark-only" --target-hosts="<IP_ADDRESS>:19200" --test-mode
[...]
2022-09-13 03:13:23,694 ActorAddr-(T|:53103)/PID:24086 esrally.actor ERROR Worker[0] has detected a benchmark failure. Notifying master...
Traceback (most recent call last):

  File "/Users/bradleydeam/perf/github.com/b-deam/rally/esrally/driver/runner.py", line 109, in runner_for
    return __RUNNERS[operation_type]

KeyError: 'downsample'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

  File "/Users/bradleydeam/.pyenv/versions/3.8.10/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)

  File "/Users/bradleydeam/perf/github.com/b-deam/rally/esrally/driver/driver.py", line 1707, in __call__
    loop.run_until_complete(self.run())

  File "/Users/bradleydeam/.pyenv/versions/3.8.10/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
    return future.result()

  File "/Users/bradleydeam/perf/github.com/b-deam/rally/esrally/driver/driver.py", line 1735, in run
    schedule = schedule_for(task_allocation, params_per_task[task])

  File "/Users/bradleydeam/perf/github.com/b-deam/rally/esrally/driver/driver.py", line 2207, in schedule_for
    runner_for_op = runner.runner_for(op.type)

  File "/Users/bradleydeam/perf/github.com/b-deam/rally/esrally/driver/runner.py", line 111, in runner_for
    raise exceptions.RallyError(f"No runner available for operation-type: [{operation_type}]")

esrally.exceptions.RallyError: No runner available for operation-type: [downsample]

Secondly, it fails on:
esrally race --track="elastic/security" --challenge="security-indexing-querying" --track-revision="master" --configuration-name="pytest" --enable-assertions --kill-running-processes --on-error="abort" --pipeline="benchmark-only" --target-hosts="<IP_ADDRESS>:29200" --test-mode --track-params="number_of_replicas:0,query_warmup_time_period:1,query_time_period:1,workflow_time_interval:1,think_time_interval:1"

But I can repro this failure locally.

Ah, the downsample failure is because the Rally Track includes the new runner, but Rally doesn't yet have the PR merged.

This PR will fail ITs until https://github.com/elastic/rally-teams/pull/75 is merged.

@elasticmachine run rally/it-python310


Table panel cells color

I'm submitting a ...

[ ] Bug report
[ ] Feature requestdd
[*] Question / Support request

Hello! I am trying to retrieving data from ZabbixDB and showing it in table panel.
In 'Metric' section, i've chosen Format as: Table (pic. below)

In 'Column Styles' section:

But, no colors appears.
If i choose Format as: "Time Series", i can see colors, but i lose columns, which was not marked as "time_sec/metric/value". And this is important for me.
Any ideas?

Solved. Problem was cause of VARCHAR type of my value.


style: Fix inconsistent formatting

only a spacing change:
https://github.com/twosigma/beaker-notebook/commit/66dd3577f1be84854d9046ca2c29135545bdc532?w=1

I ran into this when I was updating a few styles in a previous commit, and just ran through all of the scss files in one pass to make sure they are consistent


Has many tracking

Codecov Report
Patch coverage: 64.16% and project coverage change: -0.54 :warning:

Comparison is base (2fa9689) 83.66% compared to head (9fb0713) 83.13%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #73      +/-   ##
==========================================
- Coverage   83.66%   83.13%   -0.54%
==========================================
  Files         124      124
  Lines       11019    11170     +151
  Branches     1349     1358       +9
==========================================
+ Hits         9219     9286      +67
- Misses       1772     1858      +86
+ Partials       28       26       -2

Impacted Files
Coverage Δ

<EMAIL_ADDRESS>92.70% <18.75%> (-2.13%)
:arrow_down:

<EMAIL_ADDRESS>76.34% <42.62%> (-9.84%)
:arrow_down:

<EMAIL_ADDRESS>81.19% <70.73%> (+1.99%)
:arrow_up:

<EMAIL_ADDRESS>90.00% <78.94%> (-7.85%)
:arrow_down:

...test/helpers/models-with-relations/rest/id/user.ts
100.00% <100.00%> (ø)

<EMAIL_ADDRESS>82.64% <100.00%> (+0.34%)
:arrow_up:

<EMAIL_ADDRESS>89.79% <100.00%> (+0.90%)
:arrow_up:

<EMAIL_ADDRESS>100.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


JSON Schema validation/code-assist for interaction model

In the earlier version of the add-on, there was code assist for the interaction model (and I think the skill manifest). This was very helpful, as it helped remind me of what was needed and available when working on my skill's interaction model. I believe it was based on the JSON Schema for those file types. The new version doesn't seem to include this.
I'd like to be able to use code-assist on my interaction models again.
I have attempted to manually add schema validation/code-assist, but have been largely unsuccessful. It would be much easier if it were just part of the add-on as it was before.

Hey @habuma , thanks for raising this feature request. I will discuss this internally with the team and see how we can prioritize on this task.

Because of the stale issue message and because I sincerely want this to be added back into the extension, I'm sending this "PING" message to revive this issues.
Ping!

@habuma sorry about the github-actions bot update. We will work on updating it's configuration. Rest assured, this feature request is being looked into and we will update the ticket once we get to adding this feature.


Revert blue h1 background to white

The descriptions will have markdown and code in them, so we should revert this to standard.

Implemented.


ATEM Blackmagic pb to import config

Hi I am on macOs High Sierra and I want to import a configuration
When I try to "replace current configuration" I obtain this message :

Can you help me ?
Sorry for my bad English, I am French
Xtof

Hi @cristofar can you please let me know which version/build of Companion are you currently running ... and/or let me know the atem module version number (displayed in the log panel). Thanks!

Hi
My version of companion is
1.3.0 (1a7592b-1203)
https://bitfocus.io/companion/
https://bitfocus.io/companion/
In the log panel, I can read : 16. 14:18:22 instance(atem): Connected to a ATEM Television Studio HD
Thanks

Le 16 juil. 2019 à 14:14, Keith Rocheck<EMAIL_ADDRESS>a écrit :
Hi @cristofar https://github.com/cristofar can you please let me know which version/build of Companion are you currently running ... and/or let me know the atem module version number (displayed in the log panel). Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-atem/issues/20?email_source=notifications&email_token=AMUCEM3RKQSJENMVHSCEEEDP7W3S5A5CNFSM4IEAIOQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2AU3FY#issuecomment-511790487, or mute the thread https://github.com/notifications/unsubscribe-auth/AMUCEM4W3NBDZ4UGG2MDLYTP7W3S5ANCNFSM4IEAIOQQ.

When I go down in the log panel I can read this :
16. 14:18:19 USB(undefined): Found device, but no access. Please quit any other applications using the device, and try again.

Le 16 juil. 2019 à 14:21, Free<EMAIL_ADDRESS>a écrit :
Hi
My version of companion is
1.3.0 (1a7592b-1203)
https://bitfocus.io/companion/
https://bitfocus.io/companion/
In the log panel, I can read : 16. 14:18:22 instance(atem): Connected to a ATEM Television Studio HD
Thanks

Le 16 juil. 2019 à 14:14, Keith Rocheck<EMAIL_ADDRESS><EMAIL_ADDRESS>a écrit :
Hi @cristofar https://github.com/cristofar can you please let me know which version/build of Companion are you currently running ... and/or let me know the atem module version number (displayed in the log panel). Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-atem/issues/20?email_source=notifications&email_token=AMUCEM3RKQSJENMVHSCEEEDP7W3S5A5CNFSM4IEAIOQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2AU3FY#issuecomment-511790487, or mute the thread https://github.com/notifications/unsubscribe-auth/AMUCEM4W3NBDZ4UGG2MDLYTP7W3S5ANCNFSM4IEAIOQQ.

I can read this :
16. 14:18:21 loaded<EMAIL_ADDRESS>Blackmagic Design:ATEM by Håkon Nessjøen

Le 16 juil. 2019 à 14:21, Free<EMAIL_ADDRESS>a écrit :
Hi
My version of companion is
1.3.0 (1a7592b-1203)
https://bitfocus.io/companion/
https://bitfocus.io/companion/
In the log panel, I can read : 16. 14:18:22 instance(atem): Connected to a ATEM Television Studio HD
Thanks

Le 16 juil. 2019 à 14:14, Keith Rocheck<EMAIL_ADDRESS><EMAIL_ADDRESS>a écrit :
Hi @cristofar https://github.com/cristofar can you please let me know which version/build of Companion are you currently running ... and/or let me know the atem module version number (displayed in the log panel). Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-atem/issues/20?email_source=notifications&email_token=AMUCEM3RKQSJENMVHSCEEEDP7W3S5A5CNFSM4IEAIOQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2AU3FY#issuecomment-511790487, or mute the thread https://github.com/notifications/unsubscribe-auth/AMUCEM4W3NBDZ4UGG2MDLYTP7W3S5ANCNFSM4IEAIOQQ.

@cristofar do you still have the config you tried to import when you got this error? If not I think we will have to close this for now, as it is a bug report for 1.3.0, and you should in that case test this with 1.4.0

Closing due to inactivity


Added support for older JDK

Added a new tomcat image with an older JDK and tomcat version

We are not going to support being based on old image.  openjdk:8u151-jdk is unsupported and gets no updates.


FEAT-#5754: Add np.linalg operations

What do these changes do?
This PR adds support for np.dot and np.linalg.norm.

[x] first commit message and PR title follow format outlined here

NOTE:  If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.

[x] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] signed commit with git commit -s
[x] Resolves #5754
[x] tests added and passing
[x] module layout described at docs/development/architecture.rst is up-to-date

Mind using all close for testing norm, with error around 1e-12? That should clear the CI issue up!


Reset command

Closes #105

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6053060). Click here to learn what that means.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master     #106   +/-   ##
=========================================
  Coverage          ?   77.39%
  Complexity        ?      603
=========================================
  Files             ?       98
  Lines             ?     1761
  Branches          ?      182
=========================================
  Hits              ?     1363
  Misses            ?      357
  Partials          ?       41

Impacted Files
Coverage Δ
Complexity Δ

...ava/seedu/address/logic/commands/ResetCommand.java
100.00% <100.00%> (ø)
2.00 <2.00> (?)

...va/seedu/address/logic/parser/TutorsPetParser.java
100.00% <100.00%> (ø)
22.00 <0.00> (?)

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 6053060...2c3e2bd. Read the comment docs.


[Maistra-566] Make prometheus image configurable

https://issues.jboss.org/browse/MAISTRA-566

This looks good to me, the only question I have is whether we should keep all prometheus-related patches in patch-prometheus.sh?

LGTM.
I need these changes right now, so I'll merge this and address @dmitri-d's comments in a followup PR

Follow-up PR: https://github.com/Maistra/istio-operator/pull/117

Jira issue is wrong


Change WebSocket connection URL during runtime

Our backend at Wire requires an access token as part of the WebSocket connection URL.
The schema looks like this:
wss://prod-nginz-ssl.wire.com/await?access_token=Dp42wWHPiGukagf86Djx7JvVKed

The access token must be renewed at a certain interval which leads to problems when using ReconnectingWebsocket because it will still try to reconnect to the URL it has been initialized with (which could have an outdated access_token).
Is there a chance to change the connection URL at runtime? Telling from the type definitions it doesn't look like it's accessible. 😢

fixed in #4


⚠ GitLab Server has degraded performance

In 81eb8fb, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 6020 ms

Resolved: GitLab Server performance has improved in 3d7baf6.