Correct grammar for DE accessibility statement

This PR changes the "Bundesministerium" into genitive case in marked up in green in the following screenshot:

This affects:

https://www.coronawarn.app/de/accessibility/
https://www.coronawarn.app/de/accessibility/#android
https://www.coronawarn.app/de/accessibility/#ios

Thanks for advice from @Ein-Tim for this change.

@Ein-Tim @MikeMcC399 Thanks a lot! Enjoy the weekend!


feat(webpack): write files to support webpack builds

This PR adds a webpack writer to support use of closure-webpack-plugin in OpenSphere builds.
The writer creates two files:

JSON options object to pass to the webpack compiler plugin. All options handled internally by the webpack plugin are removed from the original GCC options generated by the resolver.
An index.js file to use as the webpack entry. This file has goog.require statements for each entry_point from the GCC options.

Tests were added for the new webpack writer and the existing JSON writer.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Basics of Visual Design : Part 3

Description 📜
Check #1313  and maintain the same folder order . In this try to discuss how to create effective color palettes for your own designs. Deep dive into talking about methods for creating your own color schemes, from scratch.

Domain of Contribution 📊

[ ] Android Dev (Flutter, Java, Kotlin)
[ ] Backend Dev (Java, .NET, Python)
[ ] C/CPP
[ ] Competitive Programming
[ ] Cyber Security
[ ] DSA
[ ] Database
[ ] Datascience with Python
[ ] Datascience with R
[ ] Frontend Dev (HTML, CSS, JS)
[ ] Frontend Dev (React, Angular, Vue)
[ ] Golang
[ ] Interview Prep
[ ] Java
[ ] JavaScript
[ ] MERN
[ ] Machine Learning
[ ] Open Source
[ ] Python
[ ] Rust
[ ] Statistics
[x] UI/UX

I want to work on this. Can you assign it to me?

Hey, I want to work on this issue. Can you assign this to me @Debasmita-01 ?
Thank you.

Hey! I want to work on this. Can you assign the issue to me? @Debasmita-01


Modify pins for ESP-01M remote

Hello, I have this ir remote

How do I change the pin to these?
transmitter - gpio04
receiver - gpio14

Can't change pin,
Download gerber,make PCB,soldering.
https://github.com/LouisLee985/Homekit-Air-Conditioner-Remote/tree/main/hardware#ac_ir_homekit_usb_type_a


Add devise

Implemented features

Remove current_user method
Install devise
Style devise views
mailer set to :file method and sent mails can be found at /tmp/mail/[email]
Require authentication for all routes

thanks for the suggestion, already implemented


Slow network will hang online TM autocompletion, and finally hang the whole program.

It seems that TM operations will hang the POedit program for a while. This is OK for local TM since it won't take long, but for online TM fetching it's quite easy to notice.

It appears that POedit is requesting those translation one by one, making the speed even slower. Is something like a bulk API available from MyMemory?

It seems that TM operations will hang the Poedit program for a while.

No, sorry, this is just not true at all. Please don't try to (wrongly) diagnose the cause of whatever it is that you're seeing and instead describe the problem in some reasonable amount of detail. Please describe what you do, how you do it, exactly and step by step, including providing any necessary files to reproduce it and information about your Poedit version, and of course the observed behavior.
It's also not clear what "slow network" means here — low bandwidth, high latency, unreliability, some combination of those or all of the above? Nor for that matter what "hang the whole program" does.
I know for a fact that pressing e.g. Ctrl+1 (my best guess as to what could you mean by "autocompletion") couldn't possible "hang" the app, so you probably meant something else. The problem is, you didn't explicitly say what...

It appears that POedit is requesting those translation one by one

Given that you are translating things one by one, you of course need the suggestions (not final "translations"!) one by one as well…

I am talking about Catalog -> FIll missing translations from TM.

Slow Network means a network that takes ~1.5s to see each translation filled with the online TM.

Slow Network means a network that takes ~1.5s to see each translation filled with the online TM.

That's the observed effect the network is having on Poedit (although I'm not quite sure how could you have measure that in Fill Missing… where individual entries handling isn't directly visible). I was hoping, since you filed an issue in the devel bug tracker, to get a technical characteristics of said network. That would be very useful in reproducing the problem and improving the code; "it's slow" is unfortunately a bit less so.

I am talking about Catalog -> Fill missing translations from TM.

Ah, I see, that wasn't apparent to me. Yes, that code is problematic, please notice how it is marked as experimental in the UI. Indeed, the lack of bulk API (or any support for such use) is part of that. The suggestions aren't really meant for any bulk use, this functionality is intended strictly for the "offline commuter" use case.


ibus: $GDK_PIXBUF_MODULE_FILE can only be one file

Issue description
ibus-setup crashes on startup
ibus-daemon crashes on shortcut
(ibus-setup:2305): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/nix/store/a75mhbbh6j97q5gkqzyr6rbq2d5slhgj-librsvg-2.40.9/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache:/nix/store/a75mhbbh6j97q5gkqzyr6rbq2d5slhgj-librsvg-2.40.9/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

The problem is this line in the wrapper
export GDK_PIXBUF_MODULE_FILE=/nix/store/a75mhbbh6j97q5gkqzyr6rbq2d5slhgj-librsvg-2.40.9/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache${GDK_PIXBUF_MODULE_FILE:+:}$GDK_PIXBUF_MODULE_FILE

GDK_PIXBUF_MODULE_FILE can only be one file. Not multiple files. This is because it is meant as a write to location. https://developer.gnome.org/gdk-pixbuf/unstable/gdk-pixbuf-query-loaders.html
I tested it, and it works perfectly if there is only one file. In my current system, the wrapper makes GDK_PIXBUF_MODULE_FILE contain two times the same file anyway.
nixos https://nixos.org/channels/nixos-unstable

Ok so replacing maybe the wrong solution, but it's still an issue that GDK_PIXBUF_MODULE_FILE can only be one file. How about using --set instead of --prefix? I pushed over the branch, but I don't think I can reopen the pull request.


Slow Down Typing

When sending keystrokes to some web-based remote management apps, the default 5ms delay per keystroke in AutoIt overruns the buffer and the pasted text is corrupted.
It'd be great to have a configurable per keystroke delay to slow down typing for my use case.
https://documentation.help/AutoItX/AutoItSetOption.htm#SendKeyDelay

Great idea

Just logged in to mention this is an issue for me as well. A missed keystroke can be pretty frustrating at times. A configurable typing speed would be great.

To anyone watching the issue: is it a problem for SendKeys mode, or only in AutoIt_Send?

Added in v1.0.1


feat(datepicker): allow to only display days of selected month

Problem
Days that don't belong to the selected month could confuse people. There is no option to handle this issue.
Solution
Add another config attribute that allows us to handle this. Per default it is set to false so basically nothing changes until someone explicitly set it to true
daysOfMonthOnly: false (default)

daysOfMonthOnly: true

Comments

Not sure if daysOfMonthOnly is really a good name for that property. Any other suggestions?
Instead of using ng-if we could just apply a certain css class like dayInMonth to the button so people can use CSS to handle this use case.

Possible improvements
If show weeks is set to true it can happen that all buttons in a row get disabled and the row is a bit short in height. There is definitely a better way to handle this:

But I first wanted to know if you guys think that this patch is worth adding or maybe there is already a different approach of achieving this.

I'm not sure how I feel about this feature - this is not standard behavior for datepickers, and so I'm not sure how confusing this actually is for users. This also adds performance overhead on the ng-if.

@wesleycho thanks for the quick response. Don't know if there is something like a standard behaviour for datepicker, however I found couple examples where it is exactly like this:
jQueryUI: https://jqueryui.com/datepicker/
datepickr: https://code.google.com/p/datepickr/
Mootools: http://aryweb.nl/projects/mootools-datepicker/Test/ (kinda)
Dojo Bootstrap: http://xsokev.github.io/Dojo-Bootstrap/datepicker.html (kinda too)
All these examples have at least the possibility to disable these days using CSS:

How about we are going the CSS solution I was mentioning above: adding a certain css class to the button tag for days that don't belong to the selected month, e.g.:

Sorry for taking a long time to get back to you.
CSS solution may be possible, but if you do attempt it, performance is something you would have to be careful about.
I'm going to close this PR for now since master changed quite a lot in the past half year, especially the datepicker. Feel free to reopen a PR implementing this again with tests.


A lot of players ID become:4074100

such as:74100,5000055007000，40704100

Closing this issue due to no response.


"This view does not mark messages as read" banner should appear immediately

Reported on CZO
Reproducer:

Go to a view with few messages, e.g. a topic with one message in it.
Mark the message as unread (via keyboard or mouse).

Expected: "This view does not mark messages as read" banner should appear immediately.
Actual: Banner appears only once the window is scrolled.

@zulipbot claim

@beingnoble03 - Thanks for your interest in working on this. But as this an urgent issue for the upcoming 6.0 release, I've got a pull request in the works to address it, and you should find another issue to work on.

@laurynmm Ok. Fine!

@laurynmm Can you please remove the help wanted tag for this issue?

The "help wanted" label can stay, but I assigned the issue to @laurynmm to avoid confusion.


I am sure it MUST be:
$ npm run dev
$ npm run prod

But only if you want to increase the learning curve, you could leave it like now.

I've seen countless projects that use build to actually "build" a the project, so yes, we are serious. :)

Sidenote: did a short search on Github:

"npm run prod" : 7k results.
"npm run build": 403k results.

What if I want to build dev version of a project?
Or dev version is not building, but constructing or scaffolding?

WordPress - About 1,710,000,000 results
Laravel - About 13,300,000 results
Does it mean I should learn WordPress, instead of Laravel? @LinusBorg

piterden 4500
linusborg 15900
You rock, man!!! :+1:

Can I ask why you are so upset about the name of a command?

Because the code is manipulation of names. What, besides the names, contains your code?

Okay, I'll bite since I have some time to kill.

Because the code is manipulation of names. What, besides the names, contains your code?

I'm not entirely sure I understand what you mean - In case you mean "names in programming are important, it's what transports the meaning of the code we write", I completely agree. But these things are often subjective, and they can and should be discussed constructively.
 I'm sure it MUST be: ...." basically suggest that we did something obviously stupid, which is not the best way to start a productive conversation with anyone.
My reply to this was meant to show you that using npm run build is very, very common in javascript projects, so it can't be something obviously stupid, but rather something very common, so we can assume that most people familiar with javascript projects already have a good intuition about what it does.
People who are not familiar with npm commands can read the templates documentation to learn quick and clearly about what each command does - that provides a better learning curve than any command name could on it's own, I think.

What if I want to build dev version of a project?
Or dev version is not building, but constructing or scaffolding?

Well, of course we can have a constructive discussio about which name is probably more or less meaningful to someone at face value. But then we quickly end up in endless bikeshedding.
Example
Your proposal was to change it to npm run prod - But since npm run dev runs a dev-server, would the user not assume that this also runs a server, but in prouction mode?
So we could rename both commands:
npm run start-dev-server`` npm run build-for-production`
That's more meaningfull, right? that's communicating very clearly what each command does.
But now people will complain about these commands being much too long to type them over and over. See where it goes?
The Point
So, don't get me wrong: Command names can be discussed and optimized, for sure. Vbut that should be done in a civil manner and with a better argument than "I am sure it MUST be:".
The current commands are commonly used commands in the npm ecosystem and are also well documented, so I don't see that Your initial PR had much of an argument.

Please excuse my rudeness.
Unfortunately, I haven't so much time to kill, but I have one idea about it:
{
// ...
  "scripts": {
    // ...
    "prod": "npm run build",
    // ...
  },
// ...
}

It would make 410k for us...

Side note: now.sh uses npm run build to build your deployments.

But what if you have multiple environments such as staging?
You build for then environment, you don't prod for the environment. Also there is nothing stopping you from changing

You build for development, build for staging, or build for production, isn't it?

You don't build for development. You run the development server. There is no "building" action for dev environment, as opposed to all the rest of them.

I see webpack(webpackConfig, cb) inside build.js command (the only one action there)
Also, I see const compiler = webpack(webpackConfig) inside dev-server.js command, together with other commands.
Ah, dev-server can work with production webpack config if the environment would be production or testing.
Do you absolutely sure, I don't have build for development, @Frizi ?
May I ask you, what is build? I mean essentially...

The build command essentially produces compiled files in a dist folder, that you can then upload to a server.
The dev command doesn't produce any file and instead starts the webpack development server with development-specific features like watching files and hot-module-replacement.
This is all regardless of the value of NODE_ENV.

I see webpack(webpackConfig, cb) inside build.js command (the only one action there)

This is not an action, it just creates an instance of webpack.

The dev server process builds the files in memory, so as far as the developer is concerned? The result of this process is only accessible though the dev server.
The build process on the other hand actually produces a tangible output on the /dist folder.
So the result of the two are very different, not just the environment flag differs.
BTW we are now essentially bike's herding about the exact same things I mentioned in my "example" above... 😷

All the outcome in dev command happens to land inside webpack's memory-fs, and it's directly served from there via express server. Those files are unusable outside of this context, as those are very big. Usually those contain evaled modules and inlined sourcemaps. You should never use that server as your production environment.
That's why we have a build step, a de-facto standard used by many deployment solutions as your default app building hook. It just produces a bunch of ready to serve files. That doesn't mean that it has to run in production though, as you might have many different environments distinct from your main prod servers. All of those targets will use the same script, but having a different value inside NODE_ENV environment variable.
In case this pattern doesn't fit well into your project (because nothing is a silver bullet), you are free to adjust the files produced by the template as you please.

That makes sense for me. Thank you for explaining.
What about environments with non-JS backends? Can vue-cli be used for such of?

That's what you have build for again. It just produces a set of files to serve, you don't need JS on server side to deal with them, it's only required on your build machine. I'm commonly using nginx to serve those files later, but you are free to use whatever solution you prefer. Github pages works just as well 😉

piterden 4500 -> 19000
linusborg 15900 -> 16000
However, me too)) :wink:


feat: @nuxt/scripts announcement

🔗 Linked issue

❓ Type of change

[x] 📖 Documentation (updates to the documentation or readme)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
Announce https://github.com/nuxt/scripts, work in progress (expect issues).

Thanks @housseindjirdeh and thanks for the edits, I was planning to send you this once I had a chance to edit for these obvious mistakes :sweat_smile:
I'm also looking for high-level feedback on anything significant missing from the post (or anything that needs to be removed). From your end do you want TPC mentioned? If so can you give some pointers.

Thank you @kara and @flashdesignory for the feedback, your suggestions should be implemented but lmk if I missed something. I will open this PR up for wider comment.


--clap-X arguments

This proposal is to introduce automagically a family of arguments to scripts using clap. They would be used to support some of the new features at run time (instead of compile time).
For example:
  $ myscript --clap-manpage
```
would output the manpage. An installation script could just run this to generate and install it where it is appropriate.

In a similar way with TAB completion:
```
  $ myscript --clap-complete <text typed by the user before the tab was pressed>
```
would output a list of possible values separated by new lines. This would make the completion script much smaller and easier to port to other terminals as all logic is in clap and not in a shell script.

This clap arguments will be hidden by default (i.e. will not show up in the help)

I'm not a huge fan of adding flags/args to end user programs, hidden or not. But if enough people think it'd be useful, I'm not against adding a setting that builds these additional flags so long as it's not on by default.
My other thought is that this type of thing is doable in the end user code, so perhaps just some details examples or blog posts on how to do this would be more appropriate. Assuming we have all the infrastructure in place, a lo App::gen_completions, App::gen_manpage etc.

Thanks for being open even if at first sight does not sound right to you. What drove me to this is the need to support multiple terminals for completion in simple way. I dislike complicated shell scripts. Using what I have proposed the bash completion script will be:
_myscript_complete() {
  COMPREPLY=()
  local word="${COMP_WORDS[COMP_CWORD]}"
  local completions="$(myscript --clap-complete "$word")"
  COMPREPLY=( $(compgen -W "$completions" -- "$word") )
}

complete -f -F _myscript_complete myscript

Porting this to zsh is trivial:
_myscript_complete() {
  local word completions
  word="$1"
  completions="$(myscript --clap-complete "${word}")"
  reply=( "${(ps:\n:)completions}" )
}

compctl -f -K _myscript_complete myscript

Supporting other terminals (maybe even Windows PowerShell) should as easy to do. The trick is that the logic is in myscript keeping the shell script very minimal.

@hgrecco I think you can simplify that even further for bash; complete supports a -C option to specify a command to run, which generates completions on stdout (one per line, with backslashes to escape newlines if necessary).

@joshtriplett cool, thanks for the tip!


Notes on statistics

Awesome job @clifmckee !

[ ] lots of datasets used. I wonder if we could use one, and select columns depending on what we want?
[ ] The doctors and visits examples.. I wonder if we should use a different example, if the data aren't really normal distributions? Visits - binomial, and hours - gamma?

this seems like a nice resource: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2938757/


Integration Test - Release - 2020/09/26 00:10:26

Auto create for integration test. IssueCommandFlow

@PRMergerTest2 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Unnecessary browsing history collection, add option to opt out

What it says on the tin. See #152 .

Simply removed.
https://github.com/maripo/CustomFilter/commit/9f427d26b21828fde746c8418cc6a3ba2819acab
There are too many things to do to make it compatible with Manifest v3 to release it right away.


Introduce release workflow.

We adopt two Github Action to automate release for Mounpoint-S3

Github Action ID: taiki-e/create-gh-release-action for create Github Release. * During the release, operator must have consensus with team on version, draft, prefix and title as workflow inputs. * This workflow can also take changelog as inputs, we can opt in that once we have a change log format ready.
Github Action ID: taiki-e/upload-rust-binary-action for uploading Mountpoint-S3 binary and all other artifacts. * This workflow uploads compiled binary on target platforms. When we do the release, artifacts must includes: bin, LICENSE, archive and checksum.

TODO: create cross compilation for EC2 AARCH64
Description of change

Relevant issues:
Does this change impact existing behavior?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and I agree to the terms of the Developer Certificate of Origin (DCO).

per-release example: https://github.com/eslrahc-swa/mountpoint-s3/releases/tag/mountpoint-s3-0.0.1


⚠ Bofrost.lu has degraded performance

In 2ea0511, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1813 ms

Resolved: Bofrost.lu performance has improved in 95324fc after 59 minutes.


Issue: Aniyomi Randomly(sometimes consistently) freezes while watching anime.

Steps to reproduce
Simply Watch Pacific Rim Black on Gogoanime
Watch Pacific Rim on Sflix(inconsistent)
Expected behavior
It should play without issue
Actual behavior
After a few seconds the application simply freezes.
The issue seems random at first but it seems to happen consistently on 60fps videos.

Crash logs
aniyomi_crash_logs (2).txt
aniyomi_crash_logs (3).txt
aniyomi_crash_logs (1).txt
I have verbose logging turned on each log.
Aniyomi version
App version: <IP_ADDRESS>-7493 (standard, 89795945a, 121, 2024-01-31T13:51Z) Android version: 12 (SDK 32; build SQ3A.220705.004) Android build ID: SQ3A.220705.004 Device brand: samsung Device manufacturer: samsung Device name: a02q (a02qnaxx) Device model: Samsung Galaxy A02S WebView: Android System WebView 122.0.6261.15
Android version
Android 12
Device
Samsung Galaxy A02s
Other details
Device is rooted and Running on a GSI.
In addition i managed to capture one of these freezes on logcat
This issue seems to also occur when a priority notification pops up
Logcat:
logcat_02-05-2024_15-13-51.txt
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an official extension, I should be opening an issue in the extensions repository.
[X] If this is an issue with an official manga extension and this issue can be replicated in the Tachiyomi app, that I should be opening an issue in Tachiyomi's extensions repository.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

... please don't go stale

Duplicate of #1249


Increase _MaxGomaxprocs to support big machines

Please do not send pull requests to the golang/* repositories.
We do, however, take contributions gladly.
See https://golang.org/doc/contribute.html
Thanks!
Currently go does not support machines that contains > 256 CPUs, as IBM's E880
that could host 1536 hardware thread, when configured with 192 CPU cores and
SMT (Symmetric Multi Thread) 8.
For example, when running a go program on this machine, I got, the following
problem[1]:
procresize: invalid arg
This is because of the following code:
_MaxGomaxprocs = 1 << 8
if old < 0 || old > _MaxGomaxprocs || nprocs <= 0 || nprocs > _MaxGomaxprocs {
throw("procresize: invalid arg")
}
This patch just redefine _MAxGomaxprocs to 1 << 12.

See discussion on the bug too: #15131


Issue 4193 evalerror output

Fixes #4193
Changes proposed in this pull request:

The corresponding issue was already closed.


Upgrade of enmasse is broken

Describe the bug
Upgrade of enmasse is broken after merge of https://github.com/EnMasseProject/enmasse/pull/2056
To Reproduce
Steps to reproduce the behavior:

Deploy enmasse
create standard address space
upgrade enmasse

Expected behavior
All pods should be upgraded to new version
Additional context
upgrade checker log
[2018-11-30 02:20:09] [INFO]: All pods are up but all containers are not ready yet
[2018-11-30 02:20:15] [INFO]: Pod address-space-controller-7d7f6ddd64-5vnsr is upgraded to ****/enmasseproject/address-space-controller:jenkins-enmasse-master-2594
[2018-11-30 02:20:16] [INFO]: Pod admin.dg08eelq1n-6dcc6b5b6f-jfkxp is not upgraded, current image: docker.io/enmasseproject/standard-controller:0.24.0 docker.io/enmasseproject/agent:0.24.0

https://github.com/EnMasseProject/enmasse/pull/2061


Jquery 1.12.3 since we still have to support IE 8

This also fixes a problem that javascript was included twice on the page.

This breaks the docs page for me

Try now? Although whether or not anything else works on IE8 is unclear. But we generally use the 1.x branch because of this. 8% of PMG users, for example, are on IE8.

Works in docs for me and was missing in babbage so added there too.


Text changes - update FAQ link in the app

current:
https://faq.carbondefi.xyz/what-is-an-overlapping-strategy#overlapping-budget-dynamics
updated:
https://faq.carbondefi.xyz/strategy-types/concentrated-liquidity#concentrated-budget-dynamics

Is this still relevant? @ashachaf


Enable Flutter compositor layers

Enable Flutter compositor layers to allow Flutter to reduce the number of compositions when unnecessary and potentially overlay them. Mirror issue for https://b.corp.google.com/issues/132812775; conversation should occur there.

Work on this is in progress on the embedder_layer branch.

Patch has been posted and unit-test coverage is a superset of anticipated needs.


Broken Link "Code-signing for Protected Media Components in Windows Vista"

This is the correct link
http://download.microsoft.com/download/a/f/7/af7777e5-7dcd-4800-8a0a-b18336565f5b/pmp-sign.doc

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

ID: 93540672-755a-ad5e-e226-f8b1ce61ff80
Version Independent ID: 99be7ed0-83a3-e8ef-b20b-865ebca374e8
Content: Introduction to Test-Signing - Windows drivers
Content Source: windows-driver-docs-pr/install/introduction-to-test-signing.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @tedhudek
Microsoft Alias: tedhudek

Thanks @cow613 and apologies for the delay.  I just pushed this change, should appear on the live site within half an hour.  Appreciate the feedback!


Changed the vite syntax to reflect vite docs.

The vite docs recommend the usage of npm create as a way to bootstrap via vite. Making this change to maintain consistency between vite docs and svelte quick start

@benmccann can you tag someone that can merge this? please

https://github.com/sveltejs/kit/pull/5262https://github.com/sveltejs/kit/pull/5262 has fixed this issue, so closing!

https://github.com/sveltejs/kit/pull/5262 updated the SvelteKit site. This is for the Svelte site

Merging this so that the two sites match one another


Restore on cluster using weave fails to get the nodes to "active" state and is stuck in "unavailable" state.

Rancher server version - Build form master - Mar 7 - c8da22fb
Steps to reproduce the problem:
Create a 3 node DO cluster with weave as network provider.
Deploy few workloads.
Take a backup.
Add 1 more worker node.
Restore to the backup.
Cluster gets to "Updating" state and then to "Active" state but the nodes continue to be stuck in "Unavailable" state with error message - "Runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized "

Tested with latest build from master  - Mar 7
Create a 3 node DO cluster with weave as network provider.
Deploy few workloads.
Take a backup.
Add 1 more worker node.
Restore to the backup.
Cluster  gets to "Active" state and all the nodes get to "Active" state as expected.
Able to deploy workloads and work with restored cluster.


xOffset in config not respected

Hi! First off, thanks for forking the mod. I was missing playing with this feature. I'm having an issue with the xOffset config not being respected. I've set it to  100, 500, 1000, -10000 but it always remains in the same place - opposite the offhand slot. This conflicts visually with Quark's armor ticker.
I'm playing in 1.15.2 and I also have "Console Experience" installed which may be messing with this, as it shifts the hotbar up the screen a few pixels. I'm setting up a vanilla profile at the moment to test if the xOffset config works without Console Experience installed.
I'm not sure if there's anything else I can provide to make debugging easier - would a debug.log even help?

Fixed in 1.16.3


added beta badge

Signed-off-by: ishitakeshawani<EMAIL_ADDRESS>Description
This PR fixes #3860
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

can you add some screenshots @ishitakeshawani  ?

Codecov Report

Merging #4043 (c836113) into master (e1ece53) will increase coverage by 7.51%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4043      +/-   ##
==========================================
+ Coverage   18.95%   26.46%   +7.51%
==========================================
  Files          64       64
  Lines        4992     4992
==========================================
+ Hits          946     1321     +375
+ Misses       3757     3262     -495
- Partials      289      409     +120

Flag
Coverage Δ

gointegrationtests
9.77% <ø> (?)

integrationtests
∅ <ø> (∅)

unittests
18.95% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

mesheryctl/internal/cli/root/system/logs.go
21.59% <0.00%> (+21.59%)
:arrow_up:

mesheryctl/internal/cli/root/system/check.go
23.77% <0.00%> (+22.37%)
:arrow_up:

mesheryctl/internal/cli/root/system/update.go
30.68% <0.00%> (+29.54%)
:arrow_up:

mesheryctl/internal/cli/root/system/restart.go
33.92% <0.00%> (+32.14%)
:arrow_up:

mesheryctl/internal/cli/root/system/stop.go
40.00% <0.00%> (+39.09%)
:arrow_up:

mesheryctl/internal/cli/root/system/start.go
53.89% <0.00%> (+52.88%)
:arrow_up:

mesheryctl/internal/cli/root/system/status.go
62.82% <0.00%> (+62.82%)
: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 bff0fa3...c836113. Read the comment docs.

can you add some screenshots @ishitakeshawani ?

Good work @ishitakeshawani, but right now the logo looks quite dull.

Could you please make it transparent, like this

and then just make the text blue or purple
// @sudo-NithishKarthik

Yes, will make it transparent. Should I also put the border color like purple or blue?

Yes that would be great

Is it looking good ?

Could please make it a little thinner and it would be great if the word "beta" is right in the centre.

Exciting, @ishitakeshawani. @Nikhil-Ladha's spot on with respect to the color.

Which color should I use here? There is also some whitespace below the text beta. Inspected it many times but have no idea that how to remove it.

@warunicorn19 @sudo-NithishKarthik

Yes, i think that too will work...

@ishitakeshawani I was thinking maybe we could use something like this instead?

@sudo-NithishKarthik @Nikhil-Ladha @debo19 views?
This is from youtube btw

Do you mean by the logo, then meshery and beta all?

No i mean the beta would go one top of Applications like in the image.

No I mean the beta would go one top of Applications like in the image.

Ok got it. Sounds good.

There are orange / yellow colors included in the Meshery UI Figma file that can be used for the "beta" word.

There are orange/yellow colors included in the Meshery UI Figma file that can be used for the "beta" word.

Yes, I will use these colors. Thank you @leecalcote

@ishitakeshawani heads-up - a merge conflict to address.

@ishitakeshawani heads-up - a merge conflict to address.

Oh, will solve it by tonight.  Thank you, Lee.

Thank you, @ishitakeshawani. You don't happen to have a screenshot handy, do you?

Thank you, @ishitakeshawani. You don't happen to have a screenshot handy, do you?

Sorry, for the delay. I will send the screenshot and push the code by tomorrow.

@sudo-NithishKarthik  I did changes in the code. Can you review it. In the header, we need to check if the page is beta then add the badge. But in the component, it is possible to add a direct beta badge in code. So should I do it or what approach should  I use for components ?

I updated the color. Visually, the tag looks good to me. @sudo-NithishKarthik, are we good to merge with this beta tagging framework?

Sorry for the late response. @ishitakeshawani , although we can improve it further, let's not spend too much time on this. This will work just fine. Thank you.

Sorry for the late response. @ishitakeshawani , although we can improve it further, let's not spend too much time on this. This will work just fine. Thank you.

Thank you @sudo-NithishKarthik Looking forward to learn more.


Post Content is Mixed up in projects part , achived project route not working

post content is mixed up with project content and UI is collapsed if I delete posts, and achive route is also not working

, could you please tell me how to fix it
thank you
you made a great portfolio

Hi @jarviotdev, it's hard for me to help without seeing any code. Is this happening on a fresh install?

@bchiang7 yes it's happening on a fresh install, i have tried more than twice

I can't seem to reproduce this problem, could you provide any more details?

Could you please fresh install from git in other directory error is in graphql query , or could you just add it on any other platform , it giving lots of error

see error in graphql querys

Hi @jarviotdev could you point me to a repository where you're experiencing this error? I've tried a fresh install in another directory, and I still can't reproduce the problem

error fixed after in fulol regex search i replaced
"projects" with "content/projects"


new version and the hassle of having to reconfigure/recode everything every time.

I saw that 1.9 was released recently.
as with each update I have to completely reconfigure all the codes of all the .css files which literally takes a lot of time.
Is there a method to be able to switch to the new version with our old settings without having to recode everything individually...?
thx

Same here as well, with the new version even the background blur is messed up I couldn't make it the same as the early version so I just went back to version 1.8.1 for now, it works perfect for me I have no reason to upgrade

there is no easy option - it has to be done manually
version 1.9 is an interim version - it had to be released because of the many changes (almost 40 innovations) and the missing documentation for them.
moudey is working hard to build the entire menu from the ground up for even more features

as it is not known if the script syntax will need to be changed further, features such as converting an old script to a new one will have to wait


browse/anime full_page

Trying to get browse/anime titles with parameters "status" = "Currently Airing" and "full_page" = "true" doesn't seem to ignore pagination.
e.g. https://anilist.co/api/browse/anime?full_page=true&access_token=...&status=Currently+Airing
returns 40 titles. I've tried few different parameter combinations yet I haven't been able to get full_page working.
Am I just failing something or...?

Sorry this took awhile, a rather silly mistake on my part, I wrote it in the docs as full_page but it was actually just fullpage, anyway it supports both now and should work as expected.


[23.05] matrix-hookshot: 4.4.1 -> 4.5.1

Description of changes
https://github.com/matrix-org/matrix-hookshot/releases/tag/4.5.0 https://github.com/matrix-org/matrix-hookshot/releases/tag/4.5.1
https://github.com/matrix-org/matrix-hookshot/security/advisories/GHSA-fr97-pv6w-4cj6
(cherry picked from commit 3ba4996d21857d883046553549f13bdc34022ee7)
Backport of #257423

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Manual backport due to automatic backport failure: https://github.com/NixOS/nixpkgs/pull/257423#issuecomment-1737094641

Sure, I can do that later today, but the message that the github-actions bot places in case of backport failure should be changed to reflect that, if that is the standard procedure. (Because I did nothing more then run the commands it gave me, fixing the conflict and then continuing the cherry-pick.

Done.


generating options

move the formatToExtension to a function or class variable, so possible extensions could be added. For now the list of format strings mapped to extensions seems to carry on some old fontLab legacy...

@typemytype is this still an issue?

nope see https://github.com/robofab-developers/fontParts/blob/master/Lib/fontParts/base/font.py#L245

that's what I thought, wanted to double check


Travis issue

Since late last week (early May) Travis has been regularly encountering this issue when testing branches on Github. It is almost always django-haystack (I encountered one time when it was a different package but didn't record it) and it happens on ~3/5 of all test runs. As we have multiple test runs per Travis build, the builds fail almost every time they are run.
This is the link in the screenshot:
https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received

This is the latest version of django-haystack, from March 2018

This issue is separate from read timeout errors, which seem to be dealt with appropriately

The issue has been narrowed down to a set of instructions that aren't normally run while we develop, specifically line 18 (i.e. Step 7/10) in Dockerfile-local:
RUN /docker_venv/bin/pip3 install -r /requirements/local.txt
This is during the Building django stage of ./csfg build.

Normally ./csfg build skips this, as its already been done.

But if I wipe everything (or at least as much as possible) to do with Docker with the following command, build is forced to run it:
docker system prune -a
Since build now has to redownload everything this takes a while, so I'm doing 5 tests to see if any fail in the same place as Travis

All 5 completed the 10 steps without issue, so nothing can be concluded

All 5 runs again completed the 10 steps without issue, so nothing can be concluded. django-haystack takes longer than the others to be retrieved, but still just a second or two - nothing near the 10 minutes required for Travis to time out

From my research so far:

It is unlikely:

A problem with the build, as it is unchanged and has worked locally in all tests
A problem with django-haystack, as it is unchanged, has worked locally on all tests, and on Travis the download does work ~3/5 of the time
A problem with the download taking too long, as it takes just a second or two on every successful test
A read timeout error, as there is evidence that these are handled appropriately

It could be:

Related to a change elsewhere in the field guide between October 10 2018 and April 23 2019; I reran Travis on #721 (a very old branch) twice and it completed the 10 steps successfully in all 20 runs, but I reran Travis on #890 (a more recently updated branch) and it failed once.
Related to how the project is slowly increasing is size; it succeeded in all 20 runs as of #721, failed once as of #890, and is now regularly failing
A problem with Travis itself, as it has worked locally on all tests

It would be worth logging a support ticket with Travis as they could look at network traffic for the jobs to check if it's something behind the scenes.
Also we could load that requirement from a different source as a work around until the problem is found.

Today everything seems to be working again, Travis has so far run the 10 steps without issue every time its run, with only one issue elsewhere

It happens a lot less often since it's needed on just the one run, but the above timeout during the Build Documentation test is not a once-off

No further issues after a week, so I believe nothing needs to be done on our part


Laravel 10

Laravel 10 updates for the Storm library

Thanks for that @wverhoogt.
If you have a chance, could you fix this error here to make the Code Quality check pass - https://github.com/wintercms/storm/actions/runs/6199942874/job/16837822721?pr=157. You can also have a try at fixing the Code Analysis errors as well (https://github.com/wintercms/storm/actions/runs/6199942875/job/16837822953?pr=157), but if some of them are too difficult, I'm happy to review them myself.

I´ll check the Qode Quality and Code Analysis errors. Let you know if I run into difficulties.

I´ve checked the code quality issues, and managed to fix them except for one:
------ ------------------------------------------------------------------------------
  Line   Database/Model.php
 ------ ------------------------------------------------------------------------------
  206    Static access to instance property Winter\Storm\Database\Model::$dispatcher.
 ------ ------------------------------------------------------------------------------

I couldn´t find a way to tell Larastan that that variable is both static and nullable.
It appears that Laravel 10 has changed quite a few types used in their API. As a result, many Winter subclasses reequired changes to pass the Larastan tests.
Also, MaintenanceModeException is no longer used within Laravel. As a result 'wentDownAt' , 'retryAfter' and                'willBeAvailableAt' are no longer available.
The package nunomaduro/larastan has fixes for Laravel 10 which are not yet in a stable version. I use "dev-master" in composer.json for that reason.

@wverhoogt feel free to commit what you have so far, and I can try and work out that last one (or ignore if it we can't fix it from our end). :)

Have committed my changes.

Trivial conflicts fixed.

Fixed Larastan composer error.


fbp-generator: add support for DECLARE statement

Now the generator handles the declaration and usage of new types in the FBP itself.
e.g.
DECLARE=MyType:fbp:my-type.fbp
my_node(MyType) OUT -> ...
In the generated C code now, we first build the node spec with a placeholder and after
we change this to the proper value, since we need to create this new types in runtime.

Is the problem of fbp A declaring a type using fbp B, which declares a type using fbp A been addressed here?
I algo agree that this code would benefit a lot from splitting some things into more functions. Maybe go through all the declarations, ensuring you have resolved all the types needed for the program to run, then create one function for each type that will hold its specs, exported ports, options, etc. Create the type from there and return that for the parent. It's a recursive solution, but I think it will make it more clear to see what's happening, when and where.

I agree with Sachiel that the type-store should have a scope of the loader. If a FBP is loaded, then all DECLARE that appears inside it should be constrained to that FBP and not leak into siblings, parent or children.

Ok, I'll send a v2, thanks!


Alternative library that is closer to oauth2client API

Note: oauth2client is now deprecated. As such, it is unlikely that we will
review or merge to your pull request. We recommend you use
google-auth and oauthlib.
I've recently removed oauth2client from a project. It was a struggle to determine how to go about it without having to do a ton of extra work. It took a bit of digging to find google-auth-oauthlib and ultimately it drops in fairly nicely, with a lot less work than using google-auth and oauthlib directly .

i signed it!


The RPM package is not noarch

I note that apisix-2.1 provided a noarch rpm package,
But it contains some binaries files built on X86_64 and caused the apifix command cant find the file at ARM system.
Like apache/apisix#issue-691844591.
# file ./local/apisix/deps/lib/lua/5.1/lfs.so
./local/apisix/deps/lib/lua/5.1/lfs.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=5de2ad9d73ddbdaa91151ddfee3eef545a010902, not stripped

Would you like to add some options to fpm in run.sh to buind different arch packages?
Or I can provided an spec file to build packages by rpmbuild command ?

Which cloud platform do you use for ARM compilation?

@membphis  I build it on my local ARM server.
If I build it locally, it's OK.

Which cloud platform do you use for ARM compilation?

Hi @membphis , we are using a physical server with Kunpeng 920.

@idbeta do you have time to look at this issue?

@idbeta do you have time to look at this issue?

Yes, but I don’t have this kind of environment now, @imjoey can you provide an environment to test it. My qq number is 83434649

I note that apisix-2.1 provided a noarch rpm package,
But it contains some binaries files built on X86_64 and caused the apifix command cant find the file at ARM system.
Like apache/apisix#issue-691844591.
# file ./local/apisix/deps/lib/lua/5.1/lfs.so
./local/apisix/deps/lib/lua/5.1/lfs.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=5de2ad9d73ddbdaa91151ddfee3eef545a010902, not stripped

Would you like to add some options to fpm in run.sh to buind different arch packages?
Or I can provided an spec file to build packages by rpmbuild command ?

I got your point, the RPM package provided now is indeed not noarch, the name needs to be changed. @moonming

I note that apisix-2.1 provided a noarch rpm package,
But it contains some binaries files built on X86_64 and caused the apifix command cant find the file at ARM system.
Like apache/apisix#issue-691844591.
# file ./local/apisix/deps/lib/lua/5.1/lfs.so
./local/apisix/deps/lib/lua/5.1/lfs.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=5de2ad9d73ddbdaa91151ddfee3eef545a010902, not stripped

Would you like to add some options to fpm in run.sh to buind different arch packages?
Or I can provided an spec file to build packages by rpmbuild command ?

I got your point, the RPM package provided now is indeed not noarch, the name needs to be changed. @moonming

@idbeta yep, exactly. We are supposed to make independent rpms for each cpu arch platforms, x86_64 and aarch64 for now.
I guess @Fuchange and I could help to commit a pr to fix this issue.

@idbeta  We are working to bring OpenResty as well as APISIX to openEuler community, please refer to https://gitee.com/openeuler/community/pulls/1240 for details. Welcome to join us.

@idbeta yep, exactly. We are supposed to make independent rpms for each cpu arch platforms, x86_64 and aarch64 for now.
I guess @Fuchange and I could help to commit a pr to fix this issue.

@idbeta  We are working to bring OpenResty as well as APISIX to openEuler community, please refer to https://gitee.com/openeuler/community/pulls/1240 for details. Welcome to join us.

Thanks, I will go to your community to learn.

@membphis  @idbeta
Hello everyone ,I merged a pr(#4) to fix it ,pls have a look~

nice, many thx @Fuchange


Add my first file

Hello World! I have created a new branch, created a  New file, and made a commit. I am so happy and I look forward to making the most of GitHub.

Pull request successful and merge successful.


Make btrfs call same interface as others

Most storage drivers call graphdriver.GetFSMagic(home),
it is more clean to easy to maintain. So btrfs need to
adopt such change.
Signed-off-by: Kai Qiang Wu(Kennan<EMAIL_ADDRESS>

ping @vbatts

LGTM

LGTM (if Janky's happy)


mzML profile mode?

From what I can tell, this tool only outputs centroided data, even when the data is acquired in profile mode.
It would be nice to have the option to output either centroided or profile data when samples are acquired in profile mode. Very useful for some metabolomics applications.

Hi,
Thanks for your input. I decided to output the centroided data when available after a mail conversation with a very helpful expert at thermo. It's important to note that not all profile scans have centroided data available and we don't do any post-processing besides the native thermo library. That's also why we have the "MGF with profile data excluded" option.
I agree that the user should be able to choose, is it ok if I add a flag and keep the default behaviour?

I think it's great if the default is to output the Thermo peak centroided data. However, that should be documented, and having a flag to get the profile data instead would be fine.

@rmflight can you test the new version. We have address the following issue.

I am pretty sure I did not change anything in our call to the TRFP but the spectrum does not get picked anymore.

For v112 vs v114, I get file sizes of 1749854 and 1749796, respectively when I specify -f 1, and don't do anything for peak picking.
When I add the -p option in v 1.1.4, my file size jumps to 23974569, or 13X the size of the other two. So from that simple perspective, the -p is definitely reporting profile mode spectra. I will read them into R using xcms hopefully on Friday (currently on vacation), but wanted to download and get this checked ASAP.

@rmflight does this work for you with the v115 version and using the new outfile= option?
We currently have the strange situation that with peak picking enabled (noPeakPicking flag is not set) we get profile data:
https://github.com/OpenMS/OpenMS/pull/4095
Can anybody confirm that?

At least they are declared as profile spectra according to the CV term that is created here (without considering the new flag somehow):
https://github.com/compomics/ThermoRawFileParser/blob/a4038c3499435b3aec44b600ef7dc5f0a6e05550/Writer/MzMlSpectrumWriter.cs#L951

Won't be able to check until tomorrow, unfortunately. Currently on
vacation, and driving all day today. Should be able to check tomorrow.
On Thu, May 16, 2019, 8:14 AM Timo Sachsenberg<EMAIL_ADDRESS>wrote:

@rmflight https://github.com/rmflight does this work for you with the
v115 version and using the new outfile= option?
We currently have the strange situation that with peak picking enabled
(noPeakPicking flag is not set) we get profile data:
OpenMS/OpenMS#4095 https://github.com/OpenMS/OpenMS/pull/4095
Can anybody confirm that?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/compomics/ThermoRawFileParser/issues/34?email_source=notifications&email_token=AALQR6VAVVQ2DIPCUCQHJW3PVVFZRA5CNFSM4HJRIVD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVRTVVY#issuecomment-493042391,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALQR6V6X25P25YZBUZMJXLPVVFZRANCNFSM4HJRIVDQ
.

OK, so both v114 and v115 have profile in the output type, there is no centroid to be found, even when thermo peak picking is asked for. This is in there even when I specify the output file directly using -b. So even though peak picking is being performed, the output does not reflect that. I'm guessing there is a small bug, as pointed out by @jpfeuffer

Hi if you run the parser without the -p flag, the native thermo library centroiding is applied. In the mzML output format, both centroid en profile scans are reported.
Using the -p flag disables the thermo centroiding and results in bigger files. In the mzML output format, both centroid en profile scans are reported.
So using the -p flag results in the same number of spectra as not using it. It's like not selecting the vendor peak picking in msconvert.
Could you provide a link with the RAW file for which you don't get centroided scans?

Same file. As Julianus linked in this issue We think just the metadata is not properly updated but centroiding is performed.

Here is a file I've been using, in case it helps to have another one: https://drive.google.com/open?id=1AWSEQV7TtnFtPHwzld5U1KWtz1aM6kUm

Hi @timosachsenberg what do you mean with the metadata?

Hey! I think he means the cvparams preceding the spectrum:
We always get
<cvParam cvRef="MS" accession="MS:1000128" value="" name="profile spectrum" />
now, although peak picking is activated.

Right. If you do a search for centroid, it is not there, even if peak picking is activated. Previously, in v112, the metadata would contain centroided spectrum (or something similar), indicating that the spectrum was peak picked. Now, it never does, whether peak picking is activated or not.

Hi thanks you're right, I changed it because I wanted to report the same scan type as msconvert but I didn't test it thoroughly enough. I fixed it in the v1.1.7-SNAPSHOT version that I've just updated.

Thanks! There seem to be some new files (e.g. log file) that are not required.

Yep, just tested, and the metadata seems correct.

I think the version string is not updated ... version="1.1.5"

except for the minor things like additional (unneeded? e.g. log) files in the release, no update of the version number (I guess because its a snapshot and no official version) everything seems to be fixed.
Thanks!

Also, just FYI, outside of the msnPrecursorIntensity issue (see #47 ), the output data from both ThermoRawFileParser and msconvert appears to be identical in profile mode. Which I have to admit is awesome, because now I can just run all my conversions under Linux.

Hi @timosachsenberg the log file has been there since the beginning but I agree the logging to file should be optional. I've commented it out in the log4net.config file and updated the v1.1.7-SNAPSHOT version. I've updated the logging section in the readme file.
@rmflight indeed the precursor intensity isn't there, I'll comment on that issue #47. The original plan was the create a simple thermo to MGF library for linux but with the mzML output addition and figuring out the thermo native library, it took a lot longer than expected. The msconvert code has proven itself over the years and is a lot more mature so I'm still expecting issues to pop up.
Thanks again for the extensive testing!

Thanks! You are awesome!


uses a different merge function for every combination of inputs

it should just have a single postgres function that takes one selector arg and one setter arg
the arg type should be record or maybe hstore or maybe json
then we don't have to constantly create new merge functions for new inputs

@evadne i think this would solve a large number of problems
it would also make the approach competitive even with 9.5 UPSERT because we don't require unique keys

@seamusabshere a couple of questions

Do we need to marshal / unmarshal and does that hurt performance
Is it bad if we rely on Postgres 9.5 UPSERT?

@evadne

i checked in the #postgresql IRC channel and apparently you can't use record as an input type. that makes me think we have to pass in json (e.g., upsert(selector::jsonb, setter::jsonb)) in order to allow many different inputs to use the same function. there will be a performance penalty, but it will still be faster (i think) than the alternatives (except of course native 9.5 upsert, but see below).
9.5's upsert is actually not equivalent... it requires you to have a unique index and runs the update only if there is a duplicate key error. also, most people don't have 9.5 (as of this writing it's not even available on Amazon RDS)

i think this is basically impossible - we have to write an upsert function for every combo of inputs.


Display length metric

It is not clear what metric a length value (e.g. for width or height of a region) is using.

Fixed in release 0.4.0

resolved by 70b8a8dbbc90004dda3427bd662807a9667cd596


Specific usage CMAKE_OSX_DEPLOYMENT_TARGET

Info
Current Veles version for macOS requires at least macOS Sierra: 10.12.4 (16E195)
See CMakeLists.txt
Details

CMake seems to ignore CMAKE_OSX_DEPLOYMENT_TARGET
Confused about CMake's cached variable setting priority

set(CMAKE_OSX_DEPLOYMENT_TARGET "10.10" CACHE STRING "Minimum OS X deployment version")
If not set explicitly as a cache variable the CMAKE_OSX_DEPLOYMENT_TARGET is initialised by the MACOSX_DEPLOYMENT_TARGET environment variable.

Thanks for spotting this! Could you please check whether #335 fixes the problem?
I've attached a .dmg file built after applying this change.
veles-osx-req-version-fix.zip

Hi mkow,
thank you for updated version, but this doesn't help, sorry.
Message when I try to launch Veles.app from /Applications:
You can’t use this version of the application “veles.app” with this version of OS X.
You have OS X 10.11.6. The application requires OS X 10.12 or later.

And then I get this error when I launch via terminal:
Check with the developer to make sure veles works with this version of OS X. You may need to reinstall the application. Be sure to install any available updates for the application and OS X.

Click Report to see more detailed information and send a report to Apple.

When I execute from terminal:
/Applications/veles.app/Contents/MacOS/veles

I get output:
dyld: Library not loaded: @rpath/QtNetwork.framework/Versions/5/QtNetwork
  Referenced from: /Applications/veles.app/Contents/MacOS/veles
  Reason: image not found

So, may be it's related to Qt too.
Additional info:
Qt for macOS - Deployment

Hmm, are you sure you downloaded the correct file? First file I attached in my response was improperly built (see #336, sorry for that!) and after about 15/20 minutes I reuploaded it. MD5 sum of the correct file:
bc6a0932c20e5c360f25a21d54a06856 *veles-osx-req-version-fix.dmg
The error you pasted (the problem with QtNetwork) looks exactly like the one caused by #336.

mkow,
I tried both files, but I'm still getting that error msg about OS version.

veles-osx-req-version-fix.dmg

MD5 (old): 585d6c3933a424755685abec8366c49d
MD5 (new): bc6a0932c20e5c360f25a21d54a06856

veles-working.dmg

MD5: bc6a0932c20e5c360f25a21d54a06856 (same as new veles-osx-req-version-fix.dmg)

Note: I succeeded with app from dmg, but failed to run from /Applications/

I'll try to find a device with macOS 10.11.6 and check if it's reproducible, without the device it may be hard to find a solution.
If you would manage to fix it anyhow please tell us (or just create pull request).

@mkow, just tested, everything works fine! Thank you so much!
Tested on:

OS X (macOS) 10.11.6 El Capitan.

Screen

That's great :)
In case of any other problems please don't hesitate to submit an issue, we definitely lack proper testing on macOS.

Sure, thanks!


Cannot import name '_ext'

Hello,
First of all, thank you for your work.
In the context of a concrete application for my thesis subject I would like to test your PVN3D code. However, I encounter a problem that I can't correct.
Indeed, when using demo_linemod.sh I encounter the following problem :
ImportError: cannot import name '_ext' from 'lib.pointnet2_utils' (/home/tpetitjean/PhD_Thesis/T1Pvn3D/PVN3D/pvn3d/lib/pointnet2_utils/__init__.py)

I'm sure I installed PointNet properly, and built it as indicated. I can see PointNet installed in my Conda env and using the python3 setup.py command build_ext has created a build file inside the PointNet tree.
Do you have any idea what I can do to correct this problem? Is there a file to move by hand after the build? Or is it the build that did not work as expected?
I thank you in advance for your clarification and wish you a very pleasant continuation.
Sincerely,
Theo

For error1. It seems that you don't have the libcudart.so.10.0, you can download it.
For error2: torch 1.4 is not suitable for this task,  you can use torch 1.0.1 as a substitute.

For error1. It seems that you don't have the libcudart.so.10.0, you can download it.
For error2: torch 1.4 is not suitable for this task, you can use torch 1.0.1 as a substitute.

Hello! Tanks for the suggestion, it can lookstrange but, I fixed the both issue in a kinda weird way. So here and update of what I did (it can be useful for someone one day).
For the first err, it appears that to install the PointNet properly I had to first run the installation of it (require.txt) in a suitable version of torch (1.4), then to build the code PVN3D by using back the 1.0.1 torch re-installed by :
pip -r req.txt

Then for error 2 (which is basically the following of the previous steps) it appear that activating the cuda env outside of the file create a sort of localization issue for the file. So I simply Run:
bash

Then cd /path of the PVN3D then conda activate my env and the problem didn't show ever again. Those first to problem come from the fact that I don't run everything on my personal laptop but on a external working server. (I suppose, like I said, I fix it, but it remain kinda obscure to me.).
Then I encountered a brand-new problem linked to PCL. Since I saw online that the problem was evilly reported, here an update of what I've done to fix it.
On the server I actually have Unbuntu 18.04 installed. Running the classical command of:
sudo apt-get install libpcl-dev -y
pip install python-pcl

Will probably return a Error such as:
/usr/lib/x86_64-linux-gnu/libpcl_keypoints.so.
This issue come from the fact that the command ran before will automatically instal the higher version of libpcl and not the 1.7 wich is an old one.
It turns out that you need to apt install libpcl-dev of version 1.7.x . But the default version of libpcl-dev on Ubuntu 18.04 is (you can run apt-cache policy libpcl-dev to check it out.).
In order to fix that issue you will have to first include inside the source of unbuntu the xenial link for instalation (by default it will be Bionic and we want to add the xenial part.). In my cases I just added those two lines:
deb http://dk.archive.ubuntu.com/ubuntu/ xenial main
deb http://dk.archive.ubuntu.com/ubuntu/ xenial universe

Then we have to run sudo apt update. After that you can run  apt-cache madison libpcl-dev to check the available version of libpcl-dev.  it should return smtg like :
apt-cache madison libpcl-dev
libpcl-dev | 1.8.1+dfsg1-2ubuntu<IP_ADDRESS> | http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages
libpcl-dev | 1.8.1+dfsg1-2ubuntu2 | http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
libpcl-dev | 1.7.2-14build1 | http://dk.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

If you don't see any 1.7.2 lib available it simply mean that it still misses some xenial source, here is a more complete source list for xenial https://gist.github.com/rohitrawat/60a04e6ebe4a9ec1203eac3a11d4afc1 just add it to your source file and try again.
Then you can run in order to install the 1.7 lib. You will encounter some dependency problems, be patient and fix them on by one. Once the 1.7 lib is installed you will be able to install all the missing part from the 1.7 such as keypoints1.7 or surface1.7.
To do so you just has to check whats part is missing when you try to. If libpcl-keypoints1.7 is missing just run, then try to import pcl again, and install package by package according to the error printed. (here some example) :
sudo apt-get install libpcl-outofcore1.7
apt-get install libpcl-segmentation1.7
apt-get install libpcl-surface1.7

According to this topic : https://ask.csdn.net/questions/1705497 it is possible to face some more issue after these steps. Please refer to this and try the proposed fix.
After all of this you should be able to correctly install PCL on the 18.04 unbuntu and of course using this amaizing PVN3D work !

I saw your words and  i think the main problem is the installation of the PCL on Ubuntu 18.04. I install it in two computer, ubuntu 16.04 and 20.04, IN 16.04, it is more easier, It seems that through sudo apt-get install libpcl-all`` can install . For 18.04 and higher, must through the git method # install dependencies
sudo apt install libpcl-dev libvtk6-dev
clone fork with fix for Ubuntu 18.04
git clone https://github.com/Tuebel/python-pcl
cd python-pcl
python3 setup.py install
`
pcl 1.7 is not suitable for 18.04,  hope this will help you!

I saw your words and i think the main problem is the installation of the PCL on Ubuntu 18.04. I install it in two computer, ubuntu 16.04 and 20.04, IN 16.04, it is more easier, It seems that through sudo apt-get install libpcl-all can install . For 18.04 and higher, must through the git method
sudo apt install libpcl-dev libvtk6-dev
clone fork with fix for Ubuntu 18.04
git clone https://github.com/Tuebel/python-pcl
cd python-pcl
python3 setup.py install
`
pcl 1.7 is not suitable for 18.04, hope this will help you!

Hello,
First of all, thank you for your work.
In the context of a concrete application for my thesis subject I would like to test your PVN3D code. However, I encounter a problem that I can't correct.
Indeed, when using demo_linemod.sh I encounter the following problem :
ImportError: cannot import name '_ext' from 'lib.pointnet2_utils' (/home/tpetitjean/PhD_Thesis/T1Pvn3D/PVN3D/pvn3d/lib/pointnet2_utils/__init__.py)

I'm sure I installed PointNet properly, and built it as indicated. I can see PointNet installed in my Conda env and using the python3 setup.py command build_ext has created a build file inside the PointNet tree.
Do you have any idea what I can do to correct this problem? Is there a file to move by hand after the build? Or is it the build that did not work as expected?
I thank you in advance for your clarification and wish you a very pleasant continuation.
Sincerely,
Theo

I have the same problem, did you manage to solve this issue ?

I have the same problem, did you manage to solve this issue ?

Hi, yes i did, some point are explained here, if you can't fix it with my previous answer, be sure to notify me, and i'll do my possible to make the solution bit more clear in order to help there ;)

I have the same problem, did you manage to solve this issue ?

Hi, yes i did, some point are explained here, if you can't fix it with my previous answer, be sure to notify me, and i'll do my possible to make the solution bit more clear in order to help there ;)

I solved this problem in a strange way, I installed the tutorial installation, and then Cannot import name'_ext' appears; the solution:
Change from. Import _ext to:
try:
from lib.pointnet2_utils import _ext
except ImportError:
from torch.utils.cpp_extension import load
import glob
import os.path as osp
import os


flutter_embedded example not working

Description

I wanted to check out how flutter_embedding works with Jaspr and after getting the example project to run it doesn't embed Flutter like in the demo video

Additional Context

jaspr: v0.16.1
pubspec.yaml
This is the pubspec.yaml file in the example project
name: flutter_embedding_demo
description: A demo of embedding a flutter app into a jaspr website.
version: 0.1.3
publish_to: none

environment:
  sdk: '>=3.0.0-0 <4.0.0'

dependencies:
  firebase_core: ^3.8.0
  flutter:
    sdk: flutter
  flutter_riverpod: ^2.6.1
  jaspr: ^0.16.1
  jaspr_flutter_embed: ^0.4.1
  jaspr_riverpod: ^0.3.15
  riverpod: ^2.6.1

dev_dependencies:
  build_runner: ^2.4.13
  flutter_test:
    sdk: flutter
  flutter_lints: ^5.0.0
  jaspr_builder: ^0.16.1
  jaspr_web_compilers: ^4.0.10+1

flutter:
  uses-material-design: true
  assets:
    - assets/dash.png

jaspr:
  mode: server

There was a layout bug in jaspr_flutter_embed. Fixed in the newest version 0.4.2.

Thanks for the swift fix @schultek!


Update the Node get started and other docs to use tsx to run .ts/.mts scripts

What is the issue?
This task is to replace node --loader ts-node/esm with tsx in our docs where running .ts/.mts scripts.
In the Node.js get started https://docs.dagger.io/sdk/nodejs/783645/get-started:

You no longer need a tsconfig.json as well. This step is not needed: npx tsc --init --module esnext --moduleResolution nodenext.
Instead of npm install ts-node typescript use npm install tsx.

Is this related to this issue I created?

@vikram-dagger Hey Vikram, is this related to our Zenith documentation?
I'm not sure we will have the kind of issue with the new doc so should we close this issue?

Closing as this is not required when running Dagger Functions.


Importing siemens-ix.css does not result in the same style as splitting it up in siemens-ix-core.css and chosen themes

Prerequisites

[X] I have read the Contributing Guidelines.
[X] I have not leaked any internal/restricted information like screenshots, videos, code snippets, links etc.

What happened?
I wanted to add a custom theme and followed the documentation as stated here
This resulted in a table not being displayed correctly, or the crucial part. Not in the same way which either means there is something wrong with the core-css, or the documentation is kind of misleading in that regard.
I created a simple stack-blitz here: https://stackblitz.com/edit/xnfrdi-ptmfn7?file=src%2Fstyles.css
Toggling between only the siemens-ix.css and the core + theme results in the table formatting differently.

Hello @Endunry.
In the core-css, the dependencies like bootstrap are not included, which is why the tables are not stylled correctly.
non-core: https://github.com/siemens/ix/blob/main/packages/core/scss/ix.scss
core: https://github.com/siemens/ix/blob/main/packages/core/scss/ix-core.scss


oes-gate needs Spinnaker services to start

https://devopsmx.atlassian.net/browse/OP-22798
Case:
when spinnaker services are disabled gate pod is down with errors where other classes expecting clouddriver and front50 client creation  even if the services are disabled. since a lot of classes dependent on those during start up  implementing No-operation classes with respect to clouddriver and front50 based on configuration status has resolved with no errors in logs and gate is up.

As part of configuration able to fix the relevant  issue and same has been updated in Jira hence closing the PR


feat: remove as self in model 1.1

Description

For model 1.1, do not use 'as self'.  Instead, always use ':'
Validate to ensure 1.0 still use 'as self' and contains no ':'

References
Close https://github.com/openfga/syntax-transformer/issues/92
Review Checklist

[X] I have clicked on "allow edits by maintainers".
[ ] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[X] The correct base branch is being used, if not main
[X] I have added tests to validate that the change in functionality is working as expected

Incorrect column identified with
model
  schema 1.1
type user
type group
  relations
    define member:[user]
type resource
  relations
    define writer as self
    define reader as self or writer

Incorrect column identified with
model
  schema 1.1
type user
type group
  relations
    define member:[user]
type resource
  relations
    define writer as self
    define reader as self or writer

Actually, confirmed that the proper line is highlighted

This error highlight looks incorrect, it should highlight [user]

Issue is now fixed

I pasted the openfga.ne file in https://omrelli.ug/nearley-playground/ and i'm not able to get my simple model to be parsed correctly. There is an error in the console that may be cause but i can't find it


Update readme for v0.1

The installation still points to node node_modules/stryker/src/Stryker.js --help while the src of stryker is now in the dist folder (until we change the package.json)

Do you think we should move the documentation about the mutations themselves to docs/mutations.md or something? We can point to that from the readme.md (with full url: https://github.com/infosupport/stryker/blob/master/docs/mutations.md)

@nicojs I think it's best to leave the mutations in the main README. This way all documentation is one place. If the size of the README increases in the future, it could be smart to move the mutations.
I have started working on this issue on https://github.com/infosupport/stryker/tree/v0.1-preparation


Some recently built crates fail to unpack

Error observed so far with selectors = "0.4.0" and glutin = "0.4.6" dependencies.
Output of cargo build --verbose:
    Updating registry `https://github.com/rust-lang/crates.io-index`
unable to get packages from source

Caused by:
  failed to unpack package `selectors v0.4.0`

Caused by:
  No such file or directory (os error 2)

    Updating registry `https://github.com/rust-lang/crates.io-index`
 Downloading xml-rs v0.2.2
 Downloading gleam v0.2.3
 Downloading objc v0.1.8
 Downloading dlib v0.2.0
 Downloading dylib v0.0.1
 Downloading core-foundation v0.2.0
 Downloading core-graphics v0.2.1
 Downloading wayland-kbd v0.3.4
 Downloading crossbeam v0.1.6
 Downloading osmesa-sys v0.0.5
 Downloading tempfile v1.1.3
 Downloading byteorder v0.4.2
 Downloading wayland-window v0.2.2
 Downloading shared_library v0.1.2
 Downloading wayland-scanner v0.5.8
 Downloading x11-dl v2.3.0
 Downloading glutin v0.4.6
unable to get packages from source

Caused by:
  failed to unpack package `glutin v0.4.6`

Caused by:
  No such file or directory (os error 2)

Running strace cargo install selectors on my machine yields this snippet just before it fails:
utimes("/home/tpg/.multirust/toolchains/stable/cargo/registry/src/github.com-88ac128001ac3a9a/12652521203/selectors-0.4.0/src/tree.rs", {{1454023299, 0}, {1454023299, 0}}) = 0
chmod("/home/tpg/.multirust/toolchains/stable/cargo/registry/src/github.com-88ac128001ac3a9a/12652521203/selectors-0.4.0/src/tree.rs", 0644) = 0
open("/home/tpg/.multirust/toolchains/stable/cargo/registry/src/github.com-88ac128001ac3a9a/selectors-0.4.0/.cargo-ok", O_WRONLY|O_CREAT|O_TRUNC|O_CLOEXEC, 0666) = -1 ENOENT (No such file or directory)

It appears that there's a timestamp inserted in the path which isn't being added everywhere.

I discovered this while trying glium. Setting the glutin version to 0.4.5 in Cargo.lock seems to work as a workaround.

Latest nightly does not show this error, but current beta does.

I'm seeing this behavior with the 0.7.0 release of cargo when fetching glutin 0.4.6.

I'm working on a fix, thanks for the report!
cc @SimonSapin, this is a bug where a newer Cargo published an archive that is triggering a bug in older Cargos. You may want to republish selectors with an older Cargo to ensure the tarball is compatible with older Cargos.

Ok, I've posted https://github.com/rust-lang/cargo/pull/2327 which should fix this error in the future.
If this crops up, the fix is unfortunately just that the original crate author needs to be contacted to republish with a version of Cargo with the fix or an older Cargo. Sorry for the inconvenience!

You may want to republish selectors with an older Cargo to ensure the tarball is compatible with older Cargos.

That’s… ugh. This is gonna be annoying, the "bad" tarballs are immutable on crates.io, so maintainers need to pick new version numbers.

What range of Cargo versions (nightly dates?) create "bad" tarballs? (How old "an older Cargo"?) The current Nightly according to multirust is 6ffd134 2016-01-26, and it looks like it it doesn’t have the fix yet.
What versions fail to install them? @programble @thepowersgang @darkstalker Is it practical for you to upgrade Cargo? Contrary to what multirust believes this can be done independently from upgrading rustc.
Is there a way to tell that a given version of a crate.io package is "bad", other than trying to install it?

Yes unfortunately maintainers will need to:

Yank these versions
Publish new versions
Recommend newer versions of Cargo

This bug was merged on 44c0d7b78548c83b6df4935fdbb15be62f30d685 which was commited on 1/25 but didn't make it out until the 1/27 nightly. It looks like the fix didn't make it outlast night, sot he affected Cargo versions are the 1/27 nightly to what I presume is today's, 1/29 nightly.
Any version of Cargo prior to 1/27 will fail to install tarballs published by the affected Cargo versions.
There's not really anyway to tell crates.io whether a package is bad, all the tarballs being upload are indeed valid tarballs. Older cargos just interpreted a valid GNU archive in a buggy manner.

There should be a test which tries to unpack a package with an older Cargo version.

Is there any issue tracking remediation here? I agree with @nox that there should be a check, ideally on the server side at upload time.

I meant that Cargo itself should include tests that test newly-created packages against older versions of Cargo, not a safety check at upload-time of third-party crates.

Ah, that makes sense. I think that there should be a check at upload time given the append only nature of crates.io. I guess this should be an issue against that project instead.

This downloads 389 crates uploaded between January 25 and Feb 4 16:04:06 2016 +0000 (according to git commit dates in the index)
git -C ~/.multirust/toolchains/nightly/cargo/registry/index/github.com-* log --format='%ai %s'|
grep -E '^2016-0(2|1-2[5-9])'|
grep Updating|
cut -d'`' -f2|
tr '#' ' '|
awk '{print "https://crates-io.s3-us-west-1.amazonaws.com/crates/" $1 "/" $1 "-" $2 ".crate"}'|
xargs wget

This shows the 27 of them whose tarball is in GNU format:
for i in *.crate; (gzcat $i|file -|grep -q GNU) && echo $i

blake2-rfc-0.2.14.crate
blas-sys-0.5.1.crate
blas-sys-0.5.2.crate
cargo-edit-0.1.1.crate
ears-0.3.3.crate
egc-0.1.1.crate
egc-0.1.2.crate
glutin-0.4.6.crate
indexing-0.1.0-alpha3.crate
inner-0.1.0.crate
lapack-sys-0.6.0.crate
lapack-sys-0.6.1.crate
libedgegrid-0.1.1.crate
libnotify-0.3.0.crate
libnotify-sys-0.3.0.crate
linked-hash-map-0.0.8.crate
lru-cache-0.0.6.crate
murmurhash64-0.3.0.crate
ndarray-0.4.0-alpha.1.crate
pandoc-0.3.0.crate
pandoc_ast-0.2.0.crate
rx-0.0.0.crate
selectors-0.4.0.crate
serde_xml-0.6.2.crate
skiplist-0.2.10.crate
splitmut-0.1.0.crate
xdrgen-0.1.9.crate

This shows other versions of the same crate for each of them:
for i in *.crate; (gzcat $i|file -|grep -q GNU) &&
(echo; echo '## ' $i; ls $(echo $i|rev|cut -d- -f2-|rev)-*|grep -v $i)

And with some manual filtering, these are the crates that likely need to be fixed (the crates in GNU format who do not have a later semver-compatible version in non-GNU format)
blake2-rfc-0.2.14.crate
cargo-edit-0.1.1.crate
egc-0.1.2.crate
indexing-0.1.0-alpha3.crate
inner-0.1.0.crate
lapack-sys-0.6.1.crate (has later, semver *incompatible* versions)
libedgegrid-0.1.1.crate
libnotify-0.3.0.crate
libnotify-sys-0.3.0.crate
linked-hash-map-0.0.8.crate
lru-cache-0.0.6.crate
murmurhash64-0.3.0.crate
pandoc-0.3.0.crate
pandoc_ast-0.2.0.crate
rx-0.0.0.crate
serde_xml-0.6.2.crate
skiplist-0.2.10.crate
splitmut-0.1.0.crate
xdrgen-0.1.9.crate


Add ecr registry policy

I think this is the last relevant policy endpoint for ECR 😄 was fun to work again on moto 💪
And of course the Terraform tests are looking nice 🙂

was fun to work again on moto :muscle:

That's always good to hear :slightly_smiling_face:


LoRA compatibility

Is there a way to make LoRA works with your script ? I have enter the name of my lora file in the prompt but it doesn't works, thanks

Everything that works in Automatic1111/web-ui should work with the script also. The main reason to use web-ui API instead of Diffusers pipeline, for example, is to keep all features that web-ui brings. If there is something that does not work with a script that works in web-ui the most likely reason is a wrong API call format or the issue in the API itself.

You have right the problem was my settings I got LoRA working after change the denoising and the hed weight in the script.py


Collect pod specific process information such as ps output, memory etc

Although we have pod level detail within k8s, there are times it may be necessary to understanding the process level utilisation of CPU and memory within the pod/container to assess inefficiencies.
At present, one would need to instruct the customer to access the pod to run various commands which can be prone to error.
Describe the solution you'd like
The objective of this issue is to explore collecting pod specific process information such as ps output, memory etc.

Some of the commands that have been asked to run are below, it would be nice to have all of this in the support package if needed.
cat /sys/fs/cgroup/memory.stat from within a Ingress Controller pod
for p in $(pidof nginx nginx-ingress); do sudo pmap ${p} -X; done from the k8s node running the Ingress Controller pods
for p in $(pidof nginx nginx-ingress); do cat /proc/${p}/status; done since azure was unable to run the command above
Collect the following information from the API endpoint from the pods
/api/8/processes
/api/8/connections
/api/8/slabs
/api/8/http/requests
/api/8/http/server_zones
/api/8/http/location_zones
/api/8/http/caches
/api/8/http/upstreams
/api/8/http/keyvals

@mrajagopal maybe an implementation of https://pkg.go.dev/k8s.io/metrics#readme-apis will further help, if not already there ofc

Our plan is to deploy a custom container as a sidecar in the pod to fetch the necessary data.

As a temporary measure, we can attached a container to the nginx-ingress container and collect the data needed:

pod=$(kb get po -n kic-0 -o name); kb -n kic-0 debug -it $pod --image=alpine:latest --target=nginx-ingress -c f5-debugger

Once the alpine container is created, you should get a shell prompt to that container where you will need to add curl and jq (optional):

/ # apk add curl jq

As we have attached this f5-debugger container to nginx-ingress container, we can now get the API output using curl and jq :

for i in /api/8/processes /api/8/connections /api/8/slabs /api/8/http/requests /api/8/http/server_zones /api/8/http/location_zones /api/8/http/caches /api/8/http/upstreams /api/8/http/keyvals; do echo "**** $i ****" ; curl "<IP_ADDRESS>:8080/$i" | jq .; echo ""; done


Add "apps" command

From user commentary in Pinax Slack, it's not obvious how to determine the current version of a Pinax application. Either poke around the source on github, or know enough to look at PyPi, neither option is quite as simple as invoking an "apps" command with pinax-cli.
$ pinax apps would simply list the current released Pinax applications and their latest versions. Perhaps something like:
Release Application
------- ---------------
1.3.1    django-user-accounts
2.0.4   pinax-announcements
5.0.2   pinax-blog
1.1.0    pinax-calendars
1.1.2    pinax-eventlog
1.0.0    pinax-events
2.0.0    pinax-images
2.0.4    pinax-likes
1.0.1    pinax-messages
1.0.0    pinax-news
3.2.1    pinax-stripe
1.0.5    pinax-testimonials
1.1.1    pinax-waitinglist
2.0.4    pinax-webanalytics

Although there's only one theme now, presumably a "themes" command would be useful as well.


clarify the algorithm?

thanks for your share. and could you please give any details about the algorithm? maybe a paper link?

Thanks for the advice! I will update recently.


Update netlify.toml

Added chmod +x to build.sh as the netlify build step fails due to execution permissions.

That's odd. It built on Netlify before, and it should just pick up the permissions from Git. I wonder if something broke on the Netlify end.

After much googling I found a few others that encountered similar issues. I thought I should share as this was the only part of your tutorial that tripped me up.  It could have something to do with my repository or netlify account as well. It really can't hurt to include it.  Great write up and I appreciate your blog :)


PROD-2217 Add "cookies" column to datamap report table

Description Of Changes
Add cookies column to datamap report
Code Changes

[ ] Add column to datamap report

Steps to Confirm

[ ] Go to Systems & Vendor and Edit a system data use
[ ] Add some cookies to the Data Use
[ ] Go to Data Inventory > Reporting
[ ] Confirm that the colum cookies is visible and display the values as tags with the grouping option
[ ] Confirm that when clicking Edit column, the cookies column is visible and can be turned on/off

Screenshots
Datamap with cookies column, group all

Datamap with cookies column, display all

Edit columns modal

Pre-Merge Checklist

[x] All CI Pipelines Succeeded
[x] Issue Requirements are Met
[x] Update CHANGELOG.md

@lucanovera any ideas on why I'm not seeing my cookies reflected in the "cookies" column?
https://www.loom.com/share/e766ed358b8d4501a61e2b5f3d90a180?sid=28ae096a-8e63-4a28-b5d5-4d38b171a493


Support for conditional validation with class-validator

Looks solid to me. It also adds @ValidateIf in general, which is nice.
It works for simple expressions. Other use cases may include calling a special function inside, e.g. @ValidateIf(o => runCustomTest(o)). However, this needs more complex parsing and collecting imports similar to the @DtoCastType decorator. I think we can keep it simple for now and may extend it when someone requests it.


Switched $key and $value to .key and .value

Hi, it's really great to be able to grab the keys of array items as I can finally edit/remove childs.
I am wondering why choosing the dot-prefixed syntax as this prevents from using dot notation to access array object props. I don't know if my limited knowledge of JS makes me miss something but wouldn't prefixing with underscores as _id or _value would be similar but permitting dot notation use?

Great point and I agree it's not perfect, but the underlying Firebase library will actually properly handle writes with objects that contain .value, so I wanted to make it as easy as possible to write back data to Firebase without having to update the object in question. For example, this will actually work with the Firebase client:
ref.set({
  '.value': 'foo'
});

While this will throw an error:
ref.set({
  '$value': 'foo'
});

So in order to write back data you got from ReactFire, all you need to do is remove the .key attribute, regardless of if the value is a primitive or an object.
Hopefully that all made sense!


[MM-34595] Provide a way for plugins to force the team sidebar to be visible

Summary
Provide a method in PluginRegistry, that forces team sidebar to be visible.
Ticket Link
https://mattermost.atlassian.net/browse/MM-34595
Related Pull Requests
Screenshots
Release Note
Provided a method in PluginRegistry, that forces team sidebar to be visible.

Hello @dezerb,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!

Thanks for this @dezerb!! I have just one request to remove some duplication from the store types, and a few questions.
For QA manual testing, we will need a plugin that implements this, which is usually done in https://github.com/mattermost/mattermost-plugin-demo. @dezerb Would you be up for adding a piece of functionality in that project that uses this new feature? It can be implemented as a client-side slash command using registerSlashCommandWillBePostedHook

Hi, I made changes according to your change request. Appropriate QA plugin changes will comes in next days.

Heads up that as part of our efforts to move to a monorepo, we're closing out a number of older pull requests like this one to help streamline the effort.
If you'd like to preserve these changes -- even if you're not the original author! -- feel free to resubmit the pull request against the monorepo once it's ready. You can subscribe to mattermost-server-issue-22420 for status updates on this effort.


Unclear CreateDockerPackage.ps1 + SFBinaryLoader.cs logic

It is unclear to me how the CreateDockerPackage.ps1 works and what it is for. As far as I understand, this removes the Microsoft.ServiceFabric.Data.Interfaces.dll and any System.Fabric.*.dll present in the publish directory. As far as I understand these dependencies should be dynamically loaded once more through the SFBinaryLoader.cs class.
However I have the following questions:

I am remoting to my cluster node that will be running SF code. If I try to inspect the FabricCodePath environment variable, there is nothing set.
If I run an instance of the microsoft/service-fabric-reliableservices-windowsservercore:latest image and try to look at the FabricCodePath environment variable, it is also not set.
Does this mean that I need to change this variable somehow?

Also, after building and publishing my container I remotely connect to my node and manually pull the image (to debug it). I I try to run the init.bat script I get the following error:
 An assembly specified in the application dependencies manifest (MyOrg.Fabric.TestContainerized.deps.json) was not found:
    package: 'Microsoft.ServiceFabric.Data.Interfaces', version: '4.0.470'
    path: 'runtimes/win/lib/netstandard2.0/Microsoft.ServiceFabric.Data.Interfaces.dll'

It looks like since these files were removed from the image with the CreateDockerPackage.ps1 the process is unable to run. Is there something I might be missing?

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

ID: 7acd6be9-dfb2-9569-ff34-cad061c47cb4
Version Independent ID: 6e0fcc47-fd74-45b2-f8be-d61fb270f186
Content: Containerize your Azure Service Fabric services on Windows - Azure Service Fabric
Content Source: articles/service-fabric/service-fabric-services-inside-containers.md
Service: service-fabric
GitHub Login: @athinanthny
Microsoft Alias: anmola

@luisbecerril-ips Thank you for your query , our team will further look into it and get back to you at the earliest.

@athinanthny please add your inputs

I am reaching out to the internal teams. i will update here once i have some information

@athinanthny please answer the users question and update the doc if needed


Can this software work with Pi 4?

Can I run this on a Raspberry Pi 4 if I connect an external LED to it?

Only if someone comes up with a way to use a Raspberry Pi 4 with the Arduino IDE. So far, no one has (as far as I know).
You're welcome to independently re-implement what I have (port) it to ARM Linux in a way that it would work on an RPi 4 and external LED. But, it would be much less effort to purchase an already compatible RPi Pico, drag and drop the .uf2 file, and connect an LED + resistor.


Settings: hide admin options for non-admin users

If the user is not an admin, since currently an external bug prevents to run centennial apps as Admin, hide the General Settings options:

This change will be rolled back once the external bug will be fixed.

Ref for the external bug https://github.com/microsoft/PowerToys/issues/1135

Fix available in 0.15.0 https://github.com/microsoft/PowerToys/releases


Fix bug sigmoid plots

Fixed off-by-one error (#17)

Thanks, let's see whether it works or not :)


Updating the app

I just updated the app and the database has broke:
Taking a database backup (saving as openeats.sql)...
Error response from daemon: Container b5935563bd04606d8fa193e96bcc6b669dfd6d0d38f46b8d62081aeb64516fe0 is restarting, wait until the container is running
openeats_db_1 is up-to-date
ERROR: for api  Container "b5935563bd04" is unhealthy.
ERROR: Encountered errors while bringing up the project.
App started. Please wait ~30 seconds for the containers to come online.
What is happening? I followed the update the app steps

Solved. I changed docker-prod.yml to pick latest mariadb vy removing the version.
Now It works.


Use ForEach to reduce stack usage

This builds on the improvements made in #809. Using ForEach reduces the number of calls to f compared to using TupleView.
I assume what happens is the type information needed is significantly lower when there is only one instance of the type.
So for a 10 element TupleView it would be:
TupleView<(F, F, F, F, F, F, F, F, F, F)>

But for a 10 element ForEach it would be:
ForEach<Range, Int, F>

I tried to measure it as described in #806 with reg read sp and calculate the difference between start and the fromNodes call. These are the deltas:

main - 610528
shadowfacts/fix-stack-overflow - 115168
stack-foreach-optimization - 29680

Could you confirm @shadowfacts?

I see a similar improvement. My concern is that using ForEach with an int range like this means that the the views in the ForEach are identified by their indices, which could cause state tracking issues if views are reordered. It's for that reason that the range initializer is annotated with @_semantics("swiftui.requires_constant_range") and the docs specifically note:

The instance only reads the initial value of the provided data and doesn’t need to identify views across updates. To compute views on demand over a dynamic range, use ForEach/init(_:id:content:).

Would that cause problems here? The ranges are all constant, it's the ForEach itself that is swapped out when the count is updated.

I don't know for certain that it would cause problems, I just think it's something to be aware of. If you've tested it and there don't seem to be adverse effects, I'm good with this change.


Globe lambertDiffuseMultiplier test failing/timing out

In the latest main, one unit test is either failing or timing out all of a sudden.

error in the console (thanks @ebogo1):
An error occurred in "SingleTileImageryProvider": Failed to load image Data/Images/Red16x16.png

Unit test link
Browser:
Chrome 98.0.4758.80
Firefox 97.0.2
Operating System: Ubuntu 18.04

Fixed in https://github.com/CesiumGS/cesium/pull/10263#issuecomment-1086262447


rows not cleaned out on pg_restorebinary

pg_restorebinary --truncate - doesn't delete rows if the target table should be empty
We did a pg_dumpbinary of a Database including an empty table
then we added a row into this empty table.
After pg_restorebinary of the above dump, the row still exists.
Regards Simon - LzLabs

Hi Simon,
I'm not able to reproduce the issue using v2.9. Can you please post the command you are using? What is the exit code of pg_restorebinary?
Regards

Got it, truncate was not applied when the table was empty at dump time. Commit a1de12d fixes this issue.


feature add docs for SHOW-CATALOG-RECYCLE-BIN

Signed-off-by: nextdreamblue<EMAIL_ADDRESS>Proposed changes
relation with: https://github.com/apache/doris/issues/8421
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[x] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[x] No Need

Has document been added or modified:

[x] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[x] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[x] No

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...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.78 seconds
load time: 440 seconds
storage size:<PHONE_NUMBER>7 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221111072047_clickbench_pr_44154.html