Differentiate goesToAgent/comesFromAgent and hasRecipient/hasGiver

Modify definitions and add examples
Closes #1024

Also, I suggest that all 4 properties have a domainIncludes gist:Event

I don't think of Event as the likeliest domain for goesTo/comesFrom.

This issue has not been triaged yet, and I think as a group we need to come to some understanding of what the differences are meant to be.

Also, I suggest that all 4 properties have a domainIncludes gist:Event

I don't think of Event as the likeliest domain for goesTo/comesFrom.

Its the only one I could think of right away, what are the obvious ones that come to mind for you?

Its the only one I could think of right away, what are the obvious ones that come to mind for you?

As the definitions say, I think of shipment, package, letter, etc., which we don't have classes for. I don't see any reason that we must have a domainIncludes value, so if nothing fits the bill I'd leave it off.

As the definitions say, I think of shipment, package, letter, etc., which we don't have classes for. I don't see any reason that we must have a domainIncludes value, so if nothing fits the bill I'd leave it off.

Shipment is an event; if a package or letter goes anywhere, that is an event, which is always a correct way to model a 'going'.  One need not always, model the event explicitly. But I cannot think of a single example of using goesToAgent where there is no event going on (so to speak) - can you?

Oh, I see, I hadn't been thinking of the events - I was thinking of the objects being shipped and delivered. The locution seems odd in ordinary English - "the event of shipping the package goes to Tom" as opposed to "the package goes to Tom." The distinctions you make above between those who handle goods in passing them from the "ultimate" giver to the "ultimate" recipient are clear, but it's not at all clear to me how we decide which set of predicates goes with which. One pair of agents are "intermediate" givers and recipients, the other are "ultimate" ones. I have no clue why one is "comesTo/goesFrom" and the other is "giver/recipient." Do you?

Oh, I see, I hadn't been thinking of the events - I was thinking of the objects being shipped and delivered. The locution seems odd in ordinary English - "the event of shipping the package goes to Tom" as opposed to "the package goes to Tom." The distinctions you make above between those who handle goods in passing them from the "ultimate" giver to the "ultimate" recipient are clear, but it's not at all clear to me how we decide which set of predicates goes with which. One pair of agents are the "intermediate" givers and recipients, the other are the "ultimate" ones. I have no clue why one is "comesFrom/goesTo" and the other is "giver/recipient." Do you? Do we need to rethink our wording choices?

Those are all excellent points, the locution is not good- the event does not go to the agent, the package does.  But changing the wording will only work if we are rock solid on what we are trying to say - we may not be.   Intermediate vs. ultimate may or may not be exactly what we want. There may be too many variations of this.  I wonder if anyone ever used the comesToAgent and goesToAgent properties? I wonder if we should just remove them. Maybe a gist dev group discussion?

@uscholdm I made that change - let me know what you think


Traffic reduction and tuned caching strats

b50e5d82f6f67450196271cf7f175c5edac205be Updates the post Feed component to 1) reduce an extraneous poll request on load, and 2) do a full reset after 60 minutes.
551b026d7a88f48a3bfa1531a8cb232c0a637611 Removes the isFeedPublic query. It's not needed now, but in the future we need to find another solution because this was adding a lot of low-value traffic.
f45ac60798f546df3eb25f201ea0c2c6106f66a1 Reduces how frequently we poll for updates by changing the timers.
5ecf724cf399c3fb653ef8f6eff129cb3d815d87 Guards against a double-fire of fetchNextPage which unfortunately can happen because isFetchingNextPage doesn't update immediately. It does this by just tracking the page count at the time of last trigger.
be87c370abc14c3442788ccab27883cf57dd007a Disables the feeds (and thus stops polling) when the ProfileFeed and ProfileList screens are blurred, reducing needless polling.

yolo merge


tf2.0

And @Oceania2018 , @Nucs  , Can you guys give me a little insight about https://github.com/tensorflow/tensorflow/blob/25006be096cd4f0242a3b979fb212bbd192127b3/tensorflow/python/module/module.py#L332 , here vars() keyword has been used.... but I don't know what data does it extract. just the variables or the functions too???

vars should return Dictionary<string, object>, it seems to access module.__dict__ and return its content (read more here).
C#'s equivalent would be to extract all public fields or properties depending on how you plan to do these in classes that inherit Module

@arnavdas88 I'm guessing you'll keep pushing to this PR untill you finish your work right? If so, let us know when you need us by requesting reviews.

@arnavdas88 I'm guessing you'll keep pushing to this PR untill you finish your work right? If so, let us know when you need us by requesting reviews.

Awsome...


[NT-594] Editorial Modal Header

📲 What
Continuation of #961, this adds in the header details. Please note TODOs below.
🛠 How
Added the views and styles similar to what was added in #962.
👀 See

Before 🐛
After 🦋

♿ Accessibility

[ ] Tap targets use minimum of 44x44 pts dimensions
[ ] Works with VoiceOver
[ ] Supports Dynamic Type (* does something weird to the contentInset when changing with the inspector, but if the view loads at a particular text size then it's fine from there on).

✅ Acceptance criteria
Put the following at the bottom of AppDelegate's application(_:didFinishLaunchingWithOptions:) (unless #965 has merged):
DispatchQueue.main.asyncAfter(deadline: .now() + 2) {
  let vc = EditorialProjectsViewController.instantiate()

  self.window?.rootViewController?.present(vc, animated: true)
}

[ ] Confirm that header looks correct.

⏰ TODO

[ ] This doesn't look quite right on iPad just yet, we're figuring it out.
[ ] Going to add the "These projects can use your support" cell in a separate PR (it appears just below the header).
[ ] Also in a separate PR will add a slight transform to the image as well as change the closeButton and status bar to be a darker colour when the list is scrolled up.

Lgtm! If you're keen, go ahead and merge this and we can open a separate PR to address updates for iPad.

Cool, will open a polish PR, I have a few other tweaks too 👍


randint() can't move to the cursor

Describe the bug
randint() can't move to the cursor
Steps to reproduce the behavior
1.Navigate to https://arcade.makecode.com/beta#
2.New project
3.Drag randint()  to the cursor
Expect behavior
randint() can move to the cursor
Actual behavior
randint() can't move to the cursor when the cursor is at the parameter of a function. And it will be automatically placed on the next line.

Additional context
1.OS: Windows(rs6)
2.arcade version: 1.3.15
3.Microsoft MakeCode version: 6.6.8

Doesn't repro with all functions... info.score() works fine


Suggested Change in NavigationRail For Longer Text in NavigationRailItem

#991 I faced this issue today and here is my solution...
outputs ->

![Screenshot from 2021-09-17 01-57-21](https://user

@AnEx07
Thank you for helping the development of the KiwiMD library.

But I have some small remarks: your PR does not contain an explanation from which people could understand why you made these changes.
The commits of your changes are not informative. The commit should contain a title and description of the changes.
Please note that we have a template by which you can make a description of your changes - https://github.com/kivymd/.github/blob/main/.github/pull_request_template.md

should i change those and redo pull request or what?

@AnEx07
The commits of your changes are not informative. The commit should contain a title and description of the changes.
https://docs.github.com/en/github/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message

@AnEx07 Check out the Git documentation: what the commits to the changed files should look like.

@AnEx07
The commits of your changes are not informative. The commit should contain a title and description of the changes.
https://docs.github.com/en/github/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message

@HeaTTheatR  I  have changed those commits messages can you please review those?

result of new changes ->
https://user-images.githubusercontent.com/79507388/133854745-3e573824-160a-454c-b801-2814a1d330e9.mp4
https://user-images.githubusercontent.com/79507388/133854754-5bff1a08-51ec-4f2c-85e2-d71a4d9c0e32.mp4

@AnEx07 The point is that the behavior that you demonstrate in the recent videos is not inherent in the NavigationRail component. Check out the spec for this component - https://material.io/components/navigation-rail

Oh I got it...

though my project need this 😅


update track

update wallet balance loading event as Stefano asked
add event loading to calculate how many accounts are open and how many times are open

@icerove can you please provide some context on what exactly you're wanting to track here?

@Patrick1904
add event loading to calculate how many accounts are open and how many times are open

@Patrick1904
add event loading to calculate how many accounts are open and how many times are open

what do you mean by "accounts are open", how many accounts are created by user?
@icerove  not sure why tracking this particular event specifically as it's gonna be fired like every time user goes to Wallet page I think

@vgrichina

not sure why tracking this particular event specifically as it's gonna be fired like every time user goes to Wallet page I think

yes, this is what Stefano want to track

@jimmy3dita may you clarify what do you want to track, as I still don't understand

@jimmy3dita may you clarify what do you want to track, as I still don't understand

Measure the number of unique users opening their wallet via https://wallet.near.org, to check the balance or the staking rewards, without signing any transaction or doing any on-chain activity.
This is critical to measure the Active Users (DAU and MAU).
It's unnecessary to measure more than once per user, on a daily basis (CET), and monthly basis (moving, last 30 days).
If the user x opens the wallet x.near, it will trigger +1 on the DAU, and for 24 hours we can ignore any further event of this type for this user.

@VGasparini
@Patrick1904

Is there any reason why we cannot calculate DAU/MAU over user sending any event vs one specific?

Any event is good, we just want to measure how often some user gets back to the wallet and simply look around.
Here's the catch: if I got right how MixPanel works, we may end up harvesting godzillions of useless events from the same user, while we simply need "the first one for today".

@MaximusHaximus adding you to the conversation - I want to understand if MAU and DAU metric is measurable with this work, or we need @icerove to rework this

Is there any reason why we cannot calculate DAU/MAU over user sending any event vs one specific?

Any event is good, we just want to measure how often some user gets back to the wallet and simply look around.
Here's the catch: if I got right how MixPanel works, we may end up harvesting godzillions of useless events from the same user, while we simply need "the first one for today".

I think that fetching account balance is probably the lowest-level single action we could rely on for this.  It does make sense that we don't need to report an event for every single time a users balance is fetched, as this will indeed create a ton of events in Mixpanel that we don't care about.
The simplest way to avoid spamming but still get some signal would be to put this action report behind a throttled call that can only be sent every X minutes.  I think if we were to make it only report once every 60 minutes it would still be sufficient for our purposes.
While we could try to do something fancy like only trigger it "once per day", even the concept of a "day" is problematic; where do we consider a day to start and where does it end, and do those hours make sense for a user in a different timezone than we are in?
I tend to lean towards getting a few more events than we technically need but be relatively sure we do get events when someone uses the app.  I'll rebase this on to current master and make this only report once every 60 minutes at the most, then I think we can merge this and see where we're at from the dashboards side of things :)

@stefanopepe @icerove This event would have fired only any time someone navigated to the Wallet tab of the UI, max once per hour.

It would not fire if someone navigates from the Wallet tab to the Staking tab
It would not fire if someone navigates from the Wallet tab or Staking tab to the Account tab.
It would only fire when someone opens the Account tab or switches accounts while already on the Account tab.

However, from Stefano's message in this thread, it sounds like we want our 'active' users counts to include people who are already on the Staking page using the app, or who are already on the Account page using the app, in addition to people who are on the Wallet page using the app.
As a result, I made two changes to this to facilitate this happening:

I added the reporting to the Staking and Account pages (it was already on the Wallet page)
I renamed the action string we are reporting to Mixpanel to be identical on all 3 pages for consistency -- it reports now ui is active.

I think this is ready for review + landing at this point.

@Patrick1904 :+1: good ideas -- I made those changes.  If this looks GTG for you, I think we're ready to rock.


logOut() does not end session on ID provider

I have the following configured in my AppComponent:
export class AppComponent {

    constructor(private router: Router,
        private oauthService: OAuthService) {

        // Login-Url
        this.oauthService.loginUrl = "https://login.microsoftonline.com/TENANT_ID_GUID/oauth2/authorize";

        // URL of the SPA to redirect the user to after login
        this.oauthService.redirectUri = window.location.origin + "/";

        // The SPA's id. Register SPA with this id at the auth-server
        this.oauthService.clientId = CLIENT_ID_GUID;

        // set the scope for the permissions the client should request
        this.oauthService.scope = "openid profile";

        // set to true, to receive also an id_token via OpenId Connect (OIDC) in addition to the
        // OAuth2-based access_token
        this.oauthService.oidc = true;

        //resourceAppId from manifest; required because requesting id_token AND token.  Would not be requied for just id_token...
        this.oauthService.resource = RESOURCE_ID_GUID;

        // Use setStorage to use sessionStorage or another implementation of the TS-type Storage
        // instead of localStorage
        this.oauthService.setStorage(sessionStorage);

        // To also enable single-sign-out set the url for your auth-server's logout-endpoint here
        this.oauthService.logoutUrl = "https://login.microsoftonline.com/TENANT_ID_GUID/oauth2/logout?id_token={{id_token}}";

        this.oauthService.issuer = "https://sts.windows.net/TENANT_ID_GUID/";

        // This method just tries to parse the token(s) within the url when
        // the auth-server redirects the user back to the web-app
        // It dosn't send the user the the login page
        this.oauthService.tryLogin({
            onTokenReceived: context => {
                var claims = context.idClaims;
                var currentUser = {
                    name: claims.name,
                    id: claims.unique_name,
                    roles: claims.roles
                };
                sessionStorage.setItem('currentUser', JSON.stringify(currentUser));
            }
        });
}

When I call oauthService.logOut(), it does not end the session on the ID provider server (Azure AD).  If I call oauthService.getAccessToken() it returns null and oauthService.hasValidAccessToken() returns false, but if I navigate to my ID provider login page (https://login.microsoftonline.com), my session is still active.
FWIW, I'm using v1.0.20.

I just did some additional investigating... it does not look like angular-oauth2-oidc ever actually calls the logoutUrl I set to end the session.  If I manually hit that URL I set this.oauthService.logoutUrl to be, it ends the session, but this library never calls that.  Any idea why?

Try removing the id_token from your logoutUrl:
this.oauthService.logoutUrl = "https://login.microsoftonline.com/TENANT_ID_GUID/oauth2/logout";

I have the same problem. How did you fix this?

@songokudbz I used the following code to log out:
this.oauthService.logoutUrl = 'https://login.microsoftonline.com/TENANT_ID_GUID/oauth2/logout?post_logout_redirect_uri=HTTPS://MYAPP.COM';

logOut() {
    this.oauthService.logOut();
    window.location.href = this.oauthService.logoutUrl;
}

It should be called. Try to remove id_token={{id_token}} (which is legacy)

@manfredsteyer I tried removing it, but to no avail.  I included it in the original post only because it was still in your documentation.  I agree with you that it "should" be called, but, nonetheless, it's not.  Not sure why you're closing this ticket...

Sorry for closing.
I did not manage to reproduce this. Perhaps you can try it with the new version 2 which just landet some minutes ago.
The sample app, committed here, can also do it, so perhaps it is a good idea to find out in which way it's usage of the lib differs from the usage in your application.
If you can crate a minimal demo-app that reproduces this issue, I'm happy to look over it.

Logout works for me. Here's the example app I'm using: https://developer.okta.com/blog/2017/04/17/angular-authentication-with-oidc

Discussion came to an end --> closing this. We can reopen it on demand.

@im1dermike Have you achieved that....?

This is happening to me too, so if i refresh the page, call logout method the localStorage is cleaned but no redirection to endsession endpoint.

Potentially related to https://github.com/damienbod/angular-auth-oidc-client/issues/1835


Entesb 13070 provide initial completion for ddl file

review and merge https://github.com/teiid/teiid-language-server/pull/1 before reviewing this PR

@apupier above looks good. Since I do not much details about LSP it may be better someone else provides you with better feedback?


Versioning of status endpoint format

2. How do we deal with versioning?

While I think it would probably be best to introduce proper API versioning to jskos-server (and therefore to wikidata-jskos as well), it would probably be easier to just add the old config keys to the expanded status response, inferred from the new config format. Of course that would bloat the status response,  but if we introduced some way of versioning for the API, the "default" version would still need to be the current one because we can't rewrite old clients, so consuming the API from the browser for example would still return the old responses.
Also, we couldn't really do versioning in the URI because that would break all our mapping and annotation URIs, and using a header would not be accessible via a browser request. I don't think there is a good solution, only different compromises.
Originally posted by @stefandesu in https://github.com/gbv/jskos-server/issues/69#issuecomment-521542609

Fur current changes (#69):

[ ] keep old sets of fields (e.g. auth.identityProviders) in addition to the new fields
[ ] change clients
[ ] remove old fields afterwards

For future versioning:

[ ] add version field with a semantic version number that refers to the API format (we can start with 1.0.0 after this refactoring)
[ ] create a JSON schema for the status format to better detect changes. The version number would basically refer to the schema
[ ] add check function to clients, so for instance Cocoda can detect when connecting to a jskos-server instance with incompatible version number

remove old fields afterwards

This will still break older Cocoda versions in our archive, as I've noted in the original comment in #69. I mean there are other older versions that don't work anymore, but I'm not sure what the point of that archive is if older version aren't working anymore.

add check function to clients, so for instance Cocoda can detect when connecting to a jskos-server instance with incompatible version number

What will Cocoda do with that information, not use the API anymore? That would only be a minor improvement over just having it break, to be honest.
In general: You are suggesting that we add the version as a field to the status response, right? But without allowing access to older API versions? In that case, I'd rather return the API version in the response header like described here.

Some more interesting links about API versioning that I've read earlier:

https://www.mnot.net/blog/2012/07/11/header_versioning
rest - Best practices for API versioning? - Stack Overflow
GitHub API v3 | GitHub Developer Guide
REST API Versioning Guide – REST API Tutorial

There are many different ways and opinions about this, and there's no right or wrong way I think (although some ways are objectively better than others I guess).

Implemented via 678d0a34fdc417b7bd144e9bc878961f4ca8dec4 (the issue tags got eaten because I had them on a separate line which was of course interpreted as a comment 🤦♂).

create a JSON schema for the status format to better detect changes. The version number would basically refer to the schema

Where should we put the JSON schema? And where should it be used? We could definitely use it in tests, so maybe it would make sense to have it in this repository as well.


Create Instance of SAP Event Mesh | No longer available in BTP Trial

Tutorials: https://developers.sap.com/tutorials/cp-enterprisemessaging-instance-create.html
Hi, I was going through this tutorial and found myself running into a wall while creating the Event Mesh Instance in my Trial account. Sadly I received the following message:
Service broker error: Service broker enterprise-messaging-service-broker failed with: Service broker parameters are invalid: The plan dev, lite and application must not be used anymore. The trial offering for the Event Mesh Service is discontinued. For more details, please read the blog: https://blogs.sap.com/2023/02/01/sap-event-mesh-trial-to-be-retired/.
Maybe you can add this as a warning to the beginning of the tutorial?
Is there a workaround to try this out?
Hope to hear from you.
Kind regards,
Julian Kuipers

Pradeep, as the original author, can you please respond to this issue?

@pradeeppanda-sap please reply to this feedback ASAP.

Hi Julian. Event Mesh was -- indeed -- retired from Trial.  The Tutorial has been updated and marked as "License Required".  Sorry we did not catch that sooner for you.  Thanks for reporting this!

Warning added with a pointer to the definition of SAP BTP commercial accounts.


Added ctrl+z and ctrl+y

May I ask, out of curiosity, why you don't accept my two PRs? Is there something wrong with it?

May I ask, out of curiosity, why you don't accept my two PRs? Is there something wrong with it?

Hi @F1nnM, apologies, I'm taking a hiatus from GitHub right now.

Hi @F1nnM, apologies, I'm taking a hiatus from GitHub right now.

That's alright, no worries, I was just curious :)


Urdu localization added

Urdu language is spoken in Pakistan and India.

Thanks! Will test and merge it in the next 24 hours. I'll add it to Siren as well.

The tests failed: https://dashboard.buddybuild.com/apps/58c4d37980c4290100790f8c/build/593c07e2cd3eb300016312fe
Looks like you forgot to add the localization the the Harpy.bundle file.

Closing this PR since there's been no response.

HI @ArtSabintsev , sorry I have added the file now. Check my new PR please.


ANSI_COLOR_NAMES naming

It seems to me that the naming is wrong. Mainly, why are "high intensity" colors named as "dark"?
Current:
ANSI_COLOR_NAMES = [
    'ansiblack', 'ansiwhite', 'ansidefault',

    # Low intensity.
    'ansired', 'ansigreen', 'ansiyellow', 'ansiblue', 'ansifuchsia', 'ansiturquoise', 'ansilightgray',

    # High intensity. (Not supported everywhere.)
    'ansidarkgray', 'ansidarkred', 'ansidarkgreen', 'ansibrown', 'ansidarkblue',
    'ansipurple', 'ansiteal',
]

Why not using well-known (https://en.wikipedia.org/wiki/ANSI_escape_code#Colors) naming like (red, brightred, etc.)?

Is ansi prefix necessary?

There are 0-15 (that is 16 ANSI colors), and then default, but list above has 18 elements.

I agree. There was some confusion around this.
Right now it's consistent with the Pygments code, but I'm in favour of fixing it in 2.0 (maybe with some compatibility towards Pygments styles.) See: https://bitbucket.org/birkenfeld/pygments-main/src/7941677dc77d4f2bf0bbd6140ade85a9454b8b80/pygments/style.py?at=default&fileviewer=file-view-default
The ANSI prefix however is necessary, because prompt_toolkit also supports all these named colors: https://github.com/jonathanslenders/python-prompt-toolkit/blob/2.0/prompt_toolkit/styles/named_colors.py The ANSI colors map to the ANSI colors of the terminal, while the named colors use whatever color from the 256 (or full) colors is closest.
cc: @Carreau

Fixed here: https://github.com/jonathanslenders/python-prompt-toolkit/commit/6fbe54116b90eb2559b00c427d89b593cb836d41


bg_color, bg_opacity don't work

They stopped working for me in latest Beta.
Workaround is to put style to #root with background_color: rgba(r,g,b,o) !important;

Hi and thanks for your feedback!
This issue is now fixed in the new 1.6.0-beta.2!
https://github.com/Clooos/Bubble-Card/releases/tag/v1.6.0-beta.2


Possibility to get connected batteries information from main battery?

Hi!
First thank you for what you have done, it's a really useful piece of software.
At the moment i have four batteries and they are connected to one Lilygo RS485 ESP32 device. If i connect to by bms via rs-232 witha Pbms software i can see all four battery packs from the main battery. Is there a possibility to get connected batteries data with this esphome-pace-bms as well instead of connecting to each battery rs485 port? With this i could lose quite a lot cabling.
To my understanding it's somehow solved with this integration: https://github.com/Tertiush/bmspace

I'm not super deep into the details of the Pace BMS. This is my understanding:
If you talk to the BMS using Pbms via RS232 a Seplos ASCII protocol is used. A frame looks like this:
https://github.com/Tertiush/bmspace/blob/main/pace-bms-dev/bms.py#L460
If you talk to the BMS using this implementation via RS485 the protocol is called Modbus. There are some users around which wasn't successful to setup a RS485/Modbus connection. They are using this project (because of the different protocol):
https://github.com/syssi/esphome-seplos-bms

Thanks for a quick reply.
So do I understand correctly that this project is modbus, meaning that i have to connect all batteries to use it and second one is Seplos protocol that uses rs232 connection and i get probably all packs data from the main battery?

Option 1: Use RS485/Modbus: Chain all RS485 ports next to the CAN bus and attach the Lilygo RS485 to the bus.
Option 2: Use RS232: Attach a ESP32 + RS232 converter to the RS232 port of the master. It looks like your Lilygo CAN485 doesn't have a RS232 converter on board.

Option 1: Use RS485/Modbus: Chain all RS485 ports next to the CAN bus and attach the Lilygo RS485 to the bus. Option 2: Use RS232: Attach a ESP32 + RS232 converter to the RS232 port of the master. It looks like your Lilygo CAN485 doesn't have a RS232 converter on board.

I currently use the option 1 and it actually works great.
I'm using this approach to optimize the amount of esp32 code: https://github.com/syssi/esphome-pace-bms/pull/59
I just have one issue, that battery 2 voltage is some random number. on discharge it's showing current value as a voltage and other times some random number. If i connect via rs232 and Pbms Tools the value is correct. So for some reason over modbus it has aome bug. Also it seems that time to time the queue is overloaded as update_interval is 10 seconds for all the sensors for all 4 packs. I havent figured out yet how to differentiate the updates so that config entities will be updated less frequently and voltages, amps, balancing status will be updated more frequently.

I totally forgot this project as possible solution too: https://github.com/nkinnan/esphome-pace-bms
It's a similar implementation to my esphome-seplos-bms project but it's tailored for the PACE BMS (RS232, Seplos like) protocol.

Your dashboard and setup looks pretty nice. Why do you want to change/touch your setup? :-)

Your dashboard and setup looks pretty nice. Why do you want to change/touch your setup? :-)

Thanks! Only reason is the issue with battery 2 wrong voltage as I said earlier.
It's weird that everything else is ok, just one battery pack voltage is showing wrong value. When it's charging it's showing pack current as voltage and other times just a random number. I think that this is some modbus error and thought I try the rs232 and connect only first battery as I can see the correct value with PBms Tools.
But to be honest I'm not sure if it's worth changing the setup


Mobile nav issues, hamburger and close icons half covered,

the hamburder and close icons are too far to the right, so they are half covered by the container for the nav.

fixed


Support for biblatex ressources is probably broken

I have a *.bib file, where the field with  the year is date and not year, which results in the date not being displayed.
I read that the newer field date should get used since years.

I use biblatex on my CV and I use date (or eventdate) on all my bibliography entries. It works as expected. Are you, maybe, using an outdated package?

I'm using Arch Linux
Is there a newer version than https://archlinux.org/groups/x86_64/texlive-most/ ?

It should work. It might be the style you are using. I use APA on my CV. Which one do you use?
Here is a MWE:
\documentclass{moderncv}
\moderncvstyle{casual}
\moderncvcolor{blue}

\begin{filecontents}{\jobname.bib}
@article{article1,
    author = {Firstname Lastname},
    date = {2020-10-10},
    title = {Some title},
    publisher = {Some publisher},
    volume = {1},
    pages = {1-10},
    url = {http://example1.com},
}
\end{filecontents}

\usepackage[style=apa]{biblatex}
\addbibresource{\jobname.bib}

\firstname{Firstname}
\lastname{Lastname}

\begin{document}
\makecvtitle
\nocite{article1}
\printbibliography
\end{document}

I tried it on Overleaf, and it works on any version of TeX Live since 2017.

Thank you for your help
I use moderncv as well
https://github.com/MartinX3-EducationOrganization/latex-template-job-application

It does not look like you are using biblatex at all.

What I'm using then?
https://github.com/MartinX3-EducationOrganization/latex-template-job-application/blob/master/datenbanken/Veroeffentlichungen.bib

The lines \bibliography{datenbanken/Veroeffentlichungen} (from ./abschnitte/Lebenslauf.tex) and \bibliographystyle{plain} (from ./aussehen/CV.sty) suggest that you are using BibTeX rather than BibLaTeX.
That's the reason for your problem. You should use date with BibLaTeX, not BibTeX.
I think this bug can be closed.


PostgreSQL specific files are generated under the wrong directory

In the postgresql example, the PostgreSQL specific files should be under dynamic directory but they're not.
https://github.com/ldbc/ldbc_snb_implementations/blob/master/postgres/load-scripts/load.sh#L17-L26
$PG_DATA_DIR/post_0_0-postgres.csv

Where PG_DATA_DIR is pointing to the social_network directory
social_network chaker$ ls dynamic/post_0_0.csv
dynamic/post_0_0.csv

Should I open a PR to fix both files?

This diverged from the datagen when we refactored/changes it to handle static and dynamic parts of the graph separately.

Should I open a PR to fix both files?

Please do. Thanks!


v50 Spawning in the void

Running latest update of all mods.
Disabling LLL allows the player to load in fine. Having it enabled causes spawning in the "void" (green foggy screen with 'grab (E)')
Running LLL on its own in a fresh profile and player loads fine. I can only assume it it conflicting with a mod but cannot work out which.
LogOutput.log

I also had this issue, it seems to only happen with existing saves before the update, however making a new save allows me to load into the game just fine

Just tried deleting a save and then making a new one and still get the issue.

Did you have a modpack for moons, like Tolian ? Modpacks made it buggy for me, so i manually downloaded each moons.

I have an issue similar to this, but instead of me loading into the void it's my friends that load into the void when they join in.

I have an issue similar to this, but instead of me loading into the void it's my friends that load into the void when they join in.

My friend are still having the same issue with the latest version.

I could also work around this by creating a new save file. You might also check to see if you have one or more versions of LethalExpansion (LE) installed, as certain moon packs include it as a dependency. The latest LE-Preview and separate LE-Core fork could cause conflicts with the now deprecated original LE.

I could also work around this by creating a new save file. You might also check to see if you have one or more versions of LethalExpansion (LE) installed, as certain moon packs include it as a dependency. The latest LE-Preview and separate LE-Core fork could cause conflicts with the now deprecated original LE.

I have tried turning off the LethalExpansionCore + ImmseriveScraps, my friend and I have the same settings and he couldn't join, we will have to play with the levelloader disable for now.

Resolved as Lethal Expansion is now deprecated. Was also likely due to using older, now invalid save files. Apologies for the inconvience.


vBump dacpac and sql database projects

Pull Request Test Coverage Report for Build 661932929

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.001%) to 43.346%

Files with Coverage Reduction
New Missed Lines
%

extensions/import/src/wizard/pages/fileConfigPage.ts
3
72.99%

Totals

Change from base Build 661888217:
-0.001%

Covered Lines:
25411

Relevant Lines:
53484

💛  - Coveralls


Autoacaling the controller statefulset

Hello,
After deploying the csi driver, I see there is statefulset created as controller. How could I apply autoscaling to statefulset? Is the HPA with checking cpu and memory going to work? Or does it require additional work?
Thanks

Hi @hyphen1370 , sorry for late reply. HPA with checking cpu and memory is ok and no more work is needed. Thanks.


bosh create - package spec github path issues.

I'm trying to deploy Diego release in my local, as part of that i'm running bosh create , but some of the package spec file github path has been migrated and create release is failing.
bosh create release --force && quit
Syncing blobs...
Building DEV release
Release artifact cache: /Users/sumanaluru/.bosh/cache
Building license
Building license...
Using final version '861d82c0d9745784acfcd026ccf44e942579824a'
Building packages
Building acceptance-tests...
Using final version '2f54ad04d4f720d8e42ad802ca431677635902c8'
Downloading from blobstore (id=e2d9e686-0234-4c24-b0e9-ddf0278ab164)...
Building auctioneer...
Package 'auctioneer' has a glob that resolves to an empty file list: github.com/cloudfoundry-incubator/auctioneer/cmd/auctioneer/*.go

Hi, @saluru,
Thanks for the report. Are you trying to deploy from the tip of the develop branch right now? Looks like the team might have forgotten to push some of the submodules on this commit. Creating a release works for me on the current master commit, though (version 0.1407.0).
Thanks again,
Eric, CF Runtime Diego PM

I have a different hypothesis @saluru, what happens if you run git submodule update --init src/github.com/cloudfoundry-incubator/auctioneer from the root of the diego-release repo?  If you then try to create the release, do you get a bit further (you might see a different glob complaining about resolving to an empty list).

Hi @Eric,
I will try with master , but i see you have same dead links in  spec file (version 0.1407.0) which are giving 404 .

name: auctioneer
dependencies:

golang_1.4

files:

github.com/cloudfoundry-incubator/auctioneer/cmd/auctioneer/*.go # gosub

Hi @Amit-PivotalLabs
unknown90840df169fe:diego-release sumanaluru$ git submodule update --init src/github.com/cloudfoundry-incubator/auctioneer
fatal: reference is not a tree: 145bc488a656a5e15d233b7c0340551dc014b4af
Unable to checkout '145bc488a656a5e15d233b7c0340551dc014b4af' in submodule path 'src/github.com/cloudfoundry-incubator/auctioneer'

Hi @Eric,
I tried using master, still got the same error . I'm following the instructions provided in diego-release.
If you observe its not just one package for all.
When i access GIT url in the browser its giving 404, but when i click from diego-release repo its going to
Problem URL in spec file: https://github.com/cloudfoundry-incubator/diego-acceptance-tests/assets/
Good One: https://github.com/cloudfoundry-incubator/diego-acceptance-tests/tree/master/assets/
Building packages
Building acceptance-tests...
Package 'acceptance-tests' has a glob that resolves to an empty file list: github.com/cloudfoundry-incubator/diego-acceptance-tests/assets/**/*

@saluru, the Unable to checkout '145bc488a656a5e15d233b7c0340551dc014b4af' in submodule path 'src/github.com/cloudfoundry-incubator/auctioneer' error message jives with what @ematpl suggested, that some of the submodules had not been pushed up, by accident.  If you don't have any work in progress in the diego-release repo, you can do the following:
git fetch origin
git checkout master
git reset --hard origin/master
./scripts/update

and then create release.  The ./scripts/update will hydrate all your submodules which will be empty until you clone the diego-release repo and update/init the submodules.  The ./scripts/update does that for you, and takes care of doing it recursively because some submodules might have their own submodules.
This should work on master because master has had a release built from it, from scratch.  It is currently failing on develop because a submodule was accidentally not pushed when diego-release was bumped to change a submodule pointer.

Thank You @Amit-PivotalLabs  & @ematpl that fixed the issue.


Search by joining properties.

What i want to do;
query.Search(x => string.Join(" ", x.Property1, x.Property2)).Containing("searchTerm");
This method does not work well. is there another way?
thanks.

Have you tried this?
[...]
query.Select(x => new { JoinedItem = x.Property1 + " " + x.Property2 })
.Search(y => y.JoinedItem).Containing("searchTerm")
[...]

Not sure EF knows about string.Join(), but it's an easy concatenation. There are other ways to do it too, the worst being to actually get the results into memory and using string.Join(). Another way is to have a computed column on that database table, that holds exactly the value you want => Property1 + " " + Property2. Then, you use Search() on this column.


Add definitions for factory builder terms

Towards #151.
This PR adds glossary definitions for factory builder terms.
WIP.

Excellent start, thank you.

Why is this draft? Will you be adding more terms? If you want, you can undraft it, and I am sure it will be reviewed/merged super quick.

Yeah I'm fine to either merge this aggresively or wait a bit longer for you to finish filling out this batch of terms. Definitely don't want this hanging around for more than a couple days though :)

I wanted to finish the rest of the factory terms before merging, but I had to leave :)
I'll finish this today or tomorrow.
Mostly opened this as draft so that we don't accidentally duplicate work.

I can't think of good definitions for "Overlay", "Resource" and "Logistic network" right now, if you have some feel free to add them :)
Otherwise this is ready for review now.


Segmentation fault on WSL 2

Hi there!
I'm currently learning egui to make a comic reader application, and have a bit of trouble making it work.
I'm using WSL 2 on Windows 11. On my first PC, everything works fine, but on my second I get a segmentation fault. Here is the minimal reproduction example I've gotten to:
use eframe::{App, NativeOptions};

fn main() -> eframe::Result<()> {
    eframe::run_native(
        "reader",
        NativeOptions::default(),
        Box::new(|_| Box::new(MyApp)),
    )
}

struct MyApp;

impl App for MyApp {
    fn update(&mut self, ctx: &egui::Context, _: &mut eframe::Frame) {
        egui::CentralPanel::default().show(ctx, |ui| {});
    }
}

The update function runs and the inner closure too, but I get a segmentation fault afterwards. I don't get to see any window displayed before the crash.
I'm currently using the latest version of egui and eframe, here is my Cargo.toml:
[package]
name = "reader"
version = "0.1.0"
edition = "2021"

[dependencies]
eframe = { version = "0.22.0", default-features = false, features = ["glow"] }
egui = "0.22.0"

Any idea of what's causing this?
EDIT: I'm using Ubuntu 23.04 (lunar), stock kernel, WSL 2 v<IP_ADDRESS>, with WSLg v1.0.51, Windows v10.0.22621.1992

Have you looked at the stack trace for the seg fault?
Have you tried the wgpu backend?

I'm also using WSL 2 on Windows 11.　I get a segmentation fault when closing the app.
And I can't find a page that I can refer to when using it with Wgpu backend.
cargo.toml
[dependencies]
egui = "0.26.2"
eframe = { version = "0.26.2", default-features = false, features = [
    "accesskit",     # Make egui comptaible with screen readers. NOTE: adds a lot of dependencies.
    "default_fonts", # Embed the default egui fonts.
    "glow",          # Use the glow rendering backend. Alternative: "wgpu".
    "persistence",   # Enable restoring app state when restarting the app.
] }

env_logger =  { version = "0.11.3", default-features = false, features = [
    "auto-color",
    "humantime",
] }

Debug
7FFFEA66DBB6: 43 8B 0C AE                movl   (%r14,%r13,4), %ecx


Feature-request: Where-clause in a field's edit-view should also be able to use join-fields

Is your feature request related to a problem? Please describe.
I need the status-field of the linked order-record in my where-clause but that's not possible in this where-clause. . I can show the joined-field-value on my edit-view but I can't use it in the where-clause of another field on that same edit-view. Saltcorn says that the where clause is to complicated
But what is the use of "$order     Key to Orders" if you can't use field-values of that linked order-record?

Describe the solution you'd like
Being able to use the field-value of a linked records in the where-clause of a Field/edit-view.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Any news about this feature (or perhaps bug)?
I can place and see the value of a join-field on my edit-view perfectly, but I can not use the value of that same join-field in the Where-clause of another select-field on that same edit-view.
Frustrating. Saltcorn gives me the error-message  that the where-clause is to complicated because of the join-field.


Update sample-test-analytics-pass-rate-trend-test.md

Corrected Power BI query syntax

@Anubhav-gangwal : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"


where is the libthrift put in my local disk?

bcs i can't connect to "http://maven.twttr.com/" for download the "libthrift-0.5.0.jar" buy build. but i can get the jar from other way.

so am i

Unfortunately, the only way forward I can recommend here is to retry until you are able to connect to twitter maven repo.

@puneetkhanduri we have now published a new copy of libthrift to maven central under the organization com.twitter.  http://search.maven.org/#artifactdetails|com.twitter|libthrift|0.5.0-7|jar

Thanks @mosesn.
@neven7 @plscomeon It seems you should be unblocked now.


Relaxed Dependencies

Issues
With ch_util supporting a wide myriad of utilities under the hood, downstream packages are currently required to build and install complicated dependencies by default even though they might not be required. An example of this could be mpi4py which is seldom used in developer environment. This proposal recommends  to split the dependencies of ch_util by purpose under extras_require in order to considerably relax base requirements.
Additionally, dependency resolution systems enabled through PEP 517 such as flit, poetry and pipx try and evaluate requirements for ch_util,it nominally includes packages under extra_installs. This process errors out, since chimedb_config package is closed sourced. As a result, currently its not possible to use ch_util with these modern build systems.
Resolutions for:
Private Extra Installs

Since chimedb_config will never be made open source, we can either remove it from the setup.py and raise an import error, if a function which requires it is called.
We can give selective access to the CHIME/FRB personnel as a workaround.

Dependency Isolation
Example Scenario
If a developer wants access to the ch_util.tools.Antenna object, they are required to install bitshuffle, which requires a hard linked installation of hdf5. This additional step adds ~3-5 minutes of compile time.
Possible Split

Extra
Dependencies

chime_io
[bitshuffle, h5py]

chime_db
[chimedb @ git+https://github.com/chime-experiment/chimedb.git, chimedb.data_index @ git+https://github.com/chime-experiment/chimedb_di.git, chimedb.dataflag @ git+https://github.com/chime-experiment/chimedb_dataflag.git]

chime_mpi
[mpi4py]

all
[*]

Additionally, I am happy to work on these issues, if the project team is interested in implementing them.

This proposal recommends to split the dependencies of ch_util by purpose under extras_require in order to considerably relax base requirements.

I do want to bring up, when considering this issue, the last time I checked extras_require does not play well with the new pip resolver.
The previous occurrence of a related conversation: https://github.com/chime-experiment/ch_util/pull/8

I was not aware of the discussion in #8 , but if relaxing the dependencies is not ameneable, would it be okay to fork and change ch_utils under the chimefrb project?

@shinybrar okay great.
I think we can try and thin down the dependencies a bit too. Looking at the requirements.txt I think we can remove a few things:

mpi4py can be removed. It's not an actual dependency of ch_util.
matplotlib doesn't need to be a dependency (although you probably have it installed anyway so it's moot)
A bunch of things (numpy, scipy, h5py, skyfield) are already dependencies of caput, so you'll be forced to install those anyway, as I think you also need caput for things.
Hidden in the chimedb stuff is mysqlclient which I think can be a pain to install. There is a pure Python MySQL client we could switch to I think provided we tweak the peewee interfacing and so that would become easier.
The other things in there like networkx and peewee are generally very easy to install.

I want to make clear that this is not my work but a PR from someone from ESRF, Grenoble (kiyo-masui/bitshuffle#81).

@nritsche can I ask you to take a look at that PR and test it and see if it does what we want (i.e. allow using bitshuffle without install h5py from source)?

@shinybrar this is making progress now. We're just about to get the code merged into bitshuffle (https://github.com/kiyo-masui/bitshuffle/pull/81) which means that we won't need to build h5py from source to use bitshuffle. Next stop is to build a binary wheel of bitshuffle, so installing that part of the chain should be more or less instantaneous.


App for Android 11

I had done everything and then was shocked because the app didn't work although Bluetooth was successfully connected. No data is sent to the watch. What can I do now😢?  Is there any apps which can be used instead?

I had done everything and then was shocked because the app didn't work although Bluetooth was successfully connected. No data is sent to the watch. What can I do now😢? Is there any apps which can be used instead?

can you provide me with the solution please if you find one :(


Updated glassMorf.json

Issue: #20
Screenshot:

Changes proposed in this pull request and/or Screenshots of changes:

Added details in glassMorf.json
In the loading screen, the contents of the site were being shown under the loading screen. Fixed that.

@Apoorv012 kindly check out https://ui.glass/ and make it better if possible.


Enhance compatibility for SqlServer 2008

The code contains several statements like "GROUP BY 1". This is not supported in MS SQL, but can easily rewritten to "GROUP BY ascendent_id", which works for all SQL implementations.

We will need a benchmark with Postgresql and MYSQL. MSSql is not supported officially.

Do you have a preferred one?
I compared spec runs on my local laptop with this gist: https://gist.github.com/MartinKoerner/20f57509a2b3cebc5d69,
but it deviated around 4sec even without any change and me not touching the laptop, so it is not helpful for this small level problem.

Fwiw, I've never seen a performance impact from ordinal versus named
group_by clauses.
I'd be more concerned with correctness here than speed, given the fairly
intricate SQL generation from this gem. I think tests are fairly
comprehensive, but I'm sure there are tons of consumers that have exercised
the code in ways that don't have test coverage.

This is innocuous to merge.


Limit the number of active promotions and demotions

Limit the number of active promotions and demotions performed by the p2p governor.

That is, limit the number of concurrent promotions/demotions.

That is, limit the number of concurrent promotions/demotions.

Yes, given that the governor has targets for "active peers" I shouldn't have used the world "active".


Allow to prefix redis keys

implements https://github.com/cschleiden/go-workflows/issues/227

🤔 I don't like that we need to pass keyPrefix through all those functions. It's probably cleaner to have a struct for the keys and to store the prefix there. Create that struct once when creating the backend instance, and then make the current key functions methods using that stored keyprefix.


Edit: BT Sport 8 [UK]

Channel ID (required)
BTSport8.uk
Channel Name
BT Sport 8
Alternative Names
No response
Network
No response
Owners
No response
Country
UK
Subdivision
No response
City
No response
Broadcast Area
No response
Languages
No response
Categories
No response
NSFW
FALSE
Launched
No response
Closed
No response
Replaced By
No response
Website
https://www.tntsports.co.uk/
Logo
https://github.com/tv-logo/tv-logos/blob/main/countries/united-kingdom/tnt-sports-8-uk.png?raw=true
Notes
"BT Sport 8" has been rebranded and is now called "TNT Sports 8"

Please update your request:

the size of the logo should not exceed 512x512px

https://github.com/iptv-org/database/blob/master/CONTRIBUTING.md#channels

Changes made


Working on our lint/vet'ing

Tested on my cluster, no regression found. Feel free to merge after typo fix.


Adding PerspectiveProjection or OrthographicProjection components doesn't get used by Camera3d

Bevy version
anytime after required components got merged, 0.15.
What you did
Added a OrthographicProjection component and a Camera3d bundle to an entity
What went wrong
It added a default Projection component, and rendered as perspective, disregarding the OrthographicProjection component

So, the easiest fix is to make both specialized projection components not be components anymore. But that's a copout, how will custom projections work?

If there is already a projection component on the entity, I would expect that it satisfies the requirement and the default constructor isn't used to add another one.

This looks like a breaking change that was not made breaking enough in the 0.15
Camera3d has a required Projection component, which is an enum of OrthographicProjection and PerspectiveProjection. The specific projection types were kept as component.
Camera2d still requires OrthographicProjection as a component.
I think we should remove the Component derive from OrthographicProjection and PerspectiveProjection, and add a wrapper type on OrthographicProjection for `Camera2d. This is a breaking change so it can't be done in a patch

But that's a copout, how will custom projections work?

That's a current limitation of required components, it's not possible to say "require a component that implements a trait, and use this specific one as a default value if none are provided"
To me, this should be regarded as "user error made easy by a bad api" and removed from the 0.15.1 milestone, the complete breaking change should be done for the 0.16, and a separate issue could be open to improve required components

moved to 0.15.2 to not block a 0.15.1 until we have a decision. my point of view is to remove it completely from a patch

Agreed on 0.16.

Played with this for a bit, and it seems like removing OrthographicProjection as a required component and replacing it with Projection(|| Projection::Orthographic(OrthographicProjection::default_2d())), works just fine.
I don't see an immediate need for making a special wrapper type for the ortho component if we can just continue to use Projection. I also don't see why we shouldn't just KISS and modify Projection to be
pub enum Projection {
    Orthographic {
        near: f32,
        far: f32,
        scale: f32,
        // ...
    },
    Perspective {
        near: f32,
        far: f32,
        fov: f32,
        // ...
    },
    // Can extend the set with other common projections like oblique in the future, and migration is self-documenting.
    Custom(Box<dyn CameraProjection>)
}

with some ergonomic public methods. This would also simplify custom camera projections - there is no need for a generic CameraProjectionPlugin<T>, and no way for custom projections to conflict with the builtins or each other, it is completely unambiguous by looking at the value of Projection.
Alternatively, if we wanted to be, IMO, overly-general, we could do something like:
struct Projection(Box<dyn CameraProjection>);

Not a huge fan of this, because it makes life harder for 99.9% of use cases for no good reason (e.g. I just want to tweak the fov), so I'd prefer the first solution.

I really like Aevyrie's first solution, and I think we should move forward with that design for 0.16.


modify tec page

modified tec page,ajusted some text format,aligned left and right to center and so on

added EWG page,modified race2023 page,add race2023 child menu


Broken Link presubmit test

A broken link check is described in
https://github.com/kubeflow/website/issues/62#issuecomment-401168561
Can we run that as a presubmit test?

/assign

I will add the following to the `kubeflow/website section of the presubmits when https://github.com/kubernetes/test-infra/issues/14343 is resolved:
  - name: kubeflow-website-link-check
    cluster: kubeflow
    always_run: true         # Run for every PR, or only when requested.
    labels:
      preset-service-account: "true"
    spec:
      containers:
      - image: registry.hub.docker.com/ktbartholomew/link-checker:latest
        imagePullPolicy: Always
    annotations:
      testgrid-dashboards: sig-big-data
      description: Presubmits for kubeflow/website.
      testgrid-num-columns-recent: '30'

Although I'm not sure if it's okay if the image is not stored in gcr.io?

/area engprod
/priority p1
/kind bug

@jlewi are you okay with the plan in my previous comment?


[Discussion] Include dask-expr dependency for Dask Dataframe?

The 2024.2.0 release of dask has deprecated the "legacy" dask.dataframe API in favor of dask-expr. I am already working on a PR to update dask-cudf accordingly (https://github.com/rapidsai/cudf/pull/14805). However, there may be a strange transition period until the dask-expr package is made an explicit dependency of dask (or when the dask-expr code is simply copied directly into dask/dask).
Until the dask-expr dependency is handled by dask/dask directly, we may want to include it in rapids-dask-dependency. Does it seem reasonable to do this once 20.02 is released?

As discussed in offline discussion, the current plan is to pin to dask/distributed 2024.1.1 for the remainder of 24.04. Since we will be adding optional (opt-in) dask-expr support for 24.04, I suggest that we add dask-expr 0.4.0 as a new dependency (should be light weight).

If we include dask-expr but pin to dask 2024.1.1, I assume the result for RAPIDS is a no-op? i.e. it requires dask>2024.1.1 to actually start importing and using dask-expr, so that'll just be an unused package installed onto the system unless someone opts in?

If we include dask-expr but pin to dask 2024.1.1, I assume the result for RAPIDS is a no-op? i.e. it requires dask>2024.1.1 to actually start importing and using dask-expr, so that'll just be an unused package installed onto the system unless someone opts in?

No, dask-expr has been an optional API engine for dask.dataframe since December-ish. https://github.com/rapidsai/cudf/pull/14805 will be needed to actually take advantage of the option, but that PR should be merged soon.

I think we're on the same page but I misstated a few things. What I means was that dask-expr will be unused by default and will require opting in until we change dask-cudf's default behavior. If we bumped to dask>2024.1.1 before we updated rapids to support the new expression-based APIs in dask by default, we would start seeing a boatload of warnings, so we have no plan to change that pinning until we also change the default. In practice, that means that when RAPIDS starts supporting dask>2024.1.1 is also when RAPIDS users will implicitly start using dask-expr. In the interim, users could choose to opt in to dask-expr usage by setting the appropriate dask configuration, but that may break e.g. dask-cudf until rapidsai/cudf#14805 is merged. Is that right?

Yes, I think you have everything generally correct. Once https://github.com/rapidsai/cudf/pull/14805 is merged, we will be using the dask-expr dependency for tests, but the user would need to opt in themselves to actually use it in practice.

Closing since @rjzamora added dask-expr in #29. Please reopen if I missed something.


Feature set exec path

https://github.com/takama/daemon/issues/62

Could you please remove changes related with previous PR from this PR? This action allow us to exclude conflict situation.


Feature/cloudsql backup configuration

Hey all,
I've added the additional variables to include all backup settings for cloudsql instance. Not sure if you wanted to tweak anything else or add extra validations, so please take a look and let me know.
Thank you!

I think you named the attribute to retained_count but are using retention_count. Let me know if you need help running the test suite locally so you can take a look at the error

Caio, for the README vars/outputs tables it's easier if you generate them with the tools/tfdoc.py tool. Just pass it the path of the module that needs updating. (apologies if I'm repeating this from previous PRs)

Hi @ludoo thank you and no need to apologize. I've been using the tfdoc.py, maybe my commit message wasn't clear as it sounds like I changed it manually lol :D


Update EXCEPT expression parsing to delineate each update specifier

These changes improve the parsing of EXCEPT expressions by explicitly demarcating each update specifier separately in the parse tree. I tried to add in helpful field names where appropriate in accordance with your suggestion, and added a suite of basic tests for the various update specifier combinations.

Also bump the version number to 0.6.0 in the rust and node.he config files so we can do another release after this is merged


fix(index): use segment diff to compute accurate base/head timestamps...

...when merging empty branch (with non-empty parent branch segments) to
another branch. Related use case: use CodeSystem version branch to
create a Code System upgrade instead of using the HEAD of the
CodeSystem's working branch.

Codecov Report

Merging #807 (cffe6d8) into 7.x (32d7f7d) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##                7.x     #807      +/-   ##
============================================
- Coverage     61.49%   61.49%   -0.01%
  Complexity    10931    10931
============================================
  Files          1588     1588
  Lines         53497    53498       +1
  Branches       5297     5299       +2
============================================
- Hits          32899    32897       -2
- Misses        18466    18467       +1
- Partials       2132     2134       +2

Impacted Files
Coverage Δ
Complexity Δ

...national/index/revision/BaseRevisionBranching.java
86.36% <100.00%> (-1.22%)
57.00 <12.00> (ø)

...owowl/core/branch/AbstractBranchChangeRequest.java
83.33% <0.00%> (-1.12%)
14.00% <0.00%> (-1.00%)

...ernational/snowowl/internal/eventbus/EventBus.java
67.32% <0.00%> (-0.50%)
38.00% <0.00%> (-1.00%)

.../snomed/core/ecl/SnomedEclRefinementEvaluator.java
87.16% <0.00%> (-0.30%)
108.00% <0.00%> (ø%)

...index/src/com/b2international/index/es/EsNode.java
85.88% <0.00%> (+1.17%)
16.00% <0.00%> (+1.00%)

...onal/snowowl/snomed/core/tree/TerminologyTree.java
82.69% <0.00%> (+1.92%)
21.00% <0.00%> (+1.00%)

Continue to review full report at Codecov.

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