WOW (can close)

Sorry this not issue per say, its for feedback to authior of this OBIS app- simply HAD to say - AMAZING BRO! How cool is this - it's amazing - hoping we have CSV - just in the middle of using it - can't you do something for barclays too pls!     NICE!!
Easy star - 5 if I could - yeahh!
Thanks a mil.  I love it.

Hey, thank you for the kind words! Glad you found it useful.
It took a lot of messing about with my own HSBC account to get OBIS working as you see it. I say this because I don't have a Barclays account, so I'm unlikely to develop a plugin for it at this point.
Still, I'm open if someone wants to contribute a plugin! :)


Change the Logo / title / subtitle

Goal
Update your batch's mainpage.

Create a random logo (or use Dall-E!) to generate a batch logo
title: Batch #{batch_number}
subtitle: Whatever you feel appropriate :)

I'm working on this Issue!

I'm working on this Issue!

Completed in this PR 🏗

I completed this PR here: https://github.com/BuidlGuidl/batch9.buidlguidl.com/pull/18

Although I really like the sober style chosen by @fedeloterstein, I find @arjanjohan 's design to be more fun. I think we could deffinitely go that way!


Add windows CI through Appveyor

The project will likely need to be activated by maintainers at https://ci.appveyor.com/projects
Also, it would be nice to have a status badge from https://ci.appveyor.com/project/docker/swarm/settings/badges added to the readme as well.

It looks like the travis build failed with coveralls returning a 500. I'm going to try launching the build again by closing the pr and reopening it.

Coverage increased (+0.08%) to 39.44% when pulling 6b1239b6d5556cb6c7de307b9e7265789065b979 on weswigham:patch-1 into b04197d3c03ad81e29fa6b0ecd1aebf9e5edc4c5 on docker:master.

Coverage increased (+0.08%) to 39.44% when pulling 6b1239b6d5556cb6c7de307b9e7265789065b979 on weswigham:patch-1 into b04197d3c03ad81e29fa6b0ecd1aebf9e5edc4c5 on docker:master.

Hey @weswigham - sorry for the mess. We are using a tool (waffle.io) that apparently is buggy and kept re-opening this PR.

It reopening the PR actually did what was required. :+1:


Release Google.Cloud.Metastore.V1 version 2.8.0

Changes in this release:
New features

Add IServiceCollection extension methods for client registration where an IServiceProvider is required. (commit 022fab2)

Created release for Google.Cloud.Metastore.V1-2.8.0

This succeeded the first time around. The failure is because the release was attempted twice.


Phantom Embedded Wallet Stuck on Mainnet - Unable to Process Devnet Transactions

I'm facing an issue where the embedded Phantom wallet integration is not working correctly with devnet transactions. Despite being configured to connect to the devnet RPC, the wallet consistently shows as being connected to the mainnet.
Here are the details of the issue:
Problem: The Phantom wallet embedded in my application always defaults to mainnet, even when explicitly configured to connect to devnet.
Connection is established with the correct devnet RPC endpoint.
Other parts of the application correctly connect to devnet.
Expected Behavior: The wallet should reflect the connection to devnet and allow transactions on devnet.
Actual Behavior: The wallet UI and functionality remain tied to mainnet, preventing devnet transactions.

Hello @siby-mathew
You're experiencing transcript error. It sounds like your query would be best dealt with by the support team.
I'll have to refer you to the official support live chat with the ticket ID PHA07638
Please see the link below to our dedicated support line:
Phantom Network DApps Support Ticket Requests.
Click on the live chat icon at the bottom corner of the page to initiate chat with a live support agent.

Thank you @Angiepeck22

@siby-mathew reach out to them now they should be able to figure something out


Use operator== to compare YAML iterators

operator== was implemented here: https://github.com/apple/swift-llvm/commit/71a6baa31c4a08a3c123953a0239bff001b2e437
/cc @jrose-apple

@swift-ci Please test

(:tada:)


Preserve topicref/topicmeta/navtitle when @locktitle is enabled

Signed-off-by: Toshihiko Makita<EMAIL_ADDRESS>Preserve topicref/topicmeta/navtitle when @locktitle="yes".
Description
This pull request fixes issue #3708.
Motivation and Context
If topicref/topicmeta/navtitle is present with topicref/@locktitle="yes", this navtitle should be honored instead of adopting topic/title. But current DITA-OT 3.6.1 does not follow this rule in some condition.
Fixes issue #3708.
How Has This Been Tested?
Tested with Windows 10 with DITA-OT 3.6.1 and modified develop branch of DITA-OT repository.
[Original test data & result archive]
20210504-navtitle.zip
temp-3.6.1 and out-3.6.1 folder contains the DITA-OT 3.6.1 results. temp-3.6.1-develop and out-3.6.1-develop contains the updated result with DITA-OT development branch using newly built dost.jar.
The modification changes the private static data in MapMetaReader.java. So it does not effect to other area.
Type of Changes

Bug fix (non-breaking change which fixes an issue)

Documentation and Compatibility
No document update will be needed.
However the content of topicref/topicmeta/navtitle will change according to the DITA 1.3 specification, it should be mentioned in the update log explicitly.
Checklist

My code follows the code style of this project.

https://github.com/dita-ot/dita-ot/wiki/Java-Coding-Conventions
https://github.com/dita-ot/dita-ot/wiki/XSLT-Coding-Conventions
https://github.com/dita-ot/docs/wiki/coding-guidelines

I have updated the unit tests to reflect the changes in my code.

@jelovirt Is this pull-request acceptable? I'm confident with my unit test result. However "Test/build" fails when I submitted this pull-request. At this moment, I have no way to analyze the cause. Also, my user is waiting this modification to use topicmeta/navtitle for their specific authoring usage. Please give me your advice.


hook Void function  error

        do {
            //劫持 layoutSubviews，setTitle
            try hookAfter(object: self, selector: #selector(UIButton.layoutSubviews), closure:{
                self.exchangeImageLocation(location: location, space: space) //Fix：img label几率重叠bug

            })
            let hookCloure =  { originalFunc,object,sel,title,state in
                self.exchangeImageLocation(location: .default, space: space) //Fix：img label几率重叠bug
                originalFunc(object,sel,title,state) //💥 这里崩溃
                self.sizeToFit() //会触发layoutSubviews

            }as @convention(block) (
                (AnyObject,Selector,String,UIControl.State)->Void,
                AnyObject,
                Selector,
                String,
                UIControl.State
            ) -> Void

            try hookInstead(object: self,
                            selector: #selector(UIButton.setTitle(_:for:)) ,
                            closure: hookCloure
            )

        }catch let error {
            print("HOOKERROR:",self.titleLabel?.text as Any,error)
        }

I tested your code with this:
import UIKit
import EasySwiftHook

class ViewController: UIViewController {
    // Hooking code is in AppDelegate.swift
    override func viewDidLoad() {
        super.viewDidLoad()
        self.title = "I am the title"
        self.view.backgroundColor = .red

        let button = UIButton.init()
        button.hahaha()
        button.layoutSubviews()
        button.setTitle("title", for: .normal)
    }
}

extension UIButton {
    func hahaha() {
        do {
            //劫持 layoutSubviews，setTitle
            try hookAfter(object: self, selector: #selector(UIButton.layoutSubviews), closure:{
//                self.exchangeImageLocation(location: location, space: space) //Fix：img label几率重叠bug

            })
            let hookCloure =  { originalFunc,object,sel,title,state in
//                self.exchangeImageLocation(location: .default, space: space) //Fix：img label几率重叠bug
                originalFunc(object,sel,title,state) //💥 这里崩溃
                self.sizeToFit() //会触发layoutSubviews

            }as @convention(block) (
                (AnyObject,Selector,String,UIControl.State)->Void,
                AnyObject,
                Selector,
                String,
                UIControl.State
            ) -> Void

            try hookInstead(object: self,
                            selector: #selector(UIButton.setTitle(_:for:)) ,
                            closure: hookCloure
            )

        }catch let error {
            print("HOOKERROR:",self.titleLabel?.text as Any,error)
        }
    }
}

It works fine on both real devices (iPhone 11 pro) and simulator with EasySwiftHook 2.0.0.
Can I get a demo project of yours? Is your crash on a real device (and what's the device detail) or a simulator?

@tanpengsccd Another issue. There is a memory leak in this code.
try hookAfter(object: self, selector: #selector(UIButton.layoutSubviews), closure:{
    self.exchangeImageLocation(location: location, space: space) //Fix：img label几率重叠bug
})

self retain hook block and hook block also retian self.
It should be
try hookAfter(object: self, selector: #selector(UIButton.layoutSubviews), closure:{ button, selector in
	button.exchangeImageLocation(location: location, space: space) //Fix：img label几率重叠bug
} as @convention(block) (UIButton, Selector) -> Void)

Or:
try hookAfter(object: self, selector: #selector(UIButton.layoutSubviews), closure:{[weak self] in
    self?.exchangeImageLocation(location: location, space: space) //Fix：img label几率重叠bug
})

@tanpengsccd Hi. Can this issue be reproduced? Please use the newest version 2.0.1 and verify it. Thanks!

Please re-open if you feel it is necessary.


Port JSON key strategy to swift-corelibs-foundation

This is a work in progress branch.
First step is to bring JSONEncoder.swift up to date with changes to the file in the overlay before the key strategy changes landed.

@swift-ci please test

@itaiferber I put two sections of code in an #if block that look to me like they are intentionally different, at least for the time being.

Nice. I wonder if we could use the DEPLOYMENT_RUNTIME_SWIFT define for the differences, then share an identical file in the overlay?

Yah that may be possible. @itaiferber and I believe we have a few errors lurking in here since there are some as casts. Maybe we can wrap those.

@swift-ci smoke test

@swift-ci please test

@swift-ci please test

@swift-ci Please test

@swift-ci please test

Looks like this failed with a core dump:
Test Case 'TestJSONEncoder.test_encodingTopLevelSingleValueEnum' started at 2017-11-30 00:49:44.323
/home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux/swift/utils/build-script-impl: line 264: 26232 Illegal instruction     (core dumped) "$@"
/home/buildnode/jenkins/workspace/swift-corelibs-foundation-PR-Linux/swift/utils/build-script: fatal error: command terminated with a non-zero exit status 132, aborting

Fixed the core dump (we needed Codable.swift changes too), but have some bridging failures to figure now now.

@swift-ci please test

I already know this fails. Just need some time to come back to this and sort out the bridging issues.

@parkera Any updates on this? I'm hoping this makes into 4.1 keyDecodingStragety is a really nice API and cleans up so much code.

Unfortunately I got stuck on this one, having trouble figuring out why the tests don't pass after merging in the prerequisite changes from the Swift overlay version.

So in case it helps, this seems to be a problem initially isolated to the decoder. Here's basically the smallest repro I can give you:
import Foundation

struct Test: Codable {
    var field: Int
}

let json = "{\"field\": 5}".data(using: .utf8)!
let decoder = JSONDecoder()
let result = try decoder.decode(Test.self, from: json)
print(result.field)

In Swift 4.0, this works fine and prints 5, as expected. In Swift 4.1, it explodes with
typeMismatch(Swift.Int, Swift.DecodingError.Context(codingPath: [CodingKeys(stringValue: "field", intValue: nil)], debugDescription: "Expected to decode Int but found Int instead.", underlyingError: nil))

This seems to be related to the underlying parsing producing an Int instead of an NSNumber. As identified before, this is likely a bridging issue, and of the two of us I suspect you're vastly better equipped to go further with this than I am @parkera.

@itaiferber I know we are still talking about the returned types from JSONSerialization in a few other PRs, but I don't recall any changes here for 4.1 specifically. Do you?

None that I've seen; I can't find any PRs that changed JSONSerialization in Swift 4.1 on here either (but I'll keep looking). @Lukasa What platform are you on? Which toolchain are you running there?

@itaiferber Sorry, I could really have made that clearer. That's Ubuntu 16.04, using a hand-compiled Swift toolchain from the swift-4.1-DEVELOPMENT-SNAPSHOT-2018-03-21-a tag, with a Foundation branched from that tag with this patch merged on top of it.
If I just use the swift-4.1-DEVELOPMENT-SNAPSHOT-2018-03-21-a tag directly without this patch, the above test passes just fine. So it's this patch that is affecting the return type.

Ah, ok.

Any updates on this issue? @parkera
Sent with GitHawk

Any update on this?

We are dealing with some bridging landing fallout and WWDC. My plan is to look at this starting late this week, unless someone else can.

We can expect this merged in swift 4.2? :(

@parkera can you rebase this so that we can run the tests again, or close it if it has gone stale?

I'm going to close this, since I think #1561 should cover it.


Returning a new constructor from a class decorator does not type check.

TypeScript Version:  2.0.0
Code
function ReplaceConstructor (target: Function) : Function {
  return class Replacement {
    constructor (public a: string) { }
  }
}

@ReplaceConstructor
class A { }

console.log((new A('hello')).a)

Expected behavior:
Should type-check.
Actual behavior:
Gives the following errors:
main.ts(7,1): error TS1238: Unable to resolve signature of class decorator when called as an expression.
  Type 'Function' is not assignable to type 'void'.
main.ts(10,14): error TS2346: Supplied parameters do not match any signature of call target.

The first error goes away with the following adjustment:
function ReplaceConstructor () : ClassDecorator {
  return (target: Function) => class Replacement {
    constructor (public a: string) { }
  }
}

@ReplaceConstructor()
class A { }

console.log((new A('hello')).a)

Both source files, when compiled and run in node.js, correctly output the string "hello".

Cause Function is not the same as A that you are decorating. a class decorator can not change the type of what it decorates.
I think you are looking for something like https://github.com/Microsoft/TypeScript-Handbook/blob/792592c8f7d36a45f3eb5d1f68fce655aa5c7f5d/pages/Decorators.md#class-decorators


format for contact info

@lahoffm was thinking it should be something like
Name:
Degree program (current for undergraduates/graduates, field of your Ph.D. for post-docs):
Research group you work with:
Programming languages and software libraries you use:

oh and maybe
Github:
website:
twitter:

Sure. Could it just be in a markdown file in a simple table?

yes.
Not sure if this is what you were suggesting but why not just have each person submit a PR with a separate FirstnameLastname.md file inside of a ./contacts subfolder that the repo will have. I'll submit my own PR so you can see what I mean.

We could then have a script that assimilates all the separate FirstnameLastname.md files into one "contacts.md" file. That way we avoid dealing with 3000 merge conflicts

Sure
On Sep 22, 2017 10:03, "Lukas Hoffmann"<EMAIL_ADDRESS>wrote:

Issue can be closed now?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Atlanta-BEST-Data-Science/BEST-contacts/issues/1#issuecomment-331455738,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALYZiq3MY-GBMbM46WT2q4wnos5E296vks5sk74UgaJpZM4Pf0Wc
.


LogEndpoint: call aio_fsync() once per second

With the default kernel settings (/proc/sys/vm/dirty_expire_centisecs
= 3000), it is possible to lose up to 30s of logging data in events of
power loss.
This patch reduces worst-case loss to 1s by calling fsync() every second.

This is the restored commit from #176  that got lost


Did you forget to add [] around it?

The hint is ambiguous at best and misleading at worst suggesting that the highlighted Field Date needs to be a list.
It so happens that line 28, the view function is the one that needs to return a list.

type alias Field a =
    { raw : String
    , value : a
    , view : a -> List (Html (Msg a))
    , label : String
    , validation : a -> List String
    }

Ended up removing the hint in https://github.com/elm/compiler/commit/0cd361d54c3a56940ebf94882069adf1fbc4600e. Seems like it's actively confusing in some cases, and in general, probably very rarely the real problem.
Thank you for reporting this!


Spike: Proxy/Dataplane/Gateway/Kong Gateway naming mess

Is there an existing issue for this?

[X] I have searched the existing issues

Problem Statement
Naming should be consistent for KOng Gateway across docs, logs, codebase, Helm chart, etc. Currently, it is referenced as

proxy (e.g. this is the name of a container with Kong Gateway deployed by Helm)
Kong proxy
 Dataplane
gateway
Kong Gateway
etc.

Proposed Solution

decide on consistent naming
implement it everywhere

Additional information
No response
Acceptance Criteria

[ ] Kong Gateway is named consistently across docs, logs, codebase, Helm chart, etc.
[ ] document it somewhere, maybe in Readme.md

This needs to be a spike because:

"Gateway" is an overloaded term (Kong Gateway, GWAPI Gateway)
"Control plane" is an overloaded term (hybrid mode CP vs KGO's managed mode CP)
"Dataplane" is likewise overloaded (hybrid mode DP vs KGO's managed mode DP)


Providing developers with alternate to QoS profile

Problem description
Today QoD API requires the application developer to pass in qosProfile as one of the mandatory params for creating POST  /sessions. as described in the yaml this qos profile can vary from each operators which puts the burden on the developers to keep themselves updated on all the qos profiles supported by each operators across the world.
I hope we all can see the problem with this. It goes against the basic CAMARA principle of requiring the APIs to be developer friendly.
Solution
Rather than the developer having to learn all the qos profile options across the different operators and figure out which suits best for their application it should be the operator's responsibility to figure out which is the best qos profile they need to apply based on the application needs as well as additional context based on user subscription data.
Proposal is to adopt the concept of application profiles as defined in connectivity insights (which is already modeled to work closely with QoD API) via which the application developers define what they expect in terms of network performance and which calling the QoD /sessions API, they can pass on application profile id as an alternate to qos profile and the operator will take on the responsibility to identify the best qos profile and create the session based on that.
Additional context
there is an open issue in commonalities on the concept of application Id. Discussions here and connectivity insights can be used as references to be adopted in commonalities.
another advantage with this proposal is that it puts us on the path of decoupling QCI based implantation to support that API request and in further the same spec can be used to provide network slice based quality on demand.

Hi @maheshc01,
The topic is interesting. Looking also into the PR, it seems like the proposal is about giving developers/applications the ability to create their own adhoc profiles, more than figuring out which of the available QoS Profiles are closer to their needs. I'm not very familiar with Connectivity Insights API, but I see that they model a policyId instead of the applicationProfileId you are proposing in the PR, are they equivalent?
To me they are 2 different requirements:

To figure out what is the best available QoS Profile, among the available ones. For this, we could enhance the qos-profiles API with some complex filters based on the profiles characteristics. But that only would make sense if implementations had lots of profiles with detailed characteristics.

To allow applications to create adhoc profiles which some required characteristics. For this, the complex part would be in the negotiation phase, when the implementation has to assure that the request can be fulfilled, which probably has to take into account many variables, such as device, requested characteristics, time interval, etc.. Also it is not clear how developers would know and negotiate/accept concepts like pricing for the request, SLAs, etc

Could you confirm if your proposal is more about the second point? Thanks

Another option could be that already the ConnectivityInsights API returns in case the requirements are beyond the standard profile one or multiple proposals of QoS Profiles which then can be directly used to create a session with the qualitiy-on-demand API.

This approach would fit quite well with the current API. If Connectivity Insights API, after evaluating the requirements, determines that certain available QoS profile fulfills those requirements, it may return it as suggestions. Developers can then examine those QoS profiles and decide to use QoD APIs. The part about pricing, SLA, etc is out of the scope of CAMARA, so probably another APIs are needed for that.

@jlurien In connectivity insights what started out as policy id which defined application needs from a network performance perspective went through its fair share of updates post multiple discussions to be renamed as application-profile to make it more developer friendly.
Application Profile takes inputs from app developers on what is the minimum values for each network performance KPI which the application is tolerant to.it doesn't take input for upper bound values.
For example a web conferencing app can say that it requires a minimum of 2 mbps uplink and minimum of 5 mbps downlink. If the network is not able to meet these requirements from any of the available QoS profiles then the API should respond saying the required quality cannot be provided so that the application can plan for contingencies on their side. As the application profile is intended to take the minimum values i think we should be good to allow it and use them for decision making.
Another example of application profile is in edge discovery service(EDS) , where via the application profile the app developer can share the minimum latency required by the app to ensure their end users have a good experience. and based on the network performance data, if there is one or more edge clouds that is able to provide the latency then EDS would return the list but in case none of the edge clouds are able to meet the latency requirement then we need to be transparent and tell that the latency requirement cannot be met so that the app developer can plan accordingly.
With the examples above i am highlighting the need for application profile in multiple sub projects and not limited to just connectivity insights and quality on demand.
Regarding the concept of using application profile to present the best set of QoS profiles to the developer. my opinion is not all subscriber will have entitlement to all qos profiles. it would be frustrating to developers to again receive failed responses based on subscriber entitlement.
Also going back to the point i have made in the additional context while creating this issue. App developers shouldn't have to care about what qos profile(telco terminology) to use or how the network operators are providing the quality on demand. Its for the operators to figure out the how part (specific QCI mapping or via NW slice mapping) and confirm if they can meet the app requirements or not.
Pricing is more complex topic but also have different approaches which the business groups can figure out.

Also going back to the point i have made in the additional context while creating this issue. App developers shouldn't have to care about what qos profile(telco terminology) to use or how the network operators are providing the quality on demand. Its for the operators to figure out the how part (specific QCI mapping or via NW slice mapping) and confirm if they can meet the app requirements or not.

@maheshc01 We tried out best to make these more generically networking centric and not just telco focused.  We may not have entirely hit the mark, but an attempt was made.  QoS Profiles actually helped us add support for fixed line networks, in addition to mobile network.  These could also apply to non-terrestrial networks (aka satellite based internet) as well, but I don't think that anyone has tested that.
Not every network will have the capabilities and capacity to support every application profile, and others will be able to support capabilities beyond and individual application.  QoD can apply to all traffic to/from a device, where this device could be a gateway on a cable or fiber network.  We don't want to limit the capabilities.
As @hdamker mentioned above, we do have issue #147 opened.  This issue has been open since QoS profiles were introduced, since the idea behind profiles was to provide a mechanism find profiles which meet the requirements for a given application or use case.
My suggestion is that we start by extending the QoS Profile to add a query mechanism to identify profiles that can meet the application requirements.  Either through profile querying based on a set of attributes or if there is a sufficient standard around the application ids.  While we are getting late into the 0.11 release, if we get consensus quickly it could make this release.
Longer term, we could look to extend the session create to allow for the QoS profile query or minimum criteria to be included instead of the QoS profile ID.  I suspect that this will be a much more involved discussion since it has far reaching implication when the developer doesn't know which profile they will use when they make the query.
The current process isn't that different from identifying the type of compute resources when spinning up cloud compute.  Even between regions within a single cloud provider, there are different classes of machines available.


Don't wait for Promise when calling setItemRaw

...turns out this is needed for reliably storing items in cache. Else the item might never be stored.


Prevented database errors from being masked by cursor close

When an error occurred during the cursor.execute statement, the cursor
is closed. This operation did not fail with client-side cursors. Now,
with server-side cursors, the close operation might fail (example
below). The original error should be raised, not the one raised by
cursor.close(), this is only clean-up code.
For example, one can attempt to create a named cursor for an invalid
query. psycopg will raise an error about the invalid query and the
server-side cursor will not be created on PostgreSQL. When the code
attempts to cursor.close(), it asks psycopg to close the cursor, which
was not created. pyscopg raises a new error: psycopg2.OperationalError:
cursor "_django_curs_140365867840512_20" does not exist.

merged in 6b6be692fcd102436c7abef1d7b3fa1d37ad4bdf, thanks!


Typescript error on optional type.

A typescript error is generated when using the v1.SubjectFilter type for the SubjectFilter.
Property 'optionalSubjectId' is missing in type '{ subjectType: string; }' but required in type 'SubjectFilter'.ts(2741) permission_service.d.ts(115, 5): 'optionalSubjectId' is declared here.
The type in question that makes the issue is the optionalSubjectId, that is not optional according to the interface generated for v1.SubjectFilter.
There is a workaround by disabling semantic checks by using // @ts-nocheck at the beginning of the file. However this kind of defeats the purpose of using typescript.

Related to https://github.com/authzed/authzed-node/issues/53

@MadsKK Are you using .create to construct the v1.SubjectFilter message instances? That helper method allows you to omit optional fields when creating messages. Unfortunately, there is a disconnect between the name of that field and the semantics of the ts code generator.
See this comment for more context https://github.com/authzed/authzed-node/issues/33#issuecomment-1229068258

@samkim Okay, that seems to fix the problem.
I was setting subjectFilter as a variable instead of setting it directly inside the .create function.
It seems that everything just has to be created inside the .create function.
Thanks for the clarification :)

No problem, glad that worked!


Crash during debugger

After launching the debugger via XCode on my iPhone device, I get this error .. if I run the application without debugger it works correctly..
-[MTLDebugDevice validateNewBufferArgs:options:]:366: failed assertion newBufferWith*:length 0x20000000 must not exceed 256 MB.'

Try to disable Metal API Validation in scheme settings. It definitely works :)

Ok, thanks, it works


laravel 5.4 not working current theme

laravel 5.4 not working current theme fixed.

Cool. Is this backwards compatible to ~5.0?
I'm pretty sure I tried this approach in the beginning but it didn't work.


Import Error : Not able to import mavsdk python module in Ubuntu 20.04.1

Ubuntu Version :20.04.1
Device : Raspberry Pi4
While installing mavsdk python module,
Ubuntu Home Screen freezes at Building wheel for grpcio (setup.py) ...
no further progress..then pi has to reboot using main power
But mavsdk python module successfully installed on my linux mint on lenovo laptop
Is mavsdk module has issues with arm64 version??
Help Me Out!!!!!

Any issues of Grpcio with python version Python 3.8??


conda-forge

We are working on using conda-forge for the distribution of discretize (see: simpeg/discretize#69). For this, we need dependencies to also be distributed through conda-forge. Would you be willing to put properties (and vectormath) on conda-forge?
https://conda-forge.org/docs/recipe.html

Ok! I'll check it out.

@lheagy - properties (and vectormath) are now on conda-forge! One minor note - properties.ImagePNG isn't supported directly through the conda distribution since pypng isn't on conda-forge. A future release of properties should be able to work around this by including the pypng code, but I'm assuming this isn't a problem for discretize?
Looking forward to seeing discretize, etc find their way to conda-forge.
https://anaconda.org/conda-forge/properties

@fwkoch you can package pypng on conda-forge if you want. There is no restriction on being the original author (though that usually helps).

thank you @fwkoch!


Use log levels for debug logging.

There's some info on how to do that on the django site.

Setting the log level now determines if things are printed or not.


allow cache "prefilling" / preloading

hey again ;-)
i'm starting to use the iconic set with my current angular project ad i'd like to "preload" few icons and put them into the cache.
currently, it's not available and i need to load the icons the "normal" way.
it would be great to have something like
/**
 * parses data and adds it to the cache on success
 * @param  {String}      url  url to cache it at
 * @param  {String|Node} data SVG (data or string) to parse
 * @return {Boolean}          true on success,
 *                            false on failure
 */
function preload( url, data ) {
  // ...
}

that would eventually parse the data and return Boolean result of the "preloading".
Would you implement that, or do you prefer PR?
this method would improve loading speed of my icons a bunch, since i could just inline the SVGs and "preload" them before injecting the icons :-)
what do you think?

This is implemented and documented on my fork.
It has an optional png argument to the end of the request to allow for a fallback to be specified to override the global fallback in SVGInjector. This allows it to work with cachekeys that don't represent urls ex. "jspm:foo.svg!"

@npbenjohnson I'm not JavaScript literate. Could you provide an example of what to place in the script to enable caching of the SVG. Currently, the code is working well but it reloads with the page reload, unlike the original img. I am aware that this is an old project, but any help would be most appreciated.


apugli:edible_item doesn't consume items when finished "eating" if apoli:modify_food is on the entity

This power when consumed only executes entity_action but doesn't actually remove the specified item if the power holder has apoli:modify_food power type already.
Example Power:
{
    "type": "apoli:multiple",
    "breaker": {
        "type": "apoli:modify_food"
    },
    "eat": {
        "type": "apugli:edible_item",
        "item_condition": {
            "type": "origins:ingredient",
            "ingredient": {
                "item": "minecraft:stick"
            }
        },
        "food_component": {
            "hunger": 1,
            "saturation": 0.5,
            "meat": false,
            "always_edible": true,
            "snack": true
        },
        "use_action": "eat",
        "entity_action": {
            "type": "origins:execute_command",
            "command": "say HMMM reusable food source!"
        }
    }
}

To quote myself elsewhere

Fixed on my end. I'm unsure how the new changes will co-operate with the Modify Food power but you can report any other bugs to me.
Will be released in Apugli v1.8.0


Create README.md

This adds a README.md file with a link to developers.google.com
Fixes #1973 and related to #1987

I like this. Just two things:

Like the bot says, you need to sign the Google CLA.
Please modify the commit message to mention where the text was copied from, since it was.

Thanks, I signed it!

I also updated the commit message.


Implemented MultiChannel logic, calculate_channel_urls and get_channe…

…l_urls
I started reimplementing all the MultiChannel logic with composite pattern and so on until I realize we just don't need them.

What's going on here? The build is systematically cancelled.

I haven't cancelled anything. Either github is has issues or they want us to pay for CI time?


'BugsnagReactNative/BugsnagReactNative.h' file not found

Hi,
Unable to build ios project for react-native. Getting the following error when trying to build:

Followed the instructions for installation and it works fine on macbook 1. cloned my repo on macbook 2 and tried to build the project but it is failing.
my build phases link binaries:

Version
react-native 0.44.1
<EMAIL_ADDRESS>xcode 9.1
regards
Tejas

Hi @tejas-syook - thanks for the report. I'm having trouble reproducing this on a fresh project, would you be able to try the following steps after cleaning + deleting derived data?

yarn add bugsnag-react-native --save
react-native link
Add #import <BugsnagReactNative/BugsnagReactNative.h> to AppDelegate

If that doesn't work it may potentially be worth changing the order of libBugsnagReactNative.a so that it's at the top. Are you using npm to install everything?

I am using npm.
Tried changing the order for libBugsnagReactNative.a, didn't work.
deleted the xcworkspace and did a pod install. Now i am getting a different error

@tejas-syook that error message sounds similar to the following Cocoapods issue. Does the error still occur if you delete Pods, Podfile.lock, and run pod install again? Setting Build Active Architectures Only to NO also appeared to work for some users.
Are you able to build the Cocoapods example project? https://github.com/bugsnag/bugsnag-react-native/tree/master/examples/ios-cocoapods-component

@tejas-syook are you still running into trouble with building the project, or has this been resolved?

The error is still there. We'll update by weekend.
On Thu, Nov 16, 2017 at 3:30 PM, Jamie Lynch<EMAIL_ADDRESS>wrote:

@tejas-syook https://github.com/tejas-syook are you still running into
trouble with building the project, or has this been resolved?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bugsnag/bugsnag-react-native/issues/181#issuecomment-344873825,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AftNRfDouMVTPV4n6ikY6v3sL3pH1TXzks5s3Ae2gaJpZM4QbYkj
.

Also getting this error with bugsnag linked.

@tejas-syook out of interest is there any difference between your first and second Macbook model? Is there any difference between your build/installation process on the two models e.g. running on a physical device on one, and a simulator on another?

The macbook models are different, one is MD-101 mid 2012 (build error) and the other is a Retina mid 2014 (build working). Building for simulators on both. I also installed it on an iMac late 2013 but getting the same build error there also. I will try to troubleshoot over the weekend and will update.

My build is successful through react-native run-ios but I can't build it using Xcode because 'BugsnagReactNative/BugsnagReactNative.h' file not found

This worked for me.

Build Active Architecture is set to No for all projects and pods.
I tried deleting the pods and reinstalling. Didn't work!
Unlinked and removed bugsnag and now I am getting the following errors:

I'm using Xcode 9.1 and I fixed this issue importing this in this way:
#import <BugsnagReactNative.h>
on AppDelegate.m.

Im having the same issue while Im using another Staging scheme on Xcode 9.1
Any through to why I get such an error when linking?

Hey everyone, there's a few different issues in a single thread, though I'll try to resolve each. I'm also going to update the title to add new details.
Using bugsnag-react-native with CocoaPods
If using CocoaPods to import BugsnagReactNative, react-native link [bugsnag-react-native] should not be used, as the library is being included already via libPods.a. The resolution is to delete libBugsnagReactNative.a from the "Link Binaries with Libraries" section.
The Bugsnag+CocoaPods example project explains how each of the components work together. Though its geared towards developers adding React Native to an existing iOS app, the core configuration (and Podfile) is the same, as well as the explanations of the React Native internals.
I recommend running the example app to see if it works for you, so we can more quickly narrow down what configuration is different.
As a general note, when changing files outside of Xcode (e.g. via package managers), using Option + Product > Clean in the Xcode menu to clear the build folder reduces headaches significantly, as its not uncommon to have Xcode build artifacts in an inconsistent state when using package managers.
Comments

Unlinked and removed bugsnag and now I am getting the following errors:
[Screenshot]

@tejas-syook was this after opening the the *.xcodeproj and not the *.xcworkspace? I've done this myself a few times.

Im having the same issue while Im using another Staging scheme on Xcode 9.1
Any through to why I get such an error when linking?

@wprater Does the scheme use a different target? If using CocoaPods, there would need to be an entry for each target you need to use, for example:
target 'MyApp' do
  platform :ios, '10.3'
  rn_pods
end

target 'MyAppStaging' do
  platform :ios, '10.3'
  rn_pods
end

def rn_pods
  # React Native requirements
  pod 'yoga', path: './node_modules/react-native/ReactCommon/yoga'
  pod 'DoubleConversion', :podspec => './node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
  pod 'Folly', :podspec => './node_modules/react-native/third-party-podspecs/Folly.podspec'
  pod 'GLog', :podspec => './node_modules/react-native/third-party-podspecs/GLog.podspec'
  # These seem to be the required subspecs, for some reason or other
  pod 'React', path: './node_modules/react-native', subspecs: [
    'Core',
    'jschelpers',
    'cxxreact',
    'CxxBridge',
    'DevSupport',
    'RCTActionSheet',
    'RCTAnimation',
    'RCTImage',
    'RCTNetwork',
    'RCTText',
    'RCTWebSocket',
  ]

  pod 'BugsnagReactNative', path: './node_modules/bugsnag-react-native'
end

pod install would then link the correct target.

I was using . xcworkspace all the while.
@krosti your solution worked!
The issue with Mach-O linker was resolved by setting Build Active Architectures Only to YES for  for all the libraries linked for debug mode and No for staging and release.

This seems to be an issue with setting up BugSnag in a project that uses CocoaPods. To resolve this issue I did the following:

Open your project in Xcode
Run open node_modules/bugsnag-react-native/cocoa
Drag BugsnagReactNative.xcodeproj into your Libraries group
Select your main project in the navigator to bring up settings
Under Build Phases expand the Link Binary With Libraries header
Scroll down and click the + to add a library
Find and add libBugsnagReactNative.a and libz.tbd under the Workspace group
⌘+B


inception score on coco pretrained model is 8.50526228697

@hanzhanggit The readme says
Our current implementation has a higher inception score(10.62±0.19) than reported in the StackGAN paper

With the provided pre-trained model, I get 8.50526228697. Is the 10+ score for StackGAN v2?

@kracwarlock
No. The inception score (10.62±0.19) is calculated from the Pytorch model of  stackgan-v1

I was unable to get that from the available pre-trained model in the repo. Can you share the evaluation code for the pytorch model?
How many images did you calculate this over and what were the splits?

@kracwarlock @hanzhanggit @taoxugit Please tell me the path details.
I put my coco train images into data/coco folder so the complete path is "H://StackGAN-Pytorch/data/coco"
and put the preprocessed char-CNN-RNN text embeddings  training coco, and saved it to data/coco/train and test folders.... complete path is H://StackGAN-Pytorch/data/coco/train" and H://StackGAN-Pytorch/data/coco/test"
As well as put the preprocessed char-CNN-RNN text embeddings evaluating coco, and save it to data folder complete path is H://StackGAN-Pytorch/data/coco/test"
now tell me these paths are ok or not? and where I put the coco val images? Are any other things are needed?
Strongly waiting for your's response....
thank you very much


Resolution 640 x 480 not supported

Hi,
I am using example-3, stream to a Wowza Media Server, i am getting errors when i selecting high and medium resolutions above [320 x 240 30fps, 250kbps] streaming get's green color and when i select [640 x 480] app raising the exception as follows and not connecting to stream engine.
is there any solution to work with high resolution?
ERROR: net.majorkernelpanic.streaming.exceptions.ConfNotSupportedException: start failed.

A fair number of android devices are bugged and advertise that they support resolutions and configurations when they actually don't. Try resolutions listed as mandatory/strongly reccomended as listed in the compatibility doc.
like 720x480, or 1280x720. However, you're probably being bottle necked by bitrate at the moment, so try doubling that first.

Thanks for information.
One more issue on orientation when i set  setPreviewOrientation(90)  rtmp streaming also rotating, but the device must be with portrait setPreviewOrientation(90) , is there any solution?

I encountered the same problem. google says that setPreviewOrientation only
affects the surface output. does not affects the Camera.PreviewCallback
nv21 data...so i think you have to use the landscape theme.. or rotate data
yourself.. if you have any other solution, please share for us. thanks.
2016-09-21 19:57 GMT+08:00 Shankar<EMAIL_ADDRESS>
Thanks for information.
One more issue on orientation when i set setPreviewOrientation(90) rtmp
streaming also rotating, but the device must be with portrait
setPreviewOrientation(90) , is there any solution?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fyhertz/libstreaming/issues/239#issuecomment-248589902,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE6EyrrQuWQgIaZGRWWbUkY-OVRiIHhZks5qsRuYgaJpZM4KCo1y
.

--
bestwishes
Paul Guo
thanks with love!!

I just use the 1080p resolution, and it works fine, but the phone can not
handle the data that quickly and quality is very bad, so just use 720p
instead. You can comment the errors and enlarge the time named 'elapased in
EncoderDebugger.java or make some other very small fix.
2016-09-21 18:25 GMT+08:00 Shankar<EMAIL_ADDRESS>
Hi,
when selecting the resolution above [320 x 240 30fps, 250kbps] streaming
get's green color and when i select [640 x 480] app raising the exception
as follows and not connecting to stream engine.
is there any solution to work with high resolution?
ERROR: net.majorkernelpanic.streaming.exceptions.ConfNotSupportedException:
start failed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fyhertz/libstreaming/issues/239, or mute the thread
https://github.com/notifications/unsubscribe-auth/AE6Eyhpy6hE5Z80qrKTcQZZhS_jUT1Aoks5qsQYUgaJpZM4KCo1y
.

--
bestwishes
Paul Guo
thanks with love!!

I have software rotation in this rtsp streamer project and work well for me in 1080p. Check YUVUtil in encoder module if you only want rotation methods.
https://github.com/pedroSG94/rtmp-rtsp-stream-client-java

I have the same question like @shankar667.
I try to enlarge "elapased" in EncoderDebugger.java, but it still can't work for high quality(720p).
@Paul-Guo Do you mean the range of "elapased"? Ex: while(elapsed<3000000)??


Add startPath option

Right now you can get curve's code by clicking the code button and copying the path coordinates from there.
Something like this: M0, 100 C0, 100 28.155286227103208, 95.35825418399047 30, 52.42857142857143 C31.844713772896824, 9.498888673152383 75.15078407720145, 24.857142857142858 75.15078407720145, 24.857142857142858 C75.15078407720145, 24.857142857142858 100, 0 100, 0
We need to do the opposite - parse this path coordinates data back to js objects:
// an array of points, where each point has the next structure:
point: {
     x: 30,
     y: 52.42,
     handle1: {x:28.15, y: 95.35},
     handle2: {x:31.84, y: 9.49}
}

There is how the SVG path data maps to js objects:
/*
  Input: M0, 100 C0, 100 28.155286227103208, 95.35825418399047 30, 52.42857142857143 C31.844713772896824, 9.498888673152383 75.15078407720145, 24.857142857142858 75.15078407720145, 24.857142857142858 C75.15078407720145, 24.857142857142858 100, 0 100, 0

  Sudo: [point1] [point1.handle2] [point2.handle1] [point2] [point2.handle2] [point3.handle1] [point3] [point3.handle2] [point4.handle1] [point4]

  Output:
    point1:
     x: 0, y: 100,
     handle2: x:0, y: 100

    point2:
     x: 30, y: 52.42857142857143,
     handle1: x:28.155286227103208, y: 95.35825418399047
     handle2: x:31.844713772896824, y: 9.498888673152383

    point3:
     x: 75.15078407720145, y: 24.857142857142858,
     handle1: x:75.15078407720145, y: 24.857142857142858
     handle2: x:75.15078407720145, y: 24.857142857142858

    point4:
     x: 100, y: 0
     handle1: x: 100, y: 0
*/

We can use getPathData polyfill that will make the parsing of theSVG coordinates data simple. After this, we need to fire few redux actions to send this data to redux store which will update components automatically. With this functionality, we can easily add startPath option to the curve editor which will allow launching(loading) the plugin with a predefined path - import the path back.
If you have any question, please feel free to ask, would love to help!
Cheers!

Will do

Oh, nice! This one will be big. 👍

Please, take a look
https://github.com/legomushroom/mojs-curve-editor/pull/15

Merged: #15


Calling AudioPlayer stop() then change scene induces music stuttering that lasts a few seconds

Godot version:
3.2.3 stable
OS/device including version:
Linux
Issue description:
I don't know if this bug is fixed by  #43210 or not as it's a different issue.
Basically, on Linux Chromium (I haven't tried Windows Chrome, I don't have it) when I stop music then change scenes the last element of the music repeat and stutters for 2 to 3 few seconds until the scene is loaded and sounds truly awful.
I have tried before changing scene:

Calling stop() - still stutters
setting pause - still stutters
setting volume to -80 - still stutters
Attaching to the audio player music finished signal then starting scene - still stutters

The only thing that has worked, and it's a pretty crap solution, is I attach a timer and wait 2 seconds after I call stop() on the music player.
Firefox Linux is ok.
Steps to reproduce:
Happy to show it working on my web server...
Minimal reproduction project:
Any combination of the below with the change scene...
		$AudioStreamPlayer.volume_db=-80
		$AudioStreamPlayer.pause_mode=true
		$AudioStreamPlayer.stop()
                get_tree().change_scene("res://scenes/Game.tscn")

btw, sorry to digress. I presume this is a browser bug and not Godot and not related to the above, but it might be. In Chromium you get no audio when a game starts, e.g. your startup logo/intro, until you click the mouse. On all other browsers it is fine. It means if you start your menu/splash with music it fails to start on Chromium. It means you have to introduce a silly 'click me' scene at the start of a Godot game.bypass this first scene.

I'd try using 3.2.4rc3 and exporting with threads enabled in the export preset to see if this is caused by the lacl of threads in HTML5. Enabling threads will also decrease sound latency.

But it's fine on Firefox?
I will try, but if not it's either suggest to players on Linux they have awful sound on Chrome or 10fps on Firefox ;-)

But it's fine on Firefox? Did you get time to read my comment above adding to the issue as I typed it late?

Yes 🙂

But it's fine on Firefox? Did you get time to read my comment above adding to the issue as I typed it late?

Yes slightly_smiling_face

and? is this a bug or Chrome feature?

@chucklepie Please upload a minimal reproduction project to make this easier to troubleshoot.

@Calinou No, I have tried it and it is even worse. See #46733

I also have this problem in the current stable version, not only in chrome but in safari as well.
The path to reproduce this erros in my case is more or less like this:
user clicks button, button plays a click audiostream wav file sound, I wait for the 'finished' signal, load another scene, sound is playing stuttering until the end of loading the new scene

@chucklepie I agree that a minimal reproduction project would help in helping troubleshoot the issue

Closing due to lack of response. Please comment if you can still reproduce this bug.
PS: If no minimal reproduction project was included in the original bug report, please upload one as well to ease troubleshooting.


Add predict_proba and threshold in cnn,bilstm

Description
Add proba function to NN to be able to return probabilities and also add threshold to be able to predict with different thresholds
Checklist

[x] Added link to Github issue or Trello card
[x] Added tests

 Add proba function and threshold parameter to NN architectures to be able to lower the threshold for predictions

Codecov Report

Merging #166 into master will decrease coverage by 0.49%.
The diff coverage is 46.15%.

@@            Coverage Diff             @@
##           master     #166      +/-   ##
==========================================
- Coverage   81.41%   80.91%   -0.50%
==========================================
  Files          39       39
  Lines        1985     2007      +22
==========================================
+ Hits         1616     1624       +8
- Misses        369      383      +14

Impacted Files
Coverage Δ

wellcomeml/ml/bilstm.py
89.55% <46.15%> (-4.76%)
:arrow_down:

wellcomeml/ml/cnn.py
90.07% <46.15%> (-4.55%)
:arrow_down:

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 6b7503a...597ed02. Read the comment docs.

@aCampello btw i altered the code a bit since sparse_y does not make sense for probs which are dense. let me know if this does not make sense

Makes sense, actually!


[PHPStan Rules] Problem after updating to 9.0.39

Hi,
After updating symplify/phpstan-rules to 9.0.39, I get following error
Service of type Symplify\PHPStanRules\CognitiveComplexity\NodeVisitor\NestingNodeVisitor:
Service of type Symplify\PackageBuilder\Php\TypeChecker needed by $typeChecker in __construct() not found.
Did you add it to configuration file?

My configuration looks like this:
includes:
    - phpstan-baseline.neon
    - ../vendor/symplify/phpstan-rules/packages/cognitive-complexity/config/cognitive-complexity-rules.neon
    - ../vendor/symplify/phpstan-rules/config/services/name-resolver-services.neon

rules:
    - Symplify\PHPStanRules\Rules\NoDefaultExceptionRule

parameters:
    level: max
    paths:
        - "../app/"
        - "../config/"
        - "../tests/"
    excludes_analyse:
        - '../tests/fixtures/'
    inferPrivatePropertyTypeFromConstructor: true
    checkMissingIterableValueType: false
    checkGenericClassInNonGenericObjectType: false

services:
    -
        class: Symplify\PHPStanRules\CognitiveComplexity\Rules\FunctionLikeCognitiveComplexityRule
        tags: [phpstan.rules.rule]
        arguments:
            maxMethodCognitiveComplexity: 60

    -
        class: Symplify\PHPStanRules\CognitiveComplexity\Rules\ClassLikeCognitiveComplexityRule
        tags: [phpstan.rules.rule]
        arguments:
            maxClassCognitiveComplexity: 60

    -
        class: Symplify\PackageBuilder\Matcher\ArrayStringAndFnMatcher

I haven't found which configuration/adjustment that I'm missing.

Hi,
thanks for detailed description.
Is it possible this is the same issue?
https://github.com/symplify/symplify/issues/2798

Hi,
thanks for detailed description.
Is it possible this is the same issue?
https://github.com/symplify/symplify/issues/2798

Looks similar, but if I do it like suggested there. I get the error that the
In Resolver.php line 442:

  Service of type Symplify\PHPStanRules\Rules\ForbiddenFuncCallRule: Multiple services of type Symplify\PackageBuilder\Matcher\ArrayStringAndFnMatcher found: 0250, 0296 (needed by $arrayStringAndFnMatcher in __construct())

In Autowiring.php line 50:

  Multiple services of type Symplify\PackageBuilder\Matcher\ArrayStringAndFnMatcher found: 0250, 0296

Looks similar, but if I do it like suggested there. I get the error that the
In Resolver.php line 442:

  Service of type Symplify\PHPStanRules\Rules\ForbiddenFuncCallRule: Multiple services of type Symplify\PackageBuilder\Matcher\ArrayStringAndFnMatcher found: 0250, 0296 (needed by $arrayStringAndFnMatcher in __construct())

In Autowiring.php line 50:

  Multiple services of type Symplify\PackageBuilder\Matcher\ArrayStringAndFnMatcher found: 0250, 0296

That means that some services are registered twice.
Probably here:
    - ../vendor/symplify/phpstan-rules/packages/cognitive-complexity/config/cognitive-complexity-rules.neon
    - ../vendor/symplify/phpstan-rules/config/services/name-resolver-services.neon

That means that some services are registered twice.
Probably here:
    - ../vendor/symplify/phpstan-rules/packages/cognitive-complexity/config/cognitive-complexity-rules.neon
    - ../vendor/symplify/phpstan-rules/config/services/name-resolver-services.neon

This brings me closer.
includes:
    - phpstan-baseline.neon
    - ../vendor/symplify/phpstan-rules/config/services/services.neon

rules:
    - Symplify\PHPStanRules\Rules\NoDefaultExceptionRule

parameters:
    level: max
    paths:
        - "../app/"
        - "../config/"
        - "../tests/"
    excludes_analyse:
        - '../tests/fixtures/'
    inferPrivatePropertyTypeFromConstructor: true
    checkMissingIterableValueType: false
    checkGenericClassInNonGenericObjectType: false

services:
    -
        class: Symplify\PHPStanRules\CognitiveComplexity\Rules\FunctionLikeCognitiveComplexityRule
        tags: [phpstan.rules.rule]
        arguments:
            astCognitiveComplexityAnalyzer: Symplify\PHPStanRules\CognitiveComplexity\AstCognitiveComplexityAnalyzer
            maxMethodCognitiveComplexity: 60

    -
        class: Symplify\PHPStanRules\CognitiveComplexity\Rules\ClassLikeCognitiveComplexityRule
        tags: [phpstan.rules.rule]
        arguments:
            astCognitiveComplexityAnalyzer: Symplify\PHPStanRules\CognitiveComplexity\AstCognitiveComplexityAnalyzer
            maxClassCognitiveComplexity: 60

But need to find out how to add the arguments as objects instead of strings

This brings me closer.
includes:
    - phpstan-baseline.neon
    - ../vendor/symplify/phpstan-rules/config/services/services.neon

rules:
    - Symplify\PHPStanRules\Rules\NoDefaultExceptionRule

parameters:
    level: max
    paths:
        - "../app/"
        - "../config/"
        - "../tests/"
    excludes_analyse:
        - '../tests/fixtures/'
    inferPrivatePropertyTypeFromConstructor: true
    checkMissingIterableValueType: false
    checkGenericClassInNonGenericObjectType: false

services:
    -
        class: Symplify\PHPStanRules\CognitiveComplexity\Rules\FunctionLikeCognitiveComplexityRule
        tags: [phpstan.rules.rule]
        arguments:
            astCognitiveComplexityAnalyzer: Symplify\PHPStanRules\CognitiveComplexity\AstCognitiveComplexityAnalyzer
            maxMethodCognitiveComplexity: 60

    -
        class: Symplify\PHPStanRules\CognitiveComplexity\Rules\ClassLikeCognitiveComplexityRule
        tags: [phpstan.rules.rule]
        arguments:
            astCognitiveComplexityAnalyzer: Symplify\PHPStanRules\CognitiveComplexity\AstCognitiveComplexityAnalyzer
            maxClassCognitiveComplexity: 60

But need to find out how to add the arguments as objects instead of strings

It works for me with with this config.
includes:
    - phpstan-baseline.neon
    - ../vendor/symplify/phpstan-rules/config/services/services.neon
    - ../vendor/symplify/phpstan-rules/packages/cognitive-complexity/config/cognitive-complexity-rules.neon

rules:
    - Symplify\PHPStanRules\Rules\NoDefaultExceptionRule

parameters:
    level: max
    paths:
        - "../app/"
        - "../config/"
        - "../tests/"
    excludes_analyse:
        - '../tests/fixtures/'
    inferPrivatePropertyTypeFromConstructor: true
    checkMissingIterableValueType: false
    checkGenericClassInNonGenericObjectType: false

It works for me with with this config.
includes:
    - phpstan-baseline.neon
    - ../vendor/symplify/phpstan-rules/config/services/services.neon
    - ../vendor/symplify/phpstan-rules/packages/cognitive-complexity/config/cognitive-complexity-rules.neon

rules:
    - Symplify\PHPStanRules\Rules\NoDefaultExceptionRule

parameters:
    level: max
    paths:
        - "../app/"
        - "../config/"
        - "../tests/"
    excludes_analyse:
        - '../tests/fixtures/'
    inferPrivatePropertyTypeFromConstructor: true
    checkMissingIterableValueType: false
    checkGenericClassInNonGenericObjectType: false

Yes, exactly :)
I though I've linked the exact comment in next reply, but the comment was not sent.
https://github.com/symplify/symplify/issues/2798#issuecomment-760150619
You've figured out :+1:

Yes, exactly :)
I though I've linked the exact comment in next reply, but the comment was not sent.
https://github.com/symplify/symplify/issues/2798#issuecomment-760150619
You've figured out :+1:

I saw you comments, with the references. But I disappear again somehow shortly after reading it, so when I wanted to read it again it was gone. And couldn't find it in my notifications or here.

I saw you comments, with the references. But I disappear again somehow shortly after reading it, so when I wanted to read it again it was gone. And couldn't find it in my notifications or here.

Intersting :D

Intersting :D


Music assistant does not reload HASS pluggin when HASS restarts

What version of Music Assistant has the issue?
2.1.4
What version of the Home Assistant Integration have you got installed?
2024.8.0
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

[X] Yes

The problem
Every time I restart Home Assistant, the Music Assistant Plugin for Home Assistant does not reload properly and tells me that the plugin hasn't loaded yet. The logs indicate that it tries to connect to home assistance only once after 5 seconds and then stops.
I am running a bit of a unique setup. I have a 5 node Kubernetes cluster in my house and all of my home services run on that. The web-accessible services are exposed via Traefik ingress routes and I have DNS set up to point *.quitman.lan to the traefik instance. Both home assistant and music-assistant are accessible on my local network at home-assistant.quitman.lan and music-assistant.quitman.lan respectively.
Additionally, I have exposed them on a Layer2 IP address via a Kubernetes LoadBalancer service and metallb so they are accessible at <IP_ADDRESS> (home-assistant) and <IP_ADDRESS> (music-assistant).
Lastly, when communicating within the cluster they are available at the hostnames home-assistant and music-assistant.
I tried to use the intra-cluster hostnames when first setting it up and had some weird results because pod/service IP addresses are ephemeral and streaming back to my media devices couldn't resolve the correct hostnames. Using the local DNS also gave me some weird behavior. It appears that the static IPs assigned from the LoadBalancers work just fine when communicating between the 2 services.
At any rate, I think the problem might be that MASS is not retrying it's connection to home assistant. As previously stated, it says (in the logs) that it will try to connect again in 5 seconds, but then throws an exception 5 seconds later. The Kubernetes Home Assistant pod takes about a minute to come back online when it's restarted which obviously is far outside the 5 second timeout.
How to reproduce
I'm not sure if there's any way to easily reproduce this, other than deploying a minikube cluster with some manifests I could write up.
Music Providers
YouTube Music
Player Providers
Home Assistant
Full log output
music-assistant.log
Additional information

What version of Home Assistant Core are your running
2024.8.1
What type of installation are you running?
Home Assistant Core
On what type of hardware are you running?
Generic x86-64 (e.g. Intel NUC)

This is actually already on the backlog https://github.com/orgs/music-assistant/projects/2/views/1?pane=issue&itemId=72559628
I will probably close this soon as the issue is being tracked internally and because your setup is not supported. Thanks for reporting though with excellent detail

This is fixed in 2.2.0 beta 8 - if the fix is confirmed working, it will also be included in the patch release 2.1.5 for the stable version

Yes this is confirmed. Takes about a minute but reconnects automatically

@marcelveldt @OzGav thank you!

Can confirm that it works on my system
2024-08-23 16:25:42.279 INFO (MainThread) [music_assistant.hass] Connection to HA lost. Connection will be automatically retried later.
2024-08-23 16:25:47.292 WARNING (MainThread) [music_assistant] Error loading provider(instance) Home Assistant: Cannot connect to host <IP_ADDRESS>:80 ssl:default [Connect call failed ('<IP_ADDRESS>', 80)] (will be retried later)
2024-08-23 16:27:47.300 INFO (MainThread) [music_assistant] Loaded plugin provider Home Assistant
2024-08-23 16:27:47.324 INFO (MainThread) [music_assistant] Loaded player provider Home Assistant MediaPlayers


console: tty: Remove dependency on older "consoles"

Console subsystem doesn't depend on older consoles-in-drivers, the
only common thing between them is CONFIG_UART_CONSOLE_ON_DEV_NAME
setting, so make it so (by depending on either UART_CONSOLE or
CONSOLE_SUBSYS.
Signed-off-by: Paul Sokolovsky<EMAIL_ADDRESS>

This comes from the fact that MicroPython build for arduino_101 started to overflow ROM, and looking at what is superfluous there.

Codecov Report

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

@@           Coverage Diff           @@
##           master   #13731   +/-   ##
=======================================
  Coverage   52.24%   52.24%
=======================================
  Files         307      307
  Lines       45413    45413
  Branches    10508    10508
=======================================
  Hits        23726    23726
  Misses      16898    16898
  Partials     4789     4789

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 23ba884...f3acc13. Read the comment docs.

ping


Realsense driver fails to build on OS X

System Configuration

Version
Your Configuration

Operating System
OS X 10.11.2

Kernel
?-?-?

ROS
indigo

ROS RealSense
1.8.0

librealsense
1.12.1

Camera Type-Firmware
zr300 (but doesn't matter)

Expected Behavior
Can build driver under OS X.
Actual Behavior
Compilation fails with an error:
/Users/helen/catkin_ws/src/realsense/realsense_camera/src/base_nodelet.cpp:1277:30: error: use of undeclared identifier 'environ'
      execvpe(argv[0], argv, environ);

Upon fixing the environ error (by adding:
#define _GNU_SOURCE
#include <unistd.h>
extern char** environ;

)
I get a new error:
/Users/helen/catkin_ws/src/realsense/realsense_camera/src/base_nodelet.cpp:1275:7: error: use of undeclared identifier 'execvpe'; did you mean 'execve'?
      execvpe(argv[0], argv, environ);
      ^~~~~~~
      execve
/usr/include/unistd.h:444:6: note: 'execve' declared here
int      execve(const char *, char * const *, char * const *) __WATCHOS_PROHIBITED __TVOS_PROHIBITED;
         ^

It appears that execvpe() isn't defined on OS X -- http://stackoverflow.com/questions/28313542/executing-a-command-with-execvpe-in-c#comment44979436_28313542
It seems like that part of the code is only for switching the PID of the process -- is this necessary in all cases? Or can this part just be skipped on OS X?
Any help is appreciated.
Thanks,
Helen

Are you trying to build the ROS camera node itself under Mac OS?  We've only used Ubuntu 14.04 and 16.04 with ROS to date.  Would love to learn more about ROS on Mac.

Yes, installed using Mike Purvis's instructions: https://github.com/mikepurvis/ros-install-osx
After just commenting out the offending line, the node mostly works under OS X except for the IMU on the ZR300, which gets 2-3 callbacks in and then stops (while everything works fine with the same driver on 14.04). Camera and depth data come in without issue though.

Yes, I've seen the same behavior with the ZR300 camera on Mac, for IMU data stream.  I'd love to see if anybody could debug that that submit a PR to http://github.com/IntelRealSense/librealsense.  I haven't had time myself, and it is not an area the librealsense team is looking at as a priority.
I'd like to keep the master branch clean for ROS on Ubuntu/Debian, but would be happy to host a experimental branch for Mac support and accept any PR's you might choose to submit for support.

[Please Ignore - RealSense system comment]

[Please Ignore - RealSense system comment]

Close this issue for lack of activity. Please feel free to reopen if the issue is still relevant.


Re-work internal code of ABM stuff, to allow interactive evolution

The parameter slider app needs to be updated still. On Monday.

Can you give me push access here? I can fix this up—it's definitely an issue.

Can you give me push access here? I can fix this up—it's definitely an issue.

I gave you access. However the daisyworld model worked for me

I gave you access. However the daisyworld model worked for me

Yes, daisyworld works because shape color and size are all functions.

Yes, daisyworld works because shape color and size are all functions.

so all okay now? everything works?

so all okay now? everything works?

Is there a reason why abm_plot displays the figure? It's getting annoying, since it displays the figure in atom which overrides the resolution I set manually.

Is there a reason why abm_plot displays the figure? It's getting annoying, since it displays the figure in atom which overrides the resolution I set manually.

good point; no there is no reason to display the figure

good point; no there is no reason to display the figure

Also, I'm having issues with extending things, but am only working sporadically.

Also, I'm having issues with extending things, but am only working sporadically.

what kind of issues?

what kind of issues?

At the moment, updating plots from abm_plot.
For schoolyard.jl
f, abmstepper = abm_plot(model, as = 15, scatterkwargs = (xlims = (0, 100), ylims = (0, 100)))
ax = contents(f[1, 1])
scatter!(ax, [50], [50]; color = :red)

I can't get the additional scatter call to work. It's fine on its own, or an empty plot, but not with the one returned here.

At the moment, updating plots from abm_plot.
For schoolyard.jl
f, abmstepper = abm_plot(model, as = 15, scatterkwargs = (xlims = (0, 100), ylims = (0, 100)))
ax = contents(f[1, 1])
scatter!(ax, [50], [50]; color = :red)

I can't get the additional scatter call to work. It's fine on its own, or an empty plot, but not with the one returned here.

Necessary progress have been done here to warrant a bump in patch version. I'm tagging now.

Necessary progress have been done here to warrant a bump in patch version. I'm tagging now.


JsonDecodingExecption

Source information
Aniwave 14.66 (English)
Source language
English
Steps to reproduce

First step (open any anime)
Issue here (it says "JsonDecodingException: Unexpected JSON token at offset 23: Expected string literal but 'null' literal was found at path: $.result Use 'coerceInputValues = true' in 'Json {}' builder to coerce nulls to default values. JSON input: {"status":403,"result":null,"message":"Request is invalid.","messages":["Request is invalid."]}")

Expected behavior
I'm just gonna watch some anime.
Actual behavior
Then this happened
Aniyomi version
<IP_ADDRESS>
Android version
Android 13
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Duplicate of #3100


data isn't updating

Hello,
I created a dashboard today to try and display how many instances are up in our aws environments.
require 'aws-sdk'

def display_env(env, creds)
  ec2 = Aws::EC2::Resource.new(credentials: creds)
  terminated = Proc.new {|instance| instance.state[:name] == "terminated" || instance.state[:name] == "shutting-down" }
  total_num_dead_instances = ec2.instances.select(&terminated).count
  total_num_alive_instances = ec2.instances.reject(&terminated).count

  found = []
  autoscaling = Aws::AutoScaling::Client.new(credentials: creds)
  autoscaling.describe_auto_scaling_groups[:auto_scaling_groups].each do |group|
    name = group[:tags].select {|tag| tag[:key] == "aws:cloudformation:stack-name" }[0][:value]
    desired_capacity = group[:desired_capacity]

    in_service = Proc.new {|instance| instance[:lifecycle_state] == "InService"}
    num_dead_instances = group[:instances].reject(&in_service).count
    num_alive_instances = group[:instances].select(&in_service).count

    found.push({alive: num_alive_instances, dead: num_dead_instances, desired: desired_capacity, name: name })
  end
  puts("#{env} - #{total_num_alive_instances} : #{total_num_dead_instances}")
  send_event("#{env}-env", { dead: total_num_dead_instances, alive: total_num_alive_instances, autoscaling: found })
end

Aws.config.update({region: 'ap-southeast-2'})

unless ENV.fetch("AWS_SECRET_ACCESS_KEY", nil).nil?
  default_creds = Aws::Credentials.new(ENV['AWS_ACCESS_KEY_ID'], ENV['AWS_SECRET_ACCESS_KEY'], ENV['AWS_SECURITY_TOKEN'])
else
  default_creds = Aws::InstanceProfileCredentials.new
end
default_sts = Aws::STS::Client.new({credentials: default_creds})

dev_creds = Aws::AssumeRoleCredentials.new({client: default_sts, role_arn:'arn:aws:iam::<<my-dev-account-id>>:role/dashing/viewer', role_session_name: 'dashing'})
stg_creds = Aws::AssumeRoleCredentials.new({client: default_sts, role_arn:'arn:aws:iam::<<my-stg-account-id>>:role/dashing/viewer', role_session_name: 'dashing'})
prod_creds = Aws::AssumeRoleCredentials.new({client: default_sts, role_arn:'arn:aws:iam::<<my-prod-account-id>>:role/dashing/viewer', role_session_name: 'dashing'})

SCHEDULER.every '1m' do
  display_env(:dev, dev_creds)
  display_env(:stg, stg_creds)
  display_env(:prod, prod_creds)
end

This seems to work fine and creates the values I expect. The puts there also puts out the correct values each time.
However, it seems the events that are sent to the server never change value and the value in history.yml never change value.
I get no errors in either the browser or the logs.
I'm using dashing 1.3.4
I'm not sure how to further debug this problem....
Thanks
Stephen.

Try loading /events in your browser and watch the event stream for a bit. Are the JSON values coming through as you expect?

Nup. When I trace the events they come in as old values. The only thing
that makes them update is stopping and starting dashing.
On Sat, 4 Apr 2015 19:44 Tyler Mauthe<EMAIL_ADDRESS>wrote:

Try loading /events in your browser and watch the event stream for a bit.
Are the JSON values coming through as you expect?
—
Reply to this email directly or view it on GitHub
https://github.com/Shopify/dashing/issues/547#issuecomment-89529523.

Do you have other jobs that are sending data successfully?

It would appear the default jobs are suffering from the same problem.
On Sat, 4 Apr 2015 at 19:56 Tyler Mauthe<EMAIL_ADDRESS>wrote:

Do you have other jobs that are sending data successfully?
—
Reply to this email directly or view it on GitHub
https://github.com/Shopify/dashing/issues/547#issuecomment-89531068.

What if you create a new project? Does that work?

If you are able to run the demo project:
Are you running Dashing with dashing start? If so, do you have any customisation in your config.ru?
You can try deleting your history.yml and ensuring the directory is writable by the user that is executing Dashing.
Alternatively, create a new project and copy your jobs, dashboards and any custom widgets into the new directory.

I compared to a new project and nothing really changes other than the new jobs and dashboards.
it does seem however that you've given me the answer.
I had a setup using unicorn instead of calling dashing start.
It would appear that if I call dashing start then the default jobs atleast are updating values.
I shall change my deployment.
Thankyou.
Stephen.

You should be able to use unicorn. Add it to your Gemfile and reinstall your bundle with bundle install and then run unicorn from the bundle with bundle exec unicorn.

it would appear unicorn's "preload_app true" option is causing the data to
be stale.
If I remove that option then the data refreshes :)
On Sat, 4 Apr 2015 at 22:48 Tyler Mauthe<EMAIL_ADDRESS>wrote:

You should be able to use unicorn. Add it to your Gemfile and reinstall
your bundle with bundle install and then run unicorn from the bundle with bundle
exec unicorn.
—
Reply to this email directly or view it on GitHub
https://github.com/Shopify/dashing/issues/547#issuecomment-89555329.


Show macro expansions for undeclared identifiers

When an undeclared identifier is found, it would be helpful to show if and where it is expanded from a macro so the user can track it down.
Code
#define y z
#define x y
int main() {
  return x;
}

Expected Result (clang)
evil-test.c:4:10: error: use of undeclared identifier 'z'
  return x;
         ^
evil-test.c:2:11: note: expanded from macro 'x'
#define x y
          ^
evil-test.c:1:11: note: expanded from macro 'y'
#define y z
          ^
1 error generated.

Actual Error
evil-test.c:4:10 error: invalid program: use of undeclared identifier 'z'
  return x;
         ^
1 error generated

This is a good idea, but it's going to be really hard. Locations will have to be expanded to keep track of each macro along the way, which means they can no longer be Copy and there will suddenly be a lot of lifetime errors.
Maybe there should be some sort of lookup table for locations so that they don't have to be passed along with each struct? I don't think HashMap<dyn Hash, Location> is a thing, though.

The Locations of #defines are stored in a map somewhere already, I assume? So could we instead add an Option<InternedStr> member to Token::Id which points to where it which macro replaced into it? Then if there's an error, we can do a recursive lookup until None.

Or if the Locations of #defines aren't already stored somewhere, then lex::replace::Definitions could be changed from
pub type Definitions = HashMap<InternedStr, Definition>;

to
pub type Definitions = HashMap<InternedStr, (Definition, Location)>;

Not sure if this will mess with lifetimes.

@hdamron17 sure, making it a HashMap<InternedStr, Locatable<Definition>> isn't hard. The hard part is tracing back from the replaced version to the original. By the time this error occurs in the parser, all context about macros has been lost, there's only tokens left and you can't tell if they originated from a macro or not.

I guess a linked list isn't the worst thing since most replacements shouldn't be highly nested. I'm a little concerned about memory usage but we can always worry about performance later.


[BUG]: SK required fields not validated on .get

Describe the bug
Entity.get does not require fields required by SK.
This may be a debatable bug or it could be seen as a feature.  Lets say i have an Entity on a table that uses PK and SK, the SK requires a field ID.  if i do Entity.get({ pk: 'somePk' }) i will get the first matching entity instead of requiring the ID of the entity i am looking for.  This behavior is completely acceptable in Entity.find, but i dont think its right for Entity.get.
At the very least there should be an option of the table such as strictGet that validates that the required parameters for the SK are provided

You are right, get should require the full primary key. We should be able to throw an exception if SK not provided.
Validating for TypeScript would require an extra type. This may or may not be worthwhile as there are a few such cases and having a multitude of types leads to other problems. There is no free lunch.

Yeah, i can imagine typescript validation must be hard. But i think run time validation would suffice as a feature.

I've committed a fix for this. If you do a get without a required sort key, the API will throw.

Fixed in 1.7.3

Super! Thanks!!!

Unintended consequence.
Seems get was being used without an SK but with other fields to create a filter expression. This is actually pretty convenient when you know the PK + filter expression identifies only a single item.
With this change, users now need to do:
let item = (await Model.find({})[0]
The alternative is to revert to the prior behavior and check that only one item is found. If more than one is found, then error.
Thoughts?

Hmmm I feel like throwing when more than one is found is definitely better than not doing anything.
I guess that is fine, i can't come up with a good argument against doing that and it doesn't seem terrible.
The other option is to specify the desired behavior when defining the model. And it could be defaulted to false, and turned true if the property isn't provided.
But either might be fine.

Thanks -- we're going to revert this change in favor of:

Get without a sort key will fall back to do a find() with filter expressions and if that returns 1 result -- all okay
If the find returns > 1 result, an exception will be thrown.

im pretty sure this is related, but i started getting and error saying sort key was missing.
"Missing sort key"
i was executing this code
return this.UserFileModel.get({ username, id });
the sort key is this
sk: {
    type: String,
    value: '${_type}:${id}',
  },

because SK is of a composed value, i would not expect us to have to manually set the SK

What version?  or is that with the main branch?

The issue is using {_type} in the template.  We are not setting _type in the properties.
The fix is below.
@@ -722,6 +749,9 @@ export class Model {
     /* private */
     async getItem(properties, params = {}) {
         ({params, properties} = this.checkArgs(properties, params))
+        if (!this.generic) {
+            properties[this.typeField] = this.name
+        }
         properties = this.prepareProperties('get', properties, params)
         let expression = new Expression(this, 'get', properties, params)
         return await this.run('get', expression)

Re-opened due to _type not being handled.

so will this be released? if so, i can let you know how it goes.  I am building things with unit tests so thats why i am catching these things

Yes, should be fixed for using _type.

so i updated to 1.7.4
relevant schema
pk: { type: String, value: 'User:${username}' },
username: {
type: String,
required: true,
map: 'u',
transform: (_model: any, _op: any, _name: any, username: string) =>
username.toLowerCase(),
},
sk: {
type: String,
value: '${_type}:${id}',
},
id: {
type: String,
required: true,
},
The error i get
Missing sort key
  31 |
  32 |   delete(username: string, id: string) {
> 33 |     return this.UserFileModel.remove({ username, id });
     |                               ^
  34 |   }
  35 | }

If i take off the _type from the SK it works well. but with _type or type the tests fail.


Memory leak in server

Server fills up memory, and eventually the swap space. Time taken depends on usage, however it seems to be about 2 weeks time.

After more than a month of monitoring, I'm happy to say that there's no memory leak - the previous issue was due to several large files being uploaded at the same time.


Updated how CSS is watched in development mode (so the page doesn't refresh after styles have been injected)

Hello, sorry I know you just merged my PR today but I forgot to fix something else (my mistake).
Previously, the CSS would be injected and then the page would refresh from the hugo task being triggered. This was annoying me as I was developing my site because I had a few hidden elements I wanted to style but the page would keep refreshing after style changes were made.
I had updated the script with an if condition in the sass task, but I forgot to update the watch args so that both the css and other files are both up to date as you develop (the way I had wrote it before was not complete as it was missing the static/!(css)**/* glob). Hope that makes sense >.<

Cool, thanks for the update :)


Macro expansion

When expanding macros from imported files comments also get expanded and break the config

Could you provide an example? I'm not sure precisely what you're working with and how I might reproduce.

I think macro is the wrong word, a line with "#define var val      // comment" will subtitle both the variable and comment, even mid line

Yeah, the preprocessor's going to do that, it doesn't care about comments. Are you writing it out that way or did a comment line get merged onto a previous line after editing with the app? If you can share the original I might be able to track down the cause and correct it.
Just a heads-up, though, I pretty much can't support preprocessor stuff so if you're relying on that to achieve more complicated keymaps there may not be a great path forward.

I was converting from a hand written file, and have since fixed the problem, though though I would submit this as a possible suggestion to improve the experience of doing so

Ah, ok, glad to hear you could resolve it. Unfortunately there's nothing I can do about preventing that as its written. If you've hand written a keymap with a line as you've described then the preprocessor is going to do the substitution regardless of whether you use the keymap editor.


'importing' a mod inside a funcion don't take effect for intelisense autocompletion or type highlights

Referring to a module with use like use self::models::Post; inside a function don't works for the code analizys (it does compile and run)

It does work if the use sentence is at mod level outside the function.

Attached some screenshots, happy to provide more info if needed.
Thanks!

Duplicate of https://github.com/rust-analyzer/rust-analyzer/issues/1165


My web app froze during deployment and I cannot deploy again

Does this occur consistently?
Repro steps:

Action: appService.Deploy
Error type: 409
Error Message: There is a deployment currently in progress. Please try again when it completes.
Version: 0.16.2
OS: win32
OS Release: 10.0.18362
Product: Visual Studio Code
Product Version: 1.42.1
Language: en

Call Stack
extension.bundle.js:323:392866extension.bundle.js:323:392866
s extension.bundle.js:218:111699
s extension.bundle.js:157:26069
extension.bundle.js:157:27311extension.bundle.js:157:27311
o extension.bundle.js:164:7076
extension.bundle.js:157:24982extension.bundle.js:157:24982
$._callback extension.bundle.js:1:579996
$.t._callback.t.callback.t.callback extension.bundle.js:194:5449
$.emit events.js:200:13
$.<anonymous> extension.bundle.js:194:18309
$.emit events.js:205:15
IncomingMessage.<anonymous> extension.bundle.js:194:17141
Object.onceWrapper events.js:288:20
IncomingMessage.emit events.js:205:15
endReadableNT _stream_readable.js:1154:12
processTicksAndRejections task_queues.js:84:9

Hi @ninahorne
Thanks for reporting.  Is this still occurring?  Could you try restarting your app or perhaps making a new one?

Hi,
Yes this is still occurring. I have reset my app and it didn't work. I can
look into making a new one. Is there anything else we can do?
On Mon, Feb 24, 2020 at 12:14 PM Nathan<EMAIL_ADDRESS>wrote:

Hi @ninahorne https://github.com/ninahorne
Thanks for reporting. Is this still occurring? Could you try restarting
your app or perhaps making a new one?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-azureappservice/issues/1405?email_source=notifications&email_token=ACTULVC4FSQCAK2L353AGB3REQFBTA5CNFSM4KZJGMV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMY6SSY#issuecomment-590473547,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACTULVHNHHIE3X35PYBYVTDREQFBTANCNFSM4KZJGMVQ
.

--
Nina Horne
Web Developer at WhereWeGo - wherewego.org
Co-Owner of Sabzi - @sabzipersianpopup
(504) 401 - 0675

It is working now! thank you
On Thu, Feb 27, 2020 at 2:27 PM Nina Horne<EMAIL_ADDRESS>wrote:

Hi,
Yes this is still occurring. I have reset my app and it didn't work. I can
look into making a new one. Is there anything else we can do?
On Mon, Feb 24, 2020 at 12:14 PM Nathan<EMAIL_ADDRESS>wrote:

Hi @ninahorne https://github.com/ninahorne
Thanks for reporting. Is this still occurring? Could you try restarting
your app or perhaps making a new one?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-azureappservice/issues/1405?email_source=notifications&email_token=ACTULVC4FSQCAK2L353AGB3REQFBTA5CNFSM4KZJGMV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMY6SSY#issuecomment-590473547,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACTULVHNHHIE3X35PYBYVTDREQFBTANCNFSM4KZJGMVQ
.

--
Nina Horne
Web Developer at WhereWeGo - wherewego.org
Co-Owner of Sabzi - @sabzipersianpopup
(504) 401 - 0675

--
Nina Horne
Web Developer at WhereWeGo - wherewego.org
Co-Owner of Sabzi - @sabzipersianpopup
(504) 401 - 0675


Implement organization management (RBAC)

This resource allows managing the members of an organization:

For each member their roles can be configured.
Added members will be invited to the organization.

The user will still have to accept the invitation before they have access to the organization.

Removed members will be removed from the organization

(~Currently all builds/tests for this PR are failing because we first need a new release of cloud-sdk-go to get the organization apis https://github.com/elastic/cloud-sdk-go/pull/477~)
Now includes cloud-sdk-go 1.21.0
Description

Regarding invitations

The resource tracks the invitation status for each member. Since some time can pass before the new member accepts the invitation.
Since invitations can't be updated, any role changes during this time will mean the invitation is cancelled and a new invitation is created.
After the invitation is accepted, the next apply will update the local state with the user-id. And now roles can be updated.

Create/delete don't really work for an organization. It already exists and can't be deleted (One can only leave an organization).

The default flow is to import the already existing organization using the terraform import flow.
It isn't possible to automatically import with the create, because then the resulting organization potentially wouldn't match the current config. So the create has to throw an error if it is called.
The delete does nothing currently, so it is possible to run the terraform destroy to remove the org from the state. However this is currently just to stop managing the resource in terraform, it won't actually be deleted.

Related Issues

https://github.com/elastic/terraform-provider-ec/issues/629
How Has This Been Tested?

Manual testing
There are no real acceptance tests because it isn't possible to automatically add new members.
However currently all use-cases are covered by acceptance tests that use mocked API requests.

Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Refactoring (improves code quality but has no user-facing effect)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Documentation

Readiness Checklist

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

I think both have their advantages. The main difference in my opinion is on the management of members:

Single organization resource: You must manage all members. This has the advantage that you can always be sure that the configured members are the only ones in the org.
Per-member resource: More flexible, you can pick which members should be managed by terraform.

The PR is now updated to include the right cloud-sdk-go and should compile now.

Small update to the PR, I reenamed the fields:

for_all_deployments -> all_deployments
for_all_projects -> all_projects

@gigerdo , does it make sense to add unit tests to cover negative use cases?
(IIUC, TestOrganizationResourceAgainstMockedAPI covers positive use cases only).

@dimuon I refactored the testcases into separate tests, and added a failure case for each.


Rename prover methods, extend test test_generate_self_attested_proof

extend test test_generate_self_attested_proof  to include verification of proof containing of self-attested attributes

method renames in aries-vcx:

generate_presentation_msg ---> get_presentation_status + changed return data from String to Presentation
presentation_request ---> get_presentation_request

method renames in libvcx_core

generate_proof_msg -> get_presentation_msg

Codecov Report

Merging #764 (4e83b6e) into main (699bffd) will decrease coverage by 24.67%.
The diff coverage is 15.38%.

@@             Coverage Diff             @@
##             main     #764       +/-   ##
===========================================
- Coverage   54.56%   29.89%   -24.67%
===========================================
  Files         380      378        -2
  Lines       36673    30516     -6157
  Branches     8059     6272     -1787
===========================================
- Hits        20009     9122    -10887
- Misses      10711    18684     +7973
+ Partials     5953     2710     -3243

Flag
Coverage Δ

unittests-aries-vcx
29.89% <15.38%> (-24.57%)
:arrow_down:

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

Impacted Files
Coverage Δ

...ries_vcx/src/handlers/proof_presentation/prover.rs
15.53% <0.00%> (-40.68%)
:arrow_down:

...es_vcx/src/handlers/proof_presentation/verifier.rs
30.37% <ø> (-22.17%)
:arrow_down:

aries_vcx/tests/test_creds_proofs.rs
100.00% <ø> (+11.87%)
:arrow_up:

messages/src/status.rs
17.50% <ø> (-20.00%)
:arrow_down:

...otocols/proof_presentation/prover/state_machine.rs
62.08% <28.57%> (-3.04%)
:arrow_down:

...tocols/proof_presentation/prover/states/initial.rs
0.00% <0.00%> (-100.00%)
:arrow_down:

...cols/proof_presentation/verifier/states/initial.rs
0.00% <0.00%> (-100.00%)
:arrow_down:

aries_vcx/src/handlers/discovery/mod.rs
0.00% <0.00%> (-93.75%)
:arrow_down:

...ies_vcx/src/core/profile/modular_wallet_profile.rs
0.00% <0.00%> (-81.25%)
:arrow_down:

aries_vcx/tests/utils/scenarios.rs
0.00% <0.00%> (-80.30%)
:arrow_down:

... and 207 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[BugFix][Cherry-Pick] Fix bug clear expire task/taskrun before save image

What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #18084
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

run starrocks_fe_unittest


Loosen pandas pin

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

pandas is no longer pinned upstream:
https://github.com/lux-org/lux/blob/57b7d803cdf32fd38838e54b3b32696eedb8709c/requirements.txt#L4
This is a bit more conservative as IMHO it's easier to put in a PR to loosen the pin than it is to yank a broken release.

Looks great! Thanks @dhirschfeld!


Nodejs 8 upgrade warning

After setup, Firebase displays a warning to upgrade from Node 8 to at least Node 10:

I heard from the Firebase team that this is a warning that's displayed in the UI for all extensions unfortunately, regardless of the actual node version used. They're working on addressing it.
The functions deployed by this extension do use Node 14:
https://github.com/typesense/firestore-typesense-search/blob/c35c0871dc2abed9c0c513f5b4b5fe7023d93d45/extension.yaml#L24