Add types Props<T>, Events<T> and Slots<T> which provide types for components

What problem does this feature solve?
In order to enhance Typescript support, I would like to easily be able to extract the props, event and slots which a component supports. This feature would be very useful for creating better developer tools.
What does the proposed API look like?
Consider the following component:

<template>

    <slot name="heading" />

    <slot />

</template>

The proposed API would allow developers to do the following:
import MyComponent from './MyComponent.vue'

type P = Props<typeof MyComponent>   // { name: string, disabled: boolean? }
type E = Events<typeof MyComponent>  // { (event: 'change', value: string): void }
type S = Slots<typeof MyComponent>   // 'default' | 'heading'

Currently, I am using the following definitions for Props<T>, Events<T> and Slots<T> but I think they are fragile and could be made better.
import { ComponentOptions, ComponentOptionsMixin, ComputedOptions, InjectionKey, MethodOptions } from 'vue'

/** evaluates to `true` if `X` and `Y` are the same type, otherwise evaluates to `false` */
type Equals<X, Y> = (<T>() => T extends X ? 0 : 1) extends <T>() => T extends Y ? 0 : 1 ? true : false

/** extracts keys from `T` which are `readonly` */
type ReadonlyKeys<T> = {
  [Ro in {
    [K in keyof T]: Equals<Pick<T, K>, Readonly<Pick<T, K>>> extends true ? K : never
  }[keyof T]]: T[Ro]
}

export type Renderable = ComponentOptions<any> & (abstract new (...args: any) => any)

export type Props<T extends Renderable> = Pick<InstanceType<T>['$props'], _PropKeys<T>>
type _PropKeys<T extends Renderable> = keyof (T extends ComponentOptions<infer P> ? ReadonlyKeys
 : never)

export type Events<T extends Renderable> = T extends ComponentOptions<
  never,
  unknown,
  unknown,
  ComputedOptions,
  MethodOptions,
  ComponentOptionsMixin,
  ComponentOptionsMixin,
  infer E
>
  ? keyof E
  : never

export type Slots<T extends Renderable> = _Slots<InstanceType<T>['$slots']>
type _Slots<S> = keyof {
  [K in keyof S as S[K] extends CallableFunction ? K : never]: S[K]
}

This is awesome. Would be cool to have it as a native helper type.

Try vue-component-type-helpers

There's a PR to introduce these type helpers, if you have more type helpers you think might be useful, please let me know


Add  blockchair.com and 3xpl.com to the block explorer

Hello team,
I would like to suggest https://3xpl.com and https://blockchair.com be added to the block explorer list.
Blockchair.com is a Universal blockchain explorer and search engine, and 3xpl.com is an ad-free, fast universal explorer.
I hope this is something the team is interested in.

来信均悉。

您好，我已经成功收到了邮件!尽快给您回复。


Use cobra's RunE wherever possible

Notably, this makes ko exit 1 when kubectl isn't installed, instead of logging and otherwise doing nothing.
Less notably, this makes the error from ko run slightly less verbose.
Otherwise no functional changes are expected.

Codecov Report

Merging #343 (751f32d) into main (75ab991) will increase coverage by 0.12%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #343      +/-   ##
==========================================
+ Coverage   38.24%   38.37%   +0.12%
==========================================
  Files          33       33
  Lines        1527     1522       -5
==========================================
  Hits          584      584
+ Misses        849      844       -5
  Partials       94       94

Impacted Files
Coverage Δ

pkg/commands/apply.go
0.00% <0.00%> (ø)

pkg/commands/create.go
0.00% <0.00%> (ø)

pkg/commands/delete.go
0.00% <0.00%> (ø)

pkg/commands/publish.go
0.00% <0.00%> (ø)

pkg/commands/resolve.go
0.00% <0.00%> (ø)

pkg/commands/run.go
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


how to use intrinsics and extrinsics from colmap ?

Hi ,
I have a custom image dataset, and run colmap to get the instrinsics and extrinsics of all the images. Then , how should I proceed to run monosdf and get the mesh?
Thanks!
Jiakui

Hi, I think you could adapt this script https://github.com/autonomousvision/monosdf/blob/main/preprocess/scannet_to_monosdf.py to prepare the data

Hi, author.
I run colmap and the following code to generate 'cameras.npz'.
    intrin_mat = np.array([
        [fx,  0, cx],
        [ 0, fy, cy],
        [ 0,  0,  1]
    ])
    intrin_mat[0, 2] -= (w - min(w, h)) / 2.
    intrin_mat[1, 2] -= (h - min(w, h)) / 2.
    intrin_mat[:2, :] *= 384. / min(w, h)

    K = np.eye(4, dtype=np.float32)
    K[:3, :3] = intrin_mat

    valid_poses = np.isfinite(poses).all(axis=2).all(axis=1)
    min_vertices = poses[:, :3, 3][valid_poses].min(axis=0)
    max_vertices = poses[:, :3, 3][valid_poses].max(axis=0)
    scale_mat = np.eye(4, dtype=np.float32)
    scale_mat[:3, 3] = - (min_vertices + max_vertices) / 2.
    scale_mat[:3] *= 2. / (np.max(max_vertices - min_vertices) + 3.)
    scale_mat = np.linalg.inv(scale_mat)

    cams = {}
    idx = 0
    for _, (pose, valid) in enumerate(zip(poses, valid_poses)):
        if not valid: continue
        pose = K @ np.linalg.inv(pose)
        cams[f"scale_mat_{idx:d}"] = scale_mat
        cams[f"world_mat_{idx:d}"] = pose
        idx += 1
    np.savez(osp.join(path, "cameras.npz"), **cams)

It seems that the losses are converging, but the mesh is just strange.

The normal train reslut is as follows.

I notice the code in 'scene_dataset.py' and comment it, the result keeping bad.
elif center_crop_type == 'center_crop_for_dtu':
     scale = 384 / 1200
     offset = (1600 - 1200) * 0.5
     intrinsics[0, 2] -= offset
     intrinsics[:2, :] *= scale

I guess the issue lies in the transform process to camera poses.
Do u have any idea?

@CCOSerika Sorry for the late reply.
This line
scale_mat[:3] *= 2. / (np.max(max_vertices - min_vertices) + 3.)

is used for ScanNet (indoor scenes) where the cameras are inside the rooms. In the DTU cases it should be changed to something like
scale_mat[:3] *= 3. / (np.max(max_vertices - min_vertices))

Sorry，I want to ask if pose conversion is only used to generate mesh in the evaluation phase？

@MingRuiye Sorry I missed your messages. Not sure whether I understand your question. The pose conversion is used in evaluation phase because we need to convert the extracted mesh back to original world space.


Redesign proxy architecture

The proxy architecture is very simply, but may not be the best design. The way it works now is if a request needs to be proxied (either is one of the requests that is always proxied, like submit, or specifies ledger_index:current), clio picks an etl source at random and forwards the request there. This works, but there are a number of improvements that could be made.

Consider disabling proxy for certain requests. For instance, ledger_data probably should never be proxied. The call is iterative, and iterating the whole ledger takes minutes, during which time the open ledger changes many times over. The list of RPCs that actually need access to the open ledger is quite small, so we could probably disable proxying on quite a bit.
Think about how to provide a consistent view to the open ledger. clio uses a collection of etl sources, and each of those has a different view of the open ledger. Transaction propagation results in a sort of eventual consistency, though there is no guarantee on consistency prior to consensus, at which point the data is validated and clio writes it to the database. When we pick a random p2p node to proxy a request to, subsequent requests are likely to go to a different p2p node. So if a user calls server_info and uses the load_factor to calculate fees, and then calls submit to submit the transaction, submit will probably go to a different p2p node than server_info did, which could cause incorrect fee calculation. A similar situation can occur with account_info.
Have clio be smarter about which node to proxy to. clio could track the load factor of each p2p node, and forward requests to the node with the lowest load factor, or some other measure of idleness. At a certain point, clio should reject proxy requests if the p2p nodes are in danger of going out of sync.
Consider caching data in clio. We proxy server_info to get the load factor, but we could probably just query each p2p node once per second to get their load factor, and then cache that in clio. We might be able to do something like this for account_info as well.
Enable separating ETL sources and proxy endpoints. Proxy endpoints could get bombarded with traffic and go out of sync, and then can no longer be ETL sources, and the database will stop getting updates.
Make the proxy asynchronous, so we are not sitting on a thread until the response comes back.

Lastly, what we really need is some way to handle a lot of requests that require a p2p node without causing the nodes to desync. Reporting nodes simply slow down when there are too many requests, forcing requests to wait in a queue and eventually returning an error rpcTOO_BUSY. p2p nodes on the other hand lose sync, at which point they can't handle any requests until they resync, which can take several seconds or longer.

A couple preliminary thoughts

We should consider disabling ledger_index: 'validated' | 'current' | 'closed' for any RPC that requires pagination. It doesn't make a lot of sense to allow this behavior (w/ the exception of book offers) because the validated/closed/open ledger can change at any time, and give clients invalid responses

2/3/4) These seem to fall into the category of smarter load balancing.

I don't have any opinions here. Seems like a reasonable suggestion. For account_info, we should try to make load balancing smarter such that the same clients (when requesting the open ledger + submitting) will attempt to hit the same p2p node for a consistent view of the open ledger.

👍

👍


Fix severity table column spillover

Reference: https://github.com/nexB/vulnerablecode/issues/982

@TG1999 Here's a screenshot of the updated table using mock data:

@johnmhoran this looks good! please add a changelog entry for same.


Allow to use EmbeddedChannel.schedule*(...)

Motivation:
At the moment when EmbeddedChannel is used and a ChannelHandler tries to schedule and task it will throw an UnsupportedOperationException. This makes it impossible to test these handlers or even reuse them with EmbeddedChannel.
Modifications:

Factor out reusable scheduling code into AbstractSchedulingEventExecutor
Let EmbeddedEventLoop and SingleThreadEventExecutor extend AbstractSchedulingEventExecutor
add EmbbededChannel.runScheduledPendingTasks() which allows to run all scheduled tasks that are ready

Result:
Embeddedchannel is now usable even with ChannelHandler that try to schedule tasks.

@trustin @Scottmitch please review

Please address the comments above. The CI server reported a test failure, too.  Could you take a look?

@normanmaurer - LGTM after comments resolved (and unit tests passing).

@netkins build

@trustin please review again... test is passing now.

@normanmaurer - Done with another round.  Just a few comments...mostly code clarity.

@trustin please check

I see naming inconsistencies - delayed* and scheduled*. Could you use scheduled wherever posible? (local variables, member variables, method names, whatever)

Looks good except for the cosmetic issues like I mentioned above. Please ping me for another quick round after addressing the comments.

@trustin addressed... please check again

Please try to be more rigorous next time. Simple text search for delayed should do it. :-)

@trustin my fault... I was only looking for delayedTaskQueue :/ Sorry

@trustin done... one last time please . And drinks on me next time we meet ;)

Please cherry-pick :-)

Cherry-picked into 4.0 (6950bfb5d8c043eaf95c1e00841119a01199c13d) , 4.1 (a70955381993e0a45a97ec732bd784a94bf458d1) and master (590c649e7d756b8284c47ec37dd71d849e06d385)

@Scottmitch I just removed the confusing checks as after thinking more about it it makes no sense.

@normanmaurer +1. Thanks for taking care of this. good stuff!


Project templates missing

I'm on Ubuntu, in vs code, I have Ionide sharp and paket installed, but when I try to create a new f# project I get the error, wrong template,
If I go to the template folder, it is indeed empty, so I tried refresh templates, which gives the following log:
forge refresh --no-prompt
Getting templates...
Deleting contents of /home/master/.vscode/extensions/Ionide.Ionide-fsharp-2.4.3/bin_forge/../templates
git clone -b templates --single-branch https://github.com/fsprojects/forge.git templates
But the folder is still empty, if I go download the templates manually and unpack the file in the templates folder, and then go create new project it suddenly works, but if I refresh templates or restart vscode, the vanish again. I'm not sure what the problem is though.

Maybe a silly Q, but do you have git on your path?

Derp, that was the problem, sorry about that :D
Once I added git to PATH everything's just dandy at least I can suggest adding an error message if that's the case in the future ;P


Issue#452

The CMakeLists.txt was modified because Ubuntu 22.04 version had gcc version 11 which did not have the  header and did not compile on my machine so i changed the conditional to allow for it to use the fmt::format library
The modification lead to updating the FormatHelper.h header to reflect the changes. in addition The fmt library was also added as dependency to the test target to enable the test compile on my machine
Estonia locaction data was added which includes EstoniaAddresses EstoniaCounties EstoniaStreetNames EstoniaStreetSuffixes

test was appended to the end of LocationTest using the test for denmark as a template
estonia was included in AddressCountry enum
finally, The estonia data was gotten from resource available on the internet and google maps so their is no guarantee that all the information are correct as i do not live in estonia. "
[issue#452 1be61dd] introduction of estonian location data The CMakeLists.txt was modified because Ubuntu 22.04 version had gcc version 11 which did not have the  header and did not compile on my machine so i changed the conditional to allow for it to use the fmt::format library The modification lead to updating the FormatHelper.h header to reflect the changes. in addition The fmt library was also added as dependency to the test target to enable the test compile on my machine Estonia locaction data was added which includes EstoniaAddresses EstoniaCounties EstoniaStreetNames EstoniaStreetSuffixes test was appended to the end of LocationTest using the test for denmark as a template estonia was included in AddressCountry enum finally, The estonia data was gotten from resource available on the internet and google maps so their is no guarantee that all the information are correct as i do not live in estonia.

Kind regards

Hello, good job! Please give a star to the repository to make the project more popular :fire:

Please fix failing pipelines

I think clang and msvc should stay the same

I think clang and msvc should stay the same

okay i reverted back to the previos commit

Try to add more specified checks in format helper like defined(GNUC) && less than 12

Looks like in clang and msvc this if resolves to true and it tries to use fmt

Btw cant you install g++ 13? 😁

Try to add more specified checks in format helper like defined(GNUC) && less than 12
ah ok i see the bug  now.

((defined(GNUC) && (GNUC < 12)  && !defined(clang)) should work :smile:

looks like  clang also defines gnuc

Btw cant you install g++ 13? 😁

reason is i would need to use a third party ppa but  i am trying to avoid any possible breaks on my OS. in addition , too lazy to manually compile the compiler . i do not understand the error message coming from  msvc workflow i have not modified any of those document in this current branch. it could be an old issue

I know about msvc issue, if clang build will pass I will merge it :)

Issue is mentioned here: https://github.com/cieslarmichal/faker-cxx/issues/469


fix: The font for unread messages is not bolded in Android

Details

Fixed Issues
$ https://github.com/Expensify/App/issues/25967
PROPOSAL: https://github.com/Expensify/App/issues/25967#issuecomment-1693784907
Tests

Open reports sidebar
Mark any report as unread if not
Observe the unread report display name is bolded

[x] Verify that no errors appear in the JS console

Offline tests

Open reports sidebar
Mark any report as unread if not
Observe the unread report display name is bolded

QA Steps

Open reports sidebar
Mark any report as unread if not
Observe the unread report display name is bolded

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

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

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://github.com/Expensify/App/assets/85894871/cfc0e936-8dfe-4485-994b-cb0a96f24be7

Mobile Web - Chrome
https://github.com/Expensify/App/assets/85894871/ce97338f-0ec8-410a-98a5-109be4fffb0b

Mobile Web - Safari
https://github.com/Expensify/App/assets/85894871/f0ec0bec-99e4-4eb1-9929-336268ca9b5f

Desktop
https://github.com/Expensify/App/assets/85894871/16c91538-39e5-4d8d-b3b1-65c4f863391c

iOS
https://github.com/Expensify/App/assets/85894871/d038710c-72aa-44d8-bea9-9854fbd98b20

Android
https://github.com/Expensify/App/assets/85894871/fa722a0b-ffbb-447b-a3d6-9f66180502d6

🚀 Deployed to staging by https://github.com/grgia in version: 1.3.77-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.77-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


Readme Script

May close #94
I have made a script that will create a string that will form a table into the README file.
Since we are still debating about either auto Updating the README file or just console.log() the result, I made the script able to take a flag. If when running the script with the flag --autoUpdateReadme, it will auto update the readme, ex:
ts-node ./src/scripts/readmeScript.ts --autoUpdateReadme

The Command Line execution above will make the scrip auto update the README. But if the flag is not given, it will just console.log() the data table, ex:
ts-node ./src/scripts/readmeScript.ts

The Command Line execution above will make the script only console.log() the table results

due to the merge with #104, manually fix the merge conflicts in the package.json, and one easy way to handle the merge conflicts in the package-lock.json is to delete it, and rerun npm install. There aren't that many conflicts so it could also be done manually.

Resolved Merge Conflicts! :)

Don't close this yet, might change the chalk dependency into something else...

@JoshuaPelealu chalk is pretty well respected, (it even comes with TS support!) so I'm fine with adding it as a dev-dep :)

Well, in that case, we can keep chalk as dev dep when we need it.


Feedback

when i select the text then it turns to black

Hi @lalaghoury, thanks for your feedback !
It seems that the issue is with the select highlighting with dark mode.
Could you provide more informations about the web browser that you're using, so we can reproduce the issue so we can fix it?
Thanks again.


anonymous class and internal class

As far as I know, there is no lack of anonymous class and internal class function in swift，I look forward to such a function

I am closing this because the description of this feature is pretty vague and there no examples or motivation. Feel free to reopen if you feel like elaborating on these.


ice-tcp-passive

Description
Adding ice-tcp-passive candidate type
works in two modes: fixed & random port (based by AgentConfig.TCPPort)
Warning
Due to the structural limitations of the ice.Agent, it is not possible to use this option in answerer mode

Can you elaborate on why this could only work as answerer? It's no immediately clear to me.
@backkem
isControlling property of ice.Agent, not of a ICE candidate, and ice.Agent's candidates cant be Controlling & Controlled same time. But tcp-passive is must be ICE-CONTROLLED


Feature/signin with phonenumber

adds a method to sign in with phone number
adds a method to verifyOtp

LGTM


Encounter duration too short

a lot of encounters (not all) are being logged with <1m duration when it should be way more

This should now be fixed but let me know if still seeing it.


docs: Readme.md 수정

:tada: This PR is included in version 1.0.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Pantheon Desktop Environment: Gala crashes when logging in when using a device with a touchscreen

Describe the bug
I believe that the version of Mutter that Gala relies on does not include a patch that changes how the touchscreen display information is retrieved, resulting in an error like this: GLib-GIO-ERROR **: 23:00:24.681: Settings schema 'org.gnome.desktop.peripherals.touchscreen' does not contain a key named 'display'
I've experienced this myself on my Thinkpad T490 that has a touchscreen and found people from the Gentoo and RedHat/Fedora communities experiencing similar issues here and here.
To Reproduce
Steps to reproduce the behavior:

Own a laptop with a touchscreen (in my case, a T490)
Set it up with NixOS and the Pantheon Desktop Environment
Log into a desktop session with either a regular user or root.

Expected behavior
Gala not to crash
Screenshots
N/A
Additional context
I'm not sure what context to add since this is my first installation of NixOS on actual hardware.
Notify maintainers
@worldofpeace
Metadata
 - system: `"x86_64-linux"`
 - host os: `Linux 5.4.68, NixOS, 20.03.3087.b4db68ff563 (Markhor)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.6`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Maintainer information:
Affected packages (that I know of)
- pantheon
- gala
- mutter

I realize this is hardware specific and you might not have access to anything with a touchscreen to verify any fixes are working, so I'm happy to do what I can to help out here. Feel free to contact me directly if that's something that would be helpful.

It was changed from display -> output https://gitlab.gnome.org/GNOME/mutter/blob/gnome-3-28/src/backends/meta-input-settings.c#L827 https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/133. This was an issue in fedora https://github.com/elementary/gala/issues/517 and I ported the changes to the 3.28 mutter expression https://github.com/NixOS/nixpkgs/blob/release-20.03/pkgs/desktops/gnome-3/core/mutter/3.28.nix#L26. You definitely have those commits, so maybe I missed something or did it incorrectly.

It's also very likely that I'm not reading the output of journalctl correctly 😅. I'm uploading the output of the journalctl for one of these crashed sessions after a reboot as well as my nix configuration. It's probably a lot to throw at you, but hopefully minimal enough that it's not too much noise. If there's something that'll be more helpful I'm happy to do that.
On another look at the output it seems there's a number of things going wrong with failed asserts including the original missing 'display' key. I'm really out of my depth as I've never debugged the Pantheon or Gnome stacks before. Like 1581 should be the missing 'display' key, I'm hesitant to say more or I might point you in the wrong direction.
journal.txt
Here's my NixOS configuration. It's pretty close to vanilla so hopefully not too much.
configuration.nix.txt
hardware-configuration.nix.txt
Let me know how else I can help and I'll do my best 😃

I believe you found the correct error, but it's coming from gnome-settings-daemon's gsd-wacom.

Here's another thing I should mention, on 20.09 this is probably not an issue. We don't use mutter 3.28 anymore, but mutter 3.34. 20.03 is not EOL yet, but it will be once 20.09 is released which is very soon.

Ahh, so it seems I ported to an API that didn't exist for me :grin:  This commit https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/bbeb97900cbac8438341a92f11c6cc8340c014f2 isn't going to be in the fork of g-s-d we use in pantheon 3.30.2

Ah, so I found a bug but attributed it to the wrong software 😆. I'm glad you have an understanding of this. Does this mean that g-s-d needs a similar patch and the issue will be more-or-less resolved for 20.03? I'm new to the Nix community so I don't really have perspective on what the right course of action would be, especially with a new release coming out so soon.

Yeah, if I backport this PR to g-s-d for pantheon https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/37 I think everything should work (since we already backported the stuff for mutter, just not g-s-d)

If you do backport that PR, I'd love to give it a go and see if it works if that would be helpful - I might need some direction on applying those changes to a Nix system.

Also, @worldofpeace, you're absolutely right that 20.09 doesn't have this issue.

Sorry about this, I don't think I'll have the time within the EOL period to fix this for 20.03 :frowning: It is fixed in 20.09 so I will close this

Makes a lot of sense, thanks for the thoughtful responses!


Upgrade shelljs to 0.7.0 and fix fatal error handling

Before: fatal errors in run() print a stacktrace and no output
After: fatal errors in run() are caught and dump stdout

Thanks!


Can there be an option to compile the file freshly each time it is loaded?

I created a sample project at https://github.com/NiranjanTambe/latexonline.cc
I committed a file and formed a build URL from the latexonline.cc
Then I added another commit and changed one word from the file. i.e. second in place of first on the 8th line of the code and 3rd line of the output.
What I expect is if I send the build URL in a mail and someone opens it ten years later, the output should show the output that is considered to be latest at that time. If not by default at least with an option like &freshcompile in the URL itself. So that it would be compiled again freshly. (Personally I don't consider this ideal, but still...) Is it possible to provide such a mechanism?
Right now even if I provide the URL of a file from a specific commit it doesn't show me the output of the code at that point of time in the commit-history. e.g. https://github.com/NiranjanTambe/latexonline.cc/blob/c13b957f1d2490da57144f4b455de5e5c6032c5b/test.tex is the address for the test-file at the point of second commit. If I generate a build URL for this address I don't get the commit part of it in the output URL. The URL produced by the site currently is still the same as the earlier one.
Ideally the normal URL (without any specific reference to a commit) should always freshly compile the file every time the URL is loaded. This might slow-down the process a bit, but it would be more transparent IMO.
There should also be an option to compile files from a specific time in the commit-history. Suppose a particular file is absent in the latest version of the project; but at some point of time it was there, loading the URL from the commit-history is the only option available and in the given mechanism it seems to be impossible.

Can't you use latexonline.cc/compile?url=https://raw.githubusercontent.com/niruvt/latexonline.cc/main/test.tex


Store a Requests.Response to HDF5

Hello,
I'm new to Julia. I'm a Python dev.
I'd like to be able to make a sort of cache mechanism of HTTP requests like requests-cache
see https://github.com/JuliaWeb/Requests.jl/issues/101
Ideally storing response to any kind of database (SQLite, MySQL, PostgreSQL...) will be nice but I haven't find an ORM like SQLAlchemy for Julia...
requests-cache is serializing response using pickle
So I have been looking at serialization and Julia and found this SO question
http://stackoverflow.com/questions/24958248/julia-how-stable-are-serialize-deserialize
An answer point to https://github.com/JuliaLang/HDF5.jl so I'm trying HDF5.jl
Here is my code:
using Requests
using HDF5
resp = get("http://httpbin.org/get")
key = string(resp.request.value.uri)
h5open("cache.h5", "w") do file
    write(file, key, resp)
end

but it raises
ERROR: MethodError: `write` has no method matching write(::HDF5.HDF5File, ::ASCIIString, ::HttpCommon.Response)WARNING: Error showing method candidates, aborted

Any idea ?
Kind regards
PS: please excuse my newbie question!

HDF5 has been split into two package, the (new) HDF5 and JLD. You might try it with JLD.

Ok so I will have a look at https://github.com/JuliaLang/JLD.jl

I did
using Requests
using JLD
resp = get("http://httpbin.org/get")
key = string(resp.request.value.uri)
jldopen("cache.jld", "w") do file
    write(file, key, resp)  # alternatively, say "@write file A"
end

retrieved_resp = jldopen("cache.jld", "r") do file
    read(file, key)
end

it works fine...
but the path is still long to make a Requests-cache.jl library
If you know some people who could be interested in working on such a project please ping them...
Pinging some people for JuliaWeb: @malmaud @jrevels @MikeInnes @sbromberger @WestleyArgentum

Pinging also @reclosedev (author of requests-cache)

You could always launch a squid server and set HTTP_PROXY to point to it - not sure it's worthwhile to reinvent that wheel in Julia.

I prefer to have a pure Julia solution.
Here is my first implementation https://github.com/femtotrader/RequestsCache.jl
I'm planning to use it for https://github.com/femtotrader/DataReader.jl


[1.17] java.lang.NoClassDefFoundError

latest.log
Log file contains the error in the title in greater detail. I have to keep force-closing minecraft at worldgen because it will hang at a random percent, throwing errors related to this mod.

Turns out I somehow forgot to grab this. Apologies.


Is it safe to execute multiple lruns simultaneously?

should be fine if in separated directories

Yes. Beware that if you are running lrun in different pid namespaces (not recommended), you need isolated cgroup mount points.
If you found undesired behaviors, please report as a bug.


fix: downstream dts for fp-ts types

fixes a typescript edge case for buildable packages which export dts containing type inferences for fp-ts types

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

14 of 14 (100.0%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2430

Relevant Lines:
2430

💛  - Coveralls


Use handwritten ansi parser

Motivation
indicatif recently removed their direct dependency on regex, but it still ends up getting pulled in through the ansi-parsing feature of this crate.
Implementation
There's nothing too exciting here. The regex was switched out for a manually implemented dfa. The dfa is represented by State which is driven by find_ansi_code_exclusive. I went through a few iterations and the dfa implementation seemed to be the cleanest in the end.
There are also a myriad of tests to try and ensure that things match the old implementation. Notably there is a proptest checking off the old regex and a test that generates strings with bytes used in ansi codes up to 6 characters long in an attempt to ensure that everything matches the old implementation.
Also beyond that I tested things with dfa_matches_regex_on_small_strings with up to 11 byte strings using the limited character set and I ran another test that tried all valid 5 byte or small strings to make sure they matched the old regex Matches. This wasn't kept in the test suite since things would take far too long to give fast feedback.
Impact
regex is a notably heavy dependency, so being able to remove it had some good improvements all around
Compile Time
Clean cargo build --release --features ansi-parsing, timed with:
$ hyperfine --warmup 1 --prepare 'cargo clean' 'cargo build --release --features ansi-parsing'

Before
Benchmark 1: cargo build --release --features ansi-parsing
  Time (mean ± σ):      5.395 s ±  0.061 s    [User: 28.892 s, System: 0.697 s]
  Range (min … max):    5.304 s …  5.531 s    10 runs

After
Benchmark 1: cargo build --release --features ansi-parsing
  Time (mean ± σ):      2.401 s ±  0.021 s    [User: 5.150 s, System: 0.405 s]
  Range (min … max):    2.374 s …  2.441 s    10 runs

Size
I wasn't sure if there was an ideal way to measure this. I setup a crate that depended on just console and printed out the results of AnsiCodeIterator on the string "hi". I also stripped the executable for good measure since there was a large size reduction from stripping such a simple executable
Size results from cargo build --release && strip target/release/testing
Before: 653 KiB
After:  305 KiB
Speed
I didn't directly test speed so this one is still unknown. I guess a good approach would be adding a benchmark to check the throughput for the new implementation iterating over something like sample_zellij_session.log and then backporting the benchmark to master to compare. From the small strings used in dfa_matches_regex_on_small_string, the new implementation was about 4x faster.

So I was curious about the speed changes, so I added in a basic benchmark that collects the results of AnsiCodeIterator to a vector along with timing strip_ansi_codes using the zellij_session_data that I already added as an asset used for a unit test. I ran the benchmark for these changes along with adding it to the current master with the one stipulation that I enabled all the default features since performance was pretty rough without the perf feature. With that being said here are the results I got on my laptop with a 11th Gen Intel i5-1135G7 (8) @ 4.200GHz with it being plugged in to charge while running the benchmarks (there's a significant difference for me when it's on battery)
Before:
ansi-parsing/parse      time:   [132.74 us 132.95 us 133.19 us]
                        thrpt:  [83.469 MiB/s 83.616 MiB/s 83.748 MiB/s]
ansi-parsing/strip      time:   [125.79 us 126.17 us 126.60 us]
                        thrpt:  [87.814 MiB/s 88.111 MiB/s 88.375 MiB/s]

After:
ansi-parsing/parse      time:   [37.180 us 37.277 us 37.379 us]
                        thrpt:  [297.41 MiB/s 298.23 MiB/s 299.01 MiB/s]
ansi-parsing/strip      time:   [38.099 us 38.204 us 38.319 us]
                        thrpt:  [290.12 MiB/s 290.99 MiB/s 291.79 MiB/s]

So it looks like the changes did have a pretty significant impact even with a larger set of data that has quite a few ansi codes.

Fewer dependencies is always a huge plus in my book. Thank you so much for this!

@LovecraftianHorror unfortunately the PR appears to be using some features unavailable in the (quite old version of Rust) this is targeting. Now 1.40.0 is quite a bit older than what I think is sensible. I would probably be okay moving this up to 1.46.0 but not higher since that's something I'm targeting with insta and other libraries that use this still.

I should be able to make the changes compatible with 1.40.0 without too much effort. It is a pretty old version though like you said, so if you want to bump it then that works too!
I'm afk so I haven't checked, but I would assume this is compatible with 1.42.0 with the different pattern matching features used

I think moving this up to 1.42 or 1.46 is fine. Barely anything targets 1.40 these days.

6339a03a0ec32dd9818cda68fbe1a6758469e076 makes states addressed by the enum instead of the variants
c548986b85ee82df383f90022176ee15708fedf2 removes all uses of or-patterns inside match destructuring (I forgot that stabilized so recently)
f939e526738737c8d41afff50b48796dedf54688 switched out all uses of matches! for slightly more verbose matches

c548986b85ee82df383f90022176ee15708fedf2 brought the MSRV down to 1.42.0 and f939e526738737c8d41afff50b48796dedf54688 brought it down to 1.40.0 since it was such a simple change.

This looks good. I will merge this after a final review.

Just from a quick look, the older tests fail because both criterion and proptest don't build back on 1.40.0, even though console itself can still build back on 1.40.0
The clippy lints on the other hand are because of using match where it would be more appropriate to use matches! instead, but that change was specifically made to support an older version of rust.
I'm not sure how you want to approach this. Only testing on the most recent stable could help with the first note since libraries intending to be used as dev dependencies are more likely to use newer versions of rust. The second note could just be an #[allow] above the two cases where matches! was removed

I'm going to try to fix the CI setup. Unfortunately the version of rust we're targeting throws dev and non dev dependencies together which is why this is happening. I will probably going to move the tests up a few versions and only check against 1.40.

Sounds good, thanks for all your help getting this PR over the finish line!

Would be nice to get this out in a release!


Add enemy zone

Enemy zones are either randomly selected, or selected from markers that are present on the map.
Random selection is only used if there are no markers on the map.


Update Account.php

Added additional fields

@bobandjokic thank you for your contribution.
I see several problems with this PR. Let me write back to you soon


freezing backbone part

@chensnathan Hello, nice work! In the code, in addition to batchnorm layers in backbone, I noticed that stem conv and res2 block of res50 are also freezed during training. Is that a principle design or u just find it will achieve better training process if these additional layers are freezed?

It is a conventional setting for detection. You can check here for more details.


Temoa

This PR:

Updates all temoa models to match the current version of temoa.
Adds items to .gitignore
Makes data_parser.py more robust to future changes by adding regex
Adds packages to requirements.txt to match the temoa environment

New temoa models can now be added.
Eventually, these first scenarios will be removed from the snakemake once we have a complete model of UIUC that includes transportation, energy storage, and new economies like hydrogen.

Hello @samgdotson! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file temoa-uiuc/data_parser.py:

Line 606:80: E501 line too long (84 > 79 characters)

I've run one of the cases and I got this warning:
Warning: ('uiuc', 'IMPELC', 2000) has a specified Efficiency, but does not have any existing install base (ExistingCapacity).
Warning: ('uiuc', 'ABBOTT', 2020) has a specified Efficiency, but does not have any existing install base (ExistingCapacity).
Warning: ('uiuc', 'TURBINE', 2020) has a specified Efficiency, but does not have any existing install base (ExistingCapacity).
Warning: ('uiuc', 'NUCLEAR', 2020) has a specified Efficiency, but does not have any existing install base (ExistingCapacity).
Warning: ('uiuc', 'UL', 2000) has a specified Efficiency, but does not have any existing install base (ExistingCapacity).
Warning: ('uiuc', 'UL', 2020) has a specified Efficiency, but does not have any existing install base (ExistingCapacity).
Warning: ('uiuc', 'UH', 2000) has a specified Efficiency, but does not have any existing install base (ExistingCapacity).
Warning: ('uiuc', 'UH', 2020) has a specified Efficiency, but does not have any existing install base (ExistingCapacity).
I am still familiarizing myself with TEMOA, how important is this warning?

I don't think it's a problem, it still produces results. I'll check if it changes anything.

@robfairh

The warning doesn't hurt anything. It's just pointing out that I offered an efficiency for some technologies that didn't actually exist in the years specified. 2000 and 2020 are considered "existing" time periods. We didn't build an import system (IMPELC) in 2000 so the technology doesn't "exist". It's a bit weird.
I have fixed scenario04 to stop the warnings. If we want to do this for the other scenarios we can (by opening a new issue) but it's not essential.

Great! I think you have addressed all of @yardasol's comments as well. So I'll merge the PR.


Error resolving lib.d.ts

http://localhost:8080/typescript/bin/lib.d.ts 404 (Not Found)
When trying to load the default library 'typescript' is not resolved to its correct location. It can be worked around by installing npm:typescript in the master project but that should not be necessary.

duplicate of https://github.com/frankwallis/plugin-typescript/issues/9


Youtube videos don't play

Hi.
It seems that youtube videos don't play, it transforms into a blank space after pressing "Play button".
Can you fix it, please?
(macOS Sierra 10.12.4)

No idea why or how to fix this. PR welcome together with an explanation of why it didn't work and how it was fixed.
I'm not going to fix it.


Xcode14 with apple M1 build error

any update news  about this lib ?

@onebean06 please go through #79 issue once


Make help command an embed

Make the help command look better by making it an embed

Just migrate the bot to python at this point smh

q ww

 15 May 2020, that's when

Fixed in latest merge


08 16 2023  as make GitHub repository private

Required items, please complete
Change(s):
New Playbook
Reason for Change(s):
New Playbook
Testing Completed:
Yes

Hello @AcceleryntSecurityDev, Thank you for raising this. This PR will be examined and will update you shortly before 24 August, 2023.

Hello @AcceleryntSecurityDev, can we connect tomorrow for this PR. I've a query.
If it's possible for you please let me know on this PR or even you can drop a mail to<EMAIL_ADDRESS>I work in IST Time Zone and I'm usually available between 2:00 PM to 6:00 PM.
Thanks,
Prasad.

Hello @AcceleryntSecurityDev, As asked earlier please respond if you are available for the call.
Thanks.

@v-prasadboke Hello Prasad, sorry I was unable to connect. I typically work on pacific time, so meeting in your proposed time window would be difficult. I do see these playbooks have already been merged, but if you still need to reach me, you can send me an email at<EMAIL_ADDRESS>


create users signin, login, logout views and routes and added login decorators to prot…

…ected views.

Alright, I'd change that. I'm off my workspace for today. I'd do it tomorrow

I've commented out the login_required decorators.

     form = UserAuthenticationForm(data=request.POST)
     if form.is_valid():
           username = form.cleaned_data.get('username')
            password = form.cleaned_data.get('password')
            user = authenticate(request, username=username, password=password)

See that section of code?
I think I've done something like this before to get the user
    if form.is_valid():
        user = form.user() # I'm not exactly sure if it's that method but something similar to get the user

It's just a suggestion though. This is also okay.

Okay, I've seen that.  I'd try that maybe next time

     form = UserAuthenticationForm(data=request.POST)
     if form.is_valid():
           username = form.cleaned_data.get('username')
            password = form.cleaned_data.get('password')
            user = authenticate(request, username=username, password=password)

See that section of code?
I think I've done something like this before to get the user
    if form.is_valid():
        user = form.user() # I'm not exactly sure if it's that method but something similar to get the user

It's just a suggestion though. This is also okay.

Okay, I've seen that.  I'd try that maybe next time


feat: export FPS and RAM reporting

We are integrating flashlisght profiler to our e2e tests pipeline and we would like to capture average FPS and RAM usage.
So I'm exporting everything from these files as it was done with cpu file.

Thanks for the PR! That makes sense 👍 Will merge once Bitrise CI has passed
Note: the iOS build seems to be broken since a Github Actions upgrade and is of course unrelated


bug: terraform plan is not working

After cloning the repo and doing terraform init and repo root, it is observed terraform plan is not working

Hi please see the examples, you reference this as a module and not run directly from cloning the repo.


Storing Workflow Spec and Status in alternative storage (Database)

Summary
Inspiration from #7121, Current Argo has etcd limitation of 1 MB on workflow object.   Argo is already supported nodestatus offload. to. DB helps for large output workflows but if we have a large no of steps/templates. It couldn't create workflow objects in k8s.
Proposal:
The entire workflow can be stored in DB and the controller will interact with the DB for workflow updates.  and execute steps in k8s pods.
What change needs making?
Use Cases
When would you use this?

Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

Duplicates #7121.


more asv bot testing

[ ] closes #xxxx
[ ] tests added / passed
[ ] Ensure all linting tests pass, see here for how to run them
[ ] whatsnew entry

@github-actions benchmark -b ^io.csv.ReadCSVEngine

@github-actions benchmark -b ^io.csv.ReadCSVEngine

@github-actions benchmark -b ^io.csv.ReadCSVEngine

@github-actions benchmark -b ^io.csv.ReadCSVEngine

@github-actions benchmark -b ^io.csv.ReadCSVEngine

@github-actions benchmark -b ^io.csv.ReadCSVEngine

@github-actions benchmark -b ^io.csv.ReadCSVEngine

@github-actions benchmark -b ^io.csv.ReadCSVEngine

@github-actions benchmark -b ^io.csv.ReadCSVEngine

@github-actions benchmark -b ^(?!libs)

@github-actions benchmark -b ^(?!libs)

@github-actions benchmark -b ^\(\?!libs\)


Reference to Documentation Guide

Should we add a reference to the Documentation Guide in https://diataxis.fr/ or https://documentation.divio.com/ (not sure which is the official one) and indicate that Implementation Guides should aim to be "How-To Guides" as per the top right quadrant?
Copied from https://github.com/jonathan-r-thorpe/nmos-implementation-guide-handbook/issues/1.

@jonathan-r-thorpe can you comment?

Added in #3, closing.


Hello,There is no gulpfile

No gulpfile found...

Oooopsss!! Sorry, my fault! Thank you very much. Fixed in https://github.com/sayden/graphql-mongodb-example/commit/0a66970762b0dd212c92cd613356012d72029c95
Gulpfile was deleted as the scripts were very simple. Everything is done now with npm scripts


Can't send messages [Windows 11]

Checklist

[X] I'm reporting a problem with Chatterino
[X] I've verified that I'm running the most recent nightly build or stable release
[X] I've looked for my problem on the wiki
[X] I've searched the issues and pull requests for similar looking reports

Describe your issue
Since installing Windows 11, I can't use the enter key to send messages. When I press enter, it adds a new line to my message instead of sending it.
Screenshots
No response
OS and Chatterino Version
Windows 11 (version 21H2 | build # 22000.376),  Chatterino Nightly 2.3.4 (commit 79db02aa6, )

#3363 with https://github.com/Chatterino/chatterino2/issues/2844
You should be able to see the channel name highlighted in white when this issue happens, and highlighted in blue (via actually clicking into chatterino) when the issue is "resolved"

vs

I still get this bug every now and then, no idea what causes it; but seems to somewhat be when I open a new split (not consistent)

I only get this when I disable the "show input when it's empty" setting, in which case it happens quite frequently. Quiet annoying as I like this setting 😞

I only get this when I disable the "show input when it's empty" setting, in which case it happens quite frequently.

Yes, that setting is sadly a bit buggy rn, in that it messes with the way splits are being focused. If you take a look at the channel name in the split header, if the split is currently focused it should appear blue.
Now, with “Show input when its empty” disabled, press i.e. Ctrl+E to open the emote picker and close it again using ESC. You will see that while you can still type messages, the split itself is no longer focused (channel name is displayed white) and does not receive key presses correctly, which results in all hotkeys seizing to function (see #2714 #2844). Previously that meant things like Ctrl+E, Ctrl+F etc stopped working, but since #2340 that includes whatever keybinding you have set to send a message as well, thus enter is not being caught by chatterino itself but instead the text field just creates a new line.

Fixed.  I have a little suspicion that hotkeys don't save properly if you do that but instead they just get emptied.

I just updated Chatterino last night. Coming from a month or 2 old build and I get this issue way too much. Basically I can't chat at all. Haven't had it before ever.

[14:34:16.059] Mm2PL: if it's empty just reset it FeelsDankMan
[14:34:39.471] VulpesHD: okay that fixed it PagMan

had this issue today, apparently, all my hotkeys really did go away somehow

had this issue today, apparently, all my hotkeys really did go away somehow "Reset to defaults" in the "Hotkeys" tab fixed it for me.

Update to the newest nightly, we attempted to blind fix this in dfa3818a701d5445dea10c102712404fbc104f27

I'm using chatterino2-nightly-appimage because building from source takes an eternity. Would be nice if that package got updates every now and then.

the appimage the package is downloading would always be the latest.

Correct, while the date is not updated, the source of the appimage in the package comes directly from our automated builds, found here which was last updated 5 hours ago.

Is there anything to test now that I do have the latest nightly?
If the issue was that the hotkeys can be wiped randomly, it's not like there are steps to reproduce here.

Is there anything to test now that I do have the latest nightly? If the issue was that the hotkeys can be wiped randomly, it's not like there are steps to reproduce here.

More or less no, as mm2pl mentioned above, he believed it to be related to the hotkeys not being saved correctly, so other than attempting to turn off your machine while Chatterino is open, you are basically just waiting to see if it breaks again.

My computer did go down unexpectedly multiple times while chattering was running, not that I would notice the issue right away, but yeah something to keep an eye on from now on :D

I have the same Issue in macOS.
It happens usually after i use the emote inline search and tab for autocomplete.

I have the same Issue in macOS. It happens usually after i use the emote inline search and tab for autocomplete.

What version of Chatterino are you using? Commit hash is relevant if running a nightly version

I suspect this isn't reproducible in the latest nightly version or in the upcoming stable release. If it happens for you, please re-open this issue.


Question about input size

Hi @richzhang , I notice you adopt input image size as 6464. My question is if atribute input size is ok? or it should be dixed as 6464?

In my testing，only the images with equal height and width is ok.


Change Antora name to include a package- prefix

This should avoid collisions when importing both component and package
documentation through Antora.
Checklist

[ ] PR contains a single logical change (to build a better changelog).
[ ] Update the documentation.
[ ] Categorize the PR by setting a good title and adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog.
[ ] Link this PR to related issues or PRs.

Checked it against our only package. Works as expected.


Conn AddAuth not working?

I'm trying to authenticate using the digest ACL scheme, but AddAuth doesn't seem to be triggering any logs in the client or the server. Here is the relevant code snippet:
client, _, err := zk.Connect(hosts, time.Second, loggerOption)
err = client.AddAuth("digest", []byte("user:dummy"))
if err != nil {
	return nil, fmt.Errorf("Failed to authenticate against zookeeper with %s", err)
}

There doesn't seem to be an error or any log at all for AddAuth. Not sure if AddAuth is doing anything functionally.

Also willing to consider other methods of authentication if this approach doesn't work.

I realize that AddAuth isn't properly adding the authCreds to the Conn. I tried adding the auth creds before even going into the loop() in Connect() using a separate thread but it seems like it still didn't get added.

Found the issue. It turns out that setting the ACLs for the zookeeper nodes was required for it to properly authenticate.


feat(controller): Use different container runtime executors for each workflow. Close #4254

Adds containerRuntimeExecutors to workflow-controller-configmap so you can select the executor you want to use.
This is controlled by the operation - users cannot change this setting.
The operator can allow 1 or more executors.
Typically I'd expect this to be used for:

Trying out k8sapi or emissary executors.
Trying out any executor prior to switching the default.
Running some workflows more or less securely.

  containerRuntimeExecutor: docker
  containerRuntimeExecutors: |
    - name: k8sapi
      selector:
        matchLabels:
          workflows.argoproj.io/container-runtime-executor: k8sapi

@sarabala1979 can I request your review as I think @jessesuen  is busy

@sarabala1979 I accidentally closed this. Can you please review/approve?

I think in the future we can have defaultExecuter under ContainerRuntimeExecutors and deprecate ContainerRuntimeExecutor

I think in the future we can have defaultExecuter under ContainerRuntimeExecutors and deprecate ContainerRuntimeExecutor

I don't think I should make this change. I'd have to write additional code and deal with what happens when they're both defined, but this does not add any new capabilities but does force migration on our users at some point.


fix: eslintignore and prettierignore not working

NOTE

fix: .prettierignore and .eslintignore files were not being correctly used.

@namniak @alemesa this PR need to be approved one more time. I made a fix for the vulnerability issue.

@namniak @alemesa this PR need to be approved one more time. I made a fix for the vulnerability issue.


darling: unstable-2023-05-02 -> unstable-2023-05-14

Description of changes

The macOS 11 update has been merged to master:
                    c.'          zhaofeng@malus
                 ,xNMM.          --------------
               .OMMMMo           OS: macOS Big Sur 11.7.4 Darling x86_64
               lMM"              Kernel: 20.6.0
     .;loddo:.  .olloddol;.      Uptime: 108 days, 21 hours, 39 mins
   cKMMMMMMMMMMNWMMMMMMMMMM0:    Shell: fish
 .KMMMMMMMMMMMMMMMMMMMMMMMWd.    DE: Aqua
 XMMMMMMMMMMMMMMMMMMMMMMMX.      WM: Quartz Compositor
;MMMMMMMMMMMMMMMMMMMMMMMM:       WM Theme: Blue (Print: Entry, AppleInterfaceStyle, Does Not Exist Cannot Write File)
:MMMMMMMMMMMMMMMMMMMMMMMM:       Terminal: /dev/pts/144
.MMMMMMMMMMMMMMMMMMMMMMMMX.      Memory: 21082MiB / 32034MiB
 kMMMMMMMMMMMMMMMMMMMMMMMMWd.
 'XMMMMMMMMMMMMMMMMMMMMMMMMMMk
  'XMMMMMMMMMMMMMMMMMMMMMMMMK.
    kMMMMMMMMMMMMMMMMMMMMMMd
     ;KMMMMMMMWXXWMMMMMMMk.
       "cooc*"    "*coo'"

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

@ofborg test darling


Fix link to Storage Classes doc

Existing link does not lead to the expected doc/section, it probably moved. Fixed link points to correct content.

/lgtm
Nice fix

/kind cleanup

My tiny memory tells me that the defect was introduced by me.
/lgtm
/approve


Unistall to clear all 10 GB space

On my laptop I don't have a proper GPU and with CPU doing all the heavy-lifting it would be better to remove all the libs.
Is there a simple way to uninstall everything?
pip-autoremove imaginairy
only cleared about 4 GB

I believe I found the rest ~6GB data.
There are stable diffustion models in /home/USER/.cache/huggingface/ which I removed too.

Yeah good point that uninstall isn't a great experience as far as recovering disk space. Not sure if that can be fixed in an automatic fashion.  In the meantime, sounds like you're on the right track. I'd delete any of the following if they exist:

~/.cache/imaginairy
~/.cache/clip
~/.cache/torch
~/.cache/huggingface


Multiple issue with daemon command line

Your Environment

Verge Release: 4.0.1 fork for stealth
CPU: AMD A-10
GPU: Nvidia 1060
RAM: 12 GB
OS:

[ ] I'm using Mac
[ ] I'm using Linux
[x] I'm using Windows

I would like to start a master thread with all of the issues I've found so far.  There's multiple issue I've brought up in #563.  A working gui wallet needs to be built upon a working command line daemon.  Once the command line starts, passing useful status and error messages it will be easier to allow the gui to use them.

You can set a socks port= in by command line, but how do you bind to a local ip so you can select an adapter to use?  Is there a way to connect to clearnet instead of tor from the command line?

(qt-wallet) The last entry in debug.log that's made, unless there's a network issue is "No OBFS4 found, not using it."  This means that a normal connection is made without using bridges. Then the gui is non-responsive for about 20 minutes with no indication of what is happening. There needs to be more messages made to know the status.  Also, until connections are made I unable to close the wallet without force quitting it.

Running the daemon starts with "which: no obfs4proxy ...."  Should say simply "starting daemon"   "starting tor service" "writing output to tor.log" etc.

Attemping to solo mine, I've not been successful.  I've followed the month old instructions at https://www.reddit.com/r/vergecurrency/comments/7l0paf/idiot_ahead_solo_mining_help/ but myself and others haven't been able to.  It must be possible because the pools are able to, but maybe the pool software knows the correct way to connect where ccminer doesn't.  No matter what I do it says it's starting scrypt.

The final message that shows in in terminal is "[notice] Opening Socks listener on <IP_ADDRESS>:9089"  and I presume it's running properly.  Tor log has output.  What is going on here?  Needs more status messages, most importantly that the daemon is up and running.  Need to also know when it's connecting and to which servers.

Debug level would be nice.  On a normal run there should just be status messages, and not these minor error messages.

There's more and I may add some updates to this when I have time to write things up.
Edit:  Another feature that's been requested is the ability to run the daemon on a remote server and access through the wallet gui.  Would need option -nodaemon and -walletconnect [ipaddress:port]

I found adding -printconsole directs output to console:
https://github.com/vergecurrency/VERGE/blob/master/doc/dev-notes.md


componentWillMount and Reflux this.store don't play nice together.

I have an issue, using the ES6 Classes, if I have componentWillMount on my React Component, then the component will not listen to the Store. Can we make both of them work?
Or at least show an error in case the Component doesn't link to the Store.
I didn't understood why the Component did not update with the Store's state and eventually found out that if I have an componentWillMount, the Component will not be linked with the Store.

@eek I started reworking some of my old code last week to implement the new es6 features that @BryanGrezeszak was so nice to work on. I ran into some similar problems. If you have componentWillMount and componentWillUnmount in your Reflux.Component you need to add this line inside the function to make sure everything gets bound correctly:
// in your componentWillMount()
Reflux.Component.prototype.componentWillMount.call(this);

// in your componentWillUnmount()
Reflux.Component.prototype.componentWillUnmount.call(this);

After the new docs were out I was going to check them over to make sure this got in there somewhere, as its easy to miss!

Yep, this is something that's going to be in the new docs. Since the ES6 classes need to utilize some of the React lifecycle it is possibly to overwrite what they use. componentWillMount and componentWillUnmount are the only 2 it uses and therefore the only 2 possible issues.
The only real question about it is: do we need an API call for this, or (since it's a one-liner anyway) leave it to the raw JS way?
Of course, if the friggin ECMAScript guys would just stop tiptoeing around the concept of classes poking one toe in at a time and would instead just COMMIT and jump in all the way then they would just let us super() any method (instead of just the constructor) like every other language out there, and the question would be solved (...yes, I'm bitter about these sort of things).
Something like this.manualWillMount() and this.manualWillUnmount() or something like that offers a little magic to do it...and I wouldn't feel too bad about that since it's a more obscure issue anyway, so it wouldn't clutter up the docs too bad. On the other hand...it's just a one liner in plain JS...just documenting it well enough could work. I'm torn on this one.

@BryanGrezeszak You have to consider that right now it's just a single, easy line of javascript. In the future that might change.
Therefore I'd vote for a small, documented function.

@dodekeract - I'm leaning that direction too. Not so much for that reason (it's a line that's pretty fundamental to how JS works with prototypes, so I'm not worried about that). I just plain think it's too verbose to ask people to remember. I'm one of the people telling people how to do it, yet even I typed it incorrectly on a few occasions and was left wondering why my stuff wasn't mounting!
I'll have to put some thought into naming though. So we'll see where it goes.

@BryanGrezeszak
@dodekeract
super.componentWillMount.call(this); in componentWillMount would be ok. I vote for just documenting it.
Now users know that writing this.store = store; in constructor in order to connect a store.
So let them know add a line in these two functions to enable it correctly won't take them much more efforts to understand.
Just provide a example with something like
componentWillMount() {
    super.componentWillMount.call(this);
   // your componentWillMount code goes here
  }
...

Since Reflux.Component is an enhancement of React.Component and Reflux encourages user to replace React.Component  by Reflux.Component. Adding some renamed functions and asking users to move their code into them makes a bit more confusing.

@tommytroylin - Where is that super object coming from? JS only has super usage (and it's as a function) in constructors.

@BryanGrezeszak
developer.mozilla.org

@tommytroylin -
I've seen that in the spec, yet every time I've ever console logged this super object to see if it's implemented yet, it errors.
Did it just now in babel, and on codepen and both errored.
And when I researched the topic of super usage outside of constructors I found an entire article about how the feature doesn't exist, and all sorts of ways around it.
Yet MDN says its implemented. Am I going crazy?

...ok, I'm going crazy a little bit.
Apparently if you try to access the super object itself...error.
But if you access properties of it...you're fine.
I've literally been checking for that feature on and off for probably at least a year now...each time thought it wasn't working because accessing the super object failed. Didn't expect that you'd be allowed to access properties on it without being allowed to access it itself.
Oh well, a feature is a feature. I'll take it. Makes a lot more sense than implementing our own method.

@BryanGrezeszak
ECMAScript Spec - The super keyword shows that super is a keyword not a object. So assign/capture it as an object will cause error.
From my tests, when using super['propertyName'] or super.propertyName as a getter, it actually refer to SuperClass.prototype.propertyName.
When you call it as a function like super.sayHello(), it actually implicit called withthisas same as SuperClass.prototype.sayHello.call(this)

this is a keyword too, but I can still log the object it references at any given moment. I expected similar behavior from super.
Since I couldn't access it I just thought that meant the feature wasn't actually implemented. Oh well, live and learn: JS always has a surprise in store, no matter how much you think you know :)
But yes, it should remove the need for any call. So that's even better.

Documented.


add endpoints-framework-all uberjar artifact

endpoints-framework-all now has all transitive dependencies included
in its JAR, repackaged to avoid dependency conflicts
endpoints-framework-guice no longer has endpoints-framework as a
dependency, so that one can use the artifact with endpoints-framework
or endpoints-framework-all.
endpoints-framework-guice has a small Preconditions class now so that
it doesn't have to depend on Guava, which it previously was
transitively.
POM URLs have been fixed to be the correct address.

Codecov Report

Merging #55 into master will increase coverage by <.01%.

@@             Coverage Diff              @@
##             master      #55      +/-   ##
============================================
+ Coverage     79.66%   79.67%   +<.01%
- Complexity     1608     1609       +1
============================================
  Files           153      154       +1
  Lines          5415     5416       +1
  Branches        694      694
============================================
+ Hits           4314     4315       +1
- Misses          829      830       +1
+ Partials        272      271       -1

Impacted Files
Coverage Δ
Complexity Δ

...com/google/api/server/spi/guice/Preconditions.java
0% <ø> (ø)
0 <ø> (?)

.../server/spi/discovery/CommonPathPrefixBuilder.java
100% <ø> (+5.55%)
9% <ø> (+1%)
:white_check_mark:

Continue to review full report at Codecov.

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


Make dependencies work for python 3.6

Keep testing on python 3.6
Move dependencies out of dev
Change the versions of dependencies we require so that they can be installed on python 3.6

Should we also publish onto pypi on the cimg/python:3.6 image then?


Update the release notes format

Remove paragraph tags around unordered lists
Add paragraph tags around list items
Remove auto-TOC generation
Add placeholder for Flare-generated TOC
Revise CHANGELOG headers to be bold entries instead of primary bullets

not sure why the UTs are failing; running them on my machine and they all pass :/


Input begins resizing after 2 characters even though value doesn't fit

Video:
https://youtu.be/g0Rzrn357b4
My input:
<input ng-model="model" pu-elastic-input maxlength="8"></input>
It's set to have min-width: 50px which is just enough to fit 2 characters. I've tried to set some big max-width but it's no use.
Browser: newest Chrome.
Any clues what can cause behaviour like this? On all other inputs everything works fine.

Hello @Senthe,
Thank you for reporting this issue but I've tried to reproduce it with no result.
There is your input with max length attribute: https://jsfiddle.net/Trono/39dwo3ea/
Looks like it depends on you specific stylesheet. Are you able to prepare some real example?


Securre default rabbitmq config

As outlined here, we need a secure default setup for rabbitmq
https://groups.google.com/forum/#!topic/sensu-dev/oYZw_UUQf2A

A first step would be a secure default rabbitmq queue setup. This setup should ensure that only the server has write access to the clients. In this case a compromised client can still report false data but cannot invoke commands on other clients.

Any news on that? I would consider it a serious issue.

Closing due to inactivity, and also because several security configuration details have been documented over the past year (with more still in the works). Please feel free to create a new issue if this matter is not resolved. #monitoringlove

This is still an open issue. The lack of activity is concerning to me.


No default value is specified for Isolate errorAreFatal

The description  for constructor Isolate.spawn() reads:

Future spawn(void entryPoint(message), message, {bool paused: false, bool errorsAreFatal, SendPort onExit, SendPort onError})
...
If the errorAreFatal, onExit and/or onError parameters are provided, the isolate will act as if, respectively, setErrorsFatal, addOnExitListener and addErrorListener were called with the corresponding parameter and was processed before the isolate starts running.

There is no default value for the parameter errorsAreFatal. It is also not specified how the created (without the parameter) Isolate instance will handle the errors. The following sample code shows that by default Isolate instance is terminated on Dart VM version: 1.16.1 (Tue May 24 12:27:14 2016) on "windows_x64". (this behavior corresponds to errorAreFatal:true)
import "dart:isolate";
import "dart:async";

void entryPoint(SendPort sendPort) {
  // this should awake the isolate from suspended state, caused by error
  new Future.delayed(new Duration(seconds:2)).then(
      (_) {
        sendPort.send("finish");
      }
  );
  sendPort.send("hello");
  sendPort.send(", "+1); // cause an error that should stop the isolate
  sendPort.send("world");
}

main() async {
  ReceivePort receivePort = new ReceivePort();
  List receivedData = [];
  receivePort.listen(
     (data){
        print(data);
        receivedData.add(data);
     }
  );
  Isolate isolate = await Isolate.spawn(entryPoint, receivePort.sendPort);
  await new Future.delayed(new Duration(seconds:1));
  ReceivePort pingPort = new ReceivePort();
  pingPort.listen(
     (data) {
        print("receive ping back");
        receivedData.add(data);
     }
  );
  print("send ping");
  isolate.ping(pingPort.sendPort, response:"ping");
  await new Future.delayed(new Duration(seconds:2));
  receivePort.close();
  pingPort.close();
  print("receivedData: $receivedData");
}

CC @lrhn


feat: psp22 standard burn

Resolved all the comments and move this to a separate PR to main: https://github.com/r0gue-io/pop-node/pull/311

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Please upload report for BASE (chungquantin/feat-psp22_example@bea0e9a). Learn more about missing BASE report.

@@                        Coverage Diff                         @@
##             chungquantin/feat-psp22_example     #309   +/-   ##
==================================================================
  Coverage                                   ?   51.52%
==================================================================
  Files                                      ?       48
  Lines                                      ?     4902
  Branches                                   ?     4902
==================================================================
  Hits                                       ?     2526
  Misses                                     ?     2327
  Partials                                   ?       49

Files with missing lines
Coverage Δ

pallets/api/src/fungibles/mod.rs
92.51% <100.00%> (ø)

pallets/api/src/fungibles/tests.rs
99.69% <100.00%> (ø)


driver: wifi: eswifi: use common log module, NET_SOCKETS_OFFLOAD as default, use K_MSEC

use common log module across all eswifi sources, which allows
to compile with CONFIG_NET_SOCKETS_OFFLOAD.
Also fix k_timeout_t compilation failure when CONFIG_NET_SOCKETS_OFFLOAD
enabled and warnings.
Signed-off-by: Parthiban Nallathambi<EMAIL_ADDRESS>

CONFIG_NET_SOCKETS=y
CONFIG_NET_SOCKETS_OFFLOAD=y

These 2 Kconfig entry is not enabled by default for eswifi under wifi sample. So these compilation errors wasn't caught in previously. Should we define these under samples/net/wifi/boards/disco_l475_iot1.conf by default?

These 2 Kconfig entry is not enabled by default for eswifi under wifi sample. So these compilation errors wasn't caught in previously. Should we define these under samples/net/wifi/boards/disco_l475_iot1.conf by default?

Wouldn't these be needed for all the boards? Why not put them to prj.conf file?

As there are two distinct changes in this PR, please separate the log changes from k_timeout_t one, so two commits. Or perhaps three/four as you have mysterious cast and null check in there too.

Sure, will split it. Thanks

These 2 Kconfig entry is not enabled by default for eswifi under wifi sample. So these compilation errors wasn't caught in previously. Should we define these under samples/net/wifi/boards/disco_l475_iot1.conf by default?

Wouldn't these be needed for all the boards? Why not put them to prj.conf file?

Not sure here. ESP and winc1500 can't use this option if I am not wrong.

Wouldn't these be needed for all the boards? Why not put them to prj.conf file?

Not sure here. ESP and winc1500 can't use this option if I am not wrong.

Ok, in that case it is probably best to put the options to eswifi driver Kconfig so that they will be always selected if they are always needed for this driver.

@jukkar Thanks for the review. Commit are split and NET_SOCKETS_OFFLOAD enabled by default.

@parthitce: The title of this PR, "driver: wifi: use common log module" doesn't correspond to its content: it doesn't patch all wifi drivers to use common log module, and for the one driver it patches (eswifi), it makes changes beyond "use common log module".
Is this intentional? If so, please update the title accordingly. Otherwise, it looks like unrelated commits got into this PR, which need to undergo separate reviews (as some of them are questionable/may need further cleanup).
Thanks.

No, it wasn't intentional. Initial revision clubs all the changes in one single commit and later split into multiple units based on @jukkar comment and I missed updating the title. Now updated, but still as the changes are discrete title may not cover all the things the PR does here. Thanks

Now updated, but still as the changes are discrete title may not cover all the things the PR does here.

Thanks for updating the PR title. Something like "driver: wifi: eswifi: Various cleanups" would work too, to set reviewers' expectations right.

Now updated, but still as the changes are discrete title may not cover all the things the PR does here.

Thanks for updating the PR title. Something like "driver: wifi: eswifi: Various cleanups" would work too, to set reviewers' expectations right.

@pfalcon Thanks for the suggestions, updated the title.

@parthitce have you tested these changes with wifi/net shell?

@parthitce have you tested these changes with wifi/net shell?

@loicpoulain Was working on older master. Rebasing to latest failed to work now. git bisect shows 62580748e536d5ff14ecc290e114c034f1ccccfd (from https://github.com/zephyrproject-rtos/zephyr/pull/26349). I will check this. DNM please!

@parthitce: Thanks for the updates.
@loicpoulain: I assume that you'll keep an eye on this PR and approve once it's confirmed to work. (I just try to clear my review backlog before going on vacation.)

@pfalcon @loicpoulain https://github.com/zephyrproject-rtos/zephyr/pull/27041 fixes the issue.


TST: Cause of test_linsolve.py test failure

Recent CI runs fail with the following error in the "Prerelease deps and 64-bit BLAS" workflow. I believe I've tracked it down.
FAILED scipy/sparse/linalg/_dsolve/tests/test_linsolve.py::TestSplu::test_threads_parallel - AssertionError:
Items are not equal:
 ACTUAL: 14
 DESIRED: 20

That test runs the same basic SuperLU tests concurrently in 20 threads and expects them all to pass.
Cause
Removing the exception catchall yields this:
E   Traceback (most recent call last):
E     File "/usr/lib/python3.10/threading.py", line 1016, in _bootstrap_inner
E       self.run()
E     File "/usr/lib/python3.10/threading.py", line 953, in run
E       self._target(*self._args, **self._kwargs)
E     File "/scipy/build-install/lib/python3/dist-packages/scipy/sparse/linalg/_dsolve/tests/test_linsolve.py", line 709, in worker
E       self._internal_test_splu_smoketest()
E     File "/scipy/build-install/lib/python3/dist-packages/scipy/sparse/linalg/_dsolve/tests/test_linsolve.py", line 496, in _internal_test_splu_smoketest
E       self._smoketest(splu, check, np.float64)
E     File "/scipy/build-install/lib/python3/dist-packages/scipy/sparse/linalg/_dsolve/tests/test_linsolve.py", line 460, in _smoketest
E       rng = random.RandomState(1234)
E     File "numpy/random/mtrand.pyx", line 184, in numpy.random.mtrand.RandomState.__init__
E     File "_mt19937.pyx", line 130, in numpy.random._mt19937.MT19937.__init__
E     File "/usr/lib/python3.10/contextlib.py", line 78, in inner
E       with self._recreate_cm():
E     File "/usr/local/lib/python3.10/dist-packages/numpy/core/_ufunc_config.py", line 406, in __enter__
E       raise TypeError("Cannot enter `np.errstate` twice.")
E   TypeError: Cannot enter `np.errstate` twice.

(and the same error on another line)
The image builds using numpy nightly, which is 2.0.0.dev0.
I believe the error is this one: https://github.com/numpy/numpy/issues/24013
Solutions
Wait for the fix in numpy nightly.
If a green CI is desired sooner, I can confirm that protecting both random.RandomState calls with a lock resolves the issue. Happy to make a PR to this effect.
class TestSplu:
    rng_mutex = threading.Lock()

    ...

        with self.rng_mutex:
            rng = random.RandomState(1234)

Thanks for tracking this down @alugowski! I'm +1 for just waiting for the fix in the numpy nightly.

New nightlies were uploaded ~12 hours ago. This test passed on the most recent PR, gh-18790. So I'll close this. Thanks @alugowski!


Too much scrolling in one go on Android M

On a Android 6.0 (build number MRA58K) Nexus 5, scrolling via Solo::scrollDown() seems to scroll two pages down instead of one, causing tests to fail to find text that lives in the first page-down.

FYI, I've opened a PR to attack this issue. Checkout https://github.com/RobotiumTech/robotium/pull/787.
Cheers!


Restart on deploy for local LLMs

@hmusum Please review.
For discussion. Is this a valid approach?

Yes, looks good to me


fix(docs): book component

Adds an href property to the component, so it redirects.
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/scullyio/scully/blob/main/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?
Improves the book component in the docs app. It also changes the landing components so they redirect to a proper url.

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Other... Please describe:

What is the current behavior?
The book components in the landing page do not redirect.
Issue Number: #710
What is the new behavior?
The book components in the landing page redirect.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

@GuzmanPI can you gix the MC


Release org.scalatest.compatible in its own artifact

Hi Chee Seng,
Instead of including org.scalatest.compatible.Assertion as part of scalatest-core, please release it in a scalatest-compatible artifact that is a dependency of scalatest-core. This will allow people who make test libraries that include assertions to make them "ScalaTest compatible." For example, Akka testkit's expectMsg assertion could result in a compatible.Assertion and therefore be last in a test that requires Assertion. Given this would be a Java interface such libraries wouldn't be dependent on anything that needs to be updated each Scala release. It therefore should not have a Scala version number in its artifact id.
As we discussed it may not make sense to release this as a separate artifact in JS and Native.
Bill

Hi @bvenners , sorry I think we had some confusion here, scalatest-core.jar already does not include org.scalatest.compatible.Assertion, but scalatest.jar does, we were thinking scalatest.jar should not include org.scalatest.compatible.Assertion, does that still hold true?

@cheeseng I think actually org.scalatest.compatible should be released in its own artifact in 3.1.0 for the scalatest artifact. I'll post a new ticket about the general approach for 3.1.0.

@bvenners If we are to exclude compatible from scalatest jar I think we shall do this in RC1, can you confirm this?
Thanks.

Sure RC1 is fine.

Hi @bvenners , fyi I pushed a new commit for this:
https://github.com/scalatest/scalatest/pull/1693/commits/d0d449a4ec5cfc8e0b8c63f46e8124eb3c0484cd
for the following pending PR:
https://github.com/scalatest/scalatest/pull/1693
Thanks!


WRR-1011: Fixed storybook-utils eslint and prettier lint rules to not conflict

Checklist

[x] I have read and understand the contribution guide
[ ] A CHANGELOG entry is included
[ ] At least one test case is included for this feature or bug fix
[x] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
Storybook-utils's eslint rules and prettier lint rules are opposite for applying spacing after function keyword. Currently a workaround was applied to avoid the conflicts.
Resolution
I have reverted the code before the workaround intended to avoid lint warnings. The fix will be applied in https://github.com/enactjs/eslint-config-enact/pull/93.
Additional Considerations
Links
WRR-1011
Comments
Enact-DCO-1.0-Signed-off-by: Stanca Pop<EMAIL_ADDRESS>

Travis will pas once https://github.com/enactjs/eslint-config-enact/pull/93 is merged.


Support bag.to_dataframe when query planning is enabled

As far as I can tell, dask bags can only be converted to dask dataframes when query planning is disabled. It would be great to support both query planning, and the flexibility of turning bags into dataframes. Currently calling to_dataframe with query planning enabled throws the following error.

df = bag.to_dataframe(columns=['line'])
File ".../python3.10/site-packages/dask/bag/core.py", line 1624, in to_dataframe
return dd.DataFrame(dsk, dfs.name, meta, divisions)
TypeError: FrameBase.init() takes 2 positional arguments but 5 were given

Thx for the report, put up a pr. It will be included in the next release


About the extra Tiktok-style data

Hi @Wangt-CN, thanks for the great work!
I have noticed that you've collected an additional 250 TikTok-style short videos from the internet. Will you consider uploading them?  This would enable us to make a comparison with the the released model trained on it.

Hi @zehongs, I have submitted the query to the corporation to open-source the additional TikTok-style data. Since it is collected by the corporation so we need to get the permission.


ACM-9017: Add hosted control plane overview and resources dashboards

This is for story https://issues.redhat.com/browse/ACM-9017 to add two new grafana dashboards.

ACM - Hosted Control Planes Overview dashboard to show the cluster's capacity estimate for hosting hosted control planes and the related cluster resources.
ACM - Resources - Hosted Control Plan dashboard that users can drill down from the overview page to see the resource utilizations of the selected hosted control plane.

@subbarao-meduri @coleenquadros Please review and merge this PR. Thanks.


Allow to update running cluster configuration w/o restart of pods

Most of configs are dynamic and do not require restart
Config file change (config map change?) can be detected and configs reloaded (via sending signal to aerospike process or by pushing config via api by operator)

We are working on it. This feature will be added in the next release.

Fixed in Aerospike Kubernetes Operator 2.0 release.
Tracking under PROD-1277 - Rapid restarts: The Operator should allow for warm start in the most scenarios.


fetch.js uses Promise() -- how to use this on IE9?

The browser support icons suggest IE9+ support.  But fetch.js uses Promise() objects.  How is this meant to work?

It requires the polyfill described in the readme: https://github.com/github/fetch#installation

I see it now -- sorry for missing it!
You'll also need a Promise polyfill for older browsers.

$ bower install es6-promise

On Wed, Feb 25, 2015 at 10:29 PM, David Graham<EMAIL_ADDRESS>wrote:

Closed #90 https://github.com/github/fetch/issues/90.
—
Reply to this email directly or view it on GitHub
https://github.com/github/fetch/issues/90#event-242237002.


Add upgrade tool docs

Summary
Docs written by @ardalis
These were in the internal repo. Considering the issues with publishing and the fact that the tool has been released, this PR is a cleaner way of getting these docs into the public repo.

Did these get built anywhere?


Support nil argument type in query

Query for pagination with 'first'/'after' arguments can now support 'null' value for the first page. This avoids the need for two separate queries - without the 'after' argument to get the first page and with the 'after' argument for subsequent pages using the end cursor as the value.
An example follows:
vars := map[string]interface{}{
    "pageSize": 20,
    "cursorId": nil
}

var query struct {
    Users <type> `graphql:"users(first:$pageSize after:$cursorId)"`
}

if err := client.Query(ctx, &query, vars); err != nil { return err }
// Do something with first page

for query.Users.PageInfo.HasNextPage {
    vars["cursorId"] = query.PageInfo.EndCursor

    if err := client.Query(ctx, &query, vars); err != nil { return err }
    // Do something with next page
}

Why was this closed? Did you find a workaround for this issue?

https://github.com/shurcooL/graphql/issues/25#issuecomment-404256179
err := client.Mutate(context.Background(), createMutation, map[string]interface{}{     "title":    githubql.String("test"),     "parentID": (*githubql.ID)(nil), })

I've found a workaround for this package to have a null cursor:
    type Cursor interface{}
    variables := map[string]interface{}{
        "first":   10,
        "cursorID": (*Cursor)(nil),
    }


Syntax highlighting for conc REPL

It should be possible to leverage the ANTLR lexer used by Concurnas to implement this functionality within the code calling jline3

in progress

resolved in latest release


Require a name when newing a tamplate, and use it as default output dir

New syntax is:
spin new http-rust wondersite  # creates it in ./wondersite
spin new http-rust wondersite ~/projects/wondersite  # creates it in ~/projects/wondersite

The well-known parameter project-name is set to the name given on the CLI.  Templates no longer define this parameter.
Fixes #491, #479, #490.

This is awesome, thanks!


Change creates statements in walkthrough.md

Description

Change creates statements in walkthrough.md. Thanks to that command can be directly copied and executed in terminal without cloning the service-catalog source code
fix namespace name in cleaning up service catalog step
fix typo

/hold

/lgtm

/hold cancel


Add blackblox

Add blackbox exporter to this config of prometheus monitoring

Add to the docker compose.yml file
Add to the prometheus.yml file
Check working status of project

done


Architecture Epic

Tracking issue for architectural decisions.

[ ] Examples repository
[ ] Workshops repository

Closing this epic, tracking done separately.


Binary tree better constructor

As we don't now whether the parameter is easily moveable, passing by value is not a real option, so instead I pass by universal reference and perfect forward the arguments.
I need to constrain the template so I don't shadow the copy constructor and move constructor. This is not really needed because I deleted them, but it's better to have it in the example.
Should I get a variable length of arguments? Not needed by tests...

First, you'll need to branch this off of master instead of my other PR branch, there's no need to be dependent on it. (Feel free to close this and make a new PR if it's easier for you).
Second, let's look at this set of guidelines. Right now this only allows a moved argument, and I'm actually kind of surprised this compiles, but I'm not an expert at all the move semantics stuff. My surprise is the string tests, that pass in a const string& to the insert function, which then moves (?) that into a new binary search tree object. And I have no idea if you can reference the string object a second time in the tests. My guess is that it copies it on one of those calls and doesn't actually move it.
So, I think you need a const T& constructor too to allow copies. And users who want to move in can std::move() in their types. Except then you have the problem with insert, which would always use the copy constructor because it has a const T& type... You could make that take in a moved parameter too so then users would be free to move parameters into it using std::move. See for example std::vector push_back which uses that pattern.
So you are welcome to go down this rabbit hole, and I will happily help out and provide some input (I have only done this a few times, with lots of references), but it is beyond the scope of what's really needed. There is a reason why the advice is that you should really just avoid move semantics unless you need the performance.
(Ugh, I am so looking forward to Concepts rather than this enable_if stuff too).

close #245. Moved to #246 that branches from master. My bad.