Added support for Webhooks

if Webhook is used the IV isn't checked by Pokeminer+
as for e.g. PokeAlarm does its own checks

Is there a particular feature of PokeAlarm that you want? I would rather improve my own notification system than support and maintain an external one.
I'm going to be re-removing the IV requirement soon.

well in this case slack

I would really appreciate if webhooks were officially supported. First of all PokeAlarm is a very fine tool, highly extensible, already offers several services and is nicely configurable (I am currently working on extending the notification rules to allow things like "notify if only X meters away (for candy) or if IV > 95% regardless of distance (for quality mons)" and I have made changes to push captcha notifications to users for manually solving them.
To be honest I find your (not sure if it's your invention) scoring algorithm way too complex to configure. I read through the example config and I still don't know how it works. The score defines the rarity and the rarest Pokemon will be notified, that's my (very basic) conclusion. And for my case this is not what I want. Your approach is good for generally notifying lots of people (e.g. via Twitter) but my use case is a handcrafted notification system that notifies me about Pokémon that I personally am interested in, may it be because I need the candy from nearby spawning mons or for high IV Pokémon. As such the notification system needs to know my location to calculate a proper distance, a problem that has been solved by PokeAlarm.
Personally I think the best solution would be a tool like PokeAlarm which is modular in a way that it offers the ability to plug in different decision modules that decide what to notify and what not (here your score system would fit in) and different notification providers (Twitter, Telegram, Slack, etc...) for those notifications (the latter already being provided by PokeAlarm).
And last but not least I prefer the unix way of services. Don't just create one tool that does it all but instead smaller tools that do exactly one thing but do it good! Pokeminer+ looks like it is a very nice scanner (not yet tested but ppl praise it more and more). Also people are currently coding different frontends for it which again shows you that it would not be the worst idea to even cut off the frontend and make it a separate project (ok, maybe including a basic frontend is an even better idea, so nevermind ;-)).

My main reservation is about adding in significant portions of code that I don't intend to test regularly (if at all). But I'll look this over when I get a chance. It would also be helpful if someone could confirm that this works.
I do intend to add in some different options for notification decisions, and hopefully more helpful documentation for them.

I intend to test Pokeminer+ this weekend and I will also test this PR. :)


use apache math libraries. delete custom gamma function computations

I deleted our custom gamma function implementation and replaced it with apache math.
@yfarjoun please have a look. should be trivial

Coverage increased (+0.13%) to 70.56% when pulling 48072a406823adf5c83dfc820be5c2ef6ee20af1 on ak_replaceCustomGamma_withApache into 1be971e166f3ca3843a01714efd9f8b543cc574e on master.

:+1:

thanks. will merge once test pass after rebasing

Coverage increased (+0.12%) to 70.56% when pulling 3bc39dff9c15857a757cf6d2a95b2f5e9d666393 on ak_replaceCustomGamma_withApache into 002aa43baefb0bc4c1bdf6ba9e55ab5b6f0b0b78 on master.


Documentation Update

Description
Go through the built documentation site and update as needed
More specifically, we want to :

add more relevant examples (langchain)
update examples to add the credentials object with api_endpoint
fix typos in PromptPattern Quick start
add documentation on the local server feature (the extension expects a user to define their model as shown in the example, ask james for more specific info)

Sphinx Documentation:

example section : group examples by functionality (add a new level/subsection)

templates will need to go under assets

Examples
  - Simple Examples (Getting Started)
        - Generate
        - Tokenize
        ...
  - Async Examples
  - Local Server (locally served models)
  - Prompts
  - Extensions
     - Langchain
     - Pandas
     - HuggingFace

Update example imports to import Credentials, Model, Metadata from genai (not genai.model)

from genail import Credentials, Model, Metadata

Action item :

@vedem1192  : Get back to Young and Mairead regarding which examples we want to add to the sphinx pages
@moneill0  : Sync with James for localserver tutorial and add it to Sphinx doc
@jayolee  :  looking into linking examples from the repo inside the sphinx doc (so we don't have to update in multiple places)

Update pre-requisites in the installation section of README with python and pip requirements @jayolee @moneill0

Update the model param of Model class's type hinting- Instead of being just ModelType, Union[ModelType, str]

Add example in the "Getting Started" section that import models by string name
Add a note in the readme.md (along with the pre-requisites) can import model with string

Add extension installation explanation link to the doc


raft: introduce progress states

for #2501

The PR implements the first part of #2501 . It introduces three states and the transitions between them.
TODO:

[ ] add becomeX test

Flow control is the next step.
/cc @bdarnell

LGTM!
/cc @bdarnell

LGTM


OSM Not Showing in "View/Open Map Window"

Hello! I am new to this software and have been learning how to use it and set it up through 3D City DB's official documentation. The current issue I am having is that when I open the Map Window utility for selecting bounding boxes, the OpenStreetMaps visuals will not load, rendering the utility unusable.

The only potential fixes I have been able to find for this issue seem to require adjusting the proxy settings in the preferences. However, the company computer I am using this software on does not connect to the internet through a network proxy. Can anyone suggest any fixes or troubleshooting steps I can take? Thank you in advance!

Thanks, @sschoenhardt. It is a known issue and has already been fixed (see https://github.com/3dcitydb/swingx-ws/commit/785aaa0122bccc007f45bc344ee187628427b2b5).
The fix will be included in the next release of the Importer/Exporter. If you need a working version earlier, then you can easily build it from the master branch following these steps: https://github.com/3dcitydb/importer-exporter#building

@clausnagel Thank you so much!

I am experiencing the same issue here. Will build from master as well. Thanks.

Thanks! I also built a new installer and the issue is gone. Just want to add that Grable requires Java's JDK and JRE running on the same version.

Closing this issue since the fix is now included in the 4.2.3 release.


Github bug/feature templates: Switch to forms

Is your feature request related to a problem?
Our issues templates sometimes lead to missing or wrongly input information.
Would be nice to fidn a way to "guide" a user through these when filing an issue.
Describe the solution you'd like
Currently we use simple templates for these.
Other projects use external services.
Zeus uses github but with a "form-generator":

See: https://github.com/ZeusLN/zeus/issues/new?assignees=&labels=Bug&template=bug_report.yml
https://raw.githubusercontent.com/ZeusLN/zeus/master/.github/ISSUE_TEMPLATE/bug_report.yml

@escapedcat Hey! I want to work on this.

Thanks @buneeIsSlo ! Assigned you. Let us know if you need any further info or feedback.

Hi! @escapedcat I've raised a PR, could you please take a look at it?

Hi! @escapedcat I've raised a PR, could you please take a look at it?

Saw it, thinking about how to test it. Eventually we're just gonna merge it and will do corrections if needed. Will let you know.

@escapedcat Got it! Thank you.

Thanks for you PR! I commented.


refactor: Adapt Challenger type in crypto modules

updates the pointer to plonky3 in Cargo.lock,
https://github.com/succinctlabs/plonky3/pull/27 updated SerializingChallenger32 to take a type parameter for an initial HashChallenger state,
Updates the Challenger type definition in the baby_bear_keccak and baby_bear_blake3 modules to reflect what typed is used there (u8).

[!NOTE]
A default type parameter, if used for T, may have made source changes unnecessary.

Thanks for the PR @huitseeker .  We actually just merged in a https://github.com/succinctlabs/sp1/pull/327 that contains your changes.


Dynamic Config Change improvement

Development Task
Today some changes cannot be dynamically changed and some can.  Because documentation is not accurate for whatever reason.
And customers feel frustrated because they don't know if the setting takes effect.
Each configuration has its own log message to indicate if the setting takes effect or not.  And that increase significant support cost as they must be very familiar with the code.
A few improvements:

In TiDB side, when running set config, we should provide explicit message telling TiDB the configuration takes effect or not.
In TiKV side, we should use unified log message to confirm that a specific config is changed and takes effect.

From SQL interface, if a config update is not successful(don't support or update failed), the sql will return a warning message like following:
mysql> set config tikv `server.addr` = "<IP_ADDRESS>:20158";
Query OK, 0 rows affected, 3 warnings (0.05 sec)

mysql> show warnings;
+---------+------+-----------------------------------------------------------------------------------------------------------+
| Level   | Code | Message                                                                                |
+---------+------+-----------------------------------------------------------------------------------------------------------+
| Warning | 1105 | bad request to http://<IP_ADDRESS>:20148/config: failed to update, error: "config addr can not be changed" |
| Warning | 1105 | bad request to http://<IP_ADDRESS>:20148/config: failed to update, error: "config addr can not be changed" |
| Warning | 1105 | bad request to http://<IP_ADDRESS>:20148/config: failed to update, error: "config addr can not be changed" |
+---------+------+-----------------------------------------------------------------------------------------------------------+
3 rows in set (0.02 sec)


localhost Not found [BUG]

Describe the problem
I have downloaded zip file from instead of git clone or not download the released versions.
Everything installed successfully. By launching http://localhost:5151 in the browser, I'm encountering Not Found error.
Code to reproduce issue
import fiftyone as fo
import fiftyone.zoo as foz

dataset = foz.load_zoo_dataset("quickstart")
session = fo.launch_app(dataset)

System information

OS Platform and Distribution (Linux Ubuntu 18.04):
Python version (3.8):
FiftyOne version (FiftyOne v0.24.0, Voxel51, Inc.):
FiftyOne installed from (source):

Hi @barzan-hayati. If you are using a source install of FiftyOne, I would double check the App is being built when using the install script.
https://github.com/voxel51/fiftyone/blob/7baa04b07a517e8a7c90073c8ca04d5440eb171e/install.bash#L133
A Not Found error usually means there is no built App in the fiftyone/server/static directory, which is what the above link accompishes


Don't allow readonly custom fields to be edited.

These already have all the necessary functionality, it just clutters the
UI.

Coverage remained the same at 96.889% when pulling 44ec1660548640aeec593e92eed0669e86009f08 on hide_readonly_fields into 64e87a2c726cd4383579480d1dec2617ea15cb1b on master.


Configure libtcmalloc_minimal based on shared libs setting

Added a switch to change the way we build libtcmalloc_minimal i.e. either a static library or shared library.
The build works successfully when tcmalloc is enabled (which is the default setting).

Thanks @navsan for debugging the issue.

@hbdeshmukh I've already merged it to master, but for some reasons, it does not close by asfgit.
Could you please close it? Thanks!

You mean close the PR right?


pull request for e2e test at 12/12/2016 13:15:03

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Typescript Definition File on DT

I understand this is maintained on DT - the issue is it's incomplete and I'm getting issues using wrappedComponentRef. There are posts from month's ago about the same issue on react-redux, so I don't expect it to be resolved soon.
Any ideas?

Unfortunately, we're not going to be able to help you here. You should open an issue via DT's support channels.

I managed to resolve the issue by first casting the component to any. Not ideal, but in the absence of any other alternatives:
// cast as any to bypass missing typescript defs
const SideMenuWithRefs = SideMenu as any;

I'm leaving this here so that anyone with the same issue with won't waste your (clearly) limited time 👎


New OAuth2 middlewares with token persistence

Fixes #2635
Replaces #2963
Currently the OAuth 2 middleware suffers from scalability issues as reported in #2635. Tokens obtained from the authorization server are stored in-memory in the Dapr runtime (a session ID is stored in a cookie on the client), so they do not persist if the runtime is restarted, and make it impossible to scale the application horizontally.
The most common solution to this problem is to store the tokens in the clients, as self-contained tokens such as JWTs; because tokens are sensitive, they are encrypted (using encrypted JWTs).
Two components
This PR rewrites the OAuth2 middleware and exposes 2 new components (which are mostly based on the same underlying implementation):

middleware.http.oauth2.cookie (aliased to middleware.http.oauth2 for backwards-compatibility)

Just like today's component, stores the JWT in a cookie that is passed to the client.
After successfully authenticating, users are automatically redirected to the endpoint they were visiting at the beginning

middleware.http.oauth2.header:

Requires the token (issued by Dapr and not by the IdP!) to be present in the Authorization header
When users authenticate successfully, the client sees a response with a JSON body containing a single key Authorization and the value of the Authorization header that clients must pass

Why 2 components?
The reason why we have two flavors of the component is due to the issue described in #2963. TLDR: tokens returned by Azure AD can be too large to be stored in a cookie.
However, using headers is not a perfect 1:1 replacement:

Cookies can set in a 302 response while the client is redirected to the original endpoint that was invoked. We cannot do that with headers
Cookies are handled automatically by browsers and other clients, while headers must always be handled manually

Token encryption key
Because cookies now store the token encrypted, users need to provide an encryption key via the new metadata property tokenEncryptionKey:

This property is required.
For backwards-compatibility, in Dapr 1.12 this property is optional and, if missing, a key will be randomly-generated by the runtime. When this happens, the key is ephemeral so tokens do not survive a restart of the Dapr runtime and horizontal scaling is not supported - this is pretty much what happens in Dapr 1.11 today! I have opted for allowing this behavior in Dapr 1.12 to offer a smoother transition period (even if the component is in alpha stage).
Technically speaking, tokenEncryptionKey is not the actual encryption key used: the Dapr runtime deterministically derives both a signing key and an encryption key from that

Future work

When dapr/dapr#6538 is implemented, we can use actors (if enabled) to store tokens when they're too large for a cookie. In this case, if the cookie is small enough, it's sent to the client as-is. Otherwise, Dapr stores the token in an actor's state, and then sends a session ID as cookie to the client; this is done transparently only for tokens that are too large to be included in cookies.
Add certification tests so the component(s) can be made stable. See #2621 .

Note that because this PR is essentially a complete rewrite, the components cannot be made stable until Dapr 1.13 at the earliest, even with certification tests

The middleware middleware.http.oauth2clientcredentials has the same issues with scalability as the OAuth2, and needs to be updated as well (and perhaps we can re-use the shared implementation of this middleware).

I remember the discussing being around keeping the existing component but having a flag instead to change the behavior. Any reason for the change of course?

I remember the discussing being around keeping the existing component but having a flag instead to change the behavior. Any reason for the change of course?

I have sent a message on Discord this morning saying that I thought it made more sense to have 2 components since the behavior is very different: one redirects, one doesn't; one works with browsers (because of cookies), the other one doesn't. I asked if anyone had objections and didn't get any.

I have sent a message on Discord this morning saying that I thought it made more sense to have 2 components since the behavior is very different: one redirects, one doesn't; one works with browsers (because of cookies), the other one doesn't. I asked if anyone had objections and didn't get any.

Going forward I advise to not equate 5 hours of no responses on Discord with an explicit agreement from everyone.

one works with browsers (because of cookies), the other one doesn't

That is not accurate and does not justify a new codebase with the additional maintenance overhead that it brings. The existing component does work with browsers and cookies, but as you pointed out recent changes in Azure AD breaks this scenario for that given provider.

one redirects, one doesn't

This change in behavior can easily be captured in the existing component without requiring an entirely new one.

Can we keep the previous decision?  It seems overkill to duplicate the component in this case. Even when we did duplicate it, like in etcd, the code is mostly shared, just the param at registration is different.

Can we keep the previous decision?  It seems overkill to duplicate the component in this case. Even when we did duplicate it, like in etcd, the code is mostly shared, just the param at registration is different.

Please review the code. Just like with etcd, the code is almost entirely shared. I am the first one that doesn't want to duplicate code :)
There just happens to be 2 folders, rather than 2 constructors in the same folder like for etcd, because I cannot put 2 metadata.yaml in the same folder

Closing in favor of #2967


Move adult diapers into adult incontinence

Summary
Adult diapers should be in adult incontinence, not disposable or cloth
Details
Change the methods on item for disposable, cloth, and adult incontinence so that adult diapers (both disposable and cloth) are in adult incontinence
Source
Conversation with Lynn Comer of NDBN, regarding the Annual Survey
criteria

[ ] items are in the right buckets, as described above
[ ] tests modified to conform with that, and pass.

Adult wipes were being counted into both.  Waiting on a clarification from Judi/Lynn

Update from slack conversation with Lynn.  Adult wipes should be other.

It also turns out that pads are being counted oddly.   Getting some stakeholder feedback on that.

I can take a look.

Thanks..  at the moment, though, this is waiting for some stakeholder feedback that came up while I was working on it (I’ve got it assigned to myself) There is some question about where Adult Liners should go because they some can be used as either adult incontinence or for period use.  Sent from my iPhoneOn 28 Feb 2024, at 13:14, Saravanan @.***> wrote:
I can take a look.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were assigned.Message ID: @.***>

I'm going to try to get clarity on the accompanying question around multiuse pads in Wednesday's meeting.  However I should be able to address this part of it independently.

Making a conscious decision to hold off on this until PR 4017 is in -- we'll need to make an adjustment with it and I don't want to hold it up any longer.

This has a PR, which needs a bit more work.

PR is waiting for review.


MADE CARD CLICKABLE

Description

Updates

Related Issues

Fixes #436

Changes

Added a new feature to cards.

DEMO
https://github.com/user-attachments/assets/baf91fbb-a97a-4c52-bd00-d2e179fba8a9
Checklist

[x] I have performed a self-review of my code
[x]  I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] I am working on this issue under GSSOC

@Soujanya2004 Requested to review PR..


After edit connection, it get out of its folder.

I have many connections to organize, so I create an structure as you can see bellow.


tests refactoring

Coverage remained the same at 94.862% when pulling 17fd77c5c5327f4cffde41998fac73467691e9eb on refactor_concurrent_tests_with_jcstress into 2cab37d3a821473c1c7fefb221842b980773478c on modularization.

Coverage remained the same at 94.862% when pulling 6f05c77359b5d8f1994f0fc9c5b57c9775829a7f on refactor_concurrent_tests_with_jcstress into 2cab37d3a821473c1c7fefb221842b980773478c on modularization.


build: use rollup-plugin-dts

Description

Use rollup-plugin-dts instead of @microsoft/api-extractor
Benefits:

No need to export internal types just to get api-extractor to bundle, which the internal props that relied on the internal types are stripped, but the internal types were still exported anyways
Faster builds
Lesser code
More type bundling control

Additional context

Original code referenced from https://github.com/vuejs/core/blob/main/rollup.dts.config.js
I'm not really sure why they use the renderChunk hook, I used the transform hook instead to strip the @internal types

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other

Wowzers that works! So much cleaner now


read a parquet file error

it reports
Error executing SQL: Error while reading parquet file: Error in c:/t/t.parquet
        Error while decoding row group 327 column chunk for column 'id' of type
'INT32' at offset<PHONE_NUMBER> of size 201495
        Decompressing compressed page of type 'DATA_PAGE_V2' at offset 141919627
9 with codec 'ZSTD' failed
        (compressed region offset:<PHONE_NUMBER>, compressed size: 193268, expected
 uncompressed size: 270339)
        Actual uncompressed size (262144 bytes) of ZSTD compressed data is less
than expected (270339 bytes)
Hint: The file is probably corrupt.
Context: 0xfa6b0e2f

both 'duckdb' and 'polars'  can read the same file.

Interesting find. Can you share the file with us?

it's too big(2.3GB), and I am trying to find a smaller exmaple.


[Vite] Bun with custom server doesn't work correctly

What version of Remix are you using?
2.2.0
Are all your remix dependencies & dev-dependencies using the same version?

[X] Yes

Steps to Reproduce

Create a simple vite.config.ts file:

import { unstable_vitePlugin as remix } from "@remix-run/dev";
import { defineConfig } from "vite";

export default defineConfig({
  plugins: [remix()],
});

Create a simple server.ts file with the following content:

import type { Serve } from "bun"

import { unstable_createViteServer } from "@remix-run/dev";

const devServer = await unstable_createViteServer();

export default {
  port: 3000,
  fetch: async (request) => new Response("Hello world!"),
} satisfies Serve;

Start the server:

bun run server.ts

Hit http://localhost:3000, you'll gonna see this screen:

If you comment the plugins: [remix()] line in vite.config.ts you'll see that the "Hello world!" message works as expected. So I think that the remix plugin breaks Bun HTTP server, even if I use the express template the problem is the same, the server will only work if the remix plugin is removed from vite.config.ts

Reproduction link: https://codesandbox.io/p/sandbox/bun-vite-remix-bug-rfps6n?file=/vite.config.ts:5,1-6,1
Bun version: 1.0.7
Expected Behavior
Vite server should work on Bun correctly
Actual Behavior
Remix plugin breaks Bun HTTP server

Seems to work on Bun 1.0.19 and Remix 2.4.1

Confirmed working w/ Bun v1.0.22 and Remix v2.5.0


Support for PMU event counters

Add support  for reading Arm PMU event counters through perf  framework and expose the readings  as a dedicated ftrace event.
This is being achieved by introducing new feature to the sched_tp kernel module for tracing the PMU event counters, plus changes to the lisa/tests/base.py, that handle the post-processing for CPU_CYCLES  counter events, which allows drawing conclusions on the estimated CPU frequency.
Additionally both util_tracking and load_tracking tests get amended to benefit from the above mentioned changes.

@bea-arm FYI I exposed feature parameters to lisa-load-kmod:
https://github.com/ARM-software/lisa/pull/1986

Drive-by comment: you might need to update any tracepoint probe you used to ensure their first param is a void *, as was done in that PR: https://github.com/ARM-software/lisa/pull/2044

Dropped changes validating expected frequency from Lisa tests.
Ongoing wok on supporting runtime configuration through vfs interface.

Closing as the project has moved to https://gitlab.arm.com/tooling/lisa/


3.9.2

So, the vinyl-fs dependency is behind the times quite a bit. I haven't had time to test this, but this would potentially remove the warnings of many npm gulp users...

https://github.com/gulpjs/gulp/issues/1571


Enhance coloring of org-files

So far, the coloring of org-files has been biased towards a heavy use of yellow. Overall, I didn't find its design very appealing or sometimes even misleading. This pull request is a try to fix these issues. The coloring is in parts inspired by doom one.
Design guidelines

Don't mash up too many colors.
Gruvbox' yellow and orange are very sharp colors, scale them back in favor of e.g. violet.
Red is one of gruvbox' trade mark colors, yet signals errors or urgent tasks. Try to integrate it unobtrusively.
TODO keywords should be distinguishable from each other.
The overview visibility should already look neat.
Consider documentation as well as personal organization files (with timestamps, drawers etc.)

Screenshots
The results look like the following (old version first):
Sample org file:

Overview:

lsp documentation:

Of course I'm open for discussion :)

Please take what I say with a grain of salt, but the fix could use more warmer colors. I think the current proposal is a bit too heavy on purple, making it look like the one dark theme instead.

You definitely got a point there. I think purple for level 1 headings looks fine, but turning org-links to purple might have been a bit overkill. They could be reverted to yellow, which makes the TOC very dominant, but that's ok then. Dates could be reverted to yellow, maybe also orange... I chose tags-face to have the color of comments, but that was also a rather personal choice. Any proposals?

My personal preference would be to mimic how the original gruvbox theme looks with markdown. One thing I noticed looking at the original version is that doom-gruvbox's yellow stands out more despite both using yellow for headings. I think the primary reason for this has to do more with how org mode is used, rather than the choice of color itself. Because we constantly fold sections with org mode, we would often see a large chunk of yellow dominating the buffer. So I guess as long as we don't use yellow as a top or second level heading, things would look a lot better.
Here's how the original gruvbox looks with markdown BTW:

I'm not quite sure with this one. I mean, Gruvbox is an "earthy" theme, so I think that the use of yellow is preferred over violet since it's a more earthy color.
Maybe you're right when you say we may be overusing it, but although I would be open to change the theme in order to use some other colors where yellow is being used, I think that yellow is ok as the "main color", and I would keep the heading 1 color yellow.
That being said, introducing some green, orange or red would be alright.
P.D. Sorry for the late response, I've been quite busy in several dimensions of my life these past few weeks.

I made the requested changes in cd1baec. In any case, thanks for bringing this to my attention!


YamlCreate Improvements

[x] Have you signed the Contributor License Agreement?

Resolves Trenly/winget-pkgs#178
Resolves Trenly/winget-pkgs#181

cc @denelon @russellbanks @mdanish-kh
Microsoft Reviewers: Open in CodeFlow

Depending on the implementation, + can sometimes get encoded as a space. Quickly testing this PowerShell code shows this happening to this too:
Add-Type -AssemblyName System.Web
$url = "https://github.com/adoptium/temurin17-binaries/releases/download/jdk-17.0.7+7/OpenJDK17U-jdk_x64_windows_hotspot_17.0.7_7.msi"
$decodedUrl = [System.Web.HttpUtility]::UrlDecode($url)
Write-Output $decodedUrl

https://github.com/adoptium/temurin17-binaries/releases/download/jdk-17.0.7 7/OpenJDK17U-jdk_x64_windows_hotspot_17.0.7_7.msi

Depending on the implementation, + can sometimes get decoded as a space. Quickly testing this PowerShell code shows this happening to this too:
Add-Type -AssemblyName System.Web
$url = "https://github.com/adoptium/temurin17-binaries/releases/download/jdk-17.0.7+7/OpenJDK17U-jdk_x64_windows_hotspot_17.0.7_7.msi"
$decodedUrl = [System.Web.HttpUtility]::UrlDecode($url)
Write-Output $decodedUrl

https://github.com/adoptium/temurin17-binaries/releases/download/jdk-17.0.7 7/OpenJDK17U-jdk_x64_windows_hotspot_17.0.7_7.msi

:o
Any other suggestions on what code to use then, other than the built in decode?

@SteveL-MSFT,
Any suggestions?

The easiest workaround without a different implementation would be to replace + with %2F before decoding, which will then get decoded back into a +.
This is the only instance of this behaviour because this is intentional when working with URL encoded forms.
Add-Type -AssemblyName System.Web
$url = "https://github.com/adoptium/temurin17-binaries/releases/download/jdk-17.0.7+7/OpenJDK17U-jdk_x64_windows_hotspot_17.0.7_7.msi"
$decodedUrl = [System.Web.HttpUtility]::UrlDecode($url.Replace('+','%2B'))
Write-Output $decodedUrl

Yep, just encode the URL before Decoding

Yep, just encode the URL before Decoding

Encoding the URL is unnecessary when you can just replace + with %2B as this doesn't happen with any other character


Need help understands View Archiving

Hey there,
Thank you very much for the great work and your contribution.
I am having a hard time understanding the logic behind archive and unarchive in TransitionDriver. It seems the we are unarchiving right after archiving. Is there any specific reason for this.

@mosn this trick allow you to copy view object. If you add any view to some other view, it leaves superview and becomes to new one. You can't have one view object in two hierarchies and therefore you must have a copy.


Is there a way to track number of conversations (not number of dialogues received) with Rasa Core ?.

Rasa Core version: 0.9
Python version: 2.7
Operating system (windows, osx, ...): Ubunute
Issue:
Content of domain file (if used & relevant):

The tracker_store keeps track of the sender IDs, which can be returned by its keys() function. You could try len(tracker_store.keys()) to get just the number of conversations, but that's really just returning the number of unique keys.

@foxjr  but this method will give the number of unique sender IDS which I already have. Each user may have multiple conversations with the agent at different times. i would like to get the number of unique conversations, not just number of unique senderIDs

Yeah, true. It depends on your use case, but the simplest way may be to create a small custom action that occurs only at the start of every interaction that increments a counter (or counts by some other mechanism).

@foxjr  I am using something similar as you suggested right now, but I need a more solid method 🏭

Maybe create your own tracker class that counts by some mechanism, both when initialized and when reset.


[PE-D][Tester C] Syntax for "delete" in User Guide doesn't match actual command syntax

The User Guide states that day/ is the tag used to specify the day of the lesson, but this doesn't work in the app and d/ works.

Labels: type.DocumentationBug severity.Low
original: kaij77/ped#4

duplicate


Rewrite page for Linux

Please provide the "deb" line so that I can update my "/etc/apt/sources.list". Then provide the "apt-get download" command line so that I can install this product.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8cfd5cf0-f28e-be49-227a-c2bbe4e57b8d
Version Independent ID: 016b2a9c-d1c9-6909-df3e-a49db60b7654
Content: Prerequisites for .NET Core on Linux
Content Source: docs/core/linux-prerequisites.md
Product: dotnet-core
GitHub Login: @JRAlexander
Microsoft Alias: johalex

@lukeperkins Click on the appropriate install link and it will take you to the download page which has those instructions.

Closing as this appears resolved.


OpenVPN 2.4.0 stable - Encryption improvements

Hey,
finally 2.4.0 seems to be there!
https://build.openvpn.net/downloads/releases/openvpn-2.4.0.tar.gz
Will you extend the installer to support TLS 1.2 by default et cetera?
Cheers

When it will be available in the repos yes

I am so looking forward to it! You have done a great job with this repo. I am excited how big the speed difference really is in the end, especially when ran on low end hardware (like travel routers)

Also,  please look in to the new option - - TLS-crypt    as this looks like an replacement to tls-authkey and is suggested here in the below link
https://community.openvpn.net/openvpn/changeset/c6e24fa3e16c32f9b427e360fd07102f613aa5c6/

I believe it is available now. I could install it fine on Ubuntu 16.04
https://community.openvpn.net/openvpn/wiki/OpenvpnSoftwareRepos
I had added the package repo [](http://build.openvpn.net/debian/openvpn/stable xenial) main and the version number reads OpenVPN 2.4.0 x86_64-pc-linux-gnu

I believe it is available now. I could install it fine on Ubuntu 16.04
https://community.openvpn.net/openvpn/wiki/OpenvpnSoftwareRepos
I had added the package repo [](http://build.openvpn.net/debian/openvpn/stable xenial) main and the version number reads OpenVPN 2.4.0 x86_64-pc-linux-gnu

It's available for Ubuntu, Debian and Arch. Waiting for CentOS (via EPEL ?)

It's available for Ubuntu, Debian and Arch. Waiting for CentOS (via EPEL ?)

I'll probably have to change more things for Arch tough : https://www.archlinux.org/news/openvpn-240-update-requires-administrative-interaction/

Hey guys, please check out PR https://github.com/Angristan/OpenVPN-install/pull/33 for the OpenVPN 2.4 update (WIP)


Add test to verify that base dashboard app config inherited properly.

Test for PR #2003

Current coverage is 84.20% (diff: 100%)

Merging #2160 into master will decrease coverage by 0.03%

@@             master      #2160   diff @@
==========================================
  Files           304        304
  Lines         15091      15091
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits          12713      12707     -6
- Misses         2378       2384     +6
  Partials          0          0

Powered by Codecov. Last update 5445da6...defbb6c


Read-only instance

This PR is intended to fulfill #195.
This PR is based on #238. To get the relevant commit for this PR, merge the master branch into the associated branch after #238 is merged into the master branch.

@yarikoptic A read-only instance of Datalad-Registry is now on Falkor.

Per @yarikoptic's recommendation, it may be a good idea to respond 405 Method Not Allowed instead of 418 I'm a teapot in the event of a user posting to the declare_dataset_url endpoint.


getMarkerEnd returning an incorrect id

Describe the Bug
Hey, I've started to use getMarkerEnd to get a closed arrowhead marker to use within my custom edge. It seems the returned string is unrecognised as no marker end is rendered.
// ... CustomEdge.tsx
      <path
        id={id}
        style={style}
        className="stroke-gray-400"
        d={edgePath}
        markerEnd={getMarkerEnd(MarkerType.ArrowClosed)}
      />

Further, if I provide the markerEnd through the edge structure, e.g.
const edge = {
        id: someId,
        source: node.id,
        target: destination,
        type: edgeType,
        markerEnd: { type: MarkerType.ArrowClosed },
}

I noticed there's a slight difference in the strings:

url(#1__type=arrowclosed) <- passed down from edge structure
url(#react-flow__arrowclosed) <- retrieved from getMarkerEnd

Your Example Website or App
No response
Steps to Reproduce the Bug or Issue

Define a custom edge
Use getMarkerEnd to retrieve closedArrowhead for path's markerEnd
No Arrow head is rendered on edge as the url id is invalidArrowhead

Expected behavior
I expect to see an arrowhead being rendered on the edge.  There's a mismatch between markerEnd strings:

url(#1__type=arrowclosed) <- passed down from edge structure
url(#react-flow__arrowclosed) <- retrieved from getMarkerEnd

Screenshots or Videos
No response
Platform

OS: [Linux]
Browser: [Chrome]
Reactflow Version: [11.3.0]

Additional context
No response

I hope I didn't misunderstand you but here are my thoughts:
So, for markers to work, you need to define them in your edges, otherwise there will be no marker definitions you can reference via url().
Meaning, what you describe as "providing through edge structure" is required for the marker to appear.
Furthermore, when you have defined a marker and want to use it in a custom edge, the url is already provided to your custom edge as a prop so using getMarkerEnd is superfluous.
Check this example and open the CustomEdge.js file, you can see that there is no getMarkerEnd call, you just pass the markerEnd prop to your path and that's it.

thanks @bcakmakoglu 🙏

Yes, you're correct!
Thanks!


Added staff email trigger alerts handling

refs https://github.com/TryGhost/Team/issues/1826
Note: WIP changes

Closed in favor of https://github.com/TryGhost/Ghost/pull/15311


Matching with parameterized start rule does not work

grammar.match(input) can be passed a second, optional rule name to start parsing the input from that rule.
Currently parameterized rules like Foo<arg> cannot be use and matched. This turns out to be a specific problem with e.g. the ES5 grammar where <guardIn> is used now.
For the ES5 grammar, a call with a reference to a defined rule (instead of a specific value) would be necessary/sufficient:
g.match('1+2', 'Expression<withIn>'); for Expression<guardIn>

A possible (tried) solution would be to:

extend Grammar.prototype.match(obj, optStartRule) with a third, optional prototype that takes an array of arguments,
forward those parameters via opts.actuals to Grammar.prototype.match(values, startRules, opts) and call the Apply with those actuals as args.

That would mean that the describe call for ES5 could be:
g.match('1+2', 'Expression', [new ohm.pexprs.Apply('withIn')]);
Another approach could be to parse the optional rule name into rule name and parameters to be able to call g.match('1+2', 'Expression<withIn>') without knowledge about the pexprs interface.

I can see how this would be useful for debugging, but do you have another use case in mind? Having a specific example would help in deciding on a solution. I think both of things you proposed could work.
If we think it's something that people will want to use for test cases in the editor (and I think it is), then the second solution might be best, because in that scenario I'd imagine people won't be writing the g.match(...) code directly...they'd have a combo box or something where they can pick a start rule. In that case, I think expressing the start rule in terms of Ohm syntax (rather than JS syntax) is a better fit.

Another approach could be to parse the optional rule name into rule name and parameters to be able to call g.match('1+2', 'Expression') without knowledge about the pexprs interface.

I like this option much better than the first one, because as you said, it doesn't require knowledge of the pexprs interface. It also seems to work better for the Ohm visualizer / editor, as @dubroy noted.
@mroeder: I'd be happy to give you a hand with this if you'd like. Let me know :)

@pdubroy: The topic came up yesterday with @sakekasi who wanted to parse ES5 expressions for the semantic actions to determine whether there is an implicit return or an explicit one.
But I also think that it would be of good use in the editor.
I will get working on it and have you take a look afterwards...

Fixed by ec1dd5c8b8f9193b1e4fca85dd12a6292a82eec4 and 2ad952d7cb97e6d2c11b1c223992bec13c010f7e.
Thanks @pdubroy!


Change Grouping to be typed and use Aggregators

(Untyped) UDAFs are known to be slower than (typed) Aggregators when complex types (Array, Map) are involved. Since Properties are in a Map, this will hopefully help performance. Aggregators are also the new default in Spark 3.0.

Change KeyFunctions from Columns to functions
Change UDAFs to Aggregators
Change AggregationFunctions from Columns to TypedColumns
Integrate in Grouping

GroupByKey is not flexible enough to use programmatically. There doesn't seem to be a way to use Aggregators with untyped groupBy yet.


Fix gatsby mocks

Fixes https://github.com/wayfair/awesome-learning/issues/123

Thank you for the fix, but this PR breaks a bunch of our tests. I addressed these issues in a similar pull request: #165


pipeline.py: create dummy inputs if pipeline begins with an input stage?

Normally, one would run flux -> osc -> etc. However, it's possible one would want to test osc -> etc. As of now, "dummy" inputs are only generated in the case that the user specifies --only-stage. Is it a good idea to accommodate the above scenario, or might that lead to the user running an invalid pipeline? Or should --dummy-inputs be another argument to pipeline.py script so that the user must explicitly choose that behavior, and then create these whether or not --only-stage is specified? Note that --only-stage for an inputs-stage will require the generation of dummy inputs, until such time as we can get inputs from a file (another TODO!).

I don't think this case is really needed to be covered..


feat(streaming): monitor materialize cache miss rate when handling pk conflict

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Add metrics to monitor materialize cache miss rate. Run a test by datagen connector, and set pk range (1, 10000), 100 rows per second, and cache hit rate increases close to 100% over time.
close https://github.com/risingwavelabs/risingwave/issues/8738
test case
CREATE TABLE metrics (
    id int primary key,
    num int,
) WITH (
    connector = 'datagen',
    fields.id.kind = 'random',
    fields.id.min= '1',
    fields.id.max= '10000',
    fields.num.kind = 'random',
    fields.num.min= '-100',
    fields.num.max= '100000',
    datagen.rows.per.second = '100'
);

dashboard:

Checklist For Contributors

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] I have demonstrated that backward compatibility is not broken by breaking changes and created issues to track deprecated features to be removed in the future. (Please refer to the issue)
[ ] All checks passed in ./risedev check (or alias, ./risedev c)

Checklist For Reviewers

[ ] I have requested macro/micro-benchmarks as this PR can affect performance substantially, and the results are shown.

Documentation

[ ] My PR DOES NOT contain user-facing changes.

Click here for Documentation
Types of user-facing changes
Please keep the types that apply to your changes, and remove the others.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note

you may try without specifying row format to achieve better datagen performance

Can you rebase main and also add this metrics to the "Executor Cache" panel in user dashboard?
https://github.com/risingwavelabs/risingwave/blob/f1b7942b92af4a0131784167b59aa0da27ab2d9c/grafana/risingwave-user-dashboard.dashboard.py#L193

dashboard

Sure, thanks for reminding。

For user dashboard

Maybe we should refactor this dashboard to show cache miss ratio instead of count(ops/s), will fix it with https://github.com/risingwavelabs/risingwave/issues/9020 in the next PR.

For user dashboard
Maybe we should refactor this dashboard to show cache miss ratio instead of count(ops/s), will fix it with #9020 in the next PR.

Although showing miss ratio is more intuitive but showing ops gives more information to user since executor QPS can be inferred from cache lookup qps. I think we should still keep the cache ops panel and we can add a new panel for cache miss ratio.

just add another panel for the cache miss ratio (join, agg, materialize) and keep the ache ops for materialize.


Canonicalize standard_coders.yaml booleans

Before this change: standard_coders.yaml uses "True" and "False for booleans, which in YAML 1.2 parse as strings since lenient boolean forms are removed
After this change: only "true" and "false are used

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[x] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Java PreCommit

I happened to be messing about with Rust and discovered that its most popular YAML library parses these as strings and not bools. I could adjust in the code, but seems like canonicalizing our file is simpler and better.

Ack, thanks for the context. I look forward to your Rust SDK prototype :)


Improvements to help make Datasette a better tool for learning SQL

Tracking issue for the general goal of making Datasette a better tool for learning SQL.

The existing flow where you can apply filters to a table and then click "View and edit SQL" to see the query is a good starting point.
Group by queries are both crucially important and difficult to assemble for beginners. Providing a way to see the query that was used by a facet (since facets are really just group-by-counts) would be very useful, which could come out of this:

#1080

Tool for setting up foreign key relationships. It can even verify the relationship before you apply it - checking that every value in the column does indeed correspond to a value in the other table.
Could also detect and suggest possible ones.

Joins are really hard. A mechanism for constructing views in the table view would help a lot:

https://github.com/simonw/datasette/issues/613

Better contextual help on the SQL editor - like in Django SQL Dashboard which shows all available tables and columns.
Fancy inline autocomplete would be great too, but that's pretty hard for SQL based on past research.


541-improve-property-transformation-section

This resolves issue https://github.com/CodeForPhilly/vacant-lots-proj/issues/541
I updated the Content Card component to include an optional arrow icon and apply a hover style. I wrapped the card in a link tag because in the Figma the whole card is click-able.

@Amberroseweeks  please take a look

@Amberroseweeks please take a look

@Moylena thank you! This branch should now be updated, please review @paulhchoi and @thansidwell

@Amberroseweeks @paulhchoi From a design standpoint it all looks good in the preview for me!
But it appears to have conflicts that need resolving. And Paul is requesting the changes. I'll let you two work what need to happen.

Thanks @paulhchoi and @thansidwell , I just pulled from staging to merge and resolve conflicts, let me know if there is still an issue


adds TextDiagramDrawer.horizontal_cut

Needs to be synced with recent changes to text diagram drawer.

Still needs to be synced with recent changes to text diagram drawer. I will close in two weeks if no activity.

@Strilanc It only makes sense to get this up to date if we're going to implement my proposal for drawing outline boxes in #1226, of which this was meant to be a first step. I know you had alternative ideas about how to proceed, so let me know.

This seems to have grown stale.  I'm closing.  If it can be salvaged, please open a new PR.


about side face

hi, bro, used my own training data which contains some side face data to training, then i found some odd output on the result folder.
when the person show front face, the odd things do not appear, but when person turn face, the odd things appear.

are there some wrong in my dataset? but i found nothing wrong on my data image from video. what should i do next?

@StawEndl Hi, this method doesn't perform well for side face (since it's rarely observed in the monocular training video). However, the shadow-like artifacts on the second example is abnormal. How long is your training video?

my whole video is 2 min long, this is me part-data-video:
https://user-images.githubusercontent.com/55580043/208333147-420f8958-0c7f-412a-8325-60879d68f0d9.mp4
and this is my output video:
https://user-images.githubusercontent.com/55580043/208333310-30e0954d-1058-44c6-a07c-7f569bf8c8b8.mp4
are there some wrong with my data-video? thanks for your help.

@StawEndl The data seems OK, though it's a little short.

Could you check if the semantic segmentation of face is correct? The test video quality is under expectation...
You could also check the GUI and turn the face to side (like obama). To me it seems the depth (z-axis) is not long enough and the face is flat, but I cannot assure.
Yes, the obama.json is in fact the same as transforms_train.json.

@StawEndl The data seems OK, though it's a little short.

Could you check if the semantic segmentation of face is correct? The test video quality is under expectation...
You could also check the GUI and turn the face to side (like obama). To me it seems the depth (z-axis) is not long enough and the face is flat, but I cannot assure.
Yes, the obama.json is in fact the same as transforms_train.json.

nice, thanks. i use your model as pretrained model, and that's better.
i would like to know, i should run "python main.py data/obama/ --workspace trial_obama/ -O --iters 200000", then run "python main.py data/obama/ --workspace trial_obama/ -O --iters 250000 --finetune_lips", or just run "python main.py data/obama/ --workspace trial_obama/ -O --iters 250000 --finetune_lips"?

@StawEndl You should run the two commands sequentially.

@StawEndl The two commands should be run sequentially, the second command is a finetuning phase for another 50k steps.

yes,thanks. i run that two commands, without pretrained model, inference output video is nice, and there are nothing wrong about the face like that which was described at my first question.

Of course! I have updated the readme. Thanks for the suggestion!


PostgresqlMetadata works very-very slowly

in the class Zend\Db\Metadata\Source\PostgresqlMetadata method loadTableNameData works very slowly.
It generate query:
SELECT "t"."table_name", "t"."table_type", "v"."view_definition", "v"."check_option", "v"."is_updatable"
FROM "information_schema"."tables" t
LEFT JOIN "information_schema"."views" v ON "t"."table_schema" = "v"."table_schema" AND "t"."table_name" = "v"."table_name"
WHERE "t"."table_type" IN ('BASE TABLE', 'VIEW') AND "t"."table_schema" = 'public'

query result: 438 rows 2160 ms!
Why make a selection from the database all the tables when we need all the data on a single table?
Perhaps you need to cache?

Mine took 5.8 seconds on 239 tables :D (used jira database as test)
Indeed, this is a problem if used to find details for a single table. But for that, general getTables() is not justified. If you use
$table = new TableGateway('tableName', new MetadataFeature());

Then resultant queries have WHERE "t"."table_name" = 'tableName' injected which cuts down on execution time pretty well to 20-40ms (although still has large execution plan). Not ideal if you want to make all table gateways dynamic.
Or do you want to use this for a different purpose?
I would be very reluctant to add caching at framework level for this. Some uses, such as db migrations or admin tools in general need to have most up to date database info. It should be up to me in my application logic to dictate what is safe to assume will not change. Improved API that narrow's down query size would be better.
So I will ask if the forthmentioned usage through table gateway, which minimized the query down to a specific table and allows you to get info about it from table gateway object, is enough for you. Or if you need to get metadata specifically through $meta = new Metadata($adapter); $meta->getTable('tablename'); can think about improving current API to let user ask same questions as table gateway can (which are currently hidden in protected methods).

Because in my project does not use db view I solved the problem simply (custom PostgresqlMetadata):
class PostgresqlMetadata extends \Zend\Db\Metadata\Source\PostgresqlMetadata
{
    /**
     * {@inheritdoc}
     */
    public function getTable($tableName, $schema = null)
    {
        $table = new \Zend\Db\Metadata\Object\TableObject($tableName);
        $table->setColumns($this->getColumns($tableName, $schema));
        $table->setConstraints($this->getConstraints($tableName, $schema));
        return $table;
    }
}

That is a clever solution to one off usage like this (with no tablegateway) . Thank you for sharing!

This problem is starting to affect me to in my migrations project having these queries run on every page request.  With some research turns out information_schema implementation for sake of compatibility with ANSI SQL has too many internal joins causing massive execution plan even on smallest of databases. Its basically a view over actual catalogue tables.  Since Zend DB has a platform specific override for metadata, usage of this very slow abstraction may not be justified. Abstraction on top of abstraction. However, if we query against catalogue directly there is a possibility postgresql may change them between versions and we have to chase those. I do not know how much, if at all, it changes.
Anyway, for now, can I please ask you for a favor and instead of first query you posted run
SELECT
c.relname as table_name,
CASE
    WHEN c.oid = pg_my_temp_schema() THEN 'LOCAL TEMPORARY'
    WHEN c.relkind = 'r' THEN 'BASE TABLE'
    WHEN c.relkind = 'v' THEN 'VIEW'
    WHEN c.relkind = 'f' THEN 'FOREIGN TABLE'
END AS table_kind,
CASE
    WHEN c.relkind = 'v' THEN (select pg_get_viewdef(c.relname, true))
END as view_definition
FROM pg_class c
    JOIN pg_namespace n
        ON n.oid = c.relnamespace
WHERE n.nspname = 'public'
AND (c.relkind = 'r' OR c.relkind = 'v')

And see (1) you do not lose any data and (2) it executes fast enough to be considered as a viable replacement?
(This does not yet include last 2 columns used by ZF Metadata, check_option, and is_updatable, I really want to see if this would help at all before researching what those are ).
That query has less joins and scans to go through without going through ANSI abstraction (screenshots included for comparison).

If this is worth it and maintainers believe doing own implementation of queries without ANSI is safe for us to do, I could consider to try converting other monsters too.

P.S. Maybe also consider lazy loading some of table properties, like constraints and columns. I feel full metadata detail queried at once will still cause huge execution plans, even if avoid information_schema. In my current usecase I just need table name, yet I have column and constraints queried too. Maybe those class properties can be replaced with lazy loading proxies instead of populated ahead of time. Then if anyone does hit those getters, multiple SQL quries will still be more performant than those huge things.
Anyway, looking forward to your result, if you can.

OO OO this one is even faster!
SELECT
c.relname as table_name,
c.relkind as table_type
FROM pg_class c
WHERE c.relnamespace = (SELECT oid FROM pg_namespace WHERE nspname = 'public')
AND (c.relkind = 'r' OR c.relkind = 'v')

Without a join, there are only 38 rows to work with. Annoyingly, fields needed from pg_* tables are not indexed.

Wondering why performance on DDL is relevant here: never had
performance-specific questions in doctrine's schema tools, and the overhead
is similar...
On 4 Jan 2017 1:54 a.m., "Sasha Alex Romanenko"<EMAIL_ADDRESS>wrote:

OO OO this one is even faster!
SELECT
c.relname as table_name,
c.relkind as table_type
FROM pg_class c
WHERE c.relnamespace = (SELECT oid FROM pg_namespace WHERE nspname = 'public')
AND (c.relkind = 'r' OR c.relkind = 'v')
[image: table names plan comparison subquery]
https://cloud.githubusercontent.com/assets/3820828/21628513/1a72323e-d1ee-11e6-97af-f72ca7f21191.png
Without a join, there are only 38 rows to work with. Annoyingly, fields
needed from pg_* tables are not indexed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/zendframework/zend-db/issues/199#issuecomment-270268464,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJakIAewVNk40maZmkekRUwQrF9COi7ks5rOu3ggaJpZM4LGaYi
.

That's why I dismissed it at first too. DDL is either one time thing or a database admin utility (for whatever reason), both of which usecases have no need to be that performant. I've seen metadata used as part of page load to check whether database version is "safe" to use against what application expects, but that too was mostly for convenience during dev and is trivial to do manually.
What got me worried was other features that use metadata without users realizing inadvertently running extra queries. MetadataFeature for TableGateway, example I can think of right now, allows to populate table gateway class instance with details for operating it, such as what column is primary key, is auto_incremented so inserts/updates do not cause conflicts.  So if instead of manually describing to table gateway the structure of the table in constructor as one typically should, they just throw new MetadataFeature()  as the framework encourages to do, given the existence of this thing, and this is done for every table in application, can get explosive. I wouldn't do it, but I can see others do it. I too am curious about original poster's usecase, just how important is this?

Sorry, never mind about auto_increment thing. I mixed it up with sequence feature that does that. I do not THINK table gateway does that on its own, in which case purpose of automatically populating its column fields seems less important, but it still gives option to do so for whatever reason.

While I agree that a more through analysis of query performance should be done, the query you provided worked perfectly for me.
I opened #321 so others could benefit from the performance improvement.


Update AQE tests to support Spark 3.4

Closes https://github.com/NVIDIA/spark-rapids/issues/7054
Spark 3.4 has a slightly different plan for writes. The write is inside AdaptiveSparkPlan rather than the write having AdaptiveSparkPlan as a child. This PR updates the tests to change the expected result depending on Spark version.


maybe add lodash.camelCase

for their latest release (1.2.1), redux-actions removed lodash.camelCase: https://github.com/acdlite/redux-actions/releases
this means that the namespaced constants created by redux-define come with a "/" when used with redux-actions. Example:
const app = defineAction('app');
const START = app.defineAction('START').ACTION;
const actions = createActions({}, START);

will produce actions.app/start as the action creator name
I can call camelCase in my code, but need to do it for every defineAction.
do you any suggestion? thanks

Are you saying that also the behavior of createAction changed? Somehow it's hard to believe they are manipulating typenames to be something else than I provide.
What is the outcome of:
createAction('app/START');

It used to be:
{ type: 'app/START', payload: .... }

createAction stayed the same.
it's createActions that has changed: the keys of the object returned by createActions are not camelCased as they used to be

I've looked into createActions, and I understand your trouble. I'm not sure if this is something this library should be fixing, and when we do; how to solve this while maintaining backwards compatibility.
The problem is not really in the created action, but more in the construction of this collection object (don't know how to name this differently).
I've created a test-sample here: https://runkit.com/smeijer/redux-define---issues-2, as you can see, the returned action is still:
{
  "type": "app/START",
  "payload": {
    "foo": "bar"
  }
}

It is the actions object that has a naming like:
actions = {
  'app/start': () => ({ ...... }),
}

Do you have a suggestion on how to make it more easy for you?

I solved it in our code, with a helper function, like this:
in _helpers.js
import _camelCase from 'lodash/camelCase';

export const actionsNames = (_actions) => {
  const actions = {};
  for (const action of Object.keys(_actions)) {
    actions[_camelCase(action)] = _actions[action];
  }
  return actions;
};

in constants.js
import { defineAction } from 'redux-define';

const app = defineAction('app');
const START = app.defineAction('START').ACTION;

in actions.js
import { actionsNames } from './_helpers.js';

const actions = createActions({}, START);
export default {
  ...actionsNames(actions),
};

I think your workaround is sufficient for now. I decided to not change anything about casing. It's not up to this library, nor up to redux-actions in my opinion. We just compose what the user is giving us.


Turn off Debug mode, allow remote access and add dockerfile

Hey @Merlyn42 thank you for the contribution.  I assume this has been tested? :) Specifically the Dockerfile? Thanks for catching the debug

Also could you add to the README.md a docker-compose and/or docker run example command to use the Dockerfile?

@Daxiongmao87 Well it worked for me 😄 . I've added the instructions

ill review and possibly merge tonight!


WIP

Use bazel's %workspace% placeholder instead of using the hard coded /work path.
Modified update-envoy-sha.sh script to understand the upstream branch names
Added the config.yml to disable issues in the repository
Removed the upstream envoy  pull request template
Add maistra directory to .bazelignore
Use the system java rather than have bazel build it.
Update the references to envoy-openssl repository
Don't link against the system libcrypto.so

Note that maistra/bazelrc-vendor is updated but the maistra/vendor directory is not committed yet i.e. you will have to run maistra/scripts/update-deps.sh script to fetch them before you can build with maistra/ci/pre-commit.sh

Closing as it was superseded by other work


windows cmake boost and gtkmm-3.0 error

On windows 10, after following the directions on the wiki i recvd this error. Note: I had to use Unix Makefiles and not MSYS Makefiles because MSYS Makefiles did not exist as an option with cmake from msys.
$ cmake -G"Unix Makefiles" -DCMAKE_INSTALL_PREFIX=/mingw64 ..                          liblldb not found. Building juCi++ without debugging support
CMake Error: Error in cmake code at
/usr/share/cmake-3.6.2/Modules/FindBoost.cmake:1805:
Parse error.  Function missing ending ")".  End of file reached.
CMake Error at CMakeLists.txt:53 (find_package):
  find_package Error reading CMake code from
  "/usr/share/cmake-3.6.2/Modules/FindBoost.cmake".

-- Checking for module 'gtkmm-3.0'
--   No package 'gtkmm-3.0' found
CMake Error at /usr/share/cmake-3.6.2/Modules/FindPkgConfig.cmake:424 (message):
  A required package was not found
Call Stack (most recent call first):
  /usr/share/cmake-3.6.2/Modules/FindPkgConfig.cmake:597 (_pkg_check_modules_int       ernal)
  CMakeLists.txt:56 (pkg_check_modules)

Try install mingw-w64-x86_64-cmake and run cmake in the MINGW64 shell.

This seemed to work in installing. Have to remember to open the MSYS64 console though.
However when trying to run juci.exe, getting
"The procedure entry point: DllMain could not be located in the dynamic link library C:\msys64\mingw64\bin\libgtksourceviewmm-3.0-0.dll"
Do i need to install gtk manually and move the dll's over to msys?

See #289, the solution is to rebuild gtksourceviewmm3. You need to run juci in a MINGW64 shell as well I think.

So i reinstalled all the packages including gtksourceviewmm but still does not run. In MSYS window it just opens and closes. When running not in MSYS it says the above error.

@Triangle345 see this comment I had the same issue, and running these commands fixed it

I see, thank you. Must have missed this while skimming through the issues.


Enhancement: spo site set enhance logo options

Right now, when you use siteLogoUrl in the spo site set command, it changes the thumbnail, not the actual logo of the site. Looking at the command's inner workings, it seems the body sent to _api/siteiconmanager/setsitelogo is missing a few things. With some tweaks to this endpoint, we should be able to modify the thumbnail and the logo as well. Let's add another option and adjust the command a bit.

Option
Description

--siteThumbnailUrl [siteThumbnailUrl]
Set the thumbnail for the site collection. This can be an absolute or relative URL to a file on the current site collection.

The request options for _api/siteiconmanager/setsitelogo should look like this:

To update the thumbnail:

const requestOptions: CliRequestOptions = {
  url: `${args.options.url}/_api/siteiconmanager/setsitelogo`,
  headers: {
    accept: 'application/json;odata=nometadata'
  },
  data: {
    aspect: 0,
    relativeLogoUrl: thumbnailUrl,
    aspect: 0
  },
  responseType: 'json'
};

To update the logo:

const requestOptions: CliRequestOptions = {
  url: `${args.options.url}/_api/siteiconmanager/setsitelogo`,
  headers: {
    accept: 'application/json;odata=nometadata'
  },
  data: {
    aspect: 1,
    relativeLogoUrl: logoUrl,
    aspect: 0
  },
  responseType: 'json'
};

So just to confirm it the only difference is the aspect 🙂? But is it actually that we have it defined twice in the data 🤔?
Let's not show an example using any but instead let's use CliRequestOptions .

I don't know why but aspect is the golden property to differentiate a logo from thumbnail and regular logo

I don't know why but aspect is the golden property to differentiate a logo from thumbnail and regular logo

ok but now we have it twice:
data: {
    aspect: 1,
    relativeLogoUrl: logoUrl,
    aspect: 0
  },

won't this work?
data: {
    aspect: 1,
    relativeLogoUrl: logoUrl,
  },

other than that seems ok and lets open it up for hacktoberfest 👍

My bad, the last param shouldn't be aspect but is type. I updated the specs.

My bad, the last param shouldn't be aspect but is type. I updated the specs.

No problem. Seems legit now 👍.
Let's open this up. Thank you @Jwaegebaert for the awesome suggestion 👍

please assign to me to attempt implementing it.

All yours @reshmee011 💪


General Bug Collection

Hey, so first of all I wanna say that this is a really cool mod, I wish this concept was in the base game.
There seem to be quite a few bugs still even in vanilla which I'd document here. And while I realize that this is still a beta, a comprehensive list may be able to help. Tested using 2.0.1-beta.2 in 1.20.1:
Lava related

Lavalogged blocks of source, flowing or falling type don't set fire to any other blocks
Fire can place itself in lava when it spreads, eventhough it's in no list. [Possibly related to #20?]

General Fluid dynamics

Sources are formed in blocks when broken or moved when the fluid is falling [e.g. let lava fall through leaves (not interactable with bucket), break leaves (suddenly can be picked up with a bucket); other example: Let fluid flow through piston head (not interactable with bucket), let piston retract (suddenly can be picked up with a bucket)]. So, general fluid duping.
Fluids don't always interact with blocks. E.g. water flows through lit campfires, but should always become extinguished, not just by sources. [Possible solution: Config list for interaction behavior with possible outcomes? E.g. "minecraft:#campfires"= "[lit=false]"]

Config

The block lines in the config file in general are disorganized, there seems to be no order?
Some blocks aren't in "fluid_permeable_blocks" that should be, like slabs and stairs, thus resulting in #17

General improvements

It would be great to have some rendering modification/honor collisions. I.e. to have fluids flow around certain blocks, e.g. hoppers & cauldrons. [so "#minecraft:cauldrons" can be included, as they have a little slit at the bottom where fluids should be able to flow through] Right now, it just flows through them, also rendering inside.
Related to that, partial fluid logging. E.g. have panes that are only filled with a fluid in one corner. So we can finally have proper aquariums.
Have more special block interactions.
E.g. while "minecraft:fern" isn't in any lists, it should not create air. But rather when placed be fluidlogged (and maybe still pop off, but it shouldn't create air).
Or being able to place a torch underwater without creating air, only for it to pop off and e.g. drop a stick instead.

Related to config:
Here is an example of the vanilla, alphabetically sorted list of block tags that I feel like belong:
{
  "fluid_permeability_enabled": true,
  "fluidloggable_blocks": {
    "blacklist": false,
    "blocks": [
	  "#minecraft:anvil",
	  "#minecraft:all_signs",
	  "#minecraft:banners",
	  "#minecraft:beds",
	  "#minecraft:buttons",
	  "#minecraft:campfires",
	  "#minecraft:candles",
	  "#minecraft:corals",
	  "#minecraft:doors",
	  "#minecraft:fence_gates",
	  "#minecraft:fences",
	  "#minecraft:leaves",
	  "#minecraft:pressure_plates",
	  "#minecraft:rails",
	  "#minecraft:slabs",
	  "#minecraft:stairs",
	  "#minecraft:trapdoors",
	  "#minecraft:walls",
	  "#minecraft:wool",
	  "#minecraft:wool_carpets"
    ]
  },
  "fluid_permeable_blocks": {
    "blacklist": false,
    "blocks": [
	  "#minecraft:anvil",
	  "#minecraft:all_signs",
	  "#minecraft:beds",
	  "#minecraft:buttons",
	  "#minecraft:doors",
	  "#minecraft:pressure_plates",
	  "#minecraft:slabs",
	  "#minecraft:stairs",
	  "#minecraft:trapdoors",
	  "#minecraft:walls"
    ]
  },
  "shape_independent_fluid_permeable_blocks": {
    "blacklist": false,
    "blocks": [
	  "#minecraft:banners",
	  "#minecraft:campfires",
	  "#minecraft:candles",
	  "#minecraft:corals",
	  "#minecraft:fence_gates",
	  "#minecraft:fences",
	  "#minecraft:leaves",
	  "#minecraft:rails",
	  "#minecraft:wool",
	  "#minecraft:wool_carpets"
    ]
  }
}


[Feature Request]: Add Support For Creating a Post for a Publication

Why Do We Need This Feature?
We have the hooks to fetch all about the posts from a publication. We need a way to create a post for a publication.
Are There Any Workarounds Available Today?
None through this NPM
Any Design Proposals(Here you can provide any raw screenshots)
Check this out: https://apidocs.hashnode.com/#mutation-publishPost
I adhere to the CODE OF CONDUCTS of this project

[X] I DO

@atapas I would like to work on this feature.
Thanks!

@atapas I would like to work on this feature.
Thanks!

Hey @itsaakashpatel assigned to you. Please let me know if you will get on it.

@atapas I would like to work on this feature.
Thanks!

Hey @itsaakashpatel assigned to you. Please let me know if you will get on it.

Hi @itsaakashpatel are you on it?

Hey @atapas Yes, I will start working on it soon.
Thanks!

@atapas I have attached the PR with the required changes. Please review it.
Thanks!

@atapas I have attached the PR with the required changes. Please review it.
Thanks!

Yes Sir! Will do


fixes attr name

import datetime

from fastapi import APIRouter
from fastapi.responses import RedirectResponse
from starlette.requests import Request
from starlette.responses import Response

from app.api.analytics.models import Statistic
from app.api.shortie.funcs import base62encode, make_short_url
from app.api.shortie.models import ShortenedURL
from app.api.shortie.schemas import (
    DeleteResponse,
    LongUrl,
    ShortenReponse,
    UpdateResponse,
)
from app.cache.conn import RedisClientManager
from app.core.config import settings

router = APIRouter()

@router.get("/{short_url_id}", response_class=RedirectResponse)
def read(short_url_id: str, request: Request, response: Response):
    with RedisClientManager() as cache:
        now = datetime.datetime.now()
        short_url_analytics = Statistic.find(Statistic.short_url_id == short_url_id).first()
        short_url_analytics.clicks += 1
        short_url_analytics.last_visited = now
        short_url_analytics.save()
        return ShortenedURL.find(ShortenedURL.short_url_id == short_url_id).first().long_url

@router.post("")
def create(req_body: LongUrl, request: Request, response: Response):
    with RedisClientManager() as cache:
        ttl = settings.CACHE_TTL
        counter = cache.incr(settings.COUNTER_CACHE_KEY)
        short_url_id, short_url, long_url = base62encode(counter - 1), make_short_url(base62encode(counter - 1)), req_body.long_url
        shortened_url, shortened_url_analytics = ShortenedURL(short_url_id=short_url_id, short_url=short_url, long_url=long_url), Statistic(short_url_id=short_url_id)

        shortened_url.save()
        shortened_url.expire(ttl)
        shortened_url_analytics.save()
        shortened_url_analytics.expire(ttl)

        return ShortenReponse(short_url_id=short_url_id, short_url=short_url, long_url=long_url, ttl=ttl)

@router.put("/{short_url_id}")
def update(short_url_id: str, req_body: LongUrl):
    shortened_url = ShortenedURL.find(ShortenedURL.short_url_id == short_url_id).first()
    if not shortened_url:
        return {"error": f"Short url id: [{short_url_id}] not found."}
    previous_long_url, new_long_url = shortened_url.long_url, req_body.long_url
    short_url = shortened_url.short_url
    shortened_url.long_url = new_long_url
    shortened_url.save()

    return UpdateResponse(short_url_id=short_url_id, short_url=short_url, previous_long_url=previous_long_url, new_long_url=new_long_url)

@router.delete("/{short_url_id}")
def delete(short_url_id: str):
    shortened_url = ShortenedURL.find(ShortenedURL.short_url_id == short_url_id).first()
    if not shortened_url:
        return {"error": f"Short url id: [{short_url_id}] not found."}
    short_url, long_url = shortened_url.short_url, shortened_url.long_url

    shortened_url.delete(shortened_url.pk)

    return DeleteResponse(short_url_id=short_url_id, short_url=short_url, long_url=long_url)

Analyzing underlying k8s object(s) changes at - 2023-05-08T17:43:31.205Z (UTC) .

<details><summary>__tests__/data/values-v2.yaml - underlying k8s object(s) changes.</summary>

```diff

--- gitops-k8s-diff-base/gitops-k8s-diff-templated-k8s-objects/__tests__/data/values-v2.yaml        2023-05-08 12:43:30
+++ gitops-k8s-diff-target/gitops-k8s-diff-templated-k8s-objects/__tests__/data/values-v2.yaml      2023-05-08 12:43:31
@@ -135,41 +135,41 @@
               port: 80
               scheme: HTTP
             initialDelaySeconds: 10 # number of seconds to wait after the pod comes up before it starts testing
             periodSeconds: 10 # interval in seconds between tests
             timeoutSeconds: 10 # number of seconds before a test will implicitly fail, if no success was returned in that time
             successThreshold: 1 # has to pass a test this number of times contiguously before it can transition to a success
             failureThreshold: 3 # has to fail a test this number of times contiguously before it can transition to a failure

           livenessProbe:

             httpGet:
               path: /actuator/health # endpoint for liveness check; must return a 200 while pod is live
               port: 80
               scheme: HTTP
             initialDelaySeconds: 10 # number of seconds to wait after the pod comes up before it starts testing
             periodSeconds: 10 # interval in seconds between tests
             timeoutSeconds: 10 # number of seconds before a test will implicitly fail, if no success was returned in that time
             successThreshold: 1 # has to pass a test this number of times contiguously before it can transition to a success
             failureThreshold: 3 # has to fail a test this number of times contiguously before it can transition to a failure
           volumeMounts:
-            - mountPath: frontendappconfig
+            - mountPath: /app/wwwroot/appConfig.js
               name: tcx-supportbi-ui-frontendappconfig
               readOnly: true
               subPath: appConfig.js
       volumes:
 ---
 # Source: ttc-standard-app/templates/hpa.yaml
 apiVersion: autoscaling/v1
 kind: HorizontalPodAutoscaler
 metadata:
   name: tcx-supportbi-ui
   namespace: dev
   labels:
     team: tcx-omega
 spec:
   maxReplicas: 3
   minReplicas: 2
   scaleTargetRef:
     apiVersion: apps/v1
     kind: Deployment
     name: tcx-supportbi-ui

```
</details>
[[gitops-k8s-diff]]

__tests__/data/values-v2.yaml - underlying k8s object(s) changes.

--- gitops-k8s-diff-base/gitops-k8s-diff-templated-k8s-objects/__tests__/data/values-v2.yaml        2023-05-08 12:43:30
+++ gitops-k8s-diff-target/gitops-k8s-diff-templated-k8s-objects/__tests__/data/values-v2.yaml      2023-05-08 12:43:31
@@ -135,41 +135,41 @@
               port: 80
               scheme: HTTP
             initialDelaySeconds: 10 # number of seconds to wait after the pod comes up before it starts testing
             periodSeconds: 10 # interval in seconds between tests
             timeoutSeconds: 10 # number of seconds before a test will implicitly fail, if no success was returned in that time
             successThreshold: 1 # has to pass a test this number of times contiguously before it can transition to a success
             failureThreshold: 3 # has to fail a test this number of times contiguously before it can transition to a failure

           livenessProbe:

             httpGet:
               path: /actuator/health # endpoint for liveness check; must return a 200 while pod is live
               port: 80
               scheme: HTTP
             initialDelaySeconds: 10 # number of seconds to wait after the pod comes up before it starts testing
             periodSeconds: 10 # interval in seconds between tests
             timeoutSeconds: 10 # number of seconds before a test will implicitly fail, if no success was returned in that time
             successThreshold: 1 # has to pass a test this number of times contiguously before it can transition to a success
             failureThreshold: 3 # has to fail a test this number of times contiguously before it can transition to a failure
           volumeMounts:
-            - mountPath: frontendappconfig
+            - mountPath: /app/wwwroot/appConfig.js
               name: tcx-supportbi-ui-frontendappconfig
               readOnly: true
               subPath: appConfig.js
       volumes:
 ---
 # Source: ttc-standard-app/templates/hpa.yaml
 apiVersion: autoscaling/v1
 kind: HorizontalPodAutoscaler
 metadata:
   name: tcx-supportbi-ui
   namespace: dev
   labels:
     team: tcx-omega
 spec:
   maxReplicas: 3
   minReplicas: 2
   scaleTargetRef:
     apiVersion: apps/v1
     kind: Deployment
     name: tcx-supportbi-ui

Analyzing underlying k8s object(s) changes at - 2023-05-08T18:04:01.359Z (UTC) .\n\ntests/data/values-v2.yaml - underlying k8s object(s) changes.\n\ndiff \n\n--- gitops-k8s-diff-base/gitops-k8s-diff-templated-k8s-objects/__tests__/data/values-v2.yaml\t2023-05-08 13:04:00\n+++ gitops-k8s-diff-target/gitops-k8s-diff-templated-k8s-objects/__tests__/data/values-v2.yaml\t2023-05-08 13:04:01\n@@ -146,21 +146,21 @@\n               path: /actuator/health # endpoint for liveness check; must return a 200 while pod is live\n               port: 80\n               scheme: HTTP\n             initialDelaySeconds: 10 # number of seconds to wait after the pod comes up before it starts testing\n             periodSeconds: 10 # interval in seconds between tests\n             timeoutSeconds: 10 # number of seconds before a test will implicitly fail, if no success was returned in that time\n             successThreshold: 1 # has to pass a test this number of times contiguously before it can transition to a success\n             failureThreshold: 3 # has to fail a test this number of times contiguously before it can transition to a failure\n           volumeMounts:\n             - mountPath: /app/wwwroot/appConfig.js\n-              name: frontendappconfig\n+              name: tcx-supportbi-ui-frontendappconfig\n               readOnly: true\n               subPath: appConfig.js\n       volumes:\n ---\n # Source: ttc-standard-app/templates/hpa.yaml\n apiVersion: autoscaling/v1\n kind: HorizontalPodAutoscaler\n metadata:\n   name: tcx-supportbi-ui\n   namespace: dev\n\n\n\n

- hello
+ bye


Adding some images related to this website

Hey, I visited your website and I found that if  we will add some photos reated to books ansd all then it will look more creative and decent. So I can do that please assign this issue to me.
Thank you

Fatima I am getting your point but the changes you are suggesting is quite subjective, you may like those photos but maybe the PA won't like it, these changes are minor and very subjective. I believe lets let the PA decide the photos. Feel free raise other issues. Thanking you for creating this one.


Add note about MDX configuration

What kind of changes does this PR include?

New or updated content

Description
Added a :::note to the main markdown page linking to the MDX config section.

Thanks for this helpful note and link, @mayank99! 🥳 As we discussed, this page is probably going to have more edits to it, but this contribution will absolutely end up, in one form or another, on any version going forward. Great catch!


Link to child workflows from parent workflow histories

Attempt to partially solve #845.

What was changed
The PR wraps child workflow IDs and Run IDs displayed in workflow histories with links to the corresponding workflow pages.
Why?
This is very useful when debugging workflows in the UI as you don't have to go back to the workflow list view and filter by workflow ID.
Ideally, we could jump to a child workflow in one click as highlighted in #845 instead of having to click on the Workflow pill, but his might need more design decision on how to render that out, so I haven't tried to implement it.
Checklist

This only partially implements #845

How was this tested:

Only locally, running the UI with a demo workflow

Any docs updates needed?

No

My frontend, typescript and svelte knowledge is very limited and I am not really satisfied with how I had to pass down the entire event attributes to the EventDetailsRowExpanded component to be able to get both the workflow and run IDs. I am not sure there is a better way given the current implementation which is a simple for loop to "display that attributes list" without full context around the attributes.

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


other sequences from the MulRan dataset

Hello, if I want to use other sequences from the MulRan dataset in your program, how should I modify it?

For other sequences like DDC, KAIST from the MulRan dataset, the processing procedure (referring to datasets/MulRanDataset.py) is the same as Sejong used in our codes.


Fix REPL

Update the usePrevious change for v2 on the REPL

Could you provide the steps to recreate the issue you are facing? svelte-previous is working on the REPL for me.
https://svelte.dev/repl/3d347bff1e5c4353869ae781f29b2fc4?version=3.38.2

Oh yeah, it works, just that the link in the readme is outdated.

Ah gotcha 👍  Fixed!


Add painless panes

This is something I missed from vim, but it may be controverisial.
It automatically resizes the active pane to a reasonable size and disables standard pane resizing.
You can hit ctrl-alt-p to turn it off entirely.
Thoughts on this? Should it be on by default?

I think it's cool, but should not be on by default. I think many people (especially the less technical folks) would be immediately confused about what's going on.

fwiw, I did a couple hallway tests w/ @ryanmclaughlin and @liz-substantial, both preferred it. I'm tempted to merge as is and if enough people complain, shift it back....

👍
On Wed, Aug 12, 2015 at 5:06 PM Aaron Jensen<EMAIL_ADDRESS>wrote:

fwiw, I did a couple hallway tests w/ @ryanmclaughlin
https://github.com/ryanmclaughlin and @liz-substantial
https://github.com/liz-substantial, both preferred it. I'm tempted to
merge as is and if enough people complain, shift it back....
—
Reply to this email directly or view it on GitHub
https://github.com/substantial/atomfiles/pull/65#issuecomment-130487000.

Another thing I thought about was supporting pane resizing... basically, as soon as you resized a pane, it'd disable painless-panes and show a message w/ the key to re-enable it. It'd be tricky to do though, right now disabling it will size the panes back to default...


Remove UNSAFE_componentWillMount and fix initialValues not passed to validation

Remove UNSAFE_componentWillMount and fix initialValues not passed to validation.
Issues: https://github.com/redux-form/redux-form/issues/4628, https://github.com/redux-form/redux-form/issues/4642
Partially ported from https://github.com/shanshanzhu/redux-form/commit/d59ea8e0ff374f45c20f463b36f7101985b3eba2
Updated React development version to 17.0.2

@erikras hi, as we discussed, please check this.
Still 4 UNSAFE lifecycle methods are left, i'm not sure how to rewrite it, tests are failing.

Maybe outside the scope of this fix, but to be (perhaps a bit too) blunt, the problem here is https://github.com/redux-form/redux-form/pull/4020 It might have fixed a bug with the wrong values being passed in under one particular set of conditions - but completely broke the behaviour of initial setup, where previously the values prop was set up to be the intialValues when first set up, and now it's set up to be an empty object because the initialization logic was inverted without account for the reason it was written that was in the first place.
So, validation not getting initialValues is just the symptom that everyone has started to notice about that change, but anything that relies on values could be broken. I won't pretend to know enough of the redux-form code to know if your fix is general enough to account for that, but as I spent days trying to understand why upgrading redux-form broke the application I'm working with, I figured I'd make note of the more general possible problem since you're working on it.

@shanshanzhu please check this too, because it based in your changes

@sanex3339 LGTM

Is there any ETA of when will this be released?

@erikras @iamandrewluca is the a chance this PR or https://github.com/redux-form/redux-form/pull/4728 will be merged?

This would also fix parts of #4373 and #3954

@erikras May you review this PR to enable React 17 support to prevent it falling behind too far especially React 18 has been out for a few months? 🙏

@erikras UP 🙏

👍

@erikras May I ask when this will be released? I am eagerly awaiting this fix.

Published in v8.3.10.


Use node scheduler to update database

We can use node scheduler to schedule update of classes/course info/popular courses
https://www.npmjs.com/package/node-schedule

Done


Feature Request: Make namespace input optional

Feature request
kubectl does not require a namespace if a namespace is set in the resource manifests. This action should also not require a namespace. This would allow deployments in multiple namespaces at once.

This would be great for charts with several components for different namespace. Definitely would be a great feature to have


How to collapse side menu on start?

I already try
Method#1: Set body class "nav-md" > "nav-sm"
Method#2: $('#menu_toggle').click(); on document ready
Menu is collapsed but side menu did work correct. It's still slide down.
Please advise.

Method 1 (changing the nav-md from nav-sm) will work, did you do it on the latest one?

@christianesperar I already try. It's ok, the menu collapsed but when I click on menu icon, child menu still slide down (normal, they should show on right side).
Thank

Did you use the latest gentelella?

@christianesperar I'm not sure but I downloaded from here for 5 week ago.

The demo is updated now. Can you try again?

@christianesperar Thank :)
PS. Do you have advise if I want only update it? Just use new css & js?

Just js but it's better if you update both files to benefit on new updates.

Method 1 is a fail on the latest, as using nav-sm starts it collapsed but it displays the sub-menu all the time.
Method 2 worked just fine for me, I did change put click trigger before every other form, table, etc initializations as then the page length was initialized as wider.
Thanks

@bthppong
Please, can you show the hole code you've done.... I've got the same problem and I dont know how to solve...

$(function() {
$('body').removeClass('nav-md').addClass('nav-sm');
$('.left_col').removeClass('scroll-view').removeAttr('style');
$('#sidebar-menu li').removeClass('active');
$('#sidebar-menu li ul').slideUp();
});
i use this code and it works, can yout try?

Fantastic, it's working... really good... thanks.

@kunbero works but not the radical solution and has some problems like it's considered extra processing, and if you have a dom structure that is constructed based on the width of the page it would be a problem

I am trying to achieve the same result (collapse the sidemenu on start). I tried the nav-sm and it works except if you open the page on a mobile device, then the collapsed nav bar still shows, where as I would like it to be hidden on narrow view ports. Anyone solved this?

If someone's still trying to achieve this, here is the way to go:
function menuToggle(){
  if ($('body').hasClass('nav-md')) {
    $("#sidebar-menu").find('li.active ul').hide();
    $("#sidebar-menu").find('li.active').addClass('active-sm').removeClass('active');
  } else {
    $("#sidebar-menu").find('li.active-sm ul').show();
    $("#sidebar-menu").find('li.active-sm').addClass('active').removeClass('active-sm');
  }
  $('body').toggleClass('nav-md nav-sm');
  setHeight();
}

function setHeight(){
  $('.right_col').css('min-height', $(window).height());
  var bodyHeight = $('body').outerHeight();
  var footerHeight = $('body').hasClass('footer_fixed') ? -10 : $('footer').height();
  var leftColHeight = $('.left_col').eq(1).height() + $('.sidebar-footer').height();
  var contentHeight = bodyHeight < leftColHeight ? leftColHeight : bodyHeight;
  contentHeight -= $('.nav_menu').height() + footerHeight;
  $('.right_col').css('min-height', contentHeight);
}

Add the two functions and call the menuToggle(); function on $(document).ready();

I do not get how to apply your sample provided. Could you explain how to handle the last info?

Add the two functions and call the menuToggle(); function on $(document).ready();

@tomtheone copy the functions in snippet i've provided. once that's done.
just add the following code:
$(document).ready(function(){
menuToggle();
});
This will call the function that you've already copied which toggles the menu on document ready event. (jQuery)

Hi,
I have a ul with li menu items has children. I would like open specific UL when page load! Anyone can help me ?
thanks

can we store a session that if the menu collapses, it will remain collapse on the other menu selection?

Hola despues de tanto buscar en muchos foros, funciono para mi, cuando ejecute
// Comenzar con Barra de Menu Small   $("#menu_toggle").click(); al Final del $(document).ready(function(){ ... }) mi explicación es que se debe cargar todo el DOM y despues ejecutar el click... así, los submenus también no se desplegaran...

$(document).ready(function() {
$('#menu_toggle').click();
});


Fix #151: add support for magicless frames

Thanks for the contribution!

Thanks for merging it! Any idea when the next release will be?

I can release it soon - I don't thing the zstd will release new version the following few weeks.


3D dataset read in / middle formatted data and label files provided

thanks for sharing your implementation, I was wondering if you could share the files below, or just a snippet that shows its format would also work:
data_path = "./data/NTU-RGB-D/xview/val_data.npy"
label_path = "./data/NTU-RGB-D/xview/val_label.pkl"
I am working with my own custom dataset, I used the format for the 2D with kinetics skeleton dataset, so I got the json format similar to openpose. Now, I want to use the 3D version with my custom dataset, and it seems the NTU-RGB-D dataset is huge and its format is very complicated, I see that using the tools you create a middle format and then read it in (the files above), I want to bypass all this format reading in and conversion and I want to figure out how I can read in the 3D dataset in a similar way to kinetics dataset, meaning only X,Y,Z coordinates of 5 joints (2 actors per frame) and the probability of the joint node coordinates. Can you share these files so that I can use this middle format instead of all the conversions required with the NTU dataset.

Did you succeed？


[shardformer] chatglm support flash attention and jit operator

📌 Checklist before creating the PR

[x] I have created an issue for this PR for traceability
[x] The title follows the standard format: [doc/gemini/tensor/...]: A concise description
[x] I have added relevant tags if possible for us to better distinguish different PRs

🚨 Issue number

Link this PR to your issue with words like fixed to automatically close the linked issue upon merge
e.g. fixed #1234, closed #1234, resolved #1234

#4184
📝 What does this PR do?

Summarize your work here.
if you have any plots/diagrams/screenshots/tables, please attach them here.

chatglm support flash attention and jit operator
💥 Checklist before requesting a review

[x] I have linked my PR to an issue (instruction)
[x] My issue clearly describes the problem/feature/proposal, with diagrams/charts/table/code if possible
[x] I have performed a self-review of my code
[x] I have added thorough tests.
[x] I have added docstrings for all the functions/methods I implemented

⭐ Do you enjoy contributing to Colossal-AI?

[ ] 🌝 Yes, I do.
[ ] 🌚 No, I don't.

Tell us more if you don't enjoy contributing to Colossal-AI.

All tests have passed.


Changed the volume settings if whole sound is decreased no sound will…

… come
This PR implements an improvement to the game's sound management by adding a conditional check for the volume slider before playing the hit sound. The main changes include:
Volume Control for Hit Sound: The hit sound will only play if the volume slider value is greater than 0. This ensures that players who mute the sound do not hear unintended audio effects when hitting aliens.
Fixes #168

Type of change
before:
https://github.com/user-attachments/assets/c22cc56f-d1c7-4632-9a84-6b2c4efe8114
After:
https://github.com/user-attachments/assets/6a788784-40da-40e0-bd19-b148aa0ac7a5

New feature (non-breaking change which adds functionality)

How should this be tested?
Here’s a template for the testing section of your Pull Request (PR) description:
How should this be tested?
To verify the changes made in this PR, follow the steps below:
Testing Instructions
Run the Game:
Launch the game in your preferred environment (browser, IDE, etc.).
Adjust the Volume Slider:
Locate the volume slider in the game settings or interface.
Set the slider to different positions:
Set to 0: Ensure that when the volume slider is at the minimum (0), the hit sound does not play when an alien is hit.
Set to Greater than 0: Move the volume slider to a value greater than 0 and confirm that the hit sound plays correctly when an alien is hit.
Hit Aliens:
Engage with the game and hit some aliens.
Verify that the sound behaves as expected based on the volume settings.

[ x] Test A
[ x] Test B

Mandatory Tasks

[x ] Make sure you have self-reviewed the code. A decent size PR without self-review might be rejected.

Could you please assign Level 3 for my hard work, as I've made a lot of changes to the project? Thank you!

Can u add the labels pls

Can add the labels pls


fix: internal email pattern regex

Custom patterns do not seem to support \Z (uppercase) but \z (lowercase) seems to work.

Thanks for the spot and the PR!
I just checked on GitHub Cloud, I get that message too, so I'll go ahead and merge, since this doesn't seem to affect the behaviour of the rule.
P.S. It's puzzling to me why this is happening.
It is listed in the Hyperscan docs as a supported construct:

The anchors ^, $, \A, \Z and \z.

I believe it used to work.

@aegilops updated the yml file as well


chore: Update all dependencies.

This also fixes the Node.js 10 setup.

Some tsc fails, what could be the cause? Fix typings or upgrade tsc?

I just did this for opticss last night. Thanks for trying to tackle it.
I noticed that @types/webpack is 4.x and webpack is 3.8 so that's probably going to cause some issues.
I'll try running the build after I'm done whacking on opticss and see what the issues are.

Probably some tslint misconfiguration. Not yet sure. Ok =)