Feature Request to Teams PowerShell module - decrease the amount of traffic returned from servers

Hi there,
Has anybody of you proposed to limiting number of attributes what different "get-" CMDlets are returned from servers? For example when run:
get-csonlineuser<EMAIL_ADDRESS>That gives 199 attributes back. With single users searches this is not big issue. But how about 20k users or even more?
The solution could be having a "properties" parameter added. And with that admins could define what parameters s/he needs. And by default there is coming only few defaults.
That would have a business case to you I believe, as that would simplifying the searches on servers site, and most likely makes the searches to happen faster.

Hey @Petri-X
It would be nice to have a modern version of the module that will allow such things as filtering.
But I would be surprise if Microsoft will do any time soon (coming years).
In the meantime, you can do this today by explicitly using PS Remoting. I know it's ugly and limited in many aspects, but at least it is something that is available today and it works.
Try the following example that executes column filtering server-side and then downloads only the final results.
Slow code: Client-side filtering
Import-PSSession (New-CsOnlineSession)
Get-CsOnlineUser | Select-Object InterpretedUserType -Unique

Fast-code - server-side filtering
Import-PSSession (New-CsOnlineSession)
Invoke-Command -Session (Get-PSSession) -ScriptBlock { Get-CsOnlineUser | Select-Object InterpretedUserType -Unique }

Above examples are for Microsoft Teams v 1.1.6 in Windows PowerShell 5.1

Hello @Petri-X how are you? Hope you are doing good.
We appreciate the feedback, however, as you might know, we are limited here to documentation issues and improvements.
I also appreciate your contribution @shivtorov for Petri and everyone that might be on the same page.
Thanks

@shivtorov
Sorry to say, but module 1.1.6 is history already, and we have started to use module version 2.0.0. "New-csOnlineSession" is not available anymore.
@get-itips
I believe that is a bit problematic. There has been no clear clarification into where the GitHub should be used, when sometimes this is helping errors on the documentation, but sometime PS module issues are listed on GitHub. Are  you able to clarify that somehow? I'm preferring to use GitHub possibilities to report PS issues as well. :)

@Petri-X Sure Petri, I'll try to do my best to give you the requested information: You can have more information here  and here.
Also a bit of history 👍

@Petri-X

@shivtorov
Sorry to say, but module 1.1.6 is history already, and we have started to use module version 2.0.0. "New-csOnlineSession" is not available anymore.

Congratulations with upgrading to v.2.0.0!!!
Connect-MicrosoftTeams
Invoke-Command -Session (Get-PSSession) -ScriptBlock { Get-CsOnlineUser | Select-Object InterpretedUserType -Unique }

🤦♂

I passed this information along, @yogkumgit please close this as it is not documentation-related. Thanks

@get-itips Thank you very much for the contribution and sharing this explanation. @Petri-X Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

@shivtorov
Sorry to say, but you need to clarify that a bit more  :D
As when I'm running:
PS C:\> Connect-MicrosoftTeams
Account                     Environment Tenant      TenantId
<EMAIL_ADDRESS>    AzureCloud  9bfcd....   9bfcd....

PS C:\> Get-PSSession
PS C:\>

At least I'm getting nothing for PS Session. So I'm not sure if the "connect-MicrosoftTeams" is a PSSession(?). But as you also referring, it would be ten times better to have this into PS module directly. AD team has made like following:
Get-ADUser -Identity UserA -Properties *
or the -properties could look like
Get-ADUser -Identity UserA -Properties emailAddress, telephoneNumber

I passed this information along, @yogkumgit please close this as it is not documentation-related. Thanks

@yogkumgit please close this thread as it is not documentation specific and I already passed this feedback along.


Cannot select column from view

After create this view:
CREATE TABLE Test (
    createdDate Date,
    str String,
    key Enum8('A' = 0, 'B' = 1, 'ALL' = 2),
    a Int64
)
 ENGINE = MergeTree(createdDate, str, 8192);

CREATE VIEW TestView AS
    SELECT str, key, sumIf(a, 0) AS sum
    FROM Test
    GROUP BY str, key

    UNION ALL

    SELECT str AS str, CAST('ALL' AS Enum8('A' = 0, 'B' = 1, 'ALL' = 2)) AS key, sumIf(a, 0) AS sum
    FROM Test
    GROUP BY str

I try to select any column, eg:
SELECT str FROM TestView
And receive this exception:
Received exception from server:
Code: 47. DB::Exception: Received from localhost:9000, <IP_ADDRESS>. DB::Exception: Unknown column: 0, there are only columns str, a.

It looks like a bug in UNION implementation:
CREATE TABLE test ( s String,  i Int64) ENGINE = Memory

SELECT s FROM (SELECT s, sum(i*2) AS i FROM test GROUP BY s  UNION ALL  SELECT s, sum(i*2) AS i FROM test GROUP BY s)

Doesn't work:
Code: 47. DB::Exception: Received from localhost:9000, ::1. DB::Exception: Unknown column: multiply(i, 2), there are only columns s, i.

Yes. Thanks!


McFly > 0.0.8 breaks in IE9 due to bind not available on console.{log,warn,error}

Amid the many strange things IE9 does, "its error/warn/log functions from the console object in IE don't inherit from Function. They are host objects, and use whatever rules IE sees fit." (quoting StackOverflow / Why can't I bind directly console.log on IE9 with developer tools open?
As a result, the var warn = (console.warn || console.log).bind(console) calls added as part of https://github.com/kenwheeler/mcfly/issues/31 and https://github.com/kenwheeler/mcfly/pull/26/ and released in McFly 0.0.8 / 0.0.9 break it :-/ :

I'd give a stab at fixing it, but am not sure how you prefer to solve this; if you don't have the time (or willpower to test on IE9 ^^), tell me what you'd like and I'll make a pull request.
Thanks for your work!

This is fixed in the Biff fork. I'll merge it back into McFly

Fantastic.
@kenwheeler I didn't know about Biff. I see you commit to both projects, what's the rationale/relationship between both?

Hey @kenwheeler sorry for the re-ping, I'm in the unfortunate situation of having upgraded to McFly 0.0.10 (breaking IE9 compatibility, it would be sad to revert to 0.0.8) and it looks like you (or your employer) are more focused on Biff, but looking at each project's README it's not clear.
→ Should I migrate to Biff? Are Biff/McFly's API-compatible? Thanks.

They are not. Moving to Biff is a choice to make if it fits with the problems you are trying to solve. That said, shouldn't you have to use es6-shim to polyfill bind anway for React?

:+1: . Thanks.

Hi @kenwheeler, any chance Biff's IE9 fixes find their way into McFly? I'm still running my app on a forked/patched version (ronjouch/mcfly) and would like to come back to a vanilla npm package.
Also, come back to Biff, if McFly is taking too much of your time and Biff is the maintained one, could you detail the differences between both? You say "Moving to Biff is a choice to make if it fits with the problems you are trying to solve", but it's tough as a non-expert user to make this choice, because both have very similar READMEs and it's hard to get the intent/direction just looking at the commits in Biff.

Hi @kenwheeler, any update on this issue? Are there plans for the above fix be merged into McFly?

You can implement a Function.prototype.bind or ES6 polyfill pretty easily, has anyone tried this?

SO, was this finally fixed? I am thinking we should close the ones that are already fixed.

@kenwheeler this issue can be closed.
Merged in:
https://github.com/kenwheeler/mcfly/pull/54


Added conference for milestone papers

Hi,
There are two main changes I made:

I added the published conference for 4 milestone research papers. Here are the details of them including where I found them:

Unifying Language Learning Paradigms - ICLR
Source: https://dblp.org/search?q=Unifying Language Learning Paradigms

The Flan Collection: Designing Data and Methods for Effective Instruction Tuning - ICML
Source: https://dblp.uni-trier.de/search?q=The Flan Collection%3A Designing Data and Methods for Effective Instruction Tuning

PaLM-E: An Embodied Multimodal Language Model - ICML
Source: https://dblp.org/search?q=PaLM-E%3A An Embodied Multimodal Language Model

Principle-Driven Self-Alignment of Language Models from Scratch with Minimal Human Supervision - NeurlPS
Source: https://dblp.uni-trier.de/search?q=Principle-Driven Self-Alignment of Language Models from Scratch with Minimal Human Supervision

I added ToT (Tree of Thoughts: Deliberate Problem Solving with Large Language Models) to the milestone papers section, which is a paper deemed by many as a milestone similar to CoT. Here's the pdf link: https://arxiv.org/pdf/2305.10601.pdf

Best,
Nathan

Appreciate!


New way of matching Tokens (NDS)

A simpler way to match tokens (atoms) has been introduced as an idea in the Natural Design System (NDS) document. According to this new method, we're using a natural nesting path, rather than adhering to a fixed length path.
https://github.com/design-ops/stylable-swiftui/blob/master/NDS.md
So, to match the following Token home/header/searchBar/label, the following is the hierarchy based on specificity:
Old way
home/header/searchBar/label
*/header/searchBar/label
home/*/searchBar/label
home/header/*/label
*/*/searchBar/label
*/header/*/label
home/*/*/label
*/*/*/label

New way (NDS)
home/header/searchBar/label
header/searchBar/label
home/searchBar/label
home/header/label
searchBar/label
header/label
home/label
label

How feasible is this based on the work we have done so far?
Is this something we can work into the existing Stylist?

@deanWombourne when you find time, I'd really appreciate any feedback on this.

One thing that might be a problem here is that in the NDS system there is no way for us to distinguish between
searchBar/label
header/label
home/label

unless we have a canonical identifier to compare them against (i.e. the "fully-formed" identifier).
Each of these identifiers are all equally specific.

These look equal if you look at them at face value. But having the original path eg. home/header/searchBar/label then we can match for specificity. In which case, searchBar/label wins.

Will there ever be a case where we don't have the full identifier?

The same goes for any identifier that has the same number of components as any other one. Unless there is a canonical identifier to compare against, they will all be equally specific.

I’m not sure I’m totally following, but in the previous approach there was an unwritten/enforced rule that there would always be an identifier that represented the atom as a fallback - in this case there would always be a label and further (I think) there was always a fallback style in the generated code if nothing else matched

The same goes for any identifier that has the same number of components as any other one. Unless there is a canonical identifier to compare against, they will all be equally specific.

I’m not sure I’m totally following, but in the previous approach there was an unwritten/enforced rule that there would always be an identifier that represented the atom as a fallback - in this case there would always be a label and further (I think) there was always a fallback style in the generated code if nothing else matched

Yup, the difference between the atomic design approach and the natural design approach is that in atomic design identifiers have an intrinsic specificity value based on the position of its components with reference to the organism/section/element/atom "base". Because the identifiers have intrinsic specificity, you can sort them at stylist initialization time. In NDS, we don't have that "base" so an identifier is only specific when referenced against another identifier i.e.:
searchBar/label
header/label
home/label

don't have intrinsic specificity, they're only specific when compared against the identifier we're trying to style for example:
home/header/searchBar/label

that's what i was trying to say in my previous comment :) but maybe i've missed something...

Would this affect how we load the assets (i.e images)?

Hey @cdemetriadis - do you have an example of NDS with variants?

@deanWombourne Here's a theme file with variants for the primaryButton/label > primaryButton[disabled]/label & primaryButton[selected]/label
NDS - SwiftUI-POC-Theme (Vanilla).zip

OK, there's been no noise on this so I've given it a go while The Boy is napping. This is a playground-friendly attempt at writing a matching method for NDS. Also, as it gives a score, not just a bool, this should also be good to use to find the best match.
struct StylistIdentifier: Equatable, Hashable {
    let components: [String]
}

extension StylistIdentifier: CustomStringConvertible {

    var description: String {
        self.components.joined(separator: "/")
    }
}

extension StylistIdentifier: ExpressibleByStringLiteral {

    init(stringLiteral value: String) {
        self.init(components: value
            .split(separator: "/")
            .map { $0.trimmingCharacters(in: .whitespacesAndNewlines) }
            .filter { !$0.isEmpty })
    }
}

struct StylistIdentifierMatcher {

    /// Returns a value > `0` if the lhs mattches the partial identifier on the rhs, `0` otherwise.
    ///
    /// i.e.
    ///
    /// matches("home/header/searchBar/label", "home") -> > 0
    /// matches("home/header/searchBar/label", "header") -> > 0
    /// matches("home/header/searchBar/label", "home/searchBar") -> > 0
    /// matches("home/header/searchBar/label", "home/potato") -> 0
    ///
    func match(lhs: StylistIdentifier, rhs: StylistIdentifier) -> Int {
        print("Attempting to match \(lhs) with \(rhs)")

        // Let's just assume that empty identifiers (which are technically invalid) won't match or be matched with.
        guard !lhs.components.isEmpty else { return 0 }
        guard !rhs.components.isEmpty else { return 0 }

        let lhsComponents = lhs.components.reversed()
        let rhsComponents = rhs.components.reversed()

        // We are going to manually step over the rhs, so we will need an iterator
        var rhsIterator = rhsComponents.makeIterator()
        var rhsComponent = rhsIterator.next()

        // Go through each component of each identifier in turn.
        //
        // If the lhs one doesn't match, move on to the next.
        // If the rhs one doesn't match then abort and return 0.
        var score = 0
        var nextScore = 1 << lhsComponents.count

        for lhsComponent in lhsComponents {
            print("  Comparing \(lhsComponent) to \(rhsComponent ?? "<nil>")")

            // Each component we look at for the lhs is _less_ important than the last
            nextScore /= 2

            // If this doesn't match the rhs component, move on to the next one
            if lhsComponent != rhsComponent {
                print("   └─No match - movng on to next lhs component")
                continue
            }

            print("   └─Match")

            // Increment the score
            // TODO: Make the score reflect the position of a match i.e. a atom match isn't worth as much as a section match
            score += nextScore

            // Move on to the next rhs component - and if we are at the end, we have matched and just return the score
            rhsComponent = rhsIterator.next()

            if rhsComponent == nil {
                print("  End of rhs - match found")
                return score
            }
        }

        // If we have got to the end of the lhs then we haven't matched everything in the rhs - no match
        print("  End of lhs, but rhs still has matches - no match")

        return 0
    }
}

let identifier: StylistIdentifier = "home/header/searchBar/label"

let matcher = StylistIdentifierMatcher()

// Matching against yourself should give the highest possible score - in this case there are 4 possible components
// to match, which is 1+2+4+8 = 15
matcher.match(lhs: identifier, rhs: identifier)

// Matching only the first component should be 1 - the lowest possible score for a match
matcher.match(lhs: identifier, rhs: "home")

matcher.match(lhs: identifier, rhs: "header")
matcher.match(lhs: identifier, rhs: "home/searchBar")
matcher.match(lhs: identifier, rhs: "searchBar")
matcher.match(lhs: identifier, rhs: "label")

// Shuold give a score of 0 - no match
matcher.match(lhs: identifier, rhs: "home/potato")

Anyone fancy a call to chat though it?

Also, gist her if you want to comment - if that's a thing on gists? https://gist.github.com/deanWombourne/eccd41634e29ec09468f8cb645eefde6

Hey @deanWombourne, thanks for looking into this.
I cannot really comment on the actual code, but I'd say adding a score makes absolute sense ;)
Question: lhs is essentially what we call token eg label in this case, right? And 'rhs' the path to that token.

Hah, I read my code and that's the first thing I've changed :) They are now "specific" and "general" where specific is the identifier for the component, and general is the identifier we have the style we are trying to apply. i.e. if we were styling "home/header/searchBar/label" with a style for "home" then the specific would be the full identifier, and general would be "home". If you follow the link to the gist that should be the most up to date version of this - I shouldn't have put any code directly in here at all really!
oh, feel free to think of better names for these two parameters :)

Still have to work out how variants work in all this . .

In my mind, this is path/to/the/designToken
So, if there's a style named title, we just need to find out where it's being used eg home/header/primaryButton/title and use that for matching against the styles in our theme file.

Just to sanity check, if we have a style for "title" it would match "section/component/title", but would also match "title/component/label"  ie if there was a section called title. Now we don't have a fixed length for identifiers I don't see how the stylist would differentiate between those two cases?

title is the Design Token, and it should always be present at the end of the path.
We could always get on a call and talk through it. I'm probably missing a million edge cases...

Hey everyone - PR #22 should fix this, with working design tokens and variants. Probably. There's tests, but there will almost certainly be edge cases I'm not testing.
And we do need to talk about image matching - the current algorithm probably isn't right anymore :|

Images use StylistImage(), right?

Yea - we couldn't find a way to extend the normal SwiftUI image :(

@cdemetriadis @atomoil @kerrmarin Is this fixed by the PRs we just merged?


model: fix invites

Discord returns only a partial channel, which cannot be deserialized into a full channel.
This commit adds a model for the partial channel (named InviteChannel following the convention set by InviteGuild)
Associated tests updated, and test for InviteChannel added.

Thanks


Incorrect date calculations for time origin < start of Gregorian calendar

Reported by sirott on 29 Dec 2001 18:32 UTC
The Grads-DODS server generates time axes with an origin of Jan-1-0001, and
units of days. Variables in the URL at:
http://cola8.iges.org:9090/dods/avn122800
are on a time axis with a first value of 12/28/2001. This corresponds to 730848
days since 1/1/0001. Ferret calculates the same date as 730846 days and so
shifts the first value to 12/30/2001.
Ferret makes the incorrect calculation (I believe) because it calculates the
day 1/1/0001 on the Gregorian calendar; all dates before 10/4/1582 should be on
the Julian calendar.
FYI, a nice summary of Gregorian/Julian calendar issues is available at:
http://home.capecod.net/~pbaum/date/back.htm
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/353

Comment by<EMAIL_ADDRESS>on 15 Nov 2002 19:15 UTC
fixed in v5.40.
with a different file from the Grads server, v5.33 shows time
starting on Nov 3, v5.41 correctly shows start at Nov 1.
use "http://cola8.iges.org:9090/dods/avn110100"
list t[gt=icec]

Comment by<EMAIL_ADDRESS>on 21 Oct 2003 20:15 UTC
Moving from the<EMAIL_ADDRESS>user to the<EMAIL_ADDRESS>user.

Comment by<EMAIL_ADDRESS>on 10 Feb 2004 21:15 UTC
Put bugs that were in component "All" into "Main"


Multi Selection type feature not available

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here

Current behavior
I am not able to find "multi" selection type feature in the latest "ngx-datatable" version which is provided on the previous "angular2-data-table - ^0.3.8" version. This feature is not available in the current version of "ngx-datatable". The new version only provide the five types of selection type "Cell, Single Row, Multi Row, Disable Callback and Checkbox". In this "Multi Row" and "Checkbox" selection type show the same behaviour.
Expected behavior
I need "multi" selection type feature in latest "ngx-datatable" version.

Table version: 0.7.x

Angular version: 2.0.x

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Language: [all | TypeScript X.X | ES6/7 | ES5]

This feature is available in latest release which is "4.1.0". Thanks for the version update.
Hence i am closing this issue.
Thanks.


add colors for leading candidate

Adding colors for the background of the leading candidate on each row.
From:

To:

New Color:

and


ShapeCast3D Returning incorrect collision point

Describe the bug
When using a ShapeCast3D the collision point is deeper than the surface I am casting against.
To Reproduce
Add a ShapeCast3D going straight down with a cylinder shape with height of 0.1, then play with Debug Visible Collision Shapes
Expected behavior
Expect to see the cylinder shape sat perfectly on top of the surface like this (This is using default Godot physics in 4.3):

Instead it appears like this:

Environment:

OS: Windows
Version 0.8.0
Godot Version 4.3
Type SIMD 3D

There is a similar issue for ShapeCast2D. Probably related.

This is related to the cylinder shape not working correctly.


Keep publishing and automatic reconnect

I have a use case where in

Keep publishing packet in a loop
And the client  should acquire connection if disconnection happens.

The first one, we can use a loop, but on the second , how do we handle reconnect with a loop. What kind of error does the client throw if disconnection happens.

From the docs you can see Client.publish (and other methods) returns a crate::Result with the error part crate::Error which includes a Disconnected variant.
You'll need to check if publish (or any other methods your use) return this result and handle the errors appropriately. Likely you can just try reconnecting for any kind of error assuming the very first connect worked ok. There may be some StdError variants that are actually fatal OS issues but what you do with those I couldn't say.

Closing due to inactivity, I think @cs2dsb gave a sufficient response.


Add testimonials in homepage

As a user, I would like to see testimonials on the homepage to gain trust and confidence in the product/service. Testimonials provide social proof and can greatly enhance the credibility of the website. This issue aims to add a testimonials section to the homepage.
I believe I can solve this issue . Assign it to me under GSSOC'23.

You can work on this..thanks! Make sure to redirect the testimonial link in the footer as well !

Hey are u working in this???

Yes . working on it. Could you give me 2-3 days . Actually my semester exams are going on.

Hey..yes yes..good luck with your exams!

Hey..testimonials component have been added to the navbar..you have to design the testimonial section..
Please do it asap!

Hey @rishitachail have u completed its been too late submit your PR ASAP.

I would like to create the testimonial section for the website .
Right Now , it is blank.
I would add an automatic carousel in there. This would improve user experience and engagement.

@rishitachail if you are unable to do let me know so that i can assign it to others.

@rishitachail if you are unable to do let me know so that i can assign it to others.

I had exam today. Shall submit in 2 hours. Thank you for the time.

Hey, @i-am-SnehaChauhan Can you assign me this issue? I can make this quicky.

Bhai localhost ka link kon share krta hai 😂

That's what I was saying it is localhost 😞

Ohh got it... Assign me this issue i can fix it.


[FIX] [BE PYTHON] [ANCHOR] Develop an API Endpoint for Join waitlist

Description
Create a backend API endpoint that enables users to sign up for a waitlist. This endpoint will capture and store user details, including their email and their name, in a secure database.
Acceptance Criteria
Data validation that ensures that only valid and unique emails are accepted
The API returns appropriate responses for successful submissions and errors.
Duplicate email entries are prevented, and appropriate error messages are returned
Emails are stored securely in the database.
Purpose
To develop an API endpoint to enables users to successfully sign up for waitlist.
Expected Outcome
Users can successfully sign up for the waitlist and their submission is securely stored in the database.

Please has this been implemented?

this has not been implemented @johnson-oragui, go and check it yourself. it is not working


Rails::Mongoid.load_models in "preload all application models" should not run when $rails_rake_task

Models shouldn't be eager-loaded on $rails_rake_task runs. In railtie.rb:
initializer "preload all application models" do |app|
config.to_prepare do
::Rails::Mongoid.load_models(app) unless $rails_rake_task
end
end

I'm a little curious why this is the case too. I added a new initializer to my app that accesses a mongoid model. The rake task will just freeze (actually it'll eventually time out) when you access a model in an initializer. Especially problematic on Heroku, since it will automatically run rake assets:precompile. It'll just time out eventually and the git push will fail.

I'm about to bring this back, since the models actually do need to be loaded for the case above, as well as creating indexes, etc...

Brought back in 2ff10c9aa2a7812a7f23a26fcd314623541290cc


Enchanted generic response

I thought that necessary add interfaces for our responses.
I made FFDCResponse and GenericResponse for more reusability of the code.
If have you questions, please ask them.

@planetf1 Hi I dont know that it is problem with gradle...

@planetf1 Hi I dont know that it is problem with gradle...

We needed the ffdc package as a dependency. I pushed the fix for you:-)
     implementation project(':open-metadata-implementation:common-services:ffdc-services')

We are part way through refactoring to a gradle build - for now this is doing compile only
However we need @davidradl to review the actual subject area change (will be next week)

@planetf1 Thank you:)

The grade build is failing after the version bump. It is not due to this pr. I have now disabled the mandatory nature of the check and will look at resolving. . The best push or update should be fine. Apologies

I would prefer to put in https://github.com/odpi/egeria/pull/3535 first, then merge to that master, as it touches some of the same files.

@immmus I suggest merging in the base branch now the LineEnds  change has gone in and I will re-review

@immmus I suggest merging in the base branch now the LineEnds change has gone in and I will re-review

We have some error after merge last changes. Error with fvt.

@davidradl There was an error in fvt after updating.

I resolve it in https://github.com/odpi/egeria/pull/3545

Hi @davidradl !
Please check and merge this ->  https://github.com/odpi/egeria/pull/3545 before current pr.

Hi @davidradl !
Please check and merge this -> #3545 before current pr.

Sorry I just saw this comment - I have merged the other one

@immmus I suggest merging in the base branch now the LineEnds change has gone in and I will re-review

We have some error after merge last changes. Error with fvt.

@immmus I am not sure how this could have happened, the FVT is run in the build and needs to succeed for the build to  allow the merge of any change. @planetf1  @immmus Any ideas why the build worked but the FVT had an NPE?

@immmus I suggest merging in the base branch now the LineEnds change has gone in and I will re-review

We have some error after merge last changes. Error with fvt.

@immmus I am not sure how this could have happened, the FVT is run in the build and needs to succeed for the build to allow the merge of any change. @planetf1 @immmus Any ideas why the build worked but the FVT had an NPE?

I dont know why build succeed but the problem was in the code which I fixed in the #3545  pr.

@davidradl the PR build should run the fvts as as you say should fail if the tests fail - indeed we've seen them fail.
What time build are you referring to that passed - we need to check the logs to see if we can see what happened. Perhaps it was an intermittent error.
The PR builds are at https://dev.azure.com/ODPi/Egeria/_build?definitionId=11&_a=summary
I see one PASSED today 48 mins ago
I also see two previous ones FAILED
Then one before that PASSED
.. in terms of this PR
I looked at the last failing one which clearly shows
2020-08-31T10:41:23.4391030Z [ERROR] Tests run: 18, Failures: 2, Errors: 0, Skipped: 0

and ends
2020-08-31T10:41:24.1533737Z [INFO] Subject Area OMAS FVT .............................. FAILURE [01:20 min]
2020-08-31T10:41:24.1534108Z [INFO] Open Metadata Open Types Test Resources ............ SKIPPED
2020-08-31T10:41:24.1534443Z [INFO] Open Types Test generator .......................... SKIPPED
2020-08-31T10:41:24.1538502Z [INFO] Open Types Test execution .......................... SKIPPED
2020-08-31T10:41:24.1539220Z [INFO] ------------------------------------------------------------------------
2020-08-31T10:41:24.1539505Z [INFO] BUILD FAILURE

Can you elaborate more on what's wrong with this, or what you saw that was odd?

Can you elaborate more on what's wrong with this, or what you saw that was odd?
@planetf1 I did not know about the errors until @immmus put in his fix, but this is something odd that the build failed after the  checkin was allowed. I am not sure what we can do to diagnose at this point, short of cloning the build and backing off to or before the failing code. I think it is something we need to keep an eye on

Can you elaborate more on what's wrong with this, or what you saw that was odd?
@planetf1 I did not know about the errors until @immmus put in his fix, but this is something odd that the build failed after the  checkin was allowed. I am not sure what we can do to diagnose at this point, short of cloning the build and backing off to or before the failing code. I think it is something we need to keep an eye on
@immmus , did you identified when the failing code was checked in so we can check the logs?

the crash happened when I pushed the latest changes from the master branch f809066

I'm trying to understand the situation are describing - we need to be precise in terms of branches and merges.
My understanding from the text above, is that @immmus you noticed a build failure after you merged changes from MASTER into your branch (you said 'pushed the latest changes from the master branch' but I think this is what you meant?) Enchanted_generic_response - which is of course linked to this PR. That merge into your branch would have kicked off a new build which failed (in fact a few did) as the FVTs did indeed run and find an error.
I think the build that represented that merge is here -> https://dev.azure.com/ODPi/Egeria/_build/results?buildId=9986&view=logs&j=4dc6fbf2-95db-5f93-ea5a-117822a16d38&t=c86a1d55-7ff7-5cd4-1eec-934a3dda1e85
and reports 'HEAD is now at 958322a7ef Merge f80906668e6c2ef39898387e4600c6ce07a7849f into 2c4f9321b093e9339e0ae43eb4db4ed508ca9feb
'
That build failed in the FVT with
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.163 s - in org.odpi.openmetadata.accessservices.subjectarea.fvt.junit.CategoryHierarchyIT
[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR]   RelationshipsIT.testRelationships:17 Unexpected exception thrown: java.lang.NullPointerException
[ERROR]   RelationshipsIT.testRelationships:17 Unexpected exception thrown: java.lang.NullPointerException
[INFO]
[ERROR] Tests run: 18, Failures: 2, Errors: 0, Skipped: 0

This isn't unusual ... even if master is working just fine, merging back changes into a branch can cause build failures -- as the branch may need updating to fix something those master changes caused.
I see no particular concern with the testing or build process here. Initially I read it as you saying that something was merged INTO master, and then caused the master code to be bad (and failing FVT). But this seems NOT to be the case (other than the fact I know you had a LOCAL issue @davidradl )
In other words, there's no protection about what anyone merges into their own branch - protection is only on the odpi master/release branches, to keep it safe & ensure tests run
Obviously the SMEs (@davidradl @immmus ) may be able to comment on exactly why the NPE occurred and pin down how the error was introduced into master, which may lead to us adding more tests if indeed it was a bug rather than just unfortunate.
If my understanding is incorrect please correct!

I'm trying to understand the situation are describing - we need to be precise in terms of branches and merges.
My understanding from the text above, is that @immmus you noticed a build failure after you merged changes from MASTER into your branch (you said 'pushed the latest changes from the master branch' but I think this is what you meant?) Enchanted_generic_response - which is of course linked to this PR. That merge into your branch would have kicked off a new build which failed (in fact a few did) as the FVTs did indeed run and find an error.
I think the build that represented that merge is here -> https://dev.azure.com/ODPi/Egeria/_build/results?buildId=9986&view=logs&j=4dc6fbf2-95db-5f93-ea5a-117822a16d38&t=c86a1d55-7ff7-5cd4-1eec-934a3dda1e85
and reports 'HEAD is now at 958322a Merge f809066 into 2c4f932
'
That build failed in the FVT with
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.163 s - in org.odpi.openmetadata.accessservices.subjectarea.fvt.junit.CategoryHierarchyIT
[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR]   RelationshipsIT.testRelationships:17 Unexpected exception thrown: java.lang.NullPointerException
[ERROR]   RelationshipsIT.testRelationships:17 Unexpected exception thrown: java.lang.NullPointerException
[INFO]
[ERROR] Tests run: 18, Failures: 2, Errors: 0, Skipped: 0

This isn't unusual ... even if master is working just fine, merging back changes into a branch can cause build failures -- as the branch may need updating to fix something those master changes caused.
I see no particular concern with the testing or build process here. Initially I read it as you saying that something was merged INTO master, and then caused the master code to be bad (and failing FVT). But this seems NOT to be the case (other than the fact I know you had a LOCAL issue @davidradl )
In other words, there's no protection about what anyone merges into their own branch - protection is only on the odpi master/release branches, to keep it safe & ensure tests run
Obviously the SMEs (@davidradl @immmus ) may be able to comment on exactly why the NPE occurred and pin down how the error was introduced into master, which may lead to us adding more tests if indeed it was a bug rather than just unfortunate.
I note we had a large open lineage merge in that period where your branch build failed, as well as another subject area refactor either of which could have broken or fixed your tests
If my understanding is incorrect please correct!

@planetf1 I agree. That makes sense; nice explanation.

Hi @davidradl !
When do you merge this pr?

@immmus sorry I lost track of this one. I will look at it today or tomorrow.

@davidradl Let's resolve these remaining conversations in a next pr?? Because this pr has been hanging for quite some time, I would like to get these changes for further work.

@immus I tested the view services and they seem fine. Please could you address the review feedback I raised in a follow-on issue.

@immus I tested the view services and they seem fine. Please could you address the review feedback I raised in a follow-on issue.

Thx for merge.
Can you give me link on issue?


VM list does not match on PVE 8 version

Hi all,
i found vm list mismatch issue in proxmox version 8.2.2. I tried to reproduce the issue on version 7.3-6 but it didn't happen.
After I tried debugging it turned out that there was a VM that was entered into the template and it shouldn't have been entered.
Debug

log

VM

VM Config

Thank You.

Once I tried analyzing the source code to check if the VM was a template, it didn't seem quite right. because the VM name is the same as the template name it is detected as a template.

Hi, thanks for raising an issue!

because the VM name is the same as the template name it is detected as a template.

Just to confirm, you're saying here that you have a VM template with the same name as an actual VM in your cluster?

yes I have the same vm name as the template name, I've tried editing the source code but still can't fix it, I hope this helps, usually I use the following command to get a list of VM templates:
pvesh get /cluster/resources --output-format json | jq '[.[] | select(.type == "qemu" and .template == 1) | {name: .name, vmid: .vmid}]'

Thanks for the confirmation! I suppose when I was writing that, I had the assumption that most people name their VMs with a purpose rather than a distro. For example my kubernetes VMs are all named controller1-3 and worker1-3, but I think it's fair to cover this case. I'll see what I can do to get a patch for that hopefully later today. The first thing that comes to mind would just be to compare VM ID to VM ID, rather than VM names.

Hey there! This is solved in v0.2.2. Thanks again for the report! :)


Create dependabot yml for package updates, similar to synthetics

This will align the behavior here with synthetics https://github.com/elastic/synthetics/blob/main/.github/dependabot.yml

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-10-24T20:32:49.269+0000

Duration: 10 min 38 sec

:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

/test all : Re-trigger the build for all the stages.


About the reading file npy.

Hi,
Beside getting the validation result from server, the docker image still had some issue.
The error we got from below:
 File "./make_objects_file_from_latency_results.py", line 149, in <module>
    timestamp_dir, context_name, int(timestamp_micros)))
  File "./make_objects_file_from_latency_results.py", line 62, in make_object_list_from_subdir
    boxes = np.load(os.path.join(np_dir, 'boxes.npy'))
  File "./numpy/lib/npyio.py", line 447, in load
    pickle_kwargs=pickle_kwargs)
  File "./numpy/lib/format.py", line 696, in read_array
    raise ValueError("Object arrays cannot be loaded when "
ValueError: Object arrays cannot be loaded when allow_pickle=False

As I know, the /code/evaluator.py (same code as wod_latency_evaluator.py) will run and save the .npy file, then the make_objects_file_from_latency_results.py load this .npy file.
However, both of files are copied or linked by the bazel build from evaluator system (not from us, the file run_latency_evaluation.sh shows this), so how can we set allow_pickle=true in the Dockerfile or docker image to avoid this error?
Thank for your reading and hope to see response soon.

Thanks in advance, the problem solve by converting from boxes with dtype=list to boxes with dtype=ndarray


Sprint 2

DoneDone :white_check_mark:

[x] CheckStyle
[x] Exercise download (with course id)
[x] User logout

Also introducing: tests with WireMock :satellite:

Changes Unknown when pulling 28e3d1d102393443482e35611b8a682c6ddd81b0 on devmaster into ** on master**.

Changes Unknown when pulling 12f9a0020a28e3357a213d68f5b95ae4a43942de on devmaster into ** on master**.

Changes Unknown when pulling 201ddf3ba6448a393be09603ce4367e5b36db323 on devmaster into ** on master**.

Changes Unknown when pulling 32b1c452e47d9b4ae049e6dc3a39c2552a469542 on devmaster into ** on master**.

Changes Unknown when pulling 9299c67986b5067e520584fe29df4fe10d4e782e on devmaster into ** on master**.

Changes Unknown when pulling 9299c67986b5067e520584fe29df4fe10d4e782e on devmaster into ** on master**.

Changes Unknown when pulling d645a9ab75a8d08a3570256040ceda437d7cae5d on devmaster into ** on master**.

Changes Unknown when pulling f3d07511f83be6b154691c57d62d64fb565666fe on devmaster into ** on master**.

Changes Unknown when pulling bd9b2ff15308fa5dd21817e263a81e4ac90a9626 on devmaster into ** on master**.

Changes Unknown when pulling 0958f51ac933ce05e5b6518ebc748989d22702b4 on devmaster into ** on master**.

Changes Unknown when pulling 8ee75a41ecc4154c71ef6a53c8859efdbff43953 on devmaster into ** on master**.

Changes Unknown when pulling 2861b40a972dcd61ed4b9dc84190b53630b1f3ca on devmaster into ** on master**.

Changes Unknown when pulling 59b737c45ede01f93152bbe9d0a6de050c4a5015 on devmaster into ** on master**.

Changes Unknown when pulling 59b737c45ede01f93152bbe9d0a6de050c4a5015 on devmaster into ** on master**.

Changes Unknown when pulling 48a0f783fb7234bd6263e057349b7774d8cf2a9c on devmaster into ** on master**.

Changes Unknown when pulling d50264272ea41f1ad9982e6e519279ea7003bb45 on devmaster into ** on master**.

Changes Unknown when pulling 778cd82da093bea3cf04f2cb897d7739f7a723cc on devmaster into ** on master**.

Changes Unknown when pulling 69889e312aef34c8b380143f4204850c64dfd120 on devmaster into ** on master**.

Changes Unknown when pulling e23ddd67024bae198fce347a875c2a7587456fd7 on devmaster into ** on master**.

Changes Unknown when pulling<PHONE_NUMBER>6bc15ee223c9eed28bec71b162cea5 on devmaster into ** on master**.


Questions about high availability

Does quay-operator support the setup as described in Deploy Project Quay - High Availability? Any caveats?
Does quay-operator support hosting components across multiple Kubernetes clusters (i.e. to tolerate the loss of any single Kubernetes cluster)? If not, is this something the authors would consider? Or can multiple quay-operators be configured to coordinate such a multi-cluster setup?

Thanks!

From this page, it seems this is possible with geo-location:

Geo-replication allows multiple, geographically distributed Red Hat Quay deployments to work as a single registry from the perspective of a client or user.

With Red Hat Quay 3.7, deployments of Red Hat Quay with geo-replication is supported by standalone and Operator deployments.


MSID: 98949 Version: 2 DOI: 10.1101/2<IP_ADDRESS>2074

MSID: 98949
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>2074
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=98949
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>2074

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/98949v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>2074
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/98949/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

(no schematron messages)

https://sciety.org/evaluations/hypothesis:voUjMF4eEe-UNSu3BKuz7A/content


Usage with Svelte

How would I use flamethrower js with svelte as a router. Thanks.

Doesn't svelte already do what this project does?


"-h / --help" double output fix

Hi, Daniel!
Thanks for your gem, it was really good idea to make it.
I installed it and tried to read options with "--help". I got help 2 times.
So this PR fixes this little bug.
Also I've changed some files with RuboCop advices.
Hope, can help you with "unbinding" gem from ruby 2.2.2 version in future.
Alexandr

Thanks, pups3s. Run Rubocop on these files was on To-do list.


Workspace- While inviting members, the contact selected is not shown

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to https://staging.new.expensify.com/
Tap profile icon
Tap Workspace
Create new workspace
Tap Members
Tap members
Tap Invite
Scroll down and select contacts

Expected Result:
After user selected a contact, the page must automatically scrolls up and he must be shown the selected contact with green tick
Actual Result:
After user selected a contact, a jump is shown but page not scrolled up automatically to show the selected contact with green tick. The user has to scroll up and see the contacts selected
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.57-2
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/78819774/143ff00c-f5fc-4ca2-acfc-f9ff9c4ee126
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

@jeet-dhandha I don't think it was always an expected behavior. Do you have any links to where this was discussed?

Slack - https://expensify.slack.com/archives/C01GTK53T8Q/p1670238226611139
Issue - https://github.com/Expensify/App/issues/12998

@thiagobrez will you please take a look at this and give us your thoughts.

@joelbettner I wasn't aware of this behavior, will work on it

confirmed this is fixed in staging and not reporting bonus, closing

Issue reproducible on Build 1.3.84-0
https://github.com/Expensify/App/assets/78819774/8d546bf3-d81f-4470-b61a-b162e312d33d

@mountiny should this be close similar to https://github.com/Expensify/App/issues/25883#issuecomment-1693849387
If not...I think @dylanexpensify might be the person to assign to this to make sure it gets paid since he was also on this.


me myself and i, thats who i am i swear]

ya so i was just stalking ur profile for no reason and i saw yoy asked rlly nicely for people to sign ur guestbook so here i am, kthxbye

hey man i know i'm over half a year late but i love your website but yea thanks for signing the book

am catgirl :3 thanks for the compliment!!


HDDS-4651: Distributed Sequence ID Gen.

What changes were proposed in this pull request?
Monotonically Increased ID Supporting Switch Between Non-Ratis SCM and Ratis-Based SCM.

SCM allocates ids in a batch way. It maintains two fields: lastId and nextId. It saves the lastId in rocksDB. The initial value of nextId is firstId.
When getNextId() is called, if nextId is less than lastId, SCM just returns nextId and increases it, otherwise it calls allocateBatch(expectedLastId, newLastId) to allocate a batch of ids, then serves the request.
In allocateBatch(expectedLastId, newLastId) , it works in CAS way:
it reads lastId from rocksDB.
if lastId equals expectedLastId, it saves newLastId into rocksDB, returns success, otherwise it rejects the allocation request.
It also provides a getLastId() to read lastId from rocksDB. The allocation works in a loop way:

See https://docs.google.com/document/d/13qSwLuDBw7mytJtF9h2oauuLocFfr-XJSBdTfc1YvxM/edit?usp=sharing
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4651
How was this patch tested?
CI

@mukul1987  @bshashikant @amaliujia  Please take look!
Monotonically Increased ID Supporting Switch Between Non-Ratis SCM and Ratis-Based SCM.

Do we need to handle overflow for "long" used here for lastId?

Thanks for the advice, I've add the check.

With these approach, we won't have monotonically increasing containerIds or block ids. IDs will be monotonically increasing within a batch.

Could you find a situation that containerId or blockId is not  monotonically increasing ? For non-HA mode, it is straightword that the id is monotonically increasing. For HA mode, since only leader can request a nextID, and leader will always refresh lastId from db and allocate a new batch, a new leader will always generate larger id than previous leader, thus monotonically increasing too.

We need to handle the upgrade scenario. This needs to be handled before the branch gets merged otherwise all existing setups won't work.

We have a discussion in the design doc:

need a hook to be used in upgrade, to ensure the monotonicity of id during switch from previous ids to current solution:
localId : the initial value should be UniqueId() + 1
containerID: scan the container db, figure the largest containerID ever used.
delTx: read from DeletedBlocksTXTable, see HDDS-4477 contributed by Lokesh.

So, we can simply use UniqueId() + 1, since containerID and delTx can not be larger than UniqueId() + 1.

Do we need to handle overflow for "long" used here for lastId?

Thanks for the advice, I've add the check.

With these approach, we won't have monotonically increasing containerIds or block ids. IDs will be monotonically increasing within a batch.

Could you find a situation that containerId or blockId is not monotonically increasing ? For non-HA mode, it is straightword that the id is monotonically increasing. For HA mode, since only leader can request a nextID, and leader will always refresh lastId from db and allocate a new batch, a new leader will always generate larger id than previous leader, thus monotonically increasing too.

What i meant was, containerIds are not sequentially increasing which is a departure from the current behaviour which is strictly sequentially increasing containerIds. and we are using the same seqID generator for both Container as well as block.
This may become the reason for scale limitation.
Instead of that, why can't we use lastAppliedIndex as base for containerIds.

We need to handle the upgrade scenario. This needs to be handled before the branch gets merged otherwise all existing setups won't work.

We have a discussion in the design doc:

need a hook to be used in upgrade, to ensure the monotonicity of id during switch from previous ids to current solution:
localId : the initial value should be UniqueId() + 1
containerID: scan the container db, figure the largest containerID ever used.
delTx: read from DeletedBlocksTXTable, see HDDS-4477 contributed by Lokesh.

So, we can simply use UniqueId() + 1 as INVALID_SEQUENCE_ID, since containerID and delTx are starting from 1, practically they can not be larger than UniqueId() + 1.

Are u going to address these changes in subsequent PR as this will be required for branch merge?

Do we need to handle overflow for "long" used here for lastId?

Thanks for the advice, I've add the check.

With these approach, we won't have monotonically increasing containerIds or block ids. IDs will be monotonically increasing within a batch.

Could you find a situation that containerId or blockId is not monotonically increasing ? For non-HA mode, it is straightword that the id is monotonically increasing. For HA mode, since only leader can request a nextID, and leader will always refresh lastId from db and allocate a new batch, a new leader will always generate larger id than previous leader, thus monotonically increasing too.

What i meant was, containerIds are not sequentially increasing which is a departure from the current behaviour which is strictly sequentially increasing containerIds. and we are using the same seqID generator for both Container as well as block.
This may become the reason for scale limitation.
Instead of that, why can't we use lastAppliedIndex as base for containerIds? Sequence Ids can be used for block Ids and can be rest to zero once all the containers are closed.

We need to handle the upgrade scenario. This needs to be handled before the branch gets merged otherwise all existing setups won't work.

We have a discussion in the design doc:

need a hook to be used in upgrade, to ensure the monotonicity of id during switch from previous ids to current solution:
localId : the initial value should be UniqueId() + 1
containerID: scan the container db, figure the largest containerID ever used.
delTx: read from DeletedBlocksTXTable, see HDDS-4477 contributed by Lokesh.

So, we can simply use UniqueId() + 1 as INVALID_SEQUENCE_ID, since containerID and delTx are starting from 1, practically they can not be larger than UniqueId() + 1.

Are u going to address these changes in subsequent PR as this will be required for branch merge?

The upgrade work will be handled in a different PR. Thanks @GlenGeng for the work.


es: relocate {storage,graph}.backend

Effort should be consolidated with #968

was handled in #983


Support for 0.14 and was >3

Hi,
I am looking for working examples of the current versions of terraform and AWS Provider. When trying to apply the code I am getting (Deploying a Load Balancer from chapter 2)  errors:

Error: Error creating Auto Scaling Group: ValidationError: The subnet ID 'vpc-XXXXX' does not exist
        status code: 400, request id: 87fa912f-1465-4066-83a8-41cd7d7397ba

  on main.tf line 32, in resource "aws_autoscaling_group" "example":
  32: resource "aws_autoscaling_group" "example" {

The error was due to an wrong variable (that was mean):
resource "aws_autoscaling_group" "example" {
  launch_configuration = aws_launch_configuration.example.name
  vpc_zone_identifier  = data.aws_subnet_ids.default.ids

I had wrongly used (missing s):
vpc_zone_identifier  = data.aws_subnet_ids.default.id

Ah, yup, that'll do it. Thx for including the resolution!


Tool not working

This is awesome tool. i have used one week ago that time it was working very smoothly. But now it is not working.

What do you mean by not working? Could you please provide more data?


Simplify the getAccess method in the CLI

Since we can parse the flags in the base class, this does so to reduce the verbosity of getAccess().
It also makes some fixes to get rid of some eslint-disable directives

@dariober When I was removing some of the eslint-disable directives, I realized we were using /dev/stdin to read from stdin. Since that's not portable cross-platform (.e.g. on Windows), I changed it to use process.stdin, but had to make the idReader async to do so. I don't think it affected anything, but would appreciate you double-checking.
Also, should this be removed? From what I remembered, .clirc was what we used before we used the conf package.
https://github.com/GMOD/Apollo3/blob/28c2d3370356a0cf4caae644c80b1a9750d98fc5/packages/apollo-cli/src/utils.ts#L25

@garrettjstevens Look good to me

I changed it to use process.stdin, but had to make the idReader async to do so

I changed edit.ts accordingly

Also, should this be removed? From what I remembered, .clirc was what we used before we used the conf package.

Yes, it seems so. I removed it and simplified the checking if user is already logged in (674e4ff).


"Incorrect Argument for command" error occurs everytime an event item is attempting to be given out

Describe the bug
everytime there's a new event (e.g. New Years Celebration) the plugin automatically gives an item(as expected) but it seems like there is something wrong with the commands as they can't be carried out correctly.
it seems it may be related to the naming of the items where it is failing
How to reproduce

advanced seasons on 1.21
set to any seasonal event
bam

Screenshots / Videos
No response
Server Log
No response

an example of the command in question: give %player% cookie 1 name:&2Christmas_Treat

Those commands are stored in events.yml. I uploaded the fixes.


Handle refreshCall failure with resendFailedRequest and always reset …

What this PR does / why we need it:

Add resendFailedRequest function & test
Add unsetState function & test
In index.ts, the refreshCall function is now invoked to handle token refresh logic
update types.d.ts refreshJwtCalll ->  Promise | undefined

This PR introduces the refreshCall function to handle token refresh operations in index.ts. It ensures that if the refreshCall fails, the request is retried using the resendFailedRequest function. After execution, the state is always reset using the unsetState function to maintain a consistent and clean state. Additionally, the types.d.ts has been updated to reflect that refreshJwtCall can now be of type Promise | undefined. …state after execution
Which issue(s) this PR fixes:

Fixes #14
Special notes for your reviewer:

Please verify that the state resetting logic works as expected after the refresh process.
Review the test cases added for resendFailedRequest and unsetState functions to ensure comprehensive coverage.

Does this PR introduce a user-facing change?:

x

Additional documentation:

x

Checklist:

[x] Added relevant tests or not required
[x] Didn't break anything

Summary by CodeRabbit

New Features

Enhanced error handling for authentication token refresh, allowing for automatic retry of failed HTTP requests.
Introduced functionality to resend failed requests with specified conditions.
Added a cleanup function to manage Axios interceptors and state effectively.

Bug Fixes

Improved handling of scenarios where the JWT refresh call may not exist, preventing potential runtime errors.

Tests

Added unit tests to validate the behavior of the new request handling and state management functions.

The configuration for retry attempts and the handling of different types of errors is currently missing. I will create a separate issue to address this


Consider adding a namespace to the proto file in our grpc template

option csharp_namespace
    = "WebApplication43.Generated";

@JamesNK / @JunTaoLuo / @shirhatti - do we need this in preview5 or should we wait for preview6? Template changes often have unexpected risk.

I created this issue, but I'm not convinced it's a good idea. We definitely need to debate this.

Turns out this would be possible. The option only affects the C# namespace and is independent of the package name. It just so happens that the namespace defaults to the package name. E.g.
syntax = "proto3";

option csharp_namespace = "Grpc";

package Greet;

// The greeting service definition.
service Greeter {
  // Sends a greeting
  rpc SayHello (HelloRequest) returns (HelloReply) {}
}
...

Generates:
namespace Grpc {
  ///
  /// The greeting service definition.
  ///
  public static partial class Greeter
  {
    static readonly string __ServiceName = "Greet.Greeter";

    static readonly grpc::Marshaller<global::Grpc.HelloRequest> __Marshaller_Greet_HelloRequest = grpc::Marshallers.Create((arg) => global::Google.Protobuf.MessageExtensions.ToByteArray(arg), global::Grpc.HelloRequest.Parser.ParseFrom);
    static readonly grpc::Marshaller<global::Grpc.HelloReply> __Marshaller_Greet_HelloReply = grpc::Marshallers.Create((arg) => global::Google.Protobuf.MessageExtensions.ToByteArray(arg), global::Grpc.HelloReply.Parser.ParseFrom);

    static readonly grpc::Method<global::Grpc.HelloRequest, global::Grpc.HelloReply> __Method_SayHello = new grpc::Method<global::Grpc.HelloRequest, global::Grpc.HelloReply>(
        grpc::MethodType.Unary,
        __ServiceName,
        "SayHello",
        __Marshaller_Greet_HelloRequest,
        __Marshaller_Greet_HelloReply);

    /// Service descriptor
    public static global::Google.Protobuf.Reflection.ServiceDescriptor Descriptor
    {
      get { return global::Grpc.GreetReflection.Descriptor.Services[0]; }
    }

    /// Base class for server-side implementations of Greeter
    public abstract partial class GreeterBase
    {
      ///
      /// Sends a greeting
      ///
      /// <param name="request">The request received from the client.</param>
      /// <param name="context">The context of the server-side call handler being invoked.</param>
      /// <returns>The response to send back to the client (wrapped by a task).</returns>
      public virtual global::System.Threading.Tasks.Task<global::Grpc.HelloReply> SayHello(global::Grpc.HelloRequest request, grpc::ServerCallContext context)
      {
        throw new grpc::RpcException(new grpc::Status(grpc::StatusCode.Unimplemented, ""));
      }

    }
...

The value __ServiceName  is the actual value used for generating routes.
@shirhatti In this case, we'd probably want to make this change?


Hyundai CAN-FD: support for ICE cars

Checklist

[x] added entry to CarInfo in selfdrive/car/*/values.py and ran selfdrive/car/docs.py to generate new docs
[x] test route added to routes.py

2022 Hyundai Santa Cruz

[x] route with openpilot:

stock longitudinal: f0709d2bc6ca451f|2022-10-15--08-13-54
openpilot longitudinal: f0709d2bc6ca451f|2022-10-15--10-39-32

[x] harness type: Hyundai N

2023 Kia Sportage

[x] route with openpilot:

stock longitudinal: 192283cdbb7a58c2|2022-10-15--00-57-57
openpilot longitudinal: 192283cdbb7a58c2|2022-10-15--01-43-18, 965a780ebeeed150|2022-10-16--20-50-38

[x] harness type: Hyundai N

2022 Genesis GV70

[x] route with openpilot: ca4de5b12321bd98|2022-10-18--21-15-59
[x] harness type: Hyundai L

Physical setup

Top port behind comma three

comma Power <-> First Harness Box <-> comma three USB C/Right-Angle C <-> comma three

Bottom port behind comma three

Camera Harness <-> Second Harness Box <-> USB C/C 3.1 <-> Red Panda <-> USB A/A <-> USB A to C OTG Adapter <-> comma three

openpilot Longitudinal Control

openpilot longitudinal control support for 2022 Hyundai Santa Cruz (ICE) and 2023 Kia Sportage (ICE), without radar disable. Message 0x1a0 | CRUISE_INFO is on bus 6, we block the message from bus 6 and send our own longitudinal commands to 0x1a0 | CRUISE_INFO bus 4.

Prerequisites

https://github.com/commaai/openpilot/pull/25276
https://github.com/commaai/panda/pull/999

Requires

https://github.com/commaai/openpilot/pull/26086
https://github.com/commaai/panda/pull/1031
https://github.com/commaai/opendbc/pull/680

Thanks to community Santa Cruz owner chrsfr, Sportage owner gaanthony and Daltoh, and GV70 owner zunichky.

Closed the gv70 (#26068) pr so we only have one open.

@adeebshihadeh @sunnyhaibin Idk if there are any more cars that are going to be like this, or if it's a genesis thing, so not sure how we want these changes generic.
GV70 LAT Changes: CRUISE_INFO comes from bus 4 not 6, so this bus needs to be changed to 4. return CANParser(DBC[CP.carFingerprint]["pt"], signals, checks, 6)
GV70 LONG Changes: Maybe make this into a different PR? Radar/TP: 0x7d0, 4 CAM_0x2a4 comes from bus 5 In create_adrv_messages, I only need to send ADRV_0x160 to keep the car happy (mines HDA1, no side radars)

I can try to take care of the change with CRUISE_INFO in carstate.
I agree with having another PR for GV70's longitudinal support, with 0x1A0 being on bus 4 and we need to disable radar unlike the other ICE models we're supporting in this PR. We could submit another one once this is merged.

@sunnyhaibin CarTestRoute("f0709d2bc6ca451f|2022-10-15--10-39-32", HYUNDAI.SANTA_CRUZ_1ST_GEN), doesn't have rlogs. can we get a new route?

@sunnyhaibin CarTestRoute("f0709d2bc6ca451f|2022-10-15--10-39-32", HYUNDAI.SANTA_CRUZ_1ST_GEN), doesn't have rlogs. can we get a new route?

@adeebshihadeh would the ones from the PR description suffice? I believe they have rlogs uploaded. If not, we can request new ones from the Santa Cruz user.

@sunnyhaibin CarTestRoute("f0709d2bc6ca451f|2022-10-15--10-39-32", HYUNDAI.SANTA_CRUZ_1ST_GEN), doesn't have rlogs. can we get a new route?

@adeebshihadeh would the ones from the PR description suffice? I believe they have rlogs uploaded. If not, we can request new ones from the Santa Cruz user.

Yeah, looks like that'll work.

@adeebshihadeh User with the Sportage 2023 mentioned that he received a Controls Mismatch alert when he installed the latest version:

192283cdbb7a58c2|2022-10-22--11-49-07

Checked and there's no common gear message :(. There's a duplicate gear signal in the ACCELERATOR message for our EV6, but it's not filled out on the Santa Cruz

Removed the GV70 from this PR as it's the sole HDA1 car where the camera doesn't do SCC (radar). @sunnyhaibin is making another PR just for that car


About universes

Currently, the typing rule for sorts is:
               Γ ⊢
--------------------------------------
Γ ⊢ Universe.make l : Universe.super l

Hence, algebraic universes (i.e. universes which are not a single level) should not appear at the left of a colon.
Do you agree that type inference should fail on terms containing algebraic universes?
Wellformedness is then:
Γ ⊢ t : A  ->  Γ ⊢ A : s  or  A is a sort

Is it correct?
If so, should we change the conversion rule from:
Γ ⊢ t : A      Γ ⊢ B : s
------------------------------------  (A ≡ B)
            Γ ⊢ t : B

to
Γ ⊢ t : A      Γ ⊢ B : s or B a sort
------------------------------------  (A ≡ B)
            Γ ⊢ t : B

???

Indeed, it's a quirk of Coq's type-checker. Indeed the generation lemma is not "clean" due to that. We can go for the conversion rule you propose, it's substitutive a priori. One step I've been thinking about is to show equivalence with a system without type inference where where the typing rule for universes looks like i < j |- Type i < Type j, and products: max(i,j) <= k |- Prod (x : A : Typei) (B x : Type j) : k, which would have a nicer generation lemma.

We changed the conversion rule a while ago


fix(ProLabel): add title

Overview

Adds a title tag to the ProLabel svg to fix an a11y bug on the catalog pages. The title is "Pro only" which matches what is currently read on the pro label for curriculum cards.

To test:

visit https://portal-app-pr-158.dev-eks.codecademy.com/catalog
open voice over and navigate via tab onto a career path card
confirm that it reads "pro only career path    ...."
navigate to a not pro course
confirm that it does not read "pro only"

PR Checklist

[ ] Related to designs:
[x] Related to JIRA ticket: REACH-1076
[x] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.40-alpha.50e91f.0@codecademy/gamut-labs@19.10.6-alpha.50e91f.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60d0e923bc28c98c540ff9e9--gamut-preview.netlify.appDeploy Logs

hold on reviewing, this is not the correct way of solving this problem

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.40-alpha.71060c.0@codecademy/gamut-labs@19.10.6-alpha.71060c.0@codecademy/gamut@34.10.4-alpha.71060c.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60d0f87f341eb600cb611454--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.41-alpha.b09b67.0@codecademy/gamut-labs@19.10.7-alpha.b09b67.0@codecademy/gamut@34.10.5-alpha.b09b67.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60d101a0da44c97bce9c02ce--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.4.42-alpha.b2cf21.0@codecademy/gamut-labs@19.10.8-alpha.b2cf21.0@codecademy/gamut@34.10.6-alpha.b2cf21.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60d113cafef65653bbe11ac2--gamut-preview.netlify.appDeploy Logs


[substrait] make dependency on parquet optional

Is your feature request related to a problem or challenge?
The datafusion-substrait package currently depends on the datafusion crate with all default features enabled. This can force users that might want to use the substrait package to always have at least all the datafusion default features turned on.
Describe the solution you'd like
I propose that we hide parts of the datafusion-substrait crate that depend on datafusion's default feature behind some feature flags (enabled by default but that can be disabled by users)
Describe alternatives you've considered
No response
Additional context
No response

take


[SDP-1032] Add logs for any changes in user profile or the organization profile

What
Start logging important changes on user or organization profiles, for traceability. Here are the functions that are now being logged:

Changes made through PatchOrganizationProfile

Log message: log.Ctx(ctx).Warnf("[PatchOrganizationProfile] - userID %s will update the organization fields %v", user.ID, nonEmptyKeys)

Changes made through PatchUserProfile

Log message: log.Ctx(ctx).Warnf("[PatchUserProfile] - Will update email for userID %s to %s", user.ID, utils.TruncateString(reqBody.Email, 3))

Changes made through PatchUserPassword

Log message: log.Ctx(ctx).Warnf("[UpdateUserPassword] - Will update password for user account ID %s", user.ID)

Why
So we can track changes made in user profiles or Organization profiles, for accountability.
Checklist
PR Structure

[x] This PR has a reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR title and description are clear enough for anyone to review it.
[x] This PR does not mix refactoring changes with feature changes (split into two PRs otherwise).

Thoroughness

[x] This PR adds tests for the new functionality or fixes.
[x] This PR contains the link to the Jira ticket it addresses.

Configs and Secrets

[x] No new CONFIG variables are required -OR- the new required ones were added to the helmchart's values.yaml file.
[x] No new CONFIG variables are required -OR- the new required ones were added to the deployments (pr-preview, dev, demo, prd).
[x] No new SECRETS variables are required -OR- the new required ones were mentioned in the helmchart's values.yaml file.
[x] No new SECRETS variables are required -OR- the new required ones were added to the deployments (pr-preview secrets, dev secrets, demo secrets, prd secrets).

Release

[x] This is not a breaking change.
[x] This is ready for production.. If your PR is not ready for production, please consider opening additional complementary PRs using this one as the base. Only merge this into develop or main after it's ready for production!

Deployment

[x] Does the deployment work after merging?

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr145.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr145.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr145.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr145.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr145.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr145.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr145.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr145.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr145.previews.kube001.services.stellar-ops.com


Wrong getter is called when interface conformance is re-asserted

This code produces incorrect results:
shared interface I {
    shared default String foo => "1";
    shared default String bar() => "1";
}

shared class C() satisfies I {
    shared actual default String foo => "2";
    shared actual default String bar() => "2";
}

shared class D() extends C() satisfies I {}

shared void testingD() {
    print(D().foo);     // prints 1
    print(D().bar());   // prints 2
}

Note: it's also possible to have Interface J satisfy I {}, and produce the error by satisfying J, which is happening in ceylon.html.

Ouch!

I didn't quite get the interface J part. I defined interface J satisfies I and refined foo and bar in J, then created a class E() satisfies J, and got the values defined in J, not in I.

In ceylon.html, J doesn't refine foo, it's just that it's J that is satisfied by the D/E class, not I directly.


OrderEnforcing error

Hello,
I am trying to run your code and make developments. I cloned your repo and installed it in editable mode with -e. Then I tried to run the demo.ipynb I faced with the following error from this cell:
CELL:
import gymnasium
import matplotlib.pyplot as plt
# importing mobile_env automatically registers the predefined scenarios in Gym
import mobile_env

# create a small mobile environment for a single, centralized control agent
# pass rgb_array as render mode so the env can be rendered inside the notebook
env = gymnasium.make("mobile-small-central-v0", render_mode="rgb_array")

print(f"\nSmall environment with {env.NUM_USERS} users and {env.NUM_STATIONS} cells.")

ERROR:

{
	"name": "AttributeError",
	"message": "'OrderEnforcing' object has no attribute 'NUM_USERS'",
	"stack": "---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
Cell In[2], line 10
      6 # create a small mobile environment for a single, centralized control agent
      7 # pass rgb_array as render mode so the env can be rendered inside the notebook
      8 env = gymnasium.make(\"mobile-small-central-v0\", render_mode=\"rgb_array\")
---> 10 print(f\"\
Small environment with {env.NUM_USERS} users and {env.NUM_STATIONS} cells.\")

AttributeError: 'OrderEnforcing' object has no attribute 'NUM_USERS'"
}

Also when I try to run a simulation, it works but after that, when I try to access the aatributes of the env object I cannot.
My python version is 3.9.20
Is there a solution that you can suggest to fix and run the notebooks?
Thank you

This is the errors I am getting

I just merged a PR to limit gymnasium support to <1.0.0. Let me know if this fixes your issue for now.
if it doesn't, feel free to reopen this issue.

Hello again,
Thank you very much for your quick reply and fix. Downgrading the Gymnasium library version helped me to fix the problem. The notebooks are running without any problem now.


Add check for undocumented names; remove a dangling exported function

I'll fix the documentation problem

Hmm, CI complaines that  GridVisualize.GridVisualize is not in the docs. That is true. But I wanted to use the README as documentation for this. Where do I put this in the docs?

We could do an allindex.md similar to how VoronoiFVM does it https://wias-pdelib.github.io/VoronoiFVM.jl/stable/allindex/
inside the public api part of docs.

I always would put the module doc on top of docs/src/index.md

I solved it in GridVisualizeTools like this https://github.com/WIAS-PDELib/GridVisualizeTools.jl/pull/18/commits/d94e6327966140b182bcf763f12a764168729d0c
@j-fu, did you check the resulting docs to see if you like how the result looks?

I checked the docs locally, it works.

Good.
Can we remove the unrelated formatting commit from this PR? or move it to #57 ?

this is just the pluto notebook thing. I think it is not worth to bother that much about this. I would just keep it here, if you want to move it, it's ok as well.

I have removed the unrelated change to examples/plutovista.jl from 'update index.md' and with it the wrong format introduced therein.

Should be good now


Update qhimm.xml

attempt at adding "Realistic, Subtle World Map Animations" and "High-Detail World Map" under the 'World Textures' category

i commented in the wrong place. I don't think you'll see it, so
gdrive links specifically have to be like this:
iros://GDrive/1fGaXEbimhHTw7n393h0IUBb2V7b4nfa1
also, your date was backwards (year comes first) and the download size can't be blank (idk how big they are so I just put 1mb until you can fix it.
the entire catalog breaks if any of these things are done like that... but from here on out you'll pretty much just be editing what's already there.


[BUG]: aks-log-collector.sh creates a large ip_netns_commands.txt which lead to ephemeral-storage issues #4148

What happened:  cf https://github.com/Azure/AKS/issues/4148
Describe the bug
We have observed that files ip_netns_commands.txt (example of location folder /tmp/tmp.4FKbTfOrn4/collect) in our AKS cluster nodes sometimes growing to many GBs and when the size comes to around 90GB nodes start having issues with ephemeral storage (The node was low on resource: ephemeral-storage.) then pods become evicted and multiple other issues appear.
root@aks-apps5--vmss000014:/tmp/tmp.4FKbTfOrn4/collect# ls -lh ip_netns_commands.txt
-rw-r--r-- 1 root root 38G Mar  7 13:19 ip_netns_commands.txt
root@aks-apps5--vmss000014:/tmp/tmp.4FKbTfOrn4/collect# fuser -v ip_netns_commands.txt
USER        PID ACCESS COMMAND
/tmp/tmp.4FKbTfOrn4/collect/ip_netns_commands.txt:
root      83233 F.... ip
root      109814 F.... ip
root      560481 F.... ip
root      1133085 F.... ip
root      1133086 F.... ip
root      1133087 F.... ip
root      1134797 F.... ip
root      1737066 F.... ip
root      1737172 F.... ip
root      1737210 F.... ip
root      1737451 F.... ip
root@aks-apps5--vmss000014:/tmp/tmp.4FKbTfOrn4/collect# pstree -aps 83233
systemd,1
└─aks-log-collect,61814 /opt/azure/containers/aks-log-collector.sh
└─ip,83233 -all netns exec /bin/bash -x -c...
└─ip,109814 -all netns exec /bin/bash -x -c...
└─ip,1737066 -all netns exec /bin/bash -x -c...
└─ip,1737172 -all netns exec /bin/bash -x -c...
└─ip,1737210 -all netns exec /bin/bash -x -c...
└─ip,1737451 -all netns exec /bin/bash -x -c...
└─ip,560481 -all netns exec /bin/bash -x -c...
└─ip,1133085 -all netns exec /bin/bash -x -c...
└─bash,1147264 -x -c...
└─ss,1147282 -anoempiO --cgroup
root@aks-apps5--vmss000014:/tmp/tmp.4FKbTfOrn4/collect# head --lines 20 /opt/azure/containers/aks-log-collector.sh
#! /bin/bash

AKS Log Collector

This script collects information and logs that are useful to AKS engineering
for support and uploads them to the Azure host via a private API. These log
bundles are available to engineering when customers open a support case and
are especially useful for troubleshooting failures of networking or
kubernetes daemons.

This script runs via a systemd unit and slice that limits it to low CPU
priority and 128MB RAM, to avoid impacting other system functions.
Log bundle upload max size is limited to 100MB
MAX_SIZE=104857600
Shell options - remove non-matching globs, don't care about case, and use
extended pattern matching
shopt -s nullglob nocaseglob extglob
AKS 1.28.5

One way to stop the issue is disabling log collector on the nodes, it is controlled by a timer systemd unit.
systemctl stop aks-log-collector.timer
systemctl disable aks-log-collector.timer

This would have to be ran on every node. We are looking into a "long term" fix for this issue.

fixed in https://github.com/Azure/AgentBaker/pull/4357


Error at startup and during stash operation

GitLens Version: 4.4.1
VSCode Version: 1.15.1
OS Version: Ubuntu 16.04.3

Steps to Reproduce:

Start VSCode or stash / unstash any file in Git
Have an error message displayed by VSCode : "Error: Path must be a string. Received undefined"

Output with verbose gitlens.outputLevel
GitLens(v4.4.1) active: /home/florian/dev/foo
Git found: 2.7.4 @ /usr/bin/git
git -c core.quotepath=false rev-parse --show-toplevel   cwd='/home/florian/dev/foo'
Git version: 2.7.4
CodeLens config changed; resetting CodeLens provider
getRemotes('/home/florian/dev/foo')
getRemotes('/home/florian/dev/foo')
git -c core.quotepath=false remote -v   cwd='/home/florian/dev/foo'
git -c core.quotepath=false remote -v   cwd='/home/florian/dev/foo'
getStash('/home/florian/dev/foo')
git -c core.quotepath=false stash list --name-status --full-history -M --format=%H -%nauthor-date %ai%nreflog-selector %gd%nsummary %B%nfilename ?   cwd='/home/florian/dev/foo'

Console output in dev tools :
Path must be a string. Received undefined: TypeError: Path must be a string. Received undefined
    at assertPath (path.js:7:11)
    at Object.resolve (path.js:1146:7)
    at GitStashCommit.get uri [as uri] (/home/florian/.vscode/extensions/eamodio.gitlens-4.4.1/out/src/git/models/commit.js:39:39)
    at StashCommitNode (/home/florian/.vscode/extensions/eamodio.gitlens-4.4.1/out/src/views/stashCommitNode.js:17:45)
    at system_1.Iterables.map.c (/home/florian/.vscode/extensions/eamodio.gitlens-4.4.1/out/src/views/stashNode.js:25:76)
    at Object.map (/home/florian/.vscode/extensions/eamodio.gitlens-4.4.1/out/src/system/iterable.js:88:19)
    at map.next (<anonymous>)
    at StashNode.<anonymous> (/home/florian/.vscode/extensions/eamodio.gitlens-4.4.1/out/src/views/stashNode.js:25:43)
    at Generator.next (<anonymous>)
    at fulfilled (/home/florian/.vscode/extensions/eamodio.gitlens-4.4.1/out/src/views/stashNode.js:4:58)

Also, stash explorer remain empty even with some files stashed in Git.
I'll try to debug this but thought it was worth report it if someone experimented the same.

@Florian-R If you run a git stash list on the command line does any look strange? I'm wondering where in the stash output parsing something is going wrong.

@eamodio Dont think anything seems weird
10:34 $ git stash list
stash@{0}: WIP on form-improvements: 230f1b4 Make FileInput text configurable

FTR, in case it could help
10:42 $ git --version
git version 2.7.4

I'll try to dig more but no time at all actually :/

Very strange, I can't reproduce anything like this. Will dig more into it via code inspection.

Without debugging that much, I think I understand what's going on.
For some reason (which I'll call for now the dark arcanes of Linux and i18n), I recently had to tweak some locale related env vars, but this as the effect to change my git output to french instead of english.
Re-reading your statement :

I'm wondering where in the stash output parsing something is going wrong.

Could this be related in some way? After forcing git to output english, I don't have this error anymore and the stash explorer work as intended.

@Florian-R that is definitely it -- GitLens can only deal with parsing English output from git. Sorry about that.

No problem. Thanks for your input and your extensions.
I'll close this one as it works as intended.


DO NOT MERGE YET Mup 12307 json serialization tests

Original JIRA:
https://meetup.atlassian.net/browse/MUP-12307
Issues
1. This does not seem doable, or doable well, without something like Scalacheck + Shapeless.
My attempt was incomplete and I’m not sure I could get it to be complete.  You can see my attempts in the branch’s check-in history — see the stuff removed here: https://github.com/meetup/meetup-scala-generator/pull/64/commits/31e12102f4eef91d021b22e5a5694a917ff86826  (it's messy but not sure a better way to reference it)
2. Scalacheck + Shapeless are impressive but introduce new issues:

The build fails sometimes, in a way that is not reproducible.  Unclear if it’s an actual serialization bug or bug in the libs, and if so, which lib.  (See below, "Occasional Build Error”)
A bunch of new dependencies are pulled in and this may not be ideal:

scalacheck-shapeless pulls in Scalacheck 1.13.  It seems like we already had Scalacheck 1.12 in the project.  So now we have both.  (Not sure what pulls in 1.12.  Maybe we could change this.)
The two new libs used for handling date times may stable… but at least one of them — scalacheck-ops — has a bug for handling ZonedDateTime.  So it may have other bugs.  (See comment in build.sbt.mustache, in the code, for some detail.)
If we need to support other date classes (https://meetup.atlassian.net/browse/MUP-16294 — suggests we need LocalDate… or no?) then these libs may not do that.  Which means we may be stuck in a place where we need to rush to add support, meaning either creating our own Arbitrary generators or fixing bugs in, or adding to, these libraries.
These new libraries create possibilities of dependency version issues.

Conclusion
Given the above, I am inclined to just not do this.  It seems questionable to introduce something complex, and not strictly necessary, to every project at Meetup, especially since it causes a build to fail on occasion.
That said, if I am overestimating the complexity this introduced, and if it's actually okay, then we'd still have a todo left: Understand why this fails on occasion (seems to be around handling of dates.)  Is it a bug in serialization itself, or in libs?  If so, which lib?  We'll need to fix that.  I think this should be a new JIRA.
(I have some other questions and thoughts but will leave out of here, for clarity.)
For reference, the Occasional Build Error
Not reproducible.  Happens occasionally.  At a glance can’t tell if this is an actual bug found in serialization, or a bug in the libs, and if so which lib.
Example 1:
...),TestMapItem(,),Apple,None,None)
serialized json for TestEntity: {"aString":"","aBoolean":false,"aDateTime":"-7567022-09-13T04:34:00.004094688Z[GMT0]","aTimestamp":"+741217-05-15T14:37:15.844898731Z","aDouble":0.0,"aFloat":0.0,"anInteger":0,"aLong":0,"anArray":[],"aMapSimple":{},"aMapOfRefs":{},"aReferenceToAnotherDefinition":{"key":"","value":""},"aStringEnum":"apple"}
Failed to deserialize: Text '-7567022-09-13T04:34:00.004094688Z[GMT0]' could not be parsed, unparsed text found at index 34
[info] ! TestEntity.two-way serialization: Falsified after 95 passed tests.
[info] > ARG_0: TestEntity(,false,-7567022-09-13T04:34:00.004094688Z[GMT0],+741217-05-15T14:37:15.844898731Z,0.0,0.0,0,0,List(),Map(),Map(),TestMapItem(,),Apple,None,None)
[info] > ARG_0_ORIGINAL: TestEntity(꽰풂潑奲갶,false,-7567022-09-13T04:34:00.004094688Z[GMT0],+741217-05-15T14:37:15.844898731Z,8.368091938004098E69,0.20794651,0,9223372036854775807,List(, ᔏꩪꕽᩮ돖炆, 蕍노٬, ),Map( -> ฻榅, ꪖ낚银 -> 弘ⶹ, ᐷ퍥Ḡ⇽ψ -> ꋛ, 㢞 -> 洛癖뽯, 㠿厑 -> 씇엕),Map( -> TestMapItem(㠩,Ỷ), ᕌ -> TestMapItem(ﻭꝃ,ษ狾), 蓮ǌ럫ࡷ脻 -> TestMapItem(㭜,½), 㔟谜㵈 -> TestMapItem(Ǣ,), ംᑜ쭗퓈ଉ퍮 -> TestMapItem(彐,쵯), ⾶ -> TestMapItem(,鲟)),TestMapItem(,뒃倂),Apple,None,Some(TestMapItem(,)))
Example 2:
Failed to deserialize: Text '-24064892-03-09T08:46:51.721532892Z[GMT0]' could not be parsed, unparsed text found at index 35
[info] ! TestEntity.two-way serialization: Falsified after 77 passed tests.
[info] > ARG_0: TestEntity(,true,0.0,0.0,0,0,+128608735-01-18T17:24:18.565155171-06:00[Etc/GMT+6],+516960-11-14T06:24:46.308Z,ReferenceEntity(,),ReferenceOfReferenceEntity(,,ReferenceEntity(,)),List(),List(),Map(),Map(),Map( -> -24064892-03-09T08:46:51.721532892Z[GMT0]),None,None,None,Orange)
[info] > ARG_0_ORIGINAL: TestEntity(,true,2.9487796263146464E32,3.8828924E7,1268694403,-6195034108067564990,+128608735-01-18T17:24:18.565155171-06:00[Etc/GMT+6],+516960-11-14T06:24:46.308Z,ReferenceEntity(靖욼,格悶),ReferenceOfReferenceEntity(⪷,,ReferenceEntity(댓,)),List(柧⇩찳),List(),Map(隊 -> 㾈㓍, 撙 -> 擯Ȑ, 苎ꃩ -> ),Map(),Map( -> -147916527-09-28T02:15:13.516768129-05:40:16[America/Indiana/Vevay], Ӌ붲 -> -24064892-03-09T08:46:51.721532892Z[GMT0]),Some(),None,None,Orange)

After discussion with @chrislewis, we are closing this.
It seems doable but not given the time already spent and our other time / resource constraints.


backtrack chams visible thu walls?

Where in the source can i make backtrack chams visible thu walls?

Does the backtrack even work as of now if the target is not visible?
or is it something to do with bestrecords part in code


Add a git CLI backend

Right now, we rely on Iceberg which relies on libgit. We should try to work directly with the CLI.

Any context on issues this solves? Curious as seems that moving from native library called through FFI to CLI called through shell might be a 'step back' and have compatibility issues if the assumption is the system git will be used (unless it's bundled in).

The main issues that we are addressing with an alternative git interface are:

The current implementation is blocking/single-threaded. We have a system process interface that is non-blocking
The current implementation has performance issues
But the main one is that it is difficult to correctly set up authentication with libgit. The cli version correctly uses the users ssh configuration on each platform.

As of today the Libgit-CLI implementation is practically usable in day to day work and can be tested.
There is a GT book pages that describes how to get started: https://book.gtoolkit.com/using-libgit-cli-as-an-alternative-to-libg-7mfe0ftw0eakhrjuf13m3hdd6

This is now practically usable.


Update version number in example/*/instance.properties

The version number in the example instance properties files (example/*/instance.properties) needs updating to version 0.11.0.

Merged into main.


Inconsistency issue

See related PyMechanical issue
For this user, get_mechanical_path(False) poins to v212

ansys.tools.path.get_mechanical_path(False)
'C:\Program Files\ANSYS Inc\v212\aisol\bin\winx64\AnsysWBU.exe'

But,
ansys.mechanical.core.find_mechanical()[0].
apparently points to a newer installation.

According to the documentation, these functions do two different things
get_mechanical_path:

Acquires Ansys Mechanical Path from a cached file or user input

find_mechanical:

Search for the Mechanical path in the standard installation location.

_clear_config_file.
But it is not exposed in the __init__.py so he will have to call it using from ansys.tools.path.path import _clear_config_file.
I think we should expose it. From the docstring:

"""Used by tests. We can consider supporting it on the library"""

The takeaway for me is that we should (1) support clear_config_file (imo the name be different, config file is an implementation detail that we shouldn't necessarily expose) and (2) fix the scenario where this might happen in PyMechanical or other applications or (3) add some minimum version argument to things like get_mechanical_path so that it ignores the config file if the cached version is too old, and maybe even adds multiple versions to the config file.

The correct way for client libraries is to use "get" first, then use "find" if its not available in "get", but never to save unless the user explicitly does so.

Actually, get_* doesn't do what it is documented, it also does a find. For dyna at least, we need a flag that says controls whether get can do a find


rp: Check intrstatus before signalling suspended

I'm not sure if this is also needed elsewhere, but currently on rp2040 the device gets stuck if the usb suspends because Bus::poll will always yield Ready(Suspended)

Thanks!


[Documentation]. Readme for this repo says to check known issues

Summary
The description of this repo's readme states:

If you have encountered a bug in with the sfdx or sf CLI, please first go to the Salesforce DX section in Known Issues to determine if there is already a documented workaround. If you don’t see your bug listed, please open an issue on this repository.

However, there is no (longer?) a SalesforceDX section, or category on the known issues page that the link takes us to.
Steps To Reproduce
Click on the [Salesforce DX] (https://success.salesforce.com/issues_index?tag=Salesforce DX) link from the repo description and try to find a DX related category.
System Information
N/a

{
  "cliVersion"<EMAIL_ADDRESS>  "architecture": "darwin-arm64",
  "nodeVersion": "node-v19.9.0",
  "osVersion": "Darwin 22.5.0",
  "shell": "zsh",
  "rootPath": "/Users/kpoorman/.volta/tools/image/packages/@salesforce/cli/lib/node_modules/@salesforce/cli",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 2.3.2 (core)",
    "@oclif/plugin-commands 2.2.18 (core)",
    "@oclif/plugin-help 5.2.13 (core)",
    "@oclif/plugin-not-found 2.3.31 (core)",
    "@oclif/plugin-plugins 3.1.6 (core)",
    "@oclif/plugin-search 0.0.20 (core)",
    "@oclif/plugin-update 3.1.26 (core)",
    "@oclif/plugin-version 1.3.7 (core)",
    "@oclif/plugin-warn-if-update-available 2.0.43 (core)",
    "@oclif/plugin-which 2.2.25 (core)",
    "@salesforce/cli 2.1.7 (core)",
    "apex 2.3.6 (core)",
    "auth 2.8.9 (core)",
    "data 2.5.1 (core)",
    "deploy-retrieve 1.16.0 (core)",
    "info 2.6.31 (core)",
    "limits 2.3.26 (core)",
    "login 1.2.20 (core)",
    "org 2.9.25 (core)",
    "schema 2.3.20 (core)",
    "settings 1.4.20 (core)",
    "sobject 0.1.37 (core)",
    "source 2.10.25 (core)",
    "telemetry 2.2.3 (core)",
    "templates 55.5.5 (core)",
    "trust 2.4.32 (core)",
    "user 2.3.24 (core)",
    "@salesforce/sfdx-scanner 3.14.0 (user)"
  ]
}

Additional information

@codefriar , thanks for pointing this out.   The readme was out of date in other ways too, so I just updated it.  Let us know if you see any other problems.  Cheers!


Experiment the haptic vibrations of the phones

Not sure if this is possible at this point.

Here is the support list for the Vibration API: https://caniuse.com/#feat=vibration