Cannot read property 'timestamp' of undefined

Hi.
Zipkin UI starts with error
error_handler.js?934c:54 EXCEPTION: Cannot read property 'timestamp' of undefined ErrorHandler.handleError @ error_handler.js?934c:54 error_handler.js?934c:59 ORIGINAL STACKTRACE: ErrorHandler.handleError @ error_handler.js?934c:59 error_handler.js?934c:60 TypeError: Cannot read property 'timestamp' of undefined     at eval (webpack-internal:///165:117:70)     at Array.sort (native)     at Array.sort (webpack-internal:///875:21:15)     at Trace.sortTrace (webpack-internal:///165:117:23)     at eval (webpack-internal:///165:120:23)     at Array.forEach (<anonymous>)     at Trace.sortTrace (webpack-internal:///165:119:27)     at eval (webpack-internal:///165:120:23)     at Array.forEach (<anonymous>)     at Trace.sortTrace (webpack-internal:///165:119:27)     at Trace.getSortedSpans (webpack-internal:///165:80:14)     at new Trace (webpack-internal:///165:55:32)     at eval (webpack-internal:///165:157:65)     at Array.map (<anonymous>)
If i understand correctly expected structure of traces (response of api/v1/traces) is ..{"traceId": "trace", ..., "**annotations**"} .. - annotations is mandatory.
But in my case trace looks like [     [         {             "traceId": "fca49abacae88255",             "id": "fca49abacae88255",             "name": "",             "timestamp":<PHONE_NUMBER>447000,             "duration": 55875,             "annotations": [                 {                     "timestamp":<PHONE_NUMBER>502875,                     "value": "ss",                     "endpoint": {                         "serviceName": "",                         "ipv4": "",                         "port": 8080                     }                 }             ]         },         {             "traceId": "fca49abacae88255",             "id": "8382a3fc6365f507",             "name": "",             "parentId": "fca49abacae88255",             "timestamp":<PHONE_NUMBER>455000,             "duration": 22310,             "binaryAnnotations": [                 {                     "key": "OUTPUT_MESSAGE",                     "value": "",                     "endpoint": {                         "serviceName": "",                         "ipv4": "",                         "port": 8080                     }                 },                 {                     "key": "lc",                     "value": "unknown",                     "endpoint": {                         "serviceName": "",                         "ipv4": "",                         "port": 8080                     }                 }             ]         }     ] ]
"Traditional" ui works fine with that trace

Sounds familiar to me.. are you running latest?
On 4 Nov 2017 00:32, "lhsm"<EMAIL_ADDRESS>wrote:

Hi.
Zipkin UI starts with error
error_handler.js?934c:54 EXCEPTION: Cannot read property 'timestamp' of
undefined ErrorHandler.handleError @ error_handler.js?934c:54
error_handler.js?934c:59 ORIGINAL STACKTRACE: ErrorHandler.handleError @
error_handler.js?934c:59 error_handler.js?934c:60 TypeError: Cannot read
property 'timestamp' of undefined at eval (webpack-internal:///165:117:70)
at Array.sort (native) at Array.sort (webpack-internal:///875:21:15) at
Trace.sortTrace (webpack-internal:///165:117:23) at eval
(webpack-internal:///165:120:23) at Array.forEach () at
Trace.sortTrace (webpack-internal:///165:119:27) at eval
(webpack-internal:///165:120:23) at Array.forEach () at
Trace.sortTrace (webpack-internal:///165:119:27) at Trace.getSortedSpans
(webpack-internal:///165:80:14) at new Trace (webpack-internal:///165:55:32)
at eval (webpack-internal:///165:157:65) at Array.map ()
If i understand correctly expected structure of traces (response of
api/v1/traces) is ..{"traceId": "trace", ..., "annotations"} .. -
annotations is mandatory.
But in my case trace looks like [ [ { "traceId": "fca49abacae88255",
"id": "fca49abacae88255", "name": "", "timestamp":<PHONE_NUMBER>447000,
"duration": 55875, "annotations": [ { "timestamp":<PHONE_NUMBER>502875,
"value": "ss", "endpoint": { "serviceName": "", "ipv4": "", "port": 8080 }
} ] }, { "traceId": "fca49abacae88255", "id": "8382a3fc6365f507", "name":
"", "parentId": "fca49abacae88255", "timestamp":<PHONE_NUMBER>455000,
"duration": 22310, "binaryAnnotations": [ { "key": "OUTPUT_MESSAGE",
"value": "", "endpoint": { "serviceName": "", "ipv4": "", "port": 8080 } },
{ "key": "lc", "value": "unknown", "endpoint": { "serviceName": "", "ipv4":
"", "port": 8080 } } ] } ] ]
"Traditional" ui works fine with that trace
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/openzipkin/zipkin/issues/1776, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAD616WWw622R1AtIeZP9qqGzGAhpn5zks5sy0A0gaJpZM4QRW0q
.

Same issue here with the latest version of openzipkin/zipkin-ui docker image

This could be a bug, when all labels are empty or unknown. Is it
intentional that you have a trace with no service or span name?
On 14 Nov 2017 7:01 am, "Bruno Bonfils"<EMAIL_ADDRESS>wrote:

Same issue here with the latest version of openzipkin/zipkin-ui docker
image
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/openzipkin/zipkin/issues/1776#issuecomment-344088689,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAD6159pOJVbkTzImtR9JRXUmuXvaxiMks5s2MpJgaJpZM4QRW0q
.

oh you are referring to https://github.com/openzipkin/zipkin-ui
someone can fix the bug, but the project is likely to be canceled because no one has been maintaining it.. see also https://github.com/openzipkin/zipkin/issues/1577 and https://github.com/openzipkin/docker-zipkin/issues/160
At any rate, this issue should be moved to https://github.com/openzipkin/zipkin-ui

Sorry, i mixed up the target project. Create one https://github.com/openzipkin/zipkin-ui/issues/42 just in case
Thanks


fasm2bels IO settings from EBLIF

This PR adds the functionality to fasm2bels that reads IOSTANDARD and DRIVE parameters from EBLIF file and applies them to IO buffers.
The mapping between EBLIF cells and IO buffers decoded from fasm is done through top-level port names and locations read from a PCF file. Therefore both EBLIF and PCF files need to be provided.

fasm has support for annotations -> https://github.com/SymbiFlow/fasm/blob/master/docs/specification.rst#annotations -- these type of things are probably a good use of them?

@mithro But that won't help much. The problem is that the actual IOSTANDARD and DRIVE cannot be unambiguously decoded from the fasm / bitstream. And since the fasm is created from the bitstream there is nothing reliable to annotate it with. What we need is a way to pass the information from the design to fasm2bels so it can set these parameters accordingly.
Right now it is a separate JSON file. But as fasm2bels can use eblif for other things we can pass the parameters in there.

I've updated the PR and fixed some bugs as well. These are the IOSTANDARD test results I'm getting on my machine:
For diff_output_arty-full_DIFF_SSTL135, output_arty-full_LVCMOS15, output_arty-full_LVCMOS25 and output_arty-full_LVCMOS33.

Failure related to https://github.com/SymbiFlow/symbiflow-arch-defs/issues/1239

For inout_arty-full_LVCMOS18 and output_arty-full_LVCMOS18

Incorrect handling of the PUDC_B special pin site. I've created an issue for that: https://github.com/SymbiFlow/symbiflow-arch-defs/issues/1263

The test for single ended SSTL135 results in unknown bits. See https://github.com/SymbiFlow/prjxray/issues/1182
The rest of the tests passes correctly with the IOSTANDARD and DRIVE passed from Yosys to EBLIF and decoded from it by fasm2bels.

I'm unclear, are the failing cases present and disabled, or simply not present?  Should we add the failing cases and comment them out?

@litghost All of them are enabled. When the CI finishes I hope to see the same failures as on my local machine.

Looks like some of the DRAM tests started failing, unclear why.  Can you replicate that?


Implement trustboost as an ibctest example

this could be fun for the right engineer
https://github.com/trustboost/TrustBoost

closing as trustboost looks unmaintained


fix: display certs on profile for username with upper chars

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

We got a report in the support inbox recently that pointed out a bug with usernames that include uppercase characters.
Currently, if your username has uppercase characters in it and you visit your public profile while signed in, you can't view any certifications you claimed.
Here's what I see after changing my username to ScissorsNeedFoodToo:

But this doesn't affect viewing profiles while signed out. Here's what that section of my profile looks like in an incognito window:

This PR is more of a quick fix for this specific issue -- it doesn't handle other cases where it might be better to differentiate between username and usernameDisplay, like viewing a public profile for another user whose username includes uppercase characters.
These changes also include some refactoring of existing Cypress tests to use commands to make it easier to update the username in new tests.

I poked at this a bit today, Kris, and I think the api is the culprit.  In https://github.com/freeCodeCamp/freeCodeCamp/pull/43667 we changed the api to return the value of username as usernameDisplay if it can.  It makes sense to make usernameDisplay default to username, but not the other way around. Also, usernameDisplay is not returned.  Oops, basically.
What do you reckon?

Hey @ojeytonwilliams, thanks for your review, and for catching that Cypress anti-pattern. I'd be happy to go in and fix that with data-cy attributes.
Also, I was considering hardcoding the number of certs there, but I wasn't sure if that was the best approach. At the time I thought it would be another thing to change, but now that you mention it, it's unlikely we'll update the certified user every time a new cert is released. I'll go ahead and add in the number of expected certifications.
About the username and usernameDisplay, I did notice them being used interchangeably at times. I don't think it's a huge problem, but it might be easier overall to better differentiate between the two.
I agree that it makes sense to default to usernameDisplay if it exists and if it's really just for display like on the public profile page, and to user username for things like querying the db where we need to know for sure that all the characters are lowercase.

Hey @ojeytonwilliams, thanks again for your earlier review.
I went in and made those changes. Also, I went ahead and added a couple more data-cy attributes for the goToSettings Cypress command as well.

Also, I was considering hardcoding the number of certs there, but I wasn't sure if that was the best approach. At the time I thought it would be another thing to change, but now that you mention it, it's unlikely we'll update the certified user every time a new cert is released. I'll go ahead and add in the number of expected certifications.

Yeah, I agree. I don't hate the idea of updating the certified user, though, even if we do have to update the tests.  It's nice to confirm that all the buttons appear and, in general, to have a user that's done everything.

About the username and usernameDisplay, I did notice them being used interchangeably at times. I don't think it's a huge problem, but it might be easier overall to better differentiate between the two.

That's only not a huge problem when username is used for usernameDisplay, the other way around is pretty bad because of how we select the user from the redux store.
That said, how about we get this fix in now and I create another PR to update the API, so we can QA that more thoroughly? It could have weird side-effects, after all.


Cmake3

I think the cmake changes themselves are fine, and a really good addition.
If there's some coordination with VFXPlatform that involves consensus for their adding cmake >= 3.11 to their CY2019 list, then I withdraw all my objections. But assuming that is not immediately forthcoming...
I'm worried about the requirement for CMake 3.11.  Personally, in an ideal world, I'm all for moving every package under the sun to CMake 3.12 (released yesterday!). But at a real studio, I'm worried about whether that will create a whole lot of hassle and burden on the people who need to build OpenEXR (and Imath, which may be used even more widely as a dependency).
Just as an illustrative example, at my work we have CMake 3.2 (I think) installed, which itself is quite a bit newer than the default cmake 2.8 that comes standard with the CentOS 7 flavor we're on right now. A sudden requirement for 3.11 would make a bit of a kerfuffle, since at the major studios these days, it's not a matter of just building or installing a new package like in the wild west -- upgrading a package facility-wide involves various levels of security approvals and whatnot. (If any of you are employed by the one or two companies primarily responsible for imposing this constant background of added friction on the rest of the industry: Grrrr, dammit.)
I think the reason you moved to such an aggressively new cmake requirement is because there are various cmake vs boost vs windows considerations that were only fixed with 3.11. Is that correct?
My suggestion would be -- keeping in mind that VFX Platform is thus far entirely mute about Windows matters -- that you should make a more moderate "requirement" based on what actual cmake syntax you require (I don't see anything in there that I think shouldn't work with 3.2 or so). But perhaps add a clause in the file that just when building on Windows, will issue a warning or error if cmake version is older than the one known to have fixed the problems you're worried about.
I sympathize and frankly feel a little dirty suggesting different cmake requirements on different platforms. But in my mind, this needs to be weighed against the extra hassle for everybody if you make the developers who have to use openexr source have to butt heads unnecessarily with their systems and security teams.

Thanks for the feedback.
Yes, boost + python + windows has been a nightmare since the release of VS2017, resolved only by 3.11
It's an omission that vfxplatform doesn't specify cmake, I'd say. Vfxplatform's mission is to specify versions of things where version skew causes difficulties, and CMake is a very high qualifier for that bar.
3.0 is I believe the minimum required for the syntax used.
My experience thus far, is that not requiring a minimum version on Windows is going to cause a sporadic flurry of support questions in various forums as people who aren't cmake experts tear their hair.
--- suggestions for cmake version ---

Make the minimum platform dependent, as it would prevent Windows developers' first attempt at OpenEXR being a frustrating one.

raise CMake version with the vfxplatform

The intent of the options in the outermost file is that you can build the components individually, although it hadn't occurred to me that one might have IlmBase already installed, and then do a separate build for OpenEXR.
--- suggestion for build methodology ---

add an option for building IlmBase independently
factor the code such that CMake could be invoked in the root with options, or in the individual subdirectories as previously.

That's probably best of both worlds; a friendly build option that doesn't require a CMake PhD, and a detailed build option to accommodate scenarios like what you describe.

There has already been some discussion on VFX Platform mail list about adding CMake (I may even be the one who first raised the issue, and it seemed to have good support from the onlookers). But they tend to be pretty conservative about version choices and my intuition is that requiring 3.11 will be an uphill fight. I think your plan is good and I'll help back it:

Use 3.0-3.2 syntax/features in OpenEXR, but just for Windows require 3.11 minimum and explain why.
Aim to get a CMake included in VFXPlatform this year at a level that can get broad consensus in time to be included and not create a hassle for the studios (I'm pushing for at least 3.2, because that's the level both of my packages currently consider a minimum).
In future years, try to push VFX Platform to upgrade its CMake requirements to a level that is known to work well across all platforms (even those not addressed by VFX Platform).

@meshula By chance, would you be able to incorporate the GNUInstallDirs, Pkg-Config (like separate .pc files), and other fixes I have in this PR: https://github.com/openexr/openexr/pull/242?

What's the current status of #242? I see @SoapGentoo made a bunch of suggestions, but I'm unclear if they've been incorporated in the PR?

@meshula I think I need to read over it again as I've been away for awhile, but it's mostly ready right now.

@dracwyrm pkg-config can be used on Windows, it just isn't very popular or idiomatic there. Windows users prefer those .cmake/.config files instead (which are imo an anti-pattern, but ok)

My opinion is that the cleanest thing would be to install the pkg-config files on windows if pkg-config is requested as an option.

the cleanest thing would be to install pkgconfig unconditionally. If people don't need it, they can delete the file.

@SoapGentoo I guess I misunderstood when I heard that Pkg-Config wasn't for Windows.
I currently use checks to see if there is Pkg-Config and to install, is that fine, or just should install by default?

My preference is to not install unused things; that's the point of configuration. pkg-config is not used in Windows installations of other vfx libraries, so OpenEXR is an outlier currently. I do imagine that MinGW users would potentially get benefit from pkg-config. For sure Visual Studio users will not.
@SoapGentoo I hear what you are saying about cleanliness. If you have a look at https://github.com/openexr/openexr/pull/305 you can see there is currently a refactor of the CMake system in progress that introduces a more rigorous options/configuration system. Have pkg-config as an option would be consistent with the refactor.

@meshula Thanks, these changes look good.  @lgritz I agree with you about version requirements, however there's no plan to remove the existing autoconf/automake build system - it's what all the distribution packages use to build with, and has no external dependencies.  If this makes it better for folks on windows, I don't see much of a problem, particularly if it the windows build doesn't work well with earlier versions of cmake anyways.

Resolved manually against top of tree.


Use servant's HasForeignType

Nice. I haven't tried this out yet, but great that Servant 0.5 is out with the necessary machinery for this built in. I'm probably not going to get chance to test this much before it gets merged, since I don't have an active project to use as a guinea pig.

Yay!


Pages not rendering correctly

Hey, I just tried to get started with portia, booted up the docker image nice and easy, but the resulting portia instance isn't rendering web pages very well.
To example product pages:
https://www.zara.com/us/en/woman/new-in/tropical-print-jumpsuit-c805003p4712067.html?ts=1495559534372
in this case, it doesn't render images or the price of the item

and
http://www.patagonia.com/product/mens-lightweight-synchilla-snap-t-fleece-vest/25500.html?dwvar_25500_color=OKSB&cgid=mens-fleece#tile-1=&start=1&sz=24
on this one we get the price, but not the images.

I can't find anything in the documentation about improving the rendering quality for a page, but that certainly doesn't mean it isn't there... can anyone point me in the right direction?

After doing some more reading, it looks like this is probably a Splash issue, not directly Portia. Does that seem right? Is there any way to get Portia to use a different rendering engine like phantomJS/selenium?


Verticle Slabs Texture not working

For some reason, no idea why, the texture is utterly broken for all wooden slabs (oak, spruce, warped, etc.) while all others work perfectly fine.
I am using other mods and maybe I had something installed that messed up the texture, so I will also include a screenshot of the mods and libs installed

This is SO bizarre

Hello,
I ran into the same rendering issue while trying out the mod. All the wooden slabs would appear glitched as you have posted whenever I ran any shaders. It would render normally without any shaders on.
The fix I found was the following; in the config file of the mod, you will find an option for lazy vertical slabs. Remove the wooden slabs from there as shown below, and it might fix the rendering issue. It did for me.
Cheers!

Thanks for the fix! Much appreciated!!

In your minecraft folder, you will find a config folder as shown below:

In the config folder, you will find the double slabs client config file in .toml format, as shown below:

Open it using an editor (I used notepad++), and do the edit I had mentioned earlier. And voila!
Hope this works for you too!
Cheers!

Hi there! Apologies for the delay but I believe that this is fixed in the latest version :) For now it is only for 1.16 but I will be backporting to older versions as soon as I can :)


gql import

When typescript code is generated, there is a duplicate defn of gql which is giving me compilation error
My config file is attached.
=========================================================
import { GraphQLResolveInfo } from 'graphql';
import * as Apollo from '@apollo/client';
import gql from 'graphql-tag';
export type Maybe = T | null;
export type Exact<T extends { [key: string]: unknown }> = { [K in keyof T]: T[K] };
export type RequireFields<T, K extends keyof T> = { [X in Exclude<keyof T, K>]?: T[X] } &
{ [P in K]-?: NonNullable<T[P]> };
const gql = Apollo.gql;
/** All built-in and custom scalars, mapped to their actual values */
========================================================
codegen.yml
overwrite: true
schema: 'src/Views/Schema/.graphql'
documents: 'src/**/.gql'
generates:
src/Views/Gql/graphql.ts:
plugins:
- 'typescript'
- 'typescript-operations'
- 'typescript-react-apollo'
- 'typescript-resolvers'
- 'typescript-document-nodes'
config:
namePrefix: 'gql'
typesPrefix: I
withMutation: true
withHOC: false
withHooks: true
withRefetchFn: true
withComponent: false
reactApolloVersion: 3
withResultType: true
withMutationOptionsType: true
useIndexSignature: true
namingConvention:
typeNames: pascal-case#pascalCase
enumValues: upper-case#upperCase
hooks:
afterOneFileWrite:
- prettier --write

seems that new version of apollo-angualr has a built in gql that should be used.
import {gql} from 'apollo-angular';

Working on it. Which plugins version do you use?

Hi @ddehghan !
typescript-react-apollo and typescript-document-nodes doesn't play nice together, since they are conflicting and generates similar output.
The typescript-document-nodes already generated the pre-compiled documents for you.
The v2 of typescript-react-apollo should take care of the gql import, and you can use documentMode: documentNode to have a pre-compiled DocumentNode just like  typescript-document-nodes outputs.
Closing. Please add more information (exact packages versions, reproduction in codesandbox) if you think it's still relevant.

I was using the following packages
"@graphql-codegen/cli": "^1.17.7",
"@graphql-codegen/typescript": "^1.17.7",
"@graphql-codegen/typescript-document-nodes": "^1.17.7",
"@graphql-codegen/typescript-operations": "^1.17.7",
"@graphql-codegen/typescript-react-apollo": "^2.0.5",
"@graphql-codegen/typescript-resolvers": "^1.17.7",
But the latest version 1.17.8 have solved the problem.

It should be fixed by<EMAIL_ADDRESS>


Implement Semantic Release

Add Semantic Release to automate versioning and management
https://github.com/semantic-release/semantic-release

I'd like to work on this issue

hey @Azanul when implementing can you check out all of the configuration added here including the GitHub Action and .releaserc? https://github.com/colbyfayock/netlify-plugin-cloudinary
I'm open to changes as this its the first project I've used it on (it was added as a contribution with changes I had to additionally make), so interested to hear if you hvae any ideas for improvements, otherwise we can implement it the same, thanks

@colbyfayock , Checkout the PR. I haven't changed much. But I think moving forward keep these two issues in our mind semantic-release issue #2351 and semantic-release issue #2584.

interesting, thanks for the heads up


<= X parsed as X

I was trying this in cargo: >= 0.1, <= 0.2. It's not valid syntax, but it is accepted without error. Output suggests it was interpreted as >= 0.1, 0.2.
(>= 0.1, < 0.3 ended up being what I wanted).

It's not valid syntax,

What's not valid about this?

Not sure why I said that, maybe because the <= operator was not listed in crates.io docs. http://doc.crates.io/specifying-dependencies.html
It seems like the version spec in the issue is working as indended when I try it now, maybe this was a mistake.

Okay! I'm gonna just give this a close then.


Add Cell Line Prediction Analysis

Adding a notebook that applies the Ras Classifier Predictions to two Cell Line Datasets

@dhimmel - particularly interested in your expertise with data usage/licensing and data visualization in this PR

PR ready for review again @dhimmel - I updated one of the cell line figures to include just one dimension.
I also added some minor changes to the ras figure script, since this is included in updates to figure 3


[Suggestion] Add Better Combat support

Hi! I'd love to use this in my modpack, but I use Better Combat and it wouldn't work well to add a weapons mod to it if doesn't support Better Combat.

Hi! I am only aware of this incompatibility that I fixed over at Better Combat: https://github.com/ZsoltMolnarrr/BetterCombat/pull/378
But apart from that, everything else should work fine. Please let me know if you find another bug that needs fixing.


Can't hotload config file if it is a symlink

Great project! I'm on Mac OSX 10.11 and using skhd to control chunkwm.
If ~/.skhdrc is a symlink, then it can't hotload the config file, and I have to do brew services restart skhd to see the changes. If ~/.skhdrc is a regular file, hotloading works just fine.

implemented support for symlinks on master.

This does not seem to work when the symlink is relative, e.g. as created by GNU Stow.

What's the expected behaviour when the symlink is relative? We have to pass the absolutepath to the FSEvents API.
My first assumption would be that we just prepend getenv("HOME") to the path returned by the symlink resolver if it is a relative symlink(?). I've never used GNU Stow and I don't know how it works.

:+1: to realpath, though I think in the GNU Stow case, prepending getenv("HOME") would work too. I'll try out your change and let you know how I fare. Thanks for the patch, and the project in general, and for chunkwm!

e616840 seems to enable hotloading only if ~/.skhdrc is a real file or an absolute symlink on startup of skhd. After that, I can swap it for the relative symlink and everything works great.

Is hotloading still supported on latest macOS?
I've installed skhd using Brew, and have the service running. Inspecting the launchctl plist shows hotloading isn't disabled, but editing my config file still does not update the running daemon.
skhd --reload works as expected.
My config is symlinked to $XDG_CONFIG_HOME/skhd/skhdrc (the result is an absolute symlink). The directory is symlinked, not the file itself.

Hotloading is still a thing yes. I have not tested having an actual file in a symlinked directory, so that is probably why it is not working for you. You can run skhd with the --verbose flag and it should print the path to the file it resolved for the hotloader.

Thanks for the pointer @koekeishiya. I suspect you are right that this use-case is unsupported.
This is what it prints:
skhd: watching files for changes:
	/Users/jean/.config/skhd/skhdrc

The /Users/jean/.config/skhd directory is symlinked to somewhere else. So that implies that it starts watching the wrong file. If I edit that file, the edits take place in the original file, so no system events are sent to indicate that /Users/jean/.config/skhd is updated.

Ran into this issue as well when I broke my .skhdrc up into multiple files.
I have my configuration tracked in a dotfiles repo:
~/.dotfiles/skhdrc/
~/.dotfiles/skhdrc/skhdrc
~/.dotfiles/skhdrc/window
~/.dotfiles/skhdrc/space
# ...

Symlinked like
ln -s ~/.dotfiles/skhdrc ~/.config/skhdrc


Enter multi-select mode via ctrl/cmd+click or shift+click

User Story
As a PD user, I would like to SHIFT/CTRL/CMD+CLICK to select multiple steps for editing.
Requirements
Entering Multi-step selection
Hold SHIFT & Click (multi-select range)
Hold CMND or CTRL & Click (multi-select steps one at a time)
For policies and selection scenarios for entering batch edit mode, see Batch Edit Step Bulk Actions Chart
Acceptance Criteria
See the Figma chart above for a full list of expected behaviors

We should dispatch SELECT_MULTIPLE_STEPS with a payload containing an array of step ids that should selected (including any step that was already selected in single-step mode, if any)

All "are you sure" modals described in the chart should appear when their conditions are met.

Several selectors involved in selection should discriminate between single-mode vs multi-select mode. See epic description (#7061 - eg, getSelectedStepId)

As per slack convo, if you have a terminal item selected, even if you shift/command click a non terminal item, you can't enter batch edit mode


Change Reader settings layout

This PR changes the way the Reader settings are displayed. The
fork specific settings for the reader have been moved to the bottom
instead of being sandwiched between settings from the main app.
Makes it look a better organised now
git tries to minimise deltas so the git diff might look a bit strange
anyways, here's a Video preview of new Reader Settings (with
Fork settings at the bottom):
https://user-images.githubusercontent.com/72807749/109381260-471cde80-78ff-11eb-87d8-e9d8b4a562a3.mp4

Should put continues vertical under webtoon like before, since its a reading mode unlike the navigation settings

So, to confirm
Reader Settings will be in the order:

Reader/Defaults/Meta
Display
Reading
Paged
Webtoon
Continuous vertical
Navigation
Fork Settings

Looks good to me

Done


Plugin straight up wont work for me; help

Plugin installed, neither Freemoji or FreeEmojis work, attempted with both emoji picker and text.

same

any updates?


Post release automated changes for recoveryservicessiterecovery releases

Post release automated changes for azure-arm-recoveryservices-siterecovery

API change check
API changes are not detected in this pull request.


kie-issues#1397 - Adjust git tag creation for Apache 10 release

Part of: https://github.com/apache/incubator-kie-issues/issues/1397

PR job #1 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
build-chain build full_downstream  -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-kogito-apps -u https://github.com/apache/incubator-kie-kogito-apps/pull/2082 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-apps-pr/job/PR-2082/1/display/redirect
Test results:

PASSED: 1663
FAILED: 2

Those are the test failures:

org.kie.kogito.index.infinispan.ProcessDataIndexInfinispanHttpIT.testProcessInstanceEvents
1 expectation failed.JSON path errors doesn't match.Expected: null  Actual: <[{message=Exception while fetching data (/UserTaskInstanceCommentUpdate) : Index 0 out of bounds for length 0, locations=[{line=1, column=12}], path=[UserTaskInstanceCommentUpdate], extensions={classification=DataFetchingException}}]>

org.kie.kogito.jobs.service.scheduler.impl.VertxTimerServiceSchedulerTest.testScheduleJob
Unnecessary stubbings detected.Clean & maintainable test code requires zero unnecessary code.Following stubbings are unnecessary (click to navigate to relevant line of code):  1. -> at org.kie.kogito.jobs.service.scheduler.impl.VertxTimerServiceSchedulerTest.testScheduleJob(VertxTimerServiceSchedulerTest.java:98)Please remove unnecessary stubbings or use 'lenient' strictness. More info: javadoc for UnnecessaryStubbingException class.

PR job #2 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
build-chain build full_downstream  -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-kogito-apps -u https://github.com/apache/incubator-kie-kogito-apps/pull/2082 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-apps-pr/job/PR-2082/2/display/redirect
Test results:

PASSED: 1662
FAILED: 3

Those are the test failures:

org.kie.kogito.index.mongodb.ProcessDataIndexMongoDBKafkaIT.testProcessInstanceEvents
1 expectation failed.JSON path data.UserTaskInstances[0].potentialGroups[0] doesn't match.Expected: managers  Actual: null

org.kie.kogito.index.ProcessDataIndexMongoDBIT.testProcessInstanceEvents
1 expectation failed.JSON path data.UserTaskInstances[0].potentialGroups[0] doesn't match.Expected: managers  Actual: null

org.kie.kogito.jobs.service.scheduler.impl.VertxTimerServiceSchedulerTest.testScheduleJob
Unnecessary stubbings detected.Clean & maintainable test code requires zero unnecessary code.Following stubbings are unnecessary (click to navigate to relevant line of code):  1. -> at org.kie.kogito.jobs.service.scheduler.impl.VertxTimerServiceSchedulerTest.testScheduleJob(VertxTimerServiceSchedulerTest.java:98)Please remove unnecessary stubbings or use 'lenient' strictness. More info: javadoc for UnnecessaryStubbingException class.

PR job #3 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
build-chain build full_downstream  -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-kogito-apps -u https://github.com/apache/incubator-kie-kogito-apps/pull/2082 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-apps-pr/job/PR-2082/3/display/redirect
Test results:

PASSED: 1662
FAILED: 3

Those are the test failures:

org.kie.kogito.index.infinispan.ProcessDataIndexInfinispanHttpIT.testProcessInstanceEvents
1 expectation failed.JSON path errors doesn't match.Expected: null  Actual: <[{message=Exception while fetching data (/UserTaskInstanceCommentUpdate) : Index 0 out of bounds for length 0, locations=[{line=1, column=12}], path=[UserTaskInstanceCommentUpdate], extensions={classification=DataFetchingException}}]>

org.kie.kogito.index.mongodb.ProcessDataIndexMongoDBKafkaIT.testProcessInstanceEvents
1 expectation failed.JSON path errors doesn't match.Expected: null  Actual: <[{message=Exception while fetching data (/UserTaskInstances[0]/schema) : Runtime service URL not defined, please review the kogito.service.url system property to point the public URL for this runtime., locations=[{line=1, column=85}], path=[UserTaskInstances, 0, schema], extensions={classification=DataFetchingException}}]>

org.kie.kogito.jobs.service.scheduler.impl.VertxTimerServiceSchedulerTest.testScheduleJob
Unnecessary stubbings detected.Clean & maintainable test code requires zero unnecessary code.Following stubbings are unnecessary (click to navigate to relevant line of code):  1. -> at org.kie.kogito.jobs.service.scheduler.impl.VertxTimerServiceSchedulerTest.testScheduleJob(VertxTimerServiceSchedulerTest.java:98)Please remove unnecessary stubbings or use 'lenient' strictness. More info: javadoc for UnnecessaryStubbingException class.


tbb: 2021.8.0 -> 2021.11.0

Fixes #301390
Description of changes
Updates tbb to 2021.11.0.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

@thoughtpolice @hesiod

Be careful not to bump tbb_2021_8 from 2021.8.0 to 2021.11.0: https://github.com/NixOS/nixpkgs/blob/ae8f15ae441a54f9579c94186ab6d715fb9266c9/pkgs/top-level/all-packages.nix#L17093
Instead, try something like tbb_2021_11: init at 2021.11.0.

Thanks for the feedback. Is this what you had in mind?

@wegank @SuperSandro2000 I made the requested changes and renamed tbb tree-wide.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 301391 run on x86_64-linux 1

2 packages failed to build and already failed to build on hydra master:

cctag: plain log
super-slicer: plain log

3 packages failed to build and are new build failures:

cctag.dev: plain log
cctag.lib: plain log
super-slicer.debug: plain log

21 packages built:

bambu-studio
bambu-studio.debug
ikos
mold
mold-wrapped
openscad-unstable
orca-slicer
orca-slicer.debug
pdf4qt
prusa-slicer
prusa-slicer.debug
salmon
super-slicer-beta
super-slicer-beta.debug
super-slicer-latest
super-slicer-latest.debug
tbb_2021_11
tbb_2021_11.dev
ueberzugpp
universal-android-debloater
ytfzf

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

bambu-studio.debug:

got build log for '/nix/store/ag9vnc0ghcylsmzql2xxqsy3c6zw42j5-bambu-studio-<IP_ADDRESS>-debug' from 'daemon'
When evaluating attribute ‘bambu-studio.debug’:
warning: unused-argument
Unused argument: qhull.
Near pkgs/applications/misc/bambu-studio/default.nix:39:3:
   |
39 | , qhull
   |   ^

warning: unused-argument
Unused argument: fetchpatch.
Near pkgs/applications/misc/bambu-studio/default.nix:45:3:
   |
45 | , fetchpatch
   |   ^

orca-slicer.debug:

got build log for '/nix/store/ykcshww40nn9m4pfnrmjs1xqx2bhnrkh-orca-slicer-1.9.1-debug' from 'daemon'
When evaluating attribute ‘orca-slicer.debug’:
warning: unused-argument
Unused argument: makeDesktopItem.
Near pkgs/applications/misc/bambu-studio/orca-slicer.nix:1:25:
  |
1 | { lib, fetchFromGitHub, makeDesktopItem, bambu-studio }:
  |                         ^

orca-slicer:

got build log for '/nix/store/n6f3hvb7p5f8j1j0ljxbbn07x37zk16g-orca-slicer-1.9.1' from 'daemon'
When evaluating attribute ‘orca-slicer’:
warning: unused-argument
Unused argument: makeDesktopItem.
Near pkgs/applications/misc/bambu-studio/orca-slicer.nix:1:25:
  |
1 | { lib, fetchFromGitHub, makeDesktopItem, bambu-studio }:
  |                         ^

super-slicer-latest.debug:

got build log for '/nix/store/1ng6c8zxg4zyycmcambqm8g52q6wqchj-super-slicer-<IP_ADDRESS>-debug' from 'daemon'
When evaluating attribute ‘super-slicer-latest.debug’:
warning: stale-substitute
Stale substituteInPlace detected.
substituteStream(): WARNING: pattern list(APPEND\ wxWidgets_LIBRARIES\ libexpat) doesn't match anything in file 'src/CMakeLists.txt'
Near pkgs/applications/misc/prusa-slicer/super-slicer.nix:83:
   |
83 |       inherit description;
   | ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/stale-substitute.md
warning: stale-substitute
Stale substituteInPlace detected.
substituteStream(): WARNING: pattern libexpat doesn't match anything in file 'src/libslic3r/CMakeLists.txt'
Near pkgs/applications/misc/prusa-slicer/super-slicer.nix:83:
   |
83 |       inherit description;
   | ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/stale-substitute.md

super-slicer-latest:

got build log for '/nix/store/jrykac1aa39fc98yxcxpc3y88fvmkbl3-super-slicer-<IP_ADDRESS>' from 'daemon'
When evaluating attribute ‘super-slicer-latest’:
warning: stale-substitute
Stale substituteInPlace detected.
substituteStream(): WARNING: pattern list(APPEND\ wxWidgets_LIBRARIES\ libexpat) doesn't match anything in file 'src/CMakeLists.txt'
Near pkgs/applications/misc/prusa-slicer/super-slicer.nix:83:
   |
83 |       inherit description;
   | ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/stale-substitute.md
warning: stale-substitute
Stale substituteInPlace detected.
substituteStream(): WARNING: pattern libexpat doesn't match anything in file 'src/libslic3r/CMakeLists.txt'
Near pkgs/applications/misc/prusa-slicer/super-slicer.nix:83:
   |
83 |       inherit description;
   | ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/stale-substitute.md


Adding '-a/--autoload' option

This PR adds a --autoload (shorthand -a) option to boris. Adding this option will make Boris automatically search for a autoload.php file and require it so that the user's classes are available immediately.
Examples:
Using -a option, autoload.php is required automatically:
~/my_composer_project$ boris -a
Requiring autoload file: /Users/leonardoraele/my_composer_project/vendor/autoload.php
[1] boris>

Not using -a option, boris works normally.
~/my_composer_project$ boris
[1] boris>

Using -a option not in a composer project, nothing is loaded. Boris works normally.
~/my_composer_project$ cd ~
~$ boris -a
No autoload file found.
[1] boris>

Closing as it is using the wrong source branch.

Replaced by https://github.com/borisrepl/boris/pull/133


The  implementation of ResNet is different from official implementation in Caffe

The downsample part in each block/layer (not the skip connection part), the PyTorch do it in conv3x3 using stride=2, but official caffe version in conv1x1 with stride=2
conv1x1 -> caffe do it in here
conv3x3 -> pytorch do it in here
conv1x1

Here in Bottleneck:
        self.conv2 = nn.Conv2d(planes, planes, kernel_size=3, stride=stride,
                               padding=1, bias=False)

  (layer2): Sequential (
    (0): Bottleneck (
      (conv1): Conv2d(256, 128, kernel_size=(1, 1), stride=(1, 1), bias=False)
      (bn1): BatchNorm2d(128, eps=1e-05, momentum=0.1, affine=True)
      (conv2): Conv2d(128, 128, kernel_size=(3, 3), stride=(2, 2), padding=(1, 1), bias=False)
       ...

but in caffe

layer {
	bottom: "res2c"
	top: "res3a_branch2a"
	name: "res3a_branch2a"
	type: "Convolution"
	convolution_param {
		num_output: 128
		kernel_size: 1
		pad: 0
		stride: 2
		bias_term: false
	}
}

From what I see, the torchvision implementation also uses 1x1 convolution kernels when downsampling, see here for example

This is only partially true (and the issue should not be closed). Downsample is one of the convolutions that should have stride 2 (and it has, like you pointed out, @fmassa), but there is also convolutions in bottleneck block (which the original issue was referencing) - see here. Here also it is the first convolution (1x1) that should have stride=stride, not the second convolution (3x3).

Also, Table 1 in the paper describes that "downsampling is performed by conv3_1, conv4_1, and conv5_1 with a stride of 2." If I am not missing something in the code, it seems that all Bottleneck layers within a convolutional group are using stride 2 in the second convolution, instead of using it only in the first convolution within the first Bottleneck layer (as pointed out by @ptrendx). For instance, in the last convolutional group, we have three Bottleneck layers following this pattern:
# Bottleneck layer (x3)
out = conv1_bn_relu(out, kernel=1, stride=1)
out = conv2_bn_relu(out, kernel=3, stride=2)
out = conv3_bn_relu(out, kernel=1, stride=1)

While it should be:
out = conv1_bn_relu(out, kernel=1, stride=2)
out = conv2_bn_relu(out, kernel=3, stride=1)
out = conv3_bn_relu(out, kernel=1, stride=1)

out = conv1_bn_relu(out, kernel=1, stride=1)
out = conv2_bn_relu(out, kernel=3, stride=1)
out = conv3_bn_relu(out, kernel=1, stride=1)

out = conv1_bn_relu(out, kernel=1, stride=1)
out = conv2_bn_relu(out, kernel=3, stride=1)
out = conv3_bn_relu(out, kernel=1, stride=1)

If you paste the original prototxt in this network visualizer, in the last convolutional group only conv5_1 (res5a_branch2a) has stride 2; the following layers in the same group all have stride 1. Are we missing something?

While I agree that the definition of the Bottleneck module seems to be different than the one mentioned in the original paper, I believe that what is currently done is throws away much less information in the beginning of each block (at the expense of a smaller receptive field). Indeed, the original implementation seems to throw away 75% of the input of each residual at the beginning of each Bottleneck module (1x1 conv with stride of 2).
Note that the BasicBlock architecture follows the right pattern.
I'm reopening the issue and tagging @colesbury (who originally implemented ResNet in PyTorch).
To summarize, the original paper mentions downsampling to happen here, while we are doing it here. The same is present in fb-resnet.torch.

That makes sense, @fmassa. A lot is being discarded in the original implementation.
To add to this discussion, according to this user, Kaiming He wrote:

In all experiments in the paper, the stride=2 operation is in the first 1x1 conv layer when downsampling. This might not be the best choice, as it wastes some computations of the preceding block. For example, using stride=2 in the first 1x1 conv in the first block of conv3 is equivalent to using stride=2 in the 3x3 conv in the last block of conv2. So I feel applying stride=2 to either the first 1x1 or the 3x3 conv should work. I just kept it “as is”, because we do not have enough resources to investigate every choice.

I actually tried to fine-tune both architectures to my task (which possibly isn't the most suitable way to evaluate it, though), and they both gave similar results.

I try to summarise:

implementation of ResNet in PyTorch does differ from the one in Kaiming He's original paper: it transfers the responsibility for downsampling from the first 1x1 convolutional layer to the 3x3 convolutional layer in Bottleneck.
This kind of variation is also known as "ResNet V1.5" as mentioned in  https://github.com/pytorch/vision/issues/1266, which seems to be defined by NVIDIA according to https://github.com/NVIDIA/DeepLearningExamples/issues/419#issuecomment-597643335.
The effects of this modification in practice  has been pointed out here by NVIDIA

This difference makes ResNet50 v1.5 slightly more accurate (~0.5% top1) than v1, but comes with a small performance drawback (~5% imgs/sec).

It may be unnecessary to change it back to the original implementation, since the differences are negligible(actually with accuracy increasing). Besides, changing it may affect the previously pre-trained models' performance.

After all, some comments  may be needed in resnet.py to explain this situation as well as to close this issue and prevent similar issues in the future.
How do you think? @fmassa If needed, I can open a PR for it.

@Dirtybluer a PR adding some comments to the resnet code would be great!

Perhaps we could have a (say) v1_downsampling=False argument to choose the v1 implementation? This is particularly useful if you want to reproduce as closely as possible a paper which uses a v1 resnet backbone for something.
Of course, you could cook a script yourself to hack a resnet instance to move the downsampling to the 1x1 convolution, but I think it would be better if everyone could rely on this being implemented consistently.
What do you think? If the above sounds reasonable, I can throw a PR.

Just FYI, training a Resnet34 model on CIFAR10 gives much worse performance when done with torchvision's version:

with torchvision's ResNet34 I am getting up to 89% accuracy on CIFAR10 (trained as in https://github.com/kuangliu/pytorch-cifar)
by using Kuangliu's version, I am easily getting 93% accuracy.

I was struggling to reproduce CIFAR10 results as I assumed the performance should be similar between the two repos.

The input image size of CIFAR10 is much smaller than ImageNet, you can prune off one layer of TorchVision's model for CIFAR10 to get similar results of Kuang Liu's results, and seems that's tricks behind Liu's repo.

Thanks for the info! You're right, I just read that the first CNN layer in torchvision has kernel of size 7, stride 2, and padding 3, while Kuang Liu uses kernel 3, stride 1 & no padding I think.

Just FYI, training a Resnet34 model on CIFAR10 gives much worse performance when done with torchvision's version:

with torchvision's ResNet34 I am getting up to 89% accuracy on CIFAR10 (trained as in https://github.com/kuangliu/pytorch-cifar)
by using Kuangliu's version, I am easily getting 93% accuracy.

I was struggling to reproduce CIFAR10 results as I assumed the performance should be similar between the two repos.

Same here on CIFAR100, it makes me frustrated on hyperparams tuning and can't find where the problem is.


Add a test for 'podman play kube' to prevent regression

As the title says.

LGTM

LGTM
Once you fix your testing/building issues.

The generated YAML works on my machine, so I'm not sure what's going on here. Probably issues writing the output of 'generate kube' to file.
I might just add a --file to generate kube to specify an output file for simplicity.

Added --filename, -f flag to generate kube. Let's see if the tests start passing.

@rhatdan @haircommander @giuseppe @baude Anyone want to hit this with an LGTM? Tests went green

/lgtm


improve tutorials

I think we need to add to the tutorial(s), somewhere:

[ ] alpha rarefaction
[ ] beta rarefaction
[ ] others?

Also, not sure if worth revising the use of _ vs - because for some outputs we have _ and for others -. I think standardizing to _ will be nice cause that way you can "auto select" by double clicking.

Thanks @antgonza!
I am closing this to move (and split) to the appropriate issue tracker

alpha rarefaction(dupe) https://github.com/qiime2/docs/issues/207
beta rarefaction (new) https://github.com/qiime2/docs/issues/209
hyphen vs underscore (new) https://github.com/qiime2/docs/issues/210

Thanks.


feat: Static menus

Menus cannot be sent via bot.api because they require an installed API transformer. This transformer is only installed during bot.use(menu).
One way would be to directly provide the API transformer to be installed on bot.api, but this does not follow the intuitive pattern of the rest of the plugin.
Instead, it would be cool if we can have a statically rendered version of the menu (a menu range) that can be passed to the constructor of the menu. Whenever the menu is sent (the internal Proxy is accessed), this static menu is rendered and sent. It obviously may not depend on a context object, so we should throw an error if someone tries to use dynamic strings/dynamic ranges.
const menu = new Menu('id', {
  static: new Menu.Range().text('go', ctx => ctx.reply('whee'))
})

Depositing the phrases I queried the issues of this repo so that they may be indexed for others:
this.id
bot.use
bot.api
Context
Question
Good evening all, a question about Menus and ctx:
Suppose I wanted to use grammY bot in an ancillary webhook that does not receive updates from Telegram but payloads from another system e.g. a scheduled message.
This message will contain a Menu, which depends on ctx to work; directly using Menu with bot.api.sendMessage(1234567, "good evening", {reply_markup: Menu} throws error Cannot send menu '${this.id}'! Did you forget to use bot.use() for it?. Actually, bot.use(Menu) is called before any other middleware.
I am assuming that if I had access to a ctx, presumably via  listener, Menu would work. If so, what listener could be triggered by a non-telegram-update payload?
Has anyone any experience with sending menus in such a manner?
Edit: Menu is an instance of the Menu class (from plugin)
Answer
@KnorpelSenf:
You are correct that menus are generated from context objects. There's an idea to create static menus (https://github.com/grammyjs/menu/issues/2) but so far there's been very little demand for this. Until then, there's a less convenient solution:
What you should do instead is to use bot.api to send a message with reply markup, using the built-in keyboard plugin of grammY. As soon as a button is pressed, you can switch over to the menu plugin and let it handle the rest.


Can't open

Downloaded the binary to give it a try but it doesn't open.
https://user-images.githubusercontent.com/6496455/166145921-a34726c4-708e-4e11-bc93-3a534553292c.mp4
The window goes completely white, the program logs Using device: NVIDIA GeForce GTX 1070, and then it exits.

I also tried to pass a test image, but the same happens.

I'm going to assume the issue is your graphics driver doesn't support some of the feature bits set by the vulkan device on initialization (for example, dynamic render passes). Can you paste the output of running vulkaninfo.exe?

vulkaninfo_output.txt

@santaclose Sorry for the delay again, I'm horrible with github notifications. From what I can tell, the only missing feature bit for your card/driver is descriptorBindingUniformBufferUpdateAfterBind which I am setting. However, the good news is, I don't actually need this feature bit. Do you think you'd be able to try compiling and running the latest commit on the main branch?

I tried to follow the build instructions but something went wrong. Also, I don't know if I have the Vulkan SDK installed. Can you upload a binary somewhere?
A:\flop (main -> origin)
λ cmake -B build -S .
-- Building for: Visual Studio 16 2019
-- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.19043.
-- The C compiler identification is MSVC 19.29.30133.0
-- The CXX compiler identification is MSVC 19.29.30133.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/cl.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/cl.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
Microsoft (R) Build Engine version 16.11.0+0538acc04 for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.

  Checking Build System
  Creating directories for 'dxcompiler-populate'
  Building Custom Rule A:/flop/build/_deps/dxcompiler-subbuild/CMakeLists.txt
  Performing download step (download, verify and extract) for 'dxcompiler-populate'
  -- Downloading...
     dst='A:/flop/build/_deps/dxcompiler-subbuild/dxcompiler-populate-prefix/src/dxc_2021_12_08.zip'
     timeout='none'
     inactivity timeout='none'
  -- Using src='https://github.com/microsoft/DirectXShaderCompiler/releases/download/v1.6.2112/dxc_2021_12_08.zip'
  -- [download 0% complete]
  -- [download 1% complete]
  -- [download 2% complete]
  -- [download 3% complete]
  -- [download 4% complete]
  -- [download 5% complete]
  -- [download 6% complete]
  -- [download 7% complete]
  -- [download 8% complete]
  -- [download 9% complete]
  -- [download 10% complete]
  -- [download 11% complete]
  -- [download 12% complete]
  -- [download 13% complete]
  -- [download 14% complete]
  -- [download 15% complete]
  -- [download 16% complete]
  -- [download 17% complete]
  -- [download 18% complete]
  -- [download 19% complete]
  -- [download 20% complete]
  -- [download 21% complete]
  -- [download 22% complete]
  -- [download 23% complete]
  -- [download 24% complete]
  -- [download 25% complete]
  -- [download 26% complete]
  -- [download 27% complete]
  -- [download 28% complete]
  -- [download 29% complete]
  -- [download 30% complete]
  -- [download 31% complete]
  -- [download 32% complete]
  -- [download 33% complete]
  -- [download 34% complete]
  -- [download 35% complete]
  -- [download 36% complete]
  -- [download 37% complete]
  -- [download 38% complete]
  -- [download 39% complete]
  -- [download 40% complete]
  -- [download 41% complete]
  -- [download 42% complete]
  -- [download 43% complete]
  -- [download 44% complete]
  -- [download 45% complete]
  -- [download 46% complete]
  -- [download 47% complete]
  -- [download 48% complete]
  -- [download 49% complete]
  -- [download 50% complete]
  -- [download 51% complete]
  -- [download 52% complete]
  -- [download 53% complete]
  -- [download 54% complete]
  -- [download 55% complete]
  -- [download 56% complete]
  -- [download 57% complete]
  -- [download 58% complete]
  -- [download 59% complete]
  -- [download 60% complete]
  -- [download 61% complete]
  -- [download 62% complete]
  -- [download 63% complete]
  -- [download 64% complete]
  -- [download 65% complete]
  -- [download 66% complete]
  -- [download 67% complete]
  -- [download 68% complete]
  -- [download 69% complete]
  -- [download 70% complete]
  -- [download 71% complete]
  -- [download 72% complete]
  -- [download 73% complete]
  -- [download 74% complete]
  -- [download 75% complete]
  -- [download 76% complete]
  -- [download 77% complete]
  -- [download 78% complete]
  -- [download 79% complete]
  -- [download 80% complete]
  -- [download 81% complete]
  -- [download 82% complete]
  -- [download 83% complete]
  -- [download 84% complete]
  -- [download 85% complete]
  -- [download 86% complete]
  -- [download 87% complete]
  -- [download 88% complete]
  -- [download 89% complete]
  -- [download 90% complete]
  -- [download 91% complete]
  -- [download 92% complete]
  -- [download 93% complete]
  -- [download 94% complete]
  -- [download 95% complete]
  -- [download 96% complete]
  -- [download 97% complete]
  -- [download 98% complete]
  -- [download 99% complete]
  -- [download 100% complete]
  -- Downloading... done
  -- extracting...
       src='A:/flop/build/_deps/dxcompiler-subbuild/dxcompiler-populate-prefix/src/dxc_2021_12_08.zip'
       dst='A:/flop/build/_deps/dxcompiler-src'
  -- extracting... [tar xfz]
CUSTOMBUILD : CMake error : Problem with archive_write_finish_entry(): Can't restore time [A:\flop\build\_deps\dxcompiler-subbuild\dxcompiler-populate.vcxproj]
  -- extracting... [error clean up]
CUSTOMBUILD : CMake error : Problem extracting tar: A:/flop/build/_deps/dxcompiler-subbuild/dxcompiler-populate-prefix/src/dxc_2021_12_08.zip [A:\flop\build\_deps\dxcompiler-subbuild\dxcompiler-populate.vcxproj]
  CMake Error at dxcompiler-subbuild/dxcompiler-populate-prefix/src/dxcompiler-populate-stamp/extract-dxcompiler-populate.cmake:33 (message): CUSTOMBUILD : error : extract of [A:\flop\build\_deps\dxcompiler-subbuild\dxcompiler-populate.vcxproj]
    'A:/flop/build/_deps/dxcompiler-subbuild/dxcompiler-populate-prefix/src/dxc_2021_12_08.zip'
    failed

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(241,5): error MSB8066: Custom build for 'A:\flop\build\_deps\dxcompiler-subbuild\CMakeFiles\dd7c1704ab0a64712aac82c92b8f07c1\dxcompiler-populate-mkdir.rule;A:\flop\build\_deps\dxcompiler-subbuild\CMakeFiles\dd7c1704ab0a64712aac82c92b8f07c1\dxcompiler-populate-download.rule;A:\flop\build\_deps\dxcompiler-subbuild\CMakeFiles\dd7c1704ab0a64712aac82c92b8f07c1\dxcompiler-populate-update.rule;A:\flop\build\_deps\dxcompiler-subbuild\CMakeFiles\dd7c1704ab0a64712aac82c92b8f07c1\dxcompiler-populate-patch.rule;A:\flop\build\_deps\dxcompiler-subbuild\CMakeFiles\dd7c1704ab0a64712aac82c92b8f07c1\dxcompiler-populate-configure.rule;A:\flop\build\_deps\dxcompiler-subbuild\CMakeFiles\dd7c1704ab0a64712aac82c92b8f07c1\dxcompiler-populate-build.rule;A:\flop\build\_deps\dxcompiler-subbuild\CMakeFiles\dd7c1704ab0a64712aac82c92b8f07c1\dxcompiler-populate-install.rule;A:\flop\build\_deps\dxcompiler-subbuild\CMakeFiles\dd7c1704ab0a64712aac82c92b8f07c1\dxcompiler-populate-test.rule;A:\flop\build\_deps\dxcompiler-subbuild\CMakeFiles\6bfc05bde7332505db09602ec912b388\dxcompiler-populate-complete.rule;A:\flop\build\_deps\dxcompiler-subbuild\CMakeFiles\dc049993d9bf55cc82306bcd81bb118c\dxcompiler-populate.rule;A:\flop\build\_deps\dxcompiler-subbuild\CMakeLists.txt' exited with code 1. [A:\flop\build\_deps\dxcompiler-subbuild\dxcompiler-populate.vcxproj]

CMake Error at C:/Program Files/CMake/share/cmake-3.21/Modules/FetchContent.cmake:1017 (message):
  Build step for dxcompiler failed: 1
Call Stack (most recent call first):
  C:/Program Files/CMake/share/cmake-3.21/Modules/FetchContent.cmake:1146:EVAL:2 (__FetchContent_directPopulate)
  C:/Program Files/CMake/share/cmake-3.21/Modules/FetchContent.cmake:1146 (cmake_language)
  shaders/CMakeLists.txt:9 (FetchContent_Populate)

-- Configuring incomplete, errors occurred!
See also "A:/flop/build/CMakeFiles/CMakeOutput.log".

A:\flop (main -> origin)
λ cmake --build build
Microsoft (R) Build Engine version 16.11.0+0538acc04 for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.

MSBUILD : error MSB1009: Project file does not exist.
Switch: ALL_BUILD.vcxproj

A:\flop (main -> origin)
λ cmake --version
cmake version 3.21.2

CMake suite maintained and supported by Kitware (kitware.com/cmake).

A:\flop (main -> origin)
λ

@santaclose Sorry for the delay again, I'm horrible with github notifications. From what I can tell, the only missing feature bit for your card/driver is descriptorBindingUniformBufferUpdateAfterBind which I am setting. However, the good news is, I don't actually need this feature bit. Do you think you'd be able to try compiling and running the latest commit on the main branch?

I'm having the same problem, and I too am having difficulties compiling.

Sorry for the late response @ImportTaste and @santaclose . I've added binaries for flop in a new release here. Please let me know if this resolves things for you

Sorry for the late response @ImportTaste and @santaclose . I've added binaries for flop in a new release here. Please let me know if this resolves things for you

Still crashes immediately, unfortunately. Identical output to the screenshots in the OP.

Well, I don't know why. Just to make sure Vulkan is working correctly, I ran an image through waifu2x-ncnn-vulkan and it worked fine.
Still can't get flop to launch though.

@ImportTaste can you copy-paste the output of the vulkaninfo command here as well? Chances are there is a similar driver or device incompatibility

Made a backup of vulkan-1.dll and started experimenting with other vulkan-1.dll files on my computer, this one comes from the Edge browser:
Faulting application name: flop.exe, version: <IP_ADDRESS>, time stamp: 0x62a57263
Faulting module name: vulkan-1.dll, version: 1.0.1111.2222, time stamp: 0x62a905e0
Exception code: 0xc0000409
Fault offset: 0x000000000006aa8d
Faulting process id: 0x1f70
Faulting application start time: 0x01d881ca76b6df4d
Faulting application path: L:\Downloads\FLOP\flop.exe
Faulting module path: C:\WINDOWS\SYSTEM32\vulkan-1.dll
Report Id: a7f2be7a-c5b7-4598-996c-f5fbe3d696f7
Faulting package full name:
Faulting package-relative application ID:

This one comes from Discord:
Faulting application name: flop.exe, version: <IP_ADDRESS>, time stamp: 0x62a57263
Faulting module name: vulkan-1.dll, version: 1.0.1111.2222, time stamp: 0x62a905e0
Exception code: 0xc0000409
Fault offset: 0x000000000006aa8d
Faulting process id: 0x1f70
Faulting application start time: 0x01d881ca76b6df4d
Faulting application path: L:\Downloads\FLOP\flop.exe
Faulting module path: C:\WINDOWS\SYSTEM32\vulkan-1.dll
Report Id: a7f2be7a-c5b7-4598-996c-f5fbe3d696f7
Faulting package full name:
Faulting package-relative application ID:

This one comes from VSCodium:
Faulting application name: flop.exe, version: <IP_ADDRESS>, time stamp: 0x62a57263
Faulting module name: vulkan-1.dll, version: 1.0.1111.2222, time stamp: 0x62979612
Exception code: 0xc0000409
Fault offset: 0x0000000000064971
Faulting process id: 0x42dc
Faulting application start time: 0x01d881cab799c22a
Faulting application path: L:\Downloads\FLOP\flop.exe
Faulting module path: C:\WINDOWS\SYSTEM32\vulkan-1.dll
Report Id: f0b72418-6f4f-46a0-a2d2-ae162cc17968
Faulting package full name:
Faulting package-relative application ID:

@ImportTaste can you copy-paste the output of the vulkaninfo command here as well? Chances are there is a similar driver or device incompatibility

I did vulkaninfo >vulkaninfo.txt and it output this to stderr, not sure if it's relevant:
WARNING: [Loader Message] Code 0 : ReadDataFilesInRegistry: Registry lookup failed to get layer manifest files.

Here is the stdout: vulkaninfo.txt

Closing this issue as resolved, but opened #5 to investigate the other problem


Results by groups in the top

Hello! Prompt please, It is possible to transfer results of aggregation in heading of group?

formatter: x => x.value + ' ' + x.totals.sum.Summa,
It turned out this way, but so far the format and rounding can not be applied

formatter: x => x.value + ' ' + (Math.round(x.totals.sum.Summa * 100) / 100).toFixed(2).replace(/(\d)(?=(\d{3})+.)/g, '$1,'),
Maybe not the most elegant, but it works!

Totals in group headers not supported, but you can put it on title like you did, just as count


[POC] IGNITE-18758 Clients 3.0: Design server-side metrics

https://issues.apache.org/jira/browse/IGNITE-18758

@agura this PR is closed, it is no longer relevant. Please see #1766.


Trouble Reopening MySQL Connection

I have a utility application that is run periodically via the node-cron module. Basically, I open a MySQL connection, run a query using knex.raw, do a database update using Bookshelf model.save, then close the connection using bookshelf.knex.destroy. My code succeeds the first time the function is called, but fails on the second and successive calls with "The genericPool is not initialized."
Here is a code sample:
function RunOnASchedule() {

  database = {
    client: 'mysql',
    connection: {
      host: config.RDS_HOSTNAME,
      user: config.RDS_USERNAME,
      password: config.RDS_PASSWORD,
      port: config.RDS_PORT,
      database: config.RDS_DATABASE
  };

  var knex = require('knex')(database);
  bookshelf = require('bookshelf')(knex);

  return RunMyKnexRawQuery()
  .then(function(queryResult) {

    return UpdateDBUsingBookshelf(queryResult);

  })
  .then(function() {
    console.log('Done doing stuff.');
    return;
  })
  .catch(function(ex) {
    console.log('Error doing stuff: %s', ex.message);
  })
  .finally(function() {
		console.log('closing db connection');
    return bookshelf.knex.destroy()
    .then(function() {
      console.log('db connection closed');
    })
  })
}

The call to RunMyKnexRawQuery() succeeds every time. But the call to UpdateDBUsingBookshelf() only works the first time. On the second and successive calls, it fails with "The genericPool is not initialized." as soon as I try to do something like MyModel.forge({model_id: id}).fetch({require: true})...
It seems like the Knex connection is successfully reinitialized (or maybe it's never really closed) because I can use it again. But somehow, the Bookshelf instance can't use the reinitialized connection.
Is there a better way to handle this? What's the best approach to closing then reopening a connection?
Thank you for your help!

Is it on purpose that database is a global?

"database is a global" No reason other than transcription error. Tried to provide sample code that is more generic than my actual solution.

Can you fix any such errors then? That way we avoid having to ask about those things.

Closing due to lack of activity. If you have anything else to add we can reopen this issue.


Add force flag to force the generators to run

Stack:

#15
#14
#13

commit MERGED in pull request #15


No Resource for Personal Session Desktops feature of Server 2016

There is no resource for enabling the new Personal Session Desktops feature of Server 2016.
http://social.technet.microsoft.com/wiki/contents/articles/31780.windows-server-2016-remote-desktop-services-introducing-personal-session-desktops.aspx
I plan to begin work on creating this resource within the xRemoteDesktopSessionHost module.
I plan to implement all the features in the above documentation link.

Because the Remote Desktop Personal Session feature is an extension of New-RDSessionCollection, but has a requirement for OS version >= 10, I plan to implement it as a new resource, rather than as additional properties on the existing xRemoteDesktopSessionCollection resource, so that I do not break backwards compatibility in that resource. I feel this will be a cleaner implementation, than testing the parameters in the Set-Target function, and throwing an exception there.
I am open to feedback on this though. @TravisEz13, looks like you contributed the original, what do you think?

@JimPriestley Could you include your proposed schema?

@TravisEz13 Here is the proposed schema for MSFT_xRDPersonalSessionDesktop
[ClassVersion("<IP_ADDRESS>"), FriendlyName("MSFT_xRDPersonalSessionDesktop")] class MSFT_xRDPersonalSessionDesktop : OMI_BaseResource {     [key, Description("Specifies a name for the session collection. ")] string CollectionName;     [key, Description("Specifies an RD Session Host server to include in the session collection. ")] string SessionHost;     [write, Description("Specifies a description for the collection.")] string CollectionDescription;     [write, Description("Specifies the Remote Desktop Connection Broker (RD Connection Broker) server for a Remote Desktop deployment.")] string ConnectionBroker;     [write, Description("Specifies whether to grant local administrative privledge")] bool GrantAdministrativePrivilege;     [write, Description("Specifies whether to auto assign user to an available session host")] bool AutoAssignUser; };

Is there really a need to configure remote hosts (ie SessionHost)?
With this property, you could have multiple LCMs trying to configure the same host.

Good point, we could restrict it to use the local host by default, implying that this would need to be applied exclusively on the session host machines. In that case, I believe the connection broker parameter would become mandatory, as it would be required in any deployment of more than one server.
I'm envisioning a scenario where a farm of hosts is deployed in Azure through an automation process, that assigns it as personal session host, and optionally assigns a user.
I was conflicted on this, as the next resource I intended to implement would be user/host assignment, to the sessionhosts.
In the feature documentation, they run this command on the connection broker, assigning users to the session hosts.
In practice, do you think it would be better to spread the user host assignment out on to each session host as part of it's individual config, or pass it in as a hash table only on the connection broker?
I was leaning towards the connection broker, as then it would only be one hash table in the config source. My thought is an admin could release a change to the config hashtable, and then only the connection broker's dsc has to refresh to update the assignment list.
In a full automation scenario, this enables me to delete the session host with out having to wait for it to update it's config, to unassign the user.

I lean to the per host assignment.  The hashtable should the configuration data passed into the configuration, then have a configuration for each host.  Most, but not all, resource that I see that allow configuring remote hosts don't have a good reason to allow it.
We need to keep in mind that DSC at the core is supposed to declare the state.  When you start declaring the state of something remote, there is no real assurance that it is in that state.  If the remote resource has LCM, it is better to create a resource, then declare that you are dependant on the remote resource instance in your local configuration.
I've seen cases where this isn't possible with resources for services that lack a master node (or conceptually equivalent.)   I'm not seeing that here (but I'm relying on your explanation.)

Makes sense. The ConnectionBroker is the master node in this scenario, and I will rework it so that this resource is to be applied locally on the session host LCM it is applied to, exclusively.

@JimPriestley this issues is labeled as in progress. I relabel this as help wanted. If you still work on this, then let me know and I relabel it again. Thanks!


Infinite scroll

For both search and my recipes we should support infinite scroll

Or alternatively use this
https://ant.design/components/pagination/


Treat paths of the form "existing-file/something" as non-existent

Some people like to construct phony target names by appending a
"/something" suffix to an existing target "foo".  But if "foo" is an
existing file, stat will report ENOTDIR for this path, causing ninja
to spew errors.  Fix this by treating ENOTDIR in the same way as we
do ENOENT -- as a non-existent path.

Can you write a test?  (Sorry!)
I think we attempt to do the same logic on Windows, but feel free to just run the test on Linux and have it break on Windows for now.  (See StatMissingFile, it looks like it's testing something similar but slightly different.)

Done.  (It looks like the test passes on Windows as well.)


ci(publish-to-npm): Fix incorrect artifact download path in GH workflow.

Related: #48

Description

ci(publish-to-npm): Fix incorrect artifact download path.

Validation performed

With this debug workflow file: https://github.com/junhaoliao/clp-ffi-js/actions/runs/12539427329/workflow , ls -l dist in the debug job showed all the artifacts: https://github.com/junhaoliao/clp-ffi-js/actions/runs/12539427329/job/34965610250

Summary by CodeRabbit

Chores

Updated GitHub Actions workflow for npm publishing
Improved artifact management during build and publish processes
Enhanced workflow reliability with explicit artifact handling and error conditions

Alternatively, this config would also work though it is less straight forward:
      - name: "Upload build artifacts"
        uses: "actions/upload-artifact@v4"
        with:
          # HERE the artifacts in "dist/" are uploaded with name "artifact" (the default value of "name")
          path: "dist/"
          if-no-files-found: "error"
          retention-days: 1

  publish-to-npm:
    needs: ["build"]
    runs-on: "ubuntu-latest"
    steps:
      - uses: "actions/checkout@v4"
      - uses: "actions/download-artifact@v4"
        with:
          # HERE we ask the action to place all artifacts into the destination path
          merge-multiple: true
          # HERE we download the artifacts into "dist/" instead of "artifact/"
          path: "dist/"


Fail to create role assignment az ad cp create-for-rbac with malformed scope

Describe the bug
Executing az ad sp create-for-rbac with --scope "/subscriptions/{subscriptionId}/resourceGroups/ argument fails with the following error
Role assignment creation failed.
role assignment response headers: {'Cache-Control': 'no-cache', 'Pragma': 'no-cache', 'Content-Type': 'application/json; charset=utf-8', 'Expires': '-1', 'x-ms-failure-cause': 'gateway', 'x-ms-request-id': 'fe7ba205-1514-4476-aedb-f79dece974a6', 'x-ms-correlation-request-id': 'fe7ba205-1514-4476-aedb-f79dece974a6', 'x-ms-routing-request-id': 'NORTHEUROPE:20190327T143620Z:fe7ba205-1514-4476-aedb-f79dece974a6', 'Strict-Transport-Security': 'max-age=31536000; includeSubDomains', 'X-Content-Type-Options': 'nosniff', 'Date': 'Wed, 27 Mar 2019 14:36:19 GMT', 'Content-Length': '440'}
The api-version '2018-01-01-preview' is invalid. The supported versions are '2019-03-01,2018-11-01,2018-09-01,2018-08-01,2018-07-01,2018-06-01,2018-05-01,2018-02-01,2018-01-01,2017-12-01,2017-08-01,2017-06-01,2017-05-10,2017-05-01,2017-03-01,2016-09-01,2016-07-01,2016-06-01,2016-02-01,2015-11-01,2015-01-01,2014-04-01-preview,2014-04-01,2014-01-01,2013-03-01,2014-02-26,2014-04'.
To Reproduce
execute az ad sp create-for-rbac with malformed scope as above
Expected behavior
Error message that the scope is invalid
Environment summary
using bash CloudShell
Additional context
azure-cli                         2.0.61

okay, this is rather a bad error from the service end.

Duplicate of https://github.com/Azure/azure-cli/issues/8892


HTMX support for starlite framework.

This solution implements HTMX support for starlite along the line of django-htmx.
How HTMX works:
HTMX adds its own headers to the HTTP request in HX-****** to the server and expects headers in response in the form HX-******. Details about every headers can be found at HTMX - Docs. Efforts have been made to provide all features of HTMX but, certain aspects of HTMX are not fully realized yet and have been left out.
Features this pull request tries to implement:

htmx-request
htmx-response

Full functionality for HX-Location has not been implemented.
HX-History-Restore-Request, HX-prompt has not been implemented.

PR Checklist

[x] Have you followed the guidelines in CONTRIBUTING.md?
[x] Have you got 100% test coverage on new code?
[ ] Have you updated the prose documentation?
[ ] Have you updated the reference documentation?

pr is empty

Sorry, I made a mistake in creating PR. I'll fix it

Is this a vendoring of code from another library? why? I need to understand the reasoning behind this. I would expect we could do our own version without vendoring.
Also - typing, this is basically untyped. Please address this.

There is no heavy logic in this library. Only thing needed to do is to read headers from request and add headers to response. Other htmx libraries for asgi frameworks i.e: flask-htmx, starlette-htmx, asgi-htmx have taken similar approach. No vendoring required.
The idea of HtmxDetails class is taken from django-htmx where htmx headers are assigned to properties to conveniently access header values, which I feel should be acknowledged and attributed. Further, extending starlite Response class to send HTMX Response headers sits well with starlite best practices.
This is an draft version, nothing is set in stone. We can discuss, bring new ideas, add features that use starlite to full extent and deliver better experience to starlite users while working with HTMX.

typing issue: this is mainly to avoid mypy errors. mypy cannot determine the return types in methods returning bool. I am searching for solutions to resolve it and will update it.

While I was writing examples for HTMXTemplate response, I got an error:
Value not declarable with JSON Schema, field: name='background_BackgroundTask' type=BackgroundTask required=True
My code is as follows:
@get()
async def handler(request: HTMXRequest) -> HTMXTemplate:
    return HTMXTemplate(name='partial.html', context={'context': request}, push_url='/partial')

How do I solve this?

I'll have to look at this - will take me a few days.

@jenish2014 - can you give me a snippet where you are stuck?

@all-contributors add @jenish2014 code docs


about limit of get_users_followers

I checked the source code and it looks like the method "get_users_followers" gets the data by scrolling the screen. However, after checking the twitter api and the followers displayed on the page, I found that I can only get the last 50 data, and even if I scroll down the page, no more data is generated. I would like to ask if it is possible to break this limitation or am I using it incorrectly?

I want to know too, I only got 50 users. Did you solve it somehow?


Upgrade odfe version to 1.13.0

Upgrade to ES 7.10.2
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

You might want to change here as well https://github.com/opendistro-for-elasticsearch/k-NN/blob/master/gradle.properties#L16.
Even though this field is not used but just to keep it consistent.

Ack.


links updated

Closes
Closes #1612

Description
proper links added

Screenshots

Note to reviewers

Checklist:

[x] I have linked the PR to the correct issue.
[x] I have read the Contribution Guidelines
[x] I have built and tested the changes, and they do not break or show any errors.

Hi @Divesh2003 bro please merged the pr


Deprecation notices related to nullable types for upcoming PHP 8.4

From https://github.com/slimphp/Slim-Psr7/actions/runs/9889214513/job/27314769934?pr=311:
Deprecation Notice: JsonSchema\Constraints\BaseConstraint::__construct(): Implicitly marking parameter $factory as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/BaseConstraint.php:41
Deprecation Notice: JsonSchema\Constraints\BaseConstraint::addError(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/BaseConstraint.php:46
Deprecation Notice: JsonSchema\Constraints\BaseConstraint::addError(): Implicitly marking parameter $more as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/BaseConstraint.php:46
Deprecation Notice: JsonSchema\Constraints\Factory::__construct(): Implicitly marking parameter $schemaStorage as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/Factory.php:76
Deprecation Notice: JsonSchema\Constraints\Factory::__construct(): Implicitly marking parameter $uriRetriever as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/Factory.php:76
Deprecation Notice: JsonSchema\Constraints\Constraint::incrementPath(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/Constraint.php:42
Deprecation Notice: JsonSchema\Constraints\Constraint::checkArray(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/Constraint.php:68
Deprecation Notice: JsonSchema\Constraints\Constraint::checkObject(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/Constraint.php:86
Deprecation Notice: JsonSchema\Constraints\Constraint::checkType(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/Constraint.php:103
Deprecation Notice: JsonSchema\Constraints\Constraint::checkUndefined(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/Constraint.php:119
Deprecation Notice: JsonSchema\Constraints\Constraint::checkString(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/Constraint.php:136
Deprecation Notice: JsonSchema\Constraints\Constraint::checkNumber(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/Constraint.php:152
Deprecation Notice: JsonSchema\Constraints\Constraint::checkEnum(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/Constraint.php:168
Deprecation Notice: JsonSchema\Constraints\Constraint::checkFormat(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/Constraint.php:184
Deprecation Notice: JsonSchema\Constraints\ConstraintInterface::addError(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/ConstraintInterface.php:43
Deprecation Notice: JsonSchema\Constraints\ConstraintInterface::addError(): Implicitly marking parameter $more as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/ConstraintInterface.php:43
Deprecation Notice: JsonSchema\Constraints\ConstraintInterface::check(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/ConstraintInterface.php:64
Deprecation Notice: JsonSchema\SchemaStorage::__construct(): Implicitly marking parameter $uriRetriever as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/SchemaStorage.php:19
Deprecation Notice: JsonSchema\SchemaStorage::__construct(): Implicitly marking parameter $uriResolver as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/SchemaStorage.php:19
Deprecation Notice: JsonSchema\Constraints\SchemaConstraint::check(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/SchemaConstraint.php:31
Deprecation Notice: JsonSchema\Constraints\UndefinedConstraint::check(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/UndefinedConstraint.php:34
Deprecation Notice: JsonSchema\Constraints\TypeConstraint::check(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/TypeConstraint.php:42
Deprecation Notice: JsonSchema\Constraints\ObjectConstraint::check(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/ObjectConstraint.php:30
Deprecation Notice: JsonSchema\Constraints\ObjectConstraint::validatePatternProperties(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/ObjectConstraint.php:54
Deprecation Notice: JsonSchema\Constraints\ObjectConstraint::validateElement(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/ObjectConstraint.php:93
Deprecation Notice: JsonSchema\Constraints\ObjectConstraint::validateProperties(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/ObjectConstraint.php:135
Deprecation Notice: JsonSchema\Constraints\ObjectConstraint::validateMinMaxConstraint(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/ObjectConstraint.php:177
Deprecation Notice: JsonSchema\Constraints\StringConstraint::check(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/StringConstraint.php:25
Deprecation Notice: JsonSchema\Constraints\FormatConstraint::check(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/FormatConstraint.php:27
Deprecation Notice: JsonSchema\Constraints\CollectionConstraint::check(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/CollectionConstraint.php:25
Deprecation Notice: JsonSchema\Constraints\CollectionConstraint::validateItems(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/CollectionConstraint.php:64
Deprecation Notice: JsonSchema\Constraints\EnumConstraint::check(): Implicitly marking parameter $path as nullable is deprecated, the explicit nullable type must be used instead in phar:///usr/local/bin/composer/vendor/justinrainbow/json-schema/src/JsonSchema/Constraints/EnumConstraint.php:25

@akrabat I suspect you need to update to 5.3.0 see https://github.com/jsonrainbow/json-schema/issues/730
If you need us to look into this in more detail please provide a more constructive issue report.

Search failed me when looking to see if this had been raised already.


Set up pre-commit hook for checking formatting

Refer #https://github.com/Real-Dev-Squad/website-www/issues/102 for more info
Please comment down to get this issue assigned to you 🙂

I ll take this up


DocC doesn't warn when a documentation file doesn't match a symbol

Description
When the symbol link in a documentation file doesn't match a symbol the content of that documentation file isn't used in the build and there's no diagnostic to inform the developer of this issue.
Checklist

[X] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue.

Expected Behavior
There should be a similar diagnostic for this as there are for other unresolved symbol links, but specific to the context of documentation extensions and more specific about this impact.
Actual behavior
No response
Steps To Reproduce
In a Swift package with a documentation catalog, add a documentation file and write an symbol link in the header that doesn't exist in the project:
# ``MyModule/ThisDoesNotExist

This content won't appear in the documentation

Swift-DocC Version Information
e135c5bd5c8f0e102f38b6303fec175c8db69e10
Swift Compiler Version Information
swift-driver version: 1.80.1 Apple Swift version 5.9 (swiftlang-<IP_ADDRESS>.11 clang-15<IP_ADDRESS>)
Target: x86_64-apple-macosx13.0

This could be a decent first issue but at the same time I may want to fix it sooner than later. I'll add the tag but I'll probably start working on this next week.

The work I'm doing for https://github.com/apple/swift-docc/issues/561 also addresses this issue so I'm removing the "good first issue" label