Move the cluster deletion protection to the addons/db

So this requires that we click "Modify" on a DB Cluster, untick "Delete protection", and then delete is, is that right? Do you know how it works for instances offhand? Do we need to remove delete protection on those to delete them too, or do we remove it from the cluster? Probably the later I guess, just curious.
Also, is this an alternative to the MFA deletion protection recommended in the pen test?

@misaka this isn't an alternative to the MFA deletion protection, that was for the S3 buckets. this is basically moving one of the functionalities in the aws-account-setup script (the database cluster deletion protection) so that it's part of the infrastructure code, rather then part of the post-setup script.
regarding the deletion question - that's right, first we will need to modify the cluster to remove the deletion protection property, and then we can do the actual deletion. this is at a cluster level, so it applies to the individual databases that are a part of the cluster as well. in practice, if a database cluster has the deletion protection property enabled, then we cannot delete the cluster of the individual databases that are a part of it. disabling it momentarily will be the workaround.
I think this is a useful property to have in place, but it does interfere with automation - e.g. if we want the cluster to be deleted as part of the copilot app/service/environment tear down if that makes sense.


Weird issue in capitalization of B

I believe I corrected the file so that crvd-b was corrected to crvd-B.  But the main entry listing did not get corrected.

I only found one more like this:

This has been resolved on dev1

Still not resolved on DAI


Create Summary Report After Completion

Please create some sort of summary.date.log file in each CDH/CDP /opt/cloudera/ scanned directory which records all of the original SHA fingerprints of the affected JAR/TAR/WAR files and the SHA fingerprints of their modified versions.  This information may be helpful, but most importantly, can be used as a maker to indicate that a particular node has been secured.

Thanks for the report. We will consider this.

I have started work on logging for my clients, as the current code also breaks permissions with a umask that was not tested


[MM-20226] Added aria-label to Invite People textbox

Summary
The new Invite People modal textbox was missing an aria-label. This PR adds the default aria-label to the email input based on its placeholder.
Ticket Link
https://mattermost.atlassian.net/browse/MM-20226

@devinbinnie Shouldn't we make it dynamic? So if users are added, then the aria-label may read out the users?
Or does it already do that? (Maybe it does because react-select may already have support for that).

@devinbinnie Shouldn't we make it dynamic? So if users are added, then the aria-label may read out the users?
Or does it already do that? (Maybe it does because react-select may already have support for that).

I wanna say it already does that, I know with the multiselect component from the same library it will do that. But that's a separate concern to be handled elsewhere.
This is just to satisfy WCAG such that the input has an aria-label so that the input itself can be identified by a screen reader, rather than its contents.

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-4252.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

/update-branch

New commit detected. SpinWick will upgrade if the updated docker image is available.

Mattermost test server updated with git commit d3c1e76d059fc6ea6f95fd64529330eae21c3312.
Access here: https://mattermost-webapp-pr-4252.test.mattermost.cloud

Test server destroyed


libu2f-host: 1.1.7 -> 1.1.9

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/libu2f-host/versions.
meta.description for libu2f-host is: '"A C library and command-line tool that implements the host-side of the U2F protocol"'.

Checks done (click to expand)

built on NixOS
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 1.1.9 with grep in /nix/store/vyn1j1hggaah9x5vbk7jfgxlzf4x3zyb-libu2f-host-1.1.9
directory tree listing: https://gist.github.com/832be17f3c2fbe010b21cf2d65789bd4
du listing: https://gist.github.com/710ae3e01ba2142e9085068691ec8d8b

Rebuild report (if merged into master) (click to expand)

24 total rebuild path(s)
7 package rebuild(s)
7 x86_64-linux rebuild(s)
6 i686-linux rebuild(s)
5 x86_64-darwin rebuild(s)
6 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
gen-oath-safe
libu2f-host
pam_u2f
yubikey-manager
yubikey-manager-qt
yubikey-neo-manager
yubioath-desktop

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vyn1j1hggaah9x5vbk7jfgxlzf4x3zyb-libu2f-host-1.1.9 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A libu2f-host https://github.com/r-ryantm/nixpkgs/archive/76a80a1394851312b3432c30bd50c0a7e6516548.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vyn1j1hggaah9x5vbk7jfgxlzf4x3zyb-libu2f-host-1.1.9
ls -la /nix/store/vyn1j1hggaah9x5vbk7jfgxlzf4x3zyb-libu2f-host-1.1.9/bin

#58309


Change the RetryAspect log levels

This log message:
LOGGER.debug("Proceed with {} retries on {}", times, Arrays.toString(retryOn));

Should be set to trace.

Fixed.


update dependencies, Go to 1.16

Various minor version updates to deps.

Version release will happen after I successfully import + use this in some private code for a bit.


Can we apply this on sequence of 3D images?

Hi Kamnitsask,
Thanks for the code and tinyCnn model is working well.
I am curious to know if, we can apply this for sequence of 3D images.
Your help is highly appreciated!
-Dev

Hello Dev,
I guess you mean 3D volumes + time?
The current code has in quite some functions the assumption of 3 dimensions. So, at its current state, it cannot.
The extension to 4D should need small changes in the code, but they will be needed in a lot of places. I am not sure how easy it is for someone else other than me to follow the control-flow of the process and find all these places that need change. Probably would be tricky.
Currently, it's not in my plans to support this functionality. You could have a brief look into the code, starting point at ./deepMedicRun and going deeper. If you think it's readable and could be done, email me to speak further. If you think it'd take you a while, then I d suggest you look at other alternatives.
Kind regards,
Kostas

Hi Kostas,
Thanks for the reply!.
Sequence in this context i referring to multiple images sent a time not
just one.
As you know usually CT/MRI scans will have sequence images for a patient.
I am curious to know if i could submit sequence of images ~200 at time and
classify the images.
As in examples i noticed you are submitting only one image patch of patient
for training and classification.
Hope i explained well, other wise i can share more details.
Thanks in advance,
Deva
On 13 October 2016 at 19:42, Konstantinos Kamnitsas <
<EMAIL_ADDRESS>wrote:

Hello Dev,
I guess you mean 3D volumes + time?
The current code has in quite some functions the assumption of 3
dimensions. So, at its current state, it cannot.
The extension to 4D should need small changes in the code, but they will
be needed in a lot of places. I am not sure how easy it is for someone else
other than me to follow the control-flow of the process and find all these
places that need change. Probably would be tricky.
Currently, it's not in my plans to support this functionality. You could
have a brief look into the code, starting point at ./deepMedicRun and going
deeper. If you think it's readable and could be done, email me to speak
further. If you think it'd take you a while, then I d suggest you look at
other alternatives.
Kind regards,
Kostas
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Kamnitsask/deepmedic/issues/25#issuecomment-253524695,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEsYZIe9vMHQxin2FGf9yQaQqDelgtsmks5qzjw3gaJpZM4KTPba
.

Hello Deva,
I am sorry, but this is still unclear to me.
You say the CT/MRI usually have "sequence images" for a patient. Do you mean that they are 3D volumes, ie have many slices? If so, the software is made for processing exactly this type of data. For the segmentation of each voxel it processes 3D information, taking into account not only voxels from one slice, but from multiple.
If you are talking about 4D volumes, eg CT/MRI with the 4th dimension being time (eg for cardiac imaging, where to analyse the whole cycle of the beating heart), then quite some changes in the code would be needed.
It is not clear to me what you mean with "submit sequence of images ~200 at time and
classify the images.". I would suggest you explain in more detail/clearer what you mean. Bear in mind that the software is a segmenter. It does not "classify images". It "classifies voxels" instead, indirectly by classifying the contents of the patch surrounding each voxel. Hope this helps with any confusion.
Kind regards,
Kostas


Initial Value of SmileyRating

Hi I tried this awesome library and I would like to know how to take default value set in it or initially none should be chosen on smileyRating when user done interacts.

I solved it, my gosh, anyway hahha


[feature](invert index) does not create an inverted index to support …

…the match_phrase_prefix feature.
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run p0


TypeScript Roadmap: January - June 2020

Roadmap Overview
This roadmap is meant to give our team and users clarity over our priorities until June. It's meant more as a set of guidelines than as a strict set of tasks we are bound to finish.
At a high-level, we're going to be focusing on the following 5 goals:

Types on every desk, in every home, for every JS developer
Productivity through strong tooling
Approachability and UX
Community engagement
Infrastructure and engineering systems

The how is broken down into the following sections:

Language design and innovation
Developer productivity tools and integration
Education and UX
Community investment
Internal engineering

If you've seen our last 6-month roadmap, you will notice that our goals and areas of investment haven't changed. The biggest changes you might notice are specific work items and amount we'll be focusing on each area of investment.
Language design and innovation
TypeScript and the core type system

Enabling popular JS patterns in a type-safe way
Increasing expressivity
Proving relationships between types
Stricter settings
Implementing ECMAScript features

The goal of TypeScript's type system is to statically model patterns in JavaScript in a reasonable way while catching bugs and enforcing correctness. As more features are added to ECMAScript, and as we notice emerging patterns in the ecosystem, we have more work to do, and because the JavaScript world moves fast, so must we.
While nothing has changed here, new areas of focus might target a few core issues like:

running under multiple runtimes with conflicting global declarations
the nature of Promise unwrapping on generic types
exploring different approaches to nominal types
experimenting with local type declarations within types

Back to top
JavaScript: TypeScript beyond TypeScript

Making the JavaScript editing experience better
Smoothing the transition to TypeScript
Automating the addition of JSDoc types
Understanding more dynamic patterns

TypeScript isn't just for TypeScript anymore. Our userbase now includes the JavaScript ecosystem as a whole, whether they are

using .js/.jsx files in editors powered by TypeScript,
compiling purely with allowJs,
type-checking with checkJs (also enabled by the // @ts-check comment), or
transitioning to TypeScript

Whoever these users are, we believe TypeScript can serve them in some way.
We largely expect investment in the following areas:

editor tooling
polish in the existing .d.ts file generation from .js files
improving parity for JSDoc mode where appropriate (e.g. fixing up generics and supporting a broader set of tags)

Back to top
Committee Representation

Class fields (public and private)
Decorators
ES/CJS module interop
Pipeline
Pattern matching
Enabling more expression-oriented styles
Protocols

We are involved in several different committees, including TC39 and the Node modules group. We try to provide representation as

implementers of TypeScript, the type-checker
implementers of JavaScript language services & tooling
a voice for the users of both of the above

We're prioritizing forward compatibility with proposals/features that we've adopted early on. For now, we will mostly act in an advisory manner for outstanding proposals. To maintain focus, we will likely only be engaged with a few proposals at a time.
We hold a policy of not implementing features unless they reach stage 3 and we have high confidence in them.
Developer productivity tools and integration
Editor productivity

Editor responsiveness and faster project load times
Reducing paper cuts
UX around refactorings/quick fixes
Moving more contextual information to TS Server
Investigate Language Server Protocol
API protocol discussions with partner editor teams
Ensure fast syntax colorization on TS Server
Swappable project contexts (editor switching between different tsconfig.json files)
Support experiments around project wide error reporting efforts

More details here.

While editor responsiveness would typically land under speed, scalability, and stability, it is worth noting here because it has consistently come up as a problem. We've fixed many responsiveness bugs, and have continued to follow up with different users to understand where TypeScript isn't performing optimally. We have some ideas around I/O speed improvements and potentially migrating to a process-per-project model for TS Server to ensure cross-project navigation never blocks on projects that are already open. We also acknowledge that we will need some infrastructure for server scenarios.
We've been aware of some of the sub-optimal UI/UX around how our refactorings and quick fixes are requested and surfaced. One fairly clear issue is that our support for refactorings is often too finicky - we require very precise ranges around expressions and statements, and that can limit discoverability. A more open-ended issue is how to surface refactorings beyond what we have today. Can we make refactorings triggerable without a range where TypeScript can "infer" appropriate ranges? Is there a better UI to surface beyond a list of fixes/refactorings intermingled? These are areas worth exploring in the next 6 months.
Regarding swappable project contexts: Today, TS Server (and hence, your editor) always associates a file with the first tsconfig.json it can find walking up the chain of directories. That might be a problem in a codebase with multiple configuration files (e.g. a tsconfig.json and a tsconfig.test.json). Swappable project contexts will provide users with an easier way to edit with different build contexts - for example, differences in development and production builds, test projects, and perhaps multiple target environments (e.g. tsconfig.web.json, tsconfig.ios.json, tsconfig.android.json, etc.).
Regarding contextual information in TS Server: Editors like VS Code have their own logic to figure out things like the right sets of characters to trigger auto-complete, or how to colorize the code in a file, on their own. On the other hand, TypeScript's language service often lacks information for why an operation was performed. These are instances where each tool has to assume more than it reasonably can, and also leads to other problems. For example, code colorization happening as part of the editor might be a problem for "thin clients" (e.g. remote sessions) where TextMate grammar classifiers can impact responsiveness. As a result, we'll be investing in helping editors delegate to the language service.
Regarding Language Server Protocol (LSP): as Visual Studio builds out deeper integration for languages leveraging the LSP, the JavaScript/TypeScript Tools for Visual Studio team has working on implementing LSP support for TypeScript. The work and investigation is still in early stages.

Back to top
Linting

Editor integration for ESLint
Speed and scalability in editor scenarios

We've seen that there are areas for improvement in ESLint integration, both for JavaScript and TypeScript.
The main few things that we're being mindful of is

Initial setup experience with TypeScript and ESLint
Performance issues in TypeScript and ESLint
Editing scenarios for ESLint, regardless of TypeScript integration

It's not clear exactly what has to improve, but we'll be keeping a watchful eye here.
Back to top
Speed, scalability, and stability

Project references parellelization
Investigate permitting circularities in project references
Dive into common libraries that exhibit poor check times (e.g. styled-components and material-ui)
Investigate continuous logging infrastructure
Learn to profile better
Implement ways to get quick feedback from TS Server restarts

More details here.

Since we last started investigating, we discovered certain performance issues including slower performance on Windows in things like file-traversal, long check times when using certain libraries, and editor operations that are too aggressive in opening other projects or discarding contexts from open files. Early experiments for improving some of these appear promising, so we expect to see some work go into this area;
however, much of what we discovered was also that profiling memory allocations in JavaScript applications is really hard. Infrastructure seems lacking in this area (e.g. figuring out what is being allocated too much), and much of our work may reside in learning about more tools, or building some out.
One area we'll also be investing in will be parallelized --build mode for project references. There's long been potential to build several different projects in parallel, and while consumers of TypeScript's project references APIs can certainly implement this behavior, this seems like a clear win for everyone using tsc --build.
We've
When it comes to stability, we've had a hunch that we could be doing better. It definitely feels like users often end up restarting TS Server, or the entire editor itself. While it's good that the option to do so exists because no product is perfect, this shouldn't become the norm for users. Today we get various crash reports from editors when the language service crashes or violates an assertion - but we're not hearing why users are restarting the editor/language server when something goes wrong. This is understandable. Taking the time to report an issue is a lot of work. We'd like to drive down the number of crashes and also get some quick feedback when users choose to restart TS Server in the Visual Studio family of editors. Finally, we also are interested in a way to enable logging by default (since we already do this with ETW), but because there doesn't seem to be an easy cross-platform built-in way to do this, we might build one for TS Server.

Back to top
Education and UX
Handbook and Website

Better onboarding for different types of developers
Refreshed look & feel
Drive accessibility
Make the playground better for playing in

The handbook is close to done, and can be viewed here. The new website is coming together as well. We'll defer work around the new website to the Website Roadmap.
Back to top
Error and type display UX

"Smarter" diagnostics
More related error spans
Interactive diagnostics and quick info

More details here.

We've made further improvements in UX and error messages, with help from the community, and are carefully monitoring feedback from users around this. We don't have specific action items, but we will try to brainstorm on tough messages. One thing that we have recognized is that error message improvements have been a great way to involve others in the TypeScript community, who can often provide input beyond what our team thinks of.
We have been experimenting with editor UX changes that make it easy to explore types in quick info (editor tooltips) and error messages. We're holding these changes until we finish user studies on whether they actually help users fix issues more quickly.

Back to top
Community investment
downlevel-dts
downlevel-dts is a tool that we've had requested many times over the past few years. It lets library authors rewrite .d.ts files so that they can be consumed by older versions of TypeScript. For example, for Typescript 3.6, .d.ts files with get accessors in classes need to be rewritten to property declarations. This tool will need ongoing investment for each release containing new .d.ts syntax.
Back to top
DefinitelyTyped

Weekly DefinitelyTyped rotations
Surrounding infrastructure

types-publisher
dt-mergebot
dtslint

Back to top
External contributors

Weekly meetings to drive down outstanding pull requests
Dedicated time from engineering team to assigned pull requests following release candidates

Back to top
Partner teams
We'd love to hear from your team if you use TypeScript in interesting or broadly applicable ways. This gives us insight on various things we could improve. Please give us your feedback!
Back to top
API Consumers

Rolling requests for API endpoints
Provide help for consumers trying to provide richer experiences like Vetur
Investigate improving rich editing experiences

in enhancing plugins like IntelliCode
in templates

Back to top
Outreach

Public talks
Meetup attendance
In-depth blog post content
Help with TSConf coordination

We want to encourage members of our team to be involved with the community, and write and talk about things that they find interesting. This keeps us close to our users and makes the project itself more approachable.
Internal engineering
Team infrastructure

Enabling parallel builds on our own codebase when available
Circular buffer logging for TS Server
Investigate building out memory profiling tools

The idea here is really anything that improves

stability
productivity
ease of contribution

for development on the TypeScript project and any of our satellite projects.
Parallel builds will ideally speed up our build times.
Implementing our own circular buffer logging for TS Server may be the only way we can achieve cross-platform logging turned on by default with little cost.
We may consider building out memory profiling tools given that we need it, but few options exist for free.
Back to top
Organizational guidance

Internal guidance on TypeScript-first API designs
Providing internal partner teams with best practices for projects
Addressing major Microsoft-internal build regressions

Because we have the expertise, and because we are involved with the JavaScript community, we're able to provide a level of guidance across Microsoft to give users better experiences all around. Additionally, when we hear about major build regressions on large codebases, our internal teams can provide us with their source code, allowing us to create minimal repros (which is not always the case with external closed-source codebases). This work usually benefits external users in some way, whether it's because a bug fix generalizes, because we've produced better APIs, or because we've been able to extract new guidance.
Back to top

And yes, the fact that we're 3 weeks into February as I post this is embarrassing :D

@DanielRosenwasser

experimenting with local type declarations within types

Do you mean something like this?? 😮

profiling memory allocations in JavaScript applications is really hard. Infrastructure seems lacking in this area (e.g. figuring out what is being allocated too much), and much of our work may reside in learning about more tools

I have done a few PRs aimed at optimizing memory usage, and I have just blogged about how I discovered the latest such optimization in https://github.com/microsoft/TypeScript/pull/36845 here: https://swatinem.de/blog/moar-ts-optimization/
Nice to see the TS team is interested in investing more into this, and I hope this helps to move things along.

@DanielRosenwasser I remember that plugins were being discussed some time ago, but they aren't on the roadmap. Is it still something you plan to implement? (If not, is there something we can do to unblock this?)

@DanielRosenwasser Any chance to see the updated roadmap on the wiki/roadmap page? It looks like a dead page...

For the Handbook and Website section, I really hope that you will take a long look at all of the documentation issues. Especially Checking JavaScript Files.md is completely missing from the new Handbook.

Looks like the concept from https://github.com/microsoft/TypeScript/issues/35822 didn't make it into the roadmap. Can it be included for the next one?

@treybrisbane @DanielRosenwasser Correct me if I'm wrong, but I assume these "local type declarations" would basically just be so we could avoid repeating ourselves in more complicated types. It'd be nice if this feature also could extend to type guards as well - that's where I could use it the most currently as I have a project with some very complicated type guards (as they're asserting invariants about them - conditional types would delay the errors to the call site and feature some unhelpful messages of "X is not assignable to never", obviously not ideal).

Uhhhhhh. Are there any new update of long-term plan? (After June)

yeah,how?

I was just wondering about the plan for July - December 2020 as well.

Is there any roadmap for January – June 2021?

Is there any roadmap for January – June 2021?

We're working on it and should have updates soon. We plan to switch to a year-long roadmap format FWIW

We're working on it and should have updates soon. We plan to switch to a year-long roadmap format FWIW

The way I am thinking about it right now is we plan with 6 months in mind and if nothing changes, we just rename it to a year-long roadmap, which is basically what happened in 2020. 😄


Fix: retry image build

Description
On top of #395  and #391, THEEDGE-1278 also requires the retry endpoint to be fully working and it wasn't. This was mostly due to a logic on the post process that considered the image done due to its error status, so I merely did some status changes on the image to allow the postProcessImage method to retry the build. The commit itself doesn't get built again on img builder, just the installer, but I assume this is okay for now as most errors are on our side.
Fixes #THEEDGE-1278
Type of change
What is it?

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update

Checklist:

[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I run go fmt ./... to check that my code is properly formatted
[x] I run go vet ./... to check that my code is free of common Go style mistakes

Codecov Report

Merging #396 (0c5b623) into main (41807e6) will increase coverage by 0.03%.
The diff coverage is 24.39%.

@@            Coverage Diff             @@
##             main     #396      +/-   ##
==========================================
+ Coverage   26.03%   26.07%   +0.03%
==========================================
  Files          31       31
  Lines        2931     2965      +34
==========================================
+ Hits          763      773      +10
- Misses       2073     2093      +20
- Partials       95       99       +4

Impacted Files
Coverage Δ

pkg/clients/imagebuilder/client.go
34.10% <0.00%> (-0.48%)
:arrow_down:

pkg/routes/images.go
24.64% <0.00%> (ø)

pkg/services/images.go
12.00% <27.77%> (+1.49%)
:arrow_up:

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 41807e6...0c5b623. Read the comment docs.


UI Bug

Clicking on the map marker for the first time creates a thin popup bubble. When you click on the map marker again, it resets itself to the correct width

can’t figure out why it is not picking up the content’s width only for first time =( but
style.css
.key-row{
white-space: nowrap;
}
.leaflet-popup-content{
width: auto !important;
}

script.js
var add_marker = function(geo, text) {
...
for (key in text){
full_text += ('
' + key + ': ' + text[key] + '
');
}
…
}

This can be quick fix for the problem.

Thanks @hanbyul-here - that could work. Did you get it to work locally?  If so, can make a pull request?? :smile_cat:

I think leaflet style was getting confused because of 'hidden' style. I used width:0 instead of hiding map now it seems to work right.

buut also, how about not hiding map at all? I didn't notice that there is additional map function actually.. :>

closing this in favor of https://github.com/pelias/feedback/issues/14


Update Go syntax file with 1.21 builtins

Go 1.21 has new builtins min and max.

Go 1.21 has new builtins min and max.

Please consider also the new clear built-in function. Thanks.


Partner Experience: horizon upgrade best practices

Create a guide focused on upgrading from and to Horizon 2.x versions.
Provide insight on db migrations and state rebuilds and how the effect the installation.
Give guidance on how to prepare and plan for an upgrade before doing an upgrade.
Offer tips to confirm upgrade completion, and triage steps when it hasn't.
Closes #145

Something went wrong with PR preview build please check

Preview is available here:http://developers-pr241.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr241.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr241.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr241.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr241.previews.kube001.services.stellar-ops.com


Use integers only in Queue-Optimized.swift

Personally, I don't find this change improves the readability of the code. It's a small performance optimization but one that probably doesn't matter in practice.
If this was code that was executed thousands of times per second then sacrificing the readability for performance may be worth it, but since the goal of this project is to educate people about algorithms and data structures, readability should come first.
(That said, it's a good trick. :-) Maybe we could have an "optimization tips and tricks" section somewhere that includes this particular technique.)

I agree with @hollance. Having the percentage calculation gives a clear indicator on why the array needs to be resized.
Nice optimization trick though @chrisamanse!


Viewer theme can be switched between dark or light theme

Implemented the theme changing dropdown in Settings dialog.
The default theme of the application is taken from config.json and if not then default theme is according to users system.

Changes in MarkdownPopover are to support the link color for dark theme.

Reviewed from a user-perspective:
The switch between themes works really well. But it seems to have no effect on the apprerance of an editor used in the following features:

Import Places
Sidebar -> Metadata -> JSON Format

Ok I check. Thanks @clarasb


add windows workload migration guidance doc

https://github.com/rancher/windows/issues/110
https://github.com/rancher/windows/issues/17
SURE-4703
SURE-4546
SURE-4616

Hi @rosskirkpat, please also update your PR to be from staging rather than master as it will apply to an upcoming release. Thanks!

Thank you @btat and @jtravee for fixing this up and getting it merged!


added install for archived package foieGras

foieGras has been archived:
https://cran.r-project.org/web/packages/foieGras/index.html
added install code including for the dependencies that did not automatically install using this method, trip and tmvtnorm: https://cran.r-project.org/web/packages/trip/index.html https://cran.r-project.org/web/packages/tmvtnorm/index.html

Thanks Charles!


Question - Configuration for multiple nodes

In a Jhipster project I need connect to a ElasticSearch multinode cluster. How can I do that?
With Spring Data ElasticSearch I used:
spring.data.elasticsearch.cluster-nodes=node1:9300,node2:9300
But something similar, like this:
spring.data.jest.uri=http://node1:9200,node2:9200
or
spring.data.jest.uri=http://node1:9200,http://node2:9200
doesn't work.
Is there any way to connect to multiple nodes?

Hi @javieryanez , the support of multiple node was introduced in Spring Data Jest 3.2.2.
And the new configuration key is : spring.data.jest.uris
Do not hesitate to send me a feedback if it's don't work as expected with the 3.2.2.
Thanks.
Julien.

Hi @VanRoy ,
Thank you for you reply.
I haven't been able to prove it yet, but it's just what I needed.

Hi @VanRoy ,
I tried the configuration for multiple nodes but unfortunately it does not really work as expected for an elasticsearch cluster ensuring high availability.
There is no fail-over management if a node falls.
So I created this PR : https://github.com/VanRoy/spring-data-jest/pull/114
to make it possible to configure the node discovery (https://github.com/searchbox-io/Jest/blob/master/jest/README.md#node-discovery-through-nodes-api) .
I also added the default configuration of the scheme to be able to set https


Set bpfd group permissions appropriately on maps created by bpfd

Maps are being created 0500 (User RW but no Group access), so the Userspace program needs CAP_DAC_SEARCH to read or CAP_DAC_OVERIDE to read/write the maps. Update the map files after program is loaded to grant access the bpfd group.
Update the documents regarding the CAP_BPF and CAP_DAC_OVERRIDE for accessing maps.
Resolves: #349
Resolves: #351

However, I wonder if it would be better to set the permissions closer to where the maps are getting pinned.

I'm not sure if we want something like this in Aya, but maybe. Guess that's a Dave question.
I originally made the function call in bpf.rs in add_multi_attach_program() and add_single_attach_program(), but the tokio::fs::set_permissions() was an async call, which means all functions calling it need to be async, all the way up the chain. So I added the call to set_map_permissions() at the highest level that was already an async call. Not a rust expert, so I can rework if desired.

I think it would also be good to be able to set the file permissions based on the permissions on the map (e.g., don't allow writes if the map is read-only).

That information is not in the bpfd gRPC API at the moment. We would need to add it.


Sort results by nested relationship

I want to sort main result set by relation in an order.. eg lets say a post has many tags i want to get all post but they should be sorted by their tags using eager load.

Something likes this? (from the Laravel docs)
$orderBySubquery = Flight::select('arrived_at')
    ->whereColumn('destination_id', 'destinations.id')
    ->orderBy('arrived_at', 'desc')
    ->limit(1);

Search::add(Destination::class, 'location', $orderBySubquery)->get('Amsterdam');

Yea so all destinations result would be ordered by flight order by

For future readers of this issue, I recommend looking at this package: https://github.com/kirschbaum-development/eloquent-power-joins


cloneElement - if children are provided in the second argument of cloneElement they are ignored.

Does not work:
return cloneElement(component, { children })

Does work:
return cloneElement(component, {}, children)

This should fix some quirky bugs that pop up in 3rd party lib like bootstrap, etc.

:)


Role back a commit

@monsieurleberre please make sure you run integration tests next time.

I have another one pending that fixes the issue coming with this

Ok but this needs to be rolled back first to fix the tests.

@Aprogiena thanks, this was pushed and tests are failing the fix is to change the test, but we need to look at that more in depth.


Issue with @vite(\Nwidart\Modules\Module::getAssets()) and npm run dev

Hi there,
I’m encountering an issue with @vite(\Nwidart\Modules\Module::getAssets()). When I run npm run dev, it returns an empty array and doesn’t discover any assets. However, after running npm run build, everything is included, which leads to conflicts between some assets from the main project and the module.
As a temporary solution, I’m using:
@vite(['Modules/Blog/resources/assets/sass/app.scss', 'Modules/Blog/resources/assets/js/app.js'])
This works fine, but I’d prefer to resolve the issue properly.
I’ve read the documentation and followed the steps carefully, but it still isn’t working as expected.
Could anyone advise on how to fix this issue?
Thanks in advance!

Alright, I see that this is a custom package that was previously created by someone. It is truly amazing, and I hope someone will look after it in case something unforeseen happens.

That's the package?

In Laravel, building a module system or a package isn't actually difficult. For example, let's say I have a module called "Blog," and I want its CSS and JS files to be automatically discovered. It’s relatively straightforward to implement this. One approach I used is to extract the URL and find the module name using regular expressions to match the URL with some of my modules. While this worked for me, there’s likely a better and more efficient solution available.


Fix observation deletion crash

#545
I'm guessing what happened was that the response from the server was cached and thus was searching for an ID in realm that didn't exist.
I wasn't able to repro the issue after this, but please lmk if you can.

Hi @Chrischuck, I can still reproduce this issue (using a real iPhone device). I created a new observation in the app, didn't upload to the server, tapped the observation, deleted the photo, returned to the observations list screen, and waited.
After maybe 2 minutes of waiting, I get the following error message:

@albullington i see, i only tested deleting an uploaded obs, i can check out that test case

@Chrischuck did this resolve the error for you? I'm still seeing the error on iOS, and it seems to appear when I scroll down in the list. The deleted observation isn't being removed from MyObservations list, which might be part of the problem.
On Android, I'm seeing a slightly different, but related error:

@albullington Yep, it resolves the issue for me and gets removed from myobservations list. Although I have to use a simulator/emulator
https://user-images.githubusercontent.com/13311268/228645921-26a58708-ef42-460b-a781-049dc5365bba.mov


Conflicting recommendations regarding bind mounts

Describe your use-case which is not covered by existing documentation.
In the README file, there are conflicting recommendations.
The Usage section recommends against using bind mounts:

...
NOTE: Avoid using a bind mount from a folder on the host machine into /var/jenkins_home ...

The next section, Backing up data recommends using bind mounts:

If you bind mount in a volume - you can simply back up that directory (which is jenkins_home) at any time.
This is highly recommended. Treat the jenkins_home directory as you would a database - in Docker you would generally put a database on a volume.

As a user, I honestly don't know which option is better.

named volumes are the recommendation, see https://github.com/jenkinsci/docker/issues/881#issuecomment-882611061
(docs need updating)

Thanks @timja for the reference. So I'm guessing this issue should stay open as a documentation task.


Inferno Creation of List View

Currently there is no implementation of Buildertrend's list view using Inferno.JS

No longer including Inferno


backport pr: fix issue-30210 to release/v1.28

https://github.com/envoyproxy/envoy/pull/30338
Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/backport


ProGuard and 4.0.1 OkHttp issue

Hello,
I updated from 3.14.2 to 4.0.1 today.
With 4.0.1 I cannot make a release build because the build gets stuck in the ProGuard phase, "Optimizing (pass 1/5)". The whole process usually takes around 10 min, I stopped after 120 minutes as it was stuck there. Cleaned up everything, restarted Android Studio, same thing.
I reverted to 3.14.2 and build is successful again.
Any idea what could cause this issue?

Looking on Google, I found something similar a few months ago on Okio: https://github.com/square/okio/issues/516

I'm not the person to help, but to get full information out, what version of proguard are you using?

I am using the one dependant on Android Gradle.
Running "./gradlew buildEnvironment" I can see it's version 6.0.3.
Other info found along the way:

com.android.tools.build:gradle:3.4.2
wrapper version 5.1.1

FYI forcing the use of the latest ProGuard version (6.1.1) ends up with the ProGuard build phase failing with an ArrayIndexOutOfBoundsException error.

https://square.github.io/okhttp/upgrading_to_okhttp_4/#r8-proguard
Does the section on ProGuard here help?

You may want to switch to R8, it fixes all those issues, else you need to report to Proguard I thought 6.1 fixed both issues but it seems they only fixed one.

Ok thanks. I'll try to switch to R8 then, it sounds easy enough if I can trust the Android Studio docs :)

Duplicate of https://github.com/square/okhttp/issues/5167

I also encountered this problem and can reproduce it. I can provide a simple reproduction project if needed. @swankjesse

Using okhttp 4 and ProGuard optimizations will never end in the Optimizing (pass 1/5) process.

Thanks!

After upgrading to ProGuard 6.2.0/6.1.1, it is fixed.

After upgrading to ProGuard 6.2.0/6.1.1, it is fixed.

this works for me,Thanks a lot!


Add methods to Android and iOS Screen Base classes

Methods added to AndroidScreenBase:

text_array_from(id, query_text = nil)
text_from(id, query_text = nil)

Methods added to iOSScreenBase:

text_array_from(marked, query_text = nil)
text_from(marked, query_text = nil)

@oscartanner ,
could take a look?
Regards,


TCGA is dead

TCGA was replaced by the Genomic Data Commons, some overengineered platform where you have to put dataset in a shopping cart.

:sob:


How to monitor model training in python?

I tried to monitor model training in python.
def model_training():
    try:
        training = replicate.trainings.create(
            version="stability-ai/sdxl:c221b2b8ef527988fb59bf24a8b97c4561f1c671f73bd389f866bfb27c061316",
            input={
                "input_images": input_images,
            },
            destination=destination
        )

        training.reload()
        print(training.status)
        print("\n".join(training.logs.split("\n")[-10:]))

        return True
    except Exception as e:
        print(str(e))
        return False

But I faced an error : 'NoneType' object has no attribute 'split', What's wrong in my code? I followed sample here
How can I monitor model training process in python?

Hi @YouthDream0925. The reason why you're seeing this error is that training.logs isn't populated at the time you've called split on it. In the code you shared, the training is reloaded immediately after creation, so it's unlikely to have started yet and have its logs property populated.
Here's some example code for how you might monitor the progress of a training job (note that trainings take at least several minutes to complete, and as long as several hours, so a polling interval of less than 30 seconds isn't recommended):
while training.status not in ["succeeded", "failed", "canceled"]:
  if training.logs is not None:
    print("\n".join(training.logs.split("\n")[-10:]))
  time.sleep(30)
    training.reload()


I get this error when accessing to http://myuser.pythonanywhere.com/static/lendingbot.html

Hi,
I have set up the bot, and it's running (it has successfully placed an order),

...but when I try to access to the web server, I got this message:

Any ideas?

"Address already in use" usually means something else is bound to the default port of 8000. netstat -napt | grep 8000 to see what else is listening on that port. Or set a specific IP and different port in the default.cfg. If you changed it to port 80, then there could be a webserver already listening on that port running on that machine.

Do not use the built in webserver on pythonanywhere, please see the
documentation (under installing on pythonanywhere) on how to set it up with
their website.
On Thu, May 4, 2017, 8:23 PM Matthew<EMAIL_ADDRESS>wrote:

"Address already in use" usually means something else is bound to the
default port of 8000. netstat -napt | grep 8000 to see what else is
listening on that port. Or set a specific IP and different port in the
default.cfg. If you changed it to port 80, then there could be a webserver
already listening on that port running on that machine.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Mikadily/poloniexlendingbot/issues/317#issuecomment-299361614,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFXDuiA2KG38zGl693jrdLFSW2LLvjciks5r2pYpgaJpZM4NRZVe
.

@unclemimo is the issue resolved?

Solution given, closing.


Register

@JuliaRegistrator register

Error while trying to register: "Pre-release version not allowed"

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/105815
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" dff7e66c4b5410b10ee2764a79d6158b25e17645
git push origin v0.1.0


sensu client 1.3.1 refuses to start (no memory error)

OS: centos 7.3
Expected Behavior
systemctl start sensu-client
should start the application
Current Behavior
sensu-service[30653]: /opt/sensu/embedded/lib/ruby/gems/2.4.0/gems/ffi-1.9.locate closure from pool (NoMemoryError)
sensu-service[30653]: from /opt/sensu/embedded/lib/ruby/gems/2.4.0/gems/ffi-1.9.sensu-service[30653]: from /opt/sensu/embedded/lib/ruby/gems/2.4.0/gems/childprocess-0.5.
sensu-service[30653]: from /opt/sensu/embedded/lib/ruby/gems/2.4.0/gems/childprocess-0.5.
sensu-service[30653]: from /opt/sensu/embedded/lib/ruby/gems/2.4.0/gems/childprocess-0.5.rocess>'
sensu-service[30653]: from /opt/sensu/embedded/lib/ruby/gems/2.4.0/gems/childprocess-0.5.)>'
sensu-service[30653]: from /opt/sensu/embedded/lib/ruby/site_ruby/2.4.e'
sensu-service[30653]: from /opt/sensu/embedded/lib/ruby/site_ruby/2.4.e'
sensu-service[30653]: from /opt/sensu/embedded/lib/ruby/gems/2.4.0/gems/sensu-spawn-2.2.sensu-service[30653]: from /opt/sensu/embedded/lib/ruby/site_ruby/2.4.e'
sensu-service[30653]: from /opt/sensu/embedded/lib/ruby/site_ruby/2.4.e'
sensu-service[30653]: from /opt/sensu/embedded/lib/ruby/gems/2.4.0/gems/sensu-1.3.sensu-service[30653]: from /opt/sensu/embedded/lib/ruby/site_ruby/2.4.e'
sensu-service[30653]: from /opt/sensu/embedded/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
Possible Solution
changed the user and group  from sensu to root in the below file
/lib/systemd/system/sensu-client.service
Steps to Reproduce (for bugs)
Installed using yum.
Till now it was installing 1.2.1.  From today it started installing 1.3.1. We have this issue in 3.1
Context
tried to add a new client to the exisiting sensu server (1.2.1) opensource environment.
Your Environment
sensu server (1.2.1)  on centos 7.3
sensu client 1.2.1 (working fine)
sensu client 1.3.1 (error)
no extensions
basic plugins

Hi @jagadeeshops,
What CPU architecture are you seeing this issue on? Please run the following:
/opt/sensu/embedded/bin/ruby -e "puts RbConfig::CONFIG['host_cpu']"

The Sensu 1.3.1 packages are not yet in repositories. @jagadeeshops perhaps you are installing 1.3.0-1?

@amdprophet this is not related to 1.3.1, the version of sensu-spawn in the error predates our latest change.

@portertech you are right. I am using 1.30

@amdprophet   Architecture is x86_64

@jagadeeshops we released Sensu 1.3.3-1 today, it fixes FFI issues that cause OOM and segfaults, please give it a try!

@portertech   Its working now


karpenter module: "name" cannot be longer than xx characters:

Description
When the cluster name is too long, I have the following errors

[x] ✋ I have searched the open/closed issues and my issue is not listed.

Versions

Module version "18.31.0"

Terraform version:
v1.3.4

Provider version(s):

+ provider registry.terraform.io/cloudposse/utils v1.5.0
+ provider registry.terraform.io/gavinbunney/kubectl v1.14.0
+ provider registry.terraform.io/hashicorp/aws v4.40.0
+ provider registry.terraform.io/hashicorp/helm v2.7.1
+ provider registry.terraform.io/hashicorp/kubernetes v2.16.0
+ provider registry.terraform.io/hashicorp/local v2.2.3
+ provider registry.terraform.io/hashicorp/null v3.2.1
+ provider registry.terraform.io/hashicorp/random v3.4.3
+ provider registry.terraform.io/hashicorp/tls v3.1.0

Reproduction Code [Required]
module "karpenter" {
  source  = "terraform-aws-modules/eks/aws//modules/karpenter"
  version = "18.31.0"

  cluster_name = var.eks_cluster_name

  irsa_oidc_provider_arn          = var.iam_oidc_provider_arn
  irsa_namespace_service_accounts = ["karpenter:karpenter"]

  # Since Karpenter is running on an EKS Managed Node group,
  # we can re-use the role that was created for the node group
  create_iam_role = false
  iam_role_arn    = var.eks-node-group-iam-role-name
}

Steps to reproduce the behavior:

Create a eks cluster with a long name
try to use the module
terraform plan
error appear

Expected behavior
terraform success
Actual behavior
...
Error: "name" cannot be longer than 64 characters: "KarpenterInstanceStateChange-REDACTED"
...
Error: expected length of name_prefix to be in the range (1 - 38), got KarpenterIRSA-REDACTED
...

Additional context
The module should do a
substr(name, 0, 37)   for the aws_iam_role
and
substr(name, 0, 63) for the aws_cloudwatch_event_rule

I could do a PR fixing the problem
let me know if you want me to fix it

The module should do a
substr(name, 0, 37) for the aws_iam_role
and
substr(name, 0, 63) for the aws_cloudwatch_event_rule

No - this is bad and problematic. You will end up hashing the name into the same base value which then causes conflicts.
Have you tried using the latest version of the module?


Failed in v1.13.0-rc0 docker file build

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information
Just used the tensorflow/tensorflow/tools/dockerfiles/dockerfiles/devel-gpu.Dockerfile in v1.13.0-rc0 tag.

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary):
TensorFlow version:
Python version:
Installed using virtualenv? pip? conda?:
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:

Describe the problem
Here is the bug:
https://github.com/tensorflow/tensorflow/blob/a8e5c41c5bbe684a88b9285e07bd9838c089e83b/tensorflow/tools/dockerfiles/dockerfiles/devel-gpu.Dockerfile#L71
Provide the exact sequence of commands / steps that you executed before running into the problem
If the condition is false, bash return 1. Thus, it breaks docker build image process.
PLEASE PLEASE PLEASE find a guy who knows dockerfile and bash to write a build script. The quality of build process is absolutely unacceptable.
I tried last stable release v1.12.0 and recent release candidate. They all failed.
Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

Looks like you're right. Thanks! I've prepared an internal change that will resolve this, so I'm closing the issue.
However, in future bug reports, please do not be so rude.


Design issue of client and server packs being the same

As far as I know it's still this way, and it should not be.

They're separated between sides because of Packwiz and mrpacks. Both keep track of which mods go on the client and server. The autoupdater for the server does in fact have -s server to prevent client-side mods from being installed.


Spring cloud function does not take Multipart file as input.

java.lang.IllegalStateException: Failed to determine input for function call with parameters: '{}' and headers: [user-agent:"PostmanRuntime/7.28.2", accept:"*/*", cache-control:"no-cache", postman-token:"522f38e5-2956-419c-8514-11dfbf738476", host:"localhost:9090", accept-encoding:"gzip, deflate, br", connection:"keep-alive", content-type:"multipart/form-data; boundary=--------------------------882500909709544349532773", content-length:"234"]
Sample
@Bean
	public Function<MultipartFile, ResponseEntity> upload() {
		return file -> this.call(file);
	}
	private ResponseEntity call(MultipartFile file){
		System.out.println(file.getName());
		return ResponseEntity.ok().build();
	}

<dependency>
			<groupId>org.springframework.cloud</groupId>
			<artifactId>spring-cloud-starter-function-web</artifactId>
			<version>3.0.14.RELEASE</version>
		</dependency>
		<dependency>
			<groupId>org.springframework.cloud</groupId>
			<artifactId>spring-cloud-function-compiler</artifactId>
			<version>3.0.14.RELEASE</version>
		</dependency>

Expected Behaivour:
It should Accept Multipart file type as function has this type.

So all it means we do not provide out of the box a MessageConverter capable of converting input to MultipartFile, and we certainly can't handle every possible case since we don't know what those might be, but you can certainly add your own MessageConverter. After al it is one of the documented extension points specifically made to handle cases like this - https://docs.spring.io/spring-cloud-function/docs/3.1.3/reference/html/spring-cloud-function.html#user-defined-message-converters

I am going to close it as there is no action necessary. As stated before type conversion is one of the extension mechanisms exposed by s-c-function to the end user and for this non-standard case i suggest you utilize that by implementing your own MessageConverter as described here - https://docs.spring.io/spring-cloud-function/docs/current/reference/html/spring-cloud-function.html#user-defined-message-converters


Feature/html

added attractions,iternary and packing list layout to HTML file.

Thanks for approving.
We can mention this at the next meeting and discuss then, as that is the part Pak Ho covered, so I'm not too sure either.
Btw I did the packing list as a floating side panel, cause I thought it was a good idea, but I'm not too sure if it will cover some of the contents on the page, so please let me know if that is too much in the way and I will move it to a separate section.


Improve lookbehind RegExp support detection

As per https://github.com/gorangajic/isbot/pull/50 and specifically https://github.com/gorangajic/isbot/commit/acb6dcf401f32a48ec7024398f653ea9d7664f53#diff-168726dbe96b3ce427e7fedce31bb0bcR70, compatibility with non-chromium browsers was broken.
These browsers would throw a SyntaxError: invalid regexp group because they can not parse the lookbehind RegExp syntax. By wrapping the RegExp in a new RegExp constructor with a string, we can catch the SyntaxError and restore compatibility with non-chromium browsers.
I wonder if there's a better RegExp to use here rather than the lookbehind, but this PR should restore compatibility with other browsers again.
Fixes #54

Thank you! Great fix

Released in 2.5.3

Fantastic, thanks!


PytorchNvCodec build is broken in Windows runner

Can't build PytorchNvCodec module in self-host Windows runner:
https://github.com/RomanArzumanyan/VALI/actions/runs/7487968963/job/20381448650

Closing the issue as WNF because PytorchNvCodec module is deleted in VALI v.3


Support thread member pagination

Add a new field, ThreadMember::member, which is included when with_member is set to true on GetThreadMembers and GetThreadMember requests. GetThreadMembers now includes pagination when with_member is true.
Docs PR: https://github.com/discord/discord-api-docs/pull/5834

I was looking into implementing this and actually had the code in place, however I noticed an issue that didn't allow my solution to work. Currently twilight uses the Member struct to represent guild members which includes a required guild_id field. It seems this was included because accessing a guild member without knowledge of a guild id wasn't possible at the time. With this newest change, however, it is. I wanted to bring up some different solutions to see which one you all would prefer.

Make Member::guild_id an Option.
This would be the most straightforward solution, but it would also be a breaking change. In terms of semantics, some users may be confused as to how a guild member has a guild_id of None.

Make a completely new structure for specifically for guild members fetched from a thread.
As far as I can tell, this change wouldn't be breaking but it would introduce some redundancy.

Add a guild_id parameter to the to  request option
To be specific:

let res = http
        .thread_members(Id::<ChannelMarker>::new(12345678))
        .with_member(true, Id::<GuildMarker>::new(17891011)) // Requires both a boolean for getting the member as well as a guild id for twilight to deserialize the member.
        .await?;

Even though the API doesn't explicitly need the guild_id, we would make it a required parameter to allow Member to be properly serialized.
I'm also open to any other solutions or ideas.

Just my two cents on this.
According to the docs guild_id isn't even a field on the Member object. Based on this, I feel like making guild_id an Option would be the most consistent with Discord's API.
I could also see doing #2. It could be something like ThreadMemberData (or MemberWithoutGuild, which would allow this to be applied to any other situations that involve member data without the guild), with a method to convert into a normal Member that accepts a guild_id.
I really dislike option 3 because that imposes a requirement for any twilight user that isn't imposed by Discord. Although it's minor, but I feel like I should be able to do anything with twilight that discord's API allows, without having to make my own requests.

Thanks for taking this on. This is a problem that was encountered with other HTTP requests that work with members, so we can use their solutions here. You can set the guild ID for the response when converting the request builder into a Future, which will be used to inject the guild ID into member and member list bodies:
https://github.com/twilight-rs/twilight/blob/85bc21e2c3383c2d2e1b9c404ea368b9c8f4aba0/twilight-http/src/request/guild/member/get_guild_members.rs#L98-L117

Hi, so I when I was implementing this feature I saw this done for other http routes. But unless I'm missing something I believe this can't be done like it is in GetGuildMembers. Iirc all endpoints/events (besides getting thread members) that return guild members always share knowledge of the guild_id, which can then be injected into the model later on. In this instance of fetching thread members, both the user initiating the request and the api response don't give a guild_id. As a result another solution would need to be put in place to correct for this. (Again, I'm new to this codebase so correct me here if needed).


Driver Implementation for the cloudscale.ch API

A Driver Implementation for the cloudscale.ch API
Description
It's pretty simple, I have added a new driver for the cloudscale.ch API (https://www.cloudscale.ch/en/api/v1). The cloudscale.ch API is very simple and doesn't offer a lot more than what libcloud's compute module by default offers. I have also tried to communicate this in the documentation.
Status
The code feels mostly like it's done and ready for review. It passes 2.7, 3.3, 3.4, 3.5, lint and pylint. I have looked at other drivers in libcloud and tried to copy how they document/test. I haven't added tons of tests, but comparably to others the driver is also smaller and therefore the amount of tests seem to align.
Just let me know what you think. Happy to improve my code!
Checklist (tick everything that applies)

[x] Code linting (required, can be done after the PR checks)
[x] Documentation
[x] Tests
[x] ICLA (required for bigger changes)

@Feuermurmel I have improved pretty much all the documentation that you complained about, except for the two places where I've commented.

@tonybaloney How would you like me to modify error handling? Or what do you think is not clean enough?

@davidhalter if you haven't already, I need you to sign the ASF ICLA (an agreement for individual contributors) https://libcloud.readthedocs.io/en/latest/development.html#contributing-bigger-changes

@tonybaloney
I have signed it and I have also gotten confirmation:

This message acknowledges receipt of your ICLA, which has been filed in the Apache Software Foundation records.
With this message, the Libcloud PMC has been notified that your ICLA has been filed.

merged. thanks @davidhalter @pquentin @Feuermurmel and @href for getting this over the line and thanks for contributing to the project. New drivers can take a little bit of time but it's important to get some consistency.

@tonybaloney Thanks for reacting so quickly. Wish I could do that on my open source projects as well, hehe. Keep up the good work!

@tonybaloney The documentation doesn't seem like it's up-to-date. Did we break the builds with this PR?
(AFAIK I was able to build the docs with this commit).

@davidhalter It looks like that for some reasons docs builds haven't been automatically triggered for a while now.
I manually triggered it for latest for now and I will look what is going on with automatically triggered builds.

The manually triggered build has finished and the provider is listed there now - https://libcloud.readthedocs.io/en/latest/compute/supported_providers.html
I believe there were two issues.

Automatic build triggering has been broken for a while now (:sadface:) - dbd080383bdf977383170025ad5b2a68eabc10d8
Table with link to the provider documentation has been broken. Just a heads up - this table is automatically generated using ./contrib/generate_provider_feature_matrix_table.py script - e5fc049be73fb020ec33825dfd138c9e84379148

I believe both issues should be fixed now, but need to wait for the Travis and RTD build to finish :)

It looks like automatic docs build triggering is working again - https://travis-ci.org/apache/libcloud/jobs/188560819#L855 and provider matrix is also back again https://libcloud.readthedocs.io/en/latest/supported_providers.html#provider-matrix :)
/cc @tonybaloney

@Kami Thanks! Is there any way to PR for the website as well? I wasn't able to find a repository of it.


[HUDI-5487] Reduce duplicate Logs in ExternalSpillableMap

Change Logs
Reduce duplicate Logs in ExternalSpillableMap
We see hundreds of thousands of duplicate logs in the executor log.
22/12/26 21:13:40,864 [Executor task launch worker for task 0.0 in stage 480.0 (TID 211376)] INFO ExternalSpillableMap: Update Estimated Payload size to => 4567
22/12/26 21:13:40,864 [Executor task launch worker for task 0.0 in stage 480.0 (TID 211376)] INFO ExternalSpillableMap: Update Estimated Payload size to => 4567
22/12/26 21:13:40,864 [Executor task launch worker for task 0.0 in stage 480.0 (TID 211376)] INFO ExternalSpillableMap: Update Estimated Payload size to => 4567
22/12/26 21:13:40,864 [Executor task launch worker for task 0.0 in stage 480.0 (TID 211376)] INFO ExternalSpillableMap: Update Estimated Payload size to => 4567
22/12/26 21:13:40,864 [Executor task launch worker for task 0.0 in stage 480.0 (TID 211376)] INFO ExternalSpillableMap: Update Estimated Payload size to => 4567
22/12/26 21:13:40,864 [Executor task launch worker for task 0.0 in stage 480.0 (TID 211376)] INFO ExternalSpillableMap: Update Estimated Payload size to => 4567
22/12/26 21:13:40,864 [Executor task launch worker for task 0.0 in stage 480.0 (TID 211376)] INFO ExternalSpillableMap: Update Estimated Payload size to => 4567

Impact
Reduce noisy logs and reduce log size
Risk level (write none, low medium or high below)
none
Documentation Update
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@hudi-bot run azure

Help review. Thanks.
@XuQianJin-Stars @alexeykudinkin


fix: detect bzlmod in swift_update_packages.bzl

Fixes #686
In swift_update_packages.bzl we need to detect if bzlmod is enabled to forward the -bzlmod flag to the gazelle generator.
This should stop gazelle from requiring a swift_deps.bzl file when bzlmod is enabled and generate_swift_deps_for_workspace == False

@luispadron Can you ping me when you have these tests green?

Yeah oops copied the comment with tabs, I'll get to a laptop soon

@cgrindel should be good now. Do we have tests for swift_update_packages in Starlark, I may have missed them

Do we have tests for swift_update_packages in Starlark

The examples/integration tests ensure that the output continues to work. We do tidy_check on the workspace, but we probably should add it to the child workspaces. I just added #701, to track the work.


Live location sharing

In WhatsApp and Messenger, you can share not only your current location, but your current live location.
We should add a similar feature, maybe using Channels or Feeds to power the real-time aspect.

I will take a look at this @lukejacksonn @bookercodes. As far as the design goes, I am just going to put the location under the username in the right hand user list. Let me know if you guys had something else in mind.


Removed default of 3 h for a DeploymentConfig on OpenShift

It seems that this long timeout could cause issues to detect errors early in deployments e.g. when the pod fails to start. AFAIK it was introduced to compensate long pull times of images over slow internet connections.
However, since I consider this a rare use case compared to the normal usage (where an image can easily be downloaded in the 10 minute or so default), I wouls like to remove that as default. The timeout can always be set explicitly when coming into a very-slow network situation (where an upfront pull of images might make even more sense).
I open the discussion, whether a default of 3 hours should be used or not. Its not about the feature itself, which is quite useful (and which btw, if set, automatically uses a RollingUpdate deployment strategy, otherwise no deployment strategy is set).
// @jstrachan @jimmidyson @rawlingsj and everybody interested.

:+1: from me.

ok, seems that this is ok so far (== no one complaining ;-). We can still revert it back if there are objections.
[merge]


Special Characters and Bash

If you run the program as demonstrated at a Bash command, you could wind up with funky things happening if you have special characters in your password.
If your password is TheyreGreat!!!, and you run python pwned.py TheyreGreat!!!, Bash will interpret the double exclamation points as a call back to the last command run.
If your password is TheyreGreat!$, Bash will interpret the !$ as the last word of the last command run.
If your password is TheyreGreat!100, Bash will interpret the !100 as the hundredth command in your history.
To run the program properly, you'll have to put single quotes around your password if you have special characters in it.  Otherwise, the program would need to be rewritten to as for the password as input rather than a command-line argument.
And, TheyreGreat!!! is not found.

However if you want to test your password but don't not want to store the command in history, put a single space at the beginning: " python pwned.py ..."

However if you want to test your password but don't not  want to store the command in history, put a single space at the  beginning: " python pwned.py ..."

That’s not guaranteed to work and depends on shell’s configuration. Specifically, bash requires ignorespace being present in HISTCONTROL environment variable.

The new merge allows you to redirect stdin, or enter commands within the script itself - hopefully this works for you.


Can't trigger audio/video .play on swipe

Use-case
Play a video when the user swipes to it
Example Code
Swipe(document.getElementById('slider'), {
  callback: (i, el) => {
    const video = el.querySelector('video')
    if (video) { video.play() }
  }
});

Problem
Some browsers, notably Mobile Safari, throw a NotAllowedError if a script tries to call video.play() (or audio.play()) in a context that is not directly tied to a user action.
See Safari HTML5 Audio and Video Guide > iOS-Specific Considerations
Cause
I believe the problem is that swipe-js wraps callback in a setTimeout(callback, 0), which breaks the connection to the original event handling. This causes the browser to believe callback (and thus play()) is not called because of a user action.

I tried changing
var offloadFn = function(fn) {
  setTimeout(fn || noop, 0);
}; // offload a functions execution

to
var offloadFn = function(fn) {
  (fn || noop)();
}; // offload a functions execution

locally to test this. The NotAllowedError remains. I reject my previous hypothesis.
My new hypothesis is that a touchend event cannot trigger play() on these devices.


Receive share file from another app

I'm looking for a two way sharing process.

First, share from our app to others (or even social sharing) - which this plugin does very well :)
Second, receive from another app some share file

Is there any plugin to receive the shared file by using this plugin?

Hi
@EddyVerbruggen @genuinefafa @marcsyp I'm currently working on this (we are building a "mobile clipper")
https://github.com/stample/cordova-sharingreceptor
However I must admit it is my first cordova plugin, and I'm not an iOS developer, and I have a really hard time... any help is welcome :) Even a iOS > 8 solution would be nice.
I've tried to add things to CFBundleDocumentTypes but it did not really do what I want.
See also: http://stackoverflow.com/questions/33105698/sharing-safari-browser-url-to-my-ios-app
As far as I understand, I have to do a  "share extension" (iOS > 8) right?

Hi,
I've finally been able to create a clipper.
For Android it is much simpler as a it only requires a Cordova plugin. (I made my own and you should probably do your own too as it requires to customize it to your needs).
For iOS it is much complicated and I've documented it there:
http://stackoverflow.com/questions/26436544/share-image-using-share-extension-in-ios8


[Bug] Jamendo audio_set->url contains track ID in query params

Description

Consider a sample url inside the audio_set JSON field:
https://usercontent.jamendo.com?type=album&id=110159&width=200&trackid=938327

The trackid query param (which is not an attribute of the album) causes the album to appear several times in the data and interferes with the DISTINCT constraint imposed on the SQL.
The trackid param should be cleaned out of this field.
Expectation

The data in the audio_set field should solely be related to the audio set. Extraneous data can affect the ability to uniquely filter out audio tracks from the data.
Screenshots

Resolution

[ ] 🙋 I would be interested in resolving this bug.

There is a mixup in the field naming. The actual URL that should be distinct is foreign_landing_url in the table on the screenshot. The url field actually has a URL of the set thumbnail (!), so there is probably no need in removing it. There is a field mixup in the AudioStore, and here is the data that is currently being written for audio_set:
{
  'title': 'Opera I',
  'foreign_landing_url': 'https://www.jamendo.com/album/119/opera-i',
  'url': 'https://usercontent.jamendo.com?type=album&id=119&width=200&trackid=730',
  'creator': 'Haeresis',
  'creator_url': 'https://www.jamendo.com/artist/92/haeresis',
  'foreign_identifier': '119'
}

Could you please confirm, @dhruvkb , if this is the naming that API expects (foreign_landing_url -> url, url -> thumbnail):
{
  'title': 'Opera I',
  'url': 'https://www.jamendo.com/album/119/opera-i',
  'thumbnail': 'https://usercontent.jamendo.com?type=album&id=119&width=200&trackid=730',
  'creator': 'Haeresis',
  'creator_url': 'https://www.jamendo.com/artist/92/haeresis',
  'foreign_identifier': '119'
}


Problem with closing panel during internal scroll view bounce

Short description
When closing the panel, if scroll view is still in the process of bouncing, there will be a visual bug. At least for me, it's quite usual to make a quick scroll to the top, which causes bounce, and then try to close the panel.
Expected behavior
Smooth transition.
Actual behavior
Glitching. See the video.
video.mov.zip
Steps to reproduce
Call the top vertical bounce of scroll view and try to close panel at the moment.
Code example that reproduces the issue
TestingNewPullUp.zip
Library version
1.6.0
Installation method
CocoaPods
iOS version(s)
12.2
Xcode version
10.2.1

Thanks, @Heltisace! At first, I'm grateful for your video and sample project for this issue because they're much helpful and save my time. Now I've confirmed this issue using them. I will fix this issue later.

This issue is resolved in the master branch. It will be released on v1.6.x or 1.7.0. Thank you.

I have 2 notices to you about TestingNewPullUp sample.

I found not calling ChildFloatingPanelController.supportedPositions expectedly by the Swift issue SR-103. You need to add AnyFloatingPanelController.supportedPositions and override it in ChildFloatingPanelController.

I guess .hidden support position is not working well as you expected on iPhone X series. The issue is mentioned in https://github.com/SCENEE/FloatingPanel/issues/175.  I'm working now to fix it.

Ok, thanks. Glad I could help :)


Embedding and Storage in Vector Database

Develop logic to create embeddings for file content.
Store vector embeddings and metadata in the local storage system (or vector database).
Write tests to ensure proper storage and retrieval of embeddings.

take


why tags is empty

$ hexo new page "tags"

get a empty page.
but I have a tag!!

edit the generated .md file, set the type to tags or categories.

Means your source/tags/index.md should look like this


delayed_action is not documented

This functionality is extremely useful for guaranteeing execution at the very end of the Chef client run when there's nothing that should trigger this with a :notifies, but it's absent from all documentation.
https://www.rubydoc.info/gems/chef/Chef/Resource:delayed_action

I can't believe this is 1 year old already.


[openocd,opentitanlib] Add earlgrey chip tapID

The earlgrey chip has the TapID in this file and fixes errors in init.

Looks like you need to sign off your commit to pass CI
git commit --amend -s
git push -f origin add_silicon_cfg

This looks good to me although I agree with @engdoreis that if possible, we should factor what the common part in another file that gets included.

CI seems to be unhappy about untrimmed whitespace:
Fixing file: "util/openocd/target/lowrisc-earlgrey-silicon.cfg"
##[error]Whitespace check failed. Please run util/fix_trailing_whitespace.py on the above files.


closes #152 Bubble Up Unit Tests

Hey Hugo. Thank you for the great test. I am really happy with this.


Add ruby24 and trunk to appveyor?

I've added 2.4 & trunk to appveyor.  tests are here, updated file is here.

Would you like a PR?
2.4 only, or 2.4 & trunk (can also add trunk as an allowable failure)?

FYI, appveyor has been asked to update ruby24 to 2.4.2.

Please create a PR, this sounds great!
For trunk, I see you use your own build. Will it be often updated?
The problem with ruby trunk on Travis CI is it often gets outdated and therefore starts failing, making it mostly useless.
My only concern is it takes longer for CI but macOS on Travis is so slow nowadays that it probably does not matter much.

@eregon

For trunk, I see you use your own build. Will it be often updated?

I call it my 'breakfast build'.  Short of a catastrophic failure/error, I update it daily.  Its come far enough along that I'm thinking of moving the build to appveyor, but I'm trying to see if I can set it up so one can use it for both local builds (using a git repo) and appveyor builds.
FYI, when I build, I run both make test-spec and ..\mspec\bin\mspec -rdevkit.
This morning, make test-spec had two fails in WIN32OLE that I've never seen before, but mspec did not.  I'll check further, and based on that, push the appveyor.yml update later.
Thanks again.

@eregon
I haven't had time to look at it, but I just squashed commits and re-ran tests in my fork.  The build this morning passed mspec
3551 files, 26041 examples, 202825 expectations, 0 failures, 0 errors, 0 tagged

But the recent fork build results showed
3548 files, 25984 examples, 202966 expectations, 6 failures, 0 errors, 0 tagged

Again, I haven't looked further...

This repo and MRI's copy in spec/ruby are only sync'd about once per month, so it's expected there are a few differences.
I think this can be closed since #468 is merged.

Benoit, thanks for all your work.

This repo and MRI's copy in spec/ruby are only sync'd about once per month

Am I correct that, at present, changes are generally pushed from trunk to here?  Exceptions for PR's here, etc.
If you know (without taking any time to check), any idea what causes the difference in 2.4 and trunk numbers?
2.4   - 3554 files, 26019 examples, 203409 expectations, 0 failures, 0 errors, 0 tagged
trunk - 3554 files, 25996 examples, 202980 expectations, 6 failures, 0 errors, 0 tagged

Call me AR, but I've always been bothered by test stats like this, since they don't give any info about
why there are differences in examples and expectations.  Same issue with the ruby test-all suite...
Greg

Am I correct that, at present, changes are generally pushed from trunk to here? Exceptions for PR's here, etc.

It's really mixed, there are PRs here but also changes from MRI, TruffleRuby and JRuby which each have a copy of this repo and synchronized about once a month here.

Call me AR

What does "AR" mean? I don't know that abbreviation.
Some examples (it blocks) are only valid on executed versions due to the ruby_version_is guard, so it's expected to have different numbers for 2.4 and trunk.
Just after a synchronization, numbers with make test-spec and run directly against trunk should be identical, I'll check next time. But in between changes in MRI or here can change the numbers of course.
The last 3 numbers are the more useful ones, and examples to get a decent approximation of how much of ruby/spec is run and pass on other implementations.

What does "AR" mean? I don't know that abbreviation.

Sorry, wasn't sure how common that was.  I previously was involved with 'high-reliability' system design.
—often used in nontechnical contexts to describe someone as extremely or excessively neat, careful, or precise
a*al-retentive
Thanks for the explanation re stats.  Re MRI, I've got results of trunk spec tests here.  GitHub.io / GitHub Pages is a little slow today, I've got 22-Sept updates that aren't appearing yet...

@eregon

For trunk, I see you use your own build. Will it be often updated?

The build is now a rolling build (every 12 hours) on Appveyor.
I looked over the CAPI files, and (with my limited c knowledge) it seemed that it was all core.  The build uses an updated OpenSSL library (1.1.0f) and a ruby specific GDBM package.  Since the CAPI files don't seem to link to any of that, the packages probably aren't required?
Also, current Appveyor environment uses GCC 6.30, but 7.2.0 is available.  At present, anyone installing MSYS2 will have gcc 7.2.0 without additional work.  FYI, MSYS2 is required for building extension gems when using ruby 2.4 + on windows.   It is included in the standard installation app.
I've got a script included with the build that updates to 7.2.0, yesterday it took 1:10 to run.
Questions:

Should I update appveyor.yml to use the rolling build?
Run the 7.2.0 script, or stay with standard Appveyor environment?

I juts ran the update (with gcc 7.2.0) on my fork, trunk results are the same as the last commit.  2.3 and 2.4 pass as before.
Thanks,
Greg

Yes, C API tests only tests C functions built-in to Ruby, not defined in stdlib C extensions.
Do as is easiest for you.
I'm happy to test with what you build for your own usage :)


Addition of popular Telegram channels

-- Please reply above this line --
Hello Bulutyazilim/awesome-Datascience,
Thank you for your email! Someone from our team will get back to you
as soon as we are back at the office. Our office hours are 9 am to 5
pm ET US.
Thank you!
Lillian Pierson & Team


How can someone use this on NixOS without Flakes

The README.md quotes "In your configuration.nix file", but does not mention how to make comin available in the configuration.nix file.
As a NixOS user, how can I use comin with and without flakes ?

You need flakes, given the entire evaluation section of the code relies on these:

https://github.com/nlewo/comin/blob/4eb600b96ddecca708cea9514ac56d3e6ee208a7/internal/nix/nix.go#L48-L61

Separate to comin - I do not believe there's a way to build a NixOS system configuration without flakes either.

The README.md quotes "In your configuration.nix file", but does not mention how to make comin available in the configuration.nix file.

Since comin in not yet in nixpkgs and doesn't provide a default.nix file, you need flakes to use it in your configuration.
Also, as said by @jpds, comin is only able to deploy NixOS machines from flakes and I don't plan to support something else atm.
(BTW, maybe this should be more explicit in the readme.)

As a NixOS user, how can I use comin with and without flakes ?

Without flakes, most of the functionality is covered by the built-in: services.self-deploy.
Perhaps this could be part of the readme update?


Version 6.3.0 - Windows - Cluster and Node views with missing Prometheus data

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Having the previous release 6.2.6 with "@kubescape/lens-extension", "lens-certificate-info", "lens-extension-network-policy-viewer" extensions
Update to 6.3.0 and open (Print 1)
Downgrade to 6.2.5 and reinstall 6.3.0 shows but with failed Prometheus metrics in the cluster view and *only memory for nodes view (Print 2 and 3)

Expected behavior
Only update without a black dashboard
Screenshots
Print 1

Print 2

Print 3

Environment (please complete the following information):

Lens Version: 6.3.0
OS: Windows 10 Enterprise
Installation method: from .exe installer

Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:
Your logs go here...

Kubeconfig:
Quite often the problems are caused by malformed kubeconfig which the application tries to load. Please share your kubeconfig, remember to remove any secret and sensitive information.
the kubeconfig didn´t have changes so I think is not necessary
Additional context

same as https://github.com/lensapp/lens/issues/6820
ctrl + r will reload and some things are showed but other problems are present

same as #6820 ctrl + r will reload and some things are showed but other problems are present

After a downgrade and reinstall 6.3.0 the dashboard back to shows something but now the Prometheus metrics from nodes are not processing right.

Thanks for reporting this, we just added it to the next patch milestone and will start looking into it!

not sure if related or a separate issue, but after refreshing to see the page, it seems the view logs option is no longer present for pods etc.

I can't install Prometheus metrics on a new cluster. The extension is missing. I also have to force reload the window after startup, because I get a blank window.

I'm testing 6.4.0-alpha.4 on Windows 10 and it was better.
The first started after installing the 6.4.0-alpha.4 over the 6.2.6, some columns (CPU, DISK) and the same metrics in the right Pod modal were missing, but after some minutes late, the metrics appeared.


Windows binary runtime error

Is there an existing issue for this?

[X] I have searched the existing issues

I'm submitting a ...

[X] bug report
[ ] feature request
[ ] support request --> Contact me over mail for support https://github.com/MShawon

Description
After downloading latest release and running it I get:

PS C:\Users\marci\OneDrive\Pictures\Desktop\YT> C:\Users\marci\OneDrive\Pictures\Desktop\YT\youtube_viewer.exe

Yb  dP  dP"Yb  88   88 888888 88   88 88""Yb 888888
 YbdP  dP   Yb 88   88   88   88   88 88__dP 88__
  8P   Yb   dP Y8   8P   88   Y8   8P 88""Yb 88""
 dP     YbodP  `YbodP'   88   `YbodP' 88oodP 888888

                        Yb    dP 88 888888 Yb        dP 888888 88""Yb
                         Yb  dP  88 88__    Yb  db  dP  88__   88__dP
                          YbdP   88 88""     YbdPYbdP   88""   88"Yb
                           YP    88 888888    YP  YP    888888 88  Yb

           [ GitHub : https://github.com/MShawon/YouTube-Viewer ]

+-------------------------- Version: 1.8.0 --------------------------+

Getting Chrome Driver...
Traceback (most recent call last):
  File "youtube_viewer.py", line 1003, in <module>
  File "youtubeviewer\download_driver.py", line 112, in download_driver
  File "undetected_chromedriver\_compat.py", line 262, in install
  File "undetected_chromedriver\_compat.py", line 192, in install
  File "undetected_chromedriver\_compat.py", line 221, in fetch_chromedriver
  File "undetected_chromedriver\_compat.py", line 211, in get_release_version_number
  File "urllib\request.py", line 214, in urlopen
  File "urllib\request.py", line 523, in open
  File "urllib\request.py", line 632, in http_response
  File "urllib\request.py", line 561, in error
  File "urllib\request.py", line 494, in _call_chain
  File "urllib\request.py", line 641, in http_error_default
urllib.error.HTTPError: HTTP Error 404: Not Found
[67500] Failed to execute script 'youtube_viewer' due to unhandled exception!

Environment
- OS : W11
- Python : EXE without Python
- Script version : 127.0.6533.89

config.json
Do not have that file in directory where exes are.

Check this one: https://github.com/akumathedyn123/js-yt-view-bot


Add basic 2D layer_norm operator

Needed for nomic-ai/nomic-embed-text-v1.5.
Example usage:
import { pipeline, layer_norm } from '@xenova/transformers';

// Create a feature extraction pipeline
const extractor = await pipeline('feature-extraction', 'nomic-ai/nomic-embed-text-v1.5', {
    quantized: false, // Comment out this line to use the quantized version
});

// Compute sentence embeddings
const texts = ['search_query: What is TSNE?', 'search_query: Who is Laurens van der Maaten?'];
let embeddings = await extractor(texts, { pooling: 'mean' });

const matryoshka_dim = 512;
embeddings = layer_norm(embeddings, [embeddings.dims[1]])
    .slice(null, [0, matryoshka_dim])
    .normalize(2, -1);
console.log(embeddings.tolist());
// [
//   [-0.00518727907910943,   0.06514579057693481,  -0.21559129655361176, ...],
//   [-0.008253306150436401,  0.005108598619699478,   -0.22179779410362244, ...],
// ]

Relevant discussion: https://huggingface.co/nomic-ai/nomic-embed-text-v1.5/discussions/4#65cce8d0c52afc14ceac26c2

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


basic doubt

sir, can you please let me know, why have you use backward compatible code also in the implementation.
I am talking about the class defined below..
@staticmethod
def backward(ctx, grad_output):
assert grad_output.is_cuda
    .........

The forward of DDF is implemented in CUDA, the autograd is not suitable for this case. So, I also implement the backward function.

sir, can you please explain the concept of the relation between dynamic filters and attention as shown in Figure 3 of your paper.
How can we relate applying dynamic concept (where every filter is applied to each pixel) with attention


K8SPXC-355 Swap day/month in S3 backup date format

S3 backup folder names were getting generated with YYYY-DD-MM date format. Change to use conventional YYYY-MM-DD order.

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

Test name
Status

recreate
passed

big-data
failed

storage
passed

init-deploy
passed

scaling
passed

self-healing
passed

scaling-proxysql
passed

limits
passed

upgrade
passed

monitoring
passed

restore-to-encrypted-cluster
failed

self-healing-advanced
failed

demand-backup
failed

upgrade-consistency
passed

monitoring-2-0
passed

security-context
passed

scheduled-backup
failed

operator-self-healing
passed

affinity
passed

one-pod
passed

demand-backup-encrypted-with-tls
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

Test name
Status

big-data
failed

init-deploy
passed

limits
passed

scaling
passed

monitoring
passed

scaling-proxysql
passed

monitoring-2-0
passed

upgrade
passed

affinity
passed

upgrade-consistency
passed

one-pod
passed

security-context
passed

recreate
passed

auto-tuning
passed

restore-to-encrypted-cluster
passed

proxysql-sidecar-res-limits
passed

storage
passed

self-healing
passed

self-healing-advanced
failed

operator-self-healing
passed

demand-backup
passed

scheduled-backup
failed

demand-backup-encrypted-with-tls
passed

Test name
Status

scaling
passed

big-data
failed

scaling-proxysql
passed

recreate
passed

upgrade
passed

restore-to-encrypted-cluster
passed

upgrade-consistency
passed

demand-backup
passed

security-context
passed

scheduled-backup
failed

storage
passed

self-healing
passed

self-healing-advanced
failed

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

demand-backup-encrypted-with-tls
passed

operator-self-healing
passed

Test name
Status

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

storage
passed

scheduled-backup
failed

self-healing
passed

big-data
failed

self-healing-advanced
failed

scaling
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

init-deploy
passed

security-context
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

operator-self-healing
passed

demand-backup-encrypted-with-tls
passed

Test name
Status

storage
passed

self-healing
passed

scaling
passed

self-healing-advanced
failed

scaling-proxysql
passed

upgrade
passed

init-deploy
passed

upgrade-consistency
passed

limits
passed

security-context
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

big-data
failed

proxysql-sidecar-res-limits
passed

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

scheduled-backup
failed

operator-self-healing
passed

demand-backup-encrypted-with-tls
passed

Test name
Status

storage
passed

self-healing
passed

self-healing-advanced
failed

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

scheduled-backup
failed

big-data
failed

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

scaling
passed

proxysql-sidecar-res-limits
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
passed

demand-backup-encrypted-with-tls
passed

operator-self-healing
passed


Error on play: "Object reference not set to an instance of an object"

Getting this error in Unity 2022.3.9:
NullReferenceException: Object reference not set to an instance of an object
GaussianSplatRenderer.OnPreCullCamera (UnityEngine.Camera cam) (at Assets/GaussianSplatting/Scripts/GaussianSplatRenderer.cs:345)
UnityEngine.Camera.FireOnPreCull (UnityEngine.Camera cam) (at <10871f9e312b442cb78b9b97db88fdcb>:0)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr, Boolean&)
I'm using a pointcloud.ply from NerfStudio with the transforms.json renamed to the expected "cameras.json"
Not sure where I went wrong, but any guidance would be much appreciated!

I have the same issue. The content of my json file looks very different from your camera.json. Is there a practical way to match the content?

@matthewrbrennan my guess is that there was some other error before that, that causes the later nullref exception. Anything else in the previous console error messages?
@carlosnavarro-cn I only made it support cameras.json files as I found them among the Gaussian Splatting paper data files. If you have something that is different format, and you'd like it to be supported by this, then feel free to either send a pull request, or at least show how your file looks like.

@aras-p So there was! It jumped so quickly to "999+ errors" I didn't think to scroll all the way to the first one, which was this:
Exception: InputVertex size mismatch, we expect 248 file has 27
GaussianSplatRenderer.LoadPLYSplatFile (System.String folder, System.Boolean use30k) (at Assets/GaussianSplatting/Scripts/GaussianSplatRenderer.cs:169)
GaussianSplatRenderer.OnEnable () (at Assets/GaussianSplatting/Scripts/GaussianSplatRenderer.cs:257)
Thanks Aras!

@matthewrbrennan "Exception: InputVertex size mismatch, we expect 248 file has 27" would mean the file is not a PLY file containing Gaussian Splats, but rather a file containing something else (perhaps just a sparse point cloud?)

@aras-p OK - so that means simply exporting a PLY pointcloud from Nerfstudio won't work - guess I've got to do some more reading up. Thanks!

@carlosnavarro-cn I only made it support cameras.json files as I found them among the Gaussian Splatting paper data files. If you have something that is different format, and you'd like it to be supported by this, then feel free to either send a pull request, or at least show how your file looks like.

Thank you, Aras! I realized I couldn't just use a NeRF transforms.json, but needed to train a Gaussian Splatting scene to get the proper camera.json. I got it working now!


[FancyZones] Nothing happens at all

Environment
Windows build number: Build 1909 [Version 10.0.18363.836]
PowerToys version: v0.18.0
PowerToy module for which you are reporting the bug (if applicable): FancyZones

Steps to reproduce
Open FancyZones and attempt to use any configuration
Expected behavior
Windows open to fall in line
Actual behavior
Literally nothing happens
Screenshots
Not applicable

You need to drag them via Shift+HoldLeftClick in their windows first.
Did you do that?
This is the first option in fancyZones settings as well.,

Ah ok. That did it. Thanks 👍


CLEANUP: Remove an unnecessary ESLint rules from eslint-config-expensify

Because we changed the style guideline to use object de-structuring to assign default values, `rulesdir/onyx-props-must-have-default': 'error' is no longer relevant. Remove the rule.

@spcheema unfortunately it's not but thank you for your interest

will do after TS migration is over

melvin, TS migration is still going

melvin, TS migration is still going

TS migration is still going

TS migration is nearing end

TS migration is nearing end

TS migration is nearing end

changing this issue to weekly as the TS migration finishes in the App repo! 🚀

Hey! I’m Błażej Kustra from Software Mansion, an expert agency, and I’d like to work on this issue!

Because we changed the style guideline to use object de-structuring to assign default values, `rulesdir/onyx-props-must-have-default': 'error' is no longer relevant. Remove the rule.

@hayata-suenaga Let me know if there are any other rules that we need to remove, or maybe I should remove/adjust all rules conflicting with NewDot configuration?

@blazejkustra some ESLint rules need to be removed from the Expensify ESlint, so I'll handle this 😄 🙇

Removing onyx-props-must-have-default -> https://github.com/Expensify/eslint-config-expensify/pull/92

@blazejkustra some ESLint rules need to be removed from the Expensify ESlint, so I'll handle this 😄 🙇

Absolutely, all yours 😄 Let me know if there is anything I could help!

The two PRs were merge and deployed. I don't know why Melvin didn't remove the reviewing label. Closing the issue now 😄


bugfix do not reset shapetracker of 0 size lazybuffer

it might be coming from an expand, and resetting st results incorrect stride. caught by interpreted backend
fixes #3094

will also check other places that ShapeTracker.from_shape are used but might not be contiguous


Expose sign and verify methods

I needed a way to easily generate/verify the webhook signature for some proper integration tests in @probot. This exposes a sign and verify method on the webhook handler that can be used to generate and verify the signatures for the given webhook secret.
Usage:
const createHandler = require('github-webhook-handler')
const handler = createHandler({ path: '/webhook', secret: 'myhashsecret' })

const sig = handler.sign({foo: 'bar'})
handler.verify(sign, {foo: 'bar'})

Updated tests to use .sign, and added tests for sign+verify.