Print title from helm get values as comment

When getting values from a release via helm get values, the first line of the output is a title that describes what values are shown:
$ helm get values my-release
USER-SUPPLIED VALUES:
foo: bar

$ helm get values --all my-release
COMPUTED VALUES:
foo: bar

This causes the output from helm get values to not be proper YAML. I propose we add #  before the title string, so that it is proper YAML. This way, it is easy for users to pipe the output directly to a file and get a valid (values) YAML file.
Proposed solution
$ helm get values my-release
# USER-SUPPLIED VALUES:
foo: bar

$ helm get values --all my-release
# COMPUTED VALUES:
foo: bar

Output of helm version:
$ helm version
version.BuildInfo{Version:"v3.13.0", GitCommit:"825e86f6a7a38cef1112bfa606e4127a706749b1", GitTreeState:"clean", GoVersion:"go1.20.8"}

Output of kubectl version:
$ kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.7", GitCommit:"84e1fc493a47446df2e155e70fca768d2653a398", GitTreeState:"clean", BuildDate:"2023-07-19T12:23:27Z", GoVersion:"go1.20.6", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.8+rke2r1", GitCommit:"395f0a2fdc940aeb9ab88849e8fa4321decbf6e1", GitTreeState:"clean", BuildDate:"2023-08-24T15:33:01Z", GoVersion:"go1.20.7 X:boringcrypto", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):
n/a

You can already get proper YAML out. Try the format helm get values my-release -o yaml. The -o is short for --output. You can specify yaml or json which are both good for machine interaction.

Thanks a lot for the input! I had missed the -o yaml flag.
In my opinion, it would still be an improvement to have the default (which is -o table, I guess? Whatever kind of table this is...) produce valid YAML, since it is so very close already. But having -o yaml is certainly good enough. Feel free to close this if you do not think it is worth implementing.

It might be worth considering for helm v4, but changing the default in v3 would break existing users.


NbMenuItem to provide ability to have notification bubble

Issue type

[ ] bug report
[x] feature request
[ ] question about the decisions made in the repository

Issue description
Current behavior:

I will start by saying, I absolutely love the simplicity and ease of use of NbMenuItem. I am only requesting an additional feature to be added.
Expected behavior:

I am looking to use this template for our custom built Help Desk application. We have different pages for actions like Approvals and Assignments. I would like to know if there is currently a way to show a notification badge next to the menu item to show the user that they need to visit that page. For example, if the logged in user had 3 approvals waiting their approval, there would be a 3 next to 'My Approvals'.
I tried to upload a photo, but it is not letting me. I can email the example, if needed.
Related code:

export declare class NbMenuItem {
    /**
     * Item Title
     * @type {string}
     */
    title: string;
    /**
     * Item relative link (for routerLink)
     * @type {string}
     */
    link?: string;
    /**
     * Item URL (absolute)
     * @type {string}
     */
    url?: string;
    /**
     * Icon class name
     * @type {string}
     */
    icon?: string;
    /**
     * Expanded by defaul
     * @type {boolean}
     */
    expanded?: boolean;
    /**
     * Children items
     * @type {List<NbMenuItem>}
     */
    children?: NbMenuItem[];
    /**
     * Children items height
     * @type {number}
     */
    subMenuHeight?: number;
    /**
     * HTML Link target
     * @type {string}
     */
    target?: string;
    /**
     * Hidden Item
     * @type {boolean}
     */
    hidden?: boolean;
    /**
     * Item is selected when partly or fully equal to the current url
     * @type {string}
     */
    pathMatch?: string;
    /**
     * Where this is a home item
     * @type {boolean}
     */
    home?: boolean;
    /**
     * Whether the item is just a group (non-clickable)
     * @type {boolean}
     */
    group?: boolean;
    /** Map of query parameters
     *@type {Params}
     */
    queryParams?: Params;
    parent?: NbMenuItem;
    selected?: boolean;
    data?: any;
    fragment?: string;
}

something like this ?

Yes, is that available now?

Hi @smithbrianscott. Thanks for your kind words. Unfortunately, you can't do this right now. See this answer for details https://github.com/akveo/nebular/issues/467#issuecomment-399354161
As for now, you need to add our own MenuItem and MenuItemComponent, probably extending nebular classes and slightly modifying the template.
Css solution we used for new icon isn't suitable for you, since you don't have static text, which could be hardcoded in css.

bump - this would be an amazing feature! I need it as well

i also need it.. plz reply

Bump!

Need this feature!

could you help me to make my own nbMenuItem component


hubot only replies to commands if his name is prefixed (heroku)

Using the 1.0.2 tar download and following the instructions on a fresh cedar stack.
Stating "help" yields the reply you'd expect, given the scripts included:
<user> is a badass guitarist - assign a role to a user
<user> is not a badass guitarist - remove a role from a user
animate me <query>  - The same thing as `image me`, except adds a few
convert me <expression> to <units> - Convert expression to given units.
help - Displays all of the help commands that Hubot knows about.
image me <query>    - The Original. Queries Google Images for <query> and
map me <query> - Returns a map view of the area returned by `query`.
math me <expression> - Calculate the given expression.
mustache me <query> - Searches Google Images for the specified query and
mustache me <url>   - Adds a mustache to the specified URL.
show storage - Display the contents that are persisted in redis
show users - Display all users that hubot knows about
translate me <phrase> - Searches for a translation for the <phrase> and then
who is <user> - see what roles a user has
youtube me <query> - Searches YouTube for the query and returns the video

However, upon trying to execute each of the commands, Hubot only seems to respond to map me <query> and none of the others.

Okay, just updated to 1.0.3, and now my hubot ("doubot") will respond to each of the commands, however it will only respond to them if the command is prefixed with its name.
I figured the Procfile has something to do with this, but that looks correct:
app: bin/hubot -a campfire -n doubot

The account's First name is "doubot", last name is blank. Thoughts?

As you can see from ddefd0474b77e1f8f7187b7bb67b744059900099, this is intentional. hear listens to everything in the room, and respond only listens to messages directed at the bot.

ah, well then I'll just close this down. Thanks @titanous.


Modal Dialog doesn't fade out

Under certain circumstances, the modal dialog will simply disappear instead of fading out (even though it successfully fades in).
The example in the documentation is what it should do (fade in and out).
https://angular-ui.github.io/bootstrap/#/modal
Ironically, the plunker link it generates shows the modal not properly fading out. I've saved my own to serve as an example here:
http://plnkr.co/edit/lmFTpQtfgV6qB4AuFrXj?p=preview
I have the same issue in a separate project of mine where I am handling the modal differently but have the same bug. I can provide the 2nd example if it would help but I imagine the plunker should be enough.
The bug appears to be browser independent as it occurs both when I use Chrome v42.0.2311.135 m and in the developer edition of Firefox (39.0a2).
UPDATE: Note that the plnkr is using the latest version of angular-ui (0.13.0) and the latest supported version of angular (1.3.13). This is not about angular 1.4.

Is this on version 0.13.0?

Yes

+1 I can also confirm this issue.

Related: #3620

also conforming the same issue with 0.13.0 + angular 1.4

Does anyone have a workaround for this bug? I really need to have it fixed by next week.

+1

+1

@jondthompson you can set animation to false so it works while fixes.

Like I said did anyone here confirm everything is working as its supposed to when you include ngAnimate?

@rvanbaalen With ngAnimate 1.40 rc.2 the modal close successfully, but the animation effect (fade out / in) won't work.

Please test with versions that we actually support. UI Bootstrap supports Angular 1.3 so you should test with Angular 1.3 and ngAnimate 1.3

@rvanbaalen  UI Bootstrap with Angular 1.3 and ngAnimate 1.3 working fine :)

Thats what I mean. Everything else will be addressed soon when we implement Angular 1.4 compatibility (when the stable release is out).

Hope this can help you, seems to be related to:
domEl.one('$animate:close', function closeFn() {
            $rootScope.$evalAsync(afterAnimating);
});

Seems that $animate:close is not triggered

Comments from #3620
There is a known issue with Angular 1.4 and the Modal/Carousel directives. The ngAnimate module had some significant changes documented here that breaks how those directives are chaining animations. The area that needs to be addressed in the modal is here. As a workaround, I changed that line from:
domEl.one('$animate:close', function closeFn() {
    $rootScope.$evalAsync(afterAnimating);
}

To:
$rootScope.$evalAsync(afterAnimating);

Keep in mind, you lose the closing animation.

Using 0.13.0 with angular 1.4 rc2, the modal dialog doesn't even appear for me. Just the dimmed backdrop.

Yay, I think angular 1.4.0 was release tonight :). When I close a dialog, the dialog disappears but the backdrop is still there.

@SlippySken I don't see the release on the official website, it is still on RC2. However, you can fix the issue as @RobJacobs mention. I did it in my code, and it is working now

I was looking at https://github.com/angular/angular.js/releases. It seems that the official website isn't updated yet.
But the workaround is working :). Thanks :)

@vprasanth @SlippySken We dont officially support Angular 1.4 yet. UI Bootstrap 0.13.0 has full Angular 1.3 support however.

+1

+1

@ecsplendid We still don't support Angular 1.4 whether bower likes it or not. The official way to verify stable releases is going to www.angularjs.org and see what versions they are offering. Currently, AngularJS 1.4 is in a release candidate state.
Based on this comment up here, I'm closing this issue. Someone can start a new issue that is specifically meant for Angular 1.4 support.

Including the corresponding version of ngAnimate and including it in the module does fix the issue. However I don't see this dependency documented anywhere on UI Bootstrap.
If we are supposed to include ngAnimate in order to get UI Bootstrap to fully function, then at a minimum the dependency needs to be added to both the Plunkr and the documentation I linked to. Oddly enough, this doesn't explain how the live example in the documentation, which does not include ngAnimate, is still working. I am also of the opinion that the "Dependencies" section at the top of the git hub page needs to specify ngAnimate as module dependency in angular.

@danielsd I agree with you. The documentation needs an update and the dependency definition of the bower project needs that as well. If I'm not mistaken @RobJacobs fixed the dependency recently. If so, that will be tackled as soon as the next release lands.
Since all code (including the docs) is open source, please feel free to help us out on that one and send a PR that includes a better documentation regarding the dependencies.
The plunkers need to be updated by @Foxandxss if I'm not mistaken.

By the way:

If we are supposed to include ngAnimate in order to get UI Bootstrap to fully function, then at a minimum the dependency needs to be added to both the Plunkr and the documentation I linked to

ngAnimate is NOT required as a dependency. UI Bootstrap is fully functioning without it. ngAnimate only adds optional eye candy with animations. At least, that's how things are supposed to work.

Angular 1.4.0 has been released

animation: false is workaround for me.

:+1:  on this issue. I'm going like this for now to globally fix it:
angular.module('MY_MODULE_NAME').config(function($modalProvider) {
  $modalProvider.options.animation = false;
});

http://angularjs.blogspot.com/2015/05/angular-140-jaracimrman-existence.html

Is there any update on this? Don't really want to have to turn animations off if possible.
I noticed this issue is labled with Angular 1.4 tag. The update in the top comment said it is for angular 1.3. I also have the issue on Angular 1.3.

I said this:

Please test with versions that we actually support. UI Bootstrap supports Angular 1.3 so you should test with Angular 1.3 and ngAnimate 1.3

And @neaped replied:

UI Bootstrap with Angular 1.3 and ngAnimate 1.3 working fine :)

That's why it has a AngularJS 1.4 label. If you're experiencing this issue in 1.3 with UI Bootstrap 0.13, please create a plunkr that demonstrates your problem.

It originally started out as an Angular 1.3 issue due to the sudden inclusion of the ngAnimate dependency, but people latched on top the Angular 1.4 issue because the ticket title didn't specify a version. The 1.4 stuff really should be in its own ticket and this one should be closed, but... *shrugs*

FWIW: As much as I'd hate to have to call this simple function for every modal I'd use, this does work and keeps animations:
      $('div.modal').removeClass('fade').addClass('hidden');
      $('body').removeClass('modal-open');
      $('.modal-backdrop').remove();

Another workaround:
instance = $modal.open(options)
promise = instance.result
promise.finally ->
  $timeout ->
    $('.modal:last').trigger('$animate:close')
    $timeout ->
      $('.modal-backdrop:last').trigger('$animate:close')

it doesn't show closing animation but it's not too hard to add.

@pgkehle, @elado should probably note that both of your solutions require jQuery.

One of the main aims of UI Bootstrap is to prevent the need of jQuery in your project. So that kind of defeats the purpose :wink:

+1

Hi,
Do you know when an update will be available?
Thank you for your work :)

:+1:, same issues, waiting for 0.14.0.

+1
Take a look on https://docs.angularjs.org/guide/migration "Migrating from 1.3 to 1.4"
Animation-related callbacks are now fired on $animate.on instead of directly being on the element.
// < 1.4
element.on('$animate:before', function(e, data) {
  if (data.event === 'enter') { ... }
});
element.off('$animate:before', fn);

// 1.4+
$animate.on(element, 'enter', function(data) {
  //...
});
$animate.off(element, 'enter', fn);

The function params for $animate.enabled() when an element is used are now flipped. This fix allows the function to act as a getter when a single element param is provided.
// < 1.4
$animate.enabled(false, element);

// 1.4+
$animate.enabled(element, false);

In addition to disabling the children of the element, $animate.enabled(element, false) will now also disable animations on the element itself.
There is no need to call $scope.$apply or $scope.$digest inside of a animation promise callback anymore since the promise is resolved within a digest automatically. (Not to worry, any extra digests will not be run unless the promise is used.)
// < 1.4
$animate.enter(element).then(function() {
  $scope.$apply(function() {
    $scope.explode = true;
  });
});

// 1.4+
$animate.enter(element).then(function() {
  $scope.explode = true;
});

When an enter, leave or move animation is triggered then it will always end any pending or active parent class based animations (animations triggered via ngClass) in order to ensure that any CSS styles are resolved in time.

+1 Thanks @LeonanCarvalho for the information

Any fix for this rather than setting
animation: false

I also have this issue with angular 1.3. Modals open, but will not close. I have been able to get around this by disabling animations globally, however this is not desirable.
I am confused though, I have seen animations working on Plunker with 1.3 and 0.13.0, however there seems to be a good portion of people who are seeing this issue. It seems that something else is involved.

I'm experiencing the same issue with angular 1.3.15, angular-animate 1.3.15, and ui-bootstrap 0.13.0.  I am unable to close a modal after opening it.

What about just CSS animation?

@311chaos @astreate I've no problem with backdrop on angular 1.3 since it requires ngAnimate.
Here is the plnkr http://plnkr.co/edit/zHEHNTI1Yps7UBh9Cze9?p=preview

+1 @astreate . Also unable to close modal with those same versions.

Hi, I've started a PR. there are still things hardcoded but it works. Any reviews would be appreciated : https://github.com/esion/bootstrap/pull/1 this include a demo

I have the same issue, 0.13 with angular grater than 1.3.16 does not work

This is what I am using as a workaround.

OK
Cancel

/*global angular */
(function () {
'use strict';
angular.module('CorvetteClub.removemodal.directive', [])
.directive('removeModal', ['$document', function ($document) {
return {
restrict: 'A',
link: function (scope, element, attrs) {
element.bind('click', function () {
$document[0].body.classList.remove('modal-open');
angular.element($document[0].getElementsByClassName('modal-backdrop')).remove();
angular.element($document[0].getElementsByClassName('modal')).remove();
});
}
};
}]);
}());

Note that the original bug/issue here is actually that the modal initially fades in when it should instead skip the animation since ngAnimate module wasn't included.

@chrisirhc No, the original issue was that the modal would fade in correctly but would skip the fade out animation and just disappear.

That's incorrect. If angular-animate isn't included, there expected behavior is that there will be no animations at all. Disappearing is the expected behavior. You need angular-animate for animations, that's the change when upgrading to 0.13 .

Read the first sentence in the OP
[Quote="danielsd"]
Under certain circumstances, the modal dialog will simply disappear instead of fading out (even though it successfully fades in).
[/Quote]

Yes, successfully fading in is the wrong behavior.

That's not what is being discussed at all. The entire gist of the thread from the original OP to the very end has been a series of workarounds to determine how to keep the animations but also not include breaking changes by doing so.
I'm not trying to turn this into an argument but incorrectly stating the issue does nothing to help resolve it.

The first thing you need for animations is angular-animate . If it isn't included, the discussion is on the wrong track.

Correct, and that was mentioned, and resolved, early on in the thread. Now the issue is that with the changes made to ngAnimate the actions provided by $modal and $modalInstance are not firing the necessary functions to remove all of the classes provided by $modal. In my case it made the entire screen disabled irregardless of if there was a mask or not.
The issue has nothing to do with inclusion at this point. Now what needs to be done is that the code needs to be updated to work with ngAnimate in its newer state. Until then a workaround is what will need to be used and has been provided.

Please see if #3895 resolves your issue. Otherwise, please open another issue for that discussion.
The reason for this is so that the issue doesn't get lost in the haystack. If the discussion is no longer about the original issue, it will be missed by the maintainer.
Unfortunately, as a maintainer, I have limited amount of time to go through issues every day and unable to go through every single message or track down every fork in the discussion.
I think the fact that the original issue was resolved is good reason to close this. This issue in its current state only serves to confuse others.

This thread needs to be forked into a completely new issue about five posts from the top if the focus is going to be put on inclusion as most of the discussion is not pertinent in that vein.

I found out that the problem is in 0.13.0 version. 0.12.0 works fine even with AngularJS 1.4.1.

:+1:
Can this fix be rolled out to bower asap please?

+1

@dyatchenko Thanks, works for me

BRAVO. Thanks for the speedy fix!

+1 @dyatchenko

Thanks @dyatchenko
Version 0.12.1 also works fine using latest Angular (1.4.1)

@rsfurlan90 yes, this is the paradox

But popover-template while only works with 0.13.0 in Angular 1.4

I'm confused... So the only way to solve this problem is using  0.12.1 with Angular 1.4?

Or config animation to false in 0.13.0
$modalProvider.options.animation = false;

This should be fixed on master and via next release (0.13.1).

Downloaded 0.13.1 today, but the issue with the modal background not closing when animations are enabled remains (I'm using Angular 1.4.2).

@bennettatoms
It seems fixed for me on angular 1.4.2 (with ng-animate installed), but I had to set $modalProvider.options.animation = true; in order to show animations (are they off by default now?)

Still experiencing the same problem with 0.13.1 and Angular 1.4.3

1.4.3 & 0.13.1 here, no more problem for me. neither with popover-template.

Double checked. I confirm the problem is there on my application with 0.13.1. Works if i rollback to 0.12.1. I'll try to investigate what could be the problem a bit later if I have the time.

Fixed for me too with Angular 1.4.3 and Angular-Bootstrap 0.13.1.

I'm using a workaround solution by turning off the animation.
$modal.open({
animation: false
}
Att,
Emerson R. Mellado
2015-07-29 12:34 GMT-03:00 aaaaahaaaaa<EMAIL_ADDRESS>
Double checked. I confirm the problem is there on my application with
0.13.1. Works if i rollback to 0.12.1. I'll try to investigate what could
be the problem a bit later if I have the time.
—
Reply to this email directly or view it on GitHub
https://github.com/angular-ui/bootstrap/issues/3633#issuecomment-125991083
.

Still broken, right? Using angular-bootstrap 0.13.1 (bower) and angular 1.4.2.

Success! Doesn't work with angular 1.4.2 with angular-bootstrap 0.13.1, but when upgraded to angular 1.4.3, suddenly starts to work.
But one thing I do not like is: when modal is closing, first the .modal-dialog will animate-out; and only when it is complete, then the .modal-backdrop will begin animate-out. So if .modal-dialog animation duration is 250ms, and .modal-backdrop animation is 250ms, it will take 500ms for the modal to close.
However, when opening modal, .modal-dialog and .modal-backdrop animate simultaneously. So it each requires duration of 250ms, the modal will use 250ms to open.
As someone who does not like waiting, I find this to be irksome. However, if I reduce the animation-out duration to be 125ms each, for a total of 250ms, the animation feels choppy and unfulfilling.

This appears to be working now with angular 1.4.3 and angular-bootstrap 0.13.1.

Confirm v1.4.3, v0.13.1

Using 1.43 with 0.13.1 with Bootstrap 3.3.5, fading in works but fading out doesn't work. It is due to reaching domEl.remove() in afterAnimating() too fast which removes the element before it has finished fading out.

I had the same issue @levin81, try to include ngAnimate module, it worked for me.

I have included it. I have tried messing around with different versions of Angular as well. Still doesn't work.

I updated angularJs 1.4.3 & angular-ui 0.13.2 from Nugget in Visual Studio 2012 yesterday,
the modal option animate is true, and no matter nganimate is included or not, modal just fade in no fade out. any workaround? I am still stocked in this animation....

Look at the plunker that I linked - it is barebones. Did you add 'ngAnimate' to the dependencies of your app?

not working with me with v1.4.3, v0.13.1. All links become disabled after the modal dismissal.
Disabling animation have solved the issue.
animate: false

Thanks @itsazzad . I've disabled the animation for now as well.

Add property 'animation: false' for resolving this issue:
var modalInstance = $modal.open({
templateUrl: '...',
controller: myController,
animation: false,
size: 'lg',
resolve: {
...
}
});

I debugged function removeAfterAnimate and it looks like the problem with the fade out is caused by this one: https://github.com/angular/angular.js/issues/6049

+1

As @Rems69 mentioned: including ngAnimate fixed this problem for me as well.

updating to angular-bootstrap 0.13.3 solved the problem for me too.

updating to angular-bootstrap 0.13.3 solved the problem for me too.

The bug still exist in my setup (ng 1.4.8). Downgrading to 0.12.1 fixes problem.


Error when generating from schema with polymorphic models - given constraint name ... has to be unique in the following namespace...

Description and expected behavior
I've been playing around with the 2.0 polymorphic features of zenstack and ran into an issue I can't seem to get around / find documented here:
"Generating Prisma schema" completes successfully but I run into the following error during "Generating PrismaClient enhancer"
error: Error parsing attribute "@relation": The given constraint name `UserFavorite_id_fkey` has to be unique in the following namespace: on model `UserFavorite` for primary key, indexes, unique constraints and foreign keys. Please provide a different name using the `map` argument.
  -->  schema.prisma:69
   |
68 |     delegate_aux_personId String
69 |     delegate_aux_studio Studio @relation(fields: [id], references: [id])
70 |     delegate_aux_studioId String
   |

Validation Error Count: 4
[Context: getDmmf]

Prisma CLI Version : 5.10.2
✖ Generating PrismaClient enhancer
Prisma: Failed to run "prisma generate

Here is a simplified version of my schema.zmodel:
generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model User {
    id            String    @id @default(cuid())
    name          String

    userRankings UserRanking[]
    userFavorites UserFavorite[]
}

model Entity {
  id      String          @id @default(cuid())
  name    String
  type String
  userRankings UserRanking[]
  userFavorites UserFavorite[]

  @@delegate(type)
}

model Person extends Entity {
}

model Studio extends Entity {
}

model UserRanking {
  id      String       @id @default(cuid())
  rank     Int

  entityId      String
  entity        Entity        @relation(fields: [entityId], references: [id], onUpdate: NoAction)
  userId   String
  user     User @relation(fields: [userId], references: [id], onDelete: Cascade, onUpdate: NoAction)
}

model UserFavorite {
  id      String       @id @default(cuid())

  entityId      String
  entity        Entity        @relation(fields: [entityId], references: [id], onUpdate: NoAction)
  userId   String
  user     User @relation(fields: [userId], references: [id], onDelete: Cascade, onUpdate: NoAction)
}

Based on the error message, I think a possible solution would be to add a map property to the relation attribute as it suggests. When I go in and modify node_modules\.zenstack\delegate.prisma just to try it out, the IDE error goes away at least so I think its promising. Maybe on generation this should be added? Or an option to specify this somewhere in the zmodel?
// delegate.prisma
-- delegate_aux_studio Studio @relation(fields: [id], references: [id])
++ delegate_aux_studio Studio @relation(fields: [id], references: [id], map: "studio")

Environment (please complete the following information):

ZenStack version: 2.0.0-alpha.1
Prisma version: 5.10.2
Database type: postgresql

Additional context
Oddly enough changing the generator provider to sqlite seems to remedy the issue (something prisma related?) but I was hoping to use postgresql
Thanks
-Andrew

Hi @andrewkucz , thanks for reporting the issue. Yes, you're right, the generated delegate.prisma should include the "map" argument to disambiguate fk constraints. I'll make a fix in the next alpha release.

Hi @andrewkucz , thanks for reporting the issue. Yes, you're right, the generated delegate.prisma should include the "map" argument to disambiguate fk constraints. I'll make a fix in the next alpha release.

Thanks for the swift feedback @ymc9 -- thats great to hear! And props on an awesome library, excited to use it!

Fixed in 2.0.0-alpha.6


[Dashboard] Add some informative badges to the Explorer

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
This PR enhances the user interface of contract function components by adding visual elements like Badge components for showing output types and function state mutability. It also improves layout and organization of the displayed information.
Detailed summary

Added Badge to display the Solidity type of function outputs in InteractiveAbiFunction.
Improved layout in InteractiveAbiFunction by wrapping output heading and type in a div.
Introduced functionSelector calculation in ContractFunctionInner.
Updated Badge usage for function state mutability in ContractFunctionInner and ContractFunctionInputs.
Adjusted layout properties for better alignment and spacing in ContractFunctionInner.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#5138  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @kien-ngo and the rest of your teammates on  Graphite


[Q]

Hi! I am using W&B with Pytorch Lightning and I have an issue with .json files of W&B Artifacts being created multiple times at different locations for each run.
Skipping to the relevant parts in my pipeline, first, I specify the cache directory for W&B and initialize a WandbLogger:
os.environ['WANDB_CACHE_DIR'] = '<save dir>'
wandb_logger = WandbLogger(project='<project name>',
                                                   name='<expt name>',
                                                   save_dir='<save dir>',  # ***
                                                   log_model=True,
                                                   entity='<entity>',
                                                   group='<run group>')

I then pass this logger to a Trainer:
trainer = pl.Trainer(...
                              default_root_dir='<root dir>',
                              logger=wandb_logger,
                              ...)

which I then use for training: trainer.fit(...).
During training, I create tables and lineplots from some run data, which I want to visualize:
wandb_table = wandb.Table(data=data, columns=[xlabel, ylabel])
wandb_lineplot = wandb.plot.line(wandb_table, xlabel, ylabel)

which I then log using the WandbLogger passed to the Trainer during training:
self.logger.experiment.log(wandb_lineplot, step=self.global_step+1)

The issue is the following: .json files containing the data I pass to wandb.Table are created in two different locations: 1) they are saved to the path I provide to the save_dir argument of WandbLogger and 2) also saved in /tmp/ a second time, where other jsons are also created that seems to contain some metadata:
{
    "version": 1,
    "storagePolicy": "wandb-storage-policy-v1",
    "storagePolicyConfig": {
        "storageLayout": "V2"
    },
    "contents": {
        "valid_prc_table.table.json": {
            "digest": "<...>",  # I manually removed the values here
            "birthArtifactID": "<...>",  # I manually removed the values here
            "size": "<...>"  # I manually removed the values here
        }
    }
}

I would like to not have the Artifact data saved multiple times at separate locations, especially because the files created in /tmp/ are on a partition that don't have a lot of space, resulting in runs crashing. Manually removing the contents of /tmp/ is also not practical because there is a high turnover of runs.
Why are .json files also created in /tmp/ and how can I control this? Do I need to specify some additional arguments somewhere that stops Artifact data from being saved in /tmp/ and only saved to the run directory I pass to WandbLogger? Otherwise, can I control the location to where the /tmp/ copies are saved?
Weights and Biases version: 0.12.1
Python version: 3.9.7
Operating System: Ubuntu 18.04.6 LTS

Hey @gnikolenyi ,
Thanks so much for taking the time to detail your use case and how you are logging in using WandB.
It is not possible to disable the logging of media to /tmp . or to control where files are stored, this is because we separate our media from what is logged in your artifact directory. We use this as a way of optimizing (especially in ephemeral compute environments) how much time it takes to pull and retrieve data that has been versioned using artifacts.
you can clear your artifact cache using:
wandb artifact cache cleanup 0GB
If you want to sync and clean the cache you can run the following:
wandb sync  --clean --clean-old-hours 0
However this will not affect the media logged-in temp, I can submit a feature request to clean this up at the end of each run for you if this is what would best fit you use case.
I know that you have advised that it would not work to clear '/tmp' but I know that if you have already synced you should be able to safely delete all WandB associated dirs and wonder if you could embed something like the following in your script after runs have synced work for you?:
os.system('find /tmp -type d -name "*wandb*" -exec rm -rf {} \;')

Hope this helps and look forward to hearing back from you.

Hi @fdsig, thank you for the quick response and explaining how logging works on your end.
I looked more into where Artifacts are logged and it seems that apart from the two locations I mentioned above (save_dir path of WandbLogger and /tmp) a third copy is created at 'WANDB_CACHE_DIR'. Running wandb artifact cache cleanup 0GB or wandb sync --clean --clean-old-hours 0 both take care of these copies.
As for the files created in /tmp, I followed your last advice and added a line of code at the end of my python script that removes them, which seems to work fine as a semi-automated solution.
Thanks again for the suggestions!

Hey @gnikolenyi ,
You are of course super welcome 😄 , I am really glad that this worked for you. I will mark this as closed but please do reach out for further assistance with this or any other area of WandB that you need support with.


Ignore latin-1 enconding errors when serializing the posting list XML

Coverage increased (+0.0004%) to 99.406% when pulling 60b934154385d1eec7f0a7855caf2670392242d9 on ignore-encoding-errors-on-xml-serialization into ffee49daf5c134bac61f2284521f969c1af55bb3 on master.

:+1:

:+1:


Scroll issue at small screens (mobile landscape)

Hi,
I attached a gif that shows the misbehaviour when we're dealing with mobile landscape screens, where the items are not been visible at the right place inside dropdown balloon.
After some quick tests, the issue is related with the translate calculation since the items are there but not in the right position due to that change.
Thanks for your good work!

@joselrio thanks for letting me know it. I will fix it in the future release.

@joselrio @gnbm This issue has been fixed in the release v1.0.28


Create tthkee

Schools homepage https://www.tthk.ee
IT related vocations page https://www.tthk.ee/oppekavad/infotehnoloogia/

@kivikangur-tthk lib/domains/com/onmicrosoft/tthkee: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@kivikangur-tthk Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


Update Lambda runtime from Go 1.x (Deprecated) to custom runtime on Amazon Linux 2

Problem:
Amazon announced the end of support for Go 1.x runtime and the lambdas deployed with cdk-ecr-deployment running on go 1.x runtime will no longer receive support from December 31, 2023 and we will not longer be able to deploy new functions from January 30, 2024.

We are ending support for the Go 1.x runtime in AWS Lambda, in line with Amazon Linux AMI end of maintenance support on December 31, 2023. Lambda continues to support the Go programming language, using the provided.al2 runtime. Using the provided.al2 runtime offers several benefits over the go1.x runtime, including support for AWS Graviton2 processors and a streamlined implementation with a smaller deployment package and faster function invoke path. For more information, see our blog post. As described in the Lambda runtime support policy, end of support for language runtimes in Lambda happens in two stages. Starting December 31, 2023, Lambda will no longer apply security patches and other updates to the Go 1.x runtime used by Lambda functions, and functions using Go 1.x will no longer be eligible for technical support. In addition, you will no longer be able to create new Lambda functions using the Go 1.x runtime. Starting January 30, 2024, you will no longer be able to update existing functions using the Go 1.x runtime. We recommend that you upgrade your existing Go 1.x functions to the provided.al2 runtime before December 31, 2023.

Reference:
https://aws.amazon.com/blogs/compute/migrating-aws-lambda-functions-from-the-go1-x-runtime-to-the-custom-runtime-on-amazon-linux-2/
Request:
Update the runtime to provided.al2 runtime as mentioned by AWS

@scanlonp I'm tagging you here based on https://github.com/cdklabs/cdk-docker-image-deployment/issues/433. I've previously tried to get someone to look at this repository and that issue received no attention.
Users of these package are in a pretty unpleasant position. An AWS recommended solution appears to be now abandoned. I have projects depending on this that will no longer be deployable to new accounts as of next year, and no path forward I know of other than create my own replacement (as we know cdk-docker-image-deployment does not support Python currently).
I'd be willing to do the work to revive and release https://github.com/cdklabs/cdk-ecr-deployment/pull/323, but currently it seems like I'd be wasting my time because there's no owner here to merge the change.
Frankly, it appears AWS's custodianship of its open source eco-system appears to be failing; I urge you to raise this with your leadership. AWS needs to either commit more resource, or actually bite the bullet and either shut these packages down or find owners outside AWS for them. Currently these unsupported packages are a trap - you build a solution around them, and only then find that the level of support and care you expect from something with the AWS brand on it just isn't there.

@SamStephens I have no problem helping that PR get merged if you would like to finish up the work on it. However, this repository is not going to be one that I personally will commit to maintaining.
I think your larger point about the state of this & other repositories in our open source sphere has weight. It is something that we are concerned with, and we are doing work to strategize on. I will voice your message to the team.

@SamStephens Also I do not know if you have a presence on the cdk.dev slack channel, but feel free to message me there! I have some thoughts about this specific issue (user control of docker images in cdk projects) that we could discuss & maybe tailor some solutions to your use case. (More than happy to have discussions on Github, just wanted to offer since Slack it is a little more direct + immediate in terms of communication!)


Grid-based dimension handling

Requires #378.
The primary intent of this PR is to remove all global instances of Dimension objects and manage dedicated default dimensions (x, y, z, t, time) either via the Grid or the Function object that uses them. The most useful effect of this is that the Operator-level substitutions of spacing variable (h_x, h_y, h_z) now become optional, as the Grid can provide default values for them. Explicit spacing substitution is kept for seismic examples though, but provided via much neater API.
The changes in detail:

The Grid now creates default space and time dimensions and all derived Function objects use those, unless explicitly overridden by the user.
The spacing symbols on each Dimension are now created as Constant objects, allowing us to use the defaulting mechanism in the argument engine to provide Grid-dependent defaults.

As a corollary of the above, we can now create completely state-free generic operators, that have no hard-coded assumptions about the domain geometry in them. This is important for baking static libraries from Devito operators.

The Grid now also provides a spacing_map that can be used to provide the operator-level substitutions of spacing symbols. This is used throughout the seismic examples.

This map does not include the temporal spacing, which has been renamed s->dt, so as to allow the notation of op(time=ntimesteps, dt=dt) on operator invocation.

SparseFunction objects always need to be created from a Grid, since they derive all meta-information about their coordinate space from it (eg. problem dimension). This will likely have some overlap with #381.
No more global dimension objects!
Various small tweaks and fixes across the DSE/DLE and arguments engine to remove hard-coded use of default dimensions and/or fix resulting bugs.

Oh, don't forget to drop the spurious is_Fixed, if you haven't done that already

Oh, don't forget to drop the spurious is_Fixed, if you haven't done that already

Yes, will do.
As for not using keyword args for Function constructors I would generally agree in principle, but I've tried before and it's a bit fiddly so I gave up. This kind of also ties in with the idea of not actually having a second-level cache, but using _hashable_content and maybe some uuid magic to force sympy to provide our desired caching behaviour for Function types. Both are on my wishlist, but quite complicated, and I have given up before. Maybe I should file an issue reminder...

Ok, I believe I have addressed all comments. @FabioLuporini can you confirm please?
The final problem now is the travis YASK builder, which times out. The problem seems to be that the YASK backend can currently not deal with Constant symbols, thus it reverts to explicit point-wise get/set methods for the core stencil instead of run_solution(). This ultimately is super slow and causes timeouts.

Could you also drop is_Open and is_Closed in Iteration? They're now useless

Update: I believe we have found all remaining YASK errors due to Constant handling. This means we need #384 to go in first. I also had to disallow explicit shape/dimension parameters in the TimeFunction constructor, but that was pretty much unused anyway. Let's see if travis agrees with my assessment.

Yes, please rebase and then, if Travis permits, merge.

Ok, let's go. Merging...

This means we need #384 to go in first. I also had to disallow explicit shape/dimension parameters in the TimeFunction constructor, but that was pretty much unused anyway.

Since when, these PR forcing are getting really annoying,

@mloubout The requirement is simply due to a YASK-bug that was fixed in #384 and was causing travis to fail for this branch. Creating and merging a separate branch is actually good practice, since it allows a single feature or fix to be reviewed independently, as in this case the use of Constant symbols through YASK. If another branch requires a certain feature or fix, this simply creates a dependency, and thus forces the merge order. This is the essence of distributed development and a vastly superior workflow to creating huge monolithic branches/PRs that contain multiple features and fixes.

The requirement is simply due to a YASK-bug that was fixed in #384

If it was fixed , why is the requirement still there?

??? #384 fixes the bug, so I rebased this branch on top of #384. Merging the individual branches in order is simply good practice to keep the diff clean and and managable. I really don't understand what your problem is here?

order is simply good practice to keep the diff clean and and managable

I have no issue with that at all, my question is:

I also had to disallow explicit shape/dimension parameters in the TimeFunction constructor

is this no decided as not possible?

Ah, now I get what you mean now. Yes, nothing in the test base really required explicit shape/dimension pairs for TimeFunction, so I removed it to break the cyclic dependency between Function and Constant that arose from the defaulting code for time (both need to be dynamically dispatched through base.py for the backend to work correctly).
If you need to define explicit dimensions on a TimeFunction object can you please provide an example and/or test case so that we can find another solution for this? In the meantime, it should need a minimal coding overhead to force TimeFunction behaviour with custom dimensions via the Function interface, for example (untested):
grid = Grid(....)
x, y, z = grid.dimensions
t = grid.stepping_dim
f = <some custom dimension>
u = Function(name='u', dimensions=(t, f, x, y, z), ...)

As for the "forcing" this change, I fast-tracked this PR because the infamous #345 now depends on it. Sorry, if that decision was rushed and/or if this inconveniences you. But I believe we all want want #345 out of the way now... :frowning:

Great, thanks for the detailed answer, will cook up a test/example as soon as I find time


No convex hull

I think the model would be much more useful if it outputted convex hull in addition to bounding box (I imagine you do convex hull anyway to get the bb?)

Closing because I realized there is no convex hull step to this since this is all in a neural network


[RFC] Moving MXNet-AMP to core

MXNet already has experimental AMP (Automatic Mixed Precision) support, exposed in mxnet.contrib package. It is used for automatic casting models to both float16 and bfloat16. This RFC covers moving it into core / making a first-class feature, as well as further development.
Here's a rough task break down for the initial move:

Need to ensure AMP works with numpy ops - i.e., all ops are in either of the lists
API change: make loss scale public (https://github.com/apache/incubator-mxnet/issues/17507)
A number of issues has to be resolved to improve user experience:

Cannot load trainer with AMP (https://github.com/apache/incubator-mxnet/issues/16858)
There's a CUDA crash (IMA) in amp_multicast, happens on some models (Yolo3)

The actual shuffling code around and updating import paths

Post move:

Layout optimization - upstreaming feature already existing in NVIDIA NGC container. This helps convolutions' performance by automatically casting between NCHW and NHWC layouts.
Explore alternatives to front end ops monkey-patching (https://github.com/apache/incubator-mxnet/issues/18697)

cc @sxjscience @leezu

@mk-61 If you'd like to see some test cases of the new numpy API, you can also try the numpy version of GluonNLP:  https://github.com/dmlc/gluon-nlp/tree/numpy . Would we connect via Slack?


Removed 1.19 from SUPPORTED_RELEASE_BRANCHES

Issue #, if available:
Related to https://github.com/aws/eks-distro/issues/983
Description of changes:
Removed 1.19 from SUPPORTED_RELEASE_BRANCHES
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


bouk/monkey license illegal

I see go.mod used bou.ke/monkey v1.0.2, but this package refused any to use it.
https://github.com/bouk/monkey/blob/master/LICENSE.md

#1631


Unable to find version latest

Following the readme, my action errors like this:
Error: Unable to resolve action `d3rhase/rsync-deploy-action@latest`, unable to find version `latest`

Fixed by using uses<EMAIL_ADDRESS>Maybe you could add a tag for latest as well?

Of course, I'll add that later.


Composer 2

Now that Composer 2 has been released I was wondering what you think is the best approach to make it available on the image.
Not sure if it makes sense to have both versions available for a while or if it'd be better to include version 2 directly since they are mostly compatible. An advantage is that we can remove prestissimo from the dependencies, for the rest, I've been testing it on the image and there's nothing else that seems to be causing issues.
I guess there will be people for which there may be some incompatibilities but if they've been using an up-to-date version of this image they probably have been getting warnings about it for a while.
What do you think? I can help create the PR with whatever approach you think is best.
Cheers!

Hello @j3j5
Temporarily, on an existing project, we are testing the following solution:
project:
  services:
    - mariadb:10.3
  image: edbizarro/gitlab-ci-pipeline-php:7.4-alpine
  script:
    - composer -V # Composer version 1.10.15 2020-10-13 15:59:09
    - sudo composer self-update --2
    - composer -V
    # The "hirak/prestissimo" plugin (installed globally) was skipped because it requires a Plugin API version ("^1.0.0") that does not match your Composer installation ("2.0.0"). You may need to run composer update with the "--no-plugins" option.
    # Composer version 2.0.3 2020-10-28 15:50:55

I think it would be good to be able to switch from V1 to V2 and vice-versa.

Hi @romainnorberg , that exactly has been my approach, to upgrade from the container, but I guess it'd be better if we could choose w/o having to download the upgrade/downgrade every time. Personally, I'd go for using composer2 only and leave the downgrade (as you mention above) as an option, but I guess it's @edbizarro call.

I see there's an open PR #108, I'm fine with that approach :+1:

@j3j5 I confirm you before doing my PR, I saw the message from @romainnorberg and i use this to solve my CI :)

@edbizarro  Possible that composer 2 is still not working?

Is there anything that is being done about this?
Is there a better alternative?


Gunpla Club Basic Modelling and Introduction

Session Name
Gunpla Club Basic Modelling and Introduction Workshop
Abstract
Gunpla Club is a plastic modelling club in SUTD. The club specialises in plastic models and welcomes all who enjoy plastic modelling, as well as improving members' maker skills and competencies with 3D printing and modelling.
Student Organisation organising this session
Gunpla Club
Event Format
Physical
Session intent (what to expect)

Student participants will get to know more about Gunpla Club's activities and session timings.
Student participants will get to learn the basics of plastic modelling, such as how to use cutters, how to file etc.
Student participants will get to learn more about 3D printing basics, 3D model preparation, basic 3D printing troubleshooting.
Student participants will get to learn more about advanced additive manufacturing capabilities in SUTD by visiting DManD Centre (TBC)

Session details
Number of participants: 10-20 (Groups of max 4 due to SMM)
Location: Student Activity Centre (SAC), Think Tank 16/17/18, others TBC
Timing: 27th September 2021, 7-10pm
Speakers/Workshop facilitators
Speakers/Facilitators are Gunpla Club members and alumni who are passionate about plastic modelling and 3D printing.
They will share their experience with plastic modelling and 3D printing, especially their use in projects and the industry.
(Will include specific facilitators at a later date)
Sign up link(if any)
MS Forms Sign Up: https://forms.office.com/r/WTizk3RBNF
Workshop Telegram: https://t.me/joinchat/DT-hEwjySWBlZDk9
Logistical details / Budget Needed
Cutters: $2x20 - Aliexpress
Glass file: $2x20 - Aliexpress/Shopee
Filament: $20x5 - Shopee
Email<EMAIL_ADDRESS>

Good day, thank you for your submission.
Could we check if there is a preferred date for your workshop? This will help with the booking of the venue.

Good day, thank you for your submission.
Could we check if there is a preferred date for your workshop? This will help with the booking of the venue.

Edited to include workshop date

Good day, thank you for your submission.
Could we check if there is a preferred date for your workshop? This will help with the booking of the venue.

Edited to include sign up link, telegram group link

Hi @9Breaker , just an update and some clarification from our team:

How many venues in total needed? Is one venue to host your 20 pax sufficient?

TT16 and TT17 will not be available during the September term. So we're quite tight on venue space.

Where is the SAC located at, we are not sure if we have booking access to that venue.

Do update before this coming Wednesday, 25 Aug. Thank you!

Hi @makehahaz ,
Apologies for the late reply. To address your queries:

We only require one venue. The above venues are suggestions as we understand that there is a chance that one of them might be occupied, therefore we put a few options that we are considering.

That is fine. Alternative suggestions are welcome.

The SAC (Student Activity Centre) is located at building 5 level 4. You do not need to book the venue for us, we can settle that on our end and drop OSL and email for access.

If anything requires urgent attention, you can drop me a pm on tele @NineBreaker

Hi @Sorahawk ,
We will request a booking of TT18 for your event.
May I clarify that the 20 participants includes the number of facilitators too? If so, would it be possible to estimate the number of facilitators?
Would be great if you could let me know by today. I have dropped you a Telegram message too.
Thank you xx

Hi @9Breaker ,
We will request a booking of TT18 for your event.
May I clarify that the 20 participants include the number of facilitators too? If so, would it be possible to estimate the number of facilitators?
Would be great if you could let me know by today. I have dropped you a Telegram message too.
Thank you xx

Replied via tele: total attendee would be 20 + 5/10facils
Just an update, no actions required


Fix the base/addon products in the test data

We were just missing the product name in the test data.
Tracks https://github.com/SUSE/spacewalk/issues/2453

I also noticed further inconsistencies in the test data, which I fixed in the last commit.

Thanks @mackdk for the review! Merging.


UDP Emitter should refresh daemon address periodically and should not throw communication errors

We have the XRay daemon running in an ECS container with awsvpc network mode and Route53 Auto Naming Service Discovery enabled. The XRay address is set via the AWS_XRAY_DAEMON_ADDRESS system property as fqdn. Due to some shortcomings in the UDPEmitter, this causes some problems.

Sometimes the XRay container is not started at the moment the UDPEmitter on the 'to be traced' server is constructed. The java InetAddress could not resolve the hostname and sets a flag 'unknown host'. This flag will never be reset.
The IP address of the XRay container could change when it is restarted. The UDPEmitter keeps throwing its data to the first found IP.
The communication errors which occurs as result of cause 1, is not catched.

I think it will be easy to implement a polling thread which periodically re-resolves the daemon address and pass the new InetAddress to the UDPEmitter.
And add some try/catch wrappers around the UDPEmitter data transfer methods.

Hello @choeflake, thank you for contacting us regarding your current issue. You raise a good point and we will add this feature into our backlog. In the meantime, you can create your own emitter by implementing Emitter class to unblock your issue by now. Feel free to contact us if you have any questions.

AWS X-Ray SDK .NET/Core has a polling thread that performs DNS resolution every 60 seconds.
While implementing this feature, it is important to consider that the DNS resolved should be correctly reflected to X-Ray client (used by sampling pollers), UDP emitter and be  thread safe.


Mark remains active when adding text or line break after highlighted comment

When I select some text and add a comment, and then add more text in the editor right after the highlighted word, the text I add is also underlined. The mark is still active. The same happens if I insert a line break.

Hey, extending Comment extension and adding inclusive: false should fix this.
Comment.extend({
  inclusive: false
}).configure({
  ...rest of configuration
})

It works perfectly. Thanks 🙏

It works perfectly. Thanks 🙏


DocExtract: take advantage of affected fields

Originally on 2013-11-19
Similarly to the record indexer, see #1573, it would be good to
take advantage of records' affected fields to see if DocExtract daemon
has to really run on a given modified record or not.  Example: when
only title field was changed, it should not be necessary to trigger
record reference extraction.

There is no PR for this issue, hence closing it as per the legacy code base freeze; it is addressed in master code base differently.


fix LocalDate use millis as default DateFormat, for issue #2477 Monster Yesterday 23:19

What this PR does / why we need it?
Fixed the issue in the Fastjson v1 compatibility module where LocalDate deserialization defaulted to timestamp. This problem does not exist in both Fastjson1 and Fastjson2.
Summary of your change
Added the 'UseISO8601DateFormat' feature when generating the default DEFAULT_GENERATE_FEATURE. and wrote the corresponding test class. The default serialization of LocalDate, LocalDateTime, Instant, Date, LocalTime, OffsetDateTime, ZonedDateTime, and Calendar will all be affected.
Here are the date formats before the fix：
{
    "date":<PHONE_NUMBER>277,
    "localDateTime":<PHONE_NUMBER>277,
    "localTime": -19451723,
    "zonedDateTime":<PHONE_NUMBER>277,
    "calendar":<PHONE_NUMBER>277,
    "offsetDateTime":<PHONE_NUMBER>277,
    "localDate":<PHONE_NUMBER>000,
    "instant":<PHONE_NUMBER>277
}

Here are the date formats after the fix：
{
    "date": "2024-04-29T02:36:33.686+08:00",
    "localDateTime": "2024-04-29T02:36:33.686+08:00",
    "localTime": "02:36:33.686",
    "zonedDateTime": "2024-04-29T02:36:33.687+08:00",
    "calendar": "2024-04-29T02:36:33.687+08:00",
    "offsetDateTime": "2024-04-29T02:36:33.686+08:00",
    "localDate": "2024-04-29",
    "instant": "2024-04-29T02:36:33.686+08:00"
}

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

请在本地执行mvn validate修复codestyle问题，通过mvn clean install跑通过testcase

@wenshao 我有个疑问，我又重新看了下代码发现Date的默认序列化在fastjson2中变成了writeDateTimeISO8601，而在fastjson1中是时间戳，这个新的feature吗？

是的，fastjson2序列化Date的行为缺省是yyyy-MM-dd'T'HH:mm:ss[.SSS]了，因为millis的方式大家反馈不方便。


Collection Hooks uses modifier from first document for all documents when an update is run with multi=true

When collection hooks are in place and an update is run with the option multi=true, the modifier which is established in the first document is used for all documents.
Example:
Say there is a collection named Jobs and it has a few fields, one of which is name. You write a hook to duplicate the name field to another field (this example could be anything else as well), it looks like this (coffeescript)
Jobs.before.update (userId, doc, fieldNames, modifier) ->
  modifier.$set = modifier.$set || {}
  modifier.$set.newField = doc.name
  return

There are a few documents that have entries like this:
Document 1
name: "Job1"
archived: true

Document 2
name: "Job2"
archived: true

If a query like this is run:
  Jobs.update({archived:true},{$set:{status:'Archived'}},{multi:true});

The results will be this:
Document 1
name: "Job1"
archived: true
status: 'Archived'
newField: "Job1"

Document 2
name: "Job2"
archived: true
status: "Archived"
newField: "Job1"

Obviously this is a lame example, but its a simpler example than my real use, but the issue is the same, the same modifier is being used for all documents.
Fixing this issue would also help make https://github.com/todda00/meteor-friendly-slugs better which uses this module, which currently is set to look for multi=true and do nothing in that situation.

Huh... There is literally nothing I can easily do about it by virtue of how it's a single operation. You get once chance to mutate the modifier, as the underlying call is a single call to mongo too. I don't think we should be changing how update with multi:true behaves as this would mess with how one expects things to go down. What I mean by this is that the only way to make this work as you described is to split a multi:true operation into a find and then looping over the cursor and doing a single update for each match.
Is there a way for you to work around this limitation for your package?

Perhaps if you detect multi: true in your before update, do the find loop with individual updates yourself and be sure to return false so the underlying update with multi: true doesn't occur.


DistilBert fails to lower through torch-mlir pass pipeline (illegal ops)

Error output:
error: failed to legalize operation 'torch.aten.view' that was explicitly marked illegal
note: see current operation: %416 = "torch.aten.view"(%414, %415) : (!torch.vtensor<[?,?,768],f32>, !torch.list<int>) -> !torch.vtensor<[?,?,12,64],f32>
Traceback (most recent call last):
  File "/home/ean/SHARK/generate_sharktank.py", line 180, in <module>
    save_torch_model(args.torch_model_csv)
  File "/home/ean/SHARK/generate_sharktank.py", line 68, in save_torch_model
    mlir_importer.import_debug(
  File "/home/ean/SHARK/shark/shark_importer.py", line 163, in import_debug
    imported_mlir = self.import_mlir(
  File "/home/ean/SHARK/shark/shark_importer.py", line 109, in import_mlir
    return self._torch_mlir(is_dynamic, tracing_required), func_name
  File "/home/ean/SHARK/shark/shark_importer.py", line 74, in _torch_mlir
    return get_torch_mlir_module(
  File "/home/ean/SHARK/shark/torch_mlir_utils.py", line 150, in get_torch_mlir_module
    pm.run(mb.module)
RuntimeError: Failure while executing pass pipeline.

Reproduce:

add distilbert-base-uncased,True,hf to tank/pytorch/torch_model_list.csv
run python generate_sharktank.py

@monorimet Could you try with this PR https://github.com/llvm/torch-mlir/pull/1168 .The problem is with dynamic shapes.

Also, you need the latest torch-mlir with this commit https://github.com/llvm/torch-mlir/commit/b1a506624ce64a8f3ae2f878d5d35cd3f0dfae1d

Traceback (most recent call last):
  File "/home/ean/SHARK/generate_sharktank.py", line 222, in <module>
    save_torch_model(args.torch_model_csv)
  File "/home/ean/SHARK/generate_sharktank.py", line 75, in save_torch_model
    mlir_importer.import_debug(
  File "/home/ean/SHARK/shark/shark_importer.py", line 163, in import_debug
    imported_mlir = self.import_mlir(
  File "/home/ean/SHARK/shark/shark_importer.py", line 109, in import_mlir
    return self._torch_mlir(is_dynamic, tracing_required), func_name
  File "/home/ean/SHARK/shark/shark_importer.py", line 74, in _torch_mlir
    return get_torch_mlir_module(
  File "/home/ean/SHARK/shark/torch_mlir_utils.py", line 65, in get_torch_mlir_module
    module = torch_mlir.compile(
  File "/home/ean/SHARK/shark.venv/lib/python3.10/site-packages/torch_mlir/__init__.py", line 217, in compile
    run_pipeline_with_repro_report(mb.module,
  File "/home/ean/SHARK/shark.venv/lib/python3.10/site-packages/torch_mlir/compiler_utils.py", line 73, in run_pipeline_with_repro_report
    raise TorchMlirCompilerError(trimmed_message) from None
torch_mlir.compiler_utils.TorchMlirCompilerError: Lowering TorchScript IR -> Torch Backend IR failed with the following diagnostics:
error: unsupported by backend contract: type '!torch.Device'
note: see current operation: %126 = "torch.constant.device"() {value = "cpu"} : () -> !torch.Device

Didn't try on the given PR but the error is different now. Any ideas?

This seems related to the error @gpetters94 is also having https://discord.com/channels/636084430946959380/742573221882364009/1009709228950294529. It would be useful to dump the MLIR. It's possible that the issue is that we don't have a lowering for an op that takes a !torch.Device as input, resulting in that variable not getting removed.


HTTP parser extension

Hey guys,
Not sure if you'd be interested, but I wrote a small php extension for the mongrel http parser a while back:
https://github.com/dhotson/httpparser-php
.. it might make for a good optional extension. I agree that having a pure PHP default makes a lot of sense however.
I'd be curious to see if it gives much of a boost over the simple implementation you've included. :-)

Thanks for sharing your project and letting us know :+1:
In case anybody feels like implementing this in React, consider looking at #6 first.


⚠ St. Lawrence Global Observatory CKAN has degraded performance

In 91dd193, St. Lawrence Global Observatory CKAN (https://catalogue.ogsl.ca/en/) experienced degraded performance:

HTTP code: 200
Response time: 5621 ms

Resolved: St. Lawrence Global Observatory CKAN performance has improved in 9f56166 after 5 minutes.


Add loading progress / revamped UX for logging

Adds a loading progress when deploying containers (in particular,
pushing..)
Revamps the logging so it's more "modern" and cleaner.

WIP.
Closing https://github.com/redhat-developer/odo/pull/917 in favor of this one since there was a lot of vendoring conflicts.
To test:

Pull the PR
Build the binary
Do odo create nodejs --git https://github.com/openshift/nodejs-ex and odo push

Some considerations when reviewing:

There are some parts of status.go and log.go that I've purposefully left since it's forked from kubernetes/kind GitHub repo.

Note: Failing tests are because of component tests failing...

@cdrage You're going to have to rebase onto master :(

@cdrage Just tried it and the UI/UX is awesome! :+1: from me!
I will hold off from approving until it's been rebased onto master

Phew. That was a lot of rebasing. Hopefully tests pass (they passed locally at least).
Ready for your review @geoand

@cdrage
Also you might want to make some changes to watch e2e https://travis-ci.org/redhat-developer/odo/jobs/458442390#L712 as it expects certain msgs in o/p

@kadel
At the moment if it fails it will output the log (unless I incorrectly updated this...).
TODO:

[ ] Build output when doing verbose
[ ] Add --show-logs parameter for showing build logs

@cdrage I just verified the PR ... Looks awesome!!! ultimate !!!

At the moment if it fails it will output the log (unless I incorrectly updated this...).

you are right, if it fails you can see the logs. That is ok and I really like this, even the fact that by default it is hidden.
But my issue is that if I want to debug what is happening in assemble script I can't as when it succeed I don't have any way to see the log. The output of the build should be always displayed when I run odo push -v 4

:white_check_mark: odo build 552 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/3213db1a11 by @cdrage)

:white_check_mark: odo build 554 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/24229ef7c4 by @cdrage)

:white_check_mark: odo build 556 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/446c44ff7f by @cdrage)

WIP again since I'm implementing changes and trying to get failing tests to pass.

:white_check_mark: odo build 572 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/307e139f28 by @cdrage)

:white_check_mark: odo build 593 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/d2f23bb78e by @cdrage)

@geoand @surajnarwade @syamgk @girishramnani @kadel
Ready for a review :100:

:white_check_mark: odo build 594 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/ee61645eb6 by @cdrage)

:white_check_mark: odo build 604 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/f6d287aa8e by @cdrage)

:white_check_mark: odo build 615 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/cfb916fbca by @cdrage)

:white_check_mark: odo build 622 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/dec2a8981f by @cdrage)

@cdrage I think we need to use log.Successf() in https://github.com/redhat-developer/odo/pull/983/files#r236999201, WDYT?

:white_check_mark: odo build 624 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/606d9fe1a1 by @cdrage)

Two ACK's / approves.
Let's merge this in!


Variantcalls

Added and tested getVarinatCalls() which returns the genotype content.

@siddharthab I have made the required changes and committed/pushed to the repository. Please let me know if I should issue a pull request again!  Thank you.

Thank you so much for making the suggested changes. Your contribution is very appreciated.

thank you @shwetagopaul92 !!

These changes should now be available in bioc-devel repository.

Thank you!
On Tue, Jan 31, 2017 at 2:13 PM, Siddhartha Bagaria <
<EMAIL_ADDRESS>wrote:

These changes should now be available in bioc-devel repository.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Bioconductor/GoogleGenomics/pull/54#issuecomment-276461285,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATtP4WQSHvA0HLJJETZWnkm-um4eU3xHks5rX4fPgaJpZM4LvNtW
.


[mwa-fix-unit-tests] Fix MWA's unit tests and create a GH action that runs the tests on each change of the frontend code

In this PR:

Fix MWA's unit tests
Introduce a Github action that runs unit tests
Introduce COMMIT file for building MWA

looks like the bot is stuck again
/lgtm

/hold

@elenzio9 looks like there are some conflicts. Could you rebase on top of the latest master?

@elenzio9 looks like there are some conflicts. Could you rebase on top of the latest master?

Just rebased!

Thanks!
/lgtm
/hold cancel

/hold

/hold cancel

/lgtm
/approve


OCPBUGS-8235: Guard pod set readiness probe endpoint explicitly

Backporting https://github.com/openshift/cluster-kube-apiserver-operator/pull/1448

/retest-required

/retest-required

/retest-required

/retest-required

/retest

/retest-required

/lgtm
/approve

/label cherry-pick-approved


NonexistentSourceIdException when using output binding

I'm trying to use the Kusto output binding to write data into a Kusto table. However, I'm getting the following exception when trying to use the output binding.
Kusto.Ingest.Exceptions.NonexistentSourceIdException: Failed to query ingestion status for source with ID:'7b2bf49d-d667-44ba-b46a-1057e8392a80'. A source with the provided ID does not exist.
  HResult=0x80131500
  Source=Kusto.Ingest
  StackTrace:
   at Kusto.Ingest.KustoIngestionResult.GetIngestionStatusBySourceId(Guid sourceId)
   at Microsoft.Azure.WebJobs.Kusto.KustoAsyncCollector`1.<IngestData>d__9.MoveNext()
   at Microsoft.Azure.WebJobs.Kusto.KustoAsyncCollector`1.<IngestRowsAsync>d__8.MoveNext()
   at Microsoft.Azure.WebJobs.Kusto.KustoAsyncCollector`1.<FlushAsync>d__7.MoveNext()
   at Microsoft.Azure.WebJobs.Host.Bindings.OutArrayValueProvider`1.<SetValueAsync>d__8.MoveNext() in D:\a\_work\1\s\src\Microsoft.Azure.WebJobs.Host\Bindings\AsyncCollector\OutArrayValueProvider.cs:line 60

  This exception was originally thrown at this call stack:
    Kusto.Ingest.KustoIngestionResult.GetIngestionStatusBySourceId(System.Guid)
    Microsoft.Azure.WebJobs.Kusto.KustoAsyncCollector<T>.IngestData(string, Kusto.Ingest.KustoIngestionProperties, Kusto.Ingest.StreamSourceOptions)
    Microsoft.Azure.WebJobs.Kusto.KustoAsyncCollector<T>.IngestRowsAsync(System.Guid)
    Microsoft.Azure.WebJobs.Kusto.KustoAsyncCollector<T>.FlushAsync(System.Threading.CancellationToken)
    Microsoft.Azure.WebJobs.Host.Bindings.OutArrayValueProvider<TMessage>.SetValueAsync(object, System.Threading.CancellationToken) in OutArrayValueProvider.cs

I'm using the following package reference:
<PackageReference Include="Microsoft.Azure.WebJobs.Extensions.Kusto" Version="1.0.7-Preview" />

Here is my function code:
public record EmbeddingsRequest(string FilePath);

public record EmailEmbedding(string Subject, string Text, IReadOnlyList<double> Embeddings, DateTime Timestamp);

[FunctionName("EmailPrompt")]
public static IActionResult IngestEmail(
    [HttpTrigger(AuthorizationLevel.Function, "post")] EmbeddingsRequest req,
    [Embeddings("{FilePath}", InputType.FilePath, MaxChunkLength = 512)] EmbeddingCreateResponse embeddingsResponse,
    [Kusto("testing", TableName = "EmailEmbeddings", Connection = "KustoConnectionString")] out EmailEmbedding[] output,
    ILogger log)
{
    output = embeddingsResponse.Data.Select(
        d => new EmailEmbedding(
            Path.GetFileName(req.FilePath),
            "TODO: Text chunk",
            d.Embedding,
            DateTime.UtcNow)).ToArray();

    return new OkObjectResult(new
    {
        status = "success",
        count = output.Length,
    });
}

...and my connection string (copied from Kusto Explorer):
"KustoConnectionString": "Data Source=https://test-kusto-cluster.westus2.kusto.windows.net;Initial Catalog=NetDefaultDB;AAD Federated Security=True"

...which corresponds to an actual database in my Kusto cluster.

The error message isn't really helpful, and searching for it online doesn't provide any information. Any ideas what might be causing my problem?

Hello @cgillum, Thanks for reporting the issue. Will have a look as to why there is an issue. Could you in the meanwhile enable streaming on the table using the following command and give it a try again.
.alter table EmailEmbeddings policy streamingingestion enable
Happy to help you on this

I tried running the following command:
.alter table EmailEmbeddings policy streamingingestion enable

However, this resulted in an error:
{
    "error": {
        "code": "BadRequest",
        "message": "Request is invalid and cannot be executed.",
        "@type": "Kusto.Common.Svc.Exceptions.AdminCommandInvalidStreamingIngestionOperationException",
        "@message": "Admin command cannot be executed as streaming ingestion is not enabled.",
        "@context": {
            "timestamp": "2023-06-21T07:06:08.8381158Z",
            "serviceAlias": "TEST-KUSTO-CLUSTER",
            "machineName": "KEngine000000",
            "processName": "Kusto.WinSvc.Svc",
            "processId": 4308,
            "threadId": 6348,
            "clientRequestId": "KE.RunCommand;844172e4-e9fe-4af9-be96-2a0693d9f9af",
            "activityId": "aa4c838d-92e3-4738-9b77-5659081664f8",
            "subActivityId": "c8a1aa30-169d-447b-90cd-f1fd1abb0617",
            "activityType": "DN.AdminCommand.TableStreamingIngestionPolicyAlterCommand",
            "parentActivityId": "2cb556c7-0c8a-4f37-b13c-c7dc943600fa",
            "activityStack": "(Activity stack: CRID=KE.RunCommand;844172e4-e9fe-4af9-be96-2a0693d9f9af ARID=aa4c838d-92e3-4738-9b77-5659081664f8 > DN.Admin.Client.ExecuteControlCommand/047dba49-c2c7-4639-a181-5617a057beff > P.WCF.Service.ExecuteControlCommand..IInterNodeCommunicationAdminContract/f55aed45-614f-466a-85ec-54a235e21794 > DN.FE.ExecuteControlCommand/2cb556c7-0c8a-4f37-b13c-c7dc943600fa > DN.AdminCommand.TableStreamingIngestionPolicyAlterCommand/c8a1aa30-169d-447b-90cd-f1fd1abb0617)"
        },
        "@permanent": true
    }
}

Also, assuming here that you have App id / Key passed in the actual connection string as well.

I don't have App ID or Key in my connection string. I assumed that my user identity would be used since I'm running the function app locally with my own credentials. Could this be an auth issue? I tried adding Authority Id and User ID as shown below, but got the same exception.
"KustoConnectionString": "Data Source=https://test-kusto-cluster.westus2.kusto.windows.net;Initial Catalog=NetDefaultDB;Fed=True;Authority Id=xxx;User ID=cgillum@xxx"

Hello @cgillum
Thanks for the reply. It could be an Auth issue
It could be an auth issue too, though the traces do not suggest that. Right now, we do not support User Id
There are 2 options, either to use an App Id / App Key
Data Source=https://test-kusto-cluster.westus2.kusto.windows.net;Database=testing;Fed=True;AppClientId=<APP-ID>;AppKey=<APP-KEY>;Authority Id=<TENANT>
(or)
We can use Managed Identity if running from the portal (We'd have to create a managed identity with ingest privileges and then attached in the Annotation)
As for streaming, it can be enabled from the portal (this is only if the Auth is not working)

and then .alter table EmailEmbeddings policy streamingingestion enable

@ag-ramachandran enabling streaming worked! I was able to use the output binding successfully and query my data in Kusto Explorer.
Do the output bindings always require streaming ingestion to be enabled for the cluster and database?

@ag-ramachandran does the fix work ? I am facing the same issue. is the only work around to enable streaming?

Hello @OlajideOgun, we did have regressions run against it. Will check it again. Quick q : Are you running this against Fabric/Synapse clusters

Hello, experiencing the same issue. Do you guys plan to make this output binding work with streaming turned off? Thank you.

@skorunka , Here was the consideration we had in this case.

Most of usage we see wrto ingest is with a few rows at best (large memory and time intensive operations are not great fitment for serverless scenarios)
Queued ingest is not really well suited for this scenario due to latency (refer aggregation policies) and also "large number of small blobs" or the fragmentation scenario
Streaming adds a little more CPU & was ideally suited for these scenarios

Changing from managed streaming to queued is not very hard to accomplish, if there are use cases that fit this case, it is something we could consider.
If you have a specific scenario that you'd like to use Queued with , happy to talk at ramacg @ .com

Hi @ag-ramachandran, the only concert I have is cluster price. I got impression when the streaming is enabled the cluster costs more money, or am I wrong?
My use case is to actually ingest messages read from the IoT Hub right into Kusto table.
I was not able to make the IoT Hub Data connection on Kusto database working, so I decided to build the AzF that does that, and found this output binding that works quite nice.
Thank you.

@skorunka , Streaming is part of the ADX BOM. No additional billing will entail if you enable it. It does take some additional cluster resources, but does not impact cost.
If you are in need of troubleshooting IoT hub connection (direct) , please let us know my email is above. Can get it directed at the right colleagues


projections fixes

changes:

fix issue when merging projections from multiple-incremental persists which was hoping that some 'dim conversion' buffers were not closed, but they already were (by the merging iterator). fix involves recreating the merging iterator to rebuild the dim conversions, which is sad, but maybe better than keeping the buffers open for the entire lifetime of the segment writeout
fix queryable index projection to not put the time-like column as a dimension, instead only adding it as __time

closing in favor of #17460


Mixing in EventEmitter2

The native Node.js EventEmitter can be mixed in or used as inheritor for other objects. Using the constructor of EventEmitter2 to initialize and setup some of the basic properties prevents that from being possible (as far as my knowledge goes).
In the examples in the documentation you are using EventEmitter2 as the base object to "create" a new server, this however is not a real server but just an EventEmitter so that's why you probably haven't run into this issue yet :)
Looking into the core API's of Node.js, the native EventEmitter is inherited with a utility function to basically copy it's properties / functions to the other object. For an example see:
https://github.com/joyent/node/blob/master/lib/http.js#L1142
I would like to be able to do this with EventEmitter2 as well.
Do you agree if I fix EventEmitter2 so it can be used as the native EventEmitter and be mixed in with other objects using the utility function?

Still not working for me.
var EventEmitter2 = require('eventemitter2').EventEmitter2;

function Backend(endpoint, http, ws) {
  EventEmitter2.call(this);

  this.endpoint = http;
  this.http = http;
  this.ws = ws;
}

module.exports = Backend;

var Backend = require('../../src/backend');
var backend = new Backend();
console.log(typeof backend.on);
// -> undefined

Anyway this is is a quite common use case, definitely consider to document it at least.

I ran into this too. I was looking to "upgrade" from EventEmitter to EventEmitter2 because of the onAny support but my code uses util.inherits. It's not a problem to refactor my code, but it caught me by surprise as I was expecting a drop-in replacement.


Docu: correct several links after renaming default branch (master to main)

Merged. Thank you for the contribution!


It would be nice to be able to make assertions on the properties of entities in the dataset

Is your feature request related to a problem? Please describe.
when only a portion of entities in a dataset have a particular value, it's easy to write a crawler in a way where you don't realise a value has been dropped, e.g. because of a typo, or because the source has changed.
e.g.

a typo in the xpath to get a detail URL fails to look up the href properly, so we keep adding None to the sourceUrl property

Describe the solution you'd like
a way to say that an expected proportion of entities have some value, or even a specified number of values, for a given property
e.g.
assertions:
  min:
    schema_entities:
      Person: 1000
    schema_properties:
      Person:
        name: 100  # this should perhaps be redundant because it's a required field
        sourceUrl: 100  # all entities are expected to have a
        nationality: 80  # 80% of entities are expected to have a value for nationality
      Sanction:
        endDate: 1  # at least 1% of sanctions are expected to be inactive

It could also be useful to specify which values are expected (e.g. which topics), or how many (e.g. 2 URLs per sanction), but this may be out of scope of a first iteration.
Describe alternatives you've considered
None
Additional context
None

FWIW this is a really cool proposal and I'd love to see it implemented!


componentWillMount is deprecated now

See https://reactjs.org/docs/react-component.html#unsafe_componentwillmount

Thank you for this doug. I know what to do now.


webM alpha transparency

webM alpha transparency

This issue was imported from Google Moderator
Moderator votes: +8
Issue added by aerin on 2015-02-04
To vote this issue up or down, simply include +1 or -1 in your comment.

+1

Here's some more info about transparency within the webm format itself: https://developers.google.com/web/updates/2013/07/Alpha-transparency-in-Chrome-video?hl=en
Here's a test page, showing off embedded webm videos with transparency: https://simpl.info/videoalpha/
Finally, here's a direct link to a webm video with transparency: https://simpl.info/videoalpha/video/dancer1.webm
The link above says it works since Chrome 31. I'm on FireFox 70.0.1 where it also works perfectly.


Test failure: TestRun/Without_ptr:_only_non-ptr_methods

I'm working on packaging this library for Debian, and have encountered a test failure when building.
    --- PA|^[[0m
                          ^[[0;31m 00000050  53 53 3a 20 54 65 73 74  52 75 6e 2f 57 69 74 68  |SS: TestRun/With|^[[0m
                          ^[[0;31m 00000060  6f 75 74 5f 70 74 72 3a  5f 6f 6e 6c 79 5f 6e 6f  |out_ptr:_only_no|^[[0m
                          ^[[0;31m 00000070  6e 2d 70 74 72 5f 6d 65  74 68 6f 64 73 2f 54 65  |n-ptr_methods/Te|^[[0m
                          ^[[0;31m 00000080  73 74 33 20 28 30 2e 30  30 73 29 0a              |st3 (0.00s).|^[[0m
                          ^[[0;31m}^[[0m
        ^[[1;32m        expected: ^[[0;32mContains("Run(): several methods are not accessible as suite is not a pointer but tdsuite_test.FullNoPtr: PostTest, Test2")^[[0m
        [under operator Contains at suite_test.go:211]
        This is how we got here:
                TestRun.func3() helpers/tdsuite/suite_test.go:210

[snip]

    --- FAIL: TestRun/Without_ptr:_only_non-ptr_methods (0.00s)
        --- PASS: TestRun/Without_ptr:_only_non-ptr_methods/Test1 (0.00s)
        --- PASS: TestRun/Without_ptr:_only_non-ptr_methods/Test3 (0.00s)

Hi, interesting. It only happens when tests are launched with -v flag.
I will have a look at it and come back soon.
Thanks for the report.

@gibmat I will publish a new release ASAP.

Done → v1.14.0.

Awesome, thanks for the quick fix!


Add option to download all textures with one click

For atlases with a lot of textures, it's really tedious to download them one by one. It might be nice to use jsZip or something similar to combine all the textures into one easy download.

My hacky solution to not have to click endlessly was to write a few lines of JS to automatically click every link. If anyone else wants it, just open your browser's dev tools and paste this in the JS console:
var links = document.querySelectorAll("#destContent a");
var i = 0;
function clicky() {
  links[i++].click();
  if (i < links.length) { setTimeout(clicky, 100); }
}
clicky();

If you wanted, you could actually just add a "Download All" button that calls my code; it'd just be a bit janky.

done


Update democracy pallet

Our fork is severely outdated, we should review the changes here and update our democracy pallet. Most notably we need to integrate the preimage pallet directly, remove enact_proposal and note_preimage.

Related: https://github.com/interlay/interbtc/pull/517


dialect/sql/schema: support time with time zone and time without time zone

Fix #2244
8.5. Date/Time Types
https://www.postgresql.org/docs/14/datatype-datetime.html

Great! Thanks @s-takehana for the contribution 🙏


New advanced client

Also NewHTTPClientFromConfig seems overkill since it's only used twice
tests/riot.go
279:	client, err := client.NewHTTPClientFromConfig(cConf)

cmd/client.go
69:		client, err := client.NewHTTPClientFromConfig(clientCtx.config)

Also NewHTTPClientFromConfig seems overkill since it's only used twice
tests/riot.go
279:	client, err := client.NewHTTPClientFromConfig(cConf)

cmd/client.go
69:		client, err := client.NewHTTPClientFromConfig(clientCtx.config)

The client is also intended to be used outside QED project. I prefer to make the client's construction more flexible.


KOGITO-4431 - Fix native build pom

JIRA: https://issues.redhat.com/browse/KOGITO-4431
Additional PRs:
kogito-apps: https://github.com/kiegroup/kogito-apps/pull/646
kogito-examples: https://github.com/kiegroup/kogito-examples/pull/492
Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[x] You have read the contributors guide
[x] Your code is properly formatted according to this configuration
[x] Pull Request title is properly formatted: KOGITO-XYZ Subject
[x] Pull Request title contains the target branch if not targeting master: [0.9.x] KOGITO-XYZ Subject
[x] Pull Request contains link to the JIRA issue
[x] Pull Request contains link to any dependent or related Pull Request
[x] Pull Request contains description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket

The Linux check has failed. Please check the logs.


bug: query plan fails resolve dependencies

for example for following schema, user field is dependent on the userId field.
schema
  @server(port: 8000)
  @upstream(baseURL: "http://jsonplaceholder.typicode.com", httpCache: 42, batch: {delay: 100}) {
  query: Query
}

type Query {
  posts: [Post] @http(path: "/posts")
}

type User {
  id: Int!
  name: String!
}

type Post {
  id: Int!
  title: String!
  userId: Int @http(path: "/users/1", select: "{{.id}}")
  user: User @http(path: "/users", query: [{key: "id", value: "{{.value.userId}}"}], batchKey: ["id"])
}

logs:
 INFO File read: ./examples/jsonplaceholder.graphql ... ok
 INFO N + 1 detected: 1
 INFO 🚀 Tailcall launched at [<IP_ADDRESS>:8000] over HTTP/1.1
 INFO 🌍 Playground: https://tailcall.run/playground/?u=http://<IP_ADDRESS>:8000/graphql&utm_source=tailcall-debug&utm_medium=server
 INFO GET http://jsonplaceholder.typicode.com/posts HTTP/1.1
 INFO GET http://jsonplaceholder.typicode.com/users/1 HTTP/1.1
 INFO GET http://jsonplaceholder.typicode.com/users?id HTTP/1.1

Query Plan should be able to figure out which operations are dependent and which are independent. Independent operations can be executed in parallel manner.

Let's throw a validation error for now.